So I "Borke" my Moms Amaze, having to buy it off her. Now I have a "Bricked Amaze". Here's what's up.
The Phones 100% Stock on the ICS 3.6 Leak. All Radios, and Boot .img. Everything flashed while the phone was stock GB. It was flashed in the bootloader as an Offical Update.
I then Unlocked the Bootloader via HTC Dev, and Flashed TWRP 2.0 via Amaze Toolkik.
Here's how I think it was "Bricked".
My little brother was playing on my Mom's Amaze, and it died. After that he kept on powering it on, and on, and on. Untill it just wouldn't power on at all. I assumed it was just 100% dead. So I went home, and my Mother called me today. Saying I broke her phone, blah, blah, gimme $300. So I own an Amaze.
The Amaze won't boot into the System. Only Recovery via Amaze Toolkit. I can get it to boot in to the OS by flashing TWRP via Toolkit. But as soon as I unplug the phone, it dies. It won't boot any other way. The phone acts like it's dead, no battery. The led flashes like it's dead, but it has 66% battery.
So what should I do?
probably one of the connections from the battery to the motherboard is dead, try restoring as stock as possible and get it warranted out
I would try getting a new battery for it first. "It's best to avoid taking the battery all the way down to zero. If the voltage of a lithium-ion cell drops below a certain level, it's ruined."
Taken from: http://electronics.howstuffworks.com/everyday-tech/lithium-ion-battery2.htm
Confirmed it was the battery, I slapped my Mytouch 4G Slide battery in it, and BAMN it powered on. Now I have an Amaze, and at a good price
Related
My friend and I both have Rezounds. I have yet to get the update, he had Scott's ICS ROM on his. The update forced itself onto his phone and bricked it. When he went to the store, the reps told him the update seems to be doing this to alot of people (rep said they saw 10 of them today!). Anyone else have the OTA brick a ROM's phone or even stock?
durthquake said:
My friend and I both have Rezounds. I have yet to get the update, he had Scott's ICS ROM on his. The update forced itself onto his phone and bricked it. When he went to the store, the reps told him the update seems to be doing this to alot of people (rep said they saw 10 of them today!). Anyone else have the OTA brick a ROM's phone or even stock?
Click to expand...
Click to collapse
No, but I am sure if you have a custom recovery on your phone with a custom rom an official update sure isn't going to help ..but I figured it would just error out. How did it brick it ? he was unable to load Hboot anymore ?
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Could you get into hboot and run the ruu? If you can do that, the phone isn't bricked...
Sent from my ADR6425LVW using XDA App
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I suspect the no charging is due to running the battery down all the way. There's a thread or two about that issue. I think the solution was to pull the battery, plug in the charger then put the battery back in while phone is connected to charger. Then you might have to wait up to 30 minutes for the light to turn on and for it to start charging.
And yeah, if you can boot into hboot you should be able to get the phone back with RUU or if the ROM is fine then flash Amon Ra recovery in fastboot.
It didn't allow anything to be done in hboot. It won't even turn on now, i have him my battery to try and still doesn't turn on.
Sent from my ADR6425LVW using Tapatalk
Well read through this thread:
http://forum.xda-developers.com/showthread.php?t=1434532
and see if you can at least get it charged up again. Then go from there.
Both me and my wife have had the OTA for at least a week and we have not had any issues with the OTA.
Also, I must say, this is the first time I have heard of the OTA causing bricking of the unit.
If you can't get it charged, try the writing hack to get it involved. Basically you just take a regular usb cable and snip the connector off. From there you take the ground and the power, and then you put the ground and power to the battery in the respective places. Worked for a bad Atrix flash that killed my battery.
Sent from my Galaxy Nexus using Tapatalk
I hadn't heard of it bricking it till I saw it first hand... As far as charging, it's a non issue since I have my friend my fully charged battery to try and wouldn't turn on. (Note that this is happened only after it stayed on the HTC screen for about 30 minutes, so it may have overheated or something during that time?)
Sent from my ADR6425LVW using Tapatalk
It bricked my stock Rezound. Could not have happened on a worse day to. I had to do a factory reset to get it to come back. Real PIA
Chris
drtnsnw said:
It bricked my stock Rezound. Could not have happened on a worse day to. I had to do a factory reset to get it to come back. Real PIA
Chris
Click to expand...
Click to collapse
That's not a brick. That's a pain in the ass.
tekhna said:
That's not a brick. That's a pain in the ass.
Click to expand...
Click to collapse
+1
a brick is just what it is.. a brick.
which means the phone is done. you can't use it again.
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
If it can get to the HTC screen, it isn't bricked. Put your battery in his phone and see if it can get to HBOOT.
durthquake said:
I hadn't heard of it bricking it till I saw it first hand... As far as charging, it's a non issue since I have my friend my fully charged battery to try and wouldn't turn on. (Note that this is happened only after it stayed on the HTC screen for about 30 minutes, so it may have overheated or something during that time?)
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I don't think you can write off the battery/charging issue. It takes some time for people who have let their battery fully drain to get the phone to charge it again although they were able charge on an external charger iirc. Anyway, point is it may be the phone not the battery that needs to "wake up" (for lack of a better term) again.
So definitely go through that dead battery charging thread and try everything in there to get the phone to charge the battery again. Then you'll know the phone is functioning as it should, atm it may not be.
I don't understand how the the OTA forced itself since all of Scotts ROMs are debloated. Everyone that rooted and debloated running stock, said that the update failed in recovery, I know I witnessed it on mine. Being on an ICS build, one would think that the update wouldn't even be downloaded.
yeah it is strange. Even if I force check for update on my Rez the update doesn't come. Are you sure your friend is telling you the whole story?
con247 said:
yeah it is strange. Even if I force check for update on my Rez the update doesn't come. Are you sure your friend is telling you the whole story?
Click to expand...
Click to collapse
I am said friend.
Durthquake sits in the cube next to me. He watched the whole event transpire.
Here's what happened and what was tried and the resolution,
Rezound reboots to the HTC screen. Won't show the think brilliantly words. Just stayed on HTC.
So I did a battery pull and rebooted phone and same thing. Just HTC.
Now I reboot to recovery, get hboot and try to do a wipe. It blinks like its going to try to go to recovery then turns off.
Do another battery pull boot maneuver and it does the same thing.
As we are at work I did have to work so I leave it on the stock wall charger for about an hour and try to turn on again. HTC screen so I leave it to see what happens, maybe I didn't wait long enough.
Like 35 minutes later screen goes black.
Now it won't power on, won't go to hboot, basically a brick. So I pull my battery give it to durthquake who gives me his rezound battery. His phone turns on, mine doesn't.
Now I try pulling sim, sdcard, and putting my battery back in. Still nada. Phone be properly bricked.
Bring it home put sim, sdcard, and battery back in and put on HTC wall charger overnight. In the am nothing. Still a pretty beats brick.
Go to vzw and the try charging turning on etc. Nada. They say since the ota they've had about 5 of these in.
The resolution is vzw sending me a new rezound and I buying a new phone so I can give the resound to my gf.
Sent from my Galaxy Nexus using Tapatalk
this is my second rezound. On the first one when the battery died it could no longer charge. i tried all chargers with zero luck. i was running stock with 1.02.605.6 with root and CWM. I exchenaged it and ran clean rom 4.1 w Amon Ra 3.15. I am now having the same problem. i bought another battery so i could atleast turn it on. what could this be?
PLS HELP
You are trying the AC charger that comes with the phone?
Via Rezound using XDA Premium
yes i have tried everything including the adapter that came with the phone.
Try a car charger, could be the amperage o draw.
i bought another battery and called verizon. They are sending me a new phone. for the return i need to get this thing back to stock from clean rom 4.1. if i re lock the bootloader and run GB RU. would i be good? will that take the boot loader back? radios?
It will still show it had once been unlocked, there is a thing on htcdev about it. You may get by or you may incur the charge back it depends on how close they (VZW employees) look at it after it scans in at the VZW warehouse, once it gets back to HTC too late to charge you back, but that is the first thing our friends at HTC look for.
Really strange battery experience last night. I've never had any problems with my phone.
Last night, I put my phone on the dock (EZO) around 1am. it had about 30% charge at the time... I saw the charge light on....
This morning, I looked expected to see green and saw no light at all. When I picked up the phone, it was cold... Turning the phone one didn't work.
Plugging the std charger it came with did nothing. No charge light at all.
I put my extended battery in, and the phone came up just fine. I then put the dead std battery into the back charger of the dock and left it for a couple hours as I got ready for work.
When I got to work, I put it into the phone and it had close to a 60% charge. I plugged in the charger at work and the charge light came on. Right now it is plugged in and approaching 90%.
Not really sure what happened last night. but apparently, when the bat loses all power, charging it via the phone may not work for some reason.
Paulb787 said:
i bought another battery and called verizon. They are sending me a new phone. for the return i need to get this thing back to stock from clean rom 4.1. if i re lock the bootloader and run GB RU. would i be good? will that take the boot loader back? radios?
Click to expand...
Click to collapse
NO, that would not work because your hboot is higher and the ruu will see that and fail.
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.
I'm going to try to be as specific as possible.
I had been flashing pretty much every third release of cm9 until the AOKP port came out a month or so ago. I was running the first aokp release until wednesday, at which point I switched over to the newest version. For each of the different ICS releases, I wiped, installed, rebooted, wiped cache, installed, gapps, rebooted, and never had any problems.
On the most recent install, everything was running smoothly and didn't have any problems. Last night, I put my phone on silent for a movie at about 8p. At about 11, I noticed my phone was dead while at a friend's house, so I plugged my phone in and walked away. I picked my phone up after I left, went home, and plugged it in again. I got the moto bootup, then it went to the battery splash, which showed 5%, and it immediately jumped to 100%. I rebooted, and it sits on the motorola screen. If I unplug it, it immediately dies; plugging it back in without hitting the power button takes me back to the battery splash, 5%-100% (the led changes colors as well).
So, I still have the rom and things on my sd card, so I reflashed, but it's doing the same thing. If i hit power, it gets to the moto screen, then black screen, then reboots. I'm using joker's recovery. If I plug the phone into my computer, I get a white LED, and no power, no found new device notice on windows, and nothing in device manager.
I'm sort of at a loss at this point. I think I could possibly use the microsd->sd adapter and put another rom on my phone's sd card, but that's about the only way I'll be able to transfer files.
tl;dr
1) Phone (running ics aokp, joker's cwm) died last night, will no longer charge
2) battery splash goes from 5%-100%, but the battery is actually dead
3) Can get into recovery, but the rom i flashed hasn't been bootable
If you guys have any ideas, I'd love to hear them. I think I'm going to try to throw a different rom onto the sd card, but I'm not sure why it would, or could affect the battery charging pre-boot.
Get a Spare battery from your friend and flash SBF.
Give a shot.
bondarun said:
Get a Spare battery from your friend and flash SBF.
Give a shot.
Click to expand...
Click to collapse
Yeah, I'm waiting until the sprint store opens so I can grab a charger.
Update: My sprint store no longer sells the photon, nor do they have a battery/external charger. I called sprint, and they're sending me a new phone. I'm just going to use the new battery to (hopefully) use rd and flash the sbf, then keep the new one.
Alright, so hopefully this will help if anyone has the same issue:
I borrowed a friend's battery and was able to flash the stock sbf onto my phone, relocking it. Even after that, I'm still not able to charge my battery; it still jumps from 5%-100% with zero charge.
When I called sprint, I just told them that the battery wouldn't charge, and I wasn't able to boot. They had me go into recovery (which at that point was still cwm for me, but I pretended to follow along with their steps) and factory reset. When I told them it still wasn't working, he put me on hold to talk to his supervisor, then said he was going to send me a replacement. I think I might have lucked out a bit, since I'm not within 100 miles of a repair center.
So I wasn't able to fix my phone, but at least when I send it back to sprint, it will be locked. I guess the fact that I'm getting a new phone is a bonus.
I had kind of the same issue, but being that my phone is out of warrant, am out of luck. Now I have to use an external charger or hope to be by a computer before my battery completely drains out :-(. I can still charge if I plug it into a USB port on a computer.
Has anyone figured this problem out I have the same problem just this morning.... I'm not anywhere near uss store ... I have tried 2 batteries and both do the same
OK so I went and got a dock for the batteries and after letting them charge and die again they seem to charge fine in the phone now.. very weird
Sent from my MB855 using xda premium
I've got a Rezound here that's s-off on HBOOT 2.28 and 2.23.10 radios. This is my problem:
A few weeks back I came home from work and plugged my phone in before I took a nap. The battery level was around 25%. After several hours on the charger the battery level had dropped to 14%. I pulled the plug and plugged it in again, the orange light came on indicating it was charging, but still, it did not charge. I powered off the device. Upon attempting to power up again, it simply wouldn't. I unplugged the device and pulled the battery out for a minute, put it back in. While off, I plugged it in. Orange light came on indicating it was charging. I attempted to power it up and it powered up, but still it would not charge even though the orange light was on and the OS showed it was charging off A/C. I powered it down again. Now the battery wouldn't charge with it off (no orange light on while off). So, I pulled the battery again. I put it back in a minute later, plugged the charger back in, and left it there off. It fully charged.
Basically, it will fully charge the battery while off after a fresh battery pull, but that is the ONLY way to make it charge the battery. This, to me, seems like a software issue, not a hardware issue, and if it's software there may be a fix for it (I hope), but I have no idea where to begin. I've flashed a new ROM, a different kernel, new radios, and even a new bootloader but the problem persists. I'm not sure where to go from here. Can anyone help me or point me in the right direction?
problem update
If anyone is interested in this issue, I've resolved it.
I suspected it was a software issue seeing as how the device would charge if it was off and the battery had just been put back in, and I was right. The fix came in the form of flashing new firmware to the phone. However, as a consequence of doing so, I lost LTE service. The fix I found to that wasn't in the Rezound forums that I could find. It was actually in the One M8 forums. Apparently partitions can become corrupted from time to time and HTC devices are somewhat known for this. The fix to the broken LTE service was to perform a factory reset in hboot with no custom recovery installed. Long story short: If your Rezound is experiencing charging issues and/or broken LTE service, it might be worth flashing complete fresh firmware and performing a factory reset in hboot.
It's probably important to mention that this device is S-off. I wouldn't try this S-on if I were you.
Hope this helps someone out.