s-off? what does that mean? - G2 and Desire Z General

subject says it all

s-off means nand unlocked
Edit: oops lol

S-off = signature verification off.
Phone: T-Mobile G2/Vision Rooted
Rom: Baconbits 0.3
Recovery: CWM waiting for Amon RA

daaango said:
s-off means nand unlocked
Click to expand...
Click to collapse
No, it doesn't. S-off means security is off, and you can flash unsigned (custom) images to the phone.

This is "sort of" a follow up question to the s-off: i have the Droid Incredible and HAD root (on the 2.2 OTA which was a 2.x Build number). They recently pushed a 3.x build which had enhancements to Exchange integration that i wanted, so i applied it. Now, I do NOT have root, but I still see s-off at the bootloader... can anyone shed some light on:
1. the difference between having ROOT and having s-off...
2. How i might regain ROOT on the 3.x build...
i had used unrEVOked3 on the original 2.2 and had no problems... now when running the latest unrEVOked3 my phone hangs (as does the unrEVOked app) at the "attempting to get root" process.... and never gets root.
I am led to believe that Verizon/HTC have patched the vulnerability... thoughts?

vyrt1go said:
This is "sort of" a follow up question to the s-off: i have the Droid Incredible and HAD root (on the 2.2 OTA which was a 2.x Build number). They recently pushed a 3.x build which had enhancements to Exchange integration that i wanted, so i applied it. Now, I do NOT have root, but I still see s-off at the bootloader... can anyone shed some light on:
1. the difference between having ROOT and having s-off...
2. How i might regain ROOT on the 3.x build...
i had used unrEVOked3 on the original 2.2 and had no problems... now when running the latest unrEVOked3 my phone hangs (as does the unrEVOked app) at the "attempting to get root" process.... and never gets root.
I am led to believe that Verizon/HTC have patched the vulnerability... thoughts?
Click to expand...
Click to collapse
With s-off u should be able to use fastboot or rom manager to push a new recovery img. Once you have that, u can flash a rooted rom.
Root is done in the rom. Recovery flashes roms. S-off controls flashing (among other things)

texasaggie1 said:
S-off controls flashing
Click to expand...
Click to collapse
Would it be more accurate to say that S-Off allows flashing?

cparekh said:
Would it be more accurate to say that S-Off allows flashing?
Click to expand...
Click to collapse
Not really, because S-ON still allows flashing, just that it only allows flashing of signed ROM. So S-ON/S-OFF determines which sort of ROMs you will be able to flash.

Don't get that part
steviewevie said:
Not really, because S-ON still allows flashing, just that it only allows flashing of signed ROM. So S-ON/S-OFF determines which sort of ROMs you will be able to flash.
Click to expand...
Click to collapse
Does that mean S-OFF is a developer phone? And how about warranty?
Btw, my one is S-ON but i can toggle between Signature check on fastboot.
The only time flashing does not work, even when signature check is disabled, is when the image doesn't match.. can't recall the exact error message. Wonder if that has to do as well with the S-ON/OFF thing?

Related

How to COMPLETELY unroot EVO to send back to Sprint

How do I COMPLETELY unroot EVO to send back to Sprint
Like s-off s-on plz help
If you rooted using Unrevoked 3.21 there is a thread listed in Android Development explaining the process as well as the needed links to download the needed zip files to turn S-On and the zip file to restore back to Stock Froyo 2.2
SouthernEvo said:
If you rooted using Unrevoked 3.21 there is a thread listed in Android Development explaining the process as well as the needed links to download the needed zip files to turn S-On and the zip file to restore back to Stock Froyo 2.2
Click to expand...
Click to collapse
Tbd but I used toast.method to root that used a lot of adb
mccurt29 said:
Tbd but I used toast.method to root that used a lot of adb
Click to expand...
Click to collapse
Ok but there are still methods in the forum for unrooting just like how you rooted. I would just do a search for them and choose which one you feel is the easiest for you to understand. Also if you are getting another EVO unrevoked 3.21 is as many in here have said easy peasy for rooting.
Good luck
playya said:
Ok but there are still methods in the forum for unrooting just like how you rooted. I would just do a search for them and choose which one you feel is the easiest for you to understand. Also if you are getting another EVO unrevoked 3.21 is as many in here have said easy peasy for rooting.
Good luck
Click to expand...
Click to collapse
Thanks!......
You need to run the RUU.exe found in the Dev section. It will do the trick.
Sent from my PC36100 using XDA App
novanosis85 said:
You need to run the RUU.exe found in the Dev section. It will do the trick.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Precisely. It can be found here:
*OFFICIAL* RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15. 00.09.01_NV_1.77_CNV_rel.
One thing to check first: do you have S-OFF? This would be the case if you ever ran Unrevoked Forever or Unrevoked 3.21. If so, you'll need to flash the Unrevoked Forever S-ON tool from recovery before running the RUU.
Noxious Ninja said:
Precisely. It can be found here:
*OFFICIAL* RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15. 00.09.01_NV_1.77_CNV_rel.
One thing to check first: do you have S-OFF? This would be the case if you ever ran Unrevoked Forever or Unrevoked 3.21. If so, you'll need to flash the Unrevoked Forever S-ON tool from recovery before running the RUU.
Click to expand...
Click to collapse
Thx guys I never used unrevok just toast methods but how do u check the A-on thing & should it be on or off
Also this 1 guy on this forum said he used the ruu & had s-on/off but Sprint still found out he rooted so should I wipe that ex--- >#366# stuff too?
mccurt29 said:
Thx guys I never used unrevok just toast methods but how do u check the A-on thing & should it be on or off
Also this 1 guy on this forum said he used the ruu & had s-on/off but Sprint still found out he rooted so should I wipe that ex--- >#366# stuff too?
Click to expand...
Click to collapse
Reboot into the bootloader (turn phone off, then hold power+volume down until it comes on). Then look at the end of the first line.
If it says SHIP S-ON, you're good.
If it says SHIP S-OFF, you need to run the Unrevoked tool.
If it says ENG S-OFF (which should be the case if you used Toast's method), it is indeterminate.
However, if you never used Unrevoked at all, you shouldn't have to worry about it. You can check after you run the RUU, which will reset it to the SHIP bootloader.
I believe the 3.29 RUU resets everything, including the PRI. Toast's method downgraded the PRI, and it was difficult to get it back before the current update, so this used to be a sure-fire way of telling whether you had rooted. Unless you had a bad Wimax flash and broke your 4G, I *think* you should be OK. But I don't know for sure.
Noxious Ninja said:
Reboot into the bootloader (turn phone off, then hold power+volume down until it comes on). Then look at the end of the first line.
If it says SHIP S-ON, you're good.
If it says SHIP S-OFF, you need to run the Unrevoked tool.
If it says ENG S-OFF (which should be the case if you used Toast's method), it is indeterminate.
However, if you never used Unrevoked at all, you shouldn't have to worry about it. You can check after you run the RUU, which will reset it to the SHIP bootloader.
I believe the 3.29 RUU resets everything, including the PRI. Toast's method downgraded the PRI, and it was difficult to get it back before the current update, so this used to be a sure-fire way of telling whether you had rooted. Unless you had a bad Wimax flash and broke your 4G, I *think* you should be OK. But I don't know for sure.
Click to expand...
Click to collapse
thanx that did the trick now to the sprint store tomorrow wish me luck
If your still having trouble then try this:
http://forum.xda-developers.com/showthread.php?t=780141&highlight=unroot
I just unrooted mine last night and it only took me 5 mins, just flash the unrevoked and then do the update on the PC36IMG and thats it.

Perma-rooted G2 a while back, do I need to Root it with Gfree??

Ok I got my G2 when it first came out. Used the old rage method to get S-OFF and perma root. Now i'm reading people say that they have "real" S-OFF and real permaroot. Do I have to do the "gfree" method now or is my phone good as it is?
I understand that with gfree you can unlock your SIM and you can switch between S-OFF and S-ON.. I'd like to have those functions. How should I go about it? Do I do a factory reset to go back to stock and unroot and then use gfree method or is there a simpler way to do it?
Here's what I have right now:
Stock rom, I NEVER installed any OTA's.
I have Baconbits.
My baseband is: 12.22.60.09bU_26.02.01.15_M2
Kernel: 2.6.32.21-cyanogenmod [email protected]#1
Build #: 1.19.531.1 CL255798 release-keys
Thanks for all the help.
Since you have root and a stock rom installed, just run gfree -- that is ALL you need to do. The advantage, aside from unlocking the radio, is that with the proper s-off, there is some new security for the radio... for unbricking and for being able to withstand accidental OTA updates. A true radio s-off can take an OTA update containing BOTH an SPL and a Radio, and yet s-off remains.
dhkr234 said:
Since you have root and a stock rom installed, just run gfree -- that is ALL you need to do. The advantage, aside from unlocking the radio, is that with the proper s-off, there is some new security for the radio... for unbricking and for being able to withstand accidental OTA updates. A true radio s-off can take an OTA update containing BOTH an SPL and a Radio, and yet s-off remains.
Click to expand...
Click to collapse
I'm in the same boat as the OP. How do i go about just running gfree?
sent from my V I S I O N.
Well I'm rooted with the old method as well but because I I cant flash cwm 3.x with the gree method. You need the eng hboot so ill stick with the old method until clockwork makes it work with the gfree method.
Sent from my gSpot2
PatrickHuey said:
I'm in the same boat as the OP. How do i go about just running gfree?
sent from my V I S I O N.
Click to expand...
Click to collapse
See the Wiki for details. Assuming you are running a kernel where gfree works (again, see the Wiki on this), you just need a root shell on your phone, copy gfree to your phone (e.g. via adb push), then run gfree with the appropriate options, e.g. "./gfree -f".
Sent from my HTC Desire Z
elracing21 said:
Well I'm rooted with the old method as well but because I I cant flash cwm 3.x with the gree method. You need the eng hboot so ill stick with the old method until clockwork makes it work with the gfree method.
Sent from my gSpot2
Click to expand...
Click to collapse
Using gfree does not get rid of the engineering hboot (or modify your existing hboot in anyway), so it's safe to do. And even if this was not the case, you can still flash the CWM3 recovery without the engineering hboot, only you'll have to use a different method than fastboot.
dhkr234 said:
Since you have root and a stock rom installed, just run gfree -- that is ALL you need to do. The advantage, aside from unlocking the radio, is that with the proper s-off, there is some new security for the radio... for unbricking and for being able to withstand accidental OTA updates. A true radio s-off can take an OTA update containing BOTH an SPL and a Radio, and yet s-off remains.
Click to expand...
Click to collapse
thanks for responding. so this will work even though i dont have a stock kernel?
also, as far as OTA's go, you mean that if after i run gfree i will be able to apply the OTA without it unrooting my phone?
thank you
konoplya said:
thanks for responding. so this will work even though i dont have a stock kernel?
also, as far as OTA's go, you mean that if after i run gfree i will be able to apply the OTA without it unrooting my phone?
Click to expand...
Click to collapse
Not sure about Baconbits, check the Wiki for the list of kernels that are known not to work with gfree.
If you apply the OTA after unlocking with gfree, you will still lose root but you won't lose the S-OFF and other stuff from gfree.
Sent from my HTC Desire Z
steviewevie said:
Not sure about Baconbits, check the Wiki for the list of kernels that are known not to work with gfree.
If you apply the OTA after unlocking with gfree, you will still lose root but you won't lose the S-OFF and other stuff from gfree.
Sent from my HTC Desire Z
Click to expand...
Click to collapse
ok, i see. so if i loose root would i just have to run gfree again after I install OTA to gain root back?
konoplya said:
ok, i see. so if i loose root would i just have to run gfree again after I install OTA to gain root back?
Click to expand...
Click to collapse
Not just gfree on its own, but you will need to go through the steps of getting temp root then perm root, which does use gfree as part of it. It's all in the Wiki.
konoplya said:
ok, i see. so if i loose root would i just have to run gfree again after I install OTA to gain root back?
Click to expand...
Click to collapse
gfree does NOT root your phone. It UNLOCKS RADIO SECURITY -- permanently. You only run it ONCE, you NEVER have to run it again... EVER.
With UNLOCKED RADIO SECURITY, gaining root is TRIVIAL.
What gets root is RAGE or PSNEUTER.
dhkr234 said:
gfree does NOT root your phone. It UNLOCKS RADIO SECURITY -- permanently. You only run it ONCE, you NEVER have to run it again... EVER.
With UNLOCKED RADIO SECURITY, gaining root is TRIVIAL.
What gets root is RAGE or PSNEUTER.
Click to expand...
Click to collapse
Yeah but gfree is often used as part of the rooting process, so I can see why people associate gfree with rooting.
gfree might be run more than once on a phone as part of the process to lock in root, i.e. to defeat the NAND write protection. Even though it's only needed once to unlock the radio etc, you might run it other times if you need to root a stock ROM and updates to that ROM.
gfree can be used to unlock radio security, but it has other options too. Sorry but I think your reply might confuse more people than it helps.
x
Help me please! I tried to find my answer, but i'm not sure.
Can be possible use the update.zip without any modification? Or i need change the hboot?
Thank you!
Janaboy
I'm perm rooted! but I lost the ota update cause I was simi-brick how can I get the OTA update? do I have to to a factory reset?
You should get the OTA right away after restarting the phone, I know I did after going back to stock on just Saturday of this week. The first time I connected to the network it said an update was available and it was the OTA.
that hasnt happen and it need to hurry up!! lol
So do a Factory reset?
hiya guys, im kinda in the same boat. Just got the g2 with build 1.22.531.8 and perma rooted it with visionary/rage method. I want to get supercid, sim unlock with gfree. can someone post or direct me to instructions on how to do so? thanks for helping a noob.
aok680 said:
hiya guys, im kinda in the same boat. Just got the g2 with build 1.22.531.8 and perma rooted it with visionary/rage method. I want to get supercid, sim unlock with gfree. can someone post or direct me to instructions on how to do so? thanks for helping a noob.
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Unlock_the_Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF

HTC Desire HD 2.3 update problem

Hi,
I'm in the UK and had the 2.3 update notification a couple hours ago. I have downloaded it and after clicking install I get an exclamation mark with a green Android robot on my screen and nothing happens.
Anyone else getting this?
Just some background info. I have stock Sense Android 2.2 which I have used Visionary to perm root with S-OFF. I have used Visionary to unroot and used the app called Root Checker to see if I am rooted and it says I am not rooted.
Do I need to get S-OFF back on aswell and if so how?
Sent from my Desire HD using XDA App
ToneyEricsson said:
Hi,
I'm in the UK and had the 2.3 update notification a couple hours ago. I have downloaded it and after clicking install I get an exclamation mark with a green Android robot on my screen and nothing happens.
Anyone else getting this?
Just some background info. I have stock Sense Android 2.2 which I have used Visionary to perm root with S-OFF. I have used Visionary to unroot and used the app called Root Checker to see if I am rooted and it says I am not rooted.
Do I need to get S-OFF back on aswell and if so how?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Do you have a recovery?, i dont know if this would work but it did work for me before, have you tried flashing it within the recovery?
I haven't no I was recommended to follow these instructions to get rooted and S-OFF to get apps like Adfree etc working
http://forum.xda-developers.com/showthread.php?t=857537
I have undone Visionary so I am not rooted anymore but the 2.3 update wont install.
Would this be because of S-OFF still being off do you think and needs to go back on?
ToneyEricsson said:
I haven't no I was recommended to follow these instructions to get rooted and S-OFF to get apps like Adfree etc working
http://forum.xda-developers.com/showthread.php?t=857537
I have undone Visionary so I am not rooted anymore but the 2.3 update wont install.
Would this be because of S-OFF still being off do you think and needs to go back on?
Click to expand...
Click to collapse
Yeah you would need S-OFF to be not off to install updates the normal way
cashisback, you are wrong. S-OFF does not matter. Get the official 2.36.405.8 RUU from the dev subforum and install it.
It is because you remove some preinstalled apps such as Amazon MP3,News etc. I did it myself and i had to reinstall stock RUU.and then it worked. It worked even with S-OFF. I still have S-OFF after update. Good Luck.
I haven't uninstalled any preinstalled apps.
All I have done is simply following those instructions to get rooted with Visionary and S-OFF so apps like Adfree, Drocap2 etc to work.
So instead of getting the OTA over wifi I have to now flash to a stock RUU? I haven't even flashed an RUU before, any help with that would be good.
jkoljo said:
cashisback, you are wrong. S-OFF does not matter. Get the official 2.36.405.8 RUU from the dev subforum and install it.
Click to expand...
Click to collapse
@jkoljo I have a stock RUU on my phone, can I not just do the latter part of these instructions?
http://forum.xda-developers.com/showthread.php?t=857537
To go back to S-ON:
Temproot using Visionary
Use my tool, do Stock CID and S-ON (enter brand CID if you had a branded device, see second post)
Enjoy your factory-state phone
And then update to 2.3 via OTA?
Edit: I tried it, it doesnt seem to be possible to get S-OFF back on using the tool?
Thanks for making me aware of this thread, OP!
My phone is ENG/S OFF and I'm using the stock rom. I'm quite certain that I haven't uninstalled any stock apps so I don't think that's related.
Regarding S-OFF: If this was the cause (and I cannot really see how it could be - but I'm at most a layman at this), there would be many more users getting this error, right?
Just to add what I've written in the main 2.3 update thread:
When entering CWM I get this error message regarding the OTA update:
Code:
ClockworkMod Recovery v3.0.0.6
Finding update package...
E:unknown volume for path [SDCARD:download/OTA_Ace_....zip]
E:Can't mount SDCARD:download/OTA_Ace_....zip
Installation aborted.
I've abbreviated the name of the file. It might be/is a stupid idea but... might the file name be too long (90 characters) for some weird format of my/our SD card? Rights: drw, format should be FAT32 - any idea how to check this on the phone?
Sorry for probably not making much sense
ToneyEricsson said:
@jkoljo I have a stock RUU on my phone, can I not just do the latter part of these instructions?
Click to expand...
Click to collapse
Keep S-OFF, trust me, you will not regret it.
baum01 said:
ClockworkMod Recovery v3.0.0.6
Finding update package...
E:unknown volume for path [SDCARD:download/OTA_Ace_....zip]
)
Click to expand...
Click to collapse
You cannot flash OTA in clockworkmod, come on..
Make sure that you have Radio S-OFF and then use Gingerbread RUU.
@jkoljo I see your point obviously still will be able to get rooted apps working in 2.3.
But I'm complete new to all this flashing RUU stuff.
Which thread is this RUU that I need and how do you flash the DHD?
The HTC Desire HD I have is unlocked sim free and I am in the UK if that makes any difference. My current software version is the 1.32.405.6 one which I think is the world wide version.
jkoljo said:
You cannot flash OTA in clockworkmod, come on..
Make sure that you have Radio S-OFF and then use Gingerbread RUU.
Click to expand...
Click to collapse
Then you will imagine my surprise when after pressing the power button briefly (while the triangle was shown) CWM was shown. Is it possible that I have to 'deactivate' it for the OTA to install itself?
(I'm currently running 1.72.405.3)
I am currently in the same boat as you same error as well.
Thanks for pointing me this way same issue here. If I'd have known it was gonna cause FOTA issues I wouldn't have bothered with root as I only wanted it for root explorer to regain the standard lock screen and thought that I'd do the Radio S-OFF and and SUPERCID in case HTC didn't live up to their word.
Chuffin annoying to say the least.
i keep getting the signature verification failure
Anyone know how to get passed this verification error? Thats what I'm having too. Click install update and on reboot theres an exclamation mark which stays there.
I've updated CWM to the latest version and tried the OTA installation again. Same triangle error after reboot, no option to get to the CWM screen and only the removal of the battery helped to restart the phone. This probably doesn't help but I thought to let you know.
I'd have used the RUU already (or another ROM) but I'm a bit hesitant of having to reconfigure my device completely again. Besides, there should be an easy solution for this problem. There always is
Sent from my Desire HD using XDA App
thanks for pointing this whole thread
i'm in Australia, and have Desire HD by Vodafone, and all i have done is permroot with visionary in order to have superuser access to be able to run Samba server on my phone.
OTA update by Vodafone is still not avail, but I wonder now, if I will be facing any kind of problem while updating ?? (p.s. only super user access is taken and only visionary was used, phone still has stock rom and no modifications)
Just so everyone is aware if having this problem. I flashed my DHD with the stock 1.32 the same as what was originally on my DHD and then was able to get the 2.3 update without any problem which I currently am on.
Alternative if you still want root and S-OFF probably be worth flashing with the leaked Gingerbread ROM from 1.32 with root and S-OFF already done. I may try this, does anyone know if there is a .zip of it so can flash from SD card?
Sent from my Desire HD using XDA App
Same issue on Vodacom South Africa DHD.
Standard install of 2.3 update shows the exclamation mark / droid image.
Booting into ClockworkMod and manually applying the update.zip file yields
====================
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
====================
DHD has been rooted a while back, installed CyanogenMod, reverted to backup ROM.
Running ClockworkMod Recovery 3.0.2.6

S-OFF and no root, what do?

Here's the story. Got my original G2, played with it, rooted, s-off, the works. Needed to send it in for a warranty exchange so I unroot, s-on, etc etc, and put gingerbread on it. So I had the pc10img file on my sdcard.
Fast forward, I got my replacement G2, it had Froyo, had it rooted, s-off, the works before the battery was even finished charged (I waited for it to finish before I rebooted of course!) and I loaded up the official MIUI. usb tethering wasn't working so I figured I would download and flash a pershoot kernel! That "bricked" it. Wouldn't boot at all! So I booted it in to recovery (vol down + pwr) forgetting that the official gingerbread pc10img was on the sdcard. I was out and about so I just needed my phone back ASAP, so I went ahead and flashed it. So now I have stock gingerbread, with S-OFF and no way to get root. Is there another pc10img I can flash that is pre-rooted, or am I SOL til someone figures out how to root the latest update?
I'm gonna try gingerbreak after posting since I DO have s-off still...
silverton said:
Here's the story. Got my original G2, played with it, rooted, s-off, the works. Needed to send it in for a warranty exchange so I unroot, s-on, etc etc, and put gingerbread on it. So I had the pc10img file on my sdcard.
Fast forward, I got my replacement G2, it had Froyo, had it rooted, s-off, the works before the battery was even finished charged (I waited for it to finish before I rebooted of course!) and I loaded up the official MIUI. usb tethering wasn't working so I figured I would download and flash a pershoot kernel! That "bricked" it. Wouldn't boot at all! So I booted it in to recovery (vol down + pwr) forgetting that the official gingerbread pc10img was on the sdcard. I was out and about so I just needed my phone back ASAP, so I went ahead and flashed it. So now I have stock gingerbread, with S-OFF and no way to get root. Is there another pc10img I can flash that is pre-rooted, or am I SOL til someone figures out how to root the latest update?
I'm gonna try gingerbreak after posting since I DO have s-off still...
Click to expand...
Click to collapse
To my knowledge there is still no temporary exploit for gingerbread that you would need to gain permanent root, sorry. It looks like you might be sol, but since you do have s-off try some of the other exploits like psneuter or gfree and post back. I would be very intrested if the hboot was somehow responsible for keeping the gingerbread g2's from getting root
Sent from my self-aware G2 w/ PyroMod v2.3.4 & UnNova Theme v1.0
gingerbreak did not work for me. I get this with the psneuter tool
spirit platform-tools # ./adb shell /data/local/tmp/psneuter
Failed to set prot mask (Inappropriate ioctl for device)
Click to expand...
Click to collapse
Did you flash the engineering HBOOT during the rooting process?
theSpam said:
Did you flash the engineering HBOOT during the rooting process?
Click to expand...
Click to collapse
Good question. I'm not sure actually. But I do know right now that it has an official HBOOT on it. 0.82.0008
silverton said:
Good question. I'm not sure actually. But I do know right now that it has an official HBOOT on it. 0.82.0008
Click to expand...
Click to collapse
I'm unsure if HTCs .zip includes a HBOOT update or not...but can you enter HBOOT (power+vol down) and check if it says SHIP S-OFF or ENG S-OFF?
I think that, since you're S-OFF, you'll be able to apply any PC10IMG.zip since it won't check signatures/versions - can someone correct me on this if I'm wrong?
theSpam said:
I'm unsure if HTCs .zip includes a HBOOT update or not...but can you enter HBOOT (power+vol down) and check if it says SHIP S-OFF or ENG S-OFF?
Click to expand...
Click to collapse
It says SHIP S-OFF. And I was also thinking that since it is S-OFF that I could flash a PC10IMG that was already rooted, but seems almost all roms these days are only clockwork flashable.
Sent from my T-Mobile G2 using XDA App
SUCCESS!
Back to semi-square one anyway.
I was able to successfully flash the shipped rom as a PC10IMG which I got here (http://shipped-roms.com/index.php?category=android&model=Vision) and I'm going to say that this is most likely because I am radio s-off.
silverton said:
SUCCESS!
Back to semi-square one anyway.
I was able to successfully flash the shipped rom as a PC10IMG which I got here (http://shipped-roms.com/index.php?category=android&model=Vision) and I'm going to say that this is most likely because I am radio s-off.
Click to expand...
Click to collapse
It is because u were s-off. That was my configuration also so if I flash that official gb PC10IMG I'm still s-off but unrooted. To reroot I simply flash the 1.19 PC10IMG, let it get the 1.22 OTA if I feel like it then psneuter/gfree it all over again.
PS - to anyone else... don't even bother with gingerbreak for that official gb
Sent from my HTC Vision using XDA App
I would put anything with root on it, just to get cwm. Than do as you normally would. As you may know, things are far easier through recovery.
::edit:: you should be able to find a custom built pc10img zip thingy, somewhere on these forums or from someone.
I'm sure you can easily make your own, and it should work.
Goodluck.
Sent from my HTC Vision using XDA Premium App

Patched (hard)hboot 1.04 for s-off/eng/fastboot

Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
UPDATE 8/1/2011: This has been updated to now block normal hboot flashing to make it much safer. It's still wise to not arbitrarily flash things but you should rest a little more at ease now.
Thread update (not a new version):
Here is the commands to re-flash hboot after installing this:
"fastboot oem mw 8d08ac54 1 31302E30"
"fastboot flash hboot whateverhbootfile.nb0"
where whateverhbootfile.nb0 is in your path, you can get this file by unzipping the PG05IMG.zip with a hboot in it
(BE CAREFUL WITH THIS, YOUR PHONE WILL FLASH TETRIS.EXE AS A BOOTLOADER IF YOU ASK IT TO)
Enjoy.
Sweet thanks
Sent from my ADR6400L using XDA Premium App
Thank you sir, I shall try this soon.
This is not newer than the ENG, its actually the same version number. The ENG one came from a 1.12.605.6 eng ruu (same as shipping)
Will this block hboot flashing like the alpharevx one (please say yes)
Shadowmite said:
Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
Enjoy.
Click to expand...
Click to collapse
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Shadowmite said:
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Click to expand...
Click to collapse
I ended up not releasing the older one, as I had both (im not sure if joshua was given both or not).
Once you add blocking hboot flash (artificially high version number does it i think??) would it be ok to place in my guide until (if/when) yall release a package? (I intend to remove mine once a reliable "auto" is out).
Flashed for fun and it works great.
Having another method of root may not mean much to Tbolt owners now but it will once devices start shipping with GB.
Great to have you guys working on this.
so this a a way to root in the future for GB owners? just want to make sure so i dont flash if i dont need to because i am already rooted
Shadowmite said:
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Click to expand...
Click to collapse
excellent! i personally would love a permanent s-off patch. ill be watching this thread,thank you kind sir.
thanks,Shadowmite
Shadowmite said:
Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
Enjoy.
Click to expand...
Click to collapse
Hey,
Might you guys post your IDB of this hboot? or send it to me via PM? or somehow. Id love to see the breakdown of the file you guys reversed.
and what patches. Thanks!
Thanks shadowmite. I followed your work way back in the 6600 days...
Sent from my ADR6400L using Tapatalk
running it now,no issues. used it to flash a recovery,and change my radios. also verified it has the same available fastboot commands.
feel free let me know if you need any kind of feedback,or help with testing. id be more thaN happy to help test a permanent patch
Ok, updated main post with new updated hboot. Now patched to block normal hboot flashes which should make it a lot safer. To test, flash the update, then try flashing it again. The second one should not take.
yes! thank you kind sir. so,if im understanding correctly,it will prevent the flash of any other hboot,including the original engineering one?
downloaded and about to flash
scotty1223 said:
yes! thank you kind sir. so,if im understanding correctly,it will prevent the flash of any other hboot,including the original engineering one?
downloaded and about to flash
Click to expand...
Click to collapse
Correct. I figure eventually someone might need to flash back to a original and ill eventually toss up instructions how to do this. For now, this should block everything we've seen for the device to date.
Is revolutionary working on root for the thunderbolt? Will it give us true s-off?
from the first post,no it will not give us true s-off. im running it now,tried flashing the stock s-on hboot and the old eng hboot and it blocked them both
next question: if one installed a stock recovery,and accepted an OTA... would this prevent hboot from being overwritten there as well?
Yes it should always block hboot unless they do something purposeful to overcome the block method. I'll post a command in the first post sometime next week that will allow you to overwrite hboot should you want to.

Categories

Resources