yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] V0latyle:
I think you mean slot. It's important to understand that each CRITICAL partition has two slots - bootloader_a, bootloader_b; boot_a, boot_b; system_a, system_b. However, the /data partition has only one slot. This is why it is not possible to "dual boot" on A/B devices.

My point was that while making nandroid backups with TWRP is pretty convenient, it should also be possible to dump the partitions of a slot via ADB without using TWRP.

Additionally, it's not the A/B layout itself that makes custom recovery difficult; it's the fact that most A/B devices do not have a bespoke /recovery partition; instead, the recovery kernel is in the boot image, alongside the system kernel. This normally isn't a problem, as installing TWRP (the right way, by patching the boot image) replaces the recovery kernel with TWRP; the problem is, since Magisk also patches the boot image, it seems the two do not play well together. I have been unable to install both TWRP and Magisk; this results in a boot loop.

Therefore, I maintain that the best way to use TWRP is via live booting, and it should not be installed..
[Google Pixel 6 Pro] badabing2003:
Yes,

Make sure you follow the initial steps of unlocking your bootloader (if you have not done that yet, it will wipe your phone)

There are excellent guides linked in OP of PixelFlasher

You can either do all the rest of the manual steps from those guides (make sure you choose the ones relevant to your device)

or continue with PixelFlasher (after unlocking bootloader) by following these steps.
[Google Pixel 6 Pro] prozack1983:
Hello and thanks for making this tool! I am having trouble with the latest release. When attempting to flash the april factory update the phone will boot into fastboot, but the program errors out with this output on the console-

PixelFlasher 2.1.0.0 Flashing Phone

==============================================================================

Rebooting device 1A091FDEE006DJ to bootloader ...

debug: "C:\Users\zwest\Desktop\platform-tools_r33.0.1-windows\platform-tools\adb.exe" -s 1A091FDEE006DJ reboot bootloader

Waiting 5 seconds ...

ERROR: Device 1A091FDEE006DJ not in bootloader mode.

Aborting ...

I'm rooted with the latest magisk and I've tried rebooting both CPU and Phone a few times, but keep getting stuck here.

Any help is much appreciated!
[Google Pixel 6 Pro] badabing2003:
if you hit the reload button, does your device show up in bootloader mode f.b ?

if it does, the you can try flashing again, without doing anything else, ie, package is already prepared, so you can jump straight to flashing, and you should be able to flash, even if your device is in fb mode.

After rebooting to bootloader, the app sleeps a little and then refreshes to see if your device is in bootloader mode, perhaps it sleep is not long enough for your device.
[Google Pixel 6 Pro] prozack1983:
It doesn't seem to be showing up in f.b. when reloading. I will continue trying. Thanks for getting back to me so quickly!
[Google Pixel 6 Pro] badabing2003:
when you open a command prompt and type

fastboot devices

what do you get, if it does not show up in there then it is a driver issue.

There are a lot of articles on how to get fastboot to detect your phone, just google it, it's not a PixelFlasher issue if fastboot devices does not see your phone.
[Google Pixel 6 Pro] prozack1983:
That seems to be the problem. I'm not sure why it's not pulling it from the platform tools, but I'll attempt to remedy that. Thanks again!
[Google Pixel 6 Pro] Lughnasadh:
This may help, if you don't have the latest installed and you're using Windows.
[Google Pixel 6 Pro] prozack1983:
Got it! The google page for installing the drivers does not list the correct procedure for installing them for some incomprehensible reason. Thanks again!
[Google Pixel 6 Pro] ntegra:
Is there a reason why this doesn't identify as "Pixel Flasher" requesting root instead of some generic "Shell"?
[Google Pixel 6 Pro] badabing2003:
PixelFlasher is a UI wrapper around the standard adb / fastboot commands you execute via shell, as far as Magisk is concerned it's a shell.
[Google Pixel 6 Pro] Blade22222:
Worked perfectly updating to the April update. Will be using this tool from now on. Great work!
[Google Pixel 6 Pro] rhetorician:
Having some issues. The program returns an error about not finding boot.img. May I post my the log?
[Google Pixel 6 Pro] badabing2003:
Sure, I'm heading out now, but will respond back when back.

Full verbose log would be very helpful
[Google Pixel 6 Pro] badabing2003:
Checking on the phone.

You're not using the latest PixelFlasher, try with that. Also you should use latest magisk
[Google Pixel 6 Pro] rhetorician:
Okay, I updated magisk and tried again. This time, I had magisk open during the prep step and was prompted for shell access again. Approving it advanced the program and soon I was ready to flash. During that process, while in fastbootd, several errors appeared in the log and I grew pretty concerned. So, I decided to walk away and about 7 minutes later the process had completed. So, I can report back that it was successful. I'll update the tool ahead of May's update. Thanks for your help and your time developing this cool tool.
[Google Pixel 6 Pro] badabing2003:
Happy to hear that you got it all working.

I'm curious to see what errors you encountered, helps in making the app more robust, or if it is a phone / connection issue, identifying and taking corrective measures.

You can find PixelFlasher logs in

%APPDATA%\PixelFlasher\Logs
[Google Pixel 6 Pro] badabing2003:
New release:

April 10, 2022 v2.2.0 release

Linux support.

Remember last window position.

List Magisk modules, when Magisk is detected.

Added fastboot verbose option.

Added more checks and validations.

Added more details when errors are encountered.

Cleaner message box (better formatting).

Notice to the user in case fastboot drivers are not setup properly.

More plumbing work for the new upcoming workflow.

Add notes on how to build the Linux version.
[Google Pixel 6 Pro] Zach Alt:
I'm actually excited to use this again for the May update.
[Google Pixel 6 Pro] puertorecon:
I have a question. Will there be support for ChromeOS?
[Google Pixel 6 Pro] Thebear j koss:
Ok, it doesn't really matter as on a pixel device your data should be getting backed up and 1 slot should have a working boot if you are switching a & b on system/security updates. (Besides the google gaffe of the android 13 update of needing both slots updated). I liked custom recoveries, but they aren't really necessary, and on newer devices not feasible at this point. I wasn't disagreeing with you, but as stated also above there are other options to backup things and you should always have a working slot to boot.
[Google Pixel 6 Pro] V0latyle:
Some data is backed up. App data and anything in storage (besides photos) is not.

I don't really understand what your point is? Of course we all want our devices to work; it seems like you're saying one slot should be kept "pristine" while you make changes to the other slot? This isn't necessarily a good idea - you can't flash a custom ROM on slot B while you have the stock firmware on slot A. I mean, you can, but it won't work because both slots share the same /data partition.

If you're talking about updates, this is really just a matter of preference - some people prefer to update alternate slots via OTA, while others (like myself) like to flash both slots every time using the factory image.
[Google Pixel 6 Pro] iwearthebelt:
Thanks for the useful information. Like I said earlier, I've been out of rooting/mods/custom stuff for about the last 5 years, so it's like learning to do things all over again as things have changed a lot. The more questions and answers posted on this topic the more it helps me understand how things work since they have changed. It will help others as well (so long as they read the discussion). Pixel Flasher is a life saver for me after being out of the game for so long. Same as Wugfresh's toolkit helped me back in the day.
[Google Pixel 6 Pro] badabing2003:
New Release:

Nov 09, 2022 v4.4.0 release

New feature: Font and Font size should be configurable by the user #33

New feature: Added WiFi-ADB connect / disconnect button. Left click to connect, Right click to disconnect.

Handy to access a device remotely.

Note: This only works in adb mode, so no fastboot or flashing features work for remote devices, but for patching / installing apks, managing Magisk modules it works well (basically anything that is done in adb).

I personally use this to test patching on remote devices, and also use it to access / install apps to my watch.

Ground work for future features: Get installed Package list, and list which are disabled, enable / disable / uninstall apps. (Will be available in future release).

Move Flash Option Flash to inactive slot to Basic mode from Advanced mode..

Minor UI Improvements

If Magisk does not create a backup attempt to trigger Magisk to create one.

Update readme to include Pixel 7 / 7P specific info.
[Google Pixel 6 Pro] badabing2003:
New Release:

Dec 04, 2022 v4.5.0 release

New look (Artwork / Icons), compliments of @t-ryder (thank you), based on Material design icons.

New Feature: Package Manager, Install / Uninstall / Freeze (disable) / Unfreeze (enable) packages even system ones (root not required). Handy with Wifi ADB.

Use latest Python updated packages.

Ubuntu 22.04 support.

Miscellaneous improvements.
[Google Pixel 6 Pro] Thebear j koss:
Worked perfect once again on pix 6 pro stock rooted from Nov to Dec update. 👍🐻
[Google Pixel 6 Pro] iwearthebelt:
I'll second that, just updated to the December release as well on my P6P. No issues, didn't even have to disable any modules. Flawless!
[Google Pixel 6 Pro] badabing2003:
New Release:

Dec 05, 2022 v4.6.0 release

Added single click button to easily flash just the boot/init_boot (stock or patched) to the phone.

#39 Display Flash Option changes in the console, and allow flashing to inactive slot in basic mode.

#39 Do the Magisk backup only when rooted.

Decouple OTA sideload from needing factory image.

Other minor improvements.
[Google Pixel 6 Pro] Kris Chen:
New version v4.5 cannot be opened in my Win11 pro.

I checked the background and I found pixelflasher was running but it just couldnot be loaded on my win11 pro desktop.

Even I tried to kill them all and tried it again, the result was the same.Now I tried v4.4 to flash new releasing Dec ROM and without any problem.

I hope developer to fix it.
[Google Pixel 6 Pro] badabing2003:
Thanks, I'm aware, I just don't have any data / error logs to understand what is going on, and I cannot reproduce the issue on multiple Windows 11 computers.

See this issue at GitHub.

See if any worked for you, and if you can try with AV off, that could help.

Please supply support.zip, you can generate it with 4.4.0.0

Hopefully the logs will include something.
[Google Pixel 6 Pro] knopie:
To use this app it is very easy, I updated to December without any issues.

Thanks.
[Google Pixel 6 Pro] bush911:
same for windows 10
[Google Pixel 6 Pro] badabing2003:
Release v4.6.1.0: - #40 Handle locale related exceptions which were causing PixelFlashe… · badabing2005/PixelFlasher

…r to not launch on some Windows 11 systems. Add the ability to download and install a special Magisk version that has modules loading intentionally disabled. Required to get out of bootloops and ...

github.com
[Google Pixel 6 Pro] badabing2003:
New Release:

Dec 06, 2022 v4.6.1 release

#40 Handle locale related exceptions which were causing PixelFlasher to not launch on some Windows 11 systems.

Add the ability to download and install a special Magisk version that has modules loading intentionally disabled. Required to get out of bootloops and manage to disable modules.

Credit to gecowa6967 at XDA.
[Google Pixel 6 Pro] AlDollaz:
This app just makes everything about flashing easier. Thanks for the quality app!
[Google Pixel 6 Pro] Nazmulhuda:
how to flash pixel phone withour boothloder unlock possable?
[Google Pixel 6 Pro] badabing2003:
Sorry, that's not possible.
[Google Pixel 6 Pro] bush911:
What I was wondering is whether I can use your flasher to update Pixel 3 from Android 11 to latest Android 12.

I pixel 3 was rooted and was with Lsposed and several moudules.
[Google Pixel 6 Pro] badabing2003:
Yes you should be able to.

Download the Android 12 firmware

process

create patch

disable Magisk modules (you can do so in PF) (you can keep Safetynet fix and systemless hosts enabled)

flash

enable modules that are safe to enable,
[Google Pixel 6 Pro] bush911:
Thank you so much. It is good to know, I have already updated Pixel 6 several times via your App, which really rocks
[Google Pixel 6 Pro] amritpal2489:
How do I update my rooted Pixel 6 Pro using this tool? Is there any step by step guide?
[Google Pixel 6 Pro] badabing2003:
Yes, you can check the main thread that this OP points to (this is the support thread).

Or you can check the links in my signature.

Should be simple and obvious, but if you have any questions, don't hesitate to ask.
[Google Pixel 6 Pro] BROKEN1981:
Sorry if this was said, I'm skimming the thread for now. Will read everything later.

Will this work on the newest beta OS?
[Google Pixel 6 Pro] badabing2003:
You're aware about the issue of needing to patch p7p boot and installing it on p6p to get the beta rooted right?

Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk

After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...

github.com

Assuming that you want to update p6p, what you could do is first extract the boot.img from P7P firmware

After processing the p6p firmware in PF

navigate to the directory where PF extracted the boot.img

(Click on the boot.img in PF, and it should tell you the path in the console)

Replace that file with the one you extracted from p7p

patch and then flash as you would.

If this is the first time you're using PF, please check the usage documentation.
[Google Pixel 6 Pro] BROKEN1981:
Thank you, I didn't know that. I haven't rooted since the LG V30. So it's been awhile.
[Google Pixel 6 Pro] 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 Pro] Kris Chen:
No problem here to use v4.7.0 to update Feb-2023 stock ROM.

Say thanks to @badabing2003 for amazing job.

Here I have one suggestion here: In function of "SDS":

"Disable" Magisk Modules mean modules still exist in magisk manager just being disabled but the script seems to remove magisk modules ... That's fine to me I just need to reflash magisk moudles from my phone but just spend a little more time...
[Google Pixel 6 Pro] badabing2003:
You're pointing out to the SOS button, and that is for emergencies only when you bootloop and can't get out of it.

You either boot to safe mode and hope that Magisk disables the modules (which does not always work) or you try that button / adb command (assuming that you get a brief adb access while it is bootlooping)

That is a magisk command, not PF

Are you concerned that the parameter says remove-modules

I could be mistaken, but I believe regardless of the parameter name, it only disables the modules.

Others can chime in with their experiences.

There is also a Magisk Module Manager in PF (the Magisk icon to the left of SOS). You can use that to enable / disable modules, and that for sure will not remove modules.
[Google Pixel 6 Pro] BROKEN1981:
The SoS button works, but I've found that I first need to boot into safe mode, then bootloader for it to actually work. If I don't, it tries to disable the mods but my phone will continuously boot loop.
[Google Pixel 6 Pro] Sand_23:
Hello everybody, how do i update my pixel 6 pro via pixel flasher. I am rooted with some magisk modules and on january build. I dont receive any ota since rooting or maybe safetynet module. I Just downloaded pixel flasher and the new february factory build. How can i update via pixel flasher, keep Data and stay rooted?

Many thanks
[Google Pixel 6 Pro] badabing2003:
Have you checked the usage on the main thread or Github?
[Google Pixel 6 Pro] StanWiz:
Detailed instructions can be found here
[Google Pixel 6 Pro] Sand_23:
So to Update i have to flash factory image not the ota.zip?
[Google Pixel 6 Pro] badabing2003:
yes
[Google Pixel 6 Pro] Sand_23:
Ended up in Fastboot Screen and nothin happened. Had to restore through Android Flash Tool. Maybe i done a mistake by clicking "Flash to inactive slot". But to be clear: With this tool you can easily update new updates? Maybe a wizard, like i saw pages back in the thread, is a great idea for newbies like me to A/B-World of Paritions.

But with all respect thank you very much for this tool.
[Google Pixel 6 Pro] badabing2003:
if you can provide a support.zip (from help menu) I can take a look at what might have happened.

As for wizard, if you follow the basic usage screenshot, that's all you need to easily update.
[Google Pixel 6 Pro] Sand_23:
Sorry, have no support.zip. Eventually i can make a screenshot by the things ive done and you can have a look? Thanks in advance
[Google Pixel 6 Pro] badabing2003:
What do you mean by there is no support.zip.

You just have to go to Help menu and select that option, you can do it now.
[Google Pixel 6 Pro] Sand_23:
Will so it later, thanks for advice
[Google Pixel 6 Pro] 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 Pro] BROKEN1981:
What does flashing to inactive slot mean? This is the first device I've owned with A/B partition. So I'm very much out of the loop. Is this something that I always want to click when updating with the newest factory image and root?
[Google Pixel 6 Pro] badabing2003:
I do it. But that does not mean that you have to do it.

I feel safer flashing to the alternate slot like ota does even though I know my current slot will not be bootable after the flash.
[Google Pixel 6 Pro] BROKEN1981:
So if current slot is not bootable, what sets do you take to boot? Also how do you know which slot you are on?
[Google Pixel 6 Pro] badabing2003:
Current slot is bootable, when you flash to one of the slot, the other slot becomes unbootable.

So if you flash to inactive slot, the current becomes inactive and unbootable, and the inactive becomes current and bootable (yeah that's mouthful)

PF tells you what is your current active slot
[Google Pixel 6 Pro] BROKEN1981:
Ahh ok that's pretty straight forward. So flash to inactive slot, ( example, inactive slot B,) then chose slot A. Pretty sure I saw the ability to chose slots in advanced section.
[Google Pixel 6 Pro] badabing2003:
If you select the option to flash to inactive slot, when you're flashing firmware, PF will automatically change to that slot, you don't have to do it yourself.
[Google Pixel 6 Pro] BROKEN1981:
Ok. You really thought out the entire program. Thank you for what you did for the community! Really so much easier then the T-Mobile LG V30 days of installing TWRP.
[Google Pixel 6 Pro] DaKing1512:
Is it possible to revert back to the January update of A13 after installing the February update of A13?
[Google Pixel 6 Pro] badabing2003:
People say yes. YMMV
[Google Pixel 6 Pro] 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 Pro] BROKEN1981:
So i loaded raven-t3b1.230224.005-factory-f1dca87c into pixel flasher, after i patch boot image i get

2023-03-16 04:26:50 NOTICE: The patched image file does not contain source boot's SHA1

This is normal for older devices, but newer deviced should have it.

If you have a newer device, please double check if everything is ok.

DB BOOT record ID: 2

DB Package_Boot record ID: 2

Please select a boot image!

Magisk Version: 25.2:25200

Patch time: 14 seconds

any idea what i am doing wrong? all other times i used the flasher app i was able to keep root.
[Google Pixel 6 Pro] badabing2003:
Support file will give me an idea.
[Google Pixel 6 Pro] BROKEN1981:
I'm not at the computer right now. Need a few hours. Do I just click the support button after a flash?
[Google Pixel 6 Pro] badabing2003:
Just click the support button, no need to flash again, it already knows.
[Google Pixel 6 Pro] BROKEN1981:
Here is the zip
[Google Pixel 6 Pro] badabing2003:
QPR Beta for P6 and P6P, you need to extract boot from the corresponding P7 and P7P and patch that.

for P6 use P7 and in your case P6P use P7P

There are few threads that talk about this.
[Google Pixel 6 Pro] BROKEN1981:
Thank you
[Google Pixel 6 Pro] BROKEN1981:
I've read how to do it and it seems a bit complicated. I'm just going to go on to the last beta that worked without patching the boot image from a pixel 7 pro
[Google Pixel 6 Pro] BROKEN1981:
for anyone who is a noob like me, this was very easy to follow.
[Google Pixel 6 Pro] Druboo666:
why use pixel p7p image to p6p?doesn't that lead to boot loop?
[Google Pixel 6 Pro] badabing2003:
One would think so, but somehow people figured out that when you patch the boot form P6 or P6P you don't get root, but if you use from P7 / P7P you do.

How they found that out, beats me, it's just shows that when there's a will there's a way.

See this.