yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] epiquiem:
I'm using the MJB set, which shipped with the 4.3 OTA for stock users. I've been on multiple ROMs and android versions from CM11 to a month of 5.0.x unofficials. I'm currently on the latest CM11 nightly. No issues, still.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scar.schemz@gmail.com:
Aaa
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bnook:
Hey, I'm hoping for some help.

I am using the Galaxy S3 i747 from AT&T, unlocked, to use on Tmobile network using their sim. I recently upgraded to LG G3 so am giving this S3 to my girlfriend. But, I can't get the cellular data to work. It's driving me absolutely nuts! already spent hours on it.

Currently what I have is:

--Bootloader: I747UCUEMJB

--Baseband: I747UCUEMJB

this is running on Cyanogenmod 11 M9 snapshot, using the kernel 3.4.101-BMS-AOSP

I have tried installing every single modem listed here on the first page, the only one that even picks up a signal is this JB option. I tried using lean kernel instead of BMS and still had the problem.

What is interesting is the other day I originally put this all back to stock firmware to put in the Tmobile card using this http://galaxys3root.com/att-galaxy-...-for-att-galaxy-s3-sgh-i747-stock-rooted-rom/ and the Ktoonsez kernel. The data didn't work initially but when I edited the APN it did. Now I can't get anything to work, pulling my hair out in frustration haha.

Any suggestions? Am I using a 4.3 or 4.4 bootloader here? I see other potential modems like here (http://xdaforums.com/galaxy-s3-att/general/modem-4-4-2-modems-i747-i747m-t2856577) that I thought about trying, but the hard-brick warning regarding incompatibile bootloaders scares me.

Currently with the setup it sends sms and calls just fine, but no mms and no data connectivity. Gah!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Before doing anything else I would verify bootloader and modem versions. There is a "Samsung Info" app in the PlayStore, or you can do this from a terminal emulator:

getprop ro.bootloader

getprop | grep version.baseband

Once sure of the versions, it will be safer to proceed.

Also, somewhere around CM11 M9 or M10 the NE4 firmware, along with modem, became necessary.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bnook:
Hey thanks for the quick reply!

Yes, I saw that app in a prior post and that is what I used to pull out the info for the bootloader and baseband I currently have installed :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Okay, it wasn't clear to me if the MJB/MJB pair was before or after you reverted to stock 4.4.2.

As long as you are sure you are on that combo, I would suggest updating to NE4 firmware and modem if you are wanting CM11 newer builds or derivatives, or comparable AOSP roms. The same would apply for Lollipop roms, except there is the chance you would need to go all of the way to NJ1 firmware and modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bnook:
OK cool, so the NE4 at the top of the list (http://xdaforums.com/galaxy-s3-att/general/modem-4-4-2-modems-i747-i747m-t2856577) is what you are recommending, if I mean to stay with some of the stable CM11 snapshots for the time being?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Use the link in this thread: http://xdaforums.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654 It has both firmware and modem. The link you posted is only the modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ntbergeron:
i747M issue

I have an interesting situation here. I bought an S3 I747M from CL for dirt cheap.

The guy I bought it from flashed it with CM11 D2LTE and he said it was working fine and then he got a notification about updates. Ran the updates and after that, couldn't connect to the carrier (Rogers) or WiFi.

Not sure if they were CM updates or Rogers. Said he did a factory wipe/reset twice and nothing fixed it. The phone does boot but as advertised, no carrier / no wifi.

I can get into TWRP but there are no backups to restore from. I can also get to download mode.

I guess I'm wondering what the best way to bring this back to life is. Can I flash it back to stock rom? Can I flash to a different CM? Will flashing modem update solve this problem?

I would like to sim unlock as well using Daveenjay's? method if it works.

Any ideas/thoughts are greatly appreciated.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
The first thing would be to determine the bootloader and modem versions that are installed on the phone. This will determine what ROMs you can install, of either the custom or stock variety. You can do this from Terminal Emulator. If it is not present in the app drawer you are not out of luck. It is built into TWRP. Enter these two commands

getprop ro.bootloader

getprop | grep version.baseband

Another way to determine the bootloader and modem versions would be to install the "Samsung Info" app from the PlayStore and run it.

Let us know which versions are on the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ntbergeron:
Thanks dawgdoc! I copied the 'samsung info' .apk to the phone and installed. It shows bootloader & baseband as I747MVLUEMK5.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Those are from an Android 4.3 version. You could download that version of the stock ROM from sammoblie.com and flash it with Odin, or Heimdall if you are running Mac or Linux. If that gets things working then consider what ROM and firmware upgrades you desire.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Stay on MK5. I am running 5.0.2 on MK5 bootloader and modem just fine!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
To fix your connection issues you could, at this point, try three things. In order of the least change to your system:

1) Check APNs and reset if necessary.

2) Reflash CM11

3) Reflash to stock ROM corresponding to your current, MK5, bootloader and modem.

Your mileage will vary with CM11 on MK5. I have seen plenty of reports of people loosing wifi, bluetooth, data after early 4th quarter 2014 if they did not update to 4.4.x bootloaders and modem.

I would guess you are not loosing any personal data and media if you reflash CM11 or stock since you recently obtained this phone. You will loose some time going through the process.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ntbergeron:
I re-flashed CM11 and network/wifi are working again. YAY!! Thanks for your help.

Do any of these 'free' sim unlock methods work? or am I wasting time?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Not since the device is on the official 4.3 bootloader and modem.

You must be on the 4.1.1 modem to do the free unlocks. BUT once you are on the official 4.3 bootloader and modem you can not downgrade without bricking the phone. Sorry.

-------

edit: true for the i747, I've read multiple comments that it is also true for the i747M

--------

glad to see I was of service
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScottBVancouver:
Likely virus in most recent modem firmware

This file downloads as type .zip.exe. Caveat emptor. Six AV programs report it as having a virus. If you down load it, send it to VirusTotal - I can't provide the link without having 10 prior posts...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Thanks for picking up this thread, and for organizing it. Awesome!

Can you add some information to the list of firmware versions? Currently, you display the firmware in this format:

Version: Download Link - Build Date

Could you add some information to your format as follows:

Version: Download Link - Build Date - Min. Android Version - Min. Bootloader Version

Min. Android Version would be the oldest version of Android that will run with that modem. This info doesn't seem well documented anywhere. For instance, one page back, someone said "somewhere around CM11 M9 or M10 the NE4 firmware, along with modem, became necessary", and then "for Lollipop roms, there is the chance you would need to go all of the way to NJ1 firmware and modem". The problem with that info is that it seems incorrect. I am running Lollipop 5.0.2 with MK5 bootloader and modem. Very confusing.

Min. Bootloader Version would be the oldest version of the bootloader that will run with that modem. As I understand it, there is some relation between bootloader version and modem version, but I can't seem to find a comprehensive list or explanation anywhere. Some seem to say that the modem must be the same version as the bootloader. If so, then that's easy, and maybe this item wouldn't be necessary, but maybe just a note somewhere stating this fact. But I have also read that that isn't necessarily the case. I have seen many people reporting using mixed bootloader/modem versions.

Lastly, would you be able to provide flashable zips of the bootloaders as well. It would be truly awesome to have all of these files and this information in one spot!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Sounds like you're clicking on an ad, already had a virus, or have something else wrong on your side. These links are to ZIP files hosted on Dev-Host. Click the big blue "Download Now" button on the download page. I've verified all the files myself.

I already have the bootloaders (up until I retired my S3) listed in the bootloader thread (little "BL" in the bottom right of my sig ;)) and unfortunately will not be updating any of my S3-related threads. Mostly because I don't use an S3 anymore and don't think I should be giving out unverified modems and bootloaders. If someone would like to take over these duties, please PM me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanKNugs:
Flashed MJB file and now cell/data no longer works. Prior to that I was NE4 and my data connection was sporadic at best. Phone boots, can use wifi, but baseband is now unknown. Downloaded Samsung Info IMEI is blank. What can I do to fix this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
MJB came before NE4, just download & reflash NE4, your lucky you didn't hard brick it. You need to download & flash NE4 boot loader & modem.zip, if you want the latest one its NJ1 but you'll need to get back to NE4 before flashing NJ1 don't skip versions & the correct order is MJB, NE4, NJ1. You can find bootloader & modem combo for NE4 & NJ1 in emewman17's thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanKNugs:
http://xdaforums.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654

I found this page and tried to install the MJB file but I get an error message when I try to. Lots of assert failed: getprop("ro.bootloader") == and a list of what seems to be modem names. Not sure what to do from here? Any advice?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
It would be best if you didn't try to flash MJB anymore, as canodroid15 said you could end up hard bricking your phone. You need to flash the NE4 borrower/modem pair. You can use the NE4 for from the thread you linked, but don't flash MJB anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanKNugs:
Thank you for the advice. I flashed the NE4 modem/bootloader and all is good now. Is it worth upgrading to the newest one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Fwiw I upgraded to nj1 because of the finicky LTE signal reception, afterwards my LTE signal did get better but if you're not having any issues NE4 is fine, just remember to flash the bootloader & modem pair, they must match & don't try to downgrade?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DorkyDev:
Is there any newer modems, I thought ne4 was the latest?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
NJ1 is newer. I flashed them from the zip in this thread.

Enewman has the bootloader and modem bundled together in one zip. No risk of getting out of sync that way, since they must match as mentioned above.

Be sure to upgrade sequentially if you're not already on NE4, and never try to downgrade.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DorkyDev:
My problem sort of is my girl is on the new S3Rx and said it's not connecting, I thought she was on NE4 would having her reflash in recovery UCUEMJB_to_UCUFNE4_Firmware_update.zip or d2att_I747UCUFNE4_bootloader_modem_4.4.2.zip fix the connectivity issue? I checked the esn and it's clean, she's using prepaid at&t go phone account and sim card? She accidentally did a factory reset from within the phone/rom and ran into google play issues "can't connect to servers" I told her that's probably because the factory reset messed it and you're supposed to do it from recovery and taught her the basic's of twrp recovery.

So can she be on NJ1 and still use rom's like S3Rx and TMS3KK etc?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Before mucking with firmware make sure you're using the right APN. For a Go Phone I think you want to be on the AT&T Phone / Phone APN. The factory reset probably kicked you back to the default and that might be AT&T PTA, which I'm not certain will work with that plan.

Be very, very careful flashing bootloaders and modems on this phone. Keep them matched, and never try to downgrade - can't say that enough. Make sure you know for certain exactly what you have installed before proceeding. Either use the Samsung phone info app or enter this in a terminal app or adb shell:

getprop ro.bootloader
getprop gsm.version.baseband

NJ1 might work if those ROMs have the right libs and binaries built-in for NJ1. I wouldn't doubt it if NJ1 is supported, but I'm not sure (I stick with AOSP based ROMs). Best bet is to search the threads for those ROMs and see what you turn up; ask in those threads if it hasn't been posted on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Yes, she can.

There are sometimes troubles flashing the older ROMs when you are on the newer bootloaders, but these can be overcome. What is happening is that the updater-script for the ROMs are written to accept bootloaders released up to that time. If the dev is not keeping the ROM current you will get an error when flashing. This can be worked around by editing that same updater-script to accept the newer bootloader. This applies to TW based ROMs like S3Rx and TMS3KK as well as CM/AOSP based ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guardian715:
No SIM card?

I have been reading xda for a while but i have a very unique issue here. I originally had the issue of having no mobile data, but being able to call and text and such. After reading a few they said come here and install the modem firmware... so I was like cool ok... but none of them worked... And now my phone will not detect the sim card. Under any mobile data options, it says that there is no sim card inserted. I tried flashing other custom roms but no success. I also tried odin flashing the 4.3 stock rom, but no success there either. I followed all instructions to the letter and it seems no one has this issue. Can anyone help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Before flashing or installing any more ROMs or modems, what bootloader and modem are currently on your phone. Either use an app, such as Phone Info - Samsung by vndnguyen from Playstore, or Terminal Emulator commands to determine the version numbers. The terminal commands are

getprop ro.bootloader
getprop | grep version.baseband
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guardian715:
Bootloader I747UCUFNE4

Modem is blank.

What does that mean?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Do not flash anything else containing less than an NE4 bootloader and modem. You could end up with a hard bricked device.

The modem probably was borked when you tried to flash the 4.3 rom with Odin.

Since you have the NE4 bootloader, I take it that you have an AT&T i747 and not an i747M from Canada. You can probably fix your woes by flashing the NE4 bootloader and modem as a pair. You can find a link to the NE4 bootloader and modem in this thread by enewman http://xdaforums.com/showthread.php?t=2789917

You could also reflash the full stock NE4 ROM from his directions in that thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guardian715:
Ok I will try that, but just so you know... the modem was messed up after installing the modem firmware from this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guardian715:
I began following the tutorial, but it bricked my phone. I now have QHSUSB_DLOAD in my device manager. Any way to fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Yes, flashing a MJB modem to an i747 with an NE4 bootloader will cause a device to brick.

I don't have a link handy, but it sounds like you need to use a debrick image on an external sdcard. If you can't find the tread in the sub-forums, development I think, [MENTION=5511100]mrrocketdog[/MENTION] may be able to provide it. Use an image based on the same bootloader as is on your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guardian715:
I have restored the phone. So now that I have, what did I do wrong?

EDIT: I finally fixed the issue. Once you told me that I had the NE4 bootloader and directed me to that thread, I google searched for NE4 modem and found it on another thread here on XDA. I booted into CWM recovery and flashed that modem and all is well. SIM card reads and shows data and all that. For anyone with the issue. Thanks! I truly appreciate you all!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
yay!!!!! good to hear. i think this is the debrick thread.

http://xdaforums.com/showthread.php?t=2549068

"all i can really do , is stay out of my own way and let the will of heaven be done"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Glad to hear you fixed your phone.

---------- Post added at 10:53 PM ---------- Previous post was at 10:53 PM ----------

I subscribed to that thread so that I now have it as a reference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jodybnd:
I747mvlufob1

Looking for this modem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I have only seen mention of it coming the the Sammobile download for the full stock rom. I guess you could always download the stock rom and extract the modem. I don't know if there are any precautions to observe when you do that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jodybnd:
Thanks for the reply. I downloaded the stock rom from sammobile and tried to flash it with Odin and got a fail. Might have been a bad dl. Trying to return my phone to stock because I flashed a new modem and have no service now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iamfarhan007:
at&t SGH-I747UD 16 GB model modem

Hello

i have an at&t SGH-I747UD 16 GB model iv tried all the mentioned modems here http://xdaforums.com/showthread.php?t=1831898

i have updated even to cynogenmod 12 but sill no signal in FRANCE . can anyone help iv been stuck for ages

Thanks

Farhan
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Use either Phone Info - Samsung app from the Playstore or commands in Terminal Emulator to double check both the modem (baseband) and bootloader and then post here the results.

Terminal Emulator commands are:

getprop ro.bootloader
getprop | grep version.baseband

It is possible your problem may relate to mismatched bootloader and modem. If so, not having a signal is the better of possible outcomes. If they are mismatched after reaching the 4.4.2 modem you risk bricking your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] a-raccoon:
If I'm not having any problems with my modem, should I risk bricking my phone to upgrade it? Are there any gains for someone who isn't experiencing trouble? Are there any Security / privacy improvements? Backdoors have been removed?

I'm still using stock 4.0.4 ICS that came with the phone nearly 3 years ago. AT&T carrier. I'm putting everything together to upgrade to CM 12.1 (if possible) and stumbled across this thread, too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I would say for someone not experiencing any problems with there current setup, and not planning to upgrade Android versions there is not much of a reason to change modem or bootloader. With your intention to up your device to CM12 you will need to upgrade bootloader and modern. Most reports say you need to go to 4.4.2. For the i747 that is NE4 at a minimum, NF1 would be the most current.

If you are on a stock rom the simplest way may be to take OTA updates until you are at NE4 because this should take care of any partitioning changes that have occurred as Android updated. You can change you system date and time to avoid the 24 your wait between OTAs. I would recommend doing the free carrier unlock, found in these forums, when you are at stock 4.1.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] a-raccoon:
It seems when I rooted my phone 2+ years ago, it prevented OTA updates from happening. Even now if I click About > Update, nothing happens. How should I proceed from here, then?

Looking at your list of files, the most current for my phone would be I747UCUEMJB: modem_CWM_I747UCUEMJB.zip - 19.15 MB - October 11, 2013 ... is that NF1? Would I just flash that modem, then go straight to flashing CM12.1 + gapps? Or not quite so direct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
You can get back to stock by flashing the 4.1.1 Jellybean version using Odin. The file can be found at sammobile.com. This was the last complete stock room from AT&T. Everything since has been incremental OTA updates.

For the i747 the official ROMs since you're have been:

4.1.1 JB = LK?

4.1.2 JB = MG2

4.3 JB = MJB

4.4.2 KK = NE4

4.4.2 KK = NF1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
You really are going to need to do incremental flashes. You can not make that jump in one flash. The phone won't boot I don't think. I'm looking for an old tar and read your post... wow, I didn't realize so many ppl used the S3 still! That's awesome. I loved mine while I still used it. I can't believe you're on ICS... I'm not positive, but I read a long time ago ppl had boot loops trying to go 4.0.4 to 4.2 even. Okay, I'm going to try to hunt down a bootloader now. If you happen to have a bootloader tar give me a yell... Need it from 4.1.1 JB for S3. Carrier is not specific on that. Ty

---------- Post added at 07:58 AM ---------- Previous post was at 07:55 AM ----------

Lol replied to wrong post... I'm half asleep, but had a flash of, hopefully, genius as I slept. Sry, I'll fix it in the morning on PC.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kwijybow:
Does anyone have a download link to I747MVLUFOB1 modem firmware? I am currently running this firmware and would like to have a backup of the firmware before I flash one of these other firmwares.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
If no one has a link for the file you want, you could always download the full ROM and firmware from sammobile and then extract the bits you want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kwijybow:
Sounds like a good plan but I don't know how to do that. I tried to extract the modem firmware from my device directly, however the file that was created was no where near the same size as all the other firmwares on the download page of this thread so it makes me unsure if I did it properly. Would you mind either showing me how to extract the firmware or maybe just do it for me? Would be greatly appreciated either way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I've done this, but it has been awhile.

Unzip the download from sammobile. You should have a file with the Rom.Name.tar.md5. Remove the .md5 from the end of the file name. View the resulting tar archive in your archive manager of choice. In the older stock ROM I have on hand for the SGS3 the modem file is named NON_HLOS.bin. In the ROM of my older SGS Captivate the modem file is named modem.bin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kwijybow:
Thanks for that. I found the file and injected it into a zip made for a simular modem file. The sizes match now, which is good. My only other question is can I flash the zip with twrp or do I have to use CWM? Do they both flash the same?