I just wanted to recap my experience for the benefit of others. I am running the latest rum runner ROM with CWM 5.0.x.x. I have not updated my CWM yet because I do not have an external sd card right now, and don't want to upgrade until I do, since 5.5.x.x mounts external sd, not internal.
So yesterday I let my phone completely die before I got home for the night. I plugged it in, and it booted straight into recovery as soon as I booted. If I chose reboot option in recovery, it would just reboot back into recovery again. If I unplugged my phone and chose reboot option, it would just shut the phone off. Plug charger back in, and phone would turn itself on and back into recovery. After letting it sit on the charger in recovery (which does not show a charging light btw) for about 30 minutes, it was still doing the same thing. After about another 30 minutes on the charger, I tried it one more time before I was going to start thinking of other options. I guess it built up enough of a charge to boot without being plugged in, and since it was not plugged in, it booted normally.
I just wanted to share my experience in case this happens to anyone else. Just leave the phone on the charger sitting in recovery mode. Even though there is not light on, the phone is still charging.
I'm glad someone posted this. The very samething happened to me and I was freaking out too. I knew the phone wasn't bricked bc it would always boot back into recovery but it just wouldn't boot into the rom. I too left on the charger for about an hour until it finally booted back up. I'm not running a custom rom but I am rooted.
That is an issue with the 5.5 rec. It's causing devices which are off and plugged in to boot to rec.
Just let it charge for a few minutes to make sure it has some juice, then pull the battery and unplug it. Then turn it on, wait ten seconds to get past the initial bootup, and then plug back in. Also I think you can avoid it all by using fastboot in settings/power.
Sent from my HTC PH39100 using xda premium
I guess it is an issue in the 5.0 recovery too. I guess the best thing to do is to just shut your phone off once it hits a couple of percent
I am also using CWM 5.0. I haven't upgraded to 5.5 yet.
I upgraded using ROM manger and let my phones battery die and now it will not charge. So now that my battery will not charge my phone will not turn back on. I have tried every thing I can think of and nothing is working. Anyone have any ideas?
Sent from my ADR6425LVW using XDA App
Neodous said:
I upgraded using ROM manger and let my phones battery die and now it will not charge. So now that my battery will not charge my phone will not turn back on. I have tried every thing I can think of and nothing is working. Anyone have any ideas?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Did you read what the OP had posted??
Sent from my HTC PH39100 using xda premium
I did read that but I was not getting into recovery. But now I did get the phone to boot into hboot. Tired to flash the old cwr but it tells me that the battery is to low and it fails. So do you know if the phone will charge in hboot?
Sent from my ADR6425LVW using XDA App
I seem to have fixed the issue by using adb and booting into hboot and letting the phone charge enough to turn it on. After which I reflashed the 1st CWR that I had on the phone and now everything seem to be just fine.
Related
I let my Nook die yesterday, unintentionally, and now I can't get it to charge back up. The second I plug it in, it goes to the "battery too low to power on, try again in 15minutes" screen and just sits there. Its been nearly an hour on an AC wall charger. I can't power it off because it automatically turns on when plugged in, so then it goes straight to that screen. When its plugged in and I power it off, it comes right back on and to that screen also.
Any tips? I'm just going to let it sit on the charger and hope for the best. Otherwise it seems like I'm kinda screwed?
Sent from my HTC Glacier using XDA App
Damn no one else has had this problem?
I made a bootable recovery SD card and managed to get into clockwork, I let it sit on the charger for 20mins, took out the SD and rebooted it and still goes to the 'battery too low' screen. Idk what else to try, I've done every possible way I can think of and I guess I'm declaring it 'semi-bricked'.
No one know a trick way thru ADB I can bypass that screen?
I suppose ill be returning this sometime today
Sent from my HTC Glacier using XDA App
civicvx94 said:
Damn no one else has had this problem?
I made a bootable recovery SD card and managed to get into clockwork, I let it sit on the charger for 20mins, took out the SD and rebooted it and still goes to the 'battery too low' screen. Idk what else to try, I've done every possible way I can think of and I guess I'm declaring it 'semi-bricked'.
No one know a trick way thru ADB I can bypass that screen?
I suppose ill be returning this sometime today
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
You let it sit on the charger for twenty minutes did you? Patient much?
Are you using the Nook Charger cable AND charger? If not, 20 minutes wouldn't put enough charge in there to register a change at all.
Leave it on the charger for a few hours. And for the love of god, don't screw up your NC and take it back and exchange it, it just screws it up for everyone else. You messed it up, fix it.
Today my phone suddenly died on me and refuses to boot up. I came home from work and the phone was working fine. Made a few phone calls, checked a few apps etc. Battery was about 70%.
I left the phone aside and when I picked it up at bed time, it had shut down. Now it doesn't boot at all. I thought maybe the battery had suddenly died down and put it to charge but it isn't turning on at all. Can't even get to the LG logo. Anyone have any clue what to do?
I thought I was one of the lucky few to get a handset which didn't reboot
Edit: Thought I should mention that I was running stock ROM, rooted, with CWM recovery installed
Can you bring up recovery mode? Did you try NVFlash?
Sent from my LG-P990 using XDA App
Remove and replace the battery first and then try charging trough your usb cable and pc. Let it charge for a few minutes and try to boot.
Sent from my LG-P990 using XDA Premium App
mparack said:
Today my phone suddenly died on me and refuses to boot up. I came home from work and the phone was working fine. Made a few phone calls, checked a few apps etc. Battery was about 70%.
I left the phone aside and when I picked it up at bed time, it had shut down. Now it doesn't boot at all. I thought maybe the battery had suddenly died down and put it to charge but it isn't turning on at all. Can't even get to the LG logo. Anyone have any clue what to do?
I thought I was one of the lucky few to get a handset which didn't reboot
Edit: Thought I should mention that I was running stock ROM, rooted, with CWM recovery installed
Click to expand...
Click to collapse
had the same problem.
nvflash fixed it, once the problem was solved I kept getting reboots 20x a day so I nvflashed again and flashed CM7 and havent had a reboot/ BSOD since. I also thought I was one of the lucky ones that didn't reboot at first btw
Thanks guys. Wouldn't power up at all in normal or recovery so couldn't nvflash it. Tried usb, charging etc etc.
However after countless battery pulls just started up again and working perfectly since. I've powered up my trusty htc magic as a backup meanwhile. No idea what went wrong at all.
Sent from my LG-P990 using XDA App
by recovery you ment CWM or Upgrade mode? (that is remove battery, hold volume down button and plug in usb while holding it)
mikee2185 said:
by recovery you ment CWM or Upgrade mode? (that is remove battery, hold volume down button and plug in usb while holding it)
Click to expand...
Click to collapse
Not tried upgrade mode just the volume+power. Maybe something to keep in mind for next time.
ok, i just wanted to make sure that upgrade mode works even if the phone is completely ****ed up
I frequently receive a notification pop up indicating something like, "that the device power consumption currently exceeds the supply. Please plug in."
I take care to exit unused applications, etc, but this still occurs. In fact, I have tried rebooting to ensure nothing is left running in the background. Oddly, it occurs EVEN WHEN PLUGGED INTO THE CAR OR USB outlet... Most often this occurs when I'm using the device for navigation, so GPS, and DATA will be on. The notice has also popped up during other applications. It has happened when using LTE but also when LTE is disabled.
Is this something that everyone is experiencing? If you are, can you please post your Service provider, your SPECS, any mods, or if you have made any progress in stopping it. Lets see if we can track this down.
Mad Medik said:
I frequently receive a notification pop up indicating something like, "that the device power consumption currently exceeds the supply. Please plug in."
Click to expand...
Click to collapse
That's strange. I've never seen a message like that. It doesn't sound like something native to Android / Sense, do you have any battery monitoring / power control apps installed that could be giving this message? How long does your phone last on a charge if you don't plug it in?
I've seen that error before. I wasn't using the USB cable and charger that came with my phone and that cable was damaged in the USB socket. Have you tried other plugs?
Sent from my HTC Raider X710e using XDA App
The reason you are probably seeing that on car or USB charger is due to then not proving the right amount of power. If you have the screen brightness set high and using navigation it uses quite a bit of power. Most USB and car chargers usually only provide I believe a half amp where as most phones like a charger that users 1 amp.
Sent from my GT-I9000 using xda premium
Ive had that happen once when I was playing a really graphics intense game. I was over at a friends house and had it plugged into his computer to charge and was showing him how much better a game looked on my phone than his and it did that. I was using the 3 usb ports on the front of his tower, and he also had his phone and a headset plugged in that front hub as well, and since that hub is powered by one connection on the motherboard I just figured the 3 devices (mainly the 2 phones) were just drawing too much power at the time.
I have had it happen when I was playing a graphics intensive game while plugged into USB on my computer, but never when plugged into AC or car charger.
Thanks for the replies. Good to know it is not just my device.
Unfortunately, my problem has compounded. While I was using it last night, plugged into a USB in the car, it drained enough to shut itself down. I let it sit for a bit and tried to boot it up again. It quickly shut off again. I plugged it into the HTC wall charger over night. When I got up in the morning, it still wouldnt turn on. I tried pulling the battery, replacing it and plugging in again. The LED lights up orange for about 4 seconds, goes off and stays off. It wont turn on.
I left it plugged in for the day while I was out, and nothing. It still won't power up. I notice the battery is cold, further indicating to me that the issue is that it is not being charged at all (rather than a charged battery in a dead device).
I have tried two different USB cables and tried both the wall adapter as well as the computer USB port. Nada... Unfortunately I don't know anyone with a Holiday, so I think I will have to go to the store tomorrow and see if someone will be kind enough to charge my battery in a store phone for an hour or something...
Anyhow, once I get it running again, I want to avoid this in future. I currently have it Network unlocked, and Bootloader unlocked. I have installed CWM Recovery 5.5.0.4, and Rumrunner Beta 11. There was talk that a version of CWM Recovery was not allowing the device to charge while it was off. I am thinking that this is perhaps the culprit in my case. Although I thought that was for 5.0.2.7 (or something similar)?
Any input would be appreciated.
I would find someone with a vivid and try on it, maybe the battery is dead.
Sent from my HTC Vivid via Tapatalk
Mad Medik said:
Thanks for the replies. Good to know it is not just my device.
Unfortunately, my problem has compounded. While I was using it last night, plugged into a USB in the car, it drained enough to shut itself down. I let it sit for a bit and tried to boot it up again. It quickly shut off again. I plugged it into the HTC wall charger over night. When I got up in the morning, it still wouldnt turn on. I tried pulling the battery, replacing it and plugging in again. The LED lights up orange for about 4 seconds, goes off and stays off. It wont turn on.
I left it plugged in for the day while I was out, and nothing. It still won't power up. I notice the battery is cold, further indicating to me that the issue is that it is not being charged at all (rather than a charged battery in a dead device).
I have tried two different USB cables and tried both the wall adapter as well as the computer USB port. Nada... Unfortunately I don't know anyone with a Holiday, so I think I will have to go to the store tomorrow and see if someone will be kind enough to charge my battery in a store phone for an hour or something...
Anyhow, once I get it running again, I want to avoid this in future. I currently have it Network unlocked, and Bootloader unlocked. I have installed CWM Recovery 5.5.0.4, and Rumrunner Beta 11. There was talk that a version of CWM Recovery was not allowing the device to charge while it was off. I am thinking that this is perhaps the culprit in my case. Although I thought that was for 5.0.2.7 (or something similar)?
Any input would be appreciated.
Click to expand...
Click to collapse
Make sure you have beta2 of the recovery which resolves this issue, I too have the Bell Raider and have yet to see this error. I'm running stock with bloat removed and rooted with beta2 recovery. Just go in the recovery if you do not see beta2 written in the CWM header you don't have the latest.
rquiett said:
Most USB and car chargers usually only provide I believe a half amp where as most phones like a charger that users 1 amp.
Click to expand...
Click to collapse
It looks like this is bang on. Apparantly computer USB ports for USB 1, 1.1 are minimum 200 mA with 500 mA recommended. Not sure about USB 2.0. Interestingly there is a proposal for USB 3.0 to allow for 20 Amps or more so you could easily power a laptop and other devices through a USB connection.
The HTC Holiday draws something more than 500 mA and presumably a max of 1 Amp as this is what the included HTC wall charger is rated for.
Anyhow, I guess I will have to pick up a new car charger, because the USB port in my car only pushes 500 mA max, and same for my current car charger.
I noticed that when I would remove and reinsert the battery with the device plugged in, the orange light would illuminate for about 4 or 5 seconds, then go off. In the hopes that this meant that the battery was charging for that brief period, I repeatedly removed and reinserted the battery for about 10 minutes this morning, trying the power button each time. It finally booted up. I turned the screen off and left it alone to charge. A few hours later I checked on it and it is up to about 1/3. Anyhow, putting that out there as a last resort if anyone else has a similar problem.
jebise101 said:
Make sure you have beta2 of the recovery which resolves this issue, I too have the Bell Raider and have yet to see this error. I'm running stock with bloat removed and rooted with beta2 recovery. Just go in the recovery if you do not see beta2 written in the CWM header you don't have the latest.
Click to expand...
Click to collapse
Thanks. After I let the battery charge right up, I will check that. (I don't want to tempt trouble by rebooting until I have finished a charge). I thought I had the latest version but maybe I borked something in the update.
jebise or other Bell Raider users: Were you able to use the ph39IMG method of flashing? I have had no success with it; I got an error that it was for the wrong type of device. I deleted the zip and used the next method listed in the superguide. However, now I get a series of errors relating to not finding ph39IMG when I boot into HBoot.
Thanks
Mad Medik said:
I noticed that when I would remove and reinsert the battery with the device plugged in, the orange light would illuminate for about 4 or 5 seconds, then go off. In the hopes that this meant that the battery was charging for that brief period, I repeatedly removed and reinserted the battery for about 10 minutes this morning, trying the power button each time. It finally booted up. I turned the screen off and left it alone to charge. A few hours later I checked on it and it is up to about 1/3. Anyhow, putting that out there as a last resort if anyone else has a similar problem.
Thanks. After I let the battery charge right up, I will check that. (I don't want to tempt trouble by rebooting until I have finished a charge). I thought I had the latest version but maybe I borked something in the update.
jebise or other Bell Raider users: Were you able to use the ph39IMG method of flashing? I have had no success with it; I got an error that it was for the wrong type of device. I deleted the zip and used the next method listed in the superguide. However, now I get a series of errors relating to not finding ph39IMG when I boot into HBoot.
Thanks
Click to expand...
Click to collapse
if you use the fastboot method to flash the recovery, you dont need the PH39IMG. the 'error' messages you see when you boot into HBOOT is normal. every time you boot into HBOOT it looks for the PH39IMG.zip on your sdcard
PH39IMG.zip did not work for me had to use fastboot. As PG states its normal to get those errors, because it looking for PH39IMG.zip and can't find it.
Pirateghost said:
if you use the fastboot method to flash the recovery, you dont need the PH39IMG. the 'error' messages you see when you boot into HBOOT is normal. every time you boot into HBOOT it looks for the PH39IMG.zip on your sdcard
Click to expand...
Click to collapse
jebise101 said:
PH39IMG.zip did not work for me had to use fastboot. As PG states its normal to get those errors, because it looking for PH39IMG.zip and can't find it.
Click to expand...
Click to collapse
Thanks for clarification on the "normal" errors I should expect. Im not a total noob, but feel like it, switching to HTC. I understand I can use the fastboot method and have done so. But do I have to? The PH39IMG.ZIP would be much more user friendly. So, why would I be getting an Invalid Device error with the PH39IMG.zip from the superguide post? Is it specific to the AT&T Vivid or something?
Anyhow, after all the problems I was having, I decided to wipe/factory reset and restore from a Backup made in CWM recovery right after installing Rumraider for the first time. I am just waiting for the device to reboot (has been on the HTC boot screen for about 10 minutes now... :-/
Mad Medik said:
Thanks for clarification on the "normal" errors I should expect. Im not a total noob, but feel like it, switching to HTC. I understand I can use the fastboot method and have done so. But do I have to? The PH39IMG.ZIP would be much more user friendly. So, why would I be getting an Invalid Device error with the PH39IMG.zip from the superguide post? Is it specific to the AT&T Vivid or something?
Anyhow, after all the problems I was having, I decided to wipe/factory reset and restore from a Backup made in CWM recovery right after installing Rumraider for the first time. I am just waiting for the device to reboot (has been on the HTC boot screen for about 10 minutes now... :-/
Click to expand...
Click to collapse
once you have done your recovery you dont need to do it again until you update the recovery with a newer version. its a one time thing, unless you relock stock RUU the device.
the ph39img.zip was configured for at&t vivid. you would probably need to modify it for any other holiday device.
if you are restoring from a backup, did you make sure and flash your boot.img from your backup first? otherwise you will be stuck at that HTC screen for a lot longer....just boot into HBOOT and flash the stock boot.img
So I've been running HoliRaider v1 and it's been working beautifully however last night my phone died, and when it dies it boots into recovery. This is usually fine however the phone will not charge in recovery but instantly boots into it if i plug it in. Basically, it's stuck there because it only charges (as shown by the orange light indicator) for a second before entering recovery. Then, it just stays there. I'm not sure if I should even restore at this point, as that wouldn't exactly work with 0 battery. If anyone has any idea what to do please let me know.
Looks like you either need to charge the battery using a stock phone from either a friend or go to the att store and see if they will let you charge your battery on their floor unit for a few
Sent from my HTC PH39100 using xda premium
at this point getting the battery charged is priority. this is probably your best bet without having to buy some kind of charger or new battery
ccb101 said:
Looks like you either need to charge the battery using a stock phone from either a friend or go to the att store and see if they will let you charge your battery on their floor unit for a few
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
I had this happen when I first got the phone. Should you eventually get it to boot (I did after taking out the battery, putting it back in, and then trying to turn it on while plugging it in, it took many attempts), let it charge to 100%, then flash thecubed's ClockworkMod which supports chargemode when powered off. You should be fine after that.
you can flash the recovery in fastboot if the phone stays on long enough.
formicae said:
I had this happen when I first got the phone. Should you eventually get it to boot (I did after taking out the battery, putting it back in, and then trying to turn it on while plugging it in, it took many attempts), let it charge to 100%, then flash thecubed's ClockworkMod which supports chargemode when powered off. You should be fine after that.
Click to expand...
Click to collapse
rft3ch said:
you can flash the recovery in fastboot if the phone stays on long enough.
Click to expand...
Click to collapse
Personally I wouldn't flash anything with a battery that may conk-out mid-write.
Now I experiencing a major problem
the phone battery died on me earlier tonight, I tried one time to see if i could of get it on but no juice
Now I get home it's not coming on at all
I have it plugged in one time was able to get to the boot loader screen bow nothing
and when i touch the buttons in front I feel the phone vibrating but nothing comes on not even the charging light
what do you think is the problem?
G
You are using clockworkmod...
Switch to twrp
Sent from my Vivid 4G using Tapatalk 2
rignfool said:
You are using clockworkmod...
Switch to twrp
Sent from my Vivid 4G using Tapatalk 2
Click to expand...
Click to collapse
How do I do that if I can't get it on?
Or will I be able to still accedd the bootloader if I plug it up to the PC to flash it?
G
positiveg said:
How do I do that if I can't get it on?
Or will I be able to still accedd the bootloader if I plug it up to the PC to flash it?
G
Click to expand...
Click to collapse
Nope - you'll need to charge it externally, then you need to get new recovery. CWM doesn't support off mode charging, so if your battery dies, you have to charge it out of the phone. Go to ATT store and ask them if they can charge it for you for a while
Just a question what is off mode charging?
Sent from my HTC Raider running Sense 4.1
Ok guys I think I got it.
What I did was
Take out the battery
Put the batter back in
Plug in the charger
When the light come on hold down Vol down and power button
When phone boots to bootlader choose recovery
you will get white HTC creen, leave phone plugged in for a while 30 mins or so
then while leaving charger plugged in attempt to power phone pn
phone should boot regularly
Finally.... don't let phone battery run down or get external charger or change to twrp as one person suggested.
I'm just glad that I was able to get my phone booted, as I live outside the US can't go to an ATT store and HTC phones aren't the most popular here.
I'm wondering if I should order a battery from Amazon just in case :silly: