The document outlines a series of checkpoint logs related to a device's boot and restore process, detailing various steps such as clearing nonces, setting up display parameters, and enabling USB connections. Several warnings and errors are noted, including failures in starting threads and issues with missing files during the restoration options process. The logs indicate ongoing attempts to establish network interfaces and check compatibility between the host and device.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
18 views44 pages
PreviousRestoreLog_2025424_1134
The document outlines a series of checkpoint logs related to a device's boot and restore process, detailing various steps such as clearing nonces, setting up display parameters, and enabling USB connections. Several warnings and errors are noted, including failures in starting threads and issues with missing files during the restoration options process. The logs indicate ongoing attempts to establish network interfaces and check compatibility between the host and device.
libpartition: Successfully created root Hardware folder. Proceeding to create the rest of the folder hierarchy libpartition: Successfully created Battery under /mnt4/Hardware with permissions 0700 for user root libpartition: create_update_partition_folder_hierarchy: Done creating folder hierarchy for update partition Attempting to delete stale low space cleanup cookie file(if any) Successfully deleted low space cleanup cookie file libpartition: entering get_main_container_space_info
libpartition: No data device found, can't retrieve space info
libpartition: not deleting existing update filesystem entering ramrod_execute_command_with_config: /sbin/mount executing /sbin/mount -t apfs -o nobrowse /dev/disk2s7 /mnt4 waiting for child to exit child exited exit status: 0 libpartition: create_update_partition_folder_hierarchy: Creating folder hierarchy for update partition libpartition: Creating hardware folder hierarchy
libpartition: Creating root folder
libpartition: Successfully created root Hardware folder. Proceeding to create the rest of the folder hierarchy libpartition: Successfully created Battery under /mnt4/Hardware with permissions 0700 for user root libpartition: create_update_partition_folder_hierarchy: Done creating folder hierarchy for update partition Update volume was successfully unmounted. libpartition: Deleting contents of /mnt4... libpartition: Could not reset metadata on /mnt4: Read-only file system libpartition: Deleting contents of /mnt4 failed (result: 30). entering ramrod_probe_media_internal entering wait_for_device: 'EmbeddedDeviceTypeRoot' Using device path /dev/disk0 for EmbeddedDeviceTypeRoot device partitioning scheme is GPT APFS Container 'Container' /dev/disk0s1 Found synthesized APFS container. Using disk2 instead of /dev/disk0s1 device is APFS formatted found system volume not at /dev/disk0s1s1: System Captured preboot partition on main OS container 2 [11:16:56.0393-GMT]{3>6} CHECKPOINT END: (null):[0x068C] init_permanent_update_volume restore-step-ids = {0x11030677:52} restore-step-names = {0x11030677:perform_main_os_prepare} restore-step-uptime = 26 restore-step-user-progress = 4 Considering saving tolerated failures: false (null) false [11:16:56.0393-GMT]{3>6} CHECKPOINT BEGIN: (null):[0x0626] mount_filesystem restore-step-ids = {0x11030677:52;0x11030626:62} restore-step-names = {0x11030677:perform_main_os_prepare;0x11030626:mount_filesystem} restore-step-uptime = 26 restore-step-user-progress = 4 xART already mounted entering mount_filesystems ramrod_display_set_granular_progress_forced: 4.000000 entering mount_partition entering ramrod_execute_command_with_config: /sbin/mount_apfs executing /sbin/mount_apfs -R /dev/disk2s1 /mnt1 waiting for child to exit child exited exit status: 0 /dev/disk2s1 mounted on /mnt1 System mounted read-write Not counting data volume as required. Not counting user volume as required. ramrod_display_set_granular_progress_forced: 4.000000 entering mount_partition entering ramrod_execute_command_with_config: /sbin/mount_apfs executing /sbin/mount_apfs -R /dev/disk2s4 /mnt3 waiting for child to exit child exited exit status: 0 /dev/disk2s4 mounted on /mnt3 Baseband Data mounted read-write ramrod_display_set_granular_progress_forced: 4.000000 entering mount_partition entering ramrod_execute_command_with_config: /sbin/mount_apfs executing /sbin/mount_apfs -R /dev/disk2s5 /mnt6 waiting for child to exit child exited exit status: 0 /dev/disk2s5 mounted on /mnt6 Hardware mounted read-write Skipping mount of update partition ramrod_display_set_granular_progress_forced: 4.000000 entering mount_partition entering ramrod_execute_command_with_config: /sbin/mount_apfs executing /sbin/mount_apfs -R /dev/disk2s6 /mnt9 waiting for child to exit child exited exit status: 0 /dev/disk2s6 mounted on /mnt9 Preboot mounted read-write Tried to unmount a volume at '/mnt4' that wasn't mounted. Ignoring the error. Successfully called unmount on the update partition mount point(/mnt4). Attempting to mount the update partition at /mnt4 libpartition: entering mount_update_partition_if_exists