yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] iwearthebelt:
Personality, I just like running the latest builds with all the most recent updates. I've just always updated the nightlies on whatever ROM I was running so it's probably more of a habit than anything. If your device is running perfectly fine and you're happy with it, there's really no need to update other than security reasons or if you're wanting on some kind of fix for whatever issue you might be having.
[Google Pixel 6 Pro] dilligaf56:
I usually like to be on the latest build as well, so as soon as I see that there aren't any major issues, I upgrade (still using the OG CLI method, not PixelFlasher, though am going to look into it). It looks like there have been more problems than usual this month. Is there a link to the changelog for the March update anywhere? Thanks for the come-back.
[Google Pixel 6 Pro] iwearthebelt:
It really does seem like there are more issues than normal this month. The changelog is posted around here somewhere but I can't remember where I seen it. I highly recommend using PixelFlasher to update your device, it's a very well put together program that Badabing2003 created. I can't say enough good things about it, really well done. It literally takes me 224 seconds every month to update, except this month do to an error on my part. Give it a go, if you have any questions or run into any issues PM me and I'll help you out.
[Google Pixel 6 Pro] dilligaf56:
Excellent, I will check it out. I remember seeing a comment about the latest version (34.0.x?) having a bug, and to use 33.x.x instead - is this still the case? Many thanks!
[Google Pixel 6 Pro] iwearthebelt:
There's no issues with PixelFlasher, it's Platform Tools that is having issues. I guess the latest version 34.0.0 has issues so they're telling everyone to revert back to 33.0.3 If you have 34.0.0 you'll have to find a place to download 33.0.3 from. Once you get that straightened out then you can use PixelFlasher if you want. Just don't use the latest Platform Tools or you'll end up in a bootloop (at least that's what I hear).
[Google Pixel 6 Pro] V0latyle:
SDK Platform Tools 33.0.3
[Google Pixel 6 Pro] Lughnasadh:
It could be worse as several users have reported their devices being bricked or unresponsive after using 34+.
[Google Pixel 6 Pro] V0latyle:
You'd really think that with such a critical problem that can corrupt bootloaders and brick devices, they would at the very least pull the problem releases.
[Google Pixel 6 Pro] Lughnasadh:
You would think, lol. But we know how slow Google sometimes reacts to major issues: re: ARB in the Pixel 6 series.
[Google Pixel 6 Pro] V0latyle:
thisisfine.jpeg
[Google Pixel 6 Pro] iwearthebelt:
They're saying that they're bricked but from what I've read they're actually stuck in a bootloop. Not nearly as bad but still an issue. Yeah, they probably should at least include a warning with the download that warns of the potential to end up in a bootloop. At least until they get it straightened out no matter who's software is causing the problem. .
[Google Pixel 6 Pro] Dragon Kumera:
Is there a way to find out what version I have installed?
[Google Pixel 6 Pro] Nergal di Cuthah:
Type "Adb version" without quotes in command line (in the platform tools folder of course)
[Google Pixel 6 Pro] V0latyle:
Great question. Also, no friggin' idea. Maybe the help menu in adb will tell you? Testing...

Ninja'd.

This works
[Google Pixel 6 Pro] Dragon Kumera:
Android Debug Bridge version 1.0.41

Version 33.0.3-8952118

What I have installed. So guess I wont update.
[Google Pixel 6 Pro] Nergal di Cuthah:
I tried "fastboot version" but it wanted a device so i closed it
[Google Pixel 6 Pro] Dragon Kumera:
just type adb version
[Google Pixel 6 Pro] Nergal di Cuthah:
Lol i know i just told you that ROFL

I was stating as an experiment i typed "fastboot version" it might have given a build number, but i didn't let it go through to a device :)
[Google Pixel 6 Pro] Dragon Kumera:
oh lol. I didnt realize the name lol.
[Google Pixel 6 Pro] V0latyle:
Yeah, in this case you're asking fastboot to return the version of a particular variable on the device
[Google Pixel 6 Pro] dilligaf56:
Thanks. Got 33.0.3 downloaded. Will give PixelFlasher a look-see later this week, when I get enough time to do it. Much appreciated!
[Google Pixel 6 Pro] crisco654:
Well I glad I saw the posts about the issues with platform tools 34.0. Used 33.0.3 instead with magisk 2520, and just finishing updating through the factory image and fastboot, and patching and booting the patched boot.img, and it works perfectly. I was coming from the Feb. update.
[Google Pixel 6 Pro] luke1018:
many many thanks for your guide. it is very useful.

now i have upgraded my system to SD1A.210817.037.
[Google Pixel 6 Pro] Dragon Kumera:
Yes its possible through adb. But it depends on if the app allows it.

Can also go into android/data/ and android/obb/ copy those folders as some data there and will work once pasted back in
[Google Pixel 6 Pro] V0latyle:
Yes...and also no.

As I'm sure most of us know, you can still boot with an untouched (unrooted) boot image. Aside from the built in Google Cloud backup, I believe you can use apps such as Swift Backup to back up some of your data without root.

That being said, Scoped Storage was introduced with Android 11; it prevents apps from accessing /data outside of their own app specific caches - meaning without root, you can't backup app data, because an app such as Swift cannot access any other data but its own.

Fortunately, there may be a workaround:

Try live booting the patched boot image. Android should start with temporary root; this bypasses verified boot, as those mechanisms only prevent a patched boot image from loading from the /boot partition, not live via ADB. You can use this to backup app data using Swift, then once your backup is complete, disable verity/verification to gain permanent root.

I do not know for a fact whether this works on the Tensor devices; it does on the 765G devices.
[Google Pixel 6 Pro] Dragon Kumera:
so not sure if this is the right sub but.

12.0.0 (SQ1D.211205.016.A1, Dec 2021)	Link	8123451727768bc1777e5bb56c333c2674ea1a688e174aef2fdee759e442c1ce
12.0.0 (SQ1D.211205.016.A4, Dec 2021, EMEA carriers)	Link	58c4992db48439dd65a015b51497843afa2a5eabd9e7a78bd20e1133a7b14b63
12.0.0 (SQ1D.211205.017, Dec 2021, US carriers)	Link	5576891cab747592480f59096b0c224c78844de387d3bc7bbdef18c9c4279189

What one do I get for unlocked pixel 6 pro directly from google store.?
[Google Pixel 6 Pro] Starzboy77:
Have same question. In USA using TMobile sim.
[Google Pixel 6 Pro] swieder711:
I think 12.0.0 (SQ1D.211205.016.A1, Dec 2021) is the one to use for Bootloader unlocked phones.

The US carriers version seems to be for phone that were purchased from ATT, VZ or others.
[Google Pixel 6 Pro] Starzboy77:
Yeah, not sure. Don't want to take a chance. Will need more confirmation.
[Google Pixel 6 Pro] Dragon Kumera:
Ya im thinking the one that ends in dec. No us carrier or anything but I would like more info first.
[Google Pixel 6 Pro] Jiggs82:
Dang seems root isnt working dirty flashing the december build pixel 6 pro. Might have to factory reset this time guys smh
[Google Pixel 6 Pro] Morgrain:
The newest update is breaking root. Dozens of people on Telegram talking about it.

DO NOT UPDATE TO DECEMBER PATCH IF YOU WANT TO RETAIN ROOT.
[Google Pixel 6 Pro] MArtyChubbs:
The only difference between the firmwares relate to the radio images. Everything else is the same. Has nothing to do with who you got the phone from. Locked Bootloaders like Verizon phones are based the phone serial numbers. If you bought the phone from Verizon, you cannot unlock the bootloaders to flash different firmware and can only take OTA's. If your phone is unlocked, you can flash any firmware, but you will get an OTA after for the proper firmware based on your carrier. Google wants you to have the proper radio for your carrier.

The radios are optimized for each carrier or region. Hence the different firmwares...
[Google Pixel 6 Pro] Nergal di Cuthah:
I was just about to report my lack of root after flash. I guess I'll go without until a new canary comes out silly me for jumping the gun
[Google Pixel 6 Pro] MArtyChubbs:
Or just dirty flash the Nov firmware??? No?
[Google Pixel 6 Pro] Dataman100:
I was thinking about that as well. Anyone want to be a guinea pig and give it a try? I really don't want to wipe my phone if it goes sideways
[Google Pixel 6 Pro] Jiggs82:
Idk about that might work but would mess something else up...i remember this issue happening a couple of updates in the past and magisk was the issue and needed an update. So i would suggest dont flash Dec build to keep root lol factory reset(which might work) or just wait for an update to Magisk. Should be out later today if anything hopefully...if they made the dev aware
[Google Pixel 6 Pro] EndlessBliss:
Found out too late. Dirty flashed December, lost root, tried reverting back to November, phone wouldn't boot and asked for a factory reset. Back on unrooted December now :cry:
[Google Pixel 6 Pro] Dataman100:
Sorry it didn't work, but thanks for letting us know. Going to have to live without root until Magisk gets fixed. At least I have my work provided iPhone that is completely stock. Lol!
[Google Pixel 6 Pro] Morgrain:
I left topjohnwu a note on twitter, hopefully he'll take a look into it rather soon
[Google Pixel 6 Pro] Dragon Kumera:
So rip december update broking even on fresh install? Guess I will have to redo the november one i just deleted for december.

I could live without root to i guess but ill decide apon after christmas
[Google Pixel 6 Pro] Brisky86:
I thought previously that in the past the OTAs that ended in an "A" was for Verizon?

When I download the "US Carriers" version (I am unlocked) there is not even a boot image listed to run the patch.

Luckily I saw the previous note to not update as you will lose root at the moment anyway.
[Google Pixel 6 Pro] skankerveen:
I hard bricked my device today (doesn't even turn on - can't even get into fastboot recovery). I'll explain what happened so perhaps others can avoid my mistakes in the future.

I was using:

Platform-tools Version 34.0.1-9680074

Factory image raven-t3b2.230316.005-factory-3923dd64

Magisk v26.1

Magisk patched my boot image, named: magisk_patched-26100_Xq7GU

I followed this guide to the letter (I think😅), however, I did not read any of the thread past the OP before starting.

I encountered a boot loop after Step 8 of Initial Root / Create Master Root Image, and doing a fastboot reboot. I did not specify a boot area

fastboot flash boot[_a or _b] <drag and drop master root.img here>.

After encountering the boot loop, I tried to flash the original boot.img from the factory image, reflashing the magisk patched, but none of it was able to recover from the boot loop.

I then made the mistake which led to a hard brick, which was to flash the original boot.img to boot_b (fastboot flash boot_b boot.img) and use fastboot --set-active=b to force the bootloader to use that (I am not an expert, I did not know the consequences, and I take full responsibility for taking these matters into my own hands instead of asking for help). My device began to bootloop for several minutes, although the bootloop was extremely quick compared to before so I thought it was a positive sign. However, I then decided to hold the power button to force it off and boot into fastboot/recovery. Once powered off, it no longer powers on and it is hard bricked.

This was a few hours of frustration condensed, so perhaps I've overlooked some things, but felt worthwhile to post here in case anybody is interested.
[Google Pixel 6 Pro] Nergal di Cuthah:
Switch to platform tools before 34.x. it is bugged, and does what you describe in your post, i think. The fix is in march or april so readback a few pages, both for the fix and the previous working platform tools (i think it was discussed after/during the roll out of march update (which i believe is the end of march)).
[Google Pixel 6 Pro] Nergal di Cuthah:
Here's the link for old platform tool

https://xdaforums.com/t/april-10-20...7-pro-cheetah-safetynet.4502805/post-88137573
[Google Pixel 6 Pro] skankerveen:
Doesn't really matter as my device is hard-bricked. Left on the charger all night just to make sure, but it still won't even turn on.
[Google Pixel 6 Pro] V0latyle:
Sorry to hear that. Unfortunately your only option is to have it repaired by replacing the mainboard (most repair centers do not perform low level flashing). If you're still under warranty this should be free, just tell them it stopped working completely.
[Google Pixel 6 Pro] Remanifest:
Interesting to see the comments RE adb causing a bootloop. I'm using adb version 1.0.41 on Linux, and I didn't encounter any problems with the update using the factory image. Maybe I just got lucky, or maybe the bug is platform-specific?
[Google Pixel 6 Pro] Sand_23:
I got a question about rooting. I updated my p6p to TQ2A.230305.008.E1. I deinstalled magisk before and all Modules. But i cant find the factory Image to extract and create a new boot Image to Patch. I stored my old master root boot image but can i use it again? Is there any alternative? Thx in advance
[Google Pixel 6 Pro] Nergal di Cuthah:
https://xdaforums.com/t/april-10-20...pixel-6-pro-raven-all-relevant-links.4352027/

First post april 10th entry
[Google Pixel 6 Pro] Sand_23:
But this is an other Version, see the numbers. Sorry, iam confused
[Google Pixel 6 Pro] Nergal di Cuthah:
Instead of the long numbers give the month of the update, i provided you with April's but if you want another. You can find all the updates in the first post of this thread under downloads. Then scroll to raven and pick the one you want.
[Google Pixel 6 Pro] Sand_23:
So you mean i should flash latest April build and take boot image?
[Google Pixel 6 Pro] Nergal di Cuthah:
Sounds reasonable to me
[Google Pixel 6 Pro] Sand_23:
After several Updates were complete now on latest April build. So i can take the latest factory image for root. Thx guys for helping
[Google Pixel 6 Pro] Nergal di Cuthah:
You can jump version (say you've got january, you don't have to insrall February and march to install april)
[Google Pixel 6 Pro] Sand_23:
Phone update all by itself and in month steps
[Google Pixel 6 Pro] Nergal di Cuthah:
Since your rooted you must be bootloader unlocked. you could flash updates with the "flash" link in update table.

Won't have to do anything to remove root after. Just need to flash patched boot like your already doing.

Tl:dr stepped out

Step one: download factory image from "link" link. Extract boot.img as per usual. Copy it to the download folder of your phone.

Step two: connect your phone to computer and press the table's "flash" link

Step three: progress through flash website the link takes you to. When it's done reboot your phone and let it boot up. There's a silent notification "android is updating", or some such. it'll take about 2-5 minutes.

Step four: After it's done open Magisk. Root the file in your downloads folder. Copy the patched file to your computer (preferably in the platform tools folder)

Step five: Fastboot flash the patched boot. Like you normally do.
[Google Pixel 6 Pro] dilligaf56:
I'm currently on Magisk 25206 (after rolling back from previous buggy upgrade). I'm now being told that there is a new update (26101). Is this new version OK? I don't want to have to downgrade again. Thanks!
[Google Pixel 6 Pro] Lughnasadh:
Working fine for me and lots of other people.
[Google Pixel 6 Pro] Nergal di Cuthah:
Yes stable and without serious bugs (like no modules 25210).
[Google Pixel 6 Pro] Nergal di Cuthah:
That said if you don't want to downgrade it's best to stay in the stable channel; downgrading is part of the canary experience.
[Google Pixel 6 Pro] kushman:
Ok so i been on Android 13 for ever now i never rooted when on Android 12 i a confused what i all need to exactly do for root. Do i need to download my current firmware and then adload the boot.img to all slots? I guess i have been confused since i got this phone exactly what to do and its holding me back on root.
[Google Pixel 6 Pro] V0latyle:
The instructions are in the OP. What are you confused on?
[Google Pixel 6 Pro] iwearthebelt:
Let me give you a little advice, when I rooted my Pixel 6 Pro, it was the first device I had rooted since my Nexus 6p. I came across the PixelFlasher program developed by Badabing2003 and haven't gone back to the old school way of doing things. once you learn how to use it, it's so easy! it literally takes me about 4 minutes to update my device every month when the update releases. The first thing you want to do is read the OP from the beginning and follow the instructions. If for some reason you can't figure something out and can't find what you're looking for, just ask your question in the thread and someone will get back to you pretty quick. if you need to you can always message me and I'll try to help you out.
[Google Pixel 6 Pro] Buzzy42:
I feel like this is a really dumb question but I am reading sort of multiple answers, so am curious what latest "best practice" is -- I have a Pixel 6 Pro, bought unlocked from Google, with a Verizon SIM. (i.e., it wasn't a Verizon model) Should I flash the regular/World image or the specific Verizon image? is it just a difference of tweaks for Verizon's service?) I don't want it to make any changes to the phone that would lock it to Verizon... I usually flash before a Verizon variant pops up but I'm late this month... (I haven't had any issues with the phone either way)

It sounds like it's generally preferable to use the carrier version but just wanted to make sure that's still the case and I wasn't going to mess anything up.
[Google Pixel 6 Pro] iwearthebelt:
I would flash the regular world version as its a GSM Unlocked model from Google (the same one I have). The Verizon SIM will work just fine in it just like any other carrier. If it was the specific Verizon model, I would have said flash the Verizon update as it probably has something that works with their specific device because it has a different chip and also works on the millimeter wave band.
[Google Pixel 6 Pro] Nergal di Cuthah:
Because it's verizon and mnvo carriers, i use the vz one on my unlocked google phone on Verizon's network. I imagine a signal tweak but don't know if i see an actual better signal.

I also use the global before the verizon comes out and it works just as well, so either.
[Google Pixel 6 Pro] Nothex:
Excellent Guide! Thank you!
[Google Pixel 6 Pro] dlwhdrlf:
Hey, so my phone auto downloaded and installed the update before I could follow the proper steps to update and root. Now my phone is on the latest software without root but with magisk app installed. What's the best way to get my root back?
[Google Pixel 6 Pro] Lughnasadh:
Patch the boot image and flash the patched boot image as oulined in the "Initial Root/Create Master Root Image" section of the OP.
[Google Pixel 6 Pro] dlwhdrlf:
huh apparently I must have done something wrong cause now I'm in a boot loop lol

Any advice so I don't lose any data?
[Google Pixel 6 Pro] Lughnasadh:
Boot into safe mode and then reboot. Sounds like you may have a module in need of an update that is causing your bootloop and booting into safe mode will disable your mods. You can then remove or update the offending mod, if this is indeed the case.
[Google Pixel 6 Pro] dlwhdrlf:
looks like safe mode isn't working for me. I've been holding down the vol down on the google logo for a few min and its just sitting there. any other ideas?
[Google Pixel 6 Pro] V0latyle:
Use the ADB command for disabling modules while booting:

adb wait-for-device shell magisk --remove-modules
[Google Pixel 6 Pro] dlwhdrlf:
soo this didn't work. I don't know when it happened but it doesn't loop anymore and before the unlocked bootloader warning, it gives me an additional warning saying it's corrupted. If that gives you guys more of an idea of my problem.
[Google Pixel 6 Pro] V0latyle:
It actualy did work, just not the way you wanted it to.

Did you do anything to vbmeta?

Are you using a custom kernel?
[Google Pixel 6 Pro] dlwhdrlf:
nope I just did the patching boot with magisk and flashing it. no custom kernel
[Google Pixel 6 Pro] dlwhdrlf:
If I just want to get my phone working again, would flashing the latest factory image will do it?

@Lughnasadh @V0latyle​
[Google Pixel 6 Pro] Lughnasadh:
Does it boot now? If so and you are trying to get rid of the corruption message, then flash last month's boot image (it probably won't boot but that's ok} and then flash the boot image for your current build (July I'm assuming).

If it's not booting then just flash the factory image but that may not get rid of the corruption message. In this case you can do the above after flashing the factory image to try and get rid of the corruption message.
[Google Pixel 6 Pro] dlwhdrlf:
huh flashing the latest firmware without wiping got me into the system again like nothing happened.

so if I want to root again could I do these steps to ensure I don't get stuck in bootloop or mess up my phone again?

do adb command to make sure I have no magisk module

flash the previously pathed boot.img for my build

done?
[Google Pixel 6 Pro] Nergal di Cuthah:
What platform tools version are you using
[Google Pixel 6 Pro] dlwhdrlf:
the latest 34.0.4
[Google Pixel 6 Pro] Lughnasadh:
Yes

Yes, although in this circumstance it might be better to temporarily root (see command below) to make sure you can boot first. If it doesn't boot then you can just restart and it should boot with the stock boot image.

fastboot boot <nameofpatchedbootimage>

If it boots fine then you can do "Direct Install" in Magisk app to "permanantly" root.

Yes
[Google Pixel 6 Pro] Nergal di Cuthah:
There are at least 3 releases by that name and all of them buggy afaik. You might want to look at the version before. i think it's linked in @roirraW "edor" ehT 's catch all news and info thread https://xdaforums.com/t/july-21-202...-out-untested-root-pixel-6-pro-raven.4352027/
[Google Pixel 6 Pro] Lughnasadh:
The current version of 34.0.4 worked for me on my Pixel 6 Pro, albeit when flashing A14 Beta 4.1.
[Google Pixel 6 Pro] dlwhdrlf:
ok, so thanks for letting me know about the temp root. it did not boot with the patched img. I must have messed up the patching or something before. I'm currently using magisk stable 26.1 maybe I'll try using the canary build and report back
[Google Pixel 6 Pro] dlwhdrlf:
my ordeal has finally come to an end. I repatched the boot.img using magisk canary build and now everything works correctly! Thanks for all the help, especially @Lughnasadh @V0latyle

PS. it's a little weird though, even after running the magisk module adb command, now I see magisk still had them and was never removed
[Google Pixel 6 Pro] as.hs:
so i did "adb devices" and it came up with my device, i did the "adb reboot bootloader" and it works perfectly fine. but when i type "fastboot flashing unlock" it just says "<waiting for any device>" and nothing pops up on my pixel. sorry if this was posted already or seems like a noobish question, its been a while for me 😅
[Google Pixel 6 Pro] V0latyle:
You don't have the Pixel bootloader driver installed

When in bootloader mode, check Device Manager. You should see a device with a triangle, you might have to look under your USB controller. Download and install the Google USB driver linked in the first post, manually install it as the driver for that device if necessary.
[Google Pixel 6 Pro] as.hs:
OK, it was the drivers. i got it to see the phone in fastboot and patched the boot img in magisk after it rebooted. i flashed the patched file and now my pixel is in a bootloop. i can still get into fast boot but it wont load to OS
[Google Pixel 6 Pro] V0latyle:
You probably have a Magisk module causing problems.

Stay connected to USB, fire up your ADB terminal and use ADB wait-for-device shell magisk --remove-modules
[Google Pixel 6 Pro] as.hs:
I ended up fixing it by flashing a stock boot img with googles Android flash tool and rooting with pixelflasher. It all works good now, but thanks for the help!