[DEV][ROM][2018-04-18]LineageOS bring up [Motorola X4 payton][15.1] - Moto X4 ROMs, Kernels, Recoveries, & Other Develop

Update 2018-06-10:
See this thread for more up to date (and working!) development:
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
@erfanoabdi, @munchycool, @mightysween did some heroic hacking and fixed the major blockers for this phone. I apologize if I missed anyone because either I missed their posts or I didn't match them up to their XDA login. Be sure to thank them when you see their posts. There is a booting lineage os rom in the thread above. Heed the warnings, it is still experimental, and will probably require a full wipe to get it to boot.
I will eventually merge my repos with the ones in the ROM thread.
Original post below:
First off, credit goes to @invisiblek, @mightysween, and @kraatus90. I used their repos as a starting point for guidance.
I am working on bring up and porting lineage-15.1 to the payton.
kernel
device tree
vendor files
So far, it builds without major errors.
Booting to the rom hangs at the boot screen.
Booting to recovery works (lineageos recovery), but not much else is working otherwise.
The vendor files are from the stock retail rom OPWS27.57-25-6-10. This is Oreo 8.0.
I haven't tried flashing the ROM through TWRP, just fastboot.
The build process produces a zip file with a payload.bin inside. You can extract it with payload.bin extractor. You might need to install python-protobuf and python-lzma to get it to work.
Change a/b depending on what partition is currently working and which one you don't mind overwriting. I'm not sure if this will interfere with stock updates, so you might want to make a back up first.
Code:
fastboot flash boot_a boot.img
fastboot flash system_a system.img
fastboot --set-active=a reboot
What you can do:
Look through the device tree and submit pull requests for fixes. Boardconfig.mk, device.mk, and proprietary-files.txt will need lots of work.

---

*reserved*

---

Awesome work getting to this point.
I am still strapped for time, but out of curiosity does USB/adb come up in lineage recovery or during boot? That was what put the brakes on for me initially in my 7.1/14.1 based build attempt.

---

mightysween said:
Awesome work getting to this point.
I am still strapped for time, but out of curiosity does USB/adb come up in lineage recovery or during boot? That was what put the brakes on for me initially in my 7.1/14.1 based build attempt.
Click to expand...
Click to collapse
No usb/ADB yet, but that is a priority so that we can start debugging and fixing things. I think I have to look over the init scripts.

---

gee one said:
No usb/ADB yet, but that is a priority so that we can start debugging and fixing things. I think I have to look over the init scripts.
Click to expand...
Click to collapse
I had an init fix suggested by another dev for a similar device... never got to test it. Let me dig around in the threads and find it.
---------- Post added at 06:10 PM ---------- Previous post was at 06:04 PM ----------
mightysween said:
I had an init fix suggested by another dev for a similar device... never got to test it. Let me dig around in the threads and find it.
Click to expand...
Click to collapse
Actually, looks like I did test it unsuccessfully.
Seems like idVendor and idProduct are not being properly set for different USB properties.

---

gee one said:
First off, credit goes to @invisiblek, @mightysween, and @kraatus90. I used their repos as a starting point for guidance.
I am working on bring up and porting lineage-15.1 to the payton.
Click to expand...
Click to collapse
Great news, thank you already for putting effort into this :victory:
Regarding adb/USB. Both are working in the official TWRP for payton, mabye it helps if you take a look at their source code.
Cheers
Stefan

---

Super stoked to see the work being done for this phone. I bought it with the hopes that we'd see some decent ROM options come out of it. Subscribing for updates! You can do eet!

---

... Than you... Thank you... Thank you for all of you that building lineage for Payton ( I have XT-1900-7 EU) ... I bought this phone phone also with the hopes that some one will build up Lineage for it...

---

Just got this phone. Really hope we get a stable version of this soon. Not sure how much I trust the manufacturer OS.

---

trying to port LOS 15.1 to sony xperia xa2 i was hoping i could use some of your work but i see you have the same results. i can boot to lineage recovery, normal boot gets stuck on logo and fastboot boot boot.img gives me battery charging animation. maybe there's something that needs to be changed in init, boot.img from lineage works fine with aosp

---

frantisheq said:
trying to port LOS 15.1 to sony xperia xa2 i was hoping i could use some of your work but i see you have the same results. i can boot to lineage recovery, normal boot gets stuck on logo and fastboot boot boot.img gives me battery charging animation. maybe there's something that needs to be changed in init, boot.img from lineage works fine with aosp
Click to expand...
Click to collapse
gee one said:
Well, I'm working on building a lineage rom for this phone, but I can't get the thing to boot. I am using a copy of the device tree for the nash/moto Z2 force.
The boot.img will work with the stock rom, but I can't get lineage to boot. I just get bootloops until it falls back to the other A/B partition. I can boot into the lineage recovery mode from the boot.img I made, so at least that works.
I think the issue is with init. Does anyone have any hints on what will work? The marlin has the same a/b partitions, so I might try building aosp for the marlin and hope that will give me some hints about what is missing.
Click to expand...
Click to collapse
From another thread

---

steveeJ said:
Great news, thank you already for putting effort into this :victory:
Regarding adb/USB. Both are working in the official TWRP for payton, mabye it helps if you take a look at their source code.
Cheers
Stefan
Click to expand...
Click to collapse
Didn't realize this... thanks, will take a look at the source.
---------- Post added at 02:11 AM ---------- Previous post was at 01:52 AM ----------
mightysween said:
Didn't realize this... thanks, will take a look at the source.
Click to expand...
Click to collapse
@gee one FYI, although 7.1 base, addresses are the same... manual rewrite solves idVendor/Product issue.
https://github.com/TeamWin/android_...ndroid-7.1/recovery/root/init.recovery.usb.rc
---------- Post added at 02:16 AM ---------- Previous post was at 02:11 AM ----------
mightysween said:
Didn't realize this... thanks, will take a look at the source.
---------- Post added at 02:11 AM ---------- Previous post was at 01:52 AM ----------
@gee one FYI, although 7.1 base, addresses are the same... manual rewrite solves idVendor/Product issue.
https://github.com/TeamWin/android_...ndroid-7.1/recovery/root/init.recovery.usb.rc
Click to expand...
Click to collapse
BTW, totally different vendor/product addresses than I had arrived at... which probably explains why it works
The rest of the usb init seems pretty similar to where I ended up before. If it works in LOS recovery, it should carry through boot to give us some debug
---------- Post added at 02:56 AM ---------- Previous post was at 02:16 AM ----------
frantisheq said:
trying to port LOS 15.1 to sony xperia xa2 i was hoping i could use some of your work but i see you have the same results. i can boot to lineage recovery, normal boot gets stuck on logo and fastboot boot boot.img gives me battery charging animation. maybe there's something that needs to be changed in init, boot.img from lineage works fine with aosp
Click to expand...
Click to collapse
Any adb/debug from the XA2?
Obviously, we are going to face some serious kernel debugging...
Wonder if we can manually unpack/strip down/repack a boot.img that will at least get us into a position for logging.
---------- Post added at 03:03 AM ---------- Previous post was at 02:56 AM ----------
mightysween said:
Didn't realize this... thanks, will take a look at the source.
---------- Post added at 02:11 AM ---------- Previous post was at 01:52 AM ----------
@gee one FYI, although 7.1 base, addresses are the same... manual rewrite solves idVendor/Product issue.
https://github.com/TeamWin/android_...ndroid-7.1/recovery/root/init.recovery.usb.rc
---------- Post added at 02:16 AM ---------- Previous post was at 02:11 AM ----------
BTW, totally different vendor/product addresses than I had arrived at... which probably explains why it works
The rest of the usb init seems pretty similar to where I ended up before. If it works in LOS recovery, it should carry through boot to give us some debug
---------- Post added at 02:56 AM ---------- Previous post was at 02:16 AM ----------
Any adb/debug from the XA2?
Obviously, we are going to face some serious kernel debugging...
Wonder if we can manually unpack/strip down/repack a boot.img that will at least get us into a position for logging.
Click to expand...
Click to collapse
...may need to explore blacklisting/disabling peripherals to get to a basic boot state and bringup from there.

---

adb is not working. on lenovo kingdom we have used /proc/last_kmsg after reboot to twrp to see what's going on
https://github.com/K920/android_ker...mmit/7551e6960c9bbe31824437f7ba40c87b53157f3e
https://github.com/K920/android_ker...mmit/a24c3085fb001cf0b81855770bf327d9b49b5b0f
EDIT: got logcat working. eng build, not userdebug.
1. unpacked lineage boot.img using https://github.com/xiaolu/mkbootimg_tools
2. unpacked stock boot.img prepatched with magisk, not sure if magisk plays some role in it
3. replaced cmd_line=... in in lineage img_info file with the one from stock boot.img
Code:
console=ttyMSM0,115200,n8 androidboot.console=ttyMSM0 earlycon=msm_serial_dm,0xc170000 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 sched_enable_hmp=1 sched_enable_power_aware=1 service_locator.enable=1 swiotlb=1 androidboot.configfs=true androidboot.usbcontroller=a800000.dwc3 buildvariant=user
4. repacked lineage boot.img
looks like i just need to fix the camera and add some *.so to continue boot process.
EDIT: missing .so's are there, in /odm/lib64. /oem in your case. i have tried to copy them to /vendor/lib64 and it helped a little

---

i'm an idiot, forget what i wrote up there. looks like the generated kernel is all wrong, it's only 10MB compared to the 47MB in stock boot.img. after replacing kernel in boot.img with the stock one it tries to boot, the lineage one won't even try

---

Syncing fresh sources now, and will start working on this again soon!

---

frantisheq said:
i'm an idiot, forget what i wrote up there. looks like the generated kernel is all wrong, it's only 10MB compared to the 47MB in stock boot.img. after replacing kernel in boot.img with the stock one it tries to boot, the lineage one won't even try
Click to expand...
Click to collapse
But is adb working during boot? If so, can you post the boot.img even if it is otherwise junk... I can't seem to get adb up during boot and it is really bugging me
---------- Post added at 01:47 AM ---------- Previous post was at 01:14 AM ----------
Out of curiosity, how much physical memory are you guys compiling with? I have jack configured, 8GB on a quad-core i5 system and I still needed to add an 8GB swap partition just to get through ninja!

---

same here 8GB RAM and 16GB swap just to be safe.
stock sony ramdisk with working adb attached
EDIT: after hours of comparing lineage and stock boot.img all i have to do to get adb working on eng build is changing androidboot.hardware=pioneer to androidboot.hardware=qcom in img_info cmd_line='...
pioneer is a codename for sony xa2
BOARD_KERNEL_CMDLINE += androidboot.hardware=pioneer
changed to
BOARD_KERNEL_CMDLINE += androidboot.hardware=qcom
in BoardConfig.mk

---

frantisheq said:
same here 8GB RAM and 16GB swap just to be safe.
stock sony ramdisk with working adb attached
EDIT: after hours of comparing lineage and stock boot.img all i have to do to get adb working on eng build is changing androidboot.hardware=pioneer to androidboot.hardware=qcom in img_info cmd_line='...
pioneer is a codename for sony xa2
BOARD_KERNEL_CMDLINE += androidboot.hardware=pioneer
changed to
BOARD_KERNEL_CMDLINE += androidboot.hardware=qcom
in BoardConfig.mk
Click to expand...
Click to collapse
Seems to already be set to "qcom" on this device... I think we have some issues in usb init that need to be fixed.
Running a test build right now just to see where I stand with my new setup... new machine is on the slow side, but seems to be grinding along now after some memory issues.

---

mightysween said:
Running a test build right now just to see where I stand with my new setup... new machine is on the slow side, but seems to be grinding along now after some memory issues.
Click to expand...
Click to collapse
Failing RIGHT at the end as it generates the payload file...
Reinstalled all build packages, re-synced... no luck yet. Anyone run into this brillo error?
It generates the entire system, userdata, cache, radio, boot, etc... but simply fails to pack it all into the payload in the final step. Frustrating.
UPDATE: Disregard. This is a disk-space error. Apparently LOS15 is more beastly than I thought...256GB partition seems a bit on the small side suddenly
UPDATE 2: Gave up, moving to a Google Cloud Platform build system... should have done it from the beginning

---

Let the games begin!