Hey, guys. I'm having a heating issue with my Rezound. It's on Newt's OneXxX RLS3 right now, 3.14.605.5 and his kernel, S-On, just flashed it this morning in the hopes it would fix my overheating issues, but no luck.
Last night, and from May 30th, I was on BAMF ICS 2.1, 3.11 firmware. I made a 15 minute call to my Mom, and went from 100% to 87%, and up to 123 degrees with alternating amber/green light.
Just a few minutes ago, spent about 10 minutes on the phone and playing on the net, and it was up to 110 degrees, and in 10 more minutes, went from 69% battery to 25%, so looks like Newt's didn't fix it either.
I need to know what I need to do to get it into a returnable condition. Do I need to re-lock the bootloader? If so (I assume so) will that be enough to get past Verizon, or do I need to return it to stock? Do they look at software numbers and stuff? I really don't want to have to S-Off the damn thing just to get it back to GB to return it.
I tried to call Verizon and have them send me a replacement, but the tech lady said I'd need to take it to a brick and mortar store to have them check it out. She said they would want to check out the battery, the charger, and the phone.
Ok, didn't get an answer so I went ahead and S-Off'd. Now where are the directions for reverting to GB....
First, please confirm you didn't run HTCDev Unlock again after S-off, at least tell me you kept stock bootloader or flashed the JB hboot lol. If you did, you'll need to redo the S-off process to get the "Unlocked/Relocked" flag to change back to "Locked". If you are worried about full stock appearance for warranty purposes.
Download the 2.01.605.11 GB RUU, preferably the PC .exe version since it can wipe stuff easier remotely.
http://forum.xda-developers.com/showthread.php?p=19756694
Glad you were able to accomplish S-off quickly, since you don't have much technical trouble you'll probably want to follow this guide to reset the S-on flag too: http://forum.xda-developers.com/showthread.php?p=25165453
Ah, crap. No, I forgot to install the jb_hboot. I've already installed this Rom: http://forum.xda-developers.com/showthread.php?t=1467329 but I still have Amon Ra. I'm locked, but still S-Off. Can I install the 2.01 over top of what I have already? And will it overwrite the recovery?
Danariel said:
Ah, crap. No, I forgot to install the jb_hboot. I've already installed this Rom: http://forum.xda-developers.com/showthread.php?t=1467329 but I still have Amon Ra. I'm locked, but still S-Off. Can I install the 2.01 over top of what I have already? And will it overwrite the recovery?
Click to expand...
Click to collapse
Well the point is actually that once you run HTCDev Unlock on the bootloader, only S-off magic can make the flag a stock "Locked" message. Relocking normally shows "Relocked" which still indicates tampering lol. Sounds like you are good if it is still "Locked" that is what you want.:thumbup:
Yes, run the RUU and it overwrites the ROM, the recovery, bootloader, radios, and factory resets the data. What it does not affect are the flags in the bootloader (i.e. Locked/Unlocked/Relocked and S-on/S-off) That RUU covers all warranty issues except S-off flag. To toggle to S-on, all your accessing past this point will be from the adb commands you have from HTCDev/S-off process if that is what you're wondering.
So yeah, from where you are just run the RUU, do Scotty's guide for the S-on flag. Just remember on Scotty's guide you must boot into the ROM after the RUU to toggle USB debugging in the settings. So go back into the bootloader after the guide and do a factory reset to cover those tracks lol.
Well, I managed to install the jb_hboot, but now there's no Recovery at all. And since I'm already on 2.01, the .exe is failing. I think I need to set Mainversion Low, but since I don't have a recovery...looks like I'll have to use the other file to flash it in the bootloader. I'll let you know how this goes.
Edit: Ok, I am now Locked, and S-On. However, it won't boot. When I go to turn it on, it boots to a black screen with a circle arrow and one in the middle pointing down over the picture of a phone. I managed to brick it, didn't I?
Edit 2: Ok, it's rebooting now...and we have Stock! I rebooted into the bootloader to verify LOCKED, S-ON, but there's still nothing when I try to go to recovery. IDC, that's good enough for me dammit. I'm through with it for the night!
(And thank the gods I remembered to uninstall my Blizzard Authenticator before I did all this crap...)
Danariel said:
Well, I managed to install the jb_hboot, but now there's no Recovery at all. And since I'm already on 2.01, the .exe is failing. I think I need to set Mainversion Low, but since I don't have a recovery...looks like I'll have to use the other file to flash it in the bootloader. I'll let you know how this goes.
Ok, I am now Locked, and S-On. However, it won't boot. When I go to turn it on, it boots to a black screen with a circle arrow and one in the middle pointing down over the picture of a phone. I managed to brick it, didn't I?
Click to expand...
Click to collapse
Soft brick. That is the stock recovery... Did you do S-on with the JB hboot and/or custom ROM? That could cause that per the warnings in Scotty's thread.
Edit 2: haha good deal, congrats. Yes, that is what stock recovery looks like, no alarm needed.
PhantasmRezound said:
Soft brick. That is the stock recovery... Did you do S-on with the JB hboot and/or custom ROM? That could cause that per the warnings in Scotty's thread.
Edit 2: haha good deal, congrats. Yes, that is what stock recovery looks like, no alarm needed.
Click to expand...
Click to collapse
Thank you so much for all your help!
The temp on this ***** is 121 Degrees Fahrenheit right now. She's going BACK tomorrow! Absolutely unbelievable. You know, come to think about it, my Thunderbolt had overheating/rebooting issues until I rooted it and got a custom ROM. I really hope I get a good one, this time, I'd hate to go through all this **** again.
Danariel said:
Thank you so much for all your help!
The temp on this ***** is 121 Degrees Fahrenheit right now. She's going BACK tomorrow! Absolutely unbelievable. You know, come to think about it, my Thunderbolt had overheating/rebooting issues until I rooted it and got a custom ROM. I really hope I get a good one, this time, I'd hate to go through all this **** again.
Click to expand...
Click to collapse
All phones are different, depends on how a person uses it. But the radio, charginig method, running apps, and likely hardware are all factors. http://forum.xda-developers.com/showthread.php?p=20138465 Worth skimming through. Some now have newer XE and unmarked hardware models which may have better temperature performance, time will tell. Could be worse... Just don't know if these hardware revisions address quality issues with heat, or are meant to reduce production cost. Probably both. Perhaps inconsistent from revision to revision; maybe a middle-aged model got cheaper but unexpectedly ran hotter. Need to be an HTC insider or get plenty of feedback to isolate the effect hardware revision has in the overall heat equation.
Edited for TL;DR-ness of anecdotal info. Good luck with the replacement.
PhantasmRezound said:
All phones are different, depends on how a person uses it. But the radio, charginig method, running apps, and likely hardware are all factors. http://forum.xda-developers.com/showthread.php?p=20138465 Worth skimming through. Some now have newer XE and unmarked hardware models which may have better temperature performance, time will tell. Could be worse... Just don't know if these hardware revisions address quality issues with heat, or are meant to reduce production cost. Probably both. Perhaps inconsistent from revision to revision; maybe a middle-aged model got cheaper but unexpectedly ran hotter. Need to be an HTC insider or get plenty of feedback to isolate the effect hardware revision has in the overall heat equation.
Edited for TL;DR-ness of anecdotal info. Good luck with the replacement.
Click to expand...
Click to collapse
LOL, Bacon Mode! Yep, that's my phone to a Tee. However, i'm not going to LET it get to 135 or 152 before I take it back. That's Extra Crispy bacon right there!
Related
So today my Rooted Eris running nonsensikal started just randomly shutting off. If I let it sit for 15 minutes or so I can turn it back on and get it to run for a while. I used one of my old, very stable nandroid restores and still had the same problem.
So... phone must go in for warranty. I have it back to 1.5 stock. My question is how do I get it upgraded to the latest OTA 2.1? I have the 2.36.605.1 RUU .exe but it won't work Won't reboot to bootloader and says there's a USB problem (there's not).
Thanks in advance.
Since you already have the phone back to 1.5, I'll suggest a strategy which minimizes the amount of flashing which needs to be done. Note also: the stock recovery partition must be installed on the phone for any OTA update procedure to work - it will not work if Amon_RA recovery is still installed.
If your phone is having hardware troubles, it is quite possible that your phone will "glitch" in the middle of a flashing operation, and you will end up with a brick. There is little you can do to prevent that from happening, so ... you want to do as few flashing operations as possible before you turn the phone over to VZW.
For that very reason, I will suggest that you do not use the 1.5 to 2.1 OTA upgrade - it takes a LONG time to run. If the problem that your phone is having is related to the phone warming up, you want something which runs quickly.
I'll suggest that you flash the Leak-V3 PB00IMG.ZIP ROM using the HBOOT method. You know the one, right?
- download the Leak-V3 "PB00IMG.ZIP" file to the root folder of the SD card
- charge the phone to 100%
- shut down
- reboot by holding down Vol-Down+End
- accept all the prompts as they occur.
This will get you back to 100% stock (prior to the July 17 OTA). If your phone dies in the middle of the July OTA update (which is quite a bit smaller and completes faster), no big deal, the phone has been wiped and only has factory code on it.
You mentioned something similar to "letting the phone sit" for 15 minutes. Perhaps you want to charge the phone to 100%, and let it sit for an hour or two before running any flashing operation, so that it will have cooled down as much as possible before you flash anything.
Please also educate us: there have been a few users who have literally burned up their Eris by incautious overclocking; what profiles were you using for overclocking, and what Temperature settings were you using for the Safety setting? Were you using the Eris for sustained tethering operations?
bftb0
Hey thanks for the reply!
In regards to your last question, I've been running it at 806 for a couple of months without issues. Yesterday morning I followed the guide here: http://forum.xda-developers.com/showthread.php?t=761940 and I ran into problems a few hours later. My settings were:
DEFAULT 19MIN---806 on demand
SCREEN OFF 19MIN---480 MAX on demand 95 priority
TEMP <40 19MIN---528MAX 90 priority
BATT <40 19MIN---604MAX
SAMPLING RATE---100000
UP THRESHOLD---98
ignore nice ---0
power save bias---0
I guess it's also noteworthy I installed SetCPU 2.0.2 yesterday morning as well.
I'm not blaming the OP of that thread, it doesn't seem others are having problems. I wasn't using tethering or anything out of the ordinary. Nothing but text messages and Facebook for the most part.
I have ran leak V3 before. My only question, I thought that changed the bootloader and the OTA didn't? Please correct me if I'm wrong, I don't want to get hit with a bill for the phone if they notice that lol
Also noteworthy, my phone was on a charger all night and didn't die! It was dying all day yesterday, regardless of charging status.
joebob213 said:
In regards to your last question, I've been running it at 806 for a couple of months without issues.
Click to expand...
Click to collapse
That's precisely what I was getting at. Because the supply voltage to the CPU is stepped up as frequency is stepped up, it generates a lot more heat when running at high clock rates. Way more than you would expect. There have been users over on AF that burned their phones up in as little as one week by aggressively overclocking. I wouldn't recommend to any of my friends that they OC an Eris to 806. (I have mine peaking at 729, and I have never even tried to see how high it would go.)
joebob213 said:
Yesterday morning I followed the guide here: http://forum.xda-developers.com/showthread.php?t=761940 and I ran into problems a few hours later.
Click to expand...
Click to collapse
Well, your first post indicated you were also having problems with "old, very stable nandroid restores" - I suppose that they were not OC'ed to 806, and also didn't have these new tweaks applied. So, there is no reason to believe those older ROMs would be affected unless physical damage had occurred to your Eris.
joebob213 said:
I guess it's also noteworthy I installed SetCPU 2.0.2 yesterday morning as well.
Click to expand...
Click to collapse
Same comment as above - why would a software change in one ROM affect the behavior of a completely different ( "old, very stable nandroid restores" ) ROM? If the 1.5 ROM is also crashing, remember that it isn't even overclocked!
joebob213 said:
I have ran leak V3 before. My only question, I thought that changed the bootloader and the OTA didn't? Please correct me if I'm wrong, I don't want to get hit with a bill for the phone if they notice that lol
Click to expand...
Click to collapse
You are correct that the OTA doesn't touch the bootloader, but if you have run the Leak-V3 before, doesn't that would mean that you already have the 1.49.000 S-ON bootloader on your phone? (unless you were you able to change the bootloader back to 1.47 when you "went back to 1.5").
In any event, you might be getting overly anxious about it for several reasons. While you are absolutely correct that a team of forensic experts hired by Verizon to examine your phone might be able to look up the date of purchase and customer history to determine that you shouldn't have the 1.49.0000 S-ON bootloader on your phone, the chances of them taking that kind of interest in your phone is essentially zero - they get thousands of returned phones every day (all makes and models). There have been posters on this forum that reported returning multiple rooted Eris without making any effort to clean them up, and were never contacted or charged by VZW. So, the chances of them taking an interest in your phone because it has a 1.49.0000 S-ON bootloader is pretty small, especially considering that they have been shipping phones for a couple of months now with that bootloader installed.
Still, if you want to try returning it to absolute stock, you probably need to perform Jcase's "Flash any RUU" technique (which modifies the "misc" partition so that you prevent those "Main Version is Older" lock-outs by the bootloader.) That would also allow you to use the PB00IMG.ZIP file from the MR2, along with Toastcfh's "battery pull trick" to only flash the bootloader.
The thing to bear in mind is that the OTA process relies on having a stock recovery partition and the exact version of HTC software that the OTA expects to be upgrading - you didn't say exactly what state your phone was in when you restored to 1.5. Does it have the stock 1.17.605.1 recovery installed, too? Manually downloading the 1.5 -> 2.1 OTA and installing it as an "update.zip" will work - so long as your phone doesn't decide to crap its' shorts in the middle of that update. And after that, one more OTA (July 2010) to put it back to "current" stock status.
But as I said, if you think your phone has bad hardware and could fail at any moment, doing a lot of flashing just increases the chances that you will have a disaster right in the middle of flashing. Flashing the Leak-V3 ROM takes about 5 minutes including the first boot; but applying the 1.5 -> 2.1 OTA takes considerably longer - it goes in and manually patches 600+ files. It burns less than 100 MB to the phone, but it spends a lot of time running when it does so.
joebob213 said:
Also noteworthy, my phone was on a charger all night and didn't die! It was dying all day yesterday, regardless of charging status.
Click to expand...
Click to collapse
I don't know that makes me feel any better. If it is crashing with 1.5 on it, it is damaged goods.
bftb0
bftb0 said:
Since you already have the phone back to 1.5, I'll suggest a strategy which minimizes the amount of flashing which needs to be done. Note also: the stock recovery partition must be installed on the phone for any OTA update procedure to work - it will not work if Amon_RA recovery is still installed.
If your phone is having hardware troubles, it is quite possible that your phone will "glitch" in the middle of a flashing operation, and you will end up with a brick. There is little you can do to prevent that from happening, so ... you want to do as few flashing operations as possible before you turn the phone over to VZW.
For that very reason, I will suggest that you do not use the 1.5 to 2.1 OTA upgrade - it takes a LONG time to run. If the problem that your phone is having is related to the phone warming up, you want something which runs quickly.
I'll suggest that you flash the Leak-V3 PB00IMG.ZIP ROM using the HBOOT method. You know the one, right?
- download the Leak-V3 "PB00IMG.ZIP" file to the root folder of the SD card
- charge the phone to 100%
- shut down
- reboot by holding down Vol-Down+End
- accept all the prompts as they occur.
This will get you back to 100% stock (prior to the July 17 OTA). If your phone dies in the middle of the July OTA update (which is quite a bit smaller and completes faster), no big deal, the phone has been wiped and only has factory code on it.
You mentioned something similar to "letting the phone sit" for 15 minutes. Perhaps you want to charge the phone to 100%, and let it sit for an hour or two before running any flashing operation, so that it will have cooled down as much as possible before you flash anything.
Please also educate us: there have been a few users who have literally burned up their Eris by incautious overclocking; what profiles were you using for overclocking, and what Temperature settings were you using for the Safety setting? Were you using the Eris for sustained tethering operations?
bftb0
Click to expand...
Click to collapse
That's what I did when I had my trackball ball problem and had to take my phone in
Sent from my FroyoEris using XDA App
I've followed all of the instructions. I'm stuck on android stock 1.5 and every time I try to get the leakv3 to run it doesn't recognize it or something, I've tried formatting my SD card and renaming it correctly but nothing.
I need to send in my phone in a couple of days, so I need this to get fixed....
please help.
EDIT: Nevermind, leakv3 finally working.
TheDoctor1177 said:
I've followed all of the instructions. I'm stuck on android stock 1.5 and every time I try to get the leakv3 to run it doesn't recognize it or something, I've tried formatting my SD card and renaming it correctly but nothing.
I need to send in my phone in a couple of days, so I need this to get fixed....
please help.
EDIT: Nevermind, leakv3 finally working.
Click to expand...
Click to collapse
Please report what you discovered so that others will benefit from your experience - corrupted PB00IMG.ZIP file?
bftb0 said:
That's precisely what I was getting at. Because the supply voltage to the CPU is stepped up as frequency is stepped up, it generates a lot more heat when running at high clock rates. Way more than you would expect. There have been users over on AF that burned their phones up in as little as one week by aggressively overclocking. I wouldn't recommend to any of my friends that they OC an Eris to 806. (I have mine peaking at 729, and I have never even tried to see how high it would go.)
Click to expand...
Click to collapse
I knew what you were getting at, I was answering your question.
bftb0 said:
Well, your first post indicated you were also having problems with "old, very stable nandroid restores" - I suppose that they were not OC'ed to 806, and also didn't have these new tweaks applied. So, there is no reason to believe those older ROMs would be affected unless physical damage had occurred to your Eris.
Click to expand...
Click to collapse
The nandroid restore I used was also overclocked to 806, albeit without the tweaks. If I didn't think it was a hardware issue. I wouldn't be wanting to send the phone in.
bftb0 said:
Same comment as above - why would a software change in one ROM affect the behavior of a completely different ( "old, very stable nandroid restores" ) ROM? If the 1.5 ROM is also crashing, remember that it isn't even overclocked!
Click to expand...
Click to collapse
Same comment as above.
bftb0 said:
You are correct that the OTA doesn't touch the bootloader, but if you have run the Leak-V3 before, doesn't that would mean that you already have the 1.49.000 S-ON bootloader on your phone? (unless you were you able to change the bootloader back to 1.47 when you "went back to 1.5").
Click to expand...
Click to collapse
Yes, the bootloader is back to 1.47.
bftb0 said:
In any event, you might be getting overly anxious about it for several reasons. While you are absolutely correct that a team of forensic experts hired by Verizon to examine your phone might be able to look up the date of purchase and customer history to determine that you shouldn't have the 1.49.0000 S-ON bootloader on your phone, the chances of them taking that kind of interest in your phone is essentially zero - they get thousands of returned phones every day (all makes and models). There have been posters on this forum that reported returning multiple rooted Eris without making any effort to clean them up, and were never contacted or charged by VZW. So, the chances of them taking an interest in your phone because it has a 1.49.0000 S-ON bootloader is pretty small, especially considering that they have been shipping phones for a couple of months now with that bootloader installed.
Click to expand...
Click to collapse
I remember leakers getting charged $400 on their Verizon bill after sending in their phones.
bftb0 said:
The thing to bear in mind is that the OTA process relies on having a stock recovery partition and the exact version of HTC software that the OTA expects to be upgrading - you didn't say exactly what state your phone was in when you restored to 1.5. Does it have the stock 1.17.605.1 recovery installed, too? Manually downloading the 1.5 -> 2.1 OTA and installing it as an "update.zip" will work - so long as your phone doesn't decide to crap its' shorts in the middle of that update. And after that, one more OTA (July 2010) to put it back to "current" stock status.
Click to expand...
Click to collapse
I got the phone back to bone stock 1.5, OS, recovery, bootloader, etc...
Now the rest of the story. My phone is working fine now! Saturday morning I was still running 1.5 but I hadn't been using the phone at all and it still hadn't died again. I did a *228 option 1 and after the phone rebooted I got the OTA notification. I went for it. It actually didn't take very long! 10 minutes maybe? The phone was running fine after that... for a few hours. When I was at work I had it plugged in all day but I used it quite a bit. About an hour before I went home the phone died. I booted it back up and unplugged it. As soon as I took it off the charger I got the "plug in your charger" message. Said battery was less than 2% charged! Anyway, I let it die and took it home. Plugged it in at home and as soon as I turned it on it said the battery was full! I left it there for a while, then went to my other job and the battery meter drained FAST! Like, 2 hours fast with very little use. I plugged it back in yesterday morning, let it fully charge, and I haven't had any issues since! I unplugged it at about 10:00 yesterday morning and I've still got about 75% of my charge now.
So I have no idea what the issue was lol. Phone and battery lost communication with each other?
I'm going to go ahead and keep it stock for a while just in case I have to send it in but everything seems to be working fine after the battery freak out!
Maybe the problem was the battery all along?
I would ask VZW if they will swap out a battery with you to see if the problem persists.
BTW, I hope you didn't think I was "talking down" you - I provided all those "extra" details because you didn't mention them. From across the Internet, it is impossible to know whether someone doesn't mention something because they are completely aware of the details (and consider them not worth mentioning) - or because they aren't aware of them. No doubt you've seen the wide range of sophistication that posts in here.
bftb0
Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Flash the stock Rom from scrosler's website.
www.scottsroms.com
Droidel said:
Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Click to expand...
Click to collapse
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
poppajules said:
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
Click to expand...
Click to collapse
The contacts are fine. what if the phone bricked during a software update in hboot? Can they still see relocked and tampered?
Some say that vz doesnt care as long as it has no physical damage.
I don't know about Verizon not caring, but I highly doubt they would take back all of our rooted phones..
I doubt the phone bricked if it booted up. I would flash the ICS RUU and see if the radios fix your signal issue.
Like I said before, I am running Scott's CleamROM and it sets the software versions to 1.0.0.0, so any RUU will flash over it. This is your best bet.
If VZW doesn't care about the bootloader, then you're golden, but don't count on that.
If I may pry, why are you sending it back for the replacement? If it's because of the radios, then I really doubt they are going to just take the phone back, since you could have messed up software to cause the issue.
Just try flashing some stuff before you call it busted. I would go with the ICS leak, Scott's CleanROM, and then back to your old RUU if you want. There's also a patch you have to install to downgrade from CleanROM and ICS leak back to GB, so you might want to do research, also. If you need help finding stuff, just send me a PM.
p.s. Anyone can boot your phone to bootloader (unless of course your phone is in little tiny pieces all over the street), and see that the bootloader is unlocked, possibly tampered for the custom recovery installed, and even if you lock it again, it will say relocked, indicating to everyone that it has been unlocked at one point. 'Unlocked', 'Relocked', 'Tampered', and 'Security Warning' void certain parts of your warranty (in the words of HTC dev.com). The only thing that doesn't void it is if it reads 'Locked'. Period.
Some say that vz doesnt care as long as it has no physical damage.[/QUOTE] Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
ghostt021 said:
Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
Click to expand...
Click to collapse
Yeah, I've never tried to send a rooted phone back, personally, but I've never asked anyone at VZW about it. (I'm paranoid that SWAT will descend from the roof and take me down if they knew my phone was rooted)
Good luck dude, just box it up and ship it off then. 'F' 'em.
No go, reflashed ICS leak, the tamper and security warning are gone.
I don't understand why it's not letting me switch to CDMA only. It goes back to CDMA/LTE. Could a bad SIM card cause 3g issues?
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
poppajules said:
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
Click to expand...
Click to collapse
I noticed this happeneng a day prior to flashing the ICS leak. I was using wifi tether do download about 600mb's and notice a couple of hours later that it dropped to 1x. Restarted phone and it went to 4g. I usually switch to 3g to save battery, that's when i notice the problem.
The ics leak flash didn't show any errors.
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Droidel said:
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Click to expand...
Click to collapse
Make SURE you are pulling the PH98IMG for the stock RUU from the android police website, NOT Scott. He didn't post up the new leak. The RUU that Scott has will NOT flash over the old ICS stuff he's put out before.
Go here to get the leaked RUU.
In this process, relock your bootloader, flash the file from A.P.(TWICE, this is important), unlock your bootloader with your unlock token from htcdev, and THEN flash what scott has. It's a time consuming process. It's up to you though. The directions are out there on A.P., Scott's website, all over Scott's thread around the 400-page range for the 4.0.1 release... and my abbreviated directions here.
Grab one of the top three selections, not the pre-rooted version.
also, try going back and re-downloading your ROM file, maybe you got a bad download.
If you upgraded to ics, you can't ruu to gingerbread at all because of the older hboot. But you can flash a gb kernel then a Rom or nandroid+ scrosler sdcard fix
Sent from my ADR6425LVW using xda premium
So, long story short, took the Phone into Sprint so they could look at my headphone jack (was cracked and left ear bud would constantly cut in and out) because its acting up.
Gave the Tech the phone without the battery in it (since he didn’t need to power up the device to clearly see the headphone jack has a huge crack in it) but I left my SD card installed. As he was walking away, I asked him if I could remove my SD card and he let me, then seen that I gave him the phone without a battery. So, I ended up giving it to him (praying he didn’t turn it on and see ViperBoys sick ass ROM booting up) and he accidently pressed the power button turning the phone on. Promptly short after, he removed the battery when the phone was on the HTC screen, didn’t even get the boot animation. I was like OHH $h!t, that gonna mess up my phone & sure as $h!t, it did… Just loops in and out of that screen resetting each time with a little vibrate then looping.
I can get into Fastboot and use ADB, I’ve flashed RUU’s, put Stock image on root of SD and let recovery restore (losing my CWM & my HBOOT 1.400), unlocked, relocked, wiped, thrown, and screamed at it with no luck.
I did do a CWM backup before even setting foot in the Store, so I do have a backup. The 1st thing I tried was restoring it through CWM recovery and that didn’t stop the looping. I can still get into fastboot via power + vol down and adb functionality is still there.
HBOOT is 1.50 and s-on is enabled..
Been reading through threads since lunch and tried many different solutions without success. It seems once a phone is this far gone, people stop responding.
Anyone have any ideas?
New phone will be here tomorrow (free of coarse courtesy of Sprint insurance) but I’ve been without a phone all day and most of yesterday. I’d like to get this one back to stock and booting before I trade it in for the replacement tomorrow
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
yousefak said:
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
Click to expand...
Click to collapse
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
lessegr said:
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
Click to expand...
Click to collapse
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
yousefak said:
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
Click to expand...
Click to collapse
BUMMER! In case the question comes up I ran "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed" and it ran just fine.
Hmm, hardware issue. Dont see how I can check for that if it doesnt boot.
Guess I'll just have to wait for the new Phone
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
jdeoxys said:
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Click to expand...
Click to collapse
The HTC unlock went as expected. Followed the directions to the "T", then relocked, checked in fastboot (not that I could check anywhere else, LOL) and the phone says "*** RELOCKED***". Ran 2.17.651.5 RUU successfully to the finish. Still looping
WEIRD!
DarkManX4lf said:
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
Click to expand...
Click to collapse
Because I just want to know WTF happened!!! Had this Phone since release, abused\used the hell out of it by flashing ROMs constantly, restoring backups, tethering like crazy, emailing, texting, FBing...
No reason for it to crap out on me from a simple mistake, not even of my responsibility, lol!
The only issue I've had with this Phone is that damn headphone jack 1/2 way failing..
Got new phone, terrified to even think about trying to flash new ROM though
lessegr said:
Got new phone, terrified to even think about trying to flash new ROM though
Click to expand...
Click to collapse
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Threevo said:
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
DONT TEMPT ME DAMMIT! lol! Just been without a phone for almost 3 days. I'm also seeing a lot of new threads about people experiencing what I've gone through.
Woops, sprint\HTC! once again rooted, and running viperROM.... SWWWWWET!
HBOOT 1.5 and s-on is a *****!
Not to mention... But in Linux, I never got revo recovery to flash... You can do it in windows just do it via fastboot.
Took my Orig cwm bsckup "recovery" & "boot" .img and threw them @ the phone via command prompt.
After cwm was restored, I restored my 4\29\2012 backup that I made before I entered the Sprint store, now my phone is back to the exact same way
It was. Pretty Damn sweet!
So much info here!! I'm truly thankful!!!
Sent from my PG86100 using xda premium
So I was on SOS Rom with Chad's linux 3 kernel and did the wire trick. I got s off, yay!!!!
So, now my wifi stinks, 3g stinks, my touch screen was affected, I have slight dead areas. I can't flash kernels, but I can flash boot screens. Totally not worth the trade off, lol. I have tried CWM, 4Ext, fastboot and flash image GUI. None work
Anyone have any ideas WTF is going on? Or what I need to do? I was thinking about using google to find out how to get s on and try the wire trick again, or just stay s on.
Would I need to flash a firmware from Frieza to possibly fix the kernel issues? I have no idea how that would help at all, lol.
If anyone else has had issues like this,.what did you do?
XDA senior techs, any ideas?
Not saying the wire trick stinks, just saying I ran into an issue I cant figure out
Sent from my PG86100 using XDA
Well I'm deeply sorry for your issues but I also believe that the issues your experiencing is not totally related to the "wire trick".
The effects of the wire tricks can't do much damage because the voltage going out of the pin#1 is not enough to cause massive effects with the small amount of time you make contact with ground.
Questions :
what kind of wire did you use?
How long did you place the wires in full contact?
I would say as well that disclaimers are posted and there are risks with following any prodcedures written in this site.
Try flashing a RUU and see what happens, perhaps that could be a way out?
Sent from my PG86100 using Tapatalk 2
Nametaken said:
So I was on SOS Rom with Chad's linux 3 kernel and did the wire trick. I got s off, yay!!!!
So, now my wifi stinks, 3g stinks, my touch screen was affected, I have slight dead areas. I can't flash kernels, but I can flash boot screens. Totally not worth the trade off, lol. I have tried CWM, 4Ext, fastboot and flash image GUI. None work
Anyone have any ideas WTF is going on? Or what I need to do? I was thinking about using google to find out how to get s on and try the wire trick again, or just stay s on.
Would I need to flash a firmware from Frieza to possibly fix the kernel issues? I have no idea how that would help at all, lol.
If anyone else has had issues like this,.what did you do?
XDA senior techs, any ideas?
Not saying the wire trick stinks, just saying I ran into an issue I cant figure out
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Oouch! I hope there is a fix for you, I'm sure you are going to try everything.
I don't know how to fix this but I do know a little bit about electronics. Actually quite a bit. Sounds like this trick shorted out or caused a voltage spike internally. Generally when an electronic component is damaged, there is no fix.
When you let out that factory installed smoke, you can't get the Genie back in the bottle.
I had a laptop once where the fan stopped working. I bought a new one. New one was not getting any voltage. A friend of mine was sitting at the bench with me. He decides lets just find another spot with same voltage and tap in there. Starts jumping wires around on the mother board and poof -- $1,000 dollar laptop on sale for parts on Ebay. Took me a long time to get over that one.
I was just looking around and found a problem similar to yours, in the "wire trick" thread. http://forum.xda-developers.com/showthread.php?p=26390751
Yeah... I totally noob bombed that dev thread so o started up a qna here lol
Sent from my PG86100 using XDA
Just a little more info. I can flash other kernels, but on sense Roms, it just shows up as the same name as the other stock kernel. I was able to fully flash other roms, like AOSP. Once I flash AOSP, I can see the other kernels I flash.
Flashing AOSP:
While I can flash it and other kernels, I get stuck on being able to activate my phone on the device. It gets stuck saying airplane mode is on. Totally sucks. Haven't tried activating online or by calling sprint. I have been busy with family stuff.
If anyone else has issues, post em up! Perhaps we can all help each other out
Sent from my PG86100 using XDA
So Here's what I ended up doing. After wire trick got me the S-Off, I had that ICS HBoot and thought hey, maybe this has something to do with my weird AOSP issues (for background please see my post in the CDMA developers section in the JBear thread), so I flashed my 2.17 RUU that I had handy. After that, I updated PRL and Profile (hoping this would do something). Then to my surprise, everything was stock again, bootloader read hboot 1.5.0 again instead of the 1.57 one, however no root because it's an RUU! Anyway, I kept reading through the thread like some of these folks told me, however I didn't find much, I did see that most people with success were using the JBear GB version. So, I flashed the jb_hboot from the GB version (I actually took another guy's advices and simply renamed the jb_hboot.zip file to PG86IMG.zip, this worked! Got me the Jbead modified GB bootloader on 1.50. SO I guess since we're S-Off, I was able to go back to hboot 1.50 and then did a fastboot flash recovery recovery.img and flashed the Ext4 recovery image I had. From there, I restored the nandroid I had (Nocturnal ICS Xi36 r105) and it all booted up fine. Later I will try flashing back to CM9 and see what happens, perhaps I'll be able to get out of this "sort of Airplane mode" that isn't really airplane mode (where the phone htinks it's deactivated.)
The key here is that while I was on GB RUU, I updated PRL and Profile, then went to the 1.5 hboot hoping that would be enough for the CM 9 rom and other AOSP ICS roms to activate upon install. I'll keep you posted.
Thanks for starting this thread man, we need a place to sort all this out. With all the info that floods the OPs of development threads, it's hard to really find what is even relevant. So, glad to see one in the Q and A that we can ask questions.
Well what i can say is that after trying the wire trick my device would randomly turn off and stop working. No charge, No light. Nada. Completely dead then it would randomly come back to life. Anyways. I took my phone to sprint today and ill be going back in two hours to see what the problem with my phone is.
I personally think its a hardware issue. Maybe i used a bad wire? Or i touched the wire during the process which is known to mess up your device.
Thinking about it . I don't see why people don't downgrade instead of the wire trick.
Update- Sprint told me my device had hardware issues and will send me a new phone within 4 days.
There is a possibility that, as someone else has pointed out, that we are indeed hurting our phones. Not so insulated wires, paperclip with tape etc, is the culprit. Too much static getting in and possibly hurting our phones. Something to think about.
To RUU Paul, lol,
I was thinking of uprooting using a similar method like you and gaining root again to ensure it isn't permanent. While it seems you could make it back, this could mean it is a software issue then, but it is too early to tell. Hopefully we cab get enough of the anomalies in to pin point this.
Sent from my PG86100 using XDA
cmbaughman said:
Anyway, I kept reading through the thread like some of these folks told me, however I didn't find much, I did see that most people with success were using the JBear GB version. So, I flashed the jb_hboot from the GB version (I actually took another guy's advices and simply renamed the jb_hboot.zip file to PG86IMG.zip, this worked! Got me the Jbead modified GB bootloader on 1.50. SO I guess since we're S-Off, I was able to go back to hboot 1.50 and then did a fastboot flash recovery recovery.img and flashed the Ext4 recovery image I had.
The key here is that while I was on GB RUU, I updated PRL and Profile, then went to the 1.5 hboot hoping that would be enough for the CM 9 rom and other AOSP ICS roms to activate upon install. I'll keep you posted.
Thanks for starting this thread man, we need a place to sort all this out. With all the info that floods the OPs of development threads, it's hard to really find what is even relevant. So, glad to see one in the Q and A that we can ask questions.
Click to expand...
Click to collapse
Thanks for pointing this all out! I can confirm that doing this allows us to flash back to AOSP with Airplane mode off and get it all up and going.
Once in there, you can change out your kernel and see that it is changed under About Phone! I loves you so much!
Now, if anyone has a way to verify if a kernel was changed or not, we can see if my idea was right about it flashing the kernel, just not showing the correct name of the kernel that was flashed
Thank you all the effort you guys have put into this. I too ran into this issue, and simply flashing the GB hboot resolved my issue. Just so everyone knows, that it is not necessary to revert to stock first. Just simply flash the other hboot, and you should be good to go.
If we go ahead and HTC Dev Unlock, and then the lte gets s=off, will we be able to either flash everything completely back to stock and get s=off, or will we be able to just achieve s=off using the the method and write over the htc dev unlock?
The question of whether we can undo HTCDev unlocking isn't really an issue, it will almost certainly be done and figured out by the time / if somebody figures out a true S-OFF method. The only real sticking point with HTCDev for most people is the fact that your phone's serial number gets recorded (and your bootloader says "relocked" if you do revert but that's something that will probably be fixed eventually).
But in the end, who knows what the future will bring? You can already RUU back to stock in every sense except the bootloader label.
My guess is somebody will get their hands on an engineering hboot sooner or later and this will all get sorted out.
My only worry is for Sprint's TEP, but I also did read somewhere that they are taking in rooted devices, so I'm guessing it shouldn't be an issue anyway?
ghostyroasty said:
My only worry is for Sprint's TEP, but I also did read somewhere that they are taking in rooted devices, so I'm guessing it shouldn't be an issue anyway?
Click to expand...
Click to collapse
Sprint couldnt care less if you rooted your device. As long as you take it back to stock before you bring it in they usually dont care at all...