Related
I really don't know what's just happened...I think maybe my TP2 just decided to die on me.
I was using NRGZ Leo ROM from 22nd Feb. All was going well until my battery ran out today. At the time, my daughter was playing a game on it, not from WM, but from the Android port (Haret). While she was playing, I heard the familiar short vibrate of a soft reset. I know my battery was low and I suspect the battery wasn't charging, although it was plugged in (not sure if Android supports charging yet in the later builds)
Anyway, for some reason, it wouldn't go past the vibrate/Touch Pro2 screen. It just kept resetting and looping back. I attempted to do a hardware reset (power button, talk/send, end buttons) but accidently chose the wrong combo (power button, volume down) and entered bootloader. No problem yet, just reset and try again, right? Only I didn't get the chance, as it reset itself and looped through bootloader.
Now I am stuck in this loop. I can't flash from SD as it wont stay on long enough before self-resetting to find the RHODIMG.nbh on the card. I can't connect to my PC as it wont stay in bootloader long enough before self-resetting for my PC to install the "Windows Mobile Device" drivers, and even if it did, when it self-resets, it would disconnect anyway. I can't connect to MTTY for the same reason. I can't connect to ActiveSync or WMDC as I can't boot to WM to get ActiveSync running on the device.
When plugged in to AC power or through USB, it fires itself up automatically and into this loop, and it wont turn off manually, reset or accept any other button combos to enter RUU (from SD method) or to do hard reset. When it is not plugged in to any power source it won't even switch on.
I suspect it is resetting as it is not charging. I'm guessing that when in bootloader, charging is disabled, and I think this because I was originally getting 3 seconds of bootloader, now I am getting around 8 seconds, but it doesn't get any better than that, and I don't know of a rom upgrade method that can be done in 8 seconds! There are a few seconds of charging time before bootloader kicks in and the orange LED goes out and presumably stops charging. Am I right in thinking there is no charging in bootloader and in the Android port (I am using the latest version from 27/2, rhod100).
Basically, to summarise, I am stuck in bootloader-reset-bootloader loop, I cannot connect to pc in any way, flash from SD, Hard Reset, I have very little or no battery and it won't charge because it keeps going into bootloader where there is no charging taking place and it wont turn off to charge that way either.
Any help will be greatly appreciated. I don't hold out much hope though. At the moment, it doesn't seem that I am able to interact with it at all to make it do anything different or to manipulate what it is trying to do. Hopefully someone will see something familiar and maybe have some suggestions.
Oh, and by the way, it's nothing to do with a bad flash. I've been doing this for long enough to know what I'm doing, and I wasn't even doing a rom upgrade at the time. My last rom upgrade was 2 days ago and all went well, and I have been using it without problems since, until now. I haven't flashed my Radio or SPL since HSPL was released, so I know it has nothing to do with that either.
Thanks in advance for anyone who can give any advice at all, or even just take pitty on me! Apologies for all the text. I know it looks boring and may put some people off reading, but I needed to get all the info in.
Are you able to charge when it completely turned off?
can you pull the battery out, put it back in and simply charge for an hour or so to get some juice into the battery?
Then you could maybe reflash it from the bootloader or sd card...
shadixs said:
Are you able to charge when it completely turned off?
Click to expand...
Click to collapse
I can't get it to turn off, power button has no effect.
clauswl said:
can you pull the battery out, put it back in and simply charge for an hour or so to get some juice into the battery?
Then you could maybe reflash it from the bootloader or sd card...
Click to expand...
Click to collapse
If I take the battery out, obviously, it cuts the power and the looping stops...until I put the battery back in, and it starts itself again. I can't stop the loop and I can't turn the power off or even stop it switching itself on.
matmaneyre said:
I can't get it to turn off, power button has no effect.
If I take the battery out, obviously, it cuts the power and the looping stops...until I put the battery back in, and it starts itself again. I can't stop the loop and I can't turn the power off or even stop it switching itself on.
Click to expand...
Click to collapse
I had exactly that problem after a bad romflash. I bought a decktop cradle for the tp 2 that has 2nd. battery charger. Charged the battery and reflash, everything was ok again.
So, juice up the battery and do a hard reset or reflash..
SOMETHING LIKE THIS
I know you prob dont wanna hear it, but id say its a warranty job. Theyll just force flash it anyway so they wont notice the rom you were using.
Cheers guys. I thought it might be the rom. Not sure how though as like I said, my last rom flash was a couple of days ago and it was fine. Guess these things just happen sometimes. I'll try and get the battery charged somehow. Trouble is, I don't know another single person who has a TP2, so it looks like the cradle option I think. It did cross my mind to be honest when I was trying to think of alternative charging methods.
As for the warranty idea, if it can be avoided, I'd rather not take that route if I can help it, but thanks for the suggestion. Lets just say that will remain an option as my last resort if all else fails.
Still open to suggestions if anyone knows of any miracles....any Hogwarts graduates kicking about these forums with a few magic words to spare?
Hey man, I had the same issue when my phone wouldn't for some unknown reason charge.
1) Take our your battery
2) Plug in your DESKTOP CHARGER (not USB from PC!!) to microUSB slot
3) Put your battery back
4) Wait few moments (5 minutes)
5) and you are ready to boot, now you can even charge from USB. No idea why, but looks like booting takes more than 500mA :O
If it wont help, swap those 2 and 3 points
Hey guys! Please give this thread a better title. More related to the problem. Sounds like it could be useful in the future for hopefully very few people.
OK, I will change the thread title. I searched for quite a while but couldn't find any similar cases. But it seems it is more common than I thought since I raised the issue, so a new, more specific title might be more beneficial to other users experiencing similar problems.
For the record, I haven't solved it yet. Waiting on a standalone battery charger I bought from eBay. Didn't really want the cradle. THIS is the one I have bought. I will update on my progress when it arrives.
Thanks for your help to all who have contributed so far.
Hi I have the same problem the phone won't charge or connect via usb I think it is a faulty usb port the phone have & because of that it is causing the phone to go to bootloader.
I've had this happen before, just plug it into the mains charger (wall charger) and let it sit for a while. It will loop a couple times but once there is enough juice in the battery it will be back to normal.
Since you have RHODIMG.nbh on your sd card, maybe taking your sd card out would help it a bit.
There have been other posts with the same issue and plugging it into mains will solve the problem
spark001uk said:
I know you prob dont wanna hear it, but id say its a warranty job. Theyll just force flash it anyway so they wont notice the rom you were using.
Click to expand...
Click to collapse
Not true. just the battery is really low, once charged enough to power device after boot, everything will be back to normal.
fone_fanatic said:
Not true. just the battery is really low, once charged enough to power device after boot, everything will be back to normal.
Click to expand...
Click to collapse
Seems like it would make sense. I don't have my wall charger on me now...does the Rhodium not boot up without a battery in it? I thought my old Hermes did, guess I've never tried it with the TP2.
This might sound a little stupid, but I actually know somebody that said it worked for his iPhone (waste of 3-4 mins if not). Plug in the USB charger from PC. Reboot the PC without disconnecting the phone. Wait 3-4 minutes...
Toleraen said:
Seems like it would make sense. I don't have my wall charger on me now...does the Rhodium not boot up without a battery in it? I thought my old Hermes did, guess I've never tried it with the TP2.
Click to expand...
Click to collapse
from what i remember, it won't boot without the battery.
fone_fanatic said:
I've had this happen before, just plug it into the mains charger (wall charger) and let it sit for a while. It will loop a couple times but once there is enough juice in the battery it will be back to normal.
Since you have RHODIMG.nbh on your sd card, maybe taking your sd card out would help it a bit.
There have been other posts with the same issue and plugging it into mains will solve the problem
Click to expand...
Click to collapse
I left it looping for hours....no joy I'm afraid. Just gonna have to wait for this charger to arrive I think
Toleraen said:
Seems like it would make sense. I don't have my wall charger on me now...does the Rhodium not boot up without a battery in it? I thought my old Hermes did, guess I've never tried it with the TP2.
Click to expand...
Click to collapse
fone_fanatic said:
from what i remember, it won't boot without the battery.
Click to expand...
Click to collapse
Definitely doesn't power up plugged in without a battery. Battery needs to be present. Still waiting on this charger though. I'm hoping it's not one of those where it says the item location is Cardiff (UK) when actually it's in Hong Kong and takes 14 years to arrive
soocerclaude said:
Hi I have the same problem the phone won't charge or connect via usb I think it is a faulty usb port the phone have & because of that it is causing the phone to go to bootloader.
Click to expand...
Click to collapse
I really don't think it's the mini usb port as it charges and tries to connect to pc before bootloader kicks in & it all stops.
Hi I found a way 2 get past the bootloader loop just plug your headphones went in bootloader and restarted the phone but it still won't charge or sync with computer.
soocerclaude said:
Hi I found a way 2 get past the bootloader loop just plug your headphones went in bootloader and restarted the phone but it still won't charge or sync with computer.
Click to expand...
Click to collapse
Well when I unplug the ac adapter, mine doesn't last on bootloader for more than a couple of seconds before dying. Doesn't even get to the RHODIMG.nbh update screen that way - not enough charge (I'm still hoping). Tried charging overnight while looping but still wouldn't charge enough. The trouble is that obviously the bootloader is killing the battery as it's not charging very much.
Got my charger finally....but they sent the wrong one. Waiting on a response from the seller. The "dock" on the charger wasn't big enough, so while the connectors were in the right place to charge the battery, the battery didn't sit flush, so they wouldn't reach the points on the battery itself. Hope they have a TP2 one & it's not just them thinking it's compatible, as it's the only one on the whole of ebay UK that has them in stock in the UK. Don't want to have to wait up to 2 weeks for one from HK.
I will keep you posted anyway.
Hi I brought mine 2 get fix because my warrenty got void due 2 water damage. I think it is the usb port that is causing this, saw in other forums the same thing. Will get back the phone on monday & I will update u on the situation.
Hi all,
I desperate need help. After an unsuccessful radio flash, my Desire won't even turn on. No response from any buttons or lights. Here's how it happened:
I'm relatively new to Android. I recently bought a Desire, to replace my Touch HD, which has seen about 25 different WM ROMs, over it's life.
I successfully rooted my Desire and had tried a few ROMs. I was sitting on the MoDaCo Custom ROM r17, which was all customised and running perfectly. I'd even used ADB to successfully update my wifi config to connect to my company LEAP-authenticated network.
I decided to flash the latest radio (32.37.00.32U_4.06.00.16_2), from this thread:
http://forum.xda-developers.com/showthread.php?t=687464
I entered Recovery using 'Fake-Flash';
I started flashing the radio image;
All the good messages were scrolling down the screen;
I kept one eye on the phone while I worked on my laptop;
I saw a message saying something to the effect of "Finished installing radio..." (sorry, I don't remember the exact wording);
The blue recovery menu had returned, with 'reboot device' as the default selection;
As I clicked the trackball, I saw another message appear under the 'finished' messages, which said "Writing rad " I guess it didn't have time to print the whole message, when I selected reboot.
The screen went blank then a graphic appeared in the middle (where the recovery exclamation mark and triangle usually appear), of a software box with a curved yellow arrow over it and the android icon peeking out from behind it. I left it for a while (already had that sinking feeling) then pressed the power button. It switched off and stayed there.
Since then, nothing that I've tried has received any response. Various combination's of button pushes, USB connection, removed SIM, SD and battery...nothing, not even an LED.
I've searched and haven't been able to find any solutions to this particular situation. Can anyone help, or am I totally bricked?
Regards, PF.
The radio update does 2 reboots to install it. The software box with yellow arrow is the default graphic used by the fake flash recovery as far as I know so that wasn't any real problem.
I know this might sound silly, but is the battery charged?
socktug said:
The radio update does 2 reboots to install it. The software box with yellow arrow is the default graphic used by the fake flash recovery as far as I know so that wasn't any real problem.
I know this might sound silly, but is the battery charged?
Click to expand...
Click to collapse
No question is silly under this circumstance!
Yes. I'd just taken it off overnight charge. 100%. If I plug the USB cable in now, there is no response from the LED.
Leave the charger plugged into it for about 5 minutes and see if there is any response to it. With the usb bricks it would take nearly 5 mins to register and the led to light up.
I know this isn't a usb brick, but I've not seen anyone with a failed radio flash that has caused the phone to totally die to the extent that it won't even switch on.
I take it you have tried the usual power and volume button combos etc?
I suppose if there is no quick fix for this, the fact that it's totally dead may go in your favour if you try to get it repaired/replaced under warranty
socktug said:
Leave the charger plugged into it for about 5 minutes and see if there is any response to it. With the usb bricks it would take nearly 5 mins to register and the led to light up.
I know this isn't a usb brick, but I've not seen anyone with a failed radio flash that has caused the phone to totally die to the extent that it won't even switch on.
I take it you have tried the usual power and volume button combos etc?
I suppose if there is no quick fix for this, the fact that it's totally dead may go in your favour if you try to get it repaired/replaced under warranty
Click to expand...
Click to collapse
ok. The charger has been plugged in for 35 minutes and still no response.
Also don't want to sound patronizing, but have you taken the battery out and turned on with the back button helld?
Ignore me, just reread your original post.
the procedure u said sounds rite, thats whats ment to happen, when you flash a radio, only other thing that comes to mind is, sure the radio u flashed was for the gsm desire?
so what youre saying is that your phone simply doesnt turn on, not for a second?
if you press the power button NOTHING happens?
are you sure your charger isnt broken?
have you tried charging it through your pc?
have you seen if its recognised through adb devices on your computer?
have you tried a new battery?
if your phone is simply dead, it must be a hardware problem, in which case you can probably send it off for repair and not have your warranty void as the whole phone will need to be replaced. they cant identify if you have voided your warranty if your device doesnt turn on.
cgrec92 said:
so what youre saying is that your phone simply doesnt turn on, not for a second?
if you press the power button NOTHING happens?
are you sure your charger isnt broken?
have you tried charging it through your pc?
have you seen if its recognised through adb devices on your computer?
have you tried a new battery?
if your phone is simply dead, it must be a hardware problem, in which case you can probably send it off for repair and not have your warranty void as the whole phone will need to be replaced. they cant identify if you have voided your warranty if your device doesnt turn on.
Click to expand...
Click to collapse
Right first time. It won't turn on at all. It doesn't react in any way to any of the button combinations I'm aware of from rooting and flashing it. Nothing happens at all.
I live in an HTC household, so I've tried a number of chargers and cables, including the PC's USB port. I haven't tried another battery...but the incumbent battery was holdng a good charge and was 100% at the time. What's more, I remember that the phone can run on the charger without the battery.
Not surprisingly, adb devices shows no connected devices.
I think everyone is right, it's back to HTC. I *hope* you're right that they cover it under warranty. I'm going on the weekend, so I'll let you all know the result.
Thanks to all for your help.
I think you can try to remove battery, leave the phone with no battery for 30 minutes and then try to insert battery and connect to usb without power it on to check if LED (and than the phone) is revived.
I had an Acer Liquid that gave me same problem, pratically when a flash on the radio go wrong, the device go in "protection mode". You must also check on the net if there is a protection mode on Desire too, and if there is a button combination to unlock it. I repeat: i just giving an idea becouse the same problem happened for me on an Acer Liquid, so i'm not sure if it's the same for the Desire.
Good Luck
Maybe a usb brick? No usb is no charging. So when you didn't had a full battery, it may be went wrong on that.
Try another battery, if you can get to one.
peewster said:
Maybe a usb brick? No usb is no charging. So when you didn't had a full battery, it may be went wrong on that.
Try another battery, if you can get to one.
Click to expand...
Click to collapse
In the usb brick situation you can still charge. This isn't it!
socktug said:
In the usb brick situation you can still charge. This isn't it!
Click to expand...
Click to collapse
Ok i didn't know that.
If the phone doesn't turn on at all, you can maybe try sending it back to the shop for replacement. Chances are, they won't be able to know what happened, so you can pretend it just stopped working.
If it gets back to HTC, they probably won't bother to figure out what's wrong with the phone and just give you a replacement. Otherwise, they'll just send you the phone back and you won't have lost much (maybe postage costs?).
ash1684 said:
I think you can try to remove battery, leave the phone with no battery for 30 minutes and then try to insert battery and connect to usb without power it on to check if LED (and than the phone) is revived.
I had an Acer Liquid that gave me same problem, pratically when a flash on the radio go wrong, the device go in "protection mode". You must also check on the net if there is a protection mode on Desire too, and if there is a button combination to unlock it. I repeat: i just giving an idea becouse the same problem happened for me on an Acer Liquid, so i'm not sure if it's the same for the Desire.
Good Luck
Click to expand...
Click to collapse
Thanks for the suggestion. I left the battery out overnight. Then tried to activate it (all the usual button combos) with:
Battery out, USB cable plugged in;
Battery in, USB unplugged;
Battery in, USB in.
I scoured the 'net for anything on protection mode for the Desire...no luck. If there is one, it hasn't been posted yet.
I would just act stupid and try to return it under warranty!
I think it should be ok to RMA this, if its completely bricked there is no way of them knowing that you tried a different radio.
Umbrella Corp. said:
I think it should be ok to RMA this, if its completely bricked there is no way of them knowing that you tried a different radio.
Click to expand...
Click to collapse
Yes, if it's totally bricked then just send it back to HTC and they will change it with no problems just same as acer done with my Liquid
All's well that ends well
Good news...
The HTC service centre were kind enough to replace my 'faulty' handset.
Re-flashed with r19 and radio updated (patiently) successfully.
Thanks all for your support.
Nice one. Glad it worked out for you
Sorry this is a long one. Phone is a Verizon Galaxy Nexus about five months old.
Using Galaxy Nexus Root Toolkit v.1.3 I managed to get the phone unlocked and (I think) install clockwork mod but when attempting to flash to root I got as far as "install from zip file . . .' but the next option "select zip file . . ." leads to a either an icon of a hat (which I presume is clockwork icon?) or a picture of an android with his belly open and an exclamation mark in a red triangle. I can no longer get to this point to confirm exactly which. Now when attempting to get to recovery mode I get into fastboot but after selecting "recovery mode" I always get the android with his belly open and a red exclamation mark and can never get to any menu.
Now all of a sudden possibly as a result of this process or else by coincidence usb on the phone appears to be either dead or sub-functional. This may also be why I could never flash to root, (bad USB led to corrupt or missing zip?). Windows does not detect any usb connection from phone, not even a failed one (no sound, no error message) but I have confirmed it's not the PC's error as other usb connections are working.
Also, confirming some sort of USB issue, the phone does not show the charging icon when I plug it into a charger UNLESS the phone is powered off, when I do see the charging animation. To make matters even more confusing despite not seeing the charging icon or the battery manager reporting that the battery is charging the phone does appear to be charging even while powered on but this was only after one night and I'm not quite 100 % certain it charged or that it charged at the usual speed. (thankfully I have an extra, separate, standalone battery charger).
I have re flashed to factory from the " backup and reset" menu inside Android and this did not help.
Simple question: any way to RELOCK phone without USB so I can at least make the phone appear un-tampered with so I can get a warranty service or replacement to fix the apparent usb problem?
bigger question: wtf is going on, is the usb issue perhaps a software problem? and is there anyway to fix the failed flashing process by perhaps transferring a zip file by some other means than usb to the proper directory?
Thanks for anyone who bothered to read this far.
Note: the actual sequence of events is a bit more complicated and now foggy in my memory but this I hope is close enough. If anyone wants more info I'll try to supply it. Let me just say that there were issues from the start of this process. merely unlocking the phone the first time had bricked my boot, all I saw was "Google" and a picture of an un-locked lock, getting into fastboot and then choosing recovery mode led to the picture of the belly up android but after several attempts I finally got past that one time and elected to flash back to stock from recovery menu. This was all before trying to root.
No to first question.
As for second question, pull the battery for about 10 minutes and see if it fixes your USB issue. Don't connect it to a computer to test the charging issue, and instead an outlet.
adrynalyne said:
No to first question.
As for second question, pull the battery for about 10 minutes and see if it fixes your USB issue. Don't connect it to a computer to test the charging issue, and instead an outlet.
Click to expand...
Click to collapse
Trying now, will report back. I think I already tried this though. I should also tell you I have three different batteries and behavior is same for all of them.
I'm not thinking its the battery but something stuck in hardware. Hence the leave it out for 10 minutes.
Left battery out phone unplugged for almost twenty minutes... and still no luck.
oops, I see I was supposed to put this in the Q and A section, sorry, new here, should I start over there?
Could be a hardware issue with your usb connector. Try cleaning it out with a blast of compressed air or something. I just found out today that the USB ports on the GNex are weak and prone to maybe needing repair.
Good news is that the part only costs $6.00 on ebay - if you're a DIYer.
zuberio said:
Could be a hardware issue with your usb connector. Try cleaning it out with a blast of compressed air or something. I just found out today that the USB ports on the GNex are weak and prone to maybe needing repair.
Good news is that the part only costs $6.00 on ebay - if you're a DIYer.
Click to expand...
Click to collapse
That was it! I blew it out, and then I cleaned a bit with alcohol, and then when that didn't do it I pushed up (or down) on the cable while it was plugged in and suddenly it came to life. I was able to connect to PC and lock it back. Now at least I can attempt a warranty repair if I so decide.
I had gently pushed up and down on the cable before to try to make a good connection but never once did it connect - I feel like the cleaning must have been needed but apparently was not sufficient to fix it fully.. So I suppose something is still amiss with the connector - either it is damaged or askew or else still a bit dirty.
I'm happy to be back to full stock, maybe I'll root again another day after I sort out the USB issue.
Thanks everyone!
In the future, I'd recommend steering clear of "one-click" or "toolkit" root methods. Sure, they work, and gosh darn it they are easy... but when something goes wrong, you'll never know what's actually the problem. Get comfortable working with fastboot and adb; it will take you a long way with this device.
This should help get you started in the right direction.
First of all I read all the possible posts here in the XDA forum about this problem but no one was able to help me :s
I was listening music with my cellphone than it crashed and turned of from nohting. My first thought was "Damm, it crashed!" and I removed the battery and after a couple minutes I put it back and than the cellphone never turned on again. No battery status is showing up, no leds, odin and flash mode doens't work either. I don't no what to do :s
I tried this:
◘ Unplug from USB, remove battery 5 min, put it back
◘ Odin and Flash mode
◘ Turn it on without battery on pc
◘ Turn it on while recharging
My GNexus model is a I9250 GSM.
Could you add some more details? How long the phone's been in operation, refurbished?, rooted?, your current ROM, kernel, radios, advanced kernel settings such as voltage changes, any tweaks, battery type, temperature.
This exactly happened to me on my DroidX. I spent 2 weeks trying everything to revive it including taking the phone apart before adding it to the pile and getting my current GNexus Toro.. so I know how much this sucks. I'm not an expert on phones bricking but I know that connections can go bad or come loose, especially if the phone has been dropped or other impact, components start to lose their integrity over time and voltage shorts 'burn out' op-amps. You mentioned listening to music, so I'm wandering about the IVA components burning out, which usually has voltage too high especially on boot... Hope you can get it working.
7175 said:
Could you add some more details? How long the phone's been in operation, refurbished?, rooted?, your current ROM, kernel, radios, advanced kernel settings such as voltage changes, any tweaks, battery type, temperature.
This exactly happened to me on my DroidX. I spent 2 weeks trying everything to revive it including taking the phone apart before adding it to the pile and getting my current GNexus Toro.. so I know how much this sucks. I'm not an expert on phones bricking but I know that connections can go bad or come loose, especially if the phone has been dropped or other impact, components start to lose their integrity over time and voltage shorts 'burn out' op-amps. You mentioned listening to music, so I'm wandering about the IVA components burning out, which usually has voltage too high especially on boot... Hope you can get it working.
Click to expand...
Click to collapse
Well first of all I thank you for your concern and my phone is on again, thanks to my uncle. The phone is '4 months old', I rooted last month, bootloader unlocked and I was using samsung stock rom (4.2.1 JB). Yeah, that really suck monkey b*lls. If you got the same problem as me (I really hope not) that's what you should do: First remove the battery, plug the charger and than put the battery back. In my case, It kind "shorted" the battery and my phone is back on. I was reading posts and posts and discovered that GNexus has this problem and a lot. Dunno when it can happen again but I really don't want a paperweight. Once again, thank you!
Glad you got your Nexus back up and runnning. Thanks for posting back with details after you figured out the problem and got your phone working, +1 right there. There's always a good chance this will help out someone later on. :good:
Confirmation: balums worked for me
balums uncle's solution worked for me: specifically, (1) removed USB power, (2) removed battery, (3) applied USB power, (4) inserted battery, (5) press power button.
Thanks balums!
Does anybody have technical (design/EE) insight into what would cause this?
This was starting from a device that appeared totally dead.
The battery was *fully charged* (and showed up that way immediately when the device finally booted).
I had done the obvious things of removing/inserting the battery, cleaning contacts, checking the USB power connection.
Was about to pull it apart when I saw balums post, saving me huge time.
Device is about 16 months old. Stock OS and settings. First time this has happened.
Search terms:
CDMA (Verizon) Samsung Galaxy Nexus -- SCH-i515.
Phone won't boot. Device won't turn on. Won't start. Dead. No worky.
Thanks,
Seth
Awesome! You trick worked, balums!
Interestingly I also have the standard stock version of OS and Hardware which I bought 14 Months ago (nearly to the day). I was surfing over WiFi yesterday evening and when I turned the phone off I noticed the screen getting grey for a moment, not black. And this morning the Nexus just didn't turn on.
Anyway, thanks for the solution, have a nice day!
That is very odd because my i515 also did the exact same thing and I have owned it for 15 months. I can't wait to get home and try this trick. More to come.
Drew
Thanks!
balums said:
Well first of all I thank you for your concern and my phone is on again, thanks to my uncle. The phone is '4 months old', I rooted last month, bootloader unlocked and I was using samsung stock rom (4.2.1 JB). Yeah, that really suck monkey b*lls. If you got the same problem as me (I really hope not) that's what you should do: First remove the battery, plug the charger and than put the battery back. In my case, It kind "shorted" the battery and my phone is back on. I was reading posts and posts and discovered that GNexus has this problem and a lot. Dunno when it can happen again but I really don't want a paperweight. Once again, thank you!
Click to expand...
Click to collapse
Hey Balums,
My GNex didn't turn on this morning and I was really confused as to why it would do such a thing, until I saw your post. Thanks a lot for posting your uncle's remedy!
It fixed mine!
-Fupa
bookmarked. thanks op.
Galaxy nexus wont turn on or charge.
I tried (1) removed USB power, (2) removed battery, (3) applied USB power, (4) inserted battery, (5) press power button but my galaxy nexus still dont turn on. i have 4.2.2 stock rooted. i was downloading something and my screen become weird in colors and i cent use the phone. i turn it of and now wont turn on again or charge.
after unlocking and rooting i installed this touch recovery from google play. [ROOT]Recovery Tools
Excellent! balums' suggestion helped me. I thought I had tried this before but apparently didn't quite get this in the right sequence.
The only remaining issue I have now is that when it does turn on, I've got the thunderbolt on the battery indicator, the phone says it's charging at the lock screen, but when I go to Battery under Settings it says that the battery is discharging. This effectively has my phone in a state where I can't unplug it (battery is too low but it also doesn't appear to actually "charge"). I tried replacing the Micro USB charge port PCB board and came up with the same results. To me, this seems like a problem and may indicate a motherboard or battery connection issue. I used the "Battery Monitor Widget" and it indicated that it was getting AC power. Any thoughts?
Thanks to XDA and Balum's suggestion! I thought my phone just died! It was on 70somethign % battery last I looked, connected by USB to the PC and I don't know if I turned it off and walked away for a while or if it turned off by itself, but it would not turn on no matter what I did after I got back to my desk. It is on Android 4.3 takju stock not rooted.
Thank you all again for the instructions on how to revive the GNex!
Samsung Galaxy Nexus won't power up
I got a Samsung Galaxy Nexus. I got it from my cousin and therefore don't have any information about the rooting status as well as the ROM but i guess it was running stock. The phone won't turn ON, it is not detected in the computer. No LED or any other indication. I tried the above method which worked for many people but it failed. What is special about the phone is that the upper part of the screen is heating up more as compared to the rest of the phone. Can somebody help me fix this? Is this a hardware issue?
I have the EXACT same problem as you do. I have no idea where to start to try to fix it. I took a picture, then lines went squiggly across the screen, then it flickered, and died. I cannot power it on at all. I tried Uncle's tricks. No luck.
Anyone have some ideas on what to try? Thanks.
majidkhan said:
I got a Samsung Galaxy Nexus. I got it from my cousin and therefore don't have any information about the rooting status as well as the ROM but i guess it was running stock. The phone won't turn ON, it is not detected in the computer. No LED or any other indication. I tried the above method which worked for many people but it failed. What is special about the phone is that the upper part of the screen is heating up more as compared to the rest of the phone. Can somebody help me fix this? Is this a hardware issue?
Click to expand...
Click to collapse
Also having the same problem. My Nexus has been rebooting randomly for the past week or so, and finally, this morning, it refuses to turn on at all.
It's a Verizon Galaxy Nexus running stock, but it's been rooted. I'm using the extended battery. The trick that was posted earlier in this thread doesn't seem to work for me. I've tried multiple USB cables and power sources.
I'm going to try the standard battery when I get home, but I'm not expecting positive results.
Work-around
About two months ago whenever I turned my Gnex off, it became totally unresponsive to all attempts to start again. After a lot of trial and error, I discovered that if I pulled the battery for 30-60 minutes and reinstalled, it would power on normally. I have completely wiped and rooted the phone and the problem persisted.
Today I thought about it some and realized there may be some residual charge in the phone, and my waiting period is to allow the charge to drain. To test this theory, I powered the phone down and then tried to restart - nada. Pulled and reset the battery - nada. Pulled the battery, shorted out all four pins that would make contact with the battery, reinstalled battery, and it powered right up. I have not been able to successfully repeat a fast restart when shorting out all four pins. Pulling the battery and waiting 30-60 mins still works.
Incidently about the same time, my screen has stopped auto rotating (and yes it is set to do so).
mwjoerin said:
About two months ago whenever I turned my Gnex off, it became totally unresponsive to all attempts to start again. After a lot of trial and error, I discovered that if I pulled the battery for 30-60 minutes and reinstalled, it would power on normally. I have completely wiped and rooted the phone and the problem persisted.
Today I thought about it some and realized there may be some residual charge in the phone, and my waiting period is to allow the charge to drain. To test this theory, I powered the phone down and then tried to restart - nada. Pulled and reset the battery - nada. Pulled the battery, shorted out all four pins that would make contact with the battery, reinstalled battery, and it powered right up. I have not been able to successfully repeat a fast restart when shorting out all four pins. Pulling the battery and waiting 30-60 mins still works.
Incidentally about the same time, my screen has stopped auto rotating (and yes it is set to do so).
Click to expand...
Click to collapse
What are you doing exactly to short out the battery?
galaxy nexus reboot
my galaxy nexus is about 1 year old now and this is the first time that i've encountered a problem with it. It suddenly restarted, and will take about 5-7minutes before it opens, it will be open up to the "X" logo and when it reaches the normal screen it will restart again. I don't know whats wrong with it. please help/
sethbruder said:
balums uncle's solution worked for me: specifically, (1) removed USB power, (2) removed battery, (3) applied USB power, (4) inserted battery, (5) press power button.
Thanks balums!
Does anybody have technical (design/EE) insight into what would cause this?
This was starting from a device that appeared totally dead.
The battery was *fully charged* (and showed up that way immediately when the device finally booted).
I had done the obvious things of removing/inserting the battery, cleaning contacts, checking the USB power connection.
Was about to pull it apart when I saw balums post, saving me huge time.
Device is about 16 months old. Stock OS and settings. First time this has happened.
Search terms:
CDMA (Verizon) Samsung Galaxy Nexus -- SCH-i515.
Phone won't boot. Device won't turn on. Won't start. Dead. No worky.
Thanks,
Seth
Click to expand...
Click to collapse
Thanks alot... this worked for me !!
You saved my Galaxy Nexus
Similar problem + water
Ok, so I have a similar situation I believe. My phone took a swim. I left it off and riced it. Later on after I believed it to be dry enough, i turned it on. (wow it freaking worked) After a few seconds of using the device checking screen the phone snapped off and went into a reboot. I waited until it came back and i shut it down and thought I'd let it go over night. I plugged it in and let it charge (charge icon was displaying). Everything looked good.
Fast forward. Morning time. I go to turn the phone on. Nothing.
This time the phone won't boot. Instead all i see is the white battery icon show up indicating the battery is 100%. When i plug it in to the charger i get the battery with the charging bolt, then it shows the normal battery indicator light. After that, I get nothing.
I tried the method I saw above. remove power, remove battery, apply usb power, insert battery, press power. Sadly it didn't work.
Anyone have any other ideas as to what might be going on?
So short backstory, I've been loading and troubleshooting custom ROM issues on my phone for 4+ years. I'm by no means a developer but I can read word-for-word, research and follow instructions. I was given this 'bricked' Kindle Fire by a friend who knew enough to try and reset but didn't want to bother crawling through XDA to sort it out (he came across it through an acquaintance and the past history of the device is unknowable). So I figured I'd charge her up and poke around -
1. I don't have the cable the device came (or any wall unit charger) but have been using a generic micro-USB and from what I've gathered, this shouldn't be an issue. I've used it with all my other Android devices without issue...
2. While the power button's LED does light up amber while attached to my PC (back panel USB, of course) it never seems to actually charge. I've let it run all the way down to where it wouldn't boot at all, then connected to my computer overnight and the next morning it still flashes low battery. Oddly, while the amber light stays lit while plugged in, when I press the power button it somewhat randomly will actually give me the low-battery notification. Maybe 1/3 times I press it. With the device unplugged, if I press the power button, it will turn on just long enough to give me the low-battery message...but it will do this every time I press the button. Not randomly like when it is plugged in. Sorry if some of this info is extraneous but I'm also trying to sort out whether there is some type of circuitry damage....
3. The device NEVER is recognized by my PC in any way, shape or form. I've installed the KFU drivers, rebooted, disconnected, reset Kindle, uninstalled and reinstalled KFU drivers....every combination under the sun. No beeps, blips or changes in my device manager. This is obviously the biggest bummer and at first I figured I could order a fastboot cable and eventually sort it...but with all the other weird charging issues....maybe this thing is just FUBAR.
EDIT: I completely forgot to add some pertinent information - after sitting on the charger for a half an hour or so...the device will automatically boot to the 'kindlefire' logo screen and then reboot 5 or 6 times in a row flashing between the low-battery message and boot logo...where it eventually stays and still isn't recognized by my computer. I typically will try and reset it after a while...in which it then turns goes back to the normal power button lit up with amber. It then takes another 30 or so minutes and then it will randomly reboot to the logo screen again boot loop all over again. Makes zero sense.
I'd be more than happy to give more information and troubleshoot any other ideas to get this thing going, but I just wanted to illicit opinion before spending money on the cable.
I can tell you right off the bat you need a kindle (or comparable) charger. USB does not cut it. Kindle Fire has big charging requirements. Start with that and you might have better luck!
Sent from my GT-p511x
sharonbw said:
I can tell you right off the bat you need a kindle (or comparable) charger. USB does not cut it. Kindle Fire has big charging requirements. Start with that and you might have better luck!
Sent from my GT-p511x
Click to expand...
Click to collapse
Thanks...I had read that before and then read varying other information to the contrary. Instead of spending money just buying a Kindle Fire stock cable...I'm assuming I might as well spend the extra couple of bucks for a fastboot cable?
EDIT: It's late, I now realize you mean I need to buy the wall charging unit first, correct? I have a wall charger for my Samsung Galaxy S III, would that potentially work?
Ordered appropriate charger...I knew the PC and phone wall charger were underpowered but I never bothered to look up the respective specs until now...they are quite a bit underpowered.
Will check back in once received. Thanks again...
jaxwithanx said:
Ordered appropriate charger...I knew the PC and phone wall charger were underpowered but I never bothered to look up the respective specs until now...they are quite a bit underpowered.
Will check back in once received. Thanks again...
Click to expand...
Click to collapse
Unsintall any drivers you have for the kindle in Device Manger. Than run the driver in the KFU folder. If it takes 2 seconds to install you didn't uninstall it. It takes more than a minute to install the driver. Once it is installed than use the unbrick utility
mattmejia said:
Unsintall any drivers you have for the kindle in Device Manger. Than run the driver in the KFU folder. If it takes 2 seconds to install you didn't uninstall it. It takes more than a minute to install the driver. Once it is installed than use the unbrick utility
Click to expand...
Click to collapse
I mentioned above that my PC does not recognize the Kindle when it is plugged in, so I can't uninstall any drivers from the Device Manager. This is also not my only issue....did you read the entire post?
jaxwithanx said:
I mentioned above that my PC does not recognize the Kindle when it is plugged in, so I can't uninstall any drivers from the Device Manager. This is also not my only issue....did you read the entire post?
Click to expand...
Click to collapse
He meant your windows device manager. The kindle drivers are temperamental. Once you have fully charged device and properly installed drivers, you might find that your situation has changed.
Sent from my GT-p511x
sharonbw said:
He meant your windows device manager. The kindle drivers are temperamental. Once you have fully charged device and properly installed drivers, you might find that your situation has changed.
Sent from my GT-p511x
Click to expand...
Click to collapse
Yeah I knew he was talking about Windows Device Manager, that's why I mentioned that as of right now, there is nothing to uninstall from the Device Manager because the PC isn't recognizing anything. But yes, after the device fully charges, with any luck, I'll at least pull something up in the DM and then I will make sure to uninstall and reinstall before poking around.
Well, same problem remained. Charged on wall for 6+ hours with appropriate charger but the light remained lit amber and frozen at 'kindlefire' bootscreen.
Hard reset it and it now just flashes the low battery message to me briefly before powering the screen off again (remains 'charging' if on charger or just turns back off if not on charger). I figured that this wasn't my issue due to the fact my computer wasn't recognizing the Kindle in any state, even when stuck on boot logo. It's not just that it doesn't assign the right drivers....it never notices anything plugged in at all. Restarted, hard booted again, restarted with the Kindle connect stuck on boot screen and every combination in between.
No clue...any help appreciated...
Any thoughts at all here??
Been plugged in for over 12 hours...still amber light. Sometimes frozen on 'kindlefire' boot logo screen...other times just off entirely....alternates.
I'm wondering if you have a bad usb port - a common kindle defect. Sounds like you might build up enough charge for the device to attempt to boot then it goes dead again until a little more juice trickles in. This is total conjecture because I think typically it just comes off the board and quits working completely. You might want to search about replacement.
Sent from my GT-p511x
sharonbw said:
I'm wondering if you have a bad usb port - a common kindle defect. Sounds like you might build up enough charge for the device to attempt to boot then it goes dead again until a little more juice trickles in. This is total conjecture because I think typically it just comes off the board and quits working completely. You might want to search about replacement.
Sent from my GT-p511x
Click to expand...
Click to collapse
Yeah, I got this for free so I'm not going to bother paying for a replacement. Just an auxiliary device.
I cracked it open yesterday to take a look at that very issue but didn't have a small enough screwdriver with me at the time to take the board off to look. I've soldered things here and there.
I don't necessarily hold out much hope that is the issue because the charging light stays lit and never seems to falter no matter if I wiggle or move around. But who knows, I've seen weirder things...I just find it interesting that I get no response at all from my computer even when it's stuck on the boot logo. Typically with most devices, that seems to be far enough for it to be sending something out at that point. Maybe it is stopping just short of that moment though....who knows...