Database Users

September security updates being posted

MOB31E is up now (along with first Nougat patch for those other devices)
https://dl.google.com/dl/android/aosp/shamu-mob31e-factory-051e2d25.zip

so we still remain in 6.0.1?

thetransit123 said:
so we still remain in 6.0.1?
Click to expand...
Click to collapse
Yes, still Marshmallow. Oddly, this one is named differently than the last couple monthly security updates. It does follow that mid-July performance numbering system.

The 6p is still on 6.0.1 too. So don't get too discouraged!

Tried to download the sept security update and the google ota link and files not there: 404. That’s an error. That’s all we know.

ryancell said:
Tried to download the sept security update and the google ota link and files not there: 404. That’s an error. That’s all we know.
Click to expand...
Click to collapse
I had that earlier too, but it's working now.

Preparing for nougat?

we probably wont get nougat until they release the "pixel phones"

i can see two new image same time for shamu, i can understand Google.

/system/etc/hosts
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.

Voight Kampff said:
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.
Click to expand...
Click to collapse
I'm using Magisk's superuser and systemless AdAway on the new update with no problems.

JimSmith94 said:
I'm using Magisk's superuser and systemless AdAway on the new update with no problems.
Click to expand...
Click to collapse
some links, please?
thanks

gothy.gothy said:
some links, please?
thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
http://forum.xda-developers.com/showthread.php?t=2190753

AlexX-DE said:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
http://forum.xda-developers.com/showthread.php?t=2190753
Click to expand...
Click to collapse
Thanks

Can anyone tell me the difference between MMB30W and MOB31E? I was going to sideload the September OTA, but not sure which one I am supposed to use. Haven't found any details anywhere. I'm currently on MMB30R, but I hadn't noticed there were multiple images released each month when I've sideloaded until now so not sure if I'm supposed to be on that image or not?

gill30 said:
Can anyone tell me the difference between MMB30W and MOB31E? I was going to sideload the September OTA, but not sure which one I am supposed to use. Haven't found any details anywhere. I'm currently on MMB30R, but I hadn't noticed there were multiple images released each month when I've sideloaded until now so not sure if I'm supposed to be on that image or not?
Click to expand...
Click to collapse
MMB has the radio that the carriers have agreed on, it's for their own version of Marshmallow. MOB has a newer radio. If you sideload it anyway, use the most recent.

If I am currently on M0B30W Project Fi, I see there are two builds below mine...which version below would I update to for the security patches safely if I'm stock?
6.0.1 (MMB30W) or 6.0.1 (MOB31E)

Voight Kampff said:
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.
Click to expand...
Click to collapse
No issue, but i did the usual...booted into twrp and deleted a couple of unneeded keyboards to make space.

ryancell said:
If I am currently on M0B30W Project Fi, I see there are two builds below mine...which version below would I update to for the security patches safely if I'm stock?
6.0.1 (MMB30W) or 6.0.1 (MOB31E)
Click to expand...
Click to collapse
Either one will work. They are exactly the same except for the radio. The MMB images contain an older radio that carriers have approved and the MOB images contain a newer radio that hasn't been approved by carriers yet. You could try the MOB image and if the radio performance isn't up to par you could extract the one from the MMB image. I've always used the MOB images and haven't had any radio issues, but I'm not on Project Fi...

Voight Kampff said:
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.
Click to expand...
Click to collapse
Nope, but I always delete useless preinstalled junk to make space.

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...

DP4 is out!

https://developer.android.com/preview/download
Just installed. July security update. They changed the silent mode status bar icon. Still looking for other changes.
-edit- Dark theme is an option under display settings, advanced!
It seems to have some horrible contact bar in the app drawer when you pull it up now that shows 2 frequent contacts? Found out you can disable this under home screen settings.
-edit 2- root still works with magisk. Still P under build with same easter egg as before.

What's the status on root

kingbri said:
What's the status on root
Click to expand...
Click to collapse
It works with magisk 16.4

Is anyone able to tell me if Actions Services app is included in DP4 for the Pixel XL?
I originally grabbed the apk from a Pixel 2, but i suspect that it's now included in DP4.

xdatastic said:
Is anyone able to tell me if Actions Services app is included in DP4 for the Pixel XL?
I originally grabbed the apk from a Pixel 2, but i suspect that it's now included in DP4.
Click to expand...
Click to collapse
It's included.

Gordietm said:
It's included.
Click to expand...
Click to collapse
Thank you!

Anyone tried the ElementalX build for DP3 on this yet? ctsProfile seems to fail SafetyNet on Magisk 16.4, other than that haven't noticed any problems.

BoboBrazil said:
https://developer.android.com/preview/download
Just installed. July security update. They changed the silent mode status bar icon. Still looking for other changes.
-edit- Dark theme is an option under display settings, advanced!
It seems to have some horrible contact bar in the app drawer when you pull it up now that shows 2 frequent contacts? Found out you can disable this under home screen settings.
-edit 2- root still works with magisk. Still P under build with same easter egg as before.
Click to expand...
Click to collapse
Sorry, when you say root still works with magisk... do you have to unroot before updating, then reflash magisk? Or can you update right over the previous update if you're already rooted??

Hopefully Google fix up the device certification for DP4 - Google Pay won't work currently, but did on DP3. I think G need to add it server-side.
edit: Google fixed the device certification. Google Pay now works again.

Flash kernel failed cts. Might be something new detecting magisk

dht2005 said:
Sorry, when you say root still works with magisk... do you have to unroot before updating, then reflash magisk? Or can you update right over the previous update if you're already rooted??
Click to expand...
Click to collapse
Same way as always with Pixel XL ...

The theme light,dark,auto doesn't do anything for me....
Sent from my Pixel XL using Tapatalk

still not boot up, if you remove (debloat) APK's from system/app

Safety net fails but magisk hide takes care of my banking apps..so all good

I wish the OTA would hit.

Ota worked for me yesterday
shamelin73 said:
I wish the OTA would hit.
Click to expand...
Click to collapse
Sent from my Pixel XL using Tapatalk

I just need a little bit more patient it just dropped on mine too
perfoliate said:
Ota worked for me yesterday
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel XL using Tapatalk

Keep losing root, anyone else? A reboot will fix it, but it goes away eventually for me. Also magisk data partition isn't set up correctly (can't install modules).

Anyone having issues getting the light and dark themes to work?
Sent from my Pixel XL using Tapatalk

tttuning said:
Anyone having issues getting the light and dark themes to work?
Click to expand...
Click to collapse
I can't tell any difference from the settings...
---------- Post added at 07:07 AM ---------- Previous post was at 07:03 AM ----------
funkybrunk said:
Keep losing root, anyone else? A reboot will fix it, but it goes away eventually for me. Also magisk data partition isn't set up correctly (can't install modules).
Click to expand...
Click to collapse
Same for me. I install and check out everything... Everything is going great. Then randomly an app I use will say no root detected.. And I'll go to magisk and it says to install 16.4...
I've been looking around but you're the only one I've found saying what I'm seeing.

Beta 5/RC1 of Q on deck!

Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).

PGHammer said:
Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).
Click to expand...
Click to collapse
Let us know if it boots without fuss

SketchyStunts said:
Let us know if it boots without fuss
Click to expand...
Click to collapse
Working fine here. My 3a restarted once after first boot but it's working fine now

What Issues?
baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
No issues at all; just one quibble - no dark-mode launch animation (even though systemwide dark mode is still active, as I set it with beta 4). And I'm admitting it's a quibble. (It should be present if you have systemwide dark mode set.)

anyone know how to root on beta5??

jayxiao171735 said:
anyone know how to root on beta5??
Click to expand...
Click to collapse
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.

baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.

Uzephi said:
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.
Click to expand...
Click to collapse
I was on the stock July update (phone is a week old) and this is the first developer preview update I received. The build number I have is below

Where is everyone getting beta 5? I only have beta 4 available.

stevew84 said:
Where is everyone getting beta 5? I only have beta 4 available.
Click to expand...
Click to collapse
OTA here

Uzephi said:
OTA here
Click to expand...
Click to collapse
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.

stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.

SketchyStunts said:
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.
Click to expand...
Click to collapse
I went to the June image and now there is no Q beta available...even though I'm enrolled in the beta program. Weird. I've had the beta previously.
EDIT: got it. thanks.

stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.

OTA in Both Caases
Uzephi said:
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.
Click to expand...
Click to collapse
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).

PGHammer said:
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).
Click to expand...
Click to collapse
So basically you like to live dangerously....I can respect that :good:

Actually.....
SketchyStunts said:
So basically you like to live dangerously....I can respect that :good:
Click to expand...
Click to collapse
I live more dangerously testing Windows (which I have been doing since Windows 95 - the original one). Rather amusingly, I've been more conservative (if not downright chicken) when it comes to the phone side of operations - mostly because I've had to. Remember - until Q, Android beta testing was a lot more closed than the same for Windows. Heck - even with Q, where is the most OPEN portion of the testing program? Easily explained - the Pixels. Every Pixel ever built - from the first one to the current one - can- and could - opt-in to it. Problem - until now, Pixels were chained to a limited set of providers. (In the United States, a grand total of two - Verizon and Google itself (via Fi).) The 3a and 3aXL changed that - as long as you had a nano-SIM, and $479USD (at worst), you could get a Pixel and activate it. I'm not on Verizon - I'm not on a Big Four carrier, either. What carrier am I on? Tracfone - an MVNO. (Tracfone uses the towers of all of the Big Four carriers; with the S7 - the phone my SIM came out of, I used the towers of T-Mobile AKA the Uncarrier.) Since I've had the opportunities, I've paid it back, and paid it forward (when and where possible). The Pixel 3a makes it possible - so why not? However, I don't recommend it due TO that it lets me pay it forward - quite aside from that, the Pixel 3a - merely as a mainstream/midrange user - is the best-used and best-supported such new phone. THAT is why I recommend it.
#teampixel #whatcamera?

xFirefly93 said:
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.
Click to expand...
Click to collapse
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?

jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
Ask John over at Twitter.

jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
I posted this in another thread you asked this question in, but I figured it would be good to post here to for the benefit of others.....
I found this on the latest Magisk Canary build thread.
tysj said:
Problem they're having is that it isn't outputting the patched boot.img as it says it is. I'm running to the same issue on my Pixel 3.
EDIT:
Somehow got it to work. Uninstalled Magisk Manager, re-downloaded again from the OP, decided to update Magisk Manager from the app, then tried patching the boot.img again which finally work. Flash the patched_boot in fastboot and all is well.
Click to expand...
Click to collapse
So it sounds like there is so issue with the Magisk Manager - either the user wasn't really on the latest build, or there is some sort of permission issue with writing files, etc. But it seems that reinstalling the manager fixes the issue and you should be able to get Magisk to modify the stock boot.img file as normal.

is anyone having trouble with Google pay

I keep getting this error

I have no issues. Just used it today at the local supermarket.

jasonsoto said:
I have no issues. Just used it today at the local supermarket.
Click to expand...
Click to collapse
What's your security patch

Exathi said:
What's your security patch
Click to expand...
Click to collapse
It's the February 1 security patch

If you're rooted that would explain why it's not working. You need the gpay magisk module to fix it if rooted.

luigi90210 said:
If you're rooted that would explain why it's not working. You need the gpay magisk module to fix it if rooted.
Click to expand...
Click to collapse
It wasn't working even before I rooted

Is there a fix for this