I need help unlocking USB Boot

Again, look at the Chrultrabook docs for the hardware list, as well as the link there to the WP page, which is a lot more clear.

1 Like

no, it’s not more clear than the list/docs on my site. In this case, it’s less clear

And that lack of clarity, coupled with your own lack of understanding, is making this overly hard for the OP.

CRAASK uses CR50/Ti50 for firmware WP, and can only be disabled with a SuzyQ cable. End of story.

On 2023+ ChromeOS devices using a Gen2 CR50 security chip (aka Ti50 ), there is a new feature where the CR50 will verify the RO portion of the AP firmware at boot. If you want to flash custom firmware, you must use the CCD method above to disable firmware write protection, regardless if the device supports disablement via battery disconnect or a jumper as well.

1 Like

Ok, I stand corrected.
Apologies to @UnoHero

I am not new at this, but I somehow misses the requirement for using a SuzyQ,probably because I used the TOC on the docs to get to the WP section there, as opposed to the link to your docs.

The Chrultrabook support list make zero mention of SuzyQ on the hardware support page for this device, and neither does the section on disabling WP in regard to the Ti50. So, if someone has made the mistake of following the TOC, they will get different information than clicking on the link under the method column.

So…which documentation should we be using, then?

1 Like

the chrultrabook docs have the same info organized slightly differently, CRAASK still shows CR50/Ti50, and the WP disabling page still tells you that you have to use CCD/SuzyQ for Ti50 devices.

IMO the chrultrabook docs should just drop the firmware-relate bits and link to my site to avoid these kinds of inconsistencies.

1 Like

On that topic, they should also just update the site itself, for example: the notes for MORPHIUS state that “iommu=pt” needs to be entered into the GRUB boot parameters, but I and many others are able to boot into Linux without “iommu=pt”, but that’s just me.

1 Like

…Soo i need the cable and i will come back wen i have it :grin: