Totally new to ROM building, but I want LG's crap rom off my phone, so I'm trying to install Slim7 on it... yea, it's not easy, since there's next to no developer support for this device.
I've downloaded LG's source and have tried to assimilate it into Slim's source (basically merging everything but the frameworks folder) and am now trying to build.
But this is the Ninja error I get:
Code:
ninja: Entering directory `.'
ninja: error: '/home/android/Desktop/cheap_android_love/out/target/product/generic_arm64/obj/KERNEL_OBJ/usr', needed by '/home/android/Desktop/cheap_android_love/out/target/product/generic_arm64/obj/SHARED_LIBRARIES/libtinyalsa_intermediates/mixer.o', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
I've checked the directory, and the "obj" folder doesn't even exist in the out folder, so this error seems impossible to me... help me out? What files do I need to look at?
XDA:DevDB Information
Slim7 // LG K20 Plus, ROM for all devices (see above for details)
Contributors
mocklee
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: LG Source
Version Information
Status: Testing
Created 2017-07-24
Last Updated 2017-07-23
Related
I followed the directions for building CM12.1 for Samsung Galaxy S5 from CM's wiki; however, I changed my local_manifest.xml file to pull vendor code from theMuppets repository (rather than using the extract script). When I run the command mka bootimage, I recieve the following error:
Target boot image: /home/user/android/system/out/target/product/klte/boot.img
/home/user/android/system/out/target/product/klte/boot.img maxsize=13878136 blocksize=135168 total=13803520 reserve=270336
error: /home/user/android/system/out/target/product/klte/boot.img too large (13803530 > [14057472 - 270336])
make: *** [/home/user/android/system/out/target/product/klte/boot.img] Error 1​
I am not sure what is causing the boot.img to be too large since I am simply trying to compile from the CM12.1 source and have not added any modifications. Has anyone seen this error before or know a workaround?
Thanks
Hey Guys,
So happy that there's a new AOKP coming. I'd like to work towards Device Maintainer. I've got a 1+1 that I want to get going first, then I'll look at your list of other phones that need maintainers. I have two current issues:
1) My 1+1 is running MultiROM TWRP 2015-08-03 (v2.8.7) and multi-rom v32k tramponline v26. I have two 4.4 ROMS but my AOKP ROM seems to be having issues with the kernel. So my question is: can I just blow away my current roms and flash AOKP-Marshmallow?
2) I'm trying to build for Bacon using the Barbeque (Arch) linux distro. When running make I get the following:
$ time make rainbowfarts
...
Header: /home/russellh/Android/AOKP/out/target/product/bacon/obj/include/time-services/time_genoff.h
host C: mkbootimg <= system/core/mkbootimg/mkbootimg.c
prebuilts/clang/linux-x86/host/3.6/bin/clang: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
build/core/binary.mk:817: recipe for target '/home/russellh/Android/AOKP/out/host/linux-x86/obj/EXECUTABLES/mkbootimg_intermediates/mkbootimg.o' failed
make: *** [/home/russellh/Android/AOKP/out/host/linux-x86/obj/EXECUTABLES/mkbootimg_intermediates/mkbootimg.o] Error 127
#### make failed to build some targets (01:01 (mm:ss)) ####
real 1m0.514s
user 0m22.750s
sys 0m16.210s
So I checked what is installed:
[[email protected] AOKP]$ pacman -Ss ncurses
core/ncurses 6.0-4 [installed]
System V Release 4.0 curses emulation library
I tried creating a symbolic link to libncurses.so -> libncurses.so.5 but that didn't work.
Any suggestions would be great.
Thanks,
Russ
Dinsdale247 said:
Hey Guys,
So happy that there's a new AOKP coming. I'd like to work towards Device Maintainer. I've got a 1+1 that I want to get going first, then I'll look at your list of other phones that need maintainers. I have two current issues:
1) My 1+1 is running MultiROM TWRP 2015-08-03 (v2.8.7) and multi-rom v32k tramponline v26. I have two 4.4 ROMS but my AOKP ROM seems to be having issues with the kernel. So my question is: can I just blow away my current roms and flash AOKP-Marshmallow?
Click to expand...
Click to collapse
Okay, I was able to update to MultiROM TWRP v3.0.0 and multi-rom v33a. I tried creating a new rom and flashing aokp_bacon_mm_nightly_2016-02-24.zip but it always ended with:
Code:
assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0123","TZ.BF.2.0-2.0.0134") == "1"
Updater process ended with ERROR: 7
Failed to install ZIP!
Restoring mounts
Updating partition details...
...done
Erasing incomplete ROM
I then created a new secondary ROM using an older cyanogenmod zip I had around and then tried to upgrade that ROM to aokp_mm. No love. Any suggestions?
Russ
Dinsdale247 said:
Okay, I was able to update to MultiROM TWRP v3.0.0 and multi-rom v33a. I tried creating a new rom and flashing aokp_bacon_mm_nightly_2016-02-24.zip but it always ended with:
Code:
assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0123","TZ.BF.2.0-2.0.0134") == "1"
Updater process ended with ERROR: 7
Failed to install ZIP!
Restoring mounts
Updating partition details...
...done
Erasing incomplete ROM
I then created a new secondary ROM using an older cyanogenmod zip I had around and then tried to upgrade that ROM to aokp_mm. No love. Any suggestions?
Russ
Click to expand...
Click to collapse
It is due to old and outdated firmware. Flash cm13 nightly once and then reflash the AOKP build.
INCREMENTAL UPDATE GENRATOR SCRIPT
Incremental updates are the new trend amongst devs nowadays, and many maintainers wonder how to do this.
So I made a handy script to automate that ( make sure that your device has proper incremental commits in trees) , and here's a guide on how to use it:
Just run the script through the command python3 incremental.py
It will ask you for the directory of the old target files and the new one, so give the path which includes the name
Like this : out/target/product/beryllium/obj/PACKAGING/target_files_intermediates/eng-2.zip
Do this for both the old and the new target files of your builds
This will generate a package named incremental.zip, which can be flashed through recovery.
Devices with file based incremental give flashing error with incrementals sometimes if stuff is changed, it happens even if you don't use script. To bypass that, just remove asserts from the incremental zip flashing code. Which is in the META-INF folder.
Here is the link to the script: https://github.com/Dhruvgera/custom_python_scripts/blob/master/incremental.py
Peace out
Hit that thanks button if this helped you
XDA:DevDB Information
Incremental updates generator, Tool/Utility for all devices (see above for details)
Contributors
Dhruvgera
Source Code: https://github.com/Dhruvgera/custom_python_scripts.git
Version Information
Status: Stable
Created 2020-02-16
Last Updated 2020-02-16
jabra fan sir
NOICE
Great work sir ?
Sar tussi great ho
Kernel compilation error '"aarch64-linux-android-gcc" is not allowed to be used.'
I'm building the kernel with LineageOS 17.1 / Android 10 r31 however the build process errors out during kernel compilation.
Specifically with:
Code:
"aarch64-linux-android-gcc" is not allowed to be used. See https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools for more information.
make[3]: *** [/home/saltoin/android/lineageos-17.1/kernel/samsung/universal8895/scripts/Makefile.build:153: scripts/mod/devicetable-offsets.s] Error 1
Following the link says that any host tools in PATH won't be allowed to be used during compilation. However, `aarch64-linux-android-gcc` is not from my path but supplied by the build tools. Unless I'm mistaken in that assumption.
Regardless, exporting TEMPORARY_DISABLE_PATH_RESTRICTIONS=true allows aarch64-linux-android-gcc.
Unless I'm missing something, I don't believe I should be getting this error.
Thoughts?
Hello there, have you found any solution?
TEMPORARY_DISABLE_PATH_RESTRICTIONS=true doesn't work in the config file. What do you mean by export? Thanks in advance for help.
Build System Changes for Android.mk Writers
As a temporary measure, you can set TEMPORARY_DISABLE_PATH_RESTRICTIONS=true in your environment to temporarily turn off the error checks and allow any tool to be used (with logging).
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