Hey guys I need some help asap! I have had my Nexus 5 for about 2 weeks now. I had rooted it and put in cwm recovery. The other day I had switched over art from Dalvik. Later in the day I was using linux deploy from the app store. About an hour after when i was browsing the web the device returned an error stating that the devices memory was full..... I knew there was no way. I powered off the device and that was the last of it. It does not power on in the traditional sense it does not go into recovery it does not go into fastboot and it certainly not the OS. Just a black screen. However it does get recognized as a QHUSB device when connected to a PC after fussing with the drivers adb or fastboot drivers no matter the version do not work the device will appear in device manager as though it is there but running adb devices or fastboot devices returns no devices. After extensive driver version attempts and toold nexus rootkit etc i have found that the slightly responsive driver for anything is the LG AndroidNet Diagnostic driver. Although QPST hangs when trying to download via Sahara and CDMA workshop will connect but it does it fails when trying to read from phone. I know there are tools for devices in the same situation. Is there one for the nexus 5? Or can someone help me recover this bad boy? This version is the google play version and not the t-mobile or sprint variant. HEEELP!!!!!!!!!! Thanks.
Try to turn off your phone. I know it looks like it is turned off but it's not. Press power button about 10secs then release it and then press and hold it with the two volume keys. You should find yourself in the bootloader and there you could flash stock rom back.
If that not works. Connect the phone to the pc. Open up device manager. Press and hols power button and when the qhusb dissapears press and hold both volume keys while you still pressing the power key. You may end up again in qhsusb, try to wait a little bit more with the pressing both volume keys after each try.
I hope it will work, but I know a guy who bricked his device like you with cwm, his phone also appears as qhusb device on the pc and he could not recover.
Tha last thing you can do is send it back to google to recive a replacement device.
Sent from my Nexus 5 using xda app-developers app
Tried it
bitdomo said:
Try to turn off your phone. I know it looks like it is turned off but it's not. Press power button about 10secs then release it and then press and hold it with the two volume keys. You should find yourself in the bootloader and there you could flash stock rom back.
If that not works. Connect the phone to the pc. Open up device manager. Press and hols power button and when the qhusb dissapears press and hold both volume keys while you still pressing the power key. You may end up again in qhsusb, try to wait a little bit more with the pressing both volume keys after each try.
I hope it will work, but I know a guy who bricked his device like you with cwm, his phone also appears as qhusb device on the pc and he could not recover.
Tha last thing you can do is send it back to google to recive a replacement device.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thank you, I have tried that and it does not work. My fear is that I will not be able to return as I have pulled the battery and have custom software.
I was hoping there was some way to recover when the device is in the LG Android diagnostic mode.
joutcast said:
Thank you, I have tried that and it does not work. My fear is that I will not be able to return as I have pulled the battery and have custom software.
I was hoping there was some way to recover when the device is in the LG Android diagnostic mode.
Click to expand...
Click to collapse
Why did you pull the battery? You could have rma'd it.
jd1639 said:
Why did you pull the battery? You could have rma'd it.
Click to expand...
Click to collapse
Thank you your comment is of help right now....
joutcast said:
Thank you, I have tried that and it does not work. My fear is that I will not be able to return as I have pulled the battery and have custom software.
I was hoping there was some way to recover when the device is in the LG Android diagnostic mode.
Click to expand...
Click to collapse
If there is no traces or signs you removed the battery (like finger prints or damaged back cover) then google will never find out you have custom rom on your device, because they cant turn it on. It does not worth the effort to google to somehow hack the data out from the broken flash chip. What they will do is that they try to turn it on, then they see it is not possible so they flas stock rom through qhusb ans that wipes all the data of your phone and reformat everything. Or maybe unbricking the device does not wort the effort too and google just send you a replacement device.
Sent from my Nexus 5 using xda app-developers app
bitdomo said:
If there is no traces or signs you removed the battery (like finger prints or damaged back cover) then google will never find out you have custom rom on your device, because they cant turn it on. It does not worth the effort to google to somehow hack the data out from the broken flash chip. What they will do is that they try to turn it on, then they see it is not possible so they flas stock rom through qhusb ans that wipes all the data of your phone and reformat everything. Or maybe unbricking the device does not wort the effort too and google just send you a replacement device.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
OK, GREAT that first option they do....DOES ANYONE KNOW HOW TO DO THAT???? I know it can be done on other devices as shown in the link below
http://forum.legija.net/showthread....g-galaxy-S4-(i9505-and-similar)-via-USB-Cable
joutcast said:
OK, GREAT that first option they do....DOES ANYONE KNOW HOW TO DO THAT????
Click to expand...
Click to collapse
You are asking for help with it. To answer your question. It's called jtag and lots of people know how to do it. I'd look for "mobile tech videos". QHUSB is a true brick.
EDIT: Or you could just RMA it. I think that might have been what you where asking to begin with. lol
@joutcast dude it sounds bricked. I'm sure Google will give you another device if you RMA it.
I'm very serious. Im Not being smart about it. I highly doubt Google will do anything to check unless you left obvious traces of it being tampered.
Sent from my Nexus 5 using Tapatalk
You need to JTAG it. It'll cost you about $65 and you'll have a working phone again. I'd check craigslist for JTAG in your area, a lot of people are doing it now.
And stop being so sensitive.
Work the problem and not each other.
Thread Cleaned
_MetalHead_ said:
You need to JTAG it. It'll cost you about $65 and you'll have a working phone again. I'd check craigslist for JTAG in your area, a lot of people are doing it now.
And stop being so sensitive.
Click to expand...
Click to collapse
Sensitivity is what I do best LOL. I went ahead with the RMA route and have been with out a phone for over 15 days. The reason being I am unemployed and could not afford the $450 for an advanced replacement. I still have not heard a peep out of Google as to when I can even think about getting a tracking number from them..... What cracks me up is the fact that if I had done an advanced RMA the hold on my card would of fallen off a long time ago and at that point they still would not have any security on the device. Not only that they have had my phone since Tuesday of this week.
Related
Hi, I'm new here so don't know if i'm posting this in the right place but here it goes... Ok i gave my HTC Inspire to a friend to install the MIUI ROM to it. Afterwards it was running smoothly and had no problems with it. A few days later my Inspire notified me that it had an update to the ROM. At first i wasn't sure to install it because it is a custom ROM and not the default one, but did the update anyways through the phone. Again, the phone worked normal all day, but at some point the screen started glitching untill it turned completly off.
The one strange thing is that the phone seems to function normally because when charged and "turned on" i can hear the sounds and notifications(like email, text and app notifiactions). Also when i connect it to my computer, it recognizes the device.
That happened about three days ago and I have not been able to discover what really is the problem and how to fix it. If there's anyone that could help me i would REALLY appreciate it.
Thanks in advance,
Marialo
most likely was a bad update.
You should boot into recovery and reinstall miui everything should be back.
Keep in mind the devs have to set miui for each device, chances are you updated to the wrong base.
That's what i thought but can't boot into recovery because i can't see the screen... Any advice on that?
Btw, thks for the quick response
Try shutting off the phone completely and booting into your bootloader the old fashioned way by holding down the volume down key, press power, and release volume down once you see the bootloader screen.
If your screen doesn't work during that, you may have a hardware problem on your hands.
Ok thanks; will try that then.
marialo said:
Ok thanks; will try that then.
Click to expand...
Click to collapse
or while the phone's on, if you have ADB installed - open a cmd prompt and navigate to where ADB is and type "adb reboot recovery"
Yup try what they said that should work. If not ruu the ruin and really root
sent from the dark obelisk
Ok, tried with the volume and power button, but nothing happened. Thanks for the advice, but I'm kind of new with all this and don't really know how to do the other stuff that you guys told me to do... :S Should I get someone that knows a bit more or is it something that i could do with a little info. from the internet?
anudist said:
Try shutting off the phone completely and booting into your bootloader the old fashioned way by holding down the volume down key, press power, and release volume down once you see the bootloader screen.
If your screen doesn't work during that, you may have a hardware problem on your hands.
Click to expand...
Click to collapse
I don't know if you would know but... If it were hardware problems; you think I could claim that to htc? Since the phone hasn't had any accidents or anything... :/
marialo said:
I don't know if you would know but... If it were hardware problems; you think I could claim that to htc? Since the phone hasn't had any accidents or anything... :/
Click to expand...
Click to collapse
If its rooted warranty won't cover this. Get the ruu (stock exe) from the HTC support site and run it. If the phone still has a black screen after its been returned to stock then the problem is hardware related
sent from the dark obelisk
I noticed that I couldn't control the volume when in Gingerbread, I restarted the Nexus S. The Nexus S is now booting into the recovery menu by default, I can't boot into the OS.
The volume in the recovery menu works as expected (though slightly delayed), the real problem is that the power button has the same function as the volume up.
My phone is rooted and the bootloader is unlocked, this was done several months ago though.
Any help would be greatly appreciated, thanks!
Sounds like you lost your OS, you need to re-install the rom through recovery. Just Wipe your data and cache, mount usb, transfer the rom to your sd, and install. EZ PZ
smoka206 said:
Sounds like you lost your OS, you need to re-install the rom through recovery. Just Wipe your data and cache, mount usb, transfer the rom to your sd, and install. EZ PZ
Click to expand...
Click to collapse
Thanks for the reply, I was able to boot into the OS using the fastboot command "fastboot reboot". I then flashed a previous backup I made three months ago, sadly this did nothing to alleviate my problem. I am convinced this is a hardware failure of some sort.
I have now flashed an unrooted stock rom and locked the bootloader as I intend to invoke warrenty and send it over to Samsung.
Naturally, this had to happen right when Ice Cream Sandwich launches on the Nexus S.
Yes my friend this happened to my buddy as I was lucky enough to get fastboot to recognize the pc after hundreds of tries so I could lock the bootloaders back up
Let me guess does your phone turn on by itself when you plug it in to charge?
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
Yes my friend this happened to my buddy as I was lucky enough to get fastboot to recognize the pc after hundreds of tries so I could lock the bootloaders back up
Let me guess does your phone turn on by itself when you plug it in to charge?
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Click to expand...
Click to collapse
Woah, come to think of it my phone did turn on by itself! And it took me at least an hour for fastboot to recognize my phone. I assume your friend sent it in under warrenty? How long did it take until he got a replacement?
MikeUter said:
I noticed that I couldn't control the volume when in Gingerbread, I restarted the Nexus S. The Nexus S is now booting into the recovery menu by default, I can't boot into the OS.
The volume in the recovery menu works as expected (though slightly delayed), the real problem is that the power button has the same function as the volume up.
My phone is rooted and the bootloader is unlocked, this was done several months ago though.
Any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
Sounds like your volume key is broken and the volume down key is always pressed.
adam900710 said:
Sounds like your volume key is broken and the volume down key is always pressed.
Click to expand...
Click to collapse
That is what I thought at first, but the power button will not execute like it should.
He has some sort of best buy warranty and I just gave it back to him today with locked bootloaders
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
If your without warranty what I would do is install cyanogen mod and use the volume wake option or if you want to use ICS then get goto lock screen app from the market and use that to wake the device with the volume wake option
I say this because his power button went out completely and there was a major problem with his USB connection
Its like the power button is always being held in. This problem started for him before flashing any custom rom,it made it really hard to root and because mounting storage and fastboot drivers sucked but hang in there and keep this post alive as I'm going to take it apart tomorrow and see if something is loose or not making good connection
Were you hard on it? he is as we work in a sugar factory
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
If your without warranty what I would do is install cyanogen mod and use the volume wake option or if you want to use ICS then get goto lock screen app from the market and use that to wake the device with the volume wake option
I say this because his power button went out completely and there was a major problem with his USB connection
Its like the power button is always being held in. This problem started for him before flashing any custom rom,it made it really hard to root and because mounting storage and fastboot drivers sucked but hang in there and keep this post alive as I'm going to take it apart tomorrow and see if something is loose or not making good connection
Were you hard on it? he is as we work in a sugar factory
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Click to expand...
Click to collapse
I should still have warranty with Samsung as I bought my phone in May. I don't think I was too rough with my phone, that said it's in my pocket most if the time. The power button works fine, the volume up is another story. Thanks for helping.
no problem mike,please keep me posted on how your return to samsung turns out and if there are any obsticles you have to go through
mike216 said:
no problem mike,please keep me posted on how your return to samsung turns out and if there are any obsticles you have to go through
Click to expand...
Click to collapse
I called Samsung, they told me I could take it into my local Rogers store to get it repaired. When showing the Rogers employee what was wrong my phone just magically started working again, it seemed to good to be true. And as it turned out it was, as my phone cannot send or receive calls. Hopefully I won't be without a Smartphone for too long.
Thanks for all the replies everyone.
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Use heimdall n hold the volume buttons n enable flash bootlaoders
Sent from my SGH-T959V using xda app-developers app
@karose465 How old is the phone? If less than a year (doubtful), it should still be under warranty. Or you may be eligible for upgrade pricing: Fore example, "Customers with a Classic plan (two-year contract) are eligible for our lowest upgrade price on a new phone when at least 22 months have passed since their last phone upgrade. A new two-year contract is required to take advantage of best upgrade pricing. Of course, you can always upgrade a phone at any time, regardless of how many months have passed since your contract began."
For more info on Heimdall, just Google Heimdall Android.
Anyone with a sidekick contract ends earliest next march..
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.
RicAndroid said:
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.
Click to expand...
Click to collapse
I think for him and myself, the biggest problem is being unable to get the phone to stay in download mode. For some reason, the battery won't charge and the phone itself continously turns off and on when plugged in. So the charge isn't holding, therefore nothing will stay on/open.
Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium
gamingwiz said:
Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium
Click to expand...
Click to collapse
I did some forum searching and found this. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=1477838
Thanks ill check into that
Sent from my HTC Glacier using xda premium
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576
---------- Post added at 04:33 PM ---------- Previous post was at 03:41 PM ----------
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576
Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium
EpicLordPhone said:
Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Power Button Repair relating to Boot Loop
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
my Sidekick 4G is very old and just now went into bootloop... i googled the word and came across this forum.
As quoted above by previous poster that a power button repair was needed... I figured that I had nothing to lose, it being so old, I smashed the crap out of the Sidekick 4G on its power button. Lo and Behold, it booted into the system successfully.
SO... if no one has any qualms about smashing the crap out of their power button... give it a shot. It worked for me.
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app
EpicLordPhone said:
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app
immorality said:
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
Hmmm thanks, I might just try that!
Sent from my Amazon Kindle Fire2 using xda app-developers app
Mines stuck in a boot loop too.
I don't know if my Sidekicks problem is related to this or not. I rooted it and flashed it over to Glorious Overdose v5 on May 22nd this year and it's been running great. At least it was until last Friday, Sep 13. I was having trouble connecting to the WiFi at my house so I rebooted the phone. When it started to come back up a female voice started saying, "VooDoo lagfix has been disabled." "Converting /data and /system partitions." "Conversion time estimated 10 minutes."
I let it do it's thing and that's all it's been doing all weekend. I can get into recovery mode, I've tried restoring the phone from my backup with no success. I've even tried running through the process of setting up GOv5 again and it says it's successful, but the phone never boots up. It just stays in the same blasted bootloop and saying the same things over and over again about VooDoo. I've checked the VooDoo logs and there is an error file for the 13th and the logs following say "conversion." Can someone point me in the right direction as to what I can do to get my phone working again? Everything I've tried to research so far hasn't worked.
v5 hold both volume button, the track button and power button. Should put you into recovery mode. If not, you will have to put phone into download mode. You do this by taking out battery, then pluging into computer. When you reinsert battery hold volume down and power, if I remember correctly, and your download screen should come up. From your cp manually unroot it. Then it should be fixed, and just reroot it. I hope this was helpful
Sent from my SGH-T839 using xda app-developers app
No idea what I'm doing, precisely, but...
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.
LathyrusRoots said:
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.
Click to expand...
Click to collapse
And almost a year later I log in and see this. Your most welcome. I haven't been working on phones for awhile but if I remember right, some models can be powered on by plugging the phone into a power source and when the phone vibrates or has a sign of life unplugging the unit. Some cables don't work and sometimes doing this via a computer can power up a device. Other than that, the other more dangerous way is to short out the pins on the bottom of the unit. I don't remember the pins but you can google a charge port diagram to help. I don't recommend doing this unless you have absolutely no other choice. Incidentally, this is why a phone will power itself on when a battery is put in and no other button is touched. The port is wet and corrosion has caused a link on the power pin and believe its pin 3. A simple cleaning with 90%+ rubbing alcohol solution will fix if cleaned quick enough.
Hey Guys,
a friend of mine just bricked his HTC-OneS and I'm here to help him get it back to life
He installed the latest PacMan Rom and everything was awesome.
All over sudden the Phone didn't boot up anymore.
It can be charged via USB, so maybe one can do something over USB
Windows-PC doesn't recognize the Phone he says...
As far as I remember its an HTC One s ville c2 (is there anything like this)
Due to the Fact that I'm a Motorola User, I have no idea where to start trying to recover his Phone...
Please Help me do it
do you know how to use some adb/fastboot commands? run fastboot oem getcid in the bootloader.
hold down volume down and power to go into the bootloader.
I would try to get into the bootloader first. That would provide a gateway to possibly fixing his (or her) phone.
Hope to get into bootloader, will get hands in his phone in monday.
Coming from Motorola i'm used to a factory tool where i can flash official Firmware via PC. Is there anything like this for HTC phones?
If not first thing i would try is flashing a New recovery system via fastboot to have sth to work with. Anyone agree with this plan?
Sent from my XT925 using xda app-developers app
I don't think I've ever seen a tool like that. I think the best bet would be to get into recovery, mount and try to flash a new rom (C2 roms in this case).
esok44 said:
Hope to get into bootloader, will get hands in his phone in monday.
Coming from Motorola i'm used to a factory tool where i can flash official Firmware via PC. Is there anything like this for HTC phones?
If not first thing i would try is flashing a New recovery system via fastboot to have sth to work with. Anyone agree with this plan?
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Yes, go to androidruu.com, look for villec2 and click on it. The latest RUU should work unless he is carrier branded. Then you will need to use a carrier RUU.
Got hands on his phone and it doesnt do anything...
No bootloader nothing.
Only thing that happens is that it recognizes its on a wallplug...
Sent from my XT925 using xda app-developers app
Anyone got an idea?
The little charging LED is red, is it possible that there is some kind of battery driver missing, so the phone won't charge anymore and the battery is empty?
and is there an option to solve this?
esok44 said:
Anyone got an idea?
The little charging LED is red, is it possible that there is some kind of battery driver missing, so the phone won't charge anymore and the battery is empty?
and is there an option to solve this?
Click to expand...
Click to collapse
Really sounds like it is hard bricked.
I could mention things that you have already most likely tried.
Holding power down for 30 seconds
holding power down for 10 seconds under bright light so the front sensor registers (prevents messing up your phone while in your pocket)
when plugged in computer, does device manager show it as "qhsusb_dload" (bricked)
Hold power down and volume down for 10 seconds. release power button and continue holding volume down.
From replies from manufacturer that people post here, often they replace the battery and (motherboard?) Seems like something happens and a sudden battery discharge messes up the works.
tivofool said:
Really sounds like it is hard bricked.
I could mention things that you have already most likely tried.
Holding power down for 30 seconds
holding power down for 10 seconds under bright light so the front sensor registers (prevents messing up your phone while in your pocket)
when plugged in computer, does device manager show it as "qhsusb_dload" (bricked)
Hold power down and volume down for 10 seconds. release power button and continue holding volume down.
From replies from manufacturer that people post here, often they replace the battery and (motherboard?) Seems like something happens and a sudden battery discharge messes up the works.
Click to expand...
Click to collapse
Thank you for your response
So quick question, due to the fact that the Phone is hard bricked, can i send the Phone back in, and get things fixed, cause the Phone was s-off and rooted before, so warranty is void.
Is there any way they could find out about it? Like a blown fuse or anything?
esok44 said:
Thank you for your response
So quick question, due to the fact that the Phone is hard bricked, can i send the Phone back in, and get things fixed, cause the Phone was s-off and rooted before, so warranty is void.
Is there any way they could find out about it? Like a blown fuse or anything?
Click to expand...
Click to collapse
Your guess is as good as mine. There was one guy who posted here, that they did fix it, and when they sent it back they had turned back on security, or S-on. So they obviously knew and didn't care. One of those ymmv. I kind of doubt he did anything wrong and it is a defect. People post on here with completely stock w/ same symptoms.
tivofool said:
Your guess is as good as mine. There was one guy who posted here, that they did fix it, and when they sent it back they had turned back on security, or S-on. So they obviously knew and didn't care. One of those ymmv. I kind of doubt he did anything wrong and it is a defect. People post on here with completely stock w/ same symptoms.
Click to expand...
Click to collapse
Thank you dude, will give it back to him and tell him, that he should send the phone back, cause it seems like this is a common problem
Greetz Esok
Hey guys,
Earlier on, out of nowhere, my nexus 5 become totally unresponsive.
Screen is black and won't turn on
Usual methods of accessing bootloader fail (holding down vol +/- and power)
No response from the phone in terms of plugging it into a PC
--------Do however get a response from the computer; comes up as "Qualcomm HS-USB QDLoader 9008 (COM3) in the "Ports" subsection of my Device Manager
Phoned Google, they seem to think the phone is still turned on, and is therefore not Hardbricked (I have my doubts)
Phone is unlocked, rooted and running Android L (Huge mistake, I know)
-------Installed Android L Months ago without any trouble whatsoever, so no connection to now, surely?
Can anyone help, please? Google will replace it, but there are some irreplaceable images on my phone that I stupidly don't have backed up. Right now, I'd be happy with having the phone replaced and scraping as much data off it as I can, but I know, if I can't, its through my own stupidity of not having it backed up.
Thanks,
Nick :/
I'm afraid it's dead and you can't recover anything off it.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I'm afraid it's dead and you can't recover anything off it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately, I think you're right. I just don't understand what caused it, one minute it was working fine, the next it was dead.
Gonna see if I can get a connection through adb, not holding my breath, but I might be able to get something from it. If not, then back to google it goes.
Ser Nick said:
Unfortunately, I think you're right. I just don't understand what caused it, one minute it was working fine, the next it was dead.
Gonna see if I can get a connection through adb, not holding my breath, but I might be able to get something from it. If not, then back to google it goes.
Click to expand...
Click to collapse
I had a device do the same thing. It was on and everything running fine and then just went dead. Luckily it was still under warranty. The Qualcomm error you get said it all to me. Adb isn't going to work but try it anyway. Who knows, maybe you'll get lucky.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I had a device do the same thing. It was on and everything running fine and then just went dead. Luckily it was still under warranty. The Qualcomm error you get said it all to me. Adb isn't going to work but try it anyway. Who knows, maybe you'll get lucky.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The first google search of the Qualcomm thing pretty much told me it'd Hard Bricked itself, I just hoped that perhaps I'd get lucky and it'd sort itself out or I'd find a solution.
It doesn't always come up as that though, sometimes it comes up as unrecognized device, which, I suppose isn't much better.
Thanks for your help anyways
You need a blankflasher to get back your bootloader. It's corrupted!