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!
Hey,
I rooted my phone and installed Clockwork mod recovery earlier. I'd like to unroot it, and remove the files from the phone. May send it back due to hinge issue.
I'm not sure where to start. I used the rage/gfree/ADB method on the wiki. I'm on 1.34.
Thanks!
Just re-flash the stock 1.34 ROM/RUU, then get temp root and run gfree with the necessary options to go back to S-ON.
Sent from my HTC Desire Z
Kaph said:
Hey,
I rooted my phone and installed Clockwork mod recovery earlier. I'd like to unroot it, and remove the files from the phone. May send it back due to hinge issue.
I'm not sure where to start. I used the rage/gfree/ADB method on the wiki. I'm on 1.34.
Thanks!
Click to expand...
Click to collapse
You can follow the guide on the wiki http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock but you can skip the "Install the stock image" part because you still have the stock image.
So just start at "radio S-ON and original CID"
Have fun - Guhl
Like Kaph I'm also trying to return to stock, but when I follow the guide on the wiki I get an error.
After I type in gfree -r /sdcard/part7backup.bin and pressing enter I get the following message:
"Error reading input file."
I'd like to try the other method but I don't know my original CID, is there a way to find that out?
I need to return my phone for warranty so help is much appreciated.
Edit: I've already tried reflashing the ROM, I was always running the stock rom without ota and rooted with rage and gfree.
Yeah I've been trying and I keep getting invalid input file.
Also, is there anyway to revert to stock recovery from Clockwork? I think that's hindering things. Unless that's part of the whole process.
Well after some fun I'm back to S-ON with the stock recovery. I'll try applying the OTA now.
But just a massive thanks to djfoo000 and this thread: http://forum.xda-developers.com/showthread.php?t=909755 as I couldn't get the method on the Wiki to work, but doing it in terminal seems to have done the trick and recovery is now showing S-ON. I also used his recovery.img as the versions matched my phone.
On the bright side I'm now a lot more comfortable with adb/etc heh.
My only other question is will all the gfree files and the like stay on the memory, and if so should I use rm to get rid of them? Or do they get deleted upon reboot?
sorry for what may be a stupid comment but will using the ruu not restore to factory?
The reason i ask is that the wiki has the guide for the tmobile g2 and not desire z?!
I managed to root and install cm7rc1 with the newest radio and when i went back into fastboot, I noticed that S-ON was activated again. did a search and discovered that crazy HTC sets security and somehow i undid my S-OFF. I was going to use the .exploid root method but i can't write to the phone anymore. I think i still have clockworkmod recovery. so am i still rooted? can i even flash an OTA update. any suggestions? thanks.
(update: in my haste i forgot the search, i'll delete this if i find a solution)
To figure out if you still have root you can go into Terminal and type "su" if superuser comes up, you accept and it changes the symbol to a # then you're still root but you may not be S-OFF anymore.
First off if u just rooted it it will still have s on the only way to get soff is wilt the alpharev exploit and only way to lose soff is to reflash the hboot and cm7 does not do that so I think u never had soff unless u did the alpharev
After much reading I think I finally understand. I've been spoiled with the nexus one which obviously doesn't have this problem. This is my wife's phone. I thought that after rooting I would get s-off. Anyway, I guess without s-off I have to always update.zip into clockworkmod recovery to flash a cm rom? I am still unclear how to alpharev. Sounds like I need to burn a utility CD and then the app automatically forces s-off. Will need to read more. Thanks for the replies/help
I can see that more is possible when you s-off but I need to know some things before I look at doing it:
Is it better to start from scratch: i.e unroot, re-root using unrevoked, THEN s-off my phone?
Will any AMOLED WWE RUU be good enough to unroot? (if its beter that i do)
For those of you reading this that have done it, which method do you reccomend? (Virtualbox, CD or whatever)
Thank you for any and all replies, I've already ruined one phone on my contract (i tried to OEM update after rooting stock rom :/) and i REEEEALLY don't wanna have to go thru that again. Honestly any and all tips other than answers to my questions are most welcome!
**Matty Matt**
Was your phone on Orange FW when you got it? If so, you'll need a gold card to flash a non-Orange RUU. If you're OK with this, use this one:
http://www.multiupload.com/LEJCW182AH
I'd say do a nandroid backup of what you've got, go back to stock and reroot then S-OFF and then restore your backup.
As for doing the S-OFF, burn it to a CD and boot PC from the CD
Matty Matt said:
I can see that more is possible when you s-off but I need to know some things before I look at doing it:
Is it better to start from scratch: i.e unroot, re-root using unrevoked, THEN s-off my phone?
Will any AMOLED WWE RUU be good enough to unroot? (if its beter that i do)
For those of you reading this that have done it, which method do you reccomend? (Virtualbox, CD or whatever)
Thank you for any and all replies, I've already ruined one phone on my contract (i tried to OEM update after rooting stock rom :/) and i REEEEALLY don't wanna have to go thru that again. Honestly any and all tips other than answers to my questions are most welcome!
**Matty Matt**
Click to expand...
Click to collapse
1) You won't need to unroot, I S-OFF'd when I was using Oxygen RC1 and it was unaffected.
2) Any WWE RUU should suffice, but you won't need to unroot.
3)CD is by far, far, far the easiest method.
thanks for that, and thanks for the link! I believe there's also a TUT on theunlockr.com that I found with some tips too.
EDIT: thanks Kalavere so at the moment it's CD: 2 USB and Virtualbox: 0 LOL
+1 for not unrooting. In fact have a read of this thread I posted when I was trying to s-off. Never did get to the bottom of it, but it seems something in rooting stock rom and creating a goldcard stopped me from doing it.
Once I flashed a custom rom it was fine!
http://forum.xda-developers.com/showthread.php?t=987739
Yes CD method for sure.
Interesting, so by the looks of things it would save me hassle by not un-rooting! right well I think i'm gonna give this a bash this weekend/tonight depending when i have more time. Keep the advice/experiences coming guys!
It's not the hassle, it's just I prefer to do things properly and I've never had any issues doing it from stock. As said, do a nandroid before you unroot and you'll be good to go back to the ROM you're currently using once you're all done
Here is a fool proof how-to guide from DicsoHero over a MoDaCo, he helped me S-OFF my Desire back in December, it might be of use to you.
DiscoHero said:
AlphaRev 1.5 How To Get S-OFF
I am writing this from memory as I S-OFFed my phone sometime ago but here is how to do it. No responsibility if you brick your phone. This process is dangerous and may brick your phone so if you do not have a good reason to do it or do not know what it is, don't do it! Your phone should be already rooted for this to work.
1. Go to http://alpharev.nl/
2. Download AlphaRev 1.5 HBOOT reflash utility (first download link on the page)
3. Burn to CD / put on USD Stick using UNetbootin / Create VM (CD is the preferred way to do it ... "safer")
4. Boot computer from CD/USB while the phone is DISCONNECTED!
5. When prompted connect phone to computer using USB cable and follow instructions. Phone doesn't have to be in fastboot or anything, the program will reboot your phone for you. There are three steps to the entire process. Once you press enter and aknowledge that the process may brick you phone ... go make tea/coffee as it will take 10-15 minutes. DO NOT DISCONNECT your phone from the computer under any circumstances UNLESS EXPLICITLY TOLD THAT IT IS OK TO DO SO or you WILL BRICK YOUR PHONE!
6. Eventually you will be prompted to press any key to shut down the computer, that your S-OFF was a success and that you can enjoy your phone to the fullest now. Your phone will be in fastboot mode (if I remember correctly or may be rebooted fully). To check if you have S-OFF boot into fastboot and it should say ***AlphaRev*** and your HBOOT should be 0.93.001 now as in the screenshots posted above. Your splash boot image would have also changed (Search XDA for how to change your splash1 as it is doable in a few easy steps with "any" image).
Voila, you have S-OFF. You ROM should remain as is (the process only replaces HBOOT) while your recovery may or may not be there.
Click to expand...
Click to collapse
go back to stock with a RUU.
i tried to S-OFF while running GingerVillain and it didnt work, i thought i bricked my phone since it went past -STEP 3 DONT PULL BATTERY OR YOU WILL BRICK THE DEVICE- and it stopped working so i pulled the battery
then went to stock and rooted and S-OFFed without any problems
well as other replies, don't need to unroot But makes sure that the stock rooted rom you are running the process S-Off is using the folder /data of your system so it's advice not use data2sd or whatever 2sd... more there
I used the usb boot, takes 5 minutes only, rooted stock rom 2.29...
Virtualbox is probably the safest method, but is does take a lot more setup
AmonRa 2.0.1 | PVT4 40000 S-Off Alpharev 1.8| HBoot 0.93.1000 | Radio 5.17.05.08 | LeeDroid 3.0.2 (A2SD) | HTC Desire A8181 | UOT Kitchen Mods
So i called in for the warranty today since my phone's screen has been having some troubles and i need to send it in....I tried flashing to the PC10img.zip from the bootloader but that just ended turning my S-ON and not flashing me to the stock original room(main version is older).So basically im wondering what my options are here...I am able to switch between the CM7 ROM i had and the latest 2.3.3 stock rooted rom i found(which is not good enough since it shows the superuser app, any way to hide this?Can't really download apps since the market crashes for some reason) anyways i'd really rather be able to go to actual stock UNROOTED state but i think i might have messed it up.Anybody know my options here?
Do you have a rom you can boot into at the moment?
If yes, boot into it, and run misc_version to change your version number, so the restore can go through.
Otherwise, flashing the latest OTA should go through without a 'main version is older' error.
-Nipqer
And how exactly do You run misc_number?if it that hex editor process through the pc I tried the commands in terminal emulator and it said something along the lines of permission denied.if you could please direct me to a step by step guide to be able to do this.
http://forum.xda-developers.com/showthread.php?t=1178912
its the second part: Changing Version Number to Allow Downgrade
if i helped you pls use the thanks button (i want to have 10 thanks meter )
EDIT: another guide: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Unrooting_and_Returning_to_Stock