Unable to send data to ASR. Sent 0 of 131092 bytes.

[therock444]

Operating System

Arch Linux

What is your CPU's model?

Intel core i5-5300U

Describe the unexpected behaviour in detail.

when running idevicerestore, it starts working for a bit before seemingly randomly failing with "Unable to send data to ASR. Sent 0 of 131092 bytes." multiple times before aborting, this happens at a random arbitrary percantage while sending the filesystem
i also tried recompiling idevicerestore with the patch in #119 same deal though
additionally i tried removing --erase from the command as stated in #169 but same result

What should've happened instead?

the command shouldve finished restoring the iphone

Attach any logs related to this issue.

final iphone logs:
ASR: Validating sizes... ASR: done ASR STATUS: restore ASR RESTORE PROGRESS: 2% ramrod_display_set_granular_progress_forced: 8.000000 Sep 26 13:04:40 PurpleReverseProxy[9] : RPSocket.cpp:218(signal): No client callback, missing event 8 for socket 0x112904190 Sep 26 13:04:40 PurpleReverseProxy[9] : RPSocket.cpp:360(FinalizeRPSocket): Closed <RPSocket 0x1129042b0: CtrlConn fd=-1> after reading 103 bytes and writing 109 bytes Sep 26 13:04:40 PurpleReverseProxy[9] : RPSocket.cpp:363(FinalizeRPSocket): Ending os transaction for <RPSocket 0x1129042b0: CtrlConn fd=-1> recv(9, 4) failed: connection closed unable to read message size: -1 could not receive message

Issue Report Terms

• You have made sure that there are no other reports about this bug.
• You do not use any software that might interfere with correct function of this software. For Hackintosh users, that could be OCLP, WEG, etc.
• You are on the latest commit of the emulator.
• You acknowledge that violation of these terms may result in your issue being closed or you getting blocked from the organisation.

[VisualEhrmanntraut]

and... the logs from the side of the iphone instead of the companion are...?

[therock444]

you mean the logs qemu outputs when you run qemu-system-aarch64 with the flags for the iphone? those are the attached logs atleast the final ones, if you need the companion logs i can retry and dump them

[VisualEhrmanntraut]

sorry, I was tired. rather please attach the full logs from both sides

[therock444]

restore.log
iphone.log
here you go
if you need the commands im using for both:
iphone:
QEMUAppleSilicon/build/qemu-system-aarch64 -M t8030,trustcache=iPhone11_8_iPhone12_1_14.0_18A5351d_Restore/Firmware/038-44135-124.dmg.trustcache,ticket=root_ticket.der,sep-fw=sep-firmware.n104.RELEASE.new.img4,sep-rom=AppleSEPROM-Cebu-B1,kaslr-off=true,usb-conn-type=unix,usb-conn-addr=/tmp/iphone.sock \ -kernel iPhone11_8_iPhone12_1_14.0_18A5351d_Restore/kernelcache.research.iphone12b -dtb iPhone11_8_iPhone12_1_14.0_18A5351d_Restore/Firmware/all_flash/DeviceTree.n104ap.im4p \ -initrd iPhone11_8_iPhone12_1_14.0_18A5351d_Restore/038-44135-124.dmg \ -append "tlto_us=-1 mtxspin=-1 agm-genuine=1 agm-authentic=1 agm-trusted=1 serial=3 launchd_unsecure_cache=1 wdt=-1 -vm_compressor_wk_sw" \ -smp 7 -m 5G -serial mon:stdio \ -drive file=sep_nvram,if=pflash,format=raw \ -drive file=sep_ssc,if=pflash,format=raw \ -drive file=root,format=raw,if=none,id=root -device nvme-ns,drive=root,bus=nvme-bus.0,nsid=1,nstype=1,logical_block_size=4096,physical_block_size=4096 \ -drive file=firmware,format=raw,if=none,id=firmware -device nvme-ns,drive=firmware,bus=nvme-bus.0,nsid=2,nstype=2,logical_block_size=4096,physical_block_size=4096 \ -drive file=syscfg,format=raw,if=none,id=syscfg -device nvme-ns,drive=syscfg,bus=nvme-bus.0,nsid=3,nstype=3,logical_block_size=4096,physical_block_size=4096 \ -drive file=ctrl_bits,format=raw,if=none,id=ctrl_bits -device nvme-ns,drive=ctrl_bits,bus=nvme-bus.0,nsid=4,nstype=4,logical_block_size=4096,physical_block_size=4096 \ -drive file=nvram,if=none,format=raw,id=nvram -device apple-nvram,drive=nvram,bus=nvme-bus.0,nsid=5,nstype=5,id=nvram,logical_block_size=4096,physical_block_size=4096 \ -drive file=effaceable,format=raw,if=none,id=effaceable -device nvme-ns,drive=effaceable,bus=nvme-bus.0,nsid=6,nstype=6,logical_block_size=4096,physical_block_size=4096 \ -drive file=panic_log,format=raw,if=none,id=panic_log -device nvme-ns,drive=panic_log,bus=nvme-bus.0,nsid=7,nstype=8,logical_block_size=4096,physical_block_size=4096 \ -display gtk,zoom-to-fit=on,show-cursor=on

companion:
QEMUAppleSilicon/build/qemu-system-x86_64 -cpu host -m 2G -smp 2 -accel kvm -cdrom arch.iso -hda arch.img -usb -device usb-ehci,id=ehci -device usb-tcp-remote,conn-type=unix,conn-addr=/tmp/iphone.sock,bus=ehci.0 -boot cd,menu=on

[chris-pcguy]

-m 5G

Why on earth are you doing that?

[therock444]

i just tried it maybe it would change something
same thing happens on -m 4G which is the default

[chris-pcguy]

Have you made sure that the ipsw, that you put inside the companion, is complete and not corrupted? Is there enough free space left? What exact idevicerestore command are you using?

[therock444]

1. just in case ive redownloaded and recopied it over 2 times, so yeah im pretty sure its not corrupted
2. the companion has 40gb of total space, ~30 left and the iphone has 16 total, maybe ill retry it with 32 assigned to root
3. idevicerestore --erase --restore-mode -i 0x1122334455667788 iPhone11,8,iPhone12,1_14.0_18A5351d_Restore.ipsw -T root_ticket.der as shown in the wiki

[chris-pcguy]

maybe ill retry it with 32 assigned to root

the default settings are not the problem, the whole "I want to experiment without knowing what I'm doing. Oops, something broke. I'll just report an issue without telling what I've done different." is.

First with 5 GiB of RAM, and now 32 GiB for the nvme root file (formerly nvme.1)?

I would say stop the experiments until you're more comfortable using the emulator, maybe after you made it run successfully at least once.

Just try to turn off your brain and instead blindly follow the instructions. Not thinking, just doing.

https://www.youtube.com/watch?v=og2unLDWNHg

[therock444]

sure, i redid the entire thing from the ground up without deviating from the guide one bit and i got the exact same result 1:1

[chris-pcguy]

Are you sure that you're using the patched idevicerestore instead of the one installed by pacman? Try which idevicerestore.

[therock444]

returns /usr/local/bin/idevicerestore

[VisualEhrmanntraut]

I can't find whether you are actually using a modified version of the very latest idevicerestore commit. The commit hash in the log goes to 404 (libimobiledevice/idevicerestore@geda43ac).

[VisualEhrmanntraut]

but if you are, maybe this is related:

ASR: 2025-09-26 20:38:16.197724+0000 asr[27:621] [si_destination_compare] send failed: Invalid argument
ASR: 2025-09-26 20:38:16.200586+0000 asr[27:621] [si_destination_compare] send failed: Undefined error: 0
ASR: 2025-09-26 20:38:16.204688+0000 asr[27:621] [si_destination_compare] send failed: Invalid argument

[VisualEhrmanntraut]

just updated all the tools. it works fine.

[therock444]

this is mostly for proof of concept, i dont really care how awful it runs
im giving 4gb of ram to the iphone, 2gb to the companion, and the host has 8gb, with nothing open i usually have 7gb free
/dev/nvme0n1p3 226G 154G 61G 72% / so space isnt a problem
and no i actually havent verified the checksum, where can i find it

[therock444]

i retried again after the random segfault, well it got further actually, to 68% before the same thing happened

[VisualEhrmanntraut]

try running the companion under kvm (-accel kvm)

[therock444]

ive always had the companion accelerated with kvm, as shown in my reply with the initial logs and commands

[VisualEhrmanntraut]

didn't notice. maybe then try not using kvm. that screenshot I showed you was with both fully emulated (m3 macbook pro)

[therock444]

alright i tried with tcg, first off DAMN that was slow, secondly it died at 63%, same thing
i noticed my ram usage was really high, only 300mb free physical, and using 4gb of swap out of 8gb of swap total

[VisualEhrmanntraut]

maybe just try 1gb for companion and 3-4gb for the iphone

[therock444]

i tried 1gb companion 3gb iphone, the phone kernel panicked so i switched to 4, ram usage was a bit lighter but in the end same result
im pretty lost, but the only pattern ive noticed is every attempt it fails earlier, e.g attempt 1 it got to 68%, next one 63%, now 20%, it happened in the other run too but thats all i know

[VisualEhrmanntraut]

the phone kernel panicked

?

[therock444]

as i said, it dies at 3gb of ram with some debug logs

[therock444]

okay nevermind it was dying because of an unrelated thing, i fixed that and i started flashing
not surprisingly at this point the restore failed at 15%, continuing the pattern of decreasing the failure point after every attempt

[therock444]

as an update, im upgrading to a much better laptop (ryzen 5 5625U, 16gb ram) soon and ill retry it on that, probably ruling out any weird hardware constraints
if that works then ill just update and close the issue

[therock444]

i upgraded to the new laptop and i can confirm the restore works just fine and the first boot works
so uhhh i dont know where this leaves me but it was either the CPU just being too slow somehow or more likely RAM constraints screwing something up

[therock444]

[VisualEhrmanntraut]

bro... the wiki literally tells you that you have to do the FS patches.

[lyntaxxq]

I got the same error, anyone have ideas?

[therock444]

try 4GB to the companion maybe? not sure

[lyntaxxq]

ok i'll try it, also i removed all files and started from zero.

[lyntaxxq]

yaaay!! it's fixed. starting from zero is the only solution (i guess) for now.

[VisualEhrmanntraut]

yaaay!! it's fixed. starting from zero is the only solution (i guess) for now.

not the ram amount?

[lyntaxxq]

yaaay!! it's fixed. starting from zero is the only solution (i guess) for now.

not the ram amount?

didn't tried it.