Related
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.
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Sprint LG G3[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: How do I Root my LG G3?[/SIZE]You should revert to ZV4 using Flashtool - see below.
OR
You can root ZVA using THIS Thanks to @l33tlinuxh4x0r - But be aware that most ROM's/Kernels are made for the ZV4 bootloader!!! You will have all ZVA partitions, so you may have issues.
On ZV4:
1. Your phone must have NEVER been Rooted before. Even if you've uninstalled SuperSu and removed all the files IT WILL NOT WORK!! It MUST be installed on a clean phone. ie Never Rooted, LGFlashtool - see below about this.
2. Root for us is in this thread. HERE
Version 1.2.0 is the most current - Hit "Grind" it'll more than likely say not supported, then hit "OK" and it will "Bruteforce" root to your phone, then reboot when told and it'll reboot again on its own.
Let it bootup, then install SuperSu, reboot and then uninstall Stump Root.
Version 1.0.0 was made specifically for the Sprint G3.
[SIZE=+1]Q2: How do I unlock the bootloader?[/SIZE]You must Root first with Stump, then we use BUMP
HERE is another option to install BUMP.
or
for ZV8/A, This should work Thanks to @bender_007
[SIZE=+1]Q3: How do I Restore/Fix and Get my MSL on my LG G3?[/SIZE]With LGFlashtool. For a walkthru on how to use it go. HERE
This page will also get your MSL. Read Post #4
[SIZE=+1]Q4: How do I fix/backup other things on my LG G3?[/SIZE]
BACKUP EFS
STUCK IN RECOVERY
PRESERVE ROOT FROM OTA'S
[SIZE=+1]Q5: Dialer Codes to fix things[/SIZE]In order least invasive to most.
##UPDATE#
##SCRTN#
or
##RTN# - this one requires your MSL. Get it from Sprint or HERE
[SIZE=+1]Q6: What about modifying files on the LG G3? ie build.prop[/SIZE]Make a backup in TWRP first
Our build prop is too large for most text editors. 920 text editor, works so you can get it from the Playstore. Make sure after modifying anything to set permissions. For the build.prop it's rw-r-r.
[SIZE=+1]Q7: How do I Backup/Restore EFS on the LG G3?[/SIZE]VERY IMPORTANT THAT YOU BACK THIS UP!!! HERE YUP...This is here twice for a reason.
[SIZE=+1]Q8: The LG G3 has CDMA and GSM radios. How do I...?[/SIZE]For now, I'll leave the search for you.
[SIZE=+1]Q: What to do about ZVA/ZV8/ZV6 Update[/SIZE]LOOK HERE
**********
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to everyone who contributed to the production of this FAQ
*Reserved*
If you guys can think of anything else to put here, let me know.
I was just going to make this more open for now, but it would have been a pain to convert to the XDA Template.
Does the G3 have the same security check the OG did. As in removing stock apps=brick?
JESUSARIUS REX said:
Does the G3 have the same security check the OG did. As in removing stock apps=brick?
Click to expand...
Click to collapse
Nope. We're good to go on this one. Just be careful what apps you remove. Don't cut too deep.
What a lot of people are doing is freezing/disabling apps before they remove them.
Added questions Q5 - apps, Q6 - modifying build.prop and system files
Updated rooting instructions. Just made it more thorough.
Here's an idea for q8.
How do I get my QHD preloaded videos back?
The answer is... Restore your G3 with flashtool!
I accidentally deleted my QHD vids awhile back when I did a factory reset from stock recovery. I couldn't use someone else's vids because they have some kind of protection and can only be viewed on the device they came on.
I restored with flashtool the other day and when I was going through my gallery this morning I noticed that they are back.
I searched and asked everywhere trying to get them back with no luck.
---------- Post added at 06:48 AM ---------- Previous post was at 06:29 AM ----------
I'd like to make another suggestion, if you don't mind.
These are common questions that someone would search Google for. It would be great if this thread popped up when someone searched Google for the answer.
My suggestion is to make each question specific to the G3 or LG G3.
Example.. Q3: How do I restore my LG G3 back to factory stock condition?
Just think about what you'd type into the Google search bar.
Excellent faq, please don't think I'm trying to be critical.
Will32 said:
Here's an idea for q8.
How do I get my QHD preloaded videos back?
The answer is... Restore your G3 with flashtool!
I accidentally deleted my QHD vids awhile back when I did a factory reset from stock recovery. I couldn't use someone else's vids because they have some kind of protection and can only be viewed on the device they came on.
I restored with flashtool the other day and when I was going through my gallery this morning I noticed that they are back.
I searched and asked everywhere trying to get them back with no luck.
---------- Post added at 06:48 AM ---------- Previous post was at 06:29 AM ----------
I'd like to make another suggestion, if you don't mind.
These are common questions that someone would search Google for. It would be great if this thread popped up when someone searched Google for the answer.
My suggestion is to make each question specific to the G3 or LG G3.
Example.. Q3: How do I restore my LG G3 back to factory stock condition?
Just think about what you'd type into the Google search bar.
Excellent faq, please don't think I'm trying to be critical.
Click to expand...
Click to collapse
It's all good. I was the one asking for suggestions, so I don't think that at all.
The way XDA wants these FAQ's is to try and find the most common questions so as to limit the amount of new threads. I tend to take it a little further by providing links and other info that I think is helpful.
To answer your suggestions:
1. So far, I think you're the only one who wanted the QHD vids back. So I'm not being rude, but for now I'll leave it off. You, me and others that actually read these threads know how to fix this. (and this IS on the first page now). If it becomes a common issue, I will gladly add it.
2. I'm not positive about this but I think the tags at the bottom serve that purpose. I added a couple and I think anybody can do the same. I'll edit the OP just to make sure.
Thanks for the suggestions, and please don't think I was being critical. I was just explaining my position.
Added link for question #5 APPS removal list. Thanks to stas333
Q#7 Added EFS Backup info. Very Important that you do this or you could be in for a lot of work and luck.
Q#3 Added info on getting MSL
Wow. Super surprised at how dead this forum is. Just picked one up today cuz specs were amazing. Hoping I didn't make a bad choice. Just checking XDA now, but looks like no custom recovery and ROMs. I pray I'm mussing something something. Device seems fantastic.
scottspa74 said:
Wow. Super surprised at how dead this forum is. Just picked one up today cuz specs were amazing. Hoping I didn't make a bad choice. Just checking XDA now, but looks like no custom recovery and ROMs. I pray I'm mussing something something. Device seems fantastic.
Click to expand...
Click to collapse
All the G3s ( except T-Mobile ) just got unlocked like a week ago. Plus we're all waiting for the Devs to release their Bump tool so AOSP Roms and custom Kernels can be flashed.
Just be patient, it's all in the works!
scottspa74 said:
Wow. Super surprised at how dead this forum is. Just picked one up today cuz specs were amazing. Hoping I didn't make a bad choice. Just checking XDA now, but looks like no custom recovery and ROMs. I pray I'm mussing something something. Device seems fantastic.
Click to expand...
Click to collapse
Been on vacation. But I'll get this update this weekend. Here's the only thing I need to add. Bump unlock. http://forum.xda-developers.com/showthread.php?p=55932215
Edit. And just found this from @autoprime.
EFSBackup.zip. http://forum.xda-developers.com/showthread.php?p=56058409
DO THIS!!!
Edit 2. And this too. If autoprime posted it, we'll need it.
Stuck in recovery. http://forum.xda-developers.com/showthread.php?p=56061720
Wow. I'm new to bump AMD some other terminology. Always been an HTC user. It seems there like 4 different ways to get root (according yo YouTube tuts). I'm more interested in boot loader unlock to get custom recovery. Looks like I have a lot if reading to do lol.
scottspa74 said:
Wow. I'm new to bump AMD some other terminology. Always been an HTC user. It seems there like 4 different ways to get root (according yo YouTube tuts). I'm more interested in boot loader unlock to get custom recovery. Looks like I have a lot if reading to do lol.
Click to expand...
Click to collapse
If you're on Sprint, Stump is our root method. And to unlock the boot loader, we all use Bump.
Stump and Bump are the names of the apps/methods.
Almost sounds like a new song, which we're all singing now.
Edit. New from autoprime
Preserving root from OTA's. http://forum.xda-developers.com/showthread.php?p=56100153&postcount=1
OP updated
Just wanna say thanks for the one stop shop. Makes it easy to find stuff when I need it.
Well I didn't want to start a new thread so I thought I would ask here. I hope that's ok. Anyways, I was just wondering if anyone uses a cpu governor? I'm on stock and rooted through stump and bumped. If so which is a good one to use and what settings are best? Thanks
Op updated with ZV6 info - There is no Root for it yet.
Flash one of the zips in Development.
I was wondering if there was a way to flash AT&T ROM to work on the verizon model. I know how to flash international Roms but not AT&T.
For example, currently I am running Echoe 32.1 (International version), but when I try to flash Goldenfinger (AT&T) my phone calls work but I get no SMS or data.
Any help is appreciated!
Thanks!
Someone with ROM building (from source or porting) experience can better explain this, but the simplest answer is that because the frequencies that AT&T and T-Mobile operate on differ from those of Verizon and Sprint (typically). So the ROM you are trying to use has different radio drivers for frequencies your phone doesn't use, which results in most or all your antennas to not function. I know that at the very least you need to modify the ROM to utilize the Verizon radios. There may also be some system configurations to be altered in the install of the ROM so it's instructed to use the right frequencies, though a more qualified individual will need to verify that.
Hope that gives you a general idea.
http://forum.xda-developers.com/showthread.php?t=2674280
This patch can be used to flash roms from international and other carriers. It has an aroma installer allowing to decide how much Verizon stuff you want to install, anywhere from just the APN's to the full phone & messaging apk's. Read the OP and thread to understand which patch to use and how to use it.
joshm.1219 said:
http://forum.xda-developers.com/showthread.php?t=2674280
This patch can be used to flash roms from international and other carriers. It has an aroma installer allowing to decide how much Verizon stuff you want to install, anywhere from just the APN's to the full phone & messaging apk's. Read the OP and thread to understand which patch to use and how to use it.
Click to expand...
Click to collapse
Thank you for the help! But I tried the patch you suggested on two different AT&T ROMs, and I didn't have any luck. It works on international version ROMs, but not AT&T..
And I just realized I forgot to put in the OP that im on Safestrap
luke24 said:
Thank you for the help! But I tried the patch you suggested on two different AT&T ROMs, and I didn't have any luck. It works on international version ROMs, but not AT&T..
And I just realized I forgot to put in the OP that im on Safestrap
Click to expand...
Click to collapse
Yeah, unfortunately things have been weird with that patch lately. It's a mix of the dev not having time to update while everything has been getting significant updates pretty quickly and lost user interest overall. I've used that patch with AT&T roms before, but admittedly not since Jelly Bean. It should theoretically work still, but there's other variables you have to consider. All I can say is that if you're really interested in running one of those roms, read through the patch thread to see what particular aroma settings and additional zips, etc. people are using to get those roms to boot.
And Safestrap users can use that patch too. I would PM @shindiggity for assistance. He seems like a helpful guy and he uses that patch on Safestrap.
joshm.1219 said:
Yeah, unfortunately things have been weird with that patch lately. It's a mix of the dev not having time to update while everything has been getting significant updates pretty quickly and lost user interest overall. I've used that patch with AT&T roms before, but admittedly not since Jelly Bean. It should theoretically work still, but there's other variables you have to consider. All I can say is that if you're really interested in running one of those roms, read through the patch thread to see what particular aroma settings and additional zips, etc. people are using to get those roms to boot.
And Safestrap users can use that patch too. I would PM @shindiggity for assistance. He seems like a helpful guy and he uses that patch on Safestrap.
Click to expand...
Click to collapse
Thank you for all your help! Im gonna PM him and read through the thread and if and when I find a solution, I will post it here.
I've flashed Goldfinger and it does work. These are the steps that I do. Flash rom, patch,signal bar fix, modules and finally SU. In the patch I select minimal and everything else I leave pre selected. First boot does take a couple minutes. Let me know if that works.
http://www.androidfilehost.com/?fid=23501681358559252
http://www.androidfilehost.com/?fid=23578570567713275
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
Admin.. please delete. Sorry for the mix up.
chewyma said:
I upgraded to lolly pop but because of the SE Enforcing issue Xmods dose not work. There is a work around with moving Xmods to the system files etc but that doesn't work. So I was in search of a Non SE Enforcing Kenel, found this http://www.mediafire.com/download/aod6n85a198o4he/lk_hlte-v6.0.zip. Installed and works fine however now the phone is not connecting to the Sprint Network.
1. Did I install the wrong Kernel?
2. Is anyone aware of there being a no SE Enforcing Kernel for the HTLESPR?
Click to expand...
Click to collapse
EDIT: mod moved thread to correct section
this is the Dev section, where people post ROMs they've made.
for things like this, either post in the Q&A section, or post in a thread related to the ROM/app you're using/having a problem with.
I'm under the impression there Are No custom kernels for lollipop on this device yet, but that's not an area I know much about really.
Op go here and ask. If we get enough sprint users asking he may make one again. Kit Kat. Was fubared at least when in beta tested it. Wish he make a lollipop sprint.
Sent from my 0x1 Note 3...... I love tep