If you let the phone battery run down, it will not, I repeat WILL NOT boot back up out of recovery.
When I plug the charger in it just boot it right back into recovery, which we all know won't charge the battery.
Pull the battery, put battery back in, plug in the charger....boot right back into recovery.
Power off from recovery with charger still plugged in...boot right back up in recovery.
Reboot system from recovery...boot right back up in recovery.
No way to charge the battery without getting out of recovery first.
No way to boot out of recovery without enough juice in the battery.
I had to use the extended battery (spare) to boot up the phone and...well you guest it...to flash the "other" recovery to get it working normal again.
Thunderbolt
Miui
TWRP 2.3.1.0
Works fine on earlier version, if this is a false alarm, then please delete.
Update: After reading through a few forums, TWRP might be able to charge while in recovery. It doesn't work for me.
That's a +1 for 4ext. It let's you charge the battery in recovery.
Sent from my Thunderbolt using Tapatalk 2
Your phone should charge in the powered off state though.
Thought so too but I know for a fact that cwm boots you into recovery as soon as there is enough juice to boot. Then having the screen on starting what little there is left. I know because I dealt with that for a month before I realized that my stock battery finally took a drive and wasn't retaining a full charge anymore.
Sent from my SCH-I535 using xda app-developers app
Its recovery 101 never mess with recovery unless you have a decent charge. You are just asking for trouble. I agree it makes 4ext look better because you can charge while in its recovery. If you let your phone die in recovery then you deserve it. Not to sound harsh but for the longest time when devs post roms they said make sure your battery is charged before flashing the rom. You think they was joking? lol
I remember having to do that with the Droid Eris.
Sent from my Thunderbolt using Tapatalk 2
I think what he means is, if you let your phone die normally, then plug it in to charge, it will boot to recovery. I had that happen to me when i first tried clockwork touch.
Sent from my Liquid ICS Bolt
Let me clear it up a bit.
If there's not enough juice in the battery to boot up the phone. If you push and hold the power button and nothing happen then you're screwed.
As soon as you plug in the charger, it will boot right to TWRP. you can not stop it from booting into TWRP, when you power it off from within TWRP it will boot right back into TWRP as long as the charger is connected.
Bottom Line:
If your battery went dead (under normal usage condition) and you don't have a good spare. You are SCREWED. This is a FATAL bug.
There's no way to charge a dead battery.
DarkJedi thinks that I'm in TWRP while the phone went dead. The answer is NO. The battery went dead under standby.
Dark Jedi said:
Its recovery 101 never mess with recovery unless you have a decent charge. You are just asking for trouble. I agree it makes 4ext look better because you can charge while in its recovery. If you let your phone die in recovery then you deserve it. Not to sound harsh but for the longest time when devs post roms they said make sure your battery is charged before flashing the rom. You think they was joking? lol
Click to expand...
Click to collapse
You're not understanding the post. This has nothing to do with messing with TWRP. Battery went dead under normal using condition, has nothing to do with recovery.
Shadow Death said:
Your phone should charge in the powered off state though.
Click to expand...
Click to collapse
That's the problem, it will not power down out of TWRP, as soon as you plug in the charger it will boot right back into TWRP.
It has the same cwm bug there used to be. When you plug the phone in to charge it boots into recovery.
Sent from my Thunderbolt using Tapatalk 2
That's good to know, I had been using TWRP on my Thunderbolt so I guess it's time to switch back to 4ext, i just wish there was software keyboard support in 4ext.
Also with a note, I had this problem the op had when using TWRP on my Asus Transformer, actually strangely, while the recovery was installed it would not charge the device at all, not even when turned off. Once TWRP was taken off of it, and CWM back on, it charged properly. After using TWRP I can say for some reason this recovery has some serious game changing bugs.
EDIT: Also, "Boot Manager" doesn't seem to be compatible with restoring backups made with TWRP.
Give this build a shot and see if it fixes the charging:
http://techerrata.com/dees_troy/mecha.img
Ellises said:
That's good to know, I had been using TWRP on my Thunderbolt so I guess it's time to switch back to 4ext, i just wish there was software keyboard support in 4ext.
Also with a note, I had this problem the op had when using TWRP on my Asus Transformer, actually strangely, while the recovery was installed it would not charge the device at all, not even when turned off. Once TWRP was taken off of it, and CWM back on, it charged properly. After using TWRP I can say for some reason this recovery has some serious game changing bugs.
EDIT: Also, "Boot Manager" doesn't seem to be compatible with restoring backups made with TWRP.
Click to expand...
Click to collapse
No idea what your trouble with the Transformer were but charging on the Transformer isn't done in recovery and changing recovery wasn't the fix.
The Thunderbolt & most all HTC devices made after it use recovery for charging. There's a handful of HTC binaries & a special init.rc that make the device charge while turned off. None of this is part of the recovery code so it's not inherent to TWRP itself.
Dees_Troy said:
Give this build a shot and see if it fixes the charging:
http://techerrata.com/dees_troy/mecha.img
Click to expand...
Click to collapse
my port is busted so i cant test charging but the build does work
Another tester confirmed that it was fixed in that version, so I have updated everything.
Related
I rooted using z4root & installed recovery using Koush's Droid 2 bootstrap with hopes of trying out Liberty before Fission.
Everything seemed to be going well, I backed up, wiped data/cache, flashed Liberty, and booted into it. No signal or leds, so I decided to go with Fission.
So I installed the Droid 2 Bootstrap app in Liberty in order to reboot into recovery, wiped data/cache, and flashed Fission. But when I went to reboot, I still had the Liberty splash screen. So somehow I figured out how to boot back into clockwork, I think I booted into stock recovery by holding X, (maybe wiped data/cache in there), and then hit reboot from there. But this hasn't gotten me to clockwork subsequently.
This time, I tried wiping all the mounts (boot/system/data/cache) as well as fact.reset/cache before flashing Fission.
Still, I get the Liberty splash.
Now, I think my battery won't charge.
Is there any way to restore my backup without a new battery? Even if i do get a new one, how am I going to boot into clockwork to restore my backup?
Word is once you've gone Liberty, way out is first SBF then anything else. Make sure you don't play with the phone too much as battery will die and you cannot SBF.
Like I said, my battery is already dead.
Is there no way to SBF without a charged battery? Can't I just plug it into the wall?
hijklll said:
Like I said, my battery is already dead.
Is there no way to SBF without a charged battery? Can't I just plug it into the wall?
Click to expand...
Click to collapse
There is. But is a bit scary. You can jump the battery via the USB port using usb cable to provide power for the flashing. Few people have done it, it works. But you better buy a 10 bucks desktop charger for Motorola BP6X batteries and recharge the battery. If you aren't tech savvy I do not recommend you to try the USB power jump start method...
Sent from my DROID2 GLOBAL
leobg said:
But you better buy a 10 bucks desktop charger for Motorola BP6X batteries and recharge the battery.
Click to expand...
Click to collapse
That's what I've done. Now I'm just waiting for it to charge.
Now the question is will I be able to get into Clockwork Recovery, or will I have to RSD/SBF?
Depends on what the issue was exactly that was keeping you out of clockwork. In my experance, if I yanked the battery while it was still on the moto logo, when I booted back it would boot directly into clockwork. However, if you've already whiped all mounts, your only option may be to sbf anyway.
I had the same problem with the battery. What worked for me was to plug the phone in via USB while holding x to boot into the recovery. I let it sit and charge slowly for about an hour or so. After that I was able to boot without my battery losing charge.
If this does not work I suggest buying any usb wall charger / car charger and charging your phone with that.
Good luck.
blakzer0 said:
I had the same problem with the battery. What worked for me was to plug the phone in via USB while holding x to boot into the recovery. I let it sit and charge slowly for about an hour or so. After that I was able to boot without my battery losing charge.
If this does not work I suggest buying any usb wall charger / car charger and charging your phone with that.
Good luck.
Click to expand...
Click to collapse
Dang, should have tried that before I bought a battery charger. Oh well.
Since we know that the last recovery can't charge when phone is off, i'm a little bit affraid.
I love to use Rom Manager but... if my phone is fully discharged, i can't boot and it's the end for my phone? o_o
Bluewall said:
Since we know that the last recovery can't charge when phone is off, i'm a little bit affraid.
I love to use Rom Manager but... if my phone is fully discharged, i can't boot and it's the end for my phone? o_o
Click to expand...
Click to collapse
Hi,
You can download CWM 4.0.1.4 from here:
http://www.multiupload.com/UCJYHKQH23
Bluewall said:
Since we know that the last recovery can't charge when phone is off, i'm a little bit affraid.
I love to use Rom Manager but... if my phone is fully discharged, i can't boot and it's the end for my phone? o_o
Click to expand...
Click to collapse
Some people have had success reviving their phone using various methods, take a look at the link here:
http://forum.xda-developers.com/showthread.php?t=1193315
Try flashing the recovery provided in the post above me, and then run this ADB command:
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status
You should get battery status (charging or discharging)
If it is discharging, flash other recoveries, including the original AlphaRevX one and the CWM one, and seeing what output you get with the above command.
If none of the recoveries show they are charging after issuing the above ADB command, then either you can be very careful not to let the battery drain, or let the battery drain and risk it and see if the solutions provided in the above thread work, or finally you can flash the stock recovery everytime you don't need the custom recovery (but this can be a pain)
Do this:
DL the .4 referenced version of CWM and then turn off your phone with a semi charged battery. Connect the charger and leave it for an hour. Turn back on your phone and see if the battery has been charging. If it doesnt charge it, OR if you find that you cannot start the phone back up without a battery pull first, then DL the .5 version of CWM.
I found that .4 didnt work correctly for me. While it DID charge the battery, it failed to light the LED AND wouldnt start up without a battery pull. I switched to the .5 version and found everything to work correctly.
It seems that its going to be ONLY one or the other for each person. No one knows why, but this is your best bet.
Matt
I'm stuck in a boot loop and I have no idea why, and I've tried wiping cache, wiping data/factory reset, and re-flashing the CM7 rom. Nothing worked. What happned was, my phone died, so I plugged it in, and it went into "charging mode". The phone will boot, but the touchscreen doesnt work, and non of the radios turn on, so that it can just charge I guess? anyway, the phone got to about 20% battery so I decided to reboot it so I could actually use it while charging, but when I did, it started boot looping. I tried everything mentioned above and its still boot looping. Is there anything else I can try?
let phone go all the way dead
I run Cyanogemod with Da_G's kernel and I let the device die. I had a similar lock up when I finally plugged the charger back in. After it got to about 8 or 9% is all and was still unresponsive, couldn't unlock the screen I simply pulled the battery AND REMOVED THE CHARGE CORD and counted to twenty, slapped it back in and held the power button for the count of ten and let go. It booted back up fine and no issues since.
I assumed you tried a battery pull?
fukenbiker said:
I run Cyanogemod with Da_G's kernel and I let the device die. I had a similar lock up when I finally plugged the charger back in. After it got to about 8 or 9% is all and was still unresponsive, couldn't unlock the screen I simply pulled the battery AND REMOVED THE CHARGE CORD and counted to twenty, slapped it back in and held the power button for the count of ten and let go. It booted back up fine and no issues since.
I assumed you tried a battery pull?
Click to expand...
Click to collapse
Yea, that non responsive state is what led me to reboot. It only does that when the phone is dead and you plug it in. I assume it's because with cm7 there is no way to charge while the phone is off, at least that's the way it was with my infuse and captivate. So that's not the issue. It's that when I rebooted to get out of that state, it gets to the cm7 boot logo and then reboots. It's never done that before, and I do that a lot. I searched for this issue and I found someone with a nexus on cm7 that had a boot loop, and it was solved by some cwm zip that deleted the partitions, then once you do that, if you flash cm7, all will be well, but I don't know if that's applicable to this situation.
EDIT: I tried the battery pull, I left it out for 20 min and it's still boot looping
How are you getting into recovery? Seems once you get into recovery and wipe data/factory reset and flash version 4 and flash the kernel it would fix boot loop.
I use three button method to get to clockworkmod recovery.
If you Odin back to stock the method to get download mode for me was volume down only when plugging in.
I have a 400mb+ size file used by recovery of a working image of my favorite setup to flash back to. Everyone should take a few minutes and boot into recovery and make a backup to flash to once you get up and running good.
Sent from my SGH-I727 using CyanogenMod
I tried to duplicate. You are so correct I put the battery back in after making sure the phone was off and then plugged in the power.
For brief moment the big battery symbol appeared, but rather than continuing to stay with that and charge, it blinked away and promptly booted up into that frozen screen and no radio signal.
I had 50% charge when I tested this just now.
Upon pressing the power button I got the shutdown menu, but the screen was still unresponsive and wouldn't let me select reboot.
Ended up doing another battery pull (with no power cord of course)
I don't see how you did it, reboot while in that state escapes me.
Sent from my SGH-I727 using CyanogenMod
fukenbiker said:
I tried to duplicate. You are so correct I put the battery back in after making sure the phone was off and then plugged in the power.
For brief moment the big battery symbol appeared, but rather than continuing to stay with that and charge, it blinked away and promptly booted up into that frozen screen and no radio signal.
I had 50% charge when I tested this just now.
Upon pressing the power button I got the shutdown menu, but the screen was still unresponsive and wouldn't let me select reboot.
Ended up doing another battery pull (with no power cord of course)
I don't see how you did it, reboot while in that state escapes me.
Sent from my SGH-I727 using CyanogenMod
Click to expand...
Click to collapse
I hold the power button until the phone reboots.
fukenbiker said:
How are you getting into recovery? Seems once you get into recovery and wipe data/factory reset and flash version 4 and flash the kernel it would fix boot loop.
I use three button method to get to clockworkmod recovery.
If you Odin back to stock the method to get download mode for me was volume down only when plugging in.
I have a 400mb+ size file used by recovery of a working image of my favorite setup to flash back to. Everyone should take a few minutes and boot into recovery and make a backup to flash to once you get up and running good.
Sent from my SGH-I727 using CyanogenMod
Click to expand...
Click to collapse
I use the three button combo to get into recovery, and I did wipe data then flash both version 4 and the kernel, and it still loops. I am so confused as to how in the world this happened... anyway, I tried to go back to stock using odin twice and it just got stuck at system.img.ext4.
Oh dear you must take this to the Odin thread.... You belong there until you flash back to stock. Did you try only holding volume down when plugging in to download mode? Your skyrocket is powered down when you try?
Sent from my SGH-I727 using xda premium
I got into download mode fine the first time. then when it got stuck, I changed to a usb port on the back of my pc, but it still got stuck. now it just boots right into download mode.
I don't know what changed.. but since going back to stock wouldn't work, I decided to re flash cwm and try to install cm7 again, and I'm now back up and running just fine. This whole situation was very odd... Thank you for being helpful.
Odin3-v1.85.zip is what you have set up on your computer?
Glad you fixed it.
Sent from my SGH-I727 using CyanogenMod
I think it was on low battery...
what do i do?
iArtisan said:
I think it was on low battery...
what do i do?
Click to expand...
Click to collapse
Try turning it on without the battery in, while it's plugged in to the charger (obviously), if it won't turn on at all, try to flash the stock 2.3.3 via nvflash using this thread
http://forum.xda-developers.com/showthread.php?t=1248644&highlight=nvflash
If that doesn't work try flashing cwm recovery via nvflash using this thread
http://forum.xda-developers.com/showthread.php?t=1056847&highlight=nvflash
Good luck! Hope this helps
well first off shame on you for trying to flash a rom with a low battery that was prob not the smartest thing to do second if you have removed your battery and charged your phone and it still wont boot or anything well then you have a bricked phone sorry
jj_z1 said:
Try turning it on without the battery in, while it's plugged in to the charger (obviously), if it won't turn on at all, try to flash the stock 2.3.3 via nvflash using this thread
http://forum.xda-developers.com/showthread.php?t=1248644&highlight=nvflash
If that doesn't work try flashing cwm recovery via nvflash using this thread
http://forum.xda-developers.com/showthread.php?t=1056847&highlight=nvflash
Good luck! Hope this helps
Click to expand...
Click to collapse
Thanks a lot man, it doesn't turn on at all without the battery in. I was using clockwork recovery to flash the ROM. What do you suggest I do from here?
If you can't get into recovery, then you did probably brick your phone, so you'll need to follow the instructions from the first link i posted earlier to flash the stock GB. Then follow the second to flash cwm using the second link, then flash your rom again
iArtisan said:
Thanks a lot man, it doesn't turn on at all without the battery in. I was using clockwork recovery to flash the ROM. What do you suggest I do from here?
Click to expand...
Click to collapse
If your battery got TOO low, since there's no auto-shutoff while in recovery, it could be too low to take a charge or even allow the device to turn on.
Try turning on the device with a different, fully charged battery. If that works then your battery fried.... at which point it may still be salvagable.. you'd need to hot-swap the battery. that is, turn the device on plugged in and with a GOOD battery... once it's on, then without unplugging, pull out the good battery and QUICKLY insert the bad battery, which will allow it to start charging...
Now, this of course would involve you booting into RECOVERY since you don't have a working ROM, but that would still apply.
lotherius said:
If your battery got TOO low, since there's no auto-shutoff while in recovery, it could be too low to take a charge or even allow the device to turn on.
Try turning on the device with a different, fully charged battery. If that works then your battery fried.... at which point it may still be salvagable.. you'd need to hot-swap the battery. that is, turn the device on plugged in and with a GOOD battery... once it's on, then without unplugging, pull out the good battery and QUICKLY insert the bad battery, which will allow it to start charging...
Now, this of course would involve you booting into RECOVERY since you don't have a working ROM, but that would still apply.
Click to expand...
Click to collapse
jj_z1 said:
If you can't get into recovery, then you did probably brick your phone, so you'll need to follow the instructions from the first link i posted earlier to flash the stock GB. Then follow the second to flash cwm using the second link, then flash your rom again
Click to expand...
Click to collapse
Thank you both, got it working again. Whew.
Someone won't be flashing with anything below 50% battery from now on
Love this community.
​Atrix 2 will not charge it is stuck in recovery (Blue CWM) it has atrix 2 bootsrap installed and RAZR-CWMOnBoot-Global-J.Y.Daddy.zip file installed need help asap tried cmd line prompt to reboot phone but cpu wont recognize device also i left it on charger overnight and still nothing i will probably get another battery soon but i still need to know how to fix this if i run another battery to 0% thanks in advance dev team :crying:
Did you try to take the battery out of the phone? When you do it will boot into CWM Recovery.
thats the only thing it will boot into it wont go past CWM no matter what i do
dscott973 said:
thats the only thing it will boot into it wont go past CWM no matter what i do
Click to expand...
Click to collapse
When you try "reboot now", what happens?
Charge phone for awhile and FXZ back to stock. The phone will charge if you turn it off and plug into wall charger.
Sent from my SAMSUNG-SGH-I997 using xda premium
And if you have CWM on boot installed you need to either delete the bootstrap apk, or deny it su rights in super user. It's either one or the other, not both.
Sent from my MB865 using xda premium
pull the battery, then put it back after a few seconds and hold both volume buttons while turning it on. choose normal powerup and see if that will boot it. you can also try bp tools.
TheZeroDay said:
When you try "reboot now", what happens?
Click to expand...
Click to collapse
You have CWM on boot installed so this is what it's going to do every time you reboot.
You have to select "reboot now" to get it to boot up normally after getting to CWM.
Have you selected " reboot now" and what were the results?
I have seen people even having this type of trouble on other phones as well, If you are unable to charge your battery Get a battery only charger from ebay using which you will be able to charge your battery then use FXZ you will be fine
link for charger
http://www.ebay.com/itm/Battery-Cha...259246?pt=PDA_Accessories&hash=item4cff64042e
Maybe you should but a ROM in your SD card, get the SD card out put in another phone or MicroSD card adaptor, put a ROM in it and flash it, it should fix the issue. It's not the best idea but it should work.
JRW 28 said:
You have CWM on boot installed so this is what it's going to do every time you reboot.
You have to select "reboot now" to get it to boot up normally after getting to CWM.
Have you selected " reboot now" and what were the results?
Click to expand...
Click to collapse
Sounds as though he's just not familiar with CWM and its functions. I don't see how CWM can just hang there unless the user isn't selecting any of its functions to run...
Apex_Strider said:
Sounds as though he's just not familiar with CWM and its functions. I don't see how CWM can just hang there unless the user isn't selecting any of its functions to run...
Click to expand...
Click to collapse
Actually, if there is an issue with the boot image, it may NOT go past CWM, becuase it can't even check the boot partition if it is corrupted, so it will not even attempt it. I think there was link a few posts up that explained something similar.
I saw this a WHOLE lot with my inspire 4g, where the boot partition became corrupted on reboot, and CWM would not even attempt to boot.
I think tmease1 was right an fxz restore is the best fix at this point, just hope that the boot partition is not so borked that even that does not fail.
jimbridgman said:
Actually, if there is an issue with the boot image, it may NOT go past CWM, becuase it can't even check the boot partition if it is corrupted, so it will not even attempt it. I think there was link a few posts up that explained something similar.
I saw this a WHOLE lot with my inspire 4g, where the boot partition became corrupted on reboot, and CWM would not even attempt to boot.
I think tmease1 was right an fxz restore is the best fix at this point, just hope that the boot partition is not so borked that even that does not fail.
Click to expand...
Click to collapse
Ah, yes... indeed, if his boot image or system image is borked it WOULD NOT boot passed CWM in that case. Hard to diagnose the issue if we don't know what else has been done. Won't RSDlite flash the boot image in the unfortunate chance that his boot image is fudged?
Apex_Strider said:
Ah, yes... indeed, if his boot image or system image is borked it WOULD NOT boot passed CWM in that case. Hard to diagnose the issue if we don't know what else has been done. Won't RSDlite flash the boot image in the unfortunate chance that his boot image is fudged?
Click to expand...
Click to collapse
Yeah, but if I remember correctly, I think I saw a few users who still had issues restoring with RSDlite and even with the moto-fastboot commands, if the boot partition was deleted or so corrupted that it could not overwrite it. Now I have not done a search but just going off of what I remember, so I could be incorrect here though.
I fixed it I saw a post on another forum (forgot which one to anxious to try it) but it would only charge while connected to a computer led was white while charging unlike when connected to a wall charger (no led) it decided to reboot itself as I'd I selected reboot now from CWM I am thankful for all of you guys input. And I'm still gonna get a extended battery so this doesn't happen when I'm away for long periods of times...by the way the standard battery last about two days of moderate usage but can I use an extended battery designed for the Droid Bionic I figured I could but I'm not sure could it hurt?
Sent from my MB865 using xda premium
dscott973 said:
I fixed it I saw a post on another forum (forgot which one to anxious to try it) but it would only charge while connected to a computer led was white while charging unlike when connected to a wall charger (no led) it decided to reboot itself as I'd I selected reboot now from CWM I am thankful for all of you guys input. And I'm still gonna get a extended battery so this doesn't happen when I'm away for long periods of times...by the way the standard battery last about two days of moderate usage but can I use an extended battery designed for the Droid Bionic I figured I could but I'm not sure could it hurt?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
if it fits and i the same voltage, it should be fine from a hardware standpoint, not sure what the phone will think of it though, I don't know if it does any kind of check.
Oh and every time I was turning it off and connecting to wall charger it would auto boot back to CWM then I would try to "reboot now" and it would fail and I did that continuously for a few hours sorta a manual boot loop lol glad I fixed it though even though it wasn't too broke
Sent from my MB865 using xda premium
dscott973 said:
Oh and every time I was turning it off and connecting to wall charger it would auto boot back to CWM then I would try to "reboot now" and it would fail and I did that continuously for a few hours sorta a manual boot loop lol glad I fixed it though even though it wasn't too broke
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yeah, Moto is finicky about having the battery somewhat charged, and will not usually let you fully boot without it in, I think I read in some document on the Motorola forum that it had to do with the bootloader, and it was a "safeguard".
Good to see you're back up and running