Installing the update right now. It'll be the first security update for Pixel 3a.
Here's a link with more details and download links, no 3a specific fixes in the June patch.
https://9to5google.com/2019/06/03/pixel-june-19-security-patch/
Thanks. I checked around 9 EDT but nothing new. Still locked so sideloaded.
I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?
dhoang said:
I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?
Click to expand...
Click to collapse
I don't believe so but... Try and let us know how it turns out. I think the bootloader and stuff is different so I think you need factory image
Sent from my Pixel 3a using Tapatalk
Is it save to update if you're rooted?
jmtjr278 said:
I don't believe so but... Try and let us know how it turns out. I think the bootloader and stuff is different so I think you need factory image
Click to expand...
Click to collapse
It does not work. It was running for a bit then an error message"missing config CONFIG NETFILTER_XT_MATCH_QTAGUID". Oh well I tried. I guess I will have to wait until Google officially includes 3a in it beta program.
BehelitOutlaw said:
Is it save to update if you're rooted?
Click to expand...
Click to collapse
Yup. Works just fine. Just fastboot the modded boot.img provided by @pbanj afterwards and your good to go
Sent from my Pixel 3a using Tapatalk
Your running the old boot.img? Do you know if there is a problem with altering the new boot.img with magisk?
jmtjr278 said:
Yup. Works just fine. Just fastboot the modded boot.img provided by @pbanj afterwards and your good to go
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
Archangel said:
Your running the old boot.img? Do you know if there is a problem with altering the new boot.img with magisk?
Click to expand...
Click to collapse
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
jmtjr278 said:
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
https://drive.google.com/file/d/1eQ9QXQqYeQityqCR2fk2jgBt7UKBA_5P/view?usp=drivesdk
Here is the one I made. Enjoy
Sent from my Pixel 3a using Tapatalk
dhoang said:
I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?
Click to expand...
Click to collapse
No. Cannot go back to pie. I had a discussion with Google rep today. She said soon as the Q beta for this month comes out, we will be able to go back to Android Pie as normal. There is an issue on their side. Here's what my error was when trying to sideload back to Pie on my VZW Pixel 3a
Perfect thanks brother! Saves me some time.
jmtjr278 said:
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
https://drive.google.com/file/d/1eQ9QXQqYeQityqCR2fk2jgBt7UKBA_5P/view?usp=drivesdk
Here is the one I made. Enjoy
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
sd_N said:
No. Cannot go back to pie. I had a discussion with Google rep today. She said soon as the Q beta for this month comes out, we will be able to go back to Android Pie as normal. There is an issue on their side. Here's what my error was when trying to sideload back to Pie on my VZW Pixel 3a
Click to expand...
Click to collapse
Did you try to fastboot pie factory images? That should get you back to pie, kinda weird if not.
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
Did you try to fastboot pie factory images? That should get you back to pie, kinda weird if not.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
He has a VZW Pixel 3a. You can't fastboot a factory image with a locked bootloader. You can only sideload an OTA so he will need to wait in order to unenroll from the beta. Couple more days I think at the most.
Anyone else feel like the Multi tasking UI on the 3a has become faster after the update? Feels snappier to me
Rage1ofakind said:
Anyone else feel like the Multi tasking UI on the 3a has become faster after the update? Feels snappier to me
Click to expand...
Click to collapse
I think so. I have noticed you can swipe up from a bigger portion of the screen to show the appdrawer too. Now I can swipe up from the lower row of icons, and I think that before the update I had to swipe from the icon menu.
How do you even sideload the OTA ? When I do adb reboot recovery I just get a no command screen :/
EDIT: NVM Figured that out. When I sideload the OTA, I just get a signature verification failed error. I have a Tmobile 3a
Edit 2: I am dumb. I had the full image instead of OTA. Getting the OTA worked.
So i download the latest modded version on from pnabj "PQ3B.190605.006" then install it using this method "fastboot flash boot "whatever the boot.img is named" from the root guide and thats it?
oscar1823 said:
So i download the latest modded version on from pnabj "PQ3B.190605.006" then install it using this method "fastboot flash boot "whatever the boot.img is named" from the root guide and thats it?
Click to expand...
Click to collapse
If you have updated to the June security version and want to obtain root, then yes, flash the specific modified boot image. Then open the Magisk app and patch your boot image to complete the process.
12paq said:
If you have updated to the June security version and want to obtain root, then yes, flash the specific modified boot image. Then open the Magisk app and patch your boot image to complete the process.
Click to expand...
Click to collapse
Im already Rooted with magisk.
oscar1823 said:
Im already Rooted with magisk.
Click to expand...
Click to collapse
What are trying to do with the previously mentioned modified image?
Related
https://developers.google.com/android/nexus/images#ryu
https://developers.google.com/android/nexus/drivers#dragon
Is the MXB48J just an older version than MXB48K? Or are they for different hardware?
i'm not sure what is happening with the images. it could be one is u.s.a. and one is international. i've read that upon first boot there is an OTA so it might be one 48j was from factory the 48k is the new update. but i do not think it would be a newer hardwre situation. the binaries are 48k though soit might be a hardware thing. perhaps keyboard related. again complete guessing on my part.
I'm on 48J after getting the 58mb OTA on first boot, got the Pixel C yesterday(I'm in the UK). No system update available to 48k as yet?
Sent from my Pixel C using XDA Premium HD app
I'm also on j, got mine today and during setup it did an ota. I'm in the us
Also now on J in the UK after a small OTA update.
Any news on kernel sources / device tree?
Who have OTA links?
New factory image has been posted for the February security update. Anybody wanna flash it and see if they've fixed the touchscreen and wifi issues?
I'll flash this later today, hopefully it is still compatible with our current boot images.
Sent from my iPhone using Tapatalk
Since Google skipped the Jan update for the Pixel I really hope this one has the fixes for touchscreen etc
Hopefully a Dev can jump in on this and find out.
CharlesW123 said:
I'm on 48J after getting the 58mb OTA on first boot, got the Pixel C yesterday(I'm in the UK). No system update available to 48k as yet?
Sent from my Pixel C using XDA Premium HD app
Click to expand...
Click to collapse
There wss no OTA to 48K it was a developer build not released to the public other than a factory image.
I just did a Clean flash of the latest factory image and at least for me my wifi is back to normal!!! More testing will be required to see if its really fixed but just ran speedtest and looks promising
---------- Post added at 10:30 PM ---------- Previous post was at 10:28 PM ----------
Got a keyboard update as well, having trouble installing it though
andreoidb said:
I just did a Clean flash of the latest factory image and at least for me my wifi is back to normal!!! More testing will be required to see if its really fixed but just ran speedtest and looks promising
---------- Post added at 10:30 PM ---------- Previous post was at 10:28 PM ----------
Got a keyboard update as well, having trouble installing it though
Click to expand...
Click to collapse
Can you unlock and relock the bootloader okay on the pixel c? no bootloader flags or anything?
Roxas598 said:
Can you unlock and relock the bootloader okay on the pixel c? no bootloader flags or anything?
Click to expand...
Click to collapse
Yeah it was easy. I did speak to soon. The issue is not completely fixed. Before I was getting 5 mbps down and 80 up. Now I'm getting 20 down and 80 up. Better, but not fixed. That is on 2.4ghz, 5ghz is fine.
andreoidb said:
Yeah it was easy. I did speak to soon. The issue is not completely fixed. Before I was getting 5 mbps down and 80 up. Now I'm getting 20 down and 80 up. Better, but not fixed. That is on 2.4ghz, 5ghz is fine.
Click to expand...
Click to collapse
The wifi i've never had an issue with tbh and i'm on my 2nd tab.
it was the touchscreen fixes I was looking for but as of yet I haven't heard anything. dunno if I cba unlocking the bootloader etc or waiting for someone to grab the OTA link.
since im off stock recovery i cant apply OTA's if they come out cant I?
Just tried to flash the new update (30 seconds boot delay? WTF!) and it kept failing at the bootloader stage :/
Just relocked it. Guess i'm waiting.
beardymcgee said:
since im off stock recovery i cant apply OTA's if they come out cant I?
Click to expand...
Click to collapse
That is correct. You need stock recovery (along with all the other stock partitions), or the OTA flash will fail everytime. Whenever I want to update, I just flash all the images (except Userdata) from the new factory image that Google posts. That way, I don't have to wait for the OTA.
Roxas598 said:
Just tried to flash the new update (30 seconds boot delay? WTF!) and it kept failing at the bootloader stage :/
Just relocked it. Guess i'm waiting.
Click to expand...
Click to collapse
Just flash them one by one, the flash all scripts always fail for me.
Sent from my Pixel C using Tapatalk
superchilpil said:
Just flash them one by one, the flash all scripts always fail for me.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
I don't think I have ever once had that flashall script work. I don't even know why they include it.
here is the link for reference: https://developers.google.com/android/images
I have a Google play Store phone, but since I have a Verizon SIM it installed the Verizon firmware and so I have to wait until they release. I had hoped this wouldn't happen with Verizon stating they would release the same time as Google, but here I am.
Sent from my Pixel XL using Tapatalk
http://www.androidpolice.com/2016/1...-nmf26o-rolling-today-possibly-android-7-1-1/
Eager for this update!
Are all 3 on the same version now?
ahent said:
I have a Google play Store phone, but since I have a Verizon SIM it installed the Verizon firmware and so I have to wait until they release. I had hoped this wouldn't happen with Verizon stating they would release the same time as Google, but here I am.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I am in the same boat... It should be available shortly (or so I hope). No reason to believe otherwise this soon after release. :good:
I guess it looks like O is for the V version. I wish they would just label this stuff every time.
https://developers.google.com/android/ota#marlin
OTA is up.
7.1.1
Can this OTA be flashed over NPF26J?
New features are also included
From JCASE:
dePixel8 has been patched with the 7.1.1 update. Please dont ask for further support.
JAYNO20 said:
Can this OTA be flashed over NPF26J?
Click to expand...
Click to collapse
The full factory images are available so yes. Just remember to remove the -w command from the script so it won't wipe your data.
Rydah805 said:
The full factory images are available so yes. Just remember to remove the -w command from the script so it won't wipe your data.
Click to expand...
Click to collapse
So the OTA can not be flashed over it then? I am asking about specifically the OTA not the full image.
JAYNO20 said:
So the OTA can not be flashed over it then? I am asking about specifically the OTA not the full image.
Click to expand...
Click to collapse
I didn't try, sorry. I'd assume it'd work but I couldn't be sure as I already flashed the full image.
JAYNO20 said:
Can this OTA be flashed over NPF26J?
Click to expand...
Click to collapse
Try it out and let us know ?
I personally do fully images. Only have like 6 apps installed lol pretty quick set up
JAYNO20 said:
So the OTA can not be flashed over it then? I am asking about specifically the OTA not the full image.
Click to expand...
Click to collapse
Yes it can. I just did it without problem.
---------- Post added at 01:33 PM ---------- Previous post was at 01:33 PM ----------
AmesCell said:
Are all 3 on the same version now?
Click to expand...
Click to collapse
There's only one version available for December.
cam30era said:
Yes it can. I just did it without problem.
Click to expand...
Click to collapse
Excellent!
Hey all, quick question and sorry if this should be in a different section...
I have the VZW Pixel, but used beups depixel8 for bootloader unlock. I am running stock NDE63V with a T-Mobile Sim. Can I flash the factory image with leaving out the bootloader? Or can I go ahead and just flash the whole image without the -w command.
Thanks!
Installing now, this better fix my lack of bluetooth in the car or I'm going to be sad.
Mrbobrowitz said:
Hey all, quick question and sorry if this should be in a different section...
I have the VZW Pixel, but used beups depixel8 for bootloader unlock. I am running stock NDE63V with a T-Mobile Sim. Can I flash the factory image with leaving out the bootloader? Or can I go ahead and just flash the whole image without the -w command.
Thanks!
Click to expand...
Click to collapse
Just take out the -w. I just did and all is good. ??
Sent from my Pixel XL
As the subject? ?
Wondering the same myself. I have not.
Someone did mention on an Android site that the beta users should see the OTA pushed in the next few days.
iceman4357 said:
Wondering the same myself. I have not.
Someone did mention on an Android site that the beta users should see the OTA pushed in the next few days.
Click to expand...
Click to collapse
I've known it take over a week to appear ?
I think they prioritise all the older builds first then push it to us beta users ?
I'll not taking it until there's a way to unlock the bootloader Verizon's March ota update boo. It was too late when the Verizon rep was setting this phone up..
Sent from my Pixel XL using Tapatalk
sykoj82 said:
I'll not taking it until there's a way to unlock the bootloader Verizon's March ota update boo. It was too late when the Verizon rep was setting this phone up..
Click to expand...
Click to collapse
Its been relocked since last fall. It ain't happening man. Very sorry.
has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.
iceman4357 said:
has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.
Click to expand...
Click to collapse
Doubt it will wipe. But you could flash the whole image removing the -w from the bat file.
iceman4357 said:
has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.
Click to expand...
Click to collapse
You can't.
Sent from my Pixel using XDA-Developers Legacy app
---------- Post added at 05:00 PM ---------- Previous post was at 04:59 PM ----------
TonikJDK said:
Doubt it will wipe. But you could flash the whole image removing the -w from the bat file.
Click to expand...
Click to collapse
Only if you are bootloader unlocked.
Sent from my Pixel using XDA-Developers Legacy app
just flash the system img only
pretty simple
I just got the 7.1.2 image OTA on my Pixel XL and Project Fi. My wife's Pixel hasn't got it yet.
Never used an OTA always flash image simple and no problems, I remember in the past sometimes battery drain etc after installing a OTA
no joy yet here on Google Store Pixel XL on Verizon.
Stevez48 said:
no joy yet here on Google Store Pixel XL on Verizon.
Click to expand...
Click to collapse
I've been seeing delays in the Verizon rollout with this OTA, not sure why. I have a vzw Pixel however I'm on Project Fi and got the ota almost immediately. I'm not sure if that changes it or not, however.
We also need separate threads or disclaimers for those with locked bootloaders and those unlocked. To say just flash the image instead of sideloading the ota is ludicrous if the bl is locked. That simply can't be done.
aspexil said:
I just got the 7.1.2 image OTA on my Pixel XL and Project Fi. My wife's Pixel hasn't got it yet.
Click to expand...
Click to collapse
Was your pixel on beta release 2?
Garner said:
Was your pixel on beta release 2?
Click to expand...
Click to collapse
No. It was at v7.1.1 stock.
aspexil said:
No. It was at v7.1.1 stock.
Click to expand...
Click to collapse
Ahh right this thread was intended for people on the beta release ?
I haven't received the OTA yet, I'm on beta 2. I downloaded the update and tried to sideload it, but the installation failed because it says that the beta 2 is a newer build and it won't downgrade. I guess I'll just wait until the OTA from my carrier.
sideloaded the OTA file over Beta 2 tuesday morning and all went fine...have at it! :good:
iceman4357 said:
has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.
Click to expand...
Click to collapse
nozzleman_85 said:
sideloaded the OTA file over Beta 2 tuesday morning and all went fine...have at it! :good:
Click to expand...
Click to collapse
Impossible.
Sent from my Pixel using XDA-Developers Legacy app
Haha yes. Not possible at all to load the existing OTA on the beta build. Google has to release a separate OTA build which it hasnt yet
bobby janow said:
Impossible.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://developer.android.com/preview/download.html
You'll need an unlocked bootloader to flash the images.
You can also sign up for the ota program without an unlocked bootloader being required:
https://g.co/androidbeta
skaforey said:
https://developer.android.com/preview/download.html
You'll need an unlocked bootloader to flash the images.
You can also sign up for the ota program without an unlocked bootloader being required:
https://g.co/androidbeta
Click to expand...
Click to collapse
Thanks!
My phone is not here yet, should arrive today, so I'm going to hold off until I decide that I'm keeping it.
I will enroll my OG Pixel though!
Deleted
Salval said:
That isn't for our devices.
Click to expand...
Click to collapse
They just haven't updated that yet. The system images are available for the 2 and 2 XL so it certainly is for our devices.
I have flashed 8.1 on my XL but it seems to just sit at the Google logo. Verified the checksum so I know the download is fine. Any ideas?
clnzx2 said:
I have flashed 8.1 on my XL but it seems to just sit at the Google logo. Verified the checksum so I know the download is fine. Any ideas?
Click to expand...
Click to collapse
How long you been waiting at the google logo? May take awhile for it to load up
20 minutes+
It doesn't show my new Pixel XL 2 in the ota beta list, just my old Pixel XL.
OTA's are not ready yet for the 2 line - they require manual flash.
But, for what it's worth, I (re)enrolled my OG Pixel and the OTA has not dropped yet.
---------- Post added at 12:35 PM ---------- Previous post was at 12:35 PM ----------
OTA's are not ready yet for the 2 line - they require manual flash.
But, for what it's worth, I (re)enrolled my OG Pixel and the OTA has not dropped yet.
clnzx2 said:
20 minutes+
Click to expand...
Click to collapse
That's kinda long
Images seem bad, flashed successfully and get a device corrupt error. Flash back to 8.0 and things work just fine again. No luck flashing the OTA as well from 8.0 (OPD1.170816.010)
beerbaronstatic said:
Images seem bad, flashed successfully and get a device corrupt error. Flash back to 8.0 and things work just fine again. No luck flashing the OTA as well from 8.0 (OPD1.170816.010)
Click to expand...
Click to collapse
Same here
clnzx2 said:
Same here
Click to expand...
Click to collapse
Color me three!
Whew...thought I had a bunk device.
Welp.
Is it stable? Anything annoying?
Is HDR processing faster as they say it should be?
To those asking "is it stable" or "what's changed" - I don't believe anybody has successfully gotten 8.1 on their Pixel 2 XL yet. I'm with those above who get the red "corrupt" screen and then essentially hangs on a google logo. I went back to the bootloader to reinstall 8.0.
Has anyone tried sideloading the ota file?
https://developer.android.com/preview/download-ota.html
Pixel 2 XL is in the beta list now for the enrollment. I haven't received the update yet though
It boots
Sent from my Pixel 2 XL using Tapatalk
danon.brown said:
It boots
Click to expand...
Click to collapse
OTA or factory image?
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).