I unlocked the Nexus 5X, installed TWRP recovery and then locked the bootloader again. Locking the bootloader stops TWRP from working and stops the phone from booting into Android. And since the phone is locked, it's impossible to install anything else via the bootloader or unlock it since Android doesn't boot. I think the phone is now permanently bricked and locked.
Don't have my phone yet, but can you boot into the bootloader? That's usually all you need to unlock the bootloader via fastboot. Did you try the skipsoft toolkit?
Shouldn't you just be able to power volume down boot into the bootloader. Then fastboot oem unlock and then go from there?
Sent from my Nexus 5X using Tapatalk
The_Automator said:
Shouldn't you just be able to power volume down boot into the bootloader. Then fastboot oem unlock and then go from there?
Click to expand...
Click to collapse
Nope. You have to enable unlocking from within Android before the device can be unlocked from the bootloader. And since Android won't boot up after the device is re-locked... "fastboot oem unlock" fails with "FAILED (remote: oem unlock is not allowed)".
Twrp is in the recovery partition, which is not the same partition the boot loader resides in.
Since the only way to lock the boot loader is via fastboot, and since you successfully did this, we know your boot loader is working. Get back into the boot loader and unlock your device. You can enter the boot loader via hardware key combination. Also, you can enter the boot loader even if the phone has no is and no recovery since it is independent of those.
_jordan_ said:
Twrp is in the recovery partition, which is not the same partition the boot loader resides in.
Since the only way to lock the boot loader is via fastboot, and since you successfully did this, we know your boot loader is working. Get back into the boot loader and unlock your device. You can enter the boot loader via hardware key combination. Also, you can enter the boot loader even if the phone has no is and no recovery since it is independent of those.
Click to expand...
Click to collapse
I can get into the bootloader no problem. In the bootloader, the DEVICE STATE is locked. When I do "fastboot oem unlock" it fails with:
FAILED (remote: oem unlock is not allowed)
This is because you must first enable unlocking in the Settings menu in Android before the fastboot command works. Android doesn't boot anymore since I re-locked the device, so there is no way to unlock the device...hence it is permanently bricked.
Interesting didn't know that the developer option for oem unlocking unchecked itself when you locked the bootloader. That seems pretty dangerous
Sent from my Nexus 5X using Tapatalk
Can you enter safe mode? I thought there's a safe mode function built into Android
Sent from my Nexus 5
Can't you just flash a stock recovery?
@simms22 they need your help here Same issues as w/ Nexus 6.
nyjumpman said:
Can't you just flash a stock recovery?
Click to expand...
Click to collapse
Nope. You can't flash stock images unless the device is unlocked. If I run "flash-all.sh" it says "FAILED (remote: device is locked. Cannot flash images)".
This phone is totally bricked.
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
Do these work?
I'm pulling out stuff from an interesting N9 thread
Which linked to this post
PhoenixTank said:
Do these work?
I'm pulling out stuff from an interesting N9 thread
Which linked to this post
Click to expand...
Click to collapse
Nope. "fastboot format userdata" returns:
FAILED (remote: device is locked. Cannot erase)
I'm not sure why your phone isn't booting into Android, since it's stock, but you could try a factory reset inside TWRP. If that doesn't work, did you make a back-up you can flash or sideload in TWRP? If not, you may have to wait until someone either uploads a flashable OTA, or a custom ROM you can flash in TWRP.
Edit: If none of these methods work, you could try pushing the stock images via TWRP and then a factory reset/wipe. I'm not sure if you can do this with a locked bootloader, though. Also, if the re-locking wiped your device, you'll have lost root, which will render this option useless.
ol2 said:
Nope. "fastboot format userdata" returns:
FAILED (remote: device is locked. Cannot erase)
Click to expand...
Click to collapse
When you are in TWRP (broken, right? but will it just hang on the logo?), can you get adb to work?
Can you get adb shell to work?
If yes,
This might provide some help.
Bear in mind, those dd commands probably aren't correct for this device. I don't have an n5x yet to check...
PhoenixTank said:
When you are in TWRP (broken, right? but will it just hang on the logo?), can you get adb to work?
Can you get adb shell to work?
If yes,
This might provide some help.
Bear in mind, those dd commands probably aren't correct for this device. I don't have an n5x yet to check...
Click to expand...
Click to collapse
Awesome idea. TWRP is broken but there's a slight delay before it reboots itself. I'm trying to get the timing right to issue some adb commands before the reboot.
I made this same stupid mistake on my Nexus 6 a while back. I locked the bootloader for some reason and then ended up in the same position. Using the following commands while in the bootloader solved it for me. It took me hours to figure it out. In fact, I think Simms was the one who recommended it.
fastboot format userdata
fastboot format cache
If they are not working for you, then I wish you the best of luck. I feel your pain man.
The_Automator said:
Interesting didn't know that the developer option for oem unlocking unchecked itself when you locked the bootloader. That seems pretty dangerous
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I agree. I will have to keep it in mind and the geniuses that write guides hopefully will mention it.
Edit: Crud, that sounded sarcastic. It wasn't.
How about fastboot boot twrp-bullhead-blah.img
This will boot into twrp but not flash it. Adb will work if you can get in.
Also, try just flashing the os image file with fastboot update image-bullhead-marshmallow-delta-tango.zip (unzipb from the factory image)
The flash all command will try to flash the bootloader which is forbotten.
Make sure you are using the latest fastboot too. There are some new commands- flashboot flashing unlock blah to unlock the non-bootloader bits. I'm not sure if it will work for you, but at this point it can't hurt.
I don't think that you are locked out just yet.
Have you tried flashing factory images in fastboot?
Related
Hello guys. I've been looking arround for a solution before posting my situation, but I didin't find any help, so I hope you can help me over.
The fact is that my phone is stuck in the bootloader mode. No matter what I do, anytime I turn it on, it goes directly to the bootloader mode and gives me a message that says "fastboot mode-no boot or recovery img" in red. Beside that, my bootloader is locked, and if I try to unlock it, it goes to the unlock screen, it ask me if I want to unlock it, but even if I say "YES", it doesn't unlock. I can't get into recovery mode, so it is impossible to restore any previous backup i've made.
I can get into download mode, but as soon as the odin starts to flash the ROM, the program crashes.
I tried to erase the boot image and the recovery image, but it just says "unknown partition".
Now, why all this did happen?, well I was trying to install the stock firmware that I downloaded from sammobile, and it never installed, the program crashed and my phone got... bricked????
If I could only unlock the bootloader it would be easier, i think.
Any help, please????
not sure if it will work on locked boot loader.... also don't use any tool, plain adb/fast boot
Errors you are getting doesn't say boot loader, but boot and recovery so try it.
Start phone in boot loader mode
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
You can get both files from Google images.
Thanks for responding. I tried to erase the boot and recovery partition but...
This is what i get if i try to erase the boot partition
C:\Users\Casa\Desktop\Android\ADB for NEXUS S>fastboot erase boot
erasing 'boot'...
FAILED (remote: Unknown Partition)
finished. total time: 0.000s
Same thing if I try to erase the recovery image.
And if i try to flash the boot without deleting it, this is what i get:
C:\Users\Casa\Desktop\Android\ADB for NEXUS S>fastboot flash boot boot.img
sending 'boot' (4148 KB)...
OKAY [ 0.406s]
writing 'boot'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.406s
This is really weird, i can't unlock the bootloader using "fastboot oem unlock". As I said before, it takes me to the unlocking screen, asks me if i'm sure, but even if I agree, the boot loeader is still locked. I really don't understand too much thisfar, but I think there's a problem with the partitions.
Any sugestion? I really need some help please...
Well if you're sure fastboot isn't working...
Have you tried ODIN? I think officially signed Odin.tar files can be flashed with a locked bootloader.
As much as Odin freaks me out (too damn finicky)...it can have it's uses.
Well i have already tried Odin, but the flashing process fails, as a fact it doesn't even flash the kernel.
Man, this is really weird. I can't unlock the bootloader, can't erase the boot nor the recovery image because partitions seems to be broken, damaged, lost, or I dunno; I can't flash a rom using Odin...
What can I do? I flashed an md5 file that I downloaded from sammobile (I9250XXKK1 ROM), and tried to flash it, and then my nightmare begun.
I really need some help, guys... I have posted the same problem in three different pages, and I have only gotten two answers, yours.
whats the error that odin gives you?
Have you tried using the Nexus Tool Kit?
Sent from my Galaxy Nexus using xda app-developers app
vikdal said:
Have you tried using the Nexus Tool Kit?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
that will not help him. all the toolkit does is use fastboot.
Zep, thanks for responding. I think that fastboot will not work for me , as you said some lines above, unless I manage to unlock the bootloader. Right now I'm at work (I really hate to work while my phone is bricked at home), so I can't tell you exactly the error I get while using Odin, but if you don't mind, i'll back home after work and i'll teel you the error I'm getting...
ok long shot try this
Get the cwm 6 img in fast boot folder
Fastboot boot cwm.img
Format data cache system
Flash some stable stock like rom or cm9 rc2. See what happens
atifsh said:
ok long shot try this
Get the cwm 6 img in fast boot folder
Fastboot boot cwm.img
Format data cache system
Flash some stable stock like rom or cm9 rc2. See what happens
Click to expand...
Click to collapse
he cant use fastboot.... can people really not read?
Zepius said:
he cant use fastboot.... can people really not read?
Click to expand...
Click to collapse
Huh, you should start reading buddy, he can use it just fine, he can't flash any thing is the issue.
atifsh said:
Huh, you should start reading buddy, he can use it just fine, he can't flash any thing is the issue.
Click to expand...
Click to collapse
really?
apolousm said:
Hello guys. I've been looking arround for a solution before posting my situation, but I didin't find any help, so I hope you can help me over.
The fact is that my phone is stuck in the bootloader mode. No matter what I do, anytime I turn it on, it goes directly to the bootloader mode and gives me a message that says "fastboot mode-no boot or recovery img" in red. Beside that, my bootloader is locked, and if I try to unlock it, it goes to the unlock screen, it ask me if I want to unlock it, but even if I say "YES", it doesn't unlock. I can't get into recovery mode, so it is impossible to restore any previous backup i've made.
Click to expand...
Click to collapse
sure looks like he cant use fastboot to me to flash anything.
stop it man, go see what he writes in response to my first reply.
Zepius said:
really?
sure looks like he cant use fastboot to me to flash anything.
Click to expand...
Click to collapse
Exactly! He can't write, Fastboot works just fine, it even send file ok, but failed to write.
atifsh said:
stop it man, go see what he writes in response to my first reply.
Click to expand...
Click to collapse
its clear you do not understand fastboot.
he cannot flash images with a locked bootloader using fasboot. period.
even in the referenced post you just gave me, it says:
C:\Users\Casa\Desktop\Android\ADB for NEXUS S>fastboot flash boot boot.img
sending 'boot' (4148 KB)...
OKAY [ 0.406s]
writing 'boot'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.406s
Click to expand...
Click to collapse
he mentioned in the first post that he cannot unlock the bootloader for whatever reason.
Zepius said:
its clear you do not understand fastboot.
he cannot flash images with a locked bootloader using fasboot. period.
even in the referenced post you just gave me, it says:
he mentioned in the first post that he cannot unlock the bootloader for whatever reason.
Click to expand...
Click to collapse
stop replying to my posts and if you can help him, you are just making this thread useless.
Hi guys... I think I should explain this ... first of all thanks for trying to help
The fact is that I can't use fastboot (I think). Let me explain: If I try to unlock the bootloader it takes me to the unlock screen, and if I choose yes, the bootloader doesn't unlock.
So, if we consider the fact that I need to unlock the bootloader to use the fastboot, I think there's no chance to use the fastboot command.
I really, really, reaaaaaaally apretiate your help guys, your knowledge will be allways wellcome.
I understand that booth have your point of view, and try to help.
This is the first tmioe I see a prolem like this, I have reading arround and there are no similiar posts, I mean, that the bootloeader can't be unlocked... I found this ------> http://forum.xda-developers.com/showthread.php?t=1067815&page=2 and as saycnahd said "...I feel like I need A to do B, and B to do A....".
Thanls in advice you guys...
the error message that you get from ODIN will be very helpful. we dont need it to fully write a rom, just a couple things so that you can use fastboot to flash anything you need.
Ok, Zep... I get it :good: as soon as I can, I'll post the error... right now i'm seated at work, front of my computer, using my mama's phone right now I just remember that the Odin showed me a Fail message on a big red square on the upper left corner, where it is supposed to appear the progres dialog. I know it sounds pretty basic and useless for now.
Hello, I'm not sure if this has been discussed before, but atleast I didn't find a complete answer to my question.
I unlocked my bootloader some time ago, and I flashed a new Image, a stock 4.2 maguro image, but the problem is that I forgot to root the new image, i've been using my phone for some time now, and I wanted to root the phone, but is there a way to root the phone without wiping all the data and settings?
Braien
is your bootloader still unlocked?
if so, just flash or boot into a custom recovery and then flash the supersu.zip package. this will not wipe your data.
Zepius said:
is your bootloader still unlocked?
if so, just flash or boot into a custom recovery and then flash the supersu.zip package. this will not wipe your data.
Click to expand...
Click to collapse
Should be unlocked, but how can I be sure of that?
And how can I enter the custom recovery, I can't remember.
braien334 said:
Should be unlocked, but how can I be sure of that?
Click to expand...
Click to collapse
2 ways,
when you reboot your phone, do you see a little unlocked lock?
other way: boot into fastboot mode and the lock status will say "UNLOCKED"
braien334 said:
Should be unlocked, but how can I be sure of that?
Click to expand...
Click to collapse
During the boot, the padlock in the lower half is open if the device is unlocked .
Okay, it's unlocked, but how to enter the recovery mode?
If I press volume up+down and power, and I select recovery, it just says no command.
Is there some tutorial for rooting like this?
http://forum.xda-developers.com/showthread.php?t=1529058
follow the section after unlocking your device.
I used Nexus toolkit, but I guess it works the same, but is automatic.
But thanks anyways:good:
I'm trying to get my Nexus 7 back to stock but I have... an issue...
I mistyped this command: fastboot flash boot boot.img
As: fastboot boot boot.img
And now the screen is just stuck at the bootloader... I cant change options. What do I do?
The boot image is the kernel. The improper command should not have erased anything. Even if it did, the bootloader and recovery should still be functional.
Username invalid said:
The boot image is the kernel. The improper command should not have erased anything. Even if it did, the bootloader and recovery should still be functional.
Click to expand...
Click to collapse
Thanks. I got concerned I may have did something wrong. I think I'm back in business again. Thank you.
Today i did something very silly and used the Asus Flash tool to flash what i thought was the correct raw image for my ZE551ML (to try and re-lock the bootloader), it turned out that I in fact flashed the ZE550ML raw file by mistake !!! Upside is that the only difference i saw was the change in screen resolution and no harm seems to have been done to my phone.
I have now found a ZE551ML raw file and flashed that to my device and it seems to have worked and re-locked the bootloader.
The boot screen is now black again, but is there any other way to test or find out if it is indeed re-locked?
Try to flash TWRP
Kona67 said:
Try to flash TWRP
Click to expand...
Click to collapse
Installed temporarily, should i get an error or should it refuse to flash?
shake1963 said:
Installed temporarily, should i get an error or should it refuse to flash?
Click to expand...
Click to collapse
any custom recovery can not be flashed if bootloader is lock.
recovery was installed means bootloader is unlocked.
rajlko said:
any custom recovery can not be flashed if bootloader is lock.
recovery was installed means bootloader is unlocked.
Click to expand...
Click to collapse
But he said it was temporary... I assume he means it went back to stock after the second reboot?
azthemansays said:
But he said it was temporary... I assume he means it went back to stock after the second reboot?
Click to expand...
Click to collapse
Yes, back to stock after second boot...
rajlko said:
any custom recovery can not be flashed if bootloader is lock.
Click to expand...
Click to collapse
You can run a tethered TWRP without unlocking.
shake1963 said:
Yes, back to stock after second boot...
Click to expand...
Click to collapse
That was likely the "tethered" recovery then. Try the untethered, but of course skip the part where you unlock the bootloader. In short:
reboot into bootloader
fastboot flash recovery twrp.img
reboot into recovery (press volume down twice until "Reboot recovery" shows up, then press power button)
If that boots into TWRP I suppose the bootloader is still unlocked. It may not be the easiest, but it should give you an answer.
wutr said:
You can run a tethered TWRP without unlocking.
That was likely the "tethered" recovery then. Try the untethered, but of course skip the part where you unlock the bootloader. In short:
reboot into bootloader
fastboot flash recovery twrp.img
reboot into recovery (press volume down twice until "Reboot recovery" shows up, then press power button)
If that boots into TWRP I suppose the bootloader is still unlocked. It may not be the easiest, but it should give you an answer.
Click to expand...
Click to collapse
Seems bootloader is still unlocked.... TWRP untethered stuck so back to the drawing board lol..
I would love to know what the process for unlocking does when the terminal commands are processed. I have a spare ZF2 with a broken screen that I can experiment with so no great loss if I trash it...
Any recommendations for reading... or do I need to maybe learn a bit of code?
I saw a method on here somewhere where a couple of files are flashed from the ifwi.zip file found in stock rom (I think that is a method used in another zenfone variant .... The 5 or 4.) which re locks the bootloader.
Doesn't work on the ZF2 though....
My Android Knowledge is pretty good, however I have NEVER dealt with a stock recovery. I have a friend's 5x that will not boot into the OS, it's just bootlooping. Fixing that is not my issue, I'll deal with that easily. However, I do want to pull his photos and other user data off the emulated storage partition before wiping it to fix his boot. Is there anyway within the stock recovery or within fastboot to use adb or something else I'm unaware of to pull user files? Again, bootloader is LOCKED, so flashing a custom recovery to access adb from within recovery is not an option. I use Linux, is there a way to mount the user data partition from within the stock recovery or within fastboot so I can pull these files off the device before I reset it for him?
I never had this problem but have you tried the pull files option in NRT, it is able to do a lot of things with loked Bl, Stock Recovery?
annoyingduck said:
My Android Knowledge is pretty good, however I have NEVER dealt with a stock recovery. I have a friend's 5x that will not boot into the OS, it's just bootlooping. Fixing that is not my issue, I'll deal with that easily. However, I do want to pull his photos and other user data off the emulated storage partition before wiping it to fix his boot. Is there anyway within the stock recovery or within fastboot to use adb or something else I'm unaware of to pull user files? Again, bootloader is LOCKED, so flashing a custom recovery to access adb from within recovery is not an option. I use Linux, is there a way to mount the user data partition from within the stock recovery or within fastboot so I can pull these files off the device before I reset it for him?
Click to expand...
Click to collapse
Not easily. The userdata partition is encrypted and you have a locked phone, so essentially you would need to hack the phone.
If you had an unlocked phone, you could boot into TWRP and you know the rest.
Vulkaistos said:
I never had this problem but have you tried the pull files option in NRT, it is able to do a lot of things with loked Bl, Stock Recovery?
Click to expand...
Click to collapse
If it can't be done manually, NRT won't be able to do it either. Plus I feel that toolkits will someday become the foundation for the demise of humanity as a whole.
sfhub said:
Not easily. The userdata partition is encrypted and you have a locked phone, so essentially you would need to hack the phone.
If you had an unlocked phone, you could boot into TWRP and you know the rest.
Click to expand...
Click to collapse
That's what I'm coming up with. I'm wondering if the adb sideload option within the stock recovery will grant me access to traditional adb commands instead of it's singular purposed commands - I'll find out soon. On another note, looks like I might not even be able to flash a system image for him either. Apparently now an OEM unlock option needs to be checked off in DEV options - which will require a bootable OS. So strange. Hopefully at a minimum a recovery reset will at least get the phone booting. If not, I won't be able to even unlock his BL to flash a fresh system image without having a currently bootable OS in order to check off that OEM unlock option. By the sounds of it, current locked BL Nexus's turn a softbrick into a hardbrick with no way to recover?!? Very un-Nexus!!
annoyingduck said:
That's what I'm coming up with. I'm wondering if the adb sideload option within the stock recovery will grant me access to traditional adb commands instead of it's singular purposed commands - I'll find out soon. On another note, looks like I might not even be able to flash a system image for him either. Apparently now an OEM unlock option needs to be checked off in DEV options - which will require a bootable OS. So strange. Hopefully at a minimum a recovery reset will at least get the phone booting. If not, I won't be able to even unlock his BL to flash a fresh system image without having a currently bootable OS in order to check off that OEM unlock option. By the sounds of it, current locked BL Nexus's turn a softbrick into a hardbrick with no way to recover?!? Very un-Nexus!!
Click to expand...
Click to collapse
adb sideload doesn't have full adb access, only adb sideload.
You can flash without unlocking if you download the FULL OTA google started providing a couple of months ago. This can be flashed via adb sideload and is essentially equivalent to factory image, but flashable from stock recovery without needing to unlock bootloader. Factory reset when done and it will have same effect as flashing factory image.
sfhub said:
adb sideload doesn't have full adb access, only adb sideload.
You can flash without unlocking if you download the FULL OTA google started providing a couple of months ago. This can be flashed via adb sideload and is essentially equivalent to factory image, but flashable from stock recovery without needing to unlock bootloader. Factory reset when done and it will have same effect as flashing factory image.
Click to expand...
Click to collapse
Yeah, just tried that. Still not booting. Something's corrupted, may even be hardware related. At this point it seems only a full image flash would be the only option to get the device to even boot - which simply cannot be done due to the OEM unlock option not being enabled. Me no likely that new addition
Sent from my XT1575 using Tapatalk
annoyingduck said:
Yeah, just tried that. Still not booting. Something's corrupted, may even be hardware related. At this point it seems only a full image flash would be the only option to get the device to even boot - which simply cannot be done due to the OEM unlock option not being enabled. Me no likely that new addition
Click to expand...
Click to collapse
The FULL OTA *is* a full image flash.
Did you factory reset?
The image flash fails, then reads succeeded. Still will not boot past the splash screen. Hangs, then goes black. I don't think the OTA zips flash all partitions like the factory image does.
Sent from my XT1575 using Tapatalk
annoyingduck said:
The image flash fails, then reads succeeded. Still will not boot past the splash screen. Hangs, then goes black. I don't think the OTA zips flash all partitions like the factory image does.
Click to expand...
Click to collapse
Guarantee they (the FULL OTA from factory image site) do. Open up the zip file. They even flash in more granular detail than the factory image. The only thing it doesn't do is wipe user/cache, which can be performed by factory reset.
I don't know what it means for the image flash to fail then read succeeded.
sfhub said:
Guarantee they (the FULL OTA from factory image site) do. Open up the zip file. They even flash in more granular detail than the factory image. The only thing it doesn't do is wipe user/cache, which can be performed by factory reset.
I don't know what it means for the image flash to fail then read succeeded.
Click to expand...
Click to collapse
Neither do I, it's a first.
Sent from my XT1575 using Tapatalk
annoyingduck said:
Neither do I, it's a first.
Click to expand...
Click to collapse
Sorry, I should be more clear, could you list what it says.
It sounds like the flash script is not checking for errors at the end so there is some error flashing within one of the partitions, but the overall script is saying everything good.