yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] wheelbarrel:
This is what I got

SDK Version: 33.0.1-8253317

(PixelFlasher:1104258): Gtk-WARNING **: 16:36:02.543: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Flat-Remix-Blue-Dark/actions/16/image-missing.svg: Unable to load image-loading module: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /lib/x86_64-linux-gnu/librsvg-2.so.2: undefined symbol: pango_attr_overline_new (gdk-pixbuf-error-quark, 5)
Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Flat-Remix-Blue-Dark/actions/16/image-missing.svg: Unable to load image-loading module: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /lib/x86_64-linux-gnu/librsvg-2.so.2: undefined symbol: pango_attr_overline_new (gdk-pixbuf-error-quark, 5)
[Google Pixel 6] wheelbarrel:
Nice work!

It seems you have the same attitude :cool:
[Google Pixel 6] Bartx96:
Somebody help me ? i have a problem

Preparing Package

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

Found Bundled 7zip.

zip/unzip operations will be faster

Unzipping Image: C:\Users\Bartek\Downloads\oriole-ota-sp2a.220405.004-f019343f.zip into D:\PixelFlasher (2) ...

debug: "C:\Users\Bartek\AppData\Local\Temp\_MEI166722\bin\7z.exe" x -bd -y "C:\Users\Bartek\Downloads\oriole-ota-sp2a.220405.004-f019343f.zip"

Unzip time1: 7.5428197383880615

ERROR: Unzipped folder oriole-ota not found.

debug: returncode is: 0

debug: stdout is:

7-Zip 21.07 (x64) : Copyright (c) 1999-2021 Igor Pavlov : 2021-12-26

Scanning the drive for archives:

1 file, 2010717236 bytes (1918 MiB)

Extracting archive: C:\Users\Bartek\Downloads\oriole-ota-sp2a.220405.004-f019343f.zip

--

Path = C:\Users\Bartek\Downloads\oriole-ota-sp2a.220405.004-f019343f.zip

Type = zip

Physical Size = 2010717236

Comment = signed by SignApk

Everything is Ok

Files: 7

Size: 2010714635

Compressed: 2010717236

debug: stderr is:

Disabling bundled 7zip ...

Trying unzip again with python libraries ...

Unzip time1.1: 8.621312379837036

ERROR: Unzipped folder oriole-ota not found again.

Aborting ...
[Google Pixel 6] badabing2003:
It seems that you have selected OTA file and not a factory image file.

You need to select factory image.
[Google Pixel 6] Bartx96:
But I download rar from official google factory image
[Google Pixel 6] badabing2003:
Google publishing RAR files?

are you certain of your sources?

This is the official link.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 6] badabing2003:
Try this

View attachment 5590137
[Google Pixel 6] wheelbarrel:
Nice Work!!

PixelFlasher 2.2.2.0 started on 2022-04-16 18:58:56

No previous flashable package is found for the firmware:
/Documents/pixel/firmware/oriole-sd1a.210817.019.c2-factory-b1907625.zip
Android Platform Tools: /Documents/pixel/platform-tools/
SDK Version: 33.0.1-8253317
No device is selected.

The Kali version works! Now I wait on my pixel pro, probably a week or so, as I just mailed my pixel back to google. Also, I will download the raven image and replace the oriole image in firmware, as I am soon to be a pixel pro kind of guy :cool:

Thanks again for the time and effort!
[Google Pixel 6] badabing2003:
Unfortunately it looks like for each Linux flavor, I need to setup a system and manage to build the components to be able to publish a working version, not the type of cross-platform flexibility(or lack of) I was hoping for.
[Google Pixel 6] badabing2003:
New Release:

April 17, 2022 v2.3.0 release

Optional automatic check for updates feature.

Added help menu links to:

- Report an issue

- Feature Request

- PixelFlasher Project Page

- PixelFlasher Community (Forum)

- Homeboy76's Guide

- V0latyle's Guide

- Open Configuration Folder

- Check for New Version

Icons for menu items.

Link to download Pixel Firmware.

Link to download Android Platform Tools.

Unlock Bootloader.

Lock Bootloader.

SOS (experimental) - disable Magisk modules to get out of bootloop.

Additional flashing options:

- product

- system

- system_ext

- system_other

- vbmeta_system

- vbmeta_vendor

Added sideload flashing option.

Updated documentation.

Further improved console messages for troubleshooting.

Linux build using Github Actions.

Manual build for Kali Linux.
[Google Pixel 6] badabing2003:
New Release:

April 19, 2022 v2.4.0 release

Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade.

Autoscroll the console.

Code cleanup.
[Google Pixel 6] badabing2003:
Bug fix release:

April 20, 2022 v2.4.1 release

Bug Fixes: Error message during flashing, introduced by code reshuffle.

It turns out that some Magisk Modules don't set the id, which was expected to be present, which caused Magisk module management screen not to display.
[Google Pixel 6] badabing2003:
New Release:

April 30, 2022 v3.0.0 release

New workflow, no more package preparation, select options and flash all dynamic.

boot.img caching and management UI with details about the state of boot.img files.

Faster as there is no more need to zip a package.

Other optimizations and improvements.

Update documentation.

Check the main thread or the Github page for details about the new workflow, hope you find it useful.
[Google Pixel 6] matlear:
Would love to see a docker release of this so I can self host.
[Google Pixel 6] badabing2003:
I'm not sure I follow you, what you mean by self host?

The releases are single executables, you're not setting up an environment to run it, what would Docker give you?

Perhaps you can explain your use case?
[Google Pixel 6] badabing2003:
New Release

May 02, 2022 v3.1.0 release

Fixed a missing step in the final flashing of boot.img

Decoupled Firmware / ROM processing from selecting the files, now we have a separate button to process, makes it clearer and does not give the impression that selecting the file is hanging.

Added splash screen (v3.0.1), the GUI refresh hiccup is gone.

Made the boot.img management delete function more extensive.

I flashed my phone with the May drop using this version.
[Google Pixel 6] tom1807:
Just a tiny suggestion, possible to delete the content, which is not necessary anymore after flashing is done, in "%appdata%\PixelFlasher" like boot images and factory images?

Cheers

Tom
[Google Pixel 6] badabing2003:
Sure, I'll add an option to clear those.

You can manually delete them for now.

I kept it that way, because heavy users tend to switch between images, and having them cached and available makes it handy, but it is good to have options, boot images get cleared now if you delete them in the UI.

Another option is to automatically delete the firmware if the last boot in the list is deleted, this way all you have to do is delete the boot.img entries.
[Google Pixel 6] tom1807:
It's not something what has to be done at once, won't be a deal breaker. An option is even better, so heavy users won't complain about that.

Cheers

Tom
[Google Pixel 6] badabing2003:
Update:

May 02, 2022 v3.1.1 release

Handle UTF-8 Encoding
[Google Pixel 6] kariem112:
It seems the windows version does not work well if there is a space in the username folder:

2022-05-04 07:03:01 Processing firmware file ...

debug: Unzipping Image: C:\adb6\oriole.zip into C:\Users\User Name\AppData\Roaming\PixelFlasher\factory_images\oriole ...

debug: "C:\Users\KARIEM~1\AppData\Local\Temp\_MEI123202\bin\7z.exe" x -bd -y -oC:\Users\User Name\AppData\Roaming\PixelFlasher\factory_images "C:\adb6\oriole.zip"

2022-05-04 07:03:01 ERROR: Encountered an error.

ERROR: The system cannot find the file specified.

Name

System ERROR:

The system cannot find the file specified.

Aborting ...
[Google Pixel 6] badabing2003:
Can you confirm that you're using the latest version?

I don't see the double quotes in your output and suspect that you are not on the latest.

Let me know.
[Google Pixel 6] kariem112:
Yes, I am on 3.1.1.0, seems to be the latest.
[Google Pixel 6] badabing2003:
Oh I see, space in the username, that I was not expecting, it's an easy fix, I'll push an update later today, I just want to make sure I cover everywhere it is used.

Thanks for reporting it.
[Google Pixel 6] badabing2003:
New Release:

May 04, 2022 v3.2.0 release

Help menu option to create support.zip file, which sanitizes (redacts user names and device IDs) of the log files.

This makes it super easy to provide support.zip file when something goes wrong and need to report it.

In boot management, delete firmware cache of the selected boot.img if it is the last boot.img used from that firmware.

Handle space characters in username. @kariem112

Console is now responsive when processing firmware file.

More checks and validations.

Update readme with instructions on how to build PixelFlasher on MacOS.
[Google Pixel 6] kariem112:
thanks :) It seems another problem with the file path? The double // happens when trying to process the firmware file.

Traceback (most recent call last):
File "Main.py", line 740, in _on_process_firmware
File "modules.py", line 487, in process_file
File "ntpath.py", line 115, in join
File "genericpath.py", line 153, in _check_arg_types
TypeError: join() argument must be str or bytes, not 'NoneType'
e_path": "C:\\adb6\\oriole.zip",
"flash_both_slots": false,
"height": 1040,
"magisk": "com.topjohnwu.magisk",
"mode": "keepData",
"phone_path": "/storage/emulated/0/Download",
"platform_tools_path": "C:\\adb6",
"pos_x": 580,
"pos_y": 175,
"selected_boot_md5": null,
"update_check": true,
"verbose": false,
"version": "3.1.1.0",
"width": 1400
}
[Google Pixel 6] RobbyRobbb:
I also get some kind of error with the 3.2 version when selecting my phone. The mouse-cursor permanently turns into a spinning work-in-progress-cursor after this. The process also doesn't stop running when i quit PF, and even if i manually close the process in the task manager PF refuses to open when i try to re-launch it.

PixelFlasher 3.2.0.0 started on 2022-05-05 10:34:48
{
"advanced_options": false,
"boot_id": null,
"custom_rom": false,
"custom_rom_path": null,
"device": null,
"disable_verification": false,
"disable_verity": false,
"fastboot_verbose": false,
"firmware_path": null,
"flash_both_slots": false,
"height": 1040,
"magisk": "com.topjohnwu.magisk",
"mode": "dryRun",
"phone_path": "/storage/emulated/0/Download",
"platform_tools_path": "C:\\Users\\Robin\\adb",
"pos_x": 260,
"pos_y": 0,
"selected_boot_md5": null,
"update_check": true,
"verbose": true,
"version": "3.2.0.0",
"width": 1400
}

2022-05-05 10:34:48 Selected Platform Tools Path:
C:\Users\Robin\adb.
SDK Version: None

Please select a boot.img!

Loading Device list ...
This could take a while, please be patient.

debug: Populate device list
debug: select configured device
2022-05-05 10:34:48 No Device is selected!
Load time: 1 seconds

2022-05-05 10:35:06 Selected Platform Tools Path:
Y:\Android\cmdline-tools\platform-tools.
SDK Version: 31.0.3-7562133

2022-05-05 10:35:09 Reloading Device List ...
2022-05-05 10:35:10 No Device is selected!

2022-05-05 10:35:12 Reloading Device List ...
2022-05-05 10:35:12 No Device is selected!

Selected Device on 2022-05-05 10:35:14:
Device ID: 1C041FDF6000G1
Device Model: oriole
Device is Rooted: True
Device Build: SP2A.220405.004
Device Active Slot: a
Device Mode: adb
Magisk Version: 24.3:MAGISK (24300)
Magisk Modules:
Traceback (most recent call last):
File "Main.py", line 694, in _on_select_device
File "Main.py", line 537, in _print_device_details
File "phone.py", line 142, in magisk_modules_summary
File "phone.py", line 130, in magisk_detailed_modules
ValueError: not enough values to unpack (expected 2, got 1)

I just tried flashing Android 12 QPR3 with an earlier version of PF and it didn't manage to get Magisk working. The phone boots, but Magisk says it's not installed. I deleted the PF folder after running this, so i don't have the log. But i remember that the process ended with an error that said "Unknown partition: pf_boot", if that means anything.

Even though the phone boots it's a bit scary to think that there might have been more steps in the flashing process that never happened because of this error.
[Google Pixel 6] badabing2003:
Sorry for your troubles, double \\ is normal that's not the issue, can you please provide sanitized logs, you can create them from the help menu.

Thanks.

Also:

Please do not change the firmware filename, it is important to keep it intact, it has information about the hardware as well as the package signature.
[Google Pixel 6] badabing2003:
It looks like problem reading your Magisk modules.

What modules do you have, and do you have any special modules that block access?

I'll add more exception handling around that logic and also provide an option to be able to turn off Magisk modules management.
[Google Pixel 6] RobbyRobbb:
Pixelify

SafetyNet Fix

Viper4AndroidFX
[Google Pixel 6] badabing2003:
Thanks,

What do you get when you run this?

adb shell "su -c 'ls /data/adb/modules'"

One other question.

When you turn off verbose (I know you can't in UI now because of the error) but you can if you edit the configuration file

%APPDATA%\PixelFlasher\PixelFlasher.json

View attachment 5606601

The error goes away right?

It looks like the issue is when it's processing the details of the modules (probably Pixelify module)

UPDATE

@RobbyRobbb

No need to do anything, I have a fix, I'll post it later today, in the meantime if you disable verbose settings, and don't go the Magisk Modules management you should be fine.
[Google Pixel 6] badabing2003:
New Release:

May 05, 2022 v3.3.0 release

MacOS build.

Handle Magisk module.prop with comments.

Exception handling on magisk module errors.

boot.img management improvements.

Removed old Powershell script.

More checks and validations.

support.zip now includes sanitized PixelFlasher.db
[Google Pixel 6] kariem112:
Latest version worked like a charm. Kept the original firmware file name. Thanks a lot, wonderful tool!
[Google Pixel 6] badabing2003:
@Ictcreations

First and foremost, I'm really sorry that you went through these troubles, although we all take risks when rooting and modding our phones, no one wants to lose data or worse brick their expensive phone. I know how you feel, and for that I feel your pain and anger.

Having said that, I want to make something clear, PixelFlasher is just a UI layer on top of adb / fastboot commands, it automates the manual steps that you do when flashing a phone so that you don't have to type anything or fiddle with the phone, it basically follows those excellent guides that you used to do the exact same steps.

The messages you saw regarding partitions, those are not something that PixelFlasher did, it is the output of the flash process, and you would see that regardless of whichever approach you use to flash your phone, whether you follow the guide and do it manually, even if you don't root your phone and just flash, you will still see those messages.

There is no denial that something went wrong with your flashing, however pinning that on PixelFlasher is at best premature, and if you can kindly provide a Sanitized Support file by going to the help menu and selecting the option, I can take a look at the logs and determine what might have gone wrong.

View attachment 5608637

Given your anger, you might not feel inclined to provide the support file (which by the way has redacted any sensitive information) and that is your right, however I would suggest that you consider it, as it can help reveal something that could help others.

Lastly I want to say that if you search the forums, you will find many incidences of corruption (honestly quite too many), almost all of those are non PixelFlasher users, I say almost because you're the first person who reported it with PixelFlasher.

If I were a betting man, I would bet that this was more to do with the state/environment

What was on the phone (ROM and what not)

If you accepted OTA

What Magisk modules were active

Version of adb

Version of Magisk

USB cable

Your PC

...

I'm not dismissing the possibility of something being wrong in PixelFlasher, nothing is flawless, but it is highly unlikely that it was caused by PixelFlasher, had that been the case, all the folks before you (including myself) would have ran into the issue and this thread would be flooded with posts like yours.
[Google Pixel 6] Hot-Proton:
I have a Pixel 6 and use the latest Windows 11. My Problem ist the first start working but after i selecet plattform tools nothing happens anymore. I only see that the mouse cursor rotates but in the program itself does nothing more. I then closed the program and when I now starts, I only see the PixelFlasher logo, which then closes again. That is, it can no longer be started.
[Google Pixel 6] badabing2003:
See my answer to your other post here.

https://xdaforums.com/t/pixelflashe...g-managing-pixel-phones.4415453/post-86922745
[Google Pixel 6] badabing2003:
New Release:

May 21, 2022 v3.3.1 release

Change encoding from utf8 to ISO-8859-1

Button to paste the currently selected boot.img into custom flash file selection.

Several Mac version improvements, thanks to rhetorican for reporting and testing.

UI improvements

Fix: On low resolution screens, the application startup position is high enough to clip the top part.

Fix: On low resolution screens, the patch icon is too large and dis-proportional to the rest of the UI

Better dark mode handling on Mac / Linux

Increase the wait during flashing to account for slower devices.

Further improvements on support.zip redaction process.

Other minor fixes and additional validations.
[Google Pixel 6] freonchill:
Just successfully used 3.3.0 (started before I noticed that 3.3.1 was just updated), but not without some heartburn...

I had previously used pixel flasher to go from rooted 12.0.0 (SD1A.210817.015.A4, Oct 2021) to

12.1.0 (SP2A.220305.013.A3, Mar 2022) without any problems with version 1.2.0.1

and now 12.1.0 (SP2A.220305.013.A3, Mar 2022) to 12.1.0 (SP2A.220505.002, May 2022)

i have magisk hidden, so i manually did the process on the phone to patch the boot.img

did the dry run and no issues

so then i did "keep data" and flash

and it rebooted my phone, and rebooted and my phone, and oh crap a boot loop

(my kids then walked in from the pool and my wife wanted me to get dinner), so I paused on the unlock warning screen and went to go get dinner - panicking in the back of my mind)

came back hours later and used power+up / power+down to get it to go into bootloader, fastboot, adb sideload, adb rescue mode, googling to see what options I had from there, but most generic google searches came back with going to TWRP to replace X, Y, Z and I knew that wasn't an option....

the annoying thing was I couldn't do anything in adb, b/c it was unauthorized (but all for the better since i didnt mess anything up)

So I was going to see if maybe it was the fastboot current slot, so I changed from A to B, told fastboot to reboot and came back to fastboot, so I was going to reflash a stock march boot.img and see if it would get out of the boot loop. while downloading the factory image, I thought to check pixelflasher (that couldn't see my phone in all the other boot modes (adb sideload, adb rescue mode) and it showed as online?!?

so I clicked flashing thinking it would just give me an error and it all flashed through without a hiccup.

I crossed my fingers while it rebooted that it would get into a boot loop

then it all came up like nothing had happened.

did some app updates, checked the os update and it thought I still needed to update. rebooted and it said it was up to date.

out of an abundance of caution, I always download by photos and files and use swift backup to backup my apps, sms/mms, phone logs, etc. so even if i had to start over, I could get back to where i was, it would just be time consuming....

I have no idea why it bootlooped in the first place after successfully doing the dry run and then why it started to work hours later, but I'm glad it is back. time to go update my old S4 (that had lineage 14 to 19) that I used to google fixes while I at the restaurant waiting for the take out)...

windows 10 pro

pixel flasher 3.3.0

Android Debug Bridge version 1.0.41

Version 33.0.1-8253317
[Google Pixel 6] rhetorician:
This kind of an attitude is not conducive to a productive development community that's open to the lay public. It certainly doesn't help anybody who uses this thread to troubleshoot the tool. The use of these programs assumes that you accept the risk of something going wrong, even terribly wrong. We all make the decision to undertake this risk the moment we turn on developer mode; and yet you don't seem to acknowledge personal responsibility. If every person who experienced a boot loop and had to reflash the factory firmware behaved in this manner, I don't think lay folks like myself would be able to enjoy the work that these people produce and offer for free. After all, who would want to endure this kind of a response? One could be forgiven for questioning the sincerity expressed in your beginning/concluding remarks.
[Android Head-Units] MrHappyChappy:
Hello all,

I've been using my device in my Audi e-tron without issue, last week without anything changing it just stopped working, I've tried a different cable just in case but it's made no difference. When the device is plugged in, I can see that the unit is getting power and I can see a dim white light on the housing. What would my next steps be please? Are there other steps that I can take to troubleshoot the issue? Is it repairable?

Thanks in advance.

View attachment 5567245
[Android Head-Units] MrHappyChappy:
Anyone? I'm completely stuck on how to move forward with this, even a link with details on the steps that I can take would be hugely appreciated.
[Touch HD General] tonyblack:
I've just tried Orange UK and been told it's not yet available and to try again this aftenoon. If anyone else is succesful with Orange please post on here as soon as you are able to order a Touch HD.
[Touch HD General] k3v:
thanks for, the heads up. you have saved me a phone call. My contract is up and i am just waiting for this to come in stock
[Touch HD General] m.r.davies:
i called 10 mins ago and got told the same thing

I called last week, and the guy said they wont appear on the system till 2pm

looks like its a late lunch

i'll call about 1:30 and try my luck!

please let me know what deals they offer you (retention or not)
[Touch HD General] CPhoenix:
I take it everyone who is ordering their Touch HD through Orange, aren't bothered about using the data services?
[Touch HD General] k3v:
I already have an ancient unlimited data package for £3 plus vat, so i'm ok with orange
[Touch HD General] m.r.davies:
Yes, what do i need to know?
[Touch HD General] frustin:
are you a long standing customer? i'd probably want to talk to someone other than the droid that will answer the initial call. then say that the package is too inflexible.

i'm wanting more data this time myself, i'm a long standing customer and they helpped me out last time.
[Touch HD General] donbronzi:
250m for £6 and a free phone. Or £500 for the phone, another mobile provider and cheaper data.

No i'm not too worried plus i have heard that there might be a better data option in the wings. Also i have the 250 bundle and never get near it.
[Touch HD General] m.r.davies:
Yes, 12 years on contract

So what do i need to do? go through retentions dept, and then say the data package is not flexible? and speak to someone else?

oh btw, unlimited data is 500mb not 250mb
[Touch HD General] frustin:
yeah but you havent had a phone that you can

really

use on the t'internet. The browser/screen has always been too pants to use it effectively.
[Touch HD General] m.r.davies:
What are you suggesting ?