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!

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

gfree problems

I have a problem rooting a friend's phone using gfree.
When I rooted my phone, I used a different method since it was in the early days of rooting the desire z. I've followed the instructions found here: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Everything seems to work correctly until I execute ./gfree -f
At this point I get the error "Error reading input file" and the phone gets stuck (I have to remove battery to boot it up again).
Anyone has had this problem before? Possible fixes? Any help is appreciated.

Has he done the OTA update??
Edit: @Dan.. Oh yeah... my bad

MacaronyMax said:
Has he done the OTA update??
Click to expand...
Click to collapse
Look at the picture
The # is there.
Which means root.
WHich means rage / VISIONary worked.
He hasn't OTA'd

yea rage seems to have worked, i'm just getting that error at the end and can't proceed with the rooting.

If I'm not mistaking I believe he is rooted.already ( don't flame me if he's not I can't really see the pic on the xda app ....)
tsubus said:
yea rage seems to have worked, i'm just getting that error at the end and can't proceed with the rooting.
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App

unfortunately i am not rooted (i can't even sync after ./gfree -f, gives an i/o error)

tsubus said:
unfortunately i am not rooted (i can't even sync after ./gfree -f, gives an i/o error)
Click to expand...
Click to collapse
You're running as root though (# prompt), so you have at least got temp root even if it isn't permanent.
You're getting an error when it tries to disable the write protection though, so I am guessing it is indeed temp root and you lose it after a reboot.
What ROM/kernel are you running exactly ? Some don't work with gfree.

Am having the exact same problem as Tsubus.
Orginal rom, no updates applied.
details:
Vision PVT SHIP S-ON
HBOOT-0.85.0005
MIRCOP-0425
RADIO-26.03.02.26-M
Did try Visionary, rage and gfree03 without luck

stringbean82 said:
Am having the exact same problem as Tsubus.
Orginal rom, no updates applied.
details:
Vision PVT SHIP S-ON
HBOOT-0.85.0005
MIRCOP-0425
RADIO-26.03.02.26-M
Did try Visionary, rage and gfree03 without luck
Click to expand...
Click to collapse
Which original ROM exactly though ? There are loads.

steviewevie said:
Which original ROM exactly though ? There are loads.
Click to expand...
Click to collapse
Android version 2.2
Kernel 2.6.32.21
Software version 1.34.405.5

stringbean82 said:
Android version 2.2
Kernel 2.6.32.21
Software version 1.34.405.5
Click to expand...
Click to collapse
Hmm, gfree should work fine on that version
What happened with Visionary ? I wonder if Visionary messed things up somehow ?
How much of a pain would it be for you to re-flash the ROM and see if it's happier after that ? (e.g. how difficult to get your data/settings back ?)
Let's see if anyone can come up with another idea.

Am available for any test, been busy for the last 6 hours at work trying to get it to work.

stringbean82 said:
Am available for any test, been busy for the last 6 hours at work trying to get it to work.
Click to expand...
Click to collapse
Well, it should work perfectly with that ROM version. That's the same version that I'm using. If you don't mind re-flashing your ROM (with the same version) it could be worth a try. I am not saying that I think it will definitely fix it, this is a long shot, but I can't think what else to suggest right now.
Edit - have you also tried the older method using the "insmod" command, the one in the threads on rage ? That would be interesting to double-check that the insmod is coming up with the "wrong" error message, similarly showing that it failed to disable the NAND write protection.

doesn't work with this on my friend's phone:
android version 2.2
kernel 2.6.32.21
software number 1.34.166.5
haven't tried visionary, only gfree...might give visionary a try later on if you guys think it could work.

Tomorrow am going to load the same image as i have now on it and then try again.
What is the recommended method?
Sent from my HTC Vision using Tapatalk

tsubus said:
doesn't work with this on my friend's phone:
android version 2.2
kernel 2.6.32.21
software number 1.34.166.5
haven't tried visionary, only gfree...might give visionary a try later on if you guys think it could work.
Click to expand...
Click to collapse
Don't try to perm-root with Visionary it'll soft-brick... Just a warning

alright, thanks for the heads-up.
not sure what i should try now though, it kind of seems like there is no way to root it atm. i guess time will tell.

same problem for me =/

You probably need to push superuser to your phone in a different way. I had a similar problem using gfree. Hold on and I will send you a link to the nook method that I used. You do this after you run rage and are in the root shell on terminal emulator. (Pound symbol at the beginning of the command line). once you push superuser this way it locks in itself. then you can run the ./gfree command hopefully. I never had a problem with that command before I got the proper superuser but it might help you. Wait 1 and I will send the link.
Sent from my HTC Vision using XDA App

http://nookdevs.com/NookColor_Installing_su_and_the_Superuser_app
That should take you to the proper page. Don't run the first command that starts with unzip. Its easier to download the superuser zip to your desktop and then extract it to the root of Your android sdk tools folder. Aka put it in the tools folder and not inside any other folder that might be in your tools folder. Then run the next two commands on adb after you navigate to your androidsdk/tools folder to install. The next commands that you run in your root shell are run with terminal emulator. You should still be in a root shell if you used rage and haven't rebooted your phone. Pound sign will be present. Pm me if you have problems or if you are confused in any way.
Sent from my HTC Vision using XDA App

[Q] Quick question about debranding vodafone Desire Z A7272

I have a vodafone (Australia) branded HTC Desire Z A7272 I want to debrand, here is the specifics from hboot and software about screens
From Hboot
HBOOT-0.85.0010
MICROP-0425
RADIO-26.06.02.27_M
eMMC-boot
Dec 27 2010,22:19:17
From about software screen
Android Version
2.2.1
Baseband version
12.28.h.60.140fU_26.06.02.27_M
Kernel version
2.6.32.21-g132894e
[email protected] #1
Fri Jan 14 13:17:35 CST 2011
Build Number
1.85.861.3 CL331649 release-keys
Software number
1.85.861.3
Browser version
Webkit 3.1
I just want to know if this method
http://forum.xda-developers.com/showthread.php?t=832503
will work with the rom from RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed be safe to use for this phone?
I believe I will need to allow downgrade (part 3 in the guide) As from what I can tell I'd be going from 1.85 to 1.34 is that correct?
After it is done can I use over-the air updates in the generic HTC environment to update? what is the current version for this phone?

I've just tried running dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img from adb and got the error
/dev/block/mmcblk0p17: cannot open for read: Permision denied
Which makes sense because I don't have root and can't use SU to get #
Does that mean I'm going to need to root it before i can debrand it? - I don't know that this version can be rooted. Am I stuck until there is a root method for this software?

check out the G2 forums and work on the guide. the most popular is the gfree method. Hopefully that will help you out.

I ran Visionary+ r14 and the temproot now function won't even work, goes back to the menu and If i open the terminal emulator on the phone SU gives permission denied

I found a guide on cyanogenmod wiki that used misc_version and psneutter to gain temp root and that worked

Debranding worked an I'm now on 1.34, which is android 2.2 - thing is, now the over-the-air updates don't work. I'm not sure why, shouldn't I be able to just update to a higher (non branded) version now?

apopberz said:
I found a guide on cyanogenmod wiki that used misc_version and psneutter to gain temp root and that worked
Click to expand...
Click to collapse
I was just on that site trying to temporarily root my device, it has same software version as yours, from vodafone australia.
it says falied to open backup file after i enter this line
/data/local/tmp/misc_version -s 1.33.405.5 in command prompt
so did you actually root your device succesfully, beein trying but i keep getting permission denials and stuff
can you post me the method you used

Hi all
Definite noob so be easy on me. Just wanted to see if anyone has been successful since? I understand it's been a year, but google is of no help...
I'm with Voda with my HTC Desire Z and tried to gain root (even temp) but to no avail (using http: // wiki. cyanogenmod. com /wiki /HTC_Desire_Z:_Rooting sorry can't externalink because haven't posted enough yet).
I seem to stop somewhere pushing Superuser.apk
Reason for debranding is because I'm so sick of the crap Voda add in there...

for downgrade (u will need to create a goldcard for debranding):
http://forum.xda-developers.com/showthread.php?t=1178912
for permroot:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD

[Q] How To Root

Hey guys
I am totally new to the android phones, and now having a DHD which has the following specs:
Android Ver. 2.2
BaseBand Ver. 12.28b.60.140eU_26.03.02.26_m
Kernel Ver. 2.6.32.21-gf3f553d
Build No. 1.32.405.6
Software No. 1.32.405.6
Now i looked at this link -
and didn't understand if i have to downgrade my DHD as well or is my version old enough so i can skip right ahead to the S-Off and ROOT?
can anyone tell me from what ver., and Ver. of what, do you have to perform downgrading?
thanks.

No need to downgrade.
Use this one:
http://forum.xda-developers.com/showthread.php?t=857537
If u want an ENG bootloader (not needed for custom roms and root, but recommend):
http://forum.xda-developers.com/showthread.php?t=855403
You can brick your phone, be careful!

droreni said:
Hey guys
I am totally new to the android phones, and now having a DHD which has the following specs:
Android Ver. 2.2
BaseBand Ver. 12.28b.60.140eU_26.03.02.26_m
Kernel Ver. 2.6.32.21-gf3f553d
Build No. 1.32.405.6
Software No. 1.32.405.6
Now i looked at this link -
and didn't understand if i have to downgrade my DHD as well or is my version old enough so i can skip right ahead to the S-Off and ROOT?
can anyone tell me from what ver., and Ver. of what, do you have to perform downgrading?
thanks.
Click to expand...
Click to collapse
Yes you can skip the downgrade progress!

Perfect
thanks for the fast reply!

how to root gingerbread
hi everybody,
forgive me if I' writing in the wrong place but for me has been enough difficult to get here..
I'm a rookie android user and I've been flying over the forums for the last three days, I'm really getting crazy.
Here are the specifics of my phone (branded):
android version 2.3.3
kernel version 2.6.35.10-gd2564fb
software number 2.50.405.2
and here's the problem:
I have purchased an AR drone and I'm trying to get it connected so I visited the following link: http://forum.xda-developers.com/showthread.php?t=1072281
seems that the first thing i need is a ROOTED Desire HD . I have tried every thing. Visionary (in different releases installed with ASTRO) seems not to be working. When i select Temproot now, after a while, the screen turns black. I waited for several minutes but nothing happened. So I needed to exit the program selecting "home". At that point it didn't allow me to rerun the app, I needed to reboot the phone to get it working again but no success.
So I tried GINGERBREAK 1.2 but after 25 minutes the rebooting process was still going on and I guessed that something was not working properly (as usual), so I stopped it. I think there is also a problem with Superuser (v 2.3.6.3), infact when I try to update it, it says "an error occurred and su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary" (by the way...sorry for my inexperience, but what does "flash something" mean????).Anyway, my phone doesn't reboot on clockwork recovery.
Moreover, upon opening Rom manager (v4.3.2.4) it tells me that I must root my phone to get it working (of course) and that it cannot find Superuser at "system/bin/su" or "system/xbin/su". Guess what! I don't have such files on my phone.....
At this time i don't know what else I can do, I'm relly frustrated.
Can anyone help me out? keep in mind that if you have any kind of solution, I need some very "plain" explanation like if you were talking to your 5 years old son, please
Thanks

If we update with software number 2.50.405.2 can we root?

No, firmware > 2.37 cannot be rooted.

Thanks for the info, I guess I have to get rid of my AR Drone