yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] dvx2550:
100% working

Easy update and root and keep your data

You can always update to the latest build and keep your data

Like the first time installation with more 1 step

Make sure USB-Debugging is enabled in developer-options and you have authorized the pc you're using on your phone.

Boot your phone into fastboot mode.

You can do this by turning it off and then starting it by holding Power + Volume Down

until fastboot mode appears or just adb reboot bootloader

Go here and click on the link for the Android Flash Tool.

(I didn't copy the link directly so i don't have to update it everytime google releases a new update)

It should ask you to allow the website to access ADB Keys. Click Ok.

If the website somehow doesn't work, try using Google Chrome.

Select your Pixel 5. If it's not showing up click add device.

Click on the edit symbol (pen) in the box where the selected build is shown.

Make sure Wipe Device, Disable Verity and Disable Verification are checked.

make sure Wipe Device , Lock Bootloader , Force Flash all Partitions are unchecked .​

Install and boot the phone when it's finished.

and finally Patch & flash boot.img
[Google Pixel 5 Guides, News, & Discussion] Machuda:
100% not working. After it was done, it said the android system could not be loaded. I had to flash vbmeta to fix it.
[Google Pixel 5 Guides, News, & Discussion] dvx2550:
I tried it myself and it works for me
[Google Pixel 5 Guides, News, & Discussion] mistermojorizin:
Sorry, just to clarify, by "new vbmeta" you mean just the stock on from beta 2? I thought you needed to flash an empty one.

which "how to" you referring to? The OP in this thread doesn't mention vbmeta it's using the flash tool which I can't seem to get to recognize my phone
[Google Pixel 5 Guides, News, & Discussion] Machuda:
I sometimes have problems with the flash tool. You need to disable the adb server using adb kill-server command. Another thing to check is to make sure USB debugging is turned on.
[Google Pixel 5 Guides, News, & Discussion] Machuda:
Can you please check if it gives you the same error after trying to boot into the system when the tool is finished flashing?
[Google Pixel 5 Guides, News, & Discussion] mistermojorizin:
I tried this method with 2 modifications.

Step 0 - boot to bootloader switch to slot A (my system is on slot B and slot A is inactive). Recovery flashes the OTA to the inactive slot. So without this step, it was flashing it to Slot A.

Ste 4 - reboot to bootloader

Anyway it didn't work. It wouldn't even try to boot. I was able to flash the stock vbmeta.img without disabling verfication and then at least it was able to boot.
[Google Pixel 5 Guides, News, & Discussion] Machuda:
Yes that's the same problem I'm having. It won't boot with vbmeta modified.
[Google Pixel 5 Guides, News, & Discussion] fuadhdmini:
Root is not stable on beta 2. Am rooted and managed to do few rooting activity and now keeps getting handset is not rooted.

App that requires root can't get root acces
[Google Pixel 5 Guides, News, & Discussion] jshbrmn:
Hey just wondering how you achieved root with beta 2? I've tried a few things and haven't seem to be able to get it working (bootloop).

Is there a definitive process out there?
[Google Pixel 5 Guides, News, & Discussion] howtomen:
I keep getting "FAILED (remote: Failed to write to partition Not Found)" when trying to flash the patched img. Not sure what to do. Any suggestions?
[Google Pixel 5 Guides, News, & Discussion] kafisc:
The problem is you just need to disable verity and verificaion once (only possible with a full wipe).

I'm using the Android Flash Tool for Beta 2.1:

https://flash.android.com/preview/beta2.1

I'm using the Android Flash Tool for Beta 3:

https://flash.android.com/preview/beta3

Also download the latest factory image (and extract boot.img):

https://developer.android.com/about/versions/12/download

Within the flash tool uncheck every option (just to be sure).

Only check "Disable Verity" and "Disable Verificaion" and click on flash.

Boot into OS and reboot again.

Patch original boot.img with Magisk.

Reboot to fastboot and flash boot patched_magisk.img.

Done.

You can do this with every update. Always be sure that "Disable Verity" and "Disable Verificaion" are checked when upgrading (and nothing else like Lock Bootloader and so on).

You may need to wipe once. But after the first initial wipe, you don't need to wipe when you upgrade. You just need to be sure "Disable Verity" and "Disable Verificaion" are checked when upgrading.

I'm doing it this way since the first beta an everything is working and I didn't need to wipe again till this day.
[Google Pixel 5 Guides, News, & Discussion] pax2011:
Has anyone sucefully rooted beta 3?

Patched boot image with magisk canary if I only boot the image it starts

Then tried to flash patched boot image and get stuck in bootloader
[Google Pixel 5 Guides, News, & Discussion] Richiejk:
Just did on my Pixel 4XL and followed all the steps in the guide - clean install, disable verity and verification. Works perfectly.
[Google Pixel 5 Guides, News, & Discussion] pax2011:
so, every beta I have to clean install? I was on beta 2 rooted
[Google Pixel 5 Guides, News, & Discussion] jshbrmn:
For all the updates from beta 2 - 3 I've followed this process without fail:

- extract boot.img and vbmeta.img from downloaded beta of your relevant device

- add boot.img to phone (if downloaded, and extracted on another device)

- patch boot.img in magisk (i like to rename it to patched_magisk.img)

- move patched_magisk.img to desktop

- download and install latest beta from the OTA provided

- tap the reboot button on the OTA install screen once completed

- once the reboot begins and your screen turns black hit the power and volume down button to get into fastboot

- run

fastboot --disable-verity --disable-verification flash vbmeta path/to/vbmeta.img (you can drag img from location)

- then run

fastboot flash boot path/to/patched_magisk.img (you can drag img from location)

This has worked flawlessly, maintaining root while also keeping all my data.
[Google Pixel 5 Guides, News, & Discussion] SadaUkyo:
Can I do this when I already updated to beta 3?
[Google Pixel 5 Guides, News, & Discussion] pax2011:
No, I tried it. Had to format all
[Google Pixel 5 Guides, News, & Discussion] jshbrmn:
Yeah I wouldn't do this unless you've started from the initial process op outlined. I did this moving from beta 2 to 2.1 and then beta 2.1 to beta 3. However beta 2 was my first android 12 install, which I used ops procedure to achieve.
[Google Pixel 5 Guides, News, & Discussion] bleez99:
Do this:

You don't need the Android flash tool. I have been manually flashing full images for a long time:

I don't like things done behing my back.

For beta 3:

I flash both sides hence the skip secondary - it saves a few seconds.

When flashing - watch what's scrolling by. The vbmeta.img is modified on the fly.

No need to copy from another build or someone else's hack.

Below is what I use. Successfully.

Modify the last line in the flash-all.bat or.sh

fastboot --skip-reboot --skip-secondary --disable-verity --disable-verification update image-redfin-spb3.210618.013.zip
[Google Pixel 5 Guides, News, & Discussion] SadaUkyo:
Do you think this will be necessary once the finished version of Android 12 is out?
[Google Pixel 5 Guides, News, & Discussion] jshbrmn:
There are other methods that will likely be developed and supported, but this one will remain an option for the finished version of 12.
[Google Pixel 5 Guides, News, & Discussion] tauio111:
Ach right, so you can pass the arguments to a fastboot update command and not just flashing vbmeta. Hoped so, but did not find a single hint on Google about it actually working. Haven't tried it yet though.
[Google Pixel 5 Guides, News, & Discussion] bleez99:
Probably. How hard is it to modify flash-all.sh?

I apply the monthly updates myself, I always modify the shell script.

Keep --disable-verity --disable-verification in the fastboot command line. You don't need the others I'm showing, it's just how I approach updates. I flash the current slot, no reboot, change the slot, flash again. That way I flip flop slots each month. Just my OCD showing. The --skip-secondary option is my preference when flashing both a and b slots. I'll reboot myself when finished.

I wouldn't recommend the --skip-secondary when only flashing the current slot.

fastboot --skip-reboot --skip-secondary --disable-verity --disable-verification update image-redfin-spb3.210618.013.zip
[Google Pixel 5 Guides, News, & Discussion] bleez99:
For those of you who don't have safetynet working, here.

All credit goes to @kdrag0n, I just modified the shell scripts for B3

Pull request done if you don't want my zip.
[Google Pixel 5 Guides, News, & Discussion] bleez99:
I did - you'll be good to go. And I have safetynet.

Google Pay is set up, no rejected cards, but I haven't made a purchase yet. Confidence is high.
[Google Pixel 5 Guides, News, & Discussion] pndwal:
Seems no-one here tried @vvb2060 Magisk Alpha yet. 😉

Nb. Target SDK (API) bumped to 31

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85350767

Latest changes commits (link above for others):

App adapted to Android 12

Android 12+ super user hides the screen overlay when the window pops up

🤠 PW
[Google Pixel 5 Guides, News, & Discussion] Jiggs82:
Can this be installed over the official magisk app (canary) ?
[Google Pixel 5 Guides, News, & Discussion] pndwal:
Need to replace App to see Alpha channel (it's not John's).

I had no issues just installing app with Canary App installed; you can try. Others needed to uninstall it first (due to different signing keys?).

Nb. Data / modules / settings are not lost or affected simply by uninstalling App as they remain in /data/adb unless Uninstall (full) is run from App or recovery. 👍 PW
[Google Pixel 5 Guides, News, & Discussion] yoyo linuxien:
Tried it on a Pixel 4a 5G. I am on Android 12 beta 3, never disabled verity because I don't want to wipe it.

I still get the same error at boot : failed to load/verify ...
[Google Pixel 5 Guides, News, & Discussion] bgboii:
could I do this with ota?
[Google Pixel 5 Guides, News, & Discussion] bleez99:
No, I recommend a flash.
[Google Pixel 5 Guides, News, & Discussion] bgboii:
Ah okay. Will this wipe my data? I'm trying to avoid wiping data
[Google Pixel 5 Guides, News, & Discussion] bleez99:
You may have to. Going with a flash from 11 to 12 may pose problems with stability if you don't wipe. There is an example command line a few posts up that show how to disable verity and the command line I displayed excludes the -w for wiping. You may get lucky and have a good running phone. You may run into issues. If you do you'll have to wipe. I fully recommend backing up your sdcard data before doing anything. Simply taking the ota or sideloading it will be fine until you apply magisk. Then you'll pull your hair out. If you do a full flash, modifying the last line in the flash.bat or sh as shown will give you success. Read up on fastboot and the command line options. As I stated in an earlier post I flash both a and b slots, then manually restart. That's what my example command line facilitates. Read up on switching the active slot as well. My command line isn't for everyone, it's how I flash. It's an example. If you do use my example, you must flash twice, once on the current slot, then on other.
[Google Pixel 5 Guides, News, & Discussion] Eiad Ajam:
Anyone has done the latest update and kept root ?
[Google Pixel 5 Guides, News, & Discussion] bleez99:
Full flash,as always. No wipee.
[Google Pixel 5 Guides, News, & Discussion] Eiad Ajam:
Full flash of the latest system image or the OTA only ?
[Google Pixel 5 Guides, News, & Discussion] jshbrmn:
I followed the process I posted on page 4 to move from 3 to 3.1 without issue....just to be clear:

This is only confirmed working from version to version (and subversion). I'd imagine it would work even while skipping a version, but it is untested.
[Google Pixel 5 Guides, News, & Discussion] Eiad Ajam:
My phone won't boot

it keeps going to fastboot
[Google Pixel 5 Guides, News, & Discussion] jons99:
fastboot -w should fix your issue
[Google Pixel 5 Guides, News, & Discussion] Eiad Ajam:
This is working perfectly with me

thank you
[Google Pixel 5 Guides, News, & Discussion] droidkill3r:
This is where I am at on beta 3.1, what am I doing wrong
[Google Pixel 5 Guides, News, & Discussion] droidkill3r:
I had the same issues

I deleted platform tools and installed minimal adb and fast boot from xda "Google it" install to c:/ folder and create shortcut on desktop.. I wiped my phone and followed instructions in this thread. Copy the magisk boot.img to the minimal adb and fastboot folder open adb ..

Fastboot flash boot "copy name of magisk here from minimal folder and put .omg at the end and enter
[Google Pixel 5 Guides, News, & Discussion] bleez99:
This will probably be short lived, but here is the "official" safetynet fix for B3

https://github.com/kdrag0n/safetynet-fix/files/6929451/safetynet-fix-a12.3.zip
[Google Pixel 5 Guides, News, & Discussion] Jiggs82:
Hey will this be updated for beta 4 ? Thanks in advance
[Google Pixel 5 Guides, News, & Discussion] bleez99:
Don't know. I can't get B4 rooted yet without bootlooping.

Some fiddling to do.
[Google Pixel 5 Guides, News, & Discussion] Matt4542:
I rooted fine. 4a 5G

Set flash-all.bat to

fastboot --skip-reboot --disable-verity --disable-verification update image-bramble-spb4.210715.011.zip

Took boot image from B4 and ran through Magisk, flashed on slot b in fastboot successfully, and booted. Flashed safteynet fix but didn't pass ctsProfile.

Willing to test any Magisk modules if you can't get booted
[Google Pixel 5 Guides, News, & Discussion] Jiggs82:
Hmm must be a mod/magisk try the remove all modules thing
[Google Pixel 5 Guides, News, & Discussion] bleez99:
Yes, next step. I am afraid it may be the patched keystore and shared object that "just worked" from beta 2 to beta 3 in the safetynet fix. Either @kdrag0n can do a fresh patch, he's the original author (when he has the time, not asking for anything) or I will have to set up my own build environment. No time for it this week. I am really trying very hard not to factory reset - it's a pain even if you back up your sdcard and choice apps. I use Titanuim to restore app settings, but, starting to gravitate more and more towards AppDash. Either way you have to be rooted to take advantage of those tools.

It did boot once while rooted, and my pin didn't work - that's a clue right there. That kind of sucked. I like to use root tools and I like GPay. :)

Strangely enough, I removed verity with the method I used before, and I had one of those nasty your system is corrupt, try again. Without installing Magisk. A straight flash with everything intact was the only way to get it to boot normally, unrooted of course. I immediately removed my PIN after that. That kind of freaked me out.

Pin removed for now until I can sort this out. I'm an old developer, but I never really dabbled too much with AOSP code, but I can, it's only Java and C++. I am happy to try to contribute to @kdrag0n 's stuff, but it's hard to find the time, and it's a real PITA to set up any build environment.
[Google Pixel 5 Guides, News, & Discussion] bleez99:
Yup, exactly my method too. Did you use safetynet-fix - last version for B3? It's the one I checked in to @kdrag0n 's github.

EDIT:

Went back to the above command line and with disabling verity, no go. Phone just doesn't like it. Pixel 5.
[Google Pixel 5 Guides, News, & Discussion] Matt4542:
Yes, it's the latest for B3. Doesn't work.
[Google Pixel 5 Guides, News, & Discussion] bleez99:
I know why, and it's probably a good thing it doesn't. It's looking for:

if getprop ro.build.id | grep -q SPB3; then
stop keystore2
start keystore2
fi

So for you it won't restart the old keystore2 service. I've been playing around with my version, and I'm starting it.

Now, how to get rid of it...
[Google Pixel 5 Guides, News, & Discussion] ekowwillis:
I noticed you're skipping reboot, how do you path the boot image in magisk since you're not booting into the system?
[Google Pixel 5 Guides, News, & Discussion] bleez99:
Yeah, I got out of it. Had to wipe. The binaries in the safetynet fix for B2 were still compatible with B3. Not B4. I played with fire and got burned. Rooted now with the method I used in flash-all.sh. Something really bad happened on first root fire up, and I just had to do a clean start. Good thing I always back up before playing around. Just a couple of wasted hours setting the phone back up. PIN not working was the first clue. Keeping verity disabled just resulted in a corrupt system error. It's supposed to be the other way around, right? :)
[Google Pixel 5 Guides, News, & Discussion] vlubosh:
Magisk is working on beta4, flashed boot with this command fastboot flash boot_b "yourmagiskpatchedfilename".img, just for someone who want to know how to flash it.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Does the safetynet module work on beta 4?
[Google Pixel 5 Guides, News, & Discussion] vlubosh:
no, cts profile is disabled
[Google Pixel 5 Guides, News, & Discussion] SadaUkyo:
I still get a bootloop. What steps exactly do I have to follow?
[Google Pixel 5 Guides, News, & Discussion] vlubosh:
downloaded and flashed beta4 with https://flash.android.com/preview/beta4 , downloaded beta4 factory https://dl.google.com/developers/an...y/redfin-spb4.210715.011-factory-05b19986.zip , extracted boot.img, patched with magisk and flashed with this command fastboot flash boot_b magisk-patched.img (this name will be different, rename it).
[Google Pixel 5 Guides, News, & Discussion] SadaUkyo:
I have the beta installed via OTA. Is this the problem? Do I have to reinstall with flash tool? If yes, what settings do I have to use?
[Google Pixel 5 Guides, News, & Discussion] vlubosh:
Have you unlocked bootloader?
[Google Pixel 5 Guides, News, & Discussion] ggkameleon:
Hi ! I'm on on Android 11 August update can flash the Ota Android 12 Beta 4 only update it with Adb sideload the Ota over Android 11 or do make a clean install. Do you know if Magisk work on Android 12 Beta 4 ?

Yhanks
[Google Pixel 5 Guides, News, & Discussion] vandyman:
Check out the Magisk thread, it is always wise to do a little research and reading before modding your device.
[Google Pixel 5 Guides, News, & Discussion] SadaUkyo:
Yes. I tried flash boot_b and just flash boot_. Both resulted in a boot loop. But since I'm not rooted on any of those betas I just installed the OTA. Will try later with the beta 4.1. But sofar I'm very unpleased with the android 12 beta. Haven't seen a beta this unstable since android 8.
[Google Pixel 5 Guides, News, & Discussion] vlubosh:
today i`ve returned from a11 to a12 and found that it flashed to boot_a. try to flash stock rom with web android flasher, then reboot to fastboot and check which partition is active, and then flash boot image to the active partition. i`ve got same bootloop cause i didnt look at flashed partition in fastboot screen.
[Google Pixel 5 Guides, News, & Discussion] Sh0X31:
Thanks for your work, helped a lot but can you please add the fastboot command to the disabled AVB & dm-verity section

I also want to ask, do I still need disabled AVB & dm-verity
[Google Pixel 5 Guides, News, & Discussion] Sh0X31:
do I still need disabled AVB & dm-verity Form root? Want to flash beta 5
[Google Pixel 5 Guides, News, & Discussion] evanxyj:
I tried disable those two and boot magisk patched boot, but end up in "can't load system data might corrupted" screen.
[Google Pixel 5 Guides, News, & Discussion] pctv007:
Just flashed Beta 5 yesterday, with those 2 params.

Had to Wipe data because of corrupted data error.

Root works just right, but GPay doesn't allow me to add credit cards...

Any1 knwos why ?

Thanks

P.S.: Flashed Magisked patched boot.img with fastboot right after 1st boot
[Google Pixel 5 Guides, News, & Discussion] evanxyj:
FYI, when seeing corrupted data error, you can solve it by trying "fastboot update the image-redfin-xxx.zip" file, the system will restart itself.
[Google Pixel 5 Guides, News, & Discussion] junyamada:
Thank you for this thread. I've been using this to update my beta versions since Beta 3. I've been using the same command "fastboot --skip-reboot --skip-secondary --disable-verity --disable-verification update" since then up to Beta 5.

The weird thing though, ever since I setup my Gpay back in beta 3 and installed the magisk module "safetynet fix B3", I haven't lost my Gpay yet even though I'm not passing safety net during my updates.

I've read some of the comments regarding Gpay and mine is still intact, I tried both adding a new card and paying which worked flawlessly on Beta 5.

P.S. I'm a Pixel 4 XL user
[Google Pixel 5 Guides, News, & Discussion] Makishima:
My GPay works fine without Safetynet passing on Beta 4 either... No idea how. Did you also get the corrupted data error?
[Google Pixel 5 Guides, News, & Discussion] Makishima:
Does this work in this case? Updating to beta 5? Has this corrupted data error happened to everyone so far?
[Google Pixel 5 Guides, News, & Discussion] junyamada:
Never had an issue with the update starting from Beta 3 to 5.

I jumped from 3 to 4, (4.1?) And 5.0 without wiping the data.
[Google Pixel 5 Guides, News, & Discussion] Makishima:
Using the fastboot --skip-reboot --skip-secondary --disable-verity --disable-verification update beta5.zip command and then flashing the magisk patched boot image?
[Google Pixel 5 Guides, News, & Discussion] junyamada:
Right. I never lost my data all throughout starting from Beta 3. I would do the above, boot up then reboot back again to bootloader then flash patched boot (magisk). Once booted, magisk is working, Gpay is working.

Though I never dared to check Gpay before flashing the patched boot image.

I still have the safetynet fix (B3) installed til now. It never gave me any errors so I never removed it.
[Google Pixel 5 Guides, News, & Discussion] Makishima:
I never installed any safetynet fix... GPay just works. Do you disable your modules first?

Edit: I just flashed it. Disabled my modules, the Magisk app was hidden but I forgot to revert that. Rebooted directly into Fastboot, flashed the beta, no corrupted data error. Booted back fine, Fastboot again to flash Magisk patched boot.img. Everything still works, Magisk still hidden, GPay still works.
[Google Pixel 5 Guides, News, & Discussion] junyamada:
I never disabled any modules or unhide my magisk. Which is weird, I was expecting it to produce an error specifically on Gpay, but it ended up working all the way.

I have RiruCore, Lsposed, Busybox, MagiskHide Props and the Safetynet Fix (B3). Didn't need to disable them.

I've been thinking of doing a clean install but I'm worried that the Gpay might not working after.

I wonder what's different with our setup. I might try what you did sometime.
[Google Pixel 5 Guides, News, & Discussion] SadaUkyo:
So do I still have to use "skip-reboot --skip-secondary --disable-verity --disable-verification" with beta 5 ore can I just flash the patched magisk like I used to do?
[Google Pixel 5 Guides, News, & Discussion] Makishima:
I did. Not sure if it works without it.
[Google Pixel 5 Guides, News, & Discussion] SadaUkyo:
Will I loose my data if I didn't root from the beginning of beta?
[Google Pixel 5 Guides, News, & Discussion] Makishima:
If this is your first time disabling Verity etc. then I think so, I think you need to wipe your data, run the command with -w.