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?
Related
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
redpoint13 said:
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
Click to expand...
Click to collapse
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Don't you love those Asus emails telling you to flash things without any indication of consequences? That's why I didn't flash the one I was pmed.
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Seems to be a firmware update today just got it
Commodore 64
buxtahuda said:
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Click to expand...
Click to collapse
So it sounds like we are guaranteed to lose root then?
GreginNH said:
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Click to expand...
Click to collapse
The biggest thing for rooting to me was being able to install/use an ad-block program.
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Does it not work downloading and flashing 9.4.2.11 from asus' site and aquiring the .13 OTA that way?
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
*EDIT: Also, sorry, didn't meant to sound like a d'bag lol just trying to make sure some poor soul doesn't do a manual update thinking rootkeeper will work for them
buxtahuda said:
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
Click to expand...
Click to collapse
Good point..lmfao wasn't really thinkn of that. Exit stage right. Lol
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
AFAIK when you manually install "OTA" root keeper does not work, and seems like others are confirming this.
I just hope someone is able to quickly find another root exploit as fast as they did for .11.
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
I noticed that as well. 1st few times I hit it twice due to the delay which would end up turning it on and then back to standby/sleep
Moothead2 said:
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
Click to expand...
Click to collapse
Yes, also noticed it. We'll see if the .13 goes back to the quicker.
Duh!
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
What are the risks of this? I want to do this myself but I'm worried.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Trying now.
*RETARDED found both
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Even if this seems to work, I would be very worried about messing up the system. The OTAs are basically a patch file, and they only contain the changed bits of system files, not the whole files. (It's using bsdiff, if anyone cares.)
What this means is, if it's patching the wrong file because you lied about your version, it will very likely mess up your system - maybe even make it unbootable until you fix it with a full update.
Now, it's possible this update doesn't touch any files which changed between .11 and. 11.1, so it would be safe. But I wouldn't assume that.
buxtahuda said:
Trying now.
Click to expand...
Click to collapse
Any news? I.e. does it work or not?
I followed this thread to root: http://forum.xda-developers.com/showthread.php?t=2024207
I think I used the Root66 stock VRALJB I don't remember. My phone model number says SCH-I605, the Android version is 4.1.1, Baseband is I605VRALL4, Build number is JRO03C.I605VRALJB. I don't know if the kernel number is necessary because it's really long to type out, but if you need it I will post it.
Then I unlocked the Bootloader using AdamOutler's thread and now I have a custom TW recovery thing.
When I try to do the update in the Settings, it reboots to the TW recovery and doesn't do anything. When I select to turn on the phone with the TW recovery, it says the update failed. Someone told me that I shouldn't do that update because it's something called OTA and it's bad for my rooted phone, but then how do I know when I need an update? Do I have to check this forum every day for announcements? Which thread will the updates be in?
Thank you
The update option in settings is for Verizon OTA updates. OTA stands for over-the-air. The updates are sent to your phone using the Verizon data network. After the update is loaded onto your phone, it reboots into stock recovery to install the update. Since you have a custom recovery, (TWRP, I believe), the update will always fail. I see that you have the latest baseband, which is really the only reason for taking the OTA update to begin with.
Now that you have a custom recovery, you can flash any of the wonderful 4.1 ROMs that we have at our disposal. I'm currently on Jedi X11 and I recommend that, but there are more to choose from. One word of caution: if you decide to flash a 4.2 ROM, then you can't go back to a 4.1 ROM unless you flash the sd card downgrade .zip file. This is because 4.2 will change your directories around. I will try to link to a thread with the downgrade zip in it on another post.
---------- Post added at 02:40 PM ---------- Previous post was at 02:35 PM ----------
Here is the link to that thread. The downgrade .zip is in the third post
http://forum.xda-developers.com/showthread.php?t=2129787
I haven't installed a ROM because I want to keep all the stock stuff, but if there is a ROM that keeps all the stock but somehow increases speed, then I'd install it but I don't know of any that don't not have some stock stuff removed.
The annoying thing is that the phone keeps telling me to update every 3 days and I don't like it. Is there a way I can stop this without doing anything bad to the phone?
While it's true that all ROMs are not 100% stock, you have to ask yourself what you really want to keep. The ROM I'm running is Touchwiz-based, which means it has all the S-Pen apps along with true multi-window functionality. The stuff that I left coming from pure stock was mostly bloatware.
Either way, if staying on pure stock is all that you want and you want to stop receiving the OTA update notices, then you need to use an app that can freeze other apps. Freezing means that the app is disabled, will no longer appear in your app drawer, and will not start up when you boot the phone. I use Titanium Backup to freeze apps. I recommend freezing apps over outright deleting them because you may inadvertently soft brick your phone that way.
Once you have Titanium Backup or another app with the same functionality, then you need to find and freeze SDM 1.0. It was mentioned in this post here:
http://forum.xda-developers.com/showthread.php?t=2177551
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
I will add that I am not sure why you would unlock your bootloader if you didn't intend to flash any ROMs. The act of unlocking the bootloader is what took away your stock recovery and causes your OTA updates to fail when the installation process starts. You may want to research how to get your phone back to 100% stock if you want to be able to take updates in the future.
Couldn't find a clear answer to this... as we all know, Lollipop on the G3 is coming very soon, and i couldn't be more excited. However, i have my phone rooted and the TWRP[bump] recovery on my G3 and i just need to know, do i need to unroot in order to download and install the OTA update when it finally comes?
also, I currently have been using the G3 tweaks app with xposed framework and was wondering if that would cause me problems when the update happens.
Thanks in advance for your time guys.
You will need to .tot via Flashtool back to zv4. Firmware. You will get stuck in twrp. I would not advice just unrooting and flashing restore stock recovery .img. The guide is all over. Including files and walkthrough videos via YouTube. Its very painless.
Sent from rotary technology Phone
---------- Post added at 09:58 AM ---------- Previous post was at 09:55 AM ----------
I'm sure you'll hear of many warning you'll possibly to certainly lose root and or boot unlock if you ota. There will probably be flashable update to L soon. Up to you. I for 1 really don't worry. But many will. I have plenty of phones. Lol
Sent from rotary technology Phone
Or just wait for one of the Devs to bump it! I hope Engine95 gets ahold of it!! He rocks.
Updated to the zv6 this morning, lost root.. so ya you can take it over the air but prepare to reroot after
vincey2kr1 said:
Updated to the zv6 this morning, lost root.. so ya you can take it over the air but prepare to reroot after
Click to expand...
Click to collapse
Did the same. Rooted using Stumproot. After OTA to zv6, no more root. SuperSU states "There is no SU binary installed, and SuperSU cannot install it. ..."
How do you re-root? I tried running Stumproot again but it says that the phone is already rooted.
Thanks for the assistance.
racter said:
Did the same. Rooted using Stumproot. After OTA to zv6, no more root. SuperSU states "There is no SU binary installed, and SuperSU cannot install it. ..."
How do you re-root? I tried running Stumproot again but it says that the phone is already rooted.
Thanks for the assistance.
Click to expand...
Click to collapse
Maybe go back to ZV4 as Droid2drummer suggested. Then root.
Finally flash the BarRin-ZV6 ROM for a rooted LG G3 with the ZV6 software
Don't ever take an ota on rooted phones people..... Smh
^^^^^^^^^^^^ this. Duh.
Ok, so just to try it out (i'm not scared of softbricks) i did try to take the OTA update today that FINALLY came to my phone (i can only assume its the zv6 update, though it does not say) and let it install.. well it got me stuck in a TWRP bootloop. I managed to get back into the OS with a couple terminal commands but obviously i would not like to try that again and it did not successfully update and just remove root (as suggest it may above) so a fair warning to any future thread lurchers out there.
so on too my query,
if you lose root in zv6 and can't get it back.. will the same be true of lollipop? will we have to wait for a new root method?
and my second question is this; is there any way to simply unroot without actually flashing stock firmware? cause I CANNOT get the LG windows drivers to cooperate with me.. i install them and the phone still comes up with "drivers for this device not installed" in device manager. it says LGE Android Phone with the yellow driver error icon next to it.
the most important thing i need help with right now is getting those drivers working so i can unroot my phone to prepare for lollipop. i have the firmware, LG flash tool and .dll ready for the flash..
thanks for your responses thus far and any future help. i appreciate it.
Don't unroot just wait for the rooted zip to flash when it comes out..... Smh
ok... well if i'm waiting on that then how can i remove this pending update notification from my drawer? it let me click "later" a couple times but now its just a terribly annoying sticky that won't go away..
Remove OTA Update(and notification)
If an OTA notification is on your device you most likely already have the OTA file on your phone. If rooted, you can remove the OTA files and get rid of that annoying notification.
Updates are found in the /cache/ folder on your phone. Using a RootExplorer-type app(or ES File Explorer) browse to the root of your phone(NOT the root of your internal storage, /sdcard/, but the actual phone). If using ES File Explorer you may have to use the "show hidden files" option and grant the app root. You will see the update .zip file in cache if you did everything correctly. If no one has already uploaded the OTA zip.. copy the update to your sdcard and then upload for everyone else. Now delete the zip file from /cache/.
Deleting the file in /cache/ will get rid of the OTA but will not get rid of the notification. To get rid of notification:
1. Pull the notification shade down on your phone
2. Long press on the OTA notification until you see the App Info option pop up.
3. Click App Info and uncheck the Show Notifications box.
Thread: http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
thznutz87 said:
Don't ever take an ota on rooted phones people..... Smh
Click to expand...
Click to collapse
Noobs like myself would not know this "cardinal" rule.
BTW, I have updated on previous occasions via OTA without losing root.
There should be a noob forum regarding, post rooted precautions and expectations.
---------- Post added at 02:24 PM ---------- Previous post was at 02:15 PM ----------
thznutz87 said:
Don't unroot just wait for the rooted zip to flash when it comes out..... Smh
Click to expand...
Click to collapse
This probably the smartest advice that I seem given on this (throughout all various fora) topic.
Awesome advice.
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.
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.