yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Droidriven:
You may as well be asking why you can't stick your hand in fire. The obvious answer is because it will burn you. It doesn't matter which hand you use or which fire you stick it in, the results would be the same. I could go into a long technical and scientific explanation of why the fire would burn your hand but in the end it boils down to "it will burn you". That is all that needs to be said for you to get the point.

Any other modem flashed on the ST S3 will PERMANENTLY brick it.

Forget the idea, it just won't work. You are looking at it too simplistically. The devil is in the details. The stock firmwares are device model number specific no matter how you slice it, regardless of hardware.

If you want to make a brick in an effort to try and disprove that then by all means, go right ahead. Its obvious that you are determined to try it and that you're convinced it will work. With that being said,, why even post or ask about it if you're gonna do it anyway.

Give it a try and let me know how it goes. I already know what the results will be. The hardware between the models is the same, that is why the CUSTOM ROMs can be shared between the models as long as a few system files are switched to accommodate the device they are flashed on but the STOCK firmwares can not be shared in the same manner.

I said in my first reply that there are parts of the stock firmware that reside within the device's hardware, these parts of the "firmware" are not flashed to the device's internal memory like software is. They are flashed to the actual hardware pieces on the motherboard itself in much the same manner as the BIOS is flashed to an EEPROM chip on a laptop or PC motherboard. Its the same on those platforms too, if a BIOS that wasn't intended for that specific motherboard is flashed then it bricks the entire system. There are things in the hardware pieces themselves in each model that make your idea not possible.

I would imagine that if you de soldered said hardware pieces and switched them out and re-soldered them on the board then unpacked the stock firmware and switched all the pieces around then maybe what you suggest would work, its a big maybe though.

If your intent is to try and get the 4G to work then you are wasting your time, it was disabled in the hardware itself, not the firmware/software. And even if you soldered working 4G hardware on the board then it still wouldn't work. You're chasing your tail my friend. Sorry.
[Verizon Samsung Galaxy S III] Minnella_essayons:
I not a naive teenager. I asked, you answered but I wasn't sure u understood exactly what I was saying so I went deeper. That doesnt mean I'm determined to try it, that means I'm determined to learn more.

Getting 4g isn't my motivation, this was all just an idea because I thought it would be possible to flash eeproms and all that on the deepest levels, ur saying its not possible so that solves that; ill move on to another idea. Thanks for your help. U may consider working on your demeanor.
[Verizon Samsung Galaxy S III] Droidriven:
Sorry, meant no offense, I explained why it couldn't be done in my first reply with good detail. You didn't understand so I was a bit more exact and serious with the next reply so that you would understand exactly what I meant in my first reply. Your response implied that my first reply of "it can't be done" was being ignored. It was just a little illogical to post your question in a place that people come to find answers from those that know then doubt the response you get from one that knows. That implied no respect for the knowledge that was being shared with you. It would have been different if your response had been questions to clarify parts that you didn't understand, but that isn't how you replied, your reply was "I've done my research and they are all the same so it should work", I merely stated that if you were so convinced then go ahead and do it because you seemed so convinced that you didn't want to hear anything different.

When you deal with the amount of users I deal with that think they know more than you do then you would understand why I responded the way I did. I agree, you asked, I answered with my first reply, that should have been enough.

Do we understand each other now?
[Verizon Samsung Galaxy S III] Minnella_essayons:
Yeah, no worries. Can I ask if u still use the s3? Whats the rom/build u used that impressed u? idc if it needs a sim and apns and whatnot. I've looked at a handful and they all have good/bad. if anybody else cares to chime in, please do.
[Verizon Samsung Galaxy S III] Droidriven:
I still use my S3 as my daily driver, the best ROM I've found is OctOS d2ltevzw, they seem to be ahead of the game compared to the other ROMs, I've had no issues with it and I've been using it since March.

The best recovery is the d2tfnvzw TWRP.

It can be found here.

https://plus.google.com/+DonaldHoskins/posts/FLdc2CkSHRu

Its a zip so you'll have to flash a d2vzw CWM then flash the TWRP, the other d2vzw TWRP's won't mount correctly so use this one.

I believe TWRP manager app will flash the correct TWRP also.
[Verizon Samsung Galaxy S III] ScottDB:
You are correct - TWRP manager will install the TWRP recovery we use on the ST S3.
[Verizon Samsung Galaxy S III] Minnella_essayons:
Right on, thank you. I hadn't come across that yet. I have cwm touch atm so flashing twrp should be a breeze. Ive been keeping an eye out for a vzw 4g sim. All I have is an old byop sim and a micro att sim.
[Verizon Samsung Galaxy S III] Droidriven:
If you've been reading the threads and you want a working ROM without needing a SIM then why not try the Liquidsmooth 4.4.4 that I and others have mentioned and used? The camera works, the only issue I found with that ROM is the stock MMS not working but third party or hangouts works fine. If you would like to try it I have it uploaded to my copy account, I can give you a link to my copy and the Liquidsmooth themed Gapps to go with it and also the liquid kernel that goes with it as well. I actually like it better than most of the lollipop ROMs, it has tons of customizable features, I'd say it has 2-3 times the customizability the LP ROMs have.
[Verizon Samsung Galaxy S III] Minnella_essayons:
Sounds like a winner. wifey loves to customize and I had her try chomp and she loves it so if she's happy I'm happy ;) link here or inbox, don't matter to me. I'm having issues now on my phone w ST not resetting my data limit. I renewed two days ago. So when Im faster than 1.85 kb/s then ill dl. Thanks again.
[Verizon Samsung Galaxy S III] Droidriven:
SIMs can be found on eBay for $2-5, I found one for $1.95 with free shipping a couple of months back, they aren't hard to get.
[Verizon Samsung Galaxy S III] ScottDB:
I'd like to try that Liquidsmooth ROM but can't find the d2vzw version on xda. Can you please send me the link to your copy account so I can try it out?

Thanks...
[Verizon Samsung Galaxy S III] ScottDB:
Here is another link to the TWRP recovery for d2tfnvzw: http://sdboyd56.com/s968c/TWRP-2.8.7.0-d2vzw.zip
[Verizon Samsung Galaxy S III] xXGeminiXx:
I've got one of these phones up and running. Had to use a SIM to get things going as you guys did. I've got it calling and receiving texts, but it can't send. I figured out (I Think) that it's because I was using a canadian sim card. Now I've purchased a new verizon one and put it in there. *228 says it works, but doesn't do anything that I can tell except allow me to restore default APN's and display a list. Selecting any of them (Verizon internet seems the most likely to work) doesn't stick after reboot, and doesn't work. Setting the APN to any of the settings i can find for ST causes the APN To disapear. I believe it vanishes due to the MCC and/or MNC still... They're defaulting on the APN's here to 311 and 480. When i change it to 310 it vanishes. I generally use Handcent for sms, but can't get that working no matter what I've tried. Any hints?
[Verizon Samsung Galaxy S III] Droidriven:
If you edit an existing APN from the list and then save what you edit it will work, the disappearing thing is normal, trying to create a completely new APN and then saving doesn't work, editing the existing ones works. Just edit, save and reboot and you're good to go.
[Verizon Samsung Galaxy S III] xXGeminiXx:
So it does... on the default messaging app anyway. I'm saved!!! Thanks.
[Verizon Samsung Galaxy S III] Droidriven:
Are you having other issues?

What APNs are you using? Where did you get them.
[Verizon Samsung Galaxy S III] revdjenk:
Here's my "strange" question...

I have just acquired a 968c model s3. I currently use tracfone, and I know this ST s3 on stock 4.1.2 cannot be utilized on tracfone service. However, I would like to know if flashing a verizon rom would make it "appear" as a verizon phone? (and then would be acceptable by tracfone?)
[Verizon Samsung Galaxy S III] Droidriven:
The SCH-S968C is a tracfone device, its actually a d2tfnvzw(the "tfn" part stands for tracfone) its on Tracfone/Straight Talk/Net10 running on Verizon towers, just contact Tracfone/Straight Talk/Net10 and get them to setup activation for the device, you should be good to go once you set it up with them and then add airtime.
[Verizon Samsung Galaxy S III] revdjenk:
Tracfone said it can only be used on straight talk. I want to use tracfone.
[Verizon Samsung Galaxy S III] Droidriven:
That's the first I've ever heard of that. Straight talk is part of tracfone, I don't see why they wouldn't allow their own phone on their own network. I would call customer service and ask for someone higher up the chain, the phone agents usually don't know what they are talking about.
[Verizon Samsung Galaxy S III] rixter13:
Since these are the proprietary radio library files, I would like to decompile them both and compare, we need parts of the newer file, but we need to see what was added or removed to make it require the SIM. In the past (mid September) I tried to swap the files and work from that angle, but that failed. I am about to crash for the night, but plan on giving this another shot tomorrow night.

If you want and have the time, look into decompiling APK files, I put the mms.apk out on my google drive (along with the .so and .zip files generated from an online decompiler). The Mms.apk may be able to tell us at least why it prefers the 4G APN's over the 3G ones.
[Verizon Samsung Galaxy S III] Droidriven:
see, I was thinking that was what the deal was, the MMS trying to trans on 4g instead of 3g, as far as the difference between the stock and 3rd party apps, its the only thing that made sense.

I'll check that out as soon as I get setup again but I'll have to pick my way through learning the coding, its been a lot of years since I've done IT or programming and things have changed so much since then, a LONG time and A LOT of change, lol gotta start somewhere. thanks
[Verizon Samsung Galaxy S III] PSG4m3r:
I'm know how to decompile/recompile apk files (I'm trying to do framework-res.apk right now). I'll try it out tomorrow

Sent from my SCH-S968C running CM11
[Verizon Samsung Galaxy S III] Droidriven:
somehow buddy, I KNEW that, lol

---------- Post added at 12:35 AM ---------- Previous post was at 12:31 AM ----------

if we take out the sim necessity, what else would we lose?
[Verizon Samsung Galaxy S III] PSG4m3r:
These aren't radio images for our phone, but the guy has a good explanation of what radios are and how they work, etc.

http://xdaforums.com/galaxy-nexus/verizon-develop/radios-verizon-galaxy-nexus-radios-3-5-t1890585

Looking at the changelogs for CM, I noticed that for m10, it says they dropped support for "obake, toro, & toroplus". I looked up what these were, and found out that they're radios. So CM is dropping support for certain radios, but why?

Sent from my SCH-S968C running CM11
[Verizon Samsung Galaxy S III] heXacode:
Toro is Verizon nexus. Toroplus is sprint nexus. Not sure what obake is.

It could indicate a lot of things... like the radios will never have updates again for them so they've reached their maxed updates. Supporting them would mean keeping them updated when the carriers update theirs. So the carriers don't update them anymore so they drop support and keep the latest. It could mean that it could have issues on 5.0 and there isn't a Dev that knows how to keep the radios updated without carrier help.

There could be several other reasons. If you look at their git and look for radios they may have comments why they dropped support.

There's several theories lol
[Verizon Samsung Galaxy S III] PSG4m3r:
Obake is the DROID MAXX. I looked further into it, and it sounds like support for Tegra and Exynos isn't supposed to last much longer:

http://www.androidauthority.com/cyanogenmod-galaxy-nexus-support-524676/

Sent from my SCH-S968C running CM11
[Verizon Samsung Galaxy S III] rixter13:
I agree that the RIL's are not the radio images, but they are the library files that the radios use... my understanding is when things like dialer are pulled up the RIL's are used to interact with the radio. It stands to reason that the MMS would also use RIL's, and I think that is where we are having the issue. I may be going down the wrong road here (so please stop me if so), but it seems like most of the issues started with the Unifying of the rom (which if you dig into it are different libril*.so files for the different phones/providers), and again there were more issues when the rilblobs got updated in September.
[Verizon Samsung Galaxy S III] heXacode:
What I mentioned yesterday is a clue. How is it that 3rd party apps, such as chomp SMS, are able to send MMS but stock and Hangouts have issues? Chomp SMS states that it grabs the correct APNs from our devices in order to do SMS/MMS. That's what I think is an issue with stock and Hangouts SMS/MMS. There's a bridge missing. I don't think RILs have anything to do with it. I could be wrong but that's baffling how a 3rd party app can do something that stock and Hangouts can't do.
[Verizon Samsung Galaxy S III] rixter13:
I am using hangouts for MMS, I just had to go in and set the APN (MMSC) in hangouts. As for Chomp, by default it didn't work, I had to set the MMSC in it as well.

Here is my thought on the RIL's (still working on proving it). When the MMS app hits the RIL, it looks at something for the APN, in our case since we have to use the SIM card, its pretty likely trying to get the APN from it. With the StraightTalk RIL's there is no confusion on where the APN should come from. Again these are just my thoughts on it, and I may be WAY off base, but I will say that when I worked with Invisablek on this, that is one of the area's he was interested in as well, not to mention that before the September rilblob update CM based roms worked fine without a simcard (I can't say that I used MMS though, so that may have been broken on the first go around back in February during the unification of the rom). The thought mentioned above is just that, it may be way off base and not even close to right, so if someone reads across this and its wrong, please correct me.
[Verizon Samsung Galaxy S III] Droidriven:
motorhead at AA51 specifically mentioned something about a missing partition that samsung forgot from the factory and specifically mention RILs when I was explaining our issue about a week ago to him. What that means for us? I couldn't tell you, just letting you know

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

so, are you saying that on our device if MMS looks for the APNs it is probably going to the SIM to get them but its not finding Straight Talks APNs but it is finding APNs that work on Verizon and that's why 3rd party MMS is working, because third party apps are going out as random data but stock MMS being carrier specific because it is sent from our number isn't going out because the carriers APNs aren't there?
[Verizon Samsung Galaxy S III] rixter13:
I haven't seen anywhere where someone has had a 3rd party app work with MMS without putting in the MMSC. The third party apps allow you to overwrite the APN, where the stock app reads it from the RIL's (I think).
[Verizon Samsung Galaxy S III] Droidriven:
yeah, I got that, my point was the stock is looking for straight talks APNs but since straight talk handles our APNs themselves then its not finding the APNs when it checks the SIM because there are no straight talk APNs there and even if we did have the right straight talk APNs on our phones the way straight talk normally does them then it still woudnt work because the app checks the SIM instead, but since we can manually enter APNs in 3rd party then they work because they aren't looking in the same place for them that the stock is. Am I even close? I'm just trying to follow your thought.
[Verizon Samsung Galaxy S III] rixter13:
I think you are right.
[Verizon Samsung Galaxy S III] Droidriven:
I haven't been as specific with the thought or how to put it out there as what you are saying but I've had the feeling that was what's going on for a week or so, just didn't know how to communicate it but I've tried saying something similar, you guys have just defined it a little better for me to understand it, thanks for making sense of it for me.

---------- Post added at 03:06 PM ---------- Previous post was at 02:51 PM ----------

I'm still wondering if having an actual straight talk SIM would fix it or if the device would still be confused?
[Verizon Samsung Galaxy S III] rixter13:
No, there are no StraightTalk SIMs for Verizon, so since the APN's are carrier specific an AT&T or Sprint SIM won't work either. I have a Verizon SIM in mine right now, but when I get an MMS it says No apn found (or something similar), so I am not 100% sure this theory is correct still.

On a different note I am getting ready to do my own CM12 build so I can start messing around with the ROM internals, I'll keep you posted on the progress of this.
[Verizon Samsung Galaxy S III] Droidriven:
I'd rather have a rom that is for our device specifically so there's no mess for us users to have to clean up just to use it, lol. Modding is cool but only to do extra stuff, not just to get your device working right unless you are porting or building.

---------- Post added at 03:53 PM ---------- Previous post was at 03:48 PM ----------

huh? I called them the other day about getting a sim for the i535, they said the kit on the shelf wouldn't work and that they'd send one for it free if I gave them the MEID, was the representative confused or something? Why are there SO many mixed answers from ST? Do they intentionally put misinformation out to make it hard on us?

---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------

so our only hope is to remove SIM dependency and get ST to do our APNs?
[Verizon Samsung Galaxy S III] rixter13:
Thats the plan, to have a SCH-S968C rom that is.

As far as I know there is no ST SIM for Verizon, the only reason Verizion uses SIM cards are to control the access to their 4G network.

Yes, if our thought process is right that is.
[Verizon Samsung Galaxy S III] PSG4m3r:
If you're getting ready to make a rom for our devices, are you going to base it off of CM like Mastamoon did? And it'd be nice to still get updates. Like, have weeklies or something where you add all the bug fixes that CM added over the last week. Or even make some kind of flashable zip that'll fix the issues that CM has with our phone, so we can still be on CM but have a patch file that we flash whenever we update. Idk just ideas

And that's sweet that we finally have a dev for this phone! This phone could really use its own specific build (d2str? ;D)

Sent from my SCH-S968C running CM11
[Verizon Samsung Galaxy S III] Droidriven:
[emoji2]

---------- Post added at 05:10 PM ---------- Previous post was at 04:58 PM ----------

if he's gonna dev for us he's gonna need guys like you ain't he?

Hmm...CM12 d2stv (it IS the Verizon version)?

Another example CM12 d2sta (at&t)
[Verizon Samsung Galaxy S III] heXacode:
I can help dev if you need me to. I don't have anything set up on new laptop and still need to learn this stuff. I have a lot of time since I have cancer and confined to my house for awhile till I beat the cancer. Sucks but it'll give me something to do if help is needed.
[Verizon Samsung Galaxy S III] Droidriven:
You can beat it man! My dads been through it 3 times including 2 surgeries and he's completely clear now, you got this, never forget that.
[Verizon Samsung Galaxy S III] heXacode:
Thank you bro. I will beat it cause I'm that tough and determined. Bless your dad and glad he beat it!
[Verizon Samsung Galaxy S III] Droidriven:
[emoji6] don't make me start calling you Talledega(too tough to tame).
[Verizon Samsung Galaxy S III] heXacode:
Hahaha funny.
[Verizon Samsung Galaxy S III] Droidriven:
is there any way someone could crack a stock app and put in the same function for manually entering APNs into the stock app and eliminate the need to do the coding necessary to remove our SIM dependency and save yourself some work? it would be easier to mod the app wouldn't it, MMS would work, it would have stock function and appearance, it would eliminate the need to redo the whole ROM.
[Verizon Samsung Galaxy S III] heXacode:
That's why I asked for the gapps package last night. I think there's different text app versions in different gapps. Some don't even have it and use Hangouts as the default for SMS/MMS. Heck some of the Hangouts older versions don't include the APN in its' settings. There's too many variations and I have wondered if by a long shot one makes more difference over others.
[Verizon Samsung Galaxy S III] Droidriven:
if you know what we are looking for or give me some criteria that will work for us I'll do some digging and see what I can come up with.
[Verizon Samsung Galaxy S III] heXacode:
Well I still want to know from that girl what app she used or if she really did use a 3rd party app.

If she used what was in the gapps package then that's our lead. If not then I don't think it will matter what version we use as they may all act the same. So her input is important.

I also will be consulting the Dev of chomp SMS and ask exactly how does his app grab the correct APNs and maybe let him know our issue.

Also the thing about SIMs is I don't think it mattered if one has one in or not. My results are still the same with and without one. rixter13 says his Hangouts work with MMS but it doesn't work for me. He says chomp SMS didn't work but chomp SMS works with MMS for me.

Basically what he has going is the complete opposite of what I have going. I still have the Verizon SIM in. It didn't make any difference with it in or out other than making the phone believes it has a SIM now.

This kind of makes me believe its ROM related because I know he isn't on dirty unicorn. That's the ROM I'm using and I get different results than he does.

It would be more helpful if we all got on the same ROM and gapps package and produce results we need to track down the bugs.
[Verizon Samsung Galaxy S III] PSG4m3r:
[MENTION=3508760]heXacode[/MENTION] Never give up man, you got this. Keep the fight alive. I had to watch my grandma suffer from CJD, a human form of mad cow disease. She slowly started losing functions of her body to the point where she couldn't breathe anymore. She was said to have about 2 months to live, but she was gone in 2 weeks. I visited her several times on her deathbed, each time she was getting progressively worse. She knew she didn't have long to live, but everytime I saw her she had a huge smile on her face and was always in good spirits. I pray you don't have to suffer through the types of things she did, and you seem to still be in pretty good spirits. Keep it going man. Don't let it get to ya.

Sent from my SCH-S968C running CM11
[Verizon Samsung Galaxy S III] heXacode:
Thank you man. That means a lot and I'm sorry your grandma had to suffer through that. Bless her and the life she had.
[Verizon Samsung Galaxy S III] PSG4m3r:
I downloaded an app called Sim Card. Very simple app, but it showed the network type I'm connected to. Here's what I got from it:

Phone type: CDMA

Network Type: EVDO A

So we're on EVDO? :confused:

Sent from my SCH-S968C running CM11