jxxnew

Also, tried to use a Kali live image renamed to .bin as source for recovery USB, no joy. Dev_boot_usb = 1 dev_boot_legacy = 1 dev_default_boot = 0 dev_boot_signed_only = 0...

I procured an older test chromebook and followed the same process. HP Chromebook 11 G5 EE - RELM/Braswell Process worked without any issue on first try. One difference, the script...

Just so I understand. If the issue I faced with a newer Chromebook was a Tianocore issue not recognizing USB nor SD at boot and going to an older Chromebook...

Thanks, makes sense. Appreciate the detailed explanation.

I'll give that a try

Test process: 1. Start with known good SD and USB with Kali live image. 2. Boot new Chromebook to Chrome OS 3. Insert each external device 4. Result - ChromeOS...

Note: known good means they boot just fine with the older Chromebook.

After using the firmware script, when the Chromebook boots, it goes to a screen saying you are in developer mode - there is no prompt for ESC, that is what...

After choosing Tianocore, get a brief prompt for Esc. Get an HP Lantis Boot screen Boot Menu shows two devices eMMC device - choose this, dumps to Grub with same...

on the previous comment, both USB and SD devices are ISO images written using DD and work successfully with no alterations using the older Chromebook and SeaBIOS.