I am basing this thread on "[Q] How To Root the Straight Talk SCH-S968C Samsung Galaxy S III" (the latter portion of it)
Hey all, creating a new thread on this as it has blew up in the past couple of days and got the original thread all sorts of off topic. I am sharing my findings here in hopes that it will help others get Lollipop running on their StraightTalk S3 (or KK roms based off of CM after the 9/7 updates).
First a little history. Before the unified roms I was running d2vzw LiquidSmooth without any issue, then in late Feburary (2/26) the S3Unified rom was built, putting the correct rilblobs in /system/lib upon boot (if I am reading the code right that is). This was when I noticed that the Unified rom broke the S3 ST phone (no data), so I spent a couple of days researching and learning how to build roms and came up with this commit to LiquidSmooth, I noticed a few days later that it was pulled into the CM source, so all roms were back to working with our phone. I also vaguely remember something with rilblobs needing reverted around this time. So at this time, everything was working, up until the 9/7 CM updates where the rilblobs were once again changed. I worked with one of the CM devs (invisablek) on this issue and we were never really able to figure out what the issue was, the radio was throwing all sorts of odd error messages and would never connect. During that time there was enough of a change that even the old rilblobs wouldn't work (spent about a week worth of evenings trying to no avail). So I ended up giving up until 5.0 hit.
Yesterday I came across a d2lte CM12 build! Flashed it and was quite impressed to see everything working except mobile (both calling and data). In that thread I ran across the first linked thread here and seen that inserting a sim card seemed to work, so I hit up a coworker (on AT&T) and asked him if I could borrow his sim. He agreed, so I pulled the battery, popped in the sim and was AMAZED to see mobile working again, did a test call, browsed on 3g, and everything was working quite well. Got home last night and found an old (deactivated) sim card in my basement, popped it and have ran CM12 all day. Hooked it up to the bluetooth head unit in the car, setup a second account for my son, taken a few pictures, everything seems to be working fine.
One thing that has bugged me for a while (which I rarely use) was that MMS stopped working (not sure exactly when, but I'd guess back on 2/26), so I spent some time today pulling apart files, modifying things, and really haven't gained much (at least for the stock MMS). I did get hangouts working as MMS by adding an apn (Hangouts -> Settings -> SMS -> SMS Enabled, then scroll to the bottom and click on Access Point Names, Add one with the following settings Name Verizon Internet, MMSC http://mms.vtext.com/servlets/mms MMS proxy and port are blank, MCC 311 and MNC 480 ). I haven't completely given up on the stock messenger app, but I am done with it tonight.
Here are the things I have done so far:
Modified build prop to include TracFone Settings
added apns-conf.xml to /system/etc (and modified it a few times)
a few different apps to change APN settings (seems like all of them fail)
If anyone wants, my wifes S3 hasn't been touched, so I can get any of the 4.1.2 rom files from it if its helpful to anyone. I did run across this but I haven't had time to try it yet, and I ran across another page where they modified the messenger.apk and changed some of the apn settings in there (definitely interested in looking into this).
Also to clarify, what I believe is happening here with the sim card is this, Verizon updated their RIL's to require a SIM (make sense since they use 4G), and if it doesn't find one it shuts down the radio in the phone, so until ST updates their RIL's, we will probably be stuck. It might be interesting to see if some could 'emulate' having a sim card in using a 3rd party app (its well beyond my programming capabilities I am afraid).
Sorry for my rambling, but I hope this has been helpful to someone, and I am hopeful that this will take off and let the ROOTING thread go back to helping people root . Please post any other SCH-968C findings you have here, maybe we can get a good collection of information in one place.
RiXtEr
@rixter13 so you're telling us that what we already suspected was true, we have figured out that the verizon device the roms are for requires a SIM so that's why we needed it also, we have suspected that the rom is trying to drive our device the same way it does the verizon, now, how do we remove the 4g function from the ROM so it bypasses needing the SIM or 4g function and just go straight for 3g as our phones normally would? or how do we mod the stock MMS apk so it plays nice with our 3g
also I consulted with motorhead at AA51 and explained what was happening with the roms on our device and he mentioned that the rils were gonna be a b****h, we've all been digging at this trying to get it surrounded, we've approached from every angle we can think of, its to the point that its gonna take some dev to fix
or call straight talk and get them to enter the APNs because they can't be entered manually on straight talk so we need a volunteer to call them and see if them doing the APNs will fix our issue, I have a feeling it won't because if the sim is required for the rom to work then even if the APNs are done by straight talk the SIM might mess that up because with the SIM in the system pulls the APNs from the SIM, so what is on the SIM might wipe out the APNs that straight talk enters from their end. I've stopped trying to think like the phone and started trying to think like the ROM, its gonna follow its programming unless we change the ROM, I no longer think the data tricks and edits are gonna work unless the ROM is cracked open and things for our phone spliced in and the verizon stuff taken out. Can this be done?
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
@rixter13 so you're telling us that what we already suspected was true, we have figured out that the verizon device the roms are for requires a SIM so that's why we needed it also, we have suspected that the rom is trying to drive our device the same way it does the verizon, now, how do we remove the 4g function from the ROM so it bypasses needing the SIM or 4g function and just go straight for 3g as our phones nornally would? or how do we mod the stock MMS apk so it plays nice with our 3g
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Well, unless StraightTalk (or someone else) comes out with android 4.4.4 rilblobs that don't force a SIM check we are stuck with the SIM card hack. The cm patches from 9/3/14 on are what caused our phones radio's to stop working properly.
As for the MMS issues, I haven't yet had the time to dig through the code to see what changed where (I am assuming I would be looking for a pre Unified commit 2/26 or around that time). I will try to tear apart that apk and look around in there for a smoking gun, but currently my PC is dead (lightening wiped out my motherboard) and I don't have any android tools on my wifes machine. So it may be a few days before I can get that done.
I will keep you posted on any progress (or lack thereof) on this, if anyone tries anything in this area (even if it doesn't work) I'd like to know about it so we don't waste more time running down the wrong path.
how about we have everybody pull logs, would that help?
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
how about we have everybody pull logs, would that help?
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
So the radio logs often have the IMEI number in them, so we need to be careful there posting them, I can pull logs from a VM I have on my work computer and compare them to my wifes 'virgin' ST S3.
rixter13 said:
Well, unless StraightTalk (or someone else) comes out with android 4.4.4 rilblobs that don't force a SIM check we are stuck with the SIM card hack. The cm patches from 9/3/14 on are what caused our phones radio's to stop working properly.
As for the MMS issues, I haven't yet had the time to dig through the code to see what changed where (I am assuming I would be looking for a pre Unified commit 2/26 or around that time). I will try to tear apart that apk and look around in there for a smoking gun, but currently my PC is dead (lightening wiped out my motherboard) and I don't have any android tools on my wifes machine. So it may be a few days before I can get that done.
I will keep you posted on any progress (or lack thereof) on this, if anyone tries anything in this area (even if it doesn't work) I'd like to know about it so we don't waste more time running down the wrong path.
Click to expand...
Click to collapse
so users with non SIM compatable devices are screwed, I've got 4.4.4 on my KFHD7 and my S2E4GT and neither one of them are SIM compatable so how do they run 4.4.4 without one?
wait! let me guess, those devices have an internal SIM?
so you're saying that even if we strip all the verizon stuff we'll still need the SIM for anything 4.4.4 and up?
there's even a 5.0 for the S2E4GT
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
so users with non SIM compatable devices are screwed, I've got 4.4.4 on my KFHD7 and my S2E4GT and neither one of them are SIM compatable so how do they run 4.4.4 without one?
wait! let me guess, those devices have an internal SIM?
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Not exactly, you are comparing separate things here. Are either of those verizon phones? Also do they have a 'unified' build? If you look above at some of the commits for the d2lte unified build that I posted earlier, the proprietary file list changed around that time, which is where things like the gps, radio, camera, and barometer (along with other hardware specific) 'drivers' come from. We can go back and branch off of the cm build from early September which still uses the 4.1.2 rils from ST, but we would also have to modify certain other things that have changed from that point on to get to where CM is today. There is quite a bit of work involved trying to maintain a separated branch from them, a LOT of roms are based on CM and then they put their 'tweaks' on top of that.
rixter13 said:
Not exactly, you are comparing separate things here. Are either of those verizon phones? Also do they have a 'unified' build? If you look above at some of the commits for the d2lte unified build that I posted earlier, the proprietary file list changed around that time, which is where things like the gps, radio, camera, and barometer (along with other hardware specific) 'drivers' come from. We can go back and branch off of the cm build from early September which still uses the 4.1.2 rils from ST, but we would also have to modify certain other things that have changed from that point on to get to where CM is today. There is quite a bit of work involved trying to maintain a separated branch from them, a LOT of roms are based on CM and then they put their 'tweaks' on top of that.
Click to expand...
Click to collapse
so you're saying this only applies to verizon and the unified d2lte builds? Gotcha
Sent from my SCH-S968C using Tapatalk
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
rixter13 said:
Not exactly, you are comparing separate things here. Are either of those verizon phones? Also do they have a 'unified' build? If you look above at some of the commits for the d2lte unified build that I posted earlier, the proprietary file list changed around that time, which is where things like the gps, radio, camera, and barometer (along with other hardware specific) 'drivers' come from. We can go back and branch off of the cm build from early September which still uses the 4.1.2 rils from ST, but we would also have to modify certain other things that have changed from that point on to get to where CM is today. There is quite a bit of work involved trying to maintain a separated branch from them, a LOT of roms are based on CM and then they put their 'tweaks' on top of that.
Click to expand...
Click to collapse
has anyone got anything from the ST S3 with 4.4? could we work with the ST 4.4 instead of the 4.1.2 to go off of? I think that model is the AT&T version instead of the verizon version of ST S3
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
so you're saying this only applies to verizon and the unified d2lte builds? Gotcha
Sent from my SCH-S968C using Tapatalk
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
has anyone got anything from the ST S3 with 4.4? could we work with the ST 4.4 instead of the 4.1.2 to go off of? I think that model is the AT&T version instead of the verizon version of ST S3
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
The good news (if there is such a thing) is we get a fresh start with Lollipop. It looks like the first efforts for the SIII was to DE-Unify the rom . The flipside of this coin is that the Lollipop builds are still buggy. Once I get my main machine back up and running, I may try to roll my own rom for the SCH968. I have compiled CM and Liquid roms, but never ventured out on my own yet.
N_psycho_PD_uh? said:
so you're saying this only applies to verizon and the unified d2lte builds? Gotcha
Sent from my SCH-S968C using Tapatalk
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
has anyone got anything from the ST S3 with 4.4? could we work with the ST 4.4 instead of the 4.1.2 to go off of? I think that model is the AT&T version instead of the verizon version of ST S3
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
So RIL stands for Radio Interface Layer (essentially the radio drivers), so even if you could get them for the AT&T, they don't help us since our phone uses Verizon towers. And as far as I know, they are closed source and carrier specific, which is what makes this an almost impossible feat.
rixter13 said:
So RIL stands for Radio Interface Layer (essentially the radio drivers), so even if you could get them for the AT&T, they don't help us since our phone uses Verizon towers. And as far as I know, they are closed source and carrier specific, which is what makes this an almost impossible feat.
Click to expand...
Click to collapse
its a good thing that anything is possible, the trick is HOW? I'm actually kind of enjoying the challenge with this phone, my other devices have been easy compared to this one, this things like a finicky @$$ cat that got rubbed the wrong way! I'm actually learning something from you guys on this one, I might just go get another pain in the @$$ device when we get this one beat, I know everyone has tried with the H2 device but I'd like to find an exploit to root it so we can get what is in the H2 because its not available, I thought about just pulling what I can from it before I downgrade to root, kinda why I've waited to root it, gotta be a way to root this one
Question, does anyone know what part of the H1 had the vulnerabilities and is there a way to take these parts out of H1 while leaving everything else and apply those parts to the H2 to give it the same vulnerabilities so that stock H2 can be rooted, I've been trying to track down every root method I can find, I've read about rooting devices with another rooted device but they both have to be OTG capable, I've also wondered if there's a way to use the s-beam feature on this device to root it since it is another way to push or pull data to and from it, I know nothing of these things though, I'm just a thinker, but I do wonder about that and if anyone has tried even if its only remotely possible its worth a shot but it would take someone that knows way more than I, I learn fast but I wouldn't know where to start with that.
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
its a good thing that anything is possible, the trick is HOW? I'm actually kind of enjoying the challenge with this phone, my other devices have been easy compared to this one, this things like a finicky @$$ cat that got rubbed the wrong way! I'm actually learning something from you guts on this one, I might just go get another pain in the @$$ device when we get this one beat, I know everyone has tried with the H2 device but I'd like to find an exploit to root it so we can get what is in the H2 because its not available, I thought about just pulling what I can from it before I downgrade to root, kinda why I've waited to root it, gotta be a way to root this one
Question, does anyone know what part of the H1 had the vulnerabilities and is there a way to take these parts out of H1 while leaving everything else and apply those parts to the H2 to give it the same vulnerabilities so that stock H2 can be rooted, I've been trying to track down every root method I can find, I've read about rooting devices with another rooted device but they both have to be OTG capable, I've also wondered if there's a way to use the s-beam feature on this device to root it since it is another way to push or pull data to and from it, I know nothing of these things though, I'm just a thinker, but I do wonder about that and if anyone has tried even if its only remotely possible its worth a shot but it would take someone that knows way more than I, I learn fast but I wouldn't know where to start with that.
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Chainfire could root the H2's. It'd be best to ask him.
heXacode said:
Chainfire could root the H2's. It'd be best to ask him.
Click to expand...
Click to collapse
how do I go about doing that? He's a complete stranger to me, I've used plenty of things that are his though
Sent from my SCH-S968C using Tapatalk
Speaking of the H2, what android version is on it?
N_psycho_PD_uh? said:
how do I go about doing that? He's a complete stranger to me, I've used plenty of things that are his though
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
You could find his profile here. Or G+. He will probably be extremely busy and probably has 100's of people talking to him.
rixter13 said:
Speaking of the H2, what android version is on it?
Click to expand...
Click to collapse
4.1.2.
As stated by Straight Talk they never push out new android versions. Whatever phone you get is gonna stay on that version for good.
heXacode said:
You could find his profile here. Or G+. He will probably be extremely busy and probably has 100's of people talking to him.
4.1.2.
As stated by Straight Talk they never push out new android versions. Whatever phone you get is gonna stay on that version for good.
Click to expand...
Click to collapse
yeah its 4.1.2 why?
the H1 and H2 are identical except for the patched kernel and the fact that H2 has two different versions itself, a qcom and a exynos
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
yeah its 4.1.2 why?
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
No explanation as to why. They just don't handle that kind of thing which sucks.
heXacode said:
You could find his profile here. Or G+. He will probably be extremely busy and probably has 100's of people talking to him.
4.1.2.
As stated by Straight Talk they never push out new android versions. Whatever phone you get is gonna stay on that version for good.
Click to expand...
Click to collapse
yeah I know, I'd rather try myself than bother him, he has bigger fish to fry than a prepaid ST, even if it is one of the better S3's (H2/qcom anyways)
Sent from my SCH-S968C using Tapatalk
---------- Post added at 10:37 PM ---------- Previous post was at 10:33 PM ----------
Im gonna like seeing what I can do with CM on 2Gb RAM with no bloat!
Sent from my SCH-S968C using Tapatalk
So to give an idea of what we need, here are the ST (older) rilblob files (ignore the dates listed below):
-rw-r--r-- 1 root root 3.7M Dec 3 19:46 libril-qc-qmi-1.so
-rw-r--r-- 1 root root 49K Dec 3 19:45 libril.so
and here are the new ones (VZW):
-rw-r--r-- 1 root root 2.5M Feb 28 2008 libsec-ril.so
-rw-r--r-- 1 root root 53K Feb 28 2008 libril.so
(the same files as the later ones are found on Lollipop as well)
I am looking into how to decompile a .so file at the moment.
rixter13 said:
So to give an idea of what we need, here are the ST (older) rilblob files (ignore the dates listed below):
-rw-r--r-- 1 root root 3.7M Dec 3 19:46 libril-qc-qmi-1.so
-rw-r--r-- 1 root root 49K Dec 3 19:45 libril.so
and here are the new ones (VZW):
-rw-r--r-- 1 root root 2.5M Feb 28 2008 libsec-ril.so
-rw-r--r-- 1 root root 53K Feb 28 2008 libril.so
(the same files as the later ones are found on Lollipop as well)
I am looking into how to decompile a .so file at the moment.
Click to expand...
Click to collapse
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.
Sent from my SCH-S968C using Tapatalk
---------- 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
Sent from my SCH-S968C using Tapatalk
Related
I have tried a few custom roms and then when I reflash back to any of the 3 stock roms floating out there for the GS3 Verizon my Google Play Store remains permanently broken. Alogcat indicates that it is getting back an unexpected response code 400 from google. I suspect this may mean that it fails to update because SSL is broken in some way but I could be wrong.
I have done all the normal things one does to bring back the market such as clearing the data on Google Play and services framework and rebooting, but that has no positive effect. Nor does deleting my account and re-adding it or creating a new account. Also Google+ will say "No Connection" but once I close out of it and reopen it, it will always log in to my account automatically without error. I will say that the error is reminiscent of the kind of error you would expect if your time is wrong, but it is correct. Any help will be appreciated it..
Go post in Q&A Forum.
iSheep... iSheep... Meowww that's Apple
This does not belong in development.
Sent from my Galaxy SIII
considering that out of all the roms I have tried Play now only works in one of the many roms posted here.. I feel like it is connected.
http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies build 20121005 is the only rom I can flash on my device now and having a working Google Play but I absolutely hate this rom. It has bugs, it lacks polish.. yet it also seems as if it screwed up Play in some way on my device... so please install this rom and tell me I should be posting somewhere else.. where everyone only discusses the usual methods of fixing Play and no one takes any real steps to really debug the problem to get to the root of it.
glitchbit said:
considering that out of all the roms I have tried Play now only works in one of the many roms posted here.. I feel like it is connected.
http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies build 20121005 is the only rom I can flash on my device now and having a working Google Play but I absolutely hate this rom. It has bugs, it lacks polish.. yet it also seems as if it screwed up Play in some way on my device... so please install this rom and tell me I should be posting somewhere else.. where everyone only discusses the usual methods of fixing Play and no one takes any real steps to really debug the problem to get to the root of it.
Click to expand...
Click to collapse
Doesn't matter if you have the issue on every rom it doesn't belong in the development section. Take the real step of posting this in the proper section.
Sent from my Galaxy SIII
I would have to agree seems like the good place to post it since we are all flashing roms and they bare having this issue... I was pleased to see this here as in have been having this issue on synergy 74 and up and now I see it's others so now all the developers will be aware of what's going on and maybe find a fix
Sent from my SCH-I535 using xda app-developers app
READ FORUM RULES BEFORE POSTING
Development is for Developers to post threads
Questions go in Q&A
Thread moved
Moderator
I love how people comment in a thread telling you that you posted in the wrong section, but don't offer up any advice.
I don't know a whole lot about your issue, but instead of flashing a stock rom maybe you could odin back to stock, accept OTA, and start over?
Not sure if that would clear up your issue, but hope I helped...!
josh995 said:
I love how people comment in a thread telling you that you posted in the wrong section, but don't offer up any advice.
I don't know a whole lot about your issue, but instead of flashing a stock rom maybe you could odin back to stock, accept OTA, and start over?
Not sure if that would clear up your issue, but hope I helped...!
Click to expand...
Click to collapse
Thanks Josh, but yea I have been flashing back to stock via Odin a lot, more times than I can count now! I've been using the HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5 image file but Kies says it is the most recent as well so there is no newer OTA to come down. I've also tried LG and HD roms via Odin, but regardless the Google Play Store remains broken. I am positive that I have restored everything back to its original configuration as per multiple guides on the subject. It is extremely frustrating as I have spent countless hours now trying to fix this one issue. I've spent more time researching this issue on google, in the forums and irc chat rooms and speaking with more devs than what those people would care to know about. There is a serious issue here that is being ignored.
I develop iPhone apps, I do IT support, and network infrastructure for a large manufacturer and I always get a great deal of enjoyment figuring things out but something like this, which should be so simple and just work, ticks me off to no end. For me this just creates the case in point why it makes it difficult for me to care much for the Android platform as a whole. It still has a lot of growing up to do before it catches up with iOS. I use a phone to get from point A to point B and I expect a certain baseline level of performance and things to just work. I left the platform 2 years ago and from the outside it looked as though things have been improving, but I can see now that not much has changed in the OS or community and the platform isn't ready for much of anything beyond a tablet for me personally as it is just a no go as a phone OS.
I would really like to figure this out still.. so to the first person who can give me the resolution or help me significantly in some way I will gift $50 to you over paypal.
Arriving at a solution
glitchbit said:
I would really like to figure this out still.. so to the first person who can give me the resolution or help me significantly in some way I will gift $50 to you over paypal.
Click to expand...
Click to collapse
Well, you don't seem to be flashing a Base ROM using Odin. It being broken like that usually indicates DPI issues, which are carrying across ROMs.
1. Is your phone encrypted? (Do a reset and Erase everything from within, that should fix it) Settings > Backup and Reset > Reset
2. Is the ROM you are flashing using Odin a Base FW?
I had this happen on an old incredible. What it turned out being was that my phone wasn't activated. I don't think that is your problem because it sounds like you use it, but could be a corrupted area of the phone that flashing doesn't touch. I don't think its a ROM because I've flashed them all and my market has always worked.
I would try a couple things to see if either helps. First, Odin back to stock then turn you phone off pull the sim card, boot back up and let it settle, power off put the sim back in and power up. Second, if that doesn't work dial *2767*3855# to repo vision your phone, but this factory resets and people say it erases your internal SD card so back that up. Hope one of those help.
Also if neither of those work, try a new sim card. That seems to fix 90% of peoples problems on this phone.
Sent from my S3 running Eclipse 2.1
kintwofan said:
I had this happen on an old incredible. What it turned out being was that my phone wasn't activated. I don't think that is your problem because it sounds like you use it, but could be a corrupted area of the phone that flashing doesn't touch. I don't think its a ROM because I've flashed them all and my market has always worked.
I would try a couple things to see if either helps. First, Odin back to stock then turn you phone off pull the sim card, boot back up and let it settle, power off put the sim back in and power up. Second, if that doesn't work dial *2767*3855# to repo vision your phone, but this factory resets and people say it erases your internal SD card so back that up. Hope one of those help.
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
kintwofan, you may be on to something. I have flashed the 3 base roms for my phone G7, LG, and HD to no avail. I actually use this phone on another carrier and so I have manually programmed this phone myself. So there may be something regarding the activation that is causing this issue.
glitchbit said:
kintwofan, you may be on to something. I have flashed the 3 base roms for my phone G7, LG, and HD to no avail. I actually use this phone on another carrier and so I have manually programmed this phone myself. So there may be something regarding the activation that is causing this issue.
Click to expand...
Click to collapse
Sounds like may need a buildprop change. Try changing buildprop to your carrier. Although one of my rezounds is on Tmobile without problems. Using T-mobile APN. S3 should auto add the APN. At least it does with international sim.
Use market enabler then to see if you can tell it your carrier. I'm sure you can Google the apk
You could also still do the reprovision, but I'm sure you'll have to reprogram it.
Sent from my S3 running Eclipse 2.1
Market enabler didn't work on synergy 74
Sent from my SCH-I535 using xda app-developers app
GREGHARKINS said:
Market enabler didn't work on synergy 74
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I assume you're on Verizon so did you try the other suggestion I posted? I used to run synergy with no problem so I would assume something got corrupted on your phone in a segment that isn't flashed.
Sent from my S3 running Eclipse 2.1
OTA attempts to activate this phone on the carrier fails, hence the manual programming. I have tried market enabler and and market unlock but they fail to work in the stock roms and the synergyrom. The only rom that has a working Market/Play is http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies I specifically used 1005 and 1012 and they both work fine.
I don't know what he does differently but it works for whatever reason.. http://forum.xda-developers.com/showthread.php?t=1788443
I just don't really care for the rom, it seems like my reception and wifi has issues on it vs the stock.
glitchbit said:
OTA attempts to activate this phone on the carrier fails, hence the manual programming. I have tried market enabler and and market unlock but they fail to work in the stock roms and the synergyrom. The only rom that has a working Market/Play is http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies I specifically used 1005 and 1012 and they both work fine.
I don't know what he does differently but it works for whatever reason.. http://forum.xda-developers.com/showthread.php?t=1788443
I just don't really care for the rom, it seems like my reception and wifi has issues on it vs the stock.
Click to expand...
Click to collapse
Interesting, so the reprovision didn't work? Have you tried just pulling the play store from his gapps? Also, you could try his jellywiz ROM maybe he did the same thing to it were your play works, if you like touchwiz. I guess you could also upload the build.prop from that working ROM and I'll compare it to mine when I get time and see if I notice any major differences.
By the way have you tried Eclipse ROM, its very nice and bug free.
Sent from my S3 running Eclipse 2.1
Still looks probably to be a buildprop vs carrier change issue. CM is built off source and works and the TW roms are built off different carrier bases and don't work. Playstore looks at the buildprop.
I am on my next to last day to exchange. Let me say that I love this phone except for the fact that AT&T has Carrier IQ installed and it can not be removed without rooting (at least on the 2 year contract one). There is a process to stop it and it's not that hard, except that it is a PITA to do it every time you reboot. If you forget to force stop, you are in the clutches of Carrier IQ. Also, I have doubts that even though it is stopped via a forced stop, that it is not residing somewhere else on the phone and still doing the nasties that it was designed to do. There is no sense in going over CIQ as there are a couple of threads already on the subject in reference to this phone and AT&T.
Unfortunately, I am stuck with AT&T and carrier swapping is not an option so the only option open to me right now is the phone.
So, is there a version of the LG G2 that is available for sale in the US that can be used on the AT&T network that does not have CIQ installed on it? Maybe the full sale priced one that AT&T sells? Or maybe a different one from Best Buy or someplace else? In a nut shell. Looking for a LG G2 that I can use on the US AT&T network that does not have CIQ installed.
I am new to this "smart phone" game but really am impressed with this phone and want to keep it, but in reality, unless I root it and void my warranty, this CIQ issue could be a killer for me. The reason is because I used to work at that big glass building at Fort Meade and know more than I want to about electronic data mining and collection. BTW, AT&T (both on line and store front), LG tech rep (store front), and LG (on line) all say that CIQ is not removable in the version that I have without rooting.
Any options that I am missing?
I don't think you have any other options friend. I'm also in a similar boat of having to return it tomorrow if I choose to do so. I think the full price one, or the one from best buy would be the same as they're all at&t branded so i'm sure they are all part of the exact same batch. There wouldn't be anything different between them.
I think I'm going to go ahead and root and disable it. There is no other phone that I think is this good, period.
Short answer, no. Long answer, your only option would be to buy the International or maybe Korean variants online and at full price and slap an AT&T SIM in it. I'm pretty sure you wouldn't get LTE though.
I get the feeling this is not what you want to do, so if CIQ bothers you that much and you're not willing to root you're going to have to return it.
You might want to consider waiting for the Nexus 5, which will likely share at least some hardware characteristics of the G2.
Sent from my LG G2 via Tapatalk
NevetsDrassel said:
Any options that I am missing?
Click to expand...
Click to collapse
Simple. Root. Easy and fixes the issue and more.
guys...its not that hard...just root it...install system tuner...disable 6 entries...done.
I have never rooted a phone. I do not know how or what is required. I am not computer illiterate so I think that this is something that I can do if I had instructions on how to do it. Where would I start to look for the process of rooting the phone?
What is required to do it?
Hate to loose the warranty on it but I guess that I can always return it to factory default (I think) if I had a problem in the future. I just like this phone too damned much to let it go.
NevetsDrassel said:
I have never rooted a phone. I do not know how or what is required. I am not computer illiterate so I think that this is something that I can do if I had instructions on how to do it. Where would I start to look for the process of rooting the phone?
What is required to do it?
Hate to loose the warranty on it but I guess that I can always return it to factory default (I think) if I had a problem in the future. I just like this phone too damned much to let it go.
Click to expand...
Click to collapse
Now we're on to something!
http://forum.xda-developers.com/showthread.php?t=2448887
You'll also want to read up on how to install and use ADB. There are some good guides out there that include videos.
The T-Mobile variant gives you the option of turning off CIQ. I was getting wakelocks from it, but since I've turned it off, it's been as quiet as a church mouse. Not sure if the radios are the same, I don't really know what AT&T uses.
Root it. And leave at&t as soon as it becomes an option because this won't be the last CIQ phone
Sent from my LG-D801 using XDA Premium 4 mobile app
Semantics said:
The T-Mobile variant gives you the option of turning off CIQ. I was getting wakelocks from it, but since I've turned it off, it's been as quiet as a church mouse. Not sure if the radios are the same, I don't really know what AT&T uses.
Click to expand...
Click to collapse
How do u turn it off?
Sent from my LG-D801 using xda app-developers app
bgaccord said:
How do u turn it off?
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
System settings, backup, collect diagnostics and uncheck the box.
Semantics said:
The T-Mobile variant gives you the option of turning off CIQ. I was getting wakelocks from it, but since I've turned it off, it's been as quiet as a church mouse. Not sure if the radios are the same, I don't really know what AT&T uses.
Click to expand...
Click to collapse
Would like to know this as well.
Dchibro said:
Now we're on to something!
http://forum.xda-developers.com/showthread.php?t=2448887
You'll also want to read up on how to install and use ADB. There are some good guides out there that include videos.
Click to expand...
Click to collapse
Well, I read the links. It looks pretty straight forward. Bit confused on some things. On the phone, I can go directly to the "Developers Options" under the main menu and turn that function on or off at will. Why all the hum drum about going into the About Phone menu to the Software Version to hit it 8 to 10 times to get the Developers Options turned on? Also while watching the video on how to root it, I got a bit confused on the "shift right click, open a command window" at 2:08. I do not have that capability. Different OS maybe? Anyways, I can always get a command window through the Start Run menu.
If I root the phone, I know that I can restore it to it original stock based on the first sticky in this forum. However, someone indicated that even if you return it to stock, there will be indications that it was rooted. But I could not tell what version of the phone that he was referencing.
Do I/Should I back up anything first before I start? Not that much on the phone right now, just my Contacts, a couple of pictures, and some apps that I downloaded. Home screen setups and things like that.
m3lover1 said:
Would like to know this as well.
Click to expand...
Click to collapse
See the post above yours.
---------- Post added at 11:01 PM ---------- Previous post was at 10:59 PM ----------
NevetsDrassel said:
Well, I read the links. It looks pretty straight forward. Bit confused on some things. On the phone, I can go directly to the "Developers Options" under the main menu and turn that function on or off at will. Why all the hum drum about going into the About Phone menu to the Software Version to hit it 8 to 10 times to get the Developers Options turned on? Also while watching the video on how to root it, I got a bit confused on the "shift right click, open a command window" at 2:08. I do not have that capability. Different OS maybe? Anyways, I can always get a command window through the Start Run menu.
If I root the phone, I know that I can restore it to it original stock based on the first sticky in this forum. However, someone indicated that even if you return it to stock, there will be indications that it was rooted. But I could not tell what version of the phone that he was referencing.
Do I/Should I back up anything first before I start? Not that much on the phone right now, just my Contacts, a couple of pictures, and some apps that I downloaded. Home screen setups and things like that.
Click to expand...
Click to collapse
Apparntly the VZW variant shows the phone as rooted in about phone. I went through every single menu on the T-Mobile variant and I see nothing to reference that I have rooted my phone.
Oh that was it? I had that turned off when I set up the phone. Lol Thanks
Ok, so once its rooted, what do I do? Where do I delete the files to get rid of carrier iq?
Custom rom; no carrieriq. Besides didn't they change it so it's not that big a deal anymore?
Semantics said:
System settings, backup, collect diagnostics and uncheck the box.
Click to expand...
Click to collapse
This is absolutely not listed in the Verizon version. Pretty sure the VS980 has CIQ too.
Sneaky punks... :/
Or just flash a custom stock rom that is debloated and has modded options preinstalled.
Sent from my VS980 4G using XDA Premium 4 mobile app
Semantics said:
See the post above yours.
---------- Post added at 11:01 PM ---------- Previous post was at 10:59 PM ----------
Apparntly the VZW variant shows the phone as rooted in about phone. I went through every single menu on the T-Mobile variant and I see nothing to reference that I have rooted my phone.
Click to expand...
Click to collapse
You might want to double check the T-Mobile app. Under device health it says I'd the phone is rooted.
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
UPDATE 3/6/14
I installed a snapshot of CM 11 (KitKat) onto my device with little issues. I'll update this guide with the links to that firmware, and also update the existing links because of changes CyanogenMod made to how they aggregate their S4 devices now. They are treating them all as derivatives of 'jftle', so basically one firmware fits all devices, including the i9507! (even if not official yet).
Please read the bottom of this post if you wish to install KitKat on your device.
CUSTOM FIRMWARE ON SAMSUNG GALAXY S4 i9507 - Aus/HK
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
If you're looking to root this device, I found that by treating it essentially as an international i9505 I was able to fulfil all three of the things I mentioned above.
UPDATE: THIS WILL VOID YOUR WARRANTY AND RESULT IN 'KNOX WARRANTY VOID 0x1' BEING DISPLAYED WHEN YOU ENTER DOWNLOAD MODE ON THE DEVICE. PLEASE BE SURE YOU ARE OKAY WITH THIS HAPPENING BEFORE TRYING THIS FOR YOURSELF. AS IT STANDS, KNOX CANNOT BE RESET, IT IS AT A HARDWARE LEVEL.
[ROOT i9507]
Using Chainfire's guide to CF-Auto-Root in the Galaxy S 4 i9505 Original Android Development section of this forum; I was able to root my device despite it being an i9507. Being a new user, I wasn't sure exactly what things to test out whether the root worked/was permanent, but I did install AdBlock Plus and it asked me for Superuser privileges, then proceeded to work. I also restarted the device and tested whether the root was still present; it was.
[INSTALL CLOCKWORKMOD]
I decided to install CyanogenMod as I have heard from friends that have it; and read online about it being one of the more stable custom ROMs available. It has been a while since I last owned an Android device! So, continuing with my theme of treating this device as being an international i9505, I obtained CM 10.2.0, a stable release of the jfltexx CM, based on from their website (as of December 2013, this was the most recent). Their custom installer app on Windows did not support my phone, so I had to use their guide for manual installation.
Their guide contained steps to installing ClockworkMod Recovery as well as the ROM installation. Following the guide, I installed it without a hitch. When rebooting the phone from ClockworkMod, it prompted me about the fact that the phone may reflash its own recovery tool, but this did not happen. Once again, a success.
[INSTALL CYANOGENMOD]
The last task was to install CM. This was quite an endeavour as I decided to use someone else's Windows 8 laptop (being the only Windows device I had access to at the time) and I forgot how much of a struggle it can be! Again, I used CM's guide to installing 10.2.0 (which by the way is Android 4.3.1, whereas the stock firmware is bloated and heavy at 4.2.2). This went off without a hitch once I reminded myself how the ADT works. I also did as CM suggested and installed the Google Apps pack alongside the ROM.
So, currently this is where I'm at. The device boots and reboots fine. Some users in certain threads had issues with loading 4.4 (KitKat) ROMs or custom ROMs that they didn't allude to the names of, so I don't know if they were having issues with CM or not. There are other threads, but that was the one that kickstarted my attempts to get this all to work. Their issues with the custom ROMs seemed to be related to the 4.4 ROM not recognising the modem of the i9507; I'm not sure why this is but the i9507 was made specifically for Australian/Hong Kong networks so perhaps 4.4 has not been updated yet or something of the like. Anyway, on 4.3.1, or CM 10.2.0, my SMS, calling, and internet are working fine (it displays Virgin Mobile as my carrier). My 4G reception is somewhat iffy in this town (or in particular my house), and the reception seems to be switching between 3G and H so whether that is indicative of 4G not working, I'm not sure. LTE is definitely checked in the settings, however, and my area does have 4G, but my parents' iPhone 5Ss sometimes do not have 4G in this house either. I'll report back tomorrow after having tested the phone for a day to see if the 4G does activate.
As it stands, however, the phone seems to be functioning well. Oddly the Settings report that the phone is an i9505, I assume that's normal as I'm using a ROM for that particular phone!
[CONCLUSION]
So, I hope that anyone who has been looking for a way to remove the carrier/Samsung bloat from their i9507 device will have a good time using the guides I've used. I followed them to the letter and I had no issues.
DISCLAIMER: I had no troubles, but that's not to say you won't either. Please be careful, as you may potentially risk affecting your phone negatively. I'm simply telling you what I did, not giving you a 100% correct and flawless guide that will work no matter what.
Also if you're looking for a 4.4 ROM then you might be out of luck, least till some dev or coder takes notice of this device's existence and helps out to develop a specific way of rooting this phone/installing custom ROMs for this phone. Overall though, it seems to all work fine so perhaps the 4.3.1 CM isn't such a bad thing.
If you try this and want the original firmware back on your phone, use this link. I believe that OPS is the Australian firmware, the other one is for Hong Kong. So, for the second link, HK is Hong Kong, and the one without is for Aus.
UPDATE 3/6/14
I've successfully managed to install a Nightly build of CM 11, based on KitKat. Read my latest post in this forum for more info. I essentially found that upgrading from within the phone itself caused a number of issues so I did a fresh flash. Please note that such a flash of a new OS wipes all personal data but not things like images, videos, etc. I lost all my contacts, SMS, browsing history, apps etc. But my Gallery, Downloads folder, etc remained intact.
I followed my guide to flashing the phone again, but I used a Nightly build of CM 11, based on KitKat. As I write this, there are actually stable versions of CM that you can use in place of the CM 10.2.0 I used in the above guide. If you follow those steps but use this firmware you'll find no issue. Feel free to use CM's guide, but don't, under any circumstances, forget to flash Google Apps to your phone!!!
If you need a hand or want a question answered, feel free to post here and I'll do my best to help you out. Thanks!
kaiserwatson said:
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
If you're looking to root this device, I found that by treating it essentially as an international i9505 I was able to fulfill all three of the things I mentioned above.
[ROOT i9507]
Using Chainfire's guide to CF-Auto-Root in the Galaxy S 4 i9505 Original Android Development section of this forum; I was able to root my device despite it being an i9507. Being a new user, I wasn't sure exactly what things to test out whether the root worked/was permanent, but I did install AdBlock Plus and it asked me for Superuser privileges, then proceeded to work. I also restarted the device and tested whether the root was still present; it was.
[INSTALL CLOCKWORKMOD]
I decided to install CyanogenMod as I have heard from friends that have it; and read online about it being one of the more stable custom ROMs available. It has been a while since I last owned an Android device! So, continuing with my theme of treating this device as being an international i9505, I obtained the latest stable release of the jfltexx CM from their website (it was the most recent stable release at the time, may be out of date by the time you get to doing this yourself). Their custom installer app on Windows did not support my phone, so I had to use their guide for manual installation.
Their guide contained steps to installing ClockworkMod Recovery as well as the ROM installation. Following the guide, I installed it without a hitch. When rebooting the phone from ClockworkMod, it prompted me about the fact that the phone may reflash its own recovery tool, but this did not happen. Once again, a success.
[INSTALL CYANOGENMOD]
The last task was to install CM. This was quite an endeavour as I decided to use someone else's Windows 8 laptop (being the only Windows device I had access to at the time) and I forgot how much of a struggle it can be! Again, I used CM's guide to installing 10.2.0 (which by the way is Android 4.3.1, whereas the stock firmware is bloated and heavy at 4.2.2). This went off without a hitch once I reminded myself how the ADT works. I also did as CM suggested and installed the Google Apps pack alongside the ROM.
So, currently this is where I'm at. The device boots and reboots fine. Some users in certain threads had issues with loading 4.4 (KitKat) ROMs or custom ROMs that they didn't allude to the names of, so I don't know if they were having issues with CM or not. There are other threads, but that was the one that kickstarted my attempts to get this all to work. Their issues with the custom ROMs seemed to be related to the 4.4 ROM not recognising the modem of the i9507; I'm not sure why this is but the i9507 was made specifically for Australian/Hong Kong networks so perhaps 4.4 has not been updated yet or something of the like. Anyway, on 4.3.1, or CM 10.2.0, my SMS, calling, and internet are working fine (it displays Virgin Mobile as my carrier). My 4G reception is somewhat iffy in this town (or in particular my house), and the reception seems to be switching between 3G and H so whether that is indicative of 4G not working, I'm not sure. LTE is definitely checked in the settings, however, and my area does have 4G, but my parents' iPhone 5Ss sometimes do not have 4G in this house either. I'll report back tomorrow after having tested the phone for a day to see if the 4G does activate.
As it stands, however, the phone seems to be functioning well. Oddly the Settings report that the phone is an i9505, I assume that's normal as I'm using a ROM for that particular phone!
[CONCLUSION]
So, I hope that anyone who has been looking for a way to remove the carrier/Samsung bloat from their i9507 device will have a good time using the guides I've used. I followed them to the letter and I had no issues.
DISCLAIMER: I had no troubles, but that's not to say you won't either. Please be careful, as you may potentially risk affecting your phone negatively. I'm simply telling you what I did, not giving you a 100% correct and flawless guide that will work no matter what.
Also if you're looking for a 4.4 ROM then you might be out of luck, least till some dev or coder takes notice of this device's existence and helps out to develop a specific way of rooting this phone/installing custom ROMs for this phone. Overall though, it seems to all work fine so perhaps the 4.3.1 CM isn't such a bad thing.
If you try this and want the original firmware back on your phone, use this link or this one. I believe that OPS is the Australian firmware, the other one is for Hong Kong. So, for the second link, HK is Hong Kong, and the one without is for Aus.
If you have any questions, please feel free to ask. I'll post later tomorrow when I've tested the phone for a day to see if it's still working, and to see if the 4G/LTE does actually work. Fingers crossed nothing goes wrong in the meantime!
Click to expand...
Click to collapse
I've had my i-9507 rooted for about a month now with foxhound rom, also on the optus variant.
One thing i've noted is, its next to impossible to update the MODEM for it.
I think because our latest modem for this variant is the one we have stock. And new updates haven't been put in terms of modem specifically for our variant yet.
We should keep this thread stickied for Australian OPTUS GT-i9507 discussion.
OR open up a sub forum for it.
kaiserwatson said:
I'll post later tomorrow when I've tested the phone for a day to see if it's still working, and to see if the 4G/LTE does actually work. Fingers crossed nothing goes wrong in the meantime!
Click to expand...
Click to collapse
Firstly, thank you for creating this complete description of your experiences with customising the i9507.
Secondly, just wanted confirmation that you do now have the pesky "KNOX WARRANTY VOID: 0x1" displayed when your device is in Download mode, right?
Lastly, any updates, issues? All still working, including 4G/LTE?
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
I do have the Knox 0x1, which I assume means my warranty is void. There's conjecture as to whether that will actually affect warranty for this device in Australia, as I've read up on the Knox system but i think the ACCC would have serious issues with this system actually affecting the warranty. But yes, it would seem my warranty is void, let's hope the phone lasts two years!
I have been able to access 4G, the phone says 4G or LTE, sometimes switching between the two. Again, the reception in the town I'm currently staying in is pisspoor so I can't say for certain whether the antenna/modem is fully functioning to the degree it would be on the stock firmware, but I can definitely access the Optus 4G network.
One issue I did have was that I sent an SMS then immediately turned my screen off, 40 minutes later the message was still 'sending'. I have recreated the same scenario but I haven't been able to get it to happen again, perhaps just a weird tower-side quirk. I know people were having issues with the modem and the phone sleeping but this doesn't seem to be related. Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
kaiserwatson said:
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
I do have the Knox 0x1, which I assume means my warranty is void. There's conjecture as to whether that will actually affect warranty for this device in Australia, as I've read up on the Knox system but i think the ACCC would have serious issues with this system actually affecting the warranty. But yes, it would seem my warranty is void, let's hope the phone lasts two years!
I have been able to access 4G, the phone says 4G or LTE, sometimes switching between the two. Again, the reception in the town I'm currently staying in is pisspoor so I can't say for certain whether the antenna/modem is fully functioning to the degree it would be on the stock firmware, but I can definitely access the Optus 4G network.
One issue I did have was that I sent an SMS then immediately turned my screen off, 40 minutes later the message was still 'sending'. I have recreated the same scenario but I haven't been able to get it to happen again, perhaps just a weird tower-side quirk. I know people were having issues with the modem and the phone sleeping but this doesn't seem to be related. Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
Click to expand...
Click to collapse
That occurs because the modem signal cuts out after you switch your phone off, or lock it.
This issue can be resolved by updating our modems, but with our current variant we can't update it yet apparently, until the correct new modem for our specific variant has been released.
Hi guys,
I thought I would also post here.
I have the optus 9507 and I tried a couple of different kitkat 4.4 roms. They all worked perfectly except for the fact that they lost data completely as soon as the phone went to sleep. the weird thing is, the phone showed 0 bars but i could take calls just fine, just had data issues.
i tried the slimkat rom and the echoe rom with the same issue
i went back to stock firmware, rooted, ran a debloat script i found on xda, removed a bunch more apps, then unrooted again because i need to run good for enterprise for work.
im getting decent battery life with the debloated stock rom but i would like to move to 4.4 if theres a rom that works. ive been watching the optus and sammobile site hoping there will be a newer modem for the hk version because i think optus will take their time releasing 4.3 for this model.
kaiserwatson said:
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
......
Click to expand...
Click to collapse
Thanks for your experience sharing,
I also started with Cyanogen and shared about the same experience.
Just didn't know the Knox thing before I started.. should had read up more before doing it.
So you did the Recovery with Heimdall also? What has made you switch to the customized Rom camp
kaiserwatson said:
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
Click to expand...
Click to collapse
Hey, no worries at all, anyone who works weekends can take all the time they need...
But yes, it would seem my warranty is void, let's hope the phone lasts two years!
Click to expand...
Click to collapse
Yea, I've done some reading also and you're right, it seems to be all conjecture, I really doubt handset warranty refusal can be based on the KNOX Warranty chip. I think the Samsung Enterprise Security Group VP explains it well here.
Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
Click to expand...
Click to collapse
Great to hear, based on this I can ge ahead and 'burn out' my eFuse, happy in the knowledge that my Knox warranty has gone to a good cause. :fingers-crossed:
---------- Post added at 08:49 PM ---------- Previous post was at 08:40 PM ----------
opelcalibra said:
then unrooted again because i need to run good for enterprise for work.
Click to expand...
Click to collapse
I can only assume your "enterprise for work" has nothing to do with KNOX, right? Coz that option would be closed for you now...
CuriosityBrah said:
That occurs because the modem signal cuts out after you switch your phone off, or lock it.
This issue can be resolved by updating our modems, but with our current variant we can't update it yet apparently, until the correct new modem for our specific variant has been released.
Click to expand...
Click to collapse
That odd message not sending was the only issue I've had with this sort of thing; I can still download things, receive messages and calls just fine while my phone is sleeping, how do you know if the modem signal is cutting off? Perhaps it's just a selective thing, not sure. Don't know how to test if it's happening to me because it doesn't seem to be, lol.
opelcalibra said:
I have the optus 9507 and I tried a couple of different kitkat 4.4 roms. They all worked perfectly except for the fact that they lost data completely as soon as the phone went to sleep. the weird thing is, the phone showed 0 bars but i could take calls just fine, just had data issues.
Click to expand...
Click to collapse
Hey mate if you check the forum that I linked to the Knox issue; someone on there posted a fix for sound/WiFi issues post-Knox voiding, maybe that fix'll work for you. Sorry I can't link you to the exact post but it was about 10-20 pages in.
opelcalibra said:
i went back to stock firmware, rooted, ran a debloat script i found on xda, removed a bunch more apps, then unrooted again because i need to run good for enterprise for work.
im getting decent battery life with the debloated stock rom but i would like to move to 4.4 if theres a rom that works. ive been watching the optus and sammobile site hoping there will be a newer modem for the hk version because i think optus will take their time releasing 4.3 for this model.
Click to expand...
Click to collapse
Yeah I reckon they'll take ages, they have pretty much left everyone who's getting this phone in the next couple of months in the dark because of the (as I can tell) severe lack of devs etc in Aus who have Samsung phones and are willing to hack them to the ****. I wish I could help out somehow, but I don't have the time to learn so I figured I'd help out by putting up my experiences. I'm still learning as I go haha.
As for your KitKat problem, I have read that 4.4 didn't do so well in terms of battery life and bloat, what are your reasons for wanting to go to it? I wanted the most recent build also but I figured that if they're still having issues with it then it was better to go with something I knew would work (ie. 4.3.1).
phileasx said:
Thanks for your experience sharing,
I also started with Cyanogen and shared about the same experience.
Just didn't know the Knox thing before I started.. should had read up more before doing it.
So you did the Recovery with Heimdall also? What has made you switch to the customized Rom camp
Click to expand...
Click to collapse
I followed the Windows process on the CM wiki to the letter, so yeah I did the Heimdall also.
Mate legitimately I went from my stock firmware taking up so much space on the hard drive to the real lightweight CM, seeing as I haven't bought a micro SD yet that was a big deal. Also battery life was a major reason for me buying the S4 so to be able to further improve it is just hella.
siganid said:
Hey, no worries at all, anyone who works weekends can take all the time they need...
Yea, I've done some reading also and you're right, it seems to be all conjecture, I really doubt handset warranty refusal can be based on the KNOX Warranty chip. I think the Samsung Enterprise Security Group VP explains it well.Great to hear, based on this I can ge ahead and 'burn out' my eFuse, happy in the knowledge that my Knox warranty has gone to a good cause. :fingers-crossed:
Click to expand...
Click to collapse
In Australia I think we're pretty good. Funny that Samsung and Optus have given us this nice present and it's only a matter of time before someone cracks it open and remains above the warranty voiding
I have read that Knox may be software-based, which would make sense, and maybe it's a matter of time before someone cracks that too. Hehe.
Go ahead, post here if you have any issues and I'll see if I can help you out. What ROM would you be planning on using? A 4.3.x one?
kaiserwatson said:
I followed the Windows process on the CM wiki to the letter, so yeah I did the Heimdall also.
Mate legitimately I went from my stock firmware taking up so much space on the hard drive to the real lightweight CM, seeing as I haven't bought a micro SD yet that was a big deal. Also battery life was a major reason for me buying the S4 so to be able to further improve it is just hella.
Click to expand...
Click to collapse
Welcome to the rom flashing side
After read up more, I realize Odin is a more popular method for Galaxy S4 flashing,
Besides that, Stock rom battery life should also be all right. Samsung did quite some efforts to make the software user friendly.
Anyway, the Bloatware chunk are really irritating have to say.
because i cant keep still i have flashed my phone again lol.
i flashed the official CM 11 (4.4.2) and gapps for kitkat and all is working awesome so far.
no issues with losing signal when going to sleep. seems very fast. right now im happy with it.
Could someone please find new links for the original software posted in the OP?
Links are dead, would be greatly appreciated! =)
Also, Opelcalibra, you have no issues with network/signal on CM 4.4.2 with the Optus i9507?
I better give it a try then lol
RE: Signal issues
Hi,
I also have the AU i9507 Opus S4, I flashed the Omega based 4.4.2 KitKat (i9505 version) and had wifi problems (Greyed out) I tried various fixes and went back to 4.3 based Omega, this had its problems with cell signal being lost when locking the mobile.
I fixed this by going into settings and experimented with mobile networks i.e. Settings, more networks, mobile networks, network mode and tried all 4x options with (for me at least) the GSM ONLY option selected, great rom and worth losing the 4g which is very patchy in my part of Melbourne.
D
Anyone else had any sort of success rooting this phone without tripping Knox.
Also, is it just me, or does it suck pretty hard that we Aussies get stuck with an inferior version of a phone? (Snapdragon 600 in the I9507 vs the 800 in the other international versions)
Update
Hi
Just wondering if anyone has an update on this? Success or otherwise...
One of the main reasons I'm looking to root is to boost volume levels - I find the volume to be way too low. Does anyone know of a way to do that without rooting? Of course I'd like to remove bloatware but could live with it if volume was fixed.
Thanks in advance.
thestuntman80 said:
Anyone else had any sort of success rooting this phone without tripping Knox.
Also, is it just me, or does it suck pretty hard that we Aussies get stuck with an inferior version of a phone? (Snapdragon 600 in the I9507 vs the 800 in the other international versions)
Click to expand...
Click to collapse
Hey bro, no one has cracked without tripping Knox yet because as far as I can tell it's a phone specific fix/hack. So, because our phone is a different and 'rare' model, I doubt that the major heads in the Knox-proofing scene (CF comes to mind) will have the time to make a fix for the knox trip. So for now, either suffer in your jocks (QQ) get a different phone (uh, not likely) or wait for the minute chance that someone actually cares about Aussies )
As for your second point, yeah, it does suck. We get shafted with all sorts of things like prices, release dates, localization...the list goes on. Unfortunately the people who make these ploys know we're desparate and will pay the exorbitant prices anyway :/
jameshef said:
Hi
Just wondering if anyone has an update on this? Success or otherwise...
One of the main reasons I'm looking to root is to boost volume levels - I find the volume to be way too low. Does anyone know of a way to do that without rooting? Of course I'd like to remove bloatware but could live with it if volume was fixed.
Thanks in advance.
Click to expand...
Click to collapse
Hey mate, the rooting was probably the easiest part of the whole situation. You can follow my guide in the OP if you're having trouble. Just be aware about the warranty issues etc because your audio issue may be hardware related rather than software? Is the volume issue in the headphones or the speaker? Some apps may not utilise the phones full volume and also be sure to go into the settings of the phone and make sure the volume limiter is turned OFF. This **** me to tears for the longest time but once I figured out what the issue was, all good!
The only thing I'd say is just make sure its not a hardware issue because you don't want to root your phone, find out that it wasn't a software issue, take your phone into Samsung and have them tell you that your warranty is voided because you rooted. Obviously that's a worse case scenario but just be on the safe side.
I hope I helped you guys!
kaiserwatson said:
Hey mate, the rooting was probably the easiest part of the whole situation. You can follow my guide in the OP if you're having trouble. Just be aware about the warranty issues etc because your audio issue may be hardware related rather than software? Is the volume issue in the headphones or the speaker? Some apps may not utilise the phones full volume and also be sure to go into the settings of the phone and make sure the volume limiter is turned OFF. This **** me to tears for the longest time but once I figured out what the issue was, all good!
The only thing I'd say is just make sure its not a hardware issue because you don't want to root your phone, find out that it wasn't a software issue, take your phone into Samsung and have them tell you that your warranty is voided because you rooted. Obviously that's a worse case scenario but just be on the safe side.
I hope I helped you guys!
Click to expand...
Click to collapse
I'm fairly certain it's a software issue. I've done a fair bit of reading on it and the low volume is a very common complaint about the S4. My volute limiter is turned off - thanks for that tip though!
I'm going to try to root this weekend. I really hope that it works and I don't have any issues with reception dropping when the phone goes to sleep! Feels risky.
I've changed my firmware from Optus to XSA, but am still on 4.2.2, how do I upgrade now?
Kies says I have the latest release.
has anyone got links to newer modem files for this phone? been given one to update it to 4.4, but i know from experience that doing so without at least a 4.4 GSM modem, it wont behave right.
to the people without working wifi after updating: flash the Ktoonz kernel, he has a fix for that.
Hi All,
I recently updated to the new official 4.3 update from optus in order to update my baseband etc.
Then i immediately updated to the i9505 Goldeneye 4.4.2 rom. Ran a ebloat script to get rid of alot of the extras and its running very nicely.
Since updating the modem I get 4g at home which i never did before.
optus rom here
http://www.sammobile.com/firmwares/3/?download=27109
flashed via odin (will lose root and custom recovery). re-root and install recovery after flashing this room.
goldeneye rom here
http://forum.xda-developers.com/showthread.php?t=2313469
obviously this will flag knox, mine was flagged long ao
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
Because you can't. Once you take the 4.3 OTA, you're stuck with it.
McDastardly said:
Because you can't. Once you take the 4.3 OTA, you're stuck with it.
Click to expand...
Click to collapse
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
But coming back to the issue at hand: lets imagine I was lucky enough not to trust Samsung to deliver me an update and instead took a hacked one. Is there any reason whatsoever to stay on 4.3? And by that I mean:
- does 4.3 solve some problem in original firmware, that anyone should care about?
- does 4.3 implement some new feature, which was not in original 4.1 firmware that I should be excited about?
galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
What features were taken out? Anything that can be replaced with better apps on the market shouldnt count. In my opinion the new stock task manager makes it worth it.
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
Well if I could go back in time I would have just waited for a custom 4.3 tw rom. But at least I don't feel the need to flash a new rom every day now.
ThePagel said:
What features were taken out?
Click to expand...
Click to collapse
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)
galets said:
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)
Click to expand...
Click to collapse
I can understand your annoyance with the hidden menu being gone. But that wasn't a "feature" it was a "hidden menu" after all and with root there are ways to get rid of the volume warning. That bugs the crap out of me as well but not to the point to change it yet.... YET!
galets said:
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
Click to expand...
Click to collapse
Nah, Samsung hasn't been overwhelmingly developer friendly for awhile. There's a bit of dislike for them due to Exynos processors.
Additionally, it wasn't that sneaky. The phone was intended to have a locked bootloader from the beginning. It was expected that the update would patch the loophole we found from the leaked aboot step. That's why it was mentioned multiple times to not accept the 4.3 update in case it locked the bootloader.
Samsung hasn't been developer friendly for a long time. Anytime you take an OTA update you can expect it to prevent the use of custom firmware unless a trusted source says it doesn't.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Additionally, it wasn't that sneaky. The phone was intended to have a locked bootloader from the beginning. It was expected that the update would patch the loophole we found from the leaked aboot step.
Click to expand...
Click to collapse
I still maintain it's been sneaky. The boot loader was not patched for a long time, you even get an icon which indicates custom firmware. Many folks understood it as if Samsung quietly endorses modding. The S3 has had a reputation of phone friendly for modders. Many purchased this very model specifically because they intended to mod it. Also don't forget, people look up to tinkerers, so a lot of sales were made because "this guy who knows the phones has samsung"
galets said:
I still maintain it's been sneaky. The boot loader was not patched for a long time, you even get an icon which indicates custom firmware. Many folks understood it as if Samsung quietly endorses modding. The S3 has had a reputation of phone friendly for modders. Many purchased this very model specifically because they intended to mod it. Also don't forget, people look up to tinkerers, so a lot of sales were made because "this guy who knows the phones has samsung"
Click to expand...
Click to collapse
Samsung isn't as nice as you think. HTC will often allow you to unlock the phone by signing an agreement that you are voiding the warranty. Verizon has had a history of locking bootloaders that other carriers wouldn't.
This bootloader lock is mostly Verizon's implementation anyway. They're the ones who changed the bootloader and patched our loophole. Other devices on the 4.3 OTA update (sprint and T-Mobile) still have unlocked bootloaders.
The custom icon was only stating we had a custom recovery installed. Didn't have anything to do with firmware checking.
Sent from my SCH-I535 using Tapatalk 2
It's hard to call it sneaky if you look back at the thread that was all about waiting for the update it was repeated daily, if not a couple of times a day that if the OTA hits your phone not to take it because it would lock your bootloader. Taking my early upgrade from the Bionic this didn't really surprise me lol. It just clinched it that, I'll maintain my unlocked bootloader and rom away until its time for my next phone, which will be a nexus or amazingly enough a moto if i can let go of my bionic anger lol....
If you purchase a phone to be modded, after you mod it, why would you ever take a manufacturer OTA?
Sent from my SCH-I535 using xda app-developers app
galets said:
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
But coming back to the issue at hand: lets imagine I was lucky enough not to trust Samsung to deliver me an update and instead took a hacked one. Is there any reason whatsoever to stay on 4.3? And by that I mean:
- does 4.3 solve some problem in original firmware, that anyone should care about?
- does 4.3 implement some new feature, which was not in original 4.1 firmware that I should be excited about?
Click to expand...
Click to collapse
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang
XdrummerXboy said:
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
Its samsung. Every version of the s3 is locked on 4.3 the only difference is nobody is complaining about it on the other forums. samsung wants to be able to have there phones used in government agencies and the like so they locked the phone down. I accidentally upgraded and haven't complained once because its not that big of a deal. I am just not buying from samsung from now on (unless they make the tablet that folds into a phone). Someone can correct me if I am wrong but everything I have read says every s3 on 4.3 has been locked down. If you do say I am wrong please give me a link so I can educate myself.
XdrummerXboy said:
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
Ahhh I forgot about the Knox or whatever they call it. I thought you were able to switch between using it and not though.
But I guess maybe they have to make sure EVERYTHING is secure, then build the "non" secure stuff on top of that framework.
SGS3 running Android 4.4 KitKang
XdrummerXboy said:
Ahhh I forgot about the Knox or whatever they call it. I thought you were able to switch between using it and not though.
But I guess maybe they have to make sure EVERYTHING is secure, then build the "non" secure stuff on top of that framework.
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
You can still root the OTA by using saferoot. Once rooted, superSU will ask if you want to disable knox. You can then load safestrap which will allow you to load other 4.3 roms and multi-boot your phone etc. Read ALL the threads on saferoot and safestrap before you install them.
Sent from my SCH-I535 using xda app-developers app
galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
App access to notifications. That is my killer app for 4.3
Is anyone still supporting new ROMs? I never rooted because I have been using Samsung Pay but am over it. Looking to Root and have some fun but it looks like this phone is pretty much no longer supported.
1st phone I have ever not rooted and it's silly how much I miss it.
Yeah, phone is mostly dead. And if you are still on Sprint network there aren't many ROMs to try. I've unlocked my phone to use it on Mexico's largest carrier, I could share my personal ROM but I'm sure it won't work with the Sprint network.
I just got my Note 5 Sprint phone a few weeks back (our company got a really good deal but it meant older phones). Being someone who just can't use an unrooted phone (a neurosis?) I looked around and decided to try the Teleteam CDMA S8 rom. (The S8+ doesn't offer wifi calling). I'm quite glad I did root, in part because the rom is nice and in part because I *hate* face book app and a few others and like being able to remove them totally. My two cents... do it!
---------- Post added at 10:39 AM ---------- Previous post was at 10:27 AM ----------
Trying again to post... xda is being a bit difficult today.
I got my Note 5 Sprint in the past few weeks due to my company getting a nice deal, the weak end being we got older phones. So... being a serious rooter, I found the Teleteam Rom and used the CDMA S8 version. It works great and allows wifi calling. Go for it. You won't be sorry.
What is your thought regarding security patches? That Rom hasn't been updated in like a year, correct?
shonkin said:
I just got my Note 5 Sprint phone a few weeks back (our company got a really good deal but it meant older phones). Being someone who just can't use an unrooted phone (a neurosis?) I looked around and decided to try the Teleteam CDMA S8 rom. (The S8+ doesn't offer wifi calling). I'm quite glad I did root, in part because the rom is nice and in part because I *hate* face book app and a few others and like being able to remove them totally. My two cents... do it!
---------- Post added at 10:39 AM ---------- Previous post was at 10:27 AM ----------
Trying again to post... xda is being a bit difficult today.
I got my Note 5 Sprint in the past few weeks due to my company getting a nice deal, the weak end being we got older phones. So... being a serious rooter, I found the Teleteam Rom and used the CDMA S8 version. It works great and allows wifi calling. Go for it. You won't be sorry.
Click to expand...
Click to collapse
ch99tj said:
What is your thought regarding security patches? That Rom hasn't been updated in like a year, correct?
Click to expand...
Click to collapse
Funny you should mention this. I began to get nervous about that very thing, and switched back to a rooted stock version of the rom. I do wish folks with the know-how might post flashable update files of the latest stock rom modem and bootloader... it would make life a bit less worrisome. Right now I'm on a May (?) 2018 update (when I got the phone)... I think there's been one more since. It would be nice to be able to flash that to my present setup.
The only thing you can flash is the latest baseband. And thats it.
Howdy.
So could flash stock and update. Then Reroot. Repeat with each security patch.
No issue rooting current update.
Ignore my ignorance... Finally got it right. Sorry for my stupid post. Thanks for the guide!