Root Iconia Tab A100 on Android 4.0 Ice Cream Sandwich Based ROMs

ADVERTISEMENT

You may also like...

  • Lance Poore

    there are lots of errors in these instructions: the proper method should be as follows:

    $ adb shell mkdir /data/local/tools
    $ adb push tools /data/local/tools ; adb shell
    $ cd /data/local ; chmod 755 tools/*
    $ cd tools
    $ ./mempodroid 0xd9f0 0xaf47 sh
    # ./busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3
    # mkdir loop
    # mount -t ext4 -o loop /dev/block/loop7 loop
    # ./busybox cp su loop/xbin/ ; ./busybox cp busybox loop/xbin/
    # chmod 6755 loop/xbin/su ; sync

    • http://www.theandroidsoul.com/ Kapil

      Hey… thanks for that… will correct and take it up on xda… btw will get back to you (you know what I mean, hehe).. see ya!

  • Aramis

    just got the OTA ICS build – by accident. everything goes fine right up until attempting to mount the loop7 device. 
    Here’s from my terminal: 
    shell@android:/data/local/tools # mount -t ext4 /dev/block/loop7 loop
    mount: Invalid argument255|shell@android:/data/local/tools # mount -t EXT4 /dev/block/loop7 loop      mount: No such device

    note that dev/block/loop7 does exist (I’ve verified it with # ls /dev/block/loop7 ), but apparently losetup is failing silently.

  • Guest

    Step 6 should read:

    “adb shell mkdir /data/local/tools”

    and I had to push each file separately using:

    “adb push tools/su /data/local/tools/su”
    “adb push tools/mempodroid /data/local/tools/mempodroid”
    “adb push tools/busybox /data/local/tools/busybox”

    After that, it all seemed to work according to the original post

    • mook_


      Step 6 should read:

      “adb shell mkdir /data/local/tools”

      and I had to push each file separately using:

      “adb push tools/su /data/local/tools/su””adb push tools/mempodroid /data/local/tools/mempodroid””adb push tools/busybox /data/local/tools/busybox”

      After that, it all seemed to work according to the original post”

      Where am I entering this, within the cmd prompt in windows or in console of device?

      If device, not really sure how to navigate from device to c:/Program Files/Android…

      get error device not found

    • mook_

       I’m using terminal emulator on my device to input the cmds you listed and it says device not found.  Not really to familiar with droid file structure nor do I have a clue how to navigate from the device to the sdkplatform-tools folder on my pc.

      help would be appreciated.

      Thanks

  • mook_

    read only file system error like everyone else….lost at step six; if you have any tips
    please reply to this post or email mlowe1971@gmail.co

  • Guest

    after I have #, I cannot write

  • Stuckonthebay

    same problem as phanto, read only file system error…

  • Phanto

    I got the error mkdir failed for tools, Read-only file system