#futurerestore-help
1 messages · Page 17 of 1
!!
just try again
two days back i restored my X to 14.0.1 using version 190 but with 14.2 SEP
thats y i am doubting the SEP
the sep checker compares a tv os firmware and a ios firmware
how to check the real sep compatibility
@patent mortar RSS feeds are now available on The SEP Checker.
!t sep
How to check if the latest iOS version's SEP is compatible with a target iOS version: https://joshblah555.github.io/JoshTV/SEPCheckr.html
ERROR: Unable to receive message from FDR 0x7fb9b7d85000 (-2). 0/2 bytes Futurerestore v190 compiled using the above script, macOS 11.1 with iPhone 10,6
it's the FDR error
i spent the whole day trying to compile futurerestore and restore my iphone
what version are you restoring to?
Thank you!
Hopefully it works..
@vivid nova does brew actually support linux?
yes
@storm apex works great
this is a 2012 imac
nope
everything got installed from scrath
?
@storm apex oh wait
xpwn didn't get installed :?
nice
this is a clean install of mac os
@storm apex I'm surpised that openssl took 20 seconds to download and install
but yeah the only error is xpwn
where can i get or compile v187?
uhh i think this source is for v190
@nocturne egret can you compile that version https://github.com/marijuanARM/futurerestore and let me know if you get any warnings for linking at the end?
Such as something like this
I kept getting this after 30+ tries until I fixed the OpenSSL linking errors
I was futurerestoring to 14.2
My theory is that @nocturne egret needs to make sure he doesn’t have any OpenSSL linking warnings when compiling and it should work is all
I didn’t know there as one, I’ve been doing it for a few years with no issues, so it’s easy enough
followed the tutorial and FDR error was the result
from 14.3 (iPhone X) to 14.2
of course i have blobs
Can you screenshot the end of the compilation of futurerestore?
i could upload my 187 and see if y'all can try it
that would be nice
granted of course, you have the dependancies compiled
Static binary?
windows/macos/linux?
macos
thank god i dont have to reboot
windows is a nightmare and linux is like trying to enter the white house
Is it static or dynamic tho?
dynamic
“Library not loaded” incoming lol
i didn't do any different than y'all.. if you followed the tutorials then it'll work
i agree
theres a dynamic bin
i doubt it will work out of te box tho
Actually am I allowed to post that bin?
I’ve been banned once and don’t wanna do it again lol
yeah it requires libgcrypt
easy to compile
there's no libcrypt repo in thimstar's repo list
I swear this is all just an ssl linking err. Can you compile it again and screenshot the last couple lines of compilation to see if it has anything like this ?
git clone https://github.com/tihmstar/libcrippy && cd ./crippy && bash autogen.sh && make install
@sharp latch just compile open ssl
sudo mkdir ssl
sudo chmod 777 /usr/local/ssl
cd
git clone https://github.com/openssl/openssl.git
cd openssl
./config
make
make install```
copy/paste
I don’t get the needs for scripts imo. for me I just git clone recursive try and autogen.sh see what the err is and fix it by more cloning and installing
At this point it’s been fixed so it’s ok for now. But I’m gunna save that for sure
so just gotta wait it out
I appreciate it. Just a few lazy ass symbolic links that will break when I update OpenSSL fixed it for now but I’ll use your solution when I need it next.
i gave up on editing the configs.. took a good hour to compile openssl but i was able to compile everything after
libcrippy.c:156:12: error: implicitly declaring library function 'toupper' with
type 'int (int)' [-Werror,-Wimplicit-function-declaration]
res[i] = toupper(res[i]);
ah yes, the poorly written code
how can i fix this
<@&355177530061357057>
libcrippy from tihmstar
another question, how can i get source code of futurerestore v187 (not v190 on marijuanARM/futurerestore)
git reset --hard commit### that matches 187
commit### means that weird commit hex on github right?
Yea
i modified that script above and it's compiling v187
AH YES IT COMPILED
and there's one mystery left: will it restore properly?
No since it doesn’t have the restore boot manifest hash component
It will fail half way
how can i fix this
ah shit that same FDR error again
Sending NORData now...
Done sending NORData
idevice_event_cb: device - (udid: -) disconnected
ERROR: Unable to receive message from FDR 0x7fbf0dc5d850 (-2). 0/2 bytes
because of using an unsiged baseband and or unsigned sep
It’s because his SSL is fucked I’m sure. @nocturne egret can you Screenshot your compilation and let me see the end of it?
here you go
Can you do ls "/usr/local/Cellar/openssl@1.1/1.1.1i/lib"
And lmk what comes up if anything
~/res ls "/usr/local/Cellar/openssl@1.1/1.1.1i/lib"
engines-1.1/ libcrypto.1.1.dylib libcrypto.a libcrypto.dylib@ libssl.1.1.dylib libssl.a libssl.dylib@ pkgconfig/
~/res
there it is
Hmm that’s odd as that should actually work. Have you rebooted since installing it?
That’s so odd, when it fails it writes a restore log it would be nice to see it
where's the log
not in the same folder
it's the log copied from the terminal
also i checked my shsh is vaild
some one need to fix this FDR error
@storm apex why does your script compile futurerestore 190
on a fresh ly restored mac
because the repository was updated @rustic blaze
so how do we compile 187 now
if you'd like 187... I have it here #futurerestore-help message
u said 187 works good
you can tweak some code to make it compile v187
@rustic blaze you didn't drag in any script.
so... you renamed the script?
no
okay, you downloaded the 187 binary, then tried to use it?
yes
@rustic blaze brew install gnutls
ok'
installing
it
may b
libcrippy error
installing it now
when i type make
it gives me warnings and stops
imagine ppl streaming their errors instead of giving us 0 context to such issues
afaik, you're using 190
still no progress
fuck fdr error
and why the fuck my device disconnects itself after sending NORData
i think that's the problem
common.c:supressed printing 10260700 bytes plist...
Sending NORData now...
Done sending NORData
idevice_event_cb: device 001a79281007c83a (udid: ffffffffffffffffffffffffffffffff00000003) disconnected
ERROR: Unable to receive message from FDR 0x7fa737f68ab0 (-2). 0/2 bytes
FDR 0x7fa737f68ab0 terminating...
here's my log, i've been having some issues downgrading from 14.3 to 14.2, could someone take a look at it and tell me what i'm doing wrong?
you also have same error as me
good to know i'm not alone, i'm using linux if that makes a difference and i used the compile script provided to compile futurerestore on linux
@nocturne egret @celest basalt don't use --latest try with specifying your .bbfw and sep.im4p files using -t ticket.shsh2 -b baseband.bbfw -s sep.im4p -p BuildManifest.plist -m BuildManifest.plist iOS_firmware.ipsw
when i try that i get the error that it isn't signed
you need to use the latest .bbfw and sep.im4p
you may extract them from the 14.3.ipsw
ah, i'll give it a shot and see if it works
i already did and same error happened
what device?
iPhone10,6 (iPhone X GSM)
mine is apparently the global variant
i think the version 191 is creating issues
i tried v180, v187, and v190
v180 is no longer for ios 14
v180 is original tihmstar if i remember correctly
yes i know
but all 3 had the same error message
i don't know which version i'm using, i just run the compile script provided
it's probably the latest one though
if you use that script you are using v190
ah
i think so
i don't know about 14.1 but it should be with 14.2
@celest basalt y r u downgrading from 14.3 to 14.2
i kinda wanted to see if it works or not, just an experience thing
dont u have blobs for 14.1
nah, i got my device used which came with 14.4, couldn't get the 14.1 blobs sadly
oh
it's meant for work but i enjoy playing around with it
i have 14 devices
also have blobs for original 14 and 14.1
that's lucky, i was too late, i went to save blobs when it got it but missed out on 14.1
nice, guess i have to wait to see if it's futurerestore or me that prevents the downgrade
this was an interesting experience though, i thought i was the only one that has issues
Yeah, should def work now.. had to fix a few things along the way..
is there someone who can compile clean futurerestore v187/190 for macOS or linux?
i wanna see if my compiled version is causing the problem
or my macbook is the cause of the problem?
better linux than windows
doesn't exist...
and one question: how should i install this files
just unextract and run?
i dont wanna fuckup my installation anymore
thankfully i'm recovering by reinstalling glibc first and reinstalling all packages
you should be able to extract the tarball as-is. then apply perms
thanks
just extracting tarball and setting perm doesnt work
tried copying all libraries to binary folder and setting LD_LIBRARY_PATH to current folder but SIGSERV (Address boundary error)
i use artix
and also tried that script but it cant detect device in recovery mode
what mac are you using? the hackintosh?
macbook pro 16"
currently booting linux'
triple booting windows, macos, and linux
damn this laptop is even slow in linux
fuck same error even on clean installed ubuntu with different laptop
hmm i should just give up futurerestoring until actual working binary is out
damn errors
also i have uploaded logs of failed attempt in this channel so if you guys want to help me please see those logs
oml
I just noticed that my ca\lang was on 12
the one I used on linux was 8 to compile xpwn
!t futurerestore
futurerestore allows you to upgrade/downgrade/restore to unsigned iOS versions if you meet certain requirements
[Tutorial](#futurerestore-help message)
@nocturne egret https://www.dropbox.com/s/grjo5r31u2qswz5/futurerestore171-static?dl=1 could try that bin and see? I just used it on iOS 12 today
hmm, apparently my SEP is compatible to go back to iOS 13.5 if 14.3 gives me no joy =]
Baseband isn’t tho
And I know a guy who has a WiFi only iPad and they said it still failed but idk I have yet to try that on my WiFi only iPad
I got the same error as @rustic blaze
I also tried to use the 14.3 sep to go to 14.1 and it didn't work
@celest basalt what version of FR are you using?
You need this one for iOS 14 https://github.com/marijuanARM/futurerestore
14.3 sep and baseband is compatible with 14.1 correct?
@sharp latch latest version
So this version? https://github.com/marijuanARM/futurerestore
v190 I think it is
Yea that doesn’t grab v190 so that makes sense you would get the FDR for iOS 14
I'm currently making a 190 static build.. but it'll take time
thank you jtv 😄
I’m sure you know this but if you compile w/o Odysseus support you can exclude xpwn and make your life easier
but.. that just makes life more difficult for older gens
Yea but older gens can use v187
187 will require you to compile yourself
Also @celest basalt you can also just “git clone --recursive https://github.com/marijuanARM/futurerestore ; cd futurerestore ; ./autogen.sh” and see what happens.
Copy paste this and try again
LD_LIBRARY_PATH=/usr/local/opt/openssl/lib:"${LD_LIBRARY_PATH}"
CPATH=/usr/local/opt/openssl/include:"${CPATH}"
PKG_CONFIG_PATH=/usr/local/opt/openssl/lib/pkgconfig:"${PKG_CONFIG_PATH}"
export LD_LIBRARY_PATH CPATH PKG_CONFIG_PATH
Just re-run autogen.sh
Did it give the same error? I guess you could but it’s far from impossible, just takes some perseverance
ya i got the same error
Actually
That script does use v190 so I’m not sure why it gives you an FDR error. I’ve had the same issue but it was a broken open ssl config that caused it
that's so strange because the other day i used the script using the 14.2 sep and it worked but the 14.3 sep doesn't work
and i tried to go to 14.1 too
I’m not sure man I just went from 14.3 to 14.2 with 14.3 sep yesterday so I know it’s possible.
And have you rebooted the router? This is the err I was getting that iOS wrote to the restore log
Substitute has nothing to do with futurerestore
here is my full log of trying to futurerestore my device
14.3 to 14.0
and i checked and the sep is compatible
yup
Reboot router as well
yeah it could be a router issue because i tried to go to 14.2 for the heck of it and it still didn't work
that's the exact same error as me
yeah, error but it's not the usual error
it's just a log copied from terminal
and the log using > err.log
That’s just cuz it’s an older version :/ that sucks man. You’ll have to compile 190 and hope it works, or wait for the static build. Did you use this script? https://captinc.me/tutorials/futurerestore_compile.sh
Odd man
Ctrl handshake done (ConnPort = 49188)
FDR 0x7fe964f86aa0 waiting for message...
DEBUG: tss_response_get_path_by_entry: No entry 'LLB' in TSS response
NOTE: Could not get LLB path from TSS data, will fetch from build identity
I think that’s the part that matters. I had that issue and it was a broken ssl but I also chmod 777 /tmp and try and make a new network location within a system preferences
hmm then i should try ipad tethering + vpn
Wouldn’t hurt
tried vpn and that happened
searching for this in google i got many results
hmm someone had a same error and he succeeded using windows lol
2 votes and 16 comments so far on Reddit
Lol yea I ran into that as well. I’m just resting a test device to 14.1 right now to make sure it’s not just you
So I’m not sure as it seems to work for me, but if I messed with my open SSL the FDR erro comes back
then i must say this
fuck this country
because this error even happens on clean installed ubuntu 20.10
any static build for mac
Hello everyone. I was wondering if updating to 14.2 will break my Face ID?
no
Is fdr error due to open ssl error
So I should be able to use my 14.2 Blobs and as long as 14.3 is signed it wont cause any problems?
Provided u don’t have any fdr error in future restore
That is what many users have been facing off late
Oh I get it. How do I know which is compatible? is there a place to check?
How to check if the latest iOS version's SEP is compatible with a target iOS version: https://joshblah555.github.io/JoshTV/SEPCheckr.html
@jade skiff if u happen to succeed please also share the log
Isn’t it possible to downgrade to an unsigned firmware using the sep exploit
Cause ive heard before that untethered downgrades can be done with blackbird
@rustic blaze you didn't bypass anything.
huh?
iproxy 4444 44 is emad and he was having a fdr error but then i guess he kept trying and it worked for him
same error as me and a lot of other people too
again.. didn't bypass anything
yup
the fdr isn't an error.. its FR's way of talking to Apple.
The sep is compatible, so, no reason why it shouldn't restore
Embarrassing the things you say🙈🙈
it was just a means of saying things guys
every second user who is using fr is experiencing fdr issues
but let me tell something after i restored my Iphone SE
i tried to restore my X which again stopped at FDR stage
so please keep trying might b it will succeed
check for 14.3 sep
huh?
dont know whether it s the SEP or fr
@vivid nova I’m going to try and statically compile 190 today where did you get stuck?
yea FDR error is there
fdr error @sharp latch
Will an ubuntu VM work? or do i absolutely need to run it from a live USB?
Make it work on Mac
some one provide the source code for fr v 187
I think version 190 is creating havoc
But. It. Works.
What do you mean? That is a mac, it’s a hackintosh. You run it like any other FR
but on mac we get the fdr errors
i have been experiencing this for the past three days
@rustic blaze just wait out the errors.. let it finish
no it errors out and says aborting restore
^ That’s not 190 that’s 187
I think I will be getting an iPhone 11 soon (which means it's on iOS 13 and it's jailbreakable)
Just so I don't make it bad with iOS 14, what items do I need to downgrade to an unsigned iOS build?
as i know here's the list
1. shsh2 blob for your device that is from the target version
2. latest SEP firmware
3. bbfw file
4. buildmanifest
5. ipsw
6. generator nonce set to correct value
pls confirm the list above and fix stuff i did wrong
Just want to point out an iPhone 11 isn’t guaranteed to come on 13
If you get it new it’s probably gonna come on 14
That’s 190 not 187 @sharp latch
@vivid nova
@rustic blaze thats 190
wait
@sharp latch
it matches e4a81783769e6800a4efe69a4bab3478069df20e
which is 190 so
Well he’s getting the same err as 187v my mistake lol
yeah capt needs to redo the openssl part
@storm apex have you seen this before?
idk
yeah for some reason the default on my mac is libbrssl
or some shit
it's sealed, and the apple community said it will come with stock firmware. it depends on the end user to update
it's not the setup assistant's job
@nocturne egret please share your compiled script for v187
@rustic blaze its in the pins
i think @nocturne egret has modified your script
i am asking that
the one in the pins is for v190
@rustic blaze https://dl.noa.codes/futurerestore_mac_v187.sh
did this restore your iphone or the same fdr error
same fdr error for me
homebrew
any recommended fix for this error
what error?
is it the error here #futurerestore-help message
what ios is your X on?
why 14.1?
what
coolstar tweeted
It’s more likely but it’s not guaranteed to get it soon
*semi-untethered and that may not happen
although; i'm curious @rustic blaze ... what are you using to set the nonce?
how do we even know it’s coming when no exploits have officially full on released that are useful
Coolstar doesn't guarantee anything and I can pretty much confirm nothing is happening on iOS 14 at least from CS and co
but even if i downgrade with 14.0.1 blobs the error proves a show stopper
i use repo.1conan.com
dimentio
to set the nonce
@vivid nova
use new term
ah.. isee
is it wrong
nah that works
then what is the issue
i do it the old fashioned way
same
fdr could be based on your internet connection
its just a method of talking to apple
perhaps firewall? maybe interferrence
Oh no that is real old way
also X is finicky because Apple likes to up security
se would work due to the much lower security
SEP is the only difference I would imagine
well, there's different protocols of SEP for X compared to se
restoring is restoring
yeah
be it x or SE
wrong
SEP changes a lot of things
if you think restoring is all the same, then you have a narrow mind of what Apple is capable of...
yes, because you were on 14.2.. were you not?
yes
exactly.
Then you were lucky cause SEP wasn't an issue between 14.2 and whatever you restored to
and 14.2 was signed at that time
what about 14.4
the SEP is compatible with 14.3.. but FR needs to be updated
hence the errors
so going to 187 isn't going to help your case
but how long we have been discussing this fdr issues
if anything; try downgrading from 14.3 to 14.2... then using 14.2 to 14.1
makes sense I haven't used FR since ios 12 or early days ios 13
you're confusing when you switch from SE talk to X
i have to ios devices on ios 14
*two
one SE which i already downgraded
one X which i am trying to downgrade
i think u got my point now
the X won't matter to downgrade when 14.2 is already jailbreakable
yes
i want to downgrade to ios 14.1
why when you're on a jailbreakable firmware
Let me see if I understand you correctly @rustic blaze:
You're on 14.2 with an iPhone X which is jailbreakable via checkra1n
-but, you want to downgrade to 14.1 /in the hopes/ of a semi-untether to be released?
that... is the dumbest thing I've seen all week
bruh, you can jailbreak right now... why would you downgrade and wait when you could've been jailbroken by now?
a user must have choice whatever firmware he wishes to be
sure, but you're wasting time.
Mean to be fair A11 checkra1n is stuck without passcode and similar
He probably wants to jailbreak his A11 device with working SEP on 14, still not happening right now even if he downgrades to 14.1 but yeah
essentially, although it’s technically more likely for 14.1 to receive a jb
i /highly/ doubt it
I’m basically doubtful of it as well but it is a possibility
granted the shred of a possibility that 14 receives a semi-untether, there'll be an abundance of issues with device support and checkra1n will still reign supreme
Eh I doubt device support will be an issue, more so general reliability will be an issue
device support will be huge.. Apple adds different security for different devices based on OS versions.. If people were on 14.0 and some on 14.1 with older (8, 7, 6s) then it might work no problem, but because of faceID and/or other tweak incompatibilities.. I fear bootloopings in the mist
lmao no
you just need to have a PC to jailbreak
you can boot and use the device fine without needing a computer
everyone will prefer semi tethered
semi-un*tethered
And that’s not necessarily wrong but some will prefer the reliability
semi-untether is overrated tbh

you can boot into a normal stock state without needing to checkra1n or have a PC
checkra1n is qupreme
sure, its convenient.. but when you need to re-sideload it because Apple revoked you, it's nearly impossible
@vivid nova read what the guy said above
how will you boot without needing a computer
You're talking Tethered
good
not semi
entitlement alert
how about this: go make it yourself and quit demanding stuff
then stop demanding..
i am not demanding
@rustic blaze
- Tethered requires a computer to boot, this is not like anything commonly used (outside of tethered downgrades)
- Semi-Tethered requires a computer to jailbreak, but the device can be used in a jailed state (similar to checkra1n)
- Semi-Untethered does not entirely require a computer to jailbreak (uses an app usually), but is not full on untethered (similar to odyssey/u0)
- Untethered is you can freely boot into a jailbroken state without needing to do anything, this is extremely rare and the last time it has appeared was around iOS 9 days
i m requesting
requesting and demanding are extremely similar in many cases
give us a stable fr
"requesting" uh-huh
@vivid nova I mean when I occasionally check this channel I usually see the guy wanting something and not understanding what the fuck to do, this has been going on for over 2 weeks if I recall right
no, he's gotten support by countless ppl
either via pins, scrips, walkthroughs, guides, you name it
yeah and he still doesn’t understand what the fuck to do
apparently he does if he's compiled FR and used it...
I mean he doesn’t seem to understand really a whole lot so I’m amazed he pulled that off but eh

could secretly be pwn
why the fuck would the guy secretly be pwn
maybe to test our knowledge on how much we know
which seems to be little 😄
🤣😂
If you do a search you find it everywhere, it always asks the same things 🙈
Just ignore it ✅
@rustic blaze I tried to use the 14.4 sep to downgrade to 14.0 and it didn't work either. fdr that is.
⛷️ 🏂
You can't use beta files to downgrade with release files

Jesus what a discussion. I don't support @rustic blaze because I think the same over this guys as @stiff hazel. @rustic blaze have no clue what he do and is not willing to lern. But I have the same opinion as @rustic blaze what the iOS version concerns. We can see in the security notes, 14.2 have many kernel fixes. So the chance is bigger to get a semi untethered jailbreak for 14.1 with working SEP and passcode as for 14.2.
Yes we can jailbreak right now with checkra1n on 14.2. But we can also jailbreak on 14.1. So why not downgrade to a version where it has a higher chance for a semi untethered jailbreak...
Yeah I know. But I have understand it like that (I am not a dev so correct me if I am wrong), the checkra1n SEP problem with the X right now its that during boot, SEP checks if the kernel is changed or something like that or the other way. So with a semi untethered jailbreak the kernel is not changed during boot and the phone boots normal. The kernel only changed when the phone is jailbreaked and there is no SEP check and no problem anymore? Don't know if I have understand it correct because I am not a dev.
I agree with that. But its easier you can jailbreak "on the go". So I think its not the dumbest thing to have a semi untethered jailbreak if you already have a tethered jailbreak.
Thanks for the clarification.
So if I understand this correctly. The problem with checkra1n is that we modify something in DFU mode? But with a semi untethered we must not modify anything in DFU mode and boot because are already booted. So we have not the problem or I am wrong?
So I don't understand your comment "kernel fixes != sep related" in context with 14.2 security change notes and semi untethered jailbreaks. It is not related with it or?
And from that I conclude that it is the right way to stay on 14.1 so we have no passcode problem with a semi untethered jailbreak or am I thinking wrong somewhere?😅
My focus with this question was more if I was correct that I think we have no passcode problem with semi untethered jailbreaks...?
Ok nice. Thank you for all the clarifications.
@vivid nova then explain this then https://www.reddit.com/r/jailbreak/comments/am0puz/news_happy_futurerestoring_ios_122_beta_sep_is/
@celest basalt Apples since long updated..
beta sep will no longer work for release versions
this was confirmed on 13
Everybody is trying to downgrade to iOS 14.1
In the hope of a jailbreak
And they are experiencing errors
In future restore then y I m only being targeted
@storm apex when have you the last time tried downgrading to 14.1. I have downgrade my iPad Air 2 from 14.2 to 14.1 in december 2020 with v187. Now I have tried downgrading my i7 from 14.3 to 14.1 with the same FR v187 but it don't work. Maybe apple have do some stuff to prevent downgrading in 14.3.
Here.. to settle this: I'll update my i7 to 14.3 and downgrade to 14.0 using 187
Ok cool. I maybe try from 14.3 to 14.2 and if it works further to 14.1.
will do
Is there a guide anywhere to compile marijuanARM’s futurerestore fork? I think you need that one for iOS 14 to work
futurerestore allows you to upgrade/downgrade/restore to unsigned iOS versions if you meet certain requirements
[Tutorial](#futurerestore-help message)
Thank you! And sorry for asking a common question
I’ll check the pins first next time
no worries, common Q's are good.. its just the Q's about how to google stuff...
I need to checkra1n mine first. Was testing a tweak that bootlooped it..
Quick question. Do you think it is better if the FR failed to rstore with iTunes or leef the phone it restore mode and directly run FR?
*leaf

If you futurerestore and it fails, the iphone is in recovery mode (with the itunes logo and the cable). Do you think it is better to restore with itunes then or run FR directly.
Ah wait, my bad. Maybe there is a currupt iOS on the device and then we have also a error with fr. So I think it is the best to restore with itunes and start fresh so avoid maybe an error.
Ok.
after following this tutorial, i get
idevice_event_cb: device 0005301c0e60002e (udid: ffffffffffffffffffffffffffffffff00000309) disconnected
ERROR: Unable to receive message from FDR 0x7fc53ed04d70 (-2). 0/2 bytes
FDR 0x7fc53ed04d70 terminating...
ERROR: Could not read data (-256). Aborting.
Cleaning up...
[exception]:
what=ERROR: Unable to restore device
code=67829777
line=1035
file=futurerestore.cpp
commit count=190:
commit sha =e4a81783769e6800a4efe69a4bab3478069df20e:
Done: restoring failed!
iP8+ GSM, iOS 14.2
i got the sep and baseband by using /sepbb on the telegram bot
on big sur 11.1 MBP 2015 15 inch
only warnings i think, but unfortunately i think i closed that terminal by now
i mean, it was a lot of logs so i didnt scroll through every line to check
just tried with latest sep and baseband flags, same error
ig i could, ive never had connectivity issues with this particular cable tho
searching on this discord server, seems like im not the only one getting this issue
I get it on my iPhone x and what's strange is that I used the same future restore version with the 14.2 files a while back, it worked, but when 14.2 got unsigned, I used the 14.3 files and I get fdr issues now.
oh weird
Some dude was able to downgrade his iphone se (A9) to 14.1 with the 14.3 files but he couldn't do it on his a11 device
very very strange
maybe its a futurerestore bug
probably
oof
ive procrastinated on upgrading from iOS 12.. and now my apps are started to be unsupported
hmm maybe i should upgrade to ios 14.3, then downgrade later, since SEPless checkra1n is always an option to nonceset
should we open a github issue on it r smth?
ya
@storm apex pinging you cause you know more than me
But it’s probably that 14.3 changed something indirectly or patched something with A11
but why specifically with A11?
don’t ask me, they’ve done stuff specifically with A10 and higher and A11 and higher before
hmm u rite u rite
i posted it in m1sta's discord (who made the upgraded futurerestore fork), maybe hell look at it
Just tested i7 from 14.3 to 14.0 using FR 187 and 14.3 sep/bb
Getting firmware manifest from build identity
Extracting LLB.d10.RELEASE.im4p...
Personalizing IMG4 component LLB...
Extracting applelogo@2x~iphone.im4p...
Personalizing IMG4 component AppleLogo...
Extracting batterycharging0@2x~iphone.im4p...
Personalizing IMG4 component BatteryCharging0...
Extracting batterycharging1@2x~iphone.im4p...
Personalizing IMG4 component BatteryCharging1...
Extracting batteryfull@2x~iphone.im4p...
Personalizing IMG4 component BatteryFull...
Extracting batterylow0@2x~iphone.im4p...
Personalizing IMG4 component BatteryLow0...
Extracting batterylow1@2x~iphone.im4p...
Personalizing IMG4 component BatteryLow1...
Extracting glyphplugin@1334~iphone-lightning.im4p...
Personalizing IMG4 component BatteryPlugin...
Extracting DeviceTree.d101ap.im4p...
Personalizing IMG4 component DeviceTree...
Extracting liquiddetect@1334~iphone-lightning.im4p...
Personalizing IMG4 component Liquid...
Extracting recoverymode@1334~iphone-lightning.im4p...
Personalizing IMG4 component RecoveryMode...
Extracting iBoot.d10.RELEASE.im4p...
Personalizing IMG4 component iBoot...
Personalizing IMG4 component RestoreSEP...
Personalizing IMG4 component SEP...
Sending NORData now...
Done sending NORData
Fixing up /var (17)
Creating system key bag (50)
ERROR: Unable to receive message from FDR 0x7ff41e79ba00 (-2). 0/2 bytes
Modifying persistent boot-args (25)
Requesting EAN Data (74)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Got status message
Status: Restore Finished
Cleaning up...
Done: restoring succeeded!```
I’m thinking A11 changed something
Because all these FDR errors are mostly coming from users trying to do A11 downgrades and shit
or... they miscompiled something/VPN/bad internet
Again though I don’t have an A11 device to test
How would we be able to determine if this is the case
Updating Stockholm (55)
Requesting FUD data (36)
Found IsFUDFirmware component AOP
Found IsFUDFirmware component Homer
Found IsFUDFirmware component RestoreTrustCache
Found IsFUDFirmware component StaticTrustCache
Sending IsFUDFirmware image list
Updating baseband (19)
About to send BasebandData...
sending request without baseband nonce
Sending Baseband TSS request...
Request URL set to https://gs.apple.com/TSS/controller?action=2
Sending TSS request attempt 1... response successfully received
Received Baseband SHSH blobs
ERROR: can't locate 'psi_ram.bin' in '/tmp/fffff0667FV'
ERROR: Unable to send baseband data
ERROR: Unable to successfully restore device
Cleaning up...
[exception]:
what=ERROR: Unable to restore device
code=67829777
line=1035
file=futurerestore.cpp
commit count=33:
commit sha =f571dc2949c4ca4c9b5db72fff35878717e5ce0b:
Done: restoring failed!```
iPhone 7 (9.3) from 14.3 to 14.2 using FR 187 and 14.3 sep/bb
Ubuntu
Same FR where i have downgraded my iPad Air 2 in december from 14.2 to 14.1.
The strange thing is, we have all other errors...
Now I try 14.3 to 14.0 how @vivid nova
macOS HS
Have you a test devie where you can test it?
*device
Have you test it with 14.3 sep/bb?
Maybe you can if it is not your main device.
everyone on a X gets that error
got this on an iP8+, so it's probably not just X
seems to at least affect all A11 devices
wait @storm apex after following your tutorial, we can delete the futurerestore_compile folder right
since everything is make installed
That’s what I was talking about guys
I was unable to future restore my x to 14.1
Yes
I was able to restore my iPhone SE
Tried with both 187 and 190
@violet olive
@vivid nova have made some more tests. iPhone 7 from 14.3 to 14.0 with 14.3 sep/bb not working. But with --latest-sep and --latest-baseband flags it worked.
Getting firmware manifest from build identity
Extracting LLB.d10.RELEASE.im4p...
Personalizing IMG4 component LLB...
Extracting applelogo@2x~iphone.im4p...
Personalizing IMG4 component AppleLogo...
Extracting batterycharging0@2x~iphone.im4p...
Personalizing IMG4 component BatteryCharging0...
Extracting batterycharging1@2x~iphone.im4p...
Personalizing IMG4 component BatteryCharging1...
Extracting batteryfull@2x~iphone.im4p...
Personalizing IMG4 component BatteryFull...
Extracting batterylow0@2x~iphone.im4p...
Personalizing IMG4 component BatteryLow0...
Extracting batterylow1@2x~iphone.im4p...
Personalizing IMG4 component BatteryLow1...
Extracting glyphplugin@1334~iphone-lightning.im4p...
Personalizing IMG4 component BatteryPlugin...
Extracting DeviceTree.d101ap.im4p...
Personalizing IMG4 component DeviceTree...
Extracting liquiddetect@1334~iphone-lightning.im4p...
Personalizing IMG4 component Liquid...
Extracting recoverymode@1334~iphone-lightning.im4p...
Personalizing IMG4 component RecoveryMode...
Extracting iBoot.d10.RELEASE.im4p...
Personalizing IMG4 component iBoot...
Personalizing IMG4 component RestoreSEP...
Personalizing IMG4 component SEP...
Sending NORData now...
Done sending NORData
Fixing up /var (17)
Creating system key bag (50)
ERROR: Unable to receive message from FDR 0x7fdce8001180 (-2). 0/2 bytes
Modifying persistent boot-args (25)
Requesting EAN Data (74)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Got status message
Status: Restore Finished
Cleaning up...
Done: restoring succeeded!```
@rustic blaze interesting..
May b it’s only affecting A11
Not A10
I formatted my Mac thrice thinking it might be my Mac
But in vain
@subtle cosmos what FR version are you on?
linux...
Why use an old version of futurerestore?
sometimes older is better
@vivid nova i7 from 14.0. to 14.1 with --latest-sep and --latest-baseband works also. Done: restoring succeeded!
Now I doubt myself that I have the wrong files🧐
Device Identifier: iPhone9,3
Board Config: D101AP
SEP: sep-firmware.d101.RELEASE.im4p
Baseband: Mav16-8.21.01.Release.bbfw
@vivid nova can you confirm?
Really? Oh man. I have look at the iphone wiki https://www.theiphonewiki.com/wiki/MDM9645
yeah, there's multiple versions of the i7
So this is correct https://www.theiphonewiki.com/wiki/PMB9943
Thanks. Now try from 14.1 to 14.2 with 14.3 sep/bb.
it depends, i didn't look at the board number to find my identifier
I simply just ran it through idevicerestore
and it gives you the details
How is the command for this?
Identified device as d101ap, iPhone9,3
Extracting BuildManifest from IPSW
Product Version: 14.3
Product Build: 18C66 Major: 18
Device supports Image4: true
Variant: Customer Upgrade Install (IPSW)
the command for what? idevicerestore?
@subtle cosmos https://www.theiphonewiki.com/wiki/AzulC_18C66_(iPhone9,3)
Where you have found this link? Can found it by clicking me through the page.
Ok, have found the way where I find this site.
SEP is compatible, but baseband not.
If SEP and baseband from the latest signed iOS version is compatible with 14.1, yes.
For now 14.3 SEP and baseband is compatible with 14.x.
Yes, but normally after apple release a new version, you have maybe a week to check if the SEP and baseband is compatible. If it is compatible, you can stay. If not, it is your choice if you upgrade to 14.1 and use checkra1n or stay on 13.5 to have a jailbreak "on the go".
No you can go directly to 14.1.
But it does not matter because you have a checkra1n device. You can always set your nonce on any iOS version to downgrade.
So maybe you fucked up, you can restore to latest version and set your nonce with checkra1n und downgrade to your target iOS version (if the latest SEP and baseband is compatible)
And if you have save your blobs.
Yeah it is maybe a first world problem😅
The good thing is, you have a always working checkra1n device. The only "problem" is when your battery dies and you need to rejailbreak with a computer.
But you can use [[Puck]] to prevent battery die and rejailbreak.
Or [[Sentinel]] but it is not updated for iOS 14.
Yeah is takes down your device at a specific battery percent to prevent battery die.
No. Only set nonce and use futurerestore.
...
can
But I can't tell you how you should backup your device. Don't know if you must first rootfs and backup or something like that. I only start fresh and backup my data manually.
Yes you must look which generator is in your blob and this generator you must set on your device.
Then you are fine.
The good thing is, you can't do it "wrong" if you fucked up, you can checkra1n, set you nonce and try again.
You need macos or linux and you must compile it yourself.
Thats the good thing with checkra1n.
!t futurerestore
futurerestore allows you to upgrade/downgrade/restore to unsigned iOS versions if you meet certain requirements
[Tutorial](#futurerestore-help message)
macos or linux
I am not a pro at compiling. I only follow the tutorials also.
No problem.
you can message https://t.me/rJailbreakBot and use the /sepbb command
Tools for iOS and/or jailbreak.
Save SHSH2, get device info, firmware etc
Donate : https://donate.spydar007.com
Download the iOS 14.1 ipsw
Change the extension to zip
There u will find all your files
BB sep and build manifest
yes
depends what device.. the latest bbfw should be 5.01. otherwise it won't send and you'll error
yes
5.01 is the only one currently signed
so 14.1 is possible
just set your nonce, and you're good
although @slender lance updating wouldn't be smart imo
unless a 14.x semi-untethered jailbreak becomes public, I'd continue saving blobs. Reason being: in the hopes that the support gets rejected or abandoned or doesn't work right, then you've got the chance for a semi-untether by staying
Right now, you're on the best firmware for both semi-tethered and "-untethered jailbreaks
14.1 will always be supported as long as 14 is still being worked on, and we don't see 15 coming until sometime this late summer when WWDC arrives
no. Hence why I state that updating isn't smart (right now)
in the event that future 14.x firmware SEPs don't work with anything on 14.1 or lower, I'll announce it on the SEP checker
you may also add it to your RSS app to view on-the-go updates
and with that thought in mind... I'd stay until such is released. Then update. But until then, I'd stay, but up to you
I highly doubt a 14.x jb is coming soon.. perhaps later on, but you never know which is why blobs are essential
Example a of why not to go to 14
and to top it off.. 14 makes things muuch slower imo
Nah tbf that’s a first and it was iCloud docs lol
that's apple constantly updating stuff.. 'tis like a kid hitting refresh
honestly, 14 was rushed
too much fancy UI stuff and not enough stability, bug fixes and WAAAYY too many checks
iPad didn’t get half the features so it has half the problems lol
That's not normal, pretty sure something else is causing that, not iOS 14 itself
i think the problem is A11 and ios 14.3
@vivid nova the last test was also successful. Can comfirm that all 14.x versions are compatible on i7. Have downgraded my i7 from 14.3 to 14.1 with 14.3 sep/bb. Have also tried all versions successful. Can go from 14.x to whatever 14.x I want.
I thought this was already known
How do I go from iOS 14 to iOS 13.7
You can’t
neither, you need to choose a currently signed version (that is, 14.3) for SEP/BB, since that's what you'll need
this has already been confirmed.
Yeah would only give feedback.
@storm apex found the error
LMAO
Who tf messed up the includes section for xpwn
@storm apex fix this line sed -i '' 's|#include "xpwn/libxpwn.h"|#include "xpwn/libxpwn.h"\n#include "xpwn/img3.h"|' ./xpwn/ipsw-patch/xpwntool.c
No
@storm apex it inserts the that line incorrectly
It makes it all one line
Instead of going down
another fdr error
is it possible to futurerestore from 12.4 up to 13.7?
or are the seps not compatable
you'd have to use 14.3 SEP/BB, and the baseband is not compatible
14.x basebands arent
it may work on a wifi-only iPad or iPod touch though
With iPad5,3 Wi-Fi did not work
oh alright, thank you. would i be able to restore to 14.1 or .2 if i wanted to or are they also not comptable with 14.3?
Yes
alright, thanks!
I'm trying to futuresrestore from 14.3 to 14.1, but I got this error, can anyone help me please?
now my phone is stuck on the green screen mode
not an ios 14 compatible one
Yes, I'm using windows. since I don't have mac, is there any Linux futurerestore version which is compatible with ios 14?
yes
found the tutorial, I'll try the Linux version. Thanks 🙂
Just downgraded my ios version from 14.3 to 14.1 using the linux version. Thanks bro, I really appreciate it.
@vivid nova I might’ve asked this already but does sep ever reopen?
@vivid nova what's up with this
What about it
@warm finch ^^^
I second this
Cuz a11 doesn’t seem to work with downgrade to iOS 14.1 or 14.2 with iOS 14.3 sep/bb files.
If you somehow got an a11 device downgraded, pls let us know!
thanks
I mean, what's with the 14.4b2 SEP? it doesn't say compatible or incompatible
I don't know what rss feed reader you've got, but that should include a description when tapped on
it's a Telegram bot and I just get this
iPhone 7 Plus (A10) , haven't tried the A11 one
A10 is fine but not A11
a11 should work
i meant with the latest future restore A11 has issues
is there anyway to know which version can upgrade or downgrade with futurerestore?
i mean if my iphone on ios12 or ios13, how do i know which ios version can i upgrade or downgrade with futurerestore?
you need blobs for the target version, and a compatible SEP:
!t sep
How to check if the latest iOS version's SEP is compatible with a target iOS version: https://joshblah555.github.io/JoshTV/SEPCheckr.html
right now basically for an iPhone:
- A8 and lower (iPhone 5s/6/6+): 12.4-12.5.1
- A9 and higher (iPhone 6s or newer): 14.0-14.4
Wi-Fi-only iPads and iPod touch that support iOS 13 should be able to restore to 13.4-14.4
(but restoring to 13.x may not work right now)
any version in this range that you have blobs for should work
@celest basalt i cant see drop-down menu in that website
scroll all the way to the bottom
Afaik, fr isn't updated for it, but the sep should still be compat
Yeah but at this moment we can not downgrade with A11. So it should not work.
I think it was good if this post becomes an update with A11 because it can confuse people when they will try to down or upgrade to maybe 14.1 but FR failed and they must force restore to 14.3.

no need to force restore to 14.3 they can use --exit-recovery to exit out of recovery mode @subtle cosmos
i got an ipad air 2 with blobs for 13.7, can i restore?
why would it may not work
cellular iPad: no
Wi-Fi iPad: in theory yes, but I'm not sure with all the FDR errors people are getting if it will work
a8 and lower is 11.3-12.5.1
it is
i think a7/a8 devices are also not affected by the fortnight bug
a7 is also 10.1-10.3.3
(10.1 and the first 10.1.1 build won’t have touch id though)
UPDATED: 2021/02/12
Overview what devices can be downgraded.
(<iOS12 is not very treated here. This is only a quick overview for "new" iOS versions.)
Right now for iPhones:
- A7 (iPhone 5s): 10.1-10.3.2 (tethered without blobs, untethered with blobs) with inferius
10.3.3 (untethered without blobs) with inferius and/or LeetDown - A7 and A8 (iPhone 5s/6[+]): 11.3-12.5.1
- A9 and A10 (iPhone 6s[+]/SE 1st/7[+]): 14.0-14.4
- A11 (iPhone 8[+]/X): 14.3/RC-14.4
- A12 (iPhone XS[Max]/iPhone XR): 14.3/RC-14.4
- A13 (iPhone SE (2nd)/11[Pro][ProMax]): 14.3/RC-14.4
Right now for Wi-Fi-only devices:
Basically same as the iPhone chips + [X][Z].
Addition for AppleTVs:
AppleTV: 13.4-14.4
someone can pin that I'm lazy
look at what i said above
64bit devices that don’t support 13 have 11.3-12.5.1 compatibility
@subtle cosmos
(and A7 has 10.1-10.3.3, with 10.1 & first build of 10.1.1 having broken touch ID)
That doesn't make sense.. Devices that don't support iOS 12 have the capability of updating to iOS 12 and downgrading to 11?
typo :p
Has this been tested? Because afaik, the sep wouldn't go that low
yeah
i’ve restored to 11.3.1 and 11.4.1 with the latest sep multiple times
well, it was when 12.4.x was still latest, but no reason why it should’ve changed
It might've.. Apple loves to patch
time_waste has been unpatched for 7 iOS 12 releases

if they were gonna make the SEP incompatible they would’ve done it months ago
i think they just don’t care enough to at this point
so my iphone 6s+ can’t have 13.3.1 on it
no @blissful fiber
@celest basalt futurerestore wouldn't be nessesary, just use iTunes/Finder
but keep in mind, once you update, you can't jailbreak at this time...
Maybe you can check it with latest now?
And how does it work? Downgrade OTA with LeetDown to 10.3.3 and if you have blobs you can downgrade to 10.1 normally with FR?
you can tethered downgrade to 10.1-10.3.3 (and untethered downgrade to 10.3.3)
inferius can go to 10.1.1 and 10.2 on the 5s, i think i have bundles for it
@shy magnet i've got bundles for apple tv 2 as well
would make it work without seas0nspass
Untethered 10.1-10.2 is not possible?
Have pinned post updated.
without blobs, no.
with blobs, untethered 10.1-10.3.2 downgrades are possible
can 14.4 be downgraded to ios 14.1 A11
Not hoping to face fdr error again
On A11 i see some people on twitter have this error unable to recieve message from FDR 0000000185 (0/2) bytes after sending NORdata to sep
Did some on a11 that update or dowgrade and don’t have that bugs
It's a common issue @rapid creek
I know that but this will fail every time or can work
Till now there are no successful downgrades known on A11 with 14.3 SEP/BB.
14.3 is signed
no it isn’t
14.1 to 13.5 possible? Ipad 7th
no
but no A10?
can i downgrade my iphone 11 thats running ios 14.4 to ios 13.5.1?
i have the blobs for it
damn
Are there any more infos about that?


