Related
Hi there,
I have a problem that my LG will not boot the device is stuck at the logo, I've also done a hardware reset but the process also depends on the logo proof and 10min not happened.
In the download mode, I'm not coming.
About the fastboot mode I try to start TWRP, but it appears the TWRP logo and nothing else happens.
How did you manage to get it to this point? What did you do before it didn't boot anymore?
Also, if you manage to get adb access somehow you can just reflash the recovery again
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
So you cant enter download mode or recovery? And you cant turn on phone?
No download mode is not only possible fastboot mode. If I we want to install Recovery in fastboot mode, shown below
Command: fastboot flash recovery recovery .img
Error on LG G3:
Error: Command never completed
Error: Auto CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror:Command completed with errors
Failed to send stop command
Failed Writing block @1
SourceCoder said:
No download mode is not only possible fastboot mode./QUOTE]
Could you please explain this.
Is comma missing somewhere?
Click to expand...
Click to collapse
The following screen appears:
lgg3root.com/wp-content/uploads/2014/08/howto-unroot-unbrick-lgg3-2-690x492.jpg
And then immediately this screen:
android-hilfe.de/attachments/root-custom-roms-modding-fuer-lg-g3/345262d1415303724-lg-g3-kein-download-modus-mehr-img_20141106_093950.jpg
This screen does not appear:
androidheadlines.com/wp-content/uploads/2014/07/LG-G3-Download-Mode-AH-1.jpg
SourceCoder said:
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
Click to expand...
Click to collapse
Something does not compute in this at all. SuperSU should not have caused your phone to brick like that.
Is there something else you are not telling us about how your phone was set up? Were you doing anything before you updated SuperSU? This looks like a case of where you flashed the wrong image on your phone, if you ask me.
SuperSU is not phone specific, so I'm having a hard time believing SuperSU did this.
Something else must have happened that you are not telling us. You need to lay out in order, everything you did to your phone up to the point of updating SuperSU.
Also, SuperSU asks how to update: normal or via recovery. Which way did you choose? Either one shouldn't matter, but it's a start.
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1
SourceCoder said:
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1
Click to expand...
Click to collapse
Did you flash the correct laf.img file for your model of phone? If not, that could be part of it. What model of the G3 are you using and where exactly did you obtain the laf.img file from?
SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
SourceCoder said:
SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
Click to expand...
Click to collapse
Well, there you go. I have NO idea for what version of the G3 that thread was for. The guy never states which version it is. You do not, repeat, do NOT flash anything to system, boot, etc for this phone unless you know for sure it's for YOUR model of the G3. There are various models of the G3. For example, mine is the Verizon model (VZ985). There is an AT&T model (DS855), and numerous others, especially for those overseas. I would not and should not flash the DS855 boot image to my VS985 boot image. It will brick the phone as you have found out the hard way from what I can tell.
You just flashed something you have NO idea which version it was for. You may have completely bricked your phone. I'm not entirely sure, but you need to find the correct stock images for your phone and flash them back.
You need to go here and figure out which model of G3 you have:
http://forum.xda-developers.com/showthread.php?t=2791269
After that, you need to go and find the correct stock image files and flash those back onto your phone. Since this are NOT img files, you cannot fastboot flash them. You muse use either KDZ or TOT files depending on which ones are available for your model of phone:
http://lg-firmware-rom.com/
or
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
Then, you have to use the correct tool to flash these files depending on if they are KDZ or TOT file:
http://forum.xda-developers.com/showthread.php?t=2785089
Hopefully, flashing back to the correct stock image will fix you up. However, you better make darned sure which model of phone you have BEFORE you even attempt it. Once you figure out which model of G3 you have, post here and ask. Otherwise, you could bork your phone up even worse to where it may not be recoverable. Hopefully, it's not at that state right now.
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Again, did you verify with the link you posted for the image file that it was indeed for YOUR model of your phone? If not, you probably have bricked it.
You need to go and follow the links I posted which tell you how to flash back to stock.
There was no reason to go into fastboot mode for SuperSU. I don't know why you felt you had to do that.
Also, the second link you posted has the thread pretty much deleted. The OP said he was incorrect in what he posted (whatever it was I don't know since he deleted it), so it was removed due to it not working as stated.
Go back to the links I posted to flash back to stock on your model. If what you say you have is the European model, then this would be the KDZ file you want:
http://storagecow.eu/Xda/LG G3/Stock/Europe Common 16G D85510A_00.kdz
I would verify for sure that is what your phone is before continuing or else, you'll bork your phone up even worse than it is already.
The boot image you flashed is probably for the Korean version of the phone and that's why everything is messed up.
If you are not sure on how to do this, then you might want to find someone near you who does.
Just remember, just because a post says it's for the G3 doesn't mean it's specifically for YOUR model of the G3. You need to verify for sure that it is. Most have the model number in the thread's title.
LG G3 Fastboot
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
[1700] fastboot mode started
razaaliarain said:
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
Click to expand...
Click to collapse
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
_narisha_ said:
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
Click to expand...
Click to collapse
But now i am stuck again on fastboot mode and this time i was not rooted and did not had twrp installed so now when i try to use the "fastboot boot twrp.img " my device will reboot and then will be stuck on twrp logo on the screen
I have the same problem...
I ran stock OTA update 20f, since a couple of weeks ago. While I had my phone on the table and it was runing voice recorder soft it restarted once and then after a couple of minutes again. This time it never booted but stuck at the LG screen.
Never rooted, never installed anything other than the OTA 20e and 20f updates. I have not flashed anything to the phone other than the official OTA.
Doesn't boot to anything other than fastboot. Recovery starts but after confirming twice it reboots and stuck still.
If I boot to Download Mode it goes to fastboot, if I wait long enough on regular boot that only shows the LG logo it will eventually go to fastboot.
Running "fastboot.exe boot openrecovery-twrp-2.8.4.0-d855.img" gives me the same error messages, stuck at the TWRP logo screen. I found the ADB port is connected but when running "adb devices" it says "LGD855..... offline". I didn't enable ADB before the device crashed and I can't enable it in TWRP because it doesn't start properly.
I have the 32GB D855 European unlocked. I belive this is hardware problem and will send it for repairs.
SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
gee2012 said:
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
Click to expand...
Click to collapse
That's right. I tested to boot Philz recovery and it freezes at the text.
Mine says actually:
Error: Command never completed
Error: Auto CMD12 error
Error: Command never completed
Error: Command timeout error
Failed to send stop command
Failed reading block @ 1
mmc read failure misc 2048
The CMD12 is according to emmc spec a "Stop command".
So this is a hardware fault and not a software one.
So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
TMartin said:
So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
Click to expand...
Click to collapse
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
xunholyx said:
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
Click to expand...
Click to collapse
I can get into TWRP but it won't mount the data partition. Are you saying I should try flashing another ROM the normal way through TWRP or try the sideload option? I tried to fastboot flash stock recovery. It says it worked but then continues to boot to TWRP.
I can get into bootloader. I'm pretty sure it's a 4.16.401.x ROM but I'll have to double check when I get home. I've tried to flash stock everything but it you know how it restarts through the process? When it restarts, it seems to want to restart to OS.
I'm about 99% sure the OS is there because it boots into Android but only gets me to the "Decrypt storage" screen.
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?
[Unsolved] Phone sent to HTC service.
Hey Guys,
I'm back again and this phone is breaking my heart. My phone is still stock from the last time I had a similar problem.
My battery died, when I plugged it back in and hit the power button it powered up as far as the splash screen and hangs there.
When I go into recovery mode the log says
Supported API: 3
handle_cota_install: install cwpkg to /cache/cota/cwpkg.zip
handle_cota_install: install cwprop to /cache/cota/cw.prop
E:Fail to open file: /sys/devices/platform/android_usb/host_mode
Write host_mode error handle_cota_install: Can't mount /sdcard
I've tried clearing the cache/partition and rebooting but I'm in work and don't have access to save my info so I don't want to factory reset yet. Is there any thing else I can do or am I stuck with doing a factory reset ..... AGAIN!
Jamballs said:
Hey Guys,
I'm back again and this phone is breaking my heart. My phone is still stock from the last time I had a similar problem.
My battery died, when I plugged it back in and hit the power button it powered up as far as the splash screen and hangs there.
When I go into recovery mode the log says
Supported API: 3
handle_cota_install: install cwpkg to /cache/cota/cwpkg.zip
handle_cota_install: install cwprop to /cache/cota/cw.prop
E:Fail to open file: /sys/devices/platform/android_usb/host_mode
Write host_mode error handle_cota_install: Can't mount /sdcard
I've tried clearing the cache/partition and rebooting but I'm in work and don't have access to save my info so I don't want to factory reset yet. Is there any thing else I can do or am I stuck with doing a factory reset ..... AGAIN!
Click to expand...
Click to collapse
If you can get into bootloader or download mode try "fastboot erase cache"
Thanks for the suggestion thicklizard, I'll give it a shot when I get home and update the post.
Thanks!
?
You unlock Bootloader ,make Root or Soff ? Can you use warranty in HTC.
If u can go to Bootloader you can use Erase option ,or if is RUU for yours Htc verion you can flash to stock.
I dont know what is in without root and unlocked bootloader :/
I always have Unlocked bootloader ,Soff ,root and latest TWRP
If u have TWRP you can flash Rom for yours Firmware version
Sorry for my ENG
Well after a good few hours at the phone last night I'm still in the same position. My hands are a bit tied as I still have S-On but I don't know if I can even get S-off while stuck where I am. I can get in to bootloader/download/ recovery. Have tried Thicklizards suggestion above which didn't work, have also tried a hard reset. Also tried to flash a new recovery image but the error which popped up told me that I can't flash that partition with S-On. I have tried to run a RUU but I may have downloaded the wrong one, also the error which came up during install was that the battery was below 30%, I'm assuming that's an issue as I'm trying to run it from bootloader, I've tried looking around and I can't find any resource that would tell me if trying to run the RUU from bootloader would cause that error. Ive also tried to run the RUU as an image on the SD card but I got an error 99 that said I had a failure with the RU. I'll be away from my laptop for 2 days now but when I get back I'll try this RUU from Nikolay82, I don't know how I missed it before http://forum.xda-developers.com/one-m9/help/htc-one-m9-3-35-401-12-ruu-installer-t3318517. The only issue is that this is an upgrade to 3.35.401.12 and I'm already at 3.35.401.12. The struggle continues.
If your bootloader is locked you can't flash a recovery, is it looked or unlocked?.
but you can try to flash the OTA, still you're with 3.35.401.12, by Nikolay82's method...
bzhmobile said:
If your bootloader is locked you can't flash a recovery, is it looked or unlocked?.
but you can try to flash the OTA, still you're with 3.35.401.12, by Nikolay82's method...
Click to expand...
Click to collapse
Bootloader is unlocked, I did actually try to lock it again using fastboot oem lock and it failed with "unknown command". I think I'll send it away for repair this time instead of fixing it myself again, but that means my phone will be gone for who knows how long.
For the fastboot command, do you have open terminal windows from the fastboot folder?
bzhmobile said:
For the fastboot command, do you have open terminal windows from the fastboot folder?
Click to expand...
Click to collapse
Hi BZH yes I was opening the terminal from the fastboot folder. Fastboot devices command and a few other fastboot commands were working but any fastboot oem command wasn't working.
still searching where the mistake is coming from ???
Jamballs said:
Bootloader is unlocked, I did actually try to lock it again using fastboot oem lock and it failed with "unknown command". I think I'll send it away for repair this time instead of fixing it myself again, but that means my phone will be gone for who knows how long.
Click to expand...
Click to collapse
Could try fastboot oem relock
Thanks for that Thicklizard, That didn't work either I'm afraid. The phone is off to HTC service now so we'll see what comes of that. I'll mark this thread as solved ... or rather unsolved.
Hello!
I'm trying to fix a LG G4 that goes straight into fastboot mode when it's powered up.
I've tried several things:
1. Holding power + volume down. It goes into recovery mode but when I click yes to restoring everything, it automatically takes me back to the same fastboot screen.
2. I've installed Android-SDK and updated drivers when I plugged in the phone. When I put in 'adb devices', there is nothing. When I put in 'fastboot devices', the serial number shows up. The bootloader is locked and when I put in 'adb reboot bootloader', it says 'error: no devices/emulators found'. Then I tried both 'fastboot oem unlock' and 'fastboot flashing unlock', it gives me: 'FAILED <command write failed <Unknown error>>.
3. I've downloaded TWRP but it obviously does not do anything right now with my errors.
I unplugged the phone from the computer and now it says 0% battery, it does not charge.
I'm really confused and lost at what to do. Any help would be appreciated.
Thank you in advance!
JennV123 said:
Hello!
I'm trying to fix a LG G4 that goes straight into fastboot mode when it's powered up.
I've tried several things:
1. Holding power + volume down. It goes into recovery mode but when I click yes to restoring everything, it automatically takes me back to the same fastboot screen.
2. I've installed Android-SDK and updated drivers when I plugged in the phone. When I put in 'adb devices', there is nothing. When I put in 'fastboot devices', the serial number shows up. The bootloader is locked and when I put in 'adb reboot bootloader', it says 'error: no devices/emulators found'. Then I tried both 'fastboot oem unlock' and 'fastboot flashing unlock', it gives me: 'FAILED <command write failed <Unknown error>>.
3. I've downloaded TWRP but it obviously does not do anything right now with my errors.
I unplugged the phone from the computer and now it says 0% battery, it does not charge.
I'm really confused and lost at what to do. Any help would be appreciated.
Thank you in advance!
Click to expand...
Click to collapse
i dont know what fast boot means or is. but couldnt you just enter download mode and flash KDZ?
raptorddd said:
i dont know what fast boot means or is. but couldnt you just enter download mode and flash KDZ?
Click to expand...
Click to collapse
Hi! I did try to follow the guide to KDZ on here but I can't get into download mode. I'm literally stuck; the phone simply starts up right into fastboot mode.
I need to know the history. What model. What were you doing to get stuck in fastboot.
TheMadScientist420 said:
I need to know the history. What model. What were you doing to get stuck in fastboot.
Click to expand...
Click to collapse
Hi! It's the H810 model. My dad was watching YouTube videos when his phone suddenly turned black and went into fastboot. The phone was originally from Wind Mobile but my brother unlocked it through the web. My dad uses ChatR. In order to start up the phone now, I have to plug it to a wall outlet before it starts up into fastboot. When I plug it into my computer directly, it says 0% battery but it does not charge up.
I know a fastboot usb cable force charges. But it sounds like a more sisnister problem if its like u say. Id sent it to lg for waranty on bootloop issue
LG-H810 Qualcomm 9008
TheMadScientist said:
I know a fastboot usb cable force charges. But it sounds like a more sisnister problem if its like u say. Id sent it to lg for waranty on bootloop issue
Click to expand...
Click to collapse
Sir i ended up flashing wrong kdz to H810 and after flashing it become dead state (Qualcomm9008) mode i successfully recovered it by following this guide https://forum.xda-developers.com/att-g4/general/unbrick-9008-mode-h810-100-method-t3555231/page10
but now it won't go To DOWNLOAD MODE it goes To fastboot mode instead i've tried deffirent LAF.imges but no success !
here is what is on the phone screen when i connect it to pc!
(Product name-msm8992_spr_us
Variant msm8992_p1_spr_usToshiba 32GB
bootloader version -
basevand version -
serial number- LGLS991b77257e1
signing production
secureboot disabled
lock state-locked
can u help?
please (thanx)
And another one who converted his device by using qfil..
Sent from my LG-H815 using XDA Labs
JennV123 said:
Hello!
I'm trying to fix a LG G4 that goes straight into fastboot mode when it's powered up.
I've tried several things:
1. Holding power + volume down. It goes into recovery mode but when I click yes to restoring everything, it automatically takes me back to the same fastboot screen.
2. I've installed Android-SDK and updated drivers when I plugged in the phone. When I put in 'adb devices', there is nothing. When I put in 'fastboot devices', the serial number shows up. The bootloader is locked and when I put in 'adb reboot bootloader', it says 'error: no devices/emulators found'. Then I tried both 'fastboot oem unlock' and 'fastboot flashing unlock', it gives me: 'FAILED <command write failed <Unknown error>>.
3. I've downloaded TWRP but it obviously does not do anything right now with my errors.
I unplugged the phone from the computer and now it says 0% battery, it does not charge.
I'm really confused and lost at what to do. Any help would be appreciated.
Thank you in advance!
Click to expand...
Click to collapse
Try to type into the terminal: 'fastboot continue'. This should make the system start up.
JennV123 said:
Hello!
I'm trying to fix a LG G4 that goes straight into fastboot mode when it's powered up.
I've tried several things:
1. Holding power + volume down. It goes into recovery mode but when I click yes to restoring everything, it automatically takes me back to the same fastboot screen.
2. I've installed Android-SDK and updated drivers when I plugged in the phone. When I put in 'adb devices', there is nothing. When I put in 'fastboot devices', the serial number shows up. The bootloader is locked and when I put in 'adb reboot bootloader', it says 'error: no devices/emulators found'. Then I tried both 'fastboot oem unlock' and 'fastboot flashing unlock', it gives me: 'FAILED <command write failed <Unknown error>>.
3. I've downloaded TWRP but it obviously does not do anything right now with my errors.
I unplugged the phone from the computer and now it says 0% battery, it does not charge.
I'm really confused and lost at what to do. Any help would be appreciated.
Thank you in advance!
Click to expand...
Click to collapse
Just type "fasboot reboot" ..it should boot normally or just press power button for 10 seconds and release