Database Info

[Help]Moto G2014(XT1068) - max-sparse-size

Hello,
I'm having troubles with my Moto G2014 XT1068.
I was with this RETAILDSDSALL_XT1068_4.4.4_KXB21.85-27_cid7_CFC_SVC.xml on my phone.
Yesterday i tried to downgrad to this ROM RETAILDSDSALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC_SVC.xml
I was able to to this.
After that I tried to go back to the ROM RETAILDSDSALL_XT1068_4.4.4_KXB21.85-27_cid7_CFC_SVC.xml but i couldn't.
I have adb, fastboot e mfastboot in the same folder of the ROM and I'm doing this steps:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
Doing this im always getting the error:
mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
Could anyone help me?

[Q] Moto g xt1033 convert gpe to stock problem

first i flash gpe rom in xt1033 but there is some poblem in rom so i am trying to flash stock rom using fastboot using
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
after completed this process when device was roboot it show gpe rom
how can i restore stock rom now
please help me

Stuck on Bootloader Unlocked Warning

i was on custom rom 5.1 lollipop then i though i should go back to stock rom i tried one tutorial out there.
The commands i ran on fastboot are below :
oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
but now it's stuck on bootloader. any help would be appreciate

Same problem here. I was on GPE 5.1. Did exact the same steps and now I just see "Warning - Bootloader unlocked".
Edit: Alright, got it working. Was using fastboot instead of mfastboot. Just follow the steps here: http://forum.xda-developers.com/moto-g/general/how-to-to-stock-5-0-2-motorola-lollipop-t3077806 or use the attached scripts.
Edit 2: Before the bootanimation it says "Warning-Bootloader unlocked" but I already locked it again. It also says "Device is LOCKED" in recovery. Any ideas?
Edit 3: Alright, fixed it with the MotoTool AIO

Unlocked bootloader in January Security Patch and Flashed LineageOS,now can't go back

Hello!
I was trying some custom ROMs on my XT 1550 and then went back to stock using the July security patch full firmware zip posted on XDA by @lost101.
->I updated to January security patch through system updates. I unlocked bootloader again and flashed LineageOS.
->Now when I type the commands used to flash the stock firmware,it shows "Preflash validation error". A quick search on XDA shows not to flash partition gpt .bin and bootloader,but even after skipping that,even the sparsechunk files are showing error-not signed,but I have earlier used them several times to go back to stock. My system was updated to January patch but I'm trying to flash july patch,as January patch for XT 1550 is not available in XDA for download.
Bootloader status: 3(unlocked)
I can boot to twrp,3.0.2-r5,but:
->data and cache can't be mounted
->custom ROMs can't be flashed again as a result of the above
I didn't have backups and I wiped the userdata while following the commands to relock bootloader.
For your kind reference,I generally went back to stock using these commands,specific to XT 1550:
fastboot devices
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
Kindly help as it is my primary device and I can't boot it up into anything.

adb screen shows this:
C:\adb>fastboot devices
************** fastboot
C:\adb>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.038s]
finished. total time: 0.039s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.050s]
writing 'logo'...
OKAY [ 0.290s]
finished. total time: 0.344s
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.520s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.056s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.524s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.064s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (247489 KB)...
OKAY [ 7.764s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.218s
C:\adb>

Try with these commands
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Skip gpt.bin and bootloadet.img

Thanks a lot bro! You saved my device! Now if I want to relock bootloader for security,can I write "fastboot oem lock" on adb?

debopriyobasu said:
Thanks a lot bro! You saved my device! Now if I want to relock bootloader for security,can I write "fastboot oem lock" on adb?
Click to expand...
Click to collapse
No, you cannot relock the bootloader... The only way to relock is to flash a full signed image, and you did not... And you cannot flash a full signed image until the January security update image (or later version) is released.
There is no advantage to relocking the bootloader, your warranty is gone and it cannot be restored, and you will never lose the unlocked bootloader warning screen unless you flash a custom boot logo file, regardless if relock or not.

Thanks for the info! One last question: Can I update my system to January patch now? I'm getting system update notifications. I'm asking to be double sure such that I don't brick my device while updating with an unlocked bootloader. Thanks!

debopriyobasu said:
Thanks for the info! One last question: Can I update my system to January patch now? I'm getting system update notifications. I'm asking to be double sure such that I don't brick my device while updating with an unlocked bootloader. Thanks!
Click to expand...
Click to collapse
You can update with unlock bootloader but make sure to have stock recovery and unmodified files aka no root.
Regards
Ayan

Flashing Problems! :/
You need to wait to the next security patch... then flash all commands except fastboot oem lock begin and fastboot oem lock...... it works! the same thing happen with my old MotoX and i waited months! then i flashed and everything was fine!
I recommend you for your next ROM flashing experiments and updates to flash like this the patches...
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
you may try this commands! hope it works!:good:

Bootloader LOCKED after use MBM-CI. (Bootloader) Preflash validation failed

Hi everyone, i have a reallly annoying problem after use MBM-CI but, before of explain the problem, i have to say that i flashed my MOTO G XT1032 (41.1A) with Android 4.4.4 GPE Firmware ( GPE_XT1032_KTU84P.M003_CFC.xml ) and it ran very good so i charge the battery until 32% and i tried to upgrade my phone from settings, all was going normal: The phone reset with a black background, the logo of Android and a blue bar with the message of says that my phone is upgrading, please wait; the problem beging when the blue bar was too close of finish and the phone turned off, it not turn on so i hold the Power button and the phone vibratte but nothing happens, i connected it to the PC and try again to turn on but i only can hear the sound of "Device connected", "Device disconnected" from Windows; i search a solution and found this video "REVIVIR MOTO G 2013 SOLUCIÓN FULL BRICK| NO MAS LADRILLO!!!!" from "Valtitec Indrustries" in YouTube (i know, it's in spanish) and use the BlankFlash Tool from the description of that video (i already had the Qualcomm HS-USB QDLoader 9008 Driver installed in my pc), good, it works buuuut... My phone get in the bootloader screen and shows this info:
AP Fastboot Flash Mode (S)
41.1A(*) (sha-80481ae, 2015-04-10 14:30:28)
CPU: MSM8226 CS
eMMC: 8GB Toshiba RV=06 PV=51 TY=17
DRAM: 1024MB Samsung S4 SDRAM DIE=4GB
Battery OK (After use MBM, Battery was LOW)
Device is LOCKED. Status Code: 0
Transfer Mode: USB Connected
Fastboot Reason: Failed to initialize partition table​
So, i tried to flash it but after of some tries, i read the part of shows "Device is LOCKED. Status Code: 0", i search in Google and found a lot of forums and tried to solve it, the results are:
SDK Tools: fastboot oem get_unlock_data: (bootloader) Failed to get unlock data, please try again!
Try to flash the phone shows in GPT.bin "(Bootloader) Preflash validation failed", same in motoboot, aditional, motoboot patition not found; in the other files shows that "(Bootloader) Permission Denied", and all the files have failure.
I can Only use "Barcodes" in Bootloader and it shows: IMEI, SKU: 000000....; Date: 01-01-1970, Serial Number: 9fd6f218
I tried to flash my phone with various versions of Android:
RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml
BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml
XT1032_FALCON_RETBR_5.1_LPB23.13-56_cid12_CFC.xml
GPE_5.1_XT1032_LMY47M.M001_CFC.xml
GPE_XT1032_5.1_LMY47M.M005_cid222_CFC.xml
GPE_XT1032_KTU84P.M003_CFC.xml
XT1032_FALCON_TEFCO_5.1_LPBS23.13-56-2_cid12_CFC.xml
XT1032_MOVISTAR-CO-SS_4.4.4_KXB21.14-L1.40-1_1_cid12_CFC_1FF.xml
But no one works; now the MBM tool not works, i reinstall the Qualcomm driver and now shows a error :v, and the tools that i used are:
adt-bundle-windows-x86_64-20131030
MBM (BlankFlash of the video)
Moto Auto Flash Tool v6.6
Riff Box Jtag
ADB Tools (ADB Fastboot Tools)
mfastboot
And the sequences of cmd that i used are:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash gpt gpt.bin
fastboot flash motoboot motoboot.img
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 (I didn't say but if the firmware have 3 or 4 sparsechunks, i put the sequence in front of this)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot-bootloader
And no one works; ¿what i can do?, i'm poor and not have money for buy a cel phone and neither very cheap phone, only can try to fix this and it's very important for the grupal works of the university :c HELP :crying: