Open AyyItzRob opened 3 years ago
Well, on Intel Mac (11.3) works, but maybe it doesn't work on M1? Is an any process sending usb-request to the device while the tool is running? If a junk request is sent to an iOS device while the tool is running, it fail. Alternatively, it may be possible that there is a problem with the standard OS request on M1 mac + USB Type-C. This is what the checkra1n team has pointed out.
Well, on Intel Mac (11.3) works, but maybe it doesn't work on M1? Is an any process sending usb-request to the device while the tool is running? If a junk request is sent to an iOS device while the tool is running, it fail. Alternatively, it may be possible that there is a problem with the standard OS request on M1 mac + USB Type-C. This is what the checkra1n team has pointed out.
There are no processes sending usb requests to the device. And I got iPwnder32 to execute successfully every single time I ran it back on macOS 11.2. I just now started having these issues starting on macOS 11.3. It shouldn't be an M1 issue if I had it working at one point every time I executed it.
It definitely works on the Intel version. I don't have M1, so if it doesn't work it could be a problem with M1. For example, does Finder get a response when the device reconnects? Catalina or later, it becomes an obstacle to operation.
It definitely works on the Intel version. I don't have M1, so if it doesn't work it could be a problem with M1. For example, does Finder get a response when the device reconnects? Catalina or later, it becomes an obstacle to operation.
Yes, finder gets a response once my device reconnects.
Perhaps that is the cause. Those connections send junk stuff. Please stop it and try again.
Perhaps that is the cause. Those connections send junk stuff. Please stop it and try again.
How would I do so?
Stop 'AMPDevicesAgent' process
&& AMPDeviceDiscoveryAgent
&& AMPDeviceDiscoveryAgent
Terminating these processes changed nothing. Exploit still fails.
Ah, please stop it, not kill.
killall -STOP ...
Ah, please stop it, not kill. killall -STOP ...
Stopping them did nothing either.
Oh, OK. Probably not working on M1 + 11.3 or later. If you want to use it, please use it at 11.2.3 or below.
This is a temporary measure. If the cause is found, it will be fixed. https://github.com/dora2-iOS/iPwnder32/commit/ae26584dc8a1b44b383984d90380c476ed824142
Works on all Intel Mac. Even M1 works fine on Mac mini. This is a problem with Mac with M1 and Type-C ports.
On checkm8.c:238 irecv_usb_control_transfer returns IRECV_E_TIMEOUT on rob's m1 for 5s.
Describe the bug
iPwnder32 fails to pwn dfu on iPhone 5s on macOS 11.3 & 11.3.1 Public Releases. Tested on my iPhone 5s running iOS 12.5.3, with my M1 2020 MacBook Air running macOS 11.3.1 (released earlier today). Also never worked on macOS 11.3. Only worked on macOS 11.2 in my experience. To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected iPwnder to pwn dfu mode my device with 0 issues considering it worked perfectly fine on macOS 11.2 (there wasn't any huge security changes with 11.3 and 11.3.1 coming from 11.2), but instead of saying "successfully entered pwn dfu mode" or whatever it says when it executes successfully, instead I am met with the errors in the screenshot every time I run iPwnder32. libusb and libusbmuxd are installed as well.
Execution environment (please complete the following information):
Target iOS devices (please complete the following information):
Build version of iPwnder32 (please complete the following information):