Open EthanRDoesMC opened 4 years ago
this is happening to me as well, but i'm stuck on the (right before trigger) part
what's the safe way to cancel the jailbreak since it's stuck
just unplug your device and hold lock and home until you see the Apple logo; the exploit doesn’t even run on your device if you’re affected by this glitch
ok thanks
should I try the jailbreak again or should I wait?
Just tried. Doesn't work, I guess using something with intel is the best option right now.
No try this. https://github.com/foxlet/bootra1n/blob/master/README.md
That’s what I was using. That won’t fix the issue.
Haha
@Matt8745 The same problem happens with me too. Using Linux X86/64 CLI on my iphone8 and it gets stuck on the "right before trigger" step forever BTW to restart the machine you just need to click volume+ and then volume- once each and press power button for 10s and it will restart unjailbreaked orz...
Wow sorry bout that.
Sent from my iPhone
On Feb 8, 2020, at 10:28 PM, Himtur notifications@github.com wrote:
@Matt8745 The same problem happens with me too. Using Linux X86/64 CLI on my iphone8 and it gets stuck on the "right before trigger" step forever BTW to restart the machine you just need to click volume+ and then volume- once each and press power button for 10s and it will restart unjailbreaked orz...
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
same thing for me on two A7's so far. i tried repo version on my mini 2 and cli on my 5s. both had te same result. hung 5/8 through the progress bar.
this worked for me: turn off passcode turn off find my idevice plug into mobo directly via a grey USB port install these packages: ideviceinstaller python-imobiledevice libimobiledevice-utils python-plist ifuse usbmuxd libusbmuxd-tools run checkrain as superuser
@kaaskroketde3e what do you mean in the second last step
@Matt8745 run this command: sudo apt install ideviceinstaller python-imobiledevice libimobiledevice-utils python-plist ifuse usbmuxd libusbmuxd-tools
Did u try the method that only boots right to checkra1n on a usb. User name anon password voidlinux? I’ll send u a link if u don’t know what I’m talking about. Worked for me.
Sent from my iPhone
On Feb 10, 2020, at 1:19 AM, Vickronomicon notifications@github.com wrote:
same thing for me on two A7's so far. i tried repo version on my mini 2 and cli on my 5s. both had te same result. hung 5/8 through the progress bar.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
Still occurs on 0.10.2 Tried on both iphone 8 (iOS 13.3.1) and iphone 7 (iOS 12.3.1)
Also tried the suggestions posted by @kaaskroketde3e but with no luck
Also happening here: iPadOS 13.6 (iPad 2017 / 5th gen)
Running latest checkra1n as sudo.
Also tested with one older version (0.10.1), the same.
+1 Hangs on 5/8 of "right before trigger" when trying to jb iPad Air 1 on iOS 12.4.8 (A7). Running v0.11.0 from Arch Linux (installed through AUR package).
Still a problem. Checkra1n, Arch on Ryzen (3100) + B450. Worked perfectly fine on the previous rig (Arch on i5-3330 + H61) :/
Trying this on new version 0.12.3. Issue still present. Stuck on "Setting up the exploit" > "Right before trigger" loop.
Apple iPad 5 WIFI iOS 14.4 connected to motherboard USB port VM with Ubuntu 20, AMD Ryzen 7
Trying this on new version 0.12.3. Issue still present. Stuck on "Setting up the exploit" > "Right before trigger" loop.
Apple iPad 5 WIFI iOS 14.4 connected to motherboard USB port VM with Ubuntu 20, AMD Ryzen 7
For me it worked when I switched from Linux to Mac and did the jailbreak there. I think I read some people haven a problem with Ryzen CPUs in general on Linux.
Tell us about your setup:
What are the steps to reproduce the issue?
What do you expect, and what is happening instead? I expected it to continue with the jailbreak, but it hangs at that message.
Does the issue also occur if you enable Safe Mode? Have not tried, but I would assume yes, given that the exploit never reaches the device.
Any other info, error logs, screenshots, ...? After multiple reboots of both the device and my computer, I tried it on an intel laptop I have. It ran so quickly that I didn’t even see the message that my other system was hanging on. And that laptop is the slowest computer I own. Foxlet said they had narrowed the issue down to 400-Series Ryzen chipsets.