Solved: What to check if your unlocked bootloader became "permanently locked" again.
Hi,
My bootloader was suddenly locked again after
I had an unlocked single sim 6553, running E6533_32.1.A.1.185_R5C
The phone had survived several reboots and behaved well as a rooted phone.
As the phone was intended for my wife, I then did a factory reset and followed the wizard to copy her settings from her old phone and set it up,
I wanted to try out a battery saving app "2 Battery" with root access, but found that super-su wasn't there any more (assumed removed during factory reset).
Powered off phone at 30% battery intending to reboot into TWRP.
Phone would only boot into flash mode. I tried all possible button combinations and also tried fully charging. Phone was completely stuck.
As flash mode was allowed, I used FlashTool to re-flash all of E6533_32.1.A.1.185_R5C, using same image as before
Tried reflashing the patched kernel (as above) using fastboot, but got
"downloading 'boot.img'...
OKAY [ 0.523s]
booting...
FAILED (status read failed (No such device))"
Looking at the service menu security setting screen, I saw that the BL remote status was "Locked" with Allow unlock = "No"
I tried loading different roms, without wiping, all with same result and was about to wipe the phone...
Then I read in a BL unlock thread that you can't unlock the BL if "Find My Xperia" is ON!
So I turned it OFF and Hey Presto!
Status is now unlocked again!
If anyone else has similar problems, I advise to check this setting first. I could save you a lot of time and trouble!!
Only with "bootloader unlock allowed" before, mine is "allow : no" and still no even deactive my xperia... , can't root
Lavievn said:
Only with "bootloader unlock allowed" before, mine is "allow : no" and still no even deactive my xperia... , can't root
Click to expand...
Click to collapse
Me to. Any method to root with locked bootloader? Or unlock unlock it
popa.vasile.93 said:
Me to. Any method to root with locked bootloader? Or unlock unlock it
Click to expand...
Click to collapse
Try switching find my xperia off
Related
Okay, so there is no screen protector or anything. Not rooted or unlocked or tampered in any way. I've had the phone for 26 hours and then the following happened:
EDIT: YouTube video added https://youtu.be/yAVmTz7MQbQ
I pulled the phone out of my pocket to unlock it. I see the lock screen and put in my pin (yes, I see the actual screen and stuff on it. Let me make that clear.) after I enter my pin successfully the screen locks itself. I contacted Google support and they said to factory reset it. I did the full factory data reset in the recovery mode (again, the screen works. I can see everything to do a FDR and I can see the boot animation) and it starts to boot up. Once I see the "welcome" screen it instantly locks itself. I can hear the audible "latch" locking sound that it makes when you press the power button. I know the buttons are not malfunctioning because they work perfectly fine in bootloader / recovery mode to scroll up and down and select things. I've tried multiple things but nothing seems to work. The problem here is that I want to try and do a factory image but my computer will NOT recognize my Nexus 6P when in recovery mode / bootloader mode. I have all the drivers installed but since I can't access the OS and enable OEM UNLOCKING there is no way to factory flash a factory image is there? Can someone maybe help point me in the right direction? Again, I can NOT access the OS at all whatsoever.
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
hutzdani said:
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
Click to expand...
Click to collapse
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
xandr00 said:
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
Click to expand...
Click to collapse
Can you run fastboot format cache and format user data? Then will anything happen ?
Sounds like you need to edit the partition that holds the data change for allow OEM unlock - there's a few threads about this on XDA for the N9 and N6 as far as I can remember.
It would seem the ability to flash a fresh system.img would solve this
I apologize if this is in the wrong section this is my first time posting to xda
I tried rooting my tmobile LG V20 and cant seem to get into TWRP. Every time i boot up it goes to screen that says
"your device software cannot be checked for corruption. Lock the bootloader"
then it boots to a white screen that says Encryption Unsuccessful with a reset button at the bottom. I am unable to get into twrp with the power and volume down button.
epr2175 said:
I apologize if this is in the wrong section this is my first time posting to xda
I tried rooting my tmobile LG V20 and cant seem to get into TWRP. Every time i boot up it goes to screen that says
"your device software cannot be checked for corruption. Lock the bootloader"
then it boots to a white screen that says Encryption Unsuccessful with a reset button at the bottom. I am unable to get into twrp with the power and volume down button.
Click to expand...
Click to collapse
There is another thread around here that answers your problem. I had the same issue. Something along the lines of plug in phone and open command prompt with command : and reboot bootloader and reboot phone. When you see twrp booting and installing files hit enter and you should boot into twrp again.
I tried it about 35-40 times and failed. It finally worked after many tries. Look for the thread around here somewhere though.
---------- Post added at 04:42 AM ---------- Previous post was at 04:38 AM ----------
Found it, its under questions and answers. The title is "hi guys my tmobile is stuck in bootloop"
Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app
Also stuck at the same page with the reset button please help
Locking/Unlocking Bootloader Works!!
Thank You!!! You finally got my phone to work after trying for a few days! :laugh:
jjr3211 said:
Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you for this tips, i Lock the bootloader and then Unlock it again as your command, and viola my phone back to life haha
The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian
runningnak3d said:
The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian
Click to expand...
Click to collapse
still have issue, i can't install ane apps now.. how to solve it please ?
jjr3211 said:
Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
You saved the day my friend! Locking and unlocking via fastboot did the trick. Phone booted right up.
runningnak3d said:
The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian
Click to expand...
Click to collapse
Okay - I have this too now. I have a h910 that I just followed runningnak3d's dirty santa guide on. Been flashing all around the last 2 weeks - learning a lot along the way. But today I flashed back to stock 10r. I fomatted data in TWRP - typed yes etc and it just reboots to that. I went to TWRP and installed Alpha Omega Oreo - same error. Restored one of my backups of Lineage I get the same error. So what is the right way out of this problem?
KDZ back and follow your dirty santa guide to re/unlock the bootloader? (I sure hope Brian is still around reading these) Not to screw up the terminology - but if TWRP still boots as my recovery - doesn't that mean my bootloader is unlocked.?
Well - not sure what I was doing yesterday... But wiped all, format data and factory reset in TWRP this morning and flashed h910 10r and then Magisk v20.4 and it worked. Could it be as simple as forgetting to flash Magisk? Maybe that is all that was wrong?
Thanks for reading.
Well if you find yourself in this same sticky spot - check out this here
I flashed 2018-04-15 level and my restore worked without issue.
YMMV
Good Luck
I formatted data in twrp. No change
The correct answer is to downgrade twrp, at least only that fixed it for me.
Hi I have a nexus 6p entering bootloop yesterday. fully stock with latest OTA update. device is locked, not rooted, bootloader LOCKED.
I can get to fastboot screen (android robot laying down), with "start, reboot bootloader, recovery, barcodes, poweroff", all options result in bootloop again (except power off and barcode). Cannot go into recovery mode, cannot wipe cache/factory reset.
I tried using the latest solution to disable to big cluster but that guide requires the phone to have a unlocked bootloader which I cannot unlock. I get the FAILED [remote: OEM unlock is not allowed], because I never enabled developer option to unlock the phone and never enabled USB debugging.
Phone was manufactured 12-2015. Called google and was told because the phone was not bought from google store there is nothing they can do. Called Huawei was told the phone is out of warranty and there is nothing they can do.
Tried heating the phone/blowdryer method. tried freezer method. Nothing worked.
What can I do at this point?
Same here
Same exact problem here - "Tried heating the phone/blowdryer method. tried freezer method. Nothing worked." Any thoughts... anyone?
I have the same problem. I'm not able to find any information how to unlock the phone in this state. Any hint?
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.
tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?
Hi there,
I think I have screwed up my V20.
I have flashed a new rom, met the decryption unsuccessful, format data didn't work.
then I searched a thread, it said lock bootload and then unlock it could help.
then, brick.
I have not entered the new rom and tick on the oem unlock button. and now the phone didn't pass the security check and shutdown automatically.
any methods could help? 9008?
thanks a lot.
magicsword123 said:
Hi there,
I think I have screwed up my V20.
I have flashed a new rom, met the decryption unsuccessful, format data didn't work.
then I searched a thread, it said lock bootload and then unlock it could help.
then, brick.
I have not entered the new rom and tick on the oem unlock button. and now the phone didn't pass the security check and shutdown automatically.
any methods could help? 9008?
thanks a lot.
Click to expand...
Click to collapse
yeah... locking the bootloader has zero to do with encryption/decryption..
If it won't let you back into fastboot mode (volume down+usb connect) and reunlock it.
You might have Download mode/LG UP.... unless you put/left twrp on that. (volume up+usb connect from powered off).
If you don't have either of those and you have an H918 you're screwed.
If you don't have either of those and you have another variant (as long as its not an ARB 1 ls997) it may be possible to reflash using the leaked firehose (which is arb 0 and signed for the other variants besides H918) but I have no experience with
Phoenix591 said:
yeah... locking the bootloader has zero to do with encryption/decryption..
If it won't let you back into fastboot mode (volume down+usb connect) and reunlock it.
You might have Download mode/LG UP.... unless you put/left twrp on that. (volume up+usb connect from powered off).
If you don't have either of those and you have an H918 you're screwed.
If you don't have either of those and you have another variant (as long as its not an ARB 1 ls997) it may be possible to reflash using the leaked firehose (which is arb 0 and signed for the other variants besides H918) but I have no experience with
Click to expand...
Click to collapse
thanks for the reply mate.
i am afraid I have met the worst situation.
1. able to enter fastboot, but not allow wo unlock bootload. (cos I flashed the new rom and didn't even enter it, and tick the oem unlock button )
2. I have used LAF to change the download mode to be TWRP, so no hope here. the tricky thing is, once I lock the bootload, it could not even enter download mode or TWRP, showed not pass the safety check, will not boot. and then an endless boot loop.
3. my V20 is H918.
4. MY V20 is totally screwed........cry face.