Terminal information reading method, device, apparatus, and storage medium

Abstract

The application relates to a terminal information reading method, device, equipment and storage medium. The method comprises the following steps: identifying an accessed terminal device, and acquiring identification information of the terminal device; sending a preset indication command to the terminal device in a Fastboot mode according to the identification information; and receiving device information fed back by the terminal device based on the received preset indication command. The scheme provided by the application can read device information in a terminal device lock screen state, and complete device forensics work.

Description

Technical Field

[0001] This application relates to the field of device forensics technology, and in particular to a terminal information reading method, apparatus, device and storage medium. Background Technology

[0002] With the emergence of smartphones and tablets, the methods for obtaining evidence from mobile phones and other terminal devices are constantly being updated and improved. Currently, it is possible to process, fix, and analyze the identification information (such as model and version) and application data (such as instant messaging tools and social networking tools) of terminal devices.

[0003] However, in related technologies, the processing of terminal device information is often carried out when the device is unlocked. When the device is not unlocked, it is difficult to obtain the device information to complete the device forensics work. Summary of the Invention

[0004] To address or partially address the problems existing in related technologies, this application provides a terminal information reading method, apparatus, device, and storage medium, which can read device information in the locked state of a terminal device to complete device certification work.

[0005] The first aspect of this application provides a method for reading terminal information, including:

[0006] Identify the accessing terminal device and obtain the identification information of the terminal device;

[0007] A preset instruction command is sent to the terminal device that has entered Fastboot mode based on the identification information;

[0008] Receive device information fed back by the terminal device based on the received preset instruction command.

[0009] In one embodiment, identifying the accessed terminal device and obtaining the identification information of the terminal device includes:

[0010] The first communication link is established by identifying the connected terminal device through LibUSB;

[0011] The terminal device in Fastboot mode is identified by the ADB program, and a second communication link is established.

[0012] The identification information of the terminal device is obtained through the first communication link and the second communication link.

[0013] In one embodiment, obtaining the identification information of the terminal device through the first communication link and the second communication link includes:

[0014] The first device identifier is obtained through the first communication link, and the second device identifier is obtained through the second communication link;

[0015] If the first device identifier is the same as the second device identifier, then the first device identifier is determined to be the identification information;

[0016] If the first device identifier and the second device identifier are inconsistent, then the second device identifier is determined to be the identification information.

[0017] In one embodiment, after establishing a first communication link with the terminal device accessed via LibUSB, the method further includes:

[0018] The interface displays a guide prompt. By following the guide prompt, the terminal device enters Fastboot mode.

[0019] In one embodiment, sending a preset instruction command to the terminal device that has entered Fastboot mode based on the identification information includes:

[0020] Based on the identification information of the terminal device that has entered Fastboot mode, a preset instruction command matching the identification information is searched in the database and sent to the terminal device that has entered Fastboot mode.

[0021] In one embodiment, identifying the accessed terminal device and obtaining the identification information of the terminal device includes:

[0022] Identify all connected terminal devices;

[0023] Select one terminal device from all terminal devices and obtain the identification information of the terminal device, and establish a device file that stores the identification information;

[0024] The step of receiving device information fed back by the terminal device based on the received preset instruction command includes:

[0025] The device receives device information fed back by the terminal device based on the received preset instruction command and stores it in the corresponding device file.

[0026] A second aspect of this application provides a terminal information reading device, comprising:

[0027] The identification module is used to identify the accessed terminal device and obtain the identification information of the terminal device;

[0028] The processing module is used to send a preset instruction command to the terminal device that has entered Fastboot mode based on the identification information obtained by the identification module.

[0029] The receiving module is used to receive device information fed back by the terminal device based on the preset instruction command sent by the processing module.

[0030] In one embodiment, the identification module includes:

[0031] The first submodule is used to identify the connected terminal device through LibUSB and establish the first communication link;

[0032] The second submodule is used to identify the terminal device in Fastboot mode through the ADB program and establish a second communication link;

[0033] The third submodule is used to obtain the identification information of the terminal device through the first communication link and the second communication link.

[0034] A third aspect of this application provides an electronic device, comprising:

[0035] Processor; and

[0036] A memory that stores executable code, which, when executed by the processor, causes the processor to perform the method described above.

[0037] A fourth aspect of this application provides a computer-readable storage medium having executable code stored thereon, which, when executed by a processor of an electronic device, causes the processor to perform the method described above.

[0038] The technical solution provided in this application can include the following beneficial effects: by identifying terminal devices in Fastboot mode, device information of the terminal device can be obtained without unlocking the terminal device, avoiding the need for a password to unlock the terminal device screen, which is conducive to the smooth completion of device forensics.

[0039] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0040] The above and other objects, features and advantages of this application will become more apparent from the following description of exemplary embodiments of this application in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments of this application.

[0041] Figure 1 This is a schematic diagram illustrating an application scenario as shown in an embodiment of this application;

[0042] Figure 2 This is a schematic diagram of the extraction engine structure shown in an embodiment of this application;

[0043] Figure 3 This is a schematic flowchart illustrating the terminal information reading method according to an embodiment of this application;

[0044] Figure 4 This is another schematic flowchart illustrating the terminal information reading method in an embodiment of this application;

[0045] Figure 5 This is a schematic diagram of the structure of the terminal information reading device shown in the embodiments of this application;

[0046] Figure 6 This is a schematic diagram of the structure of an electronic device shown in an embodiment of this application. Detailed Implementation

[0047] Embodiments of this application will now be described in more detail with reference to the accompanying drawings. While embodiments of this application are shown in the drawings, it should be understood that this application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to make this application more thorough and complete, and to fully convey the scope of this application to those skilled in the art.

[0048] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0049] It should be understood that although the terms "first," "second," "third," etc., may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0050] First, some of the terms and related technologies used in this application will be explained to facilitate understanding by those skilled in the art.

[0051] USB (Universal Serial Bus) is a high-speed serial transmission bus that supports hot-plugging and uses differential signaling to transmit data. The USB architecture consists of three parts: "host," "device," and "physical connection." The host is a combination of hardware, software, and firmware that provides the USB interface and interface management capabilities, such as a computer. Devices include USB functional devices and USB hubs, such as mobile phones. The physical connection can be a USB data cable, which enables the connection between the "host" and the "device" to achieve interaction between them.

[0052] Fastboot mode, commonly known as fast boot mode, is included in the Android SDK (Android Software Development Kit). It's a communication protocol and tool used by servers to flash, erase / format, debug, and transmit commands to Android system terminal devices via a USB data cable. There are two ways for a terminal device to enter Fastboot mode: the first is when the terminal device is powered on and has been authenticated; the second is when the terminal device is powered off, typically by simultaneously pressing and holding the back button and power button to power on, and then pressing the power button when the Fastboot option appears on the device's interface. The second method of entering Fastboot mode varies depending on the brand and model of the terminal device, and this application does not impose any restrictions on it.

[0053] ADB (Android Debug Bridge) is included in the Android SDK. It is a client-server program where the client can be a server, such as a computer, and the server can be an Android terminal device. In other words, ADB can be used for interaction between the server and the terminal device.

[0054] LibUSB (Library for USB) is a userspace C library for accessing USB devices. It is implemented in C, is portable, and currently supports platforms such as Linux, macOS, Windows, Android, OpenBSD / NetBSD, Haiku, and Solaris.

[0055] In related technologies, reading terminal device information is often performed when the device is unlocked. When the device is locked, it is difficult to obtain device information for forensic purposes. To address this issue, this application provides a terminal information reading method that can read device information while the device is locked, thus enabling forensic investigation.

[0056] The terminal information reading method provided in this application is executed by an extraction engine; see [link to relevant documentation]. Figure 1 , Figure 1 This is a schematic diagram illustrating an application scenario as shown in an embodiment of this application. For example... Figure 1 As shown, in a specific embodiment, the extraction engine 11 can be deployed in any server 1; the user can use a USB data cable to enable the terminal device 2 to interact with the server 1 to receive or send messages, etc. The terminal device 2 can be a mobile phone, tablet or other device that can interact with the server 1 via a USB data cable, and this application does not limit it.

[0057] The extraction engine is used to identify the terminal device and obtain its device information. See also Figure 2 , Figure 2 This is a schematic diagram of the structure of the extraction engine 11 shown in the embodiment of this application. The extraction engine 11 includes LibUSB and ADB program. The extraction engine 11 can identify the terminal device 2 that has established an interactive relationship with the server 1 through LibUSB and ADB program, and establish a communication link with the terminal device 2 in Fastboot mode based on the ADB program, thereby obtaining the device information of the terminal device 2.

[0058] The technical solutions of the embodiments of this application are described in detail below with reference to the accompanying drawings.

[0059] Figure 3 This is a schematic flowchart illustrating the terminal information reading method in an embodiment of this application.

[0060] See Figure 3 The method includes the following steps:

[0061] S110. Identify the accessed terminal device through the extraction engine and obtain the identification information of the terminal device.

[0062] Once the extraction engine deployed on the server is started, it can identify terminal devices connected to the server via USB data cable, thereby obtaining the identification information of the identified terminal devices. These terminal devices can be Android phones, tablets, or other similar devices.

[0063] In one embodiment, the extraction engine can identify the accessed terminal device through the pre-built LibUSB and establish a first communication link. The extraction engine then obtains the terminal device's identification information through this first communication link. LibUSB, as a USB device access interface library, provides access permissions to the extraction engine and establishes the first communication link for data transmission between the extraction engine and the terminal device, enabling the extraction engine to access USB devices via LibUSB. The establishment of this first communication link allows interaction between the extraction engine and the terminal device, allowing the extraction engine to obtain the identified identification information of the terminal device. This identification information may include the terminal device's type, brand, model, etc.

[0064] In one embodiment, after the extraction engine identifies the connected terminal device through its built-in LibUSB, the extraction engine's interface displays a guidance prompt. The user can follow the prompt to put the terminal device into Fastboot mode, thereby facilitating the extraction engine to obtain the terminal device's identification information through the first communication link. The guidance prompt is a method for guiding the terminal device into Fastboot mode.

[0065] In one embodiment, the extraction engine can identify all connected terminal devices via a USB data cable and select one terminal device from all terminal devices to obtain its identification information. The extraction engine can select one terminal device from all terminal devices and obtain the corresponding identification information for subsequent processing steps, and then sequentially select the other terminal devices from all terminal devices for subsequent steps.

[0066] In one embodiment, the extraction engine can identify all connected terminal devices via a USB data cable, select one terminal device from all terminal devices to obtain its identification information, create a device file storing the identification information, and then proceed with subsequent steps. The device file can be displayed on the extraction engine's startup interface. The naming method for the device file includes, but is not limited to, naming it with the terminal device's identification information or naming it with the time the terminal device was identified.

[0067] In one embodiment, after establishing a device profile for one terminal device, other connected terminal devices can be selected, their identification information obtained, and device profiles established. Then, each device profile can be selected for subsequent steps. Alternatively, after establishing a device profile for one terminal device, subsequent steps can be performed. Once all steps for acquiring information about that terminal device are completed, the system returns to the extraction engine's startup interface, where other terminal devices can be selected, their identification information obtained, and device profiles established. Both paths can accomplish the step of acquiring device information from all connected terminal devices one by one, and this application does not impose any limitations on this approach.

[0068] S120. Send a preset instruction command to the terminal device that has entered Fastboot mode based on the identification information.

[0069] In one embodiment, the extraction engine can search the database for preset instruction commands that match the terminal device's identification information, and send these preset instruction commands to the terminal device via a pre-built-in ADB program. The identification information includes the terminal device's brand and model. The extraction engine can search the database for corresponding preset instruction commands based on the terminal device's brand and model. The preset instruction commands are tailored to different terminal device brands; for example, Huawei phones use "getvar:rescue_phoneinfo", while Vivo phones use "oemdevice-name".

[0070] S130, Receive device information fed back by the terminal device based on the received preset instruction command.

[0071] In one embodiment, after receiving a preset instruction command corresponding to its brand, the terminal device makes a corresponding response based on the preset instruction command, the extraction engine receives the bytecode fed back by the terminal device through serial port parsing, and then parses the bytes into the device information of the terminal device.

[0072] In one embodiment, after receiving the device information fed back by the terminal device, the extraction engine displays it on the extraction engine's acquisition interface. The user can record the device information of the terminal device displayed on the acquisition interface and store it in a set path on the server.

[0073] In one embodiment, after the extraction engine receives the device information fed back by the terminal device, it can store it in the device file about the terminal device established in S110. The user can record the device information of the terminal device in the device file and store it in a set path on the server.

[0074] The terminal information reading method of this application embodiment uses a pre-built LibUSB extraction engine to automatically identify the terminal device, and sends a preset instruction command to the terminal device in Fastboot mode through a pre-built ADB program to obtain the device information of the terminal device. This allows the extraction engine to obtain the device information of the terminal device when the terminal device is locked without the need for authentication by the terminal device, which facilitates the evidence collection of the terminal device and is conducive to the smooth progress of the device evidence collection work.

[0075] Figure 4 This is another schematic flowchart illustrating the terminal information reading method in an embodiment of this application.

[0076] See Figure 4 The method includes the following steps:

[0077] S210. Identify the connected terminal device through the LibUSB extraction engine and obtain the first device identifier of the terminal device; identify the terminal device in Fastboot mode through the ADB program of the extraction engine and obtain the second device identifier of the terminal device.

[0078] In one embodiment, the extraction engine can identify the connected terminal device through the pre-built LibUSB and establish a first communication link, through which it can obtain the first device identifier of the terminal device. Then, it can identify the connected terminal device in Fastboot mode through a pre-built ADB program and establish a second communication link, through which it can obtain the second device identifier of the terminal device. LibUSB, as a USB device access interface library, provides access permissions to the extraction engine, establishing the first communication link for data transfer between the extraction engine and the terminal device, allowing the extraction engine to access USB devices through LibUSB. Android system terminal devices have an ADB toolkit, and the extraction engine has a pre-built ADB program. The extraction engine can identify terminal devices with an ADB toolkit and operating in Fastboot mode through the ADB program, thereby establishing the second communication link for data transfer between the extraction engine and the terminal device.

[0079] The establishment of the first and second communication links enables interaction between the extraction engine and the terminal device, allowing the extraction engine to obtain the first and second device identifiers of the identified terminal device. Both the first and second device identifiers can include information such as the type, brand, and model of the terminal device.

[0080] In one embodiment, after the extraction engine identifies the connected terminal device and obtains the first device identifier through the pre-built LibUSB, the extraction engine's interface displays boot information. The user can operate the terminal device according to the boot information to make the terminal device enter Fastboot mode. At this time, the extraction engine can perform secondary identification of the terminal device that has entered Fastboot mode through the pre-built ADB program and obtain the second device identifier of the terminal device.

[0081] S220. Determine whether the first device identifier and the second device identifier are consistent. If yes, proceed to S230; otherwise, proceed to S240.

[0082] By comparing the first device identifier and the second device identifier obtained in S210, the type, brand, model, etc. of the terminal device corresponding to the first device identifier can be compared one by one with the type, brand, model, etc. of the terminal device corresponding to the second device identifier. When the first device identifier and the second device identifier are completely equal, it can be determined that the first device identifier and the second device identifier are consistent; when the first device identifier and the second device identifier are not completely equal, it can be determined that the first device identifier and the second device identifier are inconsistent.

[0083] S230: Determine that the first device identifier is the identifier information of the terminal device, and send a preset instruction command to the terminal device that has entered Fastboot mode according to the identifier information; execute S250.

[0084] When the first device identifier and the second device identifier are completely identical, the extraction engine sends a preset instruction command to the terminal device that has entered Fastboot mode based on the first device identifier. Alternatively, the extraction engine can send a preset instruction command to the terminal device that has entered Fastboot mode based on the second device identifier.

[0085] S240: Determine that the second device identifier is the identifier information of the terminal device, and send a preset instruction command to the terminal device that has entered Fastboot mode according to the identifier information; execute S250.

[0086] The secondary identification by the extraction engine involves recognizing terminal devices that have entered Fastboot mode. This means that the extraction engine's ADB program is enabled during this secondary identification. The engine uses its pre-built-in ADB program to filter terminal devices, excluding those without ADB tools, such as hard drives, allowing for accurate identification of Android system terminal devices. Therefore, the second device identifier obtained after secondary identification confirms that the device is running Android. The engine then searches the database for a preset instruction command that matches the terminal device's second device identifier and sends this command to the device. This preset instruction command is customized based on the terminal device brand; for example, Huawei phones use "getvar:rescue_phoneinfo", while Vivo phones use "oem device-name". This ensures high accuracy in matching both the second device identifier and the preset instruction command.

[0087] S250, Receive device information fed back by the terminal device based on the received preset instruction command.

[0088] This step can be found in the description of S130, and will not be repeated here.

[0089] The terminal information reading method in this application uses an extraction engine with pre-built LibUSB and ADB clients to automatically identify the terminal device in Fastboot mode twice, and receive the device information of the terminal device through a preset instruction command. This allows the extraction engine to obtain the device information of the terminal device when the terminal device is locked without the need for authentication by the terminal device, which facilitates the evidence collection of the terminal device and is conducive to the smooth progress of the device evidence collection work. Furthermore, by identifying the terminal device twice, before and after entering Fastboot mode, the accuracy of the device information of the terminal device obtained by the extraction engine is high.

[0090] Corresponding to the aforementioned application function implementation method embodiments, this application also provides a terminal information reading device, an electronic device, and corresponding embodiments.

[0091] Figure 5 This is a schematic diagram of the terminal information reading device shown in the embodiments of this application.

[0092] See Figure 5 The terminal information reading device 500 includes: an identification module 510, a processing module 520, and a receiving module 530.

[0093] The identification module 510 is used to identify the accessed terminal device and obtain the identification information of the terminal device.

[0094] In one embodiment, the identification module 510 includes a first submodule, a second submodule, and a third submodule. The first submodule is used to identify the accessed terminal device via LibUSB, establish a first communication link, and obtain a first device identifier. The second submodule is used to identify the terminal device in Fastboot mode via an ADB program, establish a second communication link, and obtain a second device identifier. The third submodule is used to obtain the terminal device's identification information via the first and second communication links.

[0095] In one embodiment, the identification module 510 is used to identify all accessed terminal devices, select one of the terminal devices and obtain the identification information of the terminal device, and establish a device file that stores the identification information.

[0096] The processing module 520 is used to send a preset instruction command to the terminal device that has entered Fastboot mode based on the identification information of the terminal device obtained by the identification module 510.

[0097] In one embodiment, the processing module 520 is used to search the database for a preset instruction command that matches the identification information of the terminal device that has entered Fastboot mode, and send the preset instruction command to the terminal device.

[0098] The receiving module 530 is used to receive device information fed back by the terminal device based on the preset instruction command sent by the processing module 520.

[0099] In one embodiment, the receiving module 530 is used to receive device information fed back by the terminal device based on the received preset instruction command, and store it in the device file established by the identification module 510.

[0100] The terminal information reading device in this application embodiment uses a pre-built LibUSB extraction engine to automatically identify the terminal device. It also sends a preset instruction command to the terminal device in Fastboot mode through a pre-built ADB program to obtain the device information of the terminal device. This allows the extraction engine to obtain the device information of the terminal device when the terminal device is locked without the need for authentication by the terminal device, which facilitates the evidence collection of the terminal device and helps the device evidence collection work to proceed smoothly.

[0101] Figure 6 This is a schematic diagram of the structure of an electronic device shown in an embodiment of this application.

[0102] See Figure 6 The electronic device 600 includes a memory 610 and a processor 620.

[0103] The processor 620 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0104] Memory 610 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage devices. ROM may store static data or instructions required by the processor 620 or other modules of the computer. Permanent storage devices may be read-write storage devices. Permanent storage devices may be non-volatile storage devices that retain stored instructions and data even when the computer is powered off. In some embodiments, permanent storage devices use mass storage devices (e.g., magnetic or optical disks, flash memory) as permanent storage devices. In other embodiments, permanent storage devices may be removable storage devices (e.g., floppy disks, optical drives). System memory may be a read-write storage device or a volatile read-write storage device, such as dynamic random access memory. System memory may store some or all of the instructions and data required by the processor during operation. Furthermore, memory 610 may include any combination of computer-readable storage media, including various types of semiconductor memory chips (e.g., DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and disks and / or optical disks may also be used. In some embodiments, memory 610 may include a removable storage device that is readable and / or writable, such as a laser disc (CD), a read-only digital multifunction optical disc (e.g., DVD-ROM, dual-layer DVD-ROM), a read-only Blu-ray disc, an ultra-high density optical disc, a flash memory card (e.g., SD card, mini SD card, Micro-SD card, etc.), a magnetic floppy disk, etc. Computer-readable storage media do not contain carrier waves or transient electronic signals transmitted wirelessly or via wired connections.

[0105] The memory 610 stores executable code, which, when processed by the processor 620, can cause the processor 620 to execute part or all of the methods described above.

[0106] Furthermore, the method according to this application can also be implemented as a computer program or computer program product, which includes computer program code instructions for performing some or all of the steps in the method described above.

[0107] Alternatively, this application may be implemented as a computer-readable storage medium (or a non-transitory machine-readable storage medium or a machine-readable storage medium) storing executable code (or computer program or computer instruction code) thereon, which, when executed by a processor of an electronic device (or server, etc.), causes the processor to perform part or all of the steps of the methods described above according to this application.

[0108] The various embodiments of this application have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A terminal information reading method, characterized by, include: Identify the accessing terminal device and obtain the identification information of the terminal device; Sending a preset instruction command to the terminal device that has entered Fastboot mode according to the identification information; the identification information includes the brand and model of the terminal device, and sending the preset instruction command to the terminal device that has entered Fastboot mode according to the identification information includes: determining the brand and model of the terminal device according to the identification information; searching for the corresponding preset instruction command in the database according to the brand and model of the terminal device; and sending the corresponding preset instruction command to the terminal device that has entered Fastboot mode. Receive device information fed back by the terminal device based on the received preset instruction command; The terminal device that is being identified and accessed. And obtain the identification information of the terminal device, including: The first communication link is established by identifying the connected terminal device through LibUSB; The terminal device in Fastboot mode is identified by the ADB program, and a second communication link is established. The identification information of the terminal device is obtained through the first communication link and the second communication link.

2. The terminal information reading method according to claim 1, characterized by: The step of obtaining the identification information of the terminal device through the first communication link and the second communication link includes: The first device identifier is obtained through the first communication link, and the second device identifier is obtained through the second communication link; If the first device identifier is the same as the second device identifier, then the first device identifier is determined to be the identification information; If the first device identifier and the second device identifier are inconsistent, then the second device identifier is determined to be the identification information.

3. The terminal information reading method according to claim 1, characterized by, After establishing a first communication link by identifying the accessing terminal device via LibUSB, the method further includes: The interface displays a guide prompt. By following the guide prompt, the terminal device enters Fastboot mode.

4. The terminal information reading method according to claim 1, characterized in that: The process of identifying the accessing terminal device and obtaining the identification information of the terminal device includes: Identify all connected terminal devices; Select one terminal device from all terminal devices and obtain the identification information of the terminal device, and establish a device file that stores the identification information; The step of receiving device information fed back by the terminal device based on the received preset instruction command includes: The device receives device information fed back by the terminal device based on the received preset instruction command and stores it in the corresponding device file.

5. A terminal information reading device, characterized by comprising: include: The identification module is used to identify the accessed terminal device and obtain the identification information of the terminal device; The processing module is configured to send a preset instruction command to the terminal device that has entered Fastboot mode based on the identification information obtained by the identification module; the identification information includes the brand and model of the terminal device; sending the preset instruction command to the terminal device that has entered Fastboot mode based on the identification information obtained by the identification module includes: determining the brand and model of the terminal device based on the identification information; searching for the corresponding preset instruction command in the database based on the brand and model of the terminal device; and sending the corresponding preset instruction command to the terminal device that has entered Fastboot mode. The receiving module is used to receive device information fed back by the terminal device based on the preset instruction command sent by the processing module. The identification module includes: The first submodule is used to identify the connected terminal device through LibUSB and establish the first communication link; The second submodule is used to identify the terminal device in Fastboot mode through the ADB program and establish a second communication link; The third submodule is used to obtain the identification information of the terminal device through the first communication link and the second communication link.

6. An electronic device, comprising: include: processor; as well as A memory having executable code stored thereon, which, when executed by the processor, causes the processor to perform the method as described in any one of claims 1-4.

7. A computer readable storage medium characterized in that, It stores executable code that, when executed by a processor of an electronic device, causes the processor to perform the method as described in any one of claims 1-4.

Images