yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Bummer..I figured what I was thinking would have been too easy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
Hope this isn't too noobie of a question. ..if I have aws enabled and I have automatic selected if I go into an area where I would normally get 2g would it pick up the 3 or 4g instead? Or do I need to have the 1700 band selected?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] New Optimus:
Generally speaking the phone will pick up HSPA before edge. So if the 1700 is strong enough to grab it will go there, However the att phones are set to look to 1900 first so if the 1700 is a weaker signal it will skip it in favor of strong 1900.

so if you are in an area you know has 1700 but your phone is showing edge go into the dialer and dial *#2263# select WCDMA 1700 let it switch and then go back and select automatic. It will then keep the 1700 as long as the signal is strong enough.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrjd:
i live in Pensacola and as a contractor I travel the area a lot. And with the way I installed everything it does seem to switch with out issue between all the bands. Including lte.

Speed test from new tower in mobile /Spanish fort area
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fatty1212:
Wife has an i747. However, i will keep monitoring this thread until there's a more permanent fix. Thanks to OP for letting this work up to this point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fffft:
Flashing m-variant phones

It's great to have a working method for US models, but it is apparent that the identical Canadian hardware (m-variant phones) doesn't work. Despite two or three people reporting that they managed to get AWS with m models, they appear to be mistaken. Unless their success is attributable to some specific and elusive modem or firmware version.. it is not repeatable. At least not for the Bell I747m. I've tried every suggestion in the handful of threads here plus quite a few more. Whether enabling NV parameters, writing various .qcn's.. enabling NV item 1877 ('06').. etc., the best I can effect for a m model is to gain AWS for about 45 seconds after a boot.. then the phone quickly moves to a no service state.

As for flashing US modems or bootloaders onto m variant phones.. the install scripts abort when they don't see an US model. Does anyone know what the hardware check looks for? Is it the model listed in build.prop? And if so would changing

ro.product.model=SGH-I747M

ro.product.name=d2vl

ro.product.device=d2can

to

ro.product.model=SAMSUNG-SGH-I747

ro.product.name=d2uc

ro.product.device=d2att

allow flashing US files to m variant phones?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
I can't say why it doesn't work for you since I do not have a Bell variant to work with. I do have a Rogers I747M, and this method worked for me without issues.

This is still a work in progress, and I appreciate your input. Once I figure out a way to make this stick past a reboot I'll try to look into what might be going wrong with your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fffft:
thus instuag

I appreciate that upncoming. Presumably the Bell branded firmware has some key parameter configured differently. Aside from replicating the suggested steps in the threads, I've flashed and configured this phone dozens of times, methodically changing each variable. And tried all of the m-version modems and a number of ICS TW roms. If the error is on my end, it's hard to imagine what it might be at this point.

Perhaps someone here has some experience with what the install scripts or recovery looks for when doing the hardware check. Unless the IDs are securely signed, it should be possible to shoehorn the TMO bootloader & modem onto the I747m models.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adika9:
I have virgin (bell) i747m and I had aokp rom after stock then returned to stock (rooted) rom

When I was on aokp I updated the bootloader (don't know if this made a difference)

For me this mode is working flawlessly with the app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fffft:
Yes, a different bootloader (or modem) could make all the difference in the world. You also have a different carrier than me. Virgin is owned by Bell, but the Virgin branded firmware may have differences from the Bell version. My Bell S3 rejects attempts to install USA S3 bootloaders or modems, which is why I was looking into editing the build properties file. I also tried flashing to a Wicked (TW) 4.1.2 rom. But I cannot update the bootloader with this rom just as is the case with the stock rom.

Can you tell us what bootloader version you updated to? It would be great if you could tell us your baseband and TW versions too. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adika9:
Here is the bootloader I upgraded the canadian version

http://xdaforums.com/showpost.php?p=41503727&postcount=13716

I'm not sure but when I reversed to 4.1.2 stock(rooted) it might reverted the bootloader so the curent version of the baseband is I747MVLDMF1

Hope this helps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jimmie48jj:
Will this enable me to use Strighttalk and have 3G over the 1700 band.... Right now I only get Edge.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperAfnan:
Yeah it should! It will work on any carrier that uses AWS 1700. Meaning T-mobile or any gsm carrier that uses that band.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fffft:
It will if Straightalk uses the 1700 band. In the past their CDMA side only used the Verizon /Sprint 1xRTT network.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yaboysupadave:
hey guys need some help i can't get qpst to recognize my i747 stock rooted, windows 7, yes running in the diag mode through dialer code restarted computer after qpst install, add port it shows com 11 but has no phone info.

thanks.

[edit] had to reinstall my samsung drivers for some reason but its workin now just finished backing up my og nv data here we go!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yaboysupadave:
edge

flashed successfully ended up getting edge on automatic and 0 connection on 1700. i was trying to get lte but guess im just gonna have to wait i have a 4g connection 98% of the time-Irving, Tx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
Can I assume this thread is over with? Sure hope not
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lost_:
In DC also. I did this mod on 2 phone and I have both AT&T and Tmo sim cards. The first one (blue) worked like a champ. The second one (white) would get stuck on Edge no matter what I do such with *#2263# or *#*#4636#*#* such choosing different preferences, going in and out of airplane, etc.

Really weird: when my 2 phones are side-by-side, both with AWS-enabled qcn, white would get stuck with Edge until I flash it back to the stock AT&T qcn.

Regardless of the sim card, AT&T or Tmo, blue, both would get HSPA or LTE. But on white, both sim is stuck on Edge unless I flash the stock qcn.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bensoren:
Att I747 with a Tmobile SIM

Question, my S3 was on Att originally and I have since unlocked and ported to Tmobile, am I going to run into issues if I run tmobile ROMs as apposed to Att given that is the original harware or are they interchangeable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] serio22:
They are interchangeable, but only flash ROMs.. Also, you don't need to quote the first post
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lost_:
What about ODIN firmware of T999? (not modem of course)

I'm still baffled why after flashing the qcn, my white i747 would get only get GSM 1900 and no WCDMA or LTE at all, while my blue i747 sitting next to it (with the same qcn flash) would get WCDMA or LTE just fine. I would have to flash back stock qcn on white to get signal on WCDMA or LTE. I did that back and forth and it's consistently doing that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xX_Psycho_PR_Xx:
i have an stupid question but i gonna do it.. i tried this method and now im running 4g... but can i root my cel and change the rom and i will dont have any problem? Sorry for my english.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bensoren:
Cool, thanks for the info and understood on the quoting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
Any work still being done on this to get it to stick?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
Yes. Slowly but surely.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Novembre5:
I was able to get this to stick even after rebooting. Can someone else please try what I did to see if this is working for others.

Here is what I did. I followed what you posted HEREl. After doing that I used EFS Professional, selected restore, and then checked off "Repair Unknown Baseband / No Signal" and clicked on Format EFS. I then followed THISl youtube video and restored my original IMEI.

I did this yesterday and I have since restarted my phone several times and even did a battery pull, and I still am receiving T-Mobile LTE on my AT&T Galaxy S3. I also want to add that before I did this mod I was stuck on edge.

Please let me know what happens for anyone else who tries this. Also, please be sure to do a backup of your NV data, just in case this does not work the same for everyone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
Sounds great! I'll give it a shot when I can later. A few questions though... Making LTE stick wasn't an issue. Is the 1700 band sticking? I'm hoping that you meant that is what's working. What file did you restore with EFS professional? Did you backup something first? Did you lose your IMEI after restoring with EFS professional? Please advise. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Novembre5:
As far as I can tell the 1700 band is sticking, but I am not 100% sure. For me I was not able to even get LTE to stick, my phone was stuck on edge. Doing what you suggested in post #1 worked for me, until I reset my phone. Once I reset the phone I was once again stuck on edge.

I did not restore a file with EFS Professional after I did the format. For some reason after I did the format everything stuck. I know that my problem was a little different, because I was stuck on edge, but as far as I can tell this is what made your NV file stick.

I noticed that after using your NV file in post #1 my IMEI number had changed. I did check my IMEI number before doing this mod, and it did change after doing your aws mod. Again, not sure if this had something to do with me being stuck on edge or not, that is why I would like someone else to try out what I did and see if it works for them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
This gets odder and odder. I didn't think EFS pro would let you do anything on the restore tab without having a file to restore. I'll have to double check.

I didn't think the Imei changed at all. I'll have to verify that too. I'm happy to hear you got things working though and 4g is up and running for you.

If you can, to check if the 1700 band is working: go to the dialer, dial *#*#2263*#*#, go to wcdma settings, select 1700 band, hit the menu button, select back, and if there's an asterisk next to 1700 then it's working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Novembre5:
Okay, I did that and it appears that it is not working. I am sorry for the confusion, I was just excited that this worked for getting me off of edge and back onto 4g / LTE. I hope that what I did will be able to help others who are stuck on edge. Once again sorry for the mix up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upncoming:
Bummer, but good to hear your phone is back in working order. Thanks for sharing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrjd:
Success?

Don't want to get everyones hopes up, but I think i found a way to load latest AOSP's with the nv method, getting around the fact we can't use the keycode to get into diag mode........I have to run into town to test to see if 1700 is on or not first.........only edge here at the house.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrjd:
I'm on paranoid androids latest beta Showing 3g and h+. No lte towers in my area but no reason to think it wouldn't work as well.

I'll post my step by step when I get a chance. There is some tricky commands you have to throw in terminal.

But the good news is you can use latest aosp and use reboot nvbackup/nvrestore method.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nemiroG1:
Awesome!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbogdann:
I have had the same problem with my phone being stucked on Edge and your method really works. Even after I reboot my phone I still have LTE. I cannot check to see if I have AWS 1700 enabled . The only thing that I have not been able to solve yet is the Serial Number which is 00000000000 . I restored my IMEI but I can not restore the serial number.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ysr84:
Hi Guys,

I know a lot of people are working on this mod... Sahilz started a bounty and well... I am willing to provide any help possible to get this mod going....

I have a I747M for testing purposes if anybody would like me to test anything... I also have a working WIND MOBILE (Canadian aws provider) sim card....

Also, if I brick my phone its not a big deal... I can unbrick it.....

If possible I am willing to do teamviewer sessions or anything else to help out... Cheers!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ysr84:
Just another thread which guys were working on before

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

---------- Post added at 03:37 AM ---------- Previous post was at 02:41 AM ----------

Just for R & D purposes I bricked my I747M and then for unbricking I tried to use the I747 (At&t) bootloader and still it would not work.....

I have also tried to replace the partitions with I747 (at&t) to I747M... got a bricked device :(

Any other suggestions????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayjr2081:
Love this!!! I know its not full proof but it works wonders...my speeds increased after following the steps and using the t999 file...just will continue to watch this until a permanent fix is available...keep up the great work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
I've used this method for a while and it worked well.

I decided to update my i747 to the latest i747ucdmg2 modem.

Since then trying to do this method using either the asw nv file or the t999L nv file doesn't work right. I can select 1700 but it doesn't connect right. It hangs when connecting to internet. After rebooting again (not nv restore). It connects right.

Has anyone else had success with this mod and the newest modem for att i747?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
I'm using the newest modem and boot loader and using this mod with no issues
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
I'm not positive I'm on the newest boot loader. How can I verify?

You are using modem UCDMG2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
Get an app called root checker from play store and if u only flashed the modem u most likely aren't on the newest boot loaders
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
Yep I was on the previous bootloader. I will try the nv flash again tonight.

which seems to work best, the AWS NV backup or the t999l nv backup?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Leggomyeggos:
Got this working on my Koodo i747M with my Mobilicity sim card. Unfortunately after a reboot it won't connect. Just waiting for a permanent solution but this will do. Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
I prefer the nv method u don't have to revert back to ICS or anything
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
That's not what I was talking about. There are two files that can be used. either the NV data from the T999L, or the NV data from the AWS mod. Either one can be used to flash the NV data to the phone but neither one works as well for me on the new modem as they did on the old modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
Far as i know either file makes no difference
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ruizramosjose:
My SkyRocket i727R was hard bricked yesterday, but today I went to JTAG service and they Unbricked it, but they installed GB 2.3.5 for i727 AT&T

They told me it had been treated like a i727 so I downloaded a i727 JB Stock Rom But whe I tried to flash it whit ODIN It get stuck on "AMSS.bin" or in Gingerbread "boot.img"

What can I do?

Thanks a lot for your help.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Odin won't work like that. Flash a Rogers tar.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ruizramosjose:
Well Thanks for your help.

Now I did Odin Work after reading a lot.

I flashed a i727 AT&T JB Rom, the only different thing I did was Uncheck "F. Reset Time" and the flash worked out.

So I can say this question is solved.
[One (M7) Q&A, Help & Troubleshooting] erapmicks:
Anyone know how? I have to return the phone because of physical defect.
[One (M7) Q&A, Help & Troubleshooting] a box of kittens:
Well then you're going to want full stock locked not relocked..do you have s off
[One (M7) Q&A, Help & Troubleshooting] TITANote2LTE:
I also would like to know how to. I have been searching endless on restoring this one back to stock every possible way leads to verification fail.... I have the correct nandroid for my model (bell mobility canada) but its becoming a pain. If anyone can point me in the direction that would be much appreciated..and yes I have read the stickies and guides. My major issue it seems is I cannot restore the nandroid in cwm as it wont mount to my sd
[One (M7) Q&A, Help & Troubleshooting] erapmicks:
My s-off is on. So no I'm not on s-off. Just rooted with custom recovery
[One (M7) Q&A, Help & Troubleshooting] bluegizmo83:
Your going to have to S-OFF first... You need S-OFF first so that you can lock your boot loader again without it saying "relocked" and "tampered". I'd recommend Revone S-OFF since it does NOT install a custom boot loader and is very easy to use.
[One (M7) Q&A, Help & Troubleshooting] erapmicks:
After having my s-off, what do I do next? Thanks in advance
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] wdibb:
I have a 9090 bought in Dubai. I am now getting a bluetooth expired message and the imate help desk told me that I must get a ROM upgrade from the Qtek suppliers. Problem is that they all give a country error. Is there a patch for the bluetooth expiry problem? Is there a ROM upgrade that is open for all Qtek 9090s? thanks Bill
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Joao_Caldeira:
You may just try the BT upgrade to 3900 (file on FTP server) or try to correct the Country error with GetDeviceData.exe also on the FTP site plus the instructions of the other thread about upgrading QTEK

Joao Caldeira
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Joao_Caldeira:
Sorry, but the 3900 does not seem to work (at least out of the box)

Just tried it and started to receive that message.

Joao Caldeira
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] mamaich:
Someone has posted the attached file and said that it can fix BT license expired error. I have not tried it myself, so use it on your own risk.

To use it - extract archive to your PocketPC and run EXE file.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Joao_Caldeira:
Thanks.

I'll try it as soon as I have my cradle.

Joao Caldeira
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Joao_Caldeira:
Hi.

No more License expired message, but I'm not being able to pair with my BT Headset HBH-660.

Maybe I'm doing somethiing wrong... I'll check it out...

Thanks,

Joao Caldeira
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Joao_Caldeira:
OK.

Paired the device. When trying to "connect" the QTEK showed failes.

Turn BT off and on and everything is working.

THANKS

Joao Caldeira
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] wdibb:
BT_key

I copied the two extracted files over to myQtek 9090 and opened the exe file. A list of BT addresses came up and a write key icon. When I try to select a BT address and write it, I get the following message: ResetMFG(). DeviceIoControl(). FL_IOCTL_BDK_OPERATION fail!

Am I doing something wrong - I copied the files into my documents on the 9090 and ran the exe file through file explorer on the Qtek.

Thanks,

Bill
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] rollinncoaster:
BT_Key

Thanks. This solved my problem.

I was getting this message everytime I turned bluetooth on:

Sorry! Bluetooth can no longer be used because the license has expired.

BDA: 00:00:00:00:00:00

Key:

E3E534E19B3E8214C543A

73C0A8B9A9074DD3B175

3515CD8

For some reason after a System ROM upgrade, my bluetooth device showed what it looks like a mac address as 00:00:00:00:00:00. This tool fixed the problem.

For anyone that is running into the Bluetooth License problem please try this.

DJ
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] nogga:
Yes it does.Seems after upgrade BT have no mac adress so this "thingie" writes it down in some register.Any way done job for me.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Ninja_Gundam:
Damn.. same thing happened to me today :((

Reset time\soft reset not work

the fix when i launch i get "ResetMFG(). DeviceIoControl(). FL_IOCTL_BDK_OPERATION fail! " too..

Is there another way to set up a mac address? :O

Chooo
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Ninja_Gundam:
Upgraded to 3900... still 00:00... BDA and that fix program doesn't work!

Chooo
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] xplode:
well in WM2003 rom they use old versions of the Bt stack thats why it shows license error
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Ninja_Gundam:
Ok.. but.. it's normal as answer? ^_^;;;

No mistaken.. thx for let me know this.. but danguard is already dead here in italy.. how the hell can i fix? I dont want to install a wm5, there isn't a way in registry to rewrite BT?

Chooo
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] tryptik:
The BT update worked for me.

FYI
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Ninja_Gundam:
I have tested 3900 and now 3500... nothing..

i want to try other stack,like this : OEM_WWE_160_600.sa.CAB

but.. how can i delete used file "audioGW.dll"?

Chooo
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] McDV:
I just want to give a short feedback.

I was experiencing the license-problem since a ROM-Update failed and my extended ROM was deleted. After hours of resaerch I finally found your post and I have to thank you very much! With this small file now everithing seems to work as it should again! :)

I can only recommend it to everyone with the same problem!

Greetz from Germany! :)
[Galaxy S 4 Accessories] snotyak:
Can I use the Smart Dock Multimedia Hub when the phone has the Spigen SGP Neo Hybrid on?
[Galaxy S 4 Accessories] sna66:
I Would like to know too
[Galaxy S 4 Accessories] subhek:
+1 :)
[Galaxy S 4 Accessories] DuckMcQUack:
One of my housemates has got a neo-hybrid and no, I don't think so.
[Galaxy S 4 Accessories] dave106:
Got Samsung's Protective Cover+ on mine, which adds a little bulk all around. Fits fine.

Sent from my GT-I9500
[Galaxy S 4 Accessories] sna66:
i heard it fits but it wont charge