I am trying build my own rom from source code, but when i reached to command "lunch", i got an error,
..............................................................................................................................................................
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:43 dumpvars failed with: exit status 1
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:45 dumpvars failed with: exit status 1
** Don't have a product spec for: 'Huawei'
** Do you have the right repo manifest?
...........................................................................................
I tried "lunch Huawei Honor 5x", "lunch device_huawei_kiwi". "lunch kiwi", still got a same error.
Can anyone tell me what is the right name of Huawei Honor 5x for ASOiP. Thanks in advance.
david3709 said:
I am trying build my own rom from source code, but when i reached to command "lunch", i got an error,
..............................................................................................................................................................
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:43 dumpvars failed with: exit status 1
build/make/core/product_config.mk:243: error: Can not locate config makefile for product "Huawei".
17:09:45 dumpvars failed with: exit status 1
** Don't have a product spec for: 'Huawei'
** Do you have the right repo manifest?
...........................................................................................
I tried "lunch Huawei Honor 5x", "lunch device_huawei_kiwi". "lunch kiwi", still got a same error.
Can anyone tell me what is the right name of Huawei Honor 5x for ASOiP. Thanks in advance.
Click to expand...
Click to collapse
What software tools are you using to build your ROM?
Thanks for your response.
I did not use any software, i follow the instruction of AlaskaLinuxUser, he has lot of videos for compling custom rom.
I am working in Ubuntu 22.04, and openjdk18, the latest git and repo. And i also use lineage os instruction(https://wiki.lineageos.org/devices/kiwi/build) for reference.
The manifest is from "https://github.com/AOSiP/platform_manifest/tree/pie"
Before command "lunch", everything is ok, and "repo sync -j 4 -c" is fine, no error.
This error looks like the name of device is wrong.
For Lineageos 17.1, i am using "kiwi", it works and already flashed my compiling rom on my phone, and everything is working fine, just sometimes has response lag problem. That is the reason i want to try another rom, i can not accept response lag, want to good performance.
There is office AOSiP rom for my phone, i just want to try to build my own rom for practice and later do some changes.
I am using terminal to build my own rom, and stuck on "lunch", can not find the right device name for honor 5x. need help.
david3709 said:
I am using terminal to build my own rom, and stuck on "lunch", can not find the right device name for honor 5x. need help.
Click to expand...
Click to collapse
david3709 said:
Thanks for your response.
I did not use any software, i follow the instruction of AlaskaLinuxUser, he has lot of videos for compling custom rom.
I am working in Ubuntu 22.04, and openjdk18, the latest git and repo. And i also use lineage os instruction(https://wiki.lineageos.org/devices/kiwi/build) for reference.
The manifest is from "https://github.com/AOSiP/platform_manifest/tree/pie"
Before command "lunch", everything is ok, and "repo sync -j 4 -c" is fine, no error.
This error looks like the name of device is wrong.
For Lineageos 17.1, i am using "kiwi", it works and already flashed my compiling rom on my phone, and everything is working fine, just sometimes has response lag problem. That is the reason i want to try another rom, i can not accept response lag, want to good performance.
There is office AOSiP rom for my phone, i just want to try to build my own rom for practice and later do some changes.
Click to expand...
Click to collapse
Using newer ROMs on older devices is going to cause lag, that is normal. The problem is not the ROM, the problem is your hardware wasn't designed to use newer, more demanding software.
yes, you are right, that is why i want to try android PIE, the reason for building AOSiP Pie is i want to do more practice, after more try, i can really build my own custom rom, right now what i only can do now is to rebuild some custom rom.
Related
As far as I know there is no official support on the LineageOS github for the zerolte model and that's when I decided that I'd like to change that.
I created my own device tree, but there are still some important directories and files missing to get passed the brunch command for zerolte.
If any kind soul would be able to help me make the changes specific for this model I'd be so happy.
Here's the tree: https://github.com/Umeaboy/android_device_samsung_zerolte
OK, here's the first error when running brunch zerolte:
Checking build tools versions...
build/core/binary.mk:1253: external/deqp/Android.mk: libdeqp: Unused source files: \
build/core/binary.mk:1253: external/deqp/Android.mk: libdeqp: Unused source files: \
build/core/binary.mk:1253: external/pdfium/third_party/pdfiumbigint.mk: libpdfiumbigint: Unused source files: bigint/BigInteger.cc bigint/BigIntegerUtils.cc bigint/BigUnsigned.cc bigint/BigUnsignedInABase.cc
build/core/binary.mk:1253: external/pdfium/third_party/pdfiumbigint.mk: libpdfiumbigint: Unused source files: bigint/BigInteger.cc bigint/BigIntegerUtils.cc bigint/BigUnsigned.cc bigint/BigUnsignedInABase.cc
./external/speex/Android.mk:56: TODOArm64: enable neon in libspeex
build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets
find: ‘/home/kristoffer/android/lineage/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates’: File or directory does not exist
build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets
build/core/base_rules.mk:183: *** hardware/samsung/audio: MODULE.TARGET.SHARED_LIBRARIES.audio.primary.universal7420 already defined by device/samsung/zerolte/audio.
build/core/ninja.mk:166: receipt for target ”/home/kristoffer/android/lineage/out/build-lineage_zerolte.ninja” failed
make: *** [/home/kristoffer/android/lineage/out/build-lineage_zerolte.ninja] Error 1
make: Leaving directory ”/home/kristoffer/android/lineage”
Is there's a repo missing in my manifest to get the files that are missing? When I google I can't seem to find which one.
Here's my local_manifest.
In fact there is a lineage os 14 build for s6 edge
alex.X said:
In fact there is a lineage os 14 build for s6 edge
Click to expand...
Click to collapse
Yes, but not one that works beyond the Setup guide.
Tried the Nexus zip already.
There is in fact even though it has quite a few bugs
alex.X said:
There is in fact even though it has quite a few bugs
Click to expand...
Click to collapse
Please point me to it.
As I said...... I already tried the Nexus version.
it would be so great to have a Lineage rom for our S6 edge ! is this phone so rare that it is not supported?
Still fed up with TW, but in love with this sreen.
I found a custom version of Lineage for this phone, but I'd prefer to build a clean version so that more updates/fixes come more often.
Here's the file: https://nexus-roms.eu/files/testing/zero/ResurrectionRemix-zero-multitarget-2017-06-14_1948.zip
If you don't care about loosing everything on your phone here's how to erase everything on it:
In TWRP
Click on Wipe.
Then click on Advanced wipe.
Select the following partitions to wipe:
Dalvik / ART Cache, System, Data, Internal Storage, Cache.
Now swipe to the right to wipe.
Go back one step and press Format data.
Type the word yes and press the blue button on the lower right corner that has a check mark in it.
Now, go back to main menu.
If you have downloaded the above mentioned zip file to your desktop and you have adb working on your local computer, connect the phone with a cable and type in the terminal:
Code:
adb devices
Once you've confirmed that the phone is recognized, do this command:
Code:
cd Desktop
adb push ResurrectionRemix-zero-multitarget-2017-06-14_1948.zip /sdcard/
It will take some time so grab a coffee or play with the cat.
Done?
Good!
Click Install.
Go all the way down to the bottom of that directory and click on the zip file and let it install.
Now just reboot the phone and wait until the boot is finished because the first boot will take a little while.
925I
Any news for release ???
On every lineage os rom I tried for g925f is the failure that, if I lock my phone with the powerbutton its impossible to turn it on again...I have to restart it. And also the sensitive buttons don't work
Billabomb75 said:
Any news for release ???
Click to expand...
Click to collapse
Well, there won't be one unless you're willing to help working on it.
Make a manifest that's as close as possible to Lineage stock and I'll add it to the repo and do a test build.
There aren't any repos for zerolte for Lineage as noone has added support for it.
Umeaboy said:
Well, there won't be one unless you're willing to help working on it.
Make a manifest that's as close as possible to Lineage stock and I'll add it to the repo and do a test build.
There aren't any repos for zerolte for Lineage as noone has added support for it.
Click to expand...
Click to collapse
Well I dont know how to work on android manifests
Billabomb75 said:
Well I dont know how to work on android manifests
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2329228 should help you learn how to do it.
I can't do ALL the work by myself you know.
Umeaboy said:
https://forum.xda-developers.com/showthread.php?t=2329228 should help you learn how to do it.
I can't do ALL the work by myself you know.
Click to expand...
Click to collapse
tnx m8 will look at
alex.X said:
In fact there is a lineage os 14 build for s6 edge
Click to expand...
Click to collapse
None of Lineage OS works on Galaxy S6 , i downloades 4 ROMs , none working. I had hope for one but when i turn screen of it doesnt come back
Its good to see Lineage is working on this.....waiting for a quick stable version from the team.
Very Thanks in advance.
[UNOFFICIAL][G920/5F][7.1.2] LineageOS 14.1 Stable Version
https://forum.xda-developers.com/galaxy-s6/orig-development/rom-lineageos-14-1-t3598775
Lol, TeamNexus always release a multitarget build here and for multitarget I mean 920/5 F/I/T/W8. You can build 925 if you want, I always build mine since my device is not supported (925S)
I am not responsible for bricked devices or anything
Unfortunately there is no official forum for the Spark X, so I thought I'd post this here if anyone needs it.
It's on security patch level 1 July 2018 so a worthwhile update if you're still on CyanogenOS.
Download: https://androidfilehost.com/?fid=1322778262903989315
Kernel sources: https://github.com/lineageos/android_kernel_cyanogen_mt6735
LineageOS Source code: https://github.com/lineageos/
Device tree: https://github.com/lineageos/android_device_wileyfox_porridgek3/
Does it have something to do with this one : rootmygalaxy .net /download-and-install-lineage-os-13-on-wileyfox-spark-x/ ?
h30x said:
Does it have something to do with this one : rootmygalaxy .net /download-and-install-lineage-os-13-on-wileyfox-spark-x/ ?
Click to expand...
Click to collapse
I didn't make that post on 'rootmygalaxy'. I did, however, make the builds.
It seems someone posted a link to my builds from their website.
That's fine though people can do what they want with my builds
I downloaded the [last version](https://eu.dl.twrp.me/porridgek3/twrp-3.2.3-0-porridgek3.img.html) of TWRP from their website but could not succeed in flashing it. OEM is unlocked, and no error message when flashing the recovery. So I can not try your build (neither try to build one myself).
h30x said:
I downloaded the [last version](https://eu.dl.twrp.me/porridgek3/twrp-3.2.3-0-porridgek3.img.html) of TWRP from their website but could not succeed in flashing it. OEM is unlocked, and no error message when flashing the recovery. So I can not try your build (neither try to build one myself).
Click to expand...
Click to collapse
Not sure how to help you there.
If you want to give a shot at building it, follow this guide, but replace 'crackling' with 'porridgek3' in all the commands and when it says
'repo init -u https://github.com/LineageOS/android.git -b lineage-16.0'
instead do
'repo init -u https://github.com/LineageOS/android.git -b cm-13.0'
Did you build the kernel boot image for MT6735?
You gave the link of the source you used https://github.com/lineageos/android_kernel_cyanogen_mt6735 but I do not know how to go from there to the kernel boot image.
If you did, it would be very nice to post it as well
hello i was looking for a samsung G928G S6 (Edge plus) kernel that has a drivedroid support but i was unable to find one.
since i am familiar with linux system i decided to try and build my first kernel.
i downloaded a stock kernel source from
https://opensource.samsung.com/uploadSearch?searchValue=g928
and other custom lineage os kernel from github
https://github.com/universal7420/android_kernel_samsung_universal7420
following this guide
https://forum.xda-developers.com/galaxy-s6/general/guide-how-to-build-samsung-kernel-july-t3429355
and this guide.
https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297
this are the steps that i did
export CROSS_COMPILE=$(pwd)/bin/aarch64-linux-android-
export ARCH=arm64 && export SUBARCH=arm64
when i came to make clean step i was getting this error
aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
i noticed in my toolchain folder aarch64-linux-android-gcc was missing
so i downloaded some other toolchains until i found one that has gcc
moving to next steps
make clean
make mrproper
make exynos7420-zenlte_defconfig based on stock kernel and
make lineageos_zenlte_defconfig based on lineage os kernel
when i did the make -j$(nproc --all) i get this error
make: *** [Makefile:552: scripts] Error 2 and when i checked in Makefile line 552 i found this
$(Q)$(MAKE) $(build)=$(@)
i get this error everytime i try. i use Arch linux i tried in Ubuntu same thing
Cool How about Kali-linux mod did you check it?
We have Kali-Linux mod for S6 it has drive-droid build-in
Johannes89 said:
Cool How about Kali-linux mod did you check it?
We have Kali-Linux mod for S6 it has drive-droid build-in
Click to expand...
Click to collapse
i tried it yesterday but it hangs on creating image since my device is s6 edge+ not s6
Try to create img file from other source like windows or other program and move it to your phone
so i followed your advice and tried to build on windows 10 ubuntu from their store (though i hate using windows) and it was a success. i patched drivedroid stuff in the kernel
i build one from samsung official kernel and boom! drivedroid works , after a minute i experience some never ending bootloops , in 30 seconds i can use my phone after that it boots again, the loop never ends.
i clone another kernel the lineage one , after spending the whole day building , failing ,errors , bugs, electricity issue and stuff ,
I HAVE FINALLY HAVE A DEVICE THAT WORKS NO BOOTLOOPS AND DRIVEDROID IS WORKING. though the lineage os rom has some camera problems . But yeah it was a good day
I am trying to build Lineage OS 18, using the Device Tree and Kernel for Lineage OS 17. When I try to run brunch avicii I get:
error: vendor/qcom/opensource/interfaces/capabilityconfigstore/1.0/Android.bp:3:1: failed to find variation "linux_glibc" for module "[email protected]" needed by "[email protected]" error: vendor/qcom/opensource/interfaces/capabilityconfigstore/1.0/Android.bp:3:1: failed to find variation "windows" for module "[email protected]" needed by "[email protected]" 14:32:43 soong bootstrap failed with: exit status 1
I also tried build Lineage OS 17 for the device, got the same error. I also tried building Lineage OS 18 for the Google Pixel 5, but the device was built without any errors, any ideas?
If you don't have a Linux device or don't have enough storage space to compile Custom Recovery, then maybe the following link can help you.
- Visit my GitHub repository and Fork it
(https://github.com/VThang51/ROM_Recovery-Builder)
-(Don't forget to read the README.md)
- Custom Recovery versions are supported:
+ OrangeFox-RP Builder (Fixing Bug)
+ PitchBlack-RP Builder
+ RedWolf-RP Builder
+ SkyHawk-RP Builder
+ TeamWin-RP Builder
- If the compilation is successful, please comment below. Just like TWRP, I also want to hear your story
Nice but i need to learn how to build twrp first haha
Guan Yu said:
Nice but i need to learn how to build twrp first haha
Click to expand...
Click to collapse
Nice, If you have a device tree and make sure it doesn't fail. I will guide you haha
I'm trying this out right now with the oneplus 7 pro 5g since there's like no development active on this specific model
TechX1991 said:
I'm trying this out right now with the oneplus 7 pro 5g since there's like no development active on this specific model
Click to expand...
Click to collapse
Make sure your Device tree is not corrupted. Because when it fails, it will have to start over and it takes at least 20-60 minutes
VThang0511 said:
Make sure your Device tree is not corrupted. Because when it fails, it will have to start over and it takes at least 20-60 minutes
Click to expand...
Click to collapse
I was using device trees from Lineage's github, but seems 3 devices i've tried so far all fail with
fatal: Remote branch master not found in upstream origin, error exit code 128
TechX1991 said:
I was using device trees from Lineage's github, but seems 3 devices i've tried so far all fail with
fatal: Remote branch master not found in upstream origin, error exit code 128
Click to expand...
Click to collapse
Haha, This error is quite rare if you double check the options. This error says your Branch is not "master" (It's just the Branch name on my URL). Double check the Branch name on GitHub.If you don't know, send me the device tree link and I'll compile it for you
VThang0511 said:
Haha, This error is quite rare if you double check the options. This error says your Branch is not "master" (It's just the Branch name on my URL). Double check the Branch name on GitHub.If you don't know, send me the device tree link and I'll compile it for you
Click to expand...
Click to collapse
just my luck, I get the "rare" error multiple times lol it was more for the learning of it that I was doing this. TWRP is available for the 3 devices I tried (op 7 pro 5g, op 8t and op 6t), but wanted to learn to do it so I can try it on lesser known devices like asus zenphone 1 or razer phone 2