So I recently bought the Korean LG G3 (F400) and the first thing I did was rooting it, which was a breeze. Of course to root it I needed to install the LG Mobile Drivers, which I did and were working completely fine. Then I decided to take a little risk and attempt to flash CWM recovery (I did not know that I need to unlock the bootloader first or BUMP! the device) and well, flashed it the same way I flash stuff on my previous Samsung phones.
So now, when I try to boot the phone, I get the LG Logo and goes through with the boot animation, but after a little less than a second the boot animation fails and I get a black screen + the LED flashing blue and green and the phone remains like that. I tried factory reset but after I click yes it shows the LG logo then goes into a black screen (without the boot animation) + LED flashing blue and red.
So I tried finally going into download mode and attempting to return it to stock via LG Flash Tools, and like I said before the drivers were installed, but when I connect the phone to the PC it gives the message "Drivers were not successfully installed" and the LG Flash Tools fails to detect the phone. I checked within Device Manager and it says the LGE MTP device "cannot start".
So I'm pretty much stuck with a phone that doesn't boot, can't flash anything via adb or flash tools and no recovery installed. Can anyone suggest anything I can do to get this beast back up?
Try using this method http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Related
Hello, I just got my g3 and decided to root it. I used stump root to do that, then installed twrp. I flashed the latest cyanogenmod rom and everything was good. this morning i opened the phone and now get a loop of
unfortunatly the process phone has stopped
I looked it up and the fix seems to be flashing the boot img to my phone via fast boot.
this is where I am having isues. i have fast boot on my computer, but I am not able to get my phone into fastboot mode, I tryed holding vol up while plugging in the usb, but that just turned the phone on normally. I tryed a few other things that I really don't remember, but now I can get the phone to a screen that says Firmware Update. butfast boot wont recognize my phone is there when I type fastboot devices. please help, I'm not very good with this so any instructions need to be dumbed down and maybe a pic of what my phone screen should look like would help
tekkaman_01 said:
Hello, I just got my g3 and decided to root it. I used stump root to do that, then installed twrp. I flashed the latest cyanogenmod rom and everything was good. this morning i opened the phone and now get a loop of
unfortunatly the process phone has stopped
I looked it up and the fix seems to be flashing the boot img to my phone via fast boot.
this is where I am having isues. i have fast boot on my computer, but I am not able to get my phone into fastboot mode, I tryed holding vol up while plugging in the usb, but that just turned the phone on normally. I tryed a few other things that I really don't remember, but now I can get the phone to a screen that says Firmware Update. butfast boot wont recognize my phone is there when I type fastboot devices. please help, I'm not very good with this so any instructions need to be dumbed down and maybe a pic of what my phone screen should look like would help
Click to expand...
Click to collapse
download the drivers for your phone(google it)
Other than being rooted my N7105 was stock before I decided to install CM via the Windows Installer. It failed once so I restarted the device and computer on the programs suggestion. Second time it seemed to be installing fine getting past the installing recovery step before I left the room. On my return it had failed again and suggested I try a different USB port or computer and the install would pick up right where it left off.
Except it hasn't.
The Installer isn't even detecting my device anymore. I'm stuck with a little blue fellow on my screen. Rebooting just brings me back to the same screen and when I remove the battery the phone reboots as soon as I replace it. I can boot into download mode but trying to boot into recovery just brings me back to the blue dude.
I'm not really sure what to do. I've tried using a Toolkit but get stuck at the "Waiting for USB debugging to be turned on" part. I've looked at Heimdall but aren't really sure where to start or if it could even help.
Any suggestions?
kimbies88 said:
Other than being rooted my N7105 was stock before I decided to install CM via the Windows Installer. It failed once so I restarted the device and computer on the programs suggestion. Second time it seemed to be installing fine getting past the installing recovery step before I left the room. On my return it had failed again and suggested I try a different USB port or computer and the install would pick up right where it left off.
Except it hasn't.
The Installer isn't even detecting my device anymore. I'm stuck with a little blue fellow on my screen. Rebooting just brings me back to the same screen and when I remove the battery the phone reboots as soon as I replace it. I can boot into download mode but trying to boot into recovery just brings me back to the blue dude.
I'm not really sure what to do. I've tried using a Toolkit but get stuck at the "Waiting for USB debugging to be turned on" part. I've looked at Heimdall but aren't really sure where to start or if it could even help.
Any suggestions?
Click to expand...
Click to collapse
try to flash stock ROM using Odin, you might have to try different versions.
Just enter download mode, connect usb and flash
Hi. I have a problem with my LG G3 D855. Yesterday I messed up and soft-bricked my Marshmallow, but I figured it out and now I'm back on stock Marshmallow, but I lost my root and, appearently, custom recovery (I had TWRP).
The device boots normally, but when I use adb:
Code:
adb reboot bootloader
the device just restarts and loads into "normal" Android desktop. Sometimes it boots into safe mode.
When I try to boot into recovery using:
Code:
adb rebood recovery
the phone turns off and LED starts blinking red and blue, as if it was bricked. I can't access them using button combinations either.
I tried using LG One Click Root, but it ended with big fat #FAIL.
From what I understood, I'm going to have to re-flash the boot.img file, but where do I get one? And how do I flash it later?
as i said much times before use kingroot to root and then autorec MM d855 you can do this from phone and you dont need a pc
My LG G3 is and international D855 and is unable to enter recovery, with the phone going black after the twrp logo shows for a few seconds. The phone has no OS installed because I was going to flash a custom rom so there are only bootloops when booting up the phone. Entering download mode is not any good either because a message appears saying secure boot error and the phone goes black with only the LED flashing Red and Blue, I tried going back to stock with fastboot but in the process I lost the ability to enter fastboot, is there any hope
I'm hoping somebody can help and I would be extremely greatful, Cheers
If you can't access Download mode or fastboot mode.you have to do this as in thread.
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
So far, I decided since my tablet was running slower than it did when I first got it, to reset it. And since I was doing that, might as well unlock the bootloader.
Well, I unlocked the device, attempted to install TWRP, then got the remote failed error, unknown command. Apparently you have to install it via flashify or whatever. Anyhow...
I rebooted the device, but now, all it does is go into recovery, shows the android robot on its side for a split second, then starts flashing white then black on the screen. The only way to stop it is to pull off the battery connector.
The LG mobile tool can see it in download mode, send it the latest kdz image or whatever, works, but still goes back to the same error - boots to recovery then hangs.
Is there a way to fix this? Trying to get it to boot a recovery img didn't work. Erasing all data seemed to have done nothing.
Did you ever unbrick it...?