yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mybook4:
Yeah, the gas situation sucks. Kind of a glimpse of the future when we start running out of fossil fuels.

Here's an updated list with "GPS" and "DB" items removed. At bare minimum, I would think editing 1877 is necessary (similarly to how the Bionic and Rezound guys changed theirs).

NV# Class# Class NV description
-----------------------------------------------------------------------
10 5003 System Digital/Analog Mode Preference
231 5005 CDMA New Format Most Recently Used Channels
240 5006 Data QNC Enabled Flag
298 5006 Data Packet Data Calls Originate String
459 5006 Data Data Services QC Mobile IP
465 5006 Data Data Services Mobile IP General User Profile
546 5006 Data Data Services Mobile IP RFC2002bis MN Home Agent Authenticator Calculation
562 5003 System Preferred Hybrid Mode
714 5006 Data Data Services Mobile IP Enable Profile
847 5008 Display CDMA SMS Parameters/Templates
905 5003 System Fatal Error Option
933 5003 System Dynamic Feature
1015 5003 System GSM/UMTS Cell Broadcast SMS Service Table Size
1017 5003 System GSM/UMTS Cell Broadcast SMS User Preference
1302 5012 GSM GSM AMR Call Configuration
1796 5018 WCDMA WCDMA TX Rotator Angle PA Range State 01
1797 5018 WCDMA WCDMA TX Rotator Angle PA Range State 10
1877 5005 CDMA RF Band Configuration
1878 5005 CDMA RF Hardware Configuration
1907 5006 Data Authentication Require Password Encryption
3060 5009 Factory DCS Power Levels
3174 5009 Factory CBS Enabled
3375 5003 System Last Registered SCI
3458 5013 HDR HDR SCP Subtype Custom Config
3461 5009 Factory ENS Enabled
3634 5005 CDMA DDTM Settings
3635 5003 System SD Configurable Items
3851 5018 WCDMA WCDMA RX Diversity Control
4184 5002 Security Sec Csprng Init Seed
4228 5009 Factory SMS MO On Access Channel
4399 5007 Debug Detect HW Reset
4548 5005 CDMA RF BC Configuration Diversity
4958 5005 CDMA Home MCC
4959 5005 CDMA User SID To MCC Assoc Table
4964 5013 HDR HDR SCP Force AT Configuration
6247 5006 Data PPP VSNCP Config Data

Some ideas:

1) Look for leaked Qualcomm documentation describing these NV items

2) Compare the data of these i535 items to the i747, Rezound, and Bionic (see post 201 for Bionic and Rezound) to spot differences. See if there is anything that catches your eye (it's ASCII, etc).

3) Read deeper into the other threads for info regarding the bit setting details of item 1877.

Moving forward:

1) Find out which of the above NV items need to be changed (might be more of a trial and error thing during testing as info for everything is hard to find)

2) Use DFS to write these changes to existing i535 items.

3) Use DFS to add NV Items related to HSPA that we found in the i747 dumps (see post 209). I've never tried adding a new NV Item to a device before, so I'm not sure of any issues we may encounter.

4) Once we modify the i535, we can run some tests near

- an AT&T 1900Mhz HSPA tower (with an AT&T or AT&T Straight Talk SIM) or

- a T-Mobile 1900Mhz HSPA tower (with a T-Mobile or T-Mobile Straight Talk SIM). This site http://www.airportal.de/ has an unofficial map of T-Mobile 1900Mhz tower sightings.
[Verizon Samsung Galaxy S III] krnnme:
I don't know if you guys have used the leaked version of TW JB... but I installed cleanrom 4.0 yesterday

and I was fooling around the settings and if you go to settings > more settings > mobile networks

there is an option called network mode in which you can choose

Global, LTE/ CDMA, or GSM/ UMTS

I haven't tried the other options besides LTE/ CDMA since I don't have a gsm card on me but maybe someone could try and see if it works if they are on the leak...

maybe verizon finally enabled the global capabilities of the phone with the JB update
[Verizon Samsung Galaxy S III] E:V:A:
Good idea. Make a dump of NV items before and after changing that and see what NVs changed.
[Verizon Samsung Galaxy S III] marcustaz:
I have both variants I535 & I747 what are you referring to exactly before and after. I can certainly give it a go EVA... Let me know.
[Verizon Samsung Galaxy S III] E:V:A:
I was referring to what krnnme wrote:

That way we can see exactly which NV item(s) changes when you change settings. My guess is that only one should change, but we don't know that, or do we?
[Verizon Samsung Galaxy S III] marcustaz:
I see, so I can can make this change and then create a dump of the same NV items? mybook4 what do you think?
[Verizon Samsung Galaxy S III] autoprime:
Yes that would be interesting... *.qcn file of sch-i535 on ics... then a *.qcn file of sch-i535 on jb. make sure the appropriate radio/modem is used for each rom... ics radio with ics rom.. jb radio with jb rom.

then run diff on two files.

this wont fix the issue with no 3G domestically... but it will help seeing what NV items they're messing with.

I suppose there's a chance that no NV items have changed and just the modem/rom has changed to allow for these global roaming abilities. Prior to JB, Verizon users could still roam globally.. they just had to use unofficial means to get around it in the rom.
[Verizon Samsung Galaxy S III] mybook4:
Yeah, I'm curious if they actually add any nv items in the update. I honestly think its just a ROM change (adding a menu to do what we normally do in the phone info app), but it'd be foolish not to take a look.

With the TW JB leak, are people simply inserting a global sim, changing to umts (in settings) and having it work? Do they still have to manually edit the APNs?
[Verizon Samsung Galaxy S III] marcustaz:
I had to change the APN manually, purchased 81 square APN pro and the paid version of Titanium Backup to convert it to a system app. So yeah I think it is just a Rom change.
[Verizon Samsung Galaxy S III] droidstyle:
If Im not mistaken the latest VRBLI5 leak has unlocked the global and gsm capabilities correct?
[Verizon Samsung Galaxy S III] mcornish86:
So how is the hspa+ on 1900/1700 mhz going? Would love to donate toward a succesful result. Updating my donation to 40$ if gets working
[Verizon Samsung Galaxy S III] AlexDeGruven:
1700 is unlikely to happen, as that's a hardware thing.
[Verizon Samsung Galaxy S III] mcornish86:
And the 1900 mhz deal?
[Verizon Samsung Galaxy S III] AlexDeGruven:
1900/WCDMA has been confirmed to be there, it's just getting the settings right to allow it to work on AT&T's fauxG. Once TMo switches over to 1900, then we might be able to get theirs as well, but that's a slower boat.
[Verizon Samsung Galaxy S III] csaket:
Are there instructions available to try out ATT 1900/WCDMA ??
[Verizon Samsung Galaxy S III] AlexDeGruven:
You won't get anything better than EDGE/GPRS at this point on either carrier, which is what the discussion in this thread is attempting to solve.
[Verizon Samsung Galaxy S III] DaileyDigital:
Hey guys I am new here but I do have the Verizon SGS3 and the Droid Bionic... This really does suck because I unlocked the bionic and it gets 3G with at&t go phone and this awesome Galaxy3 is stuck on edge... If I can do anything to help the cause let me know..

Sent from Verizon SGS3 on AT&T Go Phone
[Verizon Samsung Galaxy S III] Atsugai:
Hi everybody I'm new here as well Ive been following the thread hoping there is some way that we can get the most out of our phones. I was able to use DFS 4.0.0.6 and dump the NV Items from my roommates I-747 and copy them over to my I-535. Though I did lose signal but I was able to restore my backup and every thing worked fine after that. I hope this information can be useful to finding a solution. Also I have another 535 that I can use to do any kind of modifications yall can come up. Thanks for all the hard work. I hope this helps.
[Verizon Samsung Galaxy S III] marcustaz:
That's very interesting did you put in your roommate att sim card to test signal after the initial write?
[Verizon Samsung Galaxy S III] Atsugai:
Im currently using the phone on ATT and I lost the signal as soon as I wrote the items. Unfortunately I dont have a Verizon account to test it to verify that it still works for Verizon. I picked the phone up on craigslist for a $200 with hairline crack.
[Verizon Samsung Galaxy S III] marcustaz:
Ah I see, so your suffering with edge data? Are you running the latest JB leak? How did you edit the APN settings?
[Verizon Samsung Galaxy S III] Atsugai:
Yeah I usually get on WIFI when ever I can so its not to bad. Here in Fort Worth I get 140 - 210 K Down and around 100 - 180 K up. im running the Incubus JellyWiz 4.1.1. For the APN settings I edited the apns-config.xml file with ATT APN settings.
[Verizon Samsung Galaxy S III] marcustaz:
Thanks for trying this. I am waiting for mybook4 or the other experts to read this and post back his thoughts. I just hope the gurus do not loose touch or interest in this project.
[Verizon Samsung Galaxy S III] shangrila500:
Same here, I was really hoping we could make this work, even if we could only get 3g it would be better than nothing.

Sent from one of the many Anthropomorphic Personalities on the Disc
[Verizon Samsung Galaxy S III] mybook4:
Atsugai,

Thanks for contributing!

1) When you restored the backup, were you restoring from a Synergy Script backup? DFS? Please specify the restore method you used.

2) Could you please specify exactly how you wrote the i747 items to the i535 in DFS?

Marcustaz,

Depending on how Atsugai responds (write method), I think I can get together a modified version of your DFS NV item dump which includes

1) the AT&T specific NV items (related to 1900Mhz WCDMA) and

2) a changed item 1877 which enables 1900Mhz in the item

You could then make the appropriate backup, write the items to your i535, write the appropriate APNs, and test an AT&T SIM (or straight talk AT&T SIM). There's no guarantee that this will work, it's simply a quick test. If it doesn't work, we can continue down the path of researching what other items may need to be tweaked.

I'd really like to know the format of item 1877. I'd like to keep all the verizon bands while only adding the 1900Mhz WCDMA band. Anyone have more info on item 1877?
[Verizon Samsung Galaxy S III] marcustaz:
This seems like the most logical way to go.

mybook4, fantastic thank you for your continued support on this project.
[Verizon Samsung Galaxy S III] Atsugai:
Read I747

1) Send SPC 000000

2) Send Passcode 2010031619780721

3) Read Range 0 > 65535 / Save to File

4) Read RF 0 > 65535 / Save to File

Write I535

1) Send SPC 000000 (I535 would not accept the 16-digit passcode/tried on 2 535's)

2) Import I747 Range File / Write Range 1 > 10300

3) Import I747 RF File / Write RF 1 > 5700

4) Change NV Item 550 to match my IMEI.

From what I understood this is the method I came up with. I'm not sure if this was the best/correct way but I'm open to any suggestions. I was pretty sure this wasn't going to work but I have an extra phone so I could at least verify that drastically changing the NV Items wouldn't brick the phone and that it could be restored.

I'm willing to do anything yall can come up with as I have 2 535's to work with. One is my personal phone (currently on AT&T) and the other I use for testing at work so I'm not to worried about bricking it.

On a side note:

On the I535 I use for testing I flashed a AT&T Rom and Radio. Obviously it didn't work so I restored it but I'm unable to obtain root with "Root Debug FS" . Not sure if its a result of the AT&T SW or just something else I'm overlooking. I haven't really looked into it that much so it may be something simple.

Hope this information is useful.
[Verizon Samsung Galaxy S III] mybook4:
Thanks! When you restored your i535 NV Items, did you do it with DFS or with the Synergy backup script?
[Verizon Samsung Galaxy S III] Atsugai:
DFS 4.0.0.6
[Verizon Samsung Galaxy S III] deathknight842:
There alot alot of pages to look through here but can this happen yet? I have a chance at buying a cheap i535 but only if i can use it on gsm network.
[Verizon Samsung Galaxy S III] jclendineng:
Only 27 pages. And no you cannot. Still in development.
[Verizon Samsung Galaxy S III] mybook4:
All,

More progress today. Marcustaz and I wrote (using DFS) a modified NVF file to his i535. The file had the following:

-i535 items as is (except for item 1877)

-the i747 WCDMA items from post 209

-a modified item 1877 (changed from 87 01 68 00 00 00 00 00 to 87 03 E8 04 00 00 00 00)

After writing, and rebooting, the i747 items remained, but item 1877 was reverted back to 87 01 68 00 after reboot. We tried changing this item through DFS and EFS Explorer (file /NVM/NUM/1877), but couldn't get it to stick after reboot. It sticks after writing, just not after reboot. Does anyone know any info about how we could get the item write to stick?

Other important notes:

-Synergy Backup script was able to revert NV items back to stock (we made sure to do a backup up before writing NV items).

-Through subsequent investigation, it was confirmed that when DFS writes to item 1877, it modifies the data in the EFS file NVM/NUM/1877. This file can be accessed using EFS Explorer.

When we get access to an AT&T / Straight Talk SIM, we will be testing the following:

1) Try to get HSPA with AT&T / Straight Talk SIM inserted and item 1877 as 87 01 68 00.

2) Try to get HSPA after writing 87 03 E8 04 to item 1877 while it is powered on with AT&T / Straight Talk SIM inserted.

3) Trying 2, but this time disabling and re-enabling the radio in the phone info app.
[Verizon Samsung Galaxy S III] preusstang:
Shout-out to newuser134: please update the bounty total. I think its like $40 short
[Verizon Samsung Galaxy S III] hyunge:
Just put a T-Mobile sim card into my vzw sg3 with great signal, no phone issues. APN updated and got text and Edge to work, no picture messaging (MMS? Haven't tried sending other types of media.). Will try ATT soon. HSPA+ would be amazing!! I'm in for $40 for high speed internet on these frequencies.
[Verizon Samsung Galaxy S III] marcustaz:
Going to try and test today with a straight talk AT&T sim. Let you all know what I come up with.
[Verizon Samsung Galaxy S III] ac21365:
This is exciting! Good luck! :)
[Verizon Samsung Galaxy S III] marcustaz:
Sorry gents no go last night, best I got was edge. However not all hope is lost, we still need to iron out an issue with one of the NV fields not sticking after reboot. mybook4 has to figure this one out.
[Verizon Samsung Galaxy S III] mybook4:
This is what we tried:

No luck on any of these tries. When writing 87 03 E8 04 to 1877, the radio is disabled (circle with line) until you reboot. However, after reboot, 1877 is reverted back to 87 01 68 00.

I haven't figured out a way to make 1877 stick on reboot. I think our best bet is trying to get 1877 to keep 87 03 E8 04 on reboot. I haven't found a lot in other threads, but I've also been pretty busy. More searching could help us find something. Calling all readers, does anyone have any info on this? Does anyone have any ideas?
[Verizon Samsung Galaxy S III] AlexDeGruven:
If it's reverting on reboot, then it seems like it might be pulling the details from somewhere else in the phone. Could maybe be somewhere in the actual firmware, maybe?

This reminds me of grub2, and things like sendmail, where the configuration is rewritten from a source elsewhere on the system.

Is there a way to trace the boot process to break down each of the steps?
[Verizon Samsung Galaxy S III] skrypj:
I just found this thread and didnt get a chance to review it all but does this happen on the Stock VZW touchwiz rom. What happens on an AOSP rom? Determining if it happens on both might narrow down where the command to revert on reboot comes from(ie, not the rom)
[Verizon Samsung Galaxy S III] marcustaz:
Is cyanogen considered an AOSP rom? I can flash it and test but not sure when. Got to borrow the sim each time from my bro.
[Verizon Samsung Galaxy S III] mybook4:
Yeah, CM10 is an AOSP ROM.

Check out post 2 of this thread http://rootzwiki.com/topic/32397-tutorial-imei-backup-nv-with-qpst-us-variants/#entry897149

It has instructions to enable the modem mode (the mode we get to with the dial codes in TW based ROMs) in AOSP based roms, which is used for qpst, dfs, etc.

I recommend using CM10 M2 (you can get it from the cyanogen mode site (link is provided in the CM10 thread in original development section). To flash:

Download CM10 M2 and 7/26/12 gapps

Boot into recovery

Backup

Wipe data, cache, and dalvik cache

Install CM10 m2 zip from SD card

Install gapps zip from SD card

Reboot

I'll be getting back to action soon guys
[Verizon Samsung Galaxy S III] skrypj:
I have a contract AT&T sim card from my work iphone that I can try in my phone. However, my i535 is my daily driver and only driver so I dont really want to risk doing anything to it that could potential brick it. I tried it yesterday on Cleanrom 5.0 which is based on the latest JB leak along with the associated radio. I was able to make calls and send SMS but never entered in the APNs so I never had data. I will create a nandroid back and flash CM10. Would it be better to try i535 or i747 CM10?
[Verizon Samsung Galaxy S III] ddrum2000:
I'll had the same experience using leaked rooted VZW build.
[Verizon Samsung Galaxy S III] martirw:
Keep up the good work guys, can't wait for you guys to make it happen
[Verizon Samsung Galaxy S III] marcustaz:
This would be a huge help to me so I don't have to hunt down my bro for his straight talk sim.... Thanks a bunch.

I am not sure what mybook4 will say but if you use the vzw AOSP rom you'll have to add an AT&T apn which is sort of a pain... I do not see why using the ATT AOSP cm10 would hurt.
[Verizon Samsung Galaxy S III] skrypj:
Am I going to need to change nv values? I'm not sure how that is done, I have no experience with it.

I loaded the latest stable vzw cm10 and used phone info to change to gsm and got nothing at all unlike when I was on a touchwiz ROM. Also vzw cm10 does not have a gsm option in the mobile networks menu
[Verizon Samsung Galaxy S III] kintwofan:
To get gsm dial *#*#4636#*#* then select phone information.

Sent from my SGS3 running Eclipse 2.1
[Verizon Samsung Galaxy S III] skrypj:
I tired i747 CM10 last night and CWMR blocked the install. Maybe I missed something in the CW settings but it would not go through.

I got i535 CM10 to go into GSM mode using Phoneinfo, it even changed it in the mobile netwoks menu to say GSM even though its not usually an option, but for whatever reason i couldnt get calls or sms.
[Verizon Samsung Galaxy S III] ddrum2000:
I also tried CM10 with an AT&T sim but couldn't get any connection. The leaked VZW rom worked fine for calls and sms. I couldn't get edge data to work though.
[Verizon Samsung Galaxy S III] skrypj:
I figured how to get the i747 CM10 to load . . . http://xdaforums.com/showpost.php?p=31635980&postcount=129
[Verizon Samsung Galaxy S III] ddrum2000:
Are you on EDGE or HSPA, and what frequency in what country? Will the phone still work with CDMA/LTE with the ATT rom in stalled? Also please show a screenshot of Settings -> About Phone -> Status, where it lists the mobile network type. Thanks.
[Verizon Samsung Galaxy S III] skrypj:
Will do. I had to extract the rom and re-compress it on my phone since i dont have a usb cable, so it is taking forever. Im in the US, with a contract AT&T sim from an iPhone 4s.
[Verizon Samsung Galaxy S III] ddrum2000:
The posts you showed had Vodaphone APN? I think I'm confused.
[Verizon Samsung Galaxy S III] skrypj:
That wasnt me, that was some random dude that had loaded the AT&t rom on his i535 in Europe
[Verizon Samsung Galaxy S III] marcustaz:
delete
[Verizon Samsung Galaxy S III] ddrum2000:
Oh gotcha. I personally do view that as a very good solution. Thanks.
[Verizon Samsung Galaxy S III] marcustaz:
Awesome let us know how it goes... You should hook up with mybook4 see if you can load the modified NV file he has.
[Verizon Samsung Galaxy S III] tonu42:
Hes doing something we already know works. He is in Europe, running 3g or what not on DIFFERENT bands and works for him. We are in the same boat with the Nexus 4 perhaps where our phone can only get GSM 3g to work on certain bands.
[Verizon Samsung Galaxy S III] marcustaz:
Hey man any luck?
[Verizon Samsung Galaxy S III] marcustaz:
I was able to get Edge using this method a while back when I found the thread "Set up Verizon Galaxy S3 as World GSM Phone" So it is certainly possible.

So you want to just see if on reboot it sticks? Great idea since I currently do not have access to the Straight talk sim. I 'll get on it a bit later and email you when I am available. :good:

I thought we did try QPST already? Anyway I just grabbed a copy of QXDM 3.12.7
[Verizon Samsung Galaxy S III] E:V:A:
I'll just randomly dump this link here, as it seem to indicate that we also need to set the PRL...
[Verizon Samsung Galaxy S III] mybook4:
FYI,

Marcustaz came across an i535 that couldn't display anything (but the device still seemed to function). Since we had a device with nothing to lose, we controlled the device with ADB, unlocked the bootloader, and flashed an AT&T i747 modem (LG1) to the device. It bootlooped (we don't exactly know where as it didn't have a working display). Could have been at a bootloader screen or while the device was initializing Android. We odined the verizon LG1 modem back. The device booted back up into Android and we were able to control it with ADB. The SDCard also mounted in windows via MTP.

We did this as a "what the hell". The device had nothing to lose and it adds knowledge to the thread.

It appears that flashing the AT&T i747 LG1 modem does not permanently brick the i535.

I don't think we should do anything with this info right now. We should focus on getting item 1877 to stick. I'm reading the article E:V:A posted.
[Verizon Samsung Galaxy S III] AlexDeGruven:
In fairness, it's almost literally impossible to hard brick a device these days. That makes it quite nice for people who have the time/inclination to dink around with obscure configurations that would have completely broken things only a few years ago.
[Verizon Samsung Galaxy S III] LLStarks:
Not sure why flashing an AT&T modem causes boot loops, but bad Odin of certain partitions will give you a Secureboot error for the partition in question.

Even though it's a softbrick, I had quite a scare a few weeks ago.
[Verizon Samsung Galaxy S III] mybook4:
Things can be a little bit different when the device's boot loader is locked. I'd wager that if someone even just removed the signature from the aboot partition that the device would brick (requiring JTAG to repair).

We weren't sure if running a non-i535 modem would brick the device to a state which you couldn't Odin recover from. Turns out that flashing an i747 modem (at least the LG1 one) is Odin recoverable. If we ever have to modify the modem, that info may come in handy.

---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------

So you soft bricked via a bad modem Odin? It was recoverable by odining another modem, right?
[Verizon Samsung Galaxy S III] LLStarks:
I got secureboot errors using Odin in a VM.

I was able to unbrick by using Odin in a normal Windows environment.
[Verizon Samsung Galaxy S III] mybook4:
How was the secure boot error reported?

-By Odin (preventing the flash)?

-On the GS3 during bootup (after odining)?
[Verizon Samsung Galaxy S III] LLStarks:
On the phone's Odin screen.

It would say stuff like SECURE BOOT ERROR MODEM/SBL/BLAH
[Verizon Samsung Galaxy S III] ultrafta:
sold the phone
[Verizon Samsung Galaxy S III] Bigheadse:
I will add $30 to the bounty.
[Verizon Samsung Galaxy S III] martirw:
OP update bounty amount on topic. BTW thx for the hard work everyone
[Verizon Samsung Galaxy S III] ac21365:
Anyone had a chance to take a look at the phone with the Jelly Bean update? I wonder if they changed anything now that the global roaming thing is official.
[Verizon Samsung Galaxy S III] mybook4:
From what I've been told there is no change for domestic hspa
[Verizon Samsung Galaxy S III] ac21365:
That's what I was assuming, just thought I'd throw it out there since a new baseband accompanied the official Global Roaming update.

While the Global Roaming update is now official... it doesn't allow you to change APN's regardless of whether it's set to global or GSM/WCDMA. Could only get phone calls working with my T-Mobile sim. *sigh* Wish all this mess were easier.