Develop Bugs

Accidentally locked bootloader

Alright guys, I was trying to fix my fingerprint (which I ended up doing) by flashing the global dev ROM 7.8.31 via fastboot with the miflash tool but I accidentally locked the bootloader while doing so. My phone came with the bootloader unlocked and now I can no longer unlock the bootloader. in developper options, the OEM unlocking option is enabled but no matter what I do in fastboot, the process simply does not work. I get the remote token verification has failed message. I have tried every freakin guide out there but my phone now refuses to get unlocked. I can't flash anything with miflash tool anymore, it just says failed, even when trying to flash the global dev 7.8.31 ROM. Anyone can help me here? Xiaomi says my device is unsupported for unlocking yet it was unlocked from the start........

What i did was the official unlock guide from xiaomi where you will get the code from them. Sadly you have to wait for 3days to be able to unlock them again.

Well check this thread...
en.miui.com/thread-781303-1-1.html
You can reapply if you got rejected

blaspheme000 said:
What i did was the official unlock guide from xiaomi where you will get the code from them. Sadly you have to wait for 3days to be able to unlock them again.
Click to expand...
Click to collapse
Well I did that but it kept on saying I had too many IP requests of sorts but I used TunnelBear and set my location to Hong Kong and that allowed me to bypass that and the request was passed through. Surprisingly, I got a message 4 hours later that said I was able to unlock it instead of the 2-7 days it took for most people to get theirs

Same happened to me. I re-lock bootloader to install android pay, and bricked my phone.
Have to reboot in EDL mode (after >50 tries) and flash again.
But... Flashed a locked bootloader version, so i have to request for official unlock (phone came unlocked)
Now I have unlocked bootloader, with Magisk and Safety Net module with Android Pay working fine.
PS: i also had the IP problem. Used a Chinese proxy to override restriction.

I am bricked my phone

hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,?

[email protected] said:
hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,
Click to expand...
Click to collapse
bootloader unlock code different from frp unlock code.
installing other device firmware has chance to replace oeminfo.img partition. Changing this partitin often causes locked frp.
If lucky you can wipe from the erecovery that is loading. maybe even couple times. Then maybe it will boot. Other that that there has been no public mention of any fix.

do your best to fix it using hisuite or other methods if you can. if you have twrp that can help if you have stock recovery and locked frp your only hope might be hisuite and if that fails you will need a paid option like dc-phoenix or funkyhuewei. i only have experience with dc-phoenix, and it did fix my locked frp completely bricked phone, but i read that funky also works well but is nearly 3 times as expensive. (15€ vs 50€)

[email protected] said:
hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,?
Click to expand...
Click to collapse
Hello friend i had done the same i installed L21 firmware from firmwarefinder to my BND-AL10 and same happened my phone was bricked it was directly taking me to the stock recovery but my bootloader was locked and lucky i had Kept my bootloader unlock code with me when the site was up so when i unlocked my bootloader it did factory reset and booted normally and Oreo was installed but the only problem im facing is my build number is still showing the old one which is BND-AL10C675 B161 and i don't have face unlock and ride mode which comes with Oreo i had face unlock with BND-AL10C675 B161 . My frp was unlocked already .

sygladiator said:
Hello friend i had done the same i installed L21 firmware from firmwarefinder to my BND-AL10 and same happened my phone was bricked it was directly taking me to the stock recovery but my bootloader was locked and lucky i had Kept my bootloader unlock code with me when the site was up so when i unlocked my bootloader it did factory reset and booted normally and Oreo was installed but the only problem im facing is my build number is still showing the old one which is BND-AL10C675 B161 and i don't have face unlock and ride mode which comes with Oreo i had face unlock with BND-AL10C675 B161 . My frp was unlocked already .
Click to expand...
Click to collapse
The displayed build number comes from the data part of the update. (Update_*hw_*.zip)
If you reflash again all three files , might be fixed

mrmazak said:
The displayed build number comes from the data part of the update. (Update_*hw_*.zip)
If you reflash again all three files , might be fixed
Click to expand...
Click to collapse
How should i reflash it , can you please provide me the procedure to do so , it would be very helpfull

sygladiator said:
How should i reflash it , can you please provide me the procedure to do so , it would be very helpfull
Click to expand...
Click to collapse
If flashing again is the answer to solve problem. Use my guide here.
You are on Oreo now so use the top portion. "Flash update"
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649

mrmazak said:
If flashing again is the answer to solve problem. Use my guide here.
You are on Oreo now so use the top portion. "Flash update"
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
Click to expand...
Click to collapse
It all goes above my head , what exactly i have to do please elaborate .

sygladiator said:
It all goes above my head , what exactly i have to do please elaborate .
Click to expand...
Click to collapse
I don't want to sound like rude or anything.
But I put it all pretty simple, I thought. Like 4 steps
Download files
Put files on SD card
Install twrp
Install file I shared
If that is over your head, maybe you should not have modify and phone.

mrmazak said:
I don't want to sound like rude or anything.
But I put it all pretty simple, I thought. Like 4 steps
Download files
Put files on SD card
Install twrp
Install file I shared
If that is over your head, maybe you should not have modify and phone.
Click to expand...
Click to collapse
Sorry for silly questions by the way thankyou for your help
There is no other options to install other than installing through twrp???
Will i get OTA updates of my bootloader is unlocked ??
If not then i vl be happy to install RROS 8.1 coz am on oreo that means i have treble support so i can just install it
So far so good

sygladiator said:
Sorry for silly questions by the way thankyou for your help
There is no other options to install other than installing through twrp???
Will i get OTA updates of my bootloader is unlocked ??
If not then i vl be happy to install RROS 8.1 coz am on oreo that means i have treble support so i can just install it
So far so good
Click to expand...
Click to collapse
I know each device has it's own proceedure to, flash and all, and they are similar but different.
So can be confussing

Soft-bricked 7X (BND-AL10)

I was on rooted Stock, when I got a System update available prompt.
I uninstalled Magisk, Flashed stock recovery and did a Factory reset from the Stock recovery.
It booted up, but there was no Keyboard installed. I think, I had uninstalled the pre-installed one when I was rooted.
I couldn't get past the Setup Wizard, as the FRP was Locked and there was no way of typing the password.
I tried to flash the system.img from fastboot but it gave me 'Remote: command not allowed' error. (Even for flashing recovery)
I google'd a bit and ended up on a solution as to relock the bootloader, Turn on OEM Unlocking and lock the bootloader again.
I relocked the bootloader, it did a 'Low-level factory reset' and now the phone is even bootloop. (it boots into eRecovery from the Honor/Huawei logo)
I tried the 'Download latest version and recovery' from eRecovery. It's giving me 'Package verification failed' error.
'dload' method never worked for me, and it is still the same.
I am able to access:
fastboot: currently useless as Bootloader is re-locked and OEM Unlocking was turned off when I did a factory reset
eRecovery: 'Download latest version/recovery' and 'Factory Reset' doesn't work.
Stock recovery: 'Factory Reset' doesn't work.
Any solution/suggestion?

Honor 7x OFFICIAL Dev Hub
Official Dev & OT group for Honor 7x
If you are a Dev and wants to contribute and discuss, ask admins for Dev group link
Join Honor 7X ROM and Other Updates channel here
MOD EDIT: LINK REMOVED
Per the forum rules:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Try here
Sent from my BND-L21 using Tapatalk

I sent my phone to service center. They couldn't fix it through any software tool so they had to replace the SoC.
This basically comes down to the Treble version that Huawei is using. They should have stuck with the Google Implementation of Treble instead of customizing it. Stock Android implementation is very robust. Companies like Motorola, Nokia, OnePlus benefits a lot because of that.
Anyway, they did not charge me anything and I even got the phone back in time to get the New unlock code.
Sad to say that am not gonna unlock this device untill they fix the issue of partitions getting corrupt when you re-lock the device running Oreo.
Stopping the bootloader unlock code service makes sense now. Their implementation is flawed.

TWRP S965F Install Question with a slight twist

Hey all,
Sorry, I know that has been covered extensively on here, but I just want to clarify my understanding and make sure I'm not waiting pointlessly and hopefully avoid mucking this up in the future.
So, I've had my Galaxy S9+ long enough that OEM UNLOCK appeared in the developer options menu. I've rooted/flashed installed enough phones in the past that I stupidly didn't read up on any of the newer security features (such as RMM).
I OEM unlocked the phone, restarted, and everything looked fine. I've then rebooted into Odon (3.13.1, downloaded through Sam Mobile) and tried to install the tar file associated with my phone (twrp-3.2.3-0-star2lte).
Odin failed to install, with the error message, "only official released binaries are allowed to be flashed(recovery)" After a quick look around, this error message appears to be associated with a bootloader that is still locked:
If I look at the values at the top of the download menu, I see
RMM STATE: Prenormal
FRP LOCK: Off
OEM LOCK: Off
So, if my OEM lock is off, is it the RMM state preventing me from flashing the device? If so, is this a wait seven days without restarting the phone for RMM state to change to normal or am I missing something entirely?
What I've also read, is it is required to do the TWRP flash mid-OEM unlock (during the reboot of the factory reset), is this something I will still need to do?
Any direction appreciated. Sorry for posting on the same subject so many others have, I just can't quite find any information on it when the OEM is unlocked already.
ta.

jusx10i said:
Hey all,
Sorry, I know that has been covered extensively on here, but I just want to clarify my understanding and make sure I'm not waiting pointlessly and hopefully avoid mucking this up in the future.
So, I've had my Galaxy S9+ long enough that OEM UNLOCK appeared in the developer options menu. I've rooted/flashed installed enough phones in the past that I stupidly didn't read up on any of the newer security features (such as RMM).
I OEM unlocked the phone, restarted, and everything looked fine. I've then rebooted into Odon (3.13.1, downloaded through Sam Mobile) and tried to install the tar file associated with my phone (twrp-3.2.3-0-star2lte).
Odin failed to install, with the error message, "only official released binaries are allowed to be flashed(recovery)" After a quick look around, this error message appears to be associated with a bootloader that is still locked:
If I look at the values at the top of the download menu, I see
RMM STATE: Prenormal
FRP LOCK: Off
OEM LOCK: Off
So, if my OEM lock is off, is it the RMM state preventing me from flashing the device? If so, is this a wait seven days without restarting the phone for RMM state to change to normal or am I missing something entirely?
What I've also read, is it is required to do the TWRP flash mid-OEM unlock (during the reboot of the factory reset), is this something I will still need to do?
Any direction appreciated. Sorry for posting on the same subject so many others have, I just can't quite find any information on it when the OEM is unlocked already.
ta.
Click to expand...
Click to collapse
I'd love any info on this as well.

Unfortunately, I just had to wait the week.
I will say though when you come to install TWRP make sure you follow the instructions. I didn't, then I had to wait another week for the OEM Unlock to re-appear again!

Question Bootloop to fastboot logo and back in lock state

Hi everybody,
yesterday I tried flashing the stock pocof3 rom back onto my phone, but since it got stuck in a bootloop at the fastboot logo. Showing the poco logo for a milisecond and then straight to fastboot..
(before this I flashed twrp and the arrowOS recovery and images a few time trying, without succes, to install this rom)
Last thing I did was flash via the mi-flash tool and did't see the "clean and lock" selection so it's also in lock state again.
I cant get adb to find the phone although the mi-flashtool is finding it.
anyone any tips?
I tried the vol up power trick, but this didn't help, keeps loading into fastboot

Did Mi Flash give an error message after trying to flash?

dreamytom said:
Did Mi Flash give an error message after trying to flash?
Click to expand...
Click to collapse
I dont recall giving an error, so i dont think so
now it is though, when trying to flash the firmware. error erasing boot_ab (failed: erase not allowed in lock state)

Kaayman said:
I dont recall giving an error, so i dont think so
now it is though, when trying to flash the firmware. error erasing boot_ab (failed: erase not allowed in lock state)
Click to expand...
Click to collapse
I'm not sure, but you may still be able to flash official ROMs.
But in "Configuration" make sure Erase is disabled

Kaayman said:
I dont recall giving an error, so i dont think so
now it is though, when trying to flash the firmware. error erasing boot_ab (failed: erase not allowed in lock state)
Click to expand...
Click to collapse
BAD NEWS... your Poco is bricked. You cannot flash ANYTHING using a PC when your bootloader is locked.
(I did same thing on a Mi11 5g last week and ended up selling it on eBay for spare & repairs
I tried sideload flash, miflash, copying update.zip to internal storage via ADB, and many other options - all without success).
- if your POCO is under warranty in your country (i.e. not a chinese import)... contact Xiaomi Support they can re-flash correct ROM
- Ask your local phone repair store... they *might* be able to flash original ROM back by using "Chimera" engineering software.

dreamytom said:
I'm not sure, but you may still be able to flash official ROMs.
But in "Configuration" make sure Erase is disabled
Click to expand...
Click to collapse
this doesn't seem to be an option. there is a checkbox with "erase all" but all are already unchecked

dezborders said:
BAD NEWS... your Poco is bricked. You cannot flash ANYTHING using a PC when your bootloader is locked.
(I did same thing on a Mi11 5g last week and ended up selling it on eBay for spare & repairs
I tried sideload flash, miflash, copying update.zip to internal storage via ADB, and many other options - all without success).
- if your POCO is under warranty in your country (i.e. not a chinese import)... contact Xiaomi Support they can re-flash correct ROM
- Ask your local phone repair store... they *might* be able to flash original ROM back by using "Chimera" engineering software.
Click to expand...
Click to collapse
This is what I feared already..

Kaayman said:
This is what I feared already..
Click to expand...
Click to collapse
- Bootloader was re-locked whilst a custom ROM was in the phone.
(MIUI with Locked bootloader will not boot up where ROM is not stock or does not match the region/product code).
You cannot apply for bootoader unlock because you cannot boot up into Android and request the unlock via Developer mode.
You cannot remotely (via PC cable) flash any ROM into a Xiaomi / POCO phone whilst botloader is locked.
You are in a chicken and egg situation.,,, but if you find a way to repair your phone, please let us know how you achieved it.
Good luck!

If the system hasn't booted up yet there is a chance that you will be able to unlock bootloader again. Try it.

mar.ur said:
If the system hasn't booted up yet there is a chance that you will be able to unlock bootloader again. Try it.
Click to expand...
Click to collapse
That's what I'm thinking too ...
Connect the phone to pc and do the bootloader unlock again via the mi unlock app - you don't need to apply again and stuff as long as you're able to recognise the phone inside app correctly

Rstment ^m^ said:
That's what I'm thinking too ...
Connect the phone to pc and do the bootloader unlock again via the mi unlock app - you don't need to apply again and stuff as long as you're able to recognise the phone inside app correctly
Click to expand...
Click to collapse
thanks everyone for all the replies!
tried unlocking it via the mi unlock tool (latest) but it says (in chinese) its locked by nr 123***456 by searching the phone - can't unlock
edit:
google lens translates:
X The phone has been locked by the account number 661****647 by searching the phone, Can't unlock
but it's not the nr. of my account..

dezborders said:
- Bootloader was re-locked whilst a custom ROM was in the phone.
(MIUI with Locked bootloader will not boot up where ROM is not stock or does not match the region/product code).
You cannot apply for bootoader unlock because you cannot boot up into Android and request the unlock via Developer mode.
You cannot remotely (via PC cable) flash any ROM into a Xiaomi / POCO phone whilst botloader is locked.
You are in a chicken and egg situation.,,, but if you find a way to repair your phone, please let us know how you achieved it.
Good luck!
Click to expand...
Click to collapse
Is it not even possible to flash Official ROMs?
Isn't there like a system that it checks the signature of the ROM and if it's a signed ROM it allows the flash? Or am I mistaken?

dreamytom said:
Is it not even possible to flash Official ROMs?
Isn't there like a system that it checks the signature of the ROM and if it's a signed ROM it allows the flash? Or am I mistaken?
Click to expand...
Click to collapse
Nope bootload locked = no 'remote' flashes via pc
Apparently there is an 'authenticated user' mode for Xiaomi engineers in MiFlaah and also an EDL Emergency Download Mode which you can trigger by shorting out 2 pins on the motherboard so bypass bootloader lock and flash any ROM
Neither were available options for me

dezborders said:
Nope bootload locked = no 'remote' flashes via pc
Apparently there is an 'authenticated user' mode for Xiaomi engineers in MiFlaah and also an EDL Emergency Download Mode which you can trigger by shorting out 2 pins on the motherboard so bypass bootloader lock and flash any ROM
Neither were available options for me
Click to expand...
Click to collapse
I also tried to simulate a local OTA by copying update.zip to internal storage using ADB push command and booting into recovery mode to flash ... But it doesn't work for me

dezborders said:
Nope bootload locked = no 'remote' flashes via pc
Apparently there is an 'authenticated user' mode for Xiaomi engineers in MiFlaah and also an EDL Emergency Download Mode which you can trigger by shorting out 2 pins on the motherboard so bypass bootloader lock and flash any ROM
Neither were available options for me
Click to expand...
Click to collapse
I'm now in the procedure to sent it back under warranty. any idea if this is possible and what the cost would be if not under warranty?
If all fails i'll try the shorting by pins, should be interesting

I think a warranty repair claim is your best bet ... I have never read anywhere that unlocking bootloader invalidates Xiaomi warranty (Unlike Samsung and so many other brands!)
If warranty repair is re refused try a few independent repair shops
Last resort is get the back cover off the phone and short out the EDL pins
Good luck!
Let us know if you manage to get your phone booting up again

See this thread (last post) for a possible workaround via a 3rd party recovery image to flash EU rom
[Solved] Stuck in fastboot with locked bootloader
HI there! After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it...
forum.xda-developers.com

Kaayman said:
I'm now in the procedure to sent it back under warranty. any idea if this is possible and what the cost would be if not under warranty?
If all fails i'll try the shorting by pins, should be interesting
Click to expand...
Click to collapse
I once hardbricked (complete blackscreen, not even Fastboot reachable) a Poco F3.
I requested a replacement from Amazon and that worked.
I said a software update bricked it.
Of course having to do that is really bad, but I was scared of opening the back.

dezborders said:
See this thread (last post) for a possible workaround via a 3rd party recovery image to flash EU rom
Bootloop to fastboot logo and back in lock state
Hi everybody, yesterday I tried flashing the stock pocof3 rom back onto my phone, but since it got stuck in a bootloop at the fastboot logo. Showing the poco logo for a milisecond and then straight to fastboot.. (before this I flashed twrp and...
forum.xda-developers.com
Click to expand...
Click to collapse
You pasted the current thread, do you have the link to the thread you meant?

Kaayman said:
You pasted the current thread, do you have the link to the thread you meant?
Click to expand...
Click to collapse