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

[SOLVED] Now no OEM Unlock for 7 days???

Two days ago I got my hands on a "mint" XT1925-6, and I'm still waiting for OEM Unlock to be un-grayed (available) in Dev Options.
I've nearly lost count of the number of Moto phones I've owned, rooted, bootloader-unlocked in the past 5-6 years. I've never had to wait more than one quick little WiFi connection before tapping OEM unlock.
I know this phone is unlockable because I've already got its unlock code, emailed to me straight from Motorola. So that question has been asked and answered. But I'm still waiting to be able to tap and enable OEM Unlock.
I found the verbage below in the Lenovo G6/Plus/Play support forum -- https://forums.lenovo.com/t5/Moto-G...lay-software-image/m-p/5077477?page=1#5317655
This question was asked concerning a G6 Play (XT1922), but I've also found this same answer for the XT1925 in other pages that I've since lost track of . . . to wit, how does one get the phone unlocked if the OEM bootloader unlock switch is greyed out.
Answer by 'Agent Rich' in the 2nd post (MY emphasis/caps/etc): "I've seen it before, it looks like the phone needs to have an active data connection for a WEEK for the OEM option [to] become available."
And then in the 4th post (the last one): "The phone needs to have an active data [connection] to help mitigate the risk of device being stolen and re-flashed."
". . . . . . to help mitigate the risk of device being stolen and re-flashed" . . . . . What kind of B.S. answer is that?
Does anybody have any kind of meaningful response to this horse****?
In the meantime I've disabled all the google junk and other useless stuff while keeping the phone on an "active data connection" (WiFi), in the (probably vain) hope that it won't be anywhere near a week before OEM gets enabled . . . . . . . . . . . . . .
Firmware version is PPS29.118-15-11-16; 'getvar all' shows CID 0x0032. Just to be sure, and despite the 'advice' from 'Agent Rich', is there anything else I can look at that might show the phone I have is not a genuine, official, carrier-unlocked/bootloader-unlockable XT1925-6?

NINE days and still waiting for OEM Unlocking to enable.
The phone IS unlockable according to Motorola. I've got the unlock code. XT1925-6, RetUS, CID 0x0032, everything says it's unlockable. Methinks something is fishy with this phone but I have no idea what. No clue at all.
--- fastboot getvar all (from "day 1" after an FDR) ---
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: [**********]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: AC94058600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [***************]
(bootloader) meid:
(bootloader) date: 05-03-2018
(bootloader) sku: XT1925-6
(bootloader) carrier_sku: XT1925-6
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jul 25 14:56: 2 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:9/PPS29.118-15-11
(bootloader) ro.build.fingerprint[1]: -16/3afd9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.4.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M450_23.31.10.89R ALI_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g19723945513
(bootloader) kernel.version[1]: 7-04290-gfb8faa3398e9 ([email protected]
(bootloader) kernel.version[2]: 71) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[3]: ase) (GCC) ) #1 SMP PREEMPT Thu Apr 23 1
(bootloader) kernel.version[4]: 1:51:22 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ali_retail-5e077487fa-200423
(bootloader) rpm.git: MBM-2.1-ali_retail-218e5afd-200423
(bootloader) tz.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) devcfg.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) keymaster.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) prov.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) aboot.git: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown

I might try reflashing the firmware I downloaded through the Rescue program. Or maybe run an actual rescue through that software.

Moondroid said:
I might try reflashing the firmware I downloaded through the Rescue program. Or maybe run an actual rescue through that software.
Click to expand...
Click to collapse
The invalid slots are concerning.
I would reflash the firmware, then reconnect to the internet.

sd_shadow said:
The invalid slots are concerning.
I would reflash the firmware, then reconnect to the internet.
Click to expand...
Click to collapse
I see what you mean. I reflashed last night but didn't think to run getvar and compare. I just did that, again after reflashing FW downloaded through Lenovo Rescue and Smart Assistant, and those slots still show invalid . . .
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: [**********]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: AC94058600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [***************]
(bootloader) meid:
(bootloader) date: 05-03-2018
(bootloader) sku: XT1925-6
(bootloader) carrier_sku: XT1925-6
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 4 17:30: 0 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:9/PPS29.118-15-11
(bootloader) ro.build.fingerprint[1]: -16/3afd9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.4.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M450_23.31.10.89R ALI_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g19723945513
(bootloader) kernel.version[1]: 7-04290-gfb8faa3398e9 ([email protected]
(bootloader) kernel.version[2]: 71) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[3]: ase) (GCC) ) #1 SMP PREEMPT Thu Apr 23 1
(bootloader) kernel.version[4]: 1:51:22 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ali_retail-5e077487fa-200423
(bootloader) rpm.git: MBM-2.1-ali_retail-218e5afd-200423
(bootloader) tz.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) devcfg.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) keymaster.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) prov.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) aboot.git: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
Another thing: On this phone OEM Unlocking shows completely grayed out. But on another G6 (XT1925-6) that I picked up cheap in an eBay auction, the OEM Unlocking verbage is not grayed out. Just the button.
Edit/Add: Identical phones, exact same firmware. The second phone also shows those slots as Invalid.

getvar all from the second phone (the one that shows only the button disabled). I'm still looking for any differences . . .
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: ********DJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: FA6FB84D00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: *************19
(bootloader) meid:
(bootloader) date: 10-28-2018
(bootloader) sku: XT1925-6
(bootloader) carrier_sku: XT1925-6
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Sep 13 12: 0:16 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:9/PPS29.118-15-11
(bootloader) ro.build.fingerprint[1]: -16/3afd9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.4.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M450_23.31.10.89R ALI_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g19723945513
(bootloader) kernel.version[1]: 7-04290-gfb8faa3398e9 ([email protected]
(bootloader) kernel.version[2]: 71) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[3]: ase) (GCC) ) #1 SMP PREEMPT Thu Apr 23 1
(bootloader) kernel.version[4]: 1:51:22 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ali_retail-5e077487fa-200423
(bootloader) rpm.git: MBM-2.1-ali_retail-218e5afd-200423
(bootloader) tz.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) devcfg.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) keymaster.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) prov.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) aboot.git: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
PS: This getvar all is before I corrected the time to current.

Clarification on the images: The first image is from the second phone. The second image is from phone #1, the one I've had for 10 days and reflashed yesterday. I just double-checked on the phones themselves.

Phone #1 (100% gray):
emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5
Phone #2 (button only gray):
emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01

After taking a relaxing 4-day vacation I remembered a possible solution, which worked on the #2 phone (haven't tried it on #1):
-- FDR
-- Setup as new with Wireless enabled. I did this with Wifi turned on but without an actual working Internet connection. Apparently it just wants WiFi enabled.
-- Setting the date may or may not matter. I just went through the setup using "Skip" and "Next" liberally.
-- Enabled Developer Options and Presto, OEM Unlock was enabled. My previously requested Unlock Code then worked to unlock the bootloader.

I'm experiencing this exact same issue. The phone is a Motorola Edge 30 Neo XT2245-1. I just opened the product package, turned it on, used the Motorola website to request the bootloader unlock code (which I received via email, no problem), and then I found out that the "OEM unlock" checkbox in Android Settings > Developer options is shown but it's grayed out. It is completely grayed out, meaning both the text and the checkbox are grayed out. What I did afterwards was search XDA and found a couple of threads, most of them suggesting to do a factory reset (via the Android settings), which I did, but that didn't help.
I'm hoping now that it's simply a timer, and that I have to wait a few days before the checkbox starts working. The CID value is 50 (or hex 0x32), and I already received the bootloader unlock code, so I'm pretty sure it should be possible to liberate this phone without having to resort to (or waiting for new) privilege escalation exploits.
Will post in a few days whether it (the "OEM unlock" setting) becomes toggle-able. Feel free to nudge me if I forget to do so.

heisenbug#3141 said:
I'm experiencing this exact same issue. The phone is a Motorola Edge 30 Neo XT2245-1. . . .
Click to expand...
Click to collapse
2-3 weeks ago I went through this again with a Motorola One 5G Ace. I waited 8 days with nothing changing, finally tried a factory reset and voila. Unlock enabled.
There no longer seems to be any predictable method to this madness. Good luck, you'll get there eventually.

Moondroid said:
2-3 weeks ago I went through this again with a Motorola One 5G Ace. I waited 8 days with nothing changing, finally tried a factory reset and voila. Unlock enabled.
There no longer seems to be any predictable method to this madness. Good luck, you'll get there eventually.
Click to expand...
Click to collapse
That's wicked. Based on that, I guess it might be that, whether or not the "OEM unlock" will be toggle-able is decided at the time of the reset, or soon after the first successful internet connection has been established, and that this result is saved. In other words, the option perhaps won't become toggle-able afterwards. If that's true, it might even work to just simply try a factory reset every single day until it's toggle-able, because one of those days the (server-side) timer has elapsed. Or, if that theory proves to be false, then perhaps you need to wait at least N days and do a factory reset after having waited long enough. Time will tell. Anyhow, thanks for shining light on this! Really hoping for the best here.

It's unlocked now. The "OEM unlock" option became toggle-able today. It seems waiting is all you have to do after requesting the bootloader unlock code via the Motorola website.
For future reference, and for anyone stumbling upon this here:
I did the last factory reset about 4 days ago and from that moment on I just waited and checked every day whether the "OEM unlock" option was toggle-able or not. And when it was, I toggled it, heeded the well-known warnings, and used 'fastboot' to unlock it. I had the device a few days longer, so in total I waited about a week before being able to unlock it.
Also, in case anyone wonders, whether or not a SIM card is inserted should not matter if one's phone is an international (global) model, as those aren't carrier locked. My phone is an international model and the SIM card was not inserted while waiting for the "OEM unlock".
Whispering digits of pi to the phone also apparently doesn't matter.

Another corrupted X4, am I screwed?

My Wife has an X4, xt1900-1 from Google Fi, that she no longer uses as a phone but uses it on wifi only to run a special piece of software. It got the "device is corrupted" error and will not boot to anything other than FastBoot. Adding results of "Fastboot getvar all" at the end of post. Running "Fastboot oem get_unlock_data" returns:
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
Finished. Total time: 0.003s
Running LMSA initially wouldn't detect the device, then it did detect and begins the re-flash process but fails at flashing around 69 percent.(nice) No other information is given other than flashing failed.
Attempting to flash the firmware that the LMSA downloaded manually via fastboot and it flashes the first couple bits but fails at the bootloader.
Attempting to fastboot boot into twrp returns:
Sending 'boot.img' (38672 KB) OKAY [ 1.412s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
I found the blankflash image for this version of payton, when attempting to run it, the terminal just displays:
< waiting for device >
And nothing ever happens.
I've tried it on Windows and Linux with a handful of different cables and the results are the same. Am I SOL and it's time to replace the device?
Thanks,
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_fi-eca8056931-200924
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY224H58SP
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 356484080483981
(bootloader) meid:
(bootloader) date: 10-15-2017
(bootloader) sku: XT1900-1
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3899
(bootloader) iccid: 8901260971113779407
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton_fi/payton_sprout:9
(bootloader) ro.build.fingerprint[1]: /PPWS29.69-39-6-13/badd5:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.491.55.payton_fi.
(bootloader) ro.build.version.full[1]: google_fi.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7048.65.01.101R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g097f40be62ed
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.x
(bootloader) kernel.version[2]: 20150123 (prerelease) (GCC) ) #1 SMP PR
(bootloader) kernel.version[3]: EEMPT Thu Sep 24 04:43:29 CDT 2020
(bootloader) git:abl: MBM-3.0-payton_fi-eca8056931-200924
(bootloader) git:xbl: MBM-3.0-payton_fi-b24b3b6a2-200924
(bootloader) gitmic: MBM-3.0-payton_fi-b24b3b6a2-200924
(bootloader) git:rpm: MBM-3.0-payton_fi-f97e5eb-200924
(bootloader) git:tz: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:hyp: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:devcfg: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:cmnlib: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:cmnlib64: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:keymaster: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) gitrov: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:storsec: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) frp-state: protected (77)
(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: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.047s

Heyyo, blankflash only works if you reboot the device into EDL mode. I can't remember if powering it off, holding down both volume keys and plugging it into a PC will actually boot it into EDL mode or not for Motorola devices though...
You can also try the TinyFastbootScript and see if that works?
Download the ROM from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Download TinyFastbootScript from here which also has the instructions:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work and you can't force reboot to EDL? You can search on Amazon / AliExpress or others for an "Android EDL cable" which can also work to force EDL mode.

ThE_MarD said:
Heyyo, blankflash only works if you reboot the device into EDL mode. I can't remember if powering it off, holding down both volume keys and plugging it into a PC will actually boot it into EDL mode or not for Motorola devices though...
You can also try the TinyFastbootScript and see if that works?
Download the ROM from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Download TinyFastbootScript from here which also has the instructions:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work and you can't force reboot to EDL? You can search on Amazon / AliExpress or others for an "Android EDL cable" which can also work to force EDL mode.
Click to expand...
Click to collapse
Awesome thanks for the reply. Yeah I tried a couple different key combinations that I have seen people reference but nothing seemed to work, however I didn't try holding down both volume keys while plugging it in. I'll try that, and also try the tinyfastboot script too and see what happens. Thanks!

Well I think it's toast. The Tinyfastboot script was giving a lot of the same errors when I was running things manually. I could not get the device to boot into EDL through key combinations either. I think the biggest issue is that the bootloader is locked, and cannot be unlocked. I might try to find a cable and give that a shot but I am thinking now it's a waste of time.
Thanks for the help anyway.

Im facing same issue here as well. so EDL method doesnt work?