yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 3 General] DavidFlory:
You could try the solution of clean flashing Temasek v3.5 and then dirty flashing v6.6. That was the first thing that worked for me. I have not done a clean flash since and have had no problems.
[Verizon Galaxy Note 3 General] Capttwiggy:
I will try, I tried dirty to 6.5 without nk1 with no luck. How do I tell if nk1 worked? Alliance 2 still wont load. Bootloader issue?
[Verizon Galaxy Note 3 General] DavidFlory:
My current favorite phone info app is Device Info by jphilli85. It will tell you all you want about your phone, its firmware, and its drivers including your bootloader, recovery, modem, kernel, and ROM versions. Free from Play Store.

What goes wrong with Alliance?

(Always double check your MD5s to guarantee your are flashing an uncorrupted version.)
[Verizon Galaxy Note 3 General] alexp1289:
Do you know if anyone is working on fixing the sim card issue?
[Verizon Galaxy Note 3 General] Capttwiggy:
Success, kind of...

I was able to flash Temasek 3.2 and dirty flash to 6.6 and keep the SIM card recognized. Only downside is now somehow I do not have root access.....grrr

Thanks for the App recommendation Flory.
[Verizon Galaxy Note 3 General] DavidFlory:
On Alliance it doesn't exist. On Temasek, it may be out of his hands. Remember, Temaset takes the latests CM-12 source and builds his ROMs with his own tweaks and edits. My guess is that the SIM problem, which seems to be localized to Verizon, is in Cyanogens hands not his. A real solution may be in the works, or it may need to wait for a release of LP for the SM-N900V. I have no insight into the innards of Cyanogen.

For me, the clean flash 3.5 followed by dirty flash 6.6 is still working fine.
[Verizon Galaxy Note 3 General] Capttwiggy:
Alliance stalls out on the boot screen, never loads on clean install and battery pull.
[Verizon Galaxy Note 3 General] DavidFlory:
Are you loading a compatible kernel like Lean Kernel 3.15? And how long are you waiting?
[Verizon Galaxy Note 3 General] Capttwiggy:
No, I didn't load a new kernel. I waited 35 minutes for it to load.

Thanks for your help DFlory! I have not been messing around with my phone since last summer and I am a bit out of the loop.

What slots do kernels and modem flash in Odin?
[Verizon Galaxy Note 3 General] DavidFlory:
In Odin 3.09 (the latest) it is the AP slot. I have found that flashing a Modem sometimes requires 2x to take. I also have had better luck with download mode if started from a powered down phone rather than from recovery. Not sure why.

Other than a modem, my preference is to flash from TWRP. Just be sure to get the version that goes with your bootloader. Probably 4.3.
[Verizon Galaxy Note 3 General] capnkrunch:
For root access you may need to go to Settings/Developer options and change Root access from Disabled to Apps only or Apps and ADB.

You are correct, this is CM's domain not Temasek's. If it's even on Temasek's priorities I wouldn't expect it's very high. CM doesn't support Lollipop for us yet (there is no CM12 branch for our device tree and there is nothing in Gerrit either) so they won't be fixing it; Temasek brought up our device tree to CM12 himself (and some commits from christer12). I believe the CM maintainers are waiting for official Lollipop blobs (i.e. Verizon's OTA) due to incompatibilities between the KK blobs and the L everything else. Temasek's builds currently use Sprint blobs since the KK ones were the same as ours. I'm starting to suspect that cross compatibility didn't make the jump to L.

Long story short most likely no devs are looking into this and there's a good chance a real resolution to this won't happen until Verizon rolls out the OTA (if ever). You best bet is the clean flash 3.5, dirty flash 6+ fix or just use Alliance and LeanKernel.

Someone who is currently experiencing the SIM issue might want to try deleting

ro.telephony.ril.config=newril

from your build.prop and rebooting. I don't think it will fix the problem but who knows.

P.S. if you want to try a different Lollipop ROM I just noticed there are Dirty Unicorns weeklies out for us (I'd imagine the SIM issue is present there as well though).
[Verizon Galaxy Note 3 General] Nitrogenus:
I recently acquired an older Note 3 DE (4.3 bootloader). I installed CM11 (M12 snapshot from November 2014) and full PA-GApps for 4.4.x. Everything seemed to work except NFC, which I knew about before installing. Unfortunately, I've discovered that YouTube plays videos with a heavy green tint. Only the videos themselves are green. (I've tried complete wipes and fresh installs including latest CM11 nightlies to no avail. The YouTube issue persists.) Uninstalling and re-installing from Play doesn't work either. I use the same GApps package on another device, and YouTube functions as intended. I am currently using the MJE modem (based on feedback I read), as the most recent, (NK1?) wasn't working for me previously.

Also, OK Google from any screen is not an option on the M12 snapshot. When doing a fresh wipe and clean install with latest nightlies, the option is available, but "Ok Google" does not function properly. I love CM on other devices, and while I do not like it, I can live without NFC. I cannot live with OK Google and YouTube issues.

Is there anything I can do that would fix these issues? I tried flashing LK 3.16 for AOSP-KK, but regardless of which CM nightly I was on, the device would not boot. I've considered going back to a TW based rom, but I do not have much experience with those. I was looking at Alliance, but I cannot figure out which version is the latest (that works on this device). I've flashed and rooted countless devices, including hardware hacking a Chromecast, but I've never had so much trouble with a device. I've spent hours the past few days attempting to find fixes to my issues, but the few I could find that had similar issues, still had them. I cannot seem to find a resolution short of flashing something different. I'm ok with that, but I need a push in the right direction. I am comfortable with ADB, CWM/TWRP, Odin, etc. This isn't my first rodeo, but it surely feels like it. I rarely post, but for the first time in my Android life, I am feeling overwhelmed with problems and options for my device. Please forgive my text wall rant, and please help.

tl;dr What ROM/kernel/modem/GApps do you recommend? (Preferably with working NFC and rock solid 4G)

EDIT: It looks like THIS may be the way to go.
[Verizon Galaxy Note 3 General] LillieBennett:
From what I've read cm11 never worked quite right for note 3 de. Temasek's cm12 has promise but time will tell. Alliance is good and many like Jasmine and Hyperdrive is also good tw roms where everything on the device works. The thing with tw is we have to flash a compatible kernel after the rom, I use lean kernel which is great but his aosp version doesn't work for vzw de. I never heard of tint probs with YouTube, do other videos work (mx player vlc)?
[Verizon Galaxy Note 3 General] Nitrogenus:
Other videos work flawlessly whether in an app or via Chrome (YouTube works here).
[Verizon Galaxy Note 3 General] LillieBennett:
I never saw that, the green tint. Do you have any other streaming apps like netflix that work correctly. Have you gone the gambit of clearing data, uninstall then reinstall from the Play Store? Sorry I can't help much.
[Verizon Galaxy Note 3 General] capnkrunch:
CM11 was never quite right with any Note 3 variant. YouTube in particular was problematic. The tint issue and broken HD YouTube have been issues on and off since they unified the Note 3 builds last February or so. The good news is CM12 doesn't have these issues but there are other issues with it.

Alliance build 2 and leankernel is a solid choice and I've also liked Eclipse. Make sure to flash Hashcode's system file fixes after every TW rom you flash

http://xdaforums.com/showthread.php?t=2732869

If you're set on CM11 you could try Temasek's CM11 kernel or yank555-lu's which might fix YouTube and maybe try Nova Launcher for "Ok Google."

Temasek's cm12 is also an option. You will probably need to clean flash 3.5 then dirty flash the current to get your SIM card recognized.

Welcome to our world. I think this device probably lost Samsung a good number of loyal customers; including myself. And developers (probably most notably beans). dhufford81 and droidstyle had a good conversation about this a couple pages back.

In fact, your best bet is to try and get your money back and get a Nexus 6 instead (only half joking).

EDIT: Can you pull a logcat of the YouTube problem?
[Verizon Galaxy Note 3 General] alexp1289:
[MENTION=4477763]DavidFlory[/MENTION] try this ROM -- http://xdaforums.com/showthread.php?t=2959244 -- if you get the same SIM card issue which you probably will take the log and post it for Zion to look at. He usually will if you ask. And on a side note I don't think that the SIM card issue has anything to do with the blobs for lollipop because if I remember correctly there are no galaxy note 3 phones that have an official lollipop build anyways so they are all using different blobs. If someone finds a way to fix it it can be merged to cyanogen mod for future builds right?
[Verizon Galaxy Note 3 General] capnkrunch:
Current sprint blobs are from sprint nh4 which I believe is a leaked build. Hlte blobs are from NJ2 which I know nothing about. The SIM issue is specific to us and occurred sometime between 3.5 and 5.9. The only vzw specific changes during that period were adding newril to system.prop and using Sprint blobs. If the issue is in our device tree or blobs (seems likely to me since this is an issue specific to our variant) then a fix CANNOT be merged to upstream CM since there is no CM12 branch for us. It could be merged to Temasek's repos but that doesn't guarantee anything but a fixed Temasek build (i.e. DU merged the device tree changes but not the vendor repo changes).

I am curious about cmremix. It looks like a nice rom and it would be awesome to have a real dev look into the SIM problem for us. I'm also interested because zion (like DU) doesn't use sprint blobs. When I flashed DU my SIM wasn't recognized even though it works on Temasek. If cmremix or DU works for you 4.3 guys that seems to point to a bootloader issue which makes no sense to me would be incredibly ominous for our device's future. I don't think this will be the case though.
[Verizon Galaxy Note 3 General] alexp1289:
We need to start posting more on zions thread so he knows we are all interested.
[Verizon Galaxy Note 3 General] droidstyle:
Just wanted to update that I fixed my microphone. Had to replace the USB/Microphone flex cable board. Good as New!! I am glad too because I really like my DE N3!!
[Verizon Galaxy Note 3 General] alexp1289:
Has anyone tried flashing temasek 6.8?--- http://temasek.rajasthanautoworks.in/
[Verizon Galaxy Note 3 General] DavidFlory:
Yes, and it is working fine.
[Verizon Galaxy Note 3 General] alexp1289:
Any sim card issues from a clean install? Or did you dirty flash?
[Verizon Galaxy Note 3 General] DavidFlory:
I have not done a clean flash since I flashed v3.5 which seems to have been the thing that fixed my SIM issues. I did flash the NK1 modem but since the incremental dirty flashes are working so well I have not clean flashed since. Temasek just said to look for 7.0. Perhaps then I will test.
[Verizon Galaxy Note 3 General] alexp1289:
Yeah I saw that on his twitter. Going to wait till someone tries out 7.0 from clean install. I'd play around with it but this is my work phone so can't afford to not have connectivity. Could you post your findings once 7.0 is out and if need be send him a log?
[Verizon Galaxy Note 3 General] DavidFlory:
I will say that since the fix (3.5 clean, NK1, and 6.x dirty) I have not had a single problem with my SIM or getting a LTE/4G data connection. I am using Temasek's CM-12 hltevzw (latest) as my daily driver.
[Verizon Galaxy Note 3 General] alexp1289:
I understand what you mean but I was curious about doing a clean install. If it's really fixed then no dirty flashes should be needed. I would like to be able to wipe everything and just do a clean install coming from cm11 knowing there will be no issues. But if there are any I'll keep waiting. Hope you don't mind being the guinea pig LOL. [emoji2]
[Verizon Galaxy Note 3 General] Capttwiggy:
I am running Temasek v7 without any known issues. I dirty flashed up from 3.2, and then 6.6 via TWRP 2.8.4 and running the NK1 kernel. I do seem to have some cell data drops I don't have on KK periodically , but the SIM card issue is gone.
[Verizon Galaxy Note 3 General] alexp1289:
You think I'd be fine on a clean flash? Dirty flashing would just over write the buggy files anyways so clean flash should be just fine right?
[Verizon Galaxy Note 3 General] Capttwiggy:
I did not have any luck with a clean install on 6.6. The only way to recognize the SIM was dirty flash on 6.x coming from a clean 3.2
[Verizon Galaxy Note 3 General] alexp1289:
Why does no one clean flash and grab a log for temasek? Dirty flashing is just a bandaid.
[Verizon Galaxy Note 3 General] Nitrogenus:
Update

I just wanted to update those who had helped me a few pages back. I installed Alliance and LK 3.16, and honestly, I didn't know I could be so happy with a TW rom. =) This phone will carry me for at least another year or so (unless it breaks, or the new hotness is released). I sincerely appreciate the help.

Cheers!
[Verizon Galaxy Note 3 General] alexp1289:
Okay I just clean flashed temasek v7.0 cm12 and it boots up and let's me select English then freezes when detecting cellular service then reboots without me doing anything. Even if I try to hit the skip button it results in it freezing and rebooting. Is it possible to somehow get a log from inside of twrp so this can be looked at? If possible can someone instruct me on how to get a log since I can't do it from the ROM? I suspect the system generates a log that can be pulled somehow?
[Verizon Galaxy Note 3 General] DavidFlory:
Are you trying to get a working version of CM-12 or are you trying to troubleshoot the problem? If you want a working version, follow the clean v3.5 then dirty 7.0 path discussed in several places in this thread.

If you are trying to get a log of the problem, enable WiFi which stopped the FCs for me. Turn on airplane mode to stop the phone from trying to use the SIM. This should quiet you down to the point where you can get a log. There are tutorial on using adp to capture log files.
[Verizon Galaxy Note 3 General] alexp1289:
Trying to help diagnose the issue and stop with the Band-Aids.
[Verizon Galaxy Note 3 General] DavidFlory:
Here is a tutorial on getting a log. http://xdaforums.com/showthread.php?t=1726238

However, I strongly suspect that we will not see a solution until Verizon releases a Lolipop version for our Note 3. The modem and associated blobs are needed. That is also when Cyanogen will probably start building hltevzw nightlies of CM-12.
[Verizon Galaxy Note 3 General] LillieBennett:
Sounds like to clean flash a 3.x then without booting dirty flash 6.9+. To me, this equates to a clean flash since data hasn't been modified between the 2 flashes.

---------- Post added at 11:17 PM ---------- Previous post was at 11:11 PM ----------

Right on, everything will work!
[Verizon Galaxy Note 3 General] alexp1289:
But I don't get why if it has worked then why all of a sudden we need blobs from Samsung/Verizon LP? Something seems like it just got screwed up between versions.
[Verizon Galaxy Note 3 General] DavidFlory:
You are probably correct. However, given the number of downloads of Temasek's hltevzw build on Basketbuild (5 just now compared to 467 for the hlte version) I don't think our version is high on his priority list. We should be thankful he builds for us at all.

It could well be that the problem arose from a change in the CM-12 base that would have to be teased out and reverted. That takes time. One approach would be to clean install v3.5 and test. Then repeat, carefully, for each successive version until the problem arises. You then would have two adjacent versions, one good and the next bad. You then go into GitHub and see exactly what changed between the two version and look to see where the problem lives. My guess is that would require a serious developer with time on his hands.

I am not he. Are you?

We have a good solid work-around for the problem now. That removes the urgency. Feel free to tackle the problem yourself but please stop asking others to do it for you.
[Verizon Galaxy Note 3 General] alexp1289:
Wow... Here I am trying to ask for ways I can be helpful in fixing this and you basically just say "not worth anyone's time" I'm not asking anyone to do it I'm simply asking how I can narrow it down so when someone feels like they want to look at the issue they have everything they need. Without this information no one will take the time to look into this issue. Excuse me for not wanting to sit on my butt and complain about the issue. I'm trying to be as helpful as possible but need assistance since I'm not as hard core as the rest of you. Forgive me for wanting to help/learn and maybe I could fix it myself if someone would be my mentor. That would be nice because I thought that this "community" we supposedly have was for learning and educating one another. Don't you think if I was able to do it myself I'd be doing just that. I for one don't want to see us without people trying to work hard on our specific phone. Development seems to be slowing down and I'm trying to do what I can to speed it up and be a helpful community member and possibly be more than just a member that can help us keep development going so this train doesn't lose steam. Seriously think about what you say before you type.
[Verizon Galaxy Note 3 General] DavidFlory:
I gave you instructions on exactly how to do that. I also gave you a very simple reason why the project may not be high on Temasek or arter97's priority list. Reality.
[Verizon Galaxy Note 3 General] alexp1289:
Yes but sitting around saying it's not a priority with or thumbs up our butt does nothing. I want to find someone that will help once I gather all the documentation. Just like I did with bigbiff everyone on here was saying we had no recoveries to use so I got mine and contacted the right people and found bigbiff. Gave him my recovery from stock and bam had something us 4.4 bootloader people could use. Meanwhile it sounded like others were just giving up. Sorry if I sound frustrated but that's because I love my Dev edition and would like all of use to keep them as long as possible. PLEASE don't take any of this out of context you and all the others are a big help I just get frustrated when it seems like no ones being proactive. Right now it feels like everyone wants to play the waiting game. I want to get the logs and everything to the people that need them so they can look into it when there's time. Sorry for freaking out. Rant over!!
[Verizon Galaxy Note 3 General] alexp1289:
I may not know very much about ROMs and android but I would like to speed up support for us as fast as possible. Sorry for being frustrated earlier and I realise not everything everyone does is able to be seen. That was an oversight on my part and I'm sorry. I do however believe that we need our voices and logs seen/heard by as many as possible that could help. The squeaky wheel gets the grease :)
[Verizon Galaxy Note 3 General] capnkrunch:
Hey, hey everyone. I have a couple test builds in the works (it takes my computer forever to finish building). In the meantime, I'd like some logcats. Can someone get me a logcat of a clean flash of current Temasek with the unrecognized SIM problem AND a logcat of a working setup using the clean flash 3.x, dirty flash current fix? Please use "logcat -v long" to grab them (it formats the log a little nicer). Use adb if you can't get it from your phone (actually I'd prefer you use adb either way). See [Tutorial] How To Logcat if you need help.

[MENTION=4477763]DavidFlory[/MENTION]: I already have a logcat of your SIM not registering (from Temasek's thread). I totally understand if you don't want to risk breaking things with a clean flash and hope that the 3.5 -> current fix works again. Would you mind at least grabbing a logcat of your currently working setup? For that please do NOT use "-v long" since your old one didn't use that either ("-v long" is nice but comparing ones formatted the same way is nicer).

EDIT: More detailed instructions *PLEASE FOLLOW*

Using adb

1. Reboot phone

2. Wait for SIM error or network to connect

3. Connect to computer as soon after as possible

4. Use "adb logcat -v long > /path/to/yourlog.txt" to start pulling log

5. Toggle airplane mode

6. Stop logcat as soon as you get the SIM error or reconnect to the network

Using phone

1. Reboot phone

2. Wait for SIM error or network to connect

3. Open terminal emulator as soon as possible

4. Grant the shell root with "su"

5. Use "adb logcat -v long > /path/to/yourlog.txt" to start pulling log

6. Toggle airplane mode

7. Stop logcat as soon as you get the SIM error again or reconnect to the network

Please use the same method for both logs. This means if you can't get terminal emulator installed (or CM's built in terminal enabled) AND granted superuser permissions when you get the SIM error you need to also use adb for the working log. Please pull logs from a system that's as clean as possible (do this before installing any apps). I'd prefer you use adb to get logs. Please make sure you aren't doing anything else before or during the logcat. Please do the steps in order and as quickly as possible. Please make sure the log's name identifies if it is from the working setup or the broken one.

EDIT 2: Please grab a logcat of 3.x as well. Follow the same instructions above only instead of waiting for the SIM error wait for the com.android.phone FCs. Overall I'd like you to clean flash current Temasek, get a log, clean flash 3.5, get a log, dirty flash current, get a log.
[Verizon Galaxy Note 3 General] alexp1289:
Adb over USB connected to a PC is probably the only way to get a log of the issue. When I did a clean flash of temasek 7.0 cm12 I couldn't even get past the second part of the phones setup it would try to detect the network at the second setup screen (after choosing language). Not sure if the kernel puts the log somewhere in the root directory because getting past that second screen without a reboot/screen freezing was impossible for me. If the kernel does automatically save a log in the filesystem could it be accessed via adb in download mode? Or via adb connection in twrp?