search

checkra1n / BugTracker

checkra1n bug tracker
726 stars 104 forks source link

A7 devices require disconnect to progress with checkra1n #1169

Open nergzd723 opened 4 years ago

nergzd723 commented 4 years ago
  1. What iDevice are you using? iPad mini with retina disp
  2. On what version of iOS is it? 12.4.3
  3. What version of checkra1n are you using? beta 10.1
  4. What is your host system (OS version? Hackintosh? VM? etc.)? Ubuntu 18.04
  5. How are you connecting to the device (USB-A? USB-C? Apple/3rd party cable? Through a USB hub?)? Original Apple USB-A to Lightning What are the steps to reproduce the issue?
  6. Run the checkra1n on iPad

  8. ...

What do you expect, and what is happening instead? The same bug, stuck on right before trigger with lots of usbfs errors in kernel log

Does the issue also occur if you enable Safe Mode? Yep.

Any other info, error logs, screenshots, ...? BTW my iPad Air 2 is working, that's the same issue with A7 devices as before.

junetried commented 4 years ago

I can confirm that following @iM4CH3T3's instructions works around the issue.

EDIT: Never mind, it disappears when rebooting the phone.

iM4CH3T3 commented 4 years ago

When phone rebooted once I need more tries and the timing is very important for me at least. As soon as „right before the trigger“ appears I gently unplug and plug in directly again and it starts booting jailbroken... But as I said I need few more tries after phone is rebooted fro Jailbreak ...

iM4CH3T3 commented 4 years ago

I can confirm that following @iM4CH3T3's instructions works around the issue.

EDIT: Never mind, it disappears when rebooting the phone.

What exactly disappears

junetried commented 4 years ago

Whoops, sorry. On my first reboot, the checkra1n app disappeared, and Cydia and Filza did not open (as in, immediately exits) and tweaks were not active. I ran the checkra1n jailbreak again, but nothing changed except now I still had the checkra1n app icon, which obviously didn't actually work.

iM4CH3T3 commented 4 years ago

Sure Nothing works after reboot, it’s a semi tethered=run Checkra1n after every reboot...

zoomer555 commented 4 years ago

My issue was linked here, I already did the unplug and replug, but my phone just reboots with no code execution then goes usbmux errror 79. Anyone here who has the same problem?

doct0r3 commented 4 years ago

I have two 5s ,and one was successfully jailbroken after I unplug and plug it in,but the other （i have used checkra1n 0.9.2 on mac to jail it,but i rebooted it）do not work.

now i think only when you jailbreak ,you see a "dfu sync upload failed",and then unplug will bu succuful. but another 5s doesnt have this error,but only stuck.

zoomer555 commented 4 years ago

Yes i have that error. Sadly when dfusyncupload failed shows the phone has rebooted already

junetried commented 4 years ago

Sure Nothing works after reboot, it’s a semi tethered=run Checkra1n after every reboot...

Late, but my bad! I was under the impression it was untethered. Thanks for clarifying.

ibrahimk157 commented 4 years ago

Hasn’t this been looked into by now? It’s been open for well over a month!

junetried commented 4 years ago

Hasn’t this been looked into by now? It’s been open for well over a month!

It hasn't been closed because it's still an issue.

ibrahimk157 commented 4 years ago

Hasn’t this been looked into by now? It’s been open for well over a month!

It hasn't been closed because it's still an issue.

I am very much aware of that. Was just wondering if it got forgotten about.

Siguza commented 4 years ago

It hasn't. I get an email notification for every reply.
Currently most of us just can't dedicate time to the project, so progress is slow and this won't be fixed in 0.10.2. It will be one of the primary bugs for 0.10.3 though, which I hope we can get out in maybe 2 weeks time.

ibrahimk157 commented 4 years ago

It hasn't. I get an email notification for every reply. Currently most of us just can't dedicate time to the project, so progress is slow and this won't be fixed in 0.10.2. It will be one of the primary bugs for 0.10.3 though, which I hope we can get out in maybe 2 weeks time.

Ah I see, thanks for the clarification and your constant hard work!

MassiveBattlebotsFan commented 4 years ago

What I figured out for the version I used (idk what it was) is that Linux version is very broken. The workaround didn’t work at all. However, on bootra1n, unplugging and replugging the device works.

liamengland1 commented 4 years ago

I just encountered this using checkn1x with an iPhone 5s (Model A1533) on iOS 12.4.7.

gizzmodd commented 4 years ago

The disconnect USB cable is not working for my ipad air, A7, 12.4.7 anymore. I am running Ubuntu 18.04 and the disconnect was working for me before with either checkrain 0.10.1 and 0.10.2 and recently (couple of weeks ago) it stopped working. Any help/ideas on how to fix this? Is this an OS issue (update from Ubuntu)?

Cryptiiiic commented 4 years ago

I don't have a7 here is someone I'm helping's log:

cat checkra1n.log
 - [07/13/20 12:06:09] <Info>: Waiting for DFU devices
 - [07/13/20 12:06:09] <Verbose>: using libusb hotplug API
 - [07/13/20 12:06:09] <Verbose>: DFU device connected: 6b50a569250
 - [07/13/20 12:06:09] <Info>: Exploiting
 - [07/13/20 12:06:09] <Verbose>: Attempting to perform checkm8 on 8960 11...
 - [07/13/20 12:06:09] <Info>: Checking if device is ready
 - [07/13/20 12:06:09] <Verbose>: == Checkm8 Preparation stage ==
 - [07/13/20 12:06:09] <Info>: Setting up the exploit (this is the heap spray)
 - [07/13/20 12:06:09] <Verbose>: == Checkm8 Setup stage ==
 - [07/13/20 12:06:09] <Verbose>: Disabled probabilistic mode since we encountered a partial xfer
 - [07/13/20 12:06:09] <Verbose>: Deterministic approach was successful!
 - [07/13/20 12:07:14] <Info>: Right before trigger (this is the real bug setup)
 - [07/13/20 12:07:14] <Verbose>: Entered initial checkm8 state after 1 steps, issuing DFU abort..
 - [07/13/20 12:07:14] <Verbose>: libusb: waiting for USB events
 - [07/13/20 12:07:15] <Error>: libusb: Failed to get active config descriptor: LIBUSB_ERROR_IO
 - [07/13/20 12:07:16] <Verbose>: DFU device connected: 6b50a569250
 - [07/13/20 12:07:16] <Verbose>: == Checkm8 Trigger stage ==

This is the actual error: <Error>: libusb: Failed to get active config descriptor: LIBUSB_ERROR_IO

SwiftMove commented 4 years ago

@Cryptiiic, the devs are well aware of the issue, unfortunately they just don't know how to fix it. To be honest, I'm really surprised at how s l o w the checkra1n project has come along. Especially with all the COVID drama going on, you'd think people would have plenty of time on their hands to work on these types of projects. But then again, I guess this is just the result of having a project like this "closed source". The wait continues.

phansovanna18 commented 4 years ago

For me iPad mini 3 cellular

on mac

first time it error code -30 second time, it was crashing close checkra1n.

how?

CanerKaraca23 commented 4 years ago

Anyone tested 0.11.0 for it?

daniel071 commented 4 years ago

@CanerKaraca23 Just tested it on 0.11.0 on Manjaro Linux with iPad Mini 2, and the issue is not fixed, its still gets stuck on "Right before trigger" DMESG logs:

[23101.297600] INFO: task checkra1n:30447 blocked for more than 122 seconds.
[23101.297603]       Tainted: G           OE     5.8.9-2-MANJARO #1
[23101.297604] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[23101.297606] checkra1n       D    0 30447  30017 0x00000080
[23101.297609] Call Trace:
[23101.297622]  __schedule+0x2a6/0x810
[23101.297626]  schedule+0x46/0xf0
[23101.297629]  schedule_timeout+0x12d/0x170
[23101.297631]  wait_for_completion_timeout+0x99/0x110
[23101.297637]  usb_start_wait_urb+0xa8/0x190
[23101.297640]  usb_control_msg+0xe7/0x150
[23101.297644]  proc_control+0x199/0x2b0
[23101.297647]  usbdev_ioctl+0xaa2/0x1300
[23101.297652]  ? hrtimer_nanosleep+0xd1/0x1c0
[23101.297657]  ksys_ioctl+0x82/0xc0
[23101.297661]  __x64_sys_ioctl+0x16/0x20
[23101.297663]  do_syscall_64+0x44/0x70
[23101.297666]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[23101.297670] RIP: 0033:0xdcc59e
[23101.297670] Code: Bad RIP value.
[23101.297672] RSP: 002b:00007faca9e0b8d0 EFLAGS: 00000202 ORIG_RAX: 0000000000000010
[23101.297674] RAX: ffffffffffffffda RBX: 000000000000000a RCX: 0000000000dcc59e
[23101.297675] RDX: 00007faca9e0ba90 RSI: ffffffffc0185500 RDI: 000000000000000a
[23101.297676] RBP: 00007faca9e0bb70 R08: 0000000000000000 R09: 0000000000000004
[23101.297677] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000e56800
[23101.297678] R13: 00000000e317c388 R14: 0000000000000040 R15: 0000000000dda6d0
[23105.283492] kauditd_printk_skb: 4 callbacks suppressed

Earlier there was a lot of these errors in dmesg logs:

[22884.052728] apple-mfi-fastcharge 1-3: usbfs: USBDEVFS_CONTROL failed cmd checkra1n rqt 128 rq 6 len 64 ret -110
[22884.062704] apple-mfi-fastcharge 1-3: usbfs: USBDEVFS_CONTROL failed cmd checkra1n rqt 128 rq 6 len 64 ret -110
[22884.072705] apple-mfi-fastcharge 1-3: usbfs: USBDEVFS_CONTROL failed cmd checkra1n rqt 128 rq 6 len 64 ret -110

Even trying to quickly unplug and replug the cable doesn't do anything, it just results in a DFUSyncUpload FAILED error

shellmage commented 3 years ago

trying to jailbreak an iPad 3 mini checkra1n version 11.0 Ubuntu 20.04 fresh iOS 12.4.9 (hello screen) i keep getting "Unable to enumerate USB device" is it a know issue that workaround (unplug-replug) does not work on icloud locked devices?? logs:

3,64988,6042607020,-;INFO: task checkra1n-11:5220 blocked for more than 120 seconds.
3,64989,6042607030,-;      Not tainted 5.4.0-48-generic #52-Ubuntu
3,64990,6042607033,-;"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
6,64991,6042607037,-;checkra1n-11    D    0  5220   5184 0x00000000
4,64992,6042607052,-;Call Trace:
4,64993,6042607066,-; __schedule+0x2e3/0x740
4,64994,6042607070,-; schedule+0x42/0xb0
4,64995,6042607074,-; schedule_timeout+0x10e/0x160
4,64996,6042607079,-; wait_for_completion_timeout+0xab/0x120
4,64997,6042607086,-; ? wake_up_q+0x70/0x70
4,64998,6042607091,-; usb_start_wait_urb+0x8f/0x180
4,64999,6042607095,-; usb_control_msg+0xe3/0x140
4,65000,6042607100,-; proc_control+0x16c/0x2c0
4,65001,6042607105,-; usbdev_do_ioctl+0x9a0/0x1010
4,65002,6042607108,-; ? __schedule+0x2eb/0x740
4,65003,6042607113,-; ? hrtimer_try_to_cancel+0x2c/0x110
4,65004,6042607117,-; usbdev_ioctl+0xe/0x20
4,65005,6042607121,-; do_vfs_ioctl+0x407/0x670
4,65006,6042607124,-; ? hrtimer_nanosleep+0xc2/0x1a0
4,65007,6042607128,-; ksys_ioctl+0x67/0x90
4,65008,6042607131,-; __x64_sys_ioctl+0x1a/0x20
4,65009,6042607137,-; do_syscall_64+0x57/0x190
4,65010,6042607142,-; entry_SYSCALL_64_after_hwframe+0x44/0xa9
4,65011,6042607146,-;RIP: 0033:0xdcc59e
4,65012,6042607155,-;Code: Bad RIP value.
4,65013,6042607157,-;RSP: 002b:00007efd801b28d0 EFLAGS: 00000202 ORIG_RAX: 0000000000000010
4,65014,6042607161,-;RAX: ffffffffffffffda RBX: 000000000000000a RCX: 0000000000dcc59e
4,65015,6042607163,-;RDX: 00007efd801b2a90 RSI: ffffffffc0185500 RDI: 000000000000000a
4,65016,6042607166,-;RBP: 00007efd801b2b70 R08: 0000000000000000 R09: 0000000000000004
4,65017,6042607169,-;R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000e56800
4,65018,6042607172,-;R13: 00000000e317c388 R14: 0000000000000040 R15: 0000000000dda6d0
4,65019,6042607185,-; ? sdhci_drv_exit+0x3f4/0xef4 [sdhci]
7,65020,6060240679,-;usb 2-1.1: usbfs: USBDEVFS_CONTROL failed cmd checkra1n-11 rqt 33 rq 1 len 64 ret -71
 SUBSYSTEM=usb
 DEVICE=c189:201
6,65021,6060303795,-;usb 2-1.1: USB disconnect, device number 74
 SUBSYSTEM=usb
 DEVICE=c189:201
6,65022,6060530906,-;usb 2-1.1: new full-speed USB device number 75 using ehci-pci
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
6,65023,6060690888,-;usb 2-1.1: new high-speed USB device number 76 using ehci-pci
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65024,6065906142,-;usb 2-1.1: unable to read config index 0 descriptor/start: -110
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65025,6065906154,-;usb 2-1.1: can't read configurations, error -110
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
6,65026,6065906432,-;usb 2-1-port1: attempt power cycle
6,65027,6066506940,-;usb 2-1.1: new high-speed USB device number 77 using ehci-pci
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65028,6066535089,-;usb 2-1.1: device descriptor read/8, error 2
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65029,6071794146,-;usb 2-1.1: device descriptor read/8, error -110
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
6,65030,6071978945,-;usb 2-1.1: new high-speed USB device number 78 using ehci-pci
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65031,6077170171,-;usb 2-1.1: device descriptor read/8, error -110
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65032,6082546197,-;usb 2-1.1: device descriptor read/8, error -110
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65033,6082651004,-;usb 2-1-port1: unable to enumerate USB device
6,65034,6088845056,-;perf: interrupt took too long (2507 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
asdfugil commented 3 years ago

trying to jailbreak an iPad 3 mini checkra1n version 11.0 Ubuntu 20.04 fresh iOS 12.4.9 (hello screen) i keep getting "Unable to enumerate USB device" is it a know issue that workaround (unplug-replug) does not work on icloud locked devices?? logs:

3,64988,6042607020,-;INFO: task checkra1n-11:5220 blocked for more than 120 seconds.
3,64989,6042607030,-;      Not tainted 5.4.0-48-generic #52-Ubuntu
3,64990,6042607033,-;"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
6,64991,6042607037,-;checkra1n-11    D    0  5220   5184 0x00000000
4,64992,6042607052,-;Call Trace:
4,64993,6042607066,-; __schedule+0x2e3/0x740
4,64994,6042607070,-; schedule+0x42/0xb0
4,64995,6042607074,-; schedule_timeout+0x10e/0x160
4,64996,6042607079,-; wait_for_completion_timeout+0xab/0x120
4,64997,6042607086,-; ? wake_up_q+0x70/0x70
4,64998,6042607091,-; usb_start_wait_urb+0x8f/0x180
4,64999,6042607095,-; usb_control_msg+0xe3/0x140
4,65000,6042607100,-; proc_control+0x16c/0x2c0
4,65001,6042607105,-; usbdev_do_ioctl+0x9a0/0x1010
4,65002,6042607108,-; ? __schedule+0x2eb/0x740
4,65003,6042607113,-; ? hrtimer_try_to_cancel+0x2c/0x110
4,65004,6042607117,-; usbdev_ioctl+0xe/0x20
4,65005,6042607121,-; do_vfs_ioctl+0x407/0x670
4,65006,6042607124,-; ? hrtimer_nanosleep+0xc2/0x1a0
4,65007,6042607128,-; ksys_ioctl+0x67/0x90
4,65008,6042607131,-; __x64_sys_ioctl+0x1a/0x20
4,65009,6042607137,-; do_syscall_64+0x57/0x190
4,65010,6042607142,-; entry_SYSCALL_64_after_hwframe+0x44/0xa9
4,65011,6042607146,-;RIP: 0033:0xdcc59e
4,65012,6042607155,-;Code: Bad RIP value.
4,65013,6042607157,-;RSP: 002b:00007efd801b28d0 EFLAGS: 00000202 ORIG_RAX: 0000000000000010
4,65014,6042607161,-;RAX: ffffffffffffffda RBX: 000000000000000a RCX: 0000000000dcc59e
4,65015,6042607163,-;RDX: 00007efd801b2a90 RSI: ffffffffc0185500 RDI: 000000000000000a
4,65016,6042607166,-;RBP: 00007efd801b2b70 R08: 0000000000000000 R09: 0000000000000004
4,65017,6042607169,-;R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000e56800
4,65018,6042607172,-;R13: 00000000e317c388 R14: 0000000000000040 R15: 0000000000dda6d0
4,65019,6042607185,-; ? sdhci_drv_exit+0x3f4/0xef4 [sdhci]
7,65020,6060240679,-;usb 2-1.1: usbfs: USBDEVFS_CONTROL failed cmd checkra1n-11 rqt 33 rq 1 len 64 ret -71
 SUBSYSTEM=usb
 DEVICE=c189:201
6,65021,6060303795,-;usb 2-1.1: USB disconnect, device number 74
 SUBSYSTEM=usb
 DEVICE=c189:201
6,65022,6060530906,-;usb 2-1.1: new full-speed USB device number 75 using ehci-pci
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
6,65023,6060690888,-;usb 2-1.1: new high-speed USB device number 76 using ehci-pci
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65024,6065906142,-;usb 2-1.1: unable to read config index 0 descriptor/start: -110
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65025,6065906154,-;usb 2-1.1: can't read configurations, error -110
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
6,65026,6065906432,-;usb 2-1-port1: attempt power cycle
6,65027,6066506940,-;usb 2-1.1: new high-speed USB device number 77 using ehci-pci
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65028,6066535089,-;usb 2-1.1: device descriptor read/8, error 2
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65029,6071794146,-;usb 2-1.1: device descriptor read/8, error -110
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
6,65030,6071978945,-;usb 2-1.1: new high-speed USB device number 78 using ehci-pci
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65031,6077170171,-;usb 2-1.1: device descriptor read/8, error -110
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65032,6082546197,-;usb 2-1.1: device descriptor read/8, error -110
 SUBSYSTEM=usb
 DEVICE=+usb:2-1.1
3,65033,6082651004,-;usb 2-1-port1: unable to enumerate USB device
6,65034,6088845056,-;perf: interrupt took too long (2507 > 2500), lowering kernel.perf_event_max_sample_rate to 79750

icloud lock doesn't matter since it is not intalized yet.

AlphaJack commented 3 years ago

I were able to jailbreak my 12.5 iPhone 5s with Checkra1n 0.12.1 on Manjaro Linux. I was going to record the kernel debug output of my hopeless umpteenth try, but this time it worked for the first time (I used the disconnect in progress workaround). I have uploaded here a video recording of Checkra1n and dmesg -wH, and I also wrote a brief timestamp of what appened during the video. I have tried different versions of Checkra1n multiple times without luck, and I had planned to test Bootra1n after this last attempt would have failed (but instead it didn't). Hope it can help

EDIT:

CanerKaraca23 commented 3 years ago

Any tries on 0.12.4?

MacCraker commented 3 years ago

update: disconnecting and reconnecting device quickly(after watchdog freezes the process) boots to PongoOS and then jailbreak is successful. Maybe it has something with the way that A7 deal with USB?

Didn't work with my iPad Mini 2, so don't expect it to just work on any A7 device. It also somehow made my iPad prompt a no SIM message. Also, my iOS version is 12.5.3, which checkra1n should support.

Jeong-Min-Cho commented 3 years ago 
My System Information
=========================
OS: Ubuntu 20.04.2 LTS
Model: iPad Mini 2 
iOS: 12.5.3
=========================

Alright, so I have successfully managed to jailbreak of my iPad Mini 2.

I was about to give up jailbreaking my iPad because none of solution worked above comments and comments on Reddit as well. However, I somehow made Checkra1n working on my iPad while I was messing around with other versions of Checkra1n.

To be honest, I absolutely have no idea how it exactly worked or the real reasons behind of it. I am just here to share my method to make Checkra1n work, so please do not be mean about me :(.

1. Make sure restart your computer before you begin. I know it sounds boring but you should really restart your computer because you never know your leftover Checkra1n processes might interrupt your work.

2. Type cat /dev/kmsg on your command promt. (Optional) This step is only an optional step to track down the stacks of your linux system so that we can know wheater Checkra1n is frozen or working.

3. Download the following versions: 0.9.8.2, 0.10.1, 0.12.1 If you go to the official Checkra1n website, you can download old versions as well. https://checkra.in/

4. Connect your A7 device

5. Go to the command promt and Execute Checkra1n version 0.9.8.2.

6. You will be stuck at the step "Right before trigger screen"

7. Wait for at least 10 seconds and Check the stacks view to make sure the Checkra1n is frozen.

8. Unplug your cable from your A7 device and plug in back within one or two second(s).

9. Your A7 device will be rebooted, and the Checkra1n will restart the jailbreaking process again. If you are seeing a text "DFUSyncUpload FAILED -1", this is a normal so do not be panic.

9-1. if your A7 device did not reboot automatically, go back to the step 5 do it again.

10. Wait until the jailbreaking process is done. The jailbreak process will fail. This is normal as well.

11. Now, do the same process from the step 5 to step 8 with the version 0.12.1. But, with the version 0.12.1, it will never automatically reboot and restart after the step 8 unlike the version 0.9.8.2. This is the expected behavior.

12. Close the Checkra1n process by pressing Ctrl+Z

13. Execute the Checkra1n with the version 0.10.1.

14. Follow the same steps from the step 5 to step 8.

15. Now, your A7 device will automatically start with jailbreaking processes.

16. Enjoy !

I have tested my method three times by factory resetting my iPad to jailbreak by using Checkra1n.

Thus, I can fairly say that this method is working on my iPad at least, but it could be just me.

Futhermore, I am not totally sure why it worked, but at least I wanted to share my story to the world.

Hopefully, this method works on your A7 device as well.

TheToto318 commented 3 years ago 
My System Information
=========================
OS: Ubuntu 20.04.2 LTS
Model: iPad Mini 2 
iOS: 12.5.3
=========================

Alright, so I have successfully managed to jailbreak of my iPad Mini 2.

I was about to give up jailbreaking my iPad because none of solution worked above comments and comments on Reddit as well. However, I somehow made Checkra1n working on my iPad while I was messing around with other versions of Checkra1n.

To be honest, I absolutely have no idea how it exactly worked or the real reasons behind of it. I am just here to share my method to make Checkra1n work, so please do not be mean about me :(.

1. Make sure restart your computer before you begin. I know it sounds boring but you should really restart your computer because you never know your leftover Checkra1n processes might interrupt your work.

2. Type cat /dev/kmsg on your command promt. (Optional) This step is only an optional step to track down the stacks of your linux system so that we can know wheater Checkra1n is frozen or working.

3. Download the following versions: 0.9.8.2, 0.10.1, 0.12.1 If you go to the official Checkra1n website, you can download old versions as well. https://checkra.in/

4. Connect your A7 device

5. Go to the command promt and Execute Checkra1n version 0.9.8.2.

6. You will be stuck at the step "Right before trigger screen"

7. Wait for at least 10 seconds and Check the stacks view to make sure the Checkra1n is frozen.

8. Unplug your cable from your A7 device and plug in back within one or two second(s).

9. Your A7 device will be rebooted, and the Checkra1n will restart the jailbreaking process again. If you are seeing a text "DFUSyncUpload FAILED -1", this is a normal so do not be panic.

9-1. if your A7 device did not reboot automatically, go back to the step 5 do it again.

10. Wait until the jailbreaking process is done. The jailbreak process will fail. This is normal as well.

11. Now, do the same process from the step 5 to step 8 with the version 0.12.1. But, with the version 0.12.1, it will never automatically reboot and restart after the step 8 unlike the version 0.9.8.2. This is the expected behavior.

12. Close the Checkra1n process by pressing Ctrl+Z

13. Execute the Checkra1n with the version 0.10.1.

14. Follow the same steps from the step 5 to step 8.

15. Now, your A7 device will automatically start with jailbreaking processes.

16. Enjoy !

I have tested my method three times by factory resetting my iPad to jailbreak by using Checkra1n.

Thus, I can fairly say that this method is working on my iPad at least, but it could be just me.

Futhermore, I am not totally sure why it worked, but at least I wanted to share my story to the world.

Hopefully, this method works on your A7 device as well.

Tried your method and still stuck on can't set config #1, error -110 Anyone succesfuly tried to jailbreak their A7 devices recently on linux ?

valbrux commented 2 years ago

I had a lot of issues with this error on my Mac M1. I tried with the old Intel Mac and everything worked fine. Hope that helps!

ntd252 commented 2 years ago

For everyone who doesn't have a Mac machine or can't borrow from friends, I suggest you use ra1nusb instead: https://ra1nusb.thuthuatjb.com/ There are 3 versions and you can try any of them. The basic idea is that it use a MacOS recovery image in USB to create a MacOS environment on non-MacOS machine. This way you can avoid the error which occurs on Linux.

Remember ra1nusb is not really up-to-date with checkra1n (at this moment it supports up to 0.10). You might need to download and copy your specific version to the USB, and execute checkra1n from terminal.

I have tried every checkra1n version on Ubuntu, Linux Mint, Manjaro and they all have the problem at Exploit Failed (Error code: -31). Then I tried ra1nusb and it finally worked.

nightkall commented 2 years ago

For everyone who doesn't have a Mac machine or can't borrow from friends, I suggest you use ra1nusb instead: https://ra1nusb.thuthuatjb.com/ There are 3 versions and you can try any of them. The basic idea is that it use a MacOS recovery image in USB to create a MacOS environment on non-MacOS machine. This way you can avoid the error which occurs on Linux.

Remember ra1nusb is not really up-to-date with checkra1n (at this moment it supports up to 0.10). You might need to download and copy your specific version to the USB, and execute checkra1n from terminal.

I have tried every checkra1n version on Ubuntu, Linux Mint, Manjaro and they all have the problem at Exploit Failed (Error code: -31). Then I tried ra1nusb and it finally worked.

Thanks, It worked perfectly in an iPad Air A1474 (A7) with iOS 12.5.5.

I used Ra1nUSB_HT on an Intel laptop (I had to use an external mouse). I used balenaEtcher to write the .dmg and I had to use the troubleshoot '4. Error hangs when showing 2 lines)'. After booting in macOS, checkra1n 0.12.4 beta (type 124 in Terminal) worked flawlessly.

KGP2006 commented 1 year ago

For everyone who doesn't have a Mac machine or can't borrow from friends, I suggest you use ra1nusb instead: https://ra1nusb.thuthuatjb.com/ There are 3 versions and you can try any of them. The basic idea is that it use a MacOS recovery image in USB to create a MacOS environment on non-MacOS machine. This way you can avoid the error which occurs on Linux. Remember ra1nusb is not really up-to-date with checkra1n (at this moment it supports up to 0.10). You might need to download and copy your specific version to the USB, and execute checkra1n from terminal. I have tried every checkra1n version on Ubuntu, Linux Mint, Manjaro and they all have the problem at Exploit Failed (Error code: -31). Then I tried ra1nusb and it finally worked.

Thanks, It worked perfectly in an iPad Air A1474 (A7) with iOS 12.5.5.

I used Ra1nUSB_HT on an Intel laptop (I had to use an external mouse). I used balenaEtcher to write the .dmg and I had to use the troubleshoot '4. Error hangs when showing 2 lines)'. After booting in macOS, checkra1n 0.12.4 beta (type 124 in Terminal) worked flawlessly.

Can you please guide me from the start?

Leaf5323 commented 5 months ago 
My System Information
=========================
OS: Ubuntu 20.04.2 LTS
Model: iPad Mini 2 
iOS: 12.5.3
=========================

Alright, so I have successfully managed to jailbreak of my iPad Mini 2.

I was about to give up jailbreaking my iPad because none of solution worked above comments and comments on Reddit as well. However, I somehow made Checkra1n working on my iPad while I was messing around with other versions of Checkra1n.

To be honest, I absolutely have no idea how it exactly worked or the real reasons behind of it. I am just here to share my method to make Checkra1n work, so please do not be mean about me :(.

1. Make sure restart your computer before you begin. I know it sounds boring but you should really restart your computer because you never know your leftover Checkra1n processes might interrupt your work.

2. Type cat /dev/kmsg on your command promt. (Optional) This step is only an optional step to track down the stacks of your linux system so that we can know wheater Checkra1n is frozen or working.

3. Download the following versions: 0.9.8.2, 0.10.1, 0.12.1 If you go to the official Checkra1n website, you can download old versions as well. https://checkra.in/

4. Connect your A7 device

5. Go to the command promt and Execute Checkra1n version 0.9.8.2.

6. You will be stuck at the step "Right before trigger screen"

7. Wait for at least 10 seconds and Check the stacks view to make sure the Checkra1n is frozen.

8. Unplug your cable from your A7 device and plug in back within one or two second(s).

9. Your A7 device will be rebooted, and the Checkra1n will restart the jailbreaking process again. If you are seeing a text "DFUSyncUpload FAILED -1", this is a normal so do not be panic.

9-1. if your A7 device did not reboot automatically, go back to the step 5 do it again.

10. Wait until the jailbreaking process is done. The jailbreak process will fail. This is normal as well.

11. Now, do the same process from the step 5 to step 8 with the version 0.12.1. But, with the version 0.12.1, it will never automatically reboot and restart after the step 8 unlike the version 0.9.8.2. This is the expected behavior.

12. Close the Checkra1n process by pressing Ctrl+Z

13. Execute the Checkra1n with the version 0.10.1.

14. Follow the same steps from the step 5 to step 8.

15. Now, your A7 device will automatically start with jailbreaking processes.

16. Enjoy !

I have tested my method three times by factory resetting my iPad to jailbreak by using Checkra1n.

Thus, I can fairly say that this method is working on my iPad at least, but it could be just me.

Futhermore, I am not totally sure why it worked, but at least I wanted to share my story to the world.

Hopefully, this method works on your A7 device as well.

It's been 3 years... 🤔 but the news is, it works for my iPad Air! Seems A7 iPads need some different workarounds from iPhones.Huge thanks for your sharing! As for how and why this would work is still a puzzle though 🤣