yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
I wonder if this seems possible.

http://xdaforums.com/showthread.php?p=42781523

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.

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.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Quite the interesting theory, I agree this would be a beneficial test, however until there is a stock odin for the T999L it would probably not be a good idea,

And not having the hardware present in the T999 it probably will not work. T-Mobile would not have had the need for the T999L to be released for LTE if this was the case, it may work between the note2 and s4 because they are both LTE capable.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
I know it would not be worth anything for t-999, that wasn't in my thoughts.

but it might be perfect for the att i747 to basically turn it into a T-999L
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
That would definately be a worthy test, however if the i747 also has no stock odin rom, my comment still stands as to it being a bad idea before Having a stock odin to reflash with. ( I do not know anything about the i747 other than that it is an s3 variant and holds much of the same hardware as others, let me know) either way cross referencing data, from this thread to the i747 thread, for such purposes would be a much better idea than to continue posting this in the thread for the T999L .
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
Point taken. looking forward to the stock Odin for T-999L, or at least a CSC file. Thanks for your work and Thanks for the info.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Correct me if I'm wrong, but isn't the I747 more identical to the original t999? Don't forget, the T999L has an entirely different SoC. I believe this is why when you flash the LTE radio to the T999, you get zero connectivity. Not even a cell signal. I think it would be the same for the I747.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
you could getprop from i47 and look for the hardware specs and be pretty much certain if would work or not, I think. If it has the same modem as the t999 then would be a moot point.

-Sent from the Hairy Transformer via a wicked awsome Galaxy.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Nope its LTE according there gsmarena.com
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
I'll see your screenshot and raise you a stock file !!!

.. for the t999 Doh!

-Sent from the Hairy Transformer via a wicked awsome Galaxy.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Although I will say, based on my past network experiences LTE is not usually expressed in Mhz (even though that's what the 1700/2100 stands for) usually when a network is called out in Mhz its only HSPA+ at best, gsm arena could be wrong as they list the i747 as 700Mhz but then call it to be 1700/2100 unless they are meaning the 700Mhz to be for HSPA+ and simply didn't separate the two "4G" networks as different technology. Nice stock file though, lol, I know you saw my erroneous post about LTE speeds the other day, so its all good.

---------- Post added at 08:11 AM ---------- Previous post was at 08:05 AM ----------

BTW, I hope you didn't take my quote about the i747 as hateful angry or rude I just thought it would help us to keep the forums less fragmented between devices
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
According to Samsung specs, the t999l lte bands will be on 1700 and 700 frequencies Band IV and Band XVII so I don't believe the i47 using the 2100 band for lte will function, and they are calling it the t-999zaatmb for some silly reason. Sorry I thought I found you fellas a stock file to goof with but I was mistaken.

-Sent from the Hairy Transformer via a wicked awsome Galaxy.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
I wonder if that t-999zaatmb might actually be the elusive modem version there is no info for when using getprop?

I want to say I have seen that model number somewhere in a specsheet for a firmware, I will see if I can find it again and post thd results later, I want to say I googled the MSM8960 BOARD and came up with that in one of the spec sheets given for the board.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
could be.... samsung states that version is the pebble blue tmobile version but tmo doesn't even offer one (yet). perhaps they are waiting for the full LTE rollout before releasing the pebble blue version and then making available ota's for only the blue ones with that mystic modem that can tell which color the plastic on your phone is with nanotech nfc tags embedded at the atomic level.

:p

-Sent from the Hairy Transformer via a wicked awsome Galaxy.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
Yo Moto,

Chech this and compare to what you get. Here are a few screens:

Sent while sleeping in chair.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
not sure why it is reading i747 on my t999...?

-Sent from the Hairy Transformer via a wicked awsome Galaxy.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
What app are you using for that?

---------- Post added at 09:04 AM ---------- Previous post was at 08:54 AM ----------

Possibly because the i747 was the first LTE enabled S3, so the T999L could just be a carrier variant, with small un-similarities.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
it's a play store app called 'cpu identifier'

it requires no permissions and the author is ON THE SPOT with updates.

it's just odd because I do not have a t999L...

-Sent from the Hairy Transformer via a wicked awsome Galaxy.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
it also states SAMSUNG M2_ATT

-Sent from the Hairy Transformer via a wicked awsome Galaxy.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
This is what I get.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
Yup. Your build.prop is saying m2_att as well. That is stock rom only rooted correct?

Sent while sleeping in chair.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Absolute!
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Here are screens of terminal su getprop
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
Do the cpu evaluate in that app from screens and send results to dev by mail (click button). He will update overnight and release update tomorrow or next day and we will re-run and see if it detects different. I'll bet you will be first t999l he recieves.

Sent while sleeping in chair.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
Not at all. I get frustrated seeing the t999 post here wanting to enable lte when it doesn't have the hardware.

i747 has band4 lte support. It can do hspa on AWS band 4 also but that was disabled by the csc file and modem.

T-Mobile used the i747 to test their Lte network before the t-999L was out. There is an engineering set of bootloader, rom, modem, and csc files that makes the i747 work on all T-Mobile frequencies. Although I think it is only hspa +21 not +42

Flashing the engineering csc file and modem works with newer roms. That is why I was interested about if the t-999L is the same hardware.

It is interesting that your hardware version shows rev0.4 like my i747.

Should a new thread be started comparing and testing hardware/firmware for i747 and T-999L. ? Then these posts moved there?

original i747 build.prop
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Sent it, we will see what happens.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
I dont believe the 747 can do lte on the 700 mhz band and tmo is using 700/1700 for that.

Sent while sleeping in chair.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
I thought tmo backhauled the 700 for further expansion of their HSPA+ just kidding, they backhauled the 2100 for HSPA+ expansion.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
hspa aws 1700/2100

refarmed areas hspa 1900

LTE band 4 AWS 1700/2100

I get tmobile LTE no problem with my i747
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
There it is, I knew there was a spec sheet on it somewhere, even though I was WAY off.
[T-Mobile, Samsung Galaxy SIII] upncoming:
This is an interesting idea and sounds plausible. I have a spare I747 board to test with if anyone is willing to share their NV data backup. I'd love to give it a try.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Definitely an interesting idea but doing so might cause their device to be carrier blocked if the network detects two devices with the same imei
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
He should not use your imei but the original from his spare board. He will have to edit the nv back up to insert his imei. That is assuming his spare board has it's own and not the same as his daily i747. To be safe whoever gives the nv back up should remove that line.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
Sounds interesting

Sent while sleeping in chair.

---------- Post added at 03:44 PM ---------- Previous post was at 03:44 PM ----------

Ill share...gimmie some time

Sent while sleeping in chair.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
Just to be clear...

It needs to be a nv backup from a T-999L not a T-999.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
OP Updated!!!

Added the following to the OP:

Recovery

Secure and Insecure Kernels

Firmware

Instructions for how to return to stock will be in OP#3 shortly.

The Kernels remain untested. But they were made using a known good script and I have very high confidence they will work just fine.

The Firmware also is untested.

Thanks to Aerowinder and enewman17 for allowing me to use/mod their scripts for some of these!
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
In that case, you may not have mine and you are restricted from ice cream for 3 days.

:what:

Sent while sleeping in chair.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Well, since Doc and I started this whole mess with my T999L if you can give me a link to a safe guide for doing so, I would be glad to get you my nv data minus the imei so you can test it out. If you can use a dd of that partition I can get it for you that way, otherwise I will need a guide. If the dd will work just let me know the mmcblk0pxx partition to dd and I will do It later tonight when my kids go to sleep.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
Don't forget to los3 the device iD also Moto, if there is such a thing.

Cheers to all this' thread readers tonite. It's been a long week and we've all worked hard for the man. I'll have a rum drink for you if you'll have a beer for me.

:p

Sent while sleeping in chair.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
Hopefully upncoming has info for you. He was willing to try this.

This is all I have.

http://galaxynote2root.com/galaxy-n...3g4g-aws-bands-on-att-galaxy-note-2-sgh-i317/
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
[MENTION=5102237]upncoming[/MENTION], I assume you're going to have to use your own IMEI from your daily driver, so don't forget to power of your device, while you are testing, you wouldn't want to carrier block your own device.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Run this in terminal emulator:

echo "";
echo "Creating backup directory: /data/media/IMEI Backup.";
mkdir -p "/data/media/IMEI Backup/temp/";
cd "/data/media/IMEI Backup/temp/";

echo "Commencing backup...";

echo "Copying mmcblk0p11: efs";
dd if=/dev/block/mmcblk0p11 of=p11_efs.img > /dev/null 2>&1;
echo "Copying mmcblk0p12: modemst1";
dd if=/dev/block/mmcblk0p12 of=p12_modemst1.img > /dev/null 2>&1;
echo "Copying mmcblk0p13: modemst2";
dd if=/dev/block/mmcblk0p13 of=p13_modemst2.img > /dev/null 2>&1;
echo "Copying mmcblk0p20: backup";
dd if=/dev/block/mmcblk0p20 of=p20_backup.img > /dev/null 2>&1;
echo "Copying mmcblk0p21: fsg";
dd if=/dev/block/mmcblk0p21 of=p21_fsg.img > /dev/null 2>&1;

echo "Copying efs folder...";
cp -pr /efs/ efs/;
echo "Copying radio folder...";
cp -pr /data/misc/radio/ radio/;

datetime=$(date +'%Y%m%d_%H%M');
echo "Compressing backup (backup_$datetime.tar.gz)...";
tar -chzf "/data/media/IMEI Backup/backup_$datetime.tar.gz" *;

echo "Cleaning up...";
rm -rf "/data/media/IMEI Backup/temp/";
echo "Backup complete!";
echo "";

My personal nv backup script. Will have to find and edit your device specific stuff.
[T-Mobile, Samsung Galaxy SIII] upncoming:
Man, you boys have been busy. :D Sounds good to me, but it's a learning experience for me too. I'll see what I can find about getting the info you need. I'll work on it once my kid is in bed (Hopefully soon).

I'll use a spare phone that was waiting for a new screen assembly to test with. Luckily, that came today so I won't have to swap out my board. I'll just build a new phone. Fixing broken ones is my main hobby.

I'll let you know once I've had a chance to figure this out. Thanks a ton for helping with this!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Want Mobile Odin to Support the T999L?

Hey guys,

Some of you may already know about one of my all time favorite apps,

Mobile Odin

. <-----Click Here to go to Chainfires Mobile Odin Thread.

If you do not already know about it, I highly recommend you take a look at his thread. Basically, it allows you to flash firmware, zips, OTAs. It can even take the stock firmware and inject root during flash. (it will not get you root, as you have to be rooted already to use it). So it is an app, that can almost completely replace your custom recovery CWM/TWRP. (the only thing it doesnt do is nandroid)

Currently, you cannot use it on the T999L, but I think he will be able to easily add support for it since it is so close to the T999. But first he requires a few things.

See post 4 of his thread for more on this.

I already have everything he needs except the dump file. If someone would be willing to get this, I can pass it on to hopefully get your device supported on the next update.

All I need you to do, is download Mobile Odin from the thread and install. (Dont worry about the flash kernel. there isnt one for the T999L....yet!) When you open it you will see a message stating the device is not supported and it will give you the option to create a system dump. Click yes to proceed. This can take up to 30 minutes!

Once complete you can upload the dump file here and I will add it to everything else he needs and post it in his thread.

http://xdaforums.com/showthread.php?t=1347899
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Its dumping now.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
awesome!

And you actually have everything I've got, (assuming you still have the pit file) so it's up to you if you want to post it in his thread or if you want me to go ahead and do it.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
I never had the pit file, but if you can tell me how to get it, I will do it.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Oh that's right. I got it from someone else before we started working on all of this. Of course. The one thing I didn't get from you!

Anyway, I'll let you know how when I get back to my computer. It's easy, just can't recall off the top of my head.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Request for T999L support posted in Mobile Odin thread.
[T-Mobile, Samsung Galaxy SIII] burkebacar:
Flashers beware

Hopefully someone can help, speculate, or take heed. I'm not a total noob, but still a novice.

So I received the coveted T999L from an insurance claim and headed straight here for some flashing goodness!!

I first started with rooting and flashing TWRP recovery via mskip's unified tool box. Then I tried flashing evil1art's Wicked v10, like I had on my T999, all was well set-up trucked along, everything working fine, until I tried to use the camera. It seems that gets broken in the flash process, it popped the message that storage was going to go to the SD card, then black image area, and then a message that the camera had failed. I tried wiping cache and dalvic, as well as fixing permissions, and then flashing different camera options within the Aroma installer with no luck.

Thankfully due to Doc and Moto's work I was able to restore back to stock rooted.

I may have missed something or messed something up, even though I've been at this since my Captivate days, so I like to think I know what to do. Any ideas are welcomed!

As soon as I can raise some capital you two are getting some beer money as you saved my phone!
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
I am having the same camera issues with CM10.1, still looking into that, might have to take the camera out of the Deodexed ROM and try that.
[T-Mobile, Samsung Galaxy SIII] upncoming:
Well, there's not much out there on guides for removing the imei from a .qcn file. I pm'd sjravi, the guy that did this for the note 2, to see if he'll share how he removed the imei from his backup file and made it so anyone can upload his .qcn file and keep their own imei. I'll let you know once I have that info. Then I can lead you to a guide for backing up your nv data with qpst, you can remove your imei, and I can finish the file so the new imei doesn't have to be entered.

At least, in a perfect world that's how it would work...

Besides that my test phone is built, unlocked, and ready for action. :cool:
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
incase he doesn't get back, this is the thread I was following to back up mine.

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

on the i747 line 0550 was the imei. they said to delete that line.

I need to verify if we can just write it back with that line missing and it doesn't over write it in the phone.

It would be cool if we find out that the i747 is actually a lot closer to t-999l than the t-999 is.

it would also be cool to basicly flash the entire t-999L except the imei. and turn the I747 into a T-999L
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Try replacing wickeds samsungcamera.apk and camera data folder

with the ones in the T999L rom. May be easier to put it in and flash so permissions are correct.

For cm, try this with just cameradata folder. I can look at it better later on.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
The camera app won't work on cm. Its dependant on touchwiz framework.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
FYI, I just flashed cm-10.1-20130622-NIGHTLY-d2tmo on my T999L and the Camera works perfectly. I have found that everything that I have tried works. Thank you all for the help.

---------- Post added at 04:09 PM ---------- Previous post was at 04:05 PM ----------

I did find one thing, not really an issue, but the build.prop still has T999 instead of T999L, I'll edit it just because I'm particular like that.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
All T999 roms will report being a T999 regardless of the model you flash it on. Shouldnt be too big a deal, just be careful with apps like Mobile Odin.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
I figured that it was just a semantics-type of thing, but I changed it anyways. Thank again for your help.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Okay new project! Looking for people to help with technical data analysis, my wife has an unmodded T999 she just got the update with multiwindow support, I'm going to adb pull it and see about sideloading through stock recovery to the T999L if it doesn't work I will need someone who can analyse the framework and kernel of the T999 4.1.2 rom against that of my T999L 4.1.2 rom and see what we need to do to get it ported over to the T999L I know this is something we all want, and with no update for the T999L in sight I would just as soon try porting it than wait for sammy to update us. Pm or quote me in the tread if you want to be part of this project. It could be as simple as pulling an .apk and the odex for it, it could be as difficult as swapping versions of touchwiz without breaking hardware permissions, or worse.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
You might want to check out this thread.

http://xdaforums.com/showthread.php?t=2276645
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Just a few things real quick because I don't want to see you wasting your time on something that I know can't work.

First, since you're rooted you can just copy the update.zip from /cache/fota

(I already have all the otas in my firmware thread btw)

(Oops never mind, just checked and I never posted the last one, sorry. Will try to get to that in a bit)

Also, there is no way thst the LJC-MD5 OTA will work on your phone. The OTAs are 90% patch files. Meaning there are very few full system files. They package up only the code changes they make and then the update simply applies those changes to your existing files. So it is specifically only for updating LJC to MD5 on the T999. If you were to try, it will fail. If you gind a way to force it, you could brick, but would definitely end up at the very least needing to flash the FULL stock firmware.

Also, that ota is patching 4.1.1 to make it 4.1.2. Since you're already on 4.1.2, it would make it even more difficult as a large amount of the code changes would be worthless, and you would have to figure out for each file what is and isn't needed.

I honestly think you would be better off just flashing the MD5 rom. Everything shpuld work fine. And if it doesn't flashing the kernel and modules I posted should solve most problems.

I'm not sure why you are wanting to compare the kernel and framework of the two. It just seems like an awful lot of work to me when there is a much easier way to get T999 features.

You could try swapping out jar and apk files, but with how tied together the tw framework is you might wind up with some things not working right.

Don't take it the wrong way, just trying to help save you from what I'm pretty sure would become one helluva headache!
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
That is why I suggested the other almost stock, rooted md5 rom with multi window.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
yup... the moto could use the stock aroma v2 rom without the modumb and get the stuff he wants and even pick and choose his own bloatiness. the doc will correct me (not like in the Shining please) if I am wrong.

-Sent from the Hairy Transformer via a wicked awsome Galaxy.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
He would like that one better but unless he updates the aroma script or modifies his build prop it may not install. I had problems with that because I wanted to use all t-999 options on my i747. Failed asserts. :( the othe one worked but I would recommend stockorama v2 anyday. It's my daily. Just had to force it.