Database Users

XT1572 every time reboot enter in mode fastboot

Hello,
The first day I got my moto x style (XT1572) I started to root, everything was more or less well until I tried to install the SU when I finished installing the binary from the TWRP custom recovery-3.0.2-0- clark you say yes to install the root since the phone would not start and remains in boot loop.
After much look I followed some tutorial XDA (http://forum.xda-developers.com/moto-x-style/help/brick-downgrade-6-0-to-5-1-heeeeelp-t3253716) to return to flash the phone with the rom that theory came from factory cbox1s_XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml after following all the steps mobile and well lit and seems it was all sorted.
Well, I went back to the load to make root and remove the message that the bootloader was unlocked this time all fu well, except now every time I reboot I enter into fastboot mode and have to select START to boot normal to me.
Any ideas or suggestions to fix it?
regards,
PD: Sorry for my google translate english i'am spanish a my english level is very bad :crying:

SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect

same problem with Motorola z xt1650-03 , unlocked bootloader , every time I start up remain stuck in fastboot mode , after ,push the power button for start , and start normal.
I try to reload stock firmware 7.0 with fastboot mode but when try to flash partition.gpt he say bad key .
now I used like this ,

sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
What? how do you do it? can you tell me how to do it more specific? I'm new so I don't understand what you mean and how you do it :/
thank you.

Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.

acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
You saved my [email protected]#! Thanks.
I'm trying help a friend with her Moto X Style. The buttoms RETURN, HOME and APP is not working. I'm trying upload a ROM, but I got errors everytime and the fastboot was entering every boot.

acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc

Sam to me. Any help?

ninormalen said:
Sam to me. Any help?
Click to expand...
Click to collapse
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.

typo - fastboot, not fasboot
fastboot oem fb_mode_clear

fastboot oem fb_mode_clear
Click to expand...
Click to collapse
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?

lucas.passos said:
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
Click to expand...
Click to collapse
There is no problem... The Moto X does not have A/B software slots, the messages above are merely informational and completely normal.

With mfastboot there is no messages like this. Only "OKAY" one
However it didn't help with my Moto G (falcon).
What helped was checking the kernel. My "smartness" told me to flash Nouagt when I had Pie rom...

Dunken415 said:
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.[/QUOTE
same problem here brother did you find any solution to it?? please help me brother.
Click to expand...
Click to collapse

sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
How'd you do that? i have the same problem how do switch back to normal powerup?

XT-1570 "bootmode-recovery"
Dunken415 said:
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Click to expand...
Click to collapse
I am having the same issue. Would appriciate any help.
E:\fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.016s
PS E:\Backup\Android - XT1570> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.43
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: no
(bootloader) hwrev: 0x82A0
(bootloader) radio: 0x3
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(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: LX7C2xxxxx
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: EFFA2C001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35550006xxxxxxx
(bootloader) meid:
(bootloader) date: 04-30-2015
(bootloader) sku: XT1570
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 18 7:57:55 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :6.0.1/MPHS24.107-58-5/4:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-gb67345b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goo
(bootloader) kernel.version[2]: gle 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Sep 29 00:24:52 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=16279de-dirty
(bootloader) hyp.git: git=16279de-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) aboot.git: git=MBM-NG-VA0.43-0-gde54c6f
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
C:\fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s

Help, my Moto X Style XT1752 Brick :(

Hello people, I come with a Moto X XT1572 brickeado, out of nowhere is stuck in the Motorola logo and it does not pass from there, restarting over and over again.
I tried several methods to try to install a stock Firm, 6.0 or 6.1, but without success.
Because I can only connect it in fastboot mode and RSD Lite does not recognize it, I followed the tutorial:
https://www.youtube.com/watch?v=njXQYn53SPc
Whatever Firm it is, I throw the following error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
I understand and I have read, the problem is initially in the boot, I have tried flashing only the boot, but it does not respond, throwing the same error.
It is worth clarifying that the bootloader is blocked, and if I try to unlock it it throws me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
I can not check that option, since it does not fix je.
Also it is worth clarifying that it does not allow me to enter the recovery, when it enters that option it is automatically restarted returning to the motorola logo again and again.
Do you have any idea what else to try? Thank you in advance.

AlexAndroid said:
Hello people, I come with a Moto X XT1572 brickeado, out of nowhere is stuck in the Motorola logo and it does not pass from there, restarting over and over again.
I tried several methods to try to install a stock Firm, 6.0 or 6.1, but without success.
Because I can only connect it in fastboot mode and RSD Lite does not recognize it, I followed the tutorial:
Whatever Firm it is, I throw the following error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
I understand and I have read, the problem is initially in the boot, I have tried flashing only the boot, but it does not respond, throwing the same error.
It is worth clarifying that the bootloader is blocked, and if I try to unlock it it throws me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
I can not check that option, since it does not fix je.
Also it is worth clarifying that it does not allow me to enter the recovery, when it enters that option it is automatically restarted returning to the motorola logo again and again.
Do you have any idea what else to try? Thank you in advance.
Click to expand...
Click to collapse
Have you tried a factory reset in the stock recovery? From the bootloader select Recovery and let it start, when you get "Dead Andy" with an exclamation mark after the timeout, hold power and tap Vol Up and release both keys. Select Factory reset/Wipe data and let finish and then reboot... First boot can take 20 minutes plus after a reset.

acejavelin said:
Have you tried a factory reset in the stock recovery? From the bootloader select Recovery and let it start, when you get "Dead Andy" with an exclamation mark after the timeout, hold power and tap Vol Up and release both keys. Select Factory reset/Wipe data and let finish and then reboot... First boot can take 20 minutes plus after a reset.
Click to expand...
Click to collapse
Selecting Recovery restarts the device, returning to the Motorola logo and restarting again and again, without ever entering the recovery mode.

AlexAndroid said:
Selecting Recovery restarts the device, returning to the Motorola logo and restarting again and again, without ever entering the recovery mode.
Click to expand...
Click to collapse
In the bootloader, can you post the output of 'fastboot getvar all' (just mask out your IMEI number)?

acejavelin said:
In the bootloader, can you post the output of 'fastboot getvar all' (just mask out your IMEI number)?
Click to expand...
Click to collapse
You mean this? (attached image)

Sorry, I understand what you mean, when I go back to my house, I give you that information. Thank you

AlexAndroid said:
Sorry, I understand what you mean, when I go back to my house, I give you that information. Thank you
Click to expand...
Click to collapse
Do you know how to use fastboot and adb? This is from a computer...

acejavelin said:
Do you know how to use fastboot and adb? This is from a computer...
Click to expand...
Click to collapse
Yes, here is the information.
My English is not very good, for that reason sometimes I do not understand je.
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Micron S8 SDRAM DIE=6Gb M5=x3 M6=x0 M7=x0 M8
(bootloader) ram[1]: =x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: ---
(bootloader) cid: 0x0007
(bootloader) channelid: 0x51
(bootloader) uid: 368A71011E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: -----
(bootloader) meid:
(bootloader) date: 12-13-2016
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Feb 5 7:26: 3 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia/clark:6.0/M
(bootloader) ro.build.fingerprint[1]: PHS24.49-20-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_reta
(bootloader) ro.build.version.full[1]: sia.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02R CLARK_APAC_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-ga389d53 (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:27:17 CST 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=7ea7c4c-dirty
(bootloader) hyp.git: git=7ea7c4c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retapac

AlexAndroid said:
Yes, here is the information.
My English is not very good, for that reason sometimes I do not understand je.
(bootloader) date: 12-13-2016
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia/clark:6.0/M
(bootloader) ro.build.fingerprint[1]: PHS24.49-20-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_reta
(bootloader) ro.build.version.full[1]: sia.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
Click to expand...
Click to collapse
This is the key info... You currently have MPHS24.49-20-16 that was released in January/February, problem is we don't have that firmware and don't know when/if we will get it. That said you should be able to use XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and flash it manually with fastboot. Make sure to open the cmd window as Administrator.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- If this step fails, try once more, then continue
fastboot flash bootloader bootloader.img <- If this step fails, try once more, then continue
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 (Verify # of sparsechunks, match the number with what is in ROM image)
fastboot flash modem NON-HLOS.bin <- If this step fails, try once more, then continue
fastboot erase modemst1 <- If this step fails, try once more, then continue
fastboot erase modemst2 <- If this step fails, try once more, then continue
fastboot flash fsg fsg.mbn <- If this step fails, try once more, then continue
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot fb_mode_clear
fastboot reboot

acejavelin said:
This is the key info... You currently have MPHS24.49-20-16 that was released in January/February, problem is we don't have that firmware and don't know when/if we will get it. That said you should be able to use XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and flash it manually with fastboot. Make sure to open the cmd window as Administrator.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- If this step fails, try once more, then continue
fastboot flash bootloader bootloader.img <- If this step fails, try once more, then continue
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 (Verify # of sparsechunks, match the number with what is in ROM image)
fastboot flash modem NON-HLOS.bin <- If this step fails, try once more, then continue
fastboot erase modemst1 <- If this step fails, try once more, then continue
fastboot erase modemst2 <- If this step fails, try once more, then continue
fastboot flash fsg fsg.mbn <- If this step fails, try once more, then continue
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thank you very much, I will try with this firmware. Can you do it even though my bootloader is locked?

AlexAndroid said:
Thank you very much, I will try with this firmware. Can you do it even though my bootloader is locked?
Click to expand...
Click to collapse
Stock firmware images are digitally signed, so yes, you can flash them with a locked bootloader., but downgrading is tricky even with an unlocked bootloader. The key here us to just get it bootable.

acejavelin said:
Stock firmware images are digitally signed, so yes, you can flash them with a locked bootloader., but downgrading is tricky even with an unlocked bootloader. The key here us to just get it bootable.
Click to expand...
Click to collapse
Unfortunately it did not work, boot.img, recovery.img and the following throw
sending 'boot' (40960 KB)... OKAY [ 3.857s]
writing 'boot'... INFOPreflash validation failed
FAILED (remote failure)
finished. total time: 4.550s

AlexAndroid said:
Unfortunately it did not work, boot.img, recovery.img and the following throw
sending 'boot' (40960 KB)... OKAY [ 3.857s]
writing 'boot'... INFOPreflash validation failed
FAILED (remote failure)
finished. total time: 4.550s
Click to expand...
Click to collapse
Then your choices are Moto repair or wait for the 20-16 firmware to be released.

acejavelin said:
Then your choices are Moto repair or wait for the 20-16 firmware to be released.
Click to expand...
Click to collapse
Do Motorola's official technical services have the necessary firmware?

AlexAndroid said:
Do Motorola's official technical services have the necessary firmware?
Click to expand...
Click to collapse
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/

If you are in warranty and u haven't unlocked your boot loader yet you can give silly reason's like i revived updates last night but battery was low and while updating it turned off and now my phone isn't booting up

acejavelin said:
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
Click to expand...
Click to collapse
Hello, finally I take the equipment to an official technical service of Motorola, where they told me that they could not repair it since the cell phone did not take Software. Is this possible or would it be that the technical service did not have the necessary software version?

acejavelin said:
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
Click to expand...
Click to collapse
Good afternoon, I return the subject after a long time since yesterday I thought to try again, and I found that the cell now turns on, but when trying to complete the initial configuration, after choosing the language gives me to select the wifi networks, where it does not detect any, and I do not enable the jump or forward button, and I'm stuck there again, it's very strange, as soon as I enter that screen, it gives me the option to add a new network, and I can see that says Mac Address with pure zeros, as if it did not have MAC.
If I try to enter the recovery, now I see "No Command" (previously not directly entered), and there is no way to skip this "No Command", I have tried all the methods that appear online.
EDIT: I was able to get into recovery, but I do not know if it can help me now.
Any ideas? he seems to be brigado, but not as much as before

Flash the right modem for your region in fastboot. You should repeat the fastboot command "fastboot flash modem NON-HLOS.bin" at least two times because the first time it won't "stick". After you'll have to execute "fastboot erase modemst1" and "fastboot erase modemst2" commands and your wi-fi and data signal should return.

Edvin73 said:
Flash the right modem for your region in fastboot. You should repeat the fastboot command "fastboot flash modem NON-HLOS.bin" at least two times because the first time it won't "stick". After you'll have to execute "fastboot erase modemst1" and "fastboot erase modemst2" commands and your wi-fi and data signal should return.
Click to expand...
Click to collapse
I still have a problem, when the device is turned on, it always turns on Bootloader mode, and I have to select "Start" to turn it on. This is why when you want to upgrade to Android 7 via OTA, when the device is restarted during installation, it enters Bootloader mode, select "Start", restarts the update, restarts in Bootloader, and remains in an infinite cycle.
Is there a solution to this? I have already activated USB debugging in order to unlock the Bootloader.
Thank you!!

[SOLVED] [XT1572] Fully bricked or is there a solution ?

Hey there,
To make it short, the phone was rooted, bootloader unlocked, and it was on Resurrection Remix (don't know which one, it was Nougat 7.1.2).
I tried to restore it back to stock, lock the bootloader etc (following this guide : https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 which has files for xt1572 too ).
During the process, I got the error that a lot of people get about the Preflash validation error and yet i went through, except that I still locked at the end (I did not notice the Note about it below the command lines, I so regret it).
I also flashed the original Motorola logo (instead of "Bootloader is unlocked"), but I don't think this has anything to do with the fact that it got bricked (I can be wrong though).
Now, I can't access the phone through the cable. adb devices (with killing and restarting server) doesn't detect anything, I'm just stuck on the big Motorola logo splash screen.
Anyone has any idea on any possible way to unbrick it ? (I heard about qualcomm hsusb something but I'm just not sure where it can lead)
Thanks !

@pef6000
Bootloader is locked? What is status code...?

can't you use fastboot (from device turned off hold power + vol down) and flash stock motorola rom?

Hey there, thanks for your answers.
I can't access bootloader nor fastboot. adb doesn't show any device anymore.
I cannot even turn on or off the phone. It just reboots even if I long-press the power button. It just boots back up, and I can only leave it like this until battery is depleted.

Hold power, when screen turn off hold only vol-. It should go to bootloader.
Check and post here BL status. @pef6000
---------- Post added at 11:04 PM ---------- Previous post was at 10:58 PM ----------
Btw, if you will go to bootloader mode(locked) - you can only flash again stock 6.0.1(newest).
Without bootloader and gpt.
Check how many sparsechunks you have in zip file, I think from 0 to 11.

Sorry for being late. I tried that yesterday, but one problem after another, Windows died
I'll pass some time on it whenever I get the computer working.
I tried starting in BL and it worked !
I think the fact that it wasn't working before was due to the phone bootlooping directly on splash screen (maybe, I don't know).
Here, battery was dead since I couldn't turn it off. So I plugged the phone in while keeping vol- pressed, and it booted immediately in.
Couldn't get a hold of the status code though, the computer rebooted and crashed, so I had something else in mind, sorry :/
Anyway, I'll do that whenever I can, thanks for your help !

Here again. I accessed bootloader and I get :
AP Fastboot Flash Mode (Secure)
[…]
Console [NULL]: null
Battery OK (charging)
Device is UNLOCKED. Status Code: 3
Software status: Modified
Before this problem, when I tried to flash everything, I have parsechunks from 0 to 8, not 11.
Now, I don't really know what to do. Should I do everything back again with a 6.0.1 zip ?

pef6000 said:
Should I do everything back again with a 6.0.1 zip ?
Click to expand...
Click to collapse
Yes.
Without bootloader, gpt and Don't lock BootLoader.

Hey.
I did it, didn't lock bootloader, didn't flash bootloader.img nor gpt.bin, but it still freezes on the splash screen logo. I suppose it woudn't take as much as 15 to 30 minutes to switch from that splash screen to any other screen.
The bootloader is still accessible, and I still have the same things (unlocked, status 3, etc).
Am I doing something wrong ? :/

What is your model and what rom are you flashing?
What do you have on pc after: "fastboot getvar all"? @pef6000

It's a XT1572, European (got it in France).
I'm trying to flash the one for XT1572 in the link with the instructions : https://dl.prazaar.de/?dir=Android/XT1572/Factory/6.0.1/MPHS24.107-58-5_September_2016
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA3910197I
(bootloader) cid: 0x0007
(bootloader) channelid: 0x42
(bootloader) uid: 42C5D7001E000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [...]
(bootloader) meid:
(bootloader) date: 11-12-2015
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jul 6 10:58:55 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_reteu/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_reteu
(bootloader) ro.build.version.full[1]: .reteu.en.EU
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02R CLARK_EMEA_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g0ec7138 (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 Tue Nov 3 05:05:40 CST 2015
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=7ea7c4c-dirty
(bootloader) hyp.git: git=7ea7c4c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 2/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retfr
all: listed above
finished. total time: 0.242s

Did you flash: boot, recovery, all sparsechunks(0-11), modem, all erases? Each command ended with OK? @pef6000

Yes, I did all of this, everything turns out ok except one error (the Preflash Validation).
Now that I read it again, the post says it happens on gpt.bin, except I didn't flash it as you said.
I just did it again and I get it again at this step :
> fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41699 KB)...
OKAY [ 0.923s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.981s
Do I also not flash the modem ? :/
EDIT :
Btw, the bootloader log on the phone says "Image is too large" after the "cmd: flash:modem" line.

pef6000 said:
It's a XT1572, European (got it in France).
Click to expand...
Click to collapse
You should edit your post and remove the IMEI number...

Is it possible your last stock system was 6.0?
Download and try to flash reteu 24.49-18-4, still without BL, gpt, oem.
(I don't know how many sparsechunks there is, check it).
https://mirrors.lolinet.com/firmware/moto/clark/official/RETEU/ @pef6000

dzidexx said:
Is it possible your last stock system was 6.0?
Download and try to flash reteu 24.49-18-4, still without BL, gpt, oem.
(I don't know how many sparsechunks there is, check it).
https://mirrors.lolinet.com/firmware/moto/clark/official/RETEU/ @pef6000
Click to expand...
Click to collapse
From the getvar output, the bootloader is on 6.0
(bootloader) ro.build.fingerprint[0]: motorola/clark_reteu/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_reteu
(bootloader) ro.build.version.full[1]: .reteu.en.EU
Click to expand...
Click to collapse
on MPHS24.49-18-4... I would suggest using the same version or XT1572_CLARK_RETEU_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and NOT 6.0.1. The 6.0.1 versions were only for certain variants, and I do not know if the RETFR ones had that.
And don't skip the bootloader or gpt UNLESS they actually fail... It is best to do it like this:
Also, if possible boot into the factory recovery and perform a full factory reset before beginning.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 [Verify number of sparse chunks and make sure you are doing the correct #]
fastboot flash modem NON-HLOS.bin [May need to be done more 2 or 3 times to "take", make sure it returns an "OKAY"]
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
My 2 cents worth... hope it helps.

@acejavelin Oh damn, thank you. I thought I checked correctly but I didn't notice the IMEI in there.
Thank you both for your help. Phone booted up on original rom, I'm happy
I'll mark this post as Solved, but I have a quick question : Can I use the XT1575 logo.bin found here :https://forum.xda-developers.com/mo...o-remove-unlocked-bootloader-warning-t3201141
Or is it better not to do so ?

Yes you can.
Or any from here:
https://forum.xda-developers.com/moto-x-style/themes-apps/boot-animation-logo-bin-t3558942 @pef6000
Btw.
You flashed ...18-8 or 18-4? Maybe someone will need it in future.

dzidexx said:
Yes you can.
Or any from here:
https://forum.xda-developers.com/moto-x-style/themes-apps/[email protected]
Btw.
You flashed ...18-8 or 18-4? Maybe someone will need it in future.
Click to expand...
Click to collapse
@pef6000 Any of these or the one you mentioned is fine.

Sorry for the late answer, I flashed the 18-8 in the end.
Thanks again, I'll mark this as solved !

Flashing back to Stock, Trying to understand Errors

So I ran into some issues installing LOS15 and flashed back to stock using POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
Being paranoid I am concerned about the errors I have gotten, mainly because if the ROM messed with my system and I cannot replace it, well, who know what nefarious actions might be taking place.
I have booted the system and it works fine, but again, just being cautious.
Here are the errors:
Code:
[B]fastboot flash partition gpt.bin[/B]
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.074s
[B]fastboot flash bootloader bootloader.img[/B]
sending 'bootloader' (5115 KB)...
OKAY [ 0.233s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.510s
[B]sudo fastboot flash boot boot.img [/B]
ending 'boot' (16384 KB)...
OKAY [ 0.771s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.442s]
finished. total time: 1.213s
[B]sudo fastboot flash recovery recovery.img [/B]
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.973s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.532s]
[B]
sudo fastboot erase customize[/B]
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
[B]sudo fastboot erase clogo [/B]
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s

Is your moto g5 plus reteu?

InsaneNexuS said:
Is your moto g5 plus reteu?
Click to expand...
Click to collapse
I guess you meant retail? Yeah, it is retail. No amazon ads.

Well I need to know if it was reteu software channel. Otherwise it wont work for you. Maybe because your not flashing the right files? Mine was RETEU, which means its a european model.

No, not European. US Version. At least I bought it on Amazon in the US.
I want to add that I have flashed the stock before and did not get these errors. It only happened after I flashed LOS15.

Well then you need to find the right firmware for you US model. And start with locking the bootloader. And flash every line one by one (copy paste). Dont copy all of them and paste them otherwise it wont work. You really have to do it one by one.
Bootloader relock commands:
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
After you locked the bootloader start flashing the firmware. Use this site to find the right firmware:https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I gues you should try the one that says RETAIL in the name.
---------- Post added at 23:01 ---------- Previous post was at 22:59 ----------
NODE06 said:
No, not European. US Version. At least I bought it on Amazon in the US.
I want to add that I have flashed the stock before and did not get these errors. It only happened after I flashed LOS15.
Click to expand...
Click to collapse
Well if you have done it before then I guess I don't really know what the problem is

Here's what happened putting in that code:
Code:
sudo fastboot oem lock
[sudo] password for user:
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.002s]
finished. total time: 0.002s
sudo fastboot oem lock
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.012s]
finished. total time: 0.012s
sudo fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (75638 KB)...
OKAY [ 3.432s]
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: 3.499s
I guess I would just like to know why this is happening. like what does "(bootloader) Security version downgrade" even mean?

Your are downgrading, trying to flash a version of firmware that is older than what is installed already.
You either need a newer factory image, or are using the incorrect one. "Preflash validation failed" is basically saying the digitial signature doesn't match what is already there or is older than what you have currently.
Exactly what image are you flashing and what is the output of "fastboot getvar all" except mask out the IMEI number(s).

acejavelin said:
Your are downgrading, trying to flash a version of firmware that is older than what is installed already.
You either need a newer factory image, or are using the incorrect one. "Preflash validation failed" is basically saying the digitial signature doesn't match what is already there or is older than what you have currently.
Exactly what image are you flashing and what is the output of "fastboot getvar all" except mask out the IMEI number(s).
Click to expand...
Click to collapse
Yeah, I thought that was the issue. I guess I just kind of fracked my phone then because I installed Lineage 15.0 which uses Android O. I guess there will not be a newer firmware image anytime soon.
The flash back to stock works but I would rather have everything original. This code is with Resurrection ROM. Will be glad if you can explain any of it!
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(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: MSM8953
(bootloader) serialno: ZY224538B8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8a
(bootloader) uid: 7C6B3F8100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-18-2017
(bootloader) sku: XT1687
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 3:41:43 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:7.0/NPN25.1
(bootloader) ro.build.fingerprint[1]: 37-35/37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.37.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: M8953_02.03.07.08R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g6508460 (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]: ue Feb 14 06:47:06 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.026s

NODE06 said:
Yeah, I thought that was the issue. I guess I just kind of fracked my phone then because I installed Lineage 15.0 which uses Android O. I guess there will not be a newer firmware image anytime soon.
The flash back to stock works but I would rather have everything original. This code is with Resurrection ROM. Will be glad if you can explain any of it!
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(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: MSM8953
(bootloader) serialno: ZY224538B8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8a
(bootloader) uid: 7C6B3F8100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-18-2017
(bootloader) sku: XT1687
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 3:41:43 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:7.0/NPN25.1
(bootloader) ro.build.fingerprint[1]: 37-35/37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.37.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: M8953_02.03.07.08R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g6508460 (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]: ue Feb 14 06:47:06 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.026s
Click to expand...
Click to collapse
No, you don't understand... Your "firmware" in this case means bootloader/partition table/radios, it has nothing to do with any custom ROM you would flash, but the last stock firmware you had installed, which in your case was NPN25.137-35 (Blur_Version.25.11.37.potter.retail.en.US) and a radio of M8953_02.03.07.08R POTTER_NA_CUST, so you need that version or higher.
Which seems odd, because that is newer than my version which is completely stock and untouched.... NPNS25.137-33-5/M8953_02.03.07.06R... So I am assuming you were on a special Verizon test build? You will need one of those except the same version or newer than when you were last stock.

acejavelin said:
No, you don't understand... Your "firmware" in this case means bootloader/partition table/radios, it has nothing to do with any custom ROM you would flash, but the last stock firmware you had installed, which in your case was NPN25.137-35 (Blur_Version.25.11.37.potter.retail.en.US) and a radio of M8953_02.03.07.08R POTTER_NA_CUST, so you need that version or higher.
Which seems odd, because that is newer than my version which is completely stock and untouched.... NPNS25.137-33-5/M8953_02.03.07.06R... So I am assuming you were on a special Verizon test build? You will need one of those except the same version or newer than when you were last stock.
Click to expand...
Click to collapse
I use Consumer Cellular, and the only thing I did that started screwing everything up was install Lineage 15 which is based on Android Oreo. Could that have change it to the newer version?

NODE06 said:
I use Consumer Cellular, and the only thing I did that started screwing everything up was install Lineage 15 which is based on Android Oreo. Could that have change it to the newer version?
Click to expand...
Click to collapse
I don't know about Consumer Cellular but I think they are an AT&T MVNO so it probably isn't relevant.
Any custom ROM you flashed is not relevant either... to go back to stock you must flash a same or newer firmware than what you have, and you are confusing what that means. Lineage, or any custom ROM, does not modify your firmware, only your system and boot partitions, your firmware is in the bootloader/radios and is related to your gpt.bin (the partition table). You need a factory image that is the same or newer than what you have, which I don't think is available since Moto isn't very forthcoming with factory images (and your version is very new, newer than mine), but this has nothing to do with flashing a custom ROM.
I haven't tried this on this device, but on older Moto devices you would downgrade by flashing the firmware but skipping gpt.bin and bootloader.img (you also cannot relock the booloader) and continuing with the other parts of the firmware image. Yes, the booloader and partition table no longer match the radios and rest of the ROM, but that usually fixes itself during the next major OTA update.

acejavelin said:
I don't know about Consumer Cellular but I think they are an AT&T MVNO so it probably isn't relevant.
Any custom ROM you flashed is not relevant either... to go back to stock you must flash a same or newer firmware than what you have, and you are confusing what that means. Lineage, or any custom ROM, does not modify your firmware, only your system and boot partitions, your firmware is in the bootloader/radios and is related to your gpt.bin (the partition table). You need a factory image that is the same or newer than what you have, which I don't think is available since Moto isn't very forthcoming with factory images (and your version is very new, newer than mine), but this has nothing to do with flashing a custom ROM.
I haven't tried this on this device, but on older Moto devices you would downgrade by flashing the firmware but skipping gpt.bin and bootloader.img (you also cannot relock the booloader) and continuing with the other parts of the firmware image. Yes, the booloader and partition table no longer match the radios and rest of the ROM, but that usually fixes itself during the next major OTA update.
Click to expand...
Click to collapse
I understand what you are saying, but I am telling you I flashed the same stock firmware a month ago with no issues.
The only thing that changed everything was installing the Lineage ROM. Could the Linage ROM have messed up my partition tables? I was having issues when I tried to install it relating to data encryption. But I have no idea how I could have flashed a newer version of anything. This is why I am so confused.

NODE06 said:
I understand what you are saying, but I am telling you I flashed the same stock firmware a month ago with no issues.
The only thing that changed everything was installing the Lineage ROM. Could the Linage ROM have messed up my partition tables? I was having issues when I tried to install it relating to data encryption. But I have no idea how I could have flashed a newer version of anything. This is why I am so confused.
Click to expand...
Click to collapse
Eh, not mess up, but it could change the filesystem type for a partition or two, sometimes system or data. You could use TWRP and try a repair on them.
Can't you just restore a TWRP backup first, then flash stock?
Sorry, but I may be a considered a wizard by some with some Moto devices, but I am really new to this one and it seems to have a few different quirks. Hopefully someone else can jump in here.
Are you using an official image? They usually contain a file called flashfile.xml, that will tell you what commands you need to enter to flash and what version it is, the above instructions are to relock a stock device, not return to stock.

acejavelin said:
Eh, not mess up, but it could change the filesystem type for a partition or two, sometimes system or data. You could use TWRP and try a repair on them.
Can't you just restore a TWRP backup first, then flash stock?
Sorry, but I may be a considered a wizard by some with some Moto devices, but I am really new to this one and it seems to have a few different quirks. Hopefully someone else can jump in here.
Are you using an official image? They usually contain a file called flashfile.xml, that will tell you what commands you need to enter to flash and what version it is, the above instructions are to relock a stock device, not return to stock.
Click to expand...
Click to collapse
He's flashing a stock.zip I believe.

aaronrw said:
He's flashing a stock.zip I believe.
Click to expand...
Click to collapse
Not with fastboot...
@NODE06 What exactly are you flashing and how?

acejavelin said:
Not with fastboot...
@NODE06 What exactly are you flashing and how?
Click to expand...
Click to collapse
I am flashing
POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
on Linux using ADB, yes, fastboot. I have done it often enough on this phone and used to do it on my G4.
I am wondering, looking at the flashfile.xml, if I should flash them in the same order they are listed in that file. But again, it does not make sense since the only think I did was install Lineage 15 when I was running Resurrection. I will try again to repair with TWRP, maybe I am missing something.
I am back on Resurrection and things are running fine, but I am concerned now that Lineage 15 might be doing some really weird stuff.

I notice the flashfile.xml has
Code:
<sparsing enabled="true" max-sparse-size="536870912"/>
<step operation="getvar" var="max-sparse-size"/>
in it.
Do they matter at all?
When I run the fastboot command I get a different number
Code:
sudo fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.008s

So, I fixed it. And yeah, you need to fastboot stock in the same order as the flashfile.xml and include the getvar max-sparse-size. Here is what worked for me. I got no errors besides the "bad key" for boot and recovery images.
Code:
sudo fastboot getvar max-sparse-size
sudo fastboot oem fb_mode_set
sudo fastboot flash partition gpt.bin
sudo fastboot flash bootloader bootloader.img
sudo fastboot flash modem NON-HLOS.bin
sudo fastboot flash fsg fsg.mbn
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot flash dsp adspso.bin
sudo fastboot flash logo logo.bin
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash system system.img_sparsechunk.3
sudo fastboot flash system system.img_sparsechunk.4
sudo fastboot flash oem oem.img
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase DDR
sudo fastboot oem fb_mode_clear
sudo fastboot reboot

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.