Did I just make a brick?

mar2112

Loaded GOS on my old 4A(5g) so I could have a device to experiment with. Apparently the PIN that I used is not what I remember setting and now I can't log in to the phone. I figured "No problem" I can just wipe and start over cause there's nothing on the phone. I can't boot into recovery or rescue mode. With both I get the "No command" error.

Since I diligently followed the instructions the bootloader is locked and OEM unlocking is disabled.

Is there any way to recover from this?

nandohyphen1

mar2112 Loaded GOS on my old 4A(5g)

How did you even do this? The Pixel 4a isn't supported - it hasn't been for quite a long time. At a minimum, you need a Pixel 6. How did you flash this? There is no release for the 4a currently. These are the supported devices
https://grapheneos.org/faq#supported-devices

Watermelon

mar2112 Your device is insecure and end-of-life.

mar2112 "No command" error

This isn't an error, it's the normal behavior of the recovery mode. When you see this screen, hold the power button, press volume up key, and release both buttons.

nandohyphen1

mar2112 Apparently the PIN that I used is not what I remember setting and now I can't log in to the phone. I figured "No problem" I can just wipe and start over cause there's nothing on the phone. I can't boot into recovery or rescue mode. With both I get the "No command" error.

Since I diligently followed the instructions the bootloader is locked and OEM unlocking is disabled.

Is there any way to recover from this?

I assume that because you installed GrapheneOS on a 4a (which I don't know how that was even possible), it ran into a problem. Exactly how did you install GrapheneOS on your 4a? The web installer? I don't believe it would let you install GrapheneOS on a phone that old... Unless you mean you flashed GrapheneOS onto the 4a a while back, when it was still supported.

mar2112

nandohyphen1 I installed with CLI command and used this release: https://grapheneos.org/releases#bramble

I realized it's EOL and less secure which is why I only intend to use it for experimentation purposes such as testing an app before I install it on my daily driver which is a 9a.

mar2112

Watermelon Thanks. I've never used a recovery that behaved that way.

fernlike

nandohyphen1 Pixel 4 to 5a are all still getting legacy support, so yes you can still install Graphene on them using the Web installer or CLI: https://grapheneos.org/releases#table-of-contents

They're just not advertised as supported devices (since they're not secure) and will eventually stop getting updates.

nandohyphen1

fernlike Pixel 4 to 5a are all still getting legacy support, so yes you can still install Graphene on them using the Web installer or CLI

Oh OK. I really didn't think devices that old could still be flashed with GrapheneOS.

userofgos

fernlike Pixel 4 to 5a are all still getting legacy support

fernlike and will eventually stop getting updates

If I remember correctly, 2025012701 (4, 4XL, 4a) and 2025021000 (5, 5a) were the last legacy extended updates.

mar2112

Here's some more info as to what happened. I wiped the phone and went through the setup procedure again. I set the PIN to the same 7 digit number I used the first time. I rebooted, entered the correct PIN and received an error message. I truncated the PIN to the first 6 digits with no joy. I wiped the phone again, set a 4 digit PIN, rebooted and was able to unlock the phone.

For some reason this legacy version of GOS does not like 7 digit PINs.