UPDATING Pixel 5 Factory Image & Re-Rooting

[donlu30]

Just sharing how I do it in case someone is interested in a shorter path:

1. Download the new full factory image
2. Extract the file. Then extract boot.img from the image zip file within.
3. Copy boot.img to your pixel 5
4. Patch it with magisk
5. Move back the patched file, rename it to boot.img
6. Update the original zip file titled image-redfin-r*.zip with the new boot.img file (override the older one)
7. Edit flash-all file by removing -w so it won't wipe your device clean
8. Flash with flash-all

No need to unroot and reroot.

So no need to disable modules or anything?

 

[andybones]

So no need to disable modules or anything?

I always do, and would suggest it, as a Module could very easily be incompatible with the new update. What has worked for me since I've owned the device since release is this:
1) disable all modules (remove them if you want, but I just disable)
reboot
1a) un-hide Magisk if you hide it
2) download the latest factory image
2a) extract and remove the -w from flash-all as to not lose anything
2b) while I'm doing this, I pull the boot.img and put onto my Internal storage sdcard
2c) (optional) backup your internal storage, just incase
3) adb reboot bootloader
4) flash the factory image
5) reboot
6) patch the boot.img from 2b
7) adb reboot bootloader
8) fastboot flash boot magisk_patched_boot.img
9) re-enable the magisk modules 1 at a time
9a) go to the XDA threads of certain modules known to cause issues with updates, and make sure it's compatible BEFORE re-enabling that module
10) done

 

[madmack]

So no need to disable modules or anything?

Never did and my modules always work when I reboot into the new rooted firmware.

 

[donlu30]

So I flashed the update and no problems, but flashing the patched boot I get "failed to write to partition not found". Any suggestions?

I always do, and would suggest it, as a Module could very easily be incompatible with the new update. What has worked for me since I've owned the device since release is this:
1) disable all modules (remove them if you want, but I just disable)
reboot
1a) un-hide Magisk if you hide it
2) download the latest factory image
2a) extract and remove the -w from flash-all as to not lose anything
2b) while I'm doing this, I pull the boot.img and put onto my Internal storage sdcard
2c) (optional) backup your internal storage, just incase
3) adb reboot bootloader
4) flash the factory image
5) reboot
6) patch the boot.img from 2b
7) adb reboot bootloader
8) fastboot flash boot magisk_patched_boot.img
9) re-enable the magisk modules 1 at a time
9a) go to the XDA threads of certain modules known to cause issues with updates, and make sure it's compatible BEFORE re-enabling that module
10) done

So I flashed the update and no problems, but flashing the patched boot I get "failed to write to partition not found". Any suggestions?

 

[andybones]

Never did and my modules always work when I reboot into the new rooted firmware.

It's not a very good suggestion for others to do this, because everyone uses different Modules.
Many Modules need to be updated for each OTA, or at the least, check the files against the new OTA files, and see if the Module needs anything updated within.
Such as these 2 Modules I use:

[February 7, 2022] Pixel Tweaks for Pixel 5 with Color Picker

Badseed Customs Presents Pixel Tweaks Looking for Android 12 Support? Click Here Greetings This is a combination of a Magisk module and Substratum Theme. I originally did this as means to give custom options to people who enjoy the Pixel...

forum.xda-developers.com

[MOD][MAGISK][ANDROID 11] Addon Features for Pixel Devices - Pixel 5 Thread

So what is this? This is a Magisk module that adds the following features to any Pixel 3, 4 or 5 device running on Android 11: Forces Google Sans font system wide 63Accent colors 12Icon shapes 22Fonts Wallpapers Breel 2019; 2020 & 2020a 9...

forum.xda-developers.com

Others may be at a risk of bootloop from this suggestion.
Simply disabling the module takes no more than a toggle off and a reboot, and can save a lot of headache. And they will be at risk of bootloop once on the new OTA and re-enabling the module. Which is why I suggested in my previous post to also enable them 1 at a time, and to better yet, check the XDA thread before hand, especially for known at risk modules such as the ones I linked above.

So I flashed the update and no problems, but flashing the patched boot I get "failed to write to partition not found". Any suggestions?

Umm. Off the top of my head would be something wrong with the patched boot.img (maybe it didn't transfer fully?)
or out-of-date fastboot drivers installed.

 

[andybones]

I always do, and would suggest it, as a Module could very easily be incompatible with the new update. What has worked for me since I've owned the device since release is this:
1) disable all modules (remove them if you want, but I just disable)
reboot
1a) un-hide Magisk if you hide it
2) download the latest factory image
2a) extract and remove the -w from flash-all as to not lose anything
2b) while I'm doing this, I pull the boot.img and put onto my Internal storage sdcard
2c) (optional) backup your internal storage, just incase
3) adb reboot bootloader
4) flash the factory image
5) reboot
6) patch the boot.img from 2b
7) adb reboot bootloader
8) fastboot flash boot magisk_patched_boot.img
9) re-enable the magisk modules 1 at a time
9a) go to the XDA threads of certain modules known to cause issues with updates, and make sure it's compatible BEFORE re-enabling that module
10) done

Hey guys,
Sorry, update on this,
And someone please correct me if I am wrong.
EDIT: disabling the modules is suggested
Disabling the Magisk modules I suppose is more apart of my OCD,
thinking on it again,
I don't believe it to be necessary,
as once the new factory image is flashed,
it flashes the stock boot.img,
which will un-root you,
thus making step 1) disabling all modules, not needed.

 

[donlu30]

Hey guys,
Sorry, update on this,
And someone please correct me if I am wrong.

Disabling the Magisk modules I suppose is more apart of my OCD,
thinking on it again,
I don't believe it to be necessary,
as once the new factory image is flashed,
it flashes the stock boot.img,
which will un-root you,
thus making step 1) disabling all modules, not needed.

So I would say correct, but to an extent. Modules related to themes have given me trouble. Caused me to wipe the other day... But you won't have an issue until you flash the patched boot.

 

[andybones]

So I would say correct, but to an extent. Modules related to themes have given me trouble. Caused me to wipe the other day... But you won't have an issue until you flash the patched boot.

Hey sorry, I think I may be mis-understanding.
So, this is in relation to taking the OTA, and the steps I initially outlined?

If I am reading this correctly, and I may not be.
A Magisk Module with theming components, such as something like this:

[February 7, 2022] Pixel Tweaks for Pixel 5 with Color Picker

Badseed Customs Presents Pixel Tweaks Looking for Android 12 Support? Click Here Greetings This is a combination of a Magisk module and Substratum Theme. I originally did this as means to give custom options to people who enjoy the Pixel...

forum.xda-developers.com

which modified the SystemUIGoogle (Statusbar) and NexusLauncherRelease (Pixel Launcher) .apks --
caused you to have to wipe your device the other day?
Because you didn't disable the Magisk Module with theme before flashing the Factory image?'
I'm having a hard time understanding why this would have caused the need to wipe.

Unless you mean, you flashed the Factory image, then re-enabled the Magisk module 1 by 1 and had an issue.
That would make more sense to me.

And until you flashed the patched boot.img you are not rooted.

As for theme, I mentioned in this post

UPDATING Pixel 5 Factory Image & Re-Rooting

Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...

forum.xda-developers.com

"9a) go to the XDA threads of certain modules known to cause issues with updates, and make sure it's compatible BEFORE re-enabling that module".

 

[donlu30]

Hey sorry, I think I may be mis-understanding.
So, this is in relation to taking the OTA, and the steps I initially outlined?

If I am reading this correctly, and I may not be.
A Magisk Module with theming components, such as something like this:

[February 7, 2022] Pixel Tweaks for Pixel 5 with Color Picker

Badseed Customs Presents Pixel Tweaks Looking for Android 12 Support? Click Here Greetings This is a combination of a Magisk module and Substratum Theme. I originally did this as means to give custom options to people who enjoy the Pixel...

forum.xda-developers.com

which modified the SystemUIGoogle (Statusbar) and NexusLauncherRelease (Pixel Launcher) .apks --
caused you to have to wipe your device the other day?
Because you didn't disable the Magisk Module with theme before flashing the Factory image?'
I'm having a hard time understanding why this would have caused the need to wipe.

Unless you mean, you flashed the Factory image, then re-enabled the Magisk module 1 by 1 and had an issue.
That would make more sense to me.

And until you flashed the patched boot.img you are not rooted.

As for theme, I mentioned in this post

UPDATING Pixel 5 Factory Image & Re-Rooting

Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...

forum.xda-developers.com

"9a) go to the XDA threads of certain modules known to cause issues with updates, and make sure it's compatible BEFORE re-enabling that module".

Actually, your instructions were spot on until I flashed the patched boot. I use swift theme from the playstore that installs a module to give root to theme. When I flashed the patched boot without disabling the module related to the theme, it caused a bootloop and black screen. When I reflashed the stock image I became unrooted but flashbooted twrp to gain access to the folder containing the modules, tried to delete modules as instructed from another source, rebooted and deleted magisk and tried to start over with no avail. I pretty much wiped to keep from having to go back through the a**pain of having to flash a bunch of crap. I had a good backup and usually wipe and start fresh every few months anyway. So the wiping was on me, but I personally will disable modules from now on just in case. It takes 3 seconds to disable a module but 10 minutes to flash a fresh image. I like easy, but that's just me. And thanks for the help in update as it was pretty cut and dry unlike a lot of other threads

 

[andybones]

Actually, your instructions were spot on until I flashed the patched boot. I use swift theme from the playstore that installs a module to give root to theme. When I flashed the patched boot without disabling the module related to the theme, it caused a bootloop and black screen. When I reflashed the stock image I became unrooted but flashbooted twrp to gain access to the folder containing the modules, tried to delete modules as instructed from another source, rebooted and deleted magisk and tried to start over with no avail. I pretty much wiped to keep from having to go back through the a**pain of having to flash a bunch of crap. I had a good backup and usually wipe and start fresh every few months anyway. So the wiping was on me, but I personally will disable modules from now on just in case. It takes 3 seconds to disable a module but 10 minutes to flash a fresh image. I like easy, but that's just me. And thanks for the help in update as it was pretty cut and dry unlike a lot of other threads

Very sorry about the bootloop, even with a backup and knowing it's just part of tinkering, still stinks.
I'll go and edit my post to say to disable the modules before-hand, thanks for posting back in here with the results to help others (and myself).

Can you link me to the Swift you're using? Is this for Android 11 Pixel 5? Or another device? I remember using Swift theme back on Nougat and it was the best.
But I love to be able to help others. This thread is great. @Az Biker did a wonderful job starting this thread, and it has helped me as well!
This being my first Pixel device, I still had to search to find update instructions.
I remembered hearing stories about how everyone kind of has their own method, some even prefer sideloading the OTA if understand correctly.

But disabling the modules, and a quick reboot takes nearly no time at all, like you mentioned, especially compared to re-flashing fresh factory image.

 

[donlu30]

Very sorry about the bootloop, even with a backup and knowing it's just part of tinkering, still stinks.
I'll go and edit my post to say to disable the modules before-hand, thanks for posting back in here with the results to help others (and myself).

Can you link me to the Swift you're using? Is this for Android 11 Pixel 5? Or another device? I remember using Swift theme back on Nougat and it was the best.
But I love to be able to help others. This thread is great. @Az Biker did a wonderful job starting this thread, and it has helped me as well!
This being my first Pixel device, I still had to search to find update instructions.
I remembered hearing stories about how everyone kind of has their own method, some even prefer sideloading the OTA if understand correctly.

But disabling the modules, and a quick reboot takes nearly no time at all, like you mentioned, especially compared to re-flashing fresh factory image.

It's all good bro. I used to wipe 3-4 times a day back in the day when I had the moto razr and the HTC m8 flashing all the time when it was easy and you didn't need a computer!

Yes, swift installer is what I use and it is pretty seamless, without the need for the substratum app. I would definitely check it out and purchase if you like it.

Swift Installer - Themes & color engine - Apps on Google Play

Swift Installer includes themes and a color engine for full theming freedom

play.google.com

 

[nostromo12]

My Pixel 5 is rooted with magisk23 and I want to apply the first time an OTA update.
Therefore I want to check the procedure.
Switched auto OTA to OFF.
Hope that sometime there will be an indication, that the sept update is available.
Then I want to proceed according that guide:

Install OTA Updates on Rooted Android Devices using Magisk (Guide)

Follow this detailed guide to install OTA updates on Rooted Android devices using Magisk without losing root. You will also be able to retain TWRP after the OTA.

www.thecustomdroid.com

Is this a valid option? It seems to be a simple way avoiding all the fastboot staff

 

[nostromo12]

I did the Sept update exactly the way described in No20 of this thread.
It worked like a charm!! Thanks guys!!

Installed modules: acc, universalfix, hardware off

 

[l7777]

My Pixel 5 is rooted with magisk23 and I want to apply the first time an OTA update.
Therefore I want to check the procedure.
Switched auto OTA to OFF.
Hope that sometime there will be an indication, that the sept update is available.
Then I want to proceed according that guide:

Install OTA Updates on Rooted Android Devices using Magisk (Guide)

Follow this detailed guide to install OTA updates on Rooted Android devices using Magisk without losing root. You will also be able to retain TWRP after the OTA.

www.thecustomdroid.com

Is this a valid option? It seems to be a simple way avoiding all the fastboot staff

Should work yes. It doesn't seem any easier to me but would allow you to update without a computer.

And you should definitely disable your Magisk modules during the process.

 

[Az Biker]

Just sharing how I do it in case someone is interested in a shorter path:

1. Download the new full factory image
2. Extract the file. Then extract boot.img from the image zip file within.
3. Copy boot.img to your pixel 5
4. Patch it with magisk
5. Move back the patched file, rename it to boot.img
6. Update the original zip file titled image-redfin-r*.zip with the new boot.img file (override the older one)
7. Edit flash-all file by removing -w so it won't wipe your device clean
8. Flash with flash-all

No need to unroot and reroot.

Just a quick bump to keep it from getting buried

 

[nostromo12]

I updated my pixel 5 to last factory image, but did not disable the magisk modules and and un-hide magisk. Now I have severe crashes when using android auto. could that be the reason? Have I to factory reset and install everything new?

 

[V0latyle]

OP, I recommend updating the title to reflect that this only applies to Android 11.

The process for Android 12 will be slightly different, due to the introduction of boot verification. See my post here which explains how this works.

NOTE: DO NOT DIRTY FLASH THE FACTORY IMAGE TO UPDATE FROM ANDROID 11 TO 12. If you want to preserve data during the update, use the OTA, either via Android Update or via ADB sideload.

Subsequent updates for Android 12 may be dirty flashed.

The key difference:
Vbmeta must be flashed with the DM-Verity and boot verification flags set to Disabled to be able to use a patched boot image, otherwise the bootloader will return an "Unable to load/verify boot image".

If you intend to update via OTA:
1. Extract vbmeta.img from the factory ZIP to your ADB folder. Not yet known if this will have to be done with every update or whether you can use the same image over and over again.
2. Install the OTA and let the update complete, including a reboot.
3. Reboot to bootloader, then re flash vbmeta:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

4. Reboot back to bootloader
5. You can now flash your patched boot image (if you patched it manually) or live boot an older patched boot image, then use Magisk to directly patch /boot.

If you intend to update via factory zip: (DO NOT USE THIS TO UPDATE FROM ANDROID 11 UNLESS YOU WIPE!)

Manually via ADB:
1a. If you use the flash-all script, ensure you edit
"fastboot -w update image-redfin.zip" to
"fastboot -w --disable-verity --disable-verification update image-redfin.zip"
1b. If you prefer to do your updates manually, update bootloader and radio (if necessary) then use the same command as above to update system:

fastboot -w --disable-verity --disable-verification update image-redfin.zip

2. Let the update complete including a reboot
3. Reboot to bootloader
4. You can now flash your patched boot image (if you patched it manually) or live boot an older patched boot image, then use Magisk to directly patch /boot.

Via the Android Flash tool:
1. Select the update file, uncheck all boxes except "Wipe Data, Disable verity" and "Disable verification"
2. Let update complete including a reboot
3. Reboot to bootloader
4. You can now flash your patched boot image (if you patched it manually) or live boot an older patched boot image, then use Magisk to directly patch /boot.

Note: If you update via OTA, you should be able to dirty flash the factory image without a wipe. Make sure the disable flags are set. I personally wouldn't do this as it is redundant and reflashes all the partitions the OTA already updated. This takes about 10 minutes, vs less than 10 seconds to flash vbmeta alone. I would reserve this option for circumstances where you run into problems after taking the OTA.

Hope this helps when the Android 12 public release finally drops!

 

[ZeoFateX]

Sigh, updated via fastboot update, booted fine, went to install patched boot, received the "unable" error message. Came here to search. Followed the disable verity stuff and now I'm getting put into recovery and told 'Cannot load Android system' with both the patched boot image and with the original. Realize I probably should have read before doing that, but any way to revert the verity change or do I need to wipe? Thanks.

Was able to factory data reset ok. Thanks!

@V0latyle

 

[V0latyle]

Sigh, updated via fastboot update, booted fine, went to install patched boot, received the "unable" error message. Came here to search. Followed the disable verity stuff and now I'm getting put into recovery and told 'Cannot load Android system' with both the patched boot image and with the original. Realize I probably should have read before doing that, but any way to revert the verity change or do I need to wipe? Thanks.

@V0latyle

Were you on the beta or Android 11 before you started?

Did you dirty flash?

 

[ZeoFateX]

Were you on the beta or Android 11 before you started?

Did you dirty flash?

Android 11, I used fastboot update. Not the same as OTA.