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!!

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

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
#

Any alternative for flashing a recovery?

I'm using the U.S. Glide running dmans cm10.1 with the Aquethys touch CWM recovery and I have messed up my USB Port and cannot transfer any data what so ever. I decided to explore alternatives to update the recovery and I found the flash_image command to be the best option as I was unable generate a cwm flashable zip from the Odin tar file (a bit too complexed for me (I have a windows pc)) and while attempting the command flash_image recovery /sdcard/recovery. Img in the phones terminal (image extracted from the new cwm built from source (great job guys!!!!)) and got a partition error and after more research found this to be a common error with people with phones containing the Emmc layout. But of course no solutions presented themselves without needing a solid USB connection. Any help or troublshooting would be appreciated! Other routes included fastboot interface but I don't think this phone uses it (correct me if I'm wrong )
Sent from my SGH-I927

wat about twrp recovery... u can find it on the goomanager app

You should try the nontouch version of cwmr. I've heard several people running into similar problems as you with the touch version.
Sent form my SGH-i927 running dman's cm10.1

Right but how do I flash it without a functional USB Port?
Sent from my SGH-I927 using xda premium

Cprager said:
Right but how do I flash it without a functional USB Port?
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
Connect your phone and laptop to your wifi.
Goto Settings developer options - turn on "ADB over netwrok"
adb connect 192.168.x.x:5555
Now follow this http://forum.xda-developers.com/showthread.php?t=1630519 . Replce the .img file with the glide verison of recovery.
The above should work for you, though i've not tried it myself.

awesome, I will attempt this today and report back.

Cprager said:
awesome, I will attempt this today and report back.
Click to expand...
Click to collapse
adb push recovery.img /data/local/
adb push flash_image /data/local/
(Permission denied, copied files to sdcard and then through phone moved to /data/local)
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
(Operation not permitted, I then decided to run the following commands:
adb shell
su
chmod 777 /data/local/recovery.img
chmod 777 /data/local/flash_image
no errors listed, it seemed to function)
adb shell rm /data/local/rights/mid.txt
(rm failed for /data/local/rights/mid.txt, no such file or directory)
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
(sh: syntax error: 'in' unexpected)
adb reboot
adb shell /data/local/flash_image recovery /data/local/recovery.img
(error scanning partitions: No such file or directory (seems like its failing because it doesn't know where the recovery partition is located maybe a DD command with the correct block containing the recovery partition??)
(I also tried the above in a root adb shell with the same error being encountered)

greeneyez15o said:
wat about twrp recovery... u can find it on the goomanager app
Click to expand...
Click to collapse
And what version of twrp did you flash and for what device to work on the glide? Without smashing your partitions..
Sent from my SGH-I927 using xda premium

Cprager said:
adb push recovery.img /data/local/
adb push flash_image /data/local/
(Permission denied, copied files to sdcard and then through phone moved to /data/local)
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
(Operation not permitted, I then decided to run the following commands:
adb shell
su
chmod 777 /data/local/recovery.img
chmod 777 /data/local/flash_image
no errors listed, it seemed to function)
adb shell rm /data/local/rights/mid.txt
(rm failed for /data/local/rights/mid.txt, no such file or directory)
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
(sh: syntax error: 'in' unexpected)
adb reboot
adb shell /data/local/flash_image recovery /data/local/recovery.img
(error scanning partitions: No such file or directory (seems like its failing because it doesn't know where the recovery partition is located maybe a DD command with the correct block containing the recovery partition??)
(I also tried the above in a root adb shell with the same error being encountered)
Click to expand...
Click to collapse
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
---------- Post added at 10:09 PM ---------- Previous post was at 09:47 PM ----------
ninthsense said:
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
You can also try doing the same from inside a terminal emulator app from within the CM10. Just found out that CM10 comes with flash_image already loaded.
Sent from my SGH-I927 using xda app-developers app

ninthsense said:
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
---------- Post added at 10:09 PM ---------- Previous post was at 09:47 PM ----------
You can also try doing the same from inside a terminal emulator app from within the CM10. Just found out that CM10 comes with flash_image already loaded.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Just attempted the following:
adb shell
su
cd /data/local
./flash_image recovery recovery.img
"error scanning partitions: No such file or directory" I am getting the exact same error through the terminal

Cprager said:
Just attempted the following:
adb shell
su
cd /data/local
./flash_image recovery recovery.img
"error scanning partitions: No such file or directory" I am getting the exact same error through the terminal
Click to expand...
Click to collapse
drop the "./" just try "flash_image recovery recovery.img" from the terminal. Remember to be "su" and in the same directory where the recovery.img is.

ninthsense said:
drop the "./" just try "flash_image recovery recovery.img" from the terminal. Remember to be "su" and in the same directory where the recovery.img is.
Click to expand...
Click to collapse
Ok, I just did the revised commands and got a different error output:
opened terminal:
su
cd /data/local (the directory where flash_image and the recovery.img are located)
flash_image recovery recovery.img
"failed with error: -1"
I believe the Flash_image cannot find the partition housing the current recovery but am unable/don't know how to find the correct partiton
but assuming the correct one is found, do you think the below command would be a viable option?
dd if=/data/local/recovery.img of=/dev/block/mmcblk0xxxxx

Cprager said:
Ok, I just did the revised commands and got a different error output:
opened terminal:
su
cd /data/local (the directory where flash_image and the recovery.img are located)
flash_image recovery recovery.img
"failed with error: -1"
I believe the Flash_image cannot find the partition housing the current recovery but am unable/don't know how to find the correct partiton
but assuming the correct one is found, do you think the below command would be a viable option?
dd if=/data/local/recovery.img of=/dev/block/mmcblk0xxxxx
Click to expand...
Click to collapse
Delete the flash_image you've downloaded and run the command again. The flash_image is inbuilt in CM10, so i guess using that one makes more sense.
Also rename the .img file to recovery .img and place it in the root of your sdcard and issue the following command :
su
flash_image recovery /sdcard/recovery.img

ninthsense said:
Delete the flash_image you've downloaded and run the command again. The flash_image is inbuilt in CM10, so i guess using that one makes more sense.
Also rename the .img file to recovery .img and place it in the root of your sdcard and issue the following command :
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Same error, "failed with error: -1"

ninthsense, dd'ing the image as he said should work, something like
dd if=/path/to/cwm/boot.img of=/dev/block/mmcblk0pX
But you'll have to do some digging to figure out what X is. Flash CWM the normal way, then head boot.img and each mmcblk0pX and find the one that's identical.
And DON'T just guess; flashing the wrong partition can brick your phone.

roothorick said:
ninthsense, dd'ing the image as he said should work, something like
dd if=/path/to/cwm/boot.img of=/dev/block/mmcblk0pX
But you'll have to do some digging to figure out what X is. Flash CWM the normal way, then head boot.img and each mmcblk0pX and find the one that's identical.
And DON'T just guess; flashing the wrong partition can brick your phone.
Click to expand...
Click to collapse
didn't suggested cause i don't know the values for those xxx myself and don't want him to end up wiping/briking his phone.

ninthsense said:
didn't suggested cause i don't know the values for those xxx myself and don't want him to end up wiping/briking his phone.
Click to expand...
Click to collapse
I appreciate the concern gentlemen! i definately WILL NOT execute a command without knowing full well its purpose.
Im a PC guy so this linux command stuff is a bit newer to me, that being said, there must be a way (command) to see the partitions?
**I have currently the touch CWM so if you need me to "then head boot.img and each mmcblk0pX" to find the one thats identical I may be able to do so.
edit** don't know if this helps
cat /proc/partitions
major minor #blocks name
179 0 7552000 mmcblk0
179 1 12288 mmcblk0p1
179 2 614400 mmcblk0p2
179 3 319488 mmcblk0p3
179 4 3932672 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2097152 mmcblk0p6
179 7 16384 mmcblk0p7
259 0 5120 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 512 mmcblk0boot1
179 8 512 mmcblk0boot0
179 24 7786496 mmcblk1
179 25 7785472 mmcblk1p1

Cprager said:
I appreciate the concern gentlemen! i definately WILL NOT execute a command without knowing full well its purpose.
Im a PC guy so this linux command stuff is a bit newer to me, that being said, there must be a way (command) to see the partitions?
**I have currently the touch CWM so if you need me to "then head boot.img and each mmcblk0pX" to find the one thats identical I may be able to do so.
Click to expand...
Click to collapse
Nothing really, besides just ls /dev/block/mmcblk0p*
Phone partitions are quite a bit different from computer partitions -- about half the partitions don't even have filesystems; the entire partition is dedicated to some image that is important to one thing or the other.
I've got a pretty good overview of the CGlide ICS partitions here: http://forum.xda-developers.com/showthread.php?t=2051327

From my touch recovery logs
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
Note : I would advise you to pull out the file system into a .img file and keep the backup before flashing it with recover.img. Jsut in case you need to restore back to the original state

ninthsense said:
From my touch recovery logs
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
Note : I would advise you to pull out the file system into a .img file and keep the backup before flashing it with recover.img. Jsut in case you need to restore back to the original state
Click to expand...
Click to collapse
YOU GUYS ROCK !!!!!
I understand the procedure for replacing the previous recovery with the new recovery.img through the DD command,
but am unsure how to backup the current one. I will do more research and run my procedure by you guys before attempting anything
**edit**
to backup:
dd if=/dev/block/mmcblk0p8 of=/sdcard/current-recovery.img
to flash new recovery:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
there was an attribute listed bs=4096 (maybe bit size??)
please let me know if my commands are correct, and I will give it a go (fingers crossed lol)

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.