Ok so I apologize for my lack of knowledge on this subject in advance, but essentially I followed steps a year ago or so to get my phone rooted, everything went fine - I believe I had a stock rooted rom. A couple weeks ago people started complaining about having trouble hearing me clearly on the phone, like I was cutting in and out. A week ago apparently my mic died completely because all I hear now is a high pitched noise when I try to do a voice recording, and no one can hear me when I make or answer phone calls. So I'm trying to get my phone fixed by sprint, but I believe they can tell my phone was rooted.
I used RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10.0530_NV_NV_SPCS_1.16_release_198109_signed.exe to get my phone rom back to stock, but when I hold the vol down button and power I get to a menu that says this:
shooter xc ship s-off rl
hboot 1.40.0000
radio-0.97.10.0530
eMMC-boot
Jun 8 2011, 17:20:22
Any know what I need to do now to get my phone completely back to stock? I know that s-off is a red flag (and I'd like to know how to get that back on), but is there anything else I need to do? Thanks so much.
Personally, I'd leave it just how it is. It's stock enough. They probably won't even check hboot. If they do check it, they probably won't care since you have a hardware issue. I would only turn s-on if sprint told me they won't work on it until I did.
Edit.. if you're determined to get s-on, the command is
Code:
fastboot oem writesecureflag 3
Only use that command if you have an official hboot, like 1.4, 1.5, 1.58 (which you do, according to your post).
Related
So. I flashed that horrid firmaware by freeza thats destroyed my devices ability to call out, text... all i can do is data, broken record right?
Whats worse is my other phones a samsung, the droid charge. I thought i was alright at first after flashing the VM firmware, but then i suddenly started receiving Error Code: 97 Class: 2 on outgoing SMS, this happens after the failed SMS send so much i couldnt look the fix up on my evo so i saw on my computer that i could call sprint and have them refresh me on their network. I also saw i could work a PRI fix.
Heres a little history before the isse: i was at 1.4 HBOOT S-OFF after following the live CD S-OFF 1.5 to 1.4 revolutionary method.
After i realized my SMS and CALL was borked i tried flashing the PG86IMG (the one you pull the power cord out the moment it begins to flash boot) to get to 1.5 HBOOT stock which is what that is by what i can tell. Unfortunatly this does nothing but put me at a 1.5 bootloader and no root.
I see that the PRI downgrade method requires root so i need to get S-ON now on 1.5 which is what i am now on
UPDATE: I fastbooted a command to S-ON and i did the brick downgrade method again and its currently flashing the 1.13 RUU. Im attempting to get recovery and then flash one of the rooted roms i have and try the PRI downgrade from there.... not quite certain why i couldnt work revolutionary earlier, im pretty sure i was 1.13 and also 1.4 HBOOT w/ S-OFF... i might never care to know why if this works. I bought this phone off ebay for 150$+rush shipping and a dock and two chichitech 1900s w/ batt charger and it rounded out to about 250$ all in all. Thats a waaaay better deal than the triumph on V-mo. Oh and the phone has a clean ESN and its mint... insane deal there, i got it put on a sprint employee plan and play 30$ a month plus tax. no 4G where i live but everyone thats not living in a shack outside a tower has the same experience so im not crying
failure...
okay so it utterly failed. not really not sure what to do i just want to get my calling and texting working again this is lame... ive rooted 4 phones now and they all happily work fine nothing like this ever happened and this is the best phone i ever had
What failed, I assume you got 1.13 loaded fine and then tried to revolutionary? If it failed to revolutionary what happened? Did you run it multiple times?
yeah i ended up switching the S-OFF to S-ON somehow on 1.4 HBOOT then i ran revolutionary straight off my laptop, there was some issue on my desktop which is vastly better in all areas but somehow got a driver issue i couldnt resolve. i havnt slept yet but im on mean 4.3 fresh now. I just used the beta key straight in rEvo not on the live disc and it worked. my laptop seems better at modding phones lol this is its 3rd of my four ive had that it just has no issues with whatsoever its a cruddy d630 too!
anyway i still have to downgrade the PRI thanks to the bloody VMfirmware i flashed before we all knew the horrors it would cause... sleep now, work on that tomorrow
Sent from my PG86100 using XDA
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!
im not new here but today i made an account because not only do i love this place its the best place for rooting and troubleshooting. i have a few tricks to share in one of those troubleshooting forums that could be useful.
I'm not a noob and im very comfortable with flashing roms and kernels. Though my phones a unique case.. before i ever rooted or even tampered with the phone the audio cut out. not a single sound comes out the speaker, headphone jack, and even bluetooth. when i did have stock sense anytime i got a call or wanted to play some music my phone would freeze then reboot. every single time. for awhile roms fixed it, to be more specific cyanogenmod fixed it. Even with no sound it causes some other smaller issues too. The phone wont auto rotate, any app that requires sound like games and youtube will either quit instantly or i will have to force close them. Its been going on for about 7months now (stuck in a contract with sprint and they won't honor the TEP).Today i tried using ViperRUU to return to fresh stock and try again to solve the audio problem and everything went as it should except it just won't boot into android. I thought it might be the kernel but that wasn't it. I tried flashing another sense rom and its kernel and the same thing happens it just sits there with a black screen. those who have HTC's newer phones, i tried holding the power button to restart the phone and thats all it will let me do. While on the black screen i connected it to my computer and it knows it there so i guess its not totally bricked, i think the right term is Softbricked? i looked in other posts to see if anyone had the same issue as me and i apologize if i didnt look hard enough to find one. I'm clueless on what to do. if its not the rom, kernal, or recovery what could it be? even trying to restore from a sense backup gets the same results. It just sits there with a black blank screen.
I apologize if this is the wrong place to post this as I am new to posting here,I Also marked this as question because if im understanding this right that is right? Thank you everyone in advance for the help
Some more information would be useful. If you can get to your bootloader, what is your Hboot version, radio (baseband) version, are you S-on or S-off, and what's the status of the bootloader (locked, unlocked, relocked)? What recovery are you using?
Also, when you connect to your computer, what does your phone show up as?
Sent from my HTC EVO 4G LTE
And is there water damage at any point? That sounds like faulty hardware, like a broken/melted chip. Do you overclock?
_______________________________________
Phone: HTC EVO 4G LTE
Stock, S-On (Returning to Sprint)
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
my phone info
FinZ28 said:
Some more information would be useful. If you can get to your bootloader, what is your Hboot version, radio (baseband) version, are you S-on or S-off, and what's the status of the bootloader (locked, unlocked, relocked)? What recovery are you using?
Also, when you connect to your computer, what does your phone show up as?
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Jewel PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.12.11.1210
OpenDSP-v31.1.0.45.0815
eMMC-boot
bootloader status: *** TAMPERED ***
*** UNLOCKED ***
TWRP Version v2.6.3.0
I used htc dev to unlock it but fastboot says its unlocked, I got an ota update several months ago. I wasn't thinking and updated it and ever since it has never said S-OFF.
TWRP says theres an os on the system partition 880 something megabytes.
it has a bit of history
aarsyl said:
And is there water damage at any point? That sounds like faulty hardware, like a broken/melted chip. Do you overclock?
_______________________________________
Phone: HTC EVO 4G LTE
Stock, S-On (Returning to Sprint)
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
after like a month of owning the phone, i was in gym class one day. Felt my phone vibrate, went to the drinking fountain so my phone wouldn't be confinscated. i pressed the sleep button and BAM screen cracked. Not the glass just the screen. long story short, sprint wouldn't honor the warrenty and i don't have a lot of money so im not paying $200 for another phone when I already paid an extra $60 a month for a TEP plan witch i gladly removed. over a year I replaced the screen twice ($140 total still under the $200). I don't do the over-clocking stuff because my battery is bad enough already. I talked to htc about my phones audio problem and they have no record of any other customers with this issue i love my phone but having no sound is extremely fustrating.
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
It's been a long time since I've had a cell phone or messed with roms, etc. Last time was back in the days of the HD2. Clearly things have changed a lot since then. But I think I have an unusual issue. Just got this phone off ebay. And it appears to either have been modified, or it is an early engineering sample or maybe someone has flashed an early HTC in-house rom or something. Here's the info from the bootloader screen.
Locked
Fireball PVT Ships S-off RL
CID 11111111
Hboot-1.02.0000
Radio-.0.98.05.0427
OpenDSP v25.1.0.32.0405
eMMC-boot
Apr 20 2012,01:01:10
If I even install one or two apps, it shows low space message and comes to a crawl. I can not seem to root it, nor do anything with it. And the first time I turned it on, the HTC splash screen had a message on it saying the build is for development purposes only and must not be shared outside of HTC.
All I want to do is get a lighter weight ROM that gets rid of all the bloatware and leaves me some storage space, and maybe be able to move apps and data to the SD card.
I am no idiot, but I am a tad out of my depth here. This is not like flashing roms on my old HD2. And I suspect somethings is not normal on this particular phone as well.