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.
Hey guys,
I need your advice/help.
I have googled and searched XDA for 5 hours total now and I couldn't find a solution, so please be lenient if someone has already answered this question.
So I was browing along with my D855 32gb with CM13 on it. Then it crashed, which it did sometimes, so I pulled the battery and restarted. But instead of working flawlessly again like it did so many times it kept on crashing after my restarts (5 at least).
So I went to the twrp recovery, erased cache and dalvik cache and restarted.
It went into a bootloop (stuck at CM logo for hours)
Tried to get to the recovery again, doesn't work, stuck at LG logo. DAMN!
So I tried with download mode, but it starts fastboot mode instead.
So I tried booting twrp in tethered mode with
fastboot boot recovery.img
Stuck at TWRP logo...
I decided to go back to stock completely and try to unbrick it this way, but I need download-mode to flash the tot/kdz.
So I tried the following:
Tried flashing matching laf.img this way:
fastboot flash laf laf.img
Error: [1185970] Error: command never completed
[1185970] Error: Auto CMD12 error
[1185970] Error: command completed with errors
[1185970] Error: command never completed
[1185970] Error: command timeout error
[....]
[1191000] Failed Writing block @1
Tried BOOTING laf.img like suggested elsewhere with
fastboot boot laf.img
Error: (like above) then
"Continuous splash enabled, keeping panel alive."
and stuck there forever
So I tried erasign the laf partition before flashing it..
ends with
"MMC erase failed" error.
A "fastboot oem check_mmc" yields it being stuck there until I unplug it then it says "never completed: too many links"
So my guess is that the MMC broke (since it bricked after erasing cache.. which is very strange in my eyes) and therefore the phone is trash..
Do you guys agree? Can I try something else?
Thank you very much for all the suggestions!
i have a very simillar problem
just fully reinstall your phone if that doesnt work ist broken that simple
And how would you do that with just fastboot, no download mode, no recovery, and flashing/booting laf/recovery not working?
try charging itif it charges (gets to the battery charging screen) you still have a partially working bootloader if not it is a paperweight, try the qcom unbrick tool but with mmc not working it will be impossible
Me to, I have the same problem. Me phone freezed a couple of times, then I tried to reinstall CM and it failed and from then I can't even got to Recovery or Download mode. Only LG logo.
My Samsung Galaxy Nexus is stuck in this boot loop, where it first boots normally and then after about 10 seconds shuts down and reboots. I have tried installing a stockrom using adb sideload, but it returns "E: signature verification failed". I researched the problem and apparently verification can be disable using RomManager. I tried to flash the app using adb install, but this returns "error: closed". The device is displayed as a sideload device when i type in "adb devices", but the Nexus Root Toolkit does not detect any adb fastboot devices, although it does detect that a phone is connected.
Model Type according to Nexus Root Toolkit:
Galaxy Nexus
GSM/HSPA+
Android *.*.* Any
I am frankly at a loss, as i have no prior experience with rooting etc., so i would be grateful for any advice.
The same problem started, too. I've tried every method, but the problem is not solved. What should we do ?
Try adb reboot bootloader or adb reboot recovery. If adb doesn't accept any reboot commands, try going to the bootloader and get into recovery from there (or, install or boot a custom recovery) and install a different ROM.
I think I bricked my G3 :/
I tried usual methods but couldn't get into recovery or download mode, then a few days ago I realized I could get it into this fastboot mode by holding volume up and plugging into USB as you would normally do to get into download mode but you have to hold up for a minute or so (it shows the download mode icon for a few seconds and then goes to fastboot) when in fastboot it connects to the computer and shows in device manager as "android device" and the phone says "processing commands" So I tried to follow this guide http://forum.xda-developers.com/showthread.php?t=2785089 to return it to stock, but I couldn't get it to show up in the LG software.
I read some forum posts about fastboot mode and found that by using the command "fastboot boot twrp.img" (the recovery image I downloaded) in command prompt it would send it to the phone and the phone would display some info and then reboot into TWRP, from here I tried to install a correct rom but the installation starts and there are some errors and then it hangs. I also tried the command "fastboot flash recovery twrp.img" but it fails. This is as far as I have got with it.
It came to me in this condition but the previous owner said he was running Cyanogen and it was working fine until he tried to update it with a nightly build. I suspect he might've tried to install the wrong rom for the phone or the rom was corrupt.
ou could try to revive the phone doing a testpoint and then use boarddiag tools (look in xda thread).
Here is how to make a testpoint: http://forum.xda-developers.com/showpost.php?p=65002893&postcount=17
So I screwed up and neglected to flash copypartitions-AB.zip and now my g7 play is stuck in a locked fastboot.
I have tried this thread, pulled out an old laptop with Windows 7 32-bit for it. https://forum.xda-developers.com/t/...der-stuck-in-fastboot-unable-to-boot.3917792/
LMSA doesn't detect the phone. So I try RSD Lite, and I get "Failed flashing process. 2/29 oem fb_mode_set - > Phone returned FAIL."
Try XML to BAT converter, it spits out a bunch of "permission denied" or "invalid partition name" errors.
Tried to unlock this locked bootloader, start with "fastboot oem get_unlock_data" and it spits out "read datablock error". So I just tried to use the same unlock key I used before installing Arrow OS, but it says "<bootloader> feature disabled".
Afterwards I tried this thread: https://forum.xda-developers.com/t/need-a-loader-file-to-unbrick-moto-g7.3938342
I made my sdcard, put it inside the phone and booted it up to the same exact thing, nothing actually changed. I realized after this I needed to be in EDL mode for it, and I can't find any fastboot command to access EDL mode. I tried a modified fastboot that said it would let me reboot to EDL mode, but it just threw an unknown command error.
Found this thread: https://forum.xda-developers.com/t/ultimate-guide-how-to-unbrick-your-moto-g6-plus.3862927/ except I downloaded the blankflash for g7 play from lolinet.com. But the blankflash just hangs on "waiting for device". Tried on Windows 7, Windows 10 and Linux. So now I'm just stumped on this. Does anyone have any suggestions to fix my g7 play?
EDIT: For anyone having this issue, I fixed it. There actually IS a command to enter EDL mode- "fastboot oem blankflash". No mention of it in the blankflash thread unfortunately but I finally found it. You can probably use either the blankflash method or loader method. Though I still couldn't get blankflash to work on Windows 10, it worked on a Linux Mint live usb