Database Develop

Need Help about MM Security Patches

Good Evening! I opened this thread to ask if someone could give me an hopinion about a problem I had on mu Nexus 6 after going back to MM from Android N preview. So today I unenrolled my device and I received a Marshmallow OTA, which was said to be the last one available. But as soon as I updated my Nexus, I saw they sent me the OTA with July's Security patch. I tried to wait and see if september's update would show up but nothing in 2 days. Is it normal and have I just to wait or is it a problem? Have you had same experiences?
P.S. I wiped data and everything soon after updating back to MM.

Does it matter if it's the July patch? These security issues are not those that normally happen to users who don't download warez apps. Use Google Play, and you're safe.
But if you want the most recent version, the download the latest OTA from the Google OTA page, and sideload it.

istperson said:
Does it matter if it's the July patch? These security issues are not those that normally happen to users who don't download warez apps. Use Google Play, and you're safe.
But if you want the most recent version, the download the latest OTA from the Google OTA page, and sideload it.
Click to expand...
Click to collapse
Yes, you're actually right about it, security patches are more or less the same for normal users. Let's say, my first worry is about Android Nougat update, because my stock updater does not seem to work properly these last days after I went back to MM. So I thought it might be a matter of time.

Open beta 19 is out

New beta Oxygen OS update for the OnePlus 7 pro
Details
• Type: beta
Changelog
System
• Improved system stability and fixed general issues
• Updated Android Security Patch to 2020.10
Camera
• Fixed the flashback issue when switched to the front camera in particular cases
Links
• ROM: -Global | OP7P -
https://otafsg1.h2os.com/patch/amaz...gen_13.W.45_OTA_045_all_2010191035_181a6b.zip

This update has my phone clunky. Everything I do is on a delay (typing or keyboard appearing or texts loading/screens loading) or gets stuck (volume up it sometimes goes all the way up and so on). Never had a similar issue. Done multiple restarts, even switched slots, boosted ram. Not sure what else to do.
Suggestions?

Porquiplane said:
This update has my phone clunky. Everything I do is on a delay (typing or keyboard appearing or texts loading/screens loading) or gets stuck (volume up it sometimes goes all the way up and so on). Never had a similar issue. Done multiple restarts, even switched slots, boosted ram. Not sure what else to do.
Suggestions?
Click to expand...
Click to collapse
Ye I believe this update has issue, I'm having wifi issue I'm been disconnecting for no reason. Keyboard delay is also there .

Lol these betas are pretty irrelevant, no meaningful changes. And Android11 roms are solid so.

farhan20 said:
Ye I believe this update has issue, I'm having wifi issue I'm been disconnecting for no reason. Keyboard delay is also there .
Click to expand...
Click to collapse
No problema here, everything works flawlessly
Sent from my OnePlus7Pro using XDA Labs

No problems here too. Everything working fine, fast and smooth.

Anyone on open beta 19 having trouble removing the india.img file, where in the settings it states to login to Oneplus? I've tried using the India Fake Partition Deleter from mauronofrio, attempting to manually delete india.img in TRWP or a root file explorer, and the Overlay Mount Fix by Zackptg5. Any help would be greatly appreciated.

Porquiplane said:
This update has my phone clunky. Everything I do is on a delay (typing or keyboard appearing or texts loading/screens loading) or gets stuck (volume up it sometimes goes all the way up and so on). Never had a similar issue. Done multiple restarts, even switched slots, boosted ram. Not sure what else to do.
Suggestions?
Click to expand...
Click to collapse
Try to wipe cache (boot into recovery and wipe cache).

How do you update this and keep twrp
Is it just flash twrp retention script then flash rom

gap30 said:
How do you update this and keep twrp
Is it just flash twrp retention script then flash rom
Click to expand...
Click to collapse
Flash Full rom zip and Twrp zip file.

Solved. I showed hidden files.
Where is the downloaded firmware update saved? I would like to move it to a prepared folder and do an update via twrp.

unavix said:
Solved. I showed hidden files.
Where is the downloaded firmware update saved? I would like to move it to a prepared folder and do an update via twrp.
Click to expand...
Click to collapse
In the root directory of your internal storage (i.e. not in any folder).

The firmware update beta 19 was downloaded in a hidden folder called .ota. So not right at the root of the repository.

a63548 said:
Anyone on open beta 19 having trouble removing the india.img file, where in the settings it states to login to Oneplus? I've tried using the India Fake Partition Deleter from mauronofrio, attempting to manually delete india.img in TRWP or a root file explorer, and the Overlay Mount Fix by Zackptg5. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Having this issue as well and have tried as you have to fix. Wiping cache does not help as well.
Anyone know how to get rid of this nag?

will this beta update to android 11 beta?

klemen241 said:
will this beta update to android 11 beta?
Click to expand...
Click to collapse
No, update to 11 will come end of 2020, beginning 2021

Update to Oos 11 is supposed to be out in December

vegetaleb said:
Update to Oos 11 is supposed to be out in December
Click to expand...
Click to collapse
I really hope it comes soon. Any source for it coming in December?

Rollback to Android 11

I do hate the new Android interface, large Button in the notification screen, screen that is also always full screen, can't control Chromecast volume with cellphone buttons.
So there is some major bug that are really annoying to me.
Is there anyone who rollback to A11?
Can i just Flash the latest version over Android 12? Is a full wipe required?

Full wipe is required when downgrading. If your bootloader is unlocked, you should be able to use the Android Flash Tool to install a previous build.
If your bootloader is locked, you will have to unlock it in order to downgrade.

V0latyle said:
Full wipe is required when downgrading. If your bootloader is unlocked, you should be able to use the Android Flash Tool to install a previous build.
If your bootloader is locked, you are out of luck unfortunately.
Click to expand...
Click to collapse
Yeah my bootloader is unlocked, well.. Doing the rollback worth it, even if i want to have root on a12 that need to be done for now.
Thanks

Man, it's like I wrote this topic lol.
If we downgrade to Android 11, will it be possible to get all the security updates, or are they included in the latest images available on google.

Lol, 11 is no gem. I'd go back to 10. That is as high as I will go. Apple trashware is what Android has become, a bloated yappy poodle of an OS.
Who left that big Apple into the room?☠

dotmehdi said:
Man, it's like I wrote this topic lol.
If we downgrade to Android 11, will it be possible to get all the security updates, or are they included in the latest images available on google.
Click to expand...
Click to collapse
Just like previous updates, Android 11 on the Pixel series has now been deprecated and will no longer be supported with updates.
blackhawk said:
Lol, 11 is no gem. I'd go back to 10. That is as high as I will go. Apple trashware is what Android has become, a bloated yappy poodle of an OS.
Who left that big Apple into the room?☠
Click to expand...
Click to collapse
While you're entitled to your personal opinion regarding Android versions, your comment is neither helpful nor appropriate in this context. Some of us like Android 12, some like 11, you apparently prefer 10. Everyone has their own preference. I personally don't like the C8 Corvette, and if I were to buy a Corvette, I'd go with the C7 (or maybe keep it old school and go with a C3). But, I'm not going to be disrespectful to someone and imply the C8 is trash because it's a wannabe Ferrari.

V0latyle said:
Just like previous updates, Android 11 on the Pixel series has now been deprecated and will no longer be supported with updates.
While you're entitled to your personal opinion regarding Android versions, your comment is neither helpful nor appropriate in this context. Some of us like Android 12, some like 11, you apparently prefer 10. Everyone has their own preference. I personally don't like the C8 Corvette, and if I were to buy a Corvette, I'd go with the C7 (or maybe keep it old school and go with a C3). But, I'm not going to be disrespectful to someone and imply the C8 is trash because it's a wannabe Ferrari.
Click to expand...
Click to collapse
I'm sorry my question wasn't clear
I meant, if I download the latest image on https://developers.google.com/android/images , will it include the latest patches of Android 11 ? I assume I will not get an invite to update to the latest patches, but directly to Android 12 which is why I wonder if I will also have to install all the ota patches myself

V0latyle said:
Just like previous updates, Android 11 on the Pixel series has now been deprecated and will no longer be supported with updates.
While you're entitled to your personal opinion regarding Android versions, your comment is neither helpful nor appropriate in this context. Some of us like Android 12, some like 11, you apparently prefer 10. Everyone has their own preference. I personally don't like the C8 Corvette, and if I were to buy a Corvette, I'd go with the C7 (or maybe keep it old school and go with a C3). But, I'm not going to be disrespectful to someone and imply the C8 is trash because it's a wannabe Ferrari.
Click to expand...
Click to collapse
You don't need updates.
Don't buy the scare hype.
Almost all malware infections are done by the user and most are preventable.
{Mod edit} 11 is just a bad OS by design.
Android wanted to make it "safe" and "secure" for even the ignorami.
There's no saving ignorami... load at you're own peril
{Mod edit: Language slightly adjusted - regards Oswald Boelcke}

dotmehdi said:
I'm sorry my question wasn't clear
I meant, if I download the latest image on https://developers.google.com/android/images , will it include the latest patches of Android 11 ? I assume I will not get an invite to update to the latest patches, but directly to Android 12 which is why I wonder if I will also have to install all the ota patches myself
Click to expand...
Click to collapse
Take a look at the link you posted. Every update, from the initial release to the most recent, is hosted there. The updates are cumulative, so if you install the latest firmware, it incorporates all previous updates.
blackhawk said:
You don't need updates.
Don't buy the scare hype.
Almost all malware infections are done by the user and most are preventable.
11 is just a bad OS by design.
Android wanted to make it "safe" and "secure" for even the ignorami.
There's no saving ignorami... load at you're own peril
Click to expand...
Click to collapse
If you have nothing productive to contribute, feel welcome to find your way to an OT forum.

blackhawk said:
Lol, 11 is no gem. I'd go back to 10. That is as high as I will go. Apple trashware is what Android has become, a bloated yappy poodle of an OS.
Who left that big Apple into the room?☠
Click to expand...
Click to collapse
There isn't any Android 10 factory image for the Pixel 5..

andybones said:
There isn't any Android 10 factory image for the Pixel 5..
Click to expand...
Click to collapse
That's unfortunate, I thought that may be the case... my bad.
Maybe a custom rom built on Q but this may difficult because Titan M security chip found on the newer Pixels. Don't know if it can be bypassed as it's primary function is security.
In Q scoped storage doesn't appear to be implemented at least with older apps. That changes with R.
At the least I wait for 12 to see wide spread release for a few months before upgrading; let someone else work out/suffer the glitches.

How can I downgrade to 11 I'm not feeling the new update

xstokerx said:
How can I downgrade to 11 I'm not feeling the new update
Click to expand...
Click to collapse
Easiest way: Use the Android Flash Tool. Make sure you wipe data.

I feel the same way about Android 12 and successfully did a rollback (with full wipe unfortunately) using https://9to5google.com/2021/10/21/how-to-downgrade-from-android-12-to-android-11-on-google-pixel/ as a guide.
However, my concern now is how do I block 12 from updating automatically? I've disabled automatic updates under Developer Tools, but is that sufficient? I keep getting popups to update to 12 but so far I've managed to dismiss them. Last time I inadvertently dismissed an update popup like that the phone eventually told me too much time has passed and it will update now without giving me an option to prevent it. Do I need to enable OEM debugging and/or unlock the bootloader to really block OTA updates or is there an easier way?

lapingultah said:
I feel the same way about Android 12 and successfully did a rollback (with full wipe unfortunately) using https://9to5google.com/2021/10/21/how-to-downgrade-from-android-12-to-android-11-on-google-pixel/ as a guide.
However, my concern now is how do I block 12 from updating automatically? I've disabled automatic updates under Developer Tools, but is that sufficient? I keep getting popups to update to 12 but so far I've managed to dismiss them. Last time I inadvertently dismissed an update popup like that the phone eventually told me too much time has passed and it will update now without giving me an option to prevent it. Do I need to enable OEM debugging and/or unlock the bootloader to really block OTA updates or is there an easier way?
Click to expand...
Click to collapse
OEM Debugging won't do anything to prevent updates; disabling Automatic Updates should do the trick. Not sure how to prevent the notification though, I'm on the latest 12 release and still getting an update notification. So are some others that aren't even rooted.

lapingultah said:
I feel the same way about Android 12 and successfully did a rollback (with full wipe unfortunately) using https://9to5google.com/2021/10/21/how-to-downgrade-from-android-12-to-android-11-on-google-pixel/ as a guide.
However, my concern now is how do I block 12 from updating automatically? I've disabled automatic updates under Developer Tools, but is that sufficient? I keep getting popups to update to 12 but so far I've managed to dismiss them. Last time I inadvertently dismissed an update popup like that the phone eventually told me too much time has passed and it will update now without giving me an option to prevent it. Do I need to enable OEM debugging and/or unlock the bootloader to really block OTA updates or is there an easier way?
Click to expand...
Click to collapse
You need to use an adb edit or package disabler to kill it or it will likely force update.
If the update downloads clearing the system cache before it completes may purge it. I haven't tested that though.

Go in settings, apps, In the Google Play services apps notification, there is a system update notification that can be disabled there.
I've format and install A11 back, rooted it, and since October 25, i haven't seen any update notification. I've already tried by the past to let the system update itself with the normal update way and it wasn't able to do it caused I'm rooted.. So i think I'm safe.

blackhawk said:
You need to use an adb edit or package disabler to kill it or it will likely force update.
Click to expand...
Click to collapse
ADB edit or package disabler to kill... what exactly? I'm sorry I'm not that familiar with this specific area.
ShadowJP88 said:
Go in settings, apps, In the Google Play services apps notification, there is a system update notification that can be disabled there.
Click to expand...
Click to collapse
This is only for the notification though while other things do happen in the background still, right?

lapingultah said:
ADB edit or package disabler to kill... what exactly? I'm sorry I'm not that familiar with this specific area.
This is only for the notification though while other things do happen in the background still, right?
Click to expand...
Click to collapse
I might be wrong but the fact of being rooted prevent the update to be pushed.

lapingultah said:
ADB edit or package disabler to kill... what exactly? I'm sorry I'm not that familiar with this specific area.
Click to expand...
Click to collapse
Are you rooted? If so there are better alternatives for you.
Package Disabler is what I use as I run stock. There are numerous threads on XDA about ADB apps and editing. Use Google search to dredge them up, put XDA at the search phase end.

Want to downgrade back to android 10

I am rooted and recently upgraded to android 12 and absolutely hate it. I would really like to go back to android 10 as android 11 had things I didn't like too.
Any issues I may face going back to 10? Is it as simple as doing a clean install of the factory image and rerooting?

The Pixel 5 never had Android 10. It was released with 11.

xunholyx said:
The Pixel 5 never had Android 10. It was released with 11.
Click to expand...
Click to collapse
Fair enough, I'll have to find which version of 11 took the double tap ambient screen (or whatever they called it) away.
Question still remains, any issues with going back to an early version of Android 11?

I thnink it had 1 android 10 when it came out but i can't find it, but i never searched hard

andybones said:
I thnink it had 1 android 10 when it came out but i can't find it, but i never searched hard
Click to expand...
Click to collapse
Yea mine came with Android 10 when I bought it but it updated almost instantly to A11

thatsupnow said:
Yea mine came with Android 10 when I bought it but it updated almost instantly to A11
Click to expand...
Click to collapse
There's not even a factory image for 10 for the p5. I got mine at the end of November and obviously has an update right away. I never thought to check the current version since 11 came out on Oct.
Updated without signing into Google. Unlocked the bootloader before signing in because let's face it, I'm going to root. Might as well unlock it out of the box and avoid the wipe.

ezflip said:
Question still remains, any issues with going back to an early version of Android 11?
Click to expand...
Click to collapse
No - as long as you wipe data.
I would recommend keeping your bootloader and radio up to date; both should be backwards compatible with Android 11.
Your bootloader must be unlocked to downgrade.

V0latyle said:
No - as long as you wipe data.
I would recommend keeping your bootloader and radio up to date; both should be backwards compatible with Android 11.
Your bootloader must be unlocked to downgrade.
Click to expand...
Click to collapse
That's the info I needed. Thank you!

Question April update?

How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol

Why you so eager that you can't wait a few days?

It's available now.

it has been up for about 5 hours

kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
Layoffs, poor employee morale, and Google moving away from innovation and a move to deplete resources from projects/divisions that are not returning enough profit.

If you've ever had to deal with Google customer "service" for any technical issues before, you already know why. Sometimes you get lucky and find a unicorn of a tech to help, but it's usually an infuriating mess dealing with them.
But, to be honest, I'd rather have a delayed update than a rushed and buggy update. Quality control is important.

kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
After all we are all just humans ... they sure have their reasons

I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?

JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
No problems here.

JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
Rooted, Kirisakura Kernel, Apr. update. All good here.

JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.

LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it???
The mobile phone system is running normally.
Click to expand...
Click to collapse
Assuming you're rooted, that message is normal and can be ignored.

JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored.
Click to expand...
Click to collapse
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.

JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored I am root and magisk on my device..
Click to expand...
Click to collapse

Lughnasadh said:
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.
Click to expand...
Click to collapse
I refresh init_boot.img or prompt this message.

Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?

ozyk100 said:
Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?
Click to expand...
Click to collapse
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com

simplepinoi177 said:
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much for that explanation, I'll read up on it from the provided link.

LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
I had the same issue, but everything works normally without any issues. I regularly flash custom roms and factory images, so if you still want to fix this issue, restore a factory image using the Android flash tool.

Any info on whether the fingerprint scanner is being fixed or at east bettered with this?