Develop Bugs

Alcatel 1x DEVELOPMENT: Kernel, TWRP, Pie ROMs, Guides

ALCATEL 1X Development Thread
TWRP and Kernel work is mine and is free for everyone to use, but I appreciate being credited.
System GSIs are created by Phhusson.
Guide for flashing with SP Flash Tool is mine, but the code and binaries are proprietary information from TCL/JRD Communication and may not be redistributed.
KERNEL - Based on latest Alcatel GPL source code that they released, compiled and packaged into a boot.img - bit . ly / 2Gc4XUN
TWRP - Custom built from source TWRP from my device tree. Most things work, no special partition support other than /vendor - bit . ly / 2EevCO7
TWRP device tree - Github: milankragujevic/android_device_alcatel_5059d (I can't post a link due to XDA restrictions for new users)
Stock rom for 5059D_RU - bit . ly / 2ruktBa (remove spaces, can't share link directly)
How to unlock bootloader?
Reboot into recovery (either hold Volume Up when booting, or adb reboot-recovery), go into bootloader mode (fastboot), and run fastboot oem unlock. Then confirm with the volume button and reboot the device. Please note, all data will be wiped.
How to flash kernel?
Reboot into bootloader and run fastboot flash boot boot.img and fastboot flash boot2 boot.img (you need to flash boot2 too, or else the phone will refuse to boot due to integrity and signature problem).
How to flash system or recovery
Reboot into fastboot and run fastboot flash [partition] file.img. For system, partition is "system", for recovery it's "recovery" (obviously).
How to flash with SP Flash Tool?
Flashing is similar to most other phones, except you need a special version of SP Flash Tool, and a custom DA, preloader, Auth file and of course the scatter file for this device (MT6739-based).
Download files from here: bit . ly / 2L7gwLX
In SP Flash Tool, select "DA_PL_U5A_PLUS_4G.bin" as DA, "MT6739_Android_scatter.txt" as Scatter and "JRD_6739_HZ_U5A_PLUS_4G.auth" as Auth file. If it doesn't work with that file, try "JRD_6739_A30ATMO.auth" as Auth.
Add some files, i.e. boot.img, recovery.img, system.img, vendor.img in the same folder as the scatter file.
Then, take apart the phone, disconnect the battery, click the start button in the software and plug the phone into the computer.
Treble GSI flashing
Most GSIs work, provided you download an arm A-only image.
Both Oreo and Pie work, but on Oreo there's a problem with sending and receiving SMS, calls and USSD codes, and mobile data.
On Pie, mobile data works intermittently, and SMS, calls and USSD works constantly.
LineageOS non-GSI
I'm working on building a LineageOS image specific for this device, which should fix all issues with MTK RIL.
WIP, comments and suggestions welcome. Standard disclaimers apply (NO WARRANTY PROVIDED, AT YOUR OWN RISK, etc. )

Downloading, will post results!!! Thanks!

milankragujevic said:
ALCATEL 1X Development Thread
TWRP and Kernel work is mine and is free for everyone to use, but I appreciate being credited.
System GSIs are created by Phhusson.
Guide for flashing with SP Flash Tool is mine, but the code and binaries are proprietary information from TCL/JRD Communication and may not be redistributed.
KERNEL - Based on latest Alcatel GPL source code that they released, compiled and packaged into a boot.img - bit . ly / 2Gc4XUN
TWRP - Custom built from source TWRP from my device tree. Most things work, no special partition support other than /vendor - bit . ly / 2EevCO7
TWRP device tree - Github: milankragujevic/android_device_alcatel_5059d (I can't post a link due to XDA restrictions for new users)
Stock rom for 5059D_RU - bit . ly / 2ruktBa (remove spaces, can't share link directly)
How to unlock bootloader?
Reboot into recovery (either hold Volume Up when booting, or adb reboot-recovery), go into bootloader mode (fastboot), and run fastboot oem unlock. Then confirm with the volume button and reboot the device. Please note, all data will be wiped.
How to flash kernel?
Reboot into bootloader and run fastboot flash boot boot.img and fastboot flash boot2 boot.img (you need to flash boot2 too, or else the phone will refuse to boot due to integrity and signature problem).
How to flash system or recovery
Reboot into fastboot and run fastboot flash [partition] file.img. For system, partition is "system", for recovery it's "recovery" (obviously).
How to flash with SP Flash Tool?
Flashing is similar to most other phones, except you need a special version of SP Flash Tool, and a custom DA, preloader, Auth file and of course the scatter file for this device (MT6739-based).
Download files from here: bit . ly / 2L7gwLX
In SP Flash Tool, select "DA_PL_U5A_PLUS_4G.bin" as DA, "MT6739_Android_scatter.txt" as Scatter and "JRD_6739_HZ_U5A_PLUS_4G.auth" as Auth file. If it doesn't work with that file, try "JRD_6739_A30ATMO.auth" as Auth.
Add some files, i.e. boot.img, recovery.img, system.img, vendor.img in the same folder as the scatter file.
Then, take apart the phone, disconnect the battery, click the start button in the software and plug the phone into the computer.
Treble GSI flashing
Most GSIs work, provided you download an arm A-only image.
Both Oreo and Pie work, but on Oreo there's a problem with sending and receiving SMS, calls and USSD codes, and mobile data.
On Pie, mobile data works intermittently, and SMS, calls and USSD works constantly.
LineageOS non-GSI
I'm working on building a LineageOS image specific for this device, which should fix all issues with MTK RIL.
WIP, comments and suggestions welcome. Standard disclaimers apply (NO WARRANTY PROVIDED, AT YOUR OWN RISK, etc. )
Click to expand...
Click to collapse
Not working twrp not working touch screen
I have twrp all work i Russia

milankragujevic said:
ALCATEL 1X Development Thread
TWRP and Kernel work is mine and is free for everyone to use, but I appreciate being credited.
System GSIs are created by Phhusson.
Guide for flashing with SP Flash Tool is mine, but the code and binaries are proprietary information from TCL/JRD Communication and may not be redistributed.
KERNEL - Based on latest Alcatel GPL source code that they released, compiled and packaged into a boot.img - bit . ly / 2Gc4XUN
TWRP - Custom built from source TWRP from my device tree. Most things work, no special partition support other than /vendor - bit . ly / 2EevCO7
TWRP device tree - Github: milankragujevic/android_device_alcatel_5059d (I can't post a link due to XDA restrictions for new users)
Stock rom for 5059D_RU - bit . ly / 2ruktBa (remove spaces, can't share link directly)
How to unlock bootloader?
Reboot into recovery (either hold Volume Up when booting, or adb reboot-recovery), go into bootloader mode (fastboot), and run fastboot oem unlock. Then confirm with the volume button and reboot the device. Please note, all data will be wiped.
How to flash kernel?
Reboot into bootloader and run fastboot flash boot boot.img and fastboot flash boot2 boot.img (you need to flash boot2 too, or else the phone will refuse to boot due to integrity and signature problem).
How to flash system or recovery
Reboot into fastboot and run fastboot flash [partition] file.img. For system, partition is "system", for recovery it's "recovery" (obviously).
How to flash with SP Flash Tool?
Flashing is similar to most other phones, except you need a special version of SP Flash Tool, and a custom DA, preloader, Auth file and of course the scatter file for this device (MT6739-based).
Download files from here: bit . ly / 2L7gwLX
In SP Flash Tool, select "DA_PL_U5A_PLUS_4G.bin" as DA, "MT6739_Android_scatter.txt" as Scatter and "JRD_6739_HZ_U5A_PLUS_4G.auth" as Auth file. If it doesn't work with that file, try "JRD_6739_A30ATMO.auth" as Auth.
Add some files, i.e. boot.img, recovery.img, system.img, vendor.img in the same folder as the scatter file.
Then, take apart the phone, disconnect the battery, click the start button in the software and plug the phone into the computer.
Treble GSI flashing
Most GSIs work, provided you download an arm A-only image.
Both Oreo and Pie work, but on Oreo there's a problem with sending and receiving SMS, calls and USSD codes, and mobile data.
On Pie, mobile data works intermittently, and SMS, calls and USSD works constantly.
LineageOS non-GSI
I'm working on building a LineageOS image specific for this device, which should fix all issues with MTK RIL.
WIP, comments and suggestions welcome. Standard disclaimers apply (NO WARRANTY PROVIDED, AT YOUR OWN RISK, etc. )
Click to expand...
Click to collapse
Could it work with alacatel 1 (5033a)? It has the same chipset but differs in other characteristics.

Hey, are you still building a Lineage OS?

Los link estan caidos. Instale el twrp pero queda en bootloop twrp. Saque el boot.img con el twrp para parchearlo con magisk pero al flashearlo con cmd vuelve a quedarse en el twrp. Podrias pasar el boot.img stock? Gracias

Flash recovery

AUTH files doesn't work with A variant (5059A).

January 2020 and the link is gone. (I can host it if you like. Message me.)

The files are back up. Sorry about the inconvenience.

NP. Thanks.

Update links PLS
Hello? Does anyone have the DA and Auth files? The links are broken and I cant find online, help pls my phone is hard bricked. Thanks.

T3ll3S said:
Hello? Does anyone have the DA and Auth files? The links are broken and I cant find online, help pls my phone is hard bricked. Thanks.
Click to expand...
Click to collapse
Links are back, the server had failed and I moved the files to another datacenter which took 3 days.
Here's a MEGA link just in case, if this happens again: https://mega.nz/file/i3BhASJJ#pNzwAsflvcvdfr3pGzUfbNhe3fHUCnfyoAR_O4IsFAE

Hi again, does anyone of you know how to fix this error, im very scared that my phone wont show any screen again.
This is what happened: I tried to install Android 10 GSI and bootlooped so I went to TWRP and used my backup but from no reason the phone died during the backup and when I powered it on it vibrates but it doesnt show any image at all and takes a bit longer to vibrate.
The error on SP Flash Tool is STATUS_BROM_CMD_FAIL (0xC0060005). What do I do? When I try to flash it turns the LED on but then it turns off and turns on again but gives this error. If also there is a way to boot to bootloader directly tell me PLSS. Its Hard Bricked.

T3ll3S said:
Hi again, does anyone of you know how to fix this error, im very scared that my phone wont show any screen again.
This is what happened: I tried to install Android 10 GSI and bootlooped so I went to TWRP and used my backup but from no reason the phone died during the backup and when I powered it on it vibrates but it doesnt show any image at all and takes a bit longer to vibrate.
The error on SP Flash Tool is STATUS_BROM_CMD_FAIL (0xC0060005). What do I do? When I try to flash it turns the LED on but then it turns off and turns on again but gives this error. If also there is a way to boot to bootloader directly tell me PLSS. Its Hard Bricked.
Click to expand...
Click to collapse
You did not flash correctly. The device isn't hard bricked, you have to turn it off (take it apart and disconnect the battery then reconnect it but don't turn on, keep the back cover off because you will surely need to repeat this many times), go to Options, Download and enable "Storage checksum" and "USB checksum", and then start flashing and then plug in the phone while SPFT is trying to flash. When SPFT starts flashing do not touch it, when it flashes the phone will reboot. You also need a proper stock ROM.
You can also just literally use the Mobile Upgrade S Gotu2 tool from Alcatel: https://mega.nz/file/DjpzTRDB#vC3SrO5hQr1Nzn32lWxVGLhmclfSpPF6CsIWHRaTsP8 and restore the stock ROM that way.

I cant with SP Flash Tool It gives the same error and with the other softwate it tels that i am at the latest version

T3ll3S said:
I cant with SP Flash Tool It gives the same error and with the other softwate it tels that i am at the latest version
Click to expand...
Click to collapse
You can, you are just doing it wrong. Check the checksum options I mentioned and retry.

Do i need to touch in any button before i flash? The other software why it tells that im on the newest version? What is the error about? I cant boot onto nothing it doesnt even show a screen but i will try harder

T3ll3S said:
Do i need to touch in any button before i flash? The other software why it tells that im on the newest version? What is the error about? I cant boot onto nothing it doesnt even show a screen but i will try harder
Click to expand...
Click to collapse
Yes, I clearly told you:
In SP Flash Tool: Go to Options, Download and enable "Storage checksum" and "USB checksum".
THEN flash.

I enabled but still no results. The button i was talking about is on the phone do i need to touch the phone or just put the usb?

[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.

How To Guide Root achieved! Here's how to root the Red Magic 6 and Red Magic 6 Pro

I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up!
Join our Discord Channel
Join the Red Magic 6 & 6 Pro [XDA Developers Forums] Discord Server!
Check out the Red Magic 6 & 6 Pro [XDA Developers Forums] community on Discord - hang out with 1 other members and enjoy free voice and text chat.
discord.gg
Youtube Video Tutorial:
UPDATED VIDEO:
For all those websites that claim the RM6 can be rooted with Kingroot, Kingoroot, iRoot, SuperSU... They are MISLEADING you into downloading their software. In other words, they are full of BS and you should INGORE them at all costs as Magisk is the ONLY proper way to root the RM6.
DO NOT USE KINGROOT, iROOT, KingoROOT, or ANY OTHER THIRD-PARTY ROOTING TOOLS PLEASE!! They steal your DATA and sell it. Magisk does not steal anything.​
This procedure will require a wipe of your data.. TWICE! I'll explain why.
When you unlock the bootloader, it wipes your data. Normally you only have to wipe it once, flash the patched boot.img file with magisk, and be done.
However, it seems that users will need to perform another factory reset after flashing the patched boot image. I have no idea why but it works. Please make a note of this as it will be required or you will be stuck in a bootloop.
Requirments
1. Global ROM file
2. A payload dumper
3. Magisk APK to patch the boot img
4. A computer!
Here are the steps!
​1. Unlock your bootloader. Make sure you enable OEM unlock in developer options. This WILL WIPE YOUR DEVICE! The command to unlock your bootloader is "fastboot flashing unlock"
2. Download the global rom from here: https://rom.download.nubia.com/Europe/NX669J/V312/NX669J-update.zip
3. You will need to download a payload dumper tool. This is due to the firmware being in a .bin file (payload.bin). Follow the link below on how to extract the global firmware:
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
I ended up Downloading Termux from the playstore and extracting it with python on my phone.
When you get it extracted, just move the boot.img and vbmeta.img files to your Desktop and on your phone Place it somewhere on your internal storage where you will remember!
4. Download Magisk Manager onto your phone and install it. Select install "patch a file" option and select the boot.img you put on your phone.
Let magisk patch it. It will end outputting a file like "Magisk_Patchedxxx.img" Go ahead and copy that file to your Desktop.
5. Go onto your computer and open up command prompt. Change your directory to the Desktop ex. cd c:/Users/Your Name/Desktop
6. Type fastboot flash boot magisk_patched.img
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. From the bootloader, reboot into your recovery and perform another factory reset!
9. Reboot the phone and voila! You now have root access!
Another thing to mention is that SafteyNet does NOT pass even with MagiskHide enabled. Please keep that in mind!
So far I've installed the Xposed Framework and some Magisk modules. All seems to work really well.
Happy Modding!
​

Do u have rom V3:10

chocolote4444 said:
I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up!
This procedure will require a wipe of your data.. TWICE! I'll explain why.
When you unlock the bootloader, it wipes your data. Normally you only have to wipe it once, flash the patched boot.img file with magisk, and be done.
However, it seems that users will need to perform another factory reset after flashing the patched boot image. I have no idea why but it works. Please make a note of this as it will be required or you will be stuck in a bootloop.
Requirments
1. Global ROM file
2. A payload dumper
3. Magisk APK to patch the boot img
4. A computer!
Here are the steps!
​1. Unlock your bootloader. Make sure you enable OEM unlock in developer options. This WILL WIPE YOUR DEVICE! The command to unlock your bootloader is "fastboot flashing unlock"
2. Download the global rom from here: https://rom.download.nubia.com/Europe/NX669J/V312/NX669J-update.zip
3. You will need to download a payload dumper tool. This is due to the firmware being in a .bin file (payload.bin). Follow the link below on how to extract the global firmware:
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
I ended up Downloading Termux from the playstore and extracting it with python on my phone.
When you get it extracted, just move the boot.img and vbmeta.img files to your Desktop and on your phone Place it somewhere on your internal storage where you will remember!
4. Download Magisk Manager onto your phone and install it. Select install "patch a file" option and select the boot.img you put on your phone.
Let magisk patch it. It will end outputting a file like "Magisk_Patchedxxx.img" Go ahead and copy that file to your Desktop.
5. Go onto your computer and open up command prompt. Change your directory to the Desktop ex. cd c:/Users/Your Name/Desktop
6. Type fastboot flash boot magisk_patched.img
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification vbmeta vbmeta.img
8. From the bootloader, reboot into your recovery and perform another factory reset!
9. Reboot the phone and voila! You now have root access!
Another thing to mention is that SafteyNet does NOT pass even with MagiskHide enabled. Please keep that in mind!
Edit:
Xposed Framework DOES work!
​
Click to expand...
Click to collapse
would be the same process for version V4.12?

Masacr3 said:
would be the same process for version V4.12?
Click to expand...
Click to collapse
Yes. Mine is showing up as still 4.12

Are you SURE it doesn't pass SafetyNet? The Magisk check is broken download SafetyNet Checker from the app store and see what it says...

mslezak said:
Are you SURE it doesn't pass SafetyNet? The Magisk check is broken download SafetyNet Checker from the app store and see what it says...
Click to expand...
Click to collapse
I does not pass safety net. I've tested every testing app on the Play Store. I'll keep looking for a solution though.

chocolote4444 said:
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
You're missing the "flash" command inside, as such:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
A couple of questions:
1: does the phone retain full functionality? radio (BT/A2DP/different wifi bands/fingerprint scanner/camera)?
2: have you tried using an empty vbmeta?

adwinp said:
You're missing the "flash" command inside, as such:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
A couple of questions:
1: does the phone retain full functionality? radio (BT/A2DP/different wifi bands/fingerprint scanner/camera)?
2: have you tried using an empty vbmeta?
Click to expand...
Click to collapse
Everything still works except the fingerprint. When the bootloader is unlocked, the fingerprint stops working.
As for flashing empty vbmeta images, I have not tried it. I know some devices you may have to flash an empty vbmeta img at last resort but I was able to boot it up using the stock vbmeta.

chocolote4444 said:
Everything still works except the fingerprint. When the bootloader is unlocked, the fingerprint stops working.
As for flashing empty vbmeta images, I have not tried it. I know some devices you may have to flash an empty vbmeta img at last resort but I was able to boot it up using the stock vbmeta.
Click to expand...
Click to collapse
Thx for responding.
1: Would you be able to test/comfirm if the fingerprint scanner is restored when relocking the bootloader using either the rooted boot.img or the stock one?
2: The same issue with fp calibration is faced by RM 5S/G users; can you check if the calibration fix in these forums works also for the RM6?
3: Lastly, have you tried flashing the latest phh GSI to see if it's working?

Yes usually you just flash stock vbmeta.img via fastboot: fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification should try it out...

adwinp said:
Thx for responding.
1: Would you be able to test/comfirm if the fingerprint scanner is restored when relocking the bootloader using either the rooted boot.img or the stock one?
2: The same issue with fp calibration is faced by RM 5S/G users; can you check if the calibration fix in these forums works also for the RM6?
3: Lastly, have you tried flashing the latest phh GSI to see if it's working?
Click to expand...
Click to collapse
Fingerprint scanner should work after relocking the bootloader. As for flashing a GSI, there's no custom recovery for this device yet so I can't test any GSI roms yet.

chocolote4444 said:
Fingerprint scanner should work after relocking the bootloader. As for flashing a GSI, there's no custom recovery for this device yet so I can't test any GSI roms yet.
Click to expand...
Click to collapse
In this case, would you be able to run the following tests & share findings?
1: reflash stock boot, relock BL - check if fingerprint scanner is fixed
2: flash rooted boot.img (disable vbmeta), relock BL - check if fingerprint is fixed
If that would be the case, we could copy the calibration data from such a device; the data would be in /mnt/vendor/persist/goodix - I checked the stock ROM & it's not in there meaning it probably gets copied over during boot or mount-binded.
The last theory I want to check is the link between BL lock status & the fingerprint scanner - if some people have reported success with fixing the scanner with the builtin tool, there's a chance that the system framework or some other app is checking for the bootloader lock status & disabling the fingerprint if the former is unlocked. I've dumped the stock firmware but couldn't find a goodix dedicated apk, hence my hunch that it's a framework overlay. We would need to identify where the code is stored, decompile, find the security checking routine, disable, recompile & check agian - assuming it's not in any of the native libraries or the binary.
Assuming the access to the fingerprint scanner is indeed baked into the framework, using an AOSP GSIs would mean that the system would get unrestricted access to the fingerprint scanner, thus no blocking issue.
Thus (& addressing the 2nd part of your previous response), I'd suggest a 3rd test:
3: flash phh GSI or LOS GSI. The reason for the latter is because LOS usually has a wider range of hardware supported via hardware overlays.
You don't need a custom recovery to flash GSIs as these are fastboot images, so the following should suffice:
Code:
fastboot flash system gsi.img
fastboot -w

Umm Sir, got some problem with the global rom i patched it from your link. i cannot save any photos even screenshot. its nothing on my gallery. it seems it is not saving any photo. i hope you can teach me to solve it. thanks in advance

whincloud01 said:
Umm Sir, got some problem with the global rom i patched it from your link. i cannot save any photos even screenshot. its nothing on my gallery. it seems it is not saving any photo. i hope you can teach me to solve it. thanks in advance
Click to expand...
Click to collapse
Do a factory reset as you need to properly reinitialize package IDs, SELinux contexts & permissions.

adwinp said:
Do a factory reset as you need to properly reinitialize package IDs, SELinux contexts & permissions.
Click to expand...
Click to collapse
thank you. it is working well now.

I did the root process, but the phone stayed in the redmagic logo and it does not start me, what is the next process? flash the stock boot.img and it won't start

@chocolote4444 please share the solution when it gets stuck on the logo

FFX2 said:
@chocolote4444 please share the solution when it gets stuck on the logo
Click to expand...
Click to collapse
I am currently looking into it

Thanks for the guide

Hi. Will this also work for Android 11 on RM 5s?

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