Related
So the past two nights iv let my rezound battery go dead. The problem is it wont charge a dead battery. It charges if there is some battery and its on but when it is dead it is dead. The fix was I had to put the rezound battery in my tbolt to get a little bit of juice.
Any ideas or similar problems? I am unlocked with the htc unlock tool and running nils business sense?
Could it be a rom bug?
Don't let your battery die. It's bad for it anyway.
Sent from the Rez Beast
Once the battery is dead what does the LED on the phone do? If it blinks for a while it is either too hot or too dead to turn on, but it can still charge eventually. If the LED is not coming on at all I would pull the battery out and connect the charger with no battery and see if the LED comes on. If still no luck, get a new charger.
Blinks then Charges
I had the battery die on me once (on a prior battery and prior rezound). The phone will blink orange for a WHILE (I tried 3 different chargers not knowing what it was), but eventually started to charging. I think patience is needed. If, after 15 minutes, you still aren't charging, then that's something (but longer if the phone was also hot).
If I hit he power button with or without the battery in the led will light for a short time. I had it plugged in all night and no charge. I used two different plugs.
As for not letting it die. I know its not ideal but I couldn't help it.
jdmba said:
I had the battery die on me once (on a prior battery and prior rezound). The phone will blink orange for a WHILE (I tried 3 different chargers not knowing what it was), but eventually started to charging. I think patience is needed. If, after 15 minutes, you still aren't charging, then that's something (but longer if the phone was also hot).
Click to expand...
Click to collapse
+1. Same thing here.
KORM via the beast known as the Rezound.
I let my phone die completely once. I freaked out that my phone wasn't charging. I went onto HTC's site and it said that it could take 20 or more for the led to turn on while charging if the phone was completely dead. Just plug it in and be patient. It will charge and the led will eventually turn on.
Sent from my Vigor using xda premium
I had this problem too, and am a little concerned I have a defective phone
So I had this issue happen this weekend. My daughter was using the phone when it died. Couldn't get it restarted. (I am unlocked via HTC, stock ROM with bloat removed. Phone is a week old.)
After messing with it using the factory charger/cable and other chargers/cable combinations I got nothing. Light would only intermittently come on for a second or two then go back off.
I charged it over night with the factory charger/cable. Didn't work the next day. Charged it all day and night with my old charger/cable that I know works. Didn't work.
Tried multiple variations of taking out the Battery/Sim/SD card and using the plug-in chargers & CPU USB variations with no success.
Luckily, I had ordered a new spare battery and it came in the mail before I returned the phone. Plugged it and it started up fine.
But my concern is that my phone is not properly charging. I have also had other similar charging/battery life issues that raise concern.
As far as not letting it die, **** happens and phones die, if this is a reoccurring problem, that in my mind is pretty unacceptable. A phone should charge when its plugged in no matter what. I may end up returning it to see If just got a defective phone/battery.
My phone will turn on then off and im starting to think it has something to do with the battery. But when it started it was in tue yelllow on the status bar, now i have it charging without being turned on and the indicator light is on but hopping mine will fire up soon. This all just happened to me within the last two hours lol, already called verizon to get a replacement but still going down there tomorrow.
Sent from my SCH-I800 using xda premium
DLink888 said:
So I had this issue happen this weekend. My daughter was using the phone when it died. Couldn't get it restarted. (I am unlocked via HTC, stock ROM with bloat removed. Phone is a week old.)
After messing with it using the factory charger/cable and other chargers/cable combinations I got nothing. Light would only intermittently come on for a second or two then go back off.
I charged it over night with the factory charger/cable. Didn't work the next day. Charged it all day and night with my old charger/cable that I know works. Didn't work.
Tried multiple variations of taking out the Battery/Sim/SD card and using the plug-in chargers & CPU USB variations with no success.
Luckily, I had ordered a new spare battery and it came in the mail before I returned the phone. Plugged it and it started up fine.
But my concern is that my phone is not properly charging. I have also had other similar charging/battery life issues that raise concern.
As far as not letting it die, **** happens and phones die, if this is a reoccurring problem, that in my mind is pretty unacceptable. A phone should charge when its plugged in no matter what. I may end up returning it to see If just got a defective phone/battery.
Click to expand...
Click to collapse
As far as not letting it die, **** happens and phones die.
--I agree, but once it gets down to 5%, why not just turn it off knowing the problems people are having so wide spread now.
Under the exact same conditions I have had the same problem with a warm battery reboot. It seems to occur when you are talking on the phone and let it die. Once it dies the phone will not reboot. My wife has the exact same phone. When I put her battery in my phone the phone works fine. My wife’s phone dies every night and she simply plugs it in the wall and it charges no problem. Again the conditions seem to be related to the battery dying while it is hot. If the battery dies while the phone is cool and not used then it seems to reboot no problem. I will go to Verizon tomorrow to look for a fix. I will let you know what happens.
I'm also having this problem but i can return my phone because i unlock it or can i return it ?
Check and see if your battery is 3.7 or 3.8v . I wonder if it is related to the charging issue with the 3.8v battery some people seem to be having.
mjh68 said:
Check and see if your battery is 3.7 or 3.8v . I wonder if it is related to the charging issue with the 3.8v battery some people seem to be having.
Click to expand...
Click to collapse
it's a 3.8v what do you recommend i do ?
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
gsgleason said:
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
Click to expand...
Click to collapse
I had the same issue with my OG Droid. Would kill the battery and it would stay dead, even after a whole night of charging. The above method seemed to work for me.
I make 100% sure mine never goes totally dead after an experience I had with my Droid Charge.
I accidentally let it die completely (I fell asleep when it was almost dead & it ran all night). The next morning it was off, I put in a fully charged battery & it fired right up but started FCing like crazy. Every single thing I clicked on force closed immediately, I had never seen anything like it.
I was running a custom ROM & kernel & had done a nandroid BU the day before. I restored the BU & the phone ran perfectly again, but that scared me enough that I made darn sure it never happened again LOL........
gsgleason said:
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
Click to expand...
Click to collapse
That didn't work for me i just won't let it run down i guess.
Holy ****!!! I think I may have found the fix! I have had the same exact problem as everyone in here. It seems to happen once I root. My Rezound would die completely, then after plugging it in, the light would come on for 5 seconds or less then shut off. I plugged it into my computer and Windows makes the USB Connected sound, so I figured something is happening.
I went into my command prompt and *adb devices*. It showed my device, but says in recovery mode. I then *adb reboot bootloader* and the bastard rebooted into bootloader! From there, I chose "REBOOT" and it fired right back up! Anyone who is having this problem, please try this and let me know if it works for you!
***UPDATE***
It appears when the battery dies all the way and then doesn't charge, the phone is automatically going into recovery mode even though nothing shows on the screen. I had my SIM card out when I tried this the first time, then when putting my SIM back in, it started doing the same thing. But again, it was going directly into recovery mode. This time, I tried a simple *adb reboot* and BAM! I'm back up and running! Again, let me know if this works for you, or if you need help doing this, let me know.
thehomebiscuit said:
Holy ****!!! I think I may have found the fix! I have had the same exact problem as everyone in here. It seems to happen once I root. My Rezound would die completely, then after plugging it in, the light would come on for 5 seconds or less then shut off. I plugged it into my computer and Windows makes the USB Connected sound, so I figured something is happening.
I went into my command prompt and *adb devices*. It showed my device, but says in recovery mode. I then *adb reboot bootloader* and the bastard rebooted into bootloader! From there, I chose "REBOOT" and it fired right back up! Anyone who is having this problem, please try this and let me know if it works for you!
***UPDATE***
It appears when the battery dies all the way and then doesn't charge, the phone is automatically going into recovery mode even though nothing shows on the screen. I had my SIM card out when I tried this the first time, then when putting my SIM back in, it started doing the same thing. But again, it was going directly into recovery mode. This time, I tried a simple *adb reboot* and BAM! I'm back up and running! Again, let me know if this works for you, or if you need help doing this, let me know.
Click to expand...
Click to collapse
Yes... HTC phones never charge "powered off" When you turn it off and then put it on the charger, it is actually entering/booting a special screen off recovery mode during charging.
CWM recovery on the rezound has trouble charging a completely dead battery.
Use Amon RA recovery.
As per feralicious' suggestion I've created a poll to collect data. Information on the issue below. Sorry about the long poll.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So I'm on Rezound #2 right now. Both of the phones had the same exact problem when the battery died ie. they simply wouldn't charge. Now I thought the problem was hardware (which is why i got the replacement), but after being able to boot up my replacement phone with my girlfriend's battery, I relocked and RUU'd back to stock. I then threw in my dead battery and VOILA it began charging. I let the battery die again just to see if i can recreate the problem, and havent had the issue since.
Now i really want to unlock my phone again but my girlfriend isn't here all the time for me to test out if this was an issue with either the unlocked bootloader, a kernel issue, ROM issue, or if I'm actually having hardware issues. I'm hoping someone here with an extra battery or external charger here can recreate the problem and hopefully we can pinpoint this. Just for reference the ROM I was using was CleanROM GBE 1.6.5 *SP1* - Base: OTA 2.01.605.11 and whatever kernel that came with it. If this is a ROM and/or Kernel issue, we need to get a hold of scrosler and let him know.
Any help would be much appreciated guys thanks!
EDIT: Just to let you guys know. I did do all the OTA updates prior to unlocking the bootloader in the first place.
UPDATE: So I've been sitting with my phone literally all day trying to pinpoint what could be the cause of this. Clockworkmod seems to be the culprit. I'm going to be testing more right now so I'll keep you guys updated.
UPDATE #2: Success! The battery not charging while dead and powered off issue was resolved on my end. ClockworkMod definitely was to blame. I noticed it stopped charging while powered off/dead as soon as I flashed ClockwordMod and shut down my phone while it was connected to my PC (This was after my 5th go around with the bootloader unlock). I then flashed over Amon Ra to see if it really was ClockworkMod or if it was the recovery in general, and what do you know Amon Ra allows me to charge while powered down and dead. If you guys are having this very problem with your phone and you're running any version of ClockworkMod I suggest you try flashing Amon Ra 3.13 and posting your results so we can see if this is universal.
Instructions to flash recovery with adb and fastboot for Windows below:
Note you only need to do this if for some reason you can't boot into the bootloader using Vol. Down + Power. I am not responsible for bricked phones.
Prerequisites:
1. ADB & Fastboot (found with the Android SDK)
2. Amon Ra IMG (Use ver. 3.15 if you've flashed ICS RUU)
3. Battery with a charge.
Instructions:
1. Pull out battery, and unplug from charger/computer
2. Reinsert battery
3. Plug in your USB cable to computer and phone (your charge indicator light should go on for 1-3 seconds and shut off, then your drivers should load afterwards.)
4. Place the Amon Ra img file in the folder where ADB and Fastboot reside.
5. Once drivers have loaded open up Command Prompt, and find your way to where you set up ADB and Fastboot. Type cd <folder path>
6. Now type the command adb reboot bootloader (Note: if you get some sort of error try again a few more times. if it keeps giving you error try redoing steps 1-3 before doing 5 again)
7. Your phone should have now loaded directly into Fastboot. When in Fastboot go back to the command prompt and type in fastboot flash recovery <amon_ra_file.img>
8. When the process is done shutdown your phone and test the charging.
**ADDED** If you can run ADB commands while the phone is off, dead, and not charging, type adb reboot. The OS should boot up and begin charging. I would say let it charge till 40% before you flash an alternate recovery. If you're unsuccessful in rebooting with adb try leaving your phone plugged into the charger for 2-5 hours (this seems to have worked for some people to get a charge). If that doesn't work I recommend you get another battery or use an external charger. (Thanks excellentnuke)
If you are coming from a dead battery the charge light indicator should turn on for a few seconds then turn off for a few seconds then begin flashing continuously. When the light becomes solid you should be able to boot. When coming from a charged battery the same thing should happen, except instead of the charge indicator flashing continuously it should come back solid.
UPDATE #3: I've also discovered this problem isn't relegated to having a dead battery. Simply disabling Fast Boot and shutting off your phone can recreate the problem with CWM.
UPDATE #4: I can say that I think I've gotten enough feedback to determine that this issue was solved by what I've written above. I would highly advise people to switch over to Amon Ra until we get a bug fix/update for CWM to address this issue.
Thanks to everyone that was involved in this thread to help determine the cause of this; I appreciate it.
You should set up a poll and change the thread title to indicate that.
I am on Ineffabilis GB and accidentally let the battery die yesterday and it charged no problem. I was ready for a problem, thankfully it went straight to charging. I had also let it die once before unlocking and no problem then either.
feralicious said:
You should set up a poll and change the thread title to indicate that.
Click to expand...
Click to collapse
Good idea. Done!
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
I have been running different ROMs and had it die a few times...
When I plug it in the LED comes on and starts blinking, after a few minutes of the blinking, I unplug then re-plug in the phone to the charger and the light comes on and stays on. I never let it sit there long enough to stop blinking on its own. I get impatient LOL.
UgXvibe said:
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
Click to expand...
Click to collapse
I take it you're running stock still? or a custom rom? It seems odd that the charge indicator would take that long to start. I left mine on the charger for about 30 minutes when it was unlocked without any progress.
This happened to me, I took my phone to verizon and they just gave me a new battery... it took a little while, them trying different batteries, looking for a 'test' rezound battery before pulling a packaged battery to try and finally they were satisfied then swapped it out... all my boot logos and screens were stock but my launcher was not... they never went as far as checking phone specs or asking about root/unlock... they did check the phone settings to check on charge at one point... I was just thankful it wasn't a bad micro connector because I didn't want to have to wait for a new phone
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
andybones said:
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
Click to expand...
Click to collapse
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
drinkhere said:
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Click to expand...
Click to collapse
I would highly suggest you relock and go back to stock. It seems to have made the issue subside. Since you have 2 batteries if you wanna do further testing with other roms and configs that would help out a lot. No pressure though i understand if you dont want to do it.
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
joel4832 said:
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
Click to expand...
Click to collapse
Hmmm... I'm beginning to suspect its either an unlocked bootloader issue or a kernel issue and not a ROM issue.
Now thats cool that your phone was able to boot up after an hour on the charger without the charge indicator light telling you it was charging (my phone was probably doing the same thing) but it still shouldnt take that long to be able to boot up the device.
When stock my charge indicator blinks continuously until it's ready to boot up, then it becomes solid. This only takes about 4-5 minutes. When running custom ROM/Kernel it would give me the same thing it gave yours ie. charge indicator turns on for 1-3 seconds and turns off and nothing else.
afmracer6 said:
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I'm definitely going to take this into account and try it when i unlock my phone again. Thanks man!
IrvChynaman said:
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
Click to expand...
Click to collapse
Update in OP!
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
edit: i would also like to note, when putting the battery [my 3.7v] into my girlfriends device. It showed about 80% battery.
krstnsn said:
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
Click to expand...
Click to collapse
are you running clockworkmod recovery? Your issue sounds identical to mine and I MAY have a solution. I'm testing right now on my own phone right now.
IrvChynaman said:
are you running clockworkmod recovery?
Click to expand...
Click to collapse
yes. the touch one. However i had this issue prior with the unofficial clockwork.
krstnsn said:
yes. the touch one. However i had this issue prior with the unofficial clockwork.
Click to expand...
Click to collapse
Ok try flashing Amon Ra 3.13. Clockwork mod seems to be the culprit from my end. what was weird is when the phone was shut down I was able to run adb commands and every time i ran "adb devices" it showed my phone as recovery. It seems like clockwork mod recovery was trying to load before anything else preventing the phone from charging and booting up
So I got my Amaze on Friday, rooted and installed Energy Rom on Saturday, and phone just died on me on Sunday.
I was in the middle of playing Scramble with Friends and phone froze up on me. I had to take the batter out to reset it since the power button was not responsive. After I pulled the battery and put it back in, the phone would turn on.
So i read and read and found out people usually bought new batteries since the most likely culprit was a dead battery. I have a friend with the same phone and tried his battery. I saw the HTC Logo come on for a brief second and then that was it, nothing else. Phone died again and did not turn on (under his batter). I recharged my battery in his phone and tried that as well, but no luck.
Any ideas what went wrong and what I can do to fix this?
The phone is completely dead and not turning on. So that means I can't get into bootloader and recovery.
About Phone:
Unlocked Bootloader
TWRP recovery
Faux Kernel
ENERGY Rom
Any incite on this would be great. Thanks in advance!
Plug it in to the wall charger for 30-45min. Unplug and pull battery again. Put battery back in and you should be good...
Don't be alarmed if the orange led light flashes... It's normal when the phone dies. Be happy you're using twrp and not an old recovery that doesn't have charging while off
http://forum.xda-developers.com/showthread.php?t=1561104
Amaze Bricked
http://forum.xda-developers.com/showthread.php?t=1575191
[Q] Bricked Amaze Won't turn on
I hope that's XBoarder's TWRP 2.0.0...
Sent from my HTC_Amaze_4G using Tapatalk 2
Thanks, i actually read those threads before i posted. I think there are more threads about that but i tried all options and none seemed to work. I will try plugging it in the wall and pulling battery out but the battery is at a 100% charge right now (i can confirm from a friends phone). However, if its just a glitch, then i will try the wall charger trick.
Thanks.
ars88 said:
Thanks, i actually read those threads before i posted. I think there are more threads about that but i tried all options and none seemed to work. I will try plugging it in the wall and pulling battery out but the battery is at a 100% charge right now (i can confirm from a friends phone). However, if its just a glitch, then i will try the wall charger trick.
Thanks.
Click to expand...
Click to collapse
Once you get it booted, I recommend 4EXT recovery... But that's just my opinion
Sent from my HTC_Amaze_4G using Tapatalk 2
Thanks - tried the battery solution but unfortunately it didn't work out for me. Phone just refuses to power up.
Assuming its an official brick.
i have a similar problem, well my battery had charged and running fine for several months, so i unplugged the battery to put my sim on it, and plug it back in when it was booting up it froze on the boot logo, so i took off the battery again so i can reboot it
and ever since it wont come back on, wont either go to the bootloader, so i let it charged all night and nothing happen no led blinking or on, so got my friends amaze's battery to test and it would not do anything at either, right now i am waiting for my replacement, but i hate the fact that this had happen to me
oh wow - well i ordered a replacement as well. I really hope it doesn't come down to a software issue and they don't end up covering the device since it has been rooted.
If the phone is completely dead and non-booting, there's no way for T-Mobile to determine if it's rooted or not. Only until it gets back to HTC to be refurbished could they (HTC) find out but at that point it won't matter to anyone anyhow.
And it couldn't possibly be a software issue. There's something physically defective inside the device that caused it to die.
htc amaze 4g refuse to turn on.
hi all, i'm a newbie here, though i have always loved the XDA. I unlocked my bootloader last night, downloaded and reinstalled my fav apps since i didnt do a backup. while i was downloading the XDA app, my fone freezed and eventually went off. When i tried to get it back on, it got stuck on the white htc screen and later went off after some seconds. It has refused to come on till the time of this post. i really need urgent advice.
I was yet to install a recovery software before the tragedy occurred.
First off let me state that I have looked through a majority if not all of the Amaze bricked threads and cannot seem to locate/understand fully the unbrick process. I have found what appears to be two different ways of unbricking the phone one was here http://forum.xda-developers.com/showthread.php?t=1668340 and the other here http://forum.xda-developers.com/showthread.php?t=1627882 .
I will state my problem with the phone. The phone is about 2 months old and had the stock rom installed on the phone. I sold the phone on ebay and the guy that bought the phone contacted me a day later and stated "I sold him a dead phone" which is clearly not true. This clown attempted to root the phone and ended up bricking the phone. He states that he never did such a thing and the phone would not charge or turn on. I had the guy send the phone back to me and sure enough the phone would not charge or turn on. However when I plug into my computer it attempts to search for drivers. I had the drivers installed on my computer due to it being my phone so I thought it was odd that it was searching for new ones. The problem lies that the driver it is searching for is ( qhsusb_dload ) which from me searching around appears to be caused from bricking the phone. Long end of the short ebay sided with the buyer and I am out the money and have a bricked phone even though the picture on the listing shows the phone working and having 3/4 battery life left.
What I have tried so far is what @tiki66 explained that helped him. I downloaded the amaze file (PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14.550L.17DC_30.78.550L.15_release_257469_signed.zip) from file factory and renamed it to the ( PH85IMG ). I also reformatted an 8gb sd card to the fat32 and put the file onto the sd card and put it in the phone. The phone still would not turn on or charge.
I also have tried @dexter93 way of unbricking. I have installed the version of linux that was required. My hang up is the second and third requirements being ( the appropriate package for the device and the latest RUU for your device ) I believe the RUU is the ruby file that I have downloaded. I have watched the youtube video about 5 times and attempted to link to the phone through the terminal however it stated that the program I was searching for was not there. It seems as soon as I get clarification on steps 2 or 3 would get me through to the phone.
Any and all help would be greatly appreciated. I apologize for the run on or rambling.
Thank you!
Peter
Does adb detect the phone? And does the phone boot into fastboot? If adb does detect it then try to push a recovery to it and see if it takes.
Double0EK said:
Does adb detect the phone? And does the phone boot into fastboot? If adb does detect it then try to push a recovery to it and see if it takes.
Click to expand...
Click to collapse
I cannot get the phone to do anything. I it may be possible that the battery is completely dead however I have left it on the wall charger for about 5 hours. I have seen a few time when I would hit the power button the screen flashes a very dull white for a split second.
I have tried the down volume button and power button about 100 times in the past 2 days.
That could be it. Some recoveries don't allow charging while off so if the guy did root it and put CWM recovery then it doesn't allow charging while off. Try to charge the battery externally or use a different battery.
Yes, it sounds like the guy probably flashed a recovery that can't charge while off.. the only way to get the phone to turn on until you can fix that issue is to charge it with an external charger of some sort.
Definitely not bricked, but as useful as a brick until you can charge it somehow..
hi my htc amaze 4g tmobil wont boot unless connected to usb (charging). my phone was rooted using Hasson tool. everything was working fine. i left bootloader unlocked.
here is what happen. my phone took a dive into a soup . i left it for a few days , then i try to turn it on. it looked as if it was on a boot loop. after reading on the internet they advice forfactory reset. after playing with my phone for a few days this is want happends
at the beginning it was on boot loop .then i connected to computer and when i reboot it it reboot back to boot loader.
i locked boot loader and my phone was able to boot normally, it works im able to make and receive calls. but when i remove it from charging it shuts down. if phone is not connected to usb (charging) it stays in boot loop. i already try 2 different batteries. and batteries take charge. i was looking on the forums for similar problems and i found this is a different phone but problems is the same, i dont really understand the solution but i hope will help some1 give some advice .
http://forum.xda-developers.com/showthread.php?t=272474
guatemala84 said:
hi my htc amaze 4g tmobil wont boot unless connected to usb (charging). my phone was rooted using Hasson tool. everything was working fine. i left bootloader unlocked.
here is what happen. my phone took a dive into a soup . i left it for a few days , then i try to turn it on. it looked as if it was on a boot loop. after reading on the internet they advice forfactory reset. after playing with my phone for a few days this is want happends
at the beginning it was on boot loop .then i connected to computer and when i reboot it it reboot back to boot loader.
i locked boot loader and my phone was able to boot normally, it works im able to make and receive calls. but when i remove it from charging it shuts down. if phone is not connected to usb (charging) it stays in boot loop. i already try 2 different batteries. and batteries take charge. i was looking on the forums for similar problems and i found this is a different phone but problems is the same, i dont really understand the solution but i hope will help some1 give some advice .
http://forum.xda-developers.com/showthread.php?t=272474
Click to expand...
Click to collapse
maybe your battery can no longer hold a charge, if you droped it into soup, maybe it got partly shorted out ?
coolboy6332 said:
maybe your battery can no longer hold a charge, if you droped it into soup, maybe it got partly shorted out ?
Click to expand...
Click to collapse
thanks alot for your reply, but i said i try with 2 different batteries. and i know the batteries are taking charge because i saw the battery setting and it increases. and even at 100% the phone still shut downs if not connected to power. but when the phone is on Disk Drive mode it wont shut down. i wonder why i wont take power from battery.
update. my phone seen to be working better. now it works without been connected to power but it still shut downs. help really needed please.
still need help please, i like my amaze. any suggestions?
guatemala84 said:
thanks alot for your reply, but i said i try with 2 different batteries. and i know the batteries are taking charge because i saw the battery setting and it increases. and even at 100% the phone still shut downs if not connected to power. but when the phone is on Disk Drive mode it wont shut down. i wonder why i wont take power from battery.
update. my phone seen to be working better. now it works without been connected to power but it still shut downs. help really needed please.
Click to expand...
Click to collapse
He didn't mean the battery got shorted out, he meant that the PHONE may have shorted out. I think you need to send it in to HTC for repair. It most likely needs a new motherboard. It's really hard on electronics when they get immersed in liquid.
stevedebi said:
He didn't mean the battery got shorted out, he meant that the PHONE may have shorted out. I think you need to send it in to HTC for repair. It most likely needs a new motherboard. It's really hard on electronics when they get immersed in liquid.
Click to expand...
Click to collapse
thanks for the reply and the explanation. i bought the phone used so i dont have warranty. might as well start thinking about another phone. again thanks for the reply i was about to buy a new battery you save me afew bucks.