yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Droidriven:
so do you intend to swap or decompile both and paste parts of the ST into the other? Just trying to reason out what you are doing for myself so I understand it better, I am pretty new at this depth, been rooting and romming a short time but only been into modding system for about two months or so so don't get too far over my head, I can follow you but don't take it for granted that I understand what you are saying, I'm learning, you won't have to wait on me ill catch up quick just give ne the time and resources.

---------- Post added at 11:18 PM ---------- Previous post was at 11:05 PM ----------

to give you an idea when, CM11 4.4 was the first ROM I ever flashed lol
[Verizon Samsung Galaxy S III] Droidriven:
Here's the stock H1 PIT file for anyone that may at some point need it, unzip the file and its ready to use, if the links are dead and won't download just let me know, I'm keeping a copy to post later.
[Verizon Samsung Galaxy S III] Droidriven:
[MENTION=5806583]canodroid15[/MENTION], [MENTION=2133806]kenny1974[/MENTION], [MENTION=589932]Rixter[/MENTION] since they solved the SIM issue in the d2spr , would we be able to take the d2spr ROMs and use rilblobs and build prop edits to make a d2spr ROM work like the tmobile guys do with the d2att ROMs, just curious if you guys thought it might work so we can use ROMs without a SIM.
[Verizon Samsung Galaxy S III] heXacode:
Well this sucks... CM no longer supports T-Mobile theme engine so a lot of good themes will no longer work or show up in the themeing catalog. It's almost pointless to even merge the theme engine into Lollipop now. Mastamoons CM12 ROM just merged it and none of my favorite themes show up because of CM quitting support of it. Ridiculous.
[Verizon Samsung Galaxy S III] rixter13:
I tried that same thing back in September to no avail. Changing the build.prop and ril-blobs isn't the real issue... there is some hard code saying that our phone needs a sim before it will allow data. I will eventually find time to modify this and see if I can make it work, but between work and home life, I just haven't been able to make the time to do it.
[Verizon Samsung Galaxy S III] Droidriven:
They fixed it in the d2spr, I bet you'll find the solution if you dig into their ROM and do a comparison. Since rixter is too busy then maybe you should take a look [MENTION=6321832]giveerapearlnecklace[/MENTION], mastamoon is also looking into it.
[Verizon Samsung Galaxy S III] giveerapearlnecklace:
Yeah I just recently got Android kitchen up and running I'll look into that rom when I get a chance

Getting the kitchen running was kind of a pain and I still don't have it a hundred percent I have to use virtual linux and all the command w indow stuff is different then windows, I'm still getting used to it.

I have a few ideas I'm gonna keep trying and that's great mastamoons looking into it, nobody else seems to give a **** and I guess I can't blame em.

Also goin to play with the camera try to get that working 100 percent I have a 2 year old and I can't have a buggy ass camera [MENTION=3691964]rixter13[/MENTION] yep I mostly gave up on that as well
[Verizon Samsung Galaxy S III] Droidriven:
Its the d2spr CM12, Ive got the link if you need it.
[Verizon Samsung Galaxy S III] giveerapearlnecklace:
ya sure ill take it
[Verizon Samsung Galaxy S III] Droidriven:
Ok, here's the link for d2spr CM12, its the only CM12 that Sprint has. There a couple of other lollipop ROMs for Sprint but only one CM12. None of the Sprint ROMs use a SIM so we may be able to look at more than just one ROM an do a comparison between them all and find the commonalities between them, what we want has to be in the parts they share then compared with ours and maybe we'll find it.

https://www.androidfilehost.com/?w=files&flid=21660
[Verizon Samsung Galaxy S III] giveerapearlnecklace:
thanks and my thoughts as well, I've been using the stock Rom for a comparison and I think I may be getting somewhere.

on a related note has anyone tried anything with the stock system/ect/apns-conf.xml? I've read a few things about people with other phones losing data on a new rom, they made a flashable zip of there APN-conf.xml file, flashed it and data was restored. I was just wondering if anyone has tried messing with this file at all....I think it could be

part

of the issue.
[Verizon Samsung Galaxy S III] Droidriven:
Yeah, PSG4m3r messed around with the apn conf.xml back in Nov but didn't pan out.
[Verizon Samsung Galaxy S III] Droidriven:
Ok guys, masta just dropped this in my inbox, [MENTION=6321832]giveerapearlnecklace[/MENTION] take a look at this and see what you think.

Quoted from mastamoons PM

So basically these are the prop differences between d2spr and d2vzw... None of these exist in the d2spr build.prop. If its a prop thats causing the sim issue, its likely one of these. The top 5 or so are what I would think would be the most likely. Should be able to delete these all entirely and see what happens.

ro.cdma.subscribe_on_ruim_ready=true

ril.subscription.types=NV,RUIM

ro.telephony.default_cdma_sub=0

ro.config.multimode_cdma=1

DEVICE_PROVISIONED=1

ro.config.combined_signal=true

ro.gsm.data_retry_config=max_retries=infinite,5000,5000,60000,120000,480000,900000

ro.telephony.get_imsi_from_sim=true

ro.ril.fast.dormancy.rule=0

BUT... d2spr not needing a SIM might be more about its RIL blobs then anything else. Likely a combination of the 2. So on top of build prop edits, you'd likely need the d2spr RIL blobs. I can put together a zip of those also. 99.9% of the code is shared between d2 devices.. its only carrier specific stuff (props and blobs) that differ. Thankfully those are the easiest things to muck with.

[MENTION=6321832]giveerapearlnecklace[/MENTION], see if you can test this, do the build prop edits he suggests and see if putting the rilblobs together in a zip will get us hooked up to where we can do away with the SIM, if so this could theoretically be applied to the other d2lte ROMs, keeping my fingers crossed, let me know if anybody comes up with anything.

Nevermind on the rilblob zip, mastamoon just passed it to me, here it is

mastamoon.truelinux.net/other/d2spr_rilblobs.zip

I tested this, I deleted the lines in d2vzw CM12 that didn't exist in d2spr CM12 build prop, copied stock apns cof.xml and spn conf.xml over to CM12 d2vzw, flashed rilblob.zip provided by mastamoon but no go.

Maybe there's something in d2spr build prop that isn't in d2vzw instead of the other way around, maybe identify lines that d2spr DOES have that d2vzw doesn't then paste said lines to d2vzw build prop or maybe some edits that need to be done to apns conf.xml and spn conf xml? Are there any d2vzw or d2lte lollipop ROMs that have the setting to manually set APNs in system settings?
[Verizon Samsung Galaxy S III] Droidriven:
[MENTION=6321832]giveerapearlnecklace[/MENTION]? Have you tried anything in addition to this?
[Verizon Samsung Galaxy S III] Droidriven:
After trying mastas suggestions above and contacting him with results this is what he sent me

I took a look at the way d2lte worked on CM11.. It looks like these props were set...

ro.product.model=SCH-S968C

ro.telephony.default_cdma_sub=1

ro.telephony.default_network=4

ro.cdma.home.operator.numeric=310000

ro.cdma.home.operator.alpha=TracFone

telephony.sms.pseudo_multipart=0

telephony.lteOnCdmaDevice=1

ril.subscription.types=NV,RUIM

ro.cdma.subscribe_on_ruim_ready=true

ro.ril.svdo=true

and it uses VZW RIL blobs...

info.script.AppendExtra('ifelse(is_substring("S968 C", getprop("ro.bootloader")), run_program("/sbin/sh", "-c", "busybox cp -R /system/blobs/vzw/* /system/"));')

SOOOOO... Maybe instead of deleting these props, which is how cm12 on spr seems to do it, maybe you just need to modify the vzw cm12 build.prop with any differences above.

I get what he says about the CM11 build prop but I don't get what he says about the rilblob at the bottom, does the additional rilblob stuff he listed at the bottom need to be added to our existing rilblob in addition to the zip he put together or does the zip need to be removed then add what he listed this time? I'm new at this but I'm trying to find answers that those of you that understand it and can apply it.

[MENTION=6321832]giveerapearlnecklace[/MENTION], have you got anything to add to this? What are your ideas and what have you tried?
[Verizon Samsung Galaxy S III] giveerapearlnecklace:
I was just starting to mess around with the cm 11 stuff, and ive been working alot but I have the weekend off, Im probly going to be snowed in so I plan to do some tinkering tomorrow. but right now I'm tried as hell and im going to bed.

and thank you for that zip, I'll have to thank mastamoon as well thats def going to help

I'm think yes we need the ril's but Im honestly way to tried to think right now im going elbow deep into my phone tomorow so we'll just have to see what happens;)
[Verizon Samsung Galaxy S III] Droidriven:
We've got a whole d2tfn CM12 ROM of our own courtesy of Motorhead on the way for us right now, it should be posted in the morning I'm testing tomorrow, I'll let you know how it goes. No need to work on d2vzw or d2lte now I hope! We think we got the sim fix and two initial roms have already rolled out but needs more. ;)

He switched libs and then started running adb commands and pasting in each thing that gave an error as we chased it back then he started a ROM
[Verizon Samsung Galaxy S III] giveerapearlnecklace:
Damn that's killer!! Thank god well have our own rom theres other issues besides the sim thing:) And on top of that I think I just got the sim thing almost figured out 2 lol its totally in the props file, masta was saying they both share the same Verizon rils and they do. I lazily pasted half the kitkat bprop into the cm12, sims disabled and it boots the only thing that needs to be done now is system select needs to be set from home (default) to automatic to enable data (just like kitkat) BUT there's a snag I can't get into the mobile settings it locks up because of my lazy editing so I need to either change this manually or figure out what line I added to the props file that made the settings unstable I'm going to go through it line by line and I'll post the results

[MENTION=968349]motorhead[/MENTION] ty for the help its great to have someone that knows there stuff helping us out
[Verizon Samsung Galaxy S III] giveerapearlnecklace:
well Im glad someones making a rom because I failed lol. I didn't get anywhere but I did learn that deleting # Use IMSI from SIM

ro.telephony.get_imsi_from_sim=true disables the use of a sim but no mater what other lines I edited or rils swapped out I couldn't get any service, just a no service Icon. I can't wait for the new ROM thanks [MENTION=5691352]N_psycho_PD_uh?[/MENTION] for all the help im glad someones getting somewhere.
[Verizon Samsung Galaxy S III] Droidriven:
Its booting has our RILD but still queries SIM, still adb chasing as of right now, just run command patch run command patch back to the end of the line hopefully;)

Testing atm, don't know and can't say what or if will be let out for release, its nothing official but its being tossed around to see what happens. Its not my place to say its a ROM or not, it may not even work so nobody get your hopes up, get excited or go crazy spreading word of something that may not even exist, its only in works, no promises guys.
[Verizon Samsung Galaxy S III] Droidriven:
We tried deleting that too but as you say can't get service back changing anything else, maybe that line needs to be edited so that it gets IMSI from system instead of SIM? What to edit the line to idk; it would be nice to get in contact with the CM guys that wrote this part, they understand it better and know what they put in that created SIM dependency, if we can find that out the fix should be simple.
[Verizon Samsung Galaxy S III] dovw:
Sounds from the posts here that you may to some extent be assuming that the reason you are running into a SIM dependency is because you have a device with a SIM slot. Did you consider whether CM12 is SIM dependent because there are relatively few devices that have no SIM card?

Some evidence that's a potential issue is that the Moto G xt1028/xt1031 (my daily driver) which is 3G CDMA ONLY and has no SIM slot at all has no working CM12 - it has no outgoing calls, no 3G data and no stock SMS because of a current CM12 dependency on SIM cards despite the fact that the device has no SIM at all. We have so far only found a CM12 SIM dependency in the SetupWizard- but we suspect more dependencies in the RIL - here's the SetUpWizard dependency:

http://review.cyanogenmod.org/#/c/8...nmod/setupwizard/setup/CMSetupWizardData.java

I don't know how to look through the CM code (the above was caught by someone else) and I don't know what CM12 is like on your device - but if you do find any generic SIM dependencies (not specific to your device having a SIM slot) and you find a workaround - we may be very interested over at this thread on our issue
[Verizon Samsung Galaxy S III] Droidriven:
No we know the SIM dependency is in the RIL, we know that the SIM is built in to CM, this happened back around sept/oct last year with the last d2vzw ROMs on our device, me and [MENTION=2133806]kenny1974[/MENTION] discovered the SIM issue and some of us have been trying to rework the ROMs so that SIM is no longer needed, these ROMs have SIM dependency because they were built for 4g devices which require SIM, I've been digging at this since Nov and I'm working with a few devs on this, we have switched most of everything from our stock and the d2vzw ROMs that didn't require SIM but there's some kind of ghost tucked in CM that needs the SIM and it seems to be in a place or places that normally have nothing to do with connectivity. Its being chased though, it can't run forever. We know WHY it needs a SIM but we can't find HOW to bypass it.

And yes, its a CM12 wide dependency all across the board its in all the newest CM12 ROMs for all devices not just ours.
[Verizon Samsung Galaxy S III] ScottDB:
Has there been any progress on the ROM that motorhead was working on? Just wondering, as it's been two months without any activity in this thread.
[Verizon Samsung Galaxy S III] Droidriven:
No, we made little progress. We got to where everything that actually bypassed the SIM only killed service completely, we narrowed it down to the issue being java related then he stopped working on it. Not sure why he quit though.
[Verizon Samsung Galaxy S III] ScottDB:
That's too bad - I wish I knew Java.
[Verizon Samsung Galaxy S III] ScottDB:
For anyone still needing the H1 baseband file, it is now back up and available on my Webserver, but on a new page:

http://www.sdboyd56.com/s968c/H1baseband.html
[Verizon Samsung Galaxy S III] whodisname:
I took this phone apart and stamped on the motherboard (all one piece) was SGH-1575. Just throwing that out there.
[Verizon Samsung Galaxy S III] canodroid15:
I wish you'd taken a picture of it, were trying to figure out a few things with this phone anyway thanks for the info bro, I did manage to find some relative info on the i-575 but its hard to come by....
[Verizon Samsung Galaxy S III] Droidriven:
I'm not finding much at all about it either.
[Verizon Samsung Galaxy S III] whodisname:
Gimme 10 min
[Verizon Samsung Galaxy S III] whodisname:
And..
[Verizon Samsung Galaxy S III] whodisname:
There is this screw NY the chargingport
[Verizon Samsung Galaxy S III] whodisname:
I was mistaken about the stamp..
[Verizon Samsung Galaxy S III] whodisname:
This part..
[Verizon Samsung Galaxy S III] whodisname:
Motherboard
[Verizon Samsung Galaxy S III] whodisname:
And from finally
[Verizon Samsung Galaxy S III] whodisname:
If you see this and want something specific from r the next hour or so feel free to ask. Once I put it back together tho....

---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------

SCH-1535 stamped on the silver piece. Sorry about that.
[Verizon Samsung Galaxy S III] Droidriven:
Ahhh... That actually makes sense.
[Verizon Samsung Galaxy S III] whodisname:
Yeah, its the over zerizon model. With an unlocked bootloader too. Is there no way t take advantage of that? Like I said I am on an i747, that one (pictred above) I want to mod and give to the wife (who's s5 got hit by a car).

---------- Post added at 12:49 AM ---------- Previous post was at 12:46 AM ----------

LSO, I don't have a PC. Otherwise se I'd have MUCH day fferent questions! ;)
[Verizon Samsung Galaxy S III] Droidriven:
OK, so which actual model do you have?

What does it say behind the battery?

What did it say in system when you got it?

Does the model number on the label behind battery match the mobo?

With all the model numbers you've been using you've got me unclear what you're dealing with.
[Verizon Samsung Galaxy S III] whodisname:
Sorry. I just rereadthat and confused myself!

The one in the pic and the one I want to work on are the s968c.

I have a i717 also, but I don't need a thing done to it!

---------- Post added at 04:50 AM ---------- Previous post was at 04:48 AM ----------

Yes they all match. 4.1.2 "H2" baseband.
[Verizon Samsung Galaxy S III] ScottDB:
When I first rooted my SCH-968C, I wanted to use TWRP, but it didn't work properly (wouldn't mount any partitions). So I have been using ClockworkMod Touch for the last year, but I still would like to use TWRP, because I like the ability to use custom themes. I checked TWRP again in March 2015 (v2.8.5.0 for d2vzw), but it still wouldn't mount anything. A few days ago, I came across an app called TWRP Manager. I installed it, started the app and it downloaded the latest version (twrp-2.8.7.0-d2vzw.img) and the app installed the recovery image. When finished, it said their was an error, and that TWRP didn't install. (I may have tapped on the install button twice - therefore the error message.) But when I re-booted to recovery, TWRP started up! I have tried it out, and it looks like TWRP is now working correctly with our StraightTalk Galaxy S3 SCH-968C.

Here's a link to an xda forum with some cool themes in the correct resolution:

http://xdaforums.com/galaxy-s3/themes-apps/theme-twrp-recovery-themes-t2426961
[Verizon Samsung Galaxy S III] Minnella_essayons:
I've been reading and reading this and the parent thread, among others, trying to find a workable solution for those on straight talk. I've been working w my wifes phone, ST SCH-968c. Started with the H2 baseband, downgraded, rooted, flashed cwm touch, then tried cm10.1 before I ran into the obvious problems. I restored again w odin and the h1 tar now shea rooted w cwm again but at first data and mms outbound wouldn't work, now neither, only data and calls and txt. now on to the fun part...

I was looking into convincing my ST S3 into believing it was born under the verizon moon. I did some research and found vzw s3's have issues and also lose lte on the ST network. So I began to compare hardware, it appears all of the models among the big carriers are the same. at&t users keep 4g when switching to ST. So if we pay the same for data regardless and have to use simcards to get working 3g and mms, why not convice our sch968c that its an SPH-L710? A quick google search yeilded a stock tar. I can't post links but google this: [ROM][ODIN] SPH-L710 ND8 (ND8 Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted) by rwilco12.

Now before I go flashing this at&t package to my wifes daily phone I need more educated feedback. I wouldn't be doing this until we buy an at&t byop sim for ST and not doing that until I can make a more informed decision.

Great work everyone on this project. Lots of great minds have been in this thread and the other.
[Verizon Samsung Galaxy S III] Droidriven:
Yeah, don't use anything on the ST S3 that isn't made for it, especially the stock AT&T.

When it comes to the AOSP stock ROMs, all the d2xxx ROMs are 98% the same and they can be flashed on any of the d2xxx devices without bricking them. Stock firmware between the d2xxx devices is another world entirely. Custom ROMs don't contain everything that a device needs, there are things that remain on the device from the stock firmware even when a custom ROM is flashed, things like bootloader and modem for example. This is what is meant by the term "firmware" because it is part of the device and is "stored" in the devices hardware itself and not in the device's system or internal memory partitions. These things that remain are generally unsafe to alter because the device won't function correctly without those things present in the form that they are meant to be in.

The parts of the AT&T or other carrier stock firmwares that are meant to remain on the devices cant be used by any of the other devices because they would brick those other devices. Verizon can't use a Sprint bootloader or modem, AT&T can't use Verizon's, the same is true for all the other carriers also. Any attempts at using other carriers bootloader or modems will result in a permanently bricked device.

Now, if you decided you want to use an AT&T(GSM) custom ROM on a Verizon(CDMA) device then you could do so safely but you'd need to make some edits and switch some system files from one to other to get CDMA working vs the GSM that would be in the AT&T ROM, CDMA can't use GSM system files because they are completely different animals.

The only stock firmware that can be flashed on the ST S3 is the stock ST S3 firmware none of the others has even the least bit of a chance of working.

You can use the AT&T device with AT&T ROM on the Straight talk network, you don't need to flash a stock firmware to do this.

As for the ST S3 using a SIM to get 3G data, that's only because the ROM will not let the device get any cell signal or mobile data without it. It has nothing to do with 4G capability, it is only so that the Verizon ROMs can be used on the ST S3, it serves no other purpose than allowing the device to connect to its network. It changes nothing about your service or the type of data you can receive, its only purpose is to actually turn the radio on so that the device can send or receive, without the SIM the device is "blind" to the network and likewise the network is "blind" to the device, neither of them knows that the other is even there without the SIM.
[Verizon Samsung Galaxy S III] Minnella_essayons:
ok, thanks for the quick reply but I'm not sure I was clear enough. I knew about why the sim is needed for 3g cuz I read this whole thread and almost all of the parent. I hadn't gone as far as looking at working att roms yet. the thing is, it seems the s3 was made for all carriers with the same hardware. [Q]"The Samsung Galaxy S III is available in a number of carrier versions in the US. There's one for AT&T (SGH-I747), one for T-Mobile (SGH-T999), one for Sprint (SPH-L710), another one for Verizon (SCH-I535) and another one for U.S. Cellular (SCH-R530). We had the AT&T and the Sprint versions for testing. You should rest assured that hardware- and software-wise all the carrier versions are the same"[/Q] My research shows they are. So the difference is then just carrier specific code and such. Why then couldn't we take everything (including what the roms don't touch) from the att version and replace everything on the straight talk version? its not stripped down or need different drivers. its all the same hardware. I'm talking about cloning the att motherboard essentially. then we could use the d2att roms on our att clones, thereby maintaining root and gaining 4g using the byop sim. I'm not very familiar with the hidden places they stuff carrier code but didn't mastamoon say thats the easiest to tinker with? Why is this not possible? Permissions? Encryption?