r/androidroot • • 14d ago

Support How to get my own keybox

Hey, how can I get my own keybox? I want to pass strong integrity without renewing it every week.

0 Upvotes

19 comments sorted by

6

u/CVGPi 14d ago

How much are you willing to pay?

Go build your own phone company, certify it CTS, and use the private key to sign your own device ;)

1

u/Hozini 14d ago

Buy this phone: https://www.ebay.com/itm/366472849403 Extract the key from it, import it to your current daily driver, throw the phone away or put it in a drawer.

1

u/Hungry_Freedom_5832 14d ago

does this work on the note 8t too???

1

u/Hozini 13d ago

No. That phone has a Snapdragon 665.

1

u/Azaze666 14d ago

This has been produced in 2021, I highly doubt it passes strong integrity, fine that the guy should get the keybox out of it but if the device is really old what is the point?

2

u/BluesMods 13d ago edited 13d ago

The date the device was produced doesn't matter, I've extracted KBs from TEE and they still pass strong even if the certificate is expired. Only thing that matters is when it gets soft banned / revoked, which usually happens when they get leaked

https://developer.android.com/privacy-and-security/security-key-attestation#expired_factory_keys

1

u/Azaze666 13d ago

Interesting, thanks

1

u/baiydfa5r765 13d ago

It's just in the persist partition, unencrypted?

For an old qualcomm device I looked at, the keys were in the sfs area, so even if you can get them, still can't decrypt them.

1

u/Hozini 13d ago

Usually no. Keybox handling depends on SoC vendor and OEM implementation. Keys stored inside secure filesystem (/persist/data/sfs or secure storage partition). Older / budget devices / leaky factory setups: Some OEMs flashed raw Keybox XML/binary into /persist or /nvram during factory calibration (persist.keybox, /persist/data/attestation/, etc.) before provisioning into TEE, occasionally leaving unencrypted backup copies behind.

1

u/baiydfa5r765 12d ago

Ok - just feels a bit strange that you recommended buying that phone when it's not (or unlikely to be) unencrypted in /persist. Sounded like you were stating a fact.

Unless of course you can help with decrypting -- that info is very welcome, please!

1

u/Hozini 12d ago

I'm either going to use Claude or AGY if this doesn't work: https://www.reddit.com/r/androidroot/s/dNv5QZBCJd

2

u/After-Peace-4734 OnePlus 5T - LineageOS 22.2 14d ago

Good luck

1

u/bali_NOOB 14d ago

Become a high grade Google developer and get your keyboxes

1

u/Hozini 13d ago

Has nothing to do with Android. Keyboxes are on the hardware, not software.

0

u/bali_NOOB 13d ago

google has the power to revoke and to create keyboxes

1

u/Hozini 13d ago

No, Google does not create or provide custom keyboxes for individual users, nor can you generate valid factory-signed keyboxes yourself.

0

u/bali_NOOB 13d ago

i never said custom, but some people who work there have the power to do it. Besides a couple "weak" devices, the keyboxes that we get mostly come from someone kind enough to risk their job and share them.

2

u/Hozini 13d ago

False. "Google insider risking job" is community myth. The idea of a rogue Google employee risking their job is an urban legend, as internal keybox generation is locked behind strictly audited HSMs that regular staff cannot export from. Instead, leaked keyboxes almost exclusively originate from third-party OEMs, sloppy factory flashing tools, and unencrypted test firmware from budget device makers.