Database Develop

Solution for cant verify OTA update?

My current firmware .242 i did not unlocked boot loader. I did root using king-root. after that i installed nut's dual recovery and flashed superSu.
Now I have received OTA update .270 but i after update download getting error. cant to verify. Also failed using sony pc companion. please give me solution for update. i don't want to flash whole firmware.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

As long as ota update is concerned it will check if u have root.
I had some root issues previously and even though I actually lost root on my ROM, I was able to download but NOT INSTALL due to verification
-----------------------------------------------------
Tapatalked from Sony Xperia Z1
Stock LL 5.0.2 | Root |

I have exqctly the same problem. Just rooted afrer getting lollipop to uninstall bloatwares. Unrooted my device but i am unable to get .270 OTA. after downloading 18mb uodate i get a message saying couldn't verify !
Bootloader is locked and no recovery installed.

I have the same problem. What if we try temporary unroot?

How can we make use of temporary unroot ?

saint_diablo said:
How can we make use of temporary unroot ?
Click to expand...
Click to collapse
In superuser there is a checkbox ☑ in the menu, that reads "temp unroot". I personally have supersu and I am not willing to test it anyway. You can try and report back
Edit: I think I found why we can't update. It's because we have removed the bloatware.

giannism13 said:
In superuser there is a checkbox in the menu, that reads "temp unroot". I personally have supersu and I am not willing to test it anyway. You can try and report back
Edit: I think I found why we can't update. It's because we have removed the bloatware.
Click to expand...
Click to collapse
Only option is to factory reset the phone?

saint_diablo said:
Only option is to factory reset the phone?
Click to expand...
Click to collapse
Because you've uninstalled some system apps. Your rom is changed forever. Factory reset only wipes the /data partition. It cannot restore deleted system apps. If you want so much to update you must reinstall the rom.

giannism13 said:
Because you've uninstalled some system apps. Your rom is changed forever. Factory reset only wipes the /data partition. It cannot restore deleted system apps. If you want so much to update you must reinstall the rom.
Click to expand...
Click to collapse
I just learned the hard way that factoty reset won't solve the problem.
How can i reinstall the rom ?

There are three ways. First you can try repair your with PC companion. By using this way you will update as well, but you will loose all your data and you will get unroot. Second you can install a ftf file with flashtool, depending on the ftf you will get updated or not. And the third way is by flashing any lollipop zip.

First way is good coz its official you wont get any problems. but now repair option not coming now because new update received :/
now sol. is download stock rom and flash. but i am afraid. can i loose something after flash using flashtool?

Confused About Different Options to Root P10 VTR-L09

Hi all,
My build number is
VTR-L09C432B171
I am at the stage where I can now run either of those TWRP version:
1. twrp-3.1.1-0-vtr.img
MD5: 47e83bee437506e1308ca2e29fe30e9c
2. twrp_3.1.1_fromfuture.img
MD5: a4dd832349d345e187b4c125f2a81e18
Before going further, I would like to ask some advice. As a newbie, I want to go SLOW so I don't take a step I might regret.
First, let me clarify my goal. At this stage I am not looking for a custom ROM, but just root access so I can run things like AdAway, Titanium, Uninstall, NotificationsOff...
I found different information about rooting the P10.
For my goal, which will be best?
1. SuperSU-v2.82.zip
http://www.teamandroid.com/2017/04/19/root-huawei-p10-emui-51-android-nougat/
2. Magisk
https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
3. SuperRoot_noverity_nocrypt.zip
https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946
4. fRomFuture
https://forum.xda-developers.com/p10/development/rom-fromfuture-stock-rom-b164-t3657812
Thank you in advance for helping me out of this confusing place!

Hey Mate,
i also did try some of your posted links on my Huawei P10 but i runned in some problems. I think you also need an external SD Card to work with.
My experience so far :
1. SuperSU-v2.82.zip
When i flashed the ZIP, i didnt got any root rights on my devices.
The Phone wasn't brick, but i just had no root rights on it.
I am not sure this is defintly not working, i readed some postive Feedbacks in the internet. Its just my experience.
http://www.teamandroid.com/2017/04/19/root-huawei-p10-emui-51-android-nougat/
3. SuperRoot_noverity_nocrypt.zip
The behavoir was the same like the 1. SuperSu-v2.82.zip
I am not sure this is defintly not working, i readed also some postive Feedbacks in the internet. Its just my experience. Maybe if you got time to try i would be happy to get a Feedback from you.
https://forum.xda-developers.com/p10...0-p10-t3589946
2. Magisk
After my Trys with the Root Zips, i tried to enable the "Root" by systemless Rooting with Magisk.
First i tried the Version 14, which didnt worked for me.
After that i tried the Version 12 from Magisk, which i did exactly like the information as you got from MusicHeat:
https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
This got me the Root rights on my P10.
Important: When you try to Root your phone systemless with Magisk you must have your Stock Firmeware installed. It will get you some error by flashing magisk if you already tried another root methode. Like, if you tried your first or third opinion you have to flash your Stock Firmeware again (i did this in the fastboot with the extractet Update.app (Firmeware) from Huawei. The Boot.img, Recovery.img and System.img (also the Cust.img) is in the Update.app.) To extract the Update.app you can use HuaweiUpdateExtractor from worstenbrood.
https://forum.xda-developers.com/showthread.php?t=2433454
After all i tried xposed Framework on my systemless rooted P10, which was working fine.
The "Hide Root" Methode is also nice to have.
4. fRomFuture
I didnt try that on my own. But there is a requierment that you have prerootet with Magisk.
So in my opinion you should give a try at Number 2 (Magisk).
But its up to you. If you try 1 or 3 Possibility give me a Feedback in this thread
Kind regards

@ChipCollector
Wow, it's really lucky (for me) that you tried all these methods!
Thank you so much for sharing your experience. Isn't it weird that there are web pages out there saying the SuperSU method is the best, when in fact you and others have a completely different experience?
Alright then, based on your comments, I will probably try Magisk.
So far I have only unlocked, not rooted, so starting from a "fresh system".
Just so I am 100% sure I understand what Magisk does:
1. This is not a whole replacement ROM, right?
I am just trying to get root -- for the time being I still want to use the standard camera program for example as I would like to get to know the phone.
2. With Magisk, can you still get Huawei updates, or is that a problem?
Of course I'll go study the Magisk thread, but if you have any thoughts on those, I'd love to hear them.
Thanks, man! :good:

TRY
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
6a or 6b version 100% working!
but still the data partition remains encrypted.
The developer of Twrp describes this error precisely so that it does not work, they are looking for a solution.
It only works if the kernel is turned off by forced encryption and reformatted the whole data partition.

Update:
Tried Magisk v. 14
Device bricked immediately.
Now following unbricking steps from this thread.
Question: for my build number (VTR-L09C432B171) several firmwares are found (see screenshot). How do I know what to choose (OTA-MF / FullOTA-MF?) On that screenshot, where do I click to download a firmware?
Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update: these are three files I can download, looking like the latest on the screenshot (VTR-L09C432B201, FULLOTA-MF)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1901/g1604/v102599/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...99/f2/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...l/VTR-L09_hw_eu/update_full_VTR-L09_hw_eu.zip
Any thoughts on which is more appropriate?

I should add that I did a full backup with TWRP before bricking by installing Magisk 14.
But I am not managing to load TWRP to restore that backup. What I am trying: Press Power, when it vibrates press Volume Up and hold, quickly release power, keep holding Volume Up.
The phone boots into Huawei Recovery, with "Download latest version and recovery" the only meaningful option, and it sees my WIFI connection, but it keeps failing to download.

Update:
- Finally got TWRP to run.
- Restored the backup
- Phone is booting
- After that, tried to run TWRP again to try to install Magisk 12
NotificationsOff and other apps are saying Root Not Available, so I'm not sure what's going on. But at least the phone is booting.

Finally Working
Finally Working!!!
The steps:
- Restored the TWRP backup
- Installed Magisk 12 via TWRP
- Installed Magisk Manager via APK
- Within Magisk Manager, following this advice, checked the two boxes, selected Update, selected Direct (recommended), which updated to Magisk 14. Within SafetyNet Check, both come back Green.
Absolutely stoked. :good:
Huge thanks to everyone who puts these wonderful resources together.

February security patch installation field

hey guys i have bootloader unlocked and unrooted my phone today havent updated January security patch still using December patch but i cant install February security patch it says "Installation problem"
also i have enabled CameraApi2
anyone can help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Relock yout bootloader and try to update.
I was in the same situation, I solved it by relocking the bootloader.

but if i lock bootloader again then i will loose all data on the phone. also when i unlocked bootloader everone said ota keeps updating even if bootloader stays unlocked

ota updates will only work if all the partitions on the device are untouched !
magisk can to restore your original boot.img but if you modified "for example the system partition" in any way such as manually editing "build.prop" ota will refuse to install.
Is very important the way you followed to root on your device,and what you did after that....
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
sry for english

Maharram said:
anyone can help me?
Click to expand...
Click to collapse
Download full stock 10.0.2.0 for fastboot (http://en.miui.com/download-353.html) and flash it using "flash_all_except_data.bat" (thus preserving your data).
Locking phone with /system or /boot partitions changed (seemingly so as OTA is not accepted) is bad idea -> certain bootloop.
More than that, IMHO locking phone even with /system and /boot fully stock is also poor idea, as many users got bootloops with January and February OTA patches on untouched phones.

I will loose all data when I flash stock rom?

daitalos said:
ota updates will only work if all the partitions on the device are untouched !
magisk can to restore your original boot.img but if you modified "for example the system partition" in any way such as manually editing "build.prop" ota will refuse to install.
Is very important the way you followed to root on your device,and what you did after that....
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
sry for english
Click to expand...
Click to collapse
I have enabled CameraApi2 haven't changed anything on system if ı found original build.prop and change it with my edited one I will get ota updates right? after the update i can enable CameraApi2 again

Maharram said:
I have enabled CameraApi2 haven't changed anything on system if ı found original build.prop and change it with my edited one I will get ota updates right? after the update i can enable CameraApi2 again
Click to expand...
Click to collapse
If you have already backup with default settings of buildprop and restore it & If you did root via magisk with correct way , maybe yes you can.But ! the better solution is the way from post above (flash stock rom etc)
https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913

Maharram said:
I will loose all data when I flash stock rom?
Click to expand...
Click to collapse
No, u won't loose data if u use "flash_all_except_data.bat" command file (is inside archive with fastboot image). If u use "flash_all.bat", then u'll erase /data partition.

Aerobatic said:
No, u won't loose data if u use "flash_all_except_data.bat" command file (is inside archive with fastboot image). If u use "flash_all.bat", then u'll erase /data partition.
Click to expand...
Click to collapse
thanks a lot

Maharram said:
thanks a lot
Click to expand...
Click to collapse
Hi..I am facing the same issue. I am on Jan security patch..unrooted..unlocked bootloader and Camera 2api enabled...I get the same error while updating to Feb security patch...did the above method resolve your issue? If yes, can you please provide a stepwise rundown of how you did it?
Your help is much appreciated!

S Advance User said:
Hi..I am facing the same issue. I am on Jan security patch..unrooted..unlocked bootloader and Camera 2api enabled...I get the same error while updating to Feb security patch...did the above method resolve your issue? If yes, can you please provide a stepwise rundown of how you did it?
Your help is much appreciated!
Click to expand...
Click to collapse
hi. I haven't resloved that issue im waiting for major update ı dont want to root remove CameraApi2 and unroot update and root enable CameraApi2. if you want just root your phone remove CameraApi2 and unroot the u can update you phone also u can use other method

Maharram said:
hi. I haven't resloved that issue im waiting for major update ı dont want to root remove CameraApi2 and unroot update and root enable CameraApi2. if you want just root your phone remove CameraApi2 and unroot the u can update you phone also u can use other method
Click to expand...
Click to collapse
Other method? Which one is that?

S Advance User said:
Other method? Which one is that?
Click to expand...
Click to collapse
"Download full stock 10.0.2.0 for fastboot (http://en.miui.com/download-353.html) and flash it using "flash_all_except_data.bat" (thus preserving your data).
Locking phone with /system or /boot partitions changed (seemingly so as OTA is not accepted) is bad idea -> certain bootloop.
More than that, IMHO locking phone even with /system and /boot fully stock is also poor idea, as many users got bootloops with January and February OTA patches on untouched phones."
thanks @Aerobatic for this solution

My device downloaded and placed automatically the february path, however, it didn't installed it - it shows "restart now". I'm really scared about Xiaomi's updates and don't want to install this one based on users reports, however, I rebooted the device (power button - reboot) sometimes and the update didn't installed (thanks God).
I need to know if it will eventually install automatically, or, if I wait enough to the next update, the current update will be overwritten by the new one.
Does anyone know about this?

Maharram said:
"Download full stock 10.0.2.0 for fastboot (http://en.miui.com/download-353.html) and flash it using "flash_all_except_data.bat" (thus preserving your data).
Locking phone with /system or /boot partitions changed (seemingly so as OTA is not accepted) is bad idea -> certain bootloop.
More than that, IMHO locking phone even with /system and /boot fully stock is also poor idea, as many users got bootloops with January and February OTA patches on untouched phones."
thanks @Aerobatic for this solution
Click to expand...
Click to collapse
I am going to carry out this method tonight...If I do this method...will I loose camera 2api?

S Advance User said:
I am going to carry out this method tonight...If I do this method...will I loose camera 2api?
Click to expand...
Click to collapse
yeah becouse this method will reset your system. Your data files will stay (ex: photos, music, app datas etc.)

A question for a developer

What is my twrp password for user 0?
How do I get the phone running after updating to v22?

You need to provide much more information if you want anyone to help you…
What’s you phone brand and model ?
How did you install Magisk ?
What messages do you get ?
After doing what ?
What are you trying to achieve ?
Etc.
Please note that these are basic information that pretty much any person/service looking to help you will ask, be it here on a forum, a service hotline, your car mechanic, and even your doctor.
No one can read your mind, while you know what you did/what happened.
Also a title like "A question for a developer" doesn’t help a lot, as it doesn’t describe what is the issue or your goal.
A much better title could be "TWRP asks me for user 0 password".
Help the others help you !

Xiaomi Mi Mix 3
I update Magisk to v22 via Magisk app
In TWRP i have message: Enter password for user [0]
After update process via app is nessesary to reboot phone, after that it stuck in TWRP asking for password.
Flashing boot.img not help
Flashing same rom without wipe data also doesn't help.
The developer should test the application first. Now I am wasting hours recovering my data and being able to use my phone! It's ridiculous.

QVA said:
The developer should test the application first. Now I am wasting hours recovering my data and being able to use my phone! It's ridiculous.
Click to expand...
Click to collapse
If you did not pay the developer, you have no right to complain.
You got a product for free, without any guarantee, and can’t expect any support either.
You are, however, encouraged to try and solve your problem, post your findings here, and help others.

we know that you update Magisk to v22 via Magisk app the question is how you "install" it... most devices would not have magisk pre-installed on there system

QVA said:
Xiaomi Mi Mix 3
I update Magisk to v22 via Magisk app
In TWRP i have message: Enter password for user [0]
After update process via app is nessesary to reboot phone, after that it stuck in TWRP asking for password.
Flashing boot.img not help
Flashing same rom without wipe data also doesn't help.
Click to expand...
Click to collapse
This is a much better report !
I hope someone will be able to help you out.

I wanted to install using the first option in the application. The terminal showed up, performed some operations and wanted to reboot the phone. After that, only TWRP starts.

It look's like my boot.img file is not patched by magisk, and thats why im stuck in twrp.
There is any way to patch my image without Magisk apk?

QVA said:
It look's like my boot.img file is not patched by magisk, and thats why im stuck in twrp.
There is any way to patch my image without Magisk apk?
Click to expand...
Click to collapse
upload it and i'll patch it

@QVA There's no need for you to keep opening threads regarding the very same issue. You're currently posting about the very same issue in this thread and these two others:
https://forum.xda-developers.com/t/camera-stop-working.4248233/
https://forum.xda-developers.com/t/magisk-v22-update-encrypted-my-phone.4248421/
Keep everything in one thread, it makes it easier to follow the discussion and it keeps clutter in the forum down (please also note forum rule #5).
I suggest that you decide which thread you want to keep discussing this in and report the others for closure (I'm not a moderator in these forums, or I would have helped you with that myself).

Here is the file:
boot.img

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I also tried to remove Magisk but it failed:

Thanks for your time, but the file you sent did not solve the problem.
Still booting into twrp screen.

you device don't run a/b partition like boot_a.img and boot_b.img??

I don't know, it's a normal phone with a normal system. There is a single boot.img file in the system archive.

looking at the magisk uninstaller log you have error "Boot image is patched by other programs! Cannot uninstall!" lmao you really messed up

why don't you just do a factory reset?

I do not want to lose 100gb of photos and application from the bank.

By the way @QVA, was your device encrypted before all this?
And have you tried the default TWRP decryption password (default_password)?
And judging from that photo you posted of the TWRP flash screen you were using an ancient uninstaller... Better to try the current (just rename the Magisk apk to uninstall.zip).

Did anyone else get an Android 12 update notification...on Android 12?

This popped up today and has me completely baffled.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

yeah i got the notification nearly the same time.
u already updated it?

Loisel said:
yeah i got the notification nearly the same time.
u already updated it?
Click to expand...
Click to collapse
Yeah, I updated about a week and a half ago from 12 Beta.
Firmware version on Google's page is still the same...120812.015

V0latyle said:
Yeah, I updated about a week and a half ago from 12 Beta.
Firmware version on Google's page is still the same...120812.015
Click to expand...
Click to collapse
I will update right now from android 11.

Loisel said:
I will update right now from android 11.
Click to expand...
Click to collapse
If you intend on rooting, I'd wait a second....

Yes I got it as well

Maybe they're rolling out an update for Pixel-only-features like they did with the Pixel 6 series.
Until now I didn't get it even with manual search.

Well...I did a clean factory install yesterday, and I don't see an update anymore. It's not posted on the Google firmware pages either, but then again, neither is the new Pixel 6 OTA.
Still see an update available for download but not sure I want to try it quite yet.

Bad news bears.
Installed the update. Rebooted without root, as expected. Rebooted to bootloader, booted the patched kernel. Booted with root. Performed Magisk direct install, rebooted. Boot image verification failure. Reflashed vbmeta with disable flags - got put into Rescue Party. Tried to reflash vbmeta and boot in fastboot, no dice.

V0latyle said:
Bad news bears.
Installed the update. Rebooted without root, as expected. Rebooted to bootloader, booted the patched kernel. Booted with root. Performed Magisk direct install, rebooted. Boot image verification failure. Reflashed vbmeta with disable flags - got put into Rescue Party. Tried to reflash vbmeta and boot in fastboot, no dice.
Click to expand...
Click to collapse
Just happened to me, and I did a fresh install of the A12 release too! Kept getting nagged to install the update, but couldn't find it on the factory flash images page. So thought, I'd go ahead and install it, since there appeared to be no way to make it stop nagging me...now that I type this, there was one thing I forgot to try beforehand...Oh well, looks like my night has only just begun...time to reflash EVERYTHING. If it ain't broke don't fix it...
Also I had the auto system update feature turned off, so I'm not sure how it worked it's way through that setting.
Kind of hating this right now.

ProjectAlly said:
Just happened to me, and I did a fresh install of the A12 release too! Kept getting nagged to install the update, but couldn't find it on the factory flash images page. So thought, I'd go ahead and install it, since there appeared to be no way to make it stop nagging me...now that I type this, there was one thing I forgot to try beforehand...Oh well, looks like my night has only just begun...time to reflash EVERYTHING. If it ain't broke don't fix it...
Also I had the auto system update feature turned off, so I'm not sure how it worked it's way through that setting.
Kind of hating this right now.
Click to expand...
Click to collapse
Same

So I just wiped, re flashed with the flash tool, patched my boot image and everything is running fine again.
I will advise though! For now do NOT update Magisk! Stick with v23000 for now!
The newest release will take some effort to figure out, as far as getting V4A running and other modules since the repo has been removed from the app now. Stay on the older version for now, it will save you a headache.
I updated Magisk and regret it now.

I got the update notification too. I am bone stock, and I was never part of the beta. I went from bone stock 11 to bone stock 12 but it wants me to do a full update to 12. Strange. Well, I'm gonna install it. I got nothing to lose because my P6Pro should be in the mail tomorrow.

chrizzle30 said:
I got the update notification too. I am bone stock, and I was never part of the beta. I went from bone stock 11 to bone stock 12 but it wants me to do a full update to 12. Strange. Well, I'm gonna install it. I got nothing to lose because my P6Pro should be in the mail tomorrow.
Click to expand...
Click to collapse
Same here .. went everything well for you after installing the update again?

ulxerker said:
Same here .. went everything well for you after installing the update again?
Click to expand...
Click to collapse
Installation just finished. As far as I can tell. No issues. Build number is SP1A.211105.002.A1. I wish I had noted the build number before I installed. Doh!

chrizzle30 said:
Installation just finished. As far as I can tell. No issues. Build number is SP1A.211105.002.A1. I wish I had noted the build number before I installed. Doh!
Click to expand...
Click to collapse
Same here. Before, the build number was SP1A.211105.003 but that's how it's supposed to be according to other reports.

chrizzle30 said:
Installation just finished. As far as I can tell. No issues. Build number is SP1A.211105.002.A1. I wish I had noted the build number before I installed. Doh!
Click to expand...
Click to collapse
Since I installed Android 12 the day of the Pixel 6 announcement, I will guess that I was on build number SP1A.210812.015, Oct 2021. This is very interesting because on the Android OTA site, the build that just installed says that this is the Verizon image. I am on Google Fi and I purchased my Pixel 5 from the Google Store.

Today I got an update of Google Play System Update (?) and after that, no more system update available on notification bar or system settings!