Hi, I have an Acer Chromebook Spin 311 (R721T). My chrombook is Admin Locked ? and would like to be able to install linux instead of chrome. I see my Spin 311 R721T in the supported devices list (MrChromebox.tech) with a HWID/Board Name of KASUMI360 but it does not appear available as a downloadable firmware from MrChromebox.tech.
When looking at the sources.sh list, Kasumi is there but not Kasumi360 (export coreboot_uefi_kasumi=“coreboot_edk2-kasumi-mrchromebox_20240914.rom”)
I even attempted to compile a custom firmware following the steps “Compiling Your Own Firmware” but when i reach step #6 “Build the firmware” with command (linux) $ ./build-uefi.sh kasumi360 it returns " cp: cannot stat ‘’: No such file or directory. It is obviously not available as a rom. I verified my setup is up and running with the same command (under linux) $ ./build-uefi.sh kasumi which proceeded to build the rom and completed without error.
Is Kasumi360 going to be added as a downloadable rom or are we supposed to use Kasumi for boards labeled kasumi360.
Is there anywhere i can download a stock kasumi360 rom or are there any instructions on how to edit the existing rom to remove the “admin” or “enterprise enrolled” option in rom using the Ch341a programmer which i do have.
there’s no difference between board X and board X360 other than one is a clamshell and one is a convertible. They use the same firmware. My script handles this when processing the HWID/board name
MrChromebox, Thank your for your quick response and also all the work that you put into your script.
I was following your (unbricking) guide which calls for the rom to be downloaded and ready so now i know that coreboot_edk2-kasumi-mrchromebox_20240914.rom is the correct rom for me.
If this method does not work, i will read over the docs about using your script and do that route.
I also came a cross an old Redit post ( https://www.reddit.com/r/chrultrabook/comments/hfi0sh/acer_chromebook_spin_311_does_it_work_under_linux/ ) of 5 yrs ago were a MrChromebox (beleive you are one and the same) replayed to a user asking about the if Linux works on Acer Spin 311 and your response " in short, it’s going to run like crap, and i don’t recommend it." later you said, “all modern Chromebooks are terrible for running Linux natively, not recommended at all.”
Does your opinion still how true or did you make improvements to your firmware/roms so that linux runs natively well?
Regardless, this project is just for fun/leaning so i will flash the firmware anyway and play around with it. My bios/rom chip is (winbod 25q128fwsf1923) and Im waiting on my 1.8 v adapter before i can attempt to reprogram it.
Thank you for the clarification. I think i understand your sentiment. 4 or 5 years ago someone would have been buying the spin 311 new or newused and i agree it would be bad idea to buy it and turn it into a linux or windows. Especially when you run the risk of not having your audio work after installing linux on a chromebook and having to trouble shoot that.
Today you can find older model chrome devices being sold for dirt cheap, given away or recycled etc… its cool that (with your script) we have the ability to run alternate OS on them, tinkering with them and squeezing a little more life out of them.
I got my 1.8 v adapter today and began the process to program my chip. Last I knew my Chomebook was Enterpise enrolled but its just been sitting around for over a year. I didnt bother to log in and check its status or OS version number etc or put it into Developer Mode. My intention was to wipe it and install the custom rom so i could load Linux onto it.
Using a laptop with Linux Mint i followed the steps at MrChromebox.tech under Help and Support Unbricking. After completely removing the Motherboard from the case, I connected the ch341a and was able to read the chip. I then created a backup of my rom (backup.bin) then using my own previously compiled firmware if extracted the persisting Vital Product Data and Hardware ID (as per the guide).
After writing the VPD and HWID to the new rom, I flashed it to the chip. Here is were i got several Write Failed Errors. Apparently the (software?) Write Protection was still in place. I let the process finish and even tried it again. Reading back over the docs, I believe not putting the book into Dev Mode was the problem. I put the MB back in case, connected everything and powered on but i was landing on the page that said no ChomeOS found, It wouldn’t boot. After googling how to put the book in to Dev Mode, I tried the Esc, Refresh, Power followed by the Ctrl D keys and I believe it took affect. I still could not get it to boot or even usb boot an Ubuntu live cd.
I decided to take it all apart and reflash the rom with my Backup.bin file. I was relieved to see that the process completed without any write errors. Put the MD back in and powered on. The chromebook booted straight to the white splash screen indicating OS verification OFF. By this time i have read enough to know to press Clrl D to allow it to proceed to boot.
I was then presented with the setup menus and it gave me the option to use it as a personal, student or enterprise device. I set it up as a personal device and finished the setup process to get to the desktop. I later checked the lower right corner in the clock menu and see that there is NO icon showing that the device is Managed.
Now that i have an unmanaged Chromebook, I guess i will leave it this way and forego installing Linux. I have tried some games in the Play store and most games either didn’t play or were slow. Jellyfin seems to play the videos just fine but did notice that the server was transcoding the videos instead of the player direct playing the movies.
I will leave it here and hope that sharing my process will be of some help to anyone attempting something similar with an old Acer Spin 311.