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.
Hi, I use a Asus Zenfone 2 ZOOAD
A few days ago I decided to flash the CM13 (Marshmallow) ROM on my phone. My phone is rooted. Anyway, when I tried to enter the recovery mode using the bootloader screen ( I selected "recovery mode" by using volume up and down) I couldn't do it. So, I decided to use the adb method. I'd already done it to put the Xposed Framework. So I connected my phone to my Windows 10 laptop and tried to enter recovery. Same story. It got stuck on the bootloader. I even tried flashing the custom twrp recovery; twrp is getting installed (or so it shows on the command window) but I can't enter the recovery mode. Worst part is I can't even boot into my normal screen. When I connect my phone to my laptop, it's detected but when I try to use adb it says "device not found". I am able to execute the fastboot commands though. But all in all, I can't get out of the bootloader.
When you are in bootloader you must choose recovery then agreed (ON OFF Button) then when it reboots : "VOLUME UP + ON/OFF" *click several time*
Here it is : http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I've been trying to flash TWRP recovery to my rooted LG G3 D855 (running 4.4.2 KitKat). I used the "Bump" method (thread) since I don't have an unlocked bootloader.
I tried the ADB method in that thread, I tried the Flashify method, and I tried the Official TWRP App. Each time, the recovery flashed correctly. But when I attempted to reboot into recovery (using the method in the linked thread, or in the case of the apps, they prompted me to reboot into recovery), my phone didn't bring up TWRP recovery or even the stock recovery. It just brings up "fastboot mode started". It's not stuck though, it boots normally when I pull the battery and power on.
I also separately tried rebooting it into fastboot mode with it plugged into my computer. When I entered "adb devices" into the command prompt, the device came up. Then I rebooted it into fastboot mode and entered "fastboot devices" - then nothing came up. I entered some other fastboot commands and it said "< waiting for device >". So it appears I can't issue normal fastboot commands either.
Any thoughts on how I can succesfully flash TWRP? Thanks.
i have installed my TWRP via this app -- https://ulozto.sk/!lisJevpDG1oS/recovery-d722l-apk
try hope itll help you
Well, somehow you failed to install it. Upgrade to LP (preferably v21C) and try this
I installed this rom: (https://forum.xda-developers.com/g4/development/h815-nougat-stock-t3659860) the correct way through TWRP and having an unlocked bootloader and then the rom worked well, but then i thought i still had the TWRP as a recovery so i tried to enter the recovery mode by pressing power button+lower volume button. afterwards i clicked twice yes. so the phone rebooted and the rom didn't work anymore. So tried to find a solution by searching XDA forums and the internet. Since my previous version was MM i found LGUP which could restore the phone to its previous ROM. however i am now having issues with LG UP. i tried several methods:
the 1st one was: from https://forum.xda-developers.com/g4/...mm-lp-t3249803 with the H81520D_00_0115.kdz file and the DLL files which came with the software itself. This always led me to 25% after which LG UP would crash and give a "error code = 0x2000 invalid command response at system". then i tried a different DLL from: https://forum.xda-developers.com/g4/...-file-t3586220 #6 which led me to have the error at 11%.
the 2nd one was: from https://forum.xda-developers.com/g4/...-h815-t3673777 #6-#11 so tried this method with these DLL files and by reinstalling LG UP and the driver, also by using the H81520p_00_0314.kdz file. but now i have the issue that LGUP gets stuck at 4% "USB connection established" and will automatically close the program and windows will show me that "LGUP has stopped working".
the 3rd one was: using LG bridge and hoping it will reset the phone. but nothing it just says that the phone has no software issues and that i have the latest software which is H81529a.
Lastly i tried to get flash twrp-3.1.1-1-g4.img through fastboot and was able to flash the recovery by using "fastboot flash recovery twrp-3.1.1-1-g4.img", however i was not able to get into the recovery because when i typed "fastboot boot twrp-3.1.1-1-g4.img" i would get an error (can be seen in the picture). so i tried to enter the recovery manually by pressing power button+lower volume button, and releasing the power button for 1 second and the pressing the powerbutton again, afterwards i clicked twice yes in the white screen, but this got me to download mode and not into TWRP (can be seen here: https://www.youtube.com/watch?v=xai6_8T8BgI)
I am now stuck and don't know what to do, and was hoping you guys could help me? I am using a PC with WIN 10 and i can boot into Fastboot mode and Download mode
Rmegaxx said:
Lastly i tried to get flash twrp-3.1.1-1-g4.img through fastboot and was able to flash the recovery by using "fastboot flash recovery twrp-3.1.1-1-g4.img", however i was not able to get into the recovery because when i typed "fastboot boot twrp-3.1.1-1-g4.img" i would get an error (can be seen in the picture). so i tried to enter the recovery manually by pressing power button+lower volume button, and releasing the power button for 1 second and the pressing the powerbutton again, afterwards i clicked twice yes in the white screen, but this got me to bootloader and not into TWRP (can be seen here: https://www.youtube.com/watch?v=xai6_8T8BgI)
I am now stuck and don't know what to do, and was hoping you guys could help me? I am using a PC with WIN 10 and i can boot into Fastboot mode and Download mode
Click to expand...
Click to collapse
Suggest you post your issue re: TWRP to steadfasterX's thread: [RECOVERY][h815/h811][OFFICIAL][MM][LL] TWRP 3 touch recovery [2017-06-21]
https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
after reading through the OP thoroughly and seeing if any of the member's posts match your issue.
steadfasterX has proven very helpful to numerous members with issues.
Hello,
My H815 phone is stuck in fastboot mode.
Whenever i press the power key the phone goes directly into fastboot mode.
I wanted to reset the phone using the phone's menu but straight after that the phone booted directly in fastboot mode and it's now stucked.
I believe that the bottery should be dead as well.
The host has it's bootloader uncloked, however i cannot install TWRP as i receive a message command: unknow in ADB when i try to install the recoevery.
I tried different USB cables and different ports of the same |laptop, currently runnin windows 7 with all the drivers.
Looking for are feedback on how to install the recovery and get rid of the command:unknown error
gogobaba said:
Hello,
My H815 phone is stuck in fastboot mode.
Whenever i press the power key the phone goes directly into fastboot mode.
I wanted to reset the phone using the phone's menu but straight after that the phone booted directly in fastboot mode and it's now stucked.
I believe that the bottery should be dead as well.
The host has it's bootloader uncloked, however i cannot install TWRP as i receive a message command: unknow in ADB when i try to install the recoevery.
I tried different USB cables and different ports of the same |laptop, currently runnin windows 7 with all the drivers.
Looking for are feedback on how to install the recovery and get rid of the command:unknown error
Click to expand...
Click to collapse
Search for FWUL from Steadfasterx.
download-> flash->connect-> open Comannd-> type "fastboot flash recovery recovery.img" or "fastboot reboot system"
Which command are you using for installing TWRP in ADB?