Open NotAlexNoyle opened 6 years ago
@goodboydheeraj I've contributed to that issue with previous logs. Today is the first time I've reproduced it in months (and on a new device with an iOS 11 target).
Also, that branch is inactive.
I see
restored_fdr_initialize: FDR is supported
then
RestoredFDRCreate() returned 6 FDR is not supported on this device
which doesn't quite make sense. Could you check the IPSW hash against the hash listed on ipsw.me?
@encounter FYI, I have a test device that I can use for as long as you want me to, until Apple stops signing 10.2.2. If there's anything I can do to help you figure out what's happening here , let me know.
I'm looking into it. I think one way you could help is restoring the device with iTunes, while running some kind of USB packet capture (possibly Wireshark?). I'll also be looking into doing this with my own test device.
idevicerestore apparently doesn't know what to send during the FDR data step, which could be the root cause.
If idevicerestore is the root of the problem, it's odd that futurerestore would work on any devices at all.
I'll try to run wireshark on a restore when I get home and post logs.
Thank you for looking into this! This is a really important restore path to have working, because it will allow Apple TV 4 owners to switch from a tvos10 jailbreak to a future tvos11 jailbreak.
Wireshark seems to only support USB packet capture on Windows and Linux. I guess I will try a windows VM? We'll see how it goes. Otherwise I'll need alternative software.
EDIT: It actually only supports it on windows if it's a windows virtual machine with a linux host. Which I can do. But inconvenient.
There does appear to be a way to capture using Wireshark on macOS: https://stackoverflow.com/a/47530380
I haven't tried it yet though.
Device: Apple TV 4 on iOS 10.2.2
Target: iOS 11.1