yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] sdas683:
New Discovery

Hey guys,

I have discovered a deeper menu:

*#197328640# (System Menu)

»[1] UMTS »[1] Debug Screen »[2] NAS Information »[2] MM Reject Cause (This lists the blocked MCC/MNC From VERIZON!!)

If you select menu button, back « , and go to »[5] MM&GMM RESET REJECT LIST this will clear all of the blocked MCC and MNC codes! This sticks through reboots!

I am just curious if some of y'all can try this and see if it opens up your 3g data, I am in a remote part of N.C. at the moment and don't have a signal! Still tinkering with some ideas though, this might point us in the right direction though! (At least one right direction, I feel there are many.)

P.S. - There may be some other settings that need to chronologically follow, such as change band to WCDMA 1900/all or trying other GSM bands, also changing the NAS control settings and UE State Control to WCDMA.

PLEASE POST SOME RESULTS! THIS WILL NOT HURT YOUR PHONE!
[Verizon Samsung Galaxy S III] LLStarks:
Gave it a try and even played around with the bands in the network control menu.

No dice. Still on EDGE with my TMobile SIM.

It seems that the list never clears once "reset".

If you have a more exact procedure I should follow, I'm more than willing.
[Verizon Samsung Galaxy S III] flipinfin:
Nice write up but that's a g my dude. Ive played with band selection on my tmobile gs2 I get edge with gsm but when I switch to wcdma I get 3g. The verizon gs3 don't have wcdma. If there isn't a way already we need to enable wcdma on Verizon gs3 n we will have 3g possible 4g
[Verizon Samsung Galaxy S III] E:V:A:
​

I don't, but this path was never properly explored. Or if it was, the results were never presented.
[Verizon Samsung Galaxy S III] LLStarks:
I've never been able pull a PRL from the phone, so I'm at a loss in that regard.
[Verizon Samsung Galaxy S III] static.chaos73:
Different Roms

I don't know if this will contribute anything or not, just posting my experience.

I have NET10 on AtT&T SIM for my SCH-I535, running the MIUI v5 ROM. I decided to switch to CM10.2 to see if the data would be any better/faster..no dice. But I did notice that the signal strength/reception was a lot worse. with the MIUI ROM I almost always have 5 bars, but with CM10.2 I was lucky to get 3, and the service totally dropped a few times. I don't know if those ROMs use different PRLs or radios or whatever, but the MIUI Rom definitely has a better signal, for whatever reason.
[Verizon Samsung Galaxy S III] markdapimp:
the S3 is simply in capable of picking up HSPA Frequency's in the USA in Japan and other country's it is able to
[Verizon Samsung Galaxy S III] shonalex:
Any new news with the ML1 modem just released? Does that even make a difference? Just curious.
[Verizon Samsung Galaxy S III] mybook4:
Haven't tested it (sold my S3). Doesn't seem likely that they would add the capability for a device that isn't very new. The S3 is a year and a half old (which is like 105 in human years)
[Verizon Samsung Galaxy S III] ThePagel:
Why would you even post in that case? By the way its more like 85 in human years.
[Verizon Samsung Galaxy S III] mybook4:
85 seems reasonable.

Haha, you're right. It was kind of an empty post. I posted because I was one of the people who were working on this and I've been asked previously to continue the effort.
[Verizon Samsung Galaxy S III] ellokomen:
bad news

So I ended up here after my failed AT commands expedition.

I have read a lot of pages and seems the project is stuck at the NV Files part but I may have some bad news to you guys:

While communicating via AT commands, which talks directly to the qualcomm modem and bypass the OS installed (android itself) , every time I try to set the WCDMA band to other than 2100, the modem says: +CME ERROR: operation not allowed

While I try to set GSM band or WCDMA 2100 it says OK and then sets up the specified band, it fails when I try 850 or 1900 on WCDMA.

So in short we have a new problem in this project: Verizon i535 modem doesn't support WCDMA850 and WCDMA1900 bands at the low level.

Sorry for the bad news.
[Verizon Samsung Galaxy S III] MoodSwinger:
[MENTION=2182736]ellokomen[/MENTION]: would the editing you're attempting to do here be the same that was trying to be done here:

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

with the RadioComm tool?

if not do think something like that (radiocomm hack) would enable the GSM bands available?

Is radiocomm a Motorola only tool?

in the first couple lines of the first main paragraph it references the MSM8960 chipset

@ all:

I'm not a dev by any means just have tried, messed-up, remedied & fixed a bunch. But I went thru enabling GSM on the VZW Moto Droid Bionic, and wonder if any of that procedure would be beneficial here.

for example the build.prop edits, or the RadioComm hack.

I have tried to connect my VZW GS3 to RadioComm, but not sure exactly how. I was going to attempt to see if I could find the same lines & numbers in the NV items, being as VZW blocked GSM on the Bionic, maybe they used the same structure to block the GS3.

Also going to check the build.prop changes & see if they have any effect.

Don't know if any of this will help or maybe point someone in another direction that would help....hoping so.

also would it be possible to flash a "Euro" stock like the International I9300 UK version, into the i535. or maybe the radio config for that model?

Just saw this too....

reading more on another thread it looks like RadioComm is Moto ONLY, so maybe another called "Qualcomm service software"

http://xdaforums.com/showpost.php?p=25362292&postcount=69

Yet a bit more possible info:

http://xdaforums.com/showpost.php?p=27249316&postcount=384&nocache=1&z=200933920233598

Link to XDA thread - [REF][R&D] MSM8960 Info, Architecture and Bootloader(s)

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

Also Please check out this Thread / Question :

[Q] WHY can't we just change the GS3 to a different carrier? (US)

http://xdaforums.com/showthread.php?p=49242680
[Verizon Samsung Galaxy S III] MoodSwinger:
So I pulled the build.prop and only (by my inexperienced eyes), saw one line that might've done something:

# Data modules

ro.use_data_netmgrd=true

Thinking that was some sort of "net manager" maybe it was the block changed it to false, and I lost data completely,

put it back to "true" and connected again.

However looking thru the MSM8960 Architechture thread....

I did notice the same NV line that we changed to enable GSM bands on the Moto Bionic is the same as on this. So maybe the VZW block is on that level and if we can edit the binary the same it will unlock all the GSM freq's available on this device too. Maybe?

From Bionic on T-MO thread:

http://xdaforums.com/showpost.php?p=25549615&postcount=123

In Radiocomm go to MA->CDMA1X->QSC60x5

After it comes up, switch to FTM Common1 tab and wait for the phone to enumerate purple.

On the upper right side in the NVAccess, scroll to NV item 1877 NV_RF_BC_CONFIG_I

Read the value from the device

Replace the first 8 bytes (16 digits) with: 8703E80400000200

Write the data to the device and powercycle.

This will enable GSM/UMTS bands.
[Verizon Samsung Galaxy S III] bedwa:
With the NV editable partitions being pulled and checked from another partition with each boot, this is not possible with the S3 Series.

I had mentioned a while ago that the only way we may be able to do this is to bootjack with something like 2nd boot or safestrap and then followup with custom loading the baseband (If possible with this device) like it is done with AOSP versions of the Milestone 2 and Defy. This is probably going to be the only way to pull it off... if ever.
[Verizon Samsung Galaxy S III] ellokomen:
There are many ways to block certain bands on a handset

By High Level (Patched Android)

By Medium Level ( via the RIL )

By Low Level ( Via Baseband/Modem/Radio etc..)

I recall that time when users with the Nexus 4 were able to enable LTE on the handset just by selecting it on a hidden menu.

In the case of qualcomm chipsets, ( I don't know other chipset makers) the bands to operate are specified in the low level, Qualcomm chips operate on CDMA and GSM/WCDMA modes, and in order to allow/disallow their bands, a firmware needs to be flashed on the CDMA section of the chipset and another one different for the GSM/WCDMA section, I suspect those firmwares are inside the modem.bin file when the flashing procedure is taking place.

When I ran those AT commands, the modem itself rejected the bands telling me it's a low level cap on those bands, because the same hardware is used different carriers and those bands are operable on them.

PS: The RadioComm seems to be a NV File modifier, is different than AT commands
[Verizon Samsung Galaxy S III] bedwa:
The fun part is that with the Bootloader check on the baseband itself, we have to hijack the bootloader to have ANY hope of loading a different baseband to enable those frequencies. Along with the main baseband partition being relocated as the NV partitions every boot, it's a headache.
[Verizon Samsung Galaxy S III] MoodSwinger:
Thanks guys for your patience and the explainations..

Much appreciated, really.

some of this is a bit beyond my understanding at this point but I'm reading up on it.

A few more things I've come across...

apparently according to this thread: http://xdaforums.com/showthread.php?t=2369125

you can un-hard-brick a GS3 by booting it from an external sd-card, and at one point it wipes the sd card, kinda of like, if I'm interpreting correctly, formatting "C" on a PC, so if you can do this, what is it that the phone would check or be able to check, to make sure your flashing the correct stock rom. And if it can't check anything, what would prevent you from putting a different stock image on it and booting / loading that?

This was actually the original "Debrick" thread I saw, and here there's a "caution - wrong letter can wipe your system".

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

and in this thread (granted it's the INT'L version), (will find & fill in the link, but he's starting with a Chinese stock rom and grabs a couple of the files from a UK rom IIRC,

this guy seems to combine components from 2 stock tar files to get the features he wants. I get there are certain ones he felt he had to maintain to make it work, but also he was able to incorporate components from a different stock rom. what about loading an at&t modem bin into the tar file, then loading it that way like a clean full restore?

so is there a system in place hardcoded inside the handset, possibly on the SOC, that has to be checked against to load, and if that's the case, when you load a new stock rom (full size 800M+) is there a file in each version that references something back in the system to "know" that this is a VZW stock and not an AT&T stock. Maybe that's why or how the guy on the INT'L one, knows to keep certain files and can change others.

I'm sorry if some of this seems obviously silly or too novice to you.
[Verizon Samsung Galaxy S III] vegasbomber:
lurking chiming in

been watching this ever since i purchased a verizon galaxy s3 when the post first started too.... love how everyone has been trying hard to get this to work. but do u think that this phone will work with t-mobile sooner? like lte part? cuz tmobile just bought spectrum from verizon...

http bgr.com/2014/01/06/t-mobile-700mhz-spectrum-deal

cant post link ^ cuz im lurker not a poster...

maybe this can help those who want to use this phone on tmobile like me :D sorry if im a bit off topic, ive been back and forth... id also like to donate some time to this project as i have a fully functional Verizon Galaxy S3, and 2 att motherboards and 1 tmobile motherboard.... the ATT & T-Mobile mobos are swapable to each other, but the verizon is slightly different.... so if anyone wants me to try anything i can... i broke all my screens thats why i kept buying them :D

i just want to say keep up the good work guys, im still rooting for this to work so i can use it on any network with full internet :D

thank you

vegasbomber
[Verizon Samsung Galaxy S III] markdapimp:
Nope

---------- Post added at 10:47 AM ---------- Previous post was at 10:45 AM ----------

Nope T Mobile spectrum has a different band and it may have the same frequency but it has different bands
[Verizon Samsung Galaxy S III] Bleezle:
May I flash, please!!

I'm sure this has been asked, but I have read so many forum posts just to get this point, that I'm tired of reading forum posts. I also want to thank everyone that posts and works in developing ways to get around the blocks all these corporate f@#ks put on these phones to control how and where we use OUR phones.

I have the dreaded Verizon build Galaxy S3 (I'm also in no way trying to be part of the developer world I just want my phone to work how I was promised it would) and I'm in South America. I'm stuck on Edge and after reading all the information graciously provided by this forum I'm somewhat screwed. I wish I would have known that the Verizon version of this phone was not truly world compatible, because I would of bought the At&t version. I've been ripping my hair out for the last week trying to figure out why I don't get 3g here, because I was under the false impression that I had a "world phone." F@#K YOU IN THE FACE Verizon!!! Going from 4g to Edge will cause ulcers. :mad:

So, my question is, can I just flash the phone to a local carrier, radio stuff and all, and get 3g? Again, I'm sorry if I've asked a question that has been answered before, but I'm really tired of reading forum posts. Thanks in advance and Verizon can go to hell..... Samsung too. :cyclops:
[Verizon Samsung Galaxy S III] Lrs121:
Nope more than likely it'll brick the phone.
[Verizon Samsung Galaxy S III] t3502rc:
Where in South America? I use my Verizon S3 in Brazil and get 3G.
[Verizon Samsung Galaxy S III] Bleezle:
I'm in Buenos Aires. Is your phone rooted or stock?

Thanks for the quick response.
[Verizon Samsung Galaxy S III] t3502rc:
Yes rooted with liquid smooth.
[Verizon Samsung Galaxy S III] Mrhunter13:
if u wanna get your phone flashed I can help with that
[Verizon Samsung Galaxy S III] Bleezle:
Brazil uses UMTS 2100 which isn't blocked by Verizon. Argentina uses UMTS 1900 which is blocked by Verizon. F@#K YOU, VERIZON!!!!!!

I'll give a $100 to the person that cracks this. I'm going to have buy a new phone, something that I thought I was going to avoid by buying Verizon's alleged "global phone." This phone is almost useless here in it's current state, and I won't be back in the U.S. for a while.

---------- Post added at 01:45 AM ---------- Previous post was at 01:40 AM ----------

I'm in Buenos Aires right now and won't be back in the States for year. Do you know someone here or can you show me how to do it?
[Verizon Samsung Galaxy S III] Mrhunter13:
i flash remotely
[Verizon Samsung Galaxy S III] Bleezle:
Thanks for the offer, but there are loads of places here in the city that I can get my phone flashed, and I can look them in the eye. I think I'm just going to buy something here and send this one back to the States or buy one with a cracked screen here and swap out the guts.

**UPDATE**

I called Verizon. Come to find out the service that I signed up with, Claro, is their PRL in Argentina. Which causes the phone to get stuck on the Edge network. Has nothing to do with the problem being talked about here. They told me if I want 3g or HSPA I have to go to either, Movistar, or Personal in Buenos Aires. The same issue might arise for people in other countries in South America that have Claro and Verizon phones.
[Verizon Samsung Galaxy S III] kblack44903:
Not sure if it's already been done but has anyone tried to change everything in buildprop to d2att from d2vz then flash at&t modem?
[Verizon Samsung Galaxy S III] bedwa:
Bootloader stops it from loading. Period.
[Verizon Samsung Galaxy S III] meskes:
That's a shame.
[Verizon Samsung Galaxy S III] bedwa:
It is. Again, I said it a while back, but do not have the experience to pull it off, but the only way I can see it happening is through a similar method of how the Motorola Defy/Bravo/Milestone 2 uses 2nd Boot (predates safestrap) to load their kernel and other hardware firmware, including a way to manually load and change basebands with a reboot.

Not sure how to implement with the S III, but if it could be pulled off, we would have a way to cross enable all S IIIs no matter the carrier.

Edit: NOTE: This is only a theory, not a certainty.
[Verizon Samsung Galaxy S III] meskes:
2nd init is nothing more than an ugly hack. I am personally glad that we don't have to deal with it, on the S3.
[Verizon Samsung Galaxy S III] bedwa:
And I don't blame anyone for not wanting to have to deal with it. Just trying to offer suggestions or ideas.

As you can see, I'm using a Droid Bionic hacked to work with AT&T along with using a Safestrapped Kexec'd CM11. Works fairly well at the moment, but only due to the hard work of the guys over in the Bionic forum, including hashcode.

As I was saying, it's hacky, but I feel it's going to be the only way we can bootjack what we need to in order to get where we need.
[Verizon Samsung Galaxy S III] meskes:
I wouldn't mind seeing if a hybrid modem work, though...
[Verizon Samsung Galaxy S III] kblack44903:
Ok so I changed almost everything in buildprop to d2att and sgh-i747 have more bars Internet is faster but still on edge seems like I made some progress but not what I wanted seen on here some one said they had a g instead of e that happened to me one time before I edited build prop also had a second menu in mobile networks and every apn for every carrier... that's still there but did something and second menu disappeared any one know how to at least change the e to a g? Did everything in that earlier post but still only get a e
[Verizon Samsung Galaxy S III] Mrhunter13:
its never gonna happen that easy ...
[Verizon Samsung Galaxy S III] hackwack:
wtf?

Has everyone just given up on this noble venture? I'd really like to use my S3 on the new Cricket GSM 4g network
[Verizon Samsung Galaxy S III] meskes:
Pretty sure the general consensus is that there is a physical hardware limitation... Though, with Verizon now deploying AWS, I guess the only way we'll know for sure, is if they update the modem to support the additional band...
[Verizon Samsung Galaxy S III] LLStarks:
I put the I535OYUDNE1 (Kitkat OTA) modem on my phone. I'm not expecting anything new, but this is a curious modem.

It uses the S3 Dev Edition naming scheme (OYU) instead of VRU.

If I can find my T-Mobile SIM, I'll pop it in.
[Verizon Samsung Galaxy S III] meskes:
I noticed that too... Can't wait for the baseband guys to sort all this out for us.
[Verizon Samsung Galaxy S III] An0nYm0u5.bat:
Its definitely not hardware related. It is carrier blocked code. Wriiten exactly where im not sure yet. But if gone as far as to completely alter build prop. Change csc. Even altered to the point everything I connect to thinks its the 9300. Ir w.e. it is. I know this. Im going to get it. No challenge has forgone me yet. Neither shall this. Ill leave some s.s. to see what I've done. Any ideas. Send them in. Unless you fry a phone. Theirs no such things as a hat brick. Or w.e. you want to call it. So im up for anything. Provided its legal. I could of done that long ago and been 3g. Duh. Lol
[Verizon Samsung Galaxy S III] An0nYm0u5.bat:
I'm seriously wondering if a flash all the way back to Samsung prior to ship is possible?? Other than that any input is welcome. ANY!!!!
[Verizon Samsung Galaxy S III] preusstang:
I wonder if the qualcom band unlock would work for us:

http://xdaforums.com/crossdevice-dev/sony/thread-progress-please-leave-im-updating-t2871269

I've moved to a G3 but I still have my SCH-i535 lying around. Im gonna install QPST at home and give it a go. I'll report back.

EDIT: Nevermind. They're editing just the 1877 NV item that's been tried already in this thread :(
[Verizon Samsung Galaxy S III] D00RBELL:
I got $100 for AT&T/T-Mobile H+ data speed
[Verizon Samsung Galaxy S III] LLStarks:
I can't get the settings to stick.

Maybe we really have no choice but to do a 2nd-init.
[Verizon Samsung Galaxy S III] An0nYm0u5.bat:
Not sure what ever happened. About having both i747 and i535 and pulling from both. But I have both phones as I am still fighting to get hspa 3g or hspa+ or anything besides this stupid edge2. Hahaha. I have a cwn image of the entire i747. I'm far from dumb and actually make good money with phones/pc work I do. But I cant figure this out. And I know Samsung keeps it from happening... but what if we could reflash the whole. Entire phone. Its the EXACT same phone. And I found Verizon's signature file. I have to go through my stuff to find it. But why couldn't we use it against the boot loader if it uses this to make all yes or no decisions. Just seems every one is complacent in thinking lately. "In the box" so to say instead of thinking outside. Cause if you think.. everything we've done up until today

, was never done or heard of then. That's why were called developers....... I just want other input as I am my harshest critic and no matter my knowledge. Skills or ways . I still look up to Many of you and consider myself self behind when comparing with. Thanks brother. Just thinking ceaselessly . Also. Willing to try anything you or some of like skills think with either phone.
[Verizon Samsung Galaxy S III] budaim:
Any updates on getting 3g or 4g on the S3 i535 on T-Mobile?
[Verizon Samsung Galaxy S III] drake90001:
Hey guys, I have a Verizon GS3 with an unlock bootloader (I'm assuming and I can flash custom kernels, CyanogenMod, etc) and I'm currently using it on AT&T with the limited EDGE speeds. I am more than willing to help test anything that could help and get at least 3G working on here.
[Verizon Samsung Galaxy S III] LLStarks:
Once I buy the Nexus 6 or something and get a new T-Mobile SIM, I will be aggressively pursuing the elusive band unlock for our S3.

http://xdaforums.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059

http://xdaforums.com/galaxy-s5/general/guide-enable-unlock-edit-add-gsm-lte-t2948822

The guide is a little weird compared to what I know and have seen so far, but I'm sure I can adapt.
[Verizon Samsung Galaxy S III] :
I believe the hardware of the phone is not capable of this
[Verizon Samsung Galaxy S III] LLStarks:
*post removed as it no longer applies*

Thought I hosed my EFS, disregard
[Verizon Samsung Galaxy S III] jdshewey:
I think perhaps you can't write the settings because you have not yet unlocked the phone for writing using the samsung password for your phone. This same password allows you to change the ESN/MEID/IMEI but may also free up other items as well. I was trying to flash the 337_aws.qcn to get my phone operating in the correct bands, but was unable to do it until I plugged in the password.

Note:

Yes, I know that changing the MEID is illegal and disallowed in this forum, but in this case, that is not the goal or end game.
[Verizon Samsung Galaxy S III] LLStarks:
There's no password to enter, period. SPL and similar do not apply to this situation.

QPST/QXDM's EFS viewer gives me pretty much unrestricted access to the NV items.

Getting things to persist through reboots has been tricky. Some things stick others don't.

Interestingly enough, I've been messing around LTE bands. Haven't made a concerted effort yet, but it seems that the phone is more than happy to let you break Verizon's Band 13 (700 MHz Block C). Band 13 corresponds to a value of 4096 (don't quote me on this) for the LTE band NV items in QXDM. Efforts to enable multiple bands haven't worked but I can't help but wonder if I could enable Band 2 or 17 instead of Band 13. Not sure if Band 4 (AWS) counts as one "band" for the purpose of what I'm trying to do. I'd be shocked if Band 2 didn't work, but I don't have an AT&T sim on me at the moment.

Most of this is spitballing, so don't get too excited.