Develop Bugs

[Q] adding semc iyokan or anzu device source tree in manifest.xml

hi all.. recently, i'm trying to compile paranoid from source but i'm stuck at adding device tree in manifest.xml.
so, where can i get the source tree that can be added into manifest.xml?
i get an error after run repo sync command even after adding source tree from github.

General Device and vendor tree

I've copied a device tree from apollo (Mi 10T) with minor changes. I've also built a vendor tree from the latest MIUI 12 Firmware release
Please feel free to contribute as I've never done this stuff before

[RECOVERY][UNOFFICIAL][R11.1_2][hannah-unified] OrangeFox for Moto E5+

the orangefox recovery for moto e5 + is here
Bugs:
- the flashlight can work but also not
- encryption can cause some problems but with decrypted phone it works fine
changes
- bump to fox_9.0
Download:
GKart_builds - Browse /hannah/OrangeFox at SourceForge.net
builds by GKart
sourceforge.net
Device tree:
GitHub - GKart/recovery_device_motorola_hannah
Contribute to GKart/recovery_device_motorola_hannah development by creating an account on GitHub.
github.com
commits are not published yet
greetings and enjoy

New update soon

General [Stock][Kernel][Magisk] WireGuard Kernel Module for Moto E (2020)

This is a patched stock kernel and Magisk module to enable Wireguard's "kernel module backend" feature on stock or GSI firmwares. The patched kernel is required for unofficial modules to be loadable and is an offical kernel with binary patches applied.
The boot image is not already prepatched with Magisk as some users may not want to use it. You can always extract the kernel module from the magisk module zip and insmod it by any means you like.
Kernel Patches:
module_sig_check - always pass - bypass CONFIG_MODULE_SIG and CONFIG_MODULE_SIG_FORCE
check_version - always return true - similar to CONFIG_MODULE_FORCE_LOAD
Spoiler: Resources Used
Build instructions
readme/MMI-QPG30.82-95.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Kernel Sources
Release MMI-QPG30.82-135 · MotorolaMobilityLLC/kernel-msm
ginna push for android 10
github.com
AOSP dtc
refs/heads/android10-release - platform/external/dtc - Git at Google
magiskboot - Unpacking and repacking boot image
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
vmlinux-to-elf - Format the kernel for analysis and recover symbols
GitHub - marin-m/vmlinux-to-elf: A tool to recover a fully analyzable .ELF from a raw kernel, through extracting the kernel symbol table (kallsyms)
A tool to recover a fully analyzable .ELF from a raw kernel, through extracting the kernel symbol table (kallsyms) - GitHub - marin-m/vmlinux-to-elf: A tool to recover a fully analyzable .ELF from ...
github.com
Ghidra - Static analysis and patching
Ghidra
Download:

Running a kernel module built for an older kernel like that seems to be the wrong approach. Whenever I build a kernel with the "kernel: module: Hack to force load prebuilt vendor modules" patch and load it with a recent vendor image, I get boot loops, so the kernels are probably too different to safely force load modules.
Everything works fine with a QPG30.82-135 boot and vendor though, and doesn't need the check_version patch.

TWRP DEVICE TREE | (guam)

device tree for custom recovery compilation.
I believe you have everything you need to build, make good use of it.
GitHub - twrpdtgen/android_device_motorola_guam
Contribute to twrpdtgen/android_device_motorola_guam development by creating an account on GitHub.
github.com