My Rezzy was solid..and then I woke up - HTC Rezound

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!

Related

[Q] Bricked Thunderbolt? :(

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.

[Q] Issue with backlight

Hi all,
I am a proud owner of HTC Amaze, running BulletProof ROM with Faux Kernel v08.
The issue I am experiencing is most probably hardware issue, but I still hope it is not.
My backlight does not work at all. The phone works fine, and under heavy light you can see the actual screen, and can operate the phone as usual, but of course, otherwise, the phone is unusable, since you cannot see anything.
I've tried factory reset, restored to previous backup, charged it till full, left it without battery for few hours, nothing helped. Backlight is simply not there.
Soft buttons have the backlight, but not the screen.
There is a chance that it could be a battery issue (caused by phone), since it is my second battery, original one just died one day and refused to be charged. I got a new battery under warranty.
But even with a new battery it's been acting wierd. Random restarts after which the battery indicator would show red explanation mark. Had to take out the battery and reboot for it to work normal again.
It might be that my phone is defective and just kills batteries.
But in case of the backlight, the battery still charges normally (at least the indicators shows that it does).
Any idea what is going on with my phone? Had anyone experienced something similar? Could it be caused by software? Are there any hard reset options I can try?
And second question, if I will have to go to warranty, is there a way to relock the bootloader? And, I am sure I could find it, but if anyone has it handy, could you link me to a place where I can get the original WIND ROM and original Kernel?
What do you think are my chances of the warranty being granted?
Greg
Porcupine00 said:
Hi all,
I am a proud owner of HTC Amaze, running BulletProof ROM with Faux Kernel v08.
The issue I am experiencing is most probably hardware issue, but I still hope it is not.
My backlight does not work at all. The phone works fine, and under heavy light you can see the actual screen, and can operate the phone as usual, but of course, otherwise, the phone is unusable, since you cannot see anything.
I've tried factory reset, restored to previous backup, charged it till full, left it without battery for few hours, nothing helped. Backlight is simply not there.
Soft buttons have the backlight, but not the screen.
There is a chance that it could be a battery issue (caused by phone), since it is my second battery, original one just died one day and refused to be charged. I got a new battery under warranty.
But even with a new battery it's been acting wierd. Random restarts after which the battery indicator would show read explanation mark. Had to take out the battery and reboot for it to work normal again.
It might be that my phone is defective and just kills batteries.
But in case of the backlight, the battery still charges normally (at least the indicators shows that it does).
Any idea what is going on with my phone? Had anyone experienced something similar? Could it be caused by software? Are there any hard reset options I can try?
And second question, if I will have to go to warranty, is there a way to relock the bootloader? And, I am sure I could find it, but if anyone has it handy, could you link me to a place where I can get the original WIND ROM and original Kernel?
What do you think are my chances of the warranty being granted?
Greg
Click to expand...
Click to collapse
Well i am sorry to say i cant tell you whats wrong, but i can answer one of your questions. Yes, you can relock the bootloader, but it says "relocked". But if it is a hardware problem, being unlocked or relocked shouldnt matter, they should still warranty it for you.. if it is in fact a hardware issue that is..
Sent from my NRGized Amaze...
via xda premium
If you plan on sending in for warranty, there's no harm in using the ruu to go back to stock and seeing if in fact it is something with the software
mrmako777 said:
If you plan on sending in for warranty, there's no harm in using the ruu to go back to stock and seeing if in fact it is something with the software
Click to expand...
Click to collapse
I was just thinking the same thing. but he had mentioned he didnt kno where to get the original wind rom from. But ya, definately go back to stock and see what happens. If ur still having the problem, then i would bet its safe to say that is a problem with the phone not something you did.
As for the shipped Wind Mobile rom, you can find the RUU here:
http://forum.xda-developers.com/showthread.php?t=1335703
Rom||RUU|| Shipped Ruby ROM Collection
There is also a link in that thread to show you how to "relock" you bootloader.
Hope this helps. If you need help or run into any problems when trying to relock and go back to stock rom, just let me know man, ive had to do it on my phone too so ya, Good luck bro!
Sent from my NRGized Amaze...
via xda premium
Thanks all for the reply.
Well, finding WIND RUU wasn't a challenge at all . Thanks for the link anyways.
Never thought I would have to go back to that creature again.
I will give it a try. Also one of my work buddies has the same phone, so I'll swap batteries with him to eliminate another potential issue.
Even though we have the same phones and the same provider, he always jokes around by saying that I have a crappy phone (our old tradition, back from the time we had different phones). Well at last he might be correct
Porcupine00 said:
Thanks all for the reply.
Well, finding WIND RUU wasn't a challenge at all . Thanks for the link anyways.
Never thought I would have to go back to that creature again.
I will give it a try. Also one of my work buddies has the same phone, so I'll swap batteries with him to eliminate another potential issue.
Even though we have the same phones and the same provider, he always jokes around by saying that I have a crappy phone (our old tradition, back from the time we had different phones). Well at last he might be correct
Click to expand...
Click to collapse
Hah i was going to suggest that, but then i thought about it and if ur phone is for some reason frying batteries, then i figured u wouldnt want to try someone elses and then end up having to buy them a new battery lol
Sent from my NRGized Amaze...
via xda premium
aj_2423 said:
Hah i was going to suggest that, but then i thought about it and if ur phone is for some reason frying batteries, then i figured u wouldnt want to try someone elses and then end up having to buy them a new battery lol
Sent from my NRGized Amaze...
via xda premium
Click to expand...
Click to collapse
Well, it's not like it fries it instantaneously, it takes time and effort from my phone to do it
So if I'll insert it for few second to see if my backlight will come back, battery won't die, and I'll I know what's wrong with my phone, and that there is no point of me getting the third battery, since the same fate will be awaiting it.
In any case, if return to stock won't help, warranty is the only option, which is sad

[Q] Rezound Won't Turn On

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

Amaze won't turn on - stock

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!

Well.....that's that.

Verizon ran a special last night, LG G2 for free. I have been pining over this phone since getting one in my hands in the store, was just impressed. My Rezound has been the longest phone I've owned, but it's time is done. Late Nov 2011 until now.......an impressive stretch. But it's developed some issues recently that make me believe it's a goner. So the new white G2 is ordered and will be picked up tomorrow.
As for my rezound......if anyone is reading this......here's the issues it's developed, mainly after a particularly hard fall about two weeks ago. It was initially fine, but about 3-4 days later, it started boot looping out of nowhere. If I replace the battery it's hit or miss if it does it or not now. If it does, it could be 1-2 times, it could take over 10 minutes to get into the OS. Then in my car last week, I turned on Bluetooth (Chrysler Pacifica, has that Uconnect through the stereo) but it never fully turned on. Then two days ago the wifi quit picking up ANYTHING even though it says it's on. Now I notice the speaker (both headset and external) have gone very crackly.
I'm doubting it's software related, I think it's just been dropped one too many times. I'm going to try to reflash a stock kernel and factory ruu to set it back to stock (it's S-On, unlocked bootloader) and see how things work, but what are your guys opinion on whether or not that's worth my time?
Fastbird said:
Verizon ran a special last night, LG G2 for free. I have been pining over this phone since getting one in my hands in the store, was just impressed. My Rezound has been the longest phone I've owned, but it's time is done. Late Nov 2011 until now.......an impressive stretch. But it's developed some issues recently that make me believe it's a goner. So the new white G2 is ordered and will be picked up tomorrow.
As for my rezound......if anyone is reading this......here's the issues it's developed, mainly after a particularly hard fall about two weeks ago. It was initially fine, but about 3-4 days later, it started boot looping out of nowhere. If I replace the battery it's hit or miss if it does it or not now. If it does, it could be 1-2 times, it could take over 10 minutes to get into the OS. Then in my car last week, I turned on Bluetooth (Chrysler Pacifica, has that Uconnect through the stereo) but it never fully turned on. Then two days ago the wifi quit picking up ANYTHING even though it says it's on. Now I notice the speaker (both headset and external) have gone very crackly.
I'm doubting it's software related, I think it's just been dropped one too many times. I'm going to try to reflash a stock kernel and factory ruu to set it back to stock (it's S-On, unlocked bootloader) and see how things work, but what are your guys opinion on whether or not that's worth my time?
Click to expand...
Click to collapse
Are they discounting the full price on it too? I need to keep my unlimited.
As for the phone, what would you intend to do with it? They aren't worth much to sell, specially if it's damaged, if the screen is good, someone might take it off your hands for parts.
mjones73 said:
Are they discounting the full price on it too? I need to keep my unlimited.
As for the phone, what would you intend to do with it? They aren't worth much to sell, specially if it's damaged, if the screen is good, someone might take it off your hands for parts.
Click to expand...
Click to collapse
I don't know yet. I think I've still got my OG Droid hiding somewhere too.
I'm going to wipe it all and do a full factory ruu reflash and see if that doesn't help things out. I want to swap the outer bezel out because I closed my toolbox on it and ended up with a nice dent in the black chrome bezel. The LCD is fine, but I don't know about the digitizer considering the soft keys are really REALLY slow to respond anymore. I was thinking of rebuilding it for the fun and then I don't know. By rebuild I mean new circuit board because I think mine is the root of the issue. Won't know until after a factory reset, but the crackly speakers doesn't give me high hopes.
I really loved this phone. My biggest complaint was always the horrendous battery life. I have three batteries and could easily kill them all in a day with it. Guess I'm not done tinkering with it yet.
Hmmm.....looks like it may be getting sold for parts. It was bootlooping again tonight after I deactivated it and officially went full time to the G2. So I went into recovery (Amon Ra) and wiped everything, and did a recovery of a backup of Clean Rom that I'd done immediately after in install and setup back in July of 2012. And it's still boot looping. I get into the phone for just a few seconds, the SD card stuff tried to load, but neither Wifi or Bluetooth turn on. My guess is that the last couple of hard drops it took did the mainboard in. Good news is that I just pulled the Zagg InvisibleShield and the screen itself is freaking immaculate.
So I'm thinking one of two things. I could invest about $70 for a mainboard and a new outer bezel, see if that fixes it, and keep it as a spare phone. Or, just sell it as parts. I'm leaning towards a mainboard and bezel and just holding on to it, but I gotta say that I need to know if this is truly a mainboard issue or not.
Fastbird said:
Hmmm.....looks like it may be getting sold for parts. It was bootlooping again tonight after I deactivated it and officially went full time to the G2. So I went into recovery (Amon Ra) and wiped everything, and did a recovery of a backup of Clean Rom that I'd done immediately after in install and setup back in July of 2012. And it's still boot looping. I get into the phone for just a few seconds, the SD card stuff tried to load, but neither Wifi or Bluetooth turn on. My guess is that the last couple of hard drops it took did the mainboard in. Good news is that I just pulled the Zagg InvisibleShield and the screen itself is freaking immaculate.
So I'm thinking one of two things. I could invest about $70 for a mainboard and a new outer bezel, see if that fixes it, and keep it as a spare phone. Or, just sell it as parts. I'm leaning towards a mainboard and bezel and just holding on to it, but I gotta say that I need to know if this is truly a mainboard issue or not.
Click to expand...
Click to collapse
if after a full clean flash or even full factory restore you still have issues id lean towards hardware issues myself...and i hear you on battery life...i too have 3 batteries and the phone will die by the end of the day with it....i sold my daily rez for a different android but i still have my developer rez...which has been lately used for just that
I also just retire the rebound for similar reasons. I went with the note 3. Just picked it up yesterday. I was going to get the moto x to keep unlimited but was able to keep it with the N3.
I liking it so far. Not reboots or freezes. I think that is what finally got me. For the last few months, I could not get the red to run smoothly on any roms dating back to bean stock and maybe before. Gummy had worked great but for blacks screens that also happen on kitkat. I'm still keeping the red for roms as I am not going to root the N3.
Sent from my SM-N900V using Tapatalk
REV3NT3CH said:
if after a full clean flash or even full factory restore you still have issues id lean towards hardware issues myself...and i hear you on battery life...i too have 3 batteries and the phone will die by the end of the day with it....i sold my daily rez for a different android but i still have my developer rez...which has been lately used for just that
Click to expand...
Click to collapse
Yeah, the nandroid restore I did was, I think, CleanRom 1.4. But it was a totally clean install as I had installed it, set it up, and backed it up immediately. And it still just boots, gets into the UI, and about 30 seconds later reboots. I can't even get USB Debugging disabled so I can use Fastboot to relock the bootloader and flash an RUU.
I guess once my taxes come back in that I'll get a new logic board since ALL the modules seem to come with it (wifi, BT, etc) and get a new centerboard/outer bezel combo. Cost me about $70, but if I can get it up and running it'll be a nice backup phone. If anything, something to tinker with, lol.
Holy crap. I left it sit all night, and just turned it on and it booted! However, I try to turn Wifi on, and it just sits at "Turning Wi-Fi on......" so looks like wifi is definitely buggered. As it bluetooth.....same thing.
Just went into Settings and under Wi-Fi is says Error. Yep.....that's fubar.
It's SlimRom 1.6, just checked.
But the good news is that I now have USB Debugging enabled, so I can use Fastboot and relock and put a factory RUU on it. One last try, lol.
Fastbird, I had bought a used Rezound for my daughter over Christmas and when we tried it the wifi said the same thing as you stated, "turning on wifi". It would stay like that forever. I then went and put on ViperRez rom and then the wifi was fine. Not saying this will work for you as well but just a thought I had when I saw your problem. Good luck, hope it all works out for you.
Bryon
Fastbird said:
Yeah, the nandroid restore I did was, I think, CleanRom 1.4. But it was a totally clean install as I had installed it, set it up, and backed it up immediately. And it still just boots, gets into the UI, and about 30 seconds later reboots. I can't even get USB Debugging disabled so I can use Fastboot to relock the bootloader and flash an RUU.
I guess once my taxes come back in that I'll get a new logic board since ALL the modules seem to come with it (wifi, BT, etc) and get a new centerboard/outer bezel combo. Cost me about $70, but if I can get it up and running it'll be a nice backup phone. If anything, something to tinker with, lol.
Click to expand...
Click to collapse
you dont need to worry about usb debugging for an ruu....just boot to hboot and select fastboot and plug it in.....in my downgrade upgrade guide it will show all you need to do....the only thing you have to worry about with that is gaining s-off...an ruu wipes and reinstalls android completely...so any setting you set in rom will be wiped anyway....if wifi and all that still fails than it shows that the CleanRom is your issue....although downgrading and using the ruu.exe files require a locked bootloader and to be s-off
Also, the "turning WiFi on" issue, if it just stays like that, is usually an issue of a kernel/module mismatch... Remember when flashing a ROM or restoring a Nandroid when S-On you must flash the boot.img manually.
Sent from my Nexus 4 using Tapatalk
REV3NT3CH said:
you dont need to worry about usb debugging for an ruu....just boot to hboot and select fastboot and plug it in.....in my downgrade upgrade guide it will show all you need to do....the only thing you have to worry about with that is gaining s-off...an ruu wipes and reinstalls android completely...so any setting you set in rom will be wiped anyway....if wifi and all that still fails than it shows that the CleanRom is your issue....although downgrading and using the ruu.exe files require a locked bootloader and to be s-off
Click to expand...
Click to collapse
Now....I thought you had to be S-ON to run the RUU file? That crap-can's that idea then. I'm not S-Off. CleanRom isn't the issue. I ran a later version of it for 1.5 years, and the version I tried the restore from was 100% functional for me too. I don't think I'm going to bother flashing the phone as it sits because of the hardware issues. I'm just going to wait until I get a new logic board and then probably S-Off and play with flashing until I find something I like to sit on as a backup. The Screen is just too pretty for me to part with, lol.
Fastbird said:
Now....I thought you had to be S-ON to run the RUU file? That crap-can's that idea then. I'm not S-Off. CleanRom isn't the issue. I ran a later version of it for 1.5 years, and the version I tried the restore from was 100% functional for me too. I don't think I'm going to bother flashing the phone as it sits because of the hardware issues. I'm just going to wait until I get a new logic board and then probably S-Off and play with flashing until I find something I like to sit on as a backup. The Screen is just too pretty for me to part with, lol.
Click to expand...
Click to collapse
all ruu.exe files and ota.zips require s-off for downgrading..... ie. say your on an older version like 3.14.605.12 you can be s-on and upgrade to higher if im not mistaken...going s-off and redoing the whole phone from first to finish on ruu and ota's would be your last chance for that board without having to spend cash....and no offense you can probably get a used perfectly working rezound alot cheaper than 70 as well...is there any chance you deleted the wrong system files....only factory ruu will it restore original files...some deletions can cause these issues as well
The getting stuck turning Wifi on started BEFORE I tried a restore.
Shouldn't be a kernel mismatch because I used the same kernel for the nandroid CleamRom 1.6 and the other version of CleanRom I was running (I believe 1.7).
Only wiped Data, Cache, and dalvik cache. Several times for each.
The phone is acting EXACTLY like it was prior to the nandroid restore which is why I'm so sure it's a hardware issue. And I do mean exactly. 85% of the time after rebooting it boot loops for a random amount of time. Once booted in it's fine, save for Wifi and Bluetooth not working.
I understand I could get a replacement phone for cheaper to slightly more than te $70, but that's not the point. I like to tinker. I learn by doing. Gives me something to do.
Ok, relocked and trying to upgrade to a higher RUU which by what I read is acceptable. I flashed one of the earliest ICS firmware's and rom's, and the last RUU I could find was about 3 months later so I'm hoping it's good.f
*Edit* RUU took, trying to boot, but it's boot looping like normal. I think it's safe to say hardware is jacked at this point. It's getting into the UI then dying again, just like before.
Nappyloxs said:
I also just retire the rebound for similar reasons. I went with the note 3. Just picked it up yesterday. I was going to get the moto x to keep unlimited but was able to keep it with the N3.
Click to expand...
Click to collapse
How were you able to keep unlimited? My contract is over with my Rezound and I want to purchase a Galaxy S4. The best Verizon would offer me to give up my unlimited data is 6gb of data for $30.
Sent from my ASUS Transformer Pad TF700T using XDA Premium 4 mobile app

Categories

Resources