I read on cnet last night that Verizon would be sending an update for all GS3 users and, sure enough, I was prompted for the update for an update morning. (5/30/2013)
I am running stock 4.1.2 rooted.
Does anyone know if this is safe for me to apply? Will I lose root?
Thanks!
yep
You will lose root and if you have a custom recovery (twrp for instance) it will be overwritten. You will also get a "update failed" message. However, the update actually will succeed. You can reroot the same way you did before (unlock bootloader, root, install custom recovery if desired). I was surprised that the OTA was even available for rooted/custom folks. There will be a couple new apps installed, one dealing with CallerID which will force your 4G and WiFi to both be on - freezing that new app will fix that issue too, search the forums for details.
Goddrick said:
I read on cnet last night that Verizon would be sending an update for all GS3 users and, sure enough, I was prompted for the update for an update morning. (5/30/2013)
I am running stock 4.1.2 rooted.
Does anyone know if this is safe for me to apply? Will I lose root?
Thanks!
Click to expand...
Click to collapse
gozirra said:
You will lose root and if you have a custom recovery (twrp for instance) it will be overwritten. You will also get a "update failed" message. However, the update actually will succeed. You can reroot the same way you did before (unlock bootloader, root, install custom recovery if desired). I was surprised that the OTA was even available for rooted/custom folks. There will be a couple new apps installed, one dealing with CallerID which will force your 4G and WiFi to both be on - freezing that new app will fix that issue too, search the forums for details.
Click to expand...
Click to collapse
How are you surprised about the OTA being available for rooted phones? You don't make any sense with that comment as the update is just that an update. Verizon doesn't know which customers have rooted their device just that you have a device that needed to be updated.
Because thats the way it always was back when I had my original Incredible? A lot of people were surprised that the update was available to them, I'm not a minority here. No reason to be rude.
jmxc23 said:
How are you surprised about the OTA being available for rooted phones? You don't make any sense with that comment as the update is just that an update. Verizon doesn't know which customers have rooted their device just that you have a device that needed to be updated.
Click to expand...
Click to collapse
gozirra said:
Because thats the way it always was back when I had my original Incredible? A lot of people were surprised that the update was available to them, I'm not a minority here. No reason to be rude.
Click to expand...
Click to collapse
I am not being rude just stating the fact that Verizon doesn't know your phone is rooted in fact all companies don't know what you did to your phones until something bad happens to it. I will also add that the update will be pushed regardless if you're rooted or not the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.
jmxc23 said:
I am not being rude just stating the fact that Verizon doesn't know your phone is rooted in fact all companies don't know what you did to your phones until something bad happens to it. I will also add that the update will be pushed regardless if you're rooted or not the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.
Click to expand...
Click to collapse
Funny I did not see him mention anywhere that Verizon knew anything. His experience with a previous phone was that for some reason after rooting etc. his phone did not receive OTA updates. Whatever the reason, instead of being rude, you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".
ghostboa said:
Funny I did not see him mention anywhere that Verizon knew anything. His experience with a previous phone was that for some reason after rooting etc. his phone did not receive OTA updates. Whatever the reason, instead of being rude, you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".
Click to expand...
Click to collapse
Okay I have corrected myself like you have so eloquently posted I don't see the need to defend him if I already like you stated told him finally the reason. I already know that I should have done it sooner and like I normally do correctly fall back and respond in a normal tone. I unlike others am self aware of what I do and make an effort to correct any wrongs that I have caused. I don't filter myself when I post my thoughts so they can come across
as rude depending on your sensitivity level the difference is that I don't insult people nor belittle them in any way. I can only imagine how you or anyone will react if I was a total jackass.
ok then
Thanks for the explanation. follow-up question - if Verizon doesn't "know" then what is with the "unauthorized software discovered, call Verizon" popup that so many people have reported? Or the infamous yellow triangle? I assumed (yeah I know the cliche) that Verizon in fact DID "know" otherwise that wouldn't have happened. Simple mistake based on past experience, sorry.
As a side note.. If you have Titanium you can freeze SDM 1.0 and you won't get those updates
gozirra said:
Thanks for the explanation. follow-up question - if Verizon doesn't "know" then what is with the "unauthorized software discovered, call Verizon" popup that so many people have reported? Or the infamous yellow triangle? I assumed (yeah I know the cliche) that Verizon in fact DID "know" otherwise that wouldn't have happened. Simple mistake based on past experience, sorry.
Click to expand...
Click to collapse
This is completely unrelated to OTAs though. That warning is solely because of the secure bootloader on the Verizon GSIII. That warning is built into the system to pop up whenever you try installing software to the phone without having the prerelease bootloader in place. Verizon and Samsung intentionally made this model GSIII more difficult to install custom software onto or to make it a more secure device, depending on how you look at it. It's a business decision at the end of the day.
Sent from my SCH-I535 using Tapatalk 4 Beta
Probably business related as they don't want to be the first company to have an worldwide malware problem on their devices.
ghostboa said:
...you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".
Click to expand...
Click to collapse
That's the key (at least in my experience with HTC phones). I can't remember the name of the file, but it was one file that you could rename and the phone would not check or ignore OTA updates that were pushed by the carrier.
i downloaded the update the other day by mistake as it bricked my phone. im rooted only and stock. i know its going to keep forcing the update thru, is there anyway i can get the update to go thru successfully without bricking my phone again?
You didn't brick your phone at least not a hardware brick.
Related
http://www.androidpolice.com/2011/0...pdate-to-allow-sideloading-on-select-devices/
Here come the bricks. Will you go back to stock just for a sideloading ota update when you can do this on any custom rom?
Caution swyping! Read at your own risk.
According to 99% of the threads here on XDA, if you even look at your Cappy the wrong way you run the risk of bricking it. lol
cappysw10 said:
Here come the bricks. Will you go back to stock just for a sideloading ota update when you can do this on any custom rom?
Caution swyping! Read at your own risk.
Click to expand...
Click to collapse
KonaZXIII said:
According to 99% of the threads here on XDA, if you even look at your Cappy the wrong way you run the risk of bricking it. lol
Click to expand...
Click to collapse
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Will this be rolling out to Eclair users or just Froyo? And if you're on Eclair will this OTA include the Froyo upgrade? Anyone gotten this OTA yet?
umm...? if you receive OTA updates, you will already be OTA updatED to froyo. no?
so if you are still on eclair... umm.. wait!.. why would anyone still be on eclair?
oh... im scared of flash video and voice search... lol
TRusselo said:
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Click to expand...
Click to collapse
I was (mostly) being facetious there. I've been flashing and modding my phone for a while now and it has been next to impossible to hard brick.
well dont say stuff that can confuse the noobs please.
Anyone actually receive the update yet? Anyone who did, straight stock, rooted, any other notable differences?
Can we be connected via Wifi? Need to be on data network?
I just tried to see if it was available to me... nothing at 1pm in Atlanta
TRusselo said:
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Click to expand...
Click to collapse
AT&T could f#@% up a wet dream. This could also be a plot to void your warranty. "You loaded an unauthorized app which caused your trouble, not our problem. Oh, btw, we'll sell you an Infuse cheap."
Caution swyping! Read at your own risk.
Can at least one post in any forum I've looked at site a source or show something more believable then one crappy blurry pic of a random computer screen. Heck why is it not even the whole screen? What is that a pic of, other then something somebody made up who was not even good enough to use photoshop?
TRusselo said:
umm...? if you receive OTA updates, you will already be OTA updatED to froyo. no?
so if you are still on eclair... umm.. wait!.. why would anyone still be on eclair?
oh... im scared of flash video and voice search... lol
Click to expand...
Click to collapse
Froyo was never rolled out OTA was it? Thought it was a Kies update.
I'm helping my extremely tech-illiterate friend with her Captivate and I want to figure out exactly what the details are of the various updates so that I don't scare her with anything
I'm from I9000-land and I flash every couple of days But I'm a bit unfamiliar with the Captivate scene.
No they tried an OTA but it ended up bricking alot of devices due to no 3 button support. To be honest if it is not a kies update I would never touch it. To many things to go wrong with OTA. But we will see. It will most likely be 2.2 update
my question is would it cause any issues on a rooted stock froyo ?
I was just on-line with the Technical Support chat via the AT&T site and I asked the rep if she could confirm that this OTA update was even available. And she replied that she doesn't even see this update for the Captivate on her system. Not sure what's true or not...
I hope it's here in time for free plants vs. zombies, May 31st! I don't want my wife to have to pay. (I already have the Amazon Appstore on mine, of course).
ScottyNuttz said:
I hope it's here in time for free plants vs. zombies, May 31st! I don't want my wife to have to pay. (I already have the Amazon Appstore on mine, of course).
Click to expand...
Click to collapse
Just grab it from the Amazon website and then once AT&T allows sideloading you can install the appstore and then install the game on your phone.
At least ATT is going in the right direction, however, they need to update all their android phones to have hsupa also then having a stock phone is not so bad but I have been able to sideload with out using a computer since getting the phone enabling non market apps since the first day on my captivate *Launch date*. I have been using HSUPA ever since I started using Custom roms after the first froyo leak was released by DG.. So nothing to really effect me at all with this news, but it is good that any future phones released will have at least this enabled..
Cheers,
Charlie
dmnall said:
At least ATT is going in the right direction, however, they need to update all their android phones to have hsupa also then having a stock phone is not so bad but I have been able to sideload with out using a computer since getting the phone enabling non market apps since the first day on my captivate *Launch date*. I have been using HSUPA ever since I started using Custom roms after the first froyo leak was released by DG.. So nothing to really effect me at all with this news, but it is good that any future phones released will have at least this enabled..
Cheers,
Charlie
Click to expand...
Click to collapse
+1
they may be late to the party but at least they deserve a lil love for moving in the right direction and at least in one regard listening to their customers. Now if they would just be smart enough to realize/admit charging for tethering is a scam and recognize the marketing bonanza "Free to Tether" would be.
TRusselo said:
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Click to expand...
Click to collapse
Don't tell that to other members of the Galaxy S family. OTA updates have occasionally done worse.
Side loading
Apparently there is an update that has to be pushed to your phone from AT&T, but hardly anyone has received it yet. People in this thread are working on adding this feature without the update. This method will allow you to install non android market apps, but so far it disables your mms capability.
http://forum.xda-developers.com/showthread.php?t=1111278
Free tethering/wifi hotspot
http://forum.xda-developers.com/showthread.php?t=980591
By changing a few settings, you can have tethering/use wifi hotspot without adding a tethering plan from AT&T.
Maybe we could add future developments to this thread as they become available. I like the idea of leaving my phone stock so that it will automatically update.
Are you talking about the "silent" OTA that enables side-loading?
If so, and if by hardly anyone, you mean "hardly anyone here on XDA," it may be because they are rooted or otherwise running a custom ROM that will prevent them from getting OTA updates.
If you mean hardly anyone here on XDA that is bone stock, well, that might be true. And it also might be true that the recently discovered method of enabling sideloading will help some people, who don't mind their mms broken until some workaround fixes it.
Or they can root, and be done with it. There's nothing that will ever be OTA that I would want to get OTA anyway -- it will be available here shortly after.
The only excuse people have to not root is that it *appears* to be difficult. It really isn't. You can enjoy the same exact phone with a stock ROM, but with the added perks that rooting brings. Yes, that includes sideloading. And SIM unlock. And no more bloatware.
However, if this sideloading trick can be perfected, and it will keep people who otherwise don't have the patience to root their phones and as a result would just screw them up, causing them to further not spend the time to read and search, instead firing off 1000's of redundant "Halp Me!" posts, then that's a good thing.
ehh I would just rather use adb.... (if I was stock)
mudknot2005 said:
ehh I would just rather use adb.... (if I was stock)
Click to expand...
Click to collapse
Or that. My friggin' rant post from hell was long winded enough for me to forgo mentioning much more.
mudknot2005 said:
ehh I would just rather use adb.... (if I was stock)
Click to expand...
Click to collapse
Yeah, OP, you should definitely include a link to the adb method, or the Sideload Wonder Machine method.
I used SWM to install Swype weeks before I got the AT&T non market option (which was a week before I rooted).
ST3ALTHPSYCH0 said:
Yeah, OP, you should definitely include a link to the adb method, or the Sideload Wonder Machine method.
I used SWM to install Swype weeks before I got the AT&T non market option (which was a week before I rooted).
Click to expand...
Click to collapse
The adb method for sideloading an app is already discussed in mudknot's stickied guide.
Supposedly there is still an update floating around for unknown sources. If I happen to get my hands on it I will post it.
That's the only reason I haven't updated the side loading part of the guide. If the update gets pushed to every phone with in the month then it would be obsolete quick. I might add it just to have the most information possible... Though I will not put this method on there, because there is no reason you should have to give something up to gain something (captivate anyone?)..
Still stock here, without the non-market update.
No issues at all using the SWM. I didn't like that whole stupid "dropbox" method mentioned. It's easier and faster to just to use "disk drive" mode to copy the apk files onto the PC.
mudknot2005 said:
Supposedly there is still an update floating around for unknown sources. If I happen to get my hands on it I will post it.
That's the only reason I haven't updated the side loading part of the guide. If the update gets pushed to every phone with in the month then it would be obsolete quick. I might add it just to have the most information possible... Though I will not put this method on there, because there is no reason you should have to give something up to gain something (captivate anyone?)..
Click to expand...
Click to collapse
Absolutely agreed. Your guide should be reserved for known methods that provide the desired result without sacrificing other functionality.
I really don't see what all the excitement is about, regarding this new method. I mean, side loading has been a non-issue for rooted devices from the start, now it's *officially* a non-issue, even for bone stock devices.
This new method might have been a useful workaround for stock phones before ATT changed course on sideloading, now not so much.
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
It does not change ver. from 4.1.2
what does this updatedo?
What does this update do? Does it affect my root? Thanks!
It is notifying me too. Since I have twrp and root on stock jelly bean, how can I update if helpful, or turn off update notification?
Chad
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
AFwarbird said:
It is notifying me too. Since I have twrp and root on stock jelly bean, how can I update if helpful, or turn off update notification?
Chad
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Started getting the notification yesterday, but I'm also on stock Jelly Bean 4.1.2 and TWRP. I was able to stop the notifications by freezing "AT&T Sofware Update" with Titanium Backup, but I'd also like to know if there's anything here worth the trouble of trying to get it installed.
I just had a chat session with a Samsung official, and she said it's news to them. I told her that I am on I727UCMC1, and she said that my device is up to date. The small update AT&T is pushing must be something to do with AT&T.
Unless it updates my camera features, I'm not even bothering with it, and will keep AT&T Update frozen.
I'm pretty sure I'd have to backup everything, revert to stock UCMC1, cross my fingers and toes that it still doesn't brick my phone, and hope it still can be rooted the way I did before.
It sure would be nice if there was some sort of explanation as to what is being updated. I have looked all over and not found anything anywhere else that mentions this update to I727UCNJ1. I got the number from this an at&t website I would post the link but can't. It is only 12mb so probably not worth a bunch of trouble but I wish I knew what it is trying to update.
Paranoid?
Me too. Mine is original stock, but I upgraded the Android OS last year to 4.1.2 via Samsung Kies. However, mine is unlocked, and I can't help but be suspicious that AT&T is "updating" to do something that is to their benefit and not ours (i.e. relocking the phone?, spyware, etc.?), so it would be nice to have some details of what/why this unexpected update, before blindly agreeing to it. So, if anyone know what this update is all about, please share with us. Thanks very much!
My money's on an update that locks the phone down. What else would AT&T possibly do with a three-year-old platform that isn't making them any new money at this point?
I chatted with an AT&T representative yesterday, and all I could get out of her was that the update had to do with new features to the O/S. That's all the information that she could find, and couldn't tell me any specifics about what features were being updated.
I am about to go to an S5 or S5 Active soon, and I might just revert to stock to check it out.
It's pretty fishy though that neither Samsung, or AT&T has, or wants to divulge in any, information on exactly what it's going to do.
---------- Post added at 07:29 PM ---------- Previous post was at 07:26 PM ----------
As far as it locking your device back down, I have yet to flash, or install anything that has re-locked my phone. I guess it's possible. The only thing I'm worried about is losing root, and not being able to get it back with the last way that's available.
I see it's now listed on the AT&T eSupport website No details, just "Android OS Enhancements".
I don't have enough posts on this forum to be permitted to publish a link, but you can find it by Googling "AT&T Update to Skyrocket", and the eSupport link should be near the top of the results.
AT&T is taking the same tack as Verizon, and locking everything down. Even the mid to low end phones. So, I wouldn't be surprised if this is a way to lock older phones.
On the other hand, it really may be final bug fixes - a sort of final service pack. I wish I trusted them to give it a try.
I reverted back to stock I727UCMC1 using Odin v1.85, updated OTA to I727UCNJ1, flashed TWRP custom recovery, got root back, but I am not sure if I am still unlocked or not. I tried *#7465625# on the dialer, but the code does nothing.
Anyone know of another code to check the unlock status?
Thanks very much for your feedback. I've always just put a SIM card from another carrier into my phone. Even if it is not an active SIM, your phone should still tell you whether or not it is locked.
24fan4life said:
I reverted back to stock I727UCMC1 using Odin v1.85, updated OTA to I727UCNJ1, flashed TWRP custom recovery, got root back, but I am not sure if I am still unlocked or not. I tried *#7465625# on the dialer, but the code does nothing.
Anyone know of another code to check the unlock status?
Click to expand...
Click to collapse
unless u restored a previous efs partition that was locked to a carrier then u will remain unlocked, afaik no one lost their unlocked sim by restoring or flashing any firmwares, to read more about the sim lock or to unlock the sim read this http://forum.xda-developers.com/showthread.php?t=2638037
as for firmwares locking down the phone its referring to the way root is acheived not to the sim carrier lock
T.J. Bender said:
My money's on an update that locks the phone down. What else would AT&T possibly do with a three-year-old platform that isn't making them any new money at this point?
Click to expand...
Click to collapse
i hope you are joking, because if not then then you're insane. no offense intended.
Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices. Several devices started out unlocked, like the S2, and became locked by OTA updates. The S3, Note 2, etc.
IOW, I wouldn't put it past them, especially if Samsung wasn't aware of the update. On the flip side, the S2 is no longer even for sale, and I have to wonder how many are left in active service.
Clarification?
lingowistico said:
i hope you are joking, because if not then then you're insane. no offense intended.
Click to expand...
Click to collapse
Thanks, that was very helpful! Seriously though, as a senior member of this forum, perhaps you might have some constructive comments on this subject? After all, we're sitting here with phones (the I-727 SII Skyrocket is an oldie, but goodie!) that are trying to push an unanticipated OTA update on us, in a very suspicious manner. We hope it's just a bug fix, but don't trust the carrier (AT&T) to be doing this, unless they have some ulterior motive. The benefit of your substantial experience would be appreciated. Thanks in advance for any insight you can offer us.
Regards,
Ron M.
jshamlet said:
Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices. Several devices started out unlocked, like the S2, and became locked by OTA updates. The S3, Note 2, etc.
IOW, I wouldn't put it past them, especially if Samsung wasn't aware of the update. On the flip side, the S2 is no longer even for sale, and I have to wonder how many are left in active service.
Click to expand...
Click to collapse
Thank you for your insight, it was TRULY helpful! As a relative newbie, I just want to clarify our terms. When you use the term "unlocked", I deduce you are referring to a phone that has been rooted and is running a different platform - is that correct? In my case, I am NOT rooted and simply running the original crappy stock platform, but my phone is "unlocked" in the traditional sense, in that I can use it with different sims from different carriers throughout the world, rather than being "locked" to AT&T. So, for those of us who are not as technically advanced, could you please clarify? For me, if this OTA update doesn't prevent me from continuing to use other sims from other carriers, then I don't know what the downside would be, unless they're just adding more spyware and bloatware to their already intrusive system? I look forward to your comments.
Regards,
Ron M.
jshamlet said:
Not so insane, I'm afraid. AT&T has started a war on unlocked bootloaders lately. The CEO has officially come out as saying they don't want unlocked devices on their network, and have followed up by sending out OTA updates that lock down devices.
Click to expand...
Click to collapse
I thought T.J. Bender was talking about simlock since he didn't mention the bootloader. :silly:
At&t sure isn't making life easy for you.. I'd still be proudly rocking a skyrocket too if I didn't lose it :angel:
I only messed with my Skyrocket for an hour or so after accepting the OTA update, before starting up my new S 5 Active.
The only thing that I really noticed, was they took the AT&T phone setup app off of it, since it is no longer in use by AT&T. There may have been more that I didn't notice, but only running it a couple hours, I couldn't tell. I even checked the camera thinking they might have finally snuck some new features into it, but no dice.
lingowistico said:
i hope you are joking, because if not then then you're insane. no offense intended.
Click to expand...
Click to collapse
How does suggesting that AT&T would lock a bootloader make me insane?
Sent from my totally badass HTC One m8 using Tapatalk
I don't know how this'll go.......
So all my past android phones I have rooted + installed recoveries and what not. Originally I did this because I heard of a way to increase the battery life of my HTC Incredible via rooting. Afterwards I found myself rooting my Inc2, DNA, Inc4G, and my One M8. This time I did it so I can get the latest versions of Android/HTC Sense (until Google finally made a good looking UI w. 5.0).
Today (technically yesterday at this point) I bought the Pixel in hopes of finally being able to receive consistent android updates. That being said, the idea of being able to get consistent and relatively quick android updates was the whole point of me unlocking + rooting my phone.
I guess the question remains: Should I continue running unlocked with the Pixel, or will the updates from Google be enough?
dkris2020 said:
I guess the question remains: Should I continue running unlocked with the Pixel, or will the updates from Google be enough?
Click to expand...
Click to collapse
I like custom recoveries like TWRP because you can make nandroid backups. The downside of unlocking your bootloader is that Android Pay won't work and if someone gets ahold of your phone, like a thief, if the phone is unlocked then they can flash it and it will circumvent any protection on the device.
I like root because you can use apps that require root, like some Ad blockers and Titanium Backup, and because I can remove system apps I don't want on my phone.
It all depends on what you want to do with your phone.
Unless someone has a reason for unlocking the device, generally I don't see the point. There are some things that I want to do with my phone, which are easier to do unlocked, so personally I specifically wanted an unlockable phone. Depending on how much you've read about the Pixel, here are some things you may or may not know.
- Unlocking the device will wipe it, so if you decide later that you want to unlock it will wipe the phone.
- An unlocked stock device can still use the standard OTA updates.
- Some SuperSU users may be able to unroot and then use the standard OTA updates, and some rooted users have reported their phones automatically updating.
- After I started using root my phone fails to install the OTA updates, so I'd guess one of the checked areas on my phone has changed due to the root apps I've used.
- If the OTA notification shows up and the update will not install, with the stock ROM it's possible to burn through a lot of cellular data. When I didn't update my phone this month, it used about 1 GB before I shut off cellular data.
- Items like a computer, TWRP, or FlashFire are the sorts of alternate update routes for the stock ROM if a rooted phone cannot use the standard OTA.
alluringreality said:
some rooted users have reported their phones automatically updating..
Click to expand...
Click to collapse
Isn't there a way to disable the automatic updates?
LoliSmith said:
Isn't there a way to disable the automatic updates?
Click to expand...
Click to collapse
You can disable them in developer options. I've had my phone since early November (turned off system updates the day I got it) and have never been notified that an update is available. However, some have reported that they had system updates disabled in developer options and they still get notified an update is available. It seems to be hit and miss so I can't say for sure it would work for you or not.
Just addressing OPs concerns, unlocking your phone shouldn't have any impact on updates from Google. You can still get them, OTA or otherwise.
The only downside I'd say, are warranty related (unlocking the bootloader will void the warranty on Verizon models), and security. Google has pretty much decided that having an unlocked bootloader is not secure enough for Android pay, so you'll be without that (However, you can still use loaded gift cards/loyalty program cards. It's just credit/debit cards that won't work).
robocuff said:
You can disable them in developer options. I've had my phone since early November (turned off system updates the day I got it) and have never been notified that an update is available. However, some have reported that they had system updates disabled in developer options and they still get notified an update is available. It seems to be hit and miss so I can't say for sure it would work for you or not.
Click to expand...
Click to collapse
On my motorola phones, there was an app that you could freeze using titanium back up. I wonder if there is anything like that with the pixel?
---------- Post added at 12:28 PM ---------- Previous post was at 12:23 PM ----------
Soccerdude588 said:
The only downside I'd say, are warranty related (unlocking the bootloader will void the warranty on Verizon models),
Click to expand...
Click to collapse
First, that assumes that Google has a record of you unlocking your bootloader, which they may since jcase is saying that the phones have to communicate with the Google servers to unlock the bootloader.
Second, there is a federal law on this and the way it works in this situation is that if unlocking your bootloader is not related to the warranty claim, Google can't deny your claim. For instance, if the charging port fails that is entirely a hardware issue unrelated to unlocking your bootloader. Google must honor the warranty for that.
If you were to brick your device flashing, that would be different but Google would have to have some proof that you not only unlocked your bootloader but that it was the unlocked bootloader that resulted in a bricked phone.
robocuff said:
I've had my phone since early November (turned off system updates the day I got it) and have never been notified that an update is available.
Click to expand...
Click to collapse
Are you manually updating your device, or are you running months behind the current release? The reason I ask is that the OTA notices on my phone have been delayed my days or weeks from the initial release, but I think they have showed up eventually when I've stayed on a prior version and the developer option has been shut off.
LoliSmith said:
On my motorola phones, there was an app that you could freeze using titanium back up. I wonder if there is anything like that with the pixel?
Click to expand...
Click to collapse
I was hoping the following link might work similar to the Razr updater, but unfortunately the change kept my phone awake and didn't allow deep sleep both times I tried it. The update notification can be shut off by long pressing it, which I think shows up as a notification block. Due to the cellular data drain, my current plan is to try FlashFire for updates, and if that doesn't work well I'll probably try a ROM to avoid OTA updates.
https://www.androidexplained.com/pixel-hide-ota-notification/
alluringreality said:
Are you manually updating your device, or are you running months behind the current release? The reason I ask is that the OTA notices on my phone have been delayed my days or weeks from the initial release, but I think they have showed up eventually when I've stayed on a prior version and the developer option has been shut off.
Click to expand...
Click to collapse
I've been manually updating it. Usually within a week or so of the release. However, I skipped the January update all together and never got a notification about it. Maybe I got lucky. Don't know.
Thanks for the input guys.
So a lot of the stuff you guys are saying are things that I have had prior experience with so the actual process of unlocking I have no issues with. If unlocking the Pixel is anything like the Moto X Pure (which it should cause Google) it shouldn't be too much of a hassle.
That said I am with Verizon and I can say that in all of my years of owning rooted/unlocked HTC phones I only ever needed to use my warranty for hardware based claims. Like I said the main reason I unlocked/rooted was to get updated ROMs that Verizon/HTC wouldn't push out to the phone. I think I'll more than likely unlock it but I probably won't root unless I need to.
That's pretty much where I am. I did root, but a recent OTA update that I accidentally took unrooted me. Keeping the bootloader unlocked at least leaves that option available.