ok so, im s-off and rooted. i used ramjet73's post to do everything and i had to flash hboot 1.4 to play around with miui.
now, i just flashed hboot 1.58 from http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7
(to flash SolidRom which needs hboot 1.58) and when i booted into the bootloader after deleting the file, it says that the bootloader is LOCKED.
the rom booted up just fine, im just wondering if it's safe for me to change hboot again even though my bootloader says LOCKED and i'm still s-off.
iron and wine said:
ok so, im s-off and rooted. i used ramjet73's post to do everything and i had to flash hboot 1.4 to play around with miui.
now, i just flashed hboot 1.58 from http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7
(to flash SolidRom which needs hboot 1.58) and when i booted into the bootloader after deleting the file, it says that the bootloader is LOCKED.
the rom booted up just fine, im just wondering if it's safe for me to change hboot again even though my bootloader says LOCKED and i'm still s-off.
Click to expand...
Click to collapse
Locked is fine. If you want to run fastboot commands like "flash" and "erase" from a PC you will either need to unlock the bootloader again using the htcdev.com method (not recommended) or flash a custom bootloader like the JBear 1.58.5858 version that allows those commands with a locked bootloader (recommended).
The JuopunutBear (wire trick) method for S-OFF leaves the bootloader status as "*** LOCKED ***", which is good since that is the stock status. You don't see that with the custom bootloaders installed since they mask it and allow the fastboot commands that would normally require unlocking.
I recommend the engineering (ENG) 1.04 or JBear GB (1.50.5050) hboot for flashing and booting the GB, AOSP and most Sense ICS ROM's and the JBear ICS (1.58.5858) hboot for the Sense based ICS ROM's that require it.
ramjet73
ramjet73 said:
Locked is fine. If you want to run fastboot commands like "flash" and "erase" from a PC you will either need to unlock the bootloader again using the htcdev.com method (not recommended) or flash a custom bootloader like the JBear 1.58.5858 version that allows those commands with a locked bootloader (recommended).
The JuopunutBear (wire trick) method for S-OFF leaves the bootloader status as "*** LOCKED ***", which is good since that is the stock status. You don't see that with the custom bootloaders installed since they mask it and allow the fastboot commands that would normally require unlocking.
I recommend the engineering (ENG) 1.04 or JBear GB (1.50.5050) hboot for flashing and booting the GB, AOSP and most Sense ICS ROM's and the JBear ICS (1.58.5858) hboot for the Sense based ICS ROM's that require it.
ramjet73
Click to expand...
Click to collapse
I see, that makes a lot more sense now. thanks man
Related
I was wondering if there was a way to get an unlocked bootloader without using HTCDev.com while I'm on 1.58 Hboot?
I upgraded using Virus's PC86IMG.zip file from his thread, and that upgraded the radio's and hboot (and other stuff I'm assuming).
or do all of the methods involve downgrading the hboot while unlocking?
Triumph said:
I was wondering if there was a way to get an unlocked bootloader without using HTCDev.com while I'm on 1.58 Hboot?
Click to expand...
Click to collapse
Sort of.
If you are S-OFF you can flash one of the custom bootloaders from this post and it will support the same fastboot commands that an unlocked stock bootloader supports. Technically your bootloader status is still "***LOCKED***" and if you reflash the stock bootloader it will show that, but the custom bootloaders ignore that status and support the additional fastboot commands.
Since you are currently using 1.58, I recommend the JuopunutBear Sprint ICS (1.58.5858) version since you will probably need that for the ROM you are currently running. Just be aware that version doesn't get along well with GB and AOSP ROM's.
ramjet73
ramjet73 said:
Sort of.
If you are S-OFF you can flash one of the custom bootloaders from this post and it will support the same fastboot commands that an unlocked stock bootloader supports. Technically your bootloader status is still "***LOCKED***" and if you reflash the stock bootloader it will show that, but the custom bootloaders ignore that status and support the additional fastboot commands.
Since you are currently using 1.58, I recommend the JuopunutBear Sprint ICS (1.58.5858) version since you will probably need that for the ROM you are currently running. Just be aware that version doesn't get along well with GB and AOSP ROM's.
ramjet73
Click to expand...
Click to collapse
ok, thanks ramjet.
Just so I am clear, I won't be running a GB or AOSP rom. I have been using TribulattiFather's Roms (SolidRom Family). So I should be good with JuopunutBear's Sprint ICS 1.58.5858.
If I plan on running a AOSP rom down the line somewhere, I should just follow the downgrade hboot guides that are listed in these forums? or is running the JuopunutBear's HBoot not allowing downgrades?
Thanks again for the info, it is greatly appriciated.
Triumph said:
ok, thanks ramjet.
Just so I am clear, I won't be running a GB or AOSP rom. I have been using TribulattiFather's Roms (SolidRom Family). So I should be good with JuopunutBear's Sprint ICS 1.58.5858.
If I plan on running a AOSP rom down the line somewhere, I should just follow the downgrade hboot guides that are listed in these forums? or is running the JuopunutBear's HBoot not allowing downgrades?
Thanks again for the info, it is greatly appriciated.
Click to expand...
Click to collapse
As long as you are S-OFF you can downgrade/upgrade your bootloader anytime you want. Just make sure to delete the PG86IMG.zip file after you flash it or you will only be able to do a normal boot from the bootloader and not get into fastboot USB or recovery. Also, if you are running 4EXT recovery it will go into safe mode after changing bootloaders until cache+dalvik is reformatted and recovery is restarted.
ramjet73
ok perfect! thanks again ramjet!
I did all this and it worked perfectly. Thanks y'all
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?
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
So I recently got a hold of a rezound and it came with S-OFF and an unlocked 2.25 HBOOT. I have a couple of questions about upgrading:
1. Does keeping the HBOOT unlocked have any benefits besides extra fastboot commands (which I'll never use)?
2. How can I upgrade to the 2.27 HBOOT with my phone's current status (unlocked with S-OFF).
3. Are there any benefits to having the unlocked 2.27 HBOOT that vinylfreak released over the stock HBOOT?
Thanks in advance for the help. I've been paging through this forum and there is a lot of fragmented information floating around that's both new and old so it can be hard to make sense of it all.
polarEskimo said:
So I recently got a hold of a rezound and it came with S-OFF and an unlocked 2.25 HBOOT. I have a couple of questions about upgrading:
1. Does keeping the HBOOT unlocked have any benefits besides extra fastboot commands (which I'll never use)?
2. How can I upgrade to the 2.27 HBOOT with my phone's current status (unlocked with S-OFF).
3. Are there any benefits to having the unlocked 2.27 HBOOT that vinylfreak released over the stock HBOOT?
Thanks in advance for the help. I've been paging through this forum and there is a lot of fragmented information floating around that's both new and old so it can be hard to make sense of it all.
Click to expand...
Click to collapse
1. You can flash kernels in recovery and not HBOOT, you can also install a different splash screen logo (downside. you can brick the phone because there is zero security now. "S" in on or off means security)
2. you can update the HBOOT to 2.27 without any problems by downloading one from the develop section and it wont hurt the phone. link
3. HBOOT 2.27 was meant for the global update. if you dont plan on leaving the U.S. or use the phone for gsm then there isnt a need to update.
polarEskimo said:
So I recently got a hold of a rezound and it came with S-OFF and an unlocked 2.25 HBOOT. I have a couple of questions about upgrading:
1. Does keeping the HBOOT unlocked have any benefits besides extra fastboot commands (which I'll never use)?
2. How can I upgrade to the 2.27 HBOOT with my phone's current status (unlocked with S-OFF).
3. Are there any benefits to having the unlocked 2.27 HBOOT that vinylfreak released over the stock HBOOT?
Thanks in advance for the help. I've been paging through this forum and there is a lot of fragmented information floating around that's both new and old so it can be hard to make sense of it all.
Click to expand...
Click to collapse
I would run newest ruu with 2.27 hboot and flash a custom rom.
Damasterjj said:
I would run newest ruu with 2.27 hboot and flash a custom rom.
Click to expand...
Click to collapse
Can I run it with S-OFF and unlocked? I read somewhere that if you use an official RUU on an unlocked HBOOT that you could brick your phone. Will running the RUU re-lock the bootloader after upgrading? Thanks for the help
You can't ever brick your phone running an ruu unless its a bad ruu. To ruu though.. your phone must be relocked using fastboot. What you're thinking of is if you s-on with a modified hboot then you brick. You're good though.
1. Relock with fastboot oem lock
2. Run RUU
3. Honestly there's not much reason to unlock again
Sent from my ADR6425LVW using Tapatalk 2
polarEskimo said:
Can I run it with S-OFF and unlocked? I read somewhere that if you use an official RUU on an unlocked HBOOT that you could brick your phone. Will running the RUU re-lock the bootloader after upgrading? Thanks for the help
Click to expand...
Click to collapse
OK so unlocked and locked boot loaders mean you can use fast boot commands. If you ruu to the newest you will loose fast boot commands unless you unlock or flash an engineering hboot.
If you ever wanted to update after you have unlocked, you must relock the boot loader before updating. Ie never ruu on an unlocked hboot
Sent from my iPhone...
Don't bother updating hboot, it will net you nothing. I've been running 2.25 hboot with the new radios since the 4.03.605.2 leak. 0 issues and runs VERY well. Also unlocked on a patched/eng hboot means nothing, can run the same commands the same way with it being locked. Although a stock hboot may need to be unlocked to get access to some of those commands, of which will probably be of no use to you anyways.
@Syn
S-off shouldnt need a re-lock/unlock to update ANYTHING in hboot with a ph98img.
Snuzzo said:
Don't bother updating hboot, it will net you nothing. I've been running 2.25 hboot with the new radios since the 4.03.605.2 leak. 0 issues and runs VERY well. Also unlocked on a patched/eng hboot means nothing, can run the same commands the same way with it being locked. Although a stock hboot may need to be unlocked to get access to some of those commands, of which will probably be of no use to you anyways.
@Syn
S-off shouldnt need a re-lock/unlock to update ANYTHING in hboot with a ph98img.
Click to expand...
Click to collapse
Learned something new. Thanks.
Sent from my iPhone...
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