Develop Bugs

[q] 4.3 jellybean ota questions

I've got a Galaxy S3 I747 it is currently running 4.1.1, I747UCDLK3 Baseband. I'm not exactly a noob when it comes to flashing and rooting, I know my way around CWM and Odin pretty well. But I have a few questions on this 4.3 OTA. (I am a forum noob)
-Will I still be able to root? (I heard CF works for it)
-Can I install CWM? (Is the Bootloader locked??)
-Will I be be able to I flash other roms than the 4.3 TW like CM11Snapshot? (Is the bootloader locked?)
-What the h*ll is knox and why should I be worried?
-What is with the boot loader downgrading thing? (Have to do with locked bootloader??)
I AM NOT AT ALL WORRIED ABOUT A FLASH COUNTER OR VOIDING A WARRANTY I AM NOT ON A CONTRACT . I JUST DO NO WANT TO HARD BRICK MY PHONE.

If you take the OTA 4.3 update, it will install Knox and the 4.3 bootloader.
The 4.3 bootloader cannot be downgraded and attempts to do so will probably brick the phone.
You can root the stock 4.3 ROM with auto root but Knox may interfere with the process of cause issues after the fact.
You can still install CWM. I rrefer Philz Touch which is CWM-based.over TWRP.

So can I still flash roms?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Yes, you can flash ROMs. Is your phone unlocked? Since you're on 4.1.1 stock, you can unlock it for free.
Personally, I avoided the 4.3 update because it installs knox and the 4.3 bootloader which can cause problems when using Odin to get back to stock.
I have a Canadian version of the s3 and I'm able to run KK ROMs with a stock 4.1.2 bootloader.

audit13 said:
Yes, you can flash ROMs. Is your phone unlocked? Since you're on 4.1.1 stock, you can unlock it for free.
Personally, I avoided the 4.3 update because it installs knox and the 4.3 bootloader which can cause problems when using Odin to get back to stock.
I have a Canadian version of the s3 and I'm able to run KK ROMs with a stock 4.1.2 bootloader.
Click to expand...
Click to collapse
Unlocked as in Bootloader? Yeah I've been able to flash roms via CWM and Odin on 4.1.1 and as in Carrier unlocked? Yes I use Straight Talk on this ATT S3
If I got the 4.3OTA I wouldn't need Odin to go back stock if I flashed a ROM would I? I could just make a back up via CWM then restore later if I wanted right rather than using ODIN?
See I can't use KK roms because I have the 4.1.1 BL so is there a way I can upgrade my boot loader to the 4.1.2 version??
Would I lose my carrier unlock if I upgraded to 4.3 or if I upgrade my bootloader??

I suggest downloading a ROM you want to try, then unzip the ROM and look at the updater script to see which bootloaders are supported. The updater-script file is located in \META-INF\com\google\android\updater-script. You can use a text editor to open the updater-script file.
The first few lines will list the bootloaders that are supported. I run Validus which is a KK ROM using a stock 4.1.2 i747m bootloader.

Do you know about this > "If I got the 4.3OTA I wouldn't need Odin to go back stock if I flashed a ROM would I? I could just make a back up via CWM then restore later if I wanted right rather than using ODIN?"
Also couldn't I just upgrade my Bootloader and Modem from here?
http://forum.xda-developers.com/showthread.php?t=2321310
http://forum.xda-developers.com/showthread.php?t=1831898
I feel like if I upgrade my boot loader then I won't have to worry about restrictions.
Would I lose my carrier unlock if I upgraded to 4.3 or if I upgrade just my bootloader??

I ended up flashing the MG2 Modem and Bootloader, I'm good now, also if I want 4.3 I saw loserskater has a leak version that will be good and wont not let me downgrade my bootloader.

[Q] Downgrading CM11 to stock 4.3 on i747M

I know there are a few threads regarding this issue but I can't seem to find a definitive answer.
I am currently running stock 4.3 jellybean (rooted). My phone hasn't received the 4.4 KitKat update yet, so I wanted to install CM11 in order to get KitKat on my s3. However, I heard CM11 can be buggy on the s3, so in case things go south, I want to be able to revert back to the stock 4.3 rom. Some people have said that you can easily flash the stock ROM via ODIN. However, others said that downgrading from 4.4.2 to 4.3 will hard brick the device since installing CM11 updates the boot loader. So downgrading to 4.3 stock with a 4.4.2 boot loader will cause a hard brick according to other threads I've seen. My question is, how can I downgrade from CM11 to stock 4.3 safely without bricking? Thanks in advance.

If you are sure you are using a Canadian version of the i747m, you can flash back to stock in Odin using a stock 4.3 ROM for the phone's original carrier (Bell, Rogers, Telus).

audit13 said:
If you are sure you are using a Canadian version of the i747m, you can flash back to stock in Odin using a stock 4.3 ROM for the phone's original carrier (Bell, Rogers, Telus).
Click to expand...
Click to collapse
Yes I got the phone from Rogers, it's most definitely i747M. But do I have to worry about any issues with the bootloader? I'm assuming installing CM11 will install the 4.4.2 bootloader, so if I choose to downgrade to the stock 4.3 rom, will it cause any issues seeing as I'm running a 4.3 rom with a 4.4.2 bootloader? I just want to make sure because I heard it can cause some serious problems if the bootloader is newer than the rom.

Mzrz said:
Yes I got the phone from Rogers, it's most definitely i747M. But do I have to worry about any issues with the bootloader? I'm assuming installing CM11 will install the 4.4.2 bootloader, so if I choose to downgrade to the stock 4.3 rom, will it cause any issues seeing as I'm running a 4.3 rom with a 4.4.2 bootloader? I just want to make sure because I heard it can cause some serious problems if the bootloader is newer than the rom.
Click to expand...
Click to collapse
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.

audit13 said:
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
Click to expand...
Click to collapse
Okay, I was just making sure because I know OTA updates can change the bootloader, so I just wanted to make sure the custom roms don't do that. As for the custom recovery, are you recommending Philz Touch over CWM and TWRP? Do you know which custom recovery is installed from the CM installer?

audit13 said:
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
Click to expand...
Click to collapse
Oh and one more question, my phone was originally carrier locked to Rogers and unrooted on 4.3 jelly bean. I brought it in to a cell store for them to carrier unlock it for me, but they used a rooting method to unlock it (because SuperSU was installed on it when I brought it back). They didn't unlock it with a code, so I'm guessing they used something like Samsung Tool or z3x shell. If I install CM11, will I lose the unlock, considering it's more of a "soft unlock", or is the unlock permanent regardless of how many roms I flash? Thanks for your help!

Mzrz said:
Okay, I was just making sure because I know OTA updates can change the bootloader, so I just wanted to make sure the custom roms don't do that. As for the custom recovery, are you recommending Philz Touch over CWM and TWRP? Do you know which custom recovery is installed from the CM installer?
Click to expand...
Click to collapse
Philz is based on the latest release of CWM and I prefer CWM over TWRP because I had problems flashing ROMs. Once I switched to Philz/CWM, no more problems.
Mzrz said:
Oh and one more question, my phone was originally carrier locked to Rogers and unrooted on 4.3 jelly bean. I brought it in to a cell store for them to carrier unlock it for me, but they used a rooting method to unlock it (because SuperSU was installed on it when I brought it back). They didn't unlock it with a code, so I'm guessing they used something like Samsung Tool or z3x shell. If I install CM11, will I lose the unlock, considering it's more of a "soft unlock", or is the unlock permanent regardless of how many roms I flash? Thanks for your help!
Click to expand...
Click to collapse
The unlock should be permanent. I unlocked it using the free method when on 4.1.1 and no ROM has ever caused it to re-lock. Reflashing a completely stock ROM, including the bootloader, did not relock the phone.
Please remember that flashing and changing ROMs will always carry a risk of soft bricking or hard bricking your phone. Make sure you read all of the guides and be prepared for disaster.
Good read here: http://forum.xda-developers.com/showthread.php?t=2201860

[Q] No carrier/SIM support after 4.3 stock restore

My ATT SGH-i747 was rooted and running 4.4.2 until an OTA this past weekend soft-bricked the phone. Phone would boot to a blank screen but still allowed access to download and recovery modes, thankfully.
With help from this awesome forum, and a stock 4.3 flash via ODIN, thanks to enewman17's epic efforts and thread , the phone is back, but now won't recognize the SIM - and baseband version is "unknown" - I suspect I need to now go up to 4.4.2 to get the hw recognized by the sw. Went to ATT and they put a new SIM in but to no avail
CWM recovery is gone, but I can reload that easily enough...
Do I need to just flash the modem, or is the bootloader involved too?
Is there a single flash or .zip that will get the ROM (incl CSC and Modem) up to 4.4.2 in one shot?
I never really wanted to go this deep but here I am so now I'm looking for advice or direction as there are so many directions to look... thanks in advance!

Mismatch in firmware
Digging deeper, using Phone Info *Samsung*, I have noted the following
bootloader version: I747UCUFNJ1
baseband version: <blank>
pda version: I747UCUEMJB
csc version: I747ATTEMJB
skip a bit...
modem version: <blank>
hardware revision: <blank>
mobile operator name: <blank>
mobile network code: <blank>
So it would seem I have a mis-match of versions, where it seems all should be the same..
Would it be safe to flash to MJB following this thread?
http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654

OCTANEJUNKIE said:
My ATT SGH-i747 was rooted and running 4.4.2 until an OTA this past weekend soft-bricked the phone. Phone would boot to a blank screen but still allowed access to download and recovery modes, thankfully.
With help from this awesome forum, and a stock 4.3 flash via ODIN, thanks to enewman17's epic efforts and thread , the phone is back, but now won't recognize the SIM - and baseband version is "unknown" - I suspect I need to now go up to 4.4.2 to get the hw recognized by the sw. Went to ATT and they put a new SIM in but to no avail
CWM recovery is gone, but I can reload that easily enough...
Do I need to just flash the modem, or is the bootloader involved too?
Is there a single flash or .zip that will get the ROM (incl CSC and Modem) up to 4.4.2 in one shot?
I never really wanted to go this deep but here I am so now I'm looking for advice or direction as there are so many directions to look... thanks in advance!
Click to expand...
Click to collapse
Your modem (baseband) appears to have been compromised in the process of downgrading from Kitkat. You could try either of the following solutions...
1) Flash the UCUEMJB modem via custom recovery to return you to complete stock 4.3. You can see the modem file here ....
https://www.androidfilehost.com/?fid=23269279319197285
2) Do a complete stock restore to 4.4.2. You can find the stock update zip via the following thread ...
http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If you can reflash the 4.3MJB modem, you can check to see if you can get an OTA update to 4.4.2. Using Option 2 requires you to be on complete stock 4.3 so this may not work if you currently don't have the baseband/modem. I would strongly advise you stick to the custom recovery flashable files for now and avoid Odin. You would, however, need to restore custom recovery via Odin.
Hope this works for you.

Larry2999 said:
Your modem (baseband) appears to have been compromised in the process of downgrading from Kitkat. You could try either of the following solutions...
1) Flash the UCUEMJB modem via custom recovery to return you to complete stock 4.3. You can see the modem file here ....
https://www.androidfilehost.com/?fid=23269279319197285
2) Do a complete stock restore to 4.4.2. You can find the stock update zip via the following thread ...
http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If you can reflash the 4.3MJB modem, you can check to see if you can get an OTA update to 4.4.2. Using Option 2 requires you to be on complete stock 4.3 so this may not work if you currently don't have the baseband/modem. I would strongly advise you stick to the custom recovery flashable files for now and avoid Odin. You would, however, need to restore custom recovery via Odin.
Hope this works for you.
Click to expand...
Click to collapse
Thanks for the detailed reply with links, Larry :good:
So I guess my plan of actions will be
1) re-install custom recovery w CWM to my external SD card as was previous
-do I *need* later version of CWM? Previous one of mine was 6.0.2.3, IIRC, that is what I can easily flash back to the phone
2) install .zip (from https://www.androidfilehost.com/?fid=23269279319197285) via CWM
If that doesn't work, I was interested in the S3Rx ROM vs. a stock 4.4.2 ROM - is there any way to go straight to a custom 4.4.2 ROM or should I get the modem working in 4.3 first?
Lastly, Where can I find a later version of a CW Recovery Touch .tar to flash via ODIN? (third stoopid noob question in this post, I know...)

Attempt to flash d2att_I747UCUEMJB_bootloader_modem_4.3.zip via CWM Recovery FAILED with Status 7, Installation aborted...
Bootloader version: I747UCUFNJ1
Baseband version: <blank>
Blank stare into space...

OCTANEJUNKIE said:
Attempt to flash d2att_I747UCUEMJB_bootloader_modem_4.3.zip via CWM Recovery FAILED with Status 7, Installation aborted...
Bootloader version: I747UCUFNJ1
Baseband version: <blank>
Blank stare into space...
Click to expand...
Click to collapse
You aren't the first to have this issue. This is why I am still on NE4 and did not take the OTA to NJ1. The update is pointless anyway, all it does is patch the kernel so towelroot won't work anymore aside from updating the bootloader.
Since your bootloader is NJ1, that is your firmware which cannot be downgraded. If you try, you will brick. You have to work with NJ1 files here only. Sure you can flash older modems, but stick to NJ1. I suggest using ODIN to flash a custom recovery, then use enewman17's NJ1 .zip file in said recovery to reflash all the NJ1 stuff. Then do a complete factory reset. You might need to flash stock recovery to do the hard factory data reset, as I am not sure if it can be done in CWM or TWRP.
In the future, I suggest freezing the update and not upgrading until people on here do it and report how it's working or rather not working in this case.

StoneyJSG said:
You aren't the first to have this issue. This is why I am still on NE4 and did not take the OTA to NJ1. The update is pointless anyway, all it does is patch the kernel so towelroot won't work anymore aside from updating the bootloader.
Since your bootloader is NJ1, that is your firmware which cannot be downgraded. If you try, you will brick. You have to work with NJ1 files here only. Sure you can flash older modems, but stick to NJ1. I suggest using ODIN to flash a custom recovery, then use enewman17's NJ1 .zip file in said recovery to reflash all the NJ1 stuff. Then do a complete factory reset. You might need to flash stock recovery to do the hard factory data reset, as I am not sure if it can be done in CWM or TWRP.
In the future, I suggest freezing the update and not upgrading until people on here do it and report how it's working or rather not working in this case.
Click to expand...
Click to collapse
Thanks for the response, Stoney :good:
I have CWM and TeamEpic v5 on external SD, so a version of custom recovery is there (CWM 6.0.2.3) - but do you have a link to enewman17's NJ1 .zip /recovery?
As far as freezing the updates in the future, yes. I tried to keep the OTA push from happening, apparently not ardently enough :crying:

OCTANEJUNKIE said:
Thanks for the response, Stoney :good:
I have CWM and TeamEpic v5 on external SD, so a version of custom recovery is there (CWM 6.0.2.3) - but do you have a link to enewman17's NJ1 .zip /recovery?
As far as freezing the updates in the future, yes. I tried to keep the OTA push from happening, apparently not ardently enough :crying:
Click to expand...
Click to collapse
Not a problem, glad to help when I can. I THINK this is the link you need: http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792
You might want to post in that thread asking if it works when you are already on NJ1 though, or get a hold of enewman17 via PM or something.

SOLVED!
enewman17 posted NJ1 modem .zip here, and now me has modem and cellular service again!
Question: can I update the thread tag from [Q] to [SOLVED] myself?

Try editing your original post.

audit13 said:
Try editing your original post.
Click to expand...
Click to collapse
Yup... Done [emoji222] [emoji222] [emoji222]

[Q] Which Firmware W/ Fresh SlimKat 9 Stable Install

Background: I attempted to update from SlimKat 7.0 stable to 9.0 stable and discovered my apn's were missing and when I try to add them manually it fails to save. I have also found others with this same issue but none have an easy fix. I'm on UCDLK3 firmware, after restoring to previous state using nandroid backup apn's are present. If I try to flash any ROM (even other than Slim) my apn's are missing, even a dirty flash of 7.0 over 7.0. I know I can fix this by flashing stock UCDLK3 and root/twrp/flash slim 9 and everything will likely work fine. I plan to do just that but want to make sure I'm doing things as smart and clean as possible. There is a lot of info out there and I'm finding it hard to sift through old stuff and find the current state of things.
Question: Is there an actual advantage if I upgrade the firmware from UCDLK3 to UCUEMJB while still planning to use SlimKat 9 Stable with BMS kernel and TWRP recovery? Are there any disadvantages? Either way what is the shortest path to get back to stock (either LK3 or MJB) and flash SlimKat?
Thanks

Your APN may not be sticking because your modem and bootloader may be too outdated.
Some of the latest CM11 and AOSP ROMs require a KK bootloader and modem.

And then there are some roms that require at least a 4.3 bootloader and modem, either the MJ2 (leaked) or MJB (official) bootlaoder/modem combos. I have seen mention of these working in some OPs and in the body of other threads. In some of the later TW ROMs you may have to use a custom kernel like kt747 or iBuddler's. I don't know if any kernel other than the stock in SlimKat and AOSP ROMs would be needed with the MJ2/MJB firmware and modem.
I don't know of any advantages other than some of the ROMs require firmware newer than DLK3 to properly boot, receive data, or have a working wifi. As far as disadvantages, KNOX was introduced with the MJB firmware and stock ROMs, once going to MJB or newer firmware you can not make firmware downgrades without a very real risk of hardbricking your phone. Also you will need to insure your baseband and modem versions match. If they do not you risk hardbricking of another variety.
I had not yet realized that the newer AOSP and CM11 required you to go all of the way to NE4, thank Audit.

Just wanted to close the loop on this thread and say thanks for the assistance!
I now have my phone working properly on SlimKat 9; it really was just the firmware not being compatible with newer ROMs as many have suggested. Here is the sequence I followed to do it but really it probably only needed a twrp flash of the mjb firmware and the ROM install:
1. Used odin to restore to stock LK3 (only because I had messed with things so much and wanted a clean slate)
2. Used odin to install TWRP 2.7.1.0 recovery
3. Rooted with SuperSU 2.40 using TWRP
4. Flashed combined MJB modem & bootloader using TWRP
5. Flashed SlimKat 9 using TWRP
6. Flashed Slim GApps using TWRP
7. Rooted with SuperSU 2.40 using TWRP (Lost root after flashing ROM)

thanks for posting fix. am sure it will help others. audit13 and dawgdoc , thank you for continued help with the awesome Slll. :good:
"all i can really do , is stay out of my own way and let the will of heaven be done"

jeff.leonard said:
Just wanted to close the loop on this thread and say thanks for the assistance!
I now have my phone working properly on SlimKat 9; it really was just the firmware not being compatible with newer ROMs as many have suggested. Here is the sequence I followed to do it but really it probably only needed a twrp flash of the mjb firmware and the ROM install:
1. Used odin to restore to stock LK3 (only because I had messed with things so much and wanted a clean slate)
2. Used odin to install TWRP 2.7.1.0 recovery
3. Rooted with SuperSU 2.40 using TWRP
4. Flashed combined MJB modem & bootloader using TWRP
5. Flashed SlimKat 9 using TWRP
6. Flashed Slim GApps using TWRP
7. Rooted with SuperSU 2.40 using TWRP (Lost root after flashing ROM)
Click to expand...
Click to collapse
When you restored to LK3, what Firmware version were you coming from? I'm looking to go to LK3 from the NJ1. However there seems to be cautionary red flags all over the place due to bootloader changes that were made in 4.3.

The OP was already on LK3 with a custom ROM.
Since you are on NJ1, you cannot downgrade the bootloader.

[Q] APN not listed and cannot add

I was on CM 10.2.1
I upgraded to CM11 - I get no wireless data. My phone works but I have no APNs and I could not add them.
I tried SlimKat 9.0 same issue with the APN
I upgraded my CWM to 6.4.0.7 as I heard that caused issues when upgrading to CM11.
I bought Mobile Odin and flashed that way as I thought it might help.
Ive done the following to fix my APN
1) Loaded an old one from working CM 10.2.1
2) Run Root Tweak with the fix APN for CM11 checked
3) Done the airplane mode trick
4) Attempt to add one manually
Does anyone know why this is happening and more importantly how to correct this issue?
Yes I did pore through other threads on how to fix this but no avail.
Thank you

What is your bootloader and modem? Do you get data if you re-install your previous ROM?

audit13 said:
What is your bootloader and modem? Do you get data if you re-install your previous ROM?
Click to expand...
Click to collapse
Bootloader = I747UCDLK3
Modem = I747UCDLK3
Yes I get data when I load a backup of CM 10.2.1
Thanks

Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.

audit13 said:
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
Click to expand...
Click to collapse
Thanks for the quick reply. That sounds hard. From what I'm reading going back is treacherous.
So these are the steps.
1. Load this firmware via ODIN -> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.zip -- What about gapps? Is that in this zip?
2. Run triangle away. (Do I need to do this?)
3. Contact my carrier to unlock my sim. (If this is carrier unlocking ie taking my att phone to Sprint etc, why is this needed?)
4. Get OTA updates. Will this come automagically because I'm on 4.1.1 and does it matter if my flash counter is gt 1?
5. Root phone via Odin with this file CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5.
6. Install CWM if it went away when I went back to firmware - Of course it would because I'll factory reset my phone in step 1.
7. Flash away to a 4.4.4 Rom
Did I miss anything?
Step 4 is the one that scares me -- That one is out of my control. Either I get the OTA or I dont. Anyway I can "request" the OTA?
Thanks again
Be Well

From your custom ROM, run triangle away to reset counter and change things back to official.
Now flash back to stock 4.1.1 using Odin. If your phone does not boot, you need to get into recovery, do a factory reset, and reboot the phone and go through the set up routine.
After loading stock 4.1.1, do this to sim unlock your phone for free: http://forum.xda-developers.com/showthread.php?t=2529200. If you have a code from ATT, you must be running a stock ROM or a custom ROM that is based on a stock Samsung ROM in order to enter the unlock code.
You must be on a stock ROM in order to take OTA updates. OTA updates are the safest way to obtain an updated bootloader and modem.
After updating to 4.3, you cannot downgrade the bootloader as doing so may brick the phone.
The choice is yours in terms of what you want to do. As you found out, some ROMs will not function properly without an updated bootloader and modem. Mixing modem and bootloader versions may also result in a bricked phone.

audit13 said:
From your custom ROM, run triangle away to reset counter and change things back to official.
Now flash back to stock 4.1.1 using Odin. If your phone does not boot, you need to get into recovery, do a factory reset, and reboot the phone and go through the set up routine.
After loading stock 4.1.1, do this to sim unlock your phone for free: http://forum.xda-developers.com/showthread.php?t=2529200. If you have a code from ATT, you must be running a stock ROM or a custom ROM that is based on a stock Samsung ROM in order to enter the unlock code.
You must be on a stock ROM in order to take OTA updates. OTA updates are the safest way to obtain an updated bootloader and modem.
After updating to 4.3, you cannot downgrade the bootloader as doing so may brick the phone.
The choice is yours in terms of what you want to do. As you found out, some ROMs will not function properly without an updated bootloader and modem. Mixing modem and bootloader versions may also result in a bricked phone.
Click to expand...
Click to collapse
To stick with 10.2 or not to that is the question. Everytime I flash or do anything like this on my phone - I get a small lump in my throat knowing I'm dancing in the razors edge of bricking it.

I know how you feel, but I've done it enough times and just accept the fact that I may brick the phone. Jtag service would cost me around $75 so I'm willing to take the chance. I'd be less willing if the phone still has warranty.
Flashing back to stock and running OTA updates is the safest route.
If you don't sim unlock while on stock 4.1.1 and you want to sim unlock your phone in the future, you will need to be on a stock or virtually stock ROM in order to enter the unlock code.

Used ODIN to go back to stock 4.1.1.
Got the OTA update to 4.3
I have my MMS and cellular data back
I'll stick on stock, unrooted 4.3 for a minute.
I should be available to root and update to CM11 or SlimKat or any 4.4 rom whenever I so desire and still keep cellular data.
My baseband is I747UCUEMJB. How can I find out my bootloader and modem versions on UNROOTED device?
Your help is much appreciated and your instructions were flawless.

ddunleavy2 said:
Used ODIN to go back to stock 4.1.1.
Got the OTA update to 4.3
I have my MMS and cellular data back
I'll stick on stock, unrooted 4.3 for a minute.
I should be available to root and update to CM11 or SlimKat or any 4.4 rom whenever I so desire and still keep cellular data.
My baseband is I747UCUEMJB. How can I find out my bootloader and modem versions on UNROOTED device?
Your help is much appreciated and your instructions were flawless.
Click to expand...
Click to collapse
In a terminal or adb shell you can enter this to check your bootloader:
Code:
getprop ro.bootloader
In a terminal or adb shell you can enter this to check your modem (should match the baseband your phone reports in About):
Code:
getprop gsm.version.baseband
I don't believe either of these commands require root unless stock has getprop locked down tighter that AOSP ROMs; I just entered them in a user shell.
There are a couple of firmware updates for your device beyond MJB, NE4 and NJ1. Some users, myself included, had GPS problems that were a bit of a pain to fix on newer 4.4 AOSP based ROMs with the MJB firmware, but data was ok with MJB. Also, you'll need newer firmware if you decide to test drive the lollipop alphas that are floating around. There are custom recovery flashable firmware updates on XDA from a trusted developer if you decide you need that, or you might want to take a couple more OTAs if you're more comfortable going that route. You're already on MJB so there's no going back

The terminal worked
Bootloader and baseband = I747UCUEMJB
What???? I might need more updates for all the roms out there.....ugggh.
"There are custom recovery flashable firmware updates on XDA from a trusted developer if you decide you need that, or you might want to take a couple more OTAs if you're more comfortable going that route."
If I decide to use these flashable firmware updates on XDA from a trusted developer or OTA its same as this: going forward and NEVER going backward when getting firmware updates?, yes?

yes. downgrading bootloader will almost certainly cause a brick.
"all i can really do , is stay out of my own way and let the will of heaven be done"
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
audit13 said:
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
Click to expand...
Click to collapse
+1
"all i can really do , is stay out of my own way and let the will of heaven be done"

You guys are on point.
Last night I received another OTA to 4.4.2.
Baseband now at NE4.
Thanks again for taking the time to answer all this -- Really really appreciate it.
EDIT: Can I still use this to root my phone via ODIN or is there a different process for this baseband?
CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5
I load this into ODIN, plug my phone in download mode and root away. Does either the file I use change or do I have to use something other than ODIN?
Thanks again

To get root, I would flash a custom recovery and flash supersu from recovery, then let supersu disable know.
The file you named looks to be outdated as it refers to the s3 as d2att. Since unified builds were released, the s3 is now referred to as the d2lte.

I have ROM Manager installed. It has an option to "Flash Clockworkmod Recovery". I just tried it and it failed and I think thats because I dont have root. In the past I've had to root my phone via ODIN, then flash custom recovery then MOD away.
In the past I rooted the S3 via ODIN. With this new 4.4.2 version do I still root via ODIN provide I find the correct file because -> CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5 this one is probably for a 4.1.1 version phone?

I would not flash anything for the d2att at this point.
Try this:
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_...Edition/d2lte/
Download supersu zip from here and place it onto an external SD card or copy it to the phone's internal storage: http://download.chainfire.eu/695/SuperSU/
In Odin, uncheck everything except f.reset time. Flash Philz. When you see reset in the status window, remove USB cable, pull battery, replace battery, boot into recovery, flash supersu, reboot.

I am fairly certain that AOSP, or at least CM, de-unified in the past few months. Not that it matters much, other than for the confusion it causes.