I spoke to a rep the other day regarding Jelly Bean. Long Story short he said it is rolling out to their systems now (computer support info) so we should have it very very VERY soon.
Sent from my SCH-I535 using Tapatalk 2
Your title gives the impression that it'll be JB
Edit : you edited your post.
Sent from my SCH-I535 using xda premium
blestsol said:
Your title gives the impression that it'll be JB
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
First mistake is assuming the reps have a clue about what they are talking about. They are lucky to dress themselves for work every morning. If I had a nickel for every time a rep told me an update is coming, I'd be a thousandaire.
ddurandSGS3 said:
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
Click to expand...
Click to collapse
I think when he says a small update he is describing his post as a small update to here. No the actually Verizon update.
Of course the next Verizon update will be JB. They do not need to make our phone ready for JB, it is ready and the leak we have also says it is pretty ready to go.....
Yes to Jellybean. Sorry for the confusion.
Sent from my SCH-I535 using Tapatalk 2
ddurandSGS3 said:
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
Click to expand...
Click to collapse
I'm familiar with your posts in other threads. Carry on.
Sent from my SCH-I535 using xda premium
Never trust verizon reps....
I know a bunch of people who work for Verizon corporate.
I tell THEM when builds/phones are coming. I just updates their store model M to JB on Friday. They had no idea
Sent from my SCH-I535 using Tapatalk 2
Delete.
Sent from my Galaxy Nexus using xda app-developers app
The leak seems more stable than the ICS official to me...
I think these delays are more of a marketing strategy of sort rather than a real technical time to get it ready.... I might be wrong but...
Well VZW is going to have to do something either right before or same day the Note 2 comes out.
Sent from my SCH-I535 using Tapatalk 2
It seems more of a marketing strategy because t mobile released theirs after the note 2 was released.
Sent from my SCH-I535 using xda app-developers app
Verizon lies to there customers. When I bought the galaxy nexus I had 2 weeks to return the device. Signal was terrible but, loved the phone otherwise. I contaced them and they said and update when be comming out that would fix the problem but it would be after the 2 weeks of me being able to return the phone....no update acctually for several months then I was stuck with the useless phone.
Sent from my SCH-I535 using xda premium
Well that depends, what's their definition of "soon".
Terry_blair said:
Verizon lies to there customers. When I bought the galaxy nexus I had 2 weeks to return the device. Signal was terrible but, loved the phone otherwise. I contaced them and they said and update when be comming out that would fix the problem but it would be after the 2 weeks of me being able to return the phone....no update acctually for several months then I was stuck with the useless phone.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Same kind of thing happened to me. I wasn't getting an OTA even though one had come out. I went back to the store to exchange and he was like "it takes a while to get to everybody" so I went home and called Verizon and he advised me to go back and demand replacement.
I went back and demanded a new phone and he was like "fine I'll give you a new phone but the new one is going to do the same thing."
Well, he gives me a new phone, same sim card, and what do you know... first thing to pop up on the screen???
UPDATE AVAILABLE!
I laughed to his face and told him I would never be doing business with his store again.
Sent from my SCH-I535 using xda app-developers app
josh995 said:
Same kind of thing happened to me. I wasn't getting an OTA even though one had come out. I went back to the store to exchange and he was like "it takes a while to get to everybody" so I went home and called Verizon and he advised me to go back and demand replacement.
I went back and demanded a new phone and he was like "fine I'll give you a new phone but the new one is going to do the same thing."
Well, he gives me a new phone, same sim card, and what do you know... first thing to pop up on the screen???
UPDATE AVAILABLE!
Click to expand...
Click to collapse
Did you manually check for an update not long before you got the new phone?
From recent discussion, it seems there is a counter being kept for each account that notes when the last query for an OTA was made and it does not allow for a new check after a certain timeframe (seems anywhere from 2-4 weeks) after the most recent manual pull attempt. If your phone is not yet in the active queue for an active OTA push, the prior attempt will naturally return no new updates . . . but subsequent checks won't actually determine if you are in the OTA queue or not until the timeout period, even if your account was placed into the OTA queue by that time. My understanding is that this helps them balance load of the OTA downloads to some extent. Eventually, the OTA will be pushed to your phone, regardless of manual check attempts. It takes patience to wait.
However, this is bound to your account info, so changing a SIM card in the phone can make it seem as if the phone and/or SIM was the problem, because your prior, manual attempt was made when you were not yet in the active OTA queue, subsequent manual checks will not actually perform a check for the OTA for a period of time since the prior manual check - even if you were recently added into the active queue, and then a new SIM essentially resets the counter in your account and performs a true check for the OTA: if you were placed into the queue while unable to actually perform a check just before the new SIM, the OTA will now download and look like a miracle.
So, it does take patience. I experience the above symptoms exactly as described for the prior OTA and merely waited for the OTA to be pushed onto my phone - they gave me a timeframe for that and they were correct.
- ooofest
ooofest said:
Did you manually check for an update not long before you got the new phone?
From recent discussion, it seems there is a counter being kept for each account that notes when the last query for an OTA was made and it does not allow for a new check after a certain timeframe (seems anywhere from 2-4 weeks) after the most recent manual pull attempt. If your phone is not yet in the active queue for an active OTA push, the prior attempt will naturally return no new updates . . . but subsequent checks won't actually determine if you are in the OTA queue or not until the timeout period, even if your account was placed into the OTA queue by that time. My understanding is that this helps them balance load of the OTA downloads to some extent. Eventually, the OTA will be pushed to your phone, regardless of manual check attempts. It takes patience to wait.
However, this is bound to your account info, so changing a SIM card in the phone can make it seem as if the phone and/or SIM was the problem, because your prior, manual attempt was made when you were not yet in the active OTA queue, subsequent manual checks will not actually perform a check for the OTA for a period of time since the prior manual check - even if you were recently added into the active queue, and then a new SIM essentially resets the counter in your account and performs a true check for the OTA: if you were placed into the queue while unable to actually perform a check just before the new SIM, the OTA will now download and look like a miracle.
So, it does take patience. I experience the above symptoms exactly as described for the prior OTA and merely waited for the OTA to be pushed onto my phone - they gave me a timeframe for that and they were correct.
- ooofest
Click to expand...
Click to collapse
Well I had been manually checking for like a week, however, I wasn't receiving an update that had been out for months. The phone was 2 updates behind!
The new phone with my same SIM updated instantly after it was set up. I didn't even have to manually check. And then it updated again. So I honestly believe there was something wrong with the phone. Very strange to not get an update that had been out for months, you know?
Sent from my SCH-I535 using xda app-developers app
Related
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
3rdcoast said:
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
Click to expand...
Click to collapse
It takes time. The OTA will likely roll out over a few weeks. Once your imei is flagged you'll get the ota when the device checks in again.
Sent from my Nexus S using xda premium
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
Click to expand...
Click to collapse
That has never worked for me. Does it actually work for anyone?
Thanks folks. I'll wait a few days before looking at a manual update. Or until the bug happens too often. It rather freaked me out at first and then I found that this is a common bug on certain versions of the phone.
The "search button firing on its own" bug is NOT fixed in the latest OTA
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
I still have it and so do half a dozen or more people in the thread that got this whole thing started.
I know "Voice Search" bug has already penetrated the blogosphere ecochamber, and it is therefore useless for me to continue to correct people on semantics, but the Voice Search app just happens to be tied to a long-press of the search button so occasionally it pops up when this bug occurs. If "compose new text message" is tied to that event, you will see it and not Voice Search.. its the hardware search button that fires in low 3G areas that is the bug. Voice Search the app is completely unrelated other than most people have it tied to long-press of the hardware search button... ok, off my soap box
ericshmerick said:
That has never worked for me. Does it actually work for anyone?
Click to expand...
Click to collapse
I have no idea lol. I just figured the op could see if it works for him.
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
I've used this successfully. It's how I got 2.3.6 on Friday morning and got the link to post in the forums
Sent from my Nexus S
3rdcoast said:
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
Click to expand...
Click to collapse
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
ericshmerick said:
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
Click to expand...
Click to collapse
Then there is no reason to force an update. Not one. In fact it breaks more than it fixes. 12 more days of this and it goes back. I'm not going to go with the manufacturer route and I know that Google won't talk to me about it.
100 pages of the same issue in one post with many of them being told they are the first to report it tells me all I need to know.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Click to expand...
Click to collapse
I'm pissed at Google for sure but Sammy isn't off the hook yet. Why the same code doesn't do this on other phones and also seems to infect Canadian phones more than others says to me there is more to this than just Google code. The original SGS was a disaster until they finally replaced the pb and I flashed it properly. Now it is fine but thought I would have a better time with the N. Three times back for warranty is a bad track record. And this one might be making a trip back too.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
Click to expand...
Click to collapse
yep, my personal opinion is that Samsung has too many issues to make up for what it does do well. And google has zero customer service, this isn't the only issue I have that the robot alone will never fix.
Anyway, I'm done with this topic. I'll wait to see if a definitive fix comes or not.
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
ericshmerick said:
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
Click to expand...
Click to collapse
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
3rdcoast said:
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
Click to expand...
Click to collapse
Sparky? No need to go there kiddo.
Anyway, I have bad news for you. 2.3.6 doesn't fix the voice search bug.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
By the way, it's a google managed phone, so you will get 2.3.6 soon. It's not like Samsung grabs the release, adds bloatware and jacks up the rom like they do with their managed phones (i.e. Galaxy S).
Any other Android phone you leave for the Nexus S will mean loooong wait times for official releases.
Good luck in your journey.
I thought you read the thread, it isn't very long. Others have said and I repeated the big news about 2.3.6 not fixing the problem and causing tethering issues and who knows what else. That's why the OTA is a moot point. I won't be flashing it anyway as it turns out. So I'll go wherever I want including buying phones like I've always done which means root and rom, I know all about carrier's and manufacturer's history. The N is looking like the same deal.
Now I'm really done. No need for a reply. goodnight.
I'll reply anyway and you will read it anyway.
I'm not sure what your purpose of this thread was. Yes I read it.
You asked if it takes time to receive the update. Many answered yes.
You then said you would wait a few days (posted today) and if it wasn't OTA'd, you'd go download it.
You then said you won't force an update and if you wanted it that bad you'd flash recovery.
You then expressed your disappointment with the Nexus S.
You mentioned your frustrations with a completely different Samsung phone, the Galaxy S (not the Nexus S).
You then said Samsung has too many issues to make up for anything it does well.
You then called out Google for having zero customer service and stated you will wait to see if there is a definitive fix for your issue.
Lastly, you said the OTA and flashing the ROM is a moot point and went to bed.
When I put all of this into a calculator, the result that's spat out is:
Get an iPhone. Android isn't for you.
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
ericshmerick said:
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
Click to expand...
Click to collapse
i'll read that much. now stfu, you aren't helping.
iphone, that's funny
For some reason my phone keeps saying up to date & I have no idea if I just got a bad unit. Can anyone tells me how to get it to update? I'm still under my 30 days but time is ticking on me. Please help
Sent from my SAMSUNG-SGH-I727 using XDA App
Stevieboy02008 said:
For some reason my phone keeps saying up to date & I have no idea if I just got a bad unit. Can anyone tells me how to get it to update? I'm still under my 30 days but time is ticking on me. Please help
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
when you go into phone info does it still say 2.3.5. are you using CWM?
Nope my phone is stock. No root. Yes it says 2.3.5
Sent from my SAMSUNG-SGH-I727 using XDA App
Stevieboy02008 said:
Nope my phone is stock. No root. Yes it says 2.3.5
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
i have heard they pulled the update.....but silver posted a Zip file that you can flash to get the update in the dev section.
others have the same issue
Oh OK. I went to the AT&T store last night & their demo phones have it so I felt left out. LOL thanks for all the help. I'm new to android development but that's my 4th android phone from a long line of iPhone users used them all till the 4S. Can't seem to like them again
Sent from my SAMSUNG-SGH-I727 using XDA App
the2rrell said:
i have heard they pulled the update.....but silver posted a Zip file that you can flash to get the update in the dev section.
others have the same issue
Click to expand...
Click to collapse
that is correct, for an unknown reason they pulled the update. It was only available for like 5 days =(
nobody knows the changes in 2.3.6 and nobody knows why they pulled the update either =(
Those who are not aware of the fact that the AT&T Samsung Galaxy S II Skyrocket is delivered with Android 2.3.5 will be surprised when they receive an update notification that will allow them to upgrade their smartphones to version 2.3.6.
Although the carrier is still mum about the update, AndroidCentral reports that lots of Galaxy S II Skyrocket owners started to receive it in the last 24 hours.
No word on what's changed after the update, but those who upgraded noticed that it keeps root and boot-up seems a bit faster.
In addition, the speed of the new radio firmware on HSPA has been improved, and several changes on the camera interface have been included as well.
What's certain is that Android 2.3.6 fixes a Google Voice Search bug. Other than that AT&T may have squeezed several tweaks and possibly a few more performance improvements.
CosminVasile · 268 followers
@
AT &T
FILEDUNDER:
---------- Post added at 08:51 PM ---------- Previous post was at 08:48 PM ----------
AT&T аnԁ Samsung hаνе јυѕt voiced thаt аn over-thе-air ascent fοr Android 2.3.6 hаѕ started pulling out tο AT&T’s Samsung Galaxy S2 Skyrocket. Thе refurbish іѕ approaching tο finalise thе Google Voice Search issue.
Galaxy S2 Skyrocket users аrе anticipating thаt thеу сουԁ irrevocably υѕе Google Voice Search аftеr thе update.
If уου haven’t perceived аnу notifications јυѕt уеt, уου mау wish tο try out fοr thе refurbish manually. Tο ԁο ѕο, јυѕt daub οn Software Update underneath Settings аnԁ click οn Try out fοr Updates. Updates wουԁ customarily rυn fοr mins depending οn уουr download speeds, ѕο уου mіɡht wish tο take the lay fοr thіѕ one.
Nеіthеr Samsung nοr AT&T hаѕ nοt referred to аnу οthеr nеw underline іn thе update. Though, ѕοmе аrе suspecting thаt ѕοmе ехсееnt things аrе packaged іntο thе Android 2.3.6 update. Sο, іf уου οwn a single οf thе Samsung Galaxy S2 Skyrocket, thеn уου mіɡht wish tο try out out уουr handset fοr thе update.
Hаνе уου implement thе refurbish οn уουr phone? Whаt οthеr elements іѕ enclosed οn thе update?
Posts
Well thank you guys. I hope I get it soon
Sent from my SAMSUNG-SGH-I727 using XDA App
My phone still saying up to date. Did I get a bad headset?
Sent from my SAMSUNG-SGH-I727 using XDA App
I am in the same boat. I have heard that carriers will often roll out updates to only a certain range of IMEIs over a period of time to reduce bandwidth/server constraint... usually one batch per week until all the IMEIs are white listed.
I do not know if this is the reason many of us (myself included) are unable to update, but I consider it possible.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Just got off the phone with at&t tech , they told me the update was pulled out then re-released but based on market to market basis, so all i can do is just sit & wait till my phone tells me its there or just keep checking every 24 hours , as of what the update changes they couldnt tell me because simply they have no idea what does it fix they just know that its live , thank you all for the help if anyone knows what does that update fixes please let me know , thank you all for all your help
They probebly pulled it because of all the white screens everyone was getting. All Stock, and rooted alike.
I wont touch it unless it has something in it worth the update.
pcrat said:
They probebly pulled it because of all the white screens everyone was getting. All Stock, and rooted alike.
I wont touch it unless it has something in it worth the update.
Click to expand...
Click to collapse
Exactly. With the exception of the removal of CIQ (which we can disable anyways), there's really nothing that the update has to offer
This old thread was in refrence to the other 2.3.6 update att started then pulled. It was kk1
Lol so the new ucla3 is there second time ...hmmmm
i happened to find this while just looking online although it seems like there are arguments against it and for it accross the table... im neutral as id much rather have an unlocked bootloader i am simply just posting this so everyone can see it and maybe share something to prove or disprove
http://www.gottabemobile.com/2012/07/16/verizon-wont-unlock-galaxy-s-iii-bootloader/
this says they wont release an update to unlock the s3
beeholtz said:
this says they wont release an update to unlock the s3
Click to expand...
Click to collapse
Verizon never made any sort of promise that they would unlock the bootloader. The rumor got started a month ago from transcripts of chats with ill-informed customer service reps who didn't know a bootloader from a barnacle. They chose to lock it, and they will not willingly reverse that decision. When our bootloader gets unlocked, it will be through the fine efforts of communities like this one. Depending on the type of exploit, I might not be surprised if Verizon then pushes an update to relock the bootloader, as has happened with some HTC phones in the past.
In general, never take the word of a CSR without a fair bit of skepticism, especially if it conflicts with VZW's official statements.
lazarus2405 said:
Verizon never made any sort of promise that they would unlock the bootloader. The rumor got started a month ago from transcripts of chats with ill-informed customer service reps who didn't know a bootloader from a barnacle. They chose to lock it, and they will not willingly reverse that decision. When our bootloader gets unlocked, it will be through the fine efforts of communities like this one. Depending on the type of exploit, I might not be surprised if Verizon then pushes an update to relock the bootloader, as has happened with some HTC phones in the past.
In general, never take the word of a CSR without a fair bit of skepticism, especially if it conflicts with VZW's official statements.
Click to expand...
Click to collapse
Correct me if I'm wrong but once and if the bootloader is unlocked we can just stay on that bootloader (unlocked) even if verizon does try to re-lock it correct? In a sense similar to s-off
Sent from my SCH-I535 using Tapatalk 2
niv3d said:
Correct me if I'm wrong but once and if the bootloader is unlocked we can just stay on that bootloader (unlocked) even if verizon does try to re-lock it correct? In a sense similar to s-off
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
IMO - Its just safe practace not to take any OTA updates until after the Devs got them fixed. Verizon could patch their own bootloader if they needed to - via an OTA. So, yes, you could stay unlocked (once it is unlocked anyway), so long as you stay away from OTAs .
i have a thunderbolt and in 9 days when i have an upgrade available on my account will be getting the s3. on my thunderbolt after i rooted i never even had to block updates i just straight up never got ota updates. is there a setting in the s3 that ill need to check or uncheck a box to not receive them after i root?
why are so many folks concerned about ota updates? The day one roots his/her phone OTA should be forgotten. The devs here will have all the updates we can possibly achieve and in alot more timely fashion.
droidstyle said:
why are so many folks concerned about ota updates? The day one roots his/her phone OTA should be forgotten. The devs here will have all the updates we can possibly achieve and in alot more timely fashion.
Click to expand...
Click to collapse
**** yeah!
Sent from my SCH-I535 using Tapatalk 2
if you actually took the time to read my post you would have noticed that i asked if there is a way to NOT RECEIVE OTA UPDATES as opposed to asking about receiving them. i will post that question in q and a when i get the phone thanks anyways
beeholtz said:
if you actually took the time to read my post you would have noticed that i asked if there is a way to NOT RECEIVE OTA UPDATES as opposed to asking about receiving them. i will post that question in q and a when i get the phone thanks anyways
Click to expand...
Click to collapse
I did read your post...my apologies since that post was not 100% directed towards you...I kind of hijacked your thread posting that for others to read lol. There has been 100 threads on here about "will I lose ota if I root".
A big cellphone company lied to us? It can't be. Haha sorry for the sarcasm but the way this phone has been going I think an unlock will come through the developers over the big companies. That means we'll have to pay up on that bounty.
Sent from my SCH-I535 using xda premium
ya my bad too i didnt mean to be a **** about it. i had some ahole customer i dont like helping come up today. fixing their computers and network just makes about anything else sound like more fun. im just stoked to get the phone soon but i also am getting it knowing about having a locked bootloader and the possibility of all those little quirks and issues that some people have and some dont. On my thunderbolt i rooted it not long after i got it and have flashed roms and kernels and radios etc until i find one i really like at the time. I'm figuring once the dev. edition comes out people will get it and verizon will then do the same thing on the next big deal phone that comes out in however many months.
I swear at this point, they're just sitting back in their chairs and cackling madly. Biggest trolls ever.
I think the "ota" talk only references people who are stock and take ota, get said-bootloader "fixed" by vzw, then want to mod afterwards. Then a new/different method will have to be used, whether it be Odin/rollback/whatever is come up with.
People already unlocked and rooted will be fine.
Sent from my Galaxy S3 using Tapatalk 2
I can't say i'm terribly surprised, Verizon seems content to violate whatever they want for their benefit. Just need to put the pressure to them.
I am not even concerned about the boot loader anymore. You can flash kernels with kexec cwm(6010), Odin new modems and the roms that synergy, bean and Nos are producing are just fantastic. Developers will find a way and there are some great ones on the SG3.
Sent from my SCH-I535 using xda premium
Rather doubt it
Doubt verizon will unlock the bootloader
anytime soon. For now we are left to
root use custom stock roms with some
themes or leave Verizon.
Cheers,
INC > TB > S3
azbobs said:
For now we are left to
root use custom stock roms with some
themes or leave Verizon.
Cheers,
INC > TB > S3
Click to expand...
Click to collapse
This is simply not true...there is plenty of aosp dev going on! we have 4 cm10 roms, 1 aokp jb rom, 1 paranoidandroid rom...the bugs these roms do have are not related to the locked bootloader. Its the same issues across multiple devices. 5min of research would of yielded these results...
Verizon is NEVER going to unlock the bootloader. Ever. You can quote me on that.
Sent from my SCH-I535 using xda premium
---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------
droidstyle said:
This is simply not true...there is plenty of aosp dev going on! we have 4 cm10 roms, 1 aokp jb rom, 1 paranoidandroid rom...the bugs these roms do have are not related to the locked bootloader. Its the same issues across multiple devices. 5min of research would of yielded these results...
Click to expand...
Click to collapse
Ya and they all break your phone and wipe out vital information like imei and/or permanently break data.
Sent from my SCH-I535 using xda premium
It's the Big Red SideShow starring Mr. Smoke & Mirror's Himself Lowell McAdams.
Verizon can burn in hell. I
Off topic, but is the volume really this quiet on this phone? I came from the OG like 2 weeks ago and it was literally double the decibels that this thing is putting out. I've heard about the volume+ app but is that the only way to increase volume? I'm still stock but plan on rooting n roming soon, perhaps one of them contains that dsp manager that cm7 base used to include?
Sent from my SCH-I535 using xda app-developers app
Just got my Galaxy S III on Friday. It's on 4.0.4 right now, and I'm just checking to see if there's an update available and I get this message:
Service unavailable
Check for System Updates under Settings > About device when service is available
If it helps, I've disabled most of the Verizon apps that are included on the phone, but I don't think that would affect anything. *I enabled all of the apps that I disabled, but it's still giving me the same message when I try software update.
I also reset my phone to factory and it still did it.
If there wasn't an update, it would say something like "You are up to date" Right?
Thanks
Depends on which verizon apps. The software update comes from verizon.
Sent from my SCH-I535 using xda app-developers app
Disabling stock software can definitely stop an OTA update from installing.
Ok, I re-enabled everything and tried software update again and it's still saying the same thing... :/
Can anyone help, is this a fault with my phone?
I want to find out before my 14 day return/exchange policy is up :/
Josh...my wife has a thunderbolt and is getting the same thing...her phone booted into boatloader today which I thought was funny since she is straight stock...its not your new phone its them.
Sent from my SCH-I535 using xda app-developers app
jcandrew said:
Josh...my wife has a thunderbolt and is getting the same thing...her phone booted into boatloader today which I thought was funny since she is straight stock...its not your new phone its them.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I hope so! Would suck to not be able to update to Jelly Bean...whenever Verizon lets it come...
I'm in the same dilemma. I called Best Buy where I upgraded my phone last Friday and they said they've never heard of this. Chances are I might try to have them replace it with a phone that will update.
nike_air3 said:
I'm in the same dilemma. I called Best Buy where I upgraded my phone last Friday and they said they've never heard of this. Chances are I might try to have them replace it with a phone that will update.
Click to expand...
Click to collapse
Had my phone for a while and i get no such message... mine shows ....................No new software update available.........just did software check a cpl of of times to see if i would get your message and no.
crazydad said:
Had my phone for a while and i get no such message... mine shows ....................No new software update available.........just did software check a cpl of of times to see if i would get your message and no.
Click to expand...
Click to collapse
I think its their server. I just wiped clean all the way back to the original stock image and then tried to get the OTA, and was getting the same message. It worked on monday night...not sure what happened to them since. Oh well, I was going to make a nand backup of my phone with the OTA.
josh995 said:
Just got my Galaxy S III on Friday. It's on 4.0.4 right now, and I'm just checking to see if there's an update available and I get this message:
Service unavailable
Check for System Updates under Settings > About device when service is available
If it helps, I've disabled most of the Verizon apps that are included on the phone, but I don't think that would affect anything. *I enabled all of the apps that I disabled, but it's still giving me the same message when I try software update.
I also reset my phone to factory and it still did it.
If there wasn't an update, it would say something like "You are up to date" Right?
Thanks
Click to expand...
Click to collapse
i have the same issue. i checked on my GNEX and no issue. move the sim to my S3 and cant check for updates.WTF...not sure what the deal is. i have gone as far as restoring using ODIN back to the ROM that was shipped with the phone and same result. I know i have had some odd issues with this phone...its been locking up, GPS causes the phone to reboot (not all the time tho). im ready to go back to VZW and swap it out. Im back on stock, NO ROOT,NO NOTHING, just pure stock.
I just recently started getting the same error too. You are not alone my friend.
Sent from my SCH-I535 using xda app-developers app
josh995 said:
Just got my Galaxy S III on Friday. It's on 4.0.4 right now, and I'm just checking to see if there's an update available and I get this message:
Service unavailable
Check for System Updates under Settings > About device when service is available
If it helps, I've disabled most of the Verizon apps that are included on the phone, but I don't think that would affect anything. *I enabled all of the apps that I disabled, but it's still giving me the same message when I try software update.
I also reset my phone to factory and it still did it.
If there wasn't an update, it would say something like "You are up to date" Right?
Thanks
Click to expand...
Click to collapse
thanks you for healing Q?
Same error for me today. I'm totally stock and have been since I bought the phone. I'm not going to worry about until there's an update.
Sent from my SCH-I535 using xda premium
I'm in the same boat, I'm not rooted and get the same Service Unavailable error. That's some BS.
Please read forum rules before posting
Questions go in Q&A
Thread moved
FNM
Just to let you all know I wound up having to get a new phone. The guys in the store all tried telling me that nothing was wrong with my phone, and that the update would come to me 'eventually.' Kept telling me I don't need a new phone.
I had only had the phone for 6 days, and the return/exchange policy is 14, so I demanded they give me a new phone. They said "The new phone's gonna do the same thing dude."
So I get a new phone, and the first thing it does when it's powered up and set up...."UPDATE AVAILABLE!"
I said "Gee, imagine that."
Don't take no for an answer.
Anyone know what controls updates? I cleared data for "sdm" which is part of the check but I don't know what else is. It's pushing and pulling data when checking for an update but always comes back with service unavailable. If this doesn't work when I the next ota comes out I guess verizon is giving me permission to root and install a custom recovery
Sent from my SCH-I535 using xda premium
Are verizon customers able to update via Kies or is that international only? That might be a way around this problem?
Google says yes.... Should have check that first.... Sorry.
Sent from my SCH-I535 using xda premium
Mine has been saying the same thing.
Sent from my SCH-I535 using Tapatalk 2
I had to reset my phone back to stock due to some issues with data/signal issues. I'm now not able to accept the ota vrlg7 every time i hit check for update it says service unavailable. I have my imei, stock,bootloader locked back. Im able to get on the internet so I know data isnt an issue as far as connectivity..
Maybe try a factory reset from inside touchwiz?
fr8cture said:
Maybe try a factory reset from inside touchwiz?
Click to expand...
Click to collapse
tried that a no go..I have a replacement coming tomorrow so i guess i could wait it out...Its my fourth one...
I had the same issue. I called support and they sent me a new sim card. Once I threw it in there and it activated the error went away. I would call or go into a store and get a new sim.
Hate to tell you but you probably need a new phone. I was getting that message with my first GS3. I took it to the store I bought it at and they tried a new sim...same message. They didn't want to, but I demanded they give me a new phone. I paid full retail price for the phone, so I didn't want it replaced with some refurb piece of junk.
I commented before reading further posts. Hope your replacement is good.
Sent from my SCH-I535 using xda app-developers app
I have this problem too. I wonder how many people have this problem and don't know it? Not everyone is as update happy as the people on this forum are..... Myself included
Sent from my SCH-I535 using xda premium
The new replacement solved the issues..but decided to get new sim as well just to make sure..I am not 100% sure but Im beginning to think that some of the peoples issues may lie within flashing certain roms and zip alterations and causing hardware issues... I could be wrong but the thought has crossed my mind
antawnm26 said:
The new replacement solved the issues..but decided to get new sim as well just to make sure..I am not 100% sure but Im beginning to think that some of the peoples issues may lie within flashing certain roms and zip alterations and causing hardware issues... I could be wrong but the thought has crossed my mind
Click to expand...
Click to collapse
I have never rooted or flashed any rom on this phone, 100% stock. This started a few days after the last update.