Develop Bugs

Bootloop issue - USB debugging not enabled

Hi all,
Sorry if this thread is in the wrong area.
I have in my possession a Nexus 5X which is stuck in a boot loop. I don't think it's a case of the power button being held down because the phone behaves differently depending on whether I hold the power button down or not.
I can boot into bootloader/fastboot mode which is locked. I have the standard options to Start/Restart bootloader/Recovery mode/Power off. If I try to get into recovery mode from here, the phone enters "download mode" for a short amount of time. After that, the bootloop begins again and I can only get the phone back to bootloader at best.
If I try to use the comment fastboot oem unlock I will get the message (remote: oem unlock is not allowed). I believe this is because don't have USB debugging/developer options enabled. I can't turn the phone on to enable this.
I have tried using Nexus Root Toolkit to unlock the bootloader (using the Flash Stock + Unroot and Soft-Bricked/Bootloop option) and everything seems to run fine until it restarts the phone. This triggers the boot loop again and the Nexus Root Toolkit hangs "waiting for phone..." after previously having been able to detect it.
I've tried using WinDroid Toolkit v3.1 also to unlock the bootloader without success.
Quite simply, is it possible to unlock the bootloader while the phone is in this state? I know this is a common problem with these phones but I'm not convinced this can't be fixed at home yet!
Thanks in advance for any help.
Some extra info:
fastboot getvar all
(bootloader) product: bullhead
(bootloader) off-mode-charge: 1
(bootloader) max-download-size: 0x20000000
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4017mV
(bootloader) version-hardware: rev_1.0
(bootloader) version-baseband: M8994F-2.6.36.2.20
(bootloader) version-bootloader: BHZ11h
(bootloader) variant: bullhead LGH791 32GB
(bootloader) serialno: (hide)
(bootloader) kernel: lk
(bootloader) secure-boot: yes
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0xa80000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x65a3fb800
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x6000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:vendor: 0xf800000
(bootloader) unlocked: no

Seems u are having problems with bootloader, have u tried flash stock bootloader image via fastboot and then proceed with OEM unlock?

imor said:
Seems u are having problems with bootloader, have u tried flash stock bootloader image via fastboot and then proceed with OEM unlock?
Click to expand...
Click to collapse
No, I haven't tried that. I'll give it a go later. Assumed I couldn't flash anything with a locked bootloader.

Moto z2 force xt1789-05 does not enter into recovery mode only stays in fastboot mode

My phone does not enter in recovery mode nor can I restore it from the factory, since it does not enter into recovery mode it only stays in fastboot, the last commands that it used were: adb kill-server and then fastboot -w, that's when the problem started, any solution? Thank you.

:good:

omnismart said:
:good:
Click to expand...
Click to collapse
does not enter into recovery mode, when I select recovery, it returns to fasboot mode

luiguy said:
does not enter into recovery mode, when I select recovery, it returns to fasboot mode
Click to expand...
Click to collapse
can you flash any recovery image and see if it enters the recovery after that?
It's possible that the is no recovery image in the recovery partition to boot hence it is taking back to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app

shibaa987 said:
can you flash any recovery image and see if it enters the recovery after that?
It's possible that the is no recovery image in the recovery partition to boot hence it is taking back to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
can be done by having the boot loader blocked?

luiguy said:
can be done by having the boot loader blocked?
Click to expand...
Click to collapse
you mean to say that you have a locked bootloader?
Sent from my [device_name] using XDA-Developers Legacy app

shibaa987 said:
you mean to say that you have a locked bootloader?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
that's right, and I'm in the stock ROM, the bootloader has never been unlocked

You keep posting the same question all over the place, but you're not helping anyone to help you. I've asked a couple times to see your flashfile, but it has never been posted. Maybe there is something wrong with it. We really need to try and flash the bootloader, that will tell us what we're up against. If you can flash the bootloader, then you can flash back to stock and get out of this mess, but if you get a permission denied and you're using an official signed, then that's another problem.
You said you've tried, but no you haven't. You've tried to use your flashfile and nothing happened, hence the reason I keep asking to see it. Your main goal right now, and I've said this before, is to determine whether you can flash or not. A locked bootloader will only accept official signed firmware from the same carrier with the same revision or higher. So pretty please, don't post the same question anymore but do post your flashfile so we can see if there is anything wrong with it. Better yet, if anyone has a working flashfile for the lastest -05 variant please post it so we can rule it out. In the meantime run this command in fastboot and post the output, but be sure that you don't post your imei info. Not trying to be a ****, but posting the same question all over the forum does nothing to help and will get you banned.
Code:
fastboot getvar all
Post the output of this command minus your imei info.

Code:
fastboot getvar all
Post the output of this command minus your imei info.[/QUOTE]
all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-b48569f-170628
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: no
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: NGRL470061
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 86027E05
(bootloader) securestate: engineering
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-29-2017
(bootloader) sku: XT1789-05
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4172
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_amx/nash:7.1.1/NPX26
(bootloader) ro.build.fingerprint[1]: .122-49/53:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.53.nash_amx.am
(bootloader) ro.build.version.full[1]: x.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.7.r1-09300-8x98.0
(bootloader) version-baseband: M8998_24.71.01.87R NRS
(bootloader) kernel.version[0]: Linux version 4.4.21-perf-gb6ca254 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 2015012
(bootloader) kernel.version[2]: 3 (prerelease) (GCC) ) #1 SMP PREEMPT We
(bootloader) kernel.version[3]: d Jun 28 08:50:20 CDT 2017
(bootloader) abl.git: MBM-3.0-nash_retail-b48569f-170628
(bootloader) xbl.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) pmic.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) rpm.git: MBM-3.0-nash_retail-d3e45a4-170628
(bootloader) tz.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) hyp.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) devcfg.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib64.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) keymaster.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) storsec.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) prov.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: openmx
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _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: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.146s

41rw4lk said:
You keep posting the same question all over the place, but you're not helping anyone to help you. I've asked a couple times to see your flashfile, but it has never been posted. Maybe there is something wrong with it. We really need to try and flash the bootloader, that will tell us what we're up against. If you can flash the bootloader, then you can flash back to stock and get out of this mess, but if you get a permission denied and you're using an official signed, then that's another problem.
You said you've tried, but no you haven't. You've tried to use your flashfile and nothing happened, hence the reason I keep asking to see it. Your main goal right now, and I've said this before, is to determine whether you can flash or not. A locked bootloader will only accept official signed firmware from the same carrier with the same revision or higher. So pretty please, don't post the same question anymore but do post your flashfile so we can see if there is anything wrong with it. Better yet, if anyone has a working flashfile for the lastest -05 variant please post it so we can rule it out. In the meantime run this command in fastboot and post the output, but be sure that you don't post your imei info. Not trying to be a ****, but posting the same question all over the forum does nothing to help and will get you banned.
Code:
fastboot getvar all
Post the output of this command minus your imei info.
Click to expand...
Click to collapse
there are the data that you asked me

What were you trying to do when all your trouble initially began? I see that you still have nougat on that slot and the bootloader secure state is engineering, that's not right. Can you still boot into your system? If so make sure adb is enabled. I assume oem unlock is greyed out and unavailable right? What firmware have you tried to flash? Also, if you're able to boot into your system you should disable fingerprint/lockscreen security until you have everything resolved.

41rw4lk said:
What were you trying to do when all your trouble initially began? I see that you still have nougat on that slot and the bootloader secure state is engineering, that's not right. Can you still boot into your system? If so make sure adb is enabled. I assume oem unlock is greyed out and unavailable right? What firmware have you tried to flash? Also, if you're able to boot into your system you should disable fingerprint/lockscreen security until you have everything resolved.
Click to expand...
Click to collapse
I just tried to update it to Android 8, if I can enter the system and I have USB debugging enabled, EOM is in gray, the ROM I wanted to install was: https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ . Android 8

luiguy said:
I just tried to update it to Android 8, if I can enter the system and I have USB debugging enabled, EOM is in gray, the ROM I wanted to install was: https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/ . Android 8
Click to expand...
Click to collapse
In fastboot mode switch slots and run the getvar command again. Post the results and see if the other slot boots. If not switch back. You're currently on _a
Code:
fastboot devices
fastboot --set-active=b
fastboot getvar all
fasboot reboot
Post the results of the getvar command. If the phone boots to system on slot _b check out your settings, see if oem unlock is available and make sure adb debugging is on. If it doesn't boot, it should automatically fall back to slot _a but if it doesn't just run the commands above again only set active to a. You don't need to run the getvar command again once you're back to _a. *Note when you run the getvar command the 'current-slot' entry tells you what slot you're on.

41rw4lk said:
In fastboot mode switch slots and run the getvar command again. Post the results and see if the other slot boots. If not switch back. You're currently on _a
Code:
fastboot devices
fastboot --set-active=b
fastboot getvar all
fasboot reboot
Post the results of the getvar command. If the phone boots to system on slot _b check out your settings, see if oem unlock is available and make sure adb debugging is on. If it doesn't boot, it should automatically fall back to slot _a but if it doesn't just run the commands above again only set active to a. You don't need to run the getvar command again once you're back to _a. *Note when you run the getvar command the 'current-slot' entry tells you what slot you're on.
Click to expand...
Click to collapse
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-b48569f-17062
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: no
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: NGRL470061
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 86027E05
(bootloader) securestate: engineering
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-29-2017
(bootloader) sku: XT1789-05
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4301
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_amx/nash:7.1.1
(bootloader) ro.build.fingerprint[1]: .122-49/53:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.53.nash_
(bootloader) ro.build.version.full[1]: x.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.7.r1-09300-8x98.0
(bootloader) version-baseband: M8998_24.71.01.87R NRS
(bootloader) kernel.version[0]: Linux version 4.4.21-perf-gb6ca254
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 2
(bootloader) kernel.version[2]: 3 (prerelease) (GCC) ) #1 SMP PREE
(bootloader) kernel.version[3]: d Jun 28 08:50:20 CDT 2017
(bootloader) abl.git: MBM-3.0-nash_retail-b48569f-170628
(bootloader) xbl.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) pmic.git: MBM-3.0-nash_retail-dea2712-170628
(bootloader) rpm.git: MBM-3.0-nash_retail-d3e45a4-170628
(bootloader) tz.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) hyp.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) devcfg.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) cmnlib64.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) keymaster.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) storsec.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) prov.git: MBM-3.0-nash_retail-25be42d-170628
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: openmx
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _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: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.193s

(bootloader) current-slot: _a
(bootloader) running-bl-slot: _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: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.193s
You're still on slot a, you need to be on slot b
After you run the command set-active, reboot the bootloader then do a getvar. Also, see if it will boot.
Code:
fastboot --set-active=b
fastboot reboot bootloader
fastboot getvar all
fastboot reboot

41rw4lk said:
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _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: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 7.193s
You're still on slot a, you need to be on slot b
After you run the command set-active, reboot the bootloader then do a getvar. Also, see if it will boot.
Code:
fastboot --set-active=b
fastboot reboot bootloader
fastboot getvar all
fastboot reboot
Click to expand...
Click to collapse
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'

luiguy said:
C:\Users\luiguymm\Desktop\adb - fastboot MOTO Z2 PLAY Z2 FORCE>fastboot --set-
active = b
fastboot: unrecognised option `--set-active'
Click to expand...
Click to collapse
Either your fastboot file is out of date, or that engineering state is limiting your accessibility. Close any command prompt windows. Download this utilities zip, it has known good adb and fastboot files in it. Extract it to a folder somewhere, open the folder, hold shift and right click a blank area inside the folder, then choose open a command window here. Verify that your device is connected in fastboot 'fastboot devices', then try setting the active slot again and proceed from there.
*Note - Make sure you're using a 2.0 usb port off the motherboard, not a hub from the front of the pc and such. Most people don't have problems with this, but it has caused problems for some. Not all usb ports are so universal, ports on the mobo tend to have more consistent power supply and transfer rates; less interference as well.

41rw4lk said:
Either your fastboot file is out of date, or that engineering state is limiting your accessibility. Close any command prompt windows. Download this utilities zip, it has known good adb and fastboot files in it. Extract it to a folder somewhere, open the folder, hold shift and right click a blank area inside the folder, then choose open a command window here. Verify that your device is connected in fastboot 'fastboot devices', then try setting the active slot again and proceed from there.
*Note - Make sure you're using a 2.0 usb port off the motherboard, not a hub from the front of the pc and such. Most people don't have problems with this, but it has caused problems for some. Not all usb ports are so universal, ports on the mobo tend to have more consistent power supply and transfer rates; less interference as well.
Click to expand...
Click to collapse
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>

luiguy said:
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>
Click to expand...
Click to collapse
It has to be your phone that limiting your commands. I ran the same commands right out of the utilities zip and had no troubles. I think since you can't really do anything else, and you can't flash back to stock normally you might need to blank flash to get the gist of things back in order. First though, I would open your flashall file and paste the lines one by one in the command prompt and see if you could manually flash your phone. As it stands now, whenever you try to run the .bat file it just does nothing. Skip the fb_mode set and the getvar and start with the actual flashing. It will either flash or you'll get a permission denied most likely.
If you can't manually flash the oreo firmware, then you'll most likely need to blank flash. Several people have had their phone go wonky after trying to upgrade from nougat. So much for seamless updates.

luiguy said:
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Downloads\FlashAllUtils>fastboot --set-active = b
(bootloader) slot-suffi: not found
(bootloader) current-slots: not found
fastboot: usage: unknown command =
C:\Users\luiguymm\Downloads\FlashAllUtils>
Click to expand...
Click to collapse
Just noticed, you're entering the command wrong. The only space in this command is between the 't' and the '-' fastboot --set-active=b
You need to check out the _b slot, see what is on it and whether it will boot or not. If it does boot, check the settings and take note of everything. If it doesn't boot then we'll go from there. Just copy the fastboot command as I typed it.

Bought a bricked XT1789-06 for cheap

Good morning,
I bougth a X1789-06 for cheap on ebay and thought I can fix it. But its harder then I expected.
The system doesn't start at all, except fot the bootloader. I'm able to run fastboot but I can't do much there because it's locked. ADB is not avavailable.
Here is my fastboot getvar all:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_SS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3565180808xxxxxx
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3773
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) git:xbl: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:pmic: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:rpm: MBM-3.0-nash_retail-b13e14f-180828
(bootloader) git:tz: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:hyp: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:devcfg: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:cmnlib: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:keymaster: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:storsec: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:prov: MBM-3.0-nash_retail-22c9393-190327
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 3
all: listed above
finished. total time: 0.172s
I tried to do fastboot boot boot.img with the rom thats in "ro.build.fingerprint" but it doesn't boot. Neither does TWRP.
The result at booting into TWRP looks like that:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_SS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot boot twrp-3.2.3-2-nash.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 30.773s
LMSA also doesnt work. It says "Flash failed. Please try again".
Do you have any ideas how to get out of this and get something runnung again?
Thanks
Benny

bennyschw said:
Good morning,
I bougth a X1789-06 for cheap on ebay and thought I can fix it. But its harder then I expected.
The system doesn't start at all, except fot the bootloader. I'm able to run fastboot but I can't do much there because it's locked. ADB is not avavailable.
Here is my fastboot getvar all:
I tried to do fastboot boot boot.img with the rom thats in "ro.build.fingerprint" but it doesn't boot. Neither does TWRP.
The result at booting into TWRP looks like that:
LMSA also doesnt work. It says "Flash failed. Please try again".
Do you have any ideas how to get out of this and get something runnung again?
Thanks
Benny
Click to expand...
Click to collapse
Looks like getvar all says Retail
But you are flashing Reteu?
Try
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/
Sent from my mata using XDA Labs

Goot moring,
tried to flash this version with the flashall tool, same result.
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.222s]
finished. total time: 0.222s
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.240s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.302s
Those lines above are the first ones with the flashall tool. Flash permission is always denied so nothing changes.
When I try to boot via fastboot boot boot.img the Motorola Logo appears for 30 secounds and then goes to fastboot again.
The problem is, that flasing is locked and I need to unlock it somehow. But its not possible without some Android system running because I have to activate it in the developer options.
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem unlock RXNDLVGJRXZ65Y62EZUE
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
I dont know witch strange things happend to this poor phone.
But thank you for your reply.
Benny

Since of locked status you can't change bootloader at moment. So don't try to flash an OS version different from actual bootloader (Nougat?)
Flash an OS version "compatible" with boot loader (don't try to flash bootloader!!), boot to system, switch to unlockable status, unlock it and... enjoy!
Remember anyway thay since you have fastboot access it isn't still hardbricked at all...

enetec said:
Since of locked status you can't change bootloader at moment. So don't try to flash an OS version different from actual bootloader (Nougat?)
Flash an OS version "compatible" with boot loader (don't try to flash bootloader!!), boot to system, switch to unlockable status, unlock it and... enjoy!
Remember anyway thay since you have fastboot access it isn't still hardbricked at all...
Click to expand...
Click to collapse
What makes me suspicious is that it says "RETAIL" in the fingerprint but I have the German/Europe version. So it should be "RETEU".
Anyway, tried to flash the 7.1.1 retail stock rom because theres no reteu 7.1.1 available but the result is still the same: "Permission denied". But it was worth a try!
"Fastboot boot boot.img" doesn't work either. Bootscreen appears for a while, it vibrates and then goes back to fastboot.

I have a European z2 and it's retail version.
When it bootloop I flashed wrong firmware retu. Had the ADB debug not available and bootloader locked.
Then power and volume down I read the right version and downloaded the ROM and flashed it whit error but it worked.
Try flash this one https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

berka38 said:
I have a European z2 and it's retail version.
When it bootloop I flashed wrong firmware retu. Had the ADB debug not available and bootloader locked.
Then power and volume down I read the right version and downloaded the ROM and flashed it whit error but it worked.
Click to expand...
Click to collapse
How do I know whats the right version for my bootloader? Just by trial and error?
Ist there a list somewhere?
But yes, there is some hope rising inside me
EDIT:
I tried the rom you suggested already. It dowsn't work. Same error as always: Permission denied.

I got to check how I find my info what was on it later but it also gave me error when flashed but It booted

berka38 said:
I got to check how I find my info what was on it later but it also gave me error when flashed but It booted
Click to expand...
Click to collapse
Nope, tried it again. While flashing there are those known permission denied errors. When it should boot the "device is corrupt" screen shows up and it shuts down after a while.
But the slots changed somehow:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3565180808xxxxxx
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3760
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:pmic: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190705
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:prov: MBM-3.0-nash_retail-3537781-190705
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.274s
EDIT:
Uh, I noticed that the bootloader has also changed. Don't know whats happening here.
EDIT 2:
Is there a way to "hardbrick" the phone on purpose to do a blankflash?

bennyschw said:
Nope, tried it again. While flashing there are those known permission denied errors. ...<CUT>
Click to expand...
Click to collapse
Since what you posted you have an Oreo Reteu flashed on this phone. More, it is reported verity off and warranty void, so your bootloader should be unlocked.
My suspect is that someone has flashed it with Oreo THEN tried to relock bootloader and... bricked it! :silly:
Anyway, i don't know bootloader versions, but if this has been already flashed with Oreo, I don't think you will be able to reflash it with Nougat easily...
So, I would try this way...
- try to oem unlock it and look what it says...
- try to flash it with Oreo RETEU or Oreo Retail and look what happens...
What is weird is that "flashing locked" status...

You should try the lmsa tool first, see if it will do a rescue and get you back to booting.
https://support.lenovo.com/us/en/downloads/ds101291
If no go, then you can try a blankflash. It's possible that between all the flashing there have become discrepancies in the boot chain, and a blankflash will fix that. Afterwards you flash the correct firmware for your phone. You have an -06 Dual Sim right? So you'll probably want reteu ds firmware, but retail should also work. Either way it should boot, the only problem could be no modem. If that's the case, then factory reset from the recovery to see if that sorts it. If not, then flash the retail firmware and do a factory reset from the recovery, modem should be back.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
I would stay away from pie firmware until you're up and running. Just for verification it does say xt1789-06 by the charging port right? Does it have a dual sim try as well? Your priority should be, getting booting, sign into google, oem unlock. Once your bootloader is unlocked you'll have wiggle room, until then it'll be a little tough going.

Goot morning,
LSMA failes. It says "Fastboot flash single partition - Flash failes. Please try again.
When I do the oem unlock the phone replies:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem unlock RXNDLVGJRXZ65Y62EZUE
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.006s]
finished. total time: 0.007s
Now I just tried to flash the boot.img of RETEU:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.541s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.547s
And RETAIL:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.538s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.544s
In my first post I was trying to flash the single sim version. Was my fault. But the same things happend there. This is a XT1789-06 with dual sim.
But as you said, it should have booted with no mobile connection.
By the way, fastboot oem blankflash doesnt work either:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.005s
Is there another way to go to blankflash?
I also tired the edl cable method. But it went right into bootloader.
Right now I'm setting up my old laptop with only USB 2 ports. Maybe theres a difference. I'll keep you up to date.
Thank you for your effort!
Benny

This is the last retail oreo firmware, it appears to be newer than what you've tried or at least what has been shown from your getvar output.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Before you try and flash it, run getvar command again and note your build version, build fingerprint, and which slot is your current slot . Then try to flash the retail firmware and boot. If nothing seems to change run the getvar command again and see if there are any changes to what you noted before. If your current slot is different, run the flashall again. If the current slot is the same, then fastboot --set-active=other and faatboot reboot bootloader. Run getvar command again to verify that you're on the other slot, and note the items listed above. Then run your flashall again. Run getvar command one more time and note the items again.
Hopefully enough of that will flash so you can boot. Between what you've flashed and god knows what was flashed before you, there could be a hodge-podge of nonsense scattered between the slots.
If still no boot, try running the lmsa tool again, maybe enough was cleaned up for the tool to run. Make sure that you're using admin privileges for the tool and command prompt if needed.
*Note - oem unlock won't work until you've enabled oem unlocking in dev settings, which is why booting is your 1st priority.

41rw4lk said:
This is the last retail oreo firmware, it appears to be newer than what you've tried or at least what has been shown from your getvar output.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Before you try and flash it, run getvar command again and note your build version, build fingerprint, and which slot is your current slot . Then try to flash the retail firmware and boot. If nothing seems to change run the getvar command again and see if there are any changes to what you noted before. If your current slot is different, run the flashall again. If the current slot is the same, then fastboot --set-active=other and faatboot reboot bootloader. Run getvar command again to verify that you're on the other slot, and note the items listed above. Then run your flashall again. Run getvar command one more time and note the items again.
Hopefully enough of that will flash so you can boot. Between what you've flashed and god knows what was flashed before you, there could be a hodge-podge of nonsense scattered between the slots.
If still no boot, try running the lmsa tool again, maybe enough was cleaned up for the tool to run. Make sure that you're using admin privileges for the tool and command prompt if needed.
*Note - oem unlock won't work until you've enabled oem unlocking in dev settings, which is why booting is your 1st priority.
Click to expand...
Click to collapse
Absolutely nothing has changed except the battery voltage
Tried all the different retail and reteu 8.0 versions but there changes nothing. I also tried to boot the roms via boot boot.img but no one worked.
LSMA replies with the same error as before.
Cant even change the slots manually:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot --set-active=other
Setting current slot to 'b'...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot --set-active=b
Setting current slot to 'b'...
FAILED (remote failure)
finished. total time: 0.006s
I think I bought this phone: https://forum.xda-developers.com/z2-force/help/bricking-support-questions-xt1789-06-t3995049
:silly:
Anyway, my hope is not gone!
Thank you
Benny

adb-fastboot_ver29.0.5
Attached is the latest adb/fastboot files pulled from androidsdk. It's weird that you can't even switch slots, so here is the latest files, just unzip to their own folder. Open folder, hold shift then right-click a blank area in the folder, open command window here. Try repeating the instructions in my last post and see if anything works this time around, use a 2.0 port if possible and use a port off the motherboard. Trivial it seems, but necessary for some. Double check the command fastboot --setactive="a,b, or other" could be "_a or _b" I don't use that command often so the syntax could be wrong, so try with or with the underscore_ or simply use 'other' w/o 'quotes' to switch slots. We're trying to get the slots as matched as possible so that if all else fails hopefully the lmsa tool will at least do a rescue on it. Right now I think you have bits and pieces of everything and lmsa sees it as something foreign or custom and won't touch it.

bennyschw said:
I think I bought this phone: https://forum.xda-developers.com/z2-force/help/bricking-support-questions-xt1789-06-t3995049
:silly:
Anyway, my hope is not gone!
Thank you
Benny
Click to expand...
Click to collapse
I thought you were being funny until I looked at the serial no. in both posts... it the same f'n phone. Flashed to pie, f'd up, rolled back to oreo, bootloader locked, all kinds of wrong. Since it was on pie before, you'll need pie to fix it. Depending on what version of pie was flashed, you might need to wait for an update to roll out so you have a new enough firmware to overwrite the nv values. So there's that.

Well, that how it is now. I'll let it sit for a while, maybe sonething changes or I have some new ideas
But I'm happy about every new suggestions from you.
Thanks for your help!
Benny

bennyschw said:
Well, that how it is now. I'll let it sit for a while, maybe sonething changes or I have some new ideas
But I'm happy about every new suggestions from you.
Thanks for your help!
Benny
Click to expand...
Click to collapse
Did you succeed benny?
I'm practically having the same problem.
but when I try to change the slot with the command "fastboot --set-active = b"
the error appears: fastboot: error: Device does not support slots

danyfenton said:
Did you succeed benny?
I'm practically having the same problem.
but when I try to change the slot with the command "fastboot --set-active = b"
the error appears: fastboot: error: Device does not support slots
Click to expand...
Click to collapse
The same situation here, I am stuck in the bootloader because it indicates "Flashing_lock", I cannot enter the operating system to unlock because it says that the device is corrupt, I cannot change the slot in Fastboot mode, I cannot flash a new ROM, Neither the same ROM or the old ROM ... What do you think about forcing the EDL state, to try to recover with blankflash? (If I already tried the blankflash commands and do not allow them in the Fastboot, I would have to damage the cell phone on purpose but I don't know how)

and you haven't achieved anything yet have you?
mine is still standing here.

Fastboot reason: fall-through from normal boot mode

Hey everyone, since i tried updating my moto z2 force att with a faulty cable and then using a working one through lenovo "smart" "assistant", whenever i turn it off or restart i get: Fastboot reason: fall-through from normal boot mode, after trying many things the only way i found to recover my phone was to run this command list from adb command promt:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot reboot​
I know that those commands are for installing a rom, but i was in a hurry and got away with it.
However i found that these commands are the needed to avoid losing all my data.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Please note that this is a temporary solution, if i turn off my phone i will have to run the commands again, which honestly i dont know what are they for .
If this helps someone, use it. If someone has a permanent solution, could you provide it? the bootloader cant be unlocked in the ATT phones as far as i know, couldnt find anything to help me on the internet.

If I understand you correctly, it sounds like whenever you boot or reboot you end up in fastboot. If that is the case then simply run this command in fastboot 'fastboot oem fb_mode_clear' w/o 'quotes'. Then 'fastboot reboot'. That should let you boot normally. If that isn't the problem then you need to explain more.

thanks gotta try that one out.
What happens is that when i restart or turn on my phone, it says that it cant be trusted and wont boot, after a while it goes to the screen that i mention (havent figured out how to upload images here) where it says fastboot reason of the tittle of my post. From there the only way to interact is through adb with the commands that i mention.

41rw4lk said:
If I understand you correctly, it sounds like whenever you boot or reboot you end up in fastboot. If that is the case then simply run this command in fastboot 'fastboot oem fb_mode_clear' w/o 'quotes'. Then 'fastboot reboot'. That should let you boot normally. If that isn't the problem then you need to explain more.
Click to expand...
Click to collapse
Hey i tried that one and no sucess only got this
https:// drive. google. com/ open?id= 1obn 0MW0qLBiMet9 -4oUwZVx X7j5UmT-Z​
but if i turn it off it returns to the screens below
http s:// drive. google. com/ o pen?i d= 1ICNS -p1ZMCzp qJE6wAVM OlMEhO 2UuDVw​and
htt ps: //d rive.go ogle .com/op en?id=1pfwLb JufMHPGS3klFw td6uWl1G gKIole​
From there if i run the commands that i previously said i get this and if i reboot, the phone starts correctly
https ://driv e.goog le.co m/ope n?id=1RS aGOQfbo VkIY4u1 nLAHA9GWib5UK gJg​
The rom that is in the adb folder is XT1789-04_NASH_ATT_8.0.0_OCXS27.109-47-20_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip, and i previously tried to install this before the lenovo smart software wasnt working at all. The results were the same only that i lost all my data.
If i try to run the lenovo smart assistant again and try to recover, it says that my phone is not supported, weird because that software caused all of this and the faulty cable :silly:

Are you sure you have an ATT phone? What is the model no. by the charger port? The thing is, ATT has a locked bootloader so the only thing you should be able to do is flash officially signed firmware that is either the same version or newer. That's it. Run the command 'fastboot getvar all' in bootloader mode and post your output.

41rw4lk said:
Are you sure you have an ATT phone? What is the model no. by the charger port? The thing is, ATT has a locked bootloader so the only thing you should be able to do is flash officially signed firmware that is either the same version or newer. That's it. Run the command 'fastboot getvar all' in bootloader mode and post your output.
Click to expand...
Click to collapse
Yes, its ATT, it has the logo at the back, its the XT1789-04, according to settings.
I ran the command that you said and i get this
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_att-316e620-190110
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224B9BNP
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 9CF79D1A
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 353311080575347
(bootloader) meid:
(bootloader) date: 07-24-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4077
(bootloader) iccid: 89014103270252580378
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_att/nash:8.0.0/OCXS2
(bootloader) ro.build.fingerprint[1]: 7.109-47-23/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.261.4.nash_att.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NUS_ATT
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g0f8e904 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue May 28 02:06:00 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_att-316e620-190110
(bootloader) git:xbl: MBM-3.0-nash_att-9869834-190110
(bootloader) gitmic: MBM-3.0-nash_att-9869834-190110
(bootloader) git:rpm: MBM-3.0-nash_att-b13e14f-190110
(bootloader) git:tz: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:hyp: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:devcfg: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:cmnlib: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:cmnlib64: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:keymaster: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:storsec: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) gitrov: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: att
(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: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.750s​
I used this tutorial to install it previously, and got the issue that im mentioning in my post
https://www.getdroidtips.com/att-moto-z2-force-stock-firmware/

Anyone got a solution yet?

Why don't you download the latest firmware for ATT and use the attached zip to manually flash your phone. Just extract your firmware into the utilities zip, make sure you're in bootloader mode, and run the flashall.
Latest firmware for ATT
https://mirrors.lolinet.com/firmwar...29_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip

Awesome! it woked, tanks!

41rw4lk said:
Why don't you download the latest firmware for ATT and use the attached zip to manually flash your phone. Just extract your firmware into the utilities zip, make sure you're in bootloader mode, and run the flashall.
Latest firmware for ATT
https://mirrors.lolinet.com/firmwar...29_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hi, recently the phone reboots and stays at bootloop at night when charging, do you have any idea why?
Also it boots itself and the bootloop happens sometimes, in some bootloops i would get a notification saying "Android System there is an internal problem with your device and may be unstable until you factory data reset" which i did and after sometime it started happening again (didnt do backup restore) the apps start failing without even opening them and google play services also fail.
any clue?
Im really tired of this phone but i want to sell it to afford another phone.

mau22975 said:
Hi, recently the phone reboots and stays at bootloop at night when charging, do you have any idea why?
Also it boots itself and the bootloop happens sometimes, in some bootloops i would get a notification saying "Android System there is an internal problem with your device and may be unstable until you factory data reset" which i did and after sometime it started happening again (didnt do backup restore) the apps start failing without even opening them and google play services also fail.
any clue?
Im really tired of this phone but i want to sell it to afford another phone.
Click to expand...
Click to collapse
Might try hitting bootloader and issuing fastboot -w to format user data. Though the culprit could be a failing battery. Might check your cable and/or power source.

41rw4lk said:
Might try hitting bootloader and issuing fastboot -w to format user data. Though the culprit could be a failing battery. Might check your cable and/or power source.
Click to expand...
Click to collapse
The weird thing is that i bought a turbocharger from amazon and i used it everyday, its supposed to be oem. But after that i started using my regular 1A charger and reboots are not that frequent. Also the moto battery mod may be a cause now that you point it. Today i didnt use it and no reboot...yet.
Could you explain more about hitting the bootloader and issuing fastboot? im not very familiar with those terms
Thank you very much!

mau22975 said:
The weird thing is that i bought a turbocharger from amazon and i used it everyday, its supposed to be oem. But after that i started using my regular 1A charger and reboots are not that frequent. Also the moto battery mod may be a cause now that you point it. Today i didnt use it and no reboot...yet.
Could you explain more about hitting the bootloader and issuing fastboot? im not very familiar with those terms
Thank you very much!
Click to expand...
Click to collapse
Some general moto flashing info
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

Moto Z2 Force T-Mobile branding -> flash to retail firmware won't work

Hi there,
I'm new to xda. Thanks for having me.
I am new to the whole topic of unlocking/flashing a mobile phone, since I did not see a real need for it until now.
What's the story:
I bought a new Motorola Moto Z2 Force (XT1789-04) on eBay. The phone was shipped from the US apparently (I live in Germany).
It has a T-Mobile branding pre-installed, which was not mentioned before and which I find terrible.
So I decided to flash the Z2 with a retail firmware to get rid of all those useless pre-installed apps.
I started reading a bit about how to do this. The first pages suggested to use RSD Lite with the latest motorola drivers and provided appropriate stock firmware.
I went into developers options on the phone, and allowed USB debugging. I started fastboot with "volume down" and power.
However, the phone is not recognized in RSD Lite. The list remains empty. I reinstalled the motorola driver multiple times, rebooting my Win10 PC as was suggested.
I also tried the universal ADB drivers. No change.
I then used the adb / fastboot cmd lines to check if something is amiss. And i found a couple of strange things:
Code:
fastboot getdev all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
[B](bootloader) secure: no[/B]
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: [XXXXXXXXXXX]
(bootloader) [B]cid: 0xDEAD[/B]
(bootloader) channelid: 0x00
(bootloader) uid: D7BF5C89
(bootloader) [B]securestate: engineering[/B]
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [XXXXXXXXXXX]
(bootloader) meid:
(bootloader) date: 01-23-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4272
(bootloader) iccid: 89148000003630606544
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-14-7/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.351.12.nash_tmo_c
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.08R NNS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g5b6c26aa-0177
(bootloader) kernel.version[1]: 2-g1e9c9a2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Fri Jul 5 12:49:00 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:pmic: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:hyp: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:devcfg: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:keymaster: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:storsec: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:prov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(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: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.119s
I am unable to get unlock data.
Code:
fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
finished. total time: 0.003s
Code:
fastboot flashing get_unlock_ability
...
(bootloader) use get_unlock_bootloader_nonce and web portal
(bootloader) .....motorola.com/unlockbootloader
OKAY [ 0.004s]
finished. total time: 0.005s
In the phone setup I also noticed, that "unlock bootloader" is greyed out. It states, the bootloader would already be unlocked.
Now I tried the unlock cmd in fastboot, since it should state something like already unlocked, but instead I get this message:
Code:
fastboot oem unlock
...
(bootloader) Unsupported on engineering phone
OKAY [ 0.001s]
finished. total time: 0.002s
Now I found this quite confusing, but I tried to flash TWRP, in case this might resolve the problems with "engineering mode" without quite knowing what that really implies.
I downloaded the latest TWRP for nash (Z2 Force) and tried to flash it over fastboot:
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (34224 KB)...
OKAY [ 0.081s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.085s
Now I am out of ideas.
Can anyone help me? Maybe start by explaining, why my phone doesn't just let me do the things I want...
Thanks!

12die4 said:
Hi there,
I'm new to xda. Thanks for having me.
I am new to the whole topic of unlocking/flashing a mobile phone, since I did not see a real need for it until now.
What's the story:
I bought a new Motorola Moto Z2 Force (XT1789-04) on eBay. The phone was shipped from the US apparently (I live in Germany).
It has a T-Mobile branding pre-installed, which was not mentioned before and which I find terrible.
So I decided to flash the Z2 with a retail firmware to get rid of all those useless pre-installed apps.
I started reading a bit about how to do this. The first pages suggested to use RSD Lite with the latest motorola drivers and provided appropriate stock firmware.
I went into developers options on the phone, and allowed USB debugging. I started fastboot with "volume down" and power.
However, the phone is not recognized in RSD Lite. The list remains empty. I reinstalled the motorola driver multiple times, rebooting my Win10 PC as was suggested.
I also tried the universal ADB drivers. No change.
I then used the adb / fastboot cmd lines to check if something is amiss. And i found a couple of strange things:
Code:
fastboot getdev all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
[B](bootloader) secure: no[/B]
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: [XXXXXXXXXXX]
(bootloader) [B]cid: 0xDEAD[/B]
(bootloader) channelid: 0x00
(bootloader) uid: D7BF5C89
(bootloader) [B]securestate: engineering[/B]
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [XXXXXXXXXXX]
(bootloader) meid:
(bootloader) date: 01-23-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4272
(bootloader) iccid: 89148000003630606544
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-14-7/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.351.12.nash_tmo_c
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.08R NNS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g5b6c26aa-0177
(bootloader) kernel.version[1]: 2-g1e9c9a2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Fri Jul 5 12:49:00 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:pmic: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:hyp: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:devcfg: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:keymaster: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:storsec: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:prov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(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: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.119s
I am unable to get unlock data.
Code:
fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
finished. total time: 0.003s
Code:
fastboot flashing get_unlock_ability
...
(bootloader) use get_unlock_bootloader_nonce and web portal
(bootloader) .....motorola.com/unlockbootloader
OKAY [ 0.004s]
finished. total time: 0.005s
In the phone setup I also noticed, that "unlock bootloader" is greyed out. It states, the bootloader would already be unlocked.
Now I tried the unlock cmd in fastboot, since it should state something like already unlocked, but instead I get this message:
Code:
fastboot oem unlock
...
(bootloader) Unsupported on engineering phone
OKAY [ 0.001s]
finished. total time: 0.002s
Now I found this quite confusing, but I tried to flash TWRP, in case this might resolve the problems with "engineering mode" without quite knowing what that really implies.
I downloaded the latest TWRP for nash (Z2 Force) and tried to flash it over fastboot:
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (34224 KB)...
OKAY [ 0.081s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.085s
Now I am out of ideas.
Can anyone help me? Maybe start by explaining, why my phone doesn't just let me do the things I want...
Thanks!
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Hi, the command reply is seen in the first code box.
Sorry, I mixed up the headlines. It's NOT "fastboot getdev all", but as you said "fastboot getvar all". My mistake. :cyclops:

12die4 said:
Hi, the command reply is seen in the first code box.
Sorry, I mixed up the headlines. It's NOT "fastboot getdev all", but as you said "fastboot getvar all". My mistake. :cyclops:
Click to expand...
Click to collapse
Does the device still boot normally?
Sent from my Moto E (4) using Tapatalk

Looks like you have an engineering phone, bootloader should already be unlocked. I haven't had any experience with an engineering phone so I don't know the limitations... if any.
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)

41rw4lk said:
Looks like you have an engineering phone, bootloader should already be unlocked. I haven't had any experience with an engineering phone so I don't know the limitations... if any.
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)
Click to expand...
Click to collapse
Correct getvar says securestate engineering
Sent from my perry_f using XDA Labs
---------- Post added at 01:22 AM ---------- Previous post was at 01:11 AM ----------
If you get twrp installed, make a complete backup.
Engineering devices have unique firmware, I think.
It may not behave like a consumer model.
Sent from my perry_f using XDA Labs

41rw4lk said:
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)
Click to expand...
Click to collapse
Thank! I will try to do that. I understand that you can Boot a remote (PC located) Boot Image with this command? Flashing TWRP via fastboot didn't however. Not sure why.

41rw4lk said:
Looks like you have an engineering phone, bootloader should already be unlocked. I haven't had any experience with an engineering phone so I don't know the limitations... if any.
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)
Click to expand...
Click to collapse
Great, fastboot boot twrp.img worked!
What do I do now? My idea was: Run "install" and try to flash the new Firmware via TWRP.
Therefore I need to copy the new img-file onto an sd-card and select it in TWRP as source. Right?
Or which procedure would you recommend?
sd_shadow said:
[/COLOR]If you get twrp installed, make a complete backup.
Engineering devices have unique firmware, I think.
It may not behave like a consumer model.
Click to expand...
Click to collapse
Thanks for the advice. I tried a backup with all boxes checked - there was a failure (error 255).
But when checking only firmware and bootloader, the backup worked fine.
Do I need the other options or are firmware and bootloader sufficient for my purposes? I'm not sure, what is actually overwritten when installing the stock firmware.

12die4 said:
Great, fastboot boot twrp.img worked!
What do I do now? My idea was: Run "install" and try to flash the new Firmware via TWRP.
Therefore I need to copy the new img-file onto an sd-card and select it in TWRP as source. Right?
Or which procedure would you recommend?
Thanks for the advice. I tried a backup with all boxes checked - there was a failure (error 255).
But when checking only firmware and bootloader, the backup worked fine.
Do I need the other options or are firmware and bootloader sufficient for my purposes? I'm not sure, what is actually overwritten when installing the stock firmware.
Click to expand...
Click to collapse
You want boot twrp, install twrp in booted twrp with a twrp.zip, then back up.
Sent from my ali using XDA Labs
---------- Post added at 05:02 AM ---------- Previous post was at 04:57 AM ----------
https://dl.twrp.me/nash/
Sent from my ali using XDA Labs

sd_shadow said:
You want boot twrp, install twrp in booted twrp with a twrp.zip, then back up.
Sent from my ali using XDA Labs
---------- Post added at 05:02 AM ---------- Previous post was at 04:57 AM ----------
https://dl.twrp.me/nash/
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hurra! Installing twrp worked now. Thanks!
How do I get to boot twrp now that it is installed locally? Do I still need to use the command "fastboot boot twrp.img" or is there a possibility without adb/fastboot protocol?
I was also able to create a backup of all partitions. I only deselected "Data (excl. storage)" in the options, since the phone was not actively used yet, so there shouldn't be any data that's relevant for backup.
Next I tried installing the new retail firmware ("NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"), but TWRP states the ZIP has an invalid file format.
Why is it not working? Is it an incorrect firmware after all?

12die4 said:
Hurra! Installing twrp worked now. Thanks!
How do I get to boot twrp now that it is installed locally? Do I still need to use the command "fastboot boot twrp.img" or is there a possibility without adb/fastboot protocol?
I was also able to create a backup of all partitions. I only deselected "Data (excl. storage)" in the options, since the phone was not actively used yet, so there shouldn't be any data that's relevant for backup.
Next I tried installing the new retail firmware ("NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"), but TWRP states the ZIP has an invalid file format.
Why is it not working? Is it an incorrect firmware after all?
Click to expand...
Click to collapse
You should be able to boot to twrp using bootloader recovery option.
Stock firmware is not twrp compatible.
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
You should be able to boot to twrp using bootloader recovery option.
Stock firmware is not twrp compatible.
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Ow, that sounds tricky. (tools that are no longer updated and might or might not work...)
For now, I tried to install LineageOS 17.1 on my Z2 Force.
Maybe there is no need to keep Retail Moto-Firmware after all...
However I have some issues with LineageOS. I will post them in the corresponding thread.
For now. Thanks a lot!