Develop Bugs

Need a bit of help

Hey everyone, I'm new here and I finally decided to root my g2. I'm using the cyanogenmod wiki entry. I am at the point where it says to write "./gfree -f -b hboot-eng.img -y recovery.img" though every time I do this it says:
# ./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.17-g814e0a1
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a8d44, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a8000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02a8d44 + 0x34c
- ***WARNING***: Found fuzzy match for brq filter, but conditional branch isn't
. (0xea000012)
Backing up current partition 18 and installing specified hboot image...
Backing up partition /dev/block/mmcblk0p18 to /sdcard/part18backup-1313372731.bi
n ...
Writing image hboot-eng.img to partition /dev/block/mmcblk0p18 ...
Error opening input image.
is this normal? if it helps, I continue on to write
./root_psn
sync
and nothing happens. Thanks ahead of time for any help.

Nevermind. I just went through every step again and it worked.

have i bricked my desire Z?

hello guys
please i need your help i think i have screwed up my htc, i downgraded my desire z 2.33 to 2.2 and 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.
i tryed fix it with recovery boot, but the clockworkmod v5.02.7 is not working, its log shows
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
vision pvt ENG S is off
h.boot now is 0.76.2000 (PC1011000)
MICROP 0425
CID 11111111
OS 1.34.405.5
below is the cmd log
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
#

0.76.2000 > G2
0.84.2000 > DZ
if you have a DZ you have flashed the g2 hboot which is why it wont boot

like pnut said you may be just fine and still just need to flash a rom
can you do anything in recovery from here?
just because that message showed doesnt mean recovery wont work
but if flashing a rom via recovery dosent work try this
download this : http://www.4ext.net/ddl/vision/recovery.zip
this is a version of 4ext recovery to be flashed through fastboot
unzip it and put the image in the same folder as fastboot.exe on your computer
(if you are unfamiliar with fastboot just think of it as adb)
now open a cmd in that directory (easiest way hold shift and right click in that folder)
make sure you have phone plugged in pc and in fastboot mode
now type this into cmd
Code:
fastboot devices
if you see some leters and numbers good, this is your serial number
now type
Code:
fastboot -w
now
Code:
fastboot flash recovery recovery.img
now
Code:
fastboot reboot-bootloader
from here boot into recovery and you should see 4ext recovery now (better than clockwork)
try and flash a rom from recovery now, something known stable like cm7
reboot and see if it all works
if you want sense roms or any other reason you want the dz hboot go here for a better explanation
http://forum.xda-developers.com/showthread.php?t=1728208
good luck

PNuT. said:
0.76.2000 > G2
0.84.2000 > DZ
if you have a DZ you have flashed the g2 hboot which is why it wont boot
Click to expand...
Click to collapse
i just rechecked and you are 100% right.
Please how can i reflash hboot 084.2000?

PNuT. said:
0.76.2000 > G2
0.84.2000 > DZ
if you have a DZ you have flashed the g2 hboot which is why it wont boot
Click to expand...
Click to collapse
i just rechecked and you are 100% right.
Please how can i reflash hboot 084.2000? Is it posible through fastboot

kenanibeze said:
i just rechecked and you are 100% right.
Please how can i reflash hboot 084.2000? Is it posible through fastboot
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27796375
Sent from my HTC Vision using xda premium

demkantor said:
http://forum.xda-developers.com/showthread.php?p=27796375
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
thanks i have booth the phone back to life:victory:
but the gapps(gapps-jb-20120802-signed.zip) i flashed is not working...its like it could not connect. keeps showing sever error
is there any gapps i can flash in. i'm running on Andromadus Mimicry ROM – version 1.5.0

the gapps would be flashed via the aroma installer in mimicry, any google apps not included in the installer would be downloaded from play (maps, gmail, etc) even then you could just use a file explorer to download any .apk from your sdcard or use titanium backup to get any apps back
Sent from my HTC Vision using xda premium

[Q] rooting Desire Z issue

Hi, I'm trying to root my HTC Desire Z in order to put custom ROM on it later, and having some (prolly noob) issue:
Followed the 'ADB for noobs' thread and all ok: http://forum.xda-developers.com/showthread.php?t=865685
Now I'm trying to follow the rooting on this thread: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Stuck on step #4:
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img -y recovery.img
# ./root_psn
# sync
Getting the following:
$ ./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.35.10-g53a84f9
New .modinfo section size: 204
Attempting to power cycle eMMC... Failed.
Module returned an unknown code (Operation not permitted).
Any idea? (highlighted the part which I think is the issue, but don't know how to resolve it )

I get the same thing too
Sent from my T-Mobile G2 using xda app-developers app

so did you successfully downgrade first?
Downgrade and then ROOT
or if easier after downgrade follow The cyanogen Wiki
or many seem to find it easiest to follow STRAWMETALs PDF GUIDE

I said it was a noob issue, Didn't downgrade it :$ , will do that and update. Thanks demkantor

Unable to ROOT Desire Z from 2.2.1?

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".
Click to expand...
Click to collapse
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

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

I have included the input/output from my CMD in the initial post.

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

Also I couldn't get it to work with Gingerbreak or DooMLoRD's Easy Rooting Toolkit either.

*bump*

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

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.

Can't Flash GApps (UNLOCKED, S-On, HBOOT-0.82.0009, TWRP 2.6.3.0)

I just flashed PureKat V4 on this HTC G2 and I'm having trouble getting GApps on here. I got the rom working with S-On by flashing it in TWRP, then extracting it on my PC and doing fastboot flash boot boot.img. The problem is I cannot flash GApps. I've been trying to do it via sideload in TWRP. There is over 1 GB of space, so far more than enough. I've been using the pico and nano 4.4.x packages plus both the regular and "small" Cyanogenmod GApps packages for CM11.
For nano and CM11 regular GApps, it says:
Code:
Insufficient storage space available in
System partition. You may want to use a
smaller GApps (i.e. Mini Modular GApps)
or remove some apps using gapps-config.
For pico and CM11 "small" GApps it says:
Code:
E: Could not create file for updater extract in '
I'm not sure what it says after the apostrophe because that is the edge of the screen.
The only thing I could think of is S-On, so I tried to S-Off using the "new gfree" method, ie.
Code:
[email protected]:/data/local/tmp # ./gfree -f -b hboot-eng.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
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: 3.0.101-cyanogenmod-g9eb87bf
New .modinfo section size: 212
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: 00000000, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0x00000000
Failed to open /dev/kmem: No such file or directory trying /dev/gkmem
Failed to open /dev/gkmem: No such file or directory
I'm assuming it failed because I'm already running a custom ROM. This is the only step I tried in the gfree method because it looked like all the other steps are for root and recovery, which I have already.
I tried installing the Play Store apk, but as expected, the Play Store icon is unresponsive after installation. What should I do to get the Play Store? It's really the only Google application that needs to be on this device.

It's always right when I give up hope that I figure out the answer...
Solution: Use these GApps: http://dz.ace-com.cz/index.php/downloads