The Official Release of KitKat 4.4.2 (NC4) for the Verizon Note 3 (SM-N900V) is now available and the official change log is HERE. However, that is the change log details changes from 4.3 to 4.4.2(NC4).
As someone who installed Beans pre-rooted version of the prior 4.4.2 leak (NC2), I'm curious as to the difference between the NC2 & NC4.
I haven't done any scientific tests, but NC4 certainly seems snappier and more responsive than the NC2 leak.
Also, I had three specific issues with the (NC2) build and all seem to be resolved in NC4...at least so far. First, the NC2 modem was worse than the MJ7 or MJE versions, but the NC4 modem seems as good, if not better than all the ohers. Second, the screen rotation would occasionally stop responding and get stuck in one mode or the other and only a reboot would fix it. And third, the auto brightness didn't work very well, if at all. After five (5) full days of running NC4 with Root I'm not having any issues and this seems to be the most stable and most responsive build yet. Also, battery use is almost identical to what I was getting before...although I probably have been using the phone more just testing it out and setting everything up the way I want it.
Also @anticloud pointed out that now when you setup your hotspot, if you select advanced options, you can now choose between creating a 2.4GHz and 5GHz hotspot. I don't believe that option was available before, but I never checked it in NC2.
Please post any info you have on undocumented changes from NC2 to NC4 and/or any personal experiences you've noticed between the two.
Thanks in Advance!
*** Take the advice of all the great developers and DO NOT install NC4 until they've had a chance to check it out and pre-root it! ***
Possible Visual Voicemail Issue
I did read that at least two users who installed NC4 are having issues with Visual Voice Mail.
edwmsjr said:
The Official Release of KitKat 4.4.2 (NC4) for the Verizon Note 3 (SM-N900V) is now available for download...no OTA yet.
As someone who installed Beans pre-rooted version of the prior 4.4.2 leak (NC2), I'm curious as to the difference between the two. I had three specific issues with the (NC2) build. First, the modem was worse than the MJ7 or MJE versions, so I reverted to those. Second, the screen rotation would occasionally stop responding and get stuck in one mode or the other and only a reboot would fix it. And third the auto brightness didn't work very well, if at all. So, I'm curious if any of those specific issues were addressed in the official release.
Please post any info you have on a change log for NC4 and/or any personal experiences you've noticed between the two.
Thanks in Advance!
*** Take the advice of all the great developers and DO NOT install NC4 until they've had a chance to check it out and pre-root it! ***
Click to expand...
Click to collapse
I haven't experienced either of these issues and I've be on NC2 since the leak came out.
edwmsjr said:
The Official Release of KitKat 4.4.2 (NC4) for the Verizon Note 3 (SM-N900V) is now available for download...no OTA yet.
As someone who installed Beans pre-rooted version of the prior 4.4.2 leak (NC2), I'm curious as to the difference between the two. I had three specific issues with the (NC2) build. First, the modem was worse than the MJ7 or MJE versions, so I reverted to those. Second, the screen rotation would occasionally stop responding and get stuck in one mode or the other and only a reboot would fix it. And third the auto brightness didn't work very well, if at all. So, I'm curious if any of those specific issues were addressed in the official release.
Please post any info you have on a change log for NC4 and/or any personal experiences you've noticed between the two.
Thanks in Advance!
*** Take the advice of all the great developers and DO NOT install NC4 until they've had a chance to check it out and pre-root it! ***
Click to expand...
Click to collapse
I've definitely been hitting the screen rotation and auto brightness bugs. Hopefully, those are addressed in NC4
pinhead10 said:
I've definitely been hitting the screen rotation and auto brightness bugs. Hopefully, those are addressed in NC4
Click to expand...
Click to collapse
I as well have seen the autobrightness bug.. It seems to fix itself on a reboot for me, but irks me a bit. Screen sometimes is #1 in list of Barry draining apps.
I'm pulling OTA right now.
i wish this thread had a "?" at the end of the title. with 700+ views i cant be the only one expecting to see the NC4 change log posted LOL
Agree please rephrase you post topic because that's false information. There is no change log here
Sent from my SM-N900V
Okay...I heard ya and added a question mark at the end of the title. I assumed...and I figured we all did...that there would never be an 'official' change log posted by Samsung or VZW noting the changes from an unofficial, leaked firmware to a final, official version. That's why I wanted to create a forum where end users could document the changes they've noticed. Sorry for the confusion and misleading original title!
UPDATE: I changed the title again because we now actually have an "official VZW change log" which is available in the original post of this thread (Thanks @klittle81). However, I still would like to have users share their experiences from NC2 to NC4...which was my original intention anyway.
edwmsjr said:
Okay...I heard ya and added a question mark at the end of the title. I assumed...and I figured we all did...that there would never be an 'official' change log posted by Samsung or VZW noting the changes from an unofficial, leaked firmware to a final, official version. That's why I wanted to create a forum where end users could document the changes they've noticed. Sorry for the confusion and misleading original title!
Click to expand...
Click to collapse
I think what he meant is like how me and probably others were thinking, this thread had a change log from 4.3 to 4.4.2 NC4. Thats what I thought.
On the other thread a user is claiming by turning on survival mode on SU he was able to upgrade and keep root. Have any of you that have upgraded tried that and did it work?
amebiasis said:
I think what he meant is like how me and probably others were thinking, this thread had a change log from 4.3 to 4.4.2 NC4. Thats what I thought.
On the other thread a user is claiming by turning on survival mode on SU he was able to upgrade and keep root. Have any of you that have upgraded tried that and did it work?
Click to expand...
Click to collapse
Yeah, I get that now. I didn't really think about it at first because change logs for 4.4.2 from 4.3 have been out since January pretty much everywhere.
I was going to try the OTA with Survival mode, but when I go to "software update" from "about phone", I get the message "unfortunately, settings has stopped". I'm running the pre-rooted stock 4.4.2 NC2 prepared by Beans. I assume he disabled it to prevent people from taking OTA's by mistake.
edwmsjr said:
Yeah, I get that now. I didn't really think about it at first because change logs for 4.4.2 from 4.3 have been out since January pretty much everywhere.
I was going to try the OTA with Survival mode, but when I go to "software update" from "about phone", I get the message "unfortunately, settings has stopped". I'm running the pre-rooted stock 4.4.2 NC2 prepared by Beans. I assume he disabled it to prevent people from taking OTA's by mistake.
Click to expand...
Click to collapse
Ya I'm pretty sure I read somewhere he DID remove it for that "just in case" scenario.
amebiasis said:
Ya I'm pretty sure I read somewhere he DID remove it for that "just in case" scenario.
Click to expand...
Click to collapse
So, that leads to some questions about the people who are saying that they've installed the OTA with Survival Mode in SU. They must be rooted if they've got SU, but most devs remove the ability to do OTA's...so what gives. Are they rooted on 4.3 or 4.4.2(NC2)...and what rom, if any are they running that allows OTA's? Just thinking out loud...
I'm interested to see if they enabled the XLTE on the Note 3 since the M8 and S5 require software update....maybe that's why it took so long to get it.
Sent from my SM-N900V using Tapatalk
neopolotin75 said:
I'm interested to see if they enabled the XLTE on the Note 3 since the M8 and S5 require software update....maybe that's why it took so long to get it.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
If you search through the general forum here there's a big thread on aws we can enable it now I'm 99% sure of through a hidden menu. I'm not sure if root is required but I remember guys saying they enabled it already.
edwmsjr said:
So, that leads to some questions about the people who are saying that they've installed the OTA with Survival Mode in SU. They must be rooted if they've got SU, but most devs remove the ability to do OTA's...so what gives. Are they rooted on 4.3 or 4.4.2(NC2)...and what rom, if any are they running that allows OTA's? Just thinking out loud...
Click to expand...
Click to collapse
The stock rooted latest 4.3 ROM with all boat intact and no theme or any file tampering will allow the 4.4.2 OTA......but if you have any bloat removed or tampered with any system UI or framework files it will fail....so that why some people prefer to freeze bloat instead of deleting it so they can unfreeze it and accept a ota.....If you modded your device and want to ota with root survival mode, your best bet is to back up any internal storage data, do a fresh install of stock 4.3 MJE tar through odin, root using a MJE approved root method...do not modify or debloat anything.....check ota survival in super su app...take the OTA with your fingers crossed cause there is no guarantee. ...now welcome to a secured kernel and no way to revert back to 4.3 to root if it didn't survive..lol
Sent from my SM-N900V using Tapatalk
Janker5050 said:
The stock rooted latest 4.3 ROM with all boat intact and no theme or any file tampering will allow the 4.4.2 OTA......but if you have any bloat removed or tampered with any system UI or framework files it will fail....so that why some people prefer to freeze bloat instead of deleting it so they can unfreeze it and accept a ota.....If you modded your device and want to ota with root survival mode, your best bet is to back up any internal storage data, do a fresh install of stock 4.3 MJE tar through odin, root using a MJE approved root method...do not modify or debloat anything.....check ota survival in super su app...take the OTA with your fingers crossed cause there is no guarantee. ...now welcome to a secured kernel and no way to revert back to 4.3 to root if it didn't survive..lol
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
So my tether provisioning hack and wanam xposed probably will make it fail?
I kept a copy of the original tether file. I can uninstall xposed...
Hmmm...
As for backing up internal data, any recommendations? I find Titanium Backup too confusing to use.
amebiasis said:
If you search through the general forum here there's a big thread on aws we can enable it now I'm 99% sure of through a hidden menu. I'm not sure if root is required but I remember guys saying they enabled it already.
Click to expand...
Click to collapse
Yea I saw that thread and it had to be enabled manually but I was meaning if it would be enabled from Verizon and us not needing to hack it.
Sent from my SM-N900V using Tapatalk
I'm not sure if they will post a change log from NC2 -> NC4 but here I found this for NC4.. Pretty much says here is KitKat with updated bloatware...LOL
Update Features
http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy-note-3-05-13-14.pdf
Update Instructions
http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy-note-3-instructions-05-13-14.pdf
I just got my Note 3 today and took the OTA without even thinking. Now I'm on NC4 and absolutely no root methods are working for me. Anyone have any ideas? I tried all 3 stock ROMs, which failed. The unsupported root methods failed, through both download mode and normal. And the NC2 root ROM failed in Odin.
Related
All:
I have my note II rooted, and its running 4.1.2
I received the OTA today, and I chose not to download it. Just curious on what folks are doing ?
I dont run any custom rom on my Note II, I just use it for rooting purposes....
if I do want to upgrade to 4.3 what is the suggested path of action ?
I thought I could use wugfresh I guess not though ?
Thanks
ch3ss said:
All:
I have my note II rooted, and its running 4.1.2
I received the OTA today, and I chose not to download it. Just curious on what folks are doing ?
I dont run any custom rom on my Note II, I just use it for rooting purposes....
if I do want to upgrade to 4.3 what is the suggested path of action ?
I thought I could use wugfresh I guess not though ?
Thanks
Click to expand...
Click to collapse
Once you upgrade to 4.3 OTA, your bootloader is locked and root is gone, along with the generally unwelcome addition of Samsung's KNOX technology. No bootloader exploit currently exists. If you upgrade by flashing one of the ROM's here on XDA or the non-OTA update to 4.3 (check the Android Development forum), you get the latest software and keep an unlocked bootloader & root.
computerslayer said:
Once you upgrade to 4.3 OTA, your bootloader is locked and root is gone, along with the generally unwelcome addition of Samsung's KNOX technology. No bootloader exploit currently exists. If you upgrade by flashing one of the ROM's here on XDA or the non-OTA update to 4.3 (check the Android Development forum), you get the latest software and keep an unlocked bootloader & root.
Click to expand...
Click to collapse
Wife gave me my Christmas present yesterday...(a Note 2 she bought used...lovely phone). It started an update when I fired it up, (has been so long since I rooted my Bionic, I completely forgot about OTA's) It now has 4.3, and the only sort of tethering I can mange with it is usb pdanet, which merely qualifies as 'better than nothing', as it often drops out. Might have to put the damn thing in a drawer and fire up the Bionic until the tech gods here work it out. Am downloading a zip from another thread mentioned by Tfly12 that purports to get around the entitlement check...will see
Mejud said:
Wife gave me my Christmas present yesterday...(a Note 2 she bought used...lovely phone). It started an update when I fired it up, (has been so long since I rooted my Bionic, I completely forgot about OTA's) It now has 4.3, and the only sort of tethering I can mange with it is usb pdanet, which merely qualifies as 'better than nothing', as it often drops out. Might have to put the damn thing in a drawer and fire up the Bionic until the tech gods here work it out. Am downloading a zip from another thread mentioned by Tfly12 that purports to get around the entitlement check...will see
Click to expand...
Click to collapse
Can't flash that zip though can ya? Trust me. Loosing tethering is the biggest thing that ticks me off about 4.3.
Hate having to have an nonroot phone for work.
Nefariouss said:
Can't flash that zip though can ya? Trust me. Loosing tethering is the biggest thing that ticks me off about 4.3.
Hate having to have an nonroot phone for work.
Click to expand...
Click to collapse
not sure yet, my last experience with this was the Bionic....and after I got it doing what I wanted it to do.....never bothered with it again. Now I'm trying to learn everything Samsung, (precious little of Motorola knowledge seems to apply here....I always thought Odin was a Viking god...) so I don't end up in one of those frantic "HELPME! MY PHONEWON'TEVENTURNONANYMOREIHATEYUPEOPLE" posts....
computerslayer said:
Once you upgrade to 4.3 OTA, your bootloader is locked and root is gone, along with the generally unwelcome addition of Samsung's KNOX technology. No bootloader exploit currently exists. If you upgrade by flashing one of the ROM's here on XDA or the non-OTA update to 4.3 (check the Android Development forum), you get the latest software and keep an unlocked bootloader & root.
Click to expand...
Click to collapse
Seems like I should wait then... It tried to download and install last night but it failed, so it just rebooted and i am good... probably because i have recovery on... not sure....
I prefer to honestly just go back to stock, and then maybe goto 4.3 once there is a good root out there....
Mejud said:
not sure yet, my last experience with this was the Bionic....and after I got it doing what I wanted it to do.....never bothered with it again. Now I'm trying to learn everything Samsung, (precious little of Motorola knowledge seems to apply here....I always thought Odin was a Viking god...) so I don't end up in one of those frantic "HELPME! MY PHONEWON'TEVENTURNONANYMOREIHATEYUPEOPLE" posts....
Click to expand...
Click to collapse
I made the same move after my speaker started going on my BIONIC, fortunately for me I made the move to the N2 a few months ago. If you are lucky and someone is able to get the bootloader unlocked on 4.3, you should find this device much easier to work with then using Safestrap and all that other jazz. Odin is sort of like using HOB except I have only had to use it twice and not constantly. Once to unlock the bootloader initially and just recently to update the modem and wifi parameters when I made the move to 4.3
Hopefully someone can help you get set up to use the N2 the way you need it.
Q&A for [ROM][Official][4.4.4] CyanogenMod 11.0 Nightlies for the Verizon Galaxy S4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Bluetooth fixes in VRUFNG6
I saw today that Verizon released an updated build (VRUFNG6) that supposedly contains bluetooth fixes. Does anyone know if these are going to be Touchwiz-specific and/or if they could be pulled and incorporated into the current CM11 nightlies?
Many are reporting terrible bluetooth connectivity and related issues, so just thought I'd ask.
consultcory said:
I saw today that Verizon released an updated build (VRUFNG6) that supposedly contains bluetooth fixes. Does anyone know if these are going to be Touchwiz-specific and/or if they could be pulled and incorporated into the current CM11 nightlies?
Many are reporting terrible bluetooth connectivity and related issues, so just thought I'd ask.
Click to expand...
Click to collapse
They have been "kangbanged" from NF3 and merged today. You can see this awesome goodness in the 10/13 nightly.
See here:
http://www.cmxlog.com/11/jflte/
Look under to be included in next nightly. The new camera fix has also been merged.
Post Content Edited. Sorry, I was frustrated and had a moment of weakness.
The silence is deafening.
Just load m9. It's perfect. Eventually you'll lose the urge to Crackflash and enjoy your s4 for what it is (a pretty good 2 year old phone).
There are 4 v*rizon phones out there that 'do it for me'. I just need to figure out which one is the least 'Verizoned'. In really not too anxious though. I like my s4.
Installing Cyanogen on Verizon Galaxy S4
Hello all,
Now that this NG6 update recently pushed to my phone has made it practically unusable, I've decided it might be time to install a custom ROM. Alas, the handy Cyanogen "one-click" installer does not support my phone Since I'm new to this and really afraid of bricking my phone, I've come here just to get some assurance.
I've seen this post which gives instructions on how to install, but one thing concerns me. This link from the CM website gives pretty different instructions, and moreover adamantly warns that the build version of your phone must be I545VRUAMDK, which mine is not. Why the discrepancy in instructions?
Why is installing an alternate kernel necessary to obtain a root? Can Towelroot not be used (does that app involve installing an alternate kernel)? Is the motochopper app listed necessary to root the device in a "certain way"? Is the clockwork app the only CM supported app to make a recovery image, or can I use another standard like TWRP? And what part of this process that they list absolutely requires you to be on that build version???
I know, I have no idea what I'm doing. Please advise, or at least point me in the right direction! Also, I know the original post says that asking about rooting is off topic here, but it's only part of my question, and sort of relevant in this case because the official CM installation instructions suggest some kind of compatibility concern.
Many thanks!
I am running CM11 Nightly and the only modification I have made to the actual file system is deleting the DSP Manager apk in system/app because it was taking precedence over other equalizer apps I was trying out. Long story short, I couldn't find an equalizer that boosted the bass correctly as well as the equalizer built into the stock S4 Touchwiz did. So, I reflashed the DSP Manager apk through CWM. Now, neither Google Play Music nor Apollo will play my music on the external SD card. And for my last question, why are no equalizers working correctly with bass boost? When I have either a preset or use the bass booster slider bar in any equalizer (including DSP Manager) it just makes my music crackle. Its not my headphones either, as they worked perfectly on Touchwiz. Thanks in advance for your reply.
evesira said:
Hello all,
Now that this NG6 update recently pushed to my phone has made it practically unusable, I've decided it might be time to install a custom ROM. Alas, the handy Cyanogen "one-click" installer does not support my phone Since I'm new to this and really afraid of bricking my phone, I've come here just to get some assurance.
I've seen this post which gives instructions on how to install, but one thing concerns me. This link from the CM website gives pretty different instructions, and moreover adamantly warns that the build version of your phone must be I545VRUAMDK, which mine is not. Why the discrepancy in instructions?
Why is installing an alternate kernel necessary to obtain a root? Can Towelroot not be used (does that app involve installing an alternate kernel)? Is the motochopper app listed necessary to root the device in a "certain way"? Is the clockwork app the only CM supported app to make a recovery image, or can I use another standard like TWRP? And what part of this process that they list absolutely requires you to be on that build version???
I know, I have no idea what I'm doing. Please advise, or at least point me in the right direction! Also, I know the original post says that asking about rooting is off topic here, but it's only part of my question, and sort of relevant in this case because the official CM installation instructions suggest some kind of compatibility concern.
Many thanks!
Click to expand...
Click to collapse
Since it sounds like you updated to NG6 via a VZW OTA update CyanogenMOD is unfortunately out of your reach. CM needs a custom recovery such as CWM or TWRP and they can only be installed on a GS4 that is running the MDK bootloader. The later versions are locked down and only a SafeStrap compatible ROM can be installed.
FernBch said:
Since it sounds like you updated to NG6 via a VZW OTA update CyanogenMOD is unfortunately out of your reach. CM needs a custom recovery such as CWM or TWRP and they can only be installed on a GS4 that is running the MDK bootloader. The later versions are locked down and only a SafeStrap compatible ROM can be installed.
Click to expand...
Click to collapse
Thank you for the response. I actually solved my problems a couple of days ago. I'll post them here for posterity.
Regarding those Cyanogen instructions, they say that you should only attempt this on the MDK build, but they don't say why. Are the particular tools they suggest using incompatible? No, Cyanogen itself is only compatible with the MDK build of the I545 Verizon S4 (US), for the reasons that Fern explained above. Took me some forum snooping to actually determine that one.
For those who are going through the horrors of the NG6 update, but don't want to wait until the rumored fix in early December, do what I did. See this thread:
http://forum.xda-developers.com/showthread.php?t=2735172
The no-wipe version didn't work for me unfortunately. It booted with all my stuff still in tact, but errors constantly popped up making the phone unusable. I had to do the full wipe, which gets rid of all your apps and personal data (unless it's on the SD card I believe). So try the no-wipe first, and if it doesn't work, back up all your data and apps, then do the full wipe.
Download Odin 3.09 (no need to root first), and use the full wipe ROM from the thread and watch the video for instructions. That will get you back to NC5, the previous working version before the NG6 fiasco. However, you still need a way to stop the update from happening again. Oddly, some users get a "no thanks" option, but I didn't get that. I had to root, which I had never done before. On your phone, google towelroot, go to the site, click the lambda, download it, install it (in settings allow android to install apps from unknown locations other than the app store), press "make it rain". Still on your phone, install SuperSU from the app store and go through that process. Then buy the Titanium Backup Pro app from the app store, find the SDM.apk, and freeze it. This should stop the update prompt from happening!
Now that you had to wipe your phone and root it (possibly for the first time if you're like me), reinstall all your old apps and move your data back. And since you're now rooted, you might as well take advantage of it. Download the Xposed framework, and install some useful modules for it like Wanam, NoMapTips, Disable Clear Defaults Dialog, and more. Then you can get rid of a lot of annoying TouchWiz bull**** like "loud volume can damage your hearing" warning, low battery warning, and etc.
Hopefully this helps someone who has no Android "modding" experience like myself, and saves them some research.
Cheers
For clarity, the reason that you can only run CM on a MDK device is the MDK bootloader is the only one that can be exploited by a process called loki to allow flashing a custom recovery. All later bootloaders have had this exploit blocked (Thank Big Red). Because of this the only option is SafeStrap. On MDK ONLY this allows one to flash custom kernels and recoveries which are required in order to flash any AOSP ROM such as CyanogenMOD.
Cm11 m12/rc1
I can't remember where, but I read something about the next milestone build being available around November 7th, and that it may even be labeled as a release candidate instead. Obviously there's been no such release and the CyanogenMod blog hasn't been updated in almost a month.
Has anyone heard anything about a release date for M12/RC1?
consultcory said:
I can't remember where, but I read something about the next milestone build being available around November 7th, and that it may even be labeled as a release candidate instead. Obviously there's been no such release and the CyanogenMod blog hasn't been updated in almost a month.
Has anyone heard anything about a release date for M12/RC1?
Click to expand...
Click to collapse
I guess I should have just waited a day... M12 is now up!
At first glance on the download web page, I thought Galaxy S4 version is unsupported since the begining of the year. You should really post the information that you are building unified build to the download page.
xuhdev said:
At first glance on the download web page, I thought Galaxy S4 version is unsupported since the begining of the year. You should really post the information that you are building unified build to the download page.
Click to expand...
Click to collapse
Its hard to miss on the first page of the thread.
" CyanogenMod:
Nightly:*http://download.cyanogenmod.org/?dev...w&type=nightly
As of 20140218 we are doing unified builds. Get them here:
Unified Nightly:* http://download.cyanogenmod.org/?dev...e&type=nightly "
Sent from my SCH-I545 using Tapatalk
TMYINC said:
Its hard to miss on the first page of the thread.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
If you know Cyanogenmod, you would probably go to the cyanogenmod download page directly but not visit from here, right?
xuhdev said:
If you know Cyanogenmod, you would probably go to the cyanogenmod download page directly but not visit from here, right?
Click to expand...
Click to collapse
I do know CM. That's why I know the download page has been different since Feb. 18th. I always stay I'm touch here for updates, bug reports, or just to answer questions. I wasn't trying to be rude.
Sent from my SCH-I545 using Tapatalk
TMYINC said:
I do know CM. That's why I know the download page has been different since Feb. 18th. I always stay I'm touch here for updates, bug reports, or just to answer questions. I wasn't trying to be rude.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I'm not saying you don't know. "You" means someone. Not everyone sees xda as official document; neither do I. But I found the official wiki, so the problem I mentioned should not be a problem.
Deleted
I read that some are unable to root ZV6. I can't even install it...
My Device: Sprint LG G3 LS990
Root: One click stump root.
ROM: Stock everything else (ROM, Kernel).
Tweaks: Very slight modifications to the phone (increased volume, changed boot animation and added some dual screen apps).
I am having a problem INSTALLING the OTA update. My phone keeps downloading it but after I select install and it reboots (after looking like it installed) I am still at the ZV4 version ( KVT49L . LS990ZV4 ) , not the new ZV6...
Any tips? Is the rooting of the phone the problem?
NOTE: I only rooted to be able to make a few tweaks...
Thanks!
If you want ZV6, then you need to look...
http://forum.xda-developers.com/showthread.php?p=54912191
http://forum.xda-developers.com/showthread.php?p=55225699
And
http://forum.xda-developers.com/showthread.php?p=57185864
Thanks for taking the time to reply. Interesting response...
Why would I need ZV6?
I already said that I am receiving the OTA. My problem is NOT needing the update but INSTEAD HOW DO I GET IT INSTALLED.
Please elaborate... Did you misunderstand my problem? TL;DR? Or did you mean to say that I will need to flash?
??
Thanks
Doug
Sent from my Sprint LG G3 - not responsible for random incorrect words due to crappy auto correct...
OldDogEyes said:
Thanks for taking the time to reply. Interesting response...
Why would I need ZV6?
I already said that I am receiving the OTA. My problem is NOT needing the update but INSTEAD HOW DO I GET IT INSTALLED.
Please elaborate... Did you misunderstand my problem? TL;DR? Or did you mean to say that I will need to flash?
??
Thanks
Doug
Sent from my Sprint LG G3 - not responsible for random incorrect words due to crappy auto correct...
Click to expand...
Click to collapse
In all those threads I linked above answers all of your questions.
There is no root for ZV6.
If you have root on ZV4 you can't take the update.
If you want to update to ZV6 and still have root, then you'll need to unlock your phone so you can flash a Rom linked above.
You're actually lucky the OTA didn't install. Quite a few people have soft-bricked their phones trying to install the OTA on a rooted, modified device. Either flash the stock ZV4 using LG's flashtool and take the OTA (which can't be rooted), or install TWRP and then the pre-rooted ZV6 linked to above.
In the future, never, ever, take an OTA when rooted.
meyerweb said:
In the future, never, ever, take an OTA when rooted.
Click to expand...
Click to collapse
Thanks.. How do I get rid of the persistent notification that can't be dismissed that wants me to reboot to install?
Is there any way to block the update from being downloaded? Are the ZV6 security fixes critical?
Thanks again...
Sent from my Sprint LG G3 - not responsible for random incorrect words due to crappy auto correct...
In the 3rd link I posted. Read that post and the one below it.
It'll tell you how to remove it and how to disable the notifications.
ZV6 runs a lot better than ZV4 out of the box.
OldDogEyes said:
Thanks.. How do I get rid of the persistent notification that can't be dismissed that wants me to reboot to install?
Is there any way to block the update from being downloaded? Are the ZV6 security fixes critical?
Click to expand...
Click to collapse
I wouldn't call ZV6 critical, but it does contain quite a few bug fixes and other minor improvements. The best way, IMHO, would be to install either the stock ZV6 ROM through TWRP:
http://forum.xda-developers.com/sprint-lg-g3/development/rom-stock-zv6-base-odex-deodex-t2949087
Or flash BarRin, a debloated, slightly tweaked stock ZV6 ROM:
http://forum.xda-developers.com/sprint-lg-g3/development/rom-barrin-odexed-deodexed-t2950747
Since these are both ZV6, the updater will see you on ZV6 and not prompt you to update.
Because you may have made built.promp mods
So I've had the phone for less than a week. I've performed the ioroot procedure and installed twrp. Other than that, the phone is stock right now - 10B. I've performed a backup.
My phone is offering to install 11C. I'd like to update to that version, but at a glance it seems like there may be issues if I ever need to downgrade, or.. I may lose root.
So, for our specific phone, the VS985 model, what is the best way to upgrade to the latest stock ROM and keep root / the ability to downgrade?
Sorry for the noob question, but I'm new to the phone and am seeing some conflicting information, probably due to variances between different versions of the phone. I just want to do this right the first time and avoid having to ask more dumb questions
Look for the thread by bweN diorD in either General or Q&A that starts with [REF] and has img or images in the title.
Use the links in that thread to flash the 12b modem and system images, using autoprime's flash2Modem and flash2System zips (bweN links to that thread).
Your choice on whether you also want to flash the 12b boot image. I did flash the 11c boot, didn't bother with 12b.
After flashing the new images, anything you've tweaked in /system has to be re-nudged -- freezing verizon bloat, freezing "System updates..." (or renaming the /system/app LGDMSClient files), reinstalling the hotspot mod (if you need it). It's a pretty painless evolution.
(Definitely freeze System updates.... Once you've got twrp, if you try to install an OTA directly you'll get stuck in a boot-to-recovery problem. Autoprime has a flashable zip that wipes out the files causing the boot-to-recovery, I keep a copy of that zip loaded on my phone's user volume, but it's simpler to just not try to install an OTA.)
Wow. Okay. Thanks a lot. This is super helpful. I'm downloading as we speak. I hope you don't mind a followup question...
My understanding is that it is safer to avoid flashing the boot image because changes to the bootloader could affect root or the ability to roll back. Is there a reason you bothered flashing 11C?
For anyone else, the thread mentioned is: http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
NegativeOne said:
Wow. Okay. Thanks a lot. This is super helpful. I'm downloading as we speak. I hope you don't mind a followup question...
My understanding is that it is safer to avoid flashing the boot image because changes to the bootloader could affect root or the ability to roll back. Is there a reason you bothered flashing 11C?
For anyone else, the thread mentioned is: http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
Click to expand...
Click to collapse
There is no downside to flashing it at this point, but I haven't seen proof there is any benefit either. I'm still on 10b running L ROMs no problem, so I don't see any point in updating anything but the modem.
Sent from my G3, rockin Illusion
Which rom are you using?
Look down lol
Sent from my G3, rockin Illusion
You can root 10B and tell supersu to maintain root and take all the OTAs and still keep root. I did that so that I'd have VoLTE and I could take an OTA in the future without issue if it was shown root would survive. Your choice I guess, but we know root survives all the way to 12B so why not go the stock route to ensure you are fully updated? Just my thoughts anyway.
Schaweet said:
You can root 10B and tell supersu to maintain root and take all the OTAs and still keep root. I did that so that I'd have VoLTE and I could take an OTA in the future without issue if it was shown root would survive. Your choice I guess, but we know root survives all the way to 12B so why not go the stock route to ensure you are fully updated? Just my thoughts anyway.
Click to expand...
Click to collapse
im running android version 5.0.2, stock is whats not "fully updated" lol
bweN diorD said:
im running android version 5.0.2, stock is whats not "fully updated" lol
Click to expand...
Click to collapse
Yeah we all could be as well. The issue is your camera is jacked and you lose things like multi window, ir remote, and quick memo writing.
I tried 5.0.x for a few days but the negatives weren't worth it to me. I am fully updated at 12B as I can still use the G3 with the stock goodies that were added by LG and not cripple the device by putting AOSP on it. Don't get me wrong, I prefer the look of AOSP, but one of the major reasons I got this phone was for the camera and without the 5.0.x roms including LG camera app with them, it's a no go for me. Google camera app just doesn't do it and laser focus is gone so pics are crap in my opinion.
Instead I use g3 tweaks and Nova to make my phone look more like AOSP. I'll wait for the devs to get ahold of 5.0.x for the g3 so we can still keep the g3 goodies before I update any further.
So, I'd say 12B is as fully updated as there is at this point. Just my opinion though.
Schaweet said:
Yeah we all could be as well. The issue is your camera is jacked and you lose things like multi window, ir remote, and quick memo writing.
I tried 5.0.x for a few days but the negatives weren't worth it to me. I am fully updated at 12B as I can still use the G3 with the stock goodies that were added by LG and not cripple the device by putting AOSP on it. Don't get me wrong, I prefer the look of AOSP, but one of the major reasons I got this phone was for the camera and without the 5.0.x roms including LG camera app with them, it's a no go for me. Google camera app just doesn't do it and laser focus is gone so pics are crap in my opinion.
Instead I use g3 tweaks and Nova to make my phone look more like AOSP. I'll wait for the devs to get ahold of 5.0.x for the g3 so we can still keep the g3 goodies before I update any further.
So, I'd say 12B is as fully updated as there is at this point. Just my opinion though.
Click to expand...
Click to collapse
the camera doesnt stand up to stock, no doubt, but thats the only thing i wish could be better. the rest of that stuff i dont use.
it all depends on what you want/use/need.
i prefer custom roms the majority of the time.
bweN diorD said:
the camera doesnt stand up to stock, no doubt, but thats the only thing i wish could be better. the rest of that stuff i dont use.
it all depends on what you want/use/need.
i prefer custom roms the majority of the time.
Click to expand...
Click to collapse
You're right for sure. It's all personal preference. I figure if the only thing that looks different from stock is the settings menu and not having the quick settings tiles, I'm close enough that I'm not bothered by all the LG colors and added stuff.
I'm waiting for the camera app to get ported then I'm all in on a custom 5.0.x rom. That may be a while, but I can wait.
Schaweet said:
Yeah we all could be as well. The issue is your camera is jacked and you lose things like multi window, ir remote, and quick memo writing.
Click to expand...
Click to collapse
For anyone reading this, I just wanted to let them know that there is a ported version of Quick Remote that works under AOSP / CM including Lollipop. I think it's in the non-variant G3 sections.
Sent from my VK810 4G
Thank you for this thread. Honestly this should be Pinned, I am an extremely saavy/experienced Android user and XDA forum member, and I could not believe how long it took me to find this sort of info for such a popular phone.
This is my first LG phone, and I'm having to learn all the LG and Gseries specific "stuff". The info above was invaluable. :good:
So I have had my S4 since about a month after launch. Not long afterwards I received the OTA notification. I rejected it and froze the SDM.APK and stopped getting the notification. Fast-forward to recently. I am thinking about getting a stereo for my truck that has Google Auto, but my phone is not compatible. I believe it is because I am running version 4.2.2. Is there a way that I can upgrade to Lollipop, keep root and keep my current apps installed?
Thanks,
Dan
bumpncarstereo said:
So I have had my S4 since about a month after launch. Not long afterwards I received the OTA notification. I rejected it and froze the SDM.APK and stopped getting the notification. Fast-forward to recently. I am thinking about getting a stereo for my truck that has Google Auto, but my phone is not compatible. I believe it is because I am running version 4.2.2. Is there a way that I can upgrade to Lollipop, keep root and keep my current apps installed?
Thanks,
Dan
Click to expand...
Click to collapse
Best thing you can do is install the Custom CyanogenMod 13 ROM for S4 KitKat.
Sent from my SCH-I545 using Tapatalk
bumpncarstereo said:
So I have had my S4 since about a month after launch. Not long afterwards I received the OTA notification. I rejected it and froze the SDM.APK and stopped getting the notification. Fast-forward to recently. I am thinking about getting a stereo for my truck that has Google Auto, but my phone is not compatible. I believe it is because I am running version 4.2.2. Is there a way that I can upgrade to Lollipop, keep root and keep my current apps installed?
Thanks,
Dan
Click to expand...
Click to collapse
chaotic_jose said:
Best thing you can do is install the Custom CyanogenMod 13 ROM for S4 KitKat.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
If you're still on MDK bootloader, you can flash TWRP and then install a custom ROM. CM 13 works. I also like OctOS 6.0.
If you're on any other bootloader, however, you're stuck with safestrap and TouchWiz-based ROMs.
flamadiddle said:
If you're still on MDK bootloader, you can flash TWRP and then install a custom ROM. CM 13 works. I also like OctOS 6.0.
If you're on any other bootloader, however, you're stuck with safestrap and TouchWiz-based ROMs.
Click to expand...
Click to collapse
How do I find out what bootloader I am on? In the about phone it says "Secure Boot Status Type Samsung" Also my baseband Version is I545VRUAME7
If my research so far is correct, looks like I am stuck with safestrap and touchwiz based roms?
It may matter, I am on Verizon.
Thanks
Dan
bumpncarstereo said:
How do I find out what bootloader I am on? In the about phone it says "Secure Boot Status Type Samsung" It may matter, I am on Verizon.
Thanks
Dan
Click to expand...
Click to collapse
When you go to Settings --> About Phone, the last three letters of your Baseband version are what we're talking about. If it ends with MDK, you can bypass the security checks on the locked bootloader via the Loki patch.
Edit
Just saw your update. Yeah, you have the ME7 bootloader, which means you're out of luck for non-TW ROMs. Sorry. Check the ROM List for Safestrap-compatible ROMs. The Safestrap thread has instructions on how to use it.
flamadiddle said:
When you go to Settings --> About Phone, the last three letters of your Baseband version are what we're talking about. If it ends with MDK, you can bypass the security checks on the locked bootloader via the Loki patch.
Edit
Just saw your update. Yeah, you have the ME7 bootloader, which means you're out of luck for non-TW ROMs. Sorry. Check the ROM List for Safestrap-compatible ROMs. The Safestrap thread has instructions on how to use it.
Click to expand...
Click to collapse
Thanks for the information.
flamadiddle said:
When you go to Settings --> About Phone, the last three letters of your Baseband version are what we're talking about. If it ends with MDK, you can bypass the security checks on the locked bootloader via the Loki patch.
Edit
Just saw your update. Yeah, you have the ME7 bootloader, which means you're out of luck for non-TW ROMs. Sorry. Check the ROM List for Safestrap-compatible ROMs. The Safestrap thread has instructions on how to use it.
Click to expand...
Click to collapse
Famadiddle
I installed safestrap with no problem. I am looking at the list of available roms and there doesn't appear to be many options for me. I am coming from a stock 4.2.2 and it seems that they require you to come from 4.4.x, the one that specifically say ME7, the download link was out of date. Am I misinterpreting the pre-req's? With a custom rom, do you have to stay within your version? IE i have to stay 4.2.2, and I can't go to 4.4?
Thanks again.
Edit,
So I bit the bullet and installed this one here:
http://forum.xda-developers.com/showthread.php?t=2415780
don't really see what all the commotion was about. everything was still the same, seems to have installed over top of my stock rom. It did install something though because the about phone screen has different stuff in it.
Dan
bumpncarstereo said:
Famadiddle
I installed safestrap with no problem. I am looking at the list of available roms and there doesn't appear to be many options for me. I am coming from a stock 4.2.2 and it seems that they require you to come from 4.4.x, the one that specifically say ME7, the download link was out of date. Am I misinterpreting the pre-req's? With a custom rom, do you have to stay within your version? IE i have to stay 4.2.2, and I can't go to 4.4?
Thanks again.
Edit,
So I bit the bullet and installed this one here:
http://forum.xda-developers.com/showthread.php?t=2415780
don't really see what all the commotion was about. everything was still the same, seems to have installed over top of my stock rom. It did install something though because the about phone screen has different stuff in it.
Dan
Click to expand...
Click to collapse
AFAIK, you can install other versions of (Safestrap-compatible) ROMs. If you only install ME7 ROMs, then you're only getting modified versions of the same stock software you already had. I have not used Safestrap myself, so your questions about it will get better answers on the Safestrap thread.