yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Homeboy76:
0. When an OTA is available...

Several members are skipping this step.
[Google Pixel 6] V0latyle:
Very true! The stock image should ONLY be restored immediately before taking the OTA. Otherwise, you'll lose root if you reboot.
[Google Pixel 6] badabing2003:
I have a question about an approach which I'm pretty sure it would work, but wanted to check if anyone has tried it.

When a new image is available.

- Extract the boot.img,

- Transfer it to the phone and patch it with magisk (a question about this step further below)

- take it back to the pc and replace the boot.img with the patched one (in the zip file)

- do the required flash_all

This should theoretically boot us into a rooted updated version.

Would that work?

Q: Magisk to be able to patch the boot.img, does it need to be running the OS version that matches the boot.img it is patching,

I suspect the answer is NO, but wanted to check.
[Google Pixel 6] dknova:
Hey All,

I've installed the OTA Feb update without removing the restore image so I'm getting the error:

Any ideas how I can patch the boot.img file after you've an OTA when I haven't removed the restore image?
[Google Pixel 6] Homeboy76:
A: Yes
[Google Pixel 6] Homeboy76:
Download the Feburary Factory Image

Go to the OP, Part II - INSTRUCTION, 4. Extract Files from Factory Image/Flash boot.img, •

Extract Files from Factory Image

and extract the boot.img

Flash the boot.img to both slots fastboot flash boot --slot all boot.img: OP, Part II - INSTRUCTION, 4. Extract Files from Factory Image/Flash boot.img, •

Flash boot.img

Then Go to the OP, Part II - INSTRUCTIONS, 5. Root/Reroot with Magisk and Pass SafetyNet, •

Patching the boot.img - to root/reroot

, and patch the boot.img and flash it.
[Google Pixel 6] Wired Life:
Is this 100% safe?

What did Shuyin10 wrong?

He clicked full remove instead of restore image?
[Google Pixel 6] V0latyle:
As with anything on this site, everything is at your own risk. If you need 100% safe, don't root your device.
[Google Pixel 6] BrianRC:
I inadvertently pressed "check for updates" under Security Update in my settings. Now the phone says Installation paused, "Installation will continue when device isn't being used. To install now, tap Resume." How can I stop this OTA update so I can install it properly? I do have Automatic system updates turned off under System Settings, but the phone seems like it is going to install the OTA updated when it feels like it anyway.

Thanks for the help.
[Google Pixel 6] BrianRC:
OK. Disregard above. I went ahead and proceeded with @V0latyle 4 step instructions. OTA is installing now. We'll see.
[Google Pixel 6] Homeboy76:
True, most thread makers have a

disclaimer statment on their sites absolving them of responsibility

should a member brick their phone, or damage their equipment following their instructions.
[Google Pixel 6] BrianRC:
I believe I followed the steps above correctly and retained root with Magisk. However, it appeared that the Security update didn't take. In settings, Security update sill showed Update form January 5, 2022. And when I selected that, it said "Security update available" and at the bottom, "Restart now." So I tried step 3 a second time and now I'm screwed. Phone boots up into Android Recovery. "Cannot load Android system. Your data may be corrupt. If you contintue to get this message you may need to perform a factory data reset and rease all user data stored on this device."

Any help would be much appreciated..
[Google Pixel 6] mac796:
Did your update go through mine stopped with errors. Had to use the flash tool. That never lets me down.
[Google Pixel 6] BrianRC:
What flash tool? I had no errors initially.
[Google Pixel 6] BrianRC:
A little more detail on my perdicament. Phone says:

Android Recovery

google/oriole/oriole

12/SQID.220205.003/8069835

user/release-keys

Use volume up/dowm and power.

Cannot load Android system. Your data may be corrupt. If you contintue to get this message you may need to perform a factory data reset and erase all user data stored on this device.
[Google Pixel 6] BrianRC:
Disregard above. I went back to Install/Update Factory Image

wipe data

and will start from scratch.
[Google Pixel 6] V0latyle:
In my experience, sideloading the OTA seemed to fix the corrupted data issue.
[Google Pixel 6] BrianRC:
Thanks @V0latyle. When you say sideload, is that following the instructions of @Homeboy76 on the first page of this thread? My phone is working properly now with the February update except that when booting, before the unlocked bootlaoder warning, I get an error messate that says "Your device is corrupt. It can't be trusted and may not work properly." And I have to press the power button to contiune. I'd like to correct that. Can I reacomplish the steps after "unlock bootloader" and choose Install/Update Factory Image

keep data

and still get rid of the corrupt error message? Thanks.
[Google Pixel 6] V0latyle:
Yes, part II, item 10. However, the instructions at the link are slightly confusing, so you can just do this:

With Android running and USB debugging enabled, connect device to PC running Platform Tools.

Using a command window in Platform Tools, reboot device:

adb reboot sideload

Device will reboot into sideload mode. Begin sideload:

adb sideload <OTA zip>

When update completes, device will be in fastboot. Reboot to system. Allow the system to boot uninterrupted - do not attempt to flash or boot anything in bootloader.

After device boots and all update operations have completed, you may reboot to bootloader and flash a patched image.
[Google Pixel 6] Homeboy76:
:oops: So, you're saying the Instructions Google provides Full OTA Images for Nexus and Pixel Devices:

Updating instructions

are confusing? 😂😂😂
[Google Pixel 6] V0latyle:
Only because they're rather verbose. Check out their page on unlocking the bootloader. I like to boil things down to the simple stuff. No need to reboot to recovery and use the key combo when you can reboot to sideload mode directly.
[Google Pixel 6] Homeboy76:
Amen! I agree with your assessment of the instructions.
[Google Pixel 6] t-ryder:
But one should not forget about the -w flag in flash_all or one would get a full wipe
[Google Pixel 6] Homeboy76:
Curious

How does

not forgetting the -w flag

apply to the question and my answer?

Q: Magisk to be able to patch the boot.img,

does it need to be running the OS version that matches the boot.img it is patching,

https://xdaforums.com/t/guide-root-pixel-6-android-12-with-magisk.4388733/post-86394355
[Google Pixel 6] t-ryder:
Just saying that if someone wants to update their device by flashing using the flash_all.bat from the factory image with a replaced boot image which was patched by Magisk one should not forget that

fastboot -w update image.zip

wipes userdata from the device. So users who are rather new to flashing don't lose their data by doing so. They would need to replace the boot image and edit the bat file removing the -w ... 😋
[Google Pixel 6] Homeboy76:
Ok!

Are you saying replace the boot.img with the magisk_patched...img in the SDK Platforms-tools folder before you do fastboot update image.zip to flash the factory image and

keep data

?

If yes, does that root your phone during the update process?
[Google Pixel 6] badabing2003:
Just to be super clear, @Homeboy76 was responding to this post which I asked.

More specifically this question

> Q: Magisk to be able to patch the boot.img, does it need to be running the OS version that matches the boot.img it is patching,

His answer being Yes, makes the first part of my post totally moot, that process should not be attempted because the whole point of that process was to save multiple steps and reboots without losing root and hence not having to go through the dance of clearing Google services and others to pass Saftey Net.

But it cannot be done, because the phone is not running the latest OS when patching, hence the patched boot.img even if it is from the latest OS will not be good.

Lastly your concern about not forgetting tor remove -w is valid, but my last step intentionally had this

- do the required flash_all

By required I meant, whatever applies to your situation and not blindly run flash_all.

Thanks for your concern, it's good to be explicit, you should have quoted me with that concern, as it did not apply to @Homeboy76 correct response.

Hope this clarifies the situation.
[Google Pixel 6] t-ryder:
I get confused more and more reading this thread.

This is my update routine like I did it since November '21:

I am on build ABC and build XYZ (factory image) gets released - I am still running ABC, open latest Magisk app, and patch the extracted boot image of XYZ

I don't deactivate any modules (I don't use Substratum, I only got SafetyNet Fix Zygisk)

I prepare my flasher by copying the needed stuff (as written at Github), enable ADB and update (my flasher basically does what flash_all.bat without -w flag does and it's less complicated as it would be zipping that stuff again) - And I'm done

I don't have to clear anything, don't reboot manually, do anything ...

Maybe I just don't understand what's going on or it's because English is not my native language. If that's the case, sorry.
[Google Pixel 6] Homeboy76:
This response is keyed to @t-ryder post:

1. Good (y)

2. Since you only have one module: SafetyNet Fix Zygisk) you're ok because that module was created for Magisk. :)

3. When you write "I prepare my flasher...":

What is your flasher?

Also, Can you post the link to "(as written at

Github

)" you are using?
[Google Pixel 6] t-ryder:
There's a link already.
[Google Pixel 6] Homeboy76:
Ok, your script provides another option (Script, Manually flashing, Google's flash tool) for flashing the factory image. (y)
[Google Pixel 6] badabing2003:
@t-ryder

I just did a test, I had a copy of previously patched January boot.img (le's call it patched_boot.img) as well as unpatched January boot.img

I patched boot.img with the current magisk on current Android OS (ie Feb release)

Then did a binary diff of the new patched against the old patched

They did not match at all, in fact there are a lot of differences.

This is not conclusive test mainly because in between the magisk version has changed as well which could explain the differences, however it is also possible that depending on the OS version magisk is running on, the patched output could be different. (this can be confirmed by using the same version of magisk on two different OS versions)

Lastly, considering how often Magisk gets updated and Google seems to be breaking magisk (cat and mouse game) using an older version of magisk to patch new boot.img could be invitation for trouble, at best it would go flawless, at worse boot loop or dare I suggest even bricking? (I doubt).
[Google Pixel 6] t-ryder:
I just did a test too.

I took the unpatched boot.img from SQ1D.220205.003 - Feb 2022:

I patched the boot.img running Magisk 24102 on SQ1D.220105.007 - Jan 2022

I patched the boot.img running Magisk 24102 on SQ1D.220205.003 - Feb 2022

After that I compared the files with Beyond Compare. They are binary same.
[Google Pixel 6] badabing2003:
Good test, thanks for confirming that they are identical.
[Google Pixel 6] badabing2003:
I put together a Powershell script that automates the end-to-end process and facilitates flashing a new factory image on a previously rooted phone while maintaining root / safetynet pass.

The steps are derived from this excellent thread shared by @Homeboy76

Pre-patching of the factory image prior to flashing is performed to speed up the process and maintain root, which avoids later steps of clearing storage for Google Services and alike to pass safetynet.

If anyone is interested, you can check the script here

GitHub - badabing2005/PixelFlasher: Pixel™ phone flashing GUI utility with features.

Pixel™ phone flashing GUI utility with features. Contribute to badabing2005/PixelFlasher development by creating an account on GitHub.

github.com

I strongly encourage you to scrutinize the script, usual disclaimers apply, this is intended for people who know what they are doing, and want to speed up the process.

Beginners, please understand the steps in post #1, perform each step manually so that you get an understanding of what is happening and hopefully why it is happening, blindly running someone's script is risky business.

The script automates the following steps:

- Checks for the factory image

- Unpacks factory image

- Checks for dependencies (adb, fastboot, 7zip, ...)

- Unzips the factory image

- Extracts unpatched boot.img

- Deletes flash-all.sh and flash-base.sh (just for extra precaution)

- Patches flash-all.bat and removes the wipe option

- Checks and validates phone connection

- Checks and validates that the phone model matches the factory image

- Transfers stock boot.img to the phone

- Launches Magisk

- Waits for the user to complete the patch on the phone

(TODO: automate the previous step to magisk patch programmatically)

- Transfers patched boot.img to the PC

- Replaces stock boot.img with patched boot.img

- Repackages the image zip with patched boot.img

- Reboots to bootloader and pauses

- Launches flash_all.bat to update the phone

This script should theoretically work for any Pixel phone by passing the phoneModel parameter, however I have only tested it on Pixel 6 (oriole) which is set as the default.

If you encounter any issues, I advise you to create a github issue, I don't mind answering here but I don't want to hijack this excellent thread, I just wanted to share my work in case someone finds it useful.
[Google Pixel 6] t-ryder:
Pretty cool. This takes things even a big step further than my 0riole flasher. You really should create an own thread for this. See ya at Github.
[Google Pixel 6] badabing2003:
Thanks @t-ryder I'll consider it if it gets any interest / traction, I just wanted to give little back to the community that has given me a lot.
[Google Pixel 6] Homeboy76:
First, thanks to you @t-ryder for confirming the January and February in boot.img are the same.

Does this mean Google doesn't/won't change the boot.img or they didn't change the January boot.img?

@badabing2005 script provides an improved version of @t-ryder script and another option (Script, Manually flashing, Google's flash tool) for flashing the factory image. (y)
[Google Pixel 6] badabing2003:
@Homeboy76

My understanding is different and @t-ryder can confirm.

Boot.img is indeed different between different factory images.

The test proves that you do not need to be running the OS version that matches the boot.img version you are trying to patch

Basically you can patch next month's boot.img with the latest magisk on the current OS version and the outcome of the patched boot.img would be the same (so no need to update the OS first and lose root), that is why we're able to patch the image first, repackage it in the factory image and flash.
[Google Pixel 6] Homeboy76:
Since the, boot.img, are different my original point was valid: The boot.img you patch must come from the Factory image you are rooting. My point was not what "OS version" you are on when you patch it nor what version of Magisk you patch it with. Albeit, the Magisk version should be 24-1 Beta/Stable or 23016 Canary or greater to avoid having to disable verity, etc.
[Google Pixel 6] badabing2003:
I think things got lost in the translation, but we're all good and in sync now.

Looking at my original question posted here

> Q: Magisk to be able to patch the boot.img, does it need to be running the OS version that matches the boot.img it is patching?

Perhaps I could have worded it differently to be clearer, yeah, absolutely, the boot.img should come from the factory image we want to upgrade to or have already upgraded to.

My question was more centered around, does magisk need to be running on the same version of OS that it is trying to patch.

Thanks
[Google Pixel 6] t-ryder:
@Homeboy76

stock Jan. '22 and Feb. '22 boot.img are not binary same - Google made kernel changes

We know now, that Magisk will patch any compatible boot.img to make root work no matter on what build the Magisk app runs (this makes "flashers" like @badabing2003 or mine possible)

badabing2003's flasher is not just an improved version of my flasher or script; I used batch/cmd, badabing2003 used a PowerShell script which is much more sophisticated (PowerShell is way more "mighty" than just batch)

Indeed one would need at least Magisk canary 23016 to patch a boot.img for the use with our flashers, or one would get a full wipe because of the missing necessary fixes

Thanks to all you guys
[Google Pixel 6] Homeboy76:
"badabing2003's flasher is not just an improved version of my flasher or script; I used batch/cmd, badabing2003 used a PowerShell script which is much more sophisticated (PowerShell is way more "mighty" than just batch)"

Got it! :cool:
[Google Pixel 6] Homeboy76:
"My question was more centered around, does magisk need to be running on the same version of OS that it is trying to patch."

Part of the misunderstanding is on me. I misunderstood your question. :(

Thanks for explaining it to me.
[Google Pixel 6] mcj108:
Has anyone tried this on the 12L beta yet?
[Google Pixel 6] Homeboy76:
New Factory/OTA Images

"004"

OP, ~ ~ ~ Part I - INSTRUCTIONS ~ ~ ~, Prerequisites.
[Google Pixel 6] Homeboy76:
Update

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

Magisk Canary 24201
[Google Pixel 6] Homeboy76:
Update

Magick Releases - 24.2 (Beta)
[Google Pixel 6] Homeboy76:
Update

Notice

Check Updates,

periodlly

, for the latest update information.
[Google Pixel 6] aterox:
Does this block use of the built-in security key? It no longer works on my device after following this guide and I've had no luck searching for any information about it.
[Google Pixel 6] aterox:
I guess the correct thing to say would be that it errors out.

When used to log into a Google account, the original confirmation prompt shows up, but it never asks for the fingerprint and fails with a toast saying "An error occurred."

When used for WebAuthn on any other site the prompt never appears.

This occurs when attempting on a different PC as a bluetooth security key and on the device itself.

I followed everything needed for Step 5. From unlocking the bootloader to passing SafetyNet.

My device passes the Play Store certification and everything else works as it should such as Google Pay and banking apps.

Thanks for your help!
[Google Pixel 6] Homeboy76:
@aterox

So, you followed the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 1, Unlock Bootloader/Return Phone to Stock/Lock Bootloader and 5. Root/Reroot with Magisk and Pass SafetyNet.

Ok!

The problems you are having with you finger print reader is a different issue that is not covered by this guide:

This may help: Fingerprint: Excellent recognition - that's how I got it working finally
[Google Pixel 6] aterox:
Sorry, I should have worded that better. The fingerprint reader works fine.

When you use the security key built into the phone, it asks for your pin/pattern/fingerprint to approve usage of the security key. This prompt is what doesn't appear, leading to the error toast.
[Google Pixel 6] Homeboy76:
This may help: Use your phone's built-in security key
[Google Pixel 6] aterox:
I've followed that and had it working before I rooted my phone a few days ago.

I haven't found any mention by anyone else for it not working after rooting which is why I was asking here.
[Google Pixel 6] Homeboy76:
Was it setup before or after you unlocked the bootloader? Rooting your phone shouldn't affect your verification setup.
[Google Pixel 6] aterox:
I've had it setup and working before unlocking the bootloader. After unlocking and rooting, I went back through and deleted the key from my Google account and refollowed the Google guide you previously linked.

It has no issue adding it to the account, but once I actually try to use it then it fails.
[Google Pixel 6] Homeboy76:
This may help: Get verification codes with Google Authenticator
[Google Pixel 6] aterox:
This is an issue with the security key built into the device, not with other forms of 2FA. They key worked with any website using WebAuthn before I rooted, but no longer does so afterward.
[Google Pixel 6] Homeboy76:
Ok! Try Google search or XDA Pixel 6 forum.
[Google Pixel 6] aterox:
I didn't have much luck with those. Thanks for your help
[Google Pixel 6] t-ryder:
For those in here who haven't read this yet: @badabing2003 released his updated PixelFlasher... check it out LINK
[Google Pixel 6] Homeboy76:
Update(s)

Magisk Canary 24303

SDK Platform-tools r33.0.1

If You use a

Custom Kernel

please read the

OP, Update(s), Custom Kernel, Note
[Google Pixel 6] Lughnasadh:
Not sure if you noticed, but some custom kernels (if not all) are having problems with Canary 24303. Those that haven't likely need to be updated to be able to boot. Check out the 6 Pro Kiri thread.
[Samsung Galaxy S21 Ultra] Ivymike52:
I'm trying any fix without solution.

If i install an older version 6.18 etc... it's works partially but it works.

Newest version start, i put my account, and after it showing an error.

I'm using Zygisk and selected shealth.

In older phone i set "tima" on 0 inside build.prop but now i can't see this option.

How can resolve?
[Samsung Galaxy S21 Ultra] DaReDeViL:
No other solution except staying on older version. Samsung is making rooted phones more and more unusable. I had to sell my rooted S21 and buy an unrooted S21+ to have a "fully" usable phone and gw4 ...
[Samsung Galaxy S21 Ultra] :
so what's the point of rooting then ?
[Samsung Galaxy S21 Ultra] DaReDeViL:
That's what I said, there's no point of rooting samsung phones anymore, now that they block services due to root, while it was supposed to enhance the experience
[Samsung Galaxy S21 Ultra] whatsisnametake2:
what else does rooting screw up on samsung phones? does fingerprint unlock still work? samsung pass?
[Sony Xperia 1 III] decomposed:
Hi.

Can someone please make some camera comparisons between Android 11 and 12? I mean to take the same outdoor pictures using same settings and compare it?

I wonder whether we received planned product aging (camera quality degradation via software "update").

Interesting if it is same, worse or better.

Also, is there finally night mode included?
[Sony Xperia 1 III] Hudrator:
Would also be nice to see, if the apps themself had a update.

@decomposed

What kind of "Night mode" are you talking about?

Basic-Mode as well as Automatik-Mode include automatic scene recognition. Part of it a dedicated profiles for:

Night portrait

Night scene

Low light

Xperia 1 III XQ-BC52/XQ-BC62/XQ-BC72 | Help Guide | Scene and condition recognition
[Sony Xperia 1 III] decomposed:
This is not a true nigh-mode. I am talking about something that other manufacturers offers, a mode you can turn on / off manually and something that hives great night results. Mark 3 still is far behind competition in worse light conditions...

Example of dedicated night mode I am referring to:
[Sony Xperia 1 III] Mazellat:
A12's camera quality beter than A11's.
[Sony Xperia 1 III] Hudrator:
Ah is see what you mean.

Well i wouldn't count that in. With the more tradtionell photography appoach sony is taking, i don't think we will see something like this in near future.

Which is okay i guess - concidering the target group of the device. Not aiming for "main stream" in this regards i guess.

As well i would love to see some kind of that maybe in the basic mode - giving the customer the choice which approach he prevers.

@Mazellat

Can you give some more detail? What has become better? Would love to hear some news on this as - due to the availeability - it seems that there hasn't been to much testing on this at the moment.
[Sony Xperia 1 III] decomposed:
Not to go off the topic, this is mostly to confirm whether sony applied planned product aging for camera or not. Would be great if someone could post Android 11 and 12 comparison sample pics.
[Sony Xperia 1 III] WarVic[NZ]:
Sony is not known for improving photo quality with updates. And their updates rate and older product support lags behind the competition. For example not that old Xperia 5 is still on October 1 2021 security update. Suggest that it will never get Android 12.