yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] badabing2003:
Sorry to hear that, I supposed you already tried Android Flash Tool.

You might want to post your problem in this thread

There are lots of knowledgeable people in there that know way more than I do.

Good luck, and if you manage to fix it, post back.
[Google Pixel 6 Pro] sjgoel:
My phone is working fine after I flashed A13 as usual using Pixel Flasher, which means bootloader was flashed only on 1 slot. Should I just let it continue for now, or what can I do to flash bootloader on the other slot?
[Google Pixel 6 Pro] Lughnasadh:
You should flash the bootloader to the other slot.

Assuming you are on a Pixel 6 Pro, you can use these commands:

adb reboot bootloader

fastboot flash bootloader --slot all bootloader-raven-slider-1.2-8739948.img
[Google Pixel 6 Pro] sjgoel:
Thanks. Yes I am on 6 pro.

I'm rooted, so magisk would not cause any issues or should I uninstall it before?
[Google Pixel 6 Pro] Lughnasadh:
Magisk won't cause any issues.
[Google Pixel 6 Pro] sjgoel:
Worked perfectly. Thanks.
[Google Pixel 6 Pro] Lughnasadh:
Groovy 😎
[Google Pixel 6 Pro] heij20032003:
so I should do all others as usual, but add the following steps?

- enabled 'advanced option'

- click 'flash to both slots'
[Google Pixel 6 Pro] heij20032003:
I want to keep my data, and then did a trial run by using pixel flasher 3.5.0

chose

- keep data

- flash on both slots

did not chose

- force

but the warning said that flash option: 'force' is chosen and will wipe the data

but I want to keep my data

what should I do now?
[Google Pixel 6 Pro] Thebear j koss:
End that session. Tick verbose.
[Google Pixel 6 Pro] badabing2003:
Sorry about that, I had a silly mistake, I'll release a quick fix, the dialog is wrong, you can proceed if you have not selected force.

The code wrongly checked the Flash both Slots flag to display that message instead of checking force flag.
[Google Pixel 6 Pro] badabing2003:
Update:

Aug 21, 2022 v3.5.1 release

Fix: Incorrect warning is displayed when Flash on both slots is selected.

The contents of the generated flash-phone.bat file will now be displayed on console even if verbose option is not selected, this helps the user know exactly what commands would be executed before clicking the OK button.
[Google Pixel 6 Pro] heij20032003:
no sorrry......

this app has made my life much more easier......

thanks a lot indeed for the quick fix
[Google Pixel 6 Pro] badabing2003:
New Release:

Aug 24, 2022 v3.6.0 release

When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.

Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.

Improved tooltips.
[Google Pixel 6 Pro] crypticc:
Hi there

Normally I flash OTA or manually flash full system image using edited flash_all.bat.

However this time I tried this tool... It failed.

I am not too concerned as it's a soft brick as using long-press power and the usual keys got to fastboot and it's clear from the fastboot versioning that nothing was actually flashed to bootloader.

I'm recovering by manual fastboot flash of the full system images, but posting here in case useful to anyone.

Kind regards

Chris

Downloaded latest A13 full factory image.

In PixelFlasher I selected :

Platform tools (freshly downloaded and unpacked)

Phone in ADB connected devices

Pixel Phone Factory Image "raven-tp1a.220624.021-factory-d8ddfdca.zip" (freshly downloaded)

Selected a boot.img (freshly unpacked from above image

"dry run",

and finally "flash pixel Phone".

When prompted I manually patched boot.img using Magisk using file install method, and then adb pull to keep on c: drive.

Seeing that dummy run work, phone going to fastboot etc. and rebooting the phone I then attempted a full flash.

I selected :

as above - all were still selected from previous "dry run"

I selected "Keep data" to deselect the previous dummy ru

"Flash Pixel Phone" again.

When prompted I re-pushed the Magisk updated magisk_patched IMG file into /sdcard/Download.

Phone rebooted and attempted to flash but completed

much

too quickly - so clearly didn't flash anything

After a few "Google" logo and then a few more timed reboots went rebooted alternating between the dreaded your device maybe corrupt message, and the regular your device maybe unlocked message.

From logs it looks like the scripts created by the tool attempted to flash nothing.

Attached script created by the tool and log copy-paste below.

I've edited both only to obfuscate my deviceID

As noted above I'm now flashing manually so assuming that works this isn't to invite urgent response - but FYI only.

-----

2022-08-29 13:39:53 Flashing device XXXXXXXXXXXX...
debug: "C:\Users\chris\AppData\Roaming\PixelFlasher\factory_images\raven-tp1a.220624.021\flash-phone.bat"
C:\Users\chris\AppData\Roaming\PixelFlasher\factory_images\raven-tp1a.220624.021>chcp 850
Active code page: 850
unknown partition 'bootloader'
fastboot: error: cannot determine image filename for 'bootloader'
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Sending 'radio_a' (82772 KB) OKAY [ 1.884s]
Writing 'radio_a' (bootloader) Flashing pack version g5123b-102852-220720-M-8851166
(bootloader) Flashing partition modem_a
OKAY [ 0.190s]
Finished. Total time: 2.079s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.001s
rebooting to bootloader ...
< waiting for XXXXXXXXXXXX>
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.001s
Sleeping 5-10 seconds ...
flashing pf_boot ...
Sending 'boot_a' (65536 KB) OKAY [ 1.495s]
Writing 'boot_a' OKAY [ 0.136s]
Finished. Total time: 1.634s
rebooting to system ...
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
2022-08-29 13:40:13 Done!
Flashing elapsed time: 38 seconds
[Google Pixel 6 Pro] badabing2003:
Thanks for reporting this, and sorry for your troubles.

Some things are not adding up and the best way to understand exactly what went wrong is to analyze the logs.

You can create sanitized logs (ID and names redacted) in PixelFlasher by going to the Help Menu and selecting "Create sanitized support.zip file"

What is not making sense to me is that you should not be prompted during the flashing phase to transfer files to the phone or to manually patch them.

The logs would really help me see if there was a corner case that somehow caused this.

Thanks
[Google Pixel 6 Pro] crypticc:
Hey there

I've since updated phone manually and turned off PC. Will the logs still be there? If so happy to provide later tonight.

Regarding the promptb and my mention of transferring files I think the file transfer unnecessary and actually both material to what happened... It is because I couldn't find how to permission Shell as SU and so the app couldn't find Magisk. The prompt was to manually open Magisk and patch the boot directly there. I couldn't find where your app had transferred the boot (it had deleted the one I'd previously transferred and patched) so I pushed the boot.img from the .zip myself. Looking again I needn't as when I looked at my phone after fixing I could see your app had pushed to the Download folder. Either way the patched file was found by your app and it continued when I selected okay.

I wonder if it had something to do with doing the dry run first. I ran it twice,

regards

Chris
[Google Pixel 6 Pro] badabing2003:
Yes, you can still generate logs, you don't need a phone, it would help; thanks.

Dry run should not cause any issues, you can run it as many times as you want, all it does is it echoes what it might execute had you chosen a real run, with the exception of adb and fastboot reboots which it executes to make sure the SDK is functional.

What you're describing about for transfer should happen during the patching process, not flashing. In any case the logs should paint a good image of what might have happened.

Thanks.
[Google Pixel 6 Pro] crypticc:
Support log attached. I must say, it's very forward thinking of you creating a tool that sanitizes logs before sending, Well done you :-D

One observation... in the logs I can see a warning (not an error) of :

WARNING! Encountered an unexpected fastboot line while parsing C:\Users\REDACTED\AppData\Roaming\PixelFlasher\factory_images\raven-tp1a.220624.021\flash-all.sh
fastboot update --slot=all image-raven-tp1a.220624.021.zip

That was when I was editing the .zip to include --slot=all command that I now understand PIXEL6 doesn't allow. (see other thread on that)

But I can see your tool protects me from that and builds it's own flash script but I do wonder if that "warning" should be an "error and stop"

After that however the logs look same as I recollect

You can see that it flashes bootloader, modem, boot, and then complains about image filename for bootloader, flashes radio and then zips through the rest without flashing anything much at all except radio_a, boot, boot_a and that's it. Concluding in about 38 seconds is about how long it took

Thanks again
[Google Pixel 6 Pro] badabing2003:
Oh gosh, you actually modified the zip file?

It kind of defeats the whole point of PixelFlasher.

PixelFlasher has the necessary options to add --slot=all

And there is so much protection I can add, what if you deleted lines, I would not know that you deleted or changed order of things, the whole premise is that I treat stock flash.bat as source of truth.

With the current implementation, I discard anything I don't recognize, I suppose I can make it error out and not let you flash.

Yeah, because of you modifying the zip, it did not flash the the image or anything it discarded.
[Google Pixel 6 Pro] crypticc:
What can I say? I get paid to find breaks and then find fixes for things.

But yes, in hindsight I shouldn't have done that, but you might consider changing that warning to an error and then stop.

No harm done in the end for me as I had the (somewhat incomplete) skills to flash everything back manually.

But just checking, when you say your tool adds --slot=all. I've since learned shouldn't do that when flashing update.zip on pixel6 . Apparently individual partitions okay, but not the whole update zip.

Links>

Post in thread '[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet' https://xdaforums.com/t/guide-pixel...ate-root-pass-safetynet.4356231/post-87361165

Post in thread 'Developer Support Android 12 images (August 29, 2022) - PSA about Android 13 in OP - Unlocking the Pixel 6 Pro bootloader & central repository' https://xdaforums.com/t/developer-s...ader-central-repository.4352027/post-87309913

Thanks though,

I will try the tool again next FW upgrade. Worked great apart from some self inflicted pain.

Chris
[Google Pixel 6 Pro] niko26:
@badabing2003 - trying to get this working on my Mac OSX 10.14.6.

When trying to launch PixelFlasher it immediately shuts down. Any idea? Any further information you need?
[Google Pixel 6 Pro] niko26:
Ah.. it looks like OSX 15.x is necessary. :-(

/Applications/PixelFlasher.app/Contents/MacOS/PixelFlasher ; exit;
As-MacBook-Pro:~ nik$ /Applications/PixelFlasher.app/Contents/MacOS/PixelFlasher ; exit;
Traceback (most recent call last):
File "PixelFlasher.py", line 3, in <module>
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "Main.py", line 17, in <module>
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "darkdetect/__init__.py", line 17, in <module>
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "darkdetect/_mac_detect.py", line 7, in <module>
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "ctypes/__init__.py", line 8, in <module>
ImportError: dlopen(/var/folders/qv/b85dlxpj0jl0162fg261cvmm0000gn/T/_MEIEAFmD5/lib-dynload/_ctypes.cpython-39-darwin.so, 2): Symbol not found: _ffi_closure_alloc
Referenced from: /var/folders/qv/b85dlxpj0jl0162fg261cvmm0000gn/T/_MEIEAFmD5/lib-dynload/_ctypes.cpython-39-darwin.so (which was built for Mac OS X 10.15)
Expected in: /usr/lib/libffi.dylib
in /var/folders/qv/b85dlxpj0jl0162fg261cvmm0000gn/T/_MEIEAFmD5/lib-dynload/_ctypes.cpython-39-darwin.so
[3682] Failed to execute script 'PixelFlasher' due to unhandled exception: dlopen(/var/folders/qv/b85dlxpj0jl0162fg261cvmm0000gn/T/_MEIEAFmD5/lib-dynload/_ctypes.cpython-39-darwin.so, 2): Symbol not found: _ffi_closure_alloc
Referenced from: /var/folders/qv/b85dlxpj0jl0162fg261cvmm0000gn/T/_MEIEAFmD5/lib-dynload/_ctypes.cpython-39-darwin.so (which was built for Mac OS X 10.15)
Expected in: /usr/lib/libffi.dylib
in /var/folders/qv/b85dlxpj0jl0162fg261cvmm0000gn/T/_MEIEAFmD5/lib-dynload/_ctypes.cpython-39-darwin.so
[3682] Traceback:
Traceback (most recent call last):
File "PixelFlasher.py", line 3, in <module>
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "Main.py", line 17, in <module>
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "darkdetect/__init__.py", line 17, in <module>
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "darkdetect/_mac_detect.py", line 7, in <module>
File "PyInstaller/loader/pyimod03_importers.py", line 495, in exec_module
File "ctypes/__init__.py", line 8, in <module>
ImportError: dlopen(/var/folders/qv/b85dlxpj0jl0162fg261cvmm0000gn/T/_MEIEAFmD5/lib-dynload/_ctypes.cpython-39-darwin.so, 2): Symbol not found: _ffi_closure_alloc
Referenced from: /var/folders/qv/b85dlxpj0jl0162fg261cvmm0000gn/T/_MEIEAFmD5/lib-dynload/_ctypes.cpython-39-darwin.so (which was built for Mac OS X 10.15)
Expected in: /usr/lib/libffi.dylib
in /var/folders/qv/b85dlxpj0jl0162fg261cvmm0000gn/T/_MEIEAFmD5/lib-dynload/_ctypes.cpython-39-darwin.so

logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...7 completed.
[Google Pixel 6 Pro] badabing2003:
Yes, and PixelFlasher flashes image one slot at a time.

You should check the release notes and the usage in the main thread.

I don't have a MAC, PixelFlasher is built on macOS Catalina version 10.15.7 running in a docker container.

You can build it yourslef if you want, the steps are on the Github page.

If you do, let us know how it goes.
[Google Pixel 6 Pro] niko26:
Oh wow.. You can run Mac OS in a docker container??

I'll see... I'm at holidays and only have my Mac with me, and really don't want to put the efforts into it. Holidays you know. ;)
[Google Pixel 6 Pro] niko26:
@badabing2003 - back from holidays - now on a Windows machine again. In the meantime my damned P6P has installed the July second patch (not A13!) and I lost root. Now I am trying to install the July patch again, but I am facing some difficulties:

1. PixelFlash started, adb selected and populated correctly

2. ADB device correctly selected

3. Pixel Phone Factory image selected, extracted/processed

4. selected the according boot.img, patched it, by running Magisk, selecting the proper boot.img

5. Chosen the corrected patched boot.img

6. Keep Data mode

7. clicked on Flash Pixel Phone

8. phone reboots into "Fastboot mode" where I can choose which mode I want to continue with

9. PF shows:

Waiting 10 seconds ...
2022-09-04 00:36:01 No Device is selected!

2022-09-04 00:36:01 ERROR: Unable to detect the device.

What did I do wrong?

Edit:

Okay, different USB cable - and everything works.

Now the hell... why does rebooting the phone, sending ADB commands work via the dodgy USB cable and other commands do not work or the phone is not correctly detected later?!?
[Google Pixel 6 Pro] badabing2003:
Sounds like you have bad fastboot drivers.

Try the dry run, it should reboot couple of times and then go back to system, if it doesn't it means that your fastboot drivers are no good.
[Google Pixel 6 Pro] niko26:
Fastboot drivers = platform tools?

BTW, the fix is:

Edit:

Okay, different USB cable - and everything works.

Now the hell... why does rebooting the phone, sending ADB commands work via the dodgy USB cable and other commands do not work or the phone is not correctly detected later?!?
[Google Pixel 6 Pro] badabing2003:
Because adb and fastboot they need different drivers, one could work even if the other is not working.
[Google Pixel 6 Pro] niko26:
But I didn't change any drivers. All I did was using a different USB cable. *confused*
[Google Pixel 6 Pro] badabing2003:
I can't say for sure, but dodgy cable behavior is unpredictable, those should be tossed away.

It could be just a little jiggle of the desk, / cable / phone and it could fail.

Or it could be the power used, sometimes different USB ports make a difference, some have better success with USB 2 port over newer USB 3.
[Google Pixel 6 Pro] badabing2003:
New Release:

Sep 04, 2022 v3.7.0 release

New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.

New Feature: Install compatible apk file onto the device from PixelFlasher menu.

Check Android Platform Tools version and warn if it is old.

Block flashing when stock flash_all.bat file is tampered with.

Don't bother with flashing if bootloader is locked.

More validations and exceptions handling.

Improved logging.
[Google Pixel 6 Pro] banshee28:
Just wanted to say I once again used Flasher to update, this time from my August to Sept Factory image and it worked perfectly.

Since I originally went from A12 > A13 on only ONE slot, I first took these steps to manually flash bootloader to both:

adb reboot bootloader
fastboot --slot=other flash bootloader bootloader-raven-slider-<latest>.img
fastboot set_active other
fastboot reboot bootloader
fastboot set_active other
fastboot reboot bootloader
fastboot reboot

I then used Pixel Flasher normally (using Linux) and updated to this new build, allowed it to install Magisk for me (Very cool) patched, and let it do its thing. A few mins later it was all patched and working great! :cowboy:
[Google Pixel 6 Pro] badabing2003:
Thanks for the update.

You could have just selected `Flash on both slots` in PixelFlasher and you would have been done,
[Google Pixel 6 Pro] Thebear j koss:
Worked perfectly once again. Easily updated my platform tools thru the Pixel Flasher. 👍🐻
[Google Pixel 6 Pro] nibera:
Hi guys, I wanted to ask you being now on android 13 QPR1 beta on pixel 6 pro, with bootloader locked, I wanted to go back to stable android 13, I wanted to use pixelflasher for the first time, any tricks? from the info I read from the fastboot screen I see that slot B is active, and right?
[Google Pixel 6 Pro] badabing2003:
With bootloader locked you can't flash in PixelFlasher. The only thing you can do is sideload OTA.

And I have no idea what would happen to your phone if you attempt it, I personally wouldn't, if anything goes wrong and bootloader is locked you'll have a nice door stopper.

If unlocking the bootloader is an option, and of course that means wipe, I believe you should be able to go back to Android 13 release, I doubt that there is anything in 13 QPR1 that is not downgrade-able, of course you'd better check in 13 QPR1 threads.

After going back to A13 release you can lock your bootloader again, if that is what you want, and that means another wipe.

If you're going this path, make sure you flash both slots with A13 release just to be on the safe side.
[Google Pixel 6 Pro] nibera:
Yes, I know that I have to unlock the bootloader first and consequently lose all data, ok.

I wanted to understand if after unlocking the bootloader I can go back to stable android 13 using pixelflasher, in this case I have to select the check mark on flash on both slots in pixelflasher.
[Google Pixel 6 Pro] nibera:
this should be the pixelflasher configuration always after unlocking the bootloader, right?

just click on FLASH PIXEL PHONE and everything starts.

am I wrong something?
[Google Pixel 6 Pro] badabing2003:
yes, but as you can see the Flash button is disabled, you'd have to select the boot.img in the list first.

But please check A13 QPR1 threads to make sure there is nothing in it that prevents rollback to stable A13, there shouldn't be, but I don't know as I have not read up on A13 QPR1
[Google Pixel 6 Pro] nibera:
ok thanks, check android 13 QPR1 threads if there are any restrictions.
[Google Pixel 6 Pro] OzBoy1:
Quick question, updated to 13 and used PF, flashed both slots all good. So I want to update to the latest without loosing data, my question is do I need to flash both slots again?

Thanks for your help and absolutely love how easy PF makes flashing, (y):)
[Google Pixel 6 Pro] badabing2003:
no you don't, you can just flash without choosing that option.
[Google Pixel 6 Pro] Alekos:
Every few years or so, here on xda, an app (or script) comes along that really changes the game.

This happens when an app is released with the certain "xda" development mindset: clear vision and a need for the apps' functionality, consistent development (with fast improvements), community feedback that's always respected by the dev and suggestions sometimes added to the app, and a finished product that is used by both newbies and veterans.

Seriously, this reminds me of the Nexus-7'13/Nexus-5 days where there were so many dedicated devs that created some awesome apps (kernel managers, partition scripts and other apps). It's awesome to see @badabing2003 doing cool things and just know that a ton of people really enjoy your work.
[Google Pixel 6 Pro] DeanO74:
Well lesson learned for me. I followed the directions to the letter after weeks of studying these forums and all day studying the directions, and bricked my new 6 pro I just dropped a grand on. Just have a battery symbol and no reaction to anything now.
[Google Pixel 6 Pro] Thebear j koss:
So you didn't follow directions to the letter. Because if you had, you wouldn't be where you are at now. Plus you give absolutely no details so no one can help you.
[Google Pixel 6 Pro] badabing2003:
Which directions did you follow?

What did you observe at what stage?

Did you do anything outside any instructions you followed in an attempt to remedy the situation? If yes what did you do and what did you observe?

Just saying that you have a brick is not going to help you receive any help, as in anything related to hacking / rooting the devil is in the details, every detail matters.
[Google Pixel 6 Pro] Alekos:
It's very difficult to brick a Pixel - unless you flash an incorrect image through fastboot (fastboot doesn't have the safeguards in place like updating ota image via adb in recovery). PF also has some fail-safes but we don't know what you did.

If you are seeing a battery signal - unplug the phone and remove your case. Hold power and volume down for 30 seconds. Keep trying this procedure - if you can get into fastboot, your phone is most likely fine (at that point go directly to flash.android.com and then report back on what you are trying to do). At the very least, Google will replace your phone either through 14-day return policy or warranty. I know its frustrating when things like this happen but you have a lot of people here willing to help you.
[Google Pixel 6 Pro] DeanO74:
All the details I can offer I did in it's bricked, unresponsive with a battery symbol on screen. No further info can be obtained. And yes I did follow all directions to the T. I will add too that the app crashed on me twice. Maybe the developer included an error logging in the app, but it's not really of much consequence now, I'll be attempting to return it to stock this morning if it will fastboot after a charge following overnight battery drain.
[Google Pixel 6 Pro] badabing2003:
You keep on repeating the same thing

What directions? what happened at which step?

You have not answered any of the points from my request.

You're posting in PixelFlasher thread, so I'm assuming that you only used the app and did nothing else, if that is the case, please provide support.zip file, that should tell me the full story.

If you did anything else outside the program, you'd have to provide details of those as well.

You can create support.zip without the phone, all you have to do is launch PixelFlasher, go to the help menu and select "Create a Sanitized support.zip"