Database Develop

Moto G 4G/LTE XT1072 Bricked?

Hi,
i have a Moto G 4G 2015 alias Thea alias Model XT1072 and i cant restore Stock.
I have installed the Downgrade_RETDEALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC and think here i have killed the phone..
i know it is the wrong firmware, i have realized this too late... dont ask why....
so I have downloaded RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml and RETEUALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml.
But the errors when i try flashing via (m)fastboot are the same
Code:
mfastboot flash partition gpt.bin
fastboot error:
Code:
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for primary_gpt
Code:
mfastboot flash motoboot motoboot.img
fastboot error:
Code:
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for tz
Code:
mfastboot flash system system.img_sparsechunk.0
fastboot error:
Code:
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
Image is too large
So why is the Image too large?
getvar all :
(bootloader) version: 0.5
(bootloader) version-bootloader: 4883(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8500
(bootloader) radio: 0x1
(bootloader) emmc: 8GB ID=15 REV=06 PRV=02 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2233HX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-10-2015
(bootloader) sku: XT1072
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Feb 25 7:52:56 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.99-16/10:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(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-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:47:29 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.83-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.1D-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.83-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.83-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.83-0-g67407e2
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
(bootloader) productid:
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
Is the problem
Code:
(bootloader) product: titan
or any other bootloader settings?
Any ideas?

Hi,
twister_65 said:
i have a Moto G 4G 2015 alias Thea alias Model XT1072 and i cant restore Stock.
I have installed the Downgrade_RETDEALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC and think here i have killed the phone..
i know it is the wrong firmware, i have realized this too late... dont ask why....
so I have downloaded RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml and RETEUALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml.
But the errors when i try flashing via (m)fastboot are the same
Code:
mfastboot flash partition gpt.bin
fastboot error:
Code:
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for primary_gpt
Code:
mfastboot flash motoboot motoboot.img
fastboot error:
Code:
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for tz
Code:
mfastboot flash system system.img_sparsechunk.0
fastboot error:
Code:
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
Image is too large
So why is the Image too large?
getvar all :
(bootloader) version: 0.5
(bootloader) version-bootloader: 4883(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8500
(bootloader) radio: 0x1
(bootloader) emmc: 8GB ID=15 REV=06 PRV=02 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2233HX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-10-2015
(bootloader) sku: XT1072
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Feb 25 7:52:56 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.99-16/10:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(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-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:47:29 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.83-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.1D-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.83-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.83-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.83-0-g67407e2
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
(bootloader) productid:
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
Is the problem
Code:
(bootloader) product: titan
or any other bootloader settings?
Any ideas?
Click to expand...
Click to collapse
HI,
I have done exactly the same thing as you and facing the same problem while flashing the XT1072 stock firmware.
Could please let me know if you have found any solution.
Thanks

@twister_65 @omarhowlader: U both can now save for a new device, have fun.

LuK1337 said:
@twister_65 @omarhowlader: U both can now save for a new device, have fun.
Click to expand...
Click to collapse
wish you could help with your experience!!!

omarhowlader said:
wish you could help with your experience!!!
Click to expand...
Click to collapse
You can't recover your phone from wrong bootloader

luca020400 said:
You can't recover your phone from wrong bootloader
Click to expand...
Click to collapse
Why not?
I mean, is it a technical limitation? Then why can i install the old one.

twister_65 said:
Why not?
I mean, is it a technical limitation? Then why can i install the old one.
Click to expand...
Click to collapse
Because your device is technically dead xd

luca020400 said:
Because your device is technically dead xd
Click to expand...
Click to collapse
that helps now .......

twister_65 said:
that helps now .......
Click to expand...
Click to collapse
Try to flash motoboot.img from that http://www.filefactory.com/file/2zt...LXB22.99-24_cid12_subsidy-DEFAULT_CFC.xml.zip
It's the only thing that may help you lol.

LuK1337 said:
Try to flash motoboot.img from that http://www.filefactory.com/file/2zt...LXB22.99-24_cid12_subsidy-DEFAULT_CFC.xml.zip
It's the only thing that may help you lol.
Click to expand...
Click to collapse
twister_65 said:
that helps now .......
Click to expand...
Click to collapse
Did it work

Shawn5162 said:
Did it work
Click to expand...
Click to collapse
My device is currently on its way back from a service stadion, but they did not repaired it...

twister_65 said:
My device is currently on its way back from a service stadion, but they did not repaired it...
Click to expand...
Click to collapse
Is that because you broke Motorola's warranty terms of service by unlocking bootloader and flashing? Or is it a lost cause?

Addapp said:
Is that because you broke Motorola's warranty terms of service by unlocking bootloader and flashing? Or is it a lost cause?
Click to expand...
Click to collapse
Did anyone achieved to solve this problem? I am facing exactly the same issue.
The thing is that the Motorola naming is quite confusing and it is very easy to make a mistake between the different Moto Gs, so I flashed the stock ROM of a previous version and when I realized it, it was too late.
I suppose I have the wrong bootloader as it keeps giving me these "image is too large" messages when I try to flash the correct stock rom. I can install CM and other custom roms from TWRP, however at least the camera won't work.
If anyone has found a workaround, please share with us how you do it.

como vc conseguiu pisca? to com o mesmo problema: P

e2_e2 said:
Did anyone achieved to solve this problem? I am facing exactly the same issue.
The thing is that the Motorola naming is quite confusing and it is very easy to make a mistake between the different Moto Gs, so I flashed the stock ROM of a previous version and when I realized it, it was too late.
I suppose I have the wrong bootloader as it keeps giving me these "image is too large" messages when I try to flash the correct stock rom. I can install CM and other custom roms from TWRP, however at least the camera won't work.
If anyone has found a workaround, please share with us how you do it.
Click to expand...
Click to collapse
I've managed to fix my problem, I installed the correct TWRP recovery for my model and managed to install CM THEA and everything is working flawlessly.
The problem is that installing an incorrect recovery will mess the partition, I am sure I can go back to stock now if I use ADB to reflash, but I dont want do go back anymore, there is a bunch of new options avaliable im CM will wont even want the simple stock rom never again. Just Install the correct TWRP for your model and Install a custom rom , it will fix the partition and probably you will be able to reflash to stock using ADB.
This is the correct TWRP for XT1078
https://dl.twrp.me/thea/

twister_65 said:
Hi,
i have a Moto G 4G 2015 alias Thea alias Model XT1072 and i cant restore Stock.
I have installed the Downgrade_RETDEALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC and think here i have killed the phone..
i know it is the wrong firmware, i have realized this too late... dont ask why....
so I have downloaded RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml and RETEUALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml.
But the errors when i try flashing via (m)fastboot are the same
Code:
mfastboot flash partition gpt.bin
fastboot error:
Code:
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for primary_gpt
Code:
mfastboot flash motoboot motoboot.img
fastboot error:
Code:
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for tz
Code:
mfastboot flash system system.img_sparsechunk.0
fastboot error:
Code:
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
Image is too large
So why is the Image too large?
getvar all :
(bootloader) version: 0.5
(bootloader) version-bootloader: 4883(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8500
(bootloader) radio: 0x1
(bootloader) emmc: 8GB ID=15 REV=06 PRV=02 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2233HX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-10-2015
(bootloader) sku: XT1072
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Feb 25 7:52:56 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.99-16/10:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(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-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:47:29 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.83-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.1D-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.83-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.83-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.83-0-g67407e2
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
(bootloader) productid:
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
Is the problem
Code:
(bootloader) product: titan
or any other bootloader settings?
Any ideas?
Click to expand...
Click to collapse
Hello! I spend my same ... first thing you have to do is fix the bootloader using a command
" fastboot oem fb_mode_clear "
takes 10 seconds , once restored the fastboot install the firmware you had of stock again , I recommend unlock booloader for. I hope you serve , Greetings !

mega_vpr said:
Hello! I spend my same ... first thing you have to do is fix the bootloader using a command
" fastboot oem fb_mode_clear "
takes 10 seconds , once restored the fastboot install the firmware you had of stock again , I recommend unlock booloader for. I hope you serve , Greetings !
Click to expand...
Click to collapse
Did not work for me
mihilux said:
it will fix the partition and probably you will be able to reflash to stock using ADB.
Click to expand...
Click to collapse
Not really. I can use an CM AOSP flawlessly as you mention, but if you need to go back to stock (for example, if your phone hardware breaks), you won't be able to flash to the right stock rom unfortunatelly. Is not a 100% bricked phone but is a technically bricked phone, since NAND has been messed up by flashing accidentally with a wrong ROM. As you say this Motorola versioning system is really an issue in terms of deriving to bricked devices

MiSSigNNo said:
Did not work for me
Not really. I can use an CM AOSP flawlessly as you mention, but if you need to go back to stock (for example, if your phone hardware breaks), you won't be able to flash to the right stock rom unfortunatelly. Is not a 100% bricked phone but is a technically bricked phone, since NAND has been messed up by flashing accidentally with a wrong ROM. As you say this Motorola versioning system is really an issue in terms of deriving to bricked devices
Click to expand...
Click to collapse
I've the same problem, but I can go back to Stock Rom 5.0.2 though ADB and bootloader, the problem is that in the Stock Rom or CM13, CM12 my cellphone dont recognize the SIM card and the wifi =/. Someone with the same problem?

xt1096 moto x 2nd gen bricked

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

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

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

bump

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

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

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

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

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

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

My XT1063 goes "failed to validate boot image"

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.