Develop Bugs

S3 won't recognize SIM card

Friend of mine at work has an ATT Galaxy S3 that he said was running CM10 fine. He said that he flashed CM11 recently and that the phone boots and runs fine, but will not read his SIM card. Is this a known issue, or where should I start to help get him up and running again? I'm pretty android savvy, but I've never owned/worked with the S3 so I am not familiar at all with it specifically.
Any help would be greatly appreciated. Thanks!

Does the phone display the correct IMEI and baseband? Maybe an updated modem is required?

audit13 said:
Does the phone display the correct IMEI and baseband? Maybe an updated modem is required?
Click to expand...
Click to collapse
I asked him about it and he said that it's not showing any information under system properties for the baseband or anything. I he said that he also first flashed the bootloader from here as well as the latest CWM recovery before flashing the M3 milestone snapshot of CM11 (from here). I had him flash a different rom (pac-man rom) just to test and the same issue occurred, so I believe it could be an issue with the modem as you said.

[Q] T-Mobile branded S3 somehow became AT&T.

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.

[RESOLVED-HARDWARE ISSUE] No SIM card detected....

EDIT: ISSUE RESOLVED. THIS IS A HARDWARE PROBLEM. SEE POST #16
---------------------------------------------------
Hey folks, so my friend didn't wait for my flashing skills and flashed his g/f's phone on his own.
Phone was already on some very old version of SlimROM AOSP and an older TWRP of some version or other.
I emailed him TWRP 7.1.X zip and a 4.1.2 stock rooted ROM zip.
He flashed them both at the same time, without rebooting in between.
And got a boot loop.
I had him flash just the TWRP and reboot to recovery. Then flash the ROM zip.
Now his phone suddenly does not detect the SIM card any longer? It did before all this.
The IMEI is fine. And I tried my very old AT&T SIM card, but it didn't detect my SIM either.
I then ODIN'd back to stock 4.1.2 and had same problem.
So I then rooted and flashed a custom 4.1.2 that came with a custom kernel, and still had the same problem.
So then I ODIN'd back to a stock ICS and STILL have the same problem.
Any suggestions?

CZ Eddie said:
Hey folks, so my friend didn't wait for my flashing skills and flashed his g/f's phone on his own.
Phone was already on some very old version of SlimROM AOSP and an older TWRP of some version or other.
I emailed him TWRP 7.1.X zip and a 4.1.2 stock rooted ROM zip.
He flashed them both at the same time, without rebooting in between.
And got a boot loop.
I had him flash just the TWRP and reboot to recovery. Then flash the ROM zip.
Now his phone suddenly does not detect the SIM card any longer? It did before all this.
The IMEI is fine. And I tried my very old AT&T SIM card, but it didn't detect my SIM either.
I then ODIN'd back to stock 4.1.2 and had same problem.
So I then rooted and flashed a custom 4.1.2 that came with a custom kernel, and still had the same problem.
So then I ODIN'd back to a stock ICS and STILL have the same problem.
Any suggestions?
Click to expand...
Click to collapse
Which S2 model? This is the T-Mobile forum and you said ATT sim. ATT sim won't work in a TMobile phone without it being unlocked.
Sent from my SGH-T989

jrc2 said:
Which S2 model? This is the T-Mobile forum and you said ATT sim. ATT sim won't work in a TMobile phone without it being unlocked.
Sent from my SGH-T989
Click to expand...
Click to collapse
SGH-T989 is the phone. The Hercules. Her SIM is a T-Mobile "isis" micro SIM with the little adapter thing. She says it worked fine before the update.

CZ Eddie said:
SGH-T989 is the phone. The Hercules. Her SIM is a T-Mobile "isis" micro SIM with the little adapter thing. She says it worked fine before the update.
Click to expand...
Click to collapse
When you tried a clean flash in Odin, did you/she wipe data, cache, and Dalvik before flashing stock?
Have a good evening,
jrc2
Sent from my SGH-T989

jrc2 said:
When you tried a clean flash in Odin, did you/she wipe data, cache, and Dalvik before flashing stock?
Have a good evening,
jrc2
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, wiped system and everything except internal SD.

CZ Eddie said:
Phone was already on some very old version of SlimROM AOSP and an older TWRP of some version or other.
Click to expand...
Click to collapse
And.... that's why the SIM card worked before the "update" to stock TouchWiz. LOL
Turns out the SIM card she was using is the newer "Isis" version and it's not compatible with the 4.1.2 TouchWiz. And since 4.1.2 is the newest TouchWiz available for the Hercules, I just flashed to the newest AOSP 4.4 and now SIM is recognized again. I guess the really old Slim AOSP ROM was still somehow newer than the 4.1.2.
Dang, it sucks that Samsung hasn't even given you guys 4.2 yet. Sheesh.
Thanks for the help though.

CZ Eddie said:
And.... that's why the SIM card worked before the "update" to stock TouchWiz. LOL
Turns out the SIM card she was using is the newer "Isis" version and it's not compatible with the 4.1.2 TouchWiz. And since 4.1.2 is the newest TouchWiz available for the Hercules, I just flashed to the newest AOSP 4.4 and now SIM is recognized again. I guess the really old Slim AOSP ROM was still somehow newer than the 4.1.2.
Dang, it sucks that Samsung hasn't even given you guys 4.2 yet. Sheesh.
Thanks for the help though.
Click to expand...
Click to collapse
Glad you got it working again! Part of it is Samsung is now on the S5, and they want people to buy it so they don't update the S2. The other problem is TouchWiz is so inefficient that some if their phones with 1gb if ram can't run TouchWiz KitKat, even though KK is designed for 512 mb of RAM and up. That's why every Samsung phone or tablet I've ever owned has been rooted once it is out of warranty (about when they stop updating if you buy new.)
If I can help you with anything else, please reply to this post.
Have a good night!
jrc2
Sent from my SGH-T989

UPDATE: BROKEN AGAIN
Well I just don't understand this one. The phone and SIM were working fine last night. I gave the phone back to the owner. This morning she brings it back to me because once again, the SIM is not working. She didn't do anything to the phone, so we're not sure what caused this.
And for the life of me, I can't get the SIM card to work again, after re-doing everything I did last night to fix it.
So I went to T-Mobile store and got her the old style SIM specifically for this phone model. And the phone doesn't see that SIM either. The T-Mobile guy was perplexed.
Especially so, because the phone recognizes my AT&T SIM and asks for an unlock code. It see's my Mom's AT&T SIM also. Asks for an unlock code.
So WTF. It see's AT&T SIM's but can't see any TMO SIM.
Most.Perplexing.
Already tried ODIN to stock and flashed AOSP 4.4. Nothing working.
Full wipes in between flashes.
IMEI is still showing up fine and TMO agent didn't find any locks on the IMEI in his system.

CZ Eddie said:
UPDATE: BROKEN AGAIN
Well I just don't understand this one. The phone and SIM were working fine last night. I gave the phone back to the owner. This morning she brings it back to me because once again, the SIM is not working. She didn't do anything to the phone, so we're not sure what caused this.
And for the life of me, I can't get the SIM card to work again, after re-doing everything I did last night to fix it.
So I went to T-Mobile store and got her the old style SIM specifically for this phone model. And the phone doesn't see that SIM either. The T-Mobile guy was perplexed.
Especially so, because the phone recognizes my AT&T SIM and asks for an unlock code. It see's my Mom's AT&T SIM also. Asks for an unlock code.
So WTF. It see's AT&T SIM's but can't see any TMO SIM.
Most.Perplexing.
Already tried ODIN to stock and flashed AOSP 4.4. Nothing working.
Full wipes in between flashes.
IMEI is still showing up fine and TMO agent didn't find any locks on the IMEI in his system.
Click to expand...
Click to collapse
When you are on stock, does the sim work then?
Sent from my SGH-T989

jrc2 said:
When you are on stock, does the sim work then?
Sent from my SGH-T989
Click to expand...
Click to collapse
Nope. Tried ODIN to ICS and JB and neither see the SIM.

Gahh, just flashed the 4.4 wild kernel and a EMC6 (?) modem. Whatever the latest modem is.
No dice.

@CZ Eddie
Have you tried flashing the latest radio?
Sent from my SGH-T989

jrc2 said:
@CZ Eddie
Have you tried flashing the latest radio?
Sent from my SGH-T989
Click to expand...
Click to collapse
Yup, modem=radio.

I ODIN'd the older 4.0.X ROM found at SamMobile: T989UVLH1_T989TMBLH1_TMB
Then I ODIN'd root.
Then I flashed the older radio: sgh-t989_uvle1_radio
I followed the directions in this thread:
http://forum.xda-developers.com/showthread.php?t=2024514
This unlocked the phone for my AT&T SIM to use. And dammit, the phone see's my AT&T SIM and is making calls just fine.
BUT IT STILL REFUSES TO ACKNOWLEDGE ANY T-MOBILE SIM.
WTF WTF WTF. LOL. :silly:

Okay, I got things figured out.
This is a HARDWARE issue.
If the AT&T SIM is inserted properly, it works fine.
If either T-Mobile SIM is inserted properly, it does not work.
If the T-Mobile micro SIM is inserted properly, then slid out 1/8", then it works.
I can't get the T-Mobile normal SIM to work in any position, but then it's bigger, so it's harder to get it to "slide around" in the slot they way I need it to.

Could you please send me the link or ICS stock rom file, all link I found already die.

snake2001vn said:
Could you please send me the link or ICS stock rom file, all link I found already die.
Click to expand...
Click to collapse
Here you go. http://www.sammobile.com/firmwares/3/?download=10961
You will need a Sam Mobile account to download the file.
Sent from my SGH-T989

CZ Eddie said:
Phone was already on some very old version of SlimROM AOSP and an older TWRP of some version or other.
I emailed him TWRP 7.1.X zip and a 4.1.2 stock rooted ROM zip.
He flashed them both at the same time, without rebooting in between.
And got a boot loop.
I had him flash just the TWRP and reboot to recovery. Then flash the ROM zip.
Click to expand...
Click to collapse
I am not in a similar situation, I just bought an unlocked ATT Skyrocket using T-mobile SIM. And I hope to find a ROM supports ISIS/Softcard now. I think it would probably be a T-mobile stock ROM.
I ran through I727 and T989 forums, yet got a bit confused with all types of methods.
So, what's your latest suggested steps? Thanks,

HardBricked i747 after UCUFNE4

I've got a different issue here. I was running SlimKat 4.4.4 with BMS kernel on my d2att. I was on the CUEMJB Bootloader and Modem, so I thought that I can directly flash the rom. First, what I did was flash UCUEMJB_to_UCUFNE4_Firmware_update.zip. It flashed perfectly till the end. Then I flash the I747UCUFNE4_Stock_Rooted_Deodex_3-31-15.zip, which had an error that I had forgotten. It apparently is caused by my BMS kernel, so I went on and reinstall SlimKat 4.4.4 to remove the kernel. It flashed perfectly, but when I rebooted my phone, it did not power on. I was thinking, what's inside the UCUEMJB_to_UCUFNE4_Firmware_update.zip, are they the bootloaders and modem for CUFNE4 ? If so, is my phone dead like all the others who flashed 4.4.2 modem over 4.3 ? Please, I need my phone bad.

Did you follow this thread: http://forum.xda-developers.com/showthread.php?t=2789917 ?
Since you were already on the mjb bootloader, you flashed the UCUEMJB_to_UCUFNE4_Firmware_update.zip file? Any errors when flashing this?
Before installing NE4 firmware, did you do a full wipe as instructed in step 3 of the thread I linked?

audit13 said:
Did you follow this thread: http://forum.xda-developers.com/showthread.php?t=2789917 ?
Since you were already on the mjb bootloader, you flashed the UCUEMJB_to_UCUFNE4_Firmware_update.zip file? Any errors when flashing this?
Before installing NE4 firmware, did you do a full wipe as instructed in step 3 of the thread I linked?
Click to expand...
Click to collapse
Hey yeah. No errors occurred when I flashed it. The only I have gotten was from the OTA update zip itself. I can't remember what it is, but it prevented me from updating my phone to UCUFNE4. So I reinstalled Slimkat and booted properly but at the time I've rebooted, it's all dead.

And also, yes. That is the post that I've followed. I checked if my bootloader and modem are CUEMJB, and they are. So I figured that the firmware update should've not ruin it.
NOTE : I am running on a debrick card UCUEMJB if that helps with the information. I can't seem to boot off the eMMC itself, so I always kept the SD card on the slot. That, until it died.

I really think that my bootloader is messed up because of the UCUEMJB_to_UCUFNE4_Firmware_update.zip. I think it borked my bootloader, that's why I can't use any debrick images to recover it. Please, help. I'm short on funds, and losing this phone is a big cut on my budget.

I heard that the i747m users recovered theirs by pulling out the 128mb file. So if any of you i747 users running at the NE4 version could just pull out the bootloader partition, that would be great. enewman's debrick doesn't seem to work for me.

The bootloader for the i747 and i747m are not compatible even though they phones appear to have the same hardware.
So the phone does not boot at all with the mjb debrick image?

audit13 said:
The bootloader for the i747 and i747m are not compatible even though they phones appear to have the same hardware.
So the phone does not boot at all with the mjb debrick image?
Click to expand...
Click to collapse
It does not. Not even with the 4.4.2 debrick image. Help

If it used to boot with the debrick image and it doesnt boot now, a jtag service may be the only way to revive it.

May I just know what happened to my phone before it had gone bananas? A little information might help. Also, Im planning to buy a board for T999. Will it fit with the I747 chassis ?

I really don't know what happened to cause this problem with your phone. When flashing a phone, there is always an element of risk. I have pooched a few phones in my life too. I even damaged a couple of sim slots by using sim adapters too.
When your phone was able to boot with the debrick image, you could have tried reflashing the mjb bootloader and modem but it's a moot point now.

Sim Card not recognized..

Hey all,
I recently picked up a TracFone BYOP Sim Card for my Galaxy S3. My phone is unlocked and the IMEI is clean, so in theory the Sim Card should work. Well, it didn't. At first I thought that the Sim Card itself was faulty. My phone was recognizing it, but I wasn't able to make phone calls or connect to data. After messing with the Sim Card a bit, I realised that the modem/bootloader on my phone was outdated. It was still on the NE4 version.
So, I updated the modem/bootloader to NJ2 (the latest version) and now my phone is reporting no Sim Card at all.. great. Since it was recognized before, I know that my Sim Card slot isn't acting up. I could possibly try using Odin to reset my phone, but there are not any files available for Android 4.4.2 to flash. Other than that, I can't downgrade the modem to my knowledge so it looks like I'm stuck with a broken version.
Help would be greatly appreciated.
~Mario119~

What rom do you have installed?

jason2678 said:
What rom do you have installed?
Click to expand...
Click to collapse
I have the latest build of Matrixzone's CM 13 installed. People report phone calls, texts, and 4G LTE are fully functional on the ROM, so I know that the ROM itself isn't the culprit.

Mario119 said:
I have the latest build of Matrixzone's CM 13 installed. People report phone calls, texts, and 4G LTE are fully functional on the ROM, so I know that the ROM itself isn't the culprit.
Click to expand...
Click to collapse
Gotcha. Sometimes stock roms have issues when they aren't on the firmware they're intended for, but cm is usually pretty universal.
Try a few airplane mode toggles. Sometimes that got the no sim thing to come around for me on the early cm13 builds.
If that doesn't work, consider flashing a cm 12.1 nightly and see if it has the same issue. I'm sure it's getting better, but when I last used it cm 13 want entirely stable yet.

jason2678 said:
Gotcha. Sometimes stock roms have issues when they aren't on the firmware they're intended for, but cm is usually pretty universal.
Try a few airplane mode toggles. Sometimes that got the no sim thing to come around for me on the early cm13 builds.
If that doesn't work, consider flashing a cm 12.1 nightly and see if it has the same issue. I'm sure it's getting better, but when I last used it cm 13 want entirely stable yet.
Click to expand...
Click to collapse
I just tried the Sim Card in another Galaxy S3 (a d2tmo) after reflashing it with a stock Odin image, and it worked. I've tried to flash the 4.3 Odin image on my d2att and it failed, along with the 4.2 Odin image. Does anyone know where I could perhaps find a stock 4.4.2 image?

AT&T never released a stock image past android 4.1.1, and you can't use that. That NJ2 bootloader cannot be downgraded, or you'll have a hard brick. That is why Odin is failing.
I'd still recommend giving enewman's NJ2 stock rom, or a lollipop aosp rom a try. I haven't had much access to this phone for about a month, but I had a lot of no sim troubles with CM 13 back then.

jason2678 said:
AT&T never released a stock image past android 4.1.1, and you can't use that. That NJ2 bootloader cannot be downgraded, or you'll have a hard brick. That is why Odin is failing.
I'd still recommend giving enewman's NJ2 stock rom, or a lollipop aosp rom a try. I haven't had much access to this phone for about a month, but I had a lot of no sim troubles with CM 13 back then.
Click to expand...
Click to collapse
The stock ROM won't work, it still isn't recognizing the Sim Card. It appears that the NJ2 Bootloader screwed with something internally. Since I can't downgrade, what are my options?

Mario119 said:
The stock ROM won't work, it still isn't recognizing the Sim Card. It appears that the NJ2 Bootloader screwed with something internally. Since I can't downgrade, what are my options?
Click to expand...
Click to collapse
Install the Samsung phone info app. Report what it says for bootloader and baseband. Let's make sure of exactly what is on this phone for firmware.
Alternately type this in a terminal or adb shell
Code:
getprop ro.bootloader
getprop gsm.version.baseband

jason2678 said:
Install the Samsung phone info app. Report what it says for bootloader and baseband. Let's make sure of exactly what is on this phone for firmware.
Alternately type this in a terminal or adb shell
Code:
getprop ro.bootloader
getprop gsm.version.baseband
Click to expand...
Click to collapse
Bootloader Version: I747UCUFNJ2
PDA Version: I747UCUFNJ2
CSC Version: I747ATTFNJ2
Baseband Version: I747UCUFNJ2
From the info I've seen, it appears everything matches up.

Does the phone display the correct imei from typing in *#06#? Could the imei be blacklisted?

audit13 said:
Does the phone display the correct imei from typing in *#06#? Could the imei be blacklisted?
Click to expand...
Click to collapse
The IMEI is the same as the IMEI printed in the rear of the device. According to Swappa and IMEIPro.info, the IMEI is not blacklisted anywhere.
I directly updated the Modem/Bootloader from NE4 > NJ1 > NJ2. I rebooted between every update, but I never checked to see if the Sim was recognized on NJ1.

Are you able to try the phone in its current state with another sim card?

audit13 said:
Are you able to try the phone in its current state with another sim card?
Click to expand...
Click to collapse
I tried a spare one that came with the activation kit, no luck. NJ2 definitely did something, unfortunately. Are you able to downgrade just the modem (not the bootloader) without a chance of bricking the phone?

I would not start mixing bootloader and modems as it could cause a brick.
At this point the phone does not work or recognize any sim cards? Was a working sim tested with the phone prior to making this thread?

audit13 said:
I would not start mixing bootloader and modems as it could cause a brick.
At this point the phone does not work or recognize any sim cards? Was a working sim tested with the phone prior to making this thread?
Click to expand...
Click to collapse
Technically, yes. I was on the NE4 modem and the phone recognized the Sim Card, but nothing was working with it. I thought the Sim was broken at that point, so I tried it in another Galaxy S3 and it worked perfectly. So I narrowed the problem down to my phone. I then proceeded to update the modem/bootloader to NJ2. After I updated and turned the phone on, it reported having 'No Sim Card'. I've tested it so far on 2 different ROMs, all of them say the same thing. Something with NJ1/NJ2 must of went wrong regarding the modem. The best part is, I can't Odin my phone back to stock because AT&T never bothered to release a 4.4.2 tar.gz file...

It's also possible that the sim reader is damaged.

audit13 said:
It's also possible that the sim reader is damaged.
Click to expand...
Click to collapse
I suppose it could be, but what about the fact that it recognized the Sim Card using the NE4 bootloader/modem? Perhaps it was working slightly (albeit broken), but changes in NJ2 rendered it completely broken? I just don't want to shell out the money if it isn't necessary, y'know. It'd be a shame if a replaced SIm Card Reader still didn't work, if it turned out to be something on the software-side.

Isn't the sim reader removable? They are cheap on eBay I think.

audit13 said:
Isn't the sim reader removable? They are cheap on eBay I think.
Click to expand...
Click to collapse
It turns out that they are only $6.50 for a brand new Sim Card Reader w/ 2-Day shipping. Might as well give it try, I can only improve from here.

Good luck. Keep us informed. Thanks.