yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
Hmmmm..... One idea I've seen work, try sending an mms to yourself.

Edit:

Another idea. Do you know how to check the SMSC? The number could be wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] babyree:
I am confused. Will this only work for the model if it has been tinkered with (rooted)? I am on stock touchwiz but have this model. Would love to get this done to my phone. My phone is is this model and unlocked. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Whoareyou:
it shows as

"+12063130004",145

---------- Post added at 12:54 AM ---------- Previous post was at 12:52 AM ----------

no rooting needed, just follow the instructions included
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Doomstick:
I cant get this to work on the latest Task650 AOKP ROM. EDIT:this rom http://xdaforums.com/showthread.php?t=1766684. Everything seems to work when flashing the modem and csc files in odin, but when the phone restarts it goes into custom touch recovery v5.8.4.7 and comes up with these error codes.

E: invalid command arguement

E: failed to verify whole-file signature

E:signature verification failed

Installation aborted

Now when i boot up the phone it only connects to G

Earlier i had this running on stock rom no problem.

I did all the wipes multiple times, even different versions of Odin.

Any ideas? Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] babyree:
HELP! i followed instructions but now there is an android guy saying downloading do not turn off target. did i do something wrong? can i turn the phone off? what do i do? help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
If the flashing finished, you can turn it off. Not a big deal. Normally ODIN auto-reboots the phone when it's done flashing, but you must have unchecked the box for it. As long as nothing is in the process of being flashed, yes. Feel free to hold down the power button for a few seconds or just pull the battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockin982:
Help!!!

Almost ready to pull my hair out. I've downloaded the files twice in separate zips, and even individually, but I am getting an invalid hash on the PDA file. Are the files in the dropbox potentially corrupt, or am I doing something else wrong?

FYI, I'm using the 3.07 Odin.

Update ... trying with 3.04, and even 1.85 actually gives me a hash error on the bootloader file. I'm currently trying to flash the modem and CSC, to see if those will at least load and get me closer to where I'm try to get to. But I imagine I still need to be able to flash the other files to have a useable, working phone, so ... help please? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hith1:
Ok so i finally got my T-Mobile sim installed and my service is activated. i'm obvously in a reaffirmed area because i'm already getting LTE. My APN is currently epc.tmobile.com. After i flash the modem and CSC files from this thread via Odin will i have to do anything after that?

If i want to update to to a t mobile 4.2.2 stock rom with wifi calling what will i have to do? thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
*refarmed

Also, use fast.t-mobile.com. That's the newer APN.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
If you're in an LTE area that's also re farmed and you don't travel outside of it much then you may be better off not doing this flash. As you already see the hspa+ works fine withe the original att modem in refarmed areas and lte works either way. There is a stock tmobile rom from jovy23 that did WiFi calling and it worked on my phone. I switched to stockorama for the tether.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockin982:
Ok, so after MUCH effort (since last night), I FINALLY got this thing working. I'm on the Test Sample ROM, with LTE access. Speeds not blowing me away just yet, but it's lightyears ahead of where I was.

So ... from here, what's the fastest/easiest path to Root/custom rom? And should I be searching for TMO stuff from now on, or still use the ATT versions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Whoareyou:
I personally use the t-mobile roms but you can use either
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] babyree:
is the bootloader on the downloads correct? it is different from the screenshot one? Also I am sorry to sound stupid but do I push start on odin prior to the part on the S3? i just need a bit more clarification. thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hith1:
I flashed the Modem and CSC files and i'm now getting GPRS:1 and 'G' where i was not getting anything prior. I am not a re farmed area at home but i was earlier today at work. How do i force 1700 to determine if its working?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
Phone keypad.

*#2263# this lets you choose bands

*#0011# shows you the band you are on when in automatic or otherwise.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hith1:
sorry i should have been more specific. after getting into service mode via *#2263# how do you select it? and what to select exactly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
Has anyone tried just this csc file and left the latest stock att modem UCDLK3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hith1:
Nevermind a reboot fixed it. i was able to select the band after that and i appear to have everything Working! yay.

Though it appears i have crap signal in my basement. had great ATT Signal in my basement but T-Mobile signal sucks in my basement =(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Whoareyou:
Yes, but it restricts you back to 1900mhz, my recommendation is flash atleast the bootloader, modem, and CSC, i dont think the platform is a necessity though, but do not flash back to a AT&T modem or you will be forced back onto AT&T bands, i am currently getting GPRS/EDGE/UMTS:3/HSPAP:15/LTE on the T999 modem included in this project.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zucchero81:
I tried searching but haven't seen any news lately. Has progress for enabling AWS on the Canadian i747 model been abandoned? Or is someone still working on this? In any case thanks for the hard work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Outrager:
If I am in an area with the refarmed 1900MHz and LTE do I still need this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Whoareyou:
no but it will help you if you teavel outside of that area :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Outrager:
Cool thanks. For some reason AT&T versions seem to be cheaper to buy than T-Mobile versions so I think I might get the AT&T version instead on my T-Mobile plan.

Sorry if it has been mentioned already (still reading through the thread), but what happens with official updates or custom ROMs after this procedure? Are you locked to the old 4.0.4 ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
It's because the T-Mobile ones are pentaband out of the box and most people don't do these mods, let alone know how to root their phones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Outrager:
I wonder if AT&T's version having the proper hardware for LTE equals out the price of the chip getting the extra band on the T-Mobile version.

I just wish all companies released penta-band phones, but I guess at this point it's going to be even harder since there are so many different LTE bands.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
The 1700 MHz for HSPA+ is unusual outside of North America, so most carriers don't ask the manufacturers for it unless they themselves use it (like T-Mobile here or Mobilicity in Canada). In Europe, mostly 900 and 2100 MHz are used (which almost all phone are capable of), and here it's 850 and 1900 MHz for AT&T's HSPA+.

The thing is, T-Mobile's HSPA+ is as fast as LTE in most areas, so I don't think it really matters to people if they don't have LTE. This is besides the fact that T-Mobile now has a Galaxy S3 LTE, that's exactly the same as AT&T's but also does AWS for HSPA+. You guys should update the mod to use that.

Try flashing an NV backup from that phone (if someone has it) to an i747. That's how you enable AWS on the AT&T Galaxy Note 2 and AT&T Galaxy S4. I know someone said they tried and the settings don't stick, but I have a feeling that since they're both LTE devices it should work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Whoareyou:
you can flash any other rom, i would reccomend using the T-Mobile ROMs to be safe, (you have to remove the device identification in the zips /META-INF/com/google/android/updater-script)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Outrager:
Thanks for the information.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
Where did you get this info for flashing. Maybe I'm misunderstanding you but you can't just flash the t-999l stuff to an i747. It doesn't work. At least the t-999l modem has already been confirmed to cause no signal on the i747.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clirico:
I've been flashing AT&T and T-Mobile roms to my I747 without issue for the past few weeks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
Not the modem. The NV data. The NV data (via QPST) backup holds the modem setting, one of which (internally) is for AWS. On the AT&T Galaxy Note 2 and also recently the S4, it was found that if you take an NV backup from a T-Mobile Galaxy Note 2 (or S4 for the S4) and restore it on an AT&T Galaxy Note 2 with QPST, you gain AWS support, which means it's there but turned off by the modem. This is evidenced by the fact that if you flash or reflash an AT&T modem (even the same one currently on your phone), you lose AWS support.

Here's a video of it in action:

[YOUTUBE]y7gMO_kRxyM[/YOUTUBE]

https://www.youtube.com/watch?v=y7gMO_kRxyM

Since the T999L didn't exist at the time, people were trying this trick using a T999's backup. The settings wouldn't stick (there's no visual indication as they're internal, modem settings. You'd know if they're working if you start getting HSPA+ on AWS). This was probably because the i747 has LTE enabled while the T999 doesn't. The T999L, however, is basically the i747 with AWS enabled. I'm suggest you do what was done in the video above (of course, with a T999L backup) since they're the same hardware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Whoareyou:
Flashing the regular t999 modem does that too so that's not anything special
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
I wasn't talking about roms. Most roms don't have the modem in it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shafter13:
have you tried and confirm this? is it any better then the method used in this form?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
Interesting. I would like to see how exact the "same hardware" is. It would be cool if I could just flash the i747 to a T-999L
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
I don't have an S3. I have an AT&T Note 2 and a T-Mobile Note 2, and with this mod on the AT&T N2, it gets HSPA+ (1700 MHz) without having to change anything. It sticks across ROMs and basically anything except modem flashes. If you flash a modem you just do the mod again.

Sent from my Galaxy Note 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] talha746:
So can i use the same files on the s3 i747? Also do i have to unlock the phone first? And if i want to put a custom rom would i do that first or after? Thanks

Oh btw, i have a canadian version, dont know the deal with this version and at&t version, so can someone point me in the right direction?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdsu23:
Is there any way to get an updated modem already tunned for aws like the one included in the mod? because the one included in this mod works but it's too old.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Whoareyou:
lust make sure all lines before it mounts system are deleted, and then make sure there are no spaces at the top :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fredrick1213:
Is a backup of the NV data even available for the T999L yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dakeshon:
Did it, lost everything on my phone and I didn't back up. Blames on me. It works great, though. :victory::victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
Working on it in another thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Doomstick:
Anyone found a way to get this working with task 650 Rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fredrick1213:
Can you link me to the thread?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
http://xdaforums.com/showthread.php?t=2308514

Firmware is now on op. I don't know enough to know if that has the nv download in it. We were talking about the backup somewhere near page 30
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
The NV backup is a separate file that someone would have to point out as the NV file. Just to be safe, you should remove the IMEI number from the backup too. The file cannot be backed up or restored from the phone itself. It's held in a low-level (modem) part of the phone. The extension is .QCN.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
[MENTION=2924784]Product F(RED)[/MENTION] Are you familiar with editing these files at all? I'm curious how with the note 2 they removed the IMEI and made it so the phone you are uploading to keeps it's original IMEI.

I'm thinking they might have just deleted the whole block, but I haven't looked at it with qcn viewer on qpst to confirm that yet. That actually just popped into my head to try as I was writing... Not a bad idea. Any clue on what blocks the IMEI would be written to for a note 2? Still 550? My other thought was they might have changed all the blocks to 00.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
I've never done it myself (because the mod thread provides one that was already edited), but it's "line" 550. Someone said they just deleted the line with the IMEI and tested restoring it on their device and it didn't overwrite (it worked correctly). All you have to do is make a backup, make a copy of that backup and mess with the copy. If anything goes wrong, restore the original backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
Yup, that's pretty much what I was going to try. I think the IMEI has to be zeroed out on your phone for it to be overwritten, so I should be ok uploading a file without an IMEI. In theory I'll keep mine, but better safe than sorry. I'll dl the note 2 file when I get home to verify, just in case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
Yeah. Just don't flash any Note 2 stuff on your S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
Oh, I know better than that! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
Piece of cake. All the hex values for the IMEI in the note 2 file were just changed to 01 across the board. Now just waiting for the t999l file to play with.... Hopefully soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zswielder:
Suggestion

Hello,

May I please make a suggestion? I'm noticing that this thread has become quite branched out in terms of its contents. People are talking about various devices and different techs. As such, it is quite confusing and potentially misleading to people that visit this thread. So, how about we create designated threads to keep things more organized? To begin with, maybe someone can start a thread titled: "Instruction GS3 i747 on T-Mobile 3G & LTE" or something like that? Perhaps make it a sticky. Other conversations that are really not about that topic can create their own threads, perhaps?

GT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flamingsquash:
+1 this thread is starting get pretty confusing.

---------- Post added at 11:07 AM ---------- Previous post was at 11:02 AM ----------

Can some one help me. i did everything in the op. I can confirm that it works as i get 3g in any rom.

But i get 4g hspa+ in this rom : http://xdaforums.com/showthread.php?t=2195132what is special about this rom that is allowing me to get 4g.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
Thank you for the suggestion, but that was already done here: http://xdaforums.com/showthread.php?p=42131674

The posts in this thread are continuing with the original theme and working towards an alternate solution for enabling AWS.

I hope that helps out with the confusion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
The point of this thread is to enable 3G on tmobile AWS 1700/2100 band for the Att i747.

So far there is a old solution but it uses a somewhat antiquated modem. We are still looking for a solution that will work with the newest modem and also one to work for i747M variant.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zswielder:
upncoming,

Thank you for the info and link. It's good to know there's a different thread.

athlonxp2300,

I figured that was the purpose of this thread, but I guess I got confused when people started talking more about LTE and devices other than i747.

Just out of curiosity, what's wrong with the current method of using the old modem? Is the speed slower?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
I'm not sure if it will make the connections more stable/faster. That modem was from back on ics rom. Both T-Mobile and att have updated modems several times since then. The work upncoming is doing with the nv might prove to make it more future proof. It was that work I was referring to that has potential to be a more permanent fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flamingsquash:
That thread is closed....:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
Ha! I guess the mods didn't like him. I think it was his "accepting donations"...

You guys are right then! This needs a simpler how to thread. If anyone does start one, remember to give all the proper credit due to the people that made this fix possible. If I run into some extra time later this week I might do it myself.

---------- Post added at 09:11 AM ---------- Previous post was at 08:44 AM ----------

Back to the task at hand, our donor is having PC issues trying to do an NV data backup. Is anyone familiar with running QPST on Windows 8? There seems to be a compatibility issue. He's tried every Phoneutil setting on his phone, different compatibility modes in Win 8, and "run as admin". QPST configuration is not detecting his com port. Anyone have a fix besides try a different PC?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
The NV/qcn from a T999L was posted here by MotoDefier!

http://xdaforums.com/showthread.php?t=2308514&page=39

Post # 387. The IMEI has already been removed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
I've already tested on an I747 and an I747m (using the "m" right now). I can confirm it works on both variants. I'll write something up when I get a chance, but for now you can follow the same steps they used in the note 2 thread. Just use Moto's file. Be sure you give him thanks too! He worked very hard to get us this file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] New Optimus:
Very Awesome Thank you mr. Guinea Pig, I am glad you didn't Brick your phone, though I did not think it would happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdsu23:
Hi guys, Can you explain step by step how to use this method? I already tried to download the nv backup and the link does not exist anymore.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidjavid:
Upncoming is going to post a guide soon, but a loose guide would be to:

Back up your NV data to a qcn file using QPST

Download the file from that thread. It was moved, but the new one is here post #395

Use a hex editor to add your IMEI to the downloaded qcn file Yeah, don't actually do that.

Restore that qcn file to your phone using OPST. Same method as the Galaxy Note II uses here. Your phone has to be using a stock Touchwiz ROM.

From what I've gathered you have to redo this each time a new modem is flashed.

Can you flash a T999L modem after this? Or can they be modified to work? Or just use the latest AT&T modem? Stick with AT&T ROMs or T-Mobile T999 ROMs? When T999L ROMs are more widely available would they be a better bet? (Sorry for the millions of questions. I'm about to read through that Note II thread but wanted to see if you guys could provide clearer info)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tspx23:
yes i have flashed it and as i said earlier in the thread, your att s3 will not get any signal. most att s3's are not hardware supported if not all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statewi:
Bounty

put me down for 150
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clenh:
I've injected the T999 raw modem.bin from ysr84 into the Rogers CWM modem. : https://www.dropbox.com/sh/elrg0ahrdw3zcl7/iDyfRWh4wv

I need some brave tester to see this works. Might need to go to the Service Menu : UTMS -> Common -> WCDMA set Channel -> try set 1700 Band

Try at your own RISK.

I would test it but at the moment my phone is still network locked and still waiting for the code. Long story short don't bother with sim unlock, it'll lock backup, after flashing a few times. It's best to get the Network Unlock code.

Thanks goes out to ysr84 for T999 modem.bin and XblackdemonX for Rogers CWM modem flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sarim.ali:
I tried this and it and it doesn't work, at least for wind it doesn't. Maybe its because i use TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SaHiLzZ:
WIND has T999. did you try this on i747?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theking_13:
Getting an AT&T S3 tomorrow, put me down for $20 so its an even $300. I'll pay unless I can find someone to trade me for a T-Mobile version... :)

Sent from my sexy white HTC One X on T-Mobile ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tspx23:
this thread is ridiculous lol. i already posted the solution :P

IF the t-mobile modem doesn't work that just means the ATT S3 is not hardware supported. If you want I can post a flashable CWM zip file with the T999 modem.

3 devs have tried flashing the modem on ATT to get t-mobile 3g/4g and all confirmed their S3's don't have the hardware. I myself also tried it after tweaking some files and flashing over the modem similar to what I did when I ported the note modems.

Just use the link I posted earlier to see if your phone even has the correct bands, if it does not work--it is a hardware limitation.

---------- Post added at 09:17 AM ---------- Previous post was at 09:11 AM ----------

No offense but I don't think this was done right your modem file is 5MB -.- that is the size of a gs2 modem...

gs3 modem is about 60mb.

---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------

that is the incorrect modem file i'll post the zip in a bit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sheriffa:
My phone had and E for edge the other day. i'll try to screenshot it next time but i'm confident it has it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clenh:
No worries. I just took the raw modem file from ysr84 which is 10MB when injected it was 5MB CWM flash file. When I try dumping the modem through the terminal the modem file size is 10MB, I used the method at http://xdaforums.com/showthread.php?t=1705650 Did you try going in to the Service Menu to try to select 1700 band after the flash? If you can please post the full T999V/SC-06D modem or the modified modem. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chipstien:
Can someone explain why they want to use a ATT model on Tmobile? Surely it isn't solely because of purchasing possibilities on Craigslist. *confused*

Sent from my SGS3 running AOKP.