Develop Bugs

G2 rooting help, how to chmod?

I ran all the required commands and noticed that the chmod did not do anything. So I decided to run the temp root command abd I get permission denied.
Sent from my T-Mobile G2 using XDA App

Please anyone? I run this command "adb shell chmod 755 /data/local/tmp/*" but it does not do anything, is there something I have to change on that line?
Been trying to root for 2 days now but unsuccessful.

you're not supposed to see any return on the command prompt. Just continue with the procedure.

Thanks for giving me a reply, waited many hours. THANK you though.
When I run the temp root command, I get this.
"C:\android-sdk-windows\platform-tools>adb shell /data/local/tmp/psneuter
mmap() failed. Operation not permitted
C:\android-sdk-windows\platform-tools>adb shell
"

C:\android-sdk-windows\platform-tools>adb shell
#
#
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox md5sum /dev/block/mmcblk0p18
./busybox md5sum /dev/block/mmcblk0p18
b532ca54a073f0c4043bd7be69ebce8d /dev/block/mmcblk0p18
# cd /data/local/tmp
cd /data/local/tmp
# ./gfree -f -b hboot-eng.img
./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: 0x00015384 (86916)
Section index for section name string table: 41
String table offset: 0x000151cb (86475)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 18 and installing specified hboot image...
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.
# ./flash_image recovery recovery.img
./flash_image recovery recovery.img
# cd /data/local/tmp
cd /data/local/tmp
# ./flash_image recovery recovery.img
./flash_image recovery recovery.img
# ./root_psn
./root_psn
# sync
sync
#
Did these commands run right?
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img
# ./flash_image recovery recovery.img
# ./root_psn
# sync

All looks good to me.... When yoh restart the phone do you have s off?
Sent from my HTC Vision using XDA App

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.

[Q] Bricked G2???

I followed the instructions on the following link to downgrade and root my G2 a day ago.
When I was following the process, this message came up
PHP:
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./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...
md5sum #1 = 1477893d02ff60764d29fce795e75ac3
md5sum #2 = 0297a81509b6da5f102b1cc63893b9ad
Backing up partition /dev/block/mmcblk0p18 to /sdcard/part18backup-1354240611.bi
n ...
Writing image hboot-eng.img to partition /dev/block/mmcblk0p18 ...
md5sum #3 = 1477893d02ff60764d29fce795e75ac3
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!
and I did not notice this so I just went on with the rest of the process.
Now I cannot turn on the phone or go into recovery. The phone won't charge and the only response I got from the phone is when I plugged a USB cable to my laptop without the phone battery and pressed the two volume buttons together. I get 5 vibrations and a green light after I do that.
Any ideas how to solve this problem? Or have I just hard-bricked my phone? I don't have warranty by the way.

Sorry but you're in the market for a new phone or some JTAG equipment.
Sent from my Nexus 7 using xda premium

g2Noob said:
...and I did not notice this so I just went on with the rest of the process.
Now I cannot turn on the phone or go into recovery. The phone won't charge and the only response I got from the phone is when I plugged a USB cable to my laptop without the phone battery and pressed the two volume buttons together. I get 5 vibrations and a green light after I do that.
Any ideas how to solve this problem? Or have I just hard-bricked my phone? I don't have warranty by the way.
Click to expand...
Click to collapse
Sorry for doublechecking but it's seemed somehow unclear to me. What happends when your phone has battery in it, is inplugged and you try to power on? Absolutely nothing? Do you get any response via ADB when the phone is plugged to the computer. I will be kinda busy today so don't know how much I'll be able to help here, but I would't be so sure that it's bricked, there's hope. Good luck!

bootloader was erased then not flashed = no bootloader
no bootloader = no ability for phone to start in any scenario
not trying to be captin doom, but there is no hope without the ability to boot

sorry to hear that :crying:

g2Noob said:
I followed the instructions on the following link to downgrade and root my G2 a day ago.
When I was following the process, this message came up
PHP:
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./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...
md5sum #1 = 1477893d02ff60764d29fce795e75ac3
md5sum #2 = 0297a81509b6da5f102b1cc63893b9ad
Backing up partition /dev/block/mmcblk0p18 to /sdcard/part18backup-1354240611.bi
n ...
Writing image hboot-eng.img to partition /dev/block/mmcblk0p18 ...
md5sum #3 = 1477893d02ff60764d29fce795e75ac3
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!
and I did not notice this so I just went on with the rest of the process.
Now I cannot turn on the phone or go into recovery. The phone won't charge and the only response I got from the phone is when I plugged a USB cable to my laptop without the phone battery and pressed the two volume buttons together. I get 5 vibrations and a green light after I do that.
Any ideas how to solve this problem? Or have I just hard-bricked my phone? I don't have warranty by the way.
Click to expand...
Click to collapse
did you finish the downgrade?

ahmedrzvi said:
did you finish the downgrade?
Click to expand...
Click to collapse
Yes I did finish and for clarification I can't turn on the phone no matter what
I can recognize the device when I hold down volume up and down and plug it on the computer
It shows up as qualcomm cdma... I don't know why iot says cdma the phone is gsm and I never flashed a radio
Any help would be appreciated

g2Noob said:
Yes I did finish and for clarification I can't turn on the phone no matter what
I can recognize the device when I hold down volume up and down and plug it on the computer
It shows up as qualcomm cdma... I don't know why iot says cdma the phone is gsm and I never flashed a radio
Any help would be appreciated
Click to expand...
Click to collapse
Even a fully working g2/dz will give the same response in regard to the qualcomm cdma, I have searched a long time trying to find a way to use this mode to flash firmware directly to a phone, I have talked with a many developers who are familiar use this mode with other phones. No one has yet showed me what to do, the best information I get is you need special drivers unique to this model and a special program that only htc has. I assume someone could make another work, but for all the amazing developers who have come across this widley used phone over the years, none have
So again, not trying to be the bearer of bad news but I also don't want you sitting around with false hope so my first post still stands
Sent from my HTC Vision using xda premium

demkantor said:
Even a fully working g2/dz will give the same response in regard to the qualcomm cdma, I have searched a long time trying to find a way to use this mode to flash firmware directly to a phone, I have talked with a many developers who are familiar use this mode with other phones. No one has yet showed me what to do, the best information I get is you need special drivers unique to this model and a special program that only htc has. I assume someone could make another work, but for all the amazing developers who have come across this widley used phone over the years, none have
So again, not trying to be the bearer of bad news but I also don't want you sitting around with false hope so my first post still stands
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank you for your reply. I guess I can't do anything about this D: Time to get another phone... >.<

Hey guys I just plugged the G2 back into the computer and now there are sometimes orange lights in the corner that are either solid or just blinking. I don't know why it started doing this but I still can't turn on the phone. I've probably bricked my phone but I just want to make sure that I can't fix this by any means.

My DZ died yesterday, suddenly turned off, i cant power on and my PC do not recognize it only show QHUSB_DLOAD. I think the eMMC died.
There is any whey to repair or i need to change the motherboard?

Press and hold volume down button and track pad and press power...... How offen you used to flash Rom's? And which Rom u were on when your phone died?
Sent from my HTC Desire Z using xda app-developers app

[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

[Q] Bricked Desire Z becaues I put the wrong HBoot on it

OK so I was following the instructions to put an alternative mod on my HTC Desire Z, when I relised I had put the HBoot for the Tmobile G2 rather than the Desire Z
by following the guide
I have clockwork mod there so I can run adb shell and look arround.
This user was fixing the reverse situation. But when I try to run gfreee...
Code:
/data/local/tmp # ./gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
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.28-cyanogenmod-g4f4ee2e
New .modinfo section size: 216
Attempting to power cycle eMMC... Failed.
Module returned an unknown code (No such file or directory).
He then goes on to dd the correct HBoot into a partition:
Code:
dd if=/data/local/hboot-eng.img /dev/block/mmcblk0p18(enter)
I also found this post that talks about doing a simular thing but to a diffrent partition.
Code:
dd if=/data/local/hboot_7230_Vision_HEP_0.85.0005_101011.nb0 of=/dev/block/mmcblk0p18
so what is the correct partition for the HBoot? and is this the right way to recover from this.
Any guidence would be appreciated.
Stuart

worked
Code:
dd if=/data/local/hboot-eng.img /dev/block/mmcblk0p18(enter)
Click to expand...
Click to collapse
Well that worked.

Glad its working, but dd commands are dangerous so for anyone's future reference see here
http://forum.xda-developers.com/showthread.php?p=43201930
Links on how to easily and safely change hboots
Sent from my Nexus 4 using xda premium

O.K.
I made same mistake. But is there a problem to run only:
fastboot flash hboot hboot-eng.img with proper file from vision.hboot-0.84.2000.zip?

Look through the link in the post above yours
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Glad its working, but dd commands are dangerous so for anyone's future reference see here
http://forum.xda-developers.com/showthread.php?p=43201930
Links on how to easily and safely change hboots
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
fastboot hboot flash helped. Thanks again!