Originally Posted by d4fseeker

Afaik noone except Verizon (surprise, surprise) locks the S3's bootloader. And Verizon-devices got their own forum.
The only issue with the international S3 is that carriers often delay updates or refuse to deliver them which can be circumvented with Odin as described above.

But they don't delay them if you just get the code to unlock your phone. No need for Odin. or am i totally off? I usually buy unbranded phones, so not really an issue for me. Just wondering if i got it right or what.

You're talking about network locking, meaning that only the carrier's SIM card will work with the device.
This is about carrier-branded ROM's which has nothing to do with network lock. Basically it's the carrier getting their hands on the ROM and modifying it so it fits their needs (which usually consist of adding the most possible bloatware)
Sometimes they remove the ability for OTA-updates completely during their processing of the ROM, but usually they only cause huge delays and skipped versions due to quality control (testing, ...) and/or laziness (costs)

To get a non-carrier-branded ROM on the phone you'll have to use Odin. Sometimes Kies mistakes the ROM too and flashs a Samsung-provided ROM but that's not a reliable method. Plus depending on your regional location it still takes long until release.

Thanks for all the replies, very interesting. I know of the Odin approach, very scary and not sure I am up to that task, but really we should not have to do that.

I can understand the carrier wanting to control the firmware release when they stick loads of extra bloat ware on it, bit in the case of the S3 there does not seem to be any?

Seems like a waste of time to the carrier IMHO

Originally Posted by d4fseeker

You're talking about network locking, meaning that only the carrier's SIM card will work with the device.
This is about carrier-branded ROM's which has nothing to do with network lock. Basically it's the carrier getting their hands on the ROM and modifying it so it fits their needs (which usually consist of adding the most possible bloatware)
Sometimes they remove the ability for OTA-updates completely during their processing of the ROM, but usually they only cause huge delays and skipped versions due to quality control (testing, ...) and/or laziness (costs)

To get a non-carrier-branded ROM on the phone you'll have to use Odin. Sometimes Kies mistakes the ROM too and flashs a Samsung-provided ROM but that's not a reliable method. Plus depending on your regional location it still takes long until release.

Ahhh.. Ok Thanks a lot. And how exactly would one go about to do that? Just flash a different firmware with odin? I think my GF's S3 is has a carrier branded rom, as my phone got official updates a lot sooner than hers. I have no clue about all this stock stuff. I just always root and update when i feel like it. She doesn't want me to rooth hers, but she wants to get updates quickly, so if you could just send me a link to a guide or quckly explain in PM i would appreciate it. Sorry for going off-topic.

Originally Posted by d4fseeker

Basically it's the carrier getting their hands on the ROM and modifying it so it fits their needs (which usually consist of adding the most possible bloatware)

It's also different between the U.S. carriers and the rest of the world. In the U.S. the phones get specific model numbers, have their physical radios configured differently, have OEM features omitted (h/w and s/w), and are tweaked to perform differently. Elsewhere it's usually a carrier splash screen and some fairly harmless carrier apps. The SGS3 is the closest to unmolested of any phone offered to date by the U.S. carriers. Other than the swap of Exynos for S4 of course. And Verizon locking the bootloader.