MrChromebox
MrChromebox
nearly identical: * read current firmware * run ME cleaner on it * flash back to device
yep, works fine on all them I've tested on
there is no need to use ME Cleaner on subsequent updates, simply keep the flash descriptor locked and the IFD/ME will remain unable to be written via internal flashing, same...
> "keeping the flash descriptor locked" the flash descriptor (IFD) is a 4kb section at the start of the flash chip, it defines the layout of the flash chip and...
> Wouldn't it be possible to somehow set the HAP bit from the UEFI settings / shell? no. The HAP bit is contained in the flash descriptor (IFD) region of...
ME cleaner only works for a very small number of older Chromebooks. The process for using ME cleaner is well documented on the ME cleaner github, there's nothing I can...
@moriel5 6th/7th-gen ones require whitelisting a module or you'll lose WiFi (and maybe more). 8th-gen and up aren't supported. But you really need to ask yourself why you think using...
there are several different "8th gen" mobile platforms: * Kabylake-R * Coffeelake * Whiskeylake * Cannonlake Only KBL-R uses the same ME 11.x firmware as KBL. The others use 12.x...
what firmware type / version are you running?
suspend/resume issues on the legacy BIOS are a product of Google's use of the TPM in their verified boot -- there's nothing I can do about that, it's an issue...