yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
It seems to me that the OP is specifically about disabling verity and verification. I don't think there's anything about the OP that is wrong. The same user has a more detailed thread about the subject here: ****READ THIS BEFORE UPDATING!*****
[Google Pixel 6 Pro] 93fuelslut:
So my phone is picked up under "adb devices" and will adb to bootloader, but says waiting for devices when you fastboot nflashing unlock.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I know you said in the other thread that you updated the drivers, but I just wanted to share that when I used adb on the phone while it was fully booted up, I didn't have to install any drivers in Windows. When I was booted into recovery mode, I then had to install the latest Google drivers.

I'm only mentioning in case it shows in Device Manager that it doesn't have a driver installed after you boot to recovery.

Also, you're using the latest official Google platform tools? Sorry if you already mentioned it.
[Google Pixel 6 Pro] HankMcCoyX:
I followed the steps to root and am in a bootloop. If I try to enter recovery I get the android with a red triangle and exclamation with no command listed underneath.

Any tips on how to fix this?

Thanks!
[Google Pixel 6 Pro] V0latyle:
Bootloop, as in continuous? Or the device reboots to Rescue Party?

To enter recovery, you have to use the key combo - when you get the image of the Android with the red triangle, hold down Power and click Volume Up to enter the menu.
[Google Pixel 6 Pro] HankMcCoyX:
Turns out the phone was unhappy with the cable I was using. I had several flashes of the factory image fail when trying before I realized to try a different one.

After reflashing I got the correct events to happen.
[Google Pixel 6 Pro] 93fuelslut:
Yeah I installed the latest Google drivers but still isn't listed in device manager on my PC. I'll have to check which platform tools I'm running
[Google Pixel 6 Pro] 93fuelslut:
So I think I'm on the latest a12 so hopefully it's not beta. If I'm not rooted, I can just download an older version of magisk and install that normally? As in just patching the boot image
[Google Pixel 6 Pro] V0latyle:
Magisk 23001 and older doesn't seem to work to patch the Pixel 6/Pro boot image; you have to use 23010 or newer.

Many modules are going to be ported to Zygisk anyway so I'd recommend just using the latest Canary, 23015.
[Google Pixel 6 Pro] 93fuelslut:
So if I want root, I have to follow the OP guide?
[Google Pixel 6 Pro] V0latyle:
This is an information only thread, and as such, there is no guide. However, here is the guide I wrote for the P6/P6 Pro.
[Google Pixel 6 Pro] Dragon Kumera:
Using ssd boost app and adaway plus custom bootanimation are really the only reasons I root.
[Google Pixel 6 Pro] V0latyle:
Please don't ask the same question twice. It will be answered eventually.

Update to Magisk 23016. If possible, do this from within the Magisk app. If you are using the Alpha, you will need to remove it, then install 23016.

After doing so, you can update however you want, and root normally by patching the boot image. Disabling verity/verification is no longer necessary with Magisk 23016.

Update to Magisk 23016 first. See above. Then, dirty flash the factory image; I recommend using Android Flash Tool, as this is easiest.

There is no need to re-enable verity/verification if disabled. Just don't worry about them at next update.
[Google Pixel 6 Pro] V0latyle:
Given that most of this information is now irrelevant, this thread will be closed. Please move discussions to this thread.
[Google Pixel 6 Pro] V0latyle:
I have no idea, but there are a couple ways us Pixel 5 guys can test this.

One way is to just reflash unmodified vbmeta and boot, then attempt to disable verity and verification, and flash the patched boot image again.

The other way, which I feel would be more appropriate, would be to start with a clean install of Android 12, set up the device, then attempt to disable verity/verification and flash the patched image.

It sucks not knowing exactly what is causing our data corruption issue. For some odd reason it seems like the only way to root on Android 12 is to have a clean install...BUT there's no saying how old that original clean install can be.
[Google Pixel 6 Pro] Golf c:
Been rooting and roming since Nexus 4. I'm really starting to wonder if it's even worth it anymore.
[Google Pixel 6 Pro] plasticarmyman:
i've been rooting and roming since Android 2.1, it's still worth it even if only to block ads at the host level without using a vpn.

A lot of the things i used to root/rom for are easily done now without root but we shall see...
[Google Pixel 6 Pro] darbylonia:
So worth it, because we know how! I've been rooting and ROMing since OG Droid! I'm all in and not giving up! And I'm a girl!
[Google Pixel 6 Pro] galaxys:
You go girl! Root is an XDA addiction that is hard for me to shake...😳😁📴
[Google Pixel 6 Pro] Golf c:
My passion has been waning lately, I will admit. It was very exciting for years. Lot's of clean flashing. Haha. We shall see what kind of development this phone will bring. Hopefully something that will stoke my passion again.
[Google Pixel 6 Pro] V0latyle:
Same here, old timer! I remember thinking that slide out keyboard was cool, as I was coming from a Blackberry at the time...then pretty quickly realized it was easier to just use the on screen keyboard.

Remember how damn small those screens were?
[Google Pixel 6 Pro] darbylonia:
Yeah! I loved having the option of on screen keyboard vs. the physical one. The OG Droid was amazing at the time. The UI was so sophisticated. I was hooked on Android and never looked back. When screens started getting bigger I hopped from that to the Droid X which at the time was HUGE. I'm just passionate about Android history and development.:love:
[Google Pixel 6 Pro] roirraW "edor" ehT:
Every few years I get my HTC Droid Eris out and compare it's size side by side with whatever I'm using now. What was it, 3.5 inch screen!? LOL! I always think about how cute the old phone is compared to my modern choices. It's so tiny!
[Google Pixel 6 Pro] vibrantliker:
V4A is what rooting is for!
[Google Pixel 6 Pro] Cares:
I have a Pixel 4XL that's on Android 12 and I did not have to do any extra steps to root.
[Google Pixel 6 Pro] marvi0:
Haven't rooted in years, but gravity box, used to be the first mod I install. Just curious, what do you like about it most please?
[Google Pixel 6 Pro] V0latyle:
I was trying to remember one of the phones I had, I'm pretty sure it was an HTC...small black thing with an optical trackpad.

You really begin to appreciate how far technology has come when, like in my case, your first computer was a 486 running Windows 95...cell phones were giant bricks and weighed 10 pounds...and my laptop was a Windows 3.1 machine with a non-backlit monochrome display.
[Google Pixel 6 Pro] bobby janow:
But do you remember Gopher, Compuserve, MS-Dos, DRDos, and one of my favorites O/S 2? I'm not sure how long I used Windows 1.0 because 2.0 quickly followed and then lo and behold we could open 2 windows if we had at least 640k ram and ran in protected mode. But I digress..

I remember reading a post from Chainfire saying that it was not in our best interest to root if we run apps like banking. I was rooting all the time, flashing like crazy and then I locked the bootloader on my 5X, unlocked it again once then locked it for good. Do I miss root, yeah sometimes. TiB and V4A are the two I miss most but so many things have changed with the security checks these days. I still read every rom and root thread and will never buy a device I can't bl unlock but it's just been so long now. Lastly, I remember not only my Eris (which I recently charged and fired up only to see SetCPU on my homescreen and OC'd to 750) but flashing a test rom from @letmedanz 8 times in one night trying to figure out why the darn camera wouldn't work. Maybe one of these days I'll keep my device instead of trading it in and attempt root and flash a rom. And while I was typing this I got notification that my P6 has shipped. :-))
[Google Pixel 6 Pro] V0latyle:
I grew up playing the original Doom and Terminal Velocity....so yes, I'm painfully familiar with DOS lol

I remember that post too. I've rooted every single device I've ever had. I refuse to give up control over my device and software. That's why I run Enterprise LTSC on my computers, so I don't have to deal with all the annoying "feature updates" that the General Availability Channel gets.

Like my wife's computer. Every time it loses connection with the Internet (such as when my router performs its scheduled reboot at 0200) it decides that the best way to test the Internet connection is to open a browser window to MSN. My Enterprise machines don't care.
[Google Pixel 6 Pro] swieder711:
I primarily make Lock screen and status bar tweaks with Gravity Box. I also enable the Adv Reboot menu on the power button.
[Google Pixel 6 Pro] marvi0:
Thanks, does magisk still have the feature to force expand the notifications shed or panel. Gosh I miss that feature 😂.
[Google Pixel 6 Pro] Ghisy:
The HTC Desire maybe? It was my first Android smartphone! The HTC version of the Nexus One!
[Google Pixel 6 Pro] V0latyle:
No, I never had a Desire. Maybe I'm confusing two phones. The only HTC models I remember having were the Incredible and the Rezound. I can't remember what I had after my Droid, if anything, before I got the Inc.

I did have a Blackberry Curve 8530, but what I'm thinking of is a small round sensor very much like the Desire's.
[Google Pixel 6 Pro] Slim2none4u:
Delete double post
[Google Pixel 6 Pro] Slim2none4u:
I can confirm this on 2 devices. Pixel 3xl and Pixel 4a. I used the tried and true method of patching and flashing the boot.img with no issues.
[Google Pixel 6 Pro] GohanBurner:
If Google could just create a system-wide equalizer and allow us to force all apps to go past the camera cutout then I wouldn't need root anymore.
[Google Pixel 6 Pro] V0latyle:
Okay, so it's just the 4a, 4a 5g, 5, and 5a that this affects...and likely the 6 / 6Pro.

And just to be clear, while I doubt a data wipe will be necessary for devices that started with a clean Android 12 install...disabling dm-verity and vbmeta verification will still be necessary for Android 12, regardless of whether you upgraded or your device shipped with it.
[Google Pixel 6 Pro] diesteldorf:
Just wanted to give you a public shoutout and thank you for the bit of tech support. I was able to revert back to Magisk 23001, install RIRU, and Universal SafetyNet fix, and now I am back to officially passing Safetynet and all banking apps are working.

I appreciate it.
[Google Pixel 6 Pro] danw_oz:
Same here, which is shy I was wondering about the chat around this, on top of that I was only using Magisk 23 didn't want to change to loose Magisk hide, for banking apps, and some other random ones.
[Google Pixel 6 Pro] danw_oz:
Lol, same here. In fact I still have that phone at home, was an amazing phone with exception of the memory
[Google Pixel 6 Pro] Lughnasadh:
It's because starting with the Pixel 5 (maybe the 4a as well?) you have to do those extra steps when on Android 12. I think we're all just assuming this will be carried over to the Pixel 6. This is true even when using Magisk 23. Previous Pixels don't seem to be affected by this.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I want to be 100% clear - this is on the Pixel 4 XL you're talking about, correct? Not the Pixel 6 Pro. Just want to make sure I know if someone already threw caution to the wind and successfully rooted their Pixel 6 Pro. :D I'm not brave enough before the official firmware update zips come out.
[Google Pixel 6 Pro] V0latyle:
You aren't going to be able to root until the firmware comes out anyway, because to root you have to patch the boot image, and there's unfortunately no way to pull the boot image from the phone without root or TWRP.

You can however unlock your bootloader, although it's pretty pointless at this time given the lack of anything to flash.
[Google Pixel 6 Pro] diesteldorf:
You are correct. I check both forums, but I've had every Pixel, except the 5, and they have a lot of similarities for rooting, and differences too.

I figured someone knew the answer to my dilemma, so I posed the question and will probably use that same knowledge in a few days, once firmware is released and my Casemate case arrives.

Rooting doesn't scare me as much as dropping the phone without a case...LOL
[Google Pixel 6 Pro] V0latyle:
Well, we just have a particular challenge that we need to figure out first - how to gain permanent root without wiping /data. This seems to be particular to the 4a, 5, 5a, and I would assume the 6 as well.

Previously, on Android 11 on all Pixels, we could just flash a patched boot image, and be on our merry rooted way.

However, with the 12 Beta, we discovered that /vbmeta comes into play; flashing a patched boot image would result in "failed to load/verify boot images" at boot, which we discovered could be prevented by reflashing vbmeta with --disable-verity and --disable-verification.

Unfortunately, on the 12 stable, doing this causes the device to bootloop into recovery with a message "Can't load Android system. Your data may be corrupt". If the user chooses to wipe data, they can successfully run permanent root; otherwise, /vbmeta and /boot have to be reflashed to stock, although temporary root can be gained by live booting a patched image from fastboot.
[Google Pixel 6 Pro] Quinny899:
Cheers for this, much appreciated. I can confirm (yet again) that you have to do disable-verity to root the P6 Pro. It's early enough since getting the phone (literally today) that wiping data isn't too much of a hassle at this stage IMO.

Factory images are now up, I've just booted a freshly wiped phone with a magisk patch image, transferring stuff again now :)
[Google Pixel 6 Pro] Lughnasadh:
Thanks for testing. Curious about a few things...

1. What build were you on when you patched the boot image? Because the factory image builds are earlier (.015) than what we have received through OTA yesterday (.036). Wondering if kernel has changed between those 2 versions.

2. I understand that you are saying we have to disable dm-verity and vbmeta verificaiton when flashing the vbmeta image, but do you know if we have to wipe data for sure? Sounds like maybe you just did that anyway since it was early enough for you?

3. Which Magisk version did you use?
[Google Pixel 6 Pro] Quinny899:
I was on SD1A.210817.015.A4, flashed a patched SD1A.210817.015.A4. I did try flashing without dm-verity, it obviously refused to boot and then also refused to boot when the stock image was flashed back. Without wiping data it didn't boot with dm-verity disabled, went straight to rescue party and told me to reset.

Latest canary, I know the latest stable works on 12 (or should do) too but I'm working on root stuff so I prefer to be ahead of stable for testing.
[Google Pixel 6 Pro] Morgrain:
Just for expressiveness sake, you successfully rooted the Pixel 6 Pro with a working magisk image and it booted up already?

Hell, that was fast.
[Google Pixel 6 Pro] Quinny899:
I think it's rooted, it's restoring data so I can't access ADB or Magisk to check. I've been refreshing the factory image page for a while waiting for it, knowing it may require a data wipe so to hold back on fully setting up the phone.

It's basically a rite of passage for a new phone with me, how quick does it get soft bricked when trying to root it (OnePlus 7T Pro currently holds the record of needing the MSM tool on day 1)
[Google Pixel 6 Pro] Lughnasadh:
Thanks for that info.

So if I'm understanding correctly, aside from disabling dm-verity, we will also have to wipe data each time when patching the new monthly boot images?
[Google Pixel 6 Pro] HereticBG:
Well that's some good news that you got it going at least!

I guess now the question is if you can keep root and not have to wipe when dirty flashing a system update with all the dm-verity stuff, right?
[Google Pixel 6 Pro] Quinny899:
I don't have the experience with messing with dm-verity so I can't answer for sure (someone else correct me if I'm wrong), but I think it's a one time thing, so long as you don't flash vbmeta again without it? So basically don't use flash-all and flash the images manually, skipping vbmeta.

V0latyle was also saying that the requirement was worked around on the other Pixels anyway so it might not even be required by the next monthly patch.

In fact, re-reading his message again I could probably have got stock to boot again if I re-flashed vbmeta, which just shows my lack of experience with the newer Pixels.
[Google Pixel 6 Pro] Nekromantik:
can someone who not taken the OTA check kernel version?
[Google Pixel 6 Pro] V0latyle:
Firmware is out

The solution, if you can call it that, was to avoid the automatic OTA; instead, sideload the OTA via ADB, then enter fastboot without rebooting, and flash /vbmeta and /boot.

Still not 100%, I tested this on my Pixel 5 and got stuck at rescue party too...with the stock images.

If it makes you feel any better, those of us who updated to Android 12 already have another update notification, but the OTA hasn't been posted to Google yet, so there's no way to compare the build number.
[Google Pixel 6 Pro] Quinny899:
View attachment 5443701

Confirmed.
[Google Pixel 6 Pro] V0latyle:
Awesome.

Did you get the "your system may be corrupted" message after flashing /vbmeta and /boot?

I'm wondering if perhaps the issue was the previous version of Magisk.
[Google Pixel 6 Pro] Quinny899:
Yes, after flashing just boot (before I realised you had to do vbmeta too), and also after. Not sure if the latter was due to the former, but I'd guess it probably still happens if you flash boot *and* disable vbmeta in one swoop.

FYI, "Your system may be corrupted" is what I refer to as Rescue Party, because it does the same thing (though it might be something different as Rescue Party is in the system and it didn't get that far): https://source.android.com/devices/tech/debug/rescue-party
[Google Pixel 6 Pro] V0latyle:
Yeah, that's Rescue Party. Us Pixel 5 guys still haven't figured out why that's happening.

Might be something to do with Magisk and ramdisk, I have no idea.
[Google Pixel 6 Pro] Lughnasadh:
If I'm understanding this right, then flashing the factory image with the -w removed from the flash-all.bat file "may" not work because after you do that it automatically reboots and you want to avoid rebooting before disabling dm-verity? Or did this just pertain to going from Beta to Stable 12?

Trying to understand this because it seems that if you flash the factory image with the -w removed, you are on an unrooted/unmodified boot.img so having to disable dm-verity shouldn't be needed at that point because you aren't rooted when it automatically boots up after flashing the factory image. And that when disabling dm-verity is needed is before you boot up with a patched boot image.

Does that make any sense?
[Google Pixel 6 Pro] V0latyle:
You can dirty flash the system image if you want; honestly I don't see the point vs sideloading the OTA. So far, the only way of (possibly) avoiding Rescue Party and a data wipe is to use the OTA > fastboot method.

However, if you want to start completely clean, you can add the disable flags when you flash the system image:

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

When the update completes, you can force bootloader via key combo, flash the patched boot.img, and boot into fresh Android 12 with root.

On the other hand, if you don't care about root, then yes, you can either OTA or dirty flash factory, it makes no difference.
[Google Pixel 6 Pro] Lughnasadh:
Thanks for that info. Yeah, for the last several years I'm just used to flashing the factory image without the -w to keep data, having it automatically boot without being rooted, then patching the boot image, and going back an flashing that.

But it sounds like now may be the method du jour would be to just sideload the OTA and go from there.

Sounds good 👍
[Google Pixel 6 Pro] Quinny899:
On the Magisk note, I just tried using Magisk stable to see if I could get Hide working, but it fails to extract the boot image. I would guess that the patching updates mentioned in the changelog are important: https://cdn.jsdelivr.net/gh/topjohnwu/magisk-files@9537c5d8cedfc09ca723ae0392b1219e75d9b636/notes.md

This does mean we're "stuck" with zygisk, though modules are adding support pretty fast so it's not the end of the world.
[Google Pixel 6 Pro] V0latyle:
I was able to use Canary 23001 on the Pixel 5.

To pass SafetyNet on 23010/23011, you'll have to use pre-Riru Universal SafetyNet Fix (v1.2.0) and MagiskHide Props Config. USNF 2.0.0+ was written for Riru, which is not compatible with Zygisk.
[Google Pixel 6 Pro] Quinny899:
23001 doesn't work either sadly. USNF 1.2.0 also rejects Android 12, but there's an early build of 2.0 here that is pre-riru and installs fine. Someone on Reddit linked that. Not got it to pass yet, working on it.
[Google Pixel 6 Pro] snovvman:
Whoa--so you are seeing that with >P4a (and P6/P), one can update via OTA sideload and gain permanent root without having to wipe (with verity flags, of course)?
[Google Pixel 6 Pro] V0latyle:
Potentially. Not a guarantee by any means.

The trick is to sideload the OTA, then immediately enter fastboot and flash vbmeta and boot.
[Google Pixel 6 Pro] plasticarmyman:
what device are you on?
[Google Pixel 6 Pro] diesteldorf:
I'm sorry....I clarified earlier, but it was further upthread.

Pixel 4 XL
[Google Pixel 6 Pro] Ingenium13:
You can likely remove -w and add --skip-reboot so that you can flash patched boot without rebooting. That's how I historically did the updates: extract boot.img and patch. Reboot to bootloader, replace -w with --skip-reboot in the flash-all script, then fastboot flash magisk patched boot. That might be enough to avoid Rescue Party?
[Google Pixel 6 Pro] V0latyle:
Unsure, although probably not TBH.
[Google Pixel 6 Pro] zee3are0:
You guys are amazing. Fastest from open box brand new phone to root I've ever had.

FYI, the patching process works for Fi as well as Verizon, though I hadn't accepted the OTA prior to patching. I did have to do the wipe after the verity, but I'd just opened the box and wiped for the unlocked bootloader anyway, so literally lost zero data.

root working, I'm transferring files now. Not sure about banking apps, etc., but I only had a few apps in my MagiskHide on my old Pixel 3 (Peacock, Google Pay and my banking apps). Guessing they'll work with deny now.
[Google Pixel 6 Pro] Cares:
All my apps work fine with MagiskHide and Zygist. Unfortunately I can't pass any part of SafetyNet so I can't use GPay and Chase bank also prevents biometrics with root detected.
[Google Pixel 6 Pro] bd177:
I rooted the android 12 release version on my Pixel 4XL by patching the boot image. I first adb sideloaded the OTA image then rebooted from recovery to bootloader and fastboot flashed the magisk boot image. I didn't do anything else. The only thing that doesn't work are GPay etc.