#futurerestore-help
1 messages · Page 56 of 1
Did you cancel futurerestore while it was running?
even then as long as they’re in recovery its fine
It corrupts their ios though
Honestly, probably
no not really
yeah
I don't know what happened
thats the apple logo
Yeah you should just dfu restore, follow the steps I pasted above
well you’re definitely not giving us much to go off on
your best bet is a dfu restore
i tried and keeps going back to recovery mode
You're doing it wrong then
your holding down side too long
5-8 seconds should do
DFU is just a black screen
Again, if the Apple logo appears you're holding power button for too long
Apple logo will transition to recovery mode screen
or recovery screen
So I'm pushing vol up and the vol down, then holding side button until black screen then i cont. to hold side button and also push vol down for 5 seconds and then i let go of side button
You know what'd be cool, if a jailbreak installed a MacOS type recovery partition. Filza, terminal, ssh and dimentio all available from it when the os can't boot
it goes to apple logo for a split second and then back to recovery screen
Pretty much, if the Apple logo appears while holding the side button in those 5 seconds then let go earlier
Yeah only hold for like 3 seconds
eh, i wouldnt fuck with iboot and how it boots up partitions
Just keep holding volume down until iTunes detects
could brick your device
what about this then
i tried for 3 seconds and it does the same thing
wiping iboot bricks the device
bootrom is built into the chip
which loads up iboot
if thats wiped its perm bricked
normally if iboot fails phone goes straight to DFU
When futurerestore stopped working, if it did, the apple logo was at the half way progress bar
you’re definitely in a bootloop
if iboot is wiped phone wont know that it failed and wont enter DFU
leaving it bricked
So what do i do
try dfu again
only option
You’re definitely doing something wrong
are you pressing vol buttons too fast
Yeah dfu should work
Oh wow didn't know that, ty for knowledge
Should be some kind of failsafe for that because its RIDICULOUSLY easy to wipe iboot
just from physical access
Try this
- Quick-press the volume up button.
- Quick-press the volume down button.
- Press and hold the Side button until the screen goes black.
- Release the Side button once the screen blacks out, then ...
- Quickly press and hold both the Side and volume down buttons together for 5 seconds.
- After 5 seconds, release the Side button without letting go of the volume down button.
- Continue holding down the volume down button for at least 5 seconds.
Let go of all buttons when the screen blacks out
Then hold vol down and side for 5 seconds
Physical access with a checkm8able device or any device?
So once the screen goes black let go of everything, then repress the vol down button?
And side button, for 5 sec
Then let go of side
And only hold volume for another 5 seconds at least
“An easy way to do this is flash an Internal UI Build and go to Settings/Internal Settings/CoreOS and press "Brick Device". This will wipe the iBoot Partition. It is not currently known if this is recoverable from.”
got it into dfu mode
You just have to somehow flash a build firmware to it
Connect to itunes and press restore
Yay gg
You can just flash firmwares onto iPhones? Lol what, I must be misunderstanding
iTunes/Finder popped up, i clicked restore and then a popup showed to restore and update. i clicked yes. now nothing
Is this made by Apple or a third party, why is it literally called "brick device"
Just wait a bit, let us know if your phone or iTunes doesn't change within 5 min
You can’t, it has to be an Internal UI Build which are just internal versions of iOS for testing before release
Made by Apple
Flashing the firmware would be the main problem but with the right tools
You can easily just brick a lot of them in one go
Could i have bricked my device?
Nah
No
That’s basically impossible
So what other options are there?
link?
Sure
Restore to latest, then try futurerestore agian
did you fix the log getting cutoff
I just want my phone to boot lol
Happy to say it's actually usable now
Yep and added a few things
Auto retry on recovery mode
Also added a gui telling you what step it's on
Progress bar looks smooth as well
Only issue is I've only tested it up to the point where I can without restoring
Hopefully I can find someone to test it fully
Alright, itunes hasn't done anything
yes
Does iTunes recognize your device, what options are there rn
It knows there is any iphone plugged in. It only calls it an "iphone" and the only option i have is "restore iphone..."
Try clicking restore iPhone again
Thanks for your help
Gonna be honest no clue, managed to solve it by appending "ready to restore" in the log right before it starts. Still freezes right at the beginning but runs a lot better
Good night!!
I clicked restore iphone again and nothing happened
Does it support windows?
Yep, use Universal
Oh nice who made?
Me
Are you using window's iTunes?
i'm on mac
yeah not really itunes
Alright ill try
Okay I'm restarted
2 hours later, its restoring
wtf
Will your FutureRestore GUI work for downgrading as well?
Yes, it's just a gui for futurerestore itself
Let's test it out
Thanks so much :D
Should I restore my backup before or after I downgrade? Also, I never restored rootfs... completely forgot to do that, the first time
I don't think you need to restore rootfs, you need to be jailbroken anyways
And restore your backup afterwards, since futurerestore usually erases all data
Alright. So once I boot up my phone, I'll jailbreak with checkra1n, set apnonce, and then use your GUI
Hey 1conans dimentio works on Odyssey correct
Yay :)
Yes it does
Wait, if I restore rootfs after I set the apnonce, won't the nonce revert?
So jailbreak, set nonce, GUI?
Yep!
okay
And since you're on Mac, I'd appreciate as well if you could test using the specific Mac app instead of the universal jar
Just because the Mac app wouldn't open for other people before
Yes that's what I downloaded
Thanks!
app popped up for me
Yesss
Latest or manual sep, latest, manual, or no baseband, wait arg, update arg, debug arg, buildmanifest for both sep and bb, dark and light mode for the gui
Also of course choose futurerestore binary, blob, and ipsw
what about the -w and -u and -d, do i need to worry about any of those
Nah don't use them, -w doesn't work on modern phones, -u is to preserve data but you're fresh anyways, keep -d for extra logs
apnonce is set
Nice
anything else before i hit start futurerestore
I don't think so, just watch the process for anthing you think might be unintuitive or weird
its going
Nice
in recovery mode
It should automatically re-run the command when futurerestore fails to detect device in recovery
it says Unable to place device into recovery mode from Normal mode
It should say that once, but then keep running and actually do it
it said it twice
Lmk if it just stopped
Oh actually that's weird
Is the phone actually in recovery mode?
futurerestore: failed with exception:
[exception]:
what=Unable to place device into recovery mode from Normal mode
what=Unable to place device into recovery mode from Normal mode
code=8978449
code=8978449
line=137
file=futurerestore.cpp
commit count=29:
commit sha =2994651a10d8176a298b31e7706b4b6af97975d1:
yes phone is in recovery mode
Is the start futurerestore button greyed oht
its greyed out yes
okay it's started again
Ok
so I have an 11 pro max with 13.5 and a blob for 14.3 generated by blobsaver. I have alse retrieved the baseband and sep files from 14.4. Q1: can I use the -u option for blobs saved with blobsaver? Q2: can I use the --latest-sep --latest-baseband option or do I inject them from the 14.4 firmware?
Sending filesystem!
Yay!!
Does the progress bar actually fill up on the gui?
doesn't look like it
yes
Ugh then I gotta fix that
sweet tool though!
When it's done, I'd appreciate if you could "command a" copy the log and paste it into pastebin.com
Thanks!
it's a 14.2 issue. I faced no green bg on arch, ubuntu and windows all on the latest build
then fails out. Device cant enter restore mode
I'm getting this over and over "FDR 0x7fe634c05520 timeout waiting for command
FDR 0x7fe634c05520 waiting for message...
No data to read (timeout)
No data to read (timeout)"
Ctrl F your blobs to see if they have upgradeinstall for Q1, Q2 yeah you can just use --latest
received shsh blobs is the last line before it gets stuck and fails
Are you using v194 of futurerestore?
not sure...
The gui should have asked you at the beginning to check for latest version of futurerestore lol
Run ./futurerestore and see what version it says
In terminal
it's not the updated version i guess
I found this in the blob: <key>updateInstall</key>
What version is it
Then you can use -u
69 lol
cool
version 69?? You're sure
When i type that command it doesn't do anything
It may be version 180
Looking back at my tabs
Drag futurerestore into terminal and press enter
180
No way
That's why it failed
That's literally so ancient lol
Get the latest please
Q3: my blob has an APnonce, do I still have to set it in Unc0ver before proceeding?
What do i do to stop it and try again
Set your generator (boot nonce) in unc0ver to the generator in your blob
Is it still running or did it say "restore failed!"
And what's your phone look like rn
still running
thx man, you are amazingly kind in helping us
Np
Its definitely not going to work, if you stop it now you'll need to dfu restore again lol
If you leave it, you'll probably also need to dfu restore
so click stop
Yeah
and dfu restore
Yep
son of a
Lol
I literally included the version checker
So that this wouldn't happen
I didn't expect people to ignore it
Well i clicked yes check it and then it just started going
Lol oh well
You're lucky you're A11 lol
why?
damnnn
Or until a jailbreak for 14.4 comes out
which will eventually, but who knows when
At which point why even downgrade
iphone x gang forever
Haha yeah
Oh @valid coral could you copy the entire log with Cmd A and put it into a pastebin.com? It would help me for next time
Ok good luck
restoring succeeded
Nice gg
gg
Does the current task say "restore succeeded"
And can you upload this log as well if you don't mind
it says Restore Finished
Ah ok
I just forgot the exact wording, wanted to make sure it said that
Well gtg to bed, if you could upload the logs I'd appreciate it, otherwise enjoy your new restore and thanks for testing!!
i7's a no-go
Do I have to delete the Apple Mobile Device (rececory mode) file inside device manager?
@lilac wren GUI works perfectly on everything I tested
if you get the iBEC error yes
It’s a hit or miss
Is it wise to try and use future restore on Xs Max 13.5 to 14.3 using windows or should I wait
14.3 success rate is good
@green onyx I succsessfully updated to 14.2 now! ty
Ok cool I may try it later on gotta back up my phone first
can ya fill out the form in pins if you got a success
is it possible to upgrade my iPhone xs to 14.2? it's on ios 13.5.1 jailbroken
i thought you just upgraded
Sep is compatible
so it's a 50/50 chance
some people says no
Its your choice
i won't upgrade then unitll it's 100% clear
im not
Thats a good decision
@night harbor Linux version compiled with odysseus 32bit and 64bit patchers

How tf did you manage to get libipatcher working on linux
cctools headers
where's the form?
wen eta FR working with i7
@vivid nova without more research done there is no current workaround to got from 14.3-14.5 to 14.2 or lower
Get*
nice!
@valid adder the imazing didnt work to get out of recovery mode, but iMyFone Fixppo did!
@celest basalt stop using itunes rip-offs
i'm not
yes you are
imazing and imyfone are rip-offs
@celest basalt still think you should driver purge
that was to get out of recoveryy mode
There are some guru tools to do this probably
cryptic you deserve a blowjob after the pain of future restore
i got stuck in recovery mode and if i didnt use that fixppo i wouldnt get out if it
74c065565e64e3b447f73bcd9087ed78080193ec
@dull swallow nah I’ll take btc
@vivid nova like I’ve already tried with 187 sources didn’t work so dep maybe?
lol
194 seems to get the nonce and whatnot.. but it goes into the panic of timing out after said attempts (you'll know the !!!!!!!!! error)
nor do I.. perhaps using official idevicerestore instead of a fork?
Nah
It’s upstream
Could use a rebase tho tbh
I think apple broke img3 blobs
Lol
nah.. i think fr is /somewhat/ crippled
Just wiped linux and ran the binary and it ran so it’s linked properly @night harbor
Works out of box on 20.04.2 lts
will the linux binary be added in the 194 release?
awesome
Should I do a script or arch
I kinda did cleanroom, didn’t use your script as a base. I didn’t use static, only disable shared
Same way I do mac

ohh isee, i learned some stuff from modifying opa's script tho even if it's simple, it was something to learn from for me haha
whats the default ubuntu owner
its cryptic:cryptic
but whats the number value
im on mac now so can't check
uid 1000 i think
1000:1000 makes sense
look good for release? @night harbor

Good morning guys, have a few questions.
Im currently on iOS 13.5, iPhone 11, jailbroken through unc0ver 5.3.1, previously jailbroken with unc0ver 5.0.1.
AFAIK I never changed the Generator inside unc0ver settings, so it should have been at 0x111..... the whole time. All blobs were generated while jailbroken.
I saved blobs with Blobsaver 2.5.4 (https://github.com/airsquared/blobsaver) somewhere in november. Have blobs for 14.1, 14.2, 14.3, and 14.4 for my iphone 11 (iPhone12,1).
verify.shsh.host tells me my 14.3 blob isnt valid, but all the others (14.1, 14.2, 14.4) are valid. Is that an error on that site or is my blob actually fucked?
If my 14.3 blob for some reason is actually fucked, whats my best action?
they might be 14.3RC blobs
try selecting 14.3RC instead of 14.3
then check what shsh.host says
thanks for the help! Unfortunately i cant seem to select release-canidate versions on shsh.host to verify the blob
scroll down on the version number select box
....my bad
it’s there
apologies for thats
np
its indeed a 14.3 RC blob
awesome
so in theory i should just be able to check if my current apnonce is the same it used to be when generating the blobs (would just use blobsaver again to read it), and be on my way?
Would you recommend running future restore on windows or on linux?
you can do that, or if you set your generator with dimentio or the tss saver app it reads off the apnonce anyway which you can cross-check with the blob
both windows and linux are essentially the same
except for a driver error which is fixable
can someone test the linux version
alright will do! Appreciate all the help, if i run into any issues, ill let you guys know! Have a nice day
eh...dont wanna risk my personal device but i know the feeling of needing your software to be tested....how likely is it to put me in a situation where i need to restore to a signed IOS?
i'll test it soon
According to TSS Saver my current Generator is not the 0x1111.... one. The nonce i get from TSS Saver, matches the nonce from the saved blobs though. I assume i am still good to go?
14.4 SEP and Baseband compatible with 14.2? Want to update A12 to 14.2.
What is the best tutorial/video for future restore on Mac?
dont trust anything that comes out of my mouth, but im planning on using this: #futurerestore-help message from this channel pins
its really a 50/50 on A12 to 14.2
Will futurerestore delete all data from the phone?
yes
if your apnonce matches that blob is good to use
yes, unless you put “-u” into your command
Thanks
this is fine
appreciate it
Cool. Thanks.
Is it worth a try?
no tbh
Yes that’s what I worry about
Ok
Just tested the new build of futurerestore 194 for Ubuntu 20.04.2 live USB, and it worked out of the box, thanks @valid adder
Device: iPhone SE (iPhone8,4, A9)
Target version: 14.1
Script almost done
What if I run these commands:
wget https://lukezgd.github.io/scripts/futurerestore_compile.sh
chmod +x futurerestore_compile.sh
./futurerestore_compile.sh
then you will compile futurerestore
No point tho there’s a Linux build already
@lilac wren gonna test a full restore on your gui
not sure why it's unrecognized, i think that should work
Fixed it
nvm
@lilac wren your gui does get stuck a fuck ton
also i think i found another log output limit
restore is still going fine
just log is stuck
I successfully got back to 14.3 using futurerestore and when I tried to reinstall my backup nothing is happening. It will go into restore in progress but no progress bar. I've let it sit for 15 minutes and nothing. What is causing the issue?
progress bar at 50% on device
thats where the output stopped
ok sending filesystem finished but all that appeared after everything was sent and verified
ohhh hold on
first time it got stuck was the extracting filesystem from ipsw progress bar
next time was the sending filesystem progress bar
think its broken
restore going fine
also gets stuck at updating baseband
k now progress bar on device is stuck
restore hasnt failed
2/2 for the gui
might need to look into where it gets stuck
@night harbor builds from fresh linux fine gonna post the script soon
thanks for the linux binary and script! it will help a lot
thanks, i'll check it out
anybody have any ideas?
@lilac wren i've commented the parts where the log gets stuck, just CMD+F for "stuck"
Also another thing to note is wherever it gets stuck, the next part of the log comes all at once until the next time it gets stuck
hopefully this helps with diagnostics
try set it up as new and then restore backup
Anybody successful with future restoring iphone 11 pro , jailbroken uncover on 13.5 I want to go to 14,3 but I'm not sure on apnonce on my saved blobs, I used shsh host to save. My generator in sys info tweak the normal uncover generator of the 0x111's however when I check verify shsh on shsh host have a diff gen key
you can set the generator to the one in your shsh file
And the apnonce should be correct I'm used to tiny umbrella shit was easier back in the day
f22 would have to be generated on a jailbroken device with the generate 75a
f22 is your apnonce
Just f22 or that whole string and ah
I just didn't want to sit here for 5 mins typing it out
I feel ya
#futurerestore-help message use this tutorial and set your generator to the line in your blob (0x75a....)
@pearl fog
My phone overheats a lot I don't think it's jailbreak or tweak caused so I'm hoping 14.3 is better, do I still have to grab sep and bb from 14.4? I think I did right
@vivid nova u should probably edit the dimentio message cuz it doesn't say what repo to get it from
tru
And I wanna start fresh should I rootfs first
unc0ver, just how I remember it
@valid adder I prefer checkrain but i went with the 11 pro should've done xr
last time I jailbroke was with checkra1n, haven't kept a jailbreak more than 5 minutes since october
I just don't jailbreak
Did anyone try to futurerestore to 14.2 on A13?
I think after I go 14.3 ima reset my gen so it's the 0x11
@scarlet thistle 14.2 works if you come from 13.x
Im coming from 13.5, iphone11 pro
so should be fine
Which tutorial to follow?
just use correct 14.2 blobs, 14.2 ipsw and --latest-sep --latest-baseband -u and futurerestore v194
@scarlet thistle does your phone randomly overheat?
Is it ok to restore itunes backup after i get to 14.2?
Only when using the cam
The tutorials are rough I spent 5+ hrs of reading. But I'm new to discord Lotta smart people here
@scarlet thistle with -u you wont lose app data, it will just remove tweaks
backup still just in case
but you wont need to restore from backup with -u
Ah ok thanks, which tutorial to follow?
@valid adder you can keep app data? Cause I know I loud 13.5 can't be restored to 14
@scarlet thistle there's a couple floating around I kinda meshed three of them but also you don't need to manually set sep and bb
Will link in sec
i just thought i'd test it because libipatcher support is included, futurerestore 194 currently doesn't work on 32-bit devices btw, it has that ecid reading bug.. though i've seen a fork/commit by dora2ios where it may have been fixed: https://github.com/dora2-iOS/futurerestore/commit/21206f238863ec10a042a2a469e4f9e2c2c77208
i'll compile and try with it merged sometime later, will be doing other stuff for now
tsschecker still broken
also
getscab
broke
when tihm added oddy64
getscab is for img3 ecid
hence why u get that error @night harbor
either the blob is invalid
@scarlet thistle https://www.reddit.com/r/jailbreak/comments/lrgar6/tutorial_updating_an_a12_device_to_143_with/?utm_source=share&utm_medium=ios_app&utm_name=iossmf
or futurerestore getscab is broken
So this one @valid adder ?
And actually I don't have to rootfs by going to 14.3 does that get rid of all current Cydia tweaks in off chance a tweak causing overheat issues
yes
I haven't seen a straight a13 tutorial yet that's what held me back
oh, didn't know more stuff's broken.. i think the blob is fine, i can still use it with the old futurerestore
theoretically, if I fix 14.2, you can restore to 13.7 with baseband hax
@night harbor check the blob with validate
You can go from 14.2 to 13x!?
@night harbor what did you use to save blobs I've been using shsh host
but somewhere down the line futurerestore broke
and broke restores to 14.2
@pearl fog nah it aint like that
i use shsh host also, but i mainly use tsschecker manually
I've tried every version of tsschecker, validate command says invalid but validate command says my old 32bit blobs are still valid @night harbor
my old blobs were saved in 2018 with tsschecker during downgrade party
Oh shit
I got 13.5-current
still invalid like before
./validate iPhone4,1_8.4.1.shsh2 BuildManifest_iPhone4,1_8.4.1.plist
ERROR: Blob for LLB is invalid (crypto)
ERROR: Blob for iBSS is invalid (crypto)
iPhone4,1_8.4.1.shsh2 is BROKEN
i'll try
When I try to get my iPad 5 in ipwndfu for futurerestore, it fails.
when I run sudo ./ipwndfu -p.
luckily I master all aspects of the restore not just stock bootchain
so I know 32bit pwned, 64bit pwned and 64bit stock restores with fr
I will be able to fix the bugs for all those types of restores
sudo ./ipwndfu -p says it didn’t enter Pwned DFU.
@night harbor
old blobs
look at the difference
they are saving so weird now
wtf
yea that's what i would expect.. are those blobs the downgrade party back in jan 2018? i may have some of those to validate
Why doesn’t my iPad 5 enter Pwned DFU?
@night harbor ?????
what on earth
why are they saving so different
right is the valid blob
yeh jan 2018
@valid adder it worked, restoring to 8.4.1 with the OTA blobs
haven't updated it in a while
Version: 7895a76c8ac57e45b87bb756e6d8a617740aab62 - 317
libfragmentzip version: 0.60-120447d0f410dffb49948fa155467fc5d91ca3c8
Heyo, running into some issues here. iPhone 11 (iPhone12,1), iOS 13.5, unc0ver 6.1.0.
Trying to future-restore to iOS 14.3 RC (18C65) with valid blobs. Using the Version 194.
Tried future-restore with this tutorial from the pinned messages of this channel. #futurerestore-help message
Got the iBEC error (am on windows 10), so i downloaded that old itunes version from another pinned comment, and am now getting passed that (CLI spits out a few more lines).
I have attached the CLI / CMD output as a logfile. Line 255 and 352 seem interesting. I am not seeing the green background mentioned in 352, and i have to get my device out of recovery mode with the appropiate command line args afterwards.
Can dual boot into linux if needed.
Appreciate any help i can get!
you have to follow the exact same steps again
oh, i use the precompiled tihmstar 304 binary for the mac
driver uninstall
you’ll notice the reddit post mentions error 10
this is error 10
@night harbor all the mac ones are saving invalid 32bit blobs
all driver + itunes + apple uninstall,
reboot windows
install old version,
reboot windows
try again?
will do, thanks for the help. Must have missed that reddit post....my bad for not checking further.
@twilit quarry did you try my screenshot version
what exactly are you refering to? I most likely did not.
Oh thank you so much!! Hopefully I can get this fixed asap
not iBEC error
the linux one?
Between these two
You should be able to fix it
will do in a minute and get to you! Might just take some time, im working from home. Appreciate the input and help!
Thanks so much.
ohh.. that might be a problem, i can't compile mac versions so i use the precompiled ones publicly available
@lilac wren you’re welcome, my sister has kindly let me use her phone as a testing device which had blobs for some weird reason so I can test a full restore often if you need me to
It’s A9 and she dont bother with jailbreaking so i should be good
Yay that's great! Tell her thank you :)
Can a11 go to 14.2 yett
@lilac wren whats the status on the gui?
Sorry for asking if it feels like im pestering you
no worries, so log is still lagging/getting stuck idk why, that's the major issue I need to fix. everything after that should be just feature additions
- [ ] Fix IPSW regex being mismatching
- [ ] ibec error
- [ ] ap ticket mismatch
- [ ] Download futurerestore from m1sta fork
- [ ] Un Grey out the start button on exception
- [ ] Fix progress bar for sending filesystem
- [ ] Add confirm popup to stop futurerestore (unsafe)
- [ ] Make log send things, not just all at once at the end (half complete)
- [x] Ctrl-c button to stop futurerestore
- [x] Only allow one to run at a time, change button to “running…”
- [x] Autoscroll jank on windows
- [x] Parse recovery error
- [x] Fix glitching window
- [x] Dark mode for windows
- [x] Dark mode for Mac
- [x] Add actual GUI for current tasks
actually check off parse recovery error
and autoscroll jank on windows
and only allow one at a time
and ctrl c button
Is there a futurerestore announcement thing I can sign up for?
Announcement such as?
Like fixes or releases
Watch the repo
Seems like there is an update for macos.. hopefully this resolves the issue. If so, I successfully futurerestored from 13.5.1 to 14.3
Alright, I've been trying to restore since my last post and it hasn't moved one bit
Sits at the pie chart progress bar location and on my phone it says restore in progress
Still is sitting, if anybody has any ideas I'm open to listen. I will keep updating the thread. The storage at the bottom of Finder/iTunes has not changed either.
So it's definitely moving, just ridiculously slow. I guess I'll wait it out.
wdym by ibec error here?
I mean parse ibec error and link to them the guide on how to fix it
i can parse it rn, just need to link it in a dialogue
by the way, when it was "sending filesystem", was there an ascii progress bar or was it through the GUI?
oh yeah it froze, i forgot
ok ty
next time i’ll do a screen recording of the entire restore
will let you know when the next build to test is, tysm again
alr
that would be amazing, thx
np
It's continuing to move, but extremely slow still. Hope this isn't for nothing.
🤣
can i use my shsh2 blobs to upgrade from 13.5 to 14.0.1 on my 11?
no
usb 2 speeds
how come
It's never gone this slow before though?
Like 40gb
oh
48.6gb
Should the storage bar at the bottom of iTunes/Finder be changing during restore?
thats just an evaluation of your storage isnt it
i dont think it changes until you resync
That would make sense. Oh and my USB ports are USB 3...
the cable is 2.0
sending file system 👀
Repo is default
Succeeded Restore
Thanks everyone who helped me yesterday with the commands and steps to follow you all are legends
no its 1conan repo
anyone with “APNonce not match” on A13 has solution to FR from 13 to 14?
set your generator
the problem is i’m forgot the generator that I use before lol
I'm pretty sure if you search it up on a fresh jb, it'll be there
i did that
iphone 6s fresh jb with checkra1n
didnt come up
Who wants to test iRestore?
I dunno if i6 will work.. I couldn't downgrade i7 because fr has issues
Ah, okay.. I'll prep it for beta testing later on today
alr
Had to fix a couple GUI bugs
We're still at it. Almost to 50% lol 2.5 hours later
is your os on a hard drive
if i saved 14.4 blobs after setting nonce with u0 6.0.0 is the generator still 0x1111111111111111
I tried jumping from iOS 13.5 to iOS 14.2 on my iPhone 8 Plus A11, but I had no luck unfortunately. I tried numerous tutorials on my Mac, but I just couldn't get it to update. But I know you stated you're looking into it
when did u try this?
I tried this about 2 days ago, following the two tutorials I came across on reddit
what were the errors
FDR unfortunately
rip
I know, it sucks
can he upgrade and then downgrade?
Or do you have blobs for 14.3?
Unfortunately no, I thought that TSS Saver had saved them. I came to jailbreak the other day to then realise the iOS 14.3 blobs folder was empty. I should of checked really, but I've heard it's had some issues lately
Oh gotcha. Whats the FDR error?
Think it's unsupported software version
fdr is just sep bugging out
@valid coral You're updating?
restoring from a backup
That's it, my bad. I had read that somewhere myself
I was on 13.5.1 and tried to futurerestore to 14.3 and it didn't work the first time. I had to restore to factory default, set nonce and downgrade to 14.3, i'm currently trying to restore my backup
Yeah.. Be careful with that
A handful of users are trying to restore from backup, but iCloud settings gets stuck
Which leaves them in this loop
starting the restore now @vivid nova
Does it matter if it's a iCloud backup or a computer hard drive based one?
I don't think it does. The user reported using iTunes
I'd imagine iCloud is just as bad if not, worse
@vivid nova you have to do all this twice right? cause you have to do this from recovery mode too
Do what twice?
So when is it getting stuck? At what point? Because I've been waiting 3 hours for my backup to restore and I'm just over halfway
It gets stuck during the iCloud registration
So when you restore from backup and it connects with Apple to verify
this is why you use -u
Guess i'll just pray to be one of the lucky ones
what does -u do?
update
it tells futurerestore to keep the user data
^
when upgrading/downgrading
Oh gotcha
@vivid nova log output stuck here, though this probably is a futurerestore thing
its sending the filesystem but not saying anything about it
progress bar under apple logo is around 30%
Yeah, it's not the program, it's fr
Fr for Windows is still iffy
cause cmd dont play well with command prompt things
restore still going good
never mind i just pressed enter
@vivid nova bootlooped
not even a proper error
just
"Unable to restore device"
Filesystem validated
Sending filesystem now...
Done sending filesystem
Verifying restore (14)
Got status message
Status: Fail
restore-step-error = {0x1107065B:"[0]D(failed to invert APFS image)"}
[16:14:34.0282-GMT]{4>6} CHECKPOINT NOTICE: (NVRAM set) restore-step-user-progress=53 [sync=true] (first failure)
[16:14:34.0283-GMT]{4>6} CHECKPOINT FAILURE:(FAILURE:14) RESTORED:[0x0677] perform_main_os_prepare [0]D(failed to invert APFS image)
Safe to upgrade 13.5 unc0ver to 14.2 on A13 (iPhone 11 Max)? I read an reply earlier that it´s ok. Are the Futurerestore GUI putting the phone in recovery mode so that it can be in jailbroken state when starting the upgrade?
@zealous bridge again.. Fr not the program
As for myself, i had issues with i7
Told me sep is basically incompat
But 187 worked
Would it make a difference if I was able to set my iphone as a new iphone and connect it to my icloud account?
i didnt restore with a mac
i restored with windows
everything was exactly the same
something went wrong with this particular restore
same ipsw
same blobs
again it could just be futurerestore
but how did it work last time
Possibly.. Knowing Apple they patch anything
The program just provides the commands. 99% of the work is fr
I was able to do that so maybe it will work. Well, after 3 hours, my phone got disconnected during the restore. FML. Trying again...
well something went horribly wrong
Oof
You could possibly retry?
im gonna do a vanilla futurerestore cli first
then i'll test again
well tbh
i was restoring from 14.2 to 14.2
with -u
did that fuck up anything?
before was 14.3 to 14.2
I doubt it.. But fr needs more love imo
What fr are you using that worked? From what source?
Yeah, so it should be fine
clearly not
Wonder if it's a network issue..
dont think so
Like maybe Apple is patching
what does network have to do with sending filesystem
im guessing maybe
it was sent incorrectly
it doesnt verify the restore
so hash errors
maybe its just this one time
idk
oh here we go
same stage as last time
just with itunes
this isnt a dfu restore tho
verified successfully
restoring baseband now
imma try restore with linux acc
still vanilla fr
aight back to 14.4
Don't think I really need to include more do I?
also funny bc you'll never actually see this popup on Mac lol
Cool
^ so they dont panic
@lilac wren instead of copy link.. Go to link
ah yeah
Can we use futurerestore to move from 14.4 > 14.2 iPhone X?
really? with what soc?
A9
I know 14.3 is working but I don’t have those blobs
Ah😭
lmao
you laugh and I cry, I cry a lot. the days that I was muted the night I did not sleep
ok nice it now opens link in default browser
bro losing a jailbreak is not the end of the world
no need to be so dramatic
a jailbreak will come eventually
you are right. let's say that to me it essentially only needs to record calls and for safari plus
gonna try linux futurerestore back down to 14.2
Why are you using Linux?
Alright, so i restarted my macbook and iphone to see if it would increase the speed and it worked. So it's already done restoring backup and I'm currently sitting at the apple logo with the progress bar
"Updating iCloud Settings..." was successful!
bc why not
i wanna do a vanilla futurerestore
as a control for your gui
fuck forgot to set nonce
14.4 down to 14.2 with -u
Found out that despite FR failing.. The nonce is still set
Well, you gotta set it
found that you can just ctrl + c futurerestore as soon as it enters recovery
so you dont have to wait for that error message
Indeed
here we go
alr sending filesystem
this is what fucked up last time
why are there FDR errors in the middle of a progress bar
I know 14.2 (A11) gives FDR issue (but some have reported success) - question : what is involved to get it to work "properly" ? (just curious what needs to be done - for my own knowledge)
Looks okay to me @zealous bridge
Apple needs to stop being drunk
alr we're past the point that it failed last time
restore successful
how to open fututrestore on windows
?
have to run in command prompt
what? isnt there a futurerestore.exe?
yes
That option is coming soon 😉
oh how i do that?
no
oop
there we go
control test done
do you want me to try again with iRestore?
@vivid nova
Sure
uh
checkra1n is segfaulting
wtf
literally just used it
how do i fix this
gonna run sudo apt upgrade
this is a11 going to 14.2
a9
@zealous bridge stuck on this
bro why do no one ever read the notes
uninstalled apple iboot driver completly after but when i run the command when the driver is gone it doesnt detect my device
yes
because you have to
unplug
and plug in again
BRO
IT DOESNT WORK FROM TERMINAL
BUT IT WORKS IN THE APP
wen eta make sense
Gl
in restore mode rn
If it fails, i blame op
windows does workkk tho
It does, but is stubborn
alr
well
30%
this log keeps getting stuck
imma restore with linux from now on
i want to know whats going on
VERIFIED RESTORE
guess it was a one-off
your GUI technically has a 50% success rate
That make zero sense
That's like saying an atm has a 50% success rate compared to the bank
Its written that when using -u i shouldnt be using it if im updating from jb frimware and im currently on uncover 13.5
yeah don’t use it if you’re jailbroken
i deposited some money at an atm the other day and that shit just kernel panicked
literally lost it
smh my life
dumb bank using unc0ver

it doesnt do anything but restore rootfs
doesnt affect the restore itself
but there’s still shit all over /var
considering i’ve done it three times already today
just prefs
they persist throughout itunes backups
theyre fine
lmao
it does sound bad but it definitely isnt
i think im making people jealous... restoring to 14.2 three times in a day
You withdraw in atms bruh

Ha, okay

If I have all blobs and necessary device requirements, is FR and unc0ver compatible with ios 14.3RC(18C65)
yes
I’ve heard FR is a hit or miss with A12 to 14.2 but is fine with 14.0-14.1. can anyone confirm
FR is completely broken on 14.0-14.1
wow thanks
Is it safe to try futurerestoring to 14.2 on A13?
not safe
Or will I end up in a bootloop if it fails?
That's fine as long as I don't have to upgrade to 14.4 I guess
Bootloop is always possible
Futurerestore can be buggy sometimes
Just not common
might try upgrade to 14.2 if this is the case
Alright, do you think it's going to become better or will I have to gamble sooner or later if I want to upgrade to iOS 14?
Would say around 50/50
is there a fix for this ?
What device and what version are you restoring to?
iphone 8 global on 14.4 atm trying to go to 14.2
14.2 restores are broken from 14.4
will 14.1 or other version work?
let me know if it works for you
will do
just tried going from 14.4 to 14.4 to test out if FR is working at all. ubuntu and it's not working (no green background). 14.4 > 14.4 on iPhone 8 with generator
whats the error code here
segmentation fault on arch. The ubuntu is a kvm instance and everything is compiled from source
Gonna be trying out windows but I suspect the same error
Just restored on kubuntu from 14.4 -> 14.2 and worked just fine
iPhone 8?

