yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jdshewey:
You have to do it in QXDM in the command bar. So, for example: I was unable to restore a QCN using software download, but was able to do it once I first entrd the password. If I did not first enter the password, I was unable to restore the file and received the error "could not communicate in diagnostic mode" RequestNvItemWrite simply does not work until the password is entered for some protected NV items. The SPC unlocks some, but the samsung password is required for others. You may find that some of the items you are trying to set are some of those.
[Verizon Samsung Galaxy S III] LLStarks:
Hmm. Did not know that. Did notice that QXDM wouldn't play nice with restores like QPST. I'll take a look.

I think I also mixed SPC and MSL together or something.
[Verizon Samsung Galaxy S III] ubuntuman1:
Just a little tidbit of info. I bought an wp8 att go phone and it had H+, so prepaid Sims do allow you to get H+, even w/o a service plan.
[Verizon Samsung Galaxy S III] LLStarks:
Something interesting in the service menu with NE1 modem + ICS stock

UMTS > Debug Screen > Phone Control > Network Control > Band Selection > LTE Band Preference

http://i.imgur.com/dmuojca.png

Band 3, 4, 5, 7, 17, 20, and "all" are listed

If I set my NV 6828 to a value that covers all or a subset of those bands (eg: 1906911, 4104, or 8), reboot, and then select one of those options, the phone reboots

What I'd like to know is why 6828 sticks through reboots and 1877 doesn't and whether we can exploit 6828 (and maybe 6829?) for enabling LTE bands

Specifically, which NV items are checked between the various partitions at boot? What else besides 6828 is needed? What does our hardware even support?

The phone doesn't seem to function nicely with anything beside 4096 (Band 13) for 6828. Doesn't matter if I use a TW rom or CM12.1. You can still get B13 LTE with other values that include it, but I've noticed random radio resets that sometimes leave it without CDMA service (eg: sets itself to LTE/GSM auto)
[Verizon Samsung Galaxy S III] An0nYm0u5.bat:
Sorry for the Houdini as of late... But have been stretched out like Samsung trying there best not to be pushed off the mountain by oems such as my new devices maker... the LG G3... and let me tell you.. (S6 edge) or the name i aptly applied... (Galaxy S G3) these companies are going to be "sucking hind tit" to LG for a minute. And let's give an HM to OppOF5. :D anyway. I'm off topic a little so let me venture back. Just got to Say. Eye candy. Quality. And NO bug wise. G3 is a BEAST.. But. Back to tt. Work is slow and I'm breaking the old S3s back out. I was thinking of trying a >ifcarrierdefault=disabled or missing. Then>switchtooperator2 something along those lines. It should allow the boatloader handoff to still take place. And once all modem checks etc. Are done, disable that C. ommunist D. eveloped M. obile A. ntenna and fire up the G. reatest M. obile S. ystem known to the free world... :D (2 Expressos in an hour explanation ) Haha. Anyway. It would make the device itself give up the control. Cause it IS NOT A HARDWARE ISSUE!! It's absolutely no difference at all in the board in the two devices. NONE... Verprison (Verizon) has just written code that will not allow it to operate domestically. But they've done it so subtly that when we do figure this out. It will make us feel really stupid. Cause I promise It's hidden right in our Face. Also I've been studying qfuse and the certain pins on the i535. And I've first hand watched 3 volts applied to two pins to release network / carrier locks on other devices. So That's a place to seriously delve into. Anyway. I'm here. Back. And willing to work with any SERIOUS open minds on this. Hit me up. ₡++

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

I have many att... ST... both att and T-M Sims. Most activated and will GLADLY mail you one to use in your testing phase. Or will gladly implement your work for you. Since the theory is your baby, I'd prefer you keep the reigns. But anything to further our Coo of Verprisons pathetic attempt to control OUR bought devices. Let me know brother.
[Verizon Samsung Galaxy S III] LLStarks:
It's really unfortunate how we never got a full leak of the VRALE6 bootchain or modem. It probably had every partition unlocked.

An AT&T SIM would be interesting. Would definitely like to try Band 17 (700 MHz). I may go out and buy a GoPhone SIM.

Here's what I've found so far...

Band 2: Not sure if either carrier has this in my area, but if they do, I'm pretty sure it doesn't work

Band 4: Doesn't seem to work

Band 5: Not available in my area?

Band 12: Not available yet, in NYC exclusion zone
[Verizon Samsung Galaxy S III] An0nYm0u5.bat:
ANYTHING. I. an do to help [MENTION=4670039]LLStarks[/MENTION] I'm all in. Just let me know. I recently did work on a huawei windows phone. And to unlock it's modem etc. I had to use a jumper from the some slot to the sd slot. Just a paperclip lol

---------- Post added at 01:58 PM ---------- Previous post was at 01:57 PM ----------

And I'm in Mississippi. I'm not even sure they can spell band here. Hahaha
[Verizon Samsung Galaxy S III] LLStarks:
Lol, I thought pin-mods died with the Rezound

At any rate, I've been a little busy

Tried my Go Phone SIM a few days ago. Haven't played around too much yet, but I was having difficult picking up voice signals after NV edits

I'll try again over the next few days. Between all the reboots involved, you really have to set aside a few hours

I'm not particular happy to be using a nano-SIM adapter with the phone, but I know the SIM is good and being seen (tested with OnePlus One)
[Verizon Samsung Galaxy S III] preusstang:
Any luck on this? My nexus 5 took a dump on me so I'm back to using my i535 using a Net10 ATT sim. No data and very iffy signal. Sometimes I try to make a call and I get a Verizon message saying my phone is not activated.. Toggle airplane mode, reboot, then it goes through over ATT just fine.
[Verizon Samsung Galaxy S III] sparktologist:
The 16 dig qxdm/ qpst password for Verizon*S3 / S4 / S5/*Note*2 /*Note 3 is "2009031920090615" :)
[Verizon Samsung Galaxy S III] renzo.olivares:
I can when I get home
[Verizon Samsung Galaxy S III] ac21365:
Much appreciated! If any of the modifications require a computer, I can tote the laptop with if need be.
[Verizon Samsung Galaxy S III] newuser134:
The new Verizon iPhone 5 (CDMA version) seems to also get gsm 850, 900, 1800, 1900, wcdma 850, 900, 1900, 2100 and LTE 1, 3, 5, 13, 25. It seems like it gets almost everything. Not that I would EVER get an iPhone, but it sure looks like any other CDMA phone in the world that gets wcdma, gets both 1900 and 2100, not just one or the other, seems strange that the Samsung GS3 would, right?
[Verizon Samsung Galaxy S III] tonu42:
Yes, well they also can't do data + phone. We can.
[Verizon Samsung Galaxy S III] mybook4:
All, here's a thought. I was looking through the bootloader unlocking thread and noticed that at one point Adam stated that the order of the mmcblk0p partitions doesn't correlate 1 to 1 with the boot order.

I was thinking we should dive more into EVAs thread about the 8960 and see if we can determine the exact boot order.

I believe aboot handles Odin (I'm not 100% sure so someone please correct me if I'm wrong). If aboot (or whoever controls Odin comm) takes control before the modem, then we probably will not hard brick if we flash an AT&T modem. We would be soft bricked and simply have to flash a properly signed modem (vzw) to unbrick.

---------- Post added at 08:38 PM ---------- Previous post was at 08:02 PM ----------

Not sure if this is 100% accurate, but from these two posts, I think appsbl is aboot

http://xdaforums.com/showpost.php?p=30055671&postcount=241

http://xdaforums.com/showpost.php?p=30056934&postcount=242

That is really promising, because it could mean that we'd get access to Odin even if we flash a non-vzw modem.

The only thing that has me worried is this:

"SBL3/APPSBL/HLOS

• SBL3 (Krait SBL) loads and authenticates APPSBL and apps kernel

• Krait executes APPSBL and HLOS

• Krait loads and authenticates modem Hexagon firmware and

Hexagon software images, then takes them out of reset as needed

• Krait loads and authenticates LPA Hexagon image, then takes it out

of reset as needed

• Krait loads and authenticates DSPS ARM7 images, then takes them

out of reset as needed

• Krait loads and authenticates RIVA ARM9 images, then takes them

out of reset as needed

• Order of loading modem Hexagon, LPA Hexagon, and DSPS ARM7

can be decided by HLOS"

http://dl.dropbox.com/u/56104625/attachment.jpeg

So much seems to be going on in parallel during SBL3/APPSBL/HLOS. I don't have a very firm grasp on it right now. This is speculation, but I'm afraid that the Loki Daemon (enabling us to use Odin) wouldn't be able to start or run uninterrupted before Trust Zone found out about the non-vzw modem and kicked the phone into emergency download mode. Hopefully this isn't the case, and when we press the download mode button combo (Down+Home+Power) the execution doesn't care to continue execution on to HLOS (which appears to start the modem and other auxiliary processors).
[Verizon Samsung Galaxy S III] ac21365:
VERY interesting find, mybook! It'd be nice if we could get confirmation on that assumption, I think it'd make life a lot easier for all of us without the possibility of insta-brick looming over everyone's head.

Flashing an ATT/Tmob radio might be something I would be interested in if we can reasonably assume flashing a foreign radio wouldn't brick the phone.

Joel, I gave this a shot earlier this evening, but could not get the change to stick after a restart. Double checked that SU was granted to the editor I used, no dice.
[Verizon Samsung Galaxy S III] mybook4:
The more reading I do, the more confident I am becoming that flashing the AT&T modem will not brick our phone. Current reasons:

1) The MSM8960_Boot_Architecture.pdf slideshow from this post http://xdaforums.com/showpost.php?p=30055671&postcount=241 (page 9) states in the SBL3, "3. Check the Download mode/Mass Storage mode for software flashing" happens before loading APPSBL and HLOS. Initiating download mode may cause execution to stay in SBL3 or jump to either a different part of APPSBL/aboot or somewhere else entirely.

2) APPSBL is aboot. We have an unsecure aboot parition. Our unsecure aboot parition doesn't check the kernel for proper signature. It may also not check HLOS (if HLOS is the modem), and actually allow it to run.

I'm not sure if HLOS is the modem partition or not. The flashable vzw modem zips that invisiblek posted on rootzwiki name the modem image NON-HLOS.bin. I sent him a PM to ask why the name.

I'm still learning...I would like to just bite the bullet and flash the AT&T modem, but it'd be quite an expensive blunder if I'm wrong.
[Verizon Samsung Galaxy S III] renzo.olivares:
you really shouldn't have to flash an att modem to get gsm working
[Verizon Samsung Galaxy S III] ac21365:
Eh?

Long story short:

On a stock Verizon radio, "GSM" works. I myself have had voice/text/data working over GPRS and EDGE on both AT&T and T-Mobile. The 'advertised' GSM part works just fine.

On a stock Verizon radio, "WCDMA" works on 2100mHz, as spelled out in the Tech Manual found elsewhere on XDA. Several of us, including myself, have proof of H/H+ working on 2100 (my recent trip to Germany, for instance).

---------------------------------------------------------------------

This thread is about:

Making our Verizon GS3 operate WCDMA on the PCS 1900mHz band, and possibly on the AWS frequencies (1700/2100) that T-Mobile USA uses.

The radio flashing part is what we need info on. In order to enable PCS or AWS WCDMA, we figure flashing a new radio onto our phone might enable WCDMA in the same regard as flashing a different radio to the Galaxy Note did.

Yuh.
[Verizon Samsung Galaxy S III] mybook4:
Talked with InvisibleK. He doesn't know what HLOS means, but he did mention that the VZW modems (and most likely the AT&T ones as well) are simply FAT images.

I was able to mount the modem partition in OSX (and see its files) by simply extracting NON-HLOS.bin from the modem CWM zip, renaming to NON-HLOS.img, and letting Disk Utility mount the image. The same could be done in linux with the "mount" command (although I haven't tried it).

There were 84 files inside (almost all binary files). This info could prove helpful if we get to the reverse compiling stage (to make things more manageable). Although this is VERY complicated and I'm being VERY optimistic, but if our unsecure aboot will let non vzw modem code run, we could potentially change the modem code to enable the 1900Mhz WCDMA capabilities, or study both the Verizon and AT&T modems to see if a hybrid modem could be made.

First things first, we need to know if an AT&T modem will hard brick us. Anyone have brass ones or JTAG?

---------- Post added 27th September 2012 at 12:14 AM ---------- Previous post was 26th September 2012 at 11:34 PM ----------

Guys, koriotto in this post stated that he tried flashing several modems.

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

From the description, I'm not sure he knew when he did it that there could potentially be a problem in doing so.

Anyway, it seems that he didn't brick his phone by doing it.
[Verizon Samsung Galaxy S III] newuser134:
Hey mybook, koriotto was kind enough to pm me back, and he wrote this:

I believe that just like you said, he wasn't even aware that flashing the modem might brick the phone, I think he really did do it, and he was still able to get to CWM later to reflash his original modem. I'm still not telling anyone to flash an att modem, but it's starting to seem really likely that it won't brick. Is there ANYBODY with JTAG that would be willing to try this for us to help a little?
[Verizon Samsung Galaxy S III] newuser134:
Well, gsm AND wcdma are already working, just no wcdma on the pcs 1900 frequency. We're just trying to unlock the correct band, this is almost identical to the situation for the i717 Note, gsm or wcdma is there, flashing the T-Mobile GS2 modem just unlocked access to the AWS band, flashing an alternate or a hybrid modem on an i535 might do the same on 1900 band on this phone.
[Verizon Samsung Galaxy S III] E:V:A:
Did you guys see this thread?

(Have you tried it?)

Just IMHO, I'd refrain from flashing anything until you have exhausted the possibilities for manually changing settings using either service menu's or QPST software.

To me this sound like proof enough, that you do not need to flash anything new! You just have to properly tweak the roaming and network settings...

(And make it stick!)

Correct. HLOS = "High Level Operating System" (I.e. AOS, Linux kernel, Windows, etc)

Please dump the list of files in "code" tags [#], so we can see them.

Here is the Samsung specified partition layout for the I535:

And YES, they are not in order of booting.
[Verizon Samsung Galaxy S III] mybook4:
The reporting of "Unknown" is a vzw SecSettings.apk incompatibility. Doesn't mean are prevented from getting it to work. It means SecSettings.apk is confused.

Also, I've decompiled the Phone Info app. It's a shell app that simply launches the "Testing" settings of SecSettings.apk. I've decompiled the SecSettings.apk. It interfaces with classes in android's "internal" API to change radio settings. It could be a simple change of modem mode to make the things work on AT&T.

Our best bet for now is to

1) flash an AT&T modem then rom. Then try to get the hspa+ working.

It is very doubtful that flashing a TMobile rom will work (as I believe the TMobile version actually uses another Qualcomm chip for the AWS frequencies).

2) If we can verify that flashing an AT&T modem won't brick our device and that we can get AT&T hspa+ working, then the next step would be to try a customized modem (change a few bytes in the signature). If this works, then the door is open to custom modem creation. It would be amazing if we could just tweak the vzw modem to add 1900Mhz WCDMA support (so we could use both verizon and AT&T without changing roms and modems; although it isn't a big deal to CWM zip a modem and then restore a nandroid).

I've got work all day, but I think tonight is gonna be a good progress night.

PS, I'm willing to put up $25 towards replacement cost if someone hard bricks their phone trying to flash an AT&T modem. If others do the same we may collectively take on the risk, rather than it all fall on the shoulders of one.
[Verizon Samsung Galaxy S III] E:V:A:
First try the following (modified from here):

1. Open the keypad and dial [B]*#22745927[/B]
2. Enable hidden menu
3. Go back to the keypad and dial [B]*#[/B][B]2263#[/B]
4. Select RF band and/or post a screen-shot...
[Verizon Samsung Galaxy S III] E:V:A:
I wouldn't change it unless you're sure that there exists a property with that name. Then I'd rather change the original to a "0".

One more thing. I'd suspect that there could also be some kind of operator lock in place. I.e. a mechanism for preventing Verizon users to use ATT networks and vice-verse. Have anyone checked to make sure there is no such thing going on?
[Verizon Samsung Galaxy S III] ac21365:
Thanks. I haven't enabled this menu yet, but the field test function of the netmonitor app has enabled similar menus. Unfortunately, none of the settings would stick in netmonitor regarding wcdma bands (tested it with the AT&T sim, it refused to acknowledge any WCDMA towers when showing all nearby connections in netmonitor). I will try the built in hidden menu hopefully today and see if I can't coax it into working.

E:V:A, as far as a carrier lock goes, when using the GSM radios, there doesn't seem to be any blocking mechanism. I have made both T-Mobile and AT&T work on my phone with usable call/text/data. If there is a lock, it would only be on the WCDMA part (assuming we can get 1900 WCDMA to work)
[Verizon Samsung Galaxy S III] newuser134:
Hi E:V:A,

Very glad to see you here, we need someone with your level of knowledge of the CPU and boot chain.

As for the lock mechanism, there shouldn't be any because I've also got voice/text/edge data to work on both AT&T and t-mobile. Using the service menu *#2263# (after I installed an AT&T rom successfully a few days ago), and also with netmonitor, I could go into the band selection menu, all gsm bands would stick (showed a * next to them after selection and signal would momentarily disappear), but only IMT2000 (2100 MHz) would stick under wcdma, and unless I chose wcdma 2100, the signal would just continue to stay on gsm as if no changes were made, it wouldn't momentarily show the circle with the diagonal line in it. It would be too much of a coincidence that there would be a network lock on the same band which seems to be disabled and won't take the changes on the phone. It seems from the band selection menu to me, that the hardware is there, but something software related that Verizon put in place, if not the modem files then something else, is preventing that band from being selected and being activated in the phone menus. Another reason I really think it is that way, is that the wcdma on AWS 1700/2100 MHz band that t-mobile uses was entirely not there, even in the menus, which also strengthens the idea that hardware for the 1700 MHz band is probably not on this phone, but it is there for 1900 MHz, otherwise why would the selection be programmed into the phone secSelectoin menu?

As for the other post where you said that it is proof enough that 2100 MHz works, that it should be achieved with only tweaks in menu settings, I refer to the Note i717 case, it would also not work on AWS 1700 by just changing settings, until the modem from a t-mobile phone (GS2) was flashed, then it unlocked that band, so the hardware would not let itself be enabled with the AT&T modem on the Note. The i535 seems a lot like that too, but I could be wrong. However, we have tried almost everything on the UMTS band selection menu on netmonitor and on the *#2263# menu.
[Verizon Samsung Galaxy S III] newuser134:
I will also gladly put $25 towards replacing a bricked phone, but only as long as someone waits for everyone on here to say "flash the AT&T modem" and not just does it in a haste. I'd still like to exhaust all other options, or get a definite confirmation that I won't brick before someone flashes an AT&T modem. I would also like to see first if any dev with jtag will volunteer to help us try flashing a different modem, since the dev knows it can be recovered from with jtag. If none of that is achievable, then yes, I'd be willing to just try it and help the person if the phone is bricked, bu let's hope it won't get to that. Also, this is separate from the bounty to unlock the 1900 MHz band.
[Verizon Samsung Galaxy S III] mybook4:
I agree completely. We should exhaust all resources first. FYI, if we do get down to a gutsy decision to flash, I'd be willing to do it.
[Verizon Samsung Galaxy S III] newuser134:
Cool, great. Hope this enables us to get somewhere with 1900 MHz. The $30 plan with unlimited data/5Gb of H+ data on t-mobile looks very tempting after these 2 years if Verizon doesn't bring back their unlimited data or does something to compete, or if they don't stop locking the bootloader on every new phone while all other carriers leave them unlocked, I just don't know how long one can keep dealing with these things so they can just do whatever they want without any remorse about their customers. I'm just really hoping the modem will not brick the phone.
[Verizon Samsung Galaxy S III] E:V:A:
I was referring to this part:

And I think you must be a poet:

Because I've been reading that very long sentence several times now, and still have no idea what you are saying.

So when "they" brought their i535s to Germany, they had 2100 working or not? How about 1900? (Did they have to change any settings?) I must admit I'm getting confused with all these bands. Let's try to stay on the ones you want to get...

Another thing is that the Service menu's in the past have had some funny behavior of not sticking its settings, unless you "back"-out of it. I.e. Do not hit "END/exit" if there is such a button... Would be good if someone could confirm that.

AND BEFORE anyone starts cross-flashing stuff, someone need to (at least) compare the authentication certificates between Verizon, T-mobile, ATT or what-have-you, in the various boot loaders leading up to the "modem" image. And even if they are the same there is no guarantee that it will work, whatsoever. The more I think about this, the less likely I think this is going to work... I hope I'm wrong.

But I do think that soft bricking by flashing wrong modem is easily repairable, unless Samsung/Qualcomm have some very dirty tricks in their modem images/boot-loaders. (Like updating your bootloaders, blowing an qfuse or something...)