Database Info

[Q] Bricked Nexus S

Hi
I have bricked my nexus s when I loaded a ROM that I downloaded.
I have used several different ROMs and had no problems.
I asume this ROM was dodgey.. Anyway I get no screen at all, the menu control at the botom of the screen lights up but that is it.
I can get to it using fastboot but it won't load any ROMS. There is no action on the Nexus screen itself.
Is there a guide using fastboot to recover this also what file/files will I need to download?
Thanks in advance any help would be much appreciated.....

If you are here looking for help you need to give us more information.
What model Nexus S do you have?
What rom did you flash?
What have you done sense flashing the rom?
My guess is you flashed a rom that isn't for your model phone. So you either have SAMOLED or SLCD. I'm guessing the rom you installed was for the screen type you don't have.
So let us have some more details so we can help.
Sent from my Nexus S 4G using xda premium

Sounds like a call for the mighty Odin...
Sent from my Nexus S 4G using xda premium

And u can't get into recovery using the button method?
Sent from my Nexus S using XDA App

If you can get fastboot to work, you can flash all partitions including system. Don't worry, this is an easy fix.

Hi Again guys
Firstly thanks a lot for the replys I really appreciate it.
Its a 3g the model no: is GT-19023.
Its SAMOLED that much I know.
I cannot get into recovery I can get fastboot to recognise the phone but nothing on the screen.
I have downloaded a stock rom and extracted the boot, recovery & system.img files.
I have followed the instructions below and all seems to work till I get to the system. it fails with the following message. The other steps seem to work OK.
"FAILED (remote write failed)"
I have also tried this with several other ROMs I know work on wifes Nexus s and still no luck. Some allow the system to be flashed but the phone still won't boot.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
Any help would be great
I also downloaded ODIN but cant get it to work; It does not recognise that it is connected to the USB, but fastboot does!. (Is there a step by step guide to using it?)
Sorry for sounding like noob, but I have read everything and looked up these forums and tried a lot before asking for help.
GL

If your phone is a Gt-i9023 it is SLCD!!!!! Not SAMOLED.
Again what rom did you flash? Post a link to it. I still think you flashed a rom for SAMOLED when you have SLCD.
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
If your phone is a Gt-i9023 it is SLCD!!!!! Not SAMOLED.
Again what rom did you flash? Post a link to it. I still think you flashed a rom for SAMOLED when you have SLCD.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
BTW, so 9020 ROMs are incompatible with 9023? I am aware of differences between those devices, but when I looked in "Development" section, there is no info, about compatibility with 9020a/t/9023

http://forum.xda-developers.com/showthread.php?t=955719
pretty sure that is the link to the ROM.
I tried to restore using another stock ROM (I backed it up from another Nexus that was only rooted and stock)... Yes it was exactly the same phone model etc.
The problem is now the error is saying ===FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)===
I tried that (the unlock command) and the prompt just types three dots (...) and then hangs there. I have tried removing the battery etc and the same issue.
I am happy to erase the phone to nothing and load another image.
It seems that maybe this phone is cooked....
I hope not ==shattered==

k_myk said:
BTW, so 9020 ROMs are incompatible with 9023? I am aware of differences between those devices, but when I looked in "Development" section, there is no info, about compatibility with 9020a/t/9023
Click to expand...
Click to collapse
ROMs are compatible between those variants! But, if you're flashing some stock ROM bundles you can flash wrong one. Because bundles contain rom, kernels and radios for specific device with specific drivers. In that case you can flash wrong driver for your display, or even something worse...

Follow what it says, unlock your bootloader first.
Sent from my GT-P1000 using xda premium

glockman63 said:
http://forum.xda-developers.com/showthread.php?t=955719
pretty sure that is the link to the ROM.
I tried to restore using another stock ROM (I backed it up from another Nexus that was only rooted and stock)... Yes it was exactly the same phone model etc.
The problem is now the error is saying ===FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)===
I tried that (the unlock command) and the prompt just types three dots (...) and then hangs there. I have tried removing the battery etc and the same issue.
I am happy to erase the phone to nothing and load another image.
It seems that maybe this phone is cooked....
I hope not ==shattered==
Click to expand...
Click to collapse
Your link still does not tell us which rom you flashed....
You can't flash a rooted rom through fastboot without unlocking the bootloader first. Sounds like you need to restore a factory rom with Odin.
Sent from my Nexus S 4G using xda premium

Hi all
I got this sorted out and am really happy to have my phone going again.
For those interested or in the same predicament I was in please read on as this is how I managed to make this phone go again.
Please rmemeber this phone was really bricked no screen at all jus the menu light like in the picture in my first post.
As I stated I could get fast boot to see the phone. And also Odin. (Still no screen at all)
I had another phone the same with the original rom on board.
I rooted this phone and installed ClockworkMod recovery ad used this to backup the standard ROM.
I then rebooted this phone an copied these files from the backup into my fastboot directory (boot.img, recovery.img, system.img)
I then connected my dead phone up to my PC and ran the following commands.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
I then removed the battery and to my astonisment the phone booted normally into the standard ROM.
WOW I was over the moon I have since installed my MIUI Rom and using my phone happily...
Thanks everyone for your input..

Rem3Dy said:
Your link still does not tell us which rom you flashed....
You can't flash a rooted rom through fastboot without unlocking the bootloader first. Sounds like you need to restore a factory rom with Odin.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I've got a phone in the same state I am trying to revive for a guy. With the bootloader locked download mode gives you a locked bootloader screen. Odin sends the flash images to the phone, the phone verifies them but then refuses to flash them (presumably due to the bootloader being locked). The bootloader won't unlock so there is no way to flash a rom to fix the phone.

glockman63 said:
Hi all
I got this sorted out and am really happy to have my phone going again.
For those interested or in the same predicament I was in please read on as this is how I managed to make this phone go again.
Please rmemeber this phone was really bricked no screen at all jus the menu light like in the picture in my first post.
As I stated I could get fast boot to see the phone. And also Odin. (Still no screen at all)
I had another phone the same with the original rom on board.
I rooted this phone and installed ClockworkMod recovery ad used this to backup the standard ROM.
I then rebooted this phone an copied these files from the backup into my fastboot directory (boot.img, recovery.img, system.img)
I then connected my dead phone up to my PC and ran the following commands.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
I then removed the battery and to my astonisment the phone booted normally into the standard ROM.
WOW I was over the moon I have since installed my MIUI Rom and using my phone happily...
Thanks everyone for your input..
Click to expand...
Click to collapse
So it wasn't bricked...... glad you got it working.
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
So it wasn't bricked...... glad you got it working.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Your lucky your bootloader was already unlocked. Once a phone gets borked like that unlocking the bootloader is impossible and Odin refuses to flash.

jboxer said:
Your lucky your bootloader was already unlocked. Once a phone gets borked like that unlocking the bootloader is impossible and Odin refuses to flash.
Click to expand...
Click to collapse
Dude.... stop spreading incorrect information. The bootloader state does not affect Odin. Please understand this!
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
Dude.... stop spreading incorrect information. The bootloader state does not affect Odin. Please understand this!
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes it does! Or at least on the phone I am trying to repair it has. On the phone I am trying to repair when you go into download mode you get a screen that says to unlock the bootloader. Odin connects and sends the file but then the phone refuses to flash it. If that is not the bootloader being locked affecting Odin then I don't know what is. I have flashed with Odin hundreds of times with Galaxy S phones so I know what I am doing. I have never seen Odin send a file, have the phone say it is verified and then refuse to flash it, but that is what is happening with this Nexus S with an unlockable bootloader. The files are the correct files and Odin is the correct version. If you are so smart, then you tell me what to do to get Odin to accept the flash and you will be my hero.
I have attached a shot of the phone in "download mode." Notice it is a warning about the bootloader being locked, not the normal screen with the Android bot and a shovel. Odin sees the phone (connected to computer as Samsung device) but once the phone verifies the file nothing else happens. The file is never flashed. Notice in the photo there is no YES and NO selections to unlock the bootloader like you get when you issue the "fastboot oem unlock" command. In Fastboot when that command is issued you get the normal unlock the bootloader screen but when you select YES and press Power nothing else happens. It just hangs no matter how long you leave it. A battery pull is the only thing you can do and when you turn the phone back on the bootloader is still locked.

If you are getting g stuck there you may have a hardware issue. I still think you need to try flashing through fastboot.
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
If you are getting g stuck there you may have a hardware issue. I still think you need to try flashing through fastboot.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Cannot flash in fastboot. Sends over image then says fail due to bootloader being locked. If you have a signed update.zip with android-info and android-product files that can be flaahed in fastboot mode let me know where it can be downloaded from.
Sent from my LG-P999 using Tapatalk

[Q] Stuck at X screen

Obviously I'm a noob, so sorry if this is stupid or there is an obvious answer (I've spent a lot of time looking and couldn't find it though). I was having problems with my phone so decided to flash back to stock and relock it to 'start again'.
Maybe that wasn't a great idea because I've had lots of problems since then. When I try to flash back to stock using nexus root toolkit I get "failed (remote: invalid bootloader)" and the phone finishes still in bootloader. There was a suggestion to force flash, but given the warnings around that I'm pretty nervous about doing that. If I then start my phone up it stays on the google screen for quite a while and then gets stuck on the X screen (it isn't frozen because the animation keeps running, but nothing else happens, even if I leave it for an hour).
I did a bit more reading and tried wiping the dalvik cache and cache. It then said it was upgrading android, optimising apps etc, but then got stuck again. I tried resetting again and the phone now restarts when I push the off button and slowly goes through both the google screen and X screen.
This might be a stupid problem, but I'm stuck so any help would be great.

Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app

http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
Follow this carefully step by step using method 2. Be extremely careful flashing the boot loader, in fact you can probably skip that part. As long as your boot loader is always in tact it's virtually impossible to brick. As of right now you're stuck in what's called a boot loop. Most likely, either your boot.img (not the same as boot loader) or system.img (aka ROM/firmware) is messed up and is causing it.
Welcome to modding, have fun, but be smart
Sent from my Nexus 5 using xda app-developers app

Chromium_ said:
Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).

beshakey said:
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).
Click to expand...
Click to collapse
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app

Chromium_ said:
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks, that worked. But having done it when I reboot the phone it does the same thing (hangs of the Google screen for a long time then moves to the X screen and stays there). My phone is rooted and I have clockworkmod installed, so I selected fix root when asked, not sure if that is relevant?

Did you continue to follow the guide and flash the stock images in fastboot
Sent from my Nexus 5 using xda app-developers app

Yeah I did. I got the message "FAILED (remote:invalid bootloader image) and archive does not contain 'boot.sig' 'recovery.sig' and 'system.sig'. Everything else was OKAY. Put into recovery mode fine (with clockworkmod), wiped data and rebooted (fixing root when asked) but the problem described above remains.

More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh

beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
And you are following the factory image flashing guide that has been provided above?
Can you try going through the guide again, and tell us the specific errors that you are encountering.

And use method two, not the first one that talks about running the flash all script. You should be doing command's like "fastboot flash boot boot.img"
Sent from my Nexus 5 using xda app-developers app

beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
Don't worry, you'll get it, eventually. When you first start doing this kind of thing, it takes some getting used to because you have to read VERY carefully, and perform each step EXACTLY as stated. Computers are absolutely unforgiving of even the tiniest mistake, so you have to take your time, and be patient when you have to start all over. But, it's a challenge, and a learning process, and a lot of fun, once you get the hang of it.
Sent from my Nexus 5

OK, step by step. If you need more detail yell out.
1) I've downloaded ADB and Fastboot
2) If I put ADB devices into the command prompt I don't get any devices listed. But if I put in Fastboot devices I get the serial number of my phone
3) Previously I'd been using method one. So I now extract the image for hammerhead krt16m to my f:\ drive. I've also extracted radio-hammerhead-M8974A-1.0.25.0.17 and bootloader-hammerhead-HHZ11d to the same location and renamed them to radio.img and bootloader.img respectively
4) Phone is connected to computer and in fastboot (and detected by fastboot devices)
5) In command prompt when I type in fastboot flash bootloader f:/bootloader.img I get the error message FAILED (remoteL invalid bootloader image).
6) Flashed radio.img and rebooted bootloader and system.img (no reboot) without any errors (although they took a while)
7) Flashing userdata.img got the error 'FAILED (remote: flash write failure)
8) Performed all the remaining commands without any errors (when erasing the cache I got the message 'Did you mean to fastboot format this partition? erasing 'cache'... OKAY
9) Entered recovery mode. Earlier when I did this it was fine, but now (like when I try to start the phone) the screen lights up but no text etc appears
10) At this point I'm stuck, as I can't see the cwm text so can't select wipe data/factory data reset (although I did do this as part of earlier attempts)
From the 'on but no text' state, I can using the on button to restart into the same state or can enter fastboot (where text etc appears fine)

One at the boot loader you said you put f:/bootlaoder.img that was wrong, no drive letter. You do not need to flash your boot loader though anyways. Avoid doing that unless you have to, it is the only thing that will brick your phone.
You said system.img flashed fine, did not see any Menton of a boot.img or recovery.img. you need all three of these.
So, start over again. Make sure you flash a boot.img system.img and recovery.img separately. DO NOT flash the bootloader.img unless you have to (to update). Again, the boot loader is the one thing that will brick your phone if done wrong.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 07:31 AM ---------- Previous post was at 07:28 AM ----------
Sorry I just read through that tutorial and it does tell you to use drive letters. Im used to flashing with my files in the location of fastboot so I don't need to do that.
Sent from my Nexus 5 using xda app-developers app

@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode

Good catch.
Sent from my Nexus 5 using xda app-developers app

samersh72 said:
@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode
Click to expand...
Click to collapse
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?

beshakey said:
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?
Click to expand...
Click to collapse
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app

travisjustin said:
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?

beshakey said:
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?
Click to expand...
Click to collapse
4.3? The nexus 5 ships with kitkat 4.4 ...there is no 4.3 for it.
Sent using xda-developers app

[Q] Can't boot, recovery keeps dissapearing

I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.

aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
@bitdomo might be able to help you lol
Might be bad eMMC or something?

when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?

aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress

simms22 said:
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
Click to expand...
Click to collapse
Hey I'm using "fastboot flash recovery recovery.img" and that's what I've used in the past. I've had a fully functioning rom with fully functioning recovery for a while until yesterday.

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok thanks I'll try this and check the text in fastboot after work today. Thanks for the responses guys.
After reading some more last night I'm afraid it's an emmc problem but I like to be proven wrong sometimes.

Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447

beekay201 said:
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
Click to expand...
Click to collapse
I actually have that thread open on my computer. It was my next attempt of repair before starting the thread late last night. Thanks for the suggestion I will certainly try it.
Update: I tried pushing Philz recovery to the phone which seemed to work fine until I selected go to recovery mode. It just went back to that barely light black screen. I'll try again when I get home. Going to try Bitdomo's advice about locking bootloader first.

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Out of curiosity what's the reason for using two brands, or were they just available so they were used?

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Bitdomo I'm trying the Flashtool but it's staying at 0% on the firmware update and nothing is popping up on computer or in Device Manager. Had no connection issues prior to the brick or with adb/fastboot. My Ports aren't evening showing at all in DM even if I select show hidden devices.

aburn95 said:
How do I lock the bootloader without being able to put the .zip on my internal memory?
Click to expand...
Click to collapse
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I honestly wanted to do that but it seemed too easy. I was trying to lock it like I did before when i had to send original back to T-Mobile. Sorry and thanks.

bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok so it stayed locked so that's a start. I'm back in download mode again but it's staying at 0% and nothing on computer.

I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:

Unzip the zip and use manual flash commands. Clikc the link in my signature and read my "adb and fastboot. What is it?" thread of you're unsure of the commands.
Sent from my Nexus 5 using Tapatalk

aburn95 said:
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Click to expand...
Click to collapse
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB

bitdomo said:
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
Click to expand...
Click to collapse
Sorry I meant to tell you yesterday... D820H 16GB. Should I still be able to toggle the tamper tag so they will take it back with no problems? Or am I screwed?

aburn95 said:
Sorry I meant to tell you yesterday... 820H. Should I still be able to toggle the tamper so they will take it back with no problems? Or am I screwed?
Click to expand...
Click to collapse
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.

bitdomo said:
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
Click to expand...
Click to collapse
Ok thanks. I haven't quite figured out the adb sideload function yet. I tried doing it through TWRP but it just sits there and does nothing after selecting. Maybe I'm trying the wrong thing. I got my phone from T-Mobile so I'll need to solve this. Thanks for the help.

This phone is being a real a-hole. I'm trying to boot to stock recovery but it just sits on a screen with a really big android with wiggling antennae. I pressed up+power many times but it stayed that way. So I tried booting to TWRP again and it did but went immediately to an "OpenRecoveryScript," had a little bar at the bottom for a while with some other stuff on the screen, then turned off.
I tried stock recovery again and it went to the little dead android this time but still nothing when I press up+power.

my nexus 5 not booting.not unlocking.i can not to go to recovery mode.stuck on google

nexus 5
when I turning on nexus , stuck on google logo
when I want to go to recovery mode , stuck on black screen
when I want to unlocking , stuck on black screen ... because it have to restarting
my nexus is locked ... not unlock
my nexus was on android 6.0.1
please help me ....
what should I do????

sorry but its like ur emmc is dead.
try to flash mob30x firmware and see what happens, maybe rewriting the entire emmc unbricks it.
did u leave it alone unlocking for a few hours?
Sent from my Nexus 5 CAF using Tapatalk

Can the phone enter fastboot mode? Is the bootloader unlocked? If yes to both, try flashing a stock kit kat rom, including user data.img.

audit13 said:
Can the phone enter fastboot mode? Is the bootloader unlocked? If yes to both, try flashing a stock kit kat rom, including user data.img.
Click to expand...
Click to collapse
its not unlocked.
the dude needs to reflash the whole partition system hoping for some luck
Sent from my Nexus 5 CAF using Tapatalk

santi1993 said:
sorry but its like ur emmc is dead.
try to flash mob30x firmware and see what happens, maybe rewriting the entire emmc unbricks it.
did u leave it alone unlocking for a few hours?
Sent from my Nexus 5 CAF using Tapatalk
Click to expand...
Click to collapse
how to flash? with wath? help me plz or get a link about mob30x
No ... suddenly the phone was off ... for no reason

santi1993 said:
sorry but its like ur emmc is dead.
try to flash mob30x firmware and see what happens, maybe rewriting the entire emmc unbricks it.
did u leave it alone unlocking for a few hours?
Sent from my Nexus 5 CAF using Tapatalk
Click to expand...
Click to collapse
I have nexus 5 ...not7

The bootloader must be unlocked first.

audit13 said:
The bootloader must be unlocked first.
Click to expand...
Click to collapse
how? I was very try... but not unlocking...because can not restart after unlocking...stuck on black screen

You need adb support in order to unlock your bootloader. Open cmd/terminal if you are on Mac an type "adb devices" press enter an you should see your phone listed below
After you see your device listed.
Type "fastboot oem unlock" an press enter this will unlock your bootloader and after this you need to flash a custom recovery.
Here is a link which explains in detail how to do all the steps that I told you briefly: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Follow the instructions word by word an you can restore your dead nexus 5.
Here is the link to get the files https://developers.google.com/android/images
Press the thanks button if I helped.

You need to boot into fastboot mode on the phone and use fastboot commands to unlock the bootloader. Adb commands will not work and are not necessary with the phone in fastboot mode.

audit13 said:
You need to boot into fastboot mode on the phone and use fastboot commands to unlock the bootloader. Adb commands will not work and are not necessary with the phone in fastboot mode.
Click to expand...
Click to collapse
This. ^^^ Fastboot is the bootloader screen. You still need fastboot drivers.
Sent from my Nexus 9 using Tapatalk

Hi, I've a similar issue: my N5 had some trouble with the power button, now I just solve, but unfotunately the phone is still charging android( is blocked on the screen with the flowers).
I tried to unlock or re-flash android stock with NRT but after the first operation the phone don't want to charge android.
Any suggestion?

Need help asap pixel bricked

Hi, I really need your assistance for my pixel. I locked my bootloader after unrooting my phone. This process totally bricked my phone(I can't even get to the booting process of the phone) (I get a message saying that my phone is corrupt). I am able to gain access to my fastboot. So I was wondering if there was a way for me to flash the factory image to my phone and get it to work again. Please of there is anything you can do, please help me.

Its_joey_k23 said:
Hi, I really need your assistance for my pixel. I locked my bootloader after unrooting my phone. This process totally bricked my phone(I can't even get to the booting process of the phone) (I get a message saying that my phone is corrupt). I am able to gain access to my fastboot. So I was wondering if there was a way for me to flash the factory image to my phone and get it to work again. Please of there is anything you can do, please help me.
Click to expand...
Click to collapse
I'm really afraid there's nothing you can do. Before relocking the bootloader, you must go back to an approved stock firmware. (See, when you rooted it, you changed it.)

quangtran1 said:
I'm really afraid there's nothing you can do. Before relocking the bootloader, you must go back to an approved stock firmware. (See, when you rooted it, you changed it.)
Click to expand...
Click to collapse
I unrooted my device, so then after I can lock my bootloader. I'm just wondering if that's how I was supposed to do it.

If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot

hackworks said:
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
Click to expand...
Click to collapse
Is there any way you could lead my step by step. I don't want to screw up my phone even more. + I'm new to the community and don't know much.

You can use the fastboot continue command.
This will boot up your phone normally and then you will be able to go to developer settings and enable oem unlocking again.
After this you will be able to unlock from fastboot again.
http://forum.xda-developers.com/pixel/help/accomplished-hardbricked-pixel-d-t3516717

Its_joey_k23 said:
Is there any way you could lead my step by step. I don't want to screw up my phone even more. + I'm new to the community and don't know much.
Click to expand...
Click to collapse
If you can put your phone in fastboot mode, you're not bricked yet.

hackworks said:
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
Click to expand...
Click to collapse
You saved my life! Thank you.