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.
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,
After updating the software using the "software updates" from the settings to Jelly Bean, the device won;t start up, it will show the HTC splash screen and reboot.
I tried to do a factory reset and to shutdown the device but every time i connect the charger it will start up again and enter an infinite loop, I cannot flash a new recovery or firmware.zip using the fastboot because the device does not have enough battery (I tried recharging it using a script that will loop and enter it to reload bootloader but it is not enough, I got it up to 10%, no more)
Any thoughts?
Thanks,
Doron
Try leaving your phone to charge overnight and unlock its bootloader the next morning than follow the required steps to flash a recovery. On the recovery itself, try to make a factory reset of your stock rom and see whether it can still work or not.
If can't than you'll just have to give custom rom a try to see how it goes than
LazySheep said:
Hi,
After updating the software using the "software updates" from the settings to Jelly Bean, the device won;t start up, it will show the HTC splash screen and reboot.
I tried to do a factory reset and to shutdown the device but every time i connect the charger it will start up again and enter an infinite loop, I cannot flash a new recovery or firmware.zip using the fastboot because the device does not have enough battery (I tried recharging it using a script that will loop and enter it to reload bootloader but it is not enough, I got it up to 10%, no more)
Any thoughts?
Thanks,
Doron
Click to expand...
Click to collapse
Ok so its easy download the latest ruu from THIS THREAD for your phone charge it up and to check the charge percentage use fastboot getvar all command
In that see battery it must be above 3680volt if not USE THIS THREAD ON HOW TO CHARGE BATTERY after succesfully charging battery run RUU and you are good to go. GOOD LUCK
hapticc said:
Ok so its easy download the latest ruu from THIS THREAD for your phone charge it up and to check the charge percentage use fastboot getvar all command
In that see battery it must be above 3680volt if not USE THIS THREAD ON HOW TO CHARGE BATTERY after succesfully charging battery run RUU and you are good to go. GOOD LUCK
Click to expand...
Click to collapse
Not so easy, he tried using the script to charge and it's not going up. You have to start there, that's the main problem !
Make sure the script runs with admin rights, and use only the original HTC usb cable and connect it straight to a powered usb 2.0 port on the pc (no hubs, extension cords)
Keep it running for a long time, that process may take many hours.
Fastboot getvar all is not needed, the script tells you exactly what the batt level is after each reboot.
Keep trying the script, it's the only way to charge now. Try to get it just over 10%, it's enough to flash. If you get to that point you flash this recovery asap !
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
And enter it. Hook the phone up to the main (wall outlet) charger and let it charge to a 100% then we can continue
Mr Hofs said:
Not so easy, he tried using the script to charge and it's not going up. You have to start there, that's the main problem !
Make sure the script runs with admin rights, and use only the original HTC usb cable and connect it straight to a powered usb 2.0 port on the pc (no hubs, extension cords)
Keep it running for a long time, that process may take many hours.
Fastboot getvar all is not needed, the script tells you exactly what the batt level is after each reboot.
Keep trying the script, it's the only way to charge now. Try to get it just over 10%, it's enough to flash. If you get to that point you flash this recovery asap !
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
And enter it. Hook the phone up to the main (wall outlet) charger and let it charge to a 100% then we can continue
Click to expand...
Click to collapse
Thank you all for your answers!
I got it yesterday to about 10%, so maybe i will be able to do it again, can you tell me how can I flash this recovery? I saw that the boot loader is locked (On the top of the bootloader there is a pink line sais locked) can I still flash?
Ah no...but since you are locked you have warranty !
Don't unlock it before you let yourself informed about that !!!
Unlocking the bootloader is needed in order to flash anything except a ruu. But for a ruu you need minimal 30% of battery
Mr Hofs said:
Ah no...but since you are locked you have warranty !
Don't unlock it before you let yourself informed about that !!!
Unlocking the bootloader is needed in order to flash anything except a ruu. But for a ruu you need minimal 30% of battery
Click to expand...
Click to collapse
That is what i was afraid of, do you think i can get to 30% with this method?
How do i unlock the bootloader?
I talked to HTC today, because the 1 year has passed they suggested only out of warranty repair so...
What do you suggest?
My suggestion is to try the sctipt and run a ruu first.
We need a fastboot command to get the correct one
Fastboot getvar version-main
Otherwise it's getting over 10% and unlock, flash a recovery and continue from there.
Unlocking goes via the HTC dev site.
Mr Hofs said:
My suggestion is to try the sctipt and run a ruu first.
We need a fastboot command to get the correct one
Fastboot getvar version-main
Otherwise it's getting over 10% and unlock, flash a recovery and continue from there.
Unlocking goes via the HTC dev site.
Click to expand...
Click to collapse
Will i be able to flash ruu after replacing the recovery?
How will i know that i got to 30% ?
Flashing a ruu doesnt need any changes to the phone ! It's locked and stock. Ruu's can be flashed straight away that way. See if you can reach that 3700-3800 mV
I finally got it to 3785....
My phone is s-off with cid:11111111 so I tried to run the following RUU:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed
And I got img error, any thoughts?
OK,
Because i couldn't install the other RUU, I thought I should upgrade my hboot, I used the JBFWFlasher tool from here:
http://forum.xda-developers.com/showthread.php?t=1924003
This changed my hboot to 1.33 and my cid to 621
So I downloaded and flashed:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Radio_5.1204.162.29_release_292865_signed
Finally the system is up and running.
I am still checking to see if everything is working, do you think i will be able to update to 4.2.2?
Thanks a lot guys for all your help
What's your main version
Fastboot getvar version-main
And did you run the ruu with admin rights ?
Another option is to flash the 3.14.401 firmware, that will lift the hboot to 1.39. It's stable and then you can install any rom you want. Then you have at least a clean sense 5 rom.
Finally!
After flashing the ruu I managed to get the system up and running, I even managed to get to OTA for 4.2.2 ROM with sense 5, it seems to work fine now
Thank you very much.
Nice job !
CASE CLOSED !
I was trying to root my htc ONE x as I wanted to run an app that needed a rooted phone. I managed to unlock the bootloader using the One x all in one kit and then went on to the rooting. I followed a guide found here: knowyourmobile.com/htc/htc-one/17426/how-root-your-htc-one-x to the letter.
At the end it said it would reboot twice then once again so I waited patiently. 13 reboots later and it was still going so I disconnected it from the USB (the cmd window closed after 2nd reboot) It is now stuck in a reboot loop and I cannot get it out. I can get to the fastboot menu using the down volume and power but have no idea what to do from there. Tried flashing a stock firmware in this mode but it says my battery is below 30% and I can't get it to charge as its constantly rebooting.
Any help would be greatly appreciated...sorry again to be a pain. I have read and read and I am getting more and more confused
nikonite said:
I was trying to root my htc ONE x as I wanted to run an app that needed a rooted phone. I managed to unlock the bootloader using the One x all in one kit and then went on to the rooting. I followed a guide found here: knowyourmobile.com/htc/htc-one/17426/how-root-your-htc-one-x to the letter.
At the end it said it would reboot twice then once again so I waited patiently. 13 reboots later and it was still going so I disconnected it from the USB (the cmd window closed after 2nd reboot) It is now stuck in a reboot loop and I cannot get it out. I can get to the fastboot menu using the down volume and power but have no idea what to do from there. Tried flashing a stock firmware in this mode but it says my battery is below 30% and I can't get it to charge as its constantly rebooting.
Any help would be greatly appreciated...sorry again to be a pain. I have read and read and I am getting more and more confused
Click to expand...
Click to collapse
Rule number 1 when reading a guide: always make sure to read the comments of the users too, before following the guide.
On the link you provided, there are a lot of people saying the ADB file is out of date and it bricked their phones.
I remember seeing an old post about charging your phone while in fastboot mode. After some searching, I found it:
Mr Hofs said:
Oke new thing to do.
Put this file in the fastboot folder
https://www.dropbox.com/s/aaah8gqz8j024xz/Batt script.bat
Leave the phone in the bootloader/fastboot usb mode and execute the .bat file with admin rights.
Select the .bat file with the right mouse button and select
Run as administrator
It will restart the bootloader continuously and charge it little by little. Leave it going until it reaches around 3800 mV
Then flash the recovery and enter it !
Click to expand...
Click to collapse
I can't confirm this since I've never tried it. Mr. Hofs has to confirm if this method still works but if you still have some battery left, it's worth a try I guess.
If your battery is charged enough, flash a custom recovery and enter it. Then, from the options choose "power off" and wait until someone more knowledgeable than me can help you.
Classic 20, IT WORKED! Thanks man you rule!
nikonite said:
Classic 20, IT WORKED! Thanks man you rule!
Click to expand...
Click to collapse
No problem at all. Glad to have been able to help you!
Also, did you manage to finally boot the phone or do you still get stuck at the logo?
I installed a stock RUU in fastboot and heaved a sigh of relief
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16
ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).
Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:
ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.
Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse
It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it
ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.
Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?
Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
It now says Relocked then underneath security warning. Is that good?
ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.
Will i have to re unlock the boot-loader for the RUU.exe to work?
ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.
Yeah it says updating 0 out of 7 sending ........................
ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.
This is what comes up
It send that 1 had been sent then it said error