yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Snnorlaxx:
Well I tried something else, booted into safe mode, since I know this disables all the Magisk modules and settings. Restarted into the system, without enabling anything in Magisk and boom it see's the Pixel 6a now. Not not sure what is causing the issue, above my pay grade.
[Google Pixel 6] Snnorlaxx:
Sorry for my ignorance, but I don't know how to redirect it to a file.
[Google Pixel 6] badabing2003:
You haven't granted root access to shell process, hence PF can't perform any actions as su to get more data.

Please check the guide in OP of the main thread.

You could have done a Google search.

[command] > [filename]

You use > to redirect to a file overwriting an existing file or >> to append.

Actuall it is best to place all the set of commands I provided in the last post into a file

Let's name it test_adb.cmd and issue

test_adb.cmd 2>&1 adb_results.txt

to capture both stdout and stderr
[Google Pixel 6] badabing2003:
Update Release:

May 17, 2024 v6.9.5.0 change log:

Added Pixel 8a (akita) support.

Updated Pixel device end of life dates based on Google's published data.

Added an option to refresh Google Images download links, useful on release days when you want an immediate refresh.

Memory improvements when building Google Images list.

Added additional troubleshooting debug messages when a device is not detected.

Minor bug fixes and improvements.
[Google Pixel 6] Snnorlaxx:
here you go with the latest. Also confirmed shell is on the SU list. Will also try the latest iteration PF.

Thanks for the effort.
[Google Pixel 6] badabing2003:
Your device is not detected with adb command

Your ran this outside of PF

C:\Android\Platform-Tools>cd c:\

c:\>where adb
C:\Android\Platform-Tools\adb.exe

c:\>adb --version
Android Debug Bridge version 1.0.41
Version 35.0.1-11580240
Installed as C:\Android\Platform-Tools\adb.exe
Running on Windows 10.0.19044

c:\>adb devices
List of devices attached

c:\>cd C:\Android\Platform-Tools

C:\Android\Platform-Tools>adb --version
Android Debug Bridge version 1.0.41
Version 35.0.1-11580240
Installed as C:\Android\Platform-Tools\adb.exe
Running on Windows 10.0.19044

C:\Android\Platform-Tools>adb devices
List of devices attached

Notice how it is not listing your device, hence PF can't either.

Was your device connected to your PC when you ran the script?
[Google Pixel 6] Snnorlaxx:
It was connected, I can see my device when I boot into Lineage OS recovery, as well as when I boot into bootloader (fastboot). I also ran the script in recovery and posted that it shows up as well.

As I said earlier, all was working , including PF until I factory reset my phone, and reflashed Lineage OS and Gapps. After that, PF can 't see my devices any more. It has to be some stupid setting on my device or braindead thing I've done to cause this situation.

Appreciate all the help tho, and maybe I'll learn something along the way.
[Google Pixel 6] bdr127:
Since factory resetting and reflashing, did you re-enable ADB debugging in Developer Options?
[Google Pixel 6] bdr127:
I know this is off-topic for this thread, but I just noticed your superuser screenshot and had to comment.... You have really got to get rid of ES File Explorer. Ten years ago, it was the best. But it was bought out by DO Global (Chinese tech company) who has done a lot of shady stuff.... It turned into adware. ES File Explorer even got banned from the Play Store. Other people have also said you shouldn't use it.

So, yeah.... I would remove that if I were you. Especially since you have Solid Explorer.
[Google Pixel 6] Snnorlaxx:
yes it is on, but it seems to turn off tho every once in a while, some thing it never did before, I'm always checking that its on now. Also , I have no problems using adb from a command in Windows, get proper response in recovery and fastboot.
[Google Pixel 6] Snnorlaxx:
Thanks for the heads up.
[Google Pixel 6] badabing2003:
You're not comparing apples to apples, recovery or bootloader is not the same as adb mode.

PF can't do magic if your device is not detected.

If put your device in recovery and run the script and also scan in PF.

If PF does not detect it still and your script does, then I'll continue to investigate if you provide the new outputs and support file.

Same thing with fastboot.

Otherwise this is off topic in this thread.

Clearly command line can't see your device in adb mode.

Not an issue with PF, and you mentioned that disabling modules makes it work.

Obviously you have some module that is interfering with adb.

Something to be discussed in their respective module threads.
[Google Pixel 6] Snnorlaxx:
So here are my latest tests. Restarted the phone in safe mode(disabling Magisk modules) and ran script. Restarted in regular mode now with no modules enabled. and ran script. Phone can seen with ADB in command as well as PF. Posted the outputs as well as sanitized suport file.

I truly appreciate all the time and effort you've spent an this, I originally thought it was a simple bug, but it now looks like my setup is borked. Not sure if it's something left behind in a Magisk folder, I ran a Google restore from backed up files or something else with this fresh install is very wrong.

ps with Magisk aps still disabled, USB debugging has persisted after several reboots, and the notification that it is enabled pops up every time, for what its worth.
[Google Pixel 6] badabing2003:
Yes your device is detected with your modules disabled.

There is nothing wrong with PF.

You're still on the April release.

Yet still you have not granted root access to shell

Start enabling modules one by one and see which one is the culprit.

=======================================
Selected Device on 2024-05-18 09:41:39:
=======================================
Device ID: REDACTED
Device Model: bluejay
Device Active Slot: b
Device Mode: adb
Device Name: Pixel 6a
Device First API Level: 32
Device Version End Date: June 2025
Device Security Update End Date: June 2027
Has init_boot partition: False
Device Bootloader Version: bluejay-1.3-11403664
Device is Rooted: False
Device Build: AP1A.240405.002.A1
Device API Level: 34
Android Version: 14
Android Name: Android 14
Android Codename: Upside Down Cake
Android Release Date: Q3 2023
Android Latest Update: Present
Device Architecture: arm64-v8a
Device Kernel: Linux localhost 5.10.189-android13-4-00012-g1217bb583cc5-ab11174560 #1 SMP PREEMPT Mon Dec 4 18:59:42 UTC 2023 aarch64 Toybox
Device Kernel Version: 5.10
Device KMI: 5.10.189-android13
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 0
ro.boot.vbmeta.device_state:
ro.product.first_api_level: 32
ro.boot.veritymode:
ro.boot.verifiedbootstate: orange
ro.secure: 1
ro.zygote: zygote64_32
ro.vendor.product.cpu.abilist: arm64-v8a,armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist32: armeabi-v7a,armeabi
Magisk Manager Version: :
Checked for Package: io.github.huskydg.magisk
KernelSU App Version: :
APatch App Version: :
[Google Pixel 6] Snnorlaxx:
Didn't the previous screenshot show that shell was granted SU (see new screenshot).

Also updated the OS today and PF is still seeing the device. Will have to try modules one by one.

ps just tried my first module, Zgisk/Lposed, and rebooted and no debugging notification. tried going into dev options and enabling it, the toggle works(turns on) but still no notification. ADB from command also see's no device. Second support file after enabling Zgisk/Lposed nothing detected.
[Google Pixel 6] Snnorlaxx:
So I think I found the offending app, it was a lsposed app called "I am not a developer" used it a few time to allow me to downgrade a certain app.I wasn't even using it now, but when I reflashed my phone, I restored a backup of LSposed module list and scope and it then brought back this app. Remmoved it and after rebooting several times, everything see's my device, adb debugging notification ccomes up each and every time the device reboots as well as your most excellent PF.

I feel bad having wasted so much of your time, I'll just have to learn to debug my crap myself.

You're a scholar and a gentleman, appreciate the effort put into helping a dweeb muddle through.

I'm starting to think I'm getting too old for this stuff, but I pick something up each and every time I break a device and attempt to fix it.
[Google Pixel 6] badabing2003:
Update Release:

June 04, 2024 v6.9.6.0 change log:

#204 Fix Pyinstaller issue, thanks to PR from @cjshearer.

PIF Import favorites can now import recursively including subdirectories.

Added Device | Check otacerts menu option to quickly check if the ROM is signed.

Sync banned kernel list with @osm0sis published list.

Improved exception handling

Improved debug messages for troubleshooting

Fix timing issue for a corner case cleanup before unzipping is completed.

AVBTool improvements.
[Google Pixel 6] badabing2003:
Update Release:

June 24, 2024 v6.9.8.0 change log:

Improve Check keybox.xml to report if the certificate is software signed, also report about all included certificates.

Added settings option Keep temporary support files in case one needs to inspect the support files.

Add Github action to build on MacOS 12, MacOS 11 runner has been deprecated.

Update Pixel beta links from A14 to A15.

Minor bug fixes and improvements.
[Google Pixel 6] Sk007777:
please help me unlock bootloader
[Google Pixel 6] badabing2003:
Wrong thread.

If your bootloader is locked and can't be unlocked by fastboot, reach out to your carrier.
[Google Pixel 6] Sk007777:
i dont have a carrier

What are my options ?
[Google Pixel 6] badabing2003:
if you have tried the fastboot method and didn't work, I don't have an advice for you.
[Google Pixel 6] badabing2003:
New Release:

July 4, 2024 v7.0.0.0 change log:

When sideloading OTA, automatically cancel a previous OTA (in progress or completed but not rebooted), which assures a better success rate. (Only applies to rooted devices that are in adb mode).

Added My Tools Menu, you can now add custom tools to PixelFlasher to easily launch your favorite tools / apps (example odin3).

Added Process Image in PIF Manager, PixelFlasher can now process a device image and extract PIF print from it with a single click. (Currently supported image types are, Pixel firmware, Pixel OTA, images with payload.bin, Samsung firmware).

When reading device details, report the sys.oem_unlock_supported prop value.

Miscellaneous minor improvements.
[Google Pixel 6] DodoBro:
I'm confused about flashing custom roms.

There is a field called "Apply Custom ROM" in the program. If i add a custom ROM to that field and click "Process" this ROM shows up in the Boot list. If i click on that ROM and then on "Patch" i can patch this ROM with Magisk.

Selecting that patched ROM in the Boot list is enough when flashing official firmware via the "Device Image" field, making the "Flash Pixel Phone" button interactable. But in the case of custom ROMs it seems extra steps are required; the field next to the flash method drop-down list seems to be required to be populated.

I can't find information on what I'm supposed to put in that field. I'm also uncertain whether the "Device Image" field needs to be populated with official firmware even if I'm only going to flash a custom ROM.

The ROM in question is DerpFest. The installation instructions in that thread is simply "Flash with adb sideload ROM.zip using recovery". The thing is that several users have failed to install it this way and others referring to other methods using a program called Payload Dumper.

As i have only ever used PixelFlasher to handle firmware flashing on my Pixel 6 I'd be more comfortable installing this custom ROM via this program too.

Any further instructions?
[Google Pixel 6] badabing2003:
Each custom ROM is different process, and it's best to follow the ROM author's steps, the custom ROM option in PixelFlasher is there for convenience, but unless you know what you're doing and are very compfortable with what it does, I recommend you don't use it.

What that feature allows

Processing the image to extract boot / init-boot / vbmeta and related files from it, and they would show up in the boot list, and even though vbmeta does not show up there, it is extract and available to be used (see more about it down below)

For specific types of ROMs that follow Google's factory image format, and the ROM instructions require replacing stock factory's image-<device>.zip, (example statiXos, you would select the factory, process it, then select rom, process it, select the boot that you want (from factory or rom) and then Flash Pixel Phone with the flash options that are required (if the ROM requires verity / verification disabled ...)

I have never used DerpFest or read about it, I personally don't use any custom ROM (I'm a stock kind of guy)

I don't even know why guide you follow, I took a quick look at this guide here, I'm not even sure if this is the proper way to flash this ROM, as this guide here uses totally different process.

Assuming that you're following this guide or something with similar steps (please it's up to you to make sure you find out and follow the proper steps), I'l show you how you can perform the steps outlined using PixelFlasher (sorry it won't be one click)

Let's assume that you've already done steps 1-4

Step 5-7:

When you process stock firmware / ota in PixelFlasher, vbmeta will be extracted.

Switch to custom flash and do the following

View attachment 6120505

For flash options choose the following

View attachment 6120506

Step 8:

Device would already be in bootloader mode, so nothing to do

You probably need to perform this manually (I don't know the implications of not freeing up space.

fastboot delete-logical-partition product_a

Follow this (this covers bullets 3-5 under step 8)

View attachment 6120512

Again, it's up to you to fully understand the process and how to perform each action, and make sure you're ok with it before proceeding, there is a reason why this is only available with advanced options turned on.
[Google Pixel 6] miss:
Good afternoon,

let's see if you can help me, for a long time on my laptop I haven't been able to get pixelflasher to detect my phone, the scan button doesn't light up.

I have been granted shell su and the laptop with the command prompt window c:/android/platform-tools/adb devices if the phone identifies me.

I know it's not a pixelflasher problem and it has to be my PC but I can't find the keys. I assume that the Google USB driver is installed correctly since it detects my phone and, as I said, by adb as well.

Also say that on my desktop PC there is no problem and pixelflasher does detect my phone
[Google Pixel 6] badabing2003:
Please provide support file and also a screentshot of the entire PF screen showing that the scan button is disabled.
[Google Pixel 6] miss:
support file I can't, as you see in the image it tells me that it can't write it, I'm going to take the photo on the laptop, give me a minute, it's off
[Google Pixel 6] miss:
View attachment 6121157
[Google Pixel 6] miss:
The fact that the phone is connected does not change the button remains gray
[Google Pixel 6] badabing2003:
Please don't take this the wrong way, but I'm serious guys/gals.

You have to put some effort, the very least you have to READ.

View attachment 6121163
[Google Pixel 6] miss:
View attachment 6121165
[Google Pixel 6] miss:
What Android SDK version is the good one?
[Google Pixel 6] miss:
download the latest one from here

Notas de la versión de las Herramientas de la plataforma del SDK | Android Studio | Android Developers

Las Herramientas de la plataforma del SDK de Android son un componente del SDK de Android.

developer.android.com

I have the same problem
[Google Pixel 6] badabing2003:
Click on the link to the left of the Platform tools selection.

As for the support.zip issue.

Enable debug and create support again and provide the console output along a video.
[Google Pixel 6] miss:
I have copied the platform-tools from the desktop computer where it works to the laptop in a new folder, I say having the same problem, the scan button remains gray
[Google Pixel 6] miss:
View attachment 6121185
[Google Pixel 6] miss:
With the latest platform-tools it doesn't solve it either and with the version that works for me on the desktop PC, moving to the laptop I have the same problem
[Google Pixel 6] miss:
I found this in user/pixelflasher/support
[Google Pixel 6] badabing2003:
You have problems reading?

I requested the following

Where is it?

And please stop being creative and copying files from one computer to another.

Just download the damn thing, unzip it somewhere else

Browse and select it in PF (see you have selected nothing)

Then you should not get the error.

View attachment 6121194

Unless you do what I'm asking you to do, please don't ask for my help, I don't want to waste time circling this.
[Google Pixel 6] badabing2003:
Pixelflasher does not create such file, I don't know where you got it from.
[Google Pixel 6] miss:
from hereView attachment 6121197
[Google Pixel 6] miss:
I have done what you told me. download platform-toos again, put new folder on desktop, I have the same problem
[Google Pixel 6] miss:
View attachment 6121201
[Google Pixel 6] miss:
View attachment 6121206
[Google Pixel 6] miss:
I think I have done what you asked for the most, or so I have understood
[Google Pixel 6] miss:
Thanks anyway, I like your application and it works for me on one of the computers.

THANK YOU
[Google Pixel 6] cr4zyd:
Worked great! Updated from the February update to the March update with no issues. Maintained root/data/etc.
[Google Pixel 6] badabing2003:
New Release: (See full details here on xda or here at github)

April 03, 2022 v2.0.0.0-pre release.

Major refactoring

Added Advanced (Expert) mode UI.

Basic mode keeps UI simple and hides expert features.

Support for setting active slot.

Reboot options (recovery, system, bootloader)

Moved custom ROM options to expert mode.

Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.

Moved flashing to both slots, disabling verity / verification to expert mode.

Many other improvements, validations and checks.

Updated documentation.
[Google Pixel 6] RobbyRobbb:
This error doesn't make sense to me. Got this while trying to prepare 12.1.0 (SP2A.220305.013.A3, Mar 2022):

PixelFlasher 2.0.0.0

No previous flashable package is found for the selected firmware!
Selected Device:
Device ID: 1C041FDF6000G1
Device Model: oriole
Device is Rooted: True
Device Build: SQ1D.220205.004
Device Active Slot: a
Device Mode: adb
Magisk Version: 24.3:MAGISK (24300)

Rebooting device 1C041FDF6000G1 to bootloader ...

==============================================================================
PixelFlasher 2.0.0.0 Preparing Package
==============================================================================
ERROR: Android device model oriole does not match firmware model Pixel6
[Google Pixel 6] badabing2003:
Can you show what firmware file did you select? (full filename / path)
[Google Pixel 6] RobbyRobbb:
https://dl.google.com/dl/android/aosp/oriole-sp2a.220305.013.a3-factory-8bea92d1.zip
[Google Pixel 6] badabing2003:
Sorry if I was not clear,

I meant `Pixel Phone Factory Image` you selected in the PixelFlasher Application in step 1.

I think I should add that as the part of the displayed error message.
[Google Pixel 6] RobbyRobbb:
C:\Hämtade Filer\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip
[Google Pixel 6] RobbyRobbb:
Ok, the tenth time it worked. I have no idea why. But after the preparation has finished i get this error when trying to flash:

Traceback (most recent call last):
File "Main.py", line 489, in _on_flash
File "modules.py", line 728, in flash_phone
AttributeError: 'NoneType' object has no attribute 'id'
[Google Pixel 6] badabing2003:
That is really weird.

The fact that it reported that the firmware model is Pixel6, it means that the selected factory image was named pixel6.zip

The program picks up the factory image model from the filename

In this case `oriole-sp2a.220305.013.a3-factory-8bea92d1.zip` , and it extracts the first portion of the name before `-`

Seeing that there is no Pixel6 in your filename, I'm quite stumped, by any chance is it possible that you initially chose a filename that was named pixel6?

I asked for full path in case there was local / issues that was tripping on parsing
[Google Pixel 6] badabing2003:
do you mind turning on verbose mode , clearing the console, selecting the firmware, the phone, and then hitting the prepare package, and share full console output?

You can share privately if you want.
[Google Pixel 6] badabing2003:
@RobbyRobbb

I pushed a hotfix, v2.0.1

Please give that a try and let me know please.
[Google Pixel 6] RobbyRobbb:
That did it. Thank you for your hard work!
[Google Pixel 6] badabing2003:
Update:

Version 2.0.1 which includes a hotfix for issue reported here.
[Google Pixel 6] RobbyRobbb:
Where do i donate?
[Google Pixel 6] badabing2003:
Thank you for the consideration.

No donation, this is simply giving back to the community that has given me a lot over the years.
[Google Pixel 6] alarmdude9:
Silly question. If I am understanding it, it is written in python. Is there any plans on porting it to linux?
[Google Pixel 6] badabing2003:
Not silly at all, that's the idea, to have it ported to other platforms

GitHub - badabing2005/PixelFlasher: Pixel™ phone flashing GUI utility with features.

Pixel™ phone flashing GUI utility with features. Contribute to badabing2005/PixelFlasher development by creating an account on GitHub.

github.com

I do have have few other neat features in the pipeline that I'm working on, so this might take a back seat, though I do welcome a pull request if someone wants to tackle that.
[Google Pixel 6] tom1807:
Tested the program today, worked flawlessly. And very fast, if keeping in mind that Google needs a "lifetime" for optimizing the device.

I saw the problem reported above, is there a possibility that the program has a problem when the filepath has special letters?

In this case "C:\Hämtade Filer\". or maybe the space between the 2 words?

Cheers

Tom
[Google Pixel 6] badabing2003:
If you look at the debug output, you'd see that file paths are passed between double quotes, this was fixed few versions ago, so space is definitely not an issue anymore.

Local potentially could be (as my locale is English), but I think it is not either, you can see that RobbyRobb confirmed that it is working fine for him, the issue he experienced was an oversight on my part not initializing a variable in basic mode, which got fixed with hotfix 2.0.1.

t-ryder in Germany also has it working without any issues, so I think we don't have a locale issue either.

In case you discover anything that does not work, just report it here or at Github, and I'll tackle it.
[Google Pixel 6] badabing2003:
Reboot your computer and try again.

You have another platform tools being loaded by some other program.

Furthermore you do not need to copy PixelFlasher into platform tools directory, leave PF wherever you want, it can run from anywhere, and keep platform tools free of any other downloads and tools (seperation of concerns).

And copy and paste the console contents in full.
[Google Pixel 6] miss:
View attachment 6121261
[Google Pixel 6] miss:
the same

View attachment 6121263
[Google Pixel 6] badabing2003:
Clean up your system path.

The fact that adb was attempted even before loading the platform tools path suggests that you have a messed up system path.

Also, don't bother posting if you don't include the console text pasted here (in full, from the start to the end)

View attachment 6121268
[Google Pixel 6] miss:
ok when I get home I will delete the c:\android directory, now I'm at work.

I will send you a copy of what will appear in the complete console

thanks
[Google Pixel 6] badabing2003:
Latest Release:

July 11, 2024 v7.1.0.0 change log:

Add license headers to source files.

Improved logging.

By request, PIF Manager now supports processing img files to extract PIF prints. (This is in addition to supporting zip files of factory / OTA images).

Check keybox.xml tool now provides more extensive report about the keybox.