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?
Related
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 Everyone. Now I'm on stock hboot 1.53.0007 S-ON and I'd like to do S-OFF. I understand that i should unlock via HTC Dev, then root and after that S-OFF. But my question is how does the bootloader looks after S-OFF via JuopunutBear? Does it make LOCKED and S-OFF? If not what should I do (if it's possible) to go back for a locked bootloader (not relocked)? And if JuopunutBear makes bootloader LOCKED i should be able to flash RUU, than use fastboot oem writesecure flag 3 to make S-ON and that's all? Cheers
c000ler said:
Hi Everyone. Now I'm on stock hboot 1.53.0007 S-ON and I'd like to do S-OFF. I understand that i should unlock via HTC Dev, then root and after that S-OFF. But my question is how does the bootloader looks after S-OFF via JuopunutBear? Does it make LOCKED and S-OFF? If not what should I do (if it's possible) to go back for a locked bootloader (not relocked)? And if JuopunutBear makes bootloader LOCKED i should be able to flash RUU, than use fastboot oem writesecure flag 3 to make S-ON and that's all? Cheers
Click to expand...
Click to collapse
You are most correct sir. After you perform the wire trick the end result is a "locked" bootloader with s-off. With s-off you can flash any version of your carrier and regions ruu. Definetely right after you flash ruu you would fastboot and use that command to get back on s-on. I hope I answered your questions. Please don't hesitate to ask if you need more help. Peace.
Please hit the thank you button if I helped you in anyway.
One more thing. When it comes to the end of S-OFF via JuopunutBear there is a question: Do you want to install juopunutbear modified hboot? What will happen when I'm going to choose No? I will be on stock locked hboot with S-OFF? What pros are with Juopunutbear modified hboot? And I understand that if I want to get rid of Juopunutbear hboot I must flash RUU? Cheers
With s-off you can flash any hboot you desire by renaming the file PG86IMG.zip, place it on root of sd, reboot bootloader.
Jbear hboots accept more adb commands than stock.
sudo passwd root
I need to relock my cell to S-ON as I need to send my cell to HTC for repairs as my GPS stopped working. How do I do that if I accomplished S-OFF with jbear and HTCDev method.
Thanks!
vega312 said:
I need to relock my cell to S-ON as I need to send my cell to HTC for repairs as my GPS stopped working. How do I do that if I accomplished S-OFF with jbear and HTCDev method.
Thanks!
Click to expand...
Click to collapse
You need to start by flashing the 2.89.651.2 RUU, either using the RUU.exe from Windows or an RUU.zip renamed to PG86IMG.zip from the bootloader. If you didn't do the htcdev unlock again after the wire trick, the stock bootloader should show ***LOCKED*** with a version of 1.58. Since you are only getting the phone serviced, it's probably OK to leave it S-OFF, but if you want it 100% stock you need to issue the following command after you have verified that the bootloader is 1.58:
fastboot oem writesecureflag 3
Once you have issued this command your phone will be S-ON and you will have to do the wire trick again after you get it back to be S-OFF. My understanding is that most repair facilities, including Sprint, don't mind if you give it to them S-OFF. However, if you are sending it back to HTC it might be worth doing since with stock software, a locked bootloader and S-ON it will look "factory fresh" to them.
You might also want to test your GPS again once everything is back to stock, just to make sure it's not a ROM problem.
ramjet73
where can i get the ruu i ran the one on htcdev.com but it didnt change my rom
jb14813 said:
where can i get the ruu i ran the one on htcdev.com but it didnt change my rom
Click to expand...
Click to collapse
Try here: http://forum.xda-developers.com/showthread.php?p=19089387
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)
I recently bought my new Evo 3D from eBay. As far as I can tell, it is in perfect shape. I was hoping to flash it to Page Plus and was dismayed when I realized how impossible the rooting process looked. I began with downgrading my 1.58 HBOOT to 1.40. Now I am attempting to flash the 1.13 RUU so I can finally move on in this process, but every time I attempt to flash it (or any other RUU), I get the error, "Error [131]: CUSTOMER ID ERROR." Now most fastboot commands do not work, and my phone bootloops with the stock ROM. Any idea how to fix it?
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Brian706 said:
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Click to expand...
Click to collapse
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Macadamia Daze said:
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
Click to expand...
Click to collapse
Oh, I see now!
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Brian706 said:
Oh, I see now!
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Click to expand...
Click to collapse
So far, I have yet to have any success despite flashing many RUUs. I took a break for quite a while, but decided I may try again. I am downloading now the 2.08 RUU, which one thread suggested.
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
If I remember correctly, the HTCDev unlock doesnt work for the earlier bootloaders. It says so on the very first page when its walking you through the steps. I could be wrong but you may wanna keep that in mind