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

Search This thread

Samuelsz

New member
May 2, 2013
3
0
Code:
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Tous droits rÈservÈs.


C:\toolkit>toolkit.exe -d

======= Acer Iconia B1-A71 Toolkit =======

What do you want to do?
[1] Root
[2] Unroot
[3] Internal 2 External (only with root!)
[Q] Quit

Enter a selection: 1

================== Root =================
Before we can start, please do following:
1. Make sure drivers for Acer Iconia B1 are installed, you can find them here: h
ttp://goo.gl/doR8L
2. Plug-In your Acer Iconia B1 into this PC.
3. Enable USB Debugging Mode by going into Settings -> Developer Tools.
4. Put prerooted system.img.gz into folder: system_image.
5. Keep your device plugged in until it's finally rooted, or this procedure is a
borted!

If you sucessfully applied the steps above, we can now start.
You can always abort by pressing Ctrl+C


Press Enter when you're ready to continue...

Trying to establish ADB Connection...
* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

0123456789ABCDEF        device

ADB Connection to Acer Iconia B1 successful.

Starting Telnet server on Acer Iconia B1.
Power Manager State:
  mIsPowered=true mPowerState=3 mScreenOffTime=2048272 ms
  mPartialCount=0
  mWakeLockState=
  mUserState=SCREEN_BRIGHT_BIT SCREEN_ON_BIT
  mPowerState=SCREEN_BRIGHT_BIT SCREEN_ON_BIT
  mLocks.gather=
  mNextTimeout=5850059 now=5744085 105s from now
  mDimScreen=true mStayOnConditions=0 mPreparingForScreenOn=false mSkippedScreen
On=false
  mScreenOffReason=3 mUserState=3
  mBroadcastQueue={-1,-1,-1}
  mBroadcastWhy={0,0,0}
  mPokey=0 mPokeAwakeonSet=false
  mKeyboardVisible=false mUserActivityAllowed=true
  mKeylightDelay=6000 mDimDelay=108000 mScreenOffDelay=7000
  mPreventScreenOn=false  mScreenBrightnessOverride=-1  mButtonBrightnessOverrid
e=-1
  mScreenOffTimeoutSetting=121000 mMaximumScreenOffTimeout=2147483647
  mLastScreenOnTime=46162486
  mBroadcastWakeLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
  mStayOnWhilePluggedInScreenDimLock=UnsynchronizedWakeLock(mFlags=0x6 mCount=0
mHeld=false)
  mStayOnWhilePluggedInPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mH
eld=false)
  mPreventScreenOnPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=f
alse)
  mProximityPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
  mProximityWakeLockCount=0
  mProximitySensorEnabled=false
  mProximitySensorActive=false
  mProximityPendingValue=-1
  mLastProximityEventTime=0
  mLightSensorEnabled=false mLightSensorAdjustSetting=0.0
  mLightSensorValue=-1.0 mLightSensorPendingValue=-1.0
  mHighestLightSensorValue=-1 mWaitingForFirstLightSensor=false
  mLightSensorPendingDecrease=false mLightSensorPendingIncrease=false
  mLightSensorScreenBrightness=-1 mLightSensorScreenBrightnessWait=-1 mLightSens
orButtonBrightness=-1 mLightSensorKeyboardBrightness=-1
  mUseSoftwareAutoBrightness=false
  mAutoBrightessEnabled=false
mScreenBrightnessAnimator:
  animating: start:0, end:102, duration:0, current:102
  startSensorValue:-1 endSensorValue:-1
  startTimeMillis:46162747 now:46177113
  currentMask:SCREEN_BRIGHT_BIT

mLocks.size=0:

mPokeLocks.size=0:



Don't touch the screen! I'm taking it over now ;)
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.L
AUNCHER] cmp=com.mediatek.connectivity/.CdsInfoActivity }
Successfully started Telnet server on Acer Iconia B1.


Copying Busybox onto Acer Iconia B1.
3502 KB/s (1062992 bytes in 0.296s)
Successfully copied Busybox onto Acer Iconia B1.
/data/local/tmp/busybox telnet 127.0.0.1 1234 | cat /proc/dumchar_info

exit

exit

 127.0.0.1 1234 | cat /proc/dumchar_info                                      <

Part_Name       Size    StartAddr       Type    MapTo

preloader    0x0000000000040000   0x0000000000000000   2   /dev/misc-sd

dsp_bl       0x00000000005c0000   0x0000000000040000   2   /dev/misc-sd

mbr          0x0000000000004000   0x0000000000000000   2   /dev/block/mmcblk0

ebr1         0x0000000000004000   0x0000000000004000   2   /dev/block/mmcblk0p1

pmt          0x0000000000400000   0x0000000000008000   2   /dev/block/mmcblk0

nvram        0x0000000000500000   0x0000000000408000   2   /dev/block/mmcblk0

seccfg       0x0000000000020000   0x0000000000908000   2   /dev/block/mmcblk0

uboot        0x0000000000060000   0x0000000000928000   2   /dev/block/mmcblk0

bootimg      0x0000000000600000   0x0000000000988000   2   /dev/block/mmcblk0

recovery     0x0000000000600000   0x0000000000f88000   2   /dev/block/mmcblk0

sec_ro       0x0000000000600000   0x0000000001588000   2   /dev/block/mmcblk0p2

misc         0x0000000000060000   0x0000000001b88000   2   /dev/block/mmcblk0

logo         0x0000000000300000   0x0000000001be8000   2   /dev/block/mmcblk0

expdb        0x0000000000200000   0x0000000001ee8000   2   /dev/block/mmcblk0

android      0x0000000015e00000   0x00000000020e8000   2   /dev/block/mmcblk0p3

cache        0x0000000001400000   0x0000000017ee8000   2   /dev/block/mmcblk0p4

usrdata      0x000000000a000000   0x00000000192e8000   2   /dev/block/mmcblk0p5

fat          0x00000001b0a38000   0x00000000232e8000   2   /dev/block/mmcblk0p6

bmtpool      0x0000000001500000   0x00000000ff9f00a8   2   /dev/block/mmcblk0

Part_Name:Partition name you should open;

Size:size of partition

StartAddr:Start Address of partition;

Type:Type of partition(MTD=1,EMMC=2)

MapTo:actual device you operate
 

agentdeep

Senior Member
Apr 30, 2013
573
346
so you have 8gb and 15e.
you have not been able to update, right?
and you rooted your device successfully with the how-to for the 265 version, right?

does that mean your system.img.gz you created, is not compatible for people with the 265 version? I'm indeed confused.

yea 15e 8gb version.

I rooted mine from scratch using Ubuntu and not this toolkit. It was the procedure you posted from other thread.

I think you are right, 8gb and 16gb version has separate updates, is the 265 prerooted img came from 16gb version?
 

entonjackson

Senior Member
Dec 27, 2010
1,036
457
yea 15e 8gb version.

I rooted mine from scratch using Ubuntu and not this toolkit. It was the procedure you posted from other thread.

I think you are right, 8gb and 16gb version has separate updates, is the 265 prerooted img came from 16gb version?

No. I have 8gb and 256.
pawitp told me, the offsets in the dd command must be changed to not brick the device...
this is what makes me wonder, because you made without bricking.
 

nick_1964

Senior Member
Apr 26, 2011
61
4
prerooted img for RV04RC04 is on page 1

Why on earth I didn't see that, I read that post at least 6 times !!
Thanks. I gonna try now.

Copying Busybox onto Acer Iconia B1.
3359 KB/s (1062992 bytes in 0.309s)
Successfully copyied Busybox onto Acer Iconia B1.
E: The line 'android 0x0000000026500000 0x00000000020e8000 2 /dev/block/mmcblk0p
3' wasn't found in /proc/dumchar_info.

Then it Stops... :(
 
Last edited:

agentdeep

Senior Member
Apr 30, 2013
573
346
dumpchar_info

Here's my dump

Code:
system@android:/ $ cat /proc/dumchar_info
Part_Name       Size    StartAddr       Type    MapTo
preloader    0x0000000000040000   0x0000000000000000   2   /dev/misc-sd
dsp_bl       0x00000000005c0000   0x0000000000040000   2   /dev/misc-sd
mbr          0x0000000000004000   0x0000000000000000   2   /dev/block/mmcblk0
ebr1         0x0000000000004000   0x0000000000004000   2   /dev/block/mmcblk0p1
pmt          0x0000000000400000   0x0000000000008000   2   /dev/block/mmcblk0
nvram        0x0000000000500000   0x0000000000408000   2   /dev/block/mmcblk0
seccfg       0x0000000000020000   0x0000000000908000   2   /dev/block/mmcblk0
uboot        0x0000000000060000   0x0000000000928000   2   /dev/block/mmcblk0
bootimg      0x0000000000600000   0x0000000000988000   2   /dev/block/mmcblk0
recovery     0x0000000000600000   0x0000000000f88000   2   /dev/block/mmcblk0
sec_ro       0x0000000000600000   0x0000000001588000   2   /dev/block/mmcblk0p2
misc         0x0000000000060000   0x0000000001b88000   2   /dev/block/mmcblk0
logo         0x0000000000300000   0x0000000001be8000   2   /dev/block/mmcblk0
expdb        0x0000000000200000   0x0000000001ee8000   2   /dev/block/mmcblk0
android      0x0000000015e00000   0x00000000020e8000   2   /dev/block/mmcblk0p3
cache        0x0000000001400000   0x0000000017ee8000   2   /dev/block/mmcblk0p4
usrdata      0x000000000a000000   0x00000000192e8000   2   /dev/block/mmcblk0p5
fat          0x00000001b0a38000   0x00000000232e8000   2   /dev/block/mmcblk0p6
bmtpool      0x0000000001500000   0x00000000ff9f00a8   2   /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
system@android:/ $ cat /proc/dumchar_info
 
Last edited:

entonjackson

Senior Member
Dec 27, 2010
1,036
457
Here's my dump

Code:
system@android:/ $ cat /proc/dumchar_info
Part_Name       Size    StartAddr       Type    MapTo
preloader    0x0000000000040000   0x0000000000000000   2   /dev/misc-sd
dsp_bl       0x00000000005c0000   0x0000000000040000   2   /dev/misc-sd
mbr          0x0000000000004000   0x0000000000000000   2   /dev/block/mmcblk0
ebr1         0x0000000000004000   0x0000000000004000   2   /dev/block/mmcblk0p1
pmt          0x0000000000400000   0x0000000000008000   2   /dev/block/mmcblk0
nvram        0x0000000000500000   0x0000000000408000   2   /dev/block/mmcblk0
seccfg       0x0000000000020000   0x0000000000908000   2   /dev/block/mmcblk0
uboot        0x0000000000060000   0x0000000000928000   2   /dev/block/mmcblk0
bootimg      0x0000000000600000   0x0000000000988000   2   /dev/block/mmcblk0
recovery     0x0000000000600000   0x0000000000f88000   2   /dev/block/mmcblk0
sec_ro       0x0000000000600000   0x0000000001588000   2   /dev/block/mmcblk0p2
misc         0x0000000000060000   0x0000000001b88000   2   /dev/block/mmcblk0
logo         0x0000000000300000   0x0000000001be8000   2   /dev/block/mmcblk0
expdb        0x0000000000200000   0x0000000001ee8000   2   /dev/block/mmcblk0
android      0x0000000015e00000   0x00000000020e8000   2   /dev/block/mmcblk0p3
cache        0x0000000001400000   0x0000000017ee8000   2   /dev/block/mmcblk0p4
usrdata      0x000000000a000000   0x00000000192e8000   2   /dev/block/mmcblk0p5
fat          0x00000001b0a38000   0x00000000232e8000   2   /dev/block/mmcblk0p6
bmtpool      0x0000000001500000   0x00000000ff9f00a8   2   /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
system@android:/ $ cat /proc/dumchar_info

Thanks, that's exactly the same, the users get, using my tool.
alba81 and me are currently trying to figure out, how the new dd command must look like, to make it work for the 15e-guys
 

agentdeep

Senior Member
Apr 30, 2013
573
346
Thanks, that's exactly the same, the users get, using my tool.
alba81 and me are currently trying to figure out, how the new dd command must look like, to make it work for the 15e-guys

This is the code I used, taken from your tut:

Code:
/data/local/tmp/busybox zcat /cache/system.img.gz | dd of=/dev/block/mmcblk0 bs=4096 seek=8424 count=156928
 

agentdeep

Senior Member
Apr 30, 2013
573
346
Why on earth I didn't see that, I read that post at least 6 times !!
Thanks. I gonna try now.

Copying Busybox onto Acer Iconia B1.
3359 KB/s (1062992 bytes in 0.309s)
Successfully copyied Busybox onto Acer Iconia B1.
E: The line 'android 0x0000000026500000 0x00000000020e8000 2 /dev/block/mmcblk0p
3' wasn't found in /proc/dumchar_info.

Then it Stops... :(

this error is maybe becoz the script from toolkit is searching the 265 but you have 15e like mine.
 

emodom

Member
Oct 26, 2012
22
0
Okay ran the toolkit, got this:


======= Acer Iconia B1-A71 Toolkit =======

What do you want to do?
[1] Root
[2] Unroot
[3] Internal 2 External (only with root!)
[Q] Quit

Enter a selection: 1

================== Root =================
Before we can start, please do following:
1. Make sure drivers for Acer Iconia B1 are installed, you can find them here: h
ttp://goo.gl/doR8L
2. Plug-In your Acer Iconia B1 into this PC.
3. Enable USB Debugging Mode by going into Settings -> Developer Tools.
4. Put prerooted system.img.gz into folder: system_image.
5. Keep your device plugged in until it's finally rooted, or this procedure is a
borted!

If you sucessfully applied the steps above, we can now start.
You can always abort by pressing Ctrl+C


Press Enter when you're ready to continue...

Trying to establish ADB Connection...
ADB Connection to Acer Iconia B1 successful.

Starting Telnet server on Acer Iconia B1.

Don't touch the screen! I'm taking it over now ;)
Successfully started Telnet server on Acer Iconia B1.


Copying Busybox onto Acer Iconia B1.
7367 KB/s (1062992 bytes in 0.140s)
Successfully copied Busybox onto Acer Iconia B1.

It gets stuck after that. Any idea?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 156
    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:


    Unlock Bootloader
    CWM update, that removes bloat
    thx to FireDiamond

    Apply the "Invalid Partition Error" fix before rooting!!!
    To avoid unfixable bootloop, first apply this patch from Acer.
    Install the APK, start it, click on FixG1PMT (no feedback) and uninstall afterwards. Good luck!


    If you're rooting with prerooted system.img.gz here are the Downloads. Pick the one, fitting to the firmware installed on your tablet, otherwise you will get into bootloop!

    RV03RC05:
    Acer Firmware Update [mirror] [mirror + md5]

    RV04RC04:
    [system.img.gz] [mirror]

    RV05RC05:
    Acer Firmware Update [mirror1] [mirror2] [mirror3] [mirror4 + md5] [mirror5 + md5]
    [system.img.gz]

    RV02RC12:
    system.img.gz


    Acer Iconia B1-710 / B1-A710:


    Acer Iconia B1-711:

    RV01RC04_WW_GEN1:
    system.img.gz


    Acer Iconia B1-720:

    RV03RC01_WW_GEN1:
    system.img.gz (thx to Hayastan)

    RV07RC01_WW_GEN1:
    system.img.gz (thx to Hayastan)


    Acer Iconia A1-810:

    Acer Firmwares

    Modified XPosed Installer

    RV03RC08:
    system.img.gz

    RV18RC07_WW_GEN1:
    update.zip (about 4MB)
    system.img.gz with /system RW workaround (MD5 = 214db984aee42ef0c05d1cfa43d193c1) (needs extra config and SuperSU instead of Superuser) [torrent] (see this post also)

    RV21RC02_WW_GEN1:
    update.zip
    system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)

    RV21RC03_TWN:
    system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)

    RV27RC02_PA_CA:
    stock system.img.gz (rename to system.img.gz first!)
    system.img.gz (rename to system.img.gz first!)

    RV27RC03_WW_GEN1:
    system.img.gz
    stock system.img.gz
    update.zip

    RV18RC10_PA_CA:
    system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)

    RV26RC06_PA_CUS1:
    system.img.gz

    Stock Images: (Workaround to unroot: Put the system.img.gz of your version into system_image and choose root option in toolkit)
    RV03RC08:
    system.img.gz

    RV18RC07:
    system.img.gz ( MD5=550ECDB192F5668264B11B1070F4B932 )


    How to root from scratch


    Acer Iconia A1-811:

    RV01RC11_WW_GEN1:
    Acer Firmware Update

    RV02RC20:
    system.img.gz rooted and stock (including xposed) (thx to konsolen!!)

    RV02RC22_TWN_GEN1:
    system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)

    Unbrick:
    Stock Firmware RV01RC11 (copy on SD and flash from recovery)


    Acer Iconia A3-A10:

    A3-A10_RV05RC01_PA_CA:
    stock system image


    Your device not listed above?

    Help us getting your device to work with the toolkit.
    See this post how you can help.



    Common

    B1-A71 / B1-710 / B1-A710: Install this after rooting: Superuser App on Google Play Store
    A1-810 / A1-811 / B1-711: Install this after rooting: SuperSU App on Google Play Store
    Verify your root: Root Checker on Play Store


    FAQ

    Q: I'm stuck inside a bootloop after rooting!!!11
    A1: The system.img.gz you applied, wasn't suiting to the firmware version installed on your tablet. Download latest Acer firmware update ( !!! if available !!!), copy it on a micro sd card, plug it into your Iconia, go to recovery by holding Volume up and Power button while device is turned off. Then choose apply update from sd card.
    A2: If you cannot apply any Acer firmware, because you always get a partition error while installing, you should do a reboot after you get the error. A user reported that this made her/his device boot into Android again, showing the new version in settings -> info. Good luck
    A3: If your device is really bricked you could try bring it back to life. Here you find help: link1, link2, link3, link4 (many thanks to Gilly10, drmad and Hamza91)
    A4 (B1-A71, B1-710, B1-711 only): Unbrick
    A5: If the A1 - A4 didn't help. Send back the device to Acer. Tell them you tried to apply an update from sd card and ended up in this bootloop. Sending device back to Acer over UPS is free. Good luck!

    Q: Successfully rooted, but still no root after rebooting!
    A: Have you installed Superuser App from Google Play Store?
    (B1-A71 only)Q: Cannot update, always getting ERROR: - Invalid partition setting; 17: fat 238e8000:888e8000; Instalation aborted.
    A: Download "Invalid Partition Error" Patch.
    (B1-A71 only)Q: I applied update from RV05RC05 to RV05RC06 but still it shows RV05RC05.
    A: There is no RV05RC06. It is the RV05RC05. It got on Acers Download section with a RV05RC06 named zip file. But the content is 100% equal to RV05RC05.
    Q: Toolkit fails or crashes for any reason and I don't know what to do.
    A: Run it again with parameter -d, e.g.: toolkit.exe -d and post the entire output here.
    Q: Root from scratch on Linux doesn't work because of Error message: 'No such file or directory bin/posix/64/adb'
    A: sudo apt-get install ia32-libs libstdc++6 libgcc1 zlib1g libncurses5 libsdl1.2debian
    Q: Can i flash a custom recovery?
    A: No, because bootloader is locked. You would brick your tablet.
    Q: Are there Custom ROMs?
    A: No, see answer above.
    Q: Is my data wiped during root?
    A: No.
    Q: Do i lose root after factory reset or wipe date?
    A: No.
    Q: I get an error in Engineer mode entering telnet command.
    A: If Swiftkey is installed / enabled try settings Google AOSP Keyboard as default.
    Q: How can I start telnet server manually?
    A: Try this.



    What you can do with root:

    Apply Supercharger V6 by zeppelinrox and significally speed up your tablet! [My small How-To]
    Install Adaway, an ad-blocker for webbrowsers and apps containing ads.
    Install ROM Toolbox and customize boot screen and other funny things.
    Install Titanium Backup to Backup, Freeze, Uninstall any App and more.
    Install Datasync to sync app data like save states between rooted devices.


    What you can NOT do with root on these devices:

    Change DPI
    Flash Custom Recoveries
    Flash Custom ROMs



    Sources and Changelos @ github (thanks to nikagl)

    24
    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.
    14
    B1-A71 Unlocked bootloader + CWM

    FOR ALL B1-A71 USERS
    SOMETHING GREAT HAPPENED

    Unlocked bootloader + CWM
    11
    A1-810 4.4 WAS UNLOCKED
    Guide.

    Thanks to Acer A1-810 Devils: @Calingo, @vache, @Shreps, @swing4thefence, @FireDiamond.
    9
    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.

    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.