search

MatthewPierson / Ramiel

An open-source, multipurpose macOS GUI utility for checkm8-vulnerable iOS/iPadOS devices
GNU General Public License v3.0
172 stars 27 forks source link

[Bug] Application hangs after pressing "Run checkm8" on macOS Big Sur 11.3 beta #1

Closed PoomSmart closed 3 years ago

PoomSmart commented 3 years ago

Describe the bug

It is known that macOS Big Sur 11.3 beta breaks checkm8 exploit over USB, for some reasons. For my case, eclipsa8000 binary will never terminate, causing the whole application to hang - just like when running directly from ipwndfu.

The application should at least display an error that the exploit failed to work.

Reference: https://www.reddit.com/r/jailbreak/comments/ldbhfv/news_macos_big_sur_11_beta_3_intel_breaks/

To Reproduce Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots

image

Desktop (please complete the following information):

iOS/iPadOS Device(please complete the following information):

Additional context

Not sure if this information would help. Console app is being spammed with this from Ramiel: ... Ramiel@(null): AppleUSBHostUserClient::start: missing entitlement com.apple.ibridge.control

skyline9394 commented 3 years ago

you are not in pwndfu mode you need enter dfu and then download ipwndfu cd it and enter ./ipwndfu -p after that you can run ramiel

ch0n9waiu commented 3 years ago

After ./ipwndfu -p, ERROR: This device is not supported My device: iphone 8.1 (6s)

you are not in pwndfu mode you need enter dfu and then download ipwndfu cd it and enter ./ipwndfu -p after that you can run ramiel

skyline9394 commented 3 years ago

this error you need wait matty make it support you device

MatthewPierson commented 3 years ago

@PoomSmart v1.0.2 adds in a timeout check for when exploiting the device takes over 30 seconds (30 seconds is a long time but to allow for slow A7 exploitation it needs to be around this long). If the timer hits 30 seconds it'll terminate the task and show an alert informing the user that the exploit timed out. I think this is a good way of dealing with the issue until a proper fix is found for the 11.3 Beta issues. The reason it wasn't displaying an error (when it should have been) was because my code was waiting for the program to return before it checked if it failed or not. This will fix that issue :) Thanks for letting me know about it!