Recent content by ryanbg

Hi, I'm the guy who did the bootloader unlock. It's kind of a complicated situation, upgrading bootloaders after having an unlocked retail bootloader. The issue is that once you have a dev device (CID + matching RSA signature, the extra 256 bytes), the bootloader write-protects the eMMC where...

Just an FYI, you need to run the sasmung_unlock_n4 application twice. The first time, it will write your eMMC CID to the correct one, and the second time you execute, it will write the CID signature/blob to the bootloader - completing the unlock process. Glad to see you got it working.

Just wanted to pipe in again, I occasionally read this thread. Barring any logical mistakes in the code, the RMA/Citadel functions will most likely require a special key that's derived by Google and device-unique. It will not be possible to "bruteforce" or "crack" this key. The device most...

For now ;)

Yeah, if your device is in developer mode, the bootloader will set eMMC write protection on the bootloader partition. The only way to flash it is through Odin or re-lock the bootloader. It complicates things a bit if you are trying to upgrade.

To unlock the Pixel 3, you need root (which I don't have, nor a Pixel 3, just chiming in to help). To enable OEM unlocking temporarily to unlock the bootloader, you'd need to set the last byte in the FRP partition to 0x01 and then re-hash the partition and store the SHA256 hash at like offset...

I'm taking a look at it. Best not take any OTAs.

PLEASE don't do that. Just leave EFS alone. I'm going to look into a couple things for now, you can set your CID back to 00000001 if you want and flash back to normal.

Could you try unlocking (fastboot flashing lock_critical) and then toggle the OEM unlock option, then lock, then try unlocking again? Sorry for the rat race, just want to see if we can persistently lock/unlock bootloader with CID change.

If you login and activate, does OEM unlocking button change?

Was this after a wipe? Can you try going through initial setup and seeing if it'll let you enable OEM unlocking?

Thanks. After reboot, try checking the CID again to see if it stuck.

This is a different type of CID. This one is just an HTC SKU specifier. Let me dig a little deeper with the writecid command. UPDATE: Try fastboot oem setcid 00000000 (they renamed the command for some reason)

Verizon devices are 00000001 and Google/unlocked devices are 00000000. The writecid command was present in an earlier bootloader... hmm...

Someone wanna try something a little goofy for me? (Need a VZW device) Once you've unlocked a Verizon Pixel 2, run the following command: fastboot oem writecid 00000000 Then lock your bootloader. Then try unlocking the normal way: fastboot flashing unlock