root permissions on Android for Tiny210v2

Does anybody know how I can give root permissions for a downloaded apk
(term.apk in particular) since I need to be able to create a soft link in
/dev.

http://armworks.cc/index.php?title=Mini210S_rooting_the_mini

use adb (android debug bridge).

Thanks.  Only issue now is that windows doesnt see the standard Google USB
driver v7 as the appropriate driver for the Tiny210.

I have two tiny210's the one which has stock android from Friendlyarm was
detected by my desktop and was able to install the driver.  The one where I
modified the kernel to detect my symbol CDC device is the one that wasnt
detected.  Do you have any idea if this is a kernel option?

Both tiny's are showing the same info in About phone down to the same build
number (only change is the builder for the Kernel which is my user in
SUSE).

I'm really not that au fait with android yet, I've been pulled between 3
minifs boards, 2440,6410 and 210S, so I'm slowly getting a feel for stuff
but yes, in this instance I believe it could be, if you messed around with
the android defconfig, specifically the stuff that deals with 'usb gadget'
which is essentially drivers for 'spoofing' a linux box as a usb device to
another PC/device.

You can find it in menuconfig, under device drivers -> usb drivers -> usb
gadget support, look for USB Gadget support, make sure it's selected as a
built in driver, then hit enter to select it again and you should be given
a choice box, somewhere in the list about 7 from the bottom you will see
android gadget.  Select and recompile your kernel.  If it's already
selected then I guess there is something weird going on.

If you used the mini210_linux or mini210_android defconfig, it should
already be configured in the 3.0.8 defconfigs.

It wasnt selected for some reason but selecting it and rebuilding allows my
desktop to see the tablet now.

Thanks!

huzzah :)  For anyone else looking at this thread, you need to make sure
that you use the mini210_android_defconfig (or if you have a tiny210, use
the tiny210_android_defconfig if it exists), as it has the android usb
gadget device configured correctly along with the android staging device
drivers, the android staging driver options are not set in the
mini210_linux_defconfig, although most of the android config settings are
still in there, which seems odd to me.

It's also useful to note with the 3.0.8 kernel that if you want to use it
for linux, you should try and turn off the android settings, notably there
is an android_paranoid_network option that causes all sorts of issues with
networking on linux if you don't disable it.

one more thing to note is in the kernel source code /scripts directory
there is a FriendlyARM.cpio file, this is used by the kernel for initrd
booting, you can open it with any archive manager and you will see that it
has what looks like a rootfs inside it, which is what it is, a minimal
rootfs for booting the system, if you look in the init file in a text
editor, you will see how it goes about booting the system, this can be
useful in working out how  the touchscreen gets configured!!

FYI, I did start with mini210_android_defconfig as my base configuration so
I dont know why android USB Gadget wasnt selected by default.

Is this information still available?

The link no longer works.