imagebuilder icon indicating copy to clipboard operation
imagebuilder copied to clipboard

chromebook_x86_uefi: misc: Enhancement: EFI partition

Open EMLommers opened this issue 1 year ago • 2 comments

If you take a recovery image from Google with chromeOs and you have an UEFI enabled platform (x86, x86_64) you are able to boot into ChromeOS Take for example a Coral,eve image (tested), partition 12, undelete(really) the files and you are able to boot into chromeos (selecting image A or B and verified A and B, USB ) , especially convenient when you have flashed the firmware with Mr.Chromebox UEFI firmware. This might be a solution for persons who like to get rid of malware Google, but like to keep their pc accessories all running (because of ChromeOS kernel) and not loose any things (like audio for example). Solutions like yours and keep your 'breath' targeting u-boot/depthcharge with dev firmware, not UEFI booting chromebooks. This could be the solution to have best of both worlds..

EMLommers avatar Sep 17 '22 23:09 EMLommers

@EMLommers - i'm not sure if i understand it correct: you mean it is possible to boot chromeos completely from a modified recovery image using efi boot firmware?

hexdump0815 avatar Sep 18 '22 05:09 hexdump0815

Correct! Using .efi and syslinux. Not only recovery image, but also ChromeOS installed booting from EFI partition. Ofcourse there is also the 'brunch' / 'crunch' framework for running ChromeOS with UEFI/MBR, however in my opinion and results were not completely satisfying. And arnoldthebat images same, like neverware .

EMLommers avatar Sep 18 '22 12:09 EMLommers