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?

The device is Corrupted, Cannot Be trusted, Will not boot

Hey Guys!
I have a problem with a motorola xt1900 (x4) is stuck in the unlock bootloader notify, I tried many forms by fastboot but did not succeed.
First of all, I installed the lineage 16.0, it was great, but then I wanted to do root, I downloaded the magisk and it gave bootloop after flash, so I tried to put the 8.0 stockrom and I've been stuck ever since, can't unlock again, i still have the code from motorola.
"the device is Corrupted, Can not Be trusted, Will not boot"
I tried to flash the TWRP, but I could not.

I ended up in a semi-hard bricked phone where recovery wouldn't boot and my phone told me both slot A and B was missing. My way of fixing my phone when all I could do was seeing a bootloader with an error message (as you seem to have) was to flash it with the flash all software found here https://www.androidfilehost.com/?fid=890278863836292604 Run flash_all.bat as an administrator in Windows or ./flash_all in Linux as root ( sudo ./flash_all ). Remember, you don't need to enter recovery, the boot error message should be good enough.
The thing you need to accept is all your data will be wiped. If you wanted to save anything, it was already too late. Once you run that flash, reboot your phone into your bootloader and run the command
fastboot boot '/your_path_here/twrp-3.2.3-1-payton.img'
This will force your phone to boot using TWRP from your computer and from there you should be able to upload a ROM and install. -- Remember if using Linux to add the sudo command before that.

Hey man! I'm on Windows.
By the way, don't care about data. just want my phone working.:crying:
still same error message, (bootloader) "flash permission denied"
"remote failure"
I try again the unlock code, says ok finished, but didn't work.

danielwah said:
Hey man! I'm on Windows.
By the way, don't care about data. just want my phone working.:crying:
still same error message, (bootloader) "flash permission denied"
"remote failure"
I try again the unlock code, says ok finished, but didn't work.
Click to expand...
Click to collapse
The same happened to me using the regular adb flashboot commands...I have my X4 totaly locked... Any new?

tuliusy2k said:
The same happened to me using the regular adb flashboot commands...I have my X4 totaly locked... Any new?
Click to expand...
Click to collapse
My errors:
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.

This is my fastboot getvar all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180328
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(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 (6)
(bootloader) serialno: 0039062204
(bootloader) cid: 0x0032
(bootloader) channelid: 0x01
(bootloader) uid: 9EB17BE5
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***********************
(bootloader) meid:
(bootloader) date: 10-10-2017
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3942
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 7.57-40-25/32:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.32.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g18bb7f8 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Oct 18 11:48:40 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-641a15b-180328
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180328
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-180328
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180328
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: amxbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(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: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.219s
I have the same problem "The device is Corrupted, Cannot Be trusted, Will not boot"

Use the fastboot getvar all command, find the sku version of it and download the rom with the same number that appears in the fastboot and install normally, it worked with me now at dawn. The only rom that works when the unit is in this state and the one in it

i am the same problem...
After relock bootloader it wont boot, dont enter recovery, only enter in fastboot, but flashing is locked!
Any stock system not flash....
---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------
i am the same problem...
After relock bootloader it wont boot, dont enter recovery, only enter in fastboot, but flashing is locked!
Any stock system not flash....

I found the solution! (for me)
1 - Enter in fastboot (volume down + power), and boot up the "boot.img" of the last system used in my phone. (Lineage 16.0)
https://drive.google.com/file/d/1OaWtQo1jfX5glVj1pnjDnu8NDkgDOHDd/view?usp=sharing
"fastboot boot boot.img"
And the phone enter a System!
2 - Activate ADB, and allow superuser comands in ADB - "Developer Settings"
And run the command for show "Enable OEM Unlocking"
adb shell setprop ro.oem_unlock_supported 1
Check toggle "Enable OEM Unlocking"
3 - Power off and put in fastboot again
4 - re-run "fastboot oem unlock <<your code>>"
5 - Ready! Your phone unlocked flashing again!

I woke up in the morning and found my phone had crashed. I turned it off and it woudlnt come back on. same error message...
your devise is corrupt. it cant be trusted and will not boot.
Has anyone found a way to recover it without losign nay data. i really cant afford to lose my pics and videos.
Any help would be appreciated.
PS i rooted this phone a long time ago and not fluent in the root process

juniofdm said:
I found the solution! (for me)
1 - Enter in fastboot (volume down + power), and boot up the "boot.img" of the last system used in my phone. (Lineage 16.0)
https://drive.google.com/file/d/1OaWtQo1jfX5glVj1pnjDnu8NDkgDOHDd/view?usp=sharing
"fastboot boot boot.img"
And the phone enter a System!
Click to expand...
Click to collapse
I tried this on my device (never rooted, never unlocked bootloader), and at first it gave me the error:
Sending 'boot.img' (22249 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
Then subsequent attempts just get stuck on the 'Sending' line. This was using the stock image from this post: https://forum.xda-developers.com/t/rom-stock-pie-9-0-moto-x4-retail-android-pie.3876156/
I've run out of options as the Rescue and Smart Assistant isn't working either. Any help appreciated.

it worked for me thanks

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

Is it possible?

I'm very new to this, but I have a Motorola E5 Cruise (Cricket) that's network locked, ...sent my info to several unlocking sites and even tried a few, but so far they haven't been able to help, or tried to help but refunded me.
Other than doing a 6 month contract with Cricket to get them to network unlock, what are my options? I'd like to use this phone, but with straight talk rather than Cricket.
Is firmware for the Play & Cruise compatible? Please advise. Thanks a million!!!

RLBuddi said:
I'm very new to this, but I have a Motorola E5 Cruise (Cricket) that's network locked, ...sent my info to several unlocking sites and even tried a few, but so far they haven't been able to help, or tried to help but refunded me.
Other than doing a 6 month contract with Cricket to get them to network unlock, what are my options? I'd like to use this phone, but with straight talk rather than Cricket.
Is firmware for the Play & Cruise compatible? Please advise. Thanks a million!!!
Click to expand...
Click to collapse
I don't know, but you want to be careful about flash firmware for different model.
I would try to unlock the bootloader first
https://forum.xda-developers.com/showpost.php?p=80035798&postcount=115
Then
Check the getvar info
run
Code:
fastboot getvar all
Product = codename
securestate = bootloader locked or unlocked
carrier_sku = Model #
ro.carrier = Software Channel
Please post it here after you remove the IMEI line
Then you can compare software channels with the same model number
https://mirrors.lolinet.com/firmware/moto
If you find a retail software channel like RetUS
That is for the same model you might be able to
Either just flash the modem files
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Or the complete firmware
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
But this just a guess
Sent from my ali using XDA Labs
---------- Post added at 01:12 AM ---------- Previous post was at 01:09 AM ----------
If the bootloader cannot be unlocked
You might be able to just flash the modem files
But it would likely be less risky if bootloader is unlocked.
Sent from my ali using XDA Labs

C:\Adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 9
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY322XV4G5
(bootloader) cid: 0x0001
(bootloader) channelid: 0x89
(bootloader) uid: DBA1266E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 07-27-2018
(bootloader) sku: XT1921-2
(bootloader) carrier_sku: XT1921-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jan 4 6:42:31 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/james_a/james:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-157-28/2:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.341.2.james_a.a.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8920_34.26.11.76R JAMES_NA_ATT_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-ga94d3a1 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Feb 4 05:47:07 CST
(bootloader) kernel.version[3]: 2020
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=cc1477e
(bootloader) devcfg.git: git=cc1477e
(bootloader) keymaster.git: git=cc1477e
(bootloader) cmnlib.git: git=cc1477e
(bootloader) cmnlib64.git: git=cc1477e
(bootloader) prov.git: git=cc1477e
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: cricket
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.363s

RLBuddi said:
C:\Adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 9
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY322XV4G5
(bootloader) cid: 0x0001
(bootloader) channelid: 0x89
(bootloader) uid: DBA1266E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 07-27-2018
(bootloader) sku: XT1921-2
(bootloader) carrier_sku: XT1921-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jan 4 6:42:31 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/james_a/james:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-157-28/2:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.341.2.james_a.a.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8920_34.26.11.76R JAMES_NA_ATT_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-ga94d3a1 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Feb 4 05:47:07 CST
(bootloader) kernel.version[3]: 2020
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=cc1477e
(bootloader) devcfg.git: git=cc1477e
(bootloader) keymaster.git: git=cc1477e
(bootloader) cmnlib.git: git=cc1477e
(bootloader) cmnlib64.git: git=cc1477e
(bootloader) prov.git: git=cc1477e
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: cricket
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.363s
Click to expand...
Click to collapse
Does this device still boot normally?
Sent from my ali using XDA Labs

sd_shadow said:
Does this device still boot normally?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Yes, it boots no problem. I tried flashing the retail firmware for the same phone. It realized there was a size difference or something. Got up to step 11 ......11-20 failed
I'd tried to flash the modem files using the posted instructions, flashing was success. Still oem locked

RLBuddi said:
Yes, it boots no problem. I tried flashing the retail firmware for the same phone. It realized there was a size difference or something. Got up to step 11 ......11-20 failed
I'd tried to flash the modem files using the posted instructions, flashing was success. Still oem locked
Click to expand...
Click to collapse
Oem locked is different from carrier locked.
It's still carrier locked?
Sent from my ali using XDA Labs
---------- Post added at 01:47 AM ---------- Previous post was at 01:45 AM ----------
If it's still carrier locked the thing to try is
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my ali using XDA Labs

sd_shadow said:
Oem locked is different from carrier locked.
It's still carrier locked?
Sent from my ali using XDA Labs
---------- Post added at 01:47 AM ---------- Previous post was at 01:45 AM ----------
If it's still carrier locked the thing to try is
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Sorry bout the delay, ....Yes, it's still carrier locked. Thanks for your help!! It is very much appreciated!!! Also, checked out the link you provided.
Motorola global site does not list E5 Cruise (XT1921 2) as one that can be bootloader unlocked. Can the bootloader still be unlocked anyway?

RLBuddi said:
Sorry bout the delay, ....Yes, it's still carrier locked. Thanks for your help!! It is very much appreciated!!! Also, checked out the link you provided.
Motorola global site does not list E5 Cruise (XT1921 2) as one that can be bootloader unlocked. Can the bootloader still be unlocked anyway?
Click to expand...
Click to collapse
Moto has never listed every model that can be unlocked.
The only way to really know is go through the unlock steps.
Sent from my jerry_cheets using XDA Labs

sd_shadow said:
Moto has never listed every model that can be unlocked.
The only way to really know is go through the unlock steps.
Sent from my jerry_cheets using XDA Labs
Click to expand...
Click to collapse
Follow unlocking steps from the Moto site? Or elsewhere?

RLBuddi said:
Follow unlocking steps from the Moto site? Or elsewhere?
Click to expand...
Click to collapse
Yes, Moto site and I have some info here
https://forum.xda-developers.com/general/rooting-roms/guide-locking-motorola-bootloader-t4079111
Sent from my jerry_cheets using XDA Labs

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.