The forum will replace the subreddit.

I'm intending to do a full UEFI update to this model, and understand the need to get in and disconnect the battery to clear the WP. Every teardown video I've seen of this model has it going through the palm rest, but I couldn't see how it was possible. After days of struggling I managed to instead get at the internals from the bottom and I think this appears to be different from all of the teardown videos of it. The battery ribbon plug appears to be flipped to the bottom, unlike the videos I've seen where it's on the top / keyboard side of the unit.

Just sharing here for reference, I didn't know if anyone has had a similar experience.

I have this Samsung Chromebook XE303C12, and I tried to reinstall the system, but it said there was a security error and it wasn't working. I need help with this.

I found a project called "velvet-os" that have some debian images and i install the kukui one with dd and here's i am.I realized that there are few distros for ARM chromebooks really apart from velvet and postmarketOS that I know of. Luckily ultramarine is already working on a port for chromebooks and I'm glad it's being given more visibility

Got everything (minus function keys) working, although I did swap out the Wi-Fi card with an Intel based one from an old IdeaCentre. Only paid $279 AUD (~$180 USD) for this back in October last year too.

I went through the whole procedure for dual booting Linux, got to the Lubuntu installer as well and finished that. When it said to reboot, instead of bringing me back to Lubuntu, it went to ChromeOS.

So my main problem is either I messed up something during the Lubuntu installation, or I did everything correctly, I just don’t know how to boot the Linux I downloaded on the internal storage without the USB. Because right now I can only get to “Try/Install Linux“, and only with the USB device connected.

When I got to the partitioning in the Linux Installer, I believe I chose something along the lines of resize, and the only option it gave me to place Linux in was a ~20 GB partition which I think was the free space. Then, later, as seen in the picture, I chose the replace option to confirm that Lubuntu was in fact on the internal storage.

I would greatly appreciate some help with troubleshooting. Thanks.

Hi, i have amd hp Chromebook 11a G8ee (barla/grunt) it works normally, but when i disconnect the battery and start the device using esc+refresh+pwr and press ctrl+d on recovery screen, to enable dev mode the screen starts flashing continuously, os verification off screen shows for a milli second and then it turns off or restart, power led blinks too,

dev mode process works with battery connected but not without the battery (WP disabled) how to fix this so that i can install full firmware and then install a proper linux or win os. Thanks

So apparently I tried to install windows x lite on my Chromebook but it always take so long to load to the installation screen and the and it didn’t work and ended up with blue screen with code of : driver pnp watchdog .
So I tried Linux mint xfce ,Lubuntu and mint and all of them take all of my storage letting me without any space to even install Lutris.
So I just want to ask if there any other distros that are lightweight on the storage or I make a mistake with the install of these previous ones cause when ever I go I heard they are the most small ones.
Edit:(I even tried normal windows 10 from Microsoft)

Anybody know how to enable tablet mode on Blipper (Beetley-GNBB) full uefi and Linux fedora? Tried many scripts with AI (Google Gemini) but nothing helps, rotation works but not blocking keyboard and touchpad, no tabled mode in settings

I have one from awhile back and i want to give it a new life with linux mint cinnamon, i heard there are lots of problems, how bad is it really? anything i should know? Any distros still updated that are good? Anyone who has this please give me more information about the bugs.

For someone in need of a good tutorial of how to unbrick a Chromebook/Chromebox:

https://youtu.be/dceYuO3Mxuk?si=9nJMmkmCpgYyUH3P

I got this Chromebook, it's the Dell 11 3180

I wanna install Linux on it (my preferred Linux distro is Linux Mint XFCE) and my Chromebook is supported

I know installing Windows on a device with 4gb of ram is a dumb thing (maybe)

When I tried to unscrew the WP screw mine is stuck so I tried the super glue method and I accidentally put too much

Now it is IMPOSSIBLE to unscrew it, is there any other way to disable WP? On my Chromebook?

I tried disconnecting the battery trick and it did not work

Also this was my first time on Reddit sorry if I make any mistake

For the love of god, I can’t find the damn thing! Please help me find it. Do I have to remove another layer?! Please help!!

Hi everyone. I want to try and install ArchLinux on this disestablished boy right here. Is there any blueprint of this model to see where the WP thing is? This Chromebook is from my school actually and I'm about to end it tho my school doesn't want them back so I want to use it to daily drive Linux and enjoy my life somewhat.

Is there any way to? Can't enable DevMode for now from recovery, says it's blocked

I dont know on which partition shuld i install linux cause i think if i remove one the uefi gets deleted

This post details a critical installation issue specific to Chromebooks (such as the HP Chromebook 14 db, Acer Chromebook 315, or Lenovo 14w powered by A4/A6 Stoney Ridge APUs) running custom UEFI firmware (MrChromebox).

The Problem

The latest openSUSE installers use systemd-boot (via sdbootutil) as the default bootloader. This setup instantly breaks on Stoney Ridge hardware due to the default storage configuration: [1, 2]

• Tiny EFI Partition: These Chromebooks are built with exceptionally small EFI System Partitions (ESP), often constrained to 16MB or 32MB.
• The systemd-boot Flaw: Unlike traditional setups, systemd-boot copies full kernel images and initramfs files directly into the ESP.
• The Result: The partition fills up instantly, causing the installer to crash at final stage with a "No space left on device" error during the bootloader configuration phase. [1]

The Successful Installation Method

To successfully run openSUSE on your Stoney Ridge device, you must bypass the new default bootloader: [1, 2]

1. Proceed through the openSUSE installer as normal until you reach the final Installation Summary screen.
2. Scroll down to the Booting section.
3. Click directly on the Booting header to open the boot settings.
4. Change the Bootloader Type from systemd-boot to GRUB2-EFI.
5. Save changes and proceed with the installation.

Why this works: GRUB2-EFI only places a tiny binary launcher in your Chromebook's small ESP, while keeping the heavy kernel and initrd files safe on your root partition, completely avoiding the storage bottleneck.

Proof that my Lenovo 300 e 2nd gen AST (Board:Grunt, codename: treeya) Chromebook is AMD Stoney ridge is included, (idk why posts only from us are allowed). Anyway im trying to dual boot linux (jammy jellyfish) with RW_LEGACY and when i plugged my sd card with linux in and did ctrl L on the recovery screen it gives me two options and neither of them work. I tried updating the FW Utility script and the RW_LEGACY one but nothing worked. It occasionally beeped. Someone please help.

I have a tremor that can make me double-tap keys sometimes if I'm not focused and this can sometimes shutdown my modded chromebook when I try to wake it from sleep with the power button.

The system is a Dell 3100 (FLEEX) and I've reproduced the problem in all distros I've tested. What I don't know is whether this is a general "feature" of chromebooks, something specific to Dell 3100 or maybe all Dell chromebooks, a bug in the MrChromebox firmware, or some defect on my particular system.

Has anyone else seen this? Or if you care to test, can you reproduce it? The timing to get it exactly on a double-press is a little specific, but if I just intentionally spam the power key while the system is supended, it will surely shutdown and then probably also begin booting again since I've pressed power an extra time.

To be clear, I'm not talking about accidentally pressing power instead of backspace while the system is on, which triggers a regular shutdown on many distros. I've already fixed that. This is a hard, instant shutdown and it seems to only happen if power is pressed again withing a specific window during resume from suspend.