Related
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
shouldn't you be flashing disable_encrypt zip too?
repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside
PROdelision said:
shouldn't you be flashing disable_encrypt zip too?
Click to expand...
Click to collapse
No, its not required.
chiplovez9x said:
repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside
Click to expand...
Click to collapse
Make sure you have allowed modifications on system partition and also you dont have system as read only.
Does fingerprint working on GSI?
what is gsi?
I don't know much but gsi means u can flash almost all roms (which have images). And most of ROMs do have gsi images.. So u can install any rom on your phone. I don't know the steps to do so.. ?
bryanngapopala said:
what is gsi?
Click to expand...
Click to collapse
Simple speaking it's a image with clear android from google
Has anyone tested RR PIE GSI on RN7? Does it work?
Is it possible to boot Android O GSI? :silly:
letsmakecakes said:
No, its not required.
Click to expand...
Click to collapse
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.
Is the. Method the same for the global version with global rom?
letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Which GSI should be needed to take? A-only or A/B ?
PROdelision said:
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.
Click to expand...
Click to collapse
I have no experience with GSI images, but I know in general that PIE breaks the encryption, if you roll back the security patch level. I don't know it this happened in your case, but I have lost couple of times my encrypted storage when I have tried to restore a backup of rom with older android patch level. After that, the bootup encryption pin is no longer accepted, neither by android nor by twrp, so the only option is to format data to remove encryption and start from scratch.
Were your miui beta and rr gsi of the same android security patch level?
Getting WRONG PIN error after setting up pin ???
letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Hi!
Did you not disable dm-verity and force-encryption?
Another question, the dev MIUI roms contain both the system and vendor partitions, right? How do you install only the vendor partitions from them? Or do you just flash MIUI and then reflash the custom ROM system? In that case, won't that affect dm-verity and encryption on the data partition?
Flashing correctly a GSI like in this guide; with vendor ecc ecc, will gcam work? Actually i'm on stock MIUI 10 and obv all working fine with a perfect version. My doubt is it.
Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?
any recommended gsi rom with no bug?
booladi said:
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Did you not erase your /data partition through TWRP?
Click to expand...
Click to collapse
I did wipe userdata but not internal storage. heard its because i have unencrpyed data partition?
I would like a help, so I'm trying to install the rom via mi flash, but not installing the rom, it's in 500sec and nothing to complete the installation, luckily I was able to install via TWRP, however when I try to update via Android OTA 10 I get stuck in the bootloop.
need more info.
You installed Twrp I assume over the stock rom?
if so boot into TWRP and format user data. ( note this wipe completely erase the phone. but you have no choice it must be done. if you have files that you want on the phone, see you can access them via Windows explorer and copy them over to your desktop.
Basic Instructions
FORMAT /data partition (Important Never Ever Wipe System Or Persist!)
Copy our ROM to the internal storage or use external USB drive ( must choose which device to install from in twrp)
Install ROM, and anything else depending on rom if needed such as gapps
Reboot to recovery
Reboot to system and setup
tsongming said:
need more info.
You installed Twrp I assume over the stock rom?
if so boot into TWRP and format user data. ( note this wipe completely erase the phone. but you have no choice it must be done. if you have files that you want on the phone, see you can access them via Windows explorer and copy them over to your desktop.
Basic Instructions
FORMAT /data partition (Important Never Ever Wipe System Or Persist!)
Copy our ROM to the internal storage or use external USB drive ( must choose which device to install from in twrp)
Install ROM, and anything else depending on rom if needed such as gapps
Reboot to recovery
Reboot to system and setup
Click to expand...
Click to collapse
Now I managed to install the rom with Android 10 global, but the region is only in China, I can't change it and this one without facial unlocking.
NikolasG. said:
Now I managed to install the rom with Android 10 global, but the region is only in China, I can't change it and this one without facial unlocking.
Click to expand...
Click to collapse
I believe that @Agimax has a flashable mod on his stable page for changing regions, that seems to be a bug with the latest stable version.
Check here, and maybe tried pinging Agimax, if you need assistance.
https://forum.xda-developers.com/mi-8/themes/mods-miui-global-beta-region-free-t3898459/page5
Another option is flashing the latest Xiaomi.EU, which has every available feature some of which have not yet found their way to the stable build.
For the download links check Option 2
https://forum.xda-developers.com/mi-8/how-to/miui-11-xiaomi-eu-rom-released-t3974643
Hello, I have a Samsung Galaxy A6+ with latest fw installed.
(italian version)
A605FNXXU7CUD4
The phone is totally useless after the update to android 10, it takes AGES to perform any action, even open the Camera or open a Message.
Already tried to wipe everything, hard reset, reinstall fw. Still useless.
Since I’d like to downgrade to Android 9 to have back a useful phone, I tried to install the latest Android 9 fw with Odin.
A605FNXXS5BTB1
But it fails, saying SW REV CHECK FAIL : [aboot] Fused 7 > Binary 5
What can I do?
Is there any chance to downgrade this phone?
Thank you
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
nqnxev said:
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
Click to expand...
Click to collapse
Almost done, but I can't find any custom rom available for download. Can someone help? Since wwith twrp I cannot install a stock rom. Thanks in advance.
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Ecto1000 said:
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Click to expand...
Click to collapse
I proposed three different options: custom rom, GSI (generic system image) or conversion stock firmware to flashable form. If there's no good custom rom for A6+, then don't worry - you can still try another options. Try playing with Generic System Images:
1. Flash your current stock firmware as usual in Odin.
2. Unlock bootloader and flash TWRP.
3. Go to TWRP.
4. Wipe partitions cache, dalvik, data, system (don't wipe vendor partition - it's needed).
5. Flash GSI image (recommended will be at first phhusson's AOSP (Android 9 or 10)) as "system image". You always need to choose and download "arm32_binder64" variant of img file.
6. Reboot to your new system.
Second option is to convert stock Android 9 firmware into flashable form.
1. Download ClassyKitchen tool.
2. Import downloaded Android 9 stock firmware (for your phone) into it and save it as flashable zip.
3. Go to TWRP.
4. Wipe cache, dalvik, data, system and vendor.
5. Flash your previously done zip with Android 9 as any other flashable zip in TWRP.
6. Flash Magisk or RMM-state-bypass-v3 in TWRP to prevent your bootloader from getting locked again.
7. Reboot.
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Success, success also for RMM-state-bypass-v3.
I rebooted but I'm again stuck in the same loop described in my previous reply.
When I selecr REBOOT in twrp, do I have to flag anything? For example System?
Regarding the first option, if I go there:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
exactly which file do I have to download among ASSETS of any release?
Thank you very much
Ecto1000 said:
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Click to expand...
Click to collapse
Yes, it's correct. If RMM bypass or Magisk.zip was flashed without any errors in TWRP then everything is okay. Just reboot to system in TWRP after that - there is option to reboot directly to system. First boot always can take a bit longer than next boots.
Ecto1000 said:
exactly which file do I have to download among ASSETS of any release
Click to expand...
Click to collapse
You always need to get any "arm32_binder64" (always AB) image. Gapps or vanilla is just your choice. Just get Android 9 or 10 image and flash it as "system image" (but wipe at first partitions specified in my previous post - don't wipe only Vendor partition, because it contains important things). Android 12 GSI still aren't stable. Android 11 - maybe will work properly. Android 9 and 10 should work fine. There is even short article about GSI on Galaxy A6+ with some fixes for that device attached:
Samsung Galaxy A6 Plus (2018)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
You can try of course other GSI's as well:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Ecto1000 said:
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Click to expand...
Click to collapse
You need to reboot to recovery after flashing new system, because just after flashing TWRP doesn't recognize it - that is why you see that "no OS installed". Just reboot your phone to recovery again (you have such option in TWRP). In case of GSI (except maybe CAOS, LineageOS Q/R mod) Magisk or RMM bypass is not needed.
Btw, in case of any problems with hardware support on GSI flash also that patch in TWRP (it may be needed to mount "Vendor" partition in TWRP before flashing that fixes):
Fixes.zip
drive.google.com
Thank you again for your help.
I already rebooted to recovery and twrp keeps saying NO OS.
I'm using twrp 3.5.2_10-0.
I'm starting to suspect that this behaviour is due to the fact that this version of twrp could be too much new and unstable for my phone.
So I'd like to install an older version of twrp with Odin, as explained here:
TWRP for SM-A605FN Samsung Galaxy A6+
How to Install TWRP 3.2.3-1 on Galaxy A6+ SM-A605FN Android 8.0.0 Oreo. Once you installed TWRP recovery on your Samsung Galaxy A6+ SM-A605FN, you can customize it, Rooting or installing custom ROM
www.recovery-mode.com
But I cannot manage to go into download mode again, even from REBOOT menu of twrp it doesn't work, I keep staying in the loop explained before.
Moreover your first option of GSI need me to go into download mode to install the latest stock ROM with Odin.
I just manage to get into the attached screen.
Any idea?
Thank you again
It's not possible to ignore that message and just flash latest stock firmware via Odin? Odin refuses flashing latest stock firmware?
Other builds of TWRP for your devices you'll find here:
Releases · roynatech2544/TWRP_device_samsung_a6plte
Contribute to roynatech2544/TWRP_device_samsung_a6plte development by creating an account on GitHub.
github.com
But don't use TWRP older than 3.4.0, because it doesn't have support for "Vendor" partition.
Yes, I managed to ignore that screen and go in download mode again.
I tried to follow your first option since the second one was not successful.
Installed latest stock and then twrp 3.5.0-1.
Wipe as you explained, I flash the Gsi
system-quack-arm32_binder64-ab-gapps.img
The flash is very fast, but no errors, is it normal?
After that I reboot to recovery in order to flash
Disable_DM-Verity_ForceEncrypt_11.02.2020
it goes but just at the end it gives the error
failed to mount /odm no such file or directory.
And if I reboot to system the phone loops as always.
I'm losing all hope...
Ecto1000 said:
system-quack-arm32_binder64-ab-gapps.img
Click to expand...
Click to collapse
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Ecto1000 said:
The flash is very fast, but no errors, is it normal?
Click to expand...
Click to collapse
If you flashed it as "System Image" and it was successful then yes - should be fine. DM-Verity isn't needed for GSI - only RMM bypass v3 is sometimes needed (on CAOS, Lineage Q/R mod and maybe in case of some other images). On usual A600FN RMM bypass is not needed on phhusson AOSP. Just format "Data" partition (format, not only wipe) - it will remove encryption for you.
Procedure of flashing should be like that:
1. Wipe: cache, dalvik, data, system ("Vendor" partition leave untouched, because it's important for GSI - that is why you needed to flash stock firmware at first, because it adds vendor files for your phone, but it's needed only once, just don't wipe "Vendor").
2. Flash your GSI as "System Image".
3. Reboot phone (to recovery again).
4. Mount your "data", "vendor" and "system" partition.
5. Flash your zips: RMM bypass v3 (optionally Magisk).
5. Reboot to your new system now.
In case of any hardware support problems, reboot to TWRP again, mount "Vendor" partition and flash that fixes:
Fixes.zip
drive.google.com
Try to boot Android 10 or Android 9 images. If it will succeed, then you can try flashing Android 11 images and check what works, and what not. According to that article
nqnxev said:
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Click to expand...
Click to collapse
I don't know what are those images. Can you explain better?
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Can this be related to the hardware support problems you mentioned?
I tried with different versions of Twrp already and with Havoc Os too.
Should I try with flashing a different ROM ?
Thanks again
Ecto1000 said:
I don't know what are those images. Can you explain better?
Click to expand...
Click to collapse
Just look at filename of system images. But as I see, it's apparently important on Android 11 and newer. For now, try to boot Android 10 or 9. Let's try with that image:
https://github.com/phhusson/treble_experimentations/releases/download/v222/system-quack-arm32_binder64-ab-vanilla.img.xz
1. Decompress that image.
2. Copy to SD card or to internal storage.
3. Wipe cache, dalvik, data, system.
4. Format data partition (it's needed only once).
5. Flash downloaded and extracted file as "System Image".
6. Reboot phone to recovery (again).
7. Select in TWRP: Mount -> system, data, vendor.
8. Flash RMM bypass v3 (or Magisk).
9. Reboot now to system.
10. In case of some things not working, go back to TWRP and mount vendor partition (Mount -> tick "Vendor" -> go back to flashing zips) and flash that:
Fixes.zip
drive.google.com
11. Reboot to system again and check if now everything works properly.
Ecto1000 said:
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Click to expand...
Click to collapse
Yes, because you need to mount that partitions in TWRP:
Mount -> tick "system", "vendor" and "data" - and now flash whatever you want.
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Maybe I have to try with sideload ?
Ecto1000 said:
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Click to expand...
Click to collapse
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
nqnxev said:
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
Click to expand...
Click to collapse
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Ecto1000 said:
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Click to expand...
Click to collapse
I've never had such problem, but according to that thread it seems that it's a fault of modified kernel (so don't flash Magisk with GSI, because it patches kernel).
Try to flash stock firmware, unlock bootloader, flash TWRP, format "data" partition, wipe partitions (cache, dalvik, system, data) and flash GSI image as "system image". And reboot to system.
Don't flash RMM and Magisk for now - and check if system will run properly.
I got an European Realme X2 pro on which i now got TWRP running (after flashing a modified vbmeta image and only one TWRP version seems to work). Of course the bootloader is unlocked. The problems is that when i change setting in TWRP and reboot it doesent save them.
Also when i install a lineageos 19 zip, this goes through without an error, but it only boots to bootlaoder.
After rebooting (from twrp) files in /sdcard are gone, is this normal?
And lastly when i go to wipe in TWRP it doesent give me the option to wipe system, altough i can "mount" system. In Backup TWRP shows that there is a system partition which has 1450mb.
Thanks for your replies in advance
Links:
Modified TWRP and modified vbmeta: https://forum.xda-developers.com/t/...l-twrp-for-rui2-realme-x2-pro-stable.4388355/
Lineage: https://forum.xda-developers.com/t/...-realme-x2-pro-rmx1931-cn-unofficial.4355023/
Hey, my 9 power has an NVT-TS touch panel. All android 11 based ROMs seem to work such as Pixel Blaster and Lineage. However, when we talk about Android 12, my touch seems to only work on Evolution X.
I tried installing PixelPlusUI and PixelOS, however my touch does not work in them. If I try installing a custom kernel with those two, the OS does not boot and the phone gets stuck on the Redmi boot logo.
I have tried many fixes from various threads but nothing seems to work.
Anybody with a workaround or suggestion?
Update: Only a previous version of EvoX works. The latest version does not boot.
Hi. What kernel and recovery did you used for a12 rom ? Can you put here links to twrp/kernel and roms used in process ? Thanks. I have the same model with nvt touch and nothing worked for me and now i'm back to stock miui 12.5.11 global.
I used PitchBlack Recovery but also tried 2 different TWRP and Orange Fox Recoveries. I tried flashing various kernels but none worked. In the end, the kernel within the evox rom itself had to be used.
Hello,
I'm actually running fine a CrDroid on android 12 without issue.
Here's how i flashed it :
FOR JUICE!
1. Reflash the Firmware using MiFlash (From clean all and lock, change it to clean all Only)
2. Boot your device to Fastboot mode and Connect your device again to the PC
3. Download Minimal ADB and Fastboot and Install it, as follow the Instructions.
4. Download the OrangeFOX Recovery, download the Xiaomi.eu Rom, and download your Favourite Custom Rom.
5.Go to the Directory of Minimal ADB and Fastboot ----> C:\Program Files (x86)\Minimal ADB and Fastboot
and paste the recovery.img from the Archive in the Directory of Minimal ADB and Fastboot
6. Launch the Minimal ADB and Fastboot.exe Shotcut from the Desktop and type these commands:
1. Fastboot flash recovery recovery.img
2. If you want to reboot the device Fast type Fastboot reboot
7. Boot the device to the OrangeFOX Recovery, go to the Menu and open the Settings
8. From the Settings select General and uncheck Mount system and vendor read-only
9. Important! To install Successfully the Rom u need first to format the Data, go to Wipe section, select Format Data, type yes and Confirm.
10. Disconnect the Phone, connect it again to the USB and drag the Xiaomi.eu rom zip and the Custom Rom zip to the Phone
11. First u need to Install the Xiaomi.eu Rom zip this is Important!
12. When the flashing of the Xiaomi.eu Rom zip is Complete, u can flash your Favourite Custom Rom
13 Final Step: Format the Data with typing Yes again and Reboot the device, Enjoy!
From another XDA Post : https://forum.xda-developers.com/t/...onsive-with-custom-roms.4342665/post-86009079
Except i didn't fhashed an old CrDroid release, but the latest. Android 12 work just fine on my Juice with the same screen as yours
uzurka said:
Hello,
I'm actually running fine a CrDroid on android 12 without issue.
Here's how i flashed it :
FOR JUICE!
1. Reflash the Firmware using MiFlash (From clean all and lock, change it to clean all Only)
2. Boot your device to Fastboot mode and Connect your device again to the PC
3. Download Minimal ADB and Fastboot and Install it, as follow the Instructions.
4. Download the OrangeFOX Recovery, download the Xiaomi.eu Rom, and download your Favourite Custom Rom.
5.Go to the Directory of Minimal ADB and Fastboot ----> C:\Program Files (x86)\Minimal ADB and Fastboot
and paste the recovery.img from the Archive in the Directory of Minimal ADB and Fastboot
6. Launch the Minimal ADB and Fastboot.exe Shotcut from the Desktop and type these commands:
1. Fastboot flash recovery recovery.img
2. If you want to reboot the device Fast type Fastboot reboot
7. Boot the device to the OrangeFOX Recovery, go to the Menu and open the Settings
8. From the Settings select General and uncheck Mount system and vendor read-only
9. Important! To install Successfully the Rom u need first to format the Data, go to Wipe section, select Format Data, type yes and Confirm.
10. Disconnect the Phone, connect it again to the USB and drag the Xiaomi.eu rom zip and the Custom Rom zip to the Phone
11. First u need to Install the Xiaomi.eu Rom zip this is Important!
12. When the flashing of the Xiaomi.eu Rom zip is Complete, u can flash your Favourite Custom Rom
13 Final Step: Format the Data with typing Yes again and Reboot the device, Enjoy!
From another XDA Post : https://forum.xda-developers.com/t/...onsive-with-custom-roms.4342665/post-86009079
Except i didn't fhashed an old CrDroid release, but the latest. Android 12 work just fine on my Juice with the same screen as yours
Click to expand...
Click to collapse
Hi. What type of screen do you have ? Can you put the link here to download what rom you installed ? Thx.
I have the exact same type of screen than you, NVT-TS
I downloaded the rom from the official website of CrDroid : https://crdroid.net/juice/8
For the stock zip (step 11), i used this one : https://sourceforge.net/projects/xi...i_HMNote94G_HM9T_21.11.24_v12-11.zip/download
Btw, use crdroid 8.6 for juice. ATM 8.7 don’t work with touchscreen afaik. I did have to reinstall 8.6 after update
uzurka said:
Btw, use crdroid 8.6 for juice. ATM 8.7 don’t work with touchscreen afaik. I did have to reinstall 8.6 after update
Click to expand...
Click to collapse
Thank you, crdroid 8.6 worked. However, I wanted to use ROMs like Pixel Experience and PixelPlus but they touch does not work on them.
Atm, PixelPlusUI or PixelExperience are A12 AOSP with integrated Gapps (probably others differences but no matter), use flamegapps to get full gapps package and there you go!
Atm, i tried a lot of roms, and with A12, only CrDroid8.6 works...