yashsingh1/xdaforums huggingface dataset:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Goldsusanoo:
Rebooting to Recovery

I am unfamiliar with ADB commands, how do I move through the fastboot menu to recovery? Also, can I use SuperU from Magisk that I installed from your post in September? I only flashed the August image for root. Thank you.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Kaesberg:
twrp has an official build, and i am wondering if this build works better or if it is the same thing the build number is lower so it made me wonder? anyone know of any issues/benefits with using the official twrp?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] skywalker-live:
Official twrp is flawless. The twrp in this thread can't decrypt your data partition forcing you to format internal storage and /data leaving the phone unencrypted. Even the instructions for installing this twrp are different than installing official twrp.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Kaesberg:
so how do we get a post on the official twrp? will it get taken down if we made a link to the twrp page?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] DsturbD:
What do you need a link for? Got to twrp.me and search for Nash.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
https://xdaforums.com/z2-force/how-to/oreo-nougat-how-to-root-z2-t3756669

Has links to twrp download
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Kaesberg:
I have been getting a lot of pm from fello members asking for help and then when they talk to me they are shocked that this device has more to it. New members are having a hard time with this device and it would be awesome if we could get the officials on xea like we have for the pixel /Nexus device
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Only official ROMs right now are AOSiP and DU. Lineage is unofficial status because selinux and gapps aren't working as intended to be official from them. Other ROM devs probably think the same thing.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Kaesberg:
Well I already am running resurrection remix I ported but was asked not to share it due to the maintainer already working on a rom. So I tried to share an official rom but I guess that's a no no. So lame!
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] cervantesjc:
So, now DU, AOSiP, linage and resurrection are going to the Z2 force, I'm glad I kept the device, really good things are coming.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] JeffersonP360:
I've got this mensage, could anyone help me?

C:\Users\Windows 7\Desktop\root\adb>fastboot flash recovery TWRP3.2.img

target reported max download size of 536870912 bytes

sending 'recovery' (19720 KB)...

OKAY [ 0.596s]

writing 'recovery'...

(bootloader) Invalid partition name recovery

FAILED (remote failure)

finished. total time: 0.601s

C:\Users\Windows 7\Desktop\root\adb>
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] DsturbD:
The partition is boot not recovery and you don't want to flash it you should boot it then flash the zip once you are in twrp.

Download from twrp.me both the img file and the same version zip file

Then fastboot boot twrp.img

Then once you are in twrp install the zip like you would a rom

Then reboot recovery
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] JeffersonP360:
-----------------------------------------------------

Yes it works, but now I get in bootloop, and doesn't kown how to install back native rom.

:(

Please help, my device is global one with 6 gb of ram
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] DsturbD:
sorry about that, may have to do a factory reset
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Then you flashed twrp image rather than booting it. I don't have that stock boot image handy, but there is a flash all for your device in the forum. Just unzip the boot.img from that zip and flash it in the bootloader.

https://xdaforums.com/z2-force/how-to/xt1789-05-stock-oreo-firmware-retbr-t3773275
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] JeffersonP360:
I install the room and try all the process again, but in the moment I've try to install Su, got in boot loop again!

:confused::eek:

I don't kwon what f*** I doing wrong....
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Use Magisk, there should be a flashable zip in the root guide.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
You're flashing SU. You need to flash magisk and wipe data to avoid boot loop.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] JeffersonP360:
Yes, it works!

Thanks guys!!!!!!!!!!!:good::laugh:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] marv3lls:
Issues with SuperSU?

So I realized too late I couldn't do Magisk if I formatted /data but it wasn't mounting so I thought I had to… Now, when I install SuperSU and reboot it just goes to the Moto logo and hangs (forever?). Plz2halp. Not booting anymore (I can get back to bootloader and therefore TWRP). I backed up System and tried to restore it but it didn't seem to work. And now it's in a version of the bootloader where `fastboot flash boot TWRP3.2.img` gives me `error: Failed to identify current slot`

Anyway, I went back to stock using this and now I'm waiting for the backup from Goog to restore.

But I WANT ROOT! Someone able to tell me what I did wrong and how to go to Magisk?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
SuperSu doesn't work well with our device, if at all. You need to use magisk. Read the posts above yours, it was just addressed. I would wipe the dalvik cache afterward too since you restored your system.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] talhahahahahaa:
Stuck at logo

I did everything you said. Now my phone is stuck at the logo.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Did you flash su or magisk?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
I'm flashing the .zip for TWRP and was expecting version 3.2.1-1.

Instead, I got only 3.2.1-0.

Other posts in this thread say encryption issue was solved, but I could not decrypt my phone even formating /data.

Is there a way to really upgrade? Or this is a GUI bug?

Also, is there a way to get out from encryption now?

---------- Post added at 16:37 ---------- Previous post was at 16:29 ----------

Worst... I was loosing root and flashed Magisk. Now I'm bootlooping into the recovery... How to get out? (I know I'm stupid, read n.5 in OP :().

---------- Post added at 17:09 ---------- Previous post was at 16:37 ----------

I've restored a nandroid I've done (from extsdcard) and got the system working again. Now I have some questions:

1. How do I remove encryption?

2. Or, better, how do I upgrade TWRP to 3.2.1-1 that seems to support encryption (I don't want encryption anyway...).
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
I can boot into bootloader, or system (AOSIP) or recovery TWRP (unfortunately 3.2.1-0).

System is with Magisk + Xposed.

I've tried to boot TWRP + flash zip but I can't.

fastboot: error: Failed to identify current slot

Inside TWRP is shown I'm on slot A.

I can't get the latest TWRP, nor uninstall Magisk... I'm stuck.

I've tried to flash all the ROM again but got a lot of fastboot errors.

>fastboot devices -l

00<number> fastboot

>fastboot getvar max-sparse-size

(bootloader) max-: not found

getvar:max-sparse-size FAILED (remote failure)

Finished. Total time: 0.004s

>fastboot --set-active=other

fastboot: error: Device does not support slots
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Can you boot into twrp, not flash? I.E. fastboot boot path/to/twrp.img
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
I restore a nandroid and then go to TWRP and wipe data.

Flash DU to both slots + TWRP installer (although TWRP does not upgrade this way) + boot into flashboot and tried to wipe:

fastboot -w
(bootloader) partition: not found
Erase successfully, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
Erasing 'metadata'
(bootloader) Invalid partition name metadataon-type:metad
FAILED (remote failure)
Finished. Total time: 0.048s

I can boot system, now restoring apps into DU. But I can't flash the latest TWRP and get rid of the encryption issue.

By the way, I tried format data in the past, but somehow the phone got encrypted again...

I need to solve TWRP issue (not upgrading) and only after that try to root.

After installing the apps, I'll try to upgrade TWRP (boot + flash).
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Turn off screen lock. I.E. don't have to enter a password to get into your phone. Then twrp should be able to see your stuff.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
Right now, I can't boot TWRP:

>fastboot flash boot twrp-3.2.1.1-nash.img

fastboot: error: Failed to identify current slot

How to get out of this?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Flashing twrp isn't booting it, that is flashing it.

"Fastboot boot twrp-3.2.1-1-nash.img" is the correct one.

Also for the flash all, just try flashing the partitions again

Fastboot flash partition gpt.bin

From one of the flash all zips
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
It keeps forever on

Downloading 'boot.img'

Keeps on sending partition forever...
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
After all this mess, I lost TWRP and can't boot TWRP either.

I can't flash the full firmware:

1. RSDLite does not work on Windows 10.

2. Manually creating a flashall.bat stops on fastboot errors.

How can I get into this? I never worked with such a complicated phone.

Incredible: I can boot into DU and use the phone. I can also boot into bootloader and stock recovery... How does it come back? ??? :crying:

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

Right now, I don't know what to do... Seems like the bootloader is locked, I can't boot TWRP neither flash/open it. I could flash anything to restore phone, bit seems each thing I do things get worse...
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
I'm not sure what is worse: if we stuck on a bricked device (trying to get the “Qualcomm HS-USB QDLoader 9008” device) or if we stuck into the bootloader and all commands seems to fail. If anybody can help me from now on.

My situation is:

1. Fastboot says fastboot: error: Device does not support slots (i.e., I can only boot one slot that I don't know which one is, probably b, but it makes no difference).

2. I lost TWRP and return to the stock recovery.

3. I cannot boot TWRP (and so, cannot flash TWRP).

4. I have DU Rom running (although with some apps fc now and then).

Does anybody have an idea how to get out of this?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Grab the utilities.zip from here.

That will at least give you a known working fastboot file, adb, flashall.bat, etc.

Grab twrp from here. Both the .img and .zip

Magisk v16 in case you need to reroot.

Disable lockscreen security on your phone. No pins, patterns, fingerprints. Just leave it as none for now.

Extract the utilities.zip to a folder, put the twrp.img in there. Copy the twrp.zip and magisk (might as well) to your phone.

Open a command window from the utilities folder (shift+right click in a blank area of the folder... open command window here).

adb devices
adb reboot bootloader
fastboot devices
fastboot boot (drag n drop the twrp.img here)

flash twrp.zip

flash magisk

wipe dalvik/art

reboot system

That should get you twrp and root all back in order.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
Thanks, but it did not work.

>adb devices

List of devices attached

<number> device

>adb reboot bootloader

>fastboot devices

<number> fastboot

>fastboot boot twrp-3.2.1-1-nash.img

downloading 'boot.img'...

FAILED (remote: unknown command)

finished. total time: 0.005s

I'm sure I'm using the fastboot from Oreo utilities zip you've pointed out.

If it helps, in my bootloader is written:

AP Fastboot Flash Mode (Secure)

BL: MBM-3.0-nash_retail-641a15b-180306

Baseband: M8998_20207.117.02.41R NRD

Product/Variant: nash XT1789-05 64GB PVT

Serial number: ...

CPU: MSM8998 2.1 (4)

UFS: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200

DRAM: 64 GB SAMSUNG LP4X DIE=12GB M5=01 M6=06 M7=00 M8=0E

Console [NULL]: null

Tools Mode Config: DISABLED

Power OK

flashing_unlocked

Software status: Official

Transfer Mode: USB Connected
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Boot to bootloader

fastboot getvar all

Post result.

Don't post your imei
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
>fastboot getvar all

getvar:all FAILED (remote: unknown command)

finished. total time: 0.002s

:crying::crying::crying:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Yeah, I would try the obvious factory data reset, but honestly it sounds like you just need to return to stock. If you have an official firmware for your phone, then use the force. I would reinstall the moto drivers and make sure that you're plugged into a direct 2.0 port and not a hub or 3.0 Seems trivial, but sometimes those things can cause issues.

The way fastboot doesn't know how to do anything is disturbing. though. If you can't do that then it might be possible to sideload through stock recovery, but I've never tried. [MENTION=4604067]Uzephi[/MENTION] would know better than I about that. The whole thing reminds me of that hybrid lock/not locked situation, but you're not getting permission denied, just a fastboot that can't seem to communicate properly.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Problem solved then. Now that you're on a good usb port you should be able to do whatever.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
1. I'm restarting system into bootloader each time. When I choose system, DU is loaded. It happens if I'm connected via USB or not, via adb or physical button. Seems bootloader is my new home :D What can I do?

I can't reboot into TWRP, it goes to bootloader. I'm almost sure it's due to Magisk...

2. I'm rooted.

Just want to check which settings I should let in Magisk.

a) Keep force encryption ON? Is this related with TWRP encryption bug, i.e., if I change these settings, will TWRP encryption work?

Right now, I need to disable fingerprint, PIN, gestures, to get TWRP working.

b) Keep AVB 2.0/dm-verity OFF? Will this avoid boot signature issues?

c) Where does Magisk keep the backup of the boot partition before changing it?

Thanks. A lot of progress today!
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
I would boot the twrp.img so you can get into twrp, once inside, reflash the twrp zip, then reflash DU the version you're using now, then reflash magisk. Wipe the dalvik/art cache then reboot. Hopefully that'll get you to a proper setup. Make sure any lockscreen security is off before you start, it just makes it all easier. If those steps don't resolve the issue I would return to stock and start from a clean slate. A mix and match system can wreak havoc on this phone.

The magisk settings are fine, after you install and update magisk you can setup your lockscreen security and everything should be good to go.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
I tried a lot to get the "preparation" zip to flash before moving to AOSP. I can't find one for XT1789-05 (only US models). Firmwares on internet are different, does not have all the partitions. This worries me because if anything goes wrong I cannot start from the beginning.

Really? Force encryption ON and dm-verity OFF? Do you know where is the backup of the boot partition before flashing Magisk? It needs it to restore if uninstalled.

Yeah, I lose a lot of hours... And only with your help, I could get out of this (partially). I'll test your new sequence of flashing trying to solve the restart issue.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
You already have DU installed, all you're going to do is a dirty flash of the same version, no prep zips or any of that. Just the version of DU you have already.

Just make sure your lockscreen security is off before you flash magisk, once you reflash DU, magisk is gone, that's why you need to reflash like I mentioned. You don't need a backup of the boot.img, if you really need one, then pull the boot.img from the DU.zip

Wipe the Dalvik/Art cache after all is done to keep from having fc's.

BTW, we're way off topic here. Just follow what I posted.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
Should I flash DU in both slots? If so, which is the sequence?

1. Boot the twrp.img so you can get into twrp, once inside, reflash the twrp zip, then reflash DU the version you're using now, then reflash magisk and wipe. Then change the slot and do all the flashes again? TWRP + DU + Magisk. Then wipe the dalvik/art cache then reboot.

or, on contrary,

2. Boot the twrp.img so you can get into twrp, once inside, reflash the twrp zip, then reflash DU the version you're using now, change slots, flash in the other, return to the first one and reflash magisk. Then wipe the dalvik/art cache then reboot.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Don't worry about switching slots. If I remember right, when you flash a rom it goes to both slots, but custom recoveries, kernels, and certain other mods only go to the active slot. Don't quote me, but either way, just follow the plan and leave slots out of the equation.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Roms go to the inactive slot. If fastboot flashing isn't working and you cannot get anything working. Try Flash Fire to flash the twrp zip. You have nothing else to lose. Hopefully you can still boot to a rooted system and do that.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
This made me reboot into bootloader.

What if I do a change:

I would boot the twrp.img so you can get into twrp, once inside, reflash the twrp zip, reboot into TWRP, then reflash DU the version you're using now, then reflash magisk.

I wish I could do that. I couldn't find a flashall.zip file for XT1789-05.

Worse: now it's in the bootanimation for more than 15 minutes... :(

---------- Post added at 14:54 ---------- Previous post was at 14:10 ----------

My actual situation is:

(bootloader) current-slot: _a

(bootloader) running-bl-slot: _a/_a

(bootloader) running-boot-lun: 2

(bootloader) slot-suffixes: _a,_b

(bootloader) slot-count: 2

(bootloader) slot-successful:_a: yes

(bootloader) slot-successful:_b: no

(bootloader) slot-unbootable:_a: no

(bootloader) slot-unbootable:_b: no

(bootloader) slot-retry-count:_a: 5

(bootloader) slot-retry-count:_b: 6

Phone reboots into bootloader. Trying to start, keep on bootanimation.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
You should just get back to a nice clean setup. I'm not sure who your carrier is but a quick search of the forum found what you need. XT1789-05
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
I agree and appreciate very much your help. Indeed, I made a clean install and will start a thread to help others saving time.

The "problem" I was facing is that we do not have a flashall zip firmware. In that thread [MENTION=4604067]Uzephi[/MENTION] said the Motorola releases these files. I've downloaded all carriers and analyzed all the zips. Your models have so many other partitions that I was affraid to just "use the .bat file"... It won't work.

But, like I said, I'm clean now (will post what I've done later) and running TWRP, DU rooted with Magisk in slot B.

Thanks again for your help and support.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Good deal. If you can help others with your variant then that's a win for everyone.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
My plan is this weekend. I have a full working AOSP phone due to your help and I need to give this back to the Community.

By the way, do you know how to dirty flash DU? I'll send you a PM with some doubts I have. Thanks.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Boot twrp, flash DU, reboot. If you want any custom kernel, root, twrp, etc, be sure to flash twrp, reboot bootloader and then boot back into twrp to swap slots
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] doctorman:
is there a reason the OP does not say anything about unlocking bootloader? I promise you I searched
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] marv3lls:
[MENTION=2366275]doctorman[/MENTION]: Not sure but I unlocked before doing all of this... I went with Magisk.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
Maybe because it's a basic rule: locked boatloaders do not allow install (flash) custom recoveries.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 3's&7's:
Official version(s) of TWRP question...

Why the difference in (official) versions between the .img & .zip ?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Marcowerjr:
The .img files are only for boot from fastboot.

The .zip files are flashable from twrp
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 3's&7's:
Thanks for the reply [MENTION=7526576]Marcowe[/MENTION] ...let me be more specific

Why are the different build versions (as opposed to different file types)?

(One can flash .img's in twrp)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Marcowerjr:
If you flash the .img file in fastboot you won't boot and you will need the stock boot.img to boot.

That's because you only have to boot the .img file to to avoid that problem..

And the zip file is for flash TWRP in the device without problems.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 3's&7's:
Correct, I'll be literal this time!

V.3.1 .img vs v.3.2 .zip (build version not file types or purpose)... coincidentally, it doesn't matter now because just this afternoon, TWRP updated the Nash page lol!!! It's all updated now between .img vs .zip build versions
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] doubledragon5:
I say, if it isn't broke, don' fix it.. If v3.1.1-0 works for you, then stick with it. Unless the new version, does something special, like (cooking your dinner), and v3.1.1-0 doesn't. LOL
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Password decrypt for 8.1 was broken and the obvious adb issues from mainline... I'd say 3.2.2 is worth grabbing. Below for device specific changes.

https://github.com/TeamWin/android_device_motorola_nash/commits/android-8.1
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
And how to do it without the zip to flash?

If we flash the img file, won't it mess with the boot partition of our phone?

Edit: forget the question. Zip is there now...
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
3.2.2 is bootlooping in recovery.

I tested:

1. With Magisk installed, reboot into TWRP 3.2.1 and flash 3.2.2. Bootloop.

2. Restore a nandroid. Uninstall Magisk and reboot into System. Reboot into TWRP 3.2.1 and flash 3.2.2. Bootloop.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] 41rw4lk:
Maybe try flashing a clean boot.img, wipe dalvik, reboot. (Might even need to delete twrp folder from storage) Then boot with 3.2.2.img and flash 3.2.2.zip Re-root if needed.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Technical:
Well, I'm not sure what do you mean by "clean boot.img".

If you refer to flashing again the ROM + 3.2.2 zip TWRP, then it works.

Keep in mind that you will be "locked" with that ROM into TWRP: you can't flash it twice or you will get the error 1 about timestamp:

https://plus.google.com/u/1/+JoshCorrell/posts/Aea3mqxcXxz
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] JAWheat411:
This might be a silly question. But did you try booting from a different slot?

Also might have to reflash Magisk to be able to boot.