Im here to release a rooting program for the A110 i have successfully rooted and unlocked the one ive bought two days ago so i decided to make a program for all you guys to do the same as there is not much development support on the system. I am also working on porting cwm to the device if anyone knows how to do it i would be happy to provide you with the recovery.img in which i extracted from the SOS partition on the device so here it is download the program and try it out i am happy to read and respond to comments and question. Enjoy!!!
Can you please give us the step by step instructions for using this program? I tried it out and didn't work. The drivers was installed successfully. When i connect my acer iconia 110 and open the program everything loads ok. Three options are displayed, I selected "root" and my acer prompts me to restore. When I do this nothing happens, everything remains the same.My device is currently running version 4.1.2. Btw what version were you running when you rooted your acer iconia 110?
What file permissions does the su file need 0755? If you had a copy of the su file, and the superuser.apk you could push them with the ADB, then chmod the su file and install the .apk... Hmm, I'll have to give this some thought.
The Following User Says Thank You to JLindy For This Useful Post:
Why is my norton antivirus program keep telling me and flagging the program sayn its infected with a harmful Trojan inside this program of urs that i just downloaded from here!?? anybody know anything about this here??
We have created a tutorial for manually rooting the A110 running 4.1.1. We have had a 100% success rate via this method. There are also instructions on how to partition your external SD card and prep it for compatibility with the link2sd app, which has proven successful.
The reason the toolkit no longer works with version 4.1.2, is due to "something" (either the kernel or, possibly, the bootloader) renaming the device blocks at boot, from mmcblk* to loop* -- causing issues while attempting to mount the /system partition. We have determined that the 4.1.2 update patched the kernel, which may be the cause of this anomoly.
We're working hard on 4.1.2, and currently Skellums is working on a custom recovery of CWM, compiled from source, that's insecure with fstab and initramfs. Stay tuned!