Related
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?
I am not very much familiar with all intricacies of Android system but i have played around rooting and putting customer firmwares on few devices.
I have AT&T Galaxy S3 with following detals:
Baseband: I747UCUEMJB
Version: 4.3
I had the device rooted in the past but recently un-rooted it and reset the flash counter as well and did factory reset. Did all that since i wanted to use ISIS and couldn't make it work on a rooted S3. Seems it used to work before till they updated ISIS app to patch it.
Now AT&T got 4.4 update and my phone detects it, downloads it but while installing fails at 32%. I have seen many threads where people faced similar issues due to their phones being rooted. Seems something on my phone didn't reset to default.
I found one post which mentions that i can download UCUEMJB_to_UCUFNE4_Firmware_update.zip and load it to phone using TWRP. As i understand, this will update the baseband but android version still remains at 4.3 (?). Is that the path i should be looking for or i am shooting in wrong direction? I want to stay on default firmware since i like to use ISIS till they keep running those cashback promos
Would appreciate some feedback.
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
DocHoliday77 said:
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
Click to expand...
Click to collapse
Thanks for the reply.
Just to confirm so that i don't mess up, i will apply the following(is modem same as firmware?) and then try OTA.
I747UCUEMJB: modem_CWM_I747UCUEMJB.zip
No. The modem is only one part of the firmware. Firmware includes bootloaders, kernel, system, modem and more.
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
Q&A for [Baseband] ALL T999, T999L, T999V, T999N Modems! w/ MAP and Data Tweaks!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
modem T999VVLUFNH2
Hi everybody,
I try to find the updated modem for my S3 (videotron SGH-T999v)
I have the modem T999VVLUFNF1 (ROM LS 3.1 stable KK 4.4.4, KT747 kernel)
When I unzip the official ROM of samsung (older like 4.1.2 and the last samsung update from september 2014) , I only find the file NON-HLOS.bin
According to sammobile the last videotron modem is T999VVLUFNH2, but I cannot find the file. This is the first time I try to update the modem because I have a poor reception in my house.
Thank you for your help
I haven't decided if I will post those or not. Too great a risk with the 4.4.2 modems. If you want to try the latest I can only recommend fully updating as a safe way to do so.
If you really want to be the one to test if it's safe, I'll get it uploaded for you, but understand there is a chance it could hard brick the phone beyond repair.
Reason for all of this is because we know if you flash a 4.4.2 modem on 4.3 it'll permanently brick it. I have no idea if flashing an older or newer 4.4.2 modem on 4.4.2 firmware (like you want to do) will result in the same. Normally, I would guess it wouldn't be the case, but it seems a lot has changed in these new builds that no one understands, and there have already been too many bricks for me to be comfortable trying something new like this without exercising great caution.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Thank you for your reply and your advise.
As I don't have enought money to take the risk, I will keep my actual modem.
Thank again
Don't blame you a bit! But don't forget, you can still fully update and that may help. (From what I've seen, flashing older modems on 4.4.2 doesn't brick, so i think if you updated, it should be ok to flash the NF1 modem if the newer one doesn't help. It might not work, but I don't think it would cause any harm. Just food for thought, but again, I can't guarantee anything with these latest modems...)
If it's a bad signal issue that you did not have before, call your carrier and ask if there are any tower/network/account issues they are aware of.
Your carrier probably doesn't do this, but Tmobile will sometimes give customers a signal booster for home use only. You can buy them online too, but I'm not sure how my h they are these days. (Just make sure it boosts the frequencies used by your carrier if you look into this.)
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Just noticed today that my phone is on T999VVLUFNF1 but that there is a newer 4.4.2 release for the T999V phone that is T99VVLUFNH2. Would it be good to update via Odin to this? Is it just a newer modem?
I have a T mobile T999 that is currently flashed with CyanogenMod 11-20141008-SNAPSHOT-M11-d2lte which is kitkat 4.4.4. The baseband version is T999UVDMD5. I have a Lebara sim card in it now, and I'm in France. I'm not getting any signal and I suspect it is because the baseband version mismatch. Is there anything I can do to make this setup work or do I have to downgrade to a different version of CM? Is there and updated modem I can flash on this device or any way to make it work?
abetterlie said:
I have a T mobile T999 that is currently flashed with CyanogenMod 11-20141008-SNAPSHOT-M11-d2lte which is kitkat 4.4.4. The baseband version is T999UVDMD5. I have a Lebara sim card in it now, and I'm in France. I'm not getting any signal and I suspect it is because the baseband version mismatch. Is there anything I can do to make this setup work or do I have to downgrade to a different version of CM? Is there and updated modem I can flash on this device or any way to make it work?
Click to expand...
Click to collapse
Latest baseband is NC2, flash it, and if the device still does not pick up service flash back to MD5 firmware and see if it will pick it up. If not then it might incompatible with your provider..
Thanks!!!! Also Those using T999 switched to ATT
Just wanted to say thank you!!!
Also just wanted to say for those who have a T999 that switched to AT&T this works (I wasn't sure if this would work since it didn't say anything about AT&T working with it. To be perfectly honest I didn't read everything but again THANKS!!!!!!
Hi Guys,
I got the OTA update ( T999UVUENC2 ) about a month back and since then, my Wifi has stopped working. It stays greyed out when I try to turn it on. Just won't turn on.
The logcat says that the "WiFi driver is unstable".
What I have tried so far (with no success):
1) Flash the same build again (T999UVUENC2).
2) Flash the root666_T999UVUENC2 build. (Currently, I am on this)
3) Flash Cyanogenmod 11.
4) Factory reset.
5) Pull the battery out when the phone is on and put it back again.
6) Modify/delete the wpa_supplicant.conf file.
Can someone please give any directions on how the "Wifi driver can be fixed"? I understand from going through the forums that downgrading from 4.3 to 4.2 can cause a brick. However, can I downgrade to the previous T-Mobile 4.3 build (T999UVUEMJC ) without causing a brick? Do you guys think that can help fix the Wifi?
Any help would be greatly appreciated.
Could you point me to what one exactly i need for T999LUVUBNF4
SGH-T999L Will Not Mount Ext Sd/No root or load file from .zip to root
I always get stuck at the boot screen where I am supposed to Update from Zip, but my phone NEVER lets me Mount the External SD card, I have a 64GB card, failed, 16 GB card, failed, what am I missing. All the good tutorials, ESPECIALLY yours, get me to that point but being unable to load that .zip file from sd just murders me. The Phone is on 4.3 and I believe I loaded your stock 4.3 firmware after failing to get this part done and then trying every single rom possible (didn't realize this had murdered me) until I managed to get back to this stock rom. Why does it not want to load from ext sd? Is it the file system? I've never had any issues with any of these sd cards, and they aren't generic cards, one is a samsung other a sandisk,
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.