Hi.I tried to unlock bootloader and install recovery.I followed http://forum.xda-developers.com/showthread.php?t=1592922
Everything was ok until i install [ROM] Android Revolution HD 1.2.2 i followed the intructions but right now when i try to turn on the device I have notification "battery low switching off"i put in charge for all night but nothing happens;/when i try to boot into recovery with power and volume- i have something like that
===UNLOCKED===
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.34.0000
CPLD-None
MICROP None
RADIO None
eMMC-Bootmode disable
CPU bootmode disable
HW Secure boot enable
MODEM PATCH OFF
HBOOT
checking SD card update...
and thats all what i can do wiht my phone...
ps.the notifications LED sometimes blinking(red) and sometimes is RED for lon time
I dont know what i can do riht now:/ please help me(sorry for my english)
Get the RUU for your phone and return to stock. Ensure all hardware is working correctly before you attempt again, and try harder to follow the instructions next time.
M.
thanks a lot i'll try your solution
When i try to flash i recive something like that from terminal
MacBook-Pro-xxx:~ xxx$ cd /Users/xxx/Desktop/fastbootMacBook-Pro-xxx:fastboot xxx$ ./fastboot-mac flash recovery endeavoru_recovery_signed.img
sending 'recovery' (5786 KB)... OKAY
writing 'recovery'... FAILED (remote: battery low)
MacBook-Pro-xxx:fastboot xxx$
When try to charge red light from led blinking
I had the same problem
-Battery not charging
-I can not use RUU because low battery
Any help?
still no idea how to solve this stupid mistake?
We had the same problem with some Xperia Arc devices. It's an issue with Battery guage I think. A kernel developer found a fix for it. I'm not 100% if that's the problem. It's better you return your device.
I FOUND THE SOLUTION !!!!!!!!!!!!!
First Sorry for my French !
So, flash stock recovery first, lock the recovery.
Go to fastboot, and click on the Power Off, screen goes black and the phone is OFF.
Put the charger and the usb on the phone, WAIT 1 or 2hours, led still red, DON'T POWER ON !
When is done, go fastboot, launch RUU, IT'S DONE, battery is good !
Works for me
ShyamSasi said:
We had the same problem with some Xperia Arc devices. It's an issue with Battery guage I think. A kernel developer found a fix for it. I'm not 100% if that's the problem. It's better you return your device.
Click to expand...
Click to collapse
If they unlock the bootloader, they lost the guarantee.
how can i flash stock with empty battery?
mabey 1 step it's go to bootloader fastboot power off and then try to charge?
al-motamel said:
I had the same problem
-Battery not charging
-I can not use RUU because low battery
Any help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24821382#post24821382
I tried to use solution from link but still not charging.
Red led shines constantly only few minutes and then start blinking.
Also i left for all night but nothing heapens and when I try to fash via flasboot stock i had stiil info about low battery
Any help?
The problem is solved.I run the recovery*still dont know how phone was charge;/) and restore a previous rom.thanks for help
Related
Hiya guys,
I recently purchased a HTC desire and its been nothing but trouble. THe phone simply refuses to function. It loads directly into the boot loader after around 3 seconds after I press the power button. It will NOT go into recovery mode, I have tried many times but nothing. Even worste when it enters bootloader all buttons cease to function and I cannot scroll to select an option or enter FASTBOOT, no buttons function whatsoever.
The devices is detected via usb, fastboot commander gives me this error when reading the device details -
Code:
HT05PPL02709 Connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: failed.
Radio version: failed.
Main software version: failed.
cid: failed.
cpld: failed.
getvar:product failed (command write failed (unknown error)).
getvar:mid failed (command write failed (unknown error)).
getvar:security failed (status malformed (1 bytes)).
getvar:build-mode failed (command write failed (unknown error)).
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.
Within the bootloader itself I get this information -
HTML:
BRAVO PVT1 SHIP S-OFF
RIFF: 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02_2
AUG 10 2010, 17:52:18
When the USB is plugged in I get "HBOOT USB PLUG"
Devices is detected as "MY HTC"
I tried flashing with official htc update utility but I get error 170 (bad usb connection). The device charges etc but that's about all I have been able to do thus far.
I will provide further details if needed, I just really want this fixed.
A small reward of £10 (around $18 dollars) will be issued via Paypal to the first one to fix my problem as a token of goodwill. Would appreciate any help here guys!
Ensure to have the correct drivers (uninstall all htc drivers u have and install the latest htc synch from htc website)
then run the latest ruu for the desire 2.29.405.5
ps. no reward needed
poweroff and hold BACK and POWER. this boots you directly into fastboot mode.
From there you can issue the command
Code:
fastboot oem gencheckpt
which boots you into recovery. Try to flash a rom or restore a backup and get back at us
And yeah we don't help people for profit
bortak said:
poweroff and hold BACK and POWER. this boots you directly into fastboot mode.
From there you can issue the command
Code:
fastboot oem gencheckpt
which boots you into recovery. Try to flash a rom or restore a backup and get back at us
And yeah we don't help people for profit
Click to expand...
Click to collapse
When powered off back and power, or any combination of keys still just instantly load the boot-loader. This is what makes my problem ever more difficult to solve.
The 'reward' is merely a token of my appreciation. Anyone have any ideas please let me know!
I would say put the relevant PB99IMG.zip on the sd card via whatever means you can and return it to stock via the bootloader.
rootSU said:
I would say put the relevant PB99IMG.zip on the sd card via whatever means you can and return it to stock via the bootloader.
Click to expand...
Click to collapse
hardware keys don't work so he won't be able to begin the update :/
bortak said:
hardware keys don't work so he won't be able to begin the update :/
Click to expand...
Click to collapse
Thats exactly my problem. The strange thing is the buttons do actually work but the boot loader just doesn't. So i'm stumped! Is there any solution, i'm starting to lose hope!
Im confused. How do you know the buttons work if you can only get into bootloader and the buttons dont work in teh bootloader?
rootSU said:
Im confused. How do you know the buttons work if you can only get into bootloader and the buttons dont work in teh bootloader?
Click to expand...
Click to collapse
Well I assume they work since the power button works just fine to turn it on to the bootloader. And since they ceases to respond once there I thought perhaps the same could apply to the other buttons.
When I plug in the usb it says "HBOOT USB PLUG" and when I unplug it it simply says "HBOOT" perhaps that is relevant in any way shape or form?
Thanks for sticking by!
So when it goes into hboot, it shoudl highlight fastboot. Pressing power at that point does not take you to fastboot?
Has the device ever had water damage? It could be that the volume button is stuck down or thinks its stuck down.
Also thats an old radio you have there, from 2.1
has this device every worked for you?
rootSU said:
So when it goes into hboot, it shoudl highlight fastboot. Pressing power at that point does not take you to fastboot?
Has the device ever had water damage? It could be that the volume button is stuck down or thinks its stuck down.
Also thats an old radio you have there, from 2.1
has this device every worked for you?
Click to expand...
Click to collapse
It does simply not respond whatsoever to input from the buttons. I ran the command 'fast boot devices' and it did find a device and listed its ID. But when I try reboot or flash witt fastboot I get a 'malformed bytes' error code.
No water damage
crackmunky said:
It does simply not respond whatsoever to input from the buttons. I ran the command 'fast boot devices' and it did find a device and listed its ID. But when I try reboot or flash witt fastboot I get a 'malformed bytes' error code.
No water damage
Click to expand...
Click to collapse
Have you tried running RUU? You can try running the 2.2 RUU and if that doesn't help, 2.3. As your device recognizes that it's plugged in, it could respond to RUU
matus.karahuta said:
Have you tried running RUU? You can try running the 2.2 RUU and if that doesn't help, 2.3. As your device recognizes that it's plugged in, it could respond to RUU
Click to expand...
Click to collapse
RUU recognizes it I think, It alerts me if the battery is lower than 30%, once charged it then loads for about 40 seconds than I receive error 170, USB error. Perhaps this is a sign that it could possibly work.
I have googled the error 170 and alot of people seem to think its a driver issue? However after installing, re-installing and installing again the official, latest HTC sync files it still refuses to work.
Any ideas where to go from there?
Are you using the original cabe? Aftermarket cables seems to work, but using mine original cable, resolved all errors for my colleague who could not flash a RUU.
And try the driver from Unrevoked: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
I NEVER used the official HTC drivers nor HTC sync, but I was able to do everything with the modified USB drivers.
The unrevoked files are currently down FYI
Sent from my HTC Desire using xda premium
Trying a different cable with Unrevoked drivers, will port back shortly. Thank you for the replies thus far guys!
Dam no luck, still 170 error! Tried with two separate cables. Anything else which would cause this?
This is usually only fixable by using PB99IMG.zip but you're stuck there. Really not sure what you can do now. I think you're stuck
Sent from my HTC Desire using xda premium
crackmunky said:
Trying a different cable with Unrevoked drivers, will port back shortly. Thank you for the replies thus far guys!
Click to expand...
Click to collapse
can you take the sd card from the mobile and download "PB99IMG_downgrade" from alpharev.nl, save as PM99IMG.zip in the SD card via PC. put the SD card in the mobile and switch it on. if it is successful, then try the RUU. Hope it helps you.
kmaq said:
can you take the sd card from the mobile and download "PB99IMG_downgrade" from alpharev.nl, save as PM99IMG.zip in the SD card via PC. put the SD card in the mobile and switch it on. if it is successful, then try the RUU. Hope it helps you.
Click to expand...
Click to collapse
I will try this as soon as I get home. Will this work since I cant hit any keys? How will this take effect without me bein able to 'apply' it? or will its presence on the sd card stimulate some kind of effect? Thankyou for the reply!
Hi All
First thanks for a very good and informative forum.
======================
This was my first post/question and was placed in wrong section. Now it replaced. - Sorry for that!
======================
Information:
HTC Desire
rooted
S-OFF
EXT4 recovery
rom: runnymix...
sd-card partioned(by EXT4 recovery)
AMOLED
Motherboard and ribboncable was changed one month ago on warranty.
Symtpoms:
- Charges normally: orange charging/green full charge. Flashing orange/green without battery
- Cant NOT boot at all
- cant get into bootloader vol down + pwr
- can not be detected buy PC
- Battery inserted and charging: When pressing power to turn on => charge light goes off - and nothing happens. Leaving it in this condition for a while: the phone(mainboard) gets warm.
The phone was functioning perfectly before my son installed bootmanager app. He uninstalled the bootmanager app again without making any changes to the phone. It took long time (like freezing), so he did pull the battery out!!
Any help? Tried a lot of searches, none of them was as my problem.
Thank you
Hi! Have you tried to leave the phone without the battery for 1-2 minutes and tried a reboot?
Take the battery out, unplug it, hold power for 30 secs to get any remaining juice out.
Leave the phone for 24 hours (with battery out etc.)
Stick the battery back in, try again.
bortak said:
Take the battery out, unplug it, hold power for 30 secs to get any remaining juice out.
Leave the phone for 24 hours (with battery out etc.)
Stick the battery back in, try again.
Click to expand...
Click to collapse
What would be the cause for such a behaviour? I'm a little curious (and relatively new to the android scene)!
OT: I've took a look to your troubleshooting guide, good job indeed!
Ryther said:
What would be the cause for such a behaviour? I'm a little curious (and relatively new to the android scene)!
OT: I've took a look to your troubleshooting guide, good job indeed!
Click to expand...
Click to collapse
Really no idea, and what I told you to do is not guarantee'd to work, it may help though.
And thanks, it sure has cut down repeat posts about repeat problems by about 90% here.
Thank you all for your replies.
I did leave the phone without battery for several days - same problem.
But I did not try to press the pwr for 30 secs without battery. I will try when I get home.
I tried following:
- take battery out and reset it. then hold vol dwn + pwr -> Nothing
- take battery out and reset it. then hold back + pwr -> Nothing
By the way, if I press pwr to turn phone on, it does not come up, but leaving it for a while it gets warmer.
It looks like the CPU is trapped in a loop and running at full speed!
Could a riff box repair it?
do a battery pull then hold back & power. That usually boots into fastboot mode, see if the phone is recognised with
Code:
fastboot devices
if it is run the 2.3 RUU.
Dear bortak
I have tried. It does not enter fastboot.
command "fastboot devices" returns blank.
command "adb devices" returns empty list
command "adb reboot-bootloader" givers "device not found error"
RUU gives usb error.
have you installed the proper drivers on your pc for it to connect with the phone?
If so, when you attempt boot into fastboot and connect your phone through USB do you get the "device connected to windows" sound, like when plugging in and external driver or usb?
Because if not even that sound gets played it most likely means that your phone isn't even able to get into fastboot or hboot...
windows does NOT play any "device connected to windows" sound at all.
I have all drivers installed correct on my windows 7. My other HTC devices (desire s, wildfire, wildfire s) connects correctly to the PC and I can get the serial numbers of them using "fastboot devices" command.
Now on work, I tried a windows XP - same problem no connection - no sound.
This desire does NOT get into hboot nor fastboot. I think taht the "bootsector" is correpted.
I even used a Goldcard (made thru wildfire) - not working either.
So fixing it thru USB the normal way is not working.
Is there any way to force the device to boot up from SD card??
I have several backups of the phone system on my 8GB SD card.
You have to find a way to re-flash the hboot. That causes the blank screen display. May be a bad hboot install or something :0 Unless you have S-off and can be detected in fastboot, you can reflash hboot, otherwise you will have to try the blind flash method using PB.IMG. Best I could think of.
Sent from my PB99400 using XDA
@Jonicraw, thank you for your suggestion.
Where to get the HBOOT PBxxxx.IMG for this desire?
And how to flash it blindly, since I have black screen and no connection to PC.
AbuTarboosh said:
Hi All
First thanks for a very good and informative forum.
======================
This was my first post/question and was placed in wrong section. Now it replaced. - Sorry for that!
======================
Information:
HTC Desire
rooted
S-OFF
EXT4 recovery
rom: runnymix...
sd-card partioned(by EXT4 recovery)
AMOLED
Motherboard and ribboncable was changed one month ago on warranty.
Symtpoms:
- Charges normally: orange charging/green full charge. Flashing orange/green without battery
- Cant NOT boot at all
- cant get into bootloader vol down + pwr
- can not be detected buy PC
- Battery inserted and charging: When pressing power to turn on => charge light goes off - and nothing happens. Leaving it in this condition for a while: the phone(mainboard) gets warm.
The phone was functioning perfectly before my son installed bootmanager app. He uninstalled the bootmanager app again without making any changes to the phone. It took long time (like freezing), so he did pull the battery out!!
Any help? Tried a lot of searches, none of them was as my problem.
Thank you
Click to expand...
Click to collapse
im also same problem wont to solution
asad_sah said:
im also same problem wont to solution
Click to expand...
Click to collapse
Had the same problem. Mine could not charge at all and could not enter fastboot/recovery. Send the phone to HTC. I got back the phone with a new battery.
asad_sah said:
im also same problem wont to solution
Click to expand...
Click to collapse
Same s**t for me ... I tried everything you try and no results !
Come on experts ... somebody must have knowledge to fix this common problem.
What about an "Unbrick Jig" like the one for samsulng galaxy:
MICRO USB JIG DOWNLOAD MODE DONGLE FOR SAMSUNG GALAXY S2/I9100/I9000
This device may force the cpu to boot from usb, getting it in "boot flashing" condition.
AbuTarboosh said:
Come on experts ... somebody must have knowledge to fix this common problem.
What about an "Unbrick Jig" like the one for samsulng galaxy:
MICRO USB JIG DOWNLOAD MODE DONGLE FOR SAMSUNG GALAXY S2/I9100/I9000
This device may force the cpu to boot from usb, getting it in "boot flashing" condition.
Click to expand...
Click to collapse
No such things exists for the Desire.
Tell me what state the phone is currently in now?
Yet no solution for this problem...
STATUS for my device is:
Problem solved by changing the motherboard.
I hoped we could find a good solution for this.
I have the same problem but my phone is already on it's 3rd motherboard. I suspect the battery might be the problem but cannot get any answer as to what the voltages should be. I have already submitted a post headed Battery Voltage but it hasn't attracted a reply.
Hi there,
I got the same problem.
Can I send the phone to HTC even if I have rooted it? I also opened it a few weeks ago to replace the broken touchscreen. Do I still have warranty?
Greetings
Mika
Hi,
I really truly tried to resolve my issue (by searching etc.) and learned a lot along the way but I have the problem still.
I bought a used One X. The guy showed me Jelly Bean working on it. I didn't use it at the sale. After I got home I found it was stuck on the HTC start screen. I had to go and it wouldn't turn off so I left it for half a day.
Found the volume down and power trick and booted several times into recovery mode and clockwork. Eventually tried format SD in clockwork. I also found a factory reset or similar button somewhere (can't quite remember if it was in recovery or clockwork). I think it was then that I had no more clockwork. Got a loop into Fastboot, message at the top says "Relocked - Security Warning". Can't switch it off. It occasionally switches itself off doesn't respond to the power button, after a few minutes with a usb plug in it starts again. It turns itself off after 15-20 mins again. When in Fastboot all options just loop back to Fastboot although reboot bootloader takes more time and has more lights.
Eventually started using fastboot cmd. Got an unlock token to flash, received error Failed (remote: battery low). Continued to receive that error with whatever I tried.
Found forums on using wires on the battery to charge and cycling reboots without success. As far as I can tell you can't get to the battery of the one x and I don't get the HTC flash screen mentioned in the cycling solution anymore.
Can I charge this phone? Should I investigate taking it apart to access the battery? Will a phone shop be able to fix this problem by doing things I can't?
Thanks for your time.
Here's your solution
http://forum.xda-developers.com/showthread.php?t=1738274
ArmedandDangerous said:
Here's your solution
http://forum.xda-developers.com/showthread.php?t=1738274
Click to expand...
Click to collapse
Great! Thank you very much A&D. I downloaded and installed Android SDK, got the file and put it in the right folder, now I need to open a cmd window and type "adb ???? fastboot-battery-recharge.bat" in order to charge the phone. Can you help?
Thanks
Just extract the Fastboot-battery-recharge.bat and put it into your platform-tools folder inside your Android folder (assuming you have downloaded the SDK).
Now enter fastboot (power and Vol Down) and double click the .bat file and let it do it's work
Another source for you
http://forum.xda-developers.com/showthread.php?t=1840156
Great thanks, it's going. I didn't realise it was a batch file.
One problem is that my voltage is going down not up, happy to leave it for a while though. Started at 2877mV and now is 2858mV after about 50 cycles. You can see it going up sometimes and down others but overall is going down...
IMPORTANT: I figured out you need to use a short usb cable and avoid front panel and bracket usb slots
Weird. Your phone is still connected right? It should be charging but takes a long time. If all else fails, HTC is your only help ):
Hi,
I have the same problem but i can't get ADB to work on mac osx.
I can't get to recovery because the battery is to empty, i can't get to flash a boot.img because batt. is empty.
does anyone have a solution?
The battery is up after 30 mins to 2960mV so it does work overall.
fvanommen said:
Hi,
I have the same problem but i can't get ADB to work on mac osx.
I can't get to recovery because the battery is to empty, i can't get to flash a boot.img because batt. is empty.
does anyone have a solution?
Click to expand...
Click to collapse
The batch file contents are as follows:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
You could write your own batch for use with mac (assuming mac's can run fastboot.exe)...or just type it out for 6 hours straight
fishy12345 said:
The battery is up after 30 mins to 2960mV so it does work overall.
The batch file contents are as follows:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
You could write your own batch for use with mac (assuming mac's can run fastboot.exe)...or just type it out for 6 hours straight
Click to expand...
Click to collapse
Glad it's working! Gonna take many hours to get that charge up, but at least it's working xD
fishy12345 said:
The battery is up after 30 mins to 2960mV so it does work overall.
The batch file contents are as follows:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
You could write your own batch for use with mac (assuming mac's can run fastboot.exe)...or just type it out for 6 hours straight
Click to expand...
Click to collapse
I have the same problem, the HTC screen is coming up the led is burning and than reboot (in about 5 sec).
My Battery is charging with every reboot very slow but it is charging.
From 1% to the required 3474mV was 12 hours of charging (about (8640 reboots :silly
Now i am on 3487mV but this is still not good enough.
I will let is charge for a little while hoping it will work again.
Solved - "FAILED - Remote (battery low)" error
fvanommen said:
I have the same problem, the HTC screen is coming up the led is burning and than reboot (in about 5 sec).
My Battery is charging with every reboot very slow but it is charging.
Click to expand...
Click to collapse
Yep it's a common problem by the sounds and hopefully this thread will stand out as the one to use.
Basically if you receive a "FAILED - Remote (battery low)" error through fastboot you should use the command "fastboot getvar battery-voltage" and find out how far from the required 30% (how low the mV number is / highest mV the battery holds = [> or < 30%]), this will vary from phone to phone. If you are under the threshold and have the older boot loader you will not be able to charge your phone by leaving it plugged in and hoping. You are have 3 options:
1) If your phone has a removable battery you can the wiring from an extra usb cable in order to get charge or just put in a charged one - the One X cannot use this solution
2) If it is close to 30% you might be able to get enough charge by rebooting it 10 or 20 times (this is because for a portion of the boot up time the phone takes on charge). The report of this solution working involved the ph boot looping onto the HTC splash screen, my ph was looping into boot loader only.
3) If it is far enough off the correct mV, you can run a batch file (props to Laav) that loops 2) and reports battery voltage until you are satisfied. This requires a USB connection and you should use a short usb cable and avoid front panel or bracket slots (especially if you notice that the voltage doesn't always increase each reboot).
Once you get to 30% you are able to flash imgs using fastboot and I would recommend (as Laav does) flashing the newer Clockwork Recovery which allows you to charge the phone while in recovery mode. Then let it charge to 100% and worry no more that you'll get caught out.
If you are reading this and don't have this problem, make sure your clockwork is up to date so you don't end up with it (ie. having a problem with your rom and needing flash tools with a battery below 30% leaves you with no way to charge it).
From my experience the batch file method increased my battery voltage 300mV in about 3 hours so 100mV/hr is probably a reasonable guideline.
I'm sorry actually it's not working for me. Just checked the voltage and it's 2960mV. Because it's not my phone I don't know if it had a battery problem or anything. Is there no way around the 30% check?
The receipt says it was purchased on 24.4.12...
This tutorial thread says 30% = 3478mV
With battery-voltage: 3490mV
sending 'boot' (4466 KB)... OKAY
writing 'boot'... FAILED (remote: battery low)
Others say it has to be over 3680mV, i think this is the correct value. But i don't have that value so i have to wait until then to check.
I have the clockwork recovery but it is not loading, when i press recovery i see the clockwork logo about 1 sec and then it reboots.
For now i wil leave it to the charger for 7/6 hours and let it reboot every 5 sec, i hope this will get me enough power.
Is there someone who can make the batch work on OSX?
Thanks
2819mV now...2781mV 3 mins later... I guess aside from installing a new charged battery or sending it to HTC I'm sunk. I'll call a phone repair store and see if they'll change the battery and flash the new clockwork or stock rom for me tomorrow...
Does anyone suggest a change to the batch file/timing to see if that works? To make it longer do I change the "ping /n 6 localhost >nul" to a larger number?
Are other people getting a constant increase when they look over the voltages reported?
fishy12345 said:
2819mV now...2781mV 3 mins later... I guess aside from installing a new charged battery or sending it to HTC I'm sunk. I'll call a phone repair store and see if they'll change the battery and flash the new clockwork or stock rom for me tomorrow...
Click to expand...
Click to collapse
OMG! I found something v. important out, I was using a long usb cable (1.5m) and a usb slot on the computer that is a bracket (rather than the motherboard slots) and once I changed over to a very short cable (10cm - I have it for the car) and the motherboard usb slot I'm almost charged up in 10 mins. I'll edit the longer post now.
Received error "FAILED: remote (not allowed)" when trying "fastboot flash recovery recovery.img"
If your bootloader is unlocked, just flash CWM touch recovery whilst the phone is in fastboot.
http://db.tt/VF9J2eo8
Place it in the same folder as fastboot in Android SDK,
Enter fastboot
Plug in usb cable from PC to phone
Should now say fastboot USB
Open command prompt
cd c:/Android-SDK/platform-tools
fastboot flash recovery CWM.img
Sent from my HTC One X using Tapatalk 2
fvanommen said:
This tutorial thread says 30% = 3478mV
With battery-voltage: 3490mV
sending 'boot' (4466 KB)... OKAY
writing 'boot'... FAILED (remote: battery low)
Others say it has to be over 3680mV, i think this is the correct value. But i don't have that value so i have to wait until then to check.
I have the clockwork recovery but it is not loading, when i press recovery i see the clockwork logo about 1 sec and then it reboots.
For now i wil leave it to the charger for 7/6 hours and let it reboot every 5 sec, i hope this will get me enough power.
Is there someone who can make the batch work on OSX?
Thanks
Click to expand...
Click to collapse
A couple of hours later my battery did not charge ant more and is stuck at 3490mV.
Is there any other way to load my battery?
fvanommen said:
A couple of hours later my battery did not charge ant more and is stuck at 3490mV.
Is there any other way to load my battery?
Click to expand...
Click to collapse
You should still be able to flash ClockworkMod & a custom rom.
You could do this, even if to at least get your phone up and running to charge it fully.
Sent from my HTC One X using Tapatalk 2
fvanommen said:
A couple of hours later my battery did not charge ant more and is stuck at 3490mV.
Is there any other way to load my battery?
Click to expand...
Click to collapse
I found the same thing, it wouldn't go past this but it was enough to change the message from Battery low to (in my case) Not allowed.
I had locked the bootloader but it wouldn't unlock so I locked it (sent command twice and received 'ok' message). Unlocked the bootloader again, realised how the menus/options on stock bootloader actually work, loaded clockwork recovery through the recovery option (it was on there the whole time), went back out and made sure it was up to date, used it to install a new Jelly Bean copy, charged the phone.
Well, it took 12 solid hours of researching and attempts after I initially bought what was supposed to be a working phone but it's back again.
Thanks to all who contributed to my questions.
Hi:
The problem is the next: My HOX was bricked, the LCD display never turns on, i always have a blank screen. My firmware is 3.14.707.24 and i try to use the RUU for my CID_044 to unbrick my device like the user mr.dj26: http://forum.xda-developers.com/showthread.php?t=1859339&page=2. But after i put the unclock code (hdev) to flash the boot.img and recovery.img, my device is totally bricked.
I always have blank screen, but the device can restart and light the bottom buttons, but is like not have any rom. The device is only recognized for my windows when i put the device in bootloader, and when i use fastboot devices, he recognize the device, but when i try to flash any file use getvar command and others, he always say me: FAILED (command write failed (Unknown error)).
Before have this problem, i had blank screen but could hear the sound of the ROM starting and access to the device using adb and fastboot. Using the RUU always say that the battery still under 30%, i put 4 hours to charge and always the led is red. Connect the device after that and always have the same ERRORS. I drain the battery reboting a lot of times and after that i charge the device. After a 2 or 3 three hours the led turns green, but when i reconnect the device i have the same ERRORS.
My HOX is totally bricked or i could do something else to recover the fastboot and ADB connection to flash the ROM using RUU?
PS: I attach pictures of the fastboot errors and the device manager screens of my pc.
My guess is no you can't do much more then this, if you can't flash a recovery or boot.img the game is pretty much over..... sadly enough.
Mr Hofs said:
My guess is no you can't do much more then this, if you can't flash a recovery or boot.img the game is pretty much over..... sadly enough.
Click to expand...
Click to collapse
Thanks for your answer. Sad but is a answer. In this case i need a motherboard to fix all the problems (blank screen and no rom):crying:
Good luck on getting it fixed mate !
All the best
Marcel
Hi guys
I've got a desire Hd, over 2 years old now so out of warranty. Not rooted, Android 2.3.5 (official ROM), Middle East ROM and relocked.
When i turn it on,After a minute or less, when it would normally show an android screen, the screen goes to bootloader. and when I wanna reboot it or enter to the recovery , the screen goes blank but the phone is still on, and the screen is still on but in a very dark grey. if you hold it on an angle the backlight appears to be on. But from that point nothing happens, the buttons no longer respond, and I have to remove the battery to turn it off.
Although I've tried to reset factory my phone but it didn't work and the screen goes blank again when the backlight is still on.
Thanks for your help.
PLease help me asap.
did u ever experience this problem?
What did you do to get it in this state?
bananagranola said:
What did you do to get it in this state?
Click to expand...
Click to collapse
nothing much. I've just removed the battery many times, because the Volume down didn't respond and I wanted to enter to the bootloader!!
any solution?!! :crying:
try this:
What happens after putting battery back whitout pressing the ON-Button?
If it's still off, try pressing once ON-Button AFTER holding Volume-UP till HBOOT comes... maybe your phone need that
OR:
Connect the phone (when its off) to PC. Then turn phone on. Flash the boot.img over PC with fastboot.exe (only boot.img, not hole ROM). I had the same troubles with every ROM i tried, i had to flash it manually.
ammo12 said:
try this:
What happens after putting battery back whitout pressing the ON-Button?
If it's still off, try pressing once ON-Button AFTER holding Volume-UP till HBOOT comes... maybe your phone need that
OR:
Connect the phone (when its off) to PC. Then turn phone on. Flash the boot.img over PC with fastboot.exe (only boot.img, not hole ROM). I had the same troubles with every ROM i tried, i had to flash it manually.
Click to expand...
Click to collapse
Does it needs any RUU to do this or the boot.img is already exist in my phone?! (my phone is S-ON and relocked)
and what's the exact command to flash boot.img not the whole ROM?
Transporter2009 said:
Does it needs any RUU to do this or the boot.img is already exist in my phone?! (my phone is S-ON and relocked)
and what's the exact command to flash boot.img not the whole ROM?
Click to expand...
Click to collapse
Once you're in the bootloader, and assuming your computer has the correct drivers and img files, type in CMD:
"fastboot flash boot boot.img"
I think I'm in a worse condition than you. My phone won't even boot into bootloader, have tried all the hardware keys (Vol+-, Home, Back, Menu) with Power button. I have even tried taking the volume cable out and pressing the buttons directly but my phone still goes into the boot animation and then blank screen with backlight on. My computer is also not recognizing the phone so adb doesn't work. I'm out of ideas, anyone got any?
cherhunghow said:
Once you're in the bootloader, and assuming your computer has the correct drivers and img files, type in CMD:
"fastboot flash boot boot.img"
I think I'm in a worse condition than you. My phone won't even boot into bootloader, have tried all the hardware keys (Vol+-, Home, Back, Menu) with Power button. I have even tried taking the volume cable out and pressing the buttons directly but my phone still goes into the boot animation and then blank screen with backlight on. My computer is also not recognizing the phone so adb doesn't work. I'm out of ideas, anyone got any?
Click to expand...
Click to collapse
I did it but unfortunately I faced with this Failure:
Code:
C:\Android>fastboot flash boot boot.img
sending 'boot' (2840 KB)... OKAY
writing 'boot'... INFOsignature checkin
FAILED (remote: signature verify fail)
what should I do then?? :crying:
and about your problem i think the Volume Key is the problem and it can be fix by replacing the volume key or even with a simple cleaning. don't worry