Develop Bugs

Can't unlock bootloader on N5X

Hello guys I try 10 times unlock my N5X bootloader and nothing happened after everything. I am using NRT method. I have developer options enabled and oem unlock turned on. Phone is going to bootloader mode I tap on screen when I choose if I want to unlock and after all procedure device has wiped data because I have to set my language etc. etc. but when I want to root it in bootloader mode system show BOOTLOADER: locked. I posted screen. What am I doing wrong. Thx for helping!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Blacknighter said:
Hello guys I try 10 times unlock my N5X bootloader and nothing happened after everything. I am using NRT method. I have developer options enabled and oem unlock turned on. Phone is going to bootloader mode I tap on screen when I choose if I want to unlock and after all procedure device has wiped data because I have to set my language etc. etc. but when I want to root it in bootloader mode system show BOOTLOADER: locked. I posted screen. What am I doing wrong. Thx for helping!
Click to expand...
Click to collapse
Did you flash twrp?
I reccomend you start from scratch using this guide:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Doing it all manually gives you a way better understanding of what you are doing than using a toolkit.

Bro I can't unlock bootloader, so how can I install TWRP? What is this secure boot: enabled , what does NO RPMB mean?

Blacknighter said:
Bro I can't unlock bootloader, so how can I install TWRP? What is this secure boot: enabled , what does NO RPMB mean?
Click to expand...
Click to collapse
Just trying to help. Chill a bit please. The second part of your story isn't all that clear.
Let's take a few steps back. Do you have fastboot access working?

Yes, when I connect phone to PC in fastboot pc see my phone.

Blacknighter said:
Yes, when I connect phone to PC in fastboot pc see my phone.
Click to expand...
Click to collapse
And you tried the manual steps in Heisenbergs guide?
Mainly:
Fastbbot devices (check serial)
Fastboot OEM unlock
Fastboot reboot
If that doesn't work there's probably something wrong in your initial setup.

When I wrote command fastboot devices I don't saw serial ... so problem is here. What to do?

Blacknighter said:
When I wrote command fastboot devices I don't saw serial ... so problem is here. What to do?
Click to expand...
Click to collapse
My guess is not all required software is installed correctly.
As I said start from scratch using the guide I mentioned.

On third PC I get the sam result - when I fastboot oem unlock, I will see the lock state change to unlock, but then when I execute fastboot reboot-bootloader, the lock state after reboot will show locked.

Blacknighter said:
On third PC I get the sam result - when I fastboot oem unlock, I will see the lock state change to unlock, but then when I execute fastboot reboot-bootloader, the lock state after reboot will show locked.
Click to expand...
Click to collapse
What if you flash TWRP before executing "fastboot reboot-bootloader". Does it work?

C:\SDK\platform-tools>fastboot devices
0140998a5ec096e4 fastboot
C:\SDK\platform-tools>fastboot oem unlock
...
OKAY [ 3.972s]
finished. total time: 3.972s
C:\SDK\platform-tools>fastboot flash recovery twrp_bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16325 KB)...
OKAY [ 0.590s]
writing 'recovery'...
OKAY [ 0.100s]
finished. total time: 0.700s
C:\SDK\platform-tools>
After rebooting, information appeared that file may be corruption, but when I go to recovery it still showing state LOCKED. Now after rebooting system Logo Google appeared and nothing happened (Bootloop?) Now I can't do anything

Why after rebooting everything goes back and device state is LOCKED? I have motherboard replaced by warranty service. What to do?

USB drivers are (re-)installed?
You never relocked bootloader at any point in the proces?

OK I flash *.img files manually one by one and I installed system. But main problem isn't solved.
After fastboot command oem unlock in bootloader mode it showing bootloader unlocked but after rebooting STATE is showing LOCK.
Any ideas? What **** is restore back system unlock to lock?

ok I found a simillar thread
http://forum.xda-developers.com/google-nexus-5/help/fastboot-oem-unlock-goes-to-lock-reboot-t2903581
So it can't be repaired... great warranty service replace my damaged motherboard for another not good working motherboard where I can't unlock bootloader to even flash nexus factory images hehehehehe OMG...

It's not fastboot oem unlock anymore.. The command is fastboot flashing unlock
Sent from my Nexus 5X using Tapatalk

graffixnyc said:
It's not fastboot oem unlock anymore.. The command is fastboot flashing unlock
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Since when is this implemented?

Even I wrote command fastboot flashing unlock, after reboot bootloader I get the same result - state: locked :/ and I have to again set everything from the beginning because command wipes my device... Thx for trying to helping me but I think that nothing can solve this problem.

Blacknighter said:
Even I wrote command fastboot flashing unlock, after reboot bootloader I get the same result - state: locked :/ and I have to again set everything from the beginning because command wipes my device... Thx for trying to helping me but I think that nothing can solve this problem.
Click to expand...
Click to collapse
Which version of the SDK and Platform Tools do you have installed?
Sent from my Nexus 5X using Tapatalk

I have installed latest sdk tools version. What does this have to do with it? I have all drivers installed. Any fastboot commands work ok, even flashing manually img files also work. System after rebooting bootloader do not save the unlock state settings :/

Update 4.4.4 to marshmallow

Hello,
My uncle gave me his htc one M8 and for some days now I've been trying to factory reset it and update from 4.4.4 to latest android version with no success. Everytime I try to factory reset (from settings or fastboot or pc with ruu) it fails everytime. It doesn't delete music and gallery (deletes apps and settings though) and the update notification never shows up. I'm sorry if the solution is on another thread but I haven't found anything during these days. I live in Balkan so the phone isn't linked with any carrier (bought in a regular store).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

specs
specs

you can update by flashing verizon stock mm ruu.
1) at first update hboot. https://www.androidfilehost.com/?fid=24438995911975644
2) then flash ruu. https://www.androidfilehost.com/?fid=24438995911973442
go to this thread for future support. http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845

umesh.lk said:
you can update by flashing verizon stock mm ruu.
1) at first update hboot. https://www.androidfilehost.com/?fid=24438995911975644
2) then flash ruu. https://www.androidfilehost.com/?fid=24438995911973442
go to this thread for future support. http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
Do I need microSD for this? Because I don't have one

ergi2468 said:
Do I need microSD for this? Because I don't have one
Click to expand...
Click to collapse
you don't need micro sd. you can flash by fastboot commands. use the following files for fastboot binaries. copy the files which you downloaded to fastboot folder.
1) go to fastboot usb mode
2) fastboot oem rebootRUU
3) fastboot flash zip hboot file name.zip
4) fastboot reboot-bootloader
5) fastboot oem rebootRUU
6) htc_fastboot flash zip ruu file name.zip

Delete (obscure) IMEI and serial number from the screenshot. These are personal info, and should not be posted online.

umesh.lk said:
you don't need micro sd. you can flash by fastboot commands. use the following files for fastboot binaries. copy the files which you downloaded to fastboot folder.
1) go to fastboot usb mode
2) fastboot oem rebootRUU
3) fastboot flash zip hboot file name.zip
4) fastboot reboot-bootloader
5) fastboot oem rebootRUU
6) htc_fastboot flash zip ruu file name.zip
Click to expand...
Click to collapse
error cannot load hboot.zip
error preprocess file cannot open ruu.zip

umesh.lk said:
you don't need micro sd. you can flash by fastboot commands. use the following files for fastboot binaries. copy the files which you downloaded to fastboot folder.
1) go to fastboot usb mode
2) fastboot oem rebootRUU
3) fastboot flash zip hboot file name.zip
4) fastboot reboot-bootloader
5) fastboot oem rebootRUU
6) htc_fastboot flash zip ruu file name.zip
Click to expand...
Click to collapse
error cannot load hboot.zip
error preprocess file cannot open ruu.zip

ergi2468 said:
error cannot load hboot.zip
error preprocess file cannot open ruu.zip
Click to expand...
Click to collapse
my bad there working on it

umesh.lk said:
you don't need micro sd. you can flash by fastboot commands. use the following files for fastboot binaries. copy the files which you downloaded to fastboot folder.
1) go to fastboot usb mode
2) fastboot oem rebootRUU
3) fastboot flash zip hboot file name.zip
4) fastboot reboot-bootloader
5) fastboot oem rebootRUU
6) htc_fastboot flash zip ruu file name.zip
Click to expand...
Click to collapse
ok Everything working fine except a little sim sign with ? on status bar. I can call though so not a problem. Thank You for your help

ergi2468 said:
ok Everything working fine except a little sim sign with ? on status bar. I can call though so not a problem. Thank You for your help
Click to expand...
Click to collapse
there is a method to remove sim icon. (sku id changing) but it may be a headache for you. try that. I fixed that on LP. but I haven't changed on MM. I think it will work. All the Best!
http://forum.xda-developers.com/showthread.php?t=2594804

umesh.lk said:
you can update by flashing verizon stock mm ruu.
1) at first update hboot. https://www.androidfilehost.com/?fid=24438995911975644
2) then flash ruu. https://www.androidfilehost.com/?fid=24438995911973442
go to this thread for future support. http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
So it was fine until I arrived on campus where I rely on my data plan. Mobile hotspot doesn't work. It just says error but I assume it is because of the verizon rom. Is there a way to fix this? I think a global unlocked rom should work since the cid:111111

ergi2468 said:
So it was fine until I arrived on campus where I rely on my data plan. Mobile hotspot doesn't work. It just says error but I assume it is because of the verizon rom. Is there a way to fix this? I think a global unlocked rom should work since the cid:111111
Click to expand...
Click to collapse
did you fix sim icon?
it's different to say something about hotspot. i haven't used hotspot in verizon. what is the error? is device rooted? it may not work hotspot as a bug came after root.
i belive there may no bugs in verizon stock roms.
you have superCID. but didn't forget that MID is 0P6B20000 (M8_WLV). your device is a limited one. but can be used globally.
*) if your firmware is 6.21.605.3, didn't downgrade or change it.
*) don't change mid. ( there are hardware changes than M8_UL) device may get bricked.
*) try verizon custom rom. but there may be hidden bugs. http://forum.xda-developers.com/verizon-htc-one-m8/development
after few days, as a user you can understand that stock rom is better at all costs.

umesh.lk said:
did you fix sim icon?
it's different to say something about hotspot. i haven't used hotspot in verizon. what is the error? is device rooted? it may not work hotspot as a bug came after root.
i belive there may no bugs in verizon stock roms.
you have superCID. but didn't forget that MID is 0P6B20000 (M8_WLV). your device is a limited one. but can be used globally.
*) if your firmware is 6.21.605.3, didn't downgrade or change it.
*) don't change mid. ( there are hardware changes than M8_UL) device may get bricked.
*) try verizon custom rom. but there may be hidden bugs. http://forum.xda-developers.com/verizon-htc-one-m8/development
after few days, as a user you can understand that stock rom is better at all costs.
Click to expand...
Click to collapse
No I didn't fix sim icon, didn't downgrade, didn't root, nothing. I am pretty sure it's a sim problem. Will allowing root acces bypass the verizon check and create a hotspot?

ergi2468 said:
No I didn't fix sim icon, didn't downgrade, didn't root, nothing. I am pretty sure it's a sim problem. Will allowing root acces bypass the verizon check and create a hotspot?
Click to expand...
Click to collapse
We can't think that root access will allow to create hotspot. use this custom rom. there may be a chance to create a hotspot. http://forum.xda-developers.com/ver...t/rom-nusenseven-marshmallow-sense-7-t3266678.
it is difficult to reply you today again as this is my bed time.

umesh.lk said:
did you fix sim icon?
it's different to say something about hotspot. i haven't used hotspot in verizon. what is the error? is device rooted? it may not work hotspot as a bug came after root.
i belive there may no bugs in verizon stock roms.
you have superCID. but didn't forget that MID is 0P6B20000 (M8_WLV). your device is a limited one. but can be used globally.
*) if your firmware is 6.21.605.3, didn't downgrade or change it.
*) don't change mid. ( there are hardware changes than M8_UL) device may get bricked.
*) try verizon custom rom. but there may be hidden bugs. http://forum.xda-developers.com/verizon-htc-one-m8/development
after few days, as a user you can understand that stock rom is better at all costs.
Click to expand...
Click to collapse
Also I can't even usb tether

ergi2468 said:
I am pretty sure it's a sim problem. Will allowing root acces bypass the verizon check and create a hotspot?
Click to expand...
Click to collapse
Nope. Root is just a permissions change, that allows the users access to modify certain things. It doesn't really modify anything in itself.
Your best bet if you need WiFi hotspot or tethering, is to flash a custom ROM that supports the Verizon version.

The system has been destroyed

I was using the Mitool tool, and suddenly the machine shut down and the message "the system has been destroyed" appears and it does not start anymore, the only option I have access and the fastboot, would anyone have the solution?

ghtcp said:
I was using the Mitool tool, and suddenly the machine shut down and the message "the system has been destroyed" appears and it does not start anymore, the only option I have access and the fastboot, would anyone have the solution?
Click to expand...
Click to collapse
Is your bootloader unlocked?
Did the PC shut down or the phone?
If your bootloader is locked you will need to open the back of the phone and flash a new firmware with PC and pressing the test point on the inside of the phone.
If unlocked you can fastboot the firmware as you normally would

Dobsgw said:
If your bootloader is locked you will need to open the back of the phone and flash a new firmware with PC and pressing the test point on the inside of the phone.
Click to expand...
Click to collapse
You can flash images with Mi Flash on locked bootloader no problem.

marinespl said:
You can flash images with Mi Flash on locked bootloader no problem.
Click to expand...
Click to collapse
They can try but if recovery isn't accessible then fastboot is the only option and without unlocked bootloader you cannot use it.
Test point is then the only way.
Obviously its best to try flashing without opening the phone first.

marinespl said:
You can flash images with Mi Flash on locked bootloader no problem.
Click to expand...
Click to collapse
Wtf! You can't use mi flash tool unless your bootloader is unlocked

The problem was tense, but it's already been resolved. I find it hard to understand more I will try to explain.
-------------------------------------------------- ------------------------------------- 1º It was with the Global Beta rom and the bootloader unlocked and installing the TWRP for the mitool, however for lack of attention I selected the option to block the bootloader.
After confirming the bootloader block by mitool, the cell phone appeared the message "the system has been destroyed", and it was restarting on this same screen, the only option I had access was to the fastboot.
Since I had access to the fastboot, I tried to install the rom by the miflash only that it gave the message "remote: Erase is not allowed in loke state".
4º After despairing and thought to open the cell to do the testpoints method.
5º Since probably the bootloader had been blocked by the mitool, I decided to enter the site and ask Xiaomi to release the code to unlock the bootloader again.
6th I put the chip in another device and thanks to the holy protector of the cell phones Xiaomi quickly released the code, I did process to unlock the bootloader and the cell phone ran again.
-------------------------------------------------- -------------------------------------END

ghtcp said:
The problem was tense, but it's already been resolved. I find it hard to understand more I will try to explain.
-------------------------------------------------- ------------------------------------- 1º It was with the Global Beta rom and the bootloader unlocked and installing the TWRP for the mitool, however for lack of attention I selected the option to block the bootloader.
After confirming the bootloader block by mitool, the cell phone appeared the message "the system has been destroyed", and it was restarting on this same screen, the only option I had access was to the fastboot.
Since I had access to the fastboot, I tried to install the rom by the miflash only that it gave the message "remote: Erase is not allowed in loke state".
4º After despairing and thought to open the cell to do the testpoints method.
5º Since probably the bootloader had been blocked by the mitool, I decided to enter the site and ask Xiaomi to release the code to unlock the bootloader again.
6th I put the chip in another device and thanks to the holy protector of the cell phones Xiaomi quickly released the code, I did process to unlock the bootloader and the cell phone ran again.
-------------------------------------------------- -------------------------------------END
Click to expand...
Click to collapse
The bootloader gods have smiled upon you this time

Hello! I have locked bootloader with "fastboot oem lock". I was in panic, but randomly I press "Volume -" + "power-on" and my Mi A1 have loading in Fastboot mode, where I was able to unlock bootloader again.
Hope, this can help you.

HI there I also stuck in the same condition and it seems your phone's bootloader is locked now, this happens because you root the phone or installed custom libs or twrp in it and locked the bootloader. So unlocking the bootloader will fix this problem. You can unlock it by going into Fastboot mode (pressing power button + volume down (-) button) and then with platform tools you can unlock it again by typing "fastboot oem unlock" and then "reboot".
I hope this will help someone

same issue in redmi note 4
indersethi said:
HI there I also stuck in the same condition and it seems your phone's bootloader is locked now, this happens because you root the phone or installed custom libs or twrp in it and locked the bootloader. So unlocking the bootloader will fix this problem. You can unlock it by going into Fastboot mode (pressing power button + volume down (-) button) and then with platform tools you can unlock it again by typing "fastboot oem unlock" and then "reboot".
I hope this will help someone
Click to expand...
Click to collapse
After i flashed lots of roms in redmi note 4 there is no problem i have seen but, right now my device suddenly rebooted because of rooted and flashed imgs and it shows ''system has been detroyed''.I tried the commands using adb fastboot oem unlock then its shows ''token verification failed;i can only acess to fastboot. what i have to do now ??.....

Basilp275 said:
After i flashed lots of roms in redmi note 4 there is no problem i have seen but, right now my device suddenly rebooted because of rooted and flashed imgs and it shows ''system has been detroyed''.I tried the commands using adb fastboot oem unlock then its shows ''token verification failed;i can only acess to fastboot. what i have to do now ??.....
Click to expand...
Click to collapse
Reflash your rom with fastboot and hope you haven't messed up anything related to your data so you can still use and have access to it.

ccelik97 said:
Reflash your rom with fastboot and hope you haven't messed up anything related to your data so you can still use and have access to it.
Click to expand...
Click to collapse
Yes,it's worked

Basilp275 said:
Yes,it's worked
Click to expand...
Click to collapse
Cool then ?

I had the same problem today. my phone was distroed when I tried to install Gcam.
my phone was not unlocked so that the flash of the new stock of the ROM was not possible. The solution is to connect the phone to a PC in fastboot mode and from the platform tools in cmd to type fastboot oem unlock. After that, I did not have to have a flash phone. Everything worked as if I only had to backup the data.
now I have a new phone.
People, with Mi A1, cling to two things - slot A or slot B and lock or unlock. The easiest way to do this is a cardinal error.
Greetings.

Same thing happened to me. Had global rom with bootloader unlocked, then I installed TWRP and reinstall MIUI 10, as well as no-verity and Magisk. When installed the phone showed some issues with the proximity sensors so I decided to reinstall, after installing and booting MIUI showed a message, "the device is locked", I couldn't connect to the internet to unlock it, so I decided to do a fresh installation through miflash, after a couple attempts all of a sudden TWRP was not there anymore. Now the bootloader shows unlocked on '''fastboot oem device-info'''. Now the real problem: miflash doesn't work because bootloader is locked, I didn't unlocked it in the first place so I cannot do a fresh installation through miflash, when booting TWRP it shows the message, The system has been destroyed....
I tried miflash, fastboot oem unlock, fastboot recovery flash for TWRP, fastboot -w then fastboot flash recovery ....zip. Absolutely nothing is working.
How did you make it work exactly?

jesus4android said:
Same thing happened to me. Had global rom with bootloader unlocked, then I installed TWRP and reinstall MIUI 10, as well as no-verity and Magisk. When installed the phone showed some issues with the proximity sensors so I decided to reinstall, after installing and booting MIUI showed a message, "the device is locked", I couldn't connect to the internet to unlock it, so I decided to do a fresh installation through miflash, after a couple attempts all of a sudden TWRP was not there anymore. Now the bootloader shows unlocked on '''fastboot oem device-info'''. Now the real problem: miflash doesn't work because bootloader is locked, I didn't unlocked it in the first place so I cannot do a fresh installation through miflash, when booting TWRP it shows the message, The system has been destroyed....
I tried miflash, fastboot oem unlock, fastboot recovery flash for TWRP, fastboot -w then fastboot flash recovery ....zip. Absolutely nothing is working.
How did you make it work exactly?
Click to expand...
Click to collapse
With locked bootloader I got no chance to flash anything. Neither fastboot nor MiFlash - any solutions? Also would be helpful to enabke USB Debugging via fastboot. Anyone knows?

If you brick your device on the way as it happened to me... check: https://forum.xda-developers.com/showpost.php?p=77755947&postcount=11
These guys helped me unbricking my mi8 using EDL (Test Point) and Mi-flash!

I want to sell my Google Play app developer license.
Please email me or call me if you are interested.
phone - +917007797787
Email- [email protected]

I got a bricked Mi 6 from a friend. He was trying to flash firmware, and somehow messed up. Trying to boot normally or into recovery showed "The system has been destroyed". `fastboot continue` did not work. Bootloader was locked ( = no possibility to do fastboot oem unlock). On top of that, the phone only accepted fastboot commands right after the usb cable was connected ( => I had to run a fastboot command, like `fastboot getvar all`, fastboot would output `< waiting for any device >`, then I connected cable, and it would work). Running fastboot commands later resulted only in fastboot hanging / getting stuck, with no output, can not be terminated with ctrl+c unless cable was disconnected.
I got myself a windows computer (I use linux), tried to do bootloader unlock. Failed on "add your mi account in Settings -> Developer -> blablabla" - no way to do that with a bricked phone. Then I found out about EDL (Emergency download) mode. This is what worked.
The only way to get into the EDL mode in this state was the hardware way (shortcutting the pins / "PCB test points"). Search online for "mi 6 edl mode testpoints". Basically, you have to:
1. remove the rear cover
2. remove the screws on the plastic part above the battery, remove the plastic piece
3. disconnect the battery (shorter connector on the left side)
4. shortcut the pins using a tweezer (the pins are just above the battery connector)
5. while the pins are connected, connect the USB cable
6. check in device manager that you have "HS-USB QDloader 9008" in the COM devices
7. use mi flash tool to flash the fastboot firmware
The pins (from https://www.mobilerdx.com/2019/02/xiaomi-mi-6-test-points-xiaomi-mi-6-edl-mode-pinout.html):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And after you succeed, maybe unlock your bootloader, so that you don't have to do this again

"This MIUI version can't be installed on this device"

Bricked with a locked bootloader - "This MIUI version can't be installed on this device"
I can get to "adb sideload" and fastboot, but the bootloader is locked
Can I unlock the bootloader with EDL? Can I access EDL with an EDL-cable? Or do I need to open the phone and short the EDL pins?
Can I recover the phone from a Linux computer? Or do I need Windoze?
Is it even possible to un-screw this phone?
Any help appreciated.

go vegan said:
Bricked with a locked bootloader - "This MIUI version can't be installed on this device"
I can get to "adb sideload" and fastboot, but the bootloader is locked
Can I unlock the bootloader with EDL? Can I access EDL with an EDL-cable? Or do I need to open the phone and short the EDL pins?
Can I recover the phone from a Linux computer? Or do I need Windoze?
Is it even possible to un-screw this phone?
Any help appreciated.
Click to expand...
Click to collapse
how did you do this?

Redmi 4A abdal said:
how did you do this?
Click to expand...
Click to collapse
1- Checking if this problem is still a problem with custom ROMs; it is, and thus I believe it to be a hardware fault.
2- Done testing, re-install stock stock ROM, lock bootloader via adb; bricked phone.

go vegan said:
1- Checking if this problem is still a problem with custom ROMs; it is, and thus I believe it to be a hardware fault.
2- Done testing, re-install stock stock ROM, lock bootloader via adb; bricked phone.
Click to expand...
Click to collapse
ok, you can run edl mode but its no good for you, its already locked by xiaomi, ( go ing to fastboot mode and give commands something like this " fastboot boot edl")
* do you see padlock lock sign when you go to fastboot mode
* try to flash vbmeta in fastboot mode
* try again to flash correct version miui fastboot rom with mi flashing tool with out selecting lock bootloader

I can get to fastboot by holding power+vol-down. There's no lock icon.
On Ubuntu, I don't think fastboot is compiled to support rebooting into edl. I tried editing the source, and I'm not sure if I did it right, but the binary I built did not boot the phone into edl.
Using these commands:
Code:
fastboot flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta /tmp/platform-tools/vbmeta.img
They all give the same result:
Code:
target reported max download size of 804274176 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.006s]
writing 'vbmeta'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.007s

go vegan said:
I can get to fastboot by holding power+vol-down. There's no lock icon.
On Ubuntu, I don't think fastboot is compiled to support rebooting into edl. I tried editing the source, and I'm not sure if I did it right, but the binary I built did not boot the phone into edl.
Using these commands:
Code:
fastboot flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta /tmp/platform-tools/vbmeta.img
They all give the same result:
Code:
target reported max download size of 804274176 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.006s]
writing 'vbmeta'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.007s
Click to expand...
Click to collapse
Try to unlock bootloader using cmd and then vbmeta

T.Y.M.SAI said:
Try to unlock bootloader using cmd and then vbmeta
Click to expand...
Click to collapse
I'm not sure what that means.

go vegan said:
I'm not sure what that means.
Click to expand...
Click to collapse
There are 2 ways to unlock bootloader
1. Official way using Mi flash tool
2. Unofficial way using cmd
There are lots of videos on how to unlock bootloader using cmd go and try them
Most important is to keep your phone charged

T.Y.M.SAI said:
1. Official way using Mi flash tool
2. Unofficial way using cmd
Click to expand...
Click to collapse
1- That requires access to a working phone.
2- All I'm finding is instructions for how to type "fastboot oem unlock" on a Windoze computer.

go vegan said:
1- That requires access to a working phone.
2- All I'm finding is instructions for how to type "fastboot oem unlock" on a Windoze computer.
Click to expand...
Click to collapse
Did you found a way to fix the phone or unlock bootloader?

You have 2 ways to get out of this situation.
1. Try to unlock the bootloader with the Mi account you used last time.
2. If couldn't unlock, then switch to EDL mode. Use a no auth programmer to flash the correct variant fastboot ROM and the device should boots up. Then add account again and wait for 168 hours for unlocking.
Since we've got no auth programmer for Sm6125 we could use EDL mode freely.

Hi there @go vegan , have you already fix your phone again? because i also got the same situation on my redmi 6. or is there anybody who can help? thanks

Hi all add me to the list with a k20pro.
The device was unlocked at the start, i got MIUI 12.5 global and flashed with miflashtool.
but wipe and lock was active.
now the phone comes up to the recovery menu and says the miui version is not for this device.
When I try to flash to another version, miflashtool says the device is locked,
when I try to unlock while using the account the device is registered in, miunlock says go to settings >developer options> mi unlock status.
Gave it to a repair shop for 1.5 months and nothing. I live in Iran so no authorized service centers here.
I have access to fast boot mode and recovery.
I tried xiaomitoll V2 which had a specific question asking if my device would show This MIUI version can't be installed on this device in phone is bricked option. It goes to get china official Rom but then errors.
I'm a noob here so any help would be great, tnx.

I have encountered the same problem a few hours ago with my beloved Redmi K20 Pro. My heart became gloomy thinking that I have no way left other than having to take to an authorized service centre where they will rip off the back cover. But then I stumbled upon this simple solution that took me a minute or two. This is how I solved it:
Entered the fastboot mode
Connected the phone to my laptop using the USB cable
Opened the official Mi Unlock Tool and logged in with my Mi account, and
Clicked on the beautiful UNLOCK button!
Boom! The phone is back to its vibrant life! I'm just happy again!

when I try to unlock while using the account the device is registered in, miunlock says go to settings >developer options> mi unlock status.

TECHtacian said:
I have encountered the same problem a few hours ago with my beloved Redmi K20 Pro. My heart became gloomy thinking that I have no way left other than having to take to an authorized service centre where they will rip off the back cover. But then I stumbled upon this simple solution that took me a minute or two. This is how I solved it:
Entered the fastboot mode
Connected the phone to my laptop using the USB cable
Opened the official Mi Unlock Tool and logged in with my Mi account, and
Clicked on the beautiful UNLOCK button!
Boom! The phone is back to its vibrant life! I'm just happy again!
Click to expand...
Click to collapse
Hi! Where can I download Mi Unlock Tool?

UnDevelopedDeveloper21 said:
Hi! Where can I download Mi Unlock Tool?
Click to expand...
Click to collapse
Apply for permissions to unlock Mi devices
en.miui.com

The solution to the problem is simple.
into fast boot mode,
Run unlock again!! Obviously it's locked. When unlocking is executed,
the same screen may appear again. Please do a reboot. You will definitely see the MIUI installation screen.

Device: Redmi note 7S
I found a solution and it worked for me:
1.Download the bat file and execute in your windows pc : https://drive.google.com/file/d/1NqPotx06yRuhPsOdEAdS4JNsk7qWWchF/view
2. After that use the MI unlocker tool to unlock the device.
3, Use mi flasher to flash the Rom.
After the hours of research in the internet i found the solution.
Thanks

Shiva5558 said:
Device: Redmi note 7S
I found a solution and it worked for me:
1.Download the bat file and execute in your windows pc : https://drive.google.com/file/d/1NqPotx06yRuhPsOdEAdS4JNsk7qWWchF/view
2. After that use the MI unlocker tool to unlock the device.
3, Use mi flasher to flash the Rom.
After the hours of research in the internet i found the solution.
Thanks
Click to expand...
Click to collapse
What do you mean by "execute in your windows pc"? Sorry for asking

Question Android 13 and unlocked bootloader

Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
Click to expand...
Click to collapse
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?

Ralendil said:
Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?
Click to expand...
Click to collapse
You don't need to do all of that to upgrade to android 13. You can read how to upgrade to android 13 here: https://forum.xda-developers.com/t/...-6-pro-bootloader-central-repository.4352027/
as well as here: https://forum.xda-developers.com/t/pixel-6-pro-easy-step-by-step-unlock-root-update.4361847/
it is a long thread with a lot of information, so I'll just give you an adlibbed version of how to upgrade
I read that you have removed root. You can re-root after upgrading. Make sure your bootloader is unlocked first.
First make sure you have the latest sdk platform tools version here: https://developer.android.com/studio/releases/platform-tools
Download the android 13 factory image here: https://developers.google.com/android/images
Extract the platform tools and the factory image, and make sure the flash-all.bat file is in the same location as adb.exe and fastboot.exe
If you want to keep your data, do this. If you don't want to lose your data and don't mind wiping your phone, skip this step and just run flash-all.bat in fastboot.
Edit the flash-all.bat file and remove the -w flag from the
Code:
fastboot update -w image-raven-tp1a.220624.021.zip
command. So it'll just be
Code:
fastboot update image-raven-tp1a.220624.021.zip
Save it, edit again just to double check that -w flag is gone. If it is, reboot your phone back into fastboot and run flash-all.bat.
It'll upgrade and do everything for you. You're on Android 13 now and your data is still intact.
Once your phone is booted, you can patch the boot image from the factory image you downloaded with Magisk and flash it in fastboot again by doing fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img. Then you will have root.
If you want to go back to complete factory with a locked bootloader, run Android Flash Tool from Google here: https://flash.android.com/welcome?continue=/back-to-public
Make sure "Wipe Device", "Lock Bootloader", and "Force Flash All Partitions" are checked.

You could always try the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). It's possible you could also take advantage of it's new option to flash only the 13 bootloader to both slots, and then will update the current slot to 13 completely.
Lughnasadh said:
FYI: Even though Android Flash Tool does not flash the whole image to both slots, they have added an option to flash the A13 bootloader to the inactive slot. This may be the easiest option to use when updating to A13 from A12.
Just to be clear, when updating to A13 from A12 a prompt will show up asking whether you want to also flash the bootloader to the inactive slot as well. It doesn't show up in the regular tick boxes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
FYI, you most definitely didn't need to re-lock the bootloader. Also, a pro tip for rooters. Once you unlock a device's bootloader, never ever re-lock it except in very rare circumstances. This didn't count as rare before you consult us.

I would have loved that it would be a solution.
It would allow me only to install android 12... and locking the bootloader make me affraid… I think I will never be able to unlock it cause I can’t use bootloader (see under)
For now, I try to make bootloader drivers working.
Every time I reboot to bootloader, the phone is not recognized by the computer and no adb/fastboot command can be used. So, I cannot use the flash-all.bat script.
Also, now when I use adb reboot fastboot the fastboot screen appears, then bootloader is loaded immediately...
I can’t believe I will spend several hours to be able to install that… I am stuck.
I tried to uninstall several drivers and reinstall drivers, but no changes... or yes a change. Now it is worst, Pixel 6 pro isn’t listed in device manager, and adb bootloader driver has disapear replaced by an adb driver line. Anyways, bootloader driver was never activated.
Edit: I should add that the update through the phone doesn’t work.
Don’t know why... the interface for google android flash tool changed... and now I was able to choose the version and I could flash the two slot with a13 bootloader.
Thanks for the idea...
Even if… I would love to understand why I did not succeed to install it...
Final edit: Android 13 has been successfully installed
Now, time to root it