Related
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
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
Hi, uh I started another thread on making sure things got backed up. Which I did properly and everything was good. So today I haven't done anythign and was waiting for the new slim rom to make it's debute hopefully this week sometime as that is the one that appeals to me the most. Anyways, today my phone just got super hot, far hotter than before and it decided to die on me...I think. it shut off and I haven't been able to turn it on. Could this be a side effect of installing twrp/unlocking the bootloader/rooting? Or would it be a defective unit? One concern I had was getting a defective unit so i waited out my 30 days before even considering doing all this. So yea my 30 days from att is up. Would there possibly be a way to get a new phone from att or does anyone have any tricks on getting it back online? I personally think it was an overheating issue, but my phone is now cooled down.
So i went to the att store and of course they won't do anything. They told me to call some number they gave me. If I return it will they know it was boot unlocked and rooted? I can't turn it on at all. Using a power source or connecting to my computer nor my car charger...
blamster said:
Hi, uh I started another thread on making sure things got backed up. Which I did properly and everything was good. So today I haven't done anythign and was waiting for the new slim rom to make it's debute hopefully this week sometime as that is the one that appeals to me the most. Anyways, today my phone just got super hot, far hotter than before and it decided to die on me...I think. it shut off and I haven't been able to turn it on. Could this be a side effect of installing twrp/unlocking the bootloader/rooting? Or would it be a defective unit? One concern I had was getting a defective unit so i waited out my 30 days before even considering doing all this. So yea my 30 days from att is up. Would there possibly be a way to get a new phone from att or does anyone have any tricks on getting it back online? I personally think it was an overheating issue, but my phone is now cooled down.
So i went to the att store and of course they won't do anything. They told me to call some number they gave me. If I return it will they know it was boot unlocked and rooted? I can't turn it on at all. Using a power source or connecting to my computer nor my car charger...
Click to expand...
Click to collapse
Ok, so, im not sure if by return you mean, return for an exchange or simply a return as ATT will probably only send you a reman unit for yours and not allow an actual return. If you havent called them yet, i would recommend it. I have dealt with them many times in the past and one thing that has always shocked me is that they never have asked me about, or even commented on, how rooting or unlocking prevents them from exchanging it. Even during the disclaimer, they have never once said that if the device has been modified they wont allow the exchange.
I say all of this because should they not mention anything like that, and you send it back, im fairly sure you can claim you didnt know and werent told, and they will take care of it. Also, i say this because i personally sent back 3 bricked GS2s and an lg nitro as defective and got my reman units and every single one of them were rooted and such. So, i would feel safe. As long as they dont ask, and you dont lie to them, then there shouldnt be an issue. I wouldnt lie to them, i just dont mention it. AGAIN DO NOT lie to them or attempt to decieve them, i would never encourage that, but if its something they dont ask about, then, it, in my opinion, is not something that they are too concerned with.
cloudraker said:
Ok, so, im not sure if by return you mean, return for an exchange or simply a return as ATT will probably only send you a reman unit for yours and not allow an actual return. If you havent called them yet, i would recommend it. I have dealt with them many times in the past and one thing that has always shocked me is that they never have asked me about, or even commented on, how rooting or unlocking prevents them from exchanging it. Even during the disclaimer, they have never once said that if the device has been modified they wont allow the exchange.
I say all of this because should they not mention anything like that, and you send it back, im fairly sure you can claim you didnt know and werent told, and they will take care of it. Also, i say this because i personally sent back 3 bricked GS2s and an lg nitro as defective and got my reman units and every single one of them were rooted and such. So, i would feel safe. As long as they dont ask, and you dont lie to them, then there shouldnt be an issue. I wouldnt lie to them, i just dont mention it. AGAIN DO NOT lie to them or attempt to decieve them, i would never encourage that, but if its something they dont ask about, then, it, in my opinion, is not something that they are too concerned with.
Click to expand...
Click to collapse
Okay, thanks for the response. Sorry I was in a bit of a panic when I wrote that. But I have called ATT and they didn't ask me or mention in any disclaimer that if it's rooted or unlocked it won't qualify. I didn't mention it and so that does make me feel a lot better. Hasn't been physically damaged or come in contact with water so i'm pretty sure I'm safe. Thanks again.
blamster said:
Okay, thanks for the response. Sorry I was in a bit of a panic when I wrote that. But I have called ATT and they didn't ask me or mention in any disclaimer that if it's rooted or unlocked it won't qualify. I didn't mention it and so that does make me feel a lot better. Hasn't been physically damaged or come in contact with water so i'm pretty sure I'm safe. Thanks again.
Click to expand...
Click to collapse
They may or may not check when you return the phone. I returned my S3 a few months ago in exchange for a different phone but I forgot to unroot it and uninstall Superuser. The representative at AT&T didn't even turn the phone on. I didn't have anything to hide though, if they told me I couldn't return it because it was rooted then I would have sold it and purchased something else. I think the manufacturer is the one to worry about with these things. LG would definitely know if it were unlocked and they would be able to determine if rooting and unlocking the phone caused the problems you described.
johnbyebye said:
They may or may not check when you return the phone. I returned my S3 a few months ago in exchange for a different phone but I forgot to unroot it and uninstall Superuser. The representative at AT&T didn't even turn the phone on. I didn't have anything to hide though, if they told me I couldn't return it because it was rooted then I would have sold it and purchased something else. I think the manufacturer is the one to worry about with these things. LG would definitely know if it were unlocked and they would be able to determine if rooting and unlocking the phone caused the problems you described.
Click to expand...
Click to collapse
Well if they can turn it on I will gladly take it back due to them not accepting. I couldn't turn it on by anymeans, even plugging it in there is no lights to signifying it is receiving power. But i heard this phone had overheating issues in the first wave (or two) so it's probably for the best to get a new one. They are currently mailing me a new one and so I should receive it next week sometime hopefully.
blamster said:
Well if they can turn it on I will gladly take it back due to them not accepting. I couldn't turn it on by anymeans, even plugging it in there is no lights to signifying it is receiving power. But i heard this phone had overheating issues in the first wave (or two) so it's probably for the best to get a new one. They are currently mailing me a new one and so I should receive it next week sometime hopefully.
Click to expand...
Click to collapse
Sounds like everything worked out.
im in the same boat as you... completely dead phone. But I did open it to see of the battery pull would work. Do you think that theyll check and refuse my warranty because I opened it? the phone on the outside is NEW. Btw do you have a contract/account with ATT? I bought mine off ebay and used it on tmo...
I have the exact same problem! Totally dead phone that the charging light won't even turn on for. Unfortunately there is a small crack in the bottom left of the phone that was caused months prior so ATT wont give me a new one...
send it for repairs! I had rooted and unlocked mine so ATT didnt cover my warranty, but I only paid 50 bucks for the repairs and now I have my phone back!
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
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.