yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] badabing2003:
This should tell you what they mean.
[Google Pixel 6] freonchill:
Requesting help for what to do next when I was noob enough to not check the sha256 for the factory download and got an error...

was trying to upgrade from SQ3A.220705.001.B2

to TQ1A.221205.011

rooted

ironically, it said there was an error and still continued?! (not a good sign)

Path = D:\backups android\pixel6\22-0827\_installer\oriole-tq1a.221205.011-factory-c9a67c51.zip
Type = zip
Physical Size = 2404622434
ERROR: CRC Failed : oriole-tq1a.221205.011\image-oriole-tq1a.221205.011.zip
Sub items Errors: 1
Archives with Errors: 1
Sub items Errors: 1
Package ID: 1
Boot ID: 1
Package_Boot ID: 1

it then successfully patched the boot.img

I did the

Flash Both Slots: True

(since I had read that going from 12 to 13 it was a good idea to keep from getting a bootloop if it tried to boot to slot B and get the 12.x vs the 13.x

everything was going good until

extracting system_ext.img (353 MB) to disk...ziparchive W 12-10 23:41:21 59216 51804] Zip: inflate zerr=-3 (nIn=01801640 aIn=16888 nOut=01805f00 aOut=31040)
fastboot: error:
failed to extract 'system_ext.img': Zlib error
rebooting to bootloader ...

so it was on fastboot and I tried to reboot and it would just go back to fastboot (guessing because the system files didn't get written...

so I redownloded the TQ1A.221205.011 factory image and checked the SHA256.

what do i do now, run from fastboot, recovery, etc?

Please help me get my phone back in working order.

Thanks in advance.

sanitized log attached

support.zip

drive.google.com
[Google Pixel 6] badabing2003:
Initially, your firmware zip was corrupt, even though boot.img part was ok, the rest of the zip, specially the part where system_ext.img is stored is corrupt, hence it couldn't extract / flash.

Now that you have re-downloaded the firmware and checked the checksum, just repeat the processs (the steps) and you should be fine.

In the next version, I'll add functionality for PF to display SHA1 of the firmware this way you can check if it matches.

By the way, there is a newer Magisk than you're using.
[Google Pixel 6] freonchill:
Thanks for the confirmation.

I did download again and checked the sha256.

Can I do it from recovery mode (pixelflaher gave me a notice that if I didn’t do it right it would brick) or should I do it from fastboot? If fastboot, it wasn’t detecting the phone from that fastboot menu….

Was doing the dual slot flash the right thing to do or should I have just done the flash in the primary and then go back and boot to the b slot after successful flash?

I’ll admit I had not updated my magisk recently and was going to check all updates after doing the flash… I had debated on disabling magisk to not have any bootloop issues.

Thanks for walking me through it.
[Google Pixel 6] badabing2003:
If your phone gets into bootloader mode, PF should detect it and able to flash, do it in bootloader mode, in any case if PF detects your device, it should be able to switch to bootloader mode.

You can do either way, flash to both slots, or do one slot at a time, it's just easier if you select flash to both slots and let PF take care of it.

You don't have to disable / uninstall Magisk, although it is always a very good idea to disable modules (you can do so from within PF)

The modules I use, I keep them enabled because I know they have never caused any issues, your mileage may vary.

For reference these are the ones I use

Magisk Modules:
BuiltIn BusyBox enabled 1.0.3
Axet's Call Recorder enabled v1.8.2
Systemless Hosts enabled 1.0
Magisk Bootloop Protector enabled v1.8.1
Universal SafetyNet Fix enabled v2.3.1
SQLite for ARM aarch64 devices enabled v1.3
[Google Pixel 6] freonchill:
thanks for all your help.

i re-ran PF when I got home and it did see the phone in fastboot and I was able to run it again and get it all updated.

i learn a little more every time I do this - like is used to when using twrp on my sgh-i337 and 1+5T

thanks again
[Google Pixel 6] enigma2446:
ok so dumb question after reading this whole thread and now my head hurts lol. Can i use the most recent BETA OTA image for my pixel 6 and flash it useing this tool and all i have to do is select keep data for i dont lose anything? I ran into a issue i was rooted but magisk said stock boot image does not exist so i flashed the stock image via fastboot to be unrooted but the update says istallation problem when i try to update within the OS. Thats where im at.
[Google Pixel 6] andybones:
Are there any YT videos showing PF in action? /how to use?
[Google Pixel 6] badabing2003:
The verifications that are done by the OTA is the same if it is done correctly on the phone or from PF, so if it is failing on the phone it would also fail in PF.

On the other hand, dirty flashing full factory image does not have that issue.

Switching between beta and standard releases has some wiping requirements, / implications.

You need to read the beta docs and see if you are ok with those.

OTA is probably failing because your inactive slot is not stock.

I don't think there is, I have not made one and no one has posted a video or referenced one made by someone else.

It could be helpful, I just don't have the bandwidth to deal with video making.
[Google Pixel 6] TheProxyOne:
Hi, I just made account here, to say big thank you for the Pixel Flasher. I messed up during root process after flashing patched boot.img, phone stuck on google logo, but thanks to Pixel Flasher and XDA forum I could flash firmware again with keeping all data safe and finally gained root :)
[Google Pixel 6] enigma2446:
I'm on TQ1A.221205.011 I thought that was beta. Would flashing the unmodified boot img to inactive slot fix the issue. Sorry about the double post.
[Google Pixel 6] badabing2003:
If the only changes made are the boot, then yes.
[Google Pixel 6] Robshr:
Hi is it possible to flash one of the roms on pixel 6 forum with pixel flasher?

Thanks
[Google Pixel 6] badabing2003:
Yes and no,

It depends on the ROM, which ROM you want to flash?

Link to download / guide ?
[Google Pixel 6] Robshr:
Wasn't sure I just wanted to know if it was possible I kinda figured it would depend on the rom
[Google Pixel 6] kuusemets:
Hello!

I have Pixel 6 and Android 13 Beta 2.1 - T2B2.221216.008 https://developer.android.com/about/versions/13/download

"oriole-t2b2.221216.008-factory-24b71908.zip"

And I want to root.

I follow every step (patched, keep data).

It finish the process, no errors-

When phone starts and I check Magisk - I see installed - N/A.

Can anyone have some suggestions?

Tanel
[Google Pixel 6] Lughnasadh:
Are you using a Pixel 7 patched boot image? If not, do so as that is needed to root on the Pixel 6 series running QPR2 betas.
[Google Pixel 6] kuusemets:
I use Pixel 6 boot.img.

Just readed that Pixel 7 use "init_boot.img".

So you want to say that I need to take Pixel 7 factory image and from there this init_boot.img and rename this to boot.img?

Because as I understand Pixel 6 do not "use" init_boot.img
[Google Pixel 6] Lughnasadh:
No, use the Pixel 7 boot.img to patch.
[Google Pixel 6] kuusemets:
Thanks!

I try and I let here know my results. :)
[Google Pixel 6] kuusemets:
@Lughnasadh it works, thank you for pointing right directions. :)
[Google Pixel 6] badabing2003:
Please check this issue.

It applies to all Pixel 6 series with 13 Beta

You need to get the matching boot.img from Pixel 7 and patch + flash that to get root access.
[Google Pixel 6] badabing2003:
New Release:

Feb 05, 2023 v4.7.0 release

Added Magisk Backup Manager:

List all Magisk backups currently on the device.

Highlight the one that is backup of the current installed version.

Delete backups.

Manually add backup from PC.

Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.

Added Reset on Magisk Manager package name setting to reset to default: com.topjohnwu.magisk

Linux / Mac build.sh now switches to the PixelFlasher folder if it is run from elsewhere.

Magisk installer improvements:

When installing Magisk Alpha or Delta, PixelFlasher updates the configuration to match the package name to the respective Magisk package.

Magisk installer window displays the package name.

You can now copy to clipboard, the download URL and package ID.

Magisk Manager columns are now wider for better readability.

Package Manager improvements:

Added Search / Filter option.

Show count of filtered packages.

Application Name (label column).

"Get Application Names" Button to resolve all package application names. This is a slow process, hence PixelFlasher caches them.

Button to download (pull) APKs from the device. (Multiple downloads in one shot is also supported).

Other under the hood improvements.

When selecting a firmware or ROM file, sha256 is printed to console and displayed on hover, to validate if it matches the published sha256.

More verbose logging that helps with troubleshooting.

Double click on "ADB Connected Devices" to invoke adb kill-server which is handy at times, specially when dealing with Wifi ADB.

Moved existing links under Help Menu | Links, and added few more handy links.

Added timestamp to support.zip filename.

On request, spinning cursor with text "Please be patient ..." is now displayed in red.

Flashing to inactive slot is now in basic configuration instead of advanced configuration.

Preparation work for version 5.0 DB improvements.
[Google Pixel 6] badabing2003:
New Release:

Feb 12, 2023 v4.8.0 release

#50 Support for Android 14 Developer Preview for Pixel 7 and Pixel 7 Pro

#48 Do not allow patching with hidden Magisk (stub) and adb shell not granted root rights.

Block using Android Platform Tools version 34.0.0 and display a warning because it has known issues

Disable Magisk Backup Manager button if root access to adb shell is not granted.

Button to Open adb shell connected to the selected device.

Work in Progress: Generate graphical activity log to visualize the activity and speed up troubleshooting.
[Google Pixel 6] tom1807:
Google released SDK Platform-Tools v34.0.1

Changelog:

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

Cheers

Tom
[Google Pixel 6] Lughnasadh:
The link still points to 34.0.0. Also, the changelog doesn't include the skipping of fastbootd issue (268872725) so I would recommend people still use 33.0.3 for now if flashing factory images or anything else which may need to be flashed in fastbootd.
[Google Pixel 6] tom1807:
Damn it, you are right, I thought they would have updated the link, but there is also no direct link available.
[Google Pixel 6] spida_singh:
Hi, im trying to sideload ricedroid:-

https://xdaforums.com/t/rom-tiramisu-aosp-oriole-ricedroid-v10-2-android-project-official.4562299/

I used the tool apply the Feb 23 stock Pixel firmware which was clean flashed, all booted OK.

Enabled USB debugging, bootloder is unlocked, and attempted to sideload the ricedroid ZIP file via custom flash.

It gets to about 47% and then just stops, manually doign this also stops at the same place with an error code 21, and saying Zip file signature Verification error.:-

serving: 'D:\Sundeep\Downloads\ricedroid\riceDroid-13.0-202303070339-oriole-v10.2-CORE-OFFICIAL.zip' (~43%)
serving: 'D:\Sundeep\Downloads\ricedroid\riceDroid-13.0-202303070339-oriole-v10.2-CORE-OFFICIAL.zip' (~44%)
serving: 'D:\Sundeep\Downloads\ricedroid\riceDroid-13.0-202303070339-oriole-v10.2-CORE-OFFICIAL.zip' (~45%)
serving: 'D:\Sundeep\Downloads\ricedroid\riceDroid-13.0-202303070339-oriole-v10.2-CORE-OFFICIAL.zip' (~46%)
serving: 'D:\Sundeep\Downloads\ricedroid\riceDroid-13.0-202303070339-oriole-v10.2-CORE-OFFICIAL.zip' (~47%)
Total xfer: 1.00x
2023-03-09 10:09:28 Done!
Flashing elapsed time: 123 seconds
------------------------------------------------------------------------------

Any ideas what this could be? Thanks
[Google Pixel 6] badabing2003:
Have you tried to download the file again or check the checksum of the file to make sure it's intact?

I'm suspecting download corruption.
[Google Pixel 6] allday5850:
Hi. So I have Pixel 6 and am on build TQ1A.230205.002. I am using Pixel Flasher to patch boot img. But for the life of me I can't get root access. I read about users using the 7 series boot img intead to get root access, but I didn't read anywhere about this build succeeding that way. Also, I tried just cuz I was out of ideas and it didn't work anyways. Have you heard of it working anywhere or any users you spoke with? I'm not sure if I should report this to you or to magisk bug on GitHub but I figured I'd start here
[Google Pixel 6] badabing2003:
What version of Magisk are you using?

What version of Android platform tools are you using.

If you provide support.zip file (help menu) I can check what is going on.

I suspect Magisk version at play.

If you are using Canary 25207 up to 25211, then go back to 25206 or use stable version.

Make sure Android Platform tools version is 33.0.3, version 34.0.0 and 34.0.1 have issues
[Google Pixel 6] allday5850:
Just to add to that I was previously using Pixel Flasher to update at the beginning of January and had no issues at all. Had root and everything was fine. Then somewhere along the line something went wrong with something id flashed. And I was stuck in bootloop. I got it to boot normal again but now since I'm on February build I cannot get root
[Google Pixel 6] allday5850:
Magisk Canary 25210.

Platform tools 33.0.3
[Google Pixel 6] allday5850:
It did start happening right after a magisk update... Which I suspected may be the culprit. Let me see about getting you a log
[Google Pixel 6] badabing2003:
Yeah it's the Magisk,

Just drop to 25206 or stable and you should be good.

Create a patch with 25206 and just flash the patch, no need to do full image
[Google Pixel 6] allday5850:
Awesome thank you. But where can I find 25206? I looked on releases I didn't see it. I'm sure I just didn't look in right place
[Google Pixel 6] Lughnasadh:
This should be it...

GitHub - topjohnwu/magisk-files at 5b2934603f979d7133e67bbc30c6ce3fa0d8e31e

Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.

github.com
[Google Pixel 6] allday5850:
.... See I did look on that repo too I passed it right up. Thanks again. I'm gonna use that to patch my .img. Then I'll get back to you if for some reason I don't gain root
[Google Pixel 6] allday5850:
so its been hanging for a really long time..longer than it should be i feel like. do you want me to attatch another support file?
[Google Pixel 6] badabing2003:
yeah it shouldn't hang, please provide support.zip and I'll take a look.
[Google Pixel 6] allday5850:
Okay I appreciate you. Give me about an hour I had to leave the computer n take care of a couple things. But as soon as I get home I will send
[Google Pixel 6] allday5850:
I got it to root. FINALLY. so it must have been magisk that was causing it. Man... That was rough. Thank you for your advice with that I had a feeling magisk might be culprit, but I had no idea which release would get me root. So you saved me even more heartache I was about to endure. It was Magisk 25206 that worked for me. Do you know why the other builds of Magisk aren't working for some of us? Or is that still a developing issue
[Google Pixel 6] badabing2003:
New Release:

Mar 14, 2023 v4.8.1 release

#47 Feature request: Added partition manager - Allows to erase partitions, and / or dump / backup partitions to PC.

Added more visual troubleshooting event flows.

Added warning message for when Android platform tools versions 34.0.0 and 34.0.1 are used.

Improved support.zip redactions.

Added Support.Zip generator button on the Main screen.

APK Install option can now set the ownership to Play Store Market (useful for Android Auto)

Check and warn the user when Magisk Canary versions 25207, 25208, 25209 and 25210 are being used.

Bug fixes and other improvements.
[Google Pixel 6] badabing2003:
New Release:

Apr 10, 2023 v4.8.2 release

Include additional Magisk versions in the check to display a warning dialog when the user has installed one of the known versions to have issues.

Display USNF related flag values when selecting a device.

Check the downloaded Google firmware checksum to match the one in the filename and warn if it does not.

Link to download Google USB Driver is added in the help menu.

Added more visual troubleshooting event flows.

Install APK now defaults to Non Market.

Added Install APK cancel option.

You can now select an app in package manager and right click to launch it on the phone.

Minor bug fixes and other improvements.
[Google Pixel 6] tom1807:
Let me be the "first" giving a feedback. Everything worked smooth with the April Update on my Pixel 6 and the latest version of PF.

Btw. amazing how much the program evolved over the time and you keep adding new features.

Cheers

Tom
[Google Pixel 6] linuxdep:
Hi, where did you get the April update??? I see only the last update from february when I click on the link on the left???

Ha then searched... have found an April update, after reboot I see that was probably the beta ... hopefully this is not a problem when there is an update to go back to the normal version?

My phone has offered me an update, you can actually turn off the automatic update, then I just searched ...
[Google Pixel 6] tom1807:
I am downloading the Factory Image from the Google Website and flash with the Pixel Flasher.

Faster than Google which takes ages to "optimize the device" (not sure whether this is still the case) and everything works after that.

Cheers

Tom
[Google Pixel 6] badabing2003:
Sorry missed your post.

People have reported that they don't see all the images unless they switch to English.

Try that, click on the link in PF to take you to the downloads page and switch your language, see if that works.
[Google Pixel 6] kariem112:
hmm it seems something went wrong when flashing the April update on a rooted Pixel6. Got bootloop after initial flash and can't get it back in working state. Tried flashing the previous version with and withouth patched boot image...

"

Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)

fastboot: error: Command failed:

I am on latest version of Pixel Flasher and tried various platform tools verions.

after various tries (don;t know what changed) the phone booted again. Let me know if you need any logs to investigate
[Google Pixel 6] badabing2003:
Yeah sure, I need support files. That would tell me what went wrong.
[Google Pixel 6] mvasil:
That's what I got when I flashed using platform tools v34 instead of v33. Unfortunately it's a known issue but Google keeps v34 online.

If that's your case you need to make sure your phone is powered off, then boot it using pwr+vol down combo. You might need to try this more than one time until you get it to boot to fastboot. From there you can reflash but make sure you use platform tools v33 this time.

So yeah I think the takeaway from this is your case doesn't appear to be something new, also don't try multiple platform tools versions; stick to v33 until there are news of Google fixing v34.
[Google Pixel 6] badabing2003:
Good advice, but the user already tried various platform tools.

It's a communication issue between the phone and the PC, which got resolved by changing the cable.
[Google Pixel 6] badabing2003:
New Release:

Apr 27, 2023 v4.9.0 release

Added support for installing / creating patch with @Namelesswonder Magisk zygisk64_32 (stable, beta, canary, debug versions).

Support for recognizing Lineage firmware and extracting / patching boot.

Display 32 bit capabilities of the device.

Utilize New Magisk 26.x flags as needed (patch support for more devices).

Disable Flash to Inactive slot and Flash to both slots button if the device is not A/B device.

Partition Manager can now list the partitions even if the devices is not rooted.

Added Custom Patch button, which allows selecting a boot file from disk and getting a patched file back to save to disk (all on the PC).

Added Open Folder button to open a file browser to the directory of the selected boot image.

Added Reboot to Download button (Odin mode).

Added Reboot to Safe Mode button.

Storage reorganization, store patched files next to the stock file, and set the patch name to clearly indicate both source and target sha1.

Various additional validation checks.

Bug fixes and other improvements.
[Google Pixel 6] vendo232:
Folks I`m on latest FW 13.0.0 (TQ2A.230405.003.E1, Apr 2023) and latest PixelFlasher 4.9 when flashed the patched boot it went OK in Flasher tool but the unit is not rooted, Using latest Canary MAgisk

Tried moving the boot.img to the phone and patching in Magisk and then flashing from PC but it crashed my phone, got stucked on Google logo and had to recover my phone.

I did notice there was one small update after the big one recently and perhaps the image on the web is not the latest?

could it be beacuse the SHA1 is not matchinf Source?
[Google Pixel 6] badabing2003:
Please provide support.zip so that I can see if anything went wrong.

What you have circled is correct, the first column is the SHA1 of the file / image, and the second is the source (stock) file's sha1, if they match, then the file is not patched.

Have you at any point had Magisk hidden?
[Google Pixel 6] vendo232:
Yes I have

OK now it works. I have flashed the device manually via CMD on Windows. Used latest Canary to patch the image again and used Tools 33.

I have also uninstalled the hidden app Settings as I used to hide Magisk

Quick note: when I got stuck on Google logo I used https://flash.android.com/ to flash latest FW and got back in w/o loosing data.
[Google Pixel 6] badabing2003:
I don't see anything wrong in the logs, most likely culprit is the hidden Magisk, it's a known issue, if you have more than one Magisk (one hidden and one not) Magisk app will show that you're not rooted, but in fact you are, you just have to uninstall the hidden one.

You can then hide the normal one after reboot.
[Google Pixel 6] badabing2003:
New Release:

Apr 30, 2023 v4.10.0 release

Added no reboot option, with this option selected, after flashing is completed, the phone will not reboot to system, giving a chance to take other actions before reboot.

Added built-in file editor, you can now edit the flash script before running, in case you want to customize it (needless to say, should only be used if you know what you're doing)

Added a button to open an explorer in working directory, useful for people who want full control, perform manual actions by following guides, but using PixelFlasher to do the prep work.

Made the Firmware and Rom Process buttons, full with text. It wasn't obvious for some.

Detect and handle Magisk Zygote64_32 automatically, thanks to @Namelesswonder for adding the necessary marker.
[Google Pixel 6] maximusfoa:
Hello! Please tell me how to update the stock with root?
[Google Pixel 6] badabing2003:
Have you checked the usage in the Main thread's OP or on Github?
[Google Pixel 6] maximusfoa:
Oh no. Ok I will look.
[Google Pixel 6] maximusfoa:
Can you tell me more, is it possible to install your program in gentoo?
[Google Pixel 6] tom1807:
And again, smooth flashing with PF 4.10.0 and the May Image TQ2A.230505.002.

2 generic suggestions but I am not sure whether this has been already implemented (don't recall now all changelogs)

1. Display a warning if any higher version of ADB v33.0.3 is installed (maybe even download the correct version to avoid problems or show the download link).

2. If Magisk is hidden, maybe display a warning and ask to unhide Magisk before continue the flashing.

I myself forgot that for the April image, changed it and before started the flashing and didn't refresh the name in the configuration. Of course mobile was not rooted, so was running it again and with the correct Magisk name and everything was fine again.

Cheers

Tom