yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Angry Black Man:
i can't get past cm10.0 on my device. i've done this AWS fix stuff and have been happily using my phone, but i'd like to upgrade the software. whenever i install cm10.* (greater than 0), i get assert failure code 7.

-- Installing: /sdcard/cmupdater/cm-10.1.3-d2att.zip
Finding update package...
I:Update location: /sdcard/cmupdater/cm-10.1.3-d2att.zip
I:using /data/media for /sdcard/cmupdater/cm-10.1.3-d2att.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1"
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG2" || getprop("ro.bootloader") == "I747MVLDLK4" || getprop("ro.bootloader") == "I747MVLDMF1" || getprop("ro.bootloader") == "I747MUMBLK3" || getprop("ro.bootloader") == "I747MUMBLL1"
E:Error in /sdcard/cmupdater/cm-10.1.3-d2att.zip
(Status 7)
Installation aborted.

what CM10.1 or higher can i install on this phone?? how do i stop the assert fails?! i tried to just remove the asserts from the script, but then the installation fails without even giving an error code.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] New Optimus:
You need to update the modem, flash the newest modem then you should beable to update cm.

After that you will then reflash the older modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibuddler:
So can anyone let me know if this works for 4.3 roms?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
It's actually the bootloader (which shares an alphanumeric designation with the modem) that matters here. Search this thread for info on how to upgrade your bootloader to one that is compatible with CM 10.1 and later. There was a discussion about it a few months back:

http://xdaforums.com/showthread.php?t=1778270&page=261
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] New Optimus:
my understanding was you can't update bootloader without updating the modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
I think the converse is true--updating the modem doesn't update the bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cstone1991:
So a friend recently bought an unlocked SGH-I747 and asked me to help get it working on T-Mobile. The sticker under the battery says that it is an SGH-I747, the IMEI on the sticker matches the one that it shows in the About Phone menu, and the back cover has AT&T on it, however the model shown in the About Phone menu claims that it is an SGH-T999, the rest of the info in that menu also indicates that it is an SGH-T999 and it has the T-Mobile Apps that you would expect to see on an SGH-T999 as well as the WiFi Calling option in the menus that (to my understanding) would only be on a T-Mobile S3. Does this mean that this mod has already been done to the phone, or is it something else?

Here is the info that is shown in the About Phone menu:

Model Number: SGH-T999

Android Version: 4.1.2

Baseband version: T999UVDMD5

Kernel version: 3.0.31-1128078

sent.infra@SEP-128 #2

SMP PREEMPT Mon Apr 15 11:59:10 KST 2013

Build number: JZO54K.T999UVDMD5

Let me know if you need any other info. I have the phone currently, just no SIM card for it so I can do whatever you may need as long as it doesn't require a SIM to be inserted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
It looks to be a T-Mobile model since the Modem (Baseband) on there is a from a T999. You can't fake that. The model number you can fake, but not the modem. Even if this was an i747 and he flashed a T999 modem over, the phone would say unknown baseband, not show the IMEI, and not connect to the network due to different partitions. So yeah, it seems to be a T999.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cstone1991:
Interesting.... I decided to do some searching on this after you posted this and found this app:

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

That app claims to identify fake GS3s and the app confirmed that it is a real T999. Combine that with the fact that a couple sites I found said the IMEI belongs to a T999 and I'm convinced it must be.

I wonder why the heck the seller would have printed a sticker that claims it to be an I747 and put an AT&T back on it? Oh well, now to try to figure out why it was only getting Edge in a 4G coverage area. Thanks for your help!

Sent from my S3 using whatever is in the chamber...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
Trying to make a quick buck (scammer)? It should get EDGE and "4G" on both AT&T and T-Mobile, but obviously no LTE.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] getpierced:
anyone have a working mirror for this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RadicalDelusion:
Working with 4.0.4 but major video issues

I have flashed my AT&T i747 using the files that downgrade the OS to 4.0.4. The good news is that I am able to get 3G/4G on T-Mobile's network HOWEVER (and this happened before I flashed my phone), any version of Android prior to 4.3 causes the screen to flicker and black out occasionally. I took it to a repair shop and the tech there had the same issue with his phone and told me that upgrading to 4.3 or 4.4 using a non-cwm rom fixed it. I can confirm that it fixed the problem for me as well. Now I am stuck in a conundrum. I have to choose between horrible data caps/throttling or unlimited fast data with intermittent screen problems. Has anyone been able to keep this method working with a 4.3 or above ROM? I did manage to upgrade to AOKP's stable 4.3 build and the device info still says model T999, BUT, the baseband says i747. This was the only TMO based ROM that would actually install after the 4.0.4 fix. My TMO account is not active since the video issues were too risky. Straight Talk throttled me after 4 days and I only used their data on ONE day. It was obviously their error but they refuse to fix it. I NEED to get back on TMO but 4.0.4 just wreaks havoc on my screen. Does anyone know of any custom GPU settings that could fix this so I can revert to 4.0.4? Has anyone else encountered this problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
doubtful this would work because most 4.3 roms need 4.3 modem but... you could try flashing the 4.3 rom then flash just the modem and csc file from this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
I can't get this to work at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yu203964:
Samsung Tab3 T211 with 3G

Hi:

I am using Tab3 which is also using Android 4.1.2 and rooted and unlocked. I want to use Wind Mobile's AWS. Can this method work for my Tab? If not, is there other discussion about how to mod Tab3? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jjohn7293:
RE i747 Flashing

would we still have the 4g signal if someone were to install custom recovery and flash an aosp rom???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bit1:
Wrong forum. Hardware is completely different. Go to the forum for the Tab 3. Flashing different hardware modems and bootloaders can result in an expensive paperweight. Read the stickies and faq when you get there. Good luck!

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

Yes you would. ROM's don't flash new modems and bootloaders typically. You can flash anything unless it says you have to be on MJB or MJ2 in which case you will lose this. If you're in a metro area though T-Mobile's refarm has gotten pretty good. I finally bit the bullet and upgraded to 4.3 and typically have LTE in most areas I travel to and it knocks down to HSPA in the sticks but it's still at 2-3 mb which suits my needs just fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
So no hope for 3g aws on 4.4 Roms?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jjohn7293:
I just tried it but no luck :(

Does anyone have a list of compatible roms with the bootloader???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jjohn7293:
The KitKat version of CyanogenMod does not say it requires a specific loader. However, when I try to flash it says there is an error when getting the device model from the bootloader

---------- Post added at 08:01 AM ---------- Previous post was at 07:39 AM ----------

Will this work???

http://xdaforums.com/showthread.php?t=2388065
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jjohn7293:
My above post works!!!!!!!!! Jellybean 4.1.2 with ongoing 4G :) just flash in twrp like normal
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] forevergone:
In QPST, it currently says no phone:

What can I do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Anyone have the mod working on a KitKat d2att ROM? If so I'd appreciate the step-by-step. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
No...I've searched for hours and couldn't figure it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monera96:
Ok look... someone is selling the aws mod on ebay for 30 bucks a pop....

http://www.ebay.ca/itm/Enable-AWS-f...LH_DefaultDomain_2&hash=item1c3a164c8f&_uhb=1

-_- wow
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] boss315man315:
I have VERIZON 4g lte working on my AT&T GALAXY S3. BUT I CAN'T get CALLS to WORK
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cstone1991:
Verizon uses CDMA for calls still (and I think SMS as well) I don't think the SIM allows connection to the CDMA network by itself, I think a different part of the phone does that. I could be wrong, but this is my understanding.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
You can't because Verizon uses CDMA for calls and texts, which your AT&T model can't do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akakig:
Thank you for the post, good for fido phone for wind mobile.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] forevergone:
Does anyone know if this custom rom will work with the AWS mod on 4.3?

http://xdaforums.com/showthread.php?t=2121506
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
I haven't found one that works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] forevergone:
Do you know if flashing ROMs that do not flash a new bootloader or modem will affect the NV Data?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SaHiLzZ:
It shouldn't affect the mod. However, you should be able to run the files again if it happens to lose it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] a sandwhich:
What is the correct up to date way to enable 3g/4g access on an I747 now? I just switched to t-mobile and I can only access edge on CM11.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
I tried flashing an older modem but that didn't work. So no idea...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] a sandwhich:
Where are the up to date roms to enable LTE support on the AT&T i747 for T-Mobile? And what is this risk of completely bricking the phone? Is it possible to do this while running CM11?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Look back a few pages. I've been told no.

I'm on CM11 (Vanir) and I get LTE, HSPA, and 3G without the mod. You must be in a smaller city or rural area. When I'm out of the city it goes back to Edge because TMo hasn't refarmed those towers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] a sandwhich:
Well, I have a friend with a t-mobile purchased phone who gets LTE access all around this city. Is there a way to check if t-mobile has refarmed these towers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
The att version does 1900 band fine but the mod enables 1700 to work on some tmobilr towers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ssy080:
i747m

Hi, thank you for the method!

Anyone know if it would be possible to use Tasker app to run the script if 1700 radio is disabled?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
Not officially, but you can use http://airportal.de to see what users have reported. Bear in mind that this is user-generated, so there may be a lot of areas that have LTE but aren't reported. That being said, LTE areas are also refarmed 99% of the time, so you should get HSPA+ ("4G") in addition to LTE on your AT&T S3 in the same places that your friend gets LTE on his T-Mobile S3 LTE.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procrastistamper:
Enable 1700 AWS on stock (rooted) 4.3?

So, I just got a new factory unlocked AT&T I747, when I should have gotten a T999L to work on Solavei--which basically uses the T-Mobile network. I decided I am okay with the stock ROM (with root), though I do want to try some "desamsungizing". I went ahead and updated to stock 4.3 and did CF-Auto root. I understand that once you go to stock 4.3, you can't downgrade the bootloader. And if you use the files in the OP, that is an old bootloader. So, am I just screwed at 4.3 now, or is there some other combination of magic (or files) that will work for me to enable the 1700 band?

I understand there is also an NV backup method that works, but you have to re-enable after each boot http://xdaforums.com/showthread.php?t=2344627 but I can't even do that now because the code *#7284# no longer offers the options in 4.3 that are required for that method. And, the alternate diag scripts would not work for me on CM11, either. Isn't there some way to partner these methods/mods/discoveries together in a new set of files...somehow...? (Sorry if that's a dumb question, but I am a n00b.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jinxhyped:
1. The issue with it not sticking on reboot is limited to the i747m (Canadian) variants. So you should be ok there.

2. On 4.3 touchwiz (stock & custom) try *#0808# to access the rdnis/modem settings menu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
Just to clarify. .

Nv data is reset after reboot but will stay(stick) until the next reboot. As long as you nvrestore reboot each time it will be ok.

I747m will reset after reboot and not wait till next reboot. it changes back after a few minutes. (Not sticking after reboot)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jinxhyped:
No need to clarify what I say with wrong information.

I have been running this mod on a virgin (bell) i747m since September across multiple roms & bootloaders...and have not once lost aws until after a reboot without using NVrestore.

Thats using the Qpst method to inject T999L data onto the device, then running NVbackup BEFORE rebooting.

Currently operating on the 4.3 bootloader, using S3Rx rom & stock kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
Have you been able to run this on a 4.4 ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ben00:
I have been running this Mod (installed "I747 NV with AWS.qcn" with QPST, than NV backup NV restore) on my I747m from Koodo, running Stock, root injected RWC rom, for several months. I have no problem with the AWS (on Mobilicity) sticking. But after using the phone for a few weeks, it just started rebooting. Phone would power on for a few seconds, than reboot, and go on and on.. Restored the phone to original status, few weeks later started happening again. I have not done any other Mods to the phone.

Anyone else experiencing this problem??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SaHiLzZ:
Not heard of it. Have you flashed the official files?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ben00:
YES!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
NV Data is modem-level. That is, unless you have an i747M (since you need to reboot to flash a ROM), you're not going to do undo the mod if you flash anything except for a modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kvan99:
I747 running on T-Mo

Hi folks, forgive me if you're already answered this question in another thread but I'm a noob and some of the tech lingo is lost on me. I have an AT&T i747 which was rooted and with the 3 files in this thread and converted to a T999, I have elegencia rom on it still, I would have been ok with it but I noticed global roaming does not work on this rom, I recently traveled to Canada and I could not get my phone to sign on to another carrier. So I have 2 questions, first in the "About Device" menu it shows the phone as an SGH-T999 but the baseband shows i747UCLH1, (I imagine this is the modem version..?) so can I flash this phone with a T-mo custom rom for a T999, I'm asking because some of those roms require an updated T-mo modem, to be clear should I use a t-mo or att modems on this phone? Second question is does anyone know which rom will allow global roaming on t-mo? Thanks in advance...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jjohn7293:
I have done the mod and do get 4g with jellybean... But some service areas give me some odd signal... Can someone identify? It says 4g but runs slower then 2g. The name is umts and the only thing that the status bar had is just a crown icon...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kalel420:
Hope this will help the new PAC man ROM 4.4.2 d2lte will work with this mod I am running it now it can be found on the T-Mobile gs3 fourm or the PAC man ROM site.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jjohn7293:
Are you getting 4g on the KitKat ROM??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kalel420:
Yes I was also any of the d2lte roms will flash
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jjohn7293:
Perhaps you can help me with an error... I did flash omnirom but I had zero signal. Rebooting didn't help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
Perhaps some step by step instructions on getting it to work with 4.4.2 kitkat
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jjohn7293:
It works. I installed a different version (cm11 nightly) and it works great now. A few bugs but that's expected in a nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
So you installed the modem and all is good? When install it I get no signal. What boot loader you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jjohn7293:
You need to make sure you have already done the Frankenstein process. Make sure you have twrp and any d2lte ROM. I'm using cm11 nightly. There is no way of selecting a band that I know of, so that's a downside but it still registers on the networks by itself.

EDIT: I am now using the PAC-ROM for d2lte. It is simply amazing! Great signal for 3G (which is exactly what regular 4G is but with a "souped up" label) 4G lte, and WiFi hotspot works too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Angry Black Man:
im having the hardest time upgrading my phone from cm 10.0 to anything. all i get are assert errors (unless i install aokp which installs flawlessly and without incident). my phone currently has the AWS fix from this thread and i get all the signals that i expect on tmobile.

okay, so when i look at the bootloader through ADB, i get this:

C:\Users\Angry Black Man>adb shell getprop ro.bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
T999UCALJ2

this cm installation guide says that to install 10.1 and newer, the bootloader cannot be an ICS bootloader.

1) is T999UCALJ2 an ICS bootloader?

2) is the BOOTLOADER the same thing as the RECOVERY?

3) does anyone know why i get assert errors when trying to install? i get this error:

-- Installing: /sdcard/cmupdater/cm-10.1.3-d2att.zip
Finding update package...
I:Update location: /sdcard/cmupdater/cm-10.1.3-d2att.zip
I:using /data/media for /sdcard/cmupdater/cm-10.1.3-d2att.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1"
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG2" || getprop("ro.bootloader") == "I747MVLDLK4" || getprop("ro.bootloader") == "I747MVLDMF1" || getprop("ro.bootloader") == "I747MUMBLK3" || getprop("ro.bootloader") == "I747MUMBLL1"
E:Error in /sdcard/cmupdater/cm-10.1.3-d2att.zip
(Status 7)
Installation aborted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Product F(RED):
1) Not sure

2) NO. You rarely ever have to touch the bootloader. It just happens to be part of this mod. F*cking up the recovery = phone will still work, and you can restore the recovery. F*cking up the bootloader = phone hard-bricked and you need a JTAG service to repair it.

3) It's saying your bootloader is different from the ones in the list that is coded to recognize. Rather than flash anyways and potentially screw something up, it quit installation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Angry Black Man:
okay, a lot of information, but that does nothing to change my situation.

so let's try this from a different angle:

1) the bootloader that i specified... it's what this mod has given to my phone. i see people saying they have CM higher than 10.0. how did they get that using this mod??

2) you state you rarely have to change the bootloader. i'm trying to rule out this bootloader as the culprit behind my assert errors. i tried to flash a new bootloader from this thread:

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

but when i did, i got an error stating that the installation failed because it was looking for "d2att" and that i had ""

(that's right, two quotes with nothing in it. completely fucking frustrating)

3) i've tried to update the script to not even check the asserts and the installation still fails. what the hell am i doing wrong?

i just want to update to a CM rom higher than 10.0. i can install aokp to android 4.3 no problem so what's the problem with CM!? (please no one suggest something stupid lke "just use aokp then")
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Angry Black Man:
also, for ANYONE who has used this mod, can you let me know from ADB what bootloader it says you have? especially for anyone who has something higher than CM 10.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheStart:
I want to try this out, but I don't want to go back to stock firmware. Do I have to download the AT&T root injected firmware or T-Mobile root injected? Also, if you could post links that would be helpful, but if not i'll find them myself. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alepodj:
???

found any way to make it stick on boot up?

all methods i tried go away after restart the device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryansmith888:
ROM recommendations?

I have a i747 S3 att unlocked that I use on Tmobile LTE. Can anyone recommend a ROM that will be glitch/bugless and still keep my LTE ability? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] macklin345:
Hey guys does this work on 4.3 with the Knox bootloader version that can't be downgraded? Or will this cause a painful brick?

Because I know that down grading 4.3 bootloader will mess up devices.

It's a s3 i747 from att thanks guys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
You're right not to flash old tmobile rom and bootloader. It would brick. and if you have knox enabled still you probably are not rooted and able to use nvrestore method.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] macklin345:
No I am Rooted with Knox disabled. How would we get this to work on 4.3 bootloader with no issues?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] athlonxp2300:
All roms work with tmobile LTE. You just need the proper apn and tmobile sim card that supports lte.

If you are just looking for a great tmobile rom I like s3rx. Just don't flash bootloader or radio/modem. I use att leaked kernel also. Been very happy with it. I'm still back one version from the latest because it was just running too good to switch.