I've tried to repeatedly update to 2.3.6, forever every time it tells me i'm up to date. I'm running the stock OS, restored from Odin and rooted with zerg rush. I've cleared days on the device management app and still no love. I don't want to use the flashable update since its not complete. Any ideas?
Sent from my SAMSUNG-SGH-I727 using XDA App
I can't get mine to OTA either. I'm 100% stock except for being rooted, but even before rooting I couldn't get it to update.
No your only option is to wait and see if u get the update. Connect to wifi when u check for the update
. Or flash the zip it is complete just does not change your baseband
i think they pulled the 2.3.6 update.. who knows why.
waiters said:
i think they pulled the 2.3.6 update.. who knows why.
Click to expand...
Click to collapse
Yeah people keep reporting there phone not having the ota. My question is are you guys checking for.the ota while your connected to wifi? If not. Connect to wifi then check
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
Please and report if it worked or.not.
I got my skyrocket last week and updated instantly. My friend got one yesterday and will not see the update. I have tried it about 20 different times, so maybe the did pull the update for some reason.
Did your friend try while connected to wifi? For folks who have yet to receive the update in the status bar above, you might want to take the manual route. I am quite sure that the majority of you already know how to do that, but for those who do not know and are rather green to the entire setup, here is how you get going – first of all, pull down your phone’s Menu, head on to Settings and then Software Update. Select Check For Updates, and you ought to be able to see the Over The Air (OTA) update begin. Make sure you have a full battery and are connected to a Wi-Fi network to make it as painless as possible!
---------- Post added at 03:41 PM ---------- Previous post was at 03:32 PM ----------
......................yeah i think mabye they did pull it because so many of you havent gotten it somethings definately up
Yes. Someone has to of saved the update on their phone for Devs to look at.
silver03wrx said:
Did your friend try while connected to wifi? For folks who have yet to receive the update in the status bar above, you might want to take the manual route. I am quite sure that the majority of you already know how to do that, but for those who do not know and are rather green to the entire setup, here is how you get going – first of all, pull down your phone’s Menu, head on to Settings and then Software Update. Select Check For Updates, and you ought to be able to see the Over The Air (OTA) update begin. Make sure you have a full battery and are connected to a Wi-Fi network to make it as painless as possible!
---------- Post added at 03:41 PM ---------- Previous post was at 03:32 PM ----------
......................yeah i think mabye they did pull it because so many of you havent gotten it somethings definately up
Click to expand...
Click to collapse
I dumped my system to a dev he made a rom out of it for tmobile sgs2. I changed the build prop and apps back to at%t so there is a 2.3.6 rooted rom. It just does not update the modem.. but ive asked a dev to help me make a modem update zip to flash... but heres the rom http://forum.xda-developers.com/showthread.php?t=1361144
I called at&t today asking them why I haven't gotten the 2.3.6 update yet and the answer I got was priceless. First he stated that at&t releases the update in batches and I probably just haven't gotten there yet which I was fine with. But then he went on to say I should be getting another update after that to... wait for it... 3.1 honeycomb. At this point I hung up. I'd love to hear what answers anyone else gets from at&t.
nystreak said:
I called at&t today asking them why I haven't gotten the 2.3.6 update yet and the answer I got was priceless. First he stated that at&t releases the update in batches and I probably just haven't gotten there yet which I was fine with. But then he went on to say I should be getting another update after that to... wait for it... 3.1 honeycomb. At this point I hung up. I'd love to hear what answers anyone else gets from at&t.
Click to expand...
Click to collapse
Lol priceless
lol
10 chars
but on a side note, it appears the load was pulled. If I had to guess they saw reports in these very forums of users not loosing root when doing the OTA update. I bet the next ROM or push addresses that since the ROM itself appears to block the zergrush exploit we use to root this device. That is just a guess.
I've read someone reported problem with screen being turned all the way up after batter dropped 10 or 5%, and some other weird problems. Perhaps that's the reason for the pull?
says a patch is available but servers are busy
I'm european and my unlocked phone said servers are busy try again later, then slapped a 24hours cooldown till the next check
Only a factory reset reset the 24 hours cooldown (people suggested setting the date but nevermind)
Anyone tried the OTA update outside the US ?
Thanks
JD
You can always adjust the date forward and recheck... or date back then check if you're checking for the first time...
Sent from my SAMSUNG-SGH-I727 using xda premium
Yea mine won't find the update either even on wife. Lol AT&T had to be the worst customer service experience I've had. Took over 2 hours to update two phones.
tried with wifi also, no update
Sent from my SAMSUNG-SGH-I727 using xda premium
in the same boat as you guys...been pushing the date forward so i can check a couple times a day while on wifi, with full charge, and plugged in but still haven't found any updates.
does anybody know if they pulled the update? i've read a few different things regarding this...
I found that if you use SQLite Editor on the Device Management Database. Then open the fumo table and the change the lastupdatetime field to 0 it will reset the 24 hour cooldown.
I tried searching for this but haven't found anything on it, so I decided to post this.
There is a lot of skepticism on this.
Now I have heard it doesn't come preloaded but that UMA hooks (UMA is what Wi-fi Calling uses) are on the development piece.
Which makes sense since they will need to have it there for Skype.(Microsoft owns Skype)
This is the info I know, but I just wanted insight from more experienced developers.
Is it possible to use T-mobile Wi-fi Calling on Windows 8x?
Wifi Calling! Maybe
To follow up on the question I posted earlier:
Benjam'in said:
I tried searching for this but haven't found anything on it, so I decided to post this.
There is a lot of skepticism on this.
Now I have heard it doesn't come preloaded but that UMA hooks (UMA is what Wi-fi Calling uses) are on the development piece.
Which makes sense since they will need to have it there for Skype.(Microsoft owns Skype)
This is the info I know, but I just wanted insight from more experienced developers.
Is it possible to use T-mobile Wi-fi Calling on Windows 8x?
Click to expand...
Click to collapse
I have found some proof on the Internet here:
HTML:
https://skydrive.live.com/?cid=7ac840829c778f5e&id=7AC840829C778F5E%212924&sff=1&authkey=!ANhBCDuIfFrB2P0
And it seems as though an OTA update has been hitting some phones here are the specs:
OS version: 8.0.102211.204
Firmware revision: 1532.20.20010.531
Hardware revision: 0003
Radio software: 1.11b.32.19.23_2_15.42.32.19
Just wanted to pass this information on for others.
-Benjam'in
To follow up on my earlier post:
Benjam'in said:
I have found some proof on the Internet here:
HTML:
https://skydrive.live.com/?cid=7ac840829c778f5e&id=7AC840829C778F5E%212924&sff=1&authkey=!ANhBCDuIfFrB2P0
And it seems as though an OTA update has been hitting some phones here are the specs:
OS version: 8.0.102211.204
Firmware revision: 1532.20.20010.531
Hardware revision: 0003
Radio software: 1.11b.32.19.23_2_15.42.32.19
Just wanted to pass this information on for others.
-Benjam'in
Click to expand...
Click to collapse
I was on the phone with three different techs giving me the run around like phone techs love to do.
But, I eventually got to the bottom of what is going on. The above firmware release was accidentally released on March 20th it hit 1000 or so phones causing more problems then good and also containing wifi calling. This firmware was then pulled back and has yet to resurface. (If it even will resurface again) This is also disappointing do to the fact that now the HTC 8x has been labeled EOL.
Just thought I would inform everyone who is interested.
In a lighter note, some windows phones coming out soon will have wifi calling.
-Benjam'in
Benjam'in said:
To follow up on my earlier post:
I was on the phone with three different techs giving me the run around like phone techs love to do.
But, I eventually got to the bottom of what is going on. The above firmware release was accidentally released on March 20th it hit 1000 or so phones causing more problems then good and also containing wifi calling. This firmware was then pulled back and has yet to resurface. (If it even will resurface again) This is also disappointing do to the fact that now the HTC 8x has been labeled EOL.
Just thought I would inform everyone who is interested.
In a lighter note, some windows phones coming out soon will have wifi calling.
-Benjam'in
Click to expand...
Click to collapse
Thanks sssooooo much for this info! I have an HTC 8x with the 20008 firmware that I bought a couple of weeks ago. I was wondering what happened to this update! That was the whole reason I pulled the trigger on it...the promise of WiFi calling...the Nokia's that TMO had were all crap. Maybe we can get someone with the 200010 firmware to dump it off their phone?
compu829 said:
Thanks sssooooo much for this info! I have an HTC 8x with the 20008 firmware that I bought a couple of weeks ago. I was wondering what happened to this update! That was the whole reason I pulled the trigger on it...the promise of WiFi calling...the Nokia's that TMO had were all crap. Maybe we can get someone with the 200010 firmware to dump it off their phone?
Click to expand...
Click to collapse
Yes I wanted to make sure it had wifi calling before I bought it. (Thank God I know a Tmobile Reseller) - he let me play with the phone till I found out what was going on, also let me talk to someone knowledgeable (Dealer Line).
TMO did happen to land the Lumia 925 (Release in July sometime, Nokia's current flagship phone) which is what I will probably go with, although they haven't mention whether it will have the wifi calling or not, but the Lumia 521 (or something close to that, crappier version of current lumia's) will be released with wifi calling.
Which makes me hope/assume they would put it on the Lumia 925.
Good Luck to you though.
-Benjam'in
Thanks. I actually got a good deal on a sealed, NIB 8x on eBay. I desperately needed to replace my iPhone 3GS and I didn't want to go with the iPhone 5. I am guessing when the next update comes, it will have Wi-Fi calling. I heard it was in beta, and still has a major bug with "Wi-Fi only" mode (I'm guessing that's why they pulled it).
The 925 looks pretty damn sexy, though!
---------- Post added at 07:33 PM ---------- Previous post was at 06:55 PM ----------
I was actually just reading the Windows blog about the Lumia 521, and it says that WiFi calling will be delivered to those devices OTA starting on 5/20. Maybe it will get delivered to other devices as well? *crosses fingers*
Source:
http://blogs.windows.com/windows_ph...an-you-buy-for-under-150-answer-not-much.aspx
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
Hey,
I traded a bunch of old laptop parts and got this phone in exchange: an HTC One S. I think some call it a Ville. Nice looking phone.
Anyways, when I made the trade, I didn't notice that there was no icon in the status bar to show it was receiving any kind of cell signal. Really bright and sunny day washed the screen out. Jumped in my car, where it was a little darker, and discovered that the phone had a custom ROM (Or is it RUU?) installed. No biggie. Actually, it ran really smooth and kinda looked cool. It was a Cyanogenmod Mod, called Dark Jelly S edition. My thought was that I could use it as a backup phone, so I went to a local place to get an unlock to use on my network (it was, supposedly, on Fido. I'm on Koodo).
So, I tried to get the IMEI # off of it. No dice. Tried *#06# and I got a blank line. Went into settings, and settings crashed. When I got to the place I get my unlocking done, the guy at the desk knew that if you took off the back cover, there it was! Buddy got my code, but when I put my sim in, nothing. No way to enter the code.
Now, I'm no phone expert, but I knew something was terribly wrong. I have played around a little with smart phones, and even rooted one (well, partially at least), but I did some research, mostly here, and found that this appears to be a rather troublesome phone to mod. to make matters worse, I found out how to get into the bootloader and I fear I have done more harm than good. Not sure what I did, but then the SD card (which, of course, there really isn't one) became unmounted.
What I need, is a step by step process on what I can do, if anything, to make this phone work again. Now I know there are already threads like this on here, but they assume that the people they are helping have dev backgrounds. I do not. I get lost in all the jargon. I follow for a bit and then I get ROM and RUU all mixed up and have no idea what facepalm is or why you want S-off. It needs to be in plain english, or at least as plain a language as the terminology permits. I'm sure I'm not the only one on the planet suffering a similar fate and wondering what the heck to do.
Here is what I know:
Model - PJ40110
Kernel version - 3.0.71-gdde6c1e-dirty
[email protected] #1
Wed May 1 00:22:12 CEST 2013
CPU - ARMv& Processor rev 4 (v71)
Android version - 4.1.2
CyanogenMod version - 10-20130430-UNOFFICIAL-ville
Build version - Dark-Jelly-S-Edition -(Build-31)
Build date - Mi 1.Mai00:19:13 CEST 2013
Build # - cm_ville-userdebug 4.1.2 JZO54K eng.
xxmrhyde.20130501.001850 test-keys
Having been rooted and modded, I can access a lot, provided that doesn't happen to be one of the areas that crashes. If you need more info, tell me where to look and exactly what to look for. I'm really that much of a noob. All I really want is for it to work, whether that means taking it back to stock or another mod that actually works. Please help!
Hi, thank you for using XDA Assist. The purpose of XDA Assist is to point you in the right direction. I'm going to give you some links which hopefully will solve your problem. You're going to have to do the homework. Not having an IMEI is going to be your biggest problem but the first thing to do is get the device back to stock.
Start here, http://forum.xda-developers.com/showthread.php?t=1630459 and here, http://www.xda-developers.com/all-i...-mytouch-4g-slide-amaze-4g-rezound-and-vivid/
If you have further questions ask in here, http://forum.xda-developers.com/htc-one-s/help
Thread closed.
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!