• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

Flash_image on Tattoo

1 post in this topic

Posted

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 ?

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.