Develop Bugs

Shell commands

Here you will find a list of some shell commands you can use on your android phone, either with a terminal emulator or over adb shell from your PC. I would recommend using connectbot as your terminal emulator.
The commands listed are in no way limited to what is described below, I am just scraping the surface here. For more information on these commands type ' --help' after your command, e.g. 'mount --help' or use google, most of these commands are exactly the same as what you would find on any Linux system, so you will find EXTENSIVE information on the web if you want to know more.
These commands work on my HTC Desire running Cyanogenmod 6 (Android 2.2), most, if not all of them should work on other devices and/or roms.
If you have any suggestions post them below or pm me and I will edit this post to include them.
Notes
Most of these commands require root privileges, type su first.
Everything after a # is a not and not a part of the command.
busybox
What it does
Provides a selection of commands not built into android by default.
Example(s)
busybox cp a b
Notes
busybox is included in most custom roms and has aliases set up so you do not need to type busybox before the commands eg, 'cp' is the same as 'busybox cp' in most custom roms.
cat
What it does
Prints the contents of a (text)file onscreen.
Example(s)
cat file
cd
What it does
Changes the current directory. You may find it easier to change to the directory you will be working in before issuing other commands so you dont need to include the full path in your commands.
Example(s)
cd .. # Go up 1 directory level, eg go from '/sdcard/download/ to '/sdcard'.
cd /sd-ext # Change to '/sd-ext'.
chmod
What it does
Makes a file executable
Example(s)
chmod 755 /data/bin/yourbin
cp
What it does
Copies files/directories
Example(s)
cp filea fileb
cp -rf directorya directoryb # Copy entire directory recursively and forces copy.
df
What it does
Displays information on all mounted filesystems (free space).
Example(s)
df -hm # Show disk usage in human readable format in Megabytes.
du
What it does
Diplays the size of files/directories.
Example(s)
du -md 1 # Prints the size of all directories in Megebytes.
du -sh file # Prints the size of file in human readable format.
du -sh directory # Prints the size of directory in human readable format.
export
What it does
Sets environment variables.
Example(s)
export PATH=$PATH;/sd-ext/bin;
free
What it does
Display the amount of free and used system memory
losetup
What it does
Associates loop disk images with loop devices.
Example(s)
losetup /sdcard/disk.img /dev/block/loop7
Notes
Android 2.2's implementation of apps2sd uses one loop device for each app saved to SD. There are 8 loop devives by default (loop0-loop7) so if you have 8 or more apps saved to SD you will not be able to use this command. There is no issue when using 'oldschool a2sd'
ls
What it does
List Directory contents.
Example(s)
ls -a # List directory contents including hidden contents.
mount
What it does
Mounts a filesystem.
Example(s)
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 # Remounts /system as writable.
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 # Remounts /system as read only.
mount -t ext2 /dev/block/loop6 /sdcard/disk # Mount loop6 on /sdcard/disk.
mount /sd-ext /sdcard/sd-ext # Mount /sd-ext on /sdcard/sd-ext.
Notes
On other devices it may be possible to mount disk images without going through losetup and using the option -loop in mount instead.
If you are having trouble with mount try using busybox mount instead, the busybox version seems more capable than the one shipped with Android.
mv
What it does
Move/rename files/directories
Example(s)
mv download/file stuff/file
mv picture4.jpg mydog.jpg
ping
What it does
Pings a server to check for conectivity.
Example(s)
ping -c 5 http://www.google.com # Ping google 5 times
Notes
if you do not include the -c option ping will work indefinatly.
pwd
What it does
Prints the current directory.
rm
What it does
Remove file/directory.
Example(s)
rm file
rm -rf directory # Delete a directory and its contents.
rmdir
What it does
Removes a directory
Example(s)
rmdir emptydir
Notes
If a directory has contents us 'rm -rf' instad.
su
What it does
Gives you root privelages.
touch
What it does
Makes an empty file
Example(s)
touch file.txt
wget
What it does
Download things from http or ftp.
Example(s)
wget http://www.google.com

Excellent, thank you.
Just what the doctor ordered for n00bs like me

[Q] 【data2sd】i have some troubles~~~555

there're some troubles while data2sd, and it doesn't work.....
please help me！
my G7's infomation:
S-OFF, AlphaRev N1Table HBOOT, SdCard:6.8G+1.2G FATA32
Process：
E:\android-sdk\tools>adb shell
/ # mount /system
mount /system
/ # mount /data
mount /data
/ # mount /sdcard
mount /sdcard
/ # exit
exit
E:\android-sdk\tools>adb push c:\01data /system/etc/init.d
32 KB/s (394 bytes in 0.011s)
E:\android-sdk\tools>adb push c:\busybox-armv6l /system/xbin/busybox
1771 KB/s (1062992 bytes in 0.585s)
E:\android-sdk\tools>adb shell
/ # chmod 755 /system/etc/init.d/01data
chmod 755 /system/etc/init.d/01data
/ # chmod 777 /system/xbin/busybox
chmod 777 /system/xbin/busybox
/ # cd /
cd /
/ # mount /dev/block/mmcblk0p2 /sd-ext
mount /dev/block/mmcblk0p2 /sd-ext
/ # dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd: writing '/sd-ext/ext2': No space left on device
1199+0 records in
1197+1 records out
/ # /system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
/system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
Filesystem label=userdata
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
76800 inodes, 306639 blocks
15331 blocks (5%) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
10 block groups
32768 blocks per group, 32768 fragments per group
7680 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
/ # mkdir /sd
mkdir /sd
/ # /system/xbin/busybox mount -o loop /sd-ext/ext2 /sd
/system/xbin/busybox mount -o loop /sd-ext/ext2 /sd
/ # cd /data
cd /data
/data # cp -a * /sd
cp -a * /sd
/data # cd /
cd /
/ # /system/xbin/busybox umount /sd
/system/xbin/busybox umount /sd
/ # exit
exit
E:\android-sdk\tools>adb reboot
error: closed
BTW,when i reboot the phone,i found the second partition on sdcard is 100% full,why?where is the mistake?

help！help！help！help！help！

This is a question and belongs in q&a, not development.
Sent from my Evil Lair using Doomsday Device

It actually belongs in the Data2SD thread, which in turn IS in ROM Development

Why you don't use Androhero tutorial that I reported on post number five??
It's very simple fast and secure.
Don't fails with it
sent from the future

thx，i'll try

Btw I suggest to use the default mtd structure.
sent from the future

E:\android-sdk\tools>adb reboot
error: closed
this problem may cause by usb drives or recovery?
the drives are all installed ok...

mattiadj said:
Why you don't use Androhero tutorial that I reported on post number five??
It's very simple fast and secure.
Don't fails with it
sent from the future
Click to expand...
Click to collapse
i have a question,in your tutorial, don't need this file busybox?

Busibox may be included in ROM.
Try to install recovery driver from root thread.
sent from the future

CM7 A2SD?

I can't seem to get the Ext A2SD to work. I've got the partition but nothing installs there. Am I missing something? I remember on my G1 it was all pretty much automatic.
Sent from my CM7 EVO using XDA App.

i'm pretty sure that the most recent builds of CM do A2SD in the same fashion that Froyo implemented it.
Meaning that the apps run off your SD off the main partition, making the EXT 2/3/4 unnecessary.
The main difference between CM's version and the stock version of A2SD right now is that CM has implemented a way to get all apps unlocked to be able to go to your SD card, and not just the ones that have been enabled by the market publisher.
in general, there is no reason to keep the EXT partition on your card anymore if you are running CM. You can just reformat it and get that precious disk space back.

Hmm. Well that sucks. I always liked the Ext A2SD because it loaded much faster. With the Froyo method it takes a few once booted because the sd is mounted.
Sent from my CM7 EVO using XDA App.

IIRC CM7 supports Darktremor ext a2sd/cache2sd script. This is a necessity for me, so I hope that's correct.
The problem could be related to a bug
http://forum.cyanogenmod.com/topic/14813-darktremor-apps2sd-issue/
Have you tried the firerat a2sd+ script?
Data2sd support for performance enhancement would be nice also.

Ok, I am somewhat confused. I am coming from a sense-based rom that had a2sd enabled. I have a ton of apps so this is necessary. Was running my Dalvik from the \cache\ partition and apps from ext3.
Is this still possible in CM7?
I tried running a2sd check in CM& and it said "a2sd not located" (or something to that effect).

I've had a a2sd issue with recent aosp roms, my find is that if yours is not working and you have a2sd installed then it's the kernel, I had to try multiple kernels to get mine working, I found Sbc bcnice v7 works perfect, shows up properly partitioned and apps are utilizing it, all the new zendroids and savagezen dont support a2sd, neither does snap 7.6

my95z34 said:
I can't seem to get the Ext A2SD to work. I've got the partition but nothing installs there. Am I missing something? I remember on my G1 it was all pretty much automatic.
Sent from my CM7 EVO using XDA App.
Click to expand...
Click to collapse
use Link2SD it is the best a2sd replacement, it supports fat32 and ext as your 2nd partition.

my95z34 said:
I can't seem to get the Ext A2SD to work. I've got the partition but nothing installs there. Am I missing something? I remember on my G1 it was all pretty much automatic.
Sent from my CM7 EVO using XDA App.
Click to expand...
Click to collapse
Hey dude,
I had the same problem (or need depending on your view) - I tried to apply "cm7_legacy_a2sd_r3-signed.zip" which failed for some reason I couldn't be bothered to work out.
Which lead me to look inside and see how it was going to apply itself. Which then took me on a happy journey of discovery that resulted in the following How-To: pastebin.com/TgqtMuYX
Check it out and let me know how it goes. If you have any issues along the way either pm me or reply here if it's helpful to the wider audience. I'll feedback any relevant details if necessary.
Cheers.
AC
PS. The phone I applied this on was my Hero (GSM) before they pulled CyanogenMod-7.0.0-Hero - seems to behave quite well when you increase the heap to 32MB, but it's still work in progress for testing.
# Android.Control 2011/04
How to manually apply a2sd on CM7 from recovery - Carried out on a Hero, but other phones should be the same.
(details taken from cm7_legacy_a2sd_r3-signed.zip)
Boot into your recovery image. I used ClockworkMod as it allowed me to mount /system very easilly
If adb it is NOT in your search path you will need to specify the /full/path/to/adb
DO NOT complain to me if the adb commands below fail if adb is not in your path
All adb commands issued from a regular user account on Linux - (Windoze will be the same, I'm sure you can work it out)
Let us begin...
1. Mount the /system partition
Recovery: Select: [mounts and storage] > [- mount /system]
[ALTERNATIVE]
Code:
$ adb shell mount /system
Just to check all went well
Code:
$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98400 0 98400 0% /dev
/dev/block/mtdblock4 133120 122304 10816 92% /cache
/dev/block/mtdblock3 174080 118224 55856 68% /system
2. Find your sd-ext partition - usually /dev/block/mmcblk0p2
Recovery: Select [mounts and storage] > [- mount /sd-ext]
[ALTERNATIVE]
Code:
$ adb shell mount /sd-ext
Just to check all went well and to see what the /sd-ext device details are
Code:
$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98400 0 98400 0% /dev
/dev/block/mtdblock4 133120 122304 10816 92% /cache
/dev/block/mtdblock3 174080 118224 55856 68% /system
/dev/block/mmcblk0p2 505636 10532 468999 2% /sd-ext
Recovery: Select [mounts and storage] > [- umount /sd-ext]
[ALTERNATIVE]
Code:
$ adb shell umount /sd-ext
3. Manually aplly firstboot.sh actions - from cm7_legacy_a2sd_r3-signed.zip
Using "/dev/block/mmcblk0p2" from the df output above exceute the following (replace with apropriate value for your phone!)
Code:
$ adb shell
~ # /system/bin/e2fsck -fy /dev/block/mmcblk0p2
~ # /system/bin/tune2fs -O has_journal /dev/block/mmcblk0p2
~ # /system/bin/e2fsck -fy /dev/block/mmcblk0p2
~ # /system/bin/tune2fs -c 0 -i 0 /dev/block/mmcblk0p2
~ # /system/bin/tune2fs -l /dev/block/mmcblk0p2
4. Then mount the sd-ext partition using existing script
Need additional entry in PATH to allow /system/etc/init.d/05mountsd to work
Code:
~ # PATH=$PATH:/system/bin
~ # /system/etc/init.d/05mountsd
You should see something very similar to below
Code:
e2fsck 1.41.10 (10-Feb-2009)
/dev/block/mmcblk0p2: clean, 11/130560 files, 27008/522112 blocks
5. Create app and app-private in sd-ext
If app and app-private [or dalvik-cache] exist on sd-exe BUT are NOT a directory then they must be removed!
Code:
~ # rm /sd-ext/app
~ # rm /sd-ext/app-private
[OPTIONAL]
Code:
~ # rm /sd-ext/dalvik-cache
Now we can create the directories proper
Code:
~ # install -m 771 -o 1000 -g 1000 -d /sd-ext/app
~ # install -m 771 -o 1000 -g 1000 -d /sd-ext/app-private
[OPTIONAL]
Code:
~ # install -m 771 -o 1000 -g 1000 -d /sd-ext/dalvik-cache
If you didn't see any errors you can assume everything is ok, but just to make sure...
Code:
~ # ls -l /sd-ext/
drwxrwx--x 2 system system 1024 Apr 16 13:49 app
drwxrwx--x 2 system system 1024 Apr 16 13:49 app-private
drwxrwx--x 2 system system 1024 Apr 16 13:49 dalvik-cache
drwx------ 2 root root 1024 Apr 16 01:42 lost+found
6. Create the userinit.d and functions script directories on /sd-ext
Code:
~ # install -m 755 -o 0 -g 0 -d /sd-ext/userinit.d
~ # install -m 755 -o 0 -g 0 -d /sd-ext/userinit.d/functions
Now we need to quit adb back to the host to push some files onto the phone
Code:
~ # exit
7. Push the userinit.d files into /sd-exe/userinit.d
(extract the contents of "cm7_legacy_a2sd_r3-signed.zip" to a temporary directory, then cd into sd-ext for the following adb commands)
Code:
$ adb push ./userinit.d/functions/a2sd /sd-ext/userinit.d/functions/a2sd
$ adb push ./userinit.d/10cache2sdext-binds /sd-ext/userinit.d/10cache2sdext-binds
$ adb push ./userinit.d/11data2sdext-binds /sd-ext/userinit.d/11data2sdext-binds
$ adb push ./userinit.d/12app2sdext-binds /sd-ext/userinit.d/12app2sdext-binds
$ adb shell
~ # chmod 750 /sd-ext/userinit.d/functions/a2sd
~ # chmod 750 /sd-ext/userinit.d/10cache2sdext-binds
~ # chmod 750 /sd-ext/userinit.d/11data2sdext-binds
~ # chmod 750 /sd-ext/userinit.d/12app2sdext-binds
~ # chown root:shell /sd-ext/userinit.d/functions/a2sd
~ # chown root:shell /sd-ext/userinit.d/10cache2sdext-binds
~ # chown root:shell /sd-ext/userinit.d/11data2sdext-binds
~ # chown root:shell /sd-ext/userinit.d/12app2sdext-binds
~ # exit
[ADVISORY]
If app, app-private or dalvik-cache was NOT working you would see a line similar to these lines below in the logcat output
Code:
I/busybox ( 113): sd-ext /sd-ext/app bindings not enabled
I/busybox ( 113): sd-ext /sd-ext/app-private bindings not enabled
I/busybox ( 113): sd-ext /sd-ext/dalvik-cache bindings not enabled
Reboot the phone, then quickly run adb logcat to watch the initial progress to confirm success
If you do NOT see any lines like those above in the logcat output then everything went OK
Code:
$ adb logcat
- waiting for device -
--------- beginning of /dev/log/main
I/cm ( 67): Welcome to Android 2.3.3 / CyanogenMod-7.0.0-Hero
I/cm ( 68): _
I/cm ( 69): __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
I/cm ( 70): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
I/cm ( 71): )) _))
I/cm ( 72):
I/mountsd ( 87): Checking filesystems..
I//system/xbin/run-parts( 62): e2fsck 1.41.10 (10-Feb-2009)
I//system/xbin/run-parts( 62): /dev/block/mmcblk0p2: recovering journal
I//system/xbin/run-parts( 62): /dev/block/mmcblk0p2: clean, 555/500856 files, 428759/1000173 blocks
I/logwrapper( 93): busybox terminated by exit(0)
I/logwrapper( 97): busybox terminated by exit(0)
I/logwrapper( 99): busybox terminated by exit(0)
I/mountsd ( 101): /sd-ext successfully mounted
I/busybox ( 113): sd-ext /sd-ext/data bindings not enabled
I/busybox ( 113): sd-ext /sd-ext/system bindings not enabled
I/logwrapper( 113): busybox terminated by exit(0)
I/logwrapper( 62): /system/xbin/run-parts terminated by exit(0)
...
Please be patient while any existing files in /data/app, /data/app-private and /data/dalvik-cache are copied to /sd-ext/app, /sd-ext/app-private and /sd-ext/dalvik-cache respectively
If you have manually populated the app directory prior to enabling a2sd, then this will further delay your first boot while the dalvik-cache is updated for each unseen .apk file
[NOTE]
$ = regular user shell prompt (on your PC, depending which user you use for you adb environment)
# = root user shell prompt (on your phone)

[Acer A200] GUIDE FOR ICS OTA ROOT

Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or getting flammed because you re-rooted your phone instead of your tablet because you forgot to unplug your phone from the computer while the tablet was plugged in...
Please do some research if you have any concerns about rooting your device! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Ok, this was a pain in the arse!
I hope I can remember the steps I took in order to get this done.
By the way, I'm using windows
adb push mempodroid /data/local
adb push su /data/local
adb shell
$ chmod 777 /data/local/mempodroid
Click to expand...
Click to collapse
Then I went to here as directed,
http://rkeene.org/projects/info/wiki/210
but didn't follow the steps as they were shown because I got stuck many times and had to start over.
So here are my steps.
1.
$ /data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
which then should turn the $ into a #
2.
# mkdir /data/x-root /data/x-root/bin
Click to expand...
Click to collapse
3. Download this,
http://www.rkeene.org/projects/info/resources/diatribes/root-toshiba-thrive/busybox
and then move the file to where you have mempodroid and su so you can adb push them easier
4.
adb push busybox /data/x-root/bin/busybox
adb push su /data/x-root/bin/su
adb shell
Click to expand...
Click to collapse
5. This is where it got tricky. If you don't pay close attention, you will most likely do what I did and put files where they aren't supposed to go. So please, PAY ATTENTION!
If you still have the # in the shell, move forward. Otherwise,
/data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
and then move forward once # is confirmed.
# cd /data/x-root/bin
# chmod 755 busybox
# ./busybox bash
Click to expand...
Click to collapse
Now, there is no doubting it, you will get the "bash: precmd: not found" error.
# unset PS1 PROMPT_COMMAND
# ./busybox bash
# for tool in $(./busybox --list); do ln -s busybox $tool; done
# PATH="${PATH}:/data/x-root/bin"; export PATH
Click to expand...
Click to collapse
6. AGAIN, PAY CLOSE ATTENTION HERE!!
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
Click to expand...
Click to collapse
7. This is where I ran into another problem, so pay attention.
# cd /
# mkdir /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
You will see nothing as the steps describe. This is because we skipped a step. Why? Because mount -o ro -t ext4 /dev/loop0 /dev/tmpdir for some strange reason wouldn't unmount so I could mount the next step. So instead, we move on and then check again.
Here is the removed step
# mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
# umount /dev/tmpdir
Click to expand...
Click to collapse
You can try this but I advise not to or you could very well run into the same issue I had where you can't unmount in order to move on with the root process
# mount -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
And now you will see /system mounted.
8.
# cp /data/x-root/bin/su /dev/tmpdir/bin/
# chmod 4555 /dev/tmpdir/bin/su
# umount /dev/tmpdir
# losetup -d /dev/loop0
# sync
# reboot
Click to expand...
Click to collapse
9. Now once your A200 reboot and displays the home screen, we will confirm.
adb shell
[email protected]:/ $ su
Click to expand...
Click to collapse
If the $ doesn't turn into a #, you did something wrong...
Thank you hexmare, for opening this thread and giving the guidance.
Thank you d10369319, for "/data/local/mempodroid 0xd9f0 0xaf47 sh", I would have never figured this out.
Thank you RKeene, for writing out the guide to Root the Toshiba Thrive
And Thank you Saurik along with zx2c4, for mempodroid

Ok, for some reason, /system still refuses to mount with "mount -o remount,rw /system"
So my solution is this,
$ su
# cd /data/x-root/bin
# chmod 755 busybox
# unset PS1 PROMPT_COMMAND
./busybox bash
# PATH="${PATH}:/data/x-root/bin"; export PATH
# cd /
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
# mount -t ext4 /dev/loop0 /dev/tmpdir
Click to expand...
Click to collapse
You will have to go to /dev/tmpdir in order to do anything with /system but it is the secret passage way for now...

Why is there still no A200 forum?

agentfazexx said:
Why is there still no A200 forum?
Click to expand...
Click to collapse
Maybe there will be now that we have made some progress...

agentfazexx said:
Why is there still no A200 forum?
Click to expand...
Click to collapse
+1 A200 Forum

Enjoy your ICS A200 owners. I just saw a tweet from AcerAmerica that ICS is being rolling out to A200

Hello to all,
My A200 has been upgraded today 'OTA' , to ICS (V: 4.0.3) , so Europe/France seems to be available, now.
Applying this procedure, all goes fine, and my A200 is rooted.
I'm very happy
A lot of thanks to people having discovered this procedure, particularly mempodroid which set all of this possible.
Greetings

the last time when you do losetup -d /dev/loop0
returns No such device or address?????
ive been through it twice now
*EDIT* Nevermind I figured out my problem...I was typing in reboot instead of using the hardware power button. Got root now, sweet!

I am sooo glad we can now root the a200, but I cannot get mine to work. I have went through the steps 3+ times and had issues each time. I thought I had it twice and then tried Titanium backup root and it said it didn't work.
I can't see at all where I've gone wrong..

That's very strange because Titanium Backup works just fine for me...

rom toolbox pro doesnt work when changing numbers in kernel tweaks...numbers dont stick
titanium works though

ran into a mounting issue
i was attempting to root my A200 with the OTA ICS
first attempt i ran into an issue were i am unable to mount
# mount -t ext4 /dev/loop0 /dev/tmpdir
mount: invalid argument
so i then replaced ext4 to EXT4 and i then received error
# mount -t EXT4 /dev/loop0 /dev/tmpdir
mount: No such device
could some one please tell me where i went wrong thank you in advance

what i do wrong when i try adb push mempodroid /data/local i get evertime this here :/
D:\android-sdk-windows\platform-tools>adb push mempodroid /data/local
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Ghorn

ghorn222 said:
what i do wrong when i try adb push mempodroid /data/local i get evertime this here :/
Ghorn
Click to expand...
Click to collapse
Go download the drivers from Acer's website for this device

johnsonj067 said:
i was attempting to root my A200 with the OTA ICS
first attempt i ran into an issue were i am unable to mount
# mount -t ext4 /dev/loop0 /dev/tmpdir
mount: invalid argument
so i then replaced ext4 to EXT4 and i then received error
# mount -t EXT4 /dev/loop0 /dev/tmpdir
mount: No such device
could some one please tell me where i went wrong thank you in advance
Click to expand...
Click to collapse
You have to follow the guide to the T or you will run into numerous problems and stop signs. Try again

daimerion said:
rom toolbox pro doesnt work when changing numbers in kernel tweaks...numbers dont stick
titanium works though
Click to expand...
Click to collapse
That's because we don't have a custom kernel yet. Just wait a little while.

Unfortunate the root isn't 100% cool my boot loader Is unlocked though.
Droid 3 bldr is locked down however changing numbers in rom toolbox works w/o custom kernals or modules.
http://www.acertabletforum.com/foru...iscussions/3649-how-unlock-boot-loader-4.html
^this Does work

su file?
This may be a stupid question, but where does one get the su file they're supposed to push to the tablet in the first step? I searched and searched, and finally found one that I downloaded, but when I tried this method with that su file, everything seems to work perfectly, but when I reboot and type su I get a segmentation fault. This is feels like something everyone knows but me, because every guide I can find that has anything to do with rooting from adb it seems the possession of an the su file is just assumed.

shwilson24 said:
This may be a stupid question, but where does one get the su file they're supposed to push to the tablet in the first step? I searched and searched, and finally found one that I downloaded, but when I tried this method with that su file, everything seems to work perfectly, but when I reboot and type su I get a segmentation fault. This is feels like something everyone knows but me, because every guide I can find that has anything to do with rooting from adb it seems the possession of an the su file is just assumed.
Click to expand...
Click to collapse
Did u use reboot command or the power button on the tab? It only worked for me when I used the power button to turn off then on

daimerion said:
Did u use reboot command or the power button on the tab? It only worked for me when I used the power button to turn off then on
Click to expand...
Click to collapse
I tried using the power button. Same result. Where did you get the su file from?

[ROOT ICS] The hard way && Digging for roots

For anyone that doesn't want to root the hard way crossix has come up with a double click root for Windows forum.xda-developers.com/showpost.php?p=23052186&postcount=105
Update 2/26/12
/system can now be mounted writable see the bottom of this post.
So the old Honeycomb exploit has now been patched in ICS. But there was an exploit found in the newer ICS kernels. Written by saurik,: called mempodroid
There is an offset needed as an argument to the binary, for the a100 we'll use what has worked for the a200 as noted in sauriks github linked above.
The issue with this is mounting /system as writable. I'm not sure if it's something in ICS, but it appears to be write protected. As noted here and here we will loop mount the system partition.
The tools needed are:
1. mempodroid under Usage Instructions, download pre-compiled
2. busybox 1.20 snapshot 3-10-12
3. su the latest from androidsu.com, extract from system/bin
4. mount.txt script
After downloading and extracting place them all in a folder called tools.
This must be done with adb. Issue the following from cmd or a terminal:
Code:
$ adb shell mkdir /data/local/tools
$ adb push tools /data/local/tools ; adb shell
$ cd /data/local ; chmod 755 tools/*
$ cd tools ; ./mempodroid 0xd9f0 0xaf47 sh
If all went well you should be at a hash # prompt. This is temp root.
mount /system rw the new way:
Code:
# PATH=$PWD:$PATH
# sh mount.txt -o remount,rw /system
Copy su and busybox to /system
Code:
# ./busybox cp busybox /system/xbin; ./busybox cp su /system/xbin/
# chmod 6755 /system/xbin/su
Install busybox
Code:
# cd /system/xbin
# for i in $(busybox --list); do ln -s busybox $i; done; sync
Copy the mount script
If busybox is updated this step must be run again
Code:
# cp /data/local/tools/mount.txt /system/bin/mount
# cp /data/local/tools/mount.txt /system/xbin/mount
Done your a100 should be rooted
the old way:
Now lets loop mount /system
Code:
[b]This is no longer needed[/b]
# ./busybox losetup -o $((512 * 51200)) /dev/block/loop7 /dev/block/mmcblk0
Code:
# ./busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3
# mkdir loop ; mount -t ext4 /dev/block/loop7 loop
Copy su and busybox to the new mount point.
Code:
# ./busybox cp su loop/xbin/ ; ./busybox cp busybox loop/xbin/
# chmod 6755 loop/xbin/su ; sync
If it worked your a100 is fully rooted. Make sure to install SuperUser from the Market.
Either get busybox installer from the market, and install it to /data/local/tools/loop/xbin
Or:
Code:
# cd loop/xbin
# for i in $(busybox --list); do ln -s busybox $i; done; sync
The mount point won't survive a reboot so in order to write to /system again run:
Code:
# busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3
# mount -t ext4 /dev/block/loop7 /data/local/tools/loop
[update 2/26/12]
To mount /system as writable do the following from adb. We'll just make a directory called /data/loop for easy access.
Code:
$ adb shell
$ su
# stop
[b]your screen will go black[/b]
# mkdir /data/loop
[b]skip this if the loop is already set up
# busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3[/b]
# mount -t ext4 /dev/block/loop7 /data/loop
# mount -o bind /data/loop /system
# start
You can write to /system with any app but /system can't be remounted ro then back to rw.
This can be added to /etc/install-recovery.sh to make it permanent
Code:
busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3
mount /dev/block/loop7 /data/loop
mount -o bind /data/loop /system
Thanks to crossix as the first to get temp root, and Icewyng for pointing out the exploit and helping with the magic number.

Ill be testing this when I get home, if it works Ill attempt to write a 1 command script to do it.
Sent from my MB860 using XDA App

OK...
Testing this out and found there were a couple of bugs.
You didn't have a "loop" folder created so I made one in the "tools" folder.
and, when mounting, you need to specify -t ext4.
Here are the revised commands for # mount /dev/block/loop7 loop
mkdir loop;mount -t ext4 /dev/block/loop7 /data/local/tools/loop
I noticed that the files /data/local/tools/loop/xbin/su and /data/local/tools/loop/xbin/busybox don't exist on /system/xbin until after a restart.
Finally, the busybox we are using to install doesn't seem to make all of the links to all of the nice commands we are used to, so things like grep, cp, etc... they won't work. I'm trying to figure out how to re-run the GUI busybox installer and point it to the loop folder, but haven't had much success.

danifunker said:
OK...
Testing this out and found there were a couple of bugs.
You didn't have a "loop" folder created so I made one in the "tools" folder.
and, when mounting, you need to specify -t ext4.
Here are the revised commands for # mount /dev/block/loop7 loop
mkdir loop;mount -t ext4 /dev/block/loop7 /data/local/tools/loop
I noticed that the files /data/local/tools/loop/xbin/su and /data/local/tools/loop/xbin/busybox don't exist on /system/xbin until after a restart.
Finally, the busybox we are using to install doesn't seem to make all of the links to all of the nice commands we are used to, so things like grep, cp, etc... they won't work. I'm trying to figure out how to re-run the GUI busybox installer and point it to the loop folder, but haven't had much success.
Click to expand...
Click to collapse
You beat me to the punch... was about to point it out.
Not sure what version of busybox this is but I will try with 1.19.2 and see how it goes.
Edit: Got root! It works great... for Busybox, use Busybox Installer to be able to get the latest version (1.19.4) I confirm that system is R/O for now.

danifunker said:
OK...
Testing this out and found there were a couple of bugs.
You didn't have a "loop" folder created so I made one in the "tools" folder.
and, when mounting, you need to specify -t ext4.
Here are the revised commands for # mount /dev/block/loop7 loop
mkdir loop;mount -t ext4 /dev/block/loop7 /data/local/tools/loop
I noticed that the files /data/local/tools/loop/xbin/su and /data/local/tools/loop/xbin/busybox don't exist on /system/xbin until after a restart.
Finally, the busybox we are using to install doesn't seem to make all of the links to all of the nice commands we are used to, so things like grep, cp, etc... they won't work. I'm trying to figure out how to re-run the GUI busybox installer and point it to the loop folder, but haven't had much success.
Click to expand...
Click to collapse
I did have some typos, think it's right now. That is an old busybox, it was just a quick find and it includes losetup but it's not one to use full time. Maybe sync is needed at the end so files are written properly. I didn't have to use -t ext4 with HC, but Ill add it to the OP
[edit] you have to use "busybox cp or busybox grep" I didn't include a way to add all the symlinks. Wow I have typos everywhere it's the end of the day for me, working nights.

Ok ... Got root!
Titanium works, Busybox Installer works, Superuser works, Root Explorer works...
Only thing is that System is R/O but we will work on it.

Waiting for a R/W system...and then, no one will stop my update

I can't get it to root :-(
It say not found
Sent from my A100 using xda premium

jondi23 said:
I can't get it to root :-(
It say not found
Sent from my A100 using xda premium
Click to expand...
Click to collapse
At what point, need some more details.

The tools folder gets pushed (the 3 files are copied) but then it says there is no such folder.
edit: never mind - i created the folder manually and pushed the files into the folder
edit2: rooted - thakns guys

Brilliat work, will try this later (need to get the sdk all set up again, I've been distro swapping). Got a pool match tonight too, so will try as soon as I can, will give whatever feedback I can later.

myprecious27 said:
The tools folder gets pushed (the 3 files are copied) but then it says there is no such folder.
edit: never mind - i created the folder manually and pushed the files into the folder
Click to expand...
Click to collapse
I forgot adb can't push a whole directory, it instead only copies the files within the directory.

wait how is it rooted if it's r/o I thought point of root was to make the file system r/w... er is root just allowing you to view all directories? Sorry for a noobish question, but you gotta start somewhere right?

rando152 said:
wait how is it rooted if it's r/o I thought point of root was to make the file system r/w... er is root just allowing you to view all directories? Sorry for a noobish question, but you gotta start somewhere right?
Click to expand...
Click to collapse
Well I think if we have su working we will be able to mount /system rw in some way if not directly. I cant imagine not being able to.
In any case though being able to write to /data as root is very useful. Example: Hulu flash fix.

You can't view /data if you're not root. That's one thig. Also, other functions may require root, like advanced networking things, etc.
I agree, not being able to write to /system is a major inconvenience, but most of the root programs will still work, as long as you're not writing to /system.

Since this is a temp root, does it mean that I will have to reroot every time I reboot? Will apps like Adfree work on this?

better yet is there a way we can do this solely on the tab? im away for work for another 4 weeks and only have my cell and a100 with me :-(
Sent from my SGH-I897 using xda premium

I get
Code:
255|[email protected]:/data/local/tools # mount -t ext4 /dev/block/loop7 /data/local
/tools/loop
lock/loop7 /data/local/tools/loop <
mount: Invalid argument

simoneser said:
I get
Code:
255|[email protected]:/data/local/tools # mount -t ext4 /dev/block/loop7 /data/local
/tools/loop
lock/loop7 /data/local/tools/loop <
mount: Invalid argument
Click to expand...
Click to collapse
I noticed the same thing happen after you root it and restart... not sure what to do next. Are you at temp loop?

simoneser said:
I get
Code:
255|[email protected]:/data/local/tools # mount -t ext4 /dev/block/loop7 /data/local
/tools/loop
lock/loop7 /data/local/tools/loop <
mount: Invalid argument
Click to expand...
Click to collapse
danifunker said:
I noticed the same thing happen after you root it and restart... not sure what to do next. Are you at temp loop?
Click to expand...
Click to collapse
try:
Code:
# busybox losetup -d /dev/block/loop7
# busybox losetup -o $((512 * 51200)) /dev/block/loop7 /dev/block/mmcblk0
# mount -t ext4 /dev/block/loop7 /data/local/tools/loop
The first line may produce
losetup: /dev/block/loop7: No such device or address
If it's not looped
After you are rooted the above can be run without adb from a terminal as su.
The mount point can be anywhere ex. /sdcard/loop instead of /data/local/tools/loop