yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
I wouldn't flash a bootloader or platform file while a device is online. Use ODIN or Heimdall to flash from your PC.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iNeedICS:
I can't confirm, I used my pc, I've never used mobile Odin:/

Sent from Squishy's S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tmokeith:
HaHa....No he didnt.....all have declined.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SaHiLzZ:
Can someone upload the files to a publicly available location like mediashare/etc? Not dropbox or a short term link.

Also, everyone on the list who signed up for the bounty and hold a S3 i747 (ATT version), please send your pledged amount to TMOKIETH @ krwusa@gmail.com

I understand me & ysr84 are waiting for a i747M workaround, however this shouldn't hold back anyone else from not sending their pledged amount to TMOKIETH. I have updated first post
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theking_13:
I can host it on my GDrive account, even though I haven't owned an S3 for the longest time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iNeedICS:
wait why didn't he? Lol he obviously made it work so what's the issue?

OMG HAVENT SEEN YOU IN A LOOONG TIME! PM ME!

Sent from Squishy's S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamesbishop17:
invalid hash value

I downloaded the files for this via dropbox but im getting this for every file...any ideas would be greatly appreciated.

<osm>please wait <osm>md5 hash value invalid,<osm> bootloader_T999UCALJ2.TAR.MD5 is invalid,<osm> end.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iNeedICS:
Redownload, happened to me too, :)

Sent from Squishy's S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] latinmaxima:
I continue getting a failure at the bootloader file. I have verified the download and can't get past it. Any idea?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iNeedICS:
What version of Odin are you using?

Sent from Squishy's S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Febby:
I think this is why not many have a desire to complete a bounty because people back down or refuse to pay their part of the bounty.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] latinmaxima:
3.04 and 3.07 I got 3.04 to work after redownloading all the files over night and trying again. I actually pulled the shared dropbox into my own and then had my drop boxsync on my pc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sci2:
Does anyone know whether we should be using an AT&T or T-mobile CWM recovery once we've done this? Does it matter? Also, I didn't pledge anything to tmokeith, but I'm still throwing him $20.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Febby:
Scholar right there ladies and gentleman. Didn't even pledge originally but still donates over those who made a pledge!

- lowers hat in appalled moment -
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sci2:
I'm not sure if you're being sarcastic here or not.

As for my last question, from what I gather the recoveries are the same for all GSM/LTE variants so it doesn't matter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Febby:
I was being serious. You obviously found the method useful, so you sent a donation. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sci2:
The word appalled threw me off. But thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Febby:
Oh my mistake! I'm running on 4 hours of sleep with kids and life in the way. One of these days I'm going to regret using the wrong word. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
I wonder if this mod could be done the other way around to enable LTE on the T999. I know everyone says the T-Mobile S3 doesn't have LTE but it has the same modem/chipset as all the other S3s. It's probably just turned off.

Sent from my Galaxy Note 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iNeedICS:
I was wondering the same thing, if I had money to spare I'd just risk it and flash these files on the t999 haha but I has no money

Sent from Squishy's S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C3cars:
Link to Files?

I am having the same issue with the BOOTLOADER returning as invalid. Can you please provide a download link to the files you used to remedy the issue.

Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xmanberserker:
Im using t999 cmw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iNeedICS:
I'm using at&t twrp/cwm (I switched but both work)

Sent from Squishy's S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nodyarg:
here in canada the carriers that use the tmobile band have significantly less expensive plans. second hand i747m's from the larger more expensive carriers are widely available and reasonably priced, thus the T999's that work on the cheaper carriers are in high demand and severely overpriced. i cant afford to spend retail prices upwards of $600 whenever i get a new phone, that's how the fix will help me and lots of others up here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ysr84:
Very well said....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C3cars:
Custom ROM?

Has anyone flashed a Cyanogenmod ROM or an AOKP (AT&T or T-Mobile) onto their device and retained the AWS band functionality? I flashed TWRP d2att v2.5 and I am hesitant to flash a custom rom because I fear breaking the device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ysr84:
I will give it a shot tomorrow... if bricked i can always jtag it... :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vln004:
I flashed the latest CM nightly by flashing the newest bootloader over this one, but retaining all the other files. My phone did retain AWS but was unable to switch to HSDPA+ and was stuck on UMTS regardless of what I tried. I restored all the files from this mod and flashed MIUI over this and all is well, AWS works great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ysr84:
Let me try it now... kinda sick today... plz if you can let me know which rom or cwm did you use....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlimJ87D:
I think the future of bounties should be done with kickstarter. Makes it more legit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ysr84:
In process of trying....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ysr84:
I have it all installed but cannot access the *#7284# ... menu using cyanogenmod....

Any help is appreciated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
That menu is part of Samsung ROMs only. No way to get it to work on AOSP ROMs. Nandroid your current ROM, flash a Samsung ROM to do what you need, then Nandroid back.

Sent from my Galaxy Note 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ysr84:
Let me give it a shot....

---------- Post added at 09:48 PM ---------- Previous post was at 08:55 PM ----------

are you using i747m or i747???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vln004:
i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackmamba:
I picked up one of the "lightly loved" S3s from Wind a week back for $299 + tax. Looked brand new and came with all original accessories.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C3cars:
Steps

Can you please elaborate on the steps you have taken to install a custom rom and keep tmokeith's mod working.

I have currently flashed the 4 files via odin, but on the stock T-Mobile 4.0.4 I cannot get 3G to work, only 4G.

---------- Post added at 12:25 PM ---------- Previous post was at 11:57 AM ----------

I am having trouble testing the 1700Mhz 3G band. I am in the ServiceMode of the phone, but I cannot find a way to set the 3G band as preference. Can someone please give me a step by step explanation on how to enable 3G on the phone. I am using the stock tmobile 4.0.4. Maybe we can also post the instructions in the OP so that the question does not arise in the future.. Thanks Community.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sci2:
I think this is nomenclature confusion. So far as I can tell, you'll no longer really see '3g' on your phone. It will be displayed as '4g'. The g race in the states is about as dumb as the megapixel race in cameras. You may remember when iOS 5 or some such came out and one of the changes was that the phone showed 4g instead of 3g. It's all HSPA of some form. When you flash these 4 files, the CSC file appears to be doing the most work, changing the modem drivers from the AT&T specific bands to include the 1700MHz '4g' band that the modem hardware is already capable.

You should then be able to hit *#2263# and bring up the service menu. You may then choose WCDMA Band preference and see 1700MHz. I can switch between 1900 and 1700 and I'll lose service briefly before it picks up the new frequency. It always shows 4g.

I now am using Aamir's tmo stock based ROM which is 4.1.2. I simply flashed it with CWM per normal. Of note is that my band preference in the service menu is strictly automatic. I've yet to land on Edge or anything other than 4g for that matter. Prior to flashing those 4 files initially, I would wind up on Edge pretty often. It seems to be acting exactly as a T999.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
I have pretty much the same configuration and the same behavior occurs here too.

Just to clarify:

I live in a poor 3G coverage area, and I see "4G" on the top bar when UMTS:3 is listed on settings>about. I assume that's just 3G . My speeds are anywhere from .6 to 1.5 Megabits per second. Otherwise most of the time it falls back to "G" which I assume is GPRS/EDGE, GPRS:1 on settings>about.

I have not noticed any other sign/letter on the top bar other than those two. If you do get something else I would be interested to know.

And to get here I did exactly this:

0: SIM Unlocked the device prior to flashing. Probably not a requirement but it's free so why not.

1: Loaded all 4 files from the dropbox link as instructed.

2: Flashed Team Win Recovery for T999 manually, stock ATT would not work for me.

3: Flashed this ROM over it http://xdaforums.com/showthread.php?t=2279790

4: Verified all bands were present with *#2263# and did a manual selection to 1700mhz on service menu to ensure it worked at that particular frequency.

If you have any questions go ahead and ask me. :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daddy4life09:
if I was to try this,What would be the best way to revert back just in case I decided tmobile was not for me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
So I have the 4 files installed via Odin. Worked flawlessly and thats all set.

Now I want to install an AOSP ROM. Ive used both the att and tmo versions of cwm and twrp, but I get errors when trying to install CM 10.1 on either. Ive tried both tmo and att versions of the ROM too.

Could it be because I flashed the new recoveries via odin after I flashed the original 4? Should I replace the PDA section with my custom recovert while flashing the original files?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] livethisfight:
Did a few searches and couldn't find anything. I'd like to know as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sci2:
I have cwm 6.0.3.1 (AT&T but from what I could find, they are both the same) installed. I flashed Aamir's stock based rom no problem. The first one was 4.1.1 and the latest 4.1.2. You could try that one just to see if it will take versus a non-stock rom but I don't see any reason why you shouldn't be able to flash anything you want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
Stockorama (A stock based ROM that has options for tmobile, att, and canadian all in one) worked for me with the ATT option. But it only was capable of UMTS:3 at that point instead of the HSPA:11 I was getting before on the original "LTE Test" ROM.

When I use the tmobile option in Stockorama, it fails device verification. When I use ATT AOSP ROMs it fails bootloader verification. Seems like my phone is stuck in limbo, haha.

Ideas?

Edit: Has anyone been able to simply flash this, then a custom recovery, then an AOSP ROM? All while still keeping HSPA and HSPA+?

I feel as though if there were a CM build that either didn't try to verify correct model or bootloader this would be no problem!

I installed the latest Tmobile modem to try to trick it... no go.

EDIT 2

: I dirty flashed This Tmobile MIUI Port over the "LTE Test" build. Result: FULL spectrum of EDGE, HSPA, and HSPA +. So.... problem solved! Now we need a way to stop ROMs from verifying anything before flashing them....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
Not sure if it makes a difference, but I manually flashed TeamWin Recovery for T999 prior to flashing stockorama v2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
Which option did you chose in Stockorama? Tmobile or ATT? Did you retain HSPA and HSPA+? (In stock roms it says 4G for both HSPA and UMTS for some reason. UMTS is 3G.) You can check in the "about" screen.

I'm probably over explaining everything. I don't think everyone is a noob, I just like to be clear for anyone inexperienced (like me) trying to follow along.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
All T-Mobile.

I live in a poor coverage area so I barely get 3G as is, and yes it shows 4G on status bar, but it is in fact UMTS:3. I wrote that on my original post.

I wish I could test 4G, but I'd have to wait till over the weekend that. I can tell you all the bands show up fine on the service menu.

What exactly does yours show on top bar and settings>about?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
Sorry, I somehow missed where you noted you were getting UMTS. I live in the middle of a city with really good reception, where I get 4G HSPA(+) whilst on "lte test" and now this Tmobile MIUI port.

I tried choosing Tmobile in the Stockorama setup but the install failed with an assert failure that boiled it down to being the wrong model. Is this an issue only I'm getting? Cause that'd be annoying, haha. I had hoped I was making some (slow, very basic) progress on a group problem.

On "lte test" ROM on the top bar it says 4G while settings>about varies between HSPA:9, HSPA:11, and HSDPA:15

On MIUI the top bar varies between H and H+ while settings>about varies between HSPA:10 and HSPA+:15

On Stockorama the top bar says 4G while settings>about constantly stays on UMTS:3

I might have no idea what I'm talking about, but if we can edit the info in a CM10.1 flashable zip's build.prop and /META-INF/com/google/android/updater-script it should be able to flash whatever ROM without having to deal with the scripts being confused about the less than legit bootloader version and model version. I'm going to try to replace them with the ones from the MIUI zip.

My goal is to keep all the magic modem/bootloader stuff from the "lte test" rom and use the ROM of our choice.

I learned all this stuff over the course of today/tonight, lol. I think if someone experienced got in on this it'd be fairly easy... but till then....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
Ok, I will flash MIUI over it to see if i observe any difference on my end. I just assume UMTS:3 is all that is available here so I didn't think much of it.

I would like to stick with stock functionality if possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
Alright, let me know how that goes. I edited my last post with a slightly more specific error message I get when in recovery. (assert)

I'm simply trying to get CM 10.1/AOSP functionality. I think the key to keeping HSPA, etc, is in however that MIUI ROM is flashed, as its the only one that has worked and actually let me keep full connectivity.

Please, someone get a dev in here!

Edit: When I edit the updater-script and add the bootloader the phone is actually running (T999UCALJ2) to the allowable asserts (is that even the right terminology? Ha) I get a new error in recovery: "Error executiing updater binary" Instead of the "asserts failed" from before. Seems like I'm getting closer maybe? Is there other files I should look at to edit to account for the changed updater-script?

Edit 2:

Progress! AOSP ROM installed, but only UMTS:3, and no HSPA(+).....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
Ok, so I reflashed the stock mod.

Stock Mod = Status bar EDGE "E" - EDGE:2

Stock Mod = Status bar "4G" - UMTS:11

Stockorama v2 flashed on top of MOD = Status bar "G" - GPRS:1 or 2 Can't remember.

Stockorama v2 flashed on top of MOD = Status bar "4G" - UMTS:3

Speeds on SpeedtTest.net app are nearly identical on either ROM.

Makes me wonder if it is a glitch and they are just being reported wrong.

Did you check your actual bandwidth speeds before assuming you were locked on 3G UMTS:3?

ps: I think stock my device runs a little more consistent switching (3g/2g freq bands) back and fourth, could be just placebo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
I just did a speed test, and UMTS is definitely slower than what I was getting on HSPA. I'll check at a different time to account for network congestion.

I've considered flashing a 4.0.x AOSP or stock ROM to see if that makes a difference.

I'm gonna do my best to go through to see what makes that MIUI ROM behave so differently when it comes to network and radio handling/reporting that AOSP and Stockorama don't have. Now that I've figured out how to make any ROM flash, it should be slightly easier?

Again, if a developer came in here I think it'd be a piece of cake; I just dont quite know what I'm doing. Anyone have any suggestions of people to reach out to?

From my perspective it's almost like we have a new hybrid device that needs some small tweaking to established T-Mobile ROMS to make it work perfectly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
UMTS itself is slower than HSPA. They're all 3G technologies but UMTS is a slower form of HSPA. I think you need to flash an AT&T modem with the proper RIL files (they usually come with the ROM, but some modem zips include it). RIL files are what are used for the modem to talk to the rest of the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
Our point was that the system is potentially reporting HSPA as UTMS:3 as a glitch. That was what were trying to figure out.

When you ran tests on HSPA what did your top bar show and also under settings>about?

Thanks

---------- Post added at 07:33 PM ---------- Previous post was at 07:22 PM ----------

When you switched to both 1900 and 1700, what did your settings>about show ? And did you double check your download/upload stream speeds?

---------- Post added at 07:38 PM ---------- Previous post was at 07:33 PM ----------

What exactly did you flash on your device?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 96hondaex:
I am using Liquid Smooth 2.3 for att. T-Mobile version of this rom works as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
My phone refuses to let me flash anything AOSP on top of the LTE test ROM unless I modify the update script. Let me try Liquid right now....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vln004:
http://en.wikipedia.org/wiki/UMTS_frequency_bands

UMTS:3 = 1800 mhz.

which means that the mod is reverting on custom firmwares.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
Exactly, which is what I've been saying. Except for on the Tmobile MIUI port I used. That didn't affect the mod at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daddy4life09:
can you provide anymore details on the rom or a link?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
This ROM right here: http://xdaforums.com/showthread.php?t=2265615

Also, my involvement in this started on page 53, post #530 - incase you wanted to skim along. Might give you ideas on what we've tried.

Looking through that thread it looks like it could be because the build.prop was edited to work for both T999 and I747?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daddy4life09:
thanks alot,when in service mode I only get signal on the 1700 band all others leave me with nothing...my status says umts:3 then briefly goes to hspap:15 this is on 4.04 test rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
That means you're in an area with spotty reception... but it is working at least.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] popi09:
I did this a while back and it was working perfect. Had 4G and all but once I flashed Stockorama or something like that, I'm now stuck on G again! I restored the backup and and still on G. Any clue what might of happened for me to lose 4G?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cnims:
Popi09, try reflashing the modem file only in odin. You should get your 4G back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] popi09:
Didn't work. I just tried. Might try reflashing all four files again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] popi09:
Well flashing the files didnt work either now I'm stuck on the splash screen! Won't go any farther than that. I can get into stock recovery and into download.

Any help would be great!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] edwardng:
HELP!!!! Bricked?

I just stucked at samsung splash screen after flashing ATT preroot jb through odin... (link)

How to revert back to ATT jb???!!!!!

=== Hmm.... ====

Also, is that possible to flash 4 files and then upgrade to 4.1.2 premium suit from tmo?

if yes, where can i get the bootloader files and rom.....etc?

Besides, can someone upload any workable JB rom for this mod?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
I am not convinced that is the case yet. May just be a bug and the system is reporting false information, unless you can prove me wrong. :o

I seem to have identical speeds both with the 4 original mod files that were posted and the method listed below that replaces 1 of the files to an ATT stock rooted:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
Exactly which file from that page do you use?

Edit: Nevermind, I see it's the platform file. I wonder if it survives a flash with an AOSP ROM.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] popi09:
Try flashing twrp through Odin and restore a nandroid. I did that and it worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] effortless:
Firmware/Radio From Tmo Galaxy SIII LTE edition

I wonder if we can get/flash the firmware and radio from the soon to be released TMO GSIII LTE edition... Could that make the ATT S3 more TMO "friendly" ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vln004:
I think you're right. I've been on CM (nandroid restore) for the alst couple days. I have a solid 3g signal.. no hsdpa+ unfortunately. But before i was usually on Edge with hsdpa+ kicking in once i got a decent 1800mhz signal. So it probably is a bug of some sort. Possibly the baseband (which was meant for 4.0.4) not playing nicely with the stock 4.2.1 RIL?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
1800 MHz is not used in the US on GSM networks dude. T-Mobile uses 850/1900 MHz for EDGE (2G) and 1700/1900 (varies by area)/2100 MHz for HSPA+.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
Nevermind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Leggomyeggos:
Nevermind, found the info in the thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vln004:
lol, thanks for the correction. Either way, looks like i was wrong :). This is good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vln004:
So cm10.0 works great. I even get LTE.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daddy4life09:
great news!!!!update your guys modem file to the latest an you will be able to connect to hspap,after being stuck with a 3g icon since doing this mod on synergy I how get the h+ icon!!!all i did was update my modem to the latest att one....heres a link to the modems listed,I flashed the november 3rd one

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