[Motorola Atrix 2] jahuang:
Thanks Jim!

I follow your command line, and now get as below.

Android Debug Bridge version 1.0.25

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP disconnect <host
>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb help - show this help message
adb version - show version num

DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB adb
tcpip <port> - restarts the adbd daemon listening on TCP on the spec
ified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

and then, we get as below.

E:\Mobile Phone\HTC_Flash\r00tTattoo>adb shell
shell@edison:/$ su
su
root@edison:/# which mount
which mount
/system/bin/mount
root@edison:/# which busybox
which busybox
/system/bin/busybox
root@edison:/# which fdixk
which fdixk
root@edison:/# which fdisk
which fdisk
/sbin/fdisk
root@edison:/# which reboot
which reboot
/system/bin/reboot
root@edison:/# fdisk -l /dev/block/mmcblk0 | grep -i linux
fdisk -l /dev/block/mmcblk0 | grep -i linux
root@edison:/# fdisk -l /dev/block/mmcblk1 | grep -i linux
fdisk -l /dev/block/mmcblk1 | grep -i linux
/dev/block/mmcblk1p1 * 2 2 128 83 Linux
/dev/block/mmcblk1p2 5 8 512 83 Linux
/dev/block/mmcblk1p3 9 12 512 83 Linux
/dev/block/mmcblk1p5 17 20 512 83 Linux
/dev/block/mmcblk1p6 21 24 512 83 Linux
/dev/block/mmcblk1p7 25 56 4096 83 Linux
/dev/block/mmcblk1p8 57 60 512 83 Linux
/dev/block/mmcblk1p9 61 64 512 83 Linux
/dev/block/mmcblk1p10 65 72 1024 83 Linux
/dev/block/mmcblk1p11 73 88 2048 83 Linux
/dev/block/mmcblk1p12 89 92 512 83 Linux
/dev/block/mmcblk1p13 93 96 512 83 Linux
/dev/block/mmcblk1p14 97 128 4096 83 Linux
/dev/block/mmcblk1p15 129 192 8192 83 Linux
/dev/block/mmcblk1p16 193 264 9216 83 Linux
/dev/block/mmcblk1p17 265 360 12288 83 Linux
/dev/block/mmcblk1p18 361 364 512 83 Linux
/dev/block/mmcblk1p19 365 368 512 83 Linux
/dev/block/mmcblk1p20 369 400 4096 83 Linux
/dev/block/mmcblk1p21 417 4256 491520 83 Linux
/dev/block/mmcblk1p22 4257 9856 716800 83 Linux
/dev/block/mmcblk1p23 9857 12064 282624 83 Linux
/dev/block/mmcblk1p24 12065 22752 1368064 83 Linux
/dev/block/mmcblk1p25 22753 60607 4845440 83 Linux
/dev/block/mmcblk1p26 60608 60608 128 83 Linux
root@edison:/# ls -l /system/bin/mountosh
ls -l /system/bin/mountosh
-rwxr-xr-x root shell 5580 2011-09-22 08:37 mountosh
root@edison:/# ls -l /system/bin/mountosh.orig
ls -l /system/bin/mountosh.orig
/system/bin/mountosh.orig: No such file or directory
root@edison:/# busybox df -h | grep -i osh
busybox df -h | grep -i osh
/dev/block/webtop 1.3G 689.9M 621.7M 53% /osh
df: /mnt/sdcard/.android_secure: Invalid cross-device link
root@edison:/# ls -l /tmp/osh
ls -l /tmp/osh
/tmp/osh: No such file or directory
root@edison:/# exit
exit
shell@edison:/$ exit
exit

My phone is also a AT&T Atrix 2 MB865 from my friend, and the system information as below:

System: 55.11.16.MB865.ATT.en.US

Kernel:

2.6.35.7-gac99e44

hkdp76 @ ca25hre91 #1

Baseband:

2011-09-21 09:42 Off.Bld

LUD_EDISON_R1D7_PATCH_27_110921_0913

Build: 5.5.1-175_EDFFW1-16

Jim, thank you! I know that you have under no obligation to help me, and this will spend you so much time to do it.