Database Users

Marshmallow 6.0.1 security update released, April 2016 (MMB29X)

Available at:
https://developers.google.com/android/nexus/images#shamu
At a minimum it should fix the CVE-2015-1805 vulnerability. If you see any other changes post here.
The bootloader and the radio are the same as mmb29v.

najoor said:
Available at:
https://developers.google.com/android/nexus/images#shamu
At a minimum it should fix the CVE-2015-1805 vulnerability. If you see any other changes post here.
Click to expand...
Click to collapse
I'm not seeing that under Shamu Firmware. There is some stuff for it under Binaries, but not Firmware.
UPDATE:
Its showing up now.

This should be the list of the patches in this update. It's the April security bulletin.
https://source.android.com/security/bulletin/2016-04-02.html

MMB29X
Hey all. Ive been off the scene since July. I finally got my replacement N6. As soon as I turned it on, It had this update rarin to go so I installed it. Is this going to have any effect on unlock, root, custom recovery? I ask because it is brand new stock untouched other than the update.
Thanks Fellas

MMB29X
Hey all. Ive been off the scene since July. I finally got my replacement N6. As soon as I turned it on, It had this update rarin to go so I installed it. Is this going to have any effect on unlock, root, custom recovery? I ask because it is brand new stock untouched other than the update.
Thanks Fellas

So, I was on the 6.0 Build for a long time but finally decided it was time to update. I moved up to this build and have had some issues. Before I just replaced the Hosts file to get ad blocking. But with the 6.0.1 builds the System is full. Easy workaround was creating a symlink to a hosts file that is placed in /sdcard/ But in this build it seems like it isn't doing any ad blocking. Anyone have any ideas why?
Thanks
Basically I have 3 wants aside from stock, I don't root so I can keep Android Pay, I want ad-blocking, and edit the Build.prop to net.tethering.noprovision=true

Hello all. Has anyone gotten V4A to work with this latest update? I flashed the latest version and ended up locked at the Google Screen. Thank God for backups.
Sent from my Nexus 6 using XDA-Developers mobile app

electrojas said:
Hello all. Has anyone gotten V4A to work with this latest update? I flashed the latest version and ended up locked at the Google Screen. Thank God for backups.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
v4a has been working on most builds. you could have been doing something wrong or missing sonething

electrojas said:
Hey all. Ive been off the scene since July. I finally got my replacement N6. As soon as I turned it on, It had this update rarin to go so I installed it. Is this going to have any effect on unlock, root, custom recovery? I ask because it is brand new stock untouched other than the update.
Thanks Fellas
Click to expand...
Click to collapse
No, its a Nexus. But look into the new SuperUser by Chainfire, it is systemless now. So version 2.67 or higher. Also the system partition is full now. You cant write to it without deleting a couple of items first like unused keyboards.

I have seen so many new versions of Viper, and as I said in my previous post I turned on my phone from brand new, fast boot, unlocked bootloader and rooted. I installed TWRP, version 3001. So at this moment I am stock rooted with TWRP version MMB29X. Can anyone kindly point me to the best and correct TWRP flashable version of Viper? Without V4A, I feel like I have half a phone. Thanks to anyone who can give me a hand. Peace guys.
Sent from my Nexus 6 using XDA-Developers mobile app

electrojas said:
I have seen so many new versions of Viper, and as I said in my previous post I turned on my phone from brand new, fast boot, unlocked bootloader and rooted. I installed TWRP, version 3001. So at this moment I am stock rooted with TWRP version MMB29X. Can anyone kindly point me to the best and correct TWRP flashable version of Viper? Without V4A, I feel like I have half a phone. Thanks to anyone who can give me a hand. Peace guys.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well I did what we all need to do and just kept diggin. Turns out wugfresh updated the toolkit for the new updates, I had to reinstall the newest TWRP, and flash the latest V4A. Killer. This is the best app there is for Android by far.
Sent from my Nexus 6 using XDA-Developers mobile app

MMB29X factory image just got updated in the last day or so.
New:
https://dl.google.com/dl/android/aosp/shamu-mmb29x-factory-99e985b9.tgz
Original:
shamu-mmb29x-factory-ef4cbb75.tgz
No idea why or what changed. I'm on slow internet at the mo so can't check. Maybe just changed one of the included scripts ?

xdatastic said:
MMB29X factory image just got updated in the last day or so.
New:
https://dl.google.com/dl/android/aosp/shamu-mmb29x-factory-99e985b9.tgz
Original:
shamu-mmb29x-factory-ef4cbb75.tgz
No idea why or what changed. I'm on slow internet at the mo so can't check. Maybe just changed one of the included scripts ?
Click to expand...
Click to collapse
Its include only two changed apk. Everything else - same.
New Google Play services 9.0.86

Displax said:
Its include only two changed apk. Everything else - same.
New Google Play services 9.0.86
Click to expand...
Click to collapse
Could you extract and share the play services apk please

xdatastic said:
Could you extract and share the play services apk please
Click to expand...
Click to collapse
https://mega.nz/#F!B01wWDRT!W-GlR70PgY-iCuRrtg9azw
But it is odexed apk, so can't be uploaded on http://www.apkmirror.com

MOB30D build mirror

For reasons that haven't been specified yet, the builds labeled MOB30D have been removed from the Nexus Factory Image page.
I uploaded it on the mirror, so, you can download if you want flash it. [Nexus 7 (2013) Wi-Fi]
https://mega.nz/#!15kGUSYA!6mKmEy1oZldroLtBDgOepWBt25xTqeVc7jC9TJ1Efyg

Weird they pulled it. Whats up with that. I didn't flash it. Notice any problems or super-secret files left in there?

I haven't flashed it either. I assume the found a bug.
Sent from my Nexus 6P using Tapatalk

I flashed it but I not noticed any issues so far

I still haven't flashed it but have been listening to some Mobb Deep. MOB30D!

Anyone having issues with this release? Debating whether or not to flash my unit. I notice that the Nexus 7 WiFi has binary files available with a MMB29X release.
This is interesting....found this link on Sprint's website: https://community.sprint.com/baw/message/1038775
Almost seems like MMB30D was suppose to have been the mid-March security release.
Features/Enhancements:
•Revision of March Android Security Update to include new fixes
For those who flashed this MMB30D onto the Nexus 7, what is the date in ABOUT PHONE. Is it April 1 or April 2?

Candy[MAN] said:
Anyone having issues with this release? Debating whether or not to flash my unit. I notice that the Nexus 7 WiFi has binary files available with a MMB29X release.
This is interesting....found this link on Sprint's website: https://community.sprint.com/baw/message/1038775
Almost seems like MMB30D was suppose to have been the mid-March security release.
Features/Enhancements:
•Revision of March Android Security Update to include new fixes
For those who flashed this MMB30D onto the Nexus 7, what is the date in ABOUT PHONE. Is it April 1 or April 2?
Click to expand...
Click to collapse
2 april

The last image for the Nexus 7 2013 razor that I see is still MMB29V.
So much for Google being responsive in getting security updates out. I would have thought that after making a big deal out of that mid-March kernel fiasco that they would have fixed and re-released the images for the three devices that they pulled for whatever reason on Monday. It's now the weekend and no explanation or update from Google. Why am I not surprised?

Build "MOB30D" again available for download via direct link.
On site, it still not displayed.
https://dl.google.com/dl/android/aosp/razor-mob30d-factory-15169856.tgz

what make you guys think this is for flo razor if sprint say : Nexus 5 software update - version MOB30D
and when we download, it says RAZOR !?! WTF !

Displax said:
Build "MOB30D" again available for download via direct link.
On site, it still not displayed.
https://dl.google.com/dl/android/aosp/razor-mob30d-factory-15169856.tgz
Click to expand...
Click to collapse
Was this link not working before (after it was pulled) or was it just taken off the site?

Candy[MAN] said:
Was this link not working before (after it was pulled) or was it just taken off the site?
Click to expand...
Click to collapse
All direct links stopped working after ~20 minutes after hiding from site.
And today they start working again, but still not displayed in the list.

I just factory defaulted my Nexus 7 (2013) device and installed this new factory image (MOD30D). Once I logged into my Google account, I got an email that I successfully logged into a Nexus 7 (2102).......2012??? WTF?
I wonder if there is/was an issue with the image's fingerprint where it would think that the 2013 model is actually a 2012 model.

Builds MOB30D for both models Nexus 7 2013, finaly, available in the list.
https://developers.google.com/android/nexus/images

These builds are uploaded again to nexus pages. And include a lots of bug fixes.

Just flashed new image with WUG, rerooted, flashed Xposed and ElementalX

I'm confused. I flashed MOB30D when Google first posted it, but then took it down. Now MOB30D is back up. Do I need to re-lash it?

DaveImagery said:
I'm confused. I flashed MOB30D when Google first posted it, but then took it down. Now MOB30D is back up. Do I need to re-lash it?
Click to expand...
Click to collapse
They probably took it down for some reason first time. Flash again.

htb2050 said:
They probably took it down for some reason first time. Flash again.
Click to expand...
Click to collapse
These monthly updates while obviously a good thing, there also kind of a pain in the ass. Every month I have to flash the new image, re-root the phone, use Titanium Backup, to go in and delete enough from sys partition, to flash Xposed, followed by flashing my beloved ElementalX kernel. Unless there is some way to streamline all that, a noob like me isn't aware of. Presumably we got just a couple weeks till the May security update anyway. I'll wait.

DaveImagery said:
These monthly updates while obviously a good thing, there also kind of a pain in the ass. Every month I have to flash the new image, re-root the phone, use Titanium Backup, to go in and delete enough from sys partition, to flash Xposed, followed by flashing my beloved ElementalX kernel. Unless there is some way to streamline all that, a noob like me isn't aware of. Presumably we got just a couple weeks till the May security update anyway. I'll wait.
Click to expand...
Click to collapse
Use WUG no wipe option, then root with WUG. Not all that difficult.
Sent from my Nexus 7 using XDA-Developers mobile app

Oreo OTA Now you see it, now you don't

Very strange. I'm on DP4. About 10 minutes ago I checked for an OTA to the new official 8.0 build and hey presto, up came the Android Oreo update available message. When I hit download and install, I got an error message and now the update is no longer available. Just says I have the latest version. Anyone else experience this?

I joined the beta program today. My version is 8.0.0. Is that beta or final?
Sent from my Pixel XL using Tapatalk

SpaceGooner said:
Very strange. I'm on DP4. About 10 minutes ago I checked for an OTA to the new official 8.0 build and hey presto, up came the Android Oreo update available message. When I hit download and install, I got an error message and now the update is no longer available. Just says I have the latest version. Anyone else experience this?
Click to expand...
Click to collapse
I'm having the exact same issue and Google's help don't know ****. She keeps telling me it's not even available even though I can clearly see the update smh
Sent from my Pixel XL using XDA Free mobile app

Mine is stuck like this, lol. I have a great WiFi signal and everything. Not sure what's up.

I have this and amazing Internet speeds.

Exact same issue here

Wonder if it's those that are on DP that are effected, anyone confirm they flashed OTA successfully via DP or N?

It has been removed and is supposed to be online again, that says Google. Waiting and relaxing

I'm now on the latest version according to the updates section. Meh, I'll factory install it in the morning.

According to other threads, they had problems with signature of the update packages being incorrect. They stopped otas, and are dropping them again, I believe.

Just a second ago the OTA was available again. Tried to download it and got the same error message as the first time around. Once again it has been replaced by your system is up to date. Some crazy weirdness definitely going on here. I think I'll try again tomorrow.

noidea24 said:
According to other threads, they had problems with signature of the update packages being incorrect. They stopped otas, and are dropping them again, I believe.
Click to expand...
Click to collapse
Ah, that would explain things.

I started a help session, and they said I needed to be unrooted for the OTA to be able to do anything. I'm going to try unrooting, but tbh I'll probably just end up flashing from the factory image.

SonarMonkey said:
I started a help session, and they said I needed to be unrooted for the OTA to be able to do anything. I'm going to try unrooting, but tbh I'll probably just end up flashing from the factory image.
Click to expand...
Click to collapse
That would be pretty obvious, you can't get system updates if you're rooted on literally any device.

richfreestone said:
That would be pretty obvious, you can't get system updates if you're rooted on literally any device.
Click to expand...
Click to collapse
I knew it wouldn't install, but it usually downloads it so that I can use Flashfire. This time around it seems that it won't even do that.

I have got 2 OTA URLs for build OPR6.170623.011/8.0.0 from my Australian Telstra carrier Pixel XL registered in Beta Program.
One is incremental from DP4, the other I'm not sure but is 951MB.
Will post them up here and update with the exact contents shortly...
64MB:
https://ota.googlezip.net/packages/.../75739c219338945fd6460465b0ec6346c56235ca.zip
Code:
ota-required-cache=0
ota-streaming-property-files=payload.bin:2654:68615126,payload_properties.txt:68617832:154,care_map.txt:569:156,compatibility.zip:772:1841,metadata:63:464
ota-type=AB
post-build=google/marlin/marlin:8.0.0/OPR6.170623.011/4283328:user/release-keys
post-build-incremental=4283328
post-timestamp=1502993522
pre-build=google/marlin/marlin:8.0.0/OPP4.170623.014/4187591:user/release-keys
pre-build-incremental=4187591
pre-device=marlin
951MB for OPR6.170623.012 (it disappeared before i could accept the OTA) (update - is now trying to push this OTA to my Telstra carrier Pixel XL which seems to be incorrect as I should be on the .011 build not .012):
https://android.googleapis.com/pack.../8cfe91d60eafcec2c74e3eef4c2506473b2d7187.zip
Code:
ota-required-cache=0
ota-streaming-property-files=payload.bin:2549:996875675,payload_properties.txt:996878276:154,care_map.txt:464:156,compatibility.zip:667:1841,metadata:63:359
ota-type=AB
post-build=google/marlin/marlin:8.0.0/OPR6.170623.012/4283428:user/release-keys
post-build-incremental=4283428
post-timestamp=1502994895
pre-device=marlin
From another post on XDA for OPR6.170623.012:
https://android.googleapis.com/pack.../80cafb69c50be0fb6ed197998bd7434b26155355.zip
Code:
ota-required-cache=0
ota-streaming-property-files=payload.bin:2654:52977084,payload_properties.txt:52979790:154,care_map.txt:569:156,compatibility.zip:772:1841,metadata:63:464
ota-type=AB
post-build=google/marlin/marlin:8.0.0/OPR6.170623.012/4283428:user/release-keys
post-build-incremental=4283428
post-timestamp=1502994895
pre-build=google/marlin/marlin:8.0.0/OPP4.170623.014/4187591:user/release-keys
pre-build-incremental=4187591
pre-device=marlin

In the US and just enrolled in Beta, got the update, unenrolled in Beta and all is good.

dhaugru said:
In the US and just enrolled in Beta, got the update, unenrolled in Beta and all is good.
Click to expand...
Click to collapse
I tried that, still no OTA update, it's been about 2 hours.
Sent from my Pixel XL using Tapatalk

imnuts said:
I tried that, still no OTA update, it's been about 2 hours.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
No update for me either.
Sent from my Pixel XL using Tapatalk

imnuts said:
I tried that, still no OTA update, it's been about 2 hours.
Click to expand...
Click to collapse
millerd79 said:
No update for me either.
Click to expand...
Click to collapse
And it's coming down now, almost 3-4 hours after signing up for the beta.
Sent from my Pixel XL using Tapatalk

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