Hi all!
I'm trying for days to compile some of the Lollipop roms for the T800 and T700 available on Github.
Tried a lot of tutorials, downloaded the CM12 source on ubuntu, but I can't, for the life of me, integrate the files from github into the cyanogen downloaded source and do a "breakfast chagallwifi".
Could anyone give me some pointers?
Thanks!
Update, got it to start compiling, found another clue on local_manifests that is working! Let's see if it compiles...
Hello Guys,
I've been building find7 for one year (for crdroid tteam mainly) and since yesterday i'm facing a strange issue building:
error message:
----- Making boot image ------
error: could not load device tree image '/home/jejecule/crdroid2/out/target/product/find7/dt.img'
make: *** [/home/jejecule/crdroid2/out/target/product/find7/boot.img] Error 1
I downloaded pure cm12.1 source, made the same test and exactly the same error
Reverted last sepolicy cm-vendor commits, same issue, changed kernel, same issue...
Anyone facing the same with cm based rom with this device?
Thanks guys
cm is changing a lot of things right now. they seperated the oneplus one from msm8974-common,
and the find7 has a new kernel too..
suraj.das said:
cm is changing a lot of things right now. they seperated the oneplus one from msm8974-common,
and the find7 has a new kernel too..
Click to expand...
Click to collapse
Hey my friend, did not notice that Find7 had his own kernel...maybe it's why...
How are you? and you tipsy builds?
See U soon.
Cheers
Jerome
Oppo find7 can running cm ROM based use caf kernel and caf ROM?
Sorry for my English.
So I have been trying to get a functional build of this devices kernel for a while now and I have to say it sucks.
My first problem was finding the actual kernel source which isn't on the aosp site but rather in the chromium source. When I finally found the kernel source for it, I was greeted with an absurd amount of branches. I mean aosp has like 6 branches for a device after 4 or so years and this device has countless branches referencing its multitude of names (pixel c, ryu, smaug, and dragon). Anyways I decided to pick the chromeos-3.18 branch (https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.18) not sure if this is right. Then I spent forever looking for a fitting defconfig which there was none, only to find you have to run a script with the right flavor and device to create the defconfig. I finally got that done and got a dragon_defconfig that let me build a kernel binary.
Here is where I am stuck. So before I went to substitute this binary in the boot image I just wanted to try making a boot image with the stock provided kernel.
I was able to build using "make bootimage" and got a boot image that sent me into a bootloop. And this is with the 6.0.1r16 branch with no modifications. I looked into the dragon-kernel and noticed the provided kernel file is a file called Image.fit which is the first time seeing such a file format. The kernel binary I created was just an "Image" and a compressed version "Image.gz" but neither is anything like the Image.fit file that is provided.
Either way I am really stuck and the lack of documentation pertaining to the pixel kernel source is frustrating. Can anyone help me out?
I don't know what's the issue with my setup or kernel tree (Alberto97's git) that I'm getting these errors all the time when I try to compile any rom
1) rmnetctl library conflict. There's always this error in all roms and states that "shared libraries is already defined" in rmnetctl folder in device tree hence stopping the build at the begenning. I got past the issue by deleting the rmnetctl folder in device tree but is it the right way to do it?
2) Sepolicy error. Even after I delete above folder, the build stopped after it reaches about 34%, I don't know what it's called but I'm getting this error every time I try to compile any rom. This time while building aosp extended https://hastebin.com/yomepicili.sql
I'm a noob so pardon any lack of knowledge. I am trying to learn to compile here. Also, I'm using oreo-mr1 branch device tree and kernel and oreo-mr1-addison branch for vendor.
Following this thread, I recently built e/OS 0.22q for Motorola One xt1941-4 (deen). Please refer to https://e.foundation/e-os/ to learn more about e/OS.
After several weeks of usage this ROM seems to be very useful. Find the zip file with the images of the Andoid 10 version here. Unzip and flash using adb and fastboot. Please use at your own risk!
I used the following repos in my local manifest:
https://github.com/electimon/device_motorola_deen, branch Lineage-17.1
https://github.com/electimon/vendor_motorola_deen, branch Lineage-17.1
https://github.com/100Daisy/android_kernel_motorola_deen, branch android-10-release-qpks30.54-22-13
In addition, I included
https://github.com/LineageOS/android_system_qcom, branch Lineage-17.1
which is obviously needed by some stuff from vendor. Vendor files are from 2019, so if someone could provide a more recent repo, I would be glad to know (last stock rom provided by Motorola is from October 2021)
All credits go to the creators of the LineageOS 17.1 port (link to thread at the top of this post)! Very good job guys!
Works just fine, thanks.
LSV12 said:
Works just fine, thanks.
Click to expand...
Click to collapse
Thanks!
Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian
01nick07 said:
Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian
Click to expand...
Click to collapse
I'm sorry, but I have no time and I am not good at making tutorials at all. Please refer to the thread referenced at the beginning of the initial post. There you should find all necessary information. If this is not enough, do some more searching and reading on XDA. If you still feel uncomfortable, stay with the stock rom.
Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'
xdadevc said:
Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'
Click to expand...
Click to collapse
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...
HerrElling said:
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...
Click to expand...
Click to collapse
I read your article and managed to follow it and compile my own e/os. I'm also not an android developer. I did some kernel work in the early days, around Android 2.0 but my path diverged and now I'm completely lost.
Let's keep in touch. If you restart your efforts, I'll be happy to contribute. Meanwhile I'll try my best to get some info from the e/os forums and (pray) the lineageos residual devs.