Google Pixel 6

Google finally released the December security update for both the Google Pixel 6 and the Pixel 6 Pro devices.

If you already rooted your device then you will not be able to access the next over the air or OTA update on your device like normal. Now you need to manually install the December security update after getting the root access on your device and one of the ways through which you can manually install the update is via fastboot.

The reason for which we have to do an extra step to install the update is that there is a Magisk manager installed on our Google Pixel 6.

We have already written a step-by-step guide on how to root the Google Pixel 6 using Magisk Canary build. So, if you’re not familiar with how to do that you can check it on our website.

To root our device using Magisk Manager requires us to disable verity and verification in order for Magisk manager to load.

If we want to install the over-the-air update via the normal method then the update will flash the VB meta image file without disabling verity or verification.

We need to disable both the verity and verification to root our device, if we don’t do that then we need to wipe the system clean again.

So, now in order to update our Google Pixel 6 and the Pixel 6 pro to the latest December security update while they have root access with Magisk, we need to install this update in a very specific way.

We have to download the factory images for this update so we go to the nexus and pixel factory image website. You will find firmware files for both the model on the website and then you will need to download the specific firmware that is the next update in line.

So, we have the November update installed on our device and we are going to update to the December one, so we have downloaded the December firmware on our PC.

Next, we have to boot our device in fastboot mode and again if you are not familiar with this, we have a step-by-step guide on how to boot your phone into fastboot mode as well.

We can either boot our Google Pixel 6 into fastboot mode via the button combination or we can do it via ADB command and again we have mentioned both these steps in our detail guide.

For this tutorial we just did the ADB reboot bootloader command from a command prompt on our PC while our device is connected to the PC via USB cable and USB debugging mode is enabled on our phone. Your device will accept that command if USB debugging is enabled from the developer’s option on your device.

Extract the firmware file that you just downloaded; you will get a new folder with a number of different files.

Copy all these files and paste them into the same folder as your ADB and fastboot tools folder.

Once those files have been moved, we need to make a couple of changes.

If you are using Windows operating system then you have to use the “flash all.bat” file from the files that you just copied into ADB and the fastboot tool folder. If you are using Linux or macOS you have to use the “flash all.bat” file.

We are using Windows OS for this tutorial so we are going to stick with the “.bat” file.

Right-click that file and click edit now toward the bottom of this file. A notepad document will open containing the content of that file. Toward the bottom of that file, you will see a command that’s typed out fastboot -w update and we just need to delete that -w from the command. So that this command simply becomes “fastboot update image”, then simply save and close the file.

There is an additional zip file in the files that you just copied in the ADB folder which also needs to be open it.

There you will see a number of other files with the vbmeta.img file being one of them.

Remember if we flash this vbmeta.img file like normal then it’s going to remove the verity and verification that we have disabled, it will enable those again.

Delete that vbmeta.img file from the list of files in that zip folder. You can even double-check it by opening up that zip file again.

After we have removed that -w and the vbmeta.img file from that compressed file. Again, all of these files are going to be moved or copied into your ADB and fastboot tools folder.

The next step is to open up either a command prompt or a terminal or a windows PowerShell within the same ADB folder where you have copied the firmware files.

Type out the command flash and just press the tab button to auto-complete that file name in the command prompt. It is likely going to show up something like “.\flash-all.bat”.

We can execute this flashall.bat file by pressing enter on the keyboard and you will see the script run and it’s going to flash a number of files to our device.

During the process, our phone will reboot a couple of times and we just need to be patient.

Don’t touch your phone or unplug it from the PC while the script is still running. Just wait and let the script run completely.

You will see that your device will reboot again when the process is finished. You will see a finished message in the command prompt along with a message “Press any key to exit”.

Press any key to exit and unplug your device from the PC after your device reboots on its own.

Just wait and be patient for the phone to boot up.

It is also worth mentioning that during all this process you will not lose any of your data.

After you boot back into Android, go into settings and you will see that you are on the latest 5th December security update. The build number of the firmware file also matches the newly downloaded firmware build number.

After you manually install the latest update, you will see that you have lost the root access of the device as you have flashed an unmodified boot image file.

This is because Magisk currently has a conflict with this December update. The developer of Magisk is currently working on an update to this so we will get the support coming soon.

Experiencing difficulties with your Device, check out our “How To” page on how to resolve some of these issues.


Please enter your comment!
Please enter your name here