ADB remount failure: remount failed:operation not permitted

ADB remount failure: remount failed:operation not permittedThe use of ADB is explained here again: Use commands frequently
ADB shell-Log in to the device shell, followed by direct execution of the command. 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-drive folder

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 Use the adb remount again to turn on Android device write mode. The problem is encountered when flashing mode: remount failed:operation not permitted using the following article methods, or not practical, and finally found the root of the problem: the compiled system is the user version number, it is not possible to use the command, make clean after the release version number is OKReferences Article http://blog.sina.com.cn/s/blog_4ba5b45e0102ek4k.htmlwhen debugging Android source code, let's say that you just changed a file in a folder. Then there's no need to compile the whole system again, just look at the android.mk under the file folder you changed ,
To see what the so library is generating, then the android mm command can be used to compile the module.

Prior to MM. Need to import env
$ source build/envsetup.sh
$ lunch
$ mm
It is natural to generate the specified so library under the corresponding folder in out, and then push it to the system's/system/lib folder. Assuming that your board is capable of ADB remount, naturally there is no problem, so assume that there is
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 folder, such as you can use ADB push to push the file to the System folder. or delete the system files.

Note that if you push the so library to the/system/lib folder, you need to restart the ability to take effect, in addition, assume that the power is restarted. It is best to perform the sync command to force the file system to write back to the NAND flash device , or it may cause data loss.

ADB remount failure: remount failed:operation not permitted