How do i unroot my Sprint HTC EVO 3D AND RETURN TO STOCK..
UNLOCKED
SHOOTER XC SHIP S-OFF RL
HBOO1.58.0000
THANKS!
Follow one of the multiple guides.
sent from MY BAD A$$ ET4G
patrao_n said:
Follow one of the multiple guides.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
what multiple guildes?
I myself just run the RUU when I want stock. It's simple.
Sent from my shooter using xda premium
Unroot Help
If you want to unroot, first find the Stock Hboot 1.58, then install it.
Then run the RUU for your device.
Lastly, in fastboot (adb), run "reboot bootloader" then run "fastboot oem writesecureflag 3".
Congrats, you will now be unrooted with bootloader *LOCKED*.
If you need any more help, feel free to PM me.
Boris Spektor said:
then run "fastboot oem writesecureflag 3".
Click to expand...
Click to collapse
DON'T RUN THIS.........
What are you trying to do?
Boris Spektor said:
If you want to unroot, first find the Stock Hboot 1.58, then install it.
Then run the RUU for your device.
Lastly, in fastboot (adb), run "reboot bootloader" then run "fastboot oem writesecureflag 3".
Congrats, you will now be unrooted with bootloader *LOCKED*.
If you need any more help, feel free to PM me.
Click to expand...
Click to collapse
raptoro07 said:
DON'T RUN THIS.........
What are you trying to do?
Click to expand...
Click to collapse
He said to run the RUU before issuing that command so it should be fine if the intent is to return to 100% stock, including S-ON. It's not really necessary to flash the stock bootloader before flashing the RUU but it might save having to restart the RUU if it hangs after flashing the bootloader. The OP said he was already on hboot 1.58 anyway.
You will also need to to lock the bootloader with a zip file in recovery since flashing the RUU doesn't do that. I have a guide here that includes everything you need.
Good luck!
ramjet73
ramjet73 said:
He said to run the RUU before issuing that command so it should be fine if the intent is to return to 100% stock, including S-ON. It's not really necessary to flash the stock bootloader before flashing the RUU but it might save having to restart the RUU if it hangs after flashing the bootloader. The OP said he was already on hboot 1.58 anyway.
You will also need to to lock the bootloader with a zip file in recovery since flashing the RUU doesn't do that. I have a guide here that includes everything you need.
Good luck!
ramjet73
Click to expand...
Click to collapse
When i reinstalled the stock Hboot manually (via bootloader) it showed *LOCKED* for me.
Just wondering, how does flashing a zip file in recovery, (which doesn't touch the Hboot) turn it *LOCKED*?
Boris Spektor said:
When i reinstalled the stock Hboot manually (via bootloader) it showed *LOCKED* for me.
Just wondering, how does flashing a zip file in recovery, (which doesn't touch the Hboot) turn it *LOCKED*?
Click to expand...
Click to collapse
That's because you were locked already and it just wasn't showing because the custom hboot masks that status.
There's a link to a thread that explains how the lock zip file works in this post.
ramjet73
Thanks guys for all your help....
Back to stock.
But my HBOOT is still showing S-OFF
SHOOTER XC SHIP S-OFF RL
How do iget S-OFF TO S-ON...
PSid not run this command yet..(fastboot oem writesecureflag 3)
Related
These steps will get you completely back to stock.
I want to first say thanks to the unlimited.io team for making S-OFF possible.
Secondly, by following these instructions you are acknowledging that should something go wrong and you brick your device, I am not at fault nor are the developers of the S-OFF method for the HTC RUBY. Follow these instructions at your own risk! I am NOT a dev, just stupid enough to be the first one (I think) To try this. I am not going to give instructions on how to use fastboot, if you are S-Off, then you should already know.
Third, you WILL be able to re-unlock your bootloader and regain S-OFF after you have followed these instructions. If you want to do so, there are other threads on how to do that.
And 4th, I have only tried this on a tmobile branded device. I have no idea if this works on any other device. I think it should, but I don't know for sure. If anybody wants to give it a try and let me know, then i will update the OP.
Now to the steps.
1. Download the stock ruu from here
2. Lock your bootloader by using the fastboot command "fastboot oem lock"
3. Reboot to system
4. Flash the stock RUU you downloaded by placing it in the root of your external sd card and renaming it PH85IMG.zip and rebooting to bootloader.
5. Once you have the stock rom reinstalled, set the security lock by using fastboot command " fastboot oem writesecureflag 3"
6. Profit?
That's it!
Special thanks to frodoboy for the idea and to krook6023 for posting the stock RUU's.
If this helped you at all, please remember to hit the thanks button!
Security lock by using fastboot command (S-ON) requires a stock RUU beforehand?
interesting
kaabob said:
Security lock by using fastboot command (S-ON) requires a stock RUU beforehand?
interesting
Click to expand...
Click to collapse
I should have clarified, the steps are if you want to go completely stock, will update the OP.
Will it read "relocked" or "locked"? I thought being "completely stock" was not totally possible because it would always say "relocked".
Sent from my HTC_Amaze_4G using XDA
bjcolema said:
Will it read "relocked" or "locked"? I thought being "completely stock" was not totally possible because it would always say "relocked".
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
kishon120 said:
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
Click to expand...
Click to collapse
That's good to know. Thanks.
Sent from my HTC_Amaze_4G using XDA
kishon120 said:
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
Click to expand...
Click to collapse
Thanks for replying.
This is correct, my phone said locked, not relocked.
I would like to stress that YOU NEED A FULL RUU, not a stock nandroid backup. Otherwise, you are going to need that link on my sig
Sent from my HTC Sensation using XDA
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Thaxtonator said:
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Click to expand...
Click to collapse
You can't downgrade back to GB once you've updated to ICS, if that's what you're trying to do. At least not very easily.
electronicrice said:
You can't downgrade back to GB once you've updated to ICS, if that's what you're trying to do. At least not very easily.
Click to expand...
Click to collapse
If you are S-Off, then following this guide will put you back to stock gingerbread.
Thaxtonator said:
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Click to expand...
Click to collapse
I dont know a way for going back to stock without being s=off. You could possibly flash the newest official release (ics, one that hasnt been modified) then relock your bootloader, but i think that it will show relocked rather than locked. Worth a try though.
Okay thanks for the input guys. It isn't a huge deal, I just didn't think there was enough "goodies" rom-wise for ICS, but there are some hardworking devs on here. Looking forward to the Sense 4.0 rom.
dcmtnbkr said:
Special thanks to frodoboy for the idea and to krook6023 for posting the stock RUU's.
If this helped you at all, please remember to hit the thanks button!
Click to expand...
Click to collapse
Thanks for the "thanks" dcm. Question though. I'm sure you've gone back to S-Off so did you have to do the wire trick again or just try the fastboot oem writesecureflag 0 or whatever it needs to be to go S-Off again?
frodoboy said:
Thanks for the "thanks" dcm. Question though. I'm sure you've gone back to S-Off so did you have to do the wire trick again or just try the fastboot oem writesecureflag 0 or whatever it needs to be to go S-Off again?
Click to expand...
Click to collapse
When s-on, you can't go back to s-off by writing the security flag again . You have to do again the juopunutbear procedure including the wire trick
Sent from my HTC Sensation Z710e
Just curious which RUU one should flash if returning to stock?
RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14. 550L.17DC_30.78.550L.15_release_257469_signed.zip
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip
PH85IMG_Ruby_TMOUS_1.36.531.6_Radio_1.07.550L.04DC _30.64.550L.07_release_219373_signed.zip
3oudreaux said:
Just curious which RUU one should flash if returning to stock?
RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14. 550L.17DC_30.78.550L.15_release_257469_signed.zip
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip
PH85IMG_Ruby_TMOUS_1.36.531.6_Radio_1.07.550L.04DC _30.64.550L.07_release_219373_signed.zip
Click to expand...
Click to collapse
This one would be best: RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
I spent 3 hrs trying to solve the relocked and locked issue until finally I got it resolved. with the manual option to lock with hasoon tool, places *** RELOCKED *** in hboot, which clearly and obvious for any technician to see you tampered with the hboot files from stock. my reason for doing this to get my warranty back.
how did i fixed "RELOCKED" to show as *** LOCKED *** ? after the hasoon tool 3.2 relocked the bootloader i was challenged, but decided the first step would be switching the security off and on (s-off/ s-on)
first return to stock RUU through boot loader, then adb command fastboot oem writesecureflag 3 to enable s-on. *toggled it on
i reinstalled juopunutbear s-off again carefully following the instructions. with a paperclip grounding the phone and selecting for juopunutbear's modified files "y" enter.
then your *** RELOCKED *** shows as *** juopunutbear *** in hboot. (at first i thought I dig myself a bigger hole)
I used Hasoon tool 3.2 again to RELOCK bootloader, with the intention of reinstall the stock RUU again. however it still showed as *** juopunutbear *** with the message its already locked.
Now I installed the the Stock RUU again from bootloader. once complete back to the hboot, to show *** LOCKED *** and s-off Progress!!!
repeat enable s-on instructions by writing adb: fastboot oem writesecureflag 3,
now shows
*** LOCKED ***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
OpenADSP-02.6.0.2226.00.0202
eMMC-boot
a step closer for the warranty being back to the device, without a dispute with the warehouse/ carrier
how do we delete the line -OpenADSP-02.6.0.2226.00.0202?
it was added with the juopunutbear s-off hboot files, without that file the hboot would be 100 percent legit for the warranty!
aoakes said:
how do we delete the line -OpenADSP-02.6.0.2226.00.0202?
it was added with the juopunutbear s-off hboot files, without that file the hboot would be 100 percent legit for the warranty!
Click to expand...
Click to collapse
No need to get rid of that. New phone from T-Mobile with HBOOT 1.93 and it had that line it . It looks like 1.90 is the one that doesn't have that line. Because my wife's phone is on 1.90 and she doesn't have it.
I'm going to be following the method in a few days. Can you guys confirm this all works as it should?
has anybody succesfully gotten rid of ***RELOCKED*** on the 3d after rooting? i went back to stock so i am s-on again but want to get rid of the relocked message.
I have a gsm model. Reflashed ruu via pg86img to older version from my carrier. Then fastboot command 'fastboot oem writesecureflag 3' and then I was back to s-on showing lock not relock
I was revolutionary s-off
Sent from my HTC EVO 3D X515m using Tapatalk 2
healer82 said:
I have a gsm model. Reflashed ruu via pg86img to older version from my carrier. Then fastboot command 'fastboot oem writesecureflag 3' and then I was back to s-on showing lock not relock
I was revolutionary s-off
Sent from my HTC EVO 3D X515m using Tapatalk 2
Click to expand...
Click to collapse
Same here got the ruu from xda then run the ruu then head to %TEMP% folder in windows and copy the rom.zip then rename it to PG86IMG.zip place it on sd , boot into bootloader on phone and update. this makes your phone like brand new from factory then connect to pc open command prompt and type "fastboot oem writesecureflag 3" this turns s-off too s-on after this reboot bootloader and you will see ***locked*** s-on
But to do that, you have to be s-off first.
Otherwise there's no way to flash the img via bootloader if i'm not mistaken.
I just tried it (s-on / relocked) and neither the flashing or the fastboot command works unfortunately
KrewsialNL said:
But to do that, you have to be s-off first.
Otherwise there's no way to flash the img via bootloader if i'm not mistaken.
I just tried it (s-on / relocked) and neither the flashing or the fastboot command works unfortunately
Click to expand...
Click to collapse
cant you use the revolutionary method to s-off then flash the ruu zip? then use the command to s-on again. worked for me on hboot 1.4.9.0018 this gives you ***locked*** not relocked!
sonya chin said:
cant you use the revolutionary method to s-off then flash the ruu zip? then use the command to s-on again. worked for me on hboot 1.4.9.0018 this gives you ***locked*** not relocked!
Click to expand...
Click to collapse
I have no clue, i have never been s-off
Sent from my HTC EVO 3D X515m using xda premium
and after you do this LOCKED thing if I go with the phone for warranty they will never know that I had root,will they?
johnmarshton said:
and after you do this LOCKED thing if I go with the phone for warranty they will never know that I had root,will they?
Click to expand...
Click to collapse
Warranty with who? If sprint, they don't even care, you don't need to do all this...
Sent from my PG86100 using XDA
Im having the issue when I put the zip file on my sd card it shows no image in bootloader. I renamed it correctly and im relocked with s-on. im trying to root my 3d.
jamexman said:
Warranty with who? If sprint, they don't even care, you don't need to do all this...
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
HTC Warranty.I'm from Europe
ok i do have sprint...i want the locked message...not relocked.
For me on Sprint version, no matter what I did it would show relocked if I was on hboot 1.50. If i was on hboot 1.40 it was fine. So I stayed 1.40 on went s-on. But HTC may actually upgrade it and check. Not sure.
so if im hboot 1.50 and root, i could downgrade to 1.40 then flash a ruu to loose root and it will show locked in stead of relocked?
does this work if i unlocked the bootloader with the HTCDev method instead of revolutionary?? my evo 3d is GSM
is there a way to get the bootloader back to a pure "locked" designation?!?!
Yes, but it requires performing the S-Off method. Only way it can be done.
rezin said:
is there a way to get the bootloader back to a pure "locked" designation?!?!
Click to expand...
Click to collapse
only if youre s-off
Edit: ninja'd lol
rezin said:
is there a way to get the bootloader back to a pure "locked" designation?!?!
Click to expand...
Click to collapse
Do S-off procedure. That procedure changes the bootloader back to "locked" whenever you go through it as well. You can observe this on an hboot other than JuopunutBear's modded one.
If you want it stock, you have to re-flash a stock RUU and do S-on procedure; check the guide in the Development section.
okay i just ran the newest ruu and noticed it when i rebooted to bootloader...so all i gotta do is run it one more time...then when its fully s-off and labeled "locked" just run the secureflag 3 command again?!?!
rezin said:
okay i just ran the newest ruu and noticed it when i rebooted to bootloader...so all i gotta do is run it one more time...then when its fully s-off and labeled "locked" just run the secureflag 3 command again?!?!
Click to expand...
Click to collapse
Yes you writesecureflag on
So does that mean that you can do the following?
1. S-Off
2. Bootloader shows and "locked" instead of "relocked".
3. S-On
4. Run RUU
5. Warranty replacement with no worries
Nevermind I didn't read the op right :/
das0527 said:
So does that mean that you can do the following?
1. S-Off
2. Bootloader shows and "locked" instead of "relocked".
3. S-On
4. Run RUU
5. Warranty replacement with no worries
Click to expand...
Click to collapse
Then run the RUU *before* S-On... all else before S-On. You must make sure that is stock bootloader and not JuopunutBear or else you risk bricking when writing the security flag command.
And be sure to run the RUU twice to ensure a complete flash.
Also note the JuopunutBear bootloader, if flashed, will read "JuopunutBear" instead of Locked and indeed performs similar to an unlocked stock bootloader. But that JB version is simply hacked; once you flash a stock bootloader over that, it will read Locked.
http://forum.xda-developers.com/showthread.php?t=1612937
Note with that article you may want to do the ICS OTA RUU instead now that it is out.
Hi,
My Evo 3d GSM device was S-OFF by the Revolutionary method.
All work fine.
But for garanty purpose, l've already restored boot_signed and system.img from stock rom.zip
Can i restore original recovery with:
fastoot flash recovery recovery_signed.img ?
And Restore stock hboot with:
fastoot flash hboot hboot_SHR_U_1.53.0007_20120522_signedbyaa.nb0 ?
Thank before,
If you really want to go back to stock, run the ruu for your region/carrier. It will leave you s-off, but everything else stock. You could go 100 percent stock by going back to s-on first. EDIT: After! See ramjet's post below.
Imagika FTW... with Tapatalk 2
Running the RUU should restore the default recovery and leave you s-off if it is going in for warranty work don't forget you want to be s-on (fastboot oem lock) after running the RUU.
coal686 said:
If you really want to go back to stock, run the ruu for your region/carrier. It will leave you s-off, but everything else stock. You could go 100 percent stock by going back to s-on first.
Click to expand...
Click to collapse
ItzCrooK2UxD said:
Running the RUU should restore the default recovery and leave you s-off if it is going in for warranty work don't forget you want to be s-on (fastboot oem lock) after running the RUU.
Click to expand...
Click to collapse
That's the command to relock after doing the HTC unlock. The command to set S-ON is "fastboot oem writesecureflag 3" and should only be run after the RUU is flashed and the stock bootloader is restored. If S-ON is set while a modified bootloader such as ENG, Revolutionary, or Juopunutbear is installed it will brick the phone.
ramjet73
ramjet73 said:
That's the command to relock after doing the HTC unlock. The command to set S-ON is "fastboot oem writesecureflag 3" and should only be run after the RUU is flashed and the stock bootloader is restored. If S-ON is set while a modified bootloader such as ENG, Revolutionary, or Juopunutbear is installed it will brick the phone.
ramjet73
Click to expand...
Click to collapse
So ramjet: if s-on, you lock then run ruu. But if s-off, you run ruu then lock if you wish. Is that right? I know it's a different kind of lock, but i didn't realize order mattered going s-off to s-on.
Imagika FTW... with Tapatalk 2
coal686 said:
So ramjet: if s-on, you lock then run ruu. But if s-off, you run ruu then lock if you wish. Is that right? I know it's a different kind of lock, but i didn't realize order mattered.
Click to expand...
Click to collapse
Yes, those are separate S-OFF's. The bootloader unlock (hboot S-OFF) is different from the radio S-OFF. This post from the MeanROM ICS thread has an explanation by Unknownforce, the developer behind the the hboot 1.4 downgrade method for radio S-OFF.
The "fastboot oem lock" command will undo the bootloader S-OFF, which is required to run the RUU.exe for users that are radio S-ON. Users that are radio S-OFF can run the RUU.exe without any special considerations.
Once the RUU.exe is run and the stock bootloader is installed, the phone will be bootloader S-ON regardless of the radio S-OFF status. To run fastboot commands like "flash" and "erase" the stock bootloader needs to be unlocked by the htcdev method or a custom bootloader modified to support those commands needs to be flashed, which requires radio S-OFF.
After installing a custom bootloader, setting radio S-ON via the "fastboot oem writesecureflag 3" bricks the phone because the bootloader is not signed by HTC and that is not allowed with radio S-ON. Therefore a stock bootloader needs to be reinstalled before setting radio S-ON and the easiest way to do that is flash an RUU.exe.
Hope that makes sense.
ramjet73
Makes perfect sense. Thanks boss. Learn something new everyday. :thumbup:
Imagika FTW... with Tapatalk 2
Thank-you very much for all your post, and a special thank to ramjet73.
It's clear now, but I will try tomorow.
result
Hello,
After all your explanations, I was reassured to install "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe"
Unfortunately it did not work: probably due to the absence of CID (HTC__203) of the revolutionary HBOOT.
So I took the rom.zip file in the% temp% directory and I renamed PG86IMG.zip. I pushed on my sdcard.
A reboot in the bootloader and the EVO 3D has successfully installed the ROM with firmware radio, recovery, system ... in short, everything
Now my HBOOT is 1.53.0007 HTC, it does not show revolutionary, but it is unlocked and S-OFF
Now I think it is acceptable to send like that. What do you think?
In fact I've not said what the problem was my phone: After installing a ROM that had the good idea to turn xLOUD (I think that's it) it has blown me the speaker (communication only)
Thank you again for your help
The latest changes
fxjumper said:
Now my HBOOT is 1.53.0007 HTC, it does not show revolutionary, but it is unlocked and S-OFF
Now I think it is acceptable to send like that. What do you think?
Thank you again for your help
Click to expand...
Click to collapse
Ok, i dit it !
Code:
fastboot oem lock
relocked my phone
and
Code:
fastboot oem writesecureflag 3
put my phone S-ON ! (radio)
Everything was fine in the end? I'm in the exact same situation and I'm installing PG86IMG.zip as we speak. Did HTC see anything wrong with your phone?
i rooted my girlfriends sprint evo 3d using unknownforce's down grade method, i wanna return her phone back to complete stock how would i do that? she is s-off right now. thanks for the advice
You could flash an ruu from bootloader since your s-off. Here's a link for a list of ruu pick the one that says ics shooter 35 s 2.89 1.09.00.0706 spcs wwe to that nature http://www.filefactory.com/f/4ef0ef536face67a/. Just remember to rename the file PG86IMG in all caps and place on the root of your sdcard. Power down your phone, and boot up into bootloader and let your phone detect the file and confirm to update. Next you might want to get a drink or something to eat. It'll take like 10 minutes. Hope that helps
Jsparta26 said:
You could flash an ruu from bootloader since your s-off. Here's a link for a list of ruu pick the one that says ics shooter 35 s 2.89 1.09.00.0706 spcs wwe to that nature http://www.filefactory.com/f/4ef0ef536face67a/. Just remember to rename the file PG86IMG in all caps and place on the root of your sdcard. Power down your phone, and boot up into bootloader and let your phone detect the file and confirm to update. Next you might want to get a drink or something to eat. It'll take like 10 minutes. Hope that helps
Click to expand...
Click to collapse
that will revert the s-off to right?
wikedone said:
that will revert the s-off to right?
Click to expand...
Click to collapse
No.
You need to issue the "fastboot oem writescureflag 3" command with the phone in fastboot USB mode after flashing the RUU to reset the S-OFF status to S-ON. Make sure you have the stock bootloader installed before you do that.
ramjet73
ramjet73 said:
No.
You need to issue the "fastboot oem writescureflag 3" command with the phone in fastboot USB mode after flashing the RUU to reset the S-OFF status to S-ON. Make sure you have the stock bootloader installed before you do that.
ramjet73
Click to expand...
Click to collapse
ok the file i downloaded is RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe i just rename that to PG86IMG or what cuz when i run the ruu in windows it errors out with usb connectio error
wikedone said:
ok the file i downloaded is RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe i just rename that to PG86IMG or what cuz when i run the ruu in windows it errors out with usb connectio error
Click to expand...
Click to collapse
The .exe version of the RUU needs to be run from Windows. Make sure your phone is in the "fastboot usb" mode in the bootloader and the "fastboot devices" command returns your serial number before you run the RUU.
There's also a .zip version of the RUU around somewhere on these forums that can be run from the bootloader, but I don't have a link to that. It would be safer to extract it yourself from the RUU.exe using this procedure.
ramjet73
ramjet73 said:
The .exe version of the RUU needs to be run from Windows. Make sure your phone is in the "fastboot usb" mode in the bootloader and the "fastboot devices" command returns your serial number before you run the RUU.
There's also a .zip version of the RUU around somewhere on these forums that can be run from the bootloader, but I don't have a link to that. It would be safer to extract it yourself from the RUU.exe using this procedure.
ramjet73
Click to expand...
Click to collapse
ok i got the ruu to run and the phone is updated to ICS the hboot says
*** LOCKED ***
SHOOTER XC SHIP S-OFF RL
HBOOT-1.58.0000
RADIO-1.09.00.0706
OpenADSP-v02.6.0.2226.00.0217
eMMC-boot
May 17 2012, 15:06:44
How do i know if i have the stock bootloader so i can Make it S-On
wikedone said:
ok i got the ruu to run and the phone is updated to ICS the hboot says
*** LOCKED ***
SHOOTER XC SHIP S-OFF RL
HBOOT-1.58.0000
^^^^^^^^^^^
How do i know if i have the stock bootloader so i can Make it S-On
Click to expand...
Click to collapse
That's the stock bootloader, which was installed by the RUU. Most of the custom bootloaders (Revolutionary, Juopunutbear) have their name where the "*** LOCKED ***" status shows on your phone.
ramjet73
It's also courtesy to hit the thank you button when someone has helped you (meaning ramjet) Just thought I would throw that out.