yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] ac21365:
I wonder if compiling a new NV items is as simple as comparing 2100 files on the i535 and i747, seeing if they are the same/similar, then copying the relevant 1900 files from the i747 and flashing it to the i535.

If yall figure that's the case, I'll be the guinea pig since I have 3 other phones to use should my phone go down for a day or whatever.
[Verizon Samsung Galaxy S III] mybook4:
Possibility. We have two i747 QPST dumps. There are going to be device specific items (calibration, etc), but we may be able to see similarities between 1900 and 2100 items in the i747. What would really be awesome is finding the documentation that Yura80 posted earlier defining details about the Nvitems.

As soon as I get the chance I'll be reviewing the great new info that has been posted today as well as post the list of chips provided be marcustaz to compliment E:V:A's stuff.
[Verizon Samsung Galaxy S III] autoprime:
Samsung PST is posted various places.. what's hard to find and required for each device is the .dll file. What we need exactly is the Verizon Samsung SCH-I535 SamsungPST .DLL. Anyone? Help!! :confused:

Then we can use that with existing SamsungPST software. In my experience, Samsung PST is good for flashing bootloaders etc... almost like what Odin would do. To my knowledge there isn't anything on editing specific NV Items.. but I could be wrong.

This seems to be the doc from where the NV item table was posted. Only problem is there is "Qualcomm" over some text on every other page :(

http://www.doc88.com/p-087655159856.html
[Verizon Samsung Galaxy S III] mybook4:
The service manual is an amazing resource! Thank you E:V:A. The parts list looks very comprehensive.

The i535 service manual electronic parts list (section 5) encompasses all of what marcustaz sent (list of some chips present on the i535 and i747).

When you say "definitely worth testing", do you mean troubleshooting techniques in the service manual, or the NV item patching?
[Verizon Samsung Galaxy S III] E:V:A:
My bad. Like you say, normally they only show Odin in the Service Manuals and not QPST...

The only thing that seem usable from that document, unless you plan to reprogram every single NV item, are the following two images.

The band terminology table.

And the previously posted band support item.

I should probably have been more modest in that statement. I meant the trouble shooting, but that probably requires other very expensive equipment... And as a side note, we should know that the Samsung Service Manuals can't always be trusted. They do a lot of copy&paste, and then forget to edit...

Which lead to the various bands and their names. I am in no way in a position to clarify what all the different RF related bands and their term & acronyms refers to. For me this is very confusing, even after reading Wikipedia. What used to be CDMA --> WCDMA --> UMTS --> damn knows what, and in the Sammy specs and QPST they all seem intermingled! If someone have a clear understanding of all the various bands and their acronyms, they should help reading the Service manual and understanding the RF HW in your photos. I also suggest having a look at the MSM8960 (+etc) Reference Design schematics... (I don't have the link in my head, but you'll find it here.) That will not tell us what our connections are or what HW we actually have, but it will tell us something how it should be connected, and what components are used, if it's there...

Finally, IMHO I think this level of HW analysis should not be necessary. We just need to find someone to willing to freely play around with their NV items while having access to a nearby 1700/1900 tower, confirmed to work on a not-too "different" phone, use that SIM card in the i535 and play with the NVs & settings...
[Verizon Samsung Galaxy S III] autoprime:
Generally Verizon/Sprint guides will use SamsungPST rather than Odin. But regardless, I'd LOVE to see the PST/DLL for our devices.

As for the document.. yes it seemed pretty worthless. Just wanted to share for "completeness". I spent a few hours trying to find a more complete guide on NV Item breakdown.. but it doesn't seem like any of the info is in one single place.. it's spread around. Sometimes its fun to Google "Qualcomm confidential proprietary"(without quotes) to see what pops up :good:

I've always felt this way and completely agree. It should be NV items alone(and perhaps an AOSP rom rather than stock). I'd love to work on this myself but unfortunately I don't own an ATT/VZW version. :crying:
[Verizon Samsung Galaxy S III] mybook4:
Yeah, the band classes get confusing.

From taking a look at the differences between i747 and i535 defined NV Items, it seems there are many items defined in i747 (but not i535) that start with "NV_WCDMA_BC4". Most of the items that i747 has which i535 does not are items related to WCDMA 1900, WCDMA 800, and WCDMA BC4.

http://pastebin.com/x5pwMjBA from this post http://xdaforums.com/showpost.php?p=32600627&postcount=152

Not sure what WCDMA BC4 is, but UMTS Band IV is AWS 1700/2100. Maybe the WCDMA Band Class list is different than the UMTS Band Class list.

Meanwhile, I believe table 2.1 is referring to CDMA Band Classes (Band Class 4 is Korean PCS http://niviuk.free.fr/cdma_band.php)

From wikipedia, one would assume we need to enable UMTS Band II (1900 Mhz)

http://en.wikipedia.org/wiki/UMTS_frequency_bands

...so yeah, it all ends up being alphabet soup with all of the acronyms and band classes.
[Verizon Samsung Galaxy S III] E:V:A:
[Just for Reference]

The NV-items in the following pictures are the ones related to WCDMA calibration...

From:

80-VA360-10 A (04-02-2011) FTM Test Procedure WCDMA RF Calibration
[Verizon Samsung Galaxy S III] ac21365:
Huh, those images would seem to imply that the NV items for each band are chipset specific... not band/carrier specific.
[Verizon Samsung Galaxy S III] mybook4:
I'd guess a little bit of both. Those are the calibration items. We'd probably still need RTR8600 specific documentation/procedures to correctly set the static NV Items required to enable WCDMA 1900 (UMTS Band II). Even a list of the static items responsible could help as we have some examples having several i747 NV Item dumps to analyze. From reading through the FTM Test Procedure for WCDMA RF Calibration doc, it seems that we may need:

-Proper test equipment for calibration (highly unlikely anyone has access to this kind of stuff)

-QRCT

-QMSL (to translate measurement data into NV Items and maybe vice versa)

-RTR8600 specific documentation/procedures/NV Item Definition

PS, the rest of marcustaz's pics of the i535 and i747 were added to the drop box link in post 185. He did a great job. They look clear.

---------- Post added at 09:45 PM ---------- Previous post was at 09:36 PM ----------

Thought I'd add this to make the NV Item dumps easier to locate.

Post 152:

-mybook4's censored i535 QPST 2.7.0.378 dump (in text)

-marcustaz's censored first i747 QPST 2.7.0.378 dump (in text)

-list of QPST specified NV items that were in the i535 but NOT in the i747 dump

-list of QPST specified NV Items that were in the i747 dump but NOT the i535 dump

-list of QPST specified NV Items that were in both the i535 and i747 dumps

-list of QPST specified NV Items that were in both the i535 and i747 dumps but have different data

Post 153:

-NVF dumps for Bionic (complete RF calibration for 800/900/1700/1900/2100 wcdma bands), Rezound (calibratred for 900/2100 and some 800/1900 items) and Verizon S3 / i535 (2100 only)

Post 170:

-mybook4's censored i535 DFS 4.0.0.5 NVF dump

Post 171:

-jumperpunk's censored i535 dev edition QPST 2.7.0.378 dump (in text)

-list of items that are defined in the i535 but NOT defined in the dev edition

-the fact that all items in the dev edition are defined in the i535

-list of items that are defined in both, but have different data

Post 184:

-marcustaz's censored second i747 (cracked screen) QPST 2.7.0.378 dump (in text)

-marcustaz's censored second i747 (cracked screen) DFS 4.0.0.5 nvf dump

---------- Post added at 10:01 PM ---------- Previous post was at 09:45 PM ----------

Looks like http://dc436.4shared.com/doc/UHQFFr_i/preview.html is something that may come in handy if we had the full version.
[Verizon Samsung Galaxy S III] autoprime:
I believe this is the full version? http://www.scribd.com/doc/110733369
[Verizon Samsung Galaxy S III] mybook4:
Seems like it is. I read through it, but didn't see any list of static NV items specified. I tried looking for 80-VF535-60 as well. No luck.

Some hypothetical questions:

Is QPST used for adding / removing band capabilities? Could we use QPST to tell us what the total list of NV item changes are required to enable WCDMA 1900, then logically separate the static ones (we have a list of calibration ones)? If we can, we have several i747 dumps that we can analyze for example implementations of enabled static WCDMA 1900.

I believe E:V:A had attempted to use QPST for something similar?
[Verizon Samsung Galaxy S III] E:V:A:
Well, of course. If the HW doesn't support some band (for example), those NV items are not needed and vice versa.

Wow! Real EE RF porn! (Actually quite nice to see a real engineering quality document, for a change.) Although useless for our purpose.

From now on, I will not be able to help you guys much further. As I already mentioned, the EE aspects of this project is getting out of hand, and will for sure not lead anywhere. All you really have to do, is figure out how to apply the info we already have. In general terms, this means:

1) Choose a band (1700 or 1900) you want to enable.

2) Find a phone that supports it, and compare the NV items. (Already done.)

3) Select the relevant RF related NV items and dump the output to a QCN file.

4) Backup your phone + NV items (as much as possible)

5) Load the new QCN file to your phone.

6) Go into service menu and check band availability there. Enable if needed.

7) In service menu also make sure the selection order give priority to your band (WCDMA) or whatever.

8) Be patient and make sure you give your phone time to re-register on the new bands / network.

9) Reboot and hopefully the changes sticks. Enjoy.

[This is in no way a recipe for making it work, it merely reflect my own opinion on what needs to be done.]
[Verizon Samsung Galaxy S III] marcustaz:
I am willing to be a guinea pig, however I do not have an att sim. If I brick my phone then what? :confused::D
[Verizon Samsung Galaxy S III] ac21365:
From the looks of it, if there is a chance we'll brick a Verizon S3, it'll be after we modify the NV items... assuming the worst with the Secure Boot checking -all- partitions.

Point being having a sim is irrelevant, you'll know because brick before then :P

This is my only reservation about flashing new NV items: The unpredictability of Verizon's secure boot shenanagains. We'll see if an NV item flash will brick our phones... from someone :\
[Verizon Samsung Galaxy S III] mybook4:
With anything we do here there is always a chance (however remote) that your device will be bricked. I seriously doubt it will though.

I have a crazy week this week, but I want to keep things moving forward. As I get time, I'll try to get a more complete list of NV items we need to add/change.

Some things I recommend working on:

1) someone list out the NV item numbers (not data) that DFS grabs for an RF item dump

2) someone mess around in QPST 2.7.0.377 (without a phone connected) to see what NV items are written to when 1900 WCDMA is enabled. (see post 79). We need this info for the MSM8960. Due to the version of QPST that we have, we may not be able to use QPST for this. I compared the post 79 info to the i535 and i747 dumps we have. Only a few of the items from the UMTS PCS 1900 lost were defined. Of those items, all but one matched between the two dumps. The different item was item 10.

NV item: 10 [NV_PREF_MODE_I], index 0
*
* * * * * * i535:
* * * * * * * *NV_PREF_MODE_I 0: 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 1: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 2: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 3: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 4: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 5: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 6: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 7: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*
* * * * * * i747:
* * * * * * * *NV_PREF_MODE_I 0: 00 1f 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 1: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 2: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 3: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 4: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 5: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 6: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* * * * * * * *NV_PREF_MODE_I 7: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*

The goal is to get a list of the NV items that would need to be modified and/or added in order to enable 1900Mhz WCDMA. We have a list of calibration related 1900Mhz WCDMA NV items. We are looking for the whole list. When we have a better idea of the items needed to enable the change, we can then look at our existing nv item dumps for examples.
[Verizon Samsung Galaxy S III] autoprime:
Not sure how much this will help but I've been collecting info and have put together a list of ALL available NV items available as of summer 2012.

I have sorted the items into categories just as QXDM would sort them.

http://xdaforums.com/showthread.php?t=1954029
[Verizon Samsung Galaxy S III] mybook4:
I'm trying to piece together a list of NV items we would have to add and change.

Items to add:

Out of the items in this list http://pastebin.com/x5pwMjBA, I think we should add all EXCEPT for the following items (Verizon's LTE is on Band 13. Getting AT&T's LTE Band 17 to work is outside the scope of this effort).

NV item: 6596 [NV_LTE_B17_RX_CAL_CHAN_I], index 0
NV item: 6597 [NV_LTE_B17_LNA_RANGE_RISE_FALL_I], index 0
NV item: 6600 [NV_LTE_B17_RX_GAIN_I], index 0
NV item: 6601 [NV_LTE_B17_RX_GAIN_VS_FREQ_I], index 0
NV item: 6606 [NV_LTE_B17_MAX_TX_POWER_I], index 0
NV item: 6607 [NV_LTE_B17_AGC_PA_ON_RISE_FALL_DELAY_I], index 0
NV item: 6608 [NV_LTE_B17_AGC_TX_ON_RISE_FALL_DELAY_I], index 0
NV item: 6609 [NV_LTE_B17_PA_GAIN_UP_DOWN_TIME_I], index 0
NV item: 6610 [NV_LTE_B17_TX_ROT_ANGLE_PA_STATE_I], index 0
NV item: 6611 [NV_LTE_B17_PA_COMPENSATE_UP_DOWN_I], index 0
NV item: 6612 [NV_LTE_B17_TX_LIN_VS_TEMP_I], index 0
NV item: 6613 [NV_LTE_B17_PA_RANGE_MAP_I], index 0
NV item: 6614 [NV_LTE_B17_TIMER_HYSTERISIS_I], index 0
NV item: 6615 [NV_LTE_B17_PA_RISE_FALL_THRESHOLD_I], index 0
NV item: 6616 [NV_LTE_B17_TX_CAL_CHAN_I], index 0
NV item: 6617 [NV_LTE_B17_TX_LIMIT_VS_TEMP_I], index 0
NV item: 6618 [NV_LTE_B17_TX_LIN_MASTER_0_I], index 0
NV item: 6619 [NV_LTE_B17_MPR_BASED_PA_SWITCHPOINTS_SHIFT_I], index 0
NV item: 6620 [NV_LTE_B17_TX_MPR_BACKOFF_I], index 0
NV item: 6621 [NV_LTE_B17_TX_DIGITAL_GAIN_COMP_I], index 0
NV item: 6622 [NV_LTE_B17_TX_AGC_OFFSET_I], index 0
NV item: 6623 [NV_LTE_B17_TX_LIN_MASTER_1_I], index 0
NV item: 6624 [NV_LTE_B17_TX_LIN_MASTER_2_I], index 0
NV item: 6625 [NV_LTE_B17_TX_LIN_MASTER_3_I], index 0
NV item: 6626 [NV_LTE_B17_TX_GAIN_INDEX_0_I], index 0
NV item: 6627 [NV_LTE_B17_TX_GAIN_INDEX_1_I], index 0
NV item: 6628 [NV_LTE_B17_TX_GAIN_INDEX_2_I], index 0
NV item: 6629 [NV_LTE_B17_TX_GAIN_INDEX_3_I], index 0
NV item: 6630 [NV_LTE_B17_TX_COMP_VS_FREQ_I], index 0
NV item: 6631 [NV_LTE_B17_EXP_HDET_VS_AGC_I], index 0
NV item: 6632 [NV_LTE_B17_TX_LIMIT_VS_FREQ_I], index 0
NV item: 6633 [NV_LTE_B17_HDET_OFF_SPAN_I], index 0
NV item: 6637 [NV_LTE_B17_C1_LNA_RANGE_RISE_FALL_I], index 0
NV item: 6641 [NV_LTE_B17_C1_RX_GAIN_I], index 0
NV item: 6644 [NV_LTE_B17_C1_RX_CAL_CHAN_I], index 0
NV item: 7225 [NV_LTE_B17_C1_RX_GAIN_VS_FREQ_I_I], index 0

Items to change:

To be determined...

To better locate the items that may need to be changed, I did the following:

I compared the two i747 dumps. I recognized the items that have different data. These items are obviously not the same for all i747. I then removed these items from the list of items that are defined for both i535 and i747 but have different data. I was then left with a list of items that are different only between i535 and i747.

The list of items that are different only between i535 and i747 is below. Many of these items are unrelated to WCDMA. Hopefully we can narrow down the items associated to WCDMA from looking at autoprime's thread, the leaked Qualcomm documents, and E:V:A's previous list of UMTS PCS item build from scratch.

http://pastebin.com/5mesTveV
[Verizon Samsung Galaxy S III] mybook4:
From previous posts (around post 136), we would need to persistently change at least 1877 (RF Band Configuration). In order to persistently change the items, we may be able to use EFS Explorer to pull the particular item file, hex edit, and write back to the phone.

Our item 1877 is

87 01 68 00 00 00 00 00 00 00 00 00 00 00 00 00

While the i747 one is

80 03 e8 04 00 00 00 00 00 00 00 00 00 00 00 00

I'm not sure if anyone found the bit layout for enabled bands. We should only enable the missing bands, not remove any band capabilities.
[Verizon Samsung Galaxy S III] mrej201:
my boy in miami that flash my andoid phone via team viewer and usb over network to any other carrier told me he can do it he can flash a verizon phone cdma to work on att gsm message me if you want his number
[Verizon Samsung Galaxy S III] E:V:A:
See that look much better already! Now, you need to look at the different item "classes" of that list (above). Obviously we're not interested in items like, "GPS" and "autoanswer" etc... The classes are shown in Autoprime's list, or can be found in the NV DB file of QXDM. Then, when we have reduced these items to a small set that we are still unsure of, we can discuss and start testing further...
[Verizon Samsung Galaxy S III] mybook4:
I want to make this work, but I'm not sure how much of everyone's interest this topic will maintain now that an entry level Nexus (4) is $300 off contract. An i535 could probably fetch $350-$450 on ebay. A termination fee for leaving verizon was in the cards regardless of whether or not we got this working.

... although i guess there has always been the option of selling/swapping an i535 for an i747 or T999.
[Verizon Samsung Galaxy S III] marcustaz:
Well I for one am still interested.. I know some of us have a lot invested so I would love to see this project keep going. However I do not have the technical know how to really contribute more then I already have. All I can say this far is thanks you and KEEP TRYING! :D
[Verizon Samsung Galaxy S III] mybook4:
I will definitely keep things going, it is a fun little experiment and if we succeed should help others the way the bionic info has helped us.

I'm still in the thick of the Sandy situation, so I don't want to try anything crazy out right now (breaking a phone in the middle of hurricane would be on my top ten blunders list).
[Verizon Samsung Galaxy S III] marcustaz:
Indeed stay safe we need our phones lol. I am in the middle of it as well, on backup generator as I type! Powers been out for 6 hours now...

I take it back that I really can't contribute more to the project. I have Verizon phone I bought off ebay and although I really would not like to break it I'll give it a shot if you think it's safe to write the NV items or whatever you have up your sleeves. :eek::D
[Verizon Samsung Galaxy S III] mybook4:
We've got time. Stay safe (that goes for everyone)!
[Verizon Samsung Galaxy S III] worldlyinquirer:
Hello, actually what this thread is about is how to get 3g data from ATT or Tmobile working on the phone. There is already a was to get voice working.
[Verizon Samsung Galaxy S III] mcornish86:
30$ to the cause
[Verizon Samsung Galaxy S III] kotentie:
I'm not sure how this changes anything.
[Verizon Samsung Galaxy S III] marcustaz:
Incubus just put up an "official" Verizon JB leak on his jellywiz thread. I have updated and interestingly under mobile networks now have a new "network mode" under that we have 3 choices,
[Verizon Samsung Galaxy S III] marcustaz:
I have a straight talk simple on the way to test will post back and let you all know...

Just curious if this would update the NV items as this did not include a modem flash that I am aware of...
[Verizon Samsung Galaxy S III] marcustaz:
Just an update the I535 with straight talk sim now shows G instead of E. Data is faster and I was told G is 3G, something we were not able to accomplish before. If you want me to due further testing please advise.
[Verizon Samsung Galaxy S III] mybook4:
G might stand for GPRS. Would you mind posting the results of running the speed test app? Also, are you using a straight talk AT&T sim or T-Mobile sim? Thanks in advance!
[Verizon Samsung Galaxy S III] marcustaz:
Straight Talk Sim. Speed test seems poor but then again we are in a situation with Att and Tmobile having serious overload issues on whatever towers they have functioning in our area, so I am not sure if that is having an adverse effect.

I have a tmobile sim I purchased with free 10 minutes of talk time but I do not know if it has data, I'll give it a test soon and report back.
[Verizon Samsung Galaxy S III] mybook4:
I've never purchased a straight talk SIM, but I was under the impression that when you buy it you choose to be on AT&T or T-Mobile's network. Did you have to choose?

What kind of speeds are we talking about? Above 150kbps (0.15mbit)? The reason I ask is that an AT&T sim near a 1900Mhz HSPA tower should get above a megabit (even under heavy load). If we are still on edge/gprs speeds, then we can keep pursuing the NV item changes.
[Verizon Samsung Galaxy S III] marcustaz:
I think it is gprs speeds but I will certainly confirm in a bit and update this post.

It is gprs sorry about all the hype gents. :(
[Verizon Samsung Galaxy S III] E:V:A:
This guy seem to have made some related progress...
[Verizon Samsung Galaxy S III] marcustaz:
Seems like it can be done. Mybook4 let's kick it into high gear! :D
[Verizon Samsung Galaxy S III] mybook4:
Man do I wish I could right now. Mom and pop's house was flooded out with 4ft of water from Sandy and I'm on the graveyard shift (9pm - 8am). Towards the end of the week should be better. But don't wait for me! Ive posted pretty much all I've got at the moment, but If anyone has any questions I'll get back to ya asap.
[Verizon Samsung Galaxy S III] marcustaz:
Sorry man, take care of the folks. Our power is back on thankfully. Sat in line for 2 hours today to get gas only you make it to the pumps and they ran out of gas!

I am willing to write NV items with direction. I'll wait for you direction. Be good stay safe.