futurerestore-help

[vivid nova]

And that's not coming out till mid March

[dull swallow]

what device

[valid adder]

I already explained that error in a twitter thread...

[night harbor]

futurerestore is still being updated, better wait for a bit more

[valid adder]

we are reorganizing and pushing

one more error to fix

[nimble halo]

o

[vivid nova]

Wen eta FDR changes to "ya did something wrong boi"

[celest basalt]

oh I reduced RAM bc I have 8 GB total in my laptop

[dull swallow]

yes pls this

[valid adder]

@vivid nova nikias broke a11 a12 this time

[dull swallow]

lol

[vivid nova]

Oof

[dull swallow]

nikias bassen?

[valid adder]

pimseks

limd

[dull swallow]

didnt know he worked on future restore

[valid adder]

idevicerestore 721

[vivid nova]

Nikias = checkra1n member

[dull swallow]

yeah i know hes on checkra1n team

[valid adder]

@vivid nova but hes not in hack different

futurerestore is literally an idevicerestore wrapper in c++

it always has been

[vivid nova]

Ngl, glad that red head Canadian is on the team..

[valid adder]

hes always on ida

[dull swallow]

still need future restore for CatOS got bugs on my current cat on version 420.69

[vivid nova]

Why must you update to more garbage

[vivid nova]

Wonder if that's his Valentine

[valid adder]

looool

[vivid nova]

Unironically, he loves snow

Especially the kind that's red

[valid adder]

time to try high sierra

[vivid nova]

I bet he's the checkra1n tester/configurator

[valid adder]

heres how it goes

master is for a11 a12

theres a branch for the rest

until pimseks reads my issue

[golden silo]

i’m gonna have to use both branches for A12Z and A13 lol

[vivid nova]

Can we plz keep the versioning consistent? The statics should follow after s0uths.. 245

This would be 250

[celest basalt]

versioning is based on number of commits, which is a mess with multiple different forks

this kind of versioning is a bad idea especially with git lol

SVN is more revision based

[vivid nova]

But they're all forked from the same source

[celest basalt]

yeah but I think they forked from tihm and might not have all of s0uthwest's changes

I think s0uthwest's didn't even work on A13 for iOS 13?

[vivid nova]

He did

Just wasn't tested

[celest basalt]

I seem to remember people saying it didn't recognize the device model or something

[vivid nova]

It had face id issues iirc

[celest basalt]

idk I only used it on A12 which was fine

[vivid nova]

Anything with touch id or lower worked

But my theory was proven right today: the sep/bb is compat

After the fdr's declared otherwise

[golden silo]

about 14.5b?

[celest basalt]

@vivid nova giving it 4GB RAM worked

was stuck at like 5% before

[rustic blaze]

some one got the code for v 187 or v188

[celest basalt]

(not even using this for FR mainly sorry for offtopic just following up)

[rustic blaze]

might as well try A11 to 14.2 or 14.1

[vivid nova]

See, watching TV can help

[shy magnet]

my brain is in massive pain

[dull swallow]

why lmao

rebasing?

[shy magnet]

yup

[dull swallow]

xd

[vivid nova]

I blame the etaers begging you to fix fr

[shy magnet]

i mean

for a bag

worth

[dull swallow]

i blame blaming

[vivid nova]

https://tenor.com/view/thor-ragnarok-isitthough-doubt-it-gif-18239143

[dull swallow]

i thought adam already got the bag

[vivid nova]

Yes and no

[shy magnet]

bounty is done

[dull swallow]

oh true some people havent paid yet

[shy magnet]

kinda iffy now but done

just haven't started collecting

which i will tomorrow

[dull swallow]

lol

you can get $200 in btc

lol

[shy magnet]

cryptic's taking the btc because i don't have a btc address

[celest basalt]

what was the bounty

[shy magnet]

$880

[celest basalt]

wow

[shy magnet]

but i don't think everyone's gonna pay anyways

[dull swallow]

$440 for adam and cryptic each

[dull swallow]

thats normal for r/tweakbounty apparently

[shy magnet]

nfr

[vivid nova]

Why not dogecoin

[shy magnet]

14.2 restore with 14.4 sep&bb just succeeded

[quick vapor]

i have big sur but i’ve seen that in can cause problems; i have an old macbook with high sierra laying around, should i use it?

[shy magnet]

nice

[dull swallow]

on A11+?

[shy magnet]

a10

but that wasn't possible before anyways

[dull swallow]

oh

[shy magnet]

gonna try 13.7 for kek

[dull swallow]

isnt bb incompat

[celest basalt]

i dont understand why people didnt grab blobs when everyone was screaming update to 14.3/14.3RC

how big of a difference is 14.2 and 14.3

[dull swallow]

idk man i am going to go to 14.3 though when a jb releases

[mortal bolt]

sep exploit wen eta :/

[dull swallow]

SEP isn't incompatible xd

[celest basalt]

mega ban inc

[dull swallow]

and a SEP exploit is open sourced future restore will probably get updated for a SEP nonce when Checkra1n gets SEPnonce generator

[mortal bolt]

if

[dull swallow]

what

[dull swallow]

if @shy magnet is interested in it

[shy magnet]

no

pe

[dull swallow]

lol

true

tihm might

but he left it

so who knows

[mortal bolt]

nooo

[shy magnet]

yeah 13.7 failed

[dull swallow]

lol

[shy magnet]

expected that

[dull swallow]

bb incompat?

[shy magnet]

sep

[dull swallow]

oh

i thought the SEP was compatible between 13.3- 14.4

[viscid patio]

did you remove the precompiled FR zip on github mentioned in the guide?

[dull swallow]

what

[shy magnet]

yes

[dull swallow]

he made 2 different branches check pins

[shy magnet]

new ones are gonna be uploaded in a sec

[viscid patio]

ok ty

[dull swallow]

the precompilied still works for A13/A14 though

[dull swallow]

wet

[valid adder]

will do high sierra when I have time

will take a while

[dull swallow]

static binaries?

i am assuming

[valid adder]

yes

but no legacy support

[dull swallow]

nice

[viscid patio]

thanks! Ill try my luck on A12z later

[valid adder]

for now

[dull swallow]

i feel like adam and cryptic are tired of working with the spaghetti code future restore is

[valid adder]

the real nightmare is git

[dull swallow]

lol

but future restore is evidence that if you use enough spaghetti code something will end up working

bruh my autofill

first thing that comes up when i type github

[valid adder]

oops I just wanted pongo

[dull swallow]

LOL

[celest basalt]

worth

[shy magnet]

lol same

[dull swallow]

lol

[shy magnet]

anyways

i need to wake up in a little over 4 hours

[dull swallow]

does the shit work now

[shy magnet]

so imma go to bed

it should

if not i will cry

gn

[dull swallow]

gn

[blazing gust]

Anyone able to help me figure out why my futurerestore is failing? I must be missing a file or entering the command wrong

[dull swallow]

you using the newest one?

what device

or send the log

[blazing gust]

XS so A12. And I believe so I got a precompiled version installed this afternoon

Sec for log. Want the whole dang thing or the end where the errors start?

[dull swallow]

https://github.com/marijuanARM/futurerestore/releases/tag/v189 try the static binary for A11/A12

[celest basalt]

oop, getting an error with the new build. DR 0x7f9667704410 waiting for message... FDR 0x7f9667704410 got plist message FDR Received 130396 bytes zsh: segmentation fault ./futurerestore -t blob.shsh2 -s sep.im4p -m BuildManifest.plist -b -p -d

[blazing gust]

Alright I’ll try that one and get back to ya. Thanks a ton

[dull swallow]

adam is asleep

might have to ping cryptic

@valid adder

[dull swallow]

wait you used the command to specify SEP and BB

did you put the file path to your sep and BB

[celest basalt]

oh yea, for some reason that didnt appear? I inputted ./futurerestore -t blob.shsh2 -s sep.im4p -m BuildManifest.plist -b baseband.bbfw -p BuildManifest.plist -d target.ipsw

with their respected names

[valid adder]

full log

[dull swallow]

dont you have to put the build manifest in twice

[valid adder]

can you seen the crash file as well

[dull swallow]

oh he did xd

im blind

[blazing gust]

Sorry if stupid question: I need to extract/specify a .bbfw file right? If so I’m looking in my 14.4 ipsw folder and I see 2 under Firmware - ice18 3.02.02 and ice19 2.03.04

[valid adder]

use telegram bot

[celest basalt]

holy this took forever to export

@valid adder want it in a pastebin or

[valid adder]

I shouldn't take that long

you select a little at the bottom then shift click the top

or vise versa

[celest basalt]

oh yea, i just wasnt sure where it saved =\

[celest basalt]

!sepbb in gir eta wen

[dull swallow]

true

i could probably just make a google docs with all of the bb and SEP

but it would be annoying with repetitive editing

[valid adder]

@celest basalt you most likely specified the wrong shit

[celest basalt]

oh shit, alright. i'll re-do it all

[viscid patio]

how do I 100% know I pick the correct sep and bbfw files? There are like 10 seps in the ipsw

[valid adder]

its pretty obvious

they are labeled

use the telegram bot

[celest basalt]

I am good to use my compiled 191 from yesterday as two out two people were successful who had the same versions of the libraries and stuff as me, only difference is they were on Big Sur I’m on Mojave, or is there advantage with these new static ones

[valid adder]

issues are fixed

versions were changed

189 is the latest

there are two 189 branches

[celest basalt]

Do the static ones work on Mojave too

Or should I compile

[valid adder]

prob need to compile

[celest basalt]

Nice, cheers

[viscid patio]

and which sep should I choose? Maybe I missed it in the guide ...
Got and IPad Pro 4 11inch cellular and there are seps from j317 to j321x & j417 to j421

[zealous bridge]

what were the issues then

[valid adder]

not fully fixed

this is a temporary fix until idevicerestore gets fixed

[lime veldt]

i have an A12Z on 13.5 with unc0ver. i have 14.3 blobs that check out using img4tool. what's the worst case if something goes wrong with my restore? is it possible i might have to restore 14.4? or can i simply reboot back into 13.5 and try again?

[zealous bridge]

worst case, you have to restore 14.4, but from there you can try again to go back to 14.3

[lime veldt]

couldn't set the generator then though, could i?

[zealous bridge]

A12 success rate is pretty good tho

[zealous bridge]

you could, in the future, with a new exploit thats been hinted at, but who knows how long thatll take

But that is worst case

[celest basalt]

Done: restoring succeeded!```

woohoo, it worked! A12 iOS 13.5 -> 14.3RC 🙂

sorry about that @valid adder most likely had old files in the folder

[valid adder]

gang gang

we really out here

[zealous bridge]

Gr8

[celest basalt]

alright so if i use the script is that good to compile

[lime veldt]

why does /sepbb list a baseband for my wifi ipad

i should be using --no-baseband yes

[valid adder]

@lime veldt because you chose the wrong ipad

[cursive basin]

Does it work on macOS Big Sur?

[lime veldt]

did i though? :/

[zealous bridge]

Probably a bug

You should be using no baseband

[lime veldt]

my blobs have j420 in the filename... but i guess that's expected? the new sep might be different?

[viscid patio]

man finding the right baseband and sep was a headache.
I dont know if anyone here is associated with the telegram jailbreak bot ... but just for your interest:
when doing /sepbb and then chosing iPad Pro 4 11inch cellular you actually get the info for the wifi model and not the cellular model. Thats why I couldnt find the right bb

[lime veldt]

this is my concern

[viscid patio]

hopefully at least now the info is correct 👀

[lime veldt]

i thought 421 was the cellular

the 12.9" cellular

[viscid patio]

try like me ... chose the correct model but the opposit wifi/cellular and check

[lime veldt]

yeah it gives 420 which is what i expect.

so i'm glad i said something, i had just put 421 in place which is wrong

[viscid patio]

someone should fix that yea

[cursive basin]

??

[viscid patio]

kind of scared now that maybe more information is mixed up
are there any other reliable sources to get the correct baseband/sep?

[sharp solar]

I believe there was a tweet saying that Big Sur had some issues atm

[celest basalt]

https://www.theiphonewiki.com/wiki/Firmware shows baseband

the latest releases fixed those big sur issues iIRC

but im on Big Sur and it worked fine for me

i just recompiled, hope the issues are fixed

[valid adder]

@celest basalt just use the correct branch

[celest basalt]

i did that

[valid adder]

the recovery mode thing is still broke

thats a minor issue

[celest basalt]

was restore mode enter fixed

idk i'll give it a try

[sharp solar]

Is there a tutorial somewhere for setting your generator after saving blobs? Been a while since I’ve done this.

[celest basalt]

iirc it was my idevicerestore giving problems

[viscid patio]

@celest basalt ty that confirms it

[zealous bridge]

#futurerestore-help message

[nimble halo]

can confirm, latest release fixed the error i was having with restoring. successful upgrade from 13.5 -> 14.3RC, iPad Air 3 (LTE)

[sterile loom]

I keep getting the error "unable to place device into restore mode"

it's getting kinda frustrating now after several tries lol

[valid adder]

just don't reboot

just run the command immediately again

[sterile loom]

yeah that's what i did

i still end up with the same error every time tho

[brave pollen]

Does futurerestore work on Linux?

[lime veldt]

#futurerestore-help message

[brave pollen]

Ok thanks 🙂

[forest plank]

So I’m using iPhone 11 Pro Max but don’t seem to find any sep firmware d431ap . I can see d431. Is that the same ?
Also tried fr again and this time the error reads what=ERROR: Unable to place device into restore mode

[valid adder]

...

[brave pollen]

Do I need to specify sep and bb or can I use the —latest command?

[dull swallow]

latest should work fine

but generally specifying is the best option

[brave pollen]

Ok thanks 🙂

[celest basalt]

Do the static ones run okay on catalina?

[dull swallow]

they should i believe @valid adder did it with catalina

[celest basalt]

Sweet

[violet lotus]

I will try with Ubuntu using this #futurerestore-help message
Will i face any issues?!
13.5 A13

[dull swallow]

probably not

[violet lotus]

Okay I will feedback

[celest basalt]

it never accepts my kernelcache

smh

[zealous bridge]

Did it turn green

[high lily]

hey guys does the latest futurerestore work at Big Sur?

[celest basalt]

It does

[high lily]

is this guide https://gist.github.com/TheRealKeto/7c5191c7495fb750e79f8ce0f0cdcdaa OK to upgrade with futurerestore from 13.5 to 14.3 on iphone 11 pro max? or should i use some other?

[celest basalt]

I tried to set my generator with dimentio but when I futurerestore it failed with the genator not matching. This is an iPhone X using checkra1n

[zealous bridge]

use this: #futurerestore-help message

[tropic glade]

iPhone X 13.5 v189 restore works fine

[high lily]

thank you!

[zealous bridge]

what version are you using

[junior fiber]

thats the a11/a12 only version

[zealous bridge]

so master?

[junior fiber]

yeah straigh from gh

[zealous bridge]

baseband error...

might have used the wrong one

i do remember that one issue where you had to modify the ipsw

[hazy nova]

linux can work ?

[zealous bridge]

should work

[hazy nova]

thx sir i have windows hackintosh or linux you think to use futurerestore easy ?

[zealous bridge]

@subtle cosmos this guy had the same error with an iP7 and fixed it by using ––latest args

might wanna give that a try

[zealous bridge]

hackintosh running macos would be best

[hazy nova]

thx sir

[junior fiber]

thanks @zealous bridge. Any method to set apnonce? checkm8-nonce-setter just says unsupported device or device not found

[zealous bridge]

[[dimentio]]

[celest basalt]

dimentio

PoC tool for setting/getting nonce without triggering KPP/KTRR/PAC. (requires tfp0)

Author

0x7ff

Version

2.0.0-1

Repo

1Conan

Bundle ID

com.0x7ff.dimentio

More Info

View on Parcility

1Conan - Page 1/5 · Feb 13, 2021, 1:11 PM

[junior fiber]

checkra1n not working on m1 tho

[zealous bridge]

rosetta terminal?

oh it doesnt work ur right

how did u checkra1n in the first place then

[sharp latch]

Just decrypt patch and sign an ibss /ibec with NVRAM unlocked. Connect with irecovery and set it with nvram method

[celest basalt]

Ok trying the new a13 one now

[sharp latch]

Gl

[celest basalt]

Thank you

[spiral patio]

Hi everyone, what’s about 14.4 sep and baseband compatible with 14.0-14.2?

[sharp latch]

Just run it again

[celest basalt]

same here kind of

ERROR: Unable to send WCHFirmwareUpdater component: Unable to find device
ERROR: Unable to send WCHFirmwareUpdater to device.
ERROR: Unable to send component 'WCHFirmwareUpdater' to device.
ERROR: Unable to send components supposed to be loaded by iBoot
Cleaning up...
[exception]:
what=ERROR: Unable to place device into restore mode

ran 3 times

on old static a rerun worked

[zealous bridge]

this error is becoming very common

@valid adder has it moved up your priority list yet?

[celest basalt]

a13 here on catalina

[sharp latch]

Is this a13?

[celest basalt]

yes sir

[sharp latch]

I’ve seen this a few times now as well. It’s not fatal. Just irecovery -n should fix it

[celest basalt]

yeah im not bootloop

[zealous bridge]

irecovery -n is not a restore command

[celest basalt]

im back in

[zealous bridge]

irecovery -n just gets you out of recovery

[subtle cosmos]

A10 have always worked with 14.0-14.4.

[zealous bridge]

doesnt help get past the error in any way

[sharp latch]

I know that’s what I mean

Just get the user back to normal mode

[subtle cosmos]

??? I don't have a error...

[sharp latch]

Since it’s broken on a13 at the moment

[zealous bridge]

you had an error

[subtle cosmos]

?

[zealous bridge]

forget it

I was just making an example of a previous error you encountered while attempting to futurerestore

[subtle cosmos]

No you can say it. It have tried a lot with my iPhone 7 and can't remember that I have a error. Can you show me the post or something?

So maybe I remember.

[celest basalt]

./futurerestore -t blob.shsh2 -s --latest -m BuildManifest.plist -b --latest -p BuildManifest.plist -d target.ipsw

is that how you use latest?

[subtle cosmos]

--latest-sep and --latest-baseband

[celest basalt]

./futurerestore -t blob.shsh2 -s --latest-sep -m BuildManifest.plist -b --latest-baseband -p BuildManifest.plist -d target.ipsw

[subtle cosmos]

./futurerestore -t blob.shsh2 --latest-sep --latest-baseband -p BuildManifest.plist -m BuildManifest.plist -d target.ipsw

[celest basalt]

thank you

think its worth an attemp?

attempt

[subtle cosmos]

If you have nothing to lose...

[celest basalt]

just jb not end of world. i'll try

[subtle cosmos]

Then give it a go.

[celest basalt]

same error but no booploop

[subtle cosmos]

Don't know. Have no A13.

[celest basalt]

All good just a status update. I haven’t read every message but I try. Doesn’t seem anyone in here was successful on a13 yet. I know Adam seen success on a13. Maybe I’ll have to compile myself

Captia script is good to use still?

@subtle cosmos seen your name all over reddit and here the last several days and I appreciate the support

[viscid patio]

A12Z from 13.5 to 14.3 succeeded!

[celest basalt]

Nice!

You used the static compiled?

[viscid patio]

Yes the one from github

[celest basalt]

Nice! No luck here on a13 yet

[viscid patio]

Well dont worry Theres still plenty of time and a jailbreak isnt even out yet… So good Luck!

[celest basalt]

Thanks dog!

Guys is there a way to future restore to ios 14.1 on a device running ios 14.1 iPhone 6s??

My device is stuck in the apple logo for whos woundering why i am asking i have shsh blobs saved too

I have a computer running linux

[sage briar]

Is there working futurerestore for windows A11 and A13?

[celest basalt]

i think A11 works with future restore but for windows and for A13 idk

[sage briar]

Everything works afaik but so far there was only mac version compiled

[river lantern]

As far as I am aware there is no futurerestore working on Windows.

Just Linux and macOS

[sage briar]

Thanks

And Linux cli or gui?

[dull swallow]

future restore isnt ever gonna be a gui xd

[sage briar]

Yes, now I realized I asked a bullshit 😄

[dull swallow]

is that big sur?

and btw future restore can't put devices into recov mode rn

use something else to put it into recov

big sur broke future restore

dont bother

use a lower version

of osx

[sharp latch]

Ya big sir is a big asshole rn

[dull swallow]

big sir

lmao

[sharp latch]

Typos are pretty funny eh

[subtle cosmos]

Have you blobs for 14.1?

[dull swallow]

yeah

big sir moment

[river lantern]

Rough out here. I cannot upgrade cause both my macOS won't run futurerestore. It won't work on High Sierra and it doesn't work on Big Sur

But I think Adam said he'd look into Big Sur issue

[dull swallow]

just use linux xd

[river lantern]

quite the Big Sir moment

I have Linux mint on a laptop. But I dunno what version. Anyhow, too inexperienced to run it on Linux

[zealous bridge]

linux is even worse

[river lantern]

So i wait for a fix for Big Sur and/or High Sierra

[zealous bridge]

big sur has a good success rate for A11 and A12

[river lantern]

I thought it wasn't working at all :0

[zealous bridge]

everyone on A13 are you guys using the right builds

[zealous bridge]

there was a fix earlier in the day there were reports of success if you scroll back enough

[river lantern]

I have A11 (X 13.7), so I guess I could with Big Sur using Adam's new build

[zealous bridge]

why arent u using static binary

[river lantern]

Uhhhh

[zealous bridge]

Use that

[river lantern]

The huh? Excuse my ignorance

[zealous bridge]

the static binary

[river lantern]

https://github.com/marijuanARM/futurerestore/tree/master

this?

[dull swallow]

nah

it isn’t

[zealous bridge]

have you tried it

[dull swallow]

yes

[zealous bridge]

what device

[dull swallow]

A13

[zealous bridge]

https://github.com/marijuanARM/futurerestore/releases/download/v189/futurerestore-master-v189.zip

[dull swallow]

iPhone 11 pro

[zealous bridge]

this is what you should be using @river lantern

[zealous bridge]

ok so thats 2/6

[dull swallow]

it’s not hard to get it working if you compile it right

[river lantern]

Yea, so the one that is pinned for A11 and A12

got it

thanks

[zealous bridge]

ive seen 6 ppl attempt it with one being successful

[dull swallow]

lul

[zealous bridge]

and now

two

lol

idk man i rly wanna test it myself

[west grail]

I was successful to updating A13

[zealous bridge]

but this phone is new so no blobs

[west grail]

iPhone 11 Pro

[dull swallow]

what error did they get

[zealous bridge]

restore mode

i think 2 ppl

[west grail]

13.5-> 14.3RC no problems

[zealous bridge]

there was one or two with FDR

but they couldve been using a wrong build

oh and one with baseband error

[dull swallow]

restore mode happens because future restore has a bug were it can’t put it into recov so you use another tool to put it into recov

[zealous bridge]

no

that error is

“Couldn’t put device into recovery mode from Normal mode”

different error

[dull swallow]

well what the heck is the restore mode

then

[zealous bridge]

restore mode

[dull swallow]

a log

[zealous bridge]

recovery

[dull swallow]

he said he was on catalina not linux

[zealous bridge]

two different errors

im just showing u an example the same thing happened on linux

[celest basalt]

yes

[zealous bridge]

just the first one i could find

[dull swallow]

14.1 incompatible don’t try it

[zealous bridge]

14.2 or 14.3 only

includes 14.3 RC

[celest basalt]

My device is on ios 14.1

[dull swallow]

ok

[celest basalt]

but stuck on apple logo

[dull swallow]

did you future restore to it

[celest basalt]

so 14.2 was fixed? I thought it was also incompatible before

[zealous bridge]

it was

[west grail]

I don’t know how people have those problems on Linux, i literally used the latest compile script , used —latest-sep and baseband as arguments with 14.3RC ipsw file and everything went without errors.. (iOS 13.5-14.3RC A13) ¯_(ツ)_/¯

[celest basalt]

i didn't i did a userspacereboot and suddenly my device just showed apple logo and never booted

[zealous bridge]

because this is futurerestore 😂

[dull swallow]

perhaps the distro used

ubuntu should work

[west grail]

Ubuntu 20.04, had to run apt upgrade just to confirm os was up to date

[zealous bridge]

do ubuntu bases work too

i use kubuntu

i imagine it should

[subtle cosmos]

@celest basalt you have a 6s. So you can go to 14.X. if your have blobs. There are no errors.

[zealous bridge]

Its unreliable

[celest basalt]

Ok do i have to disable find my iphone ?

I have successfully downgraded from 14.4 to14.3, thanks everyone for your help

[zealous bridge]

https://twitter.com/marijuanarm/status/1360428592858030082?s=21

adam (@marijuanARM)

@jonatan_suarez don’t use a VM when running futurerestore

Twitter · Feb 13, 2021, 3:20 AM

[zealous bridge]

yes

[celest basalt]

It was enabled before my device got stuck

[subtle cosmos]

Don't know. Its a normal restore. Didn't know if you are disable FMP if you restore...?

[celest basalt]

VirtualBox with USB passthrough worked fine for me on 245 months ago when restoring to 13.5 ¯_(ツ)_/¯

but then again that was Win10 host Win7 guest

[zealous bridge]

same

but

[celest basalt]

So you did it on Ubuntu? Maybe I’ll try that since Mac isn’t working a13 for me

[zealous bridge]

ig this is different

[celest basalt]

I guess i will have to restore then with itunes btw if i update to latest can i go back to ios 14.1

?

[subtle cosmos]

@celest basalt I have never disable FMP when I use FR or have restored via itunes.

[celest basalt]

I guess it may not be able to pass through as perfectly to a macOS/Linux guest, maybe qemu on Linux + macOS VM would work better for passthrough

[west grail]

Yes, the only thing I did was to update the compile script to the newest one posted here

[subtle cosmos]

Yeah you have a checkra1n device. You can update to latest and jailbreak it, set nonce and use FR to downgrade if you have blobs.

[celest basalt]

I saw the link to that script. I’ll try it I guess!

[zealous bridge]

qemus only gonna be viable for those who have a dedicated graphics card

[celest basalt]

So you suggest trying to restore using future restore first ??

oh is it? never used it on my computer, just on a server

I only have an IGP

not update to latest?

[zealous bridge]

yh idk if it doesn’t work outright but it definitely causes some issues

[wheat silo]

It is possible to use —latest baseband and —latest sep instead extract these manually. Maybe that’s easier for noobs.

[vivid nova]

Yes

@wheat silo

[subtle cosmos]

If you have set your nonce you can try it directly with FR. When not you can restore with itunes and jailbreak, set nonce and downgrade.

[zealous bridge]

doing that sometimes results in an FDR

[dull swallow]

generally specifying is better though

[vivid nova]

--latest-sep --latest-baseband works just fine

[celest basalt]

you can check nonce with igetnonce but FR will also fail early on if it doesn't match the blobs IIRC

[celest basalt]

I thought you don't need nonce for iPhone 6s ?

[zealous bridge]

someone used latest earlier and got fdr

@celest basalt was it you

[subtle cosmos]

All devices need to set the nonce.

[vivid nova]

Anything with touch/face id

[shy magnet]

14.0-14.1 is incompat no matter the device

[zealous bridge]

it is

?

[subtle cosmos]

I have downgrade my iPhone 7 to 14.1 with 14.4 files...

[zealous bridge]

#futurerestore-help message

this is incorrect then

[celest basalt]

this ???

[vivid nova]

14.0 is achievable with the latest SEP.. But i had to go to 14.3 to do so

[zealous bridge]

wait that is still incorrect

[shy magnet]

i restored from 14.2 to 14.1

[zealous bridge]

it says 14.0-14.2 is incompat

[shy magnet]

failed

[zealous bridge]

when 14.2 is sep compatible

[wheat silo]

Another easy way to check if you have the right nonce is to install system info and check it in settings - general.

[subtle cosmos]

We are talking about <A10 devices....

<=A10

[zealous bridge]

and im talking about all devices

[celest basalt]

I haven’t got for today, only restore thing

[zealous bridge]

oh

[vivid nova]

A10/X /should/ work to get to 14.0, if not then you guys messed something up

[zealous bridge]

but you still used latest

And got that error

[celest basalt]

What tutorial did you use? I thought I saw Linux guide before but can’t find it

[vivid nova]

[zealous bridge]

so

[celest basalt]

Yes

[celest basalt]

you don't need to enter apnonce to save blobs, but you still have to set nonce when restoring

[zealous bridge]

soo

that means

that

[subtle cosmos]

Yes correct. I have test it a few times with my iPhone 7. If the new FR don't work there is an issue now with it.

[zealous bridge]

it didnt work tho restore mode is a known error

[celest basalt]

But my dude Krich says he got a13 on ubuntu

[zealous bridge]

so many errors

[celest basalt]

How do i do that ?

[night harbor]

Here #futurerestore-help message

[vivid nova]

But again, going to 14.0 from 14.4 didn't work had to be 14.3

[celest basalt]

ok i have no blobs for ios 14.3

😆

[wheat silo]

F

[violet lotus]

Will work on a13 without issues ?!

[vivid nova]

You had lots of time to save

[celest basalt]

I think someone mentioned something about dual booting 14.1 working on 14.3 but not 14.4

[celest basalt]

Thanks! I saw that. Once it’s launched I just use the same command I was using on Mac?

[celest basalt]

i can't open my device so i can't its stuck on apple logo

[celest basalt]

so you're bootlooping

[vivid nova]

Also, if you have checkra1n, using nvram works

[celest basalt]

no not loop just apple logo

that is a bootloop

[dull swallow]

xd

[celest basalt]

if you're on A11- just restore to 14.4 first if the nonce already changed

it doesn't appear and disappear again

[night harbor]

Yup sudo futurerestore <arguments>

[night harbor]

I think so, someone got it to work on a13

[vivid nova]

Still looped

[celest basalt]

ok'

[zealous bridge]

2 people

[celest basalt]

Tuffff thank you

[celest basalt]

maybe the watchdog isn't working, but that's still a bootloop if it gets stuck there forever

[violet lotus]

Okaay i'll give a try

[zealous bridge]

What happens after a hard reset @celest basalt

[celest basalt]

goes back to same thing

[zealous bridge]

Yep that a bootloop

[wheat silo]

And don’t forget that after setting your nonce, you should verify if it is well inserted by going to system - general - information (if you have system info installed, this is a easy way noob proof). Don’t try to futurerestore with a wrong blob because it may bootloop.

[zealous bridge]

@wheat silo if your blob is invalid then futurerestore fails in the beginning stages

[celest basalt]

It is stuck in boot logo i can't see nothing

[dull swallow]

bootloop moment

what device

[wheat silo]

Oh thanks, good then, less danger 😅

[celest basalt]

iPhone 6s on iOS 14.1

[dull swallow]

wrong blob is normally detected by FR

[dull swallow]

using itunes update it to 14.4

then checkra1n

and go down to 14.3 if you got blobs

[subtle cosmos]

@celest basalt you have a checkra1n device and blobs. So restore with itunes and downgrade. Don't make it compilcated. You can always jailbreak it.

[celest basalt]

ah ok

i didn't backup data

[zealous bridge]

.....

[celest basalt]

F

[zealous bridge]

wtf were you thinking

[celest basalt]

idk

[wheat silo]

😅

[celest basalt]

probably dumb

[zealous bridge]

futurerestore wouldve wiped everything all the data anyway

theres like

multiple warnings

[celest basalt]

yeah

[zealous bridge]

on every tutorial

[celest basalt]

i got that ok

[celest basalt]

i just noticed btw

i thought i had one

[zealous bridge]

[subtle cosmos]

@celest basalt the only thing that you "should" downgrade is to have a jailbreak "on the go" if it gets release. If you don't want it, you don't need to downgrade because of checkra1n.

[celest basalt]

i will just update to ios 14.4 then

i thought i could downgrade after updating it that is what i thought

thank u guys for the help

[subtle cosmos]

Yeah you can do that. When you ask me, I would downgrade to 14.3 because for the jailbreak "on the go". I don't have all time a computer in my near so if I run out of battery or have to restart I can jailbreak with the app.

[hoary vine]

Guys is iOS 14.2 compatible? Hearing mixed answeres

[zealous bridge]

It is

[hoary vine]

For all devices? I am currently on iPhone X, 13.5

[zealous bridge]

Yes

[hoary vine]

Oh shit nice!

[celest basalt]

so download ipsw for ios 14.3 ?

and use FR to downgrade ??

[subtle cosmos]

Yes.

[hoary vine]

Going to start looking up how to do it but any advice/things to watch out for?

[zealous bridge]

Everything imo

futurerestore can fuck up everything if you do one thing wrong

[hoary vine]

Damn

[celest basalt]

ok will do do i have to download rc or public release ?

[zealous bridge]

but if you’re competent and can follow instructions

you shouldnt have a problem

[hoary vine]

What do you mean by fuck up

Like how bad are we talking

[subtle cosmos]

This one where you have blobs for.

[zealous bridge]

send your devices into a bootloop and force you to update to latest

[celest basalt]

ok

[zealous bridge]

but ur on iPX so ur safe

you wont brick tho

[hoary vine]

Yeah generally I’m competent but I don’t know how to trouble shoot

[zealous bridge]

that is the worst case scenario

[hoary vine]

Why an I safe on iPX?

[zealous bridge]

checkra1n

so you can attempt multiple restores

if one fails

[hoary vine]

Oh shit and it won’t affect SEP?

[subtle cosmos]

You have a checkra1n device. If you fucked up you can restore with itunes and jailbreak again with checkra1n and try FR to downgrade. So nothing to lose.

[zealous bridge]

checkra1n is completely reversible

everything it does

[subtle cosmos]

You only must disable SEP for jailbreaking and set nonce. After you downgrade with FR all is stock and work.

[hoary vine]

Damn cheers guy that’s good to know

[zealous bridge]

one more thing

[hoary vine]

Yes awesome just wanted to confirm

[hoary vine]

Yup

[zealous bridge]

what device are you gonna run futurerestore from

mac/linux

[hoary vine]

Mac

Any preference?

[zealous bridge]

what version

[hoary vine]

Big Sur

[zealous bridge]

eeshhhh

its good ur on mac

but big sur has caused some errors

however there have been some reported successes

[fresh hull]

Is it not recommended to try this with Linux at the moment?

[zealous bridge]

what device

[hoary vine]

Ah darn what are the alternatives?

[night harbor]

it works so i dont see why not

[fresh hull]

X (global) on 13.5.1 atm

[zealous bridge]

yh go for it

[fresh hull]

Oh ok cool, thanks

[subtle cosmos]

If you have blobs for both, I would use public because RC is "beta".

[fresh hull]

Live USB seem to be OK? Ubuntu 20.10?

[zealous bridge]

You should try big sur first

[fresh hull]

I only have 14.3 RC unfortunately

[green onyx]

do the static libraries work with linux?

https://github.com/marijuanARM/futurerestore/releases/tag/v189

[zealous bridge]

no

can you read

[green onyx]

mb

[zealous bridge]

“for macOS”

[hoary vine]

All right, will do!

[zealous bridge]

you must compile manually

or use

the script

[hoary vine]

Thanks for the help mate, I’ll keep you guys posted on how it goes!

[zealous bridge]

gl

[nimble halo]

i have gotten this to work with linux, A12 iOS 13.5 -> 14.3RC

[hoary vine]

Also last point: is the jailbreak out already?

[zealous bridge]

no

[fresh hull]

Excellent, thank you

[hoary vine]

Okay just wanted to check, cheers!

[green onyx]

is the linux compile script updated for A13?

[zealous bridge]

yes

it gives you a choice

at one point

[nimble halo]

i believe @night harbor updated the script where it lets you choose

[rustic blaze]

Downgraded my x from 14.3 rc to final

[green onyx]

pog

thank you

[rustic blaze]

V189

[west grail]

https://www.reddit.com/r/jailbreak/comments/jx0hvc/tutorial_compiling_futurerestore_187_on_linux/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

[high lily]

anyone knows what to do in case of error what=ERROR: Unable to place device into restore mode
iphone 11 pro max macos big sur futurerestore futurerestore-a13/a14-v189 13.5->14.3

[zealous bridge]

mac or linux

[rustic blaze]

Mac

[zealous bridge]

https://twitter.com/marijuanarm/status/1360614682252484611?s=21

adam (@marijuanARM)

A13 restores with the A13/A14 build seem to be broken. they won’t bootloop you & force you to update, but the restore will fail. for now, do NOT use futurerestore to restore an A13 device.

Twitter · Feb 13, 2021, 3:39 PM

new info

[rustic blaze]

Smooth sailing

[zealous bridge]

anyone attempting A13 might as well stop now

[green onyx]

oof

[nimble halo]

if anyone gets stuck with the restore, I've had success with taking it out of recovery mode with imazing after

[zealous bridge]

@nimble halo wdym

were you able to restore after

[green onyx]

@shy magnet is it the same fdr error on A13 with A13/A14 build?

[shy magnet]

no

[covert ibex]

damn i was gonna try updating my 11 last night

[green onyx]

whats the error

[zealous bridge]

whats the error

[shy magnet]

it’s an issue with wchfirmwareupdater

[green onyx]

is it fixable?

[rapid creek]

Did some on have succed on VM

[shy magnet]

well a13 restores worked before

[zealous bridge]

dont use a vm

[rapid creek]

Ona11

[green onyx]

dont use vm

[shy magnet]

so obviously

[green onyx]

seems legit

[nimble halo]

i got stuck with an earlier version of futurerestore, and it got stuck in recovery mode.
someone said use imazing to take out of it

on A12

[zealous bridge]

ok

were you able to successfully restore after?

[shy magnet]

have y’all seen people have success with the a11/a12 build

[zealous bridge]

yes

[nimble halo]

yep, i've had success with the a12 build

[zealous bridge]

lots of it

[rapid creek]

Why i try on my 6 and is work perfect

[shy magnet]

okay great

at least not everything is fucked

[dull swallow]

so issues are A13+ build

[shy magnet]

@faint night there is none

[shy magnet]

yup

[dull swallow]

oof

[nimble halo]

gotta compile it yourself https://www.reddit.com/r/jailbreak/comments/jx0hvc/tutorial_compiling_futurerestore_187_on_linux/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

[rapid creek]

Why not work on VM i do that the first version u make bro on a 6s plus move iOS 14 and work

[shy magnet]

are you dumb or dumb

[shy magnet]

i don’t recommend it

[celest basalt]

ok

[dull swallow]

there’s a script for linux

[zealous bridge]

@shy magnet have you taken a look at that “restore mode” error

[dull swallow]

xd

[nimble halo]

the only downside of upgrading from 13.5 to 14.3 is that one of my apps got removed from appstore and now I can't read manga 😦

[zealous bridge]

pretty common

[rapid creek]

I will try it no choise to move on iOS 14 if i have only windows

[dull swallow]

adam some people are getting errors restoring with Linux too

apparently

[shy magnet]

AAAAAAA

[zealous bridge]

its b r o k e n

[shy magnet]

well i have work in like an hour so i can’t really do anything rn

[zealous bridge]

understandable

[dull swallow]

future restore is a hacked up idevicerestore wrapper keep that in mind

[zealous bridge]

why is that relevant

[green onyx]

lmao

[dull swallow]

cause it’s hacked up

meaning the code isn’t efficient

[zealous bridge]

like we didn’t know that already lmao

[celest basalt]

lmoo

[zealous bridge]

this channel over the last few days have been reminder enough

[wheat silo]

You should still get it from AppStore++, it will be available in your purchases

[zealous bridge]

you dont even need appstore++ for that

just click on your pfp at go to purchases > not on this iphone and look/search for it

[nimble halo]

will keep this in mind once i can JB on 14.3, can't wait

[lilac linden]

r

[hoary vine]

guys damn I made a mistake: I only have blobs for iOS 14.1

Is it possible to future restore to it (iPX)

[zealous bridge]

no

[hoary vine]

F

[zealous bridge]

only iOS 14.2 and 14.3

[hoary vine]

Alright, cheers!

[celest basalt]

somehow got restore mode error on ubuntu too

weird

[zealous bridge]

That error again

[celest basalt]

yeah

shoot didn't try it twice though. i'll give it a go

nope

[zealous bridge]

Rip

[celest basalt]

to anyone who cares, i was able get in restore mode with yesterdays static compiled, just fdr couldnt be read or whatever that common issue was

[zealous bridge]

And i thought i got unlucky with my futurerestore

[celest basalt]

today, new static compiled a13 specifc on mac, and compiled using LGD script on ubuntu - both couldnt get into recovery mode

[zealous bridge]

*restore mode

[celest basalt]

still not bootlooped though

yes restore mode sorry

[gusty iris]

how is FRing going

[violet lotus]

https://twitter.com/marijuanarm/status/1360614682252484611?s=21

adam (@marijuanARM)

A13 restores with the A13/A14 build seem to be broken. they won’t bootloop you & force you to update, but the restore will fail. for now, do NOT use futurerestore to restore an A13 device.

Twitter · Feb 13, 2021, 3:39 PM

[zealous bridge]

oh hey its you @gusty iris

lol pretty mixed so far

[gusty iris]

yep its me

has anyone had success with FRing for A11 w the new build on Linux or do I have the be the guinea pig again

[zealous bridge]

acc

hold on

[gusty iris]

holy shit tho ios 14 widgets are FUN and the screenshot tool is so much faster

[zealous bridge]

nope not on linux

a10 was tested on linux

https://twitter.com/marijuanarm/status/1360426729727275016?s=21

adam (@marijuanARM)

Do NOT use futurerestore on Big Sur or Linux currently. looking into issues restoring now.

Likes

126

Twitter · Feb 13, 2021, 3:13 AM

there was this tweet

[gusty iris]

A10 i could care less

yea

since A10 never had the FDR issue in the first place

[zealous bridge]

nope nothing

ready to be a guinea pig again

[gusty iris]

cool ima try again, i have a backup so im not losing anything

[zealous bridge]

i would wish you luck but lock will not help you against futurerestore

i said something like that before didnt i

[gusty iris]

lol

[zealous bridge]

o r i g i n a l

[placid sinew]

When i try to futurerestore i get error -2. Why is this happening?

[dull swallow]

what fork.

and version

[placid sinew]

a13-a14

[dull swallow]

oh that’s the cannot put device into recov normally

[placid sinew]

yea

[zealous bridge]

a13 is broken

currently

https://twitter.com/marijuanarm/status/1360614682252484611?s=21

adam (@marijuanARM)

A13 restores with the A13/A14 build seem to be broken. they won’t bootloop you & force you to update, but the restore will fail. for now, do NOT use futurerestore to restore an A13 device.

Twitter · Feb 13, 2021, 3:39 PM

[dull swallow]

some people have got it working (myself included) but it’s not worth it to try

[zealous bridge]

its a relatively new issue

[dull swallow]

even though you can’t bootloop because of it

[placid sinew]

okay thanks 🙂

[hoary vine]

Hey I am back again. Just wondering: what is the likelihood of iOS 14.1 being compatible? More specifically, what makes it different from say iOS 14.2?

[zealous bridge]

its impossible

apple unsigned the sep from their servers

[hoary vine]

Alright thanks again! Just wanted to know whether or not I should continue following

[gusty iris]

LETS FUCKING GO

IT GOT PAST THE NOR STAGE

[zealous bridge]

woah

finally

its gonna finish now

dw

[gusty iris]

dont jinx it man

[celest basalt]

It’s impossible to jailbreak 14.4?

[zealous bridge]

as of now

[gusty iris]

there is no public exploit as of rn yea

[zealous bridge]

maybe not in a year

[celest basalt]

Alright.

[celest basalt]

just tried a13 every which way. just saw the update from Adam

Can you jailbreak an ipad?

[zealous bridge]

depends

what ipad and version

ipados

or ios

[celest basalt]

Uh, what’s the difference?

[zealous bridge]

nothing

its just renamed

[celest basalt]

I have a Ipad 5th gen, just not sure what IOS.

[zealous bridge]

settings > general > about

[dull swallow]

checkra1n

ez

[zealous bridge]

ipad 5 was cut off at ios 13 right

yh so you can use checkra1n

if ur above 12.3

@gusty iris whats happened

[gusty iris]

Done: restoring succeeded!

[zealous bridge]

yay

so A11 and A12 are fixed on mac and linux

very good news

A13 on both mac and linux are fucked

the situation has become simpler

[gusty iris]

Activation successful and restore in progress

Very happy, I really thought this was just going to fail again.

[zealous bridge]

good things come to those who are patient

[celest basalt]

@west grail did get a13 to restore on Ubuntu somehow

[zealous bridge]

yes

that was when a13 worked

now it doesnt

some dependency got updated

and it broke it

[celest basalt]

Oh I thought he restored quite recently. Good info!

[zealous bridge]

^

[celest basalt]

Sounds like I should have never went to bed then 😆

[jagged lotus]

It’s still not fixed?

[zealous bridge]

what device

[jagged lotus]

a13

[zealous bridge]

it was fixed but now its broken again

[jagged lotus]

Can I just use an older version or is it something server side

[zealous bridge]

server side

[jagged lotus]

Is it fixable

[zealous bridge]

it is

but the dev is currently at work rn

[jagged lotus]

Ok at least it’s a fixable issue

[junior fiber]

a11 worked for me after using --latest

[zealous bridge]

another success

someone should make like

a troubleshooting guide

for all these errors

[dusky warren]

a12 just worked for me as well 13.5 --> 14.3

[zealous bridge]

hes right

[normal geyser]

so wait is the a13 fork broken or not

[zealous bridge]

when m1sta said 14.0-14.1 was incompatible no matter the device

y e s

[versed atlas]

im on a11 13.5 , did you fr to 14.3??

[slow pecan]

i made an exploit for 14.5 come buy it from me

[junior fiber]

yeah

[gusty iris]

I just did!

[versed atlas]

macOS or linix?

linux

??

[gusty iris]

I just restored my backup and I'm waiting for the loading bar

Linux

Ubuntu

[zealous bridge]

have you tested touch id yet

[versed atlas]

linux vm or via usb?

[gusty iris]

Erm, I have it installed to my SSD.

[versed atlas]

so you have any tutorial??

[zealous bridge]

check the pins

[gusty iris]

Its the same as the normal tutorial

[zealous bridge]

via usb

[gusty iris]

just compile it yourself with the script

[zealous bridge]

vm is unreliable

[gusty iris]

Not via USB

no

no

i ahve it installed

to my SSD

idk if its different or will work on an SSD

sorry capt lol

[zealous bridge]

think hes overwhelmed

[gusty iris]

Apple Pay setup went smoothly

TouchID works fine

[zealous bridge]

have you tested touch id

ok good

[celest basalt]

@slow pecan 20

[slow pecan]

dm me

[river lantern]

Ey! Nice!

So is there a chance that iPhone X futurerestore to 14.3 (macOS big sur) will break FaceID?

Oh I thought big sur was working for A11-A12

[celest basalt]

Proof

[high lily]

People say big sur is ok for FR. but i got error on a13. Don't know if it was first because of big sur or because of broken FR

[sharp latch]

The first one about 14.2 sep isn’t true for a11+ it’s just a10 and below that can go to 14.2

[river lantern]

I think Big Sur is working for A11-A12

Not sure

[subtle cosmos]

You must specific this

• 14.4 SEP and BB are incompatible with 14.1 and lower on all devices
  and
• A8-A10 devices can use THEIR branch of FR to restore to any iOS 14 target
  more because it contradicts himself.

It think you mean A11 and up for baseband incompatiblity.

And for A10 I am not sure because < 14.1. I test it with my i7 rn.

[mossy breach]

What's the latest version that checkra1n is relatively stable on? I'm planning to upgrade my iPhone SE (A9) and switch to checkra1n

[shy magnet]

• a8-a12 all use master
• i need someone to test 14.2 on A11 or higher (i only tested a10)
• i think big sur is fine, but i wouldn’t run on M1

😮

the man

the myth

the legend

@river lantern

[river lantern]

Yeah. From what I read on here, A11-12 worked on big sur 🧐

Ah, hello @shy magnet

Thank you for all your work

[shy magnet]

14.2 and up with 14.4 sep on a10, not sure about any newer devices

[river lantern]

We all appreciate what you and Cryptic have done 💕

[sharp latch]

I tested a11 on 14.2 but no one cares lmao

[zealous bridge]

a11 and a12 are having good success rates

big sur linux both work good

[river lantern]

Nice! Good sign for me on my A11 with big sur

[shy magnet]

nice

[shy magnet]

my bad, was it success or failure?

[sharp latch]

It was a failure bro

[shy magnet]

yeah

incompat

[sharp latch]

FDR right away

With 14.2 a11

[shy magnet]

oh yeah i remember now, that’s why i’m wanting more people to test 14.2

[sharp latch]

Fax

[zealous bridge]

yh i dont think 14.2 works on >a10

[shy magnet]

there’s been so much misinformation about iOS 14 futurerestore

[sharp latch]

Right it’s rough

[shy magnet]

that we even believed

that i wouldn’t even blame a certain person

[sharp latch]

I feel like an idiot as well tbh

[zealous bridge]

we just need one consistent and accurate source of information

instead of this mess we have

[celest basalt]

we need an insider at Apple

imagine if recovery worked on Corellium

[zealous bridge]

why doesnt it

[celest basalt]

idk

ideviceenterrecovery says successfully rebooting into recovery but then it just boots back into normal mode

[zealous bridge]

but a13s broken...

[shy magnet]

yeah

a13/a14 broken

[zealous bridge]

also put ubuntu also works for <a13 right now

[shy magnet]

can not restore currently

besides that yeah