Launcher crashes, can't access to the system menu for oem unlocking

oups

AlphaElwedritsch You have to unlock the bootloader in fastbootd

Thanks for your reply.
Yes but first I have to enable the OEM unlocking, via developper option, in the settings menu, that crashes

other8026

oups If I were in your situation, I'd try factory resetting from recovery. After a factory reset, hopefully the settings app stops crashing so you can enable bootloader unlocking.

Instructions on how to do that are here (under "with your phone's buttons") https://support.google.com/pixelphone/answer/4596836?hl=en#zippy=%2Cwith-your-phones-buttons-advanced)

oups

other8026 If I were in your situation, I'd try factory resetting from recovery. After a factory reset, hopefully the settings app stops crashing so you can enable bootloader unlocking.

I did,
But still the same problem occurs after that,
The system seems corrupt, I have no access to the "system" menu in settings, it crashes still when I try to enter it.
So can't enable oem unlocking.

Looks like my only way in is an ADP update using only update signed by the same key I have used to build at first.

oups

de0u What happens if you boot in safe mode?

Hi,
When I enter the bootloader, I have rescue mode and recovery mode, I can't see any difference between those two option, both give a "no command" screen, and more options when I press power and vol up.
I don't see any safe mode
the "more options" are :

reboot system now
reboot to bootloader
enter fastboot
apply update from ADB
wipe data
view recovery logs
run graphic test
run local test
power off

de0u

de0u What happens if you boot in safe mode?

oups When I enter the bootloader, I have rescue mode and recovery mode [...]

But that is not safe mode. Here are directions for safe mode: https://support.google.com/pixelphone/answer/2852139?hl=en

What happens if you boot in safe mode?

oups

de0u oups If the bootloader is locked I am unable to reinstall any clean system ... what if I send an adb update of an official build, might this work ?

Probably not -- that will generally work if the problem is in the system partition and will generally not work if the problem is in the user data partition.

I tried to push an offical build update via ADB but as the signing keys differs from what is currently installed (custom build), it does not accept it

de0u

oups I tried to push an offical build update via ADB but as the signing keys differs from what is currently installed (custom build), it does not accept it

Custom build of what?

My reading of the original post was that a custom build of a launcher was installed on a regular GrapheneOS. Is this a custom build of GrapheneOS?

It would be best to state in more detail how the system became inoperative. Which "Komodo" was built, from which source code (provide a link)? Which version of GrapheneOS is running?

de0u

oups Looks like my only way in is an ADP update using only update signed by the same key I have used to build at first.

If safe mode has failed, and a factory reset has failed, and OEM unlock is off, and the problem is that the system image won't work right, then it may indeed be necessary to provide a working system image.

oups

de0u de0u What happens if you boot in safe mode?

oups When I enter the bootloader, I have rescue mode and recovery mode [...]

But that is not safe mode. Here are directions for safe mode: https://support.google.com/pixelphone/answer/2852139?hl=en

What happens if you boot in safe mode?

Thanks :)
I've booted in safe mode,
But the launcher is still crashing, still not able to go in the system menu

oups

de0u Custom build of what?

My reading of the original post was that a custom build of a launcher was installed on a regular GrapheneOS. Is this a custom build of GrapheneOS?

It would be best to state in more detail how the system became inoperative. Which "Komodo" was built, from which source code (provide a link)? Which version of GrapheneOS is running?

Yes it a custom build of GrapheneOS
I know I have messed up big time
I used https://grapheneos.org/build#building-grapheneos
on Linux Mint 22
https://grapheneos.org/releases#komodo
release Stable 2024121200

de0u

oups Yes it a custom build of GrapheneOS

What customizations were done? I am wondering whether perhaps the regular GrapheneOS launcher was deleted.

oups

https://postimg.cc/MXRphtML
https://postimg.cc/SJhxq8cx

That's when I click on "System" or on "About phone"
Also I can't reinstall any app because it crashes as well when I want to set permission to add the app from source

Dumdum

oups
Can you try clearing the cache of the Settings app?
Long-press the Settings icon > App info > Storage and cache > Clear cache

oups

Dumdum

Dumdum Can you try clearing the cache of the Settings app?
Long-press the Settings icon > App info > Storage and cache > Clear cache

I just gave a try
When I long press settings icon and then press app info, it crashes, and when I insist I get the error msg "settings keeps stopping"

Same thing when I go to menu, apps, see all apps, it crashes

oups

de0u What customizations were done? I am wondering whether perhaps the regular GrapheneOS launcher was deleted.

Yet no modification were done, I've build and sent as is

oups

de0u If safe mode has failed, and a factory reset has failed, and OEM unlock is off, and the problem is that the system image won't work right, then it may indeed be necessary to provide a working system image.

Absolutely,
I have tried re-building twice using the same keys I used to build the system
took the komodo-ota_update-2024122700.zip and sent via ADB update, which seems to be completed
Restart the phone and still the same.
I can't send an ota update from official build unfortunately as the keys differs
that's what I call having fun on sunday :)

de0u

oups Yet no modification were done, I've build and sent as is

Was a particular tagged version built, or whatever was the result of the most-recent commit? The latest commit would be pre-alpha, i.e., at any moment the latest commit might contain bugs which preclude it from being released.

de0u

oups I can't send an ota update from official build unfortunately as the keys differs

In theory it should be possible to re-sign an official build with your keys. But at this point I think it would be prudent to suggest you contact the real-time chat room for development.