Chimera an error occurred your device could not be jailbroken because the exploit failed

If you’re trying to use the Electra Team’s Chimera jailbreak tool for iOS 12.0-12.1.2 and you’ve had issues jailbreaking your handset – more specifically with the device rebooting after step 2/3 with no successful jailbreak – then you might want to turn your attention to some useful advice offered by Electra Team lead developer CoolStar on Tuesday.

In a Tweet shared early this morning, CoolStar noted that this could happen if your handset was heating up from attempting the jailbreak too many times in rapid succession, and that letting the device cool down slightly before trying again “massively” increases Chimera’s success rate:

According to the recommended actions, users who experience this problem are advised to:

1) Power off device

2) Place device in front of a fan for 30 seconds and let it cool down

3) Power on device and immediately re-jailbreak

It’s worth noting that similar issues can transpire on Pwn20wnd’s unc0ver jailbreak tool as well, and we’ve found that letting the handset cool down shortly after an exploitation attack increases your odds of achieving a successful jailbreak.

As you might come to expect, CoolStar’s Tweet received sarcastic (or possibly serious, but not advisable) comments regarding putting devices in the freezer or using liquid nitrogen to cool the device down more quickly. CoolStar responded to one, recommending against this for concerns of condensation buildup, which can permanently damage your device’s hardware:

All in all, a small fan for airflow or a time out on your desk will help your device cool down safely before you proceed with the jailbreak process again after a failed attempt. So if you were having trouble getting stuck on step 2 out of 3 while attempting your jailbreak, you might want to give this a shot.

Did CoolStar’s advice help you get jailbroken with Chimera? Let us know in the comments section below.

Electra Development Team just released the A12-compatible Chimera jailbreak for iOS 12.0-12.4. Here’s how you can download and install it on your iPhone, iPad, and iPod touch.

What is Chimera?

Chimera is a semi-untethered jailbreak tool for iOS 12.0-12.5 firmware. It is developed and designed by Coolstar, Nullpixel, Alessandro Chiarlitti, and AppleBetas.

Written from the ground up, Chimera is the first “true” jailbreak tool developed for iOS 12.

Unlike unc0ver and other primitive alternatives, it offers full compatibility with devices having the A12/A12X processor (iPhone XS/XS Max, XR, and the new iPad models).    

Chimera is based on Brandon Azad’s voucher_swap exploit for iOS 12 and features a full-blown CoreTrust bypass that ensures the user doesn’t have to resign binaries over and over again. 

Up until now, all major developers have shipped Cydia as the default package manager with their tools.

What sets it apart from other alternatives is the inclusion of Sileo,  a modern Cydia replacement designed for the latest Apple devices, as the default package manager. 

You can grab this tool using the link below. But before you do that, make sure that your device is present in the compatibility list below.

Which devices are supported?

iPhone

• iPhone XS
• iPhone XS Max
• iPhone XR
• iPhone X
• iPhone 8 and 8 Plus
• iPhone 7 and 7 Plus 
• iPhone SE 
• iPhone 6S and 6S Plus
• iPhone 6 and 6 Plus
• iPhone 5S

iPad

• iPad Mini 2
• iPad Mini 3
• iPad Mini 4 
• iPad Air
• iPad Air 2
• iPad (2017) 5th Generation
• iPad (2018)
• iPad Pro (11-inch)
• Third-generation iPad Pro (12.9-inch)

iPod

• iPod touch (6th generation)

All in all, A7 -A11 devices are fully compatible with iOS 12.0-12.4 while A12 devices running iOS 12.0 -12.1.2 are good to go. Unfortunately, Chimera does not support iOS 12.1.3 and later operating systems on A12 devices. 

Download Chimera jailbreak

• v1.6 – (12.0-12.1.4/12.2-12.5)
• v1.6 – (12.0-12.1.4/12.2-12.5)
• v1.5.1 (fat/slim)
• v1.5
• v1.5.0 Beta 1 (fat/slim)
• v1.3.9
• v1.3.8
• v1.3.7
• v1.3.6
• v1.3.4
• v1.3.3
• v1.3.0
• v1.2.6
• v1.2.5 
• v1.2.4
• v1.2.3
• v1.2.2
• v1.2.1
• v1.2.0
• v1.1.0
• v1.0.9
• v1.0.8
• v1.0.7
• v1.0.6
• v1.0.5
• v1.0.4 
• v1.0.3
• v1.0.2
• v1.0.1
• v1.0.0

ChimeraTV

• v1.3.4
• v1.3.3 
• v1.2.2

Changelog

• v1.6.2 – 
  • Fully reliable userspace reboot.
  • Sileo icon now shows up reliably on fresh bootstraps.
  • uicache runs on rootfs restore and removes jailbreak app icons.
  • New Chimera splash screen on userspace reboot.
• v1.6 – Officially verified to work on iOS 12.5 (Chimera v1.5.1 already worked on 12.5).
  • Backports more of Odyssey’s changes to Chimera.
    • the platform-application entitlement is now no longer required for binaries to run.
    • skip-library-validation entitlement is now no longer required for libraries to load into binaries.
    • improves the efficiency and reliability of Chimera.
  • Note: These backported changes were adapted to use kexec [pac bypass], as such Chimera still only supports A12 devices up to iOS 12.1.2.
  • Fixes potential app black screen issue during the jailbreak process.
  • Fixes reliability issues with injecting into launchd during the jailbreak process.
  • Fixes potential post-jailbreak kernel panics on 4K devices (A7/A8) improving the reliability of the jailbreak.
  • jailbreakd plist has been moved to improve compatibility with odysseyra1n (jailbreakd no longer runs or crashes when booted with odysseyra1n).
  • Fixes memory leak and slow performance if jailbreakd is restarted.
  • Experimental support for full userspace reboot.
    • To test userspace reboot you can run launchctl reboot userspace.
    • Userspace reboot should complete in about 15 seconds.
    • Userspace reboot works about 50% of the time (hence the jailbreak itself is still using ldrestart as it’s more reliable).
• v1.5.1 – This fixes some compatibility issues between Chimera and Odysseyra1n:
  • Rejailbreaking an existing Odysseyra1n installation with Chimera will no longer wipe packages database
  • Rejailbreaking an existing Chimera installation with checkra1n (for Odysseyra1n) will have a working read/write filesystem
  • RocketBootstrap from the Odyssey repo will now work correctly on Chimera
  • This also fixes the following additional issues:
    • Exploit selector on iOS 12.2 & 12.4 now works correctly (to allow switching between sockpuppet and life_waste) 
• v1.5.0 Beta 1 –  Adds Procursus/libhooker support to Chimera. The v1.5.0b1 IPA file does not have migration support, so existing users will still have to rely on the stock Chimera bootstrap. New users (and those who perform a rootfs restore) will get Procursus bootstrap and libhooker support.
• v1.3.9 – Improves success rate of SockPuppet 3.0 exploit, especially on 4K devices. 
• v1.3.8 – Fixes error handling of nonce setter on A12 devices on iOS 12.1.3 and above. Fixes an issue with nonce setter on models that haven’t used igetnonce.
• v1.3.7 – Supports setting nonce generator on A12 devices running iOS 12.1.3-12.2 and 12.4.
• v1.3.5 – Improves reliability of SockPuppet exploit, fixes a crash issue.
• v1.3.4 – Fixes random reboots on iOS 12.2 as well as 12.4, fixes Sileo not installing properly on iOS 12.0-12.1.4, adds tvOS 12.2 and 12.4 compatibility to Apple TV.
• v1.3.3 – Replaces SockPuppet and SockPuppet2  with SockPuppet3 exploit, adds support for A7 and A8X devices, all A7-A11 devices (iOS 12.0-12.4) and A12 devices (iOS 12.0-12.1.2) are now compatible. 
• v1.3.0 – Adds support for iOS 12.4 on A8 devices. 
• v1.2.9 – Adds bug fixes and usability improvements to the application.
• v1.2.8 – Adds support for A9-A11 devices running iOS 12.4.
• v1.2.6 – Adds SockPuppet 2.0 to iOS 12.1-12.2 firmware for increased reliability. 
• v1.2.5 – Improves stability on iOS 12.2 firmware, fixes freezing issues on 12.0 – 12.1.x, adds Ned Williamson to in-app credits. 
• v1.2.4 – Adds support for A7/A8 devices running iOS 12.1.3-12.2 and some beta versions of iOS 12.3.
• v1.2.3 – Adds support for iOS 12.3 beta versions (except for iOS 12.3 Beta 6).   
• v1.2.2 – Fixes an issue where v1.2.1 failed to jailbreak A12 devices with the voucher_swap exploit.
• v1.2.1 – Fixes exploit failure on iOS 12.2 devices.
• v1.2.0 – Adds support for iOS 12.1.3-12.2 for A9-A11 devices.
• v1.1.0 – Updates Sileo to version 1.1.5. Fixes Sileo not showing up on the home screen after jailbreak.
• v1.0.9 – Includes several stability fixes and optimizations, updates Sileo package manager to version 1.1.2.
• v1.0.8 – Fixes Sileo icon not showing up after jailbreaking.
• v1.0.7 – Makes re-jailbreaking quicker (4 seconds as compared to 12 seconds in older versions). 
• v1.0.6 – Improves success rate, fixes a bug in v1.0.5 that results in automatic RootFS restore.
• v1.0.5 – Fixes the send bug in Mail, updates Sileo to version 1.0.6, fixes camera bug on A12 devices.
• v1.0.4 – Removes broken SSH toggle in v1.0.3 and replaces it with a working toggle. 
• v1.0.3 – Fixes RocketBootstrap on certain models and updates Sileo to version 1.0.5.
• v1.0.2 – Fixes jailbreak issues with A12X iPad devices.
• v1.0.1 – Fixes voucher_swap exploit in the beta firmware as well as several iPad Pro devices. Reduces the size of IPA file by 32%.
• v1.0.0 – Initial release.

Requirements

• A compatible iPhone, iPad, or iPod touch
• A compatible iOS firmware version 
• A computer running Windows, Linux or macOS (optional)
• Cydia Impactor utility (optional)
• Internet connection

How to jailbreak iPhone XS, XS Max, XR and below with Chimera

With computer

Step 1 Unlock your Apple device and connect it to your computer.

Step 2 Launch Cydia Impactor and ensure it successfully recognizes your device. If you don’t have it installed on your computer, download it from this link. 

Step 3 Download the latest IPA file from the download section above. 

Step 4 Drag this IPA file over to Cydia Impactor to start the installation.

Step 5 Cydia Impactor will now prompt you to enter your username and password. Enter your credentials and hit enter.

Step 6 Wait for the installation to complete. Once done, the app should appear on your home screen. You can disconnect your device from your computer at this point.  

Step 7 Open the stock Settings app and navigate to General > Profiles & Device Management. Select the developer certificate associated with your email address and tap Trust. 

Step 8 Open the Chimera application and hit the Jailbreak button to start the jailbreak process. The spinning wheel 

Step 9 Wait for the exploitation to complete. If the app displays “Reboot Required”, the exploit has succeeded and you will now have to restart your device to complete the jailbreak process.

If your iPhone/iPad restarts before it the spinning wheel completes all the three steps, the exploit has failed. Go back to step 8 and keep trying until the exploit succeeds.

Step 10 Launch Sileo Cydia alternative from the home screen and start downloading your favorite tweaks!

Without computer

Step 1 Open Safari and visit to this website – https://ignition.fun

Step 2 Navigate to the apps section, select Jailbreaks > Chimera.

Step 3 Tap GET and wait for the installation to commence. Once your device displays the installation prompt, press Install to confirm. Wait for the installer to load the app on your device.

Step 4 Go to Settings > General > Profiles & Device Management and trust Ignition’s enterprise certificate. If you are unable to locate the required certificate to trust, simply select the one that’s currently untrusted.

Step 5 Close all open apps from the app switcher and go to your home screen. 

Step 6 Open the Chimera app and hit Jailbreak.

Step 7 Wait for the spinning wheel to complete the required steps. At this stage, you would want to reboot your iPhone or iPad as it is a part of the exploitation process. 

Step 8 Once the app displays “Jailbroken”, your device will be successfully put in jailbreak mode.  

If, for some reason, you are unable to get it working, check out the video given below.

Chimera is available for download on Ignition. Get it before Apple revokes their certificate! #Chimera #jailbreak pic.twitter.com/qcHPFOpSIR

— Yalu Jailbreak (@Yalujb) April 30, 2019

How to re-jailbreak your iPhone, iPad, and iPod 

Since Chimera is a semi-untethered tool, your device will eventually run out of jailbreak juice. The reason being that Apple allows free developer certificates to only sign an app for a period of seven days.

You will no longer be able to use the jailbreak application should you not resign it at regular intervals.

Below is a quick tutorial that outlines how to re-jailbreak your Apple device if you reboot it into the no-jailbreak mode and are unable to use the app.

Step 1 Delete the existing Chimera application from your iPhone XS/XS Max/XR or below.

Step 2 Open Cydia Impactor again and drag the latest IPA file over to it.

Step 3 Enter your credentials and wait for the app to get loaded on your device.

Step 4 Run the app and hit the Jailbreak button.

That’s all there’s to it. If you get stuck anywhere or get hung up on unforeseen issues, feel free to leave a comment below.

Known issues

As of this writing, there are quite a few issues with Chimera, namely –    

• Jailbreaking may fail on the iPad Pro with A12X SoC as well as iOS 12.1.1 Beta 3 firmware.
• PreferenceLoader doesn’t work properly. 

default	19:55:54.635558 +0200	SpringBoard	Injecting /Library/TweakInject/SSLKillSwitch2.dylib
default	19:55:54.637374 +0200	SpringBoard	=== SSL Kill Switch 2: Preference set to 1.
default	19:55:54.637469 +0200	SpringBoard	=== SSL Kill Switch 2: Substrate hook enabled.
default	19:55:54.637646 +0200	SpringBoard	=== SSL Kill Switch 2: iOS 12 detected; hooking SSL_CTX_set_custom_verify() and SSL_get_psk_identity()...
default	19:55:54.657543 +0200	ReportCrash	TweakInject: Loading for binary ReportCrash
default	19:55:54.662192 +0200	ReportCrash	Injecting /Library/TweakInject/RocketBootstrap.dylib
default	19:55:54.662976 +0200	ReportCrash	Trying to create CR directory structure as root
default	19:55:54.668126 +0200	ReportCrash	cr_update: Parsing corpse data for pid 519
default	19:55:54.668181 +0200	ReportCrash	cr_update: Parsing corpse data for process SpringBoard [pid 519]
default	19:55:54.711263 +0200	ReportCrash	__crash_info: [libsystem_c.dylib] 'abort() called'
default	19:55:54.793957 +0200	ReportCrash	Formulating report for corpse[519] SpringBoard
default	19:55:54.796226 +0200	ReportCrash	notify_register_check() failed with error 1000000
default	19:55:54.811379 +0200	ReportCrash	CCMonitor created
default	19:55:54.811603 +0200	CommCenter	#I New CTServerConnection from pid 520 (conn=0x10f0249c0)
default	19:55:54.811694 +0200	CommCenter	#I  -- connection has entitlements: supported=[spi]
default	19:55:54.811871 +0200	CommCenter	#I CTServerConnection from pid 520[ReportCrash] is named 'com.apple.mobilegestalt'.
default	19:55:54.811984 +0200	ReportCrash	libMobileGestalt MGBasebandSupport.c:54: _CTServerConnectionCopyFirmwareVersion: CommCenter error: 1:45 (Operation not supported)
default	19:55:54.812030 +0200	ReportCrash	_CTServerConnectionCopyFirmwareVersion: CommCenter error: 1:45 (Operation not supported)
default	19:55:54.812183 +0200	CommCenter	#I CTServerConnection from pid 520 has closed (conn=0x10f0249c0)
default	19:55:54.825664 +0200	ReportCrash	Saved type '109(109_SpringBoard)' report (5 of max 25) at /var/mobile/Library/Logs/CrashReporter/SpringBoard-2019-07-16-195554.ips
default	19:55:55.318122 +0200	backboardd	             EventStatistics.m:48  :     232.08950:  Info: 3 Digitizer since     230.41501 (Tue Jul 16 19:55:53 2019)
default	19:55:55.420031 +0200	imagent	Client token: IMDaemonWiFiAssertion being removed from WiFi association clients ((null))
default	19:55:57.623958 +0200	wifid	WiFi:[584992557.623693]: __WiFiDeviceManagerLQMEventCallback: null snrNumRef
default	19:55:57.626028 +0200	symptomsd	L2 Metrics on ifname en0: rssi: -61 (txFrames/txReTx/txFail) 0/0/0 -> (was/is) 0/0
default	19:55:58.099040 +0200	UserEventAgent	determinePoSMThreshold, enabled:0 0 1 1
default	19:55:58.099228 +0200	UserEventAgent	determinePoSMThreshold, changed:0 0 0 0
default	19:55:58.099496 +0200	UserEventAgent	determinePoSMThreshold, cmp:4>0 5351>0 963>10000 18>65
default	19:55:58.099696 +0200	UserEventAgent	determinePoSMThreshold,minThreshold=-1 threshold:0 0 -1 -1
default	19:55:58.099855 +0200	UserEventAgent	 POSM running- en=0, th=65535 65535
default	19:55:58.102659 +0200	locationd	{"msg":"adapter details", "adapterDescription":"usb host", "batteryChargerType":"kChargerTypeUsb"}
default	19:55:59.729118 +0200	SpringBoard	TweakInject: Loading for binary SpringBoard
default	19:55:59.729495 +0200	SpringBoard	Entering Safe Mode!
default	19:55:59.730579 +0200	SpringBoard	TweakInject: Entering Safe Mode!

Guide: How to Fix Checkra1n Error 31

by Sophie Green Updated on 2022-10-18 / Update for iCloud

How complicated can it get to fix the checkra1n error 31 ? Not much! All you need is to try out some simple solutions and hopefully one of them will work wonders for you. Discussed below are 5 different methods to resolve the checkra1n error 110 issue.

Method 1: Restart Computer

One of the most common reasons for facing an exploit failed error code 31 windows 10 is a temporary glitch on your computer. To counter this all you need to do is restart your computer on which you are using the Checkra1n.

Method 2: Restart Your Device

Just the way your computer might be suffering a technical glitch, your other devices like iPhones or iPads might be facing the same issue. To resolve this all you need to do is restart your device and check if the issue still persists.

Method 3: Allow Untested Versions and Safe Mode

If restarting your devices did not help then here is another method that might resolve the issue. Here are the steps you need to follow.

• Restart your device.
• Now head to the Checkra1n app option.
• Now select the untested versions and safe mode option.
• Once you are done with this try jailbreaking again

In most cases, this will resolve the issue however if it does not, we still have more methods for you.

Method 4: Use the Old Version of Checkra1n

Even restarting your computer and selecting the safe mode you could not solve your checkra1n error 31iPad mini 2 issue.

No worries, you can try using the old version of Checkra1n. Many Reddit threads give assurance that the former version of Checkra is all you need to solve your checkra1n error 110 issues.

Method 5: Try 4MeKey to Jailbreak Your Device

If none of the methods mentioned above helped you resolve exploit failed error code 31 checkra1n windows, 4MeKey might be just what you need. Tenorshare 4MeKey is a software used to bypass the activation Lock on iOS devices, it is also able to remove the Apple ID which is already login on iOS devices.

Here are basic structures of writing those steps.

Download the Tenorshare 4MeKey software from the official website. Once the download is done, install it on your computer. Open the software and select the option – “Remove iCloud Activation Lock”.

With Tenorshare you can easily jailbreak into your device. Once this is done, the program begins installing the jailbreak tool to your USB drive and this process takes a few minutes to complete.

Next, you can simply start jailbreak and follow the on-screen instructions to jailbreak your device.

You can click on “Start”. You must note that after you bypass the iCloud activation lock you will not be able to use the phone features for phone calls, cellular, and iCloud of your new Apple ID.

The iCloud lock removal process will begin and the activation lock will soon be removed. You can now set up a new account on your device.

The End

Checkra1n error 31 is not an uncommon issue. Many users face it quite often and resolving it is not rocket science. With options like Tenorshare 4MeKey the process becomes even more easy and user-friendly. So? Why are you wasting your precious time? Go on and initiate a smooth jailbreak in your device.

Источник

Exploit failed (Error code: -31) #1058

Comments

DavyJohnes commented Mar 16, 2020 •

Tell us about your setup:

1. What iDevice are you using? — iPhone 5s
2. On what version of iOS is it? — 12.4.5
3. What version of checkra1n are you using? GUI or CLI? — both GUI and CLI, 0.9.8.2
4. What is your host system (OS version? Hackintosh? VM? etc.)? MacOS X 10.15.3
5. How are you connecting to the device (USB-A? USB-C? Apple/3rd party cable? Through a USB hub?)? USB-A Apple cable with adapter to type-c (checked two different adapters, both are not original)

What are the steps to reproduce the issue?

1. Connect newly activated iphone in airplane mode to mac using USB-A cable with type-с adapter
2. Open checkra1n GUI
3. Click Start
4. Follow screen guide to enter DFU

What do you expect, and what is happening instead?
Expect to have my iPhone jailbroken, but see error on «exploiting» step. After accepting error report, checkra1n continue to work, but stucking on «Booting» step, at this moment I can see console output on my iPhone. After a while, checkra1n says «Booting timeout»

Does the issue also occur if you enable Safe Mode?
Yes

Any other info, error logs, screenshots, .

The text was updated successfully, but these errors were encountered:

Источник

error -31 on real mac #255

Comments

brandonstudios commented Nov 12, 2019

What device + iOS version are you on?
iPhone 6 — iOS 12.4.3
What checkra1n version are you using?
checkra1n 0.9.2
What are the steps to reproduce the issue?
1.put phone into dfu mode
2.run checkra1n
3.get this error
.

What do you expect, and what is happening instead?
on checkra1n 0.9.2, i get Exploit failed (error -31), on the console it says [!] Timed out in state 1, assuming we are back to square one with this device. (Error -31). I am on a MacBook4,1 with Yosemite 10.10.5

Any other info, error logs, screenshots, .

The text was updated successfully, but these errors were encountered:

iondarie commented Nov 12, 2019

What device + iOS version are you on?
iPad Air — iOS 12.4.3
What checkra1n version are you using?
checkra1n 0.9.2
What are the steps to reproduce the issue?

1. Put iPad into dfu mode
2. Run checkra1n
3. Get: Exploit Failed (Error code: -31)

Shadowedstalker commented Nov 12, 2019

It’s a matter of keep trying. I had this happen, after a few times and unplugging the device and replugging it it in worked flawlessly.

iondarie commented Nov 12, 2019

Tried al least 20 times even with different cables every time i get the same error.

The exploit seems to run in the end but the device becomes painfully slow and cydia works only once. after that it no longer works.

Shadowedstalker commented Nov 12, 2019

As for the speed I can not speak, but cydia crashing, that I can help with. SSH into the phone via terminal go to var/mobile/library/cydia and delete metadata.cb0. cydia will open again.

drewfissh commented Nov 12, 2019

What device + iOS version are you on?
iPad Air — iOS 12.4.3
What checkra1n version are you using?
checkra1n 0.9.2
What are the steps to reproduce the issue?

1. Put iPad into dfu mode
2. Run checkra1n
3. Get: Exploit Failed (Error code: -31)

Exactly my issue but I encountered it on my iPad mini 2 and everything was fine.

johnwatson122 commented Nov 14, 2019

Hi! I got the same error too several times. So I updated to the latest Mac version available and install all updates from the app store. It worked after that. Maybe you could try that.

Footer

© 2023 GitHub, Inc.

You can’t perform that action at this time.

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.

Источник

iPad mini 2 error -31 #1161

Comments

iceman45575 commented Apr 9, 2020

I’m trying to jailbreak my iPad mini 2 with iOS 12.4.6 but keep getting error -31 after the heap spray screen. I am using the latest version of checkra1n, version 0.10.1. Any way to fix this?

The text was updated successfully, but these errors were encountered:

Pomell123 commented Apr 9, 2020

I am having similar issues. sometimes checkra1n decides to crash on me just after I get the error -31 or I get stuck on the right before trigger part.

Pomell123 commented Apr 9, 2020 •

Hmmm when I tried again but I backgrounded the app while it was jailbreaking and it worked fine??
coincidence?

iceman45575 commented Apr 9, 2020

Mine still doesn’t work 🙁 Are you using an iPad mini 2 as well?

Pomell123 commented Apr 9, 2020

Yes I am using an iPad mini 2

Maybe the A7 chip is still unreliable with checkra1n?

rhld16 commented Apr 9, 2020

It happens for me as well with an iPhone 6s+ iOS 13.3 on a Mac Catalina

nergzd723 commented Apr 9, 2020

rhld16 commented Apr 9, 2020 •

i fixed mine by switching to a less dodgy cable and then trying with safe mode and then without

Siguza commented Apr 9, 2020

I’m going to blindly assume you’re on Linux, and close this as a dupe of #1169.

Pomell123 commented Apr 10, 2020

Sorry but I am using Mac os

iceman45575 commented Apr 10, 2020

I am also using MacOS

nergzd723 commented Apr 10, 2020

You should open new issue if you’re on mac, mac was fixed in 0.10.1 and #1169 is linux-only issue.

Siguza commented Apr 13, 2020

Okay, probably not a dupe of #1169 then.

tigattack commented Jun 8, 2020 •

Also seeing this with checkra1n 0.10.2 on macOS 10.14.16. Checkra1n also crashes after receieving a decision for sending an error report. It crashes regardless of whether I select yes or no.
Update: Works fine if I enter DFU manually and run checkra1n in CLI mode.

nergzd723 commented Jun 8, 2020

Are you using USB-A cable or Type C?

tigattack commented Jun 8, 2020

Lightning to USB-A, going through an Apple dongle to USB-C on my MBP.

nergzd723 commented Jun 8, 2020

Lightning to USB-A, going through an Apple dongle to USB-C on my MBP.

Then you should be fine. Looks like a bug to me, but I don’t have the issue(Mac Mini, iPad mini 2, iPad Air 2)

tigattack commented Jun 8, 2020 •

Certainly seems to be, considering it worked fine through CLI after manually entering DFU, but any combination of methods and settings in the GUI didn’t seem to work. Doubt it was a device issue either, since this was straight after a factory reset on iOS 12.4.7.

ArtemBernatskyy commented Jun 8, 2020

@tigattack thx, it worked!
Here is a detailed tutorial (worked for iPad mini 2, ios 12.4.7, Mac OS High Sierra 10.13.6)

• Install checkra1n
• run in terminal cd /Applications/checkra1n.app/Contents/MacOS && sudo ./checkra1n

Somehow GUI version crashed with -31 error code but cli version combined with sudo worked.

tigattack commented Jun 9, 2020

I did not have to run as root, but I did do ./checkra1n -c , otherewise it would launch as a terminal-based UI rather than purely CLI.

Kunafish1221 commented Jun 30, 2020

what doo you guys mean @tigattack @ArtemBernatskyy @rhld16 @Siguza i dont understand how all that works were and how do i bypass Error Code-31

sarhosbulasikteli commented Jul 5, 2020

@tigattack thx, it worked!
Here is a detailed tutorial (worked for iPad mini 2, ios 12.4.7, Mac OS High Sierra 10.13.6)

• Install checkra1n
• run in terminal cd /Applications/checkra1n.app/Contents/MacOS && sudo ./checkra1n

Somehow GUI version crashed with -31 error code but cli version combined with sudo worked.

it’s works thanks 🙂

fhefh2015 commented Jul 9, 2020 •

@tigattack thx, it worked!
Here is a detailed tutorial (worked for iPad mini 2, ios 12.4.7, Mac OS High Sierra 10.13.6)

• Install checkra1n
• run in terminal cd /Applications/checkra1n.app/Contents/MacOS && sudo ./checkra1n

Somehow GUI version crashed with -31 error code but cli version combined with sudo worked.

Источник

Exploit Failed (error code: -31/-26) #2266

Comments

vxxsp commented Mar 29, 2022 •

Tell us about your setup:

1. What iDevice are you using? iPhone 6S Global
2. On what version of iOS is it? 14.5.1
3. What version of checkra1n are you using? 0.12.4beta
4. What is your host system (OS version? Hackintosh? VM? etc.)? macOS Monterey 12.3beta (OpenCore Legacy Patcher)
5. How are you connecting to the device (USB-A? USB-C? Apple/3rd party cable? Through a USB hub?)? Regular USB-A

What are the steps to reproduce the issue?

1. Jailbreak like normal
2. Shows error Exploit Failed (error code: -31) or (error code: -26)
   .

What do you expect, and what is happening instead?
Should be normally jailbreaking without a hitch

Did you see a popup on the device stating it entered «Safe Mode» due to an error?
Did not get out of DFU

Does the issue also occur if you tick «Safe Mode» in the checkra1n options?
Yes

Any other info, error logs, screenshots, .

The text was updated successfully, but these errors were encountered:

Источник