yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Oswald Boelcke:
@EmanuelCN I've edited your above post and deleted the other one!

Regarding social media links please observe that as an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads and if thorough support is provided in the thread. These conditions obviously don't apply to your posts in this thread Additional information is also available here:

Telegram Chat Channels - Way Forward

WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...

xdaforums.com

Please refrain from sharing links to social media on XDA unless done in your own development threads.

Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Google Pixel 7 Pro] TechX1991:
Came in to work today, co-worker showed me his phone and explained

- "I woke up this morning, and I'm stuck at this encryption screen after an OTA Reboot. It wouldn't accept my passcode to fully boot."

So we looked at his phone, I rebooted it to bootloader/fastboot, and his bootloader was unlocked

- "I've never unlocked it, I have no need to"

Background: We both work at a data recovery company, we both know the process of unlocking a bootloader (I've done it a million times personally). He had to re-lock it and factory reset.

Only thing I can think of is

- Temp unlock during ota install? it corrupted at this point and stayed unlocked

- Unknown exploitable glitch?
[Google Pixel 7 Pro] V0latyle:
OTA won't temporarily unlock the bootloader

Glitch...maybe.

How did he get the phone? I bet it was either unlocked before or he unlocked it not knowing what it did.
[Google Pixel 7 Pro] TechX1991:
If he said it wasn't unlocked prior, I believe him. It was from Google's online store. Purchased it unlocked straight from google.

Have seen a small number of reddit threads with this too, all with similar things

"Device was encrypted at power on needing pin, but after ota, pin didn't work and bl was unlocked?!?" but again, that's reddit... hardly often trustworthy lol
[Google Pixel 7 Pro] V0latyle:
Well, since there's other reports of the same thing, I suspect a bootloader issue.

I would say re-lock the bootloader but that's going to wipe his data.
[Google Pixel 7 Pro] TechX1991:
All his stuff was already wiped because the encryption pin on boot, pin wouldn't work, so unfortunately, all gone. Was more just wondering if anyone here has experienced this
[Google Pixel 7 Pro] V0latyle:
If it were a Verizon model I'd say root away but since he ostensibly wasn't rooted before or has any interest in doing so...

Really odd bug.

It'll be interesting to see if this affects Verizon models too
[Google Pixel Fold] badabing2003:
View attachment 5945853

This is the support thread of PixelFlasher

(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).

Note: This thread is meant for issues and problems faced in Google Pixel Fold devices, generic issues that are device agnostic should be discussed in the main thread.

For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.

IMPORTANT:

Please do not ask questions the answers of which are already stated in the OP.

I will simply ignore the request, as I'm fed up of referring people to the post that has the answers.

Troubleshooting:

If you need support or assistance, please generate and provide a support file from within PixelFlasher.

You can hit that big Support button on the main screen, or select it from the Help menu.

The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

And no, a screenshot of the console or an excerpt from the console, does not make a support file.

Clearly state the issue you're encountering, what actions did you take, and what outcome you observed, and what outcome you had expected.

Do NOT modify the support file, keep it intact.

See this post.

Generate Sanitized support.zip file (File Menu) and submit that with your report.

If your anti-virus program is telling you that PixelFlasher is a malware, or you are concerned in any way, please check this post.
[Google Pixel Fold] badabing2003:
New Release:

July 03, 2023 v5.4.0.0 release

Add Pixel Fold (Felix)

Add sorting capability to boot list.

Add warning about Magisk a8c4a33e:26103

Improved auto-resize of boot columns.

Improved internal DB management.

Handle beta or similar words in the firmware name to not trigger hardware mismatch warning.

Improved tracking the origin of a patched image.

Display Kernel version as part of device details

Refresh package manager list when packages are updated to reflect the changes.

Miscellaneous other improvements.

Update Readme.
[Google Pixel Fold] badabing2003:
Placeholder
[Google Pixel Fold] Moose0704:
I ran the Pixel Flashed and followed the directions, the process on my phone stopped at Fastboot Mode and has not gone any further, is it still doing something or do I need to make a selection on the phone?
[Google Pixel Fold] badabing2003:
support file please, that's how I can tell where exactly it is at and what's going on.
[Google Pixel Fold] Moose0704:
View attachment 5946471

I tried to get it but the program just froze
[Google Pixel Fold] Moose0704:
View attachment 5946473
[Google Pixel Fold] badabing2003:
Kill the program, start it again and generate a support file

I'll take a look
[Google Pixel Fold] Moose0704:
Thank you for your time!
[Google Pixel Fold] badabing2003:
You're bootloader is locked, you can't flash the selected Magisk_patched init_boot with a locked bootloader.

I'll add a check to not allow selecting it.

What is the current state of the phone? does PF detect it when you scan?

If it detects it in bootloader mode, it you should be able to reboot to system, and you'll have felix-ota-tq3c.230605.010.c1-4f136d8d version (I think that is the situation, because I see you flashed twice, and it switched slots)

You have two options.

1- Unlock the bootloader (if you want and can), but that will wipe your device (you can do it in PF)

2- If it does not boot to system, then just select the stock boot entry in the boot list (the one without a patch) and flash again.
[Google Pixel Fold] Moose0704:
Yeah, so while waiting on a response I found the issue, I needed to update my drivers on the pc, did that and then unlocked bootloader, running the Pixel Flash again. I will let you know if I run into any issues.

Sorry for wasting your time, I should have checked that before messaging. I greatly appreciate your time to look at this.
[Google Pixel Fold] badabing2003:
@Moose0704

Sorry won't be adding such check, as Universal Safetynet Fix spoofs the prop, hence no true way of determining if PF is dealing with locked bootloader or not.

Perhaps one day, when I find a lightweight Play Integrity check client that I can run through ADB, I'll use that.
[Google Pixel Fold] Moose0704:
No worries, totally understand. I should have checked it myself lol
[Google Pixel Fold] lorddunlow:
Just used this to flash last night. No problems at all (except I started in fastboot mode and couldn't figure out why I couldn't patch the init_boot...) 🤦

It automated unlocking the bootloader, patching/flashing the init_boot, and installing Magisk. I used Canary build with no issues.

Thanks for the app. I was planning on doing it old school, but I was on vacation and this had released by the time I got back. The less typing adb commands, the better.
[Google Pixel Fold] lorddunlow:
I also have it passing SafetyNet with a combination of Magisk Hide, Displax fork of Universal SafetyNet Fix, and Shamiko. Had some play store issues with apps saying not available until I wiped the cache and data for Play Store. Everything I've tried works now.

Glad to have my root apps going again.
[Google Pixel Fold] sawdoctor:
Got myself into a bit of a mess rooting as its my 1st pixel device so want to make sure I don't mess up again.

I am currently rooted and want to update to the July drop. I have downloaded both full factory image and the ota. I have extracted the init.boot and patched with magisk. Am i best installing the ota and which slot to flash to or is it best both ? and same again which slot do I flash the patched init.boot to or does pixelflasher sort that out automatically ? Sorry for all the questions just don't want to mess up again
[Google Pixel Fold] badabing2003:
My recommendation would be:

Since you've downloaded both Full OTA and factory, I'd go for full OTA for is benefits.

With OTA you don't choose slots, it always flashes to the inactive slot and that's for good measure because it anything goes wrong your current slot is still good and bootable.

With PF you don't manually extract boot or init_boot, the program does everything for you.

1- Select full OTA, and process it, it will extract boot / init_boot and you will see it in the list.

2- Select the boot and hit patch, a patched version will show up in the list.

3- If you want to be stock , select the stock boot from the list, if you want to be rooted, select the patched boot from the list.

4- Hit Flash Pixel Phone.

5- Optional, if you want both slots identical and bootable, repeat step 4 after the phone has finished optimizing.

You can repeat these steps with every monthly update.
[Google Pixel Fold] sawdoctor:
Thanks so much for your help, really appreciated. Things have changed so much the last few years, I've not rooted a phone since the galaxy note 4 and still getting back into the swing of things
[Google Pixel Fold] sawdoctor:
Everything went fine updated to July ota and still rooted. I did however get the same Pixelflasher is not responding popup as @Moose0704 but I simply pressed wait and then it continued to flash successfully
[Google Pixel Fold] badabing2003:
Support file might give me the clues on why it appeared non responding.
[Google Pixel Fold] sawdoctor:
Sorry for late reply been away from pc. Like I said I just pressed wait and then everything was fine
[Google Pixel Fold] badabing2003:
Thanks I don't see anything wrong in the logs.

I see that you're on Linux.

I'm wondering if the output on the Linux is buffered / delayed giving you the impression that the app is stuck?

Flashing took 523 seconds (that's close to 10 minutes, OTA is always slower than factory)

serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~84%)
serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~85%)
serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~86%)
serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~87%)
serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~88%)
serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~89%)
serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~90%)
serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~91%)
serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~92%)
serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~93%)
serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~94%)
Total xfer: 2.00x
rebooting to bootloader ...
Sleeping 5-10 seconds ...
flashing pf_boot ...
< waiting for REDACTED >
Sending 'init_boot_b' (8192 KB) OKAY [ 0.251s]
Writing 'init_boot_b' OKAY [ 0.015s]
Finished. Total time: 0.269s
rebooting to system ...
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.051s
2023-07-11 12:28:59 Done!
Flashing elapsed time: 523 seconds

When it appeared unresponsive / frozen do you recall what was displayed on the screen in PF console?

Were you seeing the progress of the flashing output? (the percentage)

serving: '/home/sawdoctor/Downloads/felix-ota-tq3c.230705.001.c1-4419bfbb.zip' (~xx%)

Or did it display all in one shot when the flashing was completed?
[Google Pixel Fold] sawdoctor:
It was strange it was stuck on 91% when I got the popup about not responding, I clicked wait and then it went to 94% and then rebooted and flashed the patched boot img. It never actually showed 100% or I don't remember seeing it but everything works and I'm fully updated. Think you maybe right about it being a Linux buffer issue, Linux likes to cache a lot
[Google Pixel Fold] badabing2003:
Thanks for the clarification.

I have never seen it go to 100%, all the OTA sideload flashing I have done, they all went up to 94%

I have noticed that the progress is not linear, sometimes it goes quickly on some percentages, and then on others it take quite a while, I suppose that is a progress reporting issue in sideload streaming.
[Google Pixel Fold] badabing2003:
New Release:

July 13, 2023 v5.5.0.0 release

Added a patch method Other Magisk App to be able to select any Magisk apk and use it to create a patch without installing Magisk, handy when a patch needs to be created with an older version of Magisk (in case the current version has issues) and Magisk daemon gets in the way and replaces the older version with a stub.

UI improvements

Added Kill Application in Package Manager.

Added Clear Application Data in Package Manager.

Now that Full OTA flashing is the preferred method, added a direct link to the device's full OTA download page from Google.

While flashing, disable the Flash Pixel Phone button to avoid accidental clicking.

Improved root detection.

Bug fixes and other improvements.
[Google Pixel Fold] badabing2003:
Bug Fix Release:

July 14, 2023 v5.5.1.0 release

Bug fix #85 Can't enable/disable Advanced option in v5.5.0

A little improvement #84 UI elements not optimized for monitors with low screen resolution
[Google Pixel Fold] badabing2003:
New Release:

July 16, 2023 v5.5.1.1 release

#84, further UI improvements for smaller screens.

Better dark mode handling for MacOS and Linux.

#86, improved handling of space characters in paths.
[Google Pixel Fold] ethical_haquer:
Man dude! How do you post a new release to that many threads so quickly? 😲
[Google Pixel Fold] badabing2003:
From the main thread, I have links to each thread.

I first open them all in my browser.

and then paste in each and submit :cowboy:
[Google Pixel Fold] badabing2003:
New Release:

Aug 07, 2023 v5.6.0.0 release

Added configurable toolbar.

Added device controls buttons to the menu.

Added feature to Magisk Manager, ability to install modules from the PC.

After flashing OTA, detect if the slot switched as expected, if it didn't, skip patched boot flashing (if selected).

Added feature to Package Manager to be able to manage (add, remove, list) Magisk denylist.

Added export csv formatted package list feature.

When sanitizing DB, wipe write-ahead logs (WAL) for better privacy.

Under the hood optimizations.

Verity / Verification status check.

Counter in package manager.

Added a quick link to Android security and update bulletins.
[Google Pixel Fold] Colchiro:
I'm on today's update and having trouble with the Roboto Mono font from Google on Windows 11.

I installed the font in the Windows Fonts folder, selected it in PF, then clicked OK, only to have it revert back to Consolas. I finally got it to stick by unchecking the "Use Custom Fontface" checkbox before clicking OK, which disables the font dropdown. Then I tried to change the font size from 12 to 11 and again, it won't stick, in fact it seems to hate 11px.

It's working fine for Notepad++.
[Google Pixel Fold] badabing2003:
There seems to be a bug in applying the changes.

I'll have it fixed for the next release.

In the meantime you can edit PixelFlasher.json file (Help Menu | Open Configuration Folder)
[Google Pixel Fold] badabing2003:
New Release:

Aug 09, 2023 v5.7.0.0 release

Rework the settings window: code refactoring and bug fixes.

Bug Fix: In some cases log files were not saved.

Bug Fix: Custom font size changes were not always applied.

When getting device details, get battery details.

Don't set ASH_STANDALONE=1 when using busybox, it encounters selinux related issue.

Extra check to make sure the created patch is not zero bytes long.
[Google Pixel Fold] Colchiro:
Custom font works great now. Thanks!
[Google Pixel Fold] badabing2003:
New Release:

Aug 13, 2023 v5.7.1.0 release

Print available memory when starting PixelFlasher.

Option to sacrifice speed in favor of using less memory (used when processing large firmware files, turn it on only if you run into out of memory errors).
[Google Pixel Fold] badabing2003:
New Release:

Aug 15, 2023 v5.7.2.0 release

Regression Bug fix: Refresh UI to display / hide flash options after changing advanced settings.

Use Python 3.11 instead of 3.10
[Google Pixel Fold] badabing2003:
New Release:

Sep 19, 2023 v5.8.0.0 release

Added support for scrcpy (Screen Copy), you can now launch scrcpy to the attached device, configuration is done in the main settings window.

Completely redid the wireless connection, there is now wireless manager, that shows history, status and quick selection from history, and supports wireless debugging which requires pairing and is the only option for newer OS-es.

For crDroid and other non Pixel firmware automatically set to Full OTA mode (ie sideload) if payload.bin is detected.

Added a button to reboot to userspace fastboot (fastbootd).

Added system menu to be able to move, resize, minimize, maximize. (useful when the window is of the screen)

When extracting from payload.bin, optionally also extract (if available) dtbo.img, super_empty.img, vendor_boot.img, vender_kernel_boot.img in addition to boot.img and init_boot.img (configurable in the settings), as some of these images are needed for 3rd party firmware flashing.

On Linux, display a message when terminal app is not set and open shell feature is used.

For Samsung devices, when creating a tar file of a patched boot, use POSIX tar format.

Miscellaneous fixes and improvements.
[Google Pixel Fold] Dixo213:
I suspect this cannot work for a Verizon Pixel fold , as we cannot unlock the bootloader?
[Google Pixel Fold] badabing2003:
Correct, you cannot root because you cannot unlock the bootloader.But you can still flash full stock OTA using PF and it will be much faster than doing it on the phone.
[Google Pixel Fold] Dixo213:
So if I buy a Verizon phone that is locked I can flush a full NON Verizon image?
[Google Pixel Fold] Dixo213:
It s been a while I haven't done anything on my Pixels . .
[Google Pixel Fold] badabing2003:
no, just the stock monthly updates
[Google Pixel Fold] Dixo213:
OK tx:). I want that dam phone but 1800$ is way to much...
[Google Pixel Fold] badabing2003:
New Release:

Sep 24, 2023 v5.8.0.1 release

Bug fix: #99 Settings not opening on linux/arch based distro
[Google Pixel Fold] badabing2003:
Update Release:

Oct 06, 2023 v5.8.0.3 release

Improved debug messages for troubleshooting.
[Google Pixel Fold] ggrks:
This is my first time using PixelFlasher. Keep data is grayed out and cannot be selected... What am I doing wrong?
[Google Pixel Fold] badabing2003:
You're doing nothing wrong, you probably are using Full OTA image, which always keeps data.
[Google Pixel Fold] ggrks:
thank you for your reply. Does the fact that data is always retained mean that the data will not be lost even if you flash it?
[Google Pixel Fold] badabing2003:
Correct, with OTA updates, data is not wiped, however you can only OTA flash same version or higher, if you need to downgrade, you would need to wipe.
[Google Pixel Fold] ggrks:
thank you! I took the plunge and flashed it, and was able to perform OTA while retaining the data! Thank you for a very useful tool!
[Google Pixel Fold] almony8:
Can someone please help me? I have been unable to get root on my pixel fold since the first qpr beta release for some reason. I can flash the ota and update the phone no problem, but as soon as I use pixel flasher to patch the file and then try to flash I just get bootloops and have to reboot to recovery and sideload the unpatched ota file again to get back up and running. I don't have any modules or anything installed on my phone at all, and I was able to root every version before, until the last 2 or 3 that I can't seem to get root on. Am I missing a stupid step maybe? Do I need to go into advanced mode in pixel flasher and flash to both slots or something?
[Google Pixel Fold] badabing2003:
If you're flashing OTA, there is no such thing as flash to both slots, it always flashes to inactive slot.

There is also no such thing as Wipe or Keep Data, it is always Keep Data.

To recover, you don't have to sideload the entire OTA,

All you have to do is flash back the stock init_boot.

Select it in PF and hit the Flash Boot File, (not Flash Pixel Phone)

But the fact that you were previously rooted, suggests that there are some remnants of Magisk, probably incompatible modules that are interfering with the new version.

Try booting to safe mode which disabled the modules, and see if it boots fine (this is when you're bootlooping)

If it does, then it's one of the modules, enable one a time until you find the culprit.

And if you need further assistance, please provide the support file, that helps me a lot to troubleshoot the issue.
[Google Pixel Fold] almony8:
Ok, so I was flashing the OTA right the whole time like I thought then.

As far as recovering, I'm not sure how to flash back the stock init boot file when my phone just continues to bootloop. So I just power it off with volume up and power, then boot into recovery and sideload the ota. I just don't know how to flash the stock init boot back if I'm in a bootloop, as pixel flasher doesn't register it if it keeps rebooting like that?

Not sure about remnants of magisk or modules as I went through the phone and uninstalled all of it? Could it just be files that didn't get deleted for whatever reason when uninstalling the apps? Basically I have booted up without root on the newest beta and made sure that I had nothing root related installed, then went back to pixel flasher and patched the file, then flashed it and got bootloops. I will look through files and apps again and see if I find anything I guess, but not sure that's my issue.

I will try it all again later tonight or tomorrow morning and see what happens. I'll send a support file if it doesn't work again. Thanks for the reply
[Google Pixel Fold] badabing2003:
Unfortunately it's the not apps that you need to clear, or at least almost never the case.

It's the modules, and it's a chicken and egg situation, you can't clear the modules unless you're rooted.

But if you manage to get into safe mode, then it will disable the modules.

Here's how to get into safe mode.

While you're bootlooping, you can click on PF's SOS button, and see if it takes you to safe mode, for that to work, the device has to very briefly get into adb mode during the bootloop, often it does and it works, but if it doesn't, then try the key combination, and unfortunately that would require proper timing, and it's not known to work 100% of the time.

If that doesn't work, you have one last option, in PF, click on Install Magisk, and read about the Special Magisk.

It is a special version that does not load modules but gives you root, it will only be used temporarily to get around the chicken and egg issue.

Lastly, to be able to flash init_boot, you need to get to bootloader mode, not recovery.

You can try the key combination, or from recovery type adb reboot bootloader

Of course this is assuming that your bootloader is unlocked which should be if you want to root.

once in bootloader, you can just flash the stock init_boot and that should be enough to get it back to non-rooted system, at which point you can install the special Magisk or use it to create a patch.