So, I was given a T-Mobile SGH-T999 that someone had found a while back, but was unable to get activated. It didn't have a SIM in it, and I think it may even have been used off T-Mobile at some point (based on evidence below). Checking the IMEI it seems that it's only blocked on T-Mobile (AT&T says they do not have a block against this IMEI, and it's not showing up in any lost/stolen databases), so I'm guessing non-payment or carrier unlock. I would like to SIM unlock it, but I'm not entirely sure what has been done to this phone. I've never owned or played with a Galaxy S3, so my only knowledge has been from digging around this forum for a couple hours. Here's what I can tell you from looking through this phone. I'm hoping to get some advice on my next course of action:
Model number SGH-T999
Android Version 4.1.2
Baseband version T999UVDMD5
Kernel version 3.0.31-1128078 [email protected] #2 SMP PREEMPT Mon Apr 15 11:59:10 KST
Build number JZO54K.T999UVDMD5
Device Status Modified
Odin Mode
Product name SGH-T999
Custom Binary Download: Yes (1 counts)
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
I first tried SIM unlock, only to eventually find out that I would need to downgrade from 4.1.2 to 4.1.1. The threads I've read on downgrading indicate that to get back down to official 4.1.1 I need to be stock to begin with. I don't think this phone is rooted because I am unable to "su" when using adb shell or browse directories like /data. However, Odin saying it has a custom binary, and the device status saying modified makes me believe this phone was rooted at some point. Again, I have no experience with the GS3, so I may be way off base (I don't even know if Odin is the stock recovery).
So, before I can downgrade to 4.1.1 do I need to use Triangle Away, reset the flash counter, etc? Or, can I just use Odin to flash 4.1.1. Finally, will I also need to flash a different modem even after that?
I'd appreciate any advice and help you can give me. Thanks.
Thanks for doing some research before posting. Its refreshing to see you picked up basics even if you have never used this model before.
You didn't mention if there's a custom recovery such as TWRP or CWM. If it was there and you were brave or comfortable enough, I'd have suggested a 4.1.1 modem to flash (UVDLJC).
So to your question on unlock, essentially, your best bet is to flash a Root66 of UVDLJC version. Read the first post of Root66 completely word for word before you download and flash. Less chances of hard brick that way. A Root66 is a Galaxy S* family term for rooted stock firmware. It just has root injected in it. Everything else is just stock. So it does not trip the flash counter.
Now your counter is already tripped. So you will have to use Triangle away as you already know. So after Root66 and Triangle Away, you will be all stock and good to go. Follow the process for unlock as you have already found out and then go with ATT.
Now if you wish, after the unlock, you can flash UVDMD5 version of Root66 and you will get JB 4.2.1. Do not flash UVUEMJC version of Root66. Locked bootloader and efuse hardbrick lie in that direction.
Perseus71 said:
Thanks for doing some research before posting. Its refreshing to see you picked up basics even if you have never used this model before.
Click to expand...
Click to collapse
No problem. I work in IT, so I know the frustration of someone asking for help without even trying to do any basic research first
You didn't mention if there's a custom recovery such as TWRP or CWM. If it was there and you were brave or comfortable enough, I'd have suggested a 4.1.1 modem to flash (UVDLJC).
Click to expand...
Click to collapse
Looks like I should have done my research a bit better. I misunderstood, thinking that Odin was some sort of recovery. Just looked up how to get into recovery, and it looks like stock to me (it just reads Android system recovery 3e). So, it is possible to just simply flash LJC modem on 4.1.2 so I can unlock, or am I misunderstanding?
So to your question on unlock, essentially, your best bet is to flash a Root66 of UVDLJC version. Read the first post of Root66 completely word for word before you download and flash. Less chances of hard brick that way. A Root66 is a Galaxy S* family term for rooted stock firmware. It just has root injected in it. Everything else is just stock. So it does not trip the flash counter.
Now your counter is already tripped. So you will have to use Triangle away as you already know. So after Root66 and Triangle Away, you will be all stock and good to go. Follow the process for unlock as you have already found out and then go with ATT.
Click to expand...
Click to collapse
Just to make sure I understand correctly, it IS Triangle away first, then Route66 second? If I'm interpreting correctly, I can do this even if not rooted? All the devices I've ever flashed ROMs to before (even when going back to stock ROM) needed a custom recovery and/or root. But, since this device doesn't appear to be rooted, I just wanted to make sure I don't need to root before flashing Route66.
Now if you wish, after the unlock, you can flash UVDMD5 version of Root66 and you will get JB 4.2.1. Do not flash UVUEMJC version of Root66. Locked bootloader and efuse hardbrick lie in that direction.
Click to expand...
Click to collapse
Thank you so much for the information. Once I get everything in order, and the SIM unlocked, I'll probably spend many hours researching how I want to progress (so you've already helped cut down that time). I honestly haven't come across modem flashing in previous devices, so I will definitely need to read more to fully understand the implications.
Out of curiosity, do you have any theories on how the flash counter was tripped? Everything appears to be stock, but the flash counter and device status seem to indicate otherwise. Just trying to figure out the history of this device. Again, thanks so much for the help.
Really everything Perseus said is on point, except you don't need to use triangle away because really that's just to reset the counter and its unnecessary for you.. You can either flash a custom recovery and flash the LJA or LJC modem to do the unlock, or Odin the LJA or LJC firmware and proceed with the unlock
Edit: and to answer how the counter was tripped, it looks like they may have rooted it at some point and then unrooted it and returned it to stock.. The counter does not change
Sent from my SGH-M919 using Tapatalk
YabosMcGee said:
Looks like I should have done my research a bit better. I misunderstood, thinking that Odin was some sort of recovery. Just looked up how to get into recovery, and it looks like stock to me (it just reads Android system recovery 3e). So, it is possible to just simply flash LJC modem on 4.1.2 so I can unlock, or am I misunderstanding?
Just to make sure I understand correctly, it IS Triangle away first, then Route66 second? If I'm interpreting correctly, I can do this even if not rooted? All the devices I've ever flashed ROMs to before (even when going back to stock ROM) needed a custom recovery and/or root. But, since this device doesn't appear to be rooted, I just wanted to make sure I don't need to root before flashing Route66.
Click to expand...
Click to collapse
Yes that's stock recovery. You can't flash modems with it. If you have custom recovery then the flash counter will keep on tripping at every boot. Best if use ODIN to flash LJA or LJC firmware, do the unlock and then flash MD5 firmware so you are back to JB 4.2.1. Triangle Away's purpose is to reset that flash counter you saw. I do believe it needs Root. I don't remember since I did it so long ago. I just thought you will want to it after all this flashing is done so its all squeaky clean.
YabosMcGee said:
Thank you so much for the information. Once I get everything in order, and the SIM unlocked, I'll probably spend many hours researching how I want to progress (so you've already helped cut down that time). I honestly haven't come across modem flashing in previous devices, so I will definitely need to read more to fully understand the implications.
Click to expand...
Click to collapse
Theoretically with android architecture, it could be done on any device. The trick lies in remounting that partition as read-write correctly. Have fun reading this.
YabosMcGee said:
Out of curiosity, do you have any theories on how the flash counter was tripped? Everything appears to be stock, but the flash counter and device status seem to indicate otherwise. Just trying to figure out the history of this device. Again, thanks so much for the help.
Click to expand...
Click to collapse
Looks like Serio beat me to it. He's spot on where the origins of the tripped counter is concerned.
Thanks Persus77 and serio22. Everything worked out great.
Related
Hi, I am sure there are countless threads out there already talking about the inconveniences that 4.3 bring and the problem you get for trying to downgrade. I have read through many of them and I think I have the general idea of how to downgrade relatively safely without running into the problems I am currently aware of. I want to confirm what I know. I would like to be informed before I do anything, especially something as dangerous as a downgrade attempt.
So all that I am aware of right now is that 4.3 brings in a new bootloader, attempts on trying to change the bootloader will result in hard brick, so does that mean any previous firmware that does not flash a bootloader will be fine? will stock firmware from sammobile work? I am looking at this one right now,
http://www.sammobile.com/firmwares/3/?download=16006
Second problem is 4.3 also changes the efs format, any modem before I think MG4 won't be able to read it, and you won't get network, this should be easily fixed by flashing the latest modem here
http://forum.xda-developers.com/showthread.php?t=1831898
...right? also the modems are made custom recovery flashable, if I want to use odin instead, do I just unzip and put the modem.bin into odin?
Also plans to root first and backup efs, I hear you have to go through hell to get it back if you lose it...
Doing any of those should trigger the knox counter...so basically anyone that still have warranty left and plan to use it cannot do anything...even rooting...right?
But that should be the least of your worries if you are determined to downgrade...
I am not sure if that is all the trouble I will run into, I don't know what made samsung so confident that they can even say it is impossible to downgrade, they meant to say difficult but you can do it, right?
also I am on SGH i747m bell.
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 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
Hello,
I just bought my first Galaxy device (had a CDMA LG for a while, and I have a Nexus Tablet), and I am looking at how to get this new phone set up right. I bought my i747 retail, so I was unable to unlock it. However, now I'm struggling with finding the right method for upgrading, rooting, etc. I know nothing about knox or any of these Samsung intricacies. Could someone please give me a little guidance on how to go about getting to the OS and status that I'm looking for? This is what I've done so far:
Came unrooted with 4.1.2 stock rom
Unlocked using legit unlock code
Tried OTA updates, but none were available (must be because of unlock)
Rooted w/ ODIN using 4.1.1 file based of MrRobinson method. (http://forum.xda-developers.com/showthread.php?t=1739426)
Now I keep getting popups like process. ... .acore,media, etc. stopped.
I'm looking to ideally get a custom recovery (either CWM or TWRP, whichever is better) and either kitkat Touchwiz or possibly kitkat nexus stock (I read somewhere that it was possible). Also, i just bought it, and have the code still, so I don't mind deleting everything if needed. Regardless, I'd like the ability to get it back to pure stock with no flash counter (I have a manufacturer's warranty I want to use if need be).
Could someone please just give me a little guidance? I'm pretty capable with rooting, etc., so you'd only need to lead me to other threads, etc. that will take me where I want to go. Thank you very much.
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
audit13 said:
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
Click to expand...
Click to collapse
Well, the bad news is I already flashed using MrRobinson's instructions, and now my phone is barely workable, as things like process.android.media and Touchwiz keep crashing. I was able to install the info app though, and my bootloader is listed as I747UCDLK3. Thanks again though, and let me know what else you need from me.
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
audit13 said:
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
Click to expand...
Click to collapse
Thank you, but wouldn't OTA updates install Knox, which would basically void my warranty if I tried to flash anything after that? And, I've checked for OTA updates twice, once on 4.1.2 and on 4.1.1, and both times it said my software was up to date.
I spoke with StoneyJSG about my situation, and he suggested that I go to stock 4.1, root w/ saferoot, then flash a kitkat custom rom without Knox through TWRP. That way, I could use triangle away and flash stock unrooted if I needed to send it in.
Although, I'm not sure if I should do that, as I thought I read that you need to update the radio and bootloader first before you can install a custom kitkat rom from jelly bean, but I'm still not entirely sure how that works.
The most recent release of many custom ROMs will not work but you may not have a signal without an updated modem and you should not be running updated modems on an older bootloader. Doing this could brick your phone.
With a rooted system, OTA updates will not work.
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
jateed said:
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
Click to expand...
Click to collapse
What is your cell service? If not AT&T, you will never get OTA.
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
audit13 said:
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
Click to expand...
Click to collapse
Well, I have an AT&T model which I unlocked and will be putting on Cricket at the end of the week (when my plan month is set to end). Right now there's no SIM in it, and I've been doing everything over wifi. I looked up whether the carrier had something to do with the OTAs, and I was told that Samsung sent the updates out, not AT&T, so I figured that the carrier info was irrelevant. I now wonder what my options are.
Can I manually flash 4.3 stock without tripping the knox warranty void?
Does Towelroot/Xposed framework trip the Knox void flag?
If I can update to 4.3/4.4 and root without tripping the knox flag, I might just manually update and just run towelroot and xposed to modify my OS the best I can until my warranty runs out.
If I can't root it at all once I'm on 4.3+, then I'll just sit on 4.1.1 for a few months until I can't stand it anymore and just void the warranty anyway.
Thanks again everyone. This whole knox/binary counter thing is not something I dealt with on my CDMA LG or Nexus, so I was totally in the dark about how it all worked. This is also my first GSM phone, so all those intricacies are new to me too. Once I know about manually flashing stock and running towelroot/xposed, I think I'll be in good shape.
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
audit13 said:
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
Click to expand...
Click to collapse
Excellent. If I did flash stock, i would just use ODIN, then factory reset to wipe the caches. And that's good to know about the KK rom, as I would probably update straight to 4.4 if at all (I've read a lot of bad things about 4.3 on the S3), but not if it means I cannot root safely and cleanly.
I'll check out the custom roms for 4.1.1. I know that flashing the rom and/or a custom recovery will trip the binary counter, but I can just use triangle away to clean that up. Do you know if there is a list of custom 4.1.1/4.1.2 roms somewhere, or do I need to scour the older threads here?
Thank you very much audit13 (thanks to StoneyJSG and pre4speed as well). You have been immensely helpful and really brought me up to speed on everything surrounding S3 customization. Needless to say it's way more complicated than what I've dealt with from LG and Google/Asus. (I mean, i could root my nexus with a single click using Wugfresh's toolkit)
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
audit13 said:
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
Click to expand...
Click to collapse
Oh, so what other way can you flash a stock rom, if not through ODIN or a custom recovery? Regardless, it seems as though I really should not dive into 4.3+ until I'm ready to concede that my warranty is over. There are just too many potential pitfalls and headaches.
On the lighter side, I've found a few 4.1.2 based custom roms that have some promise. I'm going to post them here in case anyone has opinions on them, or if someone else in my situation sees this thread and wants to go custom 4.1 too:
Hyperdrive RLS16
http://forum.xda-developers.com/showthread.php?t=2176793
Slim Bean-d2
http://forum.xda-developers.com/showthread.php?t=1865262
Jedi Academy
http://www.teamandroid.com/2013/12/...oid-412-jedi-academy-jelly-bean-custom-rom/2/
Jelly ‘Beans’
http://www.teamandroid.com/2013/04/...ndroid-412-att-galaxy-s3-sgh-i747-custom-rom/
I was also torn when I got my s3 that was running 4.1.2. I downgraded to 4.1.1, sim unlocked the phone, used it on stock 4.1.2 for about a week to make sure everything was working, hardware wise, upgraded to stock 4.4.2, installed a custom recovery and a custom ROM. I wasn't too concerned about the warranty since I got the phone as a free upgrade and had no intention of using the s3 as my daily phone. I kept it as a backup until my niece needed and phone and then it went to her. It's been over a year and there are still no problems with the phone.
Hello,
I tried to flash custom ROM, but something somewhere went terribly wrong.
I did read some guides on flashing before attempting this and did make some precutions as well.
Such as creating ROM backup with CWM and copying efs folder with Root browser.
Unfortunately I didn't succeed with the flash. Now the phone can turn on, but there is no network service, and IMEI number is missing.
I tried to go back to my original ROM, but that didn't fix the problem.
I tried to gather as much information as possible, but it seems that information on this device is a bit outdated. For example, I wanted to try to flash back to stock ROM with odin, but most links with stock ROM are down. The one that isn't down only provides .7z file instead of md5,tar file that is required by odin.
The device works, just can't connect to mobile network.
Is there something I could do?
Before flashing anything else, what baseband and bootloader is on the phone? The imei may be missing because the ROM is too new for the phone's current bootloader/modem combination.
Bootloader version is T999UVDLJA
Baseband version is UKNKOWN
I have finally found stock ROM in tar.md5 format, which is compatible with ODIN.
The t999 is the aws version of the s3 according to this: http://www.gsmarena.com/samsung_galaxy_s_iii_t999-4804.php
This forum is for the i747 and i747m (the AT&T and Rogers) version of the s3.
If the t999 is like the i747, do not flash any ROM via Odin that tries to downgrade the bootloader as this may brick the phone.
This makes just even more complicated.
When I go to settings -> About device, under model number I have SGH-I747.
When I double check this with Samsung phone info app, under model number I have SGH-I747.
In the same Samsung phone info app under PDA version I have I747UCDLK3 and under CSC version I have I747ATTDLK3
t999 only appears when I enter Download mode via volume down + home button + power button.
What does the label under the battery say about the model #?
Label under the phone is SGHT999.
Wow, this phone is weird...
I read on the forums that there is chance to restore firmware of the phone with KIES, so I tried that. At first I entered SGH-I747 model number and serial number of the phone and it failed. But after that I entered SGH-T999 model number and serial number of the phone and KIES started to update the phone.
At the moment I have android V4.3
Bootloader T999UVUENC2
Baseband T999UVUENC2
PDA version T999UVUENC2
CSC version T999MBENC2
Phone seems to be unrooted, IMEI number is visible, I can call again, but the phone's factory mode is on.
It seems that I had a SGH-T999 which somehow was tricked int thinking that it is SGH-I747.
At the moment I would just like to have a stock ROM for this phone without all the T-Mobile apps, would that be possible?
Does everything see to work?
The easiest way to root and remove apps would be to flash a custom recovery, install supersu and titanium backup. Then use titanium backup to remove the apps.
Yes, at the moment everything works.
I can call, receive sms, use wi-fi as well as mobile data.
The only problem is that phone has factory mode on Yellow text on black background. And it is heavily loaded with T-Mobile applications.
So I guess this phone is T999 then, right? How could it be that everywhere it had I747?
By custom recovery you mean custom ROM?
You need a custom recovery such as TWRP: http://forum.xda-developers.com/showthread.php?t=1809313
Download the tar version that can be flashed via Odin.
Download supersu and copy it to the phone. Flash recovery, boot directly into recovery without letting the phone boot the ROM, flash supersu, reboot. Install Titanium Backup from the Play store, remove the apps.
Thank you for sticking with me in this thread!
Could you please explain a little bit more what is TWRP? From the link provided I understand that is is a application that helps with custom rom flashing and backing up roms?
Shouldn't I do this at first - http://forum.xda-developers.com/showthread.php?t=1771687
Boot into download mode. Do you see anything about warranty bit 1? If you do, that means you have already tripped the counter.
Root is not required to flash a custom recovery.
If you are only interested in root, follow the other thread. If you want to be able to flash custom ROMs and backup the rom, you need a custom recovery which will definitely trip the counter.
Do you have any warranty left on the phone?
Yes, there is 1 next to warranty bit. What does it mean for me that I have tripped the counter?
At the moment I would just like to get rid of factory mode and remove those unwanted T-mobile APPS. I think I will be done with Flashing for quite some time
I don't have any warranty on the phone, It has been in the family for quite some time.
It would be 0 if the counter wasn't tripped.
To bring it right back to stock, you could flash one of the prerooted ROMs from the other thread. Just make sure you are flashing a rom that has the same bootloader that is currently on your phone. Hopefully, the stock rom will remove the factory mode.
I understand that the counter is only important if you need warranty, yes?
I actually just found a way how to remove the factory so that is one more thing less to worry about
And I rooted the phone with odin using the link few posts back.
Now for the final question, I understand that this rom is something along the lines that I'm looking for? http://forum.xda-developers.com/showthread.php?t=2501303
The ROM looks nice as long as you are running the correct bootloader and modem.
Installing a custom ROM only requires a custom recovery. There is no need to root or remove apps from the existing ROM since you are going to wipe the existing ROM before installing the new ROM.
I read through the thread and I understand that I have to flash T999UVUEMJC modem before flashing the ROM.
I'm not sure where the bootlaoder of this rom is mentioned. Only place where boot loader of my device T999UVUENC2 is mentioned is in change log "-Rebased to T999UVUENC2".
The official T-mobile firmware is here: http://www.sammobile.com/firmwares/database/SGH-T999/
Notice the last few letters in the firmware PDA?
Based on your post on the first page (post #7) you are on the NC2 bootloader and modem, which are compatible with the rom you are wanting to flash. (See the second line under the Disclaimer banner.) NC2 is the most current firmware for the T999 listed on the page Audit linked to.
(one explanation for how your device was reporting i747)
Is it possible that someone else flashed the i747 rom to this phone? Either someone doing you a favor or a previous owner? I747 roms will work on the T999, I frequently see people commenting on doing so successfully. You just need to have comparable bootloaders and modems. That and if the rom dev didn't accommodate the device in the updater-script the user must edit the script himself. In the unofficial cm12.1 thread for the i747 people were doing this often.
So the bootloader version is always the same as the modem version?
I understand that in my case I don't need to flash T999UVUEMJC modem, since the one I have at the moment is newer?
That is definitely possible, although, how it came to be I will never know, since I personally didn't buy the phone. But this would explain a lot.
Could you please take a look at this thread, I created steps I plan to do in order to flash the above mentioned ROM. It would really put my heart at ease http://forum.xda-developers.com/galaxy-s3-t-mobile/help/one-rom-flashes-please-double-check-t3111443