[ToolKit] Acer Iconia v0.9.4 ***New: Supporting Acer Liquid S1***

The Acer Iconia Toolkit is supporting following devices at the moment:

• B1-A71
• B1-710
• B1-A710
• B1-711
• B1-720
• A1-810
• A1-811
• A3-A10
• Liquid S1

Only use these methods if you are sure the device cannot be rooted using a custom recovery from the following thread:
http://xdaforums.com/andr...ax-b1-t2875894

Intel based devices will not be supported ever by this toolkit! Only Mediatek chips are supported!

At the moment the following features are available:

• Root from scratch (Unix only / recommended)
• Root with prerooted Image (see Download links at the bottom)
• Unroot
• Swap External <-> Internal SD
• Odex ROM
• Pull system.img.gz off your device

Download Acer Iconia Toolkit Latest Version

Older Versions:



Thank you goes to:



Acer Iconia B1-A71:


Acer Iconia B1-710 / B1-A710:


Acer Iconia B1-711:


Acer Iconia B1-720:


Acer Iconia A1-810:


Acer Iconia A1-811:


Acer Iconia A3-A10:


Your device not listed above?



Common


FAQ



What you can do with root:


What you can NOT do with root on these devices:


Sources and Changelos @ github (thanks to nikagl)

Changelog:

v0.9.4
======
- Updated SuperSU to 2.46
- Removed Xposed APK
- Added Liquid S1 support!

v0.9.3
======
- Fix Xposed removal
- Wait longer for MTKLogger to press settings
- Add 811 and KK 810 and 811 to root from system.img

v0.9.2
======
- Removed Xposed till it works
- Add global for allatonce

v0.9.1

======
Added option to enable write access to external sdcard
Added comment for Xposed not working
Removed su delete command in invalid section

v0.9.0
======
- A1-811: Kitkat Support
- A1-xxx: Added proper su-binary
- Added timestamps
- Added descision for Superuser/Supersu
- Added selection for Xposed **not working yet**
- Added option to enable write access to external sdcard
- Added selection to continue automatically (also import the system instead of waiting for enter)
- Removed invalid quote and double exit command
- Added forward delete of characters to make sure Run command is empty
- Added some additional messages during the root process

v0.8.5
======
- A1-810: Fixed target directory for system image (no permissions for /cache directory since Kitkat)
- A1-810: Fixed root from scratch for Kitkat versions (thanks to Just_Another_N00b)

v0.8.4
======
- A1-810: Fixed root for Android Kitkat >= 4.4.2
- A1-810: Fixed abd devices id, changed sind Kitkat update

v0.8.3
======
- Fixed pulling system.img.gz from Windows

v0.8.2
======
- New: Supporting B1-720

v0.8.1
======
- A1-81x: Fixed missing read/write permissions for /system partition (thanks
to twu2!)
- All other devices: fixed missing path to su binary (thanks to arzakon.nn)

v0.8.0
======
- New: Pull system.img.gz from your tablet
- New: Supporting A3-A10

v0.7.8
======
- fixed Swap Internal to External for A1 and B1-710

v0.7.7
======
- Supporting Swap Internal to External for A1 and B1-710
- fixed bug in root from scratch: checking for /bin/su although it's not there


Full Changelog inside the Download.

B1-A71 Unlocked bootloader + CWM

A1-810 4.4 WAS UNLOCKED
Guide.

Thanks to Acer A1-810 Devils: @Calingo, @vache, @Shreps, @swing4thefence, @FireDiamond.

treetop777 said:

Ok, got the tab. I'm setting every thing up (USB drivers, ADB, finding where USB damiliarebugging is etc). I fired-up the tool and went through some steps to get familiar with it, then a question popped in my head: The choices are "root" "unroot" etc so to "root from scratch" do i select "root"? Do i still move the prerooted image into the folder or not? I'm confused cause i seam to have read somewhere that the tool can read the image on the tab, fix it, then rewrite it back to the tab (i may be totally mistaken).

Basically, what does "root from scratch" mean? is the same as "root" in the tool?

Again, Thanks in advance.

Click to expand...

Click to collapse

2013-12-05 UPDATE

Since it's already version 0.8.1, user can finish root procedure and R/W Workaround automatically with the latest toolkit for A1-810, A1-811. My instructions for R/W Workaround may be no longer needed.

Even there's a system.img.gz for your device, I still suggest you do root from scratch by yourself to prevent any problem.

OK, let's get started

Q:The choices are "root" "unroot" etc so to "root from scratch" do i select "root"?

A:When you open toolkit.sh in linux, choose A1-810->root->There will be two choices, one is root from scratch, and the other one is root from prerooted system.img.gz. You should only move system.img.gz to the system_image folder if you have one, root from scratch does not require system.img.gz in system_image folder.

Q:Basically, what does "root from scratch" mean? is the same as "root" in the tool?

A:There are two ways to perform root in this toolkit. First is root from scratch, this will take files directly from your device and root it. After the toolkit puts an su into it, it will put the files back to your device so your tablet gets root permission(Of course you have to install supersu for sure). If it's root from prerooted system.img.gz, it means you use others system.img.gz made by root from scratch, which you can just download it for toolkit, and gets root permission by it.

Can you give me your device's version information, so I can give you some help. You can find it in "about tablet". Seems like you are already using Linux. You can use the system.img.gz made by others if you have the same version on device. A prerooted system.img.gz will both work for windows and linux, follow the instructions below. Root from scratch only availiable for Linux, follow the For Linux section. I highly suggest you to read the R/W fix part first, so you can use most of the root required apps without problems.

First of all, do you have the same version of system.img.gz in your device's "about tablet". If you do have the same version, download the system.img.gz and put it into the "system_image" folder. With the system.img.gz, you can easily root under windows.

For Windows:
First thing first, download the system.img.gz you need and put it into system_image folder.

1.Download the latest toolkit then open the toolkit.exe

2.Choose A1-810

3.Choose Root

4.Follow the toolkit's instructions and finish root

5.Unplug till the root opertion is finished.

If there's no same version of system.img.gz compare to your device, do the root under Linux. I myself used Lubuntu with Oracle VM VirtualBox.


For Linux:
1.Open a terminal

2.Type "sudo su"

3.Type "chmod 777 your toolkit.sh" Example: chmod 777 /root/toolkit.sh

4.Type "your toolkit.sh" Example: /root/toolkit.sh

5.Choose "A1-810"

6.Choose "Root from scratch"(Or choose Root from prerooted system.img.gz if you have it. It's the same as Windows. Remember to put system.img.gz into system_image folder)

7.Follow the toolkit's instructions and finish root

8.Unplug till the root opertion is finished.

The toolkit's version is now 0.7.6, and R/W Workaround feature is now fixed again. With 0.7.6, users don't have to apply R/W Fixes by themselves. Use 0.7.4 instead if users want to perform root safer. The followings were done with toolkit 0.7.4, lubuntu, A1-811. This will also work for A1-810(Thanks to treetop777)

In order to make a system.img.gz with R/W fix, follow these instrutions

You can only do the followings when you are performing root from scratch. If you're using root from prerooted system.img.gz, download the ones with R/W Workaround. If there's no system.img.gz for you, follow the instructions and make one by yourself.

First of all, cancel the operation of the toolkit when it's copying system.img.gz back to your tablet. We don't have to finish the whole operation yet.

Download the su.tgz https://docs.google.com/file/d/0Bz5DDMjsS0KMdHpvbEk3Y1ZNVDA/edit?usp=sharing

1.Open a terminal under Linux

2.type "sudo su", you may have to type your password here.

3.type "gzip -d your system.img.gz Example:gzip -d /root/toolkit/system.img.gz(if your system.img.gz is under /root/toolkit)", now you have your system.img

4.type "mkdir /mnt/a1(mkdir means make a folder, so here it means I make a folder named a1 under /mnt)"

5.type "mount -o loop your system.img /mnt/a1 Example: mount -o loop /root/toolkit/system.img /mnt/a1"

6.Place the su.tgz under any folder (In this example I put my su.tgz under /root)

7.back to terminal, and type "cd /mnt/a1; tar zxvf your su.tgz Example: cd /mnt/a1; tar zxvf /root/su.tgz"

Edit, thanks to fREAST0
7.5. type "chmod 6755 /mnt/a1/xbin/su; chmod 6755 /mnt/a1/bin/su"

8.type "cd /root; umount /mnt/a1"

9.type "gzip -9v your system.img Example: gzip -9v /root/toolkit/system.img", now you have your system.img.gz back.

10.Congradulations, you have a system.img.gz with R/W Workaround now, put it back into /system_image and root from prerooted system.img.gz, finish the opertion and you device will be rooted.

2013-10-23 Update

If users are facing problems even if you have R/W Workaround, try to delete or rename the /system/bin/su to make the /system/xbin/su work. I'm not quite sure, but my root permission is working fine without /system/bin/su and I can update my su binary with supersu.