Database Info

Flashing NON-GPE stock problem

Hello there guys! I'll resume my history.
So this was me one month after buying the Motorola Moto G XT1032 8GB, unlocking the bootloader without any problems So I wasn't really into the device info and didn't know about a GPE. So I downloaded a folder with a couple of images and .bin files and excuted a .bat inside the folder that turned my Stock 4.4.4 into Stock 4.4.2 GPE. After first reboot I just installed Paranoid Android and didn't come back to stock since then (a few months back).
Now I tried to go back to stock NON-GPE flashing "Android 4.3 Blur_Version.14.71.8.falcon_umts.Latam.en.AR" and "Android 4.4.2 Blur_Version.173.44.9.falcon_umts.Latam.en.AR" with this method GUIDE] Moto G - Restore stock firmware and I got this two errors in both of the cases:
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.030s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.363s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.405s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (619 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.161s]
finished. total time: 0.240s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.378s]
writing 'boot'...
OKAY [ 1.124s]
finished. total time: 1.502s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.379s]
writing 'recovery'...
OKAY [ 1.237s]
finished. total time: 1.617s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (256840 KB)...
OKAY [ 8.098s]
writing 'system'...
OKAY [ 17.707s]
finished. total time: 25.805s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (243300 KB)...
OKAY [ 7.668s]
writing 'system'...
OKAY [ 14.775s]
finished. total time: 22.443s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (219577 KB)...
OKAY [ 6.920s]
writing 'system'...
OKAY [ 23.237s]
finished. total time: 30.157s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47104 KB)...
OKAY [ 1.526s]
writing 'modem'...
OKAY [ 2.332s]
finished. total time: 3.859s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.070s]
finished. total time: 0.070s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.137s]
finished. total time: 0.137s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (107 KB)...
OKAY [ 0.082s]
writing 'fsg'...
OKAY [ 5.303s]
finished. total time: 5.385s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml#
Click to expand...
Click to collapse
You see? I got error with gtp.bin and motoboot.img but I kept flashing to see where that would take me. It turned out to take me witha bootloop Never going further than logo.
So what did I do? I ran that GPE 4.4.2 I flashed the first time I unlocked my bootloader. And it was alive again, booting like a charm. Now on crDroid again.
And my question is: what happened? Why am I able to flash a GPE 4.4.2 but not a Latam stock Retail for my country (Argentina)? I don't get it. I flashed from Windows and Ubuntu, with differents fastboot files, with mfasboot given in that Tutorial but nothing worked except turning it into a GPE Moto G.
Any contribution will be helpful, still want to go to stock Moto G. Cheers.

XXtremiXX said:
Hello there guys! I'll resume my history.
So this was me one month after buying the Motorola Moto G XT1032 8GB, unlocking the bootloader without any problems So I wasn't really into the device info and didn't know about a GPE. So I downloaded a folder with a couple of images and .bin files and excuted a .bat inside the folder that turned my Stock 4.4.4 into Stock 4.4.2 GPE. After first reboot I just installed Paranoid Android and didn't come back to stock since then (a few months back).
Now I tried to go back to stock NON-GPE flashing "Android 4.3 Blur_Version.14.71.8.falcon_umts.Latam.en.AR" and "Android 4.4.2 Blur_Version.173.44.9.falcon_umts.Latam.en.AR" with this method GUIDE] Moto G - Restore stock firmware and I got this two errors in both of the cases:
You see? I got error with gtp.bin and motoboot.img but I kept flashing to see where that would take me. It turned out to take me witha bootloop Never going further than logo.
So what did I do? I ran that GPE 4.4.2 I flashed the first time I unlocked my bootloader. And it was alive again, booting like a charm. Now on crDroid again.
And my question is: what happened? Why am I able to flash a GPE 4.4.2 but not a Latam stock Retail for my country (Argentina)? I don't get it. I flashed from Windows and Ubuntu, with differents fastboot files, with mfasboot given in that Tutorial but nothing worked except turning it into a GPE Moto G.
Any contribution will be helpful, still want to go to stock Moto G. Cheers.
Click to expand...
Click to collapse
Do this at your own risk:
If your phone is a gsm xt1032 then grab a EU(european) 4.4.4 stock firmware and flash that via fastboot. Should work...
If not then try flashing a custom recovery like twrp or clockworkmod. Grab the EU or US 4.4.4 untouched from this link: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and flash it via recovery.

XT1032 - unable to run system

MORE INFO: I would like to add that my bootloader is 41.19 and that bootloader/fastboot and recovery works ok. Only when I try to start system, it ends at BOOTLOADER UNLOCKED. I tried 4.4.4, 5.0.2 and 5.1 ... and none of them works ... And in TWRP, I can see "Unable to mount /cache" and "Unable to mount /system" ...
Hi, Ive got a problem:
Ive been using the stock DE 4.4.4. ROM + 5.0.2 OTA on my XT1032 fine for about six weeks. Today I wanted to lock it, so I
1) entered "sudo fastboot oem lock begin" (Im on Linux Mint btw)
2) flashed the DE 4.4.4 ... and the phone just doesnt boot to system; there is the WARNING BOOTLOADER UNLOCKED message and thats it.
The bootloader is still unlocked of course. And I dont think the problem is related to the locking ...
These are the commands I used (they are just from the DE 4.4.4 ROM):
Code:
sudo fastboot flash partition gpt.bin
sudo fastboot flash motoboot motoboot.img
sudo fastboot flash logo logo.bin
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash modem NON-HLOS.bin
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot flash fsg fsg.mbn
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot reboot
And this is the output
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.027s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.305s
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.365s
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.131s]
finished. total time: 0.208s
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.372s]
writing 'boot'...
OKAY [ 0.794s]
finished. total time: 1.166s
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.375s]
writing 'recovery'...
OKAY [ 0.770s]
finished. total time: 1.146s
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.639s]
sending 'system' (255397 KB)...
OKAY [ 8.085s]
writing 'system'...
OKAY [ 12.824s]
finished. total time: 21.548s
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.576s]
sending 'system' (254868 KB)...
OKAY [ 8.054s]
writing 'system'...
OKAY [ 10.562s]
finished. total time: 19.192s
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.608s]
sending 'system' (231159 KB)...
OKAY [ 7.294s]
writing 'system'...
OKAY [ 19.144s]
finished. total time: 27.046s
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.527s]
writing 'modem'...
OKAY [ 1.407s]
finished. total time: 2.934s
erasing 'modemst1'...
OKAY [ 0.065s]
finished. total time: 0.065s
erasing 'modemst2'...
OKAY [ 0.065s]
finished. total time: 0.065s
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.081s]
writing 'fsg'...
OKAY [ 5.611s]
finished. total time: 5.693s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.415s]
finished. total time: 0.415s
erasing 'userdata'...
OKAY [ 6.911s]
finished. total time: 6.911s
rebooting...
finished. total time: 0.001s
And when I try to sideload the OTA phone says "Installation aborted" ...
Im using the same files I used six weeks ago.
I tried EU 4.4.4 but it is not working either - theres only Motorola logo and thats it.
Any suggestions, please?

The gpt.bin and motoboot files won't flash because you are trying to downgrade both versions which cannot be done.
There is no need to lock the bootloader to flash stock 4.4.4 or take the OTA update.

Alright, my not-so-perfect yet-working solution.
I flashed TWRP. In the recovery (wipe-advanced-repair or format) I realized that all the partitions (system, cache, data) are corrupted and showing size zero. So I formatted all of them to ext4 and (just to be sure) ran REPAIR.
After repairing the partitions I enabled MTP - it didnt show in my PC, but reboot helped - and copied GPE 5.1 Untouched (http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510) into the storage. Then, I installed the ROM in TWRP and rebooted - dont let the recovery install SU, it ended in loopback (during first boot only: after successfully entering my google information and rebooting into recovery, I let it install SuperSU and it worked fine).
Voila, phone working again.
I checked the process once again and it worked. But when I try to flash anything now, partitions get corrupted. Weird.
audit13 said:
There is no need to lock the bootloader to flash stock 4.4.4 or take the OTA update.
Click to expand...
Click to collapse
I know, but I was going to sell the phone and I hoped relocking would make the Warning Bootloader Unlocked sign go away. Later, I read it doesnt - too bad.
But generally I'm quite satisfied now - the phone has a newer system, no Bootloader Warning, it has Czech language now and the new user is a total newbie so Im glad that (thanks to the TWRP) she wont lose her internal storage files when doing factory reset.
UPDATE: I flashed stock recovery (Brazilian 5.0.2) to make Factory reset be able to format even the /media/data partition, as was intended. Just to make sure the partition can be wiped in case of trouble. GPE 5.1 recovery didnt work btw.

sorry people, may be yo´ve heard about but if you know about the mbm-ci5 files needed to un hard brick a moto g ??? do you thing there is a hope o may be other methods to unbrick a moto g xt 1032 - sorry if its not the right place, just looking for help to revive mines...

How can i make my moto g dual sim again...

Hi this is my first request for help ever, have tired almost all roms available on xda
I never needed to touch my rom till was on kitkat, i had heard the hole world crying for bugs with kitkat but my phone never reported any major bug (i had not even rooted my phone) then came the curse LOLIPOP 5.02 there were two things that made me force to unlock bootloader 1> slow 2nd> ghost windows showing up in taskbar
from the day i flashed to stock rom kitkat 4.4.4 us retail (xt1032) availabe on xda forum i lost my second sim working
till this date i have flashed endless roms even cwm 12 and all versions of stock for asian retail have not tried flashing and brazil fimware.
it just doesn't detect if any sim is inserted.
i have tried the stock radio thread for kitkat 4.4.4 , 5.02, 5.1 none of them work.
If anyone is having moto g xt1033 indian stock rom with dual sim working
can you please send me a screen shot of about section in settings
i want to check what baseband version you guys are having
one last thing i had made a backup using cynogen recovery but on restoring the backup my moto g never boots it was of stock lolipop can anyone help in this regards..
currently am on stock lolipop 5.1
my baseband version is MSM8626BP_1032.3116.98.00R EMEA_DSDS_CUST
i think 1032 in above baseband means radio of xt1032 while i need 1033 (i guess)
i have updated using indian ota update of stock rom using stock recovery.
Issue still persists sim 2 not detected, both sims used to work before flashing any firware manually.

Simply flash the latest XT1033 Retail Asia 5.1 Factory Firmware Image.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Provide a log of the flashing process if this does not resolve your problem. Copy and paste the contents of Command Prompt. Take screen-shots if necessary.

edit: above method

new problem
i did as you said, this is first time i will be flashing 5.1 directly my system was already on 5.1 and now system is not booting did system userdata wipe and cache wipe
i flahed this file XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7 and the phone keeps stuck on bootloader logo
bootloader version is 41.1A
i can enter fastboot and am thinking of going back to 5.02 cannot enter recovery (stock)
now am flashing ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml.zip i dont think 2nd sim will work but at least working system.
still if anyone has both sims working do tell me your baseband version
thank you..
here is the log
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>

huzeifa88 said:
i did as you said, this is first time i will be flashing 5.1 directly my system was already on 5.1 and now system is not booting did system userdata wipe and cache wipe
i flahed this file XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7 and the phone keeps stuck on bootloader logo
bootloader version is 41.1A
i can enter fastboot and am thinking of going back to 5.02 cannot enter recovery (stock)
now am flashing ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml.zip i dont think 2nd sim will work but at least working system.
still if anyone has both sims working do tell me your baseband version
thank you..
here is the log
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>
Click to expand...
Click to collapse
now flashed 5.02 and it too just shows me the boot logo saying warning bootloader unlocked nothing else is happening getting a little tense now log for 5.02
C:\adb>flash.bat
C:\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.335s]
finished. total time: 0.369s
C:\adb>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.105s]
finished. total time: 1.216s
C:\adb>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.114s]
finished. total time: 0.194s
C:\adb>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.948s]
finished. total time: 1.344s
C:\adb>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.407s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.370s
C:\adb>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.216s]
sending 'system' (257755 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 15.825s]
finished. total time: 24.187s
C:\adb>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.318s]
sending 'system' (256949 KB)...
OKAY [ 8.339s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 24.692s
C:\adb>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.341s]
sending 'system' (260404 KB)...
OKAY [ 8.322s]
writing 'system'...
OKAY [ 16.104s]
finished. total time: 24.777s
C:\adb>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.317s]
sending 'system' (166184 KB)...
OKAY [ 5.299s]
writing 'system'...
OKAY [ 11.333s]
finished. total time: 16.952s
C:\adb>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49376 KB)...
OKAY [ 1.604s]
writing 'modem'...
OKAY [ 2.331s]
finished. total time: 3.937s
C:\adb>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\adb>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.069s
C:\adb>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (103 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 5.309s]
finished. total time: 5.371s
C:\adb>mfastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.117s]
finished. total time: 0.118s
C:\adb>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.577s]
finished. total time: 0.578s
C:\adb>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>

Please stop trying different Firmware Images. Only do as directed for your own safety.
Edit: Manually type commands, do not use a .bat file or script. Skip the command related to motoboot.img - repeatedly flashing the Bootloader is dangerous and completely unnecessary.
Type the following command before any other:
mfastboot oem unlock​

lost101 said:
Please stop trying different Firmware Images. Only do as directed for your own safety.
Click to expand...
Click to collapse
well i did try to flash 5.1 image twice its not working nor is the 5.02 any ideas just stays on the boot logo the simple static one not the animated one.

bootleoader version is 41.1A system is 5.02
huzeifa88 said:
well i did try to flash 5.1 image twice its not working nor is the 5.02 any ideas just stays on the boot logo the simple static one not the animated one.
Click to expand...
Click to collapse
now am on 5.02 boot loader version is same as 5.1 does it need to downgrade.

huzeifa88 said:
now am on 5.02 boot loader version is same as 5.1 does it need to downgrade.
Click to expand...
Click to collapse
Stop flashing / messing with the Bootloader. Period. You will end up with a dead phone.

Finally back from dead
I flashed kitkat stock rom without trying to downgrade boot loader as i knew it could brick my phone and just as usual phone did not boot past boot logo of boot recovery stating boot loader unlocked...
but my luck turned kitkat stock rom recovery started to work without wasting time i flashed twrp recovery over kitkat stock recovery
once twrp i flashed cm12 last stable built volla cm12 booted
now still only one sim will work but i guess i had enough experiments i had once tried the donkey kernel on cm12 it never booted. so lets forget dual sim.
please dont recommend anyone to flash 5.1 stock rom i has some bug never boots or maybe coz i already had 5.1 installed using ota method.

@huzeifa88 - You are going to destroy your phone. I have tried to help you, but you ignore what I say.
Do not flash old Firmware Images and then accept an OTA Update. Your phone will switch off and never turn on again. I have already warned you to stop trying random Firmware Images.

phone doesnt boot on 5.1 had no options
I did flash the 5.1 lolipop image but phone did not boot it would just kept stuck at bootloader spash image (White color image saying boot loader unlocked) and did not reach the motorola animated boot screen
I left it there for around 30 mins after which i was sure its not gonna boot
Again even tried deleting all data and cache using fastboot command
even the recovery would not open it would stay on the bootloader splah screen
what i am experiancing with this phone is rare and happened 1st time maybe all those who have updated their boot loader should not mess with there cell anymore
anyway all is GOOD now i am HAPPLY using CM12 ROM and am never gonna flash any stock rom again.

Allow OEM Unlock Bootloader

Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!

axbom said:
Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!
Click to expand...
Click to collapse
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.

acejavelin said:
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.
Click to expand...
Click to collapse
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!

axbom said:
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!
Click to expand...
Click to collapse
Did you factory default prior to flashing? That is a required step...

acejavelin said:
Did you factory default prior to flashing? That is a required step...
Click to expand...
Click to collapse
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..

axbom said:
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..
Click to expand...
Click to collapse
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk

acejavelin said:
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_set
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.708s]
finished. total time: 0.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.551s]
finished. total time: 1.645s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.125s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.519s]
writing 'boot'...
OKAY [ 0.936s]
finished. total time: 1.471s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 1.486s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (243355 KB)...
OKAY [ 7.717s]
writing 'system'...
OKAY [ 8.975s]
finished. total time: 16.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (233538 KB)...
OKAY [ 7.478s]
writing 'system'...
OKAY [ 7.597s]
finished. total time: 15.092s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (256922 KB)...
OKAY [ 8.213s]
writing 'system'...
OKAY [ 8.308s]
finished. total time: 16.521s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (257262 KB)...
OKAY [ 8.198s]
writing 'system'...
OKAY [ 8.303s]
finished. total time: 16.500s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (255507 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 8.575s]
finished. total time: 16.717s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (258021 KB)...
OKAY [ 8.225s]
writing 'system'...
OKAY [ 8.266s]
finished. total time: 16.507s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.6
target reported max download size of 268435456 bytes
sending 'system' (210541 KB)...
OKAY [ 6.716s]
writing 'system'...
OKAY [ 11.695s]
finished. total time: 18.410s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36984 KB)...
OKAY [ 1.165s]
writing 'modem'...
OKAY [ 0.974s]
finished. total time: 2.155s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2159 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.094s]
finished. total time: 0.172s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase customize
erasing 'customize'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>
From what I can see it all looks fine?

axbom said:
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
...
From what I can see it all looks fine?
Click to expand...
Click to collapse
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?

acejavelin said:
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?
Click to expand...
Click to collapse
After issuing the reboot command at the end it goes to the white screen with the motorola logo, then the screen goes black, and then back to the motorola logo, and keep on going like that.
Yeah that's correct, 0-6 sparsechunk files. I did fastboot ERASE cache and ERASE userdata, since I can't get into the recovery menu (goes into bootloop if I try). When I try any of those commands it says Formatting is not supported for filesystem with type 'raw'.

im having the exact same problem, used the same software and carried out the same steps as you with no luck either.
from what ive read its because you need to wipe all the data first but because we get the, cant its RAW message, it wont download the firmware onto the phone even though it says it went ok. at the minute i havnt found anyone whos successfully been able to repair this fault.
mine was working perfectly untill the ota update

There is no fix for that, use your warranty if you have so

Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.

yobac said:
Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.
Click to expand...
Click to collapse
Contact Moto directly via their website.
Sent from my MotoG3 using Tapatalk

1st Flash via Adb !
fastboot flash partition 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
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
mfastboot reboot
Post result !

FaizanChauhaan said:
1st Flash via Adb !
fastboot flash partition 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
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
mfastboot reboot
Post result !
Click to expand...
Click to collapse
It's fastboot not adb lol. Contradictory sentences
Edit: BTW motoboot.img is not present, it may refer to earlier generation of moto g. There is an line to flash bootloader.img instead. Have a look here : http://forum.xda-developers.com/showthread.php?t=3187750. Thanks.
Broadcasted from Zeta Reticuli

[GUIDE][ROM][STOCK] XT1766 Stock Firmware & Restoration Guide

Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide​
IMPORTANT NOTICE:
Because there are reports of devices becoming bricked due to downgrading, please disregard this thread and firmware. This is a link to the newly added factory firmware package for the most current build version for the xt1766 SPerry. Please go here:
https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
DISCLAIMER: Please take note that the following stock firmware package is not the official Motorola firmware package, nor is it signed by Motorola. This is a package I have compiled with partition dumps from a pure stock & unmodified Android OS. I have tested this procedure, as have other members, and no adverse issues have arisen upon installing the firmware. However, I am not responsible for devices bricked or otherwise rendered inoperable as a result of installing this firmware or using this guide. You and you alone are responsible for your device. Because this guide does involve fastboot flashing bootloader and other sensitive partitions, follow the instructions to the letter. One mishap while flashing a bootloader partition can leave a device fully inoperable. Also, I have only used this guide on Virgin Mobile variants of the xt1766. It should work on the Sprint and Boost Mobile variants as well, but I cannot personally confirm that at this time.
SPECIFICATIONS:
Hardware SKU: xt1766
Carrier/Provider: Sprint, Virgin Mobile, Boost Mobile
Android Version: 7.1.1 Nougat
Build No. NCQ26.69-64
Radio: M8920_15000.280.06.58.02R
Kernel Version: 3.18.31
Security Patch Level: January 1, 2018
NOTES: This firmware is the most recent version of the stock Android OS. It is completely unmodified.
REQUIREMENTS:
--An unlocked bootloader;
--A PC or laptop running Windows 7 or later;
--Motorola Device Manager: https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222;
--Minimal ADB & Fastboot (v1.4.3 or later): https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk;;
--Rudimentary knowledge of fastboot flashing;
--Device charged to at least 60%.
INSTRUCTIONS:
Download the stock firmware package from the link below and save the files in your ADB/Fastboot directory on your PC. Boot your device into fastboot/bootloader mode and connect your device and PC with a suitable data sync cable. Open a command window within the ADB/Fastboot directory and execute the following set of commands:
NOTE: The larger image files (system.img & oem.img) will be automatically dissected into individual sparsechunks and incrementally flashed by fastboot. You will initially receive a "header size" error, but just be patient and wait. Fastboot will resolve this and flash the images.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash aboot aboot.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash dsp dsp.img
fastboot flash modem modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.img
fastboot flash keymaster keymaster.mbn
fastboot flash oem oem.img
fastboot flash prov prov.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot erase system
fastboot flash system system.img
fastboot erase DDR
fastboot erase userdata
fastboot erase cache
fastboot oem fb_mode_clear
Now boot your device normally. You should now be updated to the most recent pure stock Android build, and your device will be fully capable of installing future OTA updates.
DOWNLOAD LINK:
LINK HAS BEEN REMOVED: Please go here: https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749

this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.

iykeDROID™ said:
this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.
Click to expand...
Click to collapse
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:

MotoJunkie01 said:
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:
Click to expand...
Click to collapse
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411

iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Thank you. I sent the thread link and a PM to Az Biker.

Update: The Sperry xt1766 received an OTA update today for minor bug fixes, stability improvements, and security patches for March 1, 2018. The OTA is Bkur_Version 26.11.68.sperry_sprint.en.US. I will be updating this thread to the new build updated by the OTA. In the meantime, should you wish to revert to pure stock and install the OTA update package, the above fastboot firmware package will put your xt1766 in a pure stock state, and thus capable of installing the OTA update. NOTE: Many people skip recovery.img in order to retain TWRP custom recovery. Here, flashing stock recovery is necessary in order to successfully install the OTA update package.

iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Hey friend, thanks again for pointing out my oversight. Moderator Az Biker helped me out and moved the thread.

Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.

MotoJunkie01 said:
Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.
Click to expand...
Click to collapse
Rock on bro! Good luck.

Hard brick
My device is bricked flashing update on custom rom AICP
Please help
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
Hard brick
My device is bricked flashing update on custom rom AICP
Please help

Restore in emergency mode
Greetings.
I would like your help to restore a MOTO E4 XT1766. It does not start with fastboot, because the bootloader is corrupt. The phone connects in emergency mode. I need the file "prog_emmc_firehose_8920.mbn" to be able to restore it. Any idea where I can find it?

error cannot load gpt.bin
I have my phone in fastboot/bootloader mode. Should I be in recovery? I can run the command "fastboot oem fb_mode_set" but I cant run the command "fastboot flash partition gpt.bin" I get "error cannot load gpt.bin". Moto E4 XT1766 Qualcomm any help?
Edit: I am sure I have the files in the same folder as adb and fastboot.

UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry bricked my phone
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.

[email protected] said:
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.
Click to expand...
Click to collapse
Nope its dead u flash bootloader partitions that were older then your current version that edl'd you're phone

MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide​
Click to expand...
Click to collapse
Thanks man, worked perfectly.
Got some errors along the way, which I ignored (permissions on Erase Data, etc).

MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
Click to expand...
Click to collapse
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike

resarfekim said:
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike
Click to expand...
Click to collapse
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.

madbat99 said:
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.
Click to expand...
Click to collapse
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968

resarfekim said:
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968
Click to expand...
Click to collapse
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.

madbat99 said:
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.
Click to expand...
Click to collapse
I was originally rooted, but after running the commands in this OP, I did nothing else.
I did save the results of all the Fastboot commands, please see below. A couple commands toward the end gave errors.
______________________________________________
E:\Phone\E4\Factory_restore_image>fastboot devices
ZY224PTXGW fastboot
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_set
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.125s]
finished. total time: 0.140s
E:\Phone\E4\Factory_restore_image>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.515s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.655s]
finished. total time: 1.186s
E:\Phone\E4\Factory_restore_image> fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 1.970s]
finished. total time: 2.517s
E:\Phone\E4\Factory_restore_image> fastboot flash aboot aboot.mbn
(bootloader) has-slot:aboot: not found
target reported max download size of 536870912 bytes
sending 'aboot' (1536 KB)...
OKAY [ 0.047s]
writing 'aboot'...
OKAY [ 0.203s]
finished. total time: 0.265s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib cmnlib.mbn
(bootloader) has-slot:cmnlib: not found
target reported max download size of 536870912 bytes
sending 'cmnlib' (251 KB)...
OKAY [ 0.001s]
writing 'cmnlib'...
OKAY [ 0.078s]
finished. total time: 0.079s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib64 cmnlib64.mbn
(bootloader) has-slot:cmnlib64: not found
target reported max download size of 536870912 bytes
sending 'cmnlib64' (251 KB)...
OKAY [ 0.016s]
writing 'cmnlib64'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash devcfg devcfg.mbn
(bootloader) has-slot:devcfg: not found
target reported max download size of 536870912 bytes
sending 'devcfg' (128 KB)...
OKAY [ 0.016s]
writing 'devcfg'...
OKAY [ 0.062s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image> fastboot flash dsp dsp.img
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.531s]
writing 'dsp'...
OKAY [ 1.686s]
finished. total time: 2.217s
E:\Phone\E4\Factory_restore_image>fastboot flash modem modem.img
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (102400 KB)...
OKAY [ 3.247s]
writing 'modem'...
OKAY [ 4.921s]
finished. total time: 8.168s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image> fastboot flash fsg fsg.img
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (8192 KB)...
OKAY [ 0.266s]
writing 'fsg'...
OKAY [ 2.795s]
finished. total time: 3.062s
E:\Phone\E4\Factory_restore_image>fastboot flash keymaster keymaster.mbn
(bootloader) has-slot:keymaster: not found
target reported max download size of 536870912 bytes
sending 'keymaster' (251 KB)...
OKAY [ 0.016s]
writing 'keymaster'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash oem oem.img
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'oem' 1/2 (507490 KB)...
OKAY [ 17.457s]
writing 'oem' 1/2...
OKAY [ 28.001s]
sending sparse 'oem' 2/2 (59511 KB)...
OKAY [ 2.081s]
writing 'oem' 2/2...
OKAY [ 6.231s]
finished. total time: 53.804s
E:\Phone\E4\Factory_restore_image> fastboot flash prov prov.mbn
(bootloader) has-slotrov: not found
target reported max download size of 536870912 bytes
sending 'prov' (187 KB)...
OKAY [ 0.016s]
writing 'prov'...
OKAY [ 0.062s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image>fastboot flash rpm rpm.mbn
(bootloader) has-slot:rpm: not found
target reported max download size of 536870912 bytes
sending 'rpm' (256 KB)...
OKAY [ 0.016s]
writing 'rpm'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash sbl1 sbl1.mbn
(bootloader) has-slot:sbl1: not found
target reported max download size of 536870912 bytes
sending 'sbl1' (507 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.047s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image> fastboot flash tz tz.mbn
(bootloader) has-slot:tz: not found
target reported max download size of 536870912 bytes
sending 'tz' (1792 KB)...
OKAY [ 0.062s]
writing 'tz'...
OKAY [ 0.265s]
finished. total time: 0.328s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image> fastboot flash system system.img
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/5 (509553 KB)...
OKAY [ 17.319s]
writing 'system' 1/5...
OKAY [ 12.350s]
sending sparse 'system' 2/5 (523636 KB)...
OKAY [ 17.753s]
writing 'system' 2/5...
OKAY [ 11.928s]
sending sparse 'system' 3/5 (519086 KB)...
OKAY [ 17.869s]
writing 'system' 3/5...
OKAY [ 11.983s]
sending sparse 'system' 4/5 (521399 KB)...
OKAY [ 17.949s]
writing 'system' 4/5...
OKAY [ 20.356s]
sending sparse 'system' 5/5 (411602 KB)...
OKAY [ 14.302s]
writing 'system' 5/5...
OKAY [ 35.077s]
finished. total time: 176.895s
E:\Phone\E4\Factory_restore_image> fastboot erase DDR
(bootloader) has-slotDR: not found
erasing 'DDR'...
OKAY [ 0.000s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 1.267s]
finished. total time: 1.267s
E:\Phone\E4\Factory_restore_image>fastboot erase cache
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_clear
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>