I have built Lineage os from the source without any error and when I flash it my phone boots only in fastboot mode or recovery. source are from LineageOS repo on github and TheMuppets repo particularly 1 result for repositories proprietary_vendor_qcom_binaries and proprietary_vendor_xiaomi. I tried using extract.sh but it gave error ./../../../device/qcom/common/extractors/extract-files.sh: No such file or directory. When I try to boot recovery.img or boot.img it gives error that dtb not found. Any help or lead would be appreciated.
Related
This is TWRP, or team win recovery project. For more about teamwin, see them here
This is compiled with omni rom as a base. For Omni, go here
The device tree used to compile is found here
Kernel: here
NOTE: To build
Code:
repo sync
. build/envsetup.sh
lunch omni_m8_whl-eng
make clobber
make -j8 recoveryimage
To install:
Code:
adb reboot bootloader
fastboot flash recovery TWRP*.img
fastboot reboot
DOWNLOAD​NATF Edit: Verified MD5 - 577684863556047FDAF555F1E3A6221D
Credits:
Thanks to @jmz @Dees_Troy @Flemmard @bigbiff
What doesnt work:
ExFat write (read works)... This will require some driver debugging, and I will look more deeply into the issue
Sent from my 831C using Tapatalk
Please post all comments questions and help requests here.
Thank you for your support
Sent from my 831C using Tapatalk
Hi,
I have successfully build Lineageos .
Vendor tree kernel from exynos7850 source github
.
Problem is someone already pushed vendor and he build lineage. But some features are not working.
While I didn't sync repo last 1day. I have made changes in my local directory and got that build with minimum bug . Now I want to push the vendor. I an noob so please elaborate this git things
Hello,
I am currently trying to build a custom build of LineageOS 15.1
ATM I have followed the official LineageOS guide to compile and have added vendor repo from Steel01 Gitlab (CM-Shield)
Afterthat, I have applied the patch for exposing the arm libm intrinisics with repopick.
Compiling is success, the tablet can boot but Youtube 1080p/60fps videos are still laggy (a lot of dropped frames).
Do you know what other things can be done?
Edit: I am also trying to build 16.0 releases. Build successfully completed but cannot boot.
How this can be troubleshooted?
I had look at the kernel and recovery logs. Kernel log show strange errors but cannot say if these are the cause of the 'non-booting'
Hello, I building twrp minimal manifest for teak board. In attached file what is this error?
Ouput Error:
ninja: error: '/root/_twrp/out/target/product/teak/system/bin/linker', needed by '/root/_twrp/out/target/product/teak/obj/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin', missing and no known rule to make it
Re-post your issue here:
[HOW-TO] Building TWRP from source with goodies
I decided to put together a guide on how to build TWRP from source, having successfully built it myself and restored a few of the goodies that disappeared in the 3.3.1-0 release (e.g. install kernel). Also, marlin (Pixel XL) has had a few...
forum.xda-developers.com
First of all, I want to thank the official Motorola contributor SyberHexen for the precious advice he gave me thorugh the process. All the credits go to him for the hard work he's been doing for our community through the years.
DISCLAIMER:
I take no responsibility whatever for any kind of damage that might occur by following the steps below. Building an unofficial ROM using "what worked for another person" and costantly updated sources includes a high risk of making your phone unstable, bricked or causing loss of data. Remember to back up your data before flashing the rom. The guide may contain errors or not be fully compatible with future PRs on the original source, so DO IT AT YOUR OWN RISK.
WHAT YOU NEED:
- SyberHexen's unofficial build and Moto Ocean partitioning file
- A Unix\Linux system (haven't tested it on WSL, sorry)
- 300/350GB of available disk space
- at least 16 GB of RAM
In case your machine doesn't fit the requirements, you might consider a dedicated cloud Linux device (I used an AWS EC2)
STEPS:
- Follow the official Lineage OS build guide for Motorola Channel up to the Turn on caching to speed up build section.
- For the Initialize the LineageOS source repository section, use the following Repo command:
repo init -u https://github.com/LineageOS/android.git -b lineage-19.1 (and NOT 18.1, as indicated)
- Follow the indications as in the Prepare the device-specific code section
- enter the device path and remove the channel folder, as some blocking changes have not been pulled into the main repo (this might become unnecessary as soon as Andrew Hexen's changes are merged into the LineageOS repo):
cd ~/android/lineage/device/motorola/ && rm -rf channel
- get the device specific content from the updated Hexen repo, rename the folder and check the branch is lineage-19.1:
git clone https://github.com/SyberHexen/android_device_motorola_channel.git
mv android_device_motorola_channel channel
cd channel
git checkout lineage-19.1
- install Python3 and python3-protobruf if not already on the system (the package named python-protobruf indicated on the following step is not available on most recent systems anymore)
- extract the proprietary files from SyberHexen's April ROM following this guide (Payload section)
- go back to the official Lineage OS build guide and follow the steps from the Start the build section on. Consider that building from source might require a few hours.
- boot your phone on Fastboot, and flash SyberHexen's ocean_gpt.bin file (fastboot flash boot ocean_gpt.bin)
- boot into Recovery Mode and sideload the Lineage OS rom you just compliled. If you use the gapps, reboot into Recovery Mode and sideload the respective package (MindTheGapps-12.1.0-arm64-20220416_174313 worked great for me)
Congratulations, your freshly built unofficial ROM should be up and running!