I have a Pixel 5, installed Graphene over a year ago, and used it ever since with no issues whatsoever.

Today I turn the phone on as usual, but it booted into this "fastboot mode", and is stuck there. no matter what buttons i push, hold, etc, it is stuck on this screen. it gives some info about the device, and states "Device state: locked" and "Enter reason: no valid slot to boot".

Is there anybody here with any expertise regarding why this happened and how to fix it? I've tried some things from Google's website regarding flashing OTA, but the computer does not detect the device when plugged in.

very disappointed, as i loved this graphene system, but i'm wondering if it has now cost me a phone. I don't imagine I could get far with google support, since i installed an OS that they don't support. Any help would be appreciated. Thank you.

Have you tried holding the power button for 60 seconds to force a reboot of the device?

If you can restart the phone, you may then be able to get to recovery mode from the fastboot menu.

a year later

i have this too, with a Pixel 5, i can't find anyway to recover from this stage.. and i have many files and contacts on the phone i desperately need to get... does anyone have a fix?

    Casper91 Can you confirm it is actually the exact same issue, that is, does it also say "Device state: locked" and "Enter reason: no valid slot to boot" for you too? If not, what does it say?

        ryrona with one exception it says "drive boot error" but stuck on bootlaoder, and all the Volume button/scroll menu options are simply restarting the device.

            Casper91 Oh, that sounds scary.

            Just to confirm, if you use the volume buttons to select "Recovery" and click power button to enter it, your phone also just reboots right back into the same fastboot menu you were at?

            If that is the case, I am afraid you are out of luck. Your device probably suffer from a hardware failure, possibly a disk failure. So don't expect any data to be possible to rescue. You can try sending the device in for repair, but probably they cannot do anything, and you will need to get a replacement device.