yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] CodeOnDiscord:
The version I flashed was `13.0.0 (TQ3A.230705.001, Jul 2023)`

On the English one, that seems to be the latest version. Could It be because I didn't do OTA for previous updates?
[Google Pixel 7] CodeOnDiscord:
I managed to fix it by using https://flash.android.com/

Their default for flashing are shady though, so make sure to disable wipe and locking the bootloader.
[Google Pixel 7] badabing2003:
I don't understand how you would get an update on 230705

Can you provide support file please?
[Google Pixel 7] Stuccio:
He probably got it from here: https://developers.google.com/android/images

I update my panther manually so I download the img from there too
[Google Pixel 7] Coxis:
Hi guys, I hope someone can help me here. I'm sitting here for one hour after starting the patching process for my Pixel 7, and it's become stuck flashing pf_boot.img. Here's a couple pictures of both the PF screen and phone screen. Sorry for the literal screenshot of my PC screen, but I'd rather not mess with it while it's stuck patching.

Running Windows 10 latest patches, latest platform tools. PF is fully frozen, i.e. the "loading wheel" on the bottom left is not spinning.
[Google Pixel 7] badabing2003:
The screen show that it is in the flashing process, not patching.

If it has been in this state for one hour, then it will be in this state forever.

Close / kill PF (leave phone as is)

Launch PF and click on Help | Create a Sanitized support.zip

Post that file, let me look at it, and I'll tell you what to do to recover.
[Google Pixel 7] scorpio76r:
You are the best. You posted while I was carefully thinking of a solution for the member but, when I about to post, you had already posted. Your dedication is greatly appreciated and, your time for a response and, solution is impeccable.
[Google Pixel 7] Coxis:
Thank you, here's the file.
[Google Pixel 7] badabing2003:
Sorry about the delayed response.

First things first, stop using Android platform tools 34.x

Please use 33.0.3

Hit the start button on your phone, and your phone should reboot and get into the system

It should be July image, and stock (unrooted)

After making sure that you have select Android Platform Tools 33.0.3

Just select the patched boot in the list

and hit the Flash Boot button, (not the Flash Pixel Phone button)

This should get you rooted.

Optionally you can choose to flash the other slot as well

by selecting either the stock boot or patched boot (depending on which you want)

And hit Flash Pixel Phone
[Google Pixel 7] Coxis:
I selected the new platform tools 33.0.3, booted the phone, selected the phone in PF, selected the patched boot image and selected flash boot, the phone rebooted into bootloader and the platform tools isn't able to find it.

EDIT: I just tried again and yeah, as soon as the phone reboots into the bootloader PF becomes unable to find it. I reboot the phone into system, and it's able to find it again.
[Google Pixel 7] badabing2003:
From the Help menu | Links | Get Google USB Drivers

download and update the drivers.

Your device is not detected in bootloader mode.
[Google Pixel 7] Coxis:
Thank you so much badabing2003. That did it, phone is now rooted and July 2023 image installed.
[Google Pixel 7] elong7681:
Please help me I can not root my phone it says the file is to large to download
[Google Pixel 7] badabing2003:
New Release:

Aug 07, 2023 v5.6.0.0 release

Added configurable toolbar.

Added device controls buttons to the menu.

Added feature to Magisk Manager, ability to install modules from the PC.

After flashing OTA, detect if the slot switched as expected, if it didn't, skip patched boot flashing (if selected).

Added feature to Package Manager to be able to manage (add, remove, list) Magisk denylist.

Added export csv formatted package list feature.

When sanitizing DB, wipe write-ahead logs (WAL) for better privacy.

Under the hood optimizations.

Verity / Verification status check.

Counter in package manager.

Added a quick link to Android security and update bulletins.
[Google Pixel 7] badabing2003:
Can you check the size of this file? Replace REDACTED with your username

C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4\afec996a66fd67a7472f8d909df4db1ad0e71eed\magisk_patched_26100_afec996a_71f19361.img

Update:

It looks like patching has failed on your phone.

mv: setfilecon:/sdcard/Download/magisk_patched_26100_afec996a_71f19361.img,u:object_r:system_file:s0: Operation not supported on transport endpoint

Something to do with selinux

What modules do you have?
[Google Pixel 7] elong7681:
No file found and I uninstalled all modules and Magisk was unhidden
[Google Pixel 7] elong7681:
I even tried using admin cmd to flash it and it said it was too big to download
[Google Pixel 7] badabing2003:
Did you reboot after uninstalling?

I'm curious what modules you had.

You can try this

Go to settings / configuration and select these options

View attachment 5972233

When you click on the patch button, you will be presented with options

Select the Use Magisk Application

View attachment 5972235
[Google Pixel 7] elong7681:
I will try it out as far as modules I had Osmosis BusyBox, USN mod by Duplix, I had data_backup and data_restore module, Zygisk and pixel tensor audio decompressor yes I did reboot
[Google Pixel 7] badabing2003:
@elong7681

I'm sorry, what is your expectation?

You just threw a support file which by the way doesn't help me when you doctor it and remove parts from it, and you have said nothing, did it work, did not work? did you follow my suggestion? what did you observe?

The support file you provided is totally useless.

Please turn off "Use Busybox Shell" and try again.
[Google Pixel 7] elong7681:
I didn't doctor the file I simply sent what was downloaded from the application, yes I followed your instructions and it said that it could not find Magisk BusyBox inaccessible or not found
[Google Pixel 7] badabing2003:
I'd like to help you, but with the information I'm receiving (or lack of) I can't make heads from tail.

The option I gave you has nothing to do with Magisk it's in PF, I'm not sure how you get that message.

The support file is cumulative, if you don't believe me, look at the file you last provided and compare it to the previous one.

More importantly, the delta of the two should show me the logs of your last actions.

Can you spot that in the file?
[Google Pixel 7] elong7681:
I believe everything you are telling me about the application that you created ( hands down the best piece of software for Pixel phones ) but the support file I sent was generated after I tried your instructions in PF and the message about Magisk/BusyBox being inaccessible is what PF generated in the console. I will provide you with everything I can as soon as I get off of work. I really do appreciate your help.
[Google Pixel 7] badabing2003:
I owe you an apology.

It looks like one of my recent changes has partially broken saving of the log files which is why I'm not seeing anything relevant in the logs.

I need to fix this ASAP.

Sorry again.
[Google Pixel 7] elong7681:
No problem at all, so should I wait for the new update before we start troubleshooting again? I never did make it home last night.
[Google Pixel 7] badabing2003:
Yeah, otherwise it's going to be tough to troubleshoot,

I'll have a release later today.
[Google Pixel 7] badabing2003:
New Release:

Aug 09, 2023 v5.7.0.0 release

Rework the settings window: code refactoring and bug fixes.

Bug Fix: In some cases log files were not saved.

Bug Fix: Custom font size changes were not always applied.

When getting device details, get battery details.

Don't set ASH_STANDALONE=1 when using busybox, it encounters selinux related issue.

Extra check to make sure the created patch is not zero bytes long.
[Google Pixel 7] elong7681:
this is from my most recent try
[Google Pixel 7] elong7681:
This is my attempt to patch the int_boot.img
[Google Pixel 7] badabing2003:
Like I previously asked.

Please uncheck the busybox option.

View attachment 5974237
[Google Pixel 7] elong7681:
I'm I'm sorry I must have missed that part. I just went back and reviewed your message to me and I see it. Now I'm on my way home. I will give it a shot and report back
[Google Pixel 7] elong7681:
That worked thank you for your help
[Google Pixel 7] Cpm0813:
Are we supposed to use the OTA now, instead of the factory image like we always did? What are the pros/cons?
[Google Pixel 7] badabing2003:
See this
[Google Pixel 7] Cpm0813:
So if I understand correctly, this is just so you have the other slot ready to go in case something happens to the primary one?
[Google Pixel 7] badabing2003:
yep
[Google Pixel 7] badabing2003:
New Release:

Aug 13, 2023 v5.7.1.0 release

Print available memory when starting PixelFlasher.

Option to sacrifice speed in favor of using less memory (used when processing large firmware files, turn it on only if you run into out of memory errors).
[Google Pixel 7] badabing2003:
New Release:

Aug 15, 2023 v5.7.2.0 release

Regression Bug fix: Refresh UI to display / hide flash options after changing advanced settings.

Use Python 3.11 instead of 3.10
[Google Pixel 7] bobby janow:
New to this thread and process but a simple question. If the answer is yes then I'll research and figure it out. If no then you've saved me a ton of reading. I need to install the July image over the August image due to an incompatibility with the Galaxy Watch LTE activation. The August update broke the install process although it works if it was previously installed. My device is not bl unlocked but the OEM switch is active and allows unlocking. Doable or must I unlock and wipe the device? I'd rather not have to wipe right now due to 14 around the corner which might or might not fix it. TIA
[Google Pixel 7] badabing2003:
Sorry to tell you, downgrade is not possible without a wipe.

OTA cannot downgrade with or without wipe, you would need to flash factory and wipe

but for that you would need unlocked bootloader.

See some discussion here.

Is there a possibility that you could use Android Emulator or another device just to activate and then pair with your current phone?
[Google Pixel 7] bobby janow:
That was quick! :) I was afraid you were going to say that. I'll wait then for A14 and if it doesn't work do a full wipe first then if it still fails to activate I'll unlock the bl and flash the full July update. Thing is, if it's already activated on LTE it will continue to work after the August update.

I'm not sure about the emulator, I'm not familiar with the process. They can activate the LTE on the back end it just won't install on the account. It's number share so if I'm away from the phone the watch will jump over from BT or Wifi to LTE and ring when the main line is called. It's really quite nice for workouts when you just don't want the phone with you and necessary when swimming. lol. Thank you for such a timely response, you did save me a ton of reading time also. Probably time for a system reset anyway after 14 drops.
[Google Pixel 7] Mississip:
I had no issues with PixelFlasher when I last used it on July 8. This time it gives me a warning that Magisk Manager is not found, and that if it is hidden, I should unhide it. It is installed, and it is not hidden. Is it because I have huskydg.magisk? I had this same version last time and got no error message. Can I safely ignore the message and proceed?
[Google Pixel 7] MikeRWK:
Just wanted to say I love this app, it makes everything too easy!
[Google Pixel 7] badabing2003:
You should set the package name in the settings so that it finds it.

It's looking for the official Magisk.
[Google Pixel 7] Mississip:
You are most excellent!

Unfortunately, I've hit another snag. Though I successfully scanned for and selected my ADB connected device, when I tap 'Flash Pixel Phone' then chose 'OK', after a pause I get 'Unable to detect the device'. Advice, please?
[Google Pixel 7] badabing2003:
support file please
[Google Pixel 7] Mississip:
Thank you for any help.
[Google Pixel 7] badabing2003:
When you reboot to bootloader, the device is not detected, this sounds like driver issue.

From the help menu, click on links | Get Google USB Drivers

Install that and try again.
[Google Pixel 7] Mississip:
I will do as you ask, but first a few (probably) ignorant comments. I installed the drivers from that link a very long time ago, and don't know how anything could have happened to it since this last worked on July 8. Also, the scan button found my phone and let me choose it in ADB devices. Would that have happened if I didn't have the Google Drivers?

Edit 1: Had shortened my post, but restored it to put the quote in context.

Edit 2: That was the issue. I can't imagine how I could have done anything to jinx the drivers when I've used them up to last month.

Thank you very much!!
[Google Pixel 7] badabing2003:
Yes, the drivers are different for adb and fastboot.

Adb drivers are working but not fasrboot.

Why in bootloader mode,

Go and check in device manager

View | Show hidden devices

delete anything that has exclamation mark or triangle.

Then connect your phone as see what shows up, you might have to do refresh in device manager, then select what shows up and browse and update driver.

You phone has to be in bootloader mode.

You can confirm if it is working by typing

fastboot devices

or scanning in PF
[Google Pixel 7] bao_gg:
Hi there, I plan to update to Apr patch from Jan's.

Is there any way to avoid wipe?

Right now the phone is rooted and Magisk is 13adb22d-32bit (25206).
[Google Pixel 7] badabing2003:
Yes of course.

Just follow the usage details in OP or at GitHub.
[Google Pixel 7] doomwithdon:
Can I use full OTA as flash mode and keep data? Or is keep data possible only if factory image flash mode is selected?
[Google Pixel 7] badabing2003:
Yes, with full OTA there is only keep data, there is no wipe data possibility.
[Google Pixel 7] omegalulred:
I have hidden magisk, so it has a different package and name, can I still update and keep that magisk/root/data?
[Google Pixel 7] badabing2003:
Yes,

If you're rooted, PF will use files from /data/adb/magisk and will not need the Manager files.

However it is a good idea to go to PF settings and set the correct package name for your Magisk.

If the Manager has been updated since your last root, then you should hide the manager so that you create a patch with the newer Magisk rather than the old one (assuming that is what you want)
[Google Pixel 7] badabing2003:
New Release:

Sep 19, 2023 v5.8.0.0 release

Added support for scrcpy (Screen Copy), you can now launch scrcpy to the attached device, configuration is done in the main settings window.

Completely redid the wireless connection, there is now wireless manager, that shows history, status and quick selection from history, and supports wireless debugging which requires pairing and is the only option for newer OS-es.

For crDroid and other non Pixel firmware automatically set to Full OTA mode (ie sideload) if payload.bin is detected.

Added a button to reboot to userspace fastboot (fastbootd).

Added system menu to be able to move, resize, minimize, maximize. (useful when the window is of the screen)

When extracting from payload.bin, optionally also extract (if available) dtbo.img, super_empty.img, vendor_boot.img, vender_kernel_boot.img in addition to boot.img and init_boot.img (configurable in the settings), as some of these images are needed for 3rd party firmware flashing.

On Linux, display a message when terminal app is not set and open shell feature is used.

For Samsung devices, when creating a tar file of a patched boot, use POSIX tar format.

Miscellaneous fixes and improvements.
[Google Pixel 7] omegalulred:
Question, how do i recover from boot loops, from magisk/lsposed modules?

I used this utility to install magisk and that's it. How do i enter recovery? To disable modules for example
[Google Pixel 7] badabing2003:
The easiest would be to use the SOS button

This work if your phone during bootloop gets a brief access to adb.

Often this is not the case, and the sos button will not be able to disable the modules.

You can also boot to safe mode by using the key combination, and that would disable Magisk modules

But again this does not always work.

your last option would be to flash a special Magisk version that gives you root without loading the modules.

You would need that so that you can disable the module.

To learn more about this option, in PF, select Install Magisk and then select special and read the instructions.

View attachment 6008817
[Google Pixel 7] omegalulred:
Thank you, with this method can get rid of lsposed modules too?

Is there a custom recovery that i can install with this?

Also using the latest version srccpy is grayed out, what am i missing?
[Google Pixel 7] badabing2003:
The first two methods would disable all modules, and then you can enable or uninstall whichever you want

The third method, you would have to selectively disable modules once you boot to system, and you can do that with PF's Modules button.

Depending on your device, there could be 3rd party recoveries available.

As far as I know you flash all those with fastboot.

You would enable PF's advanced setting, and then select custom

View attachment 6008821

You probably have not selected a device or have not defined where scrcpy files are on your system, you would do that in the settings.
[Google Pixel 7] omegalulred:
Ok thanks, so it disables both magisk and LSPosed module

My device is a pixel 7

Ok thanks!
[Google Pixel 7] badabing2003:
It disables Magisk Modules, which in effect disables all of LSPosed

I don't use 3rd party recovery, but I'm certain that there are many for Pixel 7.

You can check in the Pixel 7 forums.
[Google Pixel 7] badabing2003:
New Release:

Sep 24, 2023 v5.8.0.1 release

Bug fix: #99 Settings not opening on linux/arch based distro
[Google Pixel 7] RealNBB:
Is it possible that the days appear A14 (no custim root, no root) with this tool to flash, because the internal routine always takes forever with the updates.

If so, what would I have to click in the tool? :)
[Google Pixel 7] badabing2003:
I'm sorry I'm having hard time understanding your question.
[Google Pixel 7] Cpm0813:
I think they are asking, the day that Android 14 goes live, can they use this tool to flash their phone without root?
[Google Pixel 7] RealNBB:
Too much beer! :D

I would like to ask if I can also use the tool on a non-root device to flash the "official" Pixel A14 ROM when it comes out?!

If yes, what are the settings?

Greetz
[Google Pixel 7] badabing2003:
Oh yes, you have to use the OTA image instead of factory

Follow the steps in OP

Process the OTA image, select the boot it finds and flash pixel phone.

You don't need to be root to sideload ota
[Google Pixel 7] Project_WHaT:
I am planning on updating from TQ3A.230606.012 with the installed Magisk version listed as a8c4a33e (26103) to the newest A14 OTA with PixelFlasher. I currently have the installed Magisk app version at d4e552d0 (26301).

What is the recommended Platform Tools and Magisk version this time around? Sorry if this a simple question, but I always get tripped up with all the Magisk versions.

My current version of Platform Tools is 33.0.3-8952118. Is this okay or should I update to the newest version? I remember last time around it was recommended to stick with this older version.

When I connected my Pixel 7 to PixelFlasher, it gave the following warning:

WARNING! Problematic Magisk Version: a8c4a33e:26103 is installed. Advised not to use this version

Are there any actions I need to take before I flash A14 with this warning? I am updating to a newer version of Android (and presumably newer version of Magisk) so this shouldn't matter?
[Google Pixel 7] badabing2003:
Keep on using 33.0.3-8952118

Install the latest Magisk App 26301, you can do it in the Magisk App or you can do it from PF

You don't have to apply (install) the root component.

Select A14 OTA

Process

Select the boot/init_boot it shows

Create patch, it will use the Magisk Manager App instead of the root, because it is a newer version

Select the created patch

Flash Pixel phone.

When it loads and finishes optimizing,

Scan for devices, select your device again

Hit Flash Pixel phone to get the other slot flashed as well.

At this point if everything went well, you should have two bootable slots both on A14.

I advise everyone who is upgrading to A14, to do so, to make sure both slots are at A14 and bootable, there is no way the A13 slot is bootable, and if anything goes wrong with the current slot, you want a fallback slot.
[Google Pixel 7] Project_WHaT:
Thank you. Worked flawlessly like always
[Google Pixel 7] SOCOM-HERO:
should you select the inactive slot after rebooting to A14 the first time and then flash? wouldn't reflashing after the first boot and no restart just flash over the same slot again?
[Google Pixel 7] badabing2003:
No,

Those steps were for full OTA images, which always flashes to the inactive slot, to assure that your current slot remains intact.

PF does not do the switching, OTA flashing by design does.
[Google Pixel 7] SOCOM-HERO:
got it, I think I missed the part about OTA and assumed Project_What was upgrading using a factory image. that's correct for factory images and OTAs, it flashes inactive. got confused for a sec!

can't hurt to flash twice, right? I usually only flashed one slot when staying on the same android version, but when going from version to version (13 -> 14) flashing twice is advisable.
[Google Pixel 7] badabing2003:
I flash twice every time, it doesn't hurt to have two functional slots, if you only flash once, only one slot is functional unless both slots have the same exact version of the firmware.

At times, I also switch slots after flashing the second time, for wear balancing.
[Google Pixel 7] badabing2003:
Update Release:

Oct 06, 2023 v5.8.0.3 release

Improved debug messages for troubleshooting.
[Google Pixel 7] w0rtez:
What are the benefits of using Magisk, or rooting device nowadays...
[Google Pixel 7] t-ryder:
Please not that discussion...
[Google Pixel 7] eegee-za:
Did this with the full OTA and it flashed to Slot B. After a few restarts it went back to Slot A saying corrupted. Tried forcing to Slot B and it restarts a few times then goes to Slot A. Slot A won't reboot (probably because it's on A13) so now I'm stuck not knowing what to do.

EDIT: got back into my phone by flashing the previous Factory image "panther-tq3a.230705.001-factory-b12ec778" that I had used.
[Google Pixel 7] t-ryder:
@badabing2003 maybe add an option/checkbox [ ▢ Android OS upgrade ] ... which flashes to both slots (so everybody knows what needs to be done when upgrading to a higher OS version via FI or OTA)?