Haven't seen anything about a March update. Aren't they released on the 1st Monday of the month?
samnada said:
Haven't seen anything about a March update. Aren't they released on the 1st Monday of the month?
Click to expand...
Click to collapse
Yo last month the update came on 5 february (tuesday)
it's live.
https://source.android.com/security/bulletin/pixel/2019-03-01.html
Updated and re-rooted the wife's Pixel 3 today. Magisk 18.1 with TWRP 3.2.3-0 (.img only). ElementalX 1.05 with EX Kernel Manager direct flash. All worked normally. Couldn't do my 3XL this month since I am on dotOS. I did have to clear cache and app data (hide with Magisk of course) to get Play Store to re-certify the device which then showed a Google Pay update. Even though they claim no security fixes, clearly there are some.
anthony_dumas said:
Yo last month the update came on 5 february (tuesday)
Click to expand...
Click to collapse
The Feb bulletin was published on Mon the 4th. Patch is dated the 5th. I had read they always patch on the first Mon, but apparently sometimes not quite. March bulletin is out, so good to go.
Guys, upon checking for updates, my phone seems to be stuck on "Preparing system update.." while the spinner just keeps going.. Any suggestions?
Prasad said:
Guys, upon checking for updates, my phone seems to be stuck on "Preparing system update.." while the spinner just keeps going.. Any suggestions?
Click to expand...
Click to collapse
I'm not sure you want to update at this time. I just did the update and now my screen has that weird green flash when ambient display is on. Might want to hold off if you can.
bobby janow said:
I'm not sure you want to update at this time. I just did the update and now my screen has that weird green flash when ambient display is on. Might want to hold off if you can.
Click to expand...
Click to collapse
Actually I just sideloaded it and all seems well! I'll keep an eye out for the aforementioned issue though.. thanks!
Personally, I'm not seeing a noticeable camera app loading time improvement..
Prasad said:
Actually I just sideloaded it and all seems well! I'll keep an eye out for the aforementioned issue though.. thanks!
Personally, I'm not seeing a noticeable camera app loading time improvement..
Click to expand...
Click to collapse
Just updated my wife's phone and it's not happening on hers yet. Some are saying it takes a little time. We'll see. Camera app was never an issue for me.
For those rooted with twrp, did you download the 1.7gb zip from Google and flash through fastboot, then reinstall twrp and magisk?
codygs83 said:
For those rooted with twrp, did you download the 1.7gb zip from Google and flash through fastboot, then reinstall twrp and magisk?
Click to expand...
Click to collapse
I just got my pixel 3 today. It had the January update installed on it. I downloaded the March factory image, removed the -w and flashed via fastboot and then unlocked bootloader and installed twrp and magisk 18.1 with no issues. I was not rooted before hand though being as the phone was brand new. Only issue is slow charging at the moment but I'm not sure if it was like that before the update since I rooted right away out of the box.
I have my pixel 3 rooted and TWRP installed. Can i flash the march ota.zip via TWRP and then install TWRP and magisk again? will that work?
Would love if someone could share their patched_boot.img please
Here Ya go (problem uploading
I tried to do the update yesterday (like i've done it the last 3 times before), but came into bootloops to the point, where i had to factory reset everything. After resetting and reflashing in fastboot, it would start again. Today I wanted to flash magisk 18.1 and went straight into bootloops again. So that seems to be the problem. How do I get the uninmod.zip from my phone to my computer? I tried the command push adb "file" "sdcard" but it gave me a "adb: error: failed to get feature set: no devices/emulators found"
thanks for your help!
Anybody else has problems with google pay on march update?
i got magisk 18.1 installed, magisk hide checked for g pay, cleaned cache and everything, but g pay still tells me phone is rooted.
any help appreciated.
Bluffer94 said:
Anybody else has problems with google pay on march update?
i got magisk 18.1 installed, magisk hide checked for g pay, cleaned cache and everything, but g pay still tells me phone is rooted.
any help appreciated.
Click to expand...
Click to collapse
GPay now seems to be reporting if your device in not showing as certified by Play Store. Hide Pay store, clear app cache and data for Play Store, and reopen it and check settings to see if it is certified. Did you get the new GPay the other day? That update didn't show immediately after the update because you needed to re-certify.
sliding_billy said:
GPay now seems to be reporting if your device in not showing as certified by Play Store. Hide Pay store, clear app cache and data for Play Store, and reopen it and check settings to see if it is certified. Did you get the new GPay the other day? That update didn't show immediately after the update because you needed to re-certify.
Click to expand...
Click to collapse
Play Store is certified. Google pay is up-to-date.
Gesendet von meinem Pixel 3 mit Tapatalk
Bluffer94 said:
Play Store is certified. Google pay is up-to-date.
Gesendet von meinem Pixel 3 mit Tapatalk
Click to expand...
Click to collapse
Is GPay reporting the root when you open the app or when you touch a terminal to pay? My wife's Pixel 3 (which I updated) is able to open GPay with no issue, but she hasn't used it at a terminal since the update. My 3XL is running a custom ROM, so it got the GPay update but not the March update. Mine also opens fine but I haven't used it at a terminal.
Related
I have a completely stock Nexus 9. My wife's Nexus 9 took Android 7 a couple of weeks ago. I was checking my today and noticed that mine is still sitting at the June 1, 2016 security patch level. When I check for a system update it says my system is up to date. I tried booting to recovery and clearing the cache, but it still isn't seeing the need to update. Is there anything else I can do to "clear" the system so it can realize there are a few security updates to install (and of course android 7)? I am just trying to avoid installing ADB and such to install it manually.
Thanks in advance.
Is yours an LTE, by any chance? N still isn't posted. The easiest for you to do at this point is join the beta, take the download/install, then, remove your tab from beta. As long as it installs nougat NRD90R , it won't wipe your device when you uninstall. In fact, even before, it wouldn't wipe your device unless you installed the 6.1 package Google would send after leaving nougat.
http://www.howtogeek.com/268299/how-to-upgrade-your-nexus-now-without-waiting-for-the-rollout/
Sent from my Nexus 5 using Tapatalk
It is the WiFi only version.
radcpuman said:
It is the WiFi only version.
Click to expand...
Click to collapse
To clarify when I said leave beta, I didn't mean uninstall but rather unregister your device from Beta program.. That would have been confusing.
Sent from my Nexus 9 using Tapatalk
has anyone lost root updating to current this month? i know my v10 became an ad filled, stock navbar, paper weight after it's last forced update.
I'm curious about this as well.
I finally got around to rooting my Stylo 3 Plus for the first time over the weekend, after closely following the developments in this forum for the past 6 months. It took a lot of trial and error and reflashing of TWRP before I got the timing down right, but I finally got it rooted (using Magisk 15.2).
And of course, luck would have it that within a few hours of my rooting success, a new system update notification (which I had never heard of until now!), pops up and asks me to restart to install it. I am using Titanium Backup to force stop the particular Google service involved, which makes the notification go away and I can reboot without it upgrading. But it always come back within 24 hours or so.
Has anyone installed this update yet (MP45010f) and successfully re-rooted? I'm currently using Magisk 15.2 with systemless hosts, Ad-Away, and Xposed with Greenify & MinMinGuard enabled. I would welcome any advice on how to proceed after the update to restore root and continue using Ad-Away, Xposed, etc. Or even how to disable the update notification for good so I can stay on MP45010e a while longer.
eliaslear said:
has anyone lost root updating to current this month?
Click to expand...
Click to collapse
I Installed the 10f update.
On the download page the date was listed as March something.
While updating with LG Bridge, it was listed as Feb 22.
After it was installed (update 10f for LGMP450) the security patch date was listed as Feb 01.
I rooted and installed TWRP (and removed RCTD). Everything seems fine.
I am reverting back to my old install. Because i have made a million little tweaks, that would take forever to redo on a new install. I just wanted to see if everything still works (and it appears it does).
PS - The first time i updated this phone (back around Oct2017) the LG Bridge erased my SD storage. This time it left all of my installed apps in place. Also, this appears to simply be a google security update. No firmware changes from LG.
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Esin8785 said:
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Click to expand...
Click to collapse
yeah thats what i did was revert back to stock so u can update then i update it then re rooted my phone
if you update using the LG Bridge computer program, it will update a rooted phone. but you will need to reroot afterward.
joetbd said:
I Installed the 10f update.
On the download page the date was listed as March something.
While updating with LG Bridge, it was listed as Feb 22.
After it was installed (update 10f for LGMP450) the security patch date was listed as Feb 01.
I rooted and installed TWRP (and removed RCTD). Everything seems fine.
I am reverting back to my old install. Because i have made a million little tweaks, that would take forever to redo on a new install. I just wanted to see if everything still works (and it appears it does).
PS - The first time i updated this phone (back around Oct2017) the LG Bridge erased my SD storage. This time it left all of my installed apps in place. Also, this appears to simply be a google security update. No firmware changes from LG.
Click to expand...
Click to collapse
Thanks for testing this out. If you don't mind me asking, which method do you use to root? And do you also use Xposed?
To anyone else who might know, does everything Magisk- or Xposed-related get removed by the security updates (frameworks, modules, configs, etc)? Just trying to get an idea how many of my modules I should expect to reinstall and configure from scratch if I decide to update from 10e to 10f.
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Esin8785 said:
I thought a system update wouldn't happen if youv done rooted your phone the only way back on the day was to reflash stock ROM to get the update
Click to expand...
Click to collapse
Yeah, I thought this was kind of weird too. I've never used LG Bridge to update. The notification just appeared on my phone shortly after rooting.
Is Xposed only for Magisk or can it be used on the rom, if so can I get a link to how to do so
LG Bridge
DM.IDOL said:
root?
Click to expand...
Click to collapse
Im using Magisk 16.1 (no Xposed) and TWRP 3.2.1
I have not run into any issues.
It appears to simply be a security patch update.
I doubt it should cause any new headaches.
The original method still works to reroot and reinstall TWRP.
Using the LG Bridge program is about as easy as an update can be. You install it on your computer, plug your phone into the computer, and click "update" on the computer program. Its all automatic.
I'm looking to update to the november update by using adb since my phone doesn't seem to be getting the update. It's an unlocked version from Google but I use it on Verizon. Do I need to download the verizon version of the update or just the generic?
download the google AND the verizon. Flash google, then verizon over it?
Krusej23 said:
I'm looking to update to the november update by using adb since my phone doesn't seem to be getting the update. It's an unlocked version from Google but I use it on Verizon. Do I need to download the verizon version of the update or just the generic?
Click to expand...
Click to collapse
Verizon version. I just did it, for some reason it's not getting pushed out. Same situation as you, Google device VZW provider.
Pachacouti said:
download the google AND the verizon. Flash google, then verizon over it?
Click to expand...
Click to collapse
There is no reason to do that.
Thanks, I just sideloaded the November update and it worked. It looks like it's a major issue for Verizon users and the Pixel 6 and some others at launch.
Krusej23 said:
Thanks, I just sideloaded the November update and it worked. It looks like it's a major issue for Verizon users and the Pixel 6 and some others at launch.
Click to expand...
Click to collapse
Yeah I saw that on Reddit.. Easy enough to do the side load until they figure it out.
Problem after updating. So now after updating using the verizon version of the update, it's losing the connection to verizon data, calls and sms. Any ideas?
Hi all, I've got this same issue (unlocked P6 being used on VZW unable to get the Nov security update). Seems like the official guidance is to sideload the VZW version (SD1A.210817.036.A8) and then you'll be on the VZW update path. However, I'm getting an error when trying to sideload. On my phone, it says:
Code:
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update package verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
I've verified that I'm using the correct file (oriole-sd1a.210817.036.a8-factory-65854912.zip) and verified the file with the SHA-256. Any suggestions for how I might fix this?
Krusej23 said:
Problem after updating. So now after updating using the verizon version of the update, it's losing the connection to verizon data, calls and sms. Any ideas?
Click to expand...
Click to collapse
Mine did that only once. Rebooted and it's never happened again. Also by sideloading the VZW version we should then get the OTAs moving forward from what I understand.
meberko said:
Hi all, I've got this same issue (unlocked P6 being used on VZW unable to get the Nov security update). Seems like the official guidance is to sideload the VZW version (SD1A.210817.036.A8) and then you'll be on the VZW update path. However, I'm getting an error when trying to sideload. On my phone, it says:
Code:
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update package verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
I've verified that I'm using the correct file (oriole-sd1a.210817.036.a8-factory-65854912.zip) and verified the file with the SHA-256. Any suggestions for how I might fix this?
Click to expand...
Click to collapse
Are you sure it's the correct file? That looks like the full factory image and not the OTA.
Krusej23 said:
Problem after updating. So now after updating using the verizon version of the update, it's losing the connection to verizon data, calls and sms. Any ideas?
Click to expand...
Click to collapse
So you lost network connectivity completely it seems. As per the previous poster reboot and it shouldn't happen again. Same thing happened here some days ago.
bobby janow said:
Are you sure it's the correct file? That looks like the full factory image and not the OTA.
Click to expand...
Click to collapse
-_- I'm an idiot, can you tell it's been a while since I sideloaded an OTA?
Thanks for pointing that out. Sideloaded the OTA no problem.
robn30 said:
Mine did that only once. Rebooted and it's never happened again. Also by sideloading the VZW version we should then get the OTAs moving forward from what I understand.
Click to expand...
Click to collapse
I rebooted multiple times, reseated the sim card and it was still doing it randomly. Took it to Verizon and they got me a new sim card. Seems to have fixed it now. Part of it was that it didn't look like it was fully activated either. I logged in MyVerizon and it still showed my 2XL as my phone instead of the 6.
Krusej23 said:
I rebooted multiple times, reseated the sim card and it was still doing it randomly. Took it to Verizon and they got me a new sim card. Seems to have fixed it now. Part of it was that it didn't look like it was fully activated either. I logged in MyVerizon and it still showed my 2XL as my phone instead of the 6.
Click to expand...
Click to collapse
Glad it's fixed. Faulty SIM was gonna be my next option. I thought that's what mine was gonna be but luckily the reboot seems to have squared it away.
So is everyone on Verizon with an unlocked phone from Google using the Verizon version of the OTA? I've been on a locked 3XL for almost three years, so it's taking me a bit to get used to things again. I've got root working perfectly and am afraid I'm going to mess it up when I sideload the OTA.
deercreek said:
So is everyone on Verizon with an unlocked phone from Google using the Verizon version of the OTA? I've been on a locked 3XL for almost three years, so it's taking me a bit to get used to things again. I've got root working perfectly and am afraid I'm going to mess it up when I sideload the OTA.
Click to expand...
Click to collapse
I used the Verizon version cause they are my carrier. I'm not rooted but I would imagine flashing the OTA via sideload would kill root. So would flashing the factory image via fastboot.
I recently received a message on my pixel 6 that a system update will be "automatically installed" on my device in 1 day. The update is 2.02 gb in size and it's listed as a "security update". Would this be the Android 13 OTA? I've disabled Automatic System Updates, but I'm afraid this will install and brick my phone/mess up my root. Is there anyway to prevent it from installing?
pleiotropy said:
I recently received a message on my pixel 6 that a system update will be "automatically installed" on my device in 1 day. The update is 2.02 gb in size and it's listed as a "security update". Would this be the Android 13 OTA? I've disabled Automatic System Updates, but I'm afraid this will install and brick my phone/mess up my root. Is there anyway to prevent it from installing?
Click to expand...
Click to collapse
That's the Android 12 GPS fix it sounds like.
Google Pixel 6 getting 'Introducing Android 12' update
Many Google Pixel 6 series users are confused due to an 'Introducing Android 12' update ahead of Android 13, here is what's happening.
piunikaweb.com
Lughnasadh said:
That's the Android 12 GPS fix it sounds like.
Click to expand...
Click to collapse
Thanks, any idea how to safely install the update? Is this Magisk guide still accurate?
OTAs are arguably the safest way to update regarding any danger to bricking devices. Any hoopla you may have heard about A13->A12 or A12->A13 bricking is via flashing not OTA updates. You will have to re-root/magisk. Those guides have been (should) updated for a13. But OTA updates within android 12 and to android 13 should not brick your device and should be totally safe. But once you are on android 13, you are on it forever. No downgrading. You can only move forward (for now).
Thanks, I am still quite new to this so to confirm, the A/B partition method will not work? Would I just install the OTA and then re-root? I'm using Magisk Canary 24.3 if that matters
pleiotropy said:
Thanks, any idea how to safely install the update? Is this Magisk guide still accurate?
Click to expand...
Click to collapse
Yeah, that guide is accurate but the "Install to Inactive Slot" method has been hit and miss for some. If you are on a custom kernel you also need to return to stock kernel to make it work as well.
pleiotropy said:
Thanks, I am still quite new to this so to confirm, the A/B partition method will not work? Would I just install the OTA and then re-root? I'm using Magisk Canary 24.3 if that matters
Click to expand...
Click to collapse
Canary 24.3 does matter, it won't work. You need Magisk 25.200 or higher for A13.
Cheers
Tom
tom1807 said:
Canary 24.3 does matter, it won't work. You need Magisk 25.200 or higher for A13.
Cheers
Tom
Click to expand...
Click to collapse
Good point. Missed that he was on that.
tom1807 said:
Canary 24.3 does matter, it won't work. You need Magisk 25.200 or higher for A13.
Cheers
Tom
Click to expand...
Click to collapse
Thanks for the info, I will update Magisk and then try it
pleiotropy said:
Thanks for the info, I will update Magisk and then try it
Click to expand...
Click to collapse
Make sure to disable any Magisk mods that may need updating as well, but since you're just making a minor update from one July build to another July build I suspect you'll be ok. But it's still good practice to disable mods when updating to avoid potential bootloops.
Hi,
I have the same issue (system security update 2.02 GB) bothering me everyday and I do not want to update my phone. I am rooted but am not sure what Titanium backup should freeze to stop this. Any ideas? I appreciate it. I do not want to have to re root etc, it took me months to successfully root .
pleiotropy said:
I recently received a message on my pixel 6 that a system update will be "automatically installed" on my device in 1 day. The update is 2.02 gb in size and it's listed as a "security update". Would this be the Android 13 OTA? I've disabled Automatic System Updates, but I'm afraid this will install and brick my phone/mess up my root. Is there anyway to prevent it from installing?
Click to expand...
Click to collapse
michaelrager said:
Hi,
I have the same issue (system security update 2.02 GB) bothering me everyday and I do not want to update my phone. I am rooted but am not sure what Titanium backup should freeze to stop this. Any ideas? I appreciate it. I do not want to have to re root etc, it took me months to successfully root .
Click to expand...
Click to collapse
Did you ever figure this out? Or what happened? I have updates disabled under dev but I got the same notification.
If anyone can respond, I just have root with systemless host enabled for adblocking. If the update goes through, worst case I just have to reroot?
tbgakaadan said:
If anyone can respond, I just have root with systemless host enabled for adblocking. If the update goes through, worst case I just have to reroot?
Click to expand...
Click to collapse
Take the update. You'll have to root again.
I am rooted with Magisk and running the Raviole kernel. My Play System will not update past July no matter what I do. I delete all but one account on my phone and followed those instructions and still nothing. I have a 24MB update available and I've tried 20 times to download and install it but on reboot I just have the same level still. Anyone have a similar issue or know of a workaround? I even did a factory image install with the update to A13...twice.
I got on September 14(!) also the 24MB update, but then it showed I am now on August patch level.
Maybe it has something to do with your kernel?
Cheers
I checked on the kernel and that shouldn’t be the issue. I don’t know if Magisk would have any effect on it. I’m kind of out of ideas for the time being.
stock unrooted, and I just got the August Play system update yesterday. Prior to that I got 3 updates that were all dated July.
have you tried installing the apk from apkmirror ?
Fytdyh said:
have you tried installing the apk from apkmirror ?
Click to expand...
Click to collapse
The apk is only a "visual" update and only displays August update, too small for the complete PlaySystem Update.
But some reported after installing, it triggered something and after a while the "real" system update was downloaded and installed.
Cheers