Related
I was trying to relock my phone to return to sprint, got relocked, but couldnt successfully run ruu. tried adb fastboot to relock just in cast I hadnt relocked successfully as well. then tried to flash ruu, got stuck at htc screen, and bootloader was the only thing that worked after that. now stuck in bootloader. what should I do? recovery from bootloader doesnt work, factory reset doesnt work.
thanks
Run the RUU from fastboot
Also, are you S-oFF? you can probably still be easily saved if so
Rxpert said:
Run the RUU from fastboot
Also, are you S-oFF? you can probably still be easily saved if so
Click to expand...
Click to collapse
S-on. how do i run ruu from fastboot?
http://forums.androidcentral.com/showthread.php?t=177373Its a different phone but just substitute your IMG file where it used the tbolt
wobumang said:
S-on. how do i run ruu from fastboot?
Click to expand...
Click to collapse
You connect your phone to the computer while in bootloader and run the RUU
Rxpert said:
You connect your phone to the computer while in bootloader and run the RUU
Click to expand...
Click to collapse
great. now I feel stupid. must find others to blame...
thanks, phone exchanged.
wobumang said:
great. now I feel stupid. must find others to blame...
thanks, phone exchanged.
Click to expand...
Click to collapse
So it worked? or you went and got a new one?
Rxpert said:
So it worked? or you went and got a new one?
Click to expand...
Click to collapse
yes, it worked. many thanks.
so i recently tried rooting and putting a rom on my brothers phone. i have already done mine so i thought it would be easy. i didnt not know of the s-on/s-off concept. so i put on a rom that required s-off on the s-on htc evo 3d. i put a rom on that is compatible with s-on for the mean time. what i want to know is there a way to return to the stock rom, or fix it from here and go to s-off.
HTC EVO 3D from sprint CDMA
hboot 1.58
s-on
to add, i am still a newb at this whole thing. if anyone can help please do. if anyone needs more info please ask.
Follow the guide here: http://forum.xda-developers.com/showthread.php?t=1889438
You'll relock and run the ruu.exe. This will put everything back to stock. You can then follow the guide to get s-off.
thanks!
coal686 said:
Follow the guide here: http://forum.xda-developers.com/showthread.php?t=1889438
You'll relock and run the ruu.exe. This will put everything back to stock. You can then follow the guide to get s-off.
Click to expand...
Click to collapse
thanks, i will have to try this later my brother is currently at work. thanks for the guide. il let you know how it turns out
usb
coal686 said:
Follow the guide here: http://forum.xda-developers.com/showthread.php?t=1889438
You'll relock and run the ruu.exe. This will put everything back to stock. You can then follow the guide to get s-off.
Click to expand...
Click to collapse
In the guide it says connect phone, does it have to be in recovery, or in fastboot usb. also i tried this and it says i have the wrong ruu
error code
alexp07 said:
In the guide it says connect phone, does it have to be in recovery, or in fastboot usb. also i tried this and it says i have the wrong ruu
Click to expand...
Click to collapse
says i got error code 155
alexp07 said:
In the guide it says connect phone, does it have to be in recovery, or in fastboot usb. also i tried this and it says i have the wrong ruu
Click to expand...
Click to collapse
alexp07 said:
says i got error code 155
Click to expand...
Click to collapse
Fastboot USB is what you need to be in. That error code typically means that you forgot to relock the bootloader before running the ruu. It could also mean that you have the wrong ruu.exe. Did you get yours from the zip in ramjet's thread?
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
Dudes,
Too many dead pixels dying on my phone and ATT is sending me another replacement device through warranty. I RUU'd and brought everything back to normal from the CID, hboot, radio, and back to s-on but I cannot get my bootloader to show "Locked". It just shows relocked. Im certain I cannot send it back to them saying relocked. Ive searched and maybe im not searching good enough. Care to share some commands?
"fastboot oem lock" only relocks it.
I restored the phone to 3.17 firmware and RUU but before I update it to the 4.3 id like it to show locked. Any help is appreciated.
Edit: Nevermind I found my answer. Read that this was not possible.
kennypow3rs said:
Dudes,
Too many dead pixels dying on my phone and ATT is sending me another replacement device through warranty. I RUU'd and brought everything back to normal from the CID, hboot, radio, and back to s-on but I cannot get my bootloader to show "Locked". It just shows relocked. Im certain I cannot send it back to them saying relocked. Ive searched and maybe im not searching good enough. Care to share some commands?
"fastboot oem lock" only relocks it.
I restored the phone to 3.17 firmware and RUU but before I update it to the 4.3 id like it to show locked. Any help is appreciated.
Edit: Nevermind I found my answer. Read that this was not possible.
Click to expand...
Click to collapse
If you're s-off it is totally possible there's a command for it built right in to revone.
Sent from my HTC One using Tapatalk
to my knowledge any htc device no longer show "locked" after you unlocked it the first time..it will always show relocked when locked again..
Nick281051 said:
If you're s-off it is totally possible there's a command for it built right in to revone.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Too bad i found this out after i s-on'd the phone again lol. So now im in the process of unlocking with rumrunner, then re s-off, then try to "lock" it again. Thanks for the replies guys
kennypow3rs said:
Too bad i found this out after i s-on'd the phone again lol. So now im in the process of unlocking with rumrunner, then re s-off, then try to "lock" it again. Thanks for the replies guys
Click to expand...
Click to collapse
No problem lol good luck
Sent from my HTC One using Tapatalk
Nick281051 said:
No problem lol good luck
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
ok now I have some problems. I unlocked again, s-off'd and then tried to "lock" and s-on again. Something went wrong and now I have a message in hboot that says "security warning" and tampared over the words "locked". I doesnt boot to the rom again just goes to recovery im guessing with the phone and the red triangle. lol Pain in the butt.
To be honest I have no clue how to fix that lol I haven't tried to lock it yet
Sent from my HTC One using Tapatalk
Nick281051 said:
To be honest I have no clue how to fix that lol I haven't tried to lock it yet
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Theres no rom on the phone now lol.Gotta figure this out! Thanks for your help dude!
Run a ruu that will fix it tampered will be gone too
Sent from my HTC One using Tapatalk
So right now it's unlocked with tampered above an s-off. Is it wise to lock bootloader first before I run ruu? Which order should I go? I know s-on is last for sure...
Sent from my HTC One using Tapatalk
For anyone that's searching for this exact issue ill share what i did to get my phone completely back to stock. I did search the forum but the info was all over the place and in my opinion it was as clear as "I" needed it to be hence me creating a thread for something so simple. Ok as follows here is what I did step by step.
First I had to make sure I installed HTC sync of course. At the moment my firmware was 3.57 and I downloaded the 3.17 RUU.exe from HTC.com
Your firmware *HBOOT* and the RUU you download have to match or you will get errors. Well, least I did.
Make sure you download some type of toolkit it would make life a lot easier. I used this one it worked like a charm!
At the moment, my phone is bootloader unlocked and s-off fyi.
Next, Use the tool to "lock" your bootloader first not "re-lock" just "lock". If you're having issues push revone again and follow commands on toolbox.
Now, check hboot to see if it shows "locked" if it has tampered above locked that's ok the RUU will take care of that.
Run, the RUU, make sure usb debugging on and htc sync already installed. Let it run.
After its done, start up phone again, turn off fastboot under "power" and turn usb debugging on again.
Start up toolkit, look to the right and it will say "s-on" device. You can only s-on after you've ran the RUU and are on stock hboot and rom.
Check Hboot again and it should read "Locked" and now "s-on".
Phone now ready to send back for warranty or etc.
Hope this helps anyone that searches. I found a few thread via google and they helped out a bunch.
hey guys/gals, let me start off by saying that i knew better but as always i screwed up by letting my add get the best of me! i relocked bootloader to RUU to stock . problem is that i didnt load the correct splash1 first! now when i try to flash anything i get the signature error. im hoping that a work-around is available. i tried the htcdev but get an error 160 MID not allowed. tried the toolkit(s) available, NO ADB!!! soooo here i am hoping that you guys might have experienced a moment of dumbness as i did....i get a multitude of errors when trying to flash stuff (error 12 sig failure,wrong main version error)...was unlocked and rooted per rumrunner (THANKS BEAUPS!!!!!) prior to my screw up... heres what i have
s-on
hboot-1.33.0001
radio-1.01.1112
baseband-1.01.01.1112
version main-3.06.605.4
cid-VZW_001
bootloader-041a62aa
(lmk if any further info is needed)
like i stated before , i know i needed to flash splash1 BEFORE locking bootloader but in my defense i had my 11 week old son in my arms (multitasking FAIL) , so if you guys have ANY suggestion please feel free to lmk...THANKS IN ADVANCE as this is a new problem for me!
and btw, i spent yesterday sifting through threads to try to solve this ,to no avail....i didnt want to tie you guys up prematurely
i did try to re run rumrunner and moonshine (even though i knew moonshine wouldnt work) but as i said , i have no adb and usb debugging s questionable, although i can use fastboot to rebootRUU
stephenculkin6277 said:
i did try to re run rumrunner and moonshine (even though i knew moonshine wouldnt work) but as i said , i have no adb and usb debugging s questionable, although i can use fastboot to rebootRUU
Click to expand...
Click to collapse
Try this, access to fastboot first then connect usb to pc
http://forum.xda-developers.com/showpost.php?p=48680578&postcount=44
i get the error:remote not allowed....I had those files downloaded yesterday
i just tried in the rebootRUU status (blask screen with HTC logo and got error 43 main versio check fail?
i got firmware2 to run (both times) ... do i need to try to reset to stock from bootloader now?
or is the 2nd one no good without the 1st? im sorry , i just dont want to screw up anymore than i already have ya know
stephenculkin6277 said:
or is the 2nd one no good without the 1st? im sorry , i just dont want to screw up anymore than i already have ya know
Click to expand...
Click to collapse
Reboot bootloader, the second firmware is the new Hboot 1.54.0000 need it to run the new Ruu. hope it help
after reboot bootloader confirm that your hboot is the new. so you can go ahead with the ruu
k thanks, but I think the problem im having running the RUU is the image...whatever that is, I think the splash1 I forgot to load...I will try running the jb_50 RUU now though , thanks
finanandroid said:
Try this, access to fastboot first then connect usb to pc
http://forum.xda-developers.com/showpost.php?p=48680578&postcount=44
Click to expand...
Click to collapse
finanandroid said:
Reboot bootloader, the second firmware is the new Hboot 1.54.0000 need it to run the new Ruu. hope it help
after reboot bootloader confirm that your hboot is the new. so you can go ahead with the ruu
Click to expand...
Click to collapse
sorry , I spoke too soon...I just finished running RUU and you have solved the mystery!!! much gracias my friend!!! I cant thank you enough!!!
stephenculkin6277 said:
sorry , I spoke too soon...I just finished running RUU and you have solved the mystery!!! much gracias my friend!!! I cant thank you enough!!!
Click to expand...
Click to collapse
You're welcome! glad that you can back on business. :victory:
Instructions clearly said the splash image was only for custom splash images. It is not a necessary step.
Sent from my DLX using xda app-developers app
See that's the thing, I was running pro bam which had a non stock splash img so I assumed I had to, my bad
You may need to reinstall adb?
thayl0 said:
You may need to reinstall adb?
Click to expand...
Click to collapse
Yeah, I did as a precaution.... The firmware2 file let me run RUU after I flashed it... I still can't believe I made such a bone head mistake! Now I just wish I could get my Bootloader unlock token for future screw ups lol But I just get error 160 MID not allowed when I try, At least rumrunner worked for me!
stephenculkin6277 said:
Yeah, I did as a precaution.... The firmware2 file let me run RUU after I flashed it... I still can't believe I made such a bone head mistake! Now I just wish I could get my Bootloader unlock token for future screw ups lol But I just get error 160 MID not allowed when I try, At least rumrunner worked for me!
Click to expand...
Click to collapse
You can no longer do that any more.
That sucks donkey balls!
If you're s-off you can set cid to 22222222 and get an unlock token at htcdev
Thank you sir! I now have the token I have been needing!
Sent from my HTC6435LVW using xda app-developers app