Database Info

[Q] question about a brick problem with motorola moto g (2013)

hello guys from XDA, my problem is this, I have a moto motorola g (2013) I install the GPE version moto g OTA update kk 4.4.4, using mototool (no problems for months), one day I was charging my Motog, this is reset and stayed at motorola logo.
I tried to repair it with mototool but the result did not work, then I try to do it manually with fastboot since the following result:
Code:
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 9.947s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 15.259s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 6.557s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.569s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (717 KB)...
OKAY [ 5.042s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.059s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.011s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.023s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (70 KB)...
OKAY [ 5.050s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.087s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 5.370s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.880s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 5.364s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.875s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash system system.img_sparsechunk
.0
target reported max download size of 536870912 bytes
sending 'system' (255843 KB)...
OKAY [ 13.505s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 22.446s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash system system.img_sparsechunk
.1
target reported max download size of 536870912 bytes
sending 'system' (245954 KB)...
OKAY [ 13.127s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.419s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot flash system system.img_sparsechunk
.2
target reported max download size of 536870912 bytes
sending 'system' (235703 KB)...
OKAY [ 12.817s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 24.524s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.038s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.039s
C:\Users\LilDoggy\Desktop\GPRfix444>fastboot reboot
the room used was a GPE 4.4.4, then try with a stock version, and it did not work.
the result is always this:
Code:
C:\Users\LilDoggy\Desktop\gpt_new>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 9.947s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 15.259s
after dealing with the CM11, but when trying to install CWM recovery, I have the following error:
Code:
C:\Users\LilDoggy\Desktop\CWM>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 5.364s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.875s
I have tried everything I found on the internet about this but nothing.
any suggestions, please help.
and sorry for my poor English !!

LilDoggy said:
hello guys from XDA, my problem is this, I have a moto motorola g (2013) I install the GPE version moto g OTA update kk 4.4.4, using mototool (no problems for months), one day I was charging my Motog, this is reset and stayed at motorola logo.
I tried to repair it with mototool but the result did not work, then I try to do it manually with fastboot since the following result:
Click to expand...
Click to collapse
Questions goes HERE

try these two links. You can first download Stock ROM specific to your model number . Procedure remains the same .
http://forum.xda-developers.com/showthread.php?t=2739919
http://forum.xda-developers.com/moto-g/general/xt1033-t2821556
after that you can update to 4.4.4
GPE and Stock ROM has different file formats.

trying
aayush_neov said:
try these two links. You can first download Stock ROM specific to your model number . Procedure remains the same .
http://forum.xda-developers.com/showthread.php?t=2739919
http://forum.xda-developers.com/moto-g/general/xt1033-t2821556
after that you can update to 4.4.4
GPE and Stock ROM has different file formats.
Click to expand...
Click to collapse
ok, I'll try, although I tried other stock and GPE, even that hope dies at last, I will try these links

sorry for this start a new topic
Ja_som said:
Questions goes HERE
Click to expand...
Click to collapse
sorry for this start a new topic as well, only with many buttons and forums, I did not know where to express my question. Thank you

I forget to mention that my Motog is xt1032 16 gbs
aayush_neov said:
try these two links. You can first download Stock ROM specific to your model number . Procedure remains the same .
http://forum.xda-developers.com/showthread.php?t=2739919
http://forum.xda-developers.com/moto-g/general/xt1033-t2821556
after that you can update to 4.4.4
GPE and Stock ROM has different file formats.
Click to expand...
Click to collapse
I forget to mention that my Motog is xt1032 16 gbs, I do not think this room to work on my Motog, although some commands come I have never used the first line.
thank you!!

LilDoggy said:
I forget to mention that my Motog is xt1032 16 gbs, I do not think this room to work on my Motog, although some commands come I have never used the first line.
thank you!!
Click to expand...
Click to collapse
Did you unlock the bootloader?

Yes of course
skyguy126 said:
Did you unlock the bootloader?
Click to expand...
Click to collapse
Yes of course, I had already installed the rom stock version to rom GPE. My version of bootloader is 41.13

I have already written, download your phone specific firmware. from elsewhere on Motog G forums
You dont have to do anything just follow instructions properly and copy paste the code.
You took risk of installing GPE on your phone and afraid of these simple instructions !!

partition gpt.bin
aayush_neov said:
I have already written, download your phone specific firmware. from elsewhere on Motog G forums
You dont have to do anything just follow instructions properly and copy paste the code.
You took risk of installing GPE on your phone and afraid of these simple instructions !!
Click to expand...
Click to collapse
I have already tried but the result is always the same as they drew the "fastboot flash partition gpt.bin" command,
the result is always:
sending 'partition' (32 KB) ...
OKAY [9.947s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. Total time: 15.259s.
KK this with 4.4.4 versions with versions older than 4.4.4 (eg 4.4.3) sends a partition error.
from what I read it is a common problem and is solved by downloading a new gpt.bin file but does not work in my case, I begin to think that the problem is my Motog.

LilDoggy said:
I have already tried but the result is always the same as they drew the "fastboot flash partition gpt.bin" command,
the result is always:
sending 'partition' (32 KB) ...
OKAY [9.947s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. Total time: 15.259s.
KK this with 4.4.4 versions with versions older than 4.4.4 (eg 4.4.3) sends a partition error.
from what I read it is a common problem and is solved by downloading a new gpt.bin file but does not work in my case, I begin to think that the problem is my Motog.
Click to expand...
Click to collapse
Then you should search extensively on XDA, other members might be able to help you.

Try using mfastboot, available in this zip:
https://www.androidfilehost.com/?fid=23578570567719065​

Preflash validation failed trying to flash stock 4.4.4

I have a bootloader unlocked XT1032 MOTO G on UK EE network. I have been trying to flash stock 4.4.4 (so that I can upgrade to OTA lollipop) but am getting a 'Preflash validation failed error'.
I've tried various things to get it to flash the images but nothing has worked.
Can anyone suggest how I might get this work?
Code:
C:\motog>mfastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 1.660s]
finished. total time: 1.660s
C:\motog>mfastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 1.646s]
finished. total time: 1.647s
C:\motog>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.374s

Just skip flashing the gpt.bin and motoboot.img but flash the rest. The phone should still work.

audit13 said:
Just skip flashing the gpt.bin and motoboot.img but flash the rest. The phone should still work.
Click to expand...
Click to collapse
Thanks for the suggestion, however there's others that fail too:
boot.img won't flash
Recovery does flash but I get the broken android with 'No command' message when trying to boot to recovery
System images won't flash
Code:
C:\motog>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.372s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.840s
C:\motog>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.372s]
writing 'recovery'...
OKAY [ 0.966s]
finished. total time: 1.645s
C:\motog>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259277 KB)...
OKAY [ 8.643s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.082s
It will still boot normally after that. Any ideas?

Crazy question but are you sure you are flashing the correct rom for your phone? Was it on gpe before?

audit13 said:
Crazy question but are you sure you are flashing the correct rom for your phone? Was it on gpe before?
Click to expand...
Click to collapse
I'm pretty sure I am. I did try and convert to GPE using the AIO tool (when trying to resolve the issues) but I've seen nothing to suggest this has actually worked.
The phone has previously been rooted, but isn't currently.
System version is showing as:
210.12.40.falcon_umts.EESL.en.GB
Build number:
KXB21.14-L1.40
Kernel version:
3.4.42-gb89c9dd
[email protected] #1
Fri Jun 20 07:09:11 CDT 2014
Thanks for the help, it's very much appreciated!

@audit13
Update for lollipop in moto G Don´t work, ota Says "Updated"
HELP..
Same problem here preflash validation failed for Logo, GPT and Motoboot
(Downgrade from Lollipop 5.1 (XD1039 RETBR) To Kitkat 4.4.4
BOOOTLOADER is Unlocked.

Please help!! phone doesn't boot up

hey guys,
I used a youtube video and I did a thing with 5.x to 4.4.4 gpe but after my phone just doesn't boot up.
Do I have a bricked phone? It's Stuck at the bootloader menu with the error ''Boot up failed'' please help!!!
(sorry for bad english)

Be careful with downgrading. What model Moto G do you have?

lost101 said:
Be careful with downgrading. What model Moto G do you have?
Click to expand...
Click to collapse
I have moto g 4g version the 1st gen
and I think it didn't was a downgrade. my phone was 4.4.4 kitkat. it was really dumb of me to do this

poolta321 said:
I have moto g 4g version the 1st gen
and I think it didn't was a downgrade. my phone was 4.4.4 kitkat. it was really dumb of me to do this
Click to expand...
Click to collapse
I already tried to flash TWRP, CWM and Philz but it didn't work it still said Boot up failed

poolta321 said:
I have moto g 4g version the 1st gen
and I think it didn't was a downgrade. my phone was 4.4.4 kitkat. it was really dumb of me to do this
Click to expand...
Click to collapse
The safest thing would be to flash a custom recovery and then a ROM zip.
TWRP custom Recovery: https://www.androidfilehost.com/?fid=95916177934553450
Stock KitKat ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Stock Lollipop ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
--
To flash TWRP use the fastboot command: fastboot flash recovery twrp-2.8.6.0-falcon.img
You can then use ADB to transfer or sideload a ROM zip to phone for flashing.
Related tutorial: http://forum.xda-developers.com/moto-g/general/twrp-adb-sideloading-tutorial-t3006563
EDIT: Since you just updated the post to state you have a 4G Moto G - do not flash non-4G ROMs or firmware images - that includes GPE!

lost101 said:
The safest thing would be to flash a custom recovery and then a ROM zip.
TWRP custom Recovery: https://www.androidfilehost.com/?fid=95916177934553450
Stock KitKat ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Stock Lollipop ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
--
To flash TWRP use the fastboot command: fastboot flash recovery twrp-2.8.6.0-falcon.img
You can then use ADB to transfer or sideload a ROM zip to phone for flashing.
Related tutorial: http://forum.xda-developers.com/moto-g/general/twrp-adb-sideloading-tutorial-t3006563
Click to expand...
Click to collapse
Already tried to flash TWRP but still says Boot up failed when I go to recovery.
(my phone has a SD card slot)

poolta321 said:
Already tried to flash TWRP but still says Boot up failed when I go to recovery.
(my phone has a SD card slot)
Click to expand...
Click to collapse
You should only be flashing ROMs / Firmware / Recoveries available here: http://forum.xda-developers.com/moto-g/4g-development

lost101 said:
You should only be flashing ROMs / Firmware / Recoveries available here: http://forum.xda-developers.com/moto-g/4g-development
Click to expand...
Click to collapse
yes I know but when I flash TWRP and I go to recovery it says boot up failed

poolta321 said:
yes I know but when I flash TWRP and I go to recovery it says boot up failed
Click to expand...
Click to collapse
I'm going to assume you have flashed the XT1032 partition table (gpt.bin) - that could be the cause.
If you flash the full Factory Firmware image, that should fix everything.
4G Firmare images: http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
I'm going to assume you have flashed the XT1032 partition table (gpt.bin) - that could be the cause.
If you flash the full Factory Firmware image, that should fix everything.
4G Firmare images: http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Tried the 4G tutorial before... it didn't work

poolta321 said:
Tried the 4G tutorial before... it didn't work
Click to expand...
Click to collapse
but im going to try this again.
what is the difference with retial europe and orange europe?

poolta321 said:
but im going to try this again.
what is the difference with retial europe and orange europe?
Click to expand...
Click to collapse
I'm also being helped here http://forum.xda-developers.com/moto-g/help/stuck-boot-failed-t3104617

poolta321 said:
but im going to try this again.
what is the difference with retial europe and orange europe?
Click to expand...
Click to collapse
Orange version is one created for the network / carrier called Orange.
Do the fastboot commands manually, one at a time, and post a complete log here if the process is not successful.

lost101 said:
Orange version is one created for the network / carrier called Orange.
Do the fastboot commands manually, one at a time, and post a complete log here if the process is not successful.
Click to expand...
Click to collapse
Okay I'm gonna do that. but first I need to download the file and it says that it takes 2 hours to finish
(Slow internet connection)

poolta321 said:
Okay I'm gonna do that. but first I need to download the file and it says that it takes 2 hours to finish
(Slow internet connection)
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g/help/stuck-boot-failed-t3104617/post60653710#post60653710
I heard that I hard bricked my phone:crying:

poolta321 said:
http://forum.xda-developers.com/moto-g/help/stuck-boot-failed-t3104617/post60653710#post60653710
I heard that I hard bricked my phone:crying:
Click to expand...
Click to collapse
If the phone turns on and shows the fastboot screen, it's not hard-bricked to me. Proceed as I suggested.

lost101 said:
If the phone turns on and shows the fastboot screen, it's not hard-bricked to me. Proceed as I suggested.
Click to expand...
Click to collapse
yes but he said that the bootloader was messed up and that there was no way to fix it

poolta321 said:
yes but he said that the bootloader was messed up and that there was no way to fix it
Click to expand...
Click to collapse
I read what he said, but I do not agree. I suggest you do as I describe above.

lost101 said:
I read what he said, but I do not agree. I suggest you do as I describe above.
Click to expand...
Click to collapse
Okay so what do I need to do?
(I'm away for a while)

poolta321 said:
Okay so what do I need to do?
(I'm away for a while)
Click to expand...
Click to collapse
Okay I'm back. and I did what you said but it didn't work. when I turn on my phone it says: Fastboot Reason: Fall-trough from normal boot mode.
Here is the cmd log:
G:\Program Files\SDK\platform-tools>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.328s
G:\Program Files\SDK\platform-tools>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.366s
G:\Program Files\SDK\platform-tools>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.140s]
finished. total time: 0.218s
G:\Program Files\SDK\platform-tools>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.372s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.841s
G:\Program Files\SDK\platform-tools>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.381s]
writing 'recovery'...
OKAY [ 0.964s]
finished. total time: 1.348s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.0
target max-sparse-size: 256MB
sending 'system' (260841 KB)...
OKAY [ 8.458s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.851s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.1
target max-sparse-size: 256MB
sending 'system' (236285 KB)...
OKAY [ 7.760s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.827s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.2
target max-sparse-size: 256MB
sending 'system' (257383 KB)...
OKAY [ 8.364s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.437s
G:\Program Files\SDK\platform-tools>mfastboot flash system system.img_sparsechun
k.3
target max-sparse-size: 256MB
sending 'system' (33384 KB)...
OKAY [ 1.163s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.236s
G:\Program Files\SDK\platform-tools>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (59132 KB)...
OKAY [ 2.200s]
writing 'modem'...
OKAY [ 2.831s]
finished. total time: 5.037s
G:\Program Files\SDK\platform-tools>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.026s]
finished. total time: 0.029s
G:\Program Files\SDK\platform-tools>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.088s]
finished. total time: 0.090s
G:\Program Files\SDK\platform-tools>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (661 KB)...
OKAY [ 0.107s]
writing 'fsg'...
OKAY [ 5.061s]
finished. total time: 5.170s
G:\Program Files\SDK\platform-tools>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.103s]
finished. total time: 0.105s
G:\Program Files\SDK\platform-tools>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.218s]
finished. total time: 0.219s
G:\Program Files\SDK\platform-tools>mfastboot reboot
rebooting...
finished. total time: 0.003s

XT1541 broken after attempt do factory reset

Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks

IK1981 said:
Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks
Click to expand...
Click to collapse
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750

bobby0724 said:
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Click to expand...
Click to collapse
Already tried this. Already fails at first command... When doing this for the first time, it takes up to one minute to get a response. When retrying, it fails immediately
Code:
~/Downloads/XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7_subsidy-DEFAULT_CFC__v2.xml# fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 55.425

Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !

therealduff1 said:
Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !
Click to expand...
Click to collapse
Thanks for your help. Tried it with your tool but as far as I could see I land in the same troubles.
Code:
OSPREY_RETEU_6.0_MPI24.65-33_cid7_subsidy
please move all of the firmware files into the moto toolkit directory (the same folder containing toolkit.py)
Please make sure usb debugging is turned on in developer settings, then type 'done' into this promptdone
error: device '(null)' not found
Has your device successfully loaded bootloader mode ? please type 'yes' if it has successfully loadedyes
Press enter to confirm you would like to upgrade to android marshmallow ;)
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 55.795s
Partition table has been flashed
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.438s
Bootloader has been flashed
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.062s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.172s
boot logo has been flashed
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.530s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.093s
boot.img has been flashed
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.094s
Stock marshmallow recovery has now been flashed
target reported max download size of 268435456 bytes
sending 'system' (238438 KB)...
OKAY [ 7.500s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 15.891s
System part 1 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (238552 KB)...
OKAY [ 7.492s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.608s
System part 2 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (256695 KB)...
One thing that confuses me is the fact that the tool tells me that I shall turn on the USB debug mode. However, since Android does not boot any longer, I have no chance to do this in the Settings. Is there any way to enable this debug mode in another way?

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