Database Develop

Nexus 6 bricked and locked bootloader!?!?!?

Hi
I was side loading the new 5.1 to both my N5 and N6. N5 was ALL GOOD. N6 however is not. After waiting for a rediculous time for it to reboot when it was stuck on the white Google Image, I disconnected the USB cable. Now it won't boot past the Google screen at all.
I can see it as a fastboot device and can boot into bootloader. There appears to be no recovery. When I try to re flash or side load, I get the warning along the lines of 'unlock before flash'.
So........can anyone assist please?
Thanks in advance of responses.
Cheers
Thommo

Look here..
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
That might help, otherwise since you can get into BL mode can you try flashing stock recovery from the image you originally had? I guess I don't know if that works or not or if that is what you were trying to reflash..
fastboot command to flash recovery is
fastboot flash recovery recovery.img <--replace recovery.img with the name of the recovery you are trying to flash. It's most likely recovery.img if you are taking it from a stock image.
Good luck.

Ha66is said:
Hi
I was side loading the new 5.1 to both my N5 and N6. N5 was ALL GOOD. N6 however is not. After waiting for a rediculous time for it to reboot when it was stuck on the white Google Image, I disconnected the USB cable. Now it won't boot past the Google screen at all.
I can see it as a fastboot device and can boot into bootloader. There appears to be no recovery. When I try to re flash or side load, I get the warning along the lines of 'unlock before flash'.
So........can anyone assist please?
Thanks in advance of responses.
Cheers
Thommo
Click to expand...
Click to collapse
did you solve? how you solved?
i have a similary problem with my nexus 9.. locked bootloader and can't do anythings.. please help me

we need help
paviz96 said:
did you solve? how you solved?
i have a similary problem with my nexus 9.. locked bootloader and can't do anythings.. please help me
Click to expand...
Click to collapse
i have the same prob bro i am waiting for a fix i still have hope

So the lesson learned is: Always unlocking the bootloader once you have the phone/tablet should be the first thing to do so you can fix issues !

I also need someone to find a way to unlock the bootloader ! btw try booting into recovery (it will say no command) and then hold the volume up and power for 10 seconds and then let go, then select adb sideload ...let it time out...then try to clear data and cache. I tried to clear that when i had a bootloop but wouldnt work, i got it to work by selecting adb sideload and then letting it time out(takes a while to timeout)..must mount the partitions...

jordy787 said:
I also need someone to find a way to unlock the bootloader ! btw try booting into recovery (it will say no command) and then hold the volume up and power for 10 seconds and then let go, then select adb sideload ...let it time out...then try to clear data and cache. I tried to clear that when i had a bootloop but wouldnt work, i got it to work by selecting adb sideload and then letting it time out(takes a while to timeout)..must mount the partitions...
Click to expand...
Click to collapse
If you do not have TWRP recovery, there's nothing you can do. RMA.

Evolution_Tech said:
If you do not have TWRP recovery, there's nothing you can do. RMA.
Click to expand...
Click to collapse
think i can rma with a cracked glass but still works?

jordy787 said:
think i can rma with a cracked glass but still works?
Click to expand...
Click to collapse
Doubt it. There are some GooglePlay versions that have been RMA'd as it was a promo. Still gonna go back to original Account for the RMA.

stupid question . if this is Motorola you cant use RSD this with the correct FXZ. or they no longer use this since its a nexus.

[Q] Nexus 6 stuck in bootloop

Ok so, this is my first post on xda, and because my (sprint) Nexus 6 is stuck on a boot loop. When powered on, goes to googles boot animation, then says "Android is starting... optimizing apps # of 127, and then once it reaches the end, it just goes into the animation again. I somehow have usb debugging disabled, and oem locked. I have no idea what i did to cause this, but esentially I unlocked the phone, and rooted it, and then i tried to disable encryption, and thats where things went south. clearing chache does not help, niether does factory reset. Attempts at flashing factory images are fails. even the guy at sprint cant do it. Besides fixing it, my only other option is to send it in to google and get a reaplacement...for $200. PLease help me solve this issue and i will be eternally grateful :3

SorryLols said:
Ok so, this is my first post on xda, and because my (sprint) Nexus 6 is stuck on a boot loop. When powered on, goes to googles boot animation, then says "Android is starting... optimizing apps # of 127, and then once it reaches the end, it just goes into the animation again. I somehow have usb debugging disabled, and oem locked. I have no idea what i did to cause this, but esentially I unlocked the phone, and rooted it, and then i tried to disable encryption, and thats where things went south. clearing chache does not help, niether does factory reset. Attempts at flashing factory images are fails. even the guy at sprint cant do it. Besides fixing it, my only other option is to send it in to google and get a reaplacement...for $200. PLease help me solve this issue and i will be eternally grateful :3
Click to expand...
Click to collapse
OK. So...do u know how to use fastboot? If yes...do a fastboot format data and fastboot format cache..also...do u have stock recovery or twrp?

I got that bootloop when I flashed a bad boot image. Easily fixed by flashing a good one...
But, let's clarify a couple of things:
Did you relock your bootloader while flashing?
Do you have a custom recovery (TWRP)?
If the answer to both of those are "yes", you might get out of this by using these commands:
fastboot format userdata
fastboot format cache
This will allow you to enter TWRP and restore a backup or flash a ROM.
If you didn't relock your bootloader you shouldn't have any problems flashing. Clarify what your trying to do, please (are you using a toolkit, etc).
If the answers are 1-yes and 2-no, then your probably SOL.

Didgeridoohan said:
I got that bootloop when I flashed a bad boot image. Easily fixed by flashing a good one...
But, let's clarify a couple of things:
Did you relock your bootloader while flashing?
Do you have a custom recovery (TWRP)?
If the answer to both of those are "yes", you might get out of this by using these commands:
fastboot format userdata
fastboot format cache
This will allow you to enter TWRP and restore a backup or flash a ROM.
If you didn't relock your bootloader you shouldn't have any problems flashing. Clarify what your trying to do, please (are you using a toolkit, etc).
If the answers are 1-yes and 2-no, then your probably SOL.
Click to expand...
Click to collapse
The answers are indeed 1-yes and 2-no. What is SOL an is there any way of fixing it?

SorryLols said:
The answers are indeed 1-yes and 2-no. What is SOL an is there any way of fixing it?
Click to expand...
Click to collapse
SOL = "S**t Out of Luck".
There is currently no know way of fixing it.
Your only avenue is to RMA it.

Closed

I got into problems yesterday. I've encrypted my device some months ago and it was working fine.
Last night I don't what happend but it switched off itself and once i tried to start it, I saw bootsreen, then lock screen and after inserting pin, nothing happens, I only see black screen with some light in the background.
Now Issue it, I have soo many important files on my device, is there any way to copy that data? Because i'm not able to access it via usb since my device is not able to reboot itself properly after lockscreen..
I will appreciate any help, and will give reward once i'll get my data back.
Thank you.
Ps: I'm using 5.0.2 (XT1068)
Pss: I tried to wipe cache but it didn't helped.

No one?
I'm able to boot into fastboot and adb also but in ADB my device is listed as unauthorized device and i'm not able to see confirmation dialogue on device screen :/

transp0rt3r said:
I got into problems yesterday. I've encrypted my device some months ago and it was working fine.
Last night I don't what happend but it switched off itself and once i tried to start it, I saw bootsreen, then lock screen and after inserting pin, nothing happens, I only see black screen with some light in the background.
Now Issue it, I have soo many important files on my device, is there any way to copy that data? Because i'm not able to access it via usb since my device is not able to reboot itself properly after lockscreen..
I will appreciate any help, and will give reward once i'll get my data back.
Thank you.
Ps: I'm using 5.0.2 (XT1068)
Pss: I tried to wipe cache but it didn't helped.
Click to expand...
Click to collapse
If you have unlocked bootloader then TWRP should be able to mount /data so you could copy it to your pc using adb.

LuK1337 said:
If you have unlocked bootloader then TWRP should be able to mount /data so you could copy it to your pc using adb.
Click to expand...
Click to collapse
Sadly it's not, I'm gonna take to nearest service center tomorrow, if they are unable to do it, i guess try this TWRP method.
If you have any other idea, let me know.
Thanks

transp0rt3r said:
Sadly it's not, I'm gonna take to nearest service center tomorrow, if they are unable to do it, i guess try this TWRP method.
If you have any other idea, let me know.
Thanks
Click to expand...
Click to collapse
Flashing TWRP will require bootloader unlock which wipes your data.

You can boot in twrp without install
Fastboot boot twrp-2.xxxx.img
Then you can use adb to pull files.

reddevilx said:
You can boot in twrp without install
Fastboot boot twrp-2.xxxx.img
Then you can use adb to pull files.
Click to expand...
Click to collapse
It will require unlocked bootloader (unlocking = wipe data)

LuK1337 said:
It will require unlocked bootloader (unlocking = wipe data)
Click to expand...
Click to collapse
Yeah right, sadly I had to wipe my all data. :/
Still thanks for the advice.

Have I really bricked a Nexus phone??

Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.

claytonjn said:
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you lock the bootloader just to be clear?

bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.

gee2012 said:
Did you lock the bootloader just to be clear?
Click to expand...
Click to collapse
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
simms22 said:
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
Click to expand...
Click to collapse
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk

have you tried fastboot oem unlock again ?

uicnren said:
have you tried fastboot oem unlock again ?
Click to expand...
Click to collapse
Yes, it says it needs to be enabled in developer options
Sent from my Developer Edition Galaxy S5 using Tapatalk

when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.

uicnren said:
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
Click to expand...
Click to collapse
It says it will reboot in 5 seconds, but after 5 seconds the screen just goes blank. It appears the device is off, but maybe not.
Do you know what adb commands I would need to use to recover from this state?
Sent from my Developer Edition Galaxy S5 using Tapatalk

claytonjn said:
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
Click to expand...
Click to collapse
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.

well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.

simms22 said:
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
Click to expand...
Click to collapse
Unfortunately that is not working for me (Not allowed in locked state!)
uicnren said:
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
Click to expand...
Click to collapse
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.

Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...

claytonjn said:
Unfortunately that is not working for me (Not allowed in locked state!)
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Click to expand...
Click to collapse
If you have TWRP, boot to bootloader and use the following fastboot commands:
fastboot format userdata
fastboot format cache
Then boot to TWRP, connect to PC. Download a ROM to your PC and drag and drop in the root of internal storage. Then flash the ROM from TWRP, boot up, enable OEM unlock. Then boot back to bootloader and:
fastboot oem unlock
You should be good after that.

holeindalip said:
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
Click to expand...
Click to collapse
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.

claytonjn said:
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
Click to expand...
Click to collapse
Follow my instructions listed above.

Evolution_Tech said:
Follow my instructions listed above.
Click to expand...
Click to collapse
II'm attempting that now.but fastboot format userdata and fastboot format cache fail. after booting into twrp the Nexus shows up in My Computer, but internal storage does not. I can push a ROM zip to the device with adb, but haven't figured out how to flash it yet because touch doesn't work...

SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!

claytonjn said:
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
Click to expand...
Click to collapse
glad you got it back, persistence pays off.

Lesson learned today? QUIT RE-LOCKING YOUR BOOTLOADER!

You can lock boot loader, you just have to make sure your phone boots first before locking it

Can I flash back to stock through adb over network?

So yeah, phone has not been charging due to an issue with the USB port on my phone. I want to flash it back to stock to send it back in on warranty, problem is I've only ever done that via USB, which is conveniently kaput.
Is there a way to do it through WiFi and adb over network, or am I screwed?

Apoplectic1 said:
So yeah, phone has not been charging due to an issue with the USB port on my phone. I want to flash it back to stock to send it back in on warranty, problem is I've only ever done that via USB, which is conveniently kaput.
Is there a way to do it through WiFi and adb over network, or am I screwed?
Click to expand...
Click to collapse
You are pretty much screwed. It has to be a wired connection and if you send it back as is you will most likely be charged for a new device.

Gotcha, I'll Terry to see if I can flash a stock rom and recovery through twrp, and try to figure out how to relock the bootloader through a terminal emulator or something.

Apoplectic1 said:
Gotcha, I'll Terry to see if I can flash a stock rom and recovery through twrp, and try to figure out how to relock the bootloader through a terminal emulator or something.
Click to expand...
Click to collapse
you can't do it, no matter how hard you try.

simms22 said:
you can't do it, no matter how hard you try.
Click to expand...
Click to collapse
I've managed to flash a rooted stock ROM, used Flashing to install a stock recovery.img, uprooted and an about to take an OTA to get back to full stock.
I really only have to relock the bootloader at this point. Haven't the faintest idea on how to go about that though, every attempt at even trying connect vid adb over network has failed.

Apoplectic1 said:
I've managed to flash a rooted stock ROM, used Flashing to install a stock recovery.img, uprooted and an about to take an OTA to get back to full stock.
I really only have to relock the bootloader at this point. Haven't the faintest idea on how to go about that though, every attempt at even trying connect vid adb over network has failed.
Click to expand...
Click to collapse
don't know the answer to this, but if you have the stock recovery now and you boot into recovery and select wipe / factory reset, maybe that will return it fully to stock e.g. locked bootloader.
See this thread