I create mousemade pixel perfection stuffs for the interwebs.

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

Advertisement

Advertisement

The Acer Iconia Tab A100 got a leaked Ice Cream Sandwich firmware a few days ago, which we’re sure was tried out by many A100 owners to get a taste of Android 4.0 on their devices. Now they can root ICS based firmware using this root exploit. Though not as simple as usual rooting methods, it’s the only currently known way to root, so people are gonna have to bear with it for now. But hey, no pain, no gain, right?

Anyway, on with the procedure. Read on to find out how to root ICS firmware on your Iconia Tab A100.

Compatibility

This hack and the guide below is compatible only and only with the Acer Iconia Tab A100. It’s not compatible with any other device and may render an incompatible device unusable. Check your device model in Settings » About phone.

Warning!

The methods and procedures discussed here are considered risky and you should not attempt anything if you don’t know exactly what you are doing. If any damage occurs to you or your device, including a bricked, non-functional device, we won’t be held liable. You have been forewarned!

Pre-installation Requirements/Tips

Advertisement

  1. ADB installed on your PC. You can install ADB using this step by step guide → here.
  2. USB drivers for the Iconia A100 installed. Get them from → here.
  3. [Optional] This procedure will not wipe your apps, data and settings. But to be on the safe side, backup your Apps and important data — bookmarks, contacts, SMS, APNs (internet settings), etc. This Android backup guide would help you.

How to Root ICS Firmware on Iconia A100

  1. Download the following files (Important: Check the original development page for updated files):
    1. mempodroid  →  Download Link
    2. busybox  →  Download Link
    3. su  →  Download Link  |  Filename: su-bin-3.0.3.2-efghi-signed.zip
  2. Now, make a new folder “tools” in the “platform-tools” folder where you have installed adb. Check screenshot below.
  3. Copy the mempodroid and busybox files (from step 1.1 and 1.2) to this tools folder that you created in step 2. Also open the su-bin-3.0.3.2-efghi-signed.zip file from step 1.3 and copy the file ‘su’ from ‘system/bin’ inside the zip to the tools folder. Check the screenshot below:
  4. Connect your Iconia Tab A100 to your computer.
  5. Now open the Command Prompt from Start » Accessories. Navigate to the platform-tools folder using the cd command. For example, my platform-tools folder is located in K:\D\android-sdk-windows\platform-tools. So I would navigate to it as shown in the screenshot below:

    Taking the above screenshot as reference, navigate to your platform-tools folder.
  6. Then perform the following commands, pressing Enter after each line (do not type the $ sign at the start)
    $ adb shell mkdir tools
    $ adb push tools /data/local/tools ; adb shell
    $ cd /data/local ; chmod 755 tools/*
    $ cd tools ; ./mempodroid 0xd9f0 0xaf47 sh
  7. If the above commands worked, the $ should change to # which indicates you have temporary root. Now enter the following commands to mount the /system partition of the device:
    # ./busybox losetup -o $((512 * 51200)) /dev/block/loop7 /dev/block/mmcblk0
    # mkdir loop ; mount -t ext4 /dev/block/loop7 loop
  8. Now we need to check if system partition is mounted and writable. Enter the following command:
    # mount | grep loop
  9. You should get the following output (or similar to it) if everything worked properly:
    /dev/block/loop7 on /data/local/tools/loop type ext4 (rw,relatime,errors=continue,barrier=0,data=ordered)
  10. Now we need to copy the busybox and su files to /system for permanent root. Perform the following commands in adb:
    # ./busybox cp su loop/xbin/ ; ./busybox cp busybox loop/xbin/
    # chmod 6755 loop/xbin/su
  11. If all went well, you should now have permanent root access on your Iconia A100. You can now disconnect it from the PC.
  12. You will need to download Superuser app from the Android Market to be able to grant root access to apps on your Tab. You can install it from → here.

So there you go. Your Iconia Tab A100 is now fully rooted. Be sure to download and install Superuser to be able to get root access. Share your thoughts and experience in the comments.

Published: 
  • 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
     

Some HTML is OK
Join us on Facebook!schliessen
oeffnen