yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6a] badabing2003:
Thanks, looks to be the same issue :(

By the way I don't remember if I asked this, have you tried building PF yourself, the steps are in Github.

That would build against your system libraries.
[Google Pixel 6a] badabing2003:
New Release:

June 16, 2003 v5.3.1.2 release

Set Active slot now automatically reboots to system after setting the slot, unless "No Reboot" option is selected.

Update Ubuntu 20.04 build to be aligned to the same methods that Ubuntu 22.04 build uses.

Improve confidence value calculation when comparing compressed sha1 against normal sha1 to account for shift.

Do not abort when the sha1 comparison confidence value is low, leave the choice to the user.

Update Windows builds (both) as wxPython wheel path changed, rely on a more persistent URL instead.
[Google Pixel 6a] G5-User7080:
Maybe I'm blind but is there a button to clean up the folders where images are extracted to and processed?

I usually do that by hand after every flash so I don't get confused with which version was which the next time I use it.

If that's not a thing already would that be an idea to add that kind of thing?
[Google Pixel 6a] badabing2003:
No that's not a thing, and I probably wouldn't be adding any to make it a thing.

There is no confusion or ambiguity with Pixel firmwares, both OTA and full firmware, the date is in the filename, and considering that PF expects you to NOT unpack, as it manages the unpacking, if you want to delete it, you can always manually delete it.

PF once it unpacks, it manages, it keeps references to boot, their sha1, the related patched images ... and within PF everything is clear when you select something, it tell you all the details about it.

If you want to delete stuff to save on some disk space, although I don't see how that would be a thing considering the abundance of disk, then feel free to delete files that you think are consuming too much space.

On my system, I have all the images I ever flashed, along with all the different variations of the patches I created, and this for each device I flash or tested for, it even includes firmware for which I don't have the phones and had to process to investigate reported issues, and I don't recall every getting confused.

Pay attention to the dialogs, if it warns you that you are flashing a firmware that is not for your phone model, read it and stop there if that is the case.
[Google Pixel 6a] badabing2003:
New Release:

June 21, 2023 v5.3.2.0 release

Added support for Pixel tablet (tangorpro).

For future devices, fixed a bug to auto detect init_boot partition and flash init_boot instead of boot even if the device is newer than the PixelFlasher and is not in PixelFlasher's list.

Disable Patch buttons if device is not in adb mode.

Reboot to system after lock / unlock bootloader if No Reboot option is not selected.

Increase sleep after reboots to various modes to assure that slow devices have time to be detected.

Updated Readme and screenshots.

Minor improvements and bug fixes.
[Google Pixel 6a] badabing2003:
New Release:

June 23, 2023 v5.3.3.0 release

#79 Bug-fix: Package Manager column stays unsorted when filtered.

Warn users that extract the contents of firmware and use the image inside as firmware, which is no good.

Warn users of Android Platform-Tools 34.0.3 about potential issues and suggest using 33.0.3

Package manager bug fixes and improvements.
[Google Pixel 6a] badabing2003:
New Release:

July 03, 2023 v5.4.0.0 release

Add Pixel Fold (Felix)

Add sorting capability to boot list.

Add warning about Magisk a8c4a33e:26103

Improved auto-resize of boot columns.

Improved internal DB management.

Handle beta or similar words in the firmware name to not trigger hardware mismatch warning.

Improved tracking the origin of a patched image.

Display Kernel version as part of device details

Refresh package manager list when packages are updated to reflect the changes.

Miscellaneous other improvements.

Update Readme.
[Google Pixel 6a] G5-User7080:
very weird,.. had the same thing happening again, first sideload went just fine, trying to repeat it to flash the other slot as well and it fails after initiating the sideload command, don't think it's related to PF since I had the same thing happen doing it manually, but you might be able to figure something out from the logs, idk

weird af.. tried a different usb port, and I tried with a script that pulls file from my phone, didnt work, but when I re-ran it it magically worked.....

adb is always on and always got picked up in PF and always showed up in adb devices, but it seems like that has nothing to do with a successfull connection

true enough.. after it for some reason magically worked by just.. trying again eventually with the adb pull command, now also sideloading works just fine........... idek anymore, wtf, as if normal bugs in platform tools werent bad enough
[Google Pixel 6a] G5-User7080:
ookay.. one more, for some reason patching the boot img and then doing a live boot didnt work from pixelflasher

it patched the img, it pulled it, I selected it, it displayed it and it did a live boot, but after that I still didnt have root.

When I did it manually (push PF's original boot.img to device, go in magisk, patch, and pull it and then do fastboot boot magisk_patched.img) it worked.

logs should show that I was trying to live boot the patched image but that my device didnt have root after re-scanning on reboot.
[Google Pixel 6a] badabing2003:
Live boot did not work because it couldn't detect your device in bootloader mode to flash it.

2023-07-06 10:36:19 User Pressed Ok.
Rebooting device REDACTED to bootloader ...
Waiting 10 seconds ...
2023-07-06 10:36:36 No Device is selected!

2023-07-06 10:36:36 ERROR: Unable to detect the device.
You can try scanning for devices and selecting your device (it should be in bootloader mode).
and then press the same Live button again.

Your issues point the finger towards communication issue.

It could be any of the following

- The USB drivers (make sure you updated to the latest, there is a link for it in the help menu)

- The USB port, usb2 ports are better suited, try different ports.

- The cable

- The USB connection on the phone

if you have sounds enabled each time a usb device connects / disconnects / errors to your PC it would be easier to troubleshoot and zero in on the culprit.

The fact that adb pull script had similar faith strongly suggest a communication issue.
[Google Pixel 6a] G5-User7080:
yea, I think so too, but it is weird that those issues only happen after going through sideload the first time I feel like.. at least normally they dont happen.. I connect my phone, transfer files and it works, so idek how to reproduce it

I'll check for updated adb drivers, thx for the tip, only was aware of platform tools needing updates (well not for now anyway since the newest version is still not fixed)

Idrk why it wouldnt get a connection in bootloader,.. aka fastboot couldnt find my device?

that's quiet weird,.. considering that it worked doing it manually on the first try.. but again, its just so random I can't reproduce those issues at all to test them -_-
[Google Pixel 6a] badabing2003:
New Release:

July 13, 2023 v5.5.0.0 release

Added a patch method Other Magisk App to be able to select any Magisk apk and use it to create a patch without installing Magisk, handy when a patch needs to be created with an older version of Magisk (in case the current version has issues) and Magisk daemon gets in the way and replaces the older version with a stub.

UI improvements

Added Kill Application in Package Manager.

Added Clear Application Data in Package Manager.

Now that Full OTA flashing is the preferred method, added a direct link to the device's full OTA download page from Google.

While flashing, disable the Flash Pixel Phone button to avoid accidental clicking.

Improved root detection.

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

July 14, 2023 v5.5.1.0 release

Bug fix #85 Can't enable/disable Advanced option in v5.5.0

A little improvement #84 UI elements not optimized for monitors with low screen resolution
[Google Pixel 6a] badabing2003:
New Release:

July 16, 2023 v5.5.1.1 release

#84, further UI improvements for smaller screens.

Better dark mode handling for MacOS and Linux.

#86, improved handling of space characters in paths.
[Google Pixel 6a] penpex:
Hello,

I was on May's update on my P6A, and I received a notification that I got the June update on OTA, which is weird because I always had to download it myself manually since I rooted it in November, and each month I used PF to update...(I wonder how it happened...).

I inadvertently restarted my phone which finished the install of the June OTA...

Unfortunately I noticed that I had lost root.

So I started the process to root my phone again (following this thread).

So I:

downloaded the factory image from June (since I checked I was indeed on June in System info),

extracted the boot.img file,

sent it over my phone, patched with Magisk,

sent the patched image back on my computer,

rebooted via ADB to bootloader (which was unlocked already of course),

sent the fastboot flash boot magisk_patched.img command,

sent the fastboot reboot command.

When it rebooted I'm on recovery and it says

blah blah

13/T2QA.230505.002/9891397

blah blah

Cannot load Android system blah blah

Try again

Factory data reset

Is there a way for me via PF to save my data by reflashing an image, and not have to factory reset ?

Also I don't understand why it says that I'm on the May update ? Is it what messed up eveything ? How did it happen ?
[Google Pixel 6a] badabing2003:
I can't comment why you would see May instead of June, but how are you seeing that if you can't boot?

To fix the situation, I would do the following.

1- Download July full OTA

2- Select it in PF and process

3- Select the boot it extracts and click on the Patch button, this will create a patch and pull it to the PC, now you would see two entries in the boot list, the stock boot and the patched boot (boot here is a generic term, it could be boot.img or init_boot.img depending on the device, PF automatically knows which it needs to be)

4- Select the stock boot (not the patched one) and hit the Flash Pixel Phone button (not Flash Boot)

When completed, you should be on July version but not rooted.

Select the patched boot and hit the "Flash Boot" button (not Flash Pixel Phone)

The reason I suggested to first flash the stock is to make sure you can boot your device, in case a bad/incompatible Magisk module is causing a bootloop.
[Google Pixel 6a] penpex:
Hello,

Thank you for the answer.

Unfortunately in the meantime, I tried to turn off my phone after playing a bit going in and out of fastboot and bootlader with adb, and so I just turned it off while on bootloader by selecting the option with the volume buttons.

It immediately rebooted and told me the phone is corrupt!

I can't seem to be able to do anything at all right now, since it is not even recognized by adb anymore. I can just press Power to continue, which brings me to bootloader but then it just brings me to the Google logo and is stuck there forever.

I really don't understand what happened. In retrospect I should just have let it connected to my PC and never tried to turn it off...

Is there a way to save it now ?
[Google Pixel 6a] penpex:
In the confusion, I forgot to try fastboot, and it still works, PF recognizes the phone then.

Should I proceed as you said ?
[Google Pixel 6a] penpex:
Actually, since I can only get fastboot and not adb, PF cannot procedd at the patch stage:

Is there anything I can do ? adb devices lists nothing.

pixelrepair.withgoogle.com and flash.android.com seem to see the device, but I'm not sure what their next requirements are, as I have never tried them...
[Google Pixel 6a] badabing2003:
skip the patching, just process and flash ota, when it boots to system then you can do the patch
[Google Pixel 6a] penpex:
Thanks. I processed and clicked 'Flash Pixel Phone' 10 mins ago, and now PF is Not Responding in Task Manager and its window is faded. Not sure sure if this is normal behavior?

The last thing I see written in the log window is (approximately since I can't copy paste):

The phone in the meantime keeps getting turned off and then on every 30 seconds, ending up on the default 'Your device is corrupt' screen.
[Google Pixel 6a] badabing2003:
Ok no worries,

It sounds like the phone is not able to get into recovery mode.

In that case,

download the July Factory image

Process, and then select boot.

In PF configuration enable advanced options.

then select Keep Data, and Flash both slots.

Flash Pixel Phone
[Google Pixel 6a] penpex:
Thank you again for the answer.

I followed the procedure, and it didn't work completely.

PF noted no errors, and finished with :

But my phone is now stuck in a bootloop, in the sense that before it was stuck on the Google logo, but now after a bit it goes back to the "bootloader is unlocked" warning screen, and then again to the Google logo etc.

Is it better? What can I try now ?

EDIT: if it is of any help, I noticed that on the fastboot screen it is written boot slot: a, whereas it was b before.
[Google Pixel 6a] badabing2003:
It's time you generate a support file from PF and post
[Google Pixel 6a] badabing2003:
Sorry, I'm not sure how I missed this.

It sounds to me that perhaps you have a flaky cable or USB port.
[Google Pixel 6a] penpex:
Sure, here it is, I hope it helps!
[Google Pixel 6a] penpex:
If it helps, I noticed that I seem to be unable to get into recovery mode from fastboot.

Selecting it and pressing Power just brings up the orange "The bootloder is unlocked menu" for a few seconds and then the Google logo again (and then it loops on these two again, so it's like I just booted the phone).

Also I don't know if you saw the edit I had done in my second to last post (since it wasn't in your quote):

After flashing factory to both slots, I noticed that on the fastboot screen it is written boot slot: a, whereas it was b before. But maybe you could see that from the support file I posted.
[Google Pixel 6a] badabing2003:
I looked at your support file.

You're using an older version of PF (PixelFlasher 5.2.0.2), I suggest you update to the latest (5.5.1.1).

Please remove your old Platform tools from your system path

Found Android Platform Tools in C:\Users\REDACTED\AppData\Local\Android\Sdk\platform-tools
2023-07-17 02:11:08 ERROR: Detected older Android Platform Tools version 31.0.2-7242960
2023-07-17 02:11:11 User accepted older version 31.0.2-7242960 of Android platform tools.
SDK Version: 31.0.2-7242960

You selected and flashed a patched boot, please select the stock boot first, and hit "Flash Boot" (not "Flash Pixel Phone") to switch to stock, there could be Magisk modules issues, let's make sure you get system booted properly first

Path: C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4\aa2cdd2619d4f616d116a606c080f942f7726100\magisk_patched_c16f2c42.img

It is normal that the slot gets changed when you flash to both slots.

Let's get your system working properly before looking into recovery boot options.
[Google Pixel 6a] penpex:
Thank you for your answer.

I did what you said, and now after the orange "the bootloader is unlocked" screen and the Google logo, I have the Android lying on the floor with its belly open and it's written "No command" (It's the Rescue menu right?).

I attached a support file if you need it.
[Google Pixel 6a] penpex:
Actually, after retrying to boot the phone for a 3rd time, it booted somehow!
[Google Pixel 6a] badabing2003:
Android on the side is the recovery mode.

So you're good now?

It boots normal?

You can try flashing the patch.

Just select the patched boot and hit the flash boot button.

If it does not boot find, that would suggest that a bad module is getting in the way, we'll deal with that if that is the case.

You can flash back the stock boot and be up again.
[Google Pixel 6a] penpex:
So yes it boots normally, and I'm on the July update. No Root of course.

I was going to try flashing the patch, but when I processed the July OTA, it gave me a boot.img, but I cannot click on patch after selecting that one (Patch is grayed out). Am I missing something here?

Here is PF's console after selecting that boot.img:

Selected Boot:
File: boot.img
Path: C:\Users\my_username\AppData\Roaming\PixelFlasher\boot_images4\a46d864ae240141953dc6f413758a29238de1a33\boot.img
SHA1: a46d864ae240141953dc6f413758a29238de1a33
Patched: False
Date: 2023-07-17 00:59:27
Firmware Fingerprint: bluejay-ota-tq3a.230705.001
Firmware: C:\Users\my_username\Downloads\bluejay-ota-tq3a.230705.001-1c9bce8d.zip
Type: firmware

and Patch is grayed out.
[Google Pixel 6a] badabing2003:
Make sure you select your device and the device is in adb mode
[Google Pixel 6a] penpex:
Indeed, it probably wasn't, now that it is in adb mode, I have this option.

I will try in a couple days, as I can't afford something to happen to my phone for the next two days.

So to be clear, I will:

1) Patch the boot that came from processing the OTA update

2) Select it, and then click 'Flash Boot'

3) If my phone fails to boot, I just select the stock boot and click 'Flash Boot', and that should bring my phone back to a normal state (but no root obviously)?

Another question too: is there a way to know what I have on both slots right now? Because after everything I did, I'm unsure...
[Google Pixel 6a] badabing2003:
Exactly

If it doesn't boot, we'll cross that bridge when we get there, as there is a solution.

Technically yes, but not easily, you would need to switch slots and inspect.

Easier to flash OTA again and be certain it's a perfect match.

Considering that you've done it one, all you have to do is click on the "Flash Pixel Phone" button

and it will write to the other slot.
[Google Pixel 6a] penpex:
Thanks, I will report in a few days then.

Also, thinking ahead, since I think it was weird than an OTA got downloaded and installed silently on my phone (right?), is there a way to prevent this for sure ?
[Google Pixel 6a] badabing2003:
No guaranteed method, but for the very least you should disable "Automatic system updates" in Developer Options
[Google Pixel 6a] penpex:
Reporting, as promised.

Flashing the patched boot worked, and I'm rooted again!

Thanks for all the support throughout this.

One last thing : in the support file, there are usenames that aren't sanitized . In the first one I provided, you can find paths that sometimes are sanitized and somethimes not, even on the same line. See lines 36, 40, and 52 for examples where usernames appear.

Maybe that can be fixed ? I have an alias as my username so I don't care too much but others might.
[Google Pixel 6a] badabing2003:
I'm sorry you'd have to be more specific than that.

I don't see anything wrong on line 36, 40, 52

You have to tell me which file you're looking at as there are many files.
[Google Pixel 6a] penpex:
Sorry, I totally forgot to say in was in the PixelFlasher4.db file.
[Google Pixel 6a] badabing2003:
Are you looking at the file in generated support.zip or are you looking at the file in your filesystem?

I checked the db file in support_2023-07-17_02-42-37.zip your provided, everything looks right.
[Google Pixel 6a] penpex:
I am looking at that file in the support.zip file, and I am not sure which tool you are using to view that file, but using Notepad++ for instance you can see in that file, that at the lines I mentioned, there is a mix of REDACTED and a username in the paths.

See pic below for proof, for line 36, where there are 2 instances of a username instead of REDACTED.
[Google Pixel 6a] badabing2003:
Thanks,

I see now, you're binary checking the file.

This will be fixed in the next release.

When I redact the username, sqlite uses write-ahead logging (WAL) mechanism to improve concurrency, basically writing before applying to the db, although the old content is not visible in the db, you were able to see it in the binary.

I'll take proper measures to wipe this content before saving the file.

Thanks for bringing it up.
[Google Pixel 6a] mike.s:
Or just change your user name to REDACTED. :)
[Google Pixel 6a] 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 6a] 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 6a] 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 6a] 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 6a] penpex:
Happy to report that a double Full OTA flash with August's update worked perfectly as expected with PixelFlasher (the last release).

Thanks for your work!
[Google Pixel 6a] 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.
[Razer Phone Questions & Answers] SurvivalHorror:
Razer Phone 1 . Does anyone know where the "test point" contacts are on the board to switch to EDL mode ?

RP1 is not detected on the PC in any way - it hangs on the logo.

The charging port is working
[Magisk] Elliottgg:
how to root android subsystem on chroebook via magisk
[OnePlus 9] MsuatafaKhatab:
Hi All

i switched from Oxgen to Color os , but didn't find preferred network mode and the network always on 5 G

Thanks
[Touch GSM General] fredfrop:
Hi

How can I re-invoke touchflo? it stopped working a while ago, everything else on my elf gsm is working very well, just no touchflo. I wasn't that bothered about it being missing for a while but it's starting to bother me now.

What files should I have to make touchflo work, so I can check they are all there?

Is there any other info I should give to help get the right answer? I've made a search for existing threads but can't see anything.

Thanks

Dan