Database Info

[Q] Did I brick my Nexus 5?

Hello...
I have a horrible question. Did I ruin my Nexus 5? The short story, or just the problem I am having is that the phone is "Boot Looping", it launches as far as the 4-color animation, restarts, and repeats.
I downloaded WugFresh's toolkit and attempted to flash to stock. At this point the phone was on and operating, but the radio didn't seem to be working properly after I attempted to return to stock using a guide on youtube. When using this guide I got as far as the final command, fastboot -w update image-hammerhead-krt16m.zip. Every time I attempted to run this command a dialog box would inform me that fastboot had stopped working. So I attempted to use the toolkit Provided by WugFresh. I selected the option for a phone that was on and functioning and clicked "Flash Stock + Unroot. Everything went as I expected until it seemed to stop working, and the command window said: "erasing userdata". It would I left it like this over night and the phone was NOT booting.
I now am attempting to "Force Flash" with Wug's kit. But it's hanging on "writing system".
Can anyone advise me on what I should do next? Is my device completely bricked? What are my options? :crying:

I am going to try this: http://forum.xda-developers.com/showthread.php?t=2513937 I am going to assume that WugFresh's toolkit will NEVER finish "writing system".
I still seek council.

I would try this http://forum.xda-developers.com/showthread.php?p=47156064
I don't like tool kits and one click methods
When it's writing system how long do you give it? It can take like 5 minutes

BrightLancer said:
I downloaded WugFresh's toolkit and attempted to flash to stock.
Click to expand...
Click to collapse
That's why you should NEVER ever use a toolkit, I've seen too many instances just like this.
Use this guide to flash factory images, it's stickied in the general section :http://forum.xda-developers.com/showthread.php?t=2513701
Edit: As long as your phone can boot to the Google logo/fastboot, its all recoverable, so don't stress. And in many cases it can be recovered even if you can't get to the Google logo
Sent from my Nexus 5 using Tapatalk

jd1639 said:
I would try this http://forum.xda-developers.com/showthread.php?p=47156064
I don't like tool kits and one click methods
When it's writing system how long do you give it? It can take like 5 minutes
Click to expand...
Click to collapse
I gave it more than 2 hours. :/
I will try your link. I have had no success with method in the link I posted.

I just tried the method you suggested (above poster) and once again it seems to be unable to get past 'erasing "userdata""...

I just tried erasing "userdata" with the "fastboot -w" and it appeared to be working... until fastboot stopped working and launched a windows dialog box as previously described. I read in a different thread, regarding a nexus 7 with a similar issue, that using a different computer with fresh drivers, solved the issue... Anyone have any ideas what is preventing userdata from being erased? Or maybe that is not my issue... Rawr!
Let's solve this!!! Come on guys! Guys?
Humor aside, I appreciate the suggestions so far.
Any one else have any ideas?
Edit: Thank you for the reassurance!

Can you boot into your coustom recovery/ normal recovery (Volume down and power, keep holding them till you see a menu) if you can do that you're fine
Sent from my Nexus 5 using xda app-developers app

I fixed it... I used a different computer, an idea I got from this thread: http://forum.xda-developers.com/showthread.php?t=2424390
I appreciate all the help and I hope that someone wiser than I can isolate exactly what the problem is... Dome kind of driver issue if I know anything...
I really appreciate the quick and sincere replies to my questions and I look forward to being a part of the community.
-Kevin

[Android Lollipop.Nexus 5] New discovered problem.Urgent!!! Need help!!

I have bought a nexus 5 two months ago. Everything was fine unlocked boot loader and rooted with custom recovery twrp and have updated to Android 5.0 by flashing with adb, then I rooted installed twrp, chainfire supersu and twrp. Until today was opening my nexus 5 and it didn't turn on, I followed these steps:
1- charged the phone 2 hours, nothing happens.
2- Charged whilst pressing power and every single key combinations.
3- Tried accessing the second bootloader, nothing happens.
4- Tried all suggested steps on google's website for this particular problem, nothing happens.
5- Connecting it to the computer, "qhsusb_bulk" appears in device manager, adb and fastboot won't work.
6- Connecting to the pc and trying every key combination, nothing happens.
7- tearing down the nexus 5 and removing the battery connectors then reconnecting them, nothing happens.
8- Download Qualcom's drivers and installing Them to the nexus 5, then using QPSt to flash boot image or kernel or phone image but won't work, it needs some sort of .bin files.
I hope that someone has some useful info, don't come saying I need to send it back to Google or RMA because that is not possible, or saying that I need a replacement board.
Thanks in advance if someone can figure this out.

Hi,
If you don't have fastboot access that don't sound good...
I had the same issue with Nexus 7, the only solution was to use the warranty.

The problem is that I don't have a warranty. And if I am going to send to LG electronics it will cost me 180$ at least.

Have you tried wug's nexus root toolkit? I used to have similar problems when i couldn't even assess fastboot, but the toolkit worked.

Yes I tried it but it didn't work. What steps did you follow in wug's toolkit to solve your problem?

@bitdomo, this is the brick you want to try to fix?

rootSU said:
@bitdomo, this is the brick you want to try to fix?
Click to expand...
Click to collapse
Yep. There was another one about a week ago. I pointed that guy in @bitdomo direction as well. Maybe he's on vacation or just busy.
OP: Your bricked. Try and PM the OP of this thread:
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stucked-qualcomm-hs-usb-t2935283
He's your only chance other than LG at this point.

theesotericone said:
Yep. There was another one about a week ago. I pointed that guy in @bitdomo direction as well. Maybe he's on vacation or just busy.
OP: Your bricked. Try and PM the OP of this thread:
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stucked-qualcomm-hs-usb-t2935283
He's your only chance other than LG at this point.
Click to expand...
Click to collapse
Ah yeah I saw that thread and noted he hadn't responded.

Possible Solution
I came to this point before. My solution was to hold all buttons for 15seconds den release down volume button. actually i cant remember the key combination.

[Q] Android won't boot...

Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!

kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?

ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/

If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:

Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.

kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?

The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.

howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor

Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.

kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.

theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!

You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.

[Q] Nexus 5 stuck on google logo boot loop

Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin

Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?

If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.

Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:

mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.

spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock

I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.

Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.

[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS

Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.

Google update bricked phone

Afternoon all.
This morning I had one of the usual messages on my pixel 2 about having to restart the phone to install the update. I did so but now I can't boot the phone. I'm in the bootloader, with the following options and consequences
start > causes phone to restart instantly
restart bootloader > restart instantly
download mode > restart instantly with "ERROR: Operation Denied"
recovery mode> restart instantly with "ERROR: LoadImageAndAuth Failed: Device Error"
Barcode > works
power off > works
I've not tinckered with the phone in any way and have only installed official updates when prompted. I'm trying to get up to date with everything again, and have downloaded adb. "adb devices" doesn't show anything, however "fastboot devices" will display my device. I've tried the unlock "fastboot flashing unlock" command but get "FAILED (remote: 'Flashing Unlock is not allowed')"
Is my phone bricked? It's a few weeks out of warranty.... any help is greatly appreciated.

Hello mate, deffo not a good look with a locked bootloader. Just wondering, as you said it boots to recovery does it throw you to bootloader screen with the yellow warning at the bottom or the proper recovery screen? If you get the proper recovery screen have you tried the press power/vol up button together combo to get to the full recovery menu?

junglism93 said:
Hello mate, deffo not a good look with a locked bootloader. Just wondering, as you said it boots to recovery does it throw you to bootloader screen with the yellow warning at the bottom or the proper recovery screen? If you get the proper recovery screen have you tried the press power/vol up button together combo to get to the full recovery menu?
Click to expand...
Click to collapse
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.

thermomonkey said:
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.[/QUOTE
Fair enough, as recovery was working I thought you may be able to use the button combo to get to the full recovery and try an ota.img via sideload but as you say ADB is dead thats probably not gonna work anyway (forgot it's ADB sideload, been a while since I've used it)
Anyway, I'd be inclined to try my luck with the warranty if you ain't already as it's a only a few weeks out of date, always worth a call and chance your arm with them just in case.
Good luck
Click to expand...
Click to collapse

junglism93 said:
thermomonkey said:
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.[/QUOTE
Fair enough, as recovery was working I thought you may be able to use the button combo to get to the full recovery and try an ota.img via sideload but as you say ADB is dead thats probably not gonna work anyway (forgot it's ADB sideload, been a while since I've used it)
Anyway, I'd be inclined to try my luck with the warranty if you ain't already as it's a only a few weeks out of date, always worth a call and chance your arm with them just in case.
Good luck
Click to expand...
Click to collapse
Yeah I'll re-attack. They were sure it was a hardware issue and wanted to charge me to repair it. I'm quite sure it's their update that's done it though!
I can't believe they've designed the phone this way though? It doesn't seem very well thought out.
Click to expand...
Click to collapse

thermomonkey said:
junglism93 said:
Yeah I'll re-attack. They were sure it was a hardware issue and wanted to charge me to repair it. I'm quite sure it's their update that's done it though!
I can't believe they've designed the phone this way though? It doesn't seem very well thought out.
Click to expand...
Click to collapse
Make you right, don't see how it can be a hardware issue tbh. In case it's of any bearing I remember reading something online about someone having this happen, luckily they were unlocked and flashing a fresh bootloader image to both slots cleared the error and got them back in the game. Might be worth searching that error message online, might give you some ammo so to speak.
Edit: found the article here
https://support.google.com/pixelphone/forum/AAAAb4-OgUsHtb-5BNtncg?hl=sl
Click to expand...
Click to collapse

junglism93 said:
thermomonkey said:
Make you right, don't see how it can be a hardware issue tbh. In case it's of any bearing I remember reading something online about someone having this happen, luckily they were unlocked and flashing a fresh bootloader image to both slots cleared the error and got them back in the game. Might be worth searching that error message online, might give you some ammo so to speak.
Edit: found the article here
https://support.google.com/pixelphone/forum/AAAAb4-OgUsHtb-5BNtncg?hl=sl
Click to expand...
Click to collapse
Thanks again. Has this happened to anyone else before? i.e. just restarting when told to by the normal google updates and the phone is suddenly bricked?? Seems silly and it's totally put me off buying another pixel device!
Click to expand...
Click to collapse

If you search loadimageandauth error in XDA search you'll find a few threads on it, was just doing that myself. Seems to point at a bootloader issue from what I've skimmed over so far which would tie in with that link I posted.
I'm not put off the pixels by these things, in the grand scale of things it's a very low average of devices it happens on so I guess you've just been unlucky. This is my 2nd pixel device ( had the pixel prior to this pixel 2) and most likely won't be my last pixel device.
Good luck with having another crack at the warranty