coreboot VS Jumpdrive

Why BIOS (did you mean UEFI?) when it runs the best boot loader, which is Coreboot¹. Many users would love to re-flash their bios/uefi for it, if it’s supported.

1: https://www.coreboot.org/

Coreboot is 0.6% C++.

NovaCustom ; some models come with Dasharo a coreboot distribution.

You can also use Mr. Chromebox Script to install Coreboot on your chromebook to get a UEFI BIOS on your Chromebook and then you can go an install either a linux distro or even Windows if you want. It's a pretty straightforward process and also reversable if you want to go back to just using ChromeOS.

Some models are available with Dasharo a [coreboot]https://www.coreboot.org/) distribution.

why no haswell_ult_dmi_registers for broadwell? in https://github.com/coreboot/coreboot/blob/master/util/inteltool/pcie.c

use croshfirmware.sh from https://github.com/coreboot/coreboot/tree/master/util/chromeos

There may be other protections to restrict SPI flash access for security reasons (so you might not be able to flash your custom firmware in the OS), but worst case you can use a HW flasher (or maybe USB flashback). Still, this doesn't address the elephant in the room - platform initialization code might be open-sourced, but that isn't everything. You'll still need to figure out the board-specific stuff (the Super I/O chip, chipset GPIOs, other peripherals, etc.). Using coreboot as an example, Intel provides the Firmware Support Package blob to handle platform initialization. I think AGESA is somewhat similar to this, though Intel publicly releases the binaries for use in coreboot/etc. Thanks to the FSP, coreboot has support for recent Intel chipsets. However, there is only support for two recent consumer boards: the MSI PRO Z690-A WiFi DDR4 and DDR5.

does anyone know what is https://github.com/coreboot/coreboot/blob/b12caef23bc1b29c2e658f2b728cc4beac1e62b9/src/northbridge/intel/haswell/vcu_mailbox.c

Download crosfirmware.sh and run it from command line: bash crosfirmware.sh droid

Download: https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/pine64-pinephone.img.xz

To confirm the battery status I flashed the charging image from https://github.com/dreemurrs-embedded/Jumpdrive/issues/55. That indeed showed that there was pretty much no charge in the battery. I then took my macbook adapter and charged it for two hours using that, and then the status led started flashing green. Looks like this is solved!

I would suggest that you download https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/pine64-pinephone.img.xz. Then write it to a microSD card using "Balena Etcher" and then insert the microSD card in the top slot and let us know if there is a question or if it changed anything.

Please put Jumpdrive on a microSD card and try to boot that. Jumpdrive boots independently from the battery charge. If it boots fine you can let it charge in there for multiple hours and then see if you can boot the phone properly again. https://github.com/dreemurrs-embedded/Jumpdrive

That sounds like a corrupted installation, not a drained battery. If you're on the regular PinePhone (not the Pro) I would suggest you to flash JumpDrive on a microSD card, insert that into the phone (top slot) and to boot from that. The image can be found here: https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/pine64-pinephone.img.xz

At this point if you haven't updated in a long time it's best if you flash a new image to your eMMC because if you pacman -Syu your just gonna bork it like I did when I updated my KDE edition after a year of being sidelined lol. Luckily jumpdrive exists and makes this task as simple as running a dd command.

JumpDrive -> https://github.com/dreemurrs-embedded/Jumpdrive/releases

The last time I had to reinstall my Librem 5 I ended up using JumpDrive and a fresh image from Purism's Jenkins, reusing the instructions from postmarketOS Wiki#Installation).

https://github.com/dreemurrs-embedded/Jumpdrive/releases/tag/0.8 I had a similar situation. After getting a pinephone pro my pinephone OG set idle for several months. I couldn't boot to the eMMc or the sd. I still had jumpdrive on an sd so i tried booting from it. It fixed everything although I don't know how. Now it boots from eMMc or sd just fine. I didn't even plug it into a laptop. After the jumpdrive screen booted I powered it down and removed the jumpdrive for pinephone sd. I fired up the pinephone OG to fix the modem firmware. Flashing the modem went well and the pinephone is ready for use should I need it.