Skip to content
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.

Update docs to indicate the need for firmware keys. Drop support for a9x. #84

Open
aihkas opened this issue Oct 11, 2022 · 4 comments
Open

Comments

@aihkas
Copy link

aihkas commented Oct 11, 2022

After struggling to get things to work for A9x, I was stuck because there are no publicly available firmware keys for the iPad pro first gen.
Is there any way or a guide on how to work on extracting the firmware keys? checkm8 should've made it possible AFAIK.

I also suggest adding a note about that in the readme or the guide. iPhone Wiki - Firmware Keys

Device found in DFU Mode.
Getting firmware keys for: j99aap
Cleaning up...
[exception]:
what=getting keys failed with error: 14745615 (failed to get FirmwareJson from Server). Are keys publicly available?
code=41549892

Screenshot 2022-10-11 at 13 16 39

@aihkas
Copy link
Author

aihkas commented Oct 11, 2022

Using gaster to decrypt iBSS seems to work. Gotta figure out how to pass it to futurerestore later.

@aihkas
Copy link
Author

aihkas commented Oct 12, 2022

If anyone ends up in the same situation, I managed to decrypt and get the keys. Still gotta work on a workaround, so futurerestore grabs them locally in some way or another, maybe by tunneling the connection.

@aihkas aihkas changed the title Update docs to indicate the need for firmware keys Update docs to indicate the need for firmware keys. Drop support for a9x. Oct 16, 2022
@aihkas
Copy link
Author

aihkas commented Oct 16, 2022

Update: even after successfully passing the firmware keys, futurerestore will fail with ApNonce from device doesn't match IM4M nonce after applying ApNonce hax. Aborting! I suggest dropping support for a9x. (iPad6,8, s8001).
All the available methods will fail to set the apnonce for the iPad pro first gen because, technically, all methods to patch or remove the signature checks for this chip are flawed. gaster tool seems close to sorting it out, but it is still not perfect (It could be related to cache problems with the used methodology).

@aihkas
Copy link
Author

aihkas commented Oct 16, 2022

Screenshot 2022-10-16 at 13 44 49

Screenshot 2022-10-16 at 13 45 55

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant