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
On all devices i've tested that are pre-frecon, get_largest_cros_blockdev completely fails, and every action that uses it (cryptosmite, disabling rootfs verification, touching .developer_mode, etc) exits complaining about the internal storage not having a ChromeOS install.
This has mostly been tested on Kefka, and I have not encountered this error when running a frecon shim (e.g. octopus, legacy sh1mmer doesn't change anything), and I'm not entirely sure what the cause is as I haven't done much testing, though if I had to guess it's likely an outdated or missing binary for sfdisk.
The text was updated successfully, but these errors were encountered:
I was right, running sfdisk with those arguments shows "invalid option -- 'o'" and the rest of the sfdisk help menu. This was tested on the shim and in a chroot for the screenshot.
This seems to work in the coral shim, sfdisk lists the -o option in the help menu, but I haven't tested any of the payloads. I'll try to cryptosmite a hana Chromebook soon, I'll comment the results here.
On all devices i've tested that are pre-frecon, get_largest_cros_blockdev completely fails, and every action that uses it (cryptosmite, disabling rootfs verification, touching .developer_mode, etc) exits complaining about the internal storage not having a ChromeOS install.
This has mostly been tested on Kefka, and I have not encountered this error when running a frecon shim (e.g. octopus, legacy sh1mmer doesn't change anything), and I'm not entirely sure what the cause is as I haven't done much testing, though if I had to guess it's likely an outdated or missing binary for sfdisk.
The text was updated successfully, but these errors were encountered: