Hello everyone,

I'm seeking help to solve a problem that self occured:

Device​

• Device: Google Pixel 8
• Android version: CalyxOS / shiba-ota_update-25608200 / Android 15 (BP1A.250505.005)

Issue Description​

The phone can boot normally without issue When I unlock it after 1st boot (with code), it enters an crash loop every 2-3s.

I woke up a few days ago in the morning, unable to use the phone anymore. It spends the night in airplane mode. It wasn't charging and battery level was approx. 70-60% It was working normally the day before. I'm unable to say if an update has been installed or not - I hadn't any message noticing an update.

I'm under CalyxOS for a year now, very very happy with it. I simply don't uderstand what's happening here.

The issue seems very similar to this:https://xdaforums.com/t/fake-restart-loop-after-unlock-tips.4724977/

Troubleshooting​

Initially I didn't even had USB debugging, but afterHUNDREDS of tries, I managed to go toSettings > System > Developper > USB debugging in less than 2 seconds (which is kind of a record, not mentionning the UI was pretty unresponsive).

But now, ADB is detecting the phone:

• Only after 1st unlock (which leads to crash loop)
• Until the next crash
• After a new reboot + unlock and replug of USB cable

In other words, I can use ADB for 2-3s maximum

I did some extraction usingadb logcat. Findings so far:

• Crash is due to OutOfMemoryError:

system_server: Throwing OutOfMemoryError "Failed to allocate a 56 byte allocation with 923824 free bytes and 902KB until OOM, target footprint 536870912, growth limit 536870912; giving up on allocation because <1% of heap free after GC." (VmSize 22379880 kB)

• It cause Fatal exception in various system process:

AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: <proces (process observed across several reboots:binder:1371_10,android.usagestats,android.ui, but i think it can be anything). It makes me think that something else is eating all memory.

• Crash also occurs in Safemode

• Another interresting warning:

I trusty : WARN: system/keymint/ta/src/lib.rs:1190 failing DeviceConvertStorageKeyToEphemeral request with error Hal(KeyRequiresUpgrade, "system/keymint/ta/src/lib.rs:422: keyblob with old OS version 140000 needs upgrade to current 150000")W keymint-hal-trusty: kmr_hal: HAL: command DeviceConvertStorageKeyToEphemeral failed: -62

My top priority is to retrieve Data, as I have no recent backup.
A stable ADB access would be OK.

Any help will be highly appreciated
Thank in advance!

NB: I opened on issue at CalyxOS Gitlab, no news so far:https://gitlab.com/CalyxOS/calyxos/-/issues/3397

 

You can also try to flash a recovery (e.g.orange fox) to have access to your files. But that's just what i would try, didn't do it myself on the P8. No guarantee

 

McFlypants said:

You can also try to flash a recovery (e.g. to have access to your files. But that's just what i would try, didn't do it myself on the P8. No guarantee

Click to expand...

Click to collapse

orange fox can't decrypt data

 

Thank you for your replies guys, I'm feeling a bit less alone in this struggle

McFlypants said:

Did you try reflashing the same rom version you are on?

Click to expand...

Click to collapse

Yes of course, the 1st try was to sideload the same image. No change unfortunately
I hope downgrade would have been possible...
I must wait for the stable release. I though about sideloading the beta, but I'm afraid it will more hurt than solve the problem...and again without the possibility to rollback.

McFlypants said:

You can also try to flash a recovery (e.g.orange fox) to have access to your files. But that's just what i would try, didn't do it myself on the P8. No guarantee

Click to expand...

Click to collapse

I did discover OrangeFox after searching TWRP for Pixel.
I have no real feeling about is maturity, and at the moment I prefer to keep this for a last resort. Do you know if its widely used?

And indeed, it can't decrypt data and I have FBE enabled (I'm really thinking of disabling this when I manage to get out of this)

Finally, to be able to flash it, I need to enable OEM unlock...which require to go to the dev menu in less than 3s...again

 

If nothing else helps and before you wipe the Data Partition, you can try this command:

adb shell am start-foreground-service -a android.security.KEYSTORE_FORCE_UPGRADE

Click to expand...

Click to collapse

This command forces an upgrade of the Android Keystore system, which may resolve key-related crashes (like the KeyRequiresUpgrade error in your logs).

 

Doc Sniper said:

If nothing else helps and before you wipe the Data Partition, you can try this command:



This command forces an upgrade of the Android Keystore system, which may resolve key-related crashes (like the KeyRequiresUpgrade error in your logs).

Click to expand...

Click to collapse

Unfortunately, this does not seems to be available on my CalyxOS:

.\adb.exe wait-for-device shell am start-foreground-service -a android.security.KEYSTORE_FORCE_UPGRADEStarting service: Intent { act=android.security.KEYSTORE_FORCE_UPGRADE }Error: Not found; no service started.

 

Z3r0000 said:

Unfortunately, this does not seems to be available on my CalyxOS:

.\adb.exe wait-for-device shell am start-foreground-service -a android.security.KEYSTORE_FORCE_UPGRADEStarting service: Intent { act=android.security.KEYSTORE_FORCE_UPGRADE }Error: Not found; no service started.

Click to expand...

Click to collapse

Not good. Try this variant, I hope it works:

adb shell am start-foreground-service -n com.android.keychain/.KeyChainService -a android.security.KEYSTORE_FORCE_UPGRADE

Click to expand...

Click to collapse

Edit: You can also try other commands:

adb shell service call android.security.maintenance X

Click to expand...

Click to collapse

or

adb shell service call android.system.keystore2 X

Click to expand...

Click to collapse

You can experiment with different values for X in the command, but be cautious — this may cause unintended system behavior or data loss.