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?

moto g 2014 stuck at logo

dear i have moto g 2014 usa
yesterday the battery was dead and after recharging it, the phone stuck at the logo and reboot
and when i boot to fast boot and choose any option like normal powerup, recovery,factory it reboot and stuck again
at the moto logo.
my device is locked and i tried to flash it using the mfastboot v2 with many official rom
XT1063_TITAN_RETLA_5.0.2_LXB22.99-16.3_cid12_CFC.xml
RETLA_XT1063_4.4.4_KXB21.85-23_cid12_CFC_SVC.xml
adb didn't detect my device as connected, but mfastboot did.
mfastboot.exe oem lock begin> run okay
mfastboot.exe flash partition gpt.bin > run okay
mfastboot.exe flash motoboot motoboot.img > run okay
mfastboot.exe flash logo logo.bin > run okay
mfastboot.exe flash boot boot.img > give me this error
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.341s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.793s
and on the phone screen it say hab check failed for boot , failed to verify hab image boot.
i need your help

douha-it said:
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.793s
and on the phone screen it say hab check failed for boot , failed to verify hab image boot.
i need your help
Click to expand...
Click to collapse
If you're trying to install an older version of Android this error can happen.

Danilo-Sanchez said:
If you're trying to install an older version of Android this error can happen.
Click to expand...
Click to collapse
i don't know what was installed on it, is there is any way to know with fastboot, also i tried kit kat and lollipop, and nothing worked, if you have working link for lollipop or newer rom kindly send me the link
here is the details form fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4883(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D323RBX
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 754DBA060F000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 359297052726493
(bootloader) meid:
(bootloader) date: 10-24-2014
(bootloader) sku: XT1063
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jun 19 13:11:50 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retuglb/titan_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.85-23/21:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.23.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:
(bootloader) kernel.version[0]: Linux version 3.4.42-g668a77b ([email protected]
(bootloader) kernel.version[1]: ilclbld53) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 26 20:21:50 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V48.83-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.83-0-g22c58e4
(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 0/0
(bootloader) productid: ZX1D323RBX
(bootloader) sutinfo:
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.073s

douha-it said:
i don't know what was installed on it, is there is any way to know with fastboot, also i tried kit kat and lollipop, and nothing worked, if you have working link for lollipop or newer rom kindly send me the link
here is the details form fastboot getvar all
(bootloader) sku: XT1063
Click to expand...
Click to collapse
Try to install this rom: http://forum.xda-developers.com/showpost.php?p=58585477&postcount=2

Danilo-Sanchez said:
Try to install this rom: http://forum.xda-developers.com/showpost.php?p=58585477&postcount=2
Click to expand...
Click to collapse
thanks it did work

i softbricked moto g6 :(

so here i am, after 2 days of scrutinizing every corner of the internet, looking for solution. i had my moto g6 on pie but out of curiosity i wanted try out different roms and here is what happened:
- after ive successfully unlocked the oem lock, installed twrp and tried to install different roms just to run into error 255 and such i gave up and thought **** it lets go back to original rom, so i fired up fastboot and put back oreo that i downloaded from here, the splashscreen however was still bearing the 'device has been unlocked and cant be trusted' message, so i thought i would put back the oem lock and then formatted the device... ooops and thats when i started having these problems.
- since then i cant install any rom - stock or mod (i was however successful in flashing twrp back on the phone)
- fastboot says FLASHING_LOCKED and having tried maybe 6 different stock roms i noticed that i can flash these two lines without problems:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
but anything after that is giving me (bootloader) flash permission denied FAILED (remote failure) in powershell
so to sum it up: i can boot into fastboot or twrp but i cant do much anything else
ive seemed to exhaust every remote advice out there and really dont know what to do anymore
any of you guys could point me in the right direction? or is the phone done and done?
here is the fastboot var list
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) meid:
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 26 14: 4:32 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
thx
Peter

You have locked bootloader you cant flash anything ....unlock it, flash rom (optionaly flash stock rom and lock booloader)
mybea you can try "fastboot flashing unlock"

najjannajS650 said:
You have locked bootloader you cant flash anything ....unlock it, flash rom (optionaly flash stock rom and lock booloader)
mybea you can try "fastboot flashing unlock"
Click to expand...
Click to collapse
thanks, i think ive already tried that already before,
here is a recap of what happens when i type in fastboot flashing unlock
- (bootloader) WARNING: This command erases all user data. (bootloader) Please re-run this command to continue.
- (bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer (bootloader) Options.
i dont have any rom installed so i cant get into developers options and allow OEM unlock
edited: and if i try ./fastboot oem unlock
i get
... (bootloader) invalid boot state
:crying:

nobody has solution to this? really????

delosanto said:
nobody has solution to this? really????
Click to expand...
Click to collapse
You don't need to unlock the bootloader to flash the stock firmware. The reason gpt.bin and the bootloader won't flash is because you're attempting to downgrade them. Flash everything in your firmware in order and if something fails to flash, then just skip it and go to the next item in line. It should still work.

Spaceminer said:
You don't need to unlock the bootloader to flash the stock firmware. The reason gpt.bin and the bootloader won't flash is because you're attempting to downgrade them. Flash everything in your firmware in order and if something fails to flash, then just skip it and go to the next item in line. It should still work.
Click to expand...
Click to collapse
thanks man but those two files are the only files that seem to flash.. the rest is giving flashing denied error
after digging around xda even more ive realized im in the same situation as the guy: https://forum.xda-developers.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215
ive managed to brick it real good this time, quoting a nice chap who tried to help him: "You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK"
im really sad at this point, i didnt even have the phone for a week and even being it a budget phone i really really liked it..
RIP moto g6 you were my first... bricked... phone :crying:

delosanto said:
thanks man but those two files are the only files that seem to flash.. the rest is giving flashing denied error
after digging around xda even more ive realized im in the same situation as the guy: https://forum.xda-developers.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215
ive managed to brick it real good this time, quoting a nice chap who tried to help him: "You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK"
im really sad at this point, i didnt even have the phone for a week and even being it a budget phone i really really liked it..
RIP moto g6 you were my first... bricked... phone :crying:
Click to expand...
Click to collapse
I don't think you're bricked just yet. From fastboot try the following commands;
fastboot oem fb_mode_set
fastboot format -w
fastboot erase userdata
fastboot erase cache
fastboot erase DRR
Then try flashing your firmware again. Also, something would help is running the command;
fastboot getvar all
And posting what that says. DO NOT include your MEID number. I don't need it and it should never be given out.

Spaceminer said:
I don't think you're bricked just yet. From fastboot try the following commands;
fastboot oem fb_mode_set
fastboot format -w
fastboot erase userdata
fastboot erase cache
fastboot erase DRR
Then try flashing your firmware again. Also, something would help is running the command;
fastboot getvar all
And posting what that says. DO NOT include your MEID number. I don't need it and it should never be given out.
Click to expand...
Click to collapse
ok, here goes nothing
fastboot oem fb_mode_set returns OKAY [ 0.002s] finished. total time: 0.003s
fastboot format -w returns fastboot: usage: expected argument
fastboot erase userdata returns (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.004s
fastboot erase cache returns (bootloader) Permission denied FAILED (remote failure)
fastboot erase DRR returns (bootloader) Permission denied FAILED (remote failure)
getvarall info:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 22 19:25:37 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above

delosanto said:
ok, here goes nothing
fastboot oem fb_mode_set returns OKAY [ 0.002s] finished. total time: 0.003s
fastboot format -w returns fastboot: usage: expected argument
fastboot erase userdata returns (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.004s
fastboot erase cache returns (bootloader) Permission denied FAILED (remote failure)
fastboot erase DRR returns (bootloader) Permission denied FAILED (remote failure)
getvarall info:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 22 19:25:37 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: son[email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Click to expand...
Click to collapse
What country are you in? You have a software mismatch going on. It says your carrier is RETGB which is Great Britain, but your Blur version is saying Retail US.

Spaceminer said:
What country are you in? You have a software mismatch going on. It says your carrier is RETGB which is Great Britain, but your Blur version is saying Retail US.
Click to expand...
Click to collapse
im in the uk, please dont say there is still hope

delosanto said:
im in the uk, please dont say there is still hope
Click to expand...
Click to collapse
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.

Spaceminer said:
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Click to expand...
Click to collapse
i did exactly as you said, getting the same results as before
the first two files gpt and bootloader seem to flash fine but the rest is giving me the same error (bootloader) flash permission denied FAILED (remote failure)
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.078s]
finished. total time: 0.078s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.417s]
finished. total time: 0.630s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62664 KB)...
OKAY [ 1.660s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.665s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.219s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.219s
i tried to flashed the files exactly in the order they appear in .info file
./fastboot oem fb_mode_set
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./fastboot flash modem NON-HLOS.bin
./fastboot flash fsg fsg.mbn
./fastboot flash dsp adspso.bin
./fastboot flash logo logo.bin
./fastboot flash boot boot.img
./fastboot flash recovery recovery.img
./fastboot flash system system.img_sparsechunk.0
./fastboot flash system system.img_sparsechunk.1
./fastboot flash system system.img_sparsechunk.2
./fastboot flash system system.img_sparsechunk.3
./fastboot flash system system.img_sparsechunk.4
./fastboot flash system system.img_sparsechunk.5
./fastboot flash system system.img_sparsechunk.6
./fastboot flash system system.img_sparsechunk.7
./fastboot flash system system.img_sparsechunk.8
./fastboot flash system system.img_sparsechunk.9
./fastboot flash vendor vendor.img_sparsechunk.0
./fastboot flash vendor vendor.img_sparsechunk.1
./fastboot flash oem oem.img
./fastboot erase cache
./fastboot erase userdata
./fastboot erase ddr
./fastboot oem fb_mode_clear
./fastboot reboot

delosanto said:
i did exactly as you said, getting the same results as before
the first two files gpt and bootloader seem to flash fine but the rest is giving me the same error (bootloader) flash permission denied FAILED (remote failure)
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.078s]
finished. total time: 0.078s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.417s]
finished. total time: 0.630s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62664 KB)...
OKAY [ 1.660s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.665s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.219s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.219s
Click to expand...
Click to collapse
It looks like you have the correct firmware. If you didn't then the bootloader shouldn't be able to flash. You aren't being blocked by frp either, so that's not the problem. I'll do some research and see if I can find a way to fix this. It should allow you to flash stock firmware since it's signed by Motorola. This is a tough one.
If you're using Windows and have not tried this already, try opening the command prompt with administrator privileges. If you happen to be using Windows 10, make sure that you're using the older cmd and not powershell. If you have not tried using a different usb port, this might be worth a shot. I'd try ports that are directly connected to the motherboard. Try USB 2.0 and 3.0 if you have both. Also be sure to use the original USB cord that it came with if you have it. I'll see what I can dig up in the meantime.
---------- Post added at 07:09 PM ---------- Previous post was at 06:57 PM ----------
@delosanto
Are you able to boot or flash twrp?

Spaceminer said:
It looks like you have the correct firmware. If you didn't then the bootloader shouldn't be able to flash. You aren't being blocked by frp either, so that's not the problem. I'll do some research and see if I can find a way to fix this. It should allow you to flash stock firmware since it's signed by Motorola. This is a tough one.
If you're using Windows and have not tried this already, try opening the command prompt with administrator privileges. If you happen to be using Windows 10, make sure that you're using the older cmd and not powershell. If you have not tried using a different usb port, this might be worth a shot. I'd try ports that are directly connected to the motherboard. Try USB 2.0 and 3.0 if you have both. Also be sure to use the original USB cord that it came with if you have it. I'll see what I can dig up in the meantime.
Click to expand...
Click to collapse
thank you! i think i must have read and tried everything there is out there trying to bring the poor little fella back to life.. ive tried different ports, methods, ROMs, different cables, tomorrow im gonna try what youre suggesting - the older cmd but i doubt it will make any difference, since i was able to flash and re-flash this phone just fine before i somehow managed to **** up the oem lock with no possibility to unlock it since there is no OS.
yes, im able to totally erase twrp (pic of android with red triangle and NO COMMAND) and then bring it back by booting twrp and consequently flashing twrp so it's there back under recovery mode

Spaceminer said:
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Click to expand...
Click to collapse
I haven't seen the encrypting screen on Pie... I've only seen it on Oreo.

Ragarianok said:
I haven't seen the encrypting screen on Pie... I've only seen it on Oreo.
Click to expand...
Click to collapse
the last OS that was successfully flashed was Oreo

delosanto said:
the last OS that was successfully flashed was Oreo
Click to expand...
Click to collapse
I'm not sure if I was reading that correctly, but are you able to boot twrp? If so, try formatting /data and running fix permissions. If you can only boot the stock recovery (red triangle), try factory resetting. You can pull up the menu in stock recovery by pressing Power+Volume Up at the "no command" screen. If you can reset the phone through either method, then try flashing the firmware again. Maybe a stupid question, but have you tried flashing the last Oreo RETGB xt1925-4 firmware already? (There's a few different RETGB firmwares.)

Spaceminer said:
I'm not sure if I was reading that correctly, but are you able to boot twrp? If so, try formatting /data and running fix permissions. If you can only boot the stock recovery (red triangle), try factory resetting. You can pull up the menu in stock recovery by pressing Power+Volume Up at the "no command" screen. If you can reset the phone through either method, then try flashing the firmware again. Maybe a stupid question, but have you tried flashing the last Oreo RETGB xt1925-4 firmware already? (There's a few different RETGB firmwares.)
Click to expand...
Click to collapse
twrp runs fine, what i cant get rid of is the flashing_locked message in fastboot..
this i think prevents flashing ANYTHING onto the phone except two files:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
flashing any other file returns permission denied
and ive tried at least 6 different roms

delosanto said:
twrp runs fine, what i cant get rid of is the flashing_locked message in fastboot..
this i think prevents flashing ANYTHING onto the phone except two files:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
flashing any other file returns permission denied
and ive tried at least 6 different roms
Click to expand...
Click to collapse
Try flashing this boot.img in fastboot. If it fails, try using TWRP.

Spaceminer said:
Try flashing this boot.img in fastboot. If it fails, try using TWRP.
Click to expand...
Click to collapse
but when i try to flash the stock rom, again i get past the first two files gpt.bin and bootloader.bit but the rest is giving me the same error
(bootloader) flash permission denied
FAILED (remote failure)
but then it crashes back to fastboot
and i even did a clean windows installation today

[Recovery] Moto g7 Plus with blocked bootloader.

Recently I went to update the rom of my moto G7 +, but during the update process the bootloader blocked ... I tried to perform the unlock again however the unlock option is disabled, and to make it worse it does not start, it is only on the recovery mode screen .
I already downloaded a more current firmware, but the bootloader does not allow installation.

Best to try the LMSA tool to reflash back to stock..
Download https://support.lenovo.com/ca/en/downloads/ds101291
Guide https://support.lenovo.com/us/en/solutions/HT102605

Thanks for the answer.
Thanks for the answer.
When I try to connect the LMSA to the phone it gives an error.
"failed to match the connected device reconnect device then try again"
I tried several times, connecting the device after selecting the model, and vice versa, however the error persists.

wfsmnt said:
Recently I went to update the rom of my moto G7 +, but during the update process the bootloader blocked ... I tried to perform the unlock again however the unlock option is disabled, and to make it worse it does not start, it is only on the recovery mode screen .
I already downloaded a more current firmware, but the bootloader does not allow installation.
Click to expand...
Click to collapse
Bootloader screen => get your model (XT19XX)=> download the current firmware

WoKoschekk said:
Bootloader screen => get your model (XT19XX)=> download the current firmware
Click to expand...
Click to collapse
XT1965-2

Thanks for the answer.
WoKoschekk said:
Bootloader screen => get your model (XT19XX)=> download the current firmware
Click to expand...
Click to collapse
Even downloading the latest firmware version the bootloader gives access denied

wfsmnt said:
Even downloading the latest firmware version the bootloader gives access denied
Click to expand...
Click to collapse
Could you post the output of "fastboot getvar all" here? Furthermore it would be helpful to know the build no of your downloaded firmware.

Thanks for the answer.
WoKoschekk said:
Could you post the output of "fastboot getvar all" here? Furthermore it would be helpful to know the build no of your downloaded firmware.
Click to expand...
Click to collapse
============================================================
GETVAR ALL
D:\Users\Wilian\Downloads\>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9-191220
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ###############
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: CEE77785
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: #####################
(bootloader) meid:
(bootloader) date: 01-30-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: ###################
(bootloader) battery-voltage: 4281
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPW30.61
(bootloader) ro.build.fingerprint[1]: -21/cb81e: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-38523c9-191220
(bootloader) git:xbl: MBM-3.0-lake_retail-923e768-191220
(bootloader) gitmic: MBM-3.0-lake_retail-923e768-191220
(bootloader) git:rpm: MBM-3.0-lake_retail-50d7845-dirty-191220
(bootloader) git:tz: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:hyp: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:devcfg: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:keymaster: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) gitrov: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:storsec: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) frp-state: protected (77)
(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: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.109s
====================================================================
Follows the build of the downloaded rom.
BUILD REQUEST INFO:
SW Version: lake-user 10 QPWS30.61-21-3 0f1d7 release-keysM636_13.45.02.60R
MBM Version: MBM-3.0-lake_retail-923e768-200214
Modem Version: M636_13.45.02.60R
FSG Version: FSG-660-10.98
Build Fingerprint: motorola/lake/lake:10/QPWS30.61-21-3/0f1d7:user/release-keys
=================================================================
I tried to install using the latest rom released too.
BUILD REQUEST INFO:
SW Version: lake-user 10 QPWS30.61-21-9 664a release-keysM636_13.45.02.60R
Modem Version: M636_13.45.02.60R
FSG Version: FSG-660-10.98
MBM Version: MBM-3.0-lake_retail-efaf0cccb-200410
Build Fingerprint: motorola/lake/lake:10/QPWS30.61-21-9/664a:user/release-keys

wfsmnt said:
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPW30.61
(bootloader) ro.build.fingerprint[1]: -21/cb81e:user/release-keys
Click to expand...
Click to collapse
As you can see in your output the current installed version is motorola/lake_n/lake_n:10/QPW30.61-21/cb81e:user/release-keys.
You should try to flash exactly the same build matching to your current firmware. (download here)
Maybe the error occured due to trying to "update" your firmware (current: 30.61-21 => new: 30.61-21-3/-9) while the bootloader is locked.
Hope this solves your problem!
---------- Post added at 01:10 AM ---------- Previous post was at 01:02 AM ----------
And don't forget to use the flashing commands of the inside flashfile.xml!! Sometimes the number of the system.img_sparsechunks is different.
DO NOT USE ANY FLASH COMMANDS FROM OTHER USERS!!

Thanks for the answer.
WoKoschekk said:
As you can see in your output the current installed version is motorola/lake_n/lake_n:10/QPW30.61-21/cb81e:user/release-keys.
You should try to flash exactly the same build matching to your current firmware. (download here)
Maybe the error occured due to trying to "update" your firmware (current: 30.61-21 => new: 30.61-21-3/-9) while the bootloader is locked.
Hope this solves your problem!
---------- Post added at 01:10 AM ---------- Previous post was at 01:02 AM ----------
And don't forget to use the flashing commands of the inside flashfile.xml!! Sometimes the number of the system.img_sparsechunks is different.
DO NOT USE ANY FLASH COMMANDS FROM OTHER USERS!!
Click to expand...
Click to collapse
Even if you apply the rom you sent me permission is denied.
===============================================================
Microsoft Windows [versão 10.0.18363.900]
(c) 2019 Microsoft Corporation. Todos os direitos reservados.
C:\Users\Wilian\Downloads\XT1965-2_LAKE_RETBR_10_QPW30.61-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.006s
C:\Users\Wilian\Downloads\XT1965-2_LAKE_RETBR_10_QPW30.61-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.010s]
finished. total time: 0.013s
C:\Users\Wilian\Downloads\XT1965-2_LAKE_RETBR_10_QPW30.61-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (37 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.145s]
finished. total time: 0.159s
C:\Users\Wilian\Downloads\XT1965-2_LAKE_RETBR_10_QPW30.61-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.291s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.361s
C:\Users\Wilian\Downloads\XT1965-2_LAKE_RETBR_10_QPW30.61-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (76484 KB)...
OKAY [ 2.164s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.183s

wfsmnt said:
Even if you apply the rom you sent me permission is denied.
Click to expand...
Click to collapse
I'm running out of ideas... The bootloader.img and its signature is matching completely with your output of getvar all.
On some older devices of the Moto G series the mfastboot tools were helpful in your case. The binaries may be old but this is the latest version of the tool...
The next step would be a blank flash.

mfastboot tools

It's like fastboot, but especially for Motorola devices by Motorola. The commands are "mfastboot" instead of "fastboot". That's all.

WoKoschekk said:
It's like fastboot, but especially for Motorola devices by Motorola. The commands are "mfastboot" instead of "fastboot". That's all.
Click to expand...
Click to collapse
Unfortunately the same result.

WoKoschekk said:
It's like fastboot, but especially for Motorola devices by Motorola. The commands are "mfastboot" instead of "fastboot". That's all.
Click to expand...
Click to collapse
How can we perform the blank-flash

wfsmnt said:
How can we perform the blank-flash
Click to expand...
Click to collapse
Sorry, I can't help you with that.

Are you using Motorola's original cable, or another one? I just had problems flashing with 'custom' cable. Just connect directly by USB-C (I'm hoping that's possible for you to try).

sado1 said:
Are you using Motorola's original cable, or another one? I just had problems flashing with 'custom' cable. Just connect directly by USB-C (I'm hoping that's possible for you to try).
Click to expand...
Click to collapse
He gets "permission denied" and that's not a connection error.
Besides the first command runs without an error.

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.