Develop Bugs

How exactly does one flash a ROM with Anti-Rollback?

Accidentally updated to MIUI 10, two days before I could finally unlock my phone and now I'm stuck here with an Anti-Rollback enabled phone. Does that make flashing a ROM any harder? I just want to use Pixel Experience or so, can't stand MIUI any longer.

Der Namenlose Held said:
Accidentally updated to MIUI 10, two days before I could finally unlock my phone and now I'm stuck here with an Anti-Rollback enabled phone. Does that make flashing a ROM any harder? I just want to use Pixel Experience or so, can't stand MIUI any longer.
Click to expand...
Click to collapse
you can flash any custom rom!
i am using CRDROID 5.0 , i have flashed miui10 before and didn't like it !

my phone had it enabled and I was able to flash two custom roms without issue. Very straight forward once bootloader unlocked.
Only thing I don't seem to be able to do is retain TWRP as a recovery, even after flashing the lazy flasher file. but can boot to twrp recovery with fastboot command so just give it a go and see how you get on.

After flash the Phone doesn't Boot anymore

Hi there,
I've tried to flash my phone.
At first I've flashed the China Version Miui Beta 12.5 and it runs.
Then I've tried to flash MiuiPlus and when it starts to boot into the Rom, there comes the MiuiPlus and it didn't boot completely.
Then I've tried to flash an other Europe Miui 12.5 and after flash I did a start into the system from TWRP.
It shut down and then I saw half a second, the Display shows a little light, then it turns of.
This happens also when I wants tot start into Recovery and when I plug it on.
When I wants to start it into Fastboot Mode, there is just have a second the Fastboot Symbol, then it turns off.
Can somebody help me?
Is this a brick?
Thks. for every try to help me

Do you unlock your phone?
In case of brick, you will need to flash in QCOM mode, but that is limited to only a few service center, officially. But thanks to recent discovery, it isn't necessary. Here is how you bypass the security measures and flash your device via SPFT. If you are on latest windows 10, you will need to install the microsoft store version of python instead, and then install the necessary libraries manually.

Question Bricked Poco F3 Global.

I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.

Did you read any tutorial? For which reason you flash 12.0.3?

Looks like you triggered anti-rollback protection. Read here https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
You cannot install previous versions of miui.
If by some chance the phone still boots to fastboot mode, try to install the LATEST firmware for your phone via mi flash tool (make sure you check "clean all" option and NOT the "clean all and lock" which is default in the flash tool).
And no, you cannot use EDL with this phone. EDL is locked to regular users and can only be accessed by an authorized account.

If you ca access fastboot and the device is recognized by you computer in fastboot mode then you can flash Miui using MiFlash.EDL mode is when you dont have access to fastboot.
Read tutorials about flashing miui using miflash on youtube.

brescianienea said:
I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.
Click to expand...
Click to collapse
If u are in fastboot mode, install this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file. extract and launch the exe, click on install. wait a pop-up in chinese and close all. Then re-try to re flash the EEA (in CLEAN ALL) with this mi flash. Tell me if all works

X0PIRAT3 said:
If u are in fastboot mode, install this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file. extract and launch the exe, click on install. wait a pop-up in chinese and close all. Then re-try to re flash the EEA (in CLEAN ALL) with this mi flash. Tell me if all works
Click to expand...
Click to collapse
Or install via any mi flash lol.
It sounds like normal thing...
Cross flashing global/EEA tends to fail for whatever reason ( Super doesn't flash correctly ) and you get stuck bootlooping or straight towards fastboot depending on how far the super flashed...
Go back to global ROM and sit there. It should flash alright.
Idk why it does this ... Something is not alright with this phone

{Mod edit: Quoted post has been deleted}
Yes it's always 604 or 606 seconds for mi flash no matter how good your PC is either because I have a good one it should be like 2 minutes.
Wtf? What do you guys mean edl mode you don't boot into edl mode that requires you to take the back off and jump it with wires or something. You boot into fastboot mode like you did to unlock bootloader and flash with miflash and you don't go from 12.5.6 to 12.0.3 normally downgrading will brick your device. Where the f did you get all of this from. If you can boot back into fastboot mode volume down and power key until it boots into fastboot than reflash the last working firmware you had with miflash and look at the video. I don't understand what all the countries believe they can do with a phone edl mode is like OEM type fixes not some kid on Xda

brescianienea said:
I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.
Click to expand...
Click to collapse
Yes it's always 604 or 606 seconds for mi flash no matter how good your PC is either because I have a good one it should be like 2 minutes.
Wtf? What do you guys mean edl mode you don't boot into edl mode that requires you to take the back off and jump it with wires or something. You boot into fastboot mode like you did to unlock bootloader and flash with miflash and you don't go from 12.5.6 to 12.0.3 normally downgrading will brick your device. Where the f did you get all of this from. If you can boot back into fastboot mode volume down and power key until it boots into fastboot than reflash the last working firmware you had with miflash and look at the video. I don't understand what all the countries believe they can do with a phone edl mode is like OEM type fixes not some kid on Xda
You can always tell your on Xda when they offer help that is 1 link and try this is the only information they give. The reason you screwed up is because lazy people that don't leave full instructions. You never never never never need to worry about edl mode. Fast boot or bootloader mode as it's called is how you restore a soft bricked phone what did you do with edl mode I don't even understand what you tried to do.

brescianienea said:
I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.
Click to expand...
Click to collapse
You thought this is something you needed to do? Edl mode is nothing that a regular soft brick would require

Here's another one edl mode I can't understand why you or anyone else would think this is how we restore a soft bricked phone lol this would be crazy I would be done. Your not even close to the first person to say this. Same with battery backup that doesn't make sense it's not battery backup you don't backup your battery it's battery life

Question Revert back to Stock OOS

Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!

You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/

Salilsarkar said:
You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Click to expand...
Click to collapse
Many thanks! I was having issues downloading the stock firmware files needed for the MSM tool. I do have the downgrade zip and ota signed zip for my model, but extracting with payload dumper gives me only 7 image files so I think it's incomplete, and I would still need to download the full firmware files to be able to flash via fastboot.

If you try using fastboot to downgrade, you're very likely going to brick and have to use the MSM anyway.

blitzkriegger said:
Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!
Click to expand...
Click to collapse
I was able to flash to oos11 using twrp. Well, I was on crdroid and there are custom ROMs that require oos12 before It will work. So I went crdroid 8.6 to oos11 to oos 12 and then lineage 19

Well it was a ride for me lol. Took me a few hours to realize I can gain fastboot access via long pressing power button+volume up and volume down altogether. I was then able to reflash the modded magisk boot image to regain access to AOSPA.
The fun part came after trying to flash back to stock via MSM. First I figured out that instead of using the "vol up+vol- button approach then connect usb" way of trying to get MSM tool to connect to the EDL mode of the phone, an easier method is to use "ADB reboot edl" command.
Now as I previously used global stock OOS, I mistakenly used the MSM tool for the global region. However, this got me in a SHA-256 mismatch in the flashing process, causing a flash error which got me back to getting stuck at the bootloader again. Turns out the global MSM tool does not work for LE2120 model.
So at this point I had 2 options - either find a MSM tool that works, or try flashing back to stock via fastboot. The fastboot way would have worked but I ran into a problem - you have to flash to .img files partly via fastboot, then partly via fastbootd. And when on fastbootd my phone is not recognized by the PC (this is why trying to flash back AOSPA also failed, it can't continue the fastbootd part of the install as for some reason my pc loses connection with the phone on fastbootd).
My saving grace was I found out that for LE2120, the EU version of the MSM tool works. So long-story short I got back to stock OOS 12 again. It was a fun yet nerve wracking experience, and I learned a lot.
So the lesson of the story is, for anyone tinkering with this device, to learn the basics, from knowing your correct model number, knowing the proper button combinations to boot to fastboot/edl/recovery, knowing which tools to use, to knowing how to setup/troubleshoot your pc to ensure the phone communicates properly at every step!

Question OnePlus 9 Pro: Unlocked, but unable to boot into recovery

Hi,
my LE2123 OnePlus 9 Pro is successfully resisting a boot into the recovery. This is not the first phone I flashed, but this time I am a little out of luck and ideas what to do next. Maybe someone would have an idea on what's going wrong - already many thanks in advance.
It's a Model LE2123 with OOS 11.2.2.2.LE15BA7.
As I got it, I did the following:
OEM Unlock
Reboot into Bootloader
fastboot boot twrp-installer-3.6.2_11-0-lemonadep.zip
TWRP puts the device into the "Fastboot Mode" Screen (the on with the icon in the middle) and that's it. Trying other recoveries, like from e.OS (recovery-e-1.1-r-20220629200015-dev-lemonadep.img), this make the phone boot OOS right away.
With that being unsuccessful, I reverted back to stock OOS 11.2.2.2 going through EDL and MsmDownloadTool V4.0.exe, pushing "rev_OverSeas_210324_2236_release_OTA-BLOCK_Signed_fp2103242236_cve2021-03-01_ufs_Oxygen-OS-11.2.2.2.LE15BA" from the forum here on it (Kudos!).
That I updated to OOS 11.2.10.10 through a local system update (using OnePlus9ProOxygen_22.E.13_OTA_0130_all_2111112110_a28e911b11ec5.zip from here as well. Kudos again!).
After that I tried the various recoveries available (twrp-installer-3.6.2 (no other version), e.os recovery (all available), lineageOS recovery (both 18.1 available)). But all of the fail to boot, same as before: TWRP does not start, e.OS and lineageOS recovery hang shortly, then boot the OS (which then takes like 3 minutes to boot, but does so successfully).
So I am right out of clues. If anyone would have an advice what else I could try - greatly appreciated!
Many thanks for your help.

Mjammjam said:
Hi,
my LE2123 OnePlus 9 Pro is successfully resisting a boot into the recovery. This is not the first phone I flashed, but this time I am a little out of luck and ideas what to do next. Maybe someone would have an idea on what's going wrong - already many thanks in advance.
It's a Model LE2123 with OOS 11.2.2.2.LE15BA7.
As I got it, I did the following:
OEM Unlock
Reboot into Bootloader
fastboot boot twrp-installer-3.6.2_11-0-lemonadep.zip
TWRP puts the device into the "Fastboot Mode" Screen (the on with the icon in the middle) and that's it. Trying other recoveries, like from e.OS (recovery-e-1.1-r-20220629200015-dev-lemonadep.img), this make the phone boot OOS right away.
With that being unsuccessful, I reverted back to stock OOS 11.2.2.2 going through EDL and MsmDownloadTool V4.0.exe, pushing "rev_OverSeas_210324_2236_release_OTA-BLOCK_Signed_fp2103242236_cve2021-03-01_ufs_Oxygen-OS-11.2.2.2.LE15BA" from the forum here on it (Kudos!).
That I updated to OOS 11.2.10.10 through a local system update (using OnePlus9ProOxygen_22.E.13_OTA_0130_all_2111112110_a28e911b11ec5.zip from here as well. Kudos again!).
After that I tried the various recoveries available (twrp-installer-3.6.2 (no other version), e.os recovery (all available), lineageOS recovery (both 18.1 available)). But all of the fail to boot, same as before: TWRP does not start, e.OS and lineageOS recovery hang shortly, then boot the OS (which then takes like 3 minutes to boot, but does so successfully).
So I am right out of clues. If anyone would have an advice what else I could try - greatly appreciated!
Many thanks for your help.
Click to expand...
Click to collapse
Alright, so this is what you're going to want to do (please tell me if you attempted this)
1. MSM back to stock, then unlock bootloader
2. Update to 11.2.10.10, then flash recovery (make sure you do fastboot flash boot lineage.img from bootloader, not fastbootd)
3. Then, make sure you type "fastboot reboot recovery"
It should work after that.

Thanks for your reply razor.
I did it similarly, but not identical:
- Instead of flashing the recovery, I just booted into it. (fastboot boot .\lineage-18.1-20220524-recovery-lemonadep.img). In the past this had always worked out as a good way to try it out first.
- I did not not to fastboot reboot recovery, as that happened automatically when fastboot boot was done.
The phone is right now still on 11.2.10.10. It was flashed back to stock 11.2.2.2 using MSM and then from android settings locally updated to 11.2.10.10.
So right now I could go ahead and do as you said:
- fastboot flash boot lineage.img: Which recovery should I use? LineageOS proposes to match it with the Android version, so that should be LOS 18.1: lineage-18.1-20220524-recovery-lemonadep.img ?
- fastboot reboot recovery (I guess that will happen automatically again)
Thanks!
One thing that I checked is that slot B seems to be all empty right now. Setting this as active goes into bootloader right away. Maybe that confuses the recovery.

I managed to get into recovery now, fastboot using twrp.img word.
fastboot boot twrp-3.6.2_11-0-lemonadep.img
With both of these I had no luck getting into recovery, instead they start into OOS right away:
fastboot boot recovery-e-1.1-r-20220629200015-dev-lemonadep.img
fastboot boot lineage-18.1-20220524-recovery-lemonadep.img
LE2123 with OOS 11.2.10.10.LE15BA