Alright people, I need help. I have an HTC Rezound (obviously) for verizon. I want to go back to Complete Stock, (as if it were brand new).
It was unlocked using HTC devs method
Its rooted
It is s-on
The recovery file i used is : recovery-ra-vigor-3.16-gnm
I installed a custom rom: Business_ICS4.0.3_Sense3.6-v6.3
Android version 4.03.605.2
HTC Sense 3.6
How do i get my phone to be:
Completely stock
Stock rom
no root
Locked title in Hboot
fix the tampered title in hboot
Any help is much apreciated
Are you doing this to warranty it? It will say "relocked" when you are done. It hasn't been a problem for anyone in the past though, you should still be able to return it to Verizon.
Instructions on how to return to stock are here:
http://forum.xda-developers.com/showpost.php?p=38244272&postcount=10
You probably should use the latest official RUU (prior to the OTA they just rolled out a couple days ago) which is 3.14.605.12. The link I have is to an .exe file. You just connect your phone to your pc and then double click. It will take you through the steps.
Get it here:
http://androidfiles.org/ruu/?dir=Vigor
That will get you back to stock, unrooted and it will say "relocked".
There was a global leak that wasn't official. If you want to use that, get it here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
This is a zip file you put on your external sd card. Follow instructions in the first link I gave you.
THANK YOU
feralicious said:
Are you doing this to warranty it? It will say "relocked" when you are done. It hasn't been a problem for anyone in the past though, you should still be able to return it to Verizon.
Instructions on how to return to stock are here:
http://forum.xda-developers.com/showpost.php?p=38244272&postcount=10
You probably should use the latest OTA, prior to the one they just rolled out a couple days ago which is 3.14.605.12. The link I have is to an .exe file. You just connect your phone to your pc and then double click. It will take you through the steps.
Get it here:
http://androidfiles.org/ruu/?dir=Vigor
That will get you back to stock, unrooted and it will say "relocked".
There was a global leak that wasn't official. If you want to use that, get it here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
This is a zip file you put on your external sd card. Follow instructions in the first link I gave you.
Click to expand...
Click to collapse
Thank you so much it worked like a charm!!! You just saved me from a weeks worth of searching i did and a couple of headaches.. Thank you very much
You're welcome, glad it worked for you!
I noticed I typed the wrong thing when I said "latest OTA", I should have said "latest official RUU" (don't know what was going on in my head) so I'm going to edit that post to fix it for any future readers.
okay, im having the same problem, except im s-off. i need to send my rez back for warranty reasons, i have a custom rom, my h-boot says locked, s-off, 2.27.000. any help would be awsome! thanks!
motodanr1 said:
okay, im having the same problem, except im s-off. i need to send my rez back for warranty reasons, i have a custom rom, my h-boot says locked, s-off, 2.27.000. any help would be awsome! thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=
Sweet, thanks! When I click on the link I get "no thread specified" though ..?
Sent from my ADR6300 using xda app-developers app
Go into dev, sticky, roll up thread. Click on back to s-on link
Phaded said:
http://forum.xda-developers.com/showthread.php?t=
Click to expand...
Click to collapse
I was Tampered/Locked and s-off. I ran the 4.03.605.2 RUU twice then its said locked the tampered was removed. I used the mini-adb_vigor program to achieve S-ON. Open a Command prompt wtih admin privileges and enter these commands pressing enter after each one. Now I am completely back to Locked S-ON. Hope this helps.
cd c:\mini-adb_vigor
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
netookska05 said:
I was Tampered/Locked and s-off. I ran the 4.03.605.2 RUU twice then its said locked the tampered was removed. I used the mini-adb_vigor program to achieve S-ON. Open a Command prompt wtih admin privileges and enter these commands pressing enter after each one. Now I am completely back to Locked S-ON. Hope this helps.
cd c:\mini-adb_vigor
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Click to expand...
Click to collapse
Make sure to run this on a stock hboot or it will brick.
I am having a similar issue. I am rooted, I never relocked my bootloader, stock minus a few mods, but the ota update keeps failing. What do I need to do to be able to accept the update so it stops rebooting my phone?
Related
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Watercycle said:
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Click to expand...
Click to collapse
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
a.mcdear said:
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
Click to expand...
Click to collapse
unguarded or super user? and thank you i didn't know about that =)
Watercycle said:
unguarded or super user? and thank you i didn't know about that =)
Click to expand...
Click to collapse
Sueperuser not unguarded
this is the most rediculous process ever! (currently trying to wire trick) I'VE USED 2 DARN TYPES OF WIRE AND A PAPERCLIP AND NONE OF THEM DO ANYTHING
oh god, whew... i was running around the house making a wire out of everything...
but after trying the paperclip for like the 8th time (which took a half hour to find) it seems to have worked
S-off is the most stressful android activity ever >XO
thanks you two <3
You did use the ics jb hboot right? Make sure you can see the sd card? And don't unlock your phone again. You would need to s-on then s-off again for it to say locked. I just woke up and saw your new posts, its been a long day but I see you got help. Welcome to the club, glad it finally worked.
sent from my Clean Rezound
I used the Hboot that came with 3.14 Ruu, if S-off took the "relocked" away then i'm happy, if it didn't, oh well, but I was unlocked when I started the process =o
As long as you don't unlock it after s-off, it will be locked again ( although it says "juopunutbear" instead of "locked" if you're using their modified boot. Just flash a stock one and it will say locked)
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The patched hboot adds some advanced fast boot commands. However everything will work without the patched hboot. You don't need it its just nice to have
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
ericsignals said:
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
Click to expand...
Click to collapse
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Forgot to add that part when I typed the adb part ....thanks for correcting me.:thumbup:
Sent from my Rezound
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Watercycle said:
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Click to expand...
Click to collapse
Yes, but there are ways around that
I personally just package my own ph98img.zips if I need to flash a kernel or recovery after doing something dumb
Sent from my ADR6425LVW using Tapatalk 2
If you want to add the JB Hboot, it is very simple. You can go to their site and just download the most recent hboot. You must know if you are ICS or GB. But go here: http://unlimited.io/hboot-downloads/ and download the right one, either vigor ics or vigor gb. Put that in the folder where you had put the original controlbear program and follow these instructions:
To flash the JuopunutBear hboots
Put the phone in fastboot mode, connected to the pc and enter the following commands
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
Thats all there is to it and you can now benefit from the JB Hboot.
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Yes you need to be unlocked. It's part of the prerequisites. Please read then reread the thread in general "s-off with instructions...it's official". Understand how to avoid problems and fix them if they arise. It's very easy but it's like people half ass reading the instructions recently. Don't be that person.
sent from my Clean Rezound
th3rapist said:
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Click to expand...
Click to collapse
You have to unlock befor you s off, afterwards it's redundant to do so. But some people have
Sent from my ADR6425LVW using Tapatalk 2
doubleshot, ruby ICS, vigor ICS, holiday ICS, pyramid ICS?
which one? haha
I don't mind don't 1 more small flash that will probably be necessary in the future as long as it doesn't screw my current rom up
Hey,
I have a Telus Amaze 4G and I have lost my radio. Phone says it has an unknown Baseband/IMEI. Not sure where I went wrong/ lost my radio but this is a run down of what I've done to my handset so far:
- Rooted
- Flashed CWM recovery.
- Flashed EnergyRom.
- Sent phone to HTC because of suspected warranty issue. (Wouldn't Charge)
- Phone returned un-repaired from HTC.
- Charged battery externally, phone finally booted.
- Replaced CWM with 4EXT.
- Ran the Telus GB RUU exe from windows.
- Did the OTA ICS from the phone.
- Attempted upgrade to SpeedRom, failed because the OTA had failed, didn't realize this until the next around, this is where I think it went wrong. Had done a full wipe of all partitions, except SD from 4EXT in the process.
- Re-applied original Telus GB RUU.
- Re-applied Telus ICS OTA. this is when I realized I had no radio. I had not put in my SIM-Card since the phone was returned from HTC so not exactly sure when it stopped working but the OTA had installed correctly this time.
- Re-rooted.
- Did the wire-trick and obtained S-OFF.
- Flashed the latests JP hboot.
- Used fastboot to flash several radio.img files from various TMO and Telus RUUs, nada.
- Flashed the T-Mobile ICS RUU via hboot, still no radio.
- Extracted the rom from the Telus GB RUU and applied that via hboot, still no radio.
The only thread I could find where someone had mentioned the missing baseband on an amaze 4g, the only suggested fix was to reflash a stock, GB rom but that didn't work. Now I am at a loss at to what I could try next.
Any suggestions would be greatly appreciated.
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Jay_Rulen said:
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Click to expand...
Click to collapse
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Dark Nightmare said:
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Click to expand...
Click to collapse
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
inluck said:
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
Click to expand...
Click to collapse
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
inluck said:
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
Click to expand...
Click to collapse
I can't say, just keep your fingers crossed that it doesn't.
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
inluck said:
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
Click to expand...
Click to collapse
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
inluck said:
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
Click to expand...
Click to collapse
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
inluck said:
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
Click to expand...
Click to collapse
It's not the hboot. I gotta find the s-on thread, since you have to be on a stock bootloader before you s-on. I probably missed something.
Sent from an Amaaaaaazing place :-D
http://forum.xda-developers.com/showthread.php?t=1647728
I just remembered another trick as well, when you s-off the device, it relock your bootloader but it says "locked" not relocked, therefore when you s-off, do not flash the jb hboot when they ask you if you wanna flash it, then simply s-on via the fastboot command, voila!
Sent from an Amaaaaaazing place :-D
Alright guys, I've searched and searched and I think I have it all down, just want to lay out my steps and get verification.
I'm on T-Mo ICS, not from OTA, flashed myself
Root
S-Off
4-Ext
I'm sending my phone in and need to go back to stock. I think I would prefer to go back to GB so it's just like from factory with no OTA.
- Download the Stock GB RUU from here - HTC Ruby/Amaze 4G Stock ROMs
- The RUU I want is - PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed
- Following These Directions I connect via ADB and fastboot oem lock This will show it as Re-Locked, correct?
- Reboot
- Flash the stock RUU I got by placing it in the root of my external sd card and renaming it PH85IMG.zip and rebooting to bootloader. Which is Volume Down + Power? Can someone verify that?
- Then I set the security lock by doing "fastboot oem writesecureflag 3" - This will change the bootloader to show locked, not re-locked, correct? I thought you had to have root to ADB?
At that point I'm back as if I took the phone out of the box for the first time? 4ext will be replaced with Stock Recovery? Thanks in advance. Like I said, I've searched, but there are many conflicting reports. :good:
Minker17 said:
Alright guys, I've searched and searched and I think I have it all down, just want to lay out my steps and get verification.
I'm on T-Mo ICS, not from OTA, flashed myself
Root
S-Off
4-Ext
I'm sending my phone in and need to go back to stock. I think I would prefer to go back to GB so it's just like from factory with no OTA.
- Download the Stock GB RUU from here - HTC Ruby/Amaze 4G Stock ROMs
- The RUU I want is - PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed
- Following These Directions I connect via ADB and fastboot oem lock This will show it as Re-Locked, correct?
- Reboot
- Flash the stock RUU I got by placing it in the root of my external sd card and renaming it PH85IMG.zip and rebooting to bootloader. Which is Volume Down + Power? Can someone verify that?
- Then I set the security lock by doing "fastboot oem writesecureflag 3" - This will change the bootloader to show locked, not re-locked, correct? I thought you had to have root to ADB?
At that point I'm back as if I took the phone out of the box for the first time? 4ext will be replaced with Stock Recovery? Thanks in advance. Like I said, I've searched, but there are many conflicting reports. :good:
Click to expand...
Click to collapse
In order to flash the factory RUU you need to be either locked or relocked. Then when you flash the factory RUU it should overwrite your hboot which will reset from "relocked" to "locked" then the writesecureflasg function will turn S-ON and you'll be factory.
freakasis said:
In order to flash the factory RUU you need to be either locked or relocked. Then when you flash the factory RUU it should overwrite your hboot which will reset from "relocked" to "locked" then the writesecureflasg function will turn S-ON and you'll be factory.
Click to expand...
Click to collapse
If you're s-off you don't need to lock or relock to flash a stock ruu.
Sent from my SGH-T999 using xda app-developers app
Dark Nightmare said:
If you're s-off you don't need to lock or relock to flash a stock ruu.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Guess that does make sense, huh?
But everything looks OK then?
Update - Downloaded and renamed the RUU, rebooted into recovery and installed everything. Bootloader shows locked and I went ahead and did the ICS Update. Everything is back to factory and I'm ready to send it back.
Final Steps
Minker17 said:
Update - Downloaded and renamed the RUU, rebooted into recovery and installed everything. Bootloader shows locked and I went ahead and did the ICS Update. Everything is back to factory and I'm ready to send it back.
Click to expand...
Click to collapse
Rick. Like you, I want to bring my T-Mobile HTC Amaze back to stock so that I can upgrade to ICS. The phone was bought on eBay with GB and a custom rom. I'd like to follow your steps but it had a lot of question marks and/or needed confirmation. Will you post exactly what you did?
Your steps seems a lot easier than what I've been researching. Is it really that simple? It makes sense. Everyone else uses hasoon2000 toolkit. Thanks for your time!
TheCount01 said:
Rick. Like you, I want to bring my T-Mobile HTC Amaze back to stock so that I can upgrade to ICS. The phone was bought on eBay with GB and a custom rom. I'd like to follow your steps but it had a lot of question marks and/or needed confirmation. Will you post exactly what you did?
Your steps seems a lot easier than what I've been researching. Is it really that simple? It makes sense. Everyone else uses hasoon2000 toolkit. Thanks for your time!
Click to expand...
Click to collapse
You don't need to go back to stock you just need to download the factory ics ruu or a rom that stock like. The hasoon toolkit is more of a guide to help you with the process try to read it an maybe you can rom your cell with a better one!
Sent from my HTC_Amaze_4G using xda app-developers app
S-off
FutureAirways said:
You don't need to go back to stock you just need to download the factory ics ruu or a rom that stock like. The hasoon toolkit is more of a guide to help you with the process try to read it an maybe you can rom your cell with a better one!
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply. That makes sense, too. Plus, it'll save me a step. I'm new to Android and got a lot to learn. With the help of xda-developers, I've learned a lot these past three weeks.
From what I've been reading, it's apparent that I need to have S-off before I do any flashing. Like I mentioned, I bought the phone with a custom rom. I'm guessing if it has a custom rom, then it was S-off at one time. If so, I should be able to S-off easily. Since I didn't flash the phone, I'm not sure what program is installed. Your knowledge and experience will be greatly appreciated if you can tell me if I'm able to S-off easily and how. Whenever I go into HBOOT I see the following:
***UNLOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0008
eMMC-boot
FASTBOOT
<vol up> to previous item
<vol Down> to next item
<Power>
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
My 3G has been terrible since I got the phone, so I finally took it in to the sprint repair shop. They said before they can look at it I need to unroot and take the latest sprint update.
If I go stock and take the official OTA update, will I be able to achieve S-OFF and root again?
How do I go about going completely back to stock?
Thanks!
If you are s-off, flash the ruu.exe. Everything will go back to stock (ROM, recovery, etc), but you will remain s-off. I think you have to lock the bootloader first, but you don't need to be s-on.
Imagika FTW... with Tapatalk 2
Raillery said:
My 3G has been terrible since I got the phone, so I finally took it in to the sprint repair shop. They said before they can look at it I need to unroot and take the latest sprint update.
If I go stock and take the official OTA update, will I be able to achieve S-OFF and root again?
How do I go about going completely back to stock?
Thanks!
Click to expand...
Click to collapse
Hello,
I believe I can help you out with this. Are you s-off right now? If so, then all you have to do is download the latest ruu. It's easy. You can find it in the development section under stickies. If your s-on however you will need to run the ruu.exe on your pc which I believe you can find that file under the stickies. Now if your s-off, you can flash the ruu file by renaming it to PG86IMG in all caps and placing it on the root of your sdcard and booting into bootloader and flashing it from there. If you are going to turn s-off back to s-on you must do this immediately after you flash the ruu. Just go to fastboot on your computer with your phone in fastboot and type this command fastboot oem write securityflag 3. I believe that's the right command. Just make sure your hboot is stock and not modified or else you will brick your phone. And of course you can still achieve s-off and reroot after that. Ramjet wrote a very simple and easy guide that will help you step by step with the easiest way to get there. You can find his guide in the general discussion section. If you have any questions please do not hesitate to ask.
Please hit the thanks button if helped you in Anyway. Goodluck.
This ruu? The second one?
Raillery said:
This ruu? The second one?
Click to expand...
Click to collapse
Those are firmware .zip's that won't return everything to stock. I'd suggest that you download the 2.89.651.2 ICS RUU.exe from one of the links in this post and run it from Windows. Then you will be totally stock except for S-OFF and they shouldn't care about that. When you get the phone back you can just flash a custom recovery then root the stock ROM or flash a custom rooted ROM without having to worry about getting S-OFF again, unless they set it back to S-ON when it is serviced.
ramjet73
ramjet73 said:
Those are firmware .zip's that won't return everything to stock. I'd suggest that you download the 2.89.651.2 ICS RUU.exe from one of the links in this post and run it from Windows. Then you will be totally stock except for S-OFF and they shouldn't care about that. When you get the phone back you can just flash a custom recovery then root the stock ROM or flash a custom rooted ROM without having to worry about getting S-OFF again, unless they set it back to S-ON when it is serviced.
ramjet73
Click to expand...
Click to collapse
Do you have the link to the ruu that can be run through the phone? I keep getting error 155 unknown error.
EDIT: Nvm it worked, just had to manually rebooted to bootloader.
Raillery said:
Do you have the link to the ruu that can be run through the phone? I keep getting error 155 unknown error.
Click to expand...
Click to collapse
That error means you didn't lock the bootloader first. Use the fastboot command: fastboot oem lock. Then run the ruu.
Imagika FTW... with Tapatalk 2
I just got a warranty replacement a few days ago. I unlocked it via HTC method and flashed a recovery and all is fine. Flashed a few ROMs and was happy. I decided that I wanted to get S-OFF again tho, and to do that i need to be back on the stock ROM. So i went to flash the latest Verizon ICS OTA's RUU in the bootloader and it see's the zip file, scans it and then just goes to the main bootloader menu and gives me no option to flash. I haven't tried the global RUU because i wasn't sure I can do the S-OFF exploit on the global RUU. Is this normal? I did accept the little OTA verizon is pushing out now and i didn't think that did anything to the bootloader but i wouldn't really know. I have used this exact zip to revert back to stock very recently prior to getting the replacement. It worked fine always, and I would just rename it and leave in in the SDs root directory.
vonhinkle said:
I just got a warranty replacement a few days ago. I unlocked it via HTC method and flashed a recovery and all is fine. Flashed a few ROMs and was happy. I decided that I wanted to get S-OFF again tho, and to do that i need to be back on the stock ROM. So i went to flash the latest Verizon ICS OTA's RUU in the bootloader and it see's the zip file, scans it and then just goes to the main bootloader menu and gives me no option to flash. I haven't tried the global RUU because i wasn't sure I can do the S-OFF exploit on the global RUU. Is this normal? I did accept the little OTA verizon is pushing out now and i didn't think that did anything to the bootloader but i wouldn't really know. I have used this exact zip to revert back to stock very recently prior to getting the replacement. It worked fine always, and I would just rename it and leave in in the SDs root directory.
Click to expand...
Click to collapse
In order to RUU you need to relock your device on HTCdev.com if you still have you unlock_cod.bin file you can skip going to HTC dev and put it in you Android folder you created back when you first unlock. S-off will not be lost nor do you need to S-On to flash the RUU.
make sure you have the SDK and HTC Sync installed. Go to fastboot in bootloader connect your USB cable so its says fastboot usb. Open a command window in the Android folder where you have adb fastboot files. Easiest way is shift right click open command window here. Once your device is connected just type in the command fastboot oem lock this will relock your device and you can now RUU. Once that is over you need to re unlock using the unlock code.bin file from HTC DEV and then flash amon ra recovery using the fastboot flash recovery(name).img and then you may install roms as you please. double check those commands although I am 90 percent positive they are correct commcands. The process I have described is corecct though as I just did this last night to update my radios. Good luck hope this helps
Also rename to the correct file name with the global RUU PH98IMG.img
zkrp5108 said:
In order to RUU you need to relock your device on HTCdev.com if you still have you unlock_cod.bin file you can skip going to HTC dev and put it in you Android folder you created back when you first unlock. S-off will not be lost nor do you need to S-On to flash the RUU.
make sure you have the SDK and HTC Sync installed. Go to fastboot in bootloader connect your USB cable so its says fastboot usb. Open a command window in the Android folder where you have adb fastboot files. Easiest way is shift right click open command window here. Once your device is connected just type in the command fastboot oem lock this will relock your device and you can now RUU. Once that is over you need to re unlock using the unlock code.bin file from HTC DEV and then flash amon ra recovery using the fastboot flash recovery(name).img and then you may install roms as you please. double check those commands although I am 90 percent positive they are correct commcands. The process I have described is corecct though as I just did this last night to update my radios. Good luck hope this helps
Also rename to the correct file name with the global RUU PH98IMG.img
Click to expand...
Click to collapse
AHHHHH, i thought i needed to be unlocked to flash an RUU. THANKS!
No problem my friend.
Sent from my ADR6425LVW using xda app-developers app