I got a notification this morning saying google play services wanted to update. I thought the google play services app itself was wanting to update, so I went ahead plugged in my watch and let it start.
As it turns out, it was the official update from AT&T to android wear 2.0! Finally! I already had android wear 2.0 on my watch, I flashed it using a kdz that someone had uploaded that had already gotten it on a w200L.
Anyway, once I realized what it was doing I was worried it might brick since I had already updated it previously to a different android wear 2.0 version.
I'm happy to report that it updated successfully. I still had stock recovery so that remained the same. I had used TWRP before, but only booted twrp recovery to flash supersu. I never flashed TWRP to my device, I'm not sure if having TWRP recovery installed would've caused the update to fail.
Changes: I lost root access. That is OK because I only rooted my watch so I could add a new APN to use my watch with a Freedompop sim card. Actually it was a good thing because before the update Android pay didn't work because of my root access, and after the update android pay allowed me to add a credit card and looks like it will work, since I no longer have root, even though my bootloader is still unlocked!
Anyways, I just thought I'd bring this up in case someone else has a question about it. My experience may differ from yours, I am not responsible if you have different results.
Related
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
Hey community,
after updating my 5.0 LTE 32 Shield Tablet some month ago and rooting it, I came to the conclusion that I don't really need root, but would like to continue receiving OTAs and have a device that just works.
Prio1:
Have a tablet with the latest updates installed.
Prio2:
As 1, but rooted.
I have made a apps+sysapps backup with Titanium.
What do you recommend as the next step?
Thank you very much.
All the best, Esshahn
Some additions:
1. I noticed I'm actually having 5.0 on my Shield. It's the 5.0.1 update plus the nVidia stuff that comes up all the time in the notification center.
I really just want to undo all root and whatnot actions and have a right out of the box experience on my Shield. I already did some stupid stuff (factory reset) and therefore lost my personal data anyway, so there's nothing to lose.
I noticed this forum isn't really active. If anyone doesn't know the answer, but could point me to the right forum for help that would be nice too.
Thank you
flash the full OTA through recovery: https://forums.geforce.com/default/...hread-released-2-17-15-/post/4464815/#4464815
then reinstall supersu through recovery, no factory reset needed
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Esshahn said:
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Click to expand...
Click to collapse
you can flash the full OTA through TWRP or CWM, no idea why it won't work with stock recovery though
the update supposedly fixes the graphics glitches that appear in various apps on update 2.1, that might be a good reason to update
Thank you!
Actually, since I didn't have CWM installed anymore, I just sideloaded the latest OTA, which worked nice.
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.
I had purchased my Shield brand new some years back from Gamestop when they were quietly being discontinued. Not only that, but the employee told me because of that, whatever remaining inventory each Gamestop had was being recalled back to Nvidia. There was only one left on my area so I bought it right away for $150 brand new . It came with Jellybean and I had only did one OTA update which brought it up to 4.4.2 KitKat. This past December I decided to finally unlock the bootloader (the warranty long ran out so I had nothing to lose) and root it afterwards. I followed this thread to unlock the bootloader and this post to gain root access. Both worked great :good:. I never bothered updating to Lollipop because it doesn't have Miracast and I like the dark theme of the KitKat version of Android better. I just looks nicer to me. So I was going to leave the OS as is since everything was functioning as I wanted it to.
However, starting this year, the Nvidia Shield hub app no longer works and has been replaced with a newer app called Nvidia Games. The thing is, it only works on Android 5.0 or higher . I have also seen people mention on Youtube that using that app, you can install Steam through it, which has a beta feature that starts it in Big Picture mode. This supposedly allows you to stream any Steam game without the need of an Nvidia card or the need of a PC . After reading that I wanted to update to Lollipop right away. This sounds to good to be true, but if it is, I will be ultra happy. :laugh:
I wanted to make a nandroid back up before updating, so I followed this thread to install the TRWP recovery. I was able to make a nandroid backup and restore it without issues. Then I rebooted and
went in the Shield settings menu to check for updates and it downloaded update 110. It said to restart and it would install, so I did. Initially it looks like the update was working. But then it gets stuck in a boot loop showing either the Nvidia Shield logo or the green Android guy with a panel open on it's chest. :crying:
I also tried installing the Lollipop update using the method described in this thread. It unfortunately didn't work.
Then I attempted through fastboot to flash stock stock recovery that I extracted from the OTA, but it fails saying: "(command write failed (No such device or address))"
So all my attempts to install Lollipop aren't working. Is it due to having root and the TWRP recovery installed and not the stock recovery?
Need some answers/help...
I was stock, rooted on 8.0....saw a pop-up box yesterday about OTA, didn't think much about since I thought being rooted wouldn't allow the OTA. Have seen the occasional pop-up over maybe the last couple weeks, but I don't normally restart my phone unless it starts to lag or freeze up/run slow. A restart usually fixed that. Was perfectly happy staying on 8.0. I did a shutdown on my phone this evening, and when I restarted it, bam, I'm unrooted on 10 now, specifically, QP1A.190711.020
The phone was bought from Google, unlocked in Oct 2017. I immediately unlocked bootloader and rooted at that time and have been running stock 8.0 since. TWRP and Magisk were used following instructions from the thread here on the forum.
No data was lost after the restart today and 10 seems to be running ok. I did download some data and pictures through my USB-c onto a flashdrive and it did seem to drain my battery FAST while doing it.
What I'd like to know now is how to get root back. I wouldn't mind staying on 10, but if I re-root, will another OTA break my root again? I haven't tried to do a shutdown and a restart again to see what would happen because I'm afraid my phone will brick.
I'm kind of a noob at this, and I don't always understand when you all get technical, but I can follow step-by-step instructions.
First off, how did an OTA actually get through, update and unroot my phone?
And second, can someone point me to step-by-step instructions to re-root my phone on 10, and how do I keep it from happening again?
Thanks for looking and I'd be very appreciative if someone could help me out.
Thank you.
Jim
same here
Same here.
I've got a retail (NON-Verizon) rooted, stock OG Pixel with 8.1 and I've been ignoring the nag to update to 10.
My wife has a retail (NON-Verizon) Pixel 2 that was also stock, rooted 8.1 except she just took the update and asked me about it later.
Both were done with TWRP and Magisk, albeit differing versions.
She's now unrooted at QP1A.191005.007.A1
TWRP v3.2.1-0-walleye is installed.
EDIT: TWRP seems to have been nuked by the OTA upgrade.
I just tried to reboot into TWRP recovery and it's gone.
Magisk Manager app version 5.4.0 (57) + "Latest Magisk Version: v16.0" (I'm pretty sure I rooted via v14.5(1456) though) are present.
"Update Magisk Manager" is nagging about updating /installing MagiskManager-v5.8.2
Root Checker Basic v6.4.6 is also installed.
I'm scared to death to update Magisk or attempt root without some guidance from you fine folks here.
Until then, I'll start having her backup everything she wants to keep in case things go sideways.
I didn't think I was the only one this happened to.
Ok...noticed another issue.
I had Titanium Backup Pro installed. I had several apps frozen before the forced upgrade to 10. Guess what? Those apps are listed as disabled in the app list with no button for re-enabling them. Titanium Backup Pro no longer works because I lost root with the forced update to 10, so I can't unfreeze with Titanium Backup.
Is there any way to unfreeze those apps without re-rooting? Not too sure I even want to attempt to root again.
Also, I haven't shutdown or restarted since the forced update. S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
fjm568 said:
S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
Click to expand...
Click to collapse
Correct.
As for "other issues", none that I, or she, have noticed.
Still breathlessly waiting to hear about how I go about re-rooting without data loss.