General [NOVEMBER] Stock/Magisk Patched Boot Images

Search This thread

RetroTech07

Senior Member
Apr 24, 2021
364
274
Google Pixel 2 XL
Google Pixel 6 Pro
These corruption problems seem to come out of nowhere and make no sense, like in your case. One of the reasons I'm one of the few relics who still disable verity & verification (while still removing the -w), just in case there is still something wonky going on 🙃
Corruption issues don't just appear "out of nowhere"; it's usually user error of some sort, except in Googles case where they messed up their own factory images, lol.

Folks just need to be careful in flashing their own image files and disabling Magisk modules to ensure they don't mess up their devices. If you do these things and always follow the updated OP, you should never have any issues.

Disabling verity and vbmeta is not something normal users need to ever worry about, unless you're a developer building your own ROM or doing some sort of debugging. Those options were only mandatory for prior versions of Magisk because it hadn't been updated to support the latest A12 / P6 and its architecture.

Folks will say "but it doesn't hurt anything", yet they still end up with issues at some point because they forgot those tags were disabled during some sort of mod they were setting up on their device.

Just...stop using those tags if they aren't needed and you know why you're disabling them in the first place. It'll save you headaches down the road.
 

Lughnasadh

Senior Member
Mar 23, 2015
4,344
4,855
Google Nexus 5
Huawei Nexus 6P
Corruption issues don't just appear "out of nowhere"; it's usually user error of some sort, except in Googles case where they messed up their own factory images, lol.
When I say "These corruption issue seem to come out of nowhere...", I was specifically referring to what the user I was replying to was experiencing. They said all they did was remove the -w from the flash-all.bat file and updated. They then got into a bootloop with the corruption message. There does not appear to be any user error in this instance and it doesn't appear that Google messed up the April factory image thus their problem seemingly "came out of nowhere". In other words, it doesn't appear the user did anything wrong, yet still experienced a problem that would not normally be expected, thus "coming out of nowhere".
Folks just need to be careful in flashing their own image files and disabling Magisk modules to ensure they don't mess up their devices. If you do these things and always follow the updated OP, you should never have any issues.

Disabling verity and vbmeta is not something normal users need to ever worry about, unless you're a developer building your own ROM or doing some sort of debugging. Those options were only mandatory for prior versions of Magisk because it hadn't been updated to support the latest A12 / P6 and its architecture.
There have been plenty of instances in a variety of situations, including just updating via flash-all, updating via OTA delta, updating via OTA "Install to Inactive Slot", updating to certain Canary versions of Magisk, flashing kernels on certain versions of Magisk, etc., where people have still experienced the corrupt message post Canary 23016 (the version that fixed the initial problem of not being able to boot with a Magisk-patched boot image in December). Even when people have followed updated OPs and have been careful these issues have sometimes occurred. Just look through the threads. Of course, that's not to say that if you don't disable verity and verification you will have problems. There are plenty of instances, even the majority of instances, where people have not disabled those flags and have had no problems. However, there are plenty of examples where people still continue to get the corruption message to this day, for whatever reason, as evidence by the experience of the user I was replying to.

And of course not disabling Magisk mods before updating has been a problem for people. And of course sometimes people aren't careful when flashing. But this does not account for all the corruption errors people have experienced. As stated above, there have been a number of different scenarios where people have ran into the corruption message that have nothing to do with not being careful or not disabling Magisk mods.

Here's just a few quotes from the developer of the Kirisakura kernel posted well after Canary 23016 was released:

"Some users ran into the device is corrupted message for a quite a while now. It not only happens when flashing a kernel.zip, but in the end it seems related to a problem with verity/vbmeta and magisk. I think it´s related to keeping verity/verification enabled (not disabling the vbmeta flags via fastboot) and something just gets scrambled. Check the forums there are a few threads with plenty of cases."

"But given all the issues some people run into, when they end up with the device is corrupted message (seems also to happen when flashing/updating just factory images without the involvement of anything else, at least what I saw in the guide threads) there still seems to be something wonky."

"The issues some users are getting unfortunately have nothing to do with the kernel. It´s a mixture of google having some problems with the corruption thingy themselves as they revealed in the patchnotes
(March 2022) and the other issues are due to magisk canary being experimental canary builds."

Also, if you glance through the Pixel 6 series threads where people have had the corruption message, almost invariably the people that do get this corruption message have not kept verity and verification disabled. The above kernel developer (as well as myself) continues to keep verity and verification disabled to this day because of the continuing problems that those who don't keep it disabled may run in to.

Furthermore, the corruption message does appear to relate to a dm-verity corruption.

dm-verity corruption​

Example RED eio screen:

Red eio device warning screen

Show a RED eio screen if a valid version of Android is found and the device is currently in the eio dm-verity mode


I'll also give you a couple of examples where disabling verity and verification have helped prevent getting the corruption message:

1. When Canary 24303 was released, many, if not all, people using a custom kernel and updated to this Canary version couldn't boot and got the corruption message. Almost invariably it was only those people who had verity and verification disabled that did not get the corruption message. Those who had verity and verification enabled did get the corruption message.

2. When Canary 24304 was released many people got bootloops and experienced the corruption message while having multiple modules installed, including audio mods. Again, almost invariably those who had verity and verification disabled did not get the corruption message.

The above problems were fixed in Canary 24305.



Folks will say "but it doesn't hurt anything", yet they still end up with issues at some point because they forgot those tags were disabled during some sort of mod they were setting up on their device.

Just...stop using those tags if they aren't needed and you know why you're disabling them in the first place. It'll save you headaches down the road.
In fact, I know exactly why I personally keep verity and verification disabled. When people run into the corruption problem, often times the only way to make it disappear is to do a full wipe or clean flash. There have been other instances where people have been able to get rid of that message, such as reverting to an older monthly build, reverting to an older boot image and then updating that boot image, and on occasion just waiting for the next monthly build and then updating. How you got the corrupt message also appears to be relevant in the manner in which you make it disappear. But just going through the threads you'll see that in many, many instances the only way people could get rid of that corruption messages was to do a full wipe or clean flash.

Thus, the reason I personally keep verity and verification disabled is to prevent getting the corruption message in the first place, thus avoiding having to do the steps described above to get rid of the message. And I've described 2 of the situations above where having these flags disabled did in fact help to prevent getting the corruption message. If you go through the threads you'll also see that in almost every instance where people were getting the corruption message, those in the same situation who had the flags disabled did not get the corruption message.

And to my knowledge, I have not seen any issues from anyone I know who continue to keep these flags disabled. Maybe you know of instances where keeping these flags disabled have caused issues? If so, I would appreciate you pointing these out to me.

Again, I'm not saying that disabling those flags is needed, but it can help to prevent getting the corruption message and avoiding the steps described above to get rid of that message. So while you think you are saving me from "headaches down the road", I have actually prevented headaches for myself by keeping verity and verification disabled. To each their own...
 
Last edited:
Question, I downloaded the patched may image and then used the fastboot boot command. I then go to magisk and select to install patched image and it says it was successful, but still no root. Any ideas? Been doing this same process for ages with no issues until now.

EDIT: Nevermind, I redid the process another 4 times and it finally worked. Not sure what was going on but all good now. Thanks OP and everyone else here for the information on this.
 
  • Like
Reactions: Lycidias

RetroTech07

Senior Member
Apr 24, 2021
364
274
Google Pixel 2 XL
Google Pixel 6 Pro
Question, I downloaded the patched may image and then used the fastboot boot command. I then go to magisk and select to install patched image and it says it was successful, but still no root. Any ideas? Been doing this same process for ages with no issues until now.

EDIT: Nevermind, I redid the process another 4 times and it finally worked. Not sure what was going on but all good now. Thanks OP and everyone else here for the information on this.
If all you did was use the "boot" command you have to also flash it as well.

Code:
Fastboot flash boot patched_boot.img

What did you do differently the 5th time that wasn't working before?
 
  • Like
Reactions: jcp2

reaper000

Senior Member
Aug 3, 2009
1,470
1,152
OnePlus 9
  • Like
Reactions: Lycidias and jcp2

Lycidias

Senior Member
Wondering if some kind soul can post a modded A13 boot image for Aug. I did the process before updating (or thought I did, did this during work), and I am now on A13 with no issues, but no root as I did not patch the A13 boot like i thought. Appreciate anyone willing to post as I very much want root again. Thank you in advance.
Here you go:

Added 13.0.0 (TP1A.220624.021, Aug 2022)
 
  • Like
  • Love
Reactions: jcp2 and ozzmanj1
Hey Lycidias, hope this is okay (feel free to use the file I made). I patched my boot image and saved to my Gdrive. Feel to snag this for your use. Lycidia, if you want me to remove the link or if this is in violation of anything, let me know. Not trying to thread jack, just wanted to share.

 
  • Like
Reactions: jcp2 and Lycidias

Lycidias

Senior Member
Hey Lycidias, hope this is okay (feel free to use the file I made). I patched my boot image and saved to my Gdrive. Feel to snag this for your use. Lycidia, if you want me to remove the link or if this is in violation of anything, let me know. Not trying to thread jack, just wanted to share.

Very nice from you, thanks 👍
I'm on vacation (work) at Mallorca and can't patch anything before next week ;-)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 30
    Hello 😊

    I would like to start a thread with all the stock and magisk patched Boot Images for the Pixel 6 Pro and it's updates.

    I'll try to keep this up to date and always use the latest Magisk Stable for patching new images.

    Download Google Drive:

    Stable:

    13.0.0 (TP1A.221105.002, Nov 2022)
    13.0.0 (TP1A.221005.002, Oct 2022)
    13.0.0 (TP1A.220905.004, Sep 2022)
    13.0.0 (TP1A.220624.021, Aug 2022)
    12.1.0 (SQ3A.220705.003, Jul 2022)
    12.1.0 (SQ3A.220605.009.B1, Jun 2022)
    12.1.0 (SP2A.220505.002, May 2022)
    12.1.0 (SP2A.220405.004, Apr 2022)
    12.1.0 (SP2A.220305.013.A3, Mar 2022)
    12.0.0 (SQ1D.220205.004, Feb 2022)
    12.0.0 (SQ1D.220205.003, Feb 2022)


    Disclaimer:
    I am not responsible for what you do with your device. I only upload and/or patch the provided boot images.
    11
    Thank you for trying to keep this up to date.

    Please mind though, everyone, that using someone else's magisk patched boot images can result in problems. It's unlikely, but it has happened - @topjohnwu recommends to always patch the image yourself.
    Additionally, you also won't be able to restore the stock boot image via Uninstall or update via the "Install to Inactive Slot" method in Magisk because there will be no stock boot image that is backed up by Magisk since you didn't patch the boot image on your own device.

    Just something for people to keep in mind.
    11
    Thank you for trying to keep this up to date.

    Please mind though, everyone, that using someone else's magisk patched boot images can result in problems. It's unlikely, but it has happened - @topjohnwu recommends to always patch the image yourself.
    7
    Corruption issues don't just appear "out of nowhere"; it's usually user error of some sort, except in Googles case where they messed up their own factory images, lol.
    When I say "These corruption issue seem to come out of nowhere...", I was specifically referring to what the user I was replying to was experiencing. They said all they did was remove the -w from the flash-all.bat file and updated. They then got into a bootloop with the corruption message. There does not appear to be any user error in this instance and it doesn't appear that Google messed up the April factory image thus their problem seemingly "came out of nowhere". In other words, it doesn't appear the user did anything wrong, yet still experienced a problem that would not normally be expected, thus "coming out of nowhere".
    Folks just need to be careful in flashing their own image files and disabling Magisk modules to ensure they don't mess up their devices. If you do these things and always follow the updated OP, you should never have any issues.

    Disabling verity and vbmeta is not something normal users need to ever worry about, unless you're a developer building your own ROM or doing some sort of debugging. Those options were only mandatory for prior versions of Magisk because it hadn't been updated to support the latest A12 / P6 and its architecture.
    There have been plenty of instances in a variety of situations, including just updating via flash-all, updating via OTA delta, updating via OTA "Install to Inactive Slot", updating to certain Canary versions of Magisk, flashing kernels on certain versions of Magisk, etc., where people have still experienced the corrupt message post Canary 23016 (the version that fixed the initial problem of not being able to boot with a Magisk-patched boot image in December). Even when people have followed updated OPs and have been careful these issues have sometimes occurred. Just look through the threads. Of course, that's not to say that if you don't disable verity and verification you will have problems. There are plenty of instances, even the majority of instances, where people have not disabled those flags and have had no problems. However, there are plenty of examples where people still continue to get the corruption message to this day, for whatever reason, as evidence by the experience of the user I was replying to.

    And of course not disabling Magisk mods before updating has been a problem for people. And of course sometimes people aren't careful when flashing. But this does not account for all the corruption errors people have experienced. As stated above, there have been a number of different scenarios where people have ran into the corruption message that have nothing to do with not being careful or not disabling Magisk mods.

    Here's just a few quotes from the developer of the Kirisakura kernel posted well after Canary 23016 was released:

    "Some users ran into the device is corrupted message for a quite a while now. It not only happens when flashing a kernel.zip, but in the end it seems related to a problem with verity/vbmeta and magisk. I think it´s related to keeping verity/verification enabled (not disabling the vbmeta flags via fastboot) and something just gets scrambled. Check the forums there are a few threads with plenty of cases."

    "But given all the issues some people run into, when they end up with the device is corrupted message (seems also to happen when flashing/updating just factory images without the involvement of anything else, at least what I saw in the guide threads) there still seems to be something wonky."

    "The issues some users are getting unfortunately have nothing to do with the kernel. It´s a mixture of google having some problems with the corruption thingy themselves as they revealed in the patchnotes
    (March 2022) and the other issues are due to magisk canary being experimental canary builds."

    Also, if you glance through the Pixel 6 series threads where people have had the corruption message, almost invariably the people that do get this corruption message have not kept verity and verification disabled. The above kernel developer (as well as myself) continues to keep verity and verification disabled to this day because of the continuing problems that those who don't keep it disabled may run in to.

    Furthermore, the corruption message does appear to relate to a dm-verity corruption.

    dm-verity corruption​

    Example RED eio screen:

    Red eio device warning screen

    Show a RED eio screen if a valid version of Android is found and the device is currently in the eio dm-verity mode


    I'll also give you a couple of examples where disabling verity and verification have helped prevent getting the corruption message:

    1. When Canary 24303 was released, many, if not all, people using a custom kernel and updated to this Canary version couldn't boot and got the corruption message. Almost invariably it was only those people who had verity and verification disabled that did not get the corruption message. Those who had verity and verification enabled did get the corruption message.

    2. When Canary 24304 was released many people got bootloops and experienced the corruption message while having multiple modules installed, including audio mods. Again, almost invariably those who had verity and verification disabled did not get the corruption message.

    The above problems were fixed in Canary 24305.



    Folks will say "but it doesn't hurt anything", yet they still end up with issues at some point because they forgot those tags were disabled during some sort of mod they were setting up on their device.

    Just...stop using those tags if they aren't needed and you know why you're disabling them in the first place. It'll save you headaches down the road.
    In fact, I know exactly why I personally keep verity and verification disabled. When people run into the corruption problem, often times the only way to make it disappear is to do a full wipe or clean flash. There have been other instances where people have been able to get rid of that message, such as reverting to an older monthly build, reverting to an older boot image and then updating that boot image, and on occasion just waiting for the next monthly build and then updating. How you got the corrupt message also appears to be relevant in the manner in which you make it disappear. But just going through the threads you'll see that in many, many instances the only way people could get rid of that corruption messages was to do a full wipe or clean flash.

    Thus, the reason I personally keep verity and verification disabled is to prevent getting the corruption message in the first place, thus avoiding having to do the steps described above to get rid of the message. And I've described 2 of the situations above where having these flags disabled did in fact help to prevent getting the corruption message. If you go through the threads you'll also see that in almost every instance where people were getting the corruption message, those in the same situation who had the flags disabled did not get the corruption message.

    And to my knowledge, I have not seen any issues from anyone I know who continue to keep these flags disabled. Maybe you know of instances where keeping these flags disabled have caused issues? If so, I would appreciate you pointing these out to me.

    Again, I'm not saying that disabling those flags is needed, but it can help to prevent getting the corruption message and avoiding the steps described above to get rid of that message. So while you think you are saving me from "headaches down the road", I have actually prevented headaches for myself by keeping verity and verification disabled. To each their own...
    5
    I just flashed the April update 3 times on this update and it fails and leaves me bricked every time, Be careful!
    I updated to April via flash-all with no problems. Rooted with the latest Canary (24305). What process did you use? Did you disable any mods you have beforehand?

    EDIT: Maybe you should try patching your own boot image instead of using the one provided to see if that works?