Database Develop

xt1096 moto x 2nd gen bricked

moto x 2nd gen
was trying to upgrade to marshmallow and the person i bought from gave me the xt1092 link. went on with it and now i have a paperweight stuck in fastboot mode.. tried restoring back to xt1096 via fastboot, mfastboot and rsdlite
while doing it i am getting version downgraded for primary gpt, hab error, invalid piv image
any guru who can provide any help would be appreciated
get var all data below
C:\Phone\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x4
(bootloader) emmc: 16GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA99218ZUS
(bootloader) cid: 0x0002
(bootloader) channelid: 0x83
(bootloader) uid: 2EEA0E0D0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 990005080698989
(bootloader) meid:
(bootloader) date: 10-18-2014
(bootloader) sku: XT1096
(bootloader) iccid: 89148000001390856408
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Nov 19 18:48:29 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/victara_verizon/victara:5
(bootloader) ro.build.fingerprint[1]: .0/LXE22.46-11/11:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.11.victara_ver
(bootloader) ro.build.version.full[1]: izon.verizon.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-ga88ac50 ([email protected]
(bootloader) kernel.version[1]: ilclbld73) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Nov 20 04:01:54 CST 2014
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: vzw
all: listed above

Try unlocking your bootloader from motorola site, last o heared Verizon started too unlock bootloader of x2 from mototola site. If you can unlock bootloader do it and after that flash xt1092 rom it will pass through.
astalavistadear said:
moto x 2nd gen
was trying to upgrade to marshmallow and the person i bought from gave me the xt1092 link. went on with it and now i have a paperweight stuck in fastboot mode.. tried restoring back to xt1096 via fastboot, mfastboot and rsdlite
while doing it i am getting version downgraded for primary gpt, hab error, invalid piv image
any guru who can provide any help would be appreciated
get var all data below
C:\Phone\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x4
(bootloader) emmc: 16GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA99218ZUS
(bootloader) cid: 0x0002
(bootloader) channelid: 0x83
(bootloader) uid: 2EEA0E0D0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 990005080698989
(bootloader) meid:
(bootloader) date: 10-18-2014
(bootloader) sku: XT1096
(bootloader) iccid: 89148000001390856408
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Nov 19 18:48:29 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/victara_verizon/victara:5
(bootloader) ro.build.fingerprint[1]: .0/LXE22.46-11/11:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.11.victara_ver
(bootloader) ro.build.version.full[1]: izon.verizon.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-ga88ac50 ([email protected]
(bootloader) kernel.version[1]: ilclbld73) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Nov 20 04:01:54 CST 2014
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: vzw
all: listed above
Click to expand...
Click to collapse

Salik Iqbal said:
Try unlocking your bootloader from motorola site, last o heared Verizon started too unlock bootloader of x2 from mototola site. If you can unlock bootloader do it and after that flash xt1092 rom it will pass through.
Click to expand...
Click to collapse
its giving an error
"enable oem unlock from developer options"

bump

Did you go into developer options in settings and check oem unlock?
astalavistadear said:
bump
Click to expand...
Click to collapse

Archangel said:
Did you go into developer options in settings and check oem unlock?
Click to expand...
Click to collapse
Since he is stuck in fastboot, I assume not.
Just reflash stock whatever firmware you were on before you tried upgrading. You can do this with all fastboot commands. Your phone is far from a "paper weight" if you can still get into fastboot, most classify this as a "soft brick."
Instructions on flashing the stock firmware can be found on the Moto X FAQ. https://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769
Alternatively, I'm a huge fan of House of Moto: http://www.droidrzr.com/topic/61124-house-of-moto-43/ - automates a lot of the flashing process for you. I like to always have an install of House of Moto ready to roll incase of soft bricking.

xKroniK13x said:
Since he is stuck in fastboot, I assume not.
Just reflash stock whatever firmware you were on before you tried upgrading. You can do this with all fastboot commands. Your phone is far from a "paper weight" if you can still get into fastboot, most classify this as a "soft brick."
Instructions on flashing the stock firmware can be found on the Moto X FAQ. https://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769
Alternatively, I'm a huge fan of House of Moto: http://www.droidrzr.com/topic/61124-house-of-moto-43/ - automates a lot of the flashing process for you. I like to always have an install of House of Moto ready to roll incase of soft bricking.
Click to expand...
Click to collapse
hi.. sorry for such a late and random reply... had been stuck in a family emergency
i am getting the same error by your methods..
failed- version downgraded for boot

astalavistadear said:
hi.. sorry for such a late and random reply... had been stuck in a family emergency
i am getting the same error by your methods..
failed- version downgraded for boot
Click to expand...
Click to collapse
Sounds like you probably aren't using the correct firmware version.

mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (256352 KB)...
OKAY [ 9.646s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.762s

astalavistadear said:
hi.. sorry for such a late and random reply... had been stuck in a family emergency
i am getting the same error by your methods..
failed- version downgraded for boot
Click to expand...
Click to collapse
i flashed a wrong version earlier as the guy i bought from said it was ok to flash xt1092 on xt1096.. 1096 wasnt getting updates post lollipop... and was stuck... now when m trying to get 1096 to flash back... m stuck with these errors

Unlock bootloader moto x 2014 - XT1097

I recently bought this used cell phone, with android 5.1, I upgraded to the 6 stock (original motorola) but I now want to install a custom ROM, and for this I need to unlock the bootloader, but when I try to do this, this message appears in the command prompt "could Not get unlock data! ", I even tried a crazy on the internet some method to solve but what I found said that I should downgrade and go up rom, but I can not install another rom by RSD lite, I would like a method to be able Do the bootloader unlock and do root, exchange rom these things

roneyss93 said:
I recently bought this used cell phone, with android 5.1, I upgraded to the 6 stock (original motorola) but I now want to install a custom ROM, and for this I need to unlock the bootloader, but when I try to do this, this message appears in the command prompt "could Not get unlock data! ", I even tried a crazy on the internet some method to solve but what I found said that I should downgrade and go up rom, but I can not install another rom by RSD lite, I would like a method to be able Do the bootloader unlock and do root, exchange rom these things
Click to expand...
Click to collapse
You must have the unlock.bin from motorola official site to unlock bootloader.
After send the unlock.bin to your mail you move it to adb folder etc.

papsr6 said:
You must have the unlock.bin from motorola official site to unlock bootloader.
After send the unlock.bin to your mail you move it to adb folder etc.
Click to expand...
Click to collapse
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock

roneyss93 said:
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock
Click to expand...
Click to collapse
Did you enable Developer Options by going to Settings, About, tap Build Number 7 times, then go back, enable allow bootloader unlock and Android Debugging.

roneyss93 said:
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock
Click to expand...
Click to collapse
Do it again you do something wrong.
I do the same and my fault is the wrong copy of numbers when i copy from commant window.

Gus Ghanem said:
Did you enable Developer Options by going to Settings, About, tap Build Number 7 times, then go back, enable allow bootloader unlock and Android Debugging.
Click to expand...
Click to collapse
I do exactly this, and it continues to give error

papsr6 said:
Do it again you do something wrong.
I do the same and my fault is the wrong copy of numbers when i copy from commant window.
Click to expand...
Click to collapse
I can not even get the numbers that we put on the Motorola site, I have unlocked Motorola before, however this nor give me the codes when I put the command to generate the codes

roneyss93 said:
I do exactly this, and it continues to give error
Click to expand...
Click to collapse
Do this just to get some info, no need to paste it here:
fastboot getvar all
In bootloader mode of course.
EDIT: You can get the latest fastboot and adb from here:
https://developer.android.com/studio/releases/platform-tools.html

Gus Ghanem said:
Do this just to get some info, no need to paste it here:
fastboot getvar all
In bootloader mode of course.
EDIT: You can get the latest fastboot and adb from here:
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Open again the CMD, the most updated according to the link that you sent me. And as a response the commands had this.
D:\Programas\Celular\MOTO X 2\root\platform-tools>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: 6018
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: 0432146139
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: EC13870C0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 353320060936783
(bootloader) meid:
(bootloader) date: 2014-10-24
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jul 5 12:11:27 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retbr/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: br.retbr.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_S
(bootloader) version-baseband[1]: INGLELA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:44:51 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V60.18-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.18-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V60.18-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.18-0-g4ad5029
(bootloader) aboot.git: git=MBM-NG-V60.18-0-g3b3b501
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.229s
D:\Programas\Celular\MOTO X 2\root\platform-tools>fastboot devices
0432146139 fastboot
D:\Programas\Celular\MOTO X 2\root\platform-tools>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Could not get unlock data!
OKAY [ 0.036s]
finished. total time: 0.036s
D:\Programas\Celular\MOTO X 2\root\platform-tools>
Remember that yes "OEM unlock" and "USB debugging" was enabled. As shown in the image.

Here is mine
(bootloader) version: 0.5
(bootloader) version-bootloader: 6100
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno:
(bootloader) cid: 0x000E
(bootloader) channelid: 0x80
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-12-2015
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 1 15:55:30 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retca/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: ca.retca.en.CA
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_R
(bootloader) version-baseband[1]: ETCA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld72) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:53:00 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V61.00-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V61.00-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V61.00-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V61.00-0-gacbc999
(bootloader) aboot.git: git=MBM-NG-V61.00-0-g130760b
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: retca
Looks like your bootloader is older, but it shouldn't matter, I think I unlocked mine before the Android 6.0 update, I then relocked it, and unlocked it again a second time. I'm sure a lot of RETBR phones have been unlocked around here. I just can't see what the problem is. But don't try downgrading, you may brick the phone. I don't know what else to suggest. I'm sure you've installed the Motorola USB drivers, but I don't think that's the issue.

Try the Motorola (Lenovo) forums, you can submit your getvar to them, and they will send you an unlock code in a few days:
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
Good Luck!
They have forums in Portugese.

Gus Ghanem said:
Here is mine
(bootloader) version: 0.5
(bootloader) version-bootloader: 6100
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno:
(bootloader) cid: 0x000E
(bootloader) channelid: 0x80
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-12-2015
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 1 15:55:30 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retca/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: ca.retca.en.CA
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_R
(bootloader) version-baseband[1]: ETCA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld72) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:53:00 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V61.00-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V61.00-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V61.00-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V61.00-0-gacbc999
(bootloader) aboot.git: git=MBM-NG-V61.00-0-g130760b
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: retca
Looks like your bootloader is older, but it shouldn't matter, I think I unlocked mine before the Android 6.0 update, I then relocked it, and unlocked it again a second time. I'm sure a lot of RETBR phones have been unlocked around here. I just can't see what the problem is. But don't try downgrading, you may brick the phone. I don't know what else to suggest. I'm sure you've installed the Motorola USB drivers, but I don't think that's the issue.
Click to expand...
Click to collapse
I also do not know what the problem, I even tried to do the downgrade but does not accept any other android pq is not unlocked the bootloader.

My XT1063 goes "failed to validate boot image"

I am stuck in the AP Fastboot Flash Mode (S). Recovery, Factory, BP Tools doesn't function, giving the same line "failed to validate xxx image". I can't flash stock ROMs through fastboot commands, all of those were "Failed". The bootloader lock can't even be unlocked, same reason above. Anybody from XDA can help me with this? I desperately tried almost everything on the forum and nothing has progressed so far. Here is the getvar-all information of my device:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4887
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D325JTJ
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: AAED95070F000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359297055872880
(bootloader) meid:
(bootloader) date: 01-21-2015
(bootloader) sku: XT1063
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Nov 1 4:11:27 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retuglb/titan_umts:
(bootloader) ro.build.fingerprint[1]: 6.0/MPBS24.65-34-4/6:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.4.titan_retug
(bootloader) ro.build.version.full[1]: lb.retuglb.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8626BP_1032.3116.99.00R RETUSA_GLB_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g495dfd8 ([email protected]
(bootloader) kernel.version[1]: ilclbld36) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Wed Aug 24 07:20:10 CDT 2016
(bootloader) sdi.git: sdi.git
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) aboot.git: git=MBM-NG-V48.87-0-g1b80345
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe:
(bootloader) productid:
(bootloader) sutinfo:
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 34.876s
I would really appreciate if somebody can solve this problem for me.

Hi! Sorry if im late, but did you use a 1 click flash tool? I reflashed 5.0.2 on my 1063 but i used a 6.0 flash tool and i got the same error! It got corrected once i used the correct flash tool

Angel064able said:
Hi! Sorry if im late, but did you use a 1 click flash tool? I reflashed 5.0.2 on my 1063 but i used a 6.0 flash tool and i got the same error! It got corrected once i used the correct flash tool
Click to expand...
Click to collapse
I used mfastboot and manually entered the codes. Where can I get that flashtool?

imnewbieplsnokick said:
I used mfastboot and manually entered the codes. Where can I get that flashtool?
Click to expand...
Click to collapse
I used this video:youtu.be/Jav4tIv5sCI
Credit to the creator.

Did you downgraded the ROM of your device? The one which comes out of the box? The chances are this happens when you flash downgraded Stock flash files on upgraded bootloader. Try flashing latest factory image available for your device and firstly re flash partition, boot, recovery and bootloader files. Then go for all other flash files serially. This solution 'might' help. Otherwise there's nothing you can do.

imnewbieplsnokick said:
I used mfastboot and manually entered the codes. Where can I get that flashtool?
Click to expand...
Click to collapse
Did you solved your issue? My device went to the same state while I was trying to relock the bootloader and re-unlocking it fixed it!

Angel064able said:
Did you solved your issue? My device went to the same state while I was trying to relock the bootloader and re-unlocking it fixed it!
Click to expand...
Click to collapse
Sorry, I was quite busy with my mid-semester. I tried it out and it didn't work. I guess it is dead now. However, I am thinking about breaking the phone, turning it into a hard-brick state and then reincarnate it back to life. Is it possible?

After 10 Hours... I need help, please: "Invalid zip file format! error installing zip

After 10 Hours... I need help, please: "Invalid zip file format! error installing zip
Guys and gals - I just want to say in advance, thank you so much for your time and help with this, I really tried hard (over 10 hours) of referencing old xda forums and youtube videos, with nothing working so far.
Ok here it goes:
So I bought for a good price the Moto g5s Plus from ali express. Everything came fine, except one thing... it had a Chinese variant baseband flashed on the phone, which means everything worked normal except I couldn't update past 7.1.1
Baseband: M8937_37.13.03.53R Montana_Chinadsds_cust
The typical phones update to 8.1 oreo, so I want to jump on that wagon. It had been about 10 years since I've flashed or unlocked anything so I was happy to find through youtube and XDA that the process was easier. But the phone came with unlocked boot.
I put TWRP on there pretty easily and everything looked like it was going to be cake.
I was getting different errors after trying different tactics of flashing - everything from error 7, to error 1, to all kinds of errors that I've overcome... but when I'd solve one error, i'd get a different error...
I spent hours of diving through youtube / xda...
Eventually it led me to that I kept getting "cant unmount" error when trying to flash roms. I realized that tha phone isn't friendly to flashing because of something called "treble" or "trebling" - one of the developers here, liquidengineer, released a version of twrp to deal with it... but it didn't work for me.
To keep it short, after like 10 hours and nothing working... I then decided to do what was in this video:
Oreo 8.1 Stock ROM on Moto G5s Plus(English):
(notice url has a space between "youtube" and ".com")
youtube .com/watch?v=-f67lVbDqkc&t=3s
The video was nice because it was step by step. I chose to do it last because it involved using a custom script.
I followed all of the steps, the script ran. What I realized after is that this script only works if original stock roms, but I had this chinese custom rom/baseband.
In short, the script wiped everything... my partitions, files, etc...
TWRP Recovery still worked so I changed the format of the partitions to E2, then E4, that allowed me to use the phone as a drive and add the roms.
when I try to install any rom in TWRP 3.1.1-1... I now just get:
data successfully decrypted, new block device:
'/dev/block/dm-0'
Updating Partition Details....
...done
Successfully decrypted with default password.
Updating partition details...
...done
Full SELinux Support is present.
MTP Enabled
Installing zip file '/sdcard/arrow-v10.0-sanders-OFFICIAL-20200329-VANILLA.zip'
Invalid zip file format!
Error installign zip file '/sdcard/arrow-v10.0-sanders-OFFICIAL-20200329-VANILLA.zip'
Updating partition details...
...done.
It doesn't matter which rom i try to install.
Factory recovery doesn't work.
I also get a Motorola error that my phone has been unlocked and cant be trusted (bad ID).
I kept this post as short as I could, and didn't include all of the different attempts I tried.... but I am now completely lost as to what to do. Please, please help! I'll paypal someone $10 for the winning answer.
-----------------------------------
Current Bootscreen:
AP Fastboot Flash Mode (Secure)
BL: BC.06(*) (sha-865eb9a-diety. 2017-07-07 15:02:25)
Bandbase: M8937_37.13.03.53R Montana_Chinadsds_cust
Product/Variant: montana XT1799-2 64 gb p3
Serial #: I have one
CPU: MSM8937
eMMC: 64 GB Samsung etc...
DRAM: 4GB SAMSUNG etc...
Console [Null]: null
Tools Mode Confid: DISABLED
BATTERY OK
flashing_unlocked
Software status: modified
Connect USB Data Cable
(as of now - using TWRP 3.1.1-1 (boots normal))

If you really have the g5s plus aka sanders, and fastboot says Montana - someone flashed a g5s aka Montana firmware, which is never a good idea.
Try flashing Sanders firmware. If that doesn't work, enjoy the paperweight

Phazmos said:
If you really have the g5s plus aka sanders, and fastboot says Montana - someone flashed a g5s aka Montana firmware, which is never a good idea.
Try flashing Sanders firmware. If that doesn't work, enjoy the paperweight
Click to expand...
Click to collapse
yes that did look odd to me. I'm not so familiar with flashing firmware, do you have any good guidance with that?

smbfission said:
yes that did look odd to me. I'm not so familiar with flashing firmware, do you have any good guidance with that?
Click to expand...
Click to collapse
What's
Code:
fastboot getvar all
give you?
Please post it here after you remove the IMEI line

Hey shadow, i feel like an idiot. It's been 10 years since I've done any of this stuff and I'm realizing there are 2 things going on...
first - even though I bought a g5s Plus (also called sanders), that's not what I got. I unknowingly got a g5s (without the plus). Still, it should have installed probably anyway... regardless of whether it's a plus or not. So not sure why I get the errors - will that happen if the phone distro's don't match?
Finally, the moto g5s's are not all the same, because they each carry their own country. And in my case, I have the xt1799-2 - which is the chinese ZUI variant (customized lenovo version), which makes it more complex.
One guy sent me this: https://forum.xda-developers.com/moto-g5s/how-to/guide-moto-g5sxt179x-stock-rom-t3839003/amp/
however... the problem is because he uses the Chinese language firmware, it still seems he's stuck in 7.1.1 which won't even allow me to use custom roms because most of them rely on the 8.1 oreo firmware. Do you guys see holes in his approach?
Although to answer your question, do you want me just to run that function?
sd_shadow said:
What's
Code:
fastboot getvar all
give you?
Please post it here after you remove the IMEI line
Click to expand...
Click to collapse

smbfission said:
Hey shadow, i feel like an idiot. It's been 10 years since I've done any of this stuff and I'm realizing there are 2 things going on...
first - even though I bought a g5s Plus (also called sanders), that's not what I got. I unknowingly got a g5s (without the plus). Still, it should have installed probably anyway... regardless of whether it's a plus or not. So not sure why I get the errors - will that happen if the phone distro's don't match?
Finally, the moto g5s's are not all the same, because they each carry their own country. And in my case, I have the xt1799-2 - which is the chinese ZUI variant (customized lenovo version), which makes it more complex.
One guy sent me this: https://forum.xda-developers.com/moto-g5s/how-to/guide-moto-g5sxt179x-stock-rom-t3839003/amp/
however... the problem is because he uses the Chinese language firmware, it still seems he's stuck in 7.1.1 which won't even allow me to use custom roms because most of them rely on the 8.1 oreo firmware. Do you guys see holes in his approach?
Although to answer your question, do you want me just to run that function?
Click to expand...
Click to collapse
The getvar all give a lot of info about what is going on with the device.
So yes please.

Thanks so much in advance:
Just one note - even though it says I have a rom, i cant boot into it because as mentioned, i ran a script for g5s+ and it more or less corrupted it.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.06(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322WHXP7
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: 758A323800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) I removed this as mentioned
(bootloader) meid:
(bootloader) date: 09-06-2018
(bootloader) sku: XT1799-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 18 5: 1:50 UTC 1971"
(bootloader) ro.build.fingerprint[0]: motorola/montana_retcn_n/montana_n
(bootloader) ro.build.fingerprint[1]: :7.1.1/NZS26.86-128/112:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.112.montana_re
(bootloader) ro.build.version.full[1]: tcn.retcn.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8937_37.13.03.53R MONTANA_CHINADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g647ff94-0000
(bootloader) kernel.version[1]: 7-g13fa5e2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Wed Apr
(bootloader) kernel.version[3]: 11 23:05:29 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.06-0-g518a6f1
(bootloader) rpm.git: git=aa33522-dirty
(bootloader) tz.git: git=1fe3cc8-dirty
(bootloader) devcfg.git: git=1fe3cc8-dirty
(bootloader) keymaster.git: git=1fe3cc8-dirty
(bootloader) cmnlib.git: git=1fe3cc8-dirty
(bootloader) cmnlib64.git: git=1fe3cc8-dirty
(bootloader) prov.git: git=1fe3cc8-dirty
(bootloader) aboot.git: git=MBM-NG-VBC.06-0-g865eb9a-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retcn
all: listed above
finished. total time: 1.195s
sd_shadow said:
The getvar all give a lot of info about what is going on with the device.
So yes please.
Click to expand...
Click to collapse

smbfission said:
Thanks so much in advance:
Just one note - even though it says I have a rom, i cant boot into it because as mentioned, i ran a script for g5s+ and it more or less corrupted it.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.06(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322WHXP7
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: 758A323800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) I removed this as mentioned
(bootloader) meid:
(bootloader) date: 09-06-2018
(bootloader) sku: XT1799-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 18 5: 1:50 UTC 1971"
(bootloader) ro.build.fingerprint[0]: motorola/montana_retcn_n/montana_n
(bootloader) ro.build.fingerprint[1]: :7.1.1/NZS26.86-128/112:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.112.montana_re
(bootloader) ro.build.version.full[1]: tcn.retcn.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8937_37.13.03.53R MONTANA_CHINADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g647ff94-0000
(bootloader) kernel.version[1]: 7-g13fa5e2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Wed Apr
(bootloader) kernel.version[3]: 11 23:05:29 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.06-0-g518a6f1
(bootloader) rpm.git: git=aa33522-dirty
(bootloader) tz.git: git=1fe3cc8-dirty
(bootloader) devcfg.git: git=1fe3cc8-dirty
(bootloader) keymaster.git: git=1fe3cc8-dirty
(bootloader) cmnlib.git: git=1fe3cc8-dirty
(bootloader) cmnlib64.git: git=1fe3cc8-dirty
(bootloader) prov.git: git=1fe3cc8-dirty
(bootloader) aboot.git: git=MBM-NG-VBC.06-0-g865eb9a-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retcn
all: listed above
finished. total time: 1.195s
Click to expand...
Click to collapse
So, the correct Firmware for your device is Montana/RetCN/XT1799-2
https://mirrors.lolinet.com/firmware/moto/montana_retcn/official/RETCN/
which looks like has only been updated to 7.1.1 blur 26.68-117
You could try Retail software channel
https://mirrors.lolinet.com/firmware/moto/montana/official/RETAIL/
But I can't tell which model that is for...
RetEU is XT1793/XT1794
RetGB is XT1794
Doesn't look like there is a RetUS which is preferred if you live in the USA.
and I'm not seeing if there are any hardware differences between them.
I guess I would flash RetCN just to get it back to stock and working again.
If that goes good, try the Retail.
I've posted some general flashing instructions in
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039

sd_shadow said:
So, the correct Firmware for your device is Montana/RetCN/XT1799-2
https://mirrors.lolinet.com/firmware/moto/montana_retcn/official/RETCN/
which looks like has only been updated to 7.1.1 blur 26.68-117
You could try Retail software channel
https://mirrors.lolinet.com/firmware/moto/montana/official/RETAIL/
But I can't tell which model that is for...
RetEU is XT1793/XT1794
RetGB is XT1794
Doesn't look like there is a RetUS which is preferred if you live in the USA.
and I'm not seeing if there are any hardware differences between them.
I guess I would flash RetCN just to get it back to stock and working again.
If that goes good, try the Retail.
I've posted some general flashing instructions in
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Click to expand...
Click to collapse
Quick question - it seems that the Russians have a lot more support and roms for xt1799-2, because probably they buy from aliexpress. What I don't get is if you take this thread, https://4pda.ru/forum/index.php?showtopic=886009&st=260#entry76570414 (translate with google translate chrome extension)
people are installing custom ROM For XT1799-2
crDroid v4.7.2 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=89050911
crDroid v5.11 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=92946311
Do they first install the stock 7.1.1 firmware? and then the ROM, even though 4.7.2 is Android 8.1, and crDroid 5.11 is Android 9.0?
Does the firmware version need to match the ROM version?
Also, if i want to avoid risking to mess up the bootloader, can i just leave out the following:
fastboot of flash partition gpt.bin
fastboot of flash the bootloader bootloader.img

smbfission said:
Quick question - it seems that the Russians have a lot more support and roms for xt1799-2, because probably they buy from aliexpress. What I don't get is if you take this thread, https://4pda.ru/forum/index.php?showtopic=886009&st=260#entry76570414 (translate with google translate chrome extension)
people are installing custom ROM For XT1799-2
crDroid v4.7.2 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=89050911
crDroid v5.11 x64 https://4pda.ru/forum/index.php?showtopic=886009&view=findpost&p=92946311
Do they first install the stock 7.1.1 firmware? and then the ROM, even though 4.7.2 is Android 8.1, and crDroid 5.11 is Android 9.0?
Does the firmware version need to match the ROM version?
Also, if i want to avoid risking to mess up the bootloader, can i just leave out the following:
fastboot of flash partition gpt.bin
fastboot of flash the bootloader bootloader.img
Click to expand...
Click to collapse
I believe they are on stock 7.1.1, and installing the updated custom rom.
Likely there is not much of 7.1.1 left other than the bootloader.
Sent from my ali using XDA Labs

No IMEI after flashing the Stock from, Unable to Unlock the Bootloader

I was happy using Pixel Experience but Some bugs are worrying me so A week back I thought to go back to stock oreo and downloaded the Official Firmware lastest version for my G5s Plus, I flashed it using fastboot commands and now the only issue is that I do not have any IMEI in my phone, No network and No Signal.
Only thing I am getting is my Carrier Name Jio4G also it is able to detect my phone number. IMEI is correctly being shown using this command "$ fastboot getvar imei" but my device is unable to detect it. I have tried several time flashing with fastboot commands and Lenovo Moto Software Assistant, nothing worked for me.
I have also tried to resintall Pixel Experience ROM but no IMEI(Imei 0). I have also tried several other roms like RR and AOSP Ex also Havoc OS, nothing worked for me. I have also tried to flash TWRP backup of my Stock ROM but still IMEI 0. For your information I have also tried Pixel Experience rom with erasing modemst1 and modemst2 method, nothing worked.
Finally I thought to take it to the Moto Service Center, they flashed my devices with their software, but no success of retrieving the IMEI, even worse they gave me one more issue, which is now I am unable to unlock the bootloader with my unlock key. When I try to unlock it it says, "Code validation failure with status 7". When I try to generate new unlock data it says "Unlock data unavailable (bootloader) Failed.
I am really worried for my device because this is my only device and I am a student , I can not afford a new phone right now.
I will really appreciate your help for my entire lifetime, this issue is really making me sick.
I am attaching my "fastboot getvar all" output-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB 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: ZY322F8CL2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E320A71E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: "I AM HIDDING THIS FOR SECURITY PURPOSE, BUT IMEI IS VISIBLE HERE"
(bootloader) meid:
(bootloader) date: 12-11-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 17 9:41:58 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=82f94af-dirty
(bootloader) devcfg.git: git=82f94af-dirty
(bootloader) keymaster.git: git=82f94af-dirty
(bootloader) cmnlib.git: git=82f94af-dirty
(bootloader) cmnlib64.git: git=82f94af-dirty
(bootloader) prov.git: git=82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
Finished. Total time: 0.024s

hamhaingaurav said:
I was happy using Pixel Experience but Some bugs are worrying me so A week back I thought to go back to stock oreo and downloaded the Official Firmware lastest version for my G5s Plus, I flashed it using fastboot commands and now the only issue is that I do not have any IMEI in my phone, No network and No Signal.
Only thing I am getting is my Carrier Name Jio4G also it is able to detect my phone number. IMEI is correctly being shown using this command "$ fastboot getvar imei" but my device is unable to detect it. I have tried several time flashing with fastboot commands and Lenovo Moto Software Assistant, nothing worked for me.
I have also tried to resintall Pixel Experience ROM but no IMEI(Imei 0). I have also tried several other roms like RR and AOSP Ex also Havoc OS, nothing worked for me. I have also tried to flash TWRP backup of my Stock ROM but still IMEI 0. For your information I have also tried Pixel Experience rom with erasing modemst1 and modemst2 method, nothing worked.
Finally I thought to take it to the Moto Service Center, they flashed my devices with their software, but no success of retrieving the IMEI, even worse they gave me one more issue, which is now I am unable to unlock the bootloader with my unlock key. When I try to unlock it it says, "Code validation failure with status 7". When I try to generate new unlock data it says "Unlock data unavailable (bootloader) Failed.
I am really worried for my device because this is my only device and I am a student , I can not afford a new phone right now.
I will really appreciate your help for my entire lifetime, this issue is really making me sick.
I am attaching my "fastboot getvar all" output-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB 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: ZY322F8CL2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E320A71E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: "I AM HIDDING THIS FOR SECURITY PURPOSE, BUT IMEI IS VISIBLE HERE"
(bootloader) meid:
(bootloader) date: 12-11-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 17 9:41:58 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=82f94af-dirty
(bootloader) devcfg.git: git=82f94af-dirty
(bootloader) keymaster.git: git=82f94af-dirty
(bootloader) cmnlib.git: git=82f94af-dirty
(bootloader) cmnlib64.git: git=82f94af-dirty
(bootloader) prov.git: git=82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
Finished. Total time: 0.024s
Click to expand...
Click to collapse
You just mess your device with locked bootloader, there are not many things that can be done with locked bootloader. But still you can try this method.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
And try to unlock the bootloader, with unlock bootloader there could be some hope of recovery.

riyan65 said:
You just mess your device with locked bootloader, there are not many things that can be done with locked bootloader. But still you can try this method.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
And try to unlock the bootloader, with unlock bootloader there could be some hope of recovery.
Click to expand...
Click to collapse
Yes, I knwo there is an hope if i can unlock the bootloader, but the service center guy messed my device, I do not know how they flashed my device, they were flashing my device and said it is not turning on, i said okay return my device, i will flash it my self and after taking from them, i was trying to unlock the bootloader and I was getting the error "Code validation failure with status 7". I am also unable to get Unlock data.
What can i do now, is there any solution to it. Do i need to take my device to service center again ???

Try flashing april stock....then do the OTA update till August..

vivek1310yadav said:
Try flashing april stock....then do the OTA update till August..
Click to expand...
Click to collapse
Did it already and it have not solved my problem, There is one more issue on my phone, Whenever I flash my device with Retail and Retin verion it always shows my Harddware version as /x/x/x/x instead of PVT.
Go to settings>abount phone>hardware information then look at the version , in my case it is /x/x/x/x, because of which some of my sensors are not working.
My device is really messed up.

hamhaingaurav said:
Did it already and it have not solved my problem, There is one more issue on my phone, Whenever I flash my device with Retail and Retin verion it always shows my Harddware version as /x/x/x/x instead of PVT.
Go to settings>abount phone>hardware information then look at the version , in my case it is /x/x/x/x, because of which some of my sensors are not working.
My device is really messed up.
Click to expand...
Click to collapse
PM me..