New scripts (in 2026) can't continue on 'Install/update' on Google Pixel Slate (NOCTURNE) & disable Sleep mode/PowerBtn

[Linuxfin]

Thank you so much for your work with Chromebooks.

Please help me get the new (2026) versions of your scripts working on

• Google Pixel Slate (NOCTURNE)
  and
• Acer Chromebook 14 (EDGAR)

all chromebooks (NOCTURNE and EDGAR) have already installed Stock ChromeOS w/RW_LEGACY
(EDGAR now is EOL)

but both 2026 versions of ChromeOS Device firmware utility script (2026-02-19 and 2026-01-25) on both devices (NOCTURNE and EDGAR):

1. After a standard start - and a standard exit from the script (even if no script functionality was used) :

• the sleep mode is cancelled(or do nothing) both when closing the Chromebook lid and when pressing the Power button, to reenable sleep mode and power button - need to restart device.

2. Google Pixel Slate (NOCTURNE)
   Platform - Intel KabyLake
   fwType: Stock ChromeOS w/RW_LEGACY
   Fw ver: Google_Nocturne.10984.90.0 (06/04/2019)

if choose "1" - Install/update RW_LEGACY firmware
then "L" to choose Legacy BIOS(SeaBIOS)
then "Y" to continue
then "N" to default boot from internal storage

results:
Downloading RW_LEGACY firmware update
(seabios=kbl_18-mrchromebox_20250227.bin)
then script succesfully prints 1st string with "#" and resulted with 100.0%
#####################################################################...### 100.0%
but in 2nd and last string - scripts prints only 2# "##" and resulted with 0.9%

... 0.9%

and THAT IS ALL - script is "waiting" here
(you can exit it via ctrl+z)

Thank you again.

[MrChromebox]

the script disables power management to prevent the system from going to sleep while the firmware is being flashed, it's expected that you reboot after flashing.

not sure why it would hang on the download, can't reproduce here

[Linuxfin]

Thank you very much for your quick response.

Now it's clear why the sleep mode switch disappeared.

I would be very grateful if you could figure out how to solve the issue of installing and updating firmware using new 2026 scripts on my Google Pixel Slate (NOCTURNE).

I dont know is it important or not (for your script)
but my chromebook (NOCTURNE) is automatically updated to version Google ChromeOS 145.0.7632.216

and after some recent system restore/install, the system changed the security rules and no longer allows the chronos user to have a blank password and constantly asks for it.

[MrChromebox]

there's only a password on chronos if you incorrectly enabled 'ChromeOS debugging features', which the instructions tell you not to do

edit: just tested on my NOCTURNE here, fresh switch to developer mode on R145, no issues with chronos or flashing RW_LEGACY firmware

[Linuxfin]

there's only a password on chronos if you incorrectly enabled 'ChromeOS debugging features', which the instructions tell you not to do

Unfortunately, this dialog (enable 'ChromeOS debugging features') appeared for the first time when I was recently recovering the system and Confirm Disabling OS Verification to get Developer Mode,
and there was no opportunity to use any specialized instructions on this matter.

Please tell me - the problems in my NOCTURNE consists of:

---

1. pausing on installing and updating firmware using your new 2026 scripts

2. cant install ChromiumOS developer tools via standard "sudo dev_install"
   that starts ok but after downloading necessary files - then prints red:
   "!!! Problem with sandbox binary. Disabling.

is previously - Enabled "ChromeOS debugging features" (and password for user chronos)?

[Linuxfin]

there's only a password on chronos if you incorrectly enabled 'ChromeOS debugging features', which the instructions tell you not to do

edit: just tested on my NOCTURNE here, fresh switch to developer mode on R145, no issues with chronos or flashing RW_LEGACY firmware

Thank you very much for such testing.
If it is possible, tell me please - can you successfully use "installing and updating firmware" on your NOCTURNE
after you have already installed firmware on it via this method (and after rebooting also) ?
(such situation is more close to my).

[MrChromebox]

If it is possible, tell me please - can you successfully use "installing and updating firmware" on your NOCTURNE
after you have already installed firmware on it via this method (and after rebooting also) ?
(such situation is more close to my).

yes, I switched to dev mode, updated RWL (seaBIOS), verified it worked, then updated RWL with edk2, verified it worked, updated the edk2 payload on my script, re-updated RWL with the new edk2, and verified it worked. so 3 RWL updates.

I would powerwash and start fresh

[Linuxfin]

If it is possible, tell me please - can you successfully use "installing and updating firmware" on your NOCTURNE
after you have already installed firmware on it via this method (and after rebooting also) ?
(such situation is more close to my).

yes, I switched to dev mode, updated RWL (seaBIOS), verified it worked, then updated RWL with edk2, verified it worked, updated the edk2 payload on my script, re-updated RWL with the new edk2, and verified it worked. so 3 RWL updates.

I would powerwash and start fresh

Thank you so much for your help.
Please excuse me for my detailed question (I'm a little confused)

Do you have (after switching to dev mode):

1. installed SeaBios on your NOCTURNE via your script
2. choose "install/update and also choose SeaBios" on your NOCTURNE with already installed SeaBios ?
   ...
   in previous steps1 and 2 - I have described - my steps (with additionally Enabled "ChromeOS debugging features")

[MrChromebox]

I did not install SeaBIOS twice, but the installed firmware has no bearing on anything. Per your msg above, the download hung -- that has nothing to do with having flashed anything previously

[Linuxfin]

If it is possible, tell me please - can you successfully use "installing and updating firmware" on your NOCTURNE
after you have already installed firmware on it via this method (and after rebooting also) ?
(such situation is more close to my).

yes, I switched to dev mode, updated RWL (seaBIOS), verified it worked, then updated RWL with edk2, verified it worked, updated the edk2 payload on my script, re-updated RWL with the new edk2, and verified it worked. so 3 RWL updates.

I would powerwash and start fresh

I have done setting NOCTURNE to Normal Mode and then Setting it to Developer Mode

user chronos now have no password (OK)

But when I tried to install already new version (2026-03-19) of your script it:

1. runs OK on my (EOL) EDGAR with old ChromeOS (R103-14816.131.0) without any errors , like previous 2026 versions (2026-02-19 and 2026-01-25) of your script

BUT IT RUNS OK on my old EDGAR BECAUSE my old EDGAR ALREADY HAVE files
cbfstool 341552 bytes
cbfstool.tar.gz 152245 bytes (with cbfstool 341552 bytes inside it)

these files are collected in /usr/local/bin in my EDGAR from starting your previous scripts
and if delete then in /usr/local/bin - my EDGAR also stops on "Downloading required tools..." like my new NOCTURNE

2. runs and have new Errors on my new/fresh NOCTURNE with new ChromeOS (R145-16552.59.0)
   in "Downloading required tools..."
   Error downloading cbfstool; cannot proceed Unable to download cbfstool utility; cannot continue MrChromebox Firmware Utility setup was unsuccessful ...

NOW - BOTH EDGAR and NOCTURNE after starting your script - downloads only 12288 bytes of file cbfstool.tar.gz into /usr/local/bin (May be something wrong with my internet connections ...)

After I have manually download cbfstool.tar.gz to /usr/local/bin/ and unpack cbfstool. from it - new script again starts on my NOCTURNE and everything became the same as it was at the very beginning of my appeals
(script stops on second downloads:
Downloading RW_LEGACY firmware update
(seabios=kbl_18-mrchromebox_20250227.bin)

and in the /tmp folder file kbl_18-mrchromebox_20250227.bin is again only above 12 kb length...

Please, if it possible , help me with your cool script - to run it well on my fresh NOCTURNE - so to can successfully choose Install/update firmware method on your script .