#futurerestore-help
1 messages Ā· Page 22 of 1
Was about to ask how reliable a vm is with this
capt, can u confirm a vm would work
well i used a win7 vm before with futurerestore
aight
not sure abt the similarity
but
in terms of usb passthrough
it should work
unless fr is broken on mac too
@zealous bridge apologies for the ping, but is A12 also affected by the FDR error?
my a13 keeps failing using the static compiled on mac. could be me but the tutorial isn't that complicated
if you have a12 try using v191 instead
that is less likely to fail
FDR error?
oh yh its you
i remember
4 people
btw, A10 below on linux it should okay right ?
same error
yes
use an old version
190 should be good
no
well i just compiled the latest version, v193
apparently building linux from source should work
it is okay ?
@night harbor Tried the commit prior to A13, same issue
thats fine
I manually editted the files to what they were before the A13 commit which was just 2
building the future restore from source code on linux should work
no
it doesnt
according to adam
adam isnt working on linux however
u opened that github issue yet
no
i just asked if hed be looking for testers
okay, thanks you!
interesting..
catastrophic
I ran your script with the FR make stuff commented out, changed the files, then ran the-
wait yeah no ok
i ran the stuffs
it all compiled and made fine
is adam a heavy weed burner or what?
wait does A13 work if u compile it on linux?
weed kingpin moved to jailbreak scene
all makes sense now
if they just made a dockerfile for futurerestore
not right now
Idk I dont have A13
these unreliable pieces of software are why dockers exist
ive only got A11
man it would be so much easier
If you've got anything to try, I am willing
anyone in here got a13 working? i saw adams tweets saying good to go. anyone able to replicate?
no go
no go
not rn
@shy magnet wait is A13 on linux good to go?
thanks dog
haven't tried anything on linux so far
he doesnt work with linux
but i have no reason to believe why it won't work
It doesnt
^
couldnt get a13 working on mac, but im ass so...
5 ppl have reported FDR error in the last 2 hours
idk whats going on
something broke
send me the people who have
2 of them on mac too
is apple fighting back?
im the only one who got bootlooped tho and lost my jb
I am, sent you a dm earlier and I can send any info
on a fresh install of Ubuntu too 
i'm another one
^
tried to restore my A13 as well, couldn't get it to work, says it failed to find matching buildidentity. Though i'm pretty sure I followed the tutorial correctly
@celest basalt what platform r u on
mac
u used wrong buildmanifest
mac
macos
hm
adam pls look into it
how do i get the correct one?
@green onyx did u try it
it should be from the 14.4 ipsw
m1?
nah
no, bc everyone is saying it wont work
idk
nvm i just checked and theres like four more who had it yesterday
ok
oh i remember now
someone had a restore mode
lol @ the "v191/futurerestore-v192.zip"
unpinned the tutorial one since you linked the same thing right above
@shy magnet
@gusty iris - Ubuntu (FDR)
@celest basalt - Mac (FDR)
@junior fiber - Mac (FDR)
@celest basalt - Mac (FDR)
@celest basalt - Mac (Restore Mode)
yup
Chatting with them ab it in dms
thanks Tanbeer for all your hard work getting it straightened out š
thank the devs, not me lol
here's the set of commands for resetting to 191 for those who may want to try it (not sure if this helps in any way):
git clone --recursive https://github.com/marijuanARM/futurerestore
cd futurerestore
git reset de444ceee137537615a36b53aa7c7e58d2b7c21d
git reset --hard
git submodule update
./autogen.sh
make
sudo make install # remove sudo if on mac
Is the a13 thing getting sorted out? My internet went out
in progress
oh
Holy fuck its 1am
Thatās good
8 here
ehh tomorrows Sat
feel like this discord doesnt sleep
It doesnāt
time zones exist
Weāre up 25 hours a day, 8 days a week
saw good news around midnight est, woke up and read a lot of posts ha
seems that way
Same
i forget time zones too ha
Iāve been folllowing this since I missed the chance to update to the rc due to an update issue with my pc
what device and version you on?
i didnt update because futurestore sounded easy
Iphone se 2nd gen, iOS 13.5 and I have blobs for iOS 14.1-14.4 beta
11 pro max here if it matters
both a13
Yeah
haha you and me both
only i did this on 13.5
ok
never used it
and ur on pc so im guessing ur tryna use ubuntu @jagged lotus
well thats a no go rn
yep
well you wouldnt lose anything anyway
youd just be panicked a bit and when futurerestore did update you can go back
Iām gonna start saving blobs on my old se now to test this stuff out
nice
bye thanks
i think cryptic is working on a linux future restore after he gets mac sorted
Pls Super ban
I think the guide now so clear for mac users
@TenslasterGames @HidayetZeno @DLinuxz @askmetostay323 @CStar_OW A13 works fine with futurerestore now
tf it works?
@zealous bridge it works?
anyone confirm now
wait
theres no new commits
it does
that was 6 hours ago
probably people who compilied it wrong
xd
keep in mind you have to update img4tool
So as a windows user
Iam going to download catalina os and follow the pinned guide
hackintosh?
Yes
i'd just wait for a working linux version
@gusty iris did u update img4tool?
Thats would be better
try again
Yeah but Adam is working on it rn
Buy after saw the pinned guide for mac i think its very simple using mac
no
just wait for fixed static binaries
^compiling doesnt work either
linux static binaries wen
mhm
compiled versions dont work with A13
??!
So as i said on Catalina os will work without problems i guss
explain what?
do whatver u want
š
Iam so confused after i decide to do i read on someone who failed to restore then i become confused again
What wont work exactly ?!
A13 fr
But adam said it confirmed working
There isnt feedback until now ?!
A13 ?!
I fixed my buildidentity error, turns out I was using a 14.2 blob instead of 14.3. But I ran into another problem...
FDR 0x7ff6309ca8e0 terminating...
ERROR: Could not read data (-256). Aborting.
Cleaning up...
[exception]:
what=ERROR: Unable to restore device
code=67829777
line=1035
file=futurerestore.cpp
commit count=192:
commit sha =569f0aef459ed203ce5643c2a13757922999b252:
Done: restoring failed!```
After all i saw about failed to restore
I will wait ios 15 jailbreak , iam done
no, bc he did A14, not A13
i asked him
bruh
itās the same shit
I will be no6
Vmware IS WORKING ?
my futurerestore was straight from crypticās twitter š¤·āāļø
maybe big sur fuckin it up?
i used mojave
I suppose no windows version support for new futurerestore
11pm didnāt work. Just tried it FDR error .. could not read data Bla bla bla
A13?
Yep
Same, i already tried twice now and still got the same error
werent you a test dummy xd
that got A13 working for future restore
6 ppl have it as not working
I was walked through by Adam step by step pretty much so thereās that.
leak the steps š
send ss of what he told you to do
we could pin it and tell people to follow the steps
no Mac to compile futurerestore for ubuntu š¦
@celest basalt @junior fiber @celest basalt @celest basalt what Macs are you running futurerestore on, are you using the compiled binary or building from source, and what version of macOS are you currently running
iām using Big Sur, compiled and source, on a Macbook Pro 2020 over tb3

not M1
MBP 2017 connected via thunderbolt - compiled binaries from crpytiiic's twitter/releases from github - Big Sur 11.2.1
usb c to lightning cable?
hm
issue with big sur potentially?
@celest basalt @celest basalt what devices are you restoring, what version were they on previously, and what version were you restoring to
iPhone XR - 13.5 - restoring to 14.3RC via blobs
iPhone X to 14.3
The 5 people who got errors, how far did your restore go?
@grave dune 4/5 had FDR errors
@celest basalt iirc your restore didn't actually fail, just wouldn't enter restore mode?
@grave dune would you like for me to pastebin the debug? still have it open
exactly
FDR? I got to Ross ticket is that before or after FDR
iāve compiled usbmuxd and fr and idevicerestore previous commits a few times
nothing helped
Iām illiterate when it comes to technology Iām just trying to help deduce lol
kicking out of recovery mode via iMazing boots into vanilla iOS so it seems it doesnt get too far into the restore
think it may just be a big sur specific issue
hmm. mladysirk mentioned they used Mojave. let me run a VM and see if that does anything
usbmuxd shouldn't matter
apple's works fine
so probably SE 2020 would not work too
i also just got fdr error on big sur
perhaps
might be due to codesign idk
used to work on 11.1 when i went to 14.0.1 a while ago
wonder what the problem on linux is
just recovery mode detection here on Manjaro
but irecovery detects it and works still
did you successfully restore on linux?
no. i posted all my testing in my bug report: https://github.com/marijuanARM/futurerestore/issues/6
assuming it would be the same with ubuntu
quick question- are the terminal commands in the pinned mac futurerestore guide also applicable on linux? or are they different on linux? thanks!
kinda i guess
but linux is broken
Do NOT use futurerestore on Big Sur or Linux currently. looking into issues restoring now.
ooh i see, thanks a ton for the tip! š guess ill go bother my friends to see if i can borrow a mac
im pretty sure some libraries have them
imagine seeing a guy in the library using future restore
There is no way you could get the root login for one
sudo should work
you can sudo without the password?
depends
i imagine theres some restrictions/lockdowns on the terminal and whatnot
well i mean at my school i can still access windows powershell
joe
Mama
bama
moe
smoe
one more question^^
are there any known issues why a bootable macos usb would not work? or should it work as well as a bootable linux usb?
bootable macos usbs exist?
i was like what
Bootable mac wont work on pc
i have a question
No
gotcha thanks everyone!^^
no, you only speak when spoken to comrade
omg its lebron 
so for capts FR tutorial, it says to āget your blob for the target versionā, does this mean the blob that iām wanting to update to
i know itās a dumb question
@golden silo 
thank u
okay one last question. Iām planning to use my 14.3 RC blobs since i donāt have 14.3 blobs. The build ID between the two isnāt the same. ipsw.me doesnāt have the RC build. Can I use the 14.3 ipsw instead?
ipsw.dev does
Download developer beta versions of Apple's iOS, iPadOS and tvOS firmware.
it has 14.3rc
ah alright, thank you. sorry for dumb questions
we've all been there. its not a dumb question
yea iāve just setup FR for the first time since iām planning on updating to ios 14.3 soon
ah so big sur is broken too?
lmao, good thing I didn't run my FR today on the Big Sur I have
not sure, my mac is still on catalina haha
Just saw this. Not at home right now but I used the static compiled. Idk macOS version specific but itās Catalina
Shit maybe not, Iāve been letting someone else use it maybe itās updated. Iāll check in like 30 min
can i use ota blobs to downgrade from 14.4 to 14.3 on iphone 8?
im trying to do this via ubuntu, running the script posted a while back to compile for linux, getting 2 errors:
Package 'python-dev' has no installation candidate
Unable to locate package libzip-dev
what Ubuntu version? also try running
sudo add-apt-repository universe
sudo apt update
that repository add fixed it, thx for helping this linux noob haha
im gonna try and futurerestore my a12 ipad air to 14.3RC
it's pretty risky to futurerestore on ubuntu rn, so i recommend to hold for now
oh? what's the issue?
some people are getting issues, not really sure what causes it
hmmm, might hold then - at least it looks like this has compiled perfectly so it's just a matter of hopefully stability in the next few days
MacBook Pro (13-inch, Mid 2012), static compiled from earlier today, Mojave, iphone 11 pro max, 13.5
Any idea why I get successfully up to āEntering Recovery Mode...ā then my device hangs & terminal output says: āERROR: Failed to place device in recovery mode Lincoln++abi.dylib: terminating with uncaught exception of type tihmstar:::exception Unable to place device into recovery mode from Normal mode
Abort trap: 6ā
Iām trying to upgrade my 13.5 iPhone X from 13.5 to 14.3RC.
My device is stuck in recovery mode and futurerestore doesnāt detect it after āEntering Recovery Modeā
fml, i just realised when i saved blobs for 14.3RC i didn't specify nonce and all that
guess that means my blobs are unusable
damn i couldnt even save blobs without doing that
This isnāt true, download them and open them in a text editor. Find āgeneratorā
It will be there
if your on unc0ver, should be 0x1111111111111111
u0s is just easier
i did use unc0ver to jb, but i didn't set anything when i saved it
search nonce
find next
im certain i fked something up in the saving process bahahaha
mine defaulted to 0x1111111111111111 when i saved too
this was the only entry with 'nonce'
^
desktop version of tsssaver
what device
ipad air 3, 4g
so yeah, A12
i specified an apnonce for it on the desktop version, the same apnonce that i saved when i did the backup for 13.5
for when i backed up 14.3RC
yeah, when i go back into my 13.5 blobs there's a folder that says apnonce-xxxxx and noapnonce file
whereas my 14.3RC ones dont lmao
that moment when your generator isnt unc0ver's default or odyssey's default xd
i just tested my 14.3 rc and it doesnt have generator in there either, but i used easyblobs or whatever and def but all the info in. I saved another one from shsh.host
what in the fuck is that
use the standard blob savers please
shsh.host/system info/telegram bot tsssaver/patreon autotss bot
i said the name wrong but it was something like that
but i did use shsh.host and it did have the generator in there
luckily i did both
blobsaver****
it did help me find the apnonce mad easy which i used with shsh.host
generator is there, but the only result for nonce is
</dict>
<key>noNonce</key>
<dict>
that bad?
do you know what youre talking about? Because i dont
not really, but i do think i screwed up somewhere lol
Hmm I wonder if my shady patched Catalina will work lol
how do i verify? futurerestore? i gave up when i realised i missed a step previously lol
umm i believe shsh.host can tell you
says verified good to go
yeah
it says file is valid for me too
hmm i mightāve done something wrong when i compiled FR
It should work fine if I have this in unc0ver right?
yes
Thanks
iām setting up FR again since i botched it the first time
my nonce is in the file name, but can't search for it. could be totally normal. im new here
^ this is also my situation, im literally this guy too
fucking adam and his bullshit software wonāt work on linux or big sur which is all i have access to
why canāt this free tool have faster support
ima just try and yolo it
iām on macos catalina 
i tried twice no luck though
did you solve your problem?
tried again. didnt work but still no bootloop so thats ok
anything to do with itunes? ive seen it mentioned but not in this tutorial
fuck
same here but are you sure something should be there?
i did yeah
so my blobs fucked?
weird not sure why it didnt work
the nonce is in the file name
i also saved blobs on my phone
with systeminfo
hhhhh
is that different then what you just looked at? Let me know if the noNonce shows there or not
wow
try check your blobs with blob checker. as long as it showed apnonce:
27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae
that apnonce generated from 0x111111111111111
^ for A11 device below.
oh then im probably fine
i used blobsaver and systeminfo for my blobs
((there is a longer apnonce there i just censored it))
1conan blob checker?
yes
i got apnonce and sep nonce but no generator. shsh host check shows generator though. weird
did it show this number 27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae apnonce ?
no
isnt everyones apnonce different?
it should be right
again i have no idea i just though
it should be im pretty sure
if the key generator is 0x1111111111111111 then it should generated apnonce:
27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae
^ A11 device below only
???
r u sure
source of this?
im a13
actually you could potentially be right im a12
A12 device later had nonce entangle, so it will generated difference apnonce even the generator are 0x1111111111111111
ok that makes sense thank you
ok im big dumb, when verifying my file on shsh.host it does show both my generator and apnonce
i guess thats just not something you can search in a text editor?
when you actually manually upload your blob into shsh.host it shows all the info, if you just search by ECID it wont show as much info
anyone here use odyssey and know if the set AP nonce generator works now?
on A13 btw
@versed atlas no I have not solved my problem on A11 being detected in recovery mode
for the apnonce ? well you need img4tool to see the string apnonce.
for the key generator, yes you can see it via text editor
oh word, then all should be good.
amatuer hour
does anyone know the difference between 16C66 and 18C65
66 better
rc vs rc2
66 just has more updates
or fixes or whatever
do you guys use dimentio to set apnonce generator
closer to stock, or actually stock
well im sol on that
because c65 has generator in it
and c66 doesnt
thats great
i got 65 only
most people got 65
so thats ok
my 14.3 RC blobs have the 0x11111 generator
65 was the one that was signed up until a couple days ago so a lot of people grabbed that
i had c66 in december
too bad it doesnt have generator in it
you tried to verify at verify.shsh.host
would tell you straight up without any searching or anything
generator and apnonce
...huh
can apnonce randomly change? 
feel like i had my blobs setup right but now blobsaver changed my apnonce
from my previous blobs
when i rechecked
anyone else getting this error?
Unable to restore device
code=67829777
line=1035
file=futurerestore.cpp
commit count=192:
commit sha =569f0aef459ed203ce5643c2a13757922999b252:
Done: restoring failed!
yeah i heard if you go into dfu too many times it will change
idk if that true
dfu or restore i forget
im definetly getting Done: restoring failed! ha!
i have no idea whats going on her jengis sorry
yup correct
just upload the blob and it will select 14.3RC for you automatically
???
let me reattempt
oh i ma dumbass
and didnt scroll down
lol
awesome its valid
word
my rc has a generator
and normal one doesnt
mmmmmm
hmm
did the nonce show?
not sure if every phone needs that
mine did though
wait im lit af, can i even futurestore from 14.2 to 14.3 if i have blobs for iphone 11 pro max?
no
you have to be jailbroken
you can do it if the 14.3 jb supports 14.2
but not right now obviously
also if you werenāt jailbroken when you saved blobs then they wonāt work
yeah you should be good on 14.2 to jailbreak if one comes out though, if your goal was only to jailbreak
yeah
since im a12
((its just censored))
oh you just censored it out or something
lol nice work i thought was blank
no they werent its just censored good
..
why censor it btw? not criticism; just curious
Because the discord nsa will find you
yes
def
big facts
is the generator missing on the c66 file gonna fuck me over
from using it
Who knows, an Apple employee could be among us
but did c65 and c66 had same apnonce ?
oh so the generator doesnt matter?
I'd laugh if capt was cook
as long as apnonce is same
Would explain the noobness
with all that money for research and concern for locking down the device, theyd have to have someone in here
cook stole my blobs
thank god i kept up with 14.# releases
wait
if you have 14.3 saves just use that
not one of the two rc
it didnt have generator in it so i grabbed rc
but i learned apparently fuck the generator
oh my bad im sure you said that
as long as apnonce is same its fine (apparently)
yeah i dont get that i thought generator was important? seems like a big step in tutorial
Hey so in the tutorial we have to set the generator in the tutorial with the odyssey app. What exactly am i setting it too?
do you know how to read pinned posts?
question, im trying to compile futurerestore using the latest fork on ubuntu, and using a compile shell script which is failing because it cant find libzip-dev.
literally just says:
ubuntu@ubuntu:~/Documents/futurerestore-master/futurerestore-master$ sudo apt install -y libzip-dev Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package libzip-dev
so the nonce generator must generate the nonce (lol) so i guess the generator only needs to be on the device which, based off the generator code, will look for the answer to the generator code, the nonce code, in the blob. so generator code in blob is only used for identifying/reminding you what generator code you used
maybe?
donāt run futurerestore on a12-13
or a11
right now
and just compile it with the script
but if you do it now youāre just gonna have to do it again when it gets updated
wdym updated
I have only OTA blobs of ios 14.3. Can it be used for FR?
@celest basalt so I'm thinking I find the generator using shsh.host, and set the generator it puts out to the one on my phone using the Odyssey app?
Have you saved blobs yet? Whatās your goal? It might be too late
wasnt it already updated? if i remember correctly, adam already updated his code to reflect that they figured out how to get past the FDR bug to get to 14.3 on a11, a12, a13, and a14.
I already have blobs for 14.3RC
i downloaded that fork
Ok
I should upload my blobs to shsh.host and find my generator that way?
and maybe mojave / high sierra if you compile it manually
not on big sur?
is there a link that says linux doesnt work right now?
Damn
just curious that i didnt read something
Do NOT use futurerestore on Big Sur or Linux currently. looking into issues restoring now.
yep missed that
oops
thank you aaro
well uh when it gets updated, is that what I should be setting it to?
yeah thanks aaro
Can I upgrade mojave to Catalina, or do I need futurerestore for that too? š©
me when i
at least the apnonce are the same ig
yes just use the catalina installer for the app store
did you use blobsaver?
nah I used systeminfo
amazed my dumbass has managed for my apnonce to not change
when my phone has died like 30+ times
Thatās ok I understand
then they should already be on shah.host
yes but you will have to compile again when it gets updated
so thereās no point
but out of curiosity, how do i fix it so it detects that libzip-dev is a thing?
because it cant find that package
Yeah I'm just wondering when I'm setting my generator as it says in the guide, I'm setting this to the same generator value of my blobs right?
just run the compile script
i did
are you on a debian based build
iim on ubuntu 20.10, running from a bootable usb stick
yes
because i have no space on my hard drive
well thatās the problem
do a full install
or it wonāt work
do you know how much space it takes up?
lemme try. i have about 16 GB left
if you use mint
which i suggest
you can use ubuntu i guess
or debian 10 but thatās a little trickier
Has the a13 issue been resolved or name/specified?
@normal geyser thanks for your help that makes sense! just got one last question, after pasting my generator into odyssey, do I need to respring or anything?
if you do it with odyssey you need to rejailbreak
but if you change it with system info or dimentio it should apply
i would use dimentio or system info
Weāre you on Catalina when you tried before? Or did you not try
yes but it doesnāt work on big sur or linux
right now
I havenāt tried, but Iām gonna use Linux once itās fixed
Since my apnonce is the same as the one that has 0x11111 generator in the text am I able to make the assumption
it used the 0x11111 generator and didnt write it to the file
uh
@normal geyser I think I did it! Did not have to respring or anything. Thanks for your help
good luck
I keep getting fdr error with the latest fork from Adam.. f*ck this tomorrow I try again. A11 from 13.7 to 14.3RC1 btw
both have the same apnonce just one doesnt have generator
do you mean 14.3
Yeah sorry!
what os is your computer on
You just said only Catalina works, or nah?
Oh yes my fault
high sierra works if you compile it yourself
mine failed on ubuntu
Yes sir
ERROR: Could not read data (-256). Aborting.
ERROR: Unable to receive message from FDR 0x55660fc44050 (-2). 0/2 bytes
FDR 0x55660fc44050 terminating...
Do NOT use futurerestore on Big Sur or Linux currently. looking into issues restoring now.
Thank you!
boutta steal my cousin's macbook
@nimble halo
ah
you should probably update anyways
wew now my ipad is stuck in recovery mode
Yeah I did
make sure to set your generator again
I imazing to get out because I couldnāt figure out the line command thing
doesn't look like it
powered off and back on, same restore screen
yeah use imazing
Damn 33 minute install! Idk if this is happening tonight
A11 doesnt work on latest future restore
?
L
Hmm
i mean itās not a big deal for a11 bc if it fails you can dfu restore to 14.4 and jailbreak and do it later
Must be nice!
Damm
true
stupid a13 phone
or you could compile v188
V188 works good? Tomorrow Iāll try then, thanks again
what are my odds of being able to proceed if i just keep it in recovery mode until an update is issued for futurerestore?
idk i think it should
decent
oh i figured out how to dual boot linux. ill just wait for the source code to be updated again and then try again. thanks everybody for the help
nvm it might not
idk if imazing canāt get it out of recovery you might be fucked
adam is working on it
let me reboot to windwos and try imazing, im really not familiar with linux lol
does imazing even support linux
it doesn't, that's why i had to reboot
Yeah thought you were on Mac sorry
no
oh that
Seems to be what Iām experiencing
X2
Iām still going to try the Catalina though. If I boot loop, whoops
Nah fuck it Iām sleeping catch you later
adam is editing the README for future restore xd
š® new push
good idea especially on A12+
it's okay, i managed to get out of it using imazing
ill wait till the next futurerestore update to try again on my A12
well, as long as it still boots up and you can set nonce you're fine
I just said good idea to keep it there bc keeping it in recovery should make sure the nonce stays the same (idk if it resets when it bootloops but normally does when you reboot to normal mode), but in that case you're fine either way
I kept my XR in recovery for like 12 hours when I was trying to get futurerestore working for 13.3->13.5 a while back and the nonce stayed the same
i used the default nonce in u0 when i saved blobs so it should be okay?
yeah should be fine as long as you set the same one when using futurerestore
okay
here's current futurerestore status
the master branch is for restoring anything BUT a13/a14
okay
and the a13/a14 branch is for ONLY restoring a13/a14
oooo im on A12. i'll attempt
what is master branch?
https://github.com/marijuanARM/futurerestore/tree/a13/a14 A13/A14 branch
the READMEs on both branches are updated to show which is which & give a warning
Oh i was about to update to 14.3 on A13
https://github.com/marijuanARM/futurerestore master branch FOR A12 AND LOWER
someone pin it
@storm apex update ur futurerestore compile script to ask if a13/a14 or anything else
read above^
yoo M1sta
I have 14.3 and 14.3RC
both have the same apnonce but one is missing generator
if I ran it just now which A did it compile for o-o
am i able to make the assumption because its the same apnonce it used the 0x1111111111111111 generator
has the linux restore issue being fixed?
as far as i know
@celest basalt pin the branches
if the apnonce matches it should be the same generator for the same device yes
this is what was causing those issues
not certain operating systems
if you were using the static build
it won't work on a11/a12 at all
so linux should work fine
ight thank u
works fine
For A12 and lower: https://github.com/marijuanARM/futurerestore/tree/master
For A13/A14: https://github.com/marijuanARM/futurerestore/tree/a13/a14
what distro
debian testing
Static should still work for a13?
wait when was this updated? i failed with linux about 30 mins ago
static will only work for a13 and a14
how can i remove the old futurerestore since i installed the wrong one
just rebuild whichever one you need
Didnāt work on Mojave, updating to Catalina now
should it work on ubuntu
lol
do i just need to rerun this build script here: #futurerestore-help message
Wait for an update
still dont have future restore for catOS man 
I will be updating it shortly
epic
what broke
just reorganizing
oh xd
can i just change the futurerestore github link in capts script to the a13/a14 version?
i'd say just wait for him to update it tbh
for capt?
Scripts suck imo
well i need the A13 one
@vivid nova i'm the static god
No you're not
I don't fuck with windows
Exactly
And if you're gunna static.. Do it on Sierra
lol
@vivid nova I don't have a sierra machine
static linux wen /s
I need a SYSROOT
Bruh.. Vm
too much effort lol
vm's are shit
sysroot is fine

gonna make a sysroot @vivid nova
All i ask is for ppl to quit using Mojave >
mojave unstable but catalina is pretty damn stable big sur is not
all i ask is windows stop installing microsoft teams
@vivid nova does high sierra support sierra
Ooh yeah.. "too much effort" just to load up a vm š
Does Joe mama support joe fatha?
sysroot is way more efficient
so does high sierra libc++/libsystem/libz support sierra
You're using more brain cells to make sysroot rather than re-compiling on a vm
sysroot I just have to download a dmg
And yes, it does
so I will
I think (actually) it should be as low as el cap
nah i heard mountain lion is the OS
For those rock'in 2008 Macs
Also, why is your static less than 2 mb when its usually like 5?
mac curl
I've been trying to get macOS working in VMware btw
I have the unlocker and all
Just upgraded from Mojave to Catalina, still same error but I see cryptic in here now saying fix needed
Vmware > parallels
I got the installer to start but it's stuck on Apple logo with a progress bar
Virtualbox is epic
Vmware doesn't corrupt
even tried changing to Win10 and fiddling with smc.present
virtualbox doesn't work along WSL2 
Is your rig Intel?
I thought they fixed it
wsl has no usb
yes
yeah and? I'm not using WSL for FR/checkra1n
Vmware is pricy
Make sure your rams on exactly 4 with 2 cores
just need it for other stuff
ik
Most issues with Windows vm is virtual bios setting
is 14.4 sep compatible with 14.3
are people using futurerestore with vm???
Yes
ok i wonder if sep will be changed in 14.5
with lower 14 versions?
Yes
can you please @ me when it's been updated?
No
š¦
okay then iāll just wait until the 14 jailbreak to update to 14.3
doesnāt seem necessary to update now
Doesn't seem necessary to jump ship to 14 when 13 is pog
another update xd
Updated it now, it was just a small update to ask the user if they are using an a13/a14 device or not
but mah watch 
nice
I don't think hs has such..
it did
yeah i thought it was updated since i got the prompt, which i set N for a12
but i still get the same error o.o
I know it has time machine snaps
Sleep on it.. Give it a week
Sending NORData now...
Done sending NORData
ERROR: Unable to receive message from FDR 0x55ac026e4460 (-2). 0/2 bytes
FDR 0x55ac026e4460 terminating...
ERROR: Could not read data (-256). Aborting.
Cleaning up...
^ is where it fails
14.5 will be compat.. So no need to worry
o

