Closed m1stadev closed 1 year ago
Thanks for the bug report! I don't have a compatible device to test this on, but it seems this bug occurs because of some race for sending the different software components. Can you verify if this happens repeatedly or just this once?
Thanks for the bug report! I don't have a compatible device to test this on, but it seems this bug occurs because of some race for sending the different software components. Can you verify if this happens repeatedly or just this once?
I've verified this issue persists on both devices. I plan to do more testing & find a fix when I get home.
@m1stadev I have fixed several stuff all around the recovery's code to support the new Apple Silicon mac updates (eventhough not arround the RestoreSEP
part specifically). Can you verify if the problem persists?
@m1stadev I have fixed several stuff all around the recovery's code to support the new Apple Silicon mac updates (eventhough not arround the
RestoreSEP
part specifically). Can you verify if the problem persists?
Unfortunately doesn't look like this fixed the issue. Also, I've noticed that A10 restores no longer work (but still work when using ce971e9)
I'm okay with merging the drafted PR that at least fixes that issue
Although merging it should be a commit for fix support for >=A10, instead of <A10
My bad. Only now noticed you referenced the commit from the master and not from your existing PR
@m1stadev I think futurerestore is better way to do it and as I know you are one of it's contributors.
@vadimszzz that's a pymboledevice3 error. Probably something different with the apticket generation on these devices. I would work to fix that (by simply sniffing and comparing with apple configurator) but I don't have a device to test it with.
Also, futurerestore is meant for performing the process for unsigned firmwares, so you probably meant idevicerestore (12.5.5 is still signed on older models)
Test environment
Describe the bug While restoring an iOS device using
pymobiledevice3 restore update
,To Reproduce
Expected behavior A successful restore.
Logs
Additional context As far as I can tell, this issue only seems to be when restoring to iOS 12.5.5.