yashsingh1/xdaforums huggingface dataset:
[Google Pixel Watch 2] 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 Watch 2] GbnrVR:
trying to patch the factory firmware of the LTE Pixel Watch 2 but it keeps failing. help would be appreciated.
[Google Pixel Watch 2] roirraW "edor" ehT:
For anyone else's reference, answered here and in the post below it.
[Google Pixel Watch 2] 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 Watch 2] 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 Watch 2] 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 Watch 2] 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 Watch 2] 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 Watch 2] 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.
[Google Pixel Watch 2] badabing2003:
Update Release:

July 28, 2024 v7.2.0.1 change log:

Set a default PIF format to json to allow displaying the print when Processing Image in PIF Manager.

When PIF Manager is used with an unrooted device or one without granting su permissions to shell, display a message to inform the user about the reduced PIF Manager functionality.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Ozaza:
Hello, good day

- I am using google translate

-Currently my k40 phone is using EU rom version 14.0.8 Can anyone create a backup of the music and video app to help me install via twrp (no root). A while ago, I deleted a junk app and accidentally deleted the vibrate part of the phone (the vibrate mode still works in the second space), so I found a way to fix it. hope the helping
[Google TV General] frmariam:
I've had an Android TV for some years (when my old TV died pretty much all TV in the market were smart and I chose Android expecting the app ecosystem we had on phones) but never really made much use of it until recently. But boy, is it lacking...

I have a MiTV MSSP3 with Android TV 9.

I'm having trouble filling gaps in areas I don't remember being a problem since my Xperia Sola (Android 2) days.

Right now I'm looking for a decent running app switcher.

The "recent apps" screen is not adapted to non touch devices.

Nvidia Shield recent apps screen seems about right - is there any app like this for other TVs that work on Android 9?
[Google TV General] Not_Rich:
Could this be what you are looking for,

[Module][3.3.1] QuickSwitch - Quickstep enabler for supported launchers

QuickSwitch - Quickstep enabler for supported launchers QuickSwitch is a Magisk module which systemlessly allows supported launchers to access the recents (QuickStep) APIs. It's future proof, detects which launchers are capable of being a...

xdaforums.com

I also have a Shield with AOSP Lineage and think the recents works well.
[Google TV General] frmariam:
Thank you for your reply.

Wow. For the kind of feature enhancement wanted, having to flash the device just shows how little we evolved in terms of good practices by HW makers since the days of the WinMo ROM kitchens... With the same kind of issues for less popular devices (like having way fewer or no ROMs at all... no Lineage for my device it seems).

With just a quick search I wasn't able to find my TV firmware in the HW maker website.

And not knowing a trustworthy repo stops me from trying to go further.

Would Magisk also allow me to natively remap remote controller buttons?

Both button mapper and tvquickactions make the remote lag quite often.

This part is also needed for the recents feature to be usable
[Android Head-Units] 120mmAPFSDUPVLADSRS:
Apologies for raising this one again but I too have an issue with the button lights on my A6. I've installed my A6 in a Peugeot 207 (UK model) and I used a Connects2 CTSPG007.2AA Harness (with SWC interface) and the Atoto ISO harness (version B). This harness links the orange illumination cable to the Connects2 orange cable and with headlights off provides a 12v signal to the A6. This allows me to illuminate the buttons in daylight (which helps on dull days) but when I turn on my side/headlights at night strangely the button lights go off (when I'd much prefer them to stay on). This seems to be working in the exact opposite way to what others are saying about these button lights i.e. they are off in the day and come on when the headlights are turned on. The only way (so far) that I can get the lights to stay on during an ignition cycle in the day and stay on when its dark and I turn on the headlights was to isolate the orange illumination cable from the Atoto ISO lead (I've simply pulled out the pin from the ISO socket) and then I selected the lighting option on the Atoto settings menu. If I break the ignition cycle however (e.g. if I turn off the engine or stall it during the journey) when I restart the car the button lights are off once again and I have to do the menu setting once again. What I haven't yet tried is to connect the (isolated) orange illumination cable to a 12v (Acc) feed on the ISO lead (which is what I've seen some users do on youtube when they have this problem). Before I try that (as I can't see it actually working unless I'm being stupid here and missing the simple point that the oranage illumination cable to the HU needs a 12v all the time if want these lights on all the time?? and as I've stated the 12v on the Connects2 harness is cut when the headlights are switched on). Can someone clarify what I need to do to get them to stay on and retain that memory please as I don't want to cause any damage by doing the latter unless I know its perfectly safe to do so? I really hope that all makes sense! Thanks.
[Huawei P40 Pro Questions & Answers] afgzee:
Hi, im looking for ELS-N29 102.0.0.350(C432E3R5P5) firmware.

I will be buying an memory card to update my firmware using dload method as hisuite proxy wont work for me

so if anyone knows where to get this firmware or could upload it for me somewhere i would appreciate that.

Many thanks.
[Huawei P40 Pro Questions & Answers] V0latyle:
All Questions go in the Q&A Section

If you are asking a question, DO NOT post in Development. Rule #15: 15. Keep threads / posts on-topic Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum /...

xdaforums.com

Thread moved.
[Samsung Galaxy Z Flip 5] Taemokokey666:
Hi! Can someone please help me as I am unable to reply on notifications such as facebook messenger or ig in cover screen. It only works fine on whatsapp notification. I tried adding them on App allowed to access on cover screen but facebook messenger is not on the list for me to select.
[Samsung Galaxy Z Flip 5] Jakub.Stefan:
Correct, not everything works easily enough. Forget the "allowed apps", please install the Good Lock app (from Galaxy Store) and go to Multistar / I love galaxy foldable / launcher widget. There you can add any app and swipe over, open the app and use it. Best of luck.
[Samsung Galaxy Z Flip 5] priyan kumar:
It could be a software bug, disabled settings (check notification and app settings), or the app (not designed for cover screen answers). Check app notification settings, update software, and restart your phone.
[Android Software/Hacking General [Developers Only]] kxrma:
Hello, I'm trying to port lk2nd to my Coolpad 3632A but after adding a simple dts and compiling, it goes into a bootloop. How can I fix this?
[Upgrading, Modifying and Unlocking] brdi:
Hello

Im searching for modified roms wm 6 or beter wm 6.1.. For now i am preaty pleased with EV5X 128 Ultimate PXIHH5. But i search for newest and best customized roms.

Tnx and sory for bad englis.
[Introductions] blue Apache:
Hi guys and gals, I'm new to this, so please be gentle as I have no tech knowledge and am hoping the brains trust can help!

I've got a Junsun 9" head unit (I think its an 8788 - I can confirm later) and installed it in my 2010 VW Crafter 12 months ago. All has been well with it until a few weeks ago....and all I can put it down to is, when the battery in the car went flat, and after charging it, the head unit fires up, but freezes on the Android 11 logo and won't go any further. But, and here is the puzzling thing, after probably driving the car for about 20 minutes, bingo, radio comes on, all my settings are there and its once again a fully functioning head unit! What the?

Pressing the reset has done nothing!

Based on this sketchy info, has anyone got any ideas on what to do to fix this?

Cheers
[Introductions] Taemokokey666:
I am a new guy with Samsung Galaxy Z Flip 5. Hoping to learn more about my mobile from this forum.
[Google Pixel 7 Pro] terlynn4:
My phone is rooted and on the October A14 version, so only a couple of weeks behind. I have automatic updates turned off in developer options, and when I do get update notifications I can ignore them. But I've been getting this notification since yesterday, telling me that my phone will be updated tomorrow and a reboot will be forced. I absolutely do NOT want this to happen since I rely on root. I don't have time to install the update manually before tomorrow. Any idea what service I can disable to prevent this from happening?

I already tried disabling Dynamic System Updates, but it's still reminding me it will force the update tomorrow. Can anyone help...??
[Google Pixel 7 Pro] Locoman_:
I took the update, but didn't reboot at the end of installation. Open Magisk app, install to the inactive slot, then rebooted. Your milage may vary, but worked for me, kept root.
[Google Pixel 7 Pro] terlynn4:
Hopefully this works and it doesn't force a reboot before I'm ready. Thanks
[Google Pixel 7 Pro] pxlkeshi:
I have the same issue, can you please elaborate on this <3
[Google Pixel 7 Pro] terlynn4:
I don't know for sure if this will work to prevent the forced update, but I just did the following:

adb shell su -c 'pm disable com.google.android.gms/.update.SystemUpdateService'
adb shell su -c 'pm disable com.google.android.gms/.update.SystemUpdateActivity'
adb shell su -c 'pm disable com.google.android.gms/.update.SystemUpdateGcmTaskService'
adb shell su -c 'pm disable com.google.android.gms/.update.SystemUpdatePersistentListenerService'
adb shell su -c 'pm disable com.google.android.gms/.update.phone.PopupDialog'
adb shell su -c 'pm disable com.google.android.gms/.update.OtaSuggestionActivity'

And then rebooted the phone to make sure those were fully stopped.

In theory, this should disable the activities that perform the update and prevent them from running. 🤞

I suspect I'll have to enable these again in order to update manually when I'm ready.

This info came from this guide:

Android 12: Preventing System Update (and that nagging popup window)
[Google Pixel 7 Pro] pxlkeshi:
My update is scheduled in an hour, thank you for this you're a gem <3
[Google Pixel 7 Pro] terlynn4:
Good luck! I hope it works. Mine is still 6-8 hours away I think, but I'm not getting the notification anymore.
[Google Pixel 7 Pro] Locoman_:
Edit: Sure. My rooted phone took the update over the air. I allowed it to install. The last step, it asks permission to reboot. I ignored that. Open Magisk app. At the top it has "install." Click that, selected to the INACTIVE slot. Magisk ran the script, THEN I rebooted to updated and still rooted. Your milage may vary.
[Google Pixel 7 Pro] bird333:
Thanks for posting this. I have a notification message that says 'system update almost done' which makes me think it has the update stored somewhere on the phone. Will these commands delete that or at least prevent the install on reboot?
[Google Pixel 7 Pro] wgrant:
I could not get it to install to the inactive slot. I've tried twice and I just get an error that my system is corrupt, that I have to resume manually. Thankful after a couple reboots it goes back into the previous slot with everything working and the system pending an update.
[Google Pixel 7 Pro] simplepinoi177:
I was always under the impression that if a Pixel is rooted, it will give a notification, maybe even download, but once it attempts to install, it just wouldn't push through with it and will merely fail -- other than a few rare exceptions that only happened accidentally. So I was never too worried about letting it connect to Google's servers to try to make an OTA happen and/or a notification for it (there were many in the past that found workarounds just for the simple reason of hating the persistent notification; not for fear it might actually update).

But, in any case, it looks like Magisk fixed the Flash to Inactive Slot method that had stopped working for about a year after the Pixel 6 (when Pixel 7 launched; had something to do with changing the root method having to patch the init_boot instead of the boot partition).
[Google Pixel 7 Pro] Locoman_:
It worked for me on my 1+ 7P, so I tried it on this P7P from A13->A14 and also on the update. No issues. I keep everything backed up in case.
[Google Pixel 7 Pro] terlynn4:
My understanding (for what it's worth) is that doing these steps would prevent the install from happening as long as it hasn't already installed to the inactive slot. If it did already install to the inactive slot and it just needs to reboot to that slot now, there probably isn't much you can do except switch the active slot back to the current one after the reboot happens.

This is good to know. I'm not particularly concerned about most updates because they notify me and allow me to install when I want to/have time, or ignore it until then. But this update has different wording and sounds like the reboot will be forced/happen on its own at a specific time, which makes me nervous. I don't like to take the risk of it being forced on me when I'm busy or away from my computer, because I've been soft-bricked or lost root on other devices countless times in the past. I feel much safer disabling system updates entirely and doing it myself every couple of months. Why would Google put a toggle in Developer Options to turn off automatic system updates if they're going to force it anyway?
[Google Pixel 7 Pro] d4m4s74:
Installing to inactive slot corrupted my phone. Ended up using pixel flasher. Luckily that saved it.
[Google Pixel 7 Pro] weriwd:
I've been ignoring this message for the past 14 days.

View attachment 6038646

I noticed that my device is no longer certified, so I cannot make payments with my P8P.

View attachment 6038647

I'm wondering the following. If I'm seeing this message, does it mean that my device is already updated and just needs a reboot to complete the process? Can I postpone this until the December update and flash it directly through Pixel Flasher?
[General Questions and Answers] desoxyn101:
Hi

I am currently having an issue with the Google wallet app which refuses to setup due to my device not meeting the security standards (being rooted). The funny thing is, and according to the YASNAC app I am passing both requirements 1 being saftey Net, and 2 the CTS Profile match check (refer to attached screen shot), but I get the prompt that I have failed meeting the security requirements to use the app.

Is anyone having the same issue, or may know what it could be?

I am using the latest Shamiko 0.7.4 and the safetynet-fix-v2.4.0-MOD_2.0.zip which have worked perfectly until now, and only with the Google Wallet app.

I would appreciate any feedback. Thank you.
[General Questions and Answers] desoxyn101:
Thanks for that, and while I was typing this thread up earlier, I was thinking more or less along those lines, and it does make since due to the modifications I have done to this S20 ultra. At least I have some kind of confirmation that there is no knew obstacle in the way, and confirming that its most likely due to other modifications that have been put in place.

Cheers.
[General Questions and Answers] desoxyn101:
*******UPDATE*******

I took the sound advice given by jwoegerbauer in which I understood from the get go, what the possibilities were in rendering Google Pay/Wallet not to co-exist alongside root, even when clearing SafetyNet,/CTS-Profile Match, and frustratingly after 24 hours or so that has gone by, I still am left with YASNAC.APK giving me the green light, and Google-Pay/Wallet still refusing to co-exist side by side with root/Magisk_Canary (Latest)

This morning I thought to myself lets go back to basics, so I Re-Flashed (STOCK) Firmware on my device >> Odin, and set my device up with the least possible amount of modifying as humanly possible, and would you believe it No Dice.

I still Pass Safety-Net/CTS Profile, But still receive Google Pay/Wallets annoying Security requirements disclaimer. (Refer to 1st pair of Screenshots)

After trying to fiddle around with it for 10 - 15 minutes, I tried a Firmware-Matched TWRP backup >> Restore >> Re-Boot System, and still nothing, and where it worked not over 1 week ago, it does not now.

I tried SafetyNet Checker by flinkapps via Playstore, still Pass, and still No Dice.

All other apps that require SafetyNet/CTS-PROFILE Pass, DO work, and it is becoming more apparent that this is because of some unannounced news/on-goings at Google.

So please let me know if anyone at any stage comes across anything or has any real constructive input to tackle this problem, it would be greatly appreciated.

List of things done to Samsung 20 ULTRA SM-G988B/EXYNOS... I only reboot every time so I left 0 to chance.

Flashed STOCK Firmware with STOCK kernel.

Rooted via Magisk_Canary.apk 26.4

Reboot

Made sure that the Update Channel is Canary.

Flashed Busybox for Android NDK Module

reboot

Flashed Latest Shamiko LSPosed Module v0.7.3

reboot

Flashed Universal SafteyNet Fix v2.4.0-MOD_2.0 by kdragon

reboot

Flashed Latest Zygisk- LSPosed module

reboot

Ticked ALL Google APKs, even Playstore Due to Modded Playstore Installed Via LuckyPatcher

Thats all.

Please let me know how all goes.

​

​

​
[Google Pixel 8 Pro] whatsisnametake2:
I got this msg today. I have auto update turned off in developers settings.

what gives? is the device going to force an update anyway?View attachment 6034583
[Google Pixel 8 Pro] yanggame:
You can try to remove OTA app and GMS System Update Activity from adb shell

adb shell pm uninstall -k --user 0 com.google.android.factoryota

adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateActivity

Restore

adb shell cmd package install-existing com.google.android.factoryota

adb shell su -c pm enable com.google.android.gms/.update.SystemUpdateActivity

2nd command for GMS may need root cause without su -c I got an error.
[Google Pixel 8 Pro] E-61:
So did the phone automatically restart? Any news?
[Google Pixel 8 Pro] whatsisnametake2:
update - it didn't force a restart upgrade. so far anyway! I keep getting the update reminder tho which is annoying. how's everyone getting on with november update anyway?
[Google Pixel 8 Pro] LLStarks:
I don't understand the logic in refusing updates. If there are issues, we would have made it clear weeks ago.
[Google Pixel 8 Pro] HipKat:
I don’t think anybody had any issues with the November updates
[Google Pixel 8 Pro] whatsisnametake2:
the reason for being cautious about updates is they can go wrong. not just phone firmware, but anything. happens all the time. so my view is I only need to update (anything) if I have a problem of some description. if the device/software is working exactly as I need it to, no need to update. p8p release firmware has been absolutley fine for me. zero issues.
[Google Pixel 8 Pro] LLStarks:
Your device is not working properly if it's vulnerable to exploits in the wild.

If you accept that risk, so be it.