ok so the first problem im having is with the fixup-mountpoints file. i have used t'he commands and entered the device specific data for the mountpoints and it still gives me the mk69 and 70 errors saying it they live on /dev/block/bootdevice/by-name/boot and userdata.

it doesnt actually error and the build completes if i let it run but ive gone back over and over and rechecked spelling and placement and every thing. ive even gone and changed the devuce name of another device listed and changed its mountpoints as well. but no go

Hello every one

Ive been working on this for a while off and on as time allows for research and development but I really love the cv1 products that Lg has like the Aristo 2, Aristo 2 plus, and the K8 plus.

This port will and cover all three phones and since the source code is the same should work for any of them. i started from scratch this time around collecting the needed blobs from my device by hand but and using the guides. This process has been a bit of a pain though and im still having trouble.

Hardware
Lg Aristo 2 plus cv1 LM-X210TAL
SoC : Qualcomm Snapdragon 425 (Quad-core 1.4GHz Cortex A53)
RAM : 3GB/4GB
ROM : 16GB
5" TFT LED Screen with 1480x720

Platform :

Android Start with version 7.1.2
Kernel version : 3.18.140(Oreo)
ARCH: arm64

@dieharddan

yes the bootloader is unlocked i did that a couple months ago when i recieved the phone. And yes i downgraded or rather switched back to proper firmware. i say that because i refuse to go any higher than pie at this point. im currently running dirty unicorns rom with and got all the extras working by flashing the lineage vendor. found that out by accident by switching from lineage to unicorns.

ok so heres the problems im having....

using the gsi installer, formatting userdata to ext4 using fastboot errors every time. when i go to twrp and change the file system of data from fsf2 to ext4 its wipes the internal storage ofcourse then i cannot add the gsi installer back to internal storage. windows just hangs for as long as you let it trying to do so. i can install the gsi without formatting to ext4 but when i was working on porting to the lg aristo 2 i remember that data had to be able to be formatted to ext4 since the img files are compiled to that format.

when i use the ubports installer it hangs at preparing system image and thats both having to fastboot boot the twrp image and when it actually goes to the compiled bootable recovery

Re: Google Pixel 3a (sargo)

Any clues as to why i cant get this operating system to boot. Its driving me crazy that so many people are getting it work on thier pixel devices but i cant get it work at all.

ok guys i have tried both fastbooting the halium-boot.img dtbo.img vbmeta.img and using the gsi installer and i have tried using the ubports installer and i cannot get the os to load. it just goes to fastboot

I can't seem to get the os working or to boot on my pixel 3a. The ubports installer says sargo isn't supported

i am desperate for help. i have been porting my device the lg aristo 2 to halium-7.1 for a couple months now. i have all my sources extracted from the device and i have completed making all the images about 3 weeks ago.

i have read the docs to the point of insanity and i cannot figure out what the problem is. The build is stable and produces no errors. I cant find any thing wrong with the kernel but when i go to install i get nothing from ssh or telnet.

the kernel source is 3.18 plus upstream to latest caf. i have tried help at telegram and i only get the bot who will check my kmsg`s and says the kernel is fine. but thats all i know.

im installing as system as root if i use the halium rfs it just installs but no ssh or telnet. if i use the pm-rootfs on install it starts unpacking and says no space left on device. i tried it today with out my phone plugged in and it does that period.

please help

actually i pulled every thing from the phone. what extract-files.sh did not i did by hand. But i made the list myself. like i said i spent a lot of time preparing for this.

besides i downloaded two other builds of the /halium/devices/manifests lists and they are giving me the same problem.

yes i have tried. i was very rudely spoken to on telegram and ignored completely every where else. any way im here for some help.....

im not gonna lie i have been trying to do this for a year and have found my self cut short by either technology or knowledge. Trying to find the right machine with ram and hdd was a problem due to limited funding but i have to tell you when i compiled my first kernel a few months ago and relearned my c++ coding skills it was exciting. so even now today being able to get past the obvious build errors and see make build my kernel with in halium soi9urce i gotpretty happy.

but after downloading source for my own device and two others jusr to watch them all have pretty much the same errors sucked. i really hope you can help.

i think part of my problem is due to my device having to be 32bit a 64 wont boot no matter what. so ive tuned the build down to the same.i have removed any dependency that adds 64bit as well. besides i cant flash a 64bit image on a 32bit twrp and my porting it over has failed as well.

first upon using make or mka its starts saying build/core/binary.mk is overriding my target then going to multiple definitions of popcount_tab in for shared and static libraries and ending with a CLANG++ error code 1

Do you know what the definition of insanity is? I have read the docs over and over. Not trying to be rude but there is alot about building a device that is missing and i have scrounged around for quite some time.

But today i made some progress i got the build system to start making a bootimage. But it craps out at after building and installing the kernel modules.

you can take a look at my source at https://github.com/Duhjoker under android lge cv1.

the errors im getting are previous definitions in the static and shared libraries which i guess causes a clang++ linker error number 1. ive been pulling my hair out now for 48 hours and i cannot find a solution.

i can recreate the errors by setting up any device and trying to build

hello i have been working on porting over to the aristo 2 for a couple weeks now and just found the forum.

the problem with my device is that no one has completed making a rom for it. the roms available do not boot. so i have been trying to port on my own and not having much luck.

i have created a repo on github and i have eveey thing i need but i keep getting errors for sepolicy.mk 9 too many files open and no product spec.

i really just want to make a boot img at this point. Is there a guide on that some where