yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 3 General] radionerd:
I don't know where it lives.

OK, I just intentionally borked it up.

I will document steps, and post back.

---------- Post added at 07:51 PM ---------- Previous post was at 07:18 PM ----------

OK,

I did the following and got LTE back

On phone menus::

WiFi on and connected to an AP (I think this is what makes it hard for initial LTE lock, there network switch timings are on the edge)

Cell network settings: LTE Preferred

System Select: Auto

subscription: RUIM/SIM

Open Beans Device Info App

Select Phone Info

Touch the three ... in the top right

select radio band: Automatic Wait until it changes (set [Automatic] Successful will show up. hit back

On phone info screen look at preferred network type in not selected choose LTE/CDMA auto (PRL)

Wait a few minutes if it still has exclamation on network do a battery pull

After reboot, WiFi still on, go back into beans app. check that preferred network is still LTE...... not WCDMA, change it if needed.

now go to the dropdown menu that shows WiFi and Network, wait a few minutes.

Turn Airplane mode on for about 30 seconds, turn back off (this is where we try to coax it to lock LTE)

wait about a minute, once exclamation is gone were close.

toggle WiFi off for about 30 seconds, you might get a FC if exclamation is still on network.

Keep toggling wifi off/on waiting about thirty seconds. Took mine sever toggles to lock. (It's a timing issue I think)

Once locked on LTE you can turn off WiFi and test throughput. Once it locks I don't have any more problems after reboot or turning radios off/on

---------- Post added at 08:23 PM ---------- Previous post was at 07:51 PM ----------

OK,

I did the following and got LTE back

On phone menus::

WiFi on and connected to an AP (I think this is what makes it hard for initial LTE lock)

Cell network settings: LTE Preferred

System Select: Auto

subscription: RUIM/SIM

Open Beans Device Info App

Select Phone Info

Touch the three ... in the top right

select radio band: Automatic Wait until it changes (set [Automatic] Successful will show up. hit back

On phone info screen look at preferred network type in not selected choose LTE/CDMA auto (PRL)

Wait a few minutes if it still has exclamation on network do a battery pull

After reboot, WiFi still on, go back into beans app. check that preferred network is still LTE...... not WCDMA, change it if needed.

now go to the dropdown menu that shows WiFi and Network, wait a few minutes.

Turn Airplane mode on for about 30 seconds, turn back off (this is where we try to trick it to lock LTE)

wait about a minute, once exclamation is gone were close.

toggle WiFi off for about 30 seconds, you might get a FC if exclamation is still on network.

Keep toggling wifi off/on waiting about thirty seconds. Took mine sever toggles to lock.

Once locked on LTE you can turn off WiFi and test throughput. Once it locks I don't have any more problems after reboot or turning radios off/on

Probably more steps than needed, I think it doesn't look at the 700MHz band long enough, or maybe be at all.

Tamesek just dropped 3.3 I'm flashing :)
[Verizon Galaxy Note 3 General] DavidFlory:
Didn't work last night. This morning I have LTE [emoji1]. Maybe the wait did it?
[Verizon Galaxy Note 3 General] DavidFlory:
Intermittent. When I lose LTE toggling WiFi or Airplane Mode sometimes helps.

I notice that when I use Bean's Device Info the option (in 3-dots menu) to select the radio band sometimes shows a few options, sometime many, and sometimes hangs searching. Odd behavior. Related? If the system cannot find the band it needs clearly problems will result.
[Verizon Galaxy Note 3 General] LillieBennett:
Mine takes a couple minutes to switch. 3.3 is screwed up for vzw.
[Verizon Galaxy Note 3 General] DavidFlory:
I tried 3.3 briefly. Couldn't get past my SIM password PIN. Back to 3.2.
[Verizon Galaxy Note 3 General] somethingsomethingroot:
Well, decided to try 3.5 on a whim, and LTE works without having to mess with API stuff.

Now if I could just get Netflix and YouTube working. Netfix is giving me a 1018 playback error when choosing any title and YouTube only notes that "There was a problem while playing" on every video. I've gone through every combination of clearing cache, uninstalling and reinstalling the apps and rebooting my device and it's still no go.
[Verizon Galaxy Note 3 General] LillieBennett:
Me too. Any of us on the 4.4 bootloader? I doubt it will make a difference but it will be good to know.

I am also considering trying the Sprint version.
[Verizon Galaxy Note 3 General] DavidFlory:
I did a clean install of 3.5 with less success. I got many "com.android.phone has stopped" messages while doing my initial configuration. I still cannot get LTE data. And Play Movies does not work. (MD5 good on the CM12 3.5)
[Verizon Galaxy Note 3 General] LillieBennett:
I got just 1 YouTube video to play through after a fresh install 2.8 maybe, then nothing from there. The next version gave me a partial then nothing.
[Verizon Galaxy Note 3 General] ryanbg:
[MENTION=5639793]capnkrunch[/MENTION] Basically at this point, I need someone who is willing to be a complete guinea pig with risk of a brick. If someone is up to risk it all, we can test it.
[Verizon Galaxy Note 3 General] LillieBennett:
My Note 3 is running exceptional, I haven't had any of the problems many have complained about and it does everything it was designed to. So I guess I'm out, I can get a Nexus 6 to go forward with, the note 3 will be my good old trusty. Besides, cm12 is working with only a few bugs.
[Verizon Galaxy Note 3 General] droidstyle:
Anybody tried slimkat? I have been running it and have not found any issues. Also where are the latest cm12 builds? Thx
[Verizon Galaxy Note 3 General] LillieBennett:
Temasek unofficial cm12 :

http://xdaforums.com/showthread.php?p=57049013
[Verizon Galaxy Note 3 General] DavidFlory:
Yes, but infrequent for our hltevzw.
[Verizon Galaxy Note 3 General] LillieBennett:
It seems builds have stopped, waiting for blurbs they say.
[Verizon Galaxy Note 3 General] droidstyle:
Oh ya I seen that...after reading thru I think I will stick with SlimKat for a bit...everything seems to be working.
[Verizon Galaxy Note 3 General] alexp1289:
Do you guys thing we'll still have nfc battery drain issues like on cm11. If so we may need a new nfc remove patch for cm12.
[Verizon Galaxy Note 3 General] dhufford81:
Hashcode has been out of the scene for months... I believe he posted why in this particular thread. He didn't jump ship, he took a great job opportunity. Beans has also spoke on leaving this community. Samsung is a ****ty joke. If you want a phone with dev support, choose your purchase more wisely. PS vzw will never ever push an ota to a dev unit, and neither will Samsung. You're damn lucky it failed and you didn't lock your bootloader lol.
[Verizon Galaxy Note 3 General] droidstyle:
Samsung is not a joke...Verizon is a Joke. Development is thriving for T-mo and Sprint Samsung devices.

Proof:

http://xdaforums.com/note-4-tmobile/development
[Verizon Galaxy Note 3 General] dhufford81:
Moto makes dev edition phones on vzw and they support them by providing recovery images that don't lock the boot loader. Samsung does the opposite, which to me is a ****ty joke. That's not Verizon's fault. When I first got my dev unit in November of 2013 I tried getting a support rep on the phone to help me understand why Samsung couldn't provide the files needed to recover from a wrecked dev unit. Most of the reps and supervisors I spoke too had no idea the dev unit existed. They kept telling me to plug my wrecked phone into kies which will recover you to a retail edition with a cute locked boot loader as a souvenir.

---------- Post added at 04:39 PM ---------- Previous post was at 04:35 PM ----------

Further more the dev units from samsung were constantly sold out. Later in 2014 they started selling dev units that shipped with the kit kat boot loader unlocked but no option or way for the older 4.3 dev units to upgrade.
[Verizon Galaxy Note 3 General] droidstyle:
the point is on tmobile or sprint you do not need a damn dev edition...which stems back to Verizon.
[Verizon Galaxy Note 3 General] dhufford81:
While i agree with that sentiment, i personally can't hold verizon responsible for the lack of support/recovery images samsung provides for a phone bought full price directly from samsung. none of this really matters to me anymore because i've moved on to the n6, but i will say it runs great on vzw and i can lock or unlock my bootloader any damn time i want without worry. verizon is doing nothing to stop me. ps touchwiz
[Verizon Galaxy Note 3 General] keynith:
I will be doing the same soon! Gonna be such a relief to type "oem unlock bootlader" and then flash twrp and go about my day.

Sent From My Galaxy Note 3
[Verizon Galaxy Note 3 General] alexp1289:
Holy crap dude you're the best :) does everything work good yet? I would like it as my dd :) this is sweet thanks so much man :)
[Verizon Galaxy Note 3 General] capnkrunch:
NFC is broken still and most of the time it can't find my 5GHz WiFi (2.4 works fine though). Other than that I haven't had any issues. I have even better news though. Temasek merged my pull requests and is building for us again. Check his basketbuild for the newest build. Coming from my 01/19 build you should be ok dirty flashing but from 3.5 you probably want to clean flash.
[Verizon Galaxy Note 3 General] radionerd:
Back when I was running Temasek (up to about 3.3) I would force 5Ghz only in WiFi settings, it would connect. Then I put setting back to normal, reboot, and 5Ghz and 2.4Ghz would continue to lock after that. I never did get GPS lock though.

I'm glad you stepped up. My kid has my note3 now, he likes CM, so we will probably flash back to Temasek 12 from Alliance .

Thanks!
[Verizon Galaxy Note 3 General] capnkrunch:
Thanks! This fixed the WiFi problem. I had to reboot after forcing 5GHz for it to pick up my network though. Using Temasek's 5.9 build I get a GPS lock fine in Device Only mode. It doesn't seem as accurate as it was on CM-11 or TW (it seems to hang around accurate to 50 feet when I check GPS Test) but this has been good enough for navigation for me.
[Verizon Galaxy Note 3 General] radionerd:
Cool,

I think I left out a step ;)

Will probably flash this weekent, Tem should be up to about build 6.8 by then :)
[Verizon Galaxy Note 3 General] capnkrunch:
So I'm not sure if it's even necessary but I updated Hashcode's NFC remove zip. I don't have the BBS data to show that NFC is still causing battery drain but since NFC doesn't work there's no harm in preemptively removing it. If someone else wants to confirm or deny NFC induced drain that would be great but there's not much need to.

https://www.androidfilehost.com/?fid=95897840722648261
[Verizon Galaxy Note 3 General] DavidFlory:
I just installed Temasek's hltevzw-V5.1 CM-12 build and it is much improved. Warning, I have only tested for 18 hours.

* Most important, I can now get data over my LTE/4G connection.

* Google Play Movies is working.

* I am not getting the "com.android.phone has stopped" error message.

* GPS gets a fix

I will report more as I test more.

==============================

I may have posted too soon. I tried to dirty flash v6 and got into a boot loop. I also could not activate my SIM. I then went back to 5.9 and could not activate my SIM.
[Verizon Galaxy Note 3 General] capnkrunch:
When you went back to 5.9 was it a clean flash or another dirty flash? I've occasionally got com.android.phone FCs moving between versions and it's inconsistent and I have no idea why. But once it happens once it isn't fixed until I clean flash.
[Verizon Galaxy Note 3 General] DavidFlory:
It was a restore to my backup. However, I wonder if 6.0 did something that persisted. My next move will be a clean re-install of 5.9 which seemed to be working.

==========================================

Clean install of 5.9 which worked fine for a while. It reinstalled things and then decided to not recognize my SIM card and went into a reboot loop. Perhaps something got restored that messed things up. More testing later.
[Verizon Galaxy Note 3 General] capnkrunch:
Hmmm...did you do a Titanium Backup restore? If so did you restore system data? Is there any app in particular that you think could have caused issues? If it's not fixed already could you try connecting to your computer and pulling a logcat of the bootloop with adb?

A clean install of 6.0 might also be worth a shot.

EDIT: Are you getting a specific message about your SIM not activating? If so what is the message? If not what is going on exactly (i.e. does it just fail to connect or are you getting some kind of errors or force closes as well)?

Hopefully we can figure out what's going on and it ends up being a nice simple fix.
[Verizon Galaxy Note 3 General] LillieBennett:
I dirty flashed 5.9 to 6.1 and all seems good, even set a chummy theme. Had to reflash w/gapps & superSu as the auto restore didn't work. No sim card atm, nexus 6 has it.
[Verizon Galaxy Note 3 General] DavidFlory:
I did a clean flash of 6.1. At first, no gApps. I had to play with *#*#4636#*#* for a while and reboot a couple of times but I finally got it to recognize my SIM card. Then I installed gApps. At the moment all is working well. However, auto restore did not work so I am doing it by hand. I even have Google Play Movies working.

My only real problem is that I cannot use my YubiKey Neo & LastPass combo for my passwords since NFC does not work.
[Verizon Galaxy Note 3 General] alexp1289:
Glad to see there's progress on lollipop :) I'd help testing if I didn't need a reliable ROM since I work 7 days a week. Keep up the great work everyone :)
[Verizon Galaxy Note 3 General] DavidFlory:
I am having problems. My SIM will not unlock and the phone is not connecting to Verizon Wireless.
[Verizon Galaxy Note 3 General] Red_Out:
David-

I had the same no sim problem after doing a "clean" flash of Temasek CM12 v6.1 hltevzw from a non-AOSP rom I was running at the time (I had gotten pissed with the data dropouts on CM11, which never really worked that great for me). I restored to a non-AOSP rom and everything worked great, so I figured it was an issue with Temasek CM12 v6.1. Here is where it gets weird. I had tried Temasek CM12 v3.5 a while back, but had the com.phone.android force close issue, I said whatever and left the zip on my phone for some reason. However, in between fc's, it did at least recognize my sim and have the correct APN data. So later yesterday I tried "clean" flashing v3.5 from the non-AOSP backup, let it boot, booted into recovery again, then "dirty" flashed v6.1. It worked beautifully. I have been up for about 24 hours now with no issues. This seems more stable, faster, and better battery than CM11 ever was for me, for sure a daily driver. Was running the NC4 modem this whole time and flashing using TWRP if it matters. This makes almost no sense to me why it would work, but it did, so I thought I would post the work around.
[Verizon Galaxy Note 3 General] capnkrunch:
Here's my guess at what's going on (without actually understanding most of it so take with a grain of salt). There were major RIL changes between 3.5 and 5.9. Since the NK1 modem has worked fine for me, something about the new RIL stack probably doesn't agree with older modems. Something from 3.5 persisted across a dirty flash that let's them play nice (my guess would be something in /data/data/com.android.providers.telephony/).

Like I said in the temasek thread I'll post an odinable NK1 when I get home from work. Hopefully that will solve things. If not, it's possible the RIL update (or parts of it) might be unnecessary (I just wholesale copy and pasted the hltespr files when I updated the vendor repo). If the modem doesn't fix things I can try a test build that reverts the RIL changes. That would be at least a few days out though so fingers crossed that the modem fixes it. In the meantime it's possible that a Titanium backup of Phone/Messaging Storage and/or Phone from a 3.5 install might fix things (try just Phone/Messaging Storage first; Phone might cause the FCs again).
[Verizon Galaxy Note 3 General] DavidFlory:
Report on my hltevzw SIM problem:

A dirty flash of v6.2 does not solve the problem. SIM not recognized.

Adding the line ro.telephony.get_imsi_from_sim=true to /system/build.prop does not solve the problem. Probably because if you cannot recognize a locked SIM you cannot get the IMSI.

A clean flash of v3.5 does allow the SIM to be unlocked and recognized. I was able to connect to Verizon. Then I followed with a dirty flash of v6.2 and the SIM unlocked and I did connect to Verizon and was able to get a full LTE/4G data connection. Still testing to see if I lose the connection.

I would love to test a NK1 modem to see if it solved the problem. Back on v3.5 I could unlock the SIM and connect but I could not get an LTE/4G data connection when my WiFi was off. Now on this way into v6.2 I can get an LTE/4G data connection.
[Verizon Galaxy Note 3 General] Red_Out:
Quick update:

Annnnnnd it's gone. Back to the no sim error. I paused a podcast I was streaming via bluetooth, walked into a building. Walked out, sim error and no APN again. It could have been due to losing reception while inside given it was a large metal roofed warehouse. I had not run into this issue recurring with previous restarts, so I doubt a system crash and reboot did it. I also noticed a bluetooth audio bug, where it will stream bluetooth audio, but once you swap apps (i.e. stitcher to spotify to youtube or vice versa) it will remain connected to the bluetooth audio, but no audio will play in either app. That may just be a software thing unique to me though. This was still v6.1. I'll give v6.2 a shot as well as NK1 when available.
[Verizon Galaxy Note 3 General] capnkrunch:
Sorry guys, no time to get NK1 up tonight. I'll do it tomorrow.

*missing beans :crying:*
[Verizon Galaxy Note 3 General] droidstyle:
Anybody ever fix the mic on their n3? Mine quit working yesterday, only speakerphone works.
[Verizon Galaxy Note 3 General] radionerd:
I had the pin hole mic clogged with dirt once. Canned air cleaned it out. (One dude stuck a pin in his to clear it, I was surprised he didn't pierce his mic element)

You probably know this; During normal calls the bottom pin hole is mic, and the top pin hole is noise cancelling mic.

While using speaker mic it's the opposite; Top pin hole is mic, bottom pin hole is noise cancelling mic.

To check if the mic is dead, call yourself on a land line, just brush your finger across the pin bottom pin hole, or blow into it slightly. If the level is down but still some receive audio, then it is probably dirty. The noise cancelling mic will have just a hint of receive audio.

In the past I flashed a CM11 build that didn't have mics configured correctly, Noise cancelling didn't work. Massive echo in caller's ear.
[Verizon Galaxy Note 3 General] capnkrunch:
Sorry about the wait, here is the NK1 modem. I've got my fingers crossed that this works for you guys.

https://www.androidfilehost.com/?fid=95916177934517848

EDIT: It's just like beans' were (zipped for space only). Unzip and flash in the AP slot in Odin.
[Verizon Galaxy Note 3 General] droidstyle:
Yea people can only hear me talk on speakerphone now. This started yesterday when I was out on the ice fishing. I forgot to zip my coat pocket so it fell out when I leaned over to pick up my flasher and hit the corner closest to the mic. The device is in a shock suit case and there are no signs of any damage other then the regular mic no longer works. I did notice a little slush and ice on the bottom, I also tried using compressed air to clean the mic hole. Still nothing...
[Verizon Galaxy Note 3 General] DavidFlory:
Downloaded and installed with Odin. About to dirty flash v6.3. So far, so good.
[Verizon Galaxy Note 3 General] LillieBennett:
Maybe it shook a connection loose?

---------- Post added at 01:41 AM ---------- Previous post was at 01:38 AM ----------

Last in basketbuild is 6.1, I must have missed a download switch.
[Verizon Galaxy Note 3 General] capnkrunch:
Haha, I did the same thing. He's been uploading on the third link for the past two versions.
[Verizon Galaxy Note 3 General] droidstyle:
That is what I am thinking...going to take it apart soon as I get #000 screw driver. I am thinking the microphone flex cable came loose.
[Verizon Galaxy Note 3 General] Capttwiggy:
Brain Fade

I have a DEVED Verizon Note 3 running Liquid Smooth 4.4.4. My problem is a brain fade and memory loss. I am having problems with MMS and video play. I have completely forgot anything and everything about flashing, ROMS, etc.

I would like to try Alliance, Eclispse or some of the other KK roms out there until LP is a bit more stable. I tried the Temasek CM 12 and could not get it to recognize my SIM card. I tried a clean flash of Aliance and Eclipse but it would just stall on the the Samsung logo.

Is there a trick I have forgot?

Modem? Bootloader?

I am currently using TWRP 2.8.4.

Thanks
[Verizon Galaxy Note 3 General] capnkrunch:
That's odd that clean flashing Alliance didn't boot. Maybe the issue is that Lollipop encrypts by default so you might need to wipe internal memory as well but I haven't had that issue downgrading before. As for Temasek's CM12 it seems like the NK1 bootloader fixes the SIM issue. Look a couple posts back for my link. Let us know if it solves the problem for you and maybe we can get it listed as a fix in Temasek's OP. Good luck!

EDIT: If you do try wiping internal memory make sure to backup your data first. On TWRP 2.8.4 you should be able to use MTP to get it or you could just reflash temasek and pull it that way.

EDIT: like [MENTION=4477763]DavidFlory[/MENTION] pointed out I meant NK1 modem not bootloader. For now the bootloader issue has no effect on anything except which version of TWRP you flash. Though if you feel like living on the edge [MENTION=766721]ryanbg[/MENTION] has a theoretical method of upgrading the bootloader that he needs a tester for (might hard brick your phone though).
[Verizon Galaxy Note 3 General] DavidFlory:
Do you really mean NK1 bootloader? For me it was the NK1 modem that fixed the SIM issue.
[Verizon Galaxy Note 3 General] capnkrunch:
Good catch; you are absolutely correct. I had a brain fart there.
[Verizon Galaxy Note 3 General] DavidFlory:
I have had good success with both Aliance ROM 2 and CM-12. Here are my software options:

(both)

Device: Verizon Galaxy Note 3 (SM-N900V Dev Ed)

Recovery: TWRP 2.8.4.0

Firmware/Modem: NK1

Bootloader: MJ3

(Alliance)

ROM: AllianceRom Build 2

Kernel: Lean Kernel 3.15 Recovery: TWRP 2.8.4.0

(CM-12)

ROM: CM12 [5.0.2] Temasek's hltevzw v6.6

GApps: PA Stock 5.0.1
[Verizon Galaxy Note 3 General] alexp1289:
Does the NK1 modem really fix the sim card issues? If so I'm going to flash it soon :)
[Verizon Galaxy Note 3 General] Capttwiggy:
Thanks guys, when I get to my desktop I will do some flashing. 7z is just compressed right? Assume just unzip and flash.

Thanks for the help

---------- Post added at 08:29 PM ---------- Previous post was at 08:17 PM ----------

I am unfamiliar with MJ3 bootloader. I am sure I have messed around with bootloaders in the past but don't want to start a brick festival. Where do I get it and do I flash it in AP?
[Verizon Galaxy Note 3 General] Capttwiggy:
Update....

So I odin flashed NK1.modem.tar.md5 in CP in Odin 3.09. Took just fine.

Flashed Temasek 6.6 via TWRP 2.8.4 and did a reboot. I had to pull the battery to get it to boot. Still no SIM service. What am I missing?

Thanks in advance.
[Verizon Galaxy Note 3 General] alexp1289:
That's a known issue for us Dev edition users. I thought nk1 modem would fix it but apparently not. I think it's still being worked on.
[Verizon Galaxy Note 3 General] Capttwiggy:
I am not sure I did it correctly, Odin changes the button names! I did not try wiping internal memory. I will see if I can get Alliance to work. Thanks for the help.

Sent from my SM-N900V
[Verizon Galaxy Note 3 General] alexp1289:
Did you put the Tar file in ap slot?