yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7a] badabing2003:
New Release:

Feb 16, 2024 v6.8.0.3 change log:

Added untested support for patching with KernelSU for Pixel phones. Patching with APatch is in the works.

Detect known blacklisted kernel names, and notify the user. (list is current as of this release date).

Rename the SOS button to reflect that the modules would be removed instead of being disabled.

Removed bulk install APK feature which installed all APKs in a directory, instead reworked the Install APK feature to allow user choice multi-select, and added another option Bypass low target SDK block.

Report device Kernel and KMI.

Added Android Platform Tools 34.0.4 to known problematic versions list, which when detected warns the user.

Improved Pixel Watch flashing dialog messages.

New feature: #152 Show System Apps and Show 3rd Party Apps in Package Manager.

Bug Fix: #157 'PifManager' object has no attribute 'first_api' in some situations.

Bug Fix: scrcpy download link was not working.

Support for upcoming PlayIntegrity Fork v8 changes by @osm0sis.

Added Special Magisk 27001 install option when selecting Magisk install. (This is similar to Special Magisk 26401, just a version difference).

Support for SSL error fallback for all https requests (previously was only for PIF downloads).

Improved factory / image downloading with lower memory footprint.

Miscellaneous minor bug fixes and enhancements.
[Google Pixel 7a] badabing2003:
Update Release:

Feb 17, 2024 v6.8.0.4 change log:

Use MacOS 13 to build with Github actions instead of MacOS 11, sorry to folks who use older MacOS, unless I get it to build it successfully on Github, MacOS 13 will have to do.

#158 Fix the App version.

Note: The following versions have identical code 6.8.0.0, 6.8.0.1, 6.8.0.2, 6.8.0.3, 6.8.0.4, the differences are in Github actions.
[Google Pixel 7a] badabing2003:
Update Release:

Feb 29, 2024 v6.8.1.0 change log:

Update Xiaomi apk download function to handle exceptions and work with the latest version.

#160 Update readme to add pre-requisites for MacOS and Windows platforms.

#161 Auto detect file encoding before opening a file.

Don't check for Magisk path if in recovery mode.

Misc. bug fixes and improvements.
[Google Pixel 7a] badabing2003:
New Release:

Mar 03, 2024 v6.8.2.1 change log:

Bundle in the executable the missing files android_version.json and android_devices.json otherwise patching with KernelSU won't detect your Pixel as Pixel device.

Add back Magisk Alpha install option, thanks to pull request from @hldr4

Make Magisk install window resizable.

Add right click option on the selected Magisk to download in case you just want it downloaded and not installed.

Update all old forum.xda-developers.com links to xdaforums.com

Make Pif Manager work without a device being connected (obviously for props / pifs management and not for updating / testing pifs).

Typo fixes and other minor improvements.
[Google Pixel 7a] badabing2003:
Update Release:

Mar 11, 2024 v6.8.3.0 change log:

Fix MacOS builds, we're finally back to buiding with MacOS 11 (fingers cross it lasts).

If internet is not available, do not try to build a menu with Google Devices.
[Google Pixel 7a] traverse_m:
Hi,

I'm having problems rooting my Pixel 7a. Whenever it reaches 94%, it would stop and the following error would appear.

Encountered an error while flashing

Traceback (most recent call last):

File "Main.py", line 4035, in _on_flash

File "modules.py", line 3728, in flash_phone

File "modules.py", line 3620, in reboot_device_to_bootloader

AttributeError: 'NoneType' object has no attribute 'reboot_bootloader'

I would appreciate any assistance to resolve the issue. Thank you.
[Google Pixel 7a] badabing2003:
First order of question: is your bootloader unlocked?

94% is ok, it means 100%, don't ask me, ask Google, it's a bug in sidleoad reporting progress.

Your device is not detected when it is in bootloader mode, which is required to apply the patch to root,

There's two parts to the process,

applying the update, which is done already, when you see the 94%

applying the patch, which is not done, because your device cannot be detected when it reboots to bootloader.

Have you installed Google's USB drivers? even in bootloader mode?

You don't have to do Flash Pixel Phone again, you're already on the latest OS release, no need to waste time, same goes for Porcee the necessary files are already extarcted.

You also don't need to patch again, unless you want to change the Magisk version or the OS version or the device.

So what do you do from here? Once you sort the detection issue (you can try different cable / usb port / pc)

All you have to do is select the patched init_boot from the list and hit Flash Boot (Not Flash Pixel Phone)
[Google Pixel 7a] traverse_m:
Thank you for your kind assistance. I managed to root my Pixel 7a after following your advice.
[Google Pixel 7a] badabing2003:
New Release:

Mar 19, 2024 v6.8.4.0 change log:

When patching with KernelSu on devices that have init_boot partition, patch boot partition, not init_boot.

Added Dev Tools | keybox.xml validity checker (credit to @hldr4)

Extra Img Extraction setting now additionally extracts dtbo, vendor_boot, vendor_kernel_boot, super_empty (useful for some ROMs).

When custom patching, Paste button will automatically paste the path to the (extra) image type selected.

Improved logging.
[Google Pixel 7a] WoolfishStrives:
Hi, loving the tool, what's the difference between PixelFlasher.exe and PixelFlasher_Win_2019.exe?
[Google Pixel 7a] badabing2003:
2019 is built with older Python to support older OS-es like Windows 7,

It's named 2019 because it's built with GitHub action on Windows 2019 base OS.
[Google Pixel 7a] badabing2003:
New Release:

Mar 26, 2024 v6.9.0.0 change log:

Add support for patching KernelSU LKM (Kernel modules, GKI only). This is in addition to the classic KernelSU support.

Add support for patching with APatch

Rename Install Magisk to Install Root App as it now supports directly installing KernelSU and Apatch through PixelFlasher.

Add Install ZygiskNext module option in Magisk tool options.

Use UTF-8 encoding for the logifile instead of ISO-8859-1

Miscellaneous minor improvements.
[Google Pixel 7a] Sneeder:
Hi @badabing2003 I read that TWRP got finally updated and I was wondering if now it can be built for Pixel 7a, am I missing something?
[Google Pixel 7a] badabing2003:
I have no idea, You'd have to ask the question in twrp threads.
[Google Pixel 7a] djavo22:
Hi.

I have successefully rooted my Pixel 7a via pixelflasher & magisk.

What I need to do if system get updated at some time? do I need reflash again magisk etc.

curently I am on latest A14,

thanks
[Google Pixel 7a] badabing2003:
You repeat the same process.

Download and load new image

Process

Select the extracted boot and hit patch

Select the patched boot and hit flash pixel phone.
[Google Pixel 7a] badabing2003:
New Release:

Apr 05, 2024 v6.9.1.0 change log:

#181 Handle KernelSU new output filename format.

#187 register exit menu id for MacOS to OS's "Exit" menu.

KernelSU bug fix and improvements.

Improved logging to further easy troubleshooting.

Update banned kernels list.

Update and re-add Magisk zygote64_32 canary with a forked URL.

Minor typo corrections and other improvements.
[Google Pixel 7a] djavo22:
Is it okay that I haven't received the April update for my Pixel 7a yet? Is this related to my region, or could it be because I flashed and rooted the phone? Sorry for the question, I just got the phone about 10 days ago and I'm still getting familiar with everything. Thanks!
[Google Pixel 7a] AutomaticFailure27:
I did all the initial updates through the phone and it ended up at the March update as the latest. Was able to flash the April OTA to manually update.
[Google Pixel 7a] djavo22:
Thank you. I did it that way. I did the update using adb sideload and then re-rooted using pixelflasher and the factory image for pixel 7a. Everything works fine :)
[Google Pixel 7a] badabing2003:
Update Release:

Apr 09, 2024 v6.9.1.3 change log:

Fix regression introduced when refactoring code in KernelSU Patching.

#187 On MacOS, move the exit menu into PixelFlasher's file menu from the OS's native Exit menu.
[Google Pixel 7a] badabing2003:
New Release:

Apr 14, 2024 v6.9.2.0 change log:

Add a new experimental feature to downgrade without a wipe and potentially switch from Beta to Stable without a wipe (untested).

Credit to @tbalden for the discovery and @capntrips for the details of the process.

Select any img file and get additional image info.

#190 fix, scrcpy launch improvement.

Improved Menu to disabled advanced features when it's not enabled in the settings. (Previously only other GUI elements were hidden or disabled).

If KernelSU or APatch is installed, report their version as part of device details.

Improved logging.

Improved santization.

Other minor improvements and added stability.
[Google Pixel 7a] badabing2003:
Update Release:

Apr 16, 2024 v6.9.2.5 change log:

Roll up MacOS related changes. #187 and #190

Logging improvements

When Magisk delta is installed, automatically set the package to: io.github.huskydg.magisk
[Google Pixel 7a] badabing2003:
Update Release:

Apr 19, 2024 v6.9.3.0 change log:

Update AVBTool to use RSA library instead of depending on an external openssl.

English typo corrections.

When flashing OTA, give the option to continue, even if it is a downgrade.

Github action: Fix MacOS build deployment issue.
[Google Pixel 7a] badabing2003:
Update Release:

May 08, 2024 v6.9.4.0 change log:

Added encryption to support.zip for extra privacy / security.

Regression bug fix: When a Magisk module was disabled in Magisk, it was not reflected in PixelFlasher.

Added Refresh button to refresh Magisk module list at will.

When Apply Custom ROM checkbox is checked, make sure that a ROM file is also selected, otherwise ignore the selection.

After rebooting to bootloader, if the device is not detected, sleep 5 seconds and try again.

Update Readme to include a link to proper USB driver setup on Linux systems.
[Google Pixel 7a] badabing2003:
Update Release:

May 17, 2024 v6.9.5.0 change log:

Added Pixel 8a (akita) support.

Updated Pixel device end of life dates based on Google's published data.

Added an option to refresh Google Images download links, useful on release days when you want an immediate refresh.

Memory improvements when building Google Images list.

Added additional troubleshooting debug messages when a device is not detected.

Minor bug fixes and improvements.
[Google Pixel 7a] frank93:
i’m on magisk "classic" currently and would like to switch to kitsune -- and had one failed attempt already (using the kitsune app and "direct install", resulting in a bootloop, luckily i was able to flash stock firmware again, manually, to get my device up and running).

is there some easier ("best practice") way to do this (switch from magisk to kitsune) using pixelflasher maybe? or maybe at least escape such a bootloop when it happens? (today i managed to "pause" the loop within fastboot and then used an edited flashall.bat, but that’s not something i’d wanna do again ..)

the "patch" button in pixelflasher offers me to patch the boot image using magisk or kernelsu or apatch etc, but no kitsune here.

android 14 stock, latest may update, pixel 7a, both slots "working" currently (with magisk) ..

thanks in advance for any help!
[Google Pixel 7a] badabing2003:
All the different flavors of Magisk share the same directory /data/adb, which could cause issues when a new Magisk finds config / modules in there (not necessarily, but could be one source of problem)

The proper way to install a different flavor of Magisk is

First clear a previous magisk data /data/adb by deleting the directory as root.

Uninstall Magisk Application

Select stock boot and create Magisk patch (yes choose Magisk for any flavor)

You would be presented with which flavor to install (you could choose to install prior to creating a patch by clicking on Install Root App)

Flash the patch

By the way, Kitsune is listed as Magisk Delta
[Google Pixel 7a] frank93:
i see - thank you so much. tbh i was hoping to keep all the modules and their settings throughout the "switch" -- this sounds like a fresh reinstall (more or less), so it will have to wait until the weekend when i’ve got a bit more time to think it all through and make the correct backups before. but: sounds plausible and doable. thanks! <3
[Google Pixel 7a] badabing2003:
You can try keeping them, it might work, it's preferable that you do a fresh install, but try keeping them.

To achieve that, you do the following.

Install Magisk of choice using Install Root App button, pay attention to the package name, copy it by right clicking on the line.

Go to PF settings and check Offer Patch Methods, and change the Magisk Package name with the one you copied (if it isn't already updated by PF)

Now create a Magisk Patch, you will be offered additional options. Make sure you select Use Magisk Application after making sure that the application version is the correct Magisk you wanted (in this case Kitsune) (You can also choose Other Magisk and select a downloaded kitsune apk, but if you did the previous steps properly, the Application option should be good)

Flash the created patch by using Flash Boot button (not Flash Pixel Phone)

If the modules or the config cause a bootloop, all you have to do is Flash Boot the previous Magisk (std one) and then follow the previous post steps.
[Google Pixel 7a] frank93:
amazing, will try that tomorrow.

it’s times/comments like these when i honestly wish there was some donation/support button in pixelflasher, but, yeah, i know .. :-)

<3 thank you!
[Google Pixel 7a] badabing2003:
Update Release:

June 04, 2024 v6.9.6.0 change log:

#204 Fix Pyinstaller issue, thanks to PR from @cjshearer.

PIF Import favorites can now import recursively including subdirectories.

Added Device | Check otacerts menu option to quickly check if the ROM is signed.

Sync banned kernel list with @osm0sis published list.

Improved exception handling

Improved debug messages for troubleshooting

Fix timing issue for a corner case cleanup before unzipping is completed.

AVBTool improvements.
[Google Pixel 7a] badabing2003:
Update Release:

June 24, 2024 v6.9.8.0 change log:

Improve Check keybox.xml to report if the certificate is software signed, also report about all included certificates.

Added settings option Keep temporary support files in case one needs to inspect the support files.

Add Github action to build on MacOS 12, MacOS 11 runner has been deprecated.

Update Pixel beta links from A14 to A15.

Minor bug fixes and improvements.
[Google Pixel 7a] badabing2003:
New Release:

July 4, 2024 v7.0.0.0 change log:

When sideloading OTA, automatically cancel a previous OTA (in progress or completed but not rebooted), which assures a better success rate. (Only applies to rooted devices that are in adb mode).

Added My Tools Menu, you can now add custom tools to PixelFlasher to easily launch your favorite tools / apps (example odin3).

Added Process Image in PIF Manager, PixelFlasher can now process a device image and extract PIF print from it with a single click. (Currently supported image types are, Pixel firmware, Pixel OTA, images with payload.bin, Samsung firmware).

When reading device details, report the sys.oem_unlock_supported prop value.

Miscellaneous minor improvements.
[Google Pixel 7a] badabing2003:
Latest Release:

July 11, 2024 v7.1.0.0 change log:

Add license headers to source files.

Improved logging.

By request, PIF Manager now supports processing img files to extract PIF prints. (This is in addition to supporting zip files of factory / OTA images).

Check keybox.xml tool now provides more extensive report about the keybox.
[Google Pixel 7a] badabing2003:
Update Release:

July 14, 2024 v7.1.1.1 change log:

Bugfix: #222 Customize My Tools menu is duplicatede when no tools are added.

July 14, 2024 v7.1.1.0 change log:

Windows versions of PixelFlasher are now signed (self-signed).

Hopefully this would cut down on false positive virus / trojan alerts, but it should also get rid of Unrecognized app warnings.

PixelFlasher.crt is the certificate, and ca_badabing2005.crt is the root CA.

Bugfix: #221 handle a corner case exception.
[Google Pixel 7a] badabing2003:
Latest Release:

July 27, 2024 v7.2.0.0 change log:

In Magisk Manager, added the option to install Tricky Store module. (You now have 3 PIF related modules to choose from, Playintegrity Fix, Playintegrity fork, Tricky Store).

Updates to PIF Manager:

Option to convert from Json to prop (Env) format and vice versa (Tricky Store uses prop format) .

Compatible with Tricky Store (latest CI), you can now edit / update / test using Trick Store module.

Note: Tricky Store module does not yet support automatic updates, hence PixelFlasher is currently setup to point to the latest release in Github, this still uses Json file to spoof prints, use the latest CI.

If you have multiple PIF modules, for example if you use Trick Store and PiFork together, you can select which module's print you want to edit / update by selecting from the combo box. (Only enabled PIF modules are listed).

When loading prints from favorites, or console output, or using Smart Paste, PixelFlasher automatically converts the print to the format (json / prop) that the module requires.

Added option to push keybox.xml file to Tricky Store's predefine path.

Added a button to generate FrameworkPatcher compatible code for use in Android.java, just select the print, generate code and paste it in the proper section of Android.java to use your custom print with FrameworkPatcher.

Note: the generated code by default is commented out, as you can select multiple prints, just uncomment the ones you want to apply.

Added option to backup / restore /data/adb directory, please be aware that this only backs up / restores /data/adb/*, any modules that installs files outside this path will not be backed up, as it's impossible to know what all modules do.

New features in My Tools Manger:

Different methods to launch application.

Option to enable / disable launching detached process.

Option to insert separator.

Note: Start with the defaults and experiment if default behavior is unacceptable.

Miscellaneous fixes and improvements.
[Windows 10, 8, 7, XP etc.] cmfCyangenModteam:
Since, i have an laptop with Windows Longhorn than i installed on another partition, would Windows XP apps work?
[Windows 10, 8, 7, XP etc.] ze7zez:
If the applications are standalone i.e. do not require installation, they will work.

Some of them will require setting the compatibility mode to Windows XP.
[Windows 10, 8, 7, XP etc.] cmfCyangenModteam:
Thank you.
[Windows 10, 8, 7, XP etc.] TravisBean:
Windows XP rules.
[Touch Pro, Fuze Themes and Apps] hopper13:
Has anybody tried updating to the new version?
[Touch Pro, Fuze Themes and Apps] plfinch:
Yeah, I'm using the latest version. They have an "HTC Upgrade" special on their website. Think it was $19.99. You get both Sprite Backup and Sprite Terminator for that price. I had done the same upgarde on my Tilt (which is now my wife's).

Peter
[Touch Pro, Fuze Themes and Apps] TaurenSnake:
It is only $10 if you want just the Sprite Backup upgrade.

http://www.spritesoftware.com/?page_id=275
[Samsung Galaxy Watch] sgtcoldxx1:
anyone know how I could remap the long press since Samsung pay keeps popping up every 5 mins

or how to fix the Spay bug thank you.

or if i could root it and run a custom rom without Samsung pay
[Samsung Galaxy S21+] ronith01:
This is strange, overnight my phone lost LTE bands. Now only supports 7, 38, 42, 46 and 48. It used to support 1,3 etc. Now only 5G works for me.

View attachment 5914613

What I have tried:

Did a flash using Odin.

Tried the guide to enable bands for s22 etc that's available on XDA

Did crossflash using Odin (g996u, different carriers)

Tried changing sim card

But now only 5G works 😞

Is this a hardware issue, if not how to fix? Helppp
[Samsung Galaxy S21+] ronith01:
Can anybody tell me where the 4G antenna is located?
[Samsung Galaxy S21+] EncryptedCurse:
@ronith01 Were you ever able to figure anything out about this? I'm missing even more bands than you. I only have 46 for LTE and 260 + 261 for 5G. I've also tried all the troubleshooting steps you mentioned in your first post on top of extensively fiddling around with the service menu (*#73#).
[Samsung Galaxy S21+] Ronith128:
No, I enabled some more 5G bands using a guide that was in XDA. But only 5G bands. The bands that were lost is still not back
[Samsung Galaxy S21+] EncryptedCurse:
Thanks. I'm currently trying to mess around with QPST. I'll report back if I find anything.
[Samsung Galaxy S21+] YakirOz:
Did you manage to get any progress?
[Samsung Galaxy S21+] EncryptedCurse:
Unfortunately not...I ended up just trading it in. 😕
[Samsung Galaxy S21+] YakirOz:
God that sucks! Did you try to downgrade your phone too?
[General Topics] tarkzim:
​

Unofficial TWRP 3.7.0 For Samsung Galaxy A14 5G

Disclaimer

*I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
*Please do some research if you have any concerns about features included in this recovery before flashing it!
*YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.

Features:

Android 13 support

flash of zips

fastbootd

MTP

What's not working:

Decryption support

Flash GSI image

You tell me.

Supported models:

A146P

Downloads:

A14 5G [MediaTek]: Download

Changelogs:

How to install

Make sure your bootloader is already unlocked and OEM unlock is enabled, otherwise the installation will fail.

Download and install Samsung Drivers

Download the latest *.tar for your phone

Download Odin, from example from https://downloads.corsicanu.ro/samsung/

If not done before, flash disabled VBMeta with Odin in USERDATA or CP slot (originally posted here).

Turn off your phone, connect it to PC and reboot to download mode by holding down Volume up, Volume down and power button at the same time.

Open Odin and check if your device is detected, then untick "Autoreboot" in its settings.

Put the tar file you downloaded into the AP tab

Click start and wait for the installation to finish, Odin will show PASS

Now hold down Power button and Volume down for about 10 seconds to force reboot the device

Immediately after the screen goes black release the keys and hold down Volume up and Power button at the same time until you enter TWRP (You may need to release the keys after about 20-30secs due to the "unlocked bootloader" warning)

If you properly followed all the steps you should now see the TWRP menu.

I HIGHLY recommend to flash multidisabler and services disabler right after you enter TWRP to disable forced encryption and stock recovery restoration.

If you're scared of doing something wrong, you can also follow the steps in this video

Donations

DONATE To Me

Sources:

A14 5G [MediaTek]: https://github.com/TARKZiM/twrp_android_device_samsung_a14xm

Kernel: https://github.com/TARKZiM/android_kernel_samsung_mt6833

Credits:

TeamWin

@Could-Chaplain for A22 device tree references.

@physwizz for A14 base device trees.

Everyone else involved
[General Topics] tarkzim:
Screenshots
[General Topics] physwizz:
Great work.

Well done
[General Topics] tarkzim:
New build released - TWRP 3.7.0_12-1

Fixed MicroSD card / OTG.

Fixed Reboot to recovery.

Minor tweaks.
[General Topics] gtlkbx1623:
my model is SM-A145F will it work for me ?
[General Topics] abdullah0012:
thankyou great work again thanks for efforts. also very helpful for my samsung cell phone at tattoo station.
[General Topics] gtlkbx1623:
Thanks for your reply
[General Topics] whiteb0y5o2uk:
Help I flashed mediatek and it failed and now I'm stuck in emergency download mode and when I try and flash odin again it fails saying failed to write? Please help
[General Topics] physwizz:
Flash the ap file with Odin
[General Topics] whiteb0y5o2uk:
have tried but Odin fails and now I have vb error , if anyone can help it would be appreciated model A146u
[General Topics] physwizz:
Unlock Bootloader doesn't work on u models