yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Homeboy76:
...It's says to extract the kernel (boot.img) and a flash-all.bat file...

I'm assuming you are referring to OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 4. Extract Files from Factory Image

- Read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Install/Update Factory Image keep data or wipe data

It explains what to do with the flash-all.bat file after you have extracted it.

- Read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 5. Root/Reroot with Magisk and Pass SafetyNet., •

Patching the boot.img - to root/reroot.

It explains what to do with the boot.img file after you have extracted it.

One of the other uses for the extracted boot.img file is

removing root

: OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 4. Extract Files from Factory Image

...What's the best way to back up your data (apps & media) before performing the upgrade?

To my knowledge a clean flash

wipes everything

. Speaking of upgrades, Oneplus performs them OTA.

We flash the stock boot.img file to unroot, perform the OTA upgrade, download and patch the new boot.img with Magisk and reflash. You can't do this with Pixel 6?...

- Search the OnePlus threads for backing up data (apps & media) for your phone.

- A clean flash does wipe everything.

- We flash the stock boot.img file to unroot, perform the OTA upgrade, download and patch the new boot.img with Magisk and reflash. We do too.

The final step is the Universal SafetyNet Fix. Oneplus root instructions didn't include this at all. Is this mandatory? Or is it that the Pixel 6 requires this because it's more "googly" than the Oneplus?...

- It is mandatory if you want to pass SafetyNet.

Also: Many Oneplus users continue to use Magisk 23001. This is the last version that includes a root hider. This version won't work on the Pixel 6, or more correctly Android 12 or higher?

- If you are purchasing a Google Pixel 6 phone with an unlockable bootloader so you can root it.

- You should use Magisk Beta/Stable 24.x or Magisk Canary app-release_2431x.

- Read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 5. Root/Reroot with Magisk and Pass SafetyNet., •

Pass Safety Net with SafetyNet Fix 2.2.1

, 3. Settings for Magisk Canary

It explains how to hide your apps.
[Google Pixel 6] Homeboy76:
Magisk Canary Update

app-release (2106751e) (24315)

Zygisk

[MagiskSU] [Zygisk] Proper package management and detection

[Zygisk] Fix Zygisk's self code unloading implementation...
[Google Pixel 6] mhrussell1:
While waiting for my new phone, I used your steps for this section to get my P3 to show device certified and I was able to get GPay to work again which it had not for the last few months, so thanks for that!

My question is your steps say to check the services in the Configure Deny List: "Google Play Store, Google Pay, etc."

Then while in Airplane mode you say to clear storage on that same list.

I added at least one more service, Google Play Protect Service along with my one of my banking apps. Is there a definitive list for the deny list that allow GPay to work? What do you mean by etc.?

Mark
[Google Pixel 6] jbofc:
So can I re-lock the bootloader and retain root? I just wanted to use BCR with the google phone app... It's installed now but as I understand if I re-lock bootloader then this may brick my phone? I haven't rooted for ages...can I just take ota updates now or do I have to re-patch each update?
[Google Pixel 6] mhrussell1:
The OP Part II Instructions in the last part of step 1. states that you should NOT lock the bootloader before you return to a stock image. There is a method to do OTA updates when you are unlocked but I have never used it. I prefer the full image flash with the -w flag removed to keep my data and root.
[Google Pixel 6] Homeboy76:
Magisk Updates

- Magisk Beta 25.0

- Magisk Canary (cacf8736) (25001)
[Google Pixel 6] gazdajezda:
Works like a charm 👍
[Google Pixel 6] Bliszcur:
can i use this method to root A13 B3 ?
[Google Pixel 6] Homeboy76:
Yes.
[Google Pixel 6] Homeboy76:
SafetyNetFix Update

v2.3.1 - 27Jun

This version only supports Zygisk (Magisk 24 and newer)

.
[Google Pixel 6] badabing2003:
Thanks for the update.

By the way, section 5 the link to SNF still says 2.2.1

Perhaps you can change that to:

Latest SafetyNetFix without specifying a version and link with this URI

Release v2.4.0 · kdrag0n/safetynet-fix

Highlights Play Integrity bypass without breaking device checks or causing other issues Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109) Other changes Updated instruc...

github.com

This way it will always be accurate and no need for maintenance.
[Google Pixel 6] Homeboy76:
I removed 2.2.1.

:oops: I thought you read

"section 5

, the link to the SafetyNet releases has always been in the OP; ~~~ Part II - Instructions ~~~ ; Root/Reboot with Magisk Pass SafetyNet; • Pass SafetyNet with SafetyNet Fix; 1. Download file(s)
[Google Pixel 6] Bliszcur:
Is this 3 modules need to install?
[Google Pixel 6] Homeboy76:
To install what?
[Google Pixel 6] squidbutt:
This worked on android 13 b3 with no issues. Even used the saftynet fix. If anyone was wondering
[Google Pixel 6] Koehlix:
Flashed the july-update as usual. I used the "factory -w method". After flashing the modified boot.img i stuck in a bootloop. If i start the phone in safe mode, the phone boots correctly. Is the an issue of magisk? Maybe a module?
[Google Pixel 6] Lughnasadh:
Rebooting normally after being in safe mode will disable your mods. If you can do this then a mod likely needs updating.
[Google Pixel 6] Koehlix:
It was the module from Renovate Ice
[Google Pixel 6] tamilmad:
Great to know. Please tell about the stability and can it be a daily driver. Want to jump in quickly
[Google Pixel 6] squidbutt:
Been running it daily with no problems for about 2 or 3 weeks now. No problems other than sometimes when I get a call the screen doesn't respond but if I turn the screen off and back on again it works.

But that may be only me
[Google Pixel 6] rachnov55:
I'm unable to fastboot my device as it's not even detected after i execute adb reboot bootloader...

i've installed all the drivers, but once it goes into fastboot mode my PC won't detect it.

can someone help?

is it because i'm on android 13 beta?
[Google Pixel 6] rachnov55:
nevermind...solved it..was a problem with my usb cable
[Google Pixel 6] vlucchetti:
I used the same process that has been used for rooting the pixels via Homeboy, just using the items specific to the 6 Pro.
[Google Pixel 6] Slim2none4u:
WHy would you share a guide on rooting the Pixel 6 in a guide for rooting the pixel 6?
[Google Pixel 6] thomasvtt:
Thank you for letting me know.
[Google Pixel 6] vlucchetti:
My pleasure, glad to give back some of what I got from homeboy and the other folks who have put out guides on rooting these phones.
[Google Pixel 6] Homeboy76:
Update

Magisk Canary - app-release_f42c089b-

25102

.apk 20Jul
[Google Pixel 6] Homeboy76:
Magisk Updates

Magisk Beta - 25.2 21Jul

Magisk Canary - app-release_9b61bdfc-25201.apk 21Jul

Magisk Stable - 25.2 21Jul
[Google Pixel 6] BHUSHAN7988:
I am about to get the pixel 6a next week.

I just want to know if i unlock the bootloader and not root (can't root untill zips/ota available), will my banking apps fail like Google pay (India), PhonePe, PayTm, etc.

Don't care about safety net just want my banking apps to work untill we get the zip to patch the boot image.
[Google Pixel 6] Homeboy76:
¯\_( ͡❛ ͜ʖ ͡❛)_/¯

This is a Google Pixel 6 thread. I think you want the Google Pixel 6a Forum.
[Google Pixel 6] BHUSHAN7988:
Let me rephrase can i use unlocked pixel 6 for all banking apps without flashing magisk+safety net fix
[Google Pixel 6] Homeboy76:
AFAIK, the answer is no.
[Google Pixel 6] tom1807:
No, bootloader unlocked without Magisk installed, Google flags your phone as insecure and so the banking apps.

The day 6a is officially shipped, the OTA/Images will be available.

Edit, this is still the Pixel 6 topic (no a), your questions belong to the Pixel 6a thread, like we have a Pixel 6 Pro thread.

Cheers
[Google Pixel 6] mad_tunes:
Sorry if the answers somewhere in this thread, but I've not been able to find it..

This guide worked a treat for me up until about a week ago.

I went to pay for someting with google pay, I got two beeps instead of one and it refused to work, Didnt get a screenshot or note the message though, as I was at the counter in a shop.

I've tried to re-do everything from the '

Pass Safety Net with SafetyNet Fix

' section a few times now, and get to the point of being able to open the google pay/wallet app and adding a card.

Once I enter the three digits from the back of my card, it says its contacting my bank and then 'This phone can't be set up for contactless payments'

I've updated both magisk and safetynetfix since (both were only one version behind to begin with), but still get the same

The play store says its certified.

YASNAC & SafetyNet Fix both say everything passes

It's ony a guess, but it might have started as google pay changed to wallet... I hadn't noticed any mention of wallet prior to the problem, at least.

I've searched here, googled, and tried various things but havent been able to re-add my card.

If I could make an old-style nandroid backup of the phone I would already have tried resetting it. I'd reset if needed, but would really like to avoid doing that and ending up in the same situation if pos.

What could/should I do to get it going again?

Thanks in advance
[Google Pixel 6] DNAblue2112:
I got mine working again by using magisk props to spoof the phone fingerprint with the pixel 6 fingerprint they provide plus installing gpay sqlite fix. I tried so much other stuff as well but those two were the last two I did before it started working again
[Google Pixel 6] rrusek:
Can any please confirm or deny if the follow module work under Magisk Stable - 25.2 21Jul:

Busybox for Android NDK 1.34.1

Dolby Atmos Magic Revision 1.1

GoogleDialerMod-Magisk 1.03

Systemless Hosts 1.0

Universal SafetyNet Fix 2.2.1

Zygisk - LSPosed 1.8.2

Much appreciate it.

Thank you,

RJR
[Google Pixel 6] Homeboy76:
I can't confirm all of the modules, but these should work with no problem:

- Busybox for Android NDK 1.34.1

- Systemless Hosts 1.0 (The latest version)

- Universal SafetyNet Fix 2.2.1

- Zygisk - LSPosed 1.8.2 (The latest version)
[Google Pixel 6] mad_tunes:
I'd already tried gpay sqlite fix, which hadn't done the trick on its own.

Just set a pixel 6 fingerprint using MagiskHidePropsConf as well, and I'm back in business.

Thanks a lot @DNAblue2112

Spoiler content hidden.
[Google Pixel 6] mad_tunes:
I've used these OK with 25.2:

GoogleDialerMod-Magisk 1.03

Systemless Hosts 1.0

Universal SafetyNet Fix 2.3.1
[Google Pixel 6] Homeboy76:
Pixel 6a, Pixel 6, and Pixel 6 Pro

https://twitter.com/i/web/status/1559398190574714881

* * * * * Regular Users * * * * *

https://twitter.com/i/web/status/1559410066993938432

* * * * * No Downgrading * * * * *

PSA: Once you update to Android 13 on Pixel 6, you can't go back

Android 13 is out for Pixel devices today. But if you have a Pixel 6, 6 Pro, or 6a, you may want to make sure you're ready before updating.

www.androidauthority.com

* * * * * This is why there is No Downgrading * * * * *

https://twitter.com/i/web/status/1559537708959154177
[Google Pixel 6] Homeboy76:
Update Magisk Canary

app-release_4737c511-25202.apk
[Google Pixel 6] navaneethnk:
any youtube for this ??/
[Google Pixel 6] Absoluttalent:
I am having issues taking any OTA updates. This is the 4th time when I followed directions and same result. I disabled modules and removed them, restarted, uninstalled magisk, take update, reinstall magisk and reboot. Then I'm met with the red text "your device is corrupted" and stays frozen on the boot screen with "Google" on it.

Holding power + vol up gets me back in, but I lose root and didn't get the OTA applied. So I need to update and redo the root process all over.

Any ideas what is the reason for this is? The only modules I used was systemless hosts file and safety net fix, and outside of YT vanced and AdAway (root version) , everything else on the phone is official apps from play store. It's a pain to do this every month for the update

Forgot to mention, this was with whatever the latest versions of magisk was. Back in March 24.13 or whatever it was at the time, June was the 25.1, and recently I was on 25.2
[Google Pixel 6] Slim2none4u:
I would advice using this tool.

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

xdaforums.com

I believe your issue is that you are not disabling Verity and Verification. This tool makes the process quick and painless.
[Google Pixel 6] Homeboy76:
If you are referring to the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 3. Take the OTA Update and Maintain Root instructions. You rebooted to soon. Additionally, an upgrade for the Google Pixel 6/Pro/6a to Android 13 requires flashing the bootloader to the a and b slot to avoid bricking your phone.

Further, the instructions in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Install/Update Factory Image keep data,

wipe data

, or use @badabing2003

PixelFlasher

are the instructions most people should use to upgrade to Android 13.
[Google Pixel 6] Homeboy76:
First, AFAIK disabling Verity and Verification are no longer required.

Second, there is ,now, a link to the PixelFlasher in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Install/Update Factory Image

keep data

,

wipe data

, or use @badabing2003

PixelFlasher

. Thanks for the reminder. :)
[Google Pixel 6] Absoluttalent:
I will have to try that tool then. I would've liked to do this without involving the computer. But guess that might be my option

Rebooting too early? I followed the directions and waited until after I get the reboot button from update and from magisk install to slot screen. I gotta wait longer after the process is completed to reboot?

And I was not doing the Android 13 update, just the monthly patches

But later when I get home, I will give the pixelflasher a shot
[Google Pixel 6] Homeboy76:
@Absoluttalent

If you were you trying to install the ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 3. Take the OTA Update and Maintain Root. You would be installing the August 2022 OTA (Android 13).

If were you just trying to install the OTA update you would be installing the August 2022 update (Android 13).

Please read the Updating Pixel 6, Pixel 6 Pro, and Pixel 6a devices to Android 13 for the first time section of the Factory Images for Nexus and Pixel Devices web site.

The steps for

installing the OTA

update are:

- uninstall Magisk (remove root)

- reboot

- take the OTA update

Root Phone

- Download the Factory image for August 2022

- Extract the boot.img and the bootloader-oriole-slider-1.2-8739948.img

- install Magisk manager

- Patch the August 2022 boot.img

- Put the Magisk_patched...img and the bootloader-oriole-slider-1.2-8739948.img on your computer, in the SDK Platform-tools folder (the folder with fastboot.exe and adb.exe in it).

- boot the bootloader

- adb reboot bootloader

- flash the magisk_patched...img

- fastboot flash boot magisk_patched...img

Install bootloader to a and b slots

-

This prevents bricking your Google Pixel 6 phone.

-fastboot flash bootloader bootloader-oriole-slider-1.2-8739948.img --slot all

-fastboot reboot-bootloader

-fastboot reboot

- Done!
[Google Pixel 6] Absoluttalent:
I had no idea the august update was with Android 13, it was only 1.45mb.

Thanks for the instructions on this though. Might have to go through it on my next days off.
[Google Pixel 6] Homeboy76:
Yup, the August 2022 Google Pixel 6 Factory/OTA Image is Android 13.

Factory/OTA Image

13.0.0 (TP1A.220624.021, Aug 2022)

(The 13.0.0 is the

Android Version number

.)

Build number: TP1A.220624.021
[Google Pixel 6] Homeboy76:
Update

SDK Platform-tools - r33.0.3
[Google Pixel 6] Homeboy76:
Update

Magisk Canary

app-release_38ab6858-25203.apk
[Google Pixel 6] Born<ICs:
What happened to ??

[Guide] Root Pixel 6 with Magisk, Android 12​
[Google Pixel 6] vandyman:
The thread title was changed from A12 to A13.

Reason,,

Google does not support Android 12 for the Pixel 6 as of August 2022.
[Google Pixel 6] Born<ICs:
What?

Google still supports A12, Factory Images back to 12.0 Oct 2021 are on Google's site. They have stopped providing further updates to A12 is all.

Some, like me, may want to root last 12.0 version etc and stay on 12.
[Google Pixel 6] tom1807:
The root method is still the same, doesn't matter whether A12 or A13 is written in the title.

Cheers
[Google Pixel 6] tiiiit74:
Hi everybody, sorry for my english (G. Translate). Need help please.

[SOLVED] Use a USB A-C cable, another computer and restart Step 2. Thanks for the help provided!

On my Pixel 6 Android 12 stock new out of the box, I started following the instructions.

Unlock bootloader OK.

So i do this :

"

Flash Factory Image Wipe Data

This will wipe your phone's Internal Storage.

Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:

bootloader-oriole-....img

flash-all.bat

image-oriole-....zip

radio-oriole-....img

On your phone:

Boot the bootloader

(Power off the phone => Press the Power and Down buttons until you see

Start

)

Connect your phone to the computer.

Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.".

No error but the phone reboot on Fastboot Mode > Start > Google boot animation > Bootloop > continually pressing volume down button during Google boot animation > Fastboot Mode...

I can send commands, it works, but what to do?

I must have forgotten or skipped a step (copy files on the phone before maybe ? must be something I didn't understand), I don't know what to do, can you help me, please ? Thank you very much.
[Google Pixel 6] capntrips:
Can you post the output of flash-all? Old versions of fastboot or some incompatibility between your phone and computer may be causing an issue.

I have to use a USB-A cable from my laptop, for example.
[Google Pixel 6] tiiiit74:
I'll try it tomorow in the morning from another computer.

Can you just confirm that at this stage, I didn't have to copy anything before from the computer to the Pixel's memory, just adb commands? I've not forgotten anything ? And from a stock Android 12 to a 13, no problem ?
[Google Pixel 6] tiiiit74:
Laptop with A-C USB cable, it seems to be better ! Wait...

"Resizing 'system_a' OKAY [ 0.003s]

Resizing 'system_ext_a' OKAY [ 0.003s]

Resizing 'system_b' OKAY [ 0.002s]

Resizing 'vendor_a' OKAY [ 0.001s]

Resizing 'vendor_dlkm_a' OKAY [ 0.002s]

Resizing 'vendor_b' OKAY [ 0.001s]

archive does not contain 'boot_other.img'

archive does not contain 'odm.img'

archive does not contain 'odm_dlkm.img'

extracting product.img (2661 MB) to disk... took 18.286s

archive does not contain 'product.sig'

Resizing 'product_a' OKAY [ 0.013s]

Sending sparse 'product_a' 1/11 (262116 KB) OKAY [ 7.327s]

Writing 'product_a' OKAY [ 1.018s]

Sending sparse 'product_a' 2/11 (262120 KB) OKAY [ 7.297s]

Writing 'product_a' OKAY [ 1.049s]

Sending sparse 'product_a' 3/11 (262128 KB) OKAY [ 7.145s]

Writing 'product_a' OKAY [ 1.001s]

Sending sparse 'product_a' 4/11 (262120 KB) OKAY [ 6.819s]

Writing 'product_a' OKAY [ 0.998s]

Sending sparse 'product_a' 5/11 (262120 KB) OKAY [ 6.494s]

Writing 'product_a' OKAY [ 1.034s]

Sending sparse 'product_a' 6/11 (262124 KB) OKAY [ 6.857s]

Writing 'product_a' OKAY [ 1.033s]

Sending sparse 'product_a' 7/11 (262124 KB) OKAY [ 6.893s]

Writing 'product_a' OKAY [ 1.026s]

Sending sparse 'product_a' 8/11 (262128 KB) OKAY [

................

Edit : @capntrips Thank you very much, it's done !!! Next step tomorrow !!! Have a good...night...day ?
[Google Pixel 6] capntrips:
I see you got it sorted in your last edit, but I figured I would answer the questions, in case any of them are still relevant.

To simply flash the latest firmware, there's no need to copy anything to the device. Once you're ready to root the device, you'll need to copy your firmware's boot image to the device to patch it with Magisk.

As for the upgrade from Android 12 to 13, it is recommended that you at least flash the Android 13 bootloader to both slots after the upgrade, so your device won't be unbootable if it tries to roll back to the previous slot.

If fastboot is on your PATH, there's no need to move anything around. If not, you'll need your scripts, zips, and images to be in the same folder as your fastboot binary to use the flash-all script (or you'll have to modify the script with the path to your binaries and/or images).
[Google Pixel 6] tiiiit74:
Thank you very much for your advice !

Not sure I understood everything on the first reading, I will deepen. A (easy 😉) tutorial to make these modifications ?

- I'm ready to root, need to flash the Android 13 bootloader to both slots before ? Or after is OK ?

Edit : i've found !!!

- If I systematically paste the files at the root of SDK Platform Tool (C://SDK Platform Tool for example), I don't modify anything, I can flash-all, it's just, i understand ?

Thanks a lot.
[Google Pixel 6] centifanto:
Was successful the second time when using the proper reboot sequence, but I am curious if anyone has insight into what happened in my following scenario the first time around.

Upon flashing my magisk patched boot, disabling verity and verification, I absent mindedly booted to system instead of rebooting to bootloader as I knew better and have done many times with rooting my OnePlus phones. I ended up with the expected "device is corrupted and cannot be trusted" message. I reflashed my patched boot to both slots and made sure to switch slots, but that didn't make the message go away, yet I could still boot, which was odd to me. So I ended up just sideloading the full image in recovery and started over.

Thank you for anyone who can explain what happened :)
[Google Pixel 6] tom1807:
That's related to the unlocked bootloader, won't go away.

Cheers

Tom
[Google Pixel 6] Lughnasadh:
The corruption message (red eio) is different than the unlocked bootloader message. In this case it refers to a hash mismatch.
[Google Pixel 6] centifanto:
Thanks for the reply, but I think you're thinking of the normal message "the bootloader is unlocked and software integrity cannot be guaranteed".

My error message said the device was corrupted
[Google Pixel 6] centifanto:
Thanks for the reply. What hash is Android looking at to trip this message? I performed the same steps to root after flashing back to stock and I don't get that message anymore. Just curious 🙂
[Google Pixel 6] capntrips:
See here for more info. The entire Verified Boot implementation is complex and error prone. It trips for a ton of things (and sometimes seemingly erroneously). Reflashing the boot partition (or even just a fastboot boot) is frequently enough to fix it.
[Google Pixel 6] Lughnasadh:
People have come across this corruption message doing a variety of things, from flashing patched boot images, to flashing kernels to updating monthly security builds in various ways. Here's a better explanation...

Verifying Boot | Android Open Source Project

source.android.com

Boot Flow | Android Open Source Project

source.android.com
[Google Pixel 6] centifanto:
Thank you both @Lughnasadh and @capntrips!

What's odd is I did reflash my boot image thinking that would fix but it didn't, had to reflash anew from sideload.

Thanks again for the info
[Google Pixel 6] Lughnasadh:
Yeah, sometimes flashing an old boot image (it will fail to boot) and then flashing a new boot image works. Sometimes sideloading an OTA works. Sometimes just waiting for the next monthly OTA works. It's a crazy thing with this Pixel 6 series and the changes that have come with it.
[Google Pixel 6] centifanto:
Very good info, thank you. Yeah maybe if I had flashed my stock boot, and then reflashed my patched it would have worked, but either way sideloading the OTA fixed it. Very odd. Thanks again