Add google kano flashing guide#223
Draft
cwiggs wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Chris Wiggins <chris@cwiggs.com>
cwiggs
marked this pull request as draft
July 22, 2026 21:22
tlaurion
reviewed
Jul 22, 2026
| TODO: Do we need to run `gsctool` from ChromeOS? I did not have to but maybe the previous owner of my Kano | ||
| device did it? [source](https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html#step-1-enabling-closed-case-debugging-ccd) | ||
|
|
||
| Now we disable software write protection: |
Collaborator
There was a problem hiding this comment.
@MrChromebox this is weird and we don't understand.
Even if IFD has all regions disabled per linuxboot/heads#2133 's linuxboot/heads@aece972
Found Master Section
FLMSTR1: 0xffffffff (Host CPU/BIOS)
EC Region Write Access: enabled
Platform Data Region Write Access: enabled
GbE Region Write Access: enabled
Intel ME Region Write Access: enabled
Host CPU/BIOS Region Write Access: enabled
Flash Descriptor Write Access: enabled
EC Region Read Access: enabled
Platform Data Region Read Access: enabled
GbE Region Read Access: enabled
Intel ME Region Read Access: enabled
Host CPU/BIOS Region Read Access: enabled
Flash Descriptor Read Access: enabled
FLMSTR2: 0xffffffff (Intel ME)
EC Region Write Access: enabled
Platform Data Region Write Access: enabled
GbE Region Write Access: enabled
Intel ME Region Write Access: enabled
Host CPU/BIOS Region Write Access: enabled
Flash Descriptor Write Access: enabled
EC Region Read Access: enabled
Platform Data Region Read Access: enabled
GbE Region Read Access: enabled
Intel ME Region Read Access: enabled
Host CPU/BIOS Region Read Access: enabled
Flash Descriptor Read Access: enabled
FLMSTR3: 0xffffffff (GbE)
EC Region Write Access: enabled
Platform Data Region Write Access: enabled
GbE Region Write Access: enabled
Intel ME Region Write Access: enabled
Host CPU/BIOS Region Write Access: enabled
Flash Descriptor Write Access: enabled
EC Region Read Access: enabled
Platform Data Region Read Access: enabled
GbE Region Read Access: enabled
Intel ME Region Read Access: enabled
Host CPU/BIOS Region Read Access: enabled
Flash Descriptor Read Access: enabled
FLMSTR5: 0xffffffff (EC)
EC Region Write Access: enabled
Platform Data Region Write Access: enabled
GbE Region Write Access: enabled
Intel ME Region Write Access: enabled
Host CPU/BIOS Region Write Access: enabled
Flash Descriptor Write Access: enabled
EC Region Read Access: enabled
Platform Data Region Read Access: enabled
GbE Region Read Access: enabled
Intel ME Region Read Access: enabled
Host CPU/BIOS Region Read Access: enabled
Flash Descriptor Read Access: enabled
Heads flashprog -p internal still reports:
flashprog unknown on Linux 6.6.30-Heads (x86_64)
flashprog is free software, get the source code at https://flashprog.org
Calibrating delay loop... OK.
coreboot table found at 0x76883000.
Found chipset "Intel Alder Lake-P".
Enabling flash write... GPR0: Warning: 0x00001000-0x001a6fff is read-only.
At least some flash regions are write protected. For write operations,
you should use a flash layout and include only writable regions. See
manpage for more details.
OK.
Found Programmer flash chip "Opaque flash chip" (32768 kB, Programmer-specific) on internal.
No operations were specified.
Collaborator
There was a problem hiding this comment.
Also Heads recovery shell cbmem --console | grep '[DEBUG] ME' returns:
[DEBUG] ME: HFSTS1 : 0x90000055
[DEBUG] ME: HFSTS2 : 0x82130116
[DEBUG] ME: HFSTS3 : 0x00000050
[DEBUG] ME: HFSTS4 : 0x00004000
[DEBUG] ME: HFSTS5 : 0x00000000
[DEBUG] ME: HFSTS6 : 0x40600006
[DEBUG] ME: Manufacturing Mode : YES
[DEBUG] ME: SPI Protection Mode Enabled : NO
[DEBUG] ME: FW Partition Table : OK
[DEBUG] ME: Bringup Loader Failure : NO
[DEBUG] ME: Firmware Init Complete : NO
[DEBUG] ME: Boot Options Present : NO
[DEBUG] ME: Update In Progress : NO
[DEBUG] ME: D0i3 Support : YES
[DEBUG] ME: Low Power State Enabled : NO
[DEBUG] ME: CPU Replaced : YES
[DEBUG] ME: CPU Replacement Valid : YES
[DEBUG] ME: Current Working State : 5
[DEBUG] ME: Current Operation State : 1
[DEBUG] ME: Current Operation Mode : 0
[DEBUG] ME: Error Code : 0
[DEBUG] ME: FPFs Committed : YES
[DEBUG] ME: Enhanced Debug Mode : NO
[DEBUG] ME: CPU Debug Disabled : YES
[DEBUG] ME: TXT Support : NO
[DEBUG] ME: Manufacturing Vars Locked : YES
[DEBUG] ME: WP for RO is enabled : YES
[DEBUG] ME: RO write protection scope - Start=0x1000, End=0x1A6FFF
So ME region still protected.
[DEBUG] ME: WP for RO is enabled : YES
[DEBUG] ME: RO write protection scope - Start=0x1000, End=0x1A6FFF
tlaurion
reviewed
Jul 22, 2026
tlaurion
left a comment
Collaborator
There was a problem hiding this comment.
@MrChromebox we need some help figuring out what steps are needed to properly disactivate HW+SW protection so ME is not reported as locked
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
preview: https://cwiggs.github.io/heads-wiki/