futurerestore icon indicating copy to clipboard operation
futurerestore copied to clipboard

FDR error when restoring with iOS 11.3b2 sep and baseband

Open toniqyteza opened this issue 7 years ago • 9 comments

LOGS:https://ghostbin.com/paste/9kosd any idea why this happens?

toniqyteza avatar Feb 10 '18 10:02 toniqyteza

I'm looking into it. I have a test device now that I can use to track down the cause.

encounter avatar Feb 12 '18 18:02 encounter

Hey @encounter any progress you had on this? heard you have time constraints, so take your time!

There's 11.3 Beta 3 now!

goodboydheeraj avatar Feb 20 '18 21:02 goodboydheeraj

btw @encounter also tried with sep&& baseband of 11.3b3 and same error.

toniqyteza avatar Feb 23 '18 13:02 toniqyteza

I think this is simply an indication that iOS 11.3 SEP/baseband aren't compatible with iOS 11.0-11.2. It appears that 11.2.6 SEP/baseband is the last chance to restore to those firmwares.

encounter avatar Mar 04 '18 18:03 encounter

But isn’t it weird that it stops at checking filesystem. Maybe 11.3 changes stuff to the filesystem? And the second weird thing is that it bootloops the phone on checking filesystem, which normally it shouldn’t.

toniqyteza avatar Mar 04 '18 18:03 toniqyteza

It is odd, but restoring iOS 11.3b3 with its own SEP/baseband does work properly. It's just the combination with an older firmware that causes issues.

encounter avatar Mar 04 '18 18:03 encounter

I think this is simply an indication that iOS 11.3 SEP/baseband aren't compatible with iOS 11.0-11.2.

Aren't compatible with iOS 11.0 - 11.2.6 tho. Tested restoring 11.2.5/6 on 5s with Baseband and SEP 11.3b2/3, and still failed, stuck on "No data to read" endlessly.

jihyo-song avatar Mar 05 '18 02:03 jihyo-song

Hey, 11.3 has been released! Hope this issue gets resolved soon. Either we need to declare whether 11.3's filesystem structure or SEP whatever isn't compatible with <=11.2.6 or update futurerestore for a proper support to make it understand 11.3!

3 kernel exploit fixed in 11.3! https://support.apple.com/en-us/HT208693

The developer said he would release his CVE-2018-4143 exploit soon... https://twitter.com/derrekr6/status/979438167077130240 But we do not know if it achieves tfp0 :(

So, we need to be sure whether or not to stay on older firmware and update to 11.2.6 later using futurerestore or update to 11.2.6 once he releases his exploit!

goodboydheeraj avatar Mar 29 '18 21:03 goodboydheeraj

Sep isn't compatible

ProAppleOS avatar Mar 29 '18 22:03 ProAppleOS