Develop Bugs

[GUIDE] Permanent root on Desire Z 'the clean way', using rage

This thread is copied and modified from the G2 thread by trigeek for the Desire Z:
http://forum.xda-developers.com/showthread.php?t=834228
Apart from the changed hboot and wpthis-Z kernel module for the Desire Z instead of the G2, I have also updated the su-binary and SuperUser.apk to the latest version by ChainsDD
In no way I can be held responsible for any bricks to your phone. You are using this guide at your own risk!! I did test this guide on my own, and also on a friend's Desire Z.
As there was no manual rooting guide for the Desire Z, I posted it myself in order to help others that do not like visionary and like to do it 'the clean way'.
[GUIDE] Temp to permanent root on Desire Z, using rage instead of visionary
=================================================
There's already a guide here for obtaining permanent root using VISIONary, but some folks in #G2ROOT are having issues with the way that VISIONary modifies parititons. Using rage directly is a bit cleaner, since you know exactly what it's going to touch at each step of the way. I did NOT come up with any of this on my own, I'm building completely off of work that others have done. Speaking of which-
None of this would be possible without the tireless work that scotty2 put in. He stayed with the project for well over a month, through lots of smashed hopes and dead ends, until the solution was finally found. Were it not for his work, as well as the help of a few other key folks- we wouldn't be here. He deserves our thanks and some donations! We're talking hundreds of hours of work here, a couple bucks is not too much for that. His paypal is:
[email protected]
Send him some love! I'm not asking for anything myself, because I spent a half hour putting this together, and that doesn't deserve any donations!
DESIRE Z ROOT INSTRUCTIONS
=================================================
These are modified instructions based on the ones posted at http://bit.ly/g2root that use Visionary. A number of people have run into issues with the way that Visionary juggles around temporary partitions, and using the original root exploit is a much easier, and cleaner method for achieving permanent root. This tutorial will walk you through the rooting process by first achieving temporary root, and moving on to permanent root.
REQUIREMENTS
=================================================
•Visionary disabled at boot or uninstalled completely
•Android Terminal Emulator app
•ADB
•desirez-combined-root.zip (Attached to this post)
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.
VERY IMPORTANT!
Visionary has caused filesystem corruption for some users during the rooting process. Before attempting the instructions below, make sure that you have "auto run on boot" turned OFF, and reboot your system. Since you will not need visionary anyway after this, you might as well just uninstall visionary and reboot NOW before doing anything.
TEMP ROOT
=================================================
ON YOUR PC:
Unzip the z-temp-root files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
Code:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
ON YOUR PHONE:
1.Launch Terminal Emulator
2.
Code:
/data/local/tmp/rage
3.Wait for the message: "Forked #### childs."
4.Menu > Reset Term - Terminal Emulator will exit.
5.Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
6.**NOTE**: in the original directions from the XDA thread, you are instructed to run the /data/local/tmp/root script here. DON'T do this just yet. Leave the terminal window open.
PERM ROOT
=================================================
ON YOUR PC:
unzip z-perm-root and navigate to that folder. There will be four files. You will need to push two of these to your phone: hboot_7230_0.84.2000_100908.nb0 and wpthis-Z.ko. The other two files are optional for checksum verification.
Code:
$ adb push hboot_7230_0.84.2000_100908.nb0 /data/local
$ adb push wpthis-Z.ko /data/local
Optional but might came in handy:
Code:
$ adb push md5checksum /sdcard/md5checksum
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt. Now run:
Optional but recommended:
Code:
# /data/local/tmp/busybox md5sum /data/local/*
You should see:
hboot_7230_0.84.2000_100908.nb0 2ce1bdd5e4c1119ccfcecb938710d742
wpthis-Z.ko c73c5e77c91d306c418983c002b60b93
In case your hboot or wpthis-Z.ko file do not have the same md5hash as shown above, DO NOT CONTINUE. This means your file is corrupt or you are using a different file, for example the one for the G2 instead of Desire Z.
Now, let's turn off security for permanent flashing:
Code:
# insmod /data/local/wpthis-Z.ko
init_module 'wpthis-Z.ko' failed (Function not implemented)
That means it worked. This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)
# dd if=/data/local/hboot_7230_0.84.2000_100908.nb0 of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
You should see some messages indicating that it was written.
Code:
# /data/local/tmp/root
This will lock in root, and give you 'su' access in the future. Next, run:
Code:
# sync
Now wait at least a minute, just to be safe. After waiting, reboot your phone using the power button. After it finishes starting up, launch the terminal emulator, and type 'su'. You should get the prompt asking you to grant permissions. If you got the prompt, congratulations! You have permanent root!

Nice guide, thanks

Thank you Mr Q. works like a charm!

first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
when I just ignore it and type sync after that I have no root acces after a reboot.
Does anybody have a solution for it? I have already done a hardreset with the same results.
thanks in advance...

So this only roots your phone? Or does it s-off as well? From what I understand this s-offs as well because you're pushing the hboot as well.
EDIT: Nevermind. I read the thread again and it does indeed s-off as well.

MarDor said:
first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
when I just ignore it and type sync after that I have no root acces after a reboot.
Does anybody have a solution for it? I have already done a hardreset with the same results.
thanks in advance...
Click to expand...
Click to collapse
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen

ssyed said:
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen
Click to expand...
Click to collapse
having the same issue here

So I'm looking into these S-OFF and rooting threads and here is two bricks too. Does anyone have an answer for these two or should I skip this? Did the hboot do this or was it due to some problem in inserted kernel module? (I.E. the reboot of the emmc controller resulted in a ****ed up file system?)

yelti said:
having the same issue here
Click to expand...
Click to collapse
AnyDone said:
So I'm looking into these S-OFF and rooting threads and here is two bricks too. Does anyone have an answer for these two or should I skip this? Did the hboot do this or was it due to some problem in inserted kernel module? (I.E. the reboot of the emmc controller resulted in a ****ed up file system?)
Click to expand...
Click to collapse
Ok, so I have figured out how to get out of this "quietly brilliant" loop.
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.

ssyed said:
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.
Click to expand...
Click to collapse
Ok, so does any one have an explanation why this happened?
1. It wasn't wrong or screwed hboot, otherwise we would be facing a real brick?
Was it the root method? Was it the wpthis-Z.ko?
It might have been the kernel module, but I can't be sure about that with so little knowledge I have. (sure not the module itself but the kick to the emmc?) Just that it seems to be more likely option than a rooting attempt on a cached r-o file system?
I'm not complaining about the guide, it is specific and easy to follow but I would really love to have these semi bricks etc inspected more closely. It is not really helping to encourage ppl to root and try safe-off when we have unexplained bricks and semi-bricks around

MarDor said:
first of all.. thanks for this great guide. Everything went perfect until I came to the step to lock in root. After the command "/data/local/tmp/root" I get this error:
mkdir failed for /system/xbin, File exists
Click to expand...
Click to collapse
ssyed said:
Everything was fine up until this point. So i restarted the phone and phone is stuck on the "quietly brilliant" screen
Click to expand...
Click to collapse
yelti said:
having the same issue here
Click to expand...
Click to collapse
Did you guys run Visionary before trying this "rage" method of rooting ?

steviewevie said:
Did you guys run Visionary before trying this "rage" method of rooting ?
Click to expand...
Click to collapse
I don't know about others, but I didn't on mine. I was rooting it for the first time. Also, I don't know if this has anything to do with it, but I have the Bell version from Canada.

The root script threw an error for me too, so just to be safe I opened the script and typed in the commands manually. If you have problems with the script, just run these commands from the root terminal on your phone:
Code:
/data/local/tmp/busybox killall rage
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
mkdir /system/xbin
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
sync
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Hope this helps someone.. Thanks to the OP for the scripts.

Have a quick look, /system/xbin already seems to exist on my phone too.
So is there an error in the script ? e.g. needs to ignore if the directory already exists ? Or am I (we ?) missing something ?

goldenarmZ said:
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Click to expand...
Click to collapse
Good info, thanks. Perhaps just comment out that line of the script, to save running it all by hand (and therefore be prone to more error ?) ?

steviewevie said:
Good info, thanks. Perhaps just comment out that line of the script, to save running it all by hand (and therefore be prone to more error ?) ?
Click to expand...
Click to collapse
I did that first.. it threw more errors with the mount commands because I'd already run the script once, so some of the commands were repated. If it's your first run through, commenting it out would be fine.
I only did it line by line so I could see any more errors for myself and decide if they were important. As it turns out the script is very simple and only involves moving files around and changing their permissions.. anything that goes wrong should be immediately apparent even if you have no experience with shell commands.

goldenarmZ said:
I only did it line by line so I could see any more errors for myself and decide if they were important. As it turns out the script is very simple and only involves moving files around and changing their permissions.. anything that goes wrong should be immediately apparent even if you have no experience with shell commands.
Click to expand...
Click to collapse
Thanks, I was starting to worry about the bad experiences outlined above, given that this method appeared to be a more reliable one than VISIONary, and a route I was going to go down. But I'm pretty comfortable with shell scripts, so your input makes me feel a whole lot better !

goldenarmZ said:
The root script threw an error for me too, so just to be safe I opened the script and typed in the commands manually. If you have problems with the script, just run these commands from the root terminal on your phone:
-code-
"mkdir /system/xbin" just creates a directory, if it already exists you can ignore this command and proceed.
Hope this helps someone.. Thanks to the OP for the scripts.
Click to expand...
Click to collapse
thanks for this... I will give it a try

Yay, I just perma-rooted my phone using this method, many thanks to those who came up with the method in the first place, plus this handy guide too.
I got the message about /system/xbin already existing, but you can just ignore that message, it runs the rest of the script anyway.

ssyed said:
Ok, so I have figured out how to get out of this "quietly brilliant" loop.
First of all, this isn't a brick and all that is needed to fix this is a quick factory reset from the bootloader.
Click to expand...
Click to collapse
So after doing the guide you simply reeboot your phone into bootloader and select factory reset?
And then will the device be perm root and s-off???

[Q] Issues trying to Perm-Root using Visionary r14

So after 7 attempts, i decided i should seek help.
I've been trying to root my g2 using VISIONary r14.
1. I installed visionary r14 [i have usb debugging on] i leave all the check boxes unchecked and hit temp root
2. after temp root is finished, i hit attempt perm root.
phone reboots. i see superuser permission in the app drawer, all seems to be
fine.
3. Now I plug my phone to my PC via usb [i have the androidSDK and all drivers installed properly]
i change directory to C:\AndroidSDK\tools\
check adb devices and my device is listed.
then i shoot the following commands
adb push wpthis-OTA.ko /data/local/wpthis-OTA.ko
adb push hboot_7230_0.84.2000_100908.nb0/data/local/hboot_7230_0.84.2000_100908.nb0
adb shell
su
and this returns permission denied.
Ive searched everywhere and everyone says when the superuser prompt shows up check "Remember" and click yes. However this does not show up for me, at all.
I even go into terminal and try it, terminal also gives me 'Permission Denied'
any help anyone?

I'd just do it using the rage method. You obviously understand how to use some simple commands in adb, it's just that there's a few (read: not many) more. It's stickied in the development section.
Sent from my T-Mobile G2 running Cyanogenmod.

Yes rage way is the way to go. I think its a total of about 4 lines you need to enter
Sent from my HTC Vision using XDA App

yeah i ended up using the rage method, it was a lot easier than i thought it would be.

I did it using visionary r13 and terminal emulator. No pc. Go to youtube look up Blackprince310 he made a video on it. If it it doesn't work try permroot option on r13.
Sent from my T-Mobile G2 using XDA App

I would love to go the rage way, but I cannot get any permissions to do so...
Visionary r14 gives me a parsing error and does not install....
I've spent about 8 hours today trying to get this done!!! sigh!

Crey23 said:
I would love to go the rage way, but I cannot get any permissions to do so...
Visionary r14 gives me a parsing error and does not install....
I've spent about 8 hours today trying to get this done!!! sigh!
Click to expand...
Click to collapse
What steps have you taken? The rage way does not require visionary at all.
Sent from my HTC Vision using XDA App

shortlived said:
What steps have you taken? The rage way does not require visionary at all.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
right!!! I've been sitting at my pc for about 8 or 9 hours trying to root.
I continue to get adb: permission denied message no matter what I try. I follwed the adb for dummies guide that didnt work. I tried the VISONary r14 apk, I can't even open it.....
I'm beggining to wonder if I should run recovery first, get back to stock, and then try to root....how will that affect all my apps? Will it work?

Well you can always back them up with titanium backup. But yea i think you should do a factory reset then try the rage method. Follow the guide word for word. If you still got problems post em here i will try to help as much as i can. The whole process should take around 5min.
Sent from my HTC Vision using XDA App

I dont know how to link to a post with the xda app so here is the guide quoted
trigeek said:
There's already a guide here for obtaining permanent root using VISIONary, but some folks in #G2ROOT are having issues with the way that VISIONary modifies parititons. Using rage directly is a bit cleaner, since you know exactly what it's going to touch at each step of the way. I did NOT come up with any of this on my own, I'm building completely off of work that others have done. Speaking of which-
None of this would be possible without the tireless work that scotty2 put in. He stayed with the project for well over a month, through lots of smashed hopes and dead ends, until the solution was finally found. Were it not for his work, as well as the help of a few other key folks- we wouldn't be here. He deserves our thanks and some donations! We're talking hundreds of hours of work here, a couple bucks is not too much for that. His paypal is:
[email protected]​Send him some love! I'm not asking for anything myself, because I spent a half hour putting this together, and that doesn't deserve any donations!
[size=+2]G2 ROOT INSTRUCTIONS[/size]
=================================================
These are modified instructions based on the ones posted at http://bit.ly/g2root that use Visionary. A number of people have run into issues with the way that Visionary juggles around temporary partitions, and using the original root exploit is a much easier, and cleaner method for achieving permanent root. This tutorial will walk you through the rooting process by first achieving temporary root, and moving on to permanent root.
[size=+1]REQUIREMENTS[/size]
=================================================
Visionary disabled at boot or uninstalled completely
Android Terminal Emulator app
ADB
vision-combined-root.zip (Attached to this post, OR these two files: )
G2TempRoot.zip (http://forum.xda-developers.com/showthread.php?t=797042) NOTE: only download the files! Don't follow these instructions yet
vision-perm-root.zip (http://forum.xda-developers.com/showthread.php?t=833965) NOTE: again, just download the files from the thread.
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.
[size=+2]VERY IMPORTANT![/size]​Visionary has caused filesystem corruption for some users during the rooting process. Before attempting the instructions below, make sure that you have "auto run on boot" turned OFF, and reboot your system. Since you will not need visionary anyway after this, you might as well just uninstall visionary and reboot NOW before doing anything.
[size=+1]TEMP ROOT[/size]
=================================================
ON YOUR PC:
Unzip the G2TempRoot files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
Code:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
ON YOUR PHONE:
Launch Terminal Emulator
/data/local/tmp/rage
Wait for the message: "Forked #### childs."
Menu > Reset Term - Terminal Emulator will exit.
Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
**NOTE**: in the original directions from the XDA thread, you are instructed to run the /data/local/tmp/root script here. DON'T do this
just yet. Leave the terminal window open.
[size=+1]PERM ROOT[/size]
=================================================
ON YOUR PC:
unzip the vision-perm-root.zip and navigate to that folder. There will be four files. You will need to push two of these to your phone- hboot-eng.img, and one of the wpthis-[..].ko files.
If you HAVE applied the OTA update, push wpthis-OTA.ko.
If you HAVE NOT applied the OTA update, push wpthis-pre-OTA.ko.
Code:
$ adb push hboot-eng.img /data/local
$ adb push wpthis-OTA.ko /data/local
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt. Now run:
Code:
# insmod /data/local/wpthis-OTA.ko
You should see:
Code:
init_module 'wpthis-OTA.ko' failed (Function not implemented)
That means it worked. This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)
Code:
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
You should see some messages indicating that it was written. Next, run:
Code:
# /data/local/tmp/root
This will lock in root, and give you 'su' access in the future. Next, run:
Code:
# sync
Now wait at least a minute, just to be safe. After waiting, reboot your phone using the power button. After it finishes starting up, launch the terminal emulator, and type 'su'. You should get the prompt asking you to grant permissions. If you got the prompt, congratulations! You have permanent root!
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App

i need help, i perm rooted my phone now it got stuck at the HTC start up! what should i do?? pls reply ASAP!

Restore gfree backup

Hello all,
I've had a DZ for nearly 2 weeks now, and have been holding off on installing roms, overclocking etc until there were clear, reversible guidlines available.
A few days ago I was being curious and ended up doing this the UBERROOT guide.
Essentially I temprooted using Visionary then executed the gfree script on my PC:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
This went well, and when I got to the bootloader I could see indeed that my S was OFF.
However, before I go any further I want to know how to reverse what I've done. This is mentioned at the bottom of the UBERROOT guide:
'run gfree, which will create a new backup of partition 7 in its unlocked state.
this will disable wp on the emmc, as well as remove the brq filter from the kernel.
at this point, you can dd if=/wherever/your/partition7-relock.img of=/dev/block/mmcblk0p7
sync; reboot'
I found the backup, although it was a .bin file not .img
I entered in the command above, but my phone rebooted before I could enter the 'sync' command. My S is still off, it would seem.
So my question to you fine people, having typed all this is:
How can I use the gfree backup to return my phone back to stock?

nofixio said:
How can I use the gfree backup to return my phone back to stock?
Click to expand...
Click to collapse
You can use the "dd" command to copy back the image of that original partition, as you mention.
However, the latest version of gfree now includes some new options to un-do that stuff, e.g. you can switch S-ON back on and change your SID via options. See the Wiki on this - http://forum.xda-developers.com/wik...Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF

nofixio said:
Hello all,
I've had a DZ for nearly 2 weeks now, and have been holding off on installing roms, overclocking etc until there were clear, reversible guidlines available.
A few days ago I was being curious and ended up doing this the UBERROOT guide.
Essentially I temprooted using Visionary then executed the gfree script on my PC:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
This went well, and when I got to the bootloader I could see indeed that my S was OFF.
However, before I go any further I want to know how to reverse what I've done. This is mentioned at the bottom of the UBERROOT guide:
'run gfree, which will create a new backup of partition 7 in its unlocked state.
this will disable wp on the emmc, as well as remove the brq filter from the kernel.
at this point, you can dd if=/wherever/your/partition7-relock.img of=/dev/block/mmcblk0p7
sync; reboot'
I found the backup, although it was a .bin file not .img
I entered in the command above, but my phone rebooted before I could enter the 'sync' command. My S is still off, it would seem.
So my question to you fine people, having typed all this is:
How can I use the gfree backup to return my phone back to stock?
Click to expand...
Click to collapse
When you run gfree, it creates a bin file in your sd card. That bin file you shall rename it to "whatever".img, to be more specific rename it to partiiton7-relock.img.
Now once you did this, just run gfree again:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
Once done the above, just download terminal emulator and from there run:
su
dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7
sync
exit
And reebot the phone, Now you can go and see you are S-ON.
This method above works without a problem as myself have tried several times, however as steviewevie mentioned, the new version of gfree does this easier.

buzmay said:
When you run gfree, it creates a bin file in your sd card. That bin file you shall rename it to "whatever".img, to be more specific rename it to partiiton7-relock.img.
Now once you did this, just run gfree again:
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
Once done the above, just download terminal emulator and from there run:
su
dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7
sync
exit
And reebot the phone, Now you can go and see you are S-ON.
This method above works without a problem as myself have tried several times, however as steviewevie mentioned, the new version of gfree does this easier.
Click to expand...
Click to collapse
How to get that file (partition7-relock.img)? Because I formated the card after g-free method and I runned the official Ruu, so now I have that stupid S-Off, I need it S-On...

Niiceg said:
How to get that file (partition7-relock.img)? Because I formated the card after g-free method and I runned the official Ruu, so now I have that stupid S-Off, I need it S-On...
Click to expand...
Click to collapse
You don't need the backup for that. Just check the Wiki to find the options for gfree that will set it back to S-ON
Sent from my HTC Desire Z

steviewevie said:
You don't need the backup for that. Just check the Wiki to find the options for gfree that will set it back to S-ON
Sent from my HTC Desire Z
Click to expand...
Click to collapse
I don't find anything more than this guide:
Turning S-On
If you are returning your Vision to stock, you will want to flash your stock ROM and Recovery image before starting this, as root permissions and S-Off are required for both of those processes.
Remove Gfree (turn back S-On):
When you first ran Gfree, it automatically backed up your stock partition 7 (with S-On) and placed it on your microSD card as a file named part7-(something).bin and you will need to rename this file to: partition7-relock.img
Open up your ADB command prompt on your computer (with your phone plugged in) and type the following exactly as shown:
Code:
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7
sync
reboot bootloader
Your phone will reboot into bootloader. Look at the first line. The end should now say "S-On".

steviewevie said:
You don't need the backup for that. Just check the Wiki to find the options for gfree that will set it back to S-ON
Sent from my HTC Desire Z
Click to expand...
Click to collapse
I think they removed the automatic option for some reason, I beleive it was in version v.3 and now v.2 is back up. I was looking for that option for someone else early yesterday and noticed its not on the Wiki anymore, unless I missed it, but Im prettty sure I didn't. So I think were back to using the "dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7" command.
Update: On fattire's thread they said they took down v3 because people were having problems with it and are now advising using v2 and the old restore method.

joemm said:
I think they removed the automatic option for some reason, I beleive it was in version v.3 and now v.2 is back up. I was looking for that option for someone else early yesterday and noticed its not on the Wiki anymore, unless I missed it, but Im prettty sure I didn't. So I think were back to using the "dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7" command.
Click to expand...
Click to collapse
Where to get that file if i already formated the card?!

Niiceg said:
Where to get that file if i already formated the card?!
Click to expand...
Click to collapse
There is no where to get the file if you erased/formatted your sdcard without saving it somewhere else, the instructons on gfree tell you to do this:
"gfree created a backup of your original partition 7 at /sdcard/part7backup-<time>.bin you might consider copying this to a safe location on your computer."
So if you didnt do this I really dont know what you can do. I have my part7backup but I dont know if its specific to my device or if anyone can use it.

joemm said:
There is no where to get the file if you erased/formatted your sdcard without saving it somewhere else, the instructons on gfree tell you to do this:
"gfree created a backup of your original partition 7 at /sdcard/part7backup-<time>.bin you might consider copying this to a safe location on your computer."
So if you didnt do this I really dont know what you can do. I have my part7backup but I dont know if its specific to my device or if anyone can use it.
Click to expand...
Click to collapse
Well, What device you have? Z or G2? I think that it's not specific, because all phones are the same ;D

Niiceg said:
I don't find anything more than this guide:
Turning S-On
Click to expand...
Click to collapse
Look at http://forum.xda-developers.com/wik...Phone.2C_Set_SuperCID.2C_and_Turn_Radio_S-OFF
Scroll down to the bit that shows you the usage message for gfree and check out the "-s" option

joemm said:
I think they removed the automatic option for some reason, I beleive it was in version v.3 and now v.2 is back up. I was looking for that option for someone else early yesterday and noticed its not on the Wiki anymore, unless I missed it, but Im prettty sure I didn't. So I think were back to using the "dd if=/sdcard/partition7-relock.img of=/dev/block/mmcblk0p7" command.
Update: On fattire's thread they said they took down v3 because people were having problems with it and are now advising using v2 and the old restore method.
Click to expand...
Click to collapse
The latest gfree 0.03 had problems, yes, so they went back to 0.02 in the Wiki. But as my previous post shows, you can still un-do things with gfree 0.02.
The only reason to use the backup of partition 7 that I can think of is if you don't know what your original CID was to reset to, or if you want to SIM Lock your phone again (there doesn't seem to be an undo option for the SIM Unlock).

steviewevie said:
The latest gfree 0.03 had problems, yes, so they went back to 0.02 in the Wiki. But as my previous post shows, you can still un-do things with gfree 0.02.
The only reason to use the backup of partition 7 that I can think of is if you don't know what your original CID was to reset to, or if you want to SIM Lock your phone again (there doesn't seem to be an undo option for the SIM Unlock).
Click to expand...
Click to collapse
Ok, I see the option for sec-flag on/off but does that also restore the sim lock?
Sent from my T-Mobile G2 using XDA App

joemm said:
Ok, I see the option for sec-flag on/off but does that also restore the sim lock?
Click to expand...
Click to collapse
No it doesn't as far as I know, but that's why I said restoring SIM lock was the only real use for that part7 backup that I could think of.

steviewevie said:
No it doesn't as far as I know, but that's why I said restoring SIM lock was the only real use for that part7 backup that I could think of.
Click to expand...
Click to collapse
I wasn't sure myself, thanks.
Sent from my T-Mobile G2 using XDA App

steviewevie said:
No it doesn't as far as I know, but that's why I said restoring SIM lock was the only real use for that part7 backup that I could think of.
Click to expand...
Click to collapse
Okey, can you tell how to do everything? Because I don't know anything with that gfree... And there is no instruction... Please, help me get the S-On

I have PM'd the author of gfree about an option for SIM re-lock, because that would be useful. I guess you will still need some sort of carrier string which it needs re-locking to though ? Would be handy if perhaps gfree told you what that was before you unlocked it.

Im in the same boat as niiceg, I cannot find my backup and have had no luck in my searchs. Any Idea's what I can do from here?
Thanks in advance..
ps I'm guess my next step is to re root and do
su
cd /data/local
chmod 777 gfree
./gfree -s on
sync
???

bildo said:
Im in the same boat as niiceg, I cannot find my backup and have had no luck in my searchs. Any Idea's what I can do from here?
Thanks in advance..
ps I'm guess my next step is to re root and do
su
cd /data/local
chmod 777 gfree
./gfree -s on
sync
Click to expand...
Click to collapse
Yes, you just need to run "gfree -s on" as root to go from radio S-OFF to S-ON, no need to find/restore that backup.

[Q] Have I managed Perm Root with this much ease? Visionary+ Question

About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?

Arconaught said:
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Click to expand...
Click to collapse
Having the SuperUser icon just means the app is installed, open up terminal and type 'su' to see if it throws up any errors
Sent from my HTC Vision using XDA App

I should have mentioned that I did that and got the # symbol, am I good to go?

Arconaught said:
I should have mentioned that I did that and got the # symbol, am I good to go?
Click to expand...
Click to collapse
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Sent from my HTC Vision using XDA App

OriginalGabriel said:
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Click to expand...
Click to collapse
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).

redpoint73 said:
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
Click to expand...
Click to collapse
This is my understanding as well, though I'd probably still use GFREE to get S-OFF if I were OP.

That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.

Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
I used the wiki method myself, those that used other methods (like Visionary) and were told to root via the wiki seem to have all just started at the beginning, from what I've read.
Sent from my HTC Vision using XDA App

Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
Whoa the Wiki method is completely different, looks like it was rewritten on 04/01.
You can completely ignore the temp rooting steps and concentrate on the gfree steps
From the "Necessary Files" section you need gfree, flash_image and ClockWorkMod Recovery
I would use the latest ClockWorkMod recovery rather than the one listed on the Wiki:
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img (of course it's only the latest as of the time of this writing)
From step 2 you need to use:
Code:
$ adb push gfree /data/local/tmp/
$ adb push flash_image /data/local/tmp/
From step 2.a you need to use:
Code:
$ adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
Again note that the file name for CWM will depend on the version of CWM you are using.
Skip to step 4.b you need to use:
Code:
# cd /data/local/tmp
# ./gfree -f
# ./flash_image recovery recovery.img
# sync
Continue on as normal from here.
I skipped the temp root and perm root sections as you are already perm root.
I also skipped the ENG HBOOT parts, since that's not strictly necessary and the most risky part of the whole process (one mistake can result in a brick). If you want to flash the ENG HBOOT you would need to follow steps 4.a instead of 4.b, (you would also need the necessary HBOOT of course) the only command you need to omit from 4.a or 4.b is "# ./root_psn" which is the script which establishes permanent root.

Thanks a lot so far man, but I'm still stuck. I have adb, when I open it in the SDK, it flows for a bit, then closes. This is right, right? I'm meant to do all of these prompts via the cmd window?

OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.

Arconaught said:
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Click to expand...
Click to collapse
You say you've sorted adb, but can you be more specific please ? What works and what doesn't work exactly ?

Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?

There is a great write up here about getting adb working. It sounds like either you didn't set up a "path" to use those commands anywhere or if you don't want to do that make sure your files are in the same folder as your adb.
Sent from my HTC Vision using XDA App

Arconaught said:
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
Click to expand...
Click to collapse
You need to have the files (extracted from the ZIP files you downloaded) in the same folder you run the ADB commands, if your ADB is in your path you should be able to run ADB commands from any folder.
To summarize you need to extract all the zips you downloaded under necessary files, all to the same folder. The open a command prompt and CD to that folder before you start using your adb push commands.

shortlived said:
There is a great write up here about getting adb working.
Click to expand...
Click to collapse
Yeah, steviewevie wrote it:
http://forum.xda-developers.com/showthread.php?t=865685
But it looks like he is willing to give the OP some personalized help.

Right, thanks guys, I think I'm making some progress.
ADB is all set up, and as far as I'm aware, having:
program files > android sdk > platform tools
on my path should mean I can open adb from anywhere right? I have all of the extracted files in platform tools, where adb is, in my program files... is this right, or have I completely missed the point here?
I keep getting "cannot stat 'gfree':: No such file or directory"
Sorry, I seem really stupid concerning this whole thing, but I'm sure it's something equally obvious that I'm just not seeing.

New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?

Arconaught said:
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Click to expand...
Click to collapse
Remember you are running those commands (everything in that section) from an ADB shell, not from the Windows command prompt.

Excuse my ignorance, but what exactly do you mean by that? What should I do?

Really need help. hboot install went wrong

well the story is ive rooted the phone ages ago and i just tryed installing hboot.
when i was in the fast boot menu i always saw hboot in the titles up the top where s-off was and my radio.
well i tryed to install hboot using the terminal emulator method and i checked my MD5sums they all matched but when i turned the phone off it takes like 5 minutes to show the htc logo and it vibrates at the same time for 5 minutes or more then stops vibrating stays on the htc logo for a minute or 2 then goes to my roms boot screen and that i think is about normal boot time. it boots fine into my rom i can use it as normal.
but i cant use my 4EXT recovery or my fastboot or bootloader whatever its called.
i really need help im kicking myself for trying to install hboot just to try install a new radio so any help or suggestion would be great.
plus i originally rooted the phone using the hackkit method and i was thinking of going back to stock but because my fastboot/bootlaoder dosnt want to show i dunno what to do
im not much of a wizz at these things but i try my best

Can you boot into recovery from the rom?
Sent from a dream.

I dont think so i tried to get rom manager to boot into recovery and same with just holding the power botton and choosing it that way but i dont think it worked
Sent from my HTC Desire HD With Beats Audio using XDA

Don't think it worked? I'll take that as a no.
Link me to what you did, the hboot thing.
Sent from a dream.

kyaldearing said:
I dont think so i tried to get rom manager to boot into recovery and same with just holding the power botton and choosing it that way but i dont think it worked
Sent from my HTC Desire HD With Beats Audio using XDA
Click to expand...
Click to collapse
OK either you know it did not work or it did work which one is it. The I think it did not work just tells me you did not try it.
Sent from my Desire HD using xda premium

Im dont think it worked cause i waited 10 minutes and nothing happened so i took the battery out
and here is the link to what i did and used forum.xda-developers.com/showthread.php?t=841076
Sent from my HTC Desire HD With Beats Audio using XDA

I skimmed through the page you sent, and I do think it's fixeable. You just need to find someone more knowledgeable than myself. I don't want to recommend anything that could make things worse.
With that said, no idea what the hboot does, where it shows up and so forth. If you care to explain, maybe we can figure something out or, until someone who knows more joins in.
For the meantime, good luck.
Edit: I'm assuming hboot is the white screen before booting, which comes with the hack kit once rooted. Don't know why you wantedbto flash it again.....?
Sent from a dream.

I was going to put it back to stock.
And if no one else joins in then what should i do. If you have ideas please tell im not gonna go racing to try because whats happened but i can always keep them at the back of my mind
Sent from my HTC Desire HD With Beats Audio using XDA

Yeah you messed messed up boot loader. Flashing the eng boot on newer dhds causes issues. Here are some steps to fix it that had worked for others. Also you might want to stop in the ace hack kit irc room. They have actually helped quite a lot of people with this even though its not aahk related. Bunch of nice people there.
Note: All md5sums must be 2a28dcd53ea26504be9a86572a348aa1
let the phone fully boot. This may take 1/2 hour, and may vibrate like mad for a few minutes.
download http://tinyurl.com/6fkvepx
unzip PD98IMG-HBFX.zip to a folder you can get to from command prompt or terminal
get psneuter and gfree from hack kit, put in same folder as hboot.nb0 open command prompt and navigate to this folder
turn on usb debugging
Enter the following into the command prompt:
adb push hboot.nb0 /data/local/tmp/hboot.nb0
md5sum /data/local/tmp/hboot.nb0
adb push gfree /data/local/tmp/gfree
adb push psneuter /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/gfree
adb shell chmod 777 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter
adb shell
(should have #)
/data/local/tmp/gfree -f
md5sum /data/local/tmp/hboot.nb0
dd if=/data/local/tmp/hboot.nb0 of=/dev/block/mmcblk0p18
sync
dd if=/dev/block/mmcblk0p18 of=/data/local/tmp/hboot.test
exit
adb pull /data/local/tmp/hboot.test
md5sum hboot.test
adb shell md5sum /dev/block/mmcblk0p18
adb reboot
Note: All md5sums must be 2a28dcd53ea26504be9a86572a348aa1

marsdta said:
Yeah you messed messed up boot loader. Flashing the eng boot on newer dhds causes issues. Here are some steps to fix it that had worked for others. Also you might want to stop in the ace hack kit irc room. They have actually helped quite a lot of people with this even though its not aahk related. Bunch of nice people there.
Note: All md5sums must be 2a28dcd53ea26504be9a86572a348aa1
let the phone fully boot. This may take 1/2 hour, and may vibrate like mad for a few minutes.
download http://tinyurl.com/6fkvepx
unzip PD98IMG-HBFX.zip to a folder you can get to from command prompt or terminal
get psneuter and gfree from hack kit, put in same folder as hboot.nb0 open command prompt and navigate to this folder
turn on usb debugging
Enter the following into the command prompt:
adb push hboot.nb0 /data/local/tmp/hboot.nb0
md5sum /data/local/tmp/hboot.nb0
adb push gfree /data/local/tmp/gfree
adb push psneuter /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/gfree
adb shell chmod 777 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter
adb shell
(should have #)
/data/local/tmp/gfree -f
md5sum /data/local/tmp/hboot.nb0
dd if=/data/local/tmp/hboot.nb0 of=/dev/block/mmcblk0p18
sync
dd if=/dev/block/mmcblk0p18 of=/data/local/tmp/hboot.test
exit
adb pull /data/local/tmp/hboot.test
md5sum hboot.test
adb shell md5sum /dev/block/mmcblk0p18
adb reboot
Note: All md5sums must be 2a28dcd53ea26504be9a86572a348aa1
Click to expand...
Click to collapse
I tryed to boot into recovery and it worked took a while but happened and im not a wizz with this so i kinda need a nood version of this method and what its a complete boot
Sent from my HTC Desire HD With Beats Audio using XDA

kyaldearing said:
I tryed to boot into recovery and it worked took a while but happened and im not a wizz with this so i kinda need a nood version of this method and what its a complete boot
Sent from my HTC Desire HD With Beats Audio using XDA
Click to expand...
Click to collapse
Boot is when you power on the cellphone and it goes into your rom.
Sent from a dream.

Teichopsia said:
Boot is when you power on the cellphone and it goes into your rom.
Sent from a dream.
Click to expand...
Click to collapse
ok thank you

thank you so much this method worked perfectly and im so happy my phones back to normal

kyaldearing said:
thank you so much this method worked perfectly and im so happy my phones back to normal
Click to expand...
Click to collapse
Which OS are u using on ur computer.....and when i try the above method the first command is executed nothing happens..help??

waleedbutt256 said:
Which OS are u using on ur computer.....and when i try the above method the first command is executed nothing happens..help??
Click to expand...
Click to collapse
Lol continue writing until there's action, some of the commands don't bring back a report of whats happened. After each command wait like 5/10 seconds just to make sure.

waleedbutt256 said:
Which OS are u using on ur computer.....and when i try the above method the first command is executed nothing happens..help??
Click to expand...
Click to collapse
Im using Windows 7, make sure you have all your ABD drivers and phone drivers installed