Develop Bugs

[GUIDE] Perm-root, write access, Clockwork recovery and overclocking on the Desire Z

Edit: This guide is for EXPERIENCED users ONLY! For less experienced users please check UBERROOT easy full Root, S-OFF, SuperCID AND SIM UNLOCK for DZ/G2/DHD inc Voda .
Remember to always read and research before rooting! Discussion can be found starting on post #101 - #118 ~TheRomMistress
__________________________________________​
Please be aware that I am not responsible for any bricks etc. This is playing around with the phone internals, so be careful.
To get full write access to the Desire Z, we now have an Engineering HBOOT which was posted by MrPaveL (Thanks for that!).
To get your device to the engineering hboot stage [this is not full radio S-OFF, but 99% of people won't need radio S-OFF], please follow the guide below.
If you want full Radio S-OFF, SuperCID or want to remove the simlock on your phone, please follow this guide on instead. Once you have full Radio S-OFF you can use any Desire Z HBOOT and still have access to flash ROMs etc.
Credit goes out to scotty2, and all of the wonderful folks at #G2ROOT!
Donate to scotty2 (for root): [email protected] (PayPal)
This guide was derived from the guide for the G2, created by unrevoked512 on http://forum.xda-developers.com/showthread.php?t=833965. Also many thanks to vro25 for improvement suggestions.
You will need the following files:
VISIONary r14
wpthis-Z.ko MD5 c73c5e77c91d306c418983c002b60b93
hboot_7230_0.84.2000_100908.nb0 MD5 2ce1bdd5e4c1119ccfcecb938710d742
Step 1
Download and run VISIONary r14
Leave everything uncheck and click "temp root" now.
Once that's done click "Attempt Permroot Now!"
You now have permaroot.
Step 2
Push the files wpthis-Z.ko and hboot_7230_0.84.2000_100908.nb0 to /data/local/
Note: You might want to verify the MD5 sums, particularly for the hboot file, as if your download was corrupted, the file will brick your phone.
Step 3
Open a terminal on your phone, or open an adb shell from your computer.
Step 4
Code:
$ su
# insmod /data/local/wpthis-Z.ko
Note: make sure your screen is on before doing this as it will raise a root request on your phone (if you haven't previously granted it) - click ok on your phone to grant root.
It should return:
Code:
init_module 'wpthis-Z.ko' failed (Function not implemented)
That is good.
Step 5
FINAL WARNING: THIS STEP COULD SEVERELY DAMAGE YOUR PHONE. USING THE INCORRECT FILE COULD CAUSE IRREPARABLE DAMAGE, MAKING YOUR PHONE NOTHING MORE THAN A BRICK.
That noted, if you would like S-OFF, go ahead and run this command in your terminal.
Code:
# dd if=/data/local/hboot_7230_0.84.2000_100908.nb0 of=/dev/block/mmcblk0p18
Step 6
I think this is optional, but there are controversial opinions at the moment. In any case it will not hurt to run
Code:
# sync
to make absolutely sure everything will be saved.
Now reboot your phone gracefully and check that everything sticks.
Step 7 (optional)
This step is optional, if you want to install Clockwork Recovery.
Download ROM Manager from the market and install Clockwork, telling it that you have an HTC G2 when it asks. It will work without problems on the Desire Z.
Step 8 (optional)
This step is optional if you want to install an overclocked kernel. You might want to do a nandroid backup first, in case you want to go back later (just restore boot).
This overclocked kernel seems to crash the phone after Youtube videos are played in fullscreen. This issue is being investigated, but could take a while to resolve, since HTC hasn't released the actual DZ kernel source...
I have now recompiled the overclocked kernel for the Desire Z (all credit goes again to coolbho3000 for publishing the source!), to get the FM Radio to work as well. To get it to work please follow the guide on http://forum.xda-developers.com/showthread.php?t=834219, but instead of the zImage posted there (which breaks FM Radio on the Desire Z), get the one from http://www.opencodes.org/node/14 . You still need to use the bcm4329.ko file from the other thread. Also note that this will change your kernel version to 2.6.32.17 (instead of 2.6.32.21 stock). Please blame HTC for not releasing the newest kernel source. In any case I have not spotted any disadvantages...
So far I have not spotted any problems with this kernel, but if you do, let me know.
PS Bacon-bits by cyanogen do not fully work on the DZ. It won't boot with that ramdisk and the lights hack seems to fail as well. It is probably safest to wait for a full CM release, but this guide gets you 90% of bacon-bits.

stridger said:
Hi all,
I have just managed to get clockwork recovery work on the Desire Z. It's a bit hacky at the moment, and will probably get much easier in the due course. I am not going to post every little step that you can find out by googling, and please be aware that I am not responsible for any bricks etc. This is playing around with the phone internals, so be careful.
The reason it is this hacky is that we do not have an engineering bootloader for the Desire Z yet.
Download wpthis-Z.ko and wpthis-pre-OTA.ko from
http://content.modaco.net/dropzone/wpthis-Z.ko and
http://unforgiven512.udderweb.com/downloads/wpthis-pre-OTA.ko and put them in /data/local on the phone.
Download newest version of ROM Manager
Disable write protection via wpthis-Z.ko
Flash clockwork recovery from ROM Manager
Reboot into recovery
Make a nandroid backup !!!!!
Mount /data in Clockwork
Use wpthis-pre-OTA.ko in recovery to disable write protection.
You now have a fully working recovery. (note you will need to use wpthis-pre-OTA.ko step everytime you boot into recovery and want to write something from recovery [not needed for nandroid backups])
Click to expand...
Click to collapse
Your a genius dude Keep up the good work
We need quality devs like you to get this party started
JD

As soon as I did this step:
Disable write protection via wpthis-Z.ko
EDIT:
this is exactly what I did:
$ su
# insmod /data/local/wpthis-Z.ko
got this as result: failed (Function not implemented)
then all applications stopped working, ROM Manager crashed as soon as I select G2 from confirmation dialog when trying to flash Clockwork.
I then tried GMails and got loads of error popups, had to restart phone to get back to normal
EDIT: I do have Visionary installed set to Root on boot.

schriss said:
As soon as I did this step:
Disable write protection via wpthis-Z.ko
EDIT:
this is exactly what I did:
$ su
# insmod /data/local/wpthis-Z.ko
got this as result: failed (Function not implemented)
then all applications stopped working, ROM Manager crashed as soon as I select G2 from confirmation dialog when trying to flash Clockwork.
I then tried GMails and got loads of error popups, had to restart phone to get back to normal
EDIT: I do have Visionary installed set to Root on boot.
Click to expand...
Click to collapse
I urge you not to do anything in this direction, if you haven't even got permroot yet. Look at the G2 permroot forums, where all of these things are answered. The error is supposed to appear. Please be very careful if you don't want to end up with a brick.

I was afraid to do the G2 permanent root because it involved dd command and some G2 HBOOT file. There was one Desire Z user who ended up stuck in bootloader and have seen no other desire Z owners confirming this to work.
I guess I wait...
Sent from Desire Z

I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?

schriss said:
I was afraid to do the G2 permanent root because it involved dd command and some G2 HBOOT file. There was one Desire Z user who ended up stuck in bootloader and have seen no other desire Z owners confirming this to work.
Click to expand...
Click to collapse
You don't need the eng hboot to get permroot... You just need to temproot with write-protection disabled. But as you say, it's best to wait until the right tools come out.

stridger said:
You don't need the eng hboot to get permroot... You just need to temproot with write-protection disabled. But as you say, it's best to wait until the right tools come out.
Click to expand...
Click to collapse
Exactly, that's what the logic sugests.
I was hoping to:
Temp root with Visionary (already done)
Disable write protection via wpthis-Z.ko
then try "sync" command to write changes.
Then, after reboot, I should have perm root and nand on read-only.
But I got scared by the errors I got after I disabled write protection.

g1junky said:
I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?
Click to expand...
Click to collapse
amazing,
thanks for reporting,
good news

g1junky said:
I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?
Click to expand...
Click to collapse
You've probably still got a G2 hboot, right ? Like the G2 eng hboot ? If so, then it's still really a G2 running a Desire Z ROM. But I can't answer your main question, I'm sure someone else will be able to though.

g1junky said:
I flashed the desire z rom on my g2 yesterday after root, is my g2 now considered a desire z? if so it should be okay for me to follow these instructions right?
Click to expand...
Click to collapse
No, your phone still has the G2 partition layout, so none of this is probably needed for you as your bootloader should already show S-OFF...

I have a g2 so most of this doesnt pertain to me, but as im trying to help someone currently stuck in a hard place thought maybe u could help.
My question has to do with after clockwork is installed. Why do u have to run wpthis.ko in recovery. Shouldnt wp be turned off in recovery? thats how the phone updates stock.

fastludeh22 said:
I have a g2 so most of this doesnt pertain to me, but as im trying to help someone currently stuck in a hard place thought maybe u could help.
My question has to do with after clockwork is installed. Why do u have to run wpthis.ko in recovery. Shouldnt wp be turned off in recovery? thats how the phone updates stock.
Click to expand...
Click to collapse
I just tested doing a nand restore without using wpthis-Z.ko and it *seems* to be working. I haven't flashed anything yet so i can't be sure but it seems like it worked

Sphaerophoria said:
I just tested doing a nand restore without using wpthis-Z.ko and it *seems* to be working. I haven't flashed anything yet so i can't be sure but it seems like it worked
Click to expand...
Click to collapse
Well, for me it was able to flash system, but not boot. My guess would be hboot wouldn't work either. [Obviously it won't return an error... It will think it had written, when in fact it hadn't.]
As for the post before that, the fact that stock recovery can flash images says nothing about other recoveries being able to do the same. Stock recovery could disable wp for example.
In any case it would be nice to have permanent write-access...

stridger said:
Well, for me it was able to flash system, but not boot. My guess would be hboot wouldn't work either. [Obviously it won't return an error... It will think it had written, when in fact it hadn't.]
As for the post before that, the fact that stock recovery can flash images says nothing about other recoveries being able to do the same. Stock recovery could disable wp for example.
In any case it would be nice to have permanent write-access...
Click to expand...
Click to collapse
Dont take this as arguement, cause as ive said i dont have a z, just going by what ive thought to be right. With that being said, the fact that wp is off in stock recovery does say something. The bootloader is what sets wp on/off so if the bootloader is loading the recovery(which it thinks is stock) wp SHOULD be off. i guess a good way to test would be after a nandroid, flash a zip thats only a boot.img and see if it takes.
Heres another question then, what about using the g2 eng recovery?

stridger said:
No, your phone still has the G2 partition layout, so none of this is probably needed for you as your bootloader should already show S-OFF...
Click to expand...
Click to collapse
i tried the G2 method for obtaining clockwork and it didn't work it says it flashed from the app but when i try to backup rom im still on the stock recovery.. would u recommend i try the D-Z method?

fastludeh22 said:
Dont take this as arguement, cause as ive said i dont have a z, just going by what ive thought to be right. With that being said, the fact that wp is off in stock recovery does say something. The bootloader is what sets wp on/off so if the bootloader is loading the recovery(which it thinks is stock) wp SHOULD be off. i guess a good way to test would be after a nandroid, flash a zip thats only a boot.img and see if it takes.
Heres another question then, what about using the g2 eng recovery?
Click to expand...
Click to collapse
wp is definately off in recovery but the problem is probably "your update-binary or updater-script (don't use update-script)" in koush's own words. Anyways i hope we find a way around this soon

FYI: Method updated to reflect the fact that we now have an ENG hboot.

stridger said:
Follow G2 guide on http://forum.xda-developers.com/showthread.php?t=833965, but instead of wpthis-*.ko use the file http://content.modaco.net/dropzone/wpthis-Z.ko. ALSO DO NOT FLASH THE hboot-eng.img INSTEAD USE THE FILE ON http://www.multiupload.com/4U9P14R86Y. IF YOU FLASH THE WRONG FILE IT COULD POTENTIALLY BRICK YOUR DEVICE! .
Click to expand...
Click to collapse
Good work.
Just a suggestion, but I think it would be a lot clearer if, instead of two lots of "follow this except don't do this bit", you were to copy out the whole procedure and change those two bits appropriately ?
Just trying to help minimise the chances of bricks.

steviewevie said:
Good work.
Just a suggestion, but I think it would be a lot clearer if, instead of two lots of "follow this except don't do this bit", you were to copy out the whole procedure and change those two bits appropriately ?
Just trying to help minimise the chances of bricks.
Click to expand...
Click to collapse
Yes, I agree and would like to do that, but wanted to ask unforgiven512 first to integrate it into his guide, as it seems to much overhead to maintain two guides of essentially the same procedure...
Now both devices have a fully working eng bootloader, we really need to merge these two forums into an "HTC VISION" one!

[Q] Visionary broke my Tmobile G2 phone - PLEASE HELP !!

I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38

boyfrom75 said:
I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38
Click to expand...
Click to collapse
Try the following link:
http://forum.xda-developers.com/showthread.php?t=842495

I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?

boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
1) Just to clarify: VISIONary is a complete fail. Root using the rage method, then you can actually control what's happening to your device.
2) Did you ever flash clockwordmod recovery?
If you can boot into clockwork recovery you just need to flash another ROM.

Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.

tehseano said:
Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.
Click to expand...
Click to collapse
this guy is obviously new cut him some slack.....
just follow the instruction on the link carefully
idk why people are having trouble with VISONary i used it to root my phone n it worked....
im new on the forums but i know a thing or two about rooting

That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom

boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
Ok, this is a snip from the link in the second post, it sounds like your are stuck in a boot loop with s-on, if so then this part is the part you need to try:
"*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on."
So now you are gonna have to install Andriod SDK to your computer and the drivers for the G2, there is gonna be a lot of reading and some downloading on your part to do this. Next your gonna have to download cwm recovery.img and wpthis.ko in your sdk folder and then follow the instructions above to recover your phone. Unfortunatly there is no one click fix. Its gonna take a lot of reading and understanding to do this on your part. Gonna have to learn to use ADB there a guide for that and run some basic command promts. Im no Dev or anything but I taught myself by doing a lot of reading, watching videos and a lot of searching. Hope you find the will to do it and recover you phone. Plus we are here to help walk you through some of it but your also gonna have to do some leg work to. GOOD LUCK.

I don't think the OP knows what adb is... you gotta do some more reading get over your fear of using your computer to fix your phone. Its really nothing to be afraid of and its not at all complicated.
Sent from my HTC Vision using XDA App

I'm gonna assume he knows what ADB is and if that's the case, your only option is using one of the full updates...from tmobile. It would have to be a new version of course, for your recovery to allow it. Trying reading through thr RUU threads, perhaps something or someone there can help.
Goodluck, and sry.
Sent from my HTC Vision using XDA App

android602 said:
That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom
Click to expand...
Click to collapse
Brah its not even rooted yet
Sent from my T-Mobile G2 using XDA App

Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying

omarsalmin said:
Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying
Click to expand...
Click to collapse
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).

blackknightavalon said:
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).
Click to expand...
Click to collapse
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.

omarsalmin said:
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.
Click to expand...
Click to collapse
actually all the older guides (including the one I used to root my phone) said you ran perma root first then do s-off.
the perma root method in visionary was made before we even had s-off (only like a day before, but still before).
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.

Lennyuk said:
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.
Click to expand...
Click to collapse
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).

steviewevie said:
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).
Click to expand...
Click to collapse
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
I have a feeling the perma root process is corrupting roms on newer devices, not sure on the why though.

Lennyuk said:
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
Click to expand...
Click to collapse
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.

steviewevie said:
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.
Click to expand...
Click to collapse
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.

Lennyuk said:
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.
Click to expand...
Click to collapse
Sorry you took it that I was asking you to prove yourself. I wasn't, I was just asking for information, because I'm interested in the subject.
I'd seen those threads but do you know for certain they didn't try Visionary first, find it didn't work properly, then try rage ?
I could of course be wrong, but I don't see how rage can cause corruption because it doesn't do a lot, it just fires up a bunch of processes to exploit a way to get root. It's so much simpler than Visionary, which does a whole load of RAM disk stuff and other things that could be more risky if it goes wrong.
I suspect in those two cases that something else had already messed with their phones to cause the boot problem.

Too many root guides!!

I am finally getting my phone today and will be rooting/unlocking before I even turn the damn thing on becuase I live in israel.
My only problem is that I can't seem to find a guide that uses Rage AND gFREE. Everything I see uses gfree and visionary or Rage and the wpthis files...
All I need it someone to outline step by step what I would need to do, I already have the gfree and rage files downloaded.

Relax brother, the g2 is one of the easiest to root...I just did mine and it was a piece of cake...just go to the sticcky thread with all the reference links and go to the g2 wiki and follow that guide, its the most uptodate and uses rage and gfree...
_BMFC
Sent from my HTC Glacier using XDA App

The only "guide" you should pay attention to is the WIKI. See the button at the top of the page? Go there.

I do warn you though, VISIONary is a pain and often things go wrong.
Rage is your safest bet, and it's not at all hard...

Follow the WIKI

+1 for the Wiki. It's the most up to date one.

i'm not sure the wiki technique works with the latest bell desire z baseband version:
12.28b.60.140eU_26.03.02.26_M
i wasn't able to get visionary or gfree temp root to work.

superspacey said:
i'm not sure the wiki technique works with the latest bell desire z baseband version:
12.28b.60.140eU_26.03.02.26_M
i wasn't able to get visionary or gfree temp root to work.
Click to expand...
Click to collapse
That baseband/radio is the one from the stock European DZ's, and that worked fine with gfree for me.
gfree is incompatible with some kernels though, see the gfree thread for more details.
What problem did you have exactly ?

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.
Click to expand...
Click to collapse
When I run rage, I never get the msg saying Forked... and then my android terminal emulator automatically closes, i see the HTC splash screen and it almost looks like my photo completely reboots but there is no start up sound. but upon reset if i go back into the terminal, i'm still a regular user.
I've got the following on my vanilla Bell North American Desire Z.
Baseband version
12.28b.60.140eU_26.03.02.26_M
Kernel version
2.6.32.21-gd2764ed
[email protected] #1
Tue Oct 26
Build number/Software number
1.34.666.5

As a side note I recommend running verify before running gfree to get the original CID. I did this on my European DZ and I am glad I did as the superCID would not allow me to connect to my net op until I set it back to the original CID.
This saved me from having to do a restore from the backup.

superspacey said:
When I run rage, I never get the msg saying Forked... and then my android terminal emulator automatically closes, i see the HTC splash screen and it almost looks like my photo completely reboots but there is no start up sound. but upon reset if i go back into the terminal, i'm still a regular user.
Click to expand...
Click to collapse
That's odd. If you end up running rage twice, by accident, then the phone will automatically reboot in the way you describe, I wonder if that's what has happened somehow ? e.g. if perhaps you typed something wrong with the adb push instructions and got the rage program copied over twice ?
I would double-check everything and make sure it looks like you have the correct files (e.g. file sizes) pushed over ok.
Do you get a bunch of other messages from rage ? It puts out several lines of output and then you have to wait several seconds until you get the "forked" message.

yeah i got other stuff printed out prior to the expected forked message...
in any case, i repeated all the steps from another computer and behold, it all worked. rooted, s off and cid to 11111111.
so i probably just borked something up the first time thanks

[Q] Best Way to Root G2 Gingerbread 2.3.4

I've been trying to root this G2 I recently got and I'm kind of stuck. It's competely stock running 2.3.4 Android. I was wondering what is the best way to root it,get the Security off etc etc. I've tried many of the ways listed but none help me.
Do I really need to downgrade etc? I've used ADB to root the MyTouch Slide 3G and the Nexus S 4G, Could someone help point me in a better direction I think I might be reading something wrong or looking at the wrong threads.

DudeNo said:
I've been trying to root this G2 I recently got and I'm kind of stuck. It's competely stock running 2.3.4 Android. I was wondering what is the best way to root it,get the Security off etc etc. I've tried many of the ways listed but none help me.
Do I really need to downgrade etc? I've used ADB to root the MyTouch Slide 3G and the Nexus S 4G, Could someone help point me in a better direction I think I might be reading something wrong or looking at the wrong threads.
Click to expand...
Click to collapse
The safest way to root is by using the guide in the wiki: http://forum.xda-developers.com/wiki/HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my HTC Vision using XDA App

+1 on wiki guide!

DudeNo said:
I've been trying to root this G2 I recently got and I'm kind of stuck. It's competely stock running 2.3.4 Android. I was wondering what is the best way to root it,get the Security off etc etc. I've tried many of the ways listed but none help me.
Do I really need to downgrade etc? I've used ADB to root the MyTouch Slide 3G and the Nexus S 4G, Could someone help point me in a better direction I think I might be reading something wrong or looking at the wrong threads.
Click to expand...
Click to collapse
Yup you do need to downgrade, as currently you can only temp-root OTA GB. It unroots when you reboot your phone, and that's why the downgrading starts at temp root. Downgrade to 2.1, where a perm root is available, then flash a PRE-rooted GB if stock GB is important to you

Thanks guys. I had another question, They say look for the INFOCID, Where do I find that at? Because they don't really show a picture of it or explain how exactly to get it? Or do I not neeed to do that since I'm using a T-Mobile G2?

I remember seeing it when rooting. One of the rooting steps would print out lots of text on your command prompt. Just scroll around and you'll find it.
Found it :
Code:
cd C:\android-sdk-windows\platform-tools
adb reboot bootloader
fastboot oem boot
Just scroll through the output and you'll find it
Sent from pure meXdroidRom!!

You shouldn't need to know the cid seeing as all G2's have the same cid. (TMOB_010 or something like that for anyone wondering)
-Nipqer

Nipqer said:
You shouldn't need to know the cid seeing as all G2's have the same cid. (TMOB_010 or something like that for anyone wondering)
-Nipqer
Click to expand...
Click to collapse
I was just asking as they are asking about a Goldcard method and I was trying to figure out if I needed to follow that or not. This whole down-grading method is slightly confusing for me. Would you guys be able to help me locate a video showing someone doing it?

A goldcard is needed. Process goes goldcard, temp root, downgrade, perm root then flashing a new ROM. Just follow the guides and you'll be fine don't worry
Sent from pure meXdroidRom!!

ArmedandDangerous said:
A goldcard is needed. Process goes goldcard, temp root, downgrade, perm root then flashing a new ROM. Just follow the guides and you'll be fine don't worry
Sent from pure meXdroidRom!!
Click to expand...
Click to collapse
Thanks for the help lolz. That might be why I can't do anything. I generally just browsed over anything Goldcard, Cause all my other Androids used just ADB to push the files or I just had to flash stuff ah

Haha alright. If you still need help I might make a video this weekend as a guide.
Sent from pure meXdroidRom!!

ArmedandDangerous said:
A goldcard is needed. Process goes goldcard, temp root, downgrade, perm root then flashing a new ROM. Just follow the guides and you'll be fine don't worry
Sent from pure meXdroidRom!!
Click to expand...
Click to collapse
um no, G2's do not need goldcards.
G2's are only available from T-Mobile and thus all have the same cid.
A Goldcard is only neccesary if you are trying to flash an official PC10IMG that doesn't match the cid.
-Nipqer

Did not know that, as I'm using a Desire Z~
Sent from pure meXdroidRom!!

C:\AndroidSDK\platform-tools>adb shell chmod 777 /data/local
C:\AndroidSDK\platform-tools>adb shell chmod 777 /data/local
C:\AndroidSDK\platform-tools>adb shell /data/local/tmp/psneu
Failed to set prot mask (Inappropriate ioctl for device)
C:\AndroidSDK\platform-tools>adb shell /data/local/tmp/psneu
Failed to set prot mask (Inappropriate ioctl for device)
I'm doing the ADB, Did I do something wrong here?

Use this guide http://forum.xda-developers.com/showthread.php?t=1178912
psneuter does not work on gingerbread, so we need to use fre3vo
-Nipqer

Nipqer said:
Use this guide http://forum.xda-developers.com/showthread.php?t=1178912
psneuter does not work on gingerbread, so we need to use fre3vo
-Nipqer
Click to expand...
Click to collapse
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure
An invalid argument was passed
An error has occured.
$
Is there a way to fix this? I'm typing in the commands they list. An also thanks for the help you've given me so far man.

DudeNo said:
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure
An invalid argument was passed
An error has occured.
$
Is there a way to fix this? I'm typing in the commands they list. An also thanks for the help you've given me so far man.
Click to expand...
Click to collapse
You can actually just copy paste the commands. To paste in command prompt just right click ans paste.
Sent from pure meXdroidRom!!

Thanks for that, I feel dumb now ah wish I would of known you could copy and paste. It's all working now. I'm guessing after I downgrade the 2.3.4 I can officially follow one of the other threads listed and root and start installing roms + Clockwork Recovery?

Best way is to follow the official guide in the wiki here
And stay well away from Visionary.
-Nipqer

All right thanks. I think this is going to be my last question hopefully. I need to just follow all the steps after the Downgrading they talk about correct? I'm not trying to risk bricking this phone cause then I'm phoneless til I can get some spare cash -.-

[Q] Need help S-off my phone

Guys,
I just got a replacement phone from Verizon and need your help to get it S-OFF. I tried both the firewater method and the Rumrunner method. Neither of them worked.
I installed Weaksauce to gain root and tried firewater (method 1) first. after trying all day and night to get it to work. I decided to try Rumrunner with the same result...
Android Version : 4.3
Sence Version: 5.0
Software number: 2.10.605.1
Base 1.12.40.1112-2
Hboot: 1.55.0000
Anything else you guys need from to help me figure out why I can S-OFF?
Thanks!

robramirez007 said:
Guys,
I just got a replacement phone from Verizon and need your help to get it S-OFF. I tried both the firewater method and the Rumrunner method. Neither of them worked.
I installed Weaksauce to gain root and tried firewater (method 1) first. after trying all day and night to get it to work. I decided to try Rumrunner with the same result...
Android Version : 4.3
Sence Version: 5.0
Software number: 2.10.605.1
Base 1.12.40.1112-2
Hboot: 1.55.0000
Anything else you guys need from to help me figure out why I can S-OFF?
Thanks!
Click to expand...
Click to collapse
I don't know much about weaksauce since I haven't had to use it, but for 4.3 the temp root method of firewater is what you use.
Sent from my HTC6500LVW using Tapatalk

After trying different computers and USB cords I was able to use the Weaksauce,Firewater method to S-OFF my phone. Im back in business!

robramirez007 said:
After trying different computers and USB cords I was able to use the Weaksauce,Firewater method to S-OFF my phone. Im back in business!
Click to expand...
Click to collapse
ive tried both ways on my computer.. do you think if i used someone elses computer it would work?

What Operating system are you on? I had win 7 64bit.
uninstall everything phone related HTC Sync, drivers, everything..... install this : http://forum.xda-developers.com/showthread.php?t=2376761 (worked for me)
grab ADB and fastboot from here : http://forum.xda-developers.com/showthread.php?t=2317790
Use weaksauce to gain root and make sure you look at your phone to grant it Superuser access...
and honestly just keep trying. I tried for maybe 50 times before it worked. Switched USB port every time until it worked.

robramirez007 said:
What Operating system are you on? I had win 7 64bit.
uninstall everything phone related HTC Sync, drivers, everything..... install this : http://forum.xda-developers.com/showthread.php?t=2376761 (worked for me)
grab ADB and fastboot from here : http://forum.xda-developers.com/showthread.php?t=2317790
Use weaksauce to gain root and make sure you look at your phone to grant it Superuser access...
and honestly just keep trying. I tried for maybe 50 times before it worked. Switched USB port every time until it worked.
Click to expand...
Click to collapse
Okay I'll try that
Sent from my HTC6500LVW using xda app-developers app

so i reinstalled all drivers and out of the 3 times i tried i got to the second bottle and i switched usb ports each time so at least im getting somewhere haha

[SOLVED]
Here are my thoughts after got it S-off on the second night.
I was having problems with adb disconnecting my device or was it my computer, not sure.
I got to "adb shell", then go into phone and tap the Weaksauce app and tap on "agree", then open SU app and changed the setting to "grant".
The dialog window in SU will still pops up and you hit allow for Superuser. I think this is the reason why it never chugged before here
You have to input the "su" command in the adb window
After "grant" it is able to S-Off, you know it when the promtp windows says " Your device is now S-Off..."
ps. For some reasons Weaksauce is not stable on my phone it does take way too long to root the device and sometimes not even does it.
This may sounds broken to some ppl lol, but this is my first post and first root.
So Cheeers

Congrats. Weaksauce is just a temp root, now that your s-off, you can remove weaksauce, flash a recovery, and then flash superuser thru recovery for full permanent root.

ok

nope still not working.. im thinking that it has to be a problem with disconnecting and then it loses the root cause whenever i restart the phone i have to enable root with weaksauce again.

prichable said:
nope still not working.. im thinking that it has to be a problem with disconnecting and then it loses the root cause whenever i restart the phone i have to enable root with weaksauce again.
Click to expand...
Click to collapse
It should automatically give you root access after you installed weaksauce and SuperSU. It takes maybe 30-60 seconds after it completely boots up.

Okay good to know. it's still not finishing the first bottle though
Sent from my HTC6500LVW using xda app-developers app

prichable said:
Okay good to know. it's still not finishing the first bottle though
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
I have been at this for over a week. I've gotten as far as the 8th bottle but still haven't been able to get S-OFF.
When I first started trying firewater was version 5, now it's up to version 8.
At this point I try it once a day every night(making sure to download the latest firewater each time). I just imagine that sometime it will work.
You can try to talk to beaups in the #firewater IRC channel. He tried helping me before saying "okay Ill try to fix it in the next few days." That was over a week ago but considering he's only getting donations for this I don't hold it against him for it not working instantly for me. Head to the IRC and see if he can help out. Otherwise, I'd say keep trying.

prichable said:
Okay good to know. it's still not finishing the first bottle though
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Did you try manually turn on weaksauce in the phone ?

Yeah I've opened it every time I do an adb reboot
Sent from my HTC6500LVW using xda app-developers app