LukeZGD / Legacy-iOS-Kit

An all-in-one tool to restore/downgrade, save SHSH blobs, and jailbreak legacy iOS devices
GNU General Public License v3.0
1.28k stars 117 forks source link

Same issue regardless of what I'm using program for, only with A6 devices. #584

Closed klapanen closed 1 month ago

klapanen commented 1 month ago

I have 3 devices: an iOS 7.0.2 iPhone 5, iOS 8.1.2 iPhone 5c, and iOS 9.3 iPhone 5c. Regardless of what I try to do with what device, I am having the same problem. Tested confirmed working on two A5 devices, exact same things I'm trying to do with these A6 models.

What I've tried: Restarting Phone Restarting Mac 3 Different A6 Devices Different USB Cables Different USB Ports Putting in DFU beforehand and letting program guide me from recovery mode

What I'm trying to do: Jailbreak, save blobs, then downgrade iOS version

The output I'm getting, last pretty substantial amount at least: [checkm8_s5l8950x] running set_global_state() [set_global_state] (1/3) sent: 0, val: 640 [set_global_state] (2/3) e000404f [set_global_state] (3/3) e000404f [checkm8_s5l8950x] reconnecting [checkm8_s5l8950x] running heap_occupation() [heap_occupation] (1/3) e000404f [heap_occupation] (2/3) e0004051 [heap_occupation] (3/3) e0004051 [checkm8_s5l8950x] reconnecting [io_reset] USBDeviceReEnumerate: 0 [checkm8_s5l8950x] ERROR:Failed to reconnect to device [Log] Checking for device ERROR: Unable to connect to device [Error] Failed to enter pwnDFU mode. Please run the script again.

Should note that I did try while successfully in pwnDFU mode and the exact same error happens. Also happens regardless of what exactly I am aiming to accomplish.

Really, this is where it falls apart: [checkm8_s5l8950x] reconnecting [io_reset] USBDeviceReEnumerate: 0 [checkm8_s5l8950x] ERROR:Failed to reconnect to device [Log] Checking for device ERROR: Unable to connect to device [Error] Failed to enter pwnDFU mode. Please run the script again.

I have no idea what in the name of the lord I am doing wrong. Help, please :(

klapanen commented 1 month ago

I'm on a Mac mini running macOS 12.7.6 also, using the most up to date version of the toolkit.

Noticed this reddit user's comment has the same issue as well: https://www.reddit.com/r/LegacyJailbreak/comments/1f5eduo/comment/lktttvv

klapanen commented 1 month ago

Here's a full start to finish output from trying to jailbreak the iOS 7 iPhone 5: Legacy iOS Kit

Saving session... ...copying shared history... ...saving history...truncating history files... ...completed.

[Process completed]

LukeZGD commented 1 month ago

Pushed a test update where you can select ipwndfu instead of ipwnder: https://github.com/LukeZGD/Legacy-iOS-Kit/archive/refs/heads/test.zip

Version should say v24.09.08 (000test)

Test it out and let me know how it goes

klapanen commented 1 month ago

Thanks for such quick response! It didn't fail within terminal at least, and it did boot into an Evasion screen, but when it booted into iOS it was not jailbroken -- no Cydia or Evasion, unless I'm missing something. Log below, insanely long, I'm sorry!

klapanen commented 1 month ago

Log.txt

LukeZGD commented 1 month ago

hmm, does cydia not open thru safari? by going to cydia://

an alternative solution if you are willing to do a restore is to do this: dump onboard blobs by going to save shsh blobs -> onboard blobs. then restore/downgrade using those blobs with jailbreak option enabled

klapanen commented 1 month ago

So, weirdly, it didn't give me an instruction to restart. Once I did, the device got absolutely molasses slow. And, I got a low storage warning. Those things make me think it's jailbroken...ish? But no typing Cydia:// into the safari bar doesn't open it, and still no app.

I will try that. I was struggling badly to extract blobs without being jailbroken, but it was causing the initial issue, so perhaps it will work now.

My end goal is just backing up my 7.0.2 blobs and downgrading to the latest supported version of 6 with a jailbreak on it. The 5c's I would jailbreak, but really they were just sanity checks.

LukeZGD commented 1 month ago

Those seem like the issues that ios 7 users do face when using jailbreak device. So yeah doing the jailbreak thru a restore/downgrade is better in this case

You should be able to do it now that pwndfu is working with ipwndfu, let me know if you encounter any other issues

I'll be closing the issue now and push the update to main

klapanen commented 1 month ago

ipwnder + pwndfu has same issue as initial when doing SHSH blob save as you described.

ipwndfu + pwndfu does not detect 'a device in dfu mode' when doing SHSH blob save as you described.

Have restarted the iPhone and Mac, downloaded latest update, etc. The unplug, plug, unplug, plug doesn't do anything. Phone is clearly in DFU when not being detected as being in DFU.

Putting iPhone in DFU manually/beforehand does not change anything either. iTunes does appropriately detect it.

Log:

Legacy iOS Kit

Saving session... ...copying shared history... ...saving history...truncating history files... ...completed.

[Process completed]

klapanen commented 1 month ago

I've tried 4 or 5x with same result.

klapanen commented 1 month ago

Confirmed exact same result starting from iOS, recovery mode, or DFU mode. Same exact error. Am I supposed to be taking it out & reinserting it both times in the span of 1/2 a second? I never got this error prior, it has always detected the devices in DFU.

LukeZGD commented 1 month ago

Here's the thing: ipwndfu has a lower success rate than ipwnder when it comes to pwning. But with ipwnder having a weird issue on your end that I don't know about, you will have to make do with ipwndfu. The various errors you will get just mean that it failed, including the No Apple device in DFU Mode error you mentioned. What you want is the result that you got earlier in log.txt which was Device is now in pwned DFU Mode. (x seconds)

klapanen commented 1 month ago

I haven't had any success since the jailbreak install that's funky and doesn't have access to Cydia. But, my fear is ruining my install before I get blobs by resetting it. It just seems to be related to that. But, I guess I don't really have another option besides continuing to try, so, I suppose I will keep tying. I'm 12+ hours into this, but I have a forced inability to stop working on a project as I know I will never pick it back up if I don't finish it in a sitting. Here's hoping.

klapanen commented 1 month ago

I really do appreciate your help. It isn't your fault, but there's certainly a good reason I work in hardware repair and typically don't handle SW issues, lol. I like physical objective solutions to things, I'm not one of tremendous patience.