Develop Bugs

fail installing Magisk

I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me

IO13 said:
I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me
Click to expand...
Click to collapse
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:

marstonpear said:
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
I assure you that if I would have preferred to find the information myself rather than wait for some kind user to answer me. Unfortunately it is not so simple, there are many double posts with information missing (you imagine a new user who wants to try to install the GCam, there are several posts on the subject with redundant or sometimes opposite information, there are two posts on how to install Magisk without losing the OTA, they are almost identical but in one there is written that with Pie no longer works, in the other no ..). Look for an info here with the search function is anything but simple so thank you for answering me so exhaustively!

marstonpear said:
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)

bla.tiga said:
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)
Click to expand...
Click to collapse
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:

marstonpear said:
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:
Click to expand...
Click to collapse
Oh i see.. thanks for the explanation... Gathering information in xda is bit confusing lol
Okay one more thing to be clear, right now im on oreo august security patch V 9.6.6.0 ODLMIFF
I want to install twrp and flash magisk (do i need downgrade to 9.6.4.0?) , if i succeed install both of that, and i want upgrade rom to pie or upper version via fastbot flash, i need to remove twrp and magisk, or just directly flash with mi flash??

[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

[TOOL] Flash Tool for Custom Roms

Dear All,
This is guide for flashing custom roms, the reason for this tool to simplify the flashing procedure and make ease for beginners.
Steps to follow:
1. Extract Symbian Flasher.
2. Extract Custom Rom files using playload dumper and place it on Symbian Flasher folder
3. Now open flash all. bat (it will ask some questions and give appropriate answers) you can skip format data for dirty flash.
That's it.
All credit goes to mauronofrio
Notes: This may be initial setup for preparing device for custom rom flash. if you already have stock rom on any of slot than no need for this, just choose stock rom slot while custom rom flashing. You can follow this below procedure for flashing Stock Rom on both slots.
A) Flashing Stock Rom on slot A
1. reboot to fastboot
2. open cmd and type
fastboot --set-active=a
3. now you on slot A
4. now open fastboot firmware folder and click flash all.bat
5. it will flash Stock Rom on slot A and automatically reboot to system (no need complete full setup)
B) Flashing Stock Rom on slot B
1. reboot to fastboot
2. open cmd and type
fastboot --set-active=b
3. now you on slot B
4. now open fastboot firmware folder and click flash all.bat
5. it will flash Stock Rom on slot B and automatically reboot to system (no need complete full setup)

Android Abdullah said:
Dear All,
This is guide for flashing custom roms, the reason for this tool to simplify the flashing procedure and make ease for beginners.
Steps to follow:
1. Extract Symbian Flasher.
2. Extract Custom Rom files using playload dumper and place it on Symbian Flasher folder
3. Now open flash all. bat (it will ask some questions and give appropriate answers)
That's it.
All credit goes to mauronofrio
Notes: You can follow this below procedure for flashing Stock Rom on both slots.
A) Flashing Stock Rom on slot A
1. reboot to fastboot
2. open cmd and type
fastboot --set-active=a
3. now you on slot A
4. now open fastboot firmware folder and click flash all.bat
5. it will flash Stock Rom on slot A and automatically reboot to system (no need complete full setup)
B) Flashing Stock Rom on slot B
1. reboot to fastboot
2. open cmd and type
fastboot --set-active=b
3. now you on slot B
4. now open fastboot firmware folder and click flash all.bat
5. it will flash Stock Rom on slot B and automatically reboot to system (no need complete full setup)
Click to expand...
Click to collapse
Will this work on A11 ?

need wipe my data ?

Hi, I have a European model oneplus 8 pro 12/256, never unlocked, now it mounts the android 11 beta 2 rom, I wanted to try some custom rom, where should I start without doing any damage?

nibera said:
Hi, I have a European model oneplus 8 pro 12/256, never unlocked, now it mounts the android 11 beta 2 rom, I wanted to try some custom rom, where should I start without doing any damage?
Click to expand...
Click to collapse
yes. downgrade to android 10, unlock bootloader and flash custom rom. make sure you have chosen correct slot while flashing. normally it is A. try with A for first time.

gaww said:
Will this work on A11 ?
Click to expand...
Click to collapse
on next update i will look on it...

brmbjn said:
need wipe my data ?
Click to expand...
Click to collapse
for stock to custom its necessary. custom rom dirty flash no need to wipe.

Android Abdullah said:
for stock to custom its necessary. custom rom dirty flash no need to wipe.
Click to expand...
Click to collapse
Custom to stock no need wipe

How do you add gapps to flash as well?

Very nice tool.

Help me, I can't Flashing Stock Rom on slot B.

bionaftic said:
Help me, I can't Flashing Stock Rom on slot B.
Click to expand...
Click to collapse
The device will show qualcomm crash dump mode.

I dont see the download for this, does it still exist? Im having the hardest time trying to install roms

DinikXD said:
I dont see the download for this, does it still exist? Im having the hardest time trying to install roms
Click to expand...
Click to collapse
The best way to install custom ROMs is by following the instructions in the thread of the ROM you would like. Developers have instructions for a reason, and generally if you follow the installation instructions you will likely run into less issues.

How To Guide K40s flash miui.eu rom

Since I am in mainland China, after seven days waiting, I unlocked my k40s finally.
Get ROM from xiaomi.eu link to thread of stable release is https://xiaomi.eu/community/threads/miui-13-stable-release.64441/
Download in sourceforge: https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
I downloaded two roms:
1. xiaomi.eu_multi_MUNCH_V13.0.7.0.SLMCNXM_v13-12-fastboot.zip
2. xiaomi.eu_multi_MUNCH_V13.0.10.0.SLMCNXM_v13-12.zip
### First one:
I use script inner zip to flash, success.
### The second one:
At first I can't boot from twrp.img after search by Google I found out that I run fastboot command in fastbootd env.
There is a ref: https://forum.xda-developers.com/t/fastboot-error-no-such-file.4483677/
I boot to fastboot (Not fastbootD) by command
Code:
adb reboot bootloader
And I can boot the twrp and flash the second rom.
The guide of flash second rom is
Code:
1. push rom to sdcard
2. adb reboot bootloader
3. fastboot boot twrp.img
4. Install rom in TWRP
5. Clear data & format
Update
This guide is for MIUI13 and maybe there's something different of current MIUI14 ROM.

Latest TWRP https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v6.3_A12
BOOT VERSION A12
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP
Reboot TWRP​

hello there...
i am arsh from india. i have unlocked the bootloader of my poco f4 only to flash eu rom. i have unlocked, installed twrp and then i flashed eu rom zip file. In the last step when i try to do format data, i got an error unable to mount system and it was unsuccessful. So without rebooting to system i again rebooted to twrp to perform format data and again same error appeared. later i chaged boot slot from a to b and then performed format data and then it says "no os installed". So i changed slot again to a and then i booted to system and i am able to boot into eu rom.
My Question did i perform the flash correct???
I noticed when i m using eu rom battery is draining faster than global rom...what is your opinion??

psklf said:
Since I am in mainland China, after seven days waiting, I unlocked my k40s finally.
Get ROM from xiaomi.eu link to thread of stable release is https://xiaomi.eu/community/threads/miui-13-stable-release.64441/
Download in sourceforge: https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
I downloaded two roms:
1. xiaomi.eu_multi_MUNCH_V13.0.7.0.SLMCNXM_v13-12-fastboot.zip
2. xiaomi.eu_multi_MUNCH_V13.0.10.0.SLMCNXM_v13-12.zip
### First one:
I use script inner zip to flash, success.
### The second one:
At first I can't boot from twrp.img after search by Google I found out that I run fastboot command in fastbootd env.
There is a ref: https://forum.xda-developers.com/t/fastboot-error-no-such-file.4483677/
I boot to fastboot (Not fastbootD) by command
Code:
adb reboot bootloader
And I can boot the twrp and flash the second rom.
The guide of flash second rom is
Code:
1. push rom to sdcard
2. adb reboot bootloader
3. fastboot boot twrp.img
4. Install rom in TWRP
5. Clear data & format
Click to expand...
Click to collapse
hello there...
i am arsh from india. i have unlocked the bootloader of my poco f4 only to flash eu rom. i have unlocked, installed twrp and then i flashed eu rom zip file. In the last step when i try to do format data, i got an error unable to mount system and it was unsuccessful. So without rebooting to system i again rebooted to twrp to perform format data and again same error appeared. later i chaged boot slot from a to b and then performed format data and then it says "no os installed". So i changed slot again to a and then i booted to system and i am able to boot into eu rom.
My Question did i perform the flash correct???
I noticed when i m using eu rom battery is draining faster than global rom...what is your opinion??

arsh011 said:
hello there...
i am arsh from india. i have unlocked the bootloader of my poco f4 only to flash eu rom. i have unlocked, installed twrp and then i flashed eu rom zip file. In the last step when i try to do format data, i got an error unable to mount system and it was unsuccessful. So without rebooting to system i again rebooted to twrp to perform format data and again same error appeared. later i chaged boot slot from a to b and then performed format data and then it says "no os installed". So i changed slot again to a and then i booted to system and i am able to boot into eu rom.
My Question did i perform the flash correct???
I noticed when i m using eu rom battery is draining faster than global rom...what is your opinion??
Click to expand...
Click to collapse
Which rom and TWRP?

NOSS8 said:
Which rom and TWRP?
Click to expand...
Click to collapse
Eu rom 14.0.3.0,
Twrp - twrp-3.7.0_12-0-munch

arsh011 said:
Eu rom 14.0.3.0,
Twrp - twrp-3.7.0_12-0-munch
Click to expand...
Click to collapse
Ok, which rom were you on before flashing?

NOSS8 said:
Ok, which rom were you on before flashing?
Click to expand...
Click to collapse
i was on miui global stable rom version 13.0.6

arsh011 said:
i was on miui global stable rom version 13.0.6
Click to expand...
Click to collapse
The rom you flashed is not the latest.xiaomi.eu_multi_MUNCH_V14.0.5.0.TLMCNXM_v14-13.zip
to update you must update the twrp from A12 to A13 and use the OTA.
This rom is hybrid, which means you can update it with a pc and fastboot using the update.bat script included in the extracted zip folder.
If you haven't installed all your apps, use the First install .bat file.
The procedure for a first installation with TWRP is as follows:
Twrp/format data type yes reboot Twrp(if errors ,reds lines ,start again by restarting on the Twrp at each try.
Then sideload the rom or use OTG.
Errors remaining at the end of the flash, ignore them.
Delete the lock screen security before all opérations.

NOSS8 said:
The rom you flashed is not the latest.xiaomi.eu_multi_MUNCH_V14.0.5.0.TLMCNXM_v14-13.zip
to update you must update the twrp from A12 to A13 and use the OTA.
This rom is hybrid, which means you can update it with a pc and fastboot using the update.bat script included in the extracted zip folder.
If you haven't installed all your apps, use the First install .bat file.
The procedure for a first installation with TWRP is as follows:
Twrp/format data type yes reboot Twrp(if errors ,reds lines ,start again by restarting on the Twrp at each try.
Then sideload the rom or use OTG.
Errors remaining at the end of the flash, ignore them.
Delete the lock screen security before all opérations.
Click to expand...
Click to collapse
tq for the reply. a few hours ago i updated the eu rom to latest version via twrp. for now everything is working. i would like to know some things.
1. imo the battery backup with eu rom is terrible compared to global stable rom. whats your view about that??
2. Are there any heating issues with eu rom 14 ?
3. can we revert to stock rom and lock bootloader?

arsh011 said:
tq for the reply. a few hours ago i updated the eu rom to latest version via twrp. for now everything is working. i would like to know some things.
1. imo the battery backup with eu rom is terrible compared to global stable rom. whats your view about that??
2. Are there any heating issues with eu rom 14 ?
3. can we revert to stock rom and lock bootloader?
Click to expand...
Click to collapse
Not having this device, I cannot answer the first 2 questions precisely but on my 12 pro(Xiaomi Eu rom) the switch to A13 was beneficial for both.(Have you just updated? Give the system time to optimize itself).
3/Use miflash (if you have an F4 and not a K40s).
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com

Question how to boot from different slot ?

Мy bootloader is unlocked. My device is Le2127. I reboot into bootloader mode, switch the active slot, then reboot and get back into the bootloader. How to load firmware from another slot? Thanks.
OxygenOS 13.0 Stable F.17 GL
Android 13

stranger75 said:
Мy bootloader id unlocked. My device is Le2127. I reboot into bootloader mode, switch the active slot, then reboot and get back into the bootloader. How to load firmware from another slot?
Click to expand...
Click to collapse
What is your active slot now?

A (B not loaded) if I flash the firmware into another slot (B), then only B is loaded
In the installer script, the firmware commands write to both slots, but only the active one is loaded

stranger75 said:
A (B not loaded) if I flash the firmware into another slot (B), then only B is loaded
In the installer script, the firmware commands write to both slots, but only the active one is loaded
Click to expand...
Click to collapse
Then I don't truly understand what you are trying to do or what problem you are having.

I would like to boot from any slots, for example, if the system is damaged on one slot. As far as I know they have a common userdate section
here is a related article:
Installation of Stock ROM on both slots.
Hello friends, I have read in the threads about installation of oxygen OS on both slots to be safe to install custom ROM to avoid any error. I want to know the step by step procedure to install the stock ROM on both slots. Thanks.
forum.xda-developers.com
But it doesn't work here

stranger75 said:
I would like to boot from any slots, for example, if the system is damaged on one slot. As far as I know they have a common userdate section
here is a related article:
Installation of Stock ROM on both slots.
Hello friends, I have read in the threads about installation of oxygen OS on both slots to be safe to install custom ROM to avoid any error. I want to know the step by step procedure to install the stock ROM on both slots. Thanks.
forum.xda-developers.com
But it doesn't work here
Click to expand...
Click to collapse
Check into the "copyslot" script. Might be an answer for you

Where can you find it for os 13 ?
In that script, support only android 11

stranger75 said:
Where can you find it for os 13 ?
In that script, support only android 11
Click to expand...
Click to collapse
"fastboot getvar all" will tell you active slot while in fastboot.
fastboot --set-active=a
&
fastboot --set-active=b
is changing active slot

I know it and have done it. But loading from another slot does not happen.
Instead of loading the system, I get into Bootloader

stranger75 said:
I know it and have done it. But loading from another slot does not happen.
Instead of loading the system, I get into Bootloader
Click to expand...
Click to collapse
I have heard some say flash firmware twice to get same on both slots...otherwise I am out of ideas!

I tried several times when switching the slot via fastboot, but each time only the one installed in the current slot is loaded

@stranger75
I am not sure that it is still possable to have two seperate system levels installed since the intoduction of Dynamic Partitions.
Implementing Dynamic Partitions - [source.android] - [website] - Link
Cheers.