You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I've tried to downgrade an iPad Mini 2 a couple of times. I've done both fixes and it has reached a bit farther, but is now presenting this problem.
I have done the sudo codesign command for all but the futurerestore file doesn't go through.
Nonetheless, the problem is that the terminal tells me that device didn't enter DFU Mode, while it's plugged in with DFU Mode. Finder detects it in DFU Mode, not the terminal.
Is there any fixes for this? Please let me know.
Computer Model iMac 9,1 / Mid 2009
MacOS Version macOS 10.15.5 (DosDude patcher [http://dosdude1.com/catalina/]
Python Version Python 3.8.1
Vieux Version 1.0.1
iOS Device (please complete the following information):
REQUIRED -
Device: iPad Mini 2 (4,4)
Desired Version: iOS 10.3.3
The text was updated successfully, but these errors were encountered:
Hi, I was having this problem for a month, but after update my iPad mini 2 for the last iOS 12 version released recently and using the tool leetdown 1.0.5 version it finally worked, on the 5th try the exploited worked, before using either leetdown and vieux tools it wasn’t working, all the time this dfu error, btw I used my hackintosh Mojave version and the frontal usb 2.0 port of my cabinet, if u want try I hope it works for u
Hello, I've tried to downgrade an iPad Mini 2 a couple of times. I've done both fixes and it has reached a bit farther, but is now presenting this problem.
I have done the sudo codesign command for all but the futurerestore file doesn't go through.
Nonetheless, the problem is that the terminal tells me that device didn't enter DFU Mode, while it's plugged in with DFU Mode. Finder detects it in DFU Mode, not the terminal.
Is there any fixes for this? Please let me know.
iOS Device (please complete the following information):
REQUIRED -
The text was updated successfully, but these errors were encountered: