#futurerestore-help
1 messages · Page 215 of 1
@rocky light yes there is a tab for selecting sep/baseband
okay thx!
@vagrant sonnet I only see a log from yesterday
as for the BuildManifest, you specified both --sep-manifest and --baseband-manifest.
In the GUI there is just one cell for importing manifest.. is that for both?
Yeah cause I tried yesterday lol
Didn't try today yet
@vagrant sonnet you didn't try the beta yet
Oh one last question please, should I use the beta for windows?
or it doesn't make a difference
weird
This is with 14.8 SEP / BB, D221AP
@rocky light there is no windows beta lol
oh lol, ok thx
nope nope lol
yep
Windows: Manually fails with that error
While --latest-sep / bb fails with SEP not signed
need to try with Linux on latest futurerestore beta
but maybe @celest basalt already did yesterday?
he has X too
@vagrant sonnet the version of tsschecker in 194 isn't broken tho
yup that is very strange.. I mean. 194 on 14.8 SEP / BB works fine. I mean the whole process goes, it writes filesystem too. Nearly the very end, it complains about that file.
what file
I've read something on Reddit about it, but users loaded the wrong manifest, while I'm sure I used the right one.
this
file
(the reply message)
should I do something with "select build manifest"?
or I shouldn' touch it?
@valid adder
select it.
and load this file
xD
okay
anyways yes, the file it is complaining about is: psi_ram.bin
lol someone trolling the log server
lolol
theres a futurerestore discord btw guys 
@rocky light run it again manually if it fails again
another bug I fixed a long time ago right after 194
i should hold the power and home button at the same time right?
recovery is home when device turns on I think
hard reset, let go of all, hold home button for 20 seconds or until you see itunes logo
is it normal to take time in "checking hashes"?
so, I'm fucked here?
nah leave it for a few minutes
ok
the restore hasn't even failed anyway
what happens if it fails?
its normal
let it do its work
will I have ti restore to 14.8?
you can downgrade unlimited
if it fails, it won't boot up at all
so yea you need to flash ipws
ipsw*
i got ibec error
a.a
!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. This is the best version: https://support.apple.com/kb/DL1816?locale=en_US (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
these commands which save 14m of writing
+1
store version is irrelevant
so my phone won't boot up if i try now?
Its probably an api change, If I ever get windows to build I can possibly look into that
@rocky light it hasn't even restored...
so I can bootup normally?
try the ibec fix above
see what happens
leave it in recovery please, fix ibec
I'll try it
if you successfully build, i'll try that for u
linux is more a pain in the ass cause i need live installation
I dual boot mac/windows I just hate windows too much so I don't want to boot to it that often
i recommend having a linux distro on a drive, maybe like a 50-100gb partition
🤣
if I exit recovery, will something happen?
it will reboot
your device will no longer be in recovery
okay thx
but idk what I should remove
idk itunes's drivers
its explained with much detail
device needs to be plugged in in recovery for the drivers to show up
it's still in recovery right now
then you should be able to follow the downgrade guide for itunes
the patience in here
!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. This is the best version: https://support.apple.com/kb/DL1816?locale=en_US (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
jeeez
should I uninstall imazing too if I have it?
anyways as for iTunes not starting up, the fix is setting English as display language in Windows :')))
microsoft store itunes won't let me even use it
i just dont get how they release something (purely tested I think) and they release it broken
lol
ok will try that
Hey, so I didn’t do it because I had to use my phone, I’ll try it tomorrow. And I understood how I should do it
But right now after booting up, my battery is draining like hell
Do you think that it is because it has been connected for some time on the laptop?
use latest beta
has some fixes
for our device i guess
will do
literally you rn
hopefully it works 
me when fdr fails for the 200th time
/tmp cleared automatically
@valid adder but yeah --latest-sep and baseband isn't working at all
eh F
log with 242
kitty won't let me cmd+a 
use gui
sep not signed?
debug log too please @celest basalt
ok doing that rn
[WARNING] failed to read BasebandGoldCertID from device! Is it already in recovery?
[WARNING] using tsschecker's fallback to get BasebandGoldCertID. This might result in invalid baseband signing status information
is this normal @valid adder
always seen it
what command did u run
sudo /Users/evelyn/Downloads/futurerestore-x86_64-v2.0.0-test -t /Users/evelyn/Desktop/3986078086774830_iPhone10,6_d221ap_14.3-18C65_27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae.shsh2 -s /Users/evelyn/Downloads/checkm8-nonce-setter-master/sep-firmware.d221.RELEASE.im4p -m BuildManifest.plist -b /Users/evelyn/Downloads/checkm8-nonce-setter-master/Mav17-6.71.01.Release.bbfw -p BuildManifest.plist --debug /Users/evelyn/Downloads/iPhone10,3,iPhone10,6_14.3_18C65_Restore.ipsw | tee futurerestorelog.txt
maybe the baseband isn't the right one?
does d221 use mav17 or ice17
ice
._____.
is that why?
always been ice lol
@valid adder what been happening here
i'll try ICE rn
aight let us know
brih
ahhaha xD
Sorry bro gotta be honest, my first time
because otherwise it segfaults
lol what
i usually use --latest
send crash log
i think it's a crash because /tmp is write locked unless ur root
the problem is that with latest we wouldn't have had these issues, but it shows sep not being signed, while actually 15.0 is signed
you can use /var/tmp instead @valid adder
its a symlink
/var/tmp isn't write locked for me
u can put anything there without root
wait
no
im stupid
it's futurerestore that makes the files write protected
less gooooo it got past that error
i'm so sorry cryptic
yup
i was stupid again
i was using mav instead of ice
i used to have that when i would expirement with iOS 15 baseband
now idk if that's the issue
idk how i fixed it
i used 14.8
bb / sep
what version of fr
oh the classic make as root then your theos files are fucked type beat @celest basalt
194?
yup
yes
ah well youre on windows
yes e.e
but i don't think that's the segfault
so you cant use 2.0 beta
SUCCESS WOO
however when i used 2.0 beta it was fine
nope 😦
yes
can we confirm it was because of ice / mav swap?
Also did u use 14.8 sep / bb?
yes
ok nice
sighs in relief because it makes no sense that d221ap would fail
man
so basically 14.8 goes, but latest sep still broken
every time it's a stupid error
while it's actually signed
good lesson: it's rarely futurerestore's fault
what is this xml even for
prove that it could make an interaction with apples server?
is it worth trying 14.8 sep / bb on Windows 194?
to be fair
u could use a vm
and use 2.0 beta instead
as it fixes a bunch of things
vm linux? does it support usb through vm? or it requires a fully linux OS as per Checkra1n?
i heard it was not working
i mean, i remember checkra1n needs to be run from a proper linux installation instead of VM
cause it couldn't pass some things through usb
im p sure vm for fr works
now idk future
it did with @celest basalt didnt it
I used a Windows 7 VM on Windows 10, Linux VM may work too but haven't tried
since Win7 is less problematic with iBEC
would fr work with wsl
if you use Win7 + old iTunes it's more reliable - Linux may be easier, but back then there wasn't a Linux build that worked for me
lol nice question
uhh, WSL doesn't support USB beyond like storage devices so no
brih
like s0uthwest v245 was the only version that worked for me for 13.3->13.5 on XR but Win10 had iBEC issues
Do I understand correctly that when 14.5.1 SEP won't be compatible with newest version I will not be able tu future restore to 14.5.1? (I have two iPhone X, one with 13.5.1 and one with 13.2)
trying to get it compiled manually on Linux was a mess with the dependency hell and when I got it working it segfaulted in the middle of the restore 
at least it was before sending filesystem
mmmmh so might be better to just dual boot linux and try from there i guess
instead of a VM
@celest basalt thats not how it works
when it becomes incompatibile yes
if there's a new version, say 15.2 that breaks SEP compat, then you won't be able to FR to anything lower than 15.2 anymore after all older versions get unsigned
you have to restore with a signed sep, 14.8/15 are the only ones signed a11 is compatible down to 14.3 @celest basalt
but 14.8 exists, so SEP will probably stay compat for a while
@valid adder can we use SEP from OTA
in case 14.8 remains OTA signed only
Thank you very much for info!
A15 fr
someone really needs to fix a11 bullshit
@valid adder sorry for ping. Just understanding if I need beta 2.0.0 (So using Linux) or not
recommended
194 has a major bug, its complete magic that is still even works in some cases
in others its broken
its stood the test of time
hahahah🤣 aight so will dual boot Linux then
yall should check out the discord
And another question, on one of my iPhone X I have only 14.5.1-ota blob saved, not normal 14.5.1 blob, can I use it to future restore (via Oddyseus)?
Nice 😄
is the 502 bad gateway error a known and hopefully temporary issue?
while trying to dl the blobs
who can test futurerestore build rn on mac
Hello, I want to restore my XS Max from 13.6.1 to 14.2 but futurestore is saying that SEP is not signed. What should I do? (Also the Telegram bot is saying "The specified device doesn't seem to have an SEPOS or BBFW inside its IPSW")
manually specify 14.8 sep/bb or update futurerestore @civic sundial
I'm using https://github.com/m1stadev/futurerestore , is it wrong?
zip of 14.5 blobs
I think you should use this https://nightly.link/m1stadev/futurerestore/workflows/ci/test @civic sundial
Hi, I have 14.3 and 14.5.1 blobs and i want to try ios 15 and possibly downgrade (to keep jb), are ios15’s sep/bb compatible with 14.3/14.5.1? I do not have 15RC blobs.
(Using XS Max)
Oh, so if upgrade ill be stuck?
Ive read on a post in the subreddit that the 15RC sep/bb were usable for 14.5.1/.3 but they tried on A11 
perfect thanks yall!! imma try this tonight
Yea I don't think those work anymore just download the shsh file itself
@strange yew no jailbreak, no downgrade do I have. to spell it out lol?
Ok thanks
!t sepbb
Currently you can restore to the following versions with the latest SEP and baseband for your device:
Devices that only support up to iOS 12 (most A7 and A8 devices excluding iPad5,1 - iPad5,4): 11.3-12.5.4
A9 and A10: 14.0-14.8
A11 devices: 14.3-14.8
A12 devices and newer: 14.0-14.8
@valid adder should I downgrade my a11 from 15.0 to 14.5 for the untether
Since now it's confirmed to come out
doesn't matter when
When I downgrade or when it comes out?
when you downgrade
Oh lol
can i use 14.8 blobs and downgrade to 14.5.1?
thats not how it works at all
the blobs are for the version you are going to
@celest basalt
!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. This is the best version: https://support.apple.com/kb/DL1816?locale=en_US (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
just a question, in the first step, the driver we should remove is also iboot?
sure
and it will delete the others automatically?
idk
is futurerestore gui good for my purpose? iphone x 14.7 to 14.5?
actually from what I'm learning, it depends on the os you're using
gui has no added iOS functionality
that questions is phrased poorly
its the same as cli
but to answer your question yes
aight should i manually download futurerestore and import it in the gui or use the download button in the app?
nah just settings > enable beta
sry for the questions but its been ages since i last used it
then hit download button
will the beta take a lot of time for windows?
I have no way of knowing
futurerestore-x86_64-v2.0.0-test this is the right vers right?
yep
thx
it should say 242 in the log
if you're on the beta, can you downgrade with the ios 15 sep and bb?
should be able to, haven't tested it yet tho
not that high risk cuz backups exist
someone said earlier that backup from 14.7.1 or older works on 14.5.1
but they don't work on 14.5
if she want to restore form a backup
yeah ik
but last time i edited, i got some bugs with some apple apps
like reminder and clock
oh its fine
prolly will just back up the apps i need and restore them via jb
if i find a way to backup the whole whatsapp app without icloud
idk if yk what i mean
if you have imazing, i think you can backup a specific app
but idk if you can do this in the free version
how are you going to set boot nonce?
probably a stupid question
just restoring to stock 15
oh
no need to set nonce
so use futurerestore just to flex
anyways tried 242 on a fresh Linux installation (Live Installation) but it seems to be stuck just after downloading Savage,B0-Prod-Patch.
downloading SE firmware
100 [===================================================================================================>]
[TSSR] Checking BuildIdentity 0
[TSSR] Selected BuildIdentity for request
downloading Savage,B0-Prod-Patch
100 [=========================================================>]
irecv_event_cb: device 000474ca2853c02e (udid: N/A) connected in Recovery mode
and it just freezed for like 20m
best
Successfully restored iPhone X (D221AP) from 14.8 to 14.5.1 using 14.8 BB / SEP /BuildManifest manually with FutureRestore v194 on Windows 11.
Status: Restore Finished
Cleaning up...
Done: restoring succeeded!
FutureRestore process ended.
finally >.>
How long did it take you?
Just 10m now. But been struggling from yesterday just to know that I was using the wrong baseband file (I was using Mav instead of Ice)
But the other person sent me a mav file
Do you think that it’s because I’m on an iphone 6s+?
I don't know what BB uses iPhone 6S+.
The ICE Baseband is for iPhone X
Oh ok
I have mav iPhone X not ice @vagrant sonnet
thx man haha 🙂 Yeah been restoring 5 times at least lol. Finally made it.
Yeah that's why i needed ice instead of mav
mine 10,6
Massive W
should I sign out of icloud before using future restore??
doesn't matter unless you forgot your password
yeh but how can you forget your password that easily
no i didn't forget anything
i also have everything saved in a piece of paper
ik it's weird btw
are all your data erased?
yes
but can't you restore a backup or it won't work?
reyna from val
do i need to specify sep or
can i use the latest?
Use latest with beta fr
Request URL set to https://gs.apple.com/TSS/controller?action=2
Sending TSS request attempt 1... ERROR: Unable to send TSS request
Cleaning up...
[exception]:
what=ERROR: Unable to get signing tickets for SEP
why do i have to only get mfing problems 
hello) how to get sep and baseband file from ios 14.8 ipsw
download the 14.8 iPSW or
use partialzipbrowser
to remotely download it
you could also just use --latest
which is the very best option
i already have it downloaded) what files am i need from ipsw?
unzip the iPSW
and go to /firmware/ folder
then find the files ending in:
.im4p for SEP, your device board config will be in the name
.bbfw for baseband files
wtf
what device
there is 4 im4p file and 2 bbfw files) what i need to do with them?
whats your devices board configuration
iphone X (gsm)
mf
should be D221AP
find a im4p file with the word D221AP in it
make sure it ends in im4p, NOT plist
Sending TSS request attempt 1... ERROR: Unable to send TSS request
Cleaning up...
[exception]:
what=ERROR: Unable to get signing tickets for SEP
code=99811345
line=1523
file=futurerestore.cpp
commit count=242:
commit sha =97ff42fd3a4d8676e766543dc768e825e9173b48:
Done: restoring failed!
FutureRestore process ended.
again 😦

could it be named as "device tree"?
what
this name? DeviceTree.d221ap.im4p
tss said fuck u
bro no
thats not it
sep-firmware.d221.RELEASE.im4p is it right file?
yes
what bbfw file is needed to use Mav17-6.71.01.Release.bbfw or ICE17-4.05.00.Release.bbfw?
download this
and check settings
go to general -> about, scroll down
then youll see either ice or mav
tried cli
[exception]:
what=SEP firmware is NOT being signed!
code=16908296
line=258
file=main.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:
most concerning is TSS server returned: STATUS=94&MESSAGE=This device isn't eligible for the requested build.
mr. tss servers, i am giving u a literal iphone 10,6 ipsw
are you using pwndfu
for my iphone 10,6

no im not
im getting so angry
ong
when he has time
at least the cli doesnt make it reboot because it verifies b4 it does so i dont have to rejb and reset the gen
but like wtf
im going to try giving it everything it needs
such as buildmanifests, sep and bb
because it doesnt like me enough to use --latest-sep and bb
@tender sun what version are you trying to restore?
I succeeded with these settings.
Also using ICE baseband, not MAV.
from 14.7 to 14.51
mind sending me the files u used
such as bb sep and shit
will send u in DM
ice
iPhone 11 or XR?
Use n104.RELEASE.im4p
and check the manifest for what baseband you have to use
In the root of the ipsw
It tells you where the baseband is found
If you don’t know where to look send it here and I’ll find it for you
It should be called BuildManifest.plist
any google doc for 14.8 sep compatibility?
!t sepbb
Currently you can restore to the following versions with the latest SEP and baseband for your device:
Latest SEP is iOS 15.0 but 14.8 is also still signed
Devices that only support up to iOS 12 (most A7 and A8 devices excluding iPad5,1 - iPad5,4): 11.3-12.5.4
A9 and A10: 14.0-14.8
A11 devices: 14.3-14.8
A12 devices and newer: 14.0-14.8
maaan i could've restored to 14.3 but my stupid mind decided not to save blobs for it
😦
Is that for your board config?
There’s multiple
Send it here
The file…
Nvm then
Wait
Firmware/ICE19-2.06.00.Release.bbfw
Status: Restore Finished
FDR 0x7fbc401877d0 terminating...
Cleaning up...
Done: restoring succeeded!
lets gooo
Found device in Normal mode
Entering recovery mode...
futurerestore: failed with exception:
[exception]:
what=Unable to place device into recovery mode from (null) mode
but my phone is in recovery mode 😦
i did as the instruction said but i still receive the ibec error can anyone help me
Keep trying, if it fails enter recovery manually @civic sundial
any way to get out of recovery on linux?
major w
irecovery -n
@celest basalt your device needs to be in recovery mode and plugged in for the drivers to show up, then you can remove them
i need to delete the drivers after i plug out and plug in again ?
No I said your device should be plugged in in recovery mode, then you can uninstall the drivers
You then need to downgrade to that version of iTunes
okay i'll try
https://github.com/Chronic-Dev/libirecovery ? @zealous bridge
install it via apt that’s not even the correct repo...
wtf
got it on iphonewiki 💩
welp
Reading is hard
but i did download the 64 bit
this is regarding futurerestore
i needed to fix ibec error and they told me to download this version of itunes
where are thy are they in the buildmanifest?
Just close it
oh okay
The BuildManifest is what you need to specify
You don’t need it open, just installed
okay
and now it says this
/Users/3strikedev/Desktop/futurerestore -t /Users/3strikedev/Desktop/1153826794537006_iPhone12,1_n104ap_14.5.1-18E212_c46bde5a1a77fc4c3d24f80577828940d6779b426a26cd973a80a504db5926fc-2.shsh2 -m /Users/3strikedev/Desktop/BuildManifest.plist -p /Users/3strikedev/Desktop/BuildManifest.plist /Users/3strikedev/Desktop/iPhone11,8,iPhone12,1_14.5.1_18E212_Restore.ipsw
?
Replug
ye did it like 3 times
Where is sep and baseband
huh
You need sep, baseband and manifests
heeee
-s sep -b baseband -m sep manifest -p bb manifest
that’s how it is
And this is why you use a GUI
what should i do now
Boot linux
what i cant do that
Just get a usb and live boot it
too much work also this is my frined's laptop
Rip then
Follow the iBEC fixing steps again from the top
Try it until it works it might work after a few tries
Windows?
macos
idk
hmm?
The beta is working fine
what settings
commandline futurerestore xD
Oh lol
send me the link
I was talking about the gui
to the gui one
Okay give me a min
Click on assets, and choose macOs gui
Device ApNonce does not match APTicket nonce
can i use --wait for that or am i fucked
just set it
No package 'libimobiledevice-glue-1.0' found
I searched everywhere but no information, I can't install libirecovery 😦
can i use the terminal method of futurerestore for ios 14
libimobiledevice-glue isn't available on apt anymore, add to install checkra1n to get it 
i cant restore from ios 14.6 to ios 14.5.1...i have from 15 minutes updating baseband
i ve stopped futurerestore and now i m upgrading to 14.8
futurerestore stuck on upgrading baseband, iphone X, dowgrading to 14.5.1 from 14.8?
Which version did you use ?
@atomic bridge @balmy bough use latest beta
link
!t futurerestore
futurerestore allows you to upgrade/downgrade/restore to unsigned iOS versions if you meet certain requirements.
Tutorials:
Tutorial
Video Tutorial
Links:
FutureRestore GUI
Latest stable version (194)
Latest beta version
There are currently no pre-compiled beta builds for Windows.
is it gui? 
yes i used ios 14.8 baseband
ty @zealous bridge
hem
I don't know why but it seems i've been saving my blobs with nonce 0xbd34a880be0b53f3 in blobsaver for & year, when I open odyssey my nonce is 0xbd34a880be0b53f3 too
I guess I'm fucked, right? It's the electra nonce
Why would you be fucked
i'm getting lost in all those restore stuff x_x
Any1 knows the SEP and BB for iPhone 11PM to upgrade from 13.5 to 14.3?
help me pls
i have the blobs
I'm trying to restore for hours now lmao
What's the error you’re getting
the lastest ios15 doest not working
Use latest sep and baseband
on futurerestore
.
got error
What error
when I added argument -w it was keeping saying I had the wrong apnonce
w8 a minute
Dont add that
so I thought I fucked up when I saved my blobs
Just set your nonce
alright imma try again, rebooting to linux 
lastest ios 15 beta?
No
Latest futurerestore beta
Latest futurerestore beta
ok
can i use the latest beta in gui
i will try
?
Yes
man fr windows CI needs to be fixed
i'm on mac os
go to frgui settings
And enable beta
Then press download futurerestore again
no windows 😦
L
down bad
yes
On windows you have to manually specify 14.8 sepbb
a lot of characters appears...how long i have to wait ?
How on earth would we have any idea what that means
so my actual apnonce is 0xbd34a880be0b53f3, how do I get the right apnonce to set it to?
that’s not your apnonce, that’s your apnonce generator
but yeah that’s what you’d set it too
ah okay well it's already the right nonce, when I try to restore it get stuck in Entering recovery mode... but when I go in manually it says
Device ApNonce does not match APTicket nonce
now i use last bb

what file to extract in 14.8 for iphone 11pm
the blob file i'm trying to use doesn't contains any generator, does it means it's useless?
(waiting for ApNonce: ff 6c 43 cb 0d 4e 50 4d 6a 84 2f c2 73 8c ed 74 67 f8 74 c1 9d bd 35 de 49 b3 24 d6 31 f8 43 36
Got ApNonce from device: d7 02 dc 16 a2 10 0b dc 0d c1 97 99 f1 92 09 38 4f 91 5d be c5 77 52 b9 d4 fd 26 6b cb 30 2d c6)
how do i grab ios 15 blobs
Okay fellas I’m on iOS 14.4.2 iPhone X trying to update to 14.5.1 I’m getting a error if sep no signed.
Of sep not being signed* does this mean game over or is there a chance
enable beta in settings then download futurerestore by clicking on the button
Okay
hey
Enable beta in future restore GUI settings?
yes
Did it gonna try
heyyyyy
dude stop spaming ffs we don't know
oh ok
By the way when in Conan blobs there’s two files under the blob file which one is it? And no I don’t mean OTA
They look the same 🤷🏽♂️
maybe check both with blob checker
I think I saved all my blobs with a random generator

welp batchomatic here I am imma stay on 13.6.1
Don't use batchomatic
It sucks
kinda yeah
Tweak backuppers shouldn't be used
i'm lazy and I spent half of my day trying to restore
I just chose one and it seems to be working I got farther now waiting
nice ecid bro
lucky you
idk why blobsaver was set to use a random generator
Failed damn it
i'm mad af
What's the error
stuck on 13.6.1 the only valid blob I got is 14.6
Sorry didn’t take note I’m trying again
This iPhone X is also bypassed does that matter?
Yes
You offered no help. And it’s working
ok i don't see why you needed to say that
mf be icloud bypassing 
just put your fucking apple id details in
or return the stolen phone
stealing is NEVER the solution 
lol this is my testing device before I try on my phone.
???
You didn’t work but got further
doesn't mean you can't just put your apple id details in
are you using latest fr
are you using --latest-sep
Yes
what fr version
that shows me nothing about your fr version
I’m on 1.91
that is not futurerestore
that is the futurerestore gui
what version is the binary
should be in Files tab
delete /tmp/firmwares.json and /tmp/futurerestore @hidden plinth
How do I do that?
Where are those folders located?
/tmp
I said???
In finder?
Yes
Doesn’t pop up
there is a go to folder option in finder
Show me the options tab in the GUI @hidden plinth
It doesn’t make sense why it would fail
@valid adder actually it seems i didn't set a generator for my xs max profile months ago. useless blobs right?
setting gen is optional because it just adds the generator key in the blob
as long as you remember the gen it's valid
So is it game over for me?
mhhhhhh lmao my apnonce doesn't match with any known one
If you know the gen (and are jb) you can set it
I guess it was automatically set to a random one?? I'm so dumb I didn't paid attention
yes because it changes unless it's frozen
I'm JB yeah that's why I was able to try gens, but can't find the right one jeez
facepalming myself 1 year ago
were you jb when you saved them
if so what jb were you using
So am I fucked? Done? Game over? Or is there a chance?
How can you be fucked iPhone X has perks jailbreak @hidden plinth
I mean like being able to future restore?
I was yeah, it always was odyssey, never installed unc0ver actually
Remember that the only requirement is setting nonce
it should be the default one, but it isn't :/
Perma jailbreak means you can always set nonce
Try 0xbd34a880be0b53f3
yeah I did try it's the odyssey default
man
also tried checkrain one (0x1111111111111111)
That’s my nonce
dunno what happened hhh
no that's your gen
Will move to 14.6 when something will be available then, too bad for me 😂
That’s what I set my nonce as in new term.
no you set your gen to that
Oh
the one in nv ram is your gen
So what’s the deal? Do I have a chance to actually future restore
Cause I want to eventually update my 12 pro Max to 14.5.1 from 14.3
if you have the right gen and a valid blob file yeah
why is blobsaver detecting my gen as 0x09acc956527c03c8 while it's set as 0xbd34a880be0b53f3 in odyssey
i'm going to stop using this software 
Because when blobsaver reads from device it changes it and freezes it
so 0x09acc956527c03c8 is the default gen for my ECID with blobsaver
I don't remember if I tried this one also
nah wrong nonce, I saved dozens of blobs with random gen
how do i grab ios 15 blobs while on 13.7
ask your harvard teachers 
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
u need to set gen n stuff not like me
i tried using retrieve but for some reason the earlist version that shows up is 14.7.1
well it depends since when you started saving your blobs I guess
i cant save any more blobs?
well yeah save your blobs it will add more folders
you can only save blobs for currently signed firmwares
but do i have to update to ios 15 to do that?
lmao no
that's the goal of saving blobs
you save them so you can restore to the chosen firmware even if it is unsigned because you saved blobs
is your nonce generator set
i had a tracking extension on my browser blocking it
Use blob saver
happens sometimes, depends on the adblocker
ive been baffled for like 2 days as to how to get this to work and it was the adblocker
alright well thanks
i got it 🙂
It does and it’s 0xbd34a880be0b53f3
nice
well now I have to reinstall tweaks n stuff and stay on old fw, how sad
gbye
F
Are you getting “unable to get signing tickets for SEP” on the iPhone X?
Because that’s exactly what I’m getting
Yes
Did you figure it out?
I am moving from 14.8 to 14.4 with blobs and I'm getting SEP firmware is not being signed. Have I missed something?
Use futurerestore beta
Sep isn’t signed for 14.1 on A11 devices
Ah shit. That explains it 😂
Yuh
Doesn’t explain why it’s not working for 14.4 though and throwing the “unable to send tss request / unable to get signing tickets” error
Find out if restoring is possible!
@valid adder sorry for ping but can you look into this?
This is just wrong then?
yes it’s wrong
Damn.
we bothered him like 20 times or so and he acted like it was a three line fix
Sorry for ping but it looks like you had the same issue earlier and figured it out, do yk what you did?
which I’m not sure if I should treat that as the funniest shit in existence or just proof of how far the world has fallen
Thanks for the info though. Saved my sanity. Been trying to figure this nonsense out on my own before I realized I should just join the Discord.
hello cryptic!
even using latest SEP it doesnt work gaHHH
status=94
device isnt eligable
This error what=getting keys failed with error: 13959183 (failed to get FirmwareJson from Server). Are keys publicly available?
gets thrown when trying to use pwndfu
@stiff hazel just wanted to update you, even with latest SEP
yeah I already pinged cryptic but I’m 80% sure they’re not available or they’re asleep right now
awwwh shoot
so we’ll see what they say when they become available
thanks!
just using the beta to move from 14.8 to 14.4 on iphone x and its stuck at got ApNonce. does this just take a while or should i try again?
@celest basalt https://github.com/m1stadev/ios-tools/
python3 wiki-proxy.py
@stiff hazel I was at work
Oh hey!
youre cryptic!
Sending TSS request attempt 1... futurerestore: failed with exception:
[exception]:
what=SEP firmware is NOT being signed!
code=16908296
line=258
file=main.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:
FutureRestore process ended.```
this is using the LATEST sep
im stuck at irecv event recovery mode
194 doesn't support --latest iOS 15 for a11 and later @strong marlin
you would need 14.8
gotcha, i have the ones from 14.8
gives me a not eligable error
which device
hey y’all, i recently got a new ipad and saved the blobs and I’m wondering, do I need to be jail broke in order to downgrade? I want to be able to downgrade just incase but all the new ios 15 features are too tempting
What do I do with this?
thank you. oh well, i’ve already got my phone jailbroken so i’m not too upset
You need to proxy the keys from the wiki @celest basalt
i cant seem to get it to accept my sep
even though im using 14.8's
these fellas
as my baseband
Yah 194 has the major bug I fixed long ago in beta
oh wait wtf one sec lemme restart futurerestoregui
heres my latest ```[exception]:
what=SEP firmware is NOT being signed!
code=17956872
line=274
file=main.cpp
commit count=242:
commit sha =97ff42fd3a4d8676e766543dc768e825e9173b48:
FutureRestore process ended.```
im using 2.0.0 test
im using d221ap since im gsm
and with either baseband i get ```[exception]:
what=SEP firmware is NOT being signed!
code=17956872
line=274
file=main.cpp
commit count=242:
commit sha =97ff42fd3a4d8676e766543dc768e825e9173b48:
FutureRestore process ended.```
ran wiki-proxy.py in the background, getting this error
TSS server returned: STATUS=94&MESSAGE=This device isn't eligible for the requested build.
ERROR: TSS request failed (status=94, message=This device isn't eligible for the requested build.)
Sending TSS request attempt 1... ERROR: Unable to send TSS request
Cleaning up...
[exception]:
what=ERROR: Unable to get signing tickets for SEP```
@strong marlin should be using these
@celest basalt at least wikiproxy is working
which futurerestore version
2.0.0 beta
@valid adder that worked but now im stuck on futurerestore gui not detecting recovery
I have no idea what that even means
DEBUG: Waiting for device to disconnect...
idevice_event_cb: device 001a7c320028a02e (udid: dfd26bcc807f1c2548c30cd962c39a8977994147) disconnected
DEBUG: Waiting for device to connect in recovery mode...
irecv_event_cb: device 001a7c320028a02e (udid: dfd26bcc807f1c2548c30cd962c39a8977994147) connected in Recovery mode```
basically
phones in recovery
but the app isnt detecting it
I'm using the gui, this is the command the gui is using though
"/Users/admin/FutureRestoreGUI/extracted/futurerestore-x86_64-v2.0.0-test" --apticket "/Users/admin/Desktop/387887158067246_iPhone10,6_d221ap_14.4-18D52_27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae.shsh2" --debug --latest-sep --latest-baseband "/Users/admin/Desktop/iPhone10,3,iPhone10,6_14.4_18D52_Restore.ipsw"
why did you have have usepwndfu selected before @celest basalt
I was literally just trying everything possible bc nothing was working
That's insane, I think two other people had the same problem today?
Maybe Apple unsigned something for A11?
nah its fixable
this shit brand new, don't expect it to work immediately
I can probably fix it with the log
let me check out stuff soon
do you need a full log?
I have log already
hmm maybe I don't
can you enter your discord username in settings so it shows in logs
same here, using the stable version seems to work
you got it all done?
done, and ran it again. Did you get the log?
@celest basalt yep thanks
no problem man good luck fixing it, appreciate it
is it fixable?
so im not being stupid lol?
I guess its time for me to backup my X and test
I don't get my 13 Pro until friday so I hate restoring my main device(X)
I’m kicking myself so hard for not saving blobs more regularly now
I don’t have 14.5.1 😦
at least I have 14.4.2
We literally have an autosaver lol
I basically ignored my jailbreak for the longest time
I’ve recently started saving more regularly but only since about 14.7.1
Just have autosaver
damn i cant do this 😩 lmao
aye
new build try download newest beta



