Database Users

MOTO X STYLE XT1575 doesn't boot

Today in the morning my XT1575 didn't boot and got directly into fastboot mode.
Every time I try to start it I get this message:
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.
Click to expand...
Click to collapse
I searched for a solution but still can't reach one.
I didn't try to downgrade nothing, in fact the phone isn't mine, it's my wife's and she doesn't know anything about flashing ROMs and stuff, so the problem was not there. The phone actually started to get tilted and slow one or two days ago and then today finally "died".
Here's the getvar all I get:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4D
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 32GB Toshiba REV=07 PRV=00 TYPE=57 PNM=032G72
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: ZY223MG4VS
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x8d
(bootloader) uid: 16C4F0001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: 358195071196980
(bootloader) meid:
(bootloader) date: 11-08-2016
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 31 20:42:21 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_retu
(bootloader) ro.build.version.full[1]: s.retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g94afac7 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Dec 8 06:11:12 CST 2016
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) sdi.git: sdi.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-VA0.4D-0-g3d9d261
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.466s
Click to expand...
Click to collapse
The CID say 0xDEAD. It switches to 0x0009 when I flash TWRP with windroid but I still can't flash any other rom because I keep getting these errors (the rom im trying to install is the official one, from motorola's web, MPH24.49-18_18):
C:\Users\Flia Boquense\Desktop\motox>fastboot flash partition gpt.bin
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.097s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.816s
BOOTLOADER LOG: "version downgraded for primary_gpt"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash boot boot.img
target max-download-size: 512MB
sending 'boot' (40960 KB)...
OKAY [ 1.142s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.857s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash recovery recovery.img
target max-download-size: 512MB
sending 'recovery' (41040 KB)...
OKAY [ 1.143s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.858s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash system system.img
target max-download-size: 512MB
sending sparse 'system' (509631 KB)...
OKAY [ 15.608s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.565s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot
invalid PIV signed system image"
Click to expand...
Click to collapse
I can't find a way to make it work again, any help will be appreciated, i'm pretty much a noob in all these stuff.

Your bootloader is locked? It appears so...
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
Click to expand...
Click to collapse
How are you flashing TWRP with a locked bootloader?!?!?!
With a locked bootloader you cannot downgrade, the version on Moto's official site (MPH24.49-18_18) is actually just MPH24.49-18, which is the original Marshmallow when first released in December 2015. Moto support has been notified of this mistake in version and date on the website and have yet to change it in over 6 months since it was mis-posted.
You require MPHS24.49-18-16, which is the December 2016 security update released via OTA in February 2017, or newer version, but the problem is that it is not available. At this point we do not know if/when newer versions of factory firmware images will leak out or not in the future. The newest version we have available is MPHS24.49-18-8, you can attempt that and skip bootloader.img and gpt.bin, but I am guessing with a locked bootloader it will fail since it is still a downgrade.
You have a locked bootloader, with a bootloader state of 0? Contact Moto for repair, without an unlocked bootloader there is nothing we can can do at this point.

acejavelin said:
Your bootloader is locked? It appears so...
How are you flashing TWRP with a locked bootloader?!?!?!
With a locked bootloader you cannot downgrade, the version on Moto's official site (MPH24.49-18_18) is actually just MPH24.49-18, which is the original Marshmallow when first released in December 2015. Moto support has been notified of this mistake in version and date on the website and have yet to change it in over 6 months since it was mis-posted.
You require MPHS24.49-18-16, which is the December 2016 security update released via OTA in February 2017, or newer version, but the problem is that it is not available. At this point we do not know if/when newer versions of factory firmware images will leak out or not in the future. The newest version we have available is MPHS24.49-18-8, you can attempt that and skip bootloader.img and gpt.bin, but I am guessing with a locked bootloader it will fail since it is still a downgrade.
You have a locked bootloader, with a bootloader state of 0? Contact Moto for repair, without an unlocked bootloader there is nothing we can can do at this point.
Click to expand...
Click to collapse
Yes, my bootloader is locked. I understand that to unlock it, i have to get into developer's tools and change some option so I can get the code, am i right? Unluckily, there's no way i can do that since the phone won't start. Any other way to unlock it?
I tried to load other versions but it wont work, the errors i get are the same i get when installing the version from the webpage, so i guess they are related to the fact that they are older versions.
To sum it all, i have a rock with the form of a phone until Motorola's people hear us and upload the latest version??? Any crazy idea i could try to make the phone work?
Thank you for your time acejavelin, really appreciated.

I would contact Motorola support and see what they can do for you.
It will help to know which version of the Moto X that you have. Your thread title has Moto X Style, with the model number of the Moto X Pure Edition. The style is XT1572.
I would tell them that you tried to follow instructions listed on the phone with no luck. Remind them that current software is not available on their web site.

pizza_pablo said:
I would contact Motorola support and see what they can do for you.
It will help to know which version of the Moto X that you have. Your thread title has Moto X Style, with the model number of the Moto X Pure Edition. The style is XT1572.
I would tell them that you tried to follow instructions listed on the phone with no luck. Remind them that current software is not available on their web site.
Click to expand...
Click to collapse
Sorry, my bad, i have the Pure edition, XT1575. I will try to do that hoping to have some luck.

lcn23 said:
Yes, my bootloader is locked. I understand that to unlock it, i have to get into developer's tools and change some option so I can get the code, am i right? Unluckily, there's no way i can do that since the phone won't start. Any other way to unlock it?
I tried to load other versions but it wont work, the errors i get are the same i get when installing the version from the webpage, so i guess they are related to the fact that they are older versions.
To sum it all, i have a rock with the form of a phone until Motorola's people hear us and upload the latest version??? Any crazy idea i could try to make the phone work?
Thank you for your time acejavelin, really appreciated.
Click to expand...
Click to collapse
Any other way to unlock? Nope, impossible actually.
Basically, you need to contact Moto... because you are still locked and stock it can be repaired, either in or out of warranty. Once the bootloader has been unlocked Moto won't even look at it. And that "Software Repair Assistant" was Verizon specific I guess (weird, right), but you can try it https://www.verizonwireless.com/support/knowledge-base-209216/ since it seems to have support for Moto Z Force (it's in the sample picture) so who knows, might work.
Motorola doesn't release firmware images, except for what is on their webpage (which is old for all models listed) and even their requirements are for an unlocked bootloader. The only firmware images we have are ones that are leaked, and that source has reported that it is very difficult (almost impossible) to access these builds now... I would speculate it in part goes back to Moto's pattern of planned obsolescence, but at the same time these images affect such a small number of individuals that they probably don't care anyway.
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
I just realized this is in the old Moto X 2013 area... I will request a Mod to move it.

MY wife somehow made it power on today in the morning. I guess that's the only hope as I wait for the Motorola Support to give me an answer. Impossible to send it to them for repair as i'm from Argentina and i bought it in USA.
Sorry about the misplacement.
Is there any recovery image I could somehow install bypassing the locked status?? The Windroid application "installs" a TWRP and it somehow manages to switch the CID from 0xDEAD to 0x0009, whatever that means.

You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23

dzidexx said:
You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23
Click to expand...
Click to collapse
Will try! Thank you!

dzidexx said:
You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23
Click to expand...
Click to collapse
No man, not working. I only got something different when trying to flash partition gpt.bin. The new error message is this one:
C:\Users\Flia Boquense\Desktop\motox\rom16>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.091s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.963s
Click to expand...
Click to collapse

Your phone still is dead?
Try to flash only boot & system. @lcn23
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
Are you using the newest minimal adb...?
https://devs-lab.com/download-minimal-adb-fastboot-tool.html

UPDATE: Somehow the fastboot changed, the buttons with the options turned into a menu with options inside a light blue bubble and an image of the android pet with his belly open appeared. Seeing this, I tried to flash the gpt bin dzidexx gave me and it worked, but after that I tried to flash the bootloader and it didn't work. I guess I will try again later, because now I'm leaving to work. I will try what you told me later dzidexx. Thanks.
UPDATE 2: After that happened and i rebooted the phone, now its status switched from "stuck at fastboot" to "doesn't power up". I guess I screwed up. How can I fix that? When I plug it to the computer, the PC makes the sound of something being connected to one of her USB ports, but other than that there's nothing I get, it doesn't even appear in Windows Explorer as a connected device. @dzidexx

Nothing you can do in home.
I think the motherboard is broken(before you asked here) - memory.
Sometimes it happens.
Only warranty repair or other GSM service(motherboard replacement). @lcn23

I guess it has something to do with the aboot, because that was the only thing that got installed when flashing bootloader.img.

With locked BL you cannot check/repair it. @lcn23

Then I guess I hard fkin bricked it, damn me.

@acejavelin any ideas of how can I take it out of QHSUSB state??

lcn23 said:
@acejavelin any ideas of how can I take it out of QHSUSB state??
Click to expand...
Click to collapse
Nope... Bootloader is gone if it's going QLoad mode, nothing can be done now but get Moto to fix it. We don't have the necessary files to flash in this state.

lcn23 said:
Today in the morning my XT1575 didn't boot and got directly into fastboot mode.
Every time I try to start it I get this message:
I searched for a solution but still can't reach one.
I didn't try to downgrade nothing, in fact the phone isn't mine, it's my wife's and she doesn't know anything about flashing ROMs and stuff, so the problem was not there. The phone actually started to get tilted and slow one or two days ago and then today finally "died".
Here's the getvar all I get:
The CID say 0xDEAD. It switches to 0x0009 when I flash TWRP with windroid but I still can't flash any other rom because I keep getting these errors (the rom im trying to install is the official one, from motorola's web, MPH24.49-18_18):
I can't find a way to make it work again, any help will be appreciated, i'm pretty much a noob in all these stuff.
Click to expand...
Click to collapse
Go here, https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863, and flash recovery. Then tell us if it works.

[help] hard brick with December patch has solution?

to be able to revive but to flash the December rom stock of error

What errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

echo92 said:
what errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
i tried with above link but no success

prasadak2811 said:
i tried with above link but no success
Click to expand...
Click to collapse
Can you provide us with some information please as well?
What device do you have, how did your device hard brick and what errors/messages are you getting?

echo92 said:
What errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
xt 1640
C:\Program Files (x86)\Minimal ADB and Fastboot>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-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: 0038111937
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: D6EBBF0200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 09-15-2017
(bootloader) sku: XT1640-DS
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed May 4 19:56:34 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-13/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.3.athene.reta
(bootloader) ro.build.version.full[1]: il.pt.BR
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband: M8952_70030.25.03.62.01R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 3.10.84-ElementalX-G4-2.00
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.4 201506
(bootloader) kernel.version[2]: 29 (prerelease) (crosstool-NG 1.20.0 - L
(bootloader) kernel.version[3]: inaro GCC 2015.06 - Cortex-A15) ) #1 SMP
(bootloader) kernel.version[4]: PREEMPT Thu Jan 25 12:45:01 EST 2018
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
all: listed above
finished. total time: 0.488s

echo92 said:
What errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
I'm getting these errors
C:\Program Files (x86)\Minimal ADB and Fastboot>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' (32 KB)...
OKAY [ 0.024s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.111s]
finished. total time: 0.138s
C:\Program Files (x86)\Minimal ADB and Fastboot>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' (3651 KB)...
OKAY [ 0.158s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) will pass: flash:cmnlib
(bootloader) will pass: flash:keymaster
(bootloader) will pass: flash:sbl1
(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 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.459s]
finished. total time: 0.622s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.101s]
writing 'logo'...
OKAY [ 0.064s]
finished. total time: 0.170s
C:\Program Files (x86)\Minimal ADB and Fastboot>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.593s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.801s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.590s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.802s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.573s]
writing 'dsp'...
OKAY [ 0.267s]
finished. total time: 0.845s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 3.297s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.425s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.868s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.995s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250842 KB)...
OKAY [ 8.556s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.622s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (254493 KB)...
OKAY [ 8.667s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.714s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (247302 KB)...
OKAY [ 8.439s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.518s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (260402 KB)...
OKAY [ 8.872s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.918s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262057 KB)...
OKAY [ 8.904s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.956s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261941 KB)...
OKAY [ 8.897s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.977s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (82497 KB)...
OKAY [ 2.817s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.876s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (76958 KB)...
OKAY [ 2.624s]
writing 'modem'...
OKAY [ 1.136s]
finished. total time: 3.764s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.040s]
finished. total time: 0.043s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.039s]
finished. total time: 0.041s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (2032 KB)...
OKAY [ 0.096s]
writing 'fsg'...
OKAY [ 0.077s]
finished. total time: 0.179s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.042s]
finished. total time: 0.049s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.120s]
finished. total time: 0.122s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase customize
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:customize: not found
erasing 'customize'...
OKAY [ 0.033s]
finished. total time: 0.035s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase clogo
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:clogo: not found
erasing 'clogo'...
OKAY [ 0.031s]
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>

jadeilson777 said:
I'm getting these errors
<snip>
Click to expand...
Click to collapse
Thanks for that. A few things I've noted:
1)I'm not sure what's happened to your device, and perhaps you can elaborate on if anything happened before, but the CID=0xDEAD and the odd serial number (unless you changed that) and no presence of the iswarrantyvoid parameter is concerning. Did you try to restore a backup or give your device to a JTAG service, or did you use a blankflash?
2)Your radio baseband version is reporting DFLT_FSG as opposed to BRAZIL, so you may have no network access, though that might be immaterial at this point.
3)Which firmware are you trying to flash at the moment that is giving you the validation errors (e.g. Image boot failed validation?) Is it the NPJS25.93-14-13 Dec 2017 firmware? I note your device is running Blur_Version.25.226.3.athene.retail.pt.BR whereas the stock ROM on XDA is Blur_Version.25.226.3.athene.retail.en.US but I don't know if the different languages are that significant. Verify that you're flashing the NPJS25.93-14-13 stock ROM.
If you are flashing the NPJS25.93-14-13 stock ROM on XDA, I'm concerned that only an expensive motherboard replacement may fix the issues. However, please answer the questions I've asked so we have more information to help you. You can type your response in Portuguese or your native language and then use Google Translate or your favourite translator to translate your response into English if you so choose.

echo92 said:
Thanks for that. A few things I've noted:
1)I'm not sure what's happened to your device, and perhaps you can elaborate on if anything happened before, but the CID=0xDEAD and the odd serial number (unless you changed that) and no presence of the iswarrantyvoid parameter is concerning. Did you try to restore a backup or give your device to a JTAG service, or did you use a blankflash?
2)Your radio baseband version is reporting DFLT_FSG as opposed to BRAZIL, so you may have no network access, though that might be immaterial at this point.
3)Which firmware are you trying to flash at the moment that is giving you the validation errors (e.g. Image boot failed validation?) Is it the NPJS25.93-14-13 Dec 2017 firmware? I note your device is running Blur_Version.25.226.3.athene.retail.pt.BR whereas the stock ROM on XDA is Blur_Version.25.226.3.athene.retail.en.US but I don't know if the different languages are that significant. Verify that you're flashing the NPJS25.93-14-13 stock ROM.
If you are flashing the NPJS25.93-14-13 stock ROM on XDA, I'm concerned that only an expensive motherboard replacement may fix the issues. However, please answer the questions I've asked so we have more information to help you. You can type your response in Portuguese or your native language and then use Google Translate or your favourite translator to translate your response into English if you so choose.
Click to expand...
Click to collapse
1) I was in the stock rom of December with elemental kernel x to get root with magisk and was without network because of the baseband and I looked in the forum something about there I tried to transfer some files of the 1643 xt was when the hard brick occurred I used the recent blankflash and able to revive the bootloader but when trying to flash again the stock of December gave error plus the boot loader went back to normal as in the attached image

echo92 said:
Thanks for that. A few things I've noted:
1)I'm not sure what's happened to your device, and perhaps you can elaborate on if anything happened before, but the CID=0xDEAD and the odd serial number (unless you changed that) and no presence of the iswarrantyvoid parameter is concerning. Did you try to restore a backup or give your device to a JTAG service, or did you use a blankflash?
2)Your radio baseband version is reporting DFLT_FSG as opposed to BRAZIL, so you may have no network access, though that might be immaterial at this point.
3)Which firmware are you trying to flash at the moment that is giving you the validation errors (e.g. Image boot failed validation?) Is it the NPJS25.93-14-13 Dec 2017 firmware? I note your device is running Blur_Version.25.226.3.athene.retail.pt.BR whereas the stock ROM on XDA is Blur_Version.25.226.3.athene.retail.en.US but I don't know if the different languages are that significant. Verify that you're flashing the NPJS25.93-14-13 stock ROM.
If you are flashing the NPJS25.93-14-13 stock ROM on XDA, I'm concerned that only an expensive motherboard replacement may fix the issues. However, please answer the questions I've asked so we have more information to help you. You can type your response in Portuguese or your native language and then use Google Translate or your favourite translator to translate your response into English if you so choose.
Click to expand...
Click to collapse
2) Yes I was without a network and was trying to fix what happened to the hard brick
3) Yes I am trying to flash the December rom stock NPJS25.93-14-13

jadeilson777 said:
1) I was in the stock rom of December with elemental kernel x to get root with magisk and was without network because of the baseband and I looked in the forum something about there I tried to transfer some files of the 1643 xt was when the hard brick occurred I used the recent blankflash and able to revive the bootloader but when trying to flash again the stock of December gave error plus the boot loader went back to normal as in the attached image
Click to expand...
Click to collapse
jadeilson777 said:
2) Yes I was without a network and was trying to fix what happened to the hard brick
3) Yes I am trying to flash the December rom stock NPJS25.93-14-13
Click to expand...
Click to collapse
Hmm, what files did you try to transfer, was it the hw, fsg and modem partitions, and did you transfer them to the correct partitions? Those commands are very powerful and will not alert you if the incorrect partition is overwritten.
I'm guessing by the screenshot you're showing that your bootloader screen is similar, as that bootloader screen is for Osprey devices (Moto G 2015). It should be like that as you've flashed the bootloader from the stock NPJS25.93-14-13 ROM, just with athene (Moto G4) details.
How did you lose network in the first place, was it after flashing firmware?
If you can, I'd doublecheck if your bootloader is unlocked and try unlocking your bootloader (which will erase your information), as looking through your flash results, it looks like your bootloader is rejecting your flashing. NPJS25.93-14-13 should not give you pre-flash validation errors on a G4 Plus as that's the current firmware we have, unless you've flashed a different December 2017 build before or received an OTA update newer than December 2017.
If unlocking the bootloader doesn't work or doesn't resolve not being able to flash, then we may have to begin considering an expensive service repair.

echo92 said:
Hmm, what files did you try to transfer, was it the hw, fsg and modem partitions, and did you transfer them to the correct partitions? Those commands are very powerful and will not alert you if the incorrect partition is overwritten.
I'm guessing by the screenshot you're showing that your bootloader screen is similar, as that bootloader screen is for Osprey devices (Moto G 2015). It should be like that as you've flashed the bootloader from the stock NPJS25.93-14-13 ROM, just with athene (Moto G4) details.
How did you lose network in the first place, was it after flashing firmware?
If you can, I'd doublecheck if your bootloader is unlocked and try unlocking your bootloader (which will erase your information), as looking through your flash results, it looks like your bootloader is rejecting your flashing. NPJS25.93-14-13 should not give you pre-flash validation errors on a G4 Plus as that's the current firmware we have, unless you've flashed a different December 2017 build before or received an OTA update newer than December 2017.
If unlocking the bootloader doesn't work or doesn't resolve not being able to flash, then we may have to begin considering an expensive service repair.
Click to expand...
Click to collapse
my bootloader is blocked and in my opinion this is giving pre-flash error pq was in stock rom December with twrp and with elemental kernbel x

jadeilson777 said:
my bootloader is blocked and in my opinion this is giving pre-flash error pq was in stock rom December with twrp and with elemental kernbel x
Click to expand...
Click to collapse
If your bootloader is locked, then having TWRP and ElementalX on your device will cause your device to fail to boot. A locked bootloader, especially under Nougat, is quite strictly enforced, and is expecting stock recovery and stock kernel, no modifications whatsoever.
The stock ROM flash should be overwriting both partitions with the stock firmware, but as you're not bypassing the strict verification checks, then you can try to unlock your bootloader again and try to re-flash. Alternatively, if you unlock, you may be able to boot if there's still TWRP and ElementalX on your device. Your warranty is voided anyway as you'd have unlocked your bootloader in the past to flash TWRP and ElementalX.
If that doesn't work, it may suggest the flash memory or another hardware fault is present, which may require a motherboard replaement.

echo92 said:
If your bootloader is locked, then having TWRP and ElementalX on your device will cause your device to fail to boot. A locked bootloader, especially under Nougat, is quite strictly enforced, and is expecting stock recovery and stock kernel, no modifications whatsoever.
The stock ROM flash should be overwriting both partitions with the stock firmware, but as you're not bypassing the strict verification checks, then you can try to unlock your bootloader again and try to re-flash. Alternatively, if you unlock, you may be able to boot if there's still TWRP and ElementalX on your device. Your warranty is voided anyway as you'd have unlocked your bootloader in the past to flash TWRP and ElementalX.
If that doesn't work, it may suggest the flash memory or another hardware fault is present, which may require a motherboard replaement.
Click to expand...
Click to collapse
I already tried to unlock the bootloader but I get the result of fetuare disable which is the debugging usb or unlock option of oem that is disabled

jadeilson777 said:
I already tried to unlock the bootloader but I get the result of fetuare disable which is the debugging usb or unlock option of oem that is disabled
Click to expand...
Click to collapse
That's not good - can you boot into the system? If so, you can go to Settings>About Phone, tap the build 7 times, then go back one menu, access Developer Options and then toggle OEM unlocking, which should then let you unlock your bootloader.
If you've re-locked your bootloader and you cannot boot, then unfortunately you may have to consider a motherboard replacement (expensive) or put the money towards a new device. I think we don't have the means to bypass the bootloader security lock if you cannot boot into the system.

echo92 said:
That's not good - can you boot into the system? If so, you can go to Settings>About Phone, tap the build 7 times, then go back one menu, access Developer Options and then toggle OEM unlocking, which should then let you unlock your bootloader.
If you've re-locked your bootloader and you cannot boot, then unfortunately you may have to consider a motherboard replacement (expensive) or put the money towards a new device. I think we don't have the means to bypass the bootloader security lock if you cannot boot into the system.
Click to expand...
Click to collapse
if I was in hard brick but can revive only the bootloader and the system can not activate these options so there is no way to flip the bootloader and with the bootloader locked I can not flashear a previous ROM nor the stock of December pq was with the elemental kernel x of January 25th so I have to wait for a security patch update to flash over

echo92 said:
That's not good - can you boot into the system? If so, you can go to Settings>About Phone, tap the build 7 times, then go back one menu, access Developer Options and then toggle OEM unlocking, which should then let you unlock your bootloader.
If you've re-locked your bootloader and you cannot boot, then unfortunately you may have to consider a motherboard replacement (expensive) or put the money towards a new device. I think we don't have the means to bypass the bootloader security lock if you cannot boot into the system.
Click to expand...
Click to collapse
I'm 16 years old and I do not have money for another motherboard or a new moto g4 plus

jadeilson777 said:
if I was in hard brick but can revive only the bootloader and the system can not activate these options so there is no way to flip the bootloader and with the bootloader locked I can not flashear a previous ROM nor the stock of December pq was with the elemental kernel x of January 25th so I have to wait for a security patch update to flash over
Click to expand...
Click to collapse
Yeah, hopefully the February 2018 security patch ROM should be on its way soon. If that doesn't fix things then you may have to visit a service centre.
---------- Post added at 06:56 PM ---------- Previous post was at 06:53 PM ----------
jadeilson777 said:
I'm 16 years old and I do not have money for another motherboard or a new moto g4 plus
Click to expand...
Click to collapse
Unfortunately a hard brick in this manner seems to be quite hard to fix, especially if you cannot flash the stock ROM (with a locked bootloader failing validation). However, we'll have to see if the newer stock ROM resolves this.

echo92 said:
Yeah, hopefully the February 2018 security patch ROM should be on its way soon. If that doesn't fix things then you may have to visit a service centre.
---------- Post added at 06:56 PM ---------- Previous post was at 06:53 PM ----------
Unfortunately a hard brick in this manner seems to be quite hard to fix, especially if you cannot flash the stock ROM (with a locked bootloader failing validation). However, we'll have to see if the newer stock ROM resolves this.
Click to expand...
Click to collapse
Can you tell me when the next update comes out if and still this month?

jadeilson777 said:
Can you tell me when the next update comes out if and still this month?
Click to expand...
Click to collapse
Honestly no idea - we've not even seen the OTA update for the February 2018 security update, just the patch notes. Could be this month, could be next month. Furthermore, that still relies on someone capturing and uploading the stock ROM firmware with that patch to Android FileHost or somewhere.

Moto g5 plus IMEI 0 after flashing anything? Read on!

After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required!
Prerequisites:
U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on other versions)
8.1 custom Oreo ROM (I used Validus, we only use this to get signal and imei back to default)
Moto g5 plus STOCK ROM https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Patience
***************************
That's it!
Down to the nitty gritty. Your imei is zero or 0000000 or some funky number, and no sim cards/cellular service works in your device, right? I finally found the simple solution after hard work. You have TWO options, read on.
1. Flash custom recovery, erase everything, and get on 8.1 Oreo ROM (delete modemst1 and 2 in fastboot beforehand) and STAY THERE. Signal will work.
2. OR go back to stock everything and locked bootloader, which is what I did. My fastboot says software status official oem locked and I get updates.
******************
The TRICK is, if your imei is 0 and cellular doesn't work, you have to delete your modemst1 and 2 in fastboot before installing anything new, so that it can reset back to default. The other TRICK is if you are reverting back to stock, follow all the normal commands for reflashing, but DON'T do anything with modemst. say I was following normal commands for flashing, then ran across these three commands....
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
SKIP THEM. What we're attempting to do is keep your EFS folder as it was on the 8.1 OREO, aka WORKING. Flashing rom itself doesn't delete the EFS folder, but when you run those commands (which is in most tutorials) IT WILL WRECK YOUR IMEI AGAIN.
************
So, to recap. To fix IMEI issue, use these two commands in fastboot
fastboot erase modemst1
fastboot erase modemst2
THEN, flash 8.1 custom oreo rom, and if you like it stay with it, your signal will be working again, or go back to stock everything oem locked, your choice, just make sure you don't delete your modemst1,2 in commands WHILST doing so.
And that's it! Your imei and signal is working again. What's stupid is that this happens in the first place, but life happens. FIXED!

Did you get voLTE to work?

What carrier are you on? I am on Verizon and this only gets me 3G like all of other fixes for this issue on here.

stonewolf05 said:
What carrier are you on? I am on Verizon and this only gets me 3G like all of other fixes for this issue on here.
Click to expand...
Click to collapse
Was with Verizon, was only getting 3g, frequent drops. Switched to AT&T just because they're so much better in my area.

thankyou soo much . helped me

I dint get my signal/IMEI back after installing custom rom
any suggestions??
Thanks in Advance

mohitzr said:
I dint get my signal/IMEI back after installing custom rom
any suggestions??
Thanks in Advance
Click to expand...
Click to collapse
Unfortunately, none of these methods work no more, the question is why?. Personally, I believe something further has been borked in oreo development, just like the volte issue. Absolutely no methods restore my ime, some actually make it very difficult to even get a signal now. I spent several hours last night trying every option available just to get a signal, whereas before I flashed the latest vladious rom, flashing pixel experience, or any oreo rom for that matter, would restore 4g on first boot. My ime is 0 and i give up. In all my years with android modding (since zte blade), I have never had a device with so many issues, and so unpredictable. You can use a method to fix something, and next thing you know it does not work, for example, encryption can be really hit and miss when you first flash twrp, even flashing no verity does not always work.

Tried every possible combination as per guides/fixes....no luck..

The only thing that's worked for me without fail every time is wiping everything with twrp, Dalvik, Data, System, Cache, internal storage, hitting that dreaded Format Data button, and flashing the earliest stock firmware (which I believe is 137-33 for the XT1687) using fastboot. Having a backup can save a ton of time and headaches too. If there's any point where you DO get at least LTE working, back up that EFS partition before you do ANYTHING else. But try flashing the earliest stock you can find, or preferably the one that was on your device when you bought it.

Worked like a Charm!
Dude, i was looking for the same since yesterday, come to this thread and follow all the steps carefully. My IMEI was showing 0 before and now everything is working fine including both SIM cards.
Thanks
beatlesfan5858 said:
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required!
Prerequisites:
U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on other versions)
8.1 custom Oreo ROM (I used Validus, we only use this to get signal and imei back to default)
Moto g5 plus STOCK ROM https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Patience
***************************
That's it!
Down to the nitty gritty. Your imei is zero or 0000000 or some funky number, and no sim cards/cellular service works in your device, right? I finally found the simple solution after hard work. You have TWO options, read on.
1. Flash custom recovery, erase everything, and get on 8.1 Oreo ROM (delete modemst1 and 2 in fastboot beforehand) and STAY THERE. Signal will work.
2. OR go back to stock everything and locked bootloader, which is what I did. My fastboot says software status official oem locked and I get updates.
******************
The TRICK is, if your imei is 0 and cellular doesn't work, you have to delete your modemst1 and 2 in fastboot before installing anything new, so that it can reset back to default. The other TRICK is if you are reverting back to stock, follow all the normal commands for reflashing, but DON'T do anything with modemst. say I was following normal commands for flashing, then ran across these three commands....
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
SKIP THEM. What we're attempting to do is keep your EFS folder as it was on the 8.1 OREO, aka WORKING. Flashing rom itself doesn't delete the EFS folder, but when you run those commands (which is in most tutorials) IT WILL WRECK YOUR IMEI AGAIN.
************
So, to recap. To fix IMEI issue, use these two commands in fastboot
fastboot erase modemst1
fastboot erase modemst2
THEN, flash 8.1 custom oreo rom, and if you like it stay with it, your signal will be working again, or go back to stock everything oem locked, your choice, just make sure you don't delete your modemst1,2 in commands WHILST doing so.
And that's it! Your imei and signal is working again. What's stupid is that this happens in the first place, but life happens. FIXED!
Click to expand...
Click to collapse

(bootloader) Permission denied. Please help
Can anyone help on this error. I'm having IMEI 0 error, was working fine in morning after that my friend messed up and now same error. I was not able to fire any command now. please help.
fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
Other might helpful info:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2245K4LB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 372C889E00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358958068640199
(bootloader) meid:
(bootloader) date: 07-20-2017
(bootloader) sku: XT1686
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 6:53:42 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-15/14:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.14.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband[0]: M8953_8000.128.06.42u POTTER_INDIADSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g708ac5e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: hu Jan 12 12:24:19 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=27e6e4b-dirty
(bootloader) devcfg.git: git=27e6e4b-dirty
(bootloader) keymaster.git: git=27e6e4b-dirty
(bootloader) cmnlib.git: git=27e6e4b-dirty
(bootloader) cmnlib64.git: git=27e6e4b-dirty
(bootloader) prov.git: git=27e6e4b-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(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.121s
beatlesfan5858 said:
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required!
Prerequisites:
U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on other versions)
8.1 custom Oreo ROM (I used Validus, we only use this to get signal and imei back to default)
Moto g5 plus STOCK ROM https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Patience
***************************
That's it!
Down to the nitty gritty. Your imei is zero or 0000000 or some funky number, and no sim cards/cellular service works in your device, right? I finally found the simple solution after hard work. You have TWO options, read on.
1. Flash custom recovery, erase everything, and get on 8.1 Oreo ROM (delete modemst1 and 2 in fastboot beforehand) and STAY THERE. Signal will work.
2. OR go back to stock everything and locked bootloader, which is what I did. My fastboot says software status official oem locked and I get updates.
******************
The TRICK is, if your imei is 0 and cellular doesn't work, you have to delete your modemst1 and 2 in fastboot before installing anything new, so that it can reset back to default. The other TRICK is if you are reverting back to stock, follow all the normal commands for reflashing, but DON'T do anything with modemst. say I was following normal commands for flashing, then ran across these three commands....
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
SKIP THEM. What we're attempting to do is keep your EFS folder as it was on the 8.1 OREO, aka WORKING. Flashing rom itself doesn't delete the EFS folder, but when you run those commands (which is in most tutorials) IT WILL WRECK YOUR IMEI AGAIN.
************
So, to recap. To fix IMEI issue, use these two commands in fastboot
fastboot erase modemst1
fastboot erase modemst2
THEN, flash 8.1 custom oreo rom, and if you like it stay with it, your signal will be working again, or go back to stock everything oem locked, your choice, just make sure you don't delete your modemst1,2 in commands WHILST doing so.
And that's it! Your imei and signal is working again. What's stupid is that this happens in the first place, but life happens. FIXED!
Click to expand...
Click to collapse

deep_raman said:
Can anyone help on this error. I'm having IMEI 0 error, was working fine in morning after that my friend messed up and now same error. I was not able to fire any command now. please help.
fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
Other might helpful info:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2245K4LB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 372C889E00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358958068640199
(bootloader) meid:
(bootloader) date: 07-20-2017
(bootloader) sku: XT1686
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 6:53:42 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-15/14:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.14.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband[0]: M8953_8000.128.06.42u POTTER_INDIADSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g708ac5e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: hu Jan 12 12:24:19 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=27e6e4b-dirty
(bootloader) devcfg.git: git=27e6e4b-dirty
(bootloader) keymaster.git: git=27e6e4b-dirty
(bootloader) cmnlib.git: git=27e6e4b-dirty
(bootloader) cmnlib64.git: git=27e6e4b-dirty
(bootloader) prov.git: git=27e6e4b-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(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.121s
Click to expand...
Click to collapse
Is your device got fixed?

riyan65 said:
Is your device got fixed?
Click to expand...
Click to collapse
No yet brother! I've to take it to the customer center but they are stating that it can't be solved through software and need to replace motherboard LOL.
I took back and its with me now. Waiting for some solutions here.

deep_raman said:
No yet brother! I've to take it to the customer center but they are stating that it can't be solved through software and need to replace motherboard LOL.
I took back and its with me now. Waiting for some solutions here.
Click to expand...
Click to collapse
Your network problem can be solved since IMEI no is shown getvar. You can try installing latest stock Oreo, or trying custom ROMS. Many times custom ROM bring back the IMEI.

riyan65 said:
Your network problem can be solved since IMEI no is shown getvar. You can try installing latest stock Oreo, or trying custom ROMS. Many times custom ROM bring back the IMEI.
Click to expand...
Click to collapse
Bro, I've tried and what I'm getting is below, i think becuase of flashing_locked:
fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.410s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.419s
fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.526s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.540s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 6.117s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.175s
I can't able to flash too

deep_raman said:
Bro, I've tried and what I'm getting is below, i think becuase of flashing_locked:
fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.410s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.419s
fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.526s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.540s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 6.117s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.175s
I can't able to flash too
Click to expand...
Click to collapse
Did you try Lenovo moto smart assistant? It will flash the device for you.

riyan65 said:
Did you try Lenovo moto smart assistant? It will flash the device for you.
Click to expand...
Click to collapse
Yeah , tried that as well. It is failing at 67%. Tried in USB debugging as well as fastboot mode.!!

deep_raman said:
Yeah , tried that as well. It is failing at 67%. Tried in USB debugging as well as fastboot mode.!!
Click to expand...
Click to collapse
Use the firmware downloaded by LMSA and flash the device manually. And did you try any custom ROMs? Mostly they help you to get back your IMEI.

riyan65 said:
Use the firmware downloaded by LMSA and flash the device manually. And did you try any custom ROMs? Mostly they help you to get back your IMEI.
Click to expand...
Click to collapse
I tried the LMSA and custom ROMS but the main problem is I dont even have flashing permission too. As mentioned earlier I' m getting flashing permission denied. I dont have TWRP install, dont have flashing permission...!! So cant flash anything anymore !!! :crying:

deep_raman said:
I tried the LMSA and custom ROMS but the main problem is I dont even have flashing permission too. As mentioned earlier I' m getting flashing permission denied. I dont have TWRP install, dont have flashing permission...!! So cant flash anything anymore !!! :crying:
Click to expand...
Click to collapse
Solution
I was using previous/old version of ADB files(Fastboot.exe and ADB.exe). Post downloading latest version, I was able to fire below command through bootloader:
fastboot.exe flashing unlock
Now I'm all happy.

slot-count not found, slot-suffixes not found,bootloaer working fine

Hello,
I've recently tried to flash stock recovery to be able to receive update . I had TWRP installed already . But whenever I type fastboot command , I get error like slot-count not found .
And that's not the case . I've tried with flashing bootloader and gpt.bin as well and get the same error ! My bootloader is working fine! Also whenever I try these steps, I end up losing my WiFi/hotspot connectivity !
Here take a look . I get these errror in ADB :
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
C:\Windows\system32\cmd.exe O
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\User
s\MAYUR Desktop\New folder recovery.img"
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
bootloader) slot-suffixes: not found
(bootloader) has-slot recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.529s]
writing 'recovery'..
<bootloader) Image signed with key bad key
OKAY [ 9.668s]
finished. total time: 1.204s
rs\MAYUR\Desktop\New folder\gpt.bin"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition "C:\Use
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
<bootloader) slot-suffixes: not found
(bootloader) has-slot: partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing partition'.
(bootloader) Flashing prinary GPT image..
(bootloader) Flashing backup GPT image...
OKAY [ 9.093s]
finished. total time: 0.106s
C:\Program Files (x86)\Minimal ADB and Fastboot >fastboot flash bootloader "C:\US
ers\MAYUR Desktop\New folder\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' (3651 KB)...
OKAY [ 0.124s]
writing 'bootloader'.
(bootloader) validating: bootloader.default.xml
(bootloader will pass: flash:aboot
<bootloader) will pass: flash:tz
(bootloader) will pass: flash: rpm
(bootloader) will pass: flash: hyp
(bootloader will pass: flash: keymaster
(bootloader) will pass: flash:cmnlib
(bootloader will pass: flash sbli
(bootloader) committing: bootloader.default.xml
bootloader> flashing 'emmc_apps boot.mbn' to 'abooty
(bootloader) flashing 'tz.mbn' to 'tz'
<bootloader) flashing rpm.mbn' to rpm'
(bootloader) flashing 'hyp.mbn' to 'hyp'
(bootloader flashing 'keymaster.mbn' to 'keymaster'
bootloader) flashing 'canlib.mbn' to 'canlib'
OKAY [ 0.608s]
(bootloader) flashing 'sbll.mbn' to sbli'
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
(Getvar all) returned this : ?
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
C:\Windows\system32\cmd.exe
C:\Users\MAYUR\Desktop\New folder>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-nsm8952-B1.07
bootloader) product: athene 16mp
<bootloader board: athene_16mp
<bootloader) secure yes
<bootloader) hwrey: P2A
<bootloader) radio: 4
<bootloader) storage-type ennc
<bootloader) emnc 16GB SAMSUNG QE13MB RU-08 PU-7 FU-OOOOOOOOOOOOOOOD
<bootloader) ran: 2GB SAMSUNG LP3 DIE=8Gb M501 M6-05 M2=00 M8 -17
(bootloader) cpu MSM8952
(bootloader) serialno: *protected*
<bootloader) cid: Ox0032
<bootloader) channelid: Oxco
(bootloader) uid: 2E2FAAOOOOOOOOOOOOOOOOOOO000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvo id: yes
(bootloader) reason: Volume down key pressed
bootloader> max-download-size: 536870912,
<bootloader) meid:
(bootloader) imei: *protected*
<bootloader) date: 05-31-2016
<bootloader) sku: XT1643
<bootloader) battid: SNN5966A
bootloader> max-sparse-size: 268435456
<bootloader) iccid:
<bootloader) cust_md5:
(bootloader> current-time "'Sat Apr 30 0:19:14 UTC 2016"
(bootloader) ro.build.fingerprint [0]: motorola/athene/athene:2.0/NPJS25.
bootloader) ro.build.fingerprint(1): 93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
bootloader) ro.build.version.full[1]: il.en.US
bootloader) version-baseband: M8952_70030.25.03.62.02R DFLT_FSG
(bootloader) kernel.version [1]: 2526f <hudsoncneilclbld72) (gcc version
<bootloader) ro.build.version.qcon: LA.BR.1.3.6-01210-8926.0
bootloader) kernel.version [0]: Linux version 3.10.84-ge03508d-00131-944,
bootloader) kernel.version [2]: 4.8 (GCC) > 111 SMP PREEMPT Wed Mar 28 06
(bootloader) kernel.version [3]: :58:16 CDT 2018
(bootloader) tz.git: git-69dd24b-dirty
(bootloader) rpm.git: [email protected]
<bootloader) sbl1.git: git-MBM-NG-UB1.07-6-952d1343
(bootloader) hyp.git: git-69dd24b-dirty
(bootloader) cmnlib.git:git-69dd24b-dirty
(bootloader) aboot.git: git-MBM-NG-UB1.07-0-9f9b89ba
bootloader> keymaster-git: git-69dd24b-dirty
(bootloader) ro.carrier: retin
(bootloader) frp-state: no protection (0)
<bootloader> qe: qe 0/1
all: listed above
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
I've read all the related forum but none of them is similar to mine ! They say we've have to blank flash the bootloader . But mines working fine . Do I really need to blank flash or something else would work fine ? If i really need to blank flash , then pls guide me !
Thank you very much in advance !
Have a great day ?
P.S. = sorry if the related thread already exist !

As far as I know, those slot error messages are normal, and are more informational. The message relate to the flashing slots found on A/B partitioned devices (e.g Google pixels and newer device). We don't have that (G4 plus only had the one set of partitions) and so you expect to see that message on our device. For a newer device, fastboot may try to determine which update slot (either A or B) to flash to.
Flashing recovery or boot (kernel, not bootloader) will usually show image signed with bad key if your bootloader is unlocked. That is normal under that condition.
I'm not entirely sure where the idea to blank flash came from - that method is really only to be used if you've corrupted your bootloader and you cannot boot into the bootloader normally. It's a method of last resort and as you've got a working bootloader and GPT, you really have no need of it.
Your getvar looks mostly okay too, the information you have there matches what we expect from the April 2018 firmware. The odd thing is that your baseband is reporting DFLT_FSG rather than the expected ATHENE_INDIA suffix, which may explain the loss of radio. Can I ask if you flashed any other stock firmware before hand? You may wish to have a look through this thread for more information https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912

Sir I've flashed RR, INVICTA,and many other ROMs but... Didn't face this issue before ... I've recently flashed stock firmware provided by @rajatgupta1998 in this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/amp/ .. and ended up here !! The thread you provided as reference is an older discussion where he downgraded his bootloader by flashing ROM from different Android version ... But I've done nothing like that ! Please help me how to het the radio working ! Thanks in advance sir !

echo92 said:
As far as I know, those slot error messages are normal, and are more informational. The message relate to the flashing slots found on A/B partitioned devices (e.g Google pixels and newer device). We don't have that (G4 plus only had the one set of partitions) and so you expect to see that message on our device. For a newer device, fastboot may try to determine which update slot (either A or B) to flash to.
Flashing recovery or boot (kernel, not bootloader) will usually show image signed with bad key if your bootloader is unlocked. That is normal under that condition.
I'm not entirely sure where the idea to blank flash came from - that method is really only to be used if you've corrupted your bootloader and you cannot boot into the bootloader normally. It's a method of last resort and as you've got a working bootloader and GPT, you really have no need of it.
Your getvar looks mostly okay too, the information you have there matches what we expect from the April 2018 firmware. The odd thing is that your baseband is reporting DFLT_FSG rather than the expected ATHENE_INDIA suffix, which may explain the loss of radio. Can I ask if you flashed any other stock firmware before hand? You may wish to have a look through this thread for more information https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912
Click to expand...
Click to collapse
Hello ! I've tried to flash dsp,bootloader,and modem
In adb in twrp .. but my device doesn't detect when I type adb devices in TWRP ! Elsewhere it detects my device ... Be it when I do this while my device is on or in fasboot mode.... could you pls help me with that !!??
Without the radio it's nothing more than a iPod ... Sorry if didn't follow the steps mentioned correctly... pls help me with that ... I'd be very much thankful !
Waiting for your reply ??

Vs1607 said:
Hello ! I've tried to flash dsp,bootloader,and modem
In adb in twrp .. but my device doesn't detect when I type adb devices in TWRP ! Elsewhere it detects my device ... Be it when I do this while my device is on or in fasboot mode.... could you pls help me with that !!??
Without the radio it's nothing more than a iPod ... Sorry if didn't follow the steps mentioned correctly... pls help me with that ... I'd be very much thankful !
Waiting for your reply
Click to expand...
Click to collapse
Does your computer detect your device when you connect via USB whilst booted in TWRP (does your device appear in Device Manager if you're using Windows?) and what version of TWRP are you using? What version of fastboot/ADB do you have installed on your computer?
I'm not that familiar with helping to losing baseband - that's why I referred you to that thread - though it's old and perhaps not exactly what happened to your device, there may be some useful information as to fixing your device.

MOTO G5 PLUS, stuck in fastboot flash mode

Failed to pass validation, backup to fastboot
Boot up failed.
The flashboot flash mode screen says:
Product/Variant : potter 000000000000000 32GB P3B
....
oem_locked
All variables: https://file.io/rF0SqpBhP398
On running the cammands:
C:\ProgramData\RSA\Download\newfolder>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.123s
Every command is failing by saying remote failure.
I saw some flashboot commands and tried to run it. But I think it required oem unlocked. How to do that, can anyone please help me?
The Rescue and Smart Assistant software isn't working because the IMEI is showing all 0 (zero) here. And it says something is wrong and should go to customer support. Please help me guys. Let me know what should I do now? It is out of warranty as well.
For the image files I am using the same I downloaded via the rescue and smart assistant software.
#motog5 #motog5plus #oem_locked.

ssoni0097 said:
Failed to pass validation, backup to fastboot
Boot up failed.
The flashboot flash mode screen says:
Product/Variant : potter 000000000000000 32GB P3B
....
oem_locked
All variables: https://file.io/rF0SqpBhP398
On running the cammands:
FAILED (remote failure)
finished. total time: 0.123s
Every command is failing by saying remote failure.
I saw some flashboot commands and tried to run it. But I think it required oem unlocked. How to do that, can anyone please help me?
Click to expand...
Click to collapse
Within phone's Android -> Settings -> Developer options you have to enable "OEM Unlock" and reboot phone afterwards. Then you have to unlock phone's bootloader
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot flashing unlock
fastboot reboot

jwoegerbauer said:
Within phone's Android -> Settings -> Developer options you have to enable "OEM Unlock" and reboot phone afterwards. Then you have to unlock phone's bootloader
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot flashing unlock
fastboot reboot
Click to expand...
Click to collapse
But the phone is not turning on na .. It is stuck on the fastboot flash mode screen. How do I unlock the oem then

Try
Code:
fastboot reboot
to exit Fastboot mode

jwoegerbauer said:
Try
Code:
fastboot reboot
to exit Fastboot mode
Click to expand...
Click to collapse
The fastboot opens again. As I said, it is stuck there.
On selecting start on fastboot, it says
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed.

Try to re-flash phone's Stock ROM.

jwoegerbauer said:
Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
How to do that? Can you please help .. please
I tried following some steps, downloading the files from a website. But it results into fail.
Fix a dead Moto G5 plus and fix bootloop problem Animetrick
Recently my moto g5S plus got stuck on moto screen and I was flash with this method and this got worked on my phone. Now my phone was completely working and
animetrick.com
for example:
C:\Program Files (x86)\Minimal ADB and Fastboot1>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.023s]
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 failure)
finished. total time: 0.157s

@sd_shadow can you help please?

What you basically are doing wrong is NOT to use Motorola's proprietary mfastboot but Google's fastboot.
Must admit I didn't know of this, too.

jwoegerbauer said:
What you basically are doing wrong is NOT to use Motorola's proprietary mfastboot but Google's fastboot.
Must admit I didn't know of this, too.
Click to expand...
Click to collapse
Tried with mfastboot as well. It shows the same thing ..
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 1.554s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.562s

jwoegerbauer said:
Within phone's Android -> Settings -> Developer options you have to enable "OEM Unlock" and reboot phone afterwards. Then you have to unlock phone's bootloader
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot flashing unlock
fastboot reboot
Click to expand...
Click to collapse
Motorola devices require an unlock code
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com

ssoni0097 said:
Tried with mfastboot as well. It shows the same thing ..
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 1.554s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.562s
Click to expand...
Click to collapse
What does getvar all say?
Remove the imei line before posting
Code:
fastboot getvar all
You need the firmware that matches
Device Model #, Codename, and Software Channel.
If you have a windows PC try LMSA's fash rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

jwoegerbauer said:
What you basically are doing wrong is NOT to use Motorola's proprietary mfastboot but Google's fastboot.
Must admit I didn't know of this, too.
Click to expand...
Click to collapse
I generally do not use mfastboot, it has not been updated in years.
but if fastboot.exe fails, it doesn't hurt to try mfastboot.

sd_shadow said:
What does getvar all say?
Remove the imei line before posting
Code:
fastboot getvar all
You need the firmware that matches
Device Model #, Codename, and Software Channel.
If you have a windows PC try LMSA's fash rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
https://file.io/EEveR0bZCRDV
Tried the rescue and smart assistant tool as well. But it catches the imei as 0, and stops there.
Removed imei line below:
Code:
C:\ProgramData\RSA\Download\newfolder>mfastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 3fb4905f
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 7D81062600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(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

sd_shadow said:
What does getvar all say?
Remove the imei line before posting
Code:
fastboot getvar all
You need the firmware that matches
Device Model #, Codename, and Software Channel.
If you have a windows PC try LMSA's fash rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Tried every version of POTTER_RETAIL_8.1.0.XX (8 zip files) and run mfastboot oem get_unlock_data. But all resulted into the failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s
Please help.

ssoni0097 said:
Tried every version of POTTER_RETAIL_8.1.0.XX (8 zip files) and run mfastboot oem get_unlock_data. But all resulted into the failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s
Please help.
Click to expand...
Click to collapse
What does getvar all say?

sd_shadow said:
What does getvar all say?
Click to expand...
Click to collapse
MOTO G5 PLUS, stuck in fastboot flash mode
Failed to pass validation, backup to fastboot Boot up failed. The flashboot flash mode screen says: Product/Variant : potter 000000000000000 32GB P3B .... oem_locked All variables: https://file.io/rF0SqpBhP398 On running the cammands...
forum.xda-developers.com
Posted it above

ssoni0097 said:
Posted it above
Click to expand...
Click to collapse
Have you ever fetched the unlock code from Motorola? No way without it If you're not able to boot into your device try to flash the latest firmware and carry on from there.
Here's how to flash the latest firmware:
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com

Wolfcity said:
Have you ever fetched the unlock code from Motorola? No way without it If you're not able to boot into your device try to flash the latest firmware and carry on from there.
Here's how to flash the latest firmware:
Click to expand...
Click to collapse
please share the link
I tried it by following instructions from Motorola site. The first command to get code is
mfastboot oem get_unlock_data. But it results into failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s

ssoni0097 said:
please share the link
I tried it by following instructions from Motorola site. The first command to get code is
mfastboot oem get_unlock_data. But it results into failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s
Click to expand...
Click to collapse
Did you check if your devices bootloader is unlockable at all?
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
I would recommend to not use mfastboot as it is outdated. Better try this one:
[TOOL][WINDOWS] ADB & Fastboot++ | February 2023
NFO: • Versions: Installer, Portable & ADBKit • Android Debug Bridge & Fastboot updated to latest v1.0.41 (Version 34.0.0-9570255, February 2023) Features: • Installation Folder chooseable (Installer) • Desktop & Start Menu Shortcuts (Installer)...
forum.xda-developers.com
As written above, best may be to flash the latest signed firmware and start from scratch.
Follow this tutorial (the upper part):
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com