CN114048402B - FRP lock removing method, device, equipment and storage medium of Android system - Google Patents
FRP lock removing method, device, equipment and storage medium of Android system Download PDFInfo
- Publication number
- CN114048402B CN114048402B CN202210029304.5A CN202210029304A CN114048402B CN 114048402 B CN114048402 B CN 114048402B CN 202210029304 A CN202210029304 A CN 202210029304A CN 114048402 B CN114048402 B CN 114048402B
- Authority
- CN
- China
- Prior art keywords
- frp
- transmission port
- product name
- target
- model name
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 230000005540 biological transmission Effects 0.000 claims abstract description 99
- 230000009191 jumping Effects 0.000 claims abstract description 13
- 238000002347 injection Methods 0.000 claims description 6
- 239000007924 injection Substances 0.000 claims description 6
- 238000012545 processing Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims 2
- 239000000243 solution Substances 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000003213 activating effect Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000009434 installation Methods 0.000 description 2
- 240000003473 Grevillea banksii Species 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/90335—Query processing
- G06F16/90344—Query processing by using string matching techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Telephone Function (AREA)
Abstract
The invention relates to the field of software compatibility and use, and discloses a method, a device, equipment and a storage medium for removing an FRP lock of an Android system. The method comprises the following steps: receiving an FRP lock removal instruction of a target Android system, and triggering a preset adb service closing instruction based on the FRP lock removal instruction, wherein the FRP lock removal instruction comprises: a target model name and a target product name of the target Android system; inquiring an execution transmission port from all transmission ports based on the matched model name characters and the matched product name characters; according to a preset Android accessory protocol, sending a system control instruction to an execution transmission port, and receiving a setting link sent by the execution transmission port; jumping to access an H5 page corresponding to the set link, and injecting a preset PIN password in an H5 page; and reading the FRP unlocking setting page corresponding to the H5 page, and injecting the PIN password into the FRP unlocking setting page for removing the FRP lock of the target Android system.
Description
Technical Field
The invention relates to the field of software compatibility and use, in particular to a method, a device, equipment and a storage medium for removing an FRP lock of an Android system.
Background
Android mobile devices utilize built-in security functions to protect the device and information, including screen locking and data encryption. After registering the Google account on the device, the FRP will be automatically enabled. FRP (Factory reset protection) is one such function that is automatically enabled on android5.0 and higher version devices using the Google account. Once enabled, the FRP only allows users with Google account passwords to restore factory settings and activate their devices.
If the Google account is deleted from the device before factory settings are restored, the FRP will be disabled. Once the FRP is activated, if forced clearing of data restores factory settings, FRP locking will be enabled, the device needs to log in using the device owner's Google username and password, so even if the device is lost or stolen, others cannot restore factory settings and manipulate the device.
However, this is very inconvenient for the enterprise, as the devices provided by the company will bind to the employee's Google account. If the employee leaves the company, the device cannot be used as the company asset without removing the Google account in time, and even forced restoration of factory settings is limited.
At present, there are two existing schemes in the industry, the first scheme is to forcibly clear the FRP lock by swiping a firmware package (COMBINATION) into the mobile device through a data line, and the COMBINATION firmware package is a service firmware customized for the mobile device and used for checking security such as hardware and water resistance. It may be utilized to enable ADB and OEM unlocking, as well as clear FRP Google Account locks.
The second method is that the APK bypassing the frp is installed, the APK is in an Android installation package format, and some methods, such as a user-defined short message, the short message contains a specific url link, a browser is called through the url link, the APK is downloaded and installed in the browser, or a helpful setting interface is triggered and opened through voice operation, the interface contains a website link, but the compatibility of the method is not high.
At present, existing schemes in the industry have obvious defects, a scheme of swiping a firmware package (COMBINATION) into a mobile device through a data line is firstly adopted, because the firmware is detected on device hardware before leaving a factory, the firmware is not complete Android system firmware, and the complete function cannot be normally used after the firmware is swiped in.
After the corresponding factory firmware is flushed, the latest software firmware package corresponding to the equipment model needs to be downloaded again, and the software firmware package can be normally used after being flushed again. In addition, the problem is obvious that the firmware package matched with the equipment system can only be refreshed because the mobile equipment refresh limit cannot be degraded. To view the device firmware code, enter recovery mode, view the top code such as G950FXXU2CRED, 2 for U2 is the number of the boot loader required for the device, and download the determined firmware code by matching model number and boot loader level number. Since the number value is changed by pushing a version update periodically by the mobile device, the mobile device can write a plurality of versions of the corresponding firmware package by flashing, and the firmware package needs to be collected in a large amount, which results in poor compatibility. And is incompatible with mac systems because some mobile devices only support wins.
The second solution is by installing APK that bypasses frp. The installation of the apk needs to call a browser to trigger interfaces with links not shielded yet, such as certain function help links, for example, the opening of setting interfaces with help is triggered by voice operation, but the method can only be compatible with a certain version of a certain model. The installed apk calls an account adding interface, and a user logs in a new Google sub-account password to replace the original Google account. This solution is poorly compatible, while the latest Android11 browser will not be tolerant to install apks directly.
Therefore, in both solutions of the industry at present, there are problems of long operation time and poor compatibility, and therefore a technology is needed to solve the problem of the current FRP lock removal solution.
Disclosure of Invention
The invention mainly aims to solve the technical problems of long operation time for removing an FRP lock in an Android system and poor compatibility of a removing scheme.
The invention provides a method for removing an FRP lock of an Android system, which comprises the following steps:
receiving an FRP lock removal instruction of a target Android system, and triggering a preset adb service closing instruction based on the FRP lock removal instruction, wherein the FRP lock removal instruction comprises: a target model name and a target product name of the target Android system;
traversing and reading model name characters and product name characters analyzed by all transmission ports to obtain a model name character set and a product name character set, and comparing the model name character set and the product name character set according to the target model name and the target product name to obtain matched model name characters and matched product name characters;
inquiring an execution transmission port from all transmission ports based on the matched model name characters and the matched product name characters;
according to a preset Android accessory protocol, sending a system control instruction to the execution transmission port, and receiving a setting link sent by the execution transmission port;
jumping to access an H5 page corresponding to the setting link, and injecting a preset PIN password in the H5 page;
and reading the FRP unlocking setting page corresponding to the H5 page, and injecting the PIN password into the FRP unlocking setting page for removing the FRP lock of the target Android system.
Optionally, in a first implementation manner of the first aspect of the present invention, the receiving an FRP lock removal instruction of a target Android system, and based on the FRP lock removal instruction, triggering a preset adb service shutdown instruction includes:
receiving an FRP lock removal instruction of a target Android system;
triggering and judging whether an adb service process exists or not based on the FRP lock removal instruction;
and if so, calling a preset adb service closing instruction to close all adb service processes.
Optionally, in a second implementation manner of the first aspect of the present invention, the sending a system control instruction to the execution transmission port according to a preset Android accessory protocol, and receiving a setting link sent by the execution transmission port includes:
initializing the execution transmission port based on a preset libush library, and judging whether the execution transmission port is in an accessory mode;
and if the mobile terminal is in the accessory mode, sending a system control instruction to the execution transmission port, and receiving a setting link sent by the execution transmission port.
Optionally, in a third implementation manner of the first aspect of the present invention, the sending a system control instruction to the execution transmission port, and receiving a setup link sent by the execution transmission port includes:
based on a preset Android accessory protocol, sending a preset Android accessory request to the execution transmission port, and receiving feedback data of the execution transmission port;
judging whether the feedback data is empty or not;
if not, according to a preset control character string set, sequentially sending the control character strings in the control character string set to the execution transmission port, and receiving the setting link sent by the execution transmission port.
Optionally, in a fourth implementation manner of the first aspect of the present invention, the skipping accesses an H5 page corresponding to the setting link, and the injecting a preset PIN decryption code into the H5 page includes:
jumping to access an H5 page corresponding to the setting link;
and injecting a preset PIN decryption code into an unlocking code page of the H5 page.
Optionally, in a fifth implementation manner of the first aspect of the present invention, the reading the FRP unlock setting page corresponding to the H5 page, and the injecting the PIN decryption code into the FRP unlock setting page includes:
disconnecting the network connection of the target Android system through the execution transmission port;
and establishing network connection of the target Android system through the execution transmission port, triggering the H5 page to pop up an FRP unlocking setting page, and injecting the PIN password into the FRP unlocking setting page.
Optionally, in a sixth implementation manner of the first aspect of the present invention, the comparing, according to the target model name and the target product name, the model name character set and the product name character set to obtain a matched model name character and a matched product name character includes:
extracting product name characters in the product name character set;
judging whether the product name character is consistent with the target product name or not;
if the product name characters are not consistent, extracting new product name characters from the product name character set;
if the product name characters are consistent, determining the product name characters as matched product name characters;
extracting model name characters in the model name character set;
judging whether the model name character is consistent with the target model name or not;
if the model name characters are not consistent, extracting new model name characters from the model name character set;
and if the model name characters are consistent, determining the consistent model name characters as matched model name characters.
The second aspect of the present invention provides an FRP lock removing device for an Android system, where the FRP lock removing device for the Android system includes:
the service closing module is used for receiving an FRP lock removing instruction of a target Android system and triggering a preset adb service closing instruction based on the FRP lock removing instruction, wherein the FRP lock removing instruction comprises: a target model name and a target product name of the target Android system;
the traversal comparison module is used for reading model name characters and product name characters analyzed by all the transmission ports in a traversal mode to obtain a model name character set and a product name character set, and comparing the model name character set and the product name character set according to the target model name and the target product name to obtain matched model name characters and matched product name characters;
the query module is used for querying out the execution transmission ports from all the transmission ports based on the matched model name characters and the matched product name characters;
the link triggering module is used for sending a system control instruction to the execution transmission port according to a preset Android accessory protocol and receiving a setting link sent by the execution transmission port;
the password unlocking injection module is used for jumping to access an H5 page corresponding to the set link and injecting a preset PIN unlocking password into the H5 page;
and the FRP lock removing module is used for reading an FRP unlocking setting page corresponding to the H5 page, injecting the PIN password into the FRP unlocking setting page, and removing the FRP lock of the target Android system.
The third aspect of the present invention provides an FRP lock removing device for an Android system, including: a memory having instructions stored therein and at least one processor, the memory and the at least one processor interconnected by a line; the at least one processor calls the instructions in the memory to enable the FRP lock removal device of the Android system to execute the FRP lock removal method of the Android system.
A fourth aspect of the present invention provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to execute the above-mentioned FRP lock removal method for an Android system.
In the embodiment, the scheme switches a PC machine (win, mac) to an Android accessory by initializing a mobile device connected through a USB. The method comprises the steps of constructing a special control data packet, switching a PC into audio accessory equipment through a USB link, triggering a popup message corresponding to an Android accessory protocol of the mobile equipment, wherein the message contains a URL link, inputting a correspondingly constructed H5 page, the page contains a self-defined in-page jump protocol in Android, calling a setting page for setting an account PIN password through the jump protocol, and returning to an FRP interface to activate an FRP lock through setting the PIN code in an unlocking mode of adding a Pin code. According to the scheme, the apk is not required to be installed, the firmware is not required to be downloaded, the operation is simple and fast, the Android 6-Android 10 are compatible, the compatibility is stronger, and the stability is high.
Drawings
Fig. 1 is a schematic diagram of an embodiment of a method for removing an FRP lock of an Android system in an embodiment of the present invention;
fig. 2 is a schematic diagram of an FRP lock removing device of an Android system according to an embodiment of the present invention;
fig. 3 is a schematic diagram of another embodiment of an FRP lock removing device of an Android system according to an embodiment of the present invention;
fig. 4 is a schematic diagram of an embodiment of an FRP lock removing device of an Android system in the embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a method, a device, equipment and a storage medium for removing an FRP lock of an Android system.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," or "having," and any variations thereof, are intended to cover non-exclusive inclusions, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
For convenience of understanding, a specific flow of the embodiment of the present invention is described below, and with reference to fig. 1, an embodiment of an FRP lock removing method for an Android system in the embodiment of the present invention includes:
101. receiving an FRP lock removal instruction of a target Android system, and triggering a preset adb service closing instruction based on the FRP lock removal instruction, wherein the FRP lock removal instruction comprises: a target model name and a target product name of the target Android system;
in this embodiment, a mobile device that needs to remove an FRP lock is an Android system, and after receiving an FRP lock removal instruction of a target Android system, a VID value of the mobile device is defined as a target model name of the Android system, and a PID value of the mobile device is defined as a target product name of the Android system. The Adb service closing instruction can call the Adb kill-server of the Adb tool in the system, so as to avoid usb occupation conflict.
Further, at 101, the following steps may be performed:
1011. receiving an FRP lock removal instruction of a target Android system;
1012. triggering and judging whether an adb service process exists or not based on the FRP lock removal instruction;
1013. and if so, calling a preset adb service closing instruction to close all adb service processes.
In 1011-. The adb service close command closes the adb service. Judging and identifying the version of the current system, installing winysb drivers according to different versions of the 32-bit system and the 64-bit system, and preparing for PC and Android hardware communication, wherein the drivers are used for accessing universal drivers of USB equipment. Mac does not need to install a driver independently, and a communication driver with a base of a Mac system is directly used. After installing the winysb driver, the accessed Android device corresponds to a device driver in the device manager as follows: WinUsb devices.
102. Traversing and reading model name characters and product name characters analyzed by all transmission ports to obtain a model name character set and a product name character set, and comparing the model name character set and the product name character set according to a target model name and a target product name to obtain matched model name characters and matched product name characters;
in this embodiment, the information related to all USB devices is traversed, the mobile device ID is determined to contain "VID _" and "PID _" information, and it is determined whether the VID information is equal to "04E 8", which is a unique ID value for the mobile device, and the PID is different according to the model. And traversing all the USB devices, judging that the vender ID is the device with the value of 04E8, and acquiring the corresponding product ID value.
Further, "according to the target model name and the target product name, the model name character set and the product name character set are compared to obtain a matched model name character and a matched product name character", the following steps may be performed:
1021. extracting product name characters in a product name character set;
1022. judging whether the product name character is consistent with the target product name;
1023. if the product name characters are not consistent, extracting new product name characters from the product name character set;
1024. if the product name characters are consistent, determining the product name characters as matched product name characters;
1025. extracting model name characters in the model name character set;
1026. judging whether the model name character is consistent with the target model name;
1027. if the model name characters are not consistent, extracting new model name characters from the model name character set;
1028. and if the model name characters are consistent, determining the consistent model name characters as matched model name characters.
In step 1021-.
Firstly, extracting a product name character in the VID set, then judging whether the VID is the 04E8 target product name, if not, extracting a new product name character in the VID set, circularly judging all the product name characters in the VID set, and after the step 1023, jumping back to the step 1022 for judgment.
The model name character of the model name character PID set matches a similar model name character VID set and after the step 1027 a loop is made back to the step 1026.
103. Inquiring an execution transmission port from all transmission ports based on the matched model name characters and the matched product name characters;
in this embodiment, it is easy to understand that each transmission port has only one model name character and one product name character, and if the product name character and the product name character are determined, the transmission port provided by the product name character and the product name character is also determined, and the transmission port is determined as an execution transmission port.
104. According to a preset Android accessory protocol, sending a system control instruction to an execution transmission port, and receiving a setting link sent by the execution transmission port;
in this embodiment, the Android accessory protocol is mainly used for enabling the PC device to be injected into the Android system in an accessory mode, and the PC device releases the limitation of the FRP lock by setting a setting link of the Android system.
Further, at 104, the following steps may be performed:
1041. initializing an execution transmission port based on a preset libustb library, and judging whether the execution transmission port is in an accessory mode;
1042. if the system is in the accessory mode, a system control instruction is sent to the execution transmission port, and the setting link sent by the execution transmission port is received.
In 1041-1042 step, USB communication is performed using libush library, which is a library-supported multi-platform for supporting access to USB devices from Linux, macOS, Windows, Open BSD/Net BSD, Haiku and Solaris user spaces. The processing mode can carry out the following processes:
1. the USB device is initialized using libussb and checked to see if the device is in accessory mode.
2. If the device is in the accessory mode, acquiring the total number of the usb devices by using the libobsb, and circularly acquiring the device descriptors and corresponding device handle information, wherein the handle information comprises: the size, type, usb version number (usb 2.0 or usb 1.0), protocol, vendor id (vid), product id (pid), name of manufacturer, character string of name product, character string information of device serial number of the descriptor.
3. And acquiring the corresponding mobile device handle, comparing whether the supplier ID and the product ID are consistent with the VID and the PID acquired in the S20, and if so, opening the corresponding device handle through libussb, and if not, indicating that the opening is successful.
4. Sending a special control packet switches the PC device to accessory mode over the USB link.
Further, 1042 may also perform the following steps:
10421. based on a preset Android accessory protocol, sending a preset Android accessory request to an execution transmission port, and receiving feedback data of the execution transmission port;
10422. judging whether the feedback data is empty or not;
10423. if not, according to the preset control character string set, sequentially sending the control character strings in the control character string set to the execution transmission port, and receiving the setting link sent by the execution transmission port.
In step 10421-10423, the Android accessory request format is: 1. request type +2, request ID +3, request character string information content +4, request size
1. And sending a control request for acquiring a protocol to the equipment to determine whether the equipment supports the Android accessory protocol, if the request is successful, returning that the request is not null, indicating that the mobile equipment supports the accessory protocol, and if the request is successful, continuing sending a control request containing manufacturer character string information to the equipment, wherein the character string is set to be XXXX, Inc. And sending a control request containing the information of the model character string after the successful sending, wherein the model is set as the character string customized by us, namely the FRP unllook. And after the success, continuing to send a control request for describing the information character string, wherein the describing information is set as self-defined information: "FRP UnLock Demo". And after the control request containing the version information is successfully sent, setting the version information to be 2, and continuously sending the control request containing the URL address information, wherein the information is the calling URL.
If the Android is 9-10, calling URL (hypertext markup language) https:// apps.samsung.com/appquery/appPDetail.asappid = com.sec.android.app.sbrowser & cId = 000005006635; if the Android version is 6-8, https:// www.youtube.com/accountprivacy is set.
Sending a control request containing serial number information we "0000000012345678" a mismatch, so arranged that if there is no application for the fitting proper, the fitting protocol will send the user a URL where we previously set to prompt the fitting mismatch to pop-up.
And sending a control request for enabling USB audio support, wherein the protocol is the second version of AOA, and AOAv2 supports audio output from the Android device to the accessory through a standard USB audio-class interface. The audio class interface supports 2 channel 16 bit PCM audio with a bit rate of 44100 Khz.
After control character strings in the control character string set are successfully sent in sequence, a control request requesting to enter an accessory mode is finally sent, at the moment, special data packets sent by people are all sent, after the control character strings enter the accessory mode, due to the fact that no application suitable for accessories is found, Android equipment pops a box to prompt, App relevant to work of the accessories is not installed, https:// www.youtube.com/accountprivacy is checked, the content of the pops is the description character strings and URLs set by people, and the URL is triggered to jump to a browser after a View button is clicked.
105. Jumping to access an H5 page corresponding to the set link, and injecting a preset PIN password in an H5 page;
in this embodiment, a path of an unlocking password page in an H5 page is recorded, and after a link is set to enter the H5 page, a PIN unlocking password is directly injected according to the path access unlocking password page.
Further, at 105, the following steps may be performed:
1051. jumping to access an H5 page corresponding to the set link;
1052. and injecting a preset PIN decryption code into an unlocking code page of the H5 page.
In the 1051-1052 step, a jump is triggered to open the browser, where the link to the constructed H5 webpage is accessed. The H5 page is a guidance page that contains guidance prompts and a "set" button. And guiding to prompt setting of a PIN password, and turning to opening of a 'setting' entering 'for protecting a mobile phone' entering 'PIN' to set the password. The page "set" button is associated with a URL, which is an in-page jump protocol. The method comprises the steps that (1), an Intent is set as a utility class of GooglePlay service, com, android, scheme is set as a password page for setting unlocking, and specific url is Intent// com, good. And end, when the user clicks a webpage setting button, triggering and opening the link, and opening a page for setting an unlocking password through an in-page jump protocol route. The page prompts 'protect your mobile phone' to pass the setting of passwords, and the password types comprise face identification, fingerprints, patterns, mixed numeric-letter passwords and PIN passwords. And triggering a PIN password on the page, and setting a Pin password. After triggering, prompting whether the password is required after starting up, defaulting to trigger Do not require, and clicking a PIN code formed by 4-length numbers after the next step.
106. And reading the FRP unlocking setting page corresponding to the H5 page, and injecting the PIN password into the FRP unlocking setting page for removing the FRP lock of the target Android system.
In this embodiment, the activation path is changed into an FRP unlock setting page of an H5 page, and a PIN unlock code that needs to be activated is placed in the FRP unlock setting page, so that the FRP lock of the target Android system can be removed.
Further, at 106, the following steps may be performed:
1061. disconnecting the network connection of the target Android system through the execution transmission port;
1062. the network connection of the target Android system is established by executing the transmission port, the H5 page is triggered to pop up the FRP unlocking setting page, and the PIN password is injected into the FRP unlocking setting page.
In the 1061-1062 step, activating a "<" icon button of the device or activating a "return" button of the mobile phone device, always activating to return to a Wifi connection page, reconnecting Wifi and completing the setting wizard, then "inputting your current PIN code or using my Google account number" appears, injecting the set PIN code, after verification is correct, checking the Google account number with FRP activated at this time, and at this time, removing the FRP lock. At this point, we can choose to log in a new Google account or click SKIP over SKIP.
In the embodiment, the scheme switches a PC machine (win, mac) to an Android accessory by initializing a mobile device connected through a USB. The method comprises the steps of constructing a special control data packet, switching a PC into audio accessory equipment through a USB link, triggering a popup message corresponding to an Android accessory protocol of the mobile equipment, wherein the message contains a URL link, inputting a correspondingly constructed H5 page, the page contains a self-defined in-page jump protocol in Android, calling a setting page for setting an account PIN password through the jump protocol, and returning to an FRP interface to activate an FRP lock through setting the PIN code in an unlocking mode of adding a Pin code. According to the scheme, the apk is not required to be installed, the firmware is not required to be downloaded, the operation is simple and fast, the Android 6-Android 10 are compatible, the compatibility is stronger, and the stability is high.
With reference to fig. 2, the method for removing an FRP lock of an Android system in the embodiment of the present invention is described above, and an FRP lock removing device of an Android system in the embodiment of the present invention is described below, where the method for removing an FRP lock of an Android system in the embodiment of the present invention includes:
the service closing module 201 is configured to receive an FRP lock removal instruction of a target Android system, and trigger a preset adb service closing instruction based on the FRP lock removal instruction, where the FRP lock removal instruction includes: a target model name and a target product name of the target Android system;
a traversal comparison module 202, configured to traverse and read model name characters and product name characters analyzed by all transmission ports to obtain a model name character set and a product name character set, and perform comparison processing on the model name character set and the product name character set according to the target model name and the target product name to obtain matched model name characters and matched product name characters;
the query module 203 is used for querying out an execution transmission port from all the transmission ports based on the matched model name characters and the matched product name characters;
the link triggering module 204 is configured to send a system control instruction to the execution transmission port according to a preset Android accessory protocol, and receive a setting link sent by the execution transmission port;
the password unlocking injection module 205 is used for jumping to access an H5 page corresponding to the setting link and injecting a preset PIN password unlocking code into the H5 page;
the FRP lock removal module 206 is configured to read an FRP unlock setting page corresponding to the H5 page, and inject the PIN decryption code into the FRP unlock setting page, so as to remove the FRP lock of the target Android system.
In the embodiment, the scheme switches a PC machine (win, mac) to an Android accessory by initializing a mobile device connected through a USB. The method comprises the steps of constructing a special control data packet, switching a PC into audio accessory equipment through a USB link, triggering a popup message corresponding to an Android accessory protocol of the mobile equipment, wherein the message contains a URL link, inputting a correspondingly constructed H5 page, the page contains a self-defined in-page jump protocol in Android, calling a setting page for setting an account PIN password through the jump protocol, and returning to an FRP interface to activate an FRP lock through setting the PIN code in an unlocking mode of adding a Pin code. According to the scheme, the apk is not required to be installed, the firmware is not required to be downloaded, the operation is simple and fast, the Android 6-Android 10 are compatible, the compatibility is stronger, and the stability is high.
Referring to fig. 3, according to another embodiment of the FRP lock removing device of an Android system in the embodiment of the present invention, the FRP lock removing device of the Android system includes:
the service closing module 201 is configured to receive an FRP lock removal instruction of a target Android system, and trigger a preset adb service closing instruction based on the FRP lock removal instruction, where the FRP lock removal instruction includes: a target model name and a target product name of the target Android system;
a traversal comparison module 202, configured to traverse and read model name characters and product name characters analyzed by all transmission ports to obtain a model name character set and a product name character set, and perform comparison processing on the model name character set and the product name character set according to the target model name and the target product name to obtain matched model name characters and matched product name characters;
the query module 203 is used for querying out an execution transmission port from all the transmission ports based on the matched model name characters and the matched product name characters;
the link triggering module 204 is configured to send a system control instruction to the execution transmission port according to a preset Android accessory protocol, and receive a setting link sent by the execution transmission port;
the password unlocking injection module 205 is used for jumping to access an H5 page corresponding to the setting link and injecting a preset PIN password unlocking code into the H5 page;
the FRP lock removal module 206 is configured to read an FRP unlock setting page corresponding to the H5 page, and inject the PIN decryption code into the FRP unlock setting page, so as to remove the FRP lock of the target Android system.
The service closing module 201 is specifically configured to:
receiving an FRP lock removal instruction of a target Android system;
triggering and judging whether an adb service process exists or not based on the FRP lock removal instruction;
and if so, calling a preset adb service closing instruction to close all adb service processes.
Wherein the link triggering module 204 comprises:
an initializing unit 2041, configured to initialize the execution transmission port based on a preset libush library, and determine whether the execution transmission port is in an accessory mode;
the control unit 2042 is configured to send a system control instruction to the execution transmission port if the accessory mode is satisfied, and receive a setting link sent by the execution transmission port.
Wherein the control unit 2042 is specifically configured to:
based on a preset Android accessory protocol, sending a preset Android accessory request to the execution transmission port, and receiving feedback data of the execution transmission port;
judging whether the feedback data is empty or not;
if not, according to a preset control character string set, sequentially sending the control character strings in the control character string set to the execution transmission port, and receiving the setting link sent by the execution transmission port.
The decryption code injection module 205 is specifically configured to:
jumping to access an H5 page corresponding to the setting link;
and injecting a preset PIN decryption code into an unlocking code page of the H5 page.
The decryption code injection module 205 is specifically configured to:
disconnecting the network connection of the target Android system through the execution transmission port;
and establishing network connection of the target Android system through the execution transmission port, triggering the H5 page to pop up an FRP unlocking setting page, and injecting the PIN password into the FRP unlocking setting page.
The traversal alignment module 202 is specifically configured to:
extracting model name characters in the model name character set;
judging whether the model name character is consistent with the target model name or not;
if the model name characters are not consistent, extracting new model name characters from the model name character set;
if the model name characters are consistent, determining the consistent model name characters as matched model name characters;
extracting product name characters in the product name character set;
judging whether the product name character is consistent with the target product name or not;
if the product name characters are not consistent, extracting new product name characters from the product name character set;
and if the product name characters are consistent, determining the product name characters as matched product name characters.
In the embodiment, the scheme switches a PC machine (win, mac) to an Android accessory by initializing a mobile device connected through a USB. The method comprises the steps of constructing a special control data packet, switching a PC into audio accessory equipment through a USB link, triggering a popup message corresponding to an Android accessory protocol of the mobile equipment, wherein the message contains a URL link, inputting a correspondingly constructed H5 page, the page contains a self-defined in-page jump protocol in Android, calling a setting page for setting an account PIN password through the jump protocol, and returning to an FRP interface to activate an FRP lock through setting the PIN code in an unlocking mode of adding a Pin code. According to the scheme, the apk is not required to be installed, the firmware is not required to be downloaded, the operation is simple and fast, the Android 6-Android 10 are compatible, the compatibility is stronger, and the stability is high.
Fig. 2 and 3 describe the FRP lock removing device of the Android system in the embodiment of the present invention in detail from the perspective of the modular functional entity, and in the following, describe the FRP lock removing device of the Android system in the embodiment of the present invention in detail from the perspective of hardware processing.
Fig. 4 is a schematic structural diagram of an FRP lock removing device of an Android system according to an embodiment of the present invention, where the FRP lock removing device 400 of the Android system may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 410 (e.g., one or more processors) and a memory 420, and one or more storage media 430 (e.g., one or more mass storage devices) storing an application 433 or data 432. Memory 420 and storage medium 430 may be, among other things, transient or persistent storage. The program stored in the storage medium 430 may include one or more modules (not shown), each of which may include a series of instruction operations in the FRP lock removal device 400 of the Android system. Still further, the processor 410 may be configured to communicate with the storage medium 430, and execute a series of instruction operations in the storage medium 430 on the FRP lock removal device 400 of the Android system.
The Android system-based FRP lock removal device 400 may also include one or more power supplies 440, one or more wired or wireless network interfaces 450, one or more input-output interfaces 460, and/or one or more operating systems 431, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, and the like. Those skilled in the art will appreciate that the structure of the FRP lock removal device of the Android system illustrated in fig. 4 does not constitute a limitation to the FRP lock removal device of the Android system, and may include more or less components than those illustrated, or some components in combination, or a different arrangement of components.
The present invention also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium, or a volatile computer-readable storage medium, having stored therein instructions, which, when executed on a computer, cause the computer to perform the steps of the FRP lock removal method for an Android system.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses, and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (8)
1. An FRP lock removing method of an Android system is characterized by comprising the following steps:
receiving an FRP lock removal instruction of a target Android system, and triggering a preset adb service closing instruction based on the FRP lock removal instruction, wherein the FRP lock removal instruction comprises: a target model name and a target product name of the target Android system;
traversing and reading model name characters and product name characters analyzed by all transmission ports to obtain a model name character set and a product name character set, and comparing the model name character set and the product name character set according to the target model name and the target product name to obtain matched model name characters and matched product name characters;
inquiring an execution transmission port from all transmission ports based on the matched model name characters and the matched product name characters;
according to a preset Android accessory protocol, sending a system control instruction to the execution transmission port, and receiving a setting link sent by the execution transmission port;
jumping to access an H5 page corresponding to the setting link, and injecting a preset PIN password in the H5 page;
reading an FRP unlocking setting page corresponding to the H5 page, and injecting the PIN password into the FRP unlocking setting page for removing the FRP lock of the target Android system;
the sending of the system control instruction to the execution transmission port according to the preset Android accessory protocol and the receiving of the setting link sent by the execution transmission port include:
initializing the execution transmission port based on a preset libush library, and judging whether the execution transmission port is in an accessory mode;
if the mobile terminal is in the accessory mode, sending a system control instruction to the execution transmission port, and receiving a setting link sent by the execution transmission port;
wherein, the sending the system control command to the execution transmission port, and the receiving the setting link sent by the execution transmission port includes:
based on a preset Android accessory protocol, sending a preset Android accessory request to the execution transmission port, and receiving feedback data of the execution transmission port;
judging whether the feedback data is empty or not;
if not, according to a preset control character string set, sequentially sending the control character strings in the control character string set to the execution transmission port, and receiving the setting link sent by the execution transmission port.
2. The FRP lock removal method for the Android system of claim 1, wherein the receiving an FRP lock removal instruction for a target Android system, and the triggering a preset adb service shutdown instruction based on the FRP lock removal instruction comprises:
receiving an FRP lock removal instruction of a target Android system;
triggering and judging whether an adb service process exists or not based on the FRP lock removal instruction;
and if so, calling a preset adb service closing instruction to close all adb service processes.
3. The FRP lock removal method for Android systems according to claim 1, wherein the jump accesses an H5 page corresponding to the setting link, and the step of injecting a preset PIN password in the H5 page comprises:
jumping to access an H5 page corresponding to the setting link;
and injecting a preset PIN decryption code into an unlocking code page of the H5 page.
4. The FRP lock removal method of the Android system of claim 1, wherein the reading of the FRP unlock setting page corresponding to the H5 page and the injecting of the PIN password into the FRP unlock setting page comprises:
disconnecting the network connection of the target Android system through the execution transmission port;
and establishing network connection of the target Android system through the execution transmission port, triggering the H5 page to pop up an FRP unlocking setting page, and injecting the PIN password into the FRP unlocking setting page.
5. The FRP lock removal method of the Android system of claim 1, wherein the comparing the model name character set and the product name character set according to the target model name and the target product name to obtain the matched model name characters and the matched product name characters comprises:
extracting product name characters in the product name character set;
judging whether the product name character is consistent with the target product name or not;
if the product name characters are not consistent, extracting new product name characters from the product name character set;
if the product name characters are consistent, determining the product name characters as matched product name characters;
extracting model name characters in the model name character set;
judging whether the model name character is consistent with the target model name or not;
if the model name characters are not consistent, extracting new model name characters from the model name character set;
and if the model name characters are consistent, determining the consistent model name characters as matched model name characters.
6. An FRP lock removal device of an Android system, the FRP lock removal device of the Android system comprising:
the service closing module is used for receiving an FRP lock removing instruction of a target Android system and triggering a preset adb service closing instruction based on the FRP lock removing instruction, wherein the FRP lock removing instruction comprises: a target model name and a target product name of the target Android system;
the traversal comparison module is used for performing traversal reading on model name characters and product name characters analyzed by all the transmission ports to obtain a model name character set and a product name character set, and performing comparison processing on the model name character set and the product name character set according to the target model name and the target product name to obtain matched model name characters and matched product name characters;
the query module is used for querying out the execution transmission ports from all the transmission ports based on the matched model name characters and the matched product name characters;
the link triggering module is used for sending a system control instruction to the execution transmission port according to a preset Android accessory protocol and receiving a setting link sent by the execution transmission port;
the password unlocking injection module is used for jumping to access an H5 page corresponding to the set link and injecting a preset PIN unlocking password into the H5 page;
the FRP lock removing module is used for reading an FRP unlocking setting page corresponding to the H5 page, injecting the PIN password into the FRP unlocking setting page and removing an FRP lock of the target Android system;
wherein the link triggering module comprises:
the initialization unit is used for initializing the execution transmission port based on a preset libush library and judging whether the execution transmission port is in an accessory mode or not;
the control unit is used for sending a system control instruction to the execution transmission port and receiving a setting link sent by the execution transmission port if the control unit is in an accessory mode;
wherein the control unit is specifically configured to:
based on a preset Android accessory protocol, sending a preset Android accessory request to the execution transmission port, and receiving feedback data of the execution transmission port;
judging whether the feedback data is empty or not;
if not, according to a preset control character string set, sequentially sending the control character strings in the control character string set to the execution transmission port, and receiving the setting link sent by the execution transmission port.
7. The FRP lock removing device of the Android system is characterized by comprising: a memory having instructions stored therein and at least one processor, the memory and the at least one processor interconnected by a line;
the at least one processor calls the instructions in the memory to cause the FRP lock removal device of the Android system to execute the FRP lock removal method of the Android system of any of claims 1-5.
8. A computer-readable storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the FRP lock removal method for an Android system of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210029304.5A CN114048402B (en) | 2022-01-12 | 2022-01-12 | FRP lock removing method, device, equipment and storage medium of Android system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210029304.5A CN114048402B (en) | 2022-01-12 | 2022-01-12 | FRP lock removing method, device, equipment and storage medium of Android system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114048402A CN114048402A (en) | 2022-02-15 |
| CN114048402B true CN114048402B (en) | 2022-04-22 |
Family
ID=80196335
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210029304.5A Active CN114048402B (en) | 2022-01-12 | 2022-01-12 | FRP lock removing method, device, equipment and storage medium of Android system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114048402B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104506639A (en) * | 2014-12-29 | 2015-04-08 | 北京奇虎科技有限公司 | Root right acquiring method and device |
| TW201717089A (en) * | 2015-11-11 | 2017-05-16 | 宏碁股份有限公司 | Factory reset protection disarm method and electronic device |
| CN107124279A (en) * | 2017-04-28 | 2017-09-01 | 上海与德科技有限公司 | The method and device of erasing terminal data |
| CN110245290A (en) * | 2019-05-21 | 2019-09-17 | 平安普惠企业管理有限公司 | A kind of data correlation method, device, storage medium and the server of application registration |
| CN113691667A (en) * | 2021-08-23 | 2021-11-23 | 天津大学 | Smart phone digital password unlocking method based on screen pressing force |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9866543B2 (en) * | 2015-06-03 | 2018-01-09 | Paypal, Inc. | Authentication through multiple pathways based on device capabilities and user requests |
| CN106127897B (en) * | 2016-06-22 | 2018-02-23 | 江苏巨数智能科技有限公司 | System for unlocking or method based on iOS or Android |
| KR101856930B1 (en) * | 2016-08-29 | 2018-05-11 | 현대자동차주식회사 | Usb communication control method of usb accessory |
| CN110110504A (en) * | 2019-04-30 | 2019-08-09 | 大连睿海信息科技有限公司 | Android system mobile phone application lock crack method based on Lian Fa section MTK processor communication agreement |
| CN110113475A (en) * | 2019-04-30 | 2019-08-09 | 大连睿海信息科技有限公司 | Android system mobile phone screen lock crack method based on Lian Fa section MTK processor communication agreement |
| CN112671796B (en) * | 2020-12-31 | 2022-03-25 | 深圳软牛科技有限公司 | Google Driver cloud service authentication acquisition method, device, equipment and storage medium |
-
2022
- 2022-01-12 CN CN202210029304.5A patent/CN114048402B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104506639A (en) * | 2014-12-29 | 2015-04-08 | 北京奇虎科技有限公司 | Root right acquiring method and device |
| TW201717089A (en) * | 2015-11-11 | 2017-05-16 | 宏碁股份有限公司 | Factory reset protection disarm method and electronic device |
| CN107124279A (en) * | 2017-04-28 | 2017-09-01 | 上海与德科技有限公司 | The method and device of erasing terminal data |
| CN110245290A (en) * | 2019-05-21 | 2019-09-17 | 平安普惠企业管理有限公司 | A kind of data correlation method, device, storage medium and the server of application registration |
| CN113691667A (en) * | 2021-08-23 | 2021-11-23 | 天津大学 | Smart phone digital password unlocking method based on screen pressing force |
Non-Patent Citations (1)
| Title |
|---|
| Moto X Style 解除 Google FRP 账户锁教程;chenchen 晨晨;《https://bbs.ixmoe.com/t/moto-x-style-google-frp/17859》;20160630;第1-2页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114048402A (en) | 2022-02-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112771826B (en) | Application program login method, application program login device and mobile terminal | |
| Costin et al. | A {Large-scale} analysis of the security of embedded firmwares | |
| CN102622439B (en) | Method and device for displaying document in browser | |
| CN106462476A (en) | Consistent extension points to allow an extension to extend functionality of an application to another application | |
| JP2008547100A (en) | Service access authentication data management system | |
| EP3345112B1 (en) | Thresholds on scripts executable by unified extensible firmware interface systems | |
| CN105718171B (en) | A kind of data processing method and terminal | |
| KR20140087029A (en) | Application data processing method and computing node | |
| CN102149074B (en) | A kind of method that terminal and smart card are locked or unlock and device | |
| CN107302586A (en) | A kind of Webshell detection methods and device, computer installation, readable storage medium storing program for executing | |
| CN104021074B (en) | Vulnerability detection method and device for application program of PhoneGap framework | |
| CN108959860B (en) | Method for detecting whether Android system is cracked or not and obtaining cracking record | |
| CN114048402B (en) | FRP lock removing method, device, equipment and storage medium of Android system | |
| CN108600259B (en) | Authentication and binding method of equipment, computer storage medium and server | |
| JP5478384B2 (en) | Application determination system and program | |
| CN106507300A (en) | A kind of method for giving loss terminal for change, device and terminal | |
| CN113536242A (en) | Dynamic library calling method and device, terminal equipment and storage medium | |
| US20050005015A1 (en) | Method, system, and computer-readable medium for managing a host session on a remote computer | |
| JP2001273135A (en) | Method and device for individual authentication by using portable telephone | |
| CN104516743B (en) | The upgrade method and system of embedded device firmware based on ActiveX | |
| JP2008146551A (en) | Password information management system, terminal and program | |
| CN109657458B (en) | Method, storage medium, device and system for protecting key string data in IOS | |
| CN103955466A (en) | Method and device for displaying document in browser | |
| Cisco | Release Notes for Cisco Secure Intrusion Detection System Director for UNIX Version 2.2.2 | |
| CN115688120A (en) | Secure chip firmware importing method, secure chip and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 1301-1310, building 2, jinlitong financial center building, 1100 Xingye Road, Haiwang community, Xin'an street, Bao'an District, Shenzhen, Guangdong 518000 Patentee after: Shenzhen Ruan Niu Technology Group Co.,Ltd. Address before: 1301-1310, building 2, jinlitong financial center building, 1100 Xingye Road, Haiwang community, Xin'an street, Bao'an District, Shenzhen, Guangdong 518000 Patentee before: AFIRSTSOFT CO.,LTD. |