Robert skinzor

Preface

Before anything or any comments or ideas, this is a way I wanted to try to inform and update what a device tree is and what it has, and finally how Custom Recovery is created. So this is not a complete guide and it won't be! I never intended to do that.

The original idea

Please take a look and may you take a few minutes to read the original guide. I had written myself that I intended to update the information. I hope that after reading the original guide you can go back and have a few minutes of reading and mainly practice to gain experience.

This guide comes to complement or update some important information. All thanks to @rokibhasansagar about first guide Make A TWRP Tree For Your Device & Build

Certainly, given the breadth of the subject, it should have many more parts. But understand about "Minimal" thinking and that I didn't intend to extend it any further than necessary. So the guide has:

Generating dev-keys to sign android builds

All you need is an Android buildsystem (LineageOS is recommended)
NOTE: For Lineage 21 and newer, different steps are required.

PART 1: GENERATING KEYS

Export your infos (replace examples with your infos)

subject='/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/[email protected]'

C: Country shortform

Generate framework compatibility matrix from fqnames

Download these 2 files
Compile AOSP without fcm from stock and wait for check_vintf to error out
Delete Python prefix from all lines (e.g. checkvintf E 06-24 00:30:22 49120 49120 check_vintf.cpp:554])
Paste the result in fqnames.txt
Launch the script

A small Device Tree Bringup Guide

Introduction

So, you guys might be wondering, how do these "Developers" get your favourite Custom roms, such as LineageOS, Paranoid Android etc., to their own devices. Well I'm here to Guide you on how to do it, specifically on how to bringup or make your own device tree from scratch or adapting.

Gist of this Guide: This is for people with genuine interest in Android OS porting/development. After going through this guide, you should be able to do a total device tree bringup on your own.

Prerequisite: Certain requirements are to be met before you start with this amazing journey.

How To Work With Multiple Github Accounts on a single Machine

Let suppose I have two github accounts, https://github.com/rahul-office and https://github.com/rahul-personal. Now i want to setup my mac to easily talk to both the github accounts.

NOTE: This logic can be extended to more than two accounts also. :)

The setup can be done in 5 easy steps:

Steps:

Step 1 : Create SSH keys for all accounts
Step 2 : Add SSH keys to SSH Agent

LineageOS build guide for n00bs like me

Soo you want to build LineageOS (los) for your xiaomi davinci?

This guide will show you how! In this guide i'll lead you through the process of compiling los 17.1 for xiaomis MI 9T, optionally with spoofing support for microG.

I am not responsible for any damage you do to your phone and this guide does

Gitlab won't allow reuse of a public ssh key for multiple accounts. To get around this you need to create a second ssh key for the second account.

Create or modify your ~/.ssh/config file:

# normal                                                                                                                                                                  
Host gitlab.com-work_username
     HostName gitlab.com
     PreferredAuthentications publickey
 IdentityFile ~/.ssh/id_rsa

How To Make A Working TWRP Device Tree For Your MediaTek Device & Start Building Them, Online

This Guide is tested on 64-bit mt6735/53 chipset device. It will also work on any 64-bit and 32-bit devices.

You will need something from your Stock ROM first. Get them all and Try to modify it using the procedure.

Note: This guide will be helpful for you if you have older mediatek devices (android-5.1 or android-6.0), but up-to-date devices can also work.

Update: This guide had a few typos and derps (Oops..), but I've tried to make it free of those now (Dated November 18, 2020)

Bonus: You can also use this tool by @SebaUbuntu, @yshalsager and @mauronofrio to auto generate the twrp tree. The tool is best if your device runs on android-9.0. The tools is still not 100% compatible to all devices, but I'll still recommend it and give it 8.5/10 in the scale of varsatility.

	# last three commits
	git format-patch -3 --stdout > multi_commit.patch
	# all commits that are in your branch and not in master into a single patch file multi_commit.patch
	git format-patch --signoff master --stdout > multi_commit.patch
	# create patches in the folder ~/output/directory/ for all commits that are in your branch and not in master
	git format-patch -o ~/output/directory/ --signoff master

	VENDOR_SEPOL_PATH="${1}"
	OUT_DIR="${2}"

	rm -rf contexts contexts-sorted vendor-contexts ${OUT_DIR}
	mkdir -p ${OUT_DIR}/vendor

	context_files="file_contexts hwservice_contexts property_contexts seapp_contexts"
	for context_file in $context_files; do
	while read context_line; do
	if ! grep -Frq "`echo "${context_line}" \| cut -f1`" ../../../device/qcom/sepolicy/ ../../../system/sepolicy/ --exclude-dir=prebuilts --exclude-dir=compat; then