Android Root Related

# Tags: Read blog

Highlights of this article:

1. Mobile phone system running under normal user rights, users can not be in the operating system files and data.

2. The principle of implementing root is basically: to exploit a system vulnerability, copy the SU executable file to the/system partition of the Android system (for example:/SYSTEM/XBIN/SU) and set the executable and setuid permissions for it with the chmod command

3. Prevent its (SU file) from being invoked by unauthorized applications, and there is usually an Android application to manage the behavior of the SU program

This article goes from: http://blog.csdn.net/zhgxhuaa/article/details/38043015

The principle of root

Rootby itself meansLinuxSystem ofRootaccount, the account has the supremacy of the entire system, all objects in the system can be manipulated, forAndroidfor mobile users.Rootmeans havingRootpermissions, in general, mobile phone manufacturers will shut down their phones for security reasons.Rootpermissions, the mobile phone system is running under the normal user rights, the user is unable to operate the file and data in the operating system. As a result, the current method of acquiring root is implemented using a system vulnerability. Different mobile phone manufacturers may have different vulnerabilities, it will lead to different phone root principle may be different. However, regardless of the principle of the implementation of root, eventually you will need tosuThe executable file is copied to the/system partition of the Android system (for example:/system/xbin/su) and use the chmod command to set executable and setuid permissions for it. In order to allow users to control the use of root privileges and prevent them from being called by unauthorized applications, there is usually an Android application to manage the behavior of the SU program. The basic principle of root is to use a system vulnerability to copy Su and the corresponding Android management app to the/system partition.

The most widely exploited system vulnerability is Zergrush, which applies to android2.2-2.3.6 systems, other vulnerabilities Gingerbreak, psneuter and so on.

Access to root vulnerability

Root has different vulnerabilities in getting different phone exploits. Here are a few common vulnerabilities that have been collected to get root privileges.

http://blog.csdn.net/hikame/article/details/8713297

http://www.kanxue.com/bbs/showthread.php?t=175129

http://blog.csdn.net/androidsecurity/article/details/13293789

Http://security.tencent.com/index.php/blog/msg/26

Http://www.saurik.com/id/17

Http://www.saurik.com/id/18

Http://www.saurik.com/id/19

Post-root applications

1. installation / Uninstall:

A, silent installation/uninstallation

B, SEC loading/second unloading

C, uninstall the app to save data

D, System built-in application uninstall

E. Remove residual data after unloading

F, Batch silent installation/uninstallation

2. Data backup:

A. Backup of the application installation package

B, backup of application data

C, System data backup

3. garbage cleanup, including:

A, Memory acceleration: Clean up a running process

B. Restrict Background startup

C. Clean up residual data after application uninstall

D, application cache (in the data directory)

E, one-click acceleration

4. Control notification Bar:

A. Interception and cleanup of notifications for third-party applications

B, the main implementation principle is: Process injection

5. Boot from:

A, by setting the priority and receiving the start-up broadcast service, monitoring to other boot services to kill

B, Process injection.

6. Block ads:

A, host blacklist mode (Adblock Plus is represented)

B, Process injection method (mobile phone Jinshan Poison PA as the representative)

7. Power Saving Control:

A, control CPU frequency

B, Background Wake control

C, lock screen to kill the backstage service, and so on.

8. Networked Control:

A, principle: iptable

B. Control network access when applied to WiFi and mobile internet

9. System Camouflage:

A, Camouflage phone model

B, camouflage location

C, camouflage operators

10. Apply Permissions Control

A. Disable some permissions for the app

B. Monitor third-party app permissions

11. Obtaining and modifying system Information

A. Get System configuration Information

B, get the log information such as dump

C, modify mobile phone switch motor painting

D, modify the mobile phone switch ring

E, modify the phone font

After the reprint of the summary:

About Su, in fact, this article is far from finished, however, as far as I am now, the current Linux fundamentals, I probably understand, should be so,

First to get a su file, write their own or where to get, not clear, but to push to the phone's executable directory

The following is probably the step :

ADB remount # (This is the first to let the read-only device writable, no, try ADB reboot DISEMMCWP) adb push su/system/bin/# (push to phone executable directory) ADB shell # (change file permissions in the shell, prompt should be $) Cd/system/bin/chmod 777 Susu # (try the effect, because at this point in the shell environment, the prompt becomes #)

(Personally, don't think about trying to make a clear point at a time, so you quickly forget it and repeat it regularly.) Trust me to reprint a related type again next time, and then I try I try to roughly understand it)

Android Root related