Database Develop

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?

System UI has stopped, Phone locked

Hey All,
Device - Motorola One Power
Status - Completely in Stock condition
OS Version - 10(QPTS30.61-18-3)
After I changed a wallpaper on the phone, a popup "System UI has stopped" is perpetually occurring on top of my lock-screen which is making me unable to unlock or use the phone.
User is given with two options on the popup error, App info and Stop app, selecting any of these will give a blank screen and error will popup again repeating the same process.
Situation - USB Debugging is not enabled, USB connection settings set to charging as default.
Troubleshooting and results
1. Normal Mode - Fingerprint accepted, vibration feedback received, PIN mandatory, cannot login as display goes blank after every touch.
2. Safe Mode - Same issues as normal boot.
3. USB OTG-Mouse - Mouse pointer appears on top of the popup error, cannot dismiss, same issue as normal and safe boot.
4. Emergency call mode - Popup appears even on the emergency call.
5. Wipe Cache is unavailable in recovery as the I guess it's the new seamless A/B data structure.
Situation : Data is not backed up and Full Userdata wipe is not an option..
Wipe Data is not an option as I have the only copy of photos of recent family get-together and baby cousin's birthday which I could not back up due to lack of personal time.
Is there any way to get my data back ?
Fastboot?
ADB Zip Sideload?
Factory Mode?
Please help me out guys
Thanks

Anyone?
Please help guys

Jack_731 said:
Anyone?
Please help guys
Click to expand...
Click to collapse
Without USB debugging enabled,
I don't think there are any options.
You could try to flash firmware and skip the
erase userdata command
But with the bootloader lock likely
Flashing is blocked.
Sent from my ali using XDA Labs

sd_shadow said:
Without USB debugging enabled,
I don't think there are any options.
You could try to flash firmware and skip the
erase userdata command
But with the bootloader lock likely
Flashing is blocked.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Thank you for replying
USB Debugging is disabled, but when I boot to Recovery and go to 'load zip using ADB', ADB gets loaded in "Sideload" mode and the device is visible in Sideload mode in ADB command prompt.
Questions
1) Can I an sideload an official OTA Zip on a locked bootloader?
Here is a link from google support on that same sideload method for Google Pixel https://support.google.com/pixelphone/thread/17016500?hl=en&dark=1
Am referring to that cause my phone is running Android One, and they have migrated the data structure into the new A/B seamless partition.
Thank you again

Jack_731 said:
Thank you for replying
USB Debugging is disabled, but when I boot to Recovery and go to 'load zip using ADB', ADB gets loaded in "Sideload" mode and the device is visible in Sideload mode in ADB command prompt.
Questions
1) Can I an sideload an official OTA Zip on a locked bootloader?
Here is a link from google support on that same sideload method for Google Pixel https://support.google.com/pixelphone/thread/17016500?hl=en&dark=1
Am referring to that cause my phone is running Android One, and they have migrated the data structure into the new A/B seamless partition.
Thank you again
Click to expand...
Click to collapse
Possibly, but Motorola doesn't openly share the OTA updates like Google
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Possibly, but Motorola doesn't openly share the OTA updates like Google
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Here is a link to a tool made by members of xda https://forum.xda-developers.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039
and here is another link of firmwares for motorola one power https://mirrors.lolinet.com/firmware/moto/chef/official/RETIN/
Can you guide on how should I try this way?
Please help me out
Thanks

Anyone here with the expertise and knowledge to guide me through the process?
Any kind of link or guide or steps in which I can revive my on-device data?
Please help me out.
It will be very helpful to me ..

Anyone?
Any help will be appreciated
Thanks..

[
Jack_731 said:
Hi,
Will this method work on Locked BLs, and if USB Debug is off?
My Phone - Moto One Power
Click to expand...
Click to collapse
I don't think the ota update method is going to work.
But editing the erase userdata line
Then flashing with LMSA may
As discussed here
https://forum.xda-developers.com/g5-plus/how-to/how-to-flash-stock-loosing-data-t3871703

Jack_731 said:
Hey @sd_shadow
this is what I get on my Moto One Power (fastboot getvar all)
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-chef_retail-38523c9-200122
(bootloader) product: chef
(bootloader) board: chef
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ZF6223TFLL
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: FDF7898C
(bootloader) verity-state: enforcing (0)
No more info from bootloader.
BL = Locked
USB Debug = Locked
Unrooted
Is there anything I should do?
Thanks
Click to expand...
Click to collapse
I don't know over half the lines are missing
You should have more like this
Code:
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 11-20-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4006
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -39-6-2/d2226:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.461.11.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g496fe5a (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Oct 31 07:27:03 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-eca8056-191031
(bootloader) git:xbl: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:pmic: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-191031
(bootloader) git:tz: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:hyp: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:devcfg: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:keymaster: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:prov: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:storsec: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.250s

Hey, I just saw your post in my Pixel 3a thread (link if anyone is curious), sorry to hear you ended up in the same boat.
For what it's worth, my 3a suffered from a screen issue before. It's very unlikely (though not impossible) that something was corrupted being processed, but I wanted to add this thought.
Anyway, I hope you find a solution if nothing from my thread works. Although somewhat chaotic (and sometimes unconventional by freezing the UI before it crashes/restarts), it featured every bit me and others were able to think of.
In the end, only a factory reset helped and I lost all data in the process.
I would have been able to rescue everything, if I only had one more second between crashes or hadn't I rebooted in the meantime (no fingerprint allowed), sadly such small obstacles can be complete roadblocks.
So, sorry for not being of bigger help, but if you manage to find a solution which might be applicable to the 3a as well, I'd happily add it to my thread, too.
Good luck.

sysuicrash0511 said:
Hey, I just saw your post in my Pixel 3a thread (link if anyone is curious), sorry to hear you ended up in the same boat.
For what it's worth, my 3a suffered from a screen issue before. It's very unlikely (though not impossible) that something was corrupted being processed, but I wanted to add this thought.
Anyway, I hope you find a solution if nothing from my thread works. Although somewhat chaotic (and sometimes unconventional by freezing the UI before it crashes/restarts), it featured every bit me and others were able to think of.
In the end, only a factory reset helped and I lost all data in the process.
I would have been able to rescue everything, if I only had one more second between crashes or hadn't I rebooted in the meantime (no fingerprint allowed), sadly such small obstacles can be complete roadblocks.
So, sorry for not being of bigger help, but if you manage to find a solution which might be applicable to the 3a as well, I'd happily add it to my thread, too.
Good luck.
Click to expand...
Click to collapse
Hey there,
I think we understand each others problems very well,
Don't be sorry, your post has actually helped me understand that am not alone with the current issue.
This is a serious issue in Android Devices (System UI has stopped), and I guess more than 80% of the consumers don't know anything about USB Debugging or would keep that enabled.
First of all, an error popup should not be front and center on any UI, the pop-up should be dismiss-able / can be minimized away from the general display area of any device.
Just like when in older Android UI, even an incoming-call used to take the entire screen, but nowadays, they are part of notifications, if the user is focusing on another app.
The fact that this 'System UI' error occurred on the latest Android 10 update (Feb 2020), makes it even worse., that Android hasn't matured yet to be stable.
In hindsight, yes if we had not restarted the phone the moment we face that "System UI keeps stopping" error, the in-device data could have been saved 100%.
Cause the phone was functional even after the error pops up, and there are certain ways we can circumvent it (except restarting).
At least Google is publicly providing OTAs for Pixels so that users can try sideloading.
Motorola doesn't provide anything official, even though it's an "Android One" device.
I guess I will have to do factory reset after all , If nothing turns up positive.
Will keep you posted.
Thanks
Cheers

sd_shadow said:
I don't know over half the lines are missing
You should have more like this
Code:
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 11-20-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4006
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -39-6-2/d2226:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.461.11.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g496fe5a (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Oct 31 07:27:03 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-eca8056-191031
(bootloader) git:xbl: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:pmic: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-191031
(bootloader) git:tz: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:hyp: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:devcfg: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:keymaster: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:prov: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:storsec: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.250s
Click to expand...
Click to collapse
This was the error message displayed after the command.
Code:
getvar:all FAILED (status read failed (Too many links))
Is there any hardware issue with the phone?

Hey @sd_shadow,
Can you check these recovery logs to get a clearer picture of this issue?
Especially these lines
Code:
ro.adb.secure=1
ro.mot.security.enable=1
ro.opa.eligible_device=true
ro.secure=1
ro.debuggable=0
ro.oem_unlock_supported=1
ro.boot.flash.locked=1
ro.boot.write_protect=0
ro.boot.secure_hardware=1
1) Does it means it is flash protected?
2) If 'fastboot getvar all' command result is not completely getting loaded, does that mean "fastboot flash" command is out of bounds?
Thanks..

Jack_731 said:
Hey @sd_shadow,
Can you check these recovery logs to get a clearer picture of this issue?
Especially these lines
Code:
ro.adb.secure=1
ro.mot.security.enable=1
ro.opa.eligible_device=true
ro.secure=1
ro.debuggable=0
ro.oem_unlock_supported=1
ro.boot.flash.locked=1
ro.boot.write_protect=0
ro.boot.secure_hardware=1
1) Does it means it is flash protected?
2) If 'fastboot getvar all' command result is not completely getting loaded, does that mean "fastboot flash" command is out of bounds?
Thanks..
Click to expand...
Click to collapse
@sd_shadow
What do you think?
Am a bit concerned , as If I may get stuck while flashing and this phone will end up useless.
If 'fastboot getvar all' command result is not completely getting loaded, does that mean "fastboot flash" command is out of bounds?
Thanks

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..

Moto G2 XT1072 can't boot

Hi all,
I had a XT1072 with Android 6 and wanted to go back to 5 due to problems with GPS.
I unlocked the boot loader, flashed stock ROM with Android 6 and all was fine.
I next tried to flash stock ROM with Android 5 and was stuck in fast boot with errors like "invalid system image signature" or similar.
Next I messed around with TWRP, stock again, lock, unlock... a mess.
Now it's stuck in fastboot with status "LOCKED, status code 2" (0 is LOCKED, 3 UNLOCKED, 2 what is it?)
I tried flashing stock ROM both 5 and 6 in different versions:
RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETESALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
Motorola_Moto_G2_XT1072_MPB24.65-34_CID12_6.0
But all fail with "failed validation";
Unlock fails, but I cannot boot in Android to change mentioned option:
Code:
mfastboot-v2> .\mfastboot oem unlock XSVDURWNGOWYDFMGU5ZT
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.057s
RSD Lite to flash stock ROM doesn't see my device.
Rescue and Smart Assistant cannot proceed due to "missing version-baseband:" (see empty var listed below).
Code:
mfastboot-v2> .\mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4821
(bootloader) product: thea
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2272TX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: C96B590915000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 2
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from mot-charger boot mode
(bootloader) imei: 353310061467870
(bootloader) meid:
(bootloader) date: 04-28-2015
(bootloader) sku: XT1072
(bootloader) battid: SNN5956A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Sep 16 3: 2:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.thea_reteu.
(bootloader) ro.build.version.full[1]: reteuall.en.EU
(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-g495dfd8 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Sat Sep 10 01:48:29 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V48.21-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.21-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.21-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.21-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.21-0-gd8d8d9e
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1C2272TX
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.105s
Do you have any suggestions to restore it?
Let me know if I can give you more information.
Thanks

enricocava said:
Hi all,
I had a XT1072 with Android 6 and wanted to go back to 5 due to problems with GPS.
I unlocked the boot loader, flashed stock ROM with Android 6 and all was fine.
I next tried to flash stock ROM with Android 5 and was stuck in fast boot with errors like "invalid system image signature" or similar.
Next I messed around with TWRP, stock again, lock, unlock... a mess.
Now it's stuck in fastboot with status "LOCKED, status code 2" (0 is LOCKED, 3 UNLOCKED, 2 what is it?)
Click to expand...
Click to collapse
Sometimes the bootloader will relock, when using a custom recovery is used.
I'm not sure why usually when trying to install a rom.
It's very common, but it happens on many Moto devices.
enricocava said:
I tried flashing stock ROM both 5 and 6 in different versions:
RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETESALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
Motorola_Moto_G2_XT1072_MPB24.65-34_CID12_6.0
Click to expand...
Click to collapse
That will have made it worse.
enricocava said:
But all fail with "failed validation";
Unlocking fails with "Please allow OEM unlock from developer options", but Android is not booting so I cannot change it.
RSD Lite to flash stock ROM doesn't see my device.
Click to expand...
Click to collapse
RSD Lite doesn't work with Windows 9/10/11
Use XP/7
enricocava said:
Rescue and Smart Assistant cannot proceed due to "missing base version" (string is not correct, I'll chek it later).
Do you have any suggestions to restore it?
Let me know if I can give you more information.
Thanks
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

Thank you for your quick reply.
sd_shadow said:
RSD Lite doesn't work with Windows 9/10/11
Use XP/7
Click to expand...
Click to collapse
Colud it work on a Win7 on a Virtual machine or does it need direct access to USB ports? At the moment I have not an old Windows available.
sd_shadow said:
What does getvar all say?
Click to expand...
Click to collapse
I updated the original post.
sd_shadow said:
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
I missed this post, I'll take a look.

enricocava said:
Hi all,
I had a XT1072 with Android 6 and wanted to go back to 5 due to problems with GPS.
I unlocked the boot loader, flashed stock ROM with Android 6 and all was fine.
I next tried to flash stock ROM with Android 5 and was stuck in fast boot with errors like "invalid system image signature" or similar.
Next I messed around with TWRP, stock again, lock, unlock... a mess.
Now it's stuck in fastboot with status "LOCKED, status code 2" (0 is LOCKED, 3 UNLOCKED, 2 what is it?)
I tried flashing stock ROM both 5 and 6 in different versions:
RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETESALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
Motorola_Moto_G2_XT1072_MPB24.65-34_CID12_6.0
But all fail with "failed validation";
Unlock fails, but I cannot boot in Android to change mentioned option:
Code:
mfastboot-v2> .\mfastboot oem unlock XSVDURWNGOWYDFMGU5ZT
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.057s
RSD Lite to flash stock ROM doesn't see my device.
Rescue and Smart Assistant cannot proceed due to "missing version-baseband:" (see empty var listed below).
Code:
mfastboot-v2> .\mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4821
(bootloader) product: thea
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2272TX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: C96B590915000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 2
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from mot-charger boot mode
(bootloader) imei: 353310061467870
(bootloader) meid:
(bootloader) date: 04-28-2015
(bootloader) sku: XT1072
(bootloader) battid: SNN5956A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Sep 16 3: 2:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.thea_reteu.
(bootloader) ro.build.version.full[1]: reteuall.en.EU
(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-g495dfd8 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Sat Sep 10 01:48:29 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V48.21-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.21-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.21-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.21-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.21-0-gd8d8d9e
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1C2272TX
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.105s
Do you have any suggestions to restore it?
Let me know if I can give you more information.
Thanks
Click to expand...
Click to collapse
Code:
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
This should be the correct firmware
https://mirrors-obs-2.lolinet.com/firmware/motorola/2015/thea/official/RETEU/
XT1072_THEA_RETEU_6.0_MPBS24.65-34-5_cid7_subsidy-DEFAULT_CFC.xml.zip
Try flashing
Code:
fastboot flash partition gpt.bin
fastboot reboot bootloader
Then flash the firmware using the flash_file.xml as reference.

sd_shadow said:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
This should be the correct firmware
https://mirrors-obs-2.lolinet.com/firmware/motorola/2015/thea/official/RETEU/
XT1072_THEA_RETEU_6.0_MPBS24.65-34-5_cid7_subsidy-DEFAULT_CFC.xml.zip
Try flashing
Code:
fastboot flash partition gpt.bin
fastboot reboot bootloader
Then flash the firmware using the flash_file.xml as reference.
Click to expand...
Click to collapse
Thank you, it worked! So the problem was the wrong fw version and messing up gpt with random commands, right?
For a downgrade I can follow this one, right? https://forum.xda-developers.com/t/guide-flashing-motorola-firmware.4042039/post-84863341

enricocava said:
Thank you, it worked! So the problem was the wrong fw version and messing up gpt with random commands, right?
Click to expand...
Click to collapse
I believe so
enricocava said:
For a downgrade I can follow this one, right? https://forum.xda-developers.com/t/guide-flashing-motorola-firmware.4042039/post-84863341
Click to expand...
Click to collapse
Do not downgrade unless the bootloader says unlocked again.
If the bootloader is reported as unlocked again,
sure you should be able to downgrade the firmware.

[HELP] Unreliable Cellular and WiFi connections after restoring with LSMA

Hello everyone,
I am in a bit of a dire situation here with my Moto X4 (Model No. XT1900-1), and I cannot tell you how grateful I would be if someone might be able to assist me in fixing it. To begin, I flashed LineageOS onto my Moto X4 a couple of years back, and have had trouble updating Lineage every time there was a major update. While my phone would be able to successfully boot into the operating system, it would be unable to connect to the cellular network or WiFi, and I would have to perform 2 fresh installations in order to get the phone working properly. I tolerated it, but for this reason (and that installing Open GApps and Magisk would also require a manual update) I would rarely update the phone.
Against my better judgement I attempted to update the phone to Lineage 18.1 today, and experienced the same issue once again. Wanting to get to the root of the issue, I requested assistance in Lineage's support chat, and someone pointed out that I probably missed the critical step of copying the configuration of slot A into slot B as detailed in their fresh installation instructions, and also recommended attempting to update the firmware. I attempted the fresh installations as I normally would to fix this (the instructions are detailed here), and flashed the copy-partitions-20210323_1922.zip package linked in said instructions, sadly to no avail, even after multiple installation attempts. I then decided it might be best to attempt to flash a stock ROM and update the firmware. Using the this stock ROM and the instructions and commands detailed in this thread, I successfully flashed the software, but when it booted up I saw, to my horror, that the phone was still experiencing the same issue. My most recent attempt to fix this was to flash a stock 9.0 ROM from this thread because Lineage's instructions do specify that the firmware does need to be updated to Android 9, and I would still like to use Lineage after I overcome this issue, but sadly the phone is still experiencing the same issue in this case as well.
(EDIT) I did some more digging and stumbled upon this thread which pointed me to the LSMA. I restored the phone using the LSMA, and had a degree of success. The phone does now recognize the cellular and WiFi hardware, and can pick up their respective networks, but both the cellular and WiFi connections constantly flicker on and off. I did also try using the copy partitions package detailed in that particular thread, but sadly this new issue persists after flashing it. I have pasted the output of "fastboot getvar all" after restoring using the LSMA below:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-eca8056-191217
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2258KN6T
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: A9FB75A4
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356484083595567
(bootloader) meid:
(bootloader) date: 12-14-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4270
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -39-6-4/4011a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.481.16.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g81a5f80 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Tue Dec 17 16:30:24 CST 2019
(bootloader) git:abl: MBM-3.0-payton_retail-eca8056-191217
(bootloader) git:xbl: MBM-3.0-payton_retail-dec7b7c-191217
(bootloader) git:pmic: MBM-3.0-payton_retail-dec7b7c-191217
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-191217
(bootloader) git:tz: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:hyp: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:devcfg: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:cmnlib: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:keymaster: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:prov: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:storsec: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0

I've been in a similar situation with this phone when I attempted to flash the stock rom from various sites including the one you referenced, I found that I ran into problems because certain files were corrupted, which would cause all kinds of issues with my flash, so as a last resort of sorts, I downloaded the motorola rescue and smart assistant tool, and hook the phone up to it, I was then able to get the most up to date stock ROM for my phone downloaded to my PC. Refer to the link below for details
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
Of course any attempts to flash the Stock ROM with the tool did not succeed, so I was forced to use another tool (flash-all.bat script) from this forum, which ultimately did result in a successful flash. Refer to the link below
[TUTORIAL][Google FI][STOCK][PIE 9.0]Go From Rooted Oreo to Pie on Android One 1900-1
Rooted Oreo -> Stock Pie When I attempted to go from Oreo by flashing the Pie zip from this thread I got an error saying the update wasn't valid. This guide is how to get around that and upgrade your phone to Pie! Warning THIS IS ONLY INTENDED...
forum.xda-developers.com
Before running flash-all.bat script file, i had to edit it and remove an extra line that my stock rom didn't have, the line I had to remove is listed below
fastboot flash system system.img_sparsechunk.7
Once I removed that line, saved the script and then ran it per the instructions, everything worked fine with no issues.