yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Riddle5:
Yes, in fact, I did understand that part, and I was also not clear about what it was about, but I return to the same thing. I used the factory image to have the boot.img and thus patch it, it is not yet on the official Google page, that is why I shared where I found the factory image. If I can use the boot.img file that comes there to patch it or not?.

And beforehand he apologized because my native language is not English and I can be somewhat confusing when trying to explain myself.
[Google Pixel 6] Homeboy76:
First, I don't know what country you are in or what your native language is, but the January 2024 factory image has been on the 'Official' Google web site since January 3, 2024.

14.0.0 (UQ1A.240105.002, Jan 2024)

If you are not seeing it change the language to English.

Second, If you follow the instructions in post # 748,

can you extract the boot.img from the factory image you downloaded and patch it?

No apology needed for you trying to explain in a language that is not your native tongue.
[Google Pixel 6] Rubister:
Thank you so much for this guide! I'm looking at getting a Pixel 6, and I'll be rooting for sure, but I've gotten rusty as I'm out of practice with involvement in the Android ecosystem for the past ...several years. A lot has changed in that time. I understand you can switch slots via fastboot, but I'm not sure what the advantage is to having one slot rooted and the other not rooted. Is there an advantage? If it's not needed for the update process (intended purpose, from the manufacturer's perspective?) - is it to be able to use apps that won't be fooled by the SafetyNet fixes and associated bypasses?
[Google Pixel 6] Homeboy76:
There is no advantage of having one slot rooted and one not rooted nor is there any advantage to having both slots rooted.

...is it to be able to use apps that won't be fooled by the SafetyNet fixes and associated bypasses?

No, it is not.

The real advantage is having both slots bootable:

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

5. Make Both Slots Bootable:

Manually

, Flash the OTA Image to Both Slots - One

bootable and rooted

, the other slot

bootable without root

.
[Google Pixel 6] Toronadian:
So I just helped a family member root a Pixel 8, and for that device the rooting process has become slightly different as Magisk patches the init_boot.img file. I just want to make sure for January 2024 that for the Pixel 6 we are still continuing to just patch the boot.img file if flashing the factory image to update? Thanks.
[Google Pixel 6] Homeboy76:
Use the flash-all.bat file to install the January 2024 factory image. Don't forget to edit the flash-all.bat file, remove the -w

to keep your data (see OP)

.

If you want to root your Pixel 6, patch and flash the boot.img.
[Google Pixel 6] vlucchetti:
Anybody know where Homeboy76 is?
[Google Pixel 6] devtherockstar:
I have reflashed my google pixel 6 using android flash tool to latest stock firmware and used options to lock the bootloader.

However I am still unable to use wallet to add my payment card. It was previously unlocked and running magisk.

I get the error ''This device can't be set up to pay contactless. Your device doesn't meet the security standards to make contactless payments. It may be rooted or running uncertified software. For more info visit Google Pay Help or contact your device manufacturer.''

Can anyone help to explain how to get this working again? Thanks.

Edit: Device state is still showing unlocked. in fastboot mode.
[Google Pixel 6] simplepinoi177:
You need to pass "MEETS_DEVICE_INTEGRITY" from any Play Integrity checker.

The most established and generally accepted way is using Play Integrity Fix, but it's gotten very complicated since the end of November.

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Google Pixel 6] RimWulf:
Just had the update (against my will) and lost root. Can I use the appropriate patched boot.img (no init_boot.img) and flashed to both drives?
[Google Pixel 6] Melomi:
Once I follow the guide and root the phone using Magisk, how do I install custom roms and keep my root after that?
[Google Pixel 6] gazdajezda:
Aren't custom roms come with root? It used to be that way, years ago when I used custom roms.
[Google Pixel 6] Melomi:
No custom ROMS don't come with root. You can root with Magisk and flash a custom ROM with a Custom recovery. No rooting is needed
[Google Pixel 6] gazdajezda:
Hmm. Then I forgot. When I use my first droid phone (ZTE SF) I remember that after install via Custom Recovery, CM (CyanogenMod) had option to select if you allow root access. But yes, phone was previously unlocked by other process, which I totally forgot. Also, at that time there was no Msgisk, but SuperSU and some other option. Also on Samsung Galaxy S2 and S4. After that I switch to Pixel's and never look back. Oh, good old times... :cowboy:
[Google Pixel 6] gazdajezda:
Hello! I don't know if that thread is still active, it seems abandoned, but will try here :)

I notice that GPay stoped working - it detects root. I use commonly used pif which is now obsolete. Is there some way around that or usage of it on rooted phone is now definitely a game over? Thanx.
[Google Pixel 6] SeMmyT:
Hey there!

I'm using FP Downloader APK alongside playcurl, but it seems that now the author made the module to automatically check integrity and fetch the fingerprint - so the APK is obsolete.

You can find the downloads and instructions here: https://github.com/daboynb/PlayIntegrityNEXT/tree/main
[Google Pixel 6] sronweb:
In addition please note that, to pass integrity, which is required for GPay, if you are using a custom rom, it should be signed (by the developer, it's part of cooking steps).
[Google Pixel 6] gazdajezda:
Great! Will try that, for sure! :) Unfortunatelly, tommorow.

I use official P6 Google rom, so thank you for your notice. (y)

Thank you both!
[Google Pixel 6] gazdajezda:
It works 😄 On my P6 and girl's P2 XL. I installed PlayIntegrityFix_v15.9.9.zip and playcurl.zip, reboot and now I again have 2 green passes out of 3. Thanx!
[Google Pixel 6] gazdajezda:
It works, but still, on my phone Wallet say that Phone does not meet security requirements. Other phone of my girl is perfectly ok. Mine have A14 and her A11. I clear Wallet and Play data & cache, reboot phone but no difference. Went to the store and I was able to pay with phone. Eh, Google...

P.S. - I manage to get my phone to meet security requirements. Add Google services to hide root list and again clear caches. After reboot now is ok.
[Google Pixel 6] Nimueh:
Yea I don't like that flasher, I prefer the manual way - and if you'd ever had a bootloop due to the system having updated while you were using a substratum overlay you'd know why I disable all modules, just in case :LOL:
[Google Pixel 6] Homeboy76:
Maybe, the reason some members choose to flash the factory image is you have to download the latest factory image to get the latest boot.img.

So they just flash it instead of downloading the factory image and the OTA image.
[Google Pixel 6] Lughnasadh:
Since my Nexus days I've always just removed the -w from the flash-all.bat file and flash-all'd away, always disabling any mods that modify the SystemUI, Android framework, etc. first. Many mods often need updating to that specific monthly update or you'll get thrown into a bootloop, as Nimueh said.

I then patch the boot image and flash it.

But really, the "best" way to update is whatever way the person feels most comfortable with. Many trails to get to the same destination.
[Google Pixel 6] t-ryder:
Well, I love my flasher and who needs substratum anyway? lol.
[Google Pixel 6] bobbarker2:
OT but..

Migrate requires TWRP. Which isn't available. There's a Migrate Flasher “Alternative to TWRP flashing for Migrate apps" that's in early access and was last updated in 2020.

Titanium doesn't work on 12 or if it does it's dicey at best. Tried using it, it freezes or restores corrupt apps. There's plenty of store reviews that say the same. And it hasn't been updated since 2019.. so yeah..
[Google Pixel 6] gazdajezda:
Agree, Tibu not working ok on 12, Swift is better. Yesterday i update and root my PIX6 and today i get a message that system update is available and is downloading... Will that cancel root and brick my phone? I set system updating to off in developer settings, why it does that anyway?
[Google Pixel 6] DNAblue2112:
It won't brick the phone. If the OTA update works it will simply remove root and update. You can then reapply root after the update. I believe you can also use magisks a/b updating thing for applying it to the OTA update before rebooting. But it shouldn't be able to brick your device unless something goes horrifically wrong
[Google Pixel 6] Nimueh:
Flashing through Migrate Flasher works fine though, no matter when it was updated. It restores everything just fine, so who cares about updates since it does what it's supposed to :cool:
[Google Pixel 6] gazdajezda:
Ah, so then it will install update after it download it? Asking this because i lived happily for a month with rooted phone (36) until 4 days ago after reboot it booted to some strange mode where only have 3 options (relock, shutdown, reboot i think it was) were available. So i flash an november update (37) and root it & disable system updates. So here are we again 😀 I'm perfectly fine with current version and don't wannt such forced updates of my phone. Eh google... custom rom will be solution?
[Google Pixel 6] BrianRC:
Help @Homeboy76 !! I am stuck in bootloop.

After unlocking bootloader, I must have made a mistake in step "Install/Update Factory Image

keep data

or

wipe data"

OS would not start so I selected factory reset. Now I am stuck in bootloop. Any help would be much appreciated.
[Google Pixel 6] Homeboy76:
Just keep Pressing the volume down button during boot animation.

It should boot into safe mode.

When it finishes booting into safe mode reboot.
[Google Pixel 6] BrianRC:
Thanks @Homeboy76 . Holding volume down button gets me to Fastboot Mode. From there I can get to Recovery Mode. In Recovery Mode I can select Wipe data/factory reset and see the following:

-- Wiping data --

E: Open failed: /metadata/ota: No such file or directory

Formatting /data...

Formatting /metadata...

Wiping Titan M...

Wiping keys...

E:gto_esehal SecureElement:t1_recv_window_append free = 261

E:gto_esehal SecureElement:t1_recv_window_append free = 261

E:gto_esehal SecureElement:t1_recv_window_append free = 261

E:gto_esehal SecureElement:t1_recv_window_append free = 261

Data wipe complete

Then reboot but problem remains. I get the "bootloader is unlocked" error message for a moment followed by the initial Google splash screen, then black, then back to "bootloader is unlocked" error message.
[Google Pixel 6] Homeboy76:
Why are you going to recovery to reset your phone?

Are you trying to install Custom ROM?

If yes, read the instructions in the Custom ROM thread you are trying to install.

If you are not trying to install a Custom ROM:

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

Read the instruction in the OP, ~ ~ ~ Instructions ~ ~ ~, Install/Update Factory Image keep data or wipe data,

• Flash Factory Image Wipe Data

.

Note: Make sure the flash-all.bat file has this line: fastboot -w update image-oriole-aa9a.999999.999.zip

Then do OP, ~ ~ ~ Instructions ~ ~ ~, Install/Update Factory Image keep data or wipe data,

• Flash Factory Image Wipe Data

.
[Google Pixel 6] BrianRC:
OMG @Homeboy76, you fixed it! Editing back in the -w and running Flash-All in the bootloader worked. Thank you!

This is where I got hung up with your instructions in the first place.

Under Flash factory image Keep Data, after editing out -w and running “Flash-All” at the command prompt, it returned <waiting for any device> and nothing happened. I did some research on that and tried swapping cables and updating USB drivers to no avail.

Now this time you had me run the batch file while logged in to the bootloader. Should have I run the batch file in bootloader while trying to Keep Data? Previously I was trying to run inside the OS.

Cheers,

Brian
[Google Pixel 6] Homeboy76:
Yes.

Take a look at the, modified, instructions. :)
[Google Pixel 6] BrianRC:
Awesome. That is much more clear. I will give it another try tomorrow.
[Google Pixel 6] BrianRC:
Hello @Homeboy76,

Things are not going well.

Under instructions for "Patching the boot.img - to root/reroot" steps 16 and 17 I see the following:

C:\platform-tools>fastboot flash boot magisk_patched-24101_aK2f8.img

Sending 'boot_a' (65536 KB) OKAY [ 1.823s]

Writing 'boot_a' OKAY [ 0.100s]

Finished. Total time: 1.949s

C:\platform-tools>fastboot reboot

Rebooting OKAY [ 0.000s]

Finished. Total time: 0.003s

Then the phone boot loops, so I tried "Flash the 'stock' boot.img to both slots:"

C:\platform-tools>fastboot flash boot boot.img --slot all

Sending 'boot_a' (65536 KB) OKAY [ 1.832s]

Writing 'boot_a' OKAY [ 0.101s]

Sending 'boot_b' (65536 KB) OKAY [ 1.831s]

Writing 'boot_b' OKAY [ 0.100s]

Finished. Total time: 3.906s

When I reboot, I get an error message "Your device is corrupt. It can't be trusted and may not work properly."

Press power button to continue.

When I continue booting the phone, it gets permanently stuck on the initial Google logo.

I really appreciate your help with this.
[Google Pixel 6] Homeboy76:
Did you do wipe data before flashing the magisk_patched.img?

- Boot Safe mode then reboot:

- re-patch the boot.img with Magisk- canary_24001

- flash repatched boot.img

fastboot flash boot magisk_patched..
Img
[Google Pixel 6] BrianRC:
When you say, did I wipe data, last night i did "

Flash Factory Image Wipe Data"

as you directed. Then I set up phone again so I could use it. Then I followed instructions this morning under

Patching the boot.img

- to root/reroot.

And your instructions for booting in to safe mode... Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok. Are not working for me.

Your saying now I should wipe data again before flashing magisk_patched.img? Isn't that the same as "

Flash Factory Image Wipe Data"

?
[Google Pixel 6] Homeboy76:
No, just confirming you Wiped data.
[Google Pixel 6] BrianRC:
Does it matter that I ran the January Security update before

Patching the boot.img

- to root/reroot ?
[Google Pixel 6] Homeboy76:
No.

The boot.img you patch should come from that Factory Image.
[Google Pixel 6] BrianRC:
Actually, the most recent Factory image from the developers site is for October... 12.0.0 (SD1A.210817.015.A4, Oct 2021). Maybe that is the problem I am having.
[Google Pixel 6] Lughnasadh:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 6] BrianRC:
Thanks @Lughnasadh. I see now most recent version is at the bottom of the stack.
[Google Pixel 6] BrianRC:
Yep. That was definitely it. I am all rooted up now. Google Pay and everything working. Thanks for the help guys. And thanks for the great instructions @Homeboy76!
[Google Pixel 6] Homeboy76:
I have modified the OP to make it easier to use. It has been divided into three parts:

Information

,

Instructions

, and

Other

.

Tip: Read the, entire,

Information Part

first, then the

Instructions

for the operation you want to preform i.e., Install Factory image: Read Install/Update Factory Image

keep data

or

wipe data

, etc.
[Google Pixel 6] Nimueh:
Why do the instructions still say "Install Magisk Canary 23016"? I thought the new Stable 24.1 has all the changes that were made for our device in the Canary branch? :unsure:
[Google Pixel 6] Homeboy76:
o_O:mad:

<Edit>I removed the Magisk Canary link from the OP, Part II - Instructions, 2. Install/Update Factory Image keep data or wipe data, •

Important Note(s)

:

Why?

It is not needed in that set of instructions. The Magisk links are in the OP, Part - II Instructions, 4. Root/Reroot with Magisk and Pass SafetyNet, •

Patching the boot.img - to root/reroot.

, 2.
[Google Pixel 6] Nimueh:
What lol? I've updated Magisk (like most others in the P6 Telegram groups as well) and no issues so far 🤷‍♀️
[Google Pixel 6] Homeboy76:
My response (o_O confused :mad: embarrassed) was my way of saying I

corrected the error (removed 23016)

. :ROFLMAO:
[Google Pixel 6] Nimueh:
LOL ok, that didn't come across properly then, my bad ... and thx for fixing it :)
[Google Pixel 6] Homeboy76:
I removed the Magisk Canary link from the OP, Part II - Instructions, 2. Install/Update Factory Image keep data or wipe data, •

Important Note(s)

:

Why?

It is not needed in that set of instructions. The Magisk links are in the OP, Part - II Instructions, 4. Root/Reroot with Magisk and Pass SafetyNet, •

Patching the boot.img - to root/reroot.

, 2.

Thanks for bringing it to my attention. :)
[Google Pixel 6] BrianRC:
Question: Can I accept the Security and/or Google Play system updates in Settings or is the process different with the phone rooted?
[Google Pixel 6] Nimueh:
Play System Update sure, but what Security Update? That just informs you which one you have, you can't download/change that though.
[Google Pixel 6] Homeboy76:
What @Nimueh said with s little more information.

Android Security Update in

Settings => About phone => Android version 12

shows you the date of your last Security update and if you tap it it takes you to the Security Bulletins.

Google Play system update in

Settings => About phone => Android version 12

shows you the date of your last Google Play system update and if you tap it gets the latest Google Play system update. You have to reboot to install it.

I guess Google decided to stop pushing the Google Play app to our phones. I wonder what cause them to stop pushing it to our phones.
[Google Pixel 6] Wired Life:
Has anyone run an OTA and patched boot with new Magisk 24.1 "install into inactive slot (after OTA)"?

Does this work?
[Google Pixel 6] Homeboy76:
I, too, haven't tried the instructions:

Install to Inactive Slot (After OTA)

therefore I, too, do not know if they work and am unwilling to try them to confirm they work.

Why?

I'm not sure that @topjohnwu or @Didgeridoohan have reviewed these instructions and validated or updated them for Magick Beta/Stable 24.1 or Magick Canary 24001
[Google Pixel 6] Lughnasadh:
The instructions here should still work. Disregard the NOTE at the top as this option has been re-implemented. https://topjohnwu.github.io/Magisk/ota.html

John re-implemented the option after another person fixed it. The person that fixed it tested it on the Pixel 5a and 6 with success. It should work but we'll need confirmation from users when the February update comes out.

Here's some more behind-the-scenes info on it. These changes have been implemented in Canary 24101 and Stable 24.1 (If you look at the changelogs and John's Github master commits you'll see these commits have been implemented)

"Restore the ability to install Magisk on the other slot on some A/B devices"

https://topjohnwu.github.io/Magisk/changes.html

https://github.com/topjohnwu/Magisk/commits/master

Build `bootctl` and enable installation to inactive slot on Pixel devices by capntrips · Pull Request #5134 · topjohnwu/Magisk

This adds the necessary sources from AOSP and builds the bootctl binary along with Magisk. I'm submitting this as a draft, as I imagine it would make more sense to move the individual libraries int...

github.com

Enable installation to inactive slot on Pixel devices by capntrips · Pull Request #5204 · topjohnwu/Magisk

9c93fe6 updated the bootctl binary, which was the only thing preventing installation to the inactive slot from working on Pixel devices. This removes the check that hides the button on those device...

github.com

Update bootctl · topjohnwu/Magisk@9c93fe6

Close #5134

github.com

disable virtualAB check for noSecondSlot · topjohnwu/Magisk@053f4d4

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 6] Homeboy76:
Thanks for the update! :)
[Google Pixel 6] Homeboy76:
UPDATE!

Magisk Canary 24102
[Google Pixel 6] Homeboy76:
UPDATE!

New: Moved Magisk Alpha
[Google Pixel 6] badabing2003:
@Homeboy76

Some feedback if you don't mind.

Nice redesign, but quite confusing when it comes to magisk.

In the updates,

Magisk Alpha is the only one with a link and it is actually a telegram link, impossible to make any sense of it

and you can't visit any of the links unless you have a telegram account (for the record I don't).

For an amazing guide that this is, If I'm jumping around, I can imagine what would a noob feel like.

Alpha version stated in the update section is 24002 which to me alpha would be usually newer than canary and riskier, but Canary is already at 24.1

Few posts above you stated Canary version to be 24002, but Canary actually is at 24102, a typo perhaps or did it change too fast on you?

The link to the differences between magisk versions is outdated, ie that post is from December and not current, it states that release does not support zygote, but the latest stable release does.

I know Magisk changes rapidly and it makes guides outdated unless you're constantly updating them.

Which is a lot of maintenance and hard to keep up.

Even though at this point I suspect all 3 versions are at the same version

I'm sticking with Canary 24102, I just thought I'd share my experience.

Thanks

BB
[Google Pixel 6] Homeboy76:
I don't mind feedback. In fact I appreciate it.

Reference Magisk Alpha: I put that link to Magisk Alpha because it is the only place that list the Magisk Alpha updates for XDA Members that use Magisk Alpha. You can visit the link without the Telegram app. You do have to have the Telegram app installed to download the files. If a github link to download it becomes availible I will post that link

Magisk Alpha is usually forked from Magisk Canary. So the version is the same as Magisk Canary.

You are correct the Magisk Canary app was listed as 24002 that was a typo and I have corrected it.

The link to the differences between Magisk versions has been removed.

I appreciate you sharing your thoughts. :)
[Google Pixel 6] capntrips:
It might be worth noting that while the Alpha builds are maintained by one of Magisk's top contributors, it is not an official version of Magisk.

Unless things have changed in the last few months, the biggest feature of Alpha was that it continued to support MagiskHide.
[Google Pixel 6] Homeboy76:
Things have changed!
[Google Pixel 6] capntrips:
Alpha no longer supports MagiskHide? or it has other big features?
[Google Pixel 6] Homeboy76:
I think Magisk Alpha is forked from Magisk Canary. Magisk Canary 24101 dropped Magisk Hide for Zygisk.

<Edit>

Magisk Alpha has both Magisk Hide and Zygisk (Beta). I only use Zygisk.
[Google Pixel 6] capntrips:
I installed the latest Alpha to confirm:

If you turn off Zygisk, you're given the option to enable MagiskHide.
[Google Pixel 6] Homeboy76:
You're fast! I was editing my post while you were replying. :ROFLMAO::ROFLMAO::ROFLMAO:

Thanks for keeping me on track. :)
[Google Pixel 6] Shuyin10:
Sry guys but,What do I need to do to do the February OTA? I have root with magisk and several modules activated Thanks in advance!
[Google Pixel 6] V0latyle:
Open Magisk, tap Uninstall, tap Restore Images

Start the OTA download; when prompted to reboot DO NOT REBOOT

Open Magisk again, tap Install at the top, tap Install to Inactive Slot

Magisk will reboot your device into the updated slot, you should have root.
[Google Pixel 6] Shuyin10:
I have restore images with magisk but when i launch ota, i have an error 'install problem" :/

edit : Ok, i'm dumb...have tap Uninstall, but only restore image....not uninstall magisk...

Have reboot and now bootloop :D

I'm good at reflashing the rom :D
[Google Pixel 6] capntrips:
You can filter your logcat for update_engine to see why it fails. Fortunately, if it fails, it does it in the first few minutes.