Database Info

beeginer Moto G Bootup Problem it does not start

ok well basically i installed the Lollipop 5.02 version it worked ok except that was slower than before one night the cell run out of battery and it was shutdown and while it was doing that an incoming call was trying to get in, after that it finally shutdown, i charge the cellphone like 30 minutes and when i turn it on, it onlu give me the motorola logo screen after that a black screen
so my main concern is that i wan to recover myu photos back i did not save them in any place because i turn off the photos app to automatically save them
please help me
i have a moto g XT1032 16gb
i have ran the erase cache and i flashed a ROM but still does not let me in
and i have the bootloader block
any help is greatly appreciated
thank you:good:

helppp
gabriel32mty said:
ok well basically i installed the Lollipop 5.02 version it worked ok except that was slower than before one night the cell run out of battery and it was shutdown and while it was doing that an incoming call was trying to get in, after that it finally shutdown, i charge the cellphone like 30 minutes and when i turn it on, it onlu give me the motorola logo screen after that a black screen
so my main concern is that i wan to recover myu photos back i did not save them in any place because i turn off the photos app to automatically save them
please help me
i have a moto g XT1032 16gb
i have ran the erase cache and i flashed a ROM but still does not let me in
and i have the bootloader block
any help is greatly appreciated
thank you:good:
Click to expand...
Click to collapse
Please helppppp

gabriel32mty said:
Please helppppp
Click to expand...
Click to collapse
somebody please help!!!

Hi,
How do you flashed a rom?

1.Is your boot logo unlocked? or not?
2.try a hard formate via recovery or ADB
3.try flashing stable rom
4.post pics to clear the doubts

satanas17 said:
Hi,
How do you flashed a rom?
Click to expand...
Click to collapse
I flash it thru the computer i plug my cellphone to the computer and then i use the command c: window
like this
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot getvar cid
cid: 0x000C
finished. total time: 0.109s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.047s]
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.312s]
finished. total time: 0.359s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot flash motoboot motoboot
.img
target max-sparse-size: 256MB
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 [ 0.954s]
finished. total time: 1.063s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.078s]
writing 'logo'...
OKAY [ 0.031s]
finished. total time: 0.109s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.468s]
writing 'boot'...
OKAY [ 0.608s]
finished. total time: 1.076s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot flash recovery recovery
.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.452s]
writing 'recovery'...
OKAY [ 0.608s]
finished. total time: 1.061s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot flash system system.img
_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 10.312s]
writing 'system'...
OKAY [ 8.314s]
finished. total time: 18.625s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot flash system system.img
_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256762 KB)...
OKAY [ 10.265s]
writing 'system'...
OKAY [ 8.397s]
finished. total time: 18.662s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot flash system system.img
_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260121 KB)...
OKAY [ 10.359s]
writing 'system'...
OKAY [ 8.470s]
finished. total time: 18.844s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot flash system system.img
_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (159384 KB)...
OKAY [ 6.376s]
writing 'system'...
OKAY [ 6.558s]
finished. total time: 12.934s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot flash modem NON-HLOS.bi
n
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 2.002s]
writing 'modem'...
OKAY [ 0.832s]
finished. total time: 2.849s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.094s]
writing 'fsg'...
OKAY [ 3.193s]
finished. total time: 3.287s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Gaby\Downloads\ADB-Fastboot-mFastboot>mfastboot reboot
rebooting...
finished. total time: 0.000s
but still the same problem what else can i do???
my main concern is about the pictures i did not backup in the google photos app i want to recover that

Scronix said:
1.Is your boot logo unlocked? or not?
2.try a hard formate via recovery or ADB
3.try flashing stable rom
4.post pics to clear the doubts
Click to expand...
Click to collapse
1.- at the moment my bootloader is locked that i guess it will be my next move
2- when i tried to open the recovery the phone says "boot up failed"
3.- what do you mean stable rom?? i tried two roms for the cid 12 already and still the same issue
4.- i will
share your thoughts please
@lost101 @Scronix

@gabriel32mty - Double check that you flashing all included 'sparsechunks' files in the folder. If you still have problems; try one of the XT1032 5.1 Factory Firmware Images available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

lost101 said:
@gabriel32mty - Double check that you flashing all included 'sparsechunks' files in the folder. If you still have problems; try one of the XT1032 5.1 Factory Firmware Images available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
hi lost101
yes i did flash without doing the step delete data user but all other steps were performed as you can see up in this threat i paste what i did :good:
i use this
XT1032_FALCON-TELCEL-MX_5.0.2_LXB22.46-32_31_cid12_CFC_1FF.xml.zip
@lost101 im going to try with one of the 5.1 to see what happens but which you recommend me to use since im form mexico and my carrier is Telcel
?????????????????
thank you for your help

gabriel32mty said:
1.- at the moment my bootloader is locked that i guess it will be my next move
2- when i tried to open the recovery the phone says "boot up failed"
3.- what do you mean stable rom?? i tried two roms for the cid 12 already and still the same issue
4.- i will
share your thoughts please
@lost101 @Scronix
Click to expand...
Click to collapse
Use fastboot and flash a stock firmware or use a custom rom good enough to keep ur phone eg my personal usage nexus experience rom

you can access your phones internal storage with a custom recovery and flash roms easily

Scronix said:
Use fastboot and flash a stock firmware or use a custom rom good enough to keep ur phone eg my personal usage nexus experience rom
Click to expand...
Click to collapse
im going to try a 5.1 Rom to see if works
but im not sure which ROm to use that fits better with my phone i had 5.02

gabriel32mty said:
im going to try a 5.1 Rom to see if works
but im not sure which ROm to use that fits better with my phone i had 5.02
Click to expand...
Click to collapse
Try The latest Nexus experience rom 9.8.2 its made on 5.1 bootloader as base

Scronix said:
Try The latest Nexus experience rom 9.8.2 its made on 5.1 bootloader as base
Click to expand...
Click to collapse
huh?? but i dont have a Nexus i have Moto G XT1032

gabriel32mty said:
huh?? but i dont have a Nexus i have Moto G XT1032
Click to expand...
Click to collapse
BRo its a Custom Rom Available for Moto G (gen 1 & 2),Moto X (gen 1 & 2),nexus 4,5,6

gabriel32mty said:
im going to try a 5.1 Rom to see if works
but im not sure which ROm to use that fits better with my phone i had 5.02
Click to expand...
Click to collapse
I'm using BlissPop on my Peregrine XT1039 and my son use the same on his Condor XT1022... We are both happy users... I'm using also the Dt2w version of the Optimus kernel (Optimus Prime), port of the original version for Falcon, happy user too...

Soft Brick with Locked Booloader in Moto g3 XT1550 (Dual-SIM)

Deal all Great and Senior Devs specially @lost101 need yours extrem help
i was on rr rom 5.1 and later after that i have flash Stock Factory Firmware Image of same model via Fastboot
i was successfully booted and also received the MM update so i had downloaded it and install it after final step to reboot i was stuck on unlock boot loader warring image so after seeing many threads i have flashed Stock MM Factory Firmware Image of same model via Fastboot as i wanted to sell this phone so i have tried to relock the boot loader so i have tried
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 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
all the commands was showing okay while flashing
also boot loader got locked on final fastboot reboot i stuck on boot loop :crying:
and now I can only get into Fastboot mode .but I can't flash anything because the bootloader is locked. and I can't unlock the bootloader because I can't toggle the stupid "Allow OEM Unlock" setting.
please don't tell to visit service center its boot loop image showing unlock boot loader warning
pls help all great devs if their is any solution
thanks in advace

Stop with all locking. You cannot undo Bootloader unlock, period. Do not use any lock commands. Begin again, this time with: fastboot oem unlock
It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.

thanks @lost101 for the reply sir
but as in locked boot loader status code 2
all comments were flashing successfully but in the end on final reboot its stuck on boot loader warning logo again screen goes off again boot loader warning logo comes this process repeats
also i am not able to boot into stock recovery which agains open boot loader
following are the commands
C:\Users\Bhupesh\Desktop\Moto>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.733s]
finished. total time: 0.749s
C:\Users\Bhupesh\Desktop\Moto>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.624s]
finished. total time: 1.718s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.156s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.562s]
writing 'boot'...
OKAY [ 0.938s]
finished. total time: 1.500s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 1.515s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262142 KB)...
OKAY [ 8.713s]
writing 'system'...
OKAY [ 11.861s]
finished. total time: 20.574s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (245933 KB)...
OKAY [ 8.190s]
writing 'system'...
OKAY [ 7.958s]
finished. total time: 16.164s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (249279 KB)...
OKAY [ 8.300s]
writing 'system'...
OKAY [ 7.769s]
finished. total time: 16.069s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (262142 KB)...
OKAY [ 8.726s]
writing 'system'...
OKAY [ 9.734s]
finished. total time: 18.461s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (63875 KB)...
OKAY [ 2.150s]
writing 'system'...
OKAY [ 11.283s]
finished. total time: 13.436s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36984 KB)...
OKAY [ 1.237s]
writing 'modem'...
OKAY [ 1.056s]
finished. total time: 2.298s
C:\Users\Bhupesh\Desktop\Moto>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Users\Bhupesh\Desktop\Moto>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.010s]
finished. total time: 0.020s
C:\Users\Bhupesh\Desktop\Moto>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\Bhupesh\Desktop\Moto>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Users\Bhupesh\Desktop\Moto>fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.973s]
finished. total time: 3.976s
C:\Users\Bhupesh\Desktop\Moto>fastboot reboot
rebooting...
finished. total time: 0.008s
C:\Users\Bhupesh\Desktop\Moto>
also while
C:\Users\Bhupesh\Desktop\Moto>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.017s
thanks in advance

This is one of the reasons why it's important to unlock Bootloader. You are totally stuck as far as I can see. You have no choice but phone to return to Manufacturer.
EDIT: One possibility might be to flash the 5.1.1 Firmware (skipping bootloader.img) and if that does not boot to Android, then apply the MM OTA Update via Stock Recovery.

lost101 said:
This is one of the reasons why it's important to unlock Bootloader. You are totally stuck as far as I can see. You have no choice but phone to return to Manufacturer.
EDIT: One possibility might be to flash the 5.1.1 Firmware (skipping bootloader.img) and if that does not boot to Android, then apply the MM OTA Update via Stock Recovery.
Click to expand...
Click to collapse
thanks @lost101 for the reply again
its seems I am getting the failure message
"version downgrade for system"
"Invalid PIV signed system image "
C:\Users\Bhupesh\Desktop\Moto>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.421s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.156s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.281s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.702s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.357s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.718s]
writing 'recovery'...
OKAY [ 1.030s]
finished. total time: 1.763s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (232264 KB)...
OKAY [ 7.769s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.424s
C:\Users\Bhupesh\Desktop\Moto>
also while using MM Factory Firmware Images before which was getting successfully flashed i was still not able to boot on stcok recovery with boot loop
i have done almost googleing abt this issue
and i bet u are the only who can make my device normal
thanks in advance

Try using RSD lite as described here by @thinkfreedom:
http://forum.xda-developers.com/showpost.php?p=64844324&postcount=275​

Not i my case waited for 20-30 minute
Dear @lost101 pls help
Not i my case
I followed each steps All file were getting flash ok
Finally waiting for 20-30 minute the screen is still on off then stiching to boot loader repeating no change :crying:
please help @lost101

I'm having a similar problem, locked bootloader on bell Canada lollipop, tried to Flash US. Retail marshmallow, worked up until boot.Img now I'm stuck in fastboot and if I try to boot into recovery it just loops,can't flash twrp. . Can't unlock bootloader because of OEM Uncheck in developer option is not checked! No official marshmallow for bell yet..... Do you think MM 6.0 will flash when available?

tmmcbots said:
I'm having a similar problem, locked bootloader on bell Canada lollipop, tried to Flash US. Retail marshmallow, worked up until boot.Img now I'm stuck in fastboot and if I try to boot into recovery it just loops,can't flash twrp. . Can't unlock bootloader because of OEM Uncheck in developer option is not checked! No official marshmallow for bell yet..... Do you think MM 6.0 will flash when available?
Click to expand...
Click to collapse
yes i can via RSD Lite 6.2.4 try https://getmovil.com/motorola/moto-g-2015-android-5-1-1-lollipop/
hope u get booted

bhu999 said:
Dear @lost101 pls help
Not i my case
I followed each steps All file were getting flash ok
Finally waiting for 20-30 minute the screen is still on off then stiching to boot loader repeating no change :crying:
please help @lost101
Click to expand...
Click to collapse
Try flashing TWRP and than any custom rom i think CM13 will be better....U have tried so much so at least u can have shoot on this step...
Sent from my Toilet using Moto G3....

cant flash twrp with locked boot loader
its says Invalid partion size

bhu999 said:
cant flash twrp with locked boot loader
its says Invalid partion size
Click to expand...
Click to collapse
If you are in warranty just go to service center.. They will flash firmware.. Don't tell them you have previously unlocked boatloader.. They are just mad.. They even won't ask for money if you are in warranty period.. These guys are not aware of bootloader is previously unlocked or not.. That's the last option..
Sent from my Moto G(Osprey)

Moto G - boot loop issue - XT1033

Dear Members,
My friend owns a Moto G XT1033 (dual sim Indian version) and recently had the software go wrong. Now the phone boots - shows boot unlocked warning, booting animation. After the MOTO symbol, all that we get is a blank screen.
Now, things that I tried to recover the phone is as follows -
1. Booted into recovery menu - tried accessing the RECOVERY option. I get a NO COMMAND error (with the android lying down on his back)
2. Tried flashing custom recovery (both TWRP and CWM) - using fastboot option - I get "MISMATCHED PARTITION SIZE" error. I ignored that error (as read somewhere in this forum), I still get "NO COMMAND" while accessing the RECOVERY option
3. Tried to sideload stock 4.4.4 version using adb - the system pushes the rom to the phone successfully, but in couple of minutes I get "installation aborted" error.
I've done all I could with the help of other threads with no success. I would request your help to recover the phone. Apologies if I have started another duplicate thread on this issue. Please help. Thanks in advance.
AP Fastboot Flash Mode (S)
41.13 (sha07dc8e78, 2014-06-16 16:33:29)
CPU: MSM8226 CS
eMMC: 16GB Sandisk RV=06 PV=07 TY=17
DRAM: 1024MB Elpida S4 SDRAM DIE=4GB
Battery OK
Device is UNLOCKED. Status Code: 3
Connect USB data Cable

Flash the latest XT1033 Factory Firmware Image using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
Flash the latest XT1033 Factory Firmware Image using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Thanks for your reply and your time!
However, please find the error message and flash log below.
My image file - XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.025s]
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.359s]
finished. total time: 0.388s
mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.116s]
finished. total time: 1.216s
mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.055s]
writing 'logo'...
OKAY [ 0.037s]
finished. total time: 0.097s
mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.394s]
writing 'boot'...
OKAY [ 0.654s]
finished. total time: 1.053s
mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.403s]
writing 'recovery'...
OKAY [ 0.659s]
finished. total time: 1.068s
mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk1': No error
mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk2': No error
Please help further.

billa vimal said:
mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk1': No error
mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk2': No error
Please help further.
Click to expand...
Click to collapse
Use the file names that actually exist on your computer - there may be dots in the name or some other minor differences. And if chunk 0 exists, start with that one.

_that said:
Use the file names that actually exist on your computer - there may be dots in the name or some other minor differences. And if chunk 0 exists, start with that one.
Click to expand...
Click to collapse
Thanks for highlighting that! I actually went by the steps listed in the tutorial and didnt notice the chunk.0! I have now followed every other step - but still the problem exists! I have attached the screenshot of the rom contents. And also the flash logs. Please let me know if I'm missing anything here.
Thanks for your time!
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
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.359s]
finished. total time: 0.375s
mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.109s]
finished. total time: 1.219s
mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.391s]
writing 'boot'...
OKAY [ 0.656s]
finished. total time: 1.047s
mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.391s]
writing 'recovery'...
OKAY [ 0.656s]
finished. total time: 1.047s
mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 9.031s]
writing 'system'...
OKAY [ 8.064s]
finished. total time: 17.110s
mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256949 KB)...
OKAY [ 8.994s]
writing 'system'...
OKAY [ 8.234s]
finished. total time: 17.229s
mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260404 KB)...
OKAY [ 9.139s]
writing 'system'...
OKAY [ 8.235s]
finished. total time: 17.375s
mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166184 KB)...
OKAY [ 5.859s]
writing 'system'...
OKAY [ 6.453s]
finished. total time: 12.328s
mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 1.766s]
writing 'modem'...
OKAY [ 0.844s]
finished. total time: 2.609s
mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ -0.000s]
finished. total time: -0.000s
mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 3.188s]
finished. total time: 3.266s
mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s

Appreciate if someone can help rescue the phone. Thanks.

Dear friends, I am bumping this thread as I am still having the phone as a brick. Thanks to anyone who volunteer to help.

xt1039, mfastboot error, can't reboot, bootloop 41.1A

Hello
I really hopes one of you brilliand guys can help me. I'm at a loss (sorry in advance for bad english).
I have a xt1039 with an unlocked BL 41.1A which I can't get back to stock or flash any other ROM.
In mfastboot, my phone is recognized as TA4750I1SK, and the device is UNLOCKED and my CID is 7.
I tried flashing different stock version from here
https://firmware.center/firmware/Motorola/Moto%20G%20%281st%20gen-2013%29/Stock/XT1039/"]https://firmware.center/firmware/Motorola/Moto%20G%20%281st%20gen-2013%29/Stock/XT1039/
trying both 4.4.4 and 5.1 but without success:
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.090s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.430s
(version downgraded for primary gpt)
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.170s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.020s]
finished. total time: 1.200s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.100s]
writing 'logo'...
OKAY [ 0.090s]
finished. total time: 0.190s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.520s]
writing 'boot'...
OKAY [ 0.810s]
finished. total time: 1.330s
(This sometimes fails as well, preflash validation, and on mobile says "version downgraded for boot")
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash recovery recovery.i
mg
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.810s]
finished. total time: 1.330s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257451 KB)...
OKAY [ 10.715s]
writing 'system'...
OKAY [ 13.060s]
finished. total time: 23.776s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257661 KB)...
OKAY [ 10.383s]
writing 'system'...
OKAY [ 12.192s]
finished. total time: 22.580s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (261552 KB)...
OKAY [ 10.710s]
writing 'system'...
OKAY [ 17.881s]
finished. total time: 28.606s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (60232 KB)...
OKAY [ 2.527s]
writing 'modem'...
OKAY [ 2.090s]
finished. total time: 4.627s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.030s]
finished. total time: 0.030s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.064s]
finished. total time: 0.066s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (517 KB)...
OKAY [ 0.080s]
writing 'fsg'...
OKAY [ 5.272s]
finished. total time: 5.362s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.140s]
finished. total time: 0.140s
C:\Users\Zhe Wang\Downloads\mfastboot-v2>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.440s]
finished. total time: 0.440s
I managed to flash twrp, but the phone will hang on Bootloader logo when rebooting, and I don't know what to do next.
Any good ideas?

visit here https://forum.xda-developers.com/showthread.php?t=2317790
and download version 1.4.2
then visit this https://forum.xda-developers.com/attachment.php?attachmentid=3476163&d=1442444179 (direct download link for mfastboot)
now copy mfastboot.exe to adb folder (created from version 1.4.2 .exe)
and try to install 5.1 lollipop stock rom with mfastboot commands thats it everything will works fine
dont download adb file from google website always use version 1.4.2
enjoy

Thank you for your reply. That made no difference. Same error messages. Also when I reboot in the end, it still shows unlocked bootloader message, continues straight to periodically blinking the "no command" and then just hangs.
I tried to flash XT1039_PEREGRINE_RETEU_5.1_LPB23.13-17_cid7_CFC.xml.
Also, when I go to twrp and try to make a wipe, it shows 'unable to mount /data' and 'unable to mount internal storage'.
Any new ideas?
SunilSuni said:
visit here https://forum.xda-developers.com/showthread.php?t=2317790
and download version 1.4.2
then visit this https://forum.xda-developers.com/attachment.php?attachmentid=3476163&d=1442444179 (direct download link for mfastboot)
now copy mfastboot.exe to adb folder (created from version 1.4.2 .exe)
and try to install 5.1 lollipop stock rom with mfastboot commands thats it everything will works fine
dont download adb file from google website always use version 1.4.2
enjoy
Click to expand...
Click to collapse

Powerleech said:
Hello
I really hopes one of you brilliand guys can help me. I'm at a loss (sorry in advance for bad english).
I have a xt1039 with an unlocked BL 41.1A which I can't get back to stock or flash any other ROM.
In mfastboot, my phone is recognized as TA4750I1SK, and the device is UNLOCKED and my CID is 7.
I tried flashing different stock version from here
https://firmware.center/firmware/Motorola/Moto%20G%20%281st%20gen-2013%29/Stock/XT1039/"]https://firmware.center/firmware/Motorola/Moto%20G%20%281st%20gen-2013%29/Stock/XT1039/
trying both 4.4.4 and 5.1 but without success:
I managed to flash twrp, but the phone will hang on Bootloader logo when rebooting, and I don't know what to do next.
Any good ideas?
Click to expand...
Click to collapse
Flashing twrp 3.1 or high in bootloader .
Wipe "system" "data" and "cache" in twrp .
Dont flash "partition" and "motoboot" when you flashing stock firmware .

[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>