Develop Bugs

[Q] Need some help with no longer working desire

Hello,
I have for quite some time used leedroids rom lately the the hd port.
That rom has been a little bit unstable but no real big issue. Now however my
phone has gone totally bonkers.
I have leedroids http://forum.xda-developers.com/showthread.php?t=1038195 due to that i tried to solve the issue. Using the a2sd+ version. Tried the alignment patch etc and spend more or less the entire day studying the forum.
The issue is that the phone is highly unstable.
Most often the alpha rev joker image just keeps rebooting after the joker show up, or it just sit's there. If i pull the battery for a while like a few minutes the phone often boots up but after a while it reboots again. Faster if i open an app. Especially the market app then i get almost an instant reboot.
Did a full wipe ofcourse when installing the rom, did a checkdisk on the sdcard and got new partitions for it both primary of course etc.
I just cant seem to figure out what the error might be. Only thing i havent tried is to install the stock rom. Mainly because i'm not quite sure which one i should use. So if someone could please provide a link the the proper one i would be gratefull. Rooted and s-off one would be good. I'm on the 3 network in sweden but i think they use the standard rom.
no errors while installing
hboot 0.93
Anyone got any ideas?

Well you should start by flashing any other rom using a full wipe.
If that doesn't cut it, you should try to install a htc one. This can be easily done if you are s-off. You should install the latest alpharev hboot with stock partition-layout. Then you can flash a ruu thile staying s-off. Please write back for further help, if the first option didn't help you.

mortenmhp said:
Well you should start by flashing any other rom using a full wipe.
If that doesn't cut it, you should try to install a htc one. This can be easily done if you are s-off. You should install the latest alpharev hboot with stock partition-layout. Then you can flash a ruu thile staying s-off. Please write back for further help, if the first option didn't help you.
Click to expand...
Click to collapse
Is there a way to flash the latest alpharev without having the phone booted? In recovery for example? It's a bit dangerous i noticed cause if my phone crash in the middle of flashing that i would probably be bricked i think. But i'm already s-off though should i do it again to get the latest?

To put it simple yes there is a way to do it without being booted.(actually that is the only way you can't do while booted to the system)
And no you should not run the tool itself again. When you are already s-off you can just download a new hboot image from their website and flash it directly. Download:
http://alpharev.nl/bravo_alphaspl.img
And flash it by following my directions given here:
http://forum.xda-developers.com/showthread.php?t=1248910
You will need to have the sdk installed beforehand.

mortenmhp said:
To put it simple yes there is a way to do it without being booted.(actually that is the only way you can't do while booted to the system)
And no you should not run the tool itself again. When you are already s-off you can just download a new hboot image from their website and flash it directly. Download:
http://alpharev.nl/bravo_alphaspl.img
And flash it by following my directions given here:
http://forum.xda-developers.com/showthread.php?t=1248910
You will need to have the sdk installed beforehand.
Click to expand...
Click to collapse
doesn't seem to be able to connect it via adb. tried the zipfile thing too but it wouldn't allow to install the file using the recovery tool.
Also it seems to be able to boot if i pull the battery for a long time. But as soon as it seems to heat up a bit poof it goes into a reboot. Could there be something wrong with the battery so it get's to hot and reboots?

Might be but you need to be back to stock in order to know for sure. Lets just drop flashing another hboot and return it completely to stock(i don't have time to guide you through that process right now) then you can always reroot afterwards.
Just download the gb ruu here: http://www.htcdev.com/process/legal_download/152
In order to flash it, boot up in the bootloader by holding vol down and pressing power. Then connect it by usb and run the ruu.

mortenmhp said:
Might be but you need to be back to stock in order to know for sure. Lets just drop flashing another hboot and return it completely to stock(i don't have time to guide you through that process right now) then you can always reroot afterwards.
Just download the gb ruu here: http://www.htcdev.com/process/legal_download/152
In order to flash it, boot up in the bootloader by holding vol down and pressing power. Then connect it by usb and run the ruu.
Click to expand...
Click to collapse
Ok great thanks, trying cyanomod now to see if i get the same issues. But i put the phone in the fridge for a few minutes, then it booted just fine and i put set cpu to powersave and phone didnt get hot and no reboot. So gonna try cyano and see if the same happends. Will try full stock when i wake up tommorow. Thanks for the help
ok got reboot on cyano too

It seems to be the famous boot loop problem in HTC desire .
To confirm flash the original RUU, if the problem persist then your mainboard has developed fault.
Sent from Hell

Got it to work for a few hours this morning. Had it turned off and charged it to full during the night. Worked for some 2-3 hours and then reboot.

mortenmhp said:
Might be but you need to be back to stock in order to know for sure. Lets just drop flashing another hboot and return it completely to stock(i don't have time to guide you through that process right now) then you can always reroot afterwards.
Just download the gb ruu here: http://www.htcdev.com/process/legal_download/152
In order to flash it, boot up in the bootloader by holding vol down and pressing power. Then connect it by usb and run the ruu.
Click to expand...
Click to collapse
Ok tried this now, had the battery charged over night also, when i tried to install it it says battery below 30% but he battery has full charge :S

[Q] Need help may have bricked my one X

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?

[Q] One X Stuck at bootloader

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.

stuck on bootloader and cant charge

hello i have htc one 32gb international version with custom rom with custom recovery then i decided to back to stock rom so i did relock my bootloader but my battery was less than 20% and now my phone stuck on bootloader and i cant charge it or flash anything like recovery or ruu...i saw many thread to fix this problem i tried many method but it didnt work and i dont know what to do now...is it dead?
now i left it charged through orginal charger

hashnoz said:
hello i had htc one 32gb international version with custom rom with custom recovery then i decided to back to stock rom so i did relock my bootloader but my battery was less than 20% and now my phone stuck on bootloader and i cant charge it or flash anything like recovery or ruu...i saw many thread to fix this problem i tried many method but it didnt work and i dont know what to do now...is it dead?
now i left it charged through orginal charger
Click to expand...
Click to collapse
Sorry to hear you have problems.
Did you try with this:
http://forum.xda-developers.com/showthread.php?t=1609190
Regards.

thanks for nice reply..yes i tried but it didnt work..when i connect the phone to pc it just reboot to bootloader

I had this too,contacted HTC who repaired it under warranty.

but i see many method to fix this problem but i didnt work

hashnoz said:
but i see many method to fix this problem but i didnt work
Click to expand...
Click to collapse
Please - explain with details what you did- you only relock the bootloader, or change it with original one, or else.

Try creating a batch file using :
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Click to expand...
Click to collapse
Leave that running for a bit.

im just relock the bootloader but it have custom rom with custom recovery but i cant access to them...i creat this batch and it goes from 3000mv to 3240 then it goes down to 3210.. i dont know how charge it

it just stuck on bootloader i cant do anything

If your battery is above 10% you can still flash via fastboot.
Assuming you relocked because you want to return to stock, Do the following:
Unlock bootloader again (battery must be above 10% to fastboot flash)
Flash CWM Recovery.
Flash boot.img of custom ROM
Flash custom ROM.
Charge phone to 100%.
Relock bootloader.
Run RUU.
If that doesn't work, you'll have to leave the script posted above running overnight with the phone connected and try again in the morning.

i use the script but sometimes goes up and sometimes goes down..how many hours i need to let the battery 3680mv?

the script cant charge more than 3586 what i can do?

Gan you get into Fastboot now?
Sent from my HTC One X using xda premium

yes i can

So follow my instructions from before.
Sent from my HTC One X using xda premium

Go into hboot and select the option to power device off.? This way it keeps charging and device stays off. It only goes on if you replug the cable.
Sent from my Nexus 7 using xda app-developers app

Other option that work but u should sweat is... Start the pbone, once u get stuck re start again, this gives the phone little amount of charge, but while u r doing this, should try to flash recovery cwm. It s a long trip bro. But it works, i helped three friends wirh this method.
But u know, xmoo rocks
SkyDragon Sense Rom V1

xmoo said:
Go into hboot and select the option to power device off.? This way it keeps charging and device stays off. It only goes on if you replug the cable.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I had a similar situation, but choosing power off caused it to reboot all the time for some reason.

how many minutes i need to charge it?
i use the script charge.bat..but when it come to 3583v it goes down why?
i dont know how to power off and restart it again?
i think my phone is dead no way to fix it

Just follow my instructions on page 1. If you can get into fastboot to flash a proper recovery you're fine!
Unlock bootloader again (battery must be above 10% to fastboot flash)
Flash CWM Recovery.
Flash boot.img of custom ROM
Flash custom ROM.
Charge phone to 100%.
Relock bootloader.
Run RUU.
Click to expand...
Click to collapse
You seem to be in a panic about this, and not prepared to follow instructions.

[Q] I think i soft-bricked my phone. need advice on next step

Hey guys, im going to be as detailed as possible.
Couple of days ago i rooted my One X and it was all good, had installed a custom ROM and everything. But i found out that whatsapp doesnt play nice with custom ROMs. Sicne i need whatsapp( Yeah i tried to download LINE but i cant download large apps(?)) i decided to go back to the stock OS. I had a backup of nandroid on clockwork recovery mod and restored it. But it didnt get past the boot screen. Cleared cache etc still no dice. So i thought it would be a good idea to unroot my phone.No,no it wasnt.
I followed all the unrooting steps, locked the bootloader. Well here is my problem, when i tried to run the RUU it aid i had the wrong one. So i think i have found the right RUU but during the searching my battery went below 30%. Everytime i on/reboot the phone it just goes to fastboot. Am i wasting my time with this RUU stuff? or is it the way to fix my phone? If i it means anything, my cid is htc_44.
Thanks in advance
EDIT: Ok guys i really need your help, i cant even re-unlock the bootloader because the battery is too low. Whenever i try and charge it just goes to fastboot. Even if i try and powe it down it goes back into fastboot

what happends when you plug the phone in the wallcharger and boot into fastboot and then choose powerdown .... Does it start to charge and do you see a red charging light come on !
Otherwise you have to search for the batt charge script
This is the one i found
http://forum.xda-developers.com/showthread.php?t=1658084

Dude you should have flashed the boot.img file for stock and none of this would have happened. That was the only step you were missing
Sent from my HTC One X using xda app-developers app

tomascus said:
Dude you should have flashed the boot.img file for stock and none of this would have happened. That was the only step you were missing
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
To late now !

Mr Hofs said:
what happends when you plug the phone in the wallcharger and boot into fastboot and then choose powerdown .... Does it start to charge and do you see a red charging light come on !
Otherwise you have to search for the batt charge script
This is the one i found
http://forum.xda-developers.com/showthread.php?t=1658084
Click to expand...
Click to collapse
It just goes back into fastboot. Im currently charging my battery with the bat file. After its charged what do i do? unlock bootloader and go in clockworld recovery to charge then do the RUU

Well my best guess is that you run the ruu directly after charging
Keep the phone in fastboot USB mode and run the ruu from pc with admin rights !!!

Mr Hofs said:
Well my best guess is that you run the ruu directly after charging
Keep the phone in fastboot USB mode and run the ruu from pc with admin rights !!!
Click to expand...
Click to collapse
Ok cool, how much batter do i need to run the RUU? in volts? is 3.68 going to be enough?

Ai that's a question i can't answer ...

Mr Hofs said:
Ai that's a question i can't answer ...
Click to expand...
Click to collapse
Thanks anyway

any update?

ujiosan said:
any update?
Click to expand...
Click to collapse
Phone is still charging, going to try RUU in a few minutes.

You can charge it from Clockworkmod 5.8.4.0, which is quicker and will charge more than the script.

BenPope said:
You can charge it from Clockworkmod 5.8.4.0, which is quicker and will charge more than the script.
Click to expand...
Click to collapse
True and some people reports charging trouble in that cwm recovery if so you can flash this one
http://db.tt/K8Aoto6o
Its the cwm 6 recovery