Full root for A10x and A5xx ICS. Simple method.

Jesse6749 · Apr 21, 2012

burbank said:
I'm having trouble making this work. It looks like the files get pushed properly but then it fails. Any guidance would be appreciated.

Full root for A100 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, File exists
push: tools/su -> /data/local/tools/su
push: tools/runit.sh -> /data/local/tools/runit.sh
push: tools/mount.sh -> /data/local/tools/mount.sh
push: tools/mempodroid -> /data/local/tools/mempodroid
push: tools/getroot.sh -> /data/local/tools/getroot.sh
push: tools/delroot.sh -> /data/local/tools/delroot.sh
push: tools/busybox.sh -> /data/local/tools/busybox.sh
push: tools/busybox -> /data/local/tools/busybox
8 files pushed. 0 files skipped.
794 KB/s (839527 bytes in 1.031s)
776 KB/s (37273 bytes in 0.046s)
-
Preparation is finished.
-
Executing of the main script.
link failed File exists
mkdir failed for /system/sbin, File exists
error: device not found
The file "su" isn't created!
-
Not getting root!
-
Error!
-
Press any key.

Make sure you have installed the A510 usb drivers that you can download from the Acer website and then go to settings then developer tools and enable usb debugging on the tablet. Then you can run the tool as System Administrator and it should work, but you have to download the su file from the google play store after running the tool.
Good Luck!!!!!

burbank · Apr 22, 2012

Jesse6749 said:
Make sure you have installed the A510 usb drivers that you can download from the Acer website and then go to settings then developer tools and enable usb debugging on the tablet. Then you can run the tool as System Administrator and it should work, but you have to download the su file from the google play store after running the tool.
Good Luck!!!!!

Thank you. I did everything EXCEPT running the script as System Administrator. I'll give that a try and then report back.

californiarailroader · Apr 22, 2012

burbank said:
I'm having trouble making this work. It looks like the files get pushed properly but then it fails. Any guidance would be appreciated.

Full root for A100 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, File exists
push: tools/su -> /data/local/tools/su
push: tools/runit.sh -> /data/local/tools/runit.sh
push: tools/mount.sh -> /data/local/tools/mount.sh
push: tools/mempodroid -> /data/local/tools/mempodroid
push: tools/getroot.sh -> /data/local/tools/getroot.sh
push: tools/delroot.sh -> /data/local/tools/delroot.sh
push: tools/busybox.sh -> /data/local/tools/busybox.sh
push: tools/busybox -> /data/local/tools/busybox
8 files pushed. 0 files skipped.
794 KB/s (839527 bytes in 1.031s)
776 KB/s (37273 bytes in 0.046s)
-
Preparation is finished.
-
Executing of the main script.
link failed File exists
mkdir failed for /system/sbin, File exists
error: device not found
The file "su" isn't created!
-
Not getting root!
-
Error!
-
Press any key.

My pc gave me the same readout, but when my A510 had booted back up it had root.

Jesse6749 · Apr 22, 2012

californiarailroader said:
My pc gave me the same readout, but when my A510 had booted back up it had root.

All you should have to do is download the su (super user) app from the google play store.
I had to do this when I rooted mine cause the root tool does not install this.

californiarailroader · Apr 22, 2012

Jesse6749 said:
All you should have to do is download the su (super user) app from the google play store.
I had to do this when I rooted mine cause the root tool does not install this.

Yeah, I already had SU on it (it restored it via Google when I upgraded to it from an A200), so I was good there.

NoSudo · Apr 24, 2012

burbank said:
I'm having trouble making this work. It looks like the files get pushed properly but then it fails. Any guidance would be appreciated.

Full root for A100 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, File exists
push: tools/su -> /data/local/tools/su
push: tools/runit.sh -> /data/local/tools/runit.sh
push: tools/mount.sh -> /data/local/tools/mount.sh
push: tools/mempodroid -> /data/local/tools/mempodroid
push: tools/getroot.sh -> /data/local/tools/getroot.sh
push: tools/delroot.sh -> /data/local/tools/delroot.sh
push: tools/busybox.sh -> /data/local/tools/busybox.sh
push: tools/busybox -> /data/local/tools/busybox
8 files pushed. 0 files skipped.
794 KB/s (839527 bytes in 1.031s)
776 KB/s (37273 bytes in 0.046s)
-
Preparation is finished.
-
Executing of the main script.
link failed File exists
mkdir failed for /system/sbin, File exists
error: device not found
The file "su" isn't created!
-
Not getting root!
-
Error!
-
Press any key.

Well I have never used this script to root. But it looks to me like you already had /data/local/tools folder created, and you probably still had the files in place too.

mkdir failed for /data/local/tools, File exists <-- It says File exists
8 files pushed. 0 files skipped. <--- All the files get pushed to /data/local/tools without issue
794 KB/s (839527 bytes in 1.031s)
776 KB/s (37273 bytes in 0.046s)

Executing of the main script.
link failed File exists <---- Again not familiar with the script but this probably indicates the Symbolic link it tried to create for su or busybox was still in place.
mkdir failed for /system/sbin, File exists
error: device not found
The file "su" isn't created!
-
Not getting root!

-
Error!

What version of ICS and what kernel version are you trying this on? This root method counts on mempodroid which counts on a specific kernel vulnerability. I suppose it's possible the kernel you have is patched for that. You can try eew245's Hard way directions HERE to try each part step by step and get a better idea of what is failing.

My guess is either mempodroid needs a different offset for an A510, or that kernel has been patched to fix exploit CVE-2012-0056, or maybe an issue with mounting /system. Do you ever get a hash prompt after pushing the files or are you stuck with a $ for a prompt in adb shell?

willhard1986 · Apr 24, 2012

great!

locn · Apr 25, 2012

OTA after root?

Hi

Thanks to all the devs who put effort into making it simple for us simpletons...

Question.... Will this affect any OTA updates in the future?

Cheers

ertrax · Apr 25, 2012

Hi , rooting process remains in "Wait for connect device...." and no root

, the my PC detects it properly A100 ( ICS version 4.0.3). A100 in Debug Mode "ON".

ertrax · Apr 25, 2012

ertrax said:
Hi , rooting process remains in "Wait for connect device...." and no root , the my PC detects it properly A100 ( ICS version 4.0.3). A100 in Debug Mode "ON".

solved, was to install the USB drivers for the A100 ACER site (support.acer.com). Thanks to All

jschall · Apr 25, 2012

I just got the official OTA upgrade from unrooted 3.2.1 to 4.0.3. (Acer_AV041_A100_1.014.00_WW_GEN1)

Has anyone tried to apply the ZeroNull rooting procedure to this new OS?

Are there any old folders or files or apps that have to be removed first?

marlopainter · Apr 25, 2012

mempodroid isn't created error on a510

If you are like me, you are getting the error:

"mempodroid isn't created"

I found a solution. I'm not sure if this is anywhere else,
but I will post it here.

I am using Win7 64bit, Iconia a510

I installed Superuser BEFORE I did these steps.

I opened runit-win.bat in a text editor and found the step
sending me to the error and simply deleted it.

I deleted lines 19 -21:

Code:

adb pull /data/local/tools/mempodroid
if not exist mempodroid goto ermem
del mempodroid >nul

I "saved as" and just added a "2" to the filename: runit-win2.bat
I ran it again, got the reboot, got root

Have fun.

jschall · Apr 25, 2012

This is what I get when I run "runinit-win.bat" on Windows 7 32-bit, with the A100 connected (I can see all the A100 folders in Windows Explorer):

Full root for A100 ICS. Simple method.
-
-
Wait for connect device...

And that's all. The batch file doesn't detect the connected A100.

Am I doing something wrong? Is there an updated version of the script?

---------- Post added at 03:41 PM ---------- Previous post was at 03:02 PM ----------

OK, then I installed the USB Driver from Acer Support.

When I re-ran runinit-win.bat, the script appeared to run, then the A100 rebooted.

Now, what should I do? Is it rooted or not? How can I tell?

I think the instructions should be improved. I am not a newbie, and I have rooted Honeycomb before. If it works, this method would be great. But how do I know if it worked?

illego · Apr 25, 2012

jschall said:
This is what I get when I run "runinit-win.bat" on Windows 7 32-bit, with the A100 connected (I can see all the A100 folders in Windows Explorer):

Full root for A100 ICS. Simple method.
-
-
Wait for connect device...

And that's all. The batch file doesn't detect the connected A100.

Am I doing something wrong? Is there an updated version of the script?

---------- Post added at 03:41 PM ---------- Previous post was at 03:02 PM ----------

OK, then I installed the USB Driver from Acer Support.

When I re-ran runinit-win.bat, the script appeared to run, then the A100 rebooted.

Now, what should I do? Is it rooted or not? How can I tell?

I think the instructions should be improved. I am not a newbie, and I have rooted Honeycomb before. If it works, this method would be great. But how do I know if it worked?

Is USB debugging on?

Make sure you have all the acer drivers for the a100 installed. adb is not seeing the tablet.

jschall · Apr 26, 2012

illego said:
Is USB debugging on?

Yes, that was in ZeroNull's instructions.

Make sure you have all the acer drivers for the a100 installed.

I installed the USB Driver. What other drivers are there?

adb is not seeing the tablet.

What is "adb"?

The script did run, and my tablet rebooted. Now what? Am I rooted, or not?

goofball2k · Apr 26, 2012

jschall said:
The script did run, and my tablet rebooted. Now what? Am I rooted, or not?

Install SuperUser. Then try to update binary through Superuser, it will be OK if it is rooted, it will fail if it doesn't.

NoSudo · Apr 26, 2012

What is "adb"?

adb = android debug bridge it's the app that gives you a shell on the tablet from your PC/workstation.

You can root the OTA version as far I have read. Until they patch the kernel for CVE-2012-0056. This root method which is relying on mempodroid will work. All hail Saurik!

jschall · Apr 26, 2012

goofball2k said:
Install SuperUser.

SuperUser was already installed.

Then try to update binary through Superuser, it will be OK if it is rooted, it will fail if it doesn't.

What is "update binary"?

NoSudo · Apr 26, 2012

jschall said:
SuperUser was already installed.

What is "update binary"?

the "binary" he refered to is su. Programs that are compiled are often called binaries, he could also have said app or executable. It just means the format of the data is in Base(2), when you convert to hex you get base(16) = hexadecimal.

If you have never read up on what Binary, Hex are it's worth a few hours of reading. It can greatly expand your understanding of computers and how they function. It will teach you what a bit, nibble, byte etc are also.

http://en.wikipedia.org/wiki/Binary_numeral_system

http://en.wikipedia.org/wiki/Base_16

goofball2k · Apr 26, 2012

jschall said:
SuperUser was already installed.

What is "update binary"?

Open Superuser
CLick on the wrench in the upper right corner
Scroll until you see the option "Su binary" and click on it
Click on "Update Anyway", it should prompt you if you are rooted, it will fail if you are not rooted.

Full root for A10x and A5xx ICS. Simple method.

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts