Develop Bugs

Moto Z2 Play Italy XT1710-09 firmware gpt error

Hello to all and thank you in advance for your time.
I'm in this situation.
I wanted to try the Lineage Unofficial Rom so i did it all, unlocked the bootloader, installed TWRP and all was good but in the end after a week i thought to come back to the stock.
Now i have this problem. Probably i can't find the right Stock Rom for my Z2 because i can't receive OTA update. I tried many different roms, the problem is that i can't receive the security patch and the last working rom that i found has the 1 December 2017 update.
When i flash via fastboot, i have always this message about GPT:
C:\adb\alb>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.090s
so i guess the problem is that even i flash a working rom compatible with my XT1710-9, the partition table is wrong and that's why i can't receive OTA.
last thing, i tried to flash the last BLUR_VERSION Ota update from Junior but TWRP says:
'Flashing'
Installing zip file '/sdcard/Blur_Version.26.251.2.albus.retail.en.US.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:has_legacy_properties: Found legacy property match!
I:Legacy property environment initialized.
installing gptupgrade updater extensions
file_contexts.bin is taken from /file_contexts.bin
Mount command parameters gotten in updater script
mount point :/oem location: /dev/block/bootdevice/by-name/oem , file system type :ext4
secontext for the mount point /oem is ubject_remfs:s0
Source: motorola/albus/albus:7.1.1/NPS26.118-19-1/2:user/release-keys
Target: motorola/albus/albus:7.1.1/NPSS26.118-19-1-2/3:user/release-keys
Verifying current system...
Source: motorola/albus/albus:7.1.1/NPS26.118-19-1/2:user/release-keys
Target: motorola/albus/albus:7.1.1/NPSS26.118-19-1-2/3:user/release-keys
Verifying current system...
script aborted: E3002: Package expects build thumbprint of 7.1.1/NPSS26.118-19-1-2/3:user/release-keys or 7.1.1/NPS26.118-19-1/2:user/release-keys; this device has 7.1.1/NPSS26.118-19-14/16:user/release-keys.
E3002: Package expects build thumbprint of 7.1.1/NPSS26.118-19-1-2/3:user/release-keys or 7.1.1/NPS26.118-19-1/2:user/release-keys; this device has 7.1.1/NPSS26.118-19-14/16:user/release-keys.
error: 3002
Updater process ended with ERROR: 7
I'm asking for two solutions:
1) Does Someone have the right Stock rom for my Device? (XT1710-09 TIM-7.1.1/NPSS26.118-19-14/16?)
2) Does Someone have the last BLUR_Version OTA (March 18) for my device?
thank you for your help

1- NEVER install OTA with TWRP. You need Stock Recovery to install OTA. TWRP is a custom recovery.
2- Install Stock Firmware for you device via Fastboot.
https://androidfilehost.com/?fid=817906626617949781

Good day to you, you need to flush rom via RSD with the latest update here: http: //motozbrasil.blogspot.com/2017/09/firmware-moto-z-play-xt1710-07-firmware.html? M = 1

Thank you guys ill try soon to do it!!! Have a nice day!

big problem
ok now i have another big problem, i flashed the rom of your link junior via fastboot and ok it works. The big problem is that i cannot enter in the recovery mode, no way! It rimains the android logo with the red signal and that's all. Tried power button and vol up but nothing!! help help help!! ahah thanks again!

freddie84 said:
ok now i have another big problem, i flashed the rom of your link junior via fastboot and ok it works. The big problem is that i cannot enter in the recovery mode, no way! It rimains the android logo with the red signal and that's all. Tried power button and vol up but nothing!! help help help!! ahah thanks again!
Click to expand...
Click to collapse
You flashed Stock including recovery, which is what you saw. You need to go to fastboot and flash TWRP from there.

rom version?
Hi freddie84, I have the same model. Were you able to find the stock rom for this model? Or did you use the one suggested by junior passos? (ALBUS_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) That one appears to be for a different version.
Thanks!

SebaBaez said:
Hi freddie84, I have the same model. Were you able to find the stock rom for this model? Or did you use the one suggested by junior passos? (ALBUS_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) That one appears to be for a different version.
Thanks!
Click to expand...
Click to collapse
I found many here
https://firmware.center/firmware/Motorola/Moto Z2 Play/Stock/
Click to expand...
Click to collapse
And try ALBUS_NPSS26.118-19-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
My model is 1710-09 too. many FAILED errors while flash (click to show) but it should work. Update via OTA fine.
Just one problem, bootloader is still unlocked.
Hope it can help u.
D:\Dev\mfastboot>mfastboot flash dsp adspso.bin
target max-sparse-size: 256MB
sending 'dsp' (16384 KB)...
OKAY [ 0.350s]
writing 'dsp'...
OKAY [ 0.210s]
finished. total time: 0.560s
D:\Dev\mfastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (2192 KB)...
OKAY [ 0.060s]
writing 'logo'...
OKAY [ 0.113s]
finished. total time: 0.175s
D:\Dev\mfastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.382s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.333s]
finished. total time: 0.715s
D:\Dev\mfastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (20580 KB)...
OKAY [ 0.470s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.420s]
finished. total time: 0.890s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262142 KB)...
OKAY [ 5.840s]
writing 'system'...
OKAY [ 2.657s]
sending sparse 'system' (254988 KB)...
OKAY [ 5.703s]
writing 'system'...
OKAY [ 2.383s]
finished. total time: 16.583s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (261720 KB)...
OKAY [ 5.927s]
writing 'system'...
OKAY [ 2.883s]
sending sparse 'system' (235451 KB)...
OKAY [ 5.242s]
writing 'system'...
OKAY [ 1.971s]
finished. total time: 16.143s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (250755 KB)...
OKAY [ 5.617s]
writing 'system'...
OKAY [ 2.280s]
sending sparse 'system' (249116 KB)...
OKAY [ 5.646s]
writing 'system'...
OKAY [ 2.894s]
sending sparse 'system' (17572 KB)...
OKAY [ 0.396s]
writing 'system'...
OKAY [ 0.170s]
finished. total time: 17.003s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (252175 KB)...
OKAY [ 5.637s]
writing 'system'...
OKAY [ 2.203s]
sending sparse 'system' (254544 KB)...
OKAY [ 5.667s]
writing 'system'...
OKAY [ 2.063s]
sending sparse 'system' (13700 KB)...
OKAY [ 0.299s]
writing 'system'...
OKAY [ 0.130s]
finished. total time: 16.010s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (259627 KB)...
OKAY [ 5.795s]
writing 'system'...
OKAY [ 2.333s]
sending sparse 'system' (260620 KB)...
OKAY [ 5.823s]
writing 'system'...
OKAY [ 2.237s]
finished. total time: 16.188s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (253704 KB)...
OKAY [ 5.770s]
writing 'system'...
OKAY [ 2.806s]
sending sparse 'system' (250087 KB)...
OKAY [ 5.583s]
writing 'system'...
OKAY [ 2.317s]
sending sparse 'system' (17072 KB)...
OKAY [ 0.390s]
writing 'system'...
OKAY [ 0.163s]
finished. total time: 17.039s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (230784 KB)...
OKAY [ 5.127s]
writing 'system'...
OKAY [ 1.958s]
sending sparse 'system' (45248 KB)...
OKAY [ 0.995s]
writing 'system'...
OKAY [ 0.380s]
finished. total time: 8.470s
D:\Dev\mfastboot>mfastboot flash oem oem.img
target max-sparse-size: 256MB
sending 'oem' (232919 KB)...
OKAY [ 4.952s]
writing 'oem'...
OKAY [ 2.041s]
finished. total time: 6.995s
D:\Dev\mfastboot>mfastboot erase carrier
erasing 'carrier'...
OKAY [ 0.080s]
finished. total time: 0.080s
D:\Dev\mfastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
D:\Dev\mfastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 4.750s]
finished. total time: 4.750s
D:\Dev\mfastboot>mfastboot erase DDR
erasing 'DDR'...
OKAY [ 0.010s]
finished. total time: 0.010s
D:\Dev\mfastboot>mfastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
D:\Dev\mfastboot>mfastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.010s]
finished. total time: 0.010s
D:\Dev\mfastboot>mfastboot oem lock
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.020s]
finished. total time: 0.020s
D:\Dev\mfastboot>mfastboot flash oem oem.img
target max-sparse-size: 256MB
sending 'oem' (232919 KB)...
OKAY [ 4.946s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.016s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262142 KB)...
OKAY [ 5.844s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.924s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (261720 KB)...
OKAY [ 5.917s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.952s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (250755 KB)...
OKAY [ 5.584s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.614s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (252175 KB)...
OKAY [ 5.631s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.651s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (259627 KB)...
OKAY [ 5.808s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.828s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (253704 KB)...
OKAY [ 5.777s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.817s
D:\Dev\mfastboot>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (230784 KB)...
OKAY [ 5.140s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.150s
D:\Dev\mfastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.369s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.549s
D:\Dev\mfastboot>mfastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.010s]
finished. total time: 0.010s
D:\Dev\mfastboot>mfastboot reboot
rebooting...
finished. total time: 0.010s
D:\Dev\mfastboot>mfastboot devices
D:\Dev\mfastboot>
Click to expand...
Click to collapse

Hello, I also have the XT1710-09 Tim ITA version, Were you able to install the update?

Hello guys, I have a moto z2 play xt1710-09, there is a problem, it's written on all sites that this dual SIM product but for me is a single SIM card, what's up? Will it upgrade for this model?

Moto Z2 Play not flashable even with unlocked bootloader (XT1701-01)

Hallo all,
I seem to have a slight issue with being able to flash ROMs or even TWRP on my Moto Z2 Play. I have been trying various things the past couple weeks to get this to work, but to no avail- it won't even boot into the OS or Recovery now.
This is what happening:
[email protected]:/usr/local/bin$ fastboot -v flash partition gpt.bin
fastboot: verbose: target reported max download size of 534773760 bytes
Sending 'partition' (45 KB)
OKAY [ 0.044s]
Writing 'partition'
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
Finished. Total time: 0.132s
[email protected]:/usr/local/bin$ fastboot -v boot twrp-3.2.1-1-addison.img
Downloading 'boot.img'
OKAY [ 0.383s]
booting
FAILED (remote: '')
Finished. Total time: 1.010s
And since it doesn't boot and I cannot seem to flash .img files to the thing, I then tried erasing partitions to get around this and this is what it outputted:
[email protected]:/usr/local/bin$ fastboot erase /data/media
Erasing '/data/media' (bootloader) Permission denied
FAILED (remote: '')
Finished. Total time: 0.062s
[email protected]:/usr/local/bin$ fastboot erase /system
Erasing '/system' (bootloader) Permission denied
FAILED (remote: '')
Finished. Total time: 0.052s
[email protected]:/usr/local/bin$ fastboot -v erase /data/media
Erasing '/data/media'
(bootloader) Permission denied
FAILED (remote: '')
Finished. Total time: 0.056s
[email protected]:/usr/local/bin$ fastboot -v erase /system
Erasing '/system'
(bootloader) Permission denied
FAILED (remote: '')
Finished. Total time: 0.056s
[email protected]:/usr/local/bin$ fastboot -v erase /cache
Erasing '/cache'
(bootloader) Permission denied
FAILED (remote: '')
Finished. Total time: 0.050s
I've search `round and I can't seem to find anything pertinent to fix the problem. I also fear that I may have bricked the phone. So any help y'all could give would be appreciated; if more info is needed, just let me know.

Bricked MOTO G5(XT1676) stucked at fastboot menu

hELLO..
I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from twrp recovery and tried to install the same software again but it gave me the error at the end ..what should I know now to fix the mobile knowing that when i try to select recoverymode it tells me ersing and then takes m back to fastboot
note the first time i just opened a bat file with the software that installed the software automatically..
the bat file told me that
<bootloader> slot-count not found
<bootloader> slot suffixes not found
<bootloader>has-slot:fsg not found

Flash this firmware https://drive.google.com/file/d/1cESQyuRpeUAmmEn67_to0sQ0KLhkMnWM/view (Oreo 8.1, February 2019 security patch) using fastboot and commands below. All the data in the internal storage of the phone will be erased.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

Hi. Mine G5 is bricked as well.
When I`m trying to do what u said Andrej I got that:
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Any ideas?

pablito1984 said:
Hi. Mine G5 is bricked as well.
When I`m trying to do what u said Andrej I got that:
Any ideas?
Click to expand...
Click to collapse
The firmware you are trying to flash is too old hense the security downgrade error
You must use firmware that is equal to or newer than what was previously flashed on it
Firmware available at
https://mirrors.lolinet.com/firmware/moto/cedric/official/

TheFixItMan said:
The firmware you are trying to flash is too old hense the security downgrade error
You must use firmware that is equal to or newer than what was previously flashed on it
Firmware available at
Click to expand...
Click to collapse
Thank you for your reply.
I`ve downloaded XT1675_CEDRIC_RETGB_SS_8.1.0_OPPS28.85-13-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
as my phone model is XT1675.
I don`t know why, but when I`m trying to put fastboot oem fb_mode_set and it gives me that error

pablito1984 said:
Thank you for your reply.
I`ve downloaded XT1675_CEDRIC_RETGB_SS_8.1.0_OPPS28.85-13-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
as my phone model is XT1675.
I don`t know why, but when I`m trying to put fastboot oem fb_mode_set and it gives me that error
Click to expand...
Click to collapse
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)

TheFixItMan said:
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
Click to expand...
Click to collapse
Thanks for explaining me that
I`ve downloaded now CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And this time it`s not saying anything about downgrade, but I got this:
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logical: partition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse

pablito1984 said:
Thanks for explaining me that
I`ve downloaded now CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And this time it`s not saying anything about downgrade, but I got this:
Click to expand...
Click to collapse
I presume you can get into the bootloader without using a sdcard for a hard bricked device
If so skip gpt and bootloader parts of the firmware - these don't need to be flashed unless your phone was hard bricked (just get a red flashing led if mmcblk0 sdcard not inserted)
Also make sure you have the Motorola drivers installed and that you are using the latest fastboot drivers from the android sdk

TheFixItMan said:
I presume you can get into the bootloader without using a sdcard for a hard bricked device
If so skip gpt and bootloader parts of the firmware - these don't need to be flashed unless your phone was hard bricked (just get a red flashing led if mmcblk0 sdcard not inserted)
Also make sure you have the Motorola drivers installed and that you are using the latest fastboot drivers from the android sdk
Click to expand...
Click to collapse
Yes. I can get into bootloader, but I can`t do anything over there except restarting and checking logs.
After checking the logs I can see :
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 Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Last time flashing failed
USB Connected
failed to validate recovery iumage
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
Click to expand...
Click to collapse
Tried to use Lenovo Moto smart assistant to fix it, but it doesn`t see the device.
I`ve got all drivers, sdk, etc.
When tried to use fastboot I got this:
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.170s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.331s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2242 KB) OKAY [ 0.240s]
Writing 'logo' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.689s]
Writing 'boot' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.694s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.688s]
Writing 'dsp' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (148900 KB) OKAY [ 4.969s]
Writing 'oem' (bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (256537 KB) OKAY [ 8.462s]
Writing 'system' (bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256653 KB) OKAY [ 8.529s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (257978 KB) OKAY [ 8.446s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (260705 KB) OKAY [ 8.488s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (257421 KB) OKAY [ 8.464s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (257865 KB) OKAY [ 8.506s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (252667 KB) OKAY [ 8.402s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (253700 KB) OKAY [ 8.409s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (250301 KB) OKAY [ 8.271s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (66366 KB) OKAY [ 2.329s]
Writing 'modem' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst1
Erasing 'modemst1' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst2
Erasing 'modemst2' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2956 KB) OKAY [ 0.258s]
Writing 'fsg' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase cache
Erasing 'cache' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase userdata
Erasing 'userdata' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase customize
Erasing 'customize' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase clogo
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot oem fb_mode_clear
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
Click to expand...
Click to collapse

pablito1984 said:
Yes. I can get into bootloader, but I can`t do anything over there except restarting and checking logs.
After checking the logs I can see :
Tried to use Lenovo Moto smart assistant to fix it, but it doesn`t see the device.
I`ve got all drivers, sdk, etc.
When tried to use fastboot I got this:
Click to expand...
Click to collapse
Either your setup is wrong - try another pc USB cable etc or you have a motherboard fault & need to replace it

TheFixItMan said:
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
Click to expand...
Click to collapse
im having the same issue with moto e5play xt1921-1 i dont know what the latest fw is

ghettozo said:
im having the same issue with moto e5play xt1921-1 i dont know what the latest fw is
Click to expand...
Click to collapse
Neither do i as I don't own your phone
Go to your own phone forum or Google for firmware for your device
To flash gpt and bootloader it must be the same or newer than version on device and an unlocked bootloader to avoid permissions errors especially if has been unlocked before

TheFixItMan said:
Neither do i as I don't own your phone
Go to your own phone forum or Google for firmware for your device
To flash gpt and bootloader it must be the same or newer than version on device and an unlocked bootloader to avoid permissions errors especially if has been unlocked before
Click to expand...
Click to collapse
thanks. yes im using the forum here and google but im having issues
thankyou\

Moto z2 force Flash Stock Wifi Issues x1789-04 tmobile

Notice there is a huge issue with the modem in another post https://forum.xda-developers.com/z2-force/help/0-imei-pie-xt-1789-03-sprint-t3957851 please stay tune
I am having an issue with Wifi, I attempted to update lineage os 17.1 did process to clean flash. After did all the process provided with the guide of lineage os official wiki of my moto Z2 when it booted it got stuck on the loop lineage logo for over 15 minutes than usual with it configures. I decided to flash it back to stock, did a script for it of course(using an example of rcmaehl here XDA) due to long periods test fail I was able to boot it in stock oreo, but when I got to set it up, it does not show any wifi and not even data of carrier. went to the bootloader again to notice that broadband is unknown(not found). long story short I have a half soft brick phone. Any idea and suggestion.
The script I was able to make flash to stock oreo:
Code:
@echo off
adb reboot bootloader
fastboot --set-active=a
ECHO Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to rebooting to flash to B.
pause
adb reboot bootloader
pause
adb --set-active=b
echo Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to reboot.
pause
fastboot reboot

Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.

41rw4lk said:
Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.
Click to expand...
Click to collapse
I attempted as avised with script convertor of RootJunky. First attempt running the script
Code:
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.000s]
Finished. Total time: 0.000s
(bootloader) is-logical:partition: not found
Sending 'partition' (206 KB) OKAY [ 0.016s]
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.185s]
Finished. Total time: 0.216s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9884 KB) OKAY [ 0.331s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.169s]
Finished. Total time: 0.501s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (97431 KB) ^CTerminate batch job (Y/N)? n
Sending 'fsg' (5596 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.135s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.594s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (3151 KB) OKAY [ 0.085s]
Writing 'logo__a' (bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (23357 KB) OKAY [ 0.721s]
Writing 'boot__a' (bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516201 KB) OKAY [ 16.038s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (495129 KB) OKAY [ 15.564s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (519125 KB) OKAY [ 16.524s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523779 KB) OKAY [ 16.152s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516309 KB) OKAY [ 16.016s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (420583 KB) OKAY [ 13.061s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system_b: not found
Sending 'system_b' (515183 KB) OKAY [ 16.010s]
Writing 'system_b' OKAY [ 2.907s]
Finished. Total time: 25.177s
(bootloader) is-logical:system_b: not found
Sending 'system_b' (307220 KB) OKAY [ 9.615s]
Writing 'system_b' OKAY [ 1.648s]
Finished. Total time: 14.835s
(bootloader) is-logical:oem__a: not found
Sending 'oem__a' (175682 KB) OKAY [ 5.476s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'modemst2' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'carrier' OKAY [ 0.001s]
Finished. Total time: 0.004s
Erasing 'cache' OKAY [ 0.000s]
Finished. Total time: 0.004s
Erasing 'userdata' OKAY [ 0.075s]
Finished. Total time: 0.082s
Erasing 'ddr' OKAY [ 0.001s]
Finished. Total time: 0.006s
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5596 KB) OKAY [ 0.173s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.137s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.001s]
Finished. Total time: 0.004s
I notice the error, then proceeded to fix which it should be flash. all it flashes well, but went attempt to reboot to see if system boots up and go back to bootloader .
I'm aware that my scripting is the worst:laugh:, but funny part it got the job done to able to see the system up and running of course without data or wifi connection. :silly: I do appreciate the assistance and Hopefully keep having the assist with suggestions or guides of course. thankfully I have back up the phone(Not Moto z2) but really wish to go back this phone to able to use it as my main again...

If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.

it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?

insanegrim said:
it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?
Click to expand...
Click to collapse
Go back to fastboot and flash the modem only.
fastboot flash modem (drag and drop the NON-HLOS.bin from your firmware here)
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
If that doesn't work it may be possible that your persist partition is full and not letting the modem initialize. You'll need root for this.
adb shell
su
cd /mnt/vendor/persist/cache/recovery
rm log
rm last_log
exit
exit
adb reboot

41rw4lk said:
If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.
Click to expand...
Click to collapse
This soft bricked and now it bootloops my xt1789-04

Fastboot not working

Im trying to flash a rom and get errors. I'm not sure why.
I have the most up to date adb drivers, usb debugging is on.
Erasing 'system' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'system_ext' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'odm' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'product' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'vendor' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Sending 'boot_a' (98304 KB) OKAY [ 2.327s]
Writing 'boot_a' OKAY [ 0.385s]
Finished. Total time: 3.219s
Sending 'dtbo' (24576 KB) OKAY [ 0.585s]
Writing 'dtbo' OKAY [ 0.085s]
Finished. Total time: 0.689s
Sending 'odm' (102400 KB) OKAY [ 2.414s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')

Nvm Fixed by using FastbootD