Just a short post... You've presumably already guessed from the title, it is the VS98523C FOTA release. The format is the same as the previous two, so any methods that worked for you then should work for this as well. I haven't finished extracting everything from it yet, so no warranty on how it works, but it is the "official", unmodified 23C FOTA.
23C: http://downloads.codefi.re/illegalargument/LG_VS985/12B_TO_23C.up
All (that I know) of the VS985 FOTA packages: http://downloads.codefi.re/illegalargument/LG_VS985/
Enjoy
Here's to hoping for bugg fixes!
Downgrade-ability guinea pig? Anyone....? Not it!
I'm about to update to it, will verify root works and then downgrading.
Edit: Thanks for posting this ^^
I'm sure Verizon and LG love all the free beta testing we're giving them...
Looks like the wifi syncing issue was fixed. Still testing but definitely looks that way.
HolyAngel said:
Looks like the wifi syncing issue was fixed. Still testing but definitely looks that way.
Click to expand...
Click to collapse
Do dev options stay ticked through reboot?
6NomoN6 said:
Do dev options stay ticked through reboot?
Click to expand...
Click to collapse
not sure yet, those are saved in the data partition so should stick regardless.. pretty positive they do on my rom based on 23B..
Side note: Downgrading is NOT blocked on 23C ^^
HolyAngel said:
not sure yet, those are saved in the data partition so should stick regardless.. pretty positive they do on my rom based on 23B..
Side note: Downgrading is NOT blocked on 23C ^^
Click to expand...
Click to collapse
Should we then also assume that it'll more than likely be safe to flash the 23C modem on it's own once it's isolated?
nericollin said:
Should we then also assume that it'll more than likely be safe to flash the 23C modem on it's own once it's isolated?
Click to expand...
Click to collapse
Yeah I don't see why not.. as long as you're on lollipop it should be fine. I'll pull it along with the other partitions.
If the memory leak has been fixed though, I see no reason not to do the update as a whole.
Just so I'm understanding this correctly: both downgrading and root are retained through updating so long as we revert back to 12B first before installing?
nericollin said:
If the memory leak has been fixed though, I see no reason not to do the update as a whole.
Just so I'm understanding this correctly: both downgrading and root are retained through upgrading?
Click to expand...
Click to collapse
No root isn't at all, has to be manually rooted same as 23B. But you can still downgrade no problem.
HolyAngel said:
No root isn't at all, has to be manually rooted same as 23B. But you can still downgrade no problem.
Click to expand...
Click to collapse
Understood. For example then, could I install this update, retain TWRP, and flash a 5.1 AOSP ROM with the 23C base?
So was it just a botched update on my end or does WiFi nor work on 23c?
---------- Post added at 03:34 PM ---------- Previous post was at 03:29 PM ----------
HolyAngel said:
Looks like the wifi syncing issue was fixed. Still testing but definitely looks that way.
Click to expand...
Click to collapse
Did you factory reset? I can't get WiFi to connect.
nericollin said:
Understood. For example then, could I install this update, retain TWRP, and flash a 5.1 AOSP ROM with the 23C base?
Click to expand...
Click to collapse
No definitely not, you have to be completely stock on 12B with no root and stock recovery in order to flash it.
gregcapps said:
So was it just a botched update on my end or does WiFi nor work on 23c?
---------- Post added at 03:34 PM ---------- Previous post was at 03:29 PM ----------
Did you factory reset? I can't get WiFi to connect.
Click to expand...
Click to collapse
My wifi was connected on bootup, haven't had a single issue the two times I've ota'd to 23C. Didn't have to factory reset or nothing.
HolyAngel said:
No definitely not, you have to be completely stock on 12B with no root and stock recovery in order to flash it.
My wifi was connected on bootup, haven't had a single issue the two times I've ota'd to 23C. Didn't have to factory reset or nothing.
Click to expand...
Click to collapse
First time I used activity launcher to go to 23c from 12b....got no Wi-Fi. Kdz back to 12b, then activity launcher to 23c got no system ui. Now I'm back on 23c after Another kdz to 12b and still have no working Wi-Fi. So I'm confused.
Also won't let me do screenshots. Says cannot copy. Damaged file.
gregcapps said:
First time I used activity launcher to go to 23c from 12b....got no Wi-Fi. Kdz back to 12b, then activity launcher to 23c got no system ui. Now I'm back on 23c after Another kdz to 12b and still have no working Wi-Fi. So I'm confused.
Click to expand...
Click to collapse
I tot'd to 10b_03 and ota'd up to 12b, no root. Once on 12b i used activity launcher to go up to 23C and worked perfectly. Did that both times with no issues. I had issues with all the kdz files, it's like they're not the official release or something.
Where can i get the 10b_03? And how does the tot method work?
gregcapps said:
Where can i get the 10b_03? And how does the tot method work?
Click to expand...
Click to collapse
10b_03 tot file is here: http://www.mediafire.com/download/6ip22jjhk7g3kgz/LG_G3_VS985_10B_03_Stock_TOT.zip
Its not mine, credits to 216Monster for posting it
And I uploaded the tot based LG Flash tool for ya here:
https://www.androidfilehost.com/?fid=95916177934550550
Pretty sure it works the same as kdz with the flashtool. the hacked dll to use it, and the vs985 dll to flash tot's with are included in the folder itself, all you need to do is download it and the tot file, point it to the lg dll file and the tot file, connect phone in download mode, hit ready, unplug and replug phone and it should work. You may need to open device manager->Ports, select the lg g3 port, properties, advanced, and change the port number to COM41 instead of whatever it auto assigns. Thats pretty much it.
Hunch
gregcapps said:
First time I used activity launcher to go to 23c from 12b....got no Wi-Fi. Kdz back to 12b, then activity launcher to 23c got no system ui. Now I'm back on 23c after Another kdz to 12b and still have no working Wi-Fi. So I'm confused.
Also won't let me do screenshots. Says cannot copy. Damaged file.
Click to expand...
Click to collapse
This is just a hunch but it seems that when you KDZ to 12b and do the updates, there are errors, myself included experienced them. From what I'm reading, people who go back to 10b and do the ota's upwards are not experiencing problems if any at all. I ToT's back to 10b and ota'd to 12b. I'm going to try 23c to see if I get the no nav buttons or the wifi issues.
Related
Looks like Verizon is pushing 24B update today. Very minor fixes but it's not showing up on my phone yet. Here is Verizon's release for it. http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-g3-7-9-15.pdf?null
Hmm. Do the interruptions mean that they have fixed notifications on wifi? It seems a bit cryptic.
Does anyone know if there will be issues if you try to take this OTA while rooted?
I am still on 23a. The OTA is not showing up and the upgrade assistant is of no help either.
Going to wait and see if we can flash back to a previous version, especially if root and bumping are locked out. Don't want it and currently, LP is running pretty well for me (has been since April when I upgraded to it). I haven't rooted as of yet either. Don't have a need for it right now and want to wait and see when the next big OTA comes out or if this upcoming one does fix the WiFi sync issue completely.
adrianbli said:
Hmm. Do the interruptions mean that they have fixed notifications on wifi? It seems a bit cryptic.
Does anyone know if there will be issues if you try to take this OTA while rooted?
Click to expand...
Click to collapse
As a general rule, with ANY phone, running ANY software, do NOT take ANY OTA's while any modifications have been made to your system (this includes rooting, custom recovery, etc.). Could it go through? Maybe, no one really knows until some bonehead tries and it fails or a trusted member of the community lets people know. If it doesn't, you're in for much more of a headache than the update benefits you, and possibly much worse. Your only options should be either to 1) wait until someone releases an updated rom based on this update (which this update is pretty near worthless anyways - doesn't contain anything major), or 2) tot or kdz back to stock and upgrade without any modifications.
I am still waiting on it to show up on my phone for OTA. I'll upgrade to it and let you know if it fixes the wifi bug.
Installing now
Yeah, I just see added features, no bug fixes listed on the changelog. Does Verizon usually list bug fixes on their updates release notes?
---------- Post added at 12:13 PM ---------- Previous post was at 11:56 AM ----------
Downloading via OTA now! 197.5 MB.
It looks to me like the update might have fixed the wifi bug. I uninstalled DNSet and sent an email to myself and I got the notification right away. I am restarting now to see if that makes any difference.
I'm stock/rooted (no bump) on 23C right now. I have not changed any system files from what I can recall. I'm currently running a titanium backup.
Once that's done, I'll unfreeze my frozen apps and I'll accept the OTA. Hopefully, I'll retain root. Through all of the previous updates with this phone, I have no lost root in taking an OTA.
I'll report back in around a half hour or so.
---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------
matty032 said:
Yeah, I just see added features, no bug fixes listed on the changelog. Does Verizon usually list bug fixes on their updates release notes?
---------- Post added at 12:13 PM ---------- Previous post was at 11:56 AM ----------
Downloading via OTA now! 197.5 MB.
Click to expand...
Click to collapse
Are you currently rooted? If so, let me know if you keep root during OTA.
lexluthor said:
I'm stock/rooted (no bump) on 23C right now. I have not changed any system files from what I can recall. I'm currently running a titanium backup.
Once that's done, I'll unfreeze my frozen apps and I'll accept the OTA. Hopefully, I'll retain root. Through all of the previous updates with this phone, I have no lost root in taking an OTA.
I'll report back in around a half hour or so.
---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------
Are you currently rooted? If so, let me know if you keep root during OTA.
Click to expand...
Click to collapse
Sorry not rooted. After the first restart, it didn't seem to have fixed the WiFi sync problem. But, after it calmed down awhile, so far it seems to be fixed. God I hope so!
matty032 said:
Sorry not rooted. After the first restart, it didn't seem to have fixed the WiFi sync problem. But, after it calmed down awhile, so far it seems to be fixed. God I hope so!
Click to expand...
Click to collapse
Can someone verify if they can root with the latest one-click root method and if you can revert back to a previous version to bump (KDZ or TOT)? I want to make sure they haven't locked out the ability to bump.
Well that didn't go so well. Upon rebooting to start the install, I quickly got an error message at the 1% mark
Err: 0x1111004
I don't recall any changed system files, but I guess there must be as that's what the error is most likely about?
Guess I'm sitting this out for a bit.
lexluthor said:
Well that didn't go so well. Upon rebooting to start the install, I quickly got an error message at the 1% mark
Err: 0x1111004
I don't recall any changed system files, but I guess there must be as that's what the error is most likely about?
Guess I'm sitting this out for a bit.
Click to expand...
Click to collapse
Are you rooted and/or bumped? If you rooted and then unrooted (but didn't flash back via TOT or KDZ), then the system image is modified, even if you removed root as rooting modifies the system partition. Therefore, no OTAs will be accepted until you flash back to pure stock via TOT or KDZ.
iBolski said:
Are you rooted and/or bumped? If you rooted and then unrooted (but didn't flash back via TOT or KDZ), then the system image is modified, even if you removed root as rooting modifies the system partition. Therefore, no OTAs will be accepted until you flash back to pure stock via TOT or KDZ.
Click to expand...
Click to collapse
I'm just rooted.
I know I've accepted OTAs in the past on my LG G3 while rooted and it worked fine. I didn't even try to unroot (this time or previous times).
Posted a link to the OTA files in @bweN diorD 's thread [REFERENCE] Stock IMG files + Stock Links & Mods.
I do believe if you were rooted going from KK to LP, it definitely didn't work and it could be this time around, if you used the new one-click root, it does the root differently to the point that it won't allow an OTA. I do remember I could update from 10b to 11c to 12b rooted as long as I had preserve root enabled in SuperSU. But, going from 12b to 23c rooted was a no-go and you had to flash back to stock. So, I'm going to chalk this up to the new one-click root method has done something that won't allow even a minor OTA from 23c to 24b to be allowed.
My freshly flashed 23C KDZ is a quarter of the way optimizing, then I'll take the OTA and try the one-click root again. After that, I'll test reflashing the 23C KDZ once more.
Edit: Update...weird. Under JasmineROM 7.0 (no debloat or mods, but rooted), it gave me the OTA, which I then moved from it's folder. Now that I've flashed the 23C KDZ in CSE mode, now it says I have no updates. I'll reboot and try again. If I have to I'll use the Activity Launcher method to run the OTA I already downloaded.
Update 2: Haven't had any luck applying the update with the "Activity Launcher" method. FOTA starts, the phone reboots but just boots the ROM and I have a notification that it failed to update. System Updates still claims I don't have an OTA available even though I did under JasmineROM 7.0 (rooted but not debloated and not modded).
I left my work WiFi, and came back. Google notifications are still working, and calls are still ringing Hangouts. MS Outlook app notifications are also working.
matty032 said:
I left my work WiFi, and came back. Google notifications are still working, and calls are still ringing Hangouts. MS Outlook app notifications are also working.
Click to expand...
Click to collapse
I had to read this 4 times to make sure there weren't any "not" in front of "working."
roirraW "edor" ehT said:
Posted a link to the OTA files in @bweN diorD 's thread [REFERENCE] Stock IMG files + Stock Links & Mods.
Click to expand...
Click to collapse
I can give that a try and see if it behaves any differently than the file I downloaded, but I doubt it. I would put this on my sdcard and then what?
So if the OTA fails on my stock/rooted phone, is there any way to get to 24B without a losing everything? If that's not available today, is that something that typically would be available at some point?
Hey everyone,
I was able to root my LG G3 with the help of the XDA forms so I figured maybe someone could help me out here. I am running the STOCK Verizon Rom that came with the phone. I wanted to know if there is a customer kernal I can install to improve battery life and/or if anyone knows the good Tricker Mod settings to set up so the battery life improves, that would be helpful as well.
Thanks for the help everyone.
TheBull50 said:
Hey everyone,
I was able to root my LG G3 with the help of the XDA forms so I figured maybe someone could help me out here. I am running the STOCK Verizon Rom that came with the phone. I wanted to know if there is a customer kernal I can install to improve battery life and/or if anyone knows the good Tricker Mod settings to set up so the battery life improves, that would be helpful as well.
Thanks for the help everyone.
Click to expand...
Click to collapse
You will need to install TWRP to install a custom kernel.
I am running Jasmine ROM 8.0 with the Skydragon 4.2 Kernel with great battery life.
Great. Thank you. I was able to install twrp and installed sky dragon
Kernel to my Verizon stock Rom. Seems to be doing just fine ☺
TheBull50 said:
Great. Thank you. I was able to install twrp and installed sky dragon
Kernel to my Verizon stock Rom. Seems to be doing just fine ☺
Click to expand...
Click to collapse
Another good one is Gabriel Kernel
TheBull50 said:
Hey everyone,
I was able to root my LG G3 with the help of the XDA forms so I figured maybe someone could help me out here. I am running the STOCK Verizon Rom that came with the phone. I wanted to know if there is a customer kernal I can install to improve battery life and/or if anyone knows the good Tricker Mod settings to set up so the battery life improves, that would be helpful as well.
Thanks for the help everyone.
Click to expand...
Click to collapse
Can I ask what method you used to root after 24B update? I have tried a few different methods I found on XDA and all of them just hang at the part where it should push root to the phone. Thanks.
garyj1 said:
Can I ask what method you used to root after 24B update? I have tried a few different methods I found on XDA and all of them just hang at the part where it should push root to the phone. Thanks.
Click to expand...
Click to collapse
[GUIDE][ROOT]Newest Root Method for LG devices
garyj1 said:
Can I ask what method you used to root after 24B update? I have tried a few different methods I found on XDA and all of them just hang at the part where it should push root to the phone. Thanks.
Click to expand...
Click to collapse
Besides using the root method @quadjacks linked to below, just wanted to make sure you know that in order to root 24B, you have to come from a string of at least two OTAs. In other words, if you at any time flashed the 23C KDZ, then after you take the 24B OTA, you won't be able to root the phone, at least that's our experience.
You will be able to root it (not using the one-click but the one @quadjacks links to) if you flash the 12B KDZ, then OTA to 23C, then OTA to 24B.
quadjacks said:
[URL=" Root Method for LG devices[/URL]
Click to expand...
Click to collapse
roirraW "edor" ehT said:
Besides using the root method @quadjacks linked to below, just wanted to make sure you know that in order to root 24B, you have to come from a string of at least two OTAs. In other words, if you at any time flashed the 23C KDZ, then after you take the 24B OTA, you won't be able to root the phone, at least that's our experience.
You will be able to root it (not using the one-click but the one @quadjacks links to) if you flash the 12B KDZ, then OTA to 23C, then OTA to 24B.
Click to expand...
Click to collapse
I flashed the 23C KDZ and then OTA to 24B. Root works fine.
Sent from my VS985 4G using Tapatalk
NBreunig3 said:
I flashed the 23C KDZ and then OTA to 24B. Root works fine.
Click to expand...
Click to collapse
For most people who have tried and reported back, including myself several times and with all the root methods I could think of, that didn't work, but a couple of people have reported being able to root after OTAing from 23C.
roirraW "edor" ehT said:
For most people who have tried and reported back, including myself several times and with all the root methods I could think of, that didn't work, but a couple of people have reported being able to root after OTAing from 23C.
Click to expand...
Click to collapse
There is a 24B KDZ available. I also have used this KDZ and then been able to root.
Sent from my VS985 4G using Tapatalk
NBreunig3 said:
There is a 24B KDZ available. I also have used this KDZ and then been able to root.
Click to expand...
Click to collapse
I'm aware of that, too - I posted the link to it, but I haven't had the inclination to flash it and try rooting after. I won't be surprised since the first method I mentioned in the previous message, flashing the 23C KDZ and taking the OTA, then trying to root, didn't work myself and several others that it won't work for me with flashing the 24B KDZ directly, but I'm just speculating. I'm sure I'll attempt it again when I have a need to reset to completely stock unrooted again unless by that time I'm in too much of a hurry to take another new OTA that may come and try to root that first.
roirraW "edor" ehT said:
I'm aware of that, too - I posted the link to it, but I haven't had the inclination to flash it and try rooting after. I won't be surprised since the first method I mentioned in the previous message, flashing the 23C KDZ and taking the OTA, then trying to root, didn't work myself and several others that it won't work for me with flashing the 24B KDZ directly, but I'm just speculating. I'm sure I'll attempt it again when I have a need to reset to completely stock unrooted again unless by that time I'm in too much of a hurry to take another new OTA that may come and try to root that first.
Click to expand...
Click to collapse
I was able to root after flashing the 24B KDZ. The root.bat did not work (hung on the installing root part). But I was able to do option 2 and manually push the files and install root with one minor change. The first time I ran the Send_Command to push root it hung, I did a ctrl-C on it then ran it again right after and it went through. Then I did the send_command reboot and the phone rebooted and was rooted when it came up. I did this a couple of times and had the same results every time, first send_command would hang and I had to break out of it (ctrl-c) the send_commands after that worked fine. Not sure why that is but that is what worked for me. Just wanted to share in case anyone is having the same problem.
And then after rooting 24B, how to install TWRP??? I tried and got the Security Error message. Help would be appreciated.
sd_N said:
And then after rooting 24B, how to install TWRP??? I tried and got the Security Error message. Help would be appreciated.
Click to expand...
Click to collapse
I downloaded version 2.8.7.0 then used adb to install with the instructions from this thread...
http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
sd_N said:
And then after rooting 24B, how to install TWRP??? I tried and got the Security Error message. Help would be appreciated.
Click to expand...
Click to collapse
Just to present another option, in the Play Store, search for:
Code:
autorec VS985
It'll install TWRP v2.8.6.x and downgrade your bootloader, which you can then update TWRP to the latest from within the "old" version.
garyj1 said:
I downloaded version 2.8.7.0 then used adb to install with the instructions from this thread...
[/QUOTE]
Click to expand...
Click to collapse
Need to check if I have the 24B...... and Thanks!!
I spent the greater part of the evening trying to root my LG G3 VS985 unsuccessfully, but I don't recall if it is the 24B. I got it off eBay to upgrade my current RazrHD which is hopelessly underpowered - but it is rooted, and didn't want to lose my unlimited data plan on VZW. Need to mark this thread for all the helpful comments.
The methods of rooting I tried were the One-Click, both the gui and the CLI script with similar results of hanging trying to "see" the device, I tried PurpleDrake, but I think it is for a different LG or android version, and there was one other method that I got from a link either here on XDA or another android forum, but all seemed to have the same problem - once you connect the phone, it initially tries to connect to the device, but never succeeds, just keeps you waiting for the root push to start, but it never does. I was using a Win-7 PC and laptop, switching back and forth to see if I could get one of them to work........ Of course, I have the developer option enabled and turned on the USB debugging. I really like this LG G3 and want to get this thing rooted!!
The other root method I tried was ioroot; I checked my folders. Further reading seems to indicate I may be SOL unless I want to wait for someone to figure it out; oh, yeah, and I tried towelroot as well, but it only tells me my device is not supported........I plan to try one more root method - stumproot, and see if it can bruteforce it. If not, will be a sadder day.......
roirraW "edor" ehT said:
Just to present another option, in the Play Store, search for:
Code:
autorec VS985
It'll install TWRP v2.8.6.x and downgrade your bootloader, which you can then update TWRP to the latest from within the "old" version.
Click to expand...
Click to collapse
I think AutoRec got me the Security Error. I'll try when I get home. Thanks for ur help.
Ok-Full specs on my LG G3 that I want to root....
Running android 5.0.1
Build: LRX21Y
Software Version: VS985 23C
Went back and looked at some of the info and it can be confusing; some root progs need certain version of android running, on a certain set of builds and proper software versions........ enough to make you want to start drinking...... Going to go back one more time and see what I can do to organize all this disparate info and make some more sense out of it. On the plus side, since I have the 32GB version/model, it has 3GB RAM which I confirmed, and even though I have a ton of junky bloat stuff running that I can't currently stop, the phone is running like a champ.
Doesnt work
roirraW "edor" ehT said:
Just to present another option, in the Play Store, search for:
Code:
autorec VS985
It'll install TWRP v2.8.6.x and downgrade your bootloader, which you can then update TWRP to the latest from within the "old" version.
Click to expand...
Click to collapse
I can get into twrp.... just cant boot to system. I'm really dont want to have to KDZ back. Thanks
I used autorec to flash twrp on my 24b LP VZW G3. That was successful. Then booted to recovery...made a backup... then flashed twrp 2870 img, then booted recovery... then booted system and it went to LG bootlogo with Security Error message.
I'd really love to get this straightened out if possible. Would appreciate any advice and help.
sd_N said:
I think AutoRec got me the Security Error. I'll try when I get home. Thanks for ur help.
Click to expand...
Click to collapse
sd_N said:
I can get into twrp.... just cant boot to system. I'm really dont want to have to KDZ back. Thanks
I used autorec to flash twrp on my 24b LP VZW G3. That was successful. Then booted to recovery...made a backup... then flashed twrp 2870 img, then booted recovery... then booted system and it went to LG bootlogo with Security Error message.
I'd really love to get this straightened out if possible. Would appreciate any advice and help.
Click to expand...
Click to collapse
I apologize for the misinformation! I realized earlier after reading what some others had said that in all the testing I had done regarding 24B that I had actually NOT run autorec on 24B, or at least not *just* autorec. To fix your phone, download and flash JasmineROM 8.0. If you felt adventurous, all you really need out of the JasmineROM 8.0 zip is the bootloader (aboot.img) and possibly the kernel (boot.img) too. The changes to the bootloader and possibly the kernel too are what get rid of the security error with TWRP installed.
This morning I awoke to my rooted 24b LG G3 downloading some ~350MB file from Verizon, did not identify what it was, but it wants to install automatically. Only gave me an option to install now or later.
Anyone know what it is and if I should be concerned for my root status?
APeter001 said:
This morning I awoke to my rooted 24b LG G3 downloading some ~350MB file from Verizon, did not identify what it was, but it wants to install automatically. Only gave me an option to install now or later.
Anyone know what it is and if I should be concerned for my root status?
Click to expand...
Click to collapse
According to Verizon it is update to "35A"
Used app quarantine to quarantine "System Update" and it went away.
cant be 35a because we got 35b weeks ago. pretty standard that vzw tech dont know [email protected]#$
I was thinking that was weird, but when I clicked the "more information" link it said the download was ...35A
bweN diorD said:
cant be 35a because we got 35b weeks ago. pretty standard that vzw tech dont know [email protected]#$
Click to expand...
Click to collapse
APeter001 said:
I was thinking that was weird, but when I clicked the "more information" link it said the download was ...35A
Click to expand...
Click to collapse
Verizon's changelog said 35A too - I'm sure they just made the typo in more than one place.
---------- Post added at 03:05 PM ---------- Previous post was at 02:59 PM ----------
APeter001 said:
This morning I awoke to my rooted 24b LG G3 downloading some ~350MB file from Verizon, did not identify what it was, but it wants to install automatically. Only gave me an option to install now or later.
Anyone know what it is and if I should be concerned for my root status?
Click to expand...
Click to collapse
To answer your question:
1. From 23C (Lollipop 5.0.1) and later, you can't/shouldn't even attempt to take an OTA when rooted, even if you have stock recovery.
2. It won't update on a rooted system, although you may end up in a bootloop which you would be able to fix from custom recovery.
There are three 35B (5.1.1) rooted stock ROMs in Development. @xdabbeb 's VS985 ROM already has the OTA updates removed so in the future you wouldn't get update notices like this. I don't think JasmineROM or SkyDragon have OTA updates removed, but I'm not 100% certain especially concerning SkyDragon.
35B runs great! Much smoother than 23C and 24B.
Greetings,
Seemingly out of the blue, I have started having major wifi problems. The problem is that the wifi connection either doesn't connect, giving a "Wifi Connection Failure" or will connect briefly with no actual access to the internet. This problem occurs on multiple routers from multiple ISPs. I have already ensured the router is working, going so far as factory resetting it and providing a static IP for my phone. I have even factory reset my phone. Same problem, though it does seem to stay connected to my wifi longer but still no internet. Even in Safe Mode, I cannot get any internet access via wifi.
Verizon LG G3, Unrooted with 47A release (No custom ROMs)
Any suggestions?!?!
Hi!
What ROM are you on? The latest 47A Marshmallow? Are you rooted?
Regardless I suggest flashing the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that nothing else can, so even if you want to stay unrooted flash the TOT first, test WiFi, and if WiFi works then flash the 47A KDZ with the CSE option, and test WiFi again. Both will wipe all user apps and all data and internal storage so move everything you want to keep. You can use the built in LG Backup to backup your user apps and data to your Micro SD card.
If you wanted rooted, then while on 10B use the Stump app to root and use TWRP Manager from the Play Store to flash TWRP, then flash the ROM you want and appropriate Bootstack.
roirraW "edor" ehT said:
Hi!
What ROM are you on? The latest 47A Marshmallow? Are you rooted?
Regardless I suggest flashing the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that nothing else can, so even if you want to stay unrooted flash the TOT first, test WiFi, and if WiFi works then flash the 47A KDZ with the CSE option, and test WiFi again. Both will wipe all user apps and all data and internal storage so move everything you want to keep. You can use the built in LG Backup to backup your user apps and data to your Micro SD card.
If you wanted rooted, then while on 10B use the Stump app to root and use TWRP Manager from the Play Store to flash TWRP, then flash the ROM you want and appropriate Bootstack.
Click to expand...
Click to collapse
Sorry for leaving out info.
Stock ROM, Unrooted with 47A release.
I was thinking about flashing but I was hoping I wouldn't have to. The 47A release fixed a couple of nagging issues but this issue is obviously worse. At this point, I'm kinda desperate...
someguyouknew said:
Sorry for leaving out info.
Stock ROM, Unrooted with 47A release.
I was thinking about flashing but I was hoping I wouldn't have to. The 47A release fixed a couple of nagging issues but this issue is obviously worse. At this point, I'm kinda desperate...
Click to expand...
Click to collapse
Understood. No problem! I've been on 47A since it came out - first unrooted and then rooted so hopefully the 10B TOT and then 47A KDZ should get and keep the WiFi working unless it's a hardware issue. Hopefully just software though.
roirraW "edor" ehT said:
Understood. No problem! I've been on 47A since it came out - first unrooted and then rooted so hopefully the 10B TOT and then 47A KDZ should get and keep the WiFi working unless it's a hardware issue. Hopefully just software though.
Click to expand...
Click to collapse
I appreciate your response! I'm watching the youtube video on how to do it right now. Thanks!
roirraW "edor" ehT said:
Hi!
What ROM are you on? The latest 47A Marshmallow? Are you rooted?
Regardless I suggest flashing the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that nothing else can, so even if you want to stay unrooted flash the TOT first, test WiFi, and if WiFi works then flash the 47A KDZ with the CSE option, and test WiFi again. Both will wipe all user apps and all data and internal storage so move everything you want to keep. You can use the built in LG Backup to backup your user apps and data to your Micro SD card.
If you wanted rooted, then while on 10B use the Stump app to root and use TWRP Manager from the Play Store to flash TWRP, then flash the ROM you want and appropriate Bootstack.
Click to expand...
Click to collapse
Flashing to 10B didn't seem to work. It's starting to look like a hardware problem. Really disappointing as I have only had this phone for less than 2 years.
Thanks for the suggestion, though.
someguyouknew said:
Flashing to 10B didn't seem to work. It's starting to look like a hardware problem. Really disappointing as I have only had this phone for less than 2 years.
Thanks for the suggestion, though.
Click to expand...
Click to collapse
Sorry to hear that! I was really hoping it was software. Sorry to be a squeaky wheel but I just wanted to make sure, you flashed the 10B TOT, not just the 10B KDZ, right? You're welcome and good luck with what options you might have. You could try sending to LG and seeing what they would charge you but unless you have a backup phone that would be tough. I had an awesome experience with their repair for my tablet but that was under warranty.
roirraW "edor" ehT said:
Sorry to hear that! I was really hoping it was software. Sorry to be a squeaky wheel but I just wanted to make sure, you flashed the 10B TOT, not just the 10B KDZ, right? You're welcome and good luck with what options you might have. You could try sending to LG and seeing what they would charge you but unless you have a backup phone that would be tough. I had an awesome experience with their repair for my tablet but that was under warranty.
Click to expand...
Click to collapse
Yea, definitely used the .tot method. I am typing up an email to LG right now. Hopefully it isn't out of warranty.
someguyouknew said:
Yea, definitely used the .tot method. I am typing up an email to LG right now. Hopefully it isn't out of warranty.
Click to expand...
Click to collapse
Let us know how things work out.
Hey everyone, I have a verizon g3 with firmware version 47a. I'm hell bent on rooting it and it's hell bent on stopping me at any cost XD So the problem is, I'm trying to flash the 10b kdz file, and when I load up the tool and start the flash, it gets the bar to 100% and then gives me an error that says can't connect to server. After that, I just click OK and watch my phone for activity, and there is none. The firmware update bar on my phone remains on 0%. Any solutions would be very much appreciated.
Thanks in advance.
*IF* you're not rooted/haven't flashed one of @xdabbeb 's Bootstacks, then you can't flash anything older than the 35B KDZ from (stock unrooted) 35B or higher. You have to use the 10B TOT along with the .DLL that's extracted from the 35B KDZ. You can find both in my Android File Host section linked to at the bottom of @annoyingduck 's stickied return to stock thread in the General section, also linked to in my signature below.
Regarding no connection to server, read the second or third post of the thread I reference above. But as I said above, if you're coming from 100% stock unrooted 47A, you have to use the TOT method to downgrade to the easily rootable 10B, where you can then use the Stump app on XDA to root it using the brute force option, and then use TWRP Manager from the Play Store to put on TWRP. Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B.
roirraW "edor" ehT said:
*IF* you're not rooted/haven't flashed one of @xdabbeb 's Bootstacks, then you can't flash anything older than the 35B KDZ from (stock unrooted) 35B or higher. You have to use the 10B TOT along with the .DLL that's extracted from the 35B KDZ. You can find both in my Android File Host section linked to at the bottom of @annoyingduck 's stickied return to stock thread in the General section, also linked to in my signature below.
Regarding no connection to server, read the second or third post of the thread I reference above. But as I said above, if you're coming from 100% stock unrooted 47A, you have to use the TOT method to downgrade to the easily rootable 10B, where you can then use the Stump app on XDA to root it using the brute force option, and then use TWRP Manager from the Play Store to put on TWRP. Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B.
Click to expand...
Click to collapse
Hey, thanks so much for the help and reply. So I followed everything you said and everything in the guide, and i still have a small problem. When I start the flash, it's fine. It detects the phone and "analyzes phone setting". Then, it gets to the software extraction part, and **** hits the fanXD. Basically, the connection to server lost window pops up, and the original window states "Upgrade stopped due to an error". And of course, my phone has no activity, the firmware update bar is still on 0%. What gives??
andr0id187 said:
Hey, thanks so much for the help and reply. So I followed everything you said and everything in the guide, and i still have a small problem. When I start the flash, it's fine. It detects the phone and "analyzes phone setting". Then, it gets to the software extraction part, and **** hits the fanXD. Basically, the connection to server lost window pops up, and the original window states "Upgrade stopped due to an error". And of course, my phone has no activity, the firmware update bar is still on 0%. What gives??
Click to expand...
Click to collapse
Are you clicking on analyze phone? You don't need to do that. And I know in the past that has messed me up.
Sent from my One M8 using XDA Labs
andr0id187 said:
Hey, thanks so much for the help and reply. So I followed everything you said and everything in the guide, and i still have a small problem. When I start the flash, it's fine. It detects the phone and "analyzes phone setting". Then, it gets to the software extraction part, and **** hits the fanXD. Basically, the connection to server lost window pops up, and the original window states "Upgrade stopped due to an error". And of course, my phone has no activity, the firmware update bar is still on 0%. What gives??
Click to expand...
Click to collapse
You're welcome!
Did you wait 5-10 minutes since the connection to server dialog is normal? Commonly if you wait 5-10 minutes and not have touched any buttons in any dialogs in the software that pop up, you'll find the phone is flashed.
Can you confirm since you haven't said - are you 100% stock unrooted or rooted and have previously flashed one of @xdabbeb 's Bootstacks? Like I said, if you're 100% stock unrooted, you have to use the TOT method, not KDZs. TOT uses a different tool. Just Google for it. "TOT Method"
If waiting 5-10 minutes doesn't help, try the TOT method. It's better overall anyway, even if it's less user friendly (except that LG Flash Tool 2014 throws up bogus error dialogs).
---------- Post added at 02:59 PM ---------- Previous post was at 02:57 PM ----------
jurington said:
Are you clicking on analyze phone? You don't need to do that. And I know in the past that has messed me up.
Click to expand...
Click to collapse
^^^^^^^^^^ yep, definitely, what @jurington said.
roirraW "edor" ehT said:
You're welcome!
Did you wait 5-10 minutes since the connection to server dialog is normal? Commonly if you wait 5-10 minutes and not have touched any buttons in any dialogs in the software that pop up, you'll find the phone is flashed.
Can you confirm since you haven't said - are you 100% stock unrooted or rooted and have previously flashed one of @xdabbeb 's Bootstacks? Like I said, if you're 100% stock unrooted, you have to use the TOT method, not KDZs. TOT uses a different tool. Just Google for it. "TOT Method"
If waiting 5-10 minutes doesn't help, try the TOT method. It's better overall anyway, even if it's less user friendly (except that LG Flash Tool 2014 throws up bogus error dialogs).
---------- Post added at 02:59 PM ---------- Previous post was at 02:57 PM ----------
^^^^^^^^^^ yep, definitely, what @jurington said.
Click to expand...
Click to collapse
Goddamit you're right, I'm stupid, I didn't read that I AM on stock, unrooted so I'm going to have to use TOT. So will the file remain the same? vs98510b?
andr0id187 said:
Goddamit you're right, I'm stupid, I didn't read that I AM on stock, unrooted so I'm going to have to use TOT. So will the file remain the same? vs98510b?
Click to expand...
Click to collapse
I'm not clear on your question. It's a 10B TOT (and the .DLL I mentioned previously) instead of the 10B KDZ, so it's a different file.
roirraW "edor" ehT said:
I'm not clear on your question. It's a 10B TOT (and the .DLL I mentioned previously) instead of the 10B KDZ, so it's a different file.
Click to expand...
Click to collapse
Ok, so I flashed the 10b tot, rooted it with stump, installed SuperSU and TWRP. Then, according to this article: http://androiding.how/root-verizon-g3-47a-marshmallow-firmware/
I'm supposed to flash the 35b bootstack which I also did successfully. Then, I can flash back to 47a and keep the root. Only problem is, after installing the bootstack, when I try to flash 47a, it's not rooted, and gives me a "con.android.phone has stopped working" error. I think this might have something to do with the fact that in the article, it says NOT to let TWRP install SuperSU when flashing 47a. When i flash it, it gives me no option to accept or deny the installation of Super SU. Is this the problem? Or is it something else entirely? Thanks again.
andr0id187 said:
Ok, so I flashed the 10b tot, rooted it with stump, installed SuperSU and TWRP. Then, according to this article: http://androiding.how/root-verizon-g3-47a-marshmallow-firmware/
I'm supposed to flash the 35b bootstack which I also did successfully. Then, I can flash back to 47a and keep the root. Only problem is, after installing the bootstack, when I try to flash 47a, it's not rooted, and gives me a "con.android.phone has stopped working" error. I think this might have something to do with the fact that in the article, it says NOT to let TWRP install SuperSU when flashing 47a. When i flash it, it gives me no option to accept or deny the installation of Super SU. Is this the problem? Or is it something else entirely? Thanks again.
Click to expand...
Click to collapse
Did you flash xdabbebs 47A rom? Also did you did you do any wipes in twrp before you flashed the rom? And what version of twrp do you have?
Sent from my One M8 using XDA Labs
andr0id187 said:
Ok, so I flashed the 10b tot, rooted it with stump, installed SuperSU and TWRP. Then, according to this article: http://androiding.how/root-verizon-g3-47a-marshmallow-firmware/
I'm supposed to flash the 35b bootstack which I also did successfully. Then, I can flash back to 47a and keep the root. Only problem is, after installing the bootstack, when I try to flash 47a, it's not rooted, and gives me a "con.android.phone has stopped working" error. I think this might have something to do with the fact that in the article, it says NOT to let TWRP install SuperSU when flashing 47a. When i flash it, it gives me no option to accept or deny the installation of Super SU. Is this the problem? Or is it something else entirely? Thanks again.
Click to expand...
Click to collapse
I'd wipe Cache, Dalvik /ART and Data and reflash @xdabbeb 's VS985 stock 47A firmware.
TWRP v3.0.0 is systemless root (or at least Marshmallow) aware so doesn't offer to flash SuperSU.
2.8.7.0 isn't aware and asks since it won't be able to find SuperSU where it looks.
If you do wipes after flashing the ROM, it's common to lose root. Just reflash the ROM.
Also optional debloat zips in post three of his ROM thread.
Ok so first of all, yes I have the xdadev 47a rom, yes I did a wipe in twrp, is that bad? And I have twrp 3.0.0.0(latest?) If you need any more information please ask, I'm really hoping to solve this problem. Thanks
andr0id187 said:
Ok so first of all, yes I have the xdadev 47a rom, yes I did a wipe in twrp, is that bad? And I have twrp 3.0.0.0(latest?) If you need any more information please ask, I'm really hoping to solve this problem. Thanks
Click to expand...
Click to collapse
No, you're supposed to wipe in TWRP, he was just covering all bases. Did you re-flash the ROM?
You can also/instead potentially flash the latest SuperSU.zip from @Chainfire 's website.
roirraW "edor" ehT said:
No, you're supposed to wipe in TWRP, he was just covering all bases. Did you re-flash the ROM?
You can also/instead potentially flash the latest SuperSU.zip from @Chainfire 's website.
Click to expand...
Click to collapse
so whats happening is, every time after i flash the xdadev 47a rom(i dont wipe mind you, i just reboot), it's giving me the com.android.phone has stopped error and no root. I really don't understand why
andr0id187 said:
so whats happening is, every time after i flash the xdadev 47a rom(i dont wipe mind you, i just reboot), it's giving me the com.android.phone has stopped error and no root. I really don't understand why
Click to expand...
Click to collapse
Check the ROM zip MD5 hash? I assume you're meaning you don't wipe after. Did you try wiping again before flashing it?
roirraW "edor" ehT said:
Check the ROM zip MD5 hash? I assume you're meaning you don't wipe after. Did you try wiping again before flashing it?
Click to expand...
Click to collapse
yes i've tried wiping before flashing and it still gives me the error, I'm currently wiping after flash to see what happens, hopefully i dont lose root
andr0id187 said:
yes i've tried wiping before flashing and it still gives me the error, I'm currently wiping after flash to see what happens, hopefully i dont lose root
Click to expand...
Click to collapse
That's not going to make a difference but you will likely not be rooted. You'll still have TWRP though.
roirraW "edor" ehT said:
That's not going to make a difference but you will likely not be rooted. You'll still have TWRP though.
Click to expand...
Click to collapse
so how do i go from 10b to 47a and keep root?
andr0id187 said:
so how do i go from 10b to 47a and keep root?
Click to expand...
Click to collapse
The only way I know is what we've already discussed and what you already did. Did you check the ROM zip MD5 hash? I've flashed my (and my wife's) G3's many times with these files when I was doing tests and haven't had this problem. I'm perplexed as well but if you should check the MD5 hash to eliminate that as a problem. That said, you might need to reflash the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that flashing KDZs and ROMs can't. I once had a weird issue that it didn't matter what KDZ or rooted ROM I flashed, the problem persisted. I don't recall the exact problem but it conceivably could've been the same as similar to yours. Once I flashed the 10B TOT, all was well and when discussing with @xdabbeb, that's when he educated me that TOTs have more partitions than KDZs. I'm a diehard TOT fan ever since (I preferred KDZ when possible previously).
I know you already flashed the TOT but we're running out of ideas. If the MD5 hash of the 47A ROM and 35B Bootstack match what they're supposed to (listed on the Android File Host download page for each file). Make sure and
You should also get in the habit of flashing the appropriate Bootstack every time you flash a ROM, or after every time you restore a TWRP backup. Even if you know you're already on the 35B Bootstack - mind you, I'm not meaning this as "snake oil" or as a solution to the trouble you're having, and flashing it more than once won't change anything, but I just wanted to make sure you know this since some ROM's (JasmineROM and SkyDragon) include a partial Bootstack and can cause a brick (so the Bootstack should be flashed after the ROM in their case), and TWRP Backups/Restores don't backup or restore the entire set of partitions including in the Bootstack, so if you happen to be on a ROM that you were using the 24B Bootstack with, and restore a TWRP Backup of a 35B or higher ROM, you might not have a signal.
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
@andr0id187 I also want to be completely clear since I read back and I don't think you specified. Sorry for the repetetiveness but when you wipe before flashing, you're wiping Cache, Dalvik /ART and Data correct?
roirraW "edor" ehT said:
The only way I know is what we've already discussed and what you already did. Did you check the ROM zip MD5 hash? I've flashed my (and my wife's) G3's many times with these files when I was doing tests and haven't had this problem. I'm perplexed as well but if you should check the MD5 hash to eliminate that as a problem. That said, you might need to reflash the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that flashing KDZs and ROMs can't. I once had a weird issue that it didn't matter what KDZ or rooted ROM I flashed, the problem persisted. I don't recall the exact problem but it conceivably could've been the same as similar to yours. Once I flashed the 10B TOT, all was well and when discussing with @xdabbeb, that's when he educated me that TOTs have more partitions than KDZs. I'm a diehard TOT fan ever since (I preferred KDZ when possible previously).
I know you already flashed the TOT but we're running out of ideas. If the MD5 hash of the 47A ROM and 35B Bootstack match what they're supposed to (listed on the Android File Host download page for each file). Make sure and
You should also get in the habit of flashing the appropriate Bootstack every time you flash a ROM, or after every time you restore a TWRP backup. Even if you know you're already on the 35B Bootstack - mind you, I'm not meaning this as "snake oil" or as a solution to the trouble you're having, and flashing it more than once won't change anything, but I just wanted to make sure you know this since some ROM's (JasmineROM and SkyDragon) include a partial Bootstack and can cause a brick (so the Bootstack should be flashed after the ROM in their case), and TWRP Backups/Restores don't backup or restore the entire set of partitions including in the Bootstack, so if you happen to be on a ROM that you were using the 24B Bootstack with, and restore a TWRP Backup of a 35B or higher ROM, you might not have a signal.
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
@andr0id187 I also want to be completely clear since I read back and I don't think you specified. Sorry for the repetetiveness but when you wipe before flashing, you're wiping Cache, Dalvik /ART and Data correct?
Click to expand...
Click to collapse
Yes, I'm doing the default TWRP wipe which includes all of the above(right?)
andr0id187 said:
Yes, I'm doing the default TWRP wipe which includes all of the above(right?)
Click to expand...
Click to collapse
No idea. As with backups it might default to what was chosen previously. I don't know what it defaults to on flash of TWRP from freshly rooted. I look at the list and make sure those three are checked everytime. Sometimes I wipe other things like internal storage or just Cache and Dalvik /ART so other times I want to make sure I have selected exactly what I want.