Database Users

Quadrooter

So apparently our phone is vulnerable to a newly founded exploit being dubbed "Quadrooter" that allows for privilege escalation. Do any of you think that this could lead to root on marshmallow if used right?
EDIT: Link to CNET article - http://www.cnet.com/news/quadrooter-security-flaws-said-to-affect-over-900-million-android-devices/

Saw this today. Curious to know as well. Not that this might be any use for me anymore as I'm still waiting to see if LG will fix my bootloop issue.

aarick said:
Saw this today. Curious to know as well. Not that this might be any use for me anymore as I'm still waiting to see if LG will fix my bootloop issue.
Click to expand...
Click to collapse
That's unfortunate. I fear it may be any day for me. We're there any signs before it hit the hay?
I am curious how they claim to be able to gain root access on multiple phones running marshmallow. DM Verity in the kernel is supposed to stop a phone with modifications from voting, so I am not sure how it's supposed to work, unless it's only some form of temp root. Kind of corps of this will be the next 'towel root'. Probably not, but I could hope I guess.

I have the ATT model and would love rooted MM. Hopefully this vulnerability can be used to our benefit.

I hope my H815t could be rooted by that

I have H815T and it's rooted, bootloader is unlocked and running Genysis 4.3 with G5 theme.
But I found the four vulnerabilities in my phone too.
What to do now?

claro4u90 said:
I have H815T and it's rooted, bootloader is unlocked and running Genysis 4.3 with G5 theme.
But I found the four vulnerabilities in my phone too.
What to do now?
Click to expand...
Click to collapse
The vulnerabilities are because your processor (Qualcomm Snapdragon). So, you can't do anything until LG implement arrangements in an update (OTA, KDZ).

lept_2014 said:
The vulnerabilities are because your processor (Qualcomm Snapdragon). So, you can't do anything until LG implement arrangements in an update (OTA, KDZ).
Click to expand...
Click to collapse
Yes you are right.
But my device is rooted and unlocked and OTA updates are disabled. So how would a user like me gets his security patch or such kind of updates?

claro4u90 said:
Yes you are right.
But my device is rooted and unlocked and OTA updates are disabled. So how would a user like me gets his security patch or such kind of updates?
Click to expand...
Click to collapse
You must flash a KDZ (for your G4 model) with LGUP. You'll lose root access, and OTA updates will be enabled. Or you can wait, and flash the KDZ with the fixes.

lept_2014 said:
You must flash a KDZ (for your G4 model) with LGUP. You'll lose root access, and OTA updates will be enabled. Or you can wait, and flash the KDZ with the fixes.
Click to expand...
Click to collapse
Thanks for your help.
Actually I have a stock marshmellow rooted rom which I flashed it a day ago and OTA updates are enabled on that.
Another question, where do the updates store? On rom or some where in the recovery partition etc?
Why I'm asking this, I like Genysis rom so if I restore my device to Stock rooted 6.0 and get the air updates in september etc, will the updates remain on the device if I flash the rom(back to Gynesis)?

claro4u90 said:
Thanks for your help.
Actually I have a stock marshmellow rooted rom which I flashed it a day ago and OTA updates are enabled on that.
Another question, where do the updates store? On rom or some where in the recovery partition etc?
Why I'm asking this, I like Genysis rom so if I restore my device to Stock rooted 6.0 and get the air updates in september etc, will the updates remain on the device if I flash the rom(back to Gynesis)?
Click to expand...
Click to collapse
You can't apply a official OTA with a rooted device without a error.
And the updates are in the firmware (aka ROM), so if you change de ROM, you will lose all updates.

What to do?
Install drweb antivirus for check apps before install.
This is the unic risk i found.
Sent from my XT687 using xda premium
---------- Post added at 10:33 PM ---------- Previous post was at 10:32 PM ----------
Quadrooter affected
http://forum.xda-developers.com/showthread.php?t=3435585
Quadrooter affected
Sent from my XT687 using xda premium
---------- Post added at 10:40 PM ---------- Previous post was at 10:33 PM ----------
This is not so relevan more than, they are promoting goglebley site.
Ah! Stay protected:
I found in Settings.apk that this app access internet, for ... for example here, when i connect to wifi or 3g, my lightningWall is not on time delay to impess certain connections, so slowly i will forbid internet in some another apps by force , this app begun deny connection because some chitty google domains are included by me on the etc/hosts . So, is only prevent this app access internet , for security, this may gain privileges
I rebuilded with Lucky Patcher with denied INTERNET.permission in manifest.
Rebuild your Settings.apk, because this may gain privileges.
Sent from my XT687 using xda premium

lept_2014 said:
You can't apply a official OTA with a rooted device without a error.
And the updates are in the firmware (aka ROM), so if you change de ROM, you will lose all updates.
Click to expand...
Click to collapse
And will there be unofficial updates or such security patches for custom roms?
We have started a Q&A here, I hope many will get benefit from this conversation

Of course, mine is old xt687 , the motorola will never update anymore this, nicht paying!
Sent from my XT687 using xda premium

I hope it can be used to gain root on vs986 marshmallow
Sent from my VS986 using Tapatalk

claro4u90 said:
Thanks for your help.
Actually I have a stock marshmellow rooted rom which I flashed it a day ago and OTA updates are enabled on that.
Another question, where do the updates store? On rom or some where in the recovery partition etc?
Why I'm asking this, I like Genysis rom so if I restore my device to Stock rooted 6.0 and get the air updates in september etc, will the updates remain on the device if I flash the rom(back to Gynesis)?
Click to expand...
Click to collapse
If you are talking about the update.zip, it should be in the cache partition.

Using RR build 20160808 on h815 with llama kernel r6.
Sent from my LG-H815 using XDA Labs

Really! I believe this app haves a fake scanner with a png image as result.
All images are the same CHIT to promote goglebley crappy.
Sent from my XT687 using xda premium

Comparison of Android Updates *December 2018 (OPM7.181205.001) (Oreo 8.1.0)*

Purpose of this thread:
This thread is about changes within factory images of newly released Android updates in comparison with the previously released Android update.
Latest Android version 8.1.0 (Oreo): OPM7.181205.001
This December update is most likely gonna be the last official security update from Google for the Nexus 5X (source: https://support.google.com/nexus/answer/4457705?hl=en)
Download-Link: https://dl.google.com/dl/android/aosp/bullhead-opm7.181205.001-factory-5f189d84.zip ​MD5: 05DEE954B6FD17B6B301A4D1C90B1B5E​Changelog: https://source.android.com/security/bulletin/pixel/2018-12-01 ​Unchanged:
bootloader bhz32c
radio 2.6.42.5.03
Changed: (md5sum in brackets)
boot (438936FDD50D2C8D3FA8D7586624D670)
recovery (E55D287CBCF78DACEC618E538CE74014)
system (9DD438116FB86EDBF89876A728CC0AA8)
vendor (97C79E83F00AD006D77DA9C570A71BD7)

How to install it on rooted devices with custom recovery installed? Flashfire?
Δημοσιεύτηκε από Google Nexus 5X με Android 7.0 Nougat μέσω Tapatalk.

AFK269 said:
How to install it on rooted devices with custom recovery installed? Flashfire?
Δημοσιεύτηκε από Google Nexus 5X με Android 7.0 Nougat μέσω Tapatalk.
Click to expand...
Click to collapse
That has worked before. Still should work, I have not tried it though.
Sent from my Nexus 5X using Tapatalk
---------- Post added at 02:40 AM ---------- Previous post was at 02:39 AM ----------
Any idea what changes to the system?
Sent from my Nexus 5X using Tapatalk

Smoosh1 said:
userdata.img is the same (MD5: 808444c5b0a4cbfa1f2cbf38b6629b67)
cache.img is the same (MD5: 9aedd15ebf6bc07a38de5bcd705f516a)
Click to expand...
Click to collapse
I think you'll find userdata and cache won't change throughout the lifecycle of nougat. Through something like 14 MM updates they never changed (same MD5) until Nougat came (where they did change) and then through 2 releases they haven't changed.

AFK269 said:
How to install it on rooted devices with custom recovery installed? Flashfire?
Click to expand...
Click to collapse
I would recommend you follow Heisenberg's guide, section 9 "How To Update To A New Build Of The Stock ROM"
sfhub said:
I think you'll find userdata and cache won't change throughout the lifecycle of nougat. Through something like 14 MM updates they never changed (same MD5) until Nougat came (where they did change) and then through 2 releases they haven't changed.
Click to expand...
Click to collapse
You are right, they most likely won't change throughout the lifecycle of nougat. I just mentioned them for the sake of completeness.

Comparison of Android Updates
Do It A Your Own Risk. I am not responsible if you make a mistake.
I found this method on the Internet and I applied it to my phone right now:
(WITH THIS METHOD YOU WILL NOT LOSE ROOT, CUSTOM RECOVERY)
1.Download the ZIP.
2.Download FlashFire.
3.Open flashfire and accept for root access etc etc...
4.click "+" button and click to "flash firmware package" and find the ZIP.
5.Wait for a couple o seconds or 2mins, and then uncheck the "Recovery" (if you don't want to lose the custom recovery) and "Data" (maybe on your device will be already unchecked so keep it unchecked if you don't want to lose your data) and then I clicked the "ν" button.
6.Click "Flash". Your screen will be black for a minute and then you will see a progress bar at the bottom of your screen and log of FlashFire what installs on your device.
7.When it finish flashing, your device will be automatically reboot.
8.Wait a couple of minutes (approximately 3-6 mins).
9.Your device is running the latest Android Version with the latest Security patches and you have also root back....
Sent from my iPad using Tapatalk

AFK269 said:
I found this method on the Internet and I applied it to my phone right now
Click to expand...
Click to collapse
Strange that you didn't include a reference to where you got it on the Internet. Many times, they provide more detail than just the steps and took time create the content and test the procedure.

krelvinaz said:
Strange that you didn't include a reference to where you got it on the Internet. Many times, they provide more detail than just the steps and took time create the content and test the procedure.
Click to expand...
Click to collapse
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
Sent from my iPad using Tapatalk

AFK69 shared the typical img flashing instructions for FlashFire. I've been using it on my rooted devices for months. No issues.
Sent from my Nexus 9 using Tapatalk

Android November update NRD91N released
New Android security update NRD91N got released today.
What has changed? -> See updated OP

I'm sorry, but HERE the last one is still NPF10C, it's a different branch or I'm missing something?
EDIT: nevermind i'm dumb, the post is about the official factory image, mine is about devoloepr preview

AFK269 said:
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
Click to expand...
Click to collapse
Only problem with FlashFire is CF himself says not to flash a bootloader or radios so when there a change there you either have to make a twrp flashable or use fastboot to get atw updated.. Has anyone used FF to flash bootloader? I'm curious....
Sent from my Nexus 5X using XDA Labs

SM210 said:
Only problem with FlashFire is CF himself says not to flash a bootloader or radios so when there a change there you either have to make a twrp flashable or use fastboot to get atw updated.. Has anyone used FF to flash bootloader? I'm curious....
Click to expand...
Click to collapse
Me too!! (Curious)
Sent from my Nexus 5X using XDA Labs

My build number changed to N5D91L after the November update, not NRD91N. How come?

In the past there were some different builds for different countries with a different radio.img. So where do you come from?

I live in the UK.
Edit: And my radio is still 2.6.33.2.14.

Hm...I've only found a lot of japanese sites (f.e. Y!Mobile (is that yahoo?) if I search for this build. Don't know if there is a coherence.

N5D91L is 7.0.0_r21 while NRD91N is 7.0.0_r15. Probably a quick hotfix on the unfixed dirtycow exploit + other fixes . Too lazy to check the real changes on git.
Since some of us is still waiting for the ota by phases and by the time we are getting it, google already roll out N5D91L. Thus the mysterious build update emerged. The others on NRD91N will get it or probably not, until December.

ThorSchwar said:
Hm...I've only found a lot of japanese sites (f.e. Y!Mobile (is that yahoo?) if I search for this build. Don't know if there is a coherence.
Click to expand...
Click to collapse
Nevermind, apparently it's a regular build - see: http://forum.xda-developers.com/nexus-5x/help/n5d91l-strange-android-build-t3500378

November OTA patch has new tag:
Just captured this from my 5X.
Source: google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
Target: google/bullhead/bullhead:7.0/N5D91L/3425233:user/release-keys
https://android.googleapis.com/packa...a1f18978ec.zip
So looks like the new build is not NRD91N but N5D91L.

RETUS Nougat OTA (discussion, root, setups, etc.)

Hey guys,
Not much of a poster but it seems the retus guys are left out in discussions involving flashing our firmware...
I present the official nougat OTA I received for RETUS only. This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
For those sideloading this and are still on MM, you'll just need to adb sideload the file. Keep in mind that I received my OTA update on a November security patch, so it may not mater at all which patch you have.
RETUS NOUGAT OTA (Mega link)​
Preparation:
For those who rooted and caused a bunch of hell on your system partition, you can grab some stock unsigned firmware here and revert what you did. Fastboot flash the boot, sparsechunks (in order), recovery, and oem images (then reboot back to bootloader to choose recovery mode). You can now finally sideload it flawlessly without losing any data. If you need more information you can check out one the revert to stock firmware guides, I'm not going to post something repetitive.
Root options:
You want root? You have two options...first you obviously need TWRP.
flash a custom ROM
flash this gentleman's (tomparr) custom kernel over on his thread and then flash superSU or Magisk. You can flash both SuperSU and Magisk but you could also just flash Magisk which comes with it's own systemless root.
Revert?
You can reflash MM images but I suggest using something more autonomous like this flashing tool by core720 since there's a lot more commands involved to officially downgrade. There's also an edit of the downgrade bat script in the comments of the thread which I suggest to use instead.
Viper4Android!? Atmos!?
There are currently magisk modules that work (both arise and independent ones).

I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.

I am on July security patch and just got the prompt so don't think patch level matters

xantanion said:
I am on July security patch and just got the prompt so don't think patch level matters
Click to expand...
Click to collapse
Please let me know if yours updates, mine has failed four times today already.

Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
Mine went flawlessly

Jimi Mack said:
I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.
Click to expand...
Click to collapse
Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.

DroneDoom said:
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.
Click to expand...
Click to collapse
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
xantanion said:
Mine went flawlessly
Click to expand...
Click to collapse
You installed this downloaded OTA or did you get yours OTA? Thanks.

Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
Got my OTA today and had no issues. Just got the phone brand new yesterday as well

Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.

DroneDoom said:
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.
Click to expand...
Click to collapse
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "

Jimi Mack said:
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "
Click to expand...
Click to collapse
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.

DroneDoom said:
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.
Click to expand...
Click to collapse
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?

Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.

Jimi Mack said:
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?
Click to expand...
Click to collapse
I think there may be a difference in security patches but they have the same build number so I'm not too sure.
holabola said:
Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.
Click to expand...
Click to collapse
Yeah it is, it reminds me of the days when I had a Motorola razr lol.

For anyone that was wondering, the display size scaling works PERFECTLY.
I originally changed the DPI to make everything smaller, but it led to a lot of random issues with other apps (mainly involving the camera). The display size scaling mimics the effects of a DPI change right out of the box without all the issues and need for a computer (I wasn't rooted so)
Also, when I got the update, I was on the December 1st security patch.

DroneDoom said:
This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
Click to expand...
Click to collapse
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
DroneDoom said:
Magisk
Click to expand...
Click to collapse
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.

xxBrun0xx said:
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.
Click to expand...
Click to collapse
Thanks for the feedback (fixed op), I noticed v11 doesn't patch the kernel correctly and the ROM tries to boot without it. I thought it was just me since I was playing around trying to change my cache partition to f2fs but I guess the kernel doesn't support that filesystem for cache (ROM boots but doesn't initialize).
S3v3n's ROM is based on firmware stock right? I tried magisk with V4A module but it doesn't work and Atmos somehow bricks stock but it doesn't brick on a ROM built from different source (works on xperience). I noticed today that the ARISE project has a magisk module for it's latest project so maybe there's a possibility for stock to have systemless V4A.

Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?

Jimi Mack said:
Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?
Click to expand...
Click to collapse
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.

DroneDoom said:
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.
Click to expand...
Click to collapse
I thank you. I got the update to begin to load, it fails and aborts at 45% . It states something about content, lists my build number and give a code 755. I can not find out anything about this one either. I guess something is screwy with what is installed on my phone and what should be...

8.1. OTA

Hello, im on 8.1. dp2, and still didnt get official update with december security patch...can i manually sideload OTA from december over dp2 ??
Thanks??

scrin378 said:
Hello, im on 8.1. dp2, and still didnt get official update with december security patch...can i manually sideload OTA from december over dp2 ??
Thanks??
Click to expand...
Click to collapse
No, ADB sideload will fail. 8.1 DP2 is on a newer branch than December 8.1 stable. You could install via fastboot or wait until Google pushes the OTA for preview users.
Sent from my Nexus 5X using Tapatalk

Opt out beta tester

mr.joshuanice said:
Opt out beta tester
Click to expand...
Click to collapse
I think @mr.joshuanice is right. Opt out from the beta program.
And then, among all methods to install the update I would recommend to flash the factory image so that you can start from a very clean environment.
I can't provide link here on XDA right now because I'm a too young XDA member (not so young in the real-life however, )
By the way, look for android factory images in google and you will find download link as well as instruction for flashing.

luk.giak said:
I think @mr.joshuanice is right. Opt out from the beta program.
And then, among all methods to install the update I would recommend to flash the factory image so that you can start from a very clean environment.
I can't provide link here on XDA right now because I'm a too young XDA member (not so young in the real-life however, )
By the way, look for android factory images in google and you will find download link as well as instruction for flashing.
Click to expand...
Click to collapse
I know that option for beta program...but i dont want to lose my data..
It looks that i will wait for OTA from Google
Thanks...

scrin378 said:
I know that option for beta program...but i dont want to lose my data..
It looks that i will wait for OTA from Google
Thanks...
Click to expand...
Click to collapse
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...

whpsnp said:
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
Click to expand...
Click to collapse
No, i opt out from beta program, and then i get official version..i lose my data, but nothing special, most of pics, docs, etc...is on the cloud storage ..so no big deal for me.. good luck with patience

whpsnp said:
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
Click to expand...
Click to collapse
Factory images with January security patches are out since yesterday. Why don't you flash it?
Another option is to use the FULL OTA update. This method does not require to unlock the bootloader and, consequently, to wipe all your data.
If I were you I would go for the factory image with a clean flash

luk.giak said:
Factory images with January security patches are out since yesterday. Why don't you flash it?
Another option is to use the FULL OTA update. This method does not require to unlock the bootloader and, consequently, to wipe all your data.
If I were you I would go for the factory image with a clean flash
Click to expand...
Click to collapse
I thought I needed to have an unlocked bootloader.
By full OTA you mean sideload via adb?

whpsnp said:
I thought I needed to have an unlocked bootloader.
By full OTA you mean sideload via adb?
Click to expand...
Click to collapse
Yes the full OTA is installed via adb sideload. And it does not need an unlocked bootloader.
Look for "full ota Android O" in Google and you will find the page and the instructions.

luk.giak said:
Yes the full OTA is installed via adb sideload. And it does not need an unlocked bootloader.
Look for "full ota Android O" in Google and you will find the page and the instructions.
Click to expand...
Click to collapse
Awesome! I've done it before so it should be fairly easy.
Now I know what I'll do Friday night ?

whpsnp said:
Awesome! I've done it before so it should be fairly easy.
Now I know what I'll do Friday night ?
Click to expand...
Click to collapse
:good:

I had the OTA to 8.1 notification. I rebooted my phone and now it's gone and it shows as I'm being up to date. I want it back!
Sent from my Nexus 6P using Tapatalk

OT
As a side note for all people who do not want to unlock the bootloader. Please consider at least to:
* activate developer options (tapping 7 times on the build number under phone information)
* enter developer options and activate 1) Debug USB and 2) Enable OEM Unlock
As you probably know, the nexus 6p is subject to the bootloop of death. It is hardware based and, when it happens, the only way to give a second life to the Nexus 6p is to flash a special boot.img (or kernel) that enable only 4 cores (over 8). You can perform this procedure only if you can unlock the bootloader. Hence, only if you have previously enabled the two options above (debug USB and Enable OEM Unlock).
---------- Post added at 07:17 PM ---------- Previous post was at 07:05 PM ----------
Ulver said:
I had the OTA to 8.1 notification. I rebooted my phone and now it's gone and it shows as I'm being up to date. I want it back!
Click to expand...
Click to collapse
Google is really messing up with OTAs. You should consider to manually flash a factory image or to adb sideload a full OTA (available on the official website).

Same situation for me, i get ota 8.1 ~ 10 December then 8.1 dp2 ota. And for now no ota I am still on security update from November...

One question, if im rooted, can i flash full OTA with flashfire??

sideload the DP2 to Final ota (Dec patch).
Then unenroll your device from beta, you will get an update (Jan patch)
https://android.googleapis.com/pack.../105818de493dde2bb290a13474a367f78ac6122f.zip

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