futurerestore-help

[normal geyser]

did i chmod wrong

[celest basalt]

no that looks fine, but you're missing some dependencies

what distro/version

Updated my iPhone 6s IOS 13.3.1 >> 14.3 successfully

[normal geyser]

mint

20.1

[elder palm]

can I update to ios 14.3 using futurerestore with A12 blobs? or should I update to 14.3 rc while is still signed right now?
I’d wait until a jailbreak is released but Im not sure if futurerestore works on A12 and I don’t wanna miss 14.3 rc before apple stops signing it

[unreal bison]

Bad news RC is not signed anymore

[elder palm]

ouch

it hurts

:(

guess i’m stuck on 13.5 now

[unreal bison]

Same waiting on a FR fix hopefully

[celest basalt]

It is no longer signed

[elder palm]

can I futurerestore to ios 14.3 tho? never tried before

[celest basalt]

https://twitter.com/marijuanarm/status/1359518648071827459

adam (@marijuanARM)

if you’re not on 14.3 & you’re on A11+, DO NOT FUTURERESTORE. STAY WHERE YOU’RE AT.

Twitter · Feb 10, 2021, 3:04 PM

[normal geyser]

true

[covert ibex]

very cool adam

[normal geyser]

wtf is libzip.so.2

i have libzip installed

[unreal bison]

try the i386 version

[celest basalt]

maybe wrong version

[covert ibex]

maybe adam is hearing our prayers

[celest basalt]

did you install the -dev package

[normal geyser]

yes

i did libzipios++-dev

[violet lotus]

@elder palm we all in your case 😞

[normal geyser]

wait

there's a normal dev

nope i have that

[celest basalt]

Damn...I’m on A11 13.7 and have blobs saved for 14.3 but I can’t even future restore right now...

[covert ibex]

yikes just realized i only saved blobs up to ios 14.1

and just did 14.3RC on shsh host last night

[celest basalt]

That’s alright. 14.1 is supported

[covert ibex]

ye cstar might just release 14.3 first though

[celest basalt]

But right now it doesn’t even matter because of this FDR error

[covert ibex]

mhm

[glacial remnant]

There are fork which are working no?

[celest basalt]

his fork was the working one, but it's broken on A11 rn

[glacial remnant]

oh okay, thanks

[sage briar]

it is

[gusty iris]

Thanks but its utterly useless due to FDR error (im A11)

[gusty iris]

literally this is me rn but 13.6.1

[idle stirrup]

Does A12 have the FDR error too? Thought it was A11 and down?

[burnt siren]

anyone got latest fr compiled

the fixed 14 version

[sage briar]

check pinned messages

[idle stirrup]

What does there is no feedback mean

Oh, didnt realize the sentence was joined. so nobody has used future restore on A12 and up to know if it works?

[sage briar]

Something like that

I think

[idle stirrup]

well i guess ill give it a shot then

Will having a different generator set change your ap nonce? Becuase I'm getting two difference nonces

[celest basalt]

yes

[idle stirrup]

ah ok so I should set my generator in unc0ver to whatever generator i have set in my 14.2 shsh then see if my nonce matches?

I've been out of the scene for a while, sorry

[celest basalt]

yes

[shy magnet]

DO NOT FUTURERESTORE TO 14.0-14.3 IF YOU’RE ON A11 OR HIGHER

[gusty trench]

maaaan that's what I came to ask

it's the 13.5 life for me

[idle stirrup]

ah so the FDR error is still not fixed?

[gusty trench]

check pins

[idle stirrup]

The pin didnt make sense to me, from what i read A12 and up wasnt tested A11 and down had the FDR

[lilac holly]

my guess is someone finally tested and the tweet reflects that

[gusty trench]

yeah I read a bunch of replies for that tweet, the consensus is not to use it for A12 and up

[idle stirrup]

ah ok i see. oh well im jailbroken now just figured id jump to ios14 when i had a chance

[gusty trench]

I figured the same, missed the chance to jump to 14.3 safely

[idle stirrup]

yeah I havent even been on r/jailbreak for like a year, didnt know we were on that yet

[celest basalt]

does futurerestoring to 14.2 cause the fdr error?

[subtle cosmos]

Futurerestore was used on iOS 13 and A12 in the past and it worked (there was a post and a tut on reddit). But nobody have test it with A12+ to go from iOS 13.X to 14.X because there is no jailbreak for A12+ on 14.X so nobody will risk his jailbreak an go from jailbroken 13.X to unjailbroken 14.X with A12. So there is no feedback on reddit or here. The probability is also verry high that A12+ have the same FDR error as A11.

[celest basalt]

ive heard it only affects >14.3 restores

[green onyx]

does adam plan on fixing futurerestore

[idle stirrup]

ahh ok i see. I really dont use my jailbreak much so i might be able to. i'd be going to 14.2 because i missed 14.3 completely

[subtle cosmos]

No, A11+ all restores.

[subtle cosmos]

I don't remenber where I have read this so I can give you a source. But I mean he have say that he not plan to update it. It is not known what the error is or if FR can fix this.

[celest basalt]

if i at least try futurerestore to 14.3 and it fails would i still have my current ios?

[subtle cosmos]

But maybe @shy magnet can say something. But I think when the error can not be localized there is nothing to fix.

[idle stirrup]

youd be stuck updating i believe

[celest basalt]

fuck

[green onyx]

@subtle cosmos WHEN FR GETS FIXED, can i use checkra1n WITH DISABLED SEP to set generator and fr to a firmware WITH SEP?

[subtle cosmos]

I have not tried this. But others here have tried it. They say if it fails you can kick the device out of recovery and all is fine. But don't know.

[subtle cosmos]

Yes.

In the past that work.

[green onyx]

fr?

[subtle cosmos]

Futurerestore works in the past with disabled SEP. So when apple don't make tricky fixes it should work IF the error can be fixed with futurerestore.

But @sharp latch have make a couple of tests last time. Maybe he know more IF it can be fixed with FR or not.

I am not a dev or something like that. Have only test it on my own devices and have collected the results from others here and have make the pinned post with all in it.

[green onyx]

tf is the fdr error tho

tf does fdr stand for

[subtle cosmos]

Don't know, I am not a dev. Latest tests from @sharp latch shows that the SEP panics within the restore. Maybe you can scroll up and look his comments.

[celest basalt]

iPad5,3 updated to IOS 14.3 successfully!

[green onyx]

nice

[burnt siren]

can we get captinc's script pinned here

it's a lifesaver

[young nova]

^

[celest basalt]

what script

[young nova]

So if I'm understanding correctly, as a A12 chip XSMax, I have SHSH blobs for 14.0-14.2 using blobsaver on Mac. So what im reading is that i cant update to 14.2 because there are faceID errors and some other things that arent working on future restore, right?

[celest basalt]

this is already pinned

[young nova]

im sitting on 13.5 with unc0ver

[subtle cosmos]

Read pinned posts.

[young nova]

thanks @subtle cosmos

[burnt siren]

https://captinc.me/tutorials/futurerestore_compile.sh

[celest basalt]

yeah it's pinned already just have to follow the message links

[subtle cosmos]

[Tutorial] How to use discord

[idle stirrup]

lol as someone who has never been into using discord, that took me while to figure out what people meant by pinned messages

[shy magnet]

nfr

[celest basalt]

someone said SEP panic

seems to be something new with 14.4 too

[burnt siren]

can’t expect people to press 3 different links

and “tutorial” isn’t very explicit either

i’d consider a tutorial as how to use not how to compile

[cinder trail]

man checkra1n is useless now futurerestore

dang looks like apple can patch bootrom exploits

[zealous bridge]

thats what heavily paid security researches can do for you

its not patched, mitigated would be a better term

[idle stirrup]

Wait so I would be able to try future restore and if I get an fdr error I just kick it out of dfu or whatever?

[zealous bridge]

By the time you get a FDR error your phone will be unusable (what do you expect, you’re stopping in the middle of a system restore), so you’ll have to DFU restore via Itunes/Finder and be forced to update to the latest version

[idle stirrup]

ohh ok. I wasnt sure when that error occured

[agile veldt]

f

[celest basalt]

I mean I successfully got out of recovery once after futurerestore segfaulted in the middle of a restore but that must have been an early stage

[zealous bridge]

Yeah im guessing that was before the original partitions were deleted

[violet lotus]

Sooooo what people on 13.5 A12+ can do nowww
Saved all my 14.x blobss
I think i will not get off 13.5 until ios 15 release 😞😞😞

[celest basalt]

Fuck iOS 14, we stay on 13.5 waiting for IOS 15 🤷‍♂️

[gusty trench]

[normal geyser]

with or without updating

[celest basalt]

without

[violet lotus]

@celest basalt yess 👍🏼👍🏼

[celest basalt]

it booted back to 13.3 fine when I was trying to FR to 13.5 (before iOS 14 was a thing)

[celest basalt]

That means starting from iPhone X?

[dull swallow]

SEP incompatibility

it’s incompatible for A11+

like why

they never do that

[zealous bridge]

iPhone X is A11

yes

[dull swallow]

mhm

[celest basalt]

iPhone 8 too

Oh shit, I stayed on iOS 13.5 to update when a jb is released

[zealous bridge]

continue staying there

[celest basalt]

Is there any hope in the future for sep compatibility?

or a fix for futurestore?

[zealous bridge]

looking very very unlikely atm

for futurerestore

and once a sep is incompatible there is no chance that you can downgrade

[celest basalt]

Gets it is time to buy an iPhone 12 Pro on iOS 14.3

[dull swallow]

only way you can fix a SEP compatibility error is SEPROM exploit

which needs a bootrom exploit

as well

so good luck

or apple does a downgrade party

[celest basalt]

Lots of work for sure, doesnt sound promising at all

[dull swallow]

FR is practically dead for 14-14.3

and of course that had to be the versions that get an exploit

[celest basalt]

Typical apple -.-

[zealous bridge]

a seprom exploit doesn’t necessarily need a bootrom exploit, it’s just that the blackbird vuln was found in such a way that a bootrom exploit was needed to use it

[celest basalt]

So there is hope?

[copper nacelle]

no

[zealous bridge]

hope is not the right word

wishful thinking is probably better

lol

[celest basalt]

True

[maiden citrus]

I compiled FR using Capt's .sh script and am getting a symbol not found libimg4tool.0.dylib even though when i go to /usr/local/lib/, libimg4tool.0.dylib is there

edit: just had to rerun the script lol

[rustic blaze]

Getting these errors A10x

Downgrading from iOS 14.4 to 14.2

[rustic blaze]

but this is on A10 x

not A11

[shy magnet]

i think that’s just an idevicerestore issue

when 14.2 was still signed

i couldn’t downgrade from 14.3 to 14.2

with futurerestore

or idevicerestore

finder worked fine though

just something that needs to be fixed ig

[rustic blaze]

tryong with 14.3 rc now

wish me cluck

same issue with 14.3 also

[uneven hornet]

hey sorry if this isnt the right place to ask. Ive never used future restore and was wondering if someone could please explain to me how to use it. I have an Iphone 8 Plus on ios 13.5 jailbroken with uncover and missed the window to update to 14.3 rc but i do have blobs saved for it. would it be possible to use future restore to update?

😦

was gonna update yesterday and was like eh im tired ill just do it tomorrow

RIP

[rustic blaze]

Not right now

Future restore is fucked

[sharp latch]

Sep panic not Fr (RSEP = RestoreSEP) 14.1 destination kernel. A11 chip. 14.3/14.4 sep

https://www.reddit.com/r/TweakBounty/comments/lgxlac/25143_updated_working_futurerestore_for_a12/?utm_source=share&utm_medium=ios_app&utm_name=iossmf this is dumb AF in my opinion

You can’t update a program when apple patched the kernel and or sep itself.

[dusty coral]

Why does apple patch a11 devices alot lol

[sharp latch]

And to be very specific, the FDR err at the beginning is due to SEP. the FDR erro half way though after sending the file system is an SSL err. Compile SSL from source and it fixes the ladder but the former isn’t fixable IMO.

Anyone on 14.4 who DGAF can use 14.5 beta SEP to restore to 14.4 or vise versa and guess what? It fucking works so again why people gathering hundreds of $ together for?

I’m kinda triggered by this yes but that’s because nobody listens to JTV or I and it’s annoying as hell

[dusty coral]

So a11 is shit out of luck basically?

[sharp latch]

For now yea. But it will get iOS 15 and 14.4 will be jailbreable down the line so it’s just a tough spot RN

Stay, save blobs, use checkra1n

[inner sable]

😔

[dull swallow]

https://twitter.com/joshblah555/status/1359566214314397698?s=21 josh thinks it’s SEP

🅙🆃🆅 (@Joshblah555)

@horatiohno We've been looking into the FDR errors for quite some time now and have come to the conclusion that the SEP just isn't compatible.

Somewhere along the line, Apple has patched something to disallow this. The repairability is extremely low.

Twitter · Feb 10, 2021, 6:13 PM

[shy magnet]

not the issue i’m talking about

[dull swallow]

oh lmao

[sharp latch]

This is the fix

[shy magnet]

wait

it just needed latest openssl?

that's fucking dumb

[sharp latch]

Yessir

Tested myself brew fucks it for some reason.

[rustic blaze]

@sharp latch u mean to say this error is due to open ssl

so do i have to reinstall openssl

or format my Mac

[sharp latch]

1 what the hell is img_small
2 yes just remove your Brew SSL , compile open SSL like I said in the screenshot. Recompile future reatore and it should work

Since your err is the one after mounting file systems and it’s a10 it’s not SEP it’s open SSL

[rustic blaze]

https://cdn.discordapp.com/attachments/688124783400845336/809233810226806854/image4.jpg

I meant this error

for recompiling fr

[sharp latch]

Yes that err follow my directions if possible

[rustic blaze]

we need a clean Mac

or

???

[sharp latch]

No just brew uninstall open ssl and follow the steps in the screenshot

[rustic blaze]

how come open ssl have a error

when i had just future restored my Iphone SE

with the same system a few days back

As a matter of fact I have installed in the same way as mentioned above @sharp latch

[sharp latch]

When you run the script it downloads and installs brew open ssl I’m 90% sure. You would have to edit the script or just run make clean make

After removing old SSL and replace with new one. I had that some err a million times. Only way to fix is with latest OpenSSL. Otherwise I’m the dumped crash logs it mentions http errors

[rustic blaze]

i install openssl first , then i run the script and then the last part is idevicerestore

If i am wrong correct me

[sharp latch]

I mean when you run the script I assume it will overwrite your open SSL. Just run the script so it downloads everything. Install the correct OpenSSL. Cd into the future restore folder and run make clean ; make

[rustic blaze]

so first futurerestore then open ssl

right

how do we uninstall

already compiled fr

[sharp latch]

Brew uninstall? I’m not 100% Sind it’s 130 am lol

[gaunt atlas]

Reinstalling openssl may resolves fdr error?

[sage briar]

Will it be possible to restore iPhone SE 2020 to 14.2 with blobs when JB comes out?

or 14.3

[sharp vessel]

does futurerestore still work with a9x?

[sage briar]

it should

[subtle cosmos]

Yeah thats annoying. People don't know much about it or the tests that you or other have already made and they think that all can be fixed so they make such bounties. Its the same with the twitter kids they always scream for eta. They don't know much about the hard work that was made in the background. The only thing they can is "I WANT I WANT I WANT! >NOW!<".

[sage briar]

#futurerestore-help message could someone please answer it?

[zealous bridge]

@sage briar check pins

[celest basalt]

YouTube Reborn

YouTube Customizer

Author

SarahH12099

Version

2.0.0.2

Repo

Twickd

Bundle ID

com.twickd.sarahh12099.youtube-reborn

More Info

View on Parcility

Twickd - Page 1/2 · Feb 11, 2021, 9:53 AM

[dull swallow]

lol

[zealous bridge]

why here

[dull swallow]

because i’m finding repos lol

oh shit

[zealous bridge]

this is

[dull swallow]

thought this was not commands

[zealous bridge]

not the place

[dull swallow]

bot

LMAO

[zealous bridge]

lol

[sage briar]

So it may work or dont, yes?

[dull swallow]

it wont ever work

SEP is incompatible on A11+

[sage briar]

you mean iOS 13 and 14 SEP is incompatible?

on A11+

[dull swallow]

yes basically

the latest SEP is incompatible with 14.0-14.3

[sage briar]

Below A11 is compatible 13 and 14?

[dull swallow]

yes

[dull swallow]

but baseband doesnt work on cellular

devices

[sage briar]

But I want to update from 13.5.1 to 14.x when jailbreak will be released

It will not be possible?

SE 2020

blobs I have

[dull swallow]

not possible se 2020 is A11+

[sage briar]

Why? I want to update to 14.x and 14.x is compatible with other 14.x

doesnt matter I am on 13.5.1 now

afaik

[dull swallow]

because apple doesnt want you to

[sage briar]

Thats weird

[celest basalt]

but according to pins even wifi iPads fail to restore to 13.x, only Apple TVs work 🤔

[dull swallow]

wifi ipads that dont have A12 chip maybe

[celest basalt]

well idk but how do A12 users even downgrade to 13.x without a nonce setter

[dull swallow]

true

[sage briar]

So I am forever stuck on 13.5.1

[celest basalt]

or hope FR still works for 14.4-14.5 when they drop the new exploit

[subtle cosmos]

A few people and I have test downgrading iPads wifi only to iOS 13.X and get the FDR error.
#futurerestore-help message
@vivid nova have successfully test it on his appletv.

[celest basalt]

what iPads were tested? because A12 is out of the question, there's no A11, and A10- should work 🤔

but then now emad also got an FDR error with A10X downgrading to 14.3 and 14.2

[subtle cosmos]

Yeah only iPads <=A10X

[celest basalt]

yeah but how does even 14.3 not work on A10X, maybe it's different from A10?

but the checkra1n SEP exploit works on A10X afaik

[subtle cosmos]

A10X have also the error?

Wait, we must separate this. The tests with the iPas are only trying downgrading from 14.x to 13.x because they have not baseband. But that don't work. Only on appletvs.

[celest basalt]

yeah here

this isn't even to 13.x but it still doesn't work

[sage briar]

But is it fore sure that I will not be able to restore to 14.2/3 A13 with blobs?

[subtle cosmos]

When A10X have now also errors trying downrade from 14.X to 14.X then this is new. On my A10 iPhone 7 it works.

[celest basalt]

JTV said it seems unlikely it can be fixed

[sage briar]

fuck

[sharp latch]

No (in theory sending the rsep with panic the device) but no one has tried

[sage briar]

That is bad

That blobs are then totally useless

A11 and below is checkra1nable and a bove A11 it does not work

[sharp latch]

If it was me I know you can test it. If you cancel the restore right after sending NOR data you can exit recovery. If I’m you see unmouting file systems then you know you can in theory go to 14.2 but I’m 99% sure it’s nothing to do with what’s on the device, it’s the combination of kernelcache(14.1) and RSEP(14.4) that won’t work. That combo causes panic so you can’t get there now

I only own up to a11 and don’t use a passcode so it’s whatever for me but I still would rather 14.1 than 14.3 for dual booting purposes

[sage briar]

It is totally above my knowledge to understand this description of problem

[covert lily]

Is it possible to find out the boot nonce of an unjailbroken device?

[sharp latch]

What chipset?

[covert lily]

A11 and above

[elder palm]

his intelligence is too powerful for dumb people like us

[celest basalt]

on A11 you don't need apnonce, for A12+ it's more tricky

[subtle cosmos]

Wait, I don't know what he was really trying to downgrad. But on the photos there was a iPhone. There is no iPhone with A10X. So he can't test it with a A10X or I am wrong?

[celest basalt]

but as I discovered yesterday you can read out ApNonce (nonce) and boot-nonce (generator) from MobileGestalt with idevicediagnostics even for A12+

[covert lily]

If he has an iPad he can test it.

[celest basalt]

so you can save valid blobs that can be used later if you have a jailbreak and can set the generator

[covert lily]

Interesting.....

[celest basalt]

normally you would need a jailbreak to set the generator for A12+ to save blobs with a known generator that won't be single-use

but there is another way apparently, it was mentioned on the server a while back, and I realized yesterday that idevicediagnostics can be used for this

[subtle cosmos]

Yeah I know. but look at his photos he send to his comment...
No offence but he have really post crazy comments in the past. Maybe he don't know what chip that phone have.

Its definitely a iphone https://cdn.discordapp.com/attachments/688124783400845336/809233809869373470/image3.jpg

[sharp latch]

If it gets stuck there your SSL is fucked

This is the actual err behind the scenes

Are these fake AirPods

[subtle cosmos]

Haha don't know.

@rustic blaze what device have you try to downgrade on your pictures? iphone 7?

[sharp latch]

iPhone 8 and iPhone SE 1st gen. Same issue on both until I fixed my openssl

[zealous bridge]

Yes

they are called TWS-i7s if im not mistaken

[subtle cosmos]

But only fixed the ssl error? Not the downgrade error ?

[sharp latch]

It fixes the FDR erro AFTER sending the file system and it works but only for the FDR err after sending file system not the one at the start for a11

[subtle cosmos]

Ah ok.

[celest basalt]

Is a jailbreak ever needed to use futurerestore after blobs are saved?

[subtle cosmos]

Mostly yes because there are nonce setter within the jailbreak app or you can install nonce setter. In the past there are also nonce setter without a jailbreak. But not for newer devices. So in generelly you need one.

[uncut wren]

Is there a tutorial to use futurerestore on Linux to go from 14.4 to 14.3? I have blobs saved and using iPod touch 7

[celest basalt]

Got it! Has Apple ever randomly started resigning a previously unsigned iOS version?

[celest basalt]

signing party happened like once but never since then so far

other than that, they have resigned some specific versions that were unsigned by mistake

like tvOS 13.4.8

[subtle cosmos]

Read pinned posts. There are tuts on.

[uncut wren]

I found the version complied for windows.

[subtle cosmos]

There is no FR for iOS14 for win.

[celest basalt]

Signing party? Was that like an all versions signed type of deal? Sounds crazy

[subtle cosmos]

Yeah a few years ago apple signed a bunch of old firmwares for maybe 30 - 60 mins.

[uncut wren]

Ok. I’ll try to figure out how to run it. Thanks for pointing me in the right direction. I’ve only ever used windows compiled version haha

[subtle cosmos]

You must FR for iOS 14 yourself. It is only for macOS and linux. When you use the scripts from the pinned post you should be fine.

[uncut wren]

Awesome. Thank you!

@subtle cosmos may I ask you questions? If not it’s ok and I can wait for someone

[subtle cosmos]

Sure.

[uncut wren]

So i ran the file from the tutorial and I have a “build” folder on my desktop and terminal is doing a bunch of stuff. Is that normal?

[subtle cosmos]

Yes. It takes a few minutes (depends on your machine).

[uncut wren]

And I can only go back to 14.0-14.4 since it’s an A10 iPod or can i go back to a version of iOS 13? I only ask because this

“Wifi only iPads and iPods that support iOS 13 should be in theory to downgrade to 13.4-14.4…”

I have blobs for 13.4.1

[subtle cosmos]

Only 14.0-14.4

[uncut wren]

Ok. An error keeps popping up in terminal saying “couldn’t open directory ‘m4’ no such file or directory. Should I be worried?

[subtle cosmos]

I am not very deep in compile things. Have also used tuts for that. But the error accours on me also during compiling and it works. I don't remember exactly but on the end you become a message if it was successfully or failed.

[uncut wren]

Awesome! It’s compiled. Thank you so much! And where do I put the shsh blob and ipsw to make sure it’s seamless?

Because on windows I was able to pick and choose what directory to pull from

[subtle cosmos]

I think you have used a GUI tool for FR on windows. Here you can't use this.

You can drag and drop the files direct in the terminal window.

[uncut wren]

Awesome. Thank you!

Sorry for asking so many questions

[subtle cosmos]

Maybe it is easier to make a folder on the desktop and put all files in it. So you can easy drag and drop it in the terminal window.

[uncut wren]

Can use the latest SEP argument for an iPod touch?

[subtle cosmos]

I think so.

On which firmware you are?

[uncut wren]

14.4 going to 14.3

[subtle cosmos]

Ah ok. You have nothing to lose. You can always restore to 14.4, use checkrain, set nonce and try FR again. So you can test whatever you want. No worries.

[rustic blaze]

Any solution to the fdr error

Yet

[subtle cosmos]

What device have you tried on your photos?

@rustic blaze

[uncut wren]

I had to manually put my device in recovery mode for futurerestore to work. I’m pretty sure it’s my cord that does that

[rustic blaze]

iPhone 7 Plus and iPhone X

[uncut wren]

I don’t think those have the FDD error?

FDR*

@subtle cosmos everything starts happening but then my device gets stuck on what appears to be the restore screen and terminal says “waiting for device in restore mode” then the screen turns black and terminal times out

Nevermind. It’s working now.

Had to try a few times

[subtle cosmos]

I must run the commands twice. after FR trying to put my device in restore mode, it don't recognised it and fail. After that I run the command again and it starts.

[uncut wren]

The third attempt worked for me

[subtle cosmos]

So you don't have a A10X device... Maybe your FDR error is the SSL thing.

[subtle cosmos]

@celest basalt @sharp latch he don't have a A10X device. It was a i7+.

[celest basalt]

oh

I didn't even look at all the pics lol

[subtle cosmos]

So the FDR error on his i7+ can maybe fixed with compile openssl from source how @sharp latch says.

[rustic blaze]

But the open ssl was compiled from source and not from brew

As told earlier

[celest basalt]

https://twitter.com/imatech_/status/1359632053772423168?s=21

i.M.A.T_Tech (@iMATech_)

Please retweet so we can find the solution. I’m able to reach by this point!
Sending filesystem ✅
Verifying restore ✅

After Mounting Filesystems it gets stuck at:
Unknown operation (80)
Unknown data request ‘PersonalizedData’ received

Downgrading A11(14.4-14.3) (NO FDR ERROR)

Twitter · Feb 10, 2021, 10:35 PM

[somber nymph]

is it possible yet for futurerestore to go from ios 13.5 to 14.2 on an iphone 11 when the new jailbreak comes out

[subtle cosmos]

No.

[celest basalt]

no it would most likely fail, and we're not even sure if it can be fixed, Apple might have just made the SEP incompatible for A11+

[somber nymph]

so even if i have blobs i cant use the "odyssey14" when it releases?

[subtle cosmos]

At this time no.

[somber nymph]

"oh yeah if you're still on iOS 13.x and jailbroken on A12/13 just save blobs for iOS 14.3 RC. You'll be able to futurerestore later should an exploit be made for 14.3" -cstar

would this apply for 14.2 or 14.1 blobs?

[subtle cosmos]

This was a false info. He didn't know about the error.

[somber nymph]

damn. so i basically wont be able to jailbreak ios 14 in any way?

[drifting echo]

So does that means now saving blobs are useless?

[somber nymph]

^

[subtle cosmos]

No, always save your blobs. Nobody knows what the future brings.

[drifting echo]

Yea I did but 😿

[somber nymph]

so the only people who will be able to jailbreak are the people who were unjailbroken on ios 14.1-3 right

[subtle cosmos]

No, it depends on the jailbreak. If a jailbreak drops for 14.4 they can also jailbreak.

But regarding to cstar, yes.

[celest basalt]

it's only true for A10- now but there's not a huge reason to go to 14.0-14.3 there unless you really want semi-untether

[subtle cosmos]

Oh yes true, forgot the nice A10 and below devices 😀

@rustic blaze I tested and successfully restored my iPhone7 to 14.1 right now. No error. So the error is on your side.

[green onyx]

@celest basalt do u have a spare device A11+?

[celest basalt]

only A12 unjailbroken

[green onyx]

have u tried 14.4 to 14.5 beta 1

ah

[green onyx]

this using fr

[celest basalt]

I'm on 14.5 beta anyway, but idk if I can manage to compile FR

[green onyx]

lmao nice. hopefully u can and diagnose if its a sep issue or fr issue

if it works, sep issue

if it doesnt, fr issue

hopefully, some genius has an A11+ on 14.4

[agile veldt]

frcoal

i have an XR

waiting on 13.5 to update to 14.3 if it ever becomes possible

pls someone fix

[exotic atlas]

Ran in to Error like: "syntax error near unexpected token xxxx,' ./configure: line 12174: PKG_CHECK_MODULES(xxxx, ", turns out I do not have pkg-config installed. So, add 'pkg-config' after line 7 fixes this problem.

[zealous bridge]

thats a common issue

[green onyx]

what device are u using

[lilac holly]

someone on Reddit is supposedly trying it on an old iPhone 8

nvm that's to 14.4, not higher

[subtle cosmos]

This was already tested from @sharp latch

#futurerestore-help message

[lilac holly]

yep, i misread the initial statement

[subtle cosmos]

#futurerestore-help message

#futurerestore-help message

[celest basalt]

https://twitter.com/imatech_/status/1359980630260527109?s=21

i.M.A.T_Tech (@iMATech_)

Retweet so it can reach everyone and finally we can get the fix for FDR error! C'mon jailbreak community! Share the word! I'm sure we are gonna find the fix in few days!!!

#Retweet https://t.co/0p74qjoEKl

Twitter · Feb 11, 2021, 9:40 PM

[forest sinew]

Interesting

[copper nacelle]

does the futurestore issues only apply to a11?

[celest basalt]

Yo

How does this work

[brave pollen]

It applies to A11 and up

[copper nacelle]

Did anyone try it with an a12?

[forest sinew]

https://reddit.com/r/jailbreak/comments/lhqd4i/_/gmzp3lz/?context=1

[lilac holly]

? I thought FDR did not occur based on: #futurerestore-help message

[subtle cosmos]

Isn't the i.M.A.T_Tech guy using a outdated version? In the logs stand:

Version: 38b168002bca318c91068fc194abd36e2d54f155 - 180

https://github.com/tihmstar/futurerestore/commit/38b168002bca318c91068fc194abd36e2d54f155

The fork from @shy magnet is v 190.

[exotic atlas]

It’s not device related, just during FR compiling

[sharp latch]

Yes he is. It will never finish and that won’t work. All he’s doing is using an old version with one modification

[dull swallow]

so who the fuck is correct here

is Samg right

or is JoshTV right

[forest sinew]

Who knows anymore lol. Hopefully the bounty encourages more digging to find the truth

[dull swallow]

yeah true

[forest sinew]

Tell that to samg who said it’s worth it

[shy magnet]

if anyone wants to try something that *may* work

https://twitter.com/marijuanARM/status/1359995880384983046?s=20

adam (@marijuanARM)

@rA9_baris @exploit3dguy @halo_michael @tihmstar might be worth a shot, try this process:

• build & install latest openssl
• clone my futurerestore & its submodules
• go into the idevicerestore submodule & checkout the ‘12667e70defe51fec607ff3006729d0cb5a6aaa8’ commit
• build futurerestore, and make sure it’s linking 1/2

Twitter · Feb 11, 2021, 10:41 PM

https://twitter.com/marijuanARM/status/1359996064242274310?s=20

adam (@marijuanARM)

@rA9_baris @exploit3dguy @halo_michael @tihmstar against the openssl you just built. who knows, maybe the latest idevicerestore commit might be breaking something?

Twitter · Feb 11, 2021, 10:41 PM

emphasis on may

[forest sinew]

I may have an 8 Plus still if you wanted to remote Into a VM to try yourself. It’s shattered and sitting in a drawer not being used, don’t care if it’s updated.

[shy magnet]

if you're willing it's worth a shot ¯_(ツ)_/¯

[forest sinew]

I’m at work rn but if you ever have time to do it I’ll definitely set that up for you

Linux VM? Or just want a Old Mac Pro I have lying around with a new user on it

I think it’s High Sierra

Dm me if your willing

[dull swallow]

if it works for A11 would it work for A12+

[shy magnet]

it should

[dull swallow]

i could test it when i get home with an A10 device

nvm

[shy magnet]

no point

[dull swallow]

that doesn’t make sense

[shy magnet]

a10 devices already work fine

[dull swallow]

true

my other device is A13

and that means i’d only have one chance of testing

i’d test it if A11 works with what you said

[valid adder]

14.4 -> 14.4

X

a15???

[tall siren]

oh that wasn’t me, someone else whenever we had to redo channels

[sharp latch]

The only important idevicerestore commit is the addition of sending RSEP if found in the build manifest for 14.3+ and if you don’t include this you will get a failed to upload sep err right at the start

[dull swallow]

try to go to 14.3

tell us if it works

[sharp latch]

You know what would be hilarious. If 14.5 beta sep worked

I never tried for obvious doubt it would be any different

[shy magnet]

are they still signed

nvm

14.5 beta released way after 14.4

[valid adder]

mfw checkra1n sits on waiting for device for 10 minutes only for exploit to fail

[dull swallow]

[valid adder]

works fine

[dull swallow]

with 14.4 SEP?

[valid adder]

yeh

[dull swallow]

on A11

[valid adder]

yep

[dull swallow]

EPIC

we could try on A12+

who’s losing their JB

[valid adder]

@shy magnet idk what this shit is about but there was never any FR issues

I just used stock 187 fine

[shy magnet]

huh

downgrading to 14.3?

[valid adder]

yes

[dull swallow]

yeah

[shy magnet]

the fuck?

[dull swallow]

big news i guess

[shy magnet]

confusion

[dull swallow]

lol

[shy magnet]

stock 187 + upstream limd idevicerestore changes pulled?

[dull swallow]

@valid adder

[dull swallow]

OOH SHIT

[valid adder]

latest brew limd afaik @shy magnet

[dull swallow]

so we don’t need tihmstar

epic

[shy magnet]

wait you compiled with upstream idevicerestore?

none of tihm's changes?

[valid adder]

whatever 187 compiles with

idevicerestore

[shy magnet]

damn

go claim that $800 bag bro

[valid adder]

mostly everything from source except openssl

link?

@shy magnet

[shy magnet]

https://www.reddit.com/r/TweakBounty/comments/lgxlac/25143_updated_working_futurerestore_for_a12/

$880

[valid adder]

not a12 tho

[shy magnet]

theoretically that shouldn't be an issue

just have to have someone test

[dull swallow]

i might test

as a last resort

i am not home currently however

would correlium work

to test

[valid adder]

latest commit could work but I never tried it

I just haven't updated my fr recently

I had no need to

@shy magnet

[dull swallow]

i wouldn’t trust the tweak bounty entirely some people back out

[valid adder]

same build that got me from 14 to 13.7 but fdr would hang but with manifest hacks you can exit the hang

[shy magnet]

i reset idevicerestore fork back to the commit you tried

and i'm gonna put futurerestore back to 187 then try

[dull swallow]

are you gonna try on A12+

[celest basalt]

yoo this is sick then

i’ll try tomorrow

[valid adder]

I don't have a12 lol

[dull swallow]

well

then

[celest basalt]

@valid adder was this on a X

[dull swallow]

yeah

it was

[celest basalt]

pog

[dull swallow]

could apple even specifically make SEP incompatible on A12+

[valid adder]

@celest basalt yes 10,3 d22ap

[celest basalt]

alright

i’ve got a 10,6

[valid adder]

you can theoretically sacrifice passcode/faceid and go to 13.7

[celest basalt]

same thing i guess

[valid adder]

just only works for X

not any other

[dull swallow]

the baseband is incompatible though isn’t it

[celest basalt]

ok so i can try the exploit on my main now

sweet

[sharp latch]

im trying to test this now, do i clone 187 and reset idevicerestore and what elese?

[shy magnet]

here hold on

[dull swallow]

what are you testing on

[sharp latch]

iFone 8

lol

[dull swallow]

ok A11

[celest basalt]

it’s 11pm but i’m downloading my IPSW for tomorrow lol

[sharp latch]

i dun have a12

[shy magnet]

try with the latest commit of futurerestore rn

[dull swallow]

what device is 10,6

[shy magnet]

X

[dull swallow]

oh

[celest basalt]

iPhone X GSM

[shy magnet]

this'll confirm if it's specifically futurerestore or idevicerestore

[sharp latch]

ok will do man cloning npw

[shy magnet]

i suspect the latter

[sharp latch]

i have an old HP hackintosh so it takes a min

[celest basalt]

ok gn y’all

gonna have fun with this this weekend

[sharp latch]

Gn bro

[celest basalt]

Should I try on a13?

[sharp latch]

not yet\

[celest basalt]

Ok

[stiff hazel]

A12+ “”downgrades”” are

• one time use basically
• if it doesn’t work after a specific point you’re fucked basically

[sharp latch]

`ersonalizing IMG4 component RestoreSEP...
Personalizing IMG4 component SEP...
Sending NORData now...
Done sending NORData
ERROR: Unable to receive message from FDR 0x7fc32e634ca0 (-2). 0/2 bytes
ERROR: Could not read data (-256). Aborting.
Cleaning up...
[exception]:
what=ERROR: Unable to restore device

code=67764241
line=1034
file=futurerestore.cpp
commit count=191:
commit sha =de444ceee137537615a36b53aa7c7e58d2b7c21d:
Done: restoring failed!
`

Version: de444ceee137537615a36b53aa7c7e58d2b7c21d - 191
img4tool version: 0.174-d91d5e8404c9a2c9b255e5a917cf81ee5e3ca578
Odysseus support: no

i dont have the latest img4tool but i dont think it matters? ill update agains my will tho

[celest basalt]

I’ll def fuck it up too 😆

[grave dune]

lmao

all it was, was people using outdated tutorials?

LOL

[shy magnet]

no

[grave dune]

or no

[shy magnet]

it was some issues on my end too

[grave dune]

honestly no idea 💡 the technicalities but from samgs comment it seems it never had FDR issues but people used wrong forks?

[sharp latch]

it still doesnt work for me?

[rapid creek]

Any good tutorial tu compiled

[valid adder]

I was using limd 1.3.0 from brew @shy magnet

[shy magnet]

not building latest?

[valid adder]

nope

[grave dune]

i haven’t tried it but all i know is my A13 got one shot and that one shot better be 100% lol.

^

oh shit ur cryptic from the comment ya?

[valid adder]

always have been

[grave dune]

i just joined this Discord 😦

[valid adder]

🙂

[grave dune]

either way, i’m stoked. i have 2 devices A12 devices i bought last week

i wish i saved blobs for 14.3

they on iOS 12

i would’ve rested

tested

ima updat then anyways

[rapid creek]

Hi bro can u help to compiled that futurerestore i’m on a11 and want to move to 14.3

[grave dune]

if only i knew of the potential FDR error but we learned about that on r/jb 2 days ago

iPhone ship

[sharp latch]

@shy magnet Version: de444ceee137537615a36b53aa7c7e58d2b7c21d - 191
img4tool version: 0.197-aca6cf005c94caf135023263cbb5c61a0081804f
libipatcher version: 0.82-0b2f79ff0917ef9b8a92475d93d9466b23fc2322
Odysseus for 32-bit support: yes
Odysseus for 64-bit support: yes
Validating the filesystem
Filesystem validated
Sending filesystem now...
[===== ] 9.0%

it DOES WORK

[grave dune]

is this the correct way? https://reddit.com/r/jailbreak/comments/k7pjj6/_/gesvi63/?context=1

[shy magnet]

latest commit on my fork?

[sharp latch]

yessir!

tested a11 iphone 8

[shy magnet]

what did you change from the first time you tried?

[shy magnet]

.

[grave dune]

Pog

[sharp latch]

latest img4tool

[shy magnet]

mine or tihm's

actually

that doesn't matter

[sharp latch]

tihms but yea its the same afaik?

[shy magnet]

yeah

[sharp latch]

ok so 14.4 --> 14.3 works. 14.4 --> 14.2 DOES NOT

just FYI

[shy magnet]

interesting

are you building with latest openssl

just in case it's that bug

[sharp latch]

yea build from suace

the open SSL bug plauges ppl after sendig FS but cryptic didnt so idk

shit just relasized i didint make a bakup of my setup -__-

w/e for a good cause

[grave dune]

is doing a futurestore same as doing a succesion or itunes restore?

[shy magnet]

same as an itunes restore

not succession

[grave dune]

in terms of deleting files

gotcha

Thank you
always wondered what people did when they did futureestore

like if u update to 14.1 waiting 6 mo for jailbreak right. u don’t want any residual files to mess with your apps.

so succesion before futurestore or just running futurestore is enough

at least that’s my thoughts on it i never actually did it so just speculating

[shy magnet]

futurerestore is enough

unless you're restoring from a backup or using the update flag

[grave dune]

ahhh. ok, gotcha. Thank you so much. alleviated my concerns

[valid adder]

@shy magnet

these are my versions

[shy magnet]

thank

[rapid creek]

What need now is a good tutorial step by step

[shy magnet]

not doing anything until i confirm this works on a12+

[valid adder]

https://psty.io/f?q=492

[rapid creek]

Do u thinks u can make a good tutorial step by step how to compiled good

[valid adder]

no

[shy magnet]

im gonna take a look at capt's script

[valid adder]

I no longer do that kinda thing

[shy magnet]

and update that

[sharp latch]

I did the same deps as cryptic but compiled OpenSSL that’s all. Seems to work either way if your going to 14.3. I’ve tried 14.1/.2/.3 and only .3RC1 and 14.3 final work due to sep but at least it works

[valid adder]

manually specify

[sharp latch]

Wdym

[valid adder]

sep and bb

manually specify

[sharp latch]

I did, always do

[valid adder]

futurerestore --apticket ~/Downloads/REDACTED_iPhone10,3_d22ap_14.3-18C66_27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae.shsh2 --debug -d --sep ~/iPhone10,3,iPhone10,6_14.4_18D52_Restore/sep-firmware.d22.RELEASE.im4p --sep-manifest ~/iPhone10,3,iPhone10,6_14.4_18D52_Restore/BuildManifest.plist --baseband ~/iPhone10,3,iPhone10,6_14.4_18D52_Restore/Mav17-6.41.01.Release.bbfw --baseband-manifest ~/iPhone10,3,iPhone10,6_14.4_18D52_Restore/BuildManifest.plist ~/Library/iTunes/iPhone\ Software\ Updates/iPhone10,3,iPhone10,6_14.3_18C66_Restore.ipsw

this is the command I ran FYI

@shy magnet

[rapid creek]

Do u thinks can help me to compiled please

[sharp latch]

Dude just wait for a few days. 14.4 isn’t going anywhere

[valid adder]

I already replied lol

[grave dune]

killalll_humans. mUst kill all humans

[dull swallow]

even if it did 14.5 SEP would prolly be compatible

[rapid creek]

My bad bro i know that

[grave dune]

aka bender rodriguez

[sharp latch]

I tried the beta and get the FDR error with 14.3 lol

But still it gives people tons of time

[valid adder]

someone try a12 no balls

[sharp latch]

Lolz

[grave dune]

i got a12z

i can risk

ipads aren’t meant to be jail broken anyways

[sharp latch]

All things are meant to be jail broken

[burnt siren]

@shy magnet capts script is fine

Worked for me yesterday

[grave dune]

i know i’m joking

[shy magnet]

alright then

[burnt siren]

Except for a file where I needed to add a comment

Dunno if it was on my end

[shy magnet]

i think the only issue was my idevicerestore fork

[burnt siren]

Compiled fine otherwise

[sharp latch]

The libipatcher err?

Version #string i think

[burnt siren]

Yes

Line 53

[valid adder]

classic @burnt siren

tihmstar moment

[sharp latch]

[burnt siren]

You should do one of your static compiles @valid adder

And save the universe

[sharp latch]

Oh god that’s a task and a half

[burnt siren]

My boi has xxperience

[valid adder]

someone make backups include apps

Im tired of my apps reinstalling

[burnt siren]

Get proper Wi-Fi

[sharp latch]

Tru I remember a year or so ago when he made the Static version and saved some asses. Right before GeoJoke made a dynamic version and released it like and idiot

[valid adder]

I have proper wifi

doesn't take long

just annoying

[burnt siren]

I frd my a10x yesterday

All fine

[valid adder]

yeh the problem people were having was a11

not sure why

works fine for me

[burnt siren]

Doubt

[sharp latch]

I made a thing to set a11 nonce in DFU so that was cool

[burnt siren]

Classic r/jailbreak

[valid adder]

a11 can even go to 13 lol

[burnt siren]

Rly

[sharp latch]

Oh really? Same way?

[valid adder]

@burnt siren yeh just no passcode tho

[burnt siren]

Oh ya

[valid adder]

@sharp latch nah need manifest hacks

[burnt siren]

I’m good on 13.5

[sharp latch]

Well I don’t use a passcode and would love 13 back so what kinda build manifest hacksv

[valid adder]

hopefully they can pwn a11 sep

[burnt siren]

Nah

No way

[shy magnet]

alert alert

anyone who writes a gh action for statically compiling futurerestore is getting their dick sucked

[burnt siren]

@valid adder

[valid adder]

guess im changing my sexuallity

[sharp latch]

Lol

Do I just remove sep from the build manifest? Kinda curious on that 13 for a11 thing

[valid adder]

no

I didn't work for a9, only worked for a11

needed stuff like sep, baseband and SE from the latest manifest

modify the with ipsw manifest with that

[sharp latch]

I only have a11 that need 13. My a9 is dualbooted 14.1 main 13.7 second.

Ok that sounds easy enough. Thanks man i appreciate the tip

[dull swallow]

so no ones sacrificing A12 yet

[sharp latch]

adams getting a13 tester

[grave dune]

i think mista awesome trying a13?

[dull swallow]

okay

epic

[grave dune]

if y’all step by step me i can sacrifice a12z

[rapid creek]

Today is a good day

[shy magnet]

@grave dune accept friend req

[dull swallow]

the latest version of future restore is Linux and MacOS right

or is it just mac

[grave dune]

ight

[rapid creek]

Did u have good tutorial how to duelboot i want to test it

[sharp latch]

Not really since the tools aren’t updated it’s very manual if your on iOS 14. Plus it has to be an a9 or a10 device

Plus you need a Mac to boot it after

[rapid creek]

Oh ok thanks since that fdr error is fixed i’m happy to move on 14.3 and wait that new jailbrak

[meager axle]

i don't get why futurerestore can't see when it's put my device in recovery mode but irecovery can. is there anything i can do?

using sudo for both tools

[dull swallow]

what version

of future restore

and what repository is it from

[meager axle]

marijuanARM fork latest git using AUR; just updated a few minutes ago

[dull swallow]

@shy magnet

[shy magnet]

huh

wtf

[meager axle]

using this one: https://aur.archlinux.org/packages/futurerestore-marijuanarm-git/

[rapid creek]

Yeah u need to fix this because need to entre in recovery mode manuel

[rustic blaze]

Downgraded my iPhone 7 Plus to iOS 14.2

Had problem in blobs

[dull swallow]

what

[sharp latch]

That has been updated for 14.3 a11 is what we have tested

[meager axle]

i'm the person who wrote the bug report on iPhone 8 Plus

A11

trying to go from 14.4 to 14.3

my bug report is from before the new fix, so unrelated

just recovery mode detection

idk what's wrong with that part

[rustic blaze]

So do we need to put iPhone recovery mode manually

With the new script

[burnt siren]

No

[meager axle]

it may work on other machines, but isn't working on mine and idk why

[sharp latch]

Ok I’m not 100% sure about AUR. It’s tougher since it could be unrelated like libusb

[meager axle]

i'll build manually then

[burnt siren]

Doesn’t work for me either

You have to restart the program

It doesn’t detect it in recovery

If it’s the program sending it to recovery that is

[sharp latch]

Oh that issue yea. I just use my a11 Nonce DFU script to patch SROM and then send any pwnibss it will be in recovery and FR works fine w/o the restart

[meager axle]

actually trying yay -S libusb-git first in case that fixes it

[burnt siren]

Just ctrl c

And run it again

Too much fuss rly lol

[sharp latch]

But then I have to set my nonce before hand and that’s too much work

[burnt siren]

Do it from system info

Easy as cake

[sharp latch]

I don’t even jailbreak the phone, I just do it right from DFU. It’s much faster for testing things

[dull swallow]

does system info blobs work

lol

[burnt siren]

¯_(ツ)_/¯

They do

[dull swallow]

is the ApNonce it detects accurate?

[burnt siren]

Yes

[sharp latch]

Yea SysInfo saves my ass a few times

[dull swallow]

oh shit nice

i have a server with auto tss on it and i got system info blobs too

i got blobs down till 13.3.1

[sharp latch]

Oh yea?

[dull swallow]

the thing is my device is A13

iOS 10 on A13 eta wen

[sharp latch]

Ah that’s dope then

Lmao

[dull swallow]

imagine using totally not spyware on A13

actually that could become a reality

[meager axle]

this hasn't worked, though i wonder if i need to reboot... i'll try that

[dull swallow]

if modernpwner releases the RCE chain

[jade laurel]

Are there specific blobs for 14.3 RC? I have 14.3 blobs.

[meager axle]

if you have 14.3, that's better

[sharp latch]

Just cntr C when it’s stuck and run it again. It’s an issue with FR not your computer

[meager axle]

ok i'll try that; ty!

[jade laurel]

I just know Adam wanted someone to test 14.3/RC. Wasn't sure if it was both or one.

[sharp latch]

What chipset ?

[jade laurel]

A13

[sharp latch]

Ok we have one person testing now so it’s ok, we don’t want you to lose your JB

[dull swallow]

sick

[jade laurel]

Kk. Sounds good!

[valid adder]

@burnt siren @shy magnet one dep down

[dull swallow]

how much to go

[meager axle]

this didn't work, unfortunately :( output: https://lex.clansfx.co.uk/dump/c126317afaf570eb7e55ff98b0ad1b4c/clip.txt

[valid adder]

10

[dull swallow]

oh

who is A13 tester

is it @burnt siren

[burnt siren]

no

[dull swallow]

Big moment

someone claim that BOUNTY

[rapid creek]

That’s a great news

[burnt siren]

but

no work was needed

[dull swallow]

@solid basin put it in announcements

[burnt siren]

stuff always worked

people were just dumb af as always

[dull swallow]

lol true

[grave dune]

POG

[shy magnet]

futurerestore 14.3 issues can suck my balls

[normal geyser]

do the compile scripts work for adams version

[grave dune]

ha

[normal geyser]

ha

[rustic blaze]

Do someone have the source code for this

[dull swallow]

bruh

[rapid creek]

Adam can u put the links of the script want to try it

[sharp latch]

Shh let the dumbass kids pay up and help Adam make some $

Lol

[sleek whale]

Inc 1000 stupid questions: HoW dO i UsE ThiSs????

[dull swallow]

xdddddd

cryptic woking on the script or something

[valid adder]

@shy magnet I didn't expect azure(github actions) to be this dogshit

[dull swallow]

speak of the devil

[shy magnet]

jesus

[sharp latch]

23 MF

[shy magnet]

isn't that the only free option though for gh

[sleek whale]

Most jb users need a fucking video guide

[valid adder]

@shy magnet can u google caching lol this shit slow

[shy magnet]

yea sure

[celest basalt]

anyone knows if the a12 fr work with windows?

[shy magnet]

you will never get anyone to compile it for windows

just use a linux usb

name: Caching with npm

on: push

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2

    - name: Cache node modules
      uses: actions/cache@v2
      env:
        cache-name: cache-node-modules
      with:
        # npm cache files are stored in `~/.npm` on Linux/macOS
        path: ~/.npm
        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
        restore-keys: |
          ${{ runner.os }}-build-${{ env.cache-name }}-
          ${{ runner.os }}-build-
          ${{ runner.os }}-

    - name: Install Dependencies
      run: npm install

    - name: Build
      run: npm build

    - name: Test
      run: npm test

@valid adder example from https://docs.github.com/en/actions/guides/caching-dependencies-to-speed-up-workflows

[celest basalt]

alright thx

[fickle spire]

Hi, I saved iOS 14.3RC1 Blobs for my A12Z iPad, Is there a way to check if they are valid wihtout actually restore? Or other: if I start a restore process and it happen that they arent valid, do I have to full restore?

[valid adder]

@shy magnet ok its just straighup broken...

[fickle spire]

Also will FaceID still work?

[shy magnet]

tf

[shy magnet]

verify with tsssaver

[dull swallow]

it will if the SEP works

[fickle spire]

I actually saved them with https://tsssaver.1conan.com/v2/, but idk if I did everything right

[shy magnet]

https://tsssaver.1conan.com/check/

[fickle spire]

It only allows me to check 14.3 C66, my SHSHs are for C65 😦

[sharp meteor]

Can I futurerestore to iOS 14.3rc on iOS 13.6 iPhone 11 now?

[dull swallow]

not yet @shy magnet is working on testing it

because it didnt work b4

[subtle cosmos]

use shsh.host. There you can check betas.

[fickle spire]

Alright, theres an arrow. Thank you 🙂

[vagrant sequoia]

please i already saved my shsh blobs for 14.1 and 14.3RC, witch one should i restore ( i have XS 13.5 )

[celest basalt]

you can't restore either right now, there's an issue with futurerestore on A11+ that may or may not be fixed (SEP might be incompatible)

anyway if it gets fixed either should work for a JB, 14.1 had more bugs related to default browser and markup in photos, but 14.3 RC has a messages notification bug I think

[dull swallow]

its been fixed

turns out the problem was idevice restore

A13 is still a nogo however

[celest basalt]

what about for A10?

[celest basalt]

oh I didn't see

A10 was already fine

[dull swallow]

A10 never had problems

[celest basalt]

🤔

[dull swallow]

some shit about future restore not having the stuff A13 needs

[celest basalt]

updated my pin in #jailbreak

[dull swallow]

or blobs

[celest basalt]

oh yeah someone mentioned rose firmware

I thought tihmstar fixed A13 for 13 but maybe 14 needs additional shit

[dull swallow]

for A13

[celest basalt]

I always specified it manually because the guides said latest might fuck up

[vagrant sequoia]

so basically i can use it to restore for my A12 ?

[dull swallow]

yes but you'll have to compile it yourself or use capt's script

[celest basalt]

so the fix was just this https://github.com/marijuanARM/futurerestore/commit/de444ceee137537615a36b53aa7c7e58d2b7c21d

epic

futurerestore has been fixed for A11-A13 for restores to 14.3. Use the latest commit from https://github.com/marijuanARM/futurerestore. 14.0-14.2 is not tested yet.

[celest basalt]

me when I can't unpin the previous message bc it says pin

[modern thunder]

will the version i just compiled from capts tutorial work?

[celest basalt]

it was fixed like 5 hours ago, if you got the latest commit it should

[dull swallow]

just run the capt script

it works with the newest commit

[dull swallow]

14.0-14.2 doesnt work btw

only 14.3

and 14.3rc

[modern thunder]

[celest basalt]

oh

[modern thunder]

is that true?

[dull swallow]

yeah

[modern thunder]

where did u here that?

[dull swallow]

from adam himself

[modern thunder]

oh

um

how does that work

[dull swallow]

who knows

[modern thunder]

why would only 14.3

work

[dull swallow]

probably something with sep or some typa shit

[modern thunder]

sep is the same

[dull swallow]

who knows then

[modern thunder]

:/

[celest basalt]

someone did mention an issue with dualbooting 14.1 on 14.4+ I think so it may be related

idk about 14.2

[modern thunder]

well

[dull swallow]

but at least we can go to 14.3

which is pretty big

[modern thunder]

no cap https://twitter.com/marijuanARM/status/1360083926312714243

adam (@marijuanARM)

alright, i think it's safe to say that for A11 devices, you can futurerestore to 14.3/RC1 using THE LATEST VERSION of my futurerestore fork.

14.0-14.2 seems to be incompatible, so don't bother.

haven't tested on A12, but the same applies there (just need someone to test).

Twitter · Feb 12, 2021, 4:30 AM

[dull swallow]

i believe future restore was never properly updated for A13

[celest basalt]

https://twitter.com/marijuanARM/status/1360117409139597313

adam (@marijuanARM)

iPhone XS restore to 14.3 successful.

(thanks @rexs0nic for testing!)

Twitter · Feb 12, 2021, 6:43 AM

[modern thunder]

good for me

[celest basalt]

nice https://twitter.com/marijuanARM/status/1360118346717528066

adam (@marijuanARM)

Tip: Don't use any futurerestore binaries people send you, as they're probably not compiled statically (meaning it'll only work for the person who compiled it). Cryptic is working on a static binary that will work for everyone, without any compiling required.

Twitter · Feb 12, 2021, 6:47 AM

[modern thunder]

or

[celest basalt]

Windows build pls

[modern thunder]

simple answer

compile it your self

lazy bitches

[celest basalt]

but even a Linux static build would be pog

futurerestore in checkn1x eta wen

[modern thunder]

i have 1 question tho

is this what it looks like once complied?

[dull swallow]

cryptic is working on it

[dull swallow]

i think so

[modern thunder]

cool beans

[dull swallow]

aaron didnt put the future restore working thing in announcements

when i told him to xd

[modern thunder]

L

i can't wait to have new emojis now

and be back to cool siri

cuz i liked that

when i was on 14.0

[celest basalt]

yeah probably best to put it in announcements so more people see it

I don't have perms

[modern thunder]

also no need for call bubble

[dark nacelle]

Just to make sure cause I haven't done this shit since iOS 10

[dull swallow]

hack into his discord account and put it there

[modern thunder]

I've never done it

[dark nacelle]

we need to take latest SEP and baseband correct?

[modern thunder]

baseband was alr the same

[dull swallow]

--latest-sep and baseband args work

[celest basalt]

#hackerman

[modern thunder]

the issue was an internal change with sep

[celest basalt]

I mean 14.4 is the only signed one atm

[modern thunder]

it wasn't a full sep change tho

that was the weird part

[dark nacelle]

aite I am just using capt guide in here that is why I asked

[dull swallow]

its compatible with 14.3

[celest basalt]

yeah

[modern thunder]

i need to make sure all my tweaks work on IOS 14

[celest basalt]

just test them on Corellium

[modern thunder]

wait

u can do that

[celest basalt]

don't even need to wait for the exploit, just create a jailbroken iPhone XS on 14.3

[modern thunder]

huh

[celest basalt]

they patch the kernel for you and install Cydia + Substitute

[modern thunder]

is that the

emulator

[celest basalt]

yes

[modern thunder]

wait

so

they can jailbreak

any device

emulated ofc

[celest basalt]

yeah

[modern thunder]

is it free?

[celest basalt]

it's $1.50/hour for A11 and up, $0.50/hour for A10-

[modern thunder]

but im broke

jk