I have a nexus 5 that was rooted on stock rom. I have not made any changes recently to anything. I went to wake the phone and got nothing. I used vol down and power to get into bootloader. Selected start and then the phone sat on the google logo for 5 mins. I again tried vol down and power and it went off and now will not do anything with any button combo. I charged it overnight in case the battery was just dead. Nothing this morning. I then tried to plug it into the computer and it looked for drivers for QSUSB_BULK. Never seen this before. It also shows up in device manager and an unknown device with that same title. I assume that this is a "hard brick" but surprised it just came out of the blue... Is there any chance of saving the phone?
crazycd1 said:
I have a nexus 5 that was rooted on stock rom. I have not made any changes recently to anything. I went to wake the phone and got nothing. I used vol down and power to get into bootloader. Selected start and then the phone sat on the google logo for 5 mins. I again tried vol down and power and it went off and now will not do anything with any button combo. I charged it overnight in case the battery was just dead. Nothing this morning. I then tried to plug it into the computer and it looked for drivers for QSUSB_BULK. Never seen this before. It also shows up in device manager and an unknown device with that same title. I assume that this is a "hard brick" but surprised it just came out of the blue... Is there any chance of saving the phone?
Click to expand...
Click to collapse
Ah, that sucks! I'm a little confused though, because you said that the button combos do nothing now, but when you now plug it into the PC, it attempts to load different / incorrect drivers? Is the screen just black and it's trying to load the drivers still or...? Have you tried to manually load the drivers when it's showing the unknown device? Tried different USB cables and / or ports? I realize the phone is not acting correctly, but it's best to eliminate the easy things first.
I don't think its the screen, I saw it shut off then never do anything again. I have tried different cables and ports. The phone never booted back into android I know that much. Trying to load drivers or use nexus tool kit to look for adb or fastboot devices does nothing either.
I also do not get a light or anything on the screen when I plug in the charger.
Yea, I wasn't thinking it was the screen itself. I was just wondering if now the phone is "on" and attempting to load drivers, albeit incorrectly or not at all, and the screen was still dark/off? What computer OS are you using? I'm assuming Windows due to the unknown device error, but which iteration: XP/Vista/7/8/8.1? What is the error when you manually try to load the drivers - not with a tool kit? Have you tried another cord / USB port / PC? Like I mentioned earlier, it's obviously a phone issue, but sometimes just trying these different things can at least get it to load the drivers correctly where you could at least fastboot the system back to the phone.
Ok
You are on the qualcomm cpu strict mode.
Keep it like that for ten -15 minutes the battery will charge.
After that keep it plugued in and press the power button until you hear the sound that the device is disconnected.
After that vol down + power right after
Should work
Sent from my Nexus 5 using xda app-developers app
jsmasterx said:
You are on the qualcomm cpu strict mode.
Keep it like that for ten -15 minutes the battery will charge.
After that keep it plugued in and press the power button until you hear the sound that the device is disconnected.
After that vol down + power right after
Should work
Click to expand...
Click to collapse
Now this answer seems logical and only hope to me ....and
i also think that these nexus phones can't hard brick that much easily ...
Sent from my Nexus 5 using Tapatalk
crazycd1 said:
I don't think its the screen, I saw it shut off then never do anything again. I have tried different cables and ports. The phone never booted back into android I know that much. Trying to load drivers or use nexus tool kit to look for adb or fastboot devices does nothing either.
I also do not get a light or anything on the screen when I plug in the charger.
Click to expand...
Click to collapse
And there's your problem right there. You don't know what you're doing.
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
BirchBarlow said:
And there's your problem right there. You don't know what you're doing.
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
Click to expand...
Click to collapse
I was not doing anything with the kit other they try other option to get the phone back on. I have not even installed an app on the phone in amonth it was running fine and just shut off an died. I was not playing with things I don't know. You post was an absolute waste...
crazycd1 said:
I was not doing anything with the kit other they try other option to get the phone back on. I have not even installed an app on the phone in amonth it was running fine and just shut off an died. I was not playing with things I don't know. You post was an absolute waste...
Click to expand...
Click to collapse
Alright maybe I misunderstood what you did. Have you tried reinstalling the USB driver for fastboot?
BirchBarlow said:
Alright maybe I misunderstood what you did. Have you tried reinstalling the USB driver for fastboot?
Click to expand...
Click to collapse
Of course you misunderstood, you only read one FOUR words in the tread and made your judgement.
I am using Windows 7. I tried to update the google driver in the device manager in windows but it will not accept it for that device. It only shows up as QSUSB_BULK. I have tried different cables and different ports. I have not tried another PC yet. I am going to set one up and try it just to eliminate PC issues.
crazycd1 said:
I am using Windows 7. I tried to update the google driver in the device manager in windows but it will not accept it for that device. It only shows up as QSUSB_BULK. I have tried different cables and different ports. I have not tried another PC yet. I am going to set one up and try it just to eliminate PC issues.
Click to expand...
Click to collapse
Pretty sure your device took a dump on you. Rma is your only option.
jd1639 said:
Pretty sure your device took a dump on you. Rma is your only option.
Click to expand...
Click to collapse
That is pretty much what I am thinking!
crazycd1 said:
That is pretty much what I am thinking!
Click to expand...
Click to collapse
Hate to see it but it does happen once in awhile. Emmc probably failed
Try holding the power button only for 15 seconds this is like the fail safe of pulling the battery out since we can't do that
Sent from my Nexus 5 using XDA Premium 4 mobile app
DREWHAMM974 said:
Try holding the power button only for 15 seconds this is like the fail safe of pulling the battery out since we can't do that
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have tried holding for a minute many times. All button combos..
jsmasterx said:
Ok
You are on the qualcomm cpu strict mode.
Keep it like that for ten -15 minutes the battery will charge.
After that keep it plugued in and press the power button until you hear the sound that the device is disconnected.
After that vol down + power right after
Should work
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Also while plugged in it always shows in the device manager and I never get the disconnect while holding in the power button.
Related
Hi,
yesterday I pulled my One S out of my pocket, opened up the browser, made a search on google and all of a sudden, while the page was loading the screen turned off, completely black. The capacitive buttons stayed awake for 4-5 seconds, then they turned off too.
Completely dead, the phone won't turn on anymore, not even in recovery mode. If I connect the wall charger the charging led doesn't light up, although I can feel the phone is heating (as usually happens when charging).
I've tried connecting it to the pc via usb and windows after a while, detects a peripheral named "qhsusb_dload". I've read on google that this isn't any good... Anyway, even connected to the pc (for hours) the charging led doesn't light up.
No signs of life from my One S... :crying:
The phone is completely stock, unrooted.
Do someone have any hints?
Thanks.
I believe you're in download mode.
Hold the power button until your button leds start flashing and then keep holding it until they stop again. Now let go. If they don't start flashing within (say) 20 seconds, you can also let go. Hold the vol-down button and press&release the power button. Hopefully this boots you into bootloader mode. If not I don't nkow what else to suggest other than look at the unbricking thread in the development forum.
There's no way I can enter bootloader. The phone shows no signs of life (no capacitive buttons, no charging led, nothing at all)...
One thing that maybe is important: for about a month, I've been experiencing a strange battery drain. The drain used to occur even if the phone was in deep sleep (I'm sure about this because I've checked with cpuspy and anyway I hadn't installed any new apps for quite a while), at a rate of 7-8% each hour. I could leave the phone on the desk with screen off and in standby (no 3g data, no wifi, not even cellular network) and the drain was still there.
By the way, when my phone died I had plenty of battery left, about 70%.
nor-ric said:
The phone is completely stock, unrooted.
Do someone have any hints?
Thanks.
Click to expand...
Click to collapse
If it's unrooted then your warranty is still 100% intact and HTC will replace your phone no problem. What you describe just happens sometimes, more so with this phone then others I've seen.
The qhsusb_dload means it's not worth tinkering with yourself if you can just submit it for warranty.
dc211 said:
If it's unrooted then your warranty is still 100% intact and HTC will replace your phone no problem. What you describe just happens sometimes, more so with this phone then others I've seen.
The qhsusb_dload means it's not worth tinkering with yourself if you can just submit it for warranty.
Click to expand...
Click to collapse
I see, thanks. Is this qhsusb-dload issue hardware-related? If so, is it possible that they swap my S4 chip with an S3?
nor-ric said:
I see, thanks. Is this qhsusb-dload issue hardware-related? If so, is it possible that they swap my S4 chip with an S3?
Click to expand...
Click to collapse
Think of qhsusb-dload kinda like your normal PC without windows. Your phone could not find an operating system to boot into and defaulted to qhsusb-dload mode waiting for a command. Our problem is that we don't really know the commands for qhsusb-dload nor do we have the files needed to use it only the manufactures do.
They can't swap a s4 chip for a S3 version that isn't the same product.
Most likely it the micro USB charging port that's gone toast.. happened to mine exact same symptoms. I was actually unlocked, HTC dev unlocked too, running a custom ROM as well as custom recovery and splash screen. I still sent it in repair with hope of they will never be able to turn the damn thing on to discover my deeds and will replace my phone but they didn't mind, they reflashed stock rom after repair and sent it back but I was still s-off
Send it into repair mate. Best option instead of tinkering with it lol
Sent from my HTC Sensation using xda premium
Nope, there is a solution.
http://unlimited.io/qhsusbdload.htm
Sent from my HTC One S+
Ok, thanks everybody.
I'm going to try usaff22's method and if that doesn't work I'll send the phone in.
I'll let you know! :fingers-crossed:
It didn't work. The terminal waits for the device, however it doesn't respond...
I'll have to send the phone in.
Crazy idea but that sounds like the mode you go into for the downgrade so maybe the last part of it might help to get you up and running again.
Darknites said:
Crazy idea but that sounds like the mode you go into for the downgrade so maybe the last part of it might help to get you up and running again.
Click to expand...
Click to collapse
Where can I find the guide you're referring to?
Thanks.
nor-ric said:
Where can I find the guide you're referring to?
Thanks.
Click to expand...
Click to collapse
Here you go, Downgrade/Unbrick.
Darknites said:
Here you go, Downgrade/Unbrick.
Click to expand...
Click to collapse
I've read that thread: do you mean I should try the 9th point?
you can open a new terminal window and run the following command IF AND ONLY IF the phone doesn't reset out of QDL mode
Code:
$ sudo ./emmc_recover -r
Click to expand...
Click to collapse
nor-ric said:
I've read that thread: do you mean I should try the 9th point?
Click to expand...
Click to collapse
No that for flashing Hboot think you want step 12 but will need to edit the file the download has but you will need to do step 3 so you can do step 12. I have no idea if it will work but its an idea and also might be best to ask about it there too before doing anything.
thanks a lot touch of jobo i was going to get crazy :laugh:
touch of jobo said:
I believe you're in download mode.
Hold the power button until your button leds start flashing and then keep holding it until they stop again. Now let go. If they don't start flashing within (say) 20 seconds, you can also let go. Hold the vol-down button and press&release the power button. Hopefully this boots you into bootloader mode. If not I don't nkow what else to suggest other than look at the unbricking thread in the development forum.
Click to expand...
Click to collapse
that worked for me. thanks a lot
btw. maybe someone can answer this: how come that the phone goes in download mode?! I had the phone unused the last hours before I recognized it wasn't on anymore? Does this just happen? I am on CM11 Nightlies atm.
Ok so my mytouch was charging on my computer then i went to check on a text message, the screen was black but i could see the backlight. So I assumed it was a normal glitch or something so i disconnected it and pulled out the battery, but it wont even turn on or charge now.
I did everyting
I took out the battery
I tried a different battery
I took out both the sim and the sd card
I tried to load on bootloader
I tried a wall charger
Nothing has worked!
Anybody got any ideas.
lifebound said:
Ok so my mytouch was charging on my computer then i went to check on a text message, the screen was black but i could see the backlight. So I assumed it was a normal glitch or something so i disconnected it and pulled out the battery, but it wont even turn on or charge now.
I did everyting
I took out the battery
I tried a different battery
I took out both the sim and the sd card
I tried to load on bootloader
I tried a wall charger
Nothing has worked!
Anybody got any ideas.
Click to expand...
Click to collapse
When you say "Wont even turn on or charge"...
Do you get a buzz when trying to turn on?
How long have you left it on charge?
Does your computer recognize it when plugged in?
Have you rebooted your PC since the issue started?
When you pulled the battery, did you also unplug the USB cable?
What happens if you take out the battery and while holding down volume + & - you plug into PC via USB?
Sent from my Nexus 7 using xda premium
GoPadge said:
When you say "Wont even turn on or charge"...
Do you get a buzz when trying to turn on?
How long have you left it on charge?
Does your computer recognize it when plugged in?
Have you rebooted your PC since the issue started?
When you pulled the battery, did you also unplug the USB cable?
Click to expand...
Click to collapse
There is no buzz because it wont even turn on.
It was on charge for about 10 minutes.
Yeah it does make an noise when i plug it in.
Yes.
And Yes
demkantor said:
What happens if you take out the battery and while holding down volume + & - you plug into PC via USB?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I hear the noise of something being recognized on my computer but nothing on the phone. Happens with or without the battery regardless.
Have you tried any adb commands?
adb reboot bootloader
adb reboot recovery
Sent from my SGH-T889 using Tapatalk 2
Sounds suspiciously like hardware, maybe main flex went bad and... well actually probably not as I think it would still vibrate. If you have debugging turned on and the proper drivers in pc the you can try a screen cast and see if you have anything, that or maybe some adb commands.
Also try another pc, one that it has never been connected to, see if drivers try to install
Sent from my MyTouch 4G Slide using xda premium
lifebound said:
There is no buzz because it wont even turn on.
It was on charge for about 10 minutes.
Yeah it does make an noise when i plug it in.
Yes.
And Yes
Click to expand...
Click to collapse
Ok. So it's not totally dead. (It's not necessarily recoverable, but it's not a full brick.)
A failed flex cable isn't out of the realm of possibility. You mentioned you were checking a text.
Did you open the keyboard, or hit the power button or trackpad?
GoPadge said:
Ok. So it's not totally dead. (It's not necessarily recoverable, but it's not a full brick.)
A failed flex cable isn't out of the realm of possibility. You mentioned you were checking a text.
Did you open the keyboard, or hit the power button or trackpad?
Click to expand...
Click to collapse
I Hit the trackpad i think. Once i pressed it i got an empty screen. I already tried using ADB commands but adb wont even recognize my phone once connected. I have tried refreshing the daemon servers multiple times still no detect. Its like out of no where i decided to die or something lol
Hi everyone, so yesterday I got home, and like everyday I dropped it on the wireless charger. After about 2 hours I took it and it has turned off itself and doesn't react to my button presses or anything. I tried holding Power, Power+Vol Up, Power+Down, Power+Vol up+Vol down, charged it overnight but it still doesn't work. Is there anything else left to do? (Bootloader is unlocked, twrp recovery + franco kernel and stock fw, it was working for like 2 weeks with no crashes).
If you've already tried holding the power button for 20 seconds it sounds like rma is the answer.
Does your computer recognizing your phone?
It does not, the phone isn't turned on, how could computer recognize it? (btw. The phone takes the power from the wall it seems, cause the power cord gives a noise when only it's pluged in without cable to the phone, then I can take it out, it still makes noise, and if i plug the phone into it, it stops making the noise)
Illiuminatum said:
It does not, the phone isn't turned on, how could computer recognize it? (btw. The phone takes the power from the wall it seems, cause the power cord gives a noise when only it's pluged in without cable to the phone, then I can take it out, it still makes noise, and if i plug the phone into it, it stops making the noise)
Click to expand...
Click to collapse
It can recognize a phone even if it's not turned on,as adb,and then you can flash recovery,kernel and etc,using fastboot commands.
So go to device manager and see if recognized as adb,if yes,you're good to go,and try to flash stock rom and recovery.
Also you can try to reboot into bootloader using fastboot reboot command.
Simonna said:
It can recognize a phone even if it's not turned on,as adb,and then you can flash recovery,kernel and etc,using fastboot commands.
So go to device manager and see if recognized as adb,if yes,you're good to go,and try to flash stock rom and recovery.
Also you can try to reboot into bootloader using fastboot reboot command.
Click to expand...
Click to collapse
It doesn't recognize it ( I thought it only recognizes it if it's in vol down+power or on :?
Illiuminatum said:
It doesn't recognize it ( I thought it only recognizes it if it's in vol down+power or on :?
Click to expand...
Click to collapse
Ah yes,my bad,sorry. Also,when you took,didn't you notice that it's hot or something like that? Because I've read on the internet that wireless charging can make devices to overheat.
Simonna said:
Ah yes,my bad,sorry. Also,when you took,didn't you notice that it's hot or something like that? Because I've read on the internet that wireless charging can make devices to overheat.
Click to expand...
Click to collapse
Yes, 2 times it was hot, but not yesterday. When I took it, it wasn't cold or hot, the same as normal phone would be.
Oh, and one more thing. When I hold power button it makes noise like this: h\ttp\s://w\ww.dropbox.c\o\m\/s/d3e0rqtlzm7x2ig/N5noise.mp3 (Remove all the \ from the link)
Barely hearable so I just accidentally noticed it.
Anyways, I'll go for the RMA. One more question, I really doubt it's possible but I will ask. is there a way to transfer all files from the phone if it's not responding to anything?
Illiuminatum said:
Anyways, I'll go for the RMA. One more question, I really doubt it's possible but I will ask. is there a way to transfer all files from the phone if it's not responding to anything?
Click to expand...
Click to collapse
Nope, that's part of the package.
if at least ADB was working you could but not possible unless LG revive the phone.
GUGUITOMTG4 said:
Nope, that's part of the package.
if at least ADB was working you could but not possible unless LG revive the phone.
Click to expand...
Click to collapse
Can you ask Google when RMA'ing to try to restore the stuff from the phone?
Illiuminatum said:
Can you ask Google when RMA'ing to try to restore the stuff from the phone?
Click to expand...
Click to collapse
You can ask anything, but don't hold your breath
Do I need to worry if my phone has unlocked bootloader and is rooted? (I mean will RMA go ok?)
Illiuminatum said:
Do I need to worry if my phone has unlocked bootloader and is rooted? (I mean will RMA go ok?)
Click to expand...
Click to collapse
If your sending it to google, then you don't have to worry. However, your device is fully dead, right? They will most probably swap the mobo or just send you a refurbished piece.
vin4yak said:
If your sending it to google, then you don't have to worry. However, your device is fully dead, right? They will most probably swap the mobo or just send you a refurbished piece.
Click to expand...
Click to collapse
It's making some kind of a noise when trying to turn it on/charge it, and doesn't react any other way, so yea, dead.
Illiuminatum said:
It's making some kind of a noise when trying to turn it on/charge it, and doesn't react any other way, so yea, dead.
Click to expand...
Click to collapse
No worries! Good luck with the RMA!
Do keep us posted!
Today my phone was working fine and it was working fine all the time. I have 4.4.4 Android unlocked and not rooted (it was rooted, but when i updated to 4.4.4 the root was gone and i didnt put it on). It was in my pocket and when i got home i wanted to start the sceen and it dosent react to anything. I tryed charging it (thinking the battery died, not nothing on the screen), try pushing all the buttons (3 buttons in the same time) nothing again. it is so strange!? what i can do? i have connected to my computer, but the com is not detecting it. and the screen dont react at all. this is so strange!?!?!?
bulgaria_mitko said:
Today my phone was working fine and it was working fine all the time. I have 4.4.4 Android unlocked and not rooted (it was rooted, but when i updated to 4.4.4 the root was gone and i didnt put it on). It was in my pocket and when i got home i wanted to start the sceen and it dosent react to anything. I tryed charging it (thinking the battery died, not nothing on the screen), try pushing all the buttons (3 buttons in the same time) nothing again. it is so strange!? what i can do? i have connected to my computer, but the com is not detecting it. and the screen dont react at all. this is so strange!?!?!?
Click to expand...
Click to collapse
So You've done nothing?
Okay, well first i recommend doing the "obvious".
1) Hold Down the Power Button
else
2)Load device manager on your PC and connect your Phone, anything coming up?
else
3)leave it in the charger overnight.
Also if the battery is dead, it won't show anything on screen, it'll be black only.
then when it has enough power it'll show a red light at the bottom.
Push and good the power button for 20 seconds. See if after it'll boot
Sent from my Nexus 5 using XDA Free mobile app
Maybe try giving it a while on the chargee then toggle with the power button. I had a Lenovo tab once that did the same thing, it just suddenly died and I tried doing everything I could to revive it. So I just gave up and left it on the charger for a long time then gave it one last hold of the power button and presto! It was alive.
Sent from XT912
[AOSP/4.3] [ROM] Eclipse v5.1 build 6 spyder
thanks
thanks for ur answer.
1. i tryed that and nothing happen. i have Practical Meter and when i hold those buttons it gives me signal that it is not charging and when i stop holding the buttons it gives signal that is full charging (like charging at its 5 of 5 leval of charging)
2. i tryed this, but nothing is showing on the device manager
3. i will try this tonight.
thanks anyway! :good: hope my phone is not dead, because i have unlocked and the warrety is void.
i4GS said:
So You've done nothing?
Okay, well first i recommend doing the "obvious".
1) Hold Down the Power Button
else
2)Load device manager on your PC and connect your Phone, anything coming up?
else
3)leave it in the charger overnight.
Also if the battery is dead, it won't show anything on screen, it'll be black only.
then when it has enough power it'll show a red light at the bottom.
Click to expand...
Click to collapse
bulgaria_mitko said:
thanks for ur answer.
1. i tryed that and nothing happen. i have Practical Meter and when i hold those buttons it gives me signal that it is not charging and when i stop holding the buttons it gives signal that is full charging (like charging at its 5 of 5 leval of charging)
2. i tryed this, but nothing is showing on the device manager
3. i will try this tonight.
thanks anyway! :good: hope my phone is not dead, because i have unlocked and the warrety is void.
Click to expand...
Click to collapse
If you can't turn on the phone, even they wouldn't be able to. I guess you still have a shot at warranty. :fingers-crossed:
i am having the same problem, but when i connect my phone to the computer it's trying to instal the qhsusb_bulk driver, from my reasarch it's a hard brik... same i cand use my warranty because the phone glass it's cracked so the only solution is a jtag but i dont't know if it's posibile for the NEXUS 5. I went to a service and the say it's because of dead software. All i want to know is if it's posibile to resurect it with JTAG.
Same thing happened to my n5 32gb last Thursday. I sent it already to Google. It is unlocked but like new condition visually.
I'm really disappointed because my old 4year old HTC working.
Sent from my HTC Desire using xda premium
informatican5 said:
i am having the same problem, but when i connect my phone to the computer it's trying to instal the qhsusb_bulk driver, from my reasarch it's a hard brik... same i cand use my warranty because the phone glass it's cracked so the only solution is a jtag but i dont't know if it's posibile for the NEXUS 5. I went to a service and the say it's because of dead software. All i want to know is if it's posibile to resurect it with JTAG.
Click to expand...
Click to collapse
You need the proper equipment for it and I haven't seen anybody here resurrecting their devices using jtag.
Lior84 said:
Same thing happened to my n5 32gb last Thursday. I sent it already to Google. It is unlocked but like new condition visually.
I'm really disappointed because my old 4year old HTC working.
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Hardware failures can occur on any device. My HTC One X died within 2 months of usage. That's why the manufacturer provides warranty to take care of it under such circumstances.
vin4yak said:
You need the proper equipment for it and I haven't seen anybody here resurrecting their devices using jtag.
Click to expand...
Click to collapse
It's any chance to resurect it? Do you know a method?
informatican5 said:
It's any chance to resurect it? Do you know a method?
Click to expand...
Click to collapse
You can try to access the secondary bootloader and see if you can fix it from there. Follow the last thread which I've linked in my signature and from the its OP follow the bsod thread.
If that doesn't help, the device is a goner.
- Sent from an IceCold Hammerhead!
if you can boot into download mode (Hold down volume_up key then connect USB cable). give this a try:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-images-lg-t2713833
vin4yak said:
You need the proper equipment for it and I haven't seen anybody here resurrecting their devices using jtag.
Hardware failures can occur on any device. My HTC One X died within 2 months of usage. That's why the manufacturer provides warranty to take care of it under such circumstances.
Click to expand...
Click to collapse
vin4yak said:
You can try to access the secondary bootloader and see if you can fix it from there. Follow the last thread which I've linked in my signature and from the its OP follow the bsod thread.
If that doesn't help, the device is a goner.
- Sent from an IceCold Hammerhead!
Click to expand...
Click to collapse
i'm stuk at poit 2a, adb doesnt recognize it and i don't know exactly how to navigate to the recovery option and load recovery. except vol -+ and power wich doesn't work.
informatican5 said:
i'm stuk at poit 2a, adb doesnt recognize it and i don't know exactly how to navigate to the recovery option and load recovery. except vol -+ and power wich doesn't work.
Click to expand...
Click to collapse
You need to use the volume buttons to select recovery option in bootloader and then press the power button to get there.. If the buttons are stuck or do not work, I'm not sure what you could do now other than rma.
Sorry but your solution is RMA only.
Sent from my HTC Desire using xda premium
I manage to fix my phone. i was charging it for 1 hour and with the cable on (charging) i start to press all the buttons (for recovery mode) and nothing happen and then disconnect it from this charger and i connect it to other charger and magically when i plug the cable the phone display show that it is charging (and before that it was not showing this) and then i just turn it on. so just try a coupple of times with different situation.
Tried every combination with different chargers and sadly without success. It already on it's way to Google
Sent from my HTC Desire using xda premium
Hello everyone,
This morning while I was having coffee, my phone started playing jokes on me. At first it got really slow while doing the easiest things, like checking a mail, send a text and make a phone call. 10-15 After that I get a notification, Phone was locked, I tried to unlock it. I did spam the button like 5-10 times, Screen won't come up, but notification LED was working. At that point I thought that the power button was pretty much done for. Nope not the case. I held it down for 10 seconds, phone actually powered down. No chance in hell I could turn it back on. At that point I just went home. Got home plugged the phone into my PC. As soon as I did that, Windows started to check for a driver, had to wait almost 5 minutes to find QHSUSB_BULK.
Now, doing a bit of a search I found out that this could be the result of different problems, One that has to do with the memory just dying cause yeah, Nexus 5 and the eternal memory problem +Lollipop screw around with Data partitions, another that has to do with Roms, another that had to do with custom recovery.
What the hell is in my case? I run a custom Rom and a custom recovery, Atm I have Cyanogenmod 12.1 and lateste TWRP recovery.
I have a handful of tools at my disposal, a Cable, a good keyboard and a iron will.
In this case, Can I do something to fix my phone from home? Can't really send into warranty as I have custom software that's running on it and I'll just get a generic response that basically tells me that my warranty was voided due to custom software running on the terminal. We all love generic response like that, Don't we?
TLR: Phone died this morning, I couldn't unlock the screen and I thought it was the power button be cause, the notification led was still working. At that point I just powered it down by holding the power button down for 10 sec.
I wasn't able since to power it back on. If I connect it to my PC I get QHSUSB_BULK.
Hopefully there's some one who can point me in a direction ASAP. I have no backup phone atm and I really need this one to actually be ALIVE again.
Can't send it to Warranty because I run custom software on it. GSM Services/Fix Shops are out of the question too.
Pls halp ASAP
Will pay in Galactic Credits.
Thanks!
Your best bet is to try this, http://forum.xda-developers.com/showthread.php?p=51823398. Good luck, your device is not in a good state.
Sent from my Nexus 9 using XDA Free mobile app
metalheadbk said:
Hello everyone,
This morning while I was having coffee, my phone started playing jokes on me. At first it got really slow while doing the easiest things, like checking a mail, send a text and make a phone call. 10-15 After that I get a notification, Phone was locked, I tried to unlock it. I did spam the button like 5-10 times, Screen won't come up, but notification LED was working. At that point I thought that the power button was pretty much done for. Nope not the case. I held it down for 10 seconds, phone actually powered down. No chance in hell I could turn it back on. At that point I just went home. Got home plugged the phone into my PC. As soon as I did that, Windows started to check for a driver, had to wait almost 5 minutes to find QHSUSB_BULK.
Now, doing a bit of a search I found out that this could be the result of different problems, One that has to do with the memory just dying cause yeah, Nexus 5 and the eternal memory problem +Lollipop screw around with Data partitions, another that has to do with Roms, another that had to do with custom recovery.
What the hell is in my case? I run a custom Rom and a custom recovery, Atm I have Cyanogenmod 12.1 and lateste TWRP recovery.
I have a handful of tools at my disposal, a Cable, a good keyboard and a iron will.
In this case, Can I do something to fix my phone from home? Can't really send into warranty as I have custom software that's running on it and I'll just get a generic response that basically tells me that my warranty was voided due to custom software running on the terminal. We all love generic response like that, Don't we?
TLR: Phone died this morning, I couldn't unlock the screen and I thought it was the power button be cause, the notification led was still working. At that point I just powered it down by holding the power button down for 10 sec.
I wasn't able since to power it back on. If I connect it to my PC I get QHSUSB_BULK.
Hopefully there's some one who can point me in a direction ASAP. I have no backup phone atm and I really need this one to actually be ALIVE again.
Can't send it to Warranty because I run custom software on it. GSM Services/Fix Shops are out of the question too.
Pls halp ASAP
Will pay in Galactic Credits.
Thanks!
Click to expand...
Click to collapse
Have you tried booting into secondary boot loader?
Sent from my Nexus 5 using XDA Free mobile app
But the phone won't turn on.
jd1639 said:
Your best bet is to try this, http://forum.xda-developers.com/showthread.php?p=51823398. Good luck, your device is not in a good state.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have the exact same problem but this answer doesn't help. This solution requires that you can turn your phone on in the first place. He specifically said he can't turn the phone on at all. Same with me, no matter what I've got nothing. Need help!
metalheadbk said:
Hello everyone!
Click to expand...
Click to collapse
this is what you are looking for http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
bitdomo said:
this is what you are looking for http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
Click to expand...
Click to collapse
Thanks to everyone.
I used the board diag - clicked Start and... it said "failed to open partition from EMMC". The test aborted. I think my phone is gone for good.
Oh and I had to take the battery out, plug it in, and sometimes re-attached to latch that goes over the battery several times before I could even get it to read anything in Device Manager. Before that it would say "failed USB connection".
This all started yesterday when the phone just spontaneously put itself into a boot loop while on charge. I tried to do a factory reset but it froze. After several hours I tried to cancel it. The Nexus went full brick.
Thanks again
leopoldstotch25 said:
Thanks to everyone.
I used the board diag - clicked Start and... it said "failed to open partition from EMMC". The test aborted. I think my phone is gone for good.
Oh and I had to take the battery out, plug it in, and sometimes re-attached to latch that goes over the battery several times before I could even get it to read anything in Device Manager. Before that it would say "failed USB connection".
This all started yesterday when the phone just spontaneously put itself into a boot loop while on charge. I tried to do a factory reset but it froze. After several hours I tried to cancel it. The Nexus went full brick.
Thanks again
Click to expand...
Click to collapse
I am afraid the emmc tied then. You have to buy a new motherboard.
Tapatalk-kal küldve az én Nexus 5-el
Thanks for your help.