Database Info

OTA Available after activation

Did anyone besides be get notified of an OTA after they activated their T-Bolt? Did you install it? I didn't for fear it will ruin our current root exploit even though it's not permaroot.

I didn't get it yet, I wish I did though, don't want anything to be wrong if I can't get OTA updates. Hopefully I'll get it later today.
Update: Tried to manually update, phone said I had the latest software.

you can go to settings and check for update.
Crap i just did it again and now it says i don't have one.

I have not been notified but I was told to expect one in the next few days. I was told it contains the fixes for battery life issues.
Sent from my Xoom using Tapatalk

[Q] Verizon OTA Update - 5/30/13

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.

[Q] 4.3 to 4.4.2 rooting questions worth it or no?

Hi all,
Recently my unrooted Verizon S3 4.1.2 phone updated seemingly on it's own to 4.3 after I had been deferring the updates for over well over a year. Needless to say I was extremely pissed and ended up rooting my phone with Towelroot in order to regain some of the features I had lost in the update (auto toggling Airplane mode). One issue that I noticed right away and apparently can't be fixed even with root in 4.3 is that when the phone is set to vibrate (silent mode) EVERY notification will trigger a vibration. App level settings are ignored. Google added new ****ty notification code that ignored app level settings and forced global settings no matter what, only in silent mode though. This is pretty much the only thing I can't stand about 4.3. So naturally I looked into 4.4's notification system and sure enough this seems to have been fixed in 4.4.2 as I've tested it on my g/fs phone and I've reviewed the Android NotificationManagerService source code. So I was planning to unroot my phone and upgrade to 4.4.2 but I keep hearing people say how they wish they stayed with 4.3 or how much of a task it is to unroot. I'm a noob to rooting so I'm a little worried.
So my questions are.
1) Why is it not a good idea to upgrade to 4.4.2? I'm on Verizon so my bootloader is already locked forever .
2) If I was going to upgrade how would I go about unrooting my phone? I used Towelroot. Is there a simple one press unroot app ha ha?
3) If upgrading is a bad idea then does anyone know of any app that allows me to mess with notification vibrations. I want to go back to the old notification system were I can set the phone to vibrate but only have phone calls and text messages. Emails and everything else should just trigger the LED notification.
4) Will I even be able to root 4.4.2? I keep reading mixed answers on the forums.
Thanks in advanced!

DeathfireD said:
Hi all,
Recently my unrooted Verizon S3 4.1.2 phone updated seemingly on it's own to 4.3 after I had been deferring the updates for over well over a year. Needless to say I was extremely pissed and ended up rooting my phone with Towelroot in order to regain some of the features I had lost in the update (auto toggling Airplane mode). One issue that I noticed right away and apparently can't be fixed even with root in 4.3 is that when the phone is set to vibrate (silent mode) EVERY notification will trigger a vibration. App level settings are ignored. Google added new ****ty notification code that ignored app level settings and forced global settings no matter what, only in silent mode though. This is pretty much the only thing I can't stand about 4.3. So naturally I looked into 4.4's notification system and sure enough this seems to have been fixed in 4.4.2 as I've tested it on my g/fs phone and I've reviewed the Android NotificationManagerService source code. So I was planning to unroot my phone and upgrade to 4.4.2 but I keep hearing people say how they wish they stayed with 4.3 or how much of a task it is to unroot. I'm a noob to rooting so I'm a little worried.
So my questions are.
1) Why is it not a good idea to upgrade to 4.4.2? I'm on Verizon so my bootloader is already locked forever .
2) If I was going to upgrade how would I go about unrooting my phone? I used Towelroot. Is there a simple one press unroot app ha ha?
3) If upgrading is a bad idea then does anyone know of any app that allows me to mess with notification vibrations. I want to go back to the old notification system were I can set the phone to vibrate but only have phone calls and text messages. Emails and everything else should just trigger the LED notification.
4) Will I even be able to root 4.4.2? I keep reading mixed answers on the forums.
Thanks in advanced!
Click to expand...
Click to collapse
Are you using supersu for your superuser app? If so it has a built in unroot option
As far as taking the OTA to 4.4.2 it's best to read around the forums for information on that. I personally am on an unlocked bootloader so I really can't comment on this too much
Some people have been successful on rooting the 4.4.2 update and some have not, I would say your results may vary
Unsure about the notification part
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

ShapesBlue said:
Are you using supersu for your superuser app? If so it has a built in unroot option
As far as taking the OTA to 4.4.2 it's best to read around the forums for information on that. I personally am on an unlocked bootloader so I really can't comment on this too much
Some people have been successful on rooting the 4.4.2 update and some have not, I would say your results may vary
Unsure about the notification part
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Yes, I used towelroot and then installed superSU. I did notice the unroot feature in superSU but wasn't sure if it would work since I rooted my phone using towelroot. Not sure if the process is different or not.
I've been reading a lot about 4.4.2 and it does seem like it's a 50/50 chance towelroot will work on it...which is why I made this thread. Some people are saying that it doesn't work if the update has a date after July 2013 and others are saying it still works. I was hoping someone could chime in with a backup process for rooting just in case Towelroot didn't work. I don't really like the odds right now so it looks like I'm sticking with 4.3 and the annoying notifications until a full proof method shows up.

DeathfireD said:
Yes, I used towelroot and then installed superSU. I did notice the unroot feature in superSU but wasn't sure if it would work since I rooted my phone using towelroot. Not sure if the process is different or not.
I've been reading a lot about 4.4.2 and it does seem like it's a 50/50 chance towelroot will work on it...which is why I made this thread. Some people are saying that it doesn't work if the update has a date after July 2013 and others are saying it still works. I was hoping someone could chime in with a backup process for rooting just in case Towelroot didn't work. I don't really like the odds right now so it looks like I'm sticking with 4.3 and the annoying notifications until a full proof method shows up.
Click to expand...
Click to collapse
I truly can't say I blame you. I wouldn't either unless it was full proof also
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

Should I Unlock my Bootloader?

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.

Should I update?

Nothing is broke, I dont see why I should update. I've learned my lesson about updating when everything is working fine. I'm on Tmobile with an unlocked N10+.

Updates are more likely to bring improvements than problems. And without updates, you have no protection from newly discovered security vulnerabilities. So I'd recommend updating unless you're ok with the possibility of someone remotely and covertly taking over your phone.