yashsingh1/xdaforums huggingface dataset:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] AHMN48:
no, I didn't use any modules, I came from stock version (Android 9) to here

the new version has something annoying, one of them can't lock with fingerprint

stock Message, Phone, Calculator, Contacts are awful and can't disable, I don't want to root my phone
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Manuel Marta:
my device is shutting down and rebootin randomly using latest nightly it takes me to lineage recovery and says that android system cant start then it gives me the option to factory reset but keeps happening
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] bogante:
You can hide that apps from launcher settings

Do this steps it works for me:

1. Remove your Google account

2. Flash #stock-p with #commands-p

3. Return to fastboot mode

4. Boot to #twrp (fastboot boot twrp.img✓ NOT fastboot flash boot twrp.img×) and flash #copy-part

5. Make Backup of EFS, PERSIST, FSG, DSP in the MicroSD

6. Go to the bootloader, and make fastboot -w

1. Boot to #twrp (fastboot boot twrp.img✓ NOT fastboot flash boot twrp.img×) flash ROM and #twrp-zip

2. Reboot into recovery and flash #magisk and/or #gapps.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Vanphu_ht91:
CH play

I just flash this rom on my X1789-03 device but I can't install CH play on it. Can you help me?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Manuel Marta:
i don't know what you're meaning by #stock-p
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] bogante:
STOCK PIE (Android 9 stock) your official firmware.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Twin.Twiggs:
Same problem with him at previous post, but when i try to flash another rom, reboot disappear. (In Lineage, if i try to insert 2 sim it auto reboot to twrp, try to reboot again but it happened
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ph03n!x:
We need to make a logcat of the issue - if anyone has ADB debugging enabled and have authorised your computer, please do. I switched to stock for now, but will experiment it out sooner than later.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Manuel Marta:
I can't make a logcat of the reboot shutdown issue as this is the only phone i have and i need it because it's my daily driver so i went back to lineage 16

i guess i'm just going to wait until it gets more stable
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] mail.gearman:
Issue confirmed to be faced on 2 devices. 6 apr 2020 and 7 apr 2020 nightlies:

pico gapps,

after installing google pay, android requires to grant SMS permission to Google Play services, but SMS is not listed on permission list for Google Play Services.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Try going to the play store and installing google messages. Then try google pay. Make sure google messages is set as the default.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] mail.gearman:
No success, still the same.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
You might need google dialer as well. Might consider a fuller gapps package.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] kendallgreen:
No problems installing Lineage 17.1 and nano open-gapps over lineage 16.0 on TMO MotoZ2 force. updated from 0405 to 0406 with updater app.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
The lineage recovery sideload function is flashing just the rom without the installed gapps from the active slot to the other, right? So we can flash Q gapps after that.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Saulservin7:
How can I update without losing my data and applications?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Alpha 10:
facing same issue here

I'm facing same issue here
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] bogante:
step for upgrade to lineage 16 to 17.1?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ldmondini:
As written in the first post by the developer you can find instructions here: https://wiki.lineageos.org/devices/nash/upgrade

Here what I made using windows 10:

1) download latest Lineage zip and your favorite Gapps for android 10 zip and save them in a folder with ADB and FASTBOOT commands (if they are not already enabled in your PC)

2) take the phone, enable USB debugging in developer options and plug to the PC

3) start Windows powershell or command prompt in then previous folder where you placed the zips (shift+right mouse button)

4) Reboot official Lineage recovery

5) In the recovery select "Apply update" and then "Apply from ADB"

6) In the command prompt type "adb devices" and you should see the ID of your device, then "adb sideload lineage.zip" (inserting the name of your LineageOS package) and press enter

7) when flashing is finished reboot recovery and retap apply update and apply from ADB (thanks ph0en!x)

8) type "adb sideload gapps.zip" (inserting the name of your Gapps package)

9) restart and enjoy

You won't loose your data

At the moment with Lineage 17.1 I'm finding only some problems with magisk modules.:D
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] bogante:
I have problems with camera, don't focus at all.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
It's a known issue, soon as it's resolved I'm sure it will be posted.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ph03n!x:
PLEASE REBOOT TO RECOVERY between 6 and 7! Otherwise GApps will access the wrong slot (which probably has the old ROM), and might fail or be unpredictable...
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ldmondini:
Thanks, you are definitely right. I forgot it, what is important is to not boot lineage, but reboot in recovery. I'm correcting the post.

Sorry for the mistake:(

For camera issue I'm not a photographer but with gcam I have solved, I can't see focus issues.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
He is right. Gapps flashing is always possible in the active slot, so you have to reboot to revovery to come to the other one.

Any reteu user here? With sim inserted on slot 1 all is fine? People tells from bugs im androd framework. Any news?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ldmondini:
You are right, I made a mistake, I corrected the post, sorry:( My z2 is reteu
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
Do you use one sim card on slot 1 and no reboot issue? That should be normal. What happens, if you remove the sim? Then it can be that the phone reboots to revovery sometimes. Would be interesting, if you do have this issue, too.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ldmondini:
Yes I'm using only one sim card on slot 1 and I haven't had any reboot since the first install. I tried to remove the SIM on the fly with mobile on and no issues.:confused:

My z2 is a German unit, reteu 06 for stock firmware.

The only problems I'm finding with LOS17.1 are with the settings app after I have installed Magisk (I didn't have them with the first 25 March version): some menus doesn't work and force the app to close. I can't access to the app and notification menu and the battery utilization stats in the settings. I had some glitches with adobe profile, but none with the default one. I haven't found other problems, neither for camera focus with gcam (here a sample picture [https://ibb.co/rfHtW6g], I'm not a professional but it seems to me focused):fingers-crossed:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
German here, too. Ok, that sounds well. Then I should try it again very soon. Which baseband do you have in use? I have on both slots the latest retail reteu Pie firmware (-24 at the end, baseband .02.96R) Now with IMEI back.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ldmondini:
I'm coming from Los 16 and before I was using the stock firmware with the latest update -24.

I've never had problems with IMEI but I was looking to my baseband to tell you which one I have, and in the bootloader it says not found...:confused:

Everything is working right, but I think it's not normal that I can't see the baseband I'm the bootloader...someone has any idea?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
That's sadly normal on -24, even with oem-locked status. I have seen this by other, too. But should working all normal.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Saulservin7:
when I transmit the screen to a smartv the image if it is seen, but the audio is not heard, does anyone know how to fix it?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Manueldguez:
Does anyone know why device appears as uncertified device on the play store if anyone can explain it to me as I'm not able to install Netflix or any paying apps
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] sir_overthrow:
tethering works?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] angelwrath:
Device keep Rebooting

I did everything as per instructions.But device keep rebooting after starting within a minute.Sometimes it say data corrupt and you need to factory reset it.tried flashing Lineageos 16.1 too but same issue.Any idea why this is happening.I came to xda after 6-7 years just to pass time in this lockout :)

Flash it from Stock Pie.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
I had this in 17.1 on reteu, too. I'm back on 16 and all no reboot issue anymore. Very less people run into this issue. Do you have no or two sim cards inserted? With one sim (first one) it should work. Maybe you can test.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Just boot to recovery and factory reset it.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] angelwrath:
Did same still phone reboot after few seconds

If it didn't works then may be i ll restock it.Where i can find stock rom and how i can flash that?

---------- Post added at 12:58 PM ---------- Previous post was at 12:19 PM ----------

I think its something to do with baseband as in fastboot flash mode it says baseband not found and when i start phone both sim keep flashing keep on off while showing no network.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ph03n!x:
Was looking forward to the 12th April build as it has a long list of changes - but looks like it's not getting built? [MENTION=5848265]npjohnson[/MENTION] can you kindly check please?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] angelwrath:
ok i just check and you are right.I am on Lineage 16 right now and with one sim its not rebooting.Thanks at least i have something to use in this lockdown.Now any idea how can i make both sim work and why this happen?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
I have tries everything, too. But if nothing helps I wouldn't go back to stock rather to LOS 16, the predecessor of LOS 17.1. That has helped me. And again, baseband not found in bootloader is no problem (even on oem_locked its shown like this on -24 firmware). Here baseband and imei up in LOS 16, all working, no reboot issues.

I meant LOS 17.1 with the sim on slot 1 for reteu. On LOS 16 all should working.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] angelwrath:
Surprisingly now I tried with both sim and there isn't any issue.Earlier phone was rebooting.I didn't change anything.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] npjohnson:
https://download.lineageos.org/nash ?

It's been there all day....
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] phin586:
Ive just installed this over 16.0.

It seems all of my ringtones are now missing. When i attempt to select it is replaced by a number.. I went searching around but I cannot seem to find them....

Any suggestions? Vanilla 17.1 NO Gapps.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Twin.Twiggs:
Lineage 17.1, after flash GSI on android Q expect GoogleGSI and GenericGSI, camera not work. Nice. Focus on Gsi but cant fix camera.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] sai_vitu:
when gapps are flashed it goes into a loop

☹️
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ckristi:
Same here, latest LineageOS ( lineage-17.1-20200417-nightly-nash ) with OpenGapps (open_gapps-arm64-10.0-nano-20200418), the phone is randomly rebooting, getting into the recovery, saying a problem has occured, and offering two options:

* retry: leading to similar results (phone boots fine, then reboots at some point in time, not really deterministic)

* wipe data (reset to factory settings): also tried, leading again to same results

I have now reverted back to 16.0 and all looks OK again. Can't figure out what is causing this (can't blame it on GApps either, as I have not tried to install the phone without).
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Make sure that after you flash Los you reboot to bootloader, then back to recovery then flash gapps. I use open_gapps-arm64-10.0-pico-20200129 and have never had bootloop issues.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ckristi:
I did follow the instructions as described on the LineageOS upgrade page.

Also, i actually doesn't boot loop. It boots just fine, but after sometimes seconds, sometimes minutes the phone restarts (once it even worked for more than 1h, even got time to restore all my settings from a previous backup, only for the phone to restart some time later).
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
If you decide to go to 17.1 again I would suggest a clean install, not an upgrade. After you're all setup, flash the los recovery and use the built in updater app to upgrade. It might be your backups causing the problems, our phone and backups have never been bffs lol.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ckristi:
Just to clarify, it is not 'my backup'; it is the usual Google backup + restore from cloud... not even a real backup of all apps (just contacts+messages+some configs+re-installing the previously installed apps). So, whatever breaks it, must be either coming from GApps, or from the image itself. As, unfortunately, the phone is a daily driver, I can't test further right now.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ldmondini:
Hi to everyone, I haven't noticed in the first days of use, but I'm finding some problems with automatic display brightness: my sensor works, but it is very slow or seem disabled and I have to reboot the phone to let it work. The automatic boost to see the screen under directly sun light in live display doesn't work at all. Is it a know issue or maybe a clean install could solve my problem?

Thanks
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
It could be gapps, they've had some wonky runs here and there. The gapps I listed works fine for me, I haven't tried any others but I know there were some that caused problems. So when you get around to it, try a clean flash and use open_gapps-arm64-10.0-pico-20200129. You should be set.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
I had the same issue and now I'm on LOS 16. Very happy with it. reteu?

Why is 20200129 better than a newer version?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
I don't know that it is better, but I've used it every time I flashed Los17.1, even on the unofficial builds. I've never had any gapp issues, bootloops, etc. Newer doesn't always mean better. For a long time whenever you wanted to root oreo it was suggested to use magisk 16.0 because anything higher would cause problems. Once the initial root was done you could upgrade through the app, but the initial root needed to be 16.0. I simply suggested using a gapps package that I know works.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
It has worked everything. And that wasn't bootloops. The issues are suddenly rebooting to recovery (with option to reboot or factory reset and reboot). Nothing helped. That all while the usb charger is unplugged. With charger in LOS 17.1 is working completly normally all the time. Important, not everybody has this issues. Normally on reteu.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
I wasn't aware that it was a reteu device, but I have seen reports of reteu having problems, more specifically dual sim devices. I notice on lolinet that there are two firmwares available, one is SS (single sim) and the other is DS (dual sim). Is it possible that the wrong base was flashed? Maybe that could be the culprit. Another thing to consider is whether the copy-partitions zip was used to flash over the modems from the other slot. That zip was primarily made to ensure that there was no blank slot which can cause bricks, but also some users have reported better mobile signal when both slots have identical bases.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] fritzophrenic:
I, too, noticed this. Everything seemed fine immediately after updating from 16.0 to 17.1, I even went into Google Pay to check if all my cards were available for contactless payments, but one day later I am getting a popup from Google Pay:

I downloaded a safetynet checker app I've used before and the basicIntegrity check shows as passing, so if I understand correctly, it's not the unlocked bootloader causing the problem. But ctsProfileMatch is false so the overall status is red.

[MENTION=5848265]npjohnson[/MENTION] I remember something like this happening briefly on 16.0. You reverted something and it started passing SafetyNet again. Is there something similar that can be done in 17.1 or is whatever you reverted last time required for 17.1 for some reason? Or maybe we as users can fix by flashing updated firmware or something like that? I admit I did not check my firmware level while applying the update.

If it's just something official builds will always have going forward, is there something someone could patch out for personal unofficial builds if we want to go that route or does that have significant unintended effects?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] DrakeJones:
Use Gapps Pico

Hey All,

Just did a new clean flash with the Sprint variant with success using the latest Nightly & Recovery.

I can tell you for sure, you must use the Gapps Pico, you will get boot loop with Nano. Also I could not ADB sideload Gapps Pico right after installing the LOS image, it gave me an error that said not enough storage space which is very odd, however I was able to reboot back into recovery and ADB sideload Gapps Pico with success. Just wanted to share my experience.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] fritzophrenic:
I'm on Sprint and successfully installed with nano.

I get random camera crashes for a little while at startup (not while actually using the camera) but no bootloops.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
The reason for the storage error is because you needed to boot to the new active slot that Los was installed to. That's why it worked when you booted back to recovery, because you were on the new slot. Just for future reference.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] finrod2007:
have u solved this problem now? for my phone its the same.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ph03n!x:
Do you have a SIM card in the phone?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] abense:
Subscribing. Was contemplating upgrading from LineageOS 16, but going to hold back until the camera issues are sorted out.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] finrod2007:
is this essential to not having the bootloop then?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ph03n!x:
Yes. Please read this post of mine. The thread itself is just 10 pages, would be good to glance through to know what others have experienced.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] mail.gearman:
Please confirm if camera focus issue still faced in 25 Apr nightly build.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] BM2KTom:
I have a weird issue that I cannot figure out, with the last four nightlies starting around 4/20 my Amazon blink camera app can no longer access mobile data, wifi works perfectly fine, it's like there is a blocked hosts file when using LTE for the specific blink server. On the older builds it worked perfectly fine and nothing has changed on my phone or the app other than the build I'm on. I've also now discovered venmo doesn't work either on mobile data. Went back to the latest lineage 16 and all apps work as they should on mobile data, I think ill stay on 16 as my daily driver until the data and camera bugs get worked out.

---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------

Also I am on the 4/25 build and close up camera focus still seems to be an issue.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] fritzophrenic:
https://review.lineageos.org/c/LineageOS/android_device_motorola_nash/+/273800/

Well, darn. I guess I won't be trying to find a camera mod to order, then. :(

But I suppose, not currently having a camera mod, since the same commit also says it fixes the focus issue, that I'll be updating today. :)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ph03n!x:
Cam mod never really worked in non-stock. And the focus fix is not there yet, some of us can't get it focusing yet, but it will get fixed soon...
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ckristi:
So, someone was asking if my phone is the RETEU version; I can't seem to find this info in the menu anymore, but I believe it is RETEU (unlocked model bought in EU).

I have just tried the update process again, with the SIM card inside and using the pico OpenGapps.

Upgrade went smoothly, and I have disconnected the phone from the charger ~20m ago... no forced reboot yet. Crossing fingers.

As for the camera focus, I confirm it has issues (with the latest lineage-17.1-20200425 nightly), but no biggie if it's gonna get fixed soon.

Ah, another interesting thing about the camera was that it was crashing while taking pictures. Fixed by cleaning the cache and storage for the application; however, during re-configuration, I noticed I cannot set the storage on the SD card anymore...)

Later later edit: all good, no unexpected reboots
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] mekkelrichards:
Anyone have luck getting their camera to focus on the latest build?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] sai_vitu:
What happened to the nightly? No new construction in a while

:c
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Manuel Marta:
they got hacked!
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] TheSchlaf:
Still an issue occasionally.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] mekkelrichards:
The developers?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] npjohnson:
lineageOS's infrastructure.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 12die4:
Hi there!

I have flashed a brand-new Moto Z2 Force with Lineage OS 17.1 and nano package of open gapps.

I am however experiencing some issues with access rights of "Google Play Services".

The phone informs me regularly (e.g. when opening Google Pay but also other times) that it needs access to SMS and supplies a quick link to the access rights tab in the phone settings.

However, in this list, there is no "SMS". There is only Calender, Camera, Contacts, Fitness activity, Body sensors, Microphone, GPS, Phone and Storage. (Translation maybe a bit off, I am running the German version).

I have already allowed all but the latter - somehow I am unable to give storage access. No matter how often I activate storage access, the entry remains under "blocked".

Can someone help me out, please? :)

Some additonal info:

When I go to "all access rights" and scroll down to SMS, I actually see that Google Play Services has all those SMS rights:

- read SMS / MMS

- send SMS / MMS

- receive SMS / MMS

What else does it want, then???