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
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.
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.
Fastboot reboot fastboot to go into fastbootD
flash-all.bat script to fastboot flash all img files
fastboot set_active other to switch slot
Repeat above to flash all files into other slot
HueyT said:
Fastboot reboot fastboot to go into fastbootD
flash-all.bat script to fastboot flash all img files
fastboot set_active other to switch slot
Repeat above to flash all files into other slot
Click to expand...
Click to collapse
Sorry Sir, but I did not understand. Please confirm if I am right to go ahead.
1) first one is that what is the zip file where I can download and unzip. Is it fastboot ROM provided by
@mauronofrio or any other.
My other concern is that is flashing the ROM on both slots applies on the stock ROM or it may be done on cutom ROM too. As far as know, while installing Lineage OS, the installation method only sugest to flash copy partion zip through sideload command and nothing else.
2) What is the actual command to switch to other slot?
Is it
"fastboot set_active other"
? which you have said in my reply.
3) Can I flash two ROMs in oneplus 7t say Lineage ROM on active slot(a or b) and other custom ROM on slot(b or a) to other slot? If yes then How to boot ROM on one slot while other keeping unaffected and the how to switch to other ROM without affecting the first ROM so that my device does not brick.
sorry for so many doubts. Please clear my doubts so that I have knowledge too for my device.
thanks and thanks.
1) yes, usually oos10.0.16 and then update it's to 11.0.4.1 (or use oxygen updater app from Play store to download and update to 11)
2) correct, or use custom recovery to change slot to fastboot install rom into other slot
3) possible but both roms must be able to share same data (few can, usually by same dev). TWRP (Lossyx) or debug (Matt0301) recovery can also switch slot and boot rom from A slot or B slot. Best use same rom into both slots to less chance of bricking.
Also don't relock bootloader if playing with custom roms, kernels, root as you'll have hard brick
Orangefox recovery works also (based on TWRP). Most new roms r on Telegram as many devs don't like xda due to ads and restrictions
HueyT said:
1) yes, usually oos10.0.16 and then update it's to 11.0.4.1 (or use oxygen updater app from Play store to download and update to 11)
2) correct, or use custom recovery to change slot to fastboot install rom into other slot
3) possible but both roms must be able to share same data (few can, usually by same dev). TWRP (Lossyx) or debug (Matt0301) recovery can also switch slot and boot rom from A slot or B slot. Best use same rom into both slots to less chance of bricking.
Also don't relock bootloader if playing with custom roms, kernels, root as you'll have hard bric
Click to expand...
Click to collapse
1) I think the fastboot ROM given by @mauronofrio
should flash on both slots automatically. Am I correct?
2) Can I use Lineage recovery?
3) When I install a ROM whether it is oxyegn OS or custom ROM first time after formatting data, does the ROM automatically flash on both slots?
or I have to manually flash the ROM on both slots.
1) no, u must switch slot and do it again to other slot
2) to go into fastbootD u must use oos stock recovery. LOS recovery only allows adb sideload and not zip installation like Magisk. It can't backup rom either. It can't switch slots
3) unless you edit the flash-all.bat script to fastboot flash both slots, no rom installation will do it automatically to both slots. U must switch slot and do it again
HueyT said:
1) no, u must switch slot and do it again to other slot
2) to go into fastbootD u must use oos stock recovery. LOS recovery only allows adb sideload and not zip installation like Magisk. It can't backup rom either. It can't switch slots
3) unless you edit the flash-all.bat script to fastboot flash both slots, no rom installation will do it automatically to both slots. U must switch slot and do it again
Click to expand...
Click to collapse
Thanks for the reply.
But afaik @mauronofrio thread for fastboot ROM did not say to change the slot and also in Youtube videos also the video poster does not write any command of changing the slot.
I have read in the thread every comment, no one say about changing the slot.
So I got confused.
Not required but recommended to lessen risk of crashdump
HueyT said:
Orangefox recovery works also (based on TWRP). Most new roms r on Telegram as many devs don't like xda due to ads and restrictions
Click to expand...
Click to collapse
Where I can find a list of ROMs available on Telegram? Thanks
OnePlus 7/T/Pro | Updates
OnePlus 7 Series updates channel For Community : @op7discussion For Google Camera : @gcamOP7
t.me
Just a few goodies
.
Hello everyone,
I have a new Xiaomi 11T EEA device, tried rooting it with the following steps, but failed:
- Updated to the latest official MIUI version (13.0.9.0)
- Unlocked bootloader with MiUnlock (shows the unlocked padlock at boot, and also in developer options)
- Downloaded the latest ROM with the updater app in phone (also tried from c.mi.com, same files, checked checksums)
- Used payload dumper at PC to extract the boot.img from the ROM
- Installed latest Magisk Manager (25.2) to the phone
- Pached the boot.img with Magisk
- Installed latest adb and drivers to my PC (restarted it after the install)
And then I tried booting the phone to the patched boot.img (fastboot boot patched_boot.img), but failed (even tried with the stock boot.img, same result):
downloading 'boot.img'...
OKAY [ 3.188s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 11.135s
I tried with my PC, with another notebook, 3 different USB A to C cable, 2 different USB C to C cable (different orientations too), all of the USB ports on the devices, but I got the exact same result.
So far I succeeded with these steps with 3 other Xiaomi phones (Redmi Note7, Mi 9T, Poco F3), but not with this one, and I have no idea what else I can do.
I suspected it has something to do with MediaTek SOC, that's the only meaningful difference I can think of.
Does anyone have any idea what else I can try, or maybe have a working patched boot.img?
Thanks for reading it, have a nice day!
Once the boot modify install with Fastboot, use fastboot reboot.
NOSS8 said:
Once the boot modify install with Fastboot, use fastboot reboot.
Click to expand...
Click to collapse
Maybe I understand it wrong, but I didn't install the boot.img, and don't really want to install it until I am sure I don't soft brink the phone.
s-zoli said:
Maybe I understand it wrong, but I didn't install the boot.img, and don't really want to install it until I am sure I don't soft brink the phone.
Click to expand...
Click to collapse
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/
NOSS8 said:
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/
Click to expand...
Click to collapse
It will be rooted until reboot, which is fine for a temporary root and testing things before making it permanent.
From my understanding it should be working either way, booting to it, or flashing right away. Previously I tested the patched boot.img just by booting into it, and worked every time. At the Redmi phone when I tried to flash the boot.img (that was used to boot into and worked), it didn't boot and got stuck to fastboot, and had to flash back the original boot.img.
I read the mentioned thread, it's the same steps I did, except the last booting vs flashing with fastboot.
Am I missing some key information how the booting mechanism works?
s-zoli said:
It will be rooted until reboot, which is fine for a temporary root and testing things before making it permanent.
From my understanding it should be working either way, booting to it, or flashing right away. Previously I tested the patched boot.img just by booting into it, and worked every time. At the Redmi phone when I tried to flash the boot.img (that was used to boot into and worked), it didn't boot and got stuck to fastboot, and had to flash back the original boot.img.
I read the mentioned thread, it's the same steps I did, except the last booting vs flashing with fastboot.
Am I missing some key information how the booting mechanism works?
Click to expand...
Click to collapse
Newer devices have A/B partitions unlike old ones.
NOSS8 said:
Newer devices have A/B partitions unlike old ones.
Click to expand...
Click to collapse
So you are saying that flashing the boot.img replaces both A and B partition and will most probably work, even if booting into it doesn't?
s-zoli said:
So you are saying that flashing the boot.img replaces both A and B partition and will most probably work, even if booting into it doesn't?
Click to expand...
Click to collapse
The .img boot never replaces the partitions, I was answering that you had already rooted other but old devices, that is to say without A/B partitions.
And why do you want to root this model with soc MTK(No or few development for Xiaomi with Mediatek processors)?
NOSS8 said:
The .img boot never replaces the partitions, I was answering that you had already rooted other but old devices, that is to say without A/B partitions.
And why do you want to root this model with soc MTK(No or few development for Xiaomi with Mediatek processors)?
Click to expand...
Click to collapse
The Poco F3 is a newer phone, and I just checked with Treble Check app, that it has seamless system update, therefore A/B system partitions (and so does the 11T).
The reason is the same as for every other phone... customization, automations, battery management... etc.
The things that should be available for power users, not just in fancy gaming phones.
It just happens to have MTK instead of QC (like the 11T Pro).
Do you have any information if this SOC difference can affect the booting and therefore rooting it?
s-zoli said:
The Poco F3 is a newer phone, and I just checked with Treble Check app, that it has seamless system update, therefore A/B system partitions (and so does the 11T).
The reason is the same as for every other phone... customization, automations, battery management... etc.
The things that should be available for power users, not just in fancy gaming phones.
It just happens to have MTK instead of QC (like the 11T Pro).
Do you have any information if this SOC difference can affect the booting and therefore rooting it?
Click to expand...
Click to collapse
MTK=MediaTek
QC=Qualcomm
Change nothing at the root level.
Everything you want to optimize is possible without rooting, moreover you will have to install modules which themselves consume battery.
Except for personalization.
NOSS8 said:
MTK=MediaTek
QC=Qualcomm
Change nothing at the root level.
Everything you want to optimize is possible without rooting, moreover you will have to install modules which themselves consume battery.
Except for personalization.
Click to expand...
Click to collapse
Sure, you're right, but I already started the rooting process, the bootloader is unlocked, so I already lost a few things (Google Pay, Netflix... etc).
The only way out is re-lock the bootloader or find a way to install Magisk and modules for it.
We deviated a bit from the original question...
I haven't found any source of information what does "Too many links" error means?
Also I didn't find any information if I can easily get back to original state if flashing the supposedly good pached boot.img doesn't work. (bootloop, stuck at fastboot... etc)
My way of being somewhat sure it works was first booting to it, but that doeasn't work now, and it's suspicious for me that the flashing won't work either.
To have the play store certified, use Magisk + zygisk.
https://topjohnwu.github.io/Magisk/
https://www.droidwin.com/fix-status-read-failed-too-many-links/
Once the boot modify install with Fastboot, use fastboot reboot.
Long story short... I just went for it and flashed the patched boot.img, and it's working just fine.
I don't know why it didn't want to boot, but flashing worked and now I have root access.
NOSS8 said:
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/
Click to expand...
Click to collapse
thats snapdragon, and this is mediatek
will this work with mediatek? without specifying a/b partitions?
Code:
fastboot flash boot patched_boot.img
bluviper said:
thats snapdragon, and this is mediatek
will this work with mediatek? without specifying a/b partitions?
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
Check:
https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
getprop ro.build.ab_update
Then you will know which command to choose.
NOSS8 said:
Check:
https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
getprop ro.build.ab_update
Then you will know which command to choose.
Click to expand...
Click to collapse
i have the a/b partition
bluviper said:
i have the a/b partition
Click to expand...
Click to collapse
So,use
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
or
fastboot flash boot_ab patched_boot.img
fastboot reboot
I just flashed without _a _b or _ab and it flashed still to both slots
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
jcp2 said:
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
Click to expand...
Click to collapse
Try using Android Flash Tool to get back to stock.
I tried. it failed.
Flash FailedDevice failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
jcp2 said:
I tried. it failed.
Flash FailedDevice failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
Click to expand...
Click to collapse
Then just manually flash ROM files in fastboot
jamescable said:
Then just manually flash ROM files in fastboot
Click to expand...
Click to collapse
is there a write up somewhere with adb commands?
Use PixelFlasher and the latest full update.
AlDollaz said:
Use PixelFlasher and the latest full update.
Click to expand...
Click to collapse
tried that as well
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I'm not sure of the commands. Fastboot flash recovery "recovery.img" , same with the other files inside the zip inside the stock rom zip file
If i ran into this issue I'd try fastboot -w and fastboot update a custom rom.
jcp2 said:
is there a write up somewhere with adb commands?
Click to expand...
Click to collapse
Most need to be flashed in fastbootd I think. So to get there, fastboot reboot fastboot. You can flash recovery( boot, dtbo and vendor boot) in regular fastboot. That should fix everything because it will fully get rid of magisk
I used AFT and forced flashed partitions / wiped (kept bootloader unlock) and it's alive again!
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
StanWiz said:
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
Click to expand...
Click to collapse
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Strephon Alkhalikoi said:
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Click to expand...
Click to collapse
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
StanWiz said:
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
Click to expand...
Click to collapse
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Strephon Alkhalikoi said:
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Click to expand...
Click to collapse
It's not a question of knowledge but rather the things that are beyond ones control - possibility of bugs in the code. For example look what happened recently with platform tools.
@jcp2 With all the things you flash, you should also know what that is. Then it would be much easier for you to figure it out why your device is in an unbootable state.
Magisk, Kernel, fastbootd... have one thing in common: your boot.img!
It doesn't make sense to let Magisk patch your boot.img and installing a custom kernel without Magisk installed afterwards. In that case Magisk gets overwritten.
Your fastbootd is only a binary and located in the recovery's /sbin folder. Due to the fact that your P6P is an A/B slot device, your recovery is part of the boot.img.
Flash your stock boot.img from the image-raven-BUILD_NO.zip that you'll find inside your firmware download.
I had already tried flashing stock boot image to both slots. I had to use AFT and force flash all partions. I'm up and running/ rooted. I just have to reinstall apps .
Android flash tool is by far the easiest way to go for sure. Happy you got it fixed
{Mod edit: Quoted post has been deleted. Oswald Boelcke}
6. fast boot flash
That ADB Command does nothing.
The correct command is:
fastboot flash boot boot.img if you want to flash the boot.img
{Mod edit: Quoted post has been deleted. Oswald Boelcke}
You should give us the correct command. The syntax is (see fastboot -h):
Code:
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.
you can't use "fast boot" for a binary that's called "fastboot(.exe)".