yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] badabing2003:
I see that you have the tool running from one drive folder with spaces.

Maybe that is the issue, please move the tool to a path that does not include spaces or weird characters, see if that resolves the issue, if it does I'll fix it in the next version.

Also see when you do that if the log file gets filled
[Google Pixel 6] dilruk:
Cool let me try that.

EDIT: Works now. Still nothing in the log though
[Google Pixel 6] badabing2003:
OK Thanks for reporting back.

I'll make a fix later today for the path issue.

I'll have to figure out why the log file is empty.
[Google Pixel 6] Snow_ball:
worked flawlessly for me, making the monthly update while keeping root a breeze. THANK YOU
[Google Pixel 6] thekdub:
Not sure what I'm doing wrong, but it can't seem to find the unzipped image folder. I even tried manually unzipping it, but the app detects and deletes it. Run as administrator and using version 1.1.3:

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

Preparing Package

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

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

Found Bundled 7zip.

zip/unzip operations will be faster

Unzipping Image: C:\Downloads\Pixel6\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Apps\PixelFlasher ...

Unzip time1: 0.5752615928649902

ERROR: Unzipped folder oriole-sp2a.220305.013.a3 not found.

Aborting ...
[Google Pixel 6] badabing2003:
New release:

March 22, 2022 v1.1.4-alpha release.

Bug Fix: Handle space characters in paths.
[Google Pixel 6] badabing2003:
Can you please try with v1.1.4-alph and report back?
[Google Pixel 6] thekdub:
Unfortunately, same thing:

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

Preparing Package

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

Found Bundled 7zip.

zip/unzip operations will be faster

Unzipping Image: C:\Downloads\Pixel6\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Apps\PixelFlasher ...

Unzip time1: 0.08989071846008301

ERROR: Unzipped folder oriole-sp2a.220305.013.a3 not found.

Aborting ...
[Google Pixel 6] badabing2003:
If you're willing to help out, I'll give you a build that would try few things to determine the cause of the issue and output more verbose messages.

It won't be the final build, but would help me figure out the issue as I cannot reproduce it.
[Google Pixel 6] thekdub:
That would be great.
[Google Pixel 6] badabing2003:
Try this one, let's see what output you get.

When you paste the console output, please keep everything intact and just redact the device id.
[Google Pixel 6] thekdub:
=============================================================================

Preparing Package

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

Found Bundled 7zip.

zip/unzip operations will be faster

Unzipping Image: C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Apps\PixelFlasher ...

debug: "C:\Users\Kirk\AppData\Local\Temp\_MEI127842\bin\7z.exe" x -bd -y "C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip"

Unzip time1: 0.12499141693115234

Unzipped into oriole-sp2a.220305.013.a3 folder.

Traceback (most recent call last):

File "Main.py", line 422, in on_prepare

FileNotFoundError: [WinError 3] The system cannot find the path specified: 'C:\\Apps\\PixelFlasher\\oriole-sp2a.220305.013.a3\\flash-all.sh'
[Google Pixel 6] badabing2003:
sorry @thekdub

In order to test the app before giving it to you, I had added a line to negate a result, but unfortunately I forgot to remove it before building and giving you a copy.

Please try this one.
[Google Pixel 6] thekdub:
Looks like it worked was just waiting on python libraries.

Connect your device

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

Preparing Package

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

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

Found Bundled 7zip.

zip/unzip operations will be faster

Unzipping Image: C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Apps\PixelFlasher ...

debug: "C:\Users\Kirk\AppData\Local\Temp\_MEI51122\bin\7z.exe" x -bd -y "C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip"

Unzip time1: 0.10936474800109863

ERROR: Unzipped folder oriole-sp2a.220305.013.a3 not found.

Disabling bundled 7zip ...

Trying unzip again with python libraries ...

Unzip time1.1: 49.77444267272949

Unzipped into oriole-sp2a.220305.013.a3 folder.

Extracting image-oriole-sp2a.220305.013.a3.zip ...

Unzipped into C:\Apps\PixelFlasher\oriole-sp2a.220305.013.a3\image-oriole-sp2a.220305.013.a3 folder.

Unzip time2: 108.96331071853638

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 ...

debug: "C:\Users\Kirk\Desktop\platform-tools\adb.exe" -s 1A061FDF600H0X push "C:\Apps\PixelFlasher\oriole-sp2a.220305.013.a3\boot.img" /storage/emulated/0/Download/boot.img

C:\Apps\PixelFlasher\oriole-sp2a.220305.013.a3\boot.img: 1 file pushed, 0 skipped. 13.5 MB/s (67108864 bytes in 4.749s)

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?

User pressed cancel.

Aborting ...
[Google Pixel 6] badabing2003:
@thekdub

Yes it worked, but it would be slow because it won't be able to use the bundled 7zip.

I'd be curious as to why 7zip is failing on your system, if we figure that out you'd get it to work much faster.

Can you try these steps.

1- Quit the App

2- Launch the APP

3- repeat the package step, you can abort it when it reaches the magisk step

4- But do NOT quit the app, that's because the packaged 7zip gets unpacked into a temporary folder, and each time it is different, so we want to keep the app running, and then look at the logs of the first unzip command.

it would be something similar to this, but the part after the Temp would be different (look for the first debug message)

"C:\Users\Kirk\AppData\Local\Temp\_MEI51122\bin\7z.exe" x -bd -y "C:\Downloads\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip"

You want to remove the debug part, and copy the rest (quotes included, similar to the sample above)

Open a windows command shell and paste it and execute

Tell me what it responds with.
[Google Pixel 6] badabing2003:
Sorry to hear about your troubles, but am happy to learn that everything is working now.

If you could kindly share the support.zip file, I'll take a look and see what exactly happened. That helps immensely.
[Google Pixel 6] freonchill:
1. disclaimer - your mileage may vary

2. BACKUP

3. BACKUP

4. BACKUP

5. I am glad they posted their experience because it echoes items 1-4

6. I am glad the writer of the tool replied in the way they did - REQUESTING FEEDBACK AND OFFERING SUPPORT TO BETTER THEIR APP - its the best for the whole community

I saw the posting of their personal experience and woes, as well as the OP reply when I was going through my panic yesterday and it reminded me that despite knowing the risks, and the time I would take to get it back in working order, I took on today when trying to update from the March release and May release.

When I got into a boot loop this afternoon, it wasn't what I wanted to do with several hours of my day, but it was the risk I took for the benefits I get by rooting. Otherwise, I could be like the masses and typically just be able to use the OTA, but I take the risk for the reward of the extra features.

I am technical in comparison to the people in my life that think I am crazy for rooting, but I am no computer programmer that could be a developer, to be able to understand the specifics for why this works, let along write an app to automate the process like badabing2003 has done for us.

I commend and thank badabing2003 for the time spent on this app, as though since I have come from the experience of the flashing and rooting several devices over the last 15ish years (B&N nook, ATT S4, HP touchpad, 1+5T, 5 different generations of Kindle Fire tablets, as well as countless of dd-wrt routers) doing the manual process of updating a rooted pixel6 was over my comfort level and badabing2003's ability to make it POINT AND CLICK has been a life send...

Flashing your daily driver can be a stressful situation and this app puts a comfort level on it.

Again, I commend and thank badabing2003 for the time spent on this app (and will be replying with the logs to hopefully help factor out the issue I had in the hope that it will be seamless for someone else in the future.

(and sorry for all the quotes and long post...)
[Google Pixel 6] freonchill:
Thanks and I commend and thank you - badabing2003 for the time spent on this app.

also, I don't know how you wrote this app, but I want to make a point that I ran this from a folder that I have since deleted, but you wrote it in such a way that I could re-download the app, run it, and save-out this log after deleting the original folder - BRILLIANT! (maybe not good for portability to take everything and not leave logs in various places (cruft, but great that I can still provide this information)
[Google Pixel 6] Hot-Proton:
Can i use PixelFlasher with locked Bootloader or only with unlocked Bootloader?
[Google Pixel 6] badabing2003:
@rhetorician and @freonchill

First and foremost, thanks for your support.

I want to say that, people have the right to get angry, and when they get angry they want to blame something / someone, and often not themselves, this is normal human behavior and I accept it, specially more if the blame is correctly aimed.

To correctly aim the blame, it requires cooler heads, open mindedness and effort to dig and understand the details of the events.

Not everyone has the skills or the patience or the proper tools to do that type of analysis, hence why I added an option in PixelFlasher to generate a sanitized (all sensitive information redacted) support.zip file.

Like both of you have done, providing this file, not only helps me understand / discover any shortcomings in the PixelFlasher, but it also exposes potential issues in user's environment, or an oversight in the sequence of steps taken.

As you both correctly pointed out, providing support.zip helps everyone / the community, no program or process is flawless, and only with iterative improvements it gets better and more robust, and everyone benefits when it does.

@freonchill

I will take this opportunity to dissect your logs and color comment on everything that happened in as much details as I can. I will make a separate post of that in the main thread instead of here, but will link it here when done. That is more of a generic post rather than anything specific to Pixel 6 and it benefits more if posted in the main thread.

I think it could help others to understand better what goes on while the program is running, and perhaps help them self troubleshoot issues before getting angry (if they're inclined to do so).
[Google Pixel 6] badabing2003:
It is an absolute requirement that you have an unlocked bootloader to flash / patch your phone.

If you turn on advanced mode, PixelFlasher has a button to unlock the bootloader, this assuming that your phone bootloader is unlockable and you did turn on developer mode and did set the proper options.

It basically issues the same command that the guides tell you, nothing more nothing less.
[Google Pixel 6] Hot-Proton:
What you mean with right option?
[Google Pixel 6] badabing2003:
Guides, guides, guides.

Linked everywhere (in OP, in help menu of the app), the basis of the tool.

From Homeboy76's guide

View attachment 5620017

From V0latyle's guide

View attachment 5620019

These are all manual steps that cannot be automated and are absolute per-requisites.

Once those are done, and you can select the device in PixelFlasher, then you can continue unlocking in PixelFlasher if you wish, it will do the reboot and issue the command `fastboot flashing unlock` and warn you that you would be wiping your phone ...
[Google Pixel 6] Slim2none4u:
badabing2003 For Recognized Developer!!​

😏 😉😎😁

Thank you for this awesome tool!!!
[Google Pixel 6] badabing2003:
@freonchill

See this post.
[Google Pixel 6] badabing2003:
@Hot-Proton

1- did the phone for back to system as it was supposed to?

2- can you please run again the dryRun but this time with console verbose on and provide support.zip?

Thanks
[Google Pixel 6] Hot-Proton:
1. after finish its not go back to System. Stays in the bootloader.

2. see attachment
[Google Pixel 6] badabing2003:
Can you please run this from command line?

If the phone is in adb mode

"D:\Software_Tools\Multimedia\Medien-Geräte\Handy\PixelFlasher\platform-tools\adb.exe" -s 23071FDF6005C2 devices

If the phone is in fastboot mode

"D:\Software_Tools\Multimedia\Medien-Geräte\Handy\PixelFlasher\platform-tools\fastboot.exe" -s 23071FDF6005C2 devices

And can you please provide me this file?

C:\Users\martin\AppData\Roaming\PixelFlasher\factory_images\oriole-sp2a.220505.002\flash-phone.bat

Thanks
[Google Pixel 6] badabing2003:
Try the attached version, I believe it should work.

If it works, I'll release it,

If it does not work, please set verbose on and provide a support.zip

Thanks
[Google Pixel 6] Hot-Proton:
Get the same error.
[Google Pixel 6] Hot-Proton:
Here the file. The ADB Commands working whene remove "
[Google Pixel 6] badabing2003:
Please edit this file

C:\Users\REDACTED\AppData\Roaming\PixelFlasher\factory_images\oriole-sp2a.220505.002\flash-phone.bat

You would see the first line to be:

chcp 850

Please change it to

chcp 1252

and run that script from command window.

Let me know if you still get that error.

One other thing.

I see a dot after 850

Do you see that in that file?

If yes, let me know if removing that dot and keeping it as 850 works?

what do you get when you run the following command

chcp
[Google Pixel 6] Hot-Proton:
Dont see chcp in the flash_all?

whene i enter chcp i get this:

c:\Users\martin\AppData\Roaming\PixelFlasher\factory_images\oriole-sp2a.220505.002>chcp

Aktive Codepage: 850.
[Google Pixel 6] badabing2003:
can you attach that file please?
[Google Pixel 6] Hot-Proton:
the chcp? where can find this? If you need more help, you have to be more specific. I'm not a programmer or anything, just a simple user.
[Google Pixel 6] badabing2003:
Please share this file

%AppData%\PixelFlasher\factory_images\oriole-sp2a.220505.002\flash-phone.bat

Then open it in notepad

You should see the first line to be

chcp 850.

if there is a dot there, please remove the dot

and double click on the file, if your phone reboots, we're good

if it does not, change 850 to 1252 and double click again.

Thanks
[Google Pixel 6] Hot-Proton:
Ok can not help now. I have flash latest Image manuel with flash_all and now its not boot up. Reboot always in bootloader.
[Google Pixel 6] badabing2003:
You did the steps manually? and your phone is bootlooping? (which guide did you follow?)

flash_all would have wiped your phone, or did you modify it?

If you flashed factory image yourself with wipe, your phone should not be bootlooping.

The above test that I asked for can be even performed without the phone attached.

If you get file not found it means it didn't work, you get anything else it means it worked.
[Google Pixel 6] Hot-Proton:
Yes use flash-all.bat. have flash again and now say is corrupted and i see only now charging symbol. I used this guide: https://rootmygalaxy.net/flash-fastboot-images-on-google-pixel-6-and-google-pixel-6-pro/

I have unlock befor with fastboot flashing unlock and after this fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img. Thene i have use flash-all.bat.

Edit i am back again and flash now with Android Flash Tool. Hope its working.

Install Complete​

The build has been successfully installed. It is now safe to unplug your device.

All working now.
[Google Pixel 6] Hot-Proton:
yes have a dot. have removed now but not work with 850

Whene i cange to 1252 its reboot. But the error The system cannot find the specified path. is not fixed.
[Google Pixel 6] badabing2003:
I believe 1252 is good for your case.

Happy to hear that you were able to get your phone working again.

Here's an updated version that allows you to specify the codepage.

Change this setting in File Menu | Advanced Configuration.

View attachment 5621625

Use the attached version of PixelFlasher.
[Google Pixel 6] Hot-Proton:
Test tomorrow.
[Google Pixel 6] Hot-Proton:
This Version working now with 1252 . No error. great jop my friend.
[Google Pixel 6] badabing2003:
Thanks for all the testing and reporting.
[Google Pixel 6] badabing2003:
New Release:

May 25, 2022 v3.3.2 release

Handle system codepage.

Add configurable codepage setting in advanced settings to be able to override the value.

Selected boot color is now blue instead of red to avoid thinking that it has a problem.

After Flashing, clear connected device to avoid using device in case it is not yet ready.

Fix: Paste boot button should be hidden in basic mode.

Always print md5 of Magisk_patched (previously only verbose mode displayed it).

Wait 10 seconds instead of 5 seconds after reboot before issuing next command.
[Google Pixel 6] norman00037:
May I ask:

If I'm on February Update, can I flash May update directly , or I have to flash March > April > May update
[Google Pixel 6] badabing2003:
Yes you can, just follow the basic mode usage guide from the main thread (not this thread)
[Google Pixel 6] adewaleandrew:
Can I flash android 12l on at n t pixel 6
[Google Pixel 6] badabing2003:
I'm sure you can, I have not done so, so I'm not speaking of experience, however I see no reason why it shouldn't work, it's just another image.

Perhaps others who have done so can chime in.

Make sure you follow the 12L flashing instructions, ie if it requires a wipe then do the wipe (probably it does not require)
[Google Pixel 6] adewaleandrew:
Thanks
[Google Pixel 6] badabing2003:
Update:

June 06, 2022 v3.3.3 release

Bug Fix: When choosing custom ROM, the ROM file was not being copied to the package directory.

Update Documentation and screenshots.
[Google Pixel 6] Azusasen:
it doesn't work in windows 11 dev
[Google Pixel 6] badabing2003:
Are you talking about Windows 11 Insider builds? Which build?

What exactly does not work? What happens at what point?

Sorry I don't have /use Insider builds, so the only way I can figure this out is by your or others feedback, as detailed as possible.

Don't run as administrator.

Thanks
[Google Pixel 6] kariem112:
Latest version worked perfectly for updating to the June firmware.
[Google Pixel 6] Slim2none4u:
This software just makes life so much easier! Thank you!
[Google Pixel 6] badabing2003:
Update:

June 12,2022 v3.3.4 release

Bug fix on MacOS / Linux

Improved notice message about Fastboot process.
[Google Pixel 6] mkhcb:
I can't seem to get the EXE to open up on Win 11. I run it even as an admin and it just shows me the Pixel Flasher boot screen, but no GUI comes after that on 3.3.4.
[Google Pixel 6] badabing2003:
Don't run it as admin.

Have you used the program previously, or is this the first time you're using?

Navigate to %APPDATA% directory

See if there is a PixelFlasher directory

If there is, zip it up and send it to me, and then delete it the folder and try again, let me know if it still does the same thing.

If there is no PixelFlasher directory, see if Anti Virus or something else is blocking the application.

Run it from command line and see if the command line displays any message.
[Google Pixel 6] RobbyRobbb:
Hey!

My Pixel 6 is bootlooping after an update from SP2 to SQ3. The phone goes from the "Google" screen to the animated "G" screen with the loading bar below for about three seconds, then restarts.

What am i doing wrong?

1. I select the folder with ADB

2. I select oriole-sq3a.220605.009.b1-factory-80f98167.zip

3. I process it and then patch the boot file

4. I select the patched boot file

5. I select Keep data

6. I click Flash

Spoiler content hidden.
[Google Pixel 6] badabing2003:
You're doing everything correctly, but you have a suspect Magisk module in ViPER4AndroidFX that has caused bootloops in the past during updates.

If you're phone is getting adb briefly, you can try the disable Magisk button, if no adb, there is a key combination, I think volume down when you see the logo (can't remember, double check).
[Google Pixel 6] RobbyRobbb:
Flashing the non-patched boot file solved the problem.

I'm generally curious as to why the system boots properly when manually flashing Magisk and said problematic module but not when flashed via your program. Is it a complicated procedure required tog get this to work? How is this procedure different from the process that happens when manually flashing?
[Google Pixel 6] badabing2003:
PixelFlasher flashing is really not that different from manually flashing.

Go to the following path on your PC

%AppData%\PixelFlasher\factory_images\oriole-sq3a.220605.009.b1

Compare the two files flash-all.bat (manual file) and flash-phone.bat (PixelFlasher file)

The differences are as follows:

1- PIxel flasher adds -s DeviceID to fastboot commands, this is done to reference the specific device, in case you have multiple devices connected to your phone, this addition targets the correct device, You can't have multiple devices connected using the manual flashing with flash-all.bat, you would get an error.

This is a fastboot switch, and there is no way this could cause any issues, in fact it makes it more flexible / robust.

2- If you choose flash options (example disable verity or flash to both slots), which I suppose you don't, then those options would be added to fastboot command. Again this should not be causing an issue for you, as you don't set those.

3- -w is removed if you chose Keep Data, so that your phone is not wiped. This is from all the referenced guides and standard step you would do if you were doing things manually.

4- --skip-reboot option is added to the line that flashes the image, the line:

fastboot flash radio radio-oriole-g5123b-100840-220505-b-8544885.img

This is to keep the phone in bootloader mode after flashing so that patched boot.img can be flashed before booting to system.

Again there is no way this could make a difference in the form you reported.

5- Flashing of patched boot.img is added if you are flashing patched boot.img

fastboot flash boot pf_boot.img.

The manual way you don't flash patched boot.img, you do that afterwards right? unless you manually modify the file in a similar fashion.

6- Reboot to system is added, to finally boot to system.

As you can see, there is really not much different.

If you browser the magisk general thread, you'd see many cases where people experienced bootloops by keeping certain magisk modules enabled.

It does not mean that it happens in every version, it all depends on the changes introduced in the new version that might not work well with an older module.

It's always a good idea to temporarily disable such modules and then enable them back.

That is why PixelFlasher has added a UI to manage your modules.
[Google Pixel 6] badabing2003:
Update:

June 26, 2022 v3.3.5 release

Fix Lock / Unlock bootloader buttons being reversed.
[Google Pixel 6] miss:
In June everything went well, now with the July ota, magisk asks me to reinstall the application, and I lose root

edit. restart the phone and it works, thanks for your application
[Google Pixel 6] badabing2003:
You applied OTA?

Although PixelFlasher supports flashing OTA in advanced mode, it's there for convenience for power users, the recommendation is always to use the factory image, much less issues and easier.

In any case, please provide a support.zip file (in Help menu) and I'll take a look at it to see what happened.

What image you applied in what sequence to which slot ...
[Google Pixel 6] miss:
not, rom stock july