CN110879765A - Method and device for avoiding terminal abnormity - Google Patents
Method and device for avoiding terminal abnormity Download PDFInfo
- Publication number
- CN110879765A CN110879765A CN201911117101.6A CN201911117101A CN110879765A CN 110879765 A CN110879765 A CN 110879765A CN 201911117101 A CN201911117101 A CN 201911117101A CN 110879765 A CN110879765 A CN 110879765A
- Authority
- CN
- China
- Prior art keywords
- communication protocol
- storage area
- file
- terminal
- recovery program
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
Abstract
The invention discloses a method and a device for avoiding terminal abnormity, wherein a bootstrap program does not need to be updated when a communication protocol is changed, but a recovery program signature file is updated, when a terminal fails to operate an application program of a second communication protocol, the terminal can remind and wait for receiving a recovery signal triggered by a user, after receiving the recovery signal, the terminal writes a recovery program executable file in the recovery program signature file supporting the second communication protocol in a first storage area of an external flash into the first storage area of an internal flash, and after the terminal succeeds in writing, the terminal operates the application program of the second communication protocol and judges whether the operation succeeds or not, until the terminal works normally after the operation succeeds; the situation that the terminal cannot be recovered due to the fact that the bootstrap program is lost in the process of recovering the signature file of the program is avoided, the process of returning to the factory for maintenance is omitted, cost is saved, and the terminal is convenient to use.
Description
Technical Field
The invention relates to the field of terminal products, in particular to a method and a device for avoiding terminal abnormity.
Background
The application executable file is a binary file which is obtained after application codes are compiled and linked and can be identified by the terminal; the recovery program signature file is a signature file package containing a certificate and a recovery program executable file; the recovery program executable file is a binary file which can be identified by a machine and is obtained after the code of the recovery program is compiled and linked; the boot program is used to initialize the terminal hardware module and establish an appropriate hardware environment.
In the prior art, a terminal includes two parts, namely a boot loader and an application program, functions of the boot loader include receiving a recovery signal, loading an application program executable file, and communicating, the function of receiving the recovery signal or the function of loading the application program executable file may be lost when the update operation is performed due to the change of the communication function of the boot loader, and the boot loader cannot recover when the update operation is performed by using the boot loader, so that the terminal is paralyzed, the terminal needs to be returned to a factory for maintenance, the use of a user is inconvenient, and the after-sale service cost is increased.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provides a method and a device for avoiding terminal abnormity.
The invention provides a method for avoiding terminal abnormity, which comprises the following steps:
step R1: the terminal runs an application program of a first communication protocol, receives a recovery program signature file which is sent by an upper computer and supports a second communication protocol, stores the recovery program signature file in a communication cache region, and replaces the recovery program signature file which supports the first communication protocol in a first storage region of an external flash by using the recovery program signature file which supports the second communication protocol in the communication cache region;
step R2: the terminal judges whether the recovery program signature file supporting the second communication protocol of the communication cache area replaces the recovery program signature file supporting the first communication protocol of the first storage area of the external flash successfully, if so, the step R3 is executed, otherwise, the step R1 is returned;
step R3: the terminal receives the application program executable file supporting the second communication protocol and sent by the upper computer, stores the application program executable file supporting the second communication protocol in the communication cache area, and writes the application program executable file supporting the second communication protocol in the communication cache area into a second storage area of the external flash;
step R4: the terminal runs a bootstrap program and writes an application program executable file supporting a second communication protocol in a second storage area of the external flash into a first storage area of the internal flash;
step R5: the terminal judges whether the application program executable file supporting the second communication protocol in the second storage area of the external flash is successfully written into the first storage area of the internal flash, if so, a step R8 is executed, otherwise, a step R6 is executed;
step R6: the terminal writes a recovery program executable file in a recovery program signature file supporting a second communication protocol in a first storage area of the external flash into a first storage area of the internal flash;
step R7: the terminal judges whether the executable file of the recovery program in the signature file of the recovery program supporting the second communication protocol in the first storage area of the external flash is written into the first storage area of the internal flash successfully or not, if yes, a step R8 is executed, and if not, a step R9 is executed;
step R8: the terminal runs the application program of the second communication protocol, whether the application program running the second communication protocol is successful is judged, if yes, the terminal works normally, and if not, the step R9 is executed;
step R9: the terminal reminds and waits for receiving a recovery signal triggered by the user, and when the terminal receives the recovery signal, the terminal returns to the step R6.
The invention also provides a device for avoiding terminal abnormity, which comprises:
the operation replacement module is used for operating an application program of a first communication protocol, receiving a recovery program signature file which is sent by an upper computer and supports a second communication protocol, storing the recovery program signature file into a communication cache region, and replacing the recovery program signature file which supports the first communication protocol in a first storage region of an external flash by using the recovery program signature file which supports the second communication protocol in the communication cache region;
the first judgment module is used for judging whether the operation replacement module uses the recovery program signature file supporting the second communication protocol in the communication cache region to replace the recovery program signature file supporting the first communication protocol in the first storage region of the external flash successfully or not, if so, the receiving and writing module is triggered, otherwise, the operation replacement module is triggered;
the receiving and writing module is used for receiving the application program executable file which is sent by the upper computer and supports the second communication protocol, storing the application program executable file into the communication cache region, and writing the application program executable file which is sent by the upper computer and supports the second communication protocol into a second storage region of the external flash;
the operation writing module is used for operating a bootstrap program and writing an application program executable file supporting a second communication protocol in a second storage area of the external flash into a first storage area of the internal flash;
the second judgment module is used for judging whether the operation writing-in module successfully writes the application program executable file supporting the second communication protocol in the second storage area of the external flash into the first storage area of the internal flash, if so, the operation judgment module is triggered, and otherwise, the writing-in module is triggered;
the writing module is used for writing a recovery program executable file in a recovery program signature file supporting a second communication protocol in a first storage area of the external flash into the first storage area of the internal flash;
the third judging module is used for judging whether the writing module successfully writes the recovery program executable file in the recovery program signature file supporting the second communication protocol in the first storage area of the external flash into the first storage area of the internal flash, if so, the operation judging module is triggered, and otherwise, the reminding receiving module is triggered;
the operation judging module is used for operating the application program of the second communication protocol, judging whether the application program of the second communication protocol is operated successfully or not, if so, the terminal works normally, otherwise, the operation judging module triggers the reminding receiving module;
and the reminding receiving module is used for reminding and waiting for receiving a recovery signal triggered by a user, and triggering the writing module when receiving the trigger signal.
The beneficial effects obtained by the invention are as follows: by adopting the technical scheme, the terminal divides the original boot loader into the boot program and the recovery program signature file, updates the recovery program signature file when the communication protocol is changed, can remind and wait for receiving a recovery signal triggered by a user after the terminal fails to operate the application program of the second communication protocol, writes the recovery program executable file in the recovery program signature file supporting the second communication protocol in the first storage area of the external flash into the first storage area of the internal flash after the terminal receives the recovery signal, and operates the application program of the second communication protocol after the terminal successfully writes and judges whether the operation is successful or not until the terminal normally works after the operation is successful; the situation that the terminal cannot be recovered due to the fact that the bootstrap program is lost in the process of recovering the signature file of the program is avoided, the process of returning to the factory for maintenance is omitted, cost is saved, and the terminal is convenient to use.
Drawings
Fig. 1 is a flowchart of a method for avoiding terminal anomaly according to an embodiment of the present invention;
fig. 2 is a flowchart of a method for avoiding terminal anomaly according to a second embodiment of the present invention;
FIG. 3 is a flowchart of a detailed process of step 103 in the second embodiment of the present invention;
FIG. 4 is a flowchart of a detailed process of step 114 in the second embodiment of the present invention;
FIG. 5 is a flowchart of a detailed process of step 116 in the second embodiment of the present invention;
FIG. 6 is a flowchart illustrating the execution of an application program according to a second embodiment of the present invention;
FIG. 7 is a flowchart illustrating execution of recovering a signature file according to a second embodiment;
FIG. 8 is a flowchart illustrating the execution of a bootstrap program according to a second embodiment of the present invention;
fig. 9 is a block diagram of an apparatus for avoiding terminal abnormality according to the third embodiment.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
An embodiment of the present invention provides a method for avoiding terminal abnormality, as shown in fig. 1, including:
step R1: the terminal runs an application program of a first communication protocol, receives a recovery program signature file which is sent by an upper computer and supports a second communication protocol, stores the recovery program signature file in a communication cache region, and replaces the recovery program signature file which supports the first communication protocol in a first storage region of an external flash by using the recovery program signature file which supports the second communication protocol in the communication cache region;
in this embodiment, step R1 further includes:
step R01: the terminal receives the file data packet and stores the file data in the file data packet to a communication cache region;
step R02: the terminal judges whether the file data in the communication buffer area is complete or not according to the length of the file data, if so, the step R03 is executed, otherwise, the step R01 is returned;
step R03: the terminal judges whether the file data in the communication buffer area is legal or not, if so, the step R04 is executed, otherwise, the operation is finished;
step R04: the terminal determines the file type in the received file package, and performs step R1 if the file is a recovery signature file, or performs step R3 if the file is an application executable file.
In this embodiment, step R03 specifically includes:
the terminal performs hash operation on the file data in the communication cache area to obtain a fifth hash value, decrypts the signature value in the file data packet by using the public key of the stored CA certificate (certificate Authority certificate) to obtain a sixth hash value, and determines whether the fifth hash value and the sixth hash value are equal, if so, step S04 is executed, otherwise, the process is ended.
In this embodiment, the step R1 of replacing the recovery program signature file supporting the first communication protocol in the first storage area of the external flash by the recovery program signature file supporting the second communication protocol in the communication cache area specifically includes:
step A1: the terminal judges whether the signature file of the recovery program supporting the second communication protocol in the communication cache area is legal or not, if so, the step A2 is executed, otherwise, an error is reported;
step A2: the terminal judges whether a recovery program signature file supporting a first communication protocol in a first storage area of the external flash is legal or not, if so, the step A3 is executed, otherwise, an error is reported;
specifically, the sequence of step a1 and step a2 may be exchanged, and the sequence may be determined by first determining whether the signature file of the recovery program supporting the second communication protocol in the communication cache region is legal, then determining whether the signature file of the recovery program supporting the first communication protocol in the first storage region of the external flash is legal, or first determining whether the signature file of the recovery program supporting the first communication protocol in the first storage region of the external flash is legal, and then determining whether the signature file of the recovery program supporting the second communication protocol in the communication cache region is legal;
step A3: the terminal erases a first storage area of the external flash;
step A4: and the terminal writes the recovery program signature file supporting the second communication protocol in the communication cache area into a first storage area of the external flash.
Step R2: the terminal judges whether the recovery program signature file supporting the second communication protocol in the communication cache area replaces the recovery program signature file supporting the first communication protocol in the first storage area of the external flash successfully, if so, the step R3 is executed, otherwise, the step R1 is returned;
step R3: the terminal receives an application program executable file supporting the second communication protocol and sent by the upper computer, stores the application program executable file in the communication cache region, and writes the application program executable file supporting the second communication protocol in the communication cache region into a second storage region of the external flash;
in this embodiment, step R3 further includes: the terminal sets the first flag bit.
Step R4: the terminal runs a bootstrap program and writes an application program executable file supporting a second communication protocol in a second storage area of the external flash into a first storage area of the internal flash;
in this embodiment, step R4 specifically includes:
step C1: the terminal erases a first storage area of the internal flash;
step C2: and the terminal writes the application program executable file supporting the second communication protocol in the second storage area of the external flash into the first storage area of the internal flash.
Step R5: the terminal judges whether the application program executable file supporting the second communication protocol in the second storage area of the external flash is successfully written into the first storage area of the internal flash, if so, the step R8 is executed, otherwise, the step R6 is executed;
step R6: the terminal writes a recovery program executable file in a recovery program signature file supporting a second communication protocol in a first storage area of the external flash into a first storage area of the internal flash;
in this embodiment, step R6 specifically includes:
step E1: the terminal judges whether a recovery program signature file supporting the second communication protocol in the first storage area of the external flash is legal or not, if so, the step E2 is executed, otherwise, an error is reported;
step E2: the terminal erases a first storage area of the internal flash;
step E3: and the terminal writes the executable file of the recovery program in the recovery program signature file supporting the second communication protocol in the first storage area of the external flash into the first storage area of the internal flash.
In this embodiment, step E1 specifically includes:
step B1: the terminal carries out Hash operation on a certificate body in a certificate of a recovery program signature file supporting a second communication protocol in a first storage area of the external flash to obtain a first Hash value, and decrypts a signature value in the certificate of the recovery program signature file supporting the second communication protocol in the first storage area of the external flash by using a public key in a stored CA (certificate authority) certificate to obtain a second Hash value;
step B2: the terminal judges whether the first hash value and the second hash value are equal, if so, the step B3 is executed, otherwise, an error is reported;
step B3: the terminal carries out Hash operation on a header field of a recovery program signature file supporting a second communication protocol and a recovery program executable file of a first storage area of the external flash to obtain a third Hash value, and decrypts a signature value in the recovery program signature file by using a public key in a certificate of the recovery program signature file supporting the second communication protocol of the first storage area of the external flash to obtain a fourth Hash value;
step B4: and E2 is executed if the terminal judges whether the third hash value and the fourth hash value are equal, if so, the recovery program signature file supporting the second communication protocol in the first storage area of the external flash is legal, and otherwise, an error is reported.
Step R7: the terminal judges whether the executable file of the recovery program in the signature file of the recovery program supporting the second communication protocol in the first storage area of the external flash is successfully written into the first storage area of the internal flash, if so, the step R8 is executed, otherwise, the step R9 is executed;
step R8: the terminal runs the application program of the second communication protocol, judges whether the application program running the second communication protocol succeeds or not, if so, the terminal works normally, otherwise, the step R9 is executed;
step R9: the terminal reminds and waits for receiving a recovery signal triggered by the user, and returns to the step R6 when the terminal receives the recovery signal.
Specifically, the recovery signal is generated by a user through key triggering.
Example two
An embodiment of the present invention provides a method for avoiding terminal abnormality, as shown in fig. 2, including:
step 101: the terminal runs a bootstrap program;
specifically, after the terminal is started, a bootstrap program is operated, and the terminal comprises terminal products such as a POS machine and the like;
step 102: the terminal judges whether a first recovery signal is received, if so, step 103 is executed, otherwise, step 105 is executed;
specifically, the first recovery signal is generated by a user through key triggering;
step 103: the terminal writes a recovery program executable file in a recovery program signature file in a first storage area of the external flash into a first storage area of the internal flash;
specifically, the internal flash memory space is small, the reading speed is high, the external flash memory space is large, and the reading speed is low;
specifically, a first storage area of the external flash stores a recovery program signature file;
specifically, the recovery program signature file comprises a header field, a certificate, a recovery program executable file and a signature value, wherein the recovery program executable file is placed in a code area of the application program and then is updated and recovered during running;
the recovery program executable file is a binary file which can be identified by a machine and is obtained after the code of the recovery program is compiled and linked;
specifically, a first storage area of the internal flash stores an application program;
in this embodiment, an implementation process of step 103 is shown in fig. 3, and specifically includes:
step 201: the terminal performs Hash operation on a certificate body in the certificate of the recovery program signature file to obtain a first Hash value, and decrypts the signature value in the certificate of the recovery program signature file by using a public key in a stored CA (certificate authority) certificate to obtain a second Hash value;
step 202: the terminal judges whether the first hash value and the second hash value are equal, if so, the step 204 is executed, otherwise, an error is reported;
step 203: the terminal carries out Hash operation on the header field of the recovery program signature file and the recovery program executable file to obtain a third Hash value, and decrypts the signature value in the recovery program signature file by using a public key in the certificate of the recovery program signature file to obtain a fourth Hash value;
step 204: the terminal judges whether the third hash value and the fourth hash value are equal, if so, step 207 is executed, otherwise, an error is reported;
step 205: the terminal erases a first storage area of the internal flash;
step 206: the terminal writes the executable file of the recovery program in the first storage area of the external flash into the first storage area of the internal flash;
step 104: the terminal judges whether the executable file of the recovery program in the signature file of the recovery program in the first storage area of the external flash is successfully written into the first storage area of the internal flash, if so, the step 105 is executed, otherwise, the step is finished;
specifically, the terminal judges according to a return value of a function in which a recovery program executable file in a recovery program signature file is written to a specified position, if the return value is 1, the recovery program executable file in the recovery program signature file is successfully written into a storage area of an application program in an internal flash, otherwise, the terminal fails;
step 105: the terminal judges whether an application executable file needs to be updated or not according to the first zone bit, if so, step 106 is executed, otherwise, step 108 is executed;
specifically, the application executable file is a binary file which is generated by compiling and linking a group of application programs input in a source code mode and can be stored in a flash;
in step 105, the terminal judges whether an application executable file is updated or not according to the state of a first flag bit (flag), if the flag is 0, the application executable file does not need to be updated, and if the flag is 1, the application executable file needs to be updated;
step 106: the terminal updates the executable file of the application program;
in this embodiment, the implementation process of updating the application executable file in step 106 specifically includes:
step 301: the terminal erases a first storage area of the internal flash;
step 302: the terminal writes the application program executable file of the second storage area of the external flash into the first storage area of the internal flash;
specifically, the second storage area of the external flash is a temporary storage area of the application executable file;
step 107: the terminal judges whether the updating of the executable file of the application program is successful, if so, the step 108 is executed, otherwise, the process is ended;
step 108: the terminal judges whether the self-checking of the application program is abnormal, if so, step 109 is executed, otherwise, step 112 is executed;
step 109: the terminal judges whether a second recovery signal is received, if so, the step 110 is executed, otherwise, the process is finished;
specifically, the terminal continues to wait for the second recovery signal after judging that the application program is abnormal; the recovery signals in the embodiment are all generated by user triggering;
step 110: the terminal writes a recovery program executable file in a recovery program signature file in a first storage area of the external flash into a first storage area of the internal flash;
step 111: the terminal judges whether the executable file of the recovery program in the signature file of the recovery program in the first storage area of the external flash is successfully written into the first storage area of the internal flash, if so, the step 112 is executed, otherwise, the step is ended;
specifically, the terminal judges according to a return value of a function in which a recovery program executable file in the recovery program signature file is written to a specified position, and if the return value is 1, the recovery program executable file in the recovery program signature file is successfully written into a storage area of an application program in an internal flash;
step 112: the terminal runs an application program;
step 113: the terminal judges whether a new application executable file or a recovery program signature file sent by the upper computer waits for receiving, if so, the step 114 is executed, otherwise, the step 119 is executed;
step 114: the terminal receives and stores a new application executable file or a recovery program signature file;
in this embodiment, the implementation process of step 114 is shown in fig. 4, and specifically includes:
step 501: a terminal receives a file data packet;
specifically, the file data packet includes a file type, a total file length, and file data;
step 502: the terminal stores the file data in the file data packet to a communication cache region;
step 503: the terminal judges whether the file data in the communication buffer area is complete, if so, step 504 is executed, otherwise, step 501 is returned;
specifically, if the terminal judges that the length of the file data in the communication cache area is consistent with the total length of the received file, the file data received and stored by the terminal is complete, otherwise, the file data is incomplete;
step 504: the terminal performs hash operation on the file data in the communication cache region to obtain a fifth hash value, and decrypts the signature value in the file data packet by using the public key of the stored CA certificate to obtain a sixth hash value;
step 505: the terminal judges whether the fifth hash value and the sixth hash value are equal, if so, the file is successfully stored, and otherwise, an error is reported;
step 115: the terminal judges the file type in the received file data packet, if the file is a recovery program signature file, step 116 is executed, and if the file is an application program executable file, step 117 is executed;
specifically, step 115 determines according to the identifier of the saved file type, where the identifier of the file type is 1, and if the identifier of the file type is 0, the file is a signature file of the recovery program, and if the identifier of the file type is 0, the file is an executable file of the application program;
step 116: the terminal uses the recovery program signature file of the communication buffer area to replace the recovery program signature file of the first storage area of the external flash, and executes step 119;
in this embodiment, the implementation process of step 116 is shown in fig. 5, and specifically includes:
step 601: the terminal judges whether the recovery program signature file of the communication buffer area is legal or not, if so, step 602 is executed, otherwise, an error is reported;
step 602: the terminal judges whether the signature file of the recovery program of the first storage area of the external flash is legal or not, if so, the step 603 is executed, otherwise, an error is reported;
specifically, the sequence of step 601 and step 602 may be changed, and the sequence may be changed, so that whether the recovery program signature file of the first storage area of the external flash is legal or not may be judged first, and whether the recovery program signature file of the first storage area of the external flash is legal or not may also be judged first when the recovery program signature file of the first storage area of the external flash is legal or not;
step 603: the terminal erases a first storage area of the external flash;
step 604: the terminal writes the recovery program signature file of the communication cache area into a first storage area of an external flash;
step 117: the terminal writes the application program executable file of the communication cache area into a second storage area of the external flash, and sets the first flag bit;
specifically, in step 117, the terminal sets a first flag bit, for example, flag is 1;
step 118: the terminal is shut down and restarted, and step 101 is executed;
step 119: the terminal starts normal operation and then performs step 113.
An execution flowchart of an application program in the second embodiment of the present invention is shown in fig. 6, and includes:
step 801: the terminal runs an application program;
step 802: the terminal judges whether a new application executable file or a recovery program signature file sent by the upper computer waits for receiving, if so, the step 803 is executed, otherwise, other functions are executed;
specifically, the other functions are configuration file downloading and analysis, transaction processing, log storage or log uploading;
step 803: the terminal receives and stores a new application program executable file or a recovery program signature file, judges whether the received file is the recovery program signature file, if so, the terminal replaces the recovery program signature file of the first storage area of the external flash by the recovery program signature file of the communication cache area to execute other functions, otherwise, the terminal writes the application program executable file of the communication cache area into the second storage area of the external flash, sets the first flag bit, and restarts the terminal when the terminal is shut down.
Fig. 7 shows an execution flowchart of recovering a program signature file in the second embodiment of the present invention, which includes:
step 901: the terminal runs a recovery program;
step 902: the terminal judges whether a new application executable file or a recovery program signature file sent by the upper computer waits for receiving, if so, step 903 is executed, otherwise, the judgment operation is continued;
step 903: the terminal receives and stores a new application program executable file or a recovery program signature file, judges whether the received file is the recovery program signature file, if so, the terminal replaces the recovery program signature file of the first storage area of the external flash with the recovery program signature file of the communication cache area, otherwise, the terminal writes the application program executable file of the communication cache area into the second storage area of the external flash, sets the first flag bit, and restarts the terminal when the terminal is shut down.
The execution flow chart of the bootstrap program in the second embodiment of the present invention is shown in fig. 8, and includes:
step 1001: the terminal runs a bootstrap program;
step 1002: the terminal judges whether a recovery signal is received, if so, step 1003 is executed, otherwise, step 1005 is executed;
step 1003: the terminal writes a recovery program executable file in a recovery program signature file in a first storage area of the external flash into a first storage area of the internal flash;
step 1004: the terminal judges whether the executable file of the recovery program in the signature file of the recovery program in the first storage area of the external flash is successfully written into the first storage area of the internal flash, if so, the step 1005 is executed, otherwise, the process is ended;
step 1005: the terminal judges whether an application executable file needs to be updated according to the first flag bit, if so, step 1006 is executed, otherwise, step 1008 is executed;
step 1006: the terminal updates the executable file of the application program;
step 1007: the terminal judges whether the updating of the application executable file is successful, if so, the step 1008 is executed, otherwise, the step 1009 is executed;
step 1008: the terminal runs an application program;
step 1009: the terminal writes a recovery program executable file in a recovery program signature file in a first storage area of the external flash into a first storage area of the internal flash;
step 1010: and the terminal judges whether the executable file of the recovery program in the signature file of the recovery program in the first storage area of the external flash is successfully written into the first storage area of the internal flash, if so, the step 1008 is executed, otherwise, the process is ended.
EXAMPLE III
An embodiment of the present invention provides a device for avoiding terminal abnormality, as shown in fig. 9, including:
the operation replacement module 11 is used for operating an application program of a first communication protocol, receiving a recovery program signature file supporting a second communication protocol and sent by an upper computer, storing the recovery program signature file in a communication cache region, and replacing the recovery program signature file supporting the first communication protocol in a first storage region of an external flash by using the recovery program signature file supporting the second communication protocol in the communication cache region;
the first judging module 12 is configured to judge whether the operation replacement module 11 succeeds in replacing the recovery program signature file supporting the first communication protocol in the first storage area of the external flash with the recovery program signature file supporting the second communication protocol in the communication cache area, if yes, the receiving and writing module 13 is triggered, and if not, the operation replacement module 11 is triggered;
the receiving and writing module 13 is configured to receive the application executable file supporting the second communication protocol and sent by the upper computer, store the application executable file supporting the second communication protocol in the communication cache area, and write the application executable file supporting the second communication protocol in the communication cache area into a second storage area of the external flash;
the operation writing module 14 is configured to run a bootstrap program, and write an application executable file supporting a second communication protocol in a second storage area of the external flash into a first storage area of the internal flash;
the second judging module 15 is configured to judge whether the operation writing module 14 successfully writes the application executable file supporting the second communication protocol in the second storage area of the external flash into the first storage area of the internal flash, if so, the operation judging module 18 is triggered, and if not, the writing module 16 is triggered;
the writing module 16 is configured to write a recovery program executable file in a recovery program signature file supporting the second communication protocol in the first storage area of the external flash into the first storage area of the internal flash;
a third judging module 17, configured to judge whether the writing module 16 successfully writes the recovery program executable file in the recovery program signature file supporting the second communication protocol in the first storage area of the external flash into the first storage area of the internal flash, if so, trigger the operation judging module 18, otherwise trigger the reminder receiving module 19;
the operation judging module 18 is used for operating the application program of the second communication protocol, judging whether the application program of the second communication protocol is operated successfully or not, if so, the terminal works normally, otherwise, the reminding receiving module 19 is triggered;
and the reminding receiving module 19 is used for waiting for a recovery signal triggered by the user, and triggering the writing module 16 when the terminal receives the trigger signal.
Optionally, in this embodiment, the method further includes:
the receiving module is used for receiving the file data packet and storing the file data in the file data packet to the communication cache region;
the fourth judging module is used for judging whether the file data in the communication cache region is complete or not according to the length of the file data, if so, the fifth judging module is triggered, and otherwise, the receiving module is triggered;
the fifth judging module is used for judging whether the file data in the communication cache area is legal or not, if so, the sixth judging module is triggered, and if not, the operation is ended;
and the sixth judging module is used for judging the file type in the received file data packet, triggering the operation replacement module if the file is a recovery program signature file, and triggering the receiving write-in module if the file is an application program executable file.
Optionally, in this embodiment, the fifth determining module includes:
the first operation submodule is used for carrying out hash operation on the file data in the communication cache region by the terminal to obtain a fifth hash value;
the first decryption submodule is used for decrypting the signature value in the file data packet by using the stored public key of the CA certificate to obtain a sixth hash value;
and the first judgment submodule is used for judging whether the fifth hash value and the sixth hash value are equal, if so, the sixth judgment module is triggered, and if not, the judgment is finished.
Optionally, in this embodiment, the operation replacement module 11 specifically includes:
the first operation submodule is used for operating an application program of a first communication protocol;
the second judgment submodule is used for judging whether the signature file of the recovery program supporting the second communication protocol in the communication cache area is legal or not, if so, the third judgment submodule is triggered, and otherwise, an error is reported;
the third judgment submodule is used for judging whether a recovery program signature file supporting the first communication protocol in the first storage area of the external flash is legal or not, if so, the first erasing submodule is triggered, and otherwise, an error is reported;
the first erasing submodule is used for erasing a first storage area of the external flash;
and the first writing submodule is used for writing the recovery program signature file of the communication cache region, which supports the second communication protocol, into a first storage region of the external flash.
Optionally, in this embodiment, the operating and writing module 14 specifically includes:
the second operation submodule is used for operating the bootstrap program;
the second erasing submodule is used for erasing the first storage area of the internal flash;
and the second writing submodule is used for writing the application program executable file supporting the second communication protocol in the second storage area of the external flash into the first storage area of the internal flash.
Optionally, in this embodiment, the writing module 16 includes:
the fourth judgment submodule is used for judging whether a recovery program signature file supporting the second communication protocol in the first storage area of the external flash is legal or not, if so, the third erasing submodule is triggered, and otherwise, an error is reported;
the third erasing submodule is used for erasing the first storage area of the internal flash;
and the third writing submodule is used for writing the executable file of the recovery program in the recovery program signature file supporting the second communication protocol in the first storage area of the external flash into the first storage area of the internal flash.
Optionally, in this implementation, the fourth determining sub-module specifically includes:
the first operation unit is used for carrying out Hash operation on a certificate body in a certificate of a recovery program signature file supporting a second communication protocol in a first storage area of the external flash to obtain a first Hash value;
the first decryption unit is used for decrypting a signature value in a certificate of a recovery program signature file supporting a second communication protocol in a first storage area of the external flash by using a public key in a stored certificate authority certificate to obtain a second hash value;
the first judgment unit is used for judging whether the first hash value and the second hash value are equal, if so, the second operation unit is triggered, and otherwise, an error is reported;
the second operation unit is used for carrying out hash operation on a header field of a recovery program signature file supporting a second communication protocol and a recovery program executable file of a first storage area of the external flash to obtain a third hash value;
the second decryption unit is used for decrypting the signature value in the recovery program signature file supporting the second communication protocol in the first storage area of the external flash by using the public key in the certificate of the recovery program signature file supporting the second communication protocol in the first storage area of the external flash to obtain a fourth hash value;
and the second judging unit is used for judging whether the third hash value and the fourth hash value are equal, if so, the signature file of the recovery program supporting the second communication protocol in the first storage area of the external flash is legal, and otherwise, an error is reported.
Optionally, in this embodiment, the receiving and writing module 13 is further configured to set the first flag bit.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (16)
1. A method for avoiding terminal abnormity is characterized by comprising the following steps:
step R1: the terminal runs an application program of a first communication protocol, receives a recovery program signature file which is sent by an upper computer and supports a second communication protocol, stores the recovery program signature file in a communication cache region, and replaces the recovery program signature file which supports the first communication protocol in a first storage region of an external flash by using the recovery program signature file which supports the second communication protocol in the communication cache region;
step R2: the terminal judges whether the recovery program signature file supporting the second communication protocol of the communication cache area replaces the recovery program signature file supporting the first communication protocol of the first storage area of the external flash successfully, if so, the step R3 is executed, otherwise, the step R1 is returned;
step R3: the terminal receives the application program executable file supporting the second communication protocol and sent by the upper computer, stores the application program executable file supporting the second communication protocol in the communication cache area, and writes the application program executable file supporting the second communication protocol in the communication cache area into a second storage area of the external flash;
step R4: the terminal runs a bootstrap program and writes an application program executable file supporting a second communication protocol in a second storage area of the external flash into a first storage area of the internal flash;
step R5: the terminal judges whether the application program executable file supporting the second communication protocol in the second storage area of the external flash is successfully written into the first storage area of the internal flash, if so, a step R8 is executed, otherwise, a step R6 is executed;
step R6: the terminal writes a recovery program executable file in a recovery program signature file supporting a second communication protocol in a first storage area of the external flash into a first storage area of the internal flash;
step R7: the terminal judges whether the executable file of the recovery program in the signature file of the recovery program supporting the second communication protocol in the first storage area of the external flash is written into the first storage area of the internal flash successfully or not, if yes, a step R8 is executed, and if not, a step R9 is executed;
step R8: the terminal runs the application program of the second communication protocol, whether the application program running the second communication protocol is successful is judged, if yes, the terminal works normally, and if not, the step R9 is executed;
step R9: the terminal reminds and waits for receiving a recovery signal triggered by the user, and when the terminal receives the recovery signal, the terminal returns to the step R6.
2. The method of claim 1, wherein said step R1 is preceded by the further step of:
step R01: the terminal receives a file data packet and stores file data in the file data packet to the communication cache region;
step R02: the terminal judges whether the file data in the communication cache region are complete or not according to the length of the file data, if so, the step R03 is executed, otherwise, the step R01 is returned;
step R03: the terminal judges whether the file data in the communication cache area is legal or not, if so, the step R04 is executed, otherwise, the operation is finished;
step R04: the terminal determines the file type in the received file data package, and performs step R1 if the file is a recovery program signature file, or performs step R3 if the file is an application program executable file.
3. The method according to claim 2, wherein said step R03 is in particular:
and the terminal performs hash operation on the file data in the communication cache region to obtain a fifth hash value, decrypts the signature value in the file data packet by using the public key of the stored certificate authority certificate to obtain a sixth hash value, judges whether the fifth hash value and the sixth hash value are equal, if so, executes the step R04, and otherwise, ends.
4. The method according to claim 1, wherein the step R1 of replacing the recovery program signature file supporting the first communication protocol in the first storage area of the external flash with the recovery program signature file supporting the second communication protocol in the communication buffer area specifically includes:
step A1: the terminal judges whether the signature file of the recovery program supporting the second communication protocol in the communication cache area is legal or not, if so, the step A2 is executed, otherwise, an error is reported;
step A2: the terminal judges whether a recovery program signature file supporting a first communication protocol in a first storage area of the external flash is legal or not, if so, the step A3 is executed, otherwise, an error is reported;
step A3: the terminal erases a first storage area of the external flash;
step A4: and the terminal writes the recovery program signature file supporting the second communication protocol in the communication cache area into a first storage area of the external flash.
5. The method according to claim 1, wherein the step R4 of writing the application executable file supporting the second communication protocol in the second storage area of the external flash to the first storage area of the internal flash specifically comprises:
step C1: the terminal erases a first storage area of the internal flash;
step C2: and the terminal writes the application program executable file supporting the second communication protocol in the second storage area of the external flash into the first storage area of the internal flash.
6. The method according to claim 1, wherein said step R6 specifically comprises:
step E1: the terminal judges whether a recovery program signature file supporting the second communication protocol in the first storage area of the external flash is legal or not, if so, the step E2 is executed, otherwise, an error is reported;
step E2: the terminal erases a first storage area of the internal flash;
step E3: and the terminal writes the executable file of the recovery program in the signature file of the recovery program supporting the second communication protocol in the first storage area of the external flash into the first storage area of the internal flash.
7. The method according to claim 6, wherein the step E1 specifically comprises:
step B1: the terminal carries out Hash operation on a certificate body in a certificate of a recovery program signature file supporting a second communication protocol in a first storage area of the external flash to obtain a first Hash value, and decrypts a signature value in the certificate of the recovery program signature file supporting the second communication protocol in the first storage area of the external flash by using a public key in a stored certificate authority certificate to obtain a second Hash value;
step B2: the terminal judges whether the first hash value and the second hash value are equal, if so, the step B3 is executed, otherwise, an error is reported;
step B3: the terminal carries out Hash operation on a header field of a recovery program signature file supporting a second communication protocol in a first storage area of the external flash and a recovery program executable file to obtain a third Hash value, and decrypts a signature value in the recovery program signature file supporting the second communication protocol in the first storage area of the external flash by using a public key in a certificate of the recovery program signature file supporting the second communication protocol in the first storage area of the external flash to obtain a fourth Hash value;
step B4: and the terminal judges whether the third hash value and the fourth hash value are equal, if so, the signature file of the recovery program supporting the second communication protocol in the first storage area of the external flash is legal, and otherwise, an error is reported.
8. The method of claim 1, wherein said step R3 further comprises: and the terminal sets the first flag bit.
9. An apparatus for avoiding abnormality of a terminal, comprising:
the operation replacement module is used for operating an application program of a first communication protocol, receiving a recovery program signature file which is sent by an upper computer and supports a second communication protocol, storing the recovery program signature file into a communication cache region, and replacing the recovery program signature file which supports the first communication protocol in a first storage region of an external flash by using the recovery program signature file which supports the second communication protocol in the communication cache region;
the first judgment module is used for judging whether the operation replacement module uses the recovery program signature file supporting the second communication protocol in the communication cache region to replace the recovery program signature file supporting the first communication protocol in the first storage region of the external flash successfully or not, if so, the receiving and writing module is triggered, otherwise, the operation replacement module is triggered;
the receiving and writing module is used for receiving the application program executable file which is sent by the upper computer and supports the second communication protocol, storing the application program executable file into the communication cache region, and writing the application program executable file which is sent by the upper computer and supports the second communication protocol into a second storage region of the external flash;
the operation writing module is used for operating a bootstrap program and writing an application program executable file supporting a second communication protocol in a second storage area of the external flash into a first storage area of the internal flash;
the second judgment module is used for judging whether the operation writing-in module successfully writes the application program executable file supporting the second communication protocol in the second storage area of the external flash into the first storage area of the internal flash, if so, the operation judgment module is triggered, and otherwise, the writing-in module is triggered;
the writing module is used for writing a recovery program executable file in a recovery program signature file supporting a second communication protocol in a first storage area of the external flash into the first storage area of the internal flash;
the third judging module is used for judging whether the writing module successfully writes the recovery program executable file in the recovery program signature file supporting the second communication protocol in the first storage area of the external flash into the first storage area of the internal flash, if so, the operation judging module is triggered, and otherwise, the reminding receiving module is triggered;
the operation judging module is used for operating the application program of the second communication protocol, judging whether the application program of the second communication protocol is operated successfully or not, if so, the terminal works normally, otherwise, the operation judging module triggers the reminding receiving module;
and the reminding receiving module is used for reminding and waiting for receiving a recovery signal triggered by a user, and triggering the writing module when receiving the trigger signal.
10. The apparatus of claim 9, further comprising:
the receiving module is used for receiving a file data packet and storing file data in the file data packet to the communication cache region;
the fourth judging module is used for judging whether the file data in the communication cache region is complete or not according to the length of the file data, if so, the fifth judging module is triggered, and otherwise, the receiving module is triggered;
the fifth judging module is used for judging whether the file data in the communication cache area is legal or not, if so, the sixth judging module is triggered, and if not, the operation is finished;
the sixth judging module is configured to judge a file type in the received file data packet, trigger the operation replacement module if the file type is a recovery program signature file, and trigger the receiving write-in module if the file type is an application program executable file.
11. The apparatus as claimed in claim 10, wherein said fifth determining module comprises:
the first operation sub-module is used for carrying out hash operation on the file data in the communication cache region to obtain a fifth hash value;
the first decryption submodule is used for decrypting the signature value in the file data packet by using the stored public key of the certificate authority certificate to obtain a sixth hash value;
and the first judgment submodule is used for judging whether the fifth hash value and the sixth hash value are equal, if so, the sixth judgment module is triggered, and if not, the operation is ended.
12. The apparatus of claim 9, wherein the run replacement module specifically comprises:
the first operation submodule is used for operating an application program of a first communication protocol;
the second judgment submodule is used for judging whether the signature file of the recovery program supporting the second communication protocol in the communication cache area is legal or not, if so, the third judgment submodule is triggered, and otherwise, an error is reported;
the third judging submodule is used for judging whether a recovery program signature file supporting the first communication protocol in the first storage area of the external flash is legal or not, if so, the first erasing submodule is triggered, and otherwise, an error is reported;
the first erasing submodule is used for erasing a first storage area of the external flash;
and the first writing submodule is used for writing the recovery program signature file of the communication cache region, which supports the second communication protocol, into a first storage region of an external flash.
13. The apparatus of claim 9, wherein the run write module specifically comprises:
the second operation submodule is used for operating the bootstrap program;
the second erasing submodule is used for erasing the first storage area of the internal flash;
and the second writing submodule is used for writing the application program executable file supporting the second communication protocol in the second storage area of the external flash into the first storage area of the internal flash.
14. The apparatus of claim 9, wherein the write module comprises:
the fourth judgment submodule is used for judging whether a recovery program signature file supporting the second communication protocol in the first storage area of the external flash is legal or not, if so, the third erasing submodule is triggered, and otherwise, an error is reported;
the third erasing submodule is used for erasing the first storage area of the internal flash;
and the third writing submodule is used for writing the executable file of the recovery program in the signature file of the recovery program supporting the second communication protocol in the first storage area of the external flash into the first storage area of the internal flash.
15. The apparatus of claim 14, wherein the fourth determining sub-module specifically comprises:
the first operation unit is used for carrying out Hash operation on a certificate body in a certificate of a recovery program signature file supporting a second communication protocol in a first storage area of the external flash to obtain a first Hash value;
the first decryption unit is used for decrypting a signature value in a certificate of a recovery program signature file supporting a second communication protocol in a first storage area of the external flash by using a public key in a stored certificate authority certificate to obtain a second hash value;
the first judgment unit is used for judging whether the first hash value and the second hash value are equal, if so, the second operation unit is triggered, and otherwise, an error is reported;
the second operation unit is used for performing hash operation on a header field of a recovery program signature file supporting a second communication protocol and a recovery program executable file of a first storage area of the external flash to obtain a third hash value;
the second decryption unit is used for decrypting the signature value in the recovery program signature file supporting the second communication protocol in the first storage area of the external flash by using the public key in the certificate of the recovery program signature file supporting the second communication protocol in the first storage area of the external flash to obtain a fourth hash value;
and the second judging unit is used for judging whether the third hash value and the fourth hash value are equal, if so, the recovery program signature file supporting the second communication protocol in the first storage area of the external flash is legal, and otherwise, an error is reported.
16. The apparatus of claim 9, wherein the receive write module is further configured to set a first flag bit.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911117101.6A CN110879765B (en) | 2019-11-15 | 2019-11-15 | Method and device for avoiding terminal abnormity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911117101.6A CN110879765B (en) | 2019-11-15 | 2019-11-15 | Method and device for avoiding terminal abnormity |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110879765A true CN110879765A (en) | 2020-03-13 |
| CN110879765B CN110879765B (en) | 2022-01-14 |
Family
ID=69729903
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911117101.6A Active CN110879765B (en) | 2019-11-15 | 2019-11-15 | Method and device for avoiding terminal abnormity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110879765B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859162A (en) * | 2005-06-15 | 2006-11-08 | 华为技术有限公司 | Realizing method and system for automatic restoring equipment fault |
| CN102681915A (en) * | 2011-01-17 | 2012-09-19 | 三星电子株式会社 | Computer system and program restoring method thereof |
| CN104077196A (en) * | 2014-07-02 | 2014-10-01 | 浪潮(北京)电子信息产业有限公司 | Linux boot failure recovering method and device |
| CN104090796A (en) * | 2014-07-08 | 2014-10-08 | 成都万维图新信息技术有限公司 | Embedded device program updating method and system |
| CN104572206A (en) * | 2015-01-14 | 2015-04-29 | 厦门为那通信科技有限公司 | Application program self updating and backup recovery method |
| CN108111265A (en) * | 2016-11-25 | 2018-06-01 | 株洲中车时代电气股份有限公司 | A kind of unification of communication protocol automated testing method |
| US20180349228A1 (en) * | 2017-06-06 | 2018-12-06 | BSD Research LLC | Devices and methods for recovering data from computers |
-
2019
- 2019-11-15 CN CN201911117101.6A patent/CN110879765B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859162A (en) * | 2005-06-15 | 2006-11-08 | 华为技术有限公司 | Realizing method and system for automatic restoring equipment fault |
| CN102681915A (en) * | 2011-01-17 | 2012-09-19 | 三星电子株式会社 | Computer system and program restoring method thereof |
| CN104077196A (en) * | 2014-07-02 | 2014-10-01 | 浪潮(北京)电子信息产业有限公司 | Linux boot failure recovering method and device |
| CN104090796A (en) * | 2014-07-08 | 2014-10-08 | 成都万维图新信息技术有限公司 | Embedded device program updating method and system |
| CN104572206A (en) * | 2015-01-14 | 2015-04-29 | 厦门为那通信科技有限公司 | Application program self updating and backup recovery method |
| CN108111265A (en) * | 2016-11-25 | 2018-06-01 | 株洲中车时代电气股份有限公司 | A kind of unification of communication protocol automated testing method |
| US20180349228A1 (en) * | 2017-06-06 | 2018-12-06 | BSD Research LLC | Devices and methods for recovering data from computers |
Non-Patent Citations (1)
| Title |
|---|
| 方冲，任海兰，王成丽: "基于MCU的嵌入式在线升级系统的设计与实现", 《电视技术》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110879765B (en) | 2022-01-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8612722B2 (en) | Determining an end of valid log in a log of write records | |
| US7512749B2 (en) | Safe software revision for embedded systems | |
| EP1738256B1 (en) | Method and apparatus for reliably updating a stored version of content | |
| JP5575338B2 (en) | Information processing apparatus, information processing method, and computer program | |
| JP6585072B2 (en) | Safe reading of data into non-volatile memory or secure elements | |
| US20110004871A1 (en) | Embedded electronic device and firmware updating method thereof | |
| CN110333891A (en) | The method of enhanced OTA upgrading based on Internet of Things | |
| CN107783776B (en) | Processing method and device of firmware upgrade package and electronic equipment | |
| CN104090790A (en) | Two-chip scheme firmware updating method for safety terminal | |
| US9710340B2 (en) | Replacement of a corrupt driver variable record | |
| US20160170735A1 (en) | Operating system updating method by using a checklist | |
| JP5167936B2 (en) | Information processing device | |
| WO2018049798A1 (en) | Method and apparatus for reconstructing cache partition | |
| CN110879765B (en) | Method and device for avoiding terminal abnormity | |
| JP2022142263A (en) | Information processing apparatus and information processing program | |
| CN112416527A (en) | Data recovery method, device, equipment and storage medium | |
| KR101085681B1 (en) | System and method for recovering data in mobile terminal | |
| CN106843892A (en) | A kind of method and device of rewriting Flash | |
| CN110427203B (en) | SIM card, updating method of SIM card and updating method of SIM card operating system | |
| JP2014099097A (en) | Information processing device, information processing method, and computer program | |
| CN112311552A (en) | Electronic device with firmware and method of operating the same | |
| JP2010079382A (en) | Software update method | |
| JP2021114173A (en) | Information processing apparatus, processing method thereof, and program | |
| KR100628176B1 (en) | Method for upgrading program stored in information terminal | |
| KR100575927B1 (en) | Method for booting the nand flash memory using multi boot loader in mobile station |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 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 |