Thx for the forum, Bob:] (Steal ROM anytime soon?)

[myplane150]

Digging on my own i've found that some devices don't respond to the cat /proc/mtd. Could this be the issue with my Steal. Maybe the company blocks its use or it doesn't exist? Someon else had this issue and used cat /proc/partitions which i did in my 8:23 post. Does this help?

[myplane150]

Bob, check this out:

[IMG][/IMG]

adb push rkdump /data looks to have worked. No info for cat /proc/mtd. Does it look like the chmod 755 command worked? Probably not since the image is not found, right?

[myplane150]

[IMG][/IMG]

Is the problem possibly where we are trying to put the image? 'No such file or directory'.

Again, what about 'cat /proc/partitions' (@8:23)? I don't understand what it shows but you probably do.

[Finless]

It's probably not returning data because you are not root?
Strange it does not work but leads me to believe your not root?

The reason you cant dump it is the mounted block number maybe different for your ROM or may even have a different name like backup.img instead of update.img

So lets try a different way. We need to get the correct block and name.

At windows command prompt type adb shell
You should get a shell prompt. It maybe just a $ or a #. But you are now in a Android shell.
At that prompt type su
What does it say after you type su?
If it changes from a $ to a # you are root.

This is my command windows and what I get:
Notice the change in prompt when I typed adb shell
Then su. Since I was already root su did nothing
then mount command



Copyright (c) 2009 Microsoft Corporation. All rights reserved.

E:\Android\adb>adb shell
root@android:/ # su
su
root@android:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock8 /system ext4 rw,noatime,nodiratime,barrier=1,data=ordered,n
oauto_da_alloc 0 0
/dev/block/mtdblock6 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,dat
a=ordered,noauto_da_alloc 0 0
/dev/block/mtdblock5 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,da
ta=ordered,noauto_da_alloc 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/31:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nod
iratime,uid=1000,gid=1015,fmask=0702,dmask=0702,al low_utime=0020,codepage=cp437,
iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/31:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatim
e,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=07 02,allow_utime=0020,codepage=c
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:1 /mnt/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0 002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
root@android:/ #

[Finless]

Better yet lets just pull the mtd file.

create a folder on your C drive called adb. Adb will not pull files straight to the root of C so wee need a folder.

At the windows command prompt type:
adb pull /proc/mtd C:\adb\mtd

This will pull the mtd file and put it on c: in the adb folder.
Open that file with a text editor and we should have our mounted block names and values.

Bob

[myplane150]

This is what i get:



[IMG][/IMG]

Unknown user root? Then i tried 'mount'. Good/not good?
Now i'll try the pull.

[Finless]

try pulling the mtd file like I explained.

But based on what you just showed me yes your mount blocks are in a different order!

Bob

[myplane150]

I snipped it all to show you that everything was done correctly. Still nothing below dev: size, etc...
Where could it be???


[IMG][/IMG]

[Finless]

Do you have the mtd file in C:\adb folder on your PC?

Bob

[myplane150]

Yep, that's why i included it in the screen shot to show you that i followed each step.

When opened in Edit Lite, there is nothing beneath 'dev: size erasesize name'

[Finless]

OK do this then

adb shell
cd /dev/block
ls -l

This should list everything

Bob

[Finless]

Did you feel that earthquake we just had about 10 minutes ago?

Bob

[Finless]

Dont worry, we will figure this out. Your ROM is just setup a bit different.

so did you get a directory listing of /dev/block ?

Bob

[Finless]

FYI this is my directory listing. Asx you can see we can get the info by poking around

E:\Android\adb>adb shell
root@android:/ # cd /dev/block
cd /dev/block
root@android:/dev/block # ls -l
ls -l
brw------- root root 7, 0 2012-08-08 17:31 loop0
brw------- root root 7, 1 2012-08-08 17:31 loop1
brw------- root root 7, 2 2012-08-08 17:31 loop2
brw------- root root 7, 3 2012-08-08 17:31 loop3
brw------- root root 7, 4 2012-08-08 17:31 loop4
brw------- root root 7, 5 2012-08-08 17:31 loop5
brw------- root root 7, 6 2012-08-08 17:31 loop6
brw------- root root 7, 7 2012-08-08 17:31 loop7
brw------- root root 179, 0 2012-08-08 17:31 mmcblk0
brw------- root root 179, 1 2012-08-08 17:31 mmcblk0p1
brw------- root root 179, 2 2012-08-08 17:31 mmcblk0p2
drwxr-xr-x root root 2012-08-08 17:31 mtd
brw------- root root 31, 0 2012-08-08 17:31 mtdblock0
brw------- root root 31, 1 2012-08-08 17:31 mtdblock1
brw------- root root 31, 2 2012-08-08 17:31 mtdblock2
brw------- root root 31, 3 2012-08-08 17:31 mtdblock3
brw------- root root 31, 4 2012-08-08 17:31 mtdblock4
brw------- root root 31, 5 2012-08-08 17:31 mtdblock5
brw------- root root 31, 6 2012-08-08 17:31 mtdblock6
brw------- root root 31, 7 2012-08-08 17:31 mtdblock7
brw------- root root 31, 8 2012-08-08 17:31 mtdblock8
brw------- root root 31, 9 2012-08-08 17:31 mtdblock9
drwxr-xr-x root root 2012-08-08 17:31 platform
drwxr-xr-x root root 2012-08-08 17:31 vold


root@android:/dev/block # cd mtd
cd mtd
root@android:/dev/block/mtd # ls -l
ls -l
drwxr-xr-x root root 2012-08-08 17:31 by-name
root@android:/dev/block/mtd # cd by-name
cd by-name
root@android:/dev/block/mtd/by-name # ls -l
ls -l
lrwxrwxrwx root root 2012-08-08 17:31 backup -> /dev/block/mtdb
lock4
lrwxrwxrwx root root 2012-08-08 17:31 boot -> /dev/block/mtdblo
ck2
lrwxrwxrwx root root 2012-08-08 17:31 cache -> /dev/block/mtdbl
ock5
lrwxrwxrwx root root 2012-08-08 17:31 kernel -> /dev/block/mtdb
lock1
lrwxrwxrwx root root 2012-08-08 17:31 kpanic -> /dev/block/mtdb
lock7
lrwxrwxrwx root root 2012-08-08 17:31 misc -> /dev/block/mtdblo
ck0
lrwxrwxrwx root root 2012-08-08 17:31 recovery -> /dev/block/mt
dblock3
lrwxrwxrwx root root 2012-08-08 17:31 system -> /dev/block/mtdb
lock8
lrwxrwxrwx root root 2012-08-08 17:31 user -> /dev/block/mtdblo
ck9
lrwxrwxrwx root root 2012-08-08 17:31 userdata -> /dev/block/mt
dblock6
root@android:/dev/block/mtd/by-name #

[myplane150]

Lots of stuff. Does it help?

Nope, no earthquake. I'm up in Monterey.

Hey, thanks again for your help and patience. I really want to kick this in the ass. I even emailed Ematic with my "concerns" and never heard back. They are losers.



[IMG][/IMG]