yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] MatMew:
Where can we find an older version of platform-tools to use with the latest version of Pixel Flasher? Thank you.

After accidentally updating to Android 13, I'm so scared to try and regain root access on my Pixel 6 with 008.E1.

Scared of boot loops, using P7 boot image, many other things. Getting old over here.
[Google Pixel 6 Pro] StanWiz:
Here
[Google Pixel 6 Pro] MatMew:
Thank you!
[Google Pixel 6 Pro] klazyStrida:
PixelFlasher v4.8.1 and Platform-Tools on Ubuntu 22.04(Linux MINT 21.1)

Using Platform-Tools 34.0.1 resulted in the following situation.

(1) Platform-Tools version warning when starting PixelFlasher.

(2) After launching PixelFlasher, the "ADB Connected Devices" list box and

[SCAN] button are grayed out, so the connected device cannot be selected.

Is there something specifically wrong with the Linux version of 34.0.1?

I haven't investigated it in detail, but for the time being,

I'm avoiding this problem by using Platform-Tools 33.0.3.
[Google Pixel 6 Pro] Thebear j koss:
There is an issue with platform tools 34.0.1. Been discussed if you read back the past few pages
[Google Pixel 6 Pro] klazyStrida:
Thanks for your reply.

I've already read past logs, but it seems that

I overlooked the contents or misunderstood.
[Google Pixel 6 Pro] AllusionPDX:
Extracting short SHA1 from magisk_patched_4d938d3c.img ...

2023-04-01 13:08:09 NOTICE: The patched image file does not contain source boot's SHA1

This is normal for older devices, but newer deviced should have it.

If you have a newer device, please double check if everything is ok.
[Google Pixel 6 Pro] badabing2003:
My observations.

- You started with Android platform tools 34.0.1 (not good) but switched to 33.0.3 (good)

- You are posting in Pixel 6P thread but are using Pixel 7P, I don't mind, just making sure you are dealing with the proper firmware.

- Your phone is rooted with Magisk Delta 25210, but have magisk manager 25200 stable installed, don't mix and match.

- I can't speak of delta, 25210 but the official 25210 is no good.

- When creating a patch PF uses either the rooted Magisk core or the Magisk Manager, if the two versions are the same, the preference is to use the core.

If the manager is newer, then it uses the newer manager instead of the core. In your case because the core is at newer version, it is always using the core to create a patch, I suspect you're trying to create a patch with the stable version.

There are couple of ways to overcome that.

1- you can flash stock first and then create a patch, in which case it will use the manager (this is the preferred way)

2- you can temporarily remove su root rights from adb shell in Magisk Manager, in which case pf will not be able to access the core (which requires root access) and app report that the phone is not rooted, create a patch and it will use the manager.
[Google Pixel 6 Pro] iwearthebelt:
Just for the record, I'm using the P6P, I'm on Magisk Delta 25210 and Magisk Manager 25210. Flashed with PixelFlasher. Everything is running smoothly, I've had absolutely no issues whatsoever. If you have any questions feel free to ask. Your PixelFlasher program is great, it's made things a lot easier for me. Thank you Badabing2003!
[Google Pixel 6 Pro] AllusionPDX:
Cheers for the response, and yeah I just came here through google, my bad, i am using a p7pro.

I tried to follow your results and did a clear flash, and I was able to make a patch, however the magisk app doesnt show root, any assistance would be GREATLY appreciated, and thank you very much for the assistance you have already given =)

I think I may have made an oops with a hidden version of magisk. I know the unhide for the normal magisk: pm unhide com.topjohnwu.magisk

I do not know the one for the delta unfortunately =(
[Google Pixel 6 Pro] badabing2003:
Did you by any chance disable root on adb?

You had it properly patched and flashed, and it booted to system, rooted with Magisk 25200

Why did you flash again?

Selected Device on 2023-04-01 14:42:17:
Device ID: REDACTED
Device Model: cheetah
Device Active Slot: b
Device Mode: adb
Device is Rooted: True
Device Build: TQ2A.230305.008.C1
Device API Level: 33
Device Architecture: arm64-v8a
Device Bootloader Version: cloudripper-1.0-9618366
Magisk Manager Version: 25.2:25200
Magisk Path: /data/app/~~HLQ4CD2k4nmYR3XDH7ikPQ==/com.topjohnwu.magisk-uxdJc7HdQK8g4C5X-ro4dw==/base.apk
Checked for Package: com.topjohnwu.magisk
Magisk Version: 25.2:25200
Magisk Config SHA1: 4d938d3c7bab8b0ca7accccef2aa07eefd20602d
Magisk Modules:
Shamiko enabled v0.6 (126)
[Google Pixel 6 Pro] AllusionPDX:
Because it wasnt showing as rooted unfortunately. I went back and re-did it again, and its showing the same thing.

Edit: talk to me like im stupid, because in this case I am haha, no idea how to disable root via adb. i know how to get root in adb with su though.
[Google Pixel 6 Pro] badabing2003:
You had root and everything was good at one point, as you can see in my previous post.

Try this.

Select the Patched boot (the one with 25200), and use the Flash boot button, not Flash Pixel Phone
[Google Pixel 6 Pro] AllusionPDX:
I have done this and it shows I have root in adb, and everything else, however in magisk manager it does not show it as rooted per the picture above.

I went ahead and ran list packages -f and saw:

package:/data/app/~~QA-6DCqkV42sVpEs3syemQ==/io.github.huskydg.magisk-0vi5Ljei6--mtq2S1SkPCQ==/base.apk=io.github.huskydg.magisk

I believe this may be causing the issue...

any ideas on resolving?
[Google Pixel 6 Pro] badabing2003:
yes, uninstall all versions of Magisk manager.

unhide any Magisk Manager that you have, if you have forgotten the hidden package name, you can use TB Checker from play store to let it tell you the hidden (or not hidden) Magisk Manager that it finds.

After you do that, reboot

Then install Magisk Manager 25200 and you should be good.
[Google Pixel 6 Pro] AllusionPDX:
Ok so i tried TBChecker and Ruru and its just showing the com.topjohnwu,magisk. It shows I have root, failing safetycheck, however the magisk manager app is still showing that i do not have root.

I know I could fix this by completely wiping out my phone, however that would be an absolute nightmare currently.

any other ideas?
[Google Pixel 6 Pro] badabing2003:
no no, you don't need to wipe, you just need to find All Magisk Managers and uninstall them.

Start by uninstalling `io.github.huskydg.magisk`

You can use Package Manager (File Menu) in PF

Search for Magisk

select and uninstall.

Let me know what it finds.
[Google Pixel 6 Pro] AllusionPDX:
https://pastebin.com/raw/j8d4gsUw

nothing with magisk.

I have already removed the huskydg one, and removed the topjohnwu one and then reinstalled a few times.
[Google Pixel 6 Pro] badabing2003:
Couple of package names that are suspect

rok.abvl.q

vmvhkk.j.f.j

In the Package Manager, click on Get All Application Names

It could take some time.

Once done,

Sort by the column Name.

See if any of the ones that don't have a name, is suspect package that could be a hidden Magisk.

You can uninstall it.

Also look for the name Magisk in the Name column

let me know
[Google Pixel 6 Pro] AllusionPDX:
aaaand that resolved it. Cheers mate, you have a donation link for a beer?
[Google Pixel 6 Pro] badabing2003:
Happy to hear that, which was it?

No donation, see OP here to know why.
[Google Pixel 6 Pro] AllusionPDX:
I believe it was both of them actually. i installed and uninstalled so many times that somehow i had 2 different hidden magisks.
[Google Pixel 6 Pro] badabing2003:
New Release:

Apr 10, 2023 v4.8.2 release

Include additional Magisk versions in the check to display a warning dialog when the user has installed one of the known versions to have issues.

Display USNF related flag values when selecting a device.

Check the downloaded Google firmware checksum to match the one in the filename and warn if it does not.

Link to download Google USB Driver is added in the help menu.

Added more visual troubleshooting event flows.

Install APK now defaults to Non Market.

Added Install APK cancel option.

You can now select an app in package manager and right click to launch it on the phone.

Minor bug fixes and other improvements.
[Google Pixel 6 Pro] darkness4every1:
April update: updating while having Magisk 26.0 will result in losing root so you'll have to re-root.
[Google Pixel 6 Pro] badabing2003:
See this
[Google Pixel 6 Pro] AlDollaz:
@badabing2003 You are a god amongst men! PixelFlasher makes updating SO MUCH EASIER!

Your work is invaluable, thank you so much.
[Google Pixel 6 Pro] iwearthebelt:
@badabing2003 Just wanted to thank you for trying to help me out on Tuesday and taking a look at my logs. That was the first time I submitted a log from PixelFlasher and wasn't exactly sure what I was doing. Unfortunately my entire device took a crap and I needed to do a full wipe and reset. All is good now after 2 days of work but I do have one more question for you... I went from using Magisk Delta to Magisk Stable 25.2, Should I just stay on Magisk Manager 25.2 or take the update to 26.1? I really don't want to go through that again if I don't have to. Thanks again for taking the time to respond.
[Google Pixel 6 Pro] Thebear j koss:
You can update to the latest stable. I think 26.1 became stable yesterday. Just install latest stable from magisk manager
[Google Pixel 6 Pro] iwearthebelt:
Thanks, just wanted to be sure there's no issues with it. I haven't been having the best luck lately with Magisk updates. I went from the Canary build to the delta build and now to the stable. I I wanted to stay on canary but with all the issues lately I have had to find something stable.
[Google Pixel 6 Pro] Thebear j koss:
Always stick to stable unless there is something in a different build that fixes an issue with your device. Some devices have issues with banking apps and gpay that may require a canary or beta, but your best bet is usually stable.
[Google Pixel 6 Pro] badabing2003:
Sorry about your troubles.

I say if you want to avoid the troubles you mentioned, then follow : If it ain't broken don't fix it mantra.

Although 26.1 seems functional, honestly it is not battle tested.

I personally still am on canary 25206, even thought I keep on testing different versions on my non main driver phones.
[Google Pixel 6 Pro] iwearthebelt:
Yeah I figured I'll just stay on the stable version until the next Canary and monthly update are playing nice together. I don't have any formal training, Everything I've learned here is self taught, so when I get to the point where I'm out of my comfort zone, It's time to leave it to the professionals and just sit back, do some reading and learn some more.
[Google Pixel 6 Pro] bush911:
Hi mate,

Thank you for this amazing Application which actually saves lives.

I am using Pixel 6 with February build currently on Magisk 25.2.

Is it OK to just use PixelFlasher to upgrade to April build without firstly updating Magisk to 26.1?
[Google Pixel 6 Pro] badabing2003:
Thanks, and yes it is ok to go straight to April without first upgrading Magisk.
[Google Pixel 6 Pro] badabing2003:
New Release:

Apr 27, 2023 v4.9.0 release

Added support for installing / creating patch with @Namelesswonder Magisk zygisk64_32 (stable, beta, canary, debug versions).

Support for recognizing Lineage firmware and extracting / patching boot.

Display 32 bit capabilities of the device.

Utilize New Magisk 26.x flags as needed (patch support for more devices).

Disable Flash to Inactive slot and Flash to both slots button if the device is not A/B device.

Partition Manager can now list the partitions even if the devices is not rooted.

Added Custom Patch button, which allows selecting a boot file from disk and getting a patched file back to save to disk (all on the PC).

Added Open Folder button to open a file browser to the directory of the selected boot image.

Added Reboot to Download button (Odin mode).

Added Reboot to Safe Mode button.

Storage reorganization, store patched files next to the stock file, and set the patch name to clearly indicate both source and target sha1.

Various additional validation checks.

Bug fixes and other improvements.
[Google Pixel 6 Pro] dilligaf56:
@badabing2003 - thanks again for a fantastic application. Until last month I was updating every month via the OG CLI method, which worked fine, but is more tedious. Your app makes it easy-peasy. Just updated to rooted April image in a couple of minutes. Excellent work, thanks again! Would be happy to donate for a beer or a Starbucks or three if you have a link!
[Google Pixel 6 Pro] badabing2003:
Thanks for you support and kind words.

No donation required.

You can read about it in the main thread's OP
[Google Pixel 6 Pro] Doug D:
Hey I unlocked my bootloader, downloaded magisk using this tool, and the latest rom. I patched the bootloader. I thought I followed instructions correctly, it did seem to flash the patched bootloader...

but now I'm stuck in fastboot and I've tried every single method I can find to recover the device...

Any help?
[Google Pixel 6 Pro] badabing2003:
please provide support file so that I can take a look.
[Google Pixel 6 Pro] Doug D:
Thanks but I ended up messing with it a bunch.

What eventually worked for me was flashing developer preview and then flashing 13 again. Not rooted yet, but I'll try again another time!
[Google Pixel 6 Pro] dilligaf56:
Read and noted. Thanks again, much appreciated!
[Google Pixel 6 Pro] badabing2003:
New Release:

Apr 30, 2023 v4.10.0 release

Added no reboot option, with this option selected, after flashing is completed, the phone will not reboot to system, giving a chance to take other actions before reboot.

Added built-in file editor, you can now edit the flash script before running, in case you want to customize it (needless to say, should only be used if you know what you're doing)

Added a button to open an explorer in working directory, useful for people who want full control, perform manual actions by following guides, but using PixelFlasher to do the prep work.

Made the Firmware and Rom Process buttons, full with text. It wasn't obvious for some.

Detect and handle Magisk Zygote64_32 automatically, thanks to @Namelesswonder for adding the necessary marker.
[Google Pixel 6 Pro] 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 Pro] 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 Pro] DigiPooch:
Hey guys, I've tried finding somewhere throughout the thread where this was asked but I'm not seeing it and likely I'm just blind so apologies in advance... but i initially rooted with magisk using the 7 pro image on like the January update i believe. My question is should i use the current 7 pro factory cheetah image or the 6 pro raven image to update since I'm currently using 6 pro but technically on 7 pro patched image? I was going to use the 6 pro image to retain root and data, however I get the Sha mismatch when trying to patch the 6 pro image in pf, however when I try to patch the 7 pro image I do not receive the Sha mismatch and it will allow me to proceed but I'm too much of a chicken to pull the trigger on it yet without confirming which to use. Thank you for the insane amount of hard work with all this and any help pointing me in right direction.
[Google Pixel 6 Pro] badabing2003:
You're posting in pixel 6 pro forum so I assume your phone is pixel 6 pro. If it is not, stop right there.

Never, ever flash factory image of another device unless you are prepared to turn your expensive device into a paperweight. So if your phone is 6 pro, you want 6 pro firmware to upgrade.

You haven't stated if you are on official firmware or beta, upgrading within the same line is no problem, switching between the two might involve a wipe, depending what you have and what you're changing to.

Everything that was said above has nothing to do with rooting, that's another thing.

Rooting typically involves patching boot.img file of the same firmware your device is running and flashing that, which means if you are upgrading to standard pixel 6 pro May release, you would patch the boot file of that may release.

However with Pixel 6 series with some firmware versions (specially the beta releases) patching the boot.img to get root was broken, and you needed to patch init_boot or boot extracted from pixel 7 series firmware, but just that, not the entire firmware.

Before you go any further, gather the details and post back so that proper instructions could be provided.

Support file from PF could provide us the details.
[Google Pixel 6 Pro] DigiPooch:
Thanks for super quick reply. Should have specified currently on beta build T2B2.221216.006 with 6 pro device and I used the root workaround pulling the 7 pro boot.img flashed to my 6 pro. I didn't know if that was the possible reason for the mismatch error message in PF when trying the latest 6 pro image that matches my phone from the link within the app for the factory zip, but no error when doing same exact thing but with the 7 pro version if that makes sense. Sounds like I wouldn't need to use 7 pro image again for any reason here on out, so mainly just the matter of reason I'm seeing the mismatch or whether or not it's okay to run with a mismatch as it says may be caused by compression. Attached support file of attempt to patch 6 pro boot img. Thanks again
[Google Pixel 6 Pro] badabing2003:
Sorry,

Could you please upgrade PF to the latest 5.1.0.2, as the one you're using had a exception and I couldn't get device details.

Please scan with it while your device is connected.
[Google Pixel 6 Pro] 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 Pro] 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 Pro] 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 Pro] 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 Pro] ykjae:
@badabing2003 I'm sure I'm missing something simple. I've been rooting my devices since forever. I've recently took the latest 6pro security update and can't get the boot image to boot. I'm using the 7pro boot image and pixel flasher. Any suggestions?
[Google Pixel 6 Pro] badabing2003:
I suspect your Magisk version, which are you using, some versions have issues.

Support file would tell me the details if anything is going wrong.
[Google Pixel 6 Pro] badabing2003:
New Release:

June 16, 2003 v5.3.1.2 release

Set Active slot now automatically reboots to system after setting the slot, unless "No Reboot" option is selected.

Update Ubuntu 20.04 build to be aligned to the same methods that Ubuntu 22.04 build uses.

Improve confidence value calculation when comparing compressed sha1 against normal sha1 to account for shift.

Do not abort when the sha1 comparison confidence value is low, leave the choice to the user.

Update Windows builds (both) as wxPython wheel path changed, rely on a more persistent URL instead.