Android Phone instruction Operation explanation

Someone asked me a question about the root of Android phone, she said clearly itools display has been rooted, but she is not able to run on the phone requires root permissions of the app, such as titanium backup and so on. I told her the best way to confirm this is to go to/data/with the ADB instructions. Data path, and then execute Ls–al, if you can get the results of execution, without prompting "Permission denied", is rooted successfully, as shown.

And she asked, "How could she not change the permissions of the file while operating the ADB command?" Isn't the core of Android also Linux?

Yes, Android is the core of Linux yes, but ADB does not have a complete set of instructions, so in terms of instruction, and on the Linux/unix is slightly different. The most obvious is the use of the chmod directive.

When operating with the ADB instruction, the command chmod a+x test.sh will appear "Bad Mode" error message.

However, if you connect to an Android phone with SSH, and then execute the instruction chmod a+x test.sh, you will be able to add execute permissions to test.sh.

Is it possible to use the ADB command to manipulate the Android phone without changing the file permissions with the chmod directive? In fact, as long as the number of spring in the notation as a parameter. For example, the instruction is

chmod 777 test.sh

You can add write and execute permissions to the test.sh.

Android Phone instruction Operation explanation