#futurerestore-help
1 messages · Page 50 of 1
Yeah, you could move Altstore my dude
Can't you use iTunes to just drag custom music into your library
Don’t you have to pay to get rid of cercube ads?
If you restore from iCloud or iTunes backup they'll still be there
yeah i can but all my shit was downloaded from YT from cercube
To get rid of cercube ads yes, but they were referring to youtube ads I believe
Did you make a finder/iTunes backup
I did not, I did a full comp backup and iCloud backup
Because that you can just open with imazing and it'll have all your downloads
Full computer backup through iTunes though?
Or how did you do it
Backup editor and viewer
Open the backup in imazing, go to file system, and find youtube
Youtube > Documents > Carida_Files
out of like the hundred+ people who've done it, you're the 4th it's happened to but yes, people should know there's a small risk
@neon ginkgo can you film this out and attach your log for future research #futurerestore-help message
@lilac wren did it a 2nd time. still the same. apnonce does not match with the blob i saved. i don't get it because the generator is the same that i set on unc0ver.
having the same issue as @lilac wren
they used cercube
u mean me?
You mean khangkhong
oh my b
@lilac wren uhh so iMazing is just telling me to reinstall my IOS because it is recovery mode. Do I just wait that out and then install the backup to see it? or what do I do here
@lilac wren so this means i can't futurerestore to 14.3rc right?
so is it mandatory to be in JB mode on A13?
I think you can probably just update to iOS 14.4 and restore your backup completely, no need to extract cercube files
Yes because you have to set your generator
I've double and triple checked, and I believe this should work. Gonna jailbreak and use FR
Most likely, if you've ever jailbroken with odyssey try that generator as well
ah so the rootfs doesn't apply to a13+ device, thanks a lot
Good luck
so what's even the point then of blobsaver?
You could rootfs, make a backup, and then rejailbreak for good measure
backed up beforehand, in rooted mode will reattempt FR
you mean jailbroken mode.
You set a generator with unc0ver. AP nonce is derived from this generator. We're using blobsaver to get your AP nonce to see if it matches the ones in your blob, also so that you can try a few different generators to find one that matches the ap nonce
android hangover 
Tim Cook comes to your door and bans you from Apple products due to breaking their ToS
Happened to me a couple times
Same fuckin thing as last time
so just a checker essentially. and you lose your jailbreak everytime blobsaver reads apnonce.
Yes, but you also lose jb every time futurerestore reads ap nonce so no difference really. It would be faster with dimentio so that you don't have to restart but it doesn't work on unc0ver ios 14 yet
same issue here, think you have to set your nonce to the one found inside the shsh file?
I know I did, I set it in Unc0ver 5.3.1 right beforehand
Set your generator to the one that corresponds to the ap nonce in the shsh file
If you saved blobs when you had generator 0x1111, that will be the generator you set
If you saved blobs on Odyssey with generator 0xbd34a880be0b53f3 then set that instead
would I need to rejailbreak on top once more?
The issue most people are having is that they saved blobs with a random generator without realizing, so they cannot find the generator for that random ap nonce, and their blobs are useless
@lilac wren what i don't understand is that i am using the same generator and i have 2 different apnonces. the photo is the apnonce from when i wasn't jailbroken and used blobsaver and when i use the same generator now using unc0ver generator, it gives me a difference apnonce.
Every time you set your generator without dimentio, I'd rejailbreak
Yep, here's my blobs text for 14.3RC, default from Unc0ver
Also had that in SHSH Host
I saved my blobs through the System Info tweak
If this was the ap nonce you got when you weren't jailbroken, the generator was probably randomized and not 0x1111111111111111 contrary to what it says here. It was probably something random, therefore your blobs are useless. But before you give up, try a few generators like I said, unc0ver and odyssey's, and make sure that it's actually being set
so here's the strange thing, my generator from blobsaver and swiping that thing for the shsh files are different strangely, not entirely sure why but only the on device shsh files have a generator of 0x1111....
- how do i know that the generator is really set?
- how do i know that the generator is really set?
If it helps I was jailbroken with Odyssey a few times, but never to save blobs. I never stayed with it long enough cause I got that annoying battery drain issue
@lilac wren So I cant even fully restart or anything, im stuck on the normal recovery
LMAOOO
The first time you used shsh.host / systeminfo, you might have manually specified a random ap nonce and just always saved using the random one. If you just swipe and say "save blobs" and use the pair it gives you, it could be wrong if you don't remember specifically getting that nonce when you were sure your generator was 0x1111
I shouldnt have said shit
@lilac wren 2. odyssey is not yet compatible with ios 14.
Can you use finder or iTunes to restore to 14.4 though? Otherwise try dfu mode
I'll exit recovery and check it out
@lilac wren 3. i used texteditor and the generator of my blobs is 0x1111.
I was using finder, it said it was not able to be updated
You set generator to 0x1111, then read nonce with blobsaver. Set nonce again to 0x1111 and read again. They should be the same. Then try setting to like 0x2222... Should be different nonce. If so, your generator is really being set
@lilac wren
if jailbreak with unc0ver then blobsaver do all the job for you, just select read from device
and it's working! grabbed the generator from the shsh file that wasn't 0x1111... and rejailbroke with it
Even if it says 0x1111, most tools now seem like they don't actually read your generator from device and just put 0x1111 as default. So it's possible your generator was random at the time you saved blobs
i meant for people who saved blobs using blobsaver without being jailbroken.
If you have A12 or above you need to be jailbroken to read ap nonce for a specific generator for the first time
and there's no way of retrieving it?
that's probably it tbh, used the same tweak
No, the point of ap nonce is so that it's mathematically impossible to reverse
I checked with System Info, it has the Unc0ver generator, unless by random chance it was random on my very first blobs
Dang, that's why I recommend tsssaver tweak for automatic retrieval of ap nonce, otherwise systeminfo if you are certain you have the right nonce and generator manually
Is there really any difference being on 14.3rc and 14.3. I have blobs for both but I updated to the rc
Wait, my 13.6 blobs have a different generator
Better to update to the stable release
Try it, try all generators you can find
If 0x1111 doesn't work
that's a tweak?
Yes, 1conan repo
If you have 14.3 blobs use them. 14.3RC was right before 14.3 but still kind of a beta
oh sounds good, I've enabled the tss bot from coolstar's server but better to do it manually
[[TSS Saver]]
I have them. idk why I updated to the rc.
Technically I should be able to futurerestore again right? I believe u0 can set the generator
I think I've found the culprit, I set the nonce then rejailbreak right?
could try shsh.host too btw @sand egret
yup that's what I just did, grabbed the gen from the shsh file and set it to that
Yes I think you can, just do note that there is non-zero risk of failure and restore loop
As with any current futurerestore
I did earlier and it gave the default Unc0ver one, I think I may found the right one tucked away in my previous blobs
You just double your chances of failure if you futurerestore twice is what I mean
think that tweak system info is the culprit
or rather you need to be jailbroken when going into recovery mode with the default unc0ver nonce
That’s why I’m paranoid lol, seeing the other guy forced to update even after doing everything right
Tried that too
I'm using the other nonce in my previous blobs
you sure you're going straight into recovery with 0 issues? It'll reset if not
It does it's thing by sending me into Recovery, then I rerun the command and it says the stuff about nonces
restored succeeded! Fingers crossed it'll boot into 14.3, thanks for all your help Coocoo! 🙂
Hi guys, can someone help me? i'm planning to restore my iphone 11 pro Max to 14.3... i have already have futurerestore v194, shsh2 blobs file ready, 14.3 ipsw into one folder. Do i need to download sep & baseband file into the same folder? Appreciate you guys help.
Again it's only happened to 4 people so far, and if your device worked last time, maybe just go for it. Up to you though, 14.3 RC to 14.3 is really minor tbh
Nope, just use --latest-baseband and --latest-sep
add --latest-baseband --latest-sep
thanks buddy.
Thanks buddy
i gonna do it shortly....now i gonna backup my phone in itunes, turn off Find my phone and anything else i need to do too?
@lilac wren something's odd. i downloaded the blobs i saved in tsssaver and all of them have no generator in them. i checked with textedit.
It's normal, mine didn't have a generator I don't think. Just set the generator to the one that matches the nonce and you're good to go
I wanna just leave it alone, but I shouldn’t run into problems down the road due to it being a beta
oooooo shit
Don't think anything other than set generator, maybe export tweak list and repo list
Sending iBEC
Once 14.5 stable is released, if the sep/bb is incompatible, you'll want to probably upgrade then to 14.3 before 14.4 is unsigned. Futurerestore may have been updated in the time between now and then
welp mac just rebooted for big sur update, no apple id verification going to happen
got it.
WOOOO I THINK IT WORKED
Well heck
But your AP nonce did match so that's definitely successful, you'll probably succeed
thanks buddy
Yeah, ig it’s smart to just wait
I used a USB C - Lightning fwiw
It's a shame that it's a rare issue and almost just unlucky
Yeah
weird q, but does my iphone lose its eSim?
mine matched as well
i got super unlucky.
sadly
I would like to know this too
Yeah what are the chances :/
I'm about to find out @wet wind so we'll see, pretty screwed if so
Yeah, but at least there's an exploit for 14.4 and 14.5 waiting around
oh is there?
Yup, it's being held onto until Apple finds it
When I went to 13.5 I did a dfu restore and it was gone, was a pain as my provider does it in store
13 votes and 24 comments so far on Reddit
Now I'm unsure lol
Since futurerestore doesn't prompt for this choice at all
Any recommended tweaks which i can export repo list & tweak list?
Restore succeeded, now all that's left is the iCloud backup
Does futurerestore do a dfu restore? That deleted it for me previously
ah shit, my local store isn't open
How about if I use the -u flag?
People have reported iCloud backup forces them to update just fyi
I'll phone up tomorrow this is going to be an issue :/
.... I think my phone might be updating from the icloud backup
Did it delete the esim :/
Yeah it asked me if I wanted to install a software update and I said not now
It made me turn on automatic updates before restoring from iCloud
back into the black page with the apple logo after icloud?
didn't ask to update either
@sand egret how did you retrieve your apnonce?
ok nvm false alarm, we're on 14.3!!!
sorry maybe i shouldnt ask this in this server.
Congrats
and it seems like my sim is gone :/
still a lockdown here, will ask soon
don't think ESim's are fit for purpose just yet
@lilac wren finially got my stuffd to start downloading, where in my backups is the cercube music?
and music I had downloaded through iTunes
@iron thorn wait! so after you futurerestored your esim stopped working?
yup, fully factory resets
Restoring from iCloud, I seem to be in the clear
Thanks for all your help @lilac wren and @green onyx from earlier, y'all are lifesavers. I'll try to help in here whenever I can
Youtube > Documents > Carida_Files
I'm doing the same, this was my first ever futurerestore and I had no clue what a nonce was
I had a rough knowledge of this stuff, but yeah this was my first go around also, super nervous but glad I did it. Main issue was just the random nonce from System Info
@lilac wren systeminfo errors out when choosing derive new in saving blobs.
But this is where it is in your filesystem, if you delete youtube to get cercube I think it deletes it from your phone. So you'll have to get it from imazing
You have to find your AP nonce that matches 0x1111 manually by using something like blobsaver, then input it into https://shsh.host
on iamazing rn
Then when you slide to save blobs it'll be the one you manually specified
Wait LOL
YouTube is now showing up as an app
because I assume cercbue was using it
Where would it be?
wait no
im blind
idk sorry
i have no blobs that matches 0x111... checked all of them have different nonce that what i have now with 0x111... generator.
If you restored from backup then it's currently sitting on your phone, inaccessible. And if you try to delete youtube to replace with cercube, it will delete all of the music from your phone. So you should do that, but then I guess manually download every song again; but now you at least have a list in imazing of every song
Then you probably don't have any valid blobs if you can't find a generator that makes your AP nonces. You'll have to start saving fresh, so go to shsh.host and input all the data, with your new nonce, manually
I think they'll still be in your iTunes library if you use iCloud music library
yeah that's what i thought. thanks.
yes they will be
thank god
now i just gotta sideload cercube
where can i find that hoe
Try this generator fwiw. I had got it from system info
0x5ea2aa6b6ef489ec
That looks like a random generator though, no chance his random generator was also that
Pretty sure generators are device specific unless default like Odyssey and Unc0ver
Generators are randomized until you jailbreak with unc0ver or Odyssey, then they're set to 0x1111111111111111 or 0xbd34a880be0b53f3 respectively
what nonce does it generate?
Nonces are specific to device
So even with that generator on your phone, you'll get some other nonce
They’re device specific, so only you can know
Unless you're both on A11 or below
ah alright.
Nope I’m on a12
In which case we wouldn't even be having an issue lol
A11 and below have a static generator right?
yeah this was a non issue on a11 and below.
Since tanbeer isn't here.. I guess i can take over
Going to sleep now, gn everyone. Congrats to everyone who succeeded in restoring and major F to @neon ginkgo (remember to fill out that form and attach log to help others in the future https://forms.gle/n9kSXcc1iUejRBGo6).
thanks for the help.
Remember that you don't need to rush to updating where 14.5s sep is compatible too
Unless you're relying on checkra1n in case restore fails
is A13 compatible now, I have an iPhone 11 on 13.5 with saved blobs with the default unc0ver nonce
@vivid nova @lilac wren is there really a vulnerability for 14.4 and 14.5 that may be used for a jailbreak?
Fuck i didnt know about all this blob shit, so I missed having a 14.3 blob saved
We tried to warn ppl to save them
Used blobsaver to get my apnonce and saved a blob with it but its only valid for 14.4
I saved mine now what the fuck do I do
I didnt even know this futurerestore thing existed
Depends what device
iPhone 11
It has for years
What iOS are you on?
13.5
If im jailbroken on ios 13.5 with iphone xs max, nothing i can still really do except wait for 14.4 or a future version to be jailbreakable correct?
Since i just saved my first blob?
Just stay for the time being
Save blobs
Then when 14.4 gets jb
You can update
is the support still buggy?
Yeah
what if SEP changes tho
Yikes, RIP. One last question, do blobs auto save on tsssaver for future iOS signed releases or do I need to manually put in my ECID again and hit Save every time a new iOS version comes out?
Even if sep changes, Apple gives about a week until the Lower firmware is unsigned
So still, plenty of time
For safe practice, always save manually
Save on every release
Doing so will grant you downgrade abilities
Ahh I see okay, will do. Btw how come my blobs differ from tsssaver and blobsaver? One says <key>generator</key><string>0x111...</string> and the other doesnt have those two fields in it
Is it because its the default from unc0ver but theyre both still valid?
Tsssaver i believe captures the apnonce whereas blob saver does both
@vivid nova Hey so I’m new I had a few questions
- Should I update to 14.3 or 14.3rc version. I have blobs for both
- I saw message about 14.5 exploit, will jailbrake be released?
- Is futurerestore safe to do on iPhone XS 13.5 iOS. Have both matching apNonce and generator
Ahh okay just checked both and theyre valid. Sucks i cant upgrade yet, fuckin hell.
Thank you for your time Capt4demote
- Always 14.3
- Most likely no
- Yes
oh ok
wait, if futurerestore fails I'm forced to update?
Yes
that doesn't seem worth the risk
especially if I'm on a very stable 13.5 jailbreak
If u see above, some guy did everything correctly. it still failed
So risk is there
sounds like my entire life
Lol
Every condom brand
By the time an exploit is released though and unc0ver dev or some other team releases a jailbreak, isnt that version usually not being signed anymore?
So you necessarily have to use futurerestore no?
No
The latest jbs will cover older oses
You don't need to update
Updating was for those whom were stuck on 14
But the older ones aint signed either
Wdym
Like im on 13.5jb right now. Say 14.4 jb comes in the future, by the time its released 14.4 wont be signed
So i would need to use futurerestore
that's why you save blobs
Not necessarily true
blob's your uncle
There's dozens of teams working on third-party jailbreaks
Anyone worth knowledge to Unix can produce one
Ye I understand the blob thing now but futurerestore could still fail no?
Ill take the chance, aint no thang to me. Was just curious how it all worked
Right now, you're walking the plank
So if you wait for the boat to dock
You'll make it to land
Meaning: too much of a risk, wait a little until it's safer
Oh well, sad I didn’t do enough research about the blobs to have done this for one version ago =_=
Could've used -u
No biggie though, thanks everyone for the explanations
? -u?
Futurerestore -u allows you to update instead of clean restore
Oof
Tl;dr
and had to force restart
What device was it?

Send a log
What my ex said
There ya go
But now Its even worse, I lost all my photos... after a update and icloud restore.
omg
why
why
why does everyone keep using prehistoric versions
of futurerestore
this doesnt even have ios 14 support
Thats just what I did from a guide...
: (
on reddit
that was made
a couple days ago
What's the link
Now I’m scared. Mine is same device and same firmware
Don't b scared
Xs restores just fine
; (
Granted you're not following a dumb guide not made by a dev
I mean does anyone know what I can do about my photos..
I cant even find
I at least want that
v182
Did you make a backup
hi, how do i upgrade to ios 14.3RC? I saved the blobs using system info but im not sure how to use it
yeah I got backups
Some guy said me to use futurerestore v194 and latest seo and Baseband commands. Is it ok?
I did an iCloud backup, buit they didnt load in
I have a computer backup as well
Can I use iMazing to move it or something?
then restore to latest and restore your backup
yes
ok thanks
@neon ginkgo plug your phone into itunes and when prompted press “restore”
Follow the pin
The pins are vital
once you’re restored you can restore from a computer backup
I did use the pin, but I just had the wrong futurerestore version
and your photos will be fine
I just thought it was the same version
thats so upsetting
why the fuck is there such an old shit
ok
Because people like to recycle
To get likes, subs etc
This is what I used
Because OP said he used this guide
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...
so I followed that guide.
"IF A12: download this INSTEAD of s0uthwest’s fork https://cdn.discordapp.com/attachments/548958604687048735/677469535737217024/futurerestore_HighSierra_182.tar.xz"
Theres even people on it
Got it..
I mean thanks I suppose
not sure what you want me to do with that info now
well
Futurerestore iOS 14 is by marijuanARM, u should’ve used that
read guides properly next time
lol don’t blame me for the fact that you can’t keep up with latest news
Didnt blame you, you're just saying something that is of no use
to rub it in my face.
aka, an asshole.
rub it in your face? bro, this is a lesson to be learnt
Thank you very much mate.
you dont
that was a bug in ios 11 that somehow has retained itself
in every single tutorial
Fckd Phone with tweaks And I could not jb with uncover restarted phone but futurerestore successed lol
İp 11 14.3
turn off load tweaks in u0 settings and jailbreak
I mean Restarted phone and futurerestore successed again
That’s overkill lmao
😂
how do i get an sep and baseband that are compatible with ios 14.3
does it matter if i have an A13 device
okay thanks
You just have to use the correct arguments @whole stag
i still need an ispw right?
im trying to upgrade to ios 14.3 so do i download the 14.3 ispw
No just need the ipsw and blobs of the version you are upgrading/ downgrading too
And do you want to wipe it or keep user data?
keep
windows or Mac
cryptic why does everyone keep using prehistoric versions of futurerestore and bootlooping their device
sux
Wait for me to fix 14.2
aww have i displaced you
Do you feel somewhat happy i was there?
You’re more likely to drop the beer while balancing it on the TV
I'm not 4K (yet) so you can set it on top
well the beer is stuck in processing rn so ig the TV will have to do
Took an hour.. But finally got idevicerestore on Linux
Hey guys, I have a question, is it possible to downgrade my iPad 7gen (iOS 14.4j to iOS 13.7 with futurestore? I didn’t saved any blobs or SSH or something like that cause I never thought that I want do downgrade, but I miss the iOS 13 Jailbreak (cause on iOS 14 doesn’t have much tweak suport)
Well, but I have the ability to jailbreak it with checkra1n cause on iOS 14.4 it won’t work for me
Oh?
Yeah the iPad 7 have A10 I guess
Won’t work for me :/
What error you get?
No error, checkra1n closed while it’s trying to jailbreak my iPad, and my iPad stucks at the dfu Mode
Wdym it closed? Did you try cli?
Yes
How did you do cli?
I use the file from checkra1n.app/Contents/MacOS/checkra1n
No. Need to add -c
Well then I will try that when I’m back @ home😅
im restoring to 14.2 rn? seems to be working too
you have or is it still restoring
well did you not get warned abt 14.2
yeah ik
whats the error?
i wanna try though
oops
ERROR: Unable to receive message from FDR 0x7f958ec06b00 (-2). 0/2 bytes
ERROR: Could not read data (-256). Aborting.
Cleaning up...
[exception]:
what=ERROR: Unable to restore device
code=68026385
line=1038
file=futurerestore.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:
Was there a loading bar below the apple logo
yes
you back?
this didnt happen then
it did
how far was the loading bar
oh
makes sense then
You should maybe say that when I ask you
its fine
its broken asf tho
I dont think anyone has been successful in the past few days
true
Halfway done half the pain left
to change my ECID to match my blob, input what verify.shsh.host tells me my ECID is?
Big thank @zealous bridge & @heady thicket & @vocal sundial help me. Use fr v194 from 14.1 upgrade to 14.3 add -u to keep data for my A11 device. Now works propely.
ay
@spiral patio write survey plz
survey? how to write loooool
ok let me see
my blob doesn't have generator in it, so I don't know what my blob APNonce is
device?
11 Pro Max
went to verify.shsh.host and it says "3fbdaf3c3c195b7d3243341f7c551f39810ec8e38d8b22ecaea46d3854d65ed3"
yes
were you jailbroken with unc0ver
yeah
if so your generator is probably 0x1111111111111111
i can't rejailbreak using unc0ver app now
why not
complete
because i already rootfs
gets to 30/31 says jailbreak complete and reboots, still no jailbreak
you have to wait a minute or two for cydia to pop up
even if it only gets to 30 out of 31?
yes
nevermind figured it out, didn't select reinstall cydia
when i change my generator, do i need to rejailbreak it or just click done in unc0ver?
rejailbreak
damn but i lost all my tweaks
shouldve saved a tweak list
i did take a screenshot
you wont need it anyway futurerestore wipes your phone
i know, but if it's pointless going to 14.3 from iphone 11 Pro Max, then why try
do I need to rootFS if I'm trying to do futurerestore?
alright
futurerestore isn't working for me, so i guess I'll stick to 13.5 for now
Entering recovery mode...
ERROR: Failed to place device in recovery mode
futurerestore: failed with exception:
[exception]:
what=Unable to place device into recovery mode from Normal mode
it's weird because i'm looking at my phone right now and it's in recovery mode
restore failed
error?
Sending iBEC (1709144 bytes)...
ERROR: Unable to send iBEC component: Unable to find device
ERROR: Unable to send iBEC to device.
Cleaning up...
[exception]:
what=ERROR: Unable to send iBEC
code=64684049
line=987
file=futurerestore.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:
Done: restoring failed!
dope, it didn't fail after running step 1-6, so it looks like it's working so far. install apple logo
nice
i hope 14.3 is worth it
14.2 is broken
Can’t restore it to right now
Futurerestore will error out if you try to restore to 14.2
Device model doesn’t affect futurerestore
can anybody help me out in #genius-bar :/
what chip is ipad 6
oh its A10
hm wait lemme see
@celest basalt if you use v194 14.2 should work
Use latest sep
and you’re probably better of with windows static exe
Can i use -u and keep mydata?!
Yes
@zealous bridge
Then i should to restore rootfs then futurerestore
No
Looking good
Doesn’t matter
Looking fine
Updating wipes root anyway
@violet lotus
Doesn’t matter if you rootfs or not
It’s redundant if u do
So it's not risky to use -u
Done it loads of times
the update will restore rootfs but it wont affect any user data
yep
thats why 14.2 is broken
Told you
@valid adder looks like 14.2 is broken on all chips
It’s not
Where i put -u on windows command
@violet lotus doesn’t matter ipsw has to be last and the blob has to be after -t
so no problem
futurerestore-v194.exe -t blob.shsh2 --latest-sep --latest-baseband -u target.ipsw
ya dont have to but its always useful
Hello everyone, I am jailbroken on iphone 11 (A13) ios 13.5 unc0ver 5.3.1, I have blobs saved for ios 14.3, can you recommend the best tutorial for using futurerestore on a mac please ? Thank you !
first pin @kind kraken
Thank you !
Anyone know if FRIng to 14.2 is fixed?
The mostly static Linux build I mentioned earlier seems to be working! I have only tested my iPad mini 2 for now, so next I will be testing my SE to test restoring to iOS 14
Here's the output of ldd btw
no
i used succession on 13.1.3 to reset my phone, now i cant even activate it
any ideas why
whoops wrong channel
Hey, when I try to save blobs with system info, it says the generator that it’s saved with is 0x3a... rather than 0x1111111111111111, any help with this?
@night harbor missing patchers u noob
yeah haha
My CI will eventually support Linux and windows
v194 was the first CI mac release
Prior releases were built by hand
is there an a11 nonce setter?
[[dimentio]]
so its completely impossible to set the nonce after i updated to 14.4?
a11 or under then you can jailbreak using checkra1n and set the nonve
nonce
but checkra1n doesnt support 14.4
just use
and try it out
if all you need is the nonce setter then you should be good
make sure to disable passcode and face ID
and enable this
if you're on A11
after restoring backup device is stuck at bootloop(14.3, iphone 11 pro max)is there anyway to reset the device without updating to 14.4?
no
if youre in a bootloop
you have to restore to latest
can you send a log first @jade raft
how to pull out the log since i am in bootloop @zealous bridge ?
on futurerestore
from windows cmd / terminal
copy everything and paste
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
im guessing 14.2 is still broken?
Yeah that's definitely user error then...
What should you have done differently / what to do next time? I could say read the pins of this channel, but it's not really told to you (only would've come up if you asked what futurerestore version to use). I could say follow a guide, but technically you did.
I think I'll just say to be more aware of what's happening currently with anything that's brand new (new fork https://github.com/marijuanARM/futurerestore/releases, still a bit jank, doesn't work for below 14.3 on A11 and above). Especially because all this new stuff isn't really the first thing you see when you Google "how to restore to 14.3 A12"
So even while it may technically be user error, that doesn't mean it's really your fault
doesnt work
can you put it in a text file and DM to me
Be frank..today is my first day in discord
you can try using https://gist.github.com/ instead
Thank you
you're not in a bootloop
use this command to get out: "C:\Users\m.anas\Downloads\restore>futurerestore-v194.exe" --exit-recovery
next time you use futurerestore make sure to set nonce
back to same ..bootloop
i
You didnt set generator properly
why did you edit blob
lmoa dont touch the blob
well you done fucked up now
redownload on shsh host or tsssaver unless u only did it locally
if you dont have the previous generator of the blob that blobs gonna be useless
is there any way to set nonce on recovery mode for A13 device?
no
be jailbroken
i have it so can i recommand with the orignal blob ?!
now this is the orignal blob and still the same error
you have to set your device generator to match the one in your blob
now i cant get of recovery ?!
^^^ tutorial
drag futurerestore to terminal then type “––exit–recovery”
yes but this is easier to explain and easier to do
No..again it goes back to bootloop..only what i am able to do it boot in to recovery
okay now iam on unc0ver i just goto unc0ver app and put 0x1111111111111111
no change that and put the generator from your blob in there
then goto recovery ?!
then run futurerestore
should i run fr firist or goto recovery first ?!
i just said run futurerestore
okay
I'm gettin error "Device ApNonce does not match APTicket nonce" I checked my generator inside the blob and set it with NewTerm. any idea?
Nope
me too i match my blob generator to inside uncover app and still get the same error
Did you press rejailbreak after typing the generator
iam now jailbroken
now the device it rebooted and become not jailbroken but the generator is match with blob
can i run fr or i need to rejailbrake and set it and rejailberak agine ?!
Did you have to enter your password or did touch/Face ID work?
yes
If you used touch/face ID then it’s a user space reboot and the generator is set
i will turn it of and repet all steps againe
when you set it in unc0ver app press jailbreak button
Hello, I'm jailbroken on unc0ver iphone 11, ios 13.5
If I don't have generator in blobs and in Settings -> About -> Boot-nonce is default 0x1111111111111111, am I good to go ? do I have to do anything else at this step ?
this will work only if you were jailbroken with unc0ver at the time of saving blobs
I have been jailbroken for a year since 13.3 and have saved blobs ever since with blobsaver on mac
you mustve been jailbroken and with unc0ver at the time of saving blobs
thats all that matters
however sometimes while trying to save blobs with blobsaver my phone would reboot and I might have saved blobs in unjailbroken state. does it make a difference ?
is there any way I can know for sure if it's safe ?
as long as you jailbroke right before saving the blobs, that's fine - it reboots to recovery mode to get the apnonce
well, doesn't have to be right before, just make sure you were in jailbroken state when you clicked "read from device"
wow, now I'm not sure anymore. I remember it failing once to save them, it rebooted and I'm pretty sure I didn't rejailbreak when saving them the second time. and I can't remember for which version this happened 14.2/3/4 ...
if you're jailbroken you can verify it by saving new blobs (for 14.4) and comparing the apnonce
that doesn't necessarily confirm that it was saved with the correct apnonce
right, how do I compare apnonce ?
make sure you're jailbroken, then click "read from device" in blobsaver again
the old blob's apnonce should show at the end of the filename or on verify.shsh.host
and just compare that with what blobsaver says
all of my blobs from 13.5 to 14.3 have the same long string of characters at the end of the filename
does that match what is shown in blobsaver?
it matches with blobsaver and verify.shsh.host but blobsaver fails to get apnonce in jailbroken state, i get irecovery error =-3, it works only unjailbroken it seems
the generator persists sometimes during reboots
so yeah as long as it matches
you can use them with futurerestore
so from the tutorial pinned here, I can skip step 6, settings nonce generator, right ?
if you rebooted you should do it again just to be sure
do what again ? jailbreak ?
step 6
ok, so I can set my generator in unc0ver and use the default 0x1111111111111111 ?
if thats whats in your blobs
that's what I was saying earlier, I opened my blobs with textedit and I don't have any generator in them
what generator did you use that made the apnonce match?
just use that one
which im guessing is default
so yeah do this
Alright, thanks, hope it works. I've been a little confused about this part 🙂
Any news on 14.2?
no
is that normal ?!
if the apnonce on verify.shs.host and blobsaver doesn' match that blob is useless?
Windows?
yes
its still running ( extracting ipsw )
okay
I have used Linux and MacOS, will try the windows
MacOS and Linux have the same errors thou
@zealous bridge will it cause any errors ?!
dont think so
if the apnonce on verify.shs.host and blobsaver doesn't match that blob is useless?
yes the apnonce must match with your blob

i tried deleting iboot and reenter the command but same error
Drags the Futurerestore file then type - -exit-recovery ( no spaces between the - - )
Futurerestore —exit-recovery
i followed this guide
i didnt exit recoverumode yet
but its still the same error
Why does apple make such bad drivers
lol
i have read that to uninstall itunes MS store version
and download spasific version
Make sure you check the box to delete driver files
Yes that’s the exact reason for that error
Lol
My pinned fix is the best for fixing that
i tricked it
where ?!
You can search my history messages. I followed this guide to fix IBEC error
I’m sure @valid adder pined message can fix this error 🙂
So is a11 futurerestoring to 14.2 a fixable problem within futurerestore? Or its on apple's side and doomed?
Apples side but there may be a workaround
hi guys, can some help me..i'm stuck now while performing futurerestore to 14.3. iphone 11 pro max in windows
i need some help here..
I'm getting this error
actually i read many times..i'm cant think...
The ironic thing is this was just support right before you asked
How do I verify that my blobs have the same nonce as my phone?
Thanks buddy, manage to restore
lol
And are 14.0 and 14.1 bugged just like 14.2?
yes
Also I compared my 14.2 blob and just saved 14.4 blob and the name is basically the same except for the iOS version of course and the 14.4 blob has the string “18D52” while the 14.2 blob has the string “18B92”
Is this ok?
And they were both saved with the generator 0xdc77cc754eccb488 for some reason instead of the generator set by unc0ver
Is this bad?
would anyone be willing to just send me the 14.4 buildmanifest if they have it on hand, don't wanna download the whole ipsw rn
Hey guys and girls!
I'm currently taking a backup of my jailbroken iPhone XS Max. Just to be sure: can I update from 13.5 to 14.3 using the guide in the pinned messages (PC with Windows)?
yes
I heard it was a 50/50 chance of success bc there’s something wrong
Not willing to risk it until a fix
Searching for clarification as the information surrounding this has been all over the place. Is there any potential chance that A13+ will be able to FR to 14.1 in a future build? Uncertain if we know for sure that the SEP is incompatible, or if this is something that is being further investigated
if you downloaded itunes from microsoft store uninstall it and all drivers then download it from itunes site
Yeah it needs a fix
I tried 14.1 on A11 and same error
I'm pretty sure I didn't install it from microsoft store, but it's been a while since I installed it. Any way to check where it was installed from?
Yeah I think below 14.3 doesn’t work rn
It’s a shame that’s the only blob I forgot to save
hello
just uninstall it and redownload it
fair enough, thank you!
Yeah I usually save blobs religiously but I have an Android device I use and was off the iPhone train during 14.3 so that is the only one I'm missing also.
i have iphone 11 and blob from ios 14 beta 8. Futurerestore works with beta? I want restore from 13.5 to 14 beta 8!
are those the only blobs you have?
it should work, but expect it to be buggy
actually hold on
no, 14.0 SEP isn't compatible for A13, so it won't work
🙂
only 14.3 sep is work?
14.3 yes, possibly 14.2 too but that seems to have more issues
i have 1 apnonce when i save in site shsh.host, but when i futurestore'd ios i have an error! Diferent apnonce!
when i look in recovery mode my apnonce, and i have diferent apnonce then i save it! I want add my old apnonce, how i can to do this?
so it seems something did not work for me. May I post a part of the CMD here?
@valid adder @zealous bridge Thanks for your great help !! now i can rest in peace 😂
this is the result I get. Seems somethings wrong with the nonce I set in unc0ver what is a bit weird imo as I entered the nonce which I've found in the shsh2 file
its not done
it hasnt said succeeded yet
idk but the device started up and its 14.3 now
did you use -u ?!
@shy magnet does it need to say succeeded?
nope
what
does it need to say the restore worked?
yeah i think it does

and it did what are you talking about @green onyx
you are a blind person
doesn’t matter
that’s just futurerestore cleaning up
if it fails after restore succeeded it doesn’t matter restore’s already done
sorry to crash again guys, just a quick question: my restoring failed with some apnonce error (I'm quite sure I entered it correctly)... any way I can safely boot the phone again?
i think its just say finished cuz i use it in update option and kept all my data
as long as the device knows that its done restoring (status message) your fine
it’ll go into the second apple loading screen and verify
@green onyx thank u very much
np
––
sorry again for crashing in
two dashes
just to make sure, futurerestore-v194.exe , right?
Also I compared my 14.2 blob and just saved 14.4 blob and the name is basically the same except for the iOS version of course and the 14.4 blob has the string “18D52” while the 14.2 blob has the string “18B92”
And they were both saved with the generator 0xdc77cc754eccb488 for some reason instead of the generator set by unc0ver
Is this bad?
yes
no
Can I set my generator to that when I’m futurerestoring?
ur suppose to set it to that when using fr
so this is the nonce in my blob.shsh2, I have to input this string in unc0ver>settings>generator right?
May be a dumb question but if I futurerestore from 13.5 to 14.3, will I be able to restore my data from an iCloud/iTunes backup?
So guys, I've been chilling on 13.5 and got lazy with saving blobs. I just want confirmation that I COULD HAVE downgraded from 14.4 to 14.3 (or RC) if I had saved blobs with FR on an A12 device
no, on A12 you can't downgrade from 14.4 even with blobs
until a jailbreak comes out for 14.4
Okay thank you! That makes me feel better
yes, should be fine, iCloud probably better (or restore rootfs before making an iTunes backup, then JB again to set the generator)
yes
Cool thanks.
getting a new error now:
failed verification with error: [exception]: what=verification failed! code=84279308 line=1286 file=img4tool.cpp commit count=197: commit sha =aca6cf005c94caf135023263cbb5c61a0081804f: [IMG4TOOL] checking buildidentity 8: [IMG4TOOL] checking buildidentity matches board ... NO [IMG4TOOL] checking buildidentity 9: [IMG4TOOL] checking buildidentity matches board ... NO Cleaning up... [exception]: what=Failed to find matching buildidentity code=85917708 line=1311 file=img4tool.cpp commit count=197: commit sha =aca6cf005c94caf135023263cbb5c61a0081804f: Done: restoring failed!
anyone nows whats wrong? it's not the nonce this time
what blobs do you have
the blobs I'm using are for 14.3
14.3 normal or 14.3RC
14.3 RC
And what ipsw did you download?
get it from https://ipsw.dev
Download developer beta versions of Apple's iOS, iPadOS and tvOS firmware.
I checked if theres another 14.3 ipsw available, but only found this one so I assumed it was the correct one
Build number 18C65
thanks for the clarification
Download developer beta versions of Apple's iOS, iPadOS and tvOS firmware.
Select device
And choose 14.3RC 1
You’ll be surprised how many people did the same thing
it's very confusing tbh
RC, non-RC, I just saw RC 2 lmao
.
ye
looks good so far, it's writing something on the phone
I see the apple logo with the progress bar
thats good
hope nothing goes wrong now, otherwise the phone is rip I guess?
Oof, unlike nothing should go wrong from here I'm a bit worried tbh ^^
so the screen went black, the apple logo and later a second progress bar appeared. The log says "restoring succeeded"
yep thats normal
good lord, that was killing me. I see the welcome screen now
thanks guys for your help!
@flint valve fill out survery in pins
will do!
Restored successfully an iPhone 11 Pro seconds ago from 13.5 to 14.3. Smooth sailing.
Thanks to all you Devs out there
If you had a success could you please fill out the survey in pins
of course. where do i get the log file from?
you can copy paste everything in command prompt / terminal and put it in a .txt file, then upload that



