Database Develop

[4.4.4][XT1039][OFFICIAL][TWRP/CWM] Stock Moto G 4G 21.1.46.en.EU

Stock with unlocked bootloader warning removed
Motorola 4G 4.4.4 Kitkat for EUROPE/AUSTRALIA aka XT1039
This is for unlocked bootloader only
Update brings:​
Android 4.4.4 Kitkat
SD Card Fixes
Instructions:
FLASH CWM
WIPE DATA/FACTORY RESET
FLASH ROM
FLASH Super SU (if you want to root)
WIPE DALVIK.
ENJOY!
Only tested with CWM
Dowload:​
Mega
Google Drive
If you want another filehost just ask and if the zip does not work tell me we will look into it :highfive:​

OMG!!!
About root procedure... Did anyone know about it?

Flash this Super SU
Ps: Is my update working ?

I didn't try it yet. I prefer TWRP, so I was going to test if it's working with it. But I just got the XT1039 last week, so I set it up to my liking, then I unlocked bootloader to root it, so second setup, and then I messed up deleting some files (don't really know what happened), so I had to set it up for the 3rd time just yesterday. I'm not in the mood of wiping it again just yet!
But i will
EDIT: Just installed it, with TWRP and wiping only cache. Works like a charm!

I did the update with the file above without any wipe (except cache)
Envoyé de mon XT1039 en utilisant Tapatalk

It works perfectly, thank you!
I was having some trouble updating to 4.4.4 using OTA as I changed a lot in the stock rom. After spending hours reverting changes, I still couldn't get it to work (without flashing stock and starting all over again, which I didn't want to do really).
Was thinking of starting all over again, flashing stock image, OTA to 4.4.4 and changing everything after that, when I came across your thread.
You saved me from spending hours having to start from scratch! Top job!
I only flashed your file from my OTG drive in TWRP , over my heavily changed system, and it works like a dream.
See this screenshot I took right after flashing and reboot:
{
"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"
}
So, yes man, you did it! Thanks again! [emoji106]
Verstuurd vanaf mijn XT1039 met Tapatalk

Nice work Darius.
Also had probs with 4.4.4 OTA due to custom recovery/rooting.
This was easiest way to 4.4.4 happiness....

I want to try this one, but I want to know how can I verify that bootloader is locked or not, and how can I unlock it.
Any threat talking about this?
PD: Could be unlocked from adb typing "fastboot oem unlock"?

Will this work for the XT1039 from Great Britain? Build numbers are the same but instead of EU there is a GB. I bought mine from Amazon and it is the unlocked version.

Awesome!
Hi,
Just installed on my 4.4.3, wiping only the cache partition as you said. As far as I can see everythying works perfectly.
Thank you man !

guijarrelson said:
I want to try this one, but I want to know how can I verify that bootloader is locked or not, and how can I unlock it.
Any threat talking about this?
PD: Could be unlocked from adb typing "fastboot oem unlock"?
Click to expand...
Click to collapse
The bootloader is proprietary so you need to ask Motorola for an unlock code. "Fastboot oem unlock" won't work. There are a lot of threads about this in Q&A and General.

I just finished updating my GB version to this EU version and it worked great! No issues to report. Installed CWM recovery, then EU 4.4.4., wiped cache then installed superuser. Fantastic work with no lost data. My 32GB sdcard works too!!!! AMAZING

I tried using a Sandisk 32 Gb sd card (bought in 2011, and still working perfectly in my old HTC Desire) that didn't work in this phone before the update, but it still doesn't. Have seen other reports about the same issue, so I guess not every sd card problem is solved with the 4.4.4 update.
The card mounts normally, I can see the files on it in any explorer, but it's not possible to read from or write onto the card.
Phone can't format the card, and a check with a Windows pc doesn't show anything wrong with the card.
Strange huh? Any ideas?

I've flashed this and all is working but I can not enable ART can someone else let me know if they can or can't please?

mhisani said:
I've flashed this and all is working but I can not enable ART can someone else let me know if they can or can't please?
Click to expand...
Click to collapse
Do you have xposed framework installed? Art doesnt work with it so...
Second, do you have enough internal memory free?

jkoetsier said:
Do you have xposed framework installed? Art doesnt work with it so...
Second, do you have enough internal memory free?
Click to expand...
Click to collapse
I factory reset the device and still I could not. I flashed the rom via recovery and that seemed to solve it.. perhaps xposed changed something that was not cleared on wipining

mhisani said:
I factory reset the device and still I could not. I flashed the rom via recovery and that seemed to solve it.. perhaps xposed changed something that was not cleared on wipining
Click to expand...
Click to collapse
Factory Reset does not touch your system partition. Only wipes your data.
Xposed would have modified your system partition to prevent ART. Flashing a new rom would restore your system partition to how it was.
Next time, either disable xposed before uninstalling. Or if that doesn't work, either fastboot flash the system.img chunks found in the stock firmware OR flash the same firmware in a custom recovery (if zip available). This will refresh your system partition and restore any changes without affecting your data.

Edit: ignore

Wait so will this work on the XT1045?

I have flashed this ROM and my SD card (Sandisk 16 GB) is still not recognized by the phone. Any advices ?

[Q&A] [RECOVERY LOCKED] Safestrap Recovery v3.75 [2014-06-29 KK B03]

Q&A for [RECOVERY LOCKED] Safestrap Recovery v3.75 [2014-06-29 KK B03]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Hey guys,
I installed safestrap 3.75 on my att note 3 (NC2 version). Couple issues I've noticed. When I reboot the phone, the screen says safestrap: disabled. So I click on "recovery mode". Now I"m in SS and try to back up my stock rom. I select backup, swipe to perform backup. It says backup failed. Questions are how do I get ss to enabled and why did the backup failed? Was ss installed incorrectly in the first place?
TIA.

Cyanogenmod?
Has anyone had any luck with installing Cyanogenmod via Safestrap? I'm currently getting just a black screen with CM11 (M11) or the CM-variant temasek v151.

clamchowder86 said:
Hey guys,
I installed safestrap 3.75 on my att note 3 (NC2 version). Couple issues I've noticed. When I reboot the phone, the screen says safestrap: disabled. So I click on "recovery mode". Now I"m in SS and try to back up my stock rom. I select backup, swipe to perform backup. It says backup failed. Questions are how do I get ss to enabled and why did the backup failed? Was ss installed incorrectly in the first place?
TIA.
Click to expand...
Click to collapse
first of make sure you're running the latest version, second it will say safestrap disabled when you have your Rom in stock slot, it becomes active when you have your stock Rom on stock slot and you create a slot and install your custom Rom in another slot.
AySz88 said:
Has anyone had any luck with installing Cyanogenmod via Safestrap? I'm currently getting just a black screen with CM11 (M11) or the CM-variant temasek v151.
Click to expand...
Click to collapse
With locked bootloader you can't install anything but stock based roms, for our note 3, and you're not flashing kernel either. Until the bootloader get unlocked nothing aosp based or cm we'll boot up.
RoloRacer on KillerKat Note 3

I have used this before on the t-mobile version of the note 3. I used it initially because I didn't want to break Knox. However, I now have twrp fully working on my note, with Knox tripped, but I'm wandering if it is save to use this to dual boot roms. That way I can rock my regular dd, and still boot some rocking aosp roms or some cm. Any thoughts on this would be appreciated.

Where's the .apk?
I followed the links for download at the top of the thread, but once downloaded all I have is a .zip file. There's no .apk in the zip. Suggestions welcome.

Unable to download the Safestrap-HLTEATT 3.1 version.
Unable to download the Safestrap-HLTEATT 3.71 version. Link not working. Please resolve this issue. I am using the at&t note 3 running on jelly bean. I installed safestrap 3.75. It showed installed. But the recovery option is not working. When I click on recovery it simply restarting the mobile. Please help me regarding this issue
Thank you

OC2 is available
Got OC2 update for AT&T Note 3 today when manually checked for software updates.
{
"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"
}

what is the OC2 update? your screenshot still says android version 5.0

Anyone know why I can't get safestrap to mount system? Can't make a backup, it fails during DATA. And if I try to install another rom in a slot, it also fails but for a reason I can't remember atm ...

From rooted Lolipop I did a backup and now the system won't boot. Makes me wish I didn't do the backup.

Does anyone have the safestrap apk for at&t ive looked all over the net and can not find it....
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Never mind 8 found it sorry guys

here ya go http://forum.xda-developers.com/attachment.php?attachmentid=3119865&d=1421514108

I download the safestrap app and installed the recovery, but my phone won't boot into recovery despite installing it. I have a galaxy s5 g900a and I'm running lollipop 5.0 rooted (which I manually flashed via odin).
*update* i downgraded to kitkat and it works perfectly again

Samsung Galaxy Note 3
MY note 3 SM-N900A
will not do anything after i tried to update, and now its saying firmware upgrade encountered an issue. Please select recovery mode in Kies (all versions) and try again, but ive tried that and it keeps saying my phone isnt supported, please help me.

I have a Galaxy Note 3 n900a AT&T and its rooted, busboy installed, Knox disabled and superuser. I followed every step to install safestrap but it doesn't boot into recovery at all. It boots to the Samsung Galaxy note 3 screen twice and then that's it. I've even tried wiping and factory reset and starting over. That didn't work either. Any idea where to go from here? ?

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.

[GUIDE] How to Officially Unlock Z2L Z00RD - ZE500KG Bootloader

I'm not responsible for any damage on your phone. Do it at your own risk. Don't come angry or get mad at me, because I'll totally ignore them. I'm just trying to help, if you think this is dangerous for your phone or not worth it, please do back down.
If my thread here is a duplicate, then please feel free to report it so it would be brought down.
I don't own this device, It was my friends device, and I just messed around with it because he bootlooped the phone by doing things without understanding'em. After getting frustrated over and over, suddenly an idea dawned inside my head to do 'what you're about to do' to your phone. This thread here is just to help other ZE500KG users that are as frustrated as I am (was). I didn't find any guide to unlock the ZE500KG here so I decided to do one. If anyone wants to redo this guide, feel free to do it! I'm just here to help even if with very limited knowledge and resources.
First of all, before reading or doing this guide, I'd like to give you a small note, I WON'T BE GIVING LINKS OF THE FILES ITSELF, please search them yourself, you've got google and the threads here (another reason why I'm not giving you links of the files is because my external HDD got corrupted and I lost nearly every file there is for the Z00RD). Plus I did this unlocking like 8-6 months ago, in frustration, so I've forgotten lots of things about the Z00RD.
Now I'd like to explain whats about to happen:
As you guys might know, the only official bootloader unlocking is only available for the Z00ED. What you are about to do is tricking the Z00RD as if it was Z00ED by flashing the Z00ED's stock recovery and flashing stock rom of Z00ED to Z00RD (I hope some users can automatically get the idea of what to do after reading this). After it boots just download the official unlock tool for Z00ED and unlock it. How is this possible? Currently Z00RD (ZE500KG) & Z00ED (ZE500KL) are siblings. They're using the same hardware inside, the only difference is in the camera and modem. So theoretically we can flash ROMs of Z00ED to Z00RD.
Prerequisites:
First of all, please download the respective stock recoveries of Z00ED as per current OS version. Search for them. There is a link somewhere in the forums, just try searching for it. If you're on Lollipop, download the LP stock recovery of Z00ED (ZE500KL) and if you're on Marshmallow download the MM stock recovery Z00ED. Technically this it's just upgrading to latest stock MM ROM.
Download the final stock rom for Z00ED in ASUS's Official Website
Download the official unlock tool for Z00ED that is in the ASUS Official Website too
Optional:
Download stock recovery and stock ROM of ZE500KG and after the unlocking process is finished try reverting back to stock ROM with stock recovery of ZE500KG <- Just incase you are afraid something will go wrong and don't know how to edit build.prop-s to change your device type.
MOST IMPORTANT IS THAT YOU UNDERSTAND & KNOW HOW TO USE ADB & FASTBOOT COMMANDS! I won't be helping you with this, because I'm pretty sure if you're here on XDA, it means you've done some research and pretty much have the knowledge to use the commands.
Okay lets get started:
Move the downloaded stock rom of Z00ED to your phone (I forgot if it has to be renamed and forgot if it has to be in internal or can be put to external) or you could just skip this and later on uise ADB commands to sideload the file.
Boot to fastboot mode / bootloader
Flash the stock recovery via fastboot
Boot to stock recovery that can be done via fastboot command 'fastboot boot' or manually doing it (I forgot the combinations, I'm pretty sure you guys have this covered)
Once it boots to recovery, install the stock rom of Z00ED that has been downloaded (I'd prefer using adb sideload, but it's up to you guys)
You don't have to wipe data, because if you're on MM the data will stay, if you came from LP, it'll be migrated.
Reboot the device and after it wait until it finishes booting (If you're lucky nothing would go wrong in this step)
After it finishes booting, just install the official unlock bootloader app that you've downloaded, open the app and follow the instructions.
Voila device will reboot and you've (somehow) officially unlocked the bootloader of ZE500KG! You're free to flash custom recoveries, custom roms and blablabla without any restriction!
This last step is optional:
If you're planning on sticking with stock ROM, I suggest you to revert back to ZE500KG stock ROM. I don't know if this is a must or optional, but for safety measures I did this to my friends phone.
Notes:
If you've tried rooting this phone via hotbooting a custom kernel (boot.img) that you've found in the threads here (Sorry if I'm not mentioning any names here) and have the fastboot error in every reboot, this will fix it, but if you plan on sticking with stock rom, you won't be able to flash SuperSU in it, because the su binaries will be occupied. On the other hand, MagiskSU works flawlessly.
If somehow this guide doesn't work for you, Try to do other things, or flash other stock recoveries of different stock rom releases of Z00ED. At least you've got the idea on how it works.
If nothing works for you, maybe you're just unlucky, because as usual, ASUS ships different variants of it's phone that may prove to be incompatible with my guide.
There you go! Happy unlocking! Sorry if my post was semi "TL : DR" or I don't reply your posts ASAP, I'm not always online on XDA. Just try your luck and give it a shot! Trial and error is bound to happen when you're dealing with Android phones. Good luck!

Lucky enough my friend sent me some screenies. If this isn't enough, I'll ask him to make a video to see his unlocked status and device type.
{
"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"
}

How to Officially Unlock Z2L Z00RD - ZE500KG Bootloader
Need Help
Please Contact

Shafkat said:
How to Officially Unlock Z2L Z00RD - ZE500KG Bootloader
Need Help
Please Contact
Click to expand...
Click to collapse
It's all in the first post friend, just read the guide slowly and enjoy the process.

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!