It says no such file or directory.
It does not seem to copy su from the sdcard.
Also adb shell /system/bin/cmdclient ec_micswitch '\`mount -o remount,rw /system\`' does not seem to put the system in RW mode.
I really dont know how the superuser app displays under my apps though if it didnt copy su.

Some more info:

When running the commands from your initial post, it fails on:

2. adb shell /system/bin/cmdclient ec_micswitch '\`cat /mnt/sdcard/su >/system/xbin/su\`'

The error is The system cannot find the path specified.

However if i login to a shell session via adb shell first and then run "/system/bin/cmdclient ec_micswitch '\`cat /mnt/sdcard/su >/system/xbin/su\`' " it does not fail, but it also does nothing. i can't find su under /system/xbin

usb host

---

sorry for such a question in a rooting thread, but it is actually as interresting as the GPS "confusion". Does the A100 have USB host capabilities? And if not, would it be possible to get such functionality working? Maybe an A500 port would help in this matter, as it has a full blown USB?

A100 == A500 + time

---

Originally Posted by jgal

Does the A100 have USB host capabilities? And if not, would it be possible to get such functionality working? Maybe an A500 port would help in this matter, as it has a full blown USB?

The A100 is a scaled down (physically, not electronically) version of the A500 with a different starting version of the OS (3.2 instead of 3.1). Although the A500 and A100 have both been rooted, the source code for Honeycomb has not been released to the public so we cannot expect fully custom ROMs such as Cyanogen for the A500/A100.

However, what can be done after rooting is the installation of additional kernel modules and configuration files to enable additional functionality. The hardware on the A100 is capable of USB host (as it is on the A500) but needs one of these kernel modules and some configuration changes to get it working.

We should be able to achieve everything that has been accomplished with the A500 (including support for external USB modems!) but we may not be able to directly use the solutions that were developed for the A500 because of the differences in the starting point.

For examples of what has been done with the A500 (and therefore should be doable with the A100 now that root has been achieved) google for "A500 ROM list". Developers have made flashable images with the kernel modules and configuration changes built right in to one handy dandy image. One such all-in-one solution is http://forum.xda-developers.com/arch...t-1188253.html

Originally Posted by ((RayDar))

The A100 is a scaled down (physically, not electronically) version of the A500 with a different starting version of the OS (3.2 instead of 3.1). Although the A500 and A100 have both been rooted, the source code for Honeycomb has not been released to the public so we cannot expect fully custom ROMs such as Cyanogen for the A500/A100.

However, what can be done after rooting is the installation of additional kernel modules and configuration files to enable additional functionality. The hardware on the A100 is capable of USB host (as it is on the A500) but needs one of these kernel modules and some configuration changes to get it working.

We should be able to achieve everything that has been accomplished with the A500 (including support for external USB modems!) but we may not be able to directly use the solutions that were developed for the A500 because of the differences in the starting point.

For examples of what has been done with the A500 (and therefore should be doable with the A100 now that root has been achieved) google for "A500 ROM list". Developers have made flashable images with the kernel modules and configuration changes built right in to one handy dandy image. One such all-in-one solution is http://forum.xda-developers.com/arch...t-1188253.html

Maybe i missed this but where do you see the A100 has been rooted? The topic of this specific post is confusing as it does not work. i have tried it and while you do see superuser installed, you don't have root access.
So unless i missed something, i don't think the A100 has been rooted yet.

Originally Posted by clubtech

Maybe i missed this but where do you see the A100 has been rooted?

From the first two posts in this thread:

Originally Posted by abliss

So until sc2k releases a new iconiaroot-1.4.apk, you can try this:

Steps to get root:
0. put your favorite su binary in /mnt/sdcard/su
1. adb shell /system/bin/cmdclient ec_micswitch '\`mount -o remount,rw /system\`'
2. adb shell /system/bin/cmdclient ec_micswitch '\`cat /mnt/sdcard/su >/system/xbin/su\`'
3. adb shell /system/bin/cmdclient ec_micswitch '\`chmod 6755 /system/xbin/su\`'

And:

Originally Posted by sc2k

I will probably release a new version of iconiaroot tonight.

It seemed to me that root on the A100 had been achieved -- especially since "ROOTED" is in the title of this thread.

If not, then my post should say "Although the A500 has been rooted and one day the A100 will be as well, ...".

Yes, sadly the above commands don't really work (at least not for me).
They don't mount the system as RW and su never gets copied over to /system/xbin

Hoping that someone can figure this out.

Originally Posted by sc2k

I will probably release a new version of iconiaroot tonight.

Hello. Have you released a new version of iconia root yet? Il looked on your "how to root hc3.1" and did not see an update supporting the a100.

We all greatly appreciate the effort put forth.

id love to root this as I am unable to mount system as rw too.

Originally Posted by clubtech

Some more info:

When running the commands from your initial post, it fails on:

2. adb shell /system/bin/cmdclient ec_micswitch '\`cat /mnt/sdcard/su >/system/xbin/su\`'

The error is The system cannot find the path specified.

However if i login to a shell session via adb shell first and then run "/system/bin/cmdclient ec_micswitch '\`cat /mnt/sdcard/su >/system/xbin/su\`' " it does not fail, but it also does nothing. i can't find su under /system/xbin

What do these command say?
1. adb shell ls -l /system/bin/cmd*
2. adb shell ls -l /mnt/sdcard/su
3. adb shell getprop ro.build.fingerprint