followed some of the guildlines on here about unrooting phone , however it seems no matter what i do S-off will not become S-on, tried the guide to unrooting the automated way, also the Flashing the stock rom way, and the 2.3.4 GB update still stuck with S-off any help would be appreciated
Read saranhai's instructions in this recent thread. Pretty straight-forward and bulletproof.
TeeJay3800 said:
Read saranhai's instructions in this recent thread. Pretty straight-forward and bulletproof.
Click to expand...
Click to collapse
haha thanks TeeJay3800
yea, like i said in the other thread, just follow those instructions and you should be able to get s-on again.
If you have Radio S-OFF, then flashing a stock ROM from RUU or PD15IMG.zip will *not* give you S-ON again. There is already a whole thread about how to get back to S-ON.
cmstlist said:
If you have Radio S-OFF, then flashing a stock ROM from RUU or PD15IMG.zip will *not* give you S-ON again. There is already a whole thread about how to get back to S-ON.
Click to expand...
Click to collapse
Actually it depends on how you turned s-off. IF you use the root.sh version flashing the PD15IMG will turn "s" back on. If you use ./gfree, flashing the PD15IMG will not turn the "s" back on.
I know, I've done it both ways.
neidlinger said:
Actually it depends on how you turned s-off. IF you use the root.sh version flashing the PD15IMG will turn "s" back on. If you use ./gfree, flashing the PD15IMG will not turn the "s" back on.
I know, I've done it both ways.
Click to expand...
Click to collapse
Thank you for the clarification. My understanding is that root.sh does not confer Radio S-OFF but rather fakes it via the ENG HBOOT. Is this a correct assessment?
Ergo if you have true Radio S-OFF (via gfree), then PD15IMG will maintain that S-OFF.
My understanding was that most devs are recommending gfree over root.sh to make things easier to users down the line and reduce the chances of perm-brick. It just means a bit more manual labour.
cmstlist said:
Thank you for the clarification. My understanding is that root.sh does not confer Radio S-OFF but rather fakes it via the ENG HBOOT. Is this a correct assessment?
Ergo if you have true Radio S-OFF (via gfree), then PD15IMG will maintain that S-OFF.
My understanding was that most devs are recommending gfree over root.sh to make things easier to users down the line and reduce the chances of perm-brick. It just means a bit more manual labour.
Click to expand...
Click to collapse
Basically yes. The root.sh is a faux s-off. It works like s-off but not really turning it off. The ./gfree IIRC removes the flags completely. So said person down the road will not have problems.
However with us having two different eMMC chips. The root.sh will turn off the flags for the good eMMC chips, and will not do anything if you have a bad eMMC chip set. While the ./gfree completely removes them. So if you have a good chip or a problematic chip ./gfree will root both.
Now with that being said it's extremely easy for a bad eMMC chipped phone to become bricked. That is why we are seeing so many "Failed-PU" threads popping up. The Partition Update isn't being handled correctly via the eMMC chip, and bricking the device.
all in all use root.sh to root your phone, if that doesn't work use ./gfree with EXTREME caution.
I got a bad eMMC on my Mobilicity Panache, but I decided to take the gamble anyway. So I cautiously went with gfree. Apparently 80% of the "bad" chips will never fail, so... Rolling the dice here.
Anyway to the OP, there's your answer: it depends on how you rooted it.
Sent from my HTC Glacier using Tapatalk
cmstlist said:
I got a bad eMMC on my Mobilicity Panache, but I decided to take the gamble anyway. So I cautiously went with gfree. Apparently 80% of the "bad" chips will never fail, so... Rolling the dice here.
Anyway to the OP, there's your answer: it depends on how you rooted it.
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Hmm guess my old phone was one of the unlucky 20%...
Sent from the HTC Glacier Sense 3.0 using XDA premium app
Related
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.
This has been in progress for a while. If you follow the G2 forums, then you'll know that there have been big problems with G2 phones that have been unlocked via unlock codes, with those unlocked phones then not being able to find a network at all.
It looks like the guys on #G2ROOT have cracked S-OFF for radio. This is *not* the same as the current S-OFF that we have from HBOOT. Apparently it should help to prevent semi-bricking via incorrect flashing of older ROMs.
The article in the Wiki explains all. Documentation about the procedures should be coming soon. We will of course have to make sure it's fine on the DZ too :
http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF
nice gives all those "bricked" g2's hope
Radio S-OFF is permanent S-OFF?
So no more warranty? Damn.
I'll stick to the stock ROM for a while with root, then HBOOT S-OFF, but never radio S-OFF.
I like warranty. Never know when you'll need it.
DanWilson said:
Radio S-OFF is permanent S-OFF?
So no more warranty? Damn.
I'll stick to the stock ROM for a while with root, then HBOOT S-OFF, but never radio S-OFF.
I like warranty. Never know when you'll need it.
Click to expand...
Click to collapse
I imagine it'll still be possible to reverse it. From a scan of the IRC logs (though of course I might have missed important stuff), it looks like you just need to write the correct data to the right area of a partition to get the radio S-OFF. So surely you can un-do that by writing the previous data ?
Documentation on this is now up, see http://forum.xda-developers.com/showthread.php?t=855764
Bear in mind that the instructions are for the G2 right now, so if you try this out on a DZ there's a high chance of a permanent brick ! But hopefully someone will sort out a verified method for the DZ soon
I would not advise people do this form of S-OFF unless they really need to anyway, its harder to come back from (if you did semi-brick) and holds more risks.
Lennyuk said:
I would not advise people do this form of S-OFF unless they really need to anyway, its harder to come back from (if you did semi-brick) and holds more risks.
Click to expand...
Click to collapse
But when an easier way to do it comes along (which is being worked on, I believe), a full S-OFF will be a lot safer, because then it won't be so easy to brick your phone by simply flashing an old RUU.
steviewevie said:
But when an easier way to do it comes along (which is being worked on, I believe), a full S-OFF will be a lot safer, because then it won't be so easy to brick your phone by simply flashing an old RUU.
Click to expand...
Click to collapse
people should not be flashing an old RUU anyway!
anyone who is silly enough to do that gets a brick for a reason.
Always either flash the latest ruu, or restore a nandroid of stock and flash an ota it offers, these are the safest ways.
You will get more bricks from people doing radio s-off than the s-off + ruu method gives.
Lennyuk said:
I would not advise people do this form of S-OFF unless they really need to anyway, its harder to come back from (if you did semi-brick) and holds more risks.
Click to expand...
Click to collapse
You're an ass-talker. You talk through your ass, blow hot air, and have no idea what you're talking about.
1) it is SAFER,
2) it is EASIER to come back from,
3) it is SAFER.
Why is it safer? Because it does NOT require writing the hboot or radio! You can blow p7 out and android will still boot, which means that you have the opportunity to fix it if something goes wrong.
A bad flash of the radio or hboot and you're dead.
For those who might not have seen it yet, there's now a fully documented procedure on how to do this to your DZ (and yes, it's been tested on the DZ too).
As has been said, this is a safer method to get S-OFF (letting you flash custom ROMs) than the previous method of putting on an engineering hboot.
See http://forum.xda-developers.com/showthread.php?t=857390
DanWilson said:
Radio S-OFF is permanent S-OFF?
So no more warranty? Damn.
I'll stick to the stock ROM for a while with root, then HBOOT S-OFF, but never radio S-OFF.
I like warranty. Never know when you'll need it.
Click to expand...
Click to collapse
all i do for warrenty with modded phones is feed 12-20 volts ( from a wall adapter) into the battery contacts and tost the main board and bring it back as dead they send me a new one no questions asked cause the phone is dead...even did this with a htc ppc6800 that i smashed the screen in and thay warrenteyed it no prob....this is on bell in canada....
666
I was following your discussion on bricking because of flashing ruus but for some reason it doesn't apply to me. I had an Asian WWE 1.34.707.5 (shipped with my phone) then I flashed it with Asian WWE 1.34.707.3 RUU and it didn't brick my phone.
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
Previously, when I flashed the Stock GB update by putting the PD15IMG.zip on the root of the SD card etc. the phone would return to Stock GB with S=ON
I later downgraded to re-root and turn S=OFF, but I am now giving my phone to another user and wanted to restore to stock. Since it is so easy to run the GB update and have it automatically turn S=ON, I figured I'd do it that way.
However, for some reason, when I ran the update from PD15IMG.zip it did not turn S back on.
So now I'm stuck with an unrooted, stock GB phone and S=OFF.
I can of course go through the whole downgrade again, and reverse gfree (yes I kept the file to revert back) and then re-update to Stock GB, but I am wondering why in the world it did not just turn S=ON like it did before?
Did it remove the eng bootloader?
$pitacular1 said:
...but I am wondering why in the world it did not just turn S=ON like it did before?
Click to expand...
Click to collapse
because when you ./gfree completely removes the security flags. Where as the root.sh just turns them off. By reverting the ./gfree method you are replacing them.
DistrictDigital said:
Did it remove the eng bootloader?
Click to expand...
Click to collapse
Should've, since the update reflashes everything.
Sent from my HTC Glacier using xda premium
neidlinger said:
because when you ./gfree completely removes the security flags. Where as the root.sh just turns them off. By reverting the ./gfree method you are replacing them.
Click to expand...
Click to collapse
Then why did it work twice on two different phones? I always use gfree to get S=OFF when I permaroot, and twice previously restored the phones to stock & S=ON by flashing the "official" GB update.
Used the same file, same techniques.. different results.
I'm actually wondering if someone isn't playing around with their ROMs.. or apps.. and rewriting system files for questionable reasons.
I'm fairly consistent with what I do on my phone(s), and I did notice some interesting things after rooting, turning S=OFF and trying two different GB ROMs on my latest MT4G
I think I'm going to piece apart these two ROMs and look for anything that shouldn't be there. Which means, I'm going to be busy figuring all of that out. But I've been meaning to get into Android at a deeper level anyway, so I guess here we go!
DistrictDigital said:
Did it remove the eng bootloader?
Click to expand...
Click to collapse
yes it did....
I have followed this guide http://forum.xda-developers.com/showthread.php?p=25372466&highlight=s-off+still#post25372466 to the roots of it and i still cant get s-on! Any one willing to help?! after i do the last step it still says s-off but this time with 85.000 hboot! do i have to flash the PD15IMG so i can have s-on after that last step?!
OKAY! i did the type ./gfee --secu_flag on" now if i redo the PD15IMG will i have s-on?!!?!?!
Did you restore the part7backup?
Sent from my HTC Glacier using XDA
Part7backup doesn't matter much. If gfree was run and pd15img will be flashed after it, S-ON will be restored.
Jack_R1 said:
Part7backup doesn't matter much. If gfree was run and pd15img will be flashed after it, S-ON will be restored.
Click to expand...
Click to collapse
So what's his problem then? I'm not being sarcastic. If he got S-OFF with gfree and used gfree to turn the security flag back on, then...?
With Eng HBOOT the security flag isn't being checked - so he sees S-OFF even though the flag itself might be ON. PD15IMG with stock bootloader will revert his HBOOT to stock, which will reflect the actual flag status.
You guys were great help but I tried everything on what you guys showed me. But nothing seemed to work.. I sent the phone back unrooted but the flag still said s-off even without the eng boatloader... They sent me a replacement mt4g and it had the same issue with the screen being washed off. I talked with them (someone hung up on me twice, pissed me off) and they decoded to send me the sensation 4g. I am now going to be here and there trying to port good roms for you guys to enjoy on the mt4g! By the way, sense 3.6 on HTC isn't that different. Don't get too excited about it folks... Well thanks a lot for you're help ladies and gentlemen! Gcashiel singing off.
Ps. Pm Me if you like any sensation roms for me to port over!