Related
I'm a bit of a noob, so apologies if this is in the wrong section. I've had a very difficult time finding threads that focus on those who have (stupidly!) applied the OTA 4.3 jellybean update, and what they can do to network unlock the phone. So here goes:
Samsung Galaxy SIII
SGH-T999
Android Version 4.3
Baseband Version T999UVUEMJC
Stock build. No root.
The closest step-by-step I've come across:
Remove T-Mobile SIM. Replace with ATT SIM. Reboot phone.
*#197328640# which successfully puts me into service mode.
This brings up the following menu:
MAIN MENU
[1]UMTS
[2]CDMA
[3]LTE
[4]SIM
From there its
[1]UMTS
[1] DEBUG SCREEN
[8]PHONE CONTROL
[6]NETWORK UNLOCK
[3]PERSO SHA256 OFF ...
Now, that's as far as I can get. The guide then says to go back to [6] and there should be an option, [4] NV INITIALIZZ.
This option is not there for me. (Note: at this point the PERSO SHA256 status is indeed set to SHA256_ENABLE_FLAG [0]).
Another guide suggested BACKing to the MAIN MENU and selecting option [5] run EFS SYNC() after selecting [3]PERSO SHA256 OFF.
I have done this and the screen reads: SYNC success. please reboot.
I do so, heart aflutter... only to be met with a SIM unlock PIN code entry screen.
Unlock fail.
Other threads have suggested downgrading to 4.1.1 in order for this to work and the necessary options be made available. Most of what I have read has said that attempts to downgrade from OTA 4.3 (with big brother KNOX) will result in a hard brick.
So, if you've made it this far... Has anyone figured out how to SIM unlock this particular phone running OTA 4.3 without rooting/downgrading?
If there is a more suitable thread discussing SIII's that are running 4.3 please direct me there.
Many thanks!
You could try and flash a 4.1.1 Modem. After that, try the above process.
Note - In that process, you are required to be super patient at each step.
Perseus71 said:
You could try and flash a 4.1.1 Modem. After that, try the above process.
Note - In that process, you are required to be super patient at each step.
Click to expand...
Click to collapse
Appreciate the response.
Yes, most of what I have come across has indicated that I would need to get 4.1.1 by hook or by crook in order to network unlock the phone, having upgraded to 4.3.
I have some experience fiddling with such things, but many posts have also indicated that, with the new KNOX package in tow, backing down from 4.3 will hard brick this device. I am hoping that, with access to Service Mode, someone will discover a way to network unlock without root/flashing.
Thanks again!
Are you Rooted ? If so flashing the LJC modem from Doc's thread won't brick your device.
Perseus71 said:
Are you Rooted ? If so flashing the LJC modem from Doc's thread won't brick your device.
Click to expand...
Click to collapse
The phone is not currently rooted, no. Most rooting instructions I've seen are for 4.1.1 or 4.1.2. My guess is I'm going to have to root to unlock...
Could you direct me to instructions for rooting OTA 4.3?
Again, many thanks for taking the time to help.
etrash310 said:
The phone is not currently rooted, no. Most rooting instructions I've seen are for 4.1.1 or 4.1.2. My guess is I'm going to have to root to unlock...
Could you direct me to instructions for rooting OTA 4.3?
Again, many thanks for taking the time to help.
Click to expand...
Click to collapse
Follow these. Effectively Flash Custom Rom using ODIN then flash SuperUser Zip.
Perseus71 said:
Follow these. Effectively Flash Custom Rom using ODIN then flash SuperUser Zip.
Click to expand...
Click to collapse
Awesome. I will try this tonight.
etrash310 said:
Awesome. I will try this tonight.
Click to expand...
Click to collapse
Well, no luck. Followed all the directions I could (provided by some awesome contributors including Doc) including:
1)Rooting using the aforementioned method and installing 4.3 with SU and no KNOX. Then just flashing stock modem 4.1.1 UVDLJC, in order to reveal the [4] NV INITIALIZZ option that is not present in Servicemode on jellybean 4.3 firmware.
--- This resulted in very slowed down system with no WiFi capability and no startup or shutdown sounds. Logging into Servicemode just resulted in a blank screen that said Servicemode.
--- Ultimately had to emergency restore firmware via KIES. (Thanks to reading a post by Doc on another thread). This got me up and running again.
2) Rooting using aforementioned method. And searching for stock 4.1.1 firmware in order to downgrade...
--- This has proven to be impossible. I can not find stock 4.1.1 anywhere. All links that have turned up have either been dead hotfile.com links or corrupted .zip files.
--- Additionally, I have been informed that once you upgrade to 4.3 OTA it is IMPOSSIBLE to flash an earlier firmware using ODIN. (Is is possible using CWM perhaps?)
In the end, it appears that the jellybean 4.3 OTA update currently has the community stumped as to how to unlock the SGH-T999 for use on another network with your only option to either convince T-Mobile to give you an unlock code or ordering one online. (And I've read of too many folks getting bogus codes ordering online...)
Still having fun trying, and its very cool to see all the hard work and info that folks like Doc are compiling on here. Maybe somebody is on the way to cracking this nut!!!
etrash310 said:
In the end, it appears that the jellybean 4.3 OTA update currently has the community stumped as to how to unlock the SGH-T999 for use on another network with your only option to either convince T-Mobile to give you an unlock code or ordering one online. (And I've read of too many folks getting bogus codes ordering online...)
Click to expand...
Click to collapse
So after all that, what is your current Rom and Firmware ? Can you try Root66 of 4.2 Rom ? Doc has Re-Hosted with mirrors.
I followed cLogic's guide that you linked to above and am running 4.3 rooted w/o Knox garbage.
Ended up getting phone network unlocked at a local hole in the wall phone shoppe. Figured it was worth a couple extra bucks to have it unlocked face to face in case code didn't work rather than fish out a reputable online source on my own.
Will be curious to compare its power usage to stock 4.3. Phone is working well, although it seems I will have to play with the APN settings as I am unable to send MMS messages... hmmm. Any advice off the top of your head?
I'd given root66 a try and also gave Doc's reposts another shot, but no dice.
So the sum of my endeavors are as follows:
1) If you want to network unlock your galaxy s3 on your own, DO NOT upgrade to jellybean 4.3 OTA until you do. It does not seem anyone has figured a way to ala ServiceMode in 4.1.1 yet.
2) If you have upgraded to 4.3 OTA you can use cLogic's guide linked to above to root your phone sans Knox.
3) If you have already upgraded to 4.3 OTA and want your phone network unlocked, you will have to pay to have it factory unlocked.
4) XDA is the bomb.
UPDATE:
Looks like the MMS messages I was trying to send finally went through... it just took an inordinately long time for them to do so.. not sure why yet.
Of dubious help to the OP, who had his phone commercially unlocked, but for others reading this thread or the OP's curiosity.. the 4.3 update has caused all kinds of grief. Amongst various bugs and battery drain issues, 4.3 has changed dialer codes or shuffled menus around. I can confirm the same results as the OP up to the point where he found that the initialize NV menu missing.
To progress further, I found that I needed:
An active SIM from a different carrier, with said SIM needing to be the phone throughout. This is in contrast to the previous method that worked without a SIM in the phone during the unlock procedure. I successfully unlocked a Note 2 with 4.3 using the steps in this techbeasts.com post.
And was successful with a 4.3 S4 using a slight variation (no NV initialize menu!.. back.. key input.. 1.. back). Both phones were M (Canadian) models.
Reading between the lines of various reports in addition to first hand experience implies that there may be several different carrier specific dodges being employed here. Playing musical chairs with the missing menu items that now have different dialer codes, are now found on hidden sub menus (key input = 1) or in back up files.
The commercial unlock guys are using proprietary tools such as Samsung tool v 16.8. Which usually seem to be database based factory unlocks fetched (or calculated?) from their servers.
.
since this worked on a note2, would it work on a sgs3 t999 that is already on 4.3?
fffft said:
Of dubious help to the OP, who had his phone commercially unlocked, but for others reading this thread or the OP's curiosity.. the 4.3 update has caused all kinds of grief. Amongst various bugs and battery drain issues, 4.3 has changed dialer codes or shuffled menus around. I can confirm the same results as the OP up to the point where he found that the initialize NV menu missing.
To progress further, I found that I needed:
An active SIM from a different carrier, with said SIM needing to be the phone throughout. This is in contrast to the previous method that worked without a SIM in the phone during the unlock procedure. I successfully unlocked a Note 2 with 4.3 using the steps in this techbeasts.com post.
And was successful with a 4.3 S4 using a slight variation (no NV initialize menu!.. back.. key input.. 1.. back). Both phones were M (Canadian) models.
Reading between the lines of various reports in addition to first hand experience implies that there may be several different carrier specific dodges being employed here. Playing musical chairs with the missing menu items that now have different dialer codes, are now found on hidden sub menus (key input = 1) or in back up files.
The commercial unlock guys are using proprietary tools such as Samsung tool v 16.8. Which usually seem to be database based factory unlocks fetched (or calculated?) from their servers.
.
Click to expand...
Click to collapse
etrash310 said:
Well, no luck. Followed all the directions I could (provided by some awesome contributors including Doc) including:
1)Rooting using the aforementioned method and installing 4.3 with SU and no KNOX. Then just flashing stock modem 4.1.1 UVDLJC, in order to reveal the [4] NV INITIALIZZ option that is not present in Servicemode on jellybean 4.3 firmware.
--- This resulted in very slowed down system with no WiFi capability and no startup or shutdown sounds. Logging into Servicemode just resulted in a blank screen that said Servicemode.
--- Ultimately had to emergency restore firmware via KIES. (Thanks to reading a post by Doc on another thread). This got me up and running again.
2) Rooting using aforementioned method. And searching for stock 4.1.1 firmware in order to downgrade...
--- This has proven to be impossible. I can not find stock 4.1.1 anywhere. All links that have turned up have either been dead hotfile.com links or corrupted .zip files.
--- Additionally, I have been informed that once you upgrade to 4.3 OTA it is IMPOSSIBLE to flash an earlier firmware using ODIN. (Is is possible using CWM perhaps?)
In the end, it appears that the jellybean 4.3 OTA update currently has the community stumped as to how to unlock the SGH-T999 for use on another network with your only option to either convince T-Mobile to give you an unlock code or ordering one online. (And I've read of too many folks getting bogus codes ordering online...)
Still having fun trying, and its very cool to see all the hard work and info that folks like Doc are compiling on here. Maybe somebody is on the way to cracking this nut!!!
Click to expand...
Click to collapse
Well try this link .... http://forum.xda-developers.com/showthread.php?t=1949687
well i dont know if it will work for me because my t999 is running cyanogenmod 12.1
The phone must be running stock 4.1.1 in order to sim unlock using the free method. Once the phone is on a 4.3 or newer bootloader, sim unlocking must be done using a code specific to the phone's imei. In order to enter the unlock code, the phone must be running a stock ROM or possibly a custom ROM based on a tw kernel.
audit13 said:
The phone must be running stock 4.1.1 in order to sim unlock using the free method. Once the phone is on a 4.3 or newer bootloader, sim unlocking must be done using a code specific to the phone's imei. In order to enter the unlock code, the phone must be running a stock ROM or possibly a custom ROM based on a tw kernel.
Click to expand...
Click to collapse
So, I previously rooted my s3. It is locked to tmobile. Then I unrooted and tried to unlock it but of course after 4.3 update (LUVUBOH1 Big mistake I see! I tried to flash a different 4.3 stock baseband just to make sure I flashed stock rom but odin failed. I kept trying and even updated odin, but no dice. Any ideas??
Do you have an unlock code? If not, you'll have to buy an unlock code and enter the code while running a stock ROM.
audit13 said:
Do you have an unlock code? If not, you'll have to buy an unlock code and enter the code while running a stock ROM.
Click to expand...
Click to collapse
Yes, I did purchase an unlock code. I'm going to try a different sim. I THINK I'm running stock rom 4.3 LUVUBOH1.
When you insert a non T-Mobile sim, you're not prompted to enter a network unlock code?
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.
GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.
Bummer. I'll leave it as is then. Thank you for all the help.
Hey guys! This might sound noobish, but i really never flashed, rooted, or anything on a droid/etc before. So atm I bought a galaxy s4 for my dad, and tried unlocking this stupid phone, but unlocking thru the dialer didnt work(couldnt even get *#27663368378# to work, when using *#0011#, still couldnt do anything.) All i know about it, is that it recognizes the European sim card, but the simple mobile(usa) sim card doesnt recognize, can't make calls, etc, as when you try to make a call it says "cant register to network" or w.e. So i was wondering what should I do? Do i need to flash the modem? rom? Root it? I want it to be able to work in global, in usa and euro.
On another note, I got my other phone that's on ver 4.2.2. Should i try upgrading my modem/baseband from mdl to nb4? Anything new with the new modem or anything i should update? Since i cant update OTA anymore on my 4.2.2. lol. Any suggestions would be awesome Tell me from your point of you, is it better to stay at 4.2.2? or just get the 4.4.2, and should i root my phone? Any vernabilities/security problems if done?
I found this: http://forum.xda-developers.com/showthread.php?t=2780006
Samsung Galaxy S4 M919 T-mobile
ROM: M919UVUFNB4
4.4.2 kitkat
Den Den said:
Hey guys! This might sound noobish, but i really never flashed, rooted, or anything on a droid/etc before. So atm I bought a galaxy s4 for my dad, and tried unlocking this stupid phone, but unlocking thru the dialer didnt work(couldnt even get *#27663368378# to work, when using *#0011#, still couldnt do anything.) All i know about it, is that it recognizes the European sim card, but the simple mobile(usa) sim card doesnt recognize, can't make calls, etc, as when you try to make a call it says "cant register to network" or w.e. So i was wondering what should I do? Do i need to flash the modem? rom? Root it? I want it to be able to work in global, in usa and euro.
On another note, I got my other phone that's on ver 4.2.2. Should i try upgrading my modem/baseband from mdl to nb4? Anything new with the new modem or anything i should update? Since i cant update OTA anymore on my 4.2.2. lol. Any suggestions would be awesome Tell me from your point of you, is it better to stay at 4.2.2? or just get the 4.4.2, and should i root my phone? Any vernabilities/security problems if done?
I found this: http://forum.xda-developers.com/showthread.php?t=2780006
Samsung Galaxy S4 M919 T-mobile
ROM: M919UVUFNB4
4.4.2 kitkat
Click to expand...
Click to collapse
To unlock your dad's phone the guide you linked to should do what you need done.
As far as your phone still on MDL, you should be able to use the old method through the service menu to unlock if that's what you wanted to do. You can update your modem/baseband if you desire, although if you're staying on stock 4.2.2 TouchWiz there is really no need to. It's only when you flash ROMs based on 4.3 and above that you run into issues using the MDL modem/baseband.
To add to lordcheeto's post, there's a difference between MDL bootloader and the MDL modem. When the S4 was released with Android 4.2 it had an unlocked bootloader (MDL), but with Android 4.3 and 4.4 Samsung included new security software called Knox. Knox doesn't prevent rooting, but if you flash a custom recovery such as CWMR, TWRP, or Philz Touch then a security flag will be irreversibly tripped which voids your warranty. Because this Knox software is tied into the bootloader, developers found a way around it by extracting the modems from 4.3 (MK2) and 4.4 (NB4) firmwares which allows us to keep our MDL bootloader and still use 4.2, 4.3, and 4.4 roms. The advantages are that we keep our warranty and we're able to use any 4.2+ rom. We can downgrade and upgrade easily while Knox phones can't.
lordcheeto03 said:
To unlock your dad's phone the guide you linked to should do what you need done.
As far as your phone still on MDL, you should be able to use the old method through the service menu to unlock if that's what you wanted to do. You can update your modem/baseband if you desire, although if you're staying on stock 4.2.2 TouchWiz there is really no need to. It's only when you flash ROMs based on 4.3 and above that you run into issues using the MDL modem/baseband.
Click to expand...
Click to collapse
Should i keep the 4.4.2 kitkat thats not working with my usa sim card atm? Or should i flash it to 4.2.2. ADL? If having 4.2.2 is better doing that guide i put link to above, then give me a good tut on doing it, need to do it today xD THanks in Advance!
HampTheToker said:
To add to lordcheeto's post, there's a difference between MDL bootloader and the MDL modem. When the S4 was released with Android 4.2 it had an unlocked bootloader (MDL), but with Android 4.3 and 4.4 Samsung included new security software called Knox. Knox doesn't prevent rooting, but if you flash a custom recovery such as CWMR, TWRP, or Philz Touch then a security flag will be irreversibly tripped which voids your warranty. Because this Knox software is tied into the bootloader, developers found a way around it by extracting the modems from 4.3 (MK2) and 4.4 (NB4) firmwares which allows us to keep our MDL bootloader and still use 4.2, 4.3, and 4.4 roms. The advantages are that we keep our warranty and we're able to use any 4.2+ rom. We can downgrade and upgrade easily while Knox phones can't.
Click to expand...
Click to collapse
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Den Den said:
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Click to expand...
Click to collapse
I thought the answers given were pretty clear... I'm actually confused about what phone you're asking about, and if there are, in fact, 2 different phones in question... My answer will be a bit lengthy, but I hope that you can put 1 and 2 together and apply the information I am about to type to your particular situation: Also, I'm not trying to be a ****, just concise.
In reference to the S4 that is on 4.4.2 (NB4) firmware: The unlock method which you posted SHOULD enable the device to use different SIM cards and function in "euro" and "usa." That includes making calls and using "date" (data?) as you mentioned. As far as your question on reverting that particular device: There is no way whatsoever to downgrade the firmware on a device running either stock 4.3 (MK2) or stock 4.4.2 (NB4) obtained by flashing via Odin, Kies, or OTA; so that idea can be forgotten about. The unlock method, from what I gather, simply reverts the modem and allows you to use the old unlock method. then returns the modem to NB4. It does not touch the firmware, bootloader, or anything other than the modem/baseband.
For whichever device this applies to: there should be no need to root either to accomplish either goal. If you wish to root, then I can point you in the right direction; otherwise, if you haven't needed it so far and don't foresee needing it in the future, I say don't worry about it.
As for the device running 4.2.2: if you have had no troubles with reception, then there is no need to update your modem/baseband. There are really only 2 times that updating your modem would come in handy. 1: If you are having reception problems, or 2: If you plan on keeping your bootloader at MDL AND using custom ROMs 4.3 and above. The benefit of this scenario is that keeping your bootloader on MDL means that your device does not have the KNOX-implemented bootloader and can easily be reverted to a completely stock state for warranty purposes yet you still get to have the most up-to-date version of Android. If neither of those conditions apply to you, then there is really no real need to update your modem.
Den Den said:
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Click to expand...
Click to collapse
The guide you posted should work just fine. Just follow the instructions.
Also, I left out one of the most important parts of having the modems extracted from the 4.3 and 4.4 firmwares. The reason for extracting the modems is so that we can flash them separately from the official firmware which would upgrade us to a Knox bootloader. Using the 4.2 modem with 4.3 and 4.4 roms causes data and sound issues that make the phone pretty much unusable. The same goes for using the 4.3 modem with a 4.4 rom. With the extracted modems we can flash them separately for whatever Android version we're using and have full functionality and retain the MDL bootloader and all it's perks.
If you use a 4.2 rom, you'll need to make sure to flash the MDL modem with it.
For 4.3 roms, you'll need to be on MK2 modem.
4.4 roms require NB4 modem.
As long as you don't update to official 4.3 or 4.4, you'll be able to use any version rom you want according to your preference. Personally, I use 4.4 roms, but it's nice to have the option to go back to 4.2 if I want to. Once you SIM unlock, it should stick between all versions. You should be able to flash any rom that you want without having to worry about going through that process again.
lordcheeto03 said:
I thought the answers given were pretty clear... I'm actually confused about what phone you're asking about, and if there are, in fact, 2 different phones in question... My answer will be a bit lengthy, but I hope that you can put 1 and 2 together and apply the information I am about to type to your particular situation: Also, I'm not trying to be a ****, just concise.
In reference to the S4 that is on 4.4.2 (NB4) firmware: The unlock method which you posted SHOULD enable the device to use different SIM cards and function in "euro" and "usa." That includes making calls and using "date" (data?) as you mentioned. As far as your question on reverting that particular device: There is no way whatsoever to downgrade the firmware on a device running either stock 4.3 (MK2) or stock 4.4.2 (NB4) obtained by flashing via Odin, Kies, or OTA; so that idea can be forgotten about. The unlock method, from what I gather, simply reverts the modem and allows you to use the old unlock method. then returns the modem to NB4. It does not touch the firmware, bootloader, or anything other than the modem/baseband.
For whichever device this applies to: there should be no need to root either to accomplish either goal. If you wish to root, then I can point you in the right direction; otherwise, if you haven't needed it so far and don't foresee needing it in the future, I say don't worry about it.
As for the device running 4.2.2: if you have had no troubles with reception, then there is no need to update your modem/baseband. There are really only 2 times that updating your modem would come in handy. 1: If you are having reception problems, or 2: If you plan on keeping your bootloader at MDL AND using custom ROMs 4.3 and above. The benefit of this scenario is that keeping your bootloader on MDL means that your device does not have the KNOX-implemented bootloader and can easily be reverted to a completely stock state for warranty purposes yet you still get to have the most up-to-date version of Android. If neither of those conditions apply to you, then there is really no real need to update your modem.
Click to expand...
Click to collapse
That Makes sense...just trying to grasp info. on everything so it's more clearer ;p and thanks for correcting me, yea it was data lol.
HampTheToker said:
The guide you posted should work just fine. Just follow the instructions.
Also, I left out one of the most important parts of having the modems extracted from the 4.3 and 4.4 firmwares. The reason for extracting the modems is so that we can flash them separately from the official firmware which would upgrade us to a Knox bootloader. Using the 4.2 modem with 4.3 and 4.4 roms causes data and sound issues that make the phone pretty much unusable. The same goes for using the 4.3 modem with a 4.4 rom. With the extracted modems we can flash them separately for whatever Android version we're using and have full functionality and retain the MDL bootloader and all it's perks.
If you use a 4.2 rom, you'll need to make sure to flash the MDL modem with it.
For 4.3 roms, you'll need to be on MK2 modem.
4.4 roms require NB4 modem.
As long as you don't update to official 4.3 or 4.4, you'll be able to use any version rom you want according to your preference. Personally, I use 4.4 roms, but it's nice to have the option to go back to 4.2 if I want to. Once you SIM unlock, it should stick between all versions. You should be able to flash any rom that you want without having to worry about going through that process again.
Click to expand...
Click to collapse
So If i was on 4.3, and it updated to 4.4.2 kitkat, means it went to the official update eh? As "lordcheeto03" said that once u go to 4.3 or 4.4.2 you cant go back to 4.2, the menu options and w.e go updated, the "about me" is now yellow, the top border of the phone is grey, etc. The new security is enforcing, I guess I'll try the guide i found, hope i don't do anything stupid or skip a step(usually doesn't happen) but feels kinda weird doing things the first time.
On another note, if a phone bricks or in a loop, etc can it be solved? So i still have hope if something goes wrong xD
edit: The guide i link that i found, it works for all m919 models? Since i got t-mobile, not sure if all models(tmobile, att, etc) have the same modem, wouldnt want to brick cuz of not flashing the correct file, w.e(disregard this, i forgot i posted in the t-mobile section, man sometimes i feel like an idiot because i dont double check xD)
Den Den said:
So If i was on 4.3, and it updated to 4.4.2 kitkat, means it went to the official update eh? As "lordcheeto03" said that once u go to 4.3 or 4.4.2 you cant go back to 4.2, the menu options and w.e go updated, the "about me" is now yellow, the top border of the phone is grey, etc. The new security is enforcing, I guess I'll try the guide i found, hope i don't do anything stupid or skip a step(usually doesn't happen) but feels kinda weird doing things the first time.
On another note, if a phone bricks or in a loop, etc can it be solved? So i still have hope if something goes wrong xD
edit: The guide i link that i found, it works for all m919 models? Since i got t-mobile, not sure if all models(tmobile, att, etc) have the same modem, wouldnt want to brick cuz of not flashing the correct file, w.e(disregard this, i forgot i posted in the t-mobile section, man sometimes i feel like an idiot because i dont double check xD)
Click to expand...
Click to collapse
Once you hit 4.3, you lost your ability to downgrade. You can upgrade, but you can't go back. Rest easy, as long as you can get into download mode, you can recover your device. Bootloop, soft brick, whatever; as long as Power + volume down brings you to download mode everything is still OK. Just read the directions a few times.. get used to the idea of what's going on, double check and make sure you have the right software and files, and jump in. You'll do fine. Even after years of jailbreaking iphones and rooting Droids, I still get nervous whenever I have to fire up Odin; but just remember... many many others (more than have posted in that thread for sure) have done the same thing you're about to do, so as long as you follow the directions you will be fine!
lordcheeto03 said:
Once you hit 4.3, you lost your ability to downgrade. You can upgrade, but you can't go back. Rest easy, as long as you can get into download mode, you can recover your device. Bootloop, soft brick, whatever; as long as Power + volume down brings you to download mode everything is still OK. Just read the directions a few times.. get used to the idea of what's going on, double check and make sure you have the right software and files, and jump in. You'll do fine. Even after years of jailbreaking iphones and rooting Droids, I still get nervous whenever I have to fire up Odin; but just remember... many many others (more than have posted in that thread for sure) have done the same thing you're about to do, so as long as you follow the directions you will be fine!
Click to expand...
Click to collapse
Thanks for the reply, now I'm all fired up and ready to do this I'll post back here when i'm done and see how it went xD
Edit: Can i ask you a favor? Could you get me the "M919UVUFNB4_M919TMBFNB4_TMB.zip" modem file and "M919UVUAMDL_M919TMBAMDL_TMB.zip", i think that's what the tutorial link i posted is asking for. But the files r huge, 1.6gb, etc, would take me 3hrs+ each for each file to download just to extract the modem =/ If that's the only thing i need.
found these links: http://rapidgator.net/file/59487dc515500a0430ddaddc780fa555/TMB-M919UVUFNB4-20140314115123.zip.html
and : http://terafile.co/32d149264215/M919UVUAMDL_M919TMBAMDL_TMB.zip
Not sure if they are safe to use or not, not everything on the net is...plus they r huge files =/
Den Den said:
Thanks for the reply, now I'm all fired up and ready to do this I'll post back here when i'm done and see how it went xD
Edit: Can i ask you a favor? Could you get me the "M919UVUFNB4_M919TMBFNB4_TMB.zip" modem file and "M919UVUAMDL_M919TMBAMDL_TMB.zip", i think that's what the tutorial link i posted is asking for. But the files r huge, 1.6gb, etc, would take me 3hrs+ each for each file to download just to extract the modem =/ If that's the only thing i need.
found these links: http://rapidgator.net/file/59487dc515500a0430ddaddc780fa555/TMB-M919UVUFNB4-20140314115123.zip.html
and : http://terafile.co/32d149264215/M919UVUAMDL_M919TMBAMDL_TMB.zip
Not sure if they are safe to use or not, not everything on the net is...plus they r huge files =/
Click to expand...
Click to collapse
These files include modem.bin that is required... I'm not sure why the OP linked to the entire firmware instead of just those links, but anywho...
The NB4 modem can be found in this thread. It's only ~20MB.
The MDL modem is in this thread. It is ~25MB.
Also, quote me instead of just replying to the thread. I'll respond quicker
lordcheeto03 said:
These files include modem.bin that is required... I'm not sure why the OP linked to the entire firmware instead of just those links, but anywho...
The NB4 modem can be found in this thread. It's only ~20MB.
The MDL modem is in this thread. It is ~25MB.
Also, quote me instead of just replying to the thread. I'll respond quicker
Click to expand...
Click to collapse
Flashed ADL using odin, somehow got the menu to work(couldnt budge for some reason to umts), went thru all the steps, it rebooted, put it back to download mode, and flashed it back to nb4. Put my simplemobile simcard in, still nothing, am I supposed to put a different sim card in like ATT or something for it to work? Confused why it didnt work, yet it still detects the MTC european version simcard(not in service, but it had a pin set on it, so it always asks you to unlock the sim with the sim pin u put on it to view ur files on it, etc). Am i doing something wrong? I could give you more info on the phone...
Edit: Just checked on Swappa.com of my imei and got this =/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nvm, Looks like i think its blocked on Tmobiles network, but i put in the H2O sim and it worked.(under ATT) phew....
I didnt see this on the other thread about sim unlock for the original t-mobile S3 so my apologies if this method has been posted before.
I have tested this on SGH-T999L aka theLTE version of the S3 for T-Mobile. I did this on 4.1.2 and it will more likely not work on 4.3. I havent tested it on T999N (Metro PCS version) but if someone does and it works, let us know
1. Go to https://towelroot.com/ and download towelroot. Install it and run it. Now you are rooted.
2. Install RegionLock Away
http://forum.xda-developers.com/showthread.php?t=2470551
3. Run it and grant root and reboot and now you are unlocked.
Optional step
4. Update through Kies to 4.3 and it will work despite being rooted (Device Status shows "Official" if rooted through towelroot). Update fails if you do it through the settings so this is the only to update besides odin/flashing
I test it an AT&T Straight Talk and everything was working with LTE
Thanks! I had run Region Lock Away to confirm it was safe to try a while back, but was never able to test if it actually SIM unlocked the device. If it worked on 4.1.2, I think there is a good chance it would also work on 4.3. This needs confirmation though.
Also, SIM unlocking is permanent, so it should remain unlocked regardless of how you update or if you flash any custom roms.
It may also be possible to unlock 4.3 this way, I suggested a couple people to try this but they never replied with any feedback so don't know if it worked or not. This method works on the S4 with 4.3 but I think you have to downgrade the modem if I remember correctly, or it may only be needed for 4.4.2. The same might apply here
I am guessing that you need to have a stock based ROM. I attempted it with Carbon ROM and got "Could not locate CSC data!"
Yup, gotta be stock to unlock, whether you are using a dialer code or any other methods.
DocHoliday77 said:
Yup, gotta be stock to unlock, whether you are using a dialer code or any other methods.
Click to expand...
Click to collapse
So, StockMod or S3Rx should work?
Not sure tbh. The dialer has to be unmodified stock. And I'm not certain if one of the system apps like keystring or factoryapp, or one of the others would be needed. Some custom roms debloated these, not sure about those two. (They probably didnt, but I can't say for sure. ) you could try it, but if it doesn't take, try flashing stock with Odin. Root66 should be ok if you do
DocHoliday77 said:
Not sure tbh. The dialer has to be unmodified stock. And I'm not certain if one of the system apps like keystring or factoryapp, or one of the others would be needed. Some custom roms debloated these, not sure about those two. (They probably didnt, but I can't say for sure. ) you could try it, but if it doesn't take, try flashing stock with Odin. Root66 should be ok if you do
Click to expand...
Click to collapse
I'll give it a try just to see if it works and give feedback,
The patch returns with Successful on S3Rx. I will have to wait til I get home to test it with another Sim card to see if it actually works.
DocHoliday77 said:
Thanks! I had run Region Lock Away to confirm it was safe to try a while back, but was never able to test if it actually SIM unlocked the device. If it worked on 4.1.2, I think there is a good chance it would also work on 4.3. This needs confirmation though.
Also, SIM unlocking is permanent, so it should remain unlocked regardless of how you update or if you flash any custom roms.
Click to expand...
Click to collapse
Does not work on 4.3 build NC1.
I get a hold of alot of phones and work at cell phone repair shop so i always try to find ways to unlock them instead of wasting money on unlock codes. On the S4 you have to downgrade the modem and sometimes roms on 4.3/4.4 to unlocked them. So if we can downgrade the modem, i think we can unlock on 4.3.
Sent from my SM-G900T using Tapatalk
Well, it wont brick, but downgrading the modem simply just doesnt work. No signal or anything. That's why the free unlock no longer works on 4.3.
kali323 said:
So if we can downgrade the modem, i think we can unlock on 4.3.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Try it, I know downgrading modem to unlock works with the S4 but don't know about the S3, we haven't found anyone willing to do it, or provide the feedback
edit: well I meant unlocking with regionunlock
kali323 said:
1. Go to https://towelroot.com/ and download towelroot. Install it and run it. Now you are rooted.
2. Install RegionLock Away http://forum.xda-developers.com/showthread.php?t=2470551
3. Run it and grant root and reboot and now you are unlocked.
Click to expand...
Click to collapse
I can confirm it works. Thanx. I just followed your steps and unlocked my cousin's S3 T999 running:
Stock Android 4.1.2
Baseband T999UVDMD5
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.