i dont have the OTA on the TB i just got today, when i go to Updates it says looking, then it does nothing. i have only tried it on 3g, do i have ot check it under WIFI instead?
thanks
dvigue said:
i dont have the OTA on the TB i just got today, when i go to Updates it says looking, then it does nothing. i have only tried it on 3g, do i have ot check it under WIFI instead?
thanks
Click to expand...
Click to collapse
If you plan on rooting, then don't bother with the OTA. You'll have to wipe the phone while rooting, then update to the latest. If you don't plan on rooting, then the OTA should show up when tell it to check. What version does it currently say you are running?
Even if you don't plan on rooting, I still wouldn't update. Otherwise you may end up frustrated with reboots.
I got my TB back in May. Didn't have one issue until I did the update. Since I only had the phone for 11 days VZW told me to walk into a store and exchange for a new one. I have had no issues with the new phone and will stay clear of that update. Wait until GB comes out and hopefully that will fix what ever is wrong.
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
NevetsDrassel said:
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
Click to expand...
Click to collapse
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Jank4AU said:
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Click to expand...
Click to collapse
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
NevetsDrassel said:
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
Click to expand...
Click to collapse
I don't know how to permanently disable the update, but I'm sure there's a way. As info, I was able to easily fix my phone with the help of this thread posted by @thecubed: http://forum.xda-developers.com/showthread.php?t=2451696. I didn't read it all, but this might be what disables the update.
I'm not rooted. I took the latest update and all is fine. It's google+ fixes and Google wallet support. It actually let me set up tap & pay! I'll have to go somewhere to try it out.
Sent from my LG-D800 using Tapatalk
I got the notification too but figured that it would probably screw things up since I'm rooted and running TWRP so I did a little searching and came across this, http://forum.xda-developers.com/showpost.php?p=50454408&postcount=3 . It's been a few hours since I changed the setting and haven't seen the update notification again although AT&T pushed the update into CACHE/FOTA sometime this morning.
Well scratch that, the notification just came back. I'll try freezing it now.
Well if rooted just use TB to freeze software update. I am also running a mixed partition D80020c. I am on Straight Talk AT&T. Before rooting I tried taking the official OTA of KitKat but for some reason you can't enter an APN type so I couldn't get or send MMS. So I flashed back to the D firmware,rooted,added custom recovery,entered the APN type and then flashed the modified C firmware. You could also use Root Freezer instead of Titanium Backup to freeze
Hi. Bit of a noob so bare with me.
Got the phone and it got the kitkat upgrade straight away. Then I unlocked the bootloader through the Moto site. All fine and well.
But for the past month there has been a new update which refuses to install. Did a recovery. Did a factory reset. Did a cache clean thing. In fact, did all possibilities. It will still not update. It did get the new Moto startup screen no bother, which was odd.
Should I flash new firmware onto the phone and would this take care of this update problem?
Thanks
OK. So I have flashed back to stock many times and taken the LP OTA. Never had an issue. Just started up first run went through it and hit update when I was ready. Instant OTA showing available for download. Now since I restored to stock again and and now the OTA will not show. Tried the return to stock several times and ATT shows no issue with their update service. Even though I am on Straight Talk and not AT&T they were nice enough to try and work through the problem without success.
Just wondering if anyone else has run into not getting the OTA suddenly and had taken it before.
Thanks.
I have a Pixel 2 with the bluetooth connection issues. When I go look for the Google Security Updates, it says that I am up-to-date. I did a factory reset and tried to get the update afterwards, but it has the same issue where it is not finding the update.
Has anyone successfully been able to find a way to get the phone to find the updates, or should I get a hold of Google to return the phone?
Thanks,
Mark
I have also not received the November security update, every time I check it says it is up to date. I bought the unlocked version from the Google Store and am using Verizon.
This reddit thread shows a way to potentially force it, i have not tried it yet -- https://www.reddit.com/r/GooglePixe..._on_september_security_patch_regular_pixel_2/
UPDATE: I have tried it, and it did not work
I also tried it and it didn't work. I would be more patient, but the Bluetooth issue is quite frustrating. I'll give it a few more days then will contact Google again for a replacement device.
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
thesebastian said:
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
Click to expand...
Click to collapse
Are the ones marked Verizon for the Verizon version, or also for people who bought the unlocked version and are using Verizon? My current version is OPD1.170816.010, which is not a Verizon version, so I guess I would want OPD1.170816.025 since the version I currently have is not the Verizon version? Still find it crazy that an update would come this late, never got them this late on my 5X. I never understood the point of if I manually check I cant just auto get the OTA (I know there was that article somewhat recently that they are moving to that though).
I got 023 over the air automatically on my Pixel 2. Haven't downloaded the OTA from the developer site some I got this phone.
OPD3.170816.023, Nov 2017, Verizon
I too bought unlocked from Google but using on Verizon. I was on .10 and waited weeks after release for a push, but it never came. So I manually flashed the .25 update. No issues, working perfectly, with the Nov security update.
I am still on september security update. Got a Pixel 2 (Verizon). Hope they hurry up. Its almost december
Sorry to bring up an old thread, but I have the same problem ever since I cleared the Google Play Services' data through the app's interface. The OTAs just stopped coming. I have been flashing full OTA images since August, but it is getting really annoying. I still didn't get the November's patch, nor the December's one. It always says my system is up to date. I didn't try clearing the Play Services Framework's data, as it isn't effective and only causes trouble. I tried clearing the Play Services' data though many times, but it doesn't help.
I am rooted with Magisk. Everything else is fully stock (rom, kernel, recovery) and I do pass the Safety Net test.
If anyone has a solution to this problem, please share it with the world. I don't believe that I am the only one with this problem.
Same here, rooted pixel 2, currently away from pc so would love to update from phone
Sent from my Pixel 2 using Tapatalk
I've had the same problem with my P2XL for the last couple of month. I have just been downloading the full updated firmware and flashing from my computer, but it would be nice to be able to update while travelling with no computer.
Details:
-Magisk rooted, everything else stock, including recovery.
-Google edition - I used to get updates, not sure what changed.
-Not on beta. I even tried signing up and then unsubscribing. No help.
-"Check for update" button does nothing.
-Clearing data on Google Services Framework doesn't help.
-I'm in Mexico on Telcel, but updates have worked in the past.
Haven't been receiving OTA updates since flashing the Pie factory image in August.
Device is stock apart from being rooted with Magisk.
Update button always says system is up to date, so I eventually sideloaded the latest OTA image at the end of November but still didn't receive any update notification in December.
I'm starting to suspect the update manager in Pie is detecting root or something, because I used to receive updates just fine on Oreo, and everyone else who has this problem also seems to be rooted.