Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Thread Deleted

Full root for A10x and A5xx ICS. Simple method.

OP ZeroNull

Prev Previous Post   Next Post Next
3rd July 2012, 11:01 PM   |  #10  
pio_masaki's Avatar
Recognized Contributor
Flag Surprise, Az
Thanks Meter: 3,652
 
4,568 posts
Join Date:Joined: May 2012
Donate to Me
More
Quote:
Originally Posted by nikagl

Really, no problems when using my CWM-update-script:

Code:
shell@android:/ $ su
su
shell@android:/ # mount -o remount,ro /system
mount -o remount,ro /system
shell@android:/ # mount | grep system
mount | grep system
/dev/block/platform/sdhci-tegra.3/by-name/APP on /system type ext4 (ro,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/platform/sdhci-tegra.3/by-name/FLX on /system/vendor type ext4 (ro,relatime,user_xattr,acl,barrier=1,data=ordered)
shell@android:/ # busybox mount -o remount,rw /system
busybox mount -o remount,rw /system
shell@android:/ # mount | grep system
mount | grep system
/dev/block/platform/sdhci-tegra.3/by-name/APP on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/platform/sdhci-tegra.3/by-name/FLX on /system/vendor type ext4 (ro,relatime,user_xattr,acl,barrier=1,data=ordered)
shell@android:/ # ls -l /system/xbin/busybox
ls -l /system/xbin/busybox
-rwxr-xr-x root     root         1092 2012-07-03 00:41 busybox
(as far as I can see)

Regards,

Nika.

---------- Post added at 10:28 PM ---------- Previous post was at 10:18 PM ----------



A100 (judging from your sig)? In this case it would help for you to be able to update su? Or why is the updated busybox acting up on your devices?

Also, I don't own an A100, but did someone actually create a CWM for the A100 that does not need to be installed through root? Does A100 have bootloader which you can unlock ("adb reboot bootloader" and "fastboot oem unlock" and then use flashboot to install a new recovery ("fastboot flash recovery recovery.img")? If this is possible it shouldn't be too hard to create a recovery based on a boot.img with the right recovery.fstab parameters (mount points)....

Nevertheless, I was just responding to this with my experience on an A511 as the thread said A5xx...

Regards,

Nika.

Our unlocked boot loader is the a200 boot loader, ours don't respond to the unlock command. Until the boot loader is unlocked any recovery we flash fails boot loader verification. To flash our boot loader we go in through android, so we need to root. So, we need root to run custom recoveries, which is why I said it was redundant to flash root from cwm, if you can run cwm you're already rooted.

Its been awhile since anyone has looked at unlocking the a100 boot loader so it may be possible now, this was all done back when we had leaks to work with, now that we have official, who knows?

I've never run into an issue with busy box, but I also don't run Acer based ROMs.

I'm quite familiar with flashing random stuff to the a100, but until the boot loader is unlocked we can't run anything custom. Once unlocked we can flash whatever we want wherever we wish.

But like I said the new a100 boot loader may respond to the unlock command, but I doubt it. The a500 and a100 are similar, but they do differ on some points.

Tapatalked from my Galaxy S II.
Last edited by pio_masaki; 3rd July 2012 at 11:04 PM.
Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes