Generate Your Own Private Keys. The provided keys are for temporary use only. They are publicly accessible, and using them for release is not secure. Create your private keys as soon as possible to maintain control over your builds.

Frequently Asked Questions (FAQs)

What is this?

This is Android Public Keys (basically Private Keys) that i made for Developers, Maintainers or just Custom ROMs Builders specifically for Redmi 7 and Y3 who can't make their own Private Keys, and those who still can't sign Android manually.

This is Temporary Keys for Sign Android (AOSP) until the Developers can create their own Private Keys.

This is for all types of Custom ROMs (ex: LineageOS, PixelOS, Evolution X, etc).

And also for Custom ROMs from Android 10 and newer Android version.

How to use this?

• Source configuration:

  cd your rom folder

  git clone https://github.com/onclite/android_vendor_lineage-priv_keys -b master vendor/lineage-priv/keys

• If you're using local manifests:

  <!-- Keys sources -->
  <remote  name="onclite"
           fetch="https://github.com/onclite/"
           clone-depth="1" />
  
  <!-- Certs -->
  <project path="vendor/lineage-priv/keys" name="android_vendor_lineage-priv_keys" remote="onclite" revision="master" />

• Device tree configuration:

  include vendor/lineage-priv/keys/keys.mk

  Example here.

Details of Keys registration?

C=US
ST=California
L=Mountain View
O=Xiaomi Redmi 7 and Y3
OU=Xiaomi Redmi 7 and Y3
CN=Xiaomi Redmi 7 and Y3
emailAddress=android-dev@usa.com

Is email for registration valid or just random?

Yes, i'm using a valid email. You can even send messages to this email. This is my work email specifically for Android development.

android-dev@usa.com

Is it safe to use this Keys?

Yes, This is safe and your Custom ROMs will be signed with dev-keys (same as release keys),

dev-keys/release-keys name is depend on your Custom ROMs source configuration. But it's basically same.

This will full sign your ROM include APEX.

And also there will be no information sent to the registered email.

Is this Keys same with my Private Keys?

Of course not. I'm use Production Release Keys for my Custom ROMs that already released. Leaking my Keys to public is impossible, forbidden to do. And risky.

Why I make this?

Because partial Developers don't know how to create Private Keys. And also many people ask me how to Sign Android in private message.

So why not create Public Keys for Redmi 7 and Y3 development to make this device keep alive!

How do I create my own Private Keys?

Follow AOSP documentation, here and here. Or, you can follow LineageOS documentation.

Be careful when you create your own Keys. If your Keys are corrupted, then the ROM will not boot, and will only enter fastboot mode.

Migration to your private keys!

The keys included in this repository are temporary keys provided to facilitate development and testing for Redmi 7 and Y3.

---

• These keys are public, meaning anyone can access and misuse them, potentially leading to:
  • The creation of fake or malicious builds.
  • A breach in the security and integrity of your system.
• Using your own private keys ensures that only you have full control over the builds signed with them.

Next Steps:

1. Generate your own private keys as soon as possible by following the guide.
2. Store your keys securely and avoid sharing them with anyone without proper authorization.

Important Reminder:
These keys are provided only as a temporary solution to expedite development. I'm not responsible for any misuse of these keys by third parties. Please take the necessary steps to protect your builds.

Registration of Certificates