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

Impossible to flash for fastboot-rsd lite!

Hello, I have a moto g 2014 xt1063 , from a friend who gave it to me to repair it (which left me with no more remedies to consult, since I read everywhere and still, I do not find any solution)
The phone gave me already in fastboot mode, with different errors to enter the recovery (boot up) and no way to install a stock, since in all I get "FAILED (remote failure)"
In the roms that I have tried (the ones that are supposed to be stocks for this type of phone). The skinny to know nothing android, I did not know in which stock version was (if 4.4.4 or 5.0.2) I put a fastboot getvar all and I throw this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4807(*)
(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 Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D726FMS
(bootloader) cid: 0x000C
(bootloader) channelid: 0x05
(bootloader) uid: B6331F080F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from recovery boot mode
(bootloader) imei: 353332060924115
(bootloader) meid:
(bootloader) date: 06-20-2015
(bootloader) sku: XT1063
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jun 27 12:40:47 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retla/titan_umts:4.
(bootloader) ro.build.fingerprint[1]: 4.4/KXB21.85-23/30:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.23.titan_retla
(bootloader) ro.build.version.full[1]: .retla.en.01
(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-g668a77b ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 26 20:03:02 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V48.07-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.07-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V48.07-0-g71b1aae-dirty
(bootloader) tz.git: git=MBM-NG-V48.07-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V48.07-0-ge875a20
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D726FMS
(bootloader) sutinfo:
all: listed above
finished. total time: 0.062s
I assumed by what I said that it was a 4.4.4 download from here, the stock firmware, however as I said above the blessed error in the fastboot FAILED (remote failure)
In each command set, the bootloader is unlocked. I already probe with fastboot oem fb_mode_clear, and other things reviewed in xda. I do not know what else to do ... Any solutions? (Clarify the bootloader also throws me the error (bootloader) Failed to flash partition recovery, but by reading does not matter said error)
Now at the moment, after several attempts, I get this "fastboot reason: failure-through from boot boot mode" error.
Try to put a TWRP recovery for titan (do not try some cyanogen), since the errors when flashing the recovery are the same that always throw me.
If you need more information, let me know.
Sorry for my horrible English. I speak Spanish, by the doubts.
From already thank you very much!

Stuck in fastboot mode, with OEM blocked, fastboot not accepting commands.

In short I can't flash on any official device rom, and the bootloader is blocked, which I actually need to enable and the OEM at the developer's option.
But I can't turn on the device because the phone says it has a different operating system, and goes back to fastboot. (Then after this message, it goes to the normal Motorola logo, but get stuck there)
Can anyone help me with this? I cant even flash the latest Android version for my phone (Android 10 for XT1965-2), fastboot and mfasboot is not accepting my commands.
GETVAR ALL
After some tries only this command seems to be working.
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) allt-su: not found
getvar:all FAILED (remote failure)
finished. total time: 0.003s
C:\Minimal ADB and Fastboot>fastboot getvar all
getvar:all FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200410
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0054997355
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 7FB0DF4F
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355577095140552
(bootloader) meid:
(bootloader) date: 03-11-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C44559
(bootloader) battery-voltage: 3813
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPWS30.6
(bootloader) ro.build.fingerprint[1]: 1-21-9/664a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[3]: pr 10 06:08:41 CDT 2020
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9489-200410
(bootloader) git:xbl: MBM-3.0-lake_retail-efaf0cccb-200410
(bootloader) gitmic: MBM-3.0-lake_retail-efaf0cccb-200410
(bootloader) git:rpm: MBM-3.0-lake_retail-0dc899d-200410
(bootloader) git:tz: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:hyp: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:devcfg: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:cmnlib: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:keymaster: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) gitrov: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:storsec: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.170s
ps: I'm using the translator because I don't speak English.
I tried everything possible, wiping data/cache,adb sideload rom.zip, flashing using mfasboot and fasboot, RSD LITE (This one does not shows me device).
The ONLY thing i didnt tried yet, was another cable, im using a paralel cable of a good quality.
When it doesn't show errors or it doesn't recognize commands, it just gets stuck.
(bootloader) max-sparse: not found
getvar:max-sparse-size FAILED (remote failure)
finished. total time: 0.005s
...
FAILED (remote: unknown command)
finished. total time: 0.002s
(bootloader) has: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'partition' (37 KB)...
(bootloader) Failed to get the number of bytes to download
FAILED (remote failure)
finished. total time: 0.006s
(bootloader) max: not found
target didn't report max-download-size
sending 'bootloader' (9520 KB)...
please any help ?

it looks like all my partitions are missing, is there anyway to create them ? when i trie 'adb shell' i get 'errror closed'.
can someone point me the direction ?

Mine only goes to Fastboot, he can't even start Android.

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.