Related
Hi all,
As the title says :'( I flashed the new Android Revolution HD 3.6.2 ROM (updated from 3.6.0) and the recommended radio yesterday. Everything went fine and the phone was smooth as ever.
However, while I was playing robo defence today (played for about 5 mins) the phone suddenly shut down, rebooted itself to the startup screen (HTC Logo on a white screen) then when to a black screen and then repeated the process. This happened about 5 times after which I pulled the battery and then tried to restart the phone.
Now the phone won't power on at all!
- Nothing happens when I press the power button.
- Tried vol + power: nothing.
- Took the battery out, waited 20min, tried the above again: nothing
- Plugged it into my pc: nothing i.e. no LED light either
- Plugged it into a wall charger: nothing i.e. no LED light either
What I don't understand is how come my phone has died when I was not in the middle of flashing anything? Has my phone actually bricked itself?
any help would really be appreciated!
Thanks
Is there anything I can do via adb? (I don't know how to use it that well)
Keep trying to boot into vol+down and power
Leave phone on charger and try the button combo that happened with my mytouch when I had one and that worked.
Sent from my HTC Sensation XE with Beats Audio
Remove SD card, boot in recovery, clear cache / dalvik.
If you can boot of cource.
charlieb620 said:
Keep trying to boot into vol+down and power
Leave phone on charger and try the button combo that happened with my mytouch when I had one and that worked.
Sent from my HTC Sensation XE with Beats Audio
Click to expand...
Click to collapse
I've tried that. Still no luck No LED charging light either
septix said:
Remove SD card, boot in recovery, clear cache / dalvik.
If you can boot of cource.
Click to expand...
Click to collapse
No I can't boot at all. Tried booting without the SD card and no luck.
Is it even possible from for a phone to brick itself? Because after I flashed the ROM everything worked fine. It was only when I was playing a game that it died.
Could it be a battery problem? It would explain why no charging light is showing up
charge it via the original charger, hold on for a little while and try booting it up
i've seen it happen to mine once, i panicked just like you.
Before I s-off'ed or rooted I had this happen to my phone. It took a battery pull and then a long hold of the power button to get it to boot. I freaked thinking it was a dud (I had just gotten the phone).
If nothing works, it may be a hardware failure that had nothing to do with rooting. I would go for a warranty exchange. If YOU cannot get it to boot, neither will they without re-flashing the phone the hardcore way. (I believe its called a JTAG?). They will never know you rooted. They will just try a quick boot, see it doesnt, and then open it up to re-flash the thing via factory methods.
Matt
Would have to say its prob an fault with the handset as i am running the same setup as you and also playing robo defence and i play it for about 45 mins at a time with no issues at all .
awesam said:
charge it via the original charger, hold on for a little while and try booting it up
i've seen it happen to mine once, i panicked just like you.
Click to expand...
Click to collapse
Going to try that tonight. Its my last resort because i've exhausted every other option.
Diydude said:
Would have to say its prob an fault with the handset as i am running the same setup as you and also playing robo defence and i play it for about 45 mins at a time with no issues at all .
Click to expand...
Click to collapse
LOL...robo defence love! Thinking about it...it could be a handset issue. When I use the play robo defence on ARHD 3.6.0 ROM the phone would always die or go into a boot loop. But now its just dead.
Any news?
Sent from my Sensation using xda premium
would it be ground problem? check all the contact points
---------- Post added at 08:53 PM ---------- Previous post was at 08:45 PM ----------
would it be ground problem? check all the contact points hope it'll help
Just to update you guys:
I tried everything that has been suggested on this thread and had no luck.
I've sent off my phone to HTC today to hopefully get it fixed. we'll see how it turns out. They said it should be done and on the way back in 7 days. Will post if I get new info or updates
Installing the same Rom I had the same issue. New phone is on the way so I thought what harm could it do now. I tried everything u did. What worked was pulling battery out plug the wall charger in and then hold the power and vol down button then slip in battery and it went into recovery . I tried a reg reboot and nothing. So I pulled sd card out and put into another phone then downloaded another Rom. Put sd card back in shot phone and got back into recovery and flashed a diff Rom and it worked. The phone over heating is bad tho so will leave it be till New phone comes in.
I've had the no boot problem after messing with my partition tables, took it to my carrier, and they fixed it. Hopefully, your phone is so messed up that they can't read that it's been rooted (or hope that they don't care)
Did you install any Kernels with GPU Overclocking for example? Or was it only the normal ROM?
What recovery are you using?
CrazyCharlie said:
What recovery are you using?
Click to expand...
Click to collapse
Clockwork. Can't remember the version
xotox83 said:
Did you install any Kernels with GPU Overclocking for example? Or was it only the normal ROM?
Click to expand...
Click to collapse
No I didn't. Just stock ROM and the standard kernel that came with it. No overclocking either. I mentioned this before - i use to have boot loops every time i played robo defence - even with ARHD 3.5.x. so I reckon it was a hardware issue that eventually kicked the bucket when I moved to 3.6
Matt1408 said:
I've had the no boot problem after messing with my partition tables, took it to my carrier, and they fixed it. Hopefully, your phone is so messed up that they can't read that it's been rooted (or hope that they don't care)
Click to expand...
Click to collapse
Yea...i'm hoping exactly that! its being repaired atm. finger's crossed!
Have u try to connect ur phone to ur pc see if it detected? If you connect ur phone to ur pc and it show up something like can't find the driver that mean is ur phone got hardware issue just call HTC they will fix for you.
Johnsonyc said:
Have u try to connect ur phone to ur pc see if it detected? If you connect ur phone to ur pc and it show up something like can't find the driver that mean is ur phone got hardware issue just call HTC they will fix for you.
Click to expand...
Click to collapse
Yep tried that. My PC didn't detect it - there was no response from either device. Tried to force my PC to detect all connected usb devices and no luck.
My Phone Lives!
Hi guys,
Just to update everyone: I got my phone back yesterday and it's working again!!
Although it has been returned to stock again. According to the letter that came with my phone I think I've got a new main board. This is what it says:
Parts Replaced: PCBA-Main Board with SKU_ID, HTC Global, QSD8260 UMT
Anyone know what it means for sure?
I guess there is hope if a phone bricks itself entirely! and HTC didn't even bother asking any questions i.e. if I rooted my phone or anything. All they asked me was did I try to charge the phone via the main charger, did I take the battery out etc.
Good for you dude. I'm happy it worked out fine for you! And thanks for the update, good to know how they handle things over there.
Sent from my Sensation using xda premium
Hi guys,
I've run into some problems, I installed Android Revolution HD 6.5 two days ago. Everything worked like a charm, now I shutted down my phone to go in recovery, sadly enough my phone won't reboot, does not charge nor does it respond to my desperate pushes on the power button. Anyone experienced anything like this?
Worth mentioning also is that the battery was 80+% charged.. So it would seem strange to me that this would anything to do with eventual dead battery.
Just to be clear: hadn't installed anything, nothing less, nothing more.
If I could just get acces to bootloader through usb or anything like this.
I fear that there is someting seriously wrong here?
What are you guys thinking? Any possible solutions?
Hi,
The same thing more or less happened to me.
My phone went dead one night and wouldnt turn on, charge or connect with the PC. I had already arranged a repair with HTC for another issue and so I sent it off to them and a few days later I now have it back and it is working fine so far.
They replaced the mainboard and a few other bits and pieces all under warranty.
I hope you get your phone fixed and sorted asap.
Mustak
mustakg said:
Hi,
The same thing more or less happened to me.
My phone went dead one night and wouldnt turn on, charge or connect with the PC. I had already arranged a repair with HTC for another issue and so I sent it off to them and a few days later I now have it back and it is working fine so far.
They replaced the mainboard and a few other bits and pieces all under warranty.
I hope you get your phone fixed and sorted asap.
Mustak
Click to expand...
Click to collapse
Did you root it or anything like that? It really seems like an hardware issue.. Thanks for your reply also btw.
TP-Power said:
Hi guys,
I've run into some problems, I installed Android Revolution HD 6.5 two days ago. Everything worked like a charm, now I shutted down my phone to go in recovery, sadly enough my phone won't reboot, does not charge nor does it respond to my desperate pushes on the power button. Anyone experienced anything like this?
Worth mentioning also is that the battery was 80+% charged.. So it would seem strange to me that this would anything to do with eventual dead battery.
Just to be clear: hadn't installed anything, nothing less, nothing more.
If I could just get acces to bootloader through usb or anything like this.
I fear that there is someting seriously wrong here?
What are you guys thinking? Any possible solutions?
Click to expand...
Click to collapse
Hi,
Is there any chance the battery pins could be damaged or bent?
Is there any way for you to get hold of another battery(from a shop or friend) and try that?
I will test the battery in the laboratory tomorrow.. I've read you should get a minimum of 3.6V or something like that? Curious to see what has caused this problem. Do you think htc would see I flashed a custom rom on it if I send it to repair?
TP-Power said:
I will test the battery in the laboratory tomorrow.. I've read you should get a minimum of 3.6V or something like that? Curious to see what has caused this problem. Do you think htc would see I flashed a custom rom on it if I send it to repair?
Click to expand...
Click to collapse
Hi,
That is why i suggest a different battery.
If they can switch it on,they will see the s-off.
If they cannot,it does not matter.
malybru said:
Hi,
That is why i suggest a different battery.
If they can switch it on,they will see the s-off.
If they cannot,it does not matter.
Click to expand...
Click to collapse
They don't use a JTAG unit or anything like that to see what has went wrong than I presume? Well, first thing I'll do is test it right away at the laboratory. I will post the result in the evening.
TP-Power said:
Did you root it or anything like that? It really seems like an hardware issue.. Thanks for your reply also btw.
Click to expand...
Click to collapse
My sensation was rooted and had a custom ROM on, but I was preparing to send the phone back in when it got bricked. I had managed to install stock rom and do S-on but the phone had an unlocked bootloader using HTC dev website, so I was worried they wouldnt do the repair.
As it happens they did all the work under warranty and didnt say/ mention having unlocked bootloader. It has come back locked though.
Was anybody able to find a fix for this?
My sensation 4g has basically the same problem. After rooting and installing ICS it worked fine for a few days then it ceased booting or responding to a charger (no LED response). I was able to turn on the phone again by letting it sit for a while but no luck lately. I'm wondering if my phone is bricked?
When I press the power button the screen stays black with lights on (no LED).
I can't get into bootloader and the phone is not detected by ADB, I tried the unbricking project thread by Dexter, however my phone is not detected by linux. On windows, i did get it to detect as qhsusb_dload.
Any thoughts would be helpful!
Thanks
asuen06 said:
Was anybody able to find a fix for this?
My sensation 4g has basically the same problem. After rooting and installing ICS it worked fine for a few days then it ceased booting or responding to a charger (no LED response). I was able to turn on the phone again by letting it sit for a while but no luck lately. I'm wondering if my phone is bricked?
When I press the power button the screen stays black with lights on (no LED).
I can't get into bootloader and the phone is not detected by ADB, I tried the unbricking project thread by Dexter, however my phone is not detected by linux. On windows, i did get it to detect as qhsusb_dload.
Any thoughts would be helpful!
Thanks
Click to expand...
Click to collapse
If your getting QHSUSB DLOAD I'm so sorry to tell you as I believe your device is HARD BRICKED. You can try jtag. If you search there are several companies who will jtag. I'm wishing you the best and I'm sorry about your device.
Sent from my HTC Sensation 4G using xda premium
I had to return my HTC Sensation to the repair center. Apparently the motherboard just fried. I got a new motherboard and just S-OFFed the phone again. Very weird problem though. As has been said in this post earlier, if they can't turn on the device they won't see it is S-OFFed and your warranty will apply.
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.
Hope you can help.
Today in the morning, I wake up and see that my phone was stuck at the google logo. I removed the battery but after put it again, the phone didn't start. No google logo, no recovery screen, nothing.
Does anyone know an alternative method to start (resurrect) this thing?
Model: i9020a
ROM: AOKP JB M1
Kernel: Marmite 6.7
Are you able to load fastboot using the power and vol up button?
digitalguy13 said:
Are you able to load fastboot using the power and vol up button?
Click to expand...
Click to collapse
Nop. There is no response at all.
jpvalenz said:
Nop. There is no response at all.
Click to expand...
Click to collapse
Remove the battery for a while. While the battery is out, plug the phone in with both AC and USB charging.. this will help you see if it's a defective battery
Sent from my awesome Nexus S
FirePoncho86 said:
Remove the battery for a while. While the battery is out, plug the phone in with both AC and USB charging.. this will help you see if it's a defective battery
Sent from my awesome Nexus S
Click to expand...
Click to collapse
No, this also didn't work.
Hmm.. I'm really not sure how to help
FirePoncho86 said:
Hmm.. I'm really not sure how to help
Click to expand...
Click to collapse
What is curious is that whatever button combination you use, there is no response at all. And the phone was working without problem only a couple hours before. Even if I plug, there is no battery charging image.
Battery's dead?
jpvalenz said:
What is curious is that whatever button combination you use, there is no response at all. And the phone was working without problem only a couple hours before. Even if I plug, there is no battery charging image.
Click to expand...
Click to collapse
Aw man and I thought I had it bad... lol. Good luck with this!
I would try getting your hands on another battery though. I don't think the phone would boot up without a recognizable battery whether it had enough power or not. Maybe someone that actually knows can say... Either way I'll try it with mine tomorrow (mine boots into fastboot and recovery at least) and let you know
Looks like trying out another battery might be the only next logical step. No response even when plugged in for charging indicates a possible battery issue.
hey...
you got a similar condition with my phone...
dont know what to do now...
jpvalenz said:
Hope you can help.
Today in the morning, I wake up and see that my phone was stuck at the google logo. I removed the battery but after put it again, the phone didn't start. No google logo, no recovery screen, nothing.
Does anyone know an alternative method to start (resurrect) this thing?
Model: i9020a
ROM: AOKP JB M1
Kernel: Marmite 6.7
Click to expand...
Click to collapse
I had read a lot of forums that said that with the JB upgrade (any type: AOSP, OTA, etc), after some time, theirs phones gone dead as well. Seems there is some problem with the bootloader that affect the mainframe (motherboard?). No one has been able to resolve this problem.
jpvalenz said:
I had read a lot of forums that said that with the JB upgrade (any type: AOSP, OTA, etc), after some time, theirs phones gone dead as well. Seems there is some problem with the bootloader that affect the mainframe (motherboard?). No one has been able to resolve this problem.
Click to expand...
Click to collapse
So you are saying that Jelly Bean bricks the Nexus S? Where have you read this? It seems like a very serious accusation/assumption.
jpvalenz said:
I had read a lot of forums that said that with the JB upgrade (any type: AOSP, OTA, etc), after some time, theirs phones gone dead as well. Seems there is some problem with the bootloader that affect the mainframe (motherboard?). No one has been able to resolve this problem.
Click to expand...
Click to collapse
interesting.....anything to back this up....
Maybe a jtag could resolve your problem
http://www.youtube.com/watch?v=Ecp8jKmm48k
Mine is doing the same thing. At least it turns on to the Google screen if I remove the chip labled sandisk. Its also the card that has the nfc contacts. Any solution yet?
Sent from my PC36100 using xda app-developers app
I had the exact same thing happened to me. I installed a custom jb ROM (I was already using an earlier version of the same rom) and I noticed abnormal battery drain and in a few hours it died completely. No response at all. Tries different batteries, chargers, everything. I tried sending it in to get it fixed but I was told they found corrosion on the board which was true so it would coat 450 to fix! But I know for a fact that wasn't the reason why the phone was completely unresponsive. I went to wind to get it fixed and the guy told me that they've been getting a crap load of nexus s devices back for the exact same reason. This coincided with the jelly bean upgrade. There's definitely an issue happening with the upgrade but Google or Samsung aren't saying anything.
Sent from my Nexus 4 using xda app-developers app
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.