Database Develop

Help! Got bootloop after flashing permissiver_v5 in Evo X Rom (A2)

Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
LATEST UPDATE:
With the help of KevMetal, I can now use my phone after a week of being hardbricked. At first, my device can't boot to the bootloader or recovery, so what I did was to press the volume down and power button for some time and my phone was detected by the PC. So my device booted to EDL by itself, no need to open the phone. Then I used the 2018 version of MiFlash Tool and flashed the V.10.0.17 of stock Pie ROM from here: https://forum.xda-developers.com/mi-...-t3824849/amp/
After that, I flashed the persist.zip provided by KevMetal (browse in this thread) in recovery since I can't sideload the zip, and it worked fine. I then booted to system and finally there was no bootloop.
I then noticed that the IMEI was gone, so I tried to fix through some guides online but this one worked for me. https://medium.com/@shekhawatkoki/fi...1-2ed533548d32

Ronaldendoma said:
Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
Click to expand...
Click to collapse
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?

Ronaldendoma said:
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?
Click to expand...
Click to collapse
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I missed something. I'll update here for the result once I can be back to PC.

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.

Ronaldendoma said:
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.
Click to expand...
Click to collapse
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs

here is a photo where you need to activate adb
Sent from my wayne using XDA Labs

KevMetal said:
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I need to wait more, I think. Before this thread, I tried to adb sideload in TWRP but it took somewhat long and still 0%, so I just cancelled since I ran out of time.

KevMetal said:
here is a photo where you need to activate adb
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?

techieboy2020 said:
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?
Click to expand...
Click to collapse
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs

KevMetal said:
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.

techieboy2020 said:
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.
Click to expand...
Click to collapse
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs

KevMetal said:
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.

techieboy2020 said:
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.
Click to expand...
Click to collapse
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs

KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Got it. So the zip is compatible for either Pie or Android 10?
What's the best version for Miflash tool? I tried the newer version but it can't detect my device, and only the older version can detect. But it seems that the older version can't be trusted also since I still got persist error before.
For #10, my device will bootloop 4 to 5 times. So will it automatically turn off and on again until it will successfully boot? How long does it normally boot?

UPDATE:
KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?

techieboy2020 said:
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?
Click to expand...
Click to collapse
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs

Just FYI:
Since 10.0.2.0 till now I thought that persist.img is version-insensitive, as I flashed persist.img taken from 8.1 ROM into couple of versions of 9.0 without any problems (via my method published in "Guides...").
Last week I noticed that compass is "showing south", and tried to flash various versions of persist.img into active 11.0.12.0 - and was surprised to encounter "white screen of eternal booting" with non-native version of persist.img. So finally had to flash persist.img taken from 11.0.12.0 fastboot ROM image.
(Btw, my problem with compass seems to have 2 sides -1st is somewhat very big deviation at homeplace, and 2nd is that only 1st magnetic sensor is being calibrated while second magnetic sensor is not being calibrated by means I used).

KevMetal said:
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
So I was able to use another laptop, and I managed to install adb, drivers, and MiFlash Tool. The 2018 version can now detect my phone, and I can now at least boot into fastboot. But my flashing is still not successful because I got stuck at system.img. The laptop freezes and I already tried to free up space in C: drive.

Question root failed and bootloop

I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Hey,
If you've only booted the image, then you only need to reboot and the image is lost, the only way that it would be permanent is if it was flashed: fastboot flash not: fastboot boot.
Usually what happens is when you obtain a firmware to install or in your case change region, and you wish to root this firmware you would extract payload.bin then use fastboot enhance to extract the boot.img
Then copy to your phone and patch it with the latest stable Magisk (in this case 24.3)
So again, if you've only booted the image then just reboot your phone and it'll turn on using the actual flashed boot.img from the firmware, not the one you booted.
If that doesn't work then you must have flashed it. In which case you can either re-flash your original boot.img or boot then direct install a correctly patched image for the correct firmware (after a success boot) via Magisk.

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Here's a good "how to" to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/

Canuck Knarf said:
Here's a good how to to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Click to expand...
Click to collapse
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse

dladz said:
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
Click to expand...
Click to collapse
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk

Canuck Knarf said:
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Click to expand...
Click to collapse
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
If what he's advised is true then he's successfully changed OS/region and now wants to root, the only thing he's done thus far is to boot a boot image. I think he's flashed it as booting is not permanent, to suggest to go ahead and attempt to obtain a color OS boot image or vendor image is absolutely ridiculous.
He's on an EU firmware. So he requires an EU boot image.

He's in boot loop cause he is booting to A slot...

Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode

dladz said:
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
Click to expand...
Click to collapse
oxygen OS using the firmware EU 11_A.12.... He still needs boot img ...vender_boot form the firmware EU 11_A.12 . to root

leofung_wai said:
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
Click to expand...
Click to collapse
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance

He already had boot?? What are you talking about???
He had a functional OS, in order to root you only need ONE image.
The boot image which comes from OOS. The link you sent is for Color OS?? Make sense now ??
He just needs to patch it correctly and boot it then direct install.
Im going over this again with someone who's incapable of understanding the basics.

Canuck Knarf said:
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
Click to expand...
Click to collapse
You do realise that booting an image does not need to be directed don't you?
Only by flashing should you direct the image to a particular slot.
By flashing you are permanently flashing an image.
I don't think you understand this so I'll make it simple for you.
You want to root your phone. You have an image you've just patched, from boot.img to magisk_patched.img
Firstly you would want to send this via fastboot, you do not need fastboot enhance for this.
The preferred way to do this is to fastboot boot magisk_patched.img
Why is this preferred??
Because if it fails as it may. Then you are not stuck in a boot loop, you just reboot and you're back in the OS.
The 2nd method is flashing.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter.
Now although this can work it is not the preferred method because you aren't just booting the image you are flashing it, this means that if it fails you cannot just reboot and get back to the OS you have to either obtain a new boot image and patch it although you cannot do this yourself as your phone no longer boots or you obtain an already patched boot image, again the last one I wouldn't recommend..

Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
Ok so if you've got into the system..
You need to follow the instructions I have in my guide in order to get root...
You can use the boot image I have there.

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
It is always better to patch boot.img of your own version (you can dump it from payload dumper etc.) and then only fastboot boot patched_image.img and then directly install it via Magisk.

Boot this image.
192 MB folder on MEGA
mega.nz

Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally

Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done

leofung_wai said:
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Click to expand...
Click to collapse
If you've patched your own image and booted it then click Magisk then install. Then direct install and you're done..

dladz said:
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
Click to expand...
Click to collapse
thanks i success root by your image now
but i had a question, i messed up the slot B and now can only boot through slot A Will it affect anything

Question No TWRP folder

I have flashed TWRP to recovery (on my unlocked Redmi Note 10 Pro) and can access it no problem. But I have no TWRP folder on my phone and cannot see one when connected to my computer.
I have reflashed to try to fix it, but no change. I found a thread where the suggested terminal commands but I would need to root my phone and I don't think that is something I should be doing. Any suggestions?

31272809 said:
I have flashed TWRP to recovery (on my unlocked Redmi Note 10 Pro) and can access it no problem. But I have no TWRP folder on my phone and cannot see one when connected to my computer.
I have reflashed to try to fix it, but no change. I found a thread where the suggested terminal commands but I would need to root my phone and I don't think that is something I should be doing. Any suggestions?
Click to expand...
Click to collapse
I think you can't access internal storage in case of encryption.
Google about decryption pros cons ... if you're fine with decryption check out dfe in our forum

Laptapper said:
I think you can't access internal storage in case of encryption.
Google about decryption pros cons ... if you're fine with decryption check out dfe in our forum
Click to expand...
Click to collapse
I read about that but I thought I'd see 0MB or weird filenames while looking at the filesystem in TWRP recovery and neither is the case. I did have to enter my password the first time I used TWRP and I have never been asked for it since.

31272809 said:
I read about that but I thought I'd see 0MB or weird filenames while looking at the filesystem in TWRP recovery and neither is the case. I did have to enter my password the first time I used TWRP and I have never been asked for it since.
Click to expand...
Click to collapse
Which recovery you've installed? Try newest orange fox

Laptapper said:
Which recovery you've installed? Try newest orange fox
Click to expand...
Click to collapse
So I had twrp 3.6_11-sweet installed. I just flashed Orange fox (the latest stable version) to recovery, and then I could no longer access recovery - it just restarted to flashboot. I had this problem when I tried to flash the Pixel Experience image too.
So I flashed TWRP to recovery again and everything is back to normal. But the problem is that I can’t use TWRP because there’s no folder installed.

31272809 said:
So I had twrp 3.6_11-sweet installed. I just flashed Orange fox (the latest stable version) to recovery, and then I could no longer access recovery - it just restarted to flashboot. I had this problem when I tried to flash the Pixel Experience image too.
So I flashed TWRP to recovery again and everything is back to normal. But the problem is that I can’t use TWRP because there’s no folder installed.
Click to expand...
Click to collapse
How you exactly flashed recovery?
Orange fox is working quite good....

Laptapper said:
How you exactly flashed recovery?
Orange fox is working quite good....
Click to expand...
Click to collapse
So I put the phone in fastboot mode -> connected to PC with usb -> check connection in cmd (fastboot devices) -> fastboot flash recovery "recovery_orange fox.img" -> power+up
And I get sent back to the fastboot screen
I must be doing something wrong but I have watched videos and read instructions and I don't know what it is.

31272809 said:
So I put the phone in fastboot mode -> connected to PC with usb -> check connection in cmd (fastboot devices) -> fastboot flash recovery "recovery_orange fox.img" -> power+up
And I get sent back to the fastboot screen
I must be doing something wrong but I have watched videos and read instructions and I don't know what it is.
Click to expand...
Click to collapse
Sounds ok
But without the quotes and no spaces, means change the file name like cmd:
fastboot flash recovery orangefox.img

Laptapper said:
Sounds ok
But without the quotes and no spaces, means change the file name like cmd:
fastboot flash recovery orangefox.img
Click to expand...
Click to collapse
I renamed the file but same result - it cycles through back to fastboot instead of recovery.
I don't understand. It's like it only accepts the twrp image, but even that doesn't install right.

31272809 said:
I renamed the file but same result - it cycles through back to fastboot instead of recovery.
I don't understand. It's like it only accepts the twrp image, but even that doesn't install right.
Click to expand...
Click to collapse
Please make a pc screenshot from flashing progress
You've switched on developer option usb debugging?

Laptapper said:
Please make a pc screenshot from flashing progress
You've switched on developer option usb debugging?
Click to expand...
Click to collapse
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.

31272809 said:
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.
Click to expand...
Click to collapse
Check out here
How to Enter Recovery Mode ? Volume Up and Power enabling Fastboot
Today I flashed EU RoM 13.0.4 to my Redmi Note 10 pro . Phone is working fine but I installed orange recovery and the process completed successfully on pc . When I press power and volume up it going to Fastboot mode instead of recovery mode. How...
forum.xda-developers.com
And take the files which there are downloadable
Try after flashing to boot via hardware keys and also via adb.
If both not working, I think you have to flash fastboot image via PC miflash and boot it to switch developer usb debugging on and restart to fastboot mode and flash twrp again.....

31272809 said:
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.
Click to expand...
Click to collapse
One more idea, before starting from scratch:
After flashing twrp disconnecting usb and then rebooting to recovery by pressing power and vol+ until you'll see the logo and feel the vibration

Why don't you test the recovery using fastboot boot? My recommendation is never to flash any recovery before successfully having it started manually once.
My personal approach is, never to install any recovery but only boot it in case it is needed. Disadvantage is that you need to be near a computer if you want to run it.

fastboot flash recovery twrp-3.6.0_11-0-sweet.img
fastboot boot twrp-3.6.0_11-0-sweet.img

Ashle said:
fastboot flash recovery twrp-3.6.0_11-0-sweet.img
fastboot boot twrp-3.6.0_11-0-sweet.img
Click to expand...
Click to collapse
Hi all, there's been some progress but I'd like your advice before continuing. I have my preferred ROM (Pixel Experience, zipped) copied to my SD card and I can see my SD card under Install option on TWRP. My phone data has been formatted (using the twrp Wipe option). Should I try installing from the SD card? I'm nervous since I know missing steps was warned against in the installation instructions.

1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Pixel Experience.zip
4. Reboot System

Ashle said:
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Pixel Experience.zip
4. Reboot System
Click to expand...
Click to collapse
Is 1 included in 2, or should I do something else as well?
If I'm okay to move to step 3, do I reboot to recovery or reboot into (hopefully) my new ROM?

Copy Pixel Experience.zip to sdcard
reboot to recovery
All over TWRP
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Install Pixel Experience.zip
4. Reboot System

Ashle said:
Copy Pixel Experience.zip to sdcard
reboot to recovery
All over TWRP
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Install Pixel Experience.zip
4. Reboot System
Click to expand...
Click to collapse
It didn't work.

Question Boot slot A keep rebooting

Hi.
So I recently found that my phone is using boot_b to boot up the phone, and I entered TWRP and change the boot solt to boot_a. In result, the device kept rebooting in the first page of boot (Powered by android page). And after I switch back to boot slot b the issue disappear. At first I thought the boot image was currupted and I flash the downloaded rom from xiaomirom.com and flash it using miflash via fastboot. The issue presists after flashing even without any modification (magisk/twrp/etc.). Then I thought that maybe the flash didnt include boot_a so I did:
`fastboot boot TWRP.img`
and then change the boot slot to boot_a and flashed again via fastboot. The issue still presists after that and now I have no idea what is wrong.
So I just want to ask that is anyone experiencing the same issue as me? And also how to fix the issue?
Thanks.

MiracleYueYue said:
Hi.
So I recently found that my phone is using boot_b to boot up the phone, and I entered TWRP and change the boot solt to boot_a. In result, the device kept rebooting in the first page of boot (Powered by android page). And after I switch back to boot slot b the issue disappear. At first I thought the boot image was currupted and I flash the downloaded rom from xiaomirom.com and flash it using miflash via fastboot. The issue presists after flashing even without any modification (magisk/twrp/etc.). Then I thought that maybe the flash didnt include boot_a so I did:
`fastboot boot TWRP.img`
and then change the boot slot to boot_a and flashed again via fastboot. The issue still presists after that and now I have no idea what is wrong.
So I just want to ask that is anyone experiencing the same issue as me? And also how to fix the issue?
Thanks.
Click to expand...
Click to collapse
Start by restoring the phone with this tool.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Then downloaded an old Xiaomi Eu rom fastboot.zip and installed it in fastboot mode (scrip included in the zip first install.bat).
Then install the Twrp and update via OTA.

NOSS8 said:
Start by restoring the phone with this tool.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Then downloaded an old Xiaomi Eu rom fastboot.zip and installed it in fastboot mode (scrip included in the zip first install.bat).
Then install the Twrp and update via OTA.
Click to expand...
Click to collapse
Hi. Thanks for your reply.
I have been used this tool to flash my phone. And I tested with another Xiaomi 12 Pro to make sure that the rom is correct. Turns out that the rom IS correct...

MiracleYueYue said:
Hi. Thanks for your reply.
I have been used this tool to flash my phone. And I tested with another Xiaomi 12 Pro to make sure that the rom is correct. Turns out that the rom IS correct...
Click to expand...
Click to collapse
I thought you want to install the TWRP to install a Xiaomi EU rom but maybe this is not the case.

The device is bought in china btw.

NOSS8 said:
I thought you want to install the TWRP to install a Xiaomi EU rom but maybe this is not the case.
Click to expand...
Click to collapse
No... I am just trying to slove the reboot issue with _a

MiracleYueYue said:
No... I am just trying to slove the reboot issue with _a
Click to expand...
Click to collapse
Dont relock the bootloader with Miflash.
Don't worry about the A/B slots.

NOSS8 said:
Dont relock the bootloader with Miflash.
Don't worry about the A/B slots.
Click to expand...
Click to collapse
I never lock the BL back.. lol
So the boot issue with _a doesn't matters? Dont know when the issue start but im pretty worried for the issue

MiracleYueYue said:
I never lock the BL back.. lol
So the boot issue with _a doesn't matters? Dont know when the issue start but im pretty worried for the issue
Click to expand...
Click to collapse
I also have this phone with TWRP, it seems to me that when I installed it I did not select any slot, by default it installs on A.

NOSS8 said:
I also have this phone with TWRP, it seems to me that when I installed it I did not select any slot, by default it installs on A.
Click to expand...
Click to collapse
Ummm I dont think we are on the same page.
I mean that if i change the boot slot to A in the Reboot secrion in TWRP the SYSTEM jams ans reboot when it tries to boot, and slot B boots normally.

MiracleYueYue said:
Ummm I dont think we are on the same page.
I mean that if i change the boot slot to A in the Reboot secrion in TWRP the SYSTEM jams ans reboot when it tries to boot, and slot B boots normally.
Click to expand...
Click to collapse
Why Install TWRP?
Use Miflash and that's it.

MiracleYueYue said:
Hi.
So I recently found that my phone is using boot_b to boot up the phone, and I entered TWRP and change the boot solt to boot_a. In result, the device kept rebooting in the first page of boot (Powered by android page). And after I switch back to boot slot b the issue disappear. At first I thought the boot image was currupted and I flash the downloaded rom from xiaomirom.com and flash it using miflash via fastboot. The issue presists after flashing even without any modification (magisk/twrp/etc.). Then I thought that maybe the flash didnt include boot_a so I did:
`fastboot boot TWRP.img`
and then change the boot slot to boot_a and flashed again via fastboot. The issue still presists after that and now I have no idea what is wrong.
So I just want to ask that is anyone experiencing the same issue as me? And also how to fix the issue?
Thanks.
Click to expand...
Click to collapse
Most probable reason is that you have previous version or ROM in slot A, while in slop B is the latest, one you are using. Same has happened to me. You can download recovery version of the ROM you are using and flash it in TWRP to slot A. I did that with Global ROM V13.0.7.0.SLBMIXM and now I have it on both slots working fine.

General Unofficial TWRP Image Leak

I have eagerly been waiting for the release of a TWRP image or MSM tool for this device, to no avail
I have seen on one of these posts, found here, a potentially working TWRP image.
Currently it is just the twrp.img without any zip
Directly download it here
As said below, this should be flashable within magisk to install
- I have NOT tested this personally
- I am not advising anybody try this image either
- Password decryption appears to not be functional
- This appears to only function on Android 13
sm8450 A13 Kernel Source Compile Issues
2023/02/16 UPDATE!!!! https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450/issues/4 if u want test it ---> https://github.com/negroni-development/oneplus-sm8450_t_13.0_10pro referenced by X5Pro based severecold's work.(compiles...
forum.xda-developers.com

It should be able to flash into magisk, but there is no guarantee that flashing into rom can enter the system

PlasmaTornado said:
I have eagerly been waiting for the release of a TWRP image or MSM tool for this device, to no avail
I have seen on one of these posts, found here, a potentially working TWRP image.
Currently it is just the twrp.img without any zip
- I have NOT tested this personally
- I am not advising anybody try this image either
- Password decryption appears to not be functional
- This appears to only function on Android 13
sm8450 A13 Kernel Source Compile Issues
2023/02/16 UPDATE!!!! https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450/issues/4 if u want test it ---> https://github.com/negroni-development/oneplus-sm8450_t_13.0_10pro referenced by X5Pro based severecold's work.(compiles...
forum.xda-developers.com
Click to expand...
Click to collapse
we need testers

TrajanoX3 said:
we need testers
Click to expand...
Click to collapse
Agreed. I'm sure there are some people willing to give it a shot.
I haven't flashed an image since split partitions has existed, which is a fairly long time now
Even with the OP10, I am still unrooted. TWRP provides just that extra bit of security to me

I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.

Canuck Knarf said:
I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.
Click to expand...
Click to collapse
Fantastic! Can you confirm that it can decrypt without any issues?

Its working good

Canuck Knarf said:
I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.
Click to expand...
Click to collapse
we donate screenshot

heres recovery log from TWRP

Canuck Knarf said:
heres recovery log from TWRP
Click to expand...
Click to collapse
Are you using twrp right now?

TrajanoX3 said:
Are you using twrp right now?
Click to expand...
Click to collapse
Yes

Canuck Knarf said:
Yes
Click to expand...
Click to collapse
Can you send us a screenshot of twrp?

Canuck Knarf said:
Sim
Click to expand...
Click to collapse
Thanks for the screenshots, did you flash magisk through twrp?

Canuck Knarf said:
Yes
Click to expand...
Click to collapse
Magisk installation working probably by twrp?

just installed Magisk

TrajanoX3 said:
we donate screenshot
Click to expand...
Click to collapse
then install and flash partition A and then partition B and relapse to recovery?

Yes
fastboot flash recovery_a then fastboot flash recovery_b then reboot to recovery from fastboot . then change language ...cause its in Chinese

Oh and Twrp works with screen password lock so no need to disable it

Canuck Knarf said:
Oh and Twrp works with screen password lock so no need to disable it
Click to expand...
Click to collapse
how do you operate

Beware, this twrp.img is not bootable. Command fastboot boot twrp.img won't work, you will get bootloop into OP logo. Rebooting into fastboot mode and doing fastboot boot stockboot.img will help.
So it means you can only flash it directly. Confirmed by me and three others.