yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Thebear j koss:
Waste of time. Not going to provide anything. Nobody else has had any issues outside of a hiccup that was easily remedied. Some people just shouldn't root and flash. And I'm not being mean, but if something goes wrong, you shouldn't just go blaming everything and everybody else.
[Google Pixel 6 Pro] badabing2003:
I hear you, I can imagine the user's frustrations after finding themselves with a phone that is not working properly and not knowing how to get out of it.

But the user's post doesn't help the situation, we're here to help out, and without any details, it's impossible to guess what had happened and what corrective actions to take.

Help us help you is what I would say.

I always would like to see the logs, just in case I can add another check / validation / warning to prevent a user from shooting themselves on the foot or fix a bug, we know things could go wrong, and not every scenario leads to the same outcome, anticipating the numerous scenarios we face or might face helps us add measures to prevent mishaps.
[Google Pixel 6 Pro] DeanO74:
I got it back to stock right away. If you want to pm me directions on how to pull the logs I offered them in my original post. And I didn't bash you or your application, just made the point that it did not work out well for me, I may use a different method this evening. Clearly my lack of success hurt some ego's here so I will delete the OP.

For future reference if anyone has the same situation or type of lock up or bricking I did here's what I did to get it back up and going.

1. Let battery drain completely. 2. When plugged back to charger booted into fastboot and from there Rescue option. 3. After loading into Rescue and broken robot shows on screen hold Power and Volume Up button simultaneously till more options appeared. 4. Select option for Send ADB commands. 5. Use Google's online recovery tool to flash stock ROM back onto device. https://pixelrepair.withgoogle.com/steps
[Google Pixel 6 Pro] badabing2003:
Sorry if I missed any of your posts.

I only see two posts from you

First post here, and your follow up post here. None of which is offering any logs, because you wrongly assumed that all of that is lost in a bricked phone.

Did I by any chance allude you into thinking that I was seeing your posts as bashing me? Where? what gave you that idea?.

As for asking for directions on how to pull the logs, it's all here in my reply to your post.

Makes me wonder ...
[Google Pixel 6 Pro] Gytole:
Pixel Flasher is MY go to way to flash the phone. Thanks fam. Works flawlessly everytime without fastboot kicking me out like normal. 5 stars.
[Google Pixel 6 Pro] Thebear j koss:
That's kind of my point. Anyone rooting and flashing should know the basics of debugging and logging. You shouldn't just post in a thread that your tool broke my brand new phone. And there are many people willing to help, but without any context or logs, it is impossible. Especially here with this tool which does a dry run before you flash, to prevent situations that may screw things up. My only issue with the tool was during some of the longer flashing processes I would get a message the application is not responding, but that was only because it was working
[Google Pixel 6 Pro] badabing2003:
Yeah,

One day, I will find a way to turn that into a proper async call and still capturing the output in real time without disrupting the execution.

It's just too risky and too involved for me to address that now.

I need to focus on new features that have been ready for a while pending proper testing before release.
[Google Pixel 6 Pro] Thebear j koss:
Not a problem, it is the tool functioning normally, you don't want users panicking and hitting buttons or unplugging because the tool is doing it's job. It was a bit scary the 1st time I tried the tool, but I just let it do it's thing and have not had any issues.
[Google Pixel 6 Pro] Alekos:
I don't think the "lack of your success hurt some egos". We are just trying to help and most of us in this thread have seen your mistakes posted a hundred times. The developer couldn't have been more helpful and courteous regarding your issue. Your phone was never "bricked" because a brick means no life.

Anyway glad you got it working (we all knew you would anyhow). Next time, just post your issue - it'll get resolved. Just needed to get back into fastboot and flash the original factory image.
[Google Pixel 6 Pro] Thebear j koss:
Not hurting my ego, I've been in your shoes many times and have made the same mistake you made by posting your issue without any context or logs. The way it was explained to me was to never just post problems or issues because it may scare other users from trying these tools. Some devs get more upset than others. But if someone makes a tool to simplify the process and there hasn't been any issues like yours and you don't provide details and logs, then how can anyone help you? When you post that you followed everything to the letter and this bricked my phone, it comes across as insulting to the development of the tool. Other thing is after numerous attempts to have you post details and logs, you still have provided nothing. The pixel flasher tool provides built in logs that will show exactly what happened.

I suggest in the future instead of just saying your tool bricked my phone, ask for help and provide as much info as possible to what you were doing and send logs when asked.
[Google Pixel 6 Pro] badabing2003:
Honestly that did not insult me at all, I'm not sure if anything I said somehow alluded to that.

The program is not infallible, that is why I always ask for logs, to see if there is an actual issue with the program, and make it more robust.

The other reason why I want to see the logs if I can add a verification in the process or a warning to help the user not fall into a path that could lead to issues, that is why there are checks and double checks in the program.

As for why someone would not want to submit logs, I can guess it could be one of:

1- Privacy concern, and I fall into that category, I don't want to submit logs blindly without knowing what sensitive information I might inadvertently be sending.

For that exact reason I have taken measures in the log generation to redact any sensitive information, it removes any ID or username, that is why it is called sanitized support.zip. I do my best to assure that the privacy of the user is not compromised in any way.

2- Worried that the real reason why the soft brick happened would be exposed, and that I cannot do anything about, the logs would not lie and it would reveal, although I do my best to point it out gently what step went wrong without making the person feel hurt, there will always be people that take an issue for being wrong or doing wrong.

3- Does not care about knowing what went wrong, and does not want to contribute to improvement of the guides / tools / processes by providing valuable feedback.
[Google Pixel 6 Pro] Thebear j koss:
Yeah, some devs are not as kind as you. Some get pretty upset with users who just blame their work with no logs or context.
[Google Pixel 6 Pro] DeanO74:
Well second time was a charm. I took a couple of precautionary steps this time by flashing a stock image to both partitions first and using a newer, more robust laptop to do the work with. I don't know what went wrong the first time around, I suspect it may have been related to the laptop I was using causing the crashes and fouled patch or flash. I have a question badabing2003, does the method you incorporated into this app under expert mode for locking/unlocking the bootloader wipe the device upon either action, both actions, or have to found a way to prevent the wipe? And given all the discussion I've seen around the subject of Verity and Verification has anyone every successfully tried changing the saved hash calc to match a modified flashed image to circumvent the possibility of every having a problem with them? Seems like a viable answer to me at face value, my brother is supposed to be looking into that when he has time since he is the most current coder and familiar with them those processes but we'll see.
[Google Pixel 6 Pro] badabing2003:
That would definitely cause issues, cable / connection / driver should be solid before flashing, any disruption and thing go South.

PixelFlasher is just a UI layer on top of adb / fastboot commands, all interactions with the phone is through adb/fatsboot.

lock / unlock by Google design is supposed to wipe your device, for obvious security reasons, and all PixelFlasher is doing is calling the commands.

Unless you find a loophole in the commands, your phone is supposed to be wiped, and there is nothing PF can do about it.

I'm not sure what problem you're referring to, I'm not having any Verity issues, Magisk already takes care of that, I don't even have to select disable verity / verification when flashing. It is there to support custom ROMs.
[Google Pixel 6 Pro] badabing2003:
PixelFlasher 4.0.0 pre-release:

Sep 25, 2022 v4.0.0 pre-release

New Feature: On supported devices, where device is not yet rooted (or adb shell su not allowed), an option to control the Magisk Manager GUI (drive UI) to programmatically control the app through UIAutomator and create a patched boot.img

See Patching flow chart for details.

New Feature: Detect if Magisk Manager is at a higher version than installed Magisk, warn the user of a potential rare corner case and offer a choice of patching method.

New Feature: Temporary Root, when flashing if you choose this option, the phone will be flashed with unpatched boot.img, but Live boot to patched boot.img to provide a temporary root.

New Feature: Warn the user to flash both bootloader slots if their device is a Tensor device (Pixel 6, Pixel 6a, Pixel 6 Pro), if current version of OS is lower than Android 13.

New Feature: Flash to inactive slot. Unlike OTA flashing factory image flashing is always done on the current active slot, with this option selected, PixelFlasher will write to inactive slot. This allows one to revert to current working state in case anything goes wrong. This feature combined with Temporary Flash provides best method to test a new firmware without risking losing current working setup.

Note: You should avoid this option if you are on a Tensor device and are upgrading from Android 12 to Android 13 (see the previous feature).

New Feature: Detect and operate on devices that are in Sideload or Recovery mode.

New spinner to indicate PixelFlasher activity.

Renamed Reload button to Scan, to better reflect the button's function. After a scan print the count of devices found.

PixelFlasher previously used MD5 to uniquely identify boot images (patched or otherwise), with version 4.0.0 PixelFlasher now uses SHA1 instead of MD5.

This has no bearing on the functionality, it just better aligns with Magisk way of identifying and tagging boot images.

PixelFlasher now extracts the embedded SHA1 of a Magisk Patched images (only available in newer devices) and assures that it matches the source boot.img's SHA1.

This is just an extra validation.

Code cleanup / refactoring, adding more validations and exception handling.

Print debug details when encountering non compliant Magisk modules.

Firmware link now takes you to the device's download page instead of just the general download page.

To better reflect the file details, transferred and stored boot.img files are now suffixed by their shortened SHA1, while magisk_patched.img files are now suffixed by shortened SHA1 of their source boot.img.

Allow sideload even if bootloader is locked.
[Google Pixel 6 Pro] wgrant:
Excellent work. Can't wait to use next month. Appreciate the continued effort on this tool.
[Google Pixel 6 Pro] BeachNYC:
Can anyone explain to me why my Pixel Flasher, same version 3.7.0.0 looks so different from the one pictured in the above post? Mine is missing the option of flashing to both slots, various flash options, ability to flash a custom rom, etc. I'm confused (not an unusual state of mind for me!)

Edit: NEVER MIND. Figured it out myself when re-reading the OP. So sorry.
[Google Pixel 6 Pro] BeachNYC:
I have a problem. Used the Pixel Flasher to flash Android 13 on my Pixel 6 pro. Had PF set to flash to both slots, ran it with a dry run, and there appeared to be no problems. Upon running the real flash, keeping data, the phone ends up with the "This device is corrupt" warning. It proceeds to try to boot, but never gets past the "Google" logo. Neither adb nor fastboot recognizes the device. Just hangs on the logo.

Would appreciate any advice as to how to get this working again. Attaching logs.
[Google Pixel 6 Pro] Thebear j koss:
Read here- https://www.droidwin.com/pixel-6-pro-your-device-is-corrupt-it-cant-be-trusted/
[Google Pixel 6 Pro] badabing2003:
Sorry to hear about you troubles.

If you provide a support.zip I could take a look to see what might have gone wrong.

It's in the help menu.
[Google Pixel 6 Pro] Alekos:
This was a known issue with A12. I had it on the second day after purchase 8 months ago. Had to wipe data in recovery and re-flash image on both slots (I had to use flash.android.com since PF wasn't available).

You're just trying to get access to your Data correct? I don't think there's a way. As long as you can access fastboot, just reflash after wiping.

You can try booting into safe mode (hold volume down as soon as you see Google logo).

When you boot into fastboot, does your computer recognize the device? Can you boot into recovery mode (you'll see no command, bypass it by holding power and quickly press volume up).
[Google Pixel 6 Pro] Alekos:
That guide has a ton of wrong information - for example you don't need USB debugging enabled to flash an ota. As long as OP has BL unlocked they should be fine (of course data will be gone but device saved).
[Google Pixel 6 Pro] badabing2003:
New Release:

Oct 03, 2022 v4.1.0 release

Patching is now fully automatic with or without root.

PixelFlasher uses installed Magisk Manager binaries to create a patch (root binaries are only used if Magisk Manager is not available / accessible)

UIAutomator no longer necessary, neither asking the user to manually patch and click ok when done.

Added an option to set a hidden Magisk package name so that PixelFlasher can find the Magisk and use it, the user still has a choice to use root binaries.

Speed improvements for device property reading.

Speed improvements for Magisk modules reading.
[Google Pixel 6 Pro] badabing2003:
NOTICE:

I'm marking version 4.1.0 release as pre-release because I just found out that unzip is not normally available on the phone, which this new patching mechanism uses.

On my test phones they were available.

Unless you have unzip on your phone, you should avoid using this version.

Sorry about this oversight.
[Google Pixel 6 Pro] badabing2003:
Update Release:

Oct 03, 2022 v4.1.1. release

Bug Fix: Bundle busybox with PixelFlasher to be used for unzipping Magisk.

Bug Fix #25, use the Magisk Manager version number instead of Rooted Magisk version number.

Cosmetic changes and a bit more logging.
[Google Pixel 6 Pro] tutuco:
Hey, any noob tutorial on upgrading a Rooted P6P to the last patch(October) without losing data and root?

Last time I ran everything manually but I would like to use the Pixel Flasher tool if possible.
[Google Pixel 6 Pro] badabing2003:
Just follow the Basic steps from OP or the Main thread (see in OP or in my signature)

If you previously did not flash bootloader to both slots, I suggest you do that too, in which case follow Advanced steps and choose "Flash to both slots"
[Google Pixel 6 Pro] badabing2003:
Update Release:

Oct 04, 2022 v4.1.2 release

include busybox binaries for different Android architectures (arm64-v8a, armeabi-v7a, x86_64, x86)

don't use hidden Magisk for patching, as it is a stub only.
[Google Pixel 6 Pro] Thebear j koss:
Worked perfectly on October patch. 👍🐻
[Google Pixel 6 Pro] banshee28:
Yep, was about to post my results from today!

Updating from last month to this new October patch:

Using 4.1.1 Linux build

Flashed to both slots, keeping all data

allowed flasher to patch bootloader for me, I simply choose all options in GUI, never touched phone

7 mins later, all done, fully rooted still, all data intact!!

Thanks! This is an awesome tool!
[Google Pixel 6 Pro] DeanO74:
Are you guys passing Verify on your 6 Pro after flashing a ROM patched with Magical using this app?
[Google Pixel 6 Pro] badabing2003:
I don't know what you mean by passing veify.

Safetynet is deprecated.

If you are using the Modded Saftenety module (not the original one) then Play Integrity check result the following.

Pass: - Meets Device Integrity

Pass: - Meets Basic Integrity

Fail: - Meets Strong Integrity (I'm not aware of any mechanism that passes this, even if you're not rooted but have the bootloader unlocked) there is a long thread specifically for this topic, which is Play Integrity
[Google Pixel 6 Pro] badabing2003:
Update Release:

Oct 05, 2022 v4.1.3 release

Bug Fix: Extract Magisk Manager version properly.
[Google Pixel 6 Pro] DeanO74:
Thanks. I found a little write up on adjusting some settings in Magisk and an updated module to install that's helped folks get things like their Gpay back up and going. I know as you told me, your app is simply an interface, a very helpful one too. I'll look into that thread, everything works but my Gpay oddly. Thanks again.
[Google Pixel 6 Pro] badabing2003:
This is the thread you're looking for, it's been discussed in depth.

Gpay does work.
[Google Pixel 6 Pro] badabing2003:
Update Release:

Oct 05, 2022 v4.1.4 release

Rooted Magisk patching will now automatically back up stock-boot.img (more to come).

Bug Fix #27, handle version exception.
[Google Pixel 6 Pro] rhetorician:
Wow, this has come a long ways since I was last here. Looking forward to playing with the newest Mac version soon!
[Google Pixel 6 Pro] bush911:
Just installed the latest 4.1.4 build and updated my Pixel 6 to October image with losing data and and root.

And everything works as expected 😃, thank you @badabing2003 for this outstanding app.
[Google Pixel 6 Pro] Caipi123:
I'm having issues with the boot.img validation:

any idea? Tried it several times, deleted everything, etc...
[Google Pixel 6 Pro] badabing2003:
This is a safety measure I have put in PixelFlasher, basically when Magisk patches a file, it does few things, and one of them is it embeds in the generated patch file, the SHA1 (hash) of the source boot.img that was used to create the patch.

PixelFlasher extracts this information from the generated patch file and compares it to the hash of the boot.img file that was used, if they don't match then it gives this warning and aborts.

See here the full details of it.

There are few possibilities and I would need few things (more about what I need further below) from you to confirm what is the situation with you.

1- It could be that everything is good, but Magisk just set the wrong hash in the patched image (this would be harmless Magisk bug)

2- It could be that Magisk used the wrong boot.img file even, in which case you don't want to use that patched file because it is not from the file you wanted to patch, (this would be a serious Magisk bug)

3- It could be that PixelFlasher is doing something wrong in the way it transfers the files or invokes the patching process (this would be very unlikely, in addition to the extensive testing that I do on this aspect, with validations printed in the console, there are way too many users of PixelFlasher, and they would have encountered it)

Let's hope for #1, we can fix it (I'm working on including automatic fix in the next version of PixelFlasher)

What do I need from you is first a sanitized support.zip file (see in help menu) so that I know about your device, the files that relevant to this issue along with their paths.

One I get that, I'll ask you to provide few other files, and probably few commands so that we know exactly what is going on.

Don't worry, we can fix this.
[Google Pixel 6 Pro] Caipi123:
thank you very much. I've attached the support.zip file. So far previous flashes went fine with the same magisk version (but of course different android version). Just let me know if you need anything else.
[Google Pixel 6 Pro] badabing2003:
OK Thanks

I see that you are not on Windows, are you on a Mac or Linux? (Note to self, I should add a log entry for platform)

Depending on the platform, the PF configuration folder is varies.

Let's first find out the Configuration folder.

The easiest way is to do it from PixelFlasher Help Menu, see if you have the option "Open Configuration Folder", unfortunately this menu is not available in all platforms.

No worries though.

If you are on Linux, then the configuration folder is: ~/.local/share/PixelFlasher where ~ is your home

if you are on a MacOS then the configuration folder is: ~/Library/Application Support/PixelFlasher where ~ is your home

Here's what I need next, navigate to the configuration folder, you would see boot_images folder in there

Grab the file boot.img in the folder: 912e5dba0da65a4404ee50899ef4d5192102275d

You also need to grab the file magisk_patched_912e5dba.img in configuration folder sub-directory tmp folder

zip and send them to me.

I will also give you couple of adb commands to execute to see the current state of Magisk on your phone.

This one lists files in Download folder to see what current boot.img and patched files reside (this could be a cause of Magisk confusion)

adb shell ls -l /storage/emulated/0/Download

This next command echoes the contents of Magisk config file, we'll see what is the SHA1 in there

adb shell "su -c 'cat $(magisk --path)/.magisk/config | grep SHA1 | cut -d \'=\' -f 2'"

This next command lists the backups Magisk has made of source boot.img files

adb shell "su -c 'ls -d -1 /data/magisk_backup_*'"

This command lists the files in rooted Magisk directory where the work gets done, (I might ask further commands to run based on the contents, this will provide further insight)

adb shell "su -c 'ls -l /data/adb/magisk/'"

NOTE to Pixel 6 Pro users

Considering that @Caipi123 device is Pixel 6 Pro, and I don't have Pixel 6 Pro,

It would greatly help if you could post an image like the below from PF if you flashed raven-tp1a.221005.002-factory-d61dff29.zip on your device and used Magisk 25.2:25200

This would help me know what should be the correct SHA1 of the patched image in this environment.

Even if your Magisk is not the same, post it anyways, it might help.

Thanks
[Google Pixel 6 Pro] Caipi123:
Yes, that's correct - I'm using MacOS. Attached the two boot.img files. Thanks again :)

% ./adb shell ls -l /storage/emulated/0/Download
-rw-rw---- 1 u0_a218 media_rw 67108864 2022-10-09 00:03 boot_912e5dba.img
-rw-rw---- 1 u0_a218 media_rw 67108864 2022-10-09 00:32 magisk_patched_912e5dba.img

raven:/ # cat $(magisk --path)/.magisk/config | grep SHA1 | cut -d \'=\' -f 2
fe2023f503d1c341ee94cad0f9ac44dfb9c4785e

raven:/ # ls -d -1 /data/magisk_backup_*
/data/magisk_backup_1bb81a80bd3b05ea755d4abcb2904b2526c7d4ed
/data/magisk_backup_1f3a0c538da50a418db827c20a3b742fb0b61025
/data/magisk_backup_2144ad3655b2cf1eb7c97952332fc4803966f2eb
/data/magisk_backup_df8f63e60043c12ac0c80346195faa69d4484b1a
/data/magisk_backup_ead36404c2bce9dad5bffa9d31dfd6effb09250e
/data/magisk_backup_fe2023f503d1c341ee94cad0f9ac44dfb9c4785e

raven:/ # ls -l /data/adb/magisk/
total 54843
-rwxr-xr-x 1 root root 3530 2022-08-16 00:57 addon.d.sh
-rwxr-xr-x 1 root root 5987 2022-08-16 00:57 boot_patch.sh
-rwxr-xr-x 1 root root 2107848 2022-08-16 00:57 busybox
drwxr-xr-x 2 root root 3452 2022-08-16 00:57 chromeos
-rwxr-xr-x 1 root root 51444224 2022-10-09 00:32 kernel
-rwxr-xr-x 1 root root 154452 2022-08-16 00:57 magisk32
-rwxr-xr-x 1 root root 247168 2022-08-16 00:57 magisk64
-rwxr-xr-x 1 root root 631848 2022-08-16 00:57 magiskboot
-rwxr-xr-x 1 root root 479592 2022-08-16 00:57 magiskinit
-rwxr-xr-x 1 root root 328240 2022-08-16 00:57 magiskpolicy
-rwxr-xr-x 1 root root 653956 2022-10-09 00:32 ramdisk.cpio
-rwxr-xr-x 1 root root 23888 2022-08-16 00:57 util_functions.sh