Develop Bugs

Tutorial| Fixing "Fastboot mode started"

I've saw a lot of these posts and I also had the same Issue.
first of all I'm not taking any responsible for this, but it worked for me so.. you can at least try if you have no option left.
please note thatYOU WILL LOSE EVERYTHING on the internal storage of your LG G3!
IF YOU DON'T HAVE ACCESS TO DOWNLOAD MODE :
Please get yourself the right LAF file for your phone and insert it into the adb.exe and the fastboot.exe folder (if you don't know what I talk about please download Android SDK platform)
press Ctrl+Shift and right click inside the folder and choose Open Command window here (http://img5013.photobox.co.uk/11895...2cd987792512dcafe1c9acf628a3ef5b3a604bc5f.jpg)
Now at the CMD window that opened Type :
fastboot erase recovery
PLESAE MAKE SURE YOU DOWNLOADED THE RIGHT LAF FILE FOR YOUR PHONE before attempting this (at the same android version)
fastboot erase laf
fastboot flash laf laf.img
Click to expand...
Click to collapse
If you can't find the LAF file for your phone you'll have to Extract it from the KDZ file using this Tool http://forum.xda-developers.com/showthread.php?t=2600575
Now you can accesses the download mode by restarting the phone.
Take the battery and the Sync cable out
while pressing the +Vol button insert the battery and the cable while continuing holding it
IF YOU HAVE ACCESS TO DOWNLOAD MODE :
Please download the TOT and .Dll files specifically for your phone from here: http://downloadandroidfiles.org/Files/LG G3/Stock Files/
after that follow this video and you're all good :
http://www.youtube.com/watch?v=1VVms7SdM04

SaharLevi said:
I've saw a lot of these posts and I also had the same Issue.
first of all I'm not taking any responsible for this, but it worked for me so.. you can at least try if you have no option left.
please note thatYOU WILL LOSE EVERYTHING on the internal storage of your LG G3!
IF YOU DON'T HAVE ACCESS TO DOWNLOAD MODE :
Please get yourself the right LAF file for your phone and insert it into the adb.exe and the fastboot.exe folder (if you don't know what I talk about please download Android SDK platform)
press Ctrl+Shift and right click inside the folder and choose Open Command window here (http://img5013.photobox.co.uk/11895...2cd987792512dcafe1c9acf628a3ef5b3a604bc5f.jpg)
Now at the CMD window that opened Type :
If you can't find the LAF file for your phone you'll have to Extract it from the KDZ file using this Tool http://forum.xda-developers.com/showthread.php?t=2600575
Now you can accesses the download mode by restarting the phone.
Take the battery and the Sync cable out
while pressing the +Vol button insert the battery and the cable while continuing holding it
IF YOU HAVE ACCESS TO DOWNLOAD MODE :
Please download the TOT and .Dll files specifically for your phone from here: http://downloadandroidfiles.org/Files/LG G3/Stock Files/
after that follow this video and you're all good :
http://www.youtube.com/watch?v=1VVms7SdM04
Click to expand...
Click to collapse
Am getting this ERROR :
D:\--- MOBILE\Android\android\platform-tools>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.035s
Click to expand...
Click to collapse

Have you Installed the LG G3 Drivers?
Does your windows recognize it ?
If not please download http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425

SaharLevi said:
I've saw a lot of these posts and I also had the same Issue.
first of all I'm not taking any responsible for this, but it worked for me so.. you can at least try if you have no option left.
please note thatYOU WILL LOSE EVERYTHING on the internal storage of your LG G3!
IF YOU DON'T HAVE ACCESS TO DOWNLOAD MODE :
Please get yourself the right LAF file for your phone and insert it into the adb.exe and the fastboot.exe folder (if you don't know what I talk about please download Android SDK platform)
press Ctrl+Shift and right click inside the folder and choose Open Command window here (http://img5013.photobox.co.uk/11895...2cd987792512dcafe1c9acf628a3ef5b3a604bc5f.jpg)
Now at the CMD window that opened Type :
If you can't find the LAF file for your phone you'll have to Extract it from the KDZ file using this Tool http://forum.xda-developers.com/showthread.php?t=2600575
Now you can accesses the download mode by restarting the phone.
Take the battery and the Sync cable out
while pressing the +Vol button insert the battery and the cable while continuing holding it
IF YOU HAVE ACCESS TO DOWNLOAD MODE :
Please download the TOT and .Dll files specifically for your phone from here: http://downloadandroidfiles.org/Files/LG G3/Stock Files/
after that follow this video and you're all good :
http://www.youtube.com/watch?v=1VVms7SdM04
Click to expand...
Click to collapse
hi, just one nooby question. where are the adb.exe and the fastboot exe folders?

Hi Mate, It's not noobie at all.
You need to download the Android Debug Bridge (ADB) from this Link :http://developer.android.com/sdk/index.html
Ticket the platform-tools you don't need the rest
Or you can have the easy way and Download it from here: http://forum.xda-developers.com/showthread.php?t=2588979
Or maybe you don't know where are the specific folder in which case go to where you installed it. mine is at C:\Users\Sahar\platform-tools
And on the way download the LG G3 drivers from LG download center or from this link: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425

thanks amigo! I'll check it out.

@SaharLevi
Here's the fix Quick and easy
need to have fastboot, I used ubuntu can install with sudo apt-get install android-tools-fastboot
info on fastboot
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer
also need recovery.img, I used the lastest twrp
In terminal
fastboot boot recovery.img
this will boot your phone with the img on your computer.
in recovery restore or install a good boot or kernel.
your phone should be good to go after that.
I had my phone fixed in about 5 min, I really should not play around with boot partition.
Also should be able to flash boot if you have a good one,
fastboot flash boot boot.img

zakiyy said:
Am getting this ERROR :
Click to expand...
Click to collapse
man i am getting the same error! says something about the mmc on the phone not being able to erase it or whatever

zakiyy said:
Am getting this ERROR :
Click to expand...
Click to collapse
Timahthee said:
man i am getting the same error! says something about the mmc on the phone not being able to erase it or whatever
Click to expand...
Click to collapse
if you have fastboot mode you probably already erased the laf partition and you can't erase what you don't have. just continue

I have a weird problem, i'm in fastboot, and my laptop sees the phone, but none of the fastboot commands work. They get echoed on the screen and appear to be working but they don't do anything. I've tried flashing, rebooting... pretty much everything, and nothing happens.

bartcoop2 said:
I have a weird problem, i'm in fastboot, and my laptop sees the phone, but none of the fastboot commands work. They get echoed on the screen and appear to be working but they don't do anything. I've tried flashing, rebooting... pretty much everything, and nothing happens.
Click to expand...
Click to collapse
can you show the commands you typed?

jcfunk said:
can you show the commands you typed?
Click to expand...
Click to collapse
I navigate into a folder with all my img files and then tried a few things:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot boot boot.img
fastboot flash laf laf.img
I've also tried to erase a few times, and even reboot, and nothing happens, even though it says on the lg screen that it's rebooting.

bartcoop2 said:
I navigate into a folder with all my img files and then tried a few things:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot boot boot.img
fastboot flash laf laf.img
I've also tried to erase a few times, and even reboot, and nothing happens, even though it says on the lg screen that it's rebooting.
Click to expand...
Click to collapse
try
adb fastboot flash recovery [located recovery file]
or
./adb fastboot flash recovery [located recovery file]

KingOfDope said:
try
adb fastboot flash recovery [located recovery file]
or
./adb fastboot flash recovery [located recovery file]
Click to expand...
Click to collapse
I'm assuming you meant just fastboot, adb fastboot just prints out help.
It says:
Code:
target reported max download size of 2147483648 bytes
sending 'recovery' (11496 KB)...
OKAY [ 0.362s]
writing 'recovery'...
and on the phone it says [7164300] fastboot: flash:recovery
But nothing happens. It's as if fastboot is broken.

bartcoop2 said:
I navigate into a folder with all my img files and then tried a few things:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot boot boot.img
fastboot flash laf laf.img
I've also tried to erase a few times, and even reboot, and nothing happens, even though it says on the lg screen that it's rebooting.
Click to expand...
Click to collapse
Type from folder with recovery.img
fastboot boot recovery.img
if it a bumped recovery, it should boot into recovery. Then you should be able to restore a backup

jcfunk said:
Type from folder with recovery.img
fastboot boot recovery.img
if it a bumped recovery, it should boot into recovery. Then you should be able to restore a backup
Click to expand...
Click to collapse
I've tried that, i think my fastboot is somehow corrupt, i guess i have a hard-brick, i hope LG will replace it.
Thanks for your help

bartcoop2 said:
I've tried that, i think my fastboot is somehow corrupt, i guess i have a hard-brick, i hope LG will replace it.
Thanks for your help
Click to expand...
Click to collapse
also have you tried a different usb cable? Mine stop working after a month. Only charges phone but won't connect to computer
Sent from my tf700t using Tapatalk

jcfunk said:
also have you tried a different usb cable? Mine stop working after a month. Only charges phone but won't connect to computer
Sent from my tf700t using Tapatalk
Click to expand...
Click to collapse
Yeah i tried, no go

bartcoop2 said:
I.
Click to expand...
Click to collapse
I have yoir problem,too.Have you find out how to fix it?

akaHardison said:
I have yoir problem,too.Have you find out how to fix it?
Click to expand...
Click to collapse
i find it

[Q] LG G3 Stuck on fastboot! [FIXED!!!!!]

I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!

MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work

MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:

itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
573v3 said:
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:
Click to expand...
Click to collapse
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.

MWGiants said:
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.
Click to expand...
Click to collapse
congrats. it is good to know it is fixable

That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk

That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk

Hakem said:
That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
Click to expand...
Click to collapse
Fastboot boot laf.img
But beware this doesnt work for D855. His LS980 has a unlocked bootloader

Ok thanks
Verstuurd vanaf mijn HTC One_M8 met Tapatalk

MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means

bikrame said:
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means
Click to expand...
Click to collapse
Hi, sorry for the late reply. I hope you've already fixed it, but if you're still having this problem then let me explain. "laf.img" is the "download mode" partition. The reason you can't use twrp.img (which is a recovery partition image) is because you're "too far gone" so to speak and not even at the point to try and get into recovery. You need to restore download mode first. If you have fastboot properly working (not going to explain that, look it up, there is plenty of info about that on here and other sites), then you can do what I did. (Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work, I cant tell you about that because I don't have one and haven't played around with one). Anyway, if you have fastboot working properly (read my first post about how it can be working as long as the phone is responsive, even if you don't get back the "devices comman", you may need to play around with the drivers to get this to work) then you need to obtain an laf.img from somwhere. I found a complete set of .img's for my model somewhere (don't remember if it was on this site or somewhere else). It took a lot of searching, but I'm sure you can find one. Once you have that and the working fastboot then run the command "fastboot boot [location of your laf.img]laf.img"
GOOD LUCK!!!

itsbighead said:
That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
That's interesting...do you have any idea why that would be? Is it a locked bootloader like someone else mentioned? (I don't know much about the D855 model, never got to play with one). Maybe there is a workaround we can come up with...

itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
I realized the problem with the mismatched aboot after the fact... ironically it all worked out because after all of this I am now back to the original kitkat and can just root and flash as you said lol.

Complete Fix Guide
http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965

Can you please post where you got your laf file? I have the same problem :crying:

MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
can you please help. adb shows my device and fastboot wont. when i type in fastboot devices it doesnt show anything. tried to run commands but it always gets stuck on waiting for device..

MWGiants said:
(Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work,
Click to expand...
Click to collapse
What to do with D855 than, my friend have D855 and it's stcked in fastboot mode, doesn't allow to flash anything?

lg g3 f410 stuck at fastboot
i tried the solution it didnot work. phone accepts the cmds but remain stuck at fastboot any other method?

[Q] Hardbrick after overwrite fastboot

Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks

I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/

EdoIsa said:
I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
Click to expand...
Click to collapse
What are FZ DnX, IFWI, FW DnX and OS images files ?
How to extract them from the site you mentioned?
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....

I have no experience with FZ DnX, IFWI, FW DnX files, but the OS image file is on the site I posted.
Follow my link. Once there, expand the list 'Firmware' and download firmware Version WW_2.15.40.10. Once its downloaded, open the zip file. Inside should be a System.img file. Extract the System.img file into your Fastboot folder. This is the OS image the guide is referring to.
Ask around for the meaning of the other files. Meanwhile, I will research more about those files later tomorrow and get back with any info I can find. Good luck!

cde2006 said:
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....
Click to expand...
Click to collapse
install driver manually. see attachment.

When you plug your phone into the computer, does the phone show up in the device management? Typing devmgmt.msc into the windows 7 start menu or the start run menu on XP is the fastest way to get to Device Manager.
Is the device already known by your computer?
What does device manager think it is?
If its unknown, please let us know what the Hardware Ids and Compatible Ids for this device show up as. In device manageer, you can open the devices properties and under the details tab choose Hardware Ids and Compatible Ids. you could screen shot these with Alt + PrtScn and use mspaint to save them off. Otherwise you have to use Ctrl + C to copy them out . You can choose all lines by selecting the first and while holding Shift, select the last. Then you can Ctrl + C to copy all of them out.

Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.

Chinaphonearena said:
Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.
Click to expand...
Click to collapse
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.

I think that avoiding flashing droidboot and recovery, and making sure file hashes match, everything should be fine.

Same issue
---------- Post added at 04:05 AM ---------- Previous post was at 04:02 AM ----------
cde2006 said:
Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks
Click to expand...
Click to collapse
I put my 64gb sd in my ZF2 that I originally partitioned for my LG Optimus Pro and I moved a bunch of apps to the SD with link2sd and the first time I rebooted, the same screen with the USB logo and a full progress bar showed up. It won't recognize any fastboot or adb commands even though the ASUS adb is showing up in device manager. Nothing else shows up. In devices and printers I get Moorefield. The phone randomly reboots and goes back to the same screen over and over and each time the asus adb disappears from device manager and then returns. I found a guide on the zenfone 5 that looks promising, using the intel flash tool, however it requires the ZenFone 2 raw firmware files and I can't find them... Hopefully someone could help me salvage my ZF2 cuz I was really beginning love the phone... Thanks ahead of time for anyone that looks into this for me!

i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.

sry, had only the files for V5. I will load down and put it here.

boot error and bricked zenfone 2
i have same problem with my phone please send moorefields or other intel based boot drivers.. tanks

please tutor how to fixed it, thanks for advice

cde2006 said:
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.
Click to expand...
Click to collapse
Lol @ "got sequence on this forum" and "more safe proven way."
You didn't read the instructions carefully enough and made a big mistake as a result. The correct sequence was given. You just didn't read it carefully. Lesson learned.
Hopefully you can unbrick it.

No offense, but this type of thing is what happens when people just copy/paste and don't understand what they're doing.
What you did was overwrite the fastboot partition each time you flashed. You flashed a 2GB system img on top of your fastboot partition. This probably seemed like it locked up and you either unplugged or turned it off. This likely caused a corrupt partition.
Reading is key when you do anything with your phone.
This is perfectly safe. This is the way it works for all devices. It has nothing to do with the files or the phone. This was 100% user error. Simple as that.

ze550ml hard brick
http://forum.xda-developers.com/zenfone2/help/zenfone2-ze550ml-hard-bricked-t3148174#post61657126
my ze550ml hard brick too. please help me
sorry for bad english.

hardbrick zenfone 2
konsolen said:
i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.
Click to expand...
Click to collapse
Hello, i have the same issue with my zenfone 2, I download the firmware files from Asus website, but the Intel flash tool can't found a flashable image file. My question is to, if you have the firmware files that send it to me?

same issues here please help,

same issues here please help,

[Q] Random Reboots on ZF2 4gb/32gb

Hello,
Anyone facing issues of random reboots on ZenFone 2 4gb/32gb model?
If yes, how to come over this issue?
Mine is a WW version. Bought it from FlipKart. Un-rooted.

Suhas_JS said:
Hello,
Anyone facing issues of random reboots on ZenFone 2 4gb/32gb model?
If yes, how to come over this issue?
Mine is a WW version. Bought it from FlipKart. Un-rooted.
Click to expand...
Click to collapse
You could back up any important information you had, format the phone and then sideload either the stock firmware (available from Asus) or the pre-rooted images available here.

kibmikey1 said:
You could back up any important information you had, format the phone and then sideload either the stock firmware (available from Asus) or the pre-rooted images available here.
Click to expand...
Click to collapse
Just hard reset or complete wiping of cache, dalvik, data, root and then reload the stock/pre-rooted ROM?

It's what I would try.
Download these, if you don't have them:
Intel USB Driver
ADB & Fastboot Tool
and either stock ROM from Asus or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.

Thanks a ton mate
Sent from my ASUS_Z00AD using XDA Free mobile app

i suspect this has alot to do with android 5.0. asus needs to work on getting 5.1 to the device.

Suhas_JS said:
Thanks a ton mate
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
what rom did you install? latest or stock?
did you follow the step one or alternative??
please help me i got the same problem.

kibmikey1 said:
It's what I would try.
Download these, if you don't have them:
stock ROM from Asus[/URL] or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.
Click to expand...
Click to collapse
following the process i have install stock rom... with adn sideloader... this version is not suporrted so download 1.0.32 form other place.. sucessfully install the rom . don't know yet the problem is solved or not.. but i will post update after using .. thanks man.. atlest after viewing lots of form alon with asus whole day.. following urs sucessfully able install the rom with adb sideload. thanks a lot. now hope it will work fine.
---------- Post added at 06:54 PM ---------- Previous post was at 06:48 PM ----------
kowsar684 said:
following the process i have install stock rom... with adn sideloader... this version is not suporrted so download 1.0.32 form other place.. sucessfully install the rom . don't know yet the problem is solved or not.. but i will post update after using .. thanks man.. atlest after viewing lots of form alon with asus whole day.. following urs sucessfully able install the rom with adb sideload. thanks a lot. now hope it will work fine.
Click to expand...
Click to collapse
no problem is still there ...... should i install pre root rom???
---------- Post added at 07:01 PM ---------- Previous post was at 06:54 PM ----------
what is the difference between stock ROM and pre root ROM???

can't install stock rom. how to flass

kibmikey1 said:
It's what I would try.
Download these, if you don't have them:
Intel USB Driver
ADB & Fastboot Tool
and either stock ROM from Asus or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.
Click to expand...
Click to collapse
Thanks a million man.
This saved me instead of sending back the phone rto newegg after a failed cache format.
Repped!!!

I have folowed all step successfuly but reboots are still there, i can't do **** about them, mostly happen installing / updating apps and playing games, sometime it's just random, listening music.

more ideas about why it's happen?

I have recently had a spate of random reboots. Thought it was flip cover causing problem, still the same. Its the 32Gb, 4Gb ram, 1.8mhz model.
Phone is stock, all updates applied and problem happening much more after last update, 22.

sandozer said:
I have recently had a spate of random reboots. Thought it was flip cover causing problem, still the same. Its the 32Gb, 4Gb ram, 1.8mhz model.
Phone is stock, all updates applied and problem happening much more after last update, 22.
Click to expand...
Click to collapse
If you have been using the phone as an ordinary consumer, I would suggest to get a replacement if that's within your entitlement. Just my personal opinion.
Sent from my ASUS_Z00AD

Anyone get a random shutdown with the 2.19.40.20 firmware? Happened to me overnight/this morning, at 98 to 96% charge. First time this has happened with this device.
No last_kmsg to share, so will keep a watch on it for now...
Edit: happened a second time, this afternoon. Maybe I will upgrade to 2.19.40.22, or at least install TWRP to see if I can grab a last_kmsg (if I can find it) to see what's going on..

chooks06 said:
If you have been using the phone as an ordinary consumer, I would suggest to get a replacement if that's within your entitlement. Just my personal opinion.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Yes, good advice ! Unfortunately I bought it in Hong Kong at the beginning of April. It has had no problems, seems like the last update upset something. Maybe 5.1 will do me a favour . . . .

@sandozer..5.1 will do a lot of good for a lot of people

sandozer said:
Yes, good advice ! Unfortunately I bought it in Hong Kong at the beginning of April. It has had no problems, seems like the last update upset something. Maybe 5.1 will do me a favour . . . .
Click to expand...
Click to collapse
If you have not tried resetting the phone, it may be worth a try, though painful to start setting up all over again. You can try using the stock ASUS back up app to do your back up..
Sent from my ASUS_Z00AD

I am on 22 and have random reboots as well?

I had 2 random reboots on the 2gb/16gb version, but I think it was USB cable related. I'd plug the phone into the car and do something fast and then lock it, POOF! Reboot. It hasn't happened in awhile though and I believe I did an OTA update afterwards.

Please help

I was trying to clear my cache, and do a factory wipe in recovery mode, but now all I get is an android robot lying down with the word error. It just keeps booting to this screen every few seconds. When I try to get back into recovery mode, I get a message saying there is no path to cache, and then it starts booting to the robot error again. I can still hold down power and vol+, and get options for normal, recovery, power off, ect, but it won't boot. Do I have a 300 dollar brick? I hope not. Any help would be greatly appreciated. This my 1st time on any phone other than samsung/htc, so I'm a little unfimilar with the process. I guess i'm so used to ODIN being my easy out. Waiting patiently.

I don't know if this can help... Maybe you can try to flash the image file in fastboot mode (vol up + power) since you are still able to go into that mode.
Just download these 4 files:
1. Recovery Image
2. Boot Image
3. DroidBoot Image
4. System image pre-root
refer to this: http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
or.. if you can go to Recovery mode (press a few times vol up + power in screen android lying down with error message) and do adb sideload to your device...
Just give it a try...

aatjitra said:
I don't know if this can help... Maybe you can try to flash the image file in fastboot mode (vol up + power) since you are still able to go into that mode.
Just download these 4 files:
1. Recovery Image
2. Boot Image
3. DroidBoot Image
4. System image pre-root
refer to this: http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
or.. if you can go to Recovery mode (press a few times vol up + power in screen android lying down with error message) and do adb sideload to your device...
Just give it a try...
Click to expand...
Click to collapse
I will give it a go in the morning when I have a clear mind. I'm so frustrated that I screwed something up, that I can't think straight right now. I will literally try anything at this point.

gmanhad said:
I will give it a go in the morning when I have a clear mind. I'm so frustrated that I screwed something up, that I can't think straight right now. I will literally try anything at this point.
Click to expand...
Click to collapse
Connect via ADB and after typing "fastboot devices" and checking it's connected you then type "fastboot erase cache" This worked for me but I had no cache errors, just a misunderstanding of how to get get the recovery menu....
I also erased & flashed recovery, boot, droidimg & system after erasing them. Just be careful with the droidimg though as this apparently is what allows you to get to fastboot mode and if you flash a corrupt image you will have a $300 paperweight...

aatjitra said:
I don't know if this can help... Maybe you can try to flash the image file in fastboot mode (vol up + power) since you are still able to go into that mode.
Just download these 4 files:
1. Recovery Image
2. Boot Image
3. DroidBoot Image
4. System image pre-root
refer to this: http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
or.. if you can go to Recovery mode (press a few times vol up + power in screen android lying down with error message) and do adb sideload to your device...
Just give it a try...
Click to expand...
Click to collapse
maybe I'm missing it, but I can't find a system.img file. I have the other 3.

i fastboot flashed boot, recovery, and droidboot.img's, and when I reboot the phone this is all that happens. I can still get into fastboot mode, but that's it. the pics below show what i get when i try to get into recovery mode

gmanhad said:
maybe I'm missing it, but I can't find a system.img file. I have the other 3.
Click to expand...
Click to collapse
You can download it from the Mega drive mentioned in that thread.
But here you go buddy => https://mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
gmanhad said:
i fastboot flashed boot, recovery, and droidboot.img's, and when I reboot the phone this is all that happens. I can still get into fastboot mode, but that's it. the pics below show what i get when i try to get into recovery mode
Click to expand...
Click to collapse
Have you try to flash system image?

aatjitra said:
You can download it from the Mega drive mentioned in that thread.
But here you go buddy => https://mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Have you try to flash system image?
Click to expand...
Click to collapse
i have that dl link, but which file do i flash? do i need to unzip the system w root file, or download each of the system files? thanks 4 all the help

try this it worked for me and others,steve...Connect your device and open adb
In adb Type
Code:
fastboot erase cache

gmanhad said:
i have that dl link, but which file do i flash? do i need to unzip the system w root file, or download each of the system files? thanks 4 all the help
Click to expand...
Click to collapse
Yes, you need to extract system.img from .zip. Just double click it and extract.

flashed system.img and everything says it went through in fastboot command prompt, but as soon as I reboot the phone, it just goes directly to the android robot lying down with the word error. I guess i just wasted $300......

mongonexus said:
try this it worked for me and others,steve...Connect your device and open adb
In adb Type
Code:
fastboot erase cache
Click to expand...
Click to collapse
U R the man bro. I'm back in business. This is why i love android. The community is awesome!!!

You guys are the best
Thanks to everyone who took time out of their holiday weekend to help me out with my issue. I am back up and running. WOW, I really thought I screwed it up big time. I knew that as long as I could boot to fastboot mode, that there might be hope. I truly appreciate it guys.

gmanhad said:
U R the man bro. I'm back in business. This is why i love android. The community is awesome!!!
Click to expand...
Click to collapse
your very welcome , thanx xda , its killer group of members and devs for hooking you up, i was was stuck there for 2 days and was so disappointed that i pfhucked something up, came here found others had same issue and dispensed proper comands for adb and 3 minutes my new phone was up and cranking,

gmanhad said:
U R the man bro. I'm back in business. This is why i love android. The community is awesome!!!
Click to expand...
Click to collapse
Mate, I told you to do that on the 4th post.... You should at least read the replies when people try to help...

gmanhad said:
i have that dl link, but which file do i flash? do i need to unzip the system w root file, or download each of the system files? thanks 4 all the help
Click to expand...
Click to collapse
Assuming you have ZE551ML so you need to use Z00A.
In the folder Z00A_WW_2.17.40.12, you will see some file with name Z00A_WW_2.17.40.12_system_w_root.z01, z02, z03, z04, z05 and .zip
Download all of them into the same folder on your PC. Once done, open the file with .zip extention and extract it. You'll get system.img with size around 2GB. That is system image file you need.