Related
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 bought Evo which was already upgraded to ICS (OTA I assume), and it was branded I think. I've unlocked it via HTCDev, flashed '4ext touch recovery' and then rooted. Then I flashed MIUI ICS ROM, and everything is OK for now.
I want to use BootManager to flash multiple ROMs. It requires s-off. I tried it already with s-on, because I've read that SmartFlash (from 4ext recovery) makes my phone like s-off, so ROM on SD card installed, but won't boot. I had many problems going back to my Phone ROM, I restored my backup, wiped many times, installed fresh ROM and still had a bootloop. Finally I got it working again by flashing boot.img via fastboot (glad I did nandroid backup before). I didn't try again with different ROM, because after 2 hours of trying to recover my base ROM I've had enough. So I'm pretty sure BootManager will work better if my phone will be s-off.
So my question is - what to do next? We have so many guides and different comments here, sometimes the same method works for one, and doesn't work for another one, and I'm really confused.
I assume I should follow the instructions here http://forum.xda-developers.com/showthread.php?t=1743466 but I don't understand few things:
friend.evil said:
flash an ICS ROM from recovery(Method B from 10 to 14)
open ICS ROM.zip and extract boot.img to a folder which contains adb, fastboot and AdbWinApi.dll
go to fastboot and type:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Do I have to do this if I'm already have MIUI with root privileges? Do I still need that boot.img from MIUI, and put it together with fastboot.exe?
Or should I restore stock ICS? I'm pretty sure I did nandroid backup before flashing MIUI.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
Do I need to fix hboot after s-off? What hboot version I have after doing steps 1 to 4 from section E? There's a big zip file (PG86IMG.zip), is it another ROM or what?
And most important question - if method D doesn't work, method F is recommended, but:
elias17 said:
Hboot s on will only flash roms that are based on ics 3.28xx and sense 4 roms using a special boot.img ! U can never flash GB roms until u go s off like i did its a tricky process but it works and now i can flash any rom in the gsm section
Click to expand...
Click to collapse
friend.evil said:
2_flash Leedroid GB ROM from recovery http://leedroid.ftp.rshost.eu/Shoote....zip(Don't forget to wipe data/factory reset and wipe cache + dalvik)
Click to expand...
Click to collapse
I don't get it - can I flash GB ROM or not if I have hboot 1.53.0007 s-on? Can I use method F if method D fail?
Sorry for my english, I'm from Poland.
Thanks in advance for any tip.
You're confusing yourself, What you need to do my friend is.
1. Download RUU, Run RUU
2. HTC Unlock bootloader again
3. Do the Juopunutbear Wiretrick to get s-off
4. Download the 1.04 ENG hboot (There is one of those for the GSM I think... not sure though)
5. Flash a badass Android 4.2.1 rom. They work.
There's much more detailed guides on what to do, BUT This is a summary of what you want.
Be sure to hit thanks [= I'm almost to 100
Which RUU should I search for? GB or ICS?
But isn't the 1+2 the same as restoring my ICS Stock ROM from backup?
I think hboot 1.49.0007 would be enough, I've read that BootManager works well with that version.
1. Yes you can just restore your stock ics backup BUT you will have to root it using the file provided in method B.
2. Yes the 1.49.0007 hboot is best for gsm
3. You can flash a GB rom with your hboot no problem. It just dont think it will boot. so technically you should be able to do the wire trick with a GB rom flashed(not booted into). You'll be in fastboot mode for the wiretrick. There are different files for GB and ICS when doing the wiretrick
Your best bet is to run an ICS RUU, unlock bootloader, root rom, do the wire trick, change hboot to 1.49.0007 and then flash any rom you want
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
mars28 said:
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
Click to expand...
Click to collapse
That should work But unlocking again is really easy
You should still have you unlock token in the same place,
You just plug up to the computer hop into fastboot usb and type
Fastboot flash unlocktoken Unlock_Code.bin
to unlock and then
fastboot flash recovery recovery.img
for a recovery,
Then move SU to your sd card and flash it in recovery.
Then your all ready for the wire trick, The more you do these things the more experience you get at them and the better you get with fastboot. I suggest you go through the process opposed to just restoring (First off it's much much safer) and you'll know the ropes if you (or anyone else) has this problem.
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "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" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "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" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
The token and the unlock code are specific to the phone, And doesn't change until you get a new phone.
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "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" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
you can easily get a new token from htc dev web site
Sent from my HTC EVO 3D X515m using xda app-developers app
Can't_Live_Without_My_Evo said:
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
Click to expand...
Click to collapse
I know I use shooter_u, I asked because I've found another RUU which have "Rogers_WWE" in name of the file, and the rest of the file name is identical, and I remember that I had to choose "rogers" when I was unlocking via htcdev. That's why I wasn't 100% sure if I had to choose "HTC_Europe" or "Rogers_WWE".
Another thing which confuses me:
http://forum.xda-developers.com/showthread.php?t=1495358
mpgrimm2 said:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
Should I do this or start directly with RUU.exe? My phone is currently "UNLOCKED, hboot 1.53.0007, s-on".
And what about CID? I've read somewhere that I have to change to supercid or something, to be able to flash zips via fastboot. How to check my current CID?
Search for cid getter on play store to get your cid
You certainly need to relock you hboot before running RUU. For the correct ruu you should check the box that your phone came in. It should have the details (atleast i think so)
P.S. you probably don't need to change cid. Infact i'd recommend you not to do that just yet
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
mars28 said:
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
Click to expand...
Click to collapse
I think yours might be an european model. i had the exact same cid as yours.
when you get to that step of corrupted hboot just follow the steps on this thread and flash hboot 1.49.0007
http://forum.xda-developers.com/showthread.php?t=1906172
Cant kive without my evis comments about the wire trick are bang on. It will fix everything. Having s-off is just much easier so do the wire trick. It will work. My wife and I both have an evo. I had to do the wire trick twice on hers for it to work and four times on mine for it to work. Be patient if it fails the first few times. And if the screen gets stuck on the jounuo whatever screen you can fix that.
If you are stuck at Juopunutbear screen and if you can go to bootloader you need to connect the phone to pc, go to fastboot ( should say fastboot usb)*Go to controlbear folder (from where you ran controlbear to begin withon you pc then open command window in it (hold shift and right click, that willopen command window rigjt there and then*when you get into it you need to enter:
"ControlBear.exe -f" no quotes or "ControlBear f" notice the space after the exe !
Lots of peopke forget to put it in and say it didnt work.
I presume this will fix the problem
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
My phone is now s-off. I didn't flash RUU, just restored stock rooted ROM from backup, did the wire trick (just one time, surprisingly) and everything went nice and smooth. Then I flashed hboot 1.49.0007 with no problems at all. Thanks guys for the tips.
One more thing - my phone state is now "LOCKED" - should I bother?
So I got what I wanted - I've installed ROM in BootManager (the one which doesn't boot before, while phone was 's-on') and this time it booted from SD. Today I'll try more ROMs in BootManager.
Locked doesn't matter as long as you are s-off. It only creates problems if you ever plan on using fastboot commands. Trust me, you dont need to bother with it
But if you really want to know heres a quote from ramjet where he explains it a bit.
ramjet73 said:
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.
Click to expand...
Click to collapse
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
silenthatred said:
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
Click to expand...
Click to collapse
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
silenthatred said:
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
Click to expand...
Click to collapse
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
silenthatred said:
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
Click to expand...
Click to collapse
This happens sometimes if you have a custom bootloader installed when you flash the RUU. Just cancel the Windows task and restart it and you should be fine.
ramjet73
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
silenthatred said:
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
Click to expand...
Click to collapse
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
Click to expand...
Click to collapse
Why is this? Is there not a full RUU for the latest version?
ramjet73 said:
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
silenthatred said:
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
Click to expand...
Click to collapse
Does it still say ** LOCKED ** Or does it say ** UNLOCKED ** now?
Unknownforce said:
Why is this? Is there not a full RUU for the latest version?
Click to expand...
Click to collapse
No. Virgin Mobile released an OTA update in November but there's no RUU that corresponds to it available yet. Fortunately, the bootloader version didn't change so the original RUU can be flashed with S-ON if the mainver is set low, but you need to be unlocked and rooted already to flash the zip file that does that.
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
Click to expand...
Click to collapse
That would be a problem for him then. I don't know of anyway to flash the RUU with S-ON after the OTA has been installed if the bootloader is actually locked and he can't unlock it.
ramjet73
Yeah, not looking good. Thanks for the help though!
It seems like the questions about returning to 100% stock are coming up more often lately, possibly because more users are moving on to other devices. Whatever the reason, I thought a simple guide might be useful to avoid having to duplicate this info in other threads and PM's.
This procedure should work for any CDMA or GSM Evo 3D/V that is S-OFF. There is no way to get an S-ON device that has been HTC unlocked back to 100% stock since relocking the bootloader will result in a status of "relocked".
Here are the steps to do it:
1. Flash the "query_bootloader.zip" file attached to this post in recovery. If the status message shows your bootloader is "unlocked" or "relocked" flash the "lock_bootloader.zip" file from the same post to reset it to "locked".
2. Download an RUU.exe (Windows) or RUU.zip (bootloader) file for your model from this page and flash it using the appropriate method.
If you use the .exe version from Windows it works best if you put the phone into "fastboot USB" mode, and you may have to cancel the RUU utility and restart if it hangs after flashing the stock bootloader when you start with a custom hboot installed.
To flash the RUU.zip via the bootloader it must be renamed to PG86IMG.zip and placed in the root of your SD card, and may need to be flashed twice if a custom hboot is installed the first time it is flashed.
I recommend using the latest version for your model but any compatible RUU can be flashed while S-OFF. It's also a good idea to boot the ROM without doing any setup after flashing the RUU to make sure the ROM has been reset to the stock version.
3. Confirm that the bootloader shows "***LOCKED***" on the top line of the screen and the HBOOT version is a stock bootloader for your device.
4. Issue the "fastboot oem writesecureflag 3" command from a PC.
Note: Make 100% sure you have the stock bootloader installed before issuing this command or you will brick your phone.
Your phone will now be 100% stock.
ramjet73
Thanks for the nice toturial but i´m just wondering one thing.
If you fail with the command
Code:
fastboot oem writesecureflag 3
, will your phone get hardbricked or is it possible to flash a recovery and start over again with fastboot?
dR.BaNaNe said:
Thanks for the nice toturial but i´m just wondering one thing.
If you fail with the command
Code:
fastboot oem writesecureflag 3
, will your phone get hardbricked or is it possible to flash a recovery and start over again with fastboot?
Click to expand...
Click to collapse
If that command fails nothing will happen and your phone will stay S-OFF but the odds of that happening are very small unless your phone is not in "fastboot usb" mode when you issue it.
The risk involves issuing that command when you have a custom hboot like JBear or Revolutionary installed because those bootloaders are not signed and will cause the phone to brick. In that scenario you would not be able to get into recovery.
ramjet73
Ok thanks man.
Ok, in the RUU's I can download I have 2 problems:
1) How do I know which one to download? I see a few that have Sprint ICS. I have the Virgin Mobile phone Evo V 4g. Which one would I get?
2) I have already tried downloading a few of them, and each time it stops at a different point and windows says the zip file is not valid. Is there another place I can download the correct RUU?
I need to get this done soon as I have a replacement headed this way.
matt965 said:
Ok, in the RUU's I can download I have 2 problems:
1) How do I know which one to download? I see a few that have Sprint ICS. I have the Virgin Mobile phone Evo V 4g. Which one would I get?
Click to expand...
Click to collapse
This is the correct RUU for your phone.
2) I have already tried downloading a few of them, and each time it stops at a different point and windows says the zip file is not valid. Is there another place I can download the correct RUU?
Click to expand...
Click to collapse
If that link doesn't work for you the same RUU is available here, including an MD5 checksum you can use to verify the download.
I need to get this done soon as I have a replacement headed this way.
Click to expand...
Click to collapse
ramjet73 said:
1. Flash the "query_bootloader.zip" file attached to this post in recovery. If the status message shows your bootloader is "unlocked" or "relocked" flash the "lock_bootloader.zip" file from the same post to reset it to "locked".
Click to expand...
Click to collapse
how do i do this if i have no working recovery? iv been trying to ruu with RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_219445_signed.exe
iv tried many ruu's but only 2 have ever gone through. when it does i just get reboots on htc screen. recovery does not seem to work.
thanks for the help. hope i havnt bricked my phone
birddseedd said:
how do i do this if i have no working recovery? iv been trying to ruu with RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_219445_signed.exe
iv tried many ruu's but only 2 have ever gone through. when it does i just get reboots on htc screen. recovery does not seem to work.
thanks for the help. hope i havnt bricked my phone
Click to expand...
Click to collapse
This is the wrong thread for what you need to do and I posted a link to the correct guide in the thread you opened in the development forum that got moved to Q&A.
When you are ready to download the RUU look for the 2.89.651.2 version.
ramjet73
thank you ramjet for the link. my phone is now 99% stock. The 1% is because of the S-OFF part of the bootloader. It shows it is locked so that's good, but I think that means I can't turn S-ON, as it says in the first post. Oh well, hopefully they will accept it like that.
matt965 said:
thank you ramjet for the link. my phone is now 99% stock. The 1% is because of the S-OFF part of the bootloader. It shows it is locked so that's good, but I think that means I can't turn S-ON, as it says in the first post. Oh well, hopefully they will accept it like that.
Click to expand...
Click to collapse
if you figure out how to get jb roms to boot post back so we all can know how
birddseedd said:
if you figure out how to get jb roms to boot post back so we all can know how
Click to expand...
Click to collapse
JB roms don't boot with this phone??? Strange since mine booted just fine with them.
matt965 said:
JB roms don't boot with this phone??? Strange since mine booted just fine with them.
Click to expand...
Click to collapse
They do.
This is the wrong thread to discuss booting JB ROM's and I don't know why he posted that here.
ramjet73
Thanks for this thread, great to go back to 100% stock for warranty purposes...
But for sellers who's warranty has run out, the newest JB or ICS rom is the best
Which RUU do i use for a Sprint Evo 3?
I'd like to follow the instructions here; you pointed me to this OP in another reply when I asked how to go back to stock, but I don't know which one to use. I'm on hboot 1.50.5050 running CM 10.1 on a Sprint Evo 3D, using "Wild for the Night" and I want to go back to 100% stock, S-ON, unrooted, locked.
Is 'WWE' the US version? I know not to use RUUs for other countries but I can't tell which to use from the list.
(I used the jbear wire trick and have Ext4 installed if it makes any difference.)
occulus said:
I'd like to follow the instructions here; you pointed me to this OP in another reply when I asked how to go back to stock, but I don't know which one to use. I'm on hboot 1.50.5050 running CM 10.1 on a Sprint Evo 3D, using "Wild for the Night" and I want to go back to 100% stock, S-ON, unrooted, locked.
Click to expand...
Click to collapse
This is the RUU you want to use.
ramjet73
Does it work for EVO 3D GSM with Revolutionary?
Sorry for my english.
ramjet73 said:
This procedure should work for any CDMA or GSM Evo 3D/V that is S-OFF. There is no way to get an S-ON device that has been HTC unlocked back to 100% stock since relocking the bootloader will result in a status of "relocked".
Click to expand...
Click to collapse
t_mcpardi said:
Does it work for EVO 3D GSM with Revolutionary?
Sorry for my english.
Click to expand...
Click to collapse
Probably not, since ramjet said that in the OP.
t_mcpardi said:
Does it work for EVO 3D GSM with Revolutionary?
Sorry for my english.
Click to expand...
Click to collapse
raptoro07 said:
Probably not, since ramjet said that in the OP.
Click to expand...
Click to collapse
If he has Revolutionary and is S-OFF this guide should work as long as the RUU is available for the model of his phone. That's the only thing that is specific to the GSM or CDMA model.
ramjet73
Which ruu do I use I'm running hboot 1.50.5050 and bootloader is unlocked
rafylora1230 said:
Which ruu do I use I'm running hboot 1.50.5050 and bootloader is unlocked
Click to expand...
Click to collapse
The hboot doesn't matter, but if you are on Virgin Mobile you need this one.
ramjet73
So, I have a dilemma. I am currently S-ON running TACHYON 1.2 (Android 4.3)
HBOOT 2.28.0000
Radio 2.23.10.0123/4
I updated the hboot and radio while S-ON. Now, I've decided I'd like to go S-OFF. According to JuopunutBear I need to be on a stock RUU for their S-OFF to work. I tried running the newest ICS RUU a few weeks ago and found that it would just error out when it was checking the file because the radios and hboot on the phone were newer than the ones on the RUU. Can I step backwards in HBOOT versions whlie S-ON or have I kind of screwed myself? Or is there a better option I haven't thought about?
Thanks
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Uzephi said:
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
It's a stock hboot, yes. But the RUU won't run because it is an older version hboot.
You need s-off to downgrade. Just install a stock based Rom that is rooted and run s-off procedure. You will have no issues. After s-off if you want, you can ruu
Sent from my DNA using my mind.
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
jeff925 said:
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
Click to expand...
Click to collapse
A stock rooted RUU would work. I was in your predicament once. First, do a nandroid backup then use this guide it'll get you to s-off. If you want to downgrade, then use this guide to accomplish this.
Thanks guys for the help. Installed the rom listed in the guide and it worked great. S-OFF now!! (Took me long enough...I've had the phone for 2 years!)
It installed JuopunutBear's hboot but whatever. I'd probably rather stick with a stock hboot but I can do that later.
Restored my nandroid backup and I'm back up and running like I never left.
Just flash this ROM and boot image, and you should be able to S-OFF, I can't remember if stock recovery is needed but that can be flashed separately as well if needed, but I don't think it is.
http://forum.xda-developers.com/showthread.php?t=2260154
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
jeff925 said:
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
Click to expand...
Click to collapse
In fastboot does it say s-off? Try manually flashing the boot.img by extracting it. If you haven't setup enviroment variable for fastboot put the boot.img in the same directory as fastboot.exe and use command prompt by typing
Code:
cd C:\Android\platform-tools (or wherever it is for you)
Then type
Code:
fastboot flash boot boot.img
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
You can unlock when S-OFF, but there is no reason to, you can get a PH98img.zip of CWM here: http://forum.xda-developers.com/showthread.php?t=1914215 or TWRP here: http://forum.xda-developers.com/showthread.php?t=1902381 and just copy it to your sd card (remember to name it exactly PH98IMG.zip, beware the Windoze "double zip" issue) then pop it in the phone, boot into Hboot with the USB disconnected and it should recognize it and flash either CWM or TWRP. from there you can flash ANYTHING you want, being S-OFF with custom recovery allows you to flash anything, no fastboot commands required.
Also, since you are S-OFF, your Hboot is mostly irrelevant, but should be the matching version to your radios... an engineered hboot (like Juopunutbears) would allow fastboot commands well locked, but fastboot isn't generally needed once S-OFF has been obtained...
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
4218kris said:
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
Click to expand...
Click to collapse
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
and what recovery problems are you having....flashing an hboot will not give you a recovery...and an ruu is an exe file not a ph98img file...those are OTA's.....if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
REV3NT3CH said:
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
Click to expand...
Click to collapse
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
that one or the this 2nd ph98img in my downgrade/upgrade guide work as well...that one is just radios and hboot....doesnt come with stock <3e> recovery
REV3NT3CH said:
if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
Click to expand...
Click to collapse
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
jrredho said:
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
Click to expand...
Click to collapse
when you boot into your bootloader...does your hboot now say S-OFF....if so i can give you everything you need and what id suggest doing just prior to doing it
REV3NT3CH said:
when you boot into your bootloader...does your hboot now say S-OFF..
Click to expand...
Click to collapse
Yes it does.
REV3NT3CH said:
.if so i can give you everything you need and what id suggest doing just prior to doing it
Click to expand...
Click to collapse
That would be fantastic!
Thanks,
John