I have a few questions about s-off and being in the latest OTA.
Here is the short and skinny...
When my wife got the evo when it first was released last year i tried to root it since i wanted to install a program that needed root. i had no real idea on what i was doing and think i might have gotten root, although I am not sure. I never flashed any rom nor did I ever flash that apk and just gave up since I didnt want to break her new phone. (basically got a bit scared)
As for the main screen if you reboot and hold down volume and power, it will display "s-OFF".
She did the two Gingerbread updates OTA and is now on GB 2.3.3. stock.
I noticed that the hboot is set at 2.16...and it still displays "s-off".
I just read that there are different types of "s-off".
Now, the questions are:
1. Is her phone actually rooted?
2. Can I turn on the "s-off" to "S-ON" so that we can bring the phone in for repair?
3. Is there anything that anyone here can gain from her phone being in the state that it is in for people who cant get root under the latest hboot version?
4. I just read that s-off has multiple meaning. How can i tell which one I have on her phone? ie. radio, nand??
Thanks in advance.
pretty sure sprint wont notice the s off so dont bother going s on to ttake it in, even if they do, they dont really care anymore, so long as its got the stock os at least, but they really dont care bout it being rooted anymore
but yeah, your phone basicaly kept the root
I agree with LCL22.
Unrevoked does have an S-ON tool, but I've never used it and I'm not even sure it works anymore. Just leave it S-OFF and flash one of the stock unrooted ROMs from recovery. But I've heard people take their phones back with CM6/CM7 on there, MIUI, etc. It probably depends on the store/rep to be honest.
"Rooted" means having access to the SU binary (superuser). It's a linux thing. It's like having Administrator access to a windows computer. This allows complete control over the currently installed phone software.
S-OFF means that the phones protections have been disabled and you are free to flash unsigned ROMs via the bootloader (HBOOT).
S-OFF is nice, because you can flash any ROM you want via the bootloader; there is no need for a custom recovery to be installed. Of course you can also use the bootloader to flash a custom recovery such as ClockworkMod or Amon_RA.
github said:
I agree with LCL22.
Just leave it S-OFF and flash one of the stock unrooted ROMs from recovery.
Click to expand...
Click to collapse
Will flashing the latest unroot ROM from sprint (which is already on there from the OTA update) will turn the s-off to s-on??
Also, if it says s-off, does that mean that it is fully rooted?
The reason why she is considering bringing it into sprint for repair/replace is that is having problems sending texts multiple times to the person she is texting...basically, she sends one text and the receiver gets the same text 20 times.
Either there is something wrong with the phone, the network, or the fact that it is s-off and she is running a non-rooted rom. This issue has been happening since January and on the stock Froyo.
Lastly, I just noticed that she had advanced task killer and I uninstalled it just to make sure it wasnt anything that she has running which is causing the issues.
Thanks in advance.
amart79196 said:
Will flashing the latest unroot ROM from sprint (which is already on there from the OTA update) will turn the s-off to s-on??
Also, if it says s-off, does that mean that it is fully rooted?
The reason why she is considering bringing it into sprint for repair/replace is that is having problems sending texts multiple times to the person she is texting...basically, she sends one text and the receiver gets the same text 20 times.
Either there is something wrong with the phone, the network, or the fact that it is s-off and she is running a non-rooted rom. This issue has been happening since January and on the stock Froyo.
Lastly, I just noticed that she had advanced task killer and I uninstalled it just to make sure it wasnt anything that she has running which is causing the issues.
Thanks in advance.
Click to expand...
Click to collapse
S-off only means you are nand unlocked so you can flash a custom recovery and flash a ROM. To be rooted, you have to flash a rooted rom which 99.999% of all the ROMS are rooted on XDA.
S-off just means that you can flash an alternate recovery and custom roms. It doesn't mean that it is rooted.
check in your app list and see if the Superuser app is there. If it isn't, it probably isn't rooted.
S off is perfect! Don't go s on if you can help it.
At my local repair store I chatted with the tech (after running s on tool) if they even check. The guy said not usually. They mainly check if it is stock sense like the Rosie and stuff. And even then they don't usually. They only check if someone brings in their phone with technical or software issues. With hardware they don't bother.
But that is my store.
S off and root are separate things but they kind of depend on each other. To root permanently you need s off, at least for devices with nand.
Sent from my PC36100 using Tapatalk
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
amart79196 said:
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
Click to expand...
Click to collapse
Sprint is currently having issues on their end in regards to texting. I've attached an article that you can read over.
http://m.wired.com/gadgetlab/2011/07/sprint-sms-text-problem/
ENG S-OFF
EDIT: Nevermind, I just took the risk and it paid off.
I was actually about to start a thread asking the exact same thing. I'm selling my phone and I've heard that if it's not relocked it can't be activated on the Sprint network so I've been trying to get S-ON. I have "EVT2-2 ENG S-OFF" right now.
By the sounds of this all I really need to do is flash a good PC36IMG and all should be good, right? No chance of a brick?
i will read that shortly, but i am more interested in the fact that there is a OTA update done and it now has 2.16 as the hboot. Is this now going to brick if i try to flash a rooted stock rom since she isnt into custom roms?
Now, the questions are:
1. Is her phone actually rooted?
2. Can I turn on the "s-off" to "S-ON" so that we can bring the phone in for repair?
3. Is there anything that anyone here can gain from her phone being in the state that it is in for people who cant get root under the latest hboot version?
4. I just read that s-off has multiple meaning. How can i tell which one I have on her phone? ie. radio, nand??
Thanks in advance.
Click to expand...
Click to collapse
Answers :
1. If you flash a recovery.img it will be.
2. You can't really do anything with the s-off right now because I don't think that any of the tools that would do that have been updated to work with hboot 2.16.
3. I'm not sure if anyone can use what you have but I would write up a post in a dev thread to be sure.
4. There are only two meanings that I know of when it comes to s-off. The first is accepting the OTA while rooted which will put your phone in a weird state. If you can use your phone after then I don't think this applies to you. The other is just not having a recovery installed which will render you just unlocked and not rooted.
amart79196 said:
i will read that shortly, but i am more interested in the fact that there is a OTA update done and it now has 2.16 as the hboot. Is this now going to brick if i try to flash a rooted stock rom since she isnt into custom roms?
Click to expand...
Click to collapse
No. Flashing a regular rooted odex or deodex version of the RUU won't hurt you if your s-off. I would make a nand backup using amon ra recovery before flashing anything just to be safe.
Amon Ra Recovery - http://forum.xda-developers.com/showthread.php?t=705026
Rooted OTA ROM - http://forum.xda-developers.com/showthread.php?t=1133379
amart79196 said:
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
Click to expand...
Click to collapse
It doesn't matter what hboot you have so long as you're s off
No bricks don't worry. Bricks usually occur during manual radio updates
Sent from my PC36100 using Tapatalk
Related
alrighty so here it is the ota is coming and i silly as i may be rooted like 3-4 days ago. i didnt take the time to s-off just got the custom recovery updated the radio to 2.05 and downloaded sky raider vanilla. hboot is .79.
now from my research that ive gather and correct me if im wrong but all i need to do is :
*s-off
*flash the stock recovery
after that i should be good for the ota correct?
so far i got the s-off done looking for a lil bit of instruction as to how to get the stock recovery flashed safely.
Any and all help is greatly appreciated i thank you all very much.
inessi said:
alrighty so here it is the ota is coming and i silly as i may be rooted like 3-4 days ago. i didnt take the time to s-off just got the custom recovery updated the radio to 2.05 and downloaded sky raider vanilla. hboot is .79.
now from my research that ive gather and correct me if im wrong but all i need to do is :
*s-off
*flash the stock recovery
after that i should be good for the ota correct?
so far i got the s-off done looking for a lil bit of instruction as to how to get the stock recovery flashed safely.
Any and all help is greatly appreciated i thank you all very much.
Click to expand...
Click to collapse
I have attached the stock recovery that needs to be flashed from the HBOOT.
It is my understanding however, that you need to downgrade to the .77 HBOOT, 1.xx radio AND 2.1 system for the update to notify you, give you the option to download, and install successfully. However, I am a few drinks into my night.
If you choose to follow that path. I suggest you read this
awesome stuff really appreciate it man gonna give it a try now, fellow floridian lol
inessi said:
awesome stuff really appreciate it man gonna give it a try now, fellow floridian lol
Click to expand...
Click to collapse
w00t!
If you get hung up anywhere, pm me and I'll give you a number to call me at in the morning/afternoon and I'll walk you through it.
your my hero bud, my freaking hero stock recovery got s-off i think thats all i need to recieve the ota and do it yea?
thnx
See, from this point, I'm not sure if you need the .77 HBOOT 1.xx Radio and 2.1build-1 on your phone (I'm really questioning it, as I beleive I read in a few places that you do, but I'm not sure at this point in the evening). I don't think the Skyraider rom will get a notification when the update is available. I'd say if you don't get a notification for the update when everyone else in the free world is, then you may have to.
As long as you have S-OFF, it doesn't matter either way, you have complete control for the rest of your phone's life. Whatever you do, don't turn it back on lol.
hmmm well if it doesnt show up guess my next set of questions is how to get back to stock everything
inessi said:
hmmm well if it doesnt show up guess my next set of questions is how to get back to stock everything
Click to expand...
Click to collapse
The link I posted above with the "I suggest you read this" line is where you will need to go if it boils down to that.
o haha some how i missed that lil section of text did you just add that recently?
but ok sounds good ill run through it in the morning probably
and holy crap the link you posted makes this all look so simple hah
Well I have stock everything, except for my hboot is .79, im on stock 2.1 stock recovery just have .79 hboot not .77, i think i will still get the update though...
rdmerck said:
thnx
See, from this point, I'm not sure if you need the .77 HBOOT 1.xx Radio and 2.1build-1 on your phone (I'm really questioning it, as I beleive I read in a few places that you do, but I'm not sure at this point in the evening). I don't think the Skyraider rom will get a notification when the update is available. I'd say if you don't get a notification for the update when everyone else in the free world is, then you may have to.
As long as you have S-OFF, it doesn't matter either way, you have complete control for the rest of your phone's life. Whatever you do, don't turn it back on lol.
Click to expand...
Click to collapse
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?
magneto417x said:
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?
Click to expand...
Click to collapse
Other than the root, did you modify anything else to your phone?
If not, your still with the .77 HBOOT, 1.xx baseband, and 2.1update-1 system?
Add unrevoked forever to remove s-off, then flash the stock recovery back to your phone. Your goal here is to have S-Off
in order to get the OTA (from my understanding) you need the stock recovery, do a little search I have all the faith in the world that you will find what you are looking for. you want to run unrevoked forever BEFORE you accept the OTA2.2, so this is your steps, root, run unrevoked forever getting S-OFF, find the file for the stock recovery, PB..IMG file, flash that in hboot, this will set u back to stock 2.1 update1, stock radio, stock recovery, but still have S-OFF to regain root, after the OTA comes.
So if I have stock everything, and have hboot .79 will I still get the OTA I don't see why not...
BlazeD OnE said:
in order to get the OTA (from my understanding) you need the stock recovery, do a little search I have all the faith in the world that you will find what you are looking for. you want to run unrevoked forever BEFORE you accept the OTA2.2, so this is your steps, root, run unrevoked forever getting S-OFF, find the file for the stock recovery, PB..IMG file, flash that in hboot, this will set u back to stock 2.1 update1, stock radio, stock recovery, but still have S-OFF to regain root, after the OTA comes.
Click to expand...
Click to collapse
Currently the only thing I have done was rooted and removed CityID and but have not changed the radio or anything else. I have installed Unrevoked forever now. So do I still need to flash stock recovery even though I haven't changed the boot files or radio files at all?
Yes from what I've read you HAVE to have the stock recovery. what is your HBOOT once u get stock recovery?
BlazeD OnE said:
Yes from what I've read you HAVE to have the stock recovery. what is your HBOOT once u get stock recovery?
Click to expand...
Click to collapse
My HBOOT is 0.79.0000
Radio 1.00.03.04.06
Any input would be helpful as to whether I will get OTA or do I need to do something.
once in hboot, go to recovery, if you have clockwork you wont get it i dont think, if you get a red triangle you have stock recovery and you are good to go.
magneto417x said:
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?
Click to expand...
Click to collapse
Yes, install unrevoked forever. The fact that you are rooted will not affect the ability of your upgrade, it is the lack of the stock recovery that will halt you.
Unrevoked forever will allow you to flash ANY zip file you want to the phone (namely a zip that has su and Superuser.apk) and will allow you to regain root in the event that it is ever lost due to an OTA or user error.
S-OFF is a beautiful thing.
I would love to take my phone to Verizon right now with a manufactured problem, let him see the Superuser, official 2.2 system and then stock recovery. Could be priceless!
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Is the phone s-off?
Sent from my PC36100 using XDA App
badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
animal7296 said:
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
Click to expand...
Click to collapse
Are either of these rootable yet?
and can someone explain what S-on and off means?
badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
1. 2.02 is rootable 2.10 is not and is the newest one.
2.0 S-ON means you can not flash roms s-off means you can. It is the security of the phone kind of.
If you can not get into bootloader then you can try running the oldest ruu and then the next. It wont hurt the phone at all (I just did it today) it will just give you an error and reboot the phone.
pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Sent from my PC36100 using Tapatalk
badutahboy said:
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
Click to expand...
Click to collapse
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
luckylui said:
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Click to expand...
Click to collapse
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Sent from my PC36100 using Tapatalk
tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
True this, but when i did it i was at 0.76.2 and now screw at 2.10 cause it updated all the way n i didnt want to do that.. Got lost in the tangle haha
Sent from my PC36100 using Tapatalk
tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
Yea, I heard about this in the IRC; too bad these guys can do that... unfortunate; but I'm sure the Unrevoked team will have a fix soon enough.
luckylui said:
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Click to expand...
Click to collapse
Good luck with Sprint; I don't know how helpful they're going to be, but you never know...
@luckylui and animal7296, check out the 2.02/2.10 rooting thread again, it seems they got something working. Good luck.
badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
There actually is a way to downgrade without rooting, all you need to do is flash the mtd-eng.img file to your misc partition as explained in toast's rooting part 2 thread. After you do that it will let you flash any ruu that is compatible with your phone
Sent from my PC36100 using XDA App
My wife got her replacement Inc2 today after the one she got last week just died. She was on Froyo so I might of.. swapped her phones.. anyways, I rooted, went to the bathroom and the stupid ota ran I guess because when I came back the phone was on GB 2.3.3 however my boot screen shows S-OFF. Can anyone help me to verify that S-OFF is indeed still off. I can post any screen shots etc.. I am still a noob when it comes to the Inc2.
If your boot screen says S-Off, you are S-Off
Sent from my stock, bloated ADR6350 using XDA Premium App
Did you flash clockworkmod recovery when you rooted? I didn't think the OTA would take if you had a custom recovery. In any event, since you're still s-off, you're fine.
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
kujayhawks77 said:
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
Click to expand...
Click to collapse
Alpharev changed ur hboot to a higer version than the one in the OTA.. this is why it kept you S-OFF.. if I'm wrong someone correct me.
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
kujayhawks77 said:
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
Click to expand...
Click to collapse
No. stock hboot is .97. alpharev bumped you up to 1.something.. idk I used XTC clip.. since your hboot is newer than the OTA.. it keeps you S-OFF, pretty smart by alpha.
So does this open a gateway to first root in Froyo and then go gingerbread and retain the root?
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Now when I use the term "gateway" I say this loosely because it doesn't fix anything for anyone who is already on GB. If indeed this works, it would only work for a small percentage who get Froyo and don't flash clockwork before running the OTA.
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
tnez said:
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
Click to expand...
Click to collapse
2.1??? I think you are mistaken, sir
beenz said:
2.1??? I think you are mistaken, sir
Click to expand...
Click to collapse
He was mistaken cause it is sense 2.1 but android 2.2
Sent from my Incredible 2 using XDA Premium App
kujayhawks77 said:
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Click to expand...
Click to collapse
I've been wondering about this. I got my Dinc2 early July and I'm still on stock, unrooted Froyo. Somehow the OTA update to GB hasn't hit yet. Could I run ApharevX to get S-off and stop there for now? I am happy with bloated stock for the time being and want to be able to receive OTA updates, but would like to have the option down the road to add Clockworkmod and flash custom ROMs. From kujayhawks experience it seems that this should be possible.
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
P.S. First post, though I've been lurking around for a while. Great forum/community.
xenakis said:
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
Click to expand...
Click to collapse
It appears from reports that S-off stays after the OTA to 2.3, so yea, that would seem to be the case.
If you turn S-off with AlphaRev, you might want to just go ahead and install Clockwork recovery at the same time. Doing so won't root or install SuperUser or anything, but you would be able to then backup your phone and be ready to flash if you wanted.
If you install clockwork recovery you won't be able to receive OTAs though, just keep that in mind. You can flash back to the stock recovery, but unless you are familiar with ADB, it won't necessarily be an easy process.
So I'm ending Verizon and need to give my phone to best buy for the buyback program but I don't think they will take it running rooted I know the new ota is out but what do I do to do this ota do I flash a froyo stock rom? Or ...
Help me out guys thanks alot ill miss my incredible and y'all aswell
Ill be getting att infuse 4g over the HTC inspire 4g I think..
Sent from my NookColor using Tapatalk
I'd put it back to stock 2.2. There are a couple "get back to stock" threads in the development section, basically you'll just have to flash the S-ON zip in recovery, then flash the stock 2.2 RUU.
Just wondering, does Verizon refuse to work on your phone if it is rooted? Different scenarios:
1) Hardware issue. Do they care if it is S-Off and has a custom ROM?
2) Will they not even touch a phone that is obviously rooted?
3) Do they care about S-Off when you take it in?
Evo 4G over here, Sprint works on rooted phones. If it is a software issue they will RUU you, but won't mess with S-Off
Thanks! this is helpful
tropicalbrit said:
Just wondering, does Verizon refuse to work on your phone if it is rooted?
Click to expand...
Click to collapse
I personally would return the phone to stock before returning it for a hardware issue, but I think most Verizon employees (a) don't care about rooting because their phones are probably rooted as well, or (b) wouldn't even know what S-OFF means or what to look for to determine if a phone's rooted. This is assuming you're just going in to your neighborhood Verizon store for a few questions or something, not for warranty issues, those people that receive the phones might look for root, who knows?
I think there's a lot more paranoia about rooting and Verizon's stance on it than is warranted though. I've seen all sorts of rumors about Verizon "tracking" rooted users, or building a database of rooted phones. Those kind of rumors have been going on for a while with no sort of confirmation or anything whatsoever coming from them.
FWIW, I've returned a rooted, s-off Incredible, with an Unrevoked splash screen to Verizon for a warranty repair. The employee did not care. (or maybe they just didn't have a clue.)
k_nivesout said:
I'd put it back to stock 2.2. There are a couple "get back to stock" threads in the development section, basically you'll just have to flash the S-ON zip in recovery, then flash the stock 2.2 RUU.
Click to expand...
Click to collapse
Question
I flash both at the same time like
S-on tool then right away stock ruu?
Sent From My Optimized HTC Incredibly Dinc
The timing doesn't really matter, but the S-ON zip has to be flashed in recovery whereas the RUU is flashed in hboot. The RUU replaces CWM recovery with the stock recovery, and you couldn't flash the S-ON zip with the stock recovery. But it shouldn't matter as far as flashing the RUU *right* after the S-ON zip, since the RUU is official HTC firmware, you can flash it with S-ON, anytime. Bear in mind that you can't downgrade with S-ON though, for example, if you flash the 2.3 RUU (with S-ON) there's no way to get back to 2.2.
Thinking about it, even if you flashed the RUU first, you still have S-OFF, so would be free to install a custom recovery & superuser then flash back to whatever.
I'm to this point and I do have some back ups but I wanted to know if I can acheive s-off where I'm at or do I need to go back to stock? Forgot to mentioned I'm unlocked and when I relocked while running a custom rom I got security warning so I quickly unlocked and it didn't seem to hurt anything I'm aware of.
farcus211 said:
I'm to this point and I do have some back ups but I wanted to know if I can acheive s-off where I'm at or do I need to go back to stock? Forgot to mentioned I'm unlocked and when I relocked while running a custom rom I got security warning so I quickly unlocked and it didn't seem to hurt anything I'm aware of.
Click to expand...
Click to collapse
theres many, many
threads about s-off.
please take a look for them, and also give some more information.
from what you say, you have recovery, at this point I have no idea the hboot you have, or anything or that matter.
so even if I wanted to help you, I can't.
hboot .98 and I didnt get s-off from the start because I couldn't get the downgrade tool to work at all and I searched for a week to find someone having the same issues as I was having with the model I have 6.01.605.05. I did find some people having the same issue when I would run the downgrade it would say failed 43 error and version older then the one I'm currently running. Which I new that. so I unlocked the phone and tried to install clockworkmod 5.0.2.0 using fastboot so I could get root and it would not take it. So I kept looking for a recovery that would work and found 4ext recovery used fastboot and it loaded and I backed up and installed superuser. Being unlocked I installed Aokp in recovery and Gapps and flashed boot.img and rebooted. I found a method to acheive s-off with tacroot and it didnt go very well.
There is a whole thread in general area for downgrading your software version. Start here
http://forum.xda-developers.com/showthread.php?t=1685387