Related
So I've ran into a new issue. Just got my replacement phone from VZW, the trackball quit on my old one, and it came with 2.1 already installed. I didn't think much about it until I went to root the phone.
I've tried the first edition PB00IMG.zip and the more recent link from Ivan on XDA and with both files, when I boot the phone holding vol dn and end, I get the following error msg:
Main Version is older!
Update Fail!
Do you want to reboot device?
<Action> Yes
I've also tried the MR2 RUU downgrade method, but it failed too. Anyone have any ideas on how to root the phone?
boostlover said:
So I've ran into a new issue. Just got my replacement phone from VZW, the trackball quit on my old one, and it came with 2.1 already installed. I didn't think much about it until I went to root the phone.
I've tried the first edition PB00IMG.zip and the more recent link from Ivan on XDA and with both files, when I boot the phone holding vol dn and end, I get the following error msg:
Main Version is older!
Update Fail!
Do you want to reboot device?
<Action> Yes
I've also tried the MR2 RUU downgrade method, but it failed too. Anyone have any ideas on how to root the phone?
Click to expand...
Click to collapse
Sorry dude, you can't root. you now have the same problem as the people with the leak versions. The boot loader on your phone of higher than the one on the root rom.
Verizon has been sending some replacement phones that have the "wrong" HBOOT on them and users aren't able to root. Sounds like you got one too...
Was this shipped to you or an in-store exchange ? Seems to me that stores might have older, non-updated phones in stock, but I could be wrong.
It was shipped, go figure. So there's no way around it? :[
Not with that phone. Same problem people (who installed a leak) have been having for many, many weeks now...
Do you think its possible that since so many leakers have swapped their phones like scum bags that verizon is refurbing them and not flashing them back to stock?
Erris Bueller said:
Do you think its possible that since so many leakers have swapped their phones like scum bags that verizon is refurbing them and not flashing them back to stock?
Click to expand...
Click to collapse
If we can't get them back to stock bootloaders, no one can
hallstevenson said:
Verizon has been sending some replacement phones that have the "wrong" HBOOT on them and users aren't able to root. Sounds like you got one too...
Was this shipped to you or an in-store exchange ? Seems to me that stores might have older, non-updated phones in stock, but I could be wrong.
Click to expand...
Click to collapse
Its not "Wrong," HBoot 1.49 is just what Verizon is shipping all of their New Eris's with. Check the latest Verizon RUU that Conflipper released
Erris Bueller said:
Do you think its possible that since so many leakers have swapped their phones like scum bags that verizon is refurbing them and not flashing them back to stock?
Click to expand...
Click to collapse
EDIT: nevermind, I checked OP's post history. Sorry, bro. That sucks.
Spencer_Moore said:
If we can't get them back to stock bootloaders, no one can
Click to expand...
Click to collapse
spencer, technically, verizon and htc, and probably even google can return the phones back to whatever version they want, its just a matter of if they want to make the ROM and bootloader that will allow that.
And of course, they are not going to willingly do that for us, since that allows us to root the phone, which they dont want. they would rather have us keep the phones on an unrootable version.
That sucks dude. Strange enough my trackball on my eris is not working in one direction but I guess I'll just get use to it since I love root.
I loved having root too, looks like I'm up s***creek without a paddle though.
Damn that sucks man!!!!! Mine were shiped overnight from Texas and both had 1.5. Crap luck man. Just pray your trackball goes out again and it probably will.
Unfortunately my friends EVO 3D's digitizer is going insane and randomly selecting things on the screen. He needs to take it in but I'm not sure how Sprint will handle it with it being S-OFF and all. I can return it to a unrooted ROM but I wouldn't want to mess with the HBOOT etc if I didn't have to.
Has anybody taken their EVO 3D in with S-OFF and got repairs done on it?
They will work on phones with s-off as long as you are on a stock rom. Actually, most of the time the techs wont even check to see if you are s-off, but just at least return to the latest stock rom
I work at a preferred service and repair store and we haven't even received parts for the 3d yet. We have been told soon. I'd assume that they will ae (advanced exchange) it for you. Just to be sure I'd unroot. But many have said they send phones back all the time rooted.
My wife just had the screen replaced on her Evo4G, which was rooted, had one of Miks roms installed, and the splash screen was changed. They didn't say anything.
sitlet said:
They will work on phones with s-off as long as you are on a stock rom. Actually, most of the time the techs wont even check to see if you are s-off, but just at least return to the latest stock rom
Click to expand...
Click to collapse
Thanks for the reply sitlet. I will get it back to a stock rom.
I am downloading the 2.17 stock RUU now. I can run the RUU and extract the zip out. In there remove at least the hboot and recovery... will that work. Do they work on phones with custom recoveries as well?
I extracted the ROM.zip out of the 2.17 RUU. Then I extracted everything out of the ROM.zip and removed hboot 1.5. Repackaged it back into a zip. So this should be good to go on flashing from the bootloader? The phone currently has a 2.08 rooted ROM on it.
I have had phones replaced with s-off and got a 150$ trade in with my og EVO. All were stock roms. I always keep a stock ROM on my SD card just in case I have to pop into a store and have them look at something
Sent from my PG86100 using XDA App
I took mine in rooted with stock rom. They replaced the screen no questions asked. However, it was alerting for an update which I knew would update the hboot. They gave it back saying they were sorry that they didn't update it for me since I didn't leave the sd card in it. So, if is signaling to be updated, don't give it to them with the card in it.
Don't worry about the phone being rooted when you take it in. That shouldn't matter. Just flash clean ROM or something similar. Just a stock rooted ROM and you'll be fine. They won't even know the difference all they are doing is replacing hardware.
And ditto on the SD card. Leave that out so they can't download any updates. I would probably even be straight forward with them and tell them you don't want them to update anything because you need the HBOOT unlocked in order to do dev work for qualcom. When they ask what you are doing just say your contract does not allow you to discuss details. They won't bother you about it.
We never even go into recovery, my store manager and repair tech had no idea what s-off was until I started...
Awesome. Thanks for all the replies everybody.
I downloaded the 2.17 RUU and extracted the rom.zip out of it. Then removed the hboot 1.5 and repacked the zip and flashed. Got it flashed back to stock 2.17 and he is going to take it into sprint tomorrow.
Anybody know what Sprints policy is on water damage stickers? My phone had got some water on it awhile back and the water stickers are red. The phone works fine and everything, I just hope I don't have this digitizer issue and need it repaired. I've got TEP but would sprint work on it if the water sticker is red?
leerage said:
Awesome. Thanks for all the replies everybody.
I downloaded the 2.17 RUU and extracted the rom.zip out of it. Then removed the hboot 1.5 and repacked the zip and flashed. Got it flashed back to stock 2.17 and he is going to take it into sprint tomorrow.
Anybody know what Sprints policy is on water damage stickers? My phone had got some water on it awhile back and the water stickers are red. The phone works fine and everything, I just hope I don't have this digitizer issue and need it repaired. I've got TEP but would sprint work on it if the water sticker is red?
Click to expand...
Click to collapse
It depends on the store. If the water stickers are red then they can reject it. Most techs will look for signs of water damage on the board. If they find water damage on the board most will send you to the insurance company. Just give a shot and see what happens.
Sent from my PG86100 using Tapatalk
I'm hoping to head over there tonight but was wondering
If I flash RUU 2.17 will it also update my bootloader?
Thanks
cjackxiii said:
I'm hoping to head over there tonight but was wondering
If I flash RUU 2.17 will it also update my bootloader?
Thanks
Click to expand...
Click to collapse
Yes, if you run the 2.17 RUU it will update your bootloader. If you are already S-OFF from revolutionary you will be fine though. You can downgrade back from 1.5 to 1.4. If you want to keep hboot 1.4 and return to a stock non-rooted ROM, you'll need to extract the rom.zip out of the RUU and remove HBOOT. Or i guess I could upload what I made if you want it.
Unfortunately, if the water indicators went off, they will likely not work on it at all. That's the FIRST thing every tech will look at. And it doesn't matter if you say it only got a little wet, they wont believe you.
Well my friend took his EVO 3D out to sprint and they replaced the whole LCD/digitizer. Luckily someone had returned a pretty much brand new EVO 3D. So the tech just swapped it out.
Sent from my PG86100 using XDA App
leerage said:
Yes, if you run the 2.17 RUU it will update your bootloader. If you are already S-OFF from revolutionary you will be fine though. You can downgrade back from 1.5 to 1.4. If you want to keep hboot 1.4 and return to a stock non-rooted ROM, you'll need to extract the rom.zip out of the RUU and remove HBOOT. Or i guess I could upload what I made if you want it.
Click to expand...
Click to collapse
I too am a victim of an hboot 1.5 replacement... If I try to downgrade to 1.4, obviously not knowing if the previous owner was rooted... Would it cause any problems, you know, in the event it was never previously rooted?
Sent from my 3VO
if you are s-off(unlikely) then ya you can downgrade. but if you are s-on even if it was s-off from the last person and you are 1.5 there is no way to get it back. htc more than likely put it back to s-on before handing it your way. oh and you can still unlock the bootloader and gain root. but you have to unlock through htc.
Vandelay007 said:
I too am a victim of an hboot 1.5 replacement... If I try to downgrade to 1.4, obviously not knowing if the previous owner was rooted... Would it cause any problems, you know, in the event it was never previously rooted?
Sent from my 3VO
Click to expand...
Click to collapse
You can't downgrade unless you have s-off, and you can't get s-ff with a 1.50 hboot.
All depends on the Sprint store. My last visit to a Sprint store the reps told me I had too many apps on my phone and most of them were bad. And I had a rooted phone because I had a Sense skin and Widget Locker running.
Sent from my HTC EVO 3D using Tapatalk
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
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!
My DNA has been acting up since I got it thanksgiving. When its plugged into the charger the phone becomes next to unuseable as the touch screen goes bazerk. It vibrates like I'm touching it when Im not, it opens and closes apps on its own and pretty much begins to have a mind of its own. When I unplug it it goes back to normal. Its useable like it should be. Its been like this since day one.
My question is will Verizon replace it if I have the $10 a month insurance on it? I am rooted with viper 1.1.3, 2.04 radios, s-off, and eng hboot. Will they take it rooted or do I have to factory reset and relock bootloader?
Sent from my ViperDNA infected with VipoerBlueDNA
termin8tor22 said:
My DNA has been acting up since I got it thanksgiving. When its plugged into the charger the phone becomes next to unuseable as the touch screen goes bazerk. It vibrates like I'm touching it when Im not, it opens and closes apps on its own and pretty much begins to have a mind of its own. When I unplug it it goes back to normal. Its useable like it should be. Its been like this since day one.
My question is will Verizon replace it if I have the $10 a month insurance on it? I am rooted with viper 1.1.3, 2.04 radios, s-off, and eng hboot. Will they take it rooted or do I have to factory reset and relock bootloader?
Sent from my ViperDNA infected with VipoerBlueDNA
Click to expand...
Click to collapse
I would re lock and load a stock rom to be safe but the reality is they probably won't check it that closely as long as it does what you say when they try to do it...but I could be wrong.
rootntootn is probably right. try to get it as close to stock as possible(I dont think you can S-ON) and bring it to vzw and hope they can replicate the problem.