My wife and I both have a G1. I have had mine rooted for a week or so, updated to RC33 yesterday, and I rooted my wife's phone and updated last night...
Well, my wife's G1, after a reboot, gets to the Android screen (after 'T-Mobile G1' screen), and the android flashes. So I put her back to RC29 till I can get it figured out.
Just now, mine suddenly rebooted and is doing the same. There are no corrupt files, all were fresh. Install and root were followed step by step......HELP!
rc33
I would recommend wiping then go back to rc29 and then update from their to rc33 hope that helps
Did you have themes installed??
If yes, are they for RC-33?
You can not use any theme you like with RC-33.
An idea.
I have a dev phone with the most recent jf update. My phone is prompting me to update with a holiday update or something like that. Do I need to do that? Or will it screw with jf update?
Thanks
***Update*** Its prompting me like every 15 minutes. Its driving me crazy!
either allow the update or get JF's 1.43
I went ahead and downloaded the OTA update, and I no longer have JFv1.41. Which is fine with me, since I have a dev1. I didnt use the multitouch or the auto-rotate anyway. As long as I have root, and tethering, im a happy man!
My wife's M8 is stock rooted. (Mine is happily running ViperOne )
She got the notification for the OTA update, and accepted. The phone rebooted into CWM, and the update failed. The phone came back up just fine, however.
How do I either get the update to install or get the OTA notification to stop popping up?
i imagine this has been answered a billion times, but I seem to only be able to find links related to other ROMs and the OTA.
Thanks
Looks like I got it done with this:
https://www.youtube.com/watch?v=e21qb7iZAOo&feature=youtube&app=desktop
and this:
http://forum.xda-developers.com/showthread.php?t=2723159
Woke up to this on my phone this morning. Is it worth updating and does it bring any harm to chances of rooting?
allways worth updating.
i updated yesterday and used cf autoroot today first time. works.
Did you by any chance catch the update?
Because when you're rooted you can't update the official way anymore.
As i said before - read again:
Updated yesterday - rooted today.
Just checked mine now, the update appeared. Installing now.
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.