yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Nimueh:
I have no idea why all those guides have such complicated ways of updating ... when I updated from rooted December to 007 it was basically 3 steps:

Patch boot.img with Magisk, disable all modules

Reboot to recovery, sideload the OTA zip

Reboot to bootloader, boot patched img and then once booted direct install in Magisk

That worked fine for me, without all those bells + whistles. There might be instances where the "complicated" way is needed but I have no idea when or why 🤷‍♀️
[Google Pixel 6] t-ryder:
Even what you do seems complicated to me.

I download the factory image, patch the boot image with magisk, flash all needed stuff with 0riole-Flasher in one single step, done.

No disabling modules, no sideloading, booting images and whatever.

Works all fine here.
[Google Pixel 6] Mahoro.san:
I have just received an OTA update . It's 2GB, I have pause it so far as I don't want to lose root access.

Might I know how I can root after the OTA ?

Million thanks
[Google Pixel 6] Homeboy76:
:rolleyes:
[Google Pixel 6] Homeboy76:
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 3. Take the OTA Update and Maintain Root

Curious

Is this Google's April 2023 update?
[Google Pixel 6] Mahoro.san:
Thank you I got it working.

It's actually march update but I just got ota yesterday.

And another separate issue arrises that my 5G no longer works. It was working through the Network Signal Guru workaround.

Now, no matter how I config it through NSG, the 5G won't be used but only LTE
[Google Pixel 6] Homeboy76:
This is the first time i've read about a Google Pixel 6 using stock Google firmware having problems getting a 5G signal in the U.S.

What carrier are you using?

Are you using a Custom ROM or Google's beta firmware Android13/14?
[Google Pixel 6] iSupakilla:
Hey there, so yesterday I got an Update even though I was sure i'd turn off Auto-Updates. So the update has downloaded but it is waiting for my phone to restart before it applies it, am I screwed? am I cool to restart my phone?

Edit: reading the guy above asked the same thing. just gonna follow those instructions
[Google Pixel 6] iSupakilla:
hey man, can I get any help by chance? i'm in the same boot as you, lost root after the OTA update but now with ANY method trying to root i'm getting stuck in a boot loop. I've flashed the stock rom to both sections and that gets me out, i've also tried disabling all the modules, i redownloaded the stock file incase it was broken, i've tried PixelFlasher, and even a "fix" where people were saying they used a pixel 7 boot.img and everything is leading me back to the bootloop
[Google Pixel 6] Homeboy76:
@iSupakilla

13.0.0 (TQ2A.230305.008.E1, Mar 2023)

Download the 13.0.0 (TQ2A.230305.008.E1, Mar 2023) Factory image, extract the boot img, and patch it with magisk (Beta 26.1, Canary 26101, or Stable 26.1).

Flash it with SDK Platform-tools r.33.0.03

Done!
[Google Pixel 6] iSupakilla:
Magisk: Canary from the guide Here

Google Pixel 6 v13 (TQ2A.230305.008.E1)

AP Tools: 33.0.3-8952118
[Google Pixel 6] iSupakilla:
Did this with both PixelFlasher as well as your guide. i've downloaded this file twice just to double check
[Google Pixel 6] Homeboy76:
:oops: <<Duplicate Deleted>> :rolleyes:
[Google Pixel 6] Homeboy76:
Weird.

You can try dirty flashing:

The 13.0.0 (TQ2A.230405.003.E1, Apr 2023) factory image.

Extract the boot img, and patch it with magisk (Beta 26.1, Canary 26101, or Stable 26.1).

Flash it with SDK Platform-tools r.33.0.03
[Google Pixel 6] iSupakilla:
Unfortunately the same thing happens. running it through PixelFlasher now so I can post the Log

Log Attached
[Google Pixel 6] chuppito:
hello, where did you find the download of TQ2A.230405.003.E1?

on the site https://developers.google.com/android/images?hl=fr the version stops at 13.0.0 (TQ1A.230205.002, février 2023).

or if you have the unmodified boot.img so I can root my phone again. THANKS
[Google Pixel 6] simplepinoi177:
it's an established issue/bug that the latest firmware images sometimes only display when in English -- it looks like you are looking at the French version of the website (the "fr" in the url)...

I'm betting you'll see it once set in English/US...
[Google Pixel 6] chuppito:
Yes thanks

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

That work
[Google Pixel 6] badabing2003:
@iSupakilla

No need to double post, besides it is against the forum rules.

See my answers in the PF thread, I'm not going to repeat them here.

If you fear that you might not catch the attention of certain people in case they are not too active in the thread you are posting, you can @ them to catch their attention.

Post back your results, doesn't matter which thread, just make sure it's only one.
[Google Pixel 6] iSupakilla:
two different guides i was trying so it was two different people I was asking questions to. my bad
[Google Pixel 6] Homeboy76:
OP Changes

I added additional notes to the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~,

5. Root/Reroot with Magisk and Pass SafetyNet.,

• Patching the boot/init_boot.img - to root/reroot.,

1 & 2.
[Google Pixel 6] Homeboy76:
Update

SDK Platform Tools r. 34.0.1

Not fixed
[Google Pixel 6] Mepsipax:
Quick question about the play integrity check guide: it says to put "Google Play Store, Google Pay, Google Wallet etc" on denylist. What does "etc" stand for? What should I deny?

I have these right now. Any I can leave or need to add?
[Google Pixel 6] Homeboy76:
etc.

used at the end of a list to indicate that further, similar items are included.

"protect seedling from damage caused by feet, lawnmowers, pets, etc."
[Google Pixel 6] Mepsipax:
Haha, yea sure. I know what etc means, but I meant to ask what apps and services specifically I should deny to pass the integrity check. That's why I attached my screenshot to show what I denied, but I'm not sure if all of those are needed or if I'm missing some app I should deny as well.

Is there no definitive list of apps we need to deny to pass integrity?
[Google Pixel 6] Homeboy76:
:oops: <<Deleted - double post>>
[Google Pixel 6] Homeboy76:
AFAIK, there is no definitive list of apps to deny.

The apps you add to the deny list are the apps you use that need hiding i.e., some use the netflick app and need to add it to the deny list.
[Google Pixel 6] Mepsipax:
I mean for passing the play integrity check in order to achieve certified device status, there's a specific list of apps to deny, right? Like the play services for example or the play store? Or did I get that wrong?
[Google Pixel 6] choukajohn:
Hi there,

Today I tried to update my pixel 6 with the latest factory image TQ2A.230505.002, May 2023 and the latest SDK Platform tools r34.0.1 but it didn't work and the result was a corrupted device warning screen.

So I had to flash again the may factory image using the SDK Platform tools r33.0.3.
[Google Pixel 6] Homeboy76:
OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,

5. Root/Reroot with

Magisk

and Pass SafetyNet.,

•

Pass Safety Net with SafetyNet Fix

,

4. Get Device Certified...
[Google Pixel 6] Homeboy76:
<<Comment removed - double post>>
[Google Pixel 6] Homeboy76:
Did you get any errors while flashing?

Did fastbootd work?
[Google Pixel 6] Homeboy76:
<<Removed comments - Original SPAM post deleted>>
[Google Pixel 6] choukajohn:
No error

Fastbootd doesn't work with SDK 34.0.1

Device is booting but now, every time I boot the phone, I have the corrupted device warning screen and I have to force boot.

If anyone could help.

Thanks.
[Google Pixel 6] Homeboy76:
When the phone boots, back up your data and wipe the phone and set it up or try flashing the other slot.

Flashing the other slot:

If your phone is rooted, open Magisk and disable all modules then reboot.

Please, verify the flash-all.bat file in the SDK Platform-tools folder has been edited:

Edit this line in the flash-all.bat file

fastboot -w update image-oriole-aa9a.999999.999.zip

Remove the -w to Keep Data.

Rename the attached flash-other.txt file

flash-other.bat

, put it in the

SDK Platform-tools folder (the folder with fastboot.exe in it).

Boot the bootloader

connect the phone to your pc

open a command prompt on the pc in tge SDK Platform tools folder and type flash-other
[Google Pixel 6] Lughnasadh:
Flash the previous month's boot image (it won't boot but that's ok), then flash the boot image from your current build. That should get rid of the corrupt message.
[Google Pixel 6] choukajohn:
To @Homeboy76 and @Lughnasadh

Thanks guys for your answers.

First I tried to flash the other slot but it doesn't worked, corrupted device warning screen was still there.

Then, I flashed boot.img from april update and rebooted the phone, no more corrupted device warning screen but a prompt from android because of corrupted data asked to wipe data or try again.

I rebooted device in fastboot and flash the boot.img from may then reboot to android.

No more corrupted device warning but again the corrupted data message. This time I choosed "try again" and android finally booted up.

Everythings seems to work properly, root and safetynet fix.
[Google Pixel 6] Homeboy76:
Update

I tested SDK Platform-tools r. 34.0.1 it is

not fixed

. There are still problems with fastbootd. Use SDK Platform-tools r. 33.0.3
[Google Pixel 6] Homeboy76:
Magisk Canary Update

app-release_47d2d4e3-26102.apk

Notes:

Tap app-release.apk

Tap 3 dots (...) across from 10.x MB

Tap Download
[Google Pixel 6] r00tcracker:
Any reports of this being screwed up like that saga we went through a few months ago?
[Google Pixel 6] Homeboy76:
One, https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88570403
[Google Pixel 6] r00tcracker:
Damn!!!!! Guess I'm staying on 26101.

Thanks for the update!! :D
[Google Pixel 6] Homeboy76:
Did you read this, it was in the same thread:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88569739
[Google Pixel 6] Homeboy76:
SDK Platform-tools Update

SDK Platform-tools r. 34.0.3, was released May 22, 2023.

@badabing2003 reported a problem when using it.

https://xdaforums.com/t/platform-to...7-pro-cheetah-safetynet.4502805/post-88571575

@Lughnasadh, suggested a fix.

https://xdaforums.com/t/platform-to...7-pro-cheetah-safetynet.4502805/post-88571601

@badabing2003, confirmed the suggested fix works.

https://xdaforums.com/t/platform-to...7-pro-cheetah-safetynet.4502805/post-88571617

If you use Linux or Windows SDK Platform- tools r. 34.0.3. You must set the environment variable:

Linux

Windows

Note:

If you have any problems with SDK Platform-tools 34.0.3

. You can get SDK Platform-tools 33.0.3 here.
[Google Pixel 6] r00tcracker:
I did not, but...... might as well wait :D
[Google Pixel 6] choukajohn:
Hi,

Did you test any update or rom flashing on Pixel 6 with the rev. 34.0.3 ?

I'm asking because with the rev. 34.0.1, I already had to set ANDROID_PRODUCT_OUT as an environment variable but flashing the rom was still failing.
[Google Pixel 6] Homeboy76:
What error message did you get (screenshot)?

Which ROM are you trying to flash?
[Google Pixel 6] choukajohn:
I don't have any error, my problem was solved using the SDK rev 33 for the May update.

I just want to know if you have tested the latest SDK platform tools rev 34.0.3 with a Pixel 6 or not.
[Google Pixel 6] Homeboy76:
No.
[Google Pixel 6] Murmel2k:
I today updated my phone months after I figured out that the OTA update with Magisk doesn't work. Before trying to take the next OTA update and bricking my phone again: Does taking the OTA update with Magisk (assuming to deactivate all modules, uninstalling Magisk and to install magisk into the inactive slot) now work?
[Google Pixel 6] shoey63:
Nope.

In fact even after restoring images it won't do an OTA update at all unless you reboot and thus lose root.

You need a PC or laptop now.

Pixel Flasher is the best tool for the job
[Google Pixel 6] Homeboy76:
Update

XDA members are reporting more issues with SDK Platform-tools 34.0.3

Use SDK Platform-tools 33.0.3
[Google Pixel 6] choukajohn:
Hi,

Does someone can share SDK Platform-tools 33.0.3 for Linux please?

Thanks.
[Google Pixel 6] badabing2003:
https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip - Windows

https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip - Mac

https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip - Linux
[Google Pixel 6] Homeboy76:
Update

[MODULE] [MOD] Universal SafetyNet Fix by Displax

v2.4.0-MOD_1.3

Fix "stat /sys/fs/selinux" access time reading. Also removed archaic MIUI cross-region shenanigans. Thanks to PR by aviraxp!

Ignore props changing on Xiaomi.eu. This fixes randomly attestation failings. So strange ROM...
[Google Pixel 6] Homeboy76:
Magisk Canary Update - notes.md:

Download: app-release.apk
[Google Pixel 6] Lughnasadh:
Beware that if you are on A14B3.1 (maybe other builds as well), you may have trouble patching the boot image with this new Canary release. Couldn't do it on my Pixel 6 Pro. Issue has been opened on Magisk Github.
[Google Pixel 6] Lughnasadh:
Looks like there is a Pull Request in progress to fix this issue.
[Google Pixel 6] Homeboy76:
Thanks for the update. :)

Does it only affect Android 14 beta or does it also affect Android 13?
[Google Pixel 6] Lughnasadh:
Have no idea. Judging by the PR, I suspect it affects both.
[Google Pixel 6] pa.pn2:
Did someone successfully parched June build A13 with latest canary 26103?or should I better wait
[Google Pixel 6] badabing2003:
https://xdaforums.com/t/guide-pixel...ate-root-pass-safetynet.4356233/post-88700369
[Google Pixel 6] Homeboy76:
Magisk Canary (a8c4a33e) (26103)

Is not working for everyone, it has some issues that need fixing:

Use, attached,

Magisk Canary app-release_47d2d4e3-26102.apk until it (26103) is fixed.
[Google Pixel 6] Cornloaf:
Anyone else getting prompted to update to Android 13 on their Magisk rooted Pixel 6 Pro? Mine just started a week ago. Have had the Android 13 June 2023 update since it released. Happens with both 26100 and 26102 Canary releases.
[Google Pixel 6] hugehead83:
I got it this morning; it seemed odd to me too since I have been on Android 13 for quite a while now.

I was having trouble patching the boot.img with Magisk. When I suspected a Magisk issue, and confirmed with Cornloaf's post above. I rolled back a version of Magisk and everything went smoothly. This is only the second time since the Pixel 6 release that I've had to do that IIRC.

Thanks All!
[Google Pixel 6] Homeboy76:
Do you have Automatic system updates turned off?

Setting > System > Developer options > Automatic system updates
[Google Pixel 6] lukypuie:
I'd like to lock the bootloader after having installed LOS20, is it risky?

Can you return to stock with a locked bootloader? I've heard of the Rescue Mode --> https://pixelrepair.withgoogle.com/steps

that can return to stock without using the bootloader, it's a sort of recovery mode, but only works if it detects an old android version installed (but with a locked bootloader too!)

Can anyone confirm?
[Google Pixel 6] Homeboy76:
Yes it is risky, you could brick your phone.

One, of the reasons xda members

unlock their bootloader

is to install Custom ROMs (lineageOS Installation Instructions).

My suggestion is do not repeat do not try

locking the bootloader

without having a 100% stock ROM on your phone. Several, XDA members have bricked their phone doing it.
[Google Pixel 6] lukypuie:
Anyway it looks loke it prevents me from locking the bootloader if it detects a non stock pixel image, in fact fastboot flashing lock gives me "invalid android images, skip locking"

I will just stick with the bootloader unlocked
[Google Pixel 6] Homeboy76:
UPDATE - July 5, 2023

<<See post 651>>
[Google Pixel 6] krotin:
Hello, Im enrolled in beta 14.

My P6 downloaded the latest upb4.230623.005.

I'd like to download it to patch boot img.

I can't seem to find the upb4.230623.005 file any_where ???

Answering myself I was too early.

Here it is :

https://dl.google.com/developers/an...ole_beta-upb4.230623.005-factory-ea5b8c42.zip

130723@15h42

Updated after downloading upb4 resulted in noboot with magisk

I rooted boot img with magisk delta canary

No worries.
[Google Pixel 6] Homeboy76:
UPDATE - July 5, 2023 <<Revised>>

SDK Platform-tools r34.0.4

Notes:

Changelog see #3 below

This brave soul verified it is working with

Android 14 beta

.

:( Still use Platform-Tools r. 33.0.3 instead of the newest - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet by roirraW "edor" ehT

<<Edited :( it's true - 33.0.3 >>
[Google Pixel 6] go_roy:
I'm on Magisk 26101 (d0c93842) and currently on the May update (230505.002). Can I keep the Magisk version and update to July or should I bump to the Canary Magisk (47d2d4e3-26102) from a few posts above before updating?
[Google Pixel 6] krotin:
I believe I was on MAgisk and July update bootlooped so I went Magik Delta and it Worked flawlessly
[Google Pixel 6] Lughnasadh:
You can continue to use Canary 26101 on the July build if you want.
[Google Pixel 6] LazerOrca:
I'm not even sure where to even look to see which factory or OTA image I should download for USCC (U.S. Cellular), or if it is even possible. They are regional. I have rooted USCC phones in the past, but this was quite a while back. Required special modem files and such to do. From what I understand, USCC phones are global variants now, but I could be wrong.

The best I could find is I went to the T-Mobile website and my phone IMEI was compatible for a switch and my EID is compatible with eSim. IMEI is supposedly compatible with Verizon as well just to complicate this more for me.
[Google Pixel 6] Homeboy76:
I'm assuming you have a Google Pixel 6 (oriole) phone.

Factory image

OTA image

If it is not a Google Pixel 6 (oriole) phone.

¯\_( ͡❛ ͜ʖ ͡❛)_/¯
[Google Pixel 6] Homeboy76:
Magisk Canary Update

Magisk (d390ca2f) (26104).

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download

Magisk (d390ca2f) (26104)

Lots of code is migrated over to Rust!

[App] Properly preserve boot.img when patching Samsung firmware

with init_boot.img

[MagiskBoot] Directly handle AVB 1.0 signing and verification without

going through Java implementation

Diffs to v26.1

[MagiskBoot] Support extracting boot image from payload.bin

[MagiskBoot] Support cpio files containing character files

[MagiskBoot] Support listing cpio content

[MagiskBoot] Directly handle AVB 1.0 signing and verification without

going through Java implementation

[Daemon] Make daemon socket a fixed path in MAGISKTMP

[resetprop] Support printing property context

[resetprop] Support only printing persistent properties from storage

[resetprop] Properly support setting persistent properties bypassing

property_service

[MagiskSU] Support -g and -G options

[MagiskSU] Support switching mount namespace to PID with -t

[App] Support patching boot image from ROM zips

[App] Properly preserve boot.img when patching Samsung firmware

with init_boot.img

© 2023 GitHub, Inc.
[Google Pixel 6] Lughnasadh:
Can confirm that patching the boot image with Magisk Canary 26104 is now working properly. The issue with Canary 26103 appears to be resolved.
[Google Pixel 6] Homeboy76:
<<Edited>>

Update Displax/safetynet-fix Mod forked from kdrag0n/safetynet-fix

Changelog: v2.4.0-MOD_2.0

Fix KernelSU support. You still need "ZygiskOnKernelSU".

Fix WiFi calling on some devices (and maybe other related issues) by moving changing ro.product.first_api_level from global namespace to GMS only.

Pass MEETS_STRONG_INTEGRITY[. By default you need device that launched with Android 13+ or custom ROM that manipulate with ro.product.first_api_level (>= 33 / or null / or not present).

If you want to play with it more complex - use separate "-STRONG" build. NOTE: Various system issues are possible on "-STRONG" build! (Fixed by Google)

Displax's v2.4.0-MOD_2.0 was Fixed by Google.

Use Displax's v2.4.0-MOD_1.3....
[Google Pixel 6] BraveOtter:
Just a probably stupid question:

What does it mean "100 percent stock"? Can I safety lock the bootloader after root the phone and install magisk if I do not change rom? or do i need wipe all modifications including root and magisk?
[Google Pixel 6] Homeboy76:
Wipe all modifications including root and Magisk.
[Google Pixel 6] badabing2003:
@BraveOtter

Make sure you do it on both slots as well.

Bascially you want to flash stock on both slots before locking.
[Google Pixel 6] BraveOtter:
So if I root the phone, the bootloader should be unlocked all the time right? Well I'll think a little more to decide if it's worth it. Thanks for clarifying it for me.
[Google Pixel 6] badabing2003:
It's recommended,

There are some who lock it while being rooted, but that's very risky, if anything goes bad, and it could when OTA is pushed, then you're locked out with no way of fixing it.
[Google Pixel 6] Homeboy76:
Yes, before you root the phone the bootloader must be unlocked and remain unlocked while you are rooted. Should you decide to relock the bootloader. Make sure you return the phone to

stock

before you relock the

bootloader

.
[Google Pixel 6] Homeboy76:
Magisk Canary Update

Magisk (ee34f775) (26105).

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download

Magisk (ee34f775) (26105)

[MagiskPolicy] Fix patching extended permissions

[MagiskPolicy] Support more syntax for extended permissions

[MagiskPolicy] Support print out the loaded sepolicy rules

Diffs to v26.1

[MagiskBoot] Support extracting boot image from payload.bin

[MagiskBoot] Support cpio files containing character files

[MagiskBoot] Support listing cpio content

[MagiskBoot] Directly handle AVB 1.0 signing and verification without going through Java implementation

[Daemon] Make daemon socket a fixed path in MAGISKTMP

[resetprop] Support printing property context

[resetprop] Support only printing persistent properties from storage

[resetprop] Properly support setting persistent properties bypassing property_service

[MagiskSU] Support -g and -G options

[MagiskSU] Support switching mount namespace to PID with -t

[MagiskPolicy] Fix patching extended permissions

[MagiskPolicy] Support more syntax for extended permissions

[MagiskPolicy] Support print out the loaded sepolicy rules

[App] Support patching boot image from ROM zips

[App] Properly preserve boot.img when patching Samsung firmware with init_boot.img

© 2023 GitHub, Inc.
[Google Pixel 6] huskyvmaske:
Help 🥲, recently updated OTA, lost root, trying to restore root as follows

1. Downloaded factory image from https://developers.google.com/android/images (versions are the same (13.0.0 (TQ3A.230605.010, Jun 2023)).

2. extracted boot.img

3. Patched with magisk

4. adb reboot bootloader

5. fastboot flash boot ./magisk_patched-26000_sT7DP.img

6. fastboot reboot

But after all these manipulations root did not appear, I tried different versions of magisk, but to no avail, maybe the reason is that before the upgrade I did not disable magisk modules, but later I did magisk --remove-modules in adb shell, what could I have missed?