#futurerestore-help
1 messages · Page 29 of 1
@rustic blaze its no longer possible
that too
I already mentioned it’s for IOS 12
yes
by you saying it works is very misleading
because literally no one is restoring to 12 anymore
a8 as well
yes
no
The mini 4 is A8 by the way
Anyone else get this message when doing make install on mac osx?
➜ futurerestore git:(a13/a14) make install
Making install in futurerestore
make[1]: *** No rule to make target ../external/idevicerestore/src/libidevicerestore.la', needed by futurerestore'. Stop.
make: *** [install-recursive] Error 1
how did you get the repo in the first place
git clone
when cloning futurerestore og libidevicerestoe?
Same error after cloning with --recursive
you aren't supposed to clone idevicerestore
First install OpenSSL then the script and then the idevicerestore part
theres no idevicerestore part at all
Without it Fr would fail
thats not what we are talking about tho
you don't need to touch idevicerestore
its a part of futurerestore
theres no need to compile it
it compiles when you compile futurerestore
he just didn't clone the repo recursive
@solid sparrow try a compiled one
@rustic blaze there is no compiled one for A13/A14.
Does the a13/14 futurerestore on marijuanARM’s repo not working? Didn’t he said that he fixed it?
@valid adder still didn't work. Deleted all created a new folder, cloned with recursive and tried again. Works now. Thanks mate!!!
Yw
Can i use a self compiled version of futurerestore for A13 now?
yeah, wanted to know the same thing
Anyone knows what causes this: Sending NORData now...
Done sending NORData
ERROR: Unable to receive message from FDR 0x7f89906f28c0 (-2). 0/2 bytes
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!
just a13 things
Any idea on how to fix?
you cant
so a13 is a no-no right now? xD
yup
well good thing i asked
Stupid that I didn't 😄
i was just compiling the latest version and wanted to give it a go
well that would be great, bc i readon adams twitter, that he pushed a13 fixes to github
Sad life...
Alright. Then i will not risk it xD
Will camp Adams' twitter and see what happens
Nej, lad lige være med det 😉
Tak, det gør jeg ikke
this might be dumb but how do i use the compiled futurerestore in cmd? like is it
futurerestore -u -t C:\whatever --latest-sep --latest-baseband iPSW C:\whatever
don't use -u
is everything else right? can i use latest sep and baseband on iphone xs
going from 14.2 to 14.3
so if i were to backup with itunes right now, when i restore to 14.3 can i use that backup? just making sure
you cannot go from 14.2 to 14.3 right now because you can't set the generator
but if it were possible then restoring a backup to a newer version would work fine, yes
even if my blobs still say theyre valid?
i saved blobs when i was jb
@celest basalt
yes, you need blobs AND the ability to set the generator
ok, thank you
What device?
And what iOS version are you on and going to
Giving fdr error still for now
yeah
What device and what iOS version are you going from and going to?
iPhone 11 pro from 13.5 to 14.3
Ya both sit tight, if we need a tester they’ll get in touch with you. They’ve been using my 11Pm to test rn
I've tried compiling 187, 198 and 189
We really need a A13 that’s on 14.4
Had any luck with yours?
No
But is it possible to go from 14.4 to 13.5?
If we get a a13 that’s on 14.4 we can see if the fdr is sep issue or fr issue
No
Just 14.4 to 14.4
Okay, else I would upgrade instantly 😄
Don’t yet
It's my primary phone, so it's just a brick for now
I can't use it 😛
Why
Stuck on recovery
Exit recovery
Your still on the same version
Nothing happened it kicked you into recovery again
what=Could not connect to device in recovery mode.
Use imazing or reiboot
Is it that simple?
If you failed with fdr
I did
uturerestore --exit-recovery
Version: e38826391ff467427d2f14286141418a7cadb758 - 189
img4tool version: 0.197-aca6cf005c94caf135023263cbb5c61a0081804f
Odysseus support: no
Exiting to recovery mode
INFO: device serial number is FK1ZXBG0N70X
[INFO] 64-bit device detected
futurerestore init done
futurerestore: failed with exception:
[exception]:
what=Could not connect to device in recovery mode.
code=10813457
line=165
file=futurerestore.cpp
commit count=189:
commit sha =e38826391ff467427d2f14286141418a7cadb758:
you could try the hardware reset
fr might just be broken for recovery actions
use reiboot
Thanks mate! I already thought that it would have overwritten something
Nah
I futurerestored to 14.3 and i am getting the storage almost full bug. Can this be fixed without erase all content and settings?
When fdr errors the bar on your phone doesn’t fill up, good way to tell if it’s to late to save it

If i can find a i11 pro max on 14.4. What do you need from it then?
The writing nand part got me thinking there was no way back
You have a 11Pm on14.4?
And a Mac?
Or do you mean finding someone
@solid sparrow
@solid sparrow
I mean if I find someone.
just finding “someone” won’t work
you need to find someone who has jailbroken before and saved blobs for ios 14.3 when they were on ios 13 or whatever version their previous jailbreak was on
unless you do that same version restore thing which was done before but its still broken
not necessarily
if u save blobs with a 11 on 14.4
u can use the blobs immediately to test fr
really useful to test fr
its not that you can
its that you must
because next reboot blobs will be invalid because nonce changed
this is why you should freeze nonce
U cannot do it w/ a13, and maybe its why a13 is still a no go - no testers
Only A13 is worth to discuss afaik
All this time I'm thinking nonce changes when you restore
Im specifically talking about non jailbreak restoring
How i can resign img4tool for Catalina ?
zsh: killed ./img4tool
Also 😦
Even futurerestore245 killed
Compiled versions
I remember there was a option to resign it but i forgot which website was
If i can help iam a13 13.5 u0
Saved all my blobs
Have 0% experience about these staff ( futurerestore )
But i want to test
Iam tired of 13.5 and want to go to ios 14 and be jailbroken
Soo what can i do
@storm apex @dull swallow at last, I've finally done the impossible
I can downgrade ios 13 to iphone 6s+ bypass no sim card ?
I can downgrade ios 13 no baseband to iphone 6s plus ?
I use 6s plus ios 14.4. Can i downgrade ios 13? Not baseband.
could you still find someone or nah?
Or if anyone else has a A13 on iOS 14.4 ONLY
(or 14.5b)
If something went wrong you’d have to go to 14.4 and lose a chance to jailbreak
Wouldn’t be the end of the world for me
If a restore failed you don’t care if your on 14.4 instead of 14.3? Do you have a Mac?
Add me as friend
Sent
@celest basalt remember to do debug log
what
what was the impossible
@dull swallow diagnosed the cause of a13
OOOO
poggers
is it idevicerestore
nvm
judging by what you are changing in VSC
recovery.c
@dull swallow it is
lol
and the same thing that broke a13 broke a11 and a12 as well
idevicerestore causes like 90% of the errors
a14 worked tho
1
pog
Windows version work i try on my 6
who knows
probably will work
might get some compile errors
i haven’t seen much feedback about opa’s future restore
okay
rip @celest basalt device
did it bootloop
who wants to test now lol
that RTKit should fix right
yes
will future restore get the recovery mode fix
so you don’t have to use a third party app
to enter recov
a13 more important
they're stumped again
stumped
yes

we are diagnosing rose
has futurerestore ever worked for a13 @storm apex
like for iOS 13
@dull swallow /cc
what about -> 13.3
i have never tried FR on A13
wasn’t necessary since the 0day thing happened
but that’s weird asf since A14 has rose too
although A14 thing was signed
A14 rosed?
A14 and A13 has new firmware called rose
it’s for the nearby airdrop shit
i think
thats a12
true
i thought it was for the new compass thing in airdrop
where you can put it up to another A13 device
or something
I fixed the FDR issue that affects a11-a13. However a13 fatally fails restore so theres still more work to be done. a11 and a12 succeed restore normally. If anyway has a13 on 14.4 or 14.5 with mac or linux, we could use as many testers as possible. https://t.co/PM8ei2dpVc https://t.co/9bP2gUdGj8
i’d be a last resort tester if you need me at all
i’m on 13.5 so if you don’t get any testers i’ll test
@valid adder r u releasing a new build
so fatally means it can’t exit recov right?
forcing you to update to 14.4
@valid adder
lol fatally fails
why does A13 have to be a pain
why did i buy A13
A13 restores have been done before though and succeeded right?
no
Will this build also work on windows
For what we need rn, no
Linux or Mac
can relate
and why did i not update when i had the chance
I feel
Because cryptic said he is working on a build for windows
Are you too lazy to run 3 commands from a live booted linux usb ?
Cryptic won’t build a windows build. Opa will
opa is a cool person
i’m going to refer to cryptic adam and opa as the future restore team
tihmstar be like
big bren
So tihmstar gave up on working on futurerestore?
Why:
APTICKET: AP 15400076bc4c35a7c8caefdcae5bda69c140a11bce870548f0862aac28c194cc BOOT 0x1111111111111111 | DEVICE: BOOT 0x1111111111111111; does NOT restore - AP error
APTICKET: same data | DEVICE: BOOT 0xbd34a880be0b53f3 restores
does that mean the AP data is necessary but boot isn't
I used this on an A10
did u set ur generator
Yeah
tf
I like tried to restore with gen 16^1 and it didn't
with the AP from bd34a880be0b53f3
SO look
I restored with DIFFERENT GENERATORS
Boot generators and not AP gens
Restoring process 1:
Using blob with AP 15400076bc4c35a7c8caefdcae5bda69c140a11bce870548f0862aac28c194cc from boot bd34a880be0b53f3(NOT THE BLOB GENERATOR); **generator is **1111111111111111; device boot is 1111111111111111:
RESTORING FAILS, AP Nonce error
Restoring process 2:
Using the same blob from RP1; device boot is bd34a880be0b53f3: success
@green onyx hope you can read the above mess
r u using the correct blobs
go ahead and verify them first
on like shsh.host or smthn
nice ecid
if you check pins you can see
it's useless anyways dude
I'm trying to practice
what device is this
iphone9,2
uh
told you an A10
Yeah I just saved a fresh blob
lmao wtf
idfk then
@celest basalt save it using blobsaver fresh
use read from device for generator
and without setting generator
use it to fr
what data
?
ye listen pls
The AP one only works with matching:
device boot
and
ticket AP
i can jb dude
whatever
how do i read the gen from device
do i not mention the ticket argument
whatever i just got it
@vocal sundial I saw your comment, the fdr error -2 specifically means UNKNOWN error meaning sep has paniced. This is caused by running the rsepfirmware command on devices other than a14 also you could be restoring to an incompatible sep version
@valid adder hm the two users reporting this definitely were using the correct sep tho (at least as far as I was able to tell), what makes it weird tho is that other users succeeded restoring A10 with the same build and only one user had this problem :/
what version were they going to tho
Ah yeah I remember now, the guy that had this issue on A10 was trying to go to 14.2
so that was probably the issue there
but restoring A10 to 14.2 should work, shouldn't it? my A10 tester only restored to 14.3
the a13/a14 branch will break a11-a13
works on a14
may or may not also break below a11
yeah I know, I'm using the <=A12 branch
and users have had success on A9, A10, A11 but the one guy trying it out on A12 got an FDR error but it was so early that he still was able to get out of recovery and everything was fine
14.0-14.3 works on a10 and below

I keep running into this issue when restoring 14.3 to my iPhone 7.
It would start the process but then the program would close when it gets to this part. ( If anyone can help, I Thank you in advance)
Device already in recovery mode
Found device in Recovery mode
Identified device as d10ap, iPhone9,1
Extracting BuildManifest from iPSW
Product version: 14.3
Product build: 18C66 Major: 18
Device supports Image4: true
Got ApNonce from device: 5a e8 52 5b c3 84 98 76 2d 43 a9 f4 e8 c1 ba 26 23 ff 6b f9 01 97 7f 01 6f 57 b7 e5 9a 67 aa 66```
that doesn’t look like an error
????
that should happen
theres no issue in this text lol
windows is notorious for not showing crashes it just exits basically
rip
@ebon crown I am the A10 tester for opa334. The build from his github works with the -n flag. But be really sure you have all the right files.
Be patient, he is fixing a lot of things and he sends me many versions. He already work on it.
Thank you for informing me, I’ll wait for when a new release rolls out. 
A13 safe to restore to 14.3?
I don't see any new fixes for it, but afaik it won't bootloop if it fails
So l cant restore atm?
it will fatally fail
huh? I thought the a13/a14 branch won't
there is so much conflicting information about futurerestore at this point
at this point i'd say they don't have a clue what they're doing
broken atm
rip
they do
xd
they just need testers
they know what they are doing
just future restore is so hacky
there is a bounty for a13?
no
Had success on windows future restore
check sileo announcements with a link
or dont
Why is A13 so ass
bro thats ancient
A11 ftw
Some here with iphone 8 gsm can tell me the baseband number please
On 14.3
I want to prepar for update as soon when Jailbreak is drope
Hey, Question. I have an iPhone X with a blob for 13.5, does that mean i can go back to 13.5? are there any risks in doing so?
No because sep and bb of 14.4 is not same as 13.5
question here. i have an iphone car with ios 14. how should i go about downgrading the ios i’m running? also, which ios should i go to if optional?
What iPhone do u have what iOS u are now and ios u want to go
i mean iphone xr* that’s on ios 14. not sure of the ios i’m wanting to go to, whichever is best for jailbreaking. easy to do/with the best features
For now 14.3 and down will have Jailbreak i can’t downgrade without jailbreak and shsh
what are you saying?
What iOS u are now bro
On u xr
If u are on 14.0 to 14.3 stay there and wait a jailbreak
If u are en 14.4 is not possible to downgrAde without shsh and jailbreak to jse futurerestore
even then his blobs still probably invalid
because you need a jailbreak to save blobs
for A12+
OH it’s 14.2. so i should wait for new software? how long will that be?
just stay on 14.2 bro
a jb is coming soon
gotcha. i assume all the websites saying it’s possible to jailbreak 14.2 are scams? i know that shit is everywhere
yeah
every jb is a scam unless it's odyssey manticore or rootless
should i just keep in contact w them three to stay updated
gotcha. thanks cutie
Some here have iphone 8 iOS 14.3 or 14.4 needone info
Is future restore compatible with high Sierra?
yes
in the coming days or weeks there will be a new release supporting a7-a12 and a14 supporting sierra - big sur
hopefully I fix a13 before that
how’s A13 going so far have you got a tester
wait for it to come back up
this why you don't put all your eggs in one basket...
yeah good thing I save blobs in multiple places
mainly the Telegram bot, which sends the blob file via TG and saves it on shsh.host
but I also use tsssaver
i already got my blobs in a local folder on my phone
fr a11 14.3 -> 14.1 FDR Fail, immediately 14.3 -> 14.3 success
sep sadly incompatible
@celest basalt
theres my log for proof
oh nice thank you
@dull swallow a13 theoretically fixed
good morning sexy mfs who would like to test a13 restoring to 14.3
GM?
What phone
iPhone 11 Pro but i’m not home right now
Lurk in the testing discord, we can use yours after we test an SE
yeah i’m in there
How can I check which Sep and Baseband i need extract, the jailbreak telegram bot isn’t currently working for me right now
wen eta //sepbb command for @mystic axle
@green onyx i was successful 🙂
what device @glacial venture
x
pog
@vocal sundial my fixes and your fixes are now pushed, try commit 191, also CI is now operational so we can try to get windows CI working eventually
@trim cargo can u test A13?
yea i can
ok lol just ping me when its good to try
Who’s gonna test an SE 13 to 14.3? Any takers
@valid adder looks like its working
if it fails it will fail right before the end
ok
ERROR: TSS request failed (status=94, message=This device isn't eligible for the requested build.)
ERROR: Unable to fetch Rose ticket
ERROR: restore_send_firmware_updater_data: Couldn't get Rose firmware data
ERROR: Unable to send FirmwareUpdater data
ERROR: Unable to successfully restore device
``` @valid adder
[exception]:
what=ERROR: Unable to restore device
code=67829777
line=1035
file=futurerestore.cpp
commit count=191:
commit sha =242163fadada9f3c2dbf29adf091a020f3f34c92:
Done: restoring failed!
so im assuming i cant try again
That doesn’t make any sense
What’s about that error
Above
@trim cargo what’s above that tss error
What does it say about rap or rose
its the apple logo rn with a progress bar
yes sir
yea now it says apnonce doesnt match
seriously
We need to request signed rose
so they are all useless then
any chance on downgrading possibly to 14.3 from 14.4 ?
guess not since you cant set the noce
I don’t think so this is a big rip
Can you send your blobs
It doesn’t make any sense that it’s missing
so do we need to specify rose firmware now @valid adder like SEP/BB
well guess i have to update then looks like i will be getting a 12 after all lol
tss saver app
I’ll look into why tsschecker blobs for 14.4 have rose ticket but not 14.3
how would i tell if my blobs has rose tickets
Yeh
why not
gotta have challenges somewhere
imagine if all A13 blobs where invalid xd because of rose
now its stuck loading in finder
Possible
@valid adder any idea how to update it with finder it just says loading
recovery
i did it was half restored so
as it literally sends a fake request to restore the device
so you get the blobs from apple
yes
i think it is actually bricked it is loading even in dfu mode
but its all good i switched to my x for now i will try again tomorrow
yea ik but it was restoring and failed in the middle so i would assume its possible
if it is bricked i have insurance so i will just get a new one might even go for the 12 now tbh
Nah you basically just unplugged mid restore in a sense
Nothing brick worthy
But if you get a 12 not it’s probably have 14.3 or lower
i will try again tomorrow
Depends on if the blobs have it
tf is a rose and how do i check if my blobs do have it
Is it possible to downgrade from ios 14 to ios 13? Or just iOS 14.0. i'm on ios 14.1
How do I check if my sep is compatible?
!t sep
How to check if the latest iOS version's SEP is compatible with a target iOS version: https://joshblah555.github.io/JoshTV/SEPCheckr.html
using futurerestore v191
SE 2 is confirmed working -> 14.3
iPhone 11, 11 Pro, 11 Pro Max still broken don't restore
W

why did the a13 fix get merged into master
@zealous bridge because they no longer have to be separate
a14 doesn't break a11 anymore
ohh gotcha
iphone 11 series still broken on 192?
it will still be broken
Unless fix it overnight
which is higly unlikely
its also an apple issue
which we have to go out of our way to fix
I really appreciate ur work guys
Guys my AP Nonce of 14.4 and 14.3 are same
can I restore from 14.4 to 14.3?
A12?
no I checked my blobs on tss website and 14.4 and 14.3 have same AP nonce
yeah
I saved blobs fpr 14.3 when I was on 13.7
Your blobs are invalid though
why?
Which version are you on?
14.4
Then you dont
they say my blobs are valid
The nonce changes when you update
so the nonce on the phone is different now
it didnt for me how?
it did.
then why on tss saver website both blobs have same ap nonce and saved at different dates
and both are valid
Because you saved them with that nonce
14.4 ones saved on 25 feb with same nonce as one saved for 14.3 on january 10
when i was on 13.7
We are talking about 2 different things
😄
wdym?
Your device has a nonce
right
yes
it generates it with every restart
but with a jailbreak and tfp0 you can set that nonce
then ap nonce for 14.4 should have been different then for 14.3
on tss website
No, because you saved them with the set generator
0x1111111111111111
i saved 14.3 with oddysey generator
Yes
and for 14.4 i didnt saved i used ecid from itunes and it saved automatically today when i was checking my blobs on tss website
But the nonce ON your iPhone changed
when u updated
This does not affect the blobs
they might be valid and would work
but you would need to set the generator on the device again
So the nonce from the blob and from the device match again
Which they dont now
then why did it saved 14.4 blob with same nonce when i didnt even have a nonce setter as im on 14.4 and not on 13.7 anymore
because you saved them with that nonce
in the “manually specify apnonce” part you put your apnonce there
but the nonce on your device is different
you need to set nonce to save valid blobs on a12-a14
SHSH2 is valid!
Hex ECID 127dde1a08002e
Dec ECID 5204942453735470
Device ID iPhone11,6
Board Config d331pap
Version 14.3 (18C66)
Restore Behavior Erase
Restore Variant Customer Erase Install (IPSW)
Generator
AP Nonce
93e0756df281e8908e108eceda66237b0d3589844b34943563095d73c8c61ad1
SEP Nonce
1f1edcb3d1eb7edf49345c6f93998979919c36b1
it is saying this
It will not work
You need to set nonce to restore
"valid" has nothing to do with it being valid tho
SHSH2 is valid!
Hex ECID 127dde1a08002e
Dec ECID 5204942453735470
Device ID iPhone11,6
Board Config d331pap
Version 14.4 (18D52)
Restore Behavior Erase
Restore Variant Customer Erase Install (IPSW)
Generator
AP Nonce
93e0756df281e8908e108eceda66237b0d3589844b34943563095d73c8c61ad1
SEP Nonce
7faa4b0a2f692a24a7d8b7a05567108bcea120ae
Because ypur device has a different nonce
and no generator set
so now say a jb drop for 14.5
and I want to downgrade to 14.3
how will i set ap nonce
?
If you didnt set a nonce when saving porbably not
Do I have to copy "AP Nonce
93e0756df281e8908e108eceda66237b0d3589844b34943563095d73c8c61ad1" and paste in oddysey?
Np
No
The device generates that nonce
Thats why you have to put that in when saving blobs
dude can you explain it easy way?
Okay
Give me a minute
how will i use my current shsh2 blob saved for 14.3
using oddysey 13.7
Not at all
Its fucked
why?
how?
Bottom Line: You did not set the nonce when saving the blob
i did for 13.7
i used tss saver app from a repo
..?
it automatically detected oddysey nonce for 14.3 my dude
not for 14.4
When I was on 13.7 iOS 14.3 was signed so I used tss saver app from repo and it detected nonce set in oddysey and saved my blobs for 14.3
now when I was checking tss saver website for my 14.3 blobs it using ecid it saved my 14.4 blobs automatically without setting any nonce as i was not jailbroken
@valid adder Can the TSS Saver tweak set the nonce on its own?
now when i checked both my blobs for 14.3 and 14.4 they both have same ap none
14.3 are 100% valid as i saved them with nonce setter
@celest basalt no, and thats an app not a tweak
Okay, thought so
set your nonce with the system info tweak
it was a tss saver tweak
set your nonce with the system info tweak
@celest basalt its an app the last time I checked
exactly its an app
also it doesn't "set" the nonce
@celest basalt So the blobs are not usable
@celest basalt remove wasabi
Bottomline
i copied nonce from oddysey and set it in this app
and it saved my blob
on january 10 when i was on 13.7
it saved 14.3 blobs
use system info tweak
correctly
im no longer jailbroken
as far as i understand you now: No you saved them without the correct nonce
i saved them with correct nonce set by oddysey
i copied that nonce and set it in the app
and it saved latest ios blob at that time it was 14.3
odyssey doesnt give you the nonce
only the generator
which doesnt help you
dude wtf are you talking bout honestly can you be more clear?
Odyssey sets that generator
The generator is the variable used to calculate your nonce
yes
is there a tutorial to see if i saved my blobs correctly?
But the device calculates it, so you need to set the "generator" in odyssey
And see what the device spits out
That is the nonc then
and that is used to save blobs
show my a tutorial so i can see if my blobs are correctly saved
if i did exactly same then it means mines are saved correctly
Did you use System Info tweak to copy the nonc?
Or your pc to read it out?
do you have a tutorial?
send me a link
But i can tell you, i am 99% sure, that your blobs are invalid
that channel is not allowed
Sorry, did not know that
93e0756df281e8908e108eceda66237b0d3589844b34943563095d73c8c61ad1 it says my apnonce is this
On your pc?
on shsh. host
Yeah like i said
That doesnt matter
Anyone know if any iOS 14-14.3 betas are signed 😂
It matters if your device has THAT EXACT nonce atm
Which it doesnt
so i can set that ap nonce with future jailbreak?
You can only set the generator
Which then calculates a nonce
yes and
If you did not do that before saving the blobs, you dont know which generator to set to get that nonce
I used 0x1111111111111111
Yup, but did you read out the nonce that this generator calculated?
its 93e0756df281e8908e108eceda66237b0d3589844b34943563095d73c8c61ad1
Nope
Again
Nope
idk where that comes from but if you did not put that in, nope
87b8ac62f4a90371180878751d6ea5ac7468e5b220b42a728b84a3cb5044c58b
That is what the blob has in it
Generator 0x1111111111111111
APNonce 87b8ac62f4a90371180878751d6ea5ac7468e5b220b42a728b84a3cb5044c58b
Yes
This is the blob right?
yes
Okay
now how will i use it in future
?
Now you need to see if that nonc matches with what your phone generates as nonce
say from 14.5 beta 2 to 14.4
if 14.5 beta 2 jb drops in say future
and i want to go to 14.4
You cant set the generator on 14.4
its an example
So the blob cant have the right nonc which makes it useless
idk man holy shit im out
xD
It is very hard to understand... This whole Apple shit
ikr apple is asshols
yeah they kind of are
fr this shit is too complicated
and get useless if both compatible sep gets unsigned
i mean even samsungs odin is better then this
To save a blob for A12 and up you need to set the generator on your device. When that is done, you read the generated nonc from the device. THIS IS CRUCIAL. This is, what you put then into your blob, when you save that.
I downgraded from 5.0 to 4.4 kitat on note 4 using odin
2 years after release
Yeah
But problem is, that i think android sucks
java is just bad as an OS
new android is better then this complicated garbage
we need native c, c++, objc, swift
True
cant even downgrade
You can
You just need to do it right
its too complicated
too many errors and all this complications man
And hope for people like @valid adder to fix things like a13 and other shit
say what should i try to dowmgrade from 14.4 to 14.3 ?
what will happen?
You are out of luck there
what will be the outcome
The device will refuse the blob because nonce doesnt match
theoratically
if it somehow does work
like american movies
then what?
And it will fail the restore
why?
Yeah... No xD
suppose it works then what?
As i said, the device will refuse to accept the blob
Then you broke apple. Congrats
can i try it?
curious to see the result
Sure, give it a go
But expect to restore
So backup your data before that
has anyone tried it?
I mean you cant even set the generator on A12 14.4 right now. So it will definitely not work.
can i downgrade an a9 device from 14.4 to 14.3?
I have iPad PRO 9.7
If you have the blobs saved, sure
CheckRa1n lets you set the generator there
OK I really-really need help.
Windows 10, iPhone X with iOS 14.5 Dev.
How can I restore to 14.3 with futurestore?
Do you have blobs saved?
No
any easy way to run without using hackintosh?
virtually maybe?
Just boot linux
linux on usb?
Install a bootable linux on an usb stick and give it a go
Yes
There you can use checkra1n linux binary
can i restore to other ios version on a9
like 9,10,11,12,13 maybe?
do you have blobs?
Only if sep is compatible
So afaik only ios 14
I have for 9.3 11.1 12.1,2,3,4, 13.5
14.1
damn
Then you might go to 14.1 there
so all other blobs are useless
Yup
why does apple have to be like that man they should atleast allow us this way as not many people can use this shsh way
should atleast make sep signed
Because they want full controll
I mean they have fked battery on 14 why not let people use this method to downgrade
They only want your best, the best security /s
meh I have friends that are still using galaxy s5 oneplus 3 and they are fine
they do banking on it
this type of security is useless for normal users
especially when theres 2fa on every app account
yeah
see if someone wants advance security they can do it themselves
why force everyone when there are still people who jailbreak
If you save your blobs right you can
it's apple's ideology
Or just stay on the version
still some people wants complete freedom rather then following rules and either stay behind and wait till god knows when the next exploit gets released
You cant buy iPhone then
how cool would it be to go back to stable ios version and jailbreak
true
That would be nice
But it is kind of fun to see new jailbreak drop out of nowhere
sometimes yes but not when you are on unsupported version
true
like unc0ver for 13.5
and 12.4
they dropped when ios was still signed
yes
Nope.... I have to save bolbs of iOS 14.3 or 14.5?
You cant, when it is unsigned
Mean don't have luck for downgrade 14.3
Yes, sadly not.
Thank you mate...
You are welcome :/
@valid adder aight nice! I don't know much about github CI atm but sure we can try to get that going, I'm busy until later today however (exam time)
sadly iPhone 11 is still broken but at least SE works
Hello good day/night everyone I have a strange request kinda lol..... I’ve never once messed with futurerestore and am looking get my XR on 13.5 ready for the upcoming 14 jailbreak would someone be willing to teamview or something with me and futurerestore my phone properly for like 15-20 bucks?? I have blobs and I’m on a Windows PC.... I’m not entirely stupid but stupid I am I know if I attempt I’ll screw It up somehow
Are your blobs 100% valid? 😄
Pretty darn sure they are I used this method
I’ve ran them through the blob checker too they say valid
On tss site
ok based on my stupidity
i am coming to the conclusion
n841ap ICE file is 3.02.02
but for a12 we need to specify it on windows, right?
idk
Can someone help me here plz ?
For only Wifi devices such iPad A9
I heard that 13 SEP is compatible with 14 SEP
The Baseband is NOT
If it’s only SEP is needed, logically why can’t I downgrade to 13 ?
Hahaha
why did it just stop
wtf
mmmmmmm
huh
oh im just a dumbass
and had an outdated file
oh ok thank u
my device is still in recovery anyways
this doesnt matter right
i think im reading it right ?
ill just proceed with what it says anyways
that's fixed in the latest build, it now outputs the exception correctly, this was caused by a faulty libgeneral patch (my bad)
i wont ask anything else unless it fails again
it worked thank you i love u @valid adder
that was my bad at first
i think it was one of the first builds he released
i didnt bother to check if it was updated until it failed
it probably shows them in event viewer
wooooo
gg
one of the most stressful things ive ever done
but thanks for all the help and tutorials <3
it made this a lot more easier
as I said, this was an issue in the first build I posted, but the current build no longer has the issue. libgeneral uses vasprintf which doesn't exist on windows and I switched it to vsprintf without manually allocating memory before that, so the exception handler always crashed due to a memory corruption
So, how do I downgrade my iOS to 14.3 if I have blobs saved.
Read pins
Ok
“- The latest iOS version's SEP & baseband must be compatible with the target iOS version: https://joshblah555.github.io/JoshTV/SEPCheckr.html”
What’s that?
no
sorry if i asked this everyday
just for SE2020
aight

