[ROM][10.0][TREBLE] LineageOS 17.1 [UNOFFICIAL] [microG version also available]

Search This thread

EmaMaker

Member
Nov 21, 2016
36
25
1614372747125.png


LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.

Code:
#include <std_disclaimer.h>

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

Known issues:
  • You tell me

Moto Mods:
  • Moto Mods Hasselblad Camera are unknown to work.
  • All the other Moto Mods work

Instructions:
Always have a backup of the EFS partition made with TWRP stored somewhere, as you may lose IMEI. Restore it if you get 0 as IMEI when booted into the ROM
You will need Pie Firmware to use this ROM, here's an automated script to install it: https://www.androidfilehost.com/?fid=17248734326145714283
  • Download Official TWRP from twrp.me
  • Flash the TWRP via fastboot
  • Enter TWRP, go to wipe menu and Wipe Dalvik, Cache, Data, System and Internal Storage.
  • In TWRP Wipe Menu, do Format Data, then reboot into recovery
  • Flash the latest build
  • Flash eventual GApps and Magisk
  • Reboot

Downloads:
  • Latest Unofficial build: AFH
  • Latest Unofficial build with microG: AFH

Notes
TWRP

If the touchscreen doesn't work when rebooting into recovery, press the power button twice to turn off and on the screen. The touchscreen will now work just fine.

GSIs
This LineageOS build ships with Project Treble compatibility, meaning you can flash a GSI as System Image from TWRP. Please don't report GSI bugs here, report them instead to the GSI's maker. A Format Data from TWRP is required after flashing a GSI in order to avoid problems.
Use Arm64 AB GSIs.

Wanna help?
If you find a problem or a bug, please share a logcat with us, alongside an explanation of the problem and steps to reproduce. We won't accept bug reporting without a logcat. Collect logcat with:
Code:
adb logcat -b all > logcat.txt

You can also join our Telegram Channels:
Global: https://t.me/z2play
Custom ROMs: https://t.me/Z2PlayGSI
There's a guide made by a user to install the ROM, written in both Portuguese and English, here it is: https://telegra.ph/Como-instalar-LOs-160-How-to-install-LOs-160-08-04

Thanks
Many thanks to @marcost22 for the pair-working we are doing, although this time he did most of the work

Sources
Device tree
Vendor tree
Kernel

XDA:DevDB Information
LineageOS 17.1, ROM for the Moto Z2 Play

Contributors

EmaMaker, marcost22, rahulsnair, @erfanoabdi @vache @jeferson1979
ROM OS Version: 10.x
ROM Kernel: Linux 3.x
ROM Firmware Required: ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC

Version Information
Status:
Stable
Current Stable Version: 17.1
Stable Release Date: 2021-02-24
 
Last edited:

lungan

Member
Oct 8, 2020
10
0
I have been running on LOS 15.1 earlier, which has been working fine. I decided to try to update my Z2 play to this rom.

It installs fine, but when booting the first time it boots forever. I have been waiting 30 min but without success. I restarted, and waited 15 min again, but still without success.

I decided to give lineage-18.1-20210110-UNOFFICIAL-albus a shot, and it also installed fine. It also booted fine and setup ran without errors. However, on that ROM the sim-card is not detected.

So I guess I am heading back to 15.1 which is the only one that has been working, although a bit old..
 

lungan

Member
Oct 8, 2020
10
0
Did you flashed stock Pie before install? All these android 10 roms are not compatible with Oreo firmware.
I thought I did it, using the script (autoinstall) in the post. However I got some errors, and then I did it manually. Somehow it started to work then. I will write a longer post later on and tell more about my experience.

So far working very well! How nice to be on Android 10 instead of 8... Thanks!
 

Zennoe

Member
Jan 29, 2017
13
5
LG Velvet
Hello. I tried out your ROM. Since the script only works on Windows, I manually flashed fsg.mbn NON-HLOS.bin adspso.bin and logo.bin prior to trying to boot it. And my WiFi is broken. I did not install a SIM-Card yet.

Here is a log excerpt from when trying to connect to public WiFi:

02-24 18:32:48.093 8186 8186 D WifiSettings: onAccessPointChanged (singular) callback initiated
02-24 18:32:48.507 2575 2575 V KeyguardUpdateMonitor: onSubscriptionInfoChanged()
02-24 18:32:49.997 1195 6806 D WificondControl: Scan result ready event
02-24 18:32:50.033 8186 8186 D WifiSettings: onAccessPointChanged (singular) callback initiated
02-24 18:32:50.035 8186 8186 I sysui_multi_action: [757,804,799,settings_wifi_speed_labels,801,0,802,1]
02-24 18:32:50.093 8186 8186 I chatty : uid=1000(system) com.android.settings identical 20 lines
02-24 18:32:50.093 8186 8186 D WifiSettings: onAccessPointChanged (singular) callback initiated
02-24 18:32:50.097 8186 8186 D WifiSettings: onAccessPointsChanged (WifiTracker) callback initiated
02-24 18:32:50.094 8186 8186 I chatty : uid=1000(system) com.android.settings identical 2 lines
02-24 18:32:50.129 8186 8186 I sysui_multi_action: [757,804,799,settings_wifi_speed_labels,801,0,802,1]
02-24 18:32:50.312 8186 8186 I sysui_multi_action: [757,135,758,4,759,1]
02-24 18:32:50.314 1195 6806 I WifiService: getWifiServiceMessenger uid=1000
02-24 18:32:50.316 1195 2515 D WifiService: AsyncChannelExternalClientHandler.handleMessage ignoring msg={ when=0 what=69632 [email protected] target=com.android.server.wifi.WifiServiceImpl$AsyncChannelExternalClientHandler }
02-24 18:32:50.317 1195 2515 D WifiService: CONNECT nid=-1 config=* ID: -1 SSID: "Vodafone Homespot" PROVIDER-NAME: null BSSID: null FQDN: null PRIO: 0 HIDDEN: false PMF: false
02-24 18:32:50.317 1195 2515 D WifiService: NetworkSelectionStatus NETWORK_SELECTION_ENABLED
02-24 18:32:50.317 1195 2515 D WifiService: hasEverConnected: false
02-24 18:32:50.317 1195 2515 D WifiService: trusted
02-24 18:32:50.317 1195 2515 D WifiService: macRandomizationSetting: 1
02-24 18:32:50.317 1195 2515 D WifiService: mRandomizedMacAddress: 02:00:00:00:00:00
02-24 18:32:50.317 1195 2515 D WifiService: KeyMgmt: NONE Protocols:
02-24 18:32:50.317 1195 2515 D WifiService: AuthAlgorithms:
02-24 18:32:50.317 1195 2515 D WifiService: PairwiseCiphers:
02-24 18:32:50.317 1195 2515 D WifiService: GroupCiphers:
02-24 18:32:50.317 1195 2515 D WifiService: GroupMgmtCiphers:
02-24 18:32:50.317 1195 2515 D WifiService: SuiteBCiphers:
02-24 18:32:50.317 1195 2515 D WifiService: PSK/SAE:
02-24 18:32:50.317 1195 2515 D WifiService: Enterprise config:
02-24 18:32:50.317 1195 2515 D WifiService: IP config:
02-24 18:32:50.317 1195 2515 D WifiService: IP assignment: UNASSIGNED
02-24 18:32:50.317 1195 2515 D WifiService: Proxy settings: UNASSIGNED
02-24 18:32:50.317 1195 2515 D WifiService: cuid=-1 luid=-1 lcuid=0 userApproved=USER_UNSPECIFIED noInternetAccessExpected=false
02-24 18:32:50.317 1195 2515 D WifiService: recentFailure: Association Rejection code: 0
02-24 18:32:50.317 1195 2515 D WifiService: uid=1000 name=android.uid.system:1000
02-24 18:32:50.317 1195 2516 E WifiConfigManager: Cannot add/update network before store is read!
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: CONNECT_NETWORK adding/updating config=* ID: -1 SSID: "Vodafone Homespot" PROVIDER-NAME: null BSSID: null FQDN: null PRIO: 0 HIDDEN: false PMF: false
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: NetworkSelectionStatus NETWORK_SELECTION_ENABLED
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: hasEverConnected: false
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: trusted
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: macRandomizationSetting: 1
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: mRandomizedMacAddress: 02:00:00:00:00:00
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: KeyMgmt: NONE Protocols:
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: AuthAlgorithms:
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: PairwiseCiphers:
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: GroupCiphers:
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: GroupMgmtCiphers:
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: SuiteBCiphers:
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: PSK/SAE:
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: Enterprise config:
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: IP config:
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: IP assignment: UNASSIGNED
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: Proxy settings: UNASSIGNED
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: cuid=-1 luid=-1 lcuid=0 userApproved=USER_UNSPECIFIED noInternetAccessExpected=false
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: recentFailure: Association Rejection code: 0
02-24 18:32:50.318 1195 2516 E WifiClientModeImpl: failed
02-24 18:32:50.400 8186 8186 I sysui_multi_action: [757,804,799,settings_wifi_speed_labels,801,0,802,1]

And other WiFi related looking stuff from the boot phase
04-13 23:06:21.927 0 0 I : [ 43.688519,2] 'opened /dev/adsprpc-smd c 228 0'
04-13 23:06:21.935 0 0 E : [ 43.699248,7] wcnss_wlan invalid size to write 5220
04-13 23:06:21.935 0 0 I : [ 43.699609,7] pil-q6v5-mss 4080000.qcom,mss: modem: Brought out of reset
04-13 23:06:21.942 0 0 E : [ 43.700544,3] wcnss_wlan invalid size to write 6148
04-13 23:06:21.942 0 0 E : [ 43.705924,7] scm_call failed: func id 0x72000206, ret: -1, syscall returns: 0x0, 0x0, 0x0


04-13 23:06:24.612 0 0 I [ 46.374504,2] ueventd: firmware: loading 'wlan/prima/WCNSS_qcom_wlan_nv.bin' for '/devices/soc/a000000.qcom,wcnss-wlan/firmware/wlan!prima!WCNSS_qcom_wlan_nv.bin'
04-13 23:06:24.625 0 0 I [ 46.387030,7] ueventd: loading /devices/soc/a000000.qcom,wcnss-wlan/firmware/wlan!prima!WCNSS_qcom_wlan_nv.bin took 12ms
04-13 23:06:24.625 0 0 I [ 46.387040,0] wcnss: NV bin size: 31719, total_fragments: 11
04-13 23:06:24.625 0 0 E [ 46.387075,0] wcnss: no space available for smd frame
04-13 23:06:24.647 0 0 E [ 46.410101,0] wcnss: no space available for smd frame


02-24 18:25:04.931 0 0 W [ 123.652964,7] wlan: module is from the staging directory, the quality is unknown, you have been warned.
02-24 18:25:04.947 0 0 I [ 123.666688,4] wlan: loading driver v3.0.11.85.9
02-24 18:25:04.955 494 2556 D vold : Remounting 10034 as mode default
02-24 18:25:04.961 0 0 I [ 123.680556,4] ueventd: firmware: loading 'wlan/prima/WCNSS_qcom_cfg.ini' for '/devices/soc/a000000.qcom,wcnss-wlan/firmware/wlan!prima!WCNSS_qcom_cfg.ini'
02-24 18:25:04.961 0 0 I [ 123.681726,4] ueventd: loading /devices/soc/a000000.qcom,wcnss-wlan/firmware/wlan!prima!WCNSS_qcom_cfg.ini took 1ms
02-24 18:25:04.961 0 0 E [ 123.682858,4] wcnss_get_wlan_nv_name: No NV name
02-24 18:25:04.965 494 2556 D vold : Remounting 10017 as mode full
02-24 18:25:04.974 0 0 I [ 123.695632,4] ueventd: firmware: loading 'wlan/prima/WCNSS_qcom_wlan_nv.bin' for '/devices/soc/a000000.qcom,wcnss-wlan/firmware/wlan!prima!WCNSS_qcom_wlan_nv.bin'
02-24 18:25:04.974 0 0 I [ 123.695984,4] ueventd: loading /devices/soc/a000000.qcom,wcnss-wlan/firmware/wlan!prima!WCNSS_qcom_wlan_nv.bin took 0ms
02-24 18:25:04.974 494 2556 D vold : Remounting 10017 as mode full
02-24 18:25:04.993 494 2556 D vold : Remounting 10151 as mode default
02-24 18:25:05.009 494 2556 D vold : Remounting 10151 as mode default
02-24 18:25:05.017 494 2556 D vold : Remounting 10293 as mode default
02-24 18:25:05.025 494 2556 D vold : Remounting 10293 as mode default
--------- beginning of events
02-24 18:25:05.062 1195 1195 I commit_sys_config_file: [package-session,1]
02-24 18:25:05.077 1195 1195 I boot_progress_ams_ready: 123799
02-24 18:25:05.077 1195 1231 I dvm_lock_sample: [system_server,1,android.display,5,ActivityManagerService.java,6488,java.lang.String com.android.server.am.ActivityManagerService.checkContentProviderAccess(java.lang.String, int),-,8951,void com.android.server.am.ActivityManagerService.systemReady(java.lang.Runnable, android.util.TimingsTraceLog),1]
02-24 18:25:05.080 1195 1195 I configuration_changed: 1073742084
02-24 18:25:05.094 0 0 I [ 123.814558,7] wlan: WCNSS WLAN version 1.5.1.2
02-24 18:25:05.094 0 0 I [ 123.814571,7] wlan: WCNSS software version CNSS-PR-4-0-3-214-202983-1
02-24 18:25:05.094 0 0 I [ 123.814576,7] wlan: WCNSS hardware version WCN v2.0 RadioPhy vIris_TSMC_4.0 with 48MHz XO
02-24 18:25:05.094 0 0 I [ 123.816051,5] hdd_get_feature_caps_cb: Firmware feature capabilities received
02-24 18:25:05.094 0 0 I : [ 123.816067,7] DefaultCountry is 00
02-24 18:25:05.100 684 684 I [email protected]: Wifi HAL started
02-24 18:25:05.101 0 0 I [ 123.816452,7] country: 00 and initiator 0
02-24 18:25:05.101 0 0 I [ 123.820480,7] wlan_logging_sock_activate_svc: Initalizing FEConsoleLog = 1 NumBuff = 32
02-24 18:25:05.101 0 0 I [ 123.820548,7] wlan_logging_sock_activate_svc: Initalizing Pkt stats pkt_stats_buff = 16
02-24 18:25:05.101 0 0 I [ 123.820828,7] wlan: driver loaded
02-24 18:25:05.107 0 0 I [ 123.827542,7] init: Received control message 'interface_start' for '[email protected]::ISupplicant/default' from pid: 490 (/system/bin/hwservicemanager)
02-24 18:25:05.107 0 0 I [ 123.828199,7] init: starting service 'wpa_supplicant'...
02-24 18:25:05.109 0 0 I [ 123.830755,5] init: Created socket '/dev/socket/vendor_wpa_wlan0', mode 660, user 1010, group 1010
 

meelten

Senior Member
Nov 21, 2018
71
18
Try flashing complete rom, not just modem. You'll find link in Resurrection Remix thread.
Boot into stock once to ensure all works.
 
Last edited:

Zennoe

Member
Jan 29, 2017
13
5
LG Velvet
Oh and btw, the settings app closes itself whenever I try to access the system section in settings. Info shows that I have two IMEIs, a WiFi MAC, but no Bluetooth MAC. And turning on bluetooth crashes settings.

Update: I reflashed back to Stock 8 and then to Stock 9 again. Now I finally got somewhere and WiFi works again. I will test mobile once I got my new SIM ;)
 
Last edited:

lungan

Member
Oct 8, 2020
10
0
Here is my story:

I have previously successfully installed
  • lineage-15.1-20200211-UNOFFICIAL-albus.zip
  • MindTheGapps-8.1.0-arm64-20180808_153856.zip
  • Magisk-v20.4.zip
using TWRP 3.2.2-r23. On that version, but middle (gesture/fingerprint) button on the phone didn't work, also there were no virtual "on screen" buttons. However, this was solved using buildprop and adding a line of code there. Thus this setup has been working very very fine, no problems at all (except the navigation/fingerprint button then).

However, with Android 8 (LOS 15.1) being quite old, I thought that at least from a security point of view it might be a good idea to not stay with Android 8 (maybe someone with knowledge of the security can comment on this?). There are of course other reasons as well.

I have been waiting for a new version to work. So when I saw this post I thought I'd give it a shot.

I installed the lineage-17.1-20210224-UNOFFICIAL-albus.zip using the same TWRP 3.2.2-r23 version without success. The installation went fine, but the first boot kept on forever (> 30 min). Using the script to flash the firmware in fastboot, I thought it was OK, but what I did later on was to manually take the commands from the script and just run the commands manually. I have no idea why the automated script didn't work, but when I did enter the commands manually (I just copy pasted them, Ubuntu 20.04) it worked.

So currently I have installed
  • lineage-17.1-20210224-UNOFFICIAL-albus.zip
  • open_gapps-arm64-10.0-stock-20210304.zip
  • Magisk-v20.4.zip
using the same old version of TWRP 3.2.2-r23. This has worked flawless on my phone. And to my big surprise, even the gesture/fingerprint button is working, which I really do like since I save some space on the screen when I don't need to have the virtual navigation buttons.

I use the powerpack (the part why I like the phone is the long battery time). And the Moto powerpack seems to be working very well as well.

Furthermore, I am located in Europe and thus run a Europe-compatible phone.

Edit: I have one question. I see that now when I use the fingerprint sensor for unlocking, it seems that the phone is reacting on the fingerprint sensor while I have the phone in my pocket? There is a feature "Prevent accidental wake-up", that I have activated, but I still have a sense of the phone being woken up. I don't have any good information here, but maybe someone have an answer if there is a possibility for me to deactivate the fingerprint sensor in a way that I need to press the power button first to activate the phone, and then having the fingerprint sensor active?

I would like to thank EmaMaker and all contributors for this.
 
Last edited:

Arcline

Senior Member
Sep 11, 2016
174
66
Gonna try it out now, seems promising. Curious though, what's the reason this isn't official? Everything works right?

Update: I've tried it, it's awsome. I only noticed 2 minor things that could be polished: the charging led thing (z2 doesn't have one) and the Moto TV seems to do nothing.
Otherwise flawless, just what this phone needed.

Update 2: I found an issue, after encrypting storage the phone bootloops. Reflashed the stock rom to use the stock encryption too, then flashed Los, but it didn't solve the problem. Also, didn't install magisk and the issue still occured.
 
Last edited:

EmaMaker

Member
Nov 21, 2016
36
25
Here is my story:

I have previously successfully installed
  • lineage-15.1-20200211-UNOFFICIAL-albus.zip
  • MindTheGapps-8.1.0-arm64-20180808_153856.zip
  • Magisk-v20.4.zip
using TWRP 3.2.2-r23. On that version, but middle (gesture/fingerprint) button on the phone didn't work, also there were no virtual "on screen" buttons. However, this was solved using buildprop and adding a line of code there. Thus this setup has been working very very fine, no problems at all (except the navigation/fingerprint button then).

However, with Android 8 (LOS 15.1) being quite old, I thought that at least from a security point of view it might be a good idea to not stay with Android 8 (maybe someone with knowledge of the security can comment on this?). There are of course other reasons as well.

I have been waiting for a new version to work. So when I saw this post I thought I'd give it a shot.

I installed the lineage-17.1-20210224-UNOFFICIAL-albus.zip using the same TWRP 3.2.2-r23 version without success. The installation went fine, but the first boot kept on forever (> 30 min). Using the script to flash the firmware in fastboot, I thought it was OK, but what I did later on was to manually take the commands from the script and just run the commands manually. I have no idea why the automated script didn't work, but when I did enter the commands manually (I just copy pasted them, Ubuntu 20.04) it worked.

So currently I have installed
  • lineage-17.1-20210224-UNOFFICIAL-albus.zip
  • open_gapps-arm64-10.0-stock-20210304.zip
  • Magisk-v20.4.zip
using the same old version of TWRP 3.2.2-r23. This has worked flawless on my phone. And to my big surprise, even the gesture/fingerprint button is working, which I really do like since I save some space on the screen when I don't need to have the virtual navigation buttons.

I use the powerpack (the part why I like the phone is the long battery time). And the Moto powerpack seems to be working very well as well.

Furthermore, I am located in Europe and thus run a Europe-compatible phone.

Edit: I have one question. I see that now when I use the fingerprint sensor for unlocking, it seems that the phone is reacting on the fingerprint sensor while I have the phone in my pocket? There is a feature "Prevent accidental wake-up", that I have activated, but I still have a sense of the phone being woken up. I don't have any good information here, but maybe someone have an answer if there is a possibility for me to deactivate the fingerprint sensor in a way that I need to press the power button first to activate the phone, and then having the fingerprint sensor active?

I would like to thank EmaMaker and all contributors for this.
Hi, thank you for sharing your experience! I myself live in europe so yes, this is a europe friendly rom and phone. The update I published today allows the mod battery level to be viewed as a notification, just like in other arrow and aicp roms. The rom also includes overlay to turn the on-screen navbar on and off from Settings>System>Buttons, so no need to modify build.prop. If you want another approach, on the Custom ROMS telegram group there's a twrp script to do the same thing, but I recommend using android settings
 

EmaMaker

Member
Nov 21, 2016
36
25
Gonna try it out now, seems promising. Curious though, what's the reason this isn't official? Everything works right?

Update: I've tried it, it's awsome. I only noticed 2 minor things that could be polished: the charging led thing (z2 doesn't have one) and the Moto TV seems to do nothing.
Otherwise flawless, just what this phone needed.

Update 2: I found an issue, after encrypting storage the phone bootloops. Reflashed the stock rom to use the stock encryption too, then flashed Los, but it didn't solve the problem. Also, didn't install magisk and the issue still occured.
Hi! It looks strange, last time I tried encryption it worked fine, maybe try with the just published update? The rom isn't official for quite a simple reason, and it is that I unfortunately lack time to follow all the things an official dev needs to do for los, maybe I will try official for other minor roms in the future, just for the sake of publishing an official rom. But I do not think an official los for albus will come from myself in the near future
 

lungan

Member
Oct 8, 2020
10
0
Changelog:

24/03/2021: Enabled battery mod level (show perfecentage of battery mod as notification, like Arrow and AICP). Reintroduce led notification light. Recompiled in a clean environment on a new machine: https://www.androidfilehost.com/?fid=2188818919693770548
24/02/2021: First release: https://www.androidfilehost.com/?fid=17248734326145743552
Stupid question maybe, but how do I update to this? Do I need to make a clean install (like when I installed the previous build with twrp) or is it possible to "just update" like in the official releases?
 

meelten

Senior Member
Nov 21, 2018
71
18
Stupid question maybe, but how do I update to this? Do I need to make a clean install (like when I installed the previous build with twrp) or is it possible to "just update" like in the official releases?
Just install through TWRP on top of old one. No clean install required when updating the same ROM. Just wipe cache and dalvik before.
 

lungan

Member
Oct 8, 2020
10
0
Just install through TWRP on top of old one. No clean install required when updating the same ROM. Just wipe cache and dalvik before.
Thank you for the answer. So I just wipe cache and dalvik. Then I install the rom, without anything more. What about MindTheGapps and Magisk etc? No need to reinstall them?

1) Wipe cache and Dalvik in TWRP
2) Install the new build in TWRP
3) Reboot
4) The phone will be like "before", but with the updated build of the ROM? Thus no need to (re)-install MindTheGapps, Magisk etc?
 

meelten

Senior Member
Nov 21, 2018
71
18
Thank you for the answer. So I just wipe cache and dalvik. Then I install the rom, without anything more. What about MindTheGapps and Magisk etc? No need to reinstall them?

1) Wipe cache and Dalvik in TWRP
2) Install the new build in TWRP
3) Reboot
4) The phone will be like "before", but with the updated build of the ROM? Thus no need to (re)-install MindTheGapps, Magisk etc?
Magisk have script that should automatically rebuild it after flashing ROM. If it won't work you'd need install it manually.
Reinstalling gapps is not needed, all applications and user data is intact.
 

Arcline

Senior Member
Sep 11, 2016
174
66
Hi! It looks strange, last time I tried encryption it worked fine, maybe try with the just published update? The rom isn't official for quite a simple reason, and it is that I unfortunately lack time to follow all the things an official dev needs to do for los, maybe I will try official for other minor roms in the future, just for the sake of publishing an official rom. But I do not think an official los for albus will come from myself in the near future
I see, I'll try it out now and will let you know if it works. I got a small request if I may, since this is gonna stay unofficial, could you add signature spoofing for Micro G?
 

ElMiamiMan

New member
Apr 4, 2021
3
0
hi, I managed to install this rom and works perfectly except for the mobile data.

Looks like the phone reads the SIM card and I can unlock it and everything but it doesn't seem to get any signal. I get a "No service" text after unlocking the SIM and I have no idea how to make it work. Also made sure to flash the Android Pie modem.

does anyone here have any idea of what could it be? sorry if I'm missing any detail, I'm pretty much lost.

I'll try to attach some clean logs later if that gives any help.

edit: ok after some more investigation i've realised that i have the chinese model (XT1710-08) and i'm not supposed to flash the modem, since i'm coming from the nougat ZUI rom, nor erase the modemst parts, so my fault on that. In any case now i'm concerned about "android 10 not being compatible with oreo firmware", which someone above pointed out. Is there any way to get around this other than maybe sticking with LineageOS 16 or am I out of luck?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    1614372747125.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.

    Code:
    #include <std_disclaimer.h>
    
    /*
    * Your warranty is now void.
    *
    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at us for messing up your device, we will laugh at you.
    *
    */

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    Known issues:
    • You tell me

    Moto Mods:
    • Moto Mods Hasselblad Camera are unknown to work.
    • All the other Moto Mods work

    Instructions:
    Always have a backup of the EFS partition made with TWRP stored somewhere, as you may lose IMEI. Restore it if you get 0 as IMEI when booted into the ROM
    You will need Pie Firmware to use this ROM, here's an automated script to install it: https://www.androidfilehost.com/?fid=17248734326145714283
    • Download Official TWRP from twrp.me
    • Flash the TWRP via fastboot
    • Enter TWRP, go to wipe menu and Wipe Dalvik, Cache, Data, System and Internal Storage.
    • In TWRP Wipe Menu, do Format Data, then reboot into recovery
    • Flash the latest build
    • Flash eventual GApps and Magisk
    • Reboot

    Downloads:
    • Latest Unofficial build: AFH
    • Latest Unofficial build with microG: AFH

    Notes
    TWRP

    If the touchscreen doesn't work when rebooting into recovery, press the power button twice to turn off and on the screen. The touchscreen will now work just fine.

    GSIs
    This LineageOS build ships with Project Treble compatibility, meaning you can flash a GSI as System Image from TWRP. Please don't report GSI bugs here, report them instead to the GSI's maker. A Format Data from TWRP is required after flashing a GSI in order to avoid problems.
    Use Arm64 AB GSIs.

    Wanna help?
    If you find a problem or a bug, please share a logcat with us, alongside an explanation of the problem and steps to reproduce. We won't accept bug reporting without a logcat. Collect logcat with:
    Code:
    adb logcat -b all > logcat.txt

    You can also join our Telegram Channels:
    Global: https://t.me/z2play
    Custom ROMs: https://t.me/Z2PlayGSI
    There's a guide made by a user to install the ROM, written in both Portuguese and English, here it is: https://telegra.ph/Como-instalar-LOs-160-How-to-install-LOs-160-08-04

    Thanks
    Many thanks to @marcost22 for the pair-working we are doing, although this time he did most of the work

    Sources
    Device tree
    Vendor tree
    Kernel

    XDA:DevDB Information
    LineageOS 17.1, ROM for the Moto Z2 Play

    Contributors

    EmaMaker, marcost22, rahulsnair, @erfanoabdi @vache @jeferson1979
    ROM OS Version: 10.x
    ROM Kernel: Linux 3.x
    ROM Firmware Required: ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC

    Version Information
    Status:
    Stable
    Current Stable Version: 17.1
    Stable Release Date: 2021-02-24
    1
    Changelog:

    24/03/2021: Enabled battery mod level (show perfecentage of battery mod as notification, like Arrow and AICP). Reintroduce led notification light. Recompiled in a clean environment on a new machine: https://www.androidfilehost.com/?fid=2188818919693770548
    24/02/2021: First release: https://www.androidfilehost.com/?fid=17248734326145743552
    1
    Hello,

    Juste tries this rom, and it works pretty well, thank you !

    The installation process went fine, following author recommendations.

    I had to "adb sideload" the zip build, as spectified in https://wiki.lineageos.org/devices/albus/install

    (don't know if this is relevant to anybody, but since it was my first rom install, I strugled with that part, so I thought that others might take use that info :) )

    Two things don't work at the moment, but are not deal breaker for me :
    - the encryption doesn't work : infinite loop at boot time, as spectified by @Arcline : "after encrypting storage the phone bootloops" . Same happens to me.
    - the charging Led is somehow wrong : when charging it turns on not a led but what looks like a front flash, that is borthering for the eyes. Only during charging time though

    Other than that, the rom is neat, and I don't find any other subject of discussion

    Do you think you could go official ? This would be awesome. It would help people discovering and adopting a modern Android 10 based rom for their Moto Z2 play, and not trash their phone away, which is always a good thing for the planet ! I could help if you want, not in the coding part, but in the procedure.

    Thanks again !