-
Notifications
You must be signed in to change notification settings - Fork 399
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
ERROR: Device did not disconnect. Possibly invalid iBEC. Reset device and try again. #655
Comments
I got the same error with the following debug log when restoring an iPad. #NOTE: No path for component iBEC in TSS, will fetch from build_identity Extracting iBEC.j310.RELEASE.im4p (Firmware/dfu/iBEC.j310.RELEASE.im4p)... |
In my case I can see in the debug it tries to send the iBEC, it doesnt error at all however it looks the device doesnt seem to be responding. I've been using a generic ThunderBolt 4 cable, I praying this is the issue. I've an official apple as the official procedure suggest, early waiting to test it all again with it. |
I've encountered this issue before. After I updated the libirecovery and rebuilt the whole project, the issue was resolved. Hope that would help. |
I've found the reason, I was putting the machine into recovery (not DFU). After setting up dfu correctly, even Apple official tool worked. |
This worked for me as well. After I placed my M2 Macbook in DFU mode, ideviserestore worked seamlessly. The instructions I followed to place my Mac in DFU mode: https://support.apple.com/en-us/108900#preparelaptop |
I am getting this on my 2023 Macbook Pro M2, that machine has the hard-drive wipped and I just wanted to install Somona again.
The text was updated successfully, but these errors were encountered: