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.
Related
I have had annoying ongoing problem of my phone needing to restart due to my Sim card being removed. I have not removed my sim card at all and it has been happening since I have updated to the newest modem NB4. My setup is as follows the Insane Kit Kat Rom V5 with the included Kernel. To note this has happened since updating to the new NB4 modem. If anyone has any suggestions I would appreciate it.
Nope, so far nothing fixes it other than exchanging your phone and hoping the replacement is fine. There is a thread over on the AT&T forum where people, me included, are having this problem. I've replaced the SIM card, SIM card holder, returned to an earlier nandroid when I did not have this problem. I've also unsynced the play store thinking it had something to do with it since it would always occur when I had an app update waiting for me. So far nothing has fixed it.
Sent from my SGH-M919 using Tapatalk
I started getting this same message a while back when on Wicked v10 and mk2 baseband. It wasn't the ROM's fault because I was using the ROM for a few months without problems. I updated to NB4 baseband and the same thing was happening. Flashed a 4.4.2 Rom didn't help. it hasn't happened since I flashed Insane kk v5.
☞ Sent from here ☜
baseballfanz said:
I started getting this same message a while back when on Wicked v10 and mk2 baseband. It wasn't the ROM's fault because I was using the ROM for a few months without problems. I updated to NB4 baseband and the same thing was happening. Flashed a 4.4.2 Rom didn't help. it hasn't happened since I flashed Insane kk v5.
☞ Sent from here ☜
Click to expand...
Click to collapse
Really?? That's great, hopefully it stays working great. What kernel are you using?
I was having the same problem and I did 2 things:
1) I verified I had no foreign debris or anything in the sim card slot. Took a can of compressed air and blew it out.
2) I re'Odin'ed the modem again (twice as mentioned in @shiamatsu thread)
It seems to have fixed things for me. Good luck.
vinniej said:
I was having the same problem and I did 2 things:
1) I verified I had no foreign debris or anything in the sim card slot. Took a can of compressed air and blew it out.
2) I re'Odin'ed the modem again (twice as mentioned in @shiamatsu thread)
It seems to have fixed things for me. Good luck.
Click to expand...
Click to collapse
I will try all of these suggestions that I have seen so far. What about Odining back to stock and then rooting again? Like I have stated previously I have started seeing this issue since updating to the NB4 Modem and Insane KK. I am sure it isn't the ROM, so I will stick with Insane KK because it is a nice ROM. If anything changes I will report back.
Well, I'm going to take back what I said about fixing it. Sim card removed error happened again. I managed to get a logcat, and dmesg. I have not seen any smoking guns in the logs so I'm going to try a different kernel.
Let me know what kernel you use.
Sent from my SGH-M919 using xda app-developers app
crazyc78 said:
Let me know what kernel you use.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I had Talexop's and switched to Ktoonsez's (TW 4.4.2). I did get another error after switching so I'm not sold on a kernel issue either.
I think I'm going to retrace my steps and start from the ground up. I jumped directly from the MDL modem directly to NB4. Maybe I need to go MDL>MK2>NB4?? Maybe try a different Odin version? Switch USB ports on my desktop? Different cable? I'm going to keep trying different things until I get it fixed. It is quite an annoyance because the error happens at times when the phone is asleep and you obviously cannot get any calls, messages, etc.
I'll keep the thread updated for sure.
Been half a day and no errors yet (knock on wood). I did not change anything as far as kernel, rom, or modem is concerned. I did go into Settings>More networks>Mobile Networks>Network Operators>Search Networks and then tapped the tmo network (manual network selection).
I do live / work in an area where Tmo goes bye-bye and there is only Vzn and ATT. I recall having to switch networks recently in order to make a call in that area for work from the no signal zone (I have a spare "work" SIM and my phone is unlocked). Perhaps doing that jacked with my selected default network and could indirectly be the cause of the no sim errors?
And I've done the SIM switch in the past on 4.3 roms without issue. Maybe it is a KK / NB4 bug?
Sounds like you're on track bro, I have tried a few things and so far knock on wood like you said it seems to have worked. First I thought about going back to stock but Odin couldn't recognize the md5 or tar files I downloaded. So then I decided to reflash the NB4 modem. I flashed it three times!! Maybe to see if that would make a difference. Then I reinstalled Insane Kit Kat V5 and did a clean install then restored my backup. So far I have Been running my set up for almost 24 hours and not one error! I will keep looking out for it and report back after my current battery had drained out.
SENT FROM MY INSANELY SICK S4
So I just wanted to give an update on my situation. I have gone back to stock the original 4.2.2, and then rooted my device and then installed Insane KK V5. I have noticed with the stock tar ball file of 4.2.2 I get the NB4 modem. A couple times I did not get the NB4 modem I had the original modem. So then I flashed the NB4 modem and my phone was saying unknown baseband. The last two times I have went back to stock it has given me the NB4 modem and I am still on Knox free bootloader. I am still getting SIM card removed errors, more frequently than ever now. A few times my phone tells me that there is no SIM card inserted at all!!! Very frustrating, I was on a phone call earlier tonight and the error happened during the call. So I called Tmo for a replacement SIM card and we will see if that helps, I'm optimistic that it will. I'm now convinced it may be the NB4 modem, we will see what happens when I get my new SIM. If anyone has any more suggestions I will be open to them.
SENT FROM MY INSANELY SICK S4
I had one error since I last posted. I agree that it must be something with the modem and perhaps we are the only 2 people seeing this issue (I find it hard to believe). I am also on the 4.2.2 bootloader with the NB4 modem. I'm hesitant to downgrade as it has not happened more than once over 4 days.
Let me know if the new SIM cures your problems. I may have to make a trip to the local tmo store as well.
vinniej said:
I had one error since I last posted. I agree that it must be something with the modem and perhaps we are the only 2 people seeing this issue (I find it hard to believe). I am also on the 4.2.2 bootloader with the NB4 modem. I'm hesitant to downgrade as it has not happened more than once over 4 days.
Let me know if the new SIM cures your problems. I may have to make a trip to the local tmo store as well.
Click to expand...
Click to collapse
This was the 2nd post in the thread. I've tried all that and for a while I thought it was fixed. I think I made it 4 days without a problem but then they came back.
_eroz said:
Nope, so far nothing fixes it other than exchanging your phone and hoping the replacement is fine. There is a thread over on the AT&T forum where people, me included, are having this problem. I've replaced the SIM card, SIM card holder, returned to an earlier nandroid when I did not have this problem. I've also unsynced the play store thinking it had something to do with it since it would always occur when I had an app update waiting for me. So far nothing has fixed it.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Well...Here is my latest and greatest attempt. I flashed the NB4 modem 3 times (no auto reboot throughout the process), and did battery pulls after the first two flashes. 36 hours and no messages.
Sorry if this is a noob question but I'm having this same issue and waiting on new sim tray, which I gather....isn't going to fix the issue. Did you flash this modem in recovery or through Odin? And I'm not too keen on this Knox business. Im on a 4.4.2 ROM and not sure what bootloader I'm on and not really sure how to go about finding out. From what I gather, the process is different...... Or the file nb4 file I need to flash is different for each bootloader. I'm glued to this thread because I just bought the phone on CL about 2 months ago. Im pretty upset about this to say the least. I loved this phone before all this bull****
analogchild said:
Sorry if this is a noob question but I'm having this same issue and waiting on new sim tray, which I gather....isn't going to fix the issue. Did you flash this modem in recovery or through Odin? And I'm not too keen on this Knox business. Im on a 4.4.2 ROM and not sure what bootloader I'm on and not really sure how to go about finding out. From what I gather, the process is different...... Or the file nb4 file I need to flash is different for each bootloader. I'm glued to this thread because I just bought the phone on CL about 2 months ago. Im pretty upset about this to say the least. I loved this phone before all this bull****
Click to expand...
Click to collapse
I'll try to explain what I know (which ain't much!). In order to avoid Knox some folks including myself have retained the knox free (MDL) 4.2.2 bootloader. How to tell if you have a knox free bootloader look HERE (credit to @shiamatsu) By flashing a modem.bin (which can only be done via. ODIN) we are able to have the benefits of the newer radio, but keep the knox free bootloader. A few of us like _eroz and crazyc78 have seen issues with SIM errors since going to the NB4 modem with MDL bootloader. And thus this thread. And in case you want the instructions to upgrade to the NB4 modem look HERE
I imagine if you don't mind knox and you did the full upgrade, you probably should not be seeing the SIM card errors. I'd be curious to know if anyone is seeing SIM card removed errors with the NB4 bootloader / modem.
Brain hurts. Time for a beer...
Thank you. I'm gunna give it a go and see if it works
This may be a hardware issue. My wife gets it on stock never rooted.
I am curious to know when you flashed the NB4 modem did you go back to stock first and then reroot your device and then flash a rom and then odin the NB4 modem? I did all that and still got errors. I am going to update to Insane Kit Kat V6 later tonight hopefully I don't have issues after updating. I am going to try your remedy and see if it works, and if it doesn'tjust wait for my new simcard.
SENT FROM MY INSANELY SICK S4
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.
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,
These issues started with the upgrade to latest T-Mobile 4.3 software pack at the end of November. Phone operated perfectly before then. After the update, the phone would periodically not receive/place calls/texts/use data. The issue kept worsening daily. It is not related to the SIM card or location, as the card has been replaced and tested in an alternate phone where it performs perfectly.
The T999L was then consequently rooted, KNOX flagged (it's already past warranty, Samsung wouldn't give a rat's ass about it), flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted. Restored to stock 4.1.2, same issues. Did 3 updates OTA to get to latest 4.3, same issues.
Messed around with 4636 menu, 2263 menu, etc. Some changes had a temporary result but nothing permanent. Calls to the phone are redirected to voicemail. When placing a call, it takes 5-10 seconds to either place it or disconnect it (as it can't connect to the network, I guess?). The bars on the phone show 3-4 bars typically, but the phone is rarely able to acquire a data connection. Again, this is not the case with other phones the SIM is tried on.
Any suggestions? I've spent probably close to 10 hours researching this and trying everything out and I am absolutely stumped. This is my mom's phone and a replacement Alcatel OneTouch Fierce 2 just "doesn't look nice", so I'm getting a fair bit of *****ing for trying to help solve this, even though it's not my fault. Would appreciate some help before Christmas.
Have you tried updating the modem?
systemcode said:
Have you tried updating the modem?
Click to expand...
Click to collapse
flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted.
Click to expand...
Click to collapse
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
dwegiel said:
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
Click to expand...
Click to collapse
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
nirogu325 said:
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
Click to expand...
Click to collapse
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
dwegiel said:
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
Click to expand...
Click to collapse
Well, OTA updates can sometimes fail, that's why I gave you the ODIN firmware link. It's the best help I can offer.
Hey guys... Been a LONG time since messing with an S3, and I don't want to brick it... SO, figured I'd reach out and ask before doing anything...
I downgraded a friend's S3 to UVDLJC to sim unlock it and it seemed to work fine on stock ROM. I then rooted the rom, flashed TWRP and factory reset the device and then flashed a custom ROM (this version is SlimKat but I had tried CM13 as well.. both have the same issue, no SIM detected)...
Anyway, I assume that it is a modem/radio issue and I should just be able to flash the modem firmware and be fine.. Problem I'm having is I'm not sure what to use... The phone is a T-999L Which, as I understand it, is the LTE GS3, but the software that was on it was based on the non LTE version (not sure if I'm correct about this)...
Anyway, looking to get this phone working for the friend's daughter (it was supposed to be a christmas present )...
Any and all help is appreciated.
Additional Info:
Phone model is T-999L
Boot loader is T999UVDLJC
Build version reports 4.4.4
Rom is currently SlimKat
Unified tools reports model as SGH-T999, type as d2tmo
Not sure what other info can help, but happy to provide.
RBThompsonV said:
Hey guys... Been a LONG time since messing with an S3, and I don't want to brick it... SO, figured I'd reach out and ask before doing anything...
I downgraded a friend's S3 to UVDLJC to sim unlock it and it seemed to work fine on stock ROM. I then rooted the rom, flashed TWRP and factory reset the device and then flashed a custom ROM (this version is SlimKat but I had tried CM13 as well.. both have the same issue, no SIM detected)...
Anyway, I assume that it is a modem/radio issue and I should just be able to flash the modem firmware and be fine.. Problem I'm having is I'm not sure what to use... The phone is a T-999L Which, as I understand it, is the LTE GS3, but the software that was on it was based on the non LTE version (not sure if I'm correct about this)...
Anyway, looking to get this phone working for the friend's daughter (it was supposed to be a christmas present )...
Any and all help is appreciated.
Additional Info:
Phone model is T-999L
Boot loader is T999UVDLJC
Build version reports 4.4.4
Rom is currently SlimKat
Unified tools reports model as SGH-T999, type as d2tmo
Not sure what other info can help, but happy to provide.
Click to expand...
Click to collapse
Odin'ed back to LJC original firmware... still shows no Sim card.
The latest custom ROMs require the latest bootloader and modem to function properly so the phone probably needs an update. Once the phone is running a 4.3 or higher bootloader means the bootloader cannot be downgraded in the future.
I don't see the LJC firmware for the T999L: http://www.sammobile.com/firmwares/database/SGH-T999L/
I see LJC for teh T999: http://www.sammobile.com/firmwares/database/SGH-T999/
audit13 said:
The latest custom ROMs require the latest bootloader and modem to function properly so the phone probably needs an update. Once the phone is running a 4.3 or higher bootloader means the bootloader cannot be downgraded in the future.
I don't see the LJC firmware for the T999L: http://www.sammobile.com/firmwares/database/SGH-T999L/
I see LJC for teh T999: http://www.sammobile.com/firmwares/database/SGH-T999/
Click to expand...
Click to collapse
Yeah, I'm thinking the phone is a T999, not a T999L. In my best estimation, the motherboard was swapped to a T999L case/screen. The sticker shows T-999L, the phone reports T-999. Additionally, under settings, the IMEI differs from the IMEI reported on the sticker. (Neither He, nor I was the original owner of the phone... so who knows it's history... For all I know, I really am working with a T-999L and someone flashed a different IMEI (worst case scenario I guess).
Is there any way to know for absolute sure? and should I go ahead and just flash 4.3? is there any downside to doing it other than that the boot loader can't be rolled back afterwards?
Personally, I would go by the model # shown with the phone in download mode.
Did it ever detect a sim card after unlocking restoring to stock?
It detected a sim when we got it (on 4.1.2), it detected a sim when i downgraded to 4.1.1, it detected a sim when i unlocked the sim, it did not detect a sim after flashing CM13, it did not detect a sim on SlimKat, and now it does not detect a sim after 4.1.1 (flashed via Odin) (LJC) and Download mode shows T-999 (NOT T-999L).
audit13 said:
Personally, I would go by the model # shown with the phone in download mode.
Did it ever detect a sim card after unlocking restoring to stock?
Click to expand...
Click to collapse
The 4.1.1 firmware came from sammobile? The baseband under settings is also LJC?
audit13 said:
The 4.1.1 firmware came from sammobile? The baseband under settings is also LJC?
Click to expand...
Click to collapse
Correct and correct.
This is bizarre because I don't understand why it would suddenly stop working. Did it say SGH-T999 on the download screen before flashing to 4.1.1?
I assume the stock ROM boots without issue?
Also try this: download and install the Samsung Phone Info from the play store to confirm the bootloader and baseband currently on the phone.
When flashing from a custom ROM to stock 4.1.1, did you perform a factory wipe?
audit13 said:
This is bizarre because I don't understand why it would suddenly stop working. Did it say SGH-T999 on the download screen before flashing to 4.1.1?
I assume the stock ROM boots without issue?
Also try this: download and install the Samsung Phone Info from the play store to confirm the bootloader and baseband currently on the phone.
When flashing from a custom ROM to stock 4.1.1, did you perform a factory wipe?
Click to expand...
Click to collapse
Stock rom boots without issue...
Yes i did a factory wipe between flashes. (Although, first flash of CM13 I did not, it ran weird, i rebooted, factory reset, flashed again then it worked fine minus the sim card issue).
Phone Info confirms SGH-T999, type: d2tmo
Boot loader: T999UVDLJC, Baseband: T999UVDLJC
Not sure what else to suggest other than reflashing the LJC ROM and performing a factory wipe from stock recovery before the phone's first boot of LJC.
audit13 said:
Not sure what else to suggest other than reflashing the LJC ROM and performing a factory wipe from stock recovery before the phone's first boot of LJC.
Click to expand...
Click to collapse
Nope...no go.
Hmm, I'm out of suggestions because you did everything I would do other than either flashing the latest stock 4.3 since the phone is now sim unlocked or running OTA updates. on a stock ROM.
The sim card in the phone works properly in another phone? Is it possible the sim reader was damaged in some manner? I know it can happen when using micro/nano sim card adapters.
audit13 said:
Hmm, I'm out of suggestions because you did everything I would do other than either flashing the latest stock 4.3 since the phone is now sim unlocked or running OTA updates. on a stock ROM.
The sim card in the phone works properly in another phone? Is it possible the sim reader was damaged in some manner? I know it can happen when using micro/nano sim card adapters.
Click to expand...
Click to collapse
Oh... adapters is a good suggestion. Yes, when I originally unlocked the phone, I used an adapter as my sim is a nano sim... Whats the damage look like? and is it fixable? I'm assuming just bent pins?
Is flashing an LTE Rom a possible solution? or is that a hard brick result?
You could try flashing TWRP and an older build of CM that will work with a 4.1.1 bootloader and modem just to see if the sim card is detected.
The metal housing on top of the sim pins is difficult to remove so it may be easier to just buy a replacement sim/sd card reader.
audit13 said:
You could try flashing TWRP and an older build of CM that will work with a 4.1.1 bootloader and modem just to see if the sim card is detected.
The metal housing on top of the sim pins is difficult to remove so it may be easier to just buy a replacement sim/sd card reader.
Click to expand...
Click to collapse
The posts aren't real specific... do you know which CM is 4.1.1 friendly?
I would try the latest cm10 or cm10.1.
https://download.cyanogenmod.org/?device=d2tmo&type=snapshot
dang you rock @audit13. as always :thumbup: , aint enuff. happy good new year for you and yours sir.
"all i can really do is stay out of my own way and let the will of heaven be done"
Any luck getting the phone to recognize the sim card?
@mrrocketdog, thanks
audit13 said:
Any luck getting the phone to recognize the sim card?
@mrrocketdog, thanks
Click to expand...
Click to collapse
Sorry for the delayed response... Yes, I finally got it to recognize (last night) ordered a new sim card tray.. interesting way to mount it by the way...
Anyway, seems as if the guess at the adapter damaging the original was correct... new one seems to be good to go.