#futurerestore-help
1 messages Ā· Page 66 of 1
here
thanks a lot
this is what apnonce comes out even though i used dimentio to set it to 0x11111111***
I'm really starting to hate the negative feedback of ppl blaming the guis for FRs 'hit and miss' reliability
I haven't had a complaint yet
Everyone who's restored with frgui afaik has succeeded
that's normal
just check if it matches what dimentio says at the end with entangled_nonce
it makes future restore much easier to use. just that im not compatible yet
the GUIs make no difference though
generator is 0x[16 chars], but apnonce is a longer random string that's determined by the generator
All they do is input commands
Actually no
yes it matches @celest basalt
then it's fine
that's awesome!
one last thing
when editing the .shsh file using notepad++ i cannot find generator string or apnonce, just "nononce", is that normal?
There's error parsing with links on how to solve the errors, automatic reboot once on unable to put into recovery so there are less messages in this channel about that, automatically save logs so devs don't have to worry about asking everyone to copy paste logs, etc
There's so much more you can do then just generate a command
blobsaver won't include generator (at least for A12 and above) but it should still be valid
If a GUI is designed to input a command and initiate said execution.. 99% of the fault is on the program it's initiating
Yes ofc
If there is a problem.. It's presented
Frgui next update (or new tool idk) called blob analyzer. Will help solve people with AP nonce / ticket mismatch by setting generator for them and trying a few until it finds the correct ap nonce. So yes, the error is presented, but why don't we help make the issues much easier to solve?
Because the issues aren't the GUI.. It's FR
It's not FR's fault that they didn't set their generator
It's not the generator in most cases
For ap nonce does not match ap ticket? I think it is, what else would it be
It's either FR not succeeding, ibec issues or recovery problems
Oh you mean on the scope of all errors
Ok you do have a point, those are all things FR should fix, not the gui
And ppl are led to believe that it's something the GUI installs which is not the case
FR doesn't detect device for me after it reboots to recovery btw, I have to Ctrl+C and start it again (both Windows and Linux)
Same for everyone, idk anyone who's just worked without having to restart
MacOS here and same issue
So definitely FR's fault
I just hate having to fix something that isn't broken
It is broken though
Ah ok
I mean you could just point people on how to solve the issue through the gui
Point is to make it more user friendly right
People are top hung up to the 90s where you install a program and it comes with everything you need.. Not like today's day and age where updates give you what you need.. And the programs just run off it
Doesn't irestore have a download FR button though, technically it has everything you need ig
Honestly, at this point I'd like to eliminate selecting sep/bb altogether, just auto latest
Yeah but if latest is incompatible
guys
And fr updates the moment it's open
You think FR should auto select the last compatible signed version?
in all honesty i was like fuck it and tried to restore to 14.2 from 13.5 on A13 (11 pro max)
I think the GUIs should look at the sep checker first to certify compatibility prior to using latest
any idea how to get out of recovery or if it's even possible?
Windows 10 moment
futurerestore --exit-recovery
should work since it didn't even send iBEC yet
But my thinking involves more work for a simple app
you're a hero
im just happy the installation process didnt start before it failed lol
do this #futurerestore-help message
but get this version of iTunes: #futurerestore-help message
Ah I see. So something more like you just choose your blob, and the program does the rest?
Indeed
It's tough because sep and bb can't be just checked automatically, I don't think there's an api
but do you think its gonna work anyways? or should i avoid?
I tested it, mine successfully got past iBEC with that
14.2 seems like a hit or miss though but it did work for a bunch of people so idk
I could prolly make one for the checker
hmm
Then the gui can just list it
Yeah but don't you have to input it manually every new iOS version
https://www.apple.com/sepchecker eta wen
i could borrow my sister's mac and try
Yeah, but it's a simple yes or no.. Unlike ipsws they list every little thing
I think Apple would just allow us to downgrade sep before they do that haha
So the api implementation would be iOS whatever.. Yes with latest
And the gui would look at that
What if ios 14.4.2 came out rn though
--latest would be wrong
If 14.4.2 was incompatible
Apple gives about a week leeway to update
So granted the latest did come out.. I'd edit accordingly
There's room for error then
It would need further implementation to seek out what's currently signed which the checker has too
To prevent that, you'd have to have an api for latest signed verified working sep and bb, and you could never use --latest then
Oh you're smart lol
Just see if latest signed is what your checker has and if so, use --latest
Would be a lot of if in the code
It would work though
It'd be iffy (no pun intended) at first, but it'd succeed
I don't see why? Request response would just be "18D66" or whatever and then you could use ipsw me's api to see if it's latest I think
Should be "future" proof (pun intended)
I don't think ipsw me has latest signed
And if somehow you die or something, and your checker is never updated, check with ipswme to see if what your api is saying is even signed.
Before this TV burns out, it'll prolly have Jarvis to do auto updating
Fuck apples restore kernel
Me or cryptic lol
Lil peep
I can assure you TVs may broadcast children, but will never play with one

It was unwise to let jools...
Jools never made me a pfp
@vivid nova and the weird thing is it works some of the time on some devices
Itās like thereās a bug in some seps or Kernels in restore mode
Or a race condition
It would be difficult to create different SEP recognition for separate devices based on what OS when its all the same security. The logic doesn't make sense and would end up putting Apples releases much farther behind imo
It just depends on restoremode entry
This would be like opening up every package of m&ms because you decided to individually wrap each chocolate
For some reason itās using 14.2 to enter restoremode
It should use latest components to load sep
Iāll try that see if it fixes it
Im in a loop how can I stop this
update with itunes
any loop other than respring cant be fixed except itunes restore
I will give it a try
Hello I am getting an error in futurerestore going from 13.5 to 14.3: "Device ApNonce does not match APTicket nonce". My blobs were fine when I started so i dont see what the issue is. :(
Both were 0x1111?
if u use frgui, it should tell u how to fix ur error
upload to https://verify.shsh.host
and screenshot
and use dimentio
to set generator
Im currently on the restore screen on my phone... can I get out of it easily?
recovery mode?
Yes I think so.
futurerestore.exe --exit-recovery
Inb4 "cannot execute program, futurerestore.exe does not exist"
So my blobs are valid though right? And in unc0ver, my generator was already set to 0x1111111, so is dimentio different?
use dimentio
sets bootnonce in nvram
Gotcha. Will report back when that's done.
Although.. Nvram with the latest checkra1n also sets nonce too
true
but not many ppl know how to do that
damn some repos are down
and cydia is being a dick
mhm true
Ironically they know dimentio 0x111... But not nvram apple.System...
Hey Conan.. You're back
the nonce icon is gone
Btw the gui was saying this when I tried to just put my stuff in (without my phone plugged in, just testing)
make sure it mathces
ignore and hit ok

1725873098719278_iPhone10,5_d211ap_14.3-18C66_#####.shsh2
iPhone_5.5_P3_14.3_18C66_Restore.ipsw
To me, the 18C66 matches in both but?
just ignore it like what @lilac wren said
Lol thought that was a troll
yeah I just have a bad regex
no Im the dev of the GUI lol
Gotcha xD
ah i see
hey conan, think you can help. i'm trying to compile dimentio but get this when I run as root
regular dimentio works fine
no but I'm trying to edit it
oh you mean compile the one you have?
im using the one from 0x7ff
Hum. I do have dimentio already installed o_o
ill try
turns out that I already have dimentio installed. I was using TSSSaver from that repo. The generator on TSSSaver is different though.

But the blobs still say 0x1111 :\
set ur generator to 0x111 with dimentio
Iām not sure how to check that 100%
This says 0x1111. Does dimentio have a GUI or terminal where I can see my generator? The blob is set as 0x111 though so Iād imagine it worked
But futurerestore seems to thinks itās not
But TSS Saver says this. Dunno if I need to look at this
to set the generator
ye bc u0 is broken
su
alpine
Just reinstalled it before trying this...
Should I not future restore?
to be fair I saw the repo site said version 2.0.0 and yet i have 2.0.3 but idk if thats something that needs to be looked at.
New error! :P
Oh is this the error -8 that was on the github?
I did those steps in the github but my screen hasnt turned green yet...
it never turns green
only turns green on a7-a10
this has been fixed in v196
that makes sense
it wont print green on >= 0x8015
thats what I added
the warning message included
@sinful spade this the code now
before, it didn't have device check
oh cool so it doesn't give a false warning
that happened to me
because it didn't turn green...
windows?
Is nonceset143 any good?
just use unc0ver
What abt for saving blobs?
System info isnāt working for my 14.0.1 iPad Pro
^ignore that I just realized that Iām probably just on an old version of unc0ver 6
Also, should I keep my generator set to match the blob I used to futurerestore or should I change it back to 0x111111111111?
Why is that even the default?
Can you elaborate on that first part
download libkrw and dimentio from cydia
login as root in newterm
then run
dimentio
command
And that does what?
Oh so specify the apnonce and not just the generator ok
What benefits does that have?

ignore me
it literally makes the blobs useable
u have a10x
oh
@brisk leaf
kek
this is not needed nvm
thought he was 64e
Ok yeah I was confused
just use tsssaver site
yeah
What devices is this necessary for
I have an iPhone 11 Pro
I didnāt do this and my blobs worked fine with futurerestore?
did you use system info
or something
because they do it for you
like tweaks do it for you
Anyway my actual question was if I should save blobs with the generator 0x1111111111111 moving forward instead of whatever systeminfo used
0xdc77cc754eccb488
use whatever the blob says
which will probably be 0xdc77cc754eccb488
since thatās what system info says
Thatās what I did when FRing but moving forward should I use the unc0ver default or what system info uses?
To save
@brisk leaf yah do the apnonce method I said earlier for 11 pro
yeah i just decided to stick with whatever systeminfo wants me to use
it worked so im just not gonna change anything
is systeminfo even updated tho?
dk but its runs fine
on both my ipad pro and iphone 11 pro both on 14
and it seemed to save 14.4.1 blobs perfectly fine
should i have derived new before saving since i future restored tho?
Hi, I was told that earlier someone was helped with FutureRestore on their 11 Pro
I'm the user who made this thread https://www.reddit.com/r/jailbreak/comments/m1luvj/question_missing_generator_in_blobsaver_saved/ and someone there told me they were in the same situation but were able to make it through with help here.
I just want to be absolutely sure whether I'm screwed out of FR before I give up and leave disappointed.
Basically I'm working with blobs that I saved from when I first got my phone up until today. I started saving them when I was unjailbroken, and so my generator was randomized.
FR is completely unusable without the correct generator for the blob to use. Correct?
And if that's the case, given also the thread above, I will not be able to use FR. Is this also correct?
if you werenāt jailbroken when you saved the blobs then you canāt unless you know the generator but even then
idk
you probably are
cant you just find the generator and set it with unc0ver before doing fr?
If I'm at all able to get the correct generator, then set it and reproduce the nonce on my device, then I can use FR, from what I understand about all this
oh you dont know the generator
Can't find the generator, it's not in the blob
Yeah
yeah idrk i cant really help
The generator was random and since I wasn't jailbroken when the blobs were made, the generator cannot be found unless it's brute forced, and the chances of that are incredibly slim
yeah i doubt theres anything you can do then
I'm still almost tempted to at least try it. It's not like I'd be hurting anything by doing that
itll give you a mismatch error if the blob generator is different from the device generator afaik
But you can set a generator and then check the nonce, then set the generator again and check again, etc.
i mean in theory yes
but is it worth it
By this logic, it can be scripted if the right tools are available
Probably not but I still wanna try it
I'm insane like that
fair enough
@empty pollen if you want to bruteforce no need for a script, just use -w flag with fr
uh
it will reboot until apnonce matches
this was used for a7 because a7 had apnonce collisions
not for 14
but hypothetically with enough time it'll work for an A13?
doubt it
lol
sha384
that would take a long time
indeed
with the app im on it spits out the apnonce on the spot
script would be way quicker
alright well
if i was gonna do that
im on 13.5.1 rn trying to get to 14.3
what exactly do i set if im using futurerestore gui?
i mean obviously i know how to set the files i need but what about the baseband and sep?
seems to work for me
not for 14 on arm64e 
u sure?
cuz i have no issues with it and im on a13
oh damn your probably right
i think it just caused a boot loop on my iphone and i cant rejailbreak on my ipad
what do i set baseband and sep to for a 13.5.1 - 14.3 using blobs on A13
no issues until i go to rejailbreak damn
you cant do anything that requires TFP0
cant even restore rootfs
š©
what am i supposed to do
i cant rejailbreak, rejailbreak with load tweaks disabled, or restore root fs
i think system info is the culprit
but doesnt help that unc0ver is being extremely unreliable
i was able to rootfs and rejailbreak on my phone but i still cant on my ipad
its the restore ok ?
what ios/device?
Has the success rate improved on the xs max 13.5
Crap ok
@vivid nova 14.4ā”ļø14.3 IPHONE 7 (GSM)
ok?
I restored with iTunes because stuck
you can downgrade with valid blobs
I did it
cool
has my nonce changed? so this blobs can't be use?
what jailbreak
unc0ver
So if by some chance you mess up and go to 14.4 are you able to go back to 14.3 xs max
@vivid wagon were you jailbroken when you saved blobs
Ok thanks idk if I should risk it or not
no...i was on 13.5.1

no
u wont mess up
Why you say that @valid adder
its pretty high successrate
O ok how long does it take to do everything
I should stay 13.5.1, and wait for 14.4+ jailbreak?
Hi, is it possibile to downgrade my iPhone 7 from iOS 14.4.1 to iOS 14.2? Thanks
Oh, I saved iOS 14.2 SHSH
So when it says get your target blob that's my saved blob correct? and then when it says download the ispw from the target version is that 14.4 or 14.3
Target blobs are the ones you saved, target ipsw is the iOS version you want to go to
ok so basically i have 14.3 blobs saved and then Ill just download 14.3 ipsw as well just wanna make sure I have everything before trying it
Tbh youāre going to need both 14.4 and 14.3 ipsw
ok well I have both already
well I have 14.3 blobs but only 14.3 ipsw im downloading 14.3 ipsw now
You need 14.3 blobs, 14.3 ipsw , 14.4 ipsw
So which one would I name blob.shsh2 and which one will i name target.ipsw since you said I need both ipsw
nah just use --latest args
why install 14.4 ipsw?
To get the info needed. I was under the assumption latest flags didnāt work
@dull swallow which ones do I need I have 14.3 blobs saved already should I continue to download 14.3 ipsw
Your target ipsw is always the version you want to go to
yeah download 14.3 ipsw
Ok im downloading that now
now I used blobsaver to back up my blobs now should I use the nonce from there Im currently on odyssey 13.5
i am assuming so
are you A12+
fuck i hate nonce entanglement
it should be comaptible anyway
yeah just use the 14.3 blob
you have
Ok what about the nonce
use the one that you had set when you saved your blobs
because thats how A12+ works
Aite will do
before saving your blobs you did set a nonce right
and you used blobsaver to get the Apnonce
How would I know if I did it wrong
the restore would non fatally fail
i believe
Hmmm so when I used blob saver I clicked read from device
It has manually specify apnonce checked and it read from device
why are you hiding your apnonce
Idk if I should or not
it literally cant be used for anything lol
O I didnāt know lol
only thing it can be used for is restores kekw
O ok well now I gotta backup my phone
why can I see this anyway lol
tru
what do i set baseband and sep to for a 13.5.1 - 14.3 using blobs on A13
can i save my a14 14.3 blobs through system info??
oh ok
system info doesnt have support for libkrw yet which is a requirement now on unc0ver 6.1.x to set nonce
you can use the TSS Saver application on https://repo.1conan.com
just make sure you install libkrw first
š
tnxxxxx
just use latest flags
is this the section??
yeah system info cant read the generator from the nonce yet on the recent unc0ver
yeah i just gave him the gui to make it easier
depends where you like it saved too
i prefer tsssaver over shsh host
so i set latest for both of them?
yes
thank you
np
do blobs saved in blobsaver work? i was doing some research about matching your device's generator to your blob's
but my blob doesn't have a generator attached to it
no
i dont recommend it
mainly because blobs saved usually dont have generators
just use shsh.host
or tsssaver
oh damn i had used blobsaver for ny 14.2 blobs tho
yeah i know now my 14.4 is with tsssaver
i'm still trying to use the GUI with my 14.2 blob i'll see if it works
it may be fine if your generator was set correctly, but unc0ver 6.x and Odyssey's recent versions both seem to have issues with setting the generator
!t blobs
To save blobs on a jailbroken device, install TSS Saver from https://repo.1conan.com/, then open it and press Save Blobs. (If you're using unc0ver on iOS 14, you'll have to update to 6.1.0 or newer and install libkrw from Cydia before TSS Saver will work.)
For A11 and lower, you can also save blobs without jailbreak on https://tsssaver.1conan.com/v2/ by entering your ECID which you can get from iTunes by clicking the serial number twice. A12 and above requires a jailbreak to start saving blobs.
i know my blob was definitely 0x with 16 1's tho i didnt mess around with it
here's how to test it:
- save 14.4/14.4.1 blobs with TSS Saver right now
- check the apnonce at the end of the filenames on https://tsssaver.1conan.com/
- if it matches the one saved with blobsaver, then your blobsaver blobs are valid
Can I save 14.3 blobs? if I'm on it right now!
install [[System Info]], swipe left on ECID cell and press "APTicket"
rip
http://apt.arx8x.net/ this repo
But can it be saved ? I mean 14.3 ?
it's already unsigned thou
but my phone on 14.3
onboard blobs can be saved, yes
it's a different method of saving than normal
the one System Info saves has a generator so it may be useful, but only while the SEP is compatible
i think it worked
it says 'Done: restoring succeeded!'
i jus wanna confirm
restoring to an itunes backup wont update to 14.4 automatically right?
oh you're already that far ahead, then yeah your blobs were valid
i'm on the hello screen
it won't, but if the backup is from a newer version it will refuse to restore unless you edit the version in the backup (see #common-issues)
yes that should be fine
So why does using SHSH blobs allow us to circumvent Apple servers?
tl;dr: when you want to restore/update firmware, iTunes or the device requests an APTicket from Apple's servers, and they return a digitally signed response
the APTicket has a field called APNonce that's supposed to make it impossible to cache the signed response and perform a replay attack
BUT if you have a jailbreak, you can set the generator that determines the value of the APNonce and fool the device into accepting it
look at my name š the restore worked man damn
Also is there anywhere for me to verify my SHSH blobs? I've been saving them through SysInfo and it's always seemed a bit too easy lol
this one works too
Great, thanks @ripe merlin and @celest basalt
I'm the big sad I tried to go from 14.4 to 14.2 and it almost worked but when it was restoring it just goes back to the recovery
does someone know if ipwndfu works on ubuntu live?
I would guess so, since checkra1n works
cool, ok
you need a mac to restore an a9 via ipwndfu
doesnt work on Ubuntu
guys I'm trying to futurerestore my iPhone X 13.5 to 14.2 but its not working
Everything goes smoothly until the iBEC part, the green doesnt flash green and it fails
IBEC error solution is pinned and the screen wonāt turn green in A11
Do I need to do anything to prep an iPad mini cell for futurerestore? Itās got the matching generator set in uncover. Do i need to uninstall or disable anything ? Im planning on using the new GUI from coocoo
I'm on Big Sur there's no iTunes installed
Going from 13.5 to 14.2
Where can I get the iOS 14.3RC ipsw?
They only have iOS 14.3
which device?
settings>about> copy device model and put it in the ipswme search
Do I need to install nonceEnabler with unc0ver 5.3.1
[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!
Download developer beta versions of Apple's iOS, iPadOS and tvOS firmware.
Is the 14.4.1 sep compatible with 14.2? A12 iPad mini 5
Am I in the wrong place to be asking these questions?
Ok
Thanks
If it fails can I kick it out, or will I be forced to update
you can kick it out
Is it a luck thing? Should I try several times. Or if it wonāt work it wonāt work
Is it worth repeating the process until it works? Or should I give up if it fails.
Repeating wont change the outcome
Ok
I presume best to try 14.4 SEP and baseband over 14.4.1, and to avoid using āālatestā
Oh. Ok. Thanks.
So no risk in trying right? Any other prep I should do to the device prior to pressing start?
Yes Iāve double checked the generator.
Ok thats fine
No
would i be able to downgrade to 14.3?
You need jailbreak to downgrade
oooooh aight whew. i previously jailbroke my device but i had to restore cuz i fucked up something
thanks, almost jumped the gun
You never have to restore
? it was bootlooping
Should I disable find my phone and passwords before?
You dont have to
Thanks
@valid adder if you bootloop an 11 on iOS 13, what is the likeliness of downgrading via FR to 14?
100% if your blobs were red saved correctly with 0x11 set when you saved
I doubt any jailbreak does that automatically
Unc0ver sets it to 0x111111111111111 automatically
Yeah Odyssey doesn't
If you have your blob, open it, and search for the generator value, use that has your nonce, and you should be able to still
So I need a little blob help here.
I just made blobs from onboard .der's (GENERATORLESS THANK GOD) but yeah
1st - how am I supposed to define the APnonce MANUALLY or do I have to crack it with the FR option
2nd - since I do not have a generator there can I just use the generator value for that specific AP?
Report sheet if you ask
Here's a better idea: stay away from 14
(yes I restored to 14.3 since that incident, no fr's)
i dont want the 13.7 incident to happen on 14.3
so im making blobs
What incident?
Bruh
and you prob remember how that ended up
Editing anything is dumb
me wondering how to fakesign the sep and bb for 13.7
So
How am I supposed to know my generator from that AP or how can I set it manually?
Uhhh this is beyond my amazingly limited understanding of futurerestore
Ugh fine understood that my well
generator
its unknown
So should I just use the "APnonce bruteforce" option?
That's probably your best bet
use System Info to dump onboard blobs with a generator
without generator they're useless for futurerestore
It never worked for me
It doesn't show up
it did for me, but never got through a full restore with them yet, even though FR says it's valid
that won't work on any modern SoC
A7 or so was the last where you could do nonce collision in DFU IIRC
oohhh
How do you dump on-board blobs with SysInfo
swipe left on ECID cell, press APTicket
Ohhh that's what that's for
with nonce collision you can do about one per 5 seconds so it would take almost 3 trillion years to hit the right one
on A7 (I think) there was a bug in DFU where it would commonly generate the same few nonces but that doesn't work on newer devices anymore
does sysinfo work for you
that's an outdated version
[[system info]]
So im getting this error
C:\Users\Josh\Desktop>C:\Users\Josh\Desktop\restore\futurerestore-v194.exe -t blob.shsh2 --latest-sep --latest-baseband target.ipsw
Version: 0ab9df3209ee599f581532d05d331e6abe0f53f3 - 194
img4tool version: 0.197-aca6cf005c94caf135023263cbb5c61a0081804f
Odysseus support: no
INFO: device serial number is
[INFO] 64-bit device detected
futurerestore init done
futurerestore: failed with exception:
[exception]:
what=failed to load APTicket at blob.shsh2
code=22282257
line=340
file=futurerestore.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:
Found it ty :D
Do you even have an apticket in your blob 
Did you try to restore with a wrong blob?
well i used blobsaver to sve my blobs so where would i get the apticket
It looks right to me.
Check it for validity
Doesnāt it? You can see it in the shot
Use the blob you have on https://verify.shsh.host and input your device and os data
do I use the same link
Ok
Put the blob in, put the device identifier in, put the version of the blob and well
so it says its valid
Yeah hope it's valid! :D
try again maybe
Wait
Why
Why does your blob say 14.2 but the IPSW says something weird
who me
do you have a fake ipsw or what
yes
get an ipsw from https://ipsw.me
Download current and previous versions of Apple's iOS, iPadOS, watchOS, tvOS and audioOS firmware and receive notifications when new firmwares are released.
no I shouldn't I used my 14.3 blobs
and I donwloaded the 14.3 ipsw
oh you need the most updated one
So why that error?
So my blobs what should I rename it to in my restore folder
whatever you want dont rename it if you want it to be easily identified by identifiers
im not being dumb right? @celest basalt
it saves 5 seconds of your life
the ipsw is supposed to be the most updated one ?
well I renamed it to blob.shsh2
For firmwares yes
For restoring no
ah ok
at best you prefer the older ipsw if 2 are signed
firmware compatibility
@jaunty raft computers are except, you donāt type the exact path it wonāt know where to find it
Welp I'm gonna go sleep now
well I have the restore folder on my desktop
hope you can solve it
You are tying to access blob.shsh2 in desktop because you didnāt provide a full path
You need to do the full path
ok for the command prompt what would I type
cd Desktop
futurerestore-v194.exe -t blob.shsh2 --latest-sep --latest-baseband target.ipsw thats what it says in the tutorial do I add anything extra
Yes
Not sure how you still donāt understand
I just explained what you did wrong
It just has blob.shsh2 without a path
Did u cd in ur folder
That means itās looking in the currently directory
Unless futurerestore and ur blob and ipsw r in the same folder
You are in desktop
U gotta write the directory
Not restore
yes everything is in the same folder
You're not on UNIX how is windows supposed to know the path to the BuildManifest? IPSW? APTicket?
@celest basalt thatās irrelevant
You're missing a BM, add one by using the --latest-manifest tag
well then
Unix doesnāt traverse depth of directories
Heās in desktop so itās looking for blob in desktop
mm i usually use 3 but ok
So do I need to worry about this error?
Just hit ok and hope for the best
I did. Just wants sure if I can ignore it
his blobis 18B92
14.2
I mean like if
its an ipad

whats
Ya. Itās an iPad
@lost stone is ur ipad wifi only
change args to no bb if wifi
No. Itās cell
ah good
yep
ok now it says restoring failed
what=ERROR: Firmware file target.ipsw does not exist.
code=43122705
line=658
file=futurerestore.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:
Done: restoring failed!
now does that mean I didnt correctly say where the target.ipsw is located
need a pig eating bacon... cannibalism
lmao what
wait
are u sure u did everything correctly
I thought I was
its a futurerestore gui how is it fucking up
so I have the restore folder on my desktop with futurerestore in it also I renamed my 14.3 blobs blob.shsh.2 and 14.3 ipsw i renamed it to target.ipsw
so idk what im missing
reselect the files
futurerestore-v194.exe -t blob.shsh2 --latest-sep --latest-baseband target.ipsw so for the -t blob.shsh2 do I put where the file is located and target.ipsw to i type where the file is located
you'd do it like
futurerestore.exe -t "C:\Users\Chris\Documents\iPhone Blobs\blob.shsh2" --latest-sep --latest-baseband "C:\Users\Chris\Documents\iPhone Blobs\target.ipsw"
example of where i had my files located
no use the select function
in the gui
it doesnt need to be in the same folder
i dont think they were the one using the gui š³
mfs when they change the name of files instead of drag-and-drop into CMD
i didnt change the name of the filesss
ok so when I double click future restrore the command promp opens and then closes
it was for simplicity sake

no, but the script did
ur not suppose to do that
just use the select buttons
on the gui
how are u complicating this
i honestly blame the lack of simplicity

why cant fr.exe be opened normally
exactly my point
.exe
bruh
if it was made as an app or cli
.app
.zip

Yāall can call me stupid but this is what it looks like
wasnt that the point of 2 futurerestore guis being released yesterday or 2 days ago
so there was clicky buttons
and dropdown menus
looks good
nothing wrong
so do I double click future restore or what would I do next
lmao nintendo switch
futurerestore-v194.exe -u -t blob.shsh2 --latest-sep --latest-baseband target.ipsw
Worked
its for atmosphere on the switch
ok done that
put your phone in recovery and paste the command i just sent
open the gui
and select the files
how hard could it be
he isnt using the GUI BROOOO
it goes into recovery on its own

how do I open the gui
enjoy 14.2 even tho its not so special- oh wait the chinese gps faker works on it
idfk why he isnt
it won't find the phone in recovery for me until i rerun it
although them using the gui would probably be safer
the same way you open literally any other app
@jaunty raft download the win one
the fact of the matter is they dont have the gui downloaded
i guess with his windows gui i should trash iRestore
because it's literally the same thing
has he unzipped and open the exe yet
he isnt talking so he probably is downloading it and stuff still
either that or they downloaded it opened it
saw the clicky buttons
and used the right files where it said to
not sure why he's not just running the command
like I said
so when using the gui do I need to place my phone in recovery mode or will it do it itself
everything is exact
it should do it itself ?
ok im making sure I have everything set up gonna try now
just put it into recovery or use checkra1n- windows moment
put it into recovery manually as I didn't have luck of fr doing it
smh people having it easy with the --latest-sep --latest-baseband
with the outdated windows tutorial i used ((the op didnt update the post with --latest at the time)) i had to get these myself
Is this correct
Because so far nothing has happened on my phone I am jailbroken using odyssey
did you do the trust prompt
no prompt never showed up

ok
alright hope for the best my friend
yea im crossing my fingers now its checking hashes
alright
ummm i think its stuck on checking hashes im still in recovery mode
just let it run
well looks like i gotta delete itunes and download the other version
ibec error?
yup
this was never an issue on 245
true
is there a way to get v245
Do you need to use the -u flag for futurerestore
it's not compat with ios 14
i wouldn't use it...
o ok
i remember having to do this at like
5am
you shouldn't have to
this is like tearing down your front door because the key doesn't work
is the ability to kick out and return to your device as normal just for the A12 iPad mini 5 in question earlier here, or is the same true for an A13 11PM 13.7? thanks for your time!
13.7 to 14.2?
correct
yea and now my computer is moving slow
14.2 errors are non-fatal
thank you š
which is better 14.2 or 14.3
14.3
alright looks like ima have to go awhile on 13.5 and not have my backup until i get back home to try it again
Since upgrading seems to break setting my apnonce. Is there a fix?
v245 is actually older than v194 (confusing, I know)
i shouldnt have to but i HAD to
because either way my device was wiped completely
my key didnt work because the locksmith left the job unfinished
so i had to kick the door down to get in
@green onyx @zealous bridge @celest basalt we did some crazy shit
lmao what
whats going on
what
sneak peek pls
mhm
lmao ok
yes github
hmm
repo change

by defition im secreitive
true
still have no idea what it is
Oh does it include procursus
š¤Ø
but I will add procursus to ci when its ready
its a repo change itself
github features
Oh my God futurerestore worked the first try
nice
that's what she said
lmao what
did you unplug it and plug it back in @vivid nova š
Managed to fubar myself lol. future restore complained about APNonce mismatch and I can't exit recovery mode via Vol Up/Down and Power until apple logo. Just restarts to the same screen lol. whoops. Guess I'm headed to 14.4! d'oh
no itās fine
just use exit recovery button
its fixable
if youāre using GUI
omg haha i was downloading the 14.4 ipsw now. THANK YOU once again š
roger that
@green onyx @zealous bridge did u find it
the change we made
look at the bar
im looking at ur repos
look at the bar in fr
the bar?
thank you kind folks, seems to be rebooting fine now š . i'll dig into my apnonce mismatch issue and give it another go
im guessing hayden's commits
i saw that
but thats 2 days ago



