Minimal manifest for building TWRP for devices shipped with Android 5.1 through Android 9.0
Find a file
Maanush Putcha dc778ac098 Switch to old repos for system_core and frameworks_base
* All pre android-14 branches of system_core and frameworks_base are
  moved to system_core_old and frameworks_base_old repos respectively
2024-09-25 18:30:59 +05:30
.gitignore Add minimal twrp for 9.0 2020-06-22 17:31:52 +02:00
default.xml manifest: android-9.0.0_r47 2019-08-05 23:12:19 +02:00
GLOBAL-PREUPLOAD.cfg manifest: disable global commit_msg_test_field repohook check 2018-12-17 00:09:44 +01:00
omni-aosp.xml Switch to old repos for system_core and frameworks_base 2024-09-25 18:30:59 +05:30
omni-caf.xml android: add qcom oss interfaces repo 2019-03-06 13:03:30 +01:00
omni-default.xml Add minimal twrp for 9.0 2020-06-22 17:31:52 +02:00
README.md Update to include python2 warning to the README.md 2022-07-27 14:56:30 -04:00
remove-minimal.xml Readd platform/system/libufdt to ensure dtbo building 2020-06-22 17:31:53 +02:00
remove.xml nos: add in host repos 2020-06-22 17:31:53 +02:00
twrp-extras.xml Add python3 repo 2022-07-03 13:05:06 -04:00

Submitting Patches


Our project is open source, and patches are always welcome! You can send patches by using:

Pull request, right here on git.

Contact us at https://rebrand.ly/teamwin-recovery-zulip-community

Maintaining Authorship


Maintaining authorship is a very important aspect of working with Open Source code. If you wish to submit a patch/fix from anywhere else (another ROM, project, etc.), it is imperative that you maintain the ownership of the person whose work you are seeking to include. Doing so will ensure that credit is given where it is deserved, and the principles of open source are upheld. Your contribution to the project will still be recognized as you will forever be listed as the committer.

If you manually cherry pick a patch/fix then you will need to add the original author prior to pushing to our gerrit. This is a very easy task to perform, and is usually done after you commit a patch/fix locally. This is accomplished after you type in git commit -a , type in the commit message and save. You would then do the following:

git commit --amend --author "Author <email@address.com>"

So it should look like this once you get all of the author's information:

git commit --amend --author "Spencer McGillicuddy <spencer.the.bestest@gmail.com>"

Alternatively, adding as part of the original git commit message is preferred and done like the following:

git commit --author="Author <email@address.com>" -m "[commit message]"

This saves time, and when part of your normal routine, prevents the infamous "ermahgerd I forgot to add authorship - let me fix it because I was found out!" message.

Getting Started


To get started with OMNI sources to build TWRP, you'll need to get familiar with Git and Repo.

To initialize your local repository using the OMNIROM trees to build TWRP, use a command like this:

repo init -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-9.0

To initialize a shallow clone, which will save even more space, use a command like this:

repo init --depth=1 -u https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-9.0

Then to sync up:

repo sync

Python Requirement Note


Before building, make sure you have your system's python implementation set to python2. This project was created before python2 was deprecated and will not build with python3.

Build


Then to build for a device with recovery partition:

 cd <source-dir>; export ALLOW_MISSING_DEPENDENCIES=true; . build/envsetup.sh; lunch omni_<device>-eng; mka recoveryimage

Then to build for a device without recovery partition:

 cd <source-dir>; export ALLOW_MISSING_DEPENDENCIES=true; . build/envsetup.sh; lunch omni_<device>-eng; mka bootimage