Related
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?
got a moto x 2014 device, model xt1097
1. I'm unable to oem unlock with the code i've got from moto dev, it says i should enable it in dev options, but there is no such option in the dev menu (running 5.1 stock)
2. I'm unable to flash custom recovery, although it seems to be successful
Code:
fastboot flash recovery twrp-2.8.7.0-victara.img
target reported max download size of 536870912 bytes
sending 'recovery' (8590 KB)...
OKAY [ 0.338s]
writing 'recovery'...
OKAY [ 0.339s]
finished. total time: 0.681s
when booting into recovery, i see dead droid logo
what should be my next steps?
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: no
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno:
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Apr 14 21: 3:24 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retbr/victara:5.1
(bootloader) ro.build.fingerprint[1]: /LPE23.32-14/13:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.11.14.victara_ret
(bootloader) ro.build.version.full[1]: br.retbr.en.BR
(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: MSM8974BP_4235210.110.09.11B DFLT_FSG
(bootloader) kernel.version[0]: Linux version 3.4.42-g0ced813 ([email protected]
(bootloader) kernel.version[1]: ilclbld28) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Apr 16 16:40:09 CDT 2015
(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:
all: listed above
finished. total time: 0.060s
You can't unlock or install custom recovery on a XT1097.
thanks, any way to root it without custom recovery?
sh33z0r said:
thanks, any way to root it without custom recovery?
Click to expand...
Click to collapse
Flash an image using MoFo.
http://forum.xda-developers.com/showthread.php?t=3127471
Sent from my Moto X 2014 Pure Edition using Tapatalk
tried it, it says that my device is not supported, try later
perhaps because im running 5.1
sh33z0r said:
got a moto x 2014 device, model xt1097
1. I'm unable to oem unlock with the code i've got from moto dev, it says i should enable it in dev options, but there is no such option in the dev menu (running 5.1 stock)
2. I'm unable to flash custom recovery, although it seems to be successful
Code:
fastboot flash recovery twrp-2.8.7.0-victara.img
target reported max download size of 536870912 bytes
sending 'recovery' (8590 KB)...
OKAY [ 0.338s]
writing 'recovery'...
OKAY [ 0.339s]
finished. total time: 0.681s
when booting into recovery, i see dead droid logo
what should be my next steps?
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: no
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno:
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Apr 14 21: 3:24 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retbr/victara:5.1
(bootloader) ro.build.fingerprint[1]: /LPE23.32-14/13:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.11.14.victara_ret
(bootloader) ro.build.version.full[1]: br.retbr.en.BR
(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: MSM8974BP_4235210.110.09.11B DFLT_FSG
(bootloader) kernel.version[0]: Linux version 3.4.42-g0ced813 ([email protected]
(bootloader) kernel.version[1]: ilclbld28) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Apr 16 16:40:09 CDT 2015
(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:
all: listed above
finished. total time: 0.060s
Click to expand...
Click to collapse
Go to developer options. There is an option called "oem unlocking". Turn it on. After that reboot to bootloader and unlock your bootloader. Then flash you custom recovery.
Sent from my XT1095
AGISCI said:
Go to developer options. There is an option called "oem unlocking". Turn it on. After that reboot to bootloader and unlock your bootloader. Then flash you custom recovery.
Sent from my XT1095
Click to expand...
Click to collapse
That is only on Pure Edition xt1095, not AT&T xt1097.
Sent from my Moto X 2014 Pure Edition using Tapatalk
xKroniK13x said:
That is only on Pure Edition xt1095, not AT&T xt1097.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Click to expand...
Click to collapse
Not all 1097's are AT&T. Here in my country(Chile) we have the 1097 and it IS unlockable. The op never said AT&T. Plus if you read what he posted, his software is retbr. His 1097 is from brazil, so it IS unlockable.
1097 are in canada, and all south american countries, like peru, brazil, argentina, etc. And they can ALL be unlocked.
Sent from my XT1095
thanks guys, its indeed a BR device, bootloader now open, but tried flashing twice twrp, one from their site and one custom from the forums here
fastboot flash recovery twrp-2.8.7.0-victara-orig.img
target reported max download size of 536870912 bytes
sending 'recovery' (8590 KB)...
OKAY [ 0.342s]
writing 'recovery'...
OKAY [ 0.234s]
finished. total time: 0.579s
when booting to recovery, all i see is a dead droid logo with no command below.
How are you getting into recovery? Via fastboot after flash? Or did you restart the phone?
Sent from my XT1095
tried after flash and tried rebooting normal and then adb reboot recovery
sh33z0r said:
tried after flash and tried rebooting normal and then adb reboot recovery
Click to expand...
Click to collapse
Try this twrp:
https://dl.twrp.me/victara/twrp-2.8.5.0-victara.img.html
Sent from my XT1095
AGISCI said:
Not all 1097's are AT&T. Here in my country(Chile) we have the 1097 and it IS unlockable. The op never said AT&T. Plus if you read what he posted, his software is retbr. His 1097 is from brazil, so it IS unlockable.
1097 are in canada, and all south american countries, like peru, brazil, argentina, etc. And they can ALL be unlocked.
Sent from my XT1095
Click to expand...
Click to collapse
Good to know! Thanks for the info.
Sent from my Moto X 2014 Pure Edition using Tapatalk
xKroniK13x said:
Good to know! Thanks for the info.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Click to expand...
Click to collapse
No problem.
Sent from my XT1095
AGISCI said:
Try this twrp:
https://dl.twrp.me/victara/twrp-2.8.5.0-victara.img.html
Sent from my XT1095
Click to expand...
Click to collapse
nope ;[ same stock recovery again, as if nothing was flashed, btw, when i try to boot into recovery (without flashing) I'm getting kernel panic screen
sh33z0r said:
nope ;[ same stock recovery again, as if nothing was flashed, btw, when i try to boot into recovery (without flashing) I'm getting kernel panic screen
Click to expand...
Click to collapse
Do you reboot after flash? Or go straight to the twrp? Don't reboot after flash, open the recovery directly after flash by pressing down till you select "recovery", then press up to boot it.
Try this command with the twrp that I posted if the previous does not work:
fastboot boot twrp-2.8.5.0-victara.img
Sent from my XT1095
AGISCI said:
Do you reboot after flash? Or go straight to the twrp? Don't reboot after flash, open the recovery directly after flash by pressing down till you select "recovery", then press up to boot it.
Try this command with the twrp that I posted if the previous does not work:
fastboot boot twrp-2.8.5.0-victara.img
Sent from my XT1095
Click to expand...
Click to collapse
great! it worked, never though that i need some strange combo of specific version and booting right into it! now i have custom recovery and root, any other suggestions for making my X better (besides xposed)?
Yes, if you reboot before starting the recovery it does not stay flashed. Glad it is working for you.
As far as things that you can do with root and recovery. I use it for backups with titanium backup, and to run linux with "linux deploy" app.
Sent from my XT1095
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 hardbrick, only blinking led, and devices in old Qualcomm HS-USB QDLoader 9008 mode,succesfully back to fastboot and recovery, with blankflash.
xt1805 eu
now i'm try to flash stock, but still with error: (downgrading, preflash validation, no gpt.bin flash, no bl flash, erorr on flash oem partition and chunk0)
(bootloader) version-bootloader: moto-msm8953-C0.C5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 10C7D55D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPSS26.116-26-11/12:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.286.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953_24.34.07.35R SANDERS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gce86ddc-0013
(bootloader) kernel.version[1]: 4-g3301624 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Thu Mar 1 15:12:52 CST 201
(bootloader) kernel.version[4]: 8
(bootloader) sbl1.git: git=MBM-NG-VC0.C5-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VC0.C5-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) devcfg.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) keymaster.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib64.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) prov.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
any suggestion plz ?
Moto G5S plus
I think parttion table go corrupted, with downgrade-upgrade, after custom mod, any way to correct parttion table ?? gpt.bin flash give me error
bro how you recover hard brick ? share blankflash.please
How u unbrick? Please share blank flash
noio said:
After hardbrick, only blinking led, and devices in old Qualcomm HS-USB QDLoader 9008 mode,succesfully back to fastboot and recovery, with blankflash.
xt1805 eu
now i'm try to flash stock, but still with error: (downgrading, preflash validation, no gpt.bin flash, no bl flash, erorr on flash oem partition and chunk0)
(bootloader) version-bootloader: moto-msm8953-C0.C5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 10C7D55D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPSS26.116-26-11/12:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.286.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953_24.34.07.35R SANDERS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gce86ddc-0013
(bootloader) kernel.version[1]: 4-g3301624 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Thu Mar 1 15:12:52 CST 201
(bootloader) kernel.version[4]: 8
(bootloader) sbl1.git: git=MBM-NG-VC0.C5-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VC0.C5-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) devcfg.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) keymaster.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib64.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) prov.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
any suggestion plz ?
Click to expand...
Click to collapse
How u unbrick? Please share blank flash
Blankflash attached
madeaboutu said:
How u unbrick? Please share blank flash
Click to expand...
Click to collapse
blankflash attached
moto g5s plus
if succesful reboot, i have procedure to stock oreo via twrp
noio said:
if succesful reboot, i have procedure to stock oreo via twrp
Click to expand...
Click to collapse
Thanks,shall share you [email protected]
noio said:
After hardbrick, only blinking led, and devices in old Qualcomm HS-USB QDLoader 9008 mode,succesfully back to fastboot and recovery, with blankflash.
xt1805 eu
now i'm try to flash stock, but still with error: (downgrading, preflash validation, no gpt.bin flash, no bl flash, erorr on flash oem partition and chunk0)
(bootloader) version-bootloader: moto-msm8953-C0.C5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 10C7D55D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPSS26.116-26-11/12:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.286.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953_24.34.07.35R SANDERS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gce86ddc-0013
(bootloader) kernel.version[1]: 4-g3301624 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Thu Mar 1 15:12:52 CST 201
(bootloader) kernel.version[4]: 8
(bootloader) sbl1.git: git=MBM-NG-VC0.C5-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VC0.C5-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) devcfg.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) keymaster.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib64.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) prov.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
any suggestion plz ?
Click to expand...
Click to collapse
bro try to flash stock oreo 8.1 latest , bucz your are flashing 7.1.1 may be it is giving you error
re-brick ....
After blankflash, no way of flash system and oem, restoring oreo backup via twrp ok, phone boot, but no imei on oreo, because have restore twrp backup (with "getvar imei" i see correct imei), but no way of flashing system and oem via fastboot or adb, frustrated !!!!!! i have restored a loader.img from extsdcard, but are wrong, people that send me right blankflash, send me wrong image loader, now i'm rebricked with only fastboot of wrong loader(bl) restored ..... In return, i think, i've succesfoul downgraded bl, baseband and othr stuff ..... now i'm on bricked Hybrid Moto .....
madeaboutu said:
Thanks,shall share you [email protected]
Click to expand...
Click to collapse
Didnt got success with this:crying:
madeaboutu said:
Didnt got success with this:crying:
Click to expand...
Click to collapse
any solution to the error?
i hope it works
madeaboutu said:
Didnt got success with this:crying:
Click to expand...
Click to collapse
Hi, boot the twrp image and go to wipe and erase all, try until it works and then install the stock android oreo using the adb, if you got an error try again because there is a corruption of the security patches. The IMEI works after the upgrade the security patches, they are many. I have a similar trouble with my moto g5s plus. Good luck
Thank you so much awesome my congratulations God bless you
Muito obrigado sensacional meus parabéns que Deus abençoe vocês
Hey there, I have two questions.
First, is it ok for a blankflash file to be less than 2Mb in size? I saw someone claiming he managed to reverse engineer xt1806 blankflash but claimed it to be too big for him to upload.
Also, does anyone know if the xt1805 blankflash would work for a xt1806 or am I gonna mess it up further than I did? I am unable to find xt1806 blankflash.
It's been like year and a half with a hard bricked xt1806 and I am so upset about being unable to bring it back. I went to my old phone but it's not usable anymore and I'm not situation to buy a new one. Argentina sucks
Thanks in advance to any kind of reply
noio said:
blankflash attached
Click to expand...
Click to collapse
You saved my day. Thank you so much :good:
Ooops. Looks like my phone is XT1804 and this has lead me into a different situation now.
Update: Managed to hard brick my phone again by intentionally flashing the wrong bootloader which is apparently the only one that got accepted. All other legit versions gave errors. Now preparing a 32GB SD card with mmcblk0. Will try to boot with that and flash the stock ROM. Shall update if I get through. Fingers crossed.
applechap said:
You saved my day. Thank you so much :good:
Ooops. Looks like my phone is XT1804 and this has lead me into a different situation now.
Update: Managed to hard brick my phone again by intentionally flashing the wrong bootloader which is apparently the only one that got accepted. All other legit versions gave errors. Now preparing a 32GB SD card with mmcblk0. Will try to boot with that and flash the stock ROM. Shall update if I get through. Fingers crossed.
Click to expand...
Click to collapse
Hey, so you tried 1805's on a 1804 and it didn't work? I'm about to try it on a 1806, they are supposed to have the same processor so I don't get why it wouldn't work
Sagazdelrey said:
Hey, so you tried 1805's on a 1804 and it didn't work? I'm about to try it on a 1806, they are supposed to have the same processor so I don't get why it wouldn't work
Click to expand...
Click to collapse
Its because 1805 boot loader is customized for Verizion USA. Sure enough it kicked the phone out of the hard brick. But I couldn't install anything after that due to the mismatch. Looks like the only way out is to open the phone and program the chip. Too much for a spare phone for me. So its a paper weight as of now.
Today I was trying to install the original stock ROM on my Moto G5s plus ....When I used the last command fastboot reboot my mobile didn't started again....What to do now please help me I am not able to start my device again in fastboot mode or recovery mode... infact it is not turning on....even when kept on charging.....please help me out and mention steps as in order what to do.....please
Help
my phone is hard bricked Moto G5s Plus given bankflash is not working can u please help me ?
email [email protected]
Moto g5s easy hard bricked solutions on this video
Moto g5s easy solution youtube my youtube channel please search P2bro techno
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.