Unable to successfully restore device. Unable to restore device.

[AmenAllahGAMER]

I'm getting a restoration problem which is likely a critical issue for Apple APFS GPT Partitions and I'm likely not finding a solution into it...

And this is the entire ERROR Log:

21:55:11.514    <Info> Using ApTicket found at root_ticket.der length 8931
Using ApTicket found at root_ticket.der length 8931
idevicerestore 1.0.0 (libirecovery 1.3.1, libtatsu 1.0.5)
Found device in Restore mode
INFO: device serial number is INFERNO_1122
INFO: model is N104DEV
INFO: model is N104DEV
ECID: 1234605616436508552
Identified device as n104ap, iPhone12,1
Device Product Version: N/A
Device Product Build: N/A
Extracting BuildManifest from IPSW
IPSW Product Version: 14.0
IPSW Product Build: 18A373 Major: 18
Device supports Image4: true
Variant: Customer Erase Install (IPSW)
This restore will erase all device data.
##################################[ WARNING ]#################################
# You are about to perform an *ERASE* restore. ALL DATA on the target device #
# will be IRREVERSIBLY DESTROYED. If you want to update your device without  #
# erasing the user data, cancel now and restart without -e or --erase        #
# command line switch.                                                       #
# Type YES and press ENTER to continue, or hit CTRL+C to cancel.             #
##############################################################################
> YES

Checking IPSW for required components...
All required components found in IPSW
Getting ApNonce failed
Device is in an invalid state
Unable to get nonce from device
About to restore device...
Connecting now...
Connected to com.apple.mobile.restored, version 15
Device 00008030-1122334455667788 has successfully entered restore mode
Hardware Information:
BoardID: 4
ChipID: 32816
UniqueChipID: 1234605616436508552
ProductionMode: true
Starting Reverse Proxy
Device will not use nonce slots.
About to send RootTicket...
Sending RootTicket now...
Done sending RootTicket
Waiting for NAND (28)
Updating NAND Firmware (58)
Got status message
Unhandled status message (41)
Log is available:
[20:53:52.0169-GMT]{4>7} CHECKPOINT NOTICE: Image4 device: AP nonce clearable
entering ramrod_clear_ap_nonce
[20:53:52.0196-GMT]{4>7} CHECKPOINT NOTICE: AP nonce consumed
[20:53:52.0202-GMT]{4>7} CHECKPOINT NOTICE: Pre-existing NVRAM variable: restore-outcome=initial_monitor_no_return
[20:53:52.0213-GMT]{4>7} CHECKPOINT ANOMALY: [check_collection]auto-boot(does_not_exist)
[20:53:52.0215-GMT]{4>7} CHECKPOINT PROGRESS: START (unknown) -> (initial_engine_no_return)
[20:53:52.0217-GMT]{4>7} CHECKPOINT NOTICE: NVRAM access available on initial check
restore-anomalies = {0x00000000:[check_collection]auto-boot(does_not_exist)}
restore-outcome = initial_engine_no_return
executing /usr/sbin/nvram restore-outcome=initial_engine_no_return
[20:53:52.0521-GMT]{4>7} CHECKPOINT BEGIN: MAIN:[0x0400] umask
restore-step-ids = {0x11030400:1}
restore-step-names = {0x11030400:umask}
restore-step-uptime = 8
restore-step-user-progress = -1
[20:53:52.0534-GMT]{4>7} CHECKPOINT END: MAIN:[0x0400] umask
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 8
restore-step-user-progress = -1
[20:53:52.0540-GMT]{4>7} CHECKPOINT BEGIN: MAIN:[0x0402] setvbuf
restore-step-ids = {0x11030402:2}
restore-step-names = {0x11030402:setvbuf}
restore-step-uptime = 8
restore-step-user-progress = -1
[20:53:52.0546-GMT]{4>7} CHECKPOINT END: MAIN:[0x0402] setvbuf
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 8
restore-step-user-progress = -1
[20:53:52.0555-GMT]{4>7} CHECKPOINT BEGIN: MAIN:[0x0403] kernel_logger_thread
restore-step-ids = {0x11030403:3}
restore-step-names = {0x11030403:kernel_logger_thread}
restore-step-uptime = 8
restore-step-user-progress = -1
[20:53:52.0561-GMT]{4>7} CHECKPOINT END: MAIN:[0x0403] kernel_logger_thread
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 8
restore-step-user-progress = -1
[20:53:52.0568-GMT]{4>7} CHECKPOINT BEGIN: MAIN:[0x0406] set_progress_0
restore-step-ids = {0x11030406:4}
restore-step-names = {0x11030406:set_progress_0}
restore-step-uptime = 8
restore-step-user-progress = -1
found display: primary
display-boot-rotation = 0
display-scale = 2
display-rotation = 0
found applelogo at /usr/share/progressui/applelogo@1792~iphone.tga
display: 828 x 1792
Progress Bar Y offset at 112, display class 19
powering on display
ramrod_display_set_granular_progress_forced: 0.000000
[20:53:53.0276-GMT]{4>7} CHECKPOINT END: MAIN:[0x0406] set_progress_0
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 9
restore-step-user-progress = 0
[20:53:53.0284-GMT]{4>7} CHECKPOINT BEGIN: MAIN:[0x0407] start_gasgauge_thread
restore-step-ids = {0x11030407:5}
restore-step-names = {0x11030407:start_gasgauge_thread}
restore-step-uptime = 9
restore-step-user-progress = 0
[20:53:53.0310-GMT]{4>7} CHECKPOINT WARNING: MAIN:[0x0407] gasgauge_start_update_thread failed: -1
[20:53:53.0313-GMT]{4>7} CHECKPOINT END: MAIN:[0x0407] start_gasgauge_thread
restore-step-ids = {}
restore-step-names = {}
restore-step-warnings = {0x11060407:{0:"gasgauge_start_update_thread failed: -1"}}
restore-step-uptime = 9
restore-step-user-progress = 0
[20:53:53.0321-GMT]{4>7} CHECKPOINT BEGIN: MAIN:[0x0408] listen_for_log_client
restore-step-ids = {0x11030408:6}
restore-step-names = {0x11030408:listen_for_log_client}
restore-step-uptime = 9
restore-step-user-progress = 0
[20:53:53.0334-GMT]{4>7} CHECKPOINT END: MAIN:[0x0408] listen_for_log_client
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 9
restore-step-user-progress = 0
[20:53:53.0344-GMT]{4>7} CHECKPOINT BEGIN: MAIN:[0x040D] create_listen_socket
restore-step-ids = {0x1103040D:7}
restore-step-names = {0x1103040D:create_listen_socket}
restore-step-uptime = 9
restore-step-user-progress = 0
[20:53:53.0354-GMT]{4>7} CHECKPOINT END: MAIN:[0x040D] create_listen_socket
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 9
restore-step-user-progress = 0
[20:53:53.0360-GMT]{4>7} CHECKPOINT BEGIN: MAIN:[0x0404] update_root_mount
restore-step-ids = {0x11030404:8}
restore-step-names = {0x11030404:update_root_mount}
restore-step-uptime = 9
restore-step-user-progress = 0
[20:53:53.0390-GMT]{4>7} CHECKPOINT END: MAIN:[0x0404] update_root_mount
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 9
restore-step-user-progress = 0
[20:53:53.0396-GMT]{4>7} CHECKPOINT BEGIN: MAIN:[0x0405] disable_watchdog
restore-step-ids = {0x11030405:9}
restore-step-names = {0x11030405:disable_watchdog}
restore-step-uptime = 9
restore-step-user-progress = 0
[20:53:53.0407-GMT]{4>7} CHECKPOINT END: MAIN:[0x0405] disable_watchdog
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 9
restore-step-user-progress = 0
[20:53:53.0415-GMT]{4>7} CHECKPOINT BEGIN: MAIN:[0x040E] enable_usb
restore-step-ids = {0x1103040E:10}
restore-step-names = {0x1103040E:enable_usb}
restore-step-uptime = 9
restore-step-user-progress = 0
waiting for matching IOKit service: {
    IOProviderClass = AppleUSBDeviceMux;
}
[20:53:56.0552-GMT]{4>7} CHECKPOINT END: MAIN:[0x040E] enable_usb
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 12
restore-step-user-progress = 0
waiting for host to trigger start of restore [timeout of 120 seconds]
recv(9, 4) failed: connection closed
unable to read message size: -1
could not receive message
[20:55:22.0705-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x0600] client_protocol_version
restore-step-ids = {0x11030600:11}
restore-step-names = {0x11030600:client_protocol_version}
restore-step-uptime = 98
restore-step-user-progress = 0
client protocol version 15
[20:55:22.0713-GMT]{4>7} CHECKPOINT END: RESTORED:[0x0600] client_protocol_version
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 98
restore-step-user-progress = 0
[20:55:22.0722-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x0601] copy_restore_options
restore-step-ids = {0x11030601:12}
restore-step-names = {0x11030601:copy_restore_options}
restore-step-uptime = 98
restore-step-user-progress = 0
unable to open /usr/local/share/restore//options.n104.plist: No such file or directory
0: NSPOSIXErrorDomain/2: create_dictionary_from_plist: unable to open plist
unable to open /usr/local/share/restore//options.plist: No such file or directory
0: NSPOSIXErrorDomain/2: create_dictionary_from_plist: unable to open plist
*** UUID AB956DE9-16E1-5D52-B8D8-69ACAD6F84E5 ***
Restore options:
        UUID                           => <CFString 0x10510e8c0 [0x101c681b8]>{contents = "AB956DE9-16E1-5D52-B8D8-69ACAD6F84E5"}
        PersonalizedDuringPreflight    => <CFBoolean 0x101c69c00 [0x101c681b8]>{value = true}
        CreateFilesystemPartitions     => <CFBoolean 0x101c69c10 [0x101c681b8]>{value = false}
[20:55:22.0758-GMT]{4>7} CHECKPOINT END: RESTORED:[0x0601] copy_restore_options
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 98
restore-step-user-progress = 0
[20:55:22.0763-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x0655] is_host_compatible
restore-step-ids = {0x11030655:13}
restore-step-names = {0x11030655:is_host_compatible}
restore-step-uptime = 98
restore-step-user-progress = 0
Checkpoint engine recorder path set to /mnt5
[20:55:22.0772-GMT]{4>7} CHECKPOINT END: RESTORED:[0x0655] is_host_compatible
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 98
restore-step-user-progress = 0
[20:55:22.0779-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x0604] set_weight_from_options
restore-step-ids = {0x11030604:14}
restore-step-names = {0x11030604:set_weight_from_options}
restore-step-uptime = 98
restore-step-user-progress = 0
[20:55:22.0800-GMT]{4>7} CHECKPOINT END: RESTORED:[0x0604] set_weight_from_options
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 98
restore-step-user-progress = 0
[20:55:22.0810-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x068F] libauthinstall_callback
restore-step-ids = {0x1103068F:15}
restore-step-names = {0x1103068F:libauthinstall_callback}
restore-step-uptime = 98
restore-step-user-progress = 0
[20:55:22.0839-GMT]{4>7} CHECKPOINT END: RESTORED:[0x068F] libauthinstall_callback
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 98
restore-step-user-progress = 0
[20:55:22.0848-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x0608] device_has_hoover
restore-step-ids = {0x11030608:16}
restore-step-names = {0x11030608:device_has_hoover}
restore-step-uptime = 98
restore-step-user-progress = 0
[20:55:22.0863-GMT]{4>7} CHECKPOINT END: RESTORED:[0x0608] device_has_hoover
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 98
restore-step-user-progress = 0
[20:55:22.0871-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x060B] update_ticket
restore-step-ids = {0x1103060B:17}
restore-step-names = {0x1103060B:update_ticket}
restore-step-uptime = 98
restore-step-user-progress = 0
entering ramrod_ticket_update_verify
looking up boot manifest hash
device tree ticket_hash: F5694A2165DB8A4B317B501C2A20D3EE540C7D0F1AB97319DB6163A75C24C8B2C07136A679318D4FA9C9BB67D7DD8E4D
crypto-hash-method found. Using SHA2-384
computed ticket_hash   : F5694A2165DB8A4B317B501C2A20D3EE540C7D0F1AB97319DB6163A75C24C8B2C07136A679318D4FA9C9BB67D7DD8E4D
received valid ticket (8931 bytes)
[20:55:22.0930-GMT]{4>7} CHECKPOINT END: RESTORED:[0x060B] update_ticket
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 98
restore-step-user-progress = 0
[20:55:22.0940-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x060D] wait_for_storage
restore-step-ids = {0x1103060D:18}
restore-step-names = {0x1103060D:wait_for_storage}
restore-step-uptime = 98
restore-step-user-progress = 0
entering wait_for_storage_device
ramrod_display_set_granular_progress_forced: 0.000000
Searching for NAND service
Searching for NAND service
Found NAND service: AppleANS2NVMeController
NAND initialized. Waiting for devnode.
entering wait_for_device: 'EmbeddedDeviceTypeRoot'
Using device path /dev/disk0 for EmbeddedDeviceTypeRoot
entering ramrod_probe_media_internal
entering wait_for_device: 'EmbeddedDeviceTypeRoot'
Using device path /dev/disk0 for EmbeddedDeviceTypeRoot
[20:55:22.0998-GMT]{4>7} CHECKPOINT END: RESTORED:[0x060D] wait_for_storage
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 98
restore-step-user-progress = 0
[20:55:23.0006-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x060E] update_NAND_firmware
restore-step-ids = {0x1103060E:19}
restore-step-names = {0x1103060E:update_NAND_firmware}
restore-step-uptime = 99
restore-step-user-progress = 0
ramrod_display_set_granular_progress_forced: 0.000000
entering update_NAND
executing /usr/bin/nvmefwupdater --query
t302/000000010800A117.pak
error NAND firmware file not exist: /usr/standalone/firmware/t302/000000010800A117.pak
skipping update_NAND
executing /usr/bin/nvmefwupdater --skip
Asked to skip the firmware update
set_pci_port_state: result=0
set_pci_port_state: result=0
set_nvme_state: result=0
Skipped firmware update successfully
[20:55:25.0155-GMT]{4>7} CHECKPOINT END: RESTORED:[0x060E] update_NAND_firmware
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 101
restore-step-user-progress = 0
[20:55:25.0168-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x060F] clear_remap_variable
restore-step-ids = {0x1103060F:20}
restore-step-names = {0x1103060F:clear_remap_variable}
restore-step-uptime = 101
restore-step-user-progress = 0
entering clear_remap_variable
executing /usr/sbin/nvram -d enable-remap-mode
enable-remap-mode
[20:55:25.0503-GMT]{4>7} CHECKPOINT END: RESTORED:[0x060F] clear_remap_variable
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 101
restore-step-user-progress = 0
[20:55:25.0512-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x065C] print_nvram_variables
restore-step-ids = {0x1103065C:21}
restore-step-names = {0x1103065C:print_nvram_variables}
restore-step-uptime = 101
restore-step-user-progress = 0
ramrod_print_NVRAM_variables
executing /usr/sbin/nvram -xp
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>boot-args</key>
        <string></string>
        <key>restore-outcome</key>
        <data>
        aW5pdGlhbF9lbmdpbmVfbm9fcmV0dXJu
        </data>
</dict>
</plist>
[20:55:25.0949-GMT]{4>7} CHECKPOINT END: RESTORED:[0x065C] print_nvram_variables
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 101
restore-step-user-progress = 0
[20:55:25.0957-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x0610] asp_nand_set_writable
restore-step-ids = {0x11030610:22}
restore-step-names = {0x11030610:asp_nand_set_writable}
restore-step-uptime = 101
restore-step-user-progress = 0
[20:55:25.0978-GMT]{4>7} CHECKPOINT END: RESTORED:[0x0610] asp_nand_set_writable
restore-step-ids = {}
restore-step-names = {}
restore-step-uptime = 101
restore-step-user-progress = 0
[20:55:26.0001-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x0613] find_filesystem_partitions
restore-step-ids = {0x11030613:23}
restore-step-names = {0x11030613:find_filesystem_partitions}
restore-step-uptime = 102
restore-step-user-progress = 0
entering ramrod_probe_media_internal
entering wait_for_device: 'EmbeddedDeviceTypeRoot'
Using device path /dev/disk0 for EmbeddedDeviceTypeRoot
0: NSMachErrorDomain/ffffffffe00002c7: ramrod_probe_media_internal: unrecognized partitioning scheme
no conversion available for domain
find_filesystem_partitions: storage=/dev/disk0 container= system= data= baseband data= log= update= xart= hardware= scratch= preboot=
find_filesystem_partitions: recovery os container= volume=
[20:55:26.0037-GMT]{4>7} CHECKPOINT FAILURE:(FAILURE:41) RESTORED:[0x0613] find_filesystem_partitions [0]D(failed to find filesystem partitions)
restore-step-results = {0x11070613:{0:41}}
restore-step-codes = {0x11070613:{0:41}}
restore-step-domains = {0x11070613:{0:"AMRestoreErrorDomain"}}
restore-step-error = {0x11070613:"[0]D(failed to find filesystem partitions)"}
restore-step-uptime = 102
restore-step-user-progress = 0
[20:55:26.0050-GMT]{4>7} CHECKPOINT NOTICE: (NVRAM set) restore-step-user-progress=0 [sync=true] (first failure)
[20:55:26.0053-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x067C] cleanup_boot_command
restore-step-ids = {0x11030613:23;0x1103067C:24}
restore-step-names = {0x11030613:find_filesystem_partitions;0x1103067C:cleanup_boot_command}
restore-step-uptime = 102
restore-step-user-progress = 0
entering reset_boot_command_if_value
executing /usr/sbin/nvram -d recovery-boot-mode
recovery-boot-mode
[20:55:26.0519-GMT]{4>7} CHECKPOINT END: RESTORED:[0x067C] cleanup_boot_command
restore-step-ids = {0x11030613:23}
restore-step-names = {0x11030613:find_filesystem_partitions}
restore-step-uptime = 102
restore-step-user-progress = 0
[20:55:26.0530-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x1613] cleanup_recovery_os_volume
restore-step-ids = {0x11030613:23;0x11031613:25}
restore-step-names = {0x11030613:find_filesystem_partitions;0x11031613:cleanup_recovery_os_volume}
restore-step-uptime = 102
restore-step-user-progress = 0
[20:55:26.0547-GMT]{4>7} CHECKPOINT END: RESTORED:[0x1613] cleanup_recovery_os_volume
restore-step-ids = {0x11030613:23}
restore-step-names = {0x11030613:find_filesystem_partitions}
restore-step-uptime = 102
restore-step-user-progress = 0
[20:55:26.0565-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x0647] cleanup_check_result
restore-step-ids = {0x11030613:23;0x11030647:26}
restore-step-names = {0x11030613:find_filesystem_partitions;0x11030647:cleanup_check_result}
restore-step-uptime = 102
restore-step-user-progress = 0
[20:55:26.0572-GMT]{4>7} CHECKPOINT END: RESTORED:[0x0647] cleanup_check_result
restore-step-ids = {0x11030613:23}
restore-step-names = {0x11030613:find_filesystem_partitions}
restore-step-uptime = 102
restore-step-user-progress = 0
[20:55:26.0587-GMT]{4>7} CHECKPOINT BEGIN: RESTORED:[0x0648] cleanup_send_final_status
restore-step-ids = {0x11030613:23;0x11030648:27}
restore-step-names = {0x11030613:find_filesystem_partitions;0x11030648:cleanup_send_final_status}
restore-step-uptime = 102
restore-step-user-progress = 0

Unable to successfully restore device
Unable to restore device

So, Is there any solution to this please?

[chris-pcguy]

and what's the full command line, that you're using for the iOS VM?

[chris-pcguy]

Sigh, I think we already established that you stick with each letter of the manual/guide, until you're more experienced.
The guide is clearly using 14.0beta5, not 14.0. Try that (the former) version.
Also, are you sure that you're creating the disk files correctly?
Also make sure that you're always running the latest commit.

[VisualEhrmanntraut]

It is supposed to support every iOS 14 version, and I am going to present you the real problem:

Using device path /dev/disk0 for EmbeddedDeviceTypeRoot
0: NSMachErrorDomain/ffffffffe00002c7: ramrod_probe_media_internal: unrecognized partitioning scheme
no conversion available for domain
find_filesystem_partitions: storage=/dev/disk0 container= system= data= baseband data= log= update= xart= hardware= scratch= preboot=
find_filesystem_partitions: recovery os container= volume=
[20:55:26.0037-GMT]{4>7} CHECKPOINT FAILURE:(FAILURE:41) RESTORED:[0x0613] find_filesystem_partitions [0]D(failed to find filesystem partitions)
restore-step-results = {0x11070613:{0:41}}
restore-step-codes = {0x11070613:{0:41}}
restore-step-domains = {0x11070613:{0:"AMRestoreErrorDomain"}}
restore-step-error = {0x11070613:"[0]D(failed to find filesystem partitions)"}
restore-step-uptime = 102
restore-step-user-progress = 0

This error suggests that you are actually using the Upgrade RAM Disk instead of the Erase one. The error presented by iOS is that there is no filesystem inside the root disk, and it therefore cannot upgrade its iOS version. You just need to switch to the correct RAM Disk.

[chris-pcguy]

Okay.. I'll try using the iOS 14.0beta5 instead

But, wait I have a question.. does it support every iOS 14 Version or just iOS 14.0beta5 ?

The manual clearly says all, but I don't trust you (yet) from deviating from the manual.
I'm not sure yet what exactly you did wrong, but I'm fairly certain that you've done something wrong.
First I assumed it to be an actual bug, but since you deviated from the manual and with your past history, so now and then, I have to assume that it isn't an actual bug.

[chris-pcguy]

This error suggests that you are actually using the Upgrade RAM Disk instead of the Erase one. The error presented by iOS is that there is no filesystem inside the root disk, and it therefore cannot upgrade its iOS version. You just need to switch to the correct RAM Disk.

Damn him. I recently got rid of my copy of the 14.0 release, because I need the space otherwise. So I couldn't check that without redownloading, and I'm not doing that effort for him, especially after all his spurious/invalid bug reports.
Okay, now I can't even assume that he would even get that right.

[chris-pcguy]

I think I didn't choose the right RAM Disk..
You can check this

do you expect us to carry your hand at every step of the way?

and I'm currently using this one: --> 048-58645-641.dmg

as seen on the cmdline you posted.

[VisualEhrmanntraut]

I couldn't have answered more clearly previously, and we will not further provide responses; your access to discussions will now be terminated.