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
Is your feature request related to a problem? Please describe.
NO
Describe the solution you'd like
Currently flashing firmware with resotre on windows requires libusb to be installed, should I be able to get away with not relying on it if I already have ituens device services installed? For example, idevicerestore.exe is fine, but pymobiledeviace3 still needs to install the libusb driver for the device again.
The idevicerestore is working fine as long as the device service for itunes is installed, would it be possible for pymobiledeviace3 to do the same?
For community
⬇️ Please click the 👍 reaction instead of leaving a +1 or 👍 comment
The text was updated successfully, but these errors were encountered:
libusb is the backend for the USB communication. idevicerestore is statically linked with the same libusb. I don't see any other option
I've roughly skimmed through it, and src/libirecovery.c uses setupapi instead of libusb in windows, so it works fine in windows without relying on libusb.
doronz88
changed the title
FEATURE REQUEST: Wish the restore service on windows didn't depend on libusb
FEATURE REQUEST: Use setupapi when using restore subcommands on windows
Aug 5, 2024
Is your feature request related to a problem? Please describe.
NO
Describe the solution you'd like
Currently flashing firmware with resotre on windows requires libusb to be installed, should I be able to get away with not relying on it if I already have ituens device services installed? For example, idevicerestore.exe is fine, but pymobiledeviace3 still needs to install the libusb driver for the device again.
The idevicerestore is working fine as long as the device service for itunes is installed, would it be possible for pymobiledeviace3 to do the same?
For community
⬇️ Please click the 👍 reaction instead of leaving a
+1
or 👍 commentThe text was updated successfully, but these errors were encountered: