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.
Hello all,
So, I've been doing some reading in regards to some problems I ran into when installing KK on my device (even though it's currently running CM11 nightly without any noticeable issues ) and I noticed that my device has something that for my understanding should not have worked: I'm still on the I747MVLDLK4 bootloader and was able of getting the latest CM11 nightly running without issues on the device.
Granted that the device's modem is updated to the latest version, but for what I've read that it should have never boot up onto any KK ROM. I've been able of getting SlimKat, AOKP and CM11 running on it, even though CM11 was the only one that didn't give me any FC's or any unwanted behavior. I must admit that getting any of these ROM installed required quite a bit of messing around in TWRP and had to do complete wipes between installing versions, but still, it worked. I also had JB 4.3 installed ( AOKP ) since around October/2013 and upgraded to KK about 1 month ago.
I have a couple of questions in regards to this:
- If the KK ROM's are not supposed to boot up on such an old bootloader, what did I do that would've overrun this?
- Since I'm still on I747MVLDLK4 bootloader, would I be able of downgrading to 4.1.1? ( I want to perform the device unlock for free, which only is available on that version)
I've added screenshots of the bootloader info on the console emulator and the system info...
Thanks in advance!
The 4.3 requirement is only for touchwiz kk roms.
So I managed to hardbrick my phone in an attempt to flash a camera fix for lollipop on S3. I used the ROM from here:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-unofficial-cm12-lollipop-t2953040
It installed perfectly, and everything worked fine except for the camera. So I used my phone a bit and then later decided to put in the camera fix, so I found this video:
https://www.youtube.com/watch?v=U8obKmPrAh4
And ended up flashing the zip to on my phone through twrp. Flashing it caused my phone to hardbrick (it was meant for i9300 I think). I am unable to go into recovery or download. I just want to know if those 16GB microsd card with the debrick image fixes will work for me? What image am I suppose to download for those fixes? 4.4.2? 4.4.4?
My model is SGH-1747M
SubArctic said:
So I managed to hardbrick my phone in an attempt to flash a camera fix for lollipop on S3. I used the ROM from here:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-unofficial-cm12-lollipop-t2953040
It installed perfectly, and everything worked fine except for the camera. So I used my phone a bit and then later decided to put in the camera fix, so I found this video:
https://www.youtube.com/watch?v=U8obKmPrAh4
And ended up flashing the zip to on my phone through twrp. Flashing it caused my phone to hardbrick (it was meant for i9300 I think). I am unable to go into recovery or download. I just want to know if those 16GB microsd card with the debrick image fixes will work for me? What image am I suppose to download for those fixes? 4.4.2? 4.4.4?
My model is SGH-1747M
Click to expand...
Click to collapse
Try a debrick image based on the same bootloader/modem version as was last running properly on your phone. Note that you may have to try several sdcards; just the way it is, a specific card may or may not work. Use either 16 or 32Gb cards if your internal storage is 16Gb, as are the AT&T i747 devices. If your i747M has 32 Gb of internal storage (not sure that any do) only use the 32 Gb cards.
dawgdoc said:
Try a debrick image based on the same bootloader/modem version as was last running properly on your phone. Note that you may have to try several sdcards; just the way it is, a specific card may or may not work. Use either 16 or 32Gb cards if your internal storage is 16Gb, as are the AT&T i747 devices. If your i747M has 32 Gb of internal storage (not sure that any do) only use the 32 Gb cards.
Click to expand...
Click to collapse
I get that, but that is not exactly what I'm asking. From the first link I posted, I said that is the ROM I had last installed. Based on that, what debrick image am I suppose to get? Because the ROM I have installed is "cm-12-20150219-UNOFFICIAL-d2spr.zip". How do I get a debrick image based off of that? Or am I looking at this wrong? Is the bootloader/modem version different from the ROM? If so, how do I get the bootloader/modem version? The version of Android I had before installing the ROM was 4.4.2, would my bootloader/modem be that?
SubArctic said:
I get that, but that is not exactly what I'm asking. From the first link I posted, I said that is the ROM I had last installed. Based on that, what debrick image am I suppose to get? Because the ROM I have installed is "cm-12-20150219-UNOFFICIAL-d2spr.zip". How do I get a debrick image based off of that? Or am I looking at this wrong? Is the bootloader/modem version different from the ROM? If so, how do I get the bootloader/modem version? The version of Android I had before installing the ROM was 4.4.2, would my bootloader/modem be that?
Click to expand...
Click to collapse
Your bootloader/modem might possibly be 4.4.2.
I haven't seen any custom ROMs on XDA which change your bootloader and modem. The ROMs leave your device running what was present prior to you flashing the ROM. Admittedly I have only checked for the devices I have, a Samsung GalaxyS and an SGS3, both on AT&T. I doubt that the Sprint SGS3 forums are any different regarding the custom ROMs and installation of bootloaders.
The only ROMs I have seen here which do install bootloaders and modems are some of the stock ROMs derived from system dumps of OTA updates.
You don't necessarily need the latest bootloaders and modems to run current custom ROMs. There are many KitKat ROMs that run perfectly well on JellyBean bootloaders as long as you have custom kernels. All of the Lollipop ROMs in this forum are running on KitKat or JellyBean bootloaders. This is because AT&T has not released a LP bootloader. In the forums for the Captivate, my 1st gen SGS, there are Lollipop ROMs running on Gingerbread bootloaders, because GB was the last bootloader released for that device.
I threw all of that out there because it is possible you are still running Jellybean bootloaders if you have been on custom ROMs since receiving your device and have not intentionally flashed an up to date bootloader and modem combo. So, if you know what bootloader you are on flash a debrick image based on that bootloader.
If you do not know what bootloader is on your device, then flash a debrick image based on a 4.4.4 ROM from your device forum (Sprint). If the image you pick is newer than your installed bootloader version, the image should not work. In that case try a 4.4.2 image, and then if necessary a 4.3 image. The troublesome part about this method is that the image may not be working becuase it is based on the wrong firmware or simply because your device doesn't like the image flashed on the micro sdcard you happen to be using, at least that is what I read in the i747 forums. That boils down to suggesting that you try the 4.4.4 image on several cards before changing to the 4.4.2 image.
dawgdoc said:
Your bootloader/modem might possibly be 4.4.2.
I haven't seen any custom ROMs on XDA which change your bootloader and modem. The ROMs leave your device running what was present prior to you flashing the ROM. Admittedly I have only checked for the devices I have, a Samsung GalaxyS and an SGS3, both on AT&T. I doubt that the Sprint SGS3 forums are any different regarding the custom ROMs and installation of bootloaders.
The only ROMs I have seen here which do install bootloaders and modems are some of the stock ROMs derived from system dumps of OTA updates.
You don't necessarily need the latest bootloaders and modems to run current custom ROMs. There are many KitKat ROMs that run perfectly well on JellyBean bootloaders as long as you have custom kernels. All of the Lollipop ROMs in this forum are running on KitKat or JellyBean bootloaders. This is because AT&T has not released a LP bootloader. In the forums for the Captivate, my 1st gen SGS, there are Lollipop ROMs running on Gingerbread bootloaders, because GB was the last bootloader released for that device.
I threw all of that out there because it is possible you are still running Jellybean bootloaders if you have been on custom ROMs since receiving your device and have not intentionally flashed an up to date bootloader and modem combo. So, if you know what bootloader you are on flash a debrick image based on that bootloader.
If you do not know what bootloader is on your device, then flash a debrick image based on a 4.4.4 ROM from your device forum (Sprint). If the image you pick is newer than your installed bootloader version, the image should not work. In that case try a 4.4.2 image, and then if necessary a 4.3 image. The troublesome part about this method is that the image may not be working becuase it is based on the wrong firmware or simply because your device doesn't like the image flashed on the micro sdcard you happen to be using, at least that is what I read in the i747 forums. That boils down to suggesting that you try the 4.4.4 image on several cards before changing to the 4.4.2 image.
Click to expand...
Click to collapse
Thanks for the information, I will probably do what you said and start with the 4.4.4 image and work downwards. Although I believe that my version of S3 didn't ever get 4.4.4 as a firmware, so I probably don't have a 4.4.4 bootloader, so it would be bbest to start from 4.4.2. Either way, I'm not sure if I can get multiple SD cards to try this on. I know my phone is 16GB, and thus I have gotten 16 GB 10 class card. I'm hoping it does the trick, since that is the one people are recommending the most.
SubArctic said:
Thanks for the information, I will probably do what you said and start with the 4.4.4 image and work downwards. Although I believe that my version of S3 didn't ever get 4.4.4 as a firmware, so I probably don't have a 4.4.4 bootloader, so it would be bbest to start from 4.4.2. Either way, I'm not sure if I can get multiple SD cards to try this on. I know my phone is 16GB, and thus I have gotten 16 GB 10 class card. I'm hoping it does the trick, since that is the one people are recommending the most.
Click to expand...
Click to collapse
I understand about nt having 4.4.4. The AT&T SGS3 received two 4.4.2 bootloaders, NE4 and NJ1, but nothing since. The Canadian SGS3/i747M received several of the NXx series bootloaders, I think they are all 4.4.2. I did see where that device received another bootloader/modem upgrade in the past few months. It was an upgade to OBx. I don't know if that was 4.4.4 or 5.0.x.
Using ting, sprint samsung s3 and when I install the rom I always get the "no sim detected" after boot, I thought the 5.1.1 builds would fix the issue for me but so far no luck. Has anyone found a fix for this issue yet or is it just me? So far I tried CM12.1 and AICP version 9 both with 5.1.1, Stock android worked fine, but after installing lolipop I've had these issues.
hello, it happened to me, i have a boost mobile s3 and tried to update it to octos team 5.1.1 (cm12 based if im not wrong (sorry if im mistaking the cm release)) and i have downloaded the zip for sprint by mistake, and it give me the no sim detected message, i made a backup from recovery after upgradong, got back to 4.4.2, then ive downloaded the zip for boost mobile sph-l710t (triband) and it worked. doesnt ask for sim card and cdma carrier info (im on venezuela movilnet) and it works good!
I was happily using 4.4.2 stock on my rooted SGH-i747M, however rooting it tripped the warranty bit, then I had the phone unlocked and changed carriers from Rogers to Bell and because of either of those my device is blacklisted from getting OTA updates.
I decided to try CM and was advised on the CM IRC channel to update the modem firmware first. I updated (or perhaps downgraded?) to I747MUMUEND3 per this thread (http://forum.xda-developers.com/showthread.php?t=1831898) and rebooted but found that I no longer had sound or WIFI and the SIM card wasn't detected. I tried other versions from that same thread with no luck.
I went ahead and flashed CM 12.1 nightly for D2ATT which worked well, however still no sound or SIM. WIFI works but slowly. I also tried 11.2 for D2LTE but got the same result, and flashing 10.1 for D2ATT gave me an assert error. In 12.1 I experimented with other modem firmware versions (I747MVLUEMK5, I747MUMUEND3, I747MVLUEND2) but it made no difference.
I'm not quite sure where to go from here. According to a CM12.1 debug log my boot loader is I747MVLUFNF2. Do I need to match the modem firmware version with this, and if so, where can I get this version? Would flashing stock from sammobile do it, would I lose root while doing so, and how can I get root back? I forget how I rooted it originally but soft bricked it but fixed it with chainfire.
Anything else I can try at this point? I might just be happy back on stock with cellular connectivity.
The latest modem for the i747m is FOB1. The END2 modem is about a year behind the FOB1.
The assert error occurred because d2lte or d2can ROMs are to be flashed to the i747m.
Fixed
I flashed the stock ROM that matched up with my current bootloader version. Inside the stock ROM everything worked as normal. I then installed TWRP and flashed 12.1 and everything worked in there as well.