[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Moto X Pure 2015 (clark)

[BZJoe]

lineage-14.1-20210218-UNOFFICIAL-clark (Nougat bootloader)

New build up
Feb. 5, 2021 security patch

Nougat bootloader only

Md5: f920871e22e23fa24ffe8135cc37e7d2

Always a good idea to do a backup when dirty flashing.

Thanks again to the Lineage team for the updates.

Excellent. Just dirty flashed unto my Clark to update to this version and all seems to be working fine. Will report if anything comes up but so far so good. Thanks Wheels!

 

[Nickolime]

Just installed the lineage-14.1-20210218-UNOFFICIAL-clark (Nougat bootloader) I have to say thanks for keeping this phone going. It's my daily for 5 years now. I had to use stock because I'm on Verizon, and I could never get the APN to load correctly for MMS. I came across the fix, and wanted to post it here too for anyone that might have the issue.

Connect the phone for ADB debugging. Then open ADB shell and use the command:
am start -a android.intent.action.INSERT content://telephony/carriers --ei simId -1

It won't let you edit the current one or list, but you can add a new one now, and use it. Worked great for me, and I'm up to date on security. Thanks again!

lineage-14.1-20210218-UNOFFICIAL-clark (Nougat bootloader)

New build up
Feb. 5, 2021 security patch

Nougat bootloader only

Md5: f920871e22e23fa24ffe8135cc37e7d2

Always a good idea to do a backup when dirty flashing.

Thanks again to the Lineage team for the updates.

 

[kb8no]

@Wheels564 I have been spending hours and hours trying to unravel things now that 17.1 and 18.1 have been shut off from ATT SIM's due to lack of VoLTE. I have managed to keep Verizon working on 18.1. I will soon be traveling and want to take advantage of both Veriaon and ATT with one phone on each.

Thank you for keeping 14.1 alive because it has VoLTE and it passes Safety Net. I was having a problem after flashing 14.1 Stock and then flashing this 14.1 LOS with boot looping. After lots of angst, I found that the latest Stock "23" Data is formatted to f2fs which causes the bootloop after flashing 14.1. If I re-format it on TWRP to EXT4 and re-flash, then it boots and runs as expected. Is this a known issue?

 

[Wheels564]

@Wheels564 I have been spending hours and hours trying to unravel things now that 17.1 and 18.1 have been shut off from ATT SIM's due to lack of VoLTE. I have managed to keep Verizon working on 18.1. I will soon be traveling and want to take advantage of both Veriaon and ATT with one phone on each.

Thank you for keeping 14.1 alive because it has VoLTE and it passes Safety Net. I was having a problem after flashing 14.1 Stock and then flashing this 14.1 LOS with boot looping. After lots of angst, I found that the latest Stock "23" Data is formatted to f2fs which causes the bootloop after flashing 14.1. If I re-format it on TWRP to EXT4 and re-flash, then it boots and runs as expected. Is this a known issue?

I have not had an issue coming from the latest stock Nougat to Hashbang's 14-1. However I don't use the latest TWRP because I believe it's geared towards Pie and Q. If he used any of the changes he made with his 16.0 build and used those to make official TWRP that could screw up 14.1. The TWRP I tested with was 3.3.1-0 from official download. Everything seemed to work fine with it.

 

[kb8no]

I have not had an issue coming from the latest stock Nougat to Hashbang's 14-1. However I don't use the latest TWRP because I believe it's geared towards Pie and Q. If he used any of the changes he made with his 16.0 build and used those to make official TWRP that could screw up 14.1. The TWRP I tested with was 3.3.1-0 from official download. Everything seemed to work fine with it.

Indeed, TWRP 3.3.1-0 works perfect to flash 14.1 for N bootloader coming from stock N which has data formatted with f2fs. Thank you.

TWRP from Chris works perfect for 17.1. But if you use it to flash 14.1 it cannot handle f2fs and will bootloop unless you reformat data to ext4 first.

Then if you are flashing 18.1 you need LOS recovery from Chris which works OK but has no ability to back up.

It was not easy to figure out all these nuances. Wouldn't it be nice to have a unifying TWRP that works for 18.1 and was backwards compatible?

 

[Wheels564]

Indeed, TWRP 3.3.1-0 works perfect to flash 14.1 for N bootloader coming from stock N which has data formatted with f2fs. Thank you.

TWRP from Chris works perfect for 17.1. But if you use it to flash 14.1 it cannot handle f2fs and will bootloop unless you reformat data to ext4 first.

Then if you are flashing 18.1 you need LOS recovery from Chris which works OK but has no ability to back up.

It was not easy to figure out all these nuances. Wouldn't it be nice to have a unifying TWRP that works for 18.1 and was backwards compatible?

Yes it would but the more Android changes the device trees change and backwards compatability gets harder to work out.

 

[RomanOnARiver]

It looks like the only way your gonna get google camera is open gapps stock version and higher. Google no longer supports anything below Oreo. There's no way to not overwrite Lineage camera unless you know how to change the install script.

I see. So if I do want to Flash the last Google Camera version from the Gapps, is it just the one apk file or do I need others? I'm seeing a cameragoogle, cameragoogle-comon, cameragoogle-legacy, cameragoogle-legacy-common. The common folders have like Jar and XML files as opposed to an apk.

 

[ashwin.terminator]

Would you by chance be willing to flash 17.1 LOS on your XT1572 and make a logcat of boot for @chrmhoffmann so he can fix why his ROM will not recognize SIM?

Does this requirement still exist?

I've a spare XT1572 that I can use for this test (I can still come back to 14.1, yes?)

 

[Wheels564]

Does this requirement still exist?

I've a spare XT1572 that I can use for this test (I can still come back to 14.1, yes?)

He's no longer developing 17.1 but I'm sure he would like to see a logcat of 18.1 with the dual sim variant. And yes you can go back to 14.1 but I believe you will have to flash back to stock Nougat again and use the TWRP I listed a few posts back to kb8no with Nougat bootloader.

 

[Wheels564]

lineage-14.1-20210410-UNOFFICIAL-clark (mm bootloader)

New build up
Apr. 5, 2021 security patch

mm bootloader only

Md5: 3fd354cf6af4d7828c35f4275fba6ea9

Always a good idea to do a backup when dirty flashing.

Thanks again to the Lineage team for the updates.

 

[Wheels564]

lineage-14.1-20210410-UNOFFICIAL-clark (Nougat bootloader)

New build up
Apr. 5, 2021 security patch

Nougat bootloader only

Md5: b46ae03b20c368330ffbcf6b306a631b

Always a good idea to do a backup when dirty flashing.

Thanks again to the Lineage team for the updates.

 

[kb8no]

@Wheels564 I flashed back to stock. Then I installed TWRP 3.3.1-0 and clean flashed this nougat ROM. It starts up into the Goggle login but hangs at Google Assistant and can't get past it. Thoughts?

Addendum. I think my motherboard is borked.

 

[Wheels564]

@Wheels564 I flashed back to stock. Then I installed TWRP 3.3.1-0 and clean flashed this nougat ROM. It starts up into the Goggle login but hangs at Google Assistant and can't get past it. Thoughts?

Addendum. I think my motherboard is borked.

Did you try a clean flash without google to see if it boots properly? Sometimes you just get a bad build of gapps. Maybe try formatting each partition in TWRP instead of just wiping. If you flash stock again and everything works ok then I would have to think trying an older gapps.

Edit: Just don't format EFS partition unless you have a backup.

 

[kb8no]

@Wheels564
Wipe - not
partition formatting - not
new 14.1 build - not
Gapps version - not
SIM card - not
Motherboard - not

I never suspected but you were right. The Gapps release was the problem. Not flashing Gapps allowed the LOS login and start the ROM. I arbitrarily grabbed 1/14 release from OpenGapps of my favorite mini version and it worked fine. The Google login is not playing well with the LOS login. It seems to be a regression bug in Gapps that generated the problem of the interface between the two.

Marginally related, We often need to do a clean flash back to stock. If you make a backup of a cleanly flashed stock, does restoring the backup work as well as a clean flash from scratch?

 

[Wheels564]

@Wheels564
Wipe - not
partition formatting - not
new 14.1 build - not
Gapps version - not
SIM card - not
Motherboard - not

I never suspected but you were right. The Gapps release was the problem. Not flashing Gapps allowed the LOS login and start the ROM. I arbitrarily grabbed 1/14 release from OpenGapps of my favorite mini version and it worked fine. The Google login is not playing well with the LOS login. It seems to be a regression bug in Gapps that generated the problem of the interface between the two.

Marginally related, We often need to do a clean flash back to stock. If you make a backup of a cleanly flashed stock, does restoring the backup work as well as a clean flash from scratch?

I've never had an issue restoring a backup and I always do backup when dirty flashing updates. I rarely do a clean install unless there's a change like the one after the last official release of 14.1. I clear dalvik and cache once a month when I dirty flash my updates. I haven't run my N bootloader roms LOS14.1 and Crdroid rom with a sim for a long time to see how reliability is compared to MM.

 

[virginwidow]

REALLY grateful to see active work on 14.1 (for any device)

Only Question - before I drop any more $$ tryin' to replace my Blackberry Passport (for that diabolical VoLTE)

(Q) Haven't found (yet) any comments how's the Camera?

Rly sorry, the "search" thingy didnt work that well before they broke XDA... Any input how to get the most out of the camera please?

THANKS in advance
VW

 

[kb8no]

@Wheels564 I did a clean flash of 7.1 today using today's latest version of OpenGapps and it installed just fine without hanging at Google Assistant. It must have been a short lived regression or else a corrupted download before. Everything OK now. On another topic, this is the only LOS ROM for this phone that works on VoLTE and thus has not been been banned by Tmo (I think) and ATT (for sure) so I need this ROM for my ATT SIM. Verizon still works on LOS 18.1 but I don't know how long that will last.

 

[Wheels564]

@Wheels564 I did a clean flash of 7.1 today using today's latest version of OpenGapps and it installed just fine without hanging at Google Assistant. It must have been a short lived regression or else a corrupted download before. Everything OK now. On another topic, this is the only LOS ROM for this phone that works on VoLTE and thus has not been been banned by Tmo (I think) and ATT (for sure) so I need this ROM for my ATT SIM. Verizon still works on LOS 18.1 but I don't know how long that will last.

VOlte is why I'm sticking on 7.1 for now. However if you want you can try CRDroid I made for N bootloader. It's much more customizable and I'll be switching to it soon for my daily driver. It's pre rooted so you will have to use Lineage's root uninstaller zip then install magisk if you want to pass safety net.

 

[virginwidow]

VOlte is why I'm sticking on 7.1 for now.

Where's the proper place to get assistance when installing twrp (3.1) fails after unlocking bootloader? (Which worked perfectly via Moto)

I've got a nasty "BSOD" nag screen, phone vibrates - and can't get to twrp at all, much less load a ROM... How do I get around this

please?

 

[Wheels564]

Where's the proper place to get assistance when installing twrp (3.1) fails after unlocking bootloader? (Which worked perfectly via Moto)

I've got a nasty "BSOD" nag screen, phone vibrates - and can't get to twrp at all, much less load a ROM... How do I get around this please?

The BSOD is really just a nag telling you the the bootloader is unlocked.

From the bootloader flash "fastboot flash logo logo.bin". Here is the logo for Nougat bootloader.

Also you do not want to use the latest TWRP. That version is written for Pie roms and you will have an issue with F2FS. See post 1823 from Kb8no. You want to use TWRP 3.3.1-0 available from official TWRP website. When you flash recovery from the bootloader go directly into recovery from the bootloader with the buttons DO NOT reboot the phone as it will overwrite the recovery you just installed. Once your into recovery it will be saved. Make sure to do a backup in recovery then flash the rom by the instructions in the first post.