Last weekend I decided to give LineageOS and Nethunter a try on my Moto Z Play device, and found a problem during installation of the kernel file from build.nethunter.com/nightly:
kernel-nethunter-genenric-armhf-xxx.zip
(tried both 2017.11-18-1618 and 3.20-20170903-2143.zip).
I believe this is the relevant output from recovery.log:
Code:
Running boot image patcher...
- Found boot partition at: /dev/block/mmcblk0p37
- Dumping & unpacking original boot image...
CANNOT LINK EXECUTABLE
"/tmp/nethunter/boot-patcher/tools/bootimg": "/sbin/libc.so" is 64-bit instead of 32 bit
libc: CANNOT LINK EXECUTABLE "/tmp/nethunter/boot-patcher/tools/bootimg": "/sbin/libc.so" is 64-bit instead of 32 bit
libc: Fatal signal 6 (SIGABRT), code-6 in tid 621 (bootimg), pid 621 (bootimg)
Aborted
- Error: Unpacking boot image failed!- Aborting...
So I need guidance from XDA experts on addison and Nethunter. Is it possible that the incorrect version (64-bit) of libc.so was included by mistake in the kernel build of Nethunter? If so, where should I obtain the correct 32-bit version?
By the way, I tried to install the Nethunter these kernel patches on top of both LineageOS 14.1 & LineageOS 15.1 ROMs.
Thanks for your time and great work. I hope to eventually contribute a how-to install Nethunter guide for addison users.
hi, could you install a nethunter kernel on the z play?
stalion said:
hi, could you install a nethunter kernel on the z play?
Click to expand...
Click to collapse
readme/MMI-PPW29.131-27-1.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Related
Hi everyone,
I'm currently working on building Lineage OS 13, which is unsupported on the Nexus 7 2013. My device has WiFi issues with 14.1 and none of the Marshmallow ROMs incorporate a fix for the Krack vulnerability. Since this fix is already part of the cm-13.0 branch, I've been trying to build it but running into the following error when I run "breakfast flo".
Code:
build/core/product_config.mk:257: *** No matches for product "lineage_flo". Stop.
Device flo not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
I have already incorporated the Muppet's proprietary blobs for Flo but don't know how to deal with this error. I have experience with the Linux command line and programming using Java but am new to ROM-building.
flamingspartan3 said:
Hi everyone,
I'm currently working on building Lineage OS 13, which is unsupported on the Nexus 7 2013. My device has WiFi issues with 14.1 and none of the Marshmallow ROMs incorporate a fix for the Krack vulnerability. Since this fix is already part of the cm-13.0 branch, I've been trying to build it but running into the following error when I run "breakfast flo".
Code:
build/core/product_config.mk:257: *** No matches for product "lineage_flo". Stop.
Device flo not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
I have already incorporated the Muppet's proprietary blobs for Flo but don't know how to deal with this error. I have experience with the Linux command line and programming using Java but am new to ROM-building.
Click to expand...
Click to collapse
You will need to apply device tree rebrand like it's done in 14.1: https://github.com/LineageOS/android_device_asus_flo/commit/e596a332b44ea40769fc516c451728b1cd58eb2b
flex1911 said:
You will need to apply device tree rebrand like it's done in 14.1: https://github.com/LineageOS/android_device_asus_flo/commit/e596a332b44ea40769fc516c451728b1cd58eb2b
Click to expand...
Click to collapse
Thanks for the help! I was able to get it to work by running 'lunch cm_flo-userdebug' and then mka.
Are you sure the Krack fix isn't already in 14.1:
https://www.lineageos.org/Changelog-15/
KRACK Wi-Fi vulnerability has been fixed in both LineageOS 14.1 and 13.0
Click to expand...
Click to collapse
THIS THREAD CLOSED
--------------------------
Hi friends,
Because lineageOS stop supporting xiaomi devices this month, so I decided to build LOS 16 ROM for sagit myself.
I have some experience of using linux, but that is my first time to build an Android rom.
I follow the official guide to build. https://wiki.lineageos.org/devices/sagit/build And I got the freshable zip rom "successfully".
However, after I install it via the lastest TWRP, it stuck on the boot MI logo and can not enter the system.
I ask one oneplus developer, he told me some xiaomi device need specific clang version, but he can not give me a solution. I come here and hope someone can give me some propose.
-----------------------------
UPDATE, I found los group ready the re-support xiaomi device. https://github.com/LineageOS/hudson/commit/9e0206569670a2566562e000b9f1e3492eacca83
But I still hope get some answer just for study.
-----------------------------
UPDATE II
I found the reason that I use a wrong branch of VT repo. I use another VT repo in gitlab when the github repo was closed because of DMCA. And the default branch of the gitlab one is not LOS16. My bad. Sorry to bother everyone.
Thread closed!
-LTT
Hello Guys I'm Building Lineage OS 17.1 but got some errors while compiling .Please assist me solving error I'm new in building roms.
I have pasted my error below. I have used device tree, kernel from Lineage repository and vendor files from muppets
- https://pastebin.com/2BLvm99c
Hello all developer
I'm kali nethunter user
please port kali nethunter with wifi monitor mode supported
Sorry for bad eng
Thank U
I know how to build custom ROMs however this seems a bit different. I'll try to get my head around it however I don't want to do a significant amount of testing.
Notes for myself:
Building NetHunter | Kali Linux Documentation
Those of you who want to build a Kali NetHunter image from our GitLab repository may do so using our Python build scripts: [email protected]:~$ git clone https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-project [email protected]:~$ [email protected]:~$ cd kali-nethunter-project/nethunter-installer/...
www.kali.org
Porting NetHunter to New Devices manually | Kali Linux Documentation
In order to port NetHunter to a new device, it’s important to understand how NetHunter is separated. NetHunter is divided by the rootfs (also known as the chroot but will be referred to here as rootfs) and the kernel. For the most part, the rootfs is not important to your Android device as it...
www.kali.org
Robert314 said:
I know how to build custom ROMs however this seems a bit different. I'll try to get my head around it however I don't want to do a significant amount of testing.
Notes for myself:
Building NetHunter | Kali Linux Documentation
Those of you who want to build a Kali NetHunter image from our GitLab repository may do so using our Python build scripts: [email protected]:~$ git clone https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-project [email protected]:~$ [email protected]:~$ cd kali-nethunter-project/nethunter-installer/...
www.kali.org
Porting NetHunter to New Devices manually | Kali Linux Documentation
In order to port NetHunter to a new device, it’s important to understand how NetHunter is separated. NetHunter is divided by the rootfs (also known as the chroot but will be referred to here as rootfs) and the kernel. For the most part, the rootfs is not important to your Android device as it...
www.kali.org
Click to expand...
Click to collapse
solohcat97 said:
Hello all developer
I'm kali nethunter user
please port kali nethunter with wifi monitor mode supported
Sorry for bad eng
Thank U
Click to expand...
Click to collapse
here you're, A powerful kernel for nethunter :^)
rtl8188eus, rtl8812au, rtl8814au ported also in modules zip, load them in Androidsu terminal via insmod/system/lib/modules/<Module Name>
lsmod to check the status
@Robert314 also you might find this useful for rom, maybe become a PocoHunter phone
Hi all,
i need your support.
I did not manage to install Android GSI / Treble (lineage-18.1-treble_arm64_a) to the:
Umidigi_A3_Pro_N
with
Android 8.1:
and current Software Version:
UMIDIGI_A3_Pro_N_V1.4_20190416
from here: https://community.umidigi.com/forum.php?mod=viewthread&tid=18713
I tried this version:
lineage-18.1-20211214-UNOFFICIAL-treble_arm64_avS.img.xz
from:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/lineage-18.1-20211214-UNOFFICIAL-treble_arm64_avS.img.xz/download
without sucess, the device does not boot after flashing the .img file within CWRP (Team Win Recovery Project 3.3.1.0 repack Cleopatra81
treble_arm64_a should be the right image, or am i wrong, my Treble Info Check App said so, see attached screenshots?
I also asked for Support in the Smartphone thread, but maybe someone has here some ideas to fix it?
Umidigi A3 Pro - TWRP & Stock Rom
Reserved exclusively for the stock rom V1.0_20181122 Download the stock rom V1.0_20181122 at the following link : https://mega.nz/#!yxkUVA4I!0exovcsKTXb75YIBZfrqDC6Ak01wsv_Bp3Nl5mGQ7o8 Download the TWRP at the following link ...
forum.xda-developers.com