Log output on the terminal is quite broken and restores take forever.
Lately i needed to use idevicerestore to update my iPad Pro to iPadOS 26 beta 3, but when i tried to do so i noticed that the log output on the terminal is completely scrambled and the restore takes much longer than it should in the process (like 30 minutes longer).
OS: Windows 7 - 64 bit, i also tested Windows 11 as well and got the same result.
I also tested around to rule out other dependencies that may cause this, it is an idevicerestore problem.
Here's some images taken during an update restore on a iPhone X:
And for reference, this is what it should look like (i used an older version of idevicerestore, all dependencies are the latest versions)
And using the version that outputs the broken logs, the restores also take much longer than with the proper working version im not sure why it takes much longer than usual.
There might be a fix in the pull requests page here: #743 but i right now can't test it.
I'm experiencing the same issue on Windows 10. #743 didn't resolve it for me. It looks like this regression was introduced in 8061f08b4e0a8f0ab5d1548b7e9978f3cc8647a2; a5905b7f905fc3cc83033ebd963f0dcba071e512 works fine.
Could you verify if the latest code still has the logging issues? There was a bugfix a while ago, but not sure if it addressed everything: https://github.com/libimobiledevice/idevicerestore/commit/8d0563380db8f3412de1fabf5ad74ccde1159eac
@nikias the output is still messed up and the restore still takes longer than normal:
iPhone 12 (D53g), iOS 26.0 23A340
Check commit ae1539e534d9d9c78ed54573d831519cfcb8741b (just committed)
It made a big improvement in the logging, its not perfect as it is still a little messy with filenames and the progress bars but it is much better.
Restores are still way slower than normal but thanks to the more readable logging i can see that it's slow particularly when restoring
the Cryptex1 SystemOS image, it takes around 25 minutes to restore the image in this case.
Restoring the Cryptex SystemOS should take a few minutes at most.
Here's what the command prompt looks like now, along with a full log of the restore copied and pasted from the command prompt itself so you can see where all the malformations are: log.txt
Can you confirm if it would restore faster if you go to a commit before the logging refactoring?
@nikias I can confirm it took only 10 minutes and 15 seconds with the same iPhone and IPSW before the commit (3x faster).
here's the log: log.txt
Hello there,
I encountered the same issue. Only that when compiled for Linux (with the latest versions ATTOW) it takes upwards of several hours (flashing iOS 26.0.1 on iPhone 13 mini). Its only progressed 5% in 20 minutes when sending the Cryptex1,SystemOS image. Have you found a solution for this?
Can confirm with the latest commit the restore speed (and some of the log output) is still an issue.
This time i tested with an iPhone XR with iOS 18.7.2:
restore_1762910936.commandpromptoutput.log restore_1762910936.log