Compatible ROMs from AT&T forum? - Verizon Samsung Galaxy S III

I didn't see a thread for this (unless I'm blind, which is partially true). I saw a post somewhere linking to the Dirty Unicorn ROM in the ATT gs3 section and saw that they had loads of roms. I simply wondered how compatible some of these were with the vzwS3 before I just started flashing away... Or maybe there is a list somewhere I failed to see?

That reminds me...
On my samsung galaxy nexus I used to use a script called rom switcher (or something like that) that allowed you to flash lets say a sprint rom on a gsm phone or a verizon rom on sprint and so on. Without the need for porting.
However I'm not sure if something like this would be applicable to the s3 because of bootloader differences (nexus is unlocked ofc) and other possible hardware issues. Samsung uses unified architecture on gnexus (kernel level at least) across all three platforms. So I'm guessing the same applies to the s3 and if so that wouldn't be a problem in itself so I think the only real major issues would come from the bootloader.
If there are any devs or someone with more knowldge than i who want to see the script just let me know and I'll see if I can get a link to the thread it's in the galaxy nexus apps and themes section.
Anyway just an idea that may be helpful to at least those who are not locked down.
Sent from my SCH-I535 using Tapatalk 2

Thanks for the response! Luckily I'm not locked which is exactly why I was curious. My friend just got a Galaxy S4 i337 and I rooted/safestrapped it for him but in the process noticed lots of Verizon and Sprint roms floating around which got me curious. There's gotta be someone here with said experience right?

Perhaps you could enlist the aid of mohammed.afaneh, shapesblue, prdog or mikeman?
All those guys are good people and always helping around the forums.
I've only had the s3 for a couple months (coming from a Galaxy Nexus r.i.p.) and locked on 4.3 when I got it so not really comfortable experimenting with things just yet. But basically the script just changes some very basic things like build.prop and updater script for example but it worked very well in my experience.
Sent from my SCH-I535 using Tapatalk 2

47th_Ronin said:
Perhaps you could enlist the aid of mohammed.afaneh, shapesblue, prdog or mikeman?
All those guys are good people and always helping around the forums.
I've only had the s3 for a couple months (coming from a Galaxy Nexus r.i.p.) and locked on 4.3 when I got it so not really comfortable experimenting with things just yet. But basically the script just changes some very basic things like build.prop and updater script for example but it worked very well in my experience.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I messaged prdog. Even if I can't get a specific answer I'll gladly accept any information on the topic. I'll even test out a lot of the roms if it isn't too "unsafe" and put together a compatibility list for other VZW users.

pyrite123 said:
I messaged prdog. Even if I can't get a specific answer I'll gladly accept any information on the topic. I'll even test out a lot of the roms if it isn't too "unsafe" and put together a compatibility list for other VZW users.
Click to expand...
Click to collapse
Ports are usually only problamatic with calls and messaging. You have to use Verizon modem and maybe even RIL cause ATT don't have CDMA. Biggest problem is you need Verizon kernel which we don't have.

prdog1 said:
Ports are usually only problamatic with calls and messaging. You have to use Verizon modem and maybe even RIL cause ATT don't have CDMA. Biggest problem is you need Verizon kernel which we don't have.
Click to expand...
Click to collapse
So you're saying there is no way to flash any of the roms and get them fully functioning without a supported kernel? :sadface:
I have an Aroma addiction >;O

pyrite123 said:
So you're saying there is no way to flash any of the roms and get them fully functioning without a supported kernel? :sadface:
I have an Aroma addiction >;O
Click to expand...
Click to collapse
No matter what we do we need a Kernel. Only option for now is AOSP.

prdog1 said:
No matter what we do we need a Kernel. Only option for now is AOSP.
Click to expand...
Click to collapse
Alright, thanks. It's a shame that companies overcomplicate things and can't all just see eye to eye. Oh well such is life. Maybe one day, when the world is taken over by Google, the world will be a happier place and things will be more simple.
[emoji16][emoji184]
Assuming everything applies to Sprint and i9300 ROMs as well?

pyrite123 said:
I didn't see a thread for this (unless I'm blind, which is partially true). I saw a post somewhere linking to the Dirty Unicorn ROM in the ATT gs3 section and saw that they had loads of roms. I simply wondered how compatible some of these were with the vzwS3 before I just started flashing away... Or maybe there is a list somewhere I failed to see?
Click to expand...
Click to collapse
Most of the AOSP ROMs for the S3 that are still being actively developed have moved to putting out one unified build that works on all US variants of the S3. They will use the tag [D2LTE] in the thread title to note that. [D2VZW] is the Verizon version of the phone. So you can use ROMs that advertise compatibility with either D2LTE or D2VZW. The only problem is that as you've seen, since development for the S3 was, for a long time, specific to each carrier's model, the various D2LTE ROMs are kind of spread around among the various forums for each individual S3 model. The LiquidSmooth thread in the AT&T forum, for example, seems to be the only one that gets updated anymore, even though that ROM is built for D2LTE now and works fine on the Verizon S3. Task650's AOKP build runs fine on our phones too and can be found in the AT&T S3 forum.
If you search all forums for the tag [D2LTE], that's a decent way to get an idea of what's out there now.
ETA: I left out something which I hope you know by now: your bootloader needs to be unlocked to use anything with a D2LTE tag. If you took either the Android 4.3 or 4.4.2 updates from Verizon and locked your bootloader, you're out of luck.

Jacquestrapp said:
Most of the AOSP ROMs for the S3 that are still being actively developed have moved to putting out one unified build that works on all US variants of the S3. They will use the tag [D2LTE] in the thread title to note that. [D2VZW] is the Verizon version of the phone. So you can use ROMs that advertise compatibility with either D2LTE or D2VZW. The only problem is that as you've seen, since development for the S3 was, for a long time, specific to each carrier's model, the various D2LTE ROMs are kind of spread around among the various forums for each individual S3 model. The LiquidSmooth thread in the AT&T forum, for example, seems to be the only one that gets updated anymore, even though that ROM is built for D2LTE now and works fine on the Verizon S3. Task650's AOKP build runs fine on our phones too and can be found in the AT&T S3 forum.
If you search all forums for the tag [D2LTE], that's a decent way to get an idea of what's out there now.
ETA: I left out something which I hope you know by now: your bootloader needs to be unlocked to use anything with a D2LTE tag. If you took either the Android 4.3 or 4.4.2 updates from Verizon and locked your bootloader, you're out of luck.
Click to expand...
Click to collapse
Thanks a lot for the tips. From my time at this forum I had kind of put two and two together and assumed that was what the tags stood for. I hadn't thought of using those tags for searching, though. And luckily I got my S3 last year when I did because my bootloader wasn't locked. And just days later I believe they released that dirty OTA

Related

Seperate subforum for Nexus S 4G

So looking through the development subforum I noticed that there's a lot of roms there that will probably not work completely for the NS4G. Should there be a separate development subforum for the NS4g? This would make it easier to determine at a glance if the rom is compatible with the phone. It may at the very least help reduce questions from people new to rooting.
(Update) I'd like to make it clear that this thread is based on the assumption that NS roms do not work on NS4G phones. This has been reported on some roms(mainly, data doesn't work). If they end up being compatible with a minor tweak or something, then by all means discard this. (/update)
+1.
would also help to alleviate the sprint vs. t-mobile/cdma vs. gsm arguments that i'm starting to sense...
That's true...and those flamewars can be quite annoying. I'm sure people would appreciate not having to deal with those as often.
bump +1million.
Bump + 2,000,000
StormCell said:
Bump + 2,000,000
Click to expand...
Click to collapse
that's a pretty legit bump
we for sure need this now that we know the gsm roms may not work.
+1 for adding a CDMA development area so that things will remain less cluttered
OP should add a poll or make another post with a poll so people can vote
And remove [Q] from title it will only get your thread moved to q/a section
Sent from my Nexus S using XDA App
BrianDigital said:
+1 for adding a CDMA development area so that things will remain less cluttered
Click to expand...
Click to collapse
+1 for this +1 bc i'm getting a headache trying to differentiate threads and posts through this clutter
fixxxer2008 said:
we for sure need this now that we know the gsm roms may not work.
Click to expand...
Click to collapse
I'm not so sure that is 100% certain yet.
Support for the Nexus 4G was just added into AOSP Gingerbread branch in 2.3.4. So far none of the custom ROMs like CyanogenMod or MIUI have fully merged 2.3.4 into their code base.
There is a chance we will see "universal" ROMs that will work.
Remember, there were three Nexus S devices even before the 4G: i9020T, i9020A, and i9023. And while those are all "GSM" phones, the radios do not work on each other's 3G networks.
I agree if there is danger of easily flashing something by mistake that will brick your phone, make them separate. And when I was first planning on getting a Nexus, I wanted the same thing. But the truth is, now that I've had a Nexus for almost a month, it would suck to have all the variants split up. The ideal solution would be to all stick together to keep the community of developers larger and to have ROMs and kernels that are easily compatible or at least easily compiled for multiple devices (then each dev thread could just link to each version).
Maybe that won't work, but so far, the 4G "dev" section would have a total of like two threads in it. So why not just wait and see what happens?
rougegoat said:
So looking through the development subforum I noticed that there's a lot of roms there that will probably not work completely for the NS4G. Should there be a separate development subforum for the NS4g? This would make it easier to determine at a glance if the rom is compatible with the phone. It may at the very least help reduce questions from people new to rooting.
Click to expand...
Click to collapse
this might be true, we may need a separate (sub)forum for the NS4G. this phone is still very new and the developers haven't completely dissected the phones software differences yet. Netarchy has already put out a kernel that is compatible for both phones, who's to say that once the differences get sorted out that a rom can't be universal. it would be nice to have one big NS development scene instead of splitting it in two.
just my two cents
I have to agree with joeB on that one
All, just FTR I started this after seeing several ROMs reported as not working with the NS4G. This is assuming that there is some reason why the two aren't completely compatible. If they are, then by all means we should keep the layout the same as it is. I literally just got mine so I haven't had a chance to root or test it, so I'm not a good judge of that fact.
I'll update the first post with the suggestions posted in previous comments.
Not sure if it's been mentioned, but there's separate boards for the gsm hero/ cdma hero :/ seems like we need different forums
Sent from my PC36100 using XDA Premium App
I agree, all these NS4G'ers walking in like they own the place, laying down their threads and disrupting the nice order of things!
matt2053 said:
I'm not so sure that is 100% certain yet.
Support for the Nexus 4G was just added into AOSP Gingerbread branch in 2.3.4. So far none of the custom ROMs like CyanogenMod or MIUI have fully merged 2.3.4 into their code base.
There is a chance we will see "universal" ROMs that will work.
Remember, there were three Nexus S devices even before the 4G: i9020T, i9020A, and i9023. And while those are all "GSM" phones, the radios do not work on each other's 3G networks.
I agree if there is danger of easily flashing something by mistake that will brick your phone, make them separate. And when I was first planning on getting a Nexus, I wanted the same thing. But the truth is, now that I've had a Nexus for almost a month, it would suck to have all the variants split up. The ideal solution would be to all stick together to keep the community of developers larger and to have ROMs and kernels that are easily compatible or at least easily compiled for multiple devices (then each dev thread could just link to each version).
Maybe that won't work, but so far, the 4G "dev" section would have a total of like two threads in it. So why not just wait and see what happens?
Click to expand...
Click to collapse
SuperAosp 8.0 is a complete 2.3.4 custom rom.
We need a NS4G user to extract their radio kernel (D720SPRKD8) So it can be tried out using a custom rom that is fully 2.3.4 such as SuperAosp 8.0
Here is the thread that it needs to be added to:
http://forum.xda-developers.com/showthread.php?t=975105
Sent from my Nexus S using XDA Premium App
I vote for 2 sub / sub forums i.e.
xda-developers > Samsung Nexus S > Nexus S Development
xda-developers > Samsung Nexus S > Nexus S 4G Development
Keeping everything else under the same hat. The roms will have to be different but not the kernels and the rest should be generally the same.
Yes. Sprint Nexus S 4G needs it's own subforum.
Sent from my PC36100 using Tapatalk
Maybe instead of creating deeper and deeper branches of a forum that's already way too branched, people and mods could be smart and label things appropriately.

[Q] Flashing Other Carriers Kernels?

So someone please explain to me how This Is possible. I was under the belief in my understanding of android that this is a BIG NO NO. I do realize and I may not fully understand the similarities and differences between the different versions of the SGS3 but I would think that because of the Radio being different among all of the carriers that Kernels would be totally different as well. I will reference the Fascinate and the Mesmerize for example. Pretty much the same phone but completely different as far as anything and everything development wise. So what it boils down is this
1. Can we flash kernels designed for the At&t, Sprint, or T-Mobile versions of our phone.
2.What versions of the SGS3 can we SAFELY flash Kernels from.
3.How is this possible given the differences in the different phones.(Question for my sake cause I am really curious and hope i can get a good explanation regarding this)
Aali1011 said:
So someone please explain to me how This Is possible. I was under the belief in my understanding of android that this is a BIG NO NO. I do realize and I may not fully understand the similarities and differences between the different versions of the SGS3 but I would think that because of the Radio being different among all of the carriers that Kernels would be totally different as well. I will reference the Fascinate and the Mesmerize for example. Pretty much the same phone but completely different as far as anything and everything development wise. So what it boils down is this
1. Can we flash kernels designed for the At&t, Sprint, or T-Mobile versions of our phone.
2.What versions of the SGS3 can we SAFELY flash Kernels from.
3.How is this possible given the differences in the different phones.(Question for my sake cause I am really curious and hope i can get a good explanation regarding this)
Click to expand...
Click to collapse
There have been some successful instances of sprint kernels being flashed that I've seen, but it is never a great idea to flash kernels not specifically designed for your phone. btw. there are some pretty good kernels available for vzw now
It's a pretty bad idea. There is a very small chance it could work but more than likely it won't boot
arrogantS3 said:
There have been some successful instances of sprint kernels being flashed that I've seen, but it is never a great idea to flash kernels not specifically designed for your phone. btw. there are some pretty good kernels available for vzw now
Click to expand...
Click to collapse
And i figured as much. I am just REALLY surprised it worked and I just kinda wanna know why it worked. The technical reasons to be honest. But to play it safe i will just stick with those kernels that have been made for the Verizon version thus far. I am still hesitant using the Sprint Kernel even knowing it works.
Neverendingxsin said:
It's a pretty bad idea. There is a very small chance it could work but more than likely it won't boot
Click to expand...
Click to collapse
And based of of you saying this and me knowing this is why i ask lol. Cause like arrogant says there have been successful flashes of the Sprint Kernel. Again idk everything there is about Android but i wonder if it possible due to the fact our unlocked bootloader is partially sprint or something along those lines. That is why i was hoping someone would see this and chime in with a technical explanation and then either a go for it, no, or tread with caution. When the phone was being released there was talks of a rom kitchen being established between the carriers and i was hoping that this was a part of that. Meaning that someone who Devs for the AT&T version of the SGS3 can have their rom or kernel ported to Sprint version and then the Verizon and T-Mobile variants. Idk if the kitchen is still a possibility or in the works but it would be cool to see it kernel wise considering most are running AOSP based roms.
I tried to flash att one two days ago, can not turn wifi on....
So, not recommended
Aali1011 said:
And based of of you saying this and me knowing this is why i ask lol. Cause like arrogant says there have been successful flashes of the Sprint Kernel. Again idk everything there is about Android but i wonder if it possible due to the fact our unlocked bootloader is partially sprint or something along those lines. That is why i was hoping someone would see this and chime in with a technical explanation and then either a go for it, no, or tread with caution. When the phone was being released there was talks of a rom kitchen being established between the carriers and i was hoping that this was a part of that. Meaning that someone who Devs for the AT&T version of the SGS3 can have their rom or kernel ported to Sprint version and then the Verizon and T-Mobile variants. Idk if the kitchen is still a possibility or in the works but it would be cool to see it kernel wise considering most are running AOSP based roms.
Click to expand...
Click to collapse
Some kernels could very well work, same as some stock themes for sprint will work with stock roms on verizon (jellybomb domination being one of them) the issue is that some things could be carried over that may not play nice with our phones and vice versa. While it may run perfectly fine, there's a greater risk that it could break something.
I have yet to run an AOSP rom because of the IMEI issues, so i can't really comment on that, but i know if i was going to flash another carriers kernel i would make sure to make a backup first.

No Love For Sprint N5?

What gives? It seems many of the roms in OG or in AD do not work with Sprint, data at least, on the nexus 5. A fix has been found by Team Slim, yet I don't see the roms being updated to work on Sprint. I understand some devs choose not to fix it as they don't run sprint which is fine but why not try fixing it, giving you a larger user base? I bought the N5 because I wanted a true google experience, and figured I would get to try out some awesome roms that were not available for my previous devices, but its almost the same here. This is a legitimate question, and I hope I don't get the usual high horse answer, "why don't you fix it" "we do this for free" etc etc I love that the devs put in personal time, im just looking for answers as to why a fix wouldn't be implemented if it is tested good and working.
Circaflex said:
What gives? It seems many of the roms in OG or in AD do not work with Sprint, data at least, on the nexus 5. A fix has been found by Team Slim, yet I don't see the roms being updated to work on Sprint. I understand some devs choose not to fix it as they don't run sprint which is fine but why not try fixing it, giving you a larger user base? I bought the N5 because I wanted a true google experience, and figured I would get to try out some awesome roms that were not available for my previous devices, but its almost the same here. This is a legitimate question, and I hope I don't get the usual high horse answer, "why don't you fix it" "we do this for free" etc etc I love that the devs put in personal time, im just looking for answers as to why a fix wouldn't be implemented if it is tested good and working.
Click to expand...
Click to collapse
Give it some time....... Its the ONLY CDMA carrier this phone works on... so for most of the devs this is a completely new thing
Or try fixing it yourself, like restore your APN's from a ROM with data working.
Rxpert said:
Give it some time....... Its the ONLY CDMA carrier this phone works on... so for most of the devs this is a completely new thing
Or try fixing it yourself, like restore your APN's from a ROM with data working.
Click to expand...
Click to collapse
the thing is there is a fix, and its proven to work on Slimrom/Slimkat and the code has been put up for use by other devs, that's why im asking this question is it just the devs don't want to support sprint or is there something else
I agree completely. The fix has been posted for weeks now. Any dev releasing a rom without it at this point is being sloppy.
Circaflex said:
What gives? It seems many of the roms in OG or in AD do not work with Sprint, data at least, on the nexus 5. A fix has been found by Team Slim, yet I don't see the roms being updated to work on Sprint. I understand some devs choose not to fix it as they don't run sprint which is fine but why not try fixing it, giving you a larger user base? I bought the N5 because I wanted a true google experience, and figured I would get to try out some awesome roms that were not available for my previous devices, but its almost the same here. This is a legitimate question, and I hope I don't get the usual high horse answer, "why don't you fix it" "we do this for free" etc etc I love that the devs put in personal time, im just looking for answers as to why a fix wouldn't be implemented if it is tested good and working.
Click to expand...
Click to collapse
While I agree that ROM devs should be updating their code with the fix from Slim, one thing I can suggest is maybe just try using a stock rooted ROM with Xposed framework. I am also on Sprint, and while I used to love using SlimBean for my Galaxy S 3, I am also perfectly satisfied with stock Nexus 5 ROMs with Xposed framework and GravityBox. If you're not happy with it, then it's easy to just disable the module and run along. Just something to try out if you're craving more customizability.
metayoshi said:
While I agree that ROM devs should be updating their code with the fix from Slim, one thing I can suggest is maybe just try using a stock rooted ROM with Xposed framework. I am also on Sprint, and while I used to love using SlimBean for my Galaxy S 3, I am also perfectly satisfied with stock Nexus 5 ROMs with Xposed framework and GravityBox. If you're not happy with it, then it's easy to just disable the module and run along. Just something to try out if you're craving more customizability.
Click to expand...
Click to collapse
side note do we know each other? lol same city
Is it only aosp that don't work? Stock works I assume?
Have you tried posting the link to the commit in dev threads asking for it to be implemented? If you're not doing it, maybe no one else is either
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Circaflex said:
side note do we know each other? lol same city
Click to expand...
Click to collapse
Lol. I doubt it, though it is a small city. I wouldn't be surprised if I passed by you a few times.

How is developer support for the Galaxy line of phones?

Wasn't sure if this is more Q&A or not.
Right now I have the evo 3d. Support for it was really good, actually still 2 or 3 developers working with it, so I'm running kitkat on it right now, which has kept me from feeling the need to upgrade right away.
Anyway, like a lot of other people I'm deciding between the m8 and s5, I might wait a little longer just to see what LG drops. I'm not too familiar with how developer friendly the Galaxy line of phones are, specifically the Sprint models. I've read varying opinions from there's little development outside of some TW roms to development is strong.
Developer support is a big deciding factor for me since it can really allow you to prolong the life of your phone, hence why I'm still using my evo 3d, though it's falling apart now and showing its age so its time to finally bite the bullet and upgrade.
Not asking anyone to predict the future on how dev support will be for the s5 but just looking for input on how it's been for the previous Galaxy phones just so I have some idea. Talking TW roms as well as AOSP roms.
Thanks!
Once you get used to using Odin to flash you'll be fine. I find that Samsung Galaxy's (I've now owned Sprints epic 4g touch, S4 and now S5) have always had excellent support here. I generally only root stock to clean up the crap software but on numerous occasions I've used full roms from XDA to see what else is out there.
A few annoyances:
1) Knox is security software that trips when you modify parts of the system and supposedly Sprint can use a tripped Knox counter to refuse warranty work. This has never happened to me however and I've had to swap handsets many times.
2) Samsung is good at getting you hooked on touchwiz and their ecosystem of apps; I like the smart view covers and it's been tough getting it to work on some of the roms available. I also like the Samsung default camera which thankfully works well on most roms, but some functions within the camera weren't available.
3) Root, in my opinion, is required to make Sprint's handsets run optimally. Mostly because you need to remove the crap software, but so far Chainfire has been fantastic getting root out very quickly for most of the handsets/providers within days of release.
Hope this helps!
So why don't you just look in the respective Galaxy phone forums and see for yourself how development is coming along? It's a simple thing to pop in here and there and just see the different ROMs, etc.
The Galaxy line is by far the most popular Android brand right now and as such gets a lot of developer attention.
I just pray @sacs will get an s5. He had the best rom ever for the s4. Id be willing to drop some $ if it would guarantee he got this phone. Kind of worried about development right now haven't seen any devs talking about doing anything for is yet. I guess thats what you get when you get a phone at release.
Sent from my SM-G900P using Tapatalk
durandetto said:
I just pray @sacs will get an s5. He had the best rom ever for the s4. Id be willing to drop some $ if it would guarantee he got this phone. Kind of worried about development right now haven't seen any devs talking about doing anything for is yet. I guess thats what you get when you get a phone at release.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Unfotunately he won't be. He's devoted to the Note series at the moment, and has not expressed any need to get teh S5
Sent from my SM-G900P using Tapatalk
I just jumped from the S2 to the S5 - I was hooked on Dirty Unicorns and SlimBean, so I'm crossing my fingers they release those (or some variant them) for the S5 soon. I've already rooted mine, but just sitting here waiting with a boring stock ROM is killing me!
Sent from my SM-G900P using Tapatalk
I'm stewing on it. Cost is an obvious factor but I have an idea on how to pull it off.
If do it won't be likely until May at earliest.
Regardless whether I get or not I'll do what I can to help things move along.
Where is the almighty Myn these days....?
Sent from my SM-G900P using xda app-developers app
rhizomorph said:
I just jumped from the S2 to the S5 - I was hooked on Dirty Unicorns and SlimBean, so I'm crossing my fingers they release those (or some variant them) for the S5 soon. I've already rooted mine, but just sitting here waiting with a boring stock ROM is killing me!
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I know what you mean. Same here.
rhizomorph said:
I just jumped from the S2 to the S5 - I was hooked on Dirty Unicorns and SlimBean, so I'm crossing my fingers they release those (or some variant them) for the S5 soon. I've already rooted mine, but just sitting here waiting with a boring stock ROM is killing me!
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Robbie Doo said:
I know what you mean. Same here.
Click to expand...
Click to collapse
Once we get our trees up Slim will be one of the first I build
The S2 was my first time playing around with custom ROMs, and by the time I got around to it there were already several available - how long does it usually take custom ROMs to hit the community when a new phone comes out? Are we talking months?
Sent from my SM-G900P using Tapatalk
bmark34 said:
Where is the almighty Myn these days....?
Sent from my SM-G900P using xda app-developers app
Click to expand...
Click to collapse
Myn switched over to T-mobile years ago, but I don't think he does much develop like he used to
Sent from my SM-G900P using Tapatalk
I love Samsung...but looks like the majority of Devs went to the M8...reason why I switched over....both are amazing devices...but I love to have a phones with a lot of options....but im sure both phones with have good support....

Just got an s5 and (edit) Keeping it, Now I have more questions. Yes I've read...

Edit now that the first part is out of the way, Please scroll down to the bottom for another question, Just trying to keep everything orgainized if possible. Hope This doesn't go in q & a.
Hey fellows, I just bought a s5 and can return it within two days for a full refund. Cost me 140 plus tax, used in great condition no scratches at all on the screen, and got a nice case with it. Was going to order an LG G3 since I'd been doing a bunch of research on it, but came around this and figured I'd give it a whirl. I did a little research on xda while in the store before buying it.
Now that I've been home and reading and reading and reading, I've got it rooted using the lollipop root thread which requires you to use odin. No biggie there but the LP safestrap wouldn't install. And after root I can't install apps from the play store anymore. Error 494 or something like that sorry I'm not more specific.
Right now it has the latest and greatest OTA B1B? I can't remember all four off hand. Some thread I've read have suggested that it is possible to install safestrap and then install rom's but I'm unclear if I have to downgrade though odin flash a different kernel or what. I'm kinda afraid to do too much too it without making a backup because I'd need to get it back to stock before I return it if I do.
I guess my questions are, will I be able to install alliance rom? I don't believe so since it's on a different base. Will I be able to do anything to it other than root? It's not a bad device by all means, but If development is dying, and it's locked down so tight I couldn't squeeze a hair in there, I see no reason to keep it. Again, i've been cramming all evening on all threads, and some say it's possible to get safestrap for lp on there with root, to install TW roms. I know I'll never be able to get AOSP stuff on there regardless.
I could probably get by with just root and debloating. But The alliance rom has some nice themeing options that I'd like.
If you guys were me and please be honest, would you keep it and try to get it to work, or just return it for a refund? I had an s3 but never took any OTA's so I could install roms until my eyes turned blue even though development was slowing on it when mine broke down..
Also do you guys have any idea why the play store isn't working anymore? I'm tempted to factory reset now probably losing root in the process, just to try to get my play store working again.
Any and all thoughts will be appreciated. Again I've studied almost all the faq type all in one general help threads and I've never dealt with safe strap before but at this point I can't even install that. The apk installs but clicking install with root access does nothing.
thanks for any input provided.
griz
Well Looks like I've got safestrap installed with the bok3 kernel although the device came with the BPB1 kernel / firmware. So does this mean that I can only install roms now that are lollipop with bok3 as their kernel? And would you still return the device to order a G3 which has better specs and more ongoing development?
Depends. Download "eMMC Brickbug Check" from the play store and post a screenshot of it.
Honestly, having played a lot with various ROMS on this phones, I can say that my fav is the current stock MM. Fast, great performance and battery life, and hopefully, we will get root eventually. In the mean time, Iam not really missing it.
Sent from my SM-T810 using Tapatalk
Thanks for the input the emmc check said the brick bug wasn't present. I've got to have root so mm is not an option. I need root for things like tibu and to set enforce =0 for selinux to use my old game pad which isn't 100% necessary but nice when I want to use it. This stock rom seems to drink battery life. Do you think I could install alliance or another debloaTed rom?
griz.droidx said:
Thanks for the input the emmc check said the brick bug wasn't present. I've got to have root so mm is not an option. I need root for things like tibu and to set enforce =0 for selinux to use my old game pad which isn't 100% necessary but nice when I want to use it. This stock rom seems to drink battery life. Do you think I could install alliance or another debloaTed rom?
Click to expand...
Click to collapse
B1B is not a build, so you should check that. All lollipop builds can be rooted, and in certain situations marshmallow can be downgraded. Especially if you can unlock the bootloader. You should really check the development thread before you just give up on the device.
Please I don't wish to start a war, just a informative Pro and Con.
Nandr0idC0nsumer thanks for the tip on that App, I ran it iniitally but didn't do the entire scan. I'm doing that as I type this. (It finished and read test passed 132s 14.7GB 114.5MB/s Under emmc chip it reads:
Type MAG2GC
Date 05/98
CID a very long string.
FwRev:00x0
Brick Bug NO. Same Chip
I was hoping this would test to see if I could make it a dev edition but I'll read more on that later.
Now, Even though this isn't the device I initially wanted, I found it in mint condition and with it and the case (Bulky but I weed eat, mow, and stuff, a Lunatik Tatik Extreme that I've read good reviews on every though it's bulky but it's red so I don't have to see the gold, and from what I've read protects well and looks Heavy Duty) and transfer of my Selectel service only paid around 160 after tax. I ended up with a gold colored model, with stock lollipop,
The baseband now says BOK3 but had something Newer BPB1 the first night I got it, I read and read and then read some more as I'm new to safestrap but not to Sammy having had an S3, nor to flashing as I've also owned a DX and DX2(bought used mainly for the sdcard at the time for 20 bucks and to use as a wifi remote)
My questions are as follows. One person above musiclover7 said he's perfectly satisfied with MM non-rooted, I assume an OTA maybe?
I rooted using the odin lollipop method, then installed Alliance Rom to start with as it seemed compatible, and I like the customization ability. I prefer AOSP for just this reason and this was why I was leary about getting this device, the locked bootloader. I've read a little about a lot of rom's available, Although Alliance is highly customizable in the looks dept, and I used the extreme Debloat scropt/zip when flashing all those options are a bit much and it can take time to get the look just right especially with the Black glass mod/zip which I remember from Alliance for the S3, on the old S3 I only ran TW occasionally, mailnly running SLIM, then Nameless, then AICP at the very end. because I'm a sucker for the T-mo theme engine. Aesthetics are very important to me.
One question is with the note roms's and S6/7 ported roms why do I need S-pen when I don't have a note? Why do I need the edge stuff built in when the device isn't an edge? What can that do? I know I have a lot more reading to do but I just want to get a general concensus on what people are running and why, if you are only on TW roms? I haven't seen any themes available in the theme section and I can't stand all the white in settings and such on a stock rom. Nor can I stand the Sammy/VZW bloat. I'm looking at Phoenix which is based on a phone rom with edge support? Am I missing something here? And with the note rom's why would I need the S-pen which I may not have to install if it's aroma based or just freeze/delete it after installation. I have xposed installed because I prefer the net stats app to any other net stat's app out there. I know Wanam is available and gravity for stock roms. I also recall using a module that let me use T-Mo themes on rom's, but I believe the roms I used that on was an AOSP based rom that didn't have T-MO or Layers Implemented yet, like slim around the KK/LP era if memory serves me and it may not.
SO What roms are you using and why? Again, I know people hate threads like this I have no intention of starting a war of roms. It'd be better if I did have the unlocked BL edition or could make it so but I've not got that far yet. Please do not hate on other peoples work. We're all in this together, and most work borrows from others work anyway. And what I've loved about Andy from the DX days is that one size doesn't fit all. We had Bur based roms, CM7 (with most all stock features added eventually), and WizardOO's awesome MIUI builds. And WIz's awesome preboot menu that let one choose a governor and overclock and such without the need for an app. That was an awesome tool back in the day. I'll never forget Wizard00's work on that nor the work done by the main CM7 dev, and those two did help one another figure things out like getting HDMI working.
Anyway, sorry for the rants, and so many questions, I know it'll be impossible to answer all, but I'll edit the Title and Tags to hopefully help other users in the future.
Thanks for reading my TLDR post. Those who know me know I tend to go into way too much detail, and sometimes not the details needed.
Thanks again, I look forward to hearing what you guys have to say.
griz
griz.droidx said:
Nandr0idC0nsumer thanks for the tip on that App, I ran it iniitally but didn't do the entire scan. I'm doing that as I type this. (It finished and read test passed 132s 14.7GB 114.5MB/s Under emmc chip it reads:
Type MAG2GC
Date 05/98
CID a very long string.
FwRev:00x0
Brick Bug NO. Same Chip
I was hoping this would test to see if I could make it a dev edition but I'll read more on that later.
Now, Even though this isn't the device I initially wanted, I found it in mint condition and with it and the case (Bulky but I weed eat, mow, and stuff, a Lunatik Tatik Extreme that I've read good reviews on every though it's bulky but it's red so I don't have to see the gold, and from what I've read protects well and looks Heavy Duty) and transfer of my Selectel service only paid around 160 after tax. I ended up with a gold colored model, with stock lollipop,
The baseband now says BOK3 but had something Newer BPB1 the first night I got it, I read and read and then read some more as I'm new to safestrap but not to Sammy having had an S3, nor to flashing as I've also owned a DX and DX2(bought used mainly for the sdcard at the time for 20 bucks and to use as a wifi remote)
My questions are as follows. One person above musiclover7 said he's perfectly satisfied with MM non-rooted, I assume an OTA maybe?
I rooted using the odin lollipop method, then installed Alliance Rom to start with as it seemed compatible, and I like the customization ability. I prefer AOSP for just this reason and this was why I was leary about getting this device, the locked bootloader. I've read a little about a lot of rom's available, Although Alliance is highly customizable in the looks dept, and I used the extreme Debloat scropt/zip when flashing all those options are a bit much and it can take time to get the look just right especially with the Black glass mod/zip which I remember from Alliance for the S3, on the old S3 I only ran TW occasionally, mailnly running SLIM, then Nameless, then AICP at the very end. because I'm a sucker for the T-mo theme engine. Aesthetics are very important to me.
One question is with the note roms's and S6/7 ported roms why do I need S-pen when I don't have a note? Why do I need the edge stuff built in when the device isn't an edge? What can that do? I know I have a lot more reading to do but I just want to get a general concensus on what people are running and why, if you are only on TW roms? I haven't seen any themes available in the theme section and I can't stand all the white in settings and such on a stock rom. Nor can I stand the Sammy/VZW bloat. I'm looking at Phoenix which is based on a phone rom with edge support? Am I missing something here? And with the note rom's why would I need the S-pen which I may not have to install if it's aroma based or just freeze/delete it after installation. I have xposed installed because I prefer the net stats app to any other net stat's app out there. I know Wanam is available and gravity for stock roms. I also recall using a module that let me use T-Mo themes on rom's, but I believe the roms I used that on was an AOSP based rom that didn't have T-MO or Layers Implemented yet, like slim around the KK/LP era if memory serves me and it may not.
SO What roms are you using and why? Again, I know people hate threads like this I have no intention of starting a war of roms. It'd be better if I did have the unlocked BL edition or could make it so but I've not got that far yet. Please do not hate on other peoples work. We're all in this together, and most work borrows from others work anyway. And what I've loved about Andy from the DX days is that one size doesn't fit all. We had Bur based roms, CM7 (with most all stock features added eventually), and WizardOO's awesome MIUI builds. And WIz's awesome preboot menu that let one choose a governor and overclock and such without the need for an app. That was an awesome tool back in the day. I'll never forget Wizard00's work on that nor the work done by the main CM7 dev, and those two did help one another figure things out like getting HDMI working.
Anyway, sorry for the rants, and so many questions, I know it'll be impossible to answer all, but I'll edit the Title and Tags to hopefully help other users in the future.
Thanks for reading my TLDR post. Those who know me know I tend to go into way too much detail, and sometimes not the details needed.
Thanks again, I look forward to hearing what you guys have to say.
griz
Click to expand...
Click to collapse
Will read the whole thing tomarrow, but what's the first 2 numbers of your CID?
Nandr0idC0nsumer said:
Will read the whole thing tomarrow, but what's the first 2 numbers of your CID?
Click to expand...
Click to collapse
I agree with Nandr0idC0nsumer. You didn't specify what the eMMC Brickbug check read. I'm showing the first 2 numbers needed but if you've read majority of these forums, you'd know what it means...lol
it'd mean I'd hit the jack pot but I figured that'd be mighty sliim.. LOL... But I'm going to give it another whirl. I haven't read everything, but most of the faq's and all-in-one threads. Then the root for lollipop thread along with safestrap, because I was completely new to safestrap, but I could have been wasting my time with safestrap, I certainly hope the hell that I am that would be so awesome, the best news for me since...... I can't remember when the last time I was so lucky.
I can't be this lucky.. Got some reading to do... I should've listened.........
I should have followed through with the posts from you guys but I honestly didn't think I'd be that luck.y... Didn't think I'd have that kind of karma... In the Morning Ladies and Gentlemen and dudes named ben. Thanks guys for hitting me in the mouth...
HOLY bat crap bat man.. Does this mean what I think it does.. I hope so.. I think I've got a new thread to read..
This is for users with 15' Sasmung eMMC's not users with 11 Toshiba eMMC's. You can check this by reading the file
/sys/block/mmcblk0/device/cid
Just the first 2 15xxxxxxxxxxxxxxxxxxxxxx or 11xxxxxxxxxxxxxxxxxxxxxxx(my number of x's are random, just read the first 2)
We still are unsure if changing the CID causes app store, verification, activation, provision, or other issues, everything you do is at your own risk!
REACTIVATION LOCK MUST BE TURNED OFF. YOU'VE BEEN WARNED
Click to expand...
Click to collapse
I figured that would be few and far between, I hope I can magically transform my phone into a dev model.... I'm assuming that'd be as good as having my old S3 without taking that bad OTA... OMG.. I'm hoping this is good news. I'm off to read the post.. I gotta work in the morning but now... Wow..... It's like a natural high if it means what I think it does. I hoonestly figured that would be like finding a needle in a haystack and my luck is never that good.. But I'm not going to count my chickens before they hatch...
Ohh attached below is the screenshot...
I'm not one for emoji's but...
Just hope I dont screw something up trying to make a dev edition out of my device... ....
I blocked out the last number as in the example above, I don't know why that's important but since the other poster did, I figure I'd better too. Monkey see Monkey doo.
PS Sorry for the mess.. as Han would say.. yeah.. I'm that old..
@griz.droidx Flash stock PB1, then root it, then unlock the bootloader! You have, by chance and luck alone, bought an S5 with the ability to unlock it
Yes you can flash Cyanogenmod. Yes you can flash MM and root it. Basically do whatever you feel like
Question is stock PB1 a stock MM build? I'll do some reading to find out, but I have a nandroid of my BPB8 lollipop rom that's already rooted From reading the unlocking thread, and maybe I missed something I just install the APK and bam I'm unlocked. I'm guessing that once I'm unlocked, and rooted, I need to find myself a TWRP for the device. I thought I could just un-install safe strap from Alliance, Unlock and then flash a recovery.
I figured I was lucky in getting one that can be unlocked or made into a dev edition. I'm never that lucky. But on the unlucky, it appears that I have to now flash roms from the unified thread. And from what I've been able to pick up in an hour or so last night and a little at work today, I'd be best to flash only rom's for Verizon specifically. I don't know exactly to to make the others work with a Verizon MVNO but I'm certain that the VZW one's will because on the S3 I could flash any VZW rom and my MVNO (Selectel) worked. I'm hoping to find a build of AICP since that's what I was using with my S3 before it bit the dust. But flashing fever usually hits and I'm sure I'll try others.
Still doesn't look like there's much development going on for the unlocked builds. But at least I can cruise around on AOSP if I want. But the Extreme Debloat of alliance has been doing pretty good already even without my usually tweaking using autostarts and AFWALL, I do miss the privacy manager most of all from AOSP. I just think that is easier to use than the AP OPS version that's included in Alliance.
Is your phone unlocked? if so What rom are you running, and which ones have you ttied?
Lastly, I want to thank everyone for all their assistance in this thread so far. And for those of you who aren't unlocked, I'd still be interested in knowing which TW rom's you're using and stuff like that. I like aesthetics, and don't like the stock TW look of white everywhere, and I've read that with OLED or OMLED or whatever theyre called, the more black there is the easier it is on the battery. Probably doesn't make a huge difference but every little bit helps.
You can run ROM's from the Android Development thread and Unified thread
The question is unless they're for vzw on particular will they work with my my mvno. I hope so. . But I don't think they will without. Changing apns. Or may not have the proper frequencies enabled for vzw
Sent from my SM-G900V using Tapatalk
Oh, that i wouldn't know. Maybe someone will come across this and have an answer for you
griz.droidx said:
The question is unless they're for vzw on particular will they work with my my mvno. I hope so. . But I don't think they will without. Changing apns. Or may not have the proper frequencies enabled for vzw
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Flash PB1 from SamMobile (PB1 is stock 5.0 Lollipop rom) and then root, unlock, and flash TWRP.
To simplify, tell me the ROM you want to flash and I'll tell you if it's compatible if you'd like.
EDIT: Yes roms have to be Verizon-compatible. And no changing apns will not help
Thanks for offering to check. . I've found that aicp. Resurrection remix. CM and Phoenix have versions for vzw. . Thanks for offering to check for me. . Thanks for simplifying the unlock and add aosp roms instructions. . I've read and re-read them. . A couple things I'm worried about ate what hardware features may no longer work like the fingerprint reader at least in the one kernel I found. Even unlocked and thrilled as I am I want to make sure as much of it works as possible with aosp. And I don't want to take a performance hit but doubt that'll happen. . Even when the numbers have said I did take a hit in the past three seat of the pants feel said otherwise. . Thanks again to you and everyone else who have replied. . Im still wondering which tw roms people prefer. . Alliance with extreme debloat has did better than I expected. .
Sent from my SM-G900V using Tapatalk
You'll have to make your best judgement. Users install the ROM's and use them as a DD to suit their likings and what they like for a ROM. You'll just have to read the OP of the said ROM and see for yourself....Good luck and HAPPY ROM'n
Hey fellows I am tickled pink that I accidentally ended up with a dev edition. Even though there's not a whole lot of AOSP out there for the VZW version of the s5, I do like me some AOSP. Always have the AOSP ROM bug hit me back with my DX. Having said all that, I was pretty satisfied with the Alliance Rom, and I'd imagine other TW roms have much to offer. I chose Alliance because I'd ran it on the S3 a few times especially when I needed to compare TW to AOSP. I did not upgrade using the method above but I appreciate all the replies from "Nandr0idC0nsumer" very much. I once thought about installing a MM pre rooted firmware first actually. If I could find just the modem and anything else like that which may help the performance and usability of my MM CM based RR rom, I might consider it. And it shouldn't be as difficult now with the unlocked BL. Although safestrap worked nicely for what it's meant to do.
After reading here and elsewhere about unlocking and installing AOSP, I decided to just run the apk which is option one in the how to unlock post, ran the app it installs, checked in recovery to see that it said developer, then using flashify I installed a TWRP image that I downloaded from somewhere. I think TWRP was just for klte though and not kltevzw specifically, but don't quote me on that. Lastly, I booted straight into twrp using the hardware buttons on a reboot to install the AOSP based rom and GAPPS. Easy Peasy. I'm looking for a kernel now, but since I feel that the fingerprint scanner works much better for me in AOSP, I don't want to get a kernel and mess that up even though I could always back it up first. or just re-install the rom.
Hopefully someone will come across this thread and find it useful. If anyone feels like it I'd still like to hear about those different TW roms, and why we'd want to use one for the note? or need one with the S-pen app? Can the S5 work as well as the note for writing on the screen using the S-Pen stuff?
Thanks again, and have a great weekend. Anyone who has any questions for me feel free to PM me. If I don't reply immediately don't think I'm putting you off I sometimes , many times, forget to check or don't notice that I have new images to read. Although help is better from the forum since you can many more opinions, and that's what it's for anyway.

Categories

Resources