yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] badabing2003:
The program is a single binary, just run it and see if it works.

Actually higher versions are not blocked, in case an update requires a new higher version platform tools, the program can't predict the future.

What it does though and disables itself is when it detects a known bad version, it has a blacklisted versions.

PixelFlasher/modules.py at main · badabing2005/PixelFlasher

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

github.com

You ran into an issue because you had two Magisks, one hidden and another not.

All you needed to do was uninstall the hidden one and reboot.
[Google Pixel 6] tom1807:
I am aware that there are maybe higher versions in the future which don't cause problems, but the current available versions are still problematic.

I mean, for me its no problem, I am running ADB 33.0.3, but I imagine that a newbie is pretty clueless what happened.

So, it disables the selection of the Image with the message: "Android Platform Tools version 34.0.1 has known issues, please select another version." "For your protection, disabling device selection." and "Please select valid Android SDK.".

So what's a new user doing then?

My suggestion would have been in this case to add a link in the Console from where a "newbie" could download v33.0.3.

Could be a temporary solution until Google gets their act together.

Nope, I maybe were chosen my wording poorly.

In April I had only Magisk v25 installed.

What i did was, that wanted to start the flashing, but then realized that my Magisk was still hidden.

"Smart" ;) as I was, just before starting flashing, I realized that, went into the "Hidden" Magisk app and selected "Restore the Magisk app" but didn't think of that, that I have to refresh the "Magisk Package Name" under Configuration.

So PF had still the previous package name.

I flashed, lost root, flashed again (with the correct package name) and after the second flash all was good.

In no time I had 2x Magisk installed.

So my suggestion, as you wrote before that Hidden Magisk could cause problems, to show a message to "restore Magisk" again to the original package name.

As I said, these are suggestions, but "could" reduce support questions.

Cheers

Tom
[Google Pixel 6] tom1807:
Ok, I understand your reasoning, so lets see how this turns out for Android 14 and Google SDK.

Thanks a lot for your explanation.

Unfortunately, I don't have the log from April anymore, but I am 100% sure there were no 2 Magisk installed.

In fact, I had that issue in February with 2 Magisk installed after unhiding, but this was not related to PF, even I am on the stable channel of Magisk.

Since then I always make sure when I unhide, that only 1 Magisk is showing up.

That's probably gonna stay a mystery.

Cheers

Tom
[Google Pixel 6] miss:
Actualizaré como siempre.

Detecta mi teléfono como root, lo parcheo y lo inicio

pero el telefono se queda en modo fastboot y pixelflasher dice que no detecta el telefono y no sigue con la actualizacion

Puedes ayudarme por favor

Lo siento, se me habia olvidado actualizar la pc desde cero, y no tenia instalado el controlador usb de google.

Despues de instalarlo, tapa bien, como siempre.

gracias

Mod translation:

I will update as always.

Detect my phone as root, patch it and start it

but the phone stays in fastboot mode and pixelflasher says that it does not detect the phone and does not continue with the update

Can you help me please

Sorry, I had forgotten to update the pc from scratch, and I didn't have the google usb driver installed.

After installing it, cover it well, as always.

thank you
[Google Pixel 6] badabing2003:
New Release:

May 19, 2023 v5.0.0.1 release

#75 Bug fix, when device is in bootloader, type error.

#74 Added Support for Pixel 7a (lynx)

Configuration option to define the file manager to use on Linux (default: Nautilus)

Configuration option to define the terminal emulator to use on Linux (default: gnome-terminal).

Support for additional types of Factory / ROM files.

Checksum validation of firmware / ROM files (if part of the checksum is in the name, otherwise just display)

New advanced option, ability to choose the patching method (with recommendations).

Added Recovery Image patching option.

Advanced option to enable the use of busybox shell (default off).

Auto detect firmware / rom with init_boot and use init_boot for creating patches, this way future firmware don't have to be manually added to PixelFlasher.

Auto detect devices with init_boot and use init_boot for flashing, this way future devices don't have to be manually added to PixelFlasher.

Auto-popup the detected devices dropdown after a scan, to make it obvious to select that next. (Thanks @pndwal for the idea)

Show SHA-256 of adb and fastboot binaries, as Google keeps on messing up Android Platform-tools, it's necessary to whitelist / blacklist specific binaries.

#66, when checking the patched files internal SHA1, provide a confidence rating.

Check, valdiate and warn if necessary when flashing an image patched with Magisk Zygote64_32, as there are wipe implications, provide links to documentation.

Added fastbootd testing to Dry Run.

Added Github actions to build all the targets on Github.

Code refactoring, bug fixes and improvements
[Google Pixel 6] badabing2003:
New Release:

May 25, 2023 v5.1.0.0 release

Support for Android platform tools version 34.0.3, and automatic setting of ANDROID_PRODUCT_OUT environment to workaround a regression introduced in version 34.0.3

Temp workaround to avoid selecting root method patching when Magisk Delta is detected.

Nicer looking / clearer manual patching dialog.

When a Pixel device is selected, PixelFlasher now displays additional information about the device's support.

Things like: Device name, version end date, security update end date, Android version, name, codename, release date, end date.

Boot image list box now displays the applied PixelFlasher patch method.

Auto-resize boot image list box columns for better readability.

Precautionary cleanup up of leftover files on the phone in case root detection software keys on presence of such files.

#77 added attrict3 to requirements.txt in case it helps with certain builds (it shouldn't be needed).

Bug fixes and improvements.

Update:

Patch Release:

v5.1.0.1 release

Exception handling when device is not in the listed Pixel devices.

v5.1.0.2 release

Skip testing fastbootd in dry run mode if Android platform tools version is > 34, is it no longer supports fastbootd (at least 34.0.3 does not)
[Google Pixel 6] V0latyle:
34.0.3? Did SDK Platform Tools finally get fixed?
[Google Pixel 6] badabing2003:
Not really, just partially, I would stick to 33.0.3 unless you are on MAC and fastbootd is not working.

You can see the discussed issues starting here.
[Google Pixel 6] V0latyle:
That's a Texas sized 10-4, good buddy.
[Google Pixel 6] badabing2003:
New Release:

June 01, 2023 v5.2.0.0 release

Update build workflows

Add payload_dumper functionality to PixelFlasher to handle OTA files, thanks to vm03 for sharing source code.

Added rules engine code to better / easier management of the UI widgets enabling / disabling.

Auto detect Pixel OTA image and extract boot / init_boot / vbmeta for patching and flashing.

Add Full OTA mode, which flashes full OTA image, while optionally retaining root, and best of all, for A/B devices, both slots are bootable, you can even have one rooted and one not.
[Google Pixel 6] kiwigi:
Thanks for you ongoing updates and improvements,🙏

Does that mean if I do a factory update(to my rooted slot) next time I could update one slot with rooted factory image and the other(after booting into it) with the same non rooted factory image.

Does that sound about right?
[Google Pixel 6] badabing2003:
Bug Fix Release:

June 01, 2023 v5.2.0.1 release

Bug fix #78 Error when opening a shell console on Linux / Mac
[Google Pixel 6] badabing2003:
To be clear on the terminology.

When we talk about Factory Image, we're talking about the files posted by Google here.

When to talk about Full OTA image, we're talking about files posted by Google here.

Factory image by default, flashes to active (current slot) unless you manually override it in PF, and when it is flashes, no matter the state of the other slot, that slot becomes unbootable, if you are interested in the details as to why that happens, just search the forums, there's lots of talk about it.

On the other hand, Full OTA image, always flashes to the inactive slot, and if something goes wrong it goes back to the current slot, which means it doesn't modify the current slot in such a way that it becomes unbootable.

If you want to be able to boot to both slots, then you should be flashing Full OTA images and not factory images.

Things to keep in mind.

Because the way OTA image is flashed (streamed) it is slower than factory flashing.

You cannot flash OTA to both slots simultaneously, you have to do it one at a time.

Keep in mind this is mainly for having both slots bootable in case something goes wrong and you want to have functional system without having to flash something immediately.

Also keep in mind that data partition is common, so if you change something in one slot, don't expect it to be different in the other slot (you can have one rooted and one not, and that's because there are two boot partitions)

You also don't want to be running different OS versions or security patch versions on the slots, and alternating between the two, although you might get away with it if it is slightly different, it is not recommended.

How it all started.
[Google Pixel 6] kiwigi:
Thanks @badabing2003 for your very detailed explanation.🥂
[Google Pixel 6] badabing2003:
Update:

June 03, 2003 v5.2.0.2 release

#76 Get a better build with Github action to support more Linux based platforms (no functionality changes).
[Google Pixel 6] badabing2003:
New Release:

June 06, 2003 v5.3.0.0 release

Added Github Action build on Windows 2019 with Python 3.8 to support Windows 7.

PixelFlasher now supports loading and processing Samsung Firmware (at least my Samsung's 😀), it would extract AP, BL, CSC, Home_CSC ... and then extract boot.img.lz4 from AP and unpack the lz4.

When creating a patch from the set boot.img, PixelFlasher will also create boot.tar to be flashed as AP to retain root.

If there was a way to pre-load odin with the extracted files, flashing could also be automated.

I know, what does PixelFlasher have anything to do with Samsung firmware? I added it for my own use.
[Google Pixel 6] shoey63:
Wrong platform tools. Use 33.03

Edit: For context, above user showed a screenshot of PF using platform tools 34.03, and being stuck whilst attempting to boot into fastbootd.
[Google Pixel 6] kiwigi:
Got it wrong, please delete my message.
[Google Pixel 6] Nightf0x_007:
normally updating from may to june like every month via pixelflasher with adb 33.0.3 and keeping data and disabled verity and verification, device wont boot and shows corrupted data message after it finished updating

reflashed may firmware also same message

help please any ideas how can i boot the device ? i dont want to lose my data asi dont have a backup
[Google Pixel 6] badabing2003:
support file please
[Google Pixel 6] Nightf0x_007:
incase this might be of any help at all i didnt flash both slots + i have a magisk patched boot image of june update on my pc

also im using magisk alpha (the patched boot image is by magisk alpha)

here it is attached
[Google Pixel 6] badabing2003:
Actually you flashed both slots, you were on slot a, when you flashed and then you were on slot b.

Either way don't worry, as long as you get into fastboot or recovery mode, you should be fine.

On the last flash I see this error

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

And considering that you're using Android Platform-tools 33.0.3, then it suggests the issue to be more on communication.

Cable , port, driver ...

I suggest you make sure you have the latest USB drivers

Make sure you use USB port 2 and a good cable.

Please do not flash a patched boot, with the number of modules you have enabled, I'd be surprised if it survives.

Don't worry about the corrupt message, that can be fixed later, let's focus on getting you to boot to system.

if you can put the phone in recover / sideload mode, It would be better if you flash stock full OTA June version, at least that won't have to use fastboot in user space.

If you can't get into sideload mode, then after changing port / cable / driver

Flash full factory with stock boot selected.

Report back, and if you encounter any errors, stop and post support file.
[Google Pixel 6] Nightf0x_007:
im using a type c to type c cable from my laptop, changed the cable im using now with another and reflashed may full factory image but also wont boot and got to the android recovery system page

here my steps i follow evey month when updating

downlaod the update full image firmware

extract the boot image and patch it via magisk and keep it

update via pxielflasher keeing data and disabling verity and verification

now device updated without root

i fastboot boot to the magisk patchec image created earlier

now device is udpated and with temp root , i reinstall magisk from inside the magisk app

done

(i know its a long prcoedure but thats what im doing for along time now and it works)
[Google Pixel 6] Nightf0x_007:
i thinking of fastbooting to a may update magisk patched boot image,will the device boot the system up ? but i need a patched image
[Google Pixel 6] Nightf0x_007:
recovery mode shows android with red traingle and no command text under it
[Google Pixel 6] Nightf0x_007:
changed port and cable still same result
[Google Pixel 6] Nightf0x_007:
deleted
[Google Pixel 6] Nightf0x_007:
device boots to the android recovery page cant load android system data ...
[Google Pixel 6] badabing2003:
While in recovery

Please try this

Download full OTA June image for your device.

Select it as firmware in PF

Process it

PF should select Full OTA

don't try to patch it yet.

Flash Pixel Phone.

Report back.
[Google Pixel 6] Nightf0x_007:
same result it boots to the android rec. cannot load android system ..., note that while on rec. mode it shows no command and in PF before flashing the ota it says your mobile model error i ignore it and press ok to continue, i want anyway to boot the device up (for ex. updating to a14 beta or something) and take notes of my apps and backup my imp. data and i have then no problem resetting the device from scratch
[Google Pixel 6] Nightf0x_007:
here is the lastest file,
[Google Pixel 6] Nightf0x_007:
Idk what to do actually, i just want to boot the system and take backup of my data and then i have no problem in resetting device

Should i try updating to a14? Or update without vb verity & verification?
[Google Pixel 6] Nightf0x_007:
Also is there a file in the log, where i can know the modules i have ?, So i know them to reinstall them incase i rested the device ?
[Google Pixel 6] badabing2003:
I'll get back to you once I analyze your log files.

Meanwhile please don't try anything random, you might lose any chance of recovery of your data, specially if you decide to flash different os version or play with Verity / verification.

I'll give you the modules list you had.
[Google Pixel 6] Nightf0x_007:
Ok thanks man god bless you, in other thread its suggested it have something to do vb verity verifcation, note that i was on magisk alpha and thats 1st time i update month to month update with it avilable as i was using magisk delta

I was about to try to flash the rom with both vb verity verifction disabled, although i know i wnt be able to flash customkernel and phone wont be running on a healthy environment but all j need now to backyp my data up and im set to resett the device from scratch
[Google Pixel 6] Nightf0x_007:
will try thanks for your time and efforts, a somehow noob question can i get a list like this one with the apps i had ? i assume no
[Google Pixel 6] badabing2003:
Did you at any point in the past use the package manager feature in PF, if you did and you clicked on "Get All Application Names", then the answer would be yes.
[Google Pixel 6] Nightf0x_007:
no actually , flashed ota june without vb's, device booted up thank god, now can i root nromally ? i wont be using a custom kernel for now anyway im planning to switch to nothing phone 2 next month, if i reflashed and disbaled vb device will get screwed this happened to me before i remember
[Google Pixel 6] badabing2003:
Happy to hear that you're back up and running again.

Yes you can root again without any issues, just remember if you disable vb there will be a wipe.
[Google Pixel 6] badabing2003:
{Mod edit: Quoted post has been deleted. Oswald Boelcke, Senior Moderator}

Sorry can you provide some context, you're linking to an old post (over a year old) and saying exact same issue?

What is happening? when doing what?

Support file please.
[Google Pixel 6] Nightf0x_007:
yes i wont touch vb again no problem i will sacrifice using custom kernel for now, thank god the phone booted up again, one question please next month when updating i will leave the disable vb options unticked right ? thats it ?

+ also while trying to get the phone to work one of the boot slots wasnt able to boot to fastbootd, so i flashed the june firmware to both slots then i proceeded with what you told me to do with the ota ? is that ok ? im afraid the phone isnt standing in a firm ground and if anything happened device will get screwed
[Google Pixel 6] badabing2003:
Correct,

What I would suggest you do now is fix your other slot as well.

Right now you only have one slot fixed / functioning.

Run the Full OTA flash again and it should flash the other slot and switch to it, this way you'd have both slots functional, in case anything goes wrong.

In fact to make it easier, create a patch now, and select that before clicking Flash Pixel Phone, your other slot will be rooted, whereas the current one will remain unrooted.
[Google Pixel 6] Nightf0x_007:
also while trying to get the phone to work one of the boot slots wasnt able to boot to fastbootd, so i flashed the june firmware to both slots then i proceeded with what you told me to do with the ota ? is that ok ? im afraid the phone isnt standing in a firm ground and if anything happened device will get screwed

thats what i did is it enough ? or should i follow your instructions (flashing the ota again)
[Google Pixel 6] V0latyle:
Since you already flashed the firmware to both slots, don't bother with the OTA.

Your device should be fine now. You can now patch your boot image for root. You can try flashing the custom kernel if you want but if it doesn't work I would say that is an issue with the kernel, not your device.
[Google Pixel 6] badabing2003:
Factory firmware flashing to both slots does not make both slots bootable, and if you ran into fastbootd issue, then you definitely were trying to flash factory not OTA.

If the last thing you did was Full OTA flashing, then do full OTA flashing one more time, you can choose to select the patched boot or the stock, it's up to you.

If the last thing you did was a factory flashing, then do the full OTA flashing twice in a row.

And you should be good to go.
[Google Pixel 6] Nightf0x_007:
i might give it a try with the kirisukra kernel, but i remember before same issues with vb happened with me and when i flashed the kernel phone bootlooped and i needed to dirty flash the firmware and to get the kernel working i factory resetted the device from scratch with vb flags disabled
[Google Pixel 6] badabing2003:
I'm suggesting OTA so that he gets both slots in bootable state, in case he ever runs into issues while experimenting, he can always fallback to the other slot.

The last flash was without disabling vb, hence he will need a wipe to switch kernels.
[Google Pixel 6] Nightf0x_007:
after updating ota as you told me, i fastbooted to the magisk patched boot image i made eralier than installed magisk from inside the app now im rooted, will now reflash the ota again so it will be flashed in the other slot too, after that can i keep the latest slot unrooted and just switch active slot to the earlier rooted one ? or what im saying is unapplicable ?
[Google Pixel 6] V0latyle:
Sounds like @Freak07 needs to fix his boot image header...disabling DM-verity and vbmeta verification shouldn't be necessary because AFAIK unlocking the bootloader mostly disables AVB

But, I could be wrong, because the Magisk patch doesn't patch the kernel itself, it patches ramdisk, so if AVB is still checking the kernel hash against vbmeta, you'd need a custom vbmeta image....still, this wouldn't require disabling verity/verification IIRC
[Google Pixel 6] badabing2003:
Yes you can have one slot rooted and one not and be able to alternate, as long as you flashed the same full OTA image twice in a row and did not flash factory afterwards.
[Google Pixel 6] V0latyle:
Can you explain this a little more for my sake? My understanding of the OTA process marks the "old" slot unbootable once the device successfully boots from the updated slot. So, if you arbitrarily change slots, rollback protection thinks that some sort of rollback hijack has occured and refuses to boot.
[Google Pixel 6] Nightf0x_007:
now my active slot is B rooted and working so i will flash ota again so it will get flashed to slot A and i wont boot it or root will leave it untouched, i will just switch active slot back to B and boot to B rooted (whats im running right now)

is this procedure ok right ? or something is missing ? sorry i keep asking as im afraid something happens
[Google Pixel 6] V0latyle:
Hold on a second, let @badabing2003 explain what he meant. Manually switching slots has always led to problems in my experience
[Google Pixel 6] Lughnasadh:
Disabling verity and verification is only needed when flashing custom kernels on the Pixel 7 series. For a while it was needed on the Pixel 6 series, but not anymore. So that person shouldn't need to disable those flags unless we are in the wrong thread, lol.
[Google Pixel 6] Nightf0x_007:
reflashed ota now both slots is ok, then switched active slot to the earlier rooted one and so far eveything is fine

thank you man @badabing2003
[Google Pixel 6] badabing2003:
You are on B and rooted, if you flash full OTA (selecting stock boot instead of the patched boot, which is a choice)

Then slot A will be flashed with stock and switched to it, and your system will be unrooted.

Switching slot (either manually or through PF) will switch it back to slot B and you will be rooted.

Rollback protection is a bootloader thing, in this case both slots have the same version of the bootloader, he's not trying to boot to an older bootloader.

In fact I discourage people from trying dual booting with different firmware versions, even if the bootloader version is the same.

You probably forgot this.

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

xdaforums.com

Let me know if you have questions about it.
[Google Pixel 6] badabing2003:
@Nightf0x_007

This is for you.
[Google Pixel 6] V0latyle:
Thanks for clearing this up. Do you remember off the top of your head what made this no longer required?

Yeah, that documentation points to tamper evident storage. I could swear I remember reading something involving the OTA process that prevents rollback to the "old" slot on successful boot of the updated slot.

Yeah I knew we had talked about it at some point
[Google Pixel 6] Lughnasadh:
I don't unfortunately. I'm sure it's buried in one of the kernel threads.

As a side note, when disabling was needed it turned out that disabling verity alone was enough. This was good because a wipe isn't needed/required when only disabling verity. Only when disabling both verity and verification is a wipe needed.