Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore gets error: (os/kern) invalid address #643

Closed
kotleni opened this issue Jun 7, 2024 · 15 comments
Closed

Restore gets error: (os/kern) invalid address #643

kotleni opened this issue Jun 7, 2024 · 15 comments

Comments

@kotleni
Copy link

kotleni commented Jun 7, 2024

I have just unique error when trying to restore my mac (air m1 8gb).

ERROR: Unable to successfully restore device
Checkpoint completed id: 0x648 (cleanup_send_final_status) result=0
Checkpoint FAILURE id: 0x648 result=0: [0]D(failed to update device firmware)[1]D(ramrod firmware update failed)[2]D(update_aht_block_invoke: ipd update failed with code 0x00000001.
Error: ((os/kern) invalid address)
)
FDR 0x5c134798fdd0 terminating...
ERROR: Unable to restore device
@kotleni
Copy link
Author

kotleni commented Jun 8, 2024

Hahah, good morning. After night a just tried it one more time, and blah - i just have a different error.

ERROR: Unable to successfully restore device
Checkpoint completed id: 0x648 (cleanup\_send\_final\_status) result=0
Checkpoint FAILURE id: 0x648 result=0: \[0\]D(failed to update device firmware)\[1\]D(ramrod firmware update failed)\[2\]D(update\_aht\_block\_invoke: ipd update failed with code -3
)
FDR 0x63e7aac74880 terminating...
ERROR: Unable to restore device

@nikias
Copy link
Member

nikias commented Jun 8, 2024

I suspect that there is some new component that has to be added to the restore logic... A full output would be helpful, the partial output doesn't show the cause of the problem (we'd want to see the checkpoint 0x648 messages from the device logs). Did you have this working before or is it your first attempt to restore a macbook?

@kotleni
Copy link
Author

kotleni commented Jun 8, 2024

@nikias Thanks for you answer.
Yes, it's my first attempt to restore macbook.

I have some problems to get all logs from idevicerestore... just my console is cut old logs and after i can't copy it.
And... i can't do '>>' for output, because not all logs is getting with it to file. And here is no any command line argument to set log output file.

I need some time to get full logs.

@kotleni
Copy link
Author

kotleni commented Jun 8, 2024

Idk, maybe it's can help. My irecovery logs:

=======================================
::
:: Microkernel iBootStage1 for j313, Copyright 2007-2022, Apple Inc.
::
::      Local boot, Board 0x26 (j313ap)/Rev 0x6
::
::      BUILD_TAG: iBoot-7459.141.1
::
::      BUILD_STYLE: RELEASE
::
::      USB_SERIAL_NUMBER: SDOM:01 CPID:8103 CPRV:11 CPFM:03 SCEP:01 BDID:26 ECID:00024XXXX01E IBFL:FD
::
=======================================

@kotleni
Copy link
Author

kotleni commented Jun 8, 2024

@nikias Here is full logs.
full_idevicerestore_latest.log

@Dazag
Copy link

Dazag commented Jun 9, 2024

I am experiencing the same error, is there any way I can help? (air m1 16GB) is it maybe the version we are trying to install?

@kotleni
Copy link
Author

kotleni commented Jun 9, 2024

@Dazag I tried a lot of different versions, no any changes here. We just should wait help.

@kotleni
Copy link
Author

kotleni commented Jun 10, 2024

@nikias Are you hoping for a fix soon?

@nikias
Copy link
Member

nikias commented Jun 10, 2024

Hi guys, could you hop on Telegram and reach out to me, so we can debug this issue? You can find me in the https://t.me/libimobiledevice group. That would make it way easier to figure out what might be happening. I have a lot of interest to getting this fixed.

@kotleni
Copy link
Author

kotleni commented Jun 10, 2024

@nikias Done.

@Tecnio
Copy link

Tecnio commented Jun 11, 2024

I am also having this issue, however I cannot join the Telegram as I was restoring my main device.

@ghost
Copy link

ghost commented Jun 11, 2024

Got the same type of error, apparently the dev is working on it, we better let him fix this issue.

@kotleni
Copy link
Author

kotleni commented Jun 11, 2024

@Tecnio Just wait, developer is already trying to fix this problem. :)

@kotleni
Copy link
Author

kotleni commented Jun 12, 2024

Latest commit in libtatsu repo is fixing this issue:
libimobiledevice/libtatsu@9e52f1c

Just rebuild and reinstall lib from source code.

@kotleni
Copy link
Author

kotleni commented Jun 12, 2024

Fixed

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

No branches or pull requests

4 participants