Black Screen and Bricking After Flashing Full ROM with MrChromebox Script + ACPI Issues with Touchscreen

Bug Reports Firmware Bugs
1

Hello everyone,

I’ve encountered a few issues while using the MrChromebox script to flash firmware on my device and I would appreciate any help or advice. Below are the two main problems I’m facing:

Issue 1: Black Screen and Bricking After Flashing Full ROM

I used the MrChromebox script to flash the Full ROM and encountered the following issue:

  • After flashing, the device shows a black screen on boot and does not start up.
  • The device became bricked, and I couldn’t access any interface.

Today, I checked the updated firmware in the script and found that the firmware has been updated to 2025-04-30 version. I flashed this version again, but the black screen and bricking issue persists.

My device is a Poin2 Chromebook 11P (internal model foob360, using Intel Gemini Lake N4120 CPU). I have tried flashing other versions of the Full ROM before, with the same result.

Issue 2: ACPI Issues with Touchscreen After Flashing Legacy ROM

After flashing the Legacy ROM using the script, the system boots up, but I’m experiencing ACPI issues with the touchscreen. Specifically:

  • The system logs show i2c_hid_acpi errors, indicating problems with the ACPI configuration of the touchscreen.
  • The touchscreen is not recognized correctly and does not work at all.

I suspect that the issue might be due to the ACPI table being incomplete when using the Legacy ROM, preventing the touchscreen from being properly initialized.

Attachments

Device Information

  • Device Model: Poin2 Chromebook 11P
  • Internal Model: foob360
  • CPU: Intel Celeron N4120 (Gemini Lake)
  • Firmware Version: 2025-04-30 Full ROM version (flashed)

Summary and Request for Help

  1. I would appreciate any solutions or suggestions regarding the black screen and bricking issue. Is this caused by firmware incompatibility or is there a need for a different configuration?
  2. For the ACPI issue with the touchscreen after flashing the Legacy ROM, are there any users who have experienced this, and can anyone provide a fix or patch?

Thank you so much for your help!

Please feel free to reach out if you need any further information or clarification. Thank you!

2

  1. did you try reflashing with a SuzyQ cable? Can you flash a debug build and provide log output? All the GLK boards I’ve tested work properly

  2. ACPI issues with the stock firmware are not resolvable without using something like OpenCore to rewrite the ACPI tables. RW_LEGACY firmware is just a bootloader, the stock firmware is the problem here.

3

Thanks for the response!

  • I did use the SuzyQ cable and successfully recovered the system.
  • I’m happy to provide debug logs, but could you please clarify where to find them after flashing a debug build? and where can I download a debug build ? Should I capture output from the serial console, or does Coreboot store logs somewhere on disk?
4

actually, I think I see the issue – the FOOB images appear to be missing the VBT, which is necessary for display init. I’ll rebuild any GLK images missing it and update them, and post here after I’ve done so

5

fixed build up

6

Hi,

Thanks a lot for the quick fix! I can confirm that with the updated ROM, the black screen issue is gone and the system now boots properly. Also, the previous ACPI error related to the touchscreen seems to have been resolved as well.

I’ll continue testing the system in the next few days to verify overall stability and check for any remaining issues, especially around suspend/resume and peripheral support.

Really appreciate your support and efforts in maintaining these builds!

Thanks,again~

1 Like
7

hi,everything goes well in last few days。such as the sleep /wake-up ，pad mode，auto rotation of the screen ，etc.
thanks for your help again. @MrChromebox

1 Like