login issue when installing "Could not mount cryptohome"

[AdeeGaming01]

I'm having issues using the USB to install onto an SSD, when I try logging in I get a Please wait... screen for a few minutes, after which there's a "Could not mount cryptohome" error. I've tried turning TPM on or off same results Brunch and ChromeOS ver: 132 CPU: Ryzen 5 5600x GPU: RX 7900XT Kernel ver: 6.1 Mobo: MSI B450 Gaming Plus Max (I assume that's not relevant, but I've had instances where it was the culprit with some issue) USB should be about 14.4 GB in size

[nunolu]

Hi, I have the same issue with r132.

Tried power wash also not working

Browse as guest not possible

[laconeo]

The same happens to me with a lenovo ideapad slim 3 14anm8 con ryzen 3

[RicardoRien]

I'm facing the same issue. Intel core i 7 8th Gen. Latest version of chromeOs and Brunch.

[PeterDD9PS]

Try a different recovery file! With the recovery file “sentry” I had the same error. For my Lenovo Yoga 260, the recovery file “nami” works perfectly without any errors!!!

I initially used the recovery file “sentry” for a Lenovo ThinkPad Yoga 260 (Intel® Core™ i7-6600U, Intel® HD Graphics 520), because its hardware is very similar to the Lenovo Thinkpad 13 Chomebook. But I could not fix the error “Could not mount cryptohome” with this recovery file. Only a guest login works. The Google account can then be accessed with the Chrome browser. If you then log out and try to set up an account again, the error “Cyptohome corrupted” appears. There is no way to fix the error with “sentry”.

My solution: I have tried several other recovery files. Of course, the recovery file “reven” works in combination with the brunch framework. The login also works here - even with the TPM 2.0 module deactivated. However, the PlayStore is missing in “reven”. You can also install the recovery file “reven” without the brunch framework. But with the framework, the root shell works via “CRTL-ALT-F2” and the developer mode also works.

For my Lenovo Yoga 260, the recovery file “nami” works perfectly!!! This recovery file also supports the hardware of my Yoga 260 and, unlike “sentry”, the error message did not appear, i.e. I was able to log in successfully:

[dineshdhotrad]

✅ FIXED: “Could not mount cryptohome / login loop” on AMD Ryzen laptops

Hi everyone,

I was hitting exactly the same symptoms described in this thread:

• ChromeOS boots but stalls after signing in (or Guest mode never proceeds)

• Repeated “Could not mount cryptohome” errors in VT-2 log

Hardware that failed: Lenovo Legion 5 15ACH6H – Ryzen 7 5800H (Zen 3 + Vega 8)

After a lot of testing I found the root cause and a repeatable solution.

Why it happens

ChromeOS recovery images are board-specific.
Using an image built for the wrong SoC (e.g. rammus, volteer, skyrim) leaves AMDGPU and cryptohome in an undefined state, which triggers the login loop.

Working solution

1. Match your CPU generation to a real Chromebook.

   • Ryzen 5000-C series Chromebooks = guybrush board

   • Example devices:
     – HP Pro c645 G2 Chromebook
     – Acer Chromebook Enterprise Spin 514 (CP514-3WH series)

2. Download the correct recovery image.
   https://cros.tech/board/guybrush/ → grab the latest stable ZIP and extract the .bin.

3. Pair it with the latest Brunch (r125+).
   Brunch r125 ships a 6.1 kernel that already supports Zen 3/Vega.

4. Standard install procedure (USB test or chromeos-install.sh single-boot):

   bash
   sudo bash chromeos-install.sh \
        -src chromeos_xxx_guybrush_recovery.bin \
        -dst /dev/sdX           # your SSD
   # optional first-boot GRUB flags
   #   amdgpu.gpu_recovery=1 mitigations=off
   

5. Reboot → Brunch GRUB → ChromeOS wizard.
   Login and Guest mode now work; no cryptohome errors. Play Store also launches on my system.

Results

Item | Status -- | -- Boot / login | ✅ Works Guest mode | ✅ Works Play Store (ARC++) | ✅ Opens & installs apps Suspend / resume | ✅ Functional (slightly higher idle drain vs real Chromebook)

Screenshots attached below.

Proposal

• Add a short “CPU → Recommended board” table to the Brunch README.

• Close this issue as resolved with the procedure above.

Hope this saves others hours of trial-and-error.
Thanks to @sebanc and all contributors for keeping Brunch alive!

— Lenovo Legion 5 user

[github-actions[bot]]

Unfortunately, this issue could not be resolved and is closed due to inactivity.