Eee Pad Transformer TF101 is rooted, we may like to install a native C executable which was generated by the NDK tool chain. A Busybox installer may be helpful since it provides the "cp" command. Then we may want to put this executable in /system. No matter we use "mv" or "cp", we still often get a "cross device link ERROR" or since /system is not writable unless we use something like this:
mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p1 /system
If the /system is not in mmcblock0p1, please use "mount" to find the right place.
Now we can use "cp" the executable to /system/xbin, and "chmod 744 ..." to be executable.
- ► 2013 (35)
- ► 2012 (99)
- Android Building the JNI Source Code in Eclipse
- One Click Rooting for Eee Pad Transformer TF101 8....
- Install a Native C Executable on Eee Pad Transform...
- Performance and Complexity Comparison between H.26...
- Using NDK to Call C code from Android Apps
- DM8168 EVM for $999
- DM6467 ARM9 Trouble Writing Memory Block at 0x1c40...
- Qualcomm to Lose HTC to Nvidia Tegra 3?
- Eee Pad Transformer TF101 Android 3.2.1 Root and a...
- HTML5 and Adobe Flash's Failures
- iOS 5.0.1 Update Failed
- DM6467 Latest CODECS
- Transformer Prime vs. iPad 2 vs. Kindle Fire vs. N...
- Intel and MIPS Bets on Android 4.0 Ice Cream Sandw...
- DM6467 Boot
- Xilinx ISE 13.3, Artix-7 and Virtex-7 XT
- DM8168 or C6-Integra EVM
- ▼ November (17)
- ► 2010 (99)
- ► 2009 (66)