So....last week, Verizon weirdly reported that my phone (rooted) used 3.5 gigs of data during the night while my phone was connected to wifi. The phone data usage screen, however, only reported 298 kb of usage. I called Verizon, we went back and forth, they finally decided that my phone was screwed up, and sent me a warranty replacement. I then began the tedious process of unrooting.
Once I finally got my phone back to the 1.08 HBOOT and S-On and stock recovery...finally.....the phone now says "RELOCKED" at the top instead of "LOCKED."
I posted about it on Infected. I was told that I could edit the hex file but it was not recommended. I have until Friday to package it up and send it in, and I'm a little worried. One user says that he has returned warranty replacements rooted and whatnot without incident, but I'm afraid that the techs might take an extra look at my phone because of the strange data issue I called them about last week that produced a "diamond tech support ticket". If they do, they will see a big, red "RELOCKED" at the top of the bootloader, which will be a dead giveaway. They won't be able to prove that I rooted it and flashed custom roms, but unlocking the bootloader is enough to void the warranty.
I did see some people with similar issues on the Rezound, and one person swore that if they used fastboot usb and typed in "fastboot oem lock" and then flashed a RUU in the boatloader, it was fixed, but I can't figure out how to make my command prompt to connect to my phone (I know, for someone who has flashed roms for a few years now, and Windows Mobile roms a few years back too, it seems like a total noob move).
Anyway, between that and the fact that we don't have a real ICS RUU, only the one that Santod put together (which worked beautifully for me otherwise), I'm not sure what else I can do. I tried flashing the .19 RUU, but it recognizes that it contains an older version of the bootloader, and won't flash. It's that one dang "RELOCKED" that has me nervous about sending it in. I'm about to just keep it and send back the warranty replacement complaining about the power button or something just to buy some time.
Any ideas?
arizonaomnia said:
So....last week, Verizon weirdly reported that my phone (rooted) used 3.5 gigs of data during the night while my phone was connected to wifi. The phone data usage screen, however, only reported 298 kb of usage. I called Verizon, we went back and forth, they finally decided that my phone was screwed up, and sent me a warranty replacement. I then began the tedious process of unrooting.
Once I finally got my phone back to the 1.08 HBOOT and S-On and stock recovery...finally.....the phone now says "RELOCKED" at the top instead of "LOCKED."
I posted about it on Infected. I was told that I could edit the hex file but it was not recommended. I have until Friday to package it up and send it in, and I'm a little worried. One user says that he has returned warranty replacements rooted and whatnot without incident, but I'm afraid that the techs might take an extra look at my phone because of the strange data issue I called them about last week that produced a "diamond tech support ticket". If they do, they will see a big, red "RELOCKED" at the top of the bootloader, which will be a dead giveaway. They won't be able to prove that I rooted it and flashed custom roms, but unlocking the bootloader is enough to void the warranty.
I did see some people with similar issues on the Rezound, and one person swore that if they used fastboot usb and typed in "fastboot oem lock" and then flashed a RUU in the boatloader, it was fixed, but I can't figure out how to make my command prompt to connect to my phone (I know, for someone who has flashed roms for a few years now, and Windows Mobile roms a few years back too, it seems like a total noob move).
Anyway, between that and the fact that we don't have a real ICS RUU, only the one that Santod put together (which worked beautifully for me otherwise), I'm not sure what else I can do. I tried flashing the .19 RUU, but it recognizes that it contains an older version of the bootloader, and won't flash. It's that one dang "RELOCKED" that has me nervous about sending it in. I'm about to just keep it and send back the warranty replacement complaining about the power button or something just to buy some time.
Any ideas?
Click to expand...
Click to collapse
the bootloader status is controled by a flag in another partition. it is well know with dual core and quad core snapdragon 3/4 devices,but i do not believe anyone has looked much into it for the older single core devices. the flag being in a block that is not touched by OTAs or RUUs is what makes hboot retain the same status regarless of hboot version,ruus run,etc.
with the newer phones,hboot looks at the flag,display locked if it finds 00 00 00 00,or .... and unlocked if it finds "HTCU" and relocked if it finds "HTCL". obviously,it comes from the factory 00 00 00 00,and htcdev sets it to HTCU when you first unlock. entering fastboot oem lock changed to HTCL.
the value is easily cahnged with adb,or with a dumped partiton and hex editor with a radio s off device,making the device out of the box stock.
the values may or not be the same in the older device,and they are defiantely in a different location. there is also the question of if youd even be able to change the flag,or is it blocked by write protection. while the eng hboot,and revolutionary patched hboot are eliminating signiture checks and ignoring the radio on things flashed in the bootloader,they are not able to override write protections in place as the phone boots.
i have been wanting to search for this flag,for S&Gs,but havent gotten to it yet. i would help you if time wasnt a factor... but ive got a fair amount on my plate this weekend. also, i dont want to get your hopes up,as the logical location is in mmcblk0p7,where the radio secure flag lives. if this is the case,that block is protected and you wont be able to change it anyway,even if we find the flag and its values.
i dont know if that helps,but its what i know about the "lock status" flag
Santod made him a faux locked s on hboot. Good writeup on the locked status though.
Sent from my HTC6500LVW using Tapatalk
Related
I've recently rooted and had some issues with my personal phone, which I've cleared up with help from this board and members, and have actually enjoyed messing with my phone, its been fun learning about android and the possibilities with these phones. But with a bit of hesitation on going at it again with my phone, and how screwed I was when I couldn't get it going for a while, I thought I'd browse for a spare phone, anything, something old to screw around with and really practice on.
well, don't I find a 'bricked' amaze in my local classifieds! so $50 later I have myself a spare amaze to mess with! This phone powers on and goes straight to hboot, and I thought sweet, a factory rom upgrade and away we go. but it wasn't so easy.
this phone is a telus, and was relocked, but the one thing I noticed on this one that I didn't on mine when I flashed the telus rom is that this one has a 'security warning' under the relocked banner at the top of hboot. For the life of me I can't seem to get an oem rom to upgrade this phone. I've tried 3 different sd's, formatting etc. downloading the telus ruu zip from lots of different sites, trying with sd out then installing it when hboot loads, with and without usb plugged in, you name it I've tried it, and I cant' seem to get a stock rom to load.
hboot checks for ph85diag, then ph85img, finds it, checks it, then checks it again and back to hboot. No matter what I do, it won't ask to upgrade, and even trying out other ruu's it'll at least tell me that its the wrong file. Funny thing is in all of this I've already done this on my fully working amaze, and it worked right away, the only thing I'm thinking is that security warning banner, if that's in any way preventing the install.
any thoughts?
andy55 said:
I've recently rooted and had some issues with my personal phone, which I've cleared up with help from this board and members, and have actually enjoyed messing with my phone, its been fun learning about android and the possibilities with these phones. But with a bit of hesitation on going at it again with my phone, and how screwed I was when I couldn't get it going for a while, I thought I'd browse for a spare phone, anything, something old to screw around with and really practice on.
well, don't I find a 'bricked' amaze in my local classifieds! so $50 later I have myself a spare amaze to mess with! This phone powers on and goes straight to hboot, and I thought sweet, a factory rom upgrade and away we go. but it wasn't so easy.
this phone is a telus, and was relocked, but the one thing I noticed on this one that I didn't on mine when I flashed the telus rom is that this one has a 'security warning' under the relocked banner at the top of hboot. For the life of me I can't seem to get an oem rom to upgrade this phone. I've tried 3 different sd's, formatting etc. downloading the telus ruu zip from lots of different sites, trying with sd out then installing it when hboot loads, with and without usb plugged in, you name it I've tried it, and I cant' seem to get a stock rom to load.
hboot checks for ph85diag, then ph85img, finds it, checks it, then checks it again and back to hboot. No matter what I do, it won't ask to upgrade, and even trying out other ruu's it'll at least tell me that its the wrong file. Funny thing is in all of this I've already done this on my fully working amaze, and it worked right away, the only thing I'm thinking is that security warning banner, if that's in any way preventing the install.
any thoughts?
Click to expand...
Click to collapse
unlock it done
you're kidding, its that easy? I thought about it too and didn't try that. First thing I'll be doing when I get home
what I was screwed by was I did the exact same thing to my good phone, I re-locked it, and loaded the telus rom and it went easy, no problems, and I tried the same with this phone, and no dice
did the unlock trick work
I'll let you know in a couple hours, the dud's at home and I'm stuck at work with computers that encrypt everything connected to them no screwing around (to a certain degree) at work
yup worked, had issues with wifi/bluetooth but bulletproof fixed that issue, all is working again, thanks, I can't believe I didn't think that would work before!
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
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...
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!
So today as I was preparing to flash the latest AOKP rom at 90% battery, I accidentally hit reboot to bootloader instead of recovery. No problem, i hit reboot. The screen turned black and a minute later it was still black, so I removed the battery. Nothing turned it on, couldn't access the bootloader and the charging light wouldn't even go on.
That was odd, so i thought maybe it was just still in bootloader mode. I gained access to ADB and it doesn't see the device at all (yes i tried the method explained because of the CWM problem, I also do not have CWM and have had a battery die before and it was able to charge fine) I also tried fastboot and it just sits at "waiting for device"
I called up Verizon support figuring it was the battery and they said i could test it at a store. The rep didn't think it was the battery, but when he tested it said 3/3 times it was increment, so it was bad. Then when he tried a regular battery it didn't work either, so he said the phone was bad.
Now, i called support and they are sending me a new phone and i am going to exchange my extended battery for a good one tomorrow. The thing is the lady on the phone said that as long as there were no hardware defects or unauthorized software than there wouldn't be any charge but if there was then it would be a $200 charge added onto the bill. A $200 charge would be pretty bad.
I would never return my phone if i messed it up actually doing something to the phone but here it didn't... at least not in any way I can think of. I am worried about the charge though. I know they usually don't check them but I had the Juopunut bear h-boot and neo's ICS installed. I am not even sure if it's recoverable at all because from everything i tried it definitely wasn't.
Am i just being silly here?
If they can't even boot the phone, then there is no way that they can tell it was hacked.
Sounds like the only way they'll get the phone booting is to do the manufacturer RUU thing with their special tools, so I'd say you're in the clear.
I've sent a phone back that was S-OFF running CM9. If they check before they JTAG it, I've seen no evidence of it.
I had heard before many times that they never checked, but i was extremely surprised whenever she said that. I wanted to ask some of you guys your opinion as well. I doubt it's recoverable without a full sbf as well, so i should be fine. Thanks!
Reaper0294 said:
I had heard before many times that they never checked, but i was extremely surprised whenever she said that. I wanted to ask some of you guys your opinion as well. I doubt it's recoverable without a full sbf as well, so i should be fine. Thanks!
Click to expand...
Click to collapse
I had to send mine back for a screen hardware issue. I was still s- on with the bootloader saying relocked and I did not get hit with that charge. As stated before I have heard of people sending back their phones with different ROMs without issue. Good luck
Sent from my Rezound using xda app-developers app
I've returned multiple devices saying relocked in the bootloader. I think Verizon simply doesn't care to be honest.. Hell I've even gotten a replacement phone that was rooted and running custom software. Shows you how muc hattention they pay to the devices they recieve and send out. Hell I've gotten replacements with screen protectors still on them and big ass gashes/scratches on the screen. 100 point inspection my ass.
Same here; my first Rezound was S-OFF, bootloader unlocked when the USB port failed (the unit would charge but couldn't connect to PC). I just factory reset it and sent it back. The folks who refurbish the phones don't even turn 'em on, and if they did, they probably wouldn't know what they were looking at. The things are bulk reflashed, if the motherboards are even retained at all.