Intermittent Boot Issues on Pixel 9a with GrapheneOS. Should I reflash GOS

pa-pol12

Hey, this is my first post. I want clarify I used IA for logs, english isnt my first language. If its not allowed at all please tell me and I will delete this post.

I had a problem where my Pixel 9a with GrapheneOS acted like it was completely dead. It wouldn’t show any signs of charging or turn on even after being plugged in for an hour.
After googling I tried a forced reboot by holding all three buttons for 20 seconds, and the phone finally turned on and showed google then GOS logo then the SIM PIN screen. However, it shut down completely again after 5 seconds. I had to force reboot several times because each time it would die again and couldnt turn on with just normal boot buttong but had to force reboot. after 3 or 4 times it finally booted normally and didnt go off. Since then, it has stayed on fine—no unexpected shutdowns, even after normal reboots.

My quesiton is: Are these errors harmless rr do they indicate that my GrapheneOS installation is corrupt or incomplete? Should I completely reflash GrapheneOS? or can I safely ignore these errors since the phone is working well now?
I’ve been using GrapheneOS on this new Pixel 9a for two months and this is the first time I have seen these issues.
Thanks

Errors from logs using IA after the last reboot.

W PackageSettings: Missing permission state for package com.whatsapp on user 10 W PackageSettings: Missing permission state for package com.x8bit.bitwarden on user 0 W PackageSettings: Missing permission state for package com.google.android.gms on user 10 W PackageSettings: Missing permission state for package org.telegram.messenger on user 11 W PackageSettings: Missing permission state for package com.android.vending on user 10 W PackageSettings: Missing permission state for package app.grapheneos.camera on user 11 W PackageSettings: Missing permission state for package com.android.contacts on user 10

am_proc_died: [Process Name=com.android.permissioncontroller]

E [GF_TA][E][gf_tee_storage][trusty_file_open] storage_client.c, 62, entry. storage_client: send_reqv: failed (-42) to send_msg E [GF_TA][E][gf_secure_object][gf_so_load_persistent_object] so(finger_10_1.so) not exist E [GF_TA][E][gf_fpcore_common][fpcore_load_finger_template] exit. err=GF_ERROR_OPEN_SECURE_OBJECT_FAILED

E JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 1056768) W BpBinder: Large outgoing transaction of 1056768 bytes, interface descriptor , code 1 was sent W ActivityManager: Too many transaction errors, throttling freezer binder callback.

`E RecoverableKeyStoreGms: java.lang.SecurityException: Caller 10159 doesn't have RecoverKeyStore permission.: Neither user 10159 nor current process has android.permission.RECOVER_KEYSTORE.

E Backup : [BackupManagerWrapper] Google Play Services doesn't have permission android.permission.BACKUPtrusty: WARN: system/keymint/ta/src/lib.rs:1279 failing DeviceBegin request with error Hal(KeyRequiresUpgrade, "system/keymint/ta/src/lib.rs:438: keyblob with old vendor patchlevel 20251001 needs upgrade to current 20251005")lmkd: Kill 'com.dgt.midgt' (3281), uid 10245, oom_score_adj 945 to free 230240kB rss, 0kB swap; reason: low watermark is breached
lmkd: Kill 'com.google.android.apps.docs.editors.sheets' (3615), uid 10000, oom_score_adj 935 to free 307656kB rss, 0kB swap; reason: low watermark is breached
lmkd: Kill 'com.android.localtransport' (3939), uid 1000, oom_score_adj 935 to free 180164kB rss, 0kB swap; reason: low watermark is breached`

de0u

pa-pol12 Are these errors harmless rr do they indicate that my GrapheneOS installation is corrupt or incomplete?

It's not clear to me what might cause those log messages. Unfortunately, only an expert developer can be sure which parts of a system log are important. An LLM can make a guess, but it can be wrong. And it might even make up lines that weren't in the original log.

Nothing there looks to me like an indication of compromise. If anything it looks more like bad hardware (though it doesn't look very much like bad hardware).