Related
Hey, I rooted, s-off/hbooted my phone and used Clockworkmod to install a ROM.
Now it won't go away no matter what I've tried and I want to be able to turn my phone off and charge it without seeing that annoying recovery screen.
I've backed up all my apps on to SD, wiped data and factory resetted with CWM and the phones built in factory reset yet it still comes back to haunt me.
What do I need to do to make this go away and revert my phone back to it's original out of box state?
CWM should come with an uninstall guide and a notice of how annoying this is, I see it's quite a widespread problem for everyone trying to calibrate the battery with no clear answer
Install the correct HTC RUU for your desire hd.
prank1 said:
Install the correct HTC RUU for your desire hd.
Click to expand...
Click to collapse
Much appreciated, you get my first thanks.
For anyone else in need here's where I got mine (every other ROM and RUU is there too)
http://forum.xda-developers.com/showthread.php?t=868610
Just to be sure, can I just put the RUU on my storage card and use CWM recovery to install it?
Thanks for the.. thanks lol
I don't know but it really doesn't matter, better if you flash it from bootloader. If you were eng hboot s-off then your dhd will become 100% stock (if you installed the correct htc ruu). If you were radio s-off you will still have s-off afterwards. I don't think this affects warrentee issues as long as you have installed the correct rom.
On another note, I am sure I read somewhere some instructions on how to calibrate your battery and fix this problem. But you may have to do a little searching for it.
Sent from my Desire HD using XDA App
even on stock the phone goes into recovery anyway just it don't show the recovery screen. reason it does so i've read is for the led light to come on lol
spookamiester that link just brings you back to this thread so i've placed a link to all HD files and it has all the RUU files there
http://forum.xda-developers.com/showthread.php?t=841207
just check the first two links for ruu files
and a guide here to install ruu's
http://forum.xda-developers.com/showthread.php?t=864054
spookamiester said:
CWM should come with an uninstall guide and a notice of how annoying this is, I see it's quite a widespread problem for everyone trying to calibrate the battery with no clear answer
Click to expand...
Click to collapse
Maybe I am being simple but I see this posted everywhere as a problem, it in no way affects battery calibration, yes when the phone is turned off and plugged in it boots into recovery (it also does this with the stock ROM) so what? It's still charging and from CW you can then wipe the battery stats which is required to complete your calibration anyway.
What exactly is the problem with it booting into CW when turned off and plugged in
and to answer the question, reflash with the appropriate RUU
Or just flash recovery.img from a stock rom
Is the s-off that stops the receiving of OTA's ?
Sent from my Desire HD using XDA App
ghostofcain said:
Maybe I am being simple but I see this posted everywhere as a problem, it in no way affects battery calibration, yes when the phone is turned off and plugged in it boots into recovery (it also does this with the stock ROM) so what? It's still charging and from CW you can then wipe the battery stats which is required to complete your calibration anyway.
What exactly is the problem with it booting into CW when turned off and plugged in
Click to expand...
Click to collapse
First of all I'd like to thank everyone for the responses, should be able to get things sorted now.
In response to the charging in CWM, I tried it for over an hour after full charge on and the LED remained amber, I turned the phone back on and the battery was at 99% which leads me to believe that it doesn't actually charge in CWM recovery, I tried this on stock and within 10 minutes after full charge on I got the green light off. I've asked in other threads if anyone can confirm the phone charge whilst in CWM but so far no confirmation, just similar results.
I'll keep my eyes pealed for answers but I don't think it works with CWM and can't find a way to charge whilst off without CWM recovery popping up.
spookamiester said:
First of all I'd like to thank everyone for the responses, should be able to get things sorted now.
In response to the charging in CWM, I tried it for over an hour after full charge on and the LED remained amber, I turned the phone back on and the battery was at 99% which leads me to believe that it doesn't actually charge in CWM recovery, I tried this on stock and within 10 minutes after full charge on I got the green light off. I've asked in other threads if anyone can confirm the phone charge whilst in CWM but so far no confirmation, just similar results.
I'll keep my eyes pealed for answers but I don't think it works with CWM and can't find a way to charge whilst off without CWM recovery popping up.
Click to expand...
Click to collapse
I have spent quite a while in recovery and I am fairly sure it's charging I wouldnt be surprised that the green led didn't function though? I don't really see how it wouldn't charge surely it a hardware thing when the power is attached?
Update: I use QtADB to give a GUI interface to ADB, have spent the past 15 minutes monitoring the battery state whilst in Clockwork recovery and it is most defintetly charging so you needn't worry about that
I bought the phone from Hong Kong with stock ROM. Rooted, S-Off and installed CWM but never flashed any ROM. But I have same the problem, screen will boot to recovery when I want to charge. I found there are a lot of DHD guys have the same problem here in China or Hong Kong..... and no solution found in any forum here yet. Some said it's a bug on CWM.
Anyway. I found an alternative myself. Instead of using the DHD original charger, I used the I9000 charger to charge the DHD. It worked perfectly (100% charged) and no recovery screen appeared so far......
Hey guys!
I have the original Desire HD stock ROM but I have clockwork mod recovery.
Could you guys provide a step by step guide on how to remove and replace with original recovery image?
I would really appreciate all the help!
xmoo said:
Or just flash recovery.img from a stock rom
Click to expand...
Click to collapse
I have a file recovery.img. How do I flash it to the DHD?
I'd like to know this as well. I have the Clockwork bootloader installed. It's OK, but I changed my mind - I'd like to keep this phone as close as possible to factory-standard and use a different phone for hacking. Is there a step-by-step guide to reverting a DHD back to normal so I can benefit from the regular OTA updates?
Thanks!
Reflashing the ruu is the hard and long way.
Just download the stock recovery.img which west2cool was good enough to post for me. (Cheers again I didn't really feel like installing windoze just for that).
Then use fastboot - "fastboot flash recovery recovery.img"
dr.m0x said:
Then use fastboot - "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
And make sure it is FASTBOOT mode. Flashing fails otherwise (unless I did something stupid).
Sorry, I'm a newb at this.
When I boot by doing vol-down + pwr I get a mainly white screen with three Androids skateboarding at the bottom. At the top it says
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
The top option is "FASTBOOT", so I press pwr once to select that.
Next I see four options:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I do not see an option to reflash a recover image.
If I go into "RECOVERY", I see the green text on a black background of ClockworkMod v2.5.1.3. There is an option to apply an update.zip, however that's clearly not the same thing as I was instructed to do.
Detailed step by step instructions would be much appreciated!
THANKS!
I'm resurrecting my laptop with ubuntu 10.10 x64 right now (so I can build gingerbread) so can't help until later. If someone doesn't beat me to it, I will up a proper set if instructions along with the links you will need once my laptop is fully functional again.
Sent from my performance enhanced Desire HD
Ok buddy, my lappy lives again
1. Download the recovery.zip posted earlier on in the thread.
2. Extract recovery.img from the recovery.zip (best to extract it somewhere easy like a new folder called c:\fastboot)
3. Download fastboot from here. http://developer.htc.com/adp.html#s2
4. Make sure fastboot.exe and recovery.img are in the same directory (e.g. c:\fastboot)
5. Reboot your phone as you did before (while holding vol down + power)
6. Select fastboot and push the power button
7. Plug your phone into your computer - it should change the message to "FASTBOOT USB"
8. Open a terminal (push start button and type in "cmd" to get one if you don't know how).
9. Type "cd c:\fastboot" and press enter.
10. Type "fastboot flash recovery recovery.img"
11. You should see a message which says something like sending ... send complete ... done.
12. To test: Push the power button on your phone once, push volume down once to highlight recovery, push power button. It should boot you to a screen with a red triangle.
13. Push vol up + power button to bring up the stock recovery menu
14. Push power button to reboot
Hopefully thats detailed enough
So I am totally lost. Have exhausted all my knowledge on these issues, but i will take u guys through my process step by step.
Right now my problem is that i am unable to charge my one x in any way. it will only respond to being connected through my pc and obviously that wont charge very well. My phone will boot to the home screen but will go from being 35% charged to 0% and just reboot. what lead up to this was my installing android revolution 1.2.2 along with the interim clockwork mod. Upon reboot is where all the problems began. I accidently forgot to wipe before installing and now this is where im at. Cant boot into recovery. cant load default recovery because battery is too low. nothing except this impossible battery screw up is all i get. and now oncve i unplug my phone from pc, its shuts down after a few moments with no charge. Im at my wits end guys. anyone know what i can do?
These threads may help:
http://forum.xda-developers.com/showthread.php?t=1596155
http://forum.xda-developers.com/showthread.php?t=1599748
chukwu77 said:
So I am totally lost. Have exhausted all my knowledge on these issues, but i will take u guys through my process step by step.
Right now my problem is that i am unable to charge my one x in any way. it will only respond to being connected through my pc and obviously that wont charge very well. My phone will boot to the home screen but will go from being 35% charged to 0% and just reboot. what lead up to this was my installing android revolution 1.2.2 along with the interim clockwork mod. Upon reboot is where all the problems began. I accidently forgot to wipe before installing and now this is where im at. Cant boot into recovery. cant load default recovery because battery is too low. nothing except this impossible battery screw up is all i get. and now oncve i unplug my phone from pc, its shuts down after a few moments with no charge. Im at my wits end guys. anyone know what i can do?
Click to expand...
Click to collapse
I assume you were on 1.19 software? This happened to a friend yesterday. He ended up fastboot erase cache. Fast boot reboot bootloader. Get into recovery and plug up to ac power. The light comes on for a min. Or so then goes off. When it goes off unplugg it then plug it back in. Keep this up till you have some juice. Then fastboot flash the stock recovery relock bootloader, then get ruu 1.26.707. Run that ruu and it should boot. After that you can flash all the roms you want.
Sent from my HTC One X using XDA
Thanks so much, I will try and let u guys know what is going on. FYI i dont see a fastboot erase cache on my screen so how would i go about doing that?
So i locked my oem back before i could boot stock revocery and stock ruu. anyone know how i would ebable to unlock my oem. ADB doesnt appear to re open it with the unlock command. i get a command error message. And yes the bin file from htc is in the fastboot folder. smh
I cant get a charge and the fastboot wont let me unlock oem or load a new recovery.... what now?
cmon guys, i spent 10 hours trying to fix this yesterday, im close to just chucking this thing into the garbage and going back to my nexus. someone please give a little help. i cant charge the phone so i cant load any stock RUU. fastboot is pretty much useless right now. nothing seems to do anything other than show a list of commands when i try to unlock oem again. im desperate so someone please help
chukwu77 said:
cmon guys, i spent 10 hours trying to fix this yesterday, im close to just chucking this thing into the garbage and going back to my nexus. someone please give a little help. i cant charge the phone so i cant load any stock RUU. fastboot is pretty much useless right now. nothing seems to do anything other than show a list of commands when i try to unlock oem again. im desperate so someone please help
Click to expand...
Click to collapse
I don't know what to tell you bro. If you locked the bootloader before putting stock recovery back on the phone. An ruu won't work anyway. Have you tried fastbooting a system.IMG and a boot.IMG. to see if it might boot? If you have your bin file from when you first unlocked. Try sending that again to unlock. Hopefully someone will pop in and give you a hand.
Sent from my HTC One X using XDA
what commands should i use to try to get it back to normal? everything is saying my battery is too low, which really thats what is keeping me from doing anything to help the situation. I need to charge but none of the threads i have read with steps for charging have worked
chukwu77 said:
what commands should i use to try to get it back to normal? everything is saying my battery is too low, which really thats what is keeping me from doing anything to help the situation. I need to charge but none of the threads i have read with steps for charging have worked
Click to expand...
Click to collapse
Did you do a backup after brick?
I have a copy of the main files... (data.img, system.img and boot.img).
i Use this commands:
Examples
Manual Nandroid restore
Make a Nandroid backup, and copy the folder off your SD card to your desktop.
cd ~/Desktop/path/to/backup/
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
MORE INFO HERE.
For the battery... try a charger with little more volts or amperes... you can buy some usb chargers on any electronic store.
thanks i will get on it and let u know what happens. Much appreciated! I did not do a backup after brick but before brick i did. I am using the transformer prime charger its a quad core tablet and it reads as having higher volts/amp than all my others.
your one x stills bricked?
No solution?
Hi all. I hope some kind person here can help me get to the bottom of this.
I unlocked my bootloader earlier from htcdev. I then installed super user.
I wanted to install Leedroid ROM so downloaded the files and used fasboot to install the version of boot.img that comes with it. Problem is that I forgot to transfer over the rom zip file to the device before doing it so now I'm stuck. I know, I just got distracted. My fault I know. I just feel totally sick at the thought of just having bought a £450 to have broken it less than a week later.
(I have successfully rooted my old desire and a wildfire in the past without bother so I do have experience of rooting....just looking like and feeling like an idiot now!)
I had a nandriod backup done from before flashing boot.img and tried to restore.. It says restore was successful but it got stuck on the HTC splash screen. Some help would be mighty appreciated.
The bootloader is now locked again but I think I still have CWM recovery installed however I can't access it any more. The phone boots directly into the bootloader and doesn't attempt to boot.
I've tried unlocking the bootloader again but now it says the battery is too low. I keep trying to turn the phone off in fastboot to let it charge but it just starts up again? Any Ideas?As I said I can't get it to charge so I can't unlock the boot loader again. I've tried running stock 1.29 RUU but again not enough juice.
Just to confirm: My HBOOT is 0.94.0000; The bootloader is relocked.
Any help would be very appreciated, I am at my wits end. Thanks in advance
http://forum.xda-developers.com/showthread.php?t=1546970
Try that. download and extract boot.img and then flash the boot.img that should then work. If not try looking for stock roms that are flashable through clock work mod and get hold of that boot.img. hope this helps
Sent from my HTC One X using XDA Premium HD app
Also if you got cwm you can go into it and charge the phone from there
Sent from my HTC One X using XDA Premium HD app
This is just a thought, maybe when the battery dies the phone will switch off on its own, and then u can charge it.
malcovitch said:
Also if you got cwm you can go into it and charge the phone from there
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for all the replies. Unfortunately, I can no longer access CWM. When I go to recovery it shows the "Quietly Brilliant" Screen then goes to fastboot menu, no CWM?
UPDATE: Ok, I have managed to unlock my bootloader again. In another thread mevorach advised running a batch script that displays the voltage and reboots the phone. Id created this script and waited until the phone charged up enough, then I ran the unlock command again.
I now have access to CWM again. Feels like I'm starting to get somewhere.
mevorach said:
Hi
I have a solution for you
make a batch file :
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
put this file in the directory where you have fastboot.exe adb.exe and all other
files , also put the unlock.bin file that you have from htcdev
put your phone to bootfsatusb , and run the batch file , you will see the voltage
off the battry each time it loop , after an hour or two you will have enough power(~3.68mv) to unlock it , then charge it and do what ever you want
Click to expand...
Click to collapse
cosmicovertones said:
Thanks for all the replies. Unfortunately, I can no longer access CWM. When I go to recovery it shows the "Quietly Brilliant" Screen then goes to fastboot menu, no CWM?
Click to expand...
Click to collapse
That's because of low battery.
have you read this : http://forum.xda-developers.com/showthread.php?t=1609190
which recovery version that you have ? If it is 5.8.3.1, what you can try is:
attach the charger to it's usb.
the phone will boot to bootloader
scroll to power down
it will shut down
don't take out the usb cable/charger from the phone.
if the phone starts again to bootloader
scroll again to power down
(normally it will stay shut down when doing this power down the second time)
let it charge for an hour.
on PC get ready the fastboot command to unlock the bootloader
fastboot flash unlocktoken Unlock_code.bin and enter
status will show waiting for device
connect your phone and power on
and see whether the "low battery" warning still there.
if successful, unlock the phone (choose yes)
when it reboot - hold power + volume down to force it to bootloader
fastboot flash boot boot.img for the nandroid backup that you restore earlier
once done reboot the phone.
---------- Post added at 02:45 PM ---------- Previous post was at 02:43 PM ----------
cosmicovertones said:
UPDATE: Ok, I have managed to unlock my bootloader again. In another thread mevorach advised running a batch script that displays the voltage and reboots the phone. Id created this script and waited until the phone charged up enough, then I ran the unlock command again.
I now have access to CWM again. Feels like I'm starting to get somewhere.
Click to expand...
Click to collapse
that's good.
what you need now is to flash the boot.img for the nandroid backup that you have which you mentioned you restored earlier. without a correct boot.img for your nandroid backup, you will stuck on "quietly brilliant"
Thanks for your reply,
ckpv5 said:
That's because of low battery.
have you read this : http://forum.xda-developers.com/showthread.php?t=1609190
Click to expand...
Click to collapse
Yes, I've gone through all the pages.
ckpv5 said:
which recovery version that you have ? If it is 5.8.3.1, what you can try is:
Click to expand...
Click to collapse
When I managed to get into CWM I realised I was not on the latest, I have now managed to flash 5.8.3.1
ckpv5 said:
attach the charger to it's usb.
the phone will boot to bootloader
scroll to power down
it will shut down
don't take out the usb cable/charger from the phone.
if the phone starts again to bootloader
scroll again to power down
(normally it will stay shut down when doing this power down the second time)
let it charge for an hour.
on PC get ready the fastboot command to unlock the bootloader
fastboot flash unlocktoken Unlock_code.bin and enter
status will show waiting for device
connect your phone and power on
and see whether the "low battery" warning still there.
if successful, unlock the phone (choose yes)
Click to expand...
Click to collapse
I have managed to get to this step.
ckpv5 said:
when it reboot - hold power + volume down to force it to bootloader
fastboot flash boot boot.img for the nandroid backup that you restore earlier
once done reboot the phone.
that's good.
what you need now is to flash the boot.img for the nandroid backup that you have which you mentioned you restored earlier. without a correct boot.img for your nandroid backup, you will stuck on "quietly brilliant"
Click to expand...
Click to collapse
I tried to restore the boot.img that backed up earlier but it is getting stuck at the "quietly brilliant" screen.
I also tried to restore all of the nandroid backup without success.
Any ideas how I can get a working boot.img to flash?
I am currently leaving the phone on the "quietly brilliant" screen (the charge LED is on) to see if I can get enough charge to restore the stock recovery, lock the bootloader and flash the 1.29 europe RUU. Is this a good plan or should I be trying something else?
Based on my experience, when you're not sure which boot.img belongs to which nandroid, a stock boot.img will work.
But if that also fail then the next best thing to do is flash RUU and make sure you have the right official RUU for your phone. Wrong RUU will not work.
Ok, will do. Thanks for the help
I'm trying to leave the phone on charge for a couple of hours, I'll then try flash the boot_signed.img file from the RUU.zip andfailing that I'll try the whole RUU.
Same situation here...
cosmicovertones said:
I'm trying to leave the phone on charge for a couple of hours, I'll then try flash the boot_signed.img file from the RUU.zip andfailing that I'll try the whole RUU.
Click to expand...
Click to collapse
I'm having the exact same problems, and have pretty much done the same steps in my attempts to get the phone back to life. Current status is that it's locked and can't unlock it due to low battery, but that .bat file seems to be helping - battery voltage is going up, so eventually I should be able to do something.
My plan however is to try RUU (tried everything else already, when I had battery and the phone was unlocked and had clockworkmod).
Anyway please keep this thread up to date with your progress.
If you broke your phone in the first week...well, I opened the box of mine 15 minutes before bricking it, hadn't even installed the SIM card (I bought it from an amazon seller and he sent me the Asian version, Thai keyboard and all - that's what started all this).
Ok... so I flashed the boot_signed.img file from the official 1.29 ruu. The phone then rebooted and again froze on the "quietly brilliant" screen. I then locked the bootloader again and rebooted. This time it booted fine
Once booted I left it to charge fully, I then was able to run the 1.29 RUU for my phone.
Next step I unlocked the bootloader again and flashed CWM 5.8.3.1. Performed a nandroid backup and flashed the super user zip file.
It is fully functioning up to this point now.
My next step is to follow ALL the steps (this time lol) to get leedroid one xtreme v5 rom installed again.
I'm getting the phone back to 100% charge before doing the next steps, just incase I need to undo anything I REALLY don't want to run into the low battery issue again.
cfsmp3 said:
I'm having the exact same problems, and have pretty much done the same steps in my attempts to get the phone back to life. Current status is that it's locked and can't unlock it due to low battery, but that .bat file seems to be helping - battery voltage is going up, so eventually I should be able to do something.
My plan however is to try RUU (tried everything else already, when I had battery and the phone was unlocked and had clockworkmod).
Anyway please keep this thread up to date with your progress.
If you broke your phone in the first week...well, I opened the box of mine 15 minutes before bricking it, hadn't even installed the SIM card (I bought it from an amazon seller and he sent me the Asian version, Thai keyboard and all - that's what started all this).
Click to expand...
Click to collapse
As the earlier quote regadring the bat file, you will have enough power(~3.68mv) to unlock it. Once it gets to ~3.689mV you will be able to unlock the phone.
Did you have it unlocked at one point? If so you can use the same unlock file HTC sent you to unlock again.
Once you have it unlocked run the bat script again until the power is around the same level again, then flash cwm 5.8.3.1 through fastboot.
Once you have this you can turn the phone off and plug it into your charger. I had mine plugged in for over an hour. The charge was then enough to flash the boot_signed.img file from the RUU for my phone, and as I said it booted fine.
Hope this all helps, I know exactly how you feel.
My killer mistake was forgetting to transfer the leedroid rom zip to the phone and I wrongly assumed CWM could mount the internal storage as USB to transfer the rom to the phone; like earlier versions.
cosmicovertones said:
Ok... so I flashed the boot_signed.img file from the official 1.29 ruu.
Click to expand...
Click to collapse
Where did you get that file? Digging into %TEMP% or is there an official repository or something?
Why not install the full RUU, by the way, to start over?
Anyway your post gives me hope I'm currently letting the .bat file run - but the plan was to do RUU if at all possible, rather than unlock, add clockworkmod, etc...
I couldn't get it to charge much higher than was required to unlock etc.. so I needed to get CWM installed to get it to charge properly.
Also, I couldnt get the boot_signed.img to flash I assume cause the bootloader is locked.
I got the boot_signed.img by opening the RUU installer but not clicking next just having it open.
Then I got the temp folder on my pc and searched in it for zip files. Only 2 appeared. The rom was called "rom.zip"
I then copied this to my desktop and opened the zip. Then I was able to extract the boot_signed.img file to the fastboot folder on my pc and got it flashed across.
I think you're probably gonna have to unlock the bootloader to fix your problem.
cosmicovertones said:
I couldn't get it to charge much higher than was required to unlock etc.. so I needed to get CWM installed to get it to charge properly.
Click to expand...
Click to collapse
I got some help in IRC on the charge front. Indeed powering off the phone from the FASTBOOT menu *without* having a cable plugged in (otherwise the damn thing won't stay off) puts it in a chargeable state. What I did was plug it in the wall charger for a bit. Then they suggested that when the phone is off you can plug it to the PC and get battery status with adb, which I did - like this:
adb shell cat /sys/class/power_supply/battery/status
adb server is out of date. killing...
* daemon started successfully *
Charging
adb shell cat /sys/class/power_supply/battery/capacity
30
[plugged again to wall charger for a while]
adb shell cat /sys/class/power_supply/battery/capacity
42
So it's looking good. I'll let it charge for a while and once it's done, relock (I just installed cwm again), and try RUU.
cosmicovertones said:
I got the boot_signed.img by opening the RUU installer but not clicking next just having it open.
Then I got the temp folder on my pc and searched in it for zip files. Only 2 appeared. The rom was called "rom.zip"
Click to expand...
Click to collapse
OK, I just did and saved the file somewhere in case it's needed.
We'll see
for the RUU to run successfully you need to flash the stock recovery (to get rid of CWM) and lock the bootloader AFTER you've flashed the boot_signed.img file. This is to get the RUU to run on an unmodified phone.
Once you get that run you can re unlock, flash CWM and super user binaries if you want.
After this experience, I'll be checking and double checking the steps provided in future. What an ass I am!!! ha just goes to prove just cause I was successful on my old htc desire and the gf's wildfire it's no guarantee I know what I'm doing
Also, I've now successfully installed Leedroid One Xtremem V5.1. Just after restoring my apps using titanium backup.
Let me know how you get on
EDIT: I think the reason I had to flash the boot_signed.img file is because I flashed the leedroid boot.img then realised my mistake of not having the rom to flash and to compound the issue relocked the bootloader and the low battery. You might be able to get away with charging and running your RUU. If that fails I would restore stock recovery, lock the bootloader and retry the RUU
cosmicovertones said:
for the RUU to run successfully you need to flash the stock recovery
Click to expand...
Click to collapse
Nope It just needs to be locked, but it was happy to run with cwm installed.
So I got it to work (back to square one, because I still need to change the ROM). I actually did more stuff than needed (because I was trying two approaches as the same time), but in summary:
- That glorious 5 line .bat file works, and allows the battery to charge, so reach a state where you can at least lock/unlock and flash. For me the battery changes from 'low charge' to 'good' at 3615mV.
- You can also turn the phone off from the service menu, but you have to be sure no cable is plugged, or it will turn itself back on in a couple seconds.
- The battery charges if the phone is off, using a wall charger.
- With the phone off, you can still plug in on a PC and find battery status (whether it's charging or not) and current charge (in %) with adb (another command line tool, like fastboot).
- With 30% or more of load, you can run RUU and get the phone back to factory state.
- You can't use a RUU for a different model, if your model is from Asia you need the Asian RUU, you can't just install a European one. You don't like a Vietnamise keyboard? Tough ****.
Anyway, since I know have all the tools and more confidence I'll just go ahead and try again. Starting will a full charge of course
Awesome!! I'm glad you got it to work, and I hope this thread serves as some help for others.
The damn battery charge issue had me worried. That bat file is really a lifesaver!
Thanks for all the info. Hope not to need it but mistakes can be made.
Ok so here's what i did.
I rooted the phone, installed the CWM Recovery and everything.
Next I installed the Android Revolution HD Rom 7.1.0 by doing the "Super Wipe".
It got into boot loops
Then after factory resetting and every other things I could do I tried to do the new RUU on my O2 HTC One X Unlocked.
For that you have to Re-Lock it (which I did)
And I cant go into any of the Fastboot settings etc too because its battery level is very low.
Please someone help me. I just bought this phone
WasifSal said:
Ok so here's what i did.
I rooted the phone, installed the CWM Recovery and everything.
Next I installed the Android Revolution HD Rom 7.1.0 by doing the "Super Wipe".
It got into boot loops
Then after factory resetting and every other things I could do I tried to do the new RUU on my O2 HTC One X Unlocked.
For that you have to Re-Lock it (which I did)
And I cant go into any of the Fastboot settings etc too because its battery level is very low.
Please someone help me. I just bought this phone
Click to expand...
Click to collapse
go into fastboot, flash the new recovery, boot into recovery, and let it charge. then do watever u want
Sent from my HTC One X using Tapatalk 2
Kevin Ma said:
go into fastboot, flash the new recovery, boot into recovery, and let it charge. then do watever u want
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I Re-Locked the phone
Will that flash the Recovery?
WasifSal said:
I Re-Locked the phone
Will that flash the Recovery?
Click to expand...
Click to collapse
unlock the phone again. flash the latest recovery. then go into fastboot. fastboot erase cache , then flash the kernel, go into recovery flash superwipe, flash rom and reboot and job done..
before you do all that though backup your current rom
I cannot go into the fastboot and do the stuff because it prompts me that I have less battery. There's another problem that the phone doesn't shut off. When it gets out of juice then it turns black, the notification light blinks then when its charging, it loads the Bootloader. It simply just doesn't turn off and that leads to the problem that it uses up the battery much more than the required :/
I've tried powering down from the menu but no use
WasifSal said:
I cannot go into the fastboot and do the stuff because it prompts me that I have less battery. There's another problem that the phone doesn't shut off. When it gets out of juice then it turns black, the notification light blinks then when its charging, it loads the Bootloader. It simply just doesn't turn off and that leads to the problem that it uses up the battery much more than the required :/
I've tried powering down from the menu but no use
Click to expand...
Click to collapse
well then leave it overnight to charge..see what happens in the morning then
Goku80 said:
well then leave it overnight to charge..see what happens in the morning then
Click to expand...
Click to collapse
You see the problem isn't that simple :'(
the phone in the end gets totally low on battery cuz its being gulped faster (cuz the screen is lit and can't turn off)
WasifSal said:
You see the problem isn't that simple :'(
the phone in the end gets totally low on battery cuz its being gulped faster (cuz the screen is lit and can't turn off)
Click to expand...
Click to collapse
man i am sorry then i wish i had more knowledge to give you help. hopefully someone else with more experience and knowledge can come and advise you different. just never had that issue you see.
if you say you can not go into bootloader or recovery then it does not sound right...maybe take it back to retailer or something might be the best option if no one can help out
have you tried the power button with the volume button down for ten seconds to see if the phone reboots?
Can anyone tell me the solution to this "keep turning on" habit. If that's resolved there's nothing to it then. Please help me out here :'(
WasifSal said:
Can anyone tell me the solution to this "keep turning on" habit. If that's resolved there's nothing to it then. Please help me out here :'(
Click to expand...
Click to collapse
try what i said to you in my last sentence mate
Have a look here:
http://forum.xda-developers.com/showthread.php?t=1609190
PatsFan1286 said:
Have a look here:
http://forum.xda-developers.com/showthread.php?t=1609190
Click to expand...
Click to collapse
OK so I managed to get the phone UNLOCKED (Finally)
Now when I flash the 5.8.4.0 recovery it says
"unknown partition 'recovery-clockwork-touch-5.8.4.0-endeavoru.img'
error: cannot determine image filename for 'recovery-clockwork-touch-5.8.4.0-end
eavoru.img'"
So i booted the phone into the recovery mode instead of flashing.
I am finally getting somewhere but how do i know it's charging there? I don't see the red LED turn ON :/
LATEST UPDATE:
So when I unlocked the bootloader again. Apparently that solved the "not turning off" habit of the phone.
I went into the bootloader and Power Down my phone, Now it's on charge (waiting for it to turn green)
And I have the O2 branded HTC One X. I also updated it to the 1.29.206.XX something.. I don't remember :/
And I only see one RUU for the O2 branded Phone and that is like 1.26.XXX.XX thing... Will that cause problems since I upgraded the firmware??
WasifSal said:
LATEST UPDATE:
So when I unlocked the bootloader again. Apparently that solved the "not turning off" habit of the phone.
I went into the bootloader and Power Down my phone, Now it's on charge (waiting for it to turn green)
And I have the O2 branded HTC One X. I also updated it to the 1.29.206.XX something.. I don't remember :/
And I only see one RUU for the O2 branded Phone and that is like 1.26.XXX.XX thing... Will that cause problems since I upgraded the firmware??
Click to expand...
Click to collapse
Why is it so hard for guys to flash roms. Man its getting old seeing 50,000 of the same threads over and over.
Ok on to helping
You have latest recovery. So boot to fastboot & flash the roms boot.IMG ( fastboot flash boot boot.img) now unplug the phone, press the power button. Now your back in hboot select recovery,once there click mounts & storage button , mount USB drive. Now copy the Rom to your phone. Unmount USB drive, now flash super wipe script. BUT DON'T REBOOT AFTER YOU FLASH THIS!!!!!! choose option to select another zip to flash. This time flash your Rom & reboot. Now your done. Simple huh. & to answer your ruu ?, you can't downgrade ruu's if your on 1.29, your stuck with it till a newer one comes out.
Sent from my HTC One X using xda premium
rayford85 said:
Why is it so hard for guys to flash roms. Man its getting old seeing 50,000 of the same threads over and over.
Ok on to helping
You have latest recovery. So boot to fastboot & flash the roms boot.IMG ( fastboot flash boot boot.img) now unplug the phone, press the power button. Now your back in hboot select recovery,once there click mounts & storage button , mount USB drive. Now copy the Rom to your phone. Unmount USB drive, now flash super wipe script. BUT DON'T REBOOT AFTER YOU FLASH THIS!!!!!! choose option to select another zip to flash. This time flash your Rom & reboot. Now your done. Simple huh. & to answer your ruu ?, you can't downgrade ruu's if your on 1.29, your stuck with it till a newer one comes out.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Woah! That's spot on... I was surely gonna mess up my phone if i had done the RUU.
Its charging while the screen is off as we speak. But I think there is a problem with the charge thingy.
Its off and charging.. but sooner or later it turns off due to low battery (IM SUCH A NOOB I DNT KNW IF THE LOW BATTERY IS CAUSING THE PROBLEM)
I'll wait for it to charge again though and connect to the PC again
In the meanwhile can u answer me something regarding this
1. Does the red light turns on while charging in CWM 5.8.4.0
2. Does the mount USB Drive works? :'( Cuz when the phone was working fine. The mount USB Drive failed and gave an error of having a "lunfile missing" :/
Both of your questions can be found :
http://forum.xda-developers.com/showthread.php?t=1594819
i flashed the boot.img like ray said. then i turned the phone to recovery mode it went there and then mounted the usb it worked etc.
but I didnt flashed just yet.. i wanted it to be charged so i turned it off.. I am again getting that "not turning off" habit again
OH God what am i doing wrong here
PLEASE!! Someone help me! It's got that nasty thing that gets HTC Queitly Brilliant thing again.. It's charging but won't go into the recovery mode now!!!!!!!!!!!!!!!
How can I charge my phone while on Relocked Bootloader. I need help u guys!
So last night I unlocked the bootloader for my HTC One X. I wanted to get CM10.1 Nightly builds onto my phone, and was able to get all the way to where I have CWM 5.8.4.0 and even installed CM10.1 Nightly release. The problem at the time was that when I rebooted the phone it would become stuck at the bootscreen with the "Quietly Brilliant" quote. I tried everything from there to get CM10.1 working based on what I found around other threads and forums.
At one point the battery started running low and the phone stated that the battery was too low to perform fastboot commands. I thought I was in the clear as forums stated that as long as you have CWM on your phone then you can charge it back to full. I turned off my phone and plug in the wall charger and the red indicator light turned on a solid red.
This morning when I woke up, the red indicator wasn't on so I tried turning it on and nothing happened. I held down the volume button and pressed it, held down power for a minute...nothing seemed to work. I tried plugging my phone into my pc and it made that sound where the computer recognizes a new device and then made the sound that a device has been disconnected shortly after. This time though, the red indicator turned on but was blinking. I check other forums on how to fix this and all of them say to either:
1. Let the phone charge until the red light is solid
2. Hold down the volume button and then click power to boot into recovery.
The problem with that was the first option didn't happen, at a certain point the red light will just turn off. The 2nd option yielded nothing as I can't turn my phone on...
I'm seriously hoping I didn't just brick my phone and am hoping someone out there has a solution to the problem I'm facing.
Please and thank you!
***UPDATE***::: I got it to charge just enough to power on back to the bootloader using a Duracell external battery pack. Stupid me decided to relock the phone and go for the RUU when I clearly didn't have 30% battery life. I ended up looking around forums until I found a fix for that located here: (http://forum.xda-developers.com/showthread.php?t=1658084)
Using that method my battery maxed at 3665mV and I had just enough power to unlock the phone again and then reflash cwm 5.8.4.0 just for safety measures. Now I have the phone booted into the recovery main screen and plugged it into my ac charger. However, there's no LED indicator and I'm not sure if the phone is even charging at this point. Unless someone can help assure me that it is actually charging then I will wait about 2 hours before plugging it back into my pc and checking the power variable. Hopefully this all works out...
***UPDATE 2***::: This is just leading to more frustration. I proceeded with the following tutorial http://forum.xda-developers.com/showthread.php?t=1859714 and got to where I start the RUU exe. Unfortunately for me I ran into a "155: Unknown Error" and I tried the following RUU's: (3.14.707.24), (3.14.401.31) first. My phone code is (3.14.707.24) so I wasn't sure why it wasn't working. I read another thread http://forum.xda-developers.com/showthread.php?t=1660642 that said to try either (1.29.401.11) or (1.29.401.7). Both of these RUU's gave me either a "USB connectivity error" or a "Main battery is below 30%"
Now I wasn't sure if my phone had actually lowered that much since I started working on it, but I checked the mV value and it gave me 4030 which I thought was more than 30%. I don't believe it's the USB cause I can still get to the 155 error for the former RUU's. I just went ahead and started charging the phone again and will try again soon. This is really ticking me off...
***UPDATE 3***::: NOPE! I flashed TWRP in replacement of clockwork just cause another thread said it's supported rather than just a port like CWM. Anyways, I've tried several other RUU's and they all give me the 30% Low Battery nonsense. I have tried: (1.28.728.9), (1.29.728.12), (1.29.707.11) but I didn't expect these to work since the previous thread menioned how I can't go backwards. Right now I'm completely lost on what I should do. RUU was supposed to be the last resort, but even this is failing me. FYI: My device's CID: HTC_044 and version as mentioned before: 3.14.707.24 Don't know if that will help but if someone out there can tell me my next steps then it would be much appreciated.
***FINAL UPDATE***::: Mission Accomplished!!! I'm glad to say that I got my phone running back on stock and am not holding a brick in my hands. How I fixed it? This morning I came across this thread here http://forum.xda-developers.com/wiki/HTC_One_X#Disaster_Recovery_-_what_to_do_in_the_event_of_a_bad_flash and I noticed something new in the instructions. It said to run fastboot when executing the RUU, and interestingly enough when I got to the 2nd to the last step the version said "updating from 3.14.707.24 to 3.14.707.24" Before, I ran the RUU while on the "Quietly Brilliant" splash screen since the tutorial I was following never mentioned having to run the RUU while in fastboot. This would probably also explain why, when I ran the RUU in the splash screen, it gave me the (3.14.401.31) version number instead of the correct (3.14.707.24) version.
Well, it's been a messed up roller coaster of a ride and I will try my luck with flashing another rom later this week. I hope I never have to revisit another HOX troubleshooting thread for the remainder of the time that I use this phone. Thanks to all that assisted in my endeavors.
Hey,
Try to boot into recovery when charger is plugged in hold power + vol up buttons and wait.
If that doesn't work, there is a script that charges the phone by looping ot on fastboot.
After you manage tocharge the phone boot into recovery and install cm 10.1 vendor installer :
http://d-h.st/487
Sent from my HTC One X using xda app-developers app
davidk-il said:
Hey,
Try to boot into recovery when charger is plugged in hold power + vol up buttons and wait.
If that doesn't work, there is a script that charges the phone by looping ot on fastboot.
After you manage tocharge the phone boot into recovery and install cm 10.1 vendor installer :
Click to expand...
Click to collapse
I already tried the method you mentioned and that didn't work. The problem with the script is that I assume I would need to have the phone charged somehow and then turn it on. I can't charge the phone at this point so I'm lost...
Did yoy actually try to boot into boot loader? Power + vol down
As far as i remember, charge script works whe on bootloader(please correct me if im wrong guys)
Im using twrp recovery and it charges just fine for me.
Sent from my HTC One X using xda app-developers app
The one and only solution to this is to plug it in to an AC charger and let it charge over night. It doesn't matter if the led is enabled or not.
davidk-il said:
Did yoy actually try to boot into boot loader? Power + vol down
As far as i remember, charge script works whe on bootloader(please correct me if im wrong guys)
Im using twrp recovery and it charges just fine for me.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, I have tried that too...it didn't work =(
At this point the phone just won't charge properly.
TToivanen said:
The one and only solution to this is to plug it in to an AC charger and let it charge over night. It doesn't matter if the led is enabled or not.
Click to expand...
Click to collapse
I plugged it into the AC charger last night and this morning is when the problem started. I'm starting to think I should have left the phone on in the recovery screen and charged it that way.
When I try plugging the phone into the AC charger now there's no red led indicator, but there's one when I plug it into the pc (even though the flashing light disappears after 5 minutes or so).
Hey,
Did you manage to get the phone charged?
Sent from my HTC One X using xda app-developers app
davidk-il said:
Hey,
Did you manage to get the phone charged?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
So last night I checked the millivolt of my battery after charging it through recovery for about 2 hours and it was at roughly 3810mV. I'm not sure what the max mV for HOX is but I let it charge overnight again. This morning I checked and it was at around 4180mV. I'm not very knowledgable on how to convert the 1800mah value over to how many mV it would equal to. I wasn't sure if this was the max so I left it charging and will get back to it once I get home.
~4200mV is equal to 100% charge.
TToivanen said:
~4200mV is equal to 100% charge.
Click to expand...
Click to collapse
Good to know! I'll give the RUU a try when I get the chance later today and post an update. Thanks!
I flashed TWRP in replacement of clockwork just cause another thread said it's supported rather than just a port like CWM. Anyways, I've tried several other RUU's and they all give me the 30% Low Battery nonsense. I have tried: (1.28.728.9), (1.29.728.12), (1.29.707.11) but I didn't expect these to work since the previous thread menioned how I can't go backwards. Right now I'm completely lost on what I should do. RUU was supposed to be the last resort, but even this is failing me. FYI: My device's CID: HTC_044 and version as mentioned before: 3.14.707.24 Don't know if that will help but if someone out there can tell me my next steps then it would be much appreciated.
Here is your ruu
http://bugsylawson.com/index.php/fi...24-radio-5120416229-release-296434-signedexe/
Relock the bootloader
Fastboot oem lock
Then run the ruu WITH admin rights
Mr Hofs said:
Here is your ruu
http://bugsylawson.com/index.php/fi...24-radio-5120416229-release-296434-signedexe/
Relock the bootloader
Fastboot oem lock
Then run the ruu WITH admin rights
Click to expand...
Click to collapse
If I'm not mistaken, that's the first one I used last night along with the same steps. It gave me the "155 Unknown Error" and I proceeded to trying other RUU's. I will try again when I get home, where I can only hope it works for some odd reason. Stay tuned.
Well its the only one that should work. A newer one in not out. And this one matches the main version 100%
Mr Hofs said:
Well its the only one that should work. A newer one in not out. And this one matches the main version 100%
Click to expand...
Click to collapse
I think what I forgot to mention in the updates was that I found something strange. During the RUU steps, after I clicked update, it said:
Upgrading from 3.14.401.31 to 3.14.707.24 which I thought was really strange since 401 indicates Europe version. Is this something to note?
It was the next steps that lead me to the 155 Unknown Error
The outcome of
Fastboot getvar version-main
That is the number that must match the ruu ....if its 3.14.401 then you have the wrong ruu. Do the command first and check the number/post the outcome here
Mr Hofs said:
The outcome of
Fastboot getvar version-main
That is the number that must match the ruu ....if its 3.14.401 then you have the wrong ruu. Do the command first and check the number/post the outcome here
Click to expand...
Click to collapse
Here's the thing, when I run the command to get the version I receive: (3.14.707.24)
However, when I run the 3.14.707.24 RUU it leads me to a page where it says I'm going from 3.14.401.31 to image: 3.14.707.24
That seemed very odd to me. Can you help explain why this is?
Hmm no i can't ! That's very strange.....try the 707 ruu again. Otherwise try the 401 ruu ?
http://bugsylawson.com/index.php/fi...-r-radio-5120416229-release-302015-signedexe/
Don't exactly know what to think about that
Is there a solution for Droid DNA?
I tried rooting it last night. It was successful. The last step was to reboot according to JCase's method. It hasnt restarted since then. No battery indicator as if its not at all plugged in. "YES IT WAS ON CHARGING THE WHOLE NIGHT". It wont even show me the boot screen. "YES, I PRESSED THE POWER AND VOL BUTTON FOR MORE THAN A MIN".
Any help would be appreciated.
Thank You