encounter / futurerestore

(unmaintained) iOS upgrade and downgrade tool utilizing SHSH blobs (unofficial fork supporting iOS 11 and newer devices)
GNU Lesser General Public License v3.0
176 stars 40 forks source link

Illegal instruction: 4 #11

Open ScknCbt opened 6 years ago

ScknCbt commented 6 years ago

I get this error in my Terminal after i download the new futurerestore_macos_v173.zip I try also with chmod +x futurerestore

MacBookPro:~ User$ cd Downloads/futurerestore_macos_v173/ MacBookPro:futurerestore_macos_v173 User$ ./futurerestore Illegal instruction: 4 MacBookPro:futurerestore_macos_v173 User$ chmod +x futurerestore MacBookPro:futurerestore_macos_v173 User$ ./futurerestore Illegal instruction: 4

encounter commented 6 years ago

What version of macOS? Have you tried redownloading?

ScknCbt commented 6 years ago

The newest version of macOS 10.13.2 I try many times but always the same error

encounter commented 6 years ago

What's the output of otool -L futurerestore?

ScknCbt commented 6 years ago

I wanna try this later today :)

ScknCbt commented 6 years ago

MacBookPro:futurerestore_macos_v173 User$ otool -L futurerestore futurerestore: /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.0.0) /usr/lib/libcurl.4.dylib (compatibility version 7.0.0, current version 9.0.0) /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.5) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1450.15.0) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 400.9.0)

ScknCbt commented 6 years ago

? and whats the problem

encounter commented 6 years ago

Please try the following and see if it works: futurerestore_macos_DEBUG2.zip

ScknCbt commented 6 years ago

the last futurerestore shows the same error

futurerestore: /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.0.0) /usr/lib/libcurl.4.dylib (compatibility version 7.0.0, current version 9.0.0) /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.5) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1450.15.0) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 400.9.0)

encounter commented 6 years ago

What MacBook Pro do you have? There's some CPU incompatibility as far as I can tell.

ScknCbt commented 6 years ago

i have MacBook Pro 13 Mid2012

encounter commented 6 years ago

OK, it looks like the actual issue is a lot more convoluted than I expected. I have a MacBook Air 2011, so I can reproduce the issue on that. It may take a little while to get it working.

encounter commented 6 years ago

Another test build, this one works on my older MacBook as well. Please see if it works for you. futurerestore_macos_DEBUG3.zip

ScknCbt commented 6 years ago

this one works perfect thx bro.

MacBookPro:futurerestore_macos_DEBUG3 User$ ./futurerestore Version: a0113a4e46bfd00962cd25e3af548fc8b0bd21fd - 173 Odysseus Support: no Usage: futurerestore [OPTIONS] /path/to/ipsw

Options:

-t, --apticket PATH APTicket used for restoring -u, --update Update instead of erase install (requires appropriate APTicket) -w, --wait Keep rebooting until nonce matches APTicket (nonce collision, unreliable) -d, --debug Verbose debug output (useful for error logs) --latest-sep Use latest signed sep instead of manually specifying one (may cause bad restore) --latest-baseband Use latest signed baseband instead of manually specifying one (may cause bad restore) --no-baseband Skip checks and don't flash baseband WARNING: only use this for device without a baseband (eg. iPod or some wifi only iPads) --exit-recovery Exit recovery mode and quit

To extract baseband/SEP automatically from IPSW:

-i, --source-ipsw PATH Source IPSW to extract baseband/SEP from

To manually specify baseband/SEP:

-b, --baseband PATH Baseband to be flashed -p, --baseband-manifest PATH BuildManifest for requesting baseband ticket -s, --sep PATH SEP to be flashed -m, --sep-manifest PATH BuildManifest for requesting sep ticket

Homepage: https://github.com/encounter/futurerestore

jmd0x commented 6 years ago

the current release you have doesnt work, please replace it with DEBUG3.

Exormeter commented 6 years ago

Is it save to use the DEBUG3 version to restore an iPhone 7 Plus GSM form 10.1.1 to 11.1.2? I am using a Macbook Pro Mid 2012 Retina with the Intel Core i7 3615QM. The official 173 Version of Futurerestore gives me the same "Illegal instruction: 4" error.

EDIT: Did the restore, worked fine.

ScknCbt commented 6 years ago

@Exormeter i restore my iPad5(6,11) working Perfect with the DEBUG3 Version no errors for me.

theIuser commented 6 years ago

My Mac 10.13.2 gave me an "Illegal instruction: 4" error so I used DEBUG3 and successfully updated my iPhone6 from 10.1.1 to 11.1.2. Thanks @encounter for the update

DaveFlash commented 6 years ago

debug 3 gives me another errror, after illegal instruction: 4" error was cleared up, now get:

Version: a0113a4e46bfd00962cd25e3af548fc8b0bd21fd - 173 Odysseus Support: no [Error] argument parsing failed! agrc=6 optind=3

I'm lost, trying to update my iphone 6 from 9.3.3. jbme site to 11.1.2 on imac mid 2010 with sierra 10.12.6

turned it was at typo. futurerestore is now working for me, my iPhone 6 is now happily runnin' iOS 11.1.2 with Electra....

paduser commented 6 years ago

What terminal commnd did you use?

DaveFlash commented 6 years ago

the one that is needed for the proces, but a dash wash wrong or i had a space where none should be, so I recommend to manually type the command