Database Info

How to flash Stock Kit Kat / no flashall.bat???

Hmm......maybe to easy but i was wondering how to flash Blur_Version.175.44.1.falcon_umts.Retail.en.DE (444MB Stock Kit Kat) which is which is available on sbf.droid-developers.org since a few days.
There is no flashall.bat in the zip.
I can not try myself. Forgot my phone at a friends place :crying:
Will have to wait for weekend to get it back or maybe by Mail.
Just by using Custom Recovery?
Maybe i should just ask my friend to do it, cause i wanna know :laugh:
Cannot wait flashing only one file instead of three when going back to stock.

Won't it void your warranty!? :S

It would void my guarantee but not my warranty.
I bought it in Germany. That's a EU directive.
And secondary i waited one month to see if everything works right.
Now i hope that no serious problems will come up.
And i want to flash a Stock Rom. So actually there is no need to Root or something cause it should be signed.

Found it here:
akaygee said:
relock bootloader
=============
download adb and fastboot extract or place into a directory.
now download the factory firmware image of your phone extract zip/rar and place into the same directory.
download "relock bootloader.txt" rename to "relock bootloader.bat" place this in the same directory as the files and double click it ,this would save you typing in all the commands from below in by hand and does it all for you.recap....if you did download and run relock bootloader.bat you dont need to type anything form below
open a command prompt as administrator ,navigate to the directory where you placed all the files we are working with and type as follows giving time for each command to finish.
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Click to expand...
Click to collapse
Sure the relock Stuff can be ignored.
And for the sparsechunk remember:
spiritflare said:
Just remember that unless you download the Motorola version of FASTBOOT, you won't be able to flash the Sparsechunk files...
You will get:
C:\sdk-tools>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
Once I downloaded the Motorola version of fastboot from here: http://theunlockr.com/2013/12/06/unroot-motorola-moto-g/ (see link in this article) - - - (or just google for Motorola g fastboot)
Also, the final step here, it says:
C:\sdk-tools>fastboot oem lock
... FAILED (status read failed (Too many links))
finished. total time: 17.659s
it will still lock the bootloader - you can verify by reboot the device and you will see bootloader status "Locked"
Hope this helps
Click to expand...
Click to collapse

Failed to erase partition...getting desperate here

Please help. I saved some money and bought this phone in January via a friend abroad (xt1033) and by February updated it to lollipop but few days later after the update the phone suddenly rebooted and got in the boot loop. Since then I haven't been able to use the phone for three months. It no longer has warranty because I attempted to unlock its bootloader and besides by availing the warranty I need to send back the phone from Philippines to the Kingdom of Saudi Arabia where it is bought and that is expensive and risky on my part. So now either I fix the phone myself or it goes straight to the trash bin.
I tried following threads here in the forum such as restoring the phone to stock, installing custom recoveries, flashing images. All of these returned the same error. And that is.
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 10.300s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.377s
No matter what I do. The line (bootloader) Failed to erase partition always comes out. I have tried searching for the same threads here in the forum but all are unanswered. Please help me to fix this phone.

Try using mfastboot:
https://www.androidfilehost.com/?fid=23578570567719065​
Just so you are aware: very careful using the 'erase' command. Erasing certain partitions will destroy the phone. The only commands to ever really use are:
mfastboot erase cache
mfastboot erase userdata​
Is the phone definitely an XT1033 Dual-SIM?

lost101 said:
Try using mfastboot:
Just so you are aware: very careful using the 'erase' command. Erasing certain partitions will destroy the phone. The only commands to ever really use are:
mfastboot erase cache
mfastboot erase userdata​
Is the phone definitely an XT1033 Dual-SIM?
Click to expand...
Click to collapse
Yes sir it was bought in Saudi (asia) and is dual sim. The box also states that it is xt1033.
I have tried what you have suggested but the error still remains.
C:\Users\...\Desktop\mfastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 14.955s
C:\Users\...\Desktop\mfastboot>mfastboot erase userdata[/U]
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.953s
If it is of any help, the screen says that it has 41.18 bootloader, I don't exactly know what this information is for.

Try flashing the XT1033 Retail Asia Factory Firmware Image: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Do all commands manually:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk4 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​

lost101 said:
Try flashing the XT1033 Retail Asia Factory Firmware Image: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Do all commands manually:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk4 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
Click to expand...
Click to collapse
I already tried sir along with the Brazilian firmware and both returned the same error. The same partition error,
I get stuck right at the first command "mfastboot flash partition gpt.bin", it says the the phone couldn't erase the partition. I'm starting to hate motorola right now
The money I saved just to buy this phone and I only got to use it for 1 month.
I understand that my partition is likely messed up or is corrupted even though I did nothing with my phone except upgrading it to lollilop (biggest mistake ever), what I don't understand is there aren't anyone else here in the forum who seem to have the same problem as mine, its like I am the only who has this kind of error so there are no threads at all discussing on how to solve this.

You could try booting into a custom recovery using the following command:
mfastboot boot recovery.img​
Try latest TWRP: http://forum.xda-developers.com/showpost.php?p=57672469&postcount=1
and flash one of these Lollipop zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510

lost101 said:
You could try booting into a custom recovery using the following command:
mfastboot boot recovery.img​
Try latest TWRP: http://forum.xda-developers.com/showpost.php?p=57672469&postcount=1
and flash one of these Lollipop zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
I can't install TWRP nor clockwerk recovery, whenever I try the same frustrating error occurs. Here:
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8480 KB)...
OKAY [ 5.306s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.424s

titan015 said:
I can't install TWRP nor clockwerk recovery, whenever I try the same frustrating error occurs. Here:
Click to expand...
Click to collapse
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​

lost101 said:
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​
Click to expand...
Click to collapse
Sir I'm sorry but could you please elaborate more on what am I supposed to do?
What I did was download TWRP, renamed it to recovery.img and then pasted it in a folder with mfastboot in it. I then executed the command you supplied "mfastboot boot recovery.img" and heres the result:
C:\Users\...\Desktop\mfastboot>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 10.297s]
booting...
FAILED (remote failure)
finished. total time: 20.326s
on the phone it says in pink font color "Incomplete boot image for booting"

Try another recovery.img just in case that one was a bad download.

titan015 said:
Please help. I saved some money and bought this phone in January via a friend abroad (xt1033) and by February updated it to lollipop but few days later after the update the phone suddenly rebooted and got in the boot loop. Since then I haven't been able to use the phone for three months. It no longer has warranty because I attempted to unlock its bootloader and besides by availing the warranty I need to send back the phone from Philippines to the Kingdom of Saudi Arabia where it is bought and that is expensive and risky on my part. So now either I fix the phone myself or it goes straight to the trash bin.
I tried following threads here in the forum such as restoring the phone to stock, installing custom recoveries, flashing images. All of these returned the same error. And that is.
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 10.300s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.377s
No matter what I do. The line (bootloader) Failed to erase partition always comes out. I have tried searching for the same threads here in the forum but all are unanswered. Please help me to fix this phone.
Click to expand...
Click to collapse
I have the same problem, do you managed to fix it?

kesy85 said:
I have the same problem, do you managed to fix it?
Click to expand...
Click to collapse
no. i've tried just about everything, didn't managed to fix it

hi
i have the same problem too bro, im from the philippines too..
have u fixed it yet?

no fix?
Is this thread abandoned?
Is unlocking your bootloader a prequisite to flashing recovery.img? I have a soft bricked (from what I've read) XT 1032 and I forgot which Lollipop version I had (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files and that had the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooted my phone either. I was running pure OTA stock when my phone suddenly stopped booting up and went into a boot loop.

Same for me, BUMP
hand_solo said:
Is this thread abandoned?
Is unlocking your bootloader a prequisite to flashing recovery.img? I have a soft bricked (from what I've read) XT 1032 and I forgot which Lollipop version I had (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files and that had the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooted my phone either. I was running pure OTA stock when my phone suddenly stopped booting up and went into a boot loop.
Click to expand...
Click to collapse
Anyone managed to fix this?

The best I've found...
hand_solo said:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
Click to expand...
Click to collapse
...is this:
Cant flash GPT / Motoboot:
Use another firmware, try for another android versions.
Fastboot Error: preflash validation failed
Try your original (or last flashed) firmware.
Click to expand...
Click to collapse
from this thread: http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076/
P.s.: I have the same problem.

titan015 said:
Sir I'm sorry but could you please elaborate more on what am I supposed to do?
What I did was download TWRP, renamed it to recovery.img and then pasted it in a folder with mfastboot in it. I then executed the command you supplied "mfastboot boot recovery.img" and heres the result:
C:\Users\...\Desktop\mfastboot>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 10.297s]
booting...
FAILED (remote failure)
finished. total time: 20.326s
on the phone it says in pink font color "Incomplete boot image for booting"
Click to expand...
Click to collapse
lost101 said:
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img​
Flashes TWRP:
mfastboot flash recovery recovery.img​
Click to expand...
Click to collapse
For me the error is:
Code:
fastboot flash recovery twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
target reported max download size of 536870912 bytes
[COLOR="SeaGreen"]sending 'recovery' (9372 KB)...
OKAY [ 0.377s]
[/COLOR]writing 'recovery'...
[COLOR="Red"][B](bootloader) Permission denied
FAILED (remote failure)[/B][/COLOR]
finished. total time: 0.408s
Same thing when I try to boot instead of Flashing
Code:
fastboot boot twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
[COLOR="SeaGreen"]downloading 'boot.img'...
OKAY [ 0.347s][/COLOR]
booting...
[B][COLOR="Red"]FAILED (remote failure)
[/COLOR][/B]finished. total time: 0.354s

An unlocked Bootloader is required to flash (or boot) a custom recovery.

lost101 said:
An unlocked Bootloader is required to flash (or boot) a custom recovery.
Click to expand...
Click to collapse
But it's a Stock rom... I've tryied this custom recovery, of course, but this isn't working with a stock rom either.

Der_K said:
But it's a Stock rom... I've tryied this custom recovery, of course, but this isn't working with a stock rom either.
Click to expand...
Click to collapse
Please try to explain more clearly. Don't use the term ROM, if you are talking about a factory firmware image - in other words - sparsechunk files.
Can you flash the stock recovery img included in the factory firmware image?

Motorola Moto G3 XT1541

Hi,
I've got a Motorola Moto G XT1541.
Being an android newbie, and bored one time I tried to root my device with what I think was the KingRoot App, and being stupid and not bothering to read to much up about it (as I wanted to store apps on the SD card as internal memory is limited) it obviously bricked my phone! It currently only boots up in the fastboot mode only stating:
"Start up failed. Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant.
AP Fastboot Flash mode(secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image"
Details on the device: Device is locked. status code: 0. Osprey XT1541. (Any other specifics needed just ask).
I have attempted to flash the firmware back to standard again which hasn't worked. (Obviously I'm doing something wrong!) the answers to the commands i have included below.
fastboot flash partition gpt.bin
sending partition okay
wiriting partition... INFOPreflash validation failed FAILED (remote failure)
fastboot flash motoboot boot.img
sending motoboot okay
writing 'flash'... INFOPermission denied FAILED (Remote failure)
fastboot flash logo logo.bin
sending logo.. okay
writing logo.. okay
fastboot flash boot boot.img
sending boot ... okay
writing boot... INFOPREFlash validation failed
fastboot flash recovery recovery.img
sending recovery .. okay
writing recover.. okay
fastboot flash system system.img_sparsechunk1
error: cannot load 'system.img_sparsechunk1'
fastboot flash system system.img_sparsechunk2
error: cannot load 'system.img_sparsechunk2'
fastboot flash system system.img_sparsechunk3
error: cannot load 'system.img_sparsechunk3'
fastboot flash modem NON-HLOS.bin
sending modem... okay
writing modem... okay
fastboot erase modemst1
erasing modemst1... okay
fastboot erase modemst2
erasing modemst2... okay
fastboot flash fsg fsg.mbn
sending fsg... okay
writing fsg... okay
fastboot erase cache
erasing cache... okay
fastboot erase userdata
erasing userdata... okay
fastboot reboot
Any help would be greatly appreciated as trying to learn this as I go
Thanks

Anyone with any ideas?

Which firmare are you trying to install? The newest one? It also seems you didn't unpack images correctly.

Acetyloaceton said:
Which firmare are you trying to install? The newest one? It also seems you didn't unpack images correctly.
Click to expand...
Click to collapse
I'm trying to install the factory firmware for the phone so it's MotoG3 Osprey XT1541 Retail GB downloaded from somewhere on this site if i remember correctly.
What do you mean by unpack the images? I extracted the firmware out of the zip file and then copied it over into the fastboot folder.
Thanks for the reply

Looks like either thexml.zip archive or download was bad. Or else it wasn't unpacked correctly. Try downloading again and make sure that it's correct firmware. [emoji39] .
Edit: Also check for additional sparsechunk files in the extracted folder, you must flash all of them.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Looks like either thexml.zip archive or download was bad. Or else it wasn't unpacked correctly. Try downloading again and make sure that it's correct firmware. [emoji39] .
Edit: Also check for additional sparsechunk files in the extracted folder, you must flash all of them.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Okay will download the firmware again and see if it works

Which version of android did you have before stuck? Lollipop or marshmallow? These commands look like you are trying to flash lollipop. You can't do downgrades without unlocking bootloader. If I were you I would try to flash 6.0.1
1. Download firmware 1gb or 2gb (I dont know which version do you have).
2. Unpack it to folder with adb driver
3. Reboot to bootloader
4. Flash images:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Remember to check how many sparsechunk do you have. If I remember correctly 6.0.1 have 0-7 sparsechunks

I think it was marshmellow, but not 100%! So i re-downloaded the firmware and redid all the steps however when going through the opening steps my phone cannot pick up a wifi network, so i'm assuming I've installed the wrong firmware onto the device now?
What information would i need to provide for you to confirm I've installed the correct firmware? I went for these drivers
https://www.androidfilehost.com/?w=...a551901007e63955ed25336c82cebd8339ed5c13843cc
Thanks for the help guys really appreciate it!

Acetyloaceton said:
Which version of android did you have before stuck? Lollipop or marshmallow? These commands look like you are trying to flash lollipop. You can't do downgrades without unlocking bootloader. If I were you I would try to flash 6.0.1
1. Download firmware 1gb or 2gb (I dont know which version do you have).
2. Unpack it to folder with adb driver
3. Reboot to bootloader
4. Flash images:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Remember to check how many sparsechunk do you have. If I remember correctly 6.0.1 have 0-7 sparsechunks
Click to expand...
Click to collapse
As my phone isn't finding wifi would you recommend i redo the steps with the above firmware? instead of the firmware I've currently used? I'm guessing I can tell how many sparsechunks by checking the downloaded folder?

I remember someone had also this issue when he didnt do hard reset before flashing firmware. Go to recovery and do full factory reset. Here is guide. After it flash firmware again

Acetyloaceton said:
I remember someone had also this issue when he didnt do hard reset before flashing firmware. Go to recovery and do full factory reset. Here is guide. After it flash firmware again
Click to expand...
Click to collapse
This Worked! Thanks alot :good:

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

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

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

Try with these commands
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Skip gpt.bin and bootloadet.img

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

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

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

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

Flashing Problems! :/
You need to wait to the next security patch... then flash all commands except fastboot oem lock begin and fastboot oem lock...... it works! the same thing happen with my old MotoX and i waited months! then i flashed and everything was fine!
I recommend you for your next ROM flashing experiments and updates to flash like this the patches...
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
you may try this commands! hope it works!:good:

MOTO G3 2015 XT1550 bricked while trying to unroot

So I unlocked my boot loader, flashed lineage OS and TWRP onto my phone, which was working fine, till I installed a root checker.
It said my phone wasn't rooted and I figured it was because I didn't flash the SuperSu files(it kept boot looping every time I flashed it so I decided to skip it. I figured I'd un root and while re rooting, I'd flash SuperSu through the command prompt to see if it made a difference..Unfortunately I watched a video from some idiot whose method rarely worked(according to the comment section) many people faced the same problem and the video creator failed to answer...many other videos using the same method had the same comments but no one fixed the problem.
The problem is that while typing the following codes, they start to spit out failed messages from the 5th code till the last sparsechunk file(it shows only 6 but my phone stock ROM version has 8, so I add 6 7 and 8)
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
I'm now unable to flash any custom ROM to fix the problem or revert back to the stock ROM using alternate methods such as simply flashing the stock ROM zip...While flashing anything, it says unable to mount cache data and storage. the boot loader says device unlocked, status code 3 but the software status says official, even while I had lineage OS installed...please help and tell me if I need to share more information to find a fix.
In my defence, the last device I NEEDED to root was my Samsung galaxy tab 2

crazykid1234 said:
So I unlocked my boot loader, flashed lineage OS and TWRP onto my phone, which was working fine, till I installed a root checker.
It said my phone wasn't rooted and I figured it was because I didn't flash the SuperSu files(it kept boot looping every time I flashed it so I decided to skip it. I figured I'd un root and while re rooting, I'd flash SuperSu through the command prompt to see if it made a difference..Unfortunately I watched a video from some idiot whose method rarely worked(according to the comment section) many people faced the same problem and the video creator failed to answer...many other videos using the same method had the same comments but no one fixed the problem.
The problem is that while typing the following codes, they start to spit out failed messages from the 5th code till the last sparsechunk file(it shows only 6 but my phone stock ROM version has 8, so I add 6 7 and 8)
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
I'm now unable to flash any custom ROM to fix the problem or revert back to the stock ROM using alternate methods such as simply flashing the stock ROM zip...While flashing anything, it says unable to mount cache data and storage. the boot loader says device unlocked, status code 3 but the software status says official, even while I had lineage OS installed...please help and tell me if I need to share more information to find a fix.
In my defence, the last device I NEEDED to root was my Samsung galaxy tab 2
Click to expand...
Click to collapse
you need to be more specific if you need help, like what command you used in command prompt and what error you are getting in fastboot.

Rohi09 said:
you need to be more specific if you need help, like what command you used in command prompt and what error you are getting in fastboot.
Click to expand...
Click to collapse
As I said, the commands were
1)fastboot flash partition gpt.bin
2)fastboot flash bootloader bootloader.img
3)fastboot flash logo logo.bin
4)fastboot flash boot boot.img
5)fastboot flash recovery recovery.img
6)fastboot flash system system.img_sparsechunk.0
7)fastboot flash system system.img_sparsechunk.1
8)fastboot flash system system.img_sparsechunk.2
9)fastboot flash system system.img_sparsechunk.3
10)fastboot flash system system.img_sparsechunk.4
11)fastboot flash system system.img_sparsechunk.5
12)fastboot flash system system.img_sparsechunk.6
13)fastboot flash system system.img_sparsechunk.7
14)fastboot flash modem NON-HLOS.bin
15)fastboot erase modemst1
16)fastboot erase modemst2
17)fastboot flash fsg fsg.mbn
18)fastboot erase cache
19)fastboot erase userdata
20)fastboot oem lock
21)fastboot reboot
In that order
"(bootloader) preflash validation failed failed (remote failure)" is the error I get in command prompt for command 4 and 6-13

crazykid1234 said:
As I said, the commands were
1)fastboot flash partition gpt.bin
2)fastboot flash bootloader bootloader.img
3)fastboot flash logo logo.bin
4)fastboot flash boot boot.img
5)fastboot flash recovery recovery.img
6)fastboot flash system system.img_sparsechunk.0
7)fastboot flash system system.img_sparsechunk.1
8)fastboot flash system system.img_sparsechunk.2
9)fastboot flash system system.img_sparsechunk.3
10)fastboot flash system system.img_sparsechunk.4
11)fastboot flash system system.img_sparsechunk.5
12)fastboot flash system system.img_sparsechunk.6
13)fastboot flash system system.img_sparsechunk.7
14)fastboot flash modem NON-HLOS.bin
15)fastboot erase modemst1
16)fastboot erase modemst2
17)fastboot flash fsg fsg.mbn
18)fastboot erase cache
19)fastboot erase userdata
20)fastboot oem lock
21)fastboot reboot
In that order
"(bootloader) preflash validation failed failed (remote failure)" is the error I get in command prompt for command 4 and 6-13
Click to expand...
Click to collapse
Skip the bootloader and gpt.bin files. It should flash successfully​. Preflash validation failure occurs when you're flashing an older version of firmware on a newer one. Skip those two files and you should be good.

crazykid1234 said:
As I said, the commands were
1)fastboot flash partition gpt.bin
2)fastboot flash bootloader bootloader.img
3)fastboot flash logo logo.bin
4)fastboot flash boot boot.img
5)fastboot flash recovery recovery.img
6)fastboot flash system system.img_sparsechunk.0
7)fastboot flash system system.img_sparsechunk.1
8)fastboot flash system system.img_sparsechunk.2
9)fastboot flash system system.img_sparsechunk.3
10)fastboot flash system system.img_sparsechunk.4
11)fastboot flash system system.img_sparsechunk.5
12)fastboot flash system system.img_sparsechunk.6
13)fastboot flash system system.img_sparsechunk.7
14)fastboot flash modem NON-HLOS.bin
15)fastboot erase modemst1
16)fastboot erase modemst2
17)fastboot flash fsg fsg.mbn
18)fastboot erase cache
19)fastboot erase userdata
20)fastboot oem lock
21)fastboot reboot
In that order
"(bootloader) preflash validation failed failed (remote failure)" is the error I get in command prompt for command 4 and 6-13
Click to expand...
Click to collapse
no I asked about the command you used to install SuperSU. anyway if you are getting preflash validation failed error then just skip the first 2 lines of command, ie. gpt and bootloader, and use the rest. do a factory reset from twrp or stock recovery before flashing anyway.

.
I didn't use any command for SuperSu...before I got to that part, the phone bricked....
I'll try the methods you've mentioned and will get back soon!

Got it to work!!! but could you please explain why whenever I flash SuperSu, either through a ZIP or through the TWRP option when exiting the recovery, my phone bootloops?

It depends on the version of TWRP and superSU you are flashing ..... Use of latest twrp version and super su version does not results in bootloop if flashed properly ... If u want to root ur device again u can download the SuperSU zip file from attachment ...
Instructions to root via twrp recovery
First flash ur room and gapp ...
Reboot ur device ... Complete the setup
Then reboot to recovery ... Flash the super su zip file ... Wipe cache and dalvik cache ... And reboot u will succeed ??? Happy Flashing

Got it to work! Thanks a lot guys!