#futurerestore-help

1 messages Ā· Page 71 of 1

green onyx
#

@light yew also make sure u have the correct ipsw

light yew
#

I do

green onyx
#

alright

lilac wren
#

Wait how is it different

light yew
#

iPhone10,3,iPhone10,6_14.2_18B92_Restore.ipsw

green onyx
#

just theres no buildidentity stuff

light yew
lilac wren
green onyx
#

ah i see

lilac wren
light yew
#

Thats the full one

light yew
lilac wren
#

It should be

light yew
#

Ok

#

DFU or recovery?

green onyx
#

recovery

lilac wren
#

^

light yew
#

ok

#

1 sec

#

FUCKKK

valid adder
#

this is normal

light yew
#

Its booted at least again fewww

valid adder
#

14.2 is hit or miss

#

it didn't even fail...

#

because restore didn't even start...

light yew
#

Im trying another cable

#

Dont trust this one no more

valid adder
#

if it works

green onyx
#

probably wont work again

valid adder
#

it works

#

if it doesn't

#

14.2 wont work at all

light yew
#

I tried the 1st blob

#

Btw

#

i have a second one

#

That was in the conan folder

#

Should i trie to use that one?

light yew
#

Sorry

#

I do understand you

#

It doest work

#

Thats the think

#

Ill give it one more shot and see

#

I think that we can conclude that 14.2 ain't working with future restore.

#

Right:

#

@lilac wren

lilac wren
#

Yes

light yew
#

It goes further when manually putting it in recovery

#

But as soon as it wants to write to nor

#

Boom out

valid adder
#

@light yew I literally said it doesn't work what more do I need to say????

light yew
#

I understand

#

Would love to know whats causing it to not work

#

Thats the thing

valid adder
#

like I said a 1000 times

#

its an apple problem

#

some people can go to 14.2 and lower

#

others cant

#

nothing you can do to fix it

light yew
#

I also have the 14.1 blobs

#

Will give it a shot

valid adder
#

I guess reading is not your strongsuit

light yew
#

Just stuborn you know šŸ˜›

#

Wanna try

green onyx
#

if it doesnt work once, it wont work again

#

@light yew are u going from ios 13?

light yew
#

13.5

#

I never tried 14.1

#

Just 14.2

#

Its now getting the IPSW

#

14.1

#

Lets see

valid adder
#

13.4 - 14.2 will have the same effect

#

if it doesn't work

#

they all won't work

light yew
#

Yup same

green onyx
#

exactly

valid adder
trail grotto
#

With 14.4 not signed, does it change anything for us preparing to get to 14.3 for Tauren release

lilac wren
#

no

untold gull
#

Ipsw.me still shows 14.4 as signed for XS Max. Is it incorrect?

lilac wren
#

probably

untold gull
#

14.4.1 sep and bb should still work to take XS Max to 14.3 correct?

lilac wren
#

yes

untold gull
#

Thanks for reassuring 😺. I had just finished taking iPad Air 2 and iPhone 6s to 14.3 with 14.4 sep/bb and was just about to start the XS Max. Will grab 14.4.1 parts and get it done

lilac wren
#

just use --latest

serene ledge
#

Was looking at marijuanARM's futurerestore github, and noticed the -u says "DO NOT use this parameter, if you update from jailbroken firmware!"
Thought it was alright to go from in my case 13.5 JB and update with -u to 14.3

#

rootfs before futurerestore i guess?

lilac wren
#

I think you're fine, others have used it—just rootfs and rejailbreak before you go

serene ledge
#

sounds good. my thoughts were conflicting because I thought I needed to be JB to have my generator set

lilac wren
#

I think you can rootfs and have generator set but nobody does that

serene ledge
#

figured. thanks!

lilac wren
#

np

untold gull
#

I’m ā€œold schoolā€, prefer to get the components manually. It’s always worked for me since 11.3 on 4 different devices, why change now

lilac wren
untold gull
#

šŸ‘šŸ»

valid adder
untold gull
#

Curious what would happen if I tried the fr command using unsigned 14.4 components. Would I be forced to restore and lose my JB, or would it fail gracefully and give me another chance?

lilac wren
#

I think it just fails bc it can't get a signature

#

It doesn't start restoring

valid adder
#

it will fail to fetch tss lol

#

the manifest is what is used to fetch tss

#

tss is hash digest locked not iOS version

untold gull
#

so if I use --latest-sep and --latest-baseband I don't specify BuildManifest's?

lilac wren
#

Yes

#

You don't

lilac wren
#

@zealous bridge I feel so relieved, I think the futurerestore gui logs lagging was only an issue for you (like you said I just blamed it on the gui anyways). Saw two people do it and it looked completely normal, one was on Mac and one was windows. Makes me feel a lot better lol

midnight basin
#

@solid basin A A RON!

valid adder
#

Well someone is getting warned for useless ping

lilac wren
#

@​Cryptic C R YPTIC!

vivid nova
#

@valid adder

#

Hi

zealous bridge
#

tho this also happened

#

so im not sure if its just me lmao

finite abyss
#

guys

#

Checkra1n 14.3 RC

#

password not working and touchid and stuff all fixed

#

im running 13.3 on ip8+

#

apparently 14.1 and all is compatible

#

so im assuming its fixed?

vivid nova
#

@finite abyss mf is comparing iOS 14.1 to tvOS 13.4

finite abyss
#

huh

#

no

#

LMAO

#

i just picked 14.1

#

its not some comparing shit or anything

vivid nova
#

okay? but what's your Q? 'cause it's compatible

finite abyss
#

no its compatible

#

but i remember people telling me touch id and all that shit wont work

#

on 13

#

14*

vivid nova
#

that's for checkra1n

#

has nothing to do with downgrading

valid adder
#

noobs

finite abyss
#

cuz i hvae blobs for everything from 14-14.5 beta 2

#

no im just asking

#

so does checkrain still have that issue

#

cuz i wanna be jailbroken on 14

vivid nova
#

yes

valid adder
#

its not an issue

vivid nova
#

but u0 works

finite abyss
#

oh ew

#

unstable for me 90% of the time

vivid nova
#

i need an @finite abyss ...

valid adder
#

its not an issue, you need sep exploit for it to work

finite abyss
#

oh okay uhm

#

so has it been found

valid adder
#

?

finite abyss
#

wait wait im still dumb on this topic how did u0 manage it but not cra1n

vivid nova
#

bruh

valid adder
#

u dumb?

#

checkra1n jailbreaks before theres even a kernel

#

u0 is a kernel jailbreak

finite abyss
#

i literally don't know half this shit

#

i just know checkra1n uses a bootrom exploit and u0 another type

vivid nova
valid adder
#

apple added mitigations with iOS 14 locking bpr in sep

vivid nova
#

before asking Qs

valid adder
#

bpr is the boot process register

#

tells device what mode it booted from

#

meaning checkra1n cant boot the os anymore

#

because sep controls bpr

finite abyss
#

okay

valid adder
#

this was bypassed on a10

#

because of sep exploit

finite abyss
#

aye ur a legend for explaining ty

valid adder
#

no exploit for a11

#

yw

finite abyss
#

okay that sucks huh

#

so is there a future where it an SEP exploit might be found?

valid adder
#

undoubtedly

#

not likely

finite abyss
valid adder
#

no

finite abyss
#

so due to that you can have the A11 BPR skip but you will lose password functionality and all that good stuff if im not wrong?

vivid nova
#

if you want a jailbreak, get a X.. it's kinda like a 11/12.. just slower and fewer cameras

valid adder
#

checkra1n can boot, but user data isn't decrypted

#

hence why removing passcode works

#

cuz no encryption

finite abyss
#

OH

#

so its acc more vulnerable

#

so you have to remove passcode

#

or else user data is undecrypted

#

huh

valid adder
#

hence why I don't jailbreak

finite abyss
#

understandable

#

man ur a legend for dumbing this down for me

#

thank you so much

valid adder
#

yw

finite abyss
#

has u0 on 14.1-14.3 been stable for any of you all?

valid adder
#

never used it

#

I only will jailbreak if I can use procursus bootstrap

vivid nova
#

it's not about what OS.. but what you install

carmine walrus
#

Anyone had success trying to FR to 14-14.2 on A11 anyway?

valid adder
#

did u send log

#

I don't remeber

#

well its a mystery why some devices can go to 14.2

#

but others cant

lilac wren
# zealous bridge tho this also happened

I never actually tested a full restore, logs always lagged at the beginning of the process but then went smoothly for me (up until the error bc I wasn't actually going to restore). I thought that was a sign that logs were going to lag throughout the whole thing but maybe not

lilac wren
worthy trail
#

HI

#

Iphone XS Max IOS 13.5 getting an error when restoring to IOS 14.2

#

what=Device ApNonce does not match APTicket nonce
code=44498961
code=44498961
line=679
file=futurerestore.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:
Done: restoring failed!
FutureRestore process ended.

lilac wren
#

did you set your generator

worthy trail
#

Yes generator set

#

0x1111111111111111

#

same on my shsh

lilac wren
#

how did you set your generator

worthy trail
#

Дonfigured with uncover, odyssey and Generator auto setter.

#

And I always get the error

dull swallow
#

@worthy trail did you save your blobs specifically for that apnonce

worthy trail
#

I have blobs saved from IOS 14.2

green onyx
#

use dimentio

final remnant
#

i thought A11 and up could only update to 14.3 and above

lilac wren
worthy trail
green onyx
#

u probably saved ur blobs wrong

valid adder
#

Nah u need Conan repo

worthy trail
green onyx
#

valid != saved properly

worthy trail
#

Where else can I check blobs?

#

SHSH2 is valid!

lilac wren
#

!= = ≠

#

≠ = "is not equal to"

worthy trail
#

SHSH2 is valid!

lilac wren
#

sigh

worthy trail
#

Then rollback on IOS 14.2 does not work for my device

green onyx
swift elm
#

Couldn’t Apple simply update SEP (disallowing for a passcode) and / or BB (if applicable) every iOS update instead of intermittently as is the case now to mitigate this. Maybe there’s some kind of technical reason why they don’t prevent replay attacks for iOS but if they cared about limiting jailbreakers; it doesn’t seem too hard to make all SEP / BB updates require matching iOS firmware, right? ThinkingMario

Or did you find out anything new out about this since @lilac wren asked their question?

green onyx
#

also

#

ios is changing updates

#

theres going to be mainstream updates

#

and security

#

so idfk if blobs will only work with mainstream

#

or will there be security update blobs

#

or smthn

valid adder
#

That’s not there intent

#

They don’t know about half of this stuff

green onyx
#

ah i see

lilac wren
lilac wren
swift elm
swift elm
golden meadow
#

does futurerestore work on A11 with blobs for 14.1

green onyx
swift elm
#

I’m thinking of doing a pull request on AltServer to detect the conditions of and automate as much of the TSS blob saving as possible for whatever device. So I’m learning all I can about this right now. Just started jailbreaking as of this week to test out AltDaemon and honestly, jailbreaking is fun af. I can’t believe I thought I was only going to use it for AltDaemon testing.

lilac wren
swift elm
#

@lilac wren Your write-up was wonderful in my jumping into this world to see if it’d make a good candidate as a PR for AltServer.

lilac wren
lilac wren
#

*while connected to the phone

swift elm
swift elm
#

And AltServer uses the same libraries needed manually to get all the data needed – I just need to make sure it can detect the phone is in a jailbroken state (for A12 and above) to display the option to ā€œAutomatically save all future blobsā€ to our users.

lilac wren
#

is it even necessary to do it with altserver then? the phone can do it all by itself as seen with System Info / shsh.host, or TSS Saver by 1conan. Is altserver just for checking new firmwares and saving SHSH in the background?

lilac wren
#

and dimentio?

swift elm
# lilac wren is it even necessary to do it with altserver then? the phone can do it all by it...

The feature I’m imagining automates (most of) the one-time manual process needed for A12 devices and above (if it detects they’re jailbroken), otherwise it’ll grab all the necessary info during its initial install of AltStore and just make sure it saves new blobs whenever Apple starts signing a new firmware for every device that’s ever connected to that AltServer before.

swift elm
lilac wren
# swift elm And for the generator for A12 and above, I have to detect the JB and assume the ...

hm ok, although know that depending on which way you go about this, you'll need to go into recovery on A12+ for getting AP Nonce which is kinda bad if they have to go out of their way to do that. Also know that people who use AltStore are usually not jailbroken at the time of installation, meaning their AP Nonce is going to be randomized and you won't know (if you don't read generator)

#

if you decide to usbmuxd, then I'd just read generator as well, doesn't take too much extra work

swift elm
brave comet
#

I just tried to use futurerestore gui to update my XR from 13.5 to 14.3 but got an apticket apnonce mismatch error

#

this is the first time I'm not just using itunes to update so I'm very confused

brave comet
#

how do I do that?

swift elm
lilac wren
swift elm
brave comet
#

so should I exit recovery mode now?

lilac wren
# brave comet how do I do that?

Download [[dimentio]] through your package manager from 1conan repo, then look in your blob to see if there's a generator, and do dimentio [generator] on your iOS device's terminal

mystic axleBOT
#
dimentio

PoC tool for setting/getting nonce without triggering KPP/KTRR/PAC. (requires tfp0)

Author

0x7ff

Version

2.0.0-1

Price

Free

Repo
Bundle ID

com.0x7ff.dimentio

More Info
lilac wren
#

Yes exit recovery

lilac wren
swift elm
lilac wren
#

Don't know of it's still up to date

swift elm
brave comet
#

I had already restored rootfs so I'm rejailbreaking now

swift elm
#

Okay, I think I’ve got it down. For A11 and below I can simply grab all the data needed during initial AltStore install.

A12 and up will save the blobs on the first time a user connects their device in jailbroken mode and AltServer can read the generator.

This makes it perfect for completely automated blob saving.

As to how to convey to users that their blobs are saved and they can use future restore with them would depend on their current firmware which AltServer will also detect.

#

Is there a master DB / list that is actively maintained of BB and SEP compatible with which iOS versions that AltServer could draw on to display only relevant options to the user?

lilac wren
lilac wren
#

But if you really want, ping JTV and ask if he has an API

swift elm
#

I’ll have to find and ask this JTV individual then.

#

A lot of our user base is jailbreakers.

lilac wren
#

Don't take this the wrong way but that seems a bit silly, that's really not what AltServer is made for I think. Even all blob savers such as blobsaver, TSS Saver, shsh.host/systeminfo, none of them have sep bb compatibility checking because it doesn't matter

swift elm
# lilac wren Don't take this the wrong way but that seems a bit silly, that's really not what...

You’re right that it’s not made for that. But I don’t see the harm in removing blobs from users view that are no longer relevant (I won’t delete them in case they become relevant later but I won’t display them either). I’ve got approval from Riley to PR this so I’m glad you’re wanting to work it out with me. I at first only wanted this for our JB users. But now I kind of want it for myself.

valid adder
#

Hence why the fortnight bug happened

lilac wren
swift elm
valid adder
#

They keybags became corrupted because the new sep handled them differently than the old sep when it did a key update for Face ID/touchid

#

It cleans every 14 days

#

A fortnight

#

So device bootlooped

lilac wren
brave comet
#

okay, I ran the dimentio command in newterm, should I now restore rootfs again and run futurerestore once more or is there another step?

swift elm
valid adder
#

Fix was turning off passcode or risking bootloop

lilac wren
brave comet
#

okee, thanks a lot, let's hope it works now

lilac wren
lilac wren
valid adder
#

That bug is long in the past

#

Now we can’t even begin the restore price

#

Process*

lilac wren
#

ah

#

ok thanks!

valid adder
#

that needs to be fixed first

peak flume
lilac wren
#

yes it looks accurate

peak flume
#

I guess it's really just a tutorial for the GUI fork

lilac wren
#

Step 8 says

Enable the Update (-u) checkbox
@green onyx always said make sure you have the "updateinstall" in your blob before doing it but idk

peak flume
#

hmm

green onyx
#

yes

#

open ur blob with notepad

#

ctrl+f

#

search updateInstall

#

if u can find it, u can use -u

#

if not, u cannot

lilac wren
#

do you have a source folky

green onyx
#

uh

#

tanbeer

#

lol

lilac wren
#

oh lol

#

SOURCE

foggy solar
#

How do i restore if i didnt save blobs

lilac wren
#

itunes

foggy solar
#

ok

peak flume
#

idk what that actually means but I will check the box for -u in the gui

lilac wren
#

if you check the -u box your data will be preserved as if you updated

green onyx
#

instead of restore

lilac wren
#

I would always restore but it's up to you

peak flume
#

How come?

green onyx
#

im going to use fr again from 14.3 to 14.3

#

when taurine drops

#

and im using the gui pog

lilac wren
# peak flume How come?

leftover junk and files, also unc0ver broke ota updates for me when I went from chimera to unc0ver to odyssey without ever restoring

peak flume
#

hm

#

would you also not advise restoring from a backup after restoring then?

lilac wren
#

yeah I'd start fresh

peak flume
#

So much work but you're probably right

lilac wren
#

only use iCloud for necessities like contacts and stuff

cedar onyx
#

Is iOS 14.4 sep compatible with 14.1?

peak flume
#

I don't wanna lose my photos

#

there are ways around that though I guess

green onyx
cedar onyx
lilac wren
green onyx
#

uh

#

what device

cedar onyx
#

X

green onyx
#

...

cedar onyx
#

Does it matter?

green onyx
#

yes

cedar onyx
#

Why

green onyx
#

its a hit or miss

#

from ios 14, doesnt work

#

from ios 13 sometimes works

green onyx
cedar onyx
#

why is it relevant on which version I’m on now, isn’t that related to the signed sep?

green onyx
#

no

#

like for example

#

A11+ is guaranteed to work on ios 14.3 and above but hit or miss for 14.0, 14.1, and 14.2

#

A10 and below can fr 14.0+

cedar onyx
#

I upgraded 11.3.1 to 14.4 two days ago, iPhone X

green onyx
#

why

#

would

#

u do that

lilac wren
#

LOL

cedar onyx
swift elm
green onyx
celest basalt
#

In the first blob in the 14.3 folder on TSSSaver, I searched updateInstall, and it showed up.

lilac wren
#

although this isn't 100% correct bc of ≤14.2 on ≄A11

#

you could just make your own API honestly, JTV does it all manually

celest basalt
#

In the first blob in the 14.3 folder on TSSSaver, I searched updateInstall, and it showed up.

#

What does updateInstall in a blob mean?

sinful spade
#

it means it has an update ticket

#

so you can use futurerestore without wiping your data

cedar onyx
#

It’s iPhone X

green onyx
#

true

#

but i didnt know if u had 14.3 blobs

#

bruh

swift elm
# lilac wren you could just make your own API honestly, JTV does it all manually

Oh, sweet, I missed that! I have no problem making my own API but I’d have no choice but to manually add the compatibilities. Maybe I could discuss this with JTV and see their process when I get to the end of the pull request and add this info.

@vivid nova, tho, should definitely be made aware of the 14.2 / A11 detail(s).

#

Thanks for all your help in this and the Reddit post which inspired me to do this pull request in the first place. happyvolnutt

cedar onyx
#

This is why I asked about the sep

#

Is 14.4 sep compatible with 14.1?

cedar onyx
#

I didn’t get what you didn’t get lol

cedar onyx
lilac wren
#

doesn't really matter because you can just not proceed

green onyx
#

^

#

fdr error isnt fatal

cedar onyx
#

Ah got it

#

So I can just —latest-sep and it will throw me if not compatible, good to know

#

latest sep is 14.4.1 sep but I heard it’s identical to 14.4

green onyx
#

yes it is

cedar onyx
#

Great thanks

#

I’ll update here if it is in fact supported on 14.1

robust warren
#

I am on 13.5 IPhone X without Blops for 14.3. Is it possible to upgrade to 14.3 without blops since it’s no longer being signed? Can I do this through jailbreaking somehow?

lilac wren
#

no

robust warren
#

So I can’t?

lilac wren
#

you can't without blobs

opal plank
#

Hello I am trying to do a restore from 13.5 --> 14.1 using an iPhone 8.

#

No luck.

#

It starts restoring with the bar and then fails, is this even possible to upgrade from 13.5?

lilac wren
#

what's the error

opal plank
#

Bear with me -- I will try to replicate

lilac wren
#

you can send the log here

opal plank
#

Done sending NORData
Cleaning up...
[exception]:
what=ERROR: Unable to restore device
what=ERROR: Unable to restore device

code=68026385
code=68026385
line=1038
file=futurerestore.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:
Done: restoring failed!

lilac wren
#

I don't think you can restore then

opal plank
#

I dont have 14.3 blobs unfortunately 😦

#

How come?

#

It isnt a big deal anyway - I can stay on 13.5 -- Just wanted to try

lilac wren
#

something about SEP I think

opal plank
#

Its strange sometimes I do it and it fails early on -- other times it nearly finishes the process.

#

Would I see more success going to 14.5 and downgrading to 14.1?

#

(I am not overly fussed about losing my jb)

lilac wren
#

I don't think so

opal plank
#

OK.

green onyx
#

yep

#

its hit or miss

opal plank
#

If I try over and over can I get lucky šŸ˜†

#

It gets to around something to do with FDR I believe, then it starts panicking

#

I also get this message which confuses me at the start

#

I have 14.1 blobs and 14.1 ipsw??

lilac wren
#

nah you're fine

#

jank regex I always say "I need to fix that" and never get around to doing it

opal plank
#

I have successfully futurerestored wayback when using the normal future restore in terminal, thought id say myself the hassle and use the gui this time. No luck

#

Might try running it through windows

lilac wren
#

won't make a difference

opal plank
#

It fails at NORData

lilac wren
green onyx
#

if it doesnt work once

#

it wont work again

opal plank
#

Ah gotcha, read it all.

#

sorry for the hassle, thanks for the help

green onyx
#

np

opal plank
#

I assume this upgrade/downgrade will never be possible then?

#

Or is it something that could potentially be 'fixed' at a later point

carmine walrus
#

Hmm... I’m really debating trying this myself on my 8+

opal plank
#

I have ios 11 blobs and im still waiting for the spice unteather jailbreak to be made šŸ˜‚

opal plank
#

@carmine walrus If you have 14.3 blobs I think you're fine

green onyx
#

ios 11 blobs will never work

#

because sep and bb not compatible

opal plank
#

ah, gutted.

green onyx
#

wait

carmine walrus
green onyx
#

what ios version @carmine walrus

#

are u on

carmine walrus
green onyx
#

ah

#

go ahead and try it

#

14.2

#

fdr isnt fatal

#

if it doesnt work once, it wont work again

#

its worth a try

carmine walrus
green onyx
#

no

#

u will be on 13.6

#

if it fails

#

fatal means -> 14.4

carmine walrus
green onyx
#

non fatal means -> (no upgrade/13.6)

#

14.4 is signed

#

oh wait

#

it isnt

#

*14.4.1

carmine walrus
green onyx
#

alright

#

open ur blob with notepad
ctrl+f
search updateInstall
if u can find it, u can use -u
if not, u cannot

#

@carmine walrus

#

-u means upgrade

#

so u dont lose ur data

#

uh, most modern blob savers have updateInstall

carmine walrus
green onyx
#

yes!

#

so u can use -u

#

use frgui

carmine walrus
green onyx
#

no

#

wtf

#

u have to be jailbroken

#

to set generator

#

tf

#

u dont need to restore root fs to update

#

u need to restore root fs if u backup tho

green onyx
carmine walrus
# green onyx yep

In that case, I’m cancelling this backup lol and will post my log

carmine walrus
#

just want to be sure if this looks right

#

C:\Users\NAME\FutureRestoreGUI\extracted\futurerestore-v194.exe -t F:\futurerestore\5481104535511086_iPhone10,5_d211ap_14.2-18B92.shsh2 -u -d --latest-sep --latest-baseband F:\futurerestore\iPhone_5.5_P3_14.2_18B92_Restore.ipsw

lilac wren
#

looks good

carmine walrus
#

here we go! šŸ¤ž

green onyx
#

oh well, ye its good

carmine walrus
#

I copied the command from it

green onyx
#

just use the gui

#

its fine

#

dw about it

#

@carmine walrus screenshot of cmd?

lilac wren
#

it's fine if he uses terminal lol

carmine walrus
#

It disappeared lol

#

Using GUI tho

#

Verification Failed!

#

iBEC error

green onyx
#

oh

#

thats fine

#

@carmine walrus check pinned

#

if u used the gui

#

it wouldve given u instructions on how to fix

green onyx
#

copy command and run

#

@lilac wren visual glitch btw

#

i also had this

lilac wren
#

yeah

green onyx
#

but solved by restarting the gui

lilac wren
#

i'll fix

green onyx
#

alright pog

carmine walrus
#

"It's thinking"

#

now I get this

green onyx
#

wait

#

dont touch

#

just wait

#

perfectly normal

carmine walrus
#

gotcha

green onyx
#

wait

#

ye

#

just wait

carmine walrus
#

should I uninstall the Apple Mobile USB driver again?

green onyx
#

uh

#

follow the steps

green onyx
#

@carmine walrus how is it going

#

did u still get ibec?

carmine walrus
#

no ibec

green onyx
#

poggers

#

wait

#

whats the issue

#

@carmine walrus

carmine walrus
green onyx
#

how long have u been waiting

carmine walrus
#

~30 min

green onyx
#

fdr issue

carmine walrus
#

noooooo

green onyx
#

@carmine walrus ctrl + c

lilac wren
#

maybe logs truly are bugged

#

wait are you sure

#

send the screenshot

carmine walrus
#

worth a try

lilac wren
#

wait look at your phone, is it with an apple logo and is there a progress bar slowly moving under it

carmine walrus
lilac wren
#

it's in recovery mode?

#

hm

carmine walrus
#

then it restarts back into recovery after some time

#

on a loop

lilac wren
#

wait you were restoring to 14.0-14.2 on A11+?

valid adder
#

Yes iPhone 8 ^

carmine walrus
#

yes, from 13.6 to 14.2 on 8 Plus

lilac wren
#

is this what it looks like normally when it doesn't work?

#

I thought it would fully error out

carmine walrus
valid adder
#

This is the normal 14.2 error

#

-2

lilac wren
#

so it doesn't error out, it's just stuck looping like this?

valid adder
#

Idk lol

lilac wren
#

oh ok

valid adder
#

Different driver bugs

lilac wren
#

then I guess it's ok to stop futurerestore

#

because you are in recovery

carmine walrus
#

thanks everyone who helped

lilac wren
zealous bridge
lilac wren
#

oh ok ty

zealous bridge
zealous bridge
#

yay

lilac wren
#

why did it just go down...by 8

#

reddit is weird nvm

zealous bridge
#

997 for me

#

lmao

#

1k now

sleek wing
#

Is it possible to downgrade ios 14.3 to 13.7 or 14.3 to 14.0?

green onyx
#

no

#

14.3 to 13.7 is no

#

14.3 to 14.0 is yes if blobs and A10 and below

#

@sleek wing

cyan surge
#

Hi guys. Just wanted to ask if someone found a fix for fdr error

zealous bridge
#

No

sleek wing
#

my iphone is 11 pro max. Is there no method to go back to 13.7 or 14.0? I have all the blobs saved @green onyx

zealous bridge
#
  1. SEP is incompatible
  2. You need a jailbreak to futurerestore
zealous bridge
#

Why

gaunt mesa
#

@sleek wing we don't support piracy please stop mentioning that tweak

zealous bridge
#

Doesnt the bot DM

sleek wing
#

ok sorry

valid adder
zealous bridge
#

ik but for the average user wont really make any difference

#

bc i dont think thats fixable unless?

valid adder
#

idk yet

high rain
#

Hi! followed th guide from ios.cfw.guide restoring ip8 global fro 13.5 > 14.3 with blobs, firmware, etc

#

I get this upon launching FS

zealous bridge
#

As it says

valid adder
#

exactly what it says

zealous bridge
#

You have the wrong ipsw

valid adder
#

read the error

high rain
#

yep, but I have my 14.3 blob

#

and 14.3 firmware

valid adder
#

but your blob is not 14.3

#

its 14.3 RC...

high rain
#

both have 18C66 in the title

valid adder
#

thats a beta

#

weird

#

hmm

#

nvm

zealous bridge
#

Check the device

high rain
#

i got lotsa blobs\

#

sooo blobby

valid adder
#

link the blob file u used

zealous bridge
#

Did you download the right one for your device?

#

the ipsw should have your device identifier in the filename

high rain
#

ipsw filename iPhone_4.7_P3_14.3_18C66_Restore.ipsw

#

should i try the 14.3-ota or 14.3 rc blobs?

valid adder
#

I said link the file

#

I don't need the actual blob

high rain
#

ah

valid adder
#

just the filename

high rain
#

4614384957038638_iPhone10,4_d201ap_14.3-18C66_27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae.shsh2

zealous bridge
#

Make sure theres nothing in the futurerestore gui folder

zealous bridge
#

Sometimes it auto detects

valid adder
#

this ipsw u downloaded?

high rain
#

looks like it

zealous bridge
#

Is that the only ipsw you have downloaded?

#

Oh hold on

#

This is a GUI error i think

#

its detecting ā€œP3ā€ as the ipsw build

#

Try renaming the ipsw

valid adder
#

its valid

#

so you prob have the wrong ipsw

zealous bridge
#

No

#

Its a GUI error

#

iPhone10,1_14.3_18C66_Restore.ipsw

#

Rename the ipsw to this ^

valid adder
#

does blob have to be an exact pattern?

#

@lilac wren

zealous bridge
#

Its detecting ā€œP3ā€

#

as the build name

#

its def a parsing error

lilac wren
#

I just have a really bad regex lemme pull it up

valid adder
#

let me fix it

zealous bridge
#

Lmao

#

Renaming should fix it

lilac wren
#

.*?_.*?_([0-9A-Z]+)_

high rain
#

cool cool

#

let me check

#

thanks for looking into this dudes

lilac wren
#

That's the regex

#

Maybe make it take {5}

#

Since all build numbers are 5

#

Group 1 (the only group) is the build #

valid adder
#

@high rain did you rename your blob before adding it to the gui

zealous bridge
#

blob build is fine

#

it says it detected 18C66 which is correct

lilac wren
#

There's a way to read the build number from an actual blob right? I'm reading from name but there might be a better way of doing it

#

Oh this is the IPSW regex sorry I'm confused

valid adder
#

yes

lilac wren
#

[0-9]{16}_.*?_.*?_.*?-([0-9A-Z]+)_ this is the blob regex

valid adder
#

ipsw regex is borked

zealous bridge
#

Lol

lilac wren
#

Ipsw regex is the one I put farther above, I'll just find another way to read it

high rain
#

ok didnt get the error this time! currently in dfu mode waiting for device to disconnect

zealous bridge
#

Recovery*

high rain
#

right right

#

my bad

zealous bridge
#

nw

high rain
#

well

#

actaully, it failed because it was unable to put it into recovery

#

hah

zealous bridge
#

it’ll run again

#

just wait

high rain
zealous bridge
#

Hm

#

Run it again

#

Manually

high rain
#

so, to be clear, i need to rejailbreak, set the generator

#

and re-run?

zealous bridge
#

No

#

Just re-run

#

Dont touch the device

#

Leave it in recovery

green onyx
#

^

high rain
#

ApNonce does not match APTicket nonce

green onyx
#

[[dimentio]]

mystic axleBOT
#
dimentio

PoC tool for setting/getting nonce without triggering KPP/KTRR/PAC. (requires tfp0)

Author

0x7ff

Version

2.0.0-1

Price

Free

Repo
Bundle ID

com.0x7ff.dimentio

More Info
zealous bridge
#

didnt set generator properly

high rain
#

hokay, i will try again

#

thanks!

green onyx
#

use futurerestore.exe --exit-recovery to exit recovery

#

or use the exit recovery button

#

in the gui

lilac wren
#

.*_([A-Z0-9]{5}) this should work

valid adder
#

(.*?_.*?_.*[0-9]?_|.*?_.*[0-9]?)([0-9A-Z]+)_

#

this too

lilac wren
#

nah that's too specific imo

valid adder
#

true

lilac wren
#

ok done pushed compiled wrapped and released

green onyx
#

poggers

lilac wren
#

github has darkmode??

#

since when

green onyx
#

a long time

lilac wren
#

how do I activate it

green onyx
#

like 4 months ago?

green onyx
lilac wren
#

oh wow

#

ty ty

#

it says "new" and "beta" ok don't blame me

green onyx
#

ye

#

theres a new dimmed

#

damn

lilac wren
#

I love it, matches IntelliJ

green onyx
#

true

#

darkmode is super nice

#

oh the dimmed is like grey-mode

lilac wren
#

yeah, I only hate true black

#

Discord does it well

green onyx
#

true

lilac wren
#

it's a shame they don't have auto switching though

#

bc I have to open Discord while blinded and then switch it to dark every night

green onyx
#

hm

#

github can read system darkmode

#

discord default is dark

lilac wren
#

yeah you can add some simple css I think and it'll switch automatically

high rain
#

keep getting stuck here, hmmmm

green onyx
#

put it manually then

lilac wren
#

someone else had this issue I think, just do recovery mode manually

zealous bridge
#

like i said before just run again

valid adder
#

!t ibec

mystic axleBOT
# valid adder !t ibec
ibec

Fix for error code 3, 8, and 10 aka the iBEC error in futurerestore

  1. Uninstall all apple drivers via device manager.
  2. Uninstall all apple products including itunes and apple device support stuff via control panel uninstall a program. MAKE SURE TO CHECK UNINSTALL DRIVER WHEN UNINSTALLING
  3. Unplug and replug device.
  4. Check device manager for more apple stuff and uninstall if so with same driver checkbox.
  5. Disconnect device.
  6. Install itunes64 exe from apple.com itself, no windows store bullshit. (It will be labeled windows 7, 8 but install it on windows 10, it works fine)
  7. Plug in device in recovery.
  8. iboot (recovery) driver should show up under usb in device manager. Uninstall it and check the with software box.
  9. Run futurerestore.
  10. Unplug and replug your device.
  11. Run futurerestore again
zealous bridge
#

if its already in recovery

green onyx
#

pog

#

ibec tag

zealous bridge
#

This is a bit execssive tho imo

#

Steps 1-5 should do

#

For most

valid adder
#

it needs to be excessive

#

because people are fucking incompetent

lime bear
#

how do i set nonce?

green onyx
zealous bridge
#

[[dimentio]]

mystic axleBOT
#
dimentio

PoC tool for setting/getting nonce without triggering KPP/KTRR/PAC. (requires tfp0)

Author

0x7ff

Version

2.0.0-1

Price

Free

Repo
Bundle ID

com.0x7ff.dimentio

More Info
#
dimentio

PoC tool for setting/getting nonce without triggering KPP/KTRR/PAC. (requires tfp0)

Author

0x7ff

Version

2.0.0-1

Price

Free

Repo
Bundle ID

com.0x7ff.dimentio

More Info
valid adder
#

dimentio, conan repo

lime bear
#

ok thx

#

and what is the nonce for a noapnonce blob

zealous bridge
#

generator is whatever is in your blob

lime bear
#

0x1111111111111111

zealous bridge
#

thats it then

lime bear
#

how do i find it tho

#

i saw that nonc somewhere

zealous bridge
#

open blob with text editor

#

then ctrl + f for ā€œgeneratorā€

green onyx
#

^

valid adder
lime bear
#

or it was in the title

zealous bridge
#

thats ecid....

lime bear
#

oh oops sorry

zealous bridge
#

lmao

lime bear
#

0x1111111111111111

#

thats the right one

#

oops

#

wait how do i use dimensio

#

im not used to this

zealous bridge
lime bear
#

my first time working on non legacy devices so

zealous bridge
#

follow that ^

lime bear
#

ok

lilac wren
valid adder
#

bottom is the normal

#

use bottom

zealous bridge
#

"

valid adder
#

still wrong

zealous bridge
#

eh i give up

#

not too pressing anyway

green onyx
#

""

#

is that wrong

#

"abc"

zealous bridge
#

"abc"

#

whats the differenxe

green onyx
#

well, i think smart quotes are straight

#

like vertical

#

mobile isnt

#

its tilted

zealous bridge
#

those were pretty straight

valid adder
#

mobile just long press

zealous bridge
#

thats what i did...

valid adder
#

chose the wrong one maybe

green onyx
#

huh

#

how tf do i do a long press on my laptop

zealous bridge
#

"very smart"

valid adder
#

u dont

#

its a mobile thing

green onyx
#

lmao

green onyx
valid adder
#

nah

#

just tryna get unc0ver working

#

doesn't work with any method ive tried

#

signature is fine tho

green onyx
#

do u have a dev acc?

valid adder
#

yeh

green onyx
#

damn wth

lilac wren
#

So maybe apple thing

valid adder
#

ive been explaining how to fix it on mac for the past 10 minutes

lilac wren
#

ā€œSmart quotesā€ "Boring quotes"

#

Fix it meaning turn it off or on?

valid adder
#

yes

zealous bridge
#

...

lilac wren
#

... indeed

#

I think there's no such thing as mobile quotes

lime bear
#

can I downgrade to any iOS if I have blobs?

zealous bridge
#

depending if theres a jailbreak available for the version you’re on right now

#

and on SEP compatibility

lime bear
#

ok

#

can I go from newest iOS to 14.0.1

zealous bridge
#

what device

lime bear
#

iPhone SE 1

zealous bridge
#

yes

lime bear
#

ok thx

#

what is the lowest version i can go

zealous bridge
#

14.0

lime bear
#

ok thx

#

i have blobs from iOS 12.2 to 14.4

#

14.4.1

spring mauve
#

havent been here in a while any news on ios 13.x to ios 14.2 on a11 devices?

lilac wren
#

no

lilac wren
high rain
#

ok so I am back 😦 here is what I've done tried, any help would be appreciated: ```
ip 8 gsm on 13.5 going to 14.3. previously on checkra1n

  1. make sure generator in blob is 0x1[16]
  2. download correct ipsw
  3. set generator on iphone in jailbroken state
  4. run future-restore from command line with ./future -t *.shsh2 *.ipsw --latest-sep --latest-baseband
  5. get stuck everytime on:

Finished downloading the latest firmware components!
Found device in Normal mode
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

code=9043985
line=138
file=futurerestore.cpp
commit count=194:
commit sha =0ab9df3209ee599f581532d05d331e6abe0f53f3:

what i have tried (grasping here):

  • different usb adapter
  • different cable
  • add -u to command
  • tried 14.3-ota blobs (have the same name)
  • tried both blobs in 14.3 (downloaded from TSS)
  • tried GUI just for fun
  • restored root fs
  • re-ran it after I get that error
  • windows/linux/osx```
#

if anyone has any thoughts or ideas, i am open

lilac wren
#

is your phone actually in recovery or no

high rain
#

it has the phone + laptop icon

lilac wren
#

yes that's recovery

#

have you exited out of recovery and entered it manually

high rain
#

and run future restore from that?

lilac wren
#

yes

high rain
#

nope, good idea, let me try!

lilac wren
#

iPhone 8 or later: Press and quickly release the Volume Up button. Press and quickly release the Volume Down button. Then, press and hold the Side button until you see the recovery mode screen.

#

while plugged in to itunes or finder

high rain
#
Identified device as d201ap, iPhone10,4
Extracting BuildManifest from iPSW
Product version: 14.3
Product build: 18C66 Major: 18
Device supports Image4: true
Got ApNonce from device: 27 32 5c 82 58 be 46 e6 9d 9e e5 7f a9 a8 fb c2 8b 87 3d f4 34 e5 e7 02 a8 b2 79 99 55 11 38 ae
Cleaning up...
[exception]:
what=Device ApNonce does not match APTicket nonce
lilac wren
#

awesome so we figured out the recovery part

#

now you just need to set the right generator

zealous bridge
#

after running again from recovery

#

failed to enter recovery isnt the main problem, you dont have the right generator set

high rain
#

ah

#

ok i misunderstood

#

my apologies

lilac wren
#

they said they used GUI though so I assume it would have given them the popup and they would have realized it's a different issue?

#

or maybe not lol

zealous bridge
#

they were using cli

high rain
#

i tried both...

zealous bridge
#

used gui once

#

hm

#

ok so

#

troubleshooting this

#

whats the generator inside your blob?

#

0x1111... right?

high rain
#

0x1111....yeah.

zealous bridge
#

thats the one inside your blob?

#

ok you have A12+ right

#

so iPhone XS and newer

high rain
#

i dont believe so?

#

i have ip8

zealous bridge
#

oh ok

#

what are you using to set generator?

#

like unc0ver app... dimentio etc

high rain
#

i was using dimentio

#

or whatever its called

zealous bridge
#

did you restore rootfs every time before using futurerestore?

high rain
#

no i did not

zealous bridge
#

so you’ve tried setting the generator and immediately futurerestoring (without rebooting in between)?

high rain
#

yes

#

and that is when i get to the failed to put device into recovery

#

when i do not jailbreak -> set generator

#

i get the Device ApNonce does not match APTicket nonce

zealous bridge
#

hm wait

#

when i tell you to run it again

#

are you taking the device out of recovery?

#

so like booting it back into normal mode

high rain
#

no

#

just running it again

zealous bridge
#

and after running it again what happens?

high rain
#

ApNonce does not match APTicket nonce

#

i assue because i am not setting the generator

#

but honestly, i have no idea

zealous bridge
#

so just to clarify

#

you set generator > recovery mode error > run again > apnonce error

#

without any reboots

zealous bridge
high rain
#

yes

#

that is correct

zealous bridge
#

ok

#

upload your blob to https://verify.shsh.host and send a screenshot

#

make sure to blur your ECID

high rain
#

ok i will do that in 3 min gotta let the dogs out

#

thanks for the help!

zealous bridge
#

nw

zealous bridge
#

lmao wtf

green onyx
#

i upvoted u to 2 upvotes

lilac wren
#

Oh lol

#

I mean

#

Ribbit

green onyx
lilac wren
#

🐸

green onyx
#

lol

zealous bridge
#

*month

zealous bridge
#

wait is that edit for futurerestore or unc0ver release troll

zealous bridge
#

that apnonce does not look right

#

wasnt the a11 apnonce for 0x1111... starting with 2735 or smth like that

high rain
#

sorry, that was the OTA blob

#

this is the 14.3 blob

zealous bridge
#

So were you using the OTA blob this entire time

high rain
#

no, ive tried both

zealous bridge
#

Ok well for now

#

Set your generator with dimentio and send a screenshot of the output

#

then immediately after try futurerestore using the 14.3 normal blob and see what happens

lilac wren
high rain
#

ok, so here is what i am going to do (haha, for my sanity):

  1. jailbreak with checkra1n
  2. set nonce to 0x1....
  3. use future restore with 14.3 blob and 14.3 ipsw
#

should i use the -u flag ?

zealous bridge
#

Make sure you dont reboot in between thats the main thing

zealous bridge
zealous bridge
lilac wren
#

Oh lol

high rain
#

1 more question: i have 2 blobs under 14.3

#

4614384957038638_iPhone10,4_d201ap_14.3-18C66_27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae.shsh2

#

4614384957038638_iPhone10,4_d201ap_14.3-18C66_15400076bc4c35a7c8caefdcae5bda69c140a11bce870548f0862aac28c194cc.shsh2

high rain
zealous bridge
#

looks fine

#

now try futurerestore with the correct blob

high rain
#

./futurerestore-v194 -u -t 4614384957038638_iPhone10,4_d201ap_14.3-18C66_27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae.shsh2 iPhone_4.7_14.3_18C66_Restore.ipsw --latest-sep --latest-baseband

zealous bridge
#

why is the ipsw there

#

you should put it at the end of the command

#

also add the -d parameter at the end

#

Just after ––latest–baseband

high rain
#

/futurerestore-v194 -u -t 4614384957038638_iPhone10,4_d201ap_14.3-18C66_27325c8258be46e69d9ee57fa9a8fbc28b873df434e5e702a8b27999551138ae.shsh2 --latest-sep --latest-baseband -d iPhone_4.7_14.3_18C66_Restore.ipsw

#

like this?

zealous bridge