Develop Bugs

Moto Z2 Play hard-brick

Hi everybody.
I ask for any help to restore my smartphone.
The problem is:
That I accidentally uploaded someone else's backup, the "cid" section. Now I have a cid: 0xDEAD
An interesting case, after this recovery the bootloader locked. Status:
securestate: oem_locked
*verity-state: enforcing
And I can not unlock it He writes an error, I think it's because of the frp section that changes the last byte to 01. After setting the checkbox in the setting - for the developer - the factory unlock.
D: \ ADB> fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) validate header error: 55
(bootloader) 3A15880808988261 #
(bootloader) 5A5932323442425A5642004D6F746F205A320000 #
(bootloader) 9D6169D0A91A800175B1EDA6CADAE6D3FB144F98 #
(bootloader) 09FAAB8E000000000000000000000000
OKAY [0.103s]
finished. total time: 0.104s
D: \ ADB> fastboot oem unlock XBZQPOSESK3KL7XQRRFT
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) feature disabled
OKAY [0.007s]
finished. total time: 0.008s
I watched a lot of articles and videos on the web. And I found an interesting video, where on Moto x the 2nd generation. In this situation, the bootloader was unlocked, unlocked, i.e. after flashing and starting the phone, oem_unlocked has already been indicated on the screen. I wonder if it's possible to do this on Z2 play?
https://www.youtube.com/watch?v=aYjzD9WZum0
I was trying to flash a full firmware. I can download all the parts of the firmware, except: system, boot, recovery. oem.img
In recovery I also can not get, only fastboot.
When flashing different versions of the bootloader, the file names change when prompting fastboot getvar all. So the bootloader loads well. But I have on my smartphone's screen:
Start up failed:
Your device did not start up succeessfuly.
Use the sofrware Repair Assistent on your computer to repair your device.
Connect yor device to your omputer to get the Software Repair Assistant.
When loading bootloader.img
-keys-cid50_retru \ Windows> fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot: bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB) ...
OKAY [0.178s]
writing 'bootloader' ...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [0.550s]
finished. total time: 0.730s
All is well.
.
But here's an example of boot.img
-keys-cid50_retru \ Windows> fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot: boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB) ...
OKAY [0.514s]
writing 'boot' ...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.726s
If you look at the smartphone's screen in bootlaoder logs - Failed to verify hab image boot.

Here's what fastboot shows: getvar all:
D:\ADB>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C7
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY224BBZVB
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 1E28AD1500000000000000000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 351888080892816
(bootloader) meid:
(bootloader) date: 07-25-2017
(bootloader) sku: XT1710-09
(bootloader) battid: SNN5985A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/albus/albus:7.1.1/NPS26.1
(bootloader) ro.build.fingerprint[1]: 18-19/19:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.51.19.albus.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953P_23.33.07.34R ALBUS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g3b78496-0000
(bootloader) kernel.version[1]: 5-ge5590f6 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Fri Jun 30 23:09:12 CDT 20
(bootloader) kernel.version[4]: 17
(bootloader) sbl1.git: git=MBM-NG-VC0.C7-0-ge9cd975
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) devcfg.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) keymaster.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) cmnlib.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) prov.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.C7-0-gb6d4956
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.134s
I will be glad to any help. I can check any action on my smartphone.

Moto z2 play stuck in bootloader with no recovery.

Okay guys This stupid phone is doing my head in.
Bought the chinese version of Moto z2 Play. (XT1710-08)
Went to the TWRP website, downloaded the recover they said was compatible and it broke the phone. Twrp 3.2.3-0 addison.
Anyway. The phone wont boot into OS, and it wont boot into recovery.
Gets stuck on the MOTO screen when trying to boot into OS, and i get the Start Up Failed error when trying to go into recovery.
Can anybody link me to some tutorials or something or tell me how to fix this?
I wanted to put Oreo on this device.
Thanks in advance.
Nathan.

try this tut:
https://forum.xda-developers.com/z2-play/development/twrp-moto-z2-play-t3729531

I have the same problem
Mine also stuck in the Bootloader, every time boot normal, recovery, even charge to the wall outlet always go to the boot loader.
I already try many STOCK ROM to reflash using Fastboot Mode as the only tools that can run (The ADB Shell come up with no device)...
Always Failed to Flash Partition GPT.BIN
C:\mfastboot>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.125s
GETVAR ALL DATA
C:\mfastboot>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.CD
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY22XXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc7
(bootloader) uid: 8006F83500000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 35XXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 07-13-2017
(bootloader) sku: XT1710-09
(bootloader) carrier_sku:
(bootloader) battid: SNN5985A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g046197e (hud
(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]: Thu Aug 2 07:47:40 CDT 2018
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: git=bd19194
(bootloader) tz.git: git=5fefee4-dirty
(bootloader) devcfg.git: git=5fefee4-dirty
(bootloader) keymaster.git: git=5fefee4-dirty
(bootloader) cmnlib.git: git=5fefee4-dirty
(bootloader) cmnlib64.git: git=5fefee4-dirty
(bootloader) prov.git: git=5fefee4-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.CD-0-g361b83a
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retid
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.125s
Please somebody help with this problem...

[Help Thread][Moto G5](2017) Ask Any Question, Noob Friendly

Moto G5
XT1670 (2GB RAM 16GB Unlocked) Latin America, Canada
XT1671 (Dual-Sim 2GB RAM 32GB) Latin America
XT1672 (Dual-Sim 2GB RAM 32GB) Brazil
XT1675 (2GB RAM 16GB) Saudi Arabia, United Arab Emirates, Israel.
XT1676 (Dual-Sim 2GB RAM 16GB) Australia, Europe, Japan, New Zealand.
XT1676 (Dual-Sim 3GB RAM 16GB) Europe/Turkey
XT1677 (Dual-Sim) India
​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
[/CENTER]
List of supporters...
...
...
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
Frequently Asked Questions for Motorola Moto G5
[Index]Motorola Flashing Utilities, Firmware, and more
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
​

Specs
https://www.phonearena.com/phones/Motorola-Moto-G5_id10421/fullspecs
https://www.phonemore.com/models/motorola/moto-g5/

Broken Firmware
Hi there, I hope that somebody here can help me with my issue.
I have a Moto G5 XT1675 (Bootloader locked), which recently has completely stopped working.
The issue
Whenever I boot into the phone I get the following error (and whenever I try and load Recovery Mode, Factory Mode, BP Tools, QCOM):
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode [Secure]
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validaton, backup to fastboot
Fastboot Reason: Fall-though from normal boot mode
(Yes the spelling of validation is wrong on the screen).
Whenever I plug into a charging cable I get the following error:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode [Secure]
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validaton, backup to fastboot
Fastboot Reason: Fall-though from charger boot mode
Other Data
(IMEI + SERIAL Removed):
Code:
> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno:
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: 313A7B0200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Fall-through from charger boot mode
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 02-07-2018
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 5 0: 9:16 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-19-4-2/3447de:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.301.2.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_46.42.02.75R CEDRIC_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gea366bb-0001
(bootloader) kernel.version[1]: 6-g6e15bdb ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Mon Mar
(bootloader) kernel.version[3]: 4 18:13:35 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=3f87a46
(bootloader) devcfg.git: git=3f87a46
(bootloader) keymaster.git: git=3f87a46
(bootloader) cmnlib.git: git=3f87a46
(bootloader) cmnlib64.git: git=3f87a46
(bootloader) prov.git: git=3f87a46
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: protected (277)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.081s
What I've tried to fix it
Rescue and Smart Assistant
I have tried to use Rescue and Smart Assistant to fix this phone, because that is what was suggest by the phone, whenever I start the repair process, it just gets to 68% and then fails.
The file it uses for the firmware is:
Code:
BUILD REQUEST INFO:
SW Version: cedric-user 8.1.0 OPP28.85-19-4-2 3447de release-keysM8937_46.42.02.75R
MBM Version: B8.31
Modem Version: M8937_46.42.02.75R
FSG Version: FSG-8937-02.65.34
Build Fingerprint: motorola/cedric/cedric:8.1.0/OPP28.85-19-4-2/3447de:user/release-keys
CQATest App Version: 6.0.6
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 28.301.2.cedric.retail.en.US
Model Number: Moto G (5)
Android Version: 8.1.0
Baseband Version: M8937_46.42.02.75R
Build Id: OPP28.85-19-4-2
SW Display Build ID: OPP28.85-19-4-2
Build Date: Mon Mar 4 17:31:16 CST 2019
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.28.301.2.cedric.retail.en.US
Version when read from CPV: cedric-user 8.1.0 OPP28.85-19-4-2 3447de release-keys
AB Update Enabled: False
Full Treble Enabled: False
Flashing Firmware Manually
Whenever I try and flash firmware, the partition table can never be written as I receive the following errors (my phone will also not let me fb_mode_set):
Code:
>(m)fastboot flash partition gpt.bin
(bootloader) is-logical:partition: not found
Sending 'partition' (45 KB) OKAY [ 0.185s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
Doing the same on linux gives a similar error:
Code:
$fastboot flash partition gpt.bin
(bootloader) is-logical:partition: not found
Sending 'partition' (45 KB) OKAY [ 0.185s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
fastboot: error: Command failed
Unlocking the bootloader
Sadly the phone requires you to go into the android and change a switch in the settings to unlock the bootloader, but i can't do this because I can't get into android..
Checking the storage chip can still be changed
Code:
> fastboot erase userdata
Erasing 'userdata' OKAY [ 0.055s]
Finished. Total time: 0.067s
Loading TWRP instead of flashing it
Code:
> fastboot boot .\twrp-3.5.2_9-0-cedric.img
Sending 'boot.img' (15822 KB) OKAY [ 0.517s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
Hard Brick
One of the last ditch attempts I tried was to hardbrick the phone, sadly due to the fact the bootloader is locked, you can't flash old firmware or broken firmware.. This meant it just booted into the same area and never went into either EDL or SD CARD mode
EDL Cable
Following this image I made my own EDL cable from an Old samsung one, but I could not get into EDL mode because the phone always boots into fastboot whenever it is plugged into a charger, so I could never get into EDL mode :///
I hope that somebody can find a way to help me, because I have tried a lot and nothing seems to work.. Even more so, whenever you search online for anyone with a similar issue, the solution is always to send it back to the manufacturer :// And one guide for a different moto phone said to try and get into EDL mode, but I could not get into this mode on my phone ://
Thanks very much in advance
Stay Safe,
- Jim
P.S. Sorry I don't know if this is the right place to post this My apologies if this is the wrong place to reply

RainbowOblivion said:
Broken Firmware
Hi there, I hope that somebody here can help me with my issue.
I have a Moto G5 XT1675 (Bootloader locked), which recently has completely stopped working.
The issue
Whenever I boot into the phone I get the following error (and whenever I try and load Recovery Mode, Factory Mode, BP Tools, QCOM):
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode [Secure]
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validaton, backup to fastboot
Fastboot Reason: Fall-though from normal boot mode
(Yes the spelling of validation is wrong on the screen).
Whenever I plug into a charging cable I get the following error:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode [Secure]
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validaton, backup to fastboot
Fastboot Reason: Fall-though from charger boot mode
Other Data
(IMEI + SERIAL Removed):
Code:
> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno:
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: 313A7B0200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Fall-through from charger boot mode
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 02-07-2018
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 5 0: 9:16 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-19-4-2/3447de:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.301.2.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_46.42.02.75R CEDRIC_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gea366bb-0001
(bootloader) kernel.version[1]: 6-g6e15bdb ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Mon Mar
(bootloader) kernel.version[3]: 4 18:13:35 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=3f87a46
(bootloader) devcfg.git: git=3f87a46
(bootloader) keymaster.git: git=3f87a46
(bootloader) cmnlib.git: git=3f87a46
(bootloader) cmnlib64.git: git=3f87a46
(bootloader) prov.git: git=3f87a46
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: protected (277)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.081s
What I've tried to fix it
Rescue and Smart Assistant
I have tried to use Rescue and Smart Assistant to fix this phone, because that is what was suggest by the phone, whenever I start the repair process, it just gets to 68% and then fails.
The file it uses for the firmware is:
Code:
BUILD REQUEST INFO:
SW Version: cedric-user 8.1.0 OPP28.85-19-4-2 3447de release-keysM8937_46.42.02.75R
MBM Version: B8.31
Modem Version: M8937_46.42.02.75R
FSG Version: FSG-8937-02.65.34
Build Fingerprint: motorola/cedric/cedric:8.1.0/OPP28.85-19-4-2/3447de:user/release-keys
CQATest App Version: 6.0.6
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 28.301.2.cedric.retail.en.US
Model Number: Moto G (5)
Android Version: 8.1.0
Baseband Version: M8937_46.42.02.75R
Build Id: OPP28.85-19-4-2
SW Display Build ID: OPP28.85-19-4-2
Build Date: Mon Mar 4 17:31:16 CST 2019
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.28.301.2.cedric.retail.en.US
Version when read from CPV: cedric-user 8.1.0 OPP28.85-19-4-2 3447de release-keys
AB Update Enabled: False
Full Treble Enabled: False
Flashing Firmware Manually
Whenever I try and flash firmware, the partition table can never be written as I receive the following errors (my phone will also not let me fb_mode_set):
Code:
>(m)fastboot flash partition gpt.bin
(bootloader) is-logical:partition: not found
Sending 'partition' (45 KB) OKAY [ 0.185s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
Doing the same on linux gives a similar error:
Code:
$fastboot flash partition gpt.bin
(bootloader) is-logical:partition: not found
Sending 'partition' (45 KB) OKAY [ 0.185s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
fastboot: error: Command failed
Unlocking the bootloader
Sadly the phone requires you to go into the android and change a switch in the settings to unlock the bootloader, but i can't do this because I can't get into android..
Checking the storage chip can still be changed
Code:
> fastboot erase userdata
Erasing 'userdata' OKAY [ 0.055s]
Finished. Total time: 0.067s
Loading TWRP instead of flashing it
Code:
> fastboot boot .\twrp-3.5.2_9-0-cedric.img
Sending 'boot.img' (15822 KB) OKAY [ 0.517s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
Hard Brick
One of the last ditch attempts I tried was to hardbrick the phone, sadly due to the fact the bootloader is locked, you can't flash old firmware or broken firmware.. This meant it just booted into the same area and never went into either EDL or SD CARD mode
EDL Cable
Following this image I made my own EDL cable from an Old samsung one, but I could not get into EDL mode because the phone always boots into fastboot whenever it is plugged into a charger, so I could never get into EDL mode :///
I hope that somebody can find a way to help me, because I have tried a lot and nothing seems to work.. Even more so, whenever you search online for anyone with a similar issue, the solution is always to send it back to the manufacturer :// And one guide for a different moto phone said to try and get into EDL mode, but I could not get into this mode on my phone ://
Thanks very much in advance
Stay Safe,
- Jim
P.S. Sorry I don't know if this is the right place to post this My apologies if this is the wrong place to reply
Click to expand...
Click to collapse
My guess would be the phone had the bootloader unlocked and someone has re-locked it.
Either this process was done wrong or the phone has tried to do an ota update whilst having unsigned firmware and a locked bootloader.
As the bootloader is locked there's no way of flashing firmware.
All firmware I've seen that you download have unsigned boot.img - if you relocked the bootloader using this you're asking for trouble which is why you should never relock the bootloader.
I would say your only solution is a motherboard replacement unless you have specialist hardware/software like a jtag to soldier connections directly onto the main board to flash firmware onto it (note a jtag costs more than this phone)

Hello guys
How to enter edl mode on moto g5?

Victor616 said:
Hello guys
How to enter edl mode on moto g5?
Click to expand...
Click to collapse
Is the bootloader locked?

sd_shadow said:
Is the bootloader locked?
Click to expand...
Click to collapse
No. Is unlocked

Boa tarde a todos. sou novato nesta área porém fiz o desbloqueio do bootloader, instalei o TWRP e tbm está com o root desbloqueado no MOTO G5 XT 1676 android 7. eu quero a principio modificar o rom dele, qual o passo seguinte a fazer. Se colocar o Lineage já muda alguma coisa?

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!

XT1922-2 JETER softbricked (newbie)

Hi. I've unlocked my phone for flashing and tried to install different ROMs, but nothing works.
My device is XT1922-2 JETER and I thought I'm having issues because I tried to install aljeter (as I can't find any jeter for XT1922-2..)
I tried to install different ROMs from TWRP, and even if it didn't give me any errors my phone was keeping loading into bootloader. Tried to use "fastboot oem fb_mode_clear" command but it didn't help.
Help me please, as I have no ideas what to do next and how to fix it. I don't know how to leave bootloop and make phone to load system.

Here's all the variables if that's helpful:
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-aljeter_retail-b1f322d35c1-2
(bootloader) version-bootloader[1]: 00404
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZL4223V3D5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 3572CA9F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 08-29-2018
(bootloader) sku: XT1922-2
(bootloader) carrier_sku: XT1922-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 5 11:34:57 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter_n/aljeter_n:9/PPP
(bootloader) ro.build.fingerprint[1]: S29.55-35-18-7/6a0d0:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.7.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: M8937_34.42.05.98R JETER_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g3e480e17e11
(bootloader) kernel.version[1]: f-04280-g407726838ebf ([email protected]
(bootloader) kernel.version[2]: 8) (gcc version 4.9.x 20150123 (prerelea
(bootloader) kernel.version[3]: se) (GCC) ) #1 SMP PREEMPT Sat Apr 4 12:
(bootloader) kernel.version[4]: 24:37 CDT 2020
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-0d2031d6b9-200404
(bootloader) rpm.git: MBM-2.1-aljeter_retail-af31f6ae-200404
(bootloader) tz.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) prov.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) aboot.git: MBM-2.1-aljeter_retail-b1f322d35c1-200404
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: eegb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.152s
Click to expand...
Click to collapse

xt123xt said:
Hi. I've unlocked my phone for flashing and tried to install different ROMs, but nothing works.
My device is XT1922-2 JETER and I thought I'm having issues because I tried to install aljeter (as I can't find any jeter for XT1922-2..)
I tried to install different ROMs from TWRP, and even if it didn't give me any errors my phone was keeping loading into bootloader. Tried to use "fastboot oem fb_mode_clear" command but it didn't help.
Help me please, as I have no ideas what to do next and how to fix it. I don't know how to leave bootloop and make phone to load system.
Click to expand...
Click to collapse
The model XT1922-2 is ALJETER , try to install Stock by fastboot from this link you can get it
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Ruben8ap said:
The model XT1922-2 is ALJETER , try to install Stock by fastboot from this link you can get it
Click to expand...
Click to collapse
Thank you for your reply.
It gave me an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system aljeter.zip
target reported max download size of 535822336 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 411641469 is not a multiple of the block size 4096
sending sparse 'system' 1/3 (523260 KB)...
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
OKAY [ 17.139s]
writing 'system' 1/3...
(bootloader) Invalid sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.145s
Click to expand...
Click to collapse

Try these https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETEU/

I tried, didn't work.
In the variables it says JETER.
(bootloader) product: jeter
(bootloader) board: jeter
I suppose XT1922-2 JETER could be a version which is exclusive to the UK.

xt123xt said:
I tried, didn't work.
In the variables it says JETER.
(bootloader) product: jeter
(bootloader) board: jeter
I suppose XT1922-2 JETER could be a version which is exclusive to the UK.
Click to expand...
Click to collapse
Download this file --> https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Then you open the CMD and put in fastboot devices and the phone code should appear, of course the phone should already be in fastboot mode for that moment.
If everything is in order you should copy these commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Just select all then copy and paste them into the CMD and the stock installation process will start :fingers-crossed:

I suppose you've saved my phone. Thank you very much!

Hi, I carried out the instruction as given above by Ruben8ap, on my XT1922-2 Aljeter Moto G6 Play phone, and have recovered my phone, so I can boot into the OS, but I have lost access to Fastboot and TWRP, etc. So, I now have a phone that is stuck with this OS and no way of gaining root access or anything else. My bootloader says AP Fastboot Flash Mode (Secure). I cannot flash anything from the stock recovery on the SD card. Can anyone advise how I can get out of this state?