-
Notifications
You must be signed in to change notification settings - Fork 40
FutureRestore error 44 on a Valid APTicket #38
Comments
Me Too! |
Same here. Debug info:
Using ios 11.2.1 => ios 11.3.1 |
Edit the plist found on the 11.3.1 to just display your devices arrays. Also, what command are you using? There are tools for both Mac and windows where you can edit a zip file without decompressing and compressing it again. The problem is that futurerestore checks the BuildManifest.Plist and the first device it sees is iPhone 7. So removing all traces of the iPhone 7 and just focusing on your own device will make futurerestore match your device boardid to your APTicket and come out valid. IPhone 7 didn’t merge with iPhone ipsw intil 11.3 where this all came out. Here is a sample BuildManifest.plist that I used for my successful restore. Edit both plist files from 11.3b6 and 11.3.1 inside the ipsw. This should work! |
I'm using Still failing on the same place. Should I be recompiling 1131.ipsw with a modified BuildManifest? |
Yes you should, and don’t use that command. Use the 11.3b6 files not latest anything :).
…Sent from my iPhone
On Jun 20, 2018, at 4:07 AM, Passive ***@***.***> wrote:
I'm using futurerestore -t blob.shsh2 -d --latest-baseband -p 114BuildManifest-Modified.plist -s 114sep-firmware.d20.RELEASE.im4p -m 114sepManifest-Unmodified.plist 1131.ipsw
Still failing on the same place. Should I be recompiling 1131.ipsw with a modified BuildManifest?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
And then use ./futurerestore -d -t blobs.shsh2 -b baseband_file -p 11.3b6BuildManifest.plist -s 11.3b6sepfile -m BuildManifest.plist 11.3.1.ipsw |
Ah right, Should I be using the same buildmanifest for both or different ones? Also where should I download the beta ipsw from? |
No don’t use the same BuildManifest.plist. They should be separate as the last BuildManifest points to 11.3.1ipsw. I’m only putting names for references. Still call your 11.36b BuildManifest.plist it’s original name |
please use my Build for windows ver v178 |
@xybp888 Was able to get it to actually make it past the error 44, but it ended up failing to install and I've had to update to 11.4 to fix rip |
Any chance I can go from 11.4 backwards? |
11.3b6 |
@PassiveModding tell Me you log this fix -4 error this my log.txt |
@dallasgroot first of tell me how to recompile ipsw with modified build manifest i change in manifest and compress file and change extension in to ipsw and it said the ipsw is courpted, didn’t find the buildManifest.plist from ipsw. How to solve this error. Thanks. |
I'm not going to bother trying for now, No reason risking now that 11.3b6 is unsigned |
Hey there, first off, here is my debug log from future restore
I have an iPhone 8 10,4 D201AP
I've verified my APTicket (shsh2) file using 1conans online checker and comes out valid
when I run the following command
./futurerestore -d -t blobs.shsh2 --latest-baseband -p BuildManifest.plist -s sep-firmware.d201.RELEASE.im4p -m BuildManifest.plist 11.3.1.ipsw
Futurerestore will start doing its thing past the nonce and fails when it checks the apticket telling me it isn't valid, when indeed it is...I searched through the BuildManifest plist file and moved my device to to top and still no luck.... anyone able to help me or know of a fix for this issue?
iPhone 8 11.3b6 - 11.3.1
iOS 11.3b6 Sep
iOS 11.3.1 ipsw
The text was updated successfully, but these errors were encountered: