irecovery error: code=-3

[JEmlay]

Describe the bug Entered recovery mode to detect APNonce which failed and now device is stuck in recovery mode. Tried using Exit Recovery Mode only to get this error - irecovery error: code=-3.

Tried using iMyFone D-Back and Tenorshare ReiBoot and both tools do not detect any device connected to the system.

This happened with two iPads back to back. Seems I have two bricks now? Anyway to fix whatever mode they are in?

Desktop:

• OS Version: Windows 11 Pro 10.0.22631.2428
• iOS Device: iPad Pro Gen 4 & iPad Pro Gen 5

Checklist (place an x between the brackets to mark as completed):

• [ X] I have made sure I am on the latest version of blobsaver
• [ X] I have checked other open issues to see if my problem has already been reported
• [ X] I have tried common troubleshooting tactics such as restarting my computer and reinstalling blobsaver

[airsquared]

Have you checked this wiki page? (especially the part on USB cables/hub)

[JEmlay]

Yes I did. No hubs, cable is fine, tried different port.

I stopped there because I couldn't find irecovery for Windows and the futurerestore github has a nasty warning:

WARNING: DEPRECATED: Please use actions/nightly instead. This build may bootloop your device. It is never a good idea to use old software!

Anyway, I finally found the updated version of futurerestore (I think) and:

futurerestore --exit-recovery Version: v2.0.0-test(ca45da2fb075ccf2921bbc04d5aef74e3e71b743-304) img4tool version: 0.197-aca6cf005c94caf135023263cbb5c61a0081804f-RELEASE libipatcher version: 0.88-1e855d70c84419014e363bdbcaead7b145fe3e1f-RELEASE Odysseus for 32-bit support: yes Odysseus for 64-bit support: yes Exiting from recovery mode to normal mode futurerestore: failed with exception: [exception]: what=can't init, no device found

code=20840491 line=318 file=C:/Users/Cryptic/futurerestore/src/main.cpp commit count=304: commit sha =ca45da2fb075ccf2921bbc04d5aef74e3e71b743:

I also just now tried an A to C cable that I verified is data and power and same thing.

[JEmlay]

Took the iPads to Apple. They are toast. Whatever Blobsaver did they are no longer able to send/receive data over the USB C port. Power, yes. No data. The iPads will simply not communicate anymore. They've been sent in for further diag.

[JEmlay]

They are both toast and Apple cannot explain why. The USB-C port and data connections are fine but iOS is in a state they cannot explain. It will not communicate. Fixing them would require a mainboard change which they don't do as they simply hand out a new unit at the same cost. Over $1,600 later, two new iPads are on their way to me. I'm going to be pissed if they are on 17.1.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you would like this issue to remain open, please comment.