Method, device, computer device and storage medium for bypassing and removing FRP lock

Abstract

The application discloses a method and device for bypassing and removing FRP lock, a computer device and a storage medium, and relates to the field of computer systems, which comprises the following steps: closing an adb process, connecting and debugging a mobile device; obtaining the right to send information to the mobile device through a serial port by opening the engineering test mode of the mobile device; constructing and sending a message list to the mobile device through the serial port to control the mobile device to open the developer mode and the USB debugging switch; and sending an adb modification setting command to the mobile device to enable the mobile device to directly enter the desktop and remove the FRP lock in the system settings of the mobile device. The application opens the developer mode and the USB debugging through the serial port communication mode to remove the FRP lock, and does not need to flash the system, does not need to download the firmware, is simple to operate, is high in stability and is more compatible.

Description

Technical Field

[0001] This invention relates to the field of computer systems, and more particularly to methods, apparatus, computer devices, and storage media for bypassing and removing FRP locks. Background Technology

[0002] Android mobile devices protect themselves and their data through a theft and loss prevention mechanism called the FRP lock. When a device needs to be reset, the FRP lock is triggered, locking the device if it isn't removed. In one existing technology, the device bypasses the FRP lock by flashing a firmware package. This method requires multiple flashes; however, firmware packages require significant memory and are time-consuming to download, and are often not official, making them insecure and unstable for the device. Furthermore, these firmware packages are only compatible with Microsoft systems, not Mac systems, resulting in poor compatibility. Another existing technology involves certain types of mobile devices connected via USB, switching a PC to an audio accessory device, and triggering a pop-up message containing a URL link. Clicking the link leads to a PIN code setup page, but this method of triggering the pop-up is disabled due to security settings. Summary of the Invention

[0003] This invention provides a method, apparatus, computer device, and storage medium for bypassing and removing FRP locks, aiming to solve the problems of complex operation, low feasibility, poor compatibility, and instability in the prior art when bypassing or removing FRP locks.

[0004] In a first aspect, embodiments of the present invention provide a method for bypassing and removing an FRP lock, comprising:

[0005] Close the adb process, connect and debug the mobile device;

[0006] By enabling the engineering test mode of the mobile device, permission is obtained to send information to the mobile device via the serial port;

[0007] A message list is constructed and sent to the mobile device via the serial port to control the mobile device to enable developer mode and USB debugging switch; wherein, the message list includes commands with various functions;

[0008] Send an adb command to modify settings to the mobile device so that the mobile device can bypass the FRP lock and directly access the desktop, and remove the FRP lock in the system settings of the mobile device.

[0009] Secondly, embodiments of the present invention also provide an apparatus for bypassing and removing an FRP lock, comprising:

[0010] The connection module is used to close the adb process and connect to and debug mobile devices.

[0011] The debugging module is used to obtain permission to send information to the mobile device via serial port by opening the engineering test mode of the mobile device;

[0012] An open module is used to construct and send a message list to the mobile device via the serial port to control the mobile device to enable developer mode and USB debugging; wherein, the message list includes commands with various functions;

[0013] The execution module is used to send adb modification settings commands to the mobile device, so that the mobile device can bypass the FRP lock and directly enter the desktop and remove the FRP lock in the system settings of the mobile device.

[0014] Thirdly, embodiments of the present invention also provide a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method of bypassing and removing the FRP lock as described above.

[0015] Fourthly, embodiments of the present invention also provide a computer-readable storage medium, wherein the storage medium stores a computer program that, when executed by a processor, can implement the method described above.

[0016] This invention provides a method, apparatus, and storage medium for bypassing and removing an FRP lock. The method includes: closing the adb process, connecting and debugging a mobile device; obtaining permission to send information to the mobile device via serial port by enabling the device's engineering test mode; constructing and sending a message list to the mobile device via the serial port to control the device to enable developer mode and USB debugging; wherein the message list includes commands with various functions; sending an adb setting modification command to the mobile device, enabling the device to bypass the FRP lock, directly access the desktop, and remove the FRP lock in the device's system settings. This embodiment removes the FRP lock by enabling developer mode and USB debugging via serial communication, without requiring firmware flashing or downloading, offering simple operation, high stability, and stronger compatibility. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Figure 1This is a flowchart illustrating a method for bypassing and removing an FRP lock according to an embodiment of the present invention.

[0018] Figure 1 A flowchart illustrating a method for bypassing and removing FRP locks provided in an embodiment of the present invention.

[0019] Figure 2 A schematic diagram of a sub-process of a method for bypassing and removing FRP locks provided in an embodiment of the present invention;

[0020] Figure 3 This is a schematic diagram of another sub-process for bypassing and removing an FRP lock device, provided by an embodiment of the present invention;

[0021] Figure 4 This is a schematic diagram of another sub-process for bypassing and removing an FRP lock device, provided by an embodiment of the present invention;

[0022] Figure 5 This is a schematic diagram of a structure for bypassing and removing an FRP lock device according to an embodiment of the present invention;

[0023] Figure 6 This is a schematic diagram of a sub-unit for bypassing and removing an FRP lock device according to an embodiment of the present invention;

[0024] Figure 7 This is a schematic diagram of another sub-unit for bypassing and removing the FRP lock device according to an embodiment of the present invention;

[0025] Figure 8 This is a schematic diagram of another sub-unit for bypassing and removing the FRP lock device, provided in an embodiment of the present invention. Detailed Implementation

[0026] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0027] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0028] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0029] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0030] As used in this specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrases "if determined" or "if [described condition or event] is detected" may be interpreted, depending on the context, as "once determined," "in response to determination," "once [described condition or event] is detected," or "in response to detection of [described condition or event]."

[0031] Figure 1 This is a flowchart illustrating the method for bypassing and removing FRP locks provided in an embodiment of the present invention. Figure 1 As shown, the method includes the following steps S101-S104.

[0032] S101. Close the adb process, connect and debug the mobile device.

[0033] In this embodiment of the invention, firstly, the adb process is closed, and then the mobile device whose FRP lock needs to be removed is connected via USB to debug the mobile device, thus avoiding USB usage conflicts.

[0034] In a specific application scenario, firstly, iterate and check if any adb processes are occupying the port; if so, close the adb process occupying the port; connect the mobile device and debug it; the port is used to connect to the mobile device. If the mobile device still cannot be found after connecting via USB, it may be because the port is occupied; check the port occupation status of all ports, find the adb process occupying the port, and close the adb process to resolve the port occupation issue, thus enabling a successful connection to the mobile device. When an adb process is occupying a port, you can use `adb kill-server` to close all adb processes; you can also close the corresponding adb process in Task Manager to avoid connection failures to mobile devices due to port occupation.

[0035] Additionally, suitable drivers based on the current system version need to be installed. These drivers are used to access mobile devices connected via USB, preparing for hardware communication with the mobile devices. Specifically, the type and version of the current PC (i.e., the host executing the method of this embodiment) system are first obtained, and it is determined whether the PC system is a Microsoft system or a Mac system. If the PC system is a Microsoft system, the Android driver is installed; if the PC system is a Mac system, the Android driver is not installed. If the installed driver is incompatible with the mobile device, debugging of the mobile device connected via USB will be impossible. After successfully installing the driver and connecting to the mobile device via USB, the mobile device information can be found in Device Manager, which serves as the basis for determining whether the connection with the mobile device is successful. Furthermore, because Mac systems have built-in communication drivers, when the PC system is a Mac, no driver installation is required to connect to the mobile device.

[0036] S102. By opening the engineering test mode of the mobile device, obtain the permission to send information to the mobile device via the serial port.

[0037] In this embodiment of the invention, an engineering test mode is triggered by entering an engineering test code in the dialer interface of the mobile device to perform engineering tests on the mobile device and modify some permissions of the mobile device. The engineering test code is provided by the manufacturer of the mobile device, and the engineering test codes are different between mobile devices of different brands. At the same time, the partial permissions opened by the engineering test are to send information to the mobile device through the serial port and communicate with the mobile device, that is, to provide conditions for serial communication.

[0038] In a specific application scenario, entering the engineering test code on the mobile device's dialer interface enters the device's engineering test mode interface. In engineering test mode, users can view performance and various hardware status information about the mobile device and perform engineering tests. During the engineering test, certain permissions on the mobile device are modified to achieve the testing objectives. This allows leveraging the device's already granted permissions and sending messages via serial port. Furthermore, the engineering test mode allows for pre-configuration of the mobile device, such as enabling permissions for Wi-Fi and Bluetooth.

[0039] S103. Construct and send a message list to the mobile device via a serial port to control the mobile device to enable developer mode and USB debugging switch; wherein, the message list includes commands with various functions.

[0040] In this embodiment, a message list is constructed by executing the commands in a specific order to control the mobile device to enable developer mode and USB debugging. If the commands are executed out of order, the goal of enabling developer mode and USB debugging cannot be achieved. By sending commands sequentially at intervals to grant permissions to the mobile device in sequence, the settings of the mobile device can be successfully modified.

[0041] In some embodiments, such as Figure 2 Methods for bypassing and removing FRP locks may also include the following steps:

[0042] S201. In Device Manager, query the name of the mobile device;

[0043] S202. Open the serial port registry, traverse the information of all serial ports, find the serial port whose name contains the name of the mobile device and obtain its information, and store the serial port information in the data structure according to the preset fields.

[0044] In a specific application scenario, firstly, the names of mobile devices connected via USB are queried in Device Manager to facilitate searching for the corresponding serial ports. The serial port registry is then opened, the serial port corresponding to the mobile device name is located, and the information of the found serial port is stored in a data structure according to preset fields. This structure contains the following information: Name (driver name, used for device selection); deviceID (port ID, used for sending messages); pnpDeviceID (driver device ID); and description.

[0045] For example, in this embodiment, such as Figure 3 As shown, step S300 may include steps S301-S305.

[0046] S301, Declare a serial port variable;

[0047] S302. Set the parameters for serial communication, including: baud rate, data bits, two stop bits, and parity bit;

[0048] S303. Construct a list of messages to be sent via serial port by writing the execution order of commands;

[0049] S304. Send the commands in the message list to the selected serial port in sequence at intervals;

[0050] S305: Receive the message returned by the mobile device, determine whether the message was sent successfully based on the received message, and then enable developer mode and USB debugging switch.

[0051] In this embodiment, a serial port variable is set to open the serial port and enable serial communication with the mobile device; a message list is constructed by writing the execution order of commands in the message list; after the message list is sent to the mobile device sequentially and at intervals through the serial port, the mobile device parses and executes the commands in the message list and returns data; the mobile device responds and enables developer mode and USB debugging.

[0052] Specifically, a serial port variable is declared and its properties are set for serial communication with the mobile device. The properties of this serial port variable include the following parameters: baud rate, data bits, two stop bits, and parity bit. For two devices communicating via serial ports, their serial port parameters must match; otherwise, communication will fail.

[0053] Baud rate is crucial for serial communication, ensuring timing synchronization between communicating parties. Data bits determine the number of valid data bits transmitted during serial communication. Stop bits not only indicate the end of transmission but also provide an opportunity to correct clock synchronization. Furthermore, if the receiver (mobile device) does not require a parity bit, it is not necessary to set its parameter. The parity bit verifies the correctness of the message list transmitted in serial communication. For example, using odd parity to detect the number of "1"s in the message list means that an odd number of errors are detected; an even number of errors will not be detected. For instance, if an odd number (e.g., 1, 3, 5, 7) of the seven signal bits of a transmitted character are simultaneously incorrect, they can be detected. However, if an even number (e.g., 2, 4, 6) of the bits are incorrect, they will not be detected. Therefore, the parity bit cannot accurately detect transmission errors in serial communication.

[0054] In addition, various commands in the message list are sent to the mobile device sequentially and at intervals. That is, commands are sent to the mobile device one by one via the serial port in the order of execution until the last command is executed, ending the sending operation. The various commands in the message list include: system-wide modification commands, dump control modification commands, privilege modification commands, activation modification commands, privilege modification commands, and debug LVC trigger commands. The commands are sent sequentially and at intervals, that is, by setting time intervals, the commands are sent to the mobile device one by one to avoid message conflicts during transmission.

[0055] In this embodiment, the commands in the message list can modify various permissions of the mobile device. Specifically, the execution order of the message list is as follows: First, a system-wide modification command is sent to set "Quickly check and verify whether the Android operating system on the device is authenticated and authorized" on the mobile device to authorized; second, a dump control modification command is sent to set the dump feature of some components on the mobile device to system dump, which enables developer mode; third, a privilege modification command is sent to disable the system operation permissions of the mobile device, which is used to obtain the system operation privileges of the mobile device; fourth, an activation modification command is sent to modify the internal activation permissions of the mobile device and set them to activated, which is used to enable USB debugging; fifth, a privilege modification command is sent to enable the system operation permissions, which is used to obtain the system operation privileges of the mobile device, corresponding to the command to disable the privilege modification command; sixth, an enable debugging LVC trigger command is sent to enable the USB debugging switch.

[0056] Alternatively, a command with a specific function can be set as a loop. After sending this command to the mobile device, a new command with a different function is sent after a time interval, such as 10 seconds. This sequential sending not only avoids message conflicts but also allows for the gradual granting of permissions to the mobile device to configure its internal information. For example, first, a system-wide modification command is sent to the mobile device, with a 10-second interval between sending. After 10 seconds, a dump control modification command is sent. If the two commands are sent in parallel, it could lead to message collisions: either the system-wide modification command is sent before the dump control command is modified, or the system-wide modification command is sent before the dump control command is fully sent. This could prevent the mobile device from successfully executing commands in the message list or even cause the mobile device to crash.

[0057] If the mobile device successfully parses and executes all commands in the message list, it will respond and enable developer mode and USB debugging. If it fails, the mobile device will remain unresponsive. Simultaneously, the mobile device will return data upon receiving the message list. Successful serial communication is determined by receiving and reading the data returned by the mobile device. For example, sending a message list to the mobile device: if the mobile device receives the message list and returns data, the serial communication is successful; if the mobile device does not receive the message list, it will remain unresponsive, and if no data is returned within a certain period, such as 5 seconds, the serial communication has failed.

[0058] S104. Send an adb command to modify settings to the mobile device so that the mobile device can bypass the FRP lock and directly access the desktop, and remove the FRP lock in the system settings of the mobile device.

[0059] In this embodiment, after successfully enabling developer mode and USB debugging, adb commands are sent to modify the device's settings, bypassing and removing the FRP lock.

[0060] For example, in this embodiment, such as Figure 4 As shown, step S400 may include steps S401-402:

[0061] S401. Send the adb command to modify settings information within the mobile device;

[0062] S402. Go to the system settings of the mobile device and remove the FRP lock.

[0063] In a specific application scenario, the settings information inside the mobile device in step S401 includes the following items: installation wizard, boot wizard, device pre-configuration key, and the boot wizard key defaults to installing applications from unknown sources. By setting the key value of all the above items to 1, the mobile device can skip the settings interface and directly enter the desktop after restarting, without getting stuck on the FRP lock interface. In other words, the FRP lock is successfully bypassed. The settings interface is used to initially configure the settings information of the mobile device. If the mobile device detects that the key value of a certain item is 0 during the boot and restart process (i.e., the item is not enabled), the mobile device will enter the settings interface and set the key value of that item. The FRP interface is a step in the settings interface. This will cause the mobile device to get stuck on the FRP interface. If the key value of all items in the mobile device's settings information is set to 1 (i.e., all items are enabled), the system of the mobile device has already configured the settings information by default, and thus it can skip the settings interface and directly enter the desktop without getting stuck on the FRP interface.

[0064] Specifically, setting the installation wizard key value to 1 enables the installation wizard's permission. After the mobile device restarts, the installation wizard will pop up to guide the user in configuring the mobile device and display the hardware status and software information of the mobile device.

[0065] Setting the startup wizard key value to 1 enables startup wizard permissions, guiding users to use or introducing basic information about the mobile device after it restarts.

[0066] Insert a device pre-configuration key into the database of the mobile device and set its key value to 1. That is, insert a device pre-configuration key into the mobile device and set the device pre-configuration key to allow users to define the function of the device pre-configuration key themselves.

[0067] Insert a startup wizard key into the database of the mobile device and set its key value to 1. That is, insert a startup wizard key into the mobile device and set the startup wizard key to perform initial settings on the mobile device during the startup process.

[0068] Insert a default key to open and install apps from unknown sources into the mobile device's database and set its value to 1. This means setting a default key to open and install apps from unknown sources on the mobile device and setting its value to 1. This enables the default key to open and install apps from unknown sources on the mobile device, allowing users to install apps from unknown sources without having to confirm it every time they install a new app.

[0069] Furthermore, after bypassing the FRP lock and entering the desktop, the mobile device has not yet removed the FRP lock. Therefore, upon the next reboot, the mobile device will become confused, causing it to randomly enter either the desktop or the FRP lock interface, resulting in screen flickering. Thus, it is necessary to send a command to the mobile device to switch to the desktop to control it to exit the FRP lock interface; then, send a command to the mobile device to switch to system settings, i.e., enter the mobile device's system settings and remove the FRP lock setting.

[0070] By modifying the FRP lock key value in the system settings to remove the FRP lock, the mobile device will directly enter the desktop after restarting and will no longer enter the FRP lock interface.

[0071] The method in this embodiment removes the FRP lock by enabling developer mode and USB debugging via serial communication. It requires no flashing or firmware download, is simple to operate, highly stable, and has stronger compatibility.

[0072] Please see Figure 5 , Figure 5 A schematic diagram of the structure of a device 500 for bypassing and removing an FRP lock provided in an embodiment of the present invention;

[0073] The device may include:

[0074] Connection module 501 is used to close the adb process and connect to and debug mobile devices.

[0075] The debugging module 502 is used to obtain permission to send information to the mobile device via serial port by opening the engineering test mode of the mobile device;

[0076] The response module 503 is used to construct and send a message list to the mobile device via a serial port to control the mobile device to enable developer mode and USB debugging switch; the message list includes commands with various functions.

[0077] Execution module 504 is used to send adb modification settings commands to the mobile device so that the mobile device can bypass the FRP lock and directly access the desktop and remove the FRP lock in the system settings of the mobile device.

[0078] The device in this embodiment unlocks FRP by using serial port operation to enable developer mode and USB debugging, without flashing the firmware or downloading firmware. It is simple to operate, highly stable, and has stronger compatibility.

[0079] In one embodiment, such as Figure 6 As shown, the connection module 501 includes:

[0080] Traverse unit 601, used to traverse whether there is an adb process occupying the port;

[0081] Shutdown unit 602 is used to shut down all adb processes if they exist, by using adbkill-server.

[0082] In one embodiment, such as Figure 7 As shown, the response module 503 includes:

[0083] Declaration unit 701 is used to declare a serial port variable;

[0084] Setting unit 702 is used to set parameters for serial communication, including: baud rate, data bits, two stop bits, and parity bit;

[0085] Construction unit 703 is used to construct the message list sent through the serial port by writing the execution order of the commands;

[0086] The sending unit 704 is used to sequentially and at intervals send commands from the message list to the selected serial port;

[0087] The determining unit 705 is used to receive the message returned by the mobile device, determine whether the message was sent successfully based on the received message, and thus enable developer mode and USB debugging switch.

[0088] In one embodiment, such as Figure 8 As shown, the execution module 504 includes:

[0089] Modification unit 801 is used to send an adb command to the mobile device to modify the settings information of the mobile device;

[0090] The jump unit 802 is used to restart the mobile device and send an adb command to the mobile device to control the mobile device to jump directly to its desktop after powering on.

[0091] The removal unit 803 is used to access the system settings of the mobile device and disable the FRP lock.

[0092] Since the embodiments of the apparatus and the embodiments of the method correspond to each other, please refer to the description of the embodiments of the method for the embodiments of the apparatus, which will not be repeated here.

[0093] This invention also provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the above-described method for bypassing and removing FRP locks.

[0094] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program may be stored in a storage medium, which is a computer-readable storage medium. The computer program is executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0095] Therefore, the present invention also provides a storage medium. This storage medium can be a computer-readable storage medium. The storage medium stores a computer program. When executed by a processor, the computer program causes the processor to perform any embodiment of the above-described communication method between the indoor and outdoor units of an air conditioner.

[0096] The storage medium can be any computer-readable storage medium capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory (ROM), magnetic disk, or optical disk.

[0097] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0098] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0099] The steps in the method of this invention can be adjusted, merged, or reduced in order according to actual needs. The units in the device of this invention can be merged, divided, or reduced according to actual needs. Furthermore, the functional units in the various embodiments of this invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0100] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an air conditioner to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0101] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0102] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Since these modifications and variations fall within the scope of the claims and their equivalents, this invention also intends to include these modifications and variations.

[0103] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for bypassing and removing FRP locks, characterized in that, include: Close the adb process, connect and debug the mobile device; By enabling the engineering test mode of the mobile device, permission is obtained to send information to the mobile device via the serial port; A message list is constructed and sent to the mobile device via the serial port to control the mobile device to enable developer mode and USB debugging switch; wherein, the message list includes commands with various functions; Send an adb command to modify settings to the mobile device so that the mobile device can bypass the FRP lock and directly access the desktop, and remove the FRP lock in the system settings of the mobile device. Open the serial port registry, iterate through the information of all serial ports, and determine whether the name of each serial port contains the name of the mobile device; if so, select the corresponding serial port and store the information of the serial port according to a preset data structure. The method of bypassing the FRP lock to directly access the desktop and removing the FRP lock in the system settings of the mobile device includes: sending an adb command to the mobile device to modify the settings information of the mobile device; restarting the mobile device and sending an adb command to the mobile device to control the mobile device to directly jump to its desktop after powering on; and entering the system settings of the mobile device to disable the FRP lock.

2. The method for bypassing and removing the FRP lock according to claim 1, characterized in that, The process of connecting and debugging the mobile device and closing the adb process includes: Iterate through whether an adb process is using a port; If it exists, you can use adb kill-server to shut down all adb processes.

3. The method for bypassing and removing the FRP lock according to claim 1, characterized in that, The construction and sending of a message list to the mobile device via the serial port to control the mobile device to enable developer mode and USB debugging switch includes: Declare a serial port variable; Configure the parameters for serial communication, including: baud rate, data bits, two stop bits, and parity bit; By writing the execution order of the commands, a list of messages sent through the serial port is constructed; Commands from the message list are sent sequentially and at intervals to the selected serial port; The system receives a message returned by the mobile device, determines whether the message was sent successfully based on the received message, and then enables developer mode and USB debugging.

4. The method for bypassing and removing the FRP lock according to claim 3, characterized in that, The step of sequentially and at intervals sending commands from the message list to the selected serial port includes: Each of the commands in the message list is sent sequentially and at intervals through the serial port in the order of execution of each command. Once all commands have been sent, the sending operation ends.

5. The method for bypassing and removing the FRP lock according to claim 1, characterized in that, The step of closing the adb process, connecting and debugging the mobile device also includes: Obtain the type of the current system and determine whether the current system is a Microsoft system; If the current system type is a Microsoft system, then install the Android driver; if the current system type is a Mac system, then do not install the Android driver.

6. A device for bypassing and removing FRP locks, characterized in that, include: The connection module is used to close the adb process and connect to and debug mobile devices. The debugging module is used to obtain permission to send information to the mobile device via serial port by opening the engineering test mode of the mobile device; A response module is used to construct and send a message list to the mobile device via the serial port to control the mobile device to enable developer mode and USB debugging switch; wherein, the message list includes commands with various functions; The execution module is used to send adb modification settings commands to the mobile device, so that the mobile device can bypass the FRP lock and directly enter the desktop and remove the FRP lock in the system settings of the mobile device; The device for bypassing and removing the FRP lock is also used to open the serial port registry, traverse the information of all serial ports, and determine whether the name of each serial port contains the name of the mobile device; if so, the corresponding serial port is selected and the information of the serial port is stored according to a preset data structure. The execution module is specifically used to send an adb command to the mobile device to modify the settings information of the mobile device; restart the mobile device by sending an adb command to the mobile device to control the mobile device to jump directly to its desktop after powering on; and enter the system settings of the mobile device to disable the FRP lock.

7. A computer device, characterized in that, The device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method for bypassing and removing the FRP lock as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, can implement the method as described in any one of claims 1-5.

Images