Hey GuyZ. I'm FuZZ moZr, I've recently picked up a Lg G3 Vs985. Yesterday I rooted it, and unlocked the bootloader with the bump method. After that I saw on the play store G3Tweaks. I downloaded it, and saw I needed xposed module to use it. So o went got it then it rebooted my phone after i installed it within the app. After my phone rebooted it now just sits at the verizon logo all day. I had twrp installed, but it won't let me boot into it since that happened. I have my STOCK ROM backed up so if o could just get it to boot into it I'll be good. I could restore my phone Without losing everything, and having to re-root and all that. My question is, is it possible to install twrp back onto my lg g3 via my laptop.? You know using cmd. I have adb tools, and latest drivers installed. That's how I unlocked the bootloader. Is this possible. Also I would just redo it all, but my WiFi has got throttled, and it would take FOREVER to download the stock firmware. Please someone help me. My nexus 5, note 3, HTC one, and z2 has no issues. I only had the phone for two days I really need it back on today. Plus it was my remote... Now I don't have one. .
Hello all, I just purchased a new LG V410 and decided to root it using TWRP with flashify. I've done this before with other phones with much success and followed the instructions precisely. I was able to root the tablet successfully, but when using the flashify install the TWRP custom recovery the phone rebooted into fastboot.udc and I have been stuck ever since. I can no longer go into download mode or recovery mode and when I try it comes back to the black fastboot screen with errors. I have to do a hard reset using Power and vol down just to restart the tablet, which otherwise works fine and is detected by my pc and the minimal adb fastboot command interface. However, the mobile support tool doesn't see the phone and I have downloaded drivers several times with no change in status. Please advise as I think that I may have fully bricked my tablet. Any help is appreciated.
Hold the volume up and plug in the usb to get to download mode properly, as well this http://forum.xda-developers.com/g-pad-10/general/kdz-lg-g-pad-7-0-v410-t3224867. Unbricked mine with that method. Hope that helps!
Just to let you know why it bricked and you often can't just use Flashify or anything else to merely flash TWRP anymore, its because of the locked bootloader. On other LG devices such as the VS985 G3 and the VK810 G Pad 8.3, we have to use old KitKat bootloaders (from the same device) to be able to get into TWRP. At least on the VS985, the KitKat bootloader was still locked, but it was vulnerable to a method to get around it called "BUMP", so anything that boots - kernels, TWRP etc, has to be BUMP'd in order to work, but still requires the BUMP-vulnerable bootloader.
So I rooted my phone by installing the rooted 13b img. And went to install xposed framework and apk. I completed all the steps found here (http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593), and now it is stuck on the android logo....suggestions on what do do from here?
A little more detail: After completing steps verbatim, it would fail to install framework. I then read somewhere else that you need to uncheck not only auto mount but the mount option, as well. I tried that and it seemed like it must have worked as it didn't immediately fail and reboot. However, it got stuck on the android logo and after an hour or so I realized there was problem. I have pulled the battery and rebooted several times. I can boot into download mode, but cannot get it to fully boot. Since I could get it into DL mode, I used LGUP to install the 24C MM update (as I didn't have the 13B on my computer). But the result is the same...stuck on the Verizon logo even after a successful install of 24C.
Is this a case of the hardware failure that others are experiencing or is this software related? I see a lot of people with bootloop issues and mine seems to be similar but different. Mine does get past the LG screen to the next screen, but even installing a stock kdz doesn't seem to help...
UPDATE:
Well I downloaded the stock 13B kdz and flashed it via LGUP and it somehow managed to boot. It looked like it was going to be stuck on the Verizon landing page but after about 10 seconds or so it completed boot up. I have now installed the rooted 13B image and made a backup img. I might try again to install xposed framework - fingers crossed it doesn't screw up this time...
Use hyleton's 'LG G4 Stock Firmware (Go Back to Stock) KDZ & TOT Method' that uses LGFlashTool2014.exe and do a CSE Flash - this will wipe all your data though
SnitchyB said:
Use hyleton's 'LG G4 Stock Firmware (Go Back to Stock) KDZ & TOT Method' that uses LGFlashTool2014.exe and do a CSE Flash - this will wipe all your data though
Click to expand...
Click to collapse
Thanks, I'll look into that. I was hoping that using LGUP to reflash to stock would do it...but I guess I have to remove whatever the flash tool put on my phone when trying to install the xposed framework...
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
If you can reach download mode you could try reflashing back to stock then starting again.....Hope you get yours fixed - Sorry to say this but mine did a very similar thing only 24 hours before you posted!!! Only mine was on stock FW and was in use at the time - I've now had to swap it as valuebasket who sold me the phone have ceased trading. If yours is a UK model you may be able to get it replaced under warranty - believe that LG guarantee their phones for 2 years and a ruling by the European court said that flashing a custom rom doesn't invalidate any warranties.
I have the same exact issue, I also flashed the latest CM14 nightly and cannot get the device to boot any rom.
I have even tried flashing stock rom but I get the same problem.
From what I have read, the bootloop issue happens once the device boots but I don't seem to be getting that far.
Any ideas?
Ran into the same problem 3 days ago. This is the first time I have encountered a non-revertible issue in 3 years as a cyanogenmod user. This changes my opinion on how safe it is to make use of a custom ROM. I tried to wipe everything, reinstall TWRP, change TWRP with another recovery, reinstall a safe NAND backup of mine.....nothing.....it went into boot loop. Before I read this post, I was convinced my phone encountered the infamous G4 bootloop problem.....now I see there are other examples, so it shouldn't be the case. Long story short, I had to check my device in at the LG assistance, with 25 days as time forecast.
The guilty nightly was 20161205.
I have never seen anything like this...
This has solved it for me - I installed LG Bridge and flashed the factory firmware using the tool. Now it seems I'm back on stock but at least it's working.
got mine working. I had to install LGUP and flash stock ROM. Once flashed I installed CM14 and I am back up and running again.
I tried LGUP but it could not recognize the device while this was looping.....a bad experience......
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. I did a cyanogenmod update from within cyanogenmod, which just booted into twrp, then I manually installed the update zip that cyanogenmod had downloaded, then it always boots into twrp. I wonder if initiating the update from within cyanogenmod was the cause. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Well. Mine got stuck in bootloop for the second time today. What is going on? In between the two bootloops I had one good update with CM. Using TWRP 3.0.2.1. Steps to reproduce failure: updating CM from within CM, it autoreboots into TWRP and after that nothing happends, no autoinstall. Then after a manual install of the new CM the bootloop starts.
Resolve the problem:
* Install LGUP 8994 DLL Ver 0 0 3 23, Install LGUP Install Ver 1 14, get the latest KDZ
* Get the phone into download mode with usb cable and after that in firmware update mode
* Startup LGUP and choose refurbish and select the kdz file.
* After that you can boot into your stock LG firmware again, reinstall TWRP an CM. If you want so.
Read that it is advised to manual update cm from within TWRP. TWRP will get an update in the future to solve this bootloop problem.
iankelling said:
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. After a cyanogenmod update, it always boots into twrp. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Click to expand...
Click to collapse
I second that. Same issue and neither LG Up nor LG Bridge will recognize my device. Looking in device manager there are no serial interfaces. Do I need a special driver that provides a com port for a phone in recovery or fastboot mode?
---Edith 2016-12-12: Found a solution for my issue:
The phone has to be in _download_ mode, not in recovery or fastboot. After realizing that I have to boot the phone in a different manner, it will be recognized by LG UP.
Here is how to boot the pone in download-mode:
- Power off your LG device.
- Press and hold Volume Up button.
- Connect your device to PC with a USB cable while holding the Volume Up button.
- You’ll boot into download mode with “Firmware Update” written on top of the screen.
Now everything is fine again.
croclacrimae said:
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
Click to expand...
Click to collapse
I was able to get out of that by also wiping by-name/misc. Don't do that, though, because then your wifi mac address will get messed up and you'll spend all day looking for a permanent fix for that.
I suggest reflashing a stock KDZ using LGUP, as others have said. You can get the usb drivers from LG Bridge.
I will release a fix for that soon. Check the twrp thread for updates on this.
Hi
I also have this problem
I installed cm-14.1-20161201-NIGHTLY-h815 successfully and was running it for almost 2 weeks without issues, today I updated to cm-14.1-20161213-NIGHTLY-h815 from cmupdater and I have been ending up in recovery every time I rebooted.
I tried flashing the latest cm recovery and reflashing the rom, with full wipes but no luck.
Full steps of recovering would be appreciated (for example, there are comments about flashing the latest stock rom, but a link to this rom would be helpful)
Thanks
Good news regarding this:
http://forum.xda-developers.com/showpost.php?p=70082901&postcount=213
The above will fix TWRP bootloop issues as well and I also released a first h811 version which should allow installing CM etc as it should.
Keep in mind that this is a BETA and not an official TWRP release.
Please report back in the above thread!
.
Does your twrp beta really fix the boot loop even it is already happening. What do I have to wipe? I have not managed to get out of the boot loop despite intalling it.
Is using using LG Up to flash to the stock rom really the only option?
Edited 2017-01-25 2:45 pm:
Well, sometimes you just have to be patient. Powered down the phone and when th H815 restarted CM did boot. Great. :good:
Hey, I just want to share a small detail, possibly a fluke that helped me overcome the bootloop.
So...I started with a fresh, stock H815, I don't quite remember the firmware version..it was something like version "20g"..
OK, I looked up several guides and tried to get the newest stable versions of each tool. I went through with the official bootloader unlock, then moved on to rooting: Kingroot didn't work for me so I went on installing twrp in fastboot mode so I could afterwards install supersu and root.
I got there eventually but first I was stuck in bootloop - kept ending up in twrp interface. I found the 2 dd commands but those didn't work for me as the msm_sdcc folder did not exist, but instead there was a "f9824900.sdhci". Tried to overwrite this one ...but as others have stated as well, it didn't work.
At that point, I had nothing to lose, I was starting to accept that I had soft-bricked my precious G4 so..I went on installing the DU 10.6 7.1.1 rom and the stock gapps, wiped dalvik, rebooted and held my breath...not literally
About 12 minutes later, after an endless red, spinning logo, my shiny ping pong paddle showed me a different screen, a fresh start welcome screen .
Almost 24h / 10-12 reboots (twrp included) / 70+ apps installed and removed later, the new OS holds around 2G ram average, a bit better battery life, smoother transitions, flawless navigation, flush streaming over both 3G/LTE & 2.4/5 G wifi.
FYI the reboots were intended, wanted to see consistency in boots - we're in the green . Now testing long term stability with moderate/high usage.
There is 1 aspect I noticed, there are a couple of contexts when the interface burps (several menus, various situations, never in apps) and resets back to homescreen...but I think that's more of a launcher topic than an OS one.
Other than that, so far I'm happy with the mod.
Hope my experience helps others that might be in the same spot I was or at lest boosts their confidence to try out a decent idea they might be pondering.
So, long story short, I followed this tutorial: www . htcmania. com/showthread.php?t=1024045 (remove the spaces in w.h and .com) and it didn't go very well.
I flashed TWRP and SuperSU as told, using both download links (TWRP 2.8.7 & SuperSU 2.46), and my phone got stuck in a bootloop at LG bootloader unlocked logo. I recovered my phone by using LG Bridge and after that, when i tried to enter TWRP using the phone keys, it resulted in a factory data reset (no TWRP after recovery, didn't know that). I then followed the exact same steps but using what I thought was the lastest SuperSU archive (SR5-SuperSU-v2.82), flashed the archive and when finished, TWRP asked me to flash it again (so I did), then rebooted, passed LG bootloader unlocked logo, got into LG animation and... Bootloop again, so I recovered again with LG Bridge but I din't attempted to enter TWRP because this time i knew it wouldn't work and I ended it there, reinstalling all apps and configuring my phone as I had it before my unsuccessfull attempt. I continued using my phone as usual but sometimes, when I enter Pokemon Go, it says that it couldn't log in and that my phone's OS is not supported. As I said, the app does this sometimes whenever it wants, so I researched a bit and turns out it doesn't work with rooted android devices (I didn't know that). I knew my root attempt failed so I downloaded and app called Root Checker and checked: Root status-Not rooted; SafetyNet Status-Failed. I don't know what should I do know, last time I rooted my phone was a Sony Xperia XL and it wasn't so tricky.
I asked for advice in the forum and got no answer, so here I am, hoping for a solution. What I want is to have a permanent custom recovery, a rooted device and to have SafetyNet status passed. Any ideas, hints or whatever? Please, help