Database Users

[Q] G2 Lost S-OFF after hboot update?

First I want to thank all from this site for all the work you've done!
OK, got a G2 few days ago rooted it using rage method, updated radio to 26.04.02.17 (read that solved some problems with cyanogen's 6.1.1 ROM), installed 6.1.1 ROM and all was well... Then I decided to upgrade hboot (for no particular reason) to 0.85.005 with fastboot. After install it rebooted and noticed I now have SHIP S-ON ...and it wouldn't boot..got stuck on HTC splash screen. So I say oops...pull battery and go into recovery and do a restore to a rooted stock ROM. Was successful but was hoping it would give me root back but no joy. Then tried to install 6.1.1 from ROM manager but no joy. (no surprise with S_ON) So I'm wondering:
Why did hboot update change it to S-ON?
Why didn't my restore restore S_OFF? ( thought restore re-wrote everything)
AND..where do I go from here? Should I just use rage again to get root?
Any help would be greatly appreciated!!
Again, thanks to all!!
Edit: OK just realized I still have root access threw terminal emulator???
How can this be with S-ON??
So I guess I still have root so I tried to install cyogen 6.1.1 from sd card using revovery.
all seems to go well, says its complete but when I reboot, it gets stuck on HTC splash screen
Also tried gfree and this method http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
got to 2nd to last command:
# /data/local/tmp/root
and get
# mkdir failed for /system/xbin, file exists
Anyone??

That sounds like the stock *DZ* hboot, not the G2 one. If so, you're lucky you didn't brick your phone. I wouldn't switch hboots between DZ/G2 unless you were flashing the whole ROM.
The fact that it's a stock one explains why you have S-ON, if you only had S-OFF via the eng hboot before.
What you need to do is run gfree, as you say, to get proper radio S-OFF.
S-ON/S-OFF has nothing to do with root. So you can still be S-ON and have root.
If you did a nandroid restore through Clockwork then as far as I'm aware that doesn't include a restore/backup of hboot.
You won't be able to flash another custom ROM/recovery until you get S-OFF back again.
That "mkdir" error message is normal, just ignore it. But gfree doesn't work with CM 6.1.1. It will work on 6.1 but there are some incompatible kernels too.
I suggest installing the eng hboot (the correct one for your phone, see the Wiki) to get S-OFF (but be careful doing this, e.g the checksums). Then revert to a ROM that is compatible with gfree and run gfree to get radio S-OFF. Then you can revert back to 6.1.1 or whatever you want.

steviewevie said:
That sounds like the stock *DZ* hboot, not the G2 one. If so, you're lucky you didn't brick your phone. I wouldn't switch hboots between DZ/G2 unless you were flashing the whole ROM.
The fact that it's a stock one explains why you have S-ON, if you only had S-OFF via the eng hboot before.
What you need to do is run gfree, as you say, to get proper radio S-OFF.
S-ON/S-OFF has nothing to do with root. So you can still be S-ON and have root.
If you did a nandroid restore through Clockwork then as far as I'm aware that doesn't include a restore/backup of hboot.
You won't be able to flash another custom ROM/recovery until you get S-OFF back again.
That "mkdir" error message is normal, just ignore it. But gfree doesn't work with CM 6.1.1. It will work on 6.1 but there are some incompatible kernels too.
I suggest installing the eng hboot (the correct one for your phone, see the Wiki) to get S-OFF (but be careful doing this, e.g the checksums). Then revert to a ROM that is compatible with gfree and run gfree to get radio S-OFF. Then you can revert back to 6.1.1 or whatever you want.
Click to expand...
Click to collapse
Thanks for responding! Especially after this post has turned into more of a rambling blog as I learn more.
I tried to run gfree to get s-off and it doesn't work, stays s-on. Thought it was because of the "mkdir" error message I was getting. Then tried to install eng hboot using the whole G2 ROOT INSTRUCTIONS here:
http://forum.xda-developers.com/showthread.php?t=834228
Everything goes smooth except for the"mkdir failed for /system/xbin. file exists"
When I reboot, still have:
VISION PVT SHIP S-ON
hboot-0.85.0005
Any ideas??
Again thanks for any help and suggestions!
Just noticed the first commands in the G2 ROOT INSTRUCTIONS have a "$" sigh ie: "$ adb push su /sdcard/su"
Does this mean you should run "adb shell" first? If that.s the case, I get "adb: permission denied" although I do see su on sdcard.
(I know I'm really grasping here )

No, you don't run "adb shell" before running those adb commands, because "adb shell" will give you a command prompt on your phone, and those adb push commands need running from your PC's command prompt. That "$" prompt shown in the guide can be confusing, because it's being run from a PC running Linux, which has a $ prompt. If you have Windows then you will have some sort of "C:\" prompt.
If you are only installing the eng hboot though, you don't need to do all that, since you already have root. Skip to the "Perm Root" section in that guide that you linked, and do everything up to and including the "dd" command. Then the sync and reboot bit (skip over the "root" script).
Although check what message you get from the insmod command. We might have a problem here, because if you're on CM 6.1.1 (that's what you're on, right ?) then gfree won't work and I don't know if either of those wpthis modules (OTA and pre-OTA) will work properly on CM 6.1.1.
The insmod is crucial because unless that command gives you the "right" error message as shown in the procedure, it won't disable the NAND write protection and so won't let you write the hboot permanently.

A bit offtopic, but maybe someone will find this helpful: in many tutorials for *NIX (Linux, OSX, BSD etc.) users you'll find that what you need to type in a command prompt (terminal) starts with either $ or #.
While that may be confusing for Windows users, it is a hint as to whether you are supposed to run the commands as a simple user (the prompt shows a $) or as the administrator (or root) user (in which case, the prompt shows a #).

steviewevie said:
No, you don't run "adb shell" before running those adb commands, because "adb shell" will give you a command prompt on your phone, and those adb push commands need running from your PC's command prompt. That "$" prompt shown in the guide can be confusing, because it's being run from a PC running Linux, which has a $ prompt. If you have Windows then you will have some sort of "C:\" prompt.
If you are only installing the eng hboot though, you don't need to do all that, since you already have root. Skip to the "Perm Root" section in that guide that you linked, and do everything up to and including the "dd" command. Then the sync and reboot bit (skip over the "root" script).
Although check what message you get from the insmod command. We might have a problem here, because if you're on CM 6.1.1 (that's what you're on, right ?) then gfree won't work and I don't know if either of those wpthis modules (OTA and pre-OTA) will work properly on CM 6.1.1.
The insmod is crucial because unless that command gives you the "right" error message as shown in the procedure, it won't disable the NAND write protection and so won't let you write the hboot permanently.
Click to expand...
Click to collapse
ahhhh..thanx for clarifying "$" issue for me.
I am NOT on CM 6.1.1
I have stock OTA rom right now (with root), sorry for the misunderstanding
OK,this is exact error message I get:
insmod: init_module '/data/local/wpthis-OTA.ko' failed (function not implemented)
After I run dd=..... I get
2048+0 records in
2048+0records out
1048576 bytes transferred in 0.079 secs (13273113bytes/sec)
So all looks perfect to me, but I still get stuck with:
....S-ON
hboot-0.85.0005
does the "insmod" being in error message mean anything?
In any event, at least I still have a working phone and learned alot more
(like you said..I'm very lucky I didn't brick it flashing this hboot update)

That's the "correct" error message from insmod. But weird stuff is going on here, which isn't too suprising if you have the wrong hboot for your phone.
I'm getting confused, I thought you were on CM 6.1.1. I also thought your phone was stuck in a boot loop, but you seem to be able to still run commands as root, so presumly it boots ok now ?

steviewevie said:
That's the "correct" error message from insmod. But weird stuff is going on here, which isn't too suprising if you have the wrong hboot for your phone.
I'm getting confused, I thought you were on CM 6.1.1. I also thought your phone was stuck in a boot loop, but you seem to be able to still run commands as root, so presumly it boots ok now ?
Click to expand...
Click to collapse
Sorry for the misunderstanding, I had CM 6.1.1 on when I flashed wrong hboot. After that it would get stuck on HTC screen when trying to boot up into CM 6.1.1
So I booted into recovery and did a restore which luckily worked. Which now I have no idea why that worked looking back other than because it was a legit stock ROM, so it allowed it. Is this the case??
Last night I actually tried to un-root and get everything back to stock (including hboot) via this method:
ttp://theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision/
but got stuck on "dd if=/sdcard
/miscnew.img of=/dev/block/mmcblk0p17" with a read only ermision denied message
which I wasn't surprised because I have S=ON

[Q] 1.34 rooted and S-off.. Need to go back. How ?

So i've rooted my Desire Z with the stock rom of v. 1.34 .. I think i need to send it back for repairs since my green led is not working anymore.. But before i can do that i want to unroot the phone.. can someone here explain to me how i do it ? Im a total retard when it comes to this.. Sometimes i even wonder how the heck i managed to root the device
EDIT: Forgot to mention that i've applied a OC kernel.. !

No one ?
5char

I reckon ppl are a bit cautious in giving advice as there have been a few issues.
Lets start with which method did you use to root and s-off?

wileykat said:
I reckon ppl are a bit cautious in giving advice as there have been a few issues.
Lets start with which method did you use to root and s-off?
Click to expand...
Click to collapse
Thanks man.. Glad you want to help ..
I wanted to able to use this kernel, so i followed the suggested rooting guide from that thread.. Which i believe is this
I just want to make sure i do everything right you know

Da9L said:
So i've rooted my Desire Z with the stock rom of v. 1.34 .. I think i need to send it back for repairs since my green led is not working anymore.. But before i can do that i want to unroot the phone.. can someone here explain to me how i do it ? Im a total retard when it comes to this.. Sometimes i even wonder how the heck i managed to root the device
EDIT: Forgot to mention that i've applied a OC kernel.. !
Click to expand...
Click to collapse
Hi !
I need to know 2 things before I can help you:
1. Did you install the engineering hboot?
You can check this by booting into fastboot mode:
- Shutdown the phone
- Press and hold the touchpad-button and hold it while pressing the Power button.
-> On the screen with the surfing androids the first lines contains either SHIP or ENG. If you have ENG then you installed the engineering hboot.
2. Did you use gfree to achive radio S-OFF
You can check this by using the gfree_verify procedure - see http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#VERIFY_.28using_.22gfree_verify.22.29
if you have @secu_flag = 0 then you are radio S-OFF if @secu_flag = 1 you are radio S-ON.
Please check this and post your results, then i can post your way to go.
have fun - Guhl

guhl99 said:
Hi !
I need to know 2 things before I can help you:
1. Did you install the engineering hboot?
You can check this by booting into fastboot mode:
- Shutdown the phone
- Press and hold the touchpad-button and hold it while pressing the Power button.
-> On the screen with the surfing androids the first lines contains either SHIP or ENG. If you have ENG then you installed the engineering hboot.
2. Did you use gfree to achive radio S-OFF
You can check this by using the gfree_verify procedure - see http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#VERIFY_.28using_.22gfree_verify.22.29
if you have @secu_flag = 0 then you are radio S-OFF if @secu_flag = 1 you are radio S-ON.
Please check this and post your results, then i can post your way to go.
have fun - Guhl
Click to expand...
Click to collapse
1. Nope it shows SHIP
2. Gave me this output (My phone has allways been sim unlocked however.. Bought it without contract!)
Code:
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK

Da9L said:
1. Nope it shows SHIP
2. Gave me this output :...
gfree verify_secu_flag returned:
@secu_flag: 0
Click to expand...
Click to collapse
!!! WARNING FOR OTHERS - DO NOT DO THIS IF YOU ARE NOT RADIO S-OFF AND HAVE THE ENGINEERING HBOOT INSTALLED !!!
OK this is good because as you don't have the eng-hboot installed we can safely flash the full stock rom and i assume that you have a custom kernel and a custom recovery installed that we need to get rid off.
Before i go into details of commands i would like to give you the principle procedure:
1. reinstall the stock firmware by copying a PC10IMG.zip to /sdcard and then boot into hboot and let it install the complete stock rom.
2. temproot again using psneuter
3. restore the backup of your partition 7 using gfree 0.4
So what we need is:
- a stock rom from here http://www.multiupload.com/GH26HXLLES
- psneuter from here http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/psneuter/psneuter.zip
- gfree 0.4 from here http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/gfree/gfree_04.zip
You need to make sure that this PC10IMG.zip really is your stock version (maybe find yours somewhere else)
1. Installing the stock rom:
connect the phone to usb.
download the file and rename it to PC10IMG.zip and put it to the root of your sdcard using:
Code:
adb push PCIMG10.zip /sdcard/
shutdown your phone.
boot into hboot by holding the <Vol-Down> key while you press <Power> to boot.
hboot (white screen with surfing androids and the word HBOOT in blue) will scan for the file PCIMG10.img and load it.
Then you can use <Vol-Up> to start the process. In the middle of the process the screen will get dark for some seconds and then it will start again -> don't panic wait until it is completely finished.
When done - reboot
2. Temp-root using psneuter:
On the phone go to Settings - Applications - Development and enable USB debugging again.
Unzip the psneuter.zip, install and execute psneuter on your phone:
Code:
adb push psneuter /data/local/
adb shell chmod 777 /data/local/psneuter
adb shell /data/local/psneuter
3. use gfree to restore your partition 7 backup
Unzip gfree_04.zip and install it on the phone
Code:
adb push gfree /data/local/
adb shell chmod 777 /data/local/gfree
3.a When you used gfree to get radio s-off it created a backup of the partition named /sdcard/part7backup-<time>.bin (replace <time> with the time number). We will restore this file now.
Get a root shell:
Code:
adb shell
The prompt should be # now
Execute gfree to restore the backup (in the root shell) - replace <time> with your time number in the following command.
Code:
/data/local/gfree -r /sdcard/part7backup-<time>.bin
3.b Alternative: (if you don't have your partition 7 backup anymore - don't do if you did 3.a):
You need to know the CID that your phone had originaly, it could be HTC__001
Excecute gfree to set S-ON and CID:
Code:
/data/local/gfree -s on -c HTC__001
4. clean up (still in the root shell):
Code:
rm /data/local/psneuter
rm /data/local/gfree
rm /sdcard/PC10IMG.zip
So now you are back to stock.
You might want to boot to hboot again and use "FACTORY RESET" to wipe data and cache.
And you might format the micro-sd card before you return the phone.
I hope this is it (written without a phone so there might be typos)
have fun - Guhl

Wow guhl99 that is really really helpfull ! I appriciate it so much! Im gonna try it later today ..
However i dont think i got the backup of that partition.. Must have deleted by mistake for some reason
Is there anyway i can find out what CID my phone had originaly ?
EDIT: Another question.. What would happen if i just acceptet the OTA upgrade ? Wouldn't that unroot and s-on my phone ?

Da9L said:
Wow guhl99 that is really really helpfull ! I appriciate it so much! Im gonna try it later today ..
However i dont think i got the backup of that partition.. Must have deleted by mistake for some reason
Is there anyway i can find out what CID my phone had originaly ?
Click to expand...
Click to collapse
Hi !
Welcome, i think it was time to summarize this once. And as I am constantly going back to stock to test some exploits and then reroot i have some practive.
Yes there is. The CID is also stored in the first 8 bytes of partition 17 - the misc partition - (and no one knows why).
So you can to the following (in a adb root shell)
Code:
dd if=/dev/block/mmcblk0p17 bs=8 count=1 2>/dev/null
The first 8 characters of the output should be your CID (the # behind it is the prompt for the next command as you do not receive a new-line by the command above)
have fun - Guhl

Da9L said:
EDIT: Another question.. What would happen if i just acceptet the OTA upgrade ? Wouldn't that unroot and s-on my phone ?
Click to expand...
Click to collapse
Sorry I did not see this question.
It will unroot but will NOT S-ON the phone.
But something really nasty will happen:
- It will install a radio firmware version that prevents gfree from dropping the write protection of the emmc chip for the radio configuration partition 7. And because of this you are not able to set S-ON again or set your CID back (or restore your partition 7 backup).
You would then have to downgrade the firmware again to 1.34 (using a procedure that is documented in this forum) and is even more complicated. And after the downgrade (that includes installing the stock rom as i described above) you would have to continue at point 2 of my description above.
SO DO NOT ACCEPT THE OTA (it would not brick things but needs another 2 steps).
have fun - Guhl

Guhl, could you use Gfree to restore your backup (or go S-ON) first while you were still rooted? Then with S-ON, use the PC10IMG.zip to restore back to the shipping ROM (which should work, assuming the zip to be signed).
Just wondering if that extra step of temp rooting before using gfree is necessary...

ianmcquinn said:
Guhl, could you use Gfree to restore your backup (or go S-ON) first while you were still rooted? Then with S-ON, use the PC10IMG.zip to restore back to the shipping ROM (which should work, assuming the zip to be signed).
Just wondering if that extra step of temp rooting before using gfree is necessary...
Click to expand...
Click to collapse
Hi !
You are absolutely right, you could do it this way.
The reason why i always remove s-on as the last step is just to have the system and recovery partitions write enabled till the last step.
So if anything goes wrong you still have options till the end.
But if you don't need that extra security you could do it your way.
have fun - Guhl

MT3g Sapphire 2.2.1 HACK YEt?! (Recovery, rom flashing)

I have a mytouch 3g its the 1st version I'm guessing (no head phone jack)
Hboot =
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0013 (SAPP30000)
CPLD-10
RADIO-2.22.28.25
OCT 21 2009 ,22:23:27
I tried flashing sappimg nbh and zip nbh says main is older
Zip seems as it flashes completes and go str8 back to hboot like nothing happened.
Tried to back up rec but says backup failed
And will not do anything with rom managers, says flashed recovery complete but in recovery mode shows a triangle.
Also 1 click works, su shows up in terminal..
I seen that this new update doesn't work yet
I tried searching but nothing. So if I just have to wait just say so.
But if something comes out please let me know.
And yes yes I know I shouldn't have updates now, but I didn't know before hand (obviously).
So thanks ahead for responses.
Sent from my HTC Vision using XDA App

Man, what exactly do you want? Custom recovery? There is sticked topic by mumilover. He wrote how to flash manually
http://forum.xda-developers.com/showthread.php?p=7707672
Sent from my A7-040 using Tapatalk

well that doesnt work... it just keeps saying failed when i try ... and i did root and tried to flash recovery via rom manager says flased successful but when i recovery boot it shows a triangle...
how can i get s-off on this phone.. its running stock 2.2.1

and as he says "This guide is confirmed to work with Rogers 2.1 update!
It will not work with the new 2.2.1 update" so im basically asking is ther any one that knows if a way around 2.2.1 yet?
If not thanks for trying/looking if so HELP! Plz!
=)

homeboy773 said:
well that doesnt work... it just keeps saying failed when i try ... and i did root and tried to flash recovery via rom manager says flased successful but when i recovery boot it shows a triangle...
how can i get s-off on this phone.. its running stock 2.2.1
Click to expand...
Click to collapse
Okay, I'm not going to get into why you can't flash a custom recovery, but if you have "Root" then just do this . . .
http://forum.xda-developers.com/showthread.php?t=1428838 : My Unroot/ReRoot Guide .
::----:: You might run into an issue where you can't change your recovery. . .Heres the Fix.
1.) Put Your Recovery.img on your SDCard : (CW Recovery)Click the above link..
2.) Put flash_image on your SDCard : Click the above link.
3.) Open up terminal/adb (which ever you prefer) :v:
3.a)
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
or you can do it from the terminal emulator app like i did . .
(Skip the adb shell part if you do)

GeEazy said:
Okay, I'm not going to get into why you can't flash a custom recovery, but if you have "Root" then just do this . . .
http://forum.xda-developers.com/showthread.php?t=1428838 : My Unroot/ReRoot Guide .
::----:: You might run into an issue where you can't change your recovery. . .Heres the Fix.
1.) Put Your Recovery.img on your SDCard : (CW Recovery)Click the above link..
2.) Put flash_image on your SDCard : Click the above link.
3.) Open up terminal/adb (which ever you prefer) :v:
3.a)
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
or you can do it from the terminal emulator app like i did . .
(Skip the adb shell part if you do)
Click to expand...
Click to collapse
this is the guide for the mytouch 3g 1.2(32A). I want a guide for the 32B on 2.2.1

playerpatrick said:
this is the guide for the mytouch 3g 1.2(32A). I want a guide for the 32B on 2.2.1
Click to expand...
Click to collapse
it doesn't matter. . . it's not like your flashing a Rom, or a spl/radio .ect its a recovery its all the same steps. . .

same here
Hi
I have the same hanset, hardware, and software.
Now I happen to be going through the same problem flashing a recovery. Just wanted to know if the unroot/ reroot method worked for you?
Thank you.

is there a way to root a stock 2.2.1 mytouch 3g? ive been searching around the forums and i can only find tutorials for pre-2.2.1

iamwhoamnot said:
is there a way to root a stock 2.2.1 mytouch 3g? ive been searching around the forums and i can only find tutorials for pre-2.2.1
Click to expand...
Click to collapse
SuperOneClick can do root even if 2.2.1

can u post a link for SuperOneClick for 2.2.1?

Here at xda: http://forum.xda-developers.com/showpost.php?p=8532790&postcount=1
Before getting root and installing custom recovery it is strongly recommended do wipe data / factory reset. Make sure you have backup.
Sent from my A7-040 using Tapatalk

rooting mytouch 3g
i have a mytouch 3g with google, has stock 2.2.1 on it, i finally got the computer to recognize it and now i can get to the SD card thru my computer, but i can't find any way to root this phone at all, i keep seeing that superoneclick method works but i can't get it to work for me, i hook the phone up, push root and it gets halfway thru the steps and stops, what am i doin wrong? do i need a certain exploit set up in superoneclick?

Supeoneclick creates log on screen. Go to pastebin.com, post log there and give me link. I guess, you have problem 'no enough space'...

[GUIDE] Returning to stock, unroot. Also with broken screen/digitizer

I've been meaning to write this guide for a little while, and someone needing it recently posted a question asking how, so I figured I'd get off my ass and do it.
This will work for Vision, Ace and Glacier devices.
NOTE: This will only work if you are TRUE S-OFF
You will need ADB set up and running to finish this off.
Also, make sure you're on charge only mode.
Flashing one of the roms provided will have that as default
Section 1: Download the appropriate rom for your device.
Obtain an appropriate rom from http://thetable.poseidon.feralhosting.com/VISION/VISION/
these are stock roms with the only change being "persist.service.adb.enable = 1" added so /system/build.prop
I modified these roms for people with broken screens/digitzers, so if you're phone is perfectly functional, go ahead and grab a rom from UNMODDED dir. Just enable adb debugging once its flashed
Section 2: Flash the rom via fastboot RUU mode.
If you don't have a fastboot executable, download the zip attached to this post, and run the one appropriate for your OS
Make sure the fastboot executable and the rom are in the same directory, and you're command prompt/terminal is pointed to that directory.
Also, make sure you don't have a PC10IMG/PD98IMG/PG15IMG on your sdcard
A. Make sure phone is powered off
B. Hold Volume Down, and press Power to run phone on
C. Wait a minute or so (while hboot scans for updates) then press Power ONCE
D. Verify you are in fastboot mode by running:
Code:
fastboot-[OS] devices
this will return your serial number if you are in fastboot mode
E. Reboot to RUU mode
Code:
fastboot-[OS] oem rebootRUU
F. Flash the rom
Code:
fastboot-[OS] flash zip [NAME].zip
This will start flashing the rom to your device.
IT (MOST PROBABLY) WILL FAIL
REPEAT THE LAST COMMAND
Code:
fastboot-[OS] flash zip [NAME].zip
G. Reboot Phone
Code:
fastboot-[OS] reboot
Section 3: Return to S-ON and original CID
A. Obtain temp-root
Download the attached psneuter and gfree zips
Code:
> adb push psneuter /data/local/tmp
> adb push gfree /data/local/tmp
> adb shell
$ cd /data/local/tmp
$ chmod 755 *
$ ./psneuter
This will kick you out of adb shell
B. Restore S-ON
If you have your part7backup-xxxxxxx.bin (check sdcard):
Code:
> adb shell
# /data/local/tmp/gfree -r /sdcard/part7backup-xxxxxxx.bin
(replace the xxxxxxx's with the correct numbers)
Rejoice! You are back to S-ON!
If you do not have your part7backup:
Find your original cid:
Code:
> adb shell
# dd if=/dev/block/mmcblk0p17 bs=1 count=8 2>/dev/null; echo
Restore S-ON and CID
Code:
# /data/local/tmp/gfree -s on -c ORIGINAL_CID
Section 4: Rejoice! And Optionally flash an official stock rom
Completely stock/unmodded roms can be found at http://thetable.poseidon.feralhosting.com/VISION/VISION/UNMODDED/
Flash them same as Section 2.
If you have any issues, need help, etc. Please join #G2ROOT on freenode
There are normally people on there all the time, but please either hang around, or come back if no one responds
Credits:
scotty2 for psneuter
scotty2 and Guhl for gfree
Setherio for the fastboot collection zip
pierre_ja for making me make those rom.zips
laga_ for how to make those rom.zips
anyone else I may've forgotten
-Nipqer

This guide is officially supported by #g2root. If you need help, join irc freenode, #g2root.
Donate to EFF

Possible errors using gfree
Hello Nipqer, cool tutorial!
An possible addition for using gfree: Make sure that the phone is in "charge only" mode. I heard that this solved some problems in the past when using "gfree -s on -c OIGINAL_CID".
Best regards,
Catherall
-----------------
HTC Desire Z with currently installed ROMs:
Virtuous Affinity 2.0.5
PyroMod's CyanogenMod 7.2 Nightly
CyanogenMod 7.1
Virtuous G-Lite 2.0.1
MIUI 1.7.22
Virtuous Quattro RC3

Added that info, charge only mode will be default anyway if they flash one of the provided roms.
-Nipqer

In step 1 For a T-Mobile G2 using http://www.ratherphallic.co.cc/ the rom I would download is 'G2_PC10IMG.zip' correct?
Also in step 2 can I flash the rom via fastboot w/o adb??? I think I rename the zip file to PC10IMG.zip correct?

Yes, use the G2_PC10IMG.
If you use fastboot, it doesn't matter how the rom is named.
If you use hboot however, then yeah it needs to be named PC10IMG.zip, and yeah, it just goes on the root of your sdcard
-Nipqer
Sent from my HTC Vision using xda premium

nice guide!
Ty for the information.
Nice guide with good downloadlink.

Hey Nipqer thank you so much, this definitely needs to be more known and used. It's the second time I need to send the phone back and I couldn't understand what to do and which files to use because the guide is for g2 and there are everywhere menaces like don't flash this/that/all pc10img with s/off.
Then pierre_ja linked me your guide and did it in ten minutes...
Edit: the bad thing is that I haven't been able to find this searching everywhere in the web....
Sent from my HTC Vision using XDA

Perfect! Thanks a lot.
When the flashing of stock rom fails it says this?
FAILED (remote: 43 main version check fail)
So its enough just to run the command again?

Hmm, that error means you're not true (radio) s-off
to resolve it you'll need to run misc_version as per this guide http://forum.xda-developers.com/showthread.php?t=1178912
-Nipqer

You were right. I was trying to flash stock rom after S-ON. The only reason I wanted to flash version w/o adb debugging on was because I couldnt update using classic Settings/Info/Update software. Everytime I got stuck on screen with red rectangle. When booting to hboot I had on top line with pink background "Locked (OOW)". I flashed stock ROM over RUU and it vanished. Everything is ok now. Fully updated stock phone.
I think I messed up things by flashing htcdev.zip. If I understand this is for people who used oficial htc unlocking method. I flashed my device back in 2011 even before it was release so I didnt know about this option.

i keep getting error message everytime i try to flash the PC10IMG.zip file doing it tru fastboot. also when i try the none adb it loads up at the boatloader but just goes back to boatloader screen . any ideas?

Whats the error message your getting?
-Nipqer

error: cannot load 'PC10IMG.zip'
i put the zip file in the same directory . platform tools

Nipqer you are the f***ing MAN thanks alot. you saved my phone. now going for a warranty. again thank you . thank you thank you.

Returning to Stock w/o S-ON
Thank you for the great guide Nipqer.
I am running CM7.2 RC version with true s-off.
I want to go back to the Stock ROM with the latest Updates but with S-OFF.
How do i achieve that???

Just download a stock rom and flash it.
S-OFF will stay no matter what you do, until you re run gfree to remove it.
If you flash a stock rom from www.ratherphallic.co.cc you should get OTA's (thought I can't guarantee that), or you could download a stock gingerbread rom from www.shipped-roms.com
-Nipqer
Sent from my HTC Vision using xda premium

Getting an error= remote : 53 image unzipping failed
after that not able to switch on the phone or anything.
was flashing Vision_DZ_1.34.405.5_PC10IMG.zip
Please Help !!!

hmm, the phone should be able to turn on fine, if it failed opening the rom to flash then it wouldn't of changed anything.
Can you run an md5 check on the downloaded rom? it might be corrupted.
Otherwise, just try a different rom.
-Nipqer

Nipqer said:
hmm, the phone should be able to turn on fine, if it failed opening the rom to flash then it wouldn't of changed anything.
Can you run an md5 check on the downloaded rom? it might be corrupted.
Otherwise, just try a different rom.
-Nipqer
Click to expand...
Click to collapse
I tried the modded rom and it worked.....thanks a lot Nipqer

help with downgrade and root

im going crazy
first i unlocked the boot loader that was easy
2. i was able to downgrade rom to version 1.00.000.0 via misc_version utility
3. i got 2.3.4 android can downgrade to froyo 2.2.1
4. and what driving me crazy when i attempt temp root i keep getting permession denied and more if i try to flash with fastboot the phone stuck on tmobile screen the only way to get the phone complete boot is by using RUU glacier exe via bootloader
i search all over the web cant fined nothing helfull HELP ! ! !

Did you unlock via HTC the bootloader
Sent from my ROOTIE TOOTIE FRESH 'N FRUITY GLACIER

yes i did and downgrage to version1.00.000.0 but when start root thats what i get
$ chmod 755 /data/local/tmp/*
chmod 755 /data/local/tmp/*
Unable to chmod /data/local/tmp/fixsu.sh: Operation not permitted
$

If you unlocked via HTCDev - you need to relock back before downgrading.
Next time try following the guides, it'll make your life easier. When you can't find anything - it often means you're searching for something wrong.

can you please right the steps im going crazy if you will please
Jack_R1 said:
If you unlocked via HTCDev - you need to relock back before downgrading.
Next time try following the guides, it'll make your life easier. When you can't find anything - it often means you're searching for something wrong.
Click to expand...
Click to collapse

i relocked bootloader and it works thank you you the man BRO