Database Users

[Q] How to get the "proprietary blobs" for the "first time" build

It's question me for a long time. All the custom rom's building instruction say that "Your device should already be running the branch of CyanogenMod you wish to build your own version of for the extract-files.sh script to function properly. If you are savvy enough to pull the files yourself off the device by examining the script, you may do that as well without flashing CyanogenMod first."
But where is the "first" proprietary blobs came from? I know for the nexus device we can get the driver from
developers.google.com / android / nexus / drivers
But how about the others? How can we get the kitkat proprietary blobs for "galaxy nexus" and other devices for the first time build?
ps: I am not sure if it is appropriate to post this question here. But I do not know where to ask... sorry if this is in appropriate. And also sorry for my bad English..

https://github.com/DonkeyCoyote

So for my i9100 (Samsung SII (intl)) I had to add
Code:
<project path="vendor/samsung" name="DonkeyCoyote/proprietary_vendor_samsung" remote="github" revision="android-4.4" />
inside the
Code:
<manifest> ... </manifest>
tags in
Code:
.repo/local_manifests/local_manifest.xml

FatMinMin said:
It's question me for a long time. All the custom rom's building instruction say that "Your device should already be running the branch of CyanogenMod you wish to build your own version of for the extract-files.sh script to function properly. If you are savvy enough to pull the files yourself off the device by examining the script, you may do that as well without flashing CyanogenMod first."
But where is the "first" proprietary blobs came from? I know for the nexus device we can get the driver from
developers.google.com / android / nexus / drivers
But how about the others? How can we get the kitkat proprietary blobs for "galaxy nexus" and other devices for the first time build?
ps: I am not sure if it is appropriate to post this question here. But I do not know where to ask... sorry if this is in appropriate. And also sorry for my bad English..
Click to expand...
Click to collapse
In general, the blobs are first obtained by pulling all of the contents of /system from a device running stock.
Sometimes the blob archive winds up being a bit of mix-and-match of stuff from multiple sources...
It's a real mess and unfortunately there is no way to simplify the mess without raising some potential legal issues, as blobs are a bit of a grey area here.

FatMinMin said:
It's question me for a long time. All the custom rom's building instruction say that "Your device should already be running the branch of CyanogenMod you wish to build your own version of for the extract-files.sh script to function properly. If you are savvy enough to pull the files yourself off the device by examining the script, you may do that as well without flashing CyanogenMod first."
But where is the "first" proprietary blobs came from? I know for the nexus device we can get the driver from
developers.google.com / android / nexus / drivers
But how about the others? How can we get the kitkat proprietary blobs for "galaxy nexus" and other devices for the first time build?
ps: I am not sure if it is appropriate to post this question here. But I do not know where to ask... sorry if this is in appropriate. And also sorry for my bad English..
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/drivers#grouper
Here are all the stock blobs, Extract to your build folder then run the scripts in bash
They will then after accepting the license install to the correct vendor location.
( i just learned this last week )

Is there any way how you can get blobs for not so popular devices?
Like Cat S50? The Android is compiled by "Bullitt Group ltd" AFAIK.
Also I know HTC One mini 2 has the same chipset, is it possible to use the one's from that device?

barkley128 said:
Is there any way how you can get blobs for not so popular devices?
Like Cat S50? The Android is compiled by "Bullitt Group ltd" AFAIK.
Also I know HTC One mini 2 has the same chipset, is it possible to use the one's from that device?
Click to expand...
Click to collapse
In general, if you're doing the bringup for a given device, you pull the blobs from a stock firmware for that device, then try to integrate them. Sometimes in the end you wind up grabbing blobs from another device (such as Adreno GPU blobs from a Nexus or a newer device with same chipset), but people always start with the stock firmware and go from there.

Incase anyone is looking for the same
See this thread here. http://forum.xda-developers.com/showthread.php?t=2794413 :good:

[Q] How to compile from source a S3Neo ROM?

Hi all,
I've already read all the useful posts on XDA to build up a ROM, I've built rom for P990 with success some times ago.
Now I'm trying to build a CM12 rom and kernel for our S3 Neo but something goes wrong.
Anyone of our developers could explain me what kinds of commands we need to write to build up with success?
this is my first test on a Samsung and I already hate it, not an help or tutorial on a samsung devs forum (stupid forum, of course).
I've tried to build up only a kernel with Google chains 4.6 with those commands:
Code:
make ARCH=arm CROSS_COMPILE=pathofmycompiler
next:
Code:
make msm8226_defconfig VARIANT_DEFCONFIG=msm8226-sec_s3ve3g_defconfig
It builds a config files:
Next i lauch:
Code:
make -j4
and lots of error... ok, fix it, make a clean and retry... build a zimage, test it and.. doesn't work.
Where I'm wrong? Anyone could post a complete tutorial to build from source for our phone? :crying:

sev3n1985 said:
Hi all,
I've already read all the useful posts on XDA to build up a ROM, I've built rom for P990 with success some times ago.
Now I'm trying to build a CM12 rom and kernel for our S3 Neo but something goes wrong.
Anyone of our developers could explain me what kinds of commands we need to write to build up with success?
this is my first test on a Samsung and I already hate it, not an help or tutorial on a samsung devs forum (stupid forum, of course).
I've tried to build up only a kernel with Google chains 4.6 with those commands:
Code:
make ARCH=arm CROSS_COMPILE=pathofmycompiler
next:
Code:
make msm8226_defconfig VARIANT_DEFCONFIG=msm8226-sec_s3ve3g_defconfig
It builds a config files:
Next i lauch:
Code:
make -j4
and lots of error... ok, fix it, make a clean and retry... build a zimage, test it and.. doesn't work.
Where I'm wrong? Anyone could post a complete tutorial to build from source for our phone? :crying:
Click to expand...
Click to collapse
You have dowloaded cm12 right with all s3 neo specific?
to run buld go :
source build/envsetup.sh
breakfast "device code name chose one from list"
for full build chose : brunch grouper
for kernel only with ramdisk(to make boot.img) : make bootimage
fi you need more contact me

n1kolaa said:
You have dowloaded cm12 right with all s3 neo specific?
to run buld go :
source build/envsetup.sh
breakfast "device code name chose one from list"
for full build chose : brunch grouper
for kernel only with ramdisk(to make boot.img) : make bootimage
fi you need more contact me
Click to expand...
Click to collapse
Tnks man, i would compile only kernel because i haven't ever compiled a CM and i know only something about kernel modding.
So i need to compile all?

sev3n1985 said:
Tnks man, i would compile only kernel because i haven't ever compiled a CM and i know only something about kernel modding.
So i need to compile all?
Click to expand...
Click to collapse
no. if you have cm mainfest i tell you how to compile only kernel and that is easyest whay and best whay

ok, after 7 hours now i have cm12 source code, i've launched breakfast the code name but obviously not found.
So i need to create the local_manifest.xml under .repo/local_manifest.xml :
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="MSM8226-Samsung/android_kernel_samsung_s3ve3g.git" path="/kernel/samsung/s3ve3g" remote="github" revision="cm-12.0"/>
<project name="MSM8226-Samsung/android_device_samsung_s3ve3g.git" path="/device/samsung/s3ve3g" remote="github" revision="cm12.0" />
<project name="MSM8226-Samsung/android_device_samsung_msm8226-common.git" path="/device/samsung/msm8226-common" remote="github" revision="cm12.0"/>
<project name="MSM8226-Samsung/android_vendor_samsung_s3ve3g.git" path="/vendor/samsung/s3ve3g" remote="github" revision="cm-12.0"/>
<project name="MSM8226-Samsung/proprietary_vendor_samsung.git" path="vendor/samsung" remote="github" revision="cm12.0"/>
</manifest>
I've some problems to identify the correct paths, could you see if all are correctly?
Compiled but when make the zimage a stupid error
Export includes file: external/compiler-rt/Android.mk -- /home/antonio/cm12/out/target/product/s3ve3g/obj/STATIC_LIBRARIES/libcompiler_rt-extras_intermediates/export_includes
make: *** Nessuna regola per generare l'obiettivo "/home/antonio/cm12/out/target/product/s3ve3g/obj/STATIC_LIBRARIES/libinit_msm_intermediates/export_includes", necessario per "/home/antonio/cm12/out/target/product/s3ve3g/obj/EXECUTABLES/init_intermediates/import_includes". Arresto.
#### make failed to build some targets (30:53 (mm:ss)) ####
Any solution?

[ROM][XT16xx][7.1.0][CyanMod 14.1 [MotoG4 / G4 Plus] - Where are the BSP files?

Hello again,
Again I post here because I am denied posting in the correct spot. I suppose this silly denial will end, eventually.
I have a question for @Silesh.Nair :
In the dev thread, you tell somebody that he can build CM14.1 from source himself, using that guide:
http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
In a further post, you seem to indicate that the Moto G4 Plus build is obtained direct from the CM source repo.
I found that github repo for CM on the moto G4: https://github.com/CyanogenMod/android_device_motorola_athene
Unfortunately, the latest tag is marked CM 13 ... and there is nowhere to find the BSP files for CM 14.1.
Now, since it seems quite evident to you, but not at all for me, could you please kindly tell us where we can obtain the BSP files (device tree, vendor, kernel) for CM14.1 - Athene?
Thank you for your understanding my confusion.

You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.

Thank you
Silesh.Nair said:
You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.
Click to expand...
Click to collapse
Thank you for this snippet of information. I will look further into it.
In the world of embedded systems, when you have a generic operating system that can be used with many different hardware targets, a Board Support Package ("BSP") is the set of files that are required to build the generic OS on a specific target. For example here the BSP is all the files that are specific for the Moto G4/Plus (e.g. device tree, vendor, kernel), once you have a generic CM 14.1 distribution to start with. "BSP" refers to all the target-specific files that would not be the same on another target (i.e. a different phone).
I think this nomenclature is quite appropriate for the subject at hand.

Help Building Lineage OS

I've tried compiling a lineageos 16 rom from source for the H990ds, but it is stuck at the bootlogo. I was wondering if any of you could help me enable the kernel log/console on the screen (console=tty0) or via the usb ((serial) console=ttyMSM2,115200n8). A few links: http://bootloader.wikidot.com/linux:android:serial
https://forum.xda-developers.com/showthread.php?t=829817
I tried a few things, but this is what I have now:
Code:
CONFIG_CMDLINE_FORCE=y
CONFIG_CMDLINE="console=tty0 console=ttyMSM2,115200n8"
CONFIG_SERIAL_MSM=y
CONFIG_SERIAL_MSM_CONSOLE=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_VT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
and commenting out this line:
Code:
CONFIG_CMDLINE="console=ttyAMA0"
in the arch/arm64/configs/defconfig file, but all with no success.
I was hoping I could get some more information on why it won't boot via the console, but now I'm stuck.
I tried cat /proc/cmdline to see if it anything happened at all there, but it hasn't changed a thing after adding those lines above.
cmdline:
Code:
androidboot.bl_unlock_complete=false androidboot.authorized_kernel=true sched_enable_hmp=1 sched_enable_power_aware=1 app_setting.use_32bit_app_setting=1 kpti=1 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] androidboot.hardware=elsa androidboot.bootdevice=624000.ufshc androidboot.selinux=permissive buildvariant=eng lge.rev=rev_10 model.name=LG-H990 lge.bootreason=recovery cc_mode=0 kswitch lge.bootreasoncode=0x77665502 bootcable.type=400MA lge.battid=SW3800_VC1 androidboot.dlcomplete=0 androidboot.ddr_size=4294967296 androidboot.ddr_info=0x1 lge.crash_handler=on lge.hreset=off boot_cpus=0-3 androidboot.revision=12 androidboot.verifiedbootstate=green androidboot.rpmb_state=1 androidboot.bootdevice=624000.ufshc androidboot.serialno=LGH990be84e8c0 qpnp-power-on.warm_boot=1 gpt lge.signed_image=true androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_sw49407_dsc_qhd_cmd:config1:1:none:cfg:single_dsi
As you can see, it still says "console=ttyHSL0,115200,n8"
I guess I'm doing something wrong here?
I'm an amature and am completely unfamiliar with kernel coding.
Edit: I'm using the "default" msm8996 Lineage 16.0 kernel.
Edit 2: Pstore could be an alternative to what I am trying to achieve here, but yet again, I have no idea how and where to enable that. I found this https://github.com/CyanogenMod/andr...mmit/17a8ee52fac02b9ec4e8c958ed1ec70bcf2156eb but it's also a mystery to me.
BTW. How would you normally debug a build of a rom or kernel if the system does not boot?

Where did you get the source for Lineage 16 on the H990DS? From my knowledge the only LG device that has it is the G3(though I might be wrong). But in any case, you might want to ask @x86cpu since he's probably the most familiar here with building Lineage on this phone.

Ak7J4 said:
Where did you get the source for Lineage 16 on the H990DS? From my knowledge the only LG device that has it is the G3(though I might be wrong). But in any case, you might want to ask @x86cpu since he's probably the most familiar here with building Lineage on this phone.
Click to expand...
Click to collapse
All I did was initialise my dir with branch lineage-16.0 with fallback branch lineage-15.1
This is my local_manifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_lge_h990" path="device/lge/h990" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_device_lge_v20-common" path="device/lge/v20-common" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_device_lge_msm8996-common" path="device/lge/msm8996-common" remote="github" />
<project name="LineageOS/android_device_lge_common" path="device/lge/common" remote="github" />
<project name="LineageOS/android_kernel_lge_msm8996" path="kernel/lge/msm8996" remote="github" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" />
</manifest>
You are right that the h990 and v20-common repo's don't have a 16.0 branch yet. I noticed that aswell, but you never know for sure that it won't work until you try.
I have commented stuff out, and added/moved lines/files to get at least a 'successful' build.
All the changes made to the source are in the attached diff.txt.

Migush said:
All I did was initialise my dir with branch lineage-16.0 with fallback branch lineage-15.1
This is my local_manifest.xml
You are right that the h990 and v20-common repo's don't have a 16.0 branch yet. I noticed that aswell, but you never know for sure that it won't work until you try.
I have commented stuff out, and added/moved lines/files to get at least a 'successful' build.
All the changes made to the source are in the attached diff.txt.
Click to expand...
Click to collapse
All devices have a lineage-16.0 branch. I created them Monday. If it gets sucks at the boot logo, it's something in the kernel in the .dtsi area. Also you cannot upgrade from 15.1 without wiping. There are also changes in 16.0 that you have to pick since they are not merged yet, they stay un-merged until it's validated they work.
You shouldn't have to comment anything out. I do know there are changes for lineage-16.0 needed for the msm8996-common area to even get past the initial make. I had to upgrade my entire build environment due to changes in the pie compiles. Still working on getting a first build.

Surprising
To see someone actually building android pie for the LG V20 is surprising, just wanted to say thanks for all your effort into making this a possibility.

That's the command line from the recovery kernel, not the one you built.
Code:
lge.bootreason=recovery
I've never tried to build lineage or debug an android kernel, but I don't think your kernel is getting loaded. Having console output probably isn't going to help you, unless you can get it from aboot.
If you want to read console output just for fun once your kernel boots, you could try ' CONFIG_CMDLINE="console=tty0 console=ttyAMA0" ' and hope it prints to the screen. Also, the serial console isn't going to help unless you have the phone opened up with probes for UART, a serial cable, etc. I don't know if qualcomm drivers support serial over USB, but that would be the way to go if they do. You could also try using netconsole, though it requires a little bit of extra setup.

x86cpu said:
Still working on getting a first build.
Click to expand...
Click to collapse
This. This makes me very happy :highfive:

Lineage 15.1 Build For Athene: Multiple Errors

Hello developers!
I am a newbie to XDA and also a newbie to ROM development, so if I am doing anything wrong, please do tell me. I own a Motorola Moto G4 Plus and I am very ready to invest as much time as needed in building and creating ROMs for this phone.
I am currently building LineageOS for this phone, and once that is done, I want to try my hand at porting Lineage 16 to this device. I had recently successfully built the cm-14.1 branch for this device (which seems to be the only official build for athene, see the LineageOS Wiki https:// wiki.lineageos.org/ devices/athene/ build#initialize-the-lineageos-source-repository). Now, I downloaded the code for LineageOS 15.1 onto my Linux computer (running Ubuntu 19.04) and have tried to build it.
Steps I took to build -
- Initialised repo with repo init.
- Synced the repository to my Linux computer with
Code:
repo sync -c --no-tags --no-clone-bundle -j24
- Created .repo/local_manifests/roomservice.xml for the device tree, kernel, etc. with the following content:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_motorola_athene" path="device/motorola/athene" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_kernel_motorola_msm8952" path="kernel/motorola/msm8952" remote="github" revision="lineage-15.0" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_external_bson" path="external/bson" remote="github" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
</manifest>
- Ran
Code:
repo sync -c -j24
- Then ran
Code:
export ROOMSERVICE_BRANCHES="lineage-15.0"
to specify a fallback branch
- Ran
Code:
source build/envsetup.sh
- Ran
Code:
breakfast athene
The command ran successfully, no errors until now.
- Then ran
Code:
brunch athene
This is where the problems started popping up. I got errors while building in the following places -
(Treat .(dot) as my source dir)
ERROR 1 - In out/soong/make-vars(don't remember correct file name) - Still get it after
Code:
make clobber[\CODE], I have to always comment line 692 which throws the my-check error to suppress it.
ERROR 2 - Couple of old CyanogenMod dependencies and packages which I managed to get past after messing about with the ./device/motorola/athene/BoardConfig.mk file.
ERROR 3 - Errored out because BOARD_KERNEL_IMAGE_NAME was not defined, finally found an old XDA thread for the 15.1 ROM that told me that I had to set that to zImage in device/motorola/athene/BoardConfig.mk
ERROR 4 - In file ./system/core/init/init.h - Could not find <android-base/chrono_utils.h>, Could not find <selinux/label.h> - Got rid of it by putting in relative file paths and also modifying the ./system/core/init/Android.mk's LOCAL_C_INCLUDES to have relative file paths.
ERROR 5 - In file system/core/adb/daemon/main.cpp, system/core/base/include/android-base/macros.h: Cannot identify arraysize(groups).
ERROR 6 - In file system/core/adb/daemon/main.cpp - Use of undeclared identifier 'AID_UHID'
I can try to fix these errors, but I feel that there must be some branch/fork of the LOS15.1 code that must have all these issues fixed. If anyone has any pointers regarding this or the errors, I would be very grateful.
Thanks in advance,
gamemaker1

I don't believe Lineage 15 or 15.1 ever made it to official status. LOS 14.1 was the last official rom for athene that I know of. You might take a look at this roomservice file and other noteworthy things.
https://forum.xda-developers.com/showpost.php?p=81772343&postcount=348
I've just started building myself and have built LOS 14.1 for a couple unsupported devices (atrix hd and razr hd). Also just started trying to build 16.0 for the old Razr HD but have quite a task ahead of me. Hope the link helps and good luck.

Wheels564 said:
I don't believe Lineage 15 or 15.1 ever made it to official status. LOS 14.1 was the last official rom for athene that I know of. You might take a look at this roomservice file and other noteworthy things.
https://forum.xda-developers.com/showpost.php?p=81772343&postcount=348
I've just started building myself and have built LOS 14.1 for a couple unsupported devices (atrix hd and razr hd). Also just started trying to build 16.0 for the old Razr HD but have quite a task ahead of me. Hope the link helps and good luck.
Click to expand...
Click to collapse
Ok, thanks! I just saw the link, it seems good. Will try it out today and let you know the result.

@Wheels564 Thanks a lot! You really made my day - the extra dependencies in the roomservice.xml got my build done in less than 40 minutes.
From here, I want to get (LOS 15.1 with some extra features of mine, maybe I could cherry pick some features from HavocOS or AEX) an official build out, maybe become an official contributor. If you have any tips about this, please do let me know.
Once again, thanks a ton for your timely help!
Regards,
gamemaker1

gamemaker1 said:
@Wheels564 Thanks a lot! You really made my day - the extra dependencies in the roomservice.xml got my build done in less than 40 minutes.
From here, I want to get (LOS 15.1 with some extra features of mine, maybe I could cherry pick some features from HavocOS or AEX) an official build out, maybe become an official contributor. If you have any tips about this, please do let me know.
Once again, thanks a ton for your timely help!
Regards,
gamemaker1
Click to expand...
Click to collapse
No problem at all. The only thing about LOS 15.1 is that Lineage will never make it official. They've dumped all the rest of the phone on 15.1 because of repo changes I believe. Check here: https://review.lineageos.org/269773
I'm sure they will continue to submit security patches just like 14.1. Looks like the only way to become official is to jump to 16.1. It looks like developers have had issues with athene on LOS 16.1. Glad you were able to build the rom and good luck with future projects.