Related
hi,all!
I root my Aria with unrevoked,but hboot screen still S-ON.
how to S-Off my Aria?
leyan22 said:
hi,all!
I root my Aria with unrevoked,but hboot screen still S-ON.
how to S-Off my Aria?
Click to expand...
Click to collapse
That feature has not been made available for the Aria as of yet. If you notice all of the phones that Unrevoked has S-OFF for are CDMA phones (Sprint, Verizon, US Celluar, etc.)
any other way to S-Off HTC G9?
Is there any update on how to S-Off the HTC Aria?
rvonins said:
Is there any update on how to S-Off the HTC Aria?
Click to expand...
Click to collapse
not yet, but look here......alpharev.nl
What exactly would this enable/allow?
whynot_ said:
What exactly would this enable/allow?
Click to expand...
Click to collapse
S-OFF (security off) unlocks the NAND on the phone and would allow you to flash new zip and img files to your Aria such as ROMs and custom recovery images.
tpbklake said:
S-OFF (security off) unlocks the NAND on the phone and would allow you to flash new zip and img files to your Aria such as ROMs and custom recovery images.
Click to expand...
Click to collapse
Would that still be possible with the AT&T update installed, or would that overwrite the S-OFF? Just trying to get all my ducks in a row
whynot_ said:
Would that still be possible with the AT&T update installed, or would that overwrite the S-OFF? Just trying to get all my ducks in a row
Click to expand...
Click to collapse
So far those HTC devices that they have been able to achieve S-OFF have been unaffected by new HBOOT, thus they are still rootable, but I wouldn't take a chance by going and installing the AT&T Froyo update and hoping that an S-OFF solution will be found.
Check out http://unrevoked.com/forever for a better explanation about S-OFF.
I wasn't going to install, but was just curious. Thanks for the link.
hxxp://modmymobile.com/forums/666-htc-aria/562661-guide-s-off-root-aria-2-2-2-a.html
(replace hxxp with http)
I think this site has given all instructions to do the S-Off and then root.
I have not tried it yet, but will be doing so soon
very useful information
I just did it last night by using the how to by zedbra......
check it out:
http://forum.xda-developers.com/showthread.php?t=1122574
http://forum.xda-developers.com/showthread.php?t=1159237
Is this root method like unrevoked forever? Is this at the radio level or just a hacked hboot?
If later on, an OTA gets applied, will the phone still be s-off so I can just flash a recovery again?
Please don't respond 'dont take OTAs', because that's not what I'm asking.
Sent from my PC36100 using XDA App
From what I have read it is at the radio level and OTA's shouldn't affect s-off.
vandon1 said:
Is this root method like unrevoked forever? Is this at the radio level or just a hacked hboot?
If later on, an OTA gets applied, will the phone still be s-off so I can just flash a recovery again?
Please don't respond 'dont take OTAs', because that's not what I'm asking.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
From that page:
What does this do, then?
revolutionary will give you S-OFF either by a patched HBOOT or setting the secureflag to off on the device itself. This behaviour will depending on your particular device. Optionally it will also replace the stock Android recovery with a custom one, which adds many features including “nandroid” backups, the ability to use custom ROMs, and a greater amount of flexibility and customization of your Android phone.
Does this permanently unlock the NAND flash on my phone?
Yes. The default configuration of this tool disables the phone's security, which also disables the NAND locks placed on the storage by the bootloader.
All the info I know about is right there.
I also found this, which I'm not positive if this applies to our method, but I think it does. Interesting none the less: http://alpharev.nl/
From what I understand, S-off will remain no matter what, until you issue a fastboot command that is "fastboot oem setsecureflag3" You can see here : http://forum.xda-developers.com/showthread.php?t=1194053 for a full tut on how to turn it back to S-on. SO yea, it's similar to unrevoked forever, where you're always S-off until you deliberately set it to S-on. Running an RUU doesn't even set it to S-on.
That all said, even though you said "don't tell me not to take OTA", I will remind you anyways, that it's always a sketchy thing, especially if HTC has included a new hboot in that OTA. To each their own though.
Thanks for the info, I missed that on the unrevoked site.
However, if it's S-Off in the radio, doesn't that mean that the hboot won't really matter? On the evo 4g at least, new hboots don't kill the s-off and you could always reflash a recovery from hboot.
I'm just wondering if you can flash a recovery with s-off from a stock hboot.
k2buckley said:
Running an RUU doesn't even set it to S-on.
Click to expand...
Click to collapse
Are you sure? I read this in the AlphaRev FAQ's
As soon as you decide to flash a stock RUU that has a HBOOT update in it, this hacked HBOOT will be overwritten.
Click to expand...
Click to collapse
This is interesting, as I have been wondering how to get S-ON after running Revolutionary, should I need to take my device in for repairs.
What's your take on it?
mattchew86 said:
Are you sure? I read this in the AlphaRev FAQ's
This is interesting, as I have been wondering how to get S-ON after running Revolutionary, should I need to take my device in for repairs.
What's your take on it?
Click to expand...
Click to collapse
I hear "fastboot oem setsecureflag3" works wonders.
Good info. Thanks
Sent from my PG86100 using Tapatalk
This thread is regarding RUU for HTC devices.
I've seen some similar threads but could not fully get the answer I was looking for.
From what I already understand, a RUU updates the ROM, the H-BOOT possibly and updates the recovery with a stock recovery. It cannot do anything that a BL-Unlocked user cannot do through adb or fastboot because the RUU uses only adb and fastboot. This means that the RUU does not (And cannot) update the radio. Am I correct in this?
And if so, what is the point of updating the RUU once you start flashing custom ROMs because they also flash the /system and /boot partitions and the only thing a custom ROM doesn't do is reflash the H-BOOT and the recovery.
And even if you update using a RUU for some reason (Whether it updates or if you just want to return to stock), do you have to choose the RUU that exactly matches your current radio version?
Assume for all the questions that the device is either BL-Unlocked or Stock (But S-ON either way).
Thanks in advance.
AceRoom said:
This thread is regarding RUU for HTC devices.
I've seen some similar threads but could not fully get the answer I was looking for.
From what I already understand, a RUU updates the ROM, the H-BOOT possibly and updates the recovery with a stock recovery. It cannot do anything that a BL-Unlocked user cannot do through adb or fastboot because the RUU uses only adb and fastboot. This means that the RUU does not (And cannot) update the radio. Am I correct in this?
And if so, what is the point of updating the RUU once you start flashing custom ROMs because they also flash the /system and /boot partitions and the only thing a custom ROM doesn't do is reflash the H-BOOT and the recovery.
And even if you update using a RUU for some reason (Whether it updates or if you just want to return to stock), do you have to choose the RUU that exactly matches your current radio version?
Assume for all the questions that the device is either BL-Unlocked or Stock (But S-ON either way).
Thanks in advance.
Click to expand...
Click to collapse
Hi, an ruu updates what you mentioned and a lot more. It will do things like change the splash screen, update the radio. and change the hboot which you cannot do with only an unlocked bootloader. It can do those things because its signed.
I had to use ruu's a few times, recently for an hboot downgrade to achieve s-off. Now that I have s-off I can flash any file I want in hboot asblong as its named correctly. Like a splash screen, or a lower hboot version.
Since an ruu updates the radio, it doesn't matter which version you choose, as long as its the same version you have or higher, but it won't let you flash a lower versionWith s-off I can flash any ruu version I want.
ok, so if I am currently running 2.3.4 and htc sense 3.0, does that mean that I can flash my phone with ics (4.0) as long as it is for the right phone and carrier???
HTC evo 3D with Rogers
icecursor said:
ok, so if I am currently running 2.3.4 and htc sense 3.0, does that mean that I can flash my phone with ics (4.0) as long as it is for the right phone and carrier???
HTC evo 3D with Rogers
Click to expand...
Click to collapse
Yes.
Theonew said:
Yes.
Click to expand...
Click to collapse
now, if I upgrade it through the ruu, is that the exact same upgrade that comes from the carrier? As in, even the HTC update too?
And if it is, is the ruu just the rooted phones way of updating?
Thanks
icecursor said:
now, if I upgrade it through the ruu, is that the exact same upgrade that comes from the carrier? As in, even the HTC update too?
And if it is, is the ruu just the rooted phones way of updating?
Thanks
Click to expand...
Click to collapse
Yes it is the same update. Updating with the RUU can be used either way (rooted or non-rooted). Just keep in mind that you'll lose root access after updating.
Theonew said:
Yes.
Click to expand...
Click to collapse
Theonew said:
Yes it is the same update. Updating with the RUU can be used either way (rooted or non-rooted). Just keep in mind that you'll lose root access after updating.
Click to expand...
Click to collapse
ok, so last question,
do I need hboot 1.5? I am currently running revolutionary s-off, HBOOT 1.49.1107.
Originally Posted by Theonew
Yes.
Click to expand...
Click to collapse
Originally Posted by Theonew
Yes it is the same update. Updating with the RUU can be used either way (rooted or non-rooted). Just keep in mind that you'll lose root access after updating.
Click to expand...
Click to collapse
ok, so last question,
do I need hboot 1.5? I am currently running revolutionary s-off, HBOOT 1.49.1107.
Click to expand...
Click to collapse
I'm not sure for your device, but as long as the RUU is for it, it should work (boot loader version doesn't usually affect it).
hello, i wanted to know if RUU also achieves S-ON. I need to return my droid incredible to verizon for replacement due to screen malfunction. I cannot see anything on the display, but everything inside works fine.
I had unlocked bootloader using htcdev and rooted with S-OFF running 4.1.1. I am now on stock Froyo thanks to RUU, but I still need to get S-ON and bootloader locked.
So does the RUU achieve S-ON? I have downloaded the forever SON zip file. But I dont know how to flash it using ADB. Can someone guide me.
haunteddevil619 said:
hello, i wanted to know if RUU also achieves S-ON. I need to return my droid incredible to verizon for replacement due to screen malfunction. I cannot see anything on the display, but everything inside works fine.
I had unlocked bootloader using htcdev and rooted with S-OFF running 4.1.1. I am now on stock Froyo thanks to RUU, but I still need to get S-ON and bootloader locked.
So does the RUU achieve S-ON? I have downloaded the forever SON zip file. But I dont know how to flash it using ADB. Can someone guide me.
Click to expand...
Click to collapse
The RUU does not return S-ON. What is in the zip file?
achieve S-ON on htc...
haunteddevil619 said:
hello, i wanted to know if RUU also achieves S-ON. I need to return my droid incredible to verizon for replacement due to screen malfunction. I cannot see anything on the display, but everything inside works fine.
I had unlocked bootloader using htcdev and rooted with S-OFF running 4.1.1. I am now on stock Froyo thanks to RUU, but I still need to get S-ON and bootloader locked.
So does the RUU achieve S-ON? I have downloaded the forever SON zip file. But I dont know how to flash it using ADB. Can someone guide me.
Click to expand...
Click to collapse
for S-ON try this Post ...
I did Bootloader unlock using the code fron HTEDev, and it showed "Unlocked" . Then I flashed 4Ext recovery and unrooted. However, when I did "S-off", the bootloader shows"Locked" again with the text "S-off".
Anyone have the same issue? Should I do the unlock again using the code? or I can just ignore it and go ahead install other custome ROM.
Edit: Educated by dark nightmare.
Sent from my HTC Vision using xda app-developers app
Just unlock it back using the unlock file you got.
Would unlocking again serve any real purpose?
Sent from my HTC Vision using xda app-developers app
death4u said:
Would unlocking again serve any real purpose?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Leave it locked and you'll see, .
sent from a galaxy you'll never see.
Dark Nightmare said:
Just unlock it back using the unlock file you got.
Click to expand...
Click to collapse
I have several questions here:
1. Is my bootloader re-locked after S-off, or it is still unlocked but just show a Irrelevant text " locked" ?
2. How could I check if the real bootloader's status: "Locked" or Unlocked", not just from the text show in the fastboot page?
2. If the "bootloader is relocked", it should show "Relocked", not "Locked", isn't it?.
3. If it IS re-locked and I don't re-unlock it, will it affect the installation of custom ROM?
If the "Locked" after S-off does not affect the installation of custom ROM, I would like to leave it that way which will be easy to roll back to complete stock for warranty.
Brightxda said:
I have several questions here:
1. Is my bootloader re-locked after S-off, or it is still unlocked but just show a Irrelevant text " locked" ?
2. How could I check if the real bootloader's status: "Locked" or Unlocked", not just from the text show in the fastboot page?
2. If the "bootloader is relocked", it should show "Relocked", not "Locked", isn't it?.
3. If it IS re-locked and I don't re-unlock it, will it affect the installation of custom ROM?
If the "Locked" after S-off does not affect the installation of custom ROM, I would like to leave it that way which will be easy to roll back to complete stock for warranty.
Click to expand...
Click to collapse
It is locked you need to un lock it again so you can flash custom recovery
sent from my NRGized Amaze,
powered by faux kernel v.16
aj_2423 said:
It is locked you need to un lock it again so you can flash custom recovery
sent from my NRGized Amaze,
powered by faux kernel v.16
Click to expand...
Click to collapse
If he had a custom recovery before s-off it's still there, but you see the thing about "locked" or "relocked" bootloaders people don't understand is that even with s-off, once it's locked, writing anything at all isn't possible via custom recoveries, that itself is the first level of security we bypass to customize our devices.
By the way to the op, it is currently locked the way it was before you unlocked via htcdev, not relocked, that text on the hboot is the verification.
sent from a galaxy you'll never see.
Dark Nightmare said:
If he had a custom recovery before s-off it's still there, but you see the thing about "locked" or "relocked" bootloaders people don't understand is that even with s-off, once it's locked, writing anything at all isn't possible via custom recoveries, that itself is the first level of security we bypass to customize our devices.
By the way to the op, it is currently locked the way it was before you unlocked via htcdev, not relocked, that text on the hboot is the verification.
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
Thank you all very much for clearing my questions. I will unlock it again.
One more question: How could it relocked during the S-off? Is it the normal thing for all of S-off or it just happens in a few cases?
Brightxda said:
Thank you all very much for clearing my questions. I will unlock it again.
One more question: How could it relocked during the S-off? Is it the normal thing for all of S-off or it just happens in a few cases?
Click to expand...
Click to collapse
It happens to all of us, once you don't install JB hboot after s-off it locks your bootloader, I guess the entire process resets a few security levels since it turns the main security lock off.
Dark Nightmare said:
It happens to all of us, once you don't install JB hboot after s-off it locks your bootloader, I guess the entire process resets a few security levels since it turns the main security lock off.
Click to expand...
Click to collapse
You are right. I skipped the last step, installing JB hboot during the S-off. I thought my Amazer came with the new ICS pre-installed which might not need other hboot. It should not be any problem, right?
Brightxda said:
You are right. I skipped the last step, installing JB hboot during the S-off. I thought my Amazer came with the new ICS pre-installed which might not need other hboot. It should not be any problem, right?
Click to expand...
Click to collapse
Na it's just a custom hboot, not needed, you can always flash that or the ENG hboot later if you wanna change your splash screen, that's probably the only thing it's useful for.
Dark Nightmare said:
Na it's just a custom hboot, not needed, you can always flash that or the ENG hboot later if you wanna change your splash screen, that's probably the only thing it's useful for.
Click to expand...
Click to collapse
Thank you again, I reunlocked the bootloader, flashed Energy™ ROM and it works great now.:victory:
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