Related
What would be the most likely reason an Evo wouldn't charge?
Here's my situation:
I've been flashing nightlies for a while. Figured that might be the problem so I restored to an older version. Won't charge. Won't even turn on the orange LED when the phone is off. If I pull up the bootloader at this point, the battery is too low for me to do anything. I've tried charging it from numerous outlets, my computer in multiple USB ports, and my PS3. I don't know what's going on. When I woke up this morning the battery was at 93% and the phone wasn't charging, but I figured the extension cord just got jarred in the middle of the night or something. Any ways any suggestions?
Update: Took it to a Sprint store and asked a guy to try putting in a different battery. He said it booted up and that it was charging, so it appears that might be the problem. Does anyone know how to force my phone to charge THIS battery, or at least what might have caused this?
Update: Turns out this is what's called a 'bricked usb', however, I can't figure out how to fix it. I've done some things with files on a terminal emulator, as well as trying to do stuff in fastboot (I don't think my computer can recognize the phone in fastboot). My phone doesn't recognize ANY usb activity- right now the way I'm charging it involves hotwiring USB leads to the battery. It won't charge when it's off, and I don't think it's recognized in fastboot (when I type 'fastboot oem boot' it says waiting for device and doesn't do anything.
Check cable and charger. It could be the port tho
I"m having the same issue
how did you fix it?
if the sprint guy put a different battery in it and it started charging just fine, then the battery is your problem. YOUR battery may have either fried, or has drained so low that it's unable to take a charge. Sprint techs can "boost" your battery so it will start charging again, or ebay has batteries for extremely cheap. like a few dollars.
I'm having this problem too. Tried new ebday batteries, and the battery life still SUCKS! What's going on!?
Right now I'm trying to get some sort of charged battery life, unroot, and take it in.
how can i unroot the phone if i dont have access trhu the usb?
please help me i need to gt a new phone and i dont want to loose my warranty
cabezapreta said:
how can i unroot the phone if i dont have access trhu the usb?
please help me i need to gt a new phone and i dont want to loose my warranty
Click to expand...
Click to collapse
Take the memory card out of the phone, mount to a pc, via card adapter, download the unrevoked s-on tool, flash it in recovery.
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip
Rename the file to PC36IMG, while memory is in the pc, drag it over. Place the file on the root of your sdcard, boot into the bootloader, then apply the update. You'll be s-on, stock unrooted.
i was able to flash PC36IMG, but when i try to flash the s-on tool all i get is a phone with a triangle when i select recovery
what am i doing wrong?
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 and greetings to all
Before I mention my issue I would like to state..
I have read most of the KF posts like beginers guide,Before asking for troubleshooting help,The 5 second bootloop! aka: Don't let your battery die! etc and it is only because I cannot find a specific answer to my problem that I am posting
I would like to thank people like pokey9000 , kinfauns and all the clever people that have given us KF life saving posts and those that came up with things like FFF, TWRP etc etc, props to you all These have been valuable in the past when I have been stuck in loading roms, rooting etc
Background
for some reason my KF got stuck in the yellow triangle boot loop, rebooting every few seconds...
The battery died before I could get round to hooking it up to my computer and run the necessary scripts...
I tried the usual adb and fastboot scripts - no response, the power didnt come on and the device was not detected.error:device not found
I left it to charge with the AC POWER pack over night...still no life or detection
I tried the
Resorted to the ubuntu memeory stick method...
Ordered a case opener and waited for it to be delivered...
few days later it arived and I opend the KF - didnt break anything
tired the shorting trick - No joy, terminal showed still waiting for device and no power light on the KF :crying:
left to charge again, still no joy
tried adb and fastboot on windows again... no joy.. error:device not found
I think the only thing I havent tried so far is a factory usb cable but I cant see how that will help me here unless ofcourse someone can tell me otherwise
fyi I had FFF and twrp installed and running an ICS 4 ROM
When your not working on it keep it charging via usb note that your battery may charge very slowly also try some of the usb scripts powering your device fully down send the command start and keep the short and plug in when it says waiting for omap you may find better success keep trying till you find a script that works likely usb fix parts install fff twrp youll know when you get it right or usb boot fff
So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?
Since you rooted and unlocked the boot loader... No warranty...so I guess try flash stock ROM...
Sent from my mighty Xperia Arc S
It won't turn on for me to do that in the first place, though.
Mods - I just realized that I posted this in the wrong forum. I apologize for that.
Yes, i searched not only here, i did in the whole internet before.
I have a problem with my nearly new Nexus 7 2013 Wifi model.
First the story hat happened, maybe it has to do with it:
I bought it in August and now updated it to the last version, 4.4.2 Kitkat.
All was fine, i never had any problems until 2 days ago. I saw that the battery was running out but since it was night i let it be. In the morning i heard the sound for an empty battery for the last time, but i didnt check screen. After 20 minutes i looked at the screen and saw the Google-letters only. It didnt respond to the Power button beeing pressed so i thought the battery is too empty to let the device start and decided to plug it to the charger.
Just now i saw that the cable was not plugged in the charger, it was plugged in the PC instead, connected to an USB port (of course). As soon as i saw it i plugged out the cable from PC-USB and put it into the charger. Im afraid this wasnt good. Not sure what happened here exactly.
Now the problem
Anyway, nothing happened after plugging into charger, the Google letters where there but no symbol that the battery is loaded or anything. I thought ok, maybe thats normal if battery fully dry so i let it charge for at least 3 hours. I saw a symbol now and it showed the battery 80% full. Now i tried to start the device but nothing at all happened. Still the Google letters showed up and not more. I know about the fastboot menu (power+volume down) and did that. The fastbook menu shows up and i can select all kind of things like "Start", "Restart bootloader", "Recovery" and "Shut off". Following things happen when i press them:
1. Start > 1 second after pressing start the Google letters show up and nothing happens anymore, no X, nothing
2. Restart bootloader > bootloader restarts (works also over tools like Nexus 7 Root Toolkit, i can restart here too)
3. Recovery > same as 1., the Google letters show up, not more.
4. Shut off > Device shuts off
Now im also developing for Android and that means i have SDK and drivers and all that iinstalled. And it worked always, i could push an app to the device over ADP etc. That just as a side note.
So now i tried to unlock the bootloader to flash my own one, with fastboot. When i enter "fastboot oem unlock" it is stuck right at the first point, wipe userdata. The device has an id so the drivers are ok i think. I just cannot erase the userdata. This will stay like this until i power of the device. Then it continues and says "failed".
The real question
Now without to be able to continue past this im not able to flash anything, if im correct yes.? So do you think this is a hardbrick? Are there other options?
Thanks for any help and tipps, im really out of options.
Btw, exactly same behaviour i have with tools like Nexus Root Toolkit or any, fastbook cannot erase user-data on bootloader and stuck
Saenchai said:
Yes, i searched not only here, i did in the whole internet before.
I have a problem with my nearly new Nexus 7 2013 Wifi model.
First the story hat happened, maybe it has to do with it:
I bought it in August and now updated it to the last version, 4.4.2 Kitkat.
All was fine, i never had any problems until 2 days ago. I saw that the battery was running out but since it was night i let it be. In the morning i heard the sound for an empty battery for the last time, but i didnt check screen. After 20 minutes i looked at the screen and saw the Google-letters only. It didnt respond to the Power button beeing pressed so i thought the battery is too empty to let the device start and decided to plug it to the charger.
Just now i saw that the cable was not plugged in the charger, it was plugged in the PC instead, connected to an USB port (of course). As soon as i saw it i plugged out the cable from PC-USB and put it into the charger. Im afraid this wasnt good. Not sure what happened here exactly.
Now the problem
Anyway, nothing happened after plugging into charger, the Google letters where there but no symbol that the battery is loaded or anything. I thought ok, maybe thats normal if battery fully dry so i let it charge for at least 3 hours. I saw a symbol now and it showed the battery 80% full. Now i tried to start the device but nothing at all happened. Still the Google letters showed up and not more. I know about the fastboot menu (power+volume down) and did that. The fastbook menu shows up and i can select all kind of things like "Start", "Restart bootloader", "Recovery" and "Shut off". Following things happen when i press them:
1. Start > 1 second after pressing start the Google letters show up and nothing happens anymore, no X, nothing
2. Restart bootloader > bootloader restarts (works also over tools like Nexus 7 Root Toolkit, i can restart here too)
3. Recovery > same as 1., the Google letters show up, not more.
4. Shut off > Device shuts off
Now im also developing for Android and that means i have SDK and drivers and all that iinstalled. And it worked always, i could push an app to the device over ADP etc. That just as a side note.
So now i tried to unlock the bootloader to flash my own one, with fastboot. When i enter "fastboot oem unlock" it is stuck right at the first point, wipe userdata. The device has an id so the drivers are ok i think. I just cannot erase the userdata. This will stay like this until i power of the device. Then it continues and says "failed".
The real question
Now without to be able to continue past this im not able to flash anything, if im correct yes.? So do you think this is a hardbrick? Are there other options?
Thanks for any help and tipps, im really out of options.
Btw, exactly same behaviour i have with tools like Nexus Root Toolkit or any, fastbook cannot erase user-data on bootloader and stuck
Click to expand...
Click to collapse
Did you try using NRT and check device unresponsive or whatever it is on the right hand side? Option is normal and bootloop or something like that?
hkgrob said:
Did you try using NRT and check device unresponsive or whatever it is on the right hand side? Option is normal and bootloop or something like that?
Click to expand...
Click to collapse
No, because i thik i have to unlock the bootloader fist to do that, or not?
Edit: Yes it is like that. Cannot flash roms without unlocking bootloader first. It gets stuck and command line shows error after "boot" command > bootloader locked.
I cannot do anything in ADB, only fastboot-menu (Advanced Utilities > Launch). But btw, i found this here, im just a bit afraid to use it. Rooting/flashing Roms WITHOUT unlocked bootloader and ADB
http://forum.xda-developers.com/showthread.php?p=43993722
This is a long shot, but you said you're developing for Android. Any other devices? What drivers are you using? I use these. http://developer.android.com/sdk/win-usb.html
What happens if you try "fastboot devices"?
What happens when you run fastboot erase cache
Sent from my Nexus 6 using Tapatalk 4
Pandae said:
This is a long shot, but you said you're developing for Android. Any other devices? What drivers are you using? I use these. http://developer.android.com/sdk/win-usb.html
What happens if you try "fastboot devices"?
Click to expand...
Click to collapse
Yes i use that ones, from latest SDK. But i also tried others by now, its all the same.
fastboot devices shows me an id like:
04e7df fastboot
xdhall said:
What happens when you run fastboot erase cache
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Wow this one bugs me.... it shows i dont have a partition table anymore...
FAILED <remote: Partition table doesnt exist>
What the hell, as i said, i did NOTHING exactly, how can a partition table be erased from a device that a battery runs dry? You have to know that im one that takes extremley care what apps i install, there are basically only apps from well know devs, like Dropbox, ES File Explorer, Flipboard and Google Apps (non root as i said). Or what should that warning tell me?
And the best of all is, the shop where i bought it doesnt want to change it, they want to send it in (its one month old). And they told me already that due to christmas it can take up to a MONTH until i get it back. In a month im not in this country anymore, i move back to Bangkok, so what can i really do now.... I hate it.
Saenchai said:
Wow this one bugs me.... it shows i dont have a partition table anymore...
FAILED <remote: Partition table doesnt exist>
What the hell, as i said, i did NOTHING exactly, how can a partition table be erased from a device that a battery runs dry? You have to know that im one that takes extremley care what apps i install, there are basically only apps from well know devs, like Dropbox, ES File Explorer, Flipboard and Google Apps (non root as i said). Or what should that warning tell me?
And the best of all is, the shop where i bought it doesnt want to change it, they want to send it in (its one month old). And they told me already that due to christmas it can take up to a MONTH until i get it back. In a month im not in this country anymore, i move back to Bangkok, so what can i really do now.... I hate it.
Click to expand...
Click to collapse
That confirms it. You're beyond my help. I'm fairly certain there's a way to unbrick from where you are. You'll just need someone with more experience than I have.
Sent from my Nexus 6 using Tapatalk 4
Saenchai said:
Yes i use that ones, from latest SDK. But i also tried others by now, its all the same.
fastboot devices shows me an id like:
04e7df fastboot
Click to expand...
Click to collapse
Fastboot appears to be working fine, but this is a bit of a problem. Let's hope this works to recreate:
fastboot oem part-add cache:552
I'm not sure if the 2013 N7 auto-resizes or if it's really this size, but 552 megs is size right now on mine.
What about using fastboot to erase the others?
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Pandae said:
Fastboot appears to be working fine, but this is a bit of a problem. Let's hope this works to recreate:
fastboot oem part-add cache:552
I'm not sure if the 2013 N7 auto-resizes or if it's really this size, but 552 megs is size right now on mine.
What about using fastboot to erase the others?
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Click to expand...
Click to collapse
Not sure why my last post wasnt posted (or got deleted?) but i commented here already yesterday.
As i saw in abother post here there are many others with the same problem, and most times it happened same way too > battery run dry and this is the result, like mine.
Any command in fastboot fails sadly. I did send it in now... guess its really hardbricked from just an empty battery.
Saenchai said:
Not sure why my last post wasnt posted (or got deleted?) but i commented here already yesterday.
As i saw in this post (and a few others) there are many others with the same problem, and most times it happened same way too > battery run dry and this is the result, like mine.
Any command in fastboot fails sadly. I did send it in now... guess its really hardbricked from just an empty battery.
Click to expand...
Click to collapse
I have found that disconnecting the battery terminal clip (yes you must remove the back cover, which is easy, no tools needed & no seals broken) & then after 5 minutes, if you plug the battery back in (the battery, not the power cord), it fixes a whole bunch of issues like this. In doing this to mine, I also discovered my screen/digitizer ribbon cable was loose, causing touch screen 7 display issues galore.
At any rate, since doing this to mine, no issues.
GSLEON3 said:
I have found that disconnecting the battery terminal clip (yes you must remove the back cover, which is easy, no tools needed & no seals broken) & then after 5 minutes, if you plug the battery back in (the battery, not the power cord), it fixes a whole bunch of issues like this. In doing this to mine, I also discovered my screen/digitizer ribbon cable was loose, causing touch screen 7 display issues galore.
At any rate, since doing this to mine, no issues.
Click to expand...
Click to collapse
Thank you very much for this tip. I heard of it but was afraid that it would break seals. I will keep this in mind should i have another problem like this.
The device is now send to repairs. i hope to get it back soon...
Good luck! Sorry we couldn't give you a working remedy to do yourself.