yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kettir:
I'm seriously thinking about trying this. Just two questions, so I know I'm doing what I should be doing.

1. I need the ROM from this thread, the modem linked from this thread, and the bootloader at http://xdaforums.com/showthread.php?t=2321310 , right? Is it absolutely necessary to update the bootloader? I am coming from basic stock I747uclg1, ICS.

2. If I do update everything including including bootloader, and decide I want to go back to ICS, will I be able to successfully go back by getting the ROM, the proper modem, and the proper bootloader, and flashing them? I will have a nandroid backup of the ICS I have now, but I presume even if I flash that, I will still need to reflash the proper modem and bootloader?

Thank you for your patience.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rokonacdc:
1. Mix and match bootloaders to find what works best for you. They don't have to match from what I've been told.

2. You can can revert to ICS the way you stated. The backup will work and yes you will need to reflash old bootloader stuff if you want them, but I don't believe it's necessary to to have outdated ones, even on outdated firmware that I don't think you'll want to go back to.

3. Update and find a good ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] renn9420:
Did my wife's phone. AT&T to T-Mobile. Had to first downgrade to a 4.1.1 ROM. Luckily I was still stock so used Odin to downgrade. Then did the whole *#*#197328640# and so on. Worked like a charm. Then rooted and updated the modem then flashes Cyanogen 4.2.2 and had no issues. But because I went from AT&T to T-Mobile I did have to go to the dial pad and *#*#info#*#* and change my band from LTE to WCDMA preferred in order to get 4G or HSPA+

Phone: HTC One S Rooted / S-Off'd

ROM: Dark Jelly (Any and All!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Sounds like you did things the right way. Just an FYI, no matter what ROM you're running, you can always just boot an S3 into download mode (VolDown+Power on) to use Odin.

Also 100% accurate. You don't need to roll back to older modems or bootloaders in most situations. Stock ICS ROMs might not boot on the latest bootloader, but that's why I keep a back catalog. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] renn9420:
I downgrade so as to unlock my phone because it isn't possible to unlock with the latest update of 4.1.2 because #*#*197328640# won't have that 4th option of NV. It will only be the RAT. And since I was only on stock at the time it was simpler to downgrade with Odin in download mode and work myself back up. Then Root and install custom recovery then custom ROM.

Phone: HTC One S Rooted / S-Off'd

ROM: Dark Jelly (Any and All!)

---------- Post added at 07:50 AM ---------- Previous post was at 07:44 AM ----------

On another note: not hard to follow instructions when the OP made it simple and understandable. ;) Thank you for the easy instructions!

Phone: HTC One S Rooted / S-Off'd

ROM: Dark Jelly (Any and All!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jonscilz:
I747UCDMG2 download link?

the link for the I747UCDMG2 radio is dead. please edit or provide an updated location. thanks!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I just checked, and it's working fine. I'll make sure my Dropbox is up to date if d-h.st starts having issues again like they did a couple months ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fornoggg:
I read the instructions, especially about only using this on my own model, but I'm going to ask about this anyway.

I have a I747m model galaxy s3 on a Rogers network. I want my modem to pick up the t mobile frequency so I can bring my phone to the States and buy a temporary SIM for use when I'm over there on business. Now I know I'm not supposed to flash this modem or anything on this forum, but hear me out first.

I'm using a custom non-touch wiz Rom which has essentially blocked me from using ussd dialer codes so I can't change the frequencies my radio picks up in the DIAG menu. I don't want to flash a stock Rom every time I go to the States so I can access the ussd codes. I'm contemplating trying to flash one of the 999 modems, because it has the frequency that'll work.

Can someone suggest a workaround before I test this potentially unsafe way?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
It's more than "potentially unsafe" - it simply won't work. You must use modem firmware for the correct device, otherwise the modem will fail to initialize during boot and you'll be stuck in a boot loop.

If you need to change options within the modem using USSD codes, then you need to run a ROM that supports them. AFAIK, none of the AOSP-based ROMs do. Install the correct modem for your device as per the instructions, and switch to a ROM that has the features you need.

You will

never

be able to flash the "wrong" modem and get away with it. Your device

will not work

.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fornoggg:
Thank you for the advice. So, is there a reason why USSD codes are not supported on roms?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
It's up to ROM developers to code their Dialer apps to accept the codes and send them through as modem commands. Because Samsung doesn't release the full Touchwiz source, we don't have the information to make it work. (Not without disassembling Touchwiz entirely.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Thanks for figuring that out. I was using mvldlk4 with tasks 7-20b release with no issues. Then I upgraded to his 9-29 release (android 4.3) and my caller ID was corrupted. I flashed the mumlj1 modem (October 2012) and it fixed the jumbled caller ID bug. I do notice it's slightly harder to get lte now, but that's a trade off to have a working call display.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
I haven't had any Caller ID issues with I747UCDMG2 runnings task 9-28 rom. I did have to ODIN back to stock to get the rom to work but after that, everything has been trouble free.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
I think the caller ID issue is specific to Canadian users/devices or specifically rogers/fido users.

I think ucdmg2 is US correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
What carrier do you have? Do you actually get names with the numbers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
In Canada, Rogers and Fido offer an enhanced Call Display option, much like landline phones have, where the caller's name is displayed along with the number. This is different than the standard Call Display that the rest of us get from our carriers. AFAIK, AT&T doesn't offer this feature, so you never would've had issues in the first place.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
anyone know how I can get data working for my i747m on the new 4.3 leak using bootloaders and modems?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
You'll most likely have to wait for the 4.3 modem for our phones. Patience is a virtue lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
Recommendations for i747 Rogers? I'm using a 4.3 ROM, if that makes a difference. I usually get 2-3 bars of reception which is quite bad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HAVOK83:
Thanks for the mg2 update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Help

Hi guys hoping someone in this forum can help me, I just flashed the latest i747 modem on my i747m so I can flash the 4.3 and before rebooting decided not to go through with it so I wiped dalvik,cache, data & system and restored my nandroid. However the phone still won`t boot up. I can`t get into recovery and my computer won`t recognize it. Can someone please help me on this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
The last i747m release is what I use, with fido. It depends on your location. I get full LTE bars and will drop down to 3G even Edge in bad areas.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
With ATT releasing 4.3, will we be getting a flash for the new modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
There probably is a new one, I haven't had a chance to look yet. I'll update later today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
You rock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RockRatt:
Destruct, I am currently on the MJ2 bootloaders and ROM and made the MJBmodem.zip flashable in twrp and tested it out with no issues. I then flashed back to LK3 modem with no issues. So basically I went from Modems MJ2>MJB>LK3 with no issues. Just wanted to let you know how it worked for me. THANKS TO LOSER for giving the MJB modem.

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Thanks for being my guinea pig on this, I didn't think there'd be issues with modem versions, I'm more concerned about the bootloader. I am curious about how the newest bootloader handles the oldest modem, or vice-versa; not because I'd ever recommend that setup, but because I know

someone's

going to try it... lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hobbit19:
pls share modem+ bootloder update zip

JB 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dpwguenther:
hobbit19 +1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Canadian carriers all updated to 4.3 today. Hopefully we'll see new modems soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
https://www.mediafire.com/?c24vvn73eipadr5

Telus UEMK5 modem.

---------- Post added at 04:15 PM ---------- Previous post was at 04:11 PM ----------

No one has proven this 100% but a lot of people think that rpm.mbn is the "Resource Power Management" and it can be beneficial to update it since it may contain better power saving algorithms so here is a flashable for this as well. I tested it. too early to tell a diff, but i did dd the block and check to be sure it updated. it did so we will see.

http://www.mediafire.com/download/0gjm08m9b94o8v2/rpm_CWM_I747MVLUEMK5.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stanguay:
Can I flash this modem on 4.3 leak and on 4.1.2 rom without problem ?

I have I-747m from Telus

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Thanks! Saves me from having to revert to stock to get the OTA myself. I don't think Telus/Rogers/Bell get different modem versions, so this should be the same modem that all the I747M's get after the 4.3 OTA. It flashed fine on mine (I'm also with Telus though, so not much of a test) and I've added it to the OP. If anyone sees other versions show up after they get their 4.3 OTA, PM me and I'll walk you through ripping them for the collection.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
There was no Telus 4.3 leak. You should be able to flash this modem on any I747

M

, please make sure you've got the correct device before flashing though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
I keep my phone updated to the 'latest,' but I wonder, is there anything resembling a 'change log' that becomes available so one knows what the changes in the 'new' version are? jf
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
That's impossible, unless you know someone that works for Samsung on their modem firmware development team.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stanguay:
I used the 4.3 leak for AT&T but I have the I-747M

Thanks I will try this modem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
The RPM is flashed as part of bootloader updates; You really shouldn't be mixing and matching RPM versions. I'm also worried that upgrading to the M's 4.3 bootloader will cause the same inability to downgrade that the AT&T guys ran in to. Please, nobody flash this RPM until it's verified safe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
If this were true, people who flashed the boot loader update so CM 10.2 would boot would be having issues, i just dd'd the 4.1.2 boot loader and seemed to be fine. I am also not having issues. Other devices i have owned flashing the rpm.mbn with the modem was common practice, across any boot loders. But we could have been wrong. And it may indeed be dangerous, but i haven't had issues. On this new modem and rpm the only thing i notice is i get LTE in my office now where i didn't before.

there is more to the bricks then the bootloader i think but who knows. I am still on the 4.1.2 bootloader and dont have any plans to upgrade it.

Edit: Seems liek the guys at rootzwiki for the VZW s3 have been cross flashing the rpm's and haven't had issues yet as well. This is about the most accurate info i can find on the RPM.mbn, not that its true but... http://rootzwiki.com/topic/36114-wip-rpm-explained-updated-2212013/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I'm talking about the AT&T 4.3 OTA that came with a new bootloader version that causes bricks when people attempt to downgrade it. Nobody's figured out which specific part of the bootloader is refusing to downgrade, and if it's the RPM, then if people only update their RPM and not the bootloader itself, I'll have no way to block them from bricking their device because the bootloader version will not reflect the fact that the RPM's been updated.

If you take a look at my bootloader update packages, you'll see that every single one of them comes with a matching RPM version. I stand by what I said about not flashing your RPM-only update.

The post on RW that you linked has been sent to me before. If you read it properly, you'll realize that it's simply a guy repeating rumors. He never claims any of them to be fact. He even specifically states that he's seen no effects positive or negative from changing RPM versions. Be my guest and flash whatever you want on your device; it is, after all, your device. But I do not condone swapping bits and pieces from different versions,

especially

since Samsung has changed something in the 4.3 builds that is bricking phones if people try to downgrade their bootloaders and nobody knows

what

was changed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
I have a spare s3 board. I have a hunch what is causing the bricks. If my buddy wants to bring me the spare board he said i could have from his smashed screen s3. then ill give it a go. i have a feeling that its the TZ.mbn only because a quick skim with a hex editor shows it seems to handle certs for encryption and decryption, and this possible could have something to do with it. If i get the board ill odin the new 4.3 then ill start downgrading piece by piece.

Samsung could also be deploying some sort of efuses.

Edit: doesnt odin verify so it would notify of a failure to downgrade/flash? havnt odined in a while so i forget. if this is the case the bootloader downgrades fine and something else has changed and caused a brick. Maybe some sort of efuse tech.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
That'd be helpful, but is it an I747M board or an I747U? The bootloaders are incompatible between models.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
its a M i'll start there then try the U stuff unless this is known to brick in which case it wont get very far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
The U bootloader will brick it, although it's probably only 1 specific partition that causes the brick. If you're willing to brick the board intentionally, go ahead and try the U partitions too, but it'll probably end badly lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
i dont care about this board, the radio was dodgy on it to begin with which caused my buddy slam it off the table thus smashing the screen. the board works, i put it in my s3 to get his internal storage off. but its not suitable for a replacement board anyways.

Spare bored is installed, will start to test.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
So far the new download mode has a few things new in it.

"Warranty Bit: 0"

"Bootloader AP SWREV: 1

Edit 1: Alright so far i have installed the rpm over the 4.3 stock odin, boots fine.

Edit2: flashed SBL2 SBL3 and aboot in one shot, and its bricked. so i can confirm that the rpm is not the cause its the bootloaders. aboot(sbl1) sbl2 and sbl3. my guess with out being able to verify at all is there have been some sort of efuses deployed that prevent a lower bootloader from booting.

Given that i had not flashed the tz yet we can probably say that wasnt it either.

NOTE: this was all done on a telus 4.3 rom downgrading to a telus 4.1.2 bootloader.

As i suspect, there has been an efuse blown that disables bootloaders earlier then the 4.3 to boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Which means that the I747M OTA also prevents downgrading the bootloader... Awesome. Guess I'll go make sure my M bootloaders are brick-proof too...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nelmaster_vc:
Actually I have the version of modem I747MVLDMF1 working perfect whit MIUI 3.7 with android 4.2.2 , I ask, I can flash the new modem I747MVLUEMK5 to my device with nothing affected? I can later flash any custom rom whit this new modem?? I just want to know before flash the new modem

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
Odin should stop the downgrade to an older bootloader if it detects the 4.3 bootloader no? maybe odin tars for the older boot loader is a safer bet top post for the users? May prevent some "Ooops" moments

Edit: i see that this is not the case, never mind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
It's not hard to add an assert at the start of the update_script in recovery-flashable ZIPs that only allows flashing from specific other versions. The same way ROMs refuse to install on the wrong device.

I just realized we're having a bootloader-related conversation in the modem thread. Whoops. lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
I'm working on an unbrick method right now. I should have something for you to put in the first post in a few hours im at work so i i have to juggle work and testing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
That's awesome man, I wish I could click Thanks more than once per post!

If your unbrick method is to fix the bricking that was happening because of attempted bootloader downgrades, you should post it here: Bootloader Thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
will do, outo f curiosity im going to try to debrick to a 4.1.2 bootloader just for the sake of saying FU to samsung and bringing a 4.3 bootloader device back to 4.1.2 boot lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nelmaster_vc:
Anyone can tell me about this¿? :crying::confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Do that, and they may just want to hire you! :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
You can update your modem all you want. It won't affect ROM installation. Just don't install the wrong modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
no dice i cant get it to boot a pre 4.3 bootloader it has popped an efuse and thus the bootloader and aboot will never boot from a 4.1.2 rom again.

good news is i have it booting on the 4.3 boot loader from SD and im about to odin it back to restore the 4.3 bootloader to EMMC so i dont have to boot the damn thing off SD all the time.

---------- Post added at 02:17 PM ---------- Previous post was at 02:02 PM ----------

Some one on the I747U who has the 4.3 bootloader with the latest OTA needs to run this for me command in a root adb shell and upload it some where so i can compare it to what i have and make sure what the I747U users need is in the dump to debrick.

this is the command
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spongdangly:
Proper MD5sum for modem_CWM_I747MVLUEMK5.zip

First of all a huge thanks to dstuck2k for maintaining this thread and to -Mr. X- for posted the latest Canadian Modem as well as all the previous modem posters.

I noticed that the modem that -Mr. X- uploaded has a different MD5sum then the opening post.

-Mr. X-: 30ad551af782fbf07d1e1bd72ec7d4fa

dstruck2k: 921e4f9f17d697cfa269baf68372adc4

I was wondering if the difference was because dstruck2k had pulled the modem from the update himself. I don't want to risk flashing an incompatible/incomplete modem file since I don't know what the risks are.

Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -Mr. X-:
He probably pulled and zipped it him self, so the md5 will differ. Either or works, i personally flashed my devices with the one i uploaded.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I modified the flashing script slightly, which would've altered the MD5. I flashed my modem using the one I posted and it's been working fine ever since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DroidJay123:
Hello-

My phone just recently got the OTA update from AT&T (4.3) and of course the bootloader is new and not recognized yet by ROM developers. Is it safe to downgrade the baseband version on Samsung Galaxy S3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
The baseband is not the bootloader. The baseband is the modem. You can flash any modem for your device that you want.

Also, please don't ever quote the first post of a thread again. All that says is that you didn't bother reading past that point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
is there a link to the MJB Modem/Baseband?? I wanna try it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DroidJay123:
Baseband unkown after flashing

So I am trying to downgrade to a baseband that is recognized by ROM developers as my g/f accepted the OTA update from AT&T and was upgraded to 4.3 and unfortunately an all new baseband. I flashed the modem zip to get it back down to i747UCDLK3. The flash went fine and I did a wipe of dalvik cache and cache. The phone now shows an UNKNOWN baseband and there is no mobile signal of course. How does this get corrected as I couldn't find it within this thread?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
ROMs don't check your baseband version. They check your bootloader version. You can not downgrade from a 4.3 bootloader. Just ask your ROM dev to add the new bootloader version to their asserts in the update-script.

I'd suggest reflashing your modem with the newest one I've posted for the I747U and then wiping cache/dalvik. I'll be restructuring the download system in the next day or two when I get a chance to rebuild these flashables to stop people from cross-flashing.

(FYI: Some ROMs will say "baseband unknown" when you first switch modem versions, but it fixes itself after a reboot.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
Have to report that Baseband version UEMK5 is rocking the house with Claro PR. Got stronger signal in places used to not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DroidJay123:
Thanks for the info. If I rather not wait around for them to update their asserts (who knows how long that might take?), can I just reflash the factory ROM file that the phone shipped with? That should then give me a recognizable bootloader version...correct?

Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
You can not downgrade your bootloader once you have the new version from the 4.3 OTA

It doesn't matter how you try to downgrade, it will brick your device. (eFUSEs suck)

Just change the update-script yourself, remove the asserts and flash the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DroidJay123:
Ok. Under "about device" where is the bootloader version listed? I thought I had read a forum post where someone flashed the original firmware of the phone to get the baseband modem and bootloader back to factory? Doing this won't revert the bootloader? Just the modem? Sorry for the questions but we are not all as well versed and I rather not do the "wrong" thing and screw it up....