Develop Bugs

Chronic Mobile Data Issues with MK2 Baseband regardless of ROM

I never had any issues with my old M919, which is still sitting in a drawer awaiting a new display assembly I cannot afford. It was running CM 10 perfectly and no issues with HSPA or LTE. I was suffering for a while with an HTC Espresso which I could not S-OFF due to HBOOT being incompatible with AlphaRev. Anyway, I ended up with my old roomate's M919 about a week ago and have had nothing but issues getting mobile data to work properly.
It already had the MK2 Baseband installed-though I did not bother to check if it worked on the stock 4.3 ROM he had already installed. Nor did he ever say anything about issues. Anyway, I tried almost all of the Infamous ROM's(and all the kernels available with AROMA) as well as Cyanogenmod 10.2. All ROM's have major issues maintaining mobile data connection regardless of network mode or which cell I am on. Wi-Fi works flawlessly however. Also, to note, my fiance is running MK2 on her stock M919 so I have had a reference of which type of cell we are on and its signal strength.
So, finally I flashed the MK2 modem manually and rebooted into CM 10.2. That just made it completely unable to connect to any type of network although Wi-Fi worked just fine. So, now I am attempting to reinstall Infamous S4 from a full wipe to see if that will work, but after that I am out of ideas.

fallofredmond said:
So, finally I flashed the MK2 modem manually and rebooted into CM 10.2. That just made it completely unable to connect to any type of network although Wi-Fi worked just fine. So, now I am attempting to reinstall Infamous S4 from a full wipe to see if that will work, but after that I am out of ideas.
Click to expand...
Click to collapse
Have you checked your APN settings (versus your fiancés) to make sure they are correct? And to be completely fair, you could post in one of the many CM threads like this one here, you will target a much larger and focused support base. :good:

The whole mdl / mk2 radios are a mess. There are 2 radios, one for lte and one for hspa and below. The LTE one stays mdl and only the other is upgraded because of knox installation that some people are worried about (their warranty).
I believe what you may want to do is install the ota official for 4.3 to get all the correct radios and just forget about the warranty. There have been ways to reset the knox counter later down the road if you want to claim your warranty but I do not recall any guides.
I've started a thread here too for some clarifications on this subject so check that for answers too

POQbum said:
The whole mdl / mk2 radios are a mess. There are 2 radios, one for lte and one for hspa and below. The LTE one stays mdl and only the other is upgraded because of knox installation that some people are worried about (their warranty).
I believe what you may want to do is install the ota official for 4.3 to get all the correct radios and just forget about the warranty. There have been ways to reset the knox counter later down the road if you want to claim your warranty but I do not recall any guides.
I've started a thread here too for some clarifications on this subject so check that for answers too
Click to expand...
Click to collapse
First, there is currently NO METHOD to reset your KNOX counter, please do not give wrong information (which is why we have THIS thread).
Second, a link to this thread of yours would be useful, if you only linked it.
Third, "correct" radios are already freely available on XDA without taking the 4.3 OTA. He may have flashed an improper or incompatible modem.bin file, which is why his problem is occurring.

xdapowerapps said:
First, there is currently NO METHOD to reset your KNOX counter, please do not give wrong information (which is why we have THIS thread).
Second, a link to this thread of yours would be useful, if you only linked it.
Third, "correct" radios are already freely available on XDA without taking the 4.3 OTA. He may have flashed an improper or incompatible modem.bin file, which is why his problem is occurring.
Click to expand...
Click to collapse
Correct radio's without knox means that there is still an old LTE radio which creates and has been creating lots of problems for people.
I don't care about a flash counter anyway, and sorry did not mean to spread mis-information.
My thread is here: http://forum.xda-developers.com/showthread.php?t=2609962
the only answer I was given was one that told me to do the exact thing I didn't want to do, which is to flash the GSM MK2, but leave the LTE MDL.
-------------
I'm looking to see if anyone can help me find a way to flash the OTA update which contains KNOX (which includes the MK2 LTE) and also the MK2 GSM radio's.
The only downside I see to flashing KNOX (and the MK2 LTE) is this flash counter. I believe I heard somewhere you may not be able to flash new kernels, but I'm not sure if that is correct or not. If it is correct and I can not flash new kernels, I also do not care and don't know why so many people are okay with LTE radio's that go out all the time vs a flash counter+stock kernel

POQbum said:
Correct radio's without knox means that there is still an old LTE radio which creates and has been creating lots of problems for people.
I don't care about a flash counter anyway, and sorry did not mean to spread mis-information.
My thread is here: http://forum.xda-developers.com/showthread.php?t=2609962
the only answer I was given was one that told me to do the exact thing I didn't want to do, which is to flash the GSM MK2, but leave the LTE MDL.
-------------
I'm looking to see if anyone can help me find a way to flash the OTA update which contains KNOX (which includes the MK2 LTE) and also the MK2 GSM radio's.
The only downside I see to flashing KNOX (and the MK2 LTE) is this flash counter. I believe I heard somewhere you may not be able to flash new kernels, but I'm not sure if that is correct or not. If it is correct and I can not flash new kernels, I also do not care and don't know why so many people are okay with LTE radio's that go out all the time vs a flash counter+stock kernel
Click to expand...
Click to collapse
It's okay, we are all learning about information . The modem.bin file you flash in Odin replaces your old one (which is why the name of the file HAS to be modem.bin, otherwise nothing will get replaced).
Why do you WANT KNOX? KNOX is part of the bootloader for 4.3+. The guide you linked is how almost everyone has updated their modems on 4.2.2 bootloader.
If you are on 4.2.2 bootloader, follow these steps:
1) Download the 4.3 modem.
2) Place phone in download mode (Vol Down + Home + Power)
3) Open Odin and plug into computer.
4) Select "Phone" and then choose the modem.bin file.
5) Uncheck "Auto-reboot"
6) Press Start and wait 30 seconds after it says "Passed."
7) Restart phone.
I can almost guarantee you that this will work because this has been proven to work hundreds of thousands of times. I am on 4.2.2 MDL LTE (since I am already on 4.2.2) and I just flashed the 4.3 MK2 modem. I have no problems at all with data now.
EDIT: I am also using a 4.3 MK2 modem on 4.2.2 and have no issues.

xdapowerapps said:
It's okay, we are all learning about information . The modem.bin file you flash in Odin replaces your old one (which is why the name of the file HAS to be modem.bin, otherwise nothing will get replaced).
Why do you WANT KNOX? KNOX is part of the bootloader for 4.3+. The guide you linked is how almost everyone has updated their modems on 4.2.2 bootloader.
If you are on 4.2.2 bootloader, follow these steps:
1) Download the 4.3 modem.
2) Place phone in download mode (Vol Down + Home + Power)
3) Open Odin and plug into computer.
4) Select "Phone" and then choose the modem.bin file.
5) Uncheck "Auto-reboot"
6) Press Start and wait 30 seconds after it says "Passed."
7) Restart phone.
I can almost guarantee you that this will work because this has been proven to work hundreds of thousands of times. I am on 4.2.2 MDL LTE (since I am already on 4.2.2) and I just flashed the 4.3 MK2 modem. I have no problems at all with data now.
Click to expand...
Click to collapse
I want knox because I want the LTE radio which is tied to knox. I don't care if I have knox or not. My phone is not under warranty anyone, and if that is the only thing that is scaring people away then I have no reason to worry about knox.
I may try out this scenario but right now my phone reboots all the time and I've heard people having issues with LTE on 4.3 ROM's so I am not looking forward to spending hours configuring my phone only to wipe it all again, but it may work out better than I am thinking so I will give it a shot.
For reference, if there is a flashable full 4.3 ROM/.tar (with knox and the MK2 LTE included) out there and you could link me, I would appreciate it. I can't seem to find any which is odd.
Cheers

POQbum said:
I want knox because I want the LTE radio which is tied to knox. I don't care if I have knox or not. My phone is not under warrantly anyone, and if that is the only thing that is scaring people away then I have no reason to worry about knox.
I may try out this scenario but right now my phone reboots all the time and I've heard people having issues with LTE on 4.3 ROM's so I am not looking forward to spending hours configuring my phone only to wipe it all again, but it may work out better than I am thinking so I will give it a shot.
For reference, if there is a flashable full 4.3 ROM/.tar out there and you could link me, I would appreciate it. I can't seem to find any which is odd.
Cheers
Click to expand...
Click to collapse
There are 4.3 flashable ROMs out there but they will not give you what you want. You will HAVE to Odin flash a stock file to get what you're after.
Here are some links for the stock MK2 with KNOX included (choose whichever one is faster). :good:
http://www.sammobile.com/firmwares/3/?download=22280
http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
http://rapidgator.net/file/c98247edd8cd1cee88383ceef83a8c7f
Cheers mate!

xdapowerapps said:
There are 4.3 flashable ROMs out there but they will not give you what you want. You will HAVE to Odin flash a stock file to get what you're after.
Here are some links for the stock MK2 with KNOX included (choose whichever one is faster). :good:
http://www.sammobile.com/firmwares/3/?download=22280
http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
http://rapidgator.net/file/c98247edd8cd1cee88383ceef83a8c7f
Cheers mate!
Click to expand...
Click to collapse
Okay so I load this file: http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
How do I flash it through ODIN? Do you know what steps I need to do? Should I wipe data/cache first?
I've flashed a few things through ODIN because and am familiar with it

POQbum said:
Okay so I load this file: http://samsung-updates.com/details/16429/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUEMK2.html
How do I flash it through ODIN? Do you know what steps I need to do? Should I wipe data/cache first?
I've flashed a few things through ODIN because and am familiar with it
Click to expand...
Click to collapse
Open up odin, select PDA, choose the tar file you just downloaded.
Then put your phone in download mode (vol down + home + power), then connect it to your computer.
Once odin detects your phone, press start. It will take 15 to 20 mins and it will restart by itself.
After it reboots and for some reason you get stuck on the tmobile screen for more than 10 mins, go into recovery and wipe/data factory reset and wipe cache. Then your phone will boot up fine. Enjoy ^_^
Sent from my SGH-M919 using XDA Premium 4 mobile app

xdapowerapps said:
Have you checked your APN settings (versus your fiancés) to make sure they are correct? And to be completely fair, you could post in one of the many CM threads like this one here, you will target a much larger and focused support base. :good:
Click to expand...
Click to collapse
Both M919's are set to fast.t-mobile.com, although I haven't checked to see if the settings all match. I will definitely check that later.
As for threads here and elsewhere to solve the problem, I have tried pretty much everything I have seen. Most of what I have been reading on both CM and custom TW ROM threads is "me too" or "I don't have that problem".
POQbum said:
The whole mdl / mk2 radios are a mess. There are 2 radios, one for lte and one for hspa and below. The LTE one stays mdl and only the other is upgraded because of knox installation that some people are worried about (their warranty).
I believe what you may want to do is install the ota official for 4.3 to get all the correct radios and just forget about the warranty. There have been ways to reset the knox counter later down the road if you want to claim your warranty but I do not recall any guides.
I've started a thread here too for some clarifications on this subject so check that for answers too
Click to expand...
Click to collapse
Ok, now I just got thrown for a loop. Please use Heimdall to print your PIT and post it. On my PIT there appears to be only one partition with a radio... not 2.

xdapowerapps said:
There are 4.3 flashable ROMs out there but they will not give you what you want. You will HAVE to Odin flash a stock file to get what you're after.
Here are some links for the stock MK2 with KNOX included (choose whichever one is faster). :good:
Cheers mate!
Click to expand...
Click to collapse
I'm not waiting 4-8 hours to download a ROM. Yes, I understand those estimates are ads to try to get you to buy "premium membership" but still, do you have a legit mirror?

[Q] Use ATT ROM on a Tmobile Note 2

Hello to all. Is it possible to transform a Tmobile Note 2 into an ATT Note 2 using this ROM http://forum.xda-developers.com/showthread.php?t=2568537 ? I tried searching but couldnt find anything on it and since the ROM says its multicarrier I wanted to know if it was possible. I intend to use that Note 2 on net10 by the way. Thanks in advance!

Whatever you do, don't flash the AT&T note 2 modem. You can't make a T889 into a I317. You can make it look and mostly act like one though.
Hastily spouted for your befuddlement

Coug76 said:
Whatever you do, don't flash the AT&T note 2 modem. You can't make a T889 into a I317. You can make it look and mostly act like one though.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
So, If I intend to use the T889 with net10, which modem should I install in order for the phone to get LTE?

sentinel5000 said:
So, If I intend to use the T889 with net10, which modem should I install in order for the phone to get LTE?
Click to expand...
Click to collapse
As long as your note 2 is unlocked, you will be able to get LTE on AT&T. You can use the current ROM that you are using now... Nothing had to be done/changed. Just pop in the new SIM, put in the correct APN, and you're good to go.

kozmo21 said:
As long as your note 2 is unlocked, you will be able to get LTE on AT&T. You can use the current ROM that you are using now... Nothing had to be done/changed. Just pop in the new SIM, put in the correct APN, and you're good to go.
Click to expand...
Click to collapse
I see. Well then problem is my T889 is not unlocked, so I was thinking about downgrading it to 4.1.1. unlock it and then upgrade to 4.3. Thing is, How do I upgrade to 4.3? Cant seem to find the 4.3 stock rom here. The instructions on the jedi rom say one needs to be on 4.3 for wifi to work.

sentinel5000 said:
I see. Well then problem is my T889 is not unlocked, so I was thinking about downgrading it to 4.1.1. unlock it and then upgrade to 4.3. Thing is, How do I upgrade to 4.3? Cant seem to find the 4.3 stock rom here. The instructions on the jedi rom say one needs to be on 4.3 for wifi to work.
Click to expand...
Click to collapse
UVALJ1 modem on a T889 *should* get you to the point of being able to unlock. If not, odin the whole package (UVALJ1). MrRobinson's root66 works great.
If you have the 4.3 knoxed bootloader you may have issues with reverting.
Hastily spouted for your befuddlement

Coug76 said:
UVALJ1 modem on a T889 *should* get you to the point of being able to unlock. If not, odin the whole package (UVALJ1). MrRobinson's root66 works great.
If you have the 4.3 knoxed bootloader you may have issues with reverting.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I see. Well I have a T889 that had to be sent to samsung because the board died. Before it died, the phone had 4.1.2 and when it was returned fixed, the phone had 4.3. So, If I flash the UVALJ1 modem on my 4.3 T889 (stock non rooted) will I be able to unlock using this method: http://forum.xda-developers.com/showthread.php?t=2176721 or is that only for 4.1.1?

sentinel5000 said:
I see. Well I have a T889 that had to be sent to samsung because the board died. Before it died, the phone had 4.1.2 and when it was returned fixed, the phone had 4.3. So, If I flash the UVALJ1 modem on my 4.3 T889 (stock non rooted) will I be able to unlock using this method: http://forum.xda-developers.com/showthread.php?t=2176721 or is that only for 4.1.1?
Click to expand...
Click to collapse
Dunno. You could ask in the thread, someone there may know. Good question though.
Hastily spouted for your befuddlement

Coug76 said:
Dunno. You could ask in the thread, someone there may know. Good question though.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Ok. So I tried flashing in Odin Mr. Robinsons 4.1.1 image in order to unlock my phone, Tried it 3 times but it always resulted in a Fail. I searched a bit and apparently the Knox thing prevents from downgrading so I flashed Mr. Robinsons 4.3 image and to my surprise the phone booted back up like it was before, all my settings, everything was there. Only new thing is that now my T889 was rooted... Which is a good thing but still I cant unlock my phone

sentinel5000 said:
Ok. So I tried flashing in Odin Mr. Robinsons 4.1.1 image in order to unlock my phone, Tried it 3 times but it always resulted in a Fail. I searched a bit and apparently the Knox thing prevents from downgrading so I flashed Mr. Robinsons 4.3 image and to my surprise the phone booted back up like it was before, all my settings, everything was there. Only new thing is that now my T889 was rooted... Which is a good thing but still I cant unlock my phone
Click to expand...
Click to collapse
You might have luck flashing the UVALJ1 modem only. If that is successful, the unlock should work.
Hastily spouted for your befuddlement

sentinel5000 said:
Ok. So I tried flashing in Odin Mr. Robinsons 4.1.1 image in order to unlock my phone, Tried it 3 times but it always resulted in a Fail. I searched a bit and apparently the Knox thing prevents from downgrading so I flashed Mr. Robinsons 4.3 image and to my surprise the phone booted back up like it was before, all my settings, everything was there. Only new thing is that now my T889 was rooted... Which is a good thing but still I cant unlock my phone
Click to expand...
Click to collapse
I've got the same phone and, thanks to my recently flashing (with Odin) to 4.3 Stock, I think I'm in about the same situation if I were to want to revert. As I understand, once you've gone to the stock 4.3 bootloader - however you got there, via Odin flash, OTA update or factory returns phone to you with it - you can no longer use Odin to revert anything because with Odin you're flashing an entire image - bootloader, modem, ROM, Kernel - and you now need to cherry pick non-bootloader items you'll revert. You can't get rid of the locked down 4.3 bootloader at all.
I am hoping we can still use Odin to at least go back to stock 4.3. I'm actually going to try that in a bit and mess with my flash counter - it seems to not want to reset that's another subject.
I'm not sure if the 4.3 bootloader prevents going back to an older modem or not - I might try that too and see what happens. If it does not, then these steps might get you back to an unlockable state - might also trip your Knox Warranty Void along the way in case if that concerns you. Mine is tripped and I'm really not sure why or when it happened.
1) Get GooManager off Play Store and use it to install custom recovery - you need this because you can no longer just flash an entire pre-4.3 image thanks to the 4.3 bootloader
2) Using custom recovery, flash UVALJ1 modem & Odexed or Deodexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2102380
If it'll boot at this point, you should be able to do the unlock thing - this is how I originally unlocked mine last April - but that was pre-4.3-locked state for me. If we cannot get back to that unlockable state, I'm going to be really sorry I knowingly let myself get locked down by 4.3 - I assumed at the time last week that it wouldn't affect that much but in hindsight I'm afraid I shoulda thought about it a bit more lol.
Hope this helps!

Coug76 said:
You might have luck flashing the UVALJ1 modem only. If that is successful, the unlock should work.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Ok, So I finally found the UVALJ1 modem and flashed it on my T889. Tried the unlock method and it worked like a charm. Thanks for all that tried to help and to Cough76, that was a great suggestion. :good:

LanceDiamond said:
I've got the same phone and, thanks to my recently flashing (with Odin) to 4.3 Stock, I think I'm in about the same situation if I were to want to revert. As I understand, once you've gone to the stock 4.3 bootloader - however you got there, via Odin flash, OTA update or factory returns phone to you with it - you can no longer use Odin to revert anything because with Odin you're flashing an entire image - bootloader, modem, ROM, Kernel - and you now need to cherry pick non-bootloader items you'll revert. You can't get rid of the locked down 4.3 bootloader at all.
I am hoping we can still use Odin to at least go back to stock 4.3. I'm actually going to try that in a bit and mess with my flash counter - it seems to not want to reset that's another subject.
I'm not sure if the 4.3 bootloader prevents going back to an older modem or not - I might try that too and see what happens. If it does not, then these steps might get you back to an unlockable state - might also trip your Knox Warranty Void along the way in case if that concerns you. Mine is tripped and I'm really not sure why or when it happened.
1) Get GooManager off Play Store and use it to install custom recovery - you need this because you can no longer just flash an entire pre-4.3 image thanks to the 4.3 bootloader
2) Using custom recovery, flash UVALJ1 modem & Odexed or Deodexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2102380
If it'll boot at this point, you should be able to do the unlock thing - this is how I originally unlocked mine last April - but that was pre-4.3-locked state for me. If we cannot get back to that unlockable state, I'm going to be really sorry I knowingly let myself get locked down by 4.3 - I assumed at the time last week that it wouldn't affect that much but in hindsight I'm afraid I shoulda thought about it a bit more lol.
Hope this helps!
Click to expand...
Click to collapse
Well, Flashing the UVALJ1 modem on my T889 with the Jedi Master X 4.3 custom ROM worked like a charm. There was no need to flash the whole image. Just the modem was enough. Hope it helps for those who are on 4.3 and need to unlock their Note 2.

Let me ask this using the same thread just to not open a new one. Well my new question is, After I flashed the UVALJ1 modem I was able to unlock the phone but I noticed I cant get 4GLTE anymore. So If I flash the newest modem for 4.3 will I lose Unlock on the phone? Thanks in advance!

No unlock sticks
Sent from my Nexus 7 using Tapatalk

sentinel5000 said:
Let me ask this using the same thread just to not open a new one. Well my new question is, After I flashed the UVALJ1 modem I was able to unlock the phone but I noticed I cant get 4GLTE anymore. So If I flash the newest modem for 4.3 will I lose Unlock on the phone? Thanks in advance!
Click to expand...
Click to collapse
You'll be fine. It should stick with you.
As you found out, UVALJ1 doesn't support LTE. It gave my phone epic battery life though. The original rom was phenomenal on battery. Subsequent releases lowered battery life until LTE was support dropped then battery was relatively crappy. It always had to hunt for LTE which sucked as it released when Las Vegas was the only market tmo supported.
Hastily spouted for your befuddlement

Coug76 said:
You'll be fine. It should stick with you.
As you found out, UVALJ1 doesn't support LTE. It gave my phone epic battery life though. The original rom was phenomenal on battery. Subsequent releases lowered battery life until LTE was support dropped then battery was relatively crappy. It always had to hunt for LTE which sucked as it released when Las Vegas was the only market tmo supported.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Yeah I noticed that flashing the UVALJ1 modem gave my Note 2 excellent battery life. Since here where I'm from T mobile just has 3 small areas of LTE and none apply to me then Ill just stay with UVALJ1. Thanks again!

little more help
LanceDiamond said:
I've got the same phone and, thanks to my recently flashing (with Odin) to 4.3 Stock, I think I'm in about the same situation if I were to want to revert. As I understand, once you've gone to the stock 4.3 bootloader - however you got there, via Odin flash, OTA update or factory returns phone to you with it - you can no longer use Odin to revert anything because with Odin you're flashing an entire image - bootloader, modem, ROM, Kernel - and you now need to cherry pick non-bootloader items you'll revert. You can't get rid of the locked down 4.3 bootloader at all.
I am hoping we can still use Odin to at least go back to stock 4.3. I'm actually going to try that in a bit and mess with my flash counter - it seems to not want to reset that's another subject.
I'm not sure if the 4.3 bootloader prevents going back to an older modem or not - I might try that too and see what happens. If it does not, then these steps might get you back to an unlockable state - might also trip your Knox Warranty Void along the way in case if that concerns you. Mine is tripped and I'm really not sure why or when it happened.
1) Get GooManager off Play Store and use it to install custom recovery - you need this because you can no longer just flash an entire pre-4.3 image thanks to the 4.3 bootloader
2) Using custom recovery, flash UVALJ1 modem & Odexed or Deodexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2102380
If it'll boot at this point, you should be able to do the unlock thing - this is how I originally unlocked mine last April - but that was pre-4.3-locked state for me. If we cannot get back to that unlockable state, I'm going to be really sorry I knowingly let myself get locked down by 4.3 - I assumed at the time last week that it wouldn't affect that much but in hindsight I'm afraid I shoulda thought about it a bit more lol.
Hope this helps!
Click to expand...
Click to collapse
Can you provide some additional detail on how to use goo manager and which custom recovery to install? (a lost newbie)
Thanks

What's the deal with lte radio?

hey guys I'm on 4.2.2 still. Rooted it and deleted the galaxy walking app, so haven't been able to do legit update, and with working alot just haven't fooled with it. Anyway I'm off and have time, want to come up to kitkat, am I not able to update my LTE radio? I'm reading and searching before turning to asking, but all I'm seeing is if I update it my sound will act up. Am I stuck on an old radio now? Was hoping for improved signal, can I go stock, update and reroot and everything will be current?? Anyway any help is appreciated.

If you don't care about tripping Knox counter, just flash the NB4 firmware with Odin and you'll be good.. I recommend fenny's fixed firmware
Edit: well it will only trip if you flash custom recovery or kernel, other than that there is root method without tripping if you plan to stay stock

serio22 said:
If you don't care about tripping Knox counter, just flash the NB4 firmware with Odin and you'll be good.. I recommend fenny's fixed firmware
Edit: well it will only trip if you flash custom recovery or kernel, other than that there is root method without tripping if you plan to stay stock
Click to expand...
Click to collapse
im not staying stock, just want the updated lte radio on it. thinking of going lg g3 since sammy become such a pain in the ass. I've flashed stock and am updating official kitkat now, i guess that will update my modem and lte radio also, i'll reroot after that and throw something on there

If you are updating officially there shouldn't be a reason to manually update anything

i was just trying to save time, my home internet is crappy ( 100.00 bucks a month for 5mb, more like 1-3 mb) and you have to use wireless to update. I'm on kit now, abut to root and find a rom

sleekgreek said:
i was just trying to save time, my home internet is crappy ( 100.00 bucks a month for 5mb, more like 1-3 mb) and you have to use wireless to update. I'm on kit now, abut to root and find a rom
Click to expand...
Click to collapse
There is a thread in general specifically for updating radios for those of us still on MDL. If you were to have followed that guide you would have updated your radio without any sound problems, would still be KNOX free, and would still be able to have the option to run 4.2.2, 4.3, and 4.4.x ROMs flawlessly.

lordcheeto03 said:
There is a thread in general specifically for updating radios for those of us still on MDL. If you were to have followed that guide you would have updated your radio without any sound problems, would still be KNOX free, and would still be able to have the option to run 4.2.2, 4.3, and 4.4.x ROMs flawlessly.
Click to expand...
Click to collapse
i've been searching here for years on everything. Unless you stay in the loop everything is just cluttered. Even rooting, I'm looking and reading threads from pre 4.4.2 where chainfire link was last updated in 2013, it sucks searching here. And I thank you guys for the help. I'm rooted now and didnt want to ota, but everything I found to read said I could update the modem but not the LTE radio without sound issues... I must of missed something. LOL, I had a ton of tabs open from searches before posting. Been rooting since iden on nextels in early 2000's so it's just basic info I need thats hard to find here , tons of threads I guess. Anyway lets a get rom on this thing..

sleekgreek said:
Unless you stay in the loop everything is just cluttered. Even rooting
Click to expand...
Click to collapse
I totally agree and understand. I've pretty much been tinkering around the S4 forums since a few weeks after release (before I even purchased my S4) and have followed pretty well everything from square one so it's pretty easy to remember THAT I've read something but not remember WHERE I read it... Looking back through the Q&A and General threads, I couldn't imagine just now getting into the S4.

lordcheeto03 said:
There is a thread in general specifically for updating radios for those of us still on MDL. If you were to have followed that guide you would have updated your radio without any sound problems, would still be KNOX free, and would still be able to have the option to run 4.2.2, 4.3, and 4.4.x ROMs flawlessly.
Click to expand...
Click to collapse
I would be interested in that thread... I have updated my GSM modem (modem.bin) to NB4 but as I understood it, the LTE part is tied to the bootloader. So, those of us with MDL have to retain the MDL LTE radio. If it is possible to update the LTE radio, without the sound/wifi problems, and retain MDL bootloader and thus no Knox, I'd love a link!

Frankenscript said:
I would be interested in that thread... I have updated my GSM modem (modem.bin) to NB4 but as I understood it, the LTE part is tied to the bootloader. So, those of us with MDL have to retain the MDL LTE radio. If it is possible to update the LTE radio, without the sound/wifi problems, and retain MDL bootloader and thus no Knox, I'd love a link!
Click to expand...
Click to collapse
Ahh, you got me on that one. It didn't even register to me that the LTE modem is unaffected by that method. My apologies.

Second Hand Note II, cannot get cellular data

I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.

GreatGrizzwald said:
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
Click to expand...
Click to collapse
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
http://www.sammobile.com/

absinthesummer said:
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
Thank you very much for the advice. I am downloading the firmware now. baseband version is showing i317ucama4. Right now the phone is not activated with AT&T, is there a way I could test if I will be able to get cellular data before going to AT&T and activating it?
Click to expand...
Click to collapse

Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.

Just use your father's sim card. Either it connects to the GSM network or it doesn't.

absinthesummer said:
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Click to expand...
Click to collapse
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?

1425
rangercaptain said:
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
Click to expand...
Click to collapse
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.

GreatGrizzwald said:
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
Click to expand...
Click to collapse
It sounds like the phone was updated previously to either 4.3 or 4.4.2, which have Knox and that pesky counter. Technically you can't directly downgrade, so be sure you're downloading firmware that is 4.3 or higher. I didn't realize sammobile only went to MA4 for US AT&T. (In a pinch you can use Canadian firmware, but we have other links for stock firmware). Also, don't worry too much about Kies. It can be helpful, but honestly I could never get my note 2 recognized by kies either.
When I get back from taking my kids to school, I'll gather some links that will help you revive this phone Links below:
@GreatGrizzwald:
More recent links to stock firmware: STOCK PACKAGES TO MK6 This is LJ2 (4.1.2), MK6 (4.3) and up. He's got all the stock firmwares, available for flashing either in recovery on via odin. I've highlighted the one I would use in the attached screenshot (MK6- ODIN)
He also has a thread for NE5 (The latest firmware, 4.4.2) HERE
So if MK6 doesn't work, try NE5. One of those two has to work. You're dad already updated to either 4.3 or 4.4.2, I don't know which so start with 4.3 (MK6) and if it doesn't work try 4.4.2 (NE5)
On those two threads, he has a TON of links that will be helpful to you in getting back to stock also.
And here's a reference page with some useful links: One Stop Shop
This one is dedicated to downgrading back to LJ2 (4.1.2) from 4.3+, it MIGHT come in handy for you: Downgrade Instructions
If you have trouble with the stock firmware, you can also try Chainfire's CF Auto Root. It's stock firmware but it's rooted. Try the other firmwares by Zen Arcade first though CF AUTO ROOT
We'll get it going for you The stock firmware will re-flash the modem and all the configuration files so you're data should work again. Then you can do whatever you want, root, recovery, flash other stuff, or leave it stock. You got this
---------- Post added at 07:51 AM ---------- Previous post was at 07:09 AM ----------
GreatGrizzwald said:
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
Click to expand...
Click to collapse
Also you have to figure out if it's software or hardware. I'm inclined to believe it's software so I think if you get it back to stock you'll be good. If it was hardware, it wouldn't even recognize a sim being inserted (recently repaired an htc one mini with this problem, it needed a new Sim tray, thankfully it was only $20).
But it sounds more like a bad flash corrupted some of those important files and configurations controlling data connections, it's all good, if it's software it can definitely be fixed. If it were hardware it could still be fixed it would just be a bit more time consuming.

One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.

absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Thank you for all this, I will start working with it today. You have been a huge help.

GreatGrizzwald said:
Thank you for all this, I will start working with it today. You have been a huge help.
Click to expand...
Click to collapse
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!

1100
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.

GreatGrizzwald said:
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
Click to expand...
Click to collapse
That is great news! I'm so glad it's working for you. Enjoy your (new-to-you) note 2 and keep those files on hand in case you need them in the future!

absinthesummer said:
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
Click to expand...
Click to collapse
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?

GreatGrizzwald said:
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
Click to expand...
Click to collapse
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.

absinthesummer said:
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
Click to expand...
Click to collapse
Awesome, that makes a lot more sense now. Thanks again.

Hey I forgot you don't have custom recovery. Anyway, I sent you PMs,and you can do a search of this very forum- use the search term "update" or "ota" and you will find a LOT of threads on boot failures after OTA. Most people got their phones back.
If you can't get into DL mode (Vol-, Home, Power), try getting into the stock recovery (Vol+, Home, Power) because you should/could be able to factory reset the device from there. Also hold the button combo longer than usual. If one recovery option (DL mode) isn't working, than theoretically the other should still be accessible, through which you can adb sideload to the device or try factory reset. I know it's frustrating, but you're not the first nor the last to have an OTA go wrong ;/ We'll get ya back up & running.
You're not the only one in trouble after that update: http://forum.xda-developers.com/galaxy-note-2-att/help/todays-update-soft-bricked-phone-t2939649

Bad/no reception on T999L, need help/suggestions

These issues started with the upgrade to latest T-Mobile 4.3 software pack at the end of November. Phone operated perfectly before then. After the update, the phone would periodically not receive/place calls/texts/use data. The issue kept worsening daily. It is not related to the SIM card or location, as the card has been replaced and tested in an alternate phone where it performs perfectly.
The T999L was then consequently rooted, KNOX flagged (it's already past warranty, Samsung wouldn't give a rat's ass about it), flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted. Restored to stock 4.1.2, same issues. Did 3 updates OTA to get to latest 4.3, same issues.
Messed around with 4636 menu, 2263 menu, etc. Some changes had a temporary result but nothing permanent. Calls to the phone are redirected to voicemail. When placing a call, it takes 5-10 seconds to either place it or disconnect it (as it can't connect to the network, I guess?). The bars on the phone show 3-4 bars typically, but the phone is rarely able to acquire a data connection. Again, this is not the case with other phones the SIM is tried on.
Any suggestions? I've spent probably close to 10 hours researching this and trying everything out and I am absolutely stumped. This is my mom's phone and a replacement Alcatel OneTouch Fierce 2 just "doesn't look nice", so I'm getting a fair bit of *****ing for trying to help solve this, even though it's not my fault. Would appreciate some help before Christmas.

Have you tried updating the modem?

systemcode said:
Have you tried updating the modem?
Click to expand...
Click to collapse
flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted.
Click to expand...
Click to collapse
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238

dwegiel said:
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
Click to expand...
Click to collapse
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.

nirogu325 said:
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
Click to expand...
Click to collapse
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.

dwegiel said:
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
Click to expand...
Click to collapse
Well, OTA updates can sometimes fail, that's why I gave you the ODIN firmware link. It's the best help I can offer.