Related
I recently tried to update my CM rom to a snapshot rom and then when I did that, it failed to update and then all the other nightly updates i wanted to update after that all failed. Yesterday, I read on the forums that I can just update my bootloader and it will update my rom again. I did that and my rom updated fine. But after I updated everything, I saw that my baseband version it said unknown and my phone #, IMEI, IMIE SV were all unknown as well. My mobile network state said disconnected and so I have no service. Is there any way I can fix this?
Thanks
Did you flash a new modem to go with the updated bootloader?
No, where can I find it for my phone? Mine is samsung galaxy s3 i747m.
ptexp said:
No, where can I find it for my phone? Mine is samsung galaxy s3 i747m.
Click to expand...
Click to collapse
Never mind I got the modem. Gonna try it now.
Works now. Thanks.
ptexp said:
Never mind I got the modem. Gonna try it now.
Works now. Thanks.
Click to expand...
Click to collapse
Glad you got it working. If you flashed a 4.3 bootloader, do not attempt to downgrade the bootloader because it will brick your phone.
I love this community. This post saved my butt this morning. You guys rule.
Hey guys. I just got a galaxy s3 from virgin mobile SPH-L710 last week and I managed to install cyanogenmod 11 m10 on it. But to go to cm11 m11 asI've recently learned needs the latest bootloader and baseband.
I know there's two threads in the development section on how to get the latest stock nd8 update.
One had a link to download and open in Odin however the link doesn't seem to be good anymore.
The second thread is for the Odin one click full restore but when I run it it fails on aboot.nbm. I've tried using different USB cables too but it doesn't seem to do any good. Any ideads on how else to upgrade?
I can assure you this is false. I have a Virgin Mobile SPH-L710 on baseband MK5 and I am running a nightly build that is newer than M11 and have no issues.
You should be fine with a dirty flash over M10. Just wipe the cache before flashing.
OK that's intriguing. How did you get MK5 baseband? I just got my s3 last week and its on NF4 which I have no idea where that is in relation to any of the others i've seen around.
I've used the cm updator in settings to try one of the m11 nightlys earlier last week but I had no service so I restored a recovery of m10. Would performing a dirty flash of a nightly build be any different?
Erunur said:
OK that's intriguing. How did you get MK5 baseband? I just got my s3 last week and its on NF4 which I have no idea where that is in relation to any of the others i've seen around.
I've used the cm updator in settings to try one of the m11 nightlys earlier last week but I had no service so I restored a recovery of m10. Would performing a dirty flash of a nightly build be any different?
Click to expand...
Click to collapse
My phone came with MK5 on it, when the phones were shipping with 4.3 installed.
To be honest with you, I would disregard the modem/baseband concerns altogether if I were you. These phones do come with KNOX on them and flashing bootloaders and modems is seriously a huge risk. Flashing a bootloader older than the one you are currently on will trip the killswitch and you will have an irreparable hard brick.
The only time I could possibly think considerations with the bootloader would need to be made is if you were looking to flash a rooted stock TouchWIZ ROM that needed newer bootloaders/modems. But, I really can't speak to that, as I am trying to avoid TouchWIZ and am only familiar with AOSP ROMs.
You may need to flash an APN fix in addition to the ROM and GAPPs. I also use @decimalman's custom kernel, the DKP kernel and have no issues. Basically, when I am clean flashing nightlies the order goes like this:
In PhilZ Recovery found here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
ROM
GAPPs
Kernel
APN fix
Re-Root system for SuperSU
Reboot
I sent you the link for the APN fix, available in another active VM S3 forum, in your inbox. Download and flash the zip and that should fix any service-related issues you're having.
OK I did a clean flash of the latest nightly, flashed the apn fix then booted. Still no service. No apn are on the device nor is it able to save any I manually put in. And settings shows the baseband version as unknown as well as anything else that has to do with cell service.
Erunur said:
OK I did a clean flash of the latest nightly, flashed the apn fix then booted. Still no service. No apn are on the device nor is it able to save any I manually put in. And settings shows the baseband version as unknown as well as anything else that has to do with cell service.
Click to expand...
Click to collapse
And, you tried flashing all of those with the lateat version of PhilZ recovery?
Yes. I tried it with the latest version of philz and flashed all the zips you had listed in order but still the same old issues. However I noticed that WiFi still works. I can also go back to M10 and have no service issues. The other thing im noticing is that CyanogenMod thinks this is a SPH-L710 but apperently its really a SPH-L710T. The difference being that my phone has a tri-band radio for something to do with Sprints Spark.
Erunur said:
Yes. I tried it with the latest version of philz and flashed all the zips you had listed in order but still the same old issues. However I noticed that WiFi still works. I can also go back to M10 and have no service issues. The other thing im noticing is that CyanogenMod thinks this is a SPH-L710 but apperently its really a SPH-L710T. The difference being that my phone has a tri-band radio for something to do with Sprints Spark.
Click to expand...
Click to collapse
When you're on M11, have you checked in system root --> /etc folder to see if the apns-conf.xml is there? You might tru copying that over from the M10 build.
In the meantime, I'll look into the modem a bit more. The CM forum users all seemed to agree on that as a fix.
I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.
SubArctic said:
I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.
Click to expand...
Click to collapse
Visit this thread but don't flash anything else until you have read and asked for help there . Post there and explain your situation and even private message the op if you need to . http://forum.xda-developers.com/showthread.php?t=2363882
I would just be extremely careful with this. Do you make a nandroid backup before flashing? I would restore that or a previous one first. That will probably fix your problem.
Have you tried to flash one of the Unified CM 11 Zips? Those are kind of universal installer, see if that will fix your problem. http://download.cyanogenmod.org/?device=d2lte Download this and make sure you wipe everything a few times. Then install the zip.
People on here bricked devices by downgrading to certain modems/basebands after flasher a newer one. It seems like you have a newer modem, so I wouldn't try it. If you can still get into download mode, I would flash the latest tar for your device. I'm pretty sure it is an AT&T device or close variant.
Search this http://forum.xda-developers.com/galaxy-s3-att
SuperGoober said:
Visit this thread but don't flash anything else until you have read and asked for help there . Post there and explain your situation and even private message the op if you need to . http://forum.xda-developers.com/showthread.php?t=2363882
Click to expand...
Click to collapse
SubArctic said:
I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.
Click to expand...
Click to collapse
lvpre said:
I would just be extremely careful with this. Do you make a nandroid backup before flashing? I would restore that or a previous one first. That will probably fix your problem.
Have you tried to flash one of the Unified CM 11 Zips? Those are kind of universal installer, see if that will fix your problem. http://download.cyanogenmod.org/?device=d2lte Download this and make sure you wipe everything a few times. Then install the zip.
People on here bricked devices by downgrading to certain modems/basebands after flasher a newer one. It seems like you have a newer modem, so I wouldn't try it. If you can still get into download mode, I would flash the latest tar for your device. I'm pretty sure it is an AT&T device or close variant.
Search this http://forum.xda-developers.com/galaxy-s3-att
Click to expand...
Click to collapse
Thanks it worked.
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.
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.