Verizon LG G3 with 24b firmware. Yesterday it started lagging massively, refusing to open most apps that weren't google, random reboots where it gets stuck on the red Verizon splash page that either resolve after 10 minutes or I pull the battery. Wiped the cache and did a factory reset. The phone is in the process of restoring stuff but now NOVA launcher freezes/quits. Any idea what this is?
I'm probably just going to attempt to upgrade until 46a or whatever is the most current since factory reset did not help and erased all my data already anyway.
Flash the 10B TOT after you move stuff you want to keep from your internal storage (if you have anything). TOTs flash more partitions than KDZs and can fix problems that nothing else can.
I had a weird problem months ago and no wiping, KDZ or ROM I flashed helped. The TOT did and after talking to @xdabbeb, that's when I found out there's a reason TOTs can help when nothing else does.
Then root with the Stump app on XDA, use TWRP Manager from the Play Store to flash TWRP, wipe Cache, Dalvik /ART and Data, flash the ROM that you want and appropriate Bootstack.
35B and 47A ROMs like both of @xdabbeb 's work great, and better than 24B and 23C.
I went ahead and upgraded to 6.0 on 47a with the instructions you gave me in another threat a while back, since I have everything backed up. Now if I can get Xposed to work..
APeter001 said:
I went ahead and upgraded to 6.0 on 47a with the instructions you gave me in another threat a while back, since I have everything backed up. Now if I can get Xposed to work..
Click to expand...
Click to collapse
Great! Shouldn't be too hard with Xposed these days, they've taken care of incompatibilities with LG weather apps, etc.
Related
First - want to thank ALL THE DEVs that put in who knows how much time and effort to make us users happy!!!
My phone:
LG G3 running android 5.0.1 on VZW
Build: LRX21Y
Software Version: VS985 23C
I got this phone off Ebay, as I wanted to keep the unlimited data plan through VZW and also wanted a more updated phone that could be rooted. I am replacing a Razr HD that I had rooted, but that phone was so underpowered it was crazy. Anyhow, I gathered all the root methods and tried to make sense of it all; apparently there has been an explosion of smartphones over the last few years.......... First two days I thought this phone could not be rooted, but I started to see some important parts in these forums related to build numbers, software versions, and android versions, and what root methods seemed to work best, or not at all. What eventually worked for me was getting the right USB drivers for the LG G3 for my Win-7 system. The older driver actually worked for me, the LG VZW United WHQL v2.14.1 - I was then able to at least get the One-Click root to see my device, but I did have to connect/reconnect a few times, and also had to do this procedure twice - the first time the device rebooted back to login and not the download mode. I saw where some were saying you needed to switch between PTP an MTP, but I found that once you found the right one (Think that was MTP) you could just disconnect the USB and reconnect. After the second reboot using One-Click root, the device did go into the download mode and finished the root process. Did a root verification and that confirmed the phone is rooted properly.
I swapped the SIM this morning into the LG G3 and powered on and still have root; however, Verizon is bugging me to update the system software and I am delaying that until I get some clarity on WHAT is getting upgraded, and if I will still have root afterwards (I'm thinking probably not), or if there is a way to "protect" the root I currently have on the device before I do the system upgrade from VZW.
I was hoping someone(s) here who understand more about the VZW upgrades and how that affects root on the LG G3s. THANKS!!!
Kevin
Hi Kevin. Good name (mine too)!
Welcome to the Verizon LG G3 section!
1. The update is 24B, which fixes a few important problems with 23C. Personally, I recommend it.
2. First, since you're rooted, trying to apply the 24B OTA will fail because it'll recognize that your system partition is changed.
3. The easiest way for you to keep root and yet be on 24B is to:
a. Use LG Backup in Settings/Backup & Reset to back all of your data and system settings to an external MicroSD card.
b. Search the Play Store for:
Code:
autorec VS985
This'll install TWRP v2.8.6.x for you. Then update to 2.8.7.0 using a TWRP flashable zip available in the non-variant specific Developement or non-Development subsection - I forget which - of the LG G3 forum.
c. Make a TWRP nandroid backup of your current setup.
d. You can try dirty flashing JasmineROM 8.0 to get updated to 24B, be nearly completely stock as it just adds a few conveniences unless you flash other stuff after. If dirty flashing didn't work well, wipe Data, System, Cache & Dalvik, flash JasmineROM 8.0 then once booted use LG Backup to restore the backup you made in step a above.
kd1966 said:
First - want to thank ALL THE DEVs that put in who knows how much time and effort to make us users happy!!!
My phone:
LG G3 running android 5.0.1 on VZW
Build: LRX21Y
Software Version: VS985 23C
I got this phone off Ebay, as I wanted to keep the unlimited data plan through VZW and also wanted a more updated phone that could be rooted. I am replacing a Razr HD that I had rooted, but that phone was so underpowered it was crazy.
Click to expand...
Click to collapse
Welcome Kevin to the world of the G3. You won't be disappointed. I myself also came from the Razr HD and mine was unlocked (bootloader exploit before it was patched). But the G3 is worlds above the Razr HD (which still was one of my favorites phones).
As @roirraW "edor" ehT stated, you have a couple of options, but I will say, Jasmine ROM with the SkyDragon 4.2 kernel is great. You are still using the stock image which is what I prefer due to the stock camera that comes with it. Anything else (Google camera, AOSP camera) just pales in comparison to the G3 stock camera.
If you do decide to just flash the Jasmine ROM, then you can do as roirraW stated which is to install the autorec VS985 app which will do all that is necessary to get you up and running with TWRP which will allow you flash custom kernels and ROMs (very similar to having an unlocked bootloader). Once you have TWRP, you can go and download the latest Jasmine ROM and then the SkyDragon kernel. Here are the links to the ROM and the kernel (the kernel gives even better battery savings):
Jasmine ROM 5.0: http://forum.xda-developers.com/showpost.php?p=61844561&postcount=4128
SkyDragon Kernel 4.2: https://www.androidfilehost.com/?fid=24052804347775438
Then do the following:
Run the autorec VS985 app (if not already done) to install TWRP
Copy the Jasmine ROM and SkyDragon kernel files to your external SD card (or internal if you don't have an external SD card installed)
Use either LG Backup or TitaniumBackup and backup all of your downloaded apps and settings.
Backup anything located on the internal SD card (photos, music, etc). This will get wiped later on.
Boot into TWRP (download Quick Boot app from Play Store and select "Recovery" in the app. Much easier this way)
Wipe system, data, cache and dalvic. You don't need to wipe internal which would wipe your internal SD card as well as the internal memory.
Flash the Jasmine ROM. This takes some time and it may appear to be doing nothing. Mine took about 5 minutes, so be patient.
If you want to debloat some of the stock apps, you can download and flash the debloating zip from the Jasmine ROM thread I linked you to but it's not necessary. You can also do it later on if you wish.
Reboot into the ROM. Be patient. It sits at the LG logo for awhile and it may appear hung, but it's not. Give it about 5 minutes.
Go to settings and do a factory reset. This needs to be done within the ROM. This WILL wipe your internal SD card, but you should have backed up anything important as stated in step 4 above.
Reboot again and profit in the glory of Jasmine ROM. Now you can use Quick Boot to boot back into recovery (TWRP) and flash the SkyDragon kernel.
Now really profit in performance and battery life that you won't get with pure stock 24B.
roirraW "edor" ehT said:
Hi Kevin. Good name (mine too)!
Welcome to the Verizon LG G3 section!
1. The update is 24B, which fixes a few important problems with 23C. Personally, I recommend it.
2. First, since you're rooted, trying to apply the 24B OTA will fail because it'll recognize that your system partition is changed.
3. The easiest way for you to keep root and yet be on 24B is to:
a. Use LG Backup in Settings/Backup & Reset to back all of your data and system settings to an external MicroSD card.
b. Search the Play Store for:
Code:
autorec VS985
This'll install TWRP v2.8.6.x for you. Then update to 2.8.7.0 using a TWRP flashable zip available in the non-variant specific Developement or non-Development subsection - I forget which - of the LG G3 forum.
c. Make a TWRP nandroid backup of your current setup.
d. You can try dirty flashing JasmineROM 8.0 to get updated to 24B, be nearly completely stock as it just adds a few conveniences unless you flash other stuff after. If dirty flashing didn't work well, wipe Data, System, Cache & Dalvik, flash JasmineROM 8.0 then once booted use LG Backup to restore the backup you made in step a above.
Click to expand...
Click to collapse
Thank you! I appreciate the tips and technical stuff. I've been catching bits here and there about this TWRP, and it seems there are a lot of people that are having issues with it, for whatever reasons. I was thinking that I might not need it unless I wanted to flash to a custom ROM, which I have not done, as I'm not sure how that would work on my carrier (VZW), or if that even matters. Again, I really appreciate the info and I will definitely do some more reading/studying what I need to do next; that would be pretty cool if I could keep root and still have the 24B.
Kevin
kd1966 said:
Thank you! I appreciate the tips and technical stuff. I've been catching bits here and there about this TWRP, and it seems there are a lot of people that are having issues with it, for whatever reasons. I was thinking that I might not need it unless I wanted to flash to a custom ROM, which I have not done, as I'm not sure how that would work on my carrier (VZW), or if that even matters. Again, I really appreciate the info and I will definitely do some more reading/studying what I need to do next; that would be pretty cool if I could keep root and still have the 24B.
Kevin
Click to expand...
Click to collapse
Well, you can definitely keep root on 24B, but probably the main reason people are having issues with TWRP is they are trying to use it incorrectly on LP. That's why the app riorraW suggested will take care of ensuring your phone is set up correctly to use TWRP, even on 24B. But, as I stated, if you are going to run 24B, I would suggest going to Jasmine ROM and then use the SkyDragon kernel. You'll get much better battery life out of it. I can attest to that.
In any case, welcome once again to the G3 family.
Thx for the welcome and great info!
iBolski said:
Welcome Kevin to the world of the G3. You won't be disappointed. I myself also came from the Razr HD and mine was unlocked (bootloader exploit before it was patched). But the G3 is worlds above the Razr HD (which still was one of my favorites phones).
As @roirraW "edor" ehT stated, you have a couple of options, but I will say, Jasmine ROM with the SkyDragon 4.2 kernel is great. You are still using the stock image which is what I prefer due to the stock camera that comes with it. Anything else (Google camera, AOSP camera) just pales in comparison to the G3 stock camera.
If you do decide to just flash the Jasmine ROM, then you can do as roirraW stated which is to install the autorec VS985 app which will do all that is necessary to get you up and running with TWRP which will allow you flash custom kernels and ROMs (very similar to having an unlocked bootloader). Once you have TWRP, you can go and download the latest Jasmine ROM and then the SkyDragon kernel. Here are the links to the ROM and the kernel (the kernel gives even better battery savings):
Jasmine ROM 5.0: http://forum.xda-developers.com/showpost.php?p=61844561&postcount=4128
SkyDragon Kernel 4.2: https://www.androidfilehost.com/?fid=24052804347775438
Then do the following:
Run the autorec VS985 app (if not already done) to install TWRP
Copy the Jasmine ROM and SkyDragon kernel files to your external SD card (or internal if you don't have an external SD card installed)
Use either LG Backup or TitaniumBackup and backup all of your downloaded apps and settings.
Backup anything located on the internal SD card (photos, music, etc). This will get wiped later on.
Boot into TWRP (download Quick Boot app from Play Store and select "Recovery" in the app. Much easier this way)
Wipe system, data, cache and dalvic. You don't need to wipe internal which would wipe your internal SD card as well as the internal memory.
Flash the Jasmine ROM. This takes some time and it may appear to be doing nothing. Mine took about 5 minutes, so be patient.
If you want to debloat some of the stock apps, you can download and flash the debloating zip from the Jasmine ROM thread I linked you to but it's not necessary. You can also do it later on if you wish.
Reboot into the ROM. Be patient. It sits at the LG logo for awhile and it may appear hung, but it's not. Give it about 5 minutes.
Go to settings and do a factory reset. This needs to be done within the ROM. This WILL wipe your internal SD card, but you should have backed up anything important as stated in step 4 above.
Reboot again and profit in the glory of Jasmine ROM. Now you can use Quick Boot to boot back into recovery (TWRP) and flash the SkyDragon kernel.
Now really profit in performance and battery life that you won't get with pure stock 24B.
Click to expand...
Click to collapse
I must say that these rooting and root protection procedures have gotten extremely complex..... but that's technology I suppose. Thank you very much for the well documented steps, which I will definitely take serious look at as I piece together my own plan. I don't seem to have too much issues with the stock rooting, but when it comes to the flashing stuff, I get a little hesitant; I just don't want to make the wrong move and wind up with a paperweight......
Gotta say that my old RazrHD was by far my most well liked smartphone device; I started on a DroidX, then the X2, and finally the RazrHD. I'm moving away from the "Moto" devices cuz they seem to be going the way of Apple - you can't add SD storage cards; you get what they give you and I don't like that. I think they are trying to push you into cloud storage or something. As for my new best, awesome smartphone device................ the LG G3 is pretty damn awesome, considering there is a G4 model out there.
Kevin
So I admit I may not be completely up to date on the latest "little things" with this 35B ota...
I sort of just took it, updated, stayed on my roms and went with it.
Well, I think that's gotten me two hard bricked G3s. My first one I thought was done so I went and bought another G3 for cheap because I like this phone... got to setting it up and it wasn't long and that one was hard-bricked too.
What is it that we're doing to cause these phones to hard brick? I'm confused, honestly. I'm not sure what it is that I am doing to cause it to hard brick. I found one thing I know I did that's possible - wiping all the partitions before flashing the 35b bootstack... so I know now not to do that again.
What do you guys think?
I would strongly suggest trying the hard brick recovery tutorial posted. I thought I truly bricked my phone but I was able to get it back. My screen wouldn't even turn on... Only reason I knew it was trying to power on was the vibration at start up. Now it's perfect. It does require you to take apart the phone though, but it really is pretty easy.
One common cause of what's actually a soft brick is flashing the 35B bootstack before flashing either JasmineROM or SkyDragon because both of those have some older partitions which will conflict with the bootstack's 35B partitions. Flashing the 35B bootstack after its fine.
Even when it appears it's turning on but the screen stays black doesn't mean it's not on. Many people on here who soft bricked their G3 this way we still able to put it in Download mode and use LG Flash Tool 2014 to flash a KDZ, even though the screen stayed black. Flashing the KDZ restores it all back to normal.
CaptainElwood said:
I would strongly suggest trying the hard brick recovery tutorial posted. I thought I truly bricked my phone but I was able to get it back. My screen wouldn't even turn on... Only reason I knew it was trying to power on was the vibration at start up. Now it's perfect. It does require you to take apart the phone though, but it really is pretty easy.
Click to expand...
Click to collapse
I have now done this tutorial four or five times now. I'm trying to investigate certain causes of these hard bricks. So I am now an expert at hard brick recovery for this device! Haha.
roirraW "edor" ehT said:
One common cause of what's actually a soft brick is flashing the 35B bootstack before flashing either JasmineROM or SkyDragon because both of those have some older partitions which will conflict with the bootstack's 35B partitions. Flashing the 35B bootstack after its fine.
Even when it appears it's turning on but the screen stays black doesn't mean it's not on. Many people on here who soft bricked their G3 this way we still able to put it in Download mode and use LG Flash Tool 2014 to flash a KDZ, even though the screen stayed black. Flashing the KDZ restores it all back to normal.
Click to expand...
Click to collapse
I was thinking it had a lot to do with the bootstack actually. I was flashing the bootstack before flashing JasmineROM. However I was flashing it after I had wiped data, cache, and system partitions. But no system installed. I know that can't be right, obviously.
droidian1441 said:
I was thinking it had a lot to do with the bootstack actually. I was flashing the bootstack before flashing JasmineROM. However I was flashing it after I had wiped data, cache, and system partitions. But no system installed. I know that can't be right, obviously.
Click to expand...
Click to collapse
The bootstack isn't the problem, just to be clear. The problem is the conflicting older partitions in JasmineROM and SkyDragon. That's why you need to flash the 35B bootstack AFTER flashing either ROM. You can flash it before just as long as you would flash it again after, but obviously, there's no reason to flash it before if you're going to flash it after.
Wiping isn't the problem either. I always wipe Data, Cache, Dalvik and System.
What exactly are you saying can't be right? Flashing a ROM flashes System, that's where the ROM goes.
Long story not-so-short.
Due to upgrading to G5 I decideed to sell my G3.
I was running CM13 (one of the latest nightlies), 21C modem and TWRP 2.8.6, so it seemed like a good idea to go back to stock-ish firmware.
To do so, I installed stock ROM using this method with 21A modem.
Everything worked fine. I had a working LG ROM.
Then I had this great idea of mine to install even 'stocker' firmware with LG UP. (I couldn't do that while running CM13 - LG UP didn't recognize the phone)
And that was the moment when everything fell apart.
It took a few minutes for LGUP to 'install' the new firmware. Qhen phone finally rebooted, I got stuck in TWRP. There was no chance to boot a system.
I tried this fix and it didn't help.
I also tried to restore my nandroid backup (i made it on clean CM13) and it didn't work either.
Then, as an idiot I thought "How hard can it be?" and went crazy: wiping, formatting, trying to flash new modem (this tme 30B hybrid), boot, sytem and doing probably all the things I shouldn't do.
So the conclusion is: I have a nice gold brick with working TWRP, adb and LG's download mode, but nothing more than that.
No chance to boot to system and I guess with a pretty messed up system partition.
Also, I think there's some problem with flashing anything, as I don't see any lines while installing, just a few seconds and info about succeeded flashing.
Is there anyone who could help me?
Hey folks. I'm stuck at the lollipop loading screen and can't get my ROM loaded, nor can I get into recovery.
I was on SkyDragon 6.x with the 35 bootstack. I wanted to load the stock 47A by xdabbeb, and all was good. I got into 47A, loaded things and then realized that I didn't have my Nova Launcher settings saved. I went back into recovery, wiped, flashed my most recent working backup, and then rebooted. Now I'm stuck at the ROM's loading screen (the four weird rotating artworks). It won't go past that even after leaving it for 30 minutes. It's possible the cause for my error was not wiping dalvik/cache after restoring, but regardless, my problem is now that I CAN'T FIND A WAY TO GET BACK INTO RECOVERY!!!
I tried the power+volume down, release at logo, then power+volume down like 20 times, but to no avail.
I tried adb in download mode, but my device isn't found in the list (maybe because the rom is not setup properly??)
What options do I have to get into recovery? I haven't backed up my photos in a while and it would be a TERRIBLE loss to have those photos go missing.
PLEASE HELP (at 3 AM!!!)!!!
Attempting adb again. My phone shows in Device Manager under USB as "LGE Mobile for VZW USB Composite Device" as well as under Portable Devices as "LGE Android MTP Device", but it won't list as an adb device when typing "adb devices"
Argghhh.
Mother plucker. I wasn't holding the buttons down long enough!!! Rebooting to recovery is working.
I should lose all of my rep for this thread.
Glad you solved it! For what it's worth I use the Mega app to automatically upload any photos and videos I take to Mega (free 50 GB cloud) whenever I'm on WIFI. You can have it do it on mobile data too if you wish. I know this sounds like an advert. OneDrive, Google Drive and DropBox all do the same thing but don't give as much space for free so I like to keep those available for other things.
By the way, the cause of the issue is mainly that TWRP doesn't do a backup of all the necessary Bootstack partitions, and also SkyDragon 6.x (and JasmineROM 9.x) only contain a partial 24B Bootstack. By themselves they're fine, but if you either are on the 35B Bootstack before you flash those ROMs or restore a backup of them, or you don't flash the 35B Bootstack after flashing either ROM or restoring a backup, you get what you experienced.
You should get in the habit of always flashing the appropriate Bootstack after flashing any ROM or restoring any backup, even if you think you were already on the necessary Bootstack.
Thanks for responding and not making me feel like the full moron that I am. Also for providing some suggestions on backing up photos. I know I'm supposed to do it. I just don't for some reason. Too trusting, I guess.
So coming from 47A and going to SD6, I should flash 24B boostack and then restore ROM from backup? Even if 35B was installed when the SD nandroid was taken? I just assumed that since my SD ROM was running on 35B bootstack, that restoring SD while still on 35B would have been sufficient. Is that incorrect?
roirraW "edor" ehT said:
Glad you solved it! For what it's worth I use the Mega app to automatically upload any photos and videos I take to Mega (free 50 GB cloud) whenever I'm on WIFI. You can have it do it on mobile data too if you wish. I know this sounds like an advert. OneDrive, Google Drive and DropBox all do the same thing but don't give as much space for free so I like to keep those available for other things.
By the way, the cause of the issue is mainly that TWRP doesn't do a backup of all the necessary Bootstack partitions, and also SkyDragon 6.x (and JasmineROM 9.x) only contain a partial 24B Bootstack. By themselves they're fine, but if you either are on the 35B Bootstack before you flash those ROMs or restore a backup of them, or you don't flash the 35B Bootstack after flashing either ROM or restoring a backup, you get what you experienced.
You should get in the habit of always flashing the appropriate Bootstack after flashing any ROM or restoring any backup, even if you think you were already on the necessary Bootstack.
Click to expand...
Click to collapse
my.ads0 said:
Thanks for responding and not making me feel like the full moron that I am. Also for providing some suggestions on backing up photos. I know I'm supposed to do it. I just don't for some reason. Too trusting, I guess.
So coming from 47A and going to SD6, I should flash 24B boostack and then restore ROM from backup? Even if 35B was installed when the SD nandroid was taken? I just assumed that since my SD ROM was running on 35B bootstack, that restoring SD while still on 35B would have been sufficient. Is that incorrect?
Click to expand...
Click to collapse
LOL, you're welcome! Restore a backup or flash a ROM and then flash the Bootstack after the flash or restore. For SD6, you can flash either the 24B or 35B Bootstack although 35B might be preferable. I believe encryption and Advanced/HD Calling on 35B ROMs don't work with the 24B Bootstack but do with the 35B Bootstack.
Just get used to flashing the appropriate Bootstack after and you don't have to bother thinking about when you can get away without doing it.
I can still boot up the phone into cm13. It is a vs985. Have an issue with data on cm13 and tried to factory reset from the phones settings instead of twrp. It restarted into a boot loop where only the TWRP screen keeps looping. If i boot it normal it boots up fine.
I dont even remember how i rooted and installed twrp originally, it was a while ago. Im going to look into it now but before i start experimenting and trying things like flashify i wanted to make sure this wasnt a known issue with certain mistakes to avoid.
I'd flash the 10B TOT, reroot with the Stump app, put TWRP on with TWRP Manager from the Play Store and start fresh.
roirraW "edor" ehT said:
I'd flash the 10B TOT, reroot with the Stump app, put TWRP on with TWRP Manager from the Play Store and start fresh.
Click to expand...
Click to collapse
Before I saw this I got impatient and just used flashify. Got the newer TWRP 3.0 and it went through no problem. Is this a known issue that you can't factory reset from within cm or is it just a bug that i encountered?
cory733 said:
Before I saw this I got impatient and just used flashify. Got the newer TWRP 3.0 and it went through no problem. Is this a known issue that you can't factory reset from within cm or is it just a bug that i encountered?
Click to expand...
Click to collapse
Glad you solved it. I knew that was possibly the solution but since I didn't know for sure what exactly CM did when you tried it's factory reset, I didn't know for sure it would be that simple. I don't play with non-Stock anymore, so I don't know the answer to your question. If no one answers this here, I'd suggest asking in the VS985 CM13 thread. Non-stock in general is always too buggy for me.