yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] badabing2003:
I'm sorry, I still have no idea what you did, please provide a support.zip file.

Thanks
[Google Pixel 6] badabing2003:
New release:

July 18, 2022 v3.4.0 release

Improvements to the boot extraction / categorization.

Live boot option directly from the selected boot.img UI, even though it was possible to live boot previously through the advanced menu, it is now super easy to select a boot.img (patched or otherwise) and Live boot to that image with a click of a button.

Added warning message in the splash screen and the help about menu, to inform users not to fall for opportunists who are claiming to be the developer of PixelFlasher with a donate button next to the download link. Reminder to all, this program will always be free, ad free, donation free; you should not be solicited for any form of payment.
[Google Pixel 6] tom1807:
Just a feedback.

Used the PixelFlasher for the update to Android 13 on my Pixel 6. No problems to report, smooth as usual.

Great work.

Cheers

Tom
[Google Pixel 6] Snow_ball:
I second this - with root and wallet working
[Google Pixel 6] :
Edit: Resolved... Turns out the damn app was patching an old magisk. I manually patched my boot.img with the latest version and my phone is fine now.
[Google Pixel 6] Project_WHaT:
I just tried to flash from patched Android 12 to patched 13, but at the end of the flash process, the console says everything finished and is rebooting into system. However, my Pixel 6 rebooted to Fastboot mode and for "Enter reason" it says "boot failure"

What should I try to do at this point? I've attached the support zip. Thanks

EDIT:

I noticed other people have had similar problems online that say "Error!", but mine is slightly different:

NOS Production: yes
Device state: unlocked
Boot slot: a
Enter reason: boot failure

I'm afraid to boot or do anything at this point since I've read a lot of articles about how downgrading to 12 after 13 can permanently brick the device, so I'm refraining from trying anything at this point

EDIT 2:

I've found the issue.

https://xdaforums.com/t/pixelflashe...g-managing-pixel-phones.4415453/post-87168183

When patching using the PixelFlasher, it uses the kernel which was on a much older version.

EDIT 3:

For those who encounter a similar situation, to recover from this, I just followed the steps in "Install/Update Factory Image keep data, wipe data, or use @badabing2003 PixelFlasher", specifically the "Flash Factory Image Keep Data" category that can be found here:

https://xdaforums.com/t/guide-root-pixel-6-with-magisk-android-13.4388733/
[Google Pixel 6] tom1807:
Thought I better ask before doing something wrong.

From my understanding, after updating to A13 (active slot: A) A12 should be still on slot B or minimum the previous bootloader "bootloader-oriole-slider-1.2-8318357".

For comparison the current bootloader of A13 is "bootloader-oriole-slider-1.2-8739948".

Saw some reports, if something goes wrong, mobile will boot from Slot B which still contains the previous bootloader and the mobile won't boot anymore.

To be prepared, I thought flash the bootloader also to Slot B

Would be the following steps correct?

1. Select the Image in PixelFlasher

2. Flash Mode select "Custom Flash"

3. Select bootloader, select the correct, extracted bootloader "bootloader-oriole-slider-1.2-8739948"

4. Select "Flash on both slots"

The last is not quite clear to me.

Or should I just "Set Active Slot" to A and then flash the bootloader

Or is the correct way "Flash to both slots"?

Cheers

Tom

Edit: NVM, I used fastboot and flashed by the command "fastboot flash bootloader --slot=all bootloader-oriole-slider-1.2-8739948.img"
[Google Pixel 6] badabing2003:
Flash to both slots does exactly what you did manually.

Switching slot and then flashing to that slot only would have worked as well, but stay in fastboot mode if the second slot is not bootable so that you can flash, otherwise the system will revert back to the good slot.

I have seen cases where flash to both slots of full image (as opposed to just boot.img) sometimes fail when resizing partitions on the older slot, I'm not sure why this actually happens, perhaps the other partition is really old and geometry is way too different, although I would have expected that Google's flashing routine would handle that gracefully, perhaps it's not meant to be used with full image.

If anyone has theories or knows why that happens please let me know if I should block flashing both slots for a full image or at least warn the user.
[Google Pixel 6] badabing2003:
Looking at your logs I see that you are using older Android SDK and older Magisk.

SDK Version: 31.0.3-7562133

Magisk Version: 92546e8a:MAGISK (23016)

I would update both to the latest and try again.

I don't know what you mean by this, it uses your current magisk to patch the boot.img that you select.
[Google Pixel 6] badabing2003:
New Release:

Aug 19, 2022 v3.5.0 release

Add support for fastboot --force flag (to help fix partition issues, caution it will wipe data) see this.

Split image flashing to all slots into two separate single slot flashing to bypass a Google bug on Pixel 6* devices, see this by @Namelesswonder.
[Google Pixel 6] RobbyRobbb:
I want to ask this to make this absolutely clear; is it possible to flash Android 13 on a Pixel 6 with an unlocked bootloader (but no root) and

keep

the data with this tool? Since A13 contains a new bootloader, and since re-locking a bootloader wipes all data, i want to make sure that i really can upgrade to A13 without losing everything.
[Google Pixel 6] Griffinx:
Hi @badabing2003 , Thanks for updating PixelFlasher. Can you confirm that if I follow your steps 1-15 here on a A12 rooted Pixel 6 that all will be well and Ill get to keep my data.
[Google Pixel 6] badabing2003:
Yes, it is possible, although I would suggest you flash to both slots with PixelFlasher 3.5.0 to make sure the Anti rollback does not bite you in the future if you accidentally boot to the older slot which has A12 and it will be prevented.

The steps do work, but keep in mind they were written for Raven, so for Pixel 6 you need to replace Raven with Oriole

However it's much better to use PixelFlasher 3.5.0 and flash to both slots, PixelFlasher 3.5.0 can handle a Google bug that failed flashing to both slots by flashing one slot at a time when you choose flash to both slots.

Either approach is fine, the latter is easier and you'd have full A13 on both slots.
[Google Pixel 6] tom1807:
Please help me to clarify this. Under which condition is this necessary?

When flash to both slots? Or when a partition resize is necessary.

Will it wipe data on both slots? Even if there is a problem only on one slot?

Cheers

Tom
[Google Pixel 6] badabing2003:
That option is almost never necessary, don't select it.

That option helps when partition resizing fails, but it's known to wipe the data.

Although technically it is possible to resize partitions without wiping, it is much more laborious process and time consuming, perhaps Google didn't want that or perhaps they chose that for security reasons just as they did for unlocking the bootloader.

I don't believe there are two data partitions, so if it is wiped it would be gone.

@V0latyle would know a lot more about it, I found out about it from his an earlier post.
[Google Pixel 6] 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] Griffinx:
I successfully updated from A12 to A13 with PixelFlasher. I disabled the Magisk module volte-properties for Pixel beforehand and re-enabled it again afterwards and everything worked fine.

Thanks to @badabing2003 again for creating this app.
[Google Pixel 6] navaneethnk:
iam using android 13 on pixel 6 i want to root my phone ,is it possible in pixel flasher ??
[Google Pixel 6] badabing2003:
Yes, follow the basic usage in the main thread.

If your inactive slot is from A12, then enable advanced options and choose "flash to both slots" to protect yourself from accidents, as A12 bootloader is no longer bootable, and flashing to both slots will make sure that both slots have the current bootloader.
[Google Pixel 6] navaneethnk:
ok ty :)
[Google Pixel 6] navaneethnk:
if i flash on both slots will it take more space on phone?
[Google Pixel 6] kariem112:
works great, update from 12 to 13, flash to both slots (latest version of pixelflasher). Thanks!
[Google Pixel 6] navaneethnk:
Does flashing phone wipe out esim profiles ???/​
[Google Pixel 6] tom1807:
Nope , I have an eSim and after each update, regardless whether Android 12 flash or update to A13, the eSim was not wiped.

Cheers

Tom
[Google Pixel 6] navaneethnk:
Thanks Tom for clearing my doubt
[Google Pixel 6] 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] freonchill:
Typically when an update came out, it would annoy me for several weeks until I used Pixel flasher to manually update from a factory image. If the phone tried to update the ota update, it would error out.

A couple weeks ago it randomly said at the updated processed and I just needed to reboot.

Thinking it was an error, I rebooted and found myself unrooted.

It was the SQ3A.220705.004 update.

I looked on here and didn't see this happening to anyone else, so thought I would ask the question.

Can I use pixel updater to re-root without forcing a data wipe?

If so, would I download the SQ3A.220705.004 factory image and go through the boot.img magisk root patch and then have it reboot?

Thanks in advance.
[Google Pixel 6] badabing2003:
Of course you can use PixelFlasher to re-root,

Make sure latest magisk manager (I personally prefer canary) is on you phone and is not hidden, because you are not currently rooted, when you click on patch in pf, it will transfer the file to the phone, launch Magisk and wait for you to click on the patch in magisk (pf will guide you) once done you click ok in pf and it will pull back the patched image and if you select it, it will use that during flashing.

Since you are still on Android 12, you can flash July image and remain on A12 or flash August image and move to A13, if you choose to go A13, make sure you flash to both slots, as there is no going back to A12, hence your A12 slot will not be bootable with older bootloader, that's why it's best to flash to both slots with A13
[Google Pixel 6] thekdub:
I was using Pixel Flasher to flash the August update and it failed in the middle of the flashing process (maybe when I picked up the phone and it possibly jostled the usb cord). I tried to flash again but it gave me a warning message:

Unless you know what you are doing, if you continue flashing

you risk bricking your device, proceed only if you are absolutely

certian that this is what you want, you have been warned.

Unsure how to proceed.
[Google Pixel 6] thekdub:
I also tried to restart the patching process, but no longer have a connection with adb.
[Google Pixel 6] badabing2003:
@thekdub

Looking at your logs.

You started with July A12,

You were on slot a

You tried to flash Aug A13

With patched boot.img

You managed to flash the bootloader to slot a ...

The process failed when flashing product to slot a, possibly as you pointed out due jostled usb cable .

When it was flashing product, the device was in fastbootd mode

The device is now detected to be in bootloader mode or fastbootd mode.

The fact that it is reported as:

Device Model:

Device is Rooted: None

Device Build:

Device Active Slot:

Device Bootloader Version:

Device Mode: f.b

Suggests that It's in limbo and not reporting device details.

We want the device either in adb mode or fastboot mode reporting info.

Have your tried rebooting your phone? long pressing the power ?

Does it always go back to this mode?

You can try power cycling if you can, and hit the refresh button in PixelFlasher, and then hit the Info button

If you get info, you're good, either in adb or fastboot is fine,

Then you want to repeat the flashing, but make sure you select flash to both slots.

report back,

We can try few other things, but let's see if you can put the device in proper adb or fb mode
[Google Pixel 6] dinuka_haxxor:
Hi I was trying to update my bootloader by using Google method but ..

PS F:\torrentz\platform-tools_r33.0.3-windows\platform-tools> fastboot --slot=other flash bootloader D:\oriole-tp1a.220624.021-factory-4bd6cec7\oriole-tp1a.220624.021\bootloader.img

Warning: bootloader does not support slots, and slot b was requested.

Sending 'bootloader' (11554 KB) OKAY [ 0.419s]

Writing 'bootloader' FAILED (remote: 'No such file or directory')

fastboot: error: Command failed

It gives me this error. And previously I wanted to sideload an ota but it was stuck in verification stage and I aborted doing that however I flashes the factory image thru PixelFlasher and it worked perfectly... So maybe there is a issues with my fastboot drivers ? Or platform tools ?

And so is it safe to try updating my bootloader thru PixelFlasher tool ? (I have already flashed the factory image of android 13 thru the PixelFlasher btw)
[Google Pixel 6] tom1807:
Seeing your path, this could maybe an issue for a too long filepath.

I created a folder called ADB and have all necessary files from platform SDK there.

Never faced any problem.

Cheers

Tom
[Google Pixel 6] badabing2003:
I don't know if you renamed the bootloader file, but the correct filename is: bootloader-oriole-slider-1.2-8739948.img (renaming is not a problem, just making sure you renamed this file and not another file)

In any case if Pixelflasher is flashing factory fine, then I would say there is no issue with your phone or your drivers.

You can flash the bootloader through PixelFlasher, or you can flash OTA, but my preferred method is to flash Factory image to both slots.
[Google Pixel 6] kiwi32:
Just wanted to say, I just bricked my Pixel 6. What a mess.

Was trying to upgrade to Android 13 with PixelFlasher. I had read the warning regarding the dual slot issue.

PixelFlasher hung while waiting for a fastboot reboot of the device that never came. My phone tried to boot a few times, but failed on the google logo.

I guess it then tried to revert to the other slot that was still on Android 12, since it then became completely bricked.

Complete black screen even while charging.

RMA in progress...

Attached is the log, if it can help anyone.

Spoiler content hidden.
[Google Pixel 6] badabing2003:
Sorry about your troubles.

Looking at the above log

Device Bootloader Version: slider-1.2-8739948

Your phone is already on A13 bootloader,

This is only possible if you had already flashed to A13.

Please upload the full support.zip so that I can analyze what might have gone wrong and if it is salvageable.

Thanks
[Google Pixel 6] kiwi32:
Just pmed you the support.zip. Dont waste too much time, it's already on the way back to Google ;)
[Google Pixel 6] badabing2003:
Thanks for the support.zip.

I'd like to get to the bottom of it, in case there is a bug in PixelFlasher or in case I can make improvements for it to abort early on before flashing in cases where it detects weird stuff.

I can already see some improvements that could help.

1- What is your adb/fastboot version? PixelFlasher could not determine the version.

Found Android Platform Tools in C:\Users\REDACTED\adb

2022-08-26 15:14:04 ERROR: Unable to determine Android Platform Tools version.

The version check was for display only, so that we know the version that is being used, however I can add a check in case it is not known or it is an old version, not to allow the device Listing (the Refresh button), hence you won't be able to proceed further than that.

2- Next Issue is, what is your Magisk Version, and is there anything unique different about your Magisk?

PixelFlasher was able to determine that you had Magisk installed and are rooted, however it couldn't get Magisk Version, nor it could list the modules.

There's another improvement I can add to at least warn the user and ask for confirmation, this situation should not happen, if rooted, Magisk should respond to magisk -c

3- On Aug 26th you tried to flash the A13, at the time the active slot was slot a

During the flashing, PixelFlasher reported the following Error.

C:\Users\REDACTED\adb\fastboot.exe: unknown option -- skip-reboot

This is a puzzle, there is a space between -- and skip which should not be there.

But PixelFlasher code does not put a space there.

you can see it from this log entry which is the code it tried to execute

"C:\Users\REDACTED\adb\fastboot.exe" -s REDACTED --skip-reboot update image-oriole-tp1a.220624.021.zip

Perhaps this is another case of adb/fastboot version being too old or something weird about it. (you should always use the latest version)

4- Patching stage, issuing simple adb command of checking if the file exists on the phone caused error, my guess it is related to adb version

I know you can't check the magisk version considering that the phone is being RMA-ed

Can you please check Android sdk version?

adb --version

It should be in C:\Users\<YOURNAME>\adb\

In the meantime I'll work on adding extra checks in the program to block user from continuing when adb version is old or unknown.
[Google Pixel 6] kiwi32:
Hi,

1- I manually changed my adb path to c:\platform-tools in the GUI. My version is platform-tools_r33.0.3-windows.zip.

2- This could be an issue. My phone had a plain Magisk and was rooted, but automatically applied an OTA and restarted overnight. It was not Android 13 from what I can see, but I lost root and Magisk reported N/A after the OTA. So, the fact PixelFlasher reported my phone had root was wrong.

3-That's weird. Fastboot comes in ADB package right ? I was using the latest version from what I gather.

4- My path ADB is old ( Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android). Thus why I manually changed the adb folder in the GUI. Perhaps I forgot to change it initially and that's what triggered the issue ?

Thanks for all the help. This shows your implication to this community. Let me know how I can help.
[Google Pixel 6] badabing2003:
Thanks for the follow up and your feedback.

I think that explains it, the root of the problem being old adb, Looking at the logs, only the adb folder was used during your patching and flashing.

Next version will prevent the use of older adb.

Thanks
[Google Pixel 6] kiwi32:
Sounds like a good idea. Also, double check that the phone is really rooted by trying sudo to prevent point 2.

Thanks,
[Google Pixel 6] kiwi32:
Hey, just an update. I got my replacement phone. Updated the OTA to Android 13, then tried flashing with PixelFlasher. Well, it did exactly the same behavior, waiting for fastboot forever, but this time I figured it out. The drivers of the phone would not be correct by default, the device would display with the red ! in device manager. I had to manually select adb driver for the pixel with every reboot of the phone by PixelFlasher. Could be a useful popup to display if the reboot timeout in the tool fails.

Thanks,
[Google Pixel 6] badabing2003:
Can you kindly provide a support.zip so that I clearly understand the issue?

Thanks

You should also resolve your drivers issue.
[Google Pixel 6] tom1807:
Which drivers did you install? You should only use these. They are for ADB and fastboot boot. Red triangle could be an indication that the drivers are not WHQL signed.

Cheers

Tom
[Google Pixel 6] kiwi32:
Not sure which drivers were used by default, but once manually selecting the correct adb drivers it worked.

I will resend the support.zip

Thanks,
[Google Pixel 6] 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] tom1807:
Umm, is this part referring to Magisk? Because it sounds like you can't flash at all when the bootloader is locked, which is hard to believe.

Cheers

Tom
[Google Pixel 6] badabing2003:
With the exception of sideloading OTA, you can't flash anything if the bootloader is locked.

Previously PixelFlasher did not block flash attempts of such if the bootloader was locked.

Although it was harmless, as it wouldn't change a thing, it was unnecessary.

That is what changed now.
[Google Pixel 6] technoterro:
Hi all !

I've got a strange issue : PixelFlasher cannot see magisk (stable 25.2) on my phone nor the root (root : false).

However, I succeed to upgrade with full factory image of september 2022, and also to keep the root. I flashed both slots with the patched boot.img (the patch line on the user interface).

Everything is fine on my phone, root status Ok, update is ok.

Why PixelFlasher (very great tool by the way) don't see both Magisk and root status ?

(I'm french, please excuse my grammar)
[Google Pixel 6] badabing2003:
Check the main thread, Basic Mode, Point 2, bullet one.

Grant root to ADB Shell.
[Google Pixel 6] technoterro:
Ooh you're right. Sorry, it was so simple. Thx mate !
[Google Pixel 6] SuperSneaky666:
Thanks
[Google Pixel 6] miss:
I want to install android 13, I have abdroid 12.

I select september rom

,bootloader patch

, I select custom rom and flash in the two slots-

but I want to keep the data.

I am doing it right?
[Google Pixel 6] badabing2003:
Why are you selecting Custom ROM?

Are you flashing factory image or some Custom ROM?
[Google Pixel 6] miss:
factory image oriole-tp1a.220905.004-factory-b7d576f5, but I want to flash the two slots

it is ok
[Google Pixel 6] badabing2003:
Yeah normal stuff, not custom rom or anything like that.

Just follow the Basic flow in the main thread and select Flash on both slots.
[Google Pixel 6] miss:
thanks, bababing2003
[Google Pixel 6] miss:
i am flashing android 13 on both slots, but there was no way for pixel fhlaser to recognize me as root.

How can I do to give permission to the root shell, I know that's the reason, but I don't know how to give it permission
[Google Pixel 6] badabing2003:
Main thread, Usage, Basic Mode, point 2

Open Magisk, Go to superuser tab and enable [SharedUID] Shell