[G2 and Desire Z Q&A, Help & Troubleshooting] kenanibeze:
is my phone bricked?

hello please i need your help i think i have screwed up my htc, i was trying to run the permanent root by strawmental, after running the sequence the phone could not boot again, it stuck at the white background with htc logo.

How can i boot it back to life.

The S is off

h.boot now is 0.76.2000 (PC1011000)

MICROP 0425

CID 11111111

OS 1.34.405.5

this is d cmd log of the permanent root

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Patrolscsn>cd C:\platform-tools

C:\platform-tools>adb devices

List of devices attached

SH0B1RT02382 device

C:\platform-tools>adb push psneuter /data/local/tmp/

1453 KB/s (557962 bytes in 0.375s)

C:\platform-tools>adb push gfree /data/local/tmp/

1357 KB/s (716548 bytes in 0.515s)

C:\platform-tools>adb push busybox /data/local/tmp/

1468 KB/s (1926944 bytes in 1.281s)

C:\platform-tools>adb push hboot-eng.img /data/local/tmp/

1456 KB/s (1048576 bytes in 0.703s)

C:\platform-tools>adb push root_psn /data/local/tmp/

0 KB/s (564 bytes in 1.000s)

C:\platform-tools>adb push su /sdcard/

109 KB/s (26264 bytes in 0.234s)

C:\platform-tools>adb push Superuser.apk /sdcard/

1535 KB/s (196521 bytes in 0.125s)

C:\platform-tools>adb shell chmod 755 /data/local/tmp/*

C:\platform-tools>adb push recovery-clockwork-5.0.2.7-vision.img /data/local/tmp

/recovery.img

1479 KB/s (3739648 bytes in 2.468s)

C:\platform-tools>adb shell /data/local/tmp/psneuter

property service neutered.

killing adbd. (should restart in a second or two)

C:\platform-tools>adb shell

# cd /data/local/tmp

cd /data/local/tmp

# ./busybox md5sum /dev/block/mmcb1k0p18

./busybox md5sum /dev/block/mmcb1k0p18

md5sum: can't open '/dev/block/mmcb1k0p18': No such file or directory

# ./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-gd2764ed

New .modinfo section size: 204

Attempting to power cycle eMMC... OK.

Write protect was successfully disabled.

Searching for mmc_blk_issue_rq symbol...

- Address: c02a6a54, type: t, name: mmc_blk_issue_rq, module: N/A

Kernel map base: 0xc02a6000

Kernel memory mapped to 0x40002000

Searching for brq filter...

- Address: 0xc02a6a54 + 0x34c

- 0x2a000012 -> 0xea000012

Backing up current partition 18 and installing specified hboot image...

Backing up partition /dev/block/mmcblk0p18 to /sdcard/part18backup-315983571.bin

...

Writing image hboot-eng.img to partition /dev/block/mmcblk0p18 ...

Backing up current partition 21 and installing specified recovery image...

Backing up partition /dev/block/mmcblk0p21 to /sdcard/part21backup-315983571.bin

...

Writing image recovery.img to partition /dev/block/mmcblk0p21 ...

Backing up current partition 7 and patching it...

Backing up partition /dev/block/mmcblk0p7 to /sdcard/part7backup-315983571.bin .

..

patching secu_flag: 0

Done.

# ./root_psn

./root_psn

# sync

sync

# cd /data/local/tmp

cd /data/local/tmp

# ./busybox md5sum hboot-eng.img

./busybox md5sum hboot-eng.img

7669ae12dc2faa10ae555a164980efd0 hboot-eng.img

# ./busybox md5sum /dev/block/mmcb1k0p18

./busybox md5sum /dev/block/mmcb1k0p18

md5sum: can't open '/dev/block/mmcb1k0p18': No such file or directory

#