IP Library Granted Patent US 12,450,133
Granted Patent B2
US 12,450,133 · App. 18/618,711 · Granted Oct 21, 2025

Electronic device for recovering file and operation method of electronic device

Inventors: Haewook Lee (Suwon-si, KR); Hyunjoon Kim (Suwon-si, KR); Kwanhee Jeong (Suwon-si, KR); Hyojong Kim (Suwon-si, KR)
Assignee: SAMSUNG ELECTRONICS CO., LTD.
G06F11/1469
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,450,133
App. No.
18/618,711
Granted
Oct 21, 2025
Kind
B2
Abstract

An electronic device may comprise memory for storing a file obtained by compressing a file including at least one module as a package, and a processor, wherein the processor: generates an uncompressed file by decompressing the compressed file; stores the generated uncompressed file in the memory; during booting of the electronic device, identifies whether deformation has occurred in the uncompressed file; and in response to the occurrence of deformation in the uncompressed file, performs a recovery operation for the uncompressed file. A method comprises: generating an uncompressed file by decompressing a file obtained by compressing a file including at least one module as a package; storing the generated uncompressed file in a memory; during booting of the electronic device, identifying whether deformation has occurred in the uncompressed file; and in response to the occurrence of deformation in the uncompressed file, performing a recovery operation for the uncompressed file.

Claims (40)

1. An electronic device, comprising:

at least one processor; and

memory for storing a compressed file of a file that constitutes at least one module into a package, the memory comprising instructions that, when executed by the at least one processor individually or collectively, cause the electronic device to:

decompress the compressed file to create an uncompressed file,

store the uncompressed file in the memory,

mount the at least one module included in the uncompressed file,

in response to mounting the at least one module, identify whether corruption has occurred in the uncompressed file while booting the electronic device,

in response to identifying that the corruption has occurred in the uncompressed file while booting the electronic device, unmount the at least one module,

in response to unmounting the at least one module, delete the uncompressed file that is corrupted including the at least one module that is unmounted, based on identifying that the corruption has occurred in the uncompressed file,

decompress the compressed file stored in the memory to recreate another uncompressed file, and

perform a recovery operation of the uncompressed file corresponding to the corruption occurring in the uncompressed file by mounting the at least one module based on the another uncompressed file that is recreated.

2. The electronic device of claim 1 , wherein the instructions that, when executed by the at least one processor, cause the electronic device to notify that the recovery operation is performed by storing a designated value in a designated area of the memory corresponding to performing the recovery operation.

3. The electronic device of claim 1 , wherein the instructions that, when executed by the at least one processor, cause the electronic device to:

identify whether a hash value previously designated for the uncompressed file matches a hash value generated for the uncompressed file,

identify that the corruption has occurred in the uncompressed file based on the hash values not matching, and

store a panic message in a designated node.

4. The electronic device of claim 1 , wherein the instructions that, when executed by the at least one processor, cause the electronic device to:

identify whether the corruption has occurred in the uncompressed file based on a signature check that identifies whether a signature previously designated for the module mounted matches a signature of the module mounted, and

identify that the corruption has occurred in the uncompressed file based on the signatures not matching.

5. The electronic device of claim 4 , wherein the instructions, when executed by the processor, cause the electronic device to present a notification of information related to the uncompressed file that is corrupted by storing a designated value in a designated area of the memory corresponding to identifying that the corruption has occurred in the uncompressed file.

6. The electronic device of claim 4 , wherein the instructions that, when executed by the at least one processor, cause the electronic device to reboot the electronic device before the recovery operation of the uncompressed file.

7. The electronic device of claim 4 , wherein the instructions, when executed by the processor, cause the electronic device to perform the recovery operation of the uncompressed file without rebooting the electronic device.

8. The electronic device of claim 1 , wherein the instructions that, when executed by the at least one processor, cause the electronic device to display information indicating completion of recovery on the display corresponding to completing the recovery operation of the uncompressed file.

9. A method of operating an electronic device, the method comprising:

creating an uncompressed file by decompressing a compressed file of a file that constitutes at least one module into a package;

storing the uncompressed file in memory of the electronic device;

mounting the at least one module included in the uncompressed file;

in response to mounting the at least one module, identifying whether corruption has occurred in the uncompressed file while booting the electronic device;

in response to identifying that the corruption has occurred in the uncompressed file while booting the electronic device, unmounting the at least one module;

in response to unmounting the at least one module, deleting the uncompressed file that is corrupted including the at least one module that is unmounted, based on identifying that the corruption has occurred in the uncompressed file;

decompressing the compressed file stored in the memory to recreate another uncompressed file; and

performing a recovery operation of the uncompressed file corresponding to the corruption occurring in the uncompressed file by mounting the at least one module based on the another uncompressed file that is recreated.

10. The method of claim 9 , further comprising notifying that the recovery operation is performed by storing a designated value in a designated area of the memory corresponding to performing the recovery operation.

11. The method of claim 9 , wherein identifying whether the corruption has occurred in the uncompressed file comprises:

identifying whether a hash value previously designated for the uncompressed file matches a hash value generated for the uncompressed file;

identifying that the corruption has occurred in the uncompressed file based on the hash values not matching, and

storing a panic message in a designated node.

12. The method of claim 9 , wherein identifying whether corruption has occurred in the uncompressed file comprises:

identifying whether the corruption has occurred in the uncompressed file based on a signature check that identifies whether a signature previously designated for the module mounted matches a signature of the module mounted; and

identifying that the corruption has occurred in the uncompressed file corresponding to the signatures not matching.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 4, 2025
From: LEE, HAEWOOK; KIM, HYUNJOON; JEONG, KWANHEE; KIM, HYOJONG
To: SAMSUNG ELECTRONICS CO., LTD.
Reel/Frame 071320/0528 →
Priority Claims (1)
KR 10-2021-0156037 · Nov 12, 2021 · national
Continuity (2)
Continuation PCTKR2022017768 · Nov 11, 2022
Related Publication 20240241799A1 · Jul 18, 2024
References Cited (24)
US 6519733B1 · Har et al. · 2003 [cited by applicant]
US 6591376B1 · Vanrooven et al. · 2003 [cited by applicant]
US 7594136B2 · Kerner et al. · 2009 [cited by applicant]
US 7694191B1 · Bono et al. · 2010 [cited by applicant]
US 8122234B1 · Orr · 2012 [cited by applicant]
US 11550480B2 · Stöttinger et al. · 2023 [cited by applicant]
US 20080114950A1 · Graham · 2008 [cited by applicant]
US 20090158086A1 · Kwon · 2009 [cited by applicant]
US 20170139786A1 · Simon · 2017 [cited by examiner]
US 20180322012A1 · Sharma · 2018 [cited by examiner]
CN 105279047A · 2016 [cited by applicant]
CN 111209143A · 2020 [cited by applicant]
CN 113296781A · 2021 [cited by applicant]
CN 113505014A · 2021 [cited by applicant]
KR 20060097329A · 2006 [cited by applicant]
KR 100652662B1 · 2006 [cited by applicant]
KR 20140000369A · 2014 [cited by applicant]
KR 101369251B1 · 2014 [cited by applicant]
KR 101727860B1 · 2017 [cited by applicant]
KR 102142905B1 · 2020 [cited by applicant]
WO 2020251542A1 · 2020 [cited by applicant]
International Search Report for International Application No. PCT/KR2022/017768; International Filing Date Nov. 11, 2022; International Search Report Mail Date Feb. 17, 2023; 4 Pages. [cited by applicant]
NAVER Corp.; blog, “Bravo !! My Life”; NAVER 1784, 95, Jeongjail-ro, Bundang-gu, Seongnam-si, Gyeonggi-do, Republic of Korea; Published Online: Dec. 31, 2016; 5 Pages. URL: https://m.blog.naver.com/PostView.naver?blogld… [cited by applicant]
Extended European Search Report Issued In EP Application No. 22893272.9-1203, Mail Date Nov. 13, 2024, 12 Pages. [cited by applicant]