yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] :
I used this app to backup and delete my APNs: https://play.google.com/store/apps/details?id=com.riteshsahu.APNBackupRestore

---------- Post added at 04:43 PM ---------- Previous post was at 04:39 PM ----------

That could explain it, then. Unfortunately, my APN settings no longer work. I've even tried to play with some of the other settings (I.E. switching Bearer between LTD and Unspecified; changing APN type, etc.). For some reason, it won't let me have data connectivity anymore. I'm going to restore to my last Nandroid backup. :crying:

So, I'm all out of ideas. Sorry guys...gave it my best shot. I had LTE for about 5 minutes, but what a sweet 5 minutes it was. :p
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Don't worry, you have at least confirmed the

T999 is capable, now we start to look for a patching solution to get all you T999 users running on LTE
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I may be way off here, it's been over a year since I messed with any of that, but isn't the qcn file basically text? Maybe it would be as simple as changing the extension?
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
In that case, I will load this to my dev-host in a few minutes

---------- Post added at 09:47 PM ---------- Previous post Here it is, nvdata backup, !!!! Removed link for further testing!!!!!!
[T-Mobile, Samsung Galaxy SIII] achmedkb01:
I used the link that you pm'd me.....the output file was in text from. The NVBACKUP worked on my phone as text.
[T-Mobile, Samsung Galaxy SIII] upncoming:
Huge thanks to achmedkb01! And another for you Moto! Did he use nv r/w? I haven't played with it before, but I can give it a try. The IMEI was just overwritten and not deleted, right?
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Good to know, for all you i747 boys here it is courtesy of achmedkb01 make sure you hit his thanks button
[T-Mobile, Samsung Galaxy SIII] achmedkb01:
I used this link to do the back up
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Qpst working on win8

SCORE!!! got QPST to work on win8, so for our phone to download the nvdata backup you have to select PDA in the util window on the phone and set it to RNDIS+DM+MODEM this will list your phone as SURF8960 in the active phones tab in QPST configuration. from there everything else is the same..

this should have made sense to me earlier since the modem has no version., i will see if i can get the hex editor to work, rewrite the blocks needed and get it up today.

here is the .qcn file from my phone i have rewritten line 550 and 1708-1710 to 01 http://d-h.st/ZKb
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Just curious what you mean by the modem not having a build ID? It should be whatever is listed as the baseband, which ought to be T999LUVAMB7 if I'm not mistaken.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Sorry, no version. I will correct my post

---------- Post added at 02:37 PM ---------- Previous post was at 02:35 PM ----------

No, his line 550 was deleted that's the .txt my .qcn just has line 550 & 1708-1710 hex edited to read 01

So the nvbackup.txt its been deleted, the nvbackup.qcn has been overwritten with a hex editor
[T-Mobile, Samsung Galaxy SIII] achmedkb01:
Sorry to get off subject but, has anyone heard/read anything about multiwindow on the t999l?
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
As of now I believe the only way to get multi window on the T999L is to flash a T999.md5 ROM not positive on that though.
[T-Mobile, Samsung Galaxy SIII] achmedkb01:
So flash t999.md5, flash t999l modem? Anything else I need to flash?
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
I believe that will work, but I would check with Doc on that he knows more about it than I do
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Just flash a T999L Rom. None of the roms should include modems so you shouldn't need to flash it.

If it is a touchwiz Rom, you may have to flash one of the kernels w/ modules in our OP here. I would try the MB7 KERNEL+ first and if anything doesn't work right or it seems unstable or laggy, then try the MD5 kernel+. If the Rom includes a kernel or if it's cm/AOSP, you shouldn't need to flash one from here.

Cm & AOSP kernels are not compatible with TW and vice versa.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
[MENTION=4686900]achmedkb01[/MENTION] For your safety I killed the link to your backup, upncoming has confirmed the .qcn I finally was able to pull worked, use this link http://d-h.st/cCs as I know for sure its safe for public consumption, he should be posting a how to soon in the i747 thread with a small description and a link to it here. He is going to test a little more before he does anything just to make sure its not a one off kind of thing.
[T-Mobile, Samsung Galaxy SIII] New Optimus:
So quick question the NV back up you have done, if I had the i747 att phone I would connect it like you have to QPST and back up my nv items then restore yours?

That is the theory right?

I dont have one yet. I am looking for either the T999L or the att as LTE is now live here and I want it.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
I know what I did to back it up, I don't know what upncoming did to make it work, he will have to answer that one for you. I'm not sure but I think you have to add your IMEI to the .qcn and then backup and restore, but I'm not sure if that's all.
[T-Mobile, Samsung Galaxy SIII] achmedkb01:
Thats great! Awesome work Moto!
[T-Mobile, Samsung Galaxy SIII] New Optimus:
I have worked with QPST fairly extensively, Though it was on cdma phones. The esn work especially, like the IMEI wont get over written unless it has been been changed to 0000's That seems to be the consensus on the note 2 how to's I was reading.

But even if the imei needs to be added into your back up, you just (in hex writer) re writ yours to 01's correct. just open in hex and write the correct imei for my phone.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
yes it should be that simple. just make sure you restore the copy you write the correct IMEI to you device to.

---------- Post added at 05:41 PM ---------- Previous post was at 05:33 PM ----------

where you quoted me on the link i just updated the link so its now incorrect where you quoted me, sorry i went back in and rewrote the 01's to all 0's

---------- Post added at 05:43 PM ---------- Previous post was at 05:41 PM ----------

@ upncoming i am working on the other backup now with the CDMA tool i will load it up soon too!:highfive:
[T-Mobile, Samsung Galaxy SIII] upncoming:
Thank you guys for all your help! The NV data backup worked to enable AWS on 1700 MHz for the I747. Not only is this much easier than our old way, but we can now use newer modems, and even the guys with Canadian variants can use this (Previously couldn't get 4g on 1700 MHz). Thanks Moto for getting us the NV file, and another big thanks to DocHoliday77 for putting up with us in his thread! Here's the dedicated thread for this now: http://xdaforums.com/showthread.php?p=43100050#post43100050

Thanks again guys!
[T-Mobile, Samsung Galaxy SIII] achmedkb01:
This are my speeds for my T999L.... I'm in Puerto Rico...any suggestions on how to make them faster?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Look over the first few posts of my modem/baseband thread. In particular the section about how to adjust some values in your build.prop.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
That's awesome! Good work guys! No worries on all the posts here, it was a good place to find help from people willing to do the extra work on a new device. As long as it was productive and not just wasteful posting, I've no problem at all with it!

Great job again!
[T-Mobile, Samsung Galaxy SIII] jmcoffey:
Did this die? Lol. It's been quite a few days.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
No its just been a battle getting the firmware to cooperate, we are still actively working on it.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Nah not dead by a long shot!

I will admit, I did have to take a day off from racking my brain on it!
[T-Mobile, Samsung Galaxy SIII] jmcoffey:
Well, I have a T999L but no access to a computer. if there is anything you need, just let me know! :)

Sent from my SGH-T999L
[T-Mobile, Samsung Galaxy SIII] New Optimus:
its too bad your so far from me, I have all the computer programs needed, Full version CDMA WORKSHOP 3.9, QPST,QXDM, and a few others could get lots of information from your phone.

But im in Jacksonville FL.:laugh:
[T-Mobile, Samsung Galaxy SIII] jmcoffey:
Lol. That's by the panhandle. Right? Only a few hours away from here.

Sent from my SGH-T999L
[T-Mobile, Samsung Galaxy SIII] New Optimus:
No east coast, just south of Brunswick. and couple hours south of Savannah.
[T-Mobile, Samsung Galaxy SIII] jmcoffey:
Still fairly close. But anyway, could I do anything with a Linux install? I don't own a copy of Windows.

Sent from my SGH-T999L
[T-Mobile, Samsung Galaxy SIII] New Optimus:
How familiar are you with linux? I am not sure on how to do several things (like pulling nv info) from the phone using linux.
[T-Mobile, Samsung Galaxy SIII] jmcoffey:
Fairly familiar. How do you do it on Windows? I can usually translate Windows commands to Linux.
[T-Mobile, Samsung Galaxy SIII] New Optimus:
You may be able to run a virtual machine.

To get those items you need windows programs, QPST, QXDM, and very helpful CDMA work shop. though this post has a nv read write tool that is similar to cdma workshop

http://xdaforums.com/showthread.php?t=1804117
[T-Mobile, Samsung Galaxy SIII] New Optimus:
I ran dhex on the T999L and Att modems but unfortunately I could not pick out any obvious settings I dont know enough about them If you do it may help.
[T-Mobile, Samsung Galaxy SIII] jmcoffey:
When I have some free time I'll toy with this. :)
[T-Mobile, Samsung Galaxy SIII] New Optimus:
:good:

The more the merrier right.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Hey guys, what is it we are working on, perhaps I can give you a little insight.
[T-Mobile, Samsung Galaxy SIII] New Optimus:
The nv settings that allow the I747 to connect to 1700 mhz tmobile get overwritten on boot so we are trying to find where the overwrite comes from, see if there is

1. A way to stop it

2. A way to use it to inject the correct setting instead, or

3. change the setting in the modem that locks out that frequency.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
Be careful... as eschelon wrote once... 'we don't want to REALLY piss the carriers off'.

:p

Sent while sleeping in chair.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
I think you might be more likely to find that in the csc, or in a manifest for the framework, it could possibly be written into one of the modem drivers as well, also could be in the secondary bootloader sequence, I don't know what line it is I will try to be more specific when I get a chance but if you compare the qcn for tmo and att the only difference in nv items when using the compare option of qcnview from qpst the third or fourth line from the top shows one carrier to have an 04 & the other to have an 05 written to one hex location of the nvitem in I believe its hex 08, just thought I would throw that out there, you might run a getprop on both devices and see if there is a major difference. It could also be in the pbl which we don't have access to currently for the T999L it may also be in the qcommbootinit.sh, you might also try using this app to backup and restore the nvdata before rebooting and see if it sticks http://d-h.st/yym
[T-Mobile, Samsung Galaxy SIII] New Optimus:
I have done this on both stock and on cm roms I looked through the boot.img could not find anything (not that means much there is so much there I could have missed it) I have found the item your refering too.

http://xdaforums.com/showpost.php?p=43320359&postcount=55

I used that app to restore nv items without the need for a computer, works fine but as always after boot the values are reverted to stock.

So to make it clear.

Connect the phone up to the computer, put it into diagnostic mode and a com port is available use QPST to restore the t999L backup when QPST completes it tries to reset/reboot the phone but fails at that point you can manually reboot the phone, but if you use that app to backup nv first the values that you just put in are put into the backup, the phone reboots and boots up with 1700 tmo frequency working, however during the boot process(after the 1700 band is made available) something is injecting the original values back in, so the next reboot it boots up into 1700 disabled.

So at that point if you use the nv backup app it will reboot the phone and your 1700 is back up and running, but if you look at the nv files they are again back to original so next reboot 1700 is gone.

I hope that makes sense.

---------- Post added at 10:24 PM ---------- Previous post was at 10:15 PM ----------

Oh and as a interesting side note.

If you use that app to save the nv on stock rom then you put cm rom on, doing a back up of the stock rom first, fully wipe and then install cm run the nv back up to restore your previously saved nv the phone just goes into a boot loop.

So something in the backup is rom specific.

Also I did a full wipe and put cm on then used the script to open diag mode and ran the t999L backup reboot the phone and 1700 tmo works, but restart and its gone.

I also did the cm enable com script ran the t999L then ran the nv backup app and it would restart 1700 was there on reboot it was gone just run nv app restore and it would reboot with it back up. but that nv restore would not work on stock, just cause boot loop, I even went so far as to test put stock on put nv app on did the back up and then did a nandroid backup and then put cm on did the nv back up and then did a nandroid back up of that.

so then restore stock nandroid and though nv backup might work still, nope it would boot loop.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I bet the cm issues are because once youre on that rom, it claims to be a T999. (Unless youre using an att rom, then itll report itself as the att model most likely) Try flashing a tw rom based on the T999 firmware and try it again. If it bootloops, that's probably the issue. If not then its probably safe to forget everything I just said!
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
I wonder if it has anything to do with the persistent cache here's a screenshot of the only file in it.

While I know bt usually stands for bluetooth the fact that it is .bt seems like it may be a persistent cache of the nv.bin that is run [MENTION=434273]boot[/MENTION] which would explain why the settings stick for first boot, but go away after a reboot, I wonder if you could place a copy of this folder from the T999L on the i747 in place of the i747's if it would stop this from happening. If you want to try it I would strongly suggest using adb to pull the file from the i747 to the sd, that way if it bootloops you just go and do this to get out of the loop. Reboot into recovery don't choose an option (only try this after you have confirmed that adb sideload is a recovery menu option for the i747)

adb.exe

Adb devices

Shell

Su

rm /persist/.bt_nv.bin

Then use adb install command to push the original back to the persist folder, please don't try any of this if you aren't familiar with most adb commands and shell commands! Unless you are at the least familiar with odin flashing which I think most of you are.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Well, id assume it has to do with Bluetooth of course.

But, ass.u.me!

You never know unless you investigate!
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
I'm willing to interrogate the suspect if anyone knows how to open this .bin file in a readable format
[T-Mobile, Samsung Galaxy SIII] New Optimus:
I will give it a try, yes fairly familiar with adb going to wait a day or so though been busy with the phone didnt get other things done, and you know those honey do lists :P

---------- Post added at 12:26 AM ---------- Previous post was at 12:23 AM ----------

I tried it on att roms mostly, but have also done tmobile rom.

The cm rom was att version, did not think there was a difference on them though.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
The .bt_NV.bin cannot ha BBC e anything to do with bluetooth, if you look at the last date of edit on it it says 1969 no bluetooth in 1969, however it being last edited in 1969 tells me its a security related file, this has been my experience with android, that also means this is a unix based file, I ran into a similar file on my motorola defy (similar in the fact it was last edited in 1969) but I guess it could still be related to boot, but not likely unless its a security setting for secure boot environment. However we all know that timestamps are easily changeable, and could possibly a false bread crumb fixed by the manufacturer to throw us off of having interest in that specific file, just a theory, I still think its worth taking a look @.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I have tons of files that have Dec 15 1970, I dont think the date can be much of a clue as its an issue with our recoveries. Anything we flash or edit from recovery will have a similar date. It just means it hasnt been changed since flashing I believe.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
I see your point, but it doesn't equate for me, our phones didn't exist in 1969 nor did the android platform, filesystem etc. So even if that were the case the last date of flashing would still be within the last five years or so, do you see what I mean, I lean further to the side of an erroneous recovery timestamp but then there is also the arguement that i still have not flashed anything to my device I'm simply stock root, not trying to be rude (of course you know this Doc as we have done a lot of work together and still have more to do) I guess I just don't see that as applicable to my device. But I'm also still learning a lot, and don't have much experience with this particular situation.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If I were to flash today, everything would reset to that 1970 date. Its a problem with the recovery not being able to read the correct time. If you create a nandroid backup, it uses the date as the default name of that backup. If you look itll have a 1970 date. Or if you use the recovery file manager to copy a file, the new copy will have this date.

Basically all im saying is you need to ignore these dates, they dont actually mean anything as they are simply just wrong. If you do a search for something like galaxy s3 recovery date problem, youll probably get numerous hits about it. No offense or anything like that taken. :cool:
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Ahh, that spells it out for me, got ya:thumbup:

---------- Post added at 01:10 PM ---------- Previous post was at 12:19 PM ----------

Googled the bt_nv.bin it is basically a cdrom.img for the system to mount, when it is searching for bluetooth addresses.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Directed here from the other thread, going to Odin the stock+root system and see what happens.

In the meantime, is a t999L NV backup still needed? I just finished making one with QPST. I can edit out my IMEI and have it on dropbox within the hour if anyone wants it.

Edit: I can remove my IMEI provided somebody helpful tells me how to edit a .qcn (it's obfuscated in notepad)
[T-Mobile, Samsung Galaxy SIII] New Optimus:
You can edit in any hex editor, winhex is what I use.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you haven't already, install and open Terminal Emulator and enter this.

Su

(Prompt should change from $ to #.)

Reboot nvbackup

Your device will restart and create an on-device backup of you're imei and other data. You never have to do it again, and if you do lose your imei all you have to do is enter

Su

Reboot nvrestore
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Everything work ok for you with using the Stock System to gain root?
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Flashing it as we speak. Tried motochopper first but that appears to have been patched.

Edit1: Flash complete. SuperSu in app drawer, su binary in place, able to check root by typing su in terminal, was prompted for root access. Thanks for packaging this up, now to reboot download and check if my binary went up (it shouldn't have).

Edit2: Checked download mode, status official, custom binary count zero!

To get custom recovery I would flash twrp/cwm with goo/rom manager correct? Then flash whatever rom/kernel I want, provided I stay on the mb7 modem (which I will by default, unless I go out of my way to flash a different modem)?

And to go back to stock (for warranty purposes), I would reboot custom recovery, wipe the things, flash the stock rom/kernel/recovery, then reboot system, then unroot from the supersu app and reboot again?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Let me know about the flash counter. It doesn't matter, but I do expect it'll be triggered by this flash since its not official firmware.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Cool! I figured it woulda tripped the counter, but glad to know for sure!

Actually, I suggest flashing the regular d2tmo (T999) cwm or twrp recovery. You'll have to do this via odin or terminal command. (Odin is easier)

Goo manager still doesn't recognize the T999L at all. Rom Manager will, but very few devs will code their roms to allow flashing by its recovery. The T999 recovery works fine and you won't have flashing problems.

If you prefer cwm let me know, if you want TWRP, you can get the flashable ones from the link on my sig.

Sounds like you've got it!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Oh, and you are fine to flash roms, kernels and recoveries. Just stay away from anything else, including the modem.

If you flash a touchwiz based rom and things like WiFi or bt don't work, flash either the MD5 kernel or the MB7 kernel plus modules.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Correct me if I'm wrong, but won't flashing a recovery in Odin trigger the counter? That's how it worked in the s2 at least.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Could I just flash cwm with rom manager, then use that cwm to flash the t999 twrp zip from here? And the t999 twrp will be able to flash the t999 roms?

Or will I need to change model number in build.prop to t999?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yes it will, but it doesn't matter. You can reset using triangle away, but also if you have a custom recovery installed, it'll trip the counter to 1 every time you reboot. So even if you use Rom Manager, as soon as you reboot your counter will be at 1.

Recovery won't add a count every boot, only flashing more in odin will do that. So basically the only way to keep it at 0 is to set triangle away to reset it at every boot.
[T-Mobile, Samsung Galaxy SIII] meshflesh:
will lte work on any rom i try?? or will i be stuck on hspa+?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
As long as its the T999L it should work. (Also providing lte has been deployed in your area of course). Depending on the rom, it may not display lte in the status bar though, I'm honestly not sure which would or would not. It may just show 4g. What does it show for lte when youre completely stock?

The best way to tell for sure though, is to start a large download, then go to About Device, Status, and check what it says for network type.
[T-Mobile, Samsung Galaxy SIII] Metzenw:
I loaded cm10.1 ok my t999l but I can't get lte. I have the right modem installed. And have the service in my area. Is it a kernel issue? Or do I just plan have to be on a TW ROM?

Thank you
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
LTE hasn't been deployed in your area yet. Sorry.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
T-mobiles coverage map show where coverage will be, not where it currently is, I had LTE for two days then it was about a week before thier official rollout to my market you may have seen it pop up during thier testing phase it will be back when they have finish configuring and testing.
[T-Mobile, Samsung Galaxy SIII] New Optimus:
Also remember the cm and other aosp roms most likely do not say 4G LTE just 4G.