yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Homeboy76:
June?

What month were you on before you updated the OTA to June 2023?

I hope you were not taking the June 2023 OTA to

roll back

.

Why?

Updating Pixel 6, Pixel 6 Pro, and Pixel 6a devices to Android 13 for the first time

Warning: The Android 13 update for Pixel 6, Pixel 6 Pro, and the Pixel 6a

contains a bootloader update that increments the anti-roll back version for the bootloader.

This prevents the device from rolling back to previous vulnerable versions of the bootloader. After flashing an Android 13 build on these devices you will not be able to flash and boot older Android 12 builds. For developers who need to develop and test against an Android 12 environment, a special Developer Support Build that contains the bootloader update should be used.

After taking an Android 13 update and successfully booting the device post update, an Android 12 build resides in the inactive slot (seamless updates for more information on slots) of the device. The inactive slot contains an older bootloader whose anti-rollback version has not been incremented. If the active slot is then flashed with a build that fails to boot, the fallback mechanism of seamless updates kicks in and the device tries to boot from the inactive slot. Since the inactive slot contains the older bootloader, the device enters an unbootable state.

To avoid hitting this state, if you are flashing a Pixel 6, Pixel 6a, or Pixel 6 Pro device with an Android 13 build for the first time, please flash the bootloader partition to the inactive slot after successfully updating and booting into Android 13 at least once. This can be done by following these steps:...

Did you try booting safe mode and then rebooting?
[Google Pixel 6] huskyvmaske:
I honestly don't remember what version I had before the current update, however I stoically ignored update notifications for a month or so. (It was definitely version 13, but I can't remember which one.)

One more thing, a feeling that at the first firmware was root, although magisk and did not show it.

Why? I use Fabricate Info to hide gesture bar and it worked, but root was not active... after I uninstalled magisk modules this hack stopped working.

Unfortunately rebooting in safe mode did not change anything
[Google Pixel 6] Homeboy76:
What Magick app did you install (Alpha/beta/Canary/Delta/stable)?

Did you check for dual Installation of Magisk of app?

[OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,

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

Patching the boot.img - to root/reroot.

, 1. , • Open the Magisk Manager app...].
[Google Pixel 6] huskyvmaske:
Yes, I flashed boot.img with magisk (stable) and tried to fastboot with it, also tried canary, but to no avail
[Google Pixel 6] badabing2003:
The issue is multiple Magisk Managers fighting with each other.

You probably had a hidden Magisk and installed another or you did unhide which did not completely remove the stub

The solution to this is uninstall all Magisk managers (hidden or otherwise)

The easiest way to discover them all is to install TB Checker from Playstore

Run Xposed Check

Check for things that fail, you should see the package name of Magisks it find.

Uninstall that package

Repeat the TB Checker until there are no more Magisk Managers installed.

Reboot

Install Magisk Manager (if Magisk doesn't automatically popup the stub) and you should be ok, it should detect root or might ask you to reboot to finish setup.
[Google Pixel 6] Homeboy76:
@badabing2003, solution to your problems with Magisk is correct (post #672).

I asked in post # 670 if you checked for

dual installation of the Magisk app

, and pointed you to the section of the OP with a link to TB so you could check for

dual installation of the Magisk app

.
[Google Pixel 6] huskyvmaske:
Tell me please, I check, from the errors I see only the following, it means that I do not have magisk installed, right?

Also I see magisk mentioned here (screenshot 2), but I don't see it in installed applications

After that I tried to reboot the phone and install it again, but after flash the result is the same

Spoiler content hidden.
[Google Pixel 6] badabing2003:
Yes you do have Magisk installed and it's hidden, that fzcw.... Is the package name

If you have already flashed patched image, you don't need to flash again, just follow the cleanup of Magisk steps.
[Google Pixel 6] Homeboy76:
He @badabing2003 is fast and correct: :ROFLMAO:

HIDDEN

Magisk Random Package Name:

fczw.oejxcewf

Fail x
[Google Pixel 6] huskyvmaske:
Thanks! I was confused because I couldn't find this app in the list of apps, but after I uninstalled it via adb, everything was back to normal
[Google Pixel 6] bdr127:
Is 26105 safe to use with the August update?
[Google Pixel 6] bdr127:
Well, I just tried to update to the August 2023 update (T-Mobile and T-Mobile MVNOs), and now I'm stuck in a bootloader bootloop after patching the Magisk boot image. I first updated to 26105, and then I definitely disabled the Magisk modules before patching. As in the instructions, "if your phone boot loops" - I tried patching the stock boot.img but that didn't fix it. I tried the adb wait-for-device shell magisk --remove-modules, but it just sits there at the command prompt and never does anything.

Please help me get my phone back!

EDIT: Nevermind.... I just tried switching from slot a to slot b, and now the phone boots!
[Google Pixel 6] Isupooov666:
Friends, hello again. I wrote about my problem. Through fastboot I calmly put, RisingOs, Crdroid, now I'm on it.

Tried to install derpFest, superiorOs. As installed tedious files, did a reboot in recovery, format data, installation through adb. I write adb sideload rom.zip. flashes successfully, I press reboot and I have a brick.... Does not respond, after about 5 minutes successfully booted into recovery. The same or different firmware I'm trying to install. Through adb sideload to flash still can not... I installed full stock via fastboot. Does anyone have any ideas?

Thanks in advance, and sorry 😞
[Google Pixel 6] Homeboy76:
If you are trying to install the

Stock August 2023 factory image

:

OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,

2. Manually Install/Update Factory Image keep data or wipe data.,

•

Flash Factory Image Wipe Data

If you are trying to install a

Custom ROM

:

OP, ~ ~ ~ Part III - OTHER ~ ~ ~, 1. Custom ROMs, •

Need help with a Custom ROM?
[Google Pixel 6] Isupooov666:
Yes, need help with installing a custom Rom
[Google Pixel 6] Homeboy76:
Please read, OP (post #1), ~ ~ ~ Part III - OTHER ~ ~ ~, 1. Custom ROMs, •

Need help with a Custom ROM?
[Google Pixel 6] Homeboy76:
UPDATE - Platform-tools r.34.0.4

You can use Platform-tools r.34.0.4 to

Dirty flash

the Google factory image. @Lughnasadh has tested it.

Multiple platform-tools_r34.0.4...zip were posted. You can verify you are using the correct revision of platform-tools_r34.0.4...zip by insuring the SHA256 matches the SHA256 below:

platform-tools_r34.0.4-windows.zip

SHA256

520a453af1d0baf1939a80038a816cb8de40d000542b1a71bf60ba6fc80784d9

platform-tools_r34.0.4-linux.zip

SHA256

f2eee6e8220f3dfde6e1acc93c5b25d3d8bd215c0b03585b21665f1ea30d66ba

platform-tools_r34.0.4-darwin.zip

SHA256

c60d9ee0acade673b649543b2d53c632ba54f9ca083ed612176105117fa16102
[Google Pixel 6] Homeboy76:
Magisk Beta Update

Magisk Beta v26.2

[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 printing 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

Magisk Canary Update

Magisk (e47e869f) (26201).

Sync with public release

Diffs to v26.2

N/A

© 2023 GitHub, Inc.

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 6] Homeboy76:
Magisk Canary Update

Magisk (de00f1d5) (26202)

[General] Fix device information detection script

Diffs to v26.2

[General] Fix device information detection script

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 6] Homeboy76:
Magisk Canary Update

Magisk (96e559fb) (26203)

[General] Update BusyBox to 1.36.1

[General] Fix compiling toolchain that produces broken arm32 executables

Diffs to v26.2

[General] Fix device information detection script

[General] Update BusyBox to 1.36.1

[General] Fix compiling toolchain that produces broken arm32 executables

magisk-files/notes.md at canary · topjohnwu/magisk-files · GitHub

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 6] Homeboy76:
Magisk

Beta/Stable

Update

Magisk Beta/Stable v26.3

[General] Fix device information detection script

[General] Update BusyBox to 1.36.1

[General] Update toolchain that produces broken arm32 executables

[App] Fix root service unable to bind on OnePlus devices

Magisk Canary Update

Magisk (d4e552d0) (26301).

Upstream to latest release

Diffs to v26.3

N/A

Download Magisk Canary

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 6] fillwithjoy1:
Hey I have momo and its detecting that my bootloader is unlocked, is there anything I can do about it?
[Google Pixel 6] Homeboy76:
This thread has the most information about

momo

: Magisk General Support / Discussion

Search it for

momo

for an answer to your question. If you do not find an answer to you question in your search results, post your question on that thread. Additionally, you should post your phone model, the ROM you are using, the type Magisk you are using, and it's revision number.
[Google Pixel 6] TaleSeeker:
Hi, can someone help me please. I don't know what I am doing wrong.

I just bought a Pixel 6 and followed the steps at ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 3. (NEW) Manually Install/update the OTA image

keep data

and

root/re-root

your phone

I am at the last step. Which is to flash the magisk image: "Type: fastboot flash init_boot magisk_patched-99999_aA99a.img at the command prompt and press Enter."

This is the error that I got:

The bootloader is still unlocked. When I go to bootloader to run fastboot flash command, it shows this error.

More Context:​

1. I am using "fastboot version 33.0.3-8952118"

2. I side loaded "oriole-ota-tq3a.230805.001.a1-fcee5ddb.zip"

3. I am using magisk version d4e552d0 (26301) to patch the above zip file.
[Google Pixel 6] Homeboy76:
The command should be fastboot flash boot magisk_patched-99999_aA99a.img
[Google Pixel 6] TaleSeeker:
This is the error I get when I try that:
[Google Pixel 6] TaleSeeker:
nevermind, it changed "init_boot" to "boot" and it worked. I don't know where I get "init_boot" from.
[Google Pixel 6] Homeboy76:
Google's September 2023 factory and OTA are up!
[Google Pixel 6] sineste:
am I missing anything wrong or they just took it down? I installed it early today and now can't find it. hope nothing is wrong.
[Google Pixel 6] deusfaux:
won't sideloading the latest OTA in section 3 fail on an already rooted device, by detecting the modified boot.img? does it not need to be un-rooted first?
[Google Pixel 6] Homeboy76:
No, side loading the OTA installs the OTA image to the inactive slot and removes root.
[Google Pixel 6] deusfaux:
So that's only an issue with normal OTA done through the OS?

I guess I'll try it next time.
[Google Pixel 6] deusfaux:
tried it for A14. very easy, straightforward, worked successfully. OS never booted with root disabled, so apps I had that require it didn't need repairing/resetting. that's what I was looking for and that method did it.

suggestion: clarify what the user should see for a successful sideload. 'finishes' could mean it fails. should say 'status 0' right?
[Google Pixel 6] Homeboy76:
Yes!

When side loading the OTA image finishes, the "user" should see:

On their computer,

C:\platform-tools>adb sideload cheetah-ota-up1a.999999.999-9a99a999.

Total xfer: 2.00x

C:\platform-tools>

On their phone, ...status 0
[Google Pixel 6] deusfaux:
Yeah, put that in your OP!

Thanks for everything
[Google Pixel 6] bdr127:
Everything working okay for the October 2023 update to Android 14? Does the latest SafetyNet Fix from krag0n/Displax pass SafetyNet and Play Integrity for A14?
[Google Pixel 6] Homeboy76:
Yes.

AFAIK Displax's 1-3 Safety fix and Play integrity work.
[Google Pixel 6] Homeboy76:
Magisk Canary Update

Magisk (0352ea2c) (26302).

[MagiskBoot] Don't pad zeros if signed boot image is larger

[MagiskPolicy] Fix genfscon and filename_trans

[MagiskPolicy] Fix bug in libsepol

[Zygisk] Fix and simplify file descriptor sanitization logic

[App] Prevent OOM when patching AP tarfiles

[App] Fix bug in device configuration detection

[Daemon] Fix certificate parsing of APKs

[General] Fix logging errors from C++ code being ignored

Diffs to v26.3

[MagiskBoot] Don't pad zeros if signed boot image is larger

[MagiskPolicy] Fix genfscon and filename_trans

[MagiskPolicy] Fix bug in libsepol

[Zygisk] Fix and simplify file descriptor sanitization logic

[App] Prevent OOM when patching AP tarfiles

[App] Fix bug in device configuration detection

[Daemon] Fix certificate parsing of APKs

[General] Fix logging errors from C++ code being ignored

magisk-files/notes.md at canary · topjohnwu/magisk-files · GitHub

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 6] Homeboy76:
Magisk Beta/Stable Update

Magisk-v26.4

[MagiskBoot] Don't pad zeros if signed boot image is larger

[MagiskPolicy] Fix genfscon and filename_trans

[MagiskPolicy] Fix bug in libsepol

[Zygisk] Fix and simplify file descriptor sanitization logic

[App] Prevent OOM when patching AP tarfiles

[App] Fix bug in device configuration detection

[Daemon] Fix certificate parsing of APKs

[General] Fix logging errors from C++ code being ignored

Magisk Canary Update

app-release (aa6c7c15) (26401)

Sync with public release

Diffs to v26.4

N/A

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 6] Homeboy76:
SafetyNet Fix

Google has made some changes that caused a SafetyNet Fix problem: Displax's SafetyNet Fix 2.4.0-MOD_1.3 is not passing Device Integrity.

Use chiteroman's

Play Integrity Fix - Latest version
[Google Pixel 6] devilsshadow:
found this out the hard way during checkout at my local supermarket. I initially just reflashed displax's modded fix again (v2.0) but it did nothing and was not passing device integrity. Chiteroman's fix works great though.
[Google Pixel 6] Homeboy76:
SafetyNet

A Google patch has rendered chiteroman's Play Integrity Fix inoperable.

chiteroman fix, V13.
[Google Pixel 6] LpowerSolace:
I just lost root after installing the latest security update. Which steps are actually needed to get root back, for I'm guessing not the factor image one?
[Google Pixel 6] Homeboy76:
If updated via the OTA automatic update, download the full OTA image and patch the boot.img. Then flash it:

fastboot flash boot magisk_patched...img
[Google Pixel 6] Dj Telo:
How can I prevent these updates from happening? I've just started a long weekend without computer access and I just lost root... Annoying!
[Google Pixel 6] Homeboy76:
Settings >> Developer options >> Automatic system updates >> disable it
[Google Pixel 6] SeMmyT:
Hello guys

I've run into an issue after updating to the latest 14.0.0 (UP1A.231105.003, Nov 2023) firmware version.

Before installing the update i've uninstalled Magisk via "Restore images" option as usual, the update got installed - I downloaded the factory image(oriole-up1a.231105.003-factory-74f703f2, made sure) and extracted the boot, launched "Settings"(hidden Magisk) - it asked me to restore Magisk, went through it.

Afterwards I've patched the boot via magisk, rebooted to fastboot and booted the patched boot in.

The phone tried booting up a few times and gave me an error "Can't load android system, your data may be corrupt" with an option to try again. Try again as it seems boots with the regular boot, so no issues afterwards - but I'm unable to get rooted :(

I tried patching with Canary, tried using the latest platform-tools version - neither helped.

Googling for the issue didn't give a solution yet. Any advices?:[

All good, question resolved.
[Google Pixel 6] SeMmyT:
Neeeeeeeevermind, It seems the boot image got corrupted at some step - coz after I downloaded it to the phone through google drive instead of telegram, it worked.
[Google Pixel 6] Homeboy76:
<<Deleted>>
[Google Pixel 6] Homeboy76:
Glad you found the problem and fixed it. :)
[Google Pixel 6] Dj Telo:
Such a noob question after >10 years rooting Android. Thanks for the guidance. I was looking at this option under the System Update section.
[Google Pixel 6] bobby8921:
Now that Play Integrity Fix is broken, is it an option to lock the bootloader and preserving root with avbroot ?

If we run the stock ROM, will we be able to pass the play integrity check and use Google Wallet ?
[Google Pixel 6] Homeboy76:
Some versions of Play Integrity Fix are still working.

Also, @osm0sis post #3,359, page 177 in the Play Integrity Fix provide a work-a-around for passing Safetyet.

Yes, if you run the stock ROM you will be able to use Google Wallet.
[Google Pixel 6] bobby8921:
I saw @osm0sis post but I don't have the time to search for hours a ROM with a possible valid fingerprint.

You mean stock ROM with locked bootloader ?

Because Google Wallet is not working with stock ROM rooted and unlocked bootloader.

I haven't been able to find return of experience from Pixel 6 user with avbroot. Is it a solution or my device will still be flagged by Google Wallet?
[Google Pixel 6] miss:
not work
[Google Pixel 6] Homeboy76:
Yes!
[Google Pixel 6] Homeboy76:
Magisk Canary Update

app-release (1dcf3255) (26402)

Magisk (1dcf3255) (26402)

[Zygisk] Introduce new code injection mechanism

Diffs to v26.4

[Zygisk] Introduce new code injection mechanism

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 6] will734:
Is safe install twrp update thru magisk ?
[Google Pixel 6] Slim2none4u:
No
[Google Pixel 6] will734:
should i reset factory setting? I stocked in loop booting
[Google Pixel 6] Slim2none4u:
If you can get to fastboot, flash factory image
[Google Pixel 6] Homeboy76:
Magisk Canary Update

app-release (d7750b72) (26403)

Magisk (d7750b72) (26403)

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

Diffs to v26.4

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 6] iSupakilla:
Even with the SafetyNet fix that was posted 2 days ago im still failing the device integrity. Followed the guide step by step
[Google Pixel 6] Homeboy76:
How to create and use a custom.pif.json!
[Google Pixel 6] iSupakilla:
thank you! gonna look into this tomorrow
[Google Pixel 6] Homeboy76:
Magisk Canary Update

app-release (65207f96) (26404)

Magisk (65207f96) (26404)

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on devices with small boot partitions

[Reset Prop] Add new wait for property feature

resetprop -w

Diffs to v26.4

[Zygisk] Introduce new code injection mechanism

[Zygisk] Support new signature introduced in U QPR2

[SEPolicy] Update libsepol to properly set some policy config bits

[MagiskBoot] Support compressing init so Magisk is installable on

devices with small boot partitions

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 6] Riddle5:
Does anyone have the image from January?
[Google Pixel 6] Homeboy76:
There is a link to download it in the OP, ~ ~ ~ Part I - INFORMATION ~ ~ ~, 2. Prerequisites.
[Google Pixel 6] Riddle5:
I found it, it's here https://sonyroot.com/google/pixel6.html
[Google Pixel 6] Homeboy76:
That is not the link to Google's 'Official' firmware downloads.
[Google Pixel 6] Riddle5:
But there is the factory image
[Google Pixel 6] Homeboy76:
Please compare the

factory image

link you posted

(https://sonyroot.com/google/pixel6.html) to the 'Official' Google (Factory Images for Nexus and Pixel Devices) link.

"Inquiring minds want to know"

What benefits does the

factory images

in your link provide for your Google Pixel 6 phone model phone that the '

Official' Google Factory Images for Nexus and Pixel Devices link does not provide

?

XDA members can learn from your answer.
[Google Pixel 6] Riddle5:
Well, I had already downloaded the image. I wanted to root but still updated the January patch. I think I'll have to wait for them to release the factory image
[Google Pixel 6] Homeboy76:
So the link you posted (https://sonyroot.com/google/pixel6.html) provides patches and factory factory images for the Google Pixel 6 phone.

What do the patches do and why do you need their factory image to root your Google Pixel 6 phone?
[Google Pixel 6] Riddle5:
I need Boot participation to patch with magisk
[Google Pixel 6] Homeboy76:
boot participation ???

Do you mean

boot partition

?

You do not root your phone by patching the

boot partition

.

Did you read the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~..., 3. Manually Install/Update Factory Image

keep data

or

wipe data

:

It explaines how to install the Google factory image, extract the boot.img file from the factory image file, and patch the boot.img file with Magisk to root your Google Pixel 6 phone.
[Google Pixel 6] Riddle5:
I don't think I explained myself well, friend! Hahaha I'm currently completely Stock, and I wanted the factory image so I could have the Boot partition so I could patch it
[Google Pixel 6] Homeboy76:
First, I know your Pixel 6 phone is "completely stock".

Second, you do not patch the

boot partion

to root your phone, you patch the boot.img file and flash it to the boot partition to root your phone.

Third, this is what you have to do to root your Pixel 6 phone

Make sure you have the latest

working

version of SDK Platform-Tools r. 34.0.5 installed on your computer

Download the latest factory image (Jan 2024) to your phone.

Extract the Factory Image file (oriole-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.

Open the folder you extracted the Factory image to, the image...zip file is in this folder.

Extract the image-oriole-aa9a.999999.999.zip file to a folder. Open the folder you extracted the image-oriole-aa9a.999999.999.zip file to, the boot.img file is in this folder.

Patch the boot.img

Open Magisk

Tap Install (next to Magisk)

Tap Select and patch a file

Navigate to the boot.img file

Tap it then tap the check mark (✓)

Tap Lets go

When you see done the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.

Tap the disc icon (upper right corner) to save the log file.

Reboot

Copy/Move the magisk_patched_xxxxxx.img file to your computer's Platform-tools folder, the folder that has fastboot.exe in it:

Copy it to a USB drive and transfer it to your computer, or move it to your computer using adb push

Boot fastboot mode, on your phone

Connect the phone to the Computer with USB cord.

Open a Command Prompt in the Platform-tools folder.

Type fastboot flash boot "name of the magisk patched.img file)" without the quote marks at the Prompt and press enter.

Type fastboot reboot at the Prompt and press enter.

Done! :)