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

T8012 support #167

Open
graphine27 opened this issue Jun 12, 2023 · 2 comments
Open

T8012 support #167

graphine27 opened this issue Jun 12, 2023 · 2 comments

Comments

@graphine27
Copy link

graphine27 commented Jun 12, 2023

I'm running into an issue with the image on a T2 device.
I can run the exploit, upload the files and boot into recovery but it stops there.
It looks like the ramdisk image is not valid.
irecovery -s


loaded ramdisk at <ptr> of size 0x7eb0200, from image at <ptr>
loaded device tree at <ptr> of size 0x100000, from image at <ptr>

ramdisk
ea0f64a4253252:448
Ramdisk image not valid

devicetree
ea0f64a4253252:448
Device Tree too large

Tried with multiple bridgeos version.

@graphine27
Copy link
Author

Figured out that issue was caused by the version, patching a really old one makes it not throw those errors, likely newer ones use APFS and script logic does not work in this case.

Even when all images are correct bootx command does not actually boot the system, it is stuck, I guess you already know that since you put a warning.

[!] WARNING: T2 MIGHT HANG AND DO NOTHING WHEN BOOTING THE RAMDISK!

I've seen videos of T2 macs booting a ramdisk, it even showed the bootlog on the touch bar (not testing on a touchbar one), @verygenericname any idea what we are doing wrong?

@alhaithammsar
Copy link

SSHRD tool does not have the correct files for T2, i have T2 jailbreak like checkra1n one that works on bridgeOS from 6.0 to 7.6+, also I have ssh ramdisk , lmk what you need these things for? Telegram @SDunlocks_91

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

2 participants