#futurerestore-help

1 messages · Page 17 of 1

patent mortar
#

big oof

cursive dirge
#

!!

rustic blaze
#

@subtle cosmos

vivid nova
#

just try again

rustic blaze
#

tried three times

#

same error

#

is 14.3 sep compatible with 14.1

#

i doubt the SEP

vivid nova
#

i seriously blame your FR version

#

you updating it to 190 was a mistake imo

rustic blaze
#

on version 190 i restored my iphone x two days back

#

i really doubt the SEP of 14.3

vivid nova
#

wdym?

#

@rustic blaze try with FR 180

rustic blaze
#

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

vivid nova
#

14.3 sep works fine

#

it restores i7

vivid nova
#

@patent mortar RSS feeds are now available on The SEP Checker.

celest basalt
#

!t sep

mystic axleBOT
nocturne egret
#

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

celest basalt
vivid nova
#

don't use v190

#

v187 works just fine @nocturne egret

vivid nova
#

Hopefully it works..

patent mortar
#

Hmm IFTTT is not letting me use it

#

Is the format correct?

drifting steeple
#

@vivid nova does brew actually support linux?

vivid nova
#

yes

drifting steeple
#

I never knew

#

omfg

drifting steeple
#

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

nocturne egret
vivid nova
nocturne egret
#

uhh i think this source is for v190

sharp latch
#

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

nocturne egret
#

followed the tutorial and FDR error was the result

#

from 14.3 (iPhone X) to 14.2

#

of course i have blobs

sharp latch
#

Can you screenshot the end of the compilation of futurerestore?

nocturne egret
#

what the heck

#

i just used the script posted up there

vivid nova
#

i could upload my 187 and see if y'all can try it

nocturne egret
#

that would be nice

vivid nova
#

granted of course, you have the dependancies compiled

sharp latch
#

Static binary?

nocturne egret
#

windows/macos/linux?

vivid nova
#

macos

nocturne egret
#

thank god i dont have to reboot

vivid nova
#

windows is a nightmare and linux is like trying to enter the white house

sharp latch
#

Is it static or dynamic tho?

vivid nova
#

dynamic

sharp latch
#

“Library not loaded” incoming lol

vivid nova
#

i didn't do any different than y'all.. if you followed the tutorials then it'll work

sharp latch
#

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

vivid nova
#

187 compiled on Catalina ^

#

i think static tbh.. but not all are compiled in

nocturne egret
#

yeah it requires libgcrypt

vivid nova
#

easy to compile

nocturne egret
#

and libgeneral error

#

one homebrew command installed libgrypt

vivid nova
#

compile/install libcrypt from tihm

#

not homebrew

sharp latch
#

^^ don’t use brew for any of it really

#

Just the bare minimum

nocturne egret
#

there's no libcrypt repo in thimstar's repo list

sharp latch
#

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 ?

vivid nova
#

@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

sharp latch
#

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

vivid nova
#

./config for openssl will take time

#

so will make

sharp latch
#

At this point it’s been fixed so it’s ok for now. But I’m gunna save that for sure

vivid nova
#

so just gotta wait it out

sharp latch
#

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.

vivid nova
#

i gave up on editing the configs.. took a good hour to compile openssl but i was able to compile everything after

nocturne egret
#

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>

nocturne egret
#

libcrippy from tihmstar

nocturne egret
#

another question, how can i get source code of futurerestore v187 (not v190 on marijuanARM/futurerestore)

sharp latch
#

git reset --hard commit### that matches 187

nocturne egret
#

commit### means that weird commit hex on github right?

sharp latch
#

Yea

nocturne egret
#

i modified that script above and it's compiling v187

#

AH YES IT COMPILED

#

and there's one mystery left: will it restore properly?

sharp latch
#

No since it doesn’t have the restore boot manifest hash component

#

It will fail half way

nocturne egret
#

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

valid adder
#

because of using an unsiged baseband and or unsigned sep

sharp latch
#

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?

nocturne egret
#

it went away due to futurerestore outputting too many lines

#

i'm recompiling

sharp latch
#

Can you do ls "/usr/local/Cellar/openssl@1.1/1.1.1i/lib"

#

And lmk what comes up if anything

nocturne egret
#

~/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 

nocturne egret
sharp latch
#

Hmm that’s odd as that should actually work. Have you rebooted since installing it?

nocturne egret
#

nah

#

should try rebooting

#

hmm same FDR error again

sharp latch
#

That’s so odd, when it fails it writes a restore log it would be nice to see it

nocturne egret
#

where's the log

#

not in the same folder

#

it's the log copied from the terminal

#

also i checked my shsh is vaild

rustic blaze
#

some one need to fix this FDR error

sharp latch
#

It look like this

rustic blaze
#

@storm apex why does your script compile futurerestore 190

#

on a fresh ly restored mac

vivid nova
#

because the repository was updated @rustic blaze

rustic blaze
#

so how do we compile 187 now

vivid nova
rustic blaze
#

u said 187 works good

nocturne egret
#

you can tweak some code to make it compile v187

vivid nova
rustic blaze
#

get thsi @storm apex after dragging your script

#

in terminal

vivid nova
#

@rustic blaze you didn't drag in any script.

rustic blaze
#

chmod 777 then i dragged the binary

#

from my dropbox

vivid nova
#

so... you renamed the script?

rustic blaze
#

no

vivid nova
#

okay, you downloaded the 187 binary, then tried to use it?

rustic blaze
#

yes

vivid nova
#

@rustic blaze brew install gnutls

rustic blaze
#

get a weird error illegal hardware error

#

futurerestore -t -s -b -m -p

vivid nova
#

screenshot?

#

log output?

rustic blaze
#

ok'

#

installing

#

it

#

may b

#

libcrippy error

#

installing it now

#

when i type make

#

it gives me warnings and stops

vivid nova
#

imagine ppl streaming their errors instead of giving us 0 context to such issues

rustic blaze
vivid nova
#

afaik, you're using 190

nocturne egret
#

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...

celest basalt
#

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?

nocturne egret
#

you also have same error as me

celest basalt
#

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

vivid nova
#

@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

celest basalt
#

when i try that i get the error that it isn't signed

vivid nova
#

you need to use the latest .bbfw and sep.im4p

#

you may extract them from the 14.3.ipsw

celest basalt
#

ah, i'll give it a shot and see if it works

nocturne egret
vivid nova
#

what device?

celest basalt
#

mine is an iphone x

#

it's the 10,3 model

nocturne egret
celest basalt
#

mine is apparently the global variant

rustic blaze
#

i think the version 191 is creating issues

nocturne egret
#

i tried v180, v187, and v190

rustic blaze
#

v180 is no longer for ios 14

nocturne egret
#

v180 is original tihmstar if i remember correctly

#

yes i know

#

but all 3 had the same error message

celest basalt
#

i don't know which version i'm using, i just run the compile script provided

#

it's probably the latest one though

nocturne egret
#

if you use that script you are using v190

celest basalt
#

ah

rustic blaze
#

it shows the version right up there

#

is 14.3 SEP and baseband compatible with 14.1

nocturne egret
#

i think so

celest basalt
#

i don't know about 14.1 but it should be with 14.2

rustic blaze
#

@celest basalt y r u downgrading from 14.3 to 14.2

celest basalt
#

i kinda wanted to see if it works or not, just an experience thing

rustic blaze
#

dont u have blobs for 14.1

celest basalt
#

nah, i got my device used which came with 14.4, couldn't get the 14.1 blobs sadly

rustic blaze
#

oh

celest basalt
#

it's meant for work but i enjoy playing around with it

rustic blaze
#

but this fr 190 sucks

#

any body in the channel

#

give us a error free fr

nocturne egret
#

i have almost all blobs from iOS 11.4.1

#

lol

rustic blaze
#

i have 14 devices

nocturne egret
#

also have blobs for original 14 and 14.1

celest basalt
#

that's lucky, i was too late, i went to save blobs when it got it but missed out on 14.1

rustic blaze
#

starting from i4 to i 10

#

and every blob saved

celest basalt
#

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

vivid nova
nocturne egret
#

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?

vivid nova
#

i've got linux static @nocturne egret

#

vers 187

nocturne egret
#

great

#

could you please send that to me

nocturne egret
#

thanks

#

i stupidly wrote those files on /usr and corrupted my linux installation

vivid nova
#

better linux than windows

rustic blaze
#

What about Mac

#

Static 187

vivid nova
#

doesn't exist...

nocturne egret
#

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

vivid nova
#

you should be able to extract the tarball as-is. then apply perms

nocturne egret
#

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)

vivid nova
#

oof

#

you could try this @nocturne egret

nocturne egret
#

i use artix

#

and also tried that script but it cant detect device in recovery mode

vivid nova
#

what mac are you using? the hackintosh?

nocturne egret
#

macbook pro 16"

#

currently booting linux'

#

triple booting windows, macos, and linux

vivid nova
#

oof.. windows on mac

nocturne egret
#

windows is only for gaming

#

i gonna try old unused hp laptop

nocturne egret
#

damn this laptop is even slow in linux

nocturne egret
#

fuck same error even on clean installed ubuntu with different laptop

rustic blaze
#

Which future restore to compile now

#

187 or 190

#

Got a fresh formatted Mac

nocturne egret
#

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

rustic blaze
#

How to compile version 187

#

@vivid nova

#

@storm apex

drifting steeple
#

oml

#

I just noticed that my ca\lang was on 12

#

the one I used on linux was 8 to compile xpwn

celest basalt
#

!t futurerestore

mystic axleBOT
sharp latch
celest basalt
#

hmm, apparently my SEP is compatible to go back to iOS 13.5 if 14.3 gives me no joy =]

sharp latch
#

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

celest basalt
#

I also tried to use the 14.3 sep to go to 14.1 and it didn't work

sharp latch
#

@celest basalt what version of FR are you using?

dusty coral
#

14.3 sep and baseband is compatible with 14.1 correct?

celest basalt
#

@sharp latch latest version

sharp latch
#

v190 I think it is

celest basalt
sharp latch
#

Yea that doesn’t grab v190 so that makes sense you would get the FDR for iOS 14

vivid nova
#

I'm currently making a 190 static build.. but it'll take time

celest basalt
#

thank you jtv 😄

sharp latch
#

I’m sure you know this but if you compile w/o Odysseus support you can exclude xpwn and make your life easier

vivid nova
#

but.. that just makes life more difficult for older gens

sharp latch
#

Yea but older gens can use v187

vivid nova
#

187 will require you to compile yourself

sharp latch
celest basalt
#

@sharp latch

sharp latch
#

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

celest basalt
#

still doesn't work

#

i guess i gotta wait for 190 static build

sharp latch
#

Did it give the same error? I guess you could but it’s far from impossible, just takes some perseverance

celest basalt
#

ya i got the same error

sharp latch
#

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

celest basalt
#

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

sharp latch
#

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

vivid nova
#

Substitute has nothing to do with futurerestore

celest basalt
#

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

sharp latch
#

Reboot router as well

celest basalt
#

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

nocturne egret
#

that's the exact same error as me

nocturne egret
#

it's just a log copied from terminal

#

and the log using > err.log

sharp latch
nocturne egret
#

yes i have used and i got fdr error

#

log soon

sharp latch
#

Odd man

nocturne egret
#

terminal log

#

stdout log

sharp latch
#

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

nocturne egret
#

hmm then i should try ipad tethering + vpn

sharp latch
#

Wouldn’t hurt

nocturne egret
#

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

sharp latch
#

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

nocturne egret
#

then i must say this

#

fuck this country

#

because this error even happens on clean installed ubuntu 20.10

rustic blaze
#

any static build for mac

jade skiff
#

Hello everyone. I was wondering if updating to 14.2 will break my Face ID?

nocturne egret
#

no

rustic blaze
#

No

#

14.2 is not signed though

rustic blaze
#

Is fdr error due to open ssl error

jade skiff
#

So I should be able to use my 14.2 Blobs and as long as 14.3 is signed it wont cause any problems?

rustic blaze
#

Provided u don’t have any fdr error in future restore

#

That is what many users have been facing off late

jade skiff
#

Oh I get it. How do I know which is compatible? is there a place to check?

mystic axleBOT
rustic blaze
#

@jade skiff if u happen to succeed please also share the log

dusty coral
#

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
#

Bypassed the fdr error in future restore

#

Restoring my iPhone SE to 14.1

vivid nova
#

@rustic blaze you didn't bypass anything.

celest basalt
#

@vivid nova

#

i guess he got lucky

vivid nova
#

huh?

celest basalt
#

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

vivid nova
#

again.. didn't bypass anything

celest basalt
#

yup

vivid nova
#

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

celest basalt
rustic blaze
#

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

vivid nova
rustic blaze
#

dont know whether it s the SEP or fr

sharp latch
#

@vivid nova I’m going to try and statically compile 190 today where did you get stuck?

celest basalt
#

yea FDR error is there

rustic blaze
#

fdr error @sharp latch

sharp latch
jade skiff
#

Will an ubuntu VM work? or do i absolutely need to run it from a live USB?

shy magnet
#

i’ve futurerestored in a vm before

#

it works

celest basalt
#

yeah I've done that too

#

Win10 host, Win7 guest with vbox USB passthrough

rustic blaze
#

Make it work on Mac

drifting steeple
#

so you can see how uh old this is

rustic blaze
#

some one provide the source code for fr v 187

drifting steeple
#

just use the github

#

it aint hard

sharp latch
#

Git clone ; git reset —hard gitCommit##

#

I provide no support good luck

shy magnet
#

don’t even need to reset

#

just git checkout <commit of v187>

rustic blaze
#

I think version 190 is creating havoc

sharp latch
rustic blaze
#

I meant on Mac

#

Where do I apply the above commands @sharp latch

#

After compiling

sharp latch
#

What do you mean? That is a mac, it’s a hackintosh. You run it like any other FR

rustic blaze
#

but on mac we get the fdr errors

#

i have been experiencing this for the past three days

vivid nova
#

@rustic blaze just wait out the errors.. let it finish

rustic blaze
#

no it errors out and says aborting restore

rustic blaze
#

@shy magnet can u type in the complet command

#

git reset

shy magnet
#

it’s literally exactly what i said

#

git checkout <whatever the v190 commit hash is>

rustic blaze
#

willthat resolve fdr issues

#

i am currently facing

#

on my x

rustic blaze
sharp latch
#

^ That’s not 190 that’s 187

celest basalt
#

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

stiff hazel
#

If you get it new it’s probably gonna come on 14

rustic blaze
#

That’s 190 not 187 @sharp latch

rustic blaze
#

@vivid nova

drifting steeple
#

@rustic blaze thats 190

#

wait

#

@sharp latch

#

it matches e4a81783769e6800a4efe69a4bab3478069df20e

#

which is 190 so

drifting steeple
#

@storm apex oml

#

LibreSSL 2.8.3

#

ffs

sharp latch
drifting steeple
#

yeah capt needs to redo the openssl part

drifting steeple
#

@storm apex have you seen this before?

#

idk

#

yeah for some reason the default on my mac is libbrssl

#

or some shit

celest basalt
#

it's not the setup assistant's job

rustic blaze
#

i install openssl through git

#

is that the mistake @drifting steeple @vivid nova

rustic blaze
#

@nocturne egret please share your compiled script for v187

vivid nova
#

@rustic blaze its in the pins

rustic blaze
#

i think @nocturne egret has modified your script

#

i am asking that

#

the one in the pins is for v190

nocturne egret
rustic blaze
#

did this restore your iphone or the same fdr error

nocturne egret
#

same fdr error for me

rustic blaze
#

how did u install openss

#

openssl

nocturne egret
#

homebrew

rustic blaze
#

any recommended fix for this error

vivid nova
#

what error?

rustic blaze
#

fdr error

#

i am using the correct SEP and BB

#

for my X

vivid nova
rustic blaze
#

yup

#

tried two to three times

#

but ........

vivid nova
#

what ios is your X on?

rustic blaze
#

14.2

#

trying to go down to 14.1

#

using 14.3 sep and bb

vivid nova
#

why 14.1?

rustic blaze
#

because 14.1 would get a semi tethered jailbreak soon

#

according to sources

stiff hazel
#

what

rustic blaze
#

coolstar tweeted

stiff hazel
#

It’s more likely but it’s not guaranteed to get it soon

vivid nova
#

*semi-untethered and that may not happen

rustic blaze
#

stay on 14.1

#

yeh may b it will be far

#

but it is coming

vivid nova
#

although; i'm curious @rustic blaze ... what are you using to set the nonce?

stiff hazel
dark nacelle
#

Coolstar doesn't guarantee anything and I can pretty much confirm nothing is happening on iOS 14 at least from CS and co

rustic blaze
#

but even if i downgrade with 14.0.1 blobs the error proves a show stopper

#

dimentio

#

to set the nonce

#

@vivid nova

#

use new term

vivid nova
#

ah.. isee

rustic blaze
#

is it wrong

vivid nova
#

no

#

just a different way

dark nacelle
#

nah that works

rustic blaze
#

then what is the issue

vivid nova
#

i do it the old fashioned way

dark nacelle
#

same

vivid nova
#

fdr could be based on your internet connection

#

its just a method of talking to apple

#

perhaps firewall? maybe interferrence

dark nacelle
#

Oh no that is real old way

rustic blaze
#

i was able to restore my iphone SE

#

i have no firewalls

vivid nova
#

also X is finicky because Apple likes to up security

#

se would work due to the much lower security

dark nacelle
#

SEP is the only difference I would imagine

vivid nova
#

well, there's different protocols of SEP for X compared to se

rustic blaze
#

restoring is restoring

dark nacelle
#

yeah

rustic blaze
#

be it x or SE

vivid nova
rustic blaze
#

then we are asked to save blobs

#

every now and then

dark nacelle
#

SEP changes a lot of things

vivid nova
#

if you think restoring is all the same, then you have a narrow mind of what Apple is capable of...

rustic blaze
#

FYI version 187 restored my X successfully

#

the issues started with v 190

vivid nova
#

yes, because you were on 14.2.. were you not?

rustic blaze
#

yes

vivid nova
#

exactly.

dark nacelle
#

Then you were lucky cause SEP wasn't an issue between 14.2 and whatever you restored to

rustic blaze
#

and 14.2 was signed at that time

vivid nova
#

14.3 up's security

#

(as i already stated)

rustic blaze
#

what about 14.4

vivid nova
#

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

rustic blaze
#

but how long we have been discussing this fdr issues

vivid nova
#

if anything; try downgrading from 14.3 to 14.2... then using 14.2 to 14.1

dark nacelle
#

makes sense I haven't used FR since ios 12 or early days ios 13

rustic blaze
#

i m on 14.2

#

trying for 14.1

vivid nova
#

you said you were on 14.3

rustic blaze
#

emadToday at 1:19 PM
14.2
trying to go down to 14.1
using 14.3 sep and bb

#

see this

vivid nova
#

you're confusing when you switch from SE talk to X

rustic blaze
#

i have to ios devices on ios 14

vivid nova
#

*two

rustic blaze
#

one SE which i already downgraded

#

one X which i am trying to downgrade

#

i think u got my point now

vivid nova
#

the X won't matter to downgrade when 14.2 is already jailbreakable

rustic blaze
#

downgrading X is creating issues

#

14.2 is checkra1n jailbreakable

vivid nova
#

yes

rustic blaze
#

i want to downgrade to ios 14.1

vivid nova
#

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?

rustic blaze
#

yup

#

u understood it right

vivid nova
#

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?

rustic blaze
#

a user must have choice whatever firmware he wishes to be

vivid nova
#

sure, but you're wasting time.

rustic blaze
#

but make a stable fr

#

so that we dont have any show stoppers

stiff hazel
vivid nova
#

i'd risk no passcode over a free device

#

just keep icloud on 😛

stiff hazel
#

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

vivid nova
#

so, this issue is still a dumb stalemate

stiff hazel
#

essentially, although it’s technically more likely for 14.1 to receive a jb

vivid nova
#

i /highly/ doubt it

stiff hazel
#

I’m basically doubtful of it as well but it is a possibility

vivid nova
#

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

stiff hazel
#

Eh I doubt device support will be an issue, more so general reliability will be an issue

vivid nova
#

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

rustic blaze
#

checkra1n needs a pc

#

to boot

stiff hazel
#

lmao no

#

you just need to have a PC to jailbreak

#

you can boot and use the device fine without needing a computer

rustic blaze
#

everyone will prefer semi tethered

stiff hazel
rustic blaze
#

how will you boot without needing a computer

#

on checkra1n

stiff hazel
#

And that’s not necessarily wrong but some will prefer the reliability

vivid nova
#

semi-untether is overrated tbh

stiff hazel
stiff hazel
rustic blaze
#

checkra1n is qupreme

vivid nova
#

sure, its convenient.. but when you need to re-sideload it because Apple revoked you, it's nearly impossible

stiff hazel
#

@vivid nova read what the guy said above

rustic blaze
#

but.......

#

unc0ver and oddyssey

#

are far or more less

vivid nova
#

how will you boot without needing a computer
You're talking Tethered

rustic blaze
#

good

vivid nova
#

not semi

rustic blaze
#

any ways guys

#

we are deviating

#

give us a stable fr

vivid nova
rustic blaze
#

be it u0 or checkra1n

#

or oddyssey

#

??

vivid nova
#

how about this: go make it yourself and quit demanding stuff

rustic blaze
#

i wish i cld make 1

#

but

#

i am not skilled

#

to make

vivid nova
#

then stop demanding..

rustic blaze
#

i am not demanding

stiff hazel
#

@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
rustic blaze
#

i m requesting

stiff hazel
vivid nova
rustic blaze
#

yes

#

guys try ur level best

vivid nova
#

bruh..

#

We're not gunna do anything if you keep talking like this

stiff hazel
#

@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

vivid nova
#

either via pins, scrips, walkthroughs, guides, you name it

stiff hazel
vivid nova
#

apparently he does if he's compiled FR and used it...

stiff hazel
#

I mean he doesn’t seem to understand really a whole lot so I’m amazed he pulled that off but eh

vivid nova
#

I think it's a disguise

stiff hazel
vivid nova
#

could secretly be pwn

stiff hazel
#

why the fuck would the guy secretly be pwn

vivid nova
#

maybe to test our knowledge on how much we know

sleek whale
#

which seems to be little 😄

celest basalt
#

Just ignore it ✅

celest basalt
#

@rustic blaze I tried to use the 14.4 sep to downgrade to 14.0 and it didn't work either. fdr that is.

drifting steeple
#

⛷️ 🏂

vivid nova
subtle cosmos
# vivid nova that... is the dumbest thing I've seen all week

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.

subtle cosmos
#

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.

celest basalt
vivid nova
#

@celest basalt Apples since long updated..

#

beta sep will no longer work for release versions

#

this was confirmed on 13

celest basalt
#

oh ok

#

thx

rustic blaze
#

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

subtle cosmos
#

@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.

vivid nova
#

Here.. to settle this: I'll update my i7 to 14.3 and downgrade to 14.0 using 187

subtle cosmos
#

Ok cool. I maybe try from 14.3 to 14.2 and if it works further to 14.1.

vivid nova
#

will do

subtle cosmos
#

Or 14.3 directly to 14.0.

#

I have time this weekende an repot back.

patent mortar
#

Is there a guide anywhere to compile marijuanARM’s futurerestore fork? I think you need that one for iOS 14 to work

mystic axleBOT
#
futurerestore

futurerestore allows you to upgrade/downgrade/restore to unsigned iOS versions if you meet certain requirements

[Tutorial](#futurerestore-help message)

patent mortar
#

Thank you! And sorry for asking a common question

#

I’ll check the pins first next time

vivid nova
vivid nova
subtle cosmos
#

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

subtle cosmos
#

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.

patent mortar
# mystic axle

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

celest basalt
#

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.

patent mortar
#

oh weird

celest basalt
#

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

patent mortar
#

maybe its a futurerestore bug

celest basalt
#

probably

patent mortar
#

specifically to do with A11

#

maybe i should try 14.1 instead..?

celest basalt
#

nope

#

i tried that already

patent mortar
#

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

patent mortar
celest basalt
#

ya

stiff hazel
#

@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

patent mortar
#

but why specifically with A11?

stiff hazel
#

don’t ask me, they’ve done stuff specifically with A10 and higher and A11 and higher before

patent mortar
#

hmm u rite u rite

patent mortar
#

i posted it in m1sta's discord (who made the upgraded futurerestore fork), maybe hell look at it

vivid nova
#

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!```
stiff hazel
#

I’m thinking A11 changed something

#

Because all these FDR errors are mostly coming from users trying to do A11 downgrades and shit

vivid nova
#

or... they miscompiled something/VPN/bad internet

stiff hazel
#

Again though I don’t have an A11 device to test

stiff hazel
subtle cosmos
#
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

vivid nova
#

macOS HS

subtle cosmos
#

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.

patent mortar
#

oof

#

thats what they said on m1sta's discord

celest basalt
#

everyone on a X gets that error

patent mortar
#

seems to at least affect all A11 devices

patent mortar
#

wait @storm apex after following your tutorial, we can delete the futurerestore_compile folder right

#

since everything is make installed

rustic blaze
#

That’s what I was talking about guys

patent mortar
#

you got the same error?

rustic blaze
#

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

subtle cosmos
#

@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!```
patent mortar
#

@rustic blaze interesting..

rustic blaze
#

May b it’s only affecting A11

#

Not A10

#

I formatted my Mac thrice thinking it might be my Mac

#

But in vain

vivid nova
#

@subtle cosmos what FR version are you on?

subtle cosmos
#

187

#

Ubuntu

vivid nova
#

linux...

celest basalt
#

Why use an old version of futurerestore?

vivid nova
#

sometimes older is better

subtle cosmos
#

@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?

vivid nova
#

baseband is ICE

#

@subtle cosmos ICE16-5.01.01.Release.bbfw

#

for 9,3 ios 14.3

subtle cosmos
vivid nova
#

yeah, there's multiple versions of the i7

subtle cosmos
#

Thanks. Now try from 14.1 to 14.2 with 14.3 sep/bb.

vivid nova
#

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

subtle cosmos
#

How is the command for this?

vivid nova
#
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
#

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.

rustic blaze
#

u cant downgrade back to ios 13

#

due to SEP

#

incompatibility

#

yup

subtle cosmos
#

SEP is compatible, but baseband not.

rustic blaze
#

13.5 ia better

#

than 14.1

subtle cosmos
#

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.

rustic blaze
#

i7plus is good on ios 13

#

my perecption

subtle cosmos
#

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.

celest basalt
subtle cosmos
#

Or [[Sentinel]] but it is not updated for iOS 14.

celest basalt
#
Sentinel

Stop having to re-jailbreak your battery dies! — What is Sentinel?

Author

MegaDev

Version

1.3.1

Bundle ID

com.megadev.sentinel

More Info
subtle cosmos
#

Yeah is takes down your device at a specific battery percent to prevent battery die.

#

No. Only set nonce and use futurerestore.

subtle cosmos
#

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

mystic axleBOT
subtle cosmos
#

macos or linux

#

I am not a pro at compiling. I only follow the tutorials also.

#

No problem.

celest basalt
rustic blaze
#

Download the iOS 14.1 ipsw

#

Change the extension to zip

#

There u will find all your files

#

BB sep and build manifest

vivid nova
#

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

sharp latch
vivid nova
#

and to top it off.. 14 makes things muuch slower imo

sharp latch
#

Nah tbf that’s a first and it was iCloud docs lol

vivid nova
#

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

sharp latch
#

iPad didn’t get half the features so it has half the problems lol

night harbor
rustic blaze
#

i think the problem is A11 and ios 14.3

subtle cosmos
#

@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.

full osprey
#

I thought this was already known

dire burrow
#

How do I go from iOS 14 to iOS 13.7

full osprey
#

You can’t

celest basalt
#

neither, you need to choose a currently signed version (that is, 14.3) for SEP/BB, since that's what you'll need

vivid nova
subtle cosmos
#

Yeah would only give feedback.

drifting steeple
#

@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

drifting steeple
#

No

#

@storm apex it inserts the that line incorrectly

#

It makes it all one line

#

Instead of going down

rustic blaze
#

another fdr error

ionic ledge
#

is it possible to futurerestore from 12.4 up to 13.7?

#

or are the seps not compatable

celest basalt
sleek whale
#

14.x basebands arent

celest basalt
#

it may work on a wifi-only iPad or iPod touch though

celest basalt
ionic ledge
#

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?

ionic ledge
#

alright, thanks!

warm finch
#

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

vivid nova
#

@warm finch hard reboot and retry

#

also.. what FR are you using?

shy magnet
vivid nova
#

obv not

#

seeing as its windows

warm finch
#

Yes, I'm using windows. since I don't have mac, is there any Linux futurerestore version which is compatible with ios 14?

vivid nova
#

yes

warm finch
#

found the tutorial, I'll try the Linux version. Thanks 🙂

warm finch
#

Just downgraded my ios version from 14.3 to 14.1 using the linux version. Thanks bro, I really appreciate it.

rustic blaze
#

@warm finch what device

#

A10 or A11

celest basalt
#

@vivid nova I might’ve asked this already but does sep ever reopen?

vivid nova
#

huh?

#

wdym?

#

no

celest basalt
rustic blaze
#

What about it

patent mortar
#

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!

vivid nova
#

@celest basalt happy birthday

#

What about it? The link?

celest basalt
#

thanks

celest basalt
vivid nova
#

I don't know what rss feed reader you've got, but that should include a description when tapped on

celest basalt
vivid nova
#

Oof.. Maybe I'll include it in the heading

#

There, fixed. May need to refresh

warm finch
rustic blaze
#

A10 is fine but not A11

vivid nova
#

a11 should work

rustic blaze
#

i meant with the latest future restore A11 has issues

dusk salmon
#

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?

celest basalt
#

!t sep

mystic axleBOT
celest basalt
#

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

dusk salmon
#

@celest basalt i cant see drop-down menu in that website

celest basalt
#

scroll all the way to the bottom

dusk salmon
#

oh it's my PC error

#

wow, its so useful, thanks

subtle cosmos
vivid nova
#

Afaik, fr isn't updated for it, but the sep should still be compat

subtle cosmos
#

Yeah but at this moment we can not downgrade with A11. So it should not work.

subtle cosmos
dusky dock
rustic blaze
#

no need to force restore to 14.3 they can use --exit-recovery to exit out of recovery mode @subtle cosmos

maiden citrus
#

why would it may not work

celest basalt
maiden citrus
#

its wifi

#

are the fdr errors only for a11 or for all devices?

celest basalt
#

oh it is?

#

I thought SEP checker said only 12.4

shy magnet
#

yeah

#

nah

celest basalt
shy magnet
#

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)

subtle cosmos
#

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

celest basalt
#

someone can pin that I'm lazy

shy magnet
#

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)

vivid nova
shy magnet
#

typo :p

vivid nova
#

Has this been tested? Because afaik, the sep wouldn't go that low

shy magnet
#

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

vivid nova
#

It might've.. Apple loves to patch

shy magnet
#

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

blissful fiber
#

so my iphone 6s+ can’t have 13.3.1 on it

vivid nova
#

no @blissful fiber

blissful fiber
#

well time to wait for a new vulnerability

#

aka 10 years

vivid nova
#

@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...

subtle cosmos
subtle cosmos
#

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?

shy magnet
#

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

vivid nova
#

@shy magnet i've got bundles for apple tv 2 as well

#

would make it work without seas0nspass

subtle cosmos
#

Have pinned post updated.

shy magnet
#

with blobs, untethered 10.1-10.3.2 downgrades are possible

rustic blaze
#

can 14.4 be downgraded to ios 14.1 A11

subtle cosmos
#

Try it.

#

But don't know if beta blobs works.

rustic blaze
#

Not hoping to face fdr error again

rapid creek
#

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

vivid nova
#

It's a common issue @rapid creek

rapid creek
subtle cosmos
#

Till now there are no successful downgrades known on A11 with 14.3 SEP/BB.

rustic blaze
#

I just upgraded to 14.3

#

On a11

#

14.2 sep BB was successful on a11

full osprey
#

14.3 is signed

shy magnet
mystic hazel
#

14.1 to 13.5 possible? Ipad 7th

full osprey
#

no

valid adder
#

A11 can go to 13 with some hacks

#

No passcode/faceid tho

full osprey
celest basalt
#

can i downgrade my iphone 11 thats running ios 14.4 to ios 13.5.1?

#

i have the blobs for it

celest basalt
#

damn

subtle cosmos