-
-
Notifications
You must be signed in to change notification settings - Fork 150
Unable to exit recovery #256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Same with iPhone 12 Pro Max / iOS 14.4.2 Apnonce wasn't retrieved. 👀 |
If you leave your phone connected and blobsaver running, you will be able to manually exit DFU and continue the process. PS. You have to be jailbroken for it to work. |
Does it give an error when it is unable to exit recovery, or does it just silently fail? |
It just keeps waiting for the phone to return (which it doesn't because of the DFU loop) indefinitely without an error. When you manually exit DFU (with another tool) while leaving the phone connected, the process continues and you're actually able to save the blobs. |
I think I've found the problem, please try the latest beta at #242. |
Added in v3.0. |
Thank you for mentioning "iMyFone D-Back". I used it in a Windows KVM passing through my iPad, and it was the only software that was able to exit my iPad Air 3 out of recovery mode (Tried libirecovery on my Linux host and Wondershare Dr.Fone and a few other tools in the Windows VM without success) |
same error java.lang.UnsatisfiedLinkError: Unable to load library 'irecovery': i use imazing exit recover mode. |
See #428, this is a known issue on macOS versions older than Big Sur. |
Describe the bug
Tool version: blobsaver 2.6
OS host: Windows 10
OS client: iOS 14.1
Jailbreak: unc0ver 6.1.2
After successfully reading the ApNonce, the device won't exit recovery mode.
In order to exit recovery mode, I had to use 3rd party software called "iMyFone D-Back". After letting it resolve the issue (while leaving it connected), I was able to continue the process and save the blobs.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop:
Checklist (place an x between the brackets to mark as completed):
Log(s)
The text was updated successfully, but these errors were encountered: