No replies to this topic

[mainfram3]

Hi all.

As some of you may have noticed, the Tattoo has been rooted.
Our first problem is that the exploit takes a long time to run successfully.
Our second problem is that, by default, every writable partition is mounted as nosuid, rendering a suid shell useless upon reboot.

So, while I've temporarily given up on fixing our first problem, I decided to tackle the second. I rebuilt the boot partition, modifying init.rc to remount /data/ but leaving us the possibility to run our suid rootshell from there.

I've now run into a problem where flash_image refuses to update the boot partition (mtd2 in our case). Here's my output:

# ./flash_image boot /sdcard/mynewimage.img
./flash_image boot /sdcard/mynewimage.img
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
mtd: erase failure at 0x00020000 (I/O error)
mtd: erase failure at 0x00020000 (I/O error)
mtd: skipping write block at 0x00020000
mtd: erase failure at 0x00040000 (I/O error)
mtd: erase failure at 0x00040000 (I/O error)
mtd: skipping write block at 0x00040000
mtd: erase failure at 0x00060000 (I/O error)
mtd: erase failure at 0x00060000 (I/O error)
mtd: skipping write block at 0x00060000
mtd: erase failure at 0x00080000 (I/O error)
mtd: erase failure at 0x00080000 (I/O error)
(.....)
mtd: erase failure at 0x00260000 (I/O error)
mtd: erase failure at 0x00260000 (I/O error)
mtd: skipping write block at 0x00260000
error writing boot: No space left on device

Tried to erase the partition:

# cat /dev/zero > /dev/mtd/mtd2
cat /dev/zero > /dev/mtd/mtd2
write: I/O error

Everyone in the Tattoo forum is preety new to this so I thought about asking around in a more general forum.
Any ideas ? Could it be that the mtd libraries on the Tattoo are crippled in some way that prevents us from flashing the mtd partitions ?