#futurerestore-help
1 messages Ā· Page 71 of 1
I do
alright
Wait how is it different
iPhone10,3,iPhone10,6_14.2_18B92_Restore.ipsw
the error log is the same
just theres no buildidentity stuff
Bc it restarted I think
ah i see
Will the generator be correct?
It should be
recovery
^
this is normal
Its booted at least again fewww
if it works
probably wont work again
I tried the 1st blob
Btw
i have a second one
That was in the conan folder
Should i trie to use that one?
Sorry
I do understand you
It doest work
Thats the think
Ill give it one more shot and see
I think that we can conclude that 14.2 ain't working with future restore.
Right:
@lilac wren
Yes
It goes further when manually putting it in recovery
But as soon as it wants to write to nor
Boom out
@light yew I literally said it doesn't work what more do I need to say????
like I said a 1000 times
its an apple problem
some people can go to 14.2 and lower
others cant
nothing you can do to fix it
I guess reading is not your strongsuit
I know
Just stuborn you know š
Wanna try
Yup same
exactly

With 14.4 not signed, does it change anything for us preparing to get to 14.3 for Tauren release
no
14.4.1 sep and bb should still work to take XS Max to 14.3 correct?
yes
Thanks for reassuring šŗ. I had just finished taking iPad Air 2 and iPhone 6s to 14.3 with 14.4 sep/bb and was just about to start the XS Max. Will grab 14.4.1 parts and get it done
just use --latest
Was looking at marijuanARM's futurerestore github, and noticed the -u says "DO NOT use this parameter, if you update from jailbroken firmware!"
Thought it was alright to go from in my case 13.5 JB and update with -u to 14.3
rootfs before futurerestore i guess?
I think you're fine, others have used itājust rootfs and rejailbreak before you go
sounds good. my thoughts were conflicting because I thought I needed to be JB to have my generator set
I think you can rootfs and have generator set but nobody does that
figured. thanks!
np
Iām āold schoolā, prefer to get the components manually. Itās always worked for me since 11.3 on 4 different devices, why change now
Yeah of course, whatever works best for you! You would need to use 14.4.1 or 14.5 bb and sep then, since 14.4 is unsigned
šš»
because latest already does that and cant go wrong
Curious what would happen if I tried the fr command using unsigned 14.4 components. Would I be forced to restore and lose my JB, or would it fail gracefully and give me another chance?
it will fail to fetch tss lol
the manifest is what is used to fetch tss
tss is hash digest locked not iOS version
so if I use --latest-sep and --latest-baseband I don't specify BuildManifest's?
@zealous bridge I feel so relieved, I think the futurerestore gui logs lagging was only an issue for you (like you said I just blamed it on the gui anyways). Saw two people do it and it looked completely normal, one was on Mac and one was windows. Makes me feel a lot better lol
@solid basin A A RON!
@āCryptic C R YPTIC!
alright! sorry for the confusion then lmao
tho this also happened
so im not sure if its just me lmao
guys
Checkra1n 14.3 RC
password not working and touchid and stuff all fixed
im running 13.3 on ip8+
apparently 14.1 and all is compatible
so im assuming its fixed?
okay? but what's your Q? 'cause it's compatible
no its compatible
but i remember people telling me touch id and all that shit wont work
on 13
14*
noobs
cuz i hvae blobs for everything from 14-14.5 beta 2
no im just asking
so does checkrain still have that issue
cuz i wanna be jailbroken on 14
yes
its not an issue
but u0 works
i need an @finite abyss ...
its not an issue, you need sep exploit for it to work
?
wait wait im still dumb on this topic how did u0 manage it but not cra1n
bruh
considering I'm just a normal jb user yes
i literally don't know half this shit
i just know checkra1n uses a bootrom exploit and u0 another type
you should go brush up on theiphonewiki.com
apple added mitigations with iOS 14 locking bpr in sep
before asking Qs
bpr is the boot process register
tells device what mode it booted from
meaning checkra1n cant boot the os anymore
because sep controls bpr
okay
aye ur a legend for explaining ty
meaning the jailbroken OS right?
no
so due to that you can have the A11 BPR skip but you will lose password functionality and all that good stuff if im not wrong?
if you want a jailbreak, get a X.. it's kinda like a 11/12.. just slower and fewer cameras
checkra1n can boot, but user data isn't decrypted
hence why removing passcode works
cuz no encryption
OH
so its acc more vulnerable
so you have to remove passcode
or else user data is undecrypted
huh
hence why I don't jailbreak
yw
has u0 on 14.1-14.3 been stable for any of you all?
it's not about what OS.. but what you install
Anyone had success trying to FR to 14-14.2 on A11 anyway?
did u send log
I don't remeber
well its a mystery why some devices can go to 14.2
but others cant
I never actually tested a full restore, logs always lagged at the beginning of the process but then went smoothly for me (up until the error bc I wasn't actually going to restore). I thought that was a sign that logs were going to lag throughout the whole thing but maybe not
I saw a success log somewhere in the other server, unsure if that was his
HI
Iphone XS Max IOS 13.5 getting an error when restoring to IOS 14.2
what=Device ApNonce does not match APTicket nonce
code=44498961
code=44498961
line=679
file=futurerestore.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:
Done: restoring failed!
FutureRestore process ended.
did you set your generator
how did you set your generator
Дonfigured with uncover, odyssey and Generator auto setter.
And I always get the error
@worthy trail did you save your blobs specifically for that apnonce
I have blobs saved from IOS 14.2
use dimentio
i thought A11 and up could only update to 14.3 and above
you can try 14.2 it sometimes works
I tried it. Error again
u probably saved ur blobs wrong
Nah u need Conan repo
May be. But on the site https://tsssaver.1conan.com/v2/ they are tested
An online easy to use APTicket / SHSH2 blob saver and checker. SHSH2 blobs are used in unsigned iOS upgrades and downgrades. App available on https://repo.1conan.com
valid != saved properly
sigh
Then rollback on IOS 14.2 does not work for my device
this
Couldnāt Apple simply update SEP (disallowing for a passcode) and / or BB (if applicable) every iOS update instead of intermittently as is the case now to mitigate this. Maybe thereās some kind of technical reason why they donāt prevent replay attacks for iOS but if they cared about limiting jailbreakers; it doesnāt seem too hard to make all SEP / BB updates require matching iOS firmware, right? 
Or did you find out anything new out about this since @lilac wren asked their question?
also
ios is changing updates
theres going to be mainstream updates
and security
so idfk if blobs will only work with mainstream
or will there be security update blobs
or smthn
ah i see
responding to @swift elm or Folky?
I feel like they could, but they'd have to go out of their way, and its really not being used maliciously... someone can't accidentally FutureRestore, activation isn't removed, SEP isn't modified/exploited, etc. I don't think Apple would really take their effort into doing this
So the SEP / BB intermittent updates being incompatible with older versions is never an intent? Just a side effect of new code?
Iām guessing preventing replay attacks is more resource heavy (server side) so they only do it on the exact pieces they deem the most necessary which in this case are other firmwares that are updated uncommonly. Unlike the base OS which is updated frequently.
does futurerestore work on A11 with blobs for 14.1
i think me
Iām thinking of doing a pull request on AltServer to detect the conditions of and automate as much of the TSS blob saving as possible for whatever device. So Iām learning all I can about this right now. Just started jailbreaking as of this week to test out AltDaemon and honestly, jailbreaking is fun af. I canāt believe I thought I was only going to use it for AltDaemon testing.
yes, I doubt they seriously attempt to stop us from futurerestoring every so often
@lilac wren Your write-up was wonderful in my jumping into this world to see if itād make a good candidate as a PR for AltServer.
this sounds correct, not sure about the server part, idk if signing is heavy. but yeah they only update their SEP and BB when they deem necessary, I doubt we make any difference
do remember that you only need to grab that 0x8A3 AES key once per device, I don't think it needs to be running constantly as a server
*while connected to the phone
I just kinda figure if itās preventing a replay attack, they must use some kind of extra resource to do so.
Yeah, thatās the key to the feature. A user only has to plug their phone in a single time.
And AltServer uses the same libraries needed manually to get all the data needed ā I just need to make sure it can detect the phone is in a jailbroken state (for A12 and above) to display the option to āAutomatically save all future blobsā to our users.
is it even necessary to do it with altserver then? the phone can do it all by itself as seen with System Info / shsh.host, or TSS Saver by 1conan. Is altserver just for checking new firmwares and saving SHSH in the background?
how are you going to grab generator? usbmuxd?
and dimentio?
The feature Iām imagining automates (most of) the one-time manual process needed for A12 devices and above (if it detects theyāre jailbroken), otherwise itāll grab all the necessary info during its initial install of AltStore and just make sure it saves new blobs whenever Apple starts signing a new firmware for every device thatās ever connected to that AltServer before.
And for the generator for A12 and above, I have to detect the JB and assume the default unc0ver generator for now.
hm ok, although know that depending on which way you go about this, you'll need to go into recovery on A12+ for getting AP Nonce which is kinda bad if they have to go out of their way to do that. Also know that people who use AltStore are usually not jailbroken at the time of installation, meaning their AP Nonce is going to be randomized and you won't know (if you don't read generator)
if you decide to usbmuxd, then I'd just read generator as well, doesn't take too much extra work
Oh, Iām v new to JB and restoring (obviously not AltStore tho). I thought that wasnāt possible on A12+ for some reason.
I just tried to use futurerestore gui to update my XR from 13.5 to 14.3 but got an apticket apnonce mismatch error
this is the first time I'm not just using itunes to update so I'm very confused
Set your generator
how do I do that?
Iāll make sure this is a one-click thing. It will appear to the user as a button in AltServer drop down and when they click it, it will ārebootā their phone from their perspective but I can grab the APNonce during that ārebootā.
It's not possible to read from computer normally but if you SSH through USB you can just use dimentio to read generator and AP nonce without needing recovery mode
This works on A12+ as long as the user is JB then?
so should I exit recovery mode now?
Download [[dimentio]] through your package manager from 1conan repo, then look in your blob to see if there's a generator, and do dimentio [generator] on your iOS device's terminal
Yes exit recovery
Haven't tried it but I believe it still works so long as you're jailbroken. Definitely won't work if you're not
Gtg eat lunch, but you may wanna read this https://iphonedevwiki.net/index.php/SSH_Over_USB
Right because it requires tftp0.
Don't know of it's still up to date
Thanks for your guidance on this. I really appreciate it! 
I had already restored rootfs so I'm rejailbreaking now
Okay, I think Iāve got it down. For A11 and below I can simply grab all the data needed during initial AltStore install.
A12 and up will save the blobs on the first time a user connects their device in jailbroken mode and AltServer can read the generator.
This makes it perfect for completely automated blob saving.
As to how to convey to users that their blobs are saved and they can use future restore with them would depend on their current firmware which AltServer will also detect.
Is there a master DB / list that is actively maintained of BB and SEP compatible with which iOS versions that AltServer could draw on to display only relevant options to the user?
On iOS 13 and below I think dimentio works out of the box. On iOS 14+, you'd also need libkrw I think
You don't need this since you can only save blobs for signed firmwares which is usually less than 10. You really should only care about this when actually resorting
But if you really want, ping JTV and ask if he has an API
Thatās what Iām referring to. I want AltServer to show and keep up to date what devices can be future-restored to what versions.
Iāll have to find and ask this JTV individual then.
A lot of our user base is jailbreakers.
Don't take this the wrong way but that seems a bit silly, that's really not what AltServer is made for I think. Even all blob savers such as blobsaver, TSS Saver, shsh.host/systeminfo, none of them have sep bb compatibility checking because it doesn't matter
Youāre right that itās not made for that. But I donāt see the harm in removing blobs from users view that are no longer relevant (I wonāt delete them in case they become relevant later but I wonāt display them either). Iāve got approval from Riley to PR this so Iām glad youāre wanting to work it out with me. I at first only wanted this for our JB users. But now I kind of want it for myself.
Correct, api change
Hence why the fortnight bug happened
Maybe, but shsh.host has an api I believe, wouldn't it just be better to save blobs and upload them there? Or you just want to be more user friendly and show which versions they can downgrade to?
I have to look that up. I read that big happened but didnāt see how such a user land app related enough to BB / SEP to crash.
They keybags became corrupted because the new sep handled them differently than the old sep when it did a key update for Face ID/touchid
It cleans every 14 days
A fortnight
So device bootlooped
So that was just SEP incompatibility? There was no fix?
okay, I ran the dimentio command in newterm, should I now restore rootfs again and run futurerestore once more or is there another step?
Thatās correct I just want to show what users can future restore to. A little QoL thing. It wonāt have any functionality.
Fix was turning off passcode or risking bootloop
No need to rootfs more than once, you can try to restore again now
okee, thanks a lot, let's hope it works now
Oh ok sounds cool! Definitely ask JTV if he can make or has made an API then
Is it possible to just disable passcode and use an incompatible SEP then? Or is much more complicated than that
that needs to be fixed first
Does anybody know if this ios.cfw guide for FR is accurate for a13/a14? It was linked on the sub. https://ios.cfw.guide/restoring-to-14-3
yes it looks accurate
I guess it's really just a tutorial for the GUI fork
Step 8 says
Enable the Update (-u) checkbox
@green onyx always said make sure you have the "updateinstall" in your blob before doing it but idk
hmm
yes
open ur blob with notepad
ctrl+f
search updateInstall
if u can find it, u can use -u
if not, u cannot
do you have a source folky
How do i restore if i didnt save blobs
itunes
ok
okay my blob seems to have this!
idk what that actually means but I will check the box for -u in the gui
it means u can update
if you check the -u box your data will be preserved as if you updated
instead of restore
I would always restore but it's up to you
How come?
leftover junk and files, also unc0ver broke ota updates for me when I went from chimera to unc0ver to odyssey without ever restoring
yeah I'd start fresh
So much work but you're probably right
only use iCloud for necessities like contacts and stuff
Is iOS 14.4 sep compatible with 14.1?
uh from what ios version are u restoring
12.1.1
iCloud
X
...
Does it matter?
yes
Why
something with sep
why is it relevant on which version Iām on now, isnāt that related to the signed sep?
no
like for example
A11+ is guaranteed to work on ios 14.3 and above but hit or miss for 14.0, 14.1, and 14.2
A10 and below can fr 14.0+
I upgraded 11.3.1 to 14.4 two days ago, iPhone X
LOL
Why not?
Awesome. One last quick question, since I just looked up JTVās database and itās solely a SEP checker. Do I need to do any extra checking for BB compatibility as well or is SEP enough, you think?
idk, maybe u like having no sep but i dont
In the first blob in the 14.3 folder on TSSSaver, I searched updateInstall, and it showed up.
I think it also shows baseband
although this isn't 100% correct bc of ā¤14.2 on ā„A11
you could just make your own API honestly, JTV does it all manually
In the first blob in the 14.3 folder on TSSSaver, I searched updateInstall, and it showed up.
What does updateInstall in a blob mean?
it means it has an update ticket
so you can use futurerestore without wiping your data
Btw I can always go up to 14.4.1 and go down to 14.3
Itās iPhone X
Oh, sweet, I missed that! I have no problem making my own API but Iād have no choice but to manually add the compatibilities. Maybe I could discuss this with JTV and see their process when I get to the end of the pull request and add this info.
@vivid nova, tho, should definitely be made aware of the 14.2 / A11 detail(s).
Thanks for all your help in this and the Reddit post which inspired me to do this pull request in the first place. 
of course! and good luck
14.1 blobs
This is why I asked about the sep
Is 14.4 sep compatible with 14.1?
Lmao I meant 14.3 not 14.4 š¹
I didnāt get what you didnāt get lol
So is this a gamble?
doesn't really matter because you can just not proceed
Ah got it
So I can just ālatest-sep and it will throw me if not compatible, good to know
latest sep is 14.4.1 sep but I heard itās identical to 14.4
yes it is
I am on 13.5 IPhone X without Blops for 14.3. Is it possible to upgrade to 14.3 without blops since itās no longer being signed? Can I do this through jailbreaking somehow?
no
So I canāt?
you can't without blobs
Hello I am trying to do a restore from 13.5 --> 14.1 using an iPhone 8.
No luck.
It starts restoring with the bar and then fails, is this even possible to upgrade from 13.5?
what's the error
Bear with me -- I will try to replicate
you can send the log here
Done sending NORData
Cleaning up...
[exception]:
what=ERROR: Unable to restore device
what=ERROR: Unable to restore device
code=68026385
code=68026385
line=1038
file=futurerestore.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:
Done: restoring failed!
I don't think you can restore then
I dont have 14.3 blobs unfortunately š¦
How come?
It isnt a big deal anyway - I can stay on 13.5 -- Just wanted to try
something about SEP I think
Its strange sometimes I do it and it fails early on -- other times it nearly finishes the process.
Would I see more success going to 14.5 and downgrading to 14.1?
(I am not overly fussed about losing my jb)
I don't think so
OK.
If I try over and over can I get lucky š
It gets to around something to do with FDR I believe, then it starts panicking
I also get this message which confuses me at the start
I have 14.1 blobs and 14.1 ipsw??
nah you're fine
jank regex I always say "I need to fix that" and never get around to doing it
I have successfully futurerestored wayback when using the normal future restore in terminal, thought id say myself the hassle and use the gui this time. No luck
Might try running it through windows
won't make a difference
It fails at NORData
np
I assume this upgrade/downgrade will never be possible then?
Or is it something that could potentially be 'fixed' at a later point
not possible
Hmm... Iām really debating trying this myself on my 8+
I have ios 11 blobs and im still waiting for the spice unteather jailbreak to be made š
no
@carmine walrus If you have 14.3 blobs I think you're fine
ah, gutted.
wait
I only have 14, 14.1, 14.2, and 14.4 sadly
13.6 right now
ah
go ahead and try it
14.2
fdr isnt fatal
if it doesnt work once, it wont work again
its worth a try
If it doesnāt, Iāll just be on 14.4 right?
Oh?
Backing up my phone now lol
alright
open ur blob with notepad
ctrl+f
search updateInstall
if u can find it, u can use -u
if not, u cannot
@carmine walrus
-u means upgrade
so u dont lose ur data
uh, most modern blob savers have updateInstall
I see <key>updateInstall</key>
yes!
so u can use -u
use frgui
Wow, Iām glad I came here!
no
wtf
u have to be jailbroken
to set generator
tf
u dont need to restore root fs to update
u need to restore root fs if u backup tho
yep
In that case, Iām cancelling this backup lol and will post my log
just want to be sure if this looks right
C:\Users\NAME\FutureRestoreGUI\extracted\futurerestore-v194.exe -t F:\futurerestore\5481104535511086_iPhone10,5_d211ap_14.2-18B92.shsh2 -u -d --latest-sep --latest-baseband F:\futurerestore\iPhone_5.5_P3_14.2_18B92_Restore.ipsw
looks good
here we go! š¤
wait, why arent u using the gui
oh well, ye its good
I copied the command from it
it's fine if he uses terminal lol
oh
thats fine
@carmine walrus check pinned
if u used the gui
it wouldve given u instructions on how to fix
yeah
but solved by restarting the gui
i'll fix
alright pog
gotcha
should I uninstall the Apple Mobile USB driver again?
probably not honestly
@carmine walrus how is it going
did u still get ibec?
it restarted and reconnected but still the same
no ibec
still waiting on message from fdr
how long have u been waiting
~30 min
noooooo
@carmine walrus ctrl + c
worth a try
wait look at your phone, is it with an apple logo and is there a progress bar slowly moving under it
it has the usb under a laptop on the screen
wait you were restoring to 14.0-14.2 on A11+?
Yes iPhone 8 ^
yes, from 13.6 to 14.2 on 8 Plus
is this what it looks like normally when it doesn't work?
I thought it would fully error out
not sure, this my first try
so it doesn't error out, it's just stuck looping like this?
yes
Idk lol
oh ok
Different driver bugs
@green onyx fixed by making it scrollable, https://github.com/JohnnnnyKlayy/FutureRestore-GUI/releases/tag/v1.56
@lilac wren #jailbreak message
oh ok ty
that's from yesterday though >:(
Yay it hit 1k
https://www.reddit.com/r/jailbreak/comments/m0r24m/free_release_futurerestore_gui_a_userfriendly/
995 votes and 124 comments so far on Reddit
fine
yay
oh poggers
Is it possible to downgrade ios 14.3 to 13.7 or 14.3 to 14.0?
Hi guys. Just wanted to ask if someone found a fix for fdr error
No
my iphone is 11 pro max. Is there no method to go back to 13.7 or 14.0? I have all the blobs saved @green onyx
No
- SEP is incompatible
- You need a jailbreak to futurerestore
no
Why
@sleek wing we don't support piracy please stop mentioning that tweak
Doesnt the bot DM
ok sorry
sep is compatible, restoremode is not sep compatible
ik but for the average user wont really make any difference
bc i dont think thats fixable unless?
idk yet
Hi! followed th guide from ios.cfw.guide restoring ip8 global fro 13.5 > 14.3 with blobs, firmware, etc
I get this upon launching FS
As it says
exactly what it says
You have the wrong ipsw
read the error
both have 18C66 in the title
Check the device
link the blob file u used
Did you download the right one for your device?
the ipsw should have your device identifier in the filename
ipsw filename iPhone_4.7_P3_14.3_18C66_Restore.ipsw
should i try the 14.3-ota or 14.3 rc blobs?
ah
just the filename
4614384957038638_iPhone10,4_d201ap_14.3-18C66_27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae.shsh2
Make sure theres nothing in the futurerestore gui folder
Sometimes it auto detects
this ipsw u downloaded?
looks like it
Is that the only ipsw you have downloaded?
Oh hold on
This is a GUI error i think
its detecting āP3ā as the ipsw build
Try renaming the ipsw
No
Its a GUI error
iPhone10,1_14.3_18C66_Restore.ipsw
Rename the ipsw to this ^
look at this carefully
Its detecting āP3ā
as the build name
its def a parsing error
I just have a really bad regex lemme pull it up
let me fix it
.*?_.*?_([0-9A-Z]+)_
That's the regex
Maybe make it take {5}
Since all build numbers are 5
Group 1 (the only group) is the build #
@high rain did you rename your blob before adding it to the gui
There's a way to read the build number from an actual blob right? I'm reading from name but there might be a better way of doing it
Oh this is the IPSW regex sorry I'm confused
yes
[0-9]{16}_.*?_.*?_.*?-([0-9A-Z]+)_ this is the blob regex
Lol
Ipsw regex is the one I put farther above, I'll just find another way to read it
ok didnt get the error this time! currently in dfu mode waiting for device to disconnect
Recovery*
nw
^
ApNonce does not match APTicket nonce
didnt set generator properly
use futurerestore.exe --exit-recovery to exit recovery
or use the exit recovery button
in the gui
.*_([A-Z0-9]{5}) this should work
nah that's too specific imo
true
ok done pushed compiled wrapped and released
a long time
how do I activate it
like 4 months ago?
settings, appearance
I love it, matches IntelliJ
true
it's a shame they don't have auto switching though
bc I have to open Discord while blinded and then switch it to dark every night
yeah you can add some simple css I think and it'll switch automatically
put it manually then
someone else had this issue I think, just do recovery mode manually
like i said before just run again
!t ibec
Fix for error code 3, 8, and 10 aka the iBEC error in futurerestore
- Uninstall all apple drivers via device manager.
- Uninstall all apple products including itunes and apple device support stuff via control panel uninstall a program. MAKE SURE TO CHECK UNINSTALL DRIVER WHEN UNINSTALLING
- Unplug and replug device.
- Check device manager for more apple stuff and uninstall if so with same driver checkbox.
- Disconnect device.
- Install itunes64 exe from apple.com itself, no windows store bullshit. (It will be labeled windows 7, 8 but install it on windows 10, it works fine)
- Plug in device in recovery.
- iboot (recovery) driver should show up under usb in device manager. Uninstall it and check the with software box.
- Run futurerestore.
- Unplug and replug your device.
- Run futurerestore again
if its already in recovery
how do i set nonce?
[[dimentio]]
[[dimentio]]
dimentio, conan repo
generator is whatever is in your blob
0x1111111111111111
thats it then
^
stop using mobile quotes
or it was in the title
thats ecid....
oh oops sorry
0x1111111111111111
thats the right one
oops
wait how do i use dimensio
im not used to this
my first time working on non legacy devices so
follow that ^
ok
Use smart quotes, they look nice, just have a good ide that doesn't put them
"
still wrong
those were pretty straight
mobile just long press
thats what i did...
chose the wrong one maybe
"very smart"
lmao
ur configuring the ota signing service?
nah
just tryna get unc0ver working
doesn't work with any method ive tried
signature is fine tho
do u have a dev acc?
yeh
damn wth
ive been explaining how to fix it on mac for the past 10 minutes
yes
...
can I downgrade to any iOS if I have blobs?
depending if theres a jailbreak available for the version youāre on right now
and on SEP compatibility
what device
iPhone SE 1
yes
14.0
havent been here in a while any news on ios 13.x to ios 14.2 on a11 devices?
no
same as last time you checked probably
ok so I am back š¦ here is what I've done tried, any help would be appreciated: ```
ip 8 gsm on 13.5 going to 14.3. previously on checkra1n
- make sure generator in blob is 0x1[16]
- download correct ipsw
- set generator on iphone in jailbroken state
- run future-restore from command line with ./future -t *.shsh2 *.ipsw --latest-sep --latest-baseband
- get stuck everytime on:
Finished downloading the latest firmware components!
Found device in Normal mode
Entering recovery mode...
ERROR: Failed to place device in recovery mode
futurerestore: failed with exception:
[exception]:
what=Unable to place device into recovery mode from Normal mode
code=9043985
line=138
file=futurerestore.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:
what i have tried (grasping here):
- different usb adapter
- different cable
- add -u to command
- tried 14.3-ota blobs (have the same name)
- tried both blobs in 14.3 (downloaded from TSS)
- tried GUI just for fun
- restored root fs
- re-ran it after I get that error
- windows/linux/osx```
if anyone has any thoughts or ideas, i am open
is your phone actually in recovery or no
it has the phone + laptop icon
and run future restore from that?
yes
nope, good idea, let me try!
iPhone 8 or later: Press and quickly release the Volume Up button. Press and quickly release the Volume Down button. Then, press and hold the Side button until you see the recovery mode screen.
while plugged in to itunes or finder
Identified device as d201ap, iPhone10,4
Extracting BuildManifest from iPSW
Product version: 14.3
Product build: 18C66 Major: 18
Device supports Image4: true
Got ApNonce from device: 27 32 5c 82 58 be 46 e6 9d 9e e5 7f a9 a8 fb c2 8b 87 3d f4 34 e5 e7 02 a8 b2 79 99 55 11 38 ae
Cleaning up...
[exception]:
what=Device ApNonce does not match APTicket nonce
awesome so we figured out the recovery part
now you just need to set the right generator
didnt that happen before too
after running again from recovery
failed to enter recovery isnt the main problem, you dont have the right generator set
they said they used GUI though so I assume it would have given them the popup and they would have realized it's a different issue?
or maybe not lol
they were using cli
i tried both...
used gui once
hm
ok so
troubleshooting this
whats the generator inside your blob?
0x1111... right?
0x1111....yeah.
did you restore rootfs every time before using futurerestore?
no i did not
so youāve tried setting the generator and immediately futurerestoring (without rebooting in between)?
yes
and that is when i get to the failed to put device into recovery
when i do not jailbreak -> set generator
i get the Device ApNonce does not match APTicket nonce
hm wait
when i tell you to run it again
are you taking the device out of recovery?
so like booting it back into normal mode
and after running it again what happens?
ApNonce does not match APTicket nonce
i assue because i am not setting the generator
but honestly, i have no idea
so just to clarify
you set generator > recovery mode error > run again > apnonce error
without any reboots
if you didnāt manually reboot in between setting the generator and the apnonce error then the generator should be set
ok
upload your blob to https://verify.shsh.host and send a screenshot
make sure to blur your ECID
nw
Nobody noticed lol https://www.reddit.com/r/jailbreak/comments/m5qmzh/tutorial_full_futurerestoregui_guide_on/gr2us0d/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3
105 votes and 12 comments so far on Reddit
lmao wtf
nah i noticed
i upvoted u to 2 upvotes

šø
lol
*month
wait is that edit for futurerestore or unc0ver release 
uhh
that apnonce does not look right
wasnt the a11 apnonce for 0x1111... starting with 2735 or smth like that
So were you using the OTA blob this entire time
no, ive tried both
Ok well for now
Set your generator with dimentio and send a screenshot of the output
then immediately after try futurerestore using the 14.3 normal blob and see what happens
It actually was more like 1.5 weeks
ok, so here is what i am going to do (haha, for my sanity):
- jailbreak with checkra1n
- set nonce to 0x1....
- use future restore with 14.3 blob and 14.3 ipsw
should i use the -u flag ?
yes pretty much
Make sure you dont reboot in between thats the main thing
No reason not to
lol i used the 26d as a reference idk why
Oh lol
1 more question: i have 2 blobs under 14.3
4614384957038638_iPhone10,4_d201ap_14.3-18C66_27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae.shsh2
4614384957038638_iPhone10,4_d201ap_14.3-18C66_15400076bc4c35a7c8caefdcae5bda69c140a11bce870548f0862aac28c194cc.shsh2
Use this one
./futurerestore-v194 -u -t 4614384957038638_iPhone10,4_d201ap_14.3-18C66_27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae.shsh2 iPhone_4.7_14.3_18C66_Restore.ipsw --latest-sep --latest-baseband
why is the ipsw there
you should put it at the end of the command
also add the -d parameter at the end
Just after āālatestābaseband
/futurerestore-v194 -u -t 4614384957038638_iPhone10,4_d201ap_14.3-18C66_27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae.shsh2 --latest-sep --latest-baseband -d iPhone_4.7_14.3_18C66_Restore.ipsw
like this?
remove one of the spaces between the blob and the latest sep



