CN102222027A - Method and device for restoring factory settings of terminal - Google Patents
Method and device for restoring factory settings of terminal Download PDFInfo
- Publication number
- CN102222027A CN102222027A CN2011101656118A CN201110165611A CN102222027A CN 102222027 A CN102222027 A CN 102222027A CN 2011101656118 A CN2011101656118 A CN 2011101656118A CN 201110165611 A CN201110165611 A CN 201110165611A CN 102222027 A CN102222027 A CN 102222027A
- Authority
- CN
- China
- Prior art keywords
- java
- configuration file
- byte
- file
- bit group
- 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
Abstract
The invention discloses a method and a device for restoring factory settings of a terminal. The method comprises the following steps of: generating and storing a configuration file comprising JAVA application remove information; deleting install files of corresponding JAVA applications and all RMS (Record Management System) data according to a configuration file when a user chooses to restore the factory setting of JAVA; and judging whether a changeable JAVA configuration file exists according to the configuration file, if so, restoring the changeable JAVA configuration file to the factory settings. By means of the technical schemes provided by the invention, the JAVA application can be specially restored to the factory settings, and the JAVA application can be ensured to work stably and normally.
Description
Technical field
The present invention relates to field of mobile communication, particularly relate to a kind of terminal factory reset method and device.
Background technology
In the prior art, along with the continuous development of mobile phone market, the function of mobile phone is more and more, the function that JAVA generally supports as a kind of mobile phone, being applied in qualitatively and very big lifting quantitatively all arranged of support.Popularizing of mobile phone terminal, making JAVA use can cross-platform cross manufacturer be widely used, and the market potential that JAVA uses is huge.
At present, most senior middle schools low-end mobile phone is all supported JAVA, and general middle-grade mobile phone the inside all is equipped with tens JAVA and uses, and mobile phone is when dispatching from the factory, and producer has also preset more abundant JAVA and used.Because the lifting of mobile phone EMS memory, also there has been large increase in JAVA module shared space in whole mobile phone, and this does not lay a good foundation for going downhill permanently of JAVA application.
Because the difference of cell phone system and JAVA virtual machine is different, also can there be some problems in JAVA when generally using in terminal.For example, be applied on the mobile phone B at the JAVA that can normally move on the mobile phone A and just can not normally use; Perhaps, same JAVA is applied in that having upgraded can go wrong after the version causes and can not normally use; Perhaps, because the problem of JAVA application itself causes the system failure etc.If had these faults, present disposal route is this application of deletion, but uses for unsuppressible-suppression, just can't recover.Use in user installation under the situation of too much handset capability decline, just need a kind of operation make JAVA return to former state, that makes JAVA return to Default Value exactly.
At present, whether the mobile phone terminal of supporting JAVA presets JAVA when dispatching from the factory is used, can be divided into and have JAVA to preset to use and do not have JAVA and preset and use two types, and the application that JAVA presets can be divided into deleting and uses and the unsuppressible-suppression application, and the application of presetting of Chu Xianing all is the unsuppressible application of presetting in the market.
Preset application type facing to above-mentioned multiple different JAVA, the method or the scheme that also do not occur special JAVA factory reset on the market, with the unified processing of multiple situation, and present most of factory reset all is the mobile phone factory reset, rather than JAVA factory reset, there is the defective of by mistake deleting easily in this way, and the deletion scope is excessive, uses dumb.In addition, some factory reset method is earlier original all files to be backed up, the present All Files of deletion in factory reset, and the file with backup recovers again.Though this way is feasible, need special storage space to preserve backup file, when backup file is too much, can occupy a large amount of storage spaces, it is not too easy that this implements on the mobile phone of limited storage space.
Summary of the invention
The invention provides a kind of terminal factory reset method and device, carry out the problem that Default Value recovers to solve to use JAVA specially in the prior art.
The invention provides a kind of terminal factory reset method, comprising:
Generation comprises configuration file and the preservation that JAVA uses deletion information;
When the user selects to recover the JAVA Default Value, delete installation file and all the record management system RMS data that corresponding JAVA uses according to configuration file;
Judge whether variable JAVA configuration file according to configuration file, be judged as under the situation that is, variable JAVA configuration file is returned to factory state.
The present invention also provides a kind of terminal factory reset device, comprising:
Generation module is used to generate the configuration file and the preservation that comprise JAVA application deletion information;
Removing module is used for when the user selects to recover the JAVA Default Value, deletes installation file and all the record management system RMS data that corresponding JAVA uses according to configuration file;
Recover module, be used for judging whether variable JAVA configuration file, be judged as under the situation that is, variable JAVA configuration file is returned to factory state according to configuration file.
Beneficial effect of the present invention is as follows:
When selecting the JAVA factory reset the user, recover JAVA according to the configuration file that sets in advance and be applied to Default Value, remove user data, the recovery JAVA that dispatches from the factory uses, solved to use JAVA specially in the prior art and carried out the problem that Default Value recovers, can specially JAVA be used and return to Default Value, and guarantee that JAVA uses and stablize operate as normal, the embodiment of the invention does not need to back up the JAVA application file, can conserve storage, in addition, the embodiment of the invention can be used for the JAVA virtual machine of different platform, has good versatility.
Description of drawings
Fig. 1 is the process flow diagram of the terminal factory reset method of the embodiment of the invention;
Fig. 2 is the detailed process process flow diagram of the terminal factory reset method of the embodiment of the invention;
Fig. 3 is the processing flow chart of the example one of the embodiment of the invention;
Fig. 4 is the processing flow chart of the example two of the embodiment of the invention;
Fig. 5 is the structural representation of the terminal factory reset device of the embodiment of the invention.
Embodiment
Carry out the problem that Default Value recovers in order to solve to use JAVA specially in the prior art, the invention provides a kind of terminal factory reset method and device, when using, JAVA goes wrong or user when wanting to recover JAVA to original factory state, JAVA is used (JAVA module) return to Default Value, remove user data, improve terminal capabilities, guarantee JAVA module stability operate as normal.Below in conjunction with accompanying drawing and embodiment, the present invention is further elaborated.Should be appreciated that specific embodiment described herein only in order to explain the present invention, does not limit the present invention.
Method embodiment
According to embodiments of the invention, a kind of terminal factory reset method is provided, Fig. 1 is the process flow diagram of the terminal factory reset method of the embodiment of the invention, as shown in Figure 1, comprises following processing according to the terminal factory reset method of the embodiment of the invention:
Step 101 generates the configuration file and the preservation that comprise JAVA application deletion information;
Particularly, in step 101, preferably, the data layout of configuration file is one group with 8 bits, and four bit groups are set altogether, and represents with 16 systems.In first bit group, first byte representation has or not and presets JAVA and use, and whether second byte representation presets that JAVA uses is to delete, and the 3rd byte representation presets JAVA and use whether variable JAVA configuration file is arranged, and remaining other bytes are for keeping the position; Second bit group is used for representing to preset the number of JAVA application; The 3rd bit group and the 4th bit group are used for representing that all preset the ID that JAVA uses.
Step 102 when the user selects to recover the JAVA Default Value, is deleted installation file and all the RMS data that corresponding JAVA uses according to configuration file;
Particularly, in step 102, use, then delete JAVA installation file and all the RMS data that all non-JAVA of presetting use according to first byte and second byte if preset JAVA according to first byte judgement existence of first bit group in the configuration file;
If judge that according to first byte of first bit group in the configuration file not presetting JAVA uses, and then deletes JAVA installation file and all RMS data that all JAVA use;
Preserve the JAVA installation file if determine to exist in external memory card and the described external memory card, then delete all JAVA installation files and all RMS data in the external memory card.
Step 103 judges whether variable JAVA configuration file according to configuration file, is being judged as under the situation that is, variable JAVA configuration file is returned to factory state.
Particularly, in step 103, judge whether variable JAVA configuration file, be judged as under the situation that is, variable JAVA configuration file is returned to factory state according to the 3rd byte of first bit group in the configuration file.In this step, variable JAVA configuration file is meant that the JAVA configuration file is changed after terminal is dispatched from the factory, and when terminal is installed the JAVA application in the back of dispatching from the factory, the JAVA configuration file has been carried out read-write operation that is:.
Below in conjunction with accompanying drawing, the technique scheme of the embodiment of the invention is elaborated.
Generally speaking, the memory location of JAVA in mobile phone mainly comprises two parts, and first is in the middle of the mobile phone EMS memory, and another part is in the middle of the exterior storage medium (for example, SD card etc.), to be stored in respectively in the middle of the different catalogues.Comprise generally under this catalogue that installation file, JAVA that JAVA uses use the configuration file of operation needs and record management system (the Record Management System that JAVA application operation back produces, abbreviate RMS as) data (for example, user name, password etc.).Wherein, the configuration file that the installation file that JAVA uses and most JAVA use operation to be needed is an immutable content, can not change along with the operation of JAVA module, and the RMS data that the JAVA application produces and few JAVA configuration file is variable content.The content of all new generations is deleted in so-called factory reset exactly, with the content recovery of some variations state when dispatching from the factory.
Because the terminal of supporting JAVA to use is divided into and has JAVA to preset to use and do not have JAVA and preset and use two types, the application that JAVA presets is divided into again deleting uses and the unsuppressible-suppression application, in order to identify these differences, the embodiment of the invention has designed a kind of data layout, variable configuration file has certain contiguity in this data layout and the mobile phone, be used in factory reset, differentiating, differentiate whether delete the installation file that JAVA presets application with it, and whether variable JAVA configuration file arranged, and the JAVA configuration file that will change returns to the state when dispatching from the factory.The data that this data layout comprises are kept in the middle of the mobile phone read-only memory (Read-Only Memory abbreviates ROM as) in the mode of configuration file.
This data layout is one group with the 8bit group, and promptly 4 bytes are unit, represents with 16 systems, altogether 32bit.Wherein, first group first byte representation has or not and presets application, and application is preset in 1 representative, and 0 representative does not have and presets application; Whether first group second byte representation is can delete to preset application, and 1 representative can be deleted application, and on behalf of unsuppressible-suppression, 0 use; Whether this JAVA virtual machine has variable JAVA configuration file to first group the 3rd byte representation, and on behalf of this virtual machine, 1 variable JAVA configuration file is arranged, the no variable JAVA configuration file of 0 representative, and first group remainder bytes is for keeping the position.Second group of number of representing to preset application, the 3rd group to last one group of ID that represents to preset application.Wherein, using ID is produced by the JAVA virtual machine automatically according to the erection sequence that JAVA uses.For example, the current JAVA of 01,010,100 00,000,002 00,000,001 00000002 expressions has 2 deletable presetting to use A and B, their ID is respectively 00000001 and 00000002, and A installs prior to B, simultaneously, some configuration files of JAVA are variable in the operational process of JAVA module.
When mobile phone terminal dispatches from the factory, generate the configuration file of above-mentioned data layout, and it is kept in the mobile phone.In actual applications, this configuration file can generate or other modes generate by hand.
When the user selected to recover the JAVA Default Value, content deletion corresponding JAVA installation file and RMS data according to this configuration file judged whether variable JAVA configuration file then, if having, then return to factory state.
Fig. 2 is the detailed process process flow diagram of the terminal factory reset method of the embodiment of the invention, as shown in Figure 2, comprises following processing:
Step 201, the configuration file of generation format also is kept in the mobile phone;
Step 202, the user selects to recover the JAVA Default Value;
Step 203 is deleted corresponding JAVA installation file and all RMS data according to the configuration file that step 201 generates;
Step 204, the configuration file that generates according to step 201 recovers variable JAVA configuration file.
Below in conjunction with accompanying drawing and example, the technical scheme of the embodiment of the invention is illustrated.
Example one under the situation that does not have variable JAVA configuration file, will have unsuppressible-suppression and preset JAVA and use the recovery of dispatching from the factory.
Fig. 3 is the processing flow chart of the example one of the embodiment of the invention, as shown in Figure 3, comprises following processing:
Step 301, the JAVA configuration file stores that generates specific format when dispatching from the factory is to mobile phone ROM, and in embodiments of the present invention, first group of configuration file is 01000000;
Step 302, the user selects to recover the JAVA Default Value;
Step 303 reads the JAVA configuration file of specific format, according to the content of first and second byte in first group of the JAVA configuration file, the non-JAVA installation file that presets application in the deletion mobile phone, the RMS data that generate in the deletion mobile phone;
Step 304 judges whether to exist external memory card, and if the judgment is Yes, then execution in step 305, otherwise, execution in step 306;
Step 305 is preserved the JAVA installation file if exist in external memory card and the described external memory card, deletes the JAVA installation files all in the external memory card (SD card etc.) and the RMS data of generation;
Step 306 judges do not have the JAVA configuration file to be changed according to the 3rd byte content in first group of the JAVA configuration file, and factory reset is finished.
Embodiment two, variable JAVA configuration file is being arranged and do not presetting under the situation of JAVA application, carry out the JAVA Default Value and recover.
Fig. 4 is the processing flow chart of the example two of the embodiment of the invention, as shown in Figure 4, comprises following processing:
Step 401, the JAVA configuration file stores that generates specific format when dispatching from the factory is to mobile phone ROM, and wherein, first group of the JAVA configuration file is 00010100;
Step 402, the user selects to recover the JAVA Default Value;
Step 403, read the JAVA configuration file of specific format, judge, determine not preset the information that JAVA uses according to first byte content of first group of JAVA configuration file, then delete the JAVA installation file of all application in the mobile phone, the RMS data that generate in the deletion mobile phone;
Step 404 judges whether to exist external memory card, and if the judgment is Yes, then execution in step 405, otherwise, execution in step 406;
Step 405 is preserved the JAVA installation file if exist in external memory card and the described external memory card, deletes the JAVA installation files all in the external memory card (SD card etc.) and the RMS data of generation;
Step 406 judges have the JAVA configuration file to be changed according to the 3rd byte content of first group of JAVA configuration file, that is: the JAVA configuration file was changed after terminal is dispatched from the factory.The information that obtains according to first byte with the configuration file reduction that has changed, is promptly deleted the information that all JAVA use in the configuration file, and factory reset is finished.
Technical scheme by means of the embodiment of the invention, when selecting the JAVA factory reset the user, recover JAVA according to the configuration file that sets in advance and be applied to Default Value, remove user data, the recovery JAVA that dispatches from the factory uses, solved to use JAVA specially in the prior art and carried out the problem that Default Value recovers, can specially JAVA be used factory reset, guarantee that JAVA uses and stablize operate as normal, the embodiment of the invention does not need to back up the JAVA application file, can conserve storage, in addition, the embodiment of the invention can be used for the JAVA virtual machine of different platform, has good versatility.
Device embodiment
According to embodiments of the invention, a kind of terminal factory reset device is provided, Fig. 5 is the structural representation of the terminal factory reset device of the embodiment of the invention, as shown in Figure 5, the terminal factory reset device according to the embodiment of the invention comprises: generation module 50, removing module 52, recovery module 54.Below each module of the embodiment of the invention is described in detail.
Preferably, the data layout of configuration file is one group with 8 bits, and four bit groups are set altogether, and represents with 16 systems.In first bit group, first byte representation has or not and presets JAVA and use, and whether second byte representation presets that JAVA uses is to delete, and the 3rd byte representation presets JAVA and use whether variable JAVA configuration file is arranged, and remaining other bytes are for keeping the position; Second bit group is used for representing to preset the number of JAVA application; The 3rd bit group and the 4th bit group are used for representing that all preset the ID that JAVA uses.
Removing module 52 is used for when the user selects to recover the JAVA Default Value, deletes installation file and all the record management system RMS data that corresponding JAVA uses according to described configuration file;
Removing module 52 specifically is used for: use if preset JAVA according to first byte judgement existence of first bit group of configuration file, then delete JAVA installation file and all the RMS data that all non-JAVA of presetting use according to first byte and second byte;
If judge that according to first byte of first bit group in the configuration file not presetting JAVA uses, and then deletes JAVA installation file and all RMS data that all JAVA use;
Preserve the JAVA installation file if determine to exist in external memory card and the described external memory card, then delete all JAVA installation files and all RMS data in the external memory card.
Recover module 54 and be used for judging whether variable JAVA configuration file, be judged as under the situation that is, described variable JAVA configuration file is returned to factory state according to described configuration file.
Recovering module 54 specifically is used for: the 3rd byte according to first bit group of configuration file judges whether variable JAVA configuration file, is being judged as under the situation that is, variable JAVA configuration file is returned to factory state.
Generally speaking, the memory location of JAVA in mobile phone mainly comprises two parts, and first is in the middle of the mobile phone EMS memory, and another part is in the middle of the exterior storage medium (for example, SD card etc.), to be stored in respectively in the middle of the different catalogues.Comprise generally under this catalogue that installation file, JAVA that JAVA uses use the configuration file of operation needs and record management system (the Record Management System that JAVA application operation back produces, abbreviate RMS as) data (for example, user name, password etc.).Wherein, the configuration file that the installation file that JAVA uses and most JAVA use operation to be needed is an immutable content, can not change along with the operation of JAVA module, and the RMS data that the JAVA application produces and few JAVA configuration file is variable content.The content of terminal all new generations after dispatching from the factory is deleted in so-called factory reset exactly, with the content recovery of some variations state when dispatching from the factory.
Because the terminal of supporting JAVA to use is divided into and has JAVA to preset to use and do not have JAVA and preset and use two types, the application that JAVA presets is divided into again deleting uses and the unsuppressible-suppression application, in order to identify these differences, the embodiment of the invention has designed a kind of data layout, variable configuration file has certain contiguity in this data layout and the mobile phone, be used in factory reset, differentiating, differentiate whether delete the installation file that JAVA presets application with it, and whether variable JAVA configuration file arranged, and the JAVA configuration file that will change returns to the state when dispatching from the factory.The data that this data layout comprises are kept in the middle of the mobile phone read-only memory (Read-Only Memory abbreviates ROM as) in the mode of configuration file.
This data layout is one group with the 8bit group, and promptly 4 bytes are unit, represents with 16 systems, altogether 32bit.Wherein, first group first byte representation has or not and presets application, and application is preset in 1 representative, and 0 representative does not have and presets application; Whether first group second byte representation is can delete to preset application, and 1 representative can be deleted application, and on behalf of unsuppressible-suppression, 0 use; Whether this JAVA virtual machine has variable JAVA configuration file to first group the 3rd byte representation, and on behalf of this virtual machine, 1 variable JAVA configuration file is arranged, the no variable JAVA configuration file of 0 representative, and first group remainder bytes is for keeping the position.Second group of number of representing to preset application, the 3rd group to last one group of ID that represents to preset application.Wherein, using ID is produced by the JAVA virtual machine automatically according to the erection sequence that JAVA uses.For example, the current JAVA of 01,010,100 00,000,002 00,000,001 00000002 expressions has 2 deletable presetting to use A and B, their ID is respectively 00000001 and 00000002, and A installs prior to B, simultaneously, some configuration files of JAVA are variable in the operational process of JAVA module.
When mobile phone terminal dispatched from the factory, generation module 50 generated the configuration file of above-mentioned data layout, and it is kept in the mobile phone.In actual applications, this configuration file can generate or other modes generate by hand.
When the user selects to recover the JAVA Default Value, removing module 52 is according to the content deletion corresponding JAVA installation file and the RMS data of this configuration file, recover module 54 then and judge whether variable JAVA configuration file,, then return to factory state if having.
Above-mentioned processing procedure can be understood with reference to Fig. 2, Fig. 3, Fig. 4, does not repeat them here.
Technical scheme by means of the embodiment of the invention, when selecting the JAVA factory reset the user, recover JAVA according to the configuration file that sets in advance and be applied to Default Value, remove user data, the recovery JAVA that dispatches from the factory uses, solved to use JAVA specially in the prior art and carried out the problem that Default Value recovers, can specially JAVA be used factory reset, guarantee that JAVA uses and stablize operate as normal, the embodiment of the invention does not need to back up the JAVA application file, can conserve storage, in addition, the embodiment of the invention can be used for the JAVA virtual machine of different platform, has good versatility.
Although be the example purpose, the preferred embodiments of the present invention are disclosed, it also is possible those skilled in the art will recognize various improvement, increase and replacement, therefore, scope of the present invention should be not limited to the foregoing description.
Claims (10)
1. a terminal factory reset method is characterized in that, comprising:
Generation comprises configuration file and the preservation that JAVA uses deletion information;
When the user selects to recover the JAVA Default Value, delete installation file and all the record management system RMS data that corresponding JAVA uses according to described configuration file;
Judge whether variable JAVA configuration file according to described configuration file, be judged as under the situation that is, described variable JAVA configuration file is returned to factory state.
2. the method for claim 1 is characterized in that, the data layout of described configuration file is one group with 8 bits, and four bit groups are set altogether, and represents with 16 systems.
3. method as claimed in claim 2, it is characterized in that, in first bit group, first byte representation has or not and presets JAVA and use, whether the described JAVA of presetting of second byte representation uses is to delete, the 3rd the described JAVA of presetting of byte representation uses whether variable JAVA configuration file is arranged, and remaining other bytes are for keeping the position; Second bit group is used for representing to preset the number of JAVA application; The 3rd bit group and the 4th bit group are used for representing that all preset the ID that JAVA uses.
4. method as claimed in claim 3 is characterized in that, when the user selected to recover the JAVA Default Value, installation file and all record management system RMS data of deleting corresponding JAVA application according to described configuration file specifically comprised:
Use if preset JAVA, then delete JAVA installation file and all the RMS data that all non-JAVA of presetting use according to described first byte and described second byte according to first byte judgement existence of first bit group in the described configuration file;
If judge that according to first byte of first bit group in the described configuration file not presetting JAVA uses, and then deletes JAVA installation file and all RMS data that all JAVA use;
Preserve the JAVA installation file if determine to exist in external memory card and the described external memory card, then delete all JAVA installation files and all RMS data in the described external memory card.
5. method as claimed in claim 3 is characterized in that, judges whether variable JAVA configuration file according to described configuration file, is being judged as under the situation that is, described variable JAVA configuration file is returned to factory state specifically comprise:
The 3rd byte according to first bit group in the described configuration file judges whether variable JAVA configuration file, is being judged as under the situation that is, described variable JAVA configuration file is returned to factory state.
6. a terminal factory reset device is characterized in that, comprising:
Generation module is used to generate the configuration file and the preservation that comprise JAVA application deletion information;
Removing module is used for when the user selects to recover the JAVA Default Value, deletes installation file and all the record management system RMS data that corresponding JAVA uses according to described configuration file;
Recover module, be used for judging whether variable JAVA configuration file, be judged as under the situation that is, described variable JAVA configuration file is returned to factory state according to described configuration file.
7. device as claimed in claim 6 is characterized in that, the data layout of described configuration file is one group with 8 bits, and four bit groups are set altogether, and represents with 16 systems.
8. device as claimed in claim 7, it is characterized in that, in first bit group, first byte representation has or not and presets JAVA and use, whether the described JAVA of presetting of second byte representation uses is to delete, the 3rd the described JAVA of presetting of byte representation uses whether variable JAVA configuration file is arranged, and remaining other bytes are for keeping the position; Second bit group is used for representing to preset the number of JAVA application; The 3rd bit group and the 4th bit group are used for representing that all preset the ID that JAVA uses.
9. device as claimed in claim 8 is characterized in that, described removing module specifically is used for:
Use if preset JAVA, then delete JAVA installation file and all the RMS data that all non-JAVA of presetting use according to described first byte and described second byte according to first byte judgement existence of first bit group in the described configuration file;
If judge that according to first byte of first bit group in the described configuration file not presetting JAVA uses, and then deletes JAVA installation file and all RMS data that all JAVA use;
Preserve the JAVA installation file if determine to exist in external memory card and the described external memory card, then delete all JAVA installation files and all RMS data in the described external memory card.
10. device as claimed in claim 8 is characterized in that, described recovery module specifically is used for:
The 3rd byte according to first bit group in the described configuration file judges whether variable JAVA configuration file, is being judged as under the situation that is, described variable JAVA configuration file is returned to factory state.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110165611.8A CN102222027B (en) | 2011-06-20 | 2011-06-20 | Terminal factory reset method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110165611.8A CN102222027B (en) | 2011-06-20 | 2011-06-20 | Terminal factory reset method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102222027A true CN102222027A (en) | 2011-10-19 |
| CN102222027B CN102222027B (en) | 2017-07-04 |
Family
ID=44778583
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110165611.8A Active CN102222027B (en) | 2011-06-20 | 2011-06-20 | Terminal factory reset method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102222027B (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102591745A (en) * | 2011-12-26 | 2012-07-18 | Tcl集团股份有限公司 | Method and device for system recovery based on android system and intelligent equipment |
| CN102609304A (en) * | 2012-02-08 | 2012-07-25 | 广东欧珀移动通信有限公司 | Management method for internal third-party applications of Android mobile phone |
| CN102830995A (en) * | 2012-08-03 | 2012-12-19 | 广东欧珀移动通信有限公司 | Method for upgrading Android platform software with user data reserved |
| CN103309699A (en) * | 2012-03-16 | 2013-09-18 | 宇龙计算机通信科技(深圳)有限公司 | Mobile terminal and application program installation method |
| CN105138420A (en) * | 2015-07-31 | 2015-12-09 | 小米科技有限责任公司 | Data backup method, apparatus and system and data recovery method, apparatus and system |
| CN105391572A (en) * | 2015-10-15 | 2016-03-09 | 上海寰创通信科技股份有限公司 | Method for restoring factory configuration of equipment |
| CN105468411A (en) * | 2015-11-25 | 2016-04-06 | 北京金山安全软件有限公司 | Application processing method and device and electronic equipment |
| CN105824839A (en) * | 2015-01-06 | 2016-08-03 | 中兴通讯股份有限公司 | Method and apparatus for safe deletion of data in mobile terminal |
| CN105913711A (en) * | 2016-04-08 | 2016-08-31 | 无锡科技职业学院 | Centralized control restoring method for fusion communication |
| CN106028306A (en) * | 2016-05-03 | 2016-10-12 | 广东欧珀移动通信有限公司 | Method and device for restoring factory settings of terminal equipment and terminal equipment |
| CN106445745A (en) * | 2016-10-09 | 2017-02-22 | 青岛海信移动通信技术股份有限公司 | Terminal device and method for recovering factory settings |
| CN106569912A (en) * | 2016-11-02 | 2017-04-19 | 惠州Tcl移动通信有限公司 | Method and system of restoring factory settings for mobile terminal |
| CN106598759A (en) * | 2016-12-16 | 2017-04-26 | 广东美晨通讯有限公司 | Application processing method, device and system |
| CN106941672A (en) * | 2017-03-09 | 2017-07-11 | 东软集团股份有限公司 | The method and device of application software abnormality processing |
| CN107704337A (en) * | 2017-08-22 | 2018-02-16 | 北京珠穆朗玛移动通信有限公司 | Method, mobile terminal and the device with store function of factory reset |
| CN109982065A (en) * | 2017-12-27 | 2019-07-05 | 浙江宇视科技有限公司 | The method, apparatus and storage medium that equipment fault restores in video surveillance network |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007115863A1 (en) * | 2006-04-12 | 2007-10-18 | International Business Machines Corporation | Method and system for adjusting environment settings to the capabilities of a client device |
| CN101256498A (en) * | 2008-03-25 | 2008-09-03 | 中兴通讯股份有限公司 | Method and device for unloading terminal drive |
| CN101426032A (en) * | 2008-11-28 | 2009-05-06 | 深圳华为通信技术有限公司 | Terminal and method for Java application installation |
| CN101876914A (en) * | 2010-04-23 | 2010-11-03 | 中兴通讯股份有限公司 | Method for deleting files and mobile terminal |
| CN102043655A (en) * | 2011-01-04 | 2011-05-04 | 奇智软件（北京）有限公司 | Method and system for carrying out advanced uninstall on software |
-
2011
- 2011-06-20 CN CN201110165611.8A patent/CN102222027B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007115863A1 (en) * | 2006-04-12 | 2007-10-18 | International Business Machines Corporation | Method and system for adjusting environment settings to the capabilities of a client device |
| CN101256498A (en) * | 2008-03-25 | 2008-09-03 | 中兴通讯股份有限公司 | Method and device for unloading terminal drive |
| CN101426032A (en) * | 2008-11-28 | 2009-05-06 | 深圳华为通信技术有限公司 | Terminal and method for Java application installation |
| CN101876914A (en) * | 2010-04-23 | 2010-11-03 | 中兴通讯股份有限公司 | Method for deleting files and mobile terminal |
| CN102043655A (en) * | 2011-01-04 | 2011-05-04 | 奇智软件（北京）有限公司 | Method and system for carrying out advanced uninstall on software |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102591745A (en) * | 2011-12-26 | 2012-07-18 | Tcl集团股份有限公司 | Method and device for system recovery based on android system and intelligent equipment |
| CN102609304A (en) * | 2012-02-08 | 2012-07-25 | 广东欧珀移动通信有限公司 | Management method for internal third-party applications of Android mobile phone |
| CN102609304B (en) * | 2012-02-08 | 2013-09-25 | 广东欧珀移动通信有限公司 | Management method for internal third-party applications of Android mobile phone |
| CN103309699B (en) * | 2012-03-16 | 2017-05-17 | 宇龙计算机通信科技(深圳)有限公司 | Mobile terminal and application program installation method |
| CN103309699A (en) * | 2012-03-16 | 2013-09-18 | 宇龙计算机通信科技(深圳)有限公司 | Mobile terminal and application program installation method |
| CN102830995B (en) * | 2012-08-03 | 2015-11-18 | 广东欧珀移动通信有限公司 | A kind of Android platform software upgrade method retaining user data |
| CN102830995A (en) * | 2012-08-03 | 2012-12-19 | 广东欧珀移动通信有限公司 | Method for upgrading Android platform software with user data reserved |
| CN105824839A (en) * | 2015-01-06 | 2016-08-03 | 中兴通讯股份有限公司 | Method and apparatus for safe deletion of data in mobile terminal |
| CN105138420A (en) * | 2015-07-31 | 2015-12-09 | 小米科技有限责任公司 | Data backup method, apparatus and system and data recovery method, apparatus and system |
| CN105391572A (en) * | 2015-10-15 | 2016-03-09 | 上海寰创通信科技股份有限公司 | Method for restoring factory configuration of equipment |
| CN105468411A (en) * | 2015-11-25 | 2016-04-06 | 北京金山安全软件有限公司 | Application processing method and device and electronic equipment |
| CN105913711A (en) * | 2016-04-08 | 2016-08-31 | 无锡科技职业学院 | Centralized control restoring method for fusion communication |
| CN106028306A (en) * | 2016-05-03 | 2016-10-12 | 广东欧珀移动通信有限公司 | Method and device for restoring factory settings of terminal equipment and terminal equipment |
| CN106445745A (en) * | 2016-10-09 | 2017-02-22 | 青岛海信移动通信技术股份有限公司 | Terminal device and method for recovering factory settings |
| CN106569912B (en) * | 2016-11-02 | 2020-08-11 | 惠州Tcl移动通信有限公司 | Method and system for restoring factory settings of mobile terminal |
| CN106569912A (en) * | 2016-11-02 | 2017-04-19 | 惠州Tcl移动通信有限公司 | Method and system of restoring factory settings for mobile terminal |
| CN106598759A (en) * | 2016-12-16 | 2017-04-26 | 广东美晨通讯有限公司 | Application processing method, device and system |
| CN106941672A (en) * | 2017-03-09 | 2017-07-11 | 东软集团股份有限公司 | The method and device of application software abnormality processing |
| CN107704337A (en) * | 2017-08-22 | 2018-02-16 | 北京珠穆朗玛移动通信有限公司 | Method, mobile terminal and the device with store function of factory reset |
| CN107704337B (en) * | 2017-08-22 | 2020-08-25 | 北京珠穆朗玛移动通信有限公司 | Factory setting restoring method, mobile terminal and device with storage function |
| CN109982065A (en) * | 2017-12-27 | 2019-07-05 | 浙江宇视科技有限公司 | The method, apparatus and storage medium that equipment fault restores in video surveillance network |
| CN109982065B (en) * | 2017-12-27 | 2020-10-20 | 浙江宇视科技有限公司 | Method, device and storage medium for equipment fault recovery in video monitoring network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102222027B (en) | 2017-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102222027A (en) | Method and device for restoring factory settings of terminal | |
| CN101098343B (en) | Information interchange method for handset and network server | |
| CN101593157B (en) | Bad block management (BBM) method and device for Nand Flash | |
| CN102722386B (en) | Generate the method and apparatus of radio firmware AKU | |
| CN101714107A (en) | Database backup and recovery method and device in ERP system | |
| CN101673243B (en) | Data storage device and method | |
| CN100429628C (en) | Method for rebuilding directory structure and recovering data in NTFS volume | |
| CN104239166A (en) | Method for realizing file backup for running virtual machine | |
| CN101998695A (en) | Method, device and system for configuring WiFi setting parameters of terminal equipment | |
| CN101430705B (en) | Memory method and apparatus based on embedded database | |
| CN101163050A (en) | Equipment near-end maintenance method, system and equipment | |
| CN102088361A (en) | Data backup equipment, method and system | |
| CN104281538A (en) | Storage device capacity expanding and snapping method and storage devices | |
| CN105740469A (en) | Storage server and metadata access method | |
| CN102375738B (en) | A kind of apparatus and method of mobile terminal data management | |
| CN103516667A (en) | System, method and apparatus used for safety information data disaster recovery backup | |
| CN103440204B (en) | A kind of method of updating file system and memory device | |
| CN202444513U (en) | Information backup system for mobile terminal | |
| CN104572339A (en) | Data backup restoring system and method based on distributed file system | |
| CN101022633B (en) | Allocation data recovering method, system and device | |
| CN103065096A (en) | Data protection method, device and system | |
| CN103309906A (en) | Address book backup and recovery method and device | |
| CN102684928B (en) | The method and apparatus of a kind of service backup and recovery | |
| CN102004633A (en) | Method and device for processing control property | |
| CN101355548A (en) | Method and system for processing terminal data on PC side |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |