Develop Bugs

[Q] unrevoked root with s-on

I just rooted my HTC Desire using unrEVOked 3.21. Everything was fine. I had superuser permission and so on.
Than i had a sudden reboots. After reboot the N1 gallery crashed. N1 gallery might have cause the reboots. So i remove it and everything is fine till now.
I wanted to load a custom rom. I boot in to bootloader and notice that its s-on.
My question is can I load custom roms with s-on. How come I'm s-on and I have root access. If everything is fine, than what does this s-on do. I'm new at all this, so please bare with me.
Thank you.

harvin23 said:
I just rooted my HTC Desire using unrEVOked 3.21. Everything was fine. I had superuser permission and so on.
Than i had a sudden reboots. After reboot the N1 gallery crashed. N1 gallery might have cause the reboots. So i remove it and everything is fine till now.
I wanted to load a custom rom. I boot in to bootloader and notice that its s-on.
My question is can I load custom roms with s-on. How come I'm s-on and I have root access. If everything is fine, than what does this s-on do. I'm new at all this, so please bare with me.
Thank you.
Click to expand...
Click to collapse
S-Off = Full root ( Not really necessary unless you want to write to system and stuff while in Android. you can also change your splash screen if you would like)
S-On with root by unrevoked = Flash custom roms, radios, kernels, etc..
S-On is Sercurity On which means that the System files are only Read-Only.
S-Off uses AlphaRev's Hboot as this removes S-On. Its the Only way to get S-Off. I just S-Offed myself yesterday. It was scary at first but i really think its a good thing as you can use Metamorph/NinjaMorph or stuff.
I'd recommend just keep this information and when you get used to clockworkmod recovery then S-Off.
Remember that to get into recovery you must boot into Bootloader then scroll to Recovery with the volume up and down buttons then press the power down.
Oh, and to scroll between the clockworkmod menu, just use the trackpad. I also would not ecommend using Rom Manager as i remember the first time i used it and booted into recovery i was scqred to death as it brought me to a attention thing. I was scared to death.
Have Fun

shockem said:
S-Off = Full root ( Not really necessary unless you want to write to system and stuff while in Android. you can also change your splash screen if you would like)
S-On with root by unrevoked = Flash custom roms, radios, kernels, etc..
S-On is Sercurity On which means that the System files are only Read-Only.
S-Off uses AlphaRev's Hboot as this removes S-On. Its the Only way to get S-Off. I just S-Offed myself yesterday. It was scary at first but i really think its a good thing as you can use Metamorph/NinjaMorph or stuff.
I'd recommend just keep this information and when you get used to clockworkmod recovery then S-Off.
Remember that to get into recovery you must boot into Bootloader then scroll to Recovery with the volume up and down buttons then press the power down.
Oh, and to scroll between the clockworkmod menu, just use the trackpad. I also would not ecommend using Rom Manager as i remember the first time i used it and booted into recovery i was scqred to death as it brought me to a attention thing. I was scared to death.
Have Fun
Click to expand...
Click to collapse
Thank you so much.. That was really usefull information bro... you mention that my system files are read only with unrEVOked... yday i used root explorer to change some system files... could that be the cause my device rebooted...
another thing i want to know is that i want to install busybox.. do i need s-off to do this... if i ever hard/soft reset will the busybox also be removed...
and i also removed some stock applications... will they also be reinstalled if i reset my HTC desire...

You dont need S-OFF to install busybox. Dont worry about S-OFF. Most power users dont need it. It's more a liability.
Stock apps may be reinstalled with choosing to install a ROM which includes them. Most ROMS have addon files with stock apps. Or you may choose and pick from a ROM Kitchen.

harvin23 said:
Thank you so much.. That was really usefull information bro... you mention that my system files are read only with unrEVOked... yday i used root explorer to change some system files... could that be the cause my device rebooted...
another thing i want to know is that i want to install busybox.. do i need s-off to do this... if i ever hard/soft reset will the busybox also be removed...
and i also removed some stock applications... will they also be reinstalled if i reset my HTC desire...
Click to expand...
Click to collapse
No problem Last time when i rooted without S-Off, i tried copying things around the system folders and it never worked. That might and should have been the cause of your reboots. The rest of it has been answered by Droidzone

thanks guys for all the information... i just download a new custom rom and was going to flash it... but there is something bothering me... its the radio... the custom rom has different radio... will the radio change once i install the custom... is there any complications...
what is the things i need to consider before flashing a rom... im really sorry guys but this phone cost RM2000 (Malaysian Ringgit)... i dont want screw it... just taking precautions...
thanks for all the help guys...

harvin23 said:
thanks guys for all the information... i just download a new custom rom and was going to flash it... but there is something bothering me... its the radio... the custom rom has different radio... will the radio change once i install the custom... is there any complications...
what is the things i need to consider before flashing a rom... im really sorry guys but this phone cost RM2000 (Malaysian Ringgit)... i dont want screw it... just taking precautions...
thanks for all the help guys...
Click to expand...
Click to collapse
Flashing a ROM is not a big deal. If something happens to go wrong, you can always revert to the Nandroid restore. Custom ROMs often come with different Radios. Just install whichever Radio the developer recommends, and it should go smoothly.
At times a ROM may have different Radios for different functions. Like, if you want the phone running faster, use one radio. If you want more battery life, use another and so on.
If you've already rooted, flashing a new ROM wont create any more trouble than you're already in. Just dont be that hasty to do S-OFF. It's S-OFF that often leads to softbricks (usually).

droidzone said:
Flashing a ROM is not a big deal. If something happens to go wrong, you can always revert to the Nandroid restore. Custom ROMs often come with different Radios. Just install whichever Radio the developer recommends, and it should go smoothly.
At times a ROM may have different Radios for different functions. Like, if you want the phone running faster, use one radio. If you want more battery life, use another and so on.
If you've already rooted, flashing a new ROM wont create any more trouble than you're already in. Just dont be that hasty to do S-OFF. It's S-OFF that often leads to softbricks (usually).
Click to expand...
Click to collapse
^^
but ussually i dont really do nandroid restore's because i keep lots of Roms for backup in case one does go wrong. Its best to do both

[Q] need help installing gingerbread keyboard

i have installed the gingerbread keyboard file on my sd card and have rooted my phone using the visonary method but now i cant seem to get into recovery mode. I have rom manager installed and have flashed clockwork recovery mode. it said that it had sucsessfully installed.
I then flashed it again as i read somewhere that i might need to do it twice as sometimes it dosent work.
when i now click on the recovery option in rom manager all i get is the red triange with the ! in the middle.
any ideas what im doing wrong?
Have tried reading the threads but with 30 plus pages i am now completley confused

Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?

steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this

just done the hboot hing and at the top of screen it says
vision pvt ship s-on

hpsauce37 said:
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
Click to expand...
Click to collapse
It's a bit confusing because there is more than one way to do this. But by far the safest way is to follow the guide at http://forum.xda-developers.com/showthread.php?t=857390
Have a good read, then if you're not sure, ask questions in that thread on the process.

steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Sent from my EVO using Tapatalk Pro

rwcj63 said:
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Click to expand...
Click to collapse
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?

steviewevie said:
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
Click to expand...
Click to collapse
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Sent from my EVO using Tapatalk Pro

rwcj63 said:
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Click to expand...
Click to collapse
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.

steviewevie said:
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
Click to expand...
Click to collapse
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro

rwcj63 said:
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
Click to expand...
Click to collapse
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.

im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems

hpsauce37 said:
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
Click to expand...
Click to collapse
Have you tried my guide on adb ? http://forum.xda-developers.com/showthread.php?t=865685

OK, I can use some help too
I have a DZ with stock ROM, root and s-off and CWR.
In my enthusiasm that I knew how to flash rom updates with clockwork (I am running the Godspeed 1Ghz) I downloaded the Gingerbread keyboard rom update from the G2 forum. I think I jumped off a bit too fast...
And now I am stuck in an infinite boot loop. I can get into Clockwork recovery but it just loops the "HTC Quietly Brilliant" forever including the annoying boot sound...
I tried some suggestions to download and reflash a second time, no effect.
I tried to mount /system before flashing, no effect.
Am I forced to go back to factory now?
Also, I found 2 gingerbread keyboards, one in the G2 forum and one over here.
Anyone know what the difference is? They have a different filesize..
Any help is welcome...
*edit*
OK so now I read that it is only to be flashed on a non-stock ROM... so I am now flashing Cyanogen 6.1

try wiping all the caches...

Lennyuk said:
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
Click to expand...
Click to collapse
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Sent from my EVO using Tapatalk Pro

rwcj63 said:
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Click to expand...
Click to collapse
S'alright.
HTC really ramped up the security on these new phones, as Lenny said, with this hardware write-protection on certain partitions. But even given that, I was amazed by just how quickly the guys on the #G2ROOT IRC channel, especially Scotty2, managed to crack it !
It also looks like they've opened the phone even wider than many others before, with the "true" radio S-OFF that they achieved.
You can read up all about it in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision

[WARNING] Do not flash a new official RUU/ROM/OTA if you have root and/or S-OFF

DO NOT FLASH A NEW RUU OR OFFICIAL ROM IMAGE UNLESS YOU *REALLY* KNOW WHAT YOU ARE DOING !
Sorry for shouting, but this is very important. Thanks to the mods for making this sticky.
The latest official RUU that has been released - http://forum.xda-developers.com/showthread.php?t=870369 - has been found to break the existing methods of rooting and getting full S-OFF.
This shouldn't be a big suprise, because when HTC saw that the amazing devs on XDA had cracked the existing security, we should expect them to put something even tougher in later releases.
So flashing any later release, whether that's an official RUU or just the ROM image (PC10IMG.zip) is a very dangerous thing to do until it has been fully tested and "cleared" by the devs here. i.e. your previously rooted and S-OFF'd phone might lose root and go back to S-ON, and be unable to be rooted and S-OFF'd again.
It's of course fine if your phone came with a particular ROM release to flash that *exact same* release back onto the phone if you want to return to stock. What I'm referring to is flashing a brand new release that isn't the one that came with your phone.
It's fine to flash custom ROMs of course, because those have already been tested out. In general, it's probably best to steer very clear of new official releases, and wait till the devs have pulled them apart and put any cool new stuff into a custom ROM. Then you know it'll be safe to flash.
Currently I don't think it's entirely clear what just flashing a new *radio* on its own will do, as opposed to the entire ROM/RUU. That's still being worked on. But steer clear of even that if you're not sure what you're doing or dont' want to take any chances of losing root/S-OFF.
Thanks for reading

Thanks for the heads up.

I flashed the ROM you mentioned.
For those who want to try:
Just remember to get REAL S-OFF using gfree before flashing it.
This provide you a medicine for regret. You can get back to WWE ROM using WWE RUU and root/recover your old ROM.

What is RUU? What is it to do with ROMs? Did HTC provide a change log for newer Radio? Or does anyone know what changes are , in the latest Radio?
Just to be clear. Don’t flame me for this please. I’m still learning just like many others in here.

androidtoy09 said:
What is RUU? What is it to do with ROMs? Did HTC provide a change log for newer Radio? Or does anyone know what changes are , in the latest Radio?
Just to be clear. Don’t flame me for this please. I’m still learning just like many others in here.
Click to expand...
Click to collapse
We don't have a changelog, no.
RUU is ROM Update Utility. It's a program to run on Windows (.exe) which flashes your new ROM for you, and holds your hand through the process. It's possible to extract just the ROM zip file from the exe so you can flash it yourself if you want.
The thing about the RUU and stock ROMs is that they will flash pretty much *everything* on your phone. So as well as a new system partition (the main stuff for Android), you'll probably get a new hboot, new radio, new recovery. Those *might* all have increased security which is a lot more difficult to crack. So generally you should not flash it until we know it's "safe" to do so, i.e. it can be re-rooted and S-OFF'd etc.

steviewevie said:
We don't have a changelog, no.
RUU is ROM Update Utility. It's a program to run on Windows (.exe) which flashes your new ROM for you, and holds your hand through the process. It's possible to extract just the ROM zip file from the exe so you can flash it yourself if you want.
The thing about the RUU and stock ROMs is that they will flash pretty much *everything* on your phone. So as well as a new system partition (the main stuff for Android), you'll probably get a new hboot, new radio, new recovery. Those *might* all have increased security which is a lot more difficult to crack. So generally you should not flash it until we know it's "safe" to do so, i.e. it can be re-rooted and S-OFF'd etc.
Click to expand...
Click to collapse
Ok, thanks for clearing it up. So, RUU is pretty much similar to the method RIM uses to flash its OS on the Blackberries.

Im a little confused here.. So just to clear some things up i hope someone will answer these questions i have.
I have the software on my Desire Z that it came with (1.34.405.5), which i've rooted, S-off'ed and installed another kernel for OC porpuses. This is working fine, but lets say that i wanted to try another rom .. After some time i decide to go back to the stock software and then update to the newest software, would that be a problem? And has HTC released some newer software than the one iam using?

If you flashed back to stock, that would be fine. But if you flashed a new official update (e.g OTA), then you run the risk of installing something that you can't root/S-OFF.
It is best to steer clear of any official upgrades until they've been checked by the devs here and been given the all-clear.
Given that the phone came with certain areas write-protected, and the devs managed to crack that, we should be expecting HTC to release an even more secure update.
Yes, there is a new ROM out, at the moment for Egypt, that seems to have increased security. It would not be a suprise if HTC rolled out similar security as an OTA update for all existing ROMs. Right now there is something in that Egypt ROM (probably the hboot, at the minimum) which mean existing permanent root and S-OFF methods fail. It may be this is easily cracked again, or maybe it will take some time, who knows.
Bottom line - don't apply any official updates to your phone if it is rooted/S-OFF or you plan to root/S-OFF.
Sent from my HTC Desire Z

perm-rooted g2 stock tmobile rom s-off
ok, my question is....i perm-rooted my g2 and have s-off, does this mean that i cant except the new gingerbread OTA update? ive had my fill of flashing roms with my old windows phone.. att tilt, tmobile touch pro 2, and tmobile hd2. im not looking to flash my g2 with a new rom...no offense to the chefs. love there work. but i only rooted the g2 to get rid of the bs apps that tmobile and google added to the phone. and i thought i heard that wen u root the phone tmobile cant tell wen u tether, so there for no more throttle b/s but thats not true...i must have miss read. but i would like to stay w/the stock rom and still b able to install the Gingerbread OTA. please someone provide an answer for me or point me in the right direction. thank you in advance.... sorry if the answer is already provided somewhere and i over looked it, i tend to do that a lot.

blitz69 said:
ok, my question is....i perm-rooted my g2 and have s-off, does this mean that i cant except the new gingerbread OTA update? ive had my fill of flashing roms with my old windows phone.. att tilt, tmobile touch pro 2, and tmobile hd2. im not looking to flash my g2 with a new rom...no offense to the chefs. love there work. but i only rooted the g2 to get rid of the bs apps that tmobile and google added to the phone. and i thought i heard that wen u root the phone tmobile cant tell wen u tether, so there for no more throttle b/s but thats not true...i must have miss read. but i would like to stay w/the stock rom and still b able to install the Gingerbread OTA. please someone provide an answer for me or point me in the right direction. thank you in advance.... sorry if the answer is already provided somewhere and i over looked it, i tend to do that a lot.
Click to expand...
Click to collapse
The trouble is, HTC/T-Mobile don't want you to root and/or S-OFF your phone, because it's a lot easier to end up bricking the phone if you don't know what you're doing. They put greatly increased security on the G2/DZ/DHD when they came out, in order to help prevent this.
Now this security has been cracked, we can expect HTC/T-Mobile to try and increase security even further (e.g. closing loopholes that let our current methods of root/S-OFF work) in future updates.
So if you accept any future OTA, you run a high risk of accepting something that will lock you out of root and S-OFF, at least temporarily, and possibly permanently (depending on how good a solution they come up with).
If you are not bothered about root/S-OFF, then that's fine of course.
This doesn't mean that you necessarily have to switch to a custom ROM to get updates though. If you stay with the stock ROM (and I'm still on a stock ROM too right now), then just do not accept the update when an OTA comes out, and keep checking these forums to see when the devs say that they can root/S-OFF with the new version. When they say it's ok then you know you can apply the update and still get root/S-OFF.
This already happened with the G2. Very soon after release, but after rooting had been achieved, there was an OTA. Most people here decided to wait until the OTA had been looked at, and sure enough there was a small adjustment needed to the rooting method. But of course this OTA was before HTC had a chance to respond to the cracking of the security, so as I said, any future updates may well require a lot more time and effort from the devs to investigate and crack again.

Ok. Thank you very much

Will this muff up my phone if I factory reset it by using the Power+Volume Down option?

Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!

Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
What do you mean with gfree?
Is my waranty broken When i execute radio s-off?
Is it possible to make it radio s-on?

Yes,warranty is broken,but with the new gfree method
you can go back to S-ON:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2

ericjosepi said:
Will this muff up my phone if I factory reset it by using the Power+Volume Down option?
Click to expand...
Click to collapse
If you do a factory reset then I think you'll lose root, but you can get it back again easily enough. The issue for this thread is flashing new updated stuff from HTC etc.

Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
You might still need that backup, e.g. if you don't know what your old CID was and you want to un-do that bit too. I would keep it.
Sorry I don't think I understand your last question though, or why you say the uberroot method (I'm personally not keen on that name, it's just the usual method using Visionary/rage with gfree, not a new method) doesn't work.

Ok,so I can go back to S-ON with gfree commands from here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
If you are only interested in permanent root you only need radio S-OFF and then it is sufficient to use
# ./gfree -s off
instead of
# ./gfree -f
in the following commands.
And gfree can now also be used to set radio S-ON by using the "-s on" option and to change the CID back to the original value be using i.e. "-c T-MOB010" if you want or have to go back.
Click to expand...
Click to collapse
But for CID (you mean SuperCid right?) I need the backup?
And with the last question which you don`t understand,I mean
with flashing the HTC RUU 1.34.405.5 I don`t go back to S-ON
and original CID whether I use UBERROT method or this from here:
(Rooting the Vision (G2/DZ) and DHD)
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2

Thanks for the advice, I will stick myself with the current rom for a while

Ganii said:
Ok,so I can go back to S-ON with gfree commands from here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
But for CID (you mean SuperCid right?) I need the backup?
Click to expand...
Click to collapse
Yes, I mean to go from your SuperCID back to your regular CID. You might not know what your original CID was.
And with the last question which you don`t understand,I mean
with flashing the HTC RUU 1.34.405.5 I don`t go back to S-ON
and original CID whether I use UBERROT method or this from here:
(Rooting the Vision (G2/DZ) and DHD)
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Click to expand...
Click to collapse
Yes, if you flash a stock ROM then it won't affect your S-OFF and CID status (or SIM unlock). These are stored in your radio configuration partition, and not in any of the partitions which are overwritten by the ROM flash.

Can't s-off alpharev

Hi guys I'm trying to s-off using alpharev ISO disc...it goes through the process then after rebooting stage 3 I get 4 lines that say unary operator expected ... I shut down pc and phone boots as usual...
I'm running rxmix s v1.1

maybe change to stock ROM and try s-off again

Yes like the post above switch to a ROOTED stock froyo rom worked for me, the reason your getting errors is because the rom you are running has probably got data2whatever, data++ ect... this affects the alpha rev process.

Ditto above. Alpharev doesn't work on a2sd or similar ROMs... Look back a couple pages and you'll see I started a thread with the same issue. I'm on IC GB a2sd+...
Once pc is repaired, I plan to load stock Telstra RUU and try again, then re-root...

bailz2506 said:
Hi guys I'm trying to s-off using alpharev ISO disc...it goes through the process then after rebooting stage 3 I get 4 lines that say unary operator expected ... I shut down pc and phone boots as usual...
I'm running rxmix s v1.1
Click to expand...
Click to collapse
First, you better use USB stick instead of a disc, it is faster a more reliable.
Secondly, you won't be able to get s-off unless you flash either stock rom or AOSP rom ( oxygen worked for me without any problems).

mikeraul said:
First, you better use USB stick instead of a disc, it is faster a more reliable.
Secondly, you won't be able to get s-off unless you flash either stock rom or AOSP rom ( oxygen worked for me without any problems).
Click to expand...
Click to collapse
+1, I s-off my phone with oxygen running on it.

ThaNx everyone for the help will try it that way and let you all no if it worked
Sent from my HTC Desire using XDA App

thanks everyone for the help it worked fine now i have fully rooted and s-offed htc desire...now to get back into the flashing fun.
When the moderator reads this i have no problems if this thread is deleted thanks again

bailz2506 said:
thanks everyone for the help it worked fine now i have fully rooted and s-offed htc desire...now to get back into the flashing fun.
When the moderator reads this i have no problems if this thread is deleted thanks again
Click to expand...
Click to collapse
Happy to hear

Hi folks. Writing this without any hope that someone is online at the moment.
I'm currently using alpharev to flash HBOOT on my htc desire. It has stucked on step 3 with two lines on phone's screen:
Aplharev SPLBOOT version 2.0
...
Normal NAND detected. Non-PVT4
and keeps hanging like that nearly an hour already.
The phone is rooted, with Clockworkmod recovery and InserCoin 2.0.1 DATA2EXT ROM installed.
Did anybody have the same behaviour while flashing HBOOT?
Should I be patient and wait for some miracle to happen?
thanks in advance.

Are you S-Off already??

use the new S-OFF utility. It's a lot quicker and easier. Just make sure you uninstall HTC Sync, or at least make sure it isn't running.

777ace said:
Are you S-Off already??
Click to expand...
Click to collapse
no...
just saw here an advice to wait for a long term and the to pull out the battery and reboot.
did as he said.
device is rebooting in fastboot mode...
will try to restore previous ROM from recovery mode...

n0vice said:
no...
just saw here an advice to wait for a long term and the to pull out the battery and reboot.
did as he said.
device is rebooting in fastboot mode...
will try to restore previous ROM from recovery mode...
Click to expand...
Click to collapse
try it with the new utility.. it should work for you..

finally I've restored my previous ROM (and sh*tted a pile of bricks during this hour).
HBOOT screen says that my device is still S-ON. strange... maybe that's because of 'DATA2EXT' ROM onboard.
bortak said:
use the new "...revolutionary.io/" S-OFF utility. It's a lot quicker and easier. Just make sure you uninstall HTC Sync, or at least make sure it isn't running.
Click to expand...
Click to collapse
thanks. I'll try it when my hands will stop shaking

You won't be able to alter HBoot without S-Off...
I am not sure how the new Utility that bortak linked to works, but I know that the "old" alpharev will not S-Off if you are using A2SD/D2SD/D2EXT type ROMs. You will need to flash stock RUU (do not use latest GB update RUU!!!), or one of the AOSP ROMs, such as Oxygen, before proceeding.
Once you have S-Off, you can go back and re-root, then upgrade your HBoot etc.

777ace said:
You won't be able to alter HBoot without S-Off...
I am not sure how the new Utility that bortak linked to works, but I know that the "old" alpharev will not S-Off if you are using A2SD/D2SD/D2EXT type ROMs. You will need to flash stock RUU (do not use latest GB update RUU!!!), or one of the AOSP ROMs, such as Oxygen, before proceeding.
Once you have S-Off, you can go back and re-root, then upgrade your HBoot etc.
Click to expand...
Click to collapse
thanks. I'll follow your advice.
I'm still wondering, why TUT-makers didn't mention this A2SD/D2SD/D2EXT ROMs inconsistency.
I think this should be written in large letters on the first line for noobs like me

Lol, you're right on that!!
If you look on alpharev site, it is mentioned in the text, but VERY small!
Requirements:
The only requirement right now is that the ROM you're running is rooted.
As techniques such as 'data2ext' have been popping up, these might disturb our finely-tuned flashing process.
Please revert to a rooted stock ROM if possible. Your /data partition is used for temporary storage of important files.
Click to expand...
Click to collapse
I missed it the first time also, had lots of dramas, and finally spotted that note after many frustrating hours. It should have been written in bright red, 72 cap at the top of screen!!

You need to use an a2sd Rom like lee Droid 2.5.
Alpha rev state this at start of web page using data2sd can cause problems.
Flash lee Droid 2.5 and try it again, you should be fine
Kind regards
John
Sent from my HTC Desire using XDA Premium App

It is being said on Alpharev website under "requirements".
Though I agree it should be said in tutorials too.
n0vice said:
thanks. I'll follow your advice.
I'm still wondering, why TUT-makers didn't mention this A2SD/D2SD/D2EXT ROMs inconsistency.
I think this should be written in large letters on the first line for noobs like me
Click to expand...
Click to collapse
Sent from my HTC Desire using XDA App

[Q] Trouble achieving S-Off

Howdy! Lemme preface all of this by saying that I'm less than a noob here....really inexperienced. Here's the background......
I rooted my DInc and I can't even remember which unrevoked tool I used. I was just reading along and punching commands and when the process was done I was rooted. I installed CWM successfully and flashed to CM7.2 which I've been running for quite some time. Lately I got an itch to try a JB ROM like infected, so when I looked into it, it clearly says I need S-off to accomplish that flash so I checked and realized I was S-on still.
At this point, I added the unrevoked-forever.zip to my sdcard root and tried to flash that ZIP by way CWM and i get these error messages:
E: unsupported radio version
E: update failed. Check/sdcard/soff.log
E: error in /sdcard/unrevoked-forever.zip (Status 42)
I am running Android version 2.3.7 and radio baseband version 2.15.10.12.20
Is this one of those things that I shouldn't be trying from CM7.2 and I should've dealt with before my initial flash to CM7.2?? Basically I'm totally freakin lost and in WAAAAY over my element, so any guidance would be duly appreciated. Thanks in advance!
Scott

Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.

PonsAsinorem said:
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
Click to expand...
Click to collapse
Sorry....i guess it pays to be extra thorough in the description of the problem. The link you left me is the one that I followed. I researched achieving S-Off on the DInc first and found this same page in my research. I followed the process and all went smooth right up until i started to flash the unrevoked-forever.zip from my sdcard via CWM. The aforementioned error messages came up on my phone and it said the process failed.
I thought it might be because the radio baseband versions that are list as "supported" do not match mine

smvogel73 said:
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
Click to expand...
Click to collapse
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.

PonsAsinorem said:
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
Click to expand...
Click to collapse
Yes thx....I'm gathering that! So this is where terminology gets so dang confusing for me. I didn't think unlocking my bootloader meant the same thing as achieving S-Off?? I already thought my bootloader was unlcoked, as I was able to flash CM7.2, which I didnt think I would be able to do if I had a locked bootloader. So wicked confused!!! And try as I miught to educate myself in these forums, I haven't located a sticky or guide that really thoroughly explains all the vernacular regarding android dev/modding/rooting/flashing/etc
So this other method will work with any radio baseband version then?? Or is it important to check compatibility there too??

What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON

PonsAsinorem said:
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
Click to expand...
Click to collapse
It says "UNLOCKED" and below that it says "S-ON
Thank u for the materials too!

So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run. I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.
The ROM I'm looking to flash is Infection JB 4.2.2. The instructions say that if you're coming from. A non-AOSP ROM and are S-On that you've gotta extract boot.img and fastboot it after the ROM flash......whatever the heck that means???

smvogel73 said:
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run.???
Click to expand...
Click to collapse
Correct. Staying S-ON minimizes the danger. It locks your radio, and HBOOT, which are the main dangers.
smvogel73 said:
I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.???
Click to expand...
Click to collapse
Not really ROM flashing, but radio and HBOOT flashing, which is what unrevoked-forever tweaks.
I'd try to flash it one more time. When you do, what, if anything, are you wiping? You should be doing a factory reset, system, and boot wipe/format, then flash the ROM.
If that doesn't work (it might not, it's been awhile since I've worked with S-ON devices), then we'll move on to S-OFF (if you want).

Oh no.....I didn't even attempt to flash the Infection JB ROM specifically because I was not able to achieve S-Off. Whether it was intended or not, yea.....u sufficiently scared me about bricking the phone if I'm not to spec per the developer.
Are u saying I should wipe and then try to flash this ROM despite still being S-On?

Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.

PonsAsinorem said:
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
Click to expand...
Click to collapse
Well there you have it....I will trust your wisdom (as it is far supperior to my own) and I shall flash this ROM tonight!! I already have a nandroid backup of CM7.2 that Im running, as well as a Titanium backup of all my user apps/files.
Sincerest thanks for all your help!!

Hello. Im no expert but i think Cyanogenmod is aosp so you should be good.
I was where you were 2 yrs ago when I rooted my 1st phone: a friends froyo Dinc (ahhh...froyo). A few months ago I aquired my own and went to research how to root GB and everything has changed and is now vastly more complicated. Also I think every phone has a locked bootloader but not encrypted and I think Soff is extra security since I've only encountered it on htc phones. Anyway I've managed to get my inc to Soff but its still locked, idk how lol
Sent from my ADR6300 using Tapatalk 2