[Galaxy Note 3 Android Development] ajm786:
I experimented with a theory I developed over the past few days about the instabilities that we all have been experiencing at random on our phones. This specific write up applies to my phone, which is the T-mobile SM-N900T. Regardless, it should still apply to you if you have a Note 3.

If you decide to follow this, make sure you download files that are specific to your Note 3. I am not responsible for you bricking your phone if you don't read.

Theory: instability is possibly caused by having a mismatched bootloader, baseband, CSC, and PDA.

When the NE6 firmware came out, I did a complete wipe and ODINed to the full stock ROM. That being said, for some reason there were always some oddities after having done that. My phone was utterly unstable, and I'd get random reboots all over the place. In addition, my baseband indeed said that I had NE6. Phone status reported it. However, SOME apps did not. One of those apps was Faux Sound; it reported I still had the NB4 baseband. I thought that it was just the app that needed to be updated.

I was wrong.

Doing some reading around on the T-mobile forums, I started to think that maybe I didn't do something right. I came across this app which is specific to Samsung phones and could read a lot more data than CPU-Z could.

https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo

Lo and behold: this app reported my BOOTLOADER as still being NB4, and my baseband as being NE6. The other screenshot that someone posted above is further proof of that; the baseband is different than the bootloader.

I immediately did a full backup to my external SD and followed this guide TO A “T”. I can’t stress it enough. FOLLOW THE GUIDE EXACTLY AS IT SPECIFIES, STEP BY STEP, substituting it with files specific to your phone.

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

What the guide doesn’t specify that I additionally did is:

1.	Before you do anything, do a full backup.

2.	Make sure you do #1.

3.	Using your custom recovery, do a full wipe on the device, including data. Wipe everything, leave no trace of anything behind.

4.	Follow the guide.

What I found was that even though I was ODINing the full ROM, it was not updating the baseband or modem properly. In order to do this, you must do TriangleAway, even though the phone reports that your flash count is 0. The goal is to ensure that when you go into download mode, your phone says that the binary is Samsung Official and there is nothing that says custom, everything should say Official, then flash the complete ODIN again.

After all this, I confirmed in the Samsung Phone Info app that my bootloader, baseband, CSC, and PDA were all reporting NE6.

To test my theory, I then decided to clean install one of the most unstable versions of Temasek that I had in recent experience: v98. If you read some of my posts regarding it, you’ll see that it was ridiculously unstable.

Looks like my theory was correct. I have not had a single reboot or FC on v98 since I installed it 2 days ago. That is pretty exciting to me, because like I said, v98 was the worst in terms of instability. I am getting the system UI restarting and kicking me back to the lock screen on occasion, but I only got that about 3 times, and only when swiping between the notification status and the QS tiles. I do think it’s just a bug with the build.

Bottom line: ENSURE THAT YOUR BOOTLOADER, BASEBAND, CSC, AND PDA ARE ALL MATCHING before you attempt to install CM11 or Temasek.

Hope this helps anyone with stability issues.