Basically my issue is, bootloader works, nothing else does, anything that causes a reboot (rebootRUU) will instantly turn off the phone, the phone will obviously not boot into RUU mode.
I did a factory reset while under a custom ROM, it seems that won't boot either, I can flash recoveries, but surprise surprise, they won't boot.
Battery is at about 10%, seems to charge VERY slowly if I manually restart the device with the charge scripts (basically, the issue is anything that turns the device off, whether to boot into recovery or OS, or to simply reboot to bootloader, simply will turn off the device.
How can I fix this issue?
CID: HTC__621
Black 32gb One X, if it at all matters, hboot 0.95
ShadowOfScales said:
Basically my issue is, bootloader works, nothing else does, anything that causes a reboot (rebootRUU) will instantly turn off the phone, the phone will obviously not boot into RUU mode.
I did a factory reset while under a custom ROM, it seems that won't boot either, I can flash recoveries, but surprise surprise, they won't boot.
Battery is at about 10%, seems to charge VERY slowly if I manually restart the device with the charge scripts (basically, the issue is anything that turns the device off, whether to boot into recovery or OS, or to simply reboot to bootloader, simply will turn off the device.
How can I fix this issue?
CID: HTC__621
Black 32gb One X, if it at all matters, hboot 0.95
Click to expand...
Click to collapse
charge the battery, it will continue to just loop and not boot up until it has enough charge.
power it off completely then plug it into a wall charger and leave it for at least 3 hours, more if possible. DO NOT use a pc or laptop to charge, must be wall charger.
Related
I have a one X unlocked international version which I had rooted and set up a recovery. I then went on to try to flash over ARHD after super wiping, and did a battery stat reset since I had flashed at around 30% and figured it would reset the calibration on the battery. Anyways, from here this is where it goes bad. After restarting it goes into a boot loop and ends up getting kicked back into bootloader. After this I try to factory reset to no avail. After trying to reflash the rom a couple times using recovery, recovery just died and won't even load anymore. In addition to this I can't get the battery to hold a charge as each time I plug it in it reboots and loads then says 0 battery and dies instantly. I can get to bootloader and fastboot but can't flash anything through fastboot because it says the battery is too low.
Any suggestions on how to fix this and get it back up and running, or am I forced to send it to HTC the moment they bring in parts for it. (right now HTC says there is a wait on parts as they do not have any in stock as its a new phone and their texas facility has diddly on hand)
Any suggestions are welcome as to fixing this predicament.
phil.W said:
did a battery stat reset since I had flashed at around 30% and figured it would reset the calibration on the battery.
Click to expand...
Click to collapse
How did you wipe batterystats, from CWM? As the recoveries are new I suppose it's possible something went wrong if you did it that way, but it seems unlikely.
However, though probably not the root of your problem, there's no point in wiping batterystats.bin, as all that file holds in information on what processes have been using battery since your last unplugged your charger. This was one of those android myths (I used to do it too ) that was officially put to bed early in the year:
http://www.xda-developers.com/andro...g-battery-stats-does-not-improve-battery-life
In addition to this I can't get the battery to hold a charge as each time I plug it in it reboots and loads then says 0 battery and dies instantly. I can get to bootloader and fastboot but can't flash anything through fastboot because it says the battery is too low.
Click to expand...
Click to collapse
I'm pretty sure I've seen others with this issue, have a search around the forums. Have you tried turning the phone from the bootloader screen, and leaving it plugged in to charge for a while?
Try this:
1. Boot into bootloader
2. Select Fastboot menu
3. Select "Power off" to shut down the phone
5. Plug in charger
Leave it for a while. From what I've read, the power LED may flash at first, but should settle after a few mins to a solid red. I'd leave it till it's green and fully charged then try again.
If that works, and you can get into recovery again, try restoring your backup of the stock ROM if you have one, to check the phone boots okay. (If you didn't take a backup first, you will next time. ) Otherwise try re-flashing the ROM, or if that fails you might have to re-flash stock recovery, re-lock your bootloader and then run the relevant RUU for your device to flash the stock firmware back. You'll have to unlock and root again in that case.
Good luck, hope it works for you!
usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Ra dio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed
good luck to you and your phone. i was afraid of these things too, so before i started to do anything, i saved some roms onto my virtual sd card, just to be sure if i get stuck without a operation OS, i still have some roms on my memory. and before starting with anything, i charged my phone up to 95%.
sorry, i can not help you and i guess you have to wait for a solution.
Hello, I have a big problem.
Suddenly my phone not switch on, only if its on charger.
Its fully charged, and when I unplug from charger, its just simply switches off to black screen. If I try to switch on, the bootscreen comes up for a few seconds, and after its just simply switch off.
=/
I was on SDv9 with Elemental X kernel.
Now I revert to stock Rom with 4.16.401.10 TWRP nandroid - but the result is the same. When the phone is pluged to the charger, I can swich on, and the system itself it works properly by the way.
I tried the " push and hold volume+ and volume- and power button for 2-3 minutes with charger" method, but no success. Also I tried to wipe cash, of course no success.
Only I can go in bootloader, but if I set recovery - I have TWRP the latest - its also switch off. I can use TWRP only with charger.
Only in bootloader it stays on.
It's behave like the battery is completely drained or 0% charged, but its full.
Does anyone experienced the same anomaly? Or idea to solve this?
Thank you in advance.
Now:
Stock Sense 6 Android 5.0.1
4.16.401.10
TWRP latest 2.8.6.0
S-ON
So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.
Lohboh said:
So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.
Click to expand...
Click to collapse
So you can't even get to download mode by holding power+vol down for several seconds?
Tarima said:
So you can't even get to download mode by holding power+vol down for several seconds?
Click to expand...
Click to collapse
No, it just brings up the same issue of it getting stuck on the monochrome HTC logo.
no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?
ffuser1 said:
no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?
Click to expand...
Click to collapse
I've tried that, and I have the latest TWRP.
I know flashing roms are easy. But it might be difficult for newcomers like me. I have always a question in mind what'll happen if my phone shut down due to low battery in fastboot/recovery. If I format the OS before shutdown, is it possible to charge the phone offline without no OS then continue flashing roms?
##Following things happened with me.
I was in MIUI 12.5. I installed Pixel Recovery to flash PE12 via adb sideload. Then I cleared all data/cache. When I tried to update the rom by sideload, it didn't work. I wanted to search the internet and as it would take time, I tried to turn the phone off. I couldn't even shut the phone to save battery. Whenever I pressed power button, instead of shutting down, it always took me to the bootloader menu. Thats when I thought about this question.
that question is so out of the box, i doubt anyone can give you an answer with proof
but yes, i believe it is possible to charge even without OS and no, i dont have any proof to back this up
That's why you need to charge phone first at least until 50% up before flashing any rom.. otherwise if still happen phone shutdown while flashing, yes you still can recover as long your phone bootloader still at unlocked stats also phone still can go into fastboot
If it shuts down when in fastboot/recovery because the battery is empty, you simply charge it and reboot, that should cause no harm. Shutting down while flashing a ROM however is a totally different story. You might get lucky and be able to boot the phone back into fastboot/recovery or you could end up with a paperweight.
jadephyre said:
If it shuts down when in fastboot/recovery because the battery is empty, you simply charge it and reboot, that should cause no harm. Shutting down while flashing a ROM however is a totally different story. You might get lucky and be able to boot the phone back into fastboot/recovery or you could end up with a paperweight.
Click to expand...
Click to collapse
I did shutdown the phone within fastboot to cancel flash all and lock....then booted in forced fastboot end flashed with flash all to not lock the bootloader....and had no prob....! I think those partitions are protected against those scenarios....
Following things happened with me.
I was in MIUI 12.5. I installed Pixel Recovery to flash PE12 via adb sideload. Then I cleared all data/cache. When I tried to update the rom by sideload, it didn't work. I wanted to search the internet and as it would take time, I tried to turn the phone off. I couldn't even shut the phone to save battery. Whenever I pressed power button, instead of shutting down, it always took me to the bootloader menu. Thats when I thought about this question.
Addymore said:
I did shutdown the phone within fastboot to cancel flash all and lock....then booted in forced fastboot end flashed with flash all to not lock the bootloader....and had no prob....! I think those partitions are protected against those scenarios....
Click to expand...
Click to collapse
No. NO NO NO and NO.
You were lucky. This can totally brick your phone. Critical partitions are being modified in the Flashing-process.
There is no protection.
If your phone shuts down during the Flashing-process, your phone can get bricked (black screen) and you can't even boot Fastboot & Recovery anymore. I know this. I have experience.
You must ensure that you have enough Battery (I recommend 75% Battery at least), that the USB connection is stable (will not disconnect randomly), and that your PC won't crash/shut down.
IF IT HAPPENS, that the Flashing-process errors out, DON'T REBOOT THE PHONE. If you do so, you won't be able to enter Fastboot anymore. You must stay in Fastboot. Just reconnect USB, and try again to Flash. Just don't reboot the phone.
Sorry for fear-mongering, but this is definitely dangerous and not to be taken lightly.
dreamytom said:
No. NO NO NO and NO.
You were lucky. This can totally brick your phone. Critical partitions are being modified in the Flashing-process.
There is no protection.
If your phone shuts down during the Flashing-process, your phone can get bricked (black screen) and you can't even boot Fastboot & Recovery anymore. I know this. I have experience.
You must ensure that you have enough Battery (I recommend 75% Battery at least), that the USB connection is stable (will not disconnect randomly), and that your PC won't crash/shut down.
IF IT HAPPENS, that the Flashing-process errors out, DON'T REBOOT THE PHONE. If you do so, you won't be able to enter Fastboot anymore. You must stay in Fastboot. Just reconnect USB, and try again to Flash. Just don't reboot the phone.
Sorry for fear-mongering, but this is definitely dangerous and not to be taken lightly.
Click to expand...
Click to collapse
I think it is because I forced fastboot mode after few seconds of starting flashing....by the way I was avoid the flash and lock option that I selected by error while I wanted flash and clean...
I think, there is no ptoblem, fastboot Mode is Read Only Memory, no one can write/edit this think.
No matter you abort the flashing prosses , or the device loss power from battery, didn't affect the fastboot sector/bios on PC
*IMO