CN102981835A - Android application program permanent Root permission acquiring method - Google Patents
Android application program permanent Root permission acquiring method Download PDFInfo
- Publication number
- CN102981835A CN102981835A CN2012104366499A CN201210436649A CN102981835A CN 102981835 A CN102981835 A CN 102981835A CN 2012104366499 A CN2012104366499 A CN 2012104366499A CN 201210436649 A CN201210436649 A CN 201210436649A CN 102981835 A CN102981835 A CN 102981835A
- Authority
- CN
- China
- Prior art keywords
- application program
- executable program
- android
- authority
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides an android application program permanent Root permission acquiring method. The method includes the steps of editing operations where Root permission is needed, compiling the operations into an executable program document, containing the executable program document into an application program which is authorized through a one-time subscriber unit (su) program, copying the executable program document to a /system/bin directory, modifying an owner and a group of the executable program document to be a root, and setting the subscriber unit identification (suid) position. As a result, the executable program document can have the Root permission every time the executable program document is executed so as to prevent an authorized window from popping out again. Due to changes of requirements, the executable program document is likely to need upgrading. Therefore, the executable program document needs achieving a self-upgrading function so as to prevent the authorized window from popping out again when upgrading. The android application program permanent Root permission acquiring method executes various operations with the identification of the Root. Even if the application program is reinstalled and upgraded, the su program authorization operation does not need repeating again. Therefore, the android application program permanent Root permission acquiring method brings great convenience to users.
Description
[technical field]
The present invention relates to the application program rights management techniques field on the Android system, relate in particular on the Android mobile phone of a kind of Root, the Android application program is forever obtained the method for Root authority.
[background technology]
In the Android Android system, third party application is to move with casual user's identity, and this is just so that the authority of this application program is restricted, in the time of will accessing or revise the Android system file such as application program, and will the failure because of insufficient permission.The Android mobile phone that has has now carried out the Root setting, and this Root is the super administrator account in the class unix systems such as Linux.For the Android mobile phone, usual said Root, be exactly to pass through the whole bag of tricks in fact, the su program file of system is copied to/the system/bin catalogue under, and the SuperUser empowerment management is installed, third party application can be carried out the operation that needs the Root authority by su program (the su program is the rights management file).But the mobile phone of Root setting, can third party application just directly have the operation of Root authority? actually this is not so, on the mobile phone of Root, can under/system/bin catalogue, deposit the file of a su program by name, and the SuperUser(empowerment management is installed) application program.Other application programs are wanted to carry out with the Root authority, just must carry out shell-command by the su program, and this moment, SuperUser will eject the mandate dialog box, and the user must click permission, and order could successfully be performed.When click allows, if do not select " remembeing " option, use so when carrying out shell-command by the su program at every turn, all can eject and authorize the dialog box of reminding.In addition, if application program updating, even if remembered so before to allow to have operated, when carrying out shell-command by the su program again, also to again carry out repetitive endowment by the su program.
The dialog box that the mandate of ejecting is in addition reminded can be brought following problem: when the third party on the operating handset uses on an interface of mobile phone for the user, authorize the ejection of frame not have too large problem, because user's this moment is seeing that mobile phone is in some operation of execution, the user can find timely to authorize dialog box to eject and confirm, just operation is more loaded down with trivial details.But, the operation interface of some application program and no longer on the mobile phone, but on the pc machine, the user is connected to the pc machine with mobile phone, then come managing mobile phone by the pc machine, at this moment, the user can't remove to pay close attention to mobile phone screen, so, the user just can not in time find and confirm when authorizing dialog box to eject, and can authorize frame to show because mobile phone enters screen protection, so just cause authorization failure.Certainly, the user can choose " remembeing " option when authorizing for the first time, and just need not authorize next time again, but application program is often to upgrade version, after the renewal, re-starts again mandate, brings very big inconvenience for user's use.
A kind of " the application program method for managing dynamic permission under the Android platform " is provided in the prior art, see that publication number is: CN102289633A, open day be: the Chinese patent of 2011.12.21 comprises that Dynamic Selection was preserved self System Privileges table when application program was installed; After the installation, the user revises described System Privileges table by the man-machine interface Dynamic Selection; When access needed the API of authority, the Android platform judged whether that according to the record in the System Privileges table of this application program this API is disabled; When described API was disabled, whether this application program was selected to revise by the man-machine interface prompting user; If user selection is revised authority, the Android platform allows the described API of this application access, otherwise this application program withdraws from access.This right management method, the user can reach the authority that the personal experience revises application program at any time as required, thereby can prevent to a great extent the malice access resources of application program, the hazardous acts such as modification, steal personal information.If but the application program under the method Android platform is when having renewal, the rights management of this setting will be lost efficacy, and also will again advance configuration, troublesome poeration.
Here it is to be noted in order to allow audit crew be more readily understood the present invention:
1, among the Linux, the problem of file permission:
File permission: each Linux file has four kinds of access rights: readable (r), can write (w), can carry out (x), lack of competence (-).
Authority classification: the owner, group membership, other users.The authority of every class can be used letter representation, represents such as rwxrwxr-x: namely the owner and group membership have the authority of reading and writing, execution, and other users only have the authority reading and carry out (be the rwx ' owner ' rwx ' group membership ' other users of r-x ' ').Digital representation: so-called digital representation, refer to r, w and x are represented with 4,2,1 respectively, what do not have granted rights (-) then is 0, then the authority addition, as follows: file permission is rwxr-xr-x, is converted to numeral for (421) (401) (401), is expressed as 755 after the addition.
2, Linux user and grouping:
Linux is a multi-task and multi-user operating system.
Multitask: operation in the time of on a plurality of foreground applications and the background service program macroscopic view.
The multi-user: a plurality of users are the login system operation simultaneously; The protection and limitation mechanism of setting up for the privacy that guarantees the user.
All there is a power user in the common multi-user system, the root user among the Linux for example, administrator in the Windows system etc., can exist several to have other users of different authority classification grades in the system, such as the domestic consumer that is set up by the power user etc., Linux distribution version all requires to set up a domestic consumer when mounted mostly at present, and uses this user to log in.
3, user's group:
Can divide into groups to the user, user's group can comprise a plurality of users, and a user also can belong to a plurality of groupings simultaneously.
For example, following grouping and user are arranged:
Grouping group1 comprises user user1, user2
Grouping group2 comprises user user2
Create a file f by the user1 among the group1 now, specifying its authority is 775, and user1 and user2 have the authority of reading and writing, execution, the authority that the user2 among the group2 then only reads and carries out to file f so
4, the flag suid in the system:
Suid is the meaning of Set User ID
If a file has been set up the suid flag, but can shows on the execute bit of possessory authority and can carry out on the position of (x), for example:
Rwsr-xr-x represents that but execute bit is set up in the possessory authority in the classification of suid and authority.
The numeral that digital representation: suid is corresponding is 4, just is expressed as 4755 such as rwsr-xr-x
The effect of suid: allow when originally not having the user of corresponding authority to move this program, can access the resource (namely allowing some resources not have the access rights that had of access rights) that he does not have the authority access.
For example, user user1 and user2 are arranged; Create an ordinary file f by user user1 now, its authority is rwxr-xr-x(755), and create an executable file r, and its authority is that rwxr-xr-x(does not arrange suid), this moment is by user2 working procedure r, the validated user id(euid of r) be exactly user2, because user2 is to the unwritten authority of file f, so the r program also just can't revised file f; If be provided with the suid of file f, namely authority changes rwsr-xr-x(4755 into), the euid of r will be set to its possessory id again by user2 working procedure r this moment, i.e. user1, also just can revised file f.
[summary of the invention]
The technical problem to be solved in the present invention is to provide a kind of Android application program forever to obtain the method for Root authority, and when it solved application program with Root identity fill order, SuperUser can repeatedly eject the problem of reminding of authorizing.
The present invention is achieved in that a kind of Android application program forever obtains the method for Root authority, comprises the steps:
Step 1, the operation that needs in the Android application program to use the Root authority is write by the C/C++ language, and be compiled into an Android system executable program file, and described executable program file can realize self-upgrade function with the function of communicating by letter of Android application program; Executable program file is packaged in the Android application program;
Step 2, judge at Android system/whether have described executable program file under the catalogue of system/bin, no, then enter step 3; Be, judge then whether executable program file needs upgrading, upgrade, then the Android application program is set up with this executable program file and is communicated by letter, and calls self-upgrade function, this executable program file is carried out upgrading processing, and change step 8 over to; Do not upgrade, then directly enter step 8;
The su program of step 3, Android application program operation Android system is carried out the first time to the operation user and is authorized;
Step 4, with Android system /the system catalogue weighs carry for can write state;
Step 5, with Android system /authority of system/bin catalogue arranges, with guarantee the Android application program right/catalogue of system/bin has the authority of writing;
Step 6, described executable program file is copied under the catalogue of described/system/bin, and revise this executable program file authority classification the owner and under be grouped into Root;
Step 7, the suid flag of executable program file is set, the suid flag is set after, executable program file just can be performed by the Android application program with possessory identity, namely has the operation of Root authority;
Step 8, Android application program are carried out executable program file and are communicated by letter with its foundation, this moment, the Android application program need to be used the operation of Root authority as long as carry out by executable program file, need not to carry out repetitive endowment by the su program of Android system.
The present invention has following advantage: the present invention writes the operation that needs are used the Root authority, and be compiled into an executable program file, this executable program file is disposed, arranged, can make so the each execution of this document all have the Root authority, thereby avoid again ejecting the mandate frame.Because the change of demand, this document program may need upgrading, so file need to realize the function of oneself's upgrading, needs again to eject when avoiding upgrading and authorizes frame.The present invention carries out various operations by this document with the identity of Root, even if application program is reset, upgraded, also need not to carry out the su program authorization operation of repetition again, brings great convenience for user's use.
[description of drawings]
Fig. 1 is the inventive method schematic flow sheet.
[embodiment]
As shown in Figure 1, a kind of Android application program of the present invention is forever obtained the method for Root authority, comprises the steps:
Step 1, the operation that needs in the Android application program to use the Root authority is write by the C/C++ language, and be compiled into an Android system executable program file (as, the name of this executable program file is called mySu), and described executable program file can realize self-upgrade function with the function of communicating by letter of Android application program; Executable program file is packaged in the Android application program;
Step 2, judge at Android system/whether have described executable program file under the catalogue of system/bin, no, then enter step 3; Be, judge then whether executable program file needs upgrading, upgrade, then the Android application program is set up communicate by letter (borrowing during this communication has the function of communicating by letter in executable program file with the Android application program) with this executable program file, and call self-upgrade function, this executable program file is carried out upgrading processing, and change step 8 over to; Do not upgrade, then directly enter step 8;
The su program of step 3, Android application program operation Android system is carried out the first time to the operation user and is authorized; It is specially: the su program of Android application program operation Android system, and obtain the output stream of su program, su order afterwards can directly write order and execution toward output stream, and need not to rerun the su program, so just only need subscriber authorisation once to get final product, at this moment, the output stream of past su program writes an arbitrarily character order, and (this character order is inessential order, such as " id "), this character order mainly is in order to allow the SuperUser of Android system can eject the mandate dialog box, at this moment, the SuperUser of Android system can eject the mandate dialog box, and the operation user clicks permission, then continues to carry out described step 4, the operation user clicks refusal, then process ends.
Step 4, with Android system /the system catalogue weighs carry for can write state; It is specially: the output stream toward the su program writes the first order, with Android system /the system catalogue weighs carry for can write state, this first order is: " mount-o remount-w-t[type] [device]/system ", wherein [type] is for wanting the file system type of carry, [device] is for wanting the equipment of carry, these two are/relevant parameter of system catalogue carry, are to obtain by the shell-command of carrying out Android system.
Step 5, with Android system /authority of system/bin catalogue arranges, with guarantee the Android application program right/catalogue of system/bin has the authority of writing; It is specially: the output stream toward the su program writes the second order, with Android system /authority of system/bin catalogue changes 777 into, with guarantee the Android application program right/catalogue of system/bin has the authority of writing, this second order is: " chmod 777/system/bin ".
Step 6, described executable program file is copied under the catalogue of described/system/bin, and revise this executable program file authority classification the owner and under be grouped into Root; It is specially: the output stream toward the su program writes the 3rd order, executable program file is copied under the catalogue of described/system/bin, the 3rd order is " dd if=[fromPath] of=[toPath] ", wherein [fromPath] is the path at executable program file place this moment, [toPath] is the path that will copy to, namely/and the title of system/bin/ executable program file; And the output stream of past su program writes the 4th order, revise the classification of this executable program file authority the owner and under be grouped into root, the 4th order is " title of chown root:root/system/bin/ executable program file (be " mySu ", this title also can be replaced with other name) ".
Step 7, the suid flag of executable program file is set, the suid flag is set after, executable program file just can be performed by the Android application program with possessory identity, namely has the operation of Root authority; It is specially: the output stream toward the su program writes the 5th order, the suid flag of executable program file is set, and the executable program file authority is set to readable the execution, be that the executable program file authority is set to 4755, wherein " 4 " are the suid flags, executable program file just can be performed by the Android application program with possessory identity, namely has the operation of Root authority; Application program can forever be obtained the operation of Root authority like this; The 5th order is: " title of chmod 4755/system/bin/ executable program file (being " mySu ") ".
Step 8, Android application program are carried out executable program file and are communicated by letter with its foundation, this moment, the Android application program need to be used the operation of Root authority as long as carry out by executable program file, need not to carry out repetitive endowment by the su program of Android system.
Wherein, the operation of described Root authority comprises: obtain file directory, mourn in silence installation procedure and Uninstaller etc.
Here it is worth mentioning that:
The difference of carry and heavy carry, carry:
In the linux system, memory device need to be mounted to certain catalogue, we could normally use in file management; Then generally can see the carry information of each catalogue by carrying out the mount order among the shell, for example :/dev/block/mmcblk0p9/system ext4 ro; This information represents: memory device "/dev/block/mmcblk0p9 " is mounted to/the system catalogue, and its file system type is " ext4 ", and its access limit is " ro " (read-only)
Heavy carry: generally carry out the remount order by shell and carry out again carry memory device: for example: " mount-o remount-w-t ext4/dev/block/mmcblk0p9/system ", the heavy carry of expression general/system, its file system type is " ext4 ", its memory device is "/dev/block/mmcblk0p9 ", its access limit is " w ", i.e. readable writing.What relate in the step 4 is the operation that weighs carry.
In a word, the present invention carries out various operations by this document with the identity of Root, even if application program is reset, upgraded, also need not to carry out the su program authorization operation of repetition again, brings great convenience for user's use.
The above only is preferred embodiment of the present invention, and all equalizations of doing according to the present patent application claim change and modify, and all should belong to covering scope of the present invention.
Claims (7)
1. an Android application program is forever obtained the method for Root authority, it is characterized in that: comprise the steps:
Step 1, the operation that needs in the Android application program to use the Root authority is write by the C/C++ language, and be compiled into an Android system executable program file, and described executable program file can realize self-upgrade function with the function of communicating by letter of Android application program; Executable program file is packaged in the Android application program;
Step 2, judge at Android system/whether have described executable program file under the catalogue of system/bin, no, then enter step 3; Be, judge then whether executable program file needs upgrading, upgrade, then the Android application program is set up with this executable program file and is communicated by letter, and calls self-upgrade function, this executable program file is carried out upgrading processing, and change step 8 over to; Do not upgrade, then directly enter step 8;
The su program of step 3, Android application program operation Android system is carried out the first time to the operation user and is authorized;
Step 4, with Android system /the system catalogue weighs carry for can write state;
Step 5, with Android system /authority of system/bin catalogue arranges, with guarantee the Android application program right/catalogue of system/bin has the authority of writing;
Step 6, described executable program file is copied under the catalogue of described/system/bin, and revise this executable program file authority classification the owner and under be grouped into Root;
Step 7, the suid flag of executable program file is set, the suid flag is set after, executable program file just can be performed by the Android application program with possessory identity, namely has the operation of Root authority;
Step 8, Android application program are carried out executable program file and are communicated by letter with its foundation, this moment, the Android application program need to be used the operation of Root authority as long as carry out by executable program file, need not to carry out repetitive endowment by the su program of Android system.
2. Android application program according to claim 1 is forever obtained the method for Root authority, it is characterized in that: the operation of described Root authority comprises: obtain file directory, mourn in silence installation procedure and Uninstaller.
3. Android application program according to claim 1 is forever obtained the method for Root authority, it is characterized in that: described step 3 is specially: the su program of Android application program operation Android system, and obtain the output stream of su program, su order afterwards can directly write order and execution toward output stream, at this moment, output stream toward the su program writes an arbitrarily character order, the SuperUser of Android system can eject the mandate dialog box, the operation user clicks permission, then continue to carry out described step 4, the operation user clicks refusal, then process ends.
4. Android application program according to claim 1 is forever obtained the method for Root authority, it is characterized in that: described step 4 is specially: the output stream toward the su program writes the first order, with Android system /the system catalogue weighs carry for can write state, this first order is: " mount-oremount-w – t[type] [device]/system ", wherein [type] is for wanting the file system type of carry, [device] is for wanting the equipment of carry, these two are/relevant parameter of system catalogue carry, are to obtain by the shell-command of carrying out Android system.
5. Android application program according to claim 1 is forever obtained the method for Root authority, it is characterized in that: described step 5 is specially: the output stream toward the su program writes the second order, with Android system /authority of system/bin catalogue changes 777 into, with guarantee the Android application program right/catalogue of system/bin has the authority of writing, this second order is: " chmod 777/system/bin ".
6. Android application program according to claim 1 is forever obtained the method for Root authority, it is characterized in that: described step 6 is specially: the output stream toward the su program writes the 3rd order, executable program file is copied under the catalogue of described/system/bin, the 3rd order is " dd if=[fromPath] of=[toPath] ", wherein [fromPath] is the path at executable program file place this moment, [toPath] is the path that will copy to, namely/and the title of system/bin/ executable program file; And write the 4th order toward the output stream of su program, revise this executable program file authority classification the owner and under be grouped into root, the 4th order is " title of chown root:root/system/bin/ executable program file ".
7. Android application program according to claim 1 is forever obtained the method for Root authority, it is characterized in that: described step 7 is specially: the output stream toward the su program writes the 5th order, the suid flag of executable program file is set, and the executable program file authority is set to readable the execution, be that the executable program file authority is set to 4755, wherein " 4 " are the suid flags, executable program file just can be performed by the Android application program with possessory identity, namely has the operation of Root authority; The 5th order is: " title of chmod 4755/system/bin/ executable program file ".
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210436649.9A CN102981835B (en) | 2012-11-02 | 2012-11-02 | Android application program permanent Root permission acquiring method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210436649.9A CN102981835B (en) | 2012-11-02 | 2012-11-02 | Android application program permanent Root permission acquiring method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102981835A true CN102981835A (en) | 2013-03-20 |
| CN102981835B CN102981835B (en) | 2015-06-10 |
Family
ID=47855900
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210436649.9A Active CN102981835B (en) | 2012-11-02 | 2012-11-02 | Android application program permanent Root permission acquiring method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102981835B (en) |
Cited By (44)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103152366A (en) * | 2013-04-10 | 2013-06-12 | 珠海市魅族科技有限公司 | Method, terminal and server for obtaining terminal authorization |
| CN103198265A (en) * | 2013-03-28 | 2013-07-10 | 上海斐讯数据通信技术有限公司 | Method for starting root permission of mobile device |
| CN103324482A (en) * | 2013-06-27 | 2013-09-25 | 苏州创智宏云信息科技有限公司 | Android one-key root permission software |
| CN103324537A (en) * | 2013-05-17 | 2013-09-25 | Tcl集团股份有限公司 | Resource sharing method and device |
| CN103365685A (en) * | 2013-06-03 | 2013-10-23 | 深圳创维无线技术有限公司 | Super authority method and super authority device based on android |
| CN103473502A (en) * | 2013-09-16 | 2013-12-25 | 惠州Tcl移动通信有限公司 | Method and system for acquiring Root rights of android-based mobile terminal |
| CN103530534A (en) * | 2013-09-23 | 2014-01-22 | 北京理工大学 | Android program ROOT authorization method based on signature verification |
| CN103559431A (en) * | 2013-11-11 | 2014-02-05 | 北京国双科技有限公司 | Detection method, device and system of Android system user permission |
| CN103714287A (en) * | 2013-12-25 | 2014-04-09 | 北京奇虎科技有限公司 | Method and device for obtaining temporary Root authority |
| CN103826215A (en) * | 2014-02-11 | 2014-05-28 | 北京奇虎科技有限公司 | Method and apparatus for carrying out root authority management at terminal equipment |
| CN103888294A (en) * | 2014-02-28 | 2014-06-25 | 广州视睿电子科技有限公司 | Method and device for assigning router in Android system |
| CN104063303A (en) * | 2014-06-30 | 2014-09-24 | 上海斐讯数据通信技术有限公司 | Method for acquiring and freeing root permissions |
| CN104134036A (en) * | 2014-07-26 | 2014-11-05 | 珠海市君天电子科技有限公司 | Method and device for obtaining Root permission |
| WO2014183534A1 (en) * | 2013-11-12 | 2014-11-20 | 中兴通讯股份有限公司 | Method and apparatus of automatically backing up application data and performing restoration as required |
| CN104199711A (en) * | 2014-09-29 | 2014-12-10 | 北京奇虎科技有限公司 | Method and device for creating root access |
| CN104217158A (en) * | 2014-09-17 | 2014-12-17 | 青岛海信移动通信技术股份有限公司 | Method for detecting system state of intelligent terminal and intelligent terminal |
| CN104252587A (en) * | 2013-06-25 | 2014-12-31 | 腾讯科技（深圳）有限公司 | File pulling method, device and system |
| CN104348628A (en) * | 2014-12-01 | 2015-02-11 | 北京奇虎科技有限公司 | Method and device for obtaining local Root authority |
| CN104391729A (en) * | 2014-12-19 | 2015-03-04 | 北京奇虎科技有限公司 | Root privilege based procedure upgrading method and device |
| CN104484611A (en) * | 2014-11-10 | 2015-04-01 | 福建联迪商用设备有限公司 | Partition-mounting control method and device of Android system |
| CN104506639A (en) * | 2014-12-29 | 2015-04-08 | 北京奇虎科技有限公司 | Root right acquiring method and device |
| CN104572158A (en) * | 2013-10-29 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Method and device for running application program by superuser identity |
| CN104714760A (en) * | 2015-03-05 | 2015-06-17 | 青岛海信宽带多媒体技术有限公司 | Method and device for read and write storage device |
| CN104809403A (en) * | 2014-01-24 | 2015-07-29 | 红板凳科技股份有限公司 | Root-preventing white screen method |
| CN105243325A (en) * | 2015-09-29 | 2016-01-13 | 北京奇虎科技有限公司 | Method for residual process file in mobile terminal, mobile terminal and server |
| CN105630544A (en) * | 2015-12-21 | 2016-06-01 | 小米科技有限责任公司 | System updating control method and apparatus as well as server device |
| CN105956457A (en) * | 2016-04-27 | 2016-09-21 | 四川秘无痕信息安全技术有限责任公司 | Method for frequently executing root privilege operations and acquiring real-time result feedbacks |
| CN106529332A (en) * | 2016-10-25 | 2017-03-22 | 广东欧珀移动通信有限公司 | Permission control method and apparatus for mobile terminal, and mobile terminal |
| CN106559546A (en) * | 2015-09-28 | 2017-04-05 | 腾讯科技（深圳）有限公司 | Method and apparatus of the control software using network internet |
| CN106650408A (en) * | 2016-12-09 | 2017-05-10 | 武汉斗鱼网络科技有限公司 | Method and system used for judging existence of root authority in Android system |
| CN106919812A (en) * | 2015-12-26 | 2017-07-04 | 腾讯科技（深圳）有限公司 | A kind of application process right management method and device |
| CN107068150A (en) * | 2017-05-03 | 2017-08-18 | 安利军 | A kind of Android intelligent sounds control method and system |
| CN108595214A (en) * | 2018-04-11 | 2018-09-28 | 北京海杭通讯科技有限公司 | Android user versions obtain the method and system of root privileges under SELinux compulsory modes |
| CN108920945A (en) * | 2018-05-02 | 2018-11-30 | 广州视源电子科技股份有限公司 | root authority obtaining and deleting method and device, terminal equipment and storage medium |
| CN109271781A (en) * | 2018-09-13 | 2019-01-25 | 西安交通大学 | A kind of application program acquisition super authority behavioral value method and system based on kernel |
| CN109815726A (en) * | 2017-11-21 | 2019-05-28 | 中标软件有限公司 | The method and its background program building method of ordinary user's modification system file |
| CN109815680A (en) * | 2018-12-27 | 2019-05-28 | 歌尔股份有限公司 | Management method, device, terminal device and the storage medium of application permission |
| CN110457894A (en) * | 2019-08-06 | 2019-11-15 | 惠州Tcl移动通信有限公司 | Distribution method, device, storage medium and the terminal device of root authority |
| CN113254916A (en) * | 2021-05-25 | 2021-08-13 | 深圳市瑞驰信息技术有限公司 | Implementation method of root switch of android system |
| CN113688377A (en) * | 2021-07-27 | 2021-11-23 | 青岛中科英泰商用系统股份有限公司 | Root authority management method and system of Android device |
| CN114090055A (en) * | 2021-11-10 | 2022-02-25 | 北京鲸鲮信息系统技术有限公司 | Application program updating method and device, terminal and storage medium |
| CN115391794A (en) * | 2022-10-27 | 2022-11-25 | 中孚安全技术有限公司 | Method, system and equipment for adding permission in application program starting process |
| CN115499420A (en) * | 2022-09-14 | 2022-12-20 | 苏州龙信信息科技有限公司 | Data transmission method and device, electronic equipment and storage medium |
| CN116702163A (en) * | 2022-09-27 | 2023-09-05 | 荣耀终端有限公司 | Authority management method and terminal equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030028508A1 (en) * | 2001-08-06 | 2003-02-06 | Joseph Quinlan | Method and apparatus for controlling the performance of a file system mount operation by a user lacking superuser authority |
| CN102289633A (en) * | 2011-09-02 | 2011-12-21 | 广东欧珀移动通信有限公司 | Method for managing dynamic permission of application program under Android platform |
-
2012
- 2012-11-02 CN CN201210436649.9A patent/CN102981835B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030028508A1 (en) * | 2001-08-06 | 2003-02-06 | Joseph Quinlan | Method and apparatus for controlling the performance of a file system mount operation by a user lacking superuser authority |
| CN102289633A (en) * | 2011-09-02 | 2011-12-21 | 广东欧珀移动通信有限公司 | Method for managing dynamic permission of application program under Android platform |
Non-Patent Citations (3)
| Title |
|---|
| AIY_YA: "《Android root权限获取原理详解》", 9 August 2012 * |
| COLIN: "《Android root权限破解原理分析》", 30 August 2011 * |
| 姜颖韬: "浅析Android平台ROOT权限", 《科技经济市场》 * |
Cited By (66)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103198265A (en) * | 2013-03-28 | 2013-07-10 | 上海斐讯数据通信技术有限公司 | Method for starting root permission of mobile device |
| CN103152366A (en) * | 2013-04-10 | 2013-06-12 | 珠海市魅族科技有限公司 | Method, terminal and server for obtaining terminal authorization |
| CN103152366B (en) * | 2013-04-10 | 2015-12-23 | 魅族科技（中国）有限公司 | Obtain the method for terminal authorization, terminal and server |
| CN103324537A (en) * | 2013-05-17 | 2013-09-25 | Tcl集团股份有限公司 | Resource sharing method and device |
| CN103365685A (en) * | 2013-06-03 | 2013-10-23 | 深圳创维无线技术有限公司 | Super authority method and super authority device based on android |
| CN104252587B (en) * | 2013-06-25 | 2018-04-27 | 腾讯科技（深圳）有限公司 | Pull the method, apparatus and system of file |
| CN104252587A (en) * | 2013-06-25 | 2014-12-31 | 腾讯科技（深圳）有限公司 | File pulling method, device and system |
| CN103324482A (en) * | 2013-06-27 | 2013-09-25 | 苏州创智宏云信息科技有限公司 | Android one-key root permission software |
| CN103473502A (en) * | 2013-09-16 | 2013-12-25 | 惠州Tcl移动通信有限公司 | Method and system for acquiring Root rights of android-based mobile terminal |
| CN103530534A (en) * | 2013-09-23 | 2014-01-22 | 北京理工大学 | Android program ROOT authorization method based on signature verification |
| CN103530534B (en) * | 2013-09-23 | 2016-06-29 | 北京理工大学 | A kind of Android program ROOT authorization method based on signature verification |
| CN104572158A (en) * | 2013-10-29 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Method and device for running application program by superuser identity |
| CN104572158B (en) * | 2013-10-29 | 2019-01-04 | 腾讯科技（深圳）有限公司 | One kind running application program method and device with power user's identity |
| CN103559431A (en) * | 2013-11-11 | 2014-02-05 | 北京国双科技有限公司 | Detection method, device and system of Android system user permission |
| US9864657B2 (en) | 2013-11-12 | 2018-01-09 | Zte Corporation | Method and apparatus of automatically backing up application data and performing restoration as required |
| WO2014183534A1 (en) * | 2013-11-12 | 2014-11-20 | 中兴通讯股份有限公司 | Method and apparatus of automatically backing up application data and performing restoration as required |
| CN104636375A (en) * | 2013-11-12 | 2015-05-20 | 中兴通讯股份有限公司 | Method and device for automatically backing up application data and restoring application data according to needs |
| CN104636375B (en) * | 2013-11-12 | 2019-05-07 | 中兴通讯股份有限公司 | A kind of automated back-up application data and the method and device restored on demand |
| CN103714287B (en) * | 2013-12-25 | 2015-07-01 | 北京奇虎科技有限公司 | Method and device for obtaining temporary Root authority |
| CN103714287A (en) * | 2013-12-25 | 2014-04-09 | 北京奇虎科技有限公司 | Method and device for obtaining temporary Root authority |
| CN104809403A (en) * | 2014-01-24 | 2015-07-29 | 红板凳科技股份有限公司 | Root-preventing white screen method |
| CN103826215B (en) * | 2014-02-11 | 2018-03-02 | 北京奇虎科技有限公司 | A kind of method and apparatus for carrying out Root authority management on the terminal device |
| CN103826215A (en) * | 2014-02-11 | 2014-05-28 | 北京奇虎科技有限公司 | Method and apparatus for carrying out root authority management at terminal equipment |
| CN103888294A (en) * | 2014-02-28 | 2014-06-25 | 广州视睿电子科技有限公司 | Method and device for assigning router in Android system |
| CN103888294B (en) * | 2014-02-28 | 2017-10-27 | 广州视睿电子科技有限公司 | Method and device for assigning router in Android system |
| CN104063303A (en) * | 2014-06-30 | 2014-09-24 | 上海斐讯数据通信技术有限公司 | Method for acquiring and freeing root permissions |
| CN104063303B (en) * | 2014-06-30 | 2019-07-16 | 上海斐讯数据通信技术有限公司 | A method of obtaining and discharge root authority |
| CN104134036A (en) * | 2014-07-26 | 2014-11-05 | 珠海市君天电子科技有限公司 | Method and device for obtaining Root permission |
| CN104134036B (en) * | 2014-07-26 | 2017-05-10 | 珠海市君天电子科技有限公司 | Method and device for obtaining Root permission |
| CN104217158A (en) * | 2014-09-17 | 2014-12-17 | 青岛海信移动通信技术股份有限公司 | Method for detecting system state of intelligent terminal and intelligent terminal |
| CN104199711A (en) * | 2014-09-29 | 2014-12-10 | 北京奇虎科技有限公司 | Method and device for creating root access |
| CN104199711B (en) * | 2014-09-29 | 2018-02-13 | 北京奇虎科技有限公司 | The method and apparatus for establishing root authority |
| CN104484611A (en) * | 2014-11-10 | 2015-04-01 | 福建联迪商用设备有限公司 | Partition-mounting control method and device of Android system |
| CN104348628A (en) * | 2014-12-01 | 2015-02-11 | 北京奇虎科技有限公司 | Method and device for obtaining local Root authority |
| CN104391729B (en) * | 2014-12-19 | 2018-05-01 | 北京奇虎科技有限公司 | Programme upgrade method and device based on Root authority |
| CN104391729A (en) * | 2014-12-19 | 2015-03-04 | 北京奇虎科技有限公司 | Root privilege based procedure upgrading method and device |
| CN104506639A (en) * | 2014-12-29 | 2015-04-08 | 北京奇虎科技有限公司 | Root right acquiring method and device |
| CN104714760B (en) * | 2015-03-05 | 2018-05-15 | 青岛海信宽带多媒体技术有限公司 | A kind of method and device for reading and writing storage device |
| CN104714760A (en) * | 2015-03-05 | 2015-06-17 | 青岛海信宽带多媒体技术有限公司 | Method and device for read and write storage device |
| CN106559546A (en) * | 2015-09-28 | 2017-04-05 | 腾讯科技（深圳）有限公司 | Method and apparatus of the control software using network internet |
| CN105243325A (en) * | 2015-09-29 | 2016-01-13 | 北京奇虎科技有限公司 | Method for residual process file in mobile terminal, mobile terminal and server |
| CN105630544A (en) * | 2015-12-21 | 2016-06-01 | 小米科技有限责任公司 | System updating control method and apparatus as well as server device |
| CN106919812A (en) * | 2015-12-26 | 2017-07-04 | 腾讯科技（深圳）有限公司 | A kind of application process right management method and device |
| CN106919812B (en) * | 2015-12-26 | 2020-06-16 | 腾讯科技（深圳）有限公司 | Application process authority management method and device |
| CN105956457B (en) * | 2016-04-27 | 2018-11-13 | 四川秘无痕信息安全技术有限责任公司 | A method of it frequently executing root authority and operates and obtain real-time results feedback |
| CN105956457A (en) * | 2016-04-27 | 2016-09-21 | 四川秘无痕信息安全技术有限责任公司 | Method for frequently executing root privilege operations and acquiring real-time result feedbacks |
| CN106529332B (en) * | 2016-10-25 | 2019-08-13 | Oppo广东移动通信有限公司 | A kind of authority control method of mobile terminal, device and mobile terminal |
| CN106529332A (en) * | 2016-10-25 | 2017-03-22 | 广东欧珀移动通信有限公司 | Permission control method and apparatus for mobile terminal, and mobile terminal |
| CN106650408B (en) * | 2016-12-09 | 2020-08-04 | 武汉斗鱼网络科技有限公司 | Method and system for judging whether android system has root permission |
| CN106650408A (en) * | 2016-12-09 | 2017-05-10 | 武汉斗鱼网络科技有限公司 | Method and system used for judging existence of root authority in Android system |
| CN107068150A (en) * | 2017-05-03 | 2017-08-18 | 安利军 | A kind of Android intelligent sounds control method and system |
| CN109815726A (en) * | 2017-11-21 | 2019-05-28 | 中标软件有限公司 | The method and its background program building method of ordinary user's modification system file |
| CN108595214A (en) * | 2018-04-11 | 2018-09-28 | 北京海杭通讯科技有限公司 | Android user versions obtain the method and system of root privileges under SELinux compulsory modes |
| CN108920945B (en) * | 2018-05-02 | 2020-10-02 | 广州视源电子科技股份有限公司 | root authority obtaining and deleting method and device, terminal equipment and storage medium |
| CN108920945A (en) * | 2018-05-02 | 2018-11-30 | 广州视源电子科技股份有限公司 | root authority obtaining and deleting method and device, terminal equipment and storage medium |
| CN109271781A (en) * | 2018-09-13 | 2019-01-25 | 西安交通大学 | A kind of application program acquisition super authority behavioral value method and system based on kernel |
| CN109815680A (en) * | 2018-12-27 | 2019-05-28 | 歌尔股份有限公司 | Management method, device, terminal device and the storage medium of application permission |
| CN109815680B (en) * | 2018-12-27 | 2021-08-31 | 歌尔股份有限公司 | Application authority management method and device, terminal equipment and storage medium |
| CN110457894A (en) * | 2019-08-06 | 2019-11-15 | 惠州Tcl移动通信有限公司 | Distribution method, device, storage medium and the terminal device of root authority |
| CN113254916A (en) * | 2021-05-25 | 2021-08-13 | 深圳市瑞驰信息技术有限公司 | Implementation method of root switch of android system |
| CN113688377A (en) * | 2021-07-27 | 2021-11-23 | 青岛中科英泰商用系统股份有限公司 | Root authority management method and system of Android device |
| CN113688377B (en) * | 2021-07-27 | 2024-07-09 | 青岛中科英泰商用系统股份有限公司 | Root authority management method and system of Android device |
| CN114090055A (en) * | 2021-11-10 | 2022-02-25 | 北京鲸鲮信息系统技术有限公司 | Application program updating method and device, terminal and storage medium |
| CN115499420A (en) * | 2022-09-14 | 2022-12-20 | 苏州龙信信息科技有限公司 | Data transmission method and device, electronic equipment and storage medium |
| CN116702163A (en) * | 2022-09-27 | 2023-09-05 | 荣耀终端有限公司 | Authority management method and terminal equipment |
| CN115391794A (en) * | 2022-10-27 | 2022-11-25 | 中孚安全技术有限公司 | Method, system and equipment for adding permission in application program starting process |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102981835B (en) | 2015-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102981835B (en) | Android application program permanent Root permission acquiring method | |
| US9075955B2 (en) | Managing permission settings applied to applications | |
| US8955142B2 (en) | Secure execution of unsecured apps on a device | |
| US8549656B2 (en) | Securing and managing apps on a device | |
| CN103544447B (en) | A kind of method preventing confidential information from revealing based on Android system and terminal | |
| CN105046146B (en) | A kind of resource access method of Android system | |
| CN102289633A (en) | Method for managing dynamic permission of application program under Android platform | |
| CN104156660B (en) | A kind of Android authority fine-grained access control method based on running environment state | |
| CN104267982A (en) | Application program start control system and method | |
| Elkhodary et al. | A survey of approaches to adaptive application security | |
| CN104036202A (en) | Method and equipment for isolating enterprise applications | |
| US12047239B2 (en) | Configuration management for co-management | |
| US11108831B2 (en) | Machine policy configuration for managed devices | |
| CN103617389A (en) | Terminal rights management method and terminal device | |
| JP2004158007A (en) | Computer access authorization | |
| CN105373714B (en) | A kind of user authority control method and device | |
| CN101309478B (en) | Method for mobile terminal data access | |
| CN111651738A (en) | Fine-grained role authority unified management method based on front-end and back-end separation framework and electronic device | |
| CA2830880C (en) | Managing permission settings applied to applications | |
| CN104063303A (en) | Method for acquiring and freeing root permissions | |
| CN103763370B (en) | A kind of method, system and device for changing mobile terminal workspace screen-lock password | |
| US9692788B2 (en) | Method and system for domain creation and bootstrapping | |
| US9953104B2 (en) | Controlling access to one or more datasets of an operating system in use | |
| KR101345959B1 (en) | Method for multi-user authority management for single-user mobile handset platform and mobile handset using the same | |
| CN110826027B (en) | Method and system for distributing computer software user permission |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20160106 Address after: 100000, No. two, building 17, Zhongguancun Software Park, 8 northeast Wang Xi Road, Beijing, Haidian District, A2 Patentee after: BAIDU.COM TIMES TECHNOLOGY (BEIJING) Co.,Ltd. Address before: 350000, 403A building, four floor, Torch Innovation Building, 8 star road, Fuzhou Development Zone, Fuzhou, Fujian, China Patentee before: Fuzhou Boyuan Wireless Network Technology Co., Ltd. |