Develop Bugs

[Q] Is my phone "really" rooted?

Ok. Let me tell you all what I have.
I have:
S-Off
Root Shell (#)
Super User App
Yet when I open ROM manager, it tells me I need to root my phone. Excuse me!? Is my phone not rooted? Am I missing something?
I tried rooting using this method (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2) and when I did the gfree_verify, everything came out ok. But when I reboot, I lose my root shell and when I type "su" it tells me permission denied. I have to do the temp root method every time to get the root shell (#).
And here's the thing. Even though I have the root shell (#), root apps, like ROM manager tell me my phone isn't rooted. I thought your phone was tempRooted or Rooted if you had the Root shell, S-Off and Super User app.
Am I missing something? The gfree_verify and what I think the problem is, is below.
()()()C:\Users\Izaya\Downloads\Phone ROMS\G2 Root_2011\Newest Root Method>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# stop ril-daemon
stop ril-daemon
# ./gfree_verify
./gfree_verify
gfree verify_cid returned:
OK
gfree verify_secu_flag returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
# start ril-daemon
start ril-daemon()()()
# cd /data/local/tmp
cd /data/local/tmp
# ./gfree -f
./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: 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 7 and patching it...
patching secu_flag: 0
Done.
(Right Here, it looks like this is a problem. I made sure that I pushed all my files to my phone, so making sure that I pushed them to the phone is not why. Please have a different response from that. Thanks *smiley face*
()()()# ./root_psn
./root_psn
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
./root_psn: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#()()()
It looks like this busybox thing is what's messing up or something. Is there someway I can format the /data/local/tmp folder so I can just redo everything, or when I push the same file, does it over right? Because I've been pushing multiple times only to come up with this same error multiple times.

No_Nickname90 said:
Ok. Let me tell you all what I have.
I have:
S-Off
Root Shell (#)
Super User App
Yet when I open ROM manager, it tells me I need to root my phone. Excuse me!? Is my phone not rooted? Am I missing something?
I tried rooting using this method (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2) and when I did the gfree_verify, everything came out ok. But when I reboot, I lose my root shell and when I type "su" it tells me permission denied. I have to do the temp root method every time to get the root shell (#).
And here's the thing. Even though I have the root shell (#), root apps, like ROM manager tell me my phone isn't rooted. I thought your phone was tempRooted or Rooted if you had the Root shell, S-Off and Super User app.
Am I missing something? The gfree_verify and what I think the problem is, is below.
()()()C:\Users\Izaya\Downloads\Phone ROMS\G2 Root_2011\Newest Root Method>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# stop ril-daemon
stop ril-daemon
# ./gfree_verify
./gfree_verify
gfree verify_cid returned:
OK
gfree verify_secu_flag returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
# start ril-daemon
start ril-daemon()()()
# cd /data/local/tmp
cd /data/local/tmp
# ./gfree -f
./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: 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 7 and patching it...
patching secu_flag: 0
Done.
(Right Here, it looks like this is a problem. I made sure that I pushed all my files to my phone, so making sure that I pushed them to the phone is not why. Please have a different response from that. Thanks *smiley face*
()()()# ./root_psn
./root_psn
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
./root_psn: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#()()()
It looks like this busybox thing is what's messing up or something. Is there someway I can format the /data/local/tmp folder so I can just redo everything, or when I push the same file, does it over right? Because I've been pushing multiple times only to come up with this same error multiple times.
Click to expand...
Click to collapse
Strange; try downloading Titanium Backup from the Market, select "Problems" and download BusyBox and SuperUser from there.
Sent from my HTC Vision using XDA App

OriginalGabriel said:
Strange; try downloading Titanium Backup from the Market, select "Problems" and download BusyBox and SuperUser from there.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I don't think I made myself clear. (I'm not being sarcastic. LoL!!) What I'm saying is, although I did the tempRoot method and have the Root shell, even after the TempRoot method, ROM manager still says "I need to Root my phone" even though I have the root shell. I don't think my phone is even tempRooting, and it looks like for some weird reason, busybox isn't getting pushed to the right places.
IDK what's going on. I have yet to see this problem else where. *sad face* I want the joys of a custom ROM.
Remember, I can't even PermaRoot, if I can't even TempRoot. Visionary didn't even TempRoot my phone. I would do the Visionary method, open Terminal Emulator, type "su" and get "permission denied" *sad face*
If someone ever tells me "permission denied" Ima hurt them. LoL!!

how can i instal instal official froyo to my 2.3.3

i was able to download stock froyo from HTC but i don't know how to instal it in my 2.3.3 Gingerbread version.
also i don't understand this instructions attached to firmware
Please follow below command to download the official android toolchain: (arm-eabi-4.4.3)
git clone https://android.googlesource.com/platform/prebuilt
NOTE: the tool ¡¥git¡¦ will need to be installed first; for example, on Ubuntu, the installation command would be: apt-get install git
--Modify the .bashrc to add the toolchain path, like bellowing example:
PATH=/usr/local/share/toolchain-eabi-4.4.3/bin:$PATH

Are you rooted with s-off? If not you must do this first if you want to easily change between roms. actually to properly root and obtain true s-off one of the steps will be to downgrade to stock froyo, follow the xda or cyanogen wiki to get there
Sent from my HTC Vision using xda premium

demkantor said:
Are you rooted with s-off? If not you must do this first if you want to easily change between roms. actually to properly root and obtain true s-off one of the steps will be to downgrade to stock froyo, follow the xda or cyanogen wiki to get there
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
i have tired to downgrade my htc vision but its not working please below is my cmd log
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Patrolscsn>adb devices
List of devices attached
SH0B1RT02382 device
C:\Documents and Settings\Patrolscsn>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\Documents and Settings\Patrolscsn>adb push fre3vo /data/local/tmp
cannot stat 'fre3vo': No such file or directory
C:\Documents and Settings\Patrolscsn>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
Unable to chmod /data/local/tmp/fre3vo: No such file or directory
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo: not found
$ /data/local/tmp/fre3vo -debug -start 10000000 -end 1FFFFFFF
/data/local/tmp/fre3vo -debug -start 10000000 -end 1FFFFFFF
/data/local/tmp/fre3vo: not found
$

Either you forgot to extract the files or you didnt put them in the same folder as adb
Sent from my HTC Vision using xda premium

kenanibeze said:
C:\Documents and Settings\Patrolscsn>adb push fre3vo /data/local/tmp
cannot stat 'fre3vo': No such file or directory
$
Click to expand...
Click to collapse
This is your first error message. All following commands fail because of this. You cannot simply continue when one step is executed with error. You have to fix it and then continue.
The reason for the error message is simple. There is no such file as 'fre3vo' in the directory ‘C:\Documents and Settings\Patrolscsn’. Copy the file 'fre3vo' in this directory or change current directory to one where the file is located. If you don’t know how, then you should probably stop trying to root your device.

the fre3vo is in the directory!!!!!
shared_ptr said:
This is your first error message. All following commands fail because of this. You cannot simply continue when one step is executed with error. You have to fix it and then continue.
The reason for the error message is simple. There is no such file as 'fre3vo' in the directory ‘C:\Documents and Settings\Patrolscsn’. Copy the file 'fre3vo' in this directory or change current directory to one where the file is located. If you don’t know how, then you should probably stop trying to root your device.
Click to expand...
Click to collapse
i have the fre3vo in the directory and i downloaded it from the link provided by xda

kenanibeze said:
i have the fre3vo in the directory and i downloaded it from the link provided by xda
Click to expand...
Click to collapse
Yes, the file fre3vo is in the directory:
C:\platform-tools
But your current directory is (the directory where you execute the commands):
C:\Documents and Settings\Patrolscsn
Execute this command to change your current directory:
cd C:\platform-tools
Good luck, you'll definitely need it

Hold shift and right click in the folder where fre3vo and fastboot.exe etc, then choose open command here
Now start from the begining
Sent from my HTC Vision using xda premium

shared_ptr said:
Yes, the file fre3vo is in the directory:
C:\platform-tools
But your current directory is (the directory where you execute the commands):
C:\Documents and Settings\Patrolscsn
Execute this command to change your current directory:
cd C:\platform-tools
Good luck, you'll definitely need it
Click to expand...
Click to collapse
Thanks so much for the tip, finally after two weeks of searching how to get the magical // sign, I got it I’m ever grateful.:victory:
Please I want to upgrade my HTC sense, but I have no idea which custom sense is good for htc desire Z (I would have preferred sense 4.0 but sense 3.0 looks ok) which one should I go for?
Also which of the custom rom of ICS is best for desire z :highfive:

kenanibeze said:
Thanks so much for the tip, finally after two weeks of searching how to get the magical // sign, I got it I’m ever grateful.:victory:
Please I want to upgrade my HTC sense, but I have no idea which custom sense is good for htc desire Z (I would have preferred sense 4.0 but sense 3.0 looks ok) which one should I go for?
Also which of the custom rom of ICS is best for desire z :highfive:
Click to expand...
Click to collapse
You’re welcome.
I’m not a big fan of Sense, but I would go for Sense 4, since it is more "lightweight" (consumes less storage and CPU) than Sense 3.x. You also have to distinguish between Sense 4.0 and Sense 4.0A which is even more lightweight.
Remember that our device has no official support from HTC, so all ICS ROMs are not perfect. You will notice some glitch here and there, but everything is getting better and better. Some ROMs are pretty stable thought, for example Andromadus Mimicry (which is based on Cyanogenmod 9.1). If you can live without Sense I would recommend you this ROM.
Here are some links to ROMs:
Cyanogenmod 9.1 - Andromadus Mimicry
Sense 4.0A - Gen.Y VisionX
Sense 4.0 - Ice Cream SENSEwich

is my phone bricked?
shared_ptr said:
You’re welcome.
I’m not a big fan of Sense, but I would go for Sense 4, since it is more "lightweight" (consumes less storage and CPU) than Sense 3.x. You also have to distinguish between Sense 4.0 and Sense 4.0A which is even more lightweight.
Remember that our device has no official support from HTC, so all ICS ROMs are not perfect. You will notice some glitch here and there, but everything is getting better and better. Some ROMs are pretty stable thought, for example Andromadus Mimicry (which is based on Cyanogenmod 9.1). If you can live without Sense I would recommend you this ROM.
Here are some links to ROMs:
Cyanogenmod 9.1 - Andromadus Mimicry
Sense 4.0A - Gen.Y VisionX
Sense 4.0 - Ice Cream SENSEwich
Click to expand...
Click to collapse
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
#

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.