You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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
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
Tried with multiple bridgeos version.
The text was updated successfully, but these errors were encountered: