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] Droid Ultra/Maxx - Is there a way to root my device and unlock the bootloader?

Hello all!
I am using the Droid Ultra forum because I can't find or there doesn't seem to be one specifically for the Maxx. I assume they are they same phone but one just has a better battery.
I recently bought my new Droid Maxx using an upgrade. When it arrived, I tried using FoxFi for wifi tethering since LTE is faster than my house internet. I found out it won't work since I have the 4.4. To anybody that is curious, 4.4 came with my phone, I didn't use the OTA update.
After looking around on the internet, I am unable to find a guide that can root my phone. Has anybody made a bootstrap?
I am wondering if there is a way to root my phone with the 4.4 kitkat, whether 4.4 root method is still in development, or people have given up on trying to root it.
Something else. I tried to root my device with two programs, each have failed in the process. Kingo and OneClickRoot.

There is no working root for Android 4.4 on the Ultra/MAXX/Mini, you're stuck like everyone else.
There was "a Chinese guy" doing bootloader unlocks for ~$40 in the recent past few weeks but he/she/it has since stopped doing so (probably unable to access Motorola's database anymore or simply got caught doing it, who knows).
So again, you're stuck with stock 4.4 like everyone else is. The info is all over this subforum...

br0adband said:
There is no working root for Android 4.4 on the Ultra/MAXX/Mini, you're stuck like everyone else.
There was "a Chinese guy" doing bootloader unlocks for ~$40 in the recent past few weeks but he/she/it has since stopped doing so (probably unable to access Motorola's database anymore or simply got caught doing it, who knows).
So again, you're stuck with stock 4.4 like everyone else is. The info is all over this subforum...
Click to expand...
Click to collapse
Ah, that is quite unfortunate. I just needed to get caught up in the news. Thanks and I hope to see some root hacks soon.

Garret27 said:
Ah, that is quite unfortunate. I just needed to get caught up in the news. Thanks and I hope to see some root hacks soon.
Click to expand...
Click to collapse
You could try easy tether pro

I've been thinking. I was reading the forums quite abit recently. The Chinese guy might of had access to the Motorola database with the IMEI or he might have developed a serial-cracker. I remember using keygens to unlock copies of Microsoft Office along time ago. This guy might have done the same but kept it for himself to make a profit. I am wondering if we might see a keygen that uses a person's IMIE.
Just an idea I had.
Sent from my XT1080 using xda app-developers app

So for the sake of getting a more informed is this piece of crap ultra worth keeping in the hope of a root solution in the near future, or is anybody really even working on one?

It's a good phone that could be great (not as great as the MAXX 'cause of that battery life and no wireless charging) - I would say don't hold your breath for an unlock for the bootloader or even root nowadays, it's getting way too tough to root and bootloaders are pretty much... well, locked up I suppose. I don't know of any devs that are seriously working on the Droid devices anymore, it's kind of a crapshoot if you find one I guess.
IF I had gotten either of them before that "Chinese guy" stopped providing the bootloader unlock codes I may have developed a different opinion, but I missed that window of opportunity and so I decided holding onto those phones wasn't feasible given my requirements.
As I said in another post, I did like the MAXX and Mini when I owned them recently, but the fact that I wanted a bit more capability meaning root access because I use some apps that require it as well as the option of potentially using some customized ROM or doing customization that might require something like the Xposed framework means you're dead in the water with the Ultra/MAXX/Mini.
I sold both, picked up a Samsung Galaxy Express for $80 and it's unlocked (for T-Mobile, did that in 2 minutes), rooted and of course running CyanogenMod 11 aka Android 4.4.2 without a single issue so far except the camera FCs often but that's a well known bug that persists and likely will always be problematic (except on those new CyanogenMod phones I suppose since they're designed to run that OS 100% without problems).
The Ultra, the MAXX, and the Mini are damned nice devices if you like "pure stock" and pretty much zero chance of them ever being anything else - the fact that they're GSM unlocked from the factory is a plus, so is the wireless charging for the MAXX and Mini, but that's about it for me and not enough to keep them for the long haul.
Good luck...

Thank you very much for an honest opinion. Fortunately I just signed on with Verizon and received this phone only a couple of days ago and have the option of retuning it and canceling the service with only a minimal restocking fee to deal with. I guess I will have to exercise that option because root access to the device is critical for use at work.

SOSDD said:
Thank you very much for an honest opinion. Fortunately I just signed on with Verizon and received this phone only a couple of days ago and have the option of retuning it and canceling the service with only a minimal restocking fee to deal with. I guess I will have to exercise that option because root access to the device is critical for use at work.
Click to expand...
Click to collapse
Exchange for a gs5. It has root. As does the HTC one m8. The m8 looks well built. And the dot view case is sweet.
Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.

[Q] Just got Shield (32GB), It has 4.4.2, says OTA "1.21" available...

Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc

I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc

Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.

And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc

the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....

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.