[Q] Undo old permaroot & S-OFF from pre-gfree, or update to new S-OFF? - G2 and Desire Z Q&A, Help & Troubleshooting

Hi guys,
I've been reading through the forums over the past two days but I have to admit it's hard to find what I am looking for now that the G2 forum and the DZ forum are merged, and the search isn't getting me anywhere for this one.
I have Bell Canada Desire Z permarooted and S-OFF'd, with CWMod. I did this before the newer gfree method and from what I can gather this can lead me to some kind of endless loop if I try to flash back to the a Bell RUU or other RUUs for that matter. It also worries me that I can't try new radios, etc.
I am getting very poor battery life compared to others so I want to have my phone replaced. I have an extended warranty from FutureShop so I probably don't even need to reset the phone to stock again (they swap on the spot) but I would like to anyway. It will also allow me to test the battery again with the stock ROM.
So, how do I go about flashing back to the Bell ROM and turning S-ON, and unrooting? Keeping in mind that I used the pre-gfree method. I believe it was Visionary R12 and gtab's guide.
Also as the title implies, I was wondering if it's possible to use the new (better) S-OFF even if I am already S-OFF'd the old way?
Any help is appreciated!

You can use gfree and achieve "real" S-OFF without having to unroot.
Just run it. Worst that'll happen is it fails if you happen to be on a kernel it doesn't like. If this happens, no harm is done, just a reboot.

Just run gfree from where you are, as the previous poster said.
That will put you in a much safer position, where you can get stuck in that boot loop that you can if you've only got the eng hboot.
Then you can flash whichever ROM you want. Then you can undo gfree if you want via its new options (see the Wiki).
Regarding your point about the merger, IMHO this issue isn't anything to do with the DZ specifically, and lots of users are posting about similar stuff with their G2s. It's all the same

Thanks guys,
I've done gfree (which is MUCH easier than the thread and wiki make it look - they need to simplify the text, it's overwhelming to look at given how simple the procedure is) and flashed the Bell RUU.
Now I am just about to root, and use gfree to undo the S-OFF I guess?
Will let you know how that turns out. Thanks again!

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
I'd keep that backup file as it is a dump of your original partition 7 before gfree mods it. You can dd i back and put everything back to how it was, if you ever need to. Do you need to keep it on the phone? No.. store it somewhere on your PC.
With the old "fake" S-OFF you would get stuck if you flashed a stock rom because it would overwrite the engineering HBOOT which was the only thing making your phone think it had S-OFF. With gfree method, you have real S-OFF, so this should be fine.
See http://forum.xda-developers.com/showthread.php?t=838484 for details.
tl;dr You should be fine.

Hm,little bit confused!
The backup I need to get original original partition 7
but not to get S-On.
To get S-On I can use the new gfree method,it`s now
possible with this!
I did the old UBERROOT method with real S-Off!
P.S.I read here about this:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2

Not 100% sure I understand the question...but:
You don't need that backup file. If you delete it nothing bad will happen. Paranoid people (like me) would copy it to a safe place, but there's no real need.
You can flash whatever roms you like, including stock ones, as long as you have real, radio (gfree) S-OFF.

Hi guys, thanks for the help! I got it all settled, it was easy.
As I mentioned above, I used gfree to do a true S-OFF, which was easy.
Then I ran Bell's RUU and it worked without any issues. I assume the RUU install also flashes the HTC recovery back to the phone, I didn't check but it must..
A little summary for anyone who needs help in the future..
If you rooted/S-OFF'd using a method older than the current rage/gfree method (the one in the wiki) then you need to redo the S-OFF using gfree.
Steps:
Use gfree -f to S-OFF again
Run the stock RUU file on your pc (you need HTC sync installed for this)
Temproot (first part of the wiki guide) the stock ROM
Use gfree -s on to S-ON your phone
Reboot, and everything should appear like stock (aside from still being sim-unlocked).

Were u sucessful in returning your phone to htc after u did the above?

I didn't have to return it to htc, just to future shop, and it was fine.
Sent from my GT-I9000 using XDA App

Related

[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.

[Q] Restoring to stock - Desire Z

Hey,
I rooted my phone and installed Clockwork mod recovery earlier. I'd like to unroot it, and remove the files from the phone. May send it back due to hinge issue.
I'm not sure where to start. I used the rage/gfree/ADB method on the wiki. I'm on 1.34.
Thanks!
Just re-flash the stock 1.34 ROM/RUU, then get temp root and run gfree with the necessary options to go back to S-ON.
Sent from my HTC Desire Z
Kaph said:
Hey,
I rooted my phone and installed Clockwork mod recovery earlier. I'd like to unroot it, and remove the files from the phone. May send it back due to hinge issue.
I'm not sure where to start. I used the rage/gfree/ADB method on the wiki. I'm on 1.34.
Thanks!
Click to expand...
Click to collapse
You can follow the guide on the wiki http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock but you can skip the "Install the stock image" part because you still have the stock image.
So just start at "radio S-ON and original CID"
Have fun - Guhl
Like Kaph I'm also trying to return to stock, but when I follow the guide on the wiki I get an error.
After I type in gfree -r /sdcard/part7backup.bin and pressing enter I get the following message:
"Error reading input file."
I'd like to try the other method but I don't know my original CID, is there a way to find that out?
I need to return my phone for warranty so help is much appreciated.
Edit: I've already tried reflashing the ROM, I was always running the stock rom without ota and rooted with rage and gfree.
Yeah I've been trying and I keep getting invalid input file.
Also, is there anyway to revert to stock recovery from Clockwork? I think that's hindering things. Unless that's part of the whole process.
Well after some fun I'm back to S-ON with the stock recovery. I'll try applying the OTA now.
But just a massive thanks to djfoo000 and this thread: http://forum.xda-developers.com/showthread.php?t=909755 as I couldn't get the method on the Wiki to work, but doing it in terminal seems to have done the trick and recovery is now showing S-ON. I also used his recovery.img as the versions matched my phone.
On the bright side I'm now a lot more comfortable with adb/etc heh.
My only other question is will all the gfree files and the like stay on the memory, and if so should I use rm to get rid of them? Or do they get deleted upon reboot?
sorry for what may be a stupid comment but will using the ruu not restore to factory?
The reason i ask is that the wiki has the guide for the tmobile g2 and not desire z?!

How to unroot?

What's up! I'm wondering if someone can help me unroot and put back to 100% stock...
I used the rage/gfree method.
Sent from my HTC Vision using XDA App
http://forum.xda-developers.com/showthread.php?t=835971
That should do the trick.
He doesn't give instructions for gfree, so I'm not sure if this is the correct method.
Sent from my HTC Vision using XDA App
Ah - apologies.
No worries bro, hopefully someone else can help answer this question for me.
Sent from my HTC Vision using XDA App
I typed in unroot G2 in bing search and the unlockr site was second one down, this method worked great for me.
I looked it and read it all.
Since I used gfree to obtain s off and super cid/sim unlock, will it work?
Sent from my T-Mobile G2 using XDA App
mftek said:
I looked it and read it all.
Since I used gfree to obtain s off and super cid/sim unlock, will it work?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I'm not 100% positive on that. I also have a Behold 2 and, it was rooted when I got it.
I had no idea how it was rooted. I used the unlockr site for it too and, it work for it.
To me, the way the instructions are wrote, it sounds like it will work to un-root all methods of the G2 root process.
Hopefully a more experienced person will chime in shortly.
tooter1 said:
I'm not 100% positive on that. I also have a Behold 2 and, it was rooted when I got it.
I had no idea how it was rooted. I used the unlockr site for it too and, it work for it.
To me, the way the instructions are wrote, it sounds like it will work to un-root all methods of the G2 root process.
Hopefully a more experienced person will chime in shortly.
Click to expand...
Click to collapse
No, those guides will technically remove root since they restore the shipping ROM but will leave you with S-OFF (since you used gfree---if you had only used the engineering HBOOT to obtain S-OFF, the guides would have been fine). Did you take a look at the actual Wiki: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock?
ianmcquinn said:
No, those guides will technically remove root since they restore the shipping ROM but will leave you with S-OFF (since you used gfree---if you had only used the engineering HBOOT to obtain S-OFF, the guides would have been fine). Did you take a look at the actual Wiki: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock?
Click to expand...
Click to collapse
When I used the unlockr method, my s-off went s-on.
tooter1 said:
When I used the unlockr method, my s-off went s-on.
Click to expand...
Click to collapse
Did you use gfree to to obtain S-OFF though? If you used the engineering HBOOT to do it, as I said in my post, those guides would work fine as is. Flashing the shipping ROM with the PC10IMG file will replace the engineering HBOOT with the shipping one (which is S-ON). If you use gfree though, you get true radio S-OFF (the engineering HBOOT is a fake one that tricks the phone into thinking you have S-OFF, thus allowing write access to the system). This is done by modifying partition 7 on the phone. Since this partition contains information specific to your phone, it is normally left untouched by a PC10IMG or RUU. This is why if S-OFF is obtained through gfree, simply replacing the HBOOT with a PC10IMG file won't revert you to S-ON.
ianmcquinn said:
Did you use gfree to to obtain S-OFF though? If you used the engineering HBOOT to do it, as I said in my post, those guides would work fine as is. Flashing the shipping ROM with the PC10IMG file will replace the engineering HBOOT with the shipping one (which is S-ON). If you use gfree though, you get true radio S-OFF (the engineering HBOOT is a fake one that tricks the phone into thinking you have S-OFF, thus allowing write access to the system). This is done by modifying partition 7 on the phone. Since this partition contains information specific to your phone, it is normally left untouched by a PC10IMG or RUU. This is why if S-OFF is obtained through gfree, simply replacing the HBOOT with a PC10IMG file won't revert you to S-ON.
Click to expand...
Click to collapse
Worked perfectly for me. I flashed stock rom, installed PC10IMG.zip and then used gfree to turn s-on and remove sim unlock.
Sent from my T-Mobile G2 using XDA App
ianmcquinn said:
Did you use gfree to to obtain S-OFF though? If you used the engineering HBOOT to do it, as I said in my post, those guides would work fine as is. Flashing the shipping ROM with the PC10IMG file will replace the engineering HBOOT with the shipping one (which is S-ON). If you use gfree though, you get true radio S-OFF (the engineering HBOOT is a fake one that tricks the phone into thinking you have S-OFF, thus allowing write access to the system). This is done by modifying partition 7 on the phone. Since this partition contains information specific to your phone, it is normally left untouched by a PC10IMG or RUU. This is why if S-OFF is obtained through gfree, simply replacing the HBOOT with a PC10IMG file won't revert you to S-ON.
Click to expand...
Click to collapse
What should I do first if I used gfree to return to stock on my T-Mobile US G2? I also flashed the eng-hboot.
I used this guide http://forum.cyanogenmod.com/topic/14344-how-to-root-a-new-g2/, and I flashed the "PC10IMG-altered.zip" right after I used gfree to get radio s-off.
Edit: I just followed the xda wiki and I didn't run into any problems.

[Q] [SOLVED] Final question before rooting my DZ

Hi,
I've got my DZ a couple of days ago. It's a secondhand DZ. Previously i've used HTC Touch, Touch Dual, TP2, so this is my first Android experience. I did lots of ROM playing on previous winmo phones, but after reading for these couple of days of Android modding, i learn that flashing another Android ROM is not so simple as winmo ROM.
This is my DZ info:
Android version 2.2.1
Baseband version 12.28e.60.140fU_26.04.02.17_M2
Kernel version 2.6.32.21-g6e170e7
Build number 1.82.707.1 CL317545 release-keys
Software number 1.82.707.1
VISION PVT SHIP S-OFF
HBOOT - 0.85.0009
MICROP - 0425
RADIO - 26.04.02.17_M2
eMMC - boot
Dec 13 2010
I've check with root checker and Titanium Backup, it says NO root access.
I've learned that with 1.82, i will have to downgrade first to 1.34.
In the steps for downgrading, i found that i will have to flash signed PC10IMG. But i also found in the sticky thread there's a warning, not to flash signed PC10IMG if i have S-OFF. So before i can downgrade, i have to get the S-ON.
I've read in a thread :
If for some reason (sending phone for warranty or repair, etc) you want to go back to S-ON:
- If you got S-OFF by flashing an Engineering hBoot, download the official HTC RUU for your phone version and flash the stock firmware back again. S-ON will be restored. This forum contains many threads with official RUUs.
- If you got S-OFF with gfree, it saved a backup copy to your SD card called "part7backup-xxxxxxxxxx.bin". It can be flashed back from a terminal emulator or from an ADB shell:
"dd if=/wherever/your/part7backup-xxxxxxx.bin of=/dev/block/mmcblk0p7
The problem is, i got a secondhand unit without microSD card. How can I get S-ON? I don't know how (what method) my DZ got S-OFF at the first place.
Any help is much appreciated.
prazzo said:
Hi,
I've got my DZ a couple of days ago. It's a secondhand DZ. Previously i've used HTC Touch, Touch Dual, TP2, so this is my first Android experience. I did lots of ROM playing on previous winmo phones, but after reading for these couple of days of Android modding, i learn that flashing another Android ROM is not so simple as winmo ROM.
This is my DZ info:
Android version 2.2.1
Baseband version 12.28e.60.140fU_26.04.02.17_M2
Kernel version 2.6.32.21-g6e170e7
Build number 1.82.707.1 CL317545 release-keys
Software number 1.82.707.1
VISION PVT SHIP S-OFF
HBOOT - 0.85.0009
MICROP - 0425
RADIO - 26.04.02.17_M2
eMMC - boot
Dec 13 2010
I've check with root checker and Titanium Backup, it says NO root access.
I've learned that with 1.82, i will have to downgrade first to 1.34.
In the steps for downgrading, i found that i will have to flash signed PC10IMG. But i also found in the sticky thread there's a warning, not to flash signed PC10IMG if i have S-OFF. So before i can downgrade, i have to get the S-ON.
I've read in a thread :
If for some reason (sending phone for warranty or repair, etc) you want to go back to S-ON:
- If you got S-OFF by flashing an Engineering hBoot, download the official HTC RUU for your phone version and flash the stock firmware back again. S-ON will be restored. This forum contains many threads with official RUUs.
- If you got S-OFF with gfree, it saved a backup copy to your SD card called "part7backup-xxxxxxxxxx.bin". It can be flashed back from a terminal emulator or from an ADB shell:
"dd if=/wherever/your/part7backup-xxxxxxx.bin of=/dev/block/mmcblk0p7
The problem is, i got a secondhand unit without microSD card. How can I get S-ON? I don't know how (what method) my DZ got S-OFF at the first place.
Any help is much appreciated.
Click to expand...
Click to collapse
You are already S-OFF? I'd find it strange that you'd be S-OFF and not be rooted.
install rom manager and check if there has been a recovery already flashed. Might answer your question
Why do you want s-on? S-off is a good thing
Sent from my T-Mobile G2 using XDA Premium App
You can check if you got S-OFF or S-ON
by entering bootloader
Power off your phone, then, hold the volume down key and the power key.
You might need to disable fastboot
Spastic909 said:
install rom manager and check if there has been a recovery already flashed. Might answer your question
Why do you want s-on? S-off is a good thing
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
I've already installed Rom manager and there's no clockwork recvery installed.
I want to flash custom rom. I need a root to do that. To get a root, i need to downgrade. To downgrade, i need to flash signed pc10img. And there's a warning here that said DONT flash pc10img with S-OFF. That's the problem.
Shinfang said:
You can check if you got S-OFF or S-ON
by entering bootloader
Power off your phone, then, hold the volume down key and the power key.
You might need to disable fastboot
Click to expand...
Click to collapse
I already did that. Bootloader says VISION PVT SHIP S-OFF. So that means i definitely have S-OFF.
I've learned some more from the post here and there. I think i figured out what happen with my DZ. I think the previous owner rooted and S-OFF the phone in the old firmware 1.34 then got an OTA update to 1.84. That update destroyed the root but somehow still S-OFF.
If I follow the direction in this thread, i assume that i can downgrade and root again. I will not need a goldcard to downgrade because currently i have S-OFF.
http://forum.xda-developers.com/showthread.php?t=905261
Am i right?
prazzo said:
I've learned some more from the post here and there. I think i figured out what happen with my DZ. I think the previous owner rooted and S-OFF the phone in the old firmware 1.34 then got an OTA update to 1.84. That update destroyed the root but somehow still S-OFF.
If I follow the direction in this thread, i assume that i can downgrade and root again. I will not need a goldcard to downgrade because currently i have S-OFF.
http://forum.xda-developers.com/showthread.php?t=905261
Am i right?
Click to expand...
Click to collapse
I am not sure whether it will work. But I am curious too.
I once upgrade via OTA and then I downgrade it following the instruction as per your link reference too. I rooted succesfully.
But, my DZ was S-ON.
Now you are in a different situation. You want to downgrade and root it but you already S-OFF.
Do you want to try it?
Cheers
silverwind said:
I am not sure whether it will work. But I am curious too.
I once upgrade via OTA and then I downgrade it following the instruction as per your link reference too. I rooted succesfully.
But, my DZ was S-ON.
Now you are in a different situation. You want to downgrade and root it but you already S-OFF.
Do you want to try it?
Cheers
Click to expand...
Click to collapse
I guess i have to try it.. will report after trying. Thnks all for the help..
Your theory on the previous owner having used the over the air update after rooting seems right to me. I've read more than a few times it will still show S-OFF but not be true S-OFF. Because you can't get S-OFF without root (well surely not on the newer 1.82's)
I'm not familiar with the 1.82 issues (why normal root methods fail on 1.82) but I wonder if temp root works, if you have radio S-OFF and temp root works it might be as simple as:
1. Obtain Temp Root (even Visionary could work)
2. Flash CWM Recovery (I'd use the flash_image method and not ROM Manager)
3. Reboot into CWM recovery
4. ...
5. Profit (Install a new pre-rooted ROM)
Of course this all depends on if temp root works with 1.82 and if your S-OFF is really S-OFF but it seems like a quick & easy thing to try.
I did it guys. It went smooth. Still needs goldcard though due to unmatched CID.
I'm on 1.34, rooted and S-OFF. Next find out ROM that i like most. Any recommendation? it has to be cool and fast..
So i figured that the warning "do not flash signed PC10IMG if you have S-OFF" is before we have the misc_version method. With misc_version "main is older" problem will never occur, provided misc_version done correctly.
Thank you all guys for your help and time especially for those guides starter. You guys are the ones who make this forum SO GREAT!
prazzo said:
I did it guys. It went smooth. Still needs goldcard though due to unmatched CID.
I'm on 1.34, rooted and S-OFF. Next find out ROM that i like most. Any recommendation? it has to be cool and fast..
So i figured that the warning "do not flash signed PC10IMG if you have S-OFF" is before we have the misc_version method. With misc_version "main is older" problem will never occur, provided misc_version done correctly.
Thank you all guys for your help and time especially for those guides starter. You guys are the ones who make this forum SO GREAT!
Click to expand...
Click to collapse
Congrats .
The first time I did after rooting was install ROM MANAGER premium version.
There a lot of rom to try with the easiest way..
Good luck

[Q] S-OFF... Again

Hi all.
I have a rooted wildfire with a custom ROM on HBOOT 0.80. As I'd like to S-OFF it, I searched for info, and at first it looked like I had to RUU it (with goldcard and all), and then use Revolutionary to do the trick.
Then I found this thread. Inside the file linked there there seem to be the correct HBOOT I need (1.01, same one as in the RUU) and a clear explanation of how to upload it, and I thought maybe it could be possible to just flash the HBOOT alone, without the rest, and then S-OFF the phone. In theory, this would cut the necessary steps quite a lot and allow S-OFF keeping the phone as it is.
The questions are, has anyone tried this procedure? If I do try and something goes wrong, will a nandroid restore of my previous setup also restore the old HBOOT, thus making the phone usable again?
Thanks!
Veon11
You can't use that method. Fastboot needs S-OFF by Revolutionary originally.
3xeno said:
You can't use that method. Fastboot needs S-OFF by Revolutionary originally.
Click to expand...
Click to collapse
It DID looked too easy...
Thanks for the quick answer.

Categories

Resources