Database Users

last update (October security patch) is out

Last build for shamu (N6F27M) is available :
https://developers.google.com/android/ota#shamu

I'm out of the office today, anyone want to let me know if there's a new radio or bootloader?
Sent from my Glade[emoji768] Plugins

SynisterWolf said:
I'm out of the office today, anyone want to let me know if there's a new radio or bootloader?
Click to expand...
Click to collapse
Looks like bootloader is the same but there's a new radio, at least for Verizon.

ota received

So long and thanks for all the fish...
This is probably the last official update for our Nexus 6.

Anyone facing this problem?

rishabh1500 said:
Anyone facing this problem?
Click to expand...
Click to collapse
Worked fine for me. If you have modded your rom, then OTA will often fail.

I've been sideloading the OTA updates for months. Since Google made the check for updates function actually do something, thought I would go that route this time. It worked and immediately offered me an update. How can I verify that it's going to install NGI77B and not N6F27M? I'm on Verizon and currently on NGI55D.
I tried capturing a bug report and looking for the OTA link in the file but am not finding it. Maybe I should just sideload it.

HankStorm said:
I've been sideloading the OTA updates for months. Since Google made the check for updates function actually do something, thought I would go that route this time. It worked and immediately offered me an update.
Click to expand...
Click to collapse
same for me
HankStorm said:
How can I verify that it's going to install NGI77B and not N6F27M? I'm on Verizon and currently on NGI55D.
I tried capturing a bug report and looking for the OTA link in the file but am not finding it. Maybe I should just sideload it.
Click to expand...
Click to collapse
I guess that if your Verizon sim is in it, the "right" ota will automatically be downloaded

Now that the final patch has been issued what & when would make you all move over to a custom rom?

iluvatrix said:
Now that the final patch has been issued what & when would make you all move over to a custom rom?
Click to expand...
Click to collapse
next month I will try LOS

T-mo users, looks like we will never get an automatic update. Have you side-loaded the latest 7.1.1? Any issues?

Note10.1Dude said:
T-mo users, looks like we will never get an automatic update. Have you side-loaded the latest 7.1.1? Any issues?
Click to expand...
Click to collapse
Using T-mobile network via Ting - no issues seen so far with the sideloaded Oct 2017 OTA update.

iluvatrix said:
Now that the final patch has been issued what & when would make you all move over to a custom rom?
Click to expand...
Click to collapse
I bought N6 in October last year and have been using custom ROMs on it since day one.
First PureNexus and now currently DirtyUnicorns.
I plan on moving to LOS once nightlies start rolling out.

LOS == Lineage OS?

java007 said:
jNote10.1Dude said:
Using T-mobile network via Ting - no issues seen so far with the sideloaded Oct 2017 OTA update.
Click to expand...
Click to collapse
Using T-mobile network via Ting - no issues seen so far with the sideloaded Oct 2017 OTA update.
Click to expand...
Click to collapse
I was getting monthly security update notifications on my Nexus 6 while using Verizon, however that stopped since moving to T-Mobile in April/2017.
I'm staying stock for now, because it seems easiest to maintain Android Pay, Snapchat compatibility, etc.
Does anyone have a recommendation on which build to use if I sideload? Would that be "N6F27M" since the other October release states "Verizon" ?
EDIT: I went ahead and sideloaded N6F27M, which seems to be working fine with T-Mobile thus far.
- ooofest

Does N6F27M include security patch against new hole in WPA ?

No, it will be in November security patch but it's not sure that Nexus 6 will receive it...

I'm on Fi but my phone doesn't give me the opportunity to update N6F27M, it does not show that there is an OTA available.
Could it be that the phone was a Verizon overstock which I flashed to NGI55D manually when I first bought it?
I suppose I will have to sideload the OTA.
Edit: Never mind, it finally came through.

November security patch is out for pixel and 2015 nexus, no new build for our good old Shamu so we will have to keep it with Krack security breach or install custom rom...

December images up

I just noticed December's images are up for og pixel xl and pixel

Zehlek said:
I just noticed December's images are up for og pixel xl and pixel
Click to expand...
Click to collapse
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.

Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?

Archangel said:
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Click to expand...
Click to collapse
Just the new search bar with the Google Assistant link and drawing program hidden in the Easter Egg.

jaytv said:
Just the new search bar with the Google Assistant link and drawing program hidden in the Easter Egg.
Click to expand...
Click to collapse
I heard for other devices (Pixel 2) the UI (At least on the home screen) has been much more fluid with the updated Pixel launcher. I would agree with this on the Pixel XL too now...I have far less stutters using navigation gestures and swiping right to go to the Discover feed. Good update!

This is really random, but after updating anyone else having an issue with the screen turning off when a right to far left of the screen is performed? Noticed it when I was swiping a word from far right of the screen to far left, and it turns the screen off. Does the same thing outside of the app. Checked the Gestures settings and couldn't find anything relevant. (Wiped data on upgrade) Any suggestions are appreciated!

chinesecooler said:
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Click to expand...
Click to collapse
I'm not 100% sure I would ask @razorloves he is the expert on this one

chinesecooler said:
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Click to expand...
Click to collapse
doubt it. you need the kernel too (boot.img). then you'd need to reflash twrp and magisk.
you also need new radio & bootloader img's.
what's so hard about re-rooting? you just have to flash twrp and magisk, right?

razorloves said:
doubt it. you need the kernel too (boot.img). then you'd need to reflash twrp and magisk.
you also need new radio & bootloader img's.
what's so hard about re-rooting? you just have to flash twrp and magisk, right?
Click to expand...
Click to collapse
Yeah figured that out. Initially I just flashed the two and it boot looped. Had to do the lot and reroot. :/

Archangel said:
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Click to expand...
Click to collapse
Before the update, I had to manually enter my apn, but After December update, all my apn automatically work. I noticed better signal reception too. I don't know if it's the update related.

I liked it,
Rebooted after initial setup and fastbooted into twrp...
Installed king kernel 3.16
Installed magisk.
Perfection, battery lasts forever now. 5.5h sot is an daily thing, 3.5-4h if streaming pandora

April 2019 - Pixel Update

There are no Pixel security patches in the April 2019 Pixel Update Bulletin.
There are no Pixel 2/ Pixel 2 XL related patches.
Pixel 3, Pixel 3 XL
1. A-119823747 A - 120135659 - Assistant
Improves Voice-Unlocking performance for Google Assistant
2. A-122883482 - Setup
Adjust Wi-Fi connectivity during eSIM activation on certain carriers
3. A-119327025 - Display
Removes screen flash when ambient display wakes for some
Pixel, Pixel XL
1. A-119109648 - Bluetooth
Improves Bluetooth connectivity on Pixel devices
Source: https://source.android.com/security/bulletin/pixel/2019-04-01.html

What that's disappointing????? Damn are we the forgotten one?

That's not true. right now i've got an ota update on my pixel 2 xl april security patch. they just didn't add any improvements maybe that's why pixel 2 was not mentions there.

astaineakash said:
That's not true. right now i've got an ota update on my pixel 2 xl april security patch. they just didn't add any improvements maybe that's why pixel 2 was not mentions there.
Click to expand...
Click to collapse
Yes. Pixel 2 will get all the security updates every month and OS versions until October 2020. This patch contains all the security patches from the AOSP line.
Source: https://source.android.com/security/bulletin/2019-04-01
So we got many security updates but no Pixel specific.
Our device now working perfectly. According to Google.

Some has managed to root again with Magisk after april manual update?

failax said:
Some has managed to root again with Magisk after april manual update?
Click to expand...
Click to collapse
No problem at all with magisk 19.0 beta :good:

Badger50 said:
No problem at all with magisk 19.0 beta :good:
Click to expand...
Click to collapse
I'm on Pie, i downloaded the ota zip and flashed on device, all ok, but i lost root, so i tried to patch img.boot again and pull to the device.Result is Android remains stuck at middle.I pulled the boot.img again and the os starts, but with no root.

failax said:
I'm on Pie, i downloaded the ota zip and flashed on device, all ok, but i lost root, so i tried to patch img.boot again and pull to the device.Result is Android remains stuck at middle.I pulled the boot.img again and the os starts, but with no root.
Click to expand...
Click to collapse
Then just fastboot into twrp and flash the magisk zip from there. It's what I do every month after fastbooting the factory image :good:

Badger50 said:
Then just fastboot into twrp and flash the magisk zip from there. It's what I do every month after fastbooting the factory image :good:
Click to expand...
Click to collapse
I've not installed TWRP, it is necessary?

failax said:
I've not installed TWRP, it is necessary?
Click to expand...
Click to collapse
Not necessary, but makes things a lot easier if you ask me. Hasn't caused me any grief since the August 2018 release :good::good:

failax said:
I've not installed TWRP, it is necessary?
Click to expand...
Click to collapse
No need to install TWRP, just plug in the USB cord, and boot the twrp.img, it is temporary, and goes away when you boot the system.

I'm seeing an increase in battery life after this update. Also i did few settings correct which was eating my battery i suppose.
What about you guys?

100rabh7791 said:
I'm seeing an increase in battery life after this update. Also i did few settings correct which was eating my battery i suppose.
What about you guys?
Click to expand...
Click to collapse
No complaints from me

Droid_Nut said:
No need to install TWRP, just plug in the USB cord, and boot the twrp.img, it is temporary, and goes away when you boot the system.
Click to expand...
Click to collapse
Thanks, it worked

Badger50 said:
No complaints from me
Click to expand...
Click to collapse
9h of SOT at 33%?????

Le_Combattant said:
9h of SOT at 33%?????
Click to expand...
Click to collapse
Yeah, that's pretty normal for my usage patterns

Badger50 said:
Yeah, that's pretty normal for my usage patterns
Click to expand...
Click to collapse
What type of usage do you have? Can you share us your battery stats (trough android parameter)

Le_Combattant said:
What type of usage do you have? Can you share us your battery stats (trough android parameter)
Click to expand...
Click to collapse
I will if you want after my next cycle. Typically it's mostly participating on xda, 1-2 hours of phone calls, some texting, NO social media, some browsing on the web. I also turn off things like, find my device, I freeze my google app, have little to no hapetic feedback, on wifi 80% of the time, I run stock Ex kernel, and since I'm retired, the phone gets to sit and sleep regularly, and my device is 18 months old. SOT is really to subjective to try and duplicate, so I wouldn't put to much stock in it

Is it possible to install the April update WITHOUT the new Magisk version? I have Magisk 18.1. Can that version STILL be used with the April Update?
I would rather not install Magisk 19 - as it seems to be having issues with Google Play. Thanks.

Badger50 said:
I will if you want after my next cycle. Typically it's mostly participating on xda, 1-2 hours of phone calls, some texting, NO social media, some browsing on the web. I also turn off things like, find my device, I freeze my google app, have little to no hapetic feedback, on wifi 80% of the time, I run stock Ex kernel, and since I'm retired, the phone gets to sit and sleep regularly, and my device is 18 months old. SOT is really to subjective to try and duplicate, so I wouldn't put to much stock in it
Click to expand...
Click to collapse
It's very impressive
I have Facebook/Messenger and Snapchat it's why I never overtake 8h of SOT.
What is the app on your previous post showing your SOT?

Android Q Beta now available for Pixel 3a and 3a XL models

The 4th beta is available publicly today and the Pixel 3a models are officially supported again. This means they should show up in "your available devices" and updates will automatically be pushed out to your device. This is certainly easier than having to manually flash them.
https://www.google.com/android/beta

Is this only for unlocked pixel 3a or will it work with carrier locked ones also, such as TMobile.

synaethe said:
Is this only for unlocked pixel 3a or will it work with carrier locked ones also, such as TMobile.
Click to expand...
Click to collapse
That is a good question, and honestly I don't know the answer for sure (my phone is bootloader unlocked).
That being said, the Q beta will come across like a normal update would. So I would think it is available to locked devices. Even if you want to quit the beta and go back to Android P, I think that comes across as an update as well (although it will do a factory reset of your device and you will have to download all apps and data again). This is the advantage to participating in the actual official beta vs. manually flashing the beta.

It's an over the air update. One of the points of getting pixel is to be on the bleeding edge with the OS. regardless of carrier. It's available whether you're locked or not. Downloading mine now and I'm still locked on T-Mobile.

Yeah confirmed downloading now. on EE network UK. Also seems fine updating from beta 3 which I was on.

sic0048 said:
That is a good question, and honestly I don't know the answer for sure (my phone is bootloader unlocked).
That being said, the Q beta will come across like a normal update would. So I would think it is available to locked devices. Even if you want to quit the beta and go back to Android P, I think that comes across as an update as well (although it will do a factory reset of your device and you will have to download all apps and data again). This is the advantage to participating in the actual official beta vs. manually flashing the beta.
Click to expand...
Click to collapse
Thanks looks like it will work, it started downloading as OTA once I opted in on the beta. Hopefully it's stable enough for basic use. Thanks!

Having a problem after updating to Q beta 4
Some apps will no longer start, and others leave a screen echo when going to home screen.
How do I re-wipe cache?
If that doesn't work I'll try a factory reset (which makes sense for switching from P to Q anyway)

Just updated to Q Beta 4. So far so good, all apps are running - let's see how this goes !
Sent from my Pixel 3a XL using Tapatalk

Matrioux said:
Having a problem after updating to Q beta 4
Some apps will no longer start, and others leave a screen echo when going to home screen.
How do I re-wipe cache?
If that doesn't work I'll try a factory reset (which makes sense for switching from P to Q anyway)
Click to expand...
Click to collapse
Ok, it seems to be a Nova launcher issue. pixel launcher works fine.
Sent from my Pixel 3a using Tapatalk

Matrioux said:
Ok, it seems to be a Nova launcher issue. pixel launcher works fine.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I find the Pixel launcher much smoother in the beta version. Using it as my default for the time being - was using Nova previously
Sent from my Pixel 3a XL using Tapatalk

Do bubble notifications work for anyone? I would like to try it out on beta 4.

apologies for the noob question but i'm on rooted stock, i understand i'll lose root installing Q but is there anything else i need to do to avoid getting myself into trouble? uninstall magisk?
edit: i'll tell you what not to do. don't uninstall magisk and reboot. this seemed innocuous enough but now i have the "No command" screen and android Q is the least of my concerns....

c_tho said:
apologies for the noob question but i'm on rooted stock, i understand i'll lose root installing Q but is there anything else i need to do to avoid getting myself into trouble? uninstall magisk?
edit: i'll tell you what not to do. don't uninstall magisk and reboot. this seemed innocuous enough but now i have the "No command" screen and android Q is the least of my concerns....
Click to expand...
Click to collapse
Take a breath. It's ok. If your bootloader is unlocked all you have to do is flash factory images with the -w and you should be up and running again in no time. It happens to everyone who plays with root at some point.
Sent from my Pixel 3a using Tapatalk

jmtjr278 said:
Take a breath. It's ok. If your bootloader is unlocked all you have to do is flash factory images with the -w and you should be up and running again in no time. It happens to everyone who plays with root at some point.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
god thanks so much for this. appears that just flashing the magisk-patched boot image has the phone booting again but i guess that puts me back at square one (sans data)? assuming to get to Q the best approach is to flash the factory image (currently downloading), go through setup and then get the OTA?

c_tho said:
god thanks so much for this. appears that just flashing the magisk-patched boot image has the phone booting again but i guess that puts me back at square one (sans data)? assuming to get to Q the best approach is to flash the factory image (currently downloading), go through setup and then get the OTA?
Click to expand...
Click to collapse
Yes, flash stock boot.img, then OTA will work. But before doing so, join the beta program so that you'll receive beta 4.

syckman said:
Yes, flash stock boot.img, then OTA will work. But before doing so, join the beta program so that you'll receive beta 4.
Click to expand...
Click to collapse
all sorted now, on Qb4. thanks for the help folks. it's looking great.

Does beta 4 enables volte on non supported carriers?
Some people on their pixel 3 with beta 3 enables volte with other carriers. Can anyone confirm please

This has been my battery stats in BETA 4 since i flashed it.

I keep getting the notification to update on my Sprint locked Pixel 3a. I don't want to though because I'm really hoping to root this phone in the near future and I don't want to not be able to because I updated.
So I'm really just asking if the Q Beta 4 would affect being able to root?

Just an FYI guys, Beta 4 was pulled this morning due to a bootloop issue. If you're on the beta and get the problem, you'll have to roll back to P, if you're looking to upgrade to Q, id say wait and make sure the issue is fixed.

Android 10 factory images is live

Enjoy!
Currently two builds: QP1A.190711.019 and QP1A.190711.020
Factory Image: https://developers.google.com/android/images#sargo
OTA Image: https://developers.google.com/android/ota#sargo

No OTA here in Germany so far

Anyone know the difference between the two builds?
Sent from my Pixel 3a using Tapatalk

Neither in France

jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
They have diferent checksums

jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
"Within the .19 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565300664 which equates to 08/08/2019 @ 9:44pm (UTC).
Within the .20 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565743352 which equates to 08/14/2019 @ 12:42am (UTC).
Based on one of Google's release tool's code, this value seems to be utilized to determine whether it should perform an incremental or full OTA.
If I'm understanding their upgrade process correctly, the .19 image does not contain the September security patch. The .20 appears to be the full stable release with the September security patch.
It would appear .19 should support an incremental upgrade from the latest Android Pie (9) version, PQ3B.190801.002 but not bring you to the latest September security patch.
This leads me to believe that the .20 image is suitable for almost all OTAs. There may be carrier specific cases that one or the other should be utilized but nothing stands out too clearly within any of the immediately available metadata files."
- https://www.reddit.com/r/Android/comments/cz7lb1/android_10_images_are_live/eywlgww/

Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?

I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Sent from my Pixel 3a using Tapatalk

Atiqx said:
Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?
Click to expand...
Click to collapse
No, just uninstall magisk or flash stock boot.img. once that is done, you should OTA just fine.

upinsmoke7610 said:
I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Click to expand...
Click to collapse
On reddit they say that coming from beta the update file is only this small.

yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
Well I knew banking apps would not work on the beta but now I'm on the stable release and my banking app still will not even open, but of a nightmare really as I rely on it.
Sent from my Pixel 3a using Tapatalk

Got the OTA from pie right now 1188.8mb

I've just received the OTA notification here in Spain
---------- Post added at 08:50 PM ---------- Previous post was at 08:49 PM ----------
anyone knows if is there any difference, or added feature compared to the last beta version?

yabadabadooo said:
They have diferent checksums
Click to expand...
Click to collapse
A factory image is a full replacement - and is meant to replace everything (you'll lose all your data and else that isn't backed up). An OTA is an update - you lose nothing. If you're coming from a STOCK factory image (either a beta of 10 OR 9) and your phone is fine, you want the OTA; otherwise (including AOSP), you want the full factory image.

germany here, installing the update now, takes quite some time for being only 41mb, hope it works

I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.

Got it 30 mins ago from stock rom over ota (1.1GB) in France.
Install was smooth and fast.
So far so good!
Enjoying the dark mode
#Edit: weather widget shows temperature in °F instead of °C while everything is setup right. Strange ^^

sic0048 said:
I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.
Click to expand...
Click to collapse
Thank you sic0048! I followed your guide when my Pixel 3a was on 9 and it was smooth. The best instructions I have found and even bookmarked it.
I do have one quick question. I followed your instructions about updating the phone and keeping root, but I lost root after reboot. I probably did something wrong. :silly:
In your instructions under the "Custom Recovery Installation method" you state that TWRP doesn't support Android 10. So how do I root my phone again? Is it safe to use this method or should I use another one of your methods in this tutorial?

After update to 10, I was able to see "Enable DDS" toggle in phone information shortcut.
Now the toggle is gone.
Anyone else has this issue?

yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
I came from RC2 - the update is indeed that little.
However, you will have to wait for a 10-ready build of TWRP; the current TWRP is not ready (of course).