#futurerestore-help
1 messages · Page 28 of 1
it does work, just the static building part is slowed
opa isnt releasing it until static build fully done
he could probably make a script to compile it tho
no tf?
hol up
isnt that macos
it is
oh i was talking about the windows build
not A13 build
lmao
windows build = fine except compiling statically sucks
A13 build = fucked
opa wont release until its statically built
oh i wasnt lmao
just a dumb question: does fr do the same thing as an itunes restore?
is there anything fr doesnt wipe that itunes does
it’s just a restore
@green onyx it's literally iTunes with a modified tss agent and device add-ons to "okay" the process
aight lmao
master branch on a13 moment
@shy magnet watch that be due to firmware if
seriously
so nothings wrong with the A13/A14 build
nope
people were using master
cause someone else tested here
lmao
yeah
why has A13 been such a pain
in other good news ci is basically done
CI is static right?
yeah
true
future restore technically did work before all of this though right?
it was just people using outdated builds?
well
just need debug log using my latest build
^
lol
192 on my twitter has always worked for a13 a14
we reverted back to 192 commit
then a14 worked
my main focus has been ci
or was it all just git shit
I didn't look at to why it failed until like yesterday
will you work on static linux after static mac?
@shy magnet watch build 69 work lmao
opa is making static windows apparently or just a script for windows
@dull swallow yeh but ill just do it via ci not host linux
ultimate nice
build 69.420
@dull swallow I'll add it to ci if it works
what’s happening in general VC
don't care
jackbox
oh nice
what is that?
ah so I wouldn't care probably
nah
@shy magnet success but running the futurerestore command for usage will return error 255 lol
ah
So, FR working fine on A13 ?
it works afaik
yes succession works, i used it on 13.3.1 once and it worked perfectly
@golden silo U still on 13.3.1 ?
yes
ah ok, wanted to know if you’ve tried to FR or not
ye when its out, sep and bb arent compatible
so ur blobs r going to go to waste
i never fucking asked
14.5 beta sep is compatible anyways so i don’t care what you say
hell no
but ok
apple isnt dumb
ofc 14.5 sep and bb is going to be incompatible
you’re uninformed
you keep on insisting that. are you an insider or something? how are you so sure? yes, sep/bb incompatibility happens mid-iOS but NOT ALWAYS!
apple wouldn’t care about FR
cause it only affects people who saved blobs
which the common user wouldn’t do
how would i go about updating to 14.3 from 14.1 using Futurerestore
i am on Iphone XS Max on 14.1
I dont really know what blobs and seps are
you don't right now, until someone releases a jailbreak or a noncesetter
well, if you don't know what blobs are, then you cannot update even when a jailbreak comes out, as you definitely don't have blobs then...
Hey just a question do you guys know if I would be able to downgrade to 14.3 just in case future restore goes wrong when updating to 14.3?
I honestly don't know if I saved the blobs properly for my device because I recall using a generator option from this tweet like an idiot
what device
iPhone 12 Pro
Fudge
Damn I'm an idiot welp my device won't be able to update but my lil brother should be will try right now thank you though man I messed up
they’d be invalid since you wouldn’t have saved the blobs with apnonce
can i use the new fork of futurerestore on linux in wsl?
should i even bother updating? im on 14.2 already but i have blobs for 14.3
is it worth the effort?
0 votes and 0 comments so far on Reddit
true
Since iOS 14.4 is signed and if sep and BB of 14.5 is same no need to move only for poeple can use checkra1n is good
how do I install these futurerestore dependencies?
terminal
Someone in here was successful on a13?
brah
I‘m on 14.1 XS Max and have blobs. Can I future restore even I’m not jailbroken?
no
wouldnt be able to change nonce
you can once the JB comes out if SEP is still compatible by then
or if coolstar releases that noncesetter 
i mean it can’t really be months
if sep not compatible just update to 14.5 and wait
I heard 14.5 baseband might be incompatible on the 12 series at least but if it's just that then who cares, nobody can futurerestore on A14 right now anyway unless they managed to keep their nonce frozen
his blobs still wouldnt be valid
hes on A12+ nonce entanglement
oh if they didn't save those with an apnonce/generator pair from an earlier jailbreak then yes they wouldn't be valid
99% the nonce has changed since then
if you don't use the nonce freeze method it changes every reboot
my A12+ blobs are somehow valid even though they have a gen in them
and even then it can change randomly when iTunes does a sync or the device checks for updates
so, how do i know for sure that i can use my blobs or not
because ive never set a custom generator
which from what i can tell was needed
valid
A tool to save your SHSH2 blobs online without using the CLI.
also valid
pretty sure he did that, depends on when you saved them
Added with the poll results. @TheOdysseyJB 1.2.0-1.2.2 users should use the 2.0.2 update.
"fix" will be removed once this is fixed in the jb. https://t.co/oIp7E1jbAc
@sharp tangle what device do you have
11
system info
did you specify your ApNonce
that should be fine
System Info sets a random apnonce/generator if it can't find an existing pair from shsh.host
although system info puts a gen on A12+ blobs which is irregular
ive never specified anything and always pressed on use existing
when it sets the gen or whatever the fuck that is
yeah that works
So, can i try to fr ?
yeah doesn't matter either way, but I prefer to use existing to not have many different generators for no reason
not worth it rn
I want to do it
it can be helpful in case you bootloop and the nonce is still set
and yes, i am willing to loose my jb
if you have blobs with like 10 different generators and the wrong one is set rn... then L
in the bootloop case I'm talking about
wanna live for a moment without one
unless A11-
i hope you realize it still isnt worth it to FR
the errors that could pop out
still potentials
what errors
worst case you have to restore to 14.4 and wait for modernpwner to drop the second exploit 
future restore is hacky
You mean downgrade with FR right now. If you are on 14.4 you can test if SEP 14.5 beta is compatible with "one time blob".
sure but I meant do anything useful
Yeah.
including upgrading to another unsigned version
But good to know if SEP 14.5 is compatible for those devices.
The time shows if maybe apple make different changes for SEP and devices. With 14.4, its the first time that SEP is not compatible for all devices and same iOS versions.
very contradictory
how to compile futurerestore for a13? used the scirpt but extchanged the link for the a13/a14 branch but gives out an error
What error
I don't have watch only one video completely from GeoSn0w. For me it is only clickbait and overdone. If you use your brain and read a little bit in some places you have all infos you need and know what you have to do or not. His videos are only for people they don't know what they doing and eta kids. No offence against GeoSn0w, each as he likes.
Pretty sure we all know that by now
But hey hes a businessman
does what he needs to for the views
Is there any guide on how to use future restore for A12+ devices
not worth it rn but pins are there
Has there been any successful restores for iPhone 11pro? I have all my ducks in a row , but nervous to pull the trigger cause I have not heard of any successful restores
dont, its not worth it if you have a stable jailbreak rn
That’s pretty much the reason why I haven’t , I updated my xs max test device a while ago , but wasn’t sure if I should pull the trigger on my 11pro thanks for the advice 👍
@celest basalt Hey. Mind helping me with FR and guide me on what i need to do and download ?
sure, what device and target iOS version?
Im about to risk this, but iPhone 11 and 14.3 ( current 13.3.1 )
If it works can you please let me know.
Sure
well, the A13/A14 macOS build was removed but you could still compile manually, bc apparently it may work and people were just using the wrng build
14.4 SEP/BB:
iPhone 11(n104ap) - 18D52
SEPOS: Firmware/all_flash/sep-firmware.n104.RELEASE.im4p
BBFW: Firmware/ICE19-2.03.04.Release.bbfw
IPSW download link (http://updates-http.cdn-apple.com/2021WinterFCS/fullrestores/001-98427/9C42F04F-C1B3-41C5-8E0D-0EDCB5087BB5/iPhone11,8,iPhone12,1_14.4_18D52_Restore.ipsw)
Aaand looks like this is where issues are going to start rising. Im on linux. Ubuntu 20.04 to be exact
Dont have a mac
Is there a script or anything I can use to install all the libs and dependencies need for fr?
you can compile or Linux

While the ipsws are downloading, how do i do that ?
oh where did the compile script go
my gpu driver fucked up on ubuntu and this scaling is just 
#728061044098072596 message
script for linux
Tells me no access lmao
same

Just add pkg-config in the end of the apt install line, in case you have fresh Ubuntu
futurerestore compile script for Ubuntu 20.04 and 20.10: https://lukezgd.github.io/scripts/futurerestore_compile.sh
- Edited 2021-02-13 - Still works for latest futurerestore 189! (you have to select if your target device is A13/A14 or not)
Compiling:
- Download this script
- Open Terminal
cdto the folder where the script is located (example:cd ~/Downloads)- Run:
chmod +x futurerestore_compile.sh - Run:
./futurerestore_compile.sh
- Launching futurerestore after compiling:
sudo futurerestore <arguments>
Seems pkg-config already there
👍
ok, deps installed, now cloning
i think
oh god
the quality of that picture
or its just because the scaling on my pc is shit rn
@celest basalt the ipsws are about done. What do i do after they've downloaded ?
you need to extract the files mentioned from the 14.4 one
the 14.3 one doesn't need to be extracted, you'll just use it as an argument
yeah the ipsw is basically just a zip afaik
Put them in the restore folder
You also need the BuildManifest.plist file
Its in the root of the ipsw
oh so are you just gonna do it from the desktop then
thats fine
make sure you get your blob on the desktop too
not a problem
thats everything
Looks like im ready to die then
maybe
GL
sudo futurerestore -t 14.3.shsh2 -s sep.imp4 -b BB.bbfw -m BuildManifest.plist -p BuildManifest.plist -d 14.3.ipsw
let me hop on windows real quick, do a final backup
that is your command if i didnt fuck anything up
make sure to restore rootfs first then
kk
aaand booting back into ubuntu
failed to read sep @zealous bridge
oh, its im4p
not imp4
brrrr
oof
error?
unable to place device into recovery from normal
run again
its in recovery rn tho
dont put it out of recovery
oh
wait, dont i need to set the generator ?
havent u done that already
uh, no
.

here
Well, yeah, i did restore rootfs to get rid of my tweaks so i can backup
ur genrator on iphone must be same with blobs??
yes
yeah
ok ty
Looks like im goin out of restore then, right ?
minor distractions
restore or recovery?
if its in recovery just type “sudo futurerestore ––exit-recovery”
no, just a pc with a cable
Lol
error code -2
uh
“irecovery -n”
if not youre gonna have to boot back into windows and download 3rd party software
yes
uh i forget where the set generator button was
i just pull the generator out of my .shsh2 file, right ?
because i didnt set any custom ones
If its there yeah
it is
Make sure to get into recovery mode first try or you have to set generator again (on my device at least)
I dont need to jb before putting it in, right ?
well thats just complicating it
Prob 1, 4, 2
open odyssey, set generator, jb
lol
yes
the long one ?
ok we in restore rn
nothing in terminal yet
except for debug: waiting for device disconnect or whatever
extracting fs from ipsw
ok good
I think Odyssey's nonce setter is still broken isn't it
wouldnt there be a device nonce doesnt match error
oh yeah
apple logo with that loading bar
what it say in terminal?
Above that
Fdr?
Send us the last ten lines or so
FDR 0x56290b6722e0 terminating...
idevice_event_cb: device 001404602609802e (udid: 00008030-001404602609802E) disconnected
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=189:
commit sha =e38826391ff467427d2f14286141418a7cadb758:
Done: restoring failed!```
whats that lol
its whats causing everyones restore to fail
Should be. i chose A13 branch when that building script prompted me
dont think you should
run that irecovery command ?
yeah run irecov again
I got the same results, but did it using the same script on Ubuntu just like you. No idea how to compile without script so haven’t tried mac
no
Well, atleast im not on a one way trip to 14.4
lol
yh lol
What is “CI” that cryptic was talking about last night?
everyone knew that
Yeah, as i said, atleast im not on a one way trip to 14.4
Remember capt or Crypt said yesterday v192 worked, not sure.
hi, im on Xs 13.5, do i need to update to 14.3 now or i can update when 14.5 out (sep/bb)
@whole yoke Up to you really, but https://reddit.com/r/jailbreak/comments/lmcrct/tip_futurerestoring_to_143_now_is_a_dumb_idea/
290 votes and 113 comments so far on Reddit
If you dont mind loosing a jailbreak and waiting possibly months for a new one, sure
ok thx
does A13 work on ubuntu
Nope @green onyx
oof
tested today, same fuckign fdr error
You can scroll up a bit if u want
keep me updated tho if i works
everythings gonna be there
v192 seems to work, but i dont really know where i gotta search for that
ah
to 189 iirc
if you know the commit ID it's probably still up on github but idk
Version: 3786d4cd230b93f4b7ade7d0fdebd56b48fbf7a6 - 189
img4tool version: 0.197-aca6cf005c94caf135023263cbb5c61a0081804f
libipatcher version: 0.82-0b2f79ff0917ef9b8a92475d93d9466b23fc2322
Odysseus for 32-bit support: yes
Odysseus for 64-bit support: yes
[INFO] 64-bit device detected
futurerestore init done
libc++abi.dylib: terminating with uncaught exception of type tihmstar::exception: failed to load APTicket at blob.shsh2
zsh: abort ./futurerestore -t blob.shsh2 -s sep.im4p -m BuildManifest.plist -b -p -d
help please
<@&355177530061357057>
is it even in the blob 
and valid
wait no apticket in blob
is the blob wrong ?
Bruh
@agile veldt
Use noap

Whom elected you as genius?!

Just like the time capt had no idea what stashing was

It works, I just forgot to put the .shsh2 extension to the blob.

FDR 0x7fe4ff804920 timeout waiting for command
FDR 0x7fe4ff804920 waiting for message...
FDR 0x7fe4ff804920 timeout waiting for command
FDR 0x7fe4ff804920 waiting for message...
No data to read (timeout)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Unmounting filesystems (29)
Got status message
Status: Restore Finished
FDR 0x7fe4ff804920 terminating...
Cleaning up...
Done: restoring succeeded!
what device
xs

6s
oh nvm
i will wait for my xs
Just upgraded an iphone XS Max from iOS 13.5 to 14.3. Everything appeared to go fine, the device restored from a backup. Did the usual facetime setup and now im stuck on a black screen with 'Updating iCloud settings...'
Am I screwed or is there a way to fix it?
reboot
idk
I tried a force reboot
that doesn’t work?
no
?
ew
If you are running into other problems with Futurerestore like reboot loop, screen freeze, or black screen, you can recover iOS system using ReiBoot to fix these problems without data loss. This professional iOS repair tool can fix all iOS problems related with downgrade, upgrade, or restore.
is this an ad
no ad just helping the required
you seem to be advertising a shitty product
Doesnt that only install the latest version of ios which is what im trying to avoid
its stuck on this
just let it finish then
i've tried turning on and off, force reboot and skipping but I always end up stuck on that screen.
Its been on it for hours
just don't restore the backup then
its already restored the backup. how do I now goto new setup?
idk
disable wifi
also, i have a feeling his tryna bypass activation lock
not trying to bypass anything I have had the phone from new
Is it safe to assume this SEP compatibility GitHub is wrong?
it's not wrong, you cannot downgrade below 14.0 on any device except Apple TV
Ohhh. Ok. That’s why I was getting FDR error on my iPod. Thanks!
then why does it say if sep is compatible, you can downgrade with blobs at the top. should say about bb too
well, something is up there because even wifi iPads (no baseband) can't downgrade to 13.x atm afaik
yeah
@wispy ferry does your device have a lot of photos, videos, documents etc on the icloud?
deleted all photos before restore and about 100gb of data/apps
oh sorry have 5gb limit that is full on icloud
subscribe to an Apple One trial
100gb geez..., i was gona say that's why it's taking so long, another user had the same problem with 25gb icloud data and it took 6 hours...

no icloud data shold be about 5gb so shouldnt take that long
Just found your reddit thread... still trying to find a solution to your problem. 🤞
Many Thanks for the help
No worries, only doing what i enjoy best. ⛑️
the only solution I keep coming across is to update to latest version... im really hoping it doesnt come to that. 😢
Not sure if its worth trying Erase All Content in Imazing, but not sure how that would work with an eSim
Just remember iOS 14.5 may have an exploit available as soon as apple patch it.
🤞
Erase all content and settings with iOS does not upgrade firmware so Imazing could possibly work however i am uncertain of this...
Just found this on a thread, Stuck iOS after futurerestore > Solved by using iMazing to Bypass Setup Assistant! ?
Thanks but I have Tried that. Says Exiting the Setup Assistant is unfortunately not possible anymore on iOS 14 and above.
OMG that's so unlucky as it may have been possible. 
Leave your device over night letting it do its thing, and with any luck it may get resolved... 🤞
It is very unfortunate that I have got to go now, sorry i couldn't be of much help in resolving your problem. 😴
Thanks for your help. 👍
No worries, Leave your iOS device near your router overnight so you do not experience a bad wifi connection.
Does the 14.4 SEP work if I restore an iPhone X (10,6) with 14.2 blobs?
not for the X, no
if you have 14.3 blobs you can use those instead
Do devs agree a13 doesn’t work, or they say it works?
I keep getting this error when restoring 14.2 to my iPhone 7
Updating baseband (19)
About to send BasebandData...
sending request without baseband nonce
Sending Baseband TSS request...
Request URL set to https://gs.apple.com/TSS/controller?action=2
Sending TSS request attempt 1... response successfully received
Received Baseband SHSH blobs
Sending BasebandData now...
Done sending BasebandData
ERROR: device didn't accept BasebandData
ERROR: Unable to successfully restore device
Updating baseband (19)
Cleaning up...
Done: restoring succeeded!```
Oop! unable and done 😆😆
Im stuck in a recovery loop
RIP, i dont know how to help you
Anyone that can?
What is happen?
14.2 should work but if not just go to 14.3 as the BB works there for sure
use some 3rd party app to get out of it
you can try the command irecovery -n and if it doesn’t work then yeah the restore failed
hi all, i read futurestore doc, saying o IF YOU ARE PLANNING TO RESTORE YOUR DEVICE USING A BACKUP, please restore rootfs(or ‘restore system’) from your jailbreak app before backing up. If you don’t, you will need to activate your device by using ideviceactivation. See cryptic’s message in r/jb discord #common-issues for more info
what is ideviceactivation> where i can download this?
OK, I manage to install ideviceactivation and run
osboxes@osboxes:/usr/lib/x86_64-linux-gnu$ ideviceactivation activate
Successfully activated device.
osboxes@osboxes:/usr/lib/x86_64-linux-gnu$ ideviceactivation state
ActivationState: Unactivated
what's wrong?
Nevermind I used the 14.4 bbfw instead of the 14.2 bbfw and it worked. thx
Hi all again
I try futurestore now, try to restore iOS12.4 on my iphone 5s
i get blob from noapnonce folder
i get this error below, anybody can help what i should do next?
Got ApNonce from device: ea 9f 23 85 3f 72 f5 33 de 31 66 86 85 34 a6 43 a3 00 5c f8
[Error] Device ApNonce doesn't match APTicket nonce
Just compiled a13 branch, not master, on Mac. Same fdr issue as with Ubuntu. Was worth a shot though
Also tried 192 static from cryptic twitter same result
iphone 11 ios 13.6?
Not yet, i still wait Windows version
you didn't set your generator correcty
the generator you need to set should be in the .shsh2 file I think, not too familiar with A11-
Cant wait for them to put out a new commit, so i can try taking a one way trip to 14.4 again
ok
Hi guys, can someone help me pls?
Do you know if I can can downgrade an iPhone 7 from iOS 14.4 to 14.2? I ve saved Blobs from 14.2, thank you
And how can I use Futurestore? It s my first time sorry
you should be able to
SEP is compatible
use the 14.4 bbfw, sep, and buildmanifest, then just use the 14.2 ipsw
make sure you use the 14.2 blob tho
and for everyone: https://docs.google.com/document/d/1WHuwuvnkcEUCwaDuck2dy-MR7q4em38uL4_4Utx2QZ8/edit?usp=sharing
A9 and newer can’t restore to iOS 12 or lowerLowest version you can restore to on iOS 13-compatible devices is 13.5 Guide last updated: Aug 20 2020 Part 1: General Notes (Please read all of these!!!) READ THE WHOLE GUIDE BEFORE BEGINNING READ PAGE ONE IF YOU DIDNT ALREADY if you have any questio...
still works to this day
fkin balls of steel
not yet
Lean and smokin both failed with A13 189
when did they fail
because 2 days ago it was fixed
I have an iPhone 8 and blobs only for iOS 14.2, what will happen if I try to future restore to 14.2?
You can’t
Only 14.3 RC and newer
Check pinned messages
succesfully restored an ipad mini 4 (A8X) from 14.4 to 14.4 on macos
windows build isn't working
You could use succession instead of futurerestoring from same iOS to the same one
i know
but i was testing oppa's windows futurerestore
which didnt worked
so i did it on macos because why not
So no futurerestore to iOS 14.x working on Windows at all?
i mean
it worked on oppa's A9
so it isn't completely broken
oh and I initially tried 14.4 to 14.0
then to 14.4
none worked on windows
and then 14.4 to 14.4 worked first try on macos
I want to go from 13.5.1 SE 2020 to 14.3 when jailbreak released but I dont have mac. Will it be possible?
Could just boot from USB be enough linux to futurerestore?
And which version is working for linux exactly?
So can I restore to 14.3 A13 with linux or not?
Anything 2020 is 
If I'm going to go from 13.5 to 14.2 would it be easier to upgrade to 14.4 first, then downgrade to 14.2. I have blobs for 14.2
no need to do that, you can do it directly from 13.5
can I use --latest-sep --latest-baseband when going from 13.5 to 14.2, or do I need to specify them
latest should be fine but I think it's recommended to do it manually just in case
also 14.2 will only work on A10 and lower according to the pins
@celest basalt is it possible to go with live boot linux with a13 to 14.3?
Nobody can give me answer
also, if it doesn't work using --latest-sep --latest-baseband are there any risks if it fails?
I thought it's clear enough that A13 futurerestore is broken right now, you could try reading what we say and results of people testing it instead of acting entitled
Someone told me it works on linux
you're in no rush to upgrade right now, if 14.5 SEP/BB turns out to be incompatible when it releases (which is still at least 2 or more weeks away) then you'll have a week notice before 14.4 is unsigned
it works for A12 or lower, but the majority of people at least haven't had success with A13
I am not trying to act entitled
I just did not receive an competent answer
When majority of people havent had success then someone has
sorry I'm just dealing with other shit right now but I thought the pinned messages are also pretty clear... if it says "A13 does not work" there is no need to ask "does A13 work on Linux"
even if capt takes a few hours to update the pins we aren't in a rush yet as I said
Ok then
It is broken, thank you
Someone told me linux is working so I dont know why is that person telling me false information
My plan is to get capt demoted
That's what joe mama said before she sat down to watch me
@celest basalt apparently adam said the issue with fr on a13 was dumb people using the wrong branch
but ig not
Alright, I just wanna double check here and make sure everything is good.
I am going from 13.5 to 14.2 on an iPhone 7
I have blobs and I set the apnonce with odyssey to 0x1111111111111111 which is what showed in shsh.host as the generator used when saving the blobs.
I am going to try using --latest-sep --latest-baseband
Does this look good, or am I doing something wrong.
mhm
tru
just give it a try
aight, what are the risks of it failing
having to restore to iOS 14.4
which isnt a real problem since you can try to downgrade again
only if you have checkra1n to jailbreak and set the nonce
mm tru
I would have stayed, but developing tweaks on 13 while everyone is on 14 is oof
nope, two people confirmed they were using the a13/a14 branch, I saw the commit number
and it still didn't work
yup
damn
me is an example
no
yup
i assume u just recovery looped
.
and used some tool to leave it
ah fair enough
good luck

i just use 3[REDACTED] cuz im lazy
does it even do that ?

if im thinking about the correct thing
3[redacted] is bruh
or just futurerestore --exit-recovery
Until you get my issue where the device doesn't accept the baseband data and you have to reflash with a different bbfw
Green screen means it set the nonce
Little do ppl know that --latest-baseband works
lmao
ayyy it worked
ppl are like scared to use it

poggg
I'd be more scared with experimenting on different file names and risking a bootloop than the automated latest sep/bb arg
@vivid nova i was thinking the exact same thing
but if you get smth like system info then you know your device's board config
so then it's as simple as navigating through a signed ipsw and get the correct sep and buildmanifest
but yes, --latest-sep and --latest-baseband is much more simple and works
Hmm, it never gave me a green screen, but went past it
Tho it still errored with FDR afterwards
Rip nonce setting
eh fuck it, wont try again, gonna wait till the A13 branch is fixed
dont wanna risk taking a one way trip to 14.4 again
@sharp tangle truth be told: as long as you have blobs.. You've got lots of time. 14.5 sep will be compat too
I never got a green screen when I restored from 13.3 to 13.5 on my XR
yeah, i know. I just want to go stock for a while, which will be till odyssey14 comes out
I know but when I was on ios 13 trying to downgrade when it wasnt signed I used the latest sep and bb args but it messed the restore up bootlooping me, making me have to go to ios 14 with my iphone 7 FROM 13 and never using it again because of that.
pretty much as long as I am careful and triple check my blobs sep and bb i am fine
i know but I lost my ability to jb on 13.5 with chimera
now I have to use checkra1n and hope my phone doesnt die when out
ofc you cant brick an iphone - thats what recovery mode is for
isnt it a separate read only chip?
that's DFU
yeah pretty much impossible without hardware damage afaik
thats the only thing I like about iphones
You can format the iboot partition
Well shit
Don't say that too many times someone gonna make a bad tweak that bricks your shit
youd need an exploit or iboot open
@green onyx sorry it just sounded like it to me, I don’t control the repo, we are still investigating why a14 works but a13 doesn’t
We need a13 testers on 14.4
hm, the people ik are either on 13.5 or 13.7
and uh ye
its fine
dw about it
Do I need to download the iOS 14.4 ipsw and get the SEP and baseband from it?
If I want to restore to 14.3RC, A12
just use --latest-sep
and latest-baseband commands
i dont remember them of by heart
--latest-baseband
--latest-sep
those commands
^
Correct no need to download multiple ipsws
––latest–* will automatically download the correct latest ipsw baseband and sep and manifest
Why some people gets the error with the Baseband??
We try with a friend on a iPhone 7Plus the restore to 14.4 all was fine but the baseband Update not work
Even with idevicerestore we get allways a Bb error
I can make a restore only from finder
and after the restore i can‘t activate the phone 😖
for those having issues with baseband update or activation, changing DNS servers might work (to 8.8.8.8 or 1.1.1.1 for example)
that worked on my iPad 3 Cellular back then
btw the latest idevicerestore commit breaks a11/a12
it could break lower too I guess?
I close terminal after , is there a option to see all the log from the last session.
which one do I use here? 
The one which coresponds to your board config
how do I find out which board config I have?
you are 100% sure you have 11,8?
yea
n841ap
please just use --latest-baseband and --latest-sep
you don't need 14.4 ipsw
bruh u a wizard or some
no I just know where all the documentation is
Oh i didn't know this was even an option. I was watching GeoSn0w's tutorial
nice
that channel is not allowed
he feeds misinformation to unaware begginners for money
he spread a lot of bad practices
and bad information
big oof
thanks for letting me know
dammit I waited an hour for the 14.4 ipsw to be downloaded
i see
all you need is the ipsw and blob for the version you are going to
and you can only go to 14.2-14.5 afaik
mhmm I got everything then. Thanks a lot
Does V189 work on Linux ?
depends
On ء?
device
A9
then yes, compile from source using the script
it’s compiled for mac
not for linux
Where can i get the file that needed to be compiled?
Any direct link for downloading plz?
theres no linux direct
What file should I download from the link above ?
do you have a mac
No, only linux
then you have to compile it yourself
Got it, but what file should I download?
In order to compile
just follow that
Okay, thanks
did adam stop working on FR
no he just ded today lol
Im working on ci caching
with 23 aaron
but I can no longer put in many hours
lol
have another job to do
is that sleep?
14.2 is not possible for him. he has an a12. sep is incompatible
Guys, should i use 2.0 or 3.0 USB Port to FR on live usb Linux?
3.0
Thanks
@storm apex pretty much all done now, builds in 4 minutes due to caching
latest sep did cause issues for me tho. Fr was stuck on downloading it so i specified myself
probably an issue at the time with the guy hosting the sep and bb
wait
who even hosts the sep and bb files?
Iam on 13.5 A13
Is there any approved futurerestore for my case ?!
not yet
Okay thanks
Check pinned messsages
futurerestore --exit-recovery or irecovery -n
Never mind
For MacOS users this works perfectly
For Windows users, you can use this https://github.com/s0uthwest/futurerestore/releases
All above for IOS 12
- All IOS 12x are compatible with latest IOS 12 SEP and Baseband
Just in case someone needs it ^_^
Has anyone tested that futurerestore v189 can run properly on a virtual machine macOS?
@brittle olive that is highly outdated don’t use that
procrastination is great
What do you mean by that?
it's old and there are better forks
Tested,works fine.
Does the latest futurerestore version work on Windows?
Old but works perfectly
hardly
they said iOS 12

I have two jobs, school, a dog and somehow procrastinate still
... And no partner
no
why windows
opa is working on windows
hi
hi
if only we had southwest
😦
although I'm not even sure if the issues in img4tool are exclusive to windows, it may just be a memory corruption or something that only happens to trigger a crash on windows
how the hell do you even have enough time to compile it for windows
honestly I don't lol
lol
anyways I got build script laying around that goes from a clean msys2 installation all the way to a fully static exe, will be released soon
nice
@vocal sundial @dull swallow yes me an opa can static compile for each update but what I did for mac can also be done for windows and linux, github actions ci static builds
there are also a few build variations
such as -DDEBUG for each dep and a13/a14 branch
has the issue for A13 been worked out yet
yeah well I'm going to publish my script soon, do with it what you want lol
or do you need testers
there was a lot of extra work needed to just get it working on windows
the only real problem windows ever caused was getting limd to compile for windows
the rest I compiled fine
curl, openssl, libzip etc
limd itself compiled for me first try lol
xpwn and other stuff was more complicated, and there is still an irecovery problem with the latest apple device drivers :/
and all the fixes posted there also don't fully work
yeah lol





