ADB remount failure: remount failed:operation not permitted

ADB remount failure: remount failed:operation not permittedFor the use of ADB, here is another explanation: common commands
ADB shell-Log in to the device shell, followed by running commands directly. such as: adb shell rm-r/system/sd/app
adb pull-download files from your phone to your computer. such as: ADB pull/data/app_s/stock.apk c:\\stock.apk
ADB push-upload files from your computer to your phone. such as: adb push c:\\stock.apk/data/app_s/stock.apk
ADB install-Installs the software on the phone. Example: adb install c:\\apps2sd.apk
ADB Uninstall-Uninstall the software on your phone. such as: adb uninstall linda.apk

Capture System Log Information:

ADB logcat > D:\log.txt This will download the system information to the local D-Disk directory

If you are debugging a 3G module, you need to use this combination

ADB logcat-b Radio-b main-b system-v time d:/log.txt to crawl log information

Wait for ADB device

ADB wait-for-device-block until device is online

Use adb root permissions

adb root-restarts adb with root permissions

Use adb push PC Desktop driver file *.ko/vendor/modules/The file system is then forced to write back to the Nandflash to avoid losing power adb sync when using adb remount to reopen the Android device write mode, that is, the brush mode , encountered the problem: remount failed:operation not permitted using the method of the following article, or is not used, and finally found the root of the problem: the compiled system is the user version, it is not possible to use the command, made clean after the release version is OKReference article http://blog.sina.com.cn/s/blog_4ba5b45e0102ek4k.htmlin the Android source debugging, if you just change a file in a directory, then there is no need to recompile the entire system, just to see the file directory you modified android.mk,
To see what the so library is generating, the module can be compiled using the android mm command. Before mm, you need to import env
$ source build/envsetup.sh
$ lunch
$ mm
then naturally will be in the corresponding directory of out to generate the specified so library, and then need to push it to the system's/system/lib directory, if your board can adb remount words, naturally no problem, then, if it appears
remount failed:operation not permitted, how to do?

1. Determine if the phone is connected correctly
$  adb devices

2. Enter shell
$  adb shell

3. Shell input Commands (the first $ and # numbers in the command do not have to be entered)
$ su 
# mount-o rw,remount-t Yaffs2/dev/block/mtdblock3/system  
# chmod 777/system
# chmod 777/system/lib 
< Span style= "Word-wrap:break-word" ># exit

4. Then you have read and write access to the system directory, for example, you can use ADB push to push the file to the system directory or delete the system files.

Note that if you push the so library to the/system/lib directory, you need to restart to take effect, in addition, if the power is restarted, it is best to run the sync command, forcing the file system to write back to the NAND flash device , Failure to do so may result in data loss.

ADB remount failure: remount failed:operation not permitted