Related
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
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.
EMUI 8 Stock ROMs:
3.2.1-0 by pretoriano80 (with data decryption on Android 8 )
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
EMUI 8 Custom ROMs:
3.2.1.0 by Catuva21:
https://mega.nz/#!JlkRVY7b!Hz0QTmbgmMNeCaU-PmVRBGKsdd9pslmWNkOZpE6I8ZA
3.2.3-0 by Askuccio
https://mega.nz/#!h9903SqS!aRXc9x6Kuz_GclVy_3ZExCLDSdnp7Ee8VIgfqOG9x8k
Chinese ROMs (inc. KangVip):
3.2.1-0
https://mega.nz/#!sp0UyCDR!bq10MAyh0sddUCPi0zecQzrmLfCESFvNlCiQ3vkPMqI
EMUI 9.1 Stock ROM & Custom ROMs:
3.2.1-0 GAGUGA Edition
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
EMUI 9.1 Custom ROMs:
3.4.0-0-emui9_eR by @S_mak
https://mega.nz/#!B8kWgJDC!_hj7xkTzF9Uj66wKjtrWPHEV5Dbkk7Q256tuiKg7FQU
On [A12], [A12.1] GSIs use 3.4.0-0-emui9_eR .
Do you mean you can install these over erecovery partition?
adamfirari said:
Do you mean you can install these over erecovery partition?
Click to expand...
Click to collapse
These TWRPs allow you to install any compatible TWRP over eRecovery.
Hi!
Is there a recovery that is able to make a full backup (modem nvm ecc..)?
TureX said:
Hi!
Is there a recovery that is able to make a full backup (modem nvm ecc..)?
Click to expand...
Click to collapse
Hello,
I never use Nandroid backup, so I don't know. Test it and let us know
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
wax_77 said:
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
Click to expand...
Click to collapse
HI!
Which vendor are you using? And which twrp shared are you using? Does lineageos 16 official boot keeping twrp installed?
Thanks in advance
wax_77 said:
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
Click to expand...
Click to collapse
Hello,
I successfully installed the addonsu-16.0-arm64 using
TWRP
You have to enable root in Developer options. Works fine...
Hi there,
which TWRP can I use to downgrade to Oreo via HuRupdater?
Thanks.
Fjord1 said:
Hi there,
which TWRP can I use to downgrade to Oreo via HuRupdater?
Thanks.
Click to expand...
Click to collapse
3.2.1-0 by pretoriano80 .
Note: If you don't have the required files stored somewhere, then it's just an academic question - Firmware finder is ďead.
-Alf- said:
Firmware finder is ďead.
Click to expand...
Click to collapse
It makes me sad...
And what about dload method?
Fjord1 said:
downgrade to Oreo
Click to expand...
Click to collapse
Fjord1 said:
dload method
Click to expand...
Click to collapse
you will get absolutely no success, it may even brick your phone.
Hi all. I am trying to recover content from a MediaTab T5 with a Damaged screen (no picture). I've managed to install these recoveries and reboot into them. However none of them provide an adb interface for shell access, only a virtual usb cd rom drive appears. How can I obtain recovery adb access? I need to enable USB debugging and push adbkey...
Anyone have any clues how I can work around this please. Is patched boot img the only way forward?
OK good news I Successfully booted into recovery and have adb access. I think the key was to power on with vol+, but WITHOUT the USB cable attached. If USB cable is attached then it tries to boot to system regardless
-Alf- said:
Hello,
I never use Nandroid backup, so I don't know. Test it and let us know
Click to expand...
Click to collapse
hi, I was just wondering incase something goes wrong, can you link me some thread or guide to go back to stock firmware (I do have the full firmware files)
Mahad Habib said:
hi, I was just wondering incase something goes wrong, can you link me some thread or guide to go back to stock firmware (I do have the full firmware files)
Click to expand...
Click to collapse
I'm not sure I fully understand your question :
- go back to stock from custom ROM?
- what full FW do you have?
-Alf- said:
I'm not sure I fully understand your question :
- go back to stock from custom ROM?
- what full FW do you have?
Click to expand...
Click to collapse
yes that's my question.
the one I have is
"Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
I know this works because I used it to downgrade.
Mahad Habib said:
yes that's my question.
the one I have is
"Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
I know this works because I used it to downgrade.
Click to expand...
Click to collapse
Yes, you can revert to stock flashing this Service ROM , if yot are running EMUI 8. For EMUI 9.1 use Service ROM 9.1.0. This process will erase all your data and lock the BL again!
Or, simply flash SYSTEM.img extracted from Service ROM using Huawei
update extractor. This procedure will not erase your data ,bootloader remains unlocked etc.
Hey Alf,
Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.
PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.
Thank you for your posts, they've been useful.
hopeless_bricker said:
Hey Alf,
Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.
PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.
Thank you for your posts, they've been useful.
Click to expand...
Click to collapse
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.
P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
hopeless_bricker said:
Since the recovery partition is occupied by Magisk
Click to expand...
Click to collapse
-Alf- said:
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.
P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
Click to expand...
Click to collapse
I got it wrong, it's a ANE-LX3! Mixed up with my other phone, sorry. In principle that method works, thank you. I didn't get to actually test it because it seems the Magisk recovery overrides the boot procedure so it always boots to recovery automatically.
Handy but I can't boot into the erecovery with the button combo now.
P.S.: I'm having issues with audio device switching. If I get a phone call with headphones inserted it routes to the speaker and I can't change it. If I remove the headphones then the mic doesn't work. I also have a bit inconsistent connection over bluetooth, sometimes it is connected but still plays over the speakers. I have the Huawei switch method enabled in the phh options. Did you experience this?
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.
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka ADB) and USB drivers should be set beforehand. Latest versions are reliable enough. PixelExperience, PixelOS and MIUI (official and Xiaomi.eu) ROMs have been tested. Before proceeding to flash, make sure about your ROM type (standard or vendor_boot) to avoid not desired consequences. Blew are the most recent versions.
_________________________________________________________________________
TWRP (standard)
Android 12:
twrp-3.7.0_12-v7.7_A12-alioth-skkk.img
Android 13:
twrp-3.7.0_12-v7.8_A13-alioth-skkk.img
[Instructions]
1. Reboot to fastboot mode.
2. Execute command below in ADB on PC:
fastboot boot "recovery.img"
Click to expand...
Click to collapse
"recovery.img" being your downloaded recovery file address.
3. Choose "Flash current TWRP" from TWRP's "Advanced" option.
4. Reboot.
_________________________________________________________________________
OrangeFox (standard)
Android 12+:
[email protected]_3_A12.zip
[Instructions]
1. Reboot to TWRP.
2. Choose "ADB Sideload" from TWRP's "Advanced" option.
3. Execute command below in ADB on PC:
adb sideload "recovery.zip"
Click to expand...
Click to collapse
"recovery.zip" being your downloaded recovery file address.
4. Reboot.
_________________________________________________________________________
OrangeFox (vendor_boot)
Read this thread for a detailed explanation and list of vendor_boot ROMs.
This is beta release. Treat it as such.
Android 13:
[email protected]_1_vendor_boot_vBaR.zip
[Instructions]
1. Reboot to your ROM's recovery.
2. Choose "ADB Sideload" from recovery's "Advanced" option.
3. Execute command below in ADB on PC:
adb sideload "recovery.zip"
Click to expand...
Click to collapse
"recovery.zip" being your downloaded recovery file address.
4. Reboot.
OR
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Execute command below in ADB on PC:
fastboot flash vendor_boot "recovery.img"
Click to expand...
Click to collapse
"recovery.img" being your extracted recovery image address.
4. Reboot.
OR
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Run "flash-whole-image.bat" file.
4. Reboot
_________________________________________________________________________
Ps: though there are some glitches, both recoveries can install Magisk to root the device.
_________________________________________________________________________
Sourceforge archive page
OrangeFox homepage
Platform Tools download page
Google USB Driver download page
Last time I tried installing lineageos using latest twrp it failed miserably
heybaybee said:
Last time I tried installing lineageos using latest twrp it failed miserably
Click to expand...
Click to collapse
Me too, better use its recovery.
New versions available. Links have been updated.
rashazad said:
New versions available. Links have been updated.
Click to expand...
Click to collapse
Thanks for the thread. Does the latest version support flashing MIUI Global ROMs? Im having a hard time flashing them via TWRP SKK 3.7.0_A12_V6.7_A13.
I tried to flash TWRP 3.7.0_7.7_13 and now my phone is in bootloop.
panjgoori said:
I tried to flash TWRP 3.7.0_7.7_13 and now my phone is in bootloop.
Click to expand...
Click to collapse
Which ROM are you using?
DarthJabba9 said:
Which ROM are you using?
Click to expand...
Click to collapse
MIUI EU 13.0.9
panjgoori said:
MIUI EU 13.0.9
Click to expand...
Click to collapse
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.
DarthJabba9 said:
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.
Click to expand...
Click to collapse
I accidently bricked my phone and its in EDL Mode now. Can you help me please
panjgoori said:
I accidently bricked my phone and its in EDL Mode now. Can you help me please
Click to expand...
Click to collapse
Sorry, I know nothing about EDL mode for this device. But I'm sure there are lots of tutorials on XDA or in a general Google search.
Vendor_Boot recovery links and instructions added.
Small changes made in instructions.
New version (7.8) for TWRP A13 (standard).
New version (11.1_1) for OFox (vendor_boot).
New version (11.1_3) for OFox (standard).
DarthJabba9 said:
So, you have flashed an A13 recovery on an A12 ROM? Of course you will have issues. You need to flash the correct recovery.
Click to expand...
Click to collapse
For those who want to.. I too thought as do @DarthJabba9 but...
I've bought a new poco F3, wich was with A12 MIUI. I tried to flash skkk twrp A12, then flash FW V14.xxx (A13), then skkk twrp A13 (trough twrp itself, or in fastboot) => bootloop, with or without rebooting in between..
It finally worked with only flashing skkk twrp A13 (on A12 MIUI), then FW V14.xx, then rom etc.
Hope it can help
néonaloj said:
For those who want to.. I too thought as do @DarthJabba9 but...
I've bought a new poco F3, wich was with A12 MIUI. I tried to flash skkk twrp A12, then flash FW V14.xxx (A13), then skkk twrp A13 (trough twrp itself, or in fastboot) => bootloop, with or without rebooting in between..
It finally worked with only flashing skkk twrp A13 (on A12 MIUI), then FW V14.xx, then rom etc.
Hope it can help
Click to expand...
Click to collapse
That's a very atrange way to have latest fw.
How did you flash twrp through twrp?
Please describe what you have done clearly.
Restarts are necessary.
Also if you plan to have a clean flash, which is recommended, there are much easier and straight forward methods.
rashazad said:
1. Reboot to fastboot mode.
2. Extract downloaded recovery zip file.
3. Execute command below in ADB on PC:
"recovery.img" being your extracted recovery image address.
4. Reboot.
Click to expand...
Click to collapse
Tried using this method but I am getting the following error on AOSPA: FAILED (remote: 'Error flashing partition : Volume Full')
nehalchoy said:
Tried using this method but I am getting the following error on AOSPA: FAILED (remote: 'Error flashing partition : Volume Full')
Click to expand...
Click to collapse
That error does not seem to be related to the process.
Something (probably free apace) is wrong about your pc or phone.
What ROM were you using?
rashazad said:
That's a very atrange way to have latest fw.
How did you flash twrp through twrp?
Please describe what you have done clearly.
Restarts are necessary.
Also if you plan to have a clean flash, which is recommended, there are much easier and straight forward methods.
Click to expand...
Click to collapse
Well I didn't want to make a complete tutorial ...
To flash twrp trough twrp, 'install' > change with "image" > install the recovery.img.. It has always worked, for long years..
About flashing a A13 rom (++) coming from MIUI A12 (I each time restarted from scratch, re-installing global MIUI) : I've tried a lot of ways.
I began to install A12 twrp skkk in fastboot mode (1st 'boot' then flash), reboot to recovery, then upgrade to A13 twrp through twrp (reboot to recovery), then A13 FW > bootloop ;
I tried flash A12 twrp (fastboot)(reboot to recovery), then A13 twrp (fastboot too)(reboot to recovery), flash FW > bootloop ;
I also tried A12 twrp (reboot to recovery), then FW (reboot to recovery ok), A13 twrp (reboot to recovery) > bootloop...
I won't list all what i did ! but finally I flashed A13 twrp directly on A12 MIUI (reboot to recovery ok), flash FW (reboot to recovery ok) and that worked. I then flashed my A13 rom (without rebooting system first) > reboot to recovery +reboot system, and finally flashed Gapps, magisk and other stuff. I do know it's not a common way, but the one that worked.
EDIT : I do know it can work (maybe even easier) to flash the MIUI A13 fastboot rom, but had a other device hard bricked some time ago doing this. That's why i tried to only flash the FW
PS : if you can help, I've only one issue to solve yet : I've flashed magisk 26.1, i could have bank & pro apps to work correctly, the only app that I cannot is the FAI tv (error P531 'can't reach my account' (even if i'm well connected), probably root detected.. thanks ! (ofc it's on the deny list, with magisk modules such as Universal Safetynet Fix, zygisk ....)
And edit 2 : I forgot to thank you for this thread !
Common way to flash rom with upgrade (not update) is clean install.
Also, magisk handles safetynet with no problem. No need for that. And zygisk is not module.
For that specific application, check that it is fully selected in zygisk since sometimes all checkboxes for application is not selected.
You're welcome