i have searched high and low for help on this one and can't find anything similar.... Though I found one thread that suggests I attempt the HTVDEV unlock code 5 times in a row.. Which did not work.
I returned my phone to stock several weeks ago. Locked the boot loader (see pic#1) Then I had something weird happen , where The phone rebooted to a "enter password to decrypt"??? I never encrypted my phone. So I read the only way around this was to do a factory reset. So, I rebooted the phone into bootloader and attempted a factory reset. The phone then rebooted and is frozen on the HTC splash screen. See pic#3
I have attempted to unlock the bootloader so I can flash a good recovery (which I cannot access, then will just reboot)
So basically I only have access to fastboot. When I plug in the phone into windows, I cannot access through ADB. (Same thing in Linux)
Any help would be appreciated.
Thanks
Have you attempted an RUU?
sauprankul said:
Have you attempted an RUU?
Click to expand...
Click to collapse
I could not get an ADB connection. I attempted to flash a new recovery, but of course with no root, s-on and bootloader locked... no dice.
charlesairman said:
I could not get an ADB connection. I attempted to flash a new recovery, but of course with no root, s-on and bootloader locked... no dice.
Click to expand...
Click to collapse
Can you get into fastboot?
sauprankul said:
Can you get into fastboot?
Click to expand...
Click to collapse
fasboot yes for me. i can get to the point to unlock the bootloader, but it freezes when i tap "yes"
Gentleman, any luck on this?
preslav88 said:
fasboot yes for me. i can get to the point to unlock the bootloader, but it freezes when i tap "yes"
Gentleman, any luck on this?
Click to expand...
Click to collapse
Yeah and all you can do from fastboot with those restrictions is, erase cache. Erase it like 3 times in a row and see if it works, who knows. I flashed cwm recovery which sometimes gets me into recovery, like 1 out of 10 recovery flashes. then you are allowed to finally use adb commands
Related
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
rootSU said:
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
Click to expand...
Click to collapse
Hmm, thanks anyway. I think this means I'm bricked. Moto E time I think.
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
TheAmazingDave said:
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
Click to expand...
Click to collapse
Can't be done.
Have the same problem and try to solve it with Motorola. No luck at the moment.
lee.jarratt said:
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Click to expand...
Click to collapse
try flashing the factory img via your bootloader/fastboot
simms22 said:
try flashing the factory img via your bootloader/fastboot
Click to expand...
Click to collapse
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
rootSU said:
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
Click to expand...
Click to collapse
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
TheAmazingDave said:
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
Click to expand...
Click to collapse
That's what all the threads about this today are saying... Including the op of this thread.
rootSU said:
That's what all the threads about this today are saying... Including the op of this thread.
Click to expand...
Click to collapse
Damn, that's really lame...
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
I'm an idiot.
I made the mistake of trying to update my Nexus 6 (Stock 5.0 encrypted, rooted, Xposed) while talking to AT&T customer service on my other phone. Distracted flashing is a bad idea. I am sure I made SEVERAL mistakes.
I too was trying to flash the new 5.1 image and got an error when running ./flash-all.sh (I'm on a Macbook). Friend suggested I try to do it by flashing the boot.img recovery.img and then system.img manually. Got the boot to flash. Recovery flashed. System failed. Unfortunately I have closed the terminal windows and don't have the errors anymore. When it failed it said something about insufficient space. So (I'm assuming this is where I f**ked up) I hit start from the boot loader screen to boot into the system and delete some things even though I had plenty of space (over 20gb). It booted fine. When I went to reboot into bootloader, I accidentally selected recovery. It booted back into TWRP which confused me. I thought best bet would be to wipe the device and start over fresh. I wiped everything and booted back into bootloader... blackness. Now I have no response from the device at all. Nothing. No response from the power button. Nothing when I plug to a charger. Just blackness. Just a pretty, 2 day old Nexus 6 (warranty replacement from T-Mobile on Tuesday).
You wiped the boot partition too? Ouch...
Last time I did that, it was with my Nook Color. Thankfully that was able to boot from SD cards...
I have a similar problem with another Nexus 7 right now. Flash went corrupt, won't boot at all. No bootloader, no Google logo, nothing.
My only hope is that the device still talks to the computer, it shows up as a Qualcomm device under Ports in Windows Dev Manager. QPST picks it up and says it's in download mode. If I can source the hex files to flash, I think I can bring it back. I'm only sharing that because it might be your only hope too. Godspeed, sir.
beachbum40 said:
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
Click to expand...
Click to collapse
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
simms22 said:
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
Click to expand...
Click to collapse
The problem is that bootloader got relocked, and the OP is unable to get to the setting to enable oem unlock. Fastboot is errors out saying to Check "Allow OEM unlock", and FAILED (remote failure).
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
efrant said:
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
Click to expand...
Click to collapse
Thank you for taking a look at my post. I have tried all the options in the bootloader menu with no dice. Things aren't looking promising for me...
You're all using the newest fastboot?
flash the factory img
edit.. nevermind, i see ive already said that
Yesterday, some bad things happened when I went to switch ROMs. Eventually, I ended up erasing my internal storage and re-locking the bootloader. I am aware that mistakes were made and I take full responsibility for my foolish actions.
So right now the problem is that I can't unlock the bootloader with the fastboot command because the "Allow OEM unlocking" box is not checked. The main problem here is that I can't simply boot into the OS and check this. I have no OS because I wiped my internal storage, including all my backups (Yes, I am an idiot.).
The phone is currently stuck on the bootloader screen. Rebooting into recovery just makes the Google splash screen flicker and it goes back to the bootloader immediately. I've seen similar threads but I haven't seen anything that mirrors my issue.
Is the phone bricked until we find a way to bypass the "Allow OEM unlocking" checkbox?
Thanks,
-PurpScurp
PurpScurp said:
Yesterday, some bad things happened when I went to switch ROMs. Eventually, I ended up erasing my internal storage and re-locking the bootloader. I am aware that mistakes were made and I take full responsibility for my foolish actions.
So right now the problem is that I can't unlock the bootloader with the fastboot command because the "Allow OEM unlocking" box is not checked. The main problem here is that I can't simply boot into the OS and check this. I have no OS because I wiped my internal storage, including all my backups (Yes, I am an idiot.).
The phone is currently stuck on the bootloader screen. Rebooting into recovery just makes the Google splash screen flicker and it goes back to the bootloader immediately. I've seen similar threads but I haven't seen anything that mirrors my issue.
Is the phone bricked until we find a way to bypass the "Allow OEM unlocking" checkbox?
Thanks,
-PurpScurp
Click to expand...
Click to collapse
Yes you are bricked.
http://forum.xda-developers.com/nexus-6/help/lock-bricked-nexus-6-t3056401
What recovery is on it?
Have you tried booting a recovery image if you don't have stock recovery?
fastboot boot recovery.img
I'd try to boot twrp may not work with the lock
fastboot erase cache got me out of trouble but I didn't relock my boot loader.
Wish I had a nexus stuck in this situation to fiddle with.
R4INS said:
What recovery is on it?
Have you tried booting a recovery image if you don't have stock recovery?
fastboot boot recovery.img
I'd try to boot twrp may not work with the lock
fastboot erase cache got me out of trouble but I didn't relock my boot loader.
Wish I had a nexus stuck in this situation to fiddle with.
Click to expand...
Click to collapse
I don't believe that command works with a locked bootloader. It had TWRP. Rebooting into recovery doesn't work at all. It just flickers the Google screen then goes back to bootloader menu.
The only thing that the phone does now is show the bootloader screen.
Simply powering on the phone brings it to the bootloader menu. I don't even have to hold power + vol up/down.
Yep it does that if you wipe the OS. There's nothing you can do at the moment.
PurpScurp said:
I don't believe that command works with a locked bootloader. It had TWRP. Rebooting into recovery doesn't work at all. It just flickers the Google screen then goes back to bootloader menu.
The only thing that the phone does now is show the bootloader screen.
Simply powering on the phone brings it to the bootloader menu. I don't even have to hold power + vol up/down.
Click to expand...
Click to collapse
Does a PC recognize it when connected? Can you get fastboot to see the device?
Evolution_Freak said:
Does a PC recognize it when connected? Can you get fastboot to see the device?
Click to expand...
Click to collapse
Yes he can. His bootloaders is locked though so he cannot unlock it.
rootSU said:
Yes he can. His bootloaders is locked though so he cannot unlock it.
Click to expand...
Click to collapse
Oh, ouch. I must have missed that part. So it's basically the same issue so many others have run into.
Evolution_Freak said:
Oh, ouch. I must have missed that part. So it's basically the same issue so many others have run into.
Click to expand...
Click to collapse
Unfortunately so.
Hi, I wanted to flash the 5.1 update to my new Nexus 6.
I went all over the basic steps.
After I unlocked the bootloader I tried to flash the image with the flash-all command.
It failed, so I remembered maybe I forgot to click on USB debugging? (This confuses me because I think I shouldn't be able to unlock bootloader without this).
When I wanted to start android I locked it first, so I would unlock it afterwards and erase everything to start as new.
Whan I locked it, I could not unlock it again. I can't access Android, neither do anything else like factory reset nor Recovery Mode. I return to the bootloader as soon as I press anything.
There are red words at the top: AP Fastboot Flash Mode (Secure). Does this means anything?
Is there any way to force unlocking the bootloader? When I try it, the phone tells me to go to Developer Options but I can't access Android.
Please HELP! Is there any way to flash a rom or android again in locked state? Recovery?
Thanks for reading this and thinking about a solution! I really hope I won't be stuck forever in bootloader.
Uh oh... Were you trying to downgrade back to LRX22C from LMY47D so that you could upgrade to LMY47M, by any chance?
If so you might be fooked.
Actually no. I was trying to upgrade from 5.01 to 5.1. I'm really scared of having my Nexus 6 bricked. I can't do anything to unlock the bootloader. Maybe I could sideload a recovery? But do I need to be unlocked?
Sent from my Nexus 7 using XDA Free mobile app
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
I hope you get it sorted out. I have read SO many bad things regarding this topic and people being screwed that they cant get back in to re-unlock after relocking
toknitup420 said:
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
I think you are 100% right. I am in panic mode, thanks. I'll do it again following every step. I'll let you know.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
toknitup420 said:
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
Click to expand...
Click to collapse
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
sotnasnauj said:
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
Click to expand...
Click to collapse
Did utry fastboot devices to see your device is connected...then fastboot oem unlock?
Also, I'm the one who has found a fix for the bricked issues when it comes to locking and unlocking the boot loader...in boot loader...when u go to recovery....what happens?
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
Now I've tried everything in that thread, when I was reading I thought flashing gpt.bin would be the solution but I can't do it, I can't flash it.. It says "Unlock before flashing". Supposedly flashing gpt.bin would allow me to flash without unlocking.
My last resource is trying this on a mac, I've read you don't need drivers so maybe it is a driver thing. I HOPE SO..
Can't access adb with my pc.
You don't need adb.
sotnasnauj said:
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
Click to expand...
Click to collapse
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
jamescable said:
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
Click to expand...
Click to collapse
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
sotnasnauj said:
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
Click to expand...
Click to collapse
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
rootSU said:
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
Click to expand...
Click to collapse
I agree because op is somehow confused.....fastboot has nothing to do with develope settings USB enabled
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
hlxanthus said:
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes.
Running
Code:
fastboot format cache
fastboot format userdata
Make sure it's FORMAT not erase.
Then walk away, watch some T.V. and don't check it for a while. (Panic mode will make it seem forever, trust me! I did the same thing as you!)
Hi,
Today i attempted to unlock my phones bootloader and flash TWRP (twrp-2.8.1.0-20142812-memul). I unlocked it fairly easily using the htc.dev website but encountered an issue when trying to flash the Recovery. The phone is stuck in the bootloader with the message ***TAMPERED*** ***UNLOCKED*** showing at the top. I cannot get off this and every attempt to get into the phone, such as by clicking on Reboot or holding the POW+VOL UP+VOL DOWN buttons, has failed, simply dumping me back on the bootloader homescreen. Does anybody know how to solve this issue?
Kind regards
James
Try re-flashing recovery from fastboot on your pc, I would even try redownloading the recovery just to be sure you didn't get a corrupted copy previously, also clear cache after flashing recovery.
The tampered message is normal so just ignore that.
You can even try rebooting boot loader and or recovery using fastboot commands, just search fastboot commands on Google and you'll find a list of relevant commands.
Jameswebb97 said:
Hi,
Today i attempted to unlock my phones bootloader and flash TWRP (twrp-2.8.1.0-20142812-memul). ...
Kind regards
James
Click to expand...
Click to collapse
there's a few problems with TWRP i notice in other phones. one of them was stuck in bootloader.
my solution was remove usb cable before rebooting.
got same issue...
Jameswebb97 said:
Hi,
Today i attempted to unlock my phones bootloader and flash TWRP (twrp-2.8.1.0-20142812-memul). I unlocked it fairly easily using the htc.dev website but encountered an issue when trying to flash the Recovery. The phone is stuck in the bootloader with the message ***TAMPERED*** ***UNLOCKED*** showing at the top. I cannot get off this and every attempt to get into the phone, such as by clicking on Reboot or holding the POW+VOL UP+VOL DOWN buttons, has failed, simply dumping me back on the bootloader homescreen. Does anybody know how to solve this issue?
Kind regards
James
Click to expand...
Click to collapse
I had that issue according to my version of TWRP. Try it with 2.8.5.0. After i re-flashed it with that, all worked fine. Give me feedback if you could solve it.
agh well after ages of trying different methods nothing worked. Even took it to my local phone shop who do software tweaks and recovery, the guy told me the entire Android OS had been removed...? Gave up and bought a new phone, thank you guys for trying anyway <3
Hi
I've been so stupid that i locked the oem setting, without any OS an recovery.
By all that, i've been searching online for a solution for days, without any luck...
So now im back with a phone that's oem locked and can't unlock it because i can't allow oem unlocking in developer settings, and can't do adb push because i do not have any recovery on the phone.
Is there anybody that can help me?
Recyclebin. said:
Hi
I've been so stupid that i locked the oem setting, without any OS an recovery.
By all that, i've been searching online for a solution for days, without any luck...
So now im back with a phone that's oem locked and can't unlock it because i can't allow oem unlocking in developer settings, and can't do adb push because i do not have any recovery on the phone.
Is there anybody that can help me?
Click to expand...
Click to collapse
Can't you get to the bootloader and fastboot the stock google images? This is a N6, right?
@ktmom: He can get to the bootloader, but it's locked, which means fastboot is not an option. Worse, he apparently has no recovery installed so he can't sideload an OTA.
The OP is screwed.
Strephon Alkhalikoi said:
@ktmom: He can get to the bootloader, but it's locked, which means fastboot is not an option. Worse, he apparently has no recovery installed so he can't sideload an OTA.
The OP is screwed.
Click to expand...
Click to collapse
Yeah, spaced
What about running recovery on the pc? I've never done that. I guess it requires an unlocked bootloader also.
I dunno, this is an N9 thread as is this one, but if I was in this position, I think I'd read through these.
I didn't think of that. It may work. Then he can sideload.
Recyclebin. said:
Hi
I've been so stupid that i locked the oem setting, without any OS an recovery.
By all that, i've been searching online for a solution for days, without any luck...
So now im back with a phone that's oem locked and can't unlock it because i can't allow oem unlocking in developer settings, and can't do adb push because i do not have any recovery on the phone.
Is there anybody that can help me?
Click to expand...
Click to collapse
Power up arrow to get into bootloader mode
might have to unlock bootloader at this point (dont remember the exact process you can google it) should be another fastboot command
fastboot flash recovery preferably twrp
then you should be able to load up a rom
ktmom said:
Yeah, spaced
What about running recovery on the pc? I've never done that. I guess it requires an unlocked bootloader also.
I dunno, this is an N9 thread as is this one, but if I was in this position, I think I'd read through these.
Click to expand...
Click to collapse
How can i make a running recovery on a pc?
Tried to search for it, but i cant find anything on it
Code:
fastboot boot recovery.img
The above command sends the device into recovery mode using an image stored on a PC's hard drive. From there the owner of the device can use the recovery just as if it were installed in the /recovery partition of the device's internal storage. Files that the owner of the device wishes to use are stored in the device's internal storage.
It won't help the OP however. An unlocked bootloader is one of the pre-requisites.
Cant boot up a live recovery either, because of tge locked bootloader...
Anyone got other ideas? Im really lost with this one
Contact Lenovorola and pay for the privilege of having your device serviced. You're totally screwed.