• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Closed] Android 12 Update and Root ***Obsolete***

Status
Not open for further replies.
Search This thread

Zorga

Senior Member
Dec 2, 2017
79
10
Google Pixel 5
Alright so I got the update through OTA and updated with no problems, tried reflashing VBmeta but got the corrupt message in recovery of try again or factory reset. tried a couple of times with no luck then used the command ( fastboot flash vbmeta vbmeta.img ) and the phone booted normally but no root obviously

what should I do now if I want root and don't want to wipe my phone? suggestions?
 

thecompany

Senior Member
Dec 17, 2006
209
16
Alright so I got the update through OTA and updated with no problems, tried reflashing VBmeta but got the corrupt message in recovery of try again or factory reset. tried a couple of times with no luck then used the command ( fastboot flash vbmeta vbmeta.img ) and the phone booted normally but no root obviously

what should I do now if I want root and don't want to wipe my phone? suggestions?
How did you get the OTA? Did you unroot first by flashing the unpatched boot.img and then checking for updates in system settings?
 

V0latyle

Forum Moderator
Staff member
From what I'm reading, looks like you can't really safely update from A11 to A12 and then successfully root without wiping even if you use the OTA update method? @V0latyle
It almost seems that way.

Reflashing vbmeta is a solution we found to work on the 12 Beta. I'm glad it worked for some of you; it didn't work for me, as I continually got a corrupt data error until I performed a factory reset.

It is extremely advisable to back up all your photos and data before any update.

For those of you who haven't been able to recover from the "data corrupted" error, see if you can ADB sideload the OTA.
 
Last edited:
  • Like
Reactions: Homeboy76
Reboot to bootloader (use the buttons on the phone)

Try to reflash vbmeta
Code:
fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img

If that doesn't fix it, reflash vbmeta without disabling verification:
Code:
fastboot flash vbmeta vbmeta.img
You'll have to reflash the stock boot image too.

This will get you out of a boot loop, albeit without root, while we try to figure this out.
Hi ! I have flash fhe Fi and do wipe data but Always when flash patch boot doesn't work !? I'm on Android 12 work but how can root it now ? I don't understand ? Please ?
Do flash ota again and vmbeta and patch boot ?
Thanks
 

V0latyle

Forum Moderator
Staff member
Hi ! I have flash fhe Fi and do wipe data but Always when flash patch boot doesn't work !? I'm on Android 12 work but how can root it now ? I don't understand ? Please ?
Do flash ota again and vmbeta and patch boot ?
Thanks
Many users are experiencing issues and we are still trying to figure out the problem. If you need root, you may need to perform a factory flash and wipe data. If you don't need root, try to ADB sideload the OTA.
 

V0latyle

Forum Moderator
Staff member
I ended up having that "corruption" screen when I tried to flash the vbmeta, glad to know I wasn't the only one who dealt with that (and that was before the post got updated to address the issue).
I've been trying to stay on top of it.

Currently the only fix seems to be to perform a factory reset. Everything seems to work just fine after that.
 

PablosCorner

Member
Aug 26, 2018
22
11
pabloscorner.akawah.net
I've been trying to stay on top of it.

Currently the only fix seems to be to perform a factory reset. Everything seems to work just fine after that.
I was able to sideload the OTA update to restore my phone back to normal with my data intact. At least this time, if I really want root back, I can prepare myself to back up all my important data before wiping it.

EDIT: In order to be able to do the OTA sideload to recover from that error, when you press "Try again" on the error screen, quickly press the button combo to boot to bootloader, and then you should be able to access the recovery menu and be able to sideload the OTA update.
 
Last edited:
  • Like
Reactions: V0latyle

V0latyle

Forum Moderator
Staff member
For those of you who have not yet wiped data and are using unrooted Android 12:

As long as your system boots, you should be able to live boot a patched boot image and use that for temporary root:

fastboot boot patched_boot.img

If you are currently stuck at the "corrupted data" message in recovery, try sideloading the OTA or dirty flashing the factory image (with NO FLAGS). If that doesn't work, the only fix that I know of that works is to perform a factory reset...but if you get to that point, you might as well clean flash the factory image with both --disable flags:

fastboot --disable-verity --disable-verification -w update redfin_image.zip

at which point you should be able to flash and boot the patched boot image.
 
Last edited:

pappy97

Senior Member
Dec 5, 2012
235
50
For those of you who have not yet wiped data and are using unrooted Android 12:

As long as your system boots, you should be able to live boot a patched boot image and use that for temporary root:
fastboot boot patched_boot.img

This works beautifully! Yeah it's not persistent, but it works! Every time I install a magisk module, instead of letting magisk reboot it, I reboot into the bootloader and boot the patched image. Works great, thanks!!
 
  • Like
Reactions: V0latyle

PablosCorner

Member
Aug 26, 2018
22
11
pabloscorner.akawah.net
For those of you who have not yet wiped data and are using unrooted Android 12:

As long as your system boots, you should be able to live boot a patched boot image and use that for temporary root:
fastboot boot patched_boot.img

If you are currently stuck at the "corrupted data" message in recovery, try sideloading the OTA or dirty flashing the factory image (with NO FLAGS). If that doesn't work, the only fix that I know of that works is to perform a factory reset...but if you get to that point, you might as well clean flash the factory image with both --disable flags:
fastboot --disable-verity --disable-verification -w update redfin_image.zip
at which point you should be able to flash and boot the patched boot image.
Wow, that's a pretty good workaround until a viable permanent method is discovered for A12. Awesome job! 👏🏼
 
  • Like
Reactions: V0latyle

Dark_Eyes_

Recognized Developer / Recognized Contributor
Sep 19, 2013
2,726
10,678
I know it's a bit OT, but I'm wondering if it isn't some side effect of installing A12 on top of A11 rooted. For now I just boot the patched magisk image through fastboot to prevent having to factory reset, but I might have to in the end. Anyway, am I the only one to see this when going in the At a glance settings?
 

Attachments

  • Screenshot_20211021-155724.png
    Screenshot_20211021-155724.png
    64.3 KB · Views: 48

V0latyle

Forum Moderator
Staff member
I know it's a bit OT, but I'm wondering if it isn't some side effect of installing A12 on top of A11 rooted. For now I just boot the patched magisk image through fastboot to prevent having to factory reset, but I might have to in the end. Anyway, am I the only one to see this when going in the At a glance settings?
I saw that too, and I performed a wipe.

There should be no issue with upgrading from rooted A11. The only issue should be trying to dirty flash the factory A12 image over A11. The proper way to upgrade while retaining data is to use the OTA.
 

Dark_Eyes_

Recognized Developer / Recognized Contributor
Sep 19, 2013
2,726
10,678
I saw that too, and I performed a wipe.

There should be no issue with upgrading from rooted A11. The only issue should be trying to dirty flash the factory A12 image over A11. The proper way to upgrade while retaining data is to use the OTA.
I used the ota. Can you check in the settings if you have the same thing as me? (long press the date on the homescreen, customize, gear icon besides At a glance).
 

V0latyle

Forum Moderator
Staff member
Hm, I suppose we could see what it looks like for someone who wasn't rooted and updated to Android 12 normally, to rule out that happening from root, or the methods to get there.
I originally took the OTA coming from beta 5, but I didn't think to check.

There are some other individuals in here that are unrooted, although I highly doubt this bug would be specific to us rooted folks
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    Update 12-16: I am closing this thread as it is no longer relevant. Please refer to this guide.
    7
    Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before. This needs testing, make sure you back up your data and photos before you try this!

    Q: "If verity/verification are disabled, do I need to enable them now?"
    A: No. The only thing you have to do is update to Magisk 23016.
    Q: "Will enabling verity/verification wipe my data?"
    A: No.

    I will be updating the OP to reflect this.
    6
    Who is calling you stupid?!?! It's an American expression: for example, your costume is ruined by rain, so, you say: it's the weather stupid.

    Anyway, I am trying to help, so, there is no reason to seek insults where there isn't one.
    It's just the way you worded it is all. I am born in America, and actually thought the same thing when I read it.
    It's confusing to me though..

    I would say, not "it's the weather, stupid"
    but rather
    "it's the stupid weather"

    so reading "It's the bootloader stupid"
    I feel should be,
    "it the stupid bootloader"

    but thank you for clearing up that you aren't passing insults.
    And it's hard to tell through text whose being argumentative, and whose being helpful.
    Glad you're the latter.
    5
    Or he/you could add this to it when flashing factory image via ADB only. Why? Because it works on the pixel 4a 5(G) and may work on the Pixel 5. It would not confuse anyone, just provide another less complicated option for upgrading/updating those phones. Seems pretty black and white to me.
    Agreed.

    The confusion arises from this:
    PS :
    Pixel 4a 5(G) phone owners need to know for the initial upgrade (Android 11 to Android 12), they do not need the fastboot flash --disable-verity --disable-verification --slot-all vbmeta vbmeta.img step in this case
    This implies that verity and verification need not be disabled when upgrading from Android 11...which if you want permanent root, is not true. This can be omitted if one flashes the factory image, as they can incorporate the flags into the command:
    Code:
    fastboot update -w --disable-verity --disable-verification image-device-buildnumber.zip
    However, if the update is performed via the OTA, then vbmeta must be specifically disabled.

    If you understand what he is saying, why not add the Pixel 4a 5(G) note to the Reminders?
    This is true across ALL affected devices - Pixels on the SD765G and Tensor. It is not specific to one device.

    Still, I will update the notes for the sake of clarity.
    4
    Who is calling you stupid?!?! It's an American expression: for example, your costume is ruined by rain, so, you say: it's the weather stupid.

    Anyway, I am trying to help, so, there is no reason to seek insults where there isn't one.
    I didn't seek one, I guess I misunderstood. I have never heard of that expression before, at least not in that context. I'm American too, and I've generally heard it like this:

    "Hey, what's making that howling noise?"
    "It's the wind, stupid!"

    I digress.

    I'll have to pick this up later; it's late, my wife is demanding....attention, and I want to enjoy the weekend.