Unable to ROOT Desire Z from 2.2.1?

AlecTaylor

Member
Apr 1, 2011
49
0
6
I want to load a custom ROM on my Desire Z. (finally!)

And I eventually got adb to work.

Now following the guide: Rooting the Vision (G2/DZ) and DHD; I got as far as this step:

4 S-OFF, root and its friends Super-CID, SIM-unlock, engineering hboot, clockwork recovery and root

In the following section we are trying to gain write access to the emmc by power cycling it.

We recommend to install the engineering hboot as part of the gfree procedure.

In the root shell (indicated by the #) that you got in the Temporary root section execute the following commands:

Code:
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img -y recovery.img
# ./root_psn
# sync
Wait a few seconds for the changes to "take".
Before receiving this error:

Code:
# ./gfree -f -b hboot-eng.img -y recovery.img
./gfree -f -b hboot-eng.img -y recovery.img
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
--hboot set. hboot image hboot-eng.img will be installed in partition 18
--recovery set. recovery image recovery.img will be installed in partition 21
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
 - Section[16]: .modinfo
 -- offset: 0x00000a14 (2580)
 -- size: 0x000000cc (204)
Kernel release: 2.6.32.21-g132894e
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
 - Address: c02adc44, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02ad000
Kernel memory mapped to 0x40002000
Searching for brq filter...
 - Address: 0xc02adc44 + 0x34c
 - 0x2a000012 -> 0xea000012
Backing up current partition 18 and installing specified hboot image...
md5sum #1 = 62c0aac0a85f3a0a0cbe364b64c552e6
md5sum #2 = 2ce1bdd5e4c1119ccfcecb938710d742
Backing up partition /dev/block/mmcblk0p18 to /sdcard/part18backup-1363017105.bin ...
Writing image hboot-eng.img to partition /dev/block/mmcblk0p18 ...
md5sum #3 = 62c0aac0a85f3a0a0cbe364b64c552e6
md5sum #3 == md5sum #1 - the hboot image was not installed!
Probably the power cycle of the eMMC failed. Check the messages above.
You might join the IRC channel #G2Root on Freenode for further help!
What should be my next course of action?

Thanks for all suggestions,

Alec Taylor
 
Last edited:

demkantor

Inactive Recognized Contributor
Nov 10, 2011
6,858
3,751
113
mpls
Double check you have the right hboot downloaded and that the md5sum matches, then run the command again. If you still have issues copy and paste your input/output from cmd here

Sent from my Nexus 7 using xda premium
 

demkantor

Inactive Recognized Contributor
Nov 10, 2011
6,858
3,751
113
mpls
Sorry I thought you were just copying and pasting from the guide you were folowing. I guess I was reffuring to the entire root procedure but its no big deal
Its telling you exactly what is happening, phone didn't take the flash of the new engineeging bootloader, probably the emmc didn't cycle, try running command again, if its the same outcome double check your radio version as that can cause this or can you post all info from your hboot screen here

Sent from my SGH-T839 using Tapatalk 2
 

demkantor

Inactive Recognized Contributor
Nov 10, 2011
6,858
3,751
113
mpls
Right down all info on boot loader, you seem to know what to do but you're missing something, possibly need to change radio as gfree will not work with newer ones

Sent from my Nexus 7 using xda premium
 

AlecTaylor

Member
Apr 1, 2011
49
0
6
FYI: Was able to root it finally by upgrading my stock to gingerbread from froyo; then back down to non-stock froyo followed by upgrade to modded Jelly Bean.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone