[A510] Root and Bootloader unlock

---

Hi,

just to put info at the right place.
A510 root is yet available, thanks to Acer dev..
A100 exploit is still working, at least on current firmwares.
Thanks to Jesse6749, ZeroNull and vdsirotkin (4pda.ru) :

see xda topic here:
http://forum.xda-developers.com/show...1&postcount=93
consider installing acer a510 drivers from their website(even if your a510 is currently recognized by your pc)
in addition, some user had bugs at the end of the script, but root is done (su + titanium backup working)

another tool should be mentioned :
http://forum.xda-developers.com/show....php?t=1661324

To unlock bootloader (Euclid's Brother ) :
You must have the ability to send adb commands to the tablet.

adb reboot-bootloader
fastboot oem unlock


As a reminder :

dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/mnt/sdcard/recovery.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/mnt/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/APP of=/mnt/sdcard/system.img

out of this :
(thanks nikagl)

/dev/block/platform/sdhci-tegra.3/by-name/SOS    /dev/block/mmcblk0p1    /recovery
/dev/block/platform/sdhci-tegra.3/by-name/LNX    /dev/block/mmcblk0p2    /boot
/dev/block/platform/sdhci-tegra.3/by-name/APP    /dev/block/mmcblk0p3    /system
/dev/block/platform/sdhci-tegra.3/by-name/CAC    /dev/block/mmcblk0p4    /cache
/dev/block/platform/sdhci-tegra.3/by-name/MSC    /dev/block/mmcblk0p5    /misc
/dev/block/platform/sdhci-tegra.3/by-name/FLX    /dev/block/mmcblk0p6    /system/vendor    /flexrom    /flex
/dev/block/platform/sdhci-tegra.3/by-name/AKB    /dev/block/mmcblk0p7    ?
/dev/block/platform/sdhci-tegra.3/by-name/USP    /dev/block/mmcblk0p8    /aboot    (bootloader.blob)
/dev/block/platform/sdhci-tegra.3/by-name/DE2    /dev/block/mmcblk0p9    ?
/dev/block/platform/sdhci-tegra.3/by-name/UDA    /dev/block/mmcblk0p10    /data
So you can use these commands:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/mnt/sdcard/recovery.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/mnt/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/APP of=/mnt/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/CAC of=/mnt/sdcard/cache.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/MSC of=/mnt/sdcard/misc.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/FLX of=/mnt/sdcard/flexrom.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/AKB of=/mnt/sdcard/AKB.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/USP of=/mnt/sdcard/bootloader.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/DE2 of=/mnt/sdcard/DE2.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/UDA of=/mnt/sdcard/data.img

I hope a mod can move at least the AIO toolbox thread to this forum.

Instead of hoping, why don't you contact the A500 forum mod directly?

Originally Posted by FloatingFatMan

Instead of hoping, why don't you contact the A500 forum mod directly?

Good idea. Done.

Update: Thread has been moved.

Has anyone been able to update their SU binaries?
I updated the superuser app and when I checked my binaries (and tried to update them), I get:
"remounting /system as rw... fail"

I'm thinking I need to update my busybox, but the steps in the OP links says I should not. Can anyone enlighten me on this?

Originally Posted by salisbury_steak

Has anyone been able to update their SU binaries?
I updated the superuser app and when I checked my binaries (and tried to update them), I get:
"remounting /system as rw... fail"

I'm thinking I need to update my busybox, but the steps in the OP links says I should not. Can anyone enlighten me on this?

Using the recovery and root scripts I created I was able to update su, etc. I think the mempodroid exploit has some problem with newer version of busybox, also judging from the other thread (Full root for A10x / A5xx) - see my posts over there. The AIO tool also uses that mempodroid exploit... maybe it's better to start using the recovery & root script?

Regards,

Nika.

---------- Post added at 11:22 PM ---------- Previous post was at 10:32 PM ----------

Originally Posted by nikagl

Using the recovery and root scripts I created I was able to update su, etc. I think the mempodroid exploit has some problem with newer version of busybox, also judging from the other thread (Full root for A10x / A5xx) - see my posts over there. The AIO tool also uses that mempodroid exploit... maybe it's better to start using the recovery & root script?

Regards,

Nika.

Sorry, got to recall this post. The new version of busybox does have some problems with mounting through busybox. Doing it directly works, but through busybox it fails. See my post here: 202

Regards,

Nika.

Thanks for the update. So for now... I just leave it as is, right?
Or should I try to update busybox? And yes, I'm using the mempodroid exploit.

Sent from my Acer Iconia A510

Originally Posted by salisbury_steak

Thanks for the update. So for now... I just leave it as is, right?
Or should I try to update busybox? And yes, I'm using the mempodroid exploit.

Sent from my Acer Iconia A510

Yes, definitely leave it like it is.

How to UNROOT & LOCK

---

Is it poosible to lock and unroot an previously rooted A511? I am not 100% satisfied with the display and would like sending back my a511 and wait for a701.