I like to start to play with some small tools, trick or treat, feeling after the start, the impression is more profound, but also can deeply understand some things, in this process, there will be some problems, start to solve, quite fun. The last time I played the phone at adb, I almost crashed it, and then with a little effort, I repaired it myself, to a false alarm. Tonight I tried to get the file into the box with ADB, and as a result, an adb Remount (to make the file system writable) prompted a denial of operation not permitted.
I initially thought it was a root issue, but if you want to get out of the shell and use ADB Remount, what’s the root issue?So, you have to do it inside the shell. The purpose of adb Remount is to make the file system available, so we might as well make the file directory writable directly in the shell with root permission, thus indirectly solving the problem, as follows (192.168.1.100 is the IP address of my Xiaomi phone) :
Of course, the key command can also be: mount -o Remount, RW-T yaffs2 /dev/block/mtdblock3 /system. In addition, the Windows path, we must not type a letter to write in, directly dragged into the file can ah.
Ok, when you encounter a problem, try to solve it, direct method, indirect method, white cat black cat can be. Now it’s done, so summarize and record it.
I initially thought it was a root issue, but if you want to get out of the shell and use ADB Remount, what’s the root issue?So, you have to do it inside the shell. The purpose of adb Remount is to make the file system available, so we might as well make the file directory writable directly in the shell with root permission, thus indirectly solving the problem, as follows (192.168.1.100 is the IP address of my Xiaomi phone) :
Of course, the key command can also be: mount -o Remount, RW-T yaffs2 /dev/block/mtdblock3 /system. In addition, the Windows path, we must not type a letter to write in, directly dragged into the file can ah.
Ok, when you encounter a problem, try to solve it, direct method, indirect method, white cat black cat can be. Now it’s done, so summarize and record it.
Read More:
- ADB remount failed: operation not permitted
- Android error: ADB port is occupied( adb.exe ,start-server’ failed — run manually if necessary)
- Android ADB command adb devices error: protocol fault (no status)
- An error is reported when an android phone visits the app webpage: net::ERR_PROXY_CONNECTION_FAILED
- How to Fix adb_server_notify: ADB server connection failed
- Solution to error: no devices found in ADB command
- Install Android SDK — stopping ADB server failed (code – 1)
- Android ADB simulates click events of sliding buttons
- Appium connecting to the ADB 5037 port of nocturnal simulator is occupied by itself
- [Android test] solution for error closed after the carriage return of the ADB shell
- On the error report after the command of ADB shell error:device not A solution of found
- Docker CentOS Failed to get D-Bus connection: Operation not permitted
- The ADB server port is changed to 10001, and appium cannot connect to the device
- linux docker Error Failed to get D-Bus connection: Operation not permitted
- npm ERR! Error: EPERM: operation not permitted, open ‘C:\Program Files\nodejs\node_ Solution to cache / xxx
- An error is displayed when virtualbox uses modifyhd command to expand capacity: Resize medium operation for this format is not implemented yet
- NPM report error: eperm: operation not permitted, unlink… Solution and clear cache_ modules
- [Solved] Appium Android, Appium settings and Unclock method will be installed every time the phone is started
- docker service Failed to get D-Bus connection: Operation not permitted
- NPM install Error: EPERM: operation not permitted, mkdir solution