yashsingh1/xdaforums huggingface dataset:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
Best rom so far. Very fast and stable. Love it. Thank's to the developer for this. The latest builds are even faster than before. Just amazing. So should Pie running :good:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] volcomguyaz:
YES

It will probably be the xt1789-05 varient. You CAN unlock 'bootloader' after that you can basically do anything you want with no stress I would familiarize yourself in the other areas of the forum for this device, its super easy to accomplish. Deff ask if unsure there's a lot of good experience here.

Great time to jump in, the LOS is peaking at greatneas!
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] manuap:
Iam using it since 6 months and I have no problem with the carrier(bsnl, Airtel). Got to tell you, LOS is way better than stock.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] stark1296:
Ah, thanks. I currently own a Potter (Moto G5 Plus) and am using pie custom ROMs on it for quite sometime. I don't think I'll have any issues with unlocking and flashing TWRP, once I look at a guide on XDA.

But, thanks for your concern.

---------- Post added at 04:28 PM ---------- Previous post was at 04:25 PM ----------

Airtel is what I have. Good to hear that Airtel network services are fine on this ROM. Now, whether I'll buy this device or not, ONLY depends on the Indian pricing of upcoming Motorola One Zoom/Pro.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] phivo_:
Hi,

I have received my new Z2 Force (X/1789-03, sprint version) and just installed latest build. Everything works fine until I insert a SIM-card into the tray.

I can enter the PIN and ~10sec later device hangs up and will reboot.

Originally I have started with the MicroG fork (lineage-16.0-20190814-microG-nash), but have also tested the latest nightly (lineage-16.0-20190817-nightly-nash-signed.zip). Both showing exactly the same problem.

Flashing back to stock ROM (7.1.1 Sprint), SIM card is working fine again.

Anyone experiencing the same problem?

Thanks & Regards

Phil
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] npjohnson:
You say 7.1.1, there is your problem. Install stock 8.0, then come to lineage like the wiki says.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] snlzkn:
My camera stops working after some hours of usage. Camera app and also WhatsApp complain that the camera is busy. After a restart it works again. Sometimes it takes 1 minute to open the Camera as well. Similarly the wireless speed goes extremely down after some time. I restart the phone to get back to normal Wireless Speeds. I have nightly from 11th of August with MindTheGapps + Magisk. I have not done any updates using LineageOS Updater yet since I didn't see anything in the change log related to my problems.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] snlzkn:
I used the updater now and my phone lost the IMEI number. It is not possible to turn the WiFi on and also it says No SIM Card. :confused::(:silly::crying:

It looks like the Updater also removed TWRP! I was assuming it would only flash system related files :crying: I am trying to find a way in order not to go back to my backup from 4 days ago...

---------- Post added at 10:56 PM ---------- Previous post was at 10:04 PM ----------

I removed the screen lock, I booted using TWRP with fastboot boot, flashed the nightly using TWRP again, wiped Dalvik and rebooted to the recovery and flashed the GApps again using the LineageOS recovery. And then booted up the system. Voila! My IMEI number, SIM Card, WiFi all available again :)

I had read somewhere that GApps have to be flashed before system boots, but I saw no where that this could have such drastic impacts! I was thinking maybe the Google apps crash or something...
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] CarlosHD912:
Could someone help me? The bootloader from which version (model) was used in this ROM, I am with my Z2 Bricked and I need to try to pass the same bootloader.

(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190608

* Locked Bootloader

* Rom does not start

* I have not activated the "Allow OEM Unlock " in Developer "

Thanks for any help.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] carlosurbina:
Hi,

How do you flash something from LineageOS recovery?

Also, do you know if I can just flash TWRP from there? I am trying to do it from fastboot but no luck, I keep getting errors, and I think ai know what I'm doing.

Thanks!
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Hey everyone,

I just installed the 20190824 nightly and now my Moto Z2 Force won't boot. It attempts to boot but then after seeing the LineageOS boot animation, restarts after about 40 seconds, and informs that it cannot boot. At that point it asks to "try again" or "factory reset".

So, question, can I simply download the 20190823 nightly zip or img and flash without having to factory reset and have to setup my phone again?

Or, Can the 20190824 be reverted?

Thanks.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
Maybe you can switch to the other slot? Has anyone else this problem?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Legza:
Got the same problem just now, tried to update to 20190824 too. I have switched the partition back to previous build using command fastboot set_active a and it had booted normally (you may need fastboot set_active b if you are on a now - just try a or b - one of them will boot).

Now trying 20190823 version, seems like 24 is broken.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Sounds promising. How do I tell which partition it is currently set on?

With that, how to I perform the "fastboot set_active a" from a powered off phone?

Sorry, just want clarification. Can I set it to adb sideload from the LOS recovery console?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Also, I was wondering if the below would work as well as I've noticed that a 20190825 has been released:

https://wiki.lineageos.org/devices/nash/upgrade

---------- Post added at 06:52 PM ---------- Previous post was at 06:15 PM ----------

Man, this LineageOS Recovery is messing me up. I'm used to TWRP where I can run commands, do file transfers, etc. I can't seem to figure out how to do a fastboot command from LOS recovery. Reboot, obviously is what I want, I don't want to Factory Reset, Apply Update only lets me sideload or from local files (none of which allow other commands like fastboot), and within Advanced, I can't Mount System and the other options won't allow it either.

What am I missing?

BTW, because I can't get into the ROM, I can't set things like Root and other options.

Any help would be appreciated. While I wait for a response, educating myself on the LOS Recovery to see what I am missing here.

Thanks again, y'all.

---------- Post added at 07:49 PM ---------- Previous post was at 06:52 PM ----------

OK... ok... KISS.... Keep it Simple, Stupid.

I was missing the driver. Grrrrr. Been offline for hours thinking it was something more complicated than that.

So, I went here to download the drivers:

https://support.motorola.com/us/en/solution/MS88481

Once done, restarted the phone into fastboot (VOL DOWN + PWR buttons). Once there 'fastboot devices' showed something... it showed nothing before.

Ran 'fastboot set_active a'.

Restarted.

VOI-FREAKING-LA!

smh

Thanks all for the assistance.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] TheSchlaf:
Did the 20190823 version work. I've got 20190825 installed and cannot boot.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
I am currently using 20190823, works fine. Waiting to update to the next one after someone else says it is fine. :)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] TheSchlaf:
How can I downgrade to the 20190823 lineage build?

EDIT: downgraded using TWRP. Now my Google Apps stop working.

Reflashed the 20190823 file and MindTheGApps in TWRP and cleared the Dalvik cache. Some Google Services are working.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Legza:
Yes sir, 20190823 works well.

In future, you do not need to use twrp. Just run 'fastboot set_active a' as I have said - or, if it will not boot, 'fastboot set_active b'.

The previous build will boot normally from previous partition, and after that you can update normally via cm updater to some other build.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Has anyone tried a build after 20190823? Being cautious since the boot loop.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] TheSchlaf:
Nope. Still on that build.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] phivo_:
Thanks a lot. This has solved my problem. (Even as it took me quite some time to get back to stock)

This is my first Motorola, so did not get the point that Wiki statement "Your device must be on bootloader version OCSX* " means, that it must be on Oreo. But now I know ;)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Well, trying for the 20190828 build... Oddly enough, the 20190824 changelog didn't give much...

Changes included in lineage-16.0-20190824-nightly-nash-signed.zip

SystemUI: Use matching data usage size formatting between QS and Settings

android_frameworks_base

Update Xbox BT controller mapping to support upcoming controller firmware update

android_frameworks_base

I'll let ya know.

---------- Post added at 09:34 AM ---------- Previous post was at 09:04 AM ----------

These longer than normal boot times always make me nervous... especially if another reboot is part of the process... well, the update failed... again. Attempting to boot to slot B... failed... I assumed I was still on A, evidently not. Switching back to slot A... booted back to 20190823.

Sticking with this ROM for a while.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
[MENTION=3671534]Legza[/MENTION]
[MENTION=7293444]TheSchlaf[/MENTION]

Would you two be on tmo? I am, and have this issue as noted previously.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Dan41:
Does anybody have problems with the LTE? For me it only says H+ and H. And according to the settings the preferred network type is set to LTE.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
No issues with LTE here... actually, mine shows LTE+.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Dan41:
It's set to "global" in "preferred network type" and outside it says "preferred network mode: LTE", and I'm in the latest build, maybe it's a problem with the signal? I mean, when I was in Stock ROM it was almost always in LTE, which is why I find it odd. Is there a way that I could test to see if the LTE is actually working?

Thanks in advance.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Instead of Global, can you select LTE? What happens?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Legza:
Yea, tmo phone here. You think it could be the submodel (-04) problem?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Dan41:
I can select LTE, but when I do, my phone says ''no service''.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Doesn't appear to be an issue with the -04 variant. One with a -5 has the issue as well.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] manuap:
I do have the same issue, mine is -06.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Are you on tmo?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] manuap:
No mine is retin. Im not on tmo
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Tigerfou:
Hi,

Installed 20190828 and I have "no sim" and no wifi...

trying to boot on second partition to downgrade, but while in bootloader, on "fastboot set_active b" (or a) adb returns the help commands and options as if the command didn't exist...

Am I doing it wrong ?

Thanks for your assistance

EDIT :

Solved using minimal adb fastboot install instead of the official tools (no idea why it didn't work).

https://androidfilehost.com/?fid=746010030569952951

could downgrade succesfully by switching slots
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Legza:
Seems like builds after 08/24 need clean installation. However, previous builds seem to be stable enough for daily use :) Will stay on 08/23 for a while.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Shreeram02:
is there any way to change resolution to 1080p?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
The screen is natively 1440p. I don't think there is a way to reduce down to 1080p. Haven't found an option for it.

The screen in the Moto Z2 Force is:

1440 x 2560 pixels, 16:9 ratio

Specs:

https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/130422/p/30,6720,10303
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Shreeram02:
Yea I know its 1440p, I just asked is there a way?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] npjohnson:
Welp, just like last year, looks like hurricane is gonna wreck my house, so I'll be a little slow to respond here/to tickets for a week or two.

As for the recent nightlies, looks like the new camera HAL requires a clean (format data) flash.

This won't happen again, but you'll have to clean flash to update :(
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Sorry to hear about the house, man. Hope that it doesn't get serious.

Keep us posted!
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
So, we need to wipe both Data and System to get to a build later than 20190823?

With the reports of those losing LTE or access to their SIM, how do we avoid that? Several who have tried builds after 20190823 have had similar issues.

I assume the previous flash process would still work:

1. Fastboot to TWRP img.

2. Wipe Data and System.

3. Flash latest build.

4. Reboot to TWRP again.

5. Install MTG, AddonSU, etc.

6. Reboot to finish flashing.

Thanks for the effort and responding. Hope the house is still in one piece.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Alrighty.... I done did it... where was my process... one snag though... after rebooting back into recovery after flashing LOS, my Internal Storage was encrypted. Had to wipe and copy the files back over. For some reason, ADB SIDELOAD wasn't working from TWRP... meh.

1. Install Moto Z2 Force drivers.

2. Copied lineage-16.0-20190903-nightly-nash-signed.zip, addonsu-16.0-arm64-signed.zip, and MindTheGapps-9.0.0-arm64-20190615_031441.zip to internal storage.

2. Ran the following commands:

a. adb devices

b. adb reboot bootloader (OR vol down + power)

c. fastboot devices

d. fastboot boot twrp-3.3.1-0-nash.img

3. Wiped System and Data.

4. using TWRP, flashed lineage-16.0-20190903-nightly-nash-signed.zip from internal storage.

5. Rebooted back into Recovery.

6. Found that Internal Storage was encrypted.

a. Wiped Internal Storage.

b. Copied addonsu-16.0-arm64-signed.zip, and MindTheGapps-9.0.0-arm64-20190615_031441.zip to internal storage, again.

7. Flashed addonsu-16.0-arm64-signed.zip.

8. Flashed MindTheGapps-9.0.0-arm64-20190615_031441.zip.

9. Wiped Dalvik Cache.

10. Rebooted.

LineageOS 20190903 booted without issue.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Ok, well, I evidently installed 20190902.

Something of note... Using the Updater, it downloads 20190903, acts like it is installing, shows Reboot option, after reboot, it didn't install. Still on 20190902.

Anything I can provide to assist troubleshooting?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] BrunoBuin:
Hello Carlos,

Can you explain what is your problem?

You hava Moto Z2 Force and OEM is not unlocked?

You try to install any custom ROM?

You remember what version of system was in you phone?

Best regards.

Bruno
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
FYI, I downloaded 20190905 and it successfully updated from 20190902. So, if you run into this, try a later build.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Kaesberg:
does this rom have any of the kernel update from the new pie rom?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Legza:
Just for your interest.

I have tried to update from 08/23 to 09/05 via ota. As expected, the phone haven't booted successfully. It booted into los recovery with the some message like "factory reset required". I have tapped the factory reset and after that it booted up and working normally.

Meaning that i haven't installed los from scratch with adb sideload etc.

User data is lost, of course - but Magisk and Gapps survived.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Good to know. I did the whole reset with sideload.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] TheSchlaf:
I ended up doing a clean install of the latest update and Mind the Gapps. Everything is working smoothly.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] zuettu:
I'm running stock on my XT1789-06 with "MBM-3.0-nash_retail-cd73d31dc-190327" bootloader, now I got the option to OTA to pie. Is this update going to be a problem if I choose to flash lineage later?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
From what I gather, only Verizon has Pie rom's available within the US carriers.

If you are on Verizon, yes. Others with Verizon have tried to flash LOS Pie and things like LTE, their SIM card, etc, would not work afterwards. From what I understand, it is best to keep on Oreo and flash to LOS Pie.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Dany XP:
Hi guys, i just a got a new tmo Z2F from ebay for cheap, strangely enough with already BL unlocked. Since it's very unlikely we will ever have an official Pie update, i guess i will have to join guys pretty soon, maybe in 2 weeks ill have some spare time.

My modding days are old as my Nexus 5 and Moto G1 :) , any advice to re-start? Especially about the 2 slots thing (which is a new thing for me)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] johnathanamber:
Hey, and welcome to the Moto family (I know, sounds cheesy.... it was meant to be.).

My process went as follows, but before using the below, be sure to read the LineageOS wiki on it here https://wiki.lineageos.org/devices/nash/:

When I did my install, I wanted root and GApps done as well. You MUST install all three BEFORE booting into Lineage for the first time.

1. Fastboot using nash TWRP.

2. Wipe Data and System.

3. Flash nash LineageOS zip.

4. Reboot back into nash TWRP recovery.

5. Sideload AddonSU.

6. Sideload GApps (Mind The GApps).

7. ADB reboot into Lineage OS to finish installation.​

Hope this helps.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Dany XP:
Excellent.

1 question though: step 1 and 4, when u mean go to twrp, u mean just BOOT using fastboot (through pc's terminal) right? It was my understanding we DONT have to flash any .img in our z2f. I don't mind having to use pc for flashing, im planning on doing this very rarely, 2 or 3 times Max, definitely not often like when I had my Nexus 5, lol, I was trying new ROMs every week ???
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Dany XP:
I'm having a little trouble here. I can't even BOOT from twrp.img...see attachment. And even device-info doest work, even if fastboot devices works...
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] npjohnson:
You're trying to flash boot don't do that. Just boot it.

But please just go back and follow the wiki linked in the OP, it details everything,
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Legza:
Looks like LOS wiki provides some copy-pasted commands from other device.

To get unlock data you should input fastboot oem get_unlock_data. However, you have mentioned that you already have unlocked bootloader, so, you don't need it.

To install los via sideload you also don't need to flash recovery (and also it could not be done by the command flash boot, but flash recovery_a, or boot_a, i think).

Just run the recovery on phone by the command: fastboot boot C:\<path to recovery>\<recovery>.img

The rest of the instruction seems to be fine. Format data from recovery, adb sideload los and after reboot gapps.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] doombuger:
I had this running on my -02 (USC) variant for several months, along with open gapps (8/12), twrp-3.3.1-0, and magisk 19.3 with no issues on verizon.

however after updating from the 8/12/19 release of lineage nightlies to any from september 3-10, i cannot get it to work again. the farthest i've gotten after updating was after initial setup... then it auto reboots continuously after each start up. almost like its unstable...?

ive gone so far as to reverting back to stock, and trying everything from scratch with no luck.

does anybody have a lineage zip from august they could share? the official website only has the past 6 days of nightlies available to download.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] allrightlite:
Yes, all updates after 08/23 needs clean data and factory reset. Then the phone should start normally and you can start from the beginning. If that not enough, you must clean install completly. But normally factory reset should be enough. Hope that's right, because I haven't test it. I can just sum up all what I have read here and in Discord.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] doombuger:
i've tried a clean install with no luck... i'm on stock build OPXS.109.40.22

here is what i've done in with past LOS releases with success:

Boot phone into bootloader. connect to PC. - USE PC to boot into TWRP recovery (Fastboot boot Twrp.img in ADB) "Fastboot boot twrp-3.3.1-0-nash.img".

Flash Lineage OS - reboot to bootloader.

fastboot twrp again using PC ADB - Flash Gapps - reboot to system - enable Dev Options and USB debugging - reboot to bootloader

(I can get lineage and gapps running fine as far as i can tell... Until the steps below....)

fastboot twrp.img - Flash TWRP.zip - *reboot to TWRP - Flash Magisk - Format Data - reboot to system.

Here is where the problem shows..

after android setup wizard is finished/mid "Checking/Installing Updates" screen; an additional dialogue pops up saying "taking a while... try connecting to a different network" and then randomly reboots and starts in recovery.

Edit: (NOT)Solved: Twrp cannot be flashed. only fastboot... after a reboot, it self rebooted just after android start up. it then booted to recovery and prompts to factory reset.. It's probably caused by magisk 19.3. i did notice that it was prompting me to download canary debug version of 19.4 which i ignored.

my goal is to have Lineage + Gapps + Magisk running again. If anyone knows what i can do to fix it or if you could point me in the right direction for a previous build download... that'd be great!! i wouldn't mind going back to what i had working in august. otherwise i'm stuck with stock... thanks
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Dany XP:
Alright, I managed to go until the flashing zip step while booting adb img But:

- can't use Los recovery. Using adb boot lineage-recovery.img doesn't boot in said recovery (not even if manually going there)

- I can use boot twrp.img, but if I try to adb sideload any zip from there I got the attach error. Funny thing is if I use last twrp I got the error u see. If I use an old twrp (ex. 3.2.1.1.) the flashing starts but ends almost immediately with error 7

(I know usually error 7 is for an incompatible Rom listed in the updater-script...I check in Los Rom under meta-inf/com/android/... But there is no updater script! Only 2 files: metadata and otacert. Is this normal for Los ROMs?)

Basically I cant install any Los zip...??

I'm already in stock T-Mobile Oreo Rom, unlock bootloader...