Develop Bugs

[GUIDE] Flash (almost) ANY GSI rom on Realme Q. RM5P should work too!

Original thread.
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software. *This is not entirely true for Realme devices since bootloader unlock or custom rom flash via TWRP or fastboot does not void your warranty but rooting does.
* So I heard. But that's question of detail.
* Same statement for XDA.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Update.:
As you already know development on realme devices suck beacuse of ****ty or incomplete sources, lack of developers interest and biggest reason is lack of community support.
Our man here @BabluS is a legendary developer of Asus Zenfone Max M1 Pro and is willing to compile stable ROMs for our device. But, he needs some donations to buy the device. He has already compiled Android 10 (PE) for our device which is 99% stable. To continue this tremendous work he needs to have the device in hand.
Reasons To Donate:
1. Official PixelExperience ROM
2. Official POSP ROM
3. Will maintain & provide public Device Trees/Sources (So anyone can compile ROMs)
4. More development for realme 5 Pro
Name : Baswanth Madhav Saladi
Donate Using UPI: [email protected]
Donate using Paypal : [email protected]
Send screenshots of payment to @orgasmtron
We have to reach 6-7k in total out of which we have collected 2.6k..
Keep donating & get closer to stable custom ROM experience. Kudos!
All the donations will be public.Anyone can view and verify them.All details will be transparent.
NOTE:
We will update money collection daily evening. All details will be transparent.
List of Donators will get updated here
CLICK HERE TO CHECK!

Has anybody got Android 10 working properly?

tonibm19 said:
Has anybody got Android 10 working properly?
Click to expand...
Click to collapse
Yes. Method is same.

greenys' said:
Yes. Method is same.
Click to expand...
Click to collapse
Yeah but I mean, everything is working fine?
Fingerprint? Camera?

tonibm19 said:
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
Click to expand...
Click to collapse
Dunno. As I said I never tried Android Q. But I presume fingerprint is missing and I'm quite sure no 48mp camera is present either.

What GSI File for Realme 5 Pro
what type GSI Image for Realme 5 pro, A or AB type?

Tegarcs142 said:
what type GSI Image for Realme 5 pro, A or AB type?
Click to expand...
Click to collapse
AB. On Android 9 and above you must use AB variant. It doesn't matter whether or not does your device use seamless updates. If you try to flash A only variant your device won't boot.

I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.

Tegarcs142 said:
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Nice. Which twrp did you use?

greenys' said:
Nice. Which twrp did you use?
Click to expand...
Click to collapse
3.3.1-0

Tegarcs142 said:
... So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Hi, can you please tell me what option you clicked for resizing the system partition?
the steps you did.
I tried doing that but don't find the option in TWRP.

For better experience with using gsi make sure to check Screenshot resolution if it's lower than our Device
Change Resolution :
1) download termux app
https://play.google.com/store/apps/d...?id=com.termux
2) run commands:
su
wm size 1080x2340
3) reboot*device
Enjoy better experience with gsi

greenys' said:
Original thread.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Click to expand...
Click to collapse
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls

Tarikooo said:
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Click to expand...
Click to collapse
Wth no. Idk. It's not even a gsi related thing. I have no idea sorry.

hi guys i tried flashing havoc 3.0 gsi, and it works great. which one gapps should i use?

Does fingerprint and face unlock work?

This method worked on global rm5p.

I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.

Salmankapuas said:
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Click to expand...
Click to collapse
Don't bother with miui. Only aosp or caf.

i flashed GSI rom, pixel, OxygenOS but the system cannot boot, only stuck on boot loading screen, is that normal?? how do i fix it?

[Guide] How to install custom ROM (Tested with Pixel Experience and Lineage OS)

I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!

thanks so much for this! Been flashing since andriod 1.6 but couldnt wrap my dumb head around these dual partitions.

And is the same for miui.eu ?

raphae34 said:
And is the same for miui.eu ?
Click to expand...
Click to collapse
No. Follow the instructions in the OP there. They work.

Kaissner said:
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
Click to expand...
Click to collapse
The 1st method for Pixel Experience does not work for me, after following all the steps carefully, if i boot into system it boots me to fastboot everytime, or if I dont reboot to system (in TWRP after flashing everything) it only says no OS installed are you sure you want to continue, so any help?

Snjeky said:
The 1st method for Pixel Experience does not work for me, after following all the steps carefully, if i boot into system it boots me to fastboot everytime, or if I dont reboot to system (in TWRP after flashing everything) it only says no OS installed are you sure you want to continue, so any help?
Click to expand...
Click to collapse
the "no os installed" is normal, dont worries.
The installation method for pixel experience worked when I installed the old version, it was updated multiple times so probably the process changed, I will update the thread later

This dual slot fuking my mind up.
TWRP asking for password to decrypt data. while first boot in recovery.
also *unable to decrypt FBE device* error while formating data.
"couldnt able to flash Any ROM "unable to partition path/cache" error.
ps. flashed in slot a.

When I install twrp on fastboot it stuck there, I have Android 10 stock, is anything that I can do ? I try like 3 times and always the same

ManuMan99 said:
When I install twrp on fastboot it stuck there, I have Android 10 stock, is anything that I can do ? I try like 3 times and always the same
Click to expand...
Click to collapse
downgrade to android 9. apparently android 10 got some issues.

pradie said:
downgrade to android 9. apparently android 10 got some issues.
Click to expand...
Click to collapse
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade

garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
I apologize for not being precise. i had the same issue. downloaded and flashed android 9 Stock global ROM with mi flash tool. now it's booted correctly.
---------- Post added at 12:37 PM ---------- Previous post was at 12:37 PM ----------
garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
I apologize for not being precise. i had the same issue. downloaded and flashed android 9 Stock global ROM with mi flash tool. now it booted correctly.

Sapper Morton said:
Indeed, it's not as straight forward, but it's possible without losing Widevine L1 security level; read my experience here, I explained the steps I took ; so far, I came back to v11.0.8.0 QFQMIXM from v10.3.17.0 PFQEUXM after the downgrade, with no issues whatsoever (no format/wipe data); my DRM Keys and sensors remains intact.
Click to expand...
Click to collapse
Thank you I wouldn't have guessed that would work it seems too easy to be a fix but that's good news.
Thanks for that info

garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
Then what to do? I downgraded from Android 10 Stock to Android 9 Stock 3.13.0.PFQMIXM because I soft-bricked my phone. I Flashed the stock ROM using Mi Flash tool. It flashed OK but my MI A3 sensors are not working. Someone said Flash persist.img via TWRP but when I try to flash it asked me in which partition to flash.
Partitions available are:
bluetooth
modem
System Image
Dtbo
Vendor Image
splash
Boot
Install Recovery Ramdisk
I am confused where to flash. If this method isnt suitable as you said then guide me what to do. I have Global Fastboot ROM for Android 9 Version 3.16.0.PFQMIXM for Mi A3 available. Should I flash this using Mi Flash tool? Does it solve sensor issues or not? Please help.

vjrx88 said:
Then what to do? I downgraded from Android 10 Stock to Android 9 Stock 3.13.0.PFQMIXM because I soft-bricked my phone. I Flashed the stock ROM using Mi Flash tool. It flashed OK but my MI A3 sensors are not working. Someone said Flash persist.img via TWRP but when I try to flash it asked me in which partition to flash.
Partitions available are:
bluetooth
modem
System Image
Dtbo
Vendor Image
splash
Boot
Install Recovery Ramdisk
I am confused where to flash. If this method isnt suitable as you said then guide me what to do. I have Global Fastboot ROM for Android 9 Version 3.16.0.PFQMIXM for Mi A3 available. Should I flash this using Mi Flash tool? Does it solve sensor issues or not? Please help.
Click to expand...
Click to collapse
If you are on stock android 9 now then flash an android 10 custom rom and then downgrade to android 9 like you did. Downgrading from stock 10 to stock 9 causes big issues like you are having.
If you did flash persist.IMG you would have caused stuff in your device to break forever without any way of fixing it don't do it!!

garylawwd said:
If you are on stock android 9 now then flash an android 10 custom rom and then downgrade to android 9 like you did. Downgrading from stock 10 to stock 9 causes big issues like you are having.
If you did flash persist.IMG you would have caused stuff in your device to break forever without any way of fixing it don't do it!!
Click to expand...
Click to collapse
I updated it to Stock Android 10 OTA update using TWRP Recovery and re-flashed TWRP and Magisk ZIP using TWRP and now sensors and phone is working fine. I know Android 10 for Mi A3 have some bugs but I decided to live with it until Stable Android 10 update made available by Xiaomi. Flashing Custom Android 10 ROMs have mixed reviews and have bugs so I decided to stay on Stock.
I tried flashing persist.img by mounting Persist partition using TWRP before doing this but nothing happens and sensors didn't worked. Now they are working.

garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
No problem in downgrade ,, i Already downgraded. No bugs facing!
---------- Post added at 06:34 AM ---------- Previous post was at 06:32 AM ----------
vjrx88 said:
I updated it to Stock Android 10 OTA update using TWRP Recovery and re-flashed TWRP and Magisk ZIP using TWRP and now sensors and phone is working fine. I know Android 10 for Mi A3 have some bugs but I decided to live with it until Stable Android 10 update made available by Xiaomi. Flashing Custom Android 10 ROMs have mixed reviews and have bugs so I decided to stay on Stock.
I tried flashing persist.img by mounting Persist partition using TWRP before doing this but nothing happens and sensors didn't worked. Now they are working.
Click to expand...
Click to collapse
Lol i came back to 9 ,, untill stable comes or i will use pixel rom ?

Kaissner said:
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
Click to expand...
Click to collapse
EDIT: Solved it by flashing this inofficial TWRP: https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
I have a problem. I am stuck on fastboot. I followed the tutorial unto step 4:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp.img
target reported max download size of 803475456 bytes
sending 'boot_a' (39892 KB)...
OKAY [ 0.910s]
writing 'boot_a'...
OKAY [ 0.197s]
finished. total time: 1.111s
But after this the phone always reboots to fastboot, I can't boot into TWRP or the system. Plz help.

spring_roll said:
EDIT: Solved it by flashing this inofficial TWRP: https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
I have a problem. I am stuck on fastboot. I followed the tutorial unto step 4:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp.img
target reported max download size of 803475456 bytes
sending 'boot_a' (39892 KB)...
OKAY [ 0.910s]
writing 'boot_a'...
OKAY [ 0.197s]
finished. total time: 1.111s
But after this the phone always reboots to fastboot, I can't boot into TWRP or the system. Plz help.
Click to expand...
Click to collapse
I know you solved it but the reason the other twrp wasn't working for you is because it is built only for Android pie and I'm assuming you have Android 10. That's why you always booted to fastboot. The installer.zip will work with any Android version but the twrp.img files are built using kernels of a specific Android version

garylawwd said:
I know you solved it but the reason the other twrp wasn't working for you is because it is built only for Android pie and I'm assuming you have Android 10. That's why you always booted to fastboot. The installer.zip will work with any Android version but the twrp.img files are built using kernels of a specific Android version
Click to expand...
Click to collapse
Ok thx for the info.
Another question. I didn't understand step 5:
"5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay)"
Where do I have to move and flash the ZIP? I just skipped this step and now I have the ROM installed which I wanted (PE Plus).
Do I have to do something now or is TWRP installed properly now? Can I fetch this step later?

spring_roll said:
Ok thx for the info.
Another question. I didn't understand step 5:
"5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay)"
Where do I have to move and flash the ZIP? I just skipped this step and now I have the ROM installed which I wanted (PE Plus).
Do I have to do something now or is TWRP installed properly now? Can I fetch this step later?
Click to expand...
Click to collapse
For you I don't think twrp is installed now. Some ROMs have twrp built in but if not then you have to manually flash twrp every time you flash a ROM or it gets overwritten with stock recovery.
When you flash the twrp.img and boot twrp it isn't actually installed, you are running it in ram and when you reboot it goes out of ram and your left with an un-bootable slot due to your boot slot being messed up from flashing the twrp.img and twrp won't stay installed.
For it to be installed properly you need to flash twrp.zip which will patch your boot.img with twrp and install it.
But as I said everytime you flash a ROM this will overwrite twrp and it will be gone unless the twrp.zip is flashed in twrp before rebooting.
Not as easy as it used to be by just installing twrp once and it is there forever. The new era of Android

Planning to flash custom rom on Redmi Note 8T, have I got the steps right?

Hello, I am poised to start customising my Redmi Note 8T. I've done loads of reading and have an outline plan but would appreciate a sanity check / review of this in case I am either missing something or doing something I shouldnt. Phone is currently encrypted, TWRP can unlock it fine. I want to end up with an encrypted device but there is nothing precious on the phone at the moment (stock MIUI as delivered, pretty much unused since the unlock factory reset).
Here's what I have following my research on other threads here:
First, what I have done already:
0. get phone Redmi 8T willow 128GB with stock MIUI (DONE)
1. unlock phone (DONE, 7 day wait!)
2. flash TWRP (DONE, used 3.3.1-1 official version, but MIUI overwrote it when I rebooted)
3. Backup from TWRP (DONE)
Next, the to-do list:
4. flash vbmeta (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
5. flash TWRP 3.3.1-10 version (fastboot flash recovery twrp-3.3.1-10-ginkgo-willow-mauronofrio.img)
6. reboot into TWRP (fastboot reboot, hold volume up + power)
7. Wipe /system, /data, and /cache
8. flash Havoc-OS-v3.2-20200229-willow-Official.zip
9. flash open_gapps-arm64-10.0-pico-20200229.zip
10. reboot & test
11. reboot into TWRP (fastboot reboot, hold volume up + power)
12. flash magisk zip (Magisk-v20.3.zip)
13. flash disable_dm_verity zip (Disable_Dm-Verity_ForceEncrypt_02.24.2020.zip)
14. reboot & test
15. Install via magisk manager the SQLite3 binary (SQLite3.Universal.Binaries.v1.0.zip)
16. Reboot
17. Install vis magisk manager the GPay SQLite fix (GPay.SQLite.Fix.v2.0.zip)
18. Reboot
Thanks very much in advance.

Hey @ogpog, at step 4, where you find vbmeta to flash?
Thanks

ogpog said:
Hello, I am poised to start customising my Redmi Note 8T. I've done loads of reading and have an outline plan but would appreciate a sanity check / review of this in case I am either missing something or doing something I shouldnt. Phone is currently encrypted, TWRP can unlock it fine. I want to end up with an encrypted device but there is nothing precious on the phone at the moment (stock MIUI as delivered, pretty much unused since the unlock factory reset).
Here's what I have following my research on other threads here:
First, what I have done already:
0. get phone Redmi 8T willow 128GB with stock MIUI (DONE)
1. unlock phone (DONE, 7 day wait!)
2. flash TWRP (DONE, used 3.3.1-1 official version, but MIUI overwrote it when I rebooted)
3. Backup from TWRP (DONE)
Next, the to-do list:
4. flash vbmeta (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
5. flash TWRP 3.3.1-10 version (fastboot flash recovery twrp-3.3.1-10-ginkgo-willow-mauronofrio.img)
6. reboot into TWRP (fastboot reboot, hold volume up + power)
7. Wipe /system, /data, and /cache
8. flash Havoc-OS-v3.2-20200229-willow-Official.zip
9. flash open_gapps-arm64-10.0-pico-20200229.zip
10. reboot & test
11. reboot into TWRP (fastboot reboot, hold volume up + power)
12. flash magisk zip (Magisk-v20.3.zip)
13. flash disable_dm_verity zip (Disable_Dm-Verity_ForceEncrypt_02.24.2020.zip)
14. reboot & test
15. Install via magisk manager the SQLite3 binary (SQLite3.Universal.Binaries.v1.0.zip)
16. Reboot
17. Install vis magisk manager the GPay SQLite fix (GPay.SQLite.Fix.v2.0.zip)
18. Reboot
Thanks very much in advance.
Click to expand...
Click to collapse
flashing vbmeta is not really needed..however keep it just in case.
iaio72 said:
Hey @ogpog, at step 4, where you find vbmeta to flash?
Thanks
Click to expand...
Click to collapse
in fastboot rom inside images folder

ok solved thanks

the_weird_aquarian said:
flashing vbmeta is not really needed..however keep it just in case.
Click to expand...
Click to collapse
Well I tried without vbmeta and ended up with the panic-inducing "The system is destroyed" screen. I went back to fastboot and flashed vbmeta and twrp again, then installed the cutom rom, set it all up, then went back and installed magisk.
in fastboot rom inside images folder
Click to expand...
Click to collapse
I got vbmeta from reading https://forum.xda-developers.com/showpost.php?p=81591273&postcount=196 and downloaded from https://t.me/rn8updates/80

The same thing happened to me and I'm still not clear on the steps to follow to fix it and be able to install a custom rom. Destroyed system appears

ogpog said:
Well I tried without vbmeta and ended up with the panic-inducing "The system is destroyed" screen. I went back to fastboot and flashed vbmeta and twrp again, then installed the cutom rom, set it all up, then went back and installed magisk.
I got vbmeta from reading https://forum.xda-developers.com/showpost.php?p=81591273&postcount=196 and downloaded from https://t.me/rn8updates/80
Click to expand...
Click to collapse
The same thing happened to me and I'm still not clear on the steps to follow to fix it and be able to install a custom rom. Destroyed system appears.
You did well with the steps outlined above??

nothing is clear, not really..to many gray areas..like can i backup rom to external sd card, why exactly in twrp do you backup rom wise, and Disable_Dm-Verity_ForceEncrypt_, iv read its two files in one, new roms are not like the old days ie marshmallow kitkat, i used all in one tool flashed twrp..all went well then flashed then flashed magisk and then the dm-verty thing, ended up in a bootloop, then tried to use mi flash tool to put original firmware back, error error, got back using twrp and using eea recovery rom, although i was on on global, remember fast boot rom is not the same as recovery rom, same rom though, all very confusing...for me anyway.

Juanlufer4 said:
The same thing happened to me and I'm still not clear on the steps to follow to fix it and be able to install a custom rom. Destroyed system appears.
You did well with the steps outlined above??
Click to expand...
Click to collapse
Just looking back over my notes from when I did it. Here is what I wrote:
A modified vbmeta.img disables verify boot on devices using Android Verified Boot. You need to disable dm-verity on the fastboot command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
source https://forum.xda-developers.com/showpost.php?p=81591273&postcount=196
(the above is a command-line given on your computer connected to your phone which has been booted in fastboot mode (boot phone with power+volume down). You need the fastboot command on your computer (I use Linux and it's in a package called "android-tools").
If you forget to flash vbmeta, you'll see a message "the system hass been destroyed". Just go back to fastboot mode and flash it.
This is the process I recorded, but please verify it rather than folllwing it blindly, and bear in mind that later versions are available now .
Code:
0. get phone Redmi 8T with stock MIUI
1. unlock phone (DONE, 7 day wait!)
2. flash TWRP (DONE, used 3.3.1-1 official version, but MIUI overwrote it)
3. Backup (DONE)
4. flash vbmeta (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
5. flash TWRP 3.3.1-10 version (fastboot flash recovery twrp-3.3.1-10-ginkgo-willow-mauronofrio.img)
6. reboot into TWRP (fastboot reboot, hold volume up + power)
7. Wipe /system, /data, and /cache
8. flash Havoc-OS-v3.2-20200229-willow-Official.zip
9. flash open_gapps-arm64-10.0-pico-20200229.zip
10. reboot & test
bluefender said:
nothing is clear, not really..to many gray areas..like can i backup rom to external sd card, why exactly in twrp do you backup rom wise, and Disable_Dm-Verity_ForceEncrypt_, iv read its two files in one, new roms are not like the old days ie marshmallow kitkat, i used all in one tool flashed twrp..all went well then flashed then flashed magisk and then the dm-verty thing, ended up in a bootloop, then tried to use mi flash tool to put original firmware back, error error, got back using twrp and using eea recovery rom, although i was on on global, remember fast boot rom is not the same as recovery rom, same rom though, all very confusing...for me anyway.
Click to expand...
Click to collapse
I get your sentiment - it's feels hard doing this on any Android despite having decades of expert level professional computer experience. But it's really a miracle we can do it at all and we have the good people providing roms and the information needed to install them to thank for that. I think the "brick fear" makes it worse due to the lack of a console port or bios to fall back to like you have on a computer. I think the first post in the thread should contain all the information needed to install the rom but it's a moving target so I guess it's a difficult call to expect it to be maintained.
If I were to call out for one thing, it would be for that page to also include instructions for Linux. Android is Linux after all
(sorry I just realised I wasn't on the havoc thread where the "first page" is - https://forum.xda-developers.com/redmi-note-8/development/rom-havocos-3-1-t4043973 )

Thanks for your interest, I just wanted to know if the steps you describe were correct. I had 2 systems destroyed and it's not funny. Hopefully it works
---------- Post added at 03:56 PM ---------- Previous post was at 03:47 PM ----------
the_weird_aquarian said:
flashing vbmeta is not really needed..however keep it just in case.
in fastboot rom inside images folder
Click to expand...
Click to collapse
A doubt? started the rom well or encrypted?

Is there any YouTube videos showing the steps for the Redmi Note 8T ?

How to install rom gsi for Redmi note 8t

chakkrit_pond said:
How to install rom gsi for Redmi note 8t
Click to expand...
Click to collapse
+1 I'm trying to test GSIs on Note 8 (ginkgo) and I'm not succeeding in any way. Phone stuck on bootanimation (or, sometimes, reboot into TWRP).
Does anyone have the steps to success? Thanks.
I can start from scratch (MIUI 11).
Trying to flash a/b gsis of Android 10.

[GUIDE]Installing a Lineage 17.1 ROM in Redmi Note 9 (merlin)

Hi everyone!
I've been testing installing Lineage 17.1 custom ROMs on merlin, here are the steps I followed plus a LOS 17.1.
I found out that this ROM works better than MIUI and its very stable as a daily driver.
Tested on Redmi Note 9 Global (merlin) - CPU (Helio G85) - ROM/RAM: 64GB/3GB, initialy flashed over MIUI 12.0.3 Global
This are the steps I followed:
Unlock bootloader (of course)
Backup all sensitive data (it maybe lost if things go wrong)
For you in case things go wrong, also download the exact fastboot rom of the MIUI version you are using from xiaomifirmwareupdater.com (it has to be fastboot ROM becouse it contains stock recovery)
Flash a TWRP with new MIUI kernel support
Download TWRP build by wzsx15, for example
Download a modifed vbmeta.img, like the one provided in this thread
Flash like this:
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
Test TWRP, at least verify it can mount and read /data.
Wipe data, cache and dalvik
Flash LOS 17.1 for merlin (details below), or anything you want to test
Details about provided LOS 17.1:
LineageOS 17.1 - UNOFFICIAL | A10.
Released : 11/02/'21
By @CosmoFreak001 & @chcepizze
SElinux permissive
Changelog:
• Fixed VoLTE
• Fixed Brightness bug
• Fixed all major bugs
• Fixed Double tap to wake
• Fixed Offline Charging
Download
Source (build using generic kernel for Mediatek Helio G85)
Works at least over:
MIUI 12.0.4 Global and less
MIUI 12.0.1 Indonesia and less
--------------
⚠WARNING⚠
MIUI 12.0.5 Global (and 12.0.2 Indonesia) and any higher version, would probably need a downgrade.
--------------
In case things go wrong:
TWRP dosen't work correctly and now my system can't boot
Restore stock recovery, vbmeta and boot partition
Go to fastboot
Extract recovery.img file from your stock fastboot ROM and flash it like this
Code:
fastboot flash recovery recovery.img
Reboot, if system dosen't boot, go to next step
Extract vbmeta.img file from stock fastboot ROM and flash it like this
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Reboot, if it can't boot, go to next step
Extract boot.img file from your stock fastboot ROM and flash all (recovery, vbmeta and boot partition) it like this
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
TWRP ask's me for a passoword
It's the first PIN number of the lockscreen you set when you first run the system
My PIN doesn't work or my phone never had a PIN and still asks me for one
Maybe /data is not accesible (TWRP compatibility problem)
Try mounting /system and /vendor partition
Navigate through them and verify you can see files and folder
If TWRP is unable to mount any partition restore stock recovery partition
If TWRP can see and mount partitions other than /data:
You can format /data (you are losing ALL data including internal storage)
I don't wont to lose all my data!
Restore stock recovery

Good work, Please note that the rom does not boot on every vendor version, So include the list of the vendors working for rom, As far as I know, it has booted successfully on MIUI 12.0.3 Global and 12.0.1 Indonesia.

Communos said:
Good work, Please note that the rom does not boot on every vendor version, So include the list of the vendors working for rom, As far as I know, it has booted successfully on MIUI 12.0.3 Global and 12.0.1 Indonesia.
Click to expand...
Click to collapse
Thanks. You are right I will add those comments.

thanks for this

Hello members after a long daunting minutes ,hours and days asking for the procedures in this forum on how i can install the custom rom on the Redmi note 9 Merlin MT 6768 3GB Ram ,64GB Rom Global version MiUI 12.0.3.0 i have managed to to install the 17.1 lineage through some experiences, First thanks to the two members who have been of help namely SparXFusion and Ma269 after i have read their post on this forum. Here is what i did i was on MIUI v11.0.4.0 which i later updated to 12.0.3.0 for this to work . Below is the procedure which i have been following and i discovered that the TWRP files i downloaded works fine from v 11.0.4 to 12.0.4.0 PROCEDURE
1- Download the TWRP file from this site : https://mega.nz/file/SuZn2QqZ#jJ6xRku...
2- Download the ADB file from this site : https://androidmtk.com/download-minim..
3- Below command prompts
fastboot devices
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash misc misc.bin
fastboot boot recovery.img
Once boot in TWRP open Wipe/format then type yes. Then go to install to get the 17.1 lineage custom rom from internal or external storage if it was downloaded there . Then fine you are good to go
All in all i have noticed that to set the email its not working may the experts explain my observation.
Waiting to hear from some members the solution
One other question is where to get the Gapps for this rom 17.1 lineage merlin mt 6768

gruka said:
Hello members after a long daunting minutes ,hours and days asking for the procedures in this forum on how i can install the custom rom on the Redmi note 9 Merlin MT 6768 3GB Ram ,64GB Rom Global version MiUI 12.0.3.0 i have managed to to install the 17.1 lineage through some experiences, First thanks to the two members who have been of help namely SparXFusion and Ma269 after i have read their post on this forum. Here is what i did i was on MIUI v11.0.4.0 which i later updated to 12.0.3.0 for this to work . Below is the procedure which i have been following and i discovered that the TWRP files i downloaded works fine from v 11.0.4 to 12.0.4.0 PROCEDURE
1- Download the TWRP file from this site : https://mega.nz/file/SuZn2QqZ#jJ6xRku...
2- Download the ADB file from this site : https://androidmtk.com/download-minim..
3- Below command prompts
fastboot devices
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash misc misc.bin
fastboot boot recovery.img
Once boot in TWRP open Wipe/format then type yes. Then go to install to get the 17.1 lineage custom rom from internal or external storage if it was downloaded there . Then fine you are good to go
All in all i have noticed that to set the email its not working may the experts explain my observation.
Waiting to hear from some memmbers the solution
Click to expand...
Click to collapse
Misc.bin isn't necessary for flashing twrp,
And what do you mean by "that to set the email it's not working"?

when you put your email on the email app you never log in , and one other question is which is the best gapps for this rom 17,1 lineage merlin

gruka said:
when you put your email on the email app you never log in , and one other question is which is the best gapps for this rom 17,1 lineage merlin
Click to expand...
Click to collapse
Pico Open Gappa or flame Gapps basic, both are fine.
And it's the stock email app, I never used it, so I don't know about that.

Question GSI wont boot after rooting phone - Xiaomi Redmi Note 8 (2021)

Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.

I have found that resizing GSI system partition could help flash gapps via Ex Kernel Manager directly from the phone.
My big question is if you can resize GSI system partition without TWRP? since Note 2021 does not support recovery, if yes how?
Or can you actually set bigger system partition than system image with this command ? --el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
(following manual steps for gsi installation)
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
what would be number for 20GB size in this command? --el KEY_USERDATA_SIZE 8589934592 how i can write it correctly?
i have enough space to assign big userdata partition.

CyraxMD said:
Is there any fix for this problem? I wish to have phone rooted AND use GSI
Click to expand...
Click to collapse
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..

vegan_monk said:
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..
Click to expand...
Click to collapse
was not neccessary, check this guide which i maked how to do it:

CyraxMD said:
was not neccessary, check this guide which i maked how to do it:
Click to expand...
Click to collapse
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.

vegan_monk said:
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.
Click to expand...
Click to collapse
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.

CyraxMD said:
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.
Click to expand...
Click to collapse
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8

vegan_monk said:
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8
Click to expand...
Click to collapse
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too

CyraxMD said:
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too
Click to expand...
Click to collapse
sorry to disappoint u mate but its just the miui recovery

GSI has better performance than MIUI? Could you tell the pros and cons that you have found?

CyraxMD said:
Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.
Click to expand...
Click to collapse
After seeing your video I understand that you was able to fix your initial problem:
"The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted."
It seem that you have been able to fix that problem, havent you? Have you had any problem using rooted GSI lineage? I am very insterested in rooting my phone using a GSI rom. I am going to follow your tutorial.
thanks