I've looked through a few threads here and on other websites regarding the Rezound not turning on. I can't find one that matches my situation.
My wife's Rezound went completely dead last night. She remarked in bed that the battery was only 5% and that she didn't want to get up to plug it in. It of course would not turn on this morning. After being plugged in all day it still would not turn on. I pulled the battery for 5 minutes and replaced and still nothing. Holding Power+Volume Down for 30 seconds does nothing. This is where I started searching online.
Attempting adb reboot does nothing as it said device not found. I saw on another thread that the Rezound battery will fit in the Thunderbolt. I was thinking was I in luck since I have a Thunderbolt. I but the Rezound battery in, plugged it in and charged it to 60%. But when I put it back in the Rezound I can't get it to turn on.
When I plug in the Rezound the indicator lights do not come on at all, even for a brief second. I saw in one thread that the issue may be attributed to CWM recovery. But I have only put on Amon Ra since we got the Rezound a few months ago. The ROM is CleanROM Developer Edition.
At this point I am at a loss of what to do and will greatly appreciate any help.
try a diff battery same thing happen to mine
The battery appears fine as it charged OK and worked fine in the Thunderbolt. And I tried my Thunderbolt battery in the Rezound and it didn't work.
take to verizon and say it dont turn on
I will do that tomorrow. Will I have any problems though since the warranty is technically voided since I unlocked it? Say for example they can't get it to turn on with a new battery and want to swap it and they later determine it was unlocked. Will they come after me?
If your using CWR that is why its a problem with that recovery use amon ra. You need to put another battery in not the thunderbolt one try another charged Rezound battery and it should work then switch to amon ra and you'll be good.
Sent from my ICS Rezound
LakerStar25 said:
If your using CWR that is why its a problem with that recovery use amon ra. You need to put another battery in not the thunderbolt one try another charged Rezound battery and it should work then switch to amon ra and you'll be good.
Sent from my ICS Rezound
Click to expand...
Click to collapse
He said he was using amon ra
Sent from my ADR6425LVW using XDA
werdna87 said:
He said he was using amon ra
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Oops I guess I missed that. Lol
Sent from my ICS Rezound
Wonder if its older amon ra?
Sent from my ICS Rezound
hawkeyejoe said:
I will do that tomorrow. Will I have any problems though since the warranty is technically voided since I unlocked it? Say for example they can't get it to turn on with a new battery and want to swap it and they later determine it was unlocked. Will they come after me?
Click to expand...
Click to collapse
Well technically you didn't void the warranty by unlocking, look at the HTC Dev notice that pops up before you unlock, but if you flashed something that made the phone not turn on then it is your fault and you have voided the warranty. Simply put, if you unlock and cause no harm to the device the warranty stays intact but if you unlock and break the device then you are held accountable for what you did.
If it won't power on at all, no matter what, they will give you a replacement, but if you can't get it to power on and you send it back to HTC and they get it back on and see it was your fault then you are going to be pinned with a fee.
i had no trouble returning mine when it did not turn on
LakerStar25 said:
Wonder if its older amon ra?
Click to expand...
Click to collapse
I don't know the exact version but it was the latest version when I flashed it a couple months ago. Everything has worked perfectly till now.
Quick question, does the camera store pictures on the SD card or on internal memory? If Verizon gives me a replacement I'm sure my wife will want her pictures.
hawkeyejoe said:
I don't know the exact version but it was the latest version when I flashed it a couple months ago. Everything has worked perfectly till now.
Quick question, does the camera store pictures on the SD card or on internal memory? If Verizon gives me a replacement I'm sure my wife will want her pictures.
Click to expand...
Click to collapse
I am using CleanROM 4.3 and the photos are stored in the SD card. Screen shots are stored in phone memory.
Sent from my Dell Streak 7 using Tapatalk 2
hawkeyejoe said:
My wife's Rezound went completely dead last night...
Click to expand...
Click to collapse
Plug it in via USB and wait a few minutes. The charging light may or may not flash on for a moment but it will definitely not remain on.
After it's gotten a bit of charge into it, what should happen is that the phone boots into a non-interactive recovery session so that the battery charge daemon loads to control the charging process, as these are fairly sensitive batteries and it's not just a simple matter of "apply power, wait until full" any more.
At this point, leaving the phone plugged in via USB to your computer, attempt to discover the device via adb in the normal way you do ... Try adb devices, or just adb shell. If this doesn't work, you are hosed, go to Verizon, get a new battery, and don't drain your phone to 0% on a custom recovery.
If you DO get into adb shell check and see if your battery is getting any juice at all, by running:
Code:
dmesg | grep BATT
You should see something like ...
Code:
<6>[ 1450.207743] [BATT] htc_batt_get_battery_adc , vref:18602, battid_adc:1087, battid:58
<4>[ 1450.208751] at 1450138728391 (2012-04-17 12:08:10.428736531 UTC)
<6>[ 1450.211802] [BATT] ioctl: battery level update: 9 at 1450141963254 (2012-04-17 12:08:10.432825887 UTC)
<6>[ 1450.212138] [BATT] ID=2, level=9, vol=3750, temp=231, curr=399, dis_curr=0, chg_src=1, chg_en=1, over_vchg=0, batt_state=1 at 1450142359983 (2012-04-17 12:08:10.433161580 UTC)
<6>[ 1450.212596] [BATT] power_supply_changed: battery at 1450142848264 (2012-04-17 12:08:10.433619344 UTC)
What you're looking for in one of those lines is the "level=#" where you can see mine is sucking along nicely at 9% (guess who else did this a couple nights ago? lol.)
At this point, you CAN issue a reboot directly from the shell, your phone will boot into your ROM and the battery charging will be handled by the main system and you're fine.
What happens when you plug it in, unplug it, power down, hold power down, and whatever else you were trying to do is that the phone gets "stuck" in that non-interactive recovery kernel (if it even started it) which then drains the battery back to zero again. Stock CWM doesn't come with the battery daemon so it won't charge and you're SOL at this point. Amon Ra should so you hopefully can get enough charge into the battery to boot the full system. However, it also should recognize the keycodes when you tried to reset it, as it comes with those daemons as well (also CWM does not.)
Leave it plugged in while you try all this, and good luck.
hawkeyejoe said:
I don't know the exact version but it was the latest version when I flashed it a couple months ago. Everything has worked perfectly till now.
Quick question, does the camera store pictures on the SD card or on internal memory? If Verizon gives me a replacement I'm sure my wife will want her pictures.
Click to expand...
Click to collapse
Yea they save to SD card sometimes you might have go to camera settings to manually set it to save to SD sometimes not. I'm using amon ra 3.15
Sent from my ICS Rezound
Mine did the same thing if u can figure out how to charge the battery in another device i.e charging your battery in a thunderbolt enough to get it to boot you are good. I still called verizon and reported the problem, they are sending me one out over night. Dail *611 from a verizon device that will get u over to a rep. Easy peezy. Don't worry about unlocked bootloaders and what not as long as there is no excessive physical or water damage u are fine. I know for a fact that is what they check for. You have to remember this is verizon you are dealing with, not HTC
Sent from my ADR6425LVW using Tapatalk 2
Update: I went to a Verizon store (actually just an authorized reseller) to have it checked out. They had no luck, even with a new battery. The guy said that since the light doesn't even flash it is probably toast. I told him I couldn't even get adb to recognize it. He advised that I go to a Verizon corporate store or call support.
Since the closest corporate store is over 100 miles away and I'm not headed that way any time soon I called Verizon support. I'm surprised at the lack of a fight they put up when I explained in detail everything I tried and requested a new device. It will be here Friday.
I just hope that when I ship the old phone back they don't figure out that it was unlocked and bill me for the new phone or something like that.
So Friday night I'll have the joy or unlocking a new Rezound all over again! It's a really nice device and I am jealous. My wife won't take my Thunderbolt though.
Thanks for the replies everyone!
hawkeyejoe said:
Update: I went to a Verizon store (actually just an authorized reseller) to have it checked out. They had no luck, even with a new battery. The guy said that since the light doesn't even flash it is probably toast. I told him I couldn't even get adb to recognize it. He advised that I go to a Verizon corporate store or call support.
Since the closest corporate store is over 100 miles away and I'm not headed that way any time soon I called Verizon support. I'm surprised at the lack of a fight they put up when I explained in detail everything I tried and requested a new device. It will be here Friday.
I just hope that when I ship the old phone back they don't figure out that it was unlocked and bill me for the new phone or something like that.
So Friday night I'll have the joy or unlocking a new Rezound all over again! It's a really nice device and I am jealous. My wife won't take my Thunderbolt though.
Thanks for the replies everyone!
Click to expand...
Click to collapse
They are really good about taking returns and I wouldn't worry about them charging you. Many people have returned relocked before
Sent from my ADR6425LVW using XDA
hawkeyejoe said:
Will they come after me?
Click to expand...
Click to collapse
FWIW I exchanged mine early in March, been five weeks so far since they recieved my phone. Just checked and nothing unusual on my bill yet (other than a charge for 25 cents on my unlimited txt plan, but I digress )
PhantasmRezound said:
FWIW I exchanged mine early in March, been five weeks so far since they recieved my phone. Just checked and nothing unusual on my bill yet (other than a charge for 25 cents on my unlimited txt plan, but I digress )
Click to expand...
Click to collapse
If the charge is 25 cents for finding an unlocked phone, I don't think anyone will complain
Sent from my ADR6425LVW using XDA
Related
This time I have really f***ed up guys. I really think this time I have actually bricked my Thunderbolt. I was on Bamf Remix 1.63 I believe and everything was running great. I was obviously rooted also. I was bored and decided to flash Protekks Battery Sipper Kernel. Right after I flashed it, the phone would not boot. I pulled the battery and booted up again and it got stuck in a boot loop. So after a few tries I finally got it to boot into the bootloader. I got into recovery and tried to flash a backup and it rebooted in the middle of restoring it. I tried that a few more times. I then let the battery die. Then I charged it up a lot and tried to power it on and got nothing. The screen will not even turn on. When plugged into my computer it sometimes vibrates and my computer detects it and then my computer makes the sound like it was disconnected. I think it is still stuck in the boot loop with the screen off though. BTW the charging light does light up when plugged in. I tried the stock and extended battery to make sure it was not a battery problem. I finally called up Verizon and after I told them it would not turn on he said he is shipping me a free replacement. I told them that after a OTA update the phone would not boot. He warned me that if there is any evidence that the phone was rooted or hacked, I would be charged the retail price for the phone. That is really the only thing I am scared of. Any help would be greatly appreciated!!! Sorry for the long post, I wanted to get in all the details that I could.
Thanks
Adam
Try putting it in download mode and flash back to gongerbread using odin
Sent from my GT-I9000 using XDA Premium App
srkoza said:
Try putting it in download mode and flash back to gongerbread using odin
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Wtf? This isn't Samsung. OP do you bootloop in bootloader? I recommend you go to the irc and give them any info you can.. you will probably end up flashing a stock ruu through the bootloader but first go to irc.
Sent from my ThunderBolt using XDA Premium App
Thanks for the quick reply! How would I get into download mode. And I was on froyo before.. Shouldn't I download a froyo based rom?
Yeah I did not think we have Odin for HTC phones, and I already have the stock zip file on my MicroSD card but my screen will not turn on at all. I can not get into anything. Any advice?
Talk to jcase. Hopefully you have some adb knowledge.
Sent from my Thunderbolt using XDA Premium App
itsdubai said:
Yeah I did not think we have Odin for HTC phones, and I already have the stock zip file on my MicroSD card but my screen will not turn on at all. I can not get into anything. Any advice?
Click to expand...
Click to collapse
Go to irc.. someone with actual Dev experience can help you there try #thunderbolt
Sent from my ThunderBolt using XDA Premium App
OK thanks for the replies. Do you think the Verizon warranty center people will actually go to the trouble of getting it to work and then charge me full retail for a new one if they see it is rooted. I already have the stock zip on the SD card so when it does boot up, it will return everything to stock. I have read online that some people have been charged retail because there phones have been rooted but most of them have gotten away with with it..
itsdubai said:
OK thanks for the replies. Do you think the Verizon warranty center people will actually go to the trouble of getting it to work and then charge me full retail for a new one if they see it is rooted. I already have the stock zip on the SD card so when it does boot up, it will return everything to stock. I have read online that some people have been charged retail because there phones have been rooted but most of them have gotten away with with it..
Click to expand...
Click to collapse
I think you're almost certainly fine. It's a lot of work and time for big red over one phone. Plus, your etf is less expensive than a replacement device
Sent from my Thunderbolt using XDA Premium App
thanks for the response man. etf= early termination fee? I might not have said in my original post but they are sending me a free replacement device. The rep on the phone specifically said that if they find my phone to be rooted or hacked, that I will be charged around 629$ for the refurb replacement. I really cannot afford that (
Call back and tell em you accidentally dropped it out of moving vehicle and that it was run over 5 times...and that it was raining outside. Then pay your deductible.
ddgarcia05 said:
Call back and tell em you accidentally dropped it out of moving vehicle and that it was run over 5 times...and that it was raining outside. Then pay your deductible.
Click to expand...
Click to collapse
I decided that if I ever bricked, that I'd post on here asking what horrible things I should do previous to sending it in to get a replacement. Then post pics. XD
Sent from my Thunderbolt using XDA Premium App
Please check out this thread when you get a moment, might help the community and we would greatly appreciate it.
http://forum.xda-developers.com/showthread.php?t=1130407
Sent from my ADR6400L using XDA App
I got out of a bootloop on my friend's Insipre 4G (which is very similar to the TB) by mounting the microSD on my computer, and then putting a stock ROM on it. I had to rename the stock ROM PG98IMG (PG05IMG on Thunderbolt), and flash it through the bootloader, but it did work.
Thanks for the post man but the Thunderbolt does not show any signs of life at all besides the flashing orange LED at the top blinking and the computer detecting it on and off every 5 minutes. The stock zip is already on the SD card so when it finally boots up it will flash and hopefully Verizon won't charge me out the @ss for a replacement.
powered on! for a second...
UPDATE: I just had it hooked up to my laptop and it booted on the the white HTC screen and I almost had a heart attaack :O but then it powered off and wont come back on. FML
itsdubai said:
UPDATE: I just had it hooked up to my laptop and it booted on the the white HTC screen and I almost had a heart attaack :O but then it powered off and wont come back on. FML
Click to expand...
Click to collapse
how long have you had your phone and what hardware revision was it? did you try to run the RUU yet?
i think some people just got a batch of faulty phones because this doesn't seem to affect many.
I highly doubt verizon is going to receive your broken phone and boot it up and it will magically work. The only way it will auto-update is if they boot it into HBOOT. If they somehow just power it on it won't automatically apply anything. Keep that in mind. But I really wouldn't worry too much about it. If they charge you call them and tell them wtf I wasn't rooted. I don't even know what that means lol.
I have had the phone since the very first days it was released. Another slight annoying thing I have had happening prior is the glue on the screen has not been holding it down very well and and I can easily get a nail under it. And it wont let me do anything. I have a Droid X as a backup for now but I miss my beast
itsdubai said:
I have had the phone since the very first days it was released. Another slight annoying thing I have had happening prior is the glue on the screen has not been holding it down very well and and I can easily get a nail under it. And it wont let me do anything. I have a Droid X as a backup for now but I miss my beast
Click to expand...
Click to collapse
that's what im starting to think as htc has since released a revision 2 thunderbolt. i know as i just bought mine a few weeks ago. im wondering if the faulty phones were version 1 phones and have since been fixed. i also do not experience the high battery drain most of you guys do either.
So, yesterday morning this all went down. My Rezound has been nothing but an expensive paperweight. I am not new to the rooting game so save the nonconstructive comments.
Early Monday morning I felt the need to change things up a bit so I wanted to flash the latest CleanRom 3.7 to check it out (coming from BAMF v.09). I backed up all my apps & data and continued to make a nandroid backup (with Amon_Ra 3.14). After that, I completed the necessary wipes (including boot because Scott packages his roms with the kernel) in recovery and then flashed CleanRom 3.7 (MD5 sum matched) then booted into bootloader to flash the kernel. Everything went perfect with that.
After the phone booted I realized how low on battery I was on but connected to Wi-Fi during the initial start-up on the new rom. I got all my accounts and data synced/restored and was getting ready to knock out. I set my alarm, placed the phone on the wall charger and confirmed it was charging by the orange light around 3am.
I woke up yesterday morning around 7:30am and realize I'm running late. I pick up my phone to see if the time is correct and I get nothing but a black screen. Pulled the battery...nothing...plugged in the phone without the battery..then plugged in the battery...nothing. On my 45 minute commute to work I removed the battery and let the phone sit (hoping some magic would happen lol) and nothing changed.
When I made it to my office, I plugged the phone in to see if it would accept a charge and 2 hours later nothing. I have the 3.7v battery and have had no indications of a bad battery (short life, warm, etc.). Due to the circumstances, I was left with no choice but to go to the local VZW and order a replacement.
The guy at the Verizon store plugged my phone in the wall charger and saw it was not accepting a charge. Swapped the battery with his own personal Rezound and mine worked in his, however, his fully-charged battery would not work in mine. Narrowed it down to the phone itself which blows. I thought at worst it would be the battery.
I am really curious how/why this all went down of all times when I wasn't doing anything to my phone. You guys/gals have any idea?
Marcismo55 said:
and continued to make a nandroid backup.
Click to expand...
Click to collapse
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
My bad..I forgot to mention I have been running Amon_Ra from the start. I've never ran CWM on my Rezound and I did run across some threads regarding the charging issues associated with CWM.
Thanks though!
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
mpalatsi said:
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
Click to expand...
Click to collapse
Yes. All the contacts were intact and free of dirt/debris.
pkopalek said:
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
Click to expand...
Click to collapse
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
More than half of all the roms out there are from ports/leaks. Please explain.
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
nosympathy said:
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Actually I didn't even take the SIM out. Maybe I should have given that a try.
EmerikL said:
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
Click to expand...
Click to collapse
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
That's only for charging when you're booted into recovery if I'm not mistaken...
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
If flashing killed it, it would have never booted back up...
Marcismo55 said:
Actually I didn't even take the SIM out. Maybe I should have given that a try.
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
Click to expand...
Click to collapse
In my case when the Verizon rep gave me the phone he put the sim in and put it in backwards. To be fair, it does go in "backwards" to every other android phone I have owned haha.
Sent from my ADR6425LVW using XDA
mjones73 said:
That's only for charging when you're booted into recovery if I'm not mistaken...
Click to expand...
Click to collapse
It may depend on how you're charging. The charging process requires some intelligent oversight - if you power off the phone, and connect a charger, the process is controlled by code loaded from somewhere. I think that code is in, or loaded by, the recovery. That would tend to explain things like this, this, this, and this.
jayochs said:
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
Click to expand...
Click to collapse
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Marcismo55 said:
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Click to expand...
Click to collapse
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
^This. Even if it is new hardware there can be defects. **** happens!
Marcismo55 said:
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Click to expand...
Click to collapse
I assessed your OP as related to a phone not charging.
I see what you mean, now. My points were in the case of non-charing, or failure to charge (and a phone going dead on the charger) which aren't things I've seen on any stock-based ROM, but very much so on ICS ROM's (and Kernels, as such).
I bid you good luck on your replacement hardware. Stuff happens!
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
I understand Scott. I am in now way shape or form saying flashing your ROM was the reasoning behind all this as I have flashed numerous times before this and had no issues. Also, considering I am one of the very few this has happened to, i think its pretty obvious this was a hardware failure. I
I'll be running your roms soon enough
Thanks to everyone providing insight on this situation. I'll be back at it again very soon!
As stated in the title...my wife's Amaze 4G is completely stock. The other day it started having trouble charging, so I charge her battery in my phone. Now the phone will not turn on at all. All contacts look ok under the back cover and no water damage. Any ideas?
I know there are already posts here for this situation, but in all the thread i've read, they have modified the phone and created new issues. This is COMPLETELY STOCK. Running official ICS update.
waltm78 said:
As stated in the title...my wife's Amaze 4G is completely stock. The other day it started having trouble charging, so I charge her battery in my phone. Now the phone will not turn on at all. All contacts look ok under the back cover and no water damage. Any ideas?
I know there are already posts here for this situation, but in all the thread i've read, they have modified the phone and created new issues. This is COMPLETELY STOCK. Running official ICS update.
Click to expand...
Click to collapse
Try unplugging everything connected to the phone, removing the battery, and then hold the power button for around 15 seconds, then reinsert the battery. Try turning it on again. I'm sure there are other things you can try doing, but this is the first thing that comes in my mind.
waltm78 said:
As stated in the title...my wife's Amaze 4G is completely stock. The other day it started having trouble charging, so I charge her battery in my phone. Now the phone will not turn on at all. All contacts look ok under the back cover and no water damage. Any ideas?
I know there are already posts here for this situation, but in all the thread i've read, they have modified the phone and created new issues. This is COMPLETELY STOCK. Running official ICS update.
Click to expand...
Click to collapse
Since it stopped turning on have u tried her battery in your phone or your battery in hers? Maybe its just her battery gone bad, which is very common
sent from my NRGized Amaze,
powered by faux kernel v.10
So does her battery run your phone? If it does then its not the battery, return it under warranty, I dont think there's anything else you can do
Tried the trick with pulling the battery and hitting power, no dice. Doesn't matter which battery is in either, it won't turn on. All I want to do at this point is have it on long enough to get any useful data from the internal storage.
And stupidly, I DID NOT opt in for the protection plan thru TMO.
waltm78 said:
Tried the trick with pulling the battery and hitting power, no dice. Doesn't matter which battery is in either, it won't turn on. All I want to do at this point is have it on long enough to get any useful data from the internal storage.
And stupidly, I DID NOT opt in for the protection plan thru TMO.
Click to expand...
Click to collapse
You could try removing the battery, then putting the battery back in, and then plug the usb cable to the computer (so the amaze and the computer is connected to each other), and then try turning it on.
This probably won't turn on the phone, but if you do see something on the computer, something like its trying to install drivers, then you MAY have a chance.
waltm78 said:
Tried the trick with pulling the battery and hitting power, no dice. Doesn't matter which battery is in either, it won't turn on. All I want to do at this point is have it on long enough to get any useful data from the internal storage.
And stupidly, I DID NOT opt in for the protection plan thru TMO.
Click to expand...
Click to collapse
you don't need the protection plan, that will cover you if you lose it/break it etc. You should have 1 yr warranty, so taking it back shouldn't be a problem. How long have you had the phone? Its still not a year old yet..
Ok, I'll contact HTC. Thank you all for your suggestions
Yup HTC is your only option, T-Mobile doesn't cover if you don't have insurance.
Sent from my SGH-T999
Dark Nightmare said:
Yup HTC is your only option, T-Mobile doesn't cover if you don't have insurance.
Sent from my SGH-T999
Click to expand...
Click to collapse
Not true. Depends on how long they have had the phone
sent from my NRGized Amaze,
powered by faux kernel v.12
aj_2423 said:
Not true. Depends on how long they have had the phone
sent from my NRGized Amaze,
powered by faux kernel v.12
Click to expand...
Click to collapse
I think the time he has had the device is pretty obvious by now.
Dark Nightmare said:
I think the time he has had the device is pretty obvious by now.
Click to expand...
Click to collapse
Lol, not really. He never stated how long he's had it. And if he's had it less than a year (which is the case for everyone since the phone is less than a year old) he can call T-Mobile and they will most likely send him a new one and have him send his back. All I'm saying is that u saying T-Mobile won't do anything for u if u dont have insurance is not true.
sent from my NRGized Amaze,
powered by faux kernel v.12
aj_2423 said:
Lol, not really. He never stated how long he's had it. And if he's had it less than a year (which is the case for everyone since the phone is less than a year old) he can call T-Mobile and they will most likely send him a new one and have him send his back. All I'm saying is that u saying T-Mobile won't do anything for u if u dont have insurance is not true.
sent from my NRGized Amaze,
powered by faux kernel v.12
Click to expand...
Click to collapse
If it's past the 30 days, they'll tell him to call HTC directly if he doesn't have insurance, how I know this? Read past post about phone replacements with no insurance, it's a lucky few who get replacements from T-Mobile despite being past that thirty day period, HTC one year warranty is not upheld by T-Mobile, if anything happens to your device past the thirty days, they always ask or check if you have handset insurance coverage, js since even when I spoke to a rep about replacing the battery on my old amaze, which was merely two months old, he told me since I didn't have insurance on it, I'd have to call HTC directly since it was still under the one year warranty but my sister called about her g2x that didn't have insurance and wasn't even bought from T-Mobile about 6months old and got a replacement in like 5 minutes without any hostile arguments, just a simple my device isn't working and they sent her a replacement, understand where I'm getting at?
Hey guys, just to clarify...we got our phones in May 2012. And I'm pretty much screwed at this point now that my wife let my 3yr old play with it thinking it was totally fried. She threw it and cracked the display. I had a chance at having HTC diagnose it as an internal issue; now they are gonna think it was a user issue.
waltm78 said:
Hey guys, just to clarify...we got our phones in May 2012. And I'm pretty much screwed at this point now that my wife let my 3yr old play with it thinking it was totally fried. She threw it and cracked the display. I had a chance at having HTC diagnose it as an internal issue; now they are gonna think it was a user issue.
Click to expand...
Click to collapse
O no man! That sux! Ya, pretty much screwed that sux
sent from my NRGized Amaze,
powered by faux kernel v.12
aj_2423 said:
O no man! That sux! Ya, pretty much screwed that sux
sent from my NRGized Amaze,
powered by faux kernel v.12
Click to expand...
Click to collapse
In my opinion you have two choices here:
1) You could still try to talk to HTC. Explain to them that it was not responding before the screen got cracked and see where it gets you
2) Go to a local repair shop and get the screen/digitizer replaced. It shouldn't cost you more that a 100 bux. Then talk to HTC for the possible internal issue.
Hope that helps!
So today as I was preparing to flash the latest AOKP rom at 90% battery, I accidentally hit reboot to bootloader instead of recovery. No problem, i hit reboot. The screen turned black and a minute later it was still black, so I removed the battery. Nothing turned it on, couldn't access the bootloader and the charging light wouldn't even go on.
That was odd, so i thought maybe it was just still in bootloader mode. I gained access to ADB and it doesn't see the device at all (yes i tried the method explained because of the CWM problem, I also do not have CWM and have had a battery die before and it was able to charge fine) I also tried fastboot and it just sits at "waiting for device"
I called up Verizon support figuring it was the battery and they said i could test it at a store. The rep didn't think it was the battery, but when he tested it said 3/3 times it was increment, so it was bad. Then when he tried a regular battery it didn't work either, so he said the phone was bad.
Now, i called support and they are sending me a new phone and i am going to exchange my extended battery for a good one tomorrow. The thing is the lady on the phone said that as long as there were no hardware defects or unauthorized software than there wouldn't be any charge but if there was then it would be a $200 charge added onto the bill. A $200 charge would be pretty bad.
I would never return my phone if i messed it up actually doing something to the phone but here it didn't... at least not in any way I can think of. I am worried about the charge though. I know they usually don't check them but I had the Juopunut bear h-boot and neo's ICS installed. I am not even sure if it's recoverable at all because from everything i tried it definitely wasn't.
Am i just being silly here?
If they can't even boot the phone, then there is no way that they can tell it was hacked.
Sounds like the only way they'll get the phone booting is to do the manufacturer RUU thing with their special tools, so I'd say you're in the clear.
I've sent a phone back that was S-OFF running CM9. If they check before they JTAG it, I've seen no evidence of it.
I had heard before many times that they never checked, but i was extremely surprised whenever she said that. I wanted to ask some of you guys your opinion as well. I doubt it's recoverable without a full sbf as well, so i should be fine. Thanks!
Reaper0294 said:
I had heard before many times that they never checked, but i was extremely surprised whenever she said that. I wanted to ask some of you guys your opinion as well. I doubt it's recoverable without a full sbf as well, so i should be fine. Thanks!
Click to expand...
Click to collapse
I had to send mine back for a screen hardware issue. I was still s- on with the bootloader saying relocked and I did not get hit with that charge. As stated before I have heard of people sending back their phones with different ROMs without issue. Good luck
Sent from my Rezound using xda app-developers app
I've returned multiple devices saying relocked in the bootloader. I think Verizon simply doesn't care to be honest.. Hell I've even gotten a replacement phone that was rooted and running custom software. Shows you how muc hattention they pay to the devices they recieve and send out. Hell I've gotten replacements with screen protectors still on them and big ass gashes/scratches on the screen. 100 point inspection my ass.
Same here; my first Rezound was S-OFF, bootloader unlocked when the USB port failed (the unit would charge but couldn't connect to PC). I just factory reset it and sent it back. The folks who refurbish the phones don't even turn 'em on, and if they did, they probably wouldn't know what they were looking at. The things are bulk reflashed, if the motherboards are even retained at all.
Gonna copy my post from the CM11 thread here for more people to see:
I experienced perhaps the strangest problem today I've ever encountered with my phone.
Today I was using my phone just fine. Went out to eat with friends. Sat down and the restaurant and took my phone out to show them something. Hit the unlock button and the soft key lights came out, no screen. Hit it again, they went out, hit it again, they came back on, still no screen.
Assumed it locked up, I pulled the battery, put it back in, and phone would just show the HTC logo and then nothing. Figured the phone was dead so I threw it on my car charger.
An hour later, same thing. Booted to recovery looking for my CM11 download file. Mysteriously vanished from both internal and external storage. So I hit reboot to see if maybe rebooting from the recovery would change anything.
No OS installed. What? How did it just vanish? I haven't touched anything recently.
This is that phone I had just gotten from warranty too.
On a side now, this is a good time to mention I'm jumping to the Note 4 as soon as it releases.
Edit: I can't just reinstall a rom like I was hoping. It only needs to last 2 more damn weeks for the Note 4. UGH!!! It tells me /cache /data /system /devlog and emmc storage are unable to be mounted. What the hell could have happened to cause this?
Edit 2: Was gonna try reinstalling the RUU but apparently I can't because I didn't do s-off this replacement device yet. Can't relock bootloader because fastboot won't connect. Any ideas??
You should be able to download and flash a ph98img.zip from hboot, just find the right one. I would link you, but I'm on my phone right now with no access to those bookmarks.
You got a slim chance with a ph98img honestly... Since it can't mount ANY partitions, the partition table is probably corrupt meaning only JTAG or a reload via an EXE RUU in dowload mode has any chance of fixes it, and that's a 50/50 chance at best but since your S-ON that isn't possible. Best bet is to beg/borrow a VZW phone from someone for a couple weeks, even if it's a dumb phone... Or get a cheapo prepaid phone and have Verizon forward your number until you get the Note 4, then sell the prepaid phone.
Thanks guys. I assumed it was totally dead anyway, sucks that I forgot to S-OFF while I could have... at least would have given me a chance to fix it. Sucks.
Also I hear a rattling sound inside the phone, presumably the memory breaking off somehow? I'm careful with my stuff, and I especially know I didn't slam the phone or anything since I had just used it before this happened, but it can't be a coincidence that this rattling started when all the partitions vanished.
Edit: Do you guys think I should attempt to get it replaced at Verizon? The reason I'm so worried about that is that since it doesn't boot I'd assume the first thing they'd check is if the bootloader loads, see the tampered flag, and then charge me for the replacement despite it being a physical issue.
Hobox10 said:
Thanks guys. I assumed it was totally dead anyway, sucks that I forgot to S-OFF while I could have... at least would have given me a chance to fix it. Sucks.
Also I hear a rattling sound inside the phone, presumably the memory breaking off somehow? I'm careful with my stuff, and I especially know I didn't slam the phone or anything since I had just used it before this happened, but it can't be a coincidence that this rattling started when all the partitions vanished.
Edit: Do you guys think I should attempt to get it replaced at Verizon? The reason I'm so worried about that is that since it doesn't boot I'd assume the first thing they'd check is if the bootloader loads, see the tampered flag, and then charge me for the replacement despite it being a physical issue.
Click to expand...
Click to collapse
Asurion or Verizon? If Verizon I would say no, although rooting/romming probably didn't cause this, they will say it did... Asurion is an insurance, they don't care if its rooted or not.
acejavelin said:
Asurion or Verizon? If Verizon I would say no, although rooting/romming probably didn't cause this, they will say it did... Asurion is an insurance, they don't care if its rooted or not.
Click to expand...
Click to collapse
Verizon.
Hobox10 said:
Verizon.
Click to expand...
Click to collapse
I wouldn't try it... Although, you get a few weeks to return the phone, so you could get a replacement, use it for two to three weeks, then get your Note 4 and return the phone Verizon had sent you as a replacement instead of your broken Rezound. It might be slightly questionable ethics, but it should net you a temp loaner as long as nothing happens to it.