Can someone with root do the following for me

[Warpedflash]

Run the following command "cat proc/mtd" from a terminal emulator program (or from adb if you know how to use it) and then post the output here.

If you want to be super dooper handy you can follow the instructions on this page:
http://www.addictivetips.com/mobile/how ... on-images/

Then upload the images created somewhere for us to prod

[Veng]

export PATH=/data/local/bin:$PATH
$ $su
# cat /proc/mtd
dev: size erasesize name
mtd0: 00a00000 00080000 "boot"
mtd1: 00500000 00080000 "kpanic"
mtd2: 09600000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 02800000 00080000 "cache"
mtd5: 12100000 00080000 "userdata"
mtd6: 00a00000 00080000 "recovery"
mtd7: 00200000 00080000 "misc"
mtd8: 00200000 00080000 "tcc"
#

[Warpedflash]

export PATH=/data/local/bin:$PATH
$ $su
# cat /proc/mtd
dev: size erasesize name
mtd0: 00a00000 00080000 "boot"
mtd1: 00500000 00080000 "kpanic"
mtd2: 09600000 00080000 "system"
mtd3: 00400000 00080000 "splash"
mtd4: 02800000 00080000 "cache"
mtd5: 12100000 00080000 "userdata"
mtd6: 00a00000 00080000 "recovery"
mtd7: 00200000 00080000 "misc"
mtd8: 00200000 00080000 "tcc"
#

Cheers Veng!

Any chance you can do the backup to SD for me? You need an sd card of course

[Veng]

Doing it now.

[Warpedflash]

Cheers! If anything it allows people to start messing around a bit more and then have a close to stock image to return to. The Recovery Image is the bit that interests me more atm because the system image will have all your details on it (unless you wiped the tablet before you started but I didnt expect you to)

[Charlie]

Hi,

will that there are 3 different firmware versions of the scroll (in use at the mo) not have a impact on the recovery image?

[Warpedflash]

Hi,

will that there are 3 different firmware versions of the scroll (in use at the mo) not have a impact on the recovery image?

Probably. But hopefully not lol.

Each firmware will have its own recovery image but it may be the same recovery image across all 3 with differences only being in the system partition. The idea of getting clockworkmod working would mean we (hopefully) would not have to worry about that as much as we could use 1 clockwork image across all 3 firmware versions.

[Veng]

Getting seg fault. Let me reboot.

[Charlie]

Warpedflash,

thanks for the info. very much appreciated.

[Veng]

I think the problem is the device has spaces?


$ export PATH=/data/local/bin:$PATH
$su
#cat /sdcard/install >/data/local/install
#chmod 04755 /data/local/install
#/data/local/install
Android ROM dumper v0.72b
(c)2010 Sebastian404
romdump installed.
#/system/bin/romdump
Android ROM dumper v0.72b
(c)2010 Sebastian404
Device : telechips_tcc8900_us-eng 2.1-update1 ECLAIR eng.root.20101214.215931 test-keys

cat: can't open '2.1-update1': No such file or directory
cat: can't open 'ECLAIR': No such file or directory
cat: can't open 'eng.root.20101214.215931': No such file or directory
cat: can't open 'test-keys/system.info': No such file or directory
sort: 2.1-update1: No such file or directory
sed: 2.1-update1: No such file or directory
sed: ECLAIR: No such file or directory
sed: eng.root.20101214.215931: No such file or directory
sed: test-keys/system.info: No such file or directory
gzip: 2.1-update1: No such file or directory
gzip: ECLAIR: No such file or directory
gzip: eng.root.20101214.215931: No such file or directory
gzip: test-keys/system.info: No such file or directory
Creating required files... done.
Opening mtd table... done.
/proc/config.gz: No such file or directory
2.1-update1: No such file or directory
ECLAIR: No such file or directory
eng.root.20101214.215931: No such file or directory
test-keys/config.gz: No such file or directory
Dumping kernel config... done.
Dumping boot partition... done.
Dumping recovery partition... done.
Dumping system partition... done.
find: 2.1-update1: No such file or directory
find: ECLAIR: No such file or directory
find: eng.root.20101214.215931: No such file or directory
find: test-keys: No such file or directory
awk: 2.1-update1: No such file or directory
Creating Checksums... done.
Cleaning up... done.
All done.

[1] Segmentation fault /system/bin/romdump
#