yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] nags92:
Excellent tool @badabing2003 !

I see you've made it in python too !

Please correct me if i'm wrong in the following, haven't read your source code, just want to help :)

You should be using spawning a separate thread from the main thread for the execution of the flash script, this keeps the GUI from freezing. You can then call to send updates to the GUI from this thread, the console output etc you have in the main window.

To stop the user pressing other buttons you can also make a function that sets the buttons to disabled state as well as disable the windows close button. Same can be said for re-enabling them, if exception occurs the same can also be done.
[Google Pixel 6 Pro] banshee28:
So unfortunately I am back stuck in a bootloop!

I dont think this has anything to do with the tool, but hoping the Flasher can get me out of here, LOL.

So after successfully updating to June, I ended up filling up the storage taking videos! I then tried to delete files and it could not even delete them, at least not the larger ones. I connected to the computer and think I deleted several large video files successfully then rebooted. After that it never booted back up all the way. It boots to the logo, animation, then back to bootloader.

ADB commands work only for for 15 seconds or so.

I have tried to go into fastboot which works, and reflash the same June image both with and without the patched Magisk boot image, and each time it flashes fine but same bootloop.

Could this be due to the storage filling up, or something else?

I would really not want to wipe data, thats the very last resort!

Thought maybe I could delete cache to free up space but not sure if thats still possible with the latest Android?

Is it possible things have not fully deleted:

raven:/ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/dm-6 865280 862636 0 100% /
/dev/block/dm-7 241244 240512 0 100% /system_ext
/dev/block/dm-8 2721120 2712952 0 100% /product
/dev/block/dm-9 476768 475308 0 100% /vendor
/dev/block/dm-10 53848 53684 0 100% /vendor_dlkm
dev/block/dm-37 115621972 102581112 12909788 89% /data

Thanks for any advice...
[Google Pixel 6 Pro] badabing2003:
I'd welcome a pull request that does exactly that.

If I have to do it, it will wait until I have some time.
[Google Pixel 6 Pro] badabing2003:
Is it possible that when deleting files you accidentally deleted some important files?

But even that should be fixed with dirty flash of the full factory image.

See if you change the slot and flash, if it fixes the issue.

You can also try Android Flash tool.

Those partitions with 100% are ok,

I don't have /data on oriole, I have /dev/fuse

and of course tmpfs
[Google Pixel 6 Pro] banshee28:
Yea I only carefully deleted some large video files from the DCIM folder as I normally do. Never changed slot, will look into that option. Thanks!
[Google Pixel 6 Pro] banshee28:
So im back in fastboot, device shows up in Flasher, :

Device Active Slot: b
Device Mode f.b
Current Active Slot: [B]

I see both slot options, but only slot A is set and available to choose from.

Pretty sure this is the default and what it has been flashing before, or is this different now that I enabled advanced options?
[Google Pixel 6 Pro] badabing2003:
Your device is currently on slot B,

That is why you can only see Slot A active, because that selection is to switch the active slot.

So select it, and hit button next to it Set Active Slot, and it should change the active slot to A,

Then flash with keep data and see how it goes.
[Google Pixel 6 Pro] banshee28:
Yea tried that, flashed then got error in fastboot on boot up saying cant load android system, either try again or factory reset. Went back and tried with b slot, now same. I also tried the May image, with no magisk patching, same.

If I could get my data from fastboot and USB, I would just wipe all data, but I dont think that will work easily?
[Google Pixel 6 Pro] badabing2003:
can you provide a support.zip file, let me take a look
[Google Pixel 6 Pro] badabing2003:
@banshee28

it looks like first time around flashing process could not extract product.img (perhaps not enough disk space? this is purely Google's flashing process)

extracting product.img (2691 MB) to disk...ziparchive W 06-08 13:13:38 4604 3600] Zip: unable to truncate file to 2822742668: File too large

Then it was able to

extracting product.img (2691 MB) to disk... took 19.223s

Then again it was able to

extracting product.img (2691 MB) to disk... took 29.118s

All of the above are with stock boot.img

Then with magisk_patched

extracting product.img (2691 MB) to disk... took 18.785s

Stock again

extracting product.img (2691 MB) to disk... took 18.014s

Then you switched to slot a

and flashed may

but that flashing had this error

Sending 'vendor_boot_b' (65536 KB) OKAY [ 1.476s]
Writing 'vendor_boot_b' OKAY [ 0.094s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for REDACTED >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
rebooting to bootloader ...
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s

Try to flash the may version again to slot a and slot b

you can even try with the both slots option in PixelFlasher.

Since you're mostly trying to flash stock

give Android flash tool a try, of course don't choose wipe

Android Flash Tool

flash.android.com
[Google Pixel 6 Pro] banshee28:
I think I really messed this up by filling up the disk!

It failed this time trying to resize the partition: Failed Remote "not enough space to resize partition".

If only I could del some files in fastboot everything may work fine??
[Google Pixel 6 Pro] badabing2003:
Yeah I see

Resizing 'vendor_b' FAILED (remote: 'Not enough space to resize partition')

Did you try Android flash tool?
[Google Pixel 6 Pro] banshee28:
Forgot to post that, yep. I did and it did the same. I flashed it with June first and it then booted and got to the animation, which was further than the previous flash but still failed and rebooted. Only thing I have not tried yet is data wipe.
[Google Pixel 6 Pro] badabing2003:
Sorry to hear, I can understand not wanting to wipe specially if you have no backups.

I know it probably won't help, but you have nothing to lose by trying.

Try a different USB cable and plugged to a different port.
[Google Pixel 6 Pro] Thebear j koss:
What device do you have? Don't you back up to Google One or backup your device daily? If so, just wipe and restore last backup. All should be good. I always make sure to backup before flashing an update.
[Google Pixel 6 Pro] banshee28:
P6P, I don't backup online but i did backup all photos a week ago so not a huge deal, just a few recent ones may be missing, plus setting up phone again. If I have to, will try that probably tomorrow.

Yea prob need to look into a backup next time before updating. First time with a rooted phone in a while so gotta be ready for when these things happen I guess, lol.
[Google Pixel 6 Pro] Lycidias:
Doesn't work either as normal user 😅 can't save to location
[Google Pixel 6 Pro] Thebear j koss:
Yeah, if you have your accounts syncing, everything should be backing up. You may lose some files, apps, pics, and videos but if your Google account is syncing then calls, messages, contacts, and other stuff should be saved. After wiping and re flashing when you set up do it from another device the last backup or sync made should be available instead of starting completely fresh. And personally I always save stuff weekly on Mega like pics and vids. That way they are always available and they don't eat space. Not sure why you have no space, do you have 2 ROMs running, 1 on A and 1 on B? Because even with 60GB of music and 15 GB of pics and music I still have 180 GB of storage available. Do you download every porn Vid available or something? 😂
[Google Pixel 6 Pro] badabing2003:
This is so weird,

Please navigate to

%APPDATA% folder, in the there should be PixelFlasher folder, can you zip that up and share?
[Google Pixel 6 Pro] niko26:
Sorry, but calling the built in "sync" function a backup is blasphemy ;) Android built in backups suck hard time. Really.
[Google Pixel 6 Pro] badabing2003:
I wish there was nandroid backup possibility, too bad there is no compatible twrp.

I have yet to find the perfect backup solution.
[Google Pixel 6 Pro] niko26:
SwiftBackup is okay for me. But still.. There's a lot of manual work involved.

This is where iPhones really shine. Apple's backup and recovery simply works. :(
[Google Pixel 6 Pro] banshee28:
So, I went back and set to slot A and only flashed (June) to that slot. Slot b was getting the "failed remote not enough space to resize partition errors. When I only set and flashed on A, it no longer got any of those errors and flashed without errors, although it still eventually boot-loops!

However, I am now able to at least get to the animation and adb is working for 10-15 seconds or so!! I tried to disable magisk during this time, but not sure if thats relevant at this stage?

Since I have adb for a few seconds, is there anything I can do to try to recover this or enter safemode?
[Google Pixel 6 Pro] badabing2003:
If you are flashing stock with no patched boot.img, it's not magisk that's causing the bootloop, so no point in trying to disable magisk.
[Google Pixel 6 Pro] badabing2003:
Update:

June 12,2022 v3.3.4 release

Bug fix on MacOS / Linux

Improved notice message about Fastboot process.
[Google Pixel 6 Pro] badabing2003:
Update:

June 26, 2022 v3.3.5 release

Fix Lock / Unlock bootloader buttons being reversed.
[Google Pixel 6 Pro] znel52:
Just wanted to say thanks for this awesome tool! Makes updating monthly and keeping root a breeze
[Google Pixel 6 Pro] Blade22222:
Yeah it's the best thing since sliced bread! Love this tool.
[Google Pixel 6 Pro] badabing2003:
lol @Blade22222
[Google Pixel 6 Pro] Thebear j koss:
Worked perfectly on July update. In fact this is easier/better than Google's own flash tool on their developer's site. 👍🐻
[Google Pixel 6 Pro] badabing2003:
New release:

July 18, 2022 v3.4.0 release

Improvements to the boot extraction / categorization.

Live boot option directly from the selected boot.img UI, even though it was possible to live boot previously through the advanced menu, it is now super easy to select a boot.img (patched or otherwise) and Live boot to that image with a click of a button.

Added warning message in the splash screen and the help about menu, to inform users not to fall for opportunists who are claiming to be the developer of PixelFlasher with a donate button next to the download link. Reminder to all, this program will always be free, ad free, donation free; you should not be solicited for any form of payment.
[Google Pixel 6 Pro] Annil:
July update done with latest alpha magisk (C97d1044) without issues on Pixel 6 Pro and Pixel 6.

Thanks for this nice tool :)
[Google Pixel 6 Pro] rester555:
This tool looks awesome. I haven't used it yet, but I will be using it in the future. Will you have to use disable verity and verification when going to Android 13 and obtaining root? Is that required for loading the Android 13 images and rooting? Or is that not required with the newest Magisk 25.2 build?

UPDATE: I used the tool to flash with the factory image and patched boot image with Magisk 25201 and I got a bootloop. Most likely it was due to a module. I should have used the disable modules command, but didn't do that. I had systemless hosts, faceunlock workaround with lsposed, 2.3.1 safetynetfix, and tether unlock modules. I don't think I turned them off before updating to get into the bootloop. I ended up reflashing the factory image first with the tool. Then updated magisk after and that worked fine since it wiped out the modules on the factory image flash first.

Thanks for the tool!
[Google Pixel 6 Pro] badabing2003:
Thanks for the update,

I have not looked into Android 13 much so I wouldn't be a good person to answer that, I would expect that Magisk would take care of it, but then again I haven't read up on it yet.

I saw this thread,

As for disabling magisk modules, In the future I suggest you use the Magisk Manager Feature in PixelFlasher instead of Disable Modules features, the disable modules is more for recovery during bootloop if the device is adb accessible briefly while looping.

The Magisk Manager feature provides a UI for you to selectively disable modules.

I never had to disable Systemless Host or Safetynetfix, the others I cannot comment on.
[Google Pixel 6 Pro] Thebear j koss:
Past 2 updates I have flashed stock firmware using this tool with all my modules enabled and haven't had any issues. This includes systemless, safetynet, lsposed, aosp mods, substratum, repainter, emoji replacer. Just reporting from Pixel 6 pro.
[Google Pixel 6 Pro] rester555:
Good to know... Will try that.
[Google Pixel 6 Pro] badabing2003:
Thanks for the info, really good to know.

For clarity, I assume when you say stock firmware, you're applying stock firmware with patched boot.img through PixelFlasher, otherwise the Magisk Modules would not be a factor, right?
[Google Pixel 6 Pro] Thebear j koss:
Correct. I patched boot image with the tool and only flashed the updated magisk boot img with the updated firmware.
[Google Pixel 6 Pro] Spookymyo:
Great tool!

One question. Is this better than the standard method for taking OTA's? Uninstalling magisk image, apply ota (without rebooting), reinstall magisk, reboot. This has always worked for me. Root is preserved.

Method I use: https://topjohnwu.github.io/Magisk/...bypassing any possible post-OTA verifications.
[Google Pixel 6 Pro] badabing2003:
Thanks,

If your method is working, no need to change, and you don't need a PC to apply your method.

I personally prefer the full factory method over the OTA, but that is a personal choice, I know a lot of people run into issues with OTA, so factory method is less error prone and with PixelFlasher it is just couple of clicks.

You have the tools at your disposal, hence you have multiple options, choose whatever you feel comfortable / safe with.
[Google Pixel 6 Pro] niko26:
That's good for you :-) In my entire Pixel life this has only worked like once or twice :-(
[Google Pixel 6 Pro] minhgi:
direct upgrade to A13 from A12 with custom kernel/modules (Shamika, universal safetynet fix, and zram swap manger) enabled went flawless. Fyi. this with A13 normal patched kernel
[Google Pixel 6 Pro] wgrant:
Wish I could say the same. Mine had all kinds of errors just now and I'm about to sort through it. Currently sitting in fastbootd after several error messages and it finishing out.

https://easyupload.io/diiap1 (sanitized support zip)

EDIT: Stupid old files... picked the April build when I was picking the files to patch and flash. Seeing if I can get back in to try again. Ugh.... Always clean up before flashing the newest build.

EDIT 2: Had to use the actual flash option for the pixel firmware provided by Google. Chose not wipe data and it flashed, booted back to system and data all intact. Silly mistake on my part but wanted to post my fix for others if they run in to it. I did test flashing with this tool again (twice) with no success before reverting to Google.
[Google Pixel 6 Pro] badabing2003:
It looks like you have a bad connection, bad usb cable perhaps? or bad usb port?

Sending sparse 'product_a' 6/11 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
< waiting for REDACTED >
Rebooting into bootloader FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sleeping 5-10 seconds ...
flashing pf_boot ...
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 67108864).
Sending 'boot' (65536 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
rebooting to system ...
Rebooting FAILED (Write to device failed (no link))
fastboot: error: Command failed
[Google Pixel 6 Pro] Lycidias:
Is the "flash to both slots" option working now?

I've red A13 need to be flashed to both slots because of a bootloader upgrade and this could lead to a permanent brick.

Just asking because I had issues reported here in the past, when using flash to both slots
[Google Pixel 6 Pro] minhgi:
IDK. I must have gotten lucky. This my third firmware upgrades using flasher without any problem. I make a backup using swift and pull the backup out the phone incase something went wrong. Had gone through few incidents where the upgrade complete mess up and don't have backup to return too.
[Google Pixel 6 Pro] badabing2003:
I believe whether `flash to both slots` works or not is a function of device state.

From PixelFlasher perspective, when this option is selected, the additional fastboot option `--slot all`

is appended to the fastboot command, that is all and nothing else.

I moved to A13 without using `flash to both slots` and did not have any issues.
[Google Pixel 6 Pro] wgrant:
I appreciate you checking the log. Connection is fine, never lost the phone at all. My issue was discovered immediately after I posted. I had selected the April firmware instead of the August one. Caused myself bootloops. The Google website flasher got me squared away. Not blaming the tool at all, it was completely user error.
[Google Pixel 6 Pro] badabing2003:
No worries, I didn't take it as criticism against the tool.

Still this message is usually displayed when the connection is dropped, typically due to bad connection,

FAILED (Write to device failed (no link))

In any case happy to hear that it's all resolved.
[Google Pixel 6 Pro] mko000:
What could be the reason for PixelFlasher not finding Magisk on my phone? It's NOT hidden.

Pixel 6 Pro, Magisk 25.2, PixelFlasher 3.4.0.0

Deleting boot.img from phone in /storage/emulated/0/Download ...
Making sure boot.img is not on the phone in /storage/emulated/0/Download ...
Deleting magisk_patched.img from phone in /storage/emulated/0/Download ...
Making sure magisk_patched.img is not on the phone in /storage/emulated/0/Download ...
Transfering boot.img to the phone in /storage/emulated/0/Download ...
C:\Users\mko\AppData\Roaming\PixelFlasher\boot_images\96cc5fa24586345d91d9797399a8c6e7\boot.img: 1 file pushed, 0 skipped. 152.6 MB/s (67108864 bytes in 0.419s)

Making sure boot.img is found on the phone in /storage/emulated/0/Download ...
Magisk Tools not found on the phone
Looking for Magisk app ...
Unable to find magisk on the phone, perhaps it is hidden?

Happy to debug. Thanks in advance!
[Google Pixel 6 Pro] badabing2003:
Check the main thread linked in op, basic usage point 2, see if that is the issue.
[Google Pixel 6 Pro] mko000:
Thank you very much for your quick answer, that was indeed the problem.

If I remember correctly, I allowed it the first time I used PixelFlasher, but only for that one time. It seemed too dangerous to me, to just keep "shell" with superuser permissions. I thought it would request the permission again the next time, but I guess not.
[Google Pixel 6 Pro] banshee28:
So I'm back! I finally decided to flash and wipe ALL data since I prev only dirty flashed from 12 to 13 Beta. Now I am trying to wipe all data and flash the latest factory image A13 to both slots. The phone will reboot to fastboot but hangs and gets error saying "unable to detect the device". I dont think this is due to Flasher, since Android flash tool does the same. However any idea what I can do to fix this?

So far I have only pressed start when it goes to fastboot and hangs. I can try cli but would like to use tool if possible.

It shows active slot is b. I tried to change to a and not sure if that worked, it still shows b after reboot?
[Google Pixel 6 Pro] badabing2003:
Perhaps slot a is corrupt and it goes back to b.

Try flashing one spot at a time.

First fash current and when it fully done, switch to the next slot, and don't try to reboot to system, stay in reactivity and flash.

Support.zip files would definitely help.
[Google Pixel 6 Pro] badabing2003:
Not sure what went on, perhaps magisk remembered your decision, this is not something I can control from PixelFlasher, especially if PixelFlasher can not get root access.
[Google Pixel 6 Pro] banshee28:
So current active slot is b, and I unchecked Flash on both slots, and it does the same. Perhaps I should try going back to A12? I know thats a problem too, lol.
[Google Pixel 6 Pro] Lughnasadh:
If you do not have the A13 bootloader on both slots, absolutely DO NOT go back to A12 unless you need another paperweight. And even if you do have the A13 bootloader on both slots, I still wouldn't go back to A12.
[Google Pixel 6 Pro] banshee28:
Would me being on A13 Beta have anything to do with this?
[Google Pixel 6 Pro] Lughnasadh:
Wait...are you still on A13 Beta? Still, there's no reason to go back to A12.
[Google Pixel 6] badabing2003:
View attachment 5567251

This is the support thread of PixelFlasher

(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).

Note: This thread is meant for issues and problems faced in Google Pixel 6 devices, generic issues that are device agnostic should be discussed in the main thread.

For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.

IMPORTANT:

Please do not ask questions the answers of which are already stated in the OP.

I will simply ignore the request, as I'm fed up of referring people to the post that has the answers.

Troubleshooting:

If you need support or assistance, please generate and provide a support file from within PixelFlasher.

You can hit that big Support button on the main screen, or select it from the Help menu.

The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

And no, a screenshot of the console or an excerpt from the console, does not make a support file.

Clearly state the issue you're encountering, what actions did you take, and what outcome you observed, and what outcome you had expected.

Do NOT modify the support file, keep it intact.

See this post.

Generate Sanitized support.zip file (File Menu) and submit that with your report.

If your anti-virus program is telling you that PixelFlasher is a malware, or you are concerned in any way, please check this post.
[Google Pixel 6] dilruk:
I'm getting this on Pixel 6. Any idea what am I doing wrong?
[Google Pixel 6] badabing2003:
What is your Android platform tools version?

Also can you please share PixelFlasher log? Or everything displayed in the console when you encountered the error.

You should redact your device ID for privacy.
[Google Pixel 6] dilruk:
==============================================================================

Preparing Package

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

Found a previous package oriole-sp2a.220305.013.a3 deleting ...

Found Bundled 7zip.

zip/unzip operations will be faster

Unzipping Image: D:\Android\Devices\oriole\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\onedrive\Desktop ...

Unzip time1: 42.51156783103943

Unzipped into oriole-sp2a.220305.013.a3 folder.

Extracting boot.img from image-oriole-sp2a.220305.013.a3.zip ...

Unzip time2: 0.8888261318206787

Deleting boot.img from phone in /storage/emulated/0/Download ...

Making sure boot.img is not on the phone in /storage/emulated/0/Download ...

Deleting magisk_patched.img from phone in /storage/emulated/0/Download ...

Making sure magisk_patched.img is not on the phone in /storage/emulated/0/Download ...

Transfering boot.img to the phone in /storage/emulated/0/Download ...

ERROR: Encountered an error.

adb.exe: unrecognized option '-'

Aborting ...

There you go...
[Google Pixel 6] dilruk:
From what I see, it fails when trying to copy the boot.img to the phone. Also, how do I see the log file? The one I see is empty