I think on Discord you said RecoMod didn’t work? If you can get it to work, I wonder what would happen if you set the GBB flags to TONORM prohibited (blocks verified mode)
If you’re trying to flash UEFI though, you’re only chance might be to flash with an external programmer…
Well, when you asked about it I actually tough you’re talking about a clean reinstallation from the recovery mode, at the point I didn’t know that RecoMod was actually… a mod… Hehe
Just for the question… how safe is this method? I mean, I don’t want to brick it, if is too risky I would like to sell it instead of have a tech brick on my desk.
I also have a ThinkPad C13 Yoga (purchased second hand specifically for converting to a Coreboot Linux laptop) but with the Athlon APU instead of the Ryzen 5. Successfully installed the MrChromebox firmware and initially installed Lubuntu 24.04 LTS (I was unaware of the docs at the time). Lubuntu appeared to not have installed the GRUB EFI loader so I set off on a journey to try to fix that. I do not remember exactly all the steps (and specific commands) that I did as this project was interrupted by a move, but from what I remember it boils down to me doing grub-install, manually copying a GRUB EFI file to the ESP (as it was missing), then learning about UEFI variables and efibootmgr and adding the Lubuntu install to the UEFI boot order with efibootmgr (and efibootmgr -v would confirm that it had been added) but upon reboot I would still get dumped into the UEFI shell and the EDK II/TianoCore interface would list the UEFI shell as the only boot option (unless a live USB was inserted) and the Lubuntu install would no longer show up in the efibootmgr -v output. Fast forward to this week and I decided to revive the project, found the docs and installed openSUSE Tumbleweed (July 8 2024 snapshot) on the C13 today. Laptop still boots to the UEFI shell when the install USB is removed and the UEFI shell is the only boot option in the TianoCore interface. Also, earlier this week I tried to boot from or add a boot option from the UEFI shell but the map command does not show any file systems/disk and FS0, FS1 etc. are unavailable. It appears that the internal eMMC disk of the C13 is simply not detected at all by the UEFI firmware.
you’re not running the UEFI firmware, you’re running edk2 as a RW_LEGACY payload – unless you flashed the UEFI Full ROM firmware and didn’t mention it in your post, but the post subject heavily implies RW_LEGACY.
coolstar wrote an edk2 driver for the eMMC on Picasso devices, but it’s not been tested on RW_LEGACY and isn’t working apparently. I don’t have a PCO device with eMMC to test/debug unfortunately
My memory is a bit fuzzy as I mentioned in my previous post but I believe that I did wipe the original Google firmware. Is there any way I can verify this? The EDK II/TianoCore interface simply says “FW: MrChromebox 4.22.1<alphanumeric sequence (git commit hash?)>”. I checked my Downloads directory but realized that your script downloads the appropriate firmware itself. Based on what you are saying it seems that this laptop having eMMC storage rather than a traditional SATA/NVMe SSD (combined with running EDK II as a RW_LEGACY payload) is the issue?
the UEFI firmware with PCO eMMC support is newer than the one you have flashed - boot a Linux USB, update the firmware to latest, and eMMC should be detected at boot
Booted an openSUSE Leap live USB today on the C13, ran firmware-util.sh and it said that I have full ROM UEFI and firmware write protect disabled. Updated to the version from June 17 and the laptop now boots to GRUB (don’t know why it doesn’t load Tumbleweed but it probably has nothing do with the UEFI firmware)! EDK II/TianoCore now indeed shows “eMMC device” as a boot option.
