Stuck for 3 days. I lost the OEM option

wizoatk

https://grapheneos.org/install/web#enabling-oem-unlocking

Enable the developer options menu by going to Settings > About phone/tablet and repeatedly pressing the Build number menu entry until developer mode is enabled.

It takes seven presses. It should popup a small window after three presses encouraging you to keep pressing.

Next, go to Settings > System > Developer options and toggle on the OEM unlocking setting. On device model variants (SKUs) which support being sold as locked devices by carriers, enabling OEM unlocking requires internet access so that the stock OS can check if the device was sold as locked by a carrier.

Are you sure there's no Developer Options in the Settings > System menu ?

As long as you can get to the Settings menu, your device is not bricked and there should be no need for you to play with adb or fastboot or recovery, etc. if what you're trying to do is enable OEM unlocking, unless you need to undo something else you did. In which case, the simplest way to get back to some sort of "normal" is a factory reset.

mishtia005

Yes I tried pressing that build numbers million times. There is no Popup message saying keep pressing.

There is no developer option in system. I did factory reset few time through the settings but it’s still the same.

Is there any possibility that somehow the file is been deleted which enable development mode?

de0u

mishtia005 Yes I tried pressing that build numbers million times. There is no Popup message saying keep pressing.

That is consistent with developer mode already being active.

mishtia005 There is no developer option in system.

Settings is being accessed in the owner profile?

mishtia005 When I try to go in to recovery menu from fastboot it just stays on to the loading screen and restart after a minute failing to go in to the recovery menu as well.

Is the device running an in of if version of GrapheneOS? When it boots, does it display a yellow "other OS" screen with the correct verified boot key hash? Or does it display a red "corrupt" screen?

raccoondad

mishtia005 s there any possibility that somehow the file is been deleted which enable development mode?

No, zero possibility on that in any capacity. It would not boot if any files were modified.

Are you doing this exactly:

As the owner (not a secondary) profile: Settings -> About phone -> build number -> spam tap

If that fails, have you tried a factory reset and retrying?

mishtia005

I’m trying to access it with the owner profile. I’m the only user in the phone.

When I restart the phone it say in yellow “ Your device is loading a different operating system”.
There is message saying corrupt. It’s onGrapheneOS.

Maybe you are right the bootloader has some problems now. How do I check?

de0u

mishtia005 There is message saying corrupt.

Do you mean there is no message saying the device is corrupt?

de0u

mishtia005 When I restart the phone it say in yellow “ Your device is loading a different operating system”.

Does the hash value that is displayed match the value listed for the device on the GrapheneOS installation page?

mishtia005

de0u
Yes there is no such message there.

mishtia005

de0u

Oh no. That part is different. It’s not the same hash which is on the website.

Is that means the OS is being tempered?

How do I fix that now?

de0u

mishtia005 What is the hash value that is displayed?

raccoondad

mishtia005 Is that means the OS is being tempered?

Oh dear, I would not use that phone at all TBH...I would get rid of it. That's concerning...

If its not signed by GOS, it could be anything, including something malicious...

mishtia005

de0u

You are great help we are getting somewhere.

The hash is
0db623ece5970ffedd1bd495e4082f68fe2969474fe7f06ef5bfdc24dbdc2512

de0u

mishtia005 The hash is
0db623ece5970ffedd1bd495e4082f68fe2969474fe7f06ef5bfdc24dbdc2512

That is not the hash of a GrapheneOS signing key. However, since the device is displaying the yellow "different operating system" instead of a red "corrupt" screen, the system image was signed by the signing key that is on the device. Thus whatever system is running on that device is not an official GrapheneOS release. Where did it come from, and how was it installed?

mishtia005

de0u

So there is no solution now?

nandohyphen1

mishtia005 It was preinstalled in the phone. I am trying to reinstall it.

Yeah that's the route I'd go then. Then you can verify that the hash is correct and developer options should work. Because looking at the hash, like de0u said, that isn't an official GrapheneOS hash so reflashing is probably a good idea anyway

de0u

mishtia005 So there is no solution now?

It's hard to say.

But if there is a solution it probably depends on knowing where that system image came from.

Said differently: if it's not an official build of GrapheneOS, then it would make sense that it wouldn't behave the way that an official build of GrapheneOS would behave, and how it does behave will depend on which changes were made by whoever made changes.

So... where did the system image come from and how was it installed?

mishtia005

de0u

I am not sure where it came from.

I bought the phone from facebook market place thinking its a good phone. Now i am stuck and cannot download anything on it. I thought maybe i revert it back to original google OS but i can't. Only lead i had was the name of GrapheneOS showing on the startup and now it's not this OS either.

I stand where i started.

nandohyphen1

mishtia005 I am not sure where it came from.

So you mean GrapheneOS was pre installed, or you installed it?

nandohyphen1

mishtia005 I thought maybe i revert it back to original google OS but i can't.

Why can't you? Just follow the directions on the website
https://grapheneos.org/install/web#replacing-grapheneos-with-the-stock-os

https://flash.android.com/back-to-public

If you are concerned and the hash doesn't match, just back up your phone, flash stock, and then re flash GrapheneOS from the website using the web installer
https://grapheneos.org/install/web#web-install

de0u

mishtia005 It wouldn't be that difficult for somebody to build a custom version of GrapheneOS that won't enter Recovery and won't enable developer mode. I can't speculate about why somebody might have done that, but if they sold the phone to you that way then it was sold in a defective state. Perhaps you can return it?

I don't know this for sure, but I think there is some reason to believe that Google repair centers have a way to forcibly re-flash a device in this state. You might try asking a repair shop what they think.

mishtia005

nandohyphen1

It was preinstalled in the phone. I am trying to reinstall it.

de0u

mishtia005 If you boot into fastboot, does it say that the bootloader is locked or unlocked? Does it say "(unlockable)"?

de0u

nandohyphen1 Reflashing is probably a good idea anyway.

If the bootloader is locked and OEM unlocking is off, then reflashing isn't going to be feasible.