yashsingh1/xdaforums huggingface dataset:
[Magisk] badabing2003:
Third bullet item should be relevant for this thread. :)

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.
[Magisk] D€INOS:
Extracting prints from erofs .img images inside OnePlus payload.bin made easy, hopefully, tough wood.
[Magisk] hsmith1514:
simple commandline tool i use for erofs images

https://xdaforums.com/t/tool-win-erofs-utils-for-cygwin64.4565233/
[Magisk] D€INOS:
images with payload.bin, in general I guess, not when payload containing img in erofs format? I noted output "Image format not supported" when processing image.
[Magisk] badabing2003:
link to an example such image?

For example this One Plus image was processed and print extracted without issues.
[Magisk] changhuapeng:
IIRC, he mentioned switching to the embedded list because fetching the revocation list at runtime is causing issues or errors.
[Magisk] badabing2003:
Yeah, but it's better to fix the bug then have to release a new update each time Google updates the CRL, besides between updates users could potentially think that their certificate is valid while it's already on the CRL.
[Magisk] massima:
I cannot remove this post but installing from the Playstore (instead offline) all my apps now work😆

😆😆!!!

!hanks everybody for your efforts
[Magisk] D€INOS:
Propably < A12

Oneplus ota

My rule of thumb is that A12-14 1+ builds are erofs.
[Magisk] Vision:
I don't notice any issues or errors in my device 😕

Yeah, and when Google add more in black list, must again updated the app.

he won't have time to updated.
[Magisk] chiteroman:
I reimplemented it: https://github.com/chiteroman/KeyAt...14dc6340e58aeb8e54aca1ea6e66d1686f685a6262R54

If you don't have Internet connection it will use embedded one.
[Magisk] Aarif goku:
The image processor is asking for a zip file, so I couldn't directly use the `system.img` file. I zipped it, but it still doesn't work and gives out a "cannot process" error. It looks like it needs full OTA zip files and not `.img`.

I use this payload dumper to dump `system.img` files, which are like 800MB to 1GB, instead of downloading whole 6GB OTA files. Sometimes they are EROFS files, so I use this tool to unpack them.

I also came across a Python extractor.

The first main thing I would like is if you can add support to directly extract from `system.img` files. Secondly, I think you could probably add something like the online `payload_dumper` to extract `build.prop` directly from the network (not sure if possible), or maybe use similar method to URL dump the `system.img` and `vendor.img` files directly and extract `prop` from them, so `.img` support won't be necessary if that's possible.
[Magisk] badabing2003:
That's correct, as stated in release notes, only Pixel factory images, Pixel Full OTA images, Samsung factory Images and images with payload.bin are currently supported.

You might think that you're not downloading the whole file, but the tool you linked to is downloading it to be able to extract the required partitions from it.

You are better off downloading it and feeding to PF.

Current version does not support EROFS, I might add it in the future, I prefer not to rely on extrernal tools and bundle those, which would increase the size of PF, and potentially cause increased false positive AV alerts, not to mention each and every platform that PF support, the respective binaries need to be included.

I'll take a look to see if this works and if it could be integrated (no promises)

Although that is trivial, but that is not enough, most often you also need vendor.img and even at times product.img.

Nope, even if URL based extraction is supported, the file needs to be downloaded first and only then extraction is possible. At the end it doesn't make a difference to your system, you end up downloading a large file, and in the future if you want to process again, it's yet another full download.

JUst download it yourself and feed it to PF.
[Magisk] Vision:
Nice.

Work perfect.

Nice feature the Secret Mode.
[Magisk] Aarif goku:
I have checked data and it didn't consume much as well and was quicker than downloading full file. I always use it to download boot.img and it hardly takes a minute. Other than network It wouldn't make sense for it to work with 4gb space left on my pc for this OnePlus12beta file.

Yeah I loosely said system.img but I means any .img file basically.

I thought img was supported but thanks for pointing out. Will be waiting for Wider support. Thanks for your Amazing tool 🔥.
[Magisk] Vision:
@chiteroman

Because you get the key attestation demo and modify, but the other is the original the Google Play recognize it and say to update to original version.

I accidentally went to upgrade it because I didn't see it in the list and I clicked update all 😂🤣
[Magisk] majorfigjam:
More older betas (14qpr)have been banned!
[Magisk] intel_core_i7:
I think it's supposed to fail updating because the apps use different signatures, no?
[Magisk] Vision:
Oh yeah right.

I try to update and say can't.

Just only show it.

The GitHub the original version not show it on Google Play.
[Magisk] maxim.a.petrov:
Hello, I have a MI 8 lite device, it does not pass Device with Play Integrity Fix module, only Basic. I have Magisk kitsune, latest version, no modules. Zygisk is enabled. The only problem is that it does not pass these two checks on Android 9. Starting with Android 10 and above, everything passes successfully. I have tried off. builds and not off, signed with non-test signature, no luck. How do I get them on the A9?
[Magisk] majorfigjam:
Have you tried Osm0sis scripts only mode, which is desgned for devices <A10.

Follow the link from Page 1 Post 1 to FAQ, then to Osm0sis resources and look for Scripts Only.
[Magisk] majorfigjam:
Find a leaked keybox, and follow the Chiteroman detailed instructions to spoof Strong Integrity?

Or persuade Niantic not to enforce Strong Integrity.

Good luck with either option.
[Magisk] pndwal:
Scripts Only mode (only) can't work for Mi 8 lite; it launched with A8.1... (Unless Xiaomi happened to break TEE on that.) 😉 PW
[Magisk] pndwal:
Is there a reason for 9 when 11 is available? 🤔 PW
[Magisk] djo_5296:
Is playcurl still unnecessary? it had an update June 27.

or a better question, how do i know if i need it, should it have another update? im on rooted stock pixel 6 pro if it mattered
[Magisk] intel_core_i7:
Or just stop using whatever is requiring it.

Though it will be another story if we're legally required to use services requiring strong (full digital ID enforcement doesn't seem so far fetched) then the best way is probably to get a secondary phone for that.
[Magisk] badabing2003:
I'll add support for img processing, but I don't think it will be very useful, this is trivial to add as all the logic already exists.

Besides you don't process them individually to create a print, you process them collectively to take the relevant (higher precedence) props from the respective images.

That is why it's best to feed a complete image and let the application extract what it is relevant and pick up the right props.
[Magisk] linuxares:
@badabing2003 Not sure if this have anything to do with Pixelflash.

I did a stupid thing just to test.

I took the Xiaomi print that my phone run right now, copy pasted it from the "active" window and put it in "output", just straight up copy and paste.

Then used the "smart" feature to import it, then the print fails on device but basic works. I'm just curious why it would fail then? is it because it gets imported wrong? Because I have a sneaky suspicion that files I've might have tried had working fingerprints but might not have worked because of me using Pixelflasher incorrect.
[Magisk] badabing2003:
Usually I would ask for support file to tell you what might have gone wrong.

As I care a lot about people's right to privacy, that is why the support files are redacted and encrypted.

In addition to that, anything related to PIF prints or keyboxes are not logged at all.

(I want people to be able to use the program without fearing that they might be leaking their private print / keybox)

So asking for the support file won't help in this case.

Considering that you're working with a public print (so nothing to hide), a video recording of your steps would show me what might be going on.

PIF Manager window is all that I need.

Start with your working print that passes the device

Run the test in PIF manager to show that it is passing,

and then do the steps you did to make it only pass basic

Attach a support file (in case there were any exception during execution)
[Magisk] linuxares:
I will try to record it later today! My phone is busy with a little script at the moment from zgfg ;)
[Magisk] linuxares:
For some reason I cannot recreate the error now? I guess it was a case of PEBKAC

EDIT: Yay found a working print that isnt Xiaomi. 7.0 version @badabing2003 is so good <3
[Magisk] badabing2003:
That's known to happen to me :)

Or perhaps the script you're running has put some stuff in a weird state.
[Magisk] linuxares:
Who knows? I also doing this on a Windows 11 PC and not a Linux, might be the issue? (Totally not bias towards Linux at aaaaaalll ;))
[Magisk] flyoffacliff:
Thanks, didn't know we had a dedicated thread for that.
[Magisk] AlexS2412:
so on magisk for me, google messages will no longer send rcs if i clear the app data. nothing will bring it back unless i switch to apatch and clear the appdata with my private google husky print. i have no explaination for this and am getting tired of fighting with google to keep this service working.

To be specific i am using latest magisk alpha + shamiko, and nothing is on the deny list. if gapps are added to the denylist even with shamiko this breaks rcs.
[Magisk] choantet:
Just want to again express thankfulness for the great tools, guides and understanding that have come out of all of this. Particular grateful for @osm0sis and @badabing2003, and so many others willing to freely give of their time, experience and knowledge. The creativity and determination displayed here is inspiring. While I missed RCS for a bit, everything has worked the rest of the time, and is still working, for now. The challenge has been healthy for this elderly brain...actually fun.

And yes, sometimes it's wiser, easier and cheaper to simply pay the taxman what he demands, and sometimes it's worthwhile to push back as best as we can. Cheers...
[Magisk] lpedia:
Couldn't agree more. RCS communication in Android should be available without Google Messages or gapps, too. Third party messaging apps should be able to use RCS and be compatible with Google and Apple RCS without being tied to either one's proprietary implementation.

The IETF Messaging Layer Security e2ee protocol was released in July last year, and Google said at the time that it intended to adopt MLS for Messages. Apparently there's now evidence that they're starting to do that.

Google Messages is preparing to implement its new messaging protocol

Google Messages spotted having Messaging Layer Security (MLS) under development

www.androidpolice.com

Might this be a light at the end of the RCS tunnel that's not just another approaching train? Could we actually soon have RCS able to function on custom ROMs via third-party messaging apps and without root and FP fudging?
[Magisk] trevtdogg:
doesn't RCS only need basic integrity?

I don't use RCS but that is just what I've absorbed from discussions and results posted so far.

also there is likely a lot of people using autopif, xiaomi eu custom rom team pif, etc. that don't often post in this thread but still are doing the play integrity fix in some way.

so it's most likely way more than just a dozen in total people, I'd guess still somewhere in the thousands.
[Magisk] Aregtheeditor:
I am here... For now
[Magisk] majorfigjam:
No, it needs Device Integrity to wotk properly.

When the 14 QPR betas were banned over the weekend, RCS stopped working for devices with those prints.
[Magisk] sawdoctor:
Still working for some
[Magisk] pershoot:
As of current (which may be subject to change as we go along), on a Pixel device, only BASIC is required for RCS functionality if using the stock device's print with an unlocked BL; Wallet / contactless will be broken and requires DEVICE. Said print in use needs to not be banned for RCS purposes (i.e. no public / mass-used / old beta prints, etc., as of current). On a non-Pixel device, I'm uncertain as the prints used would be different; others with a non-vanilla device can chime in. We have a member (@aliantonio) with a recent Pixel device operating currently in this very fashion (BASIC only using the stock device's print with an unlocked BL; RCS works using the non spoofed device's print).
[Magisk] manjaroid:
14 beta had pretty good mileage it seems. I'm surprised to learn this.
[Magisk] TurboLed:
I'm on a Pixel 6 pro, stock A14. If I turn off the PIF module, I only pass BASIC but RCS stops working. So passing BASIC doesn't seem to be enough... Should I uninstall Magisk as well? But then there's no point in having an unlocked BL.
[Magisk] pershoot:
Check your modules. If you are using LSPosed, for example, disable it.
[Magisk] cabagekiller:
I have RCS working on my OP12 with Lsposed and many modules active even if I turn pif off and lose device integrity. I also am using apatch and it seems to have much better success with RCS than magisk.
[Magisk] pershoot:
Yea, I also found APatch works better with lesser detection(s), throughout.
[Magisk] trevtdogg:
does this mean you drop back to basic integrity with RCS working, or no integrity with RCS working?
[Magisk] cabagekiller:
I drop to basic integrity but RCS works for me
[Magisk] CSX321:
I'm seeing the same thing on my P6. Stock A14, Magisk 27000, no other modules except the built-in Systemless Hosts. No RCS if I disable, or even completely remove, PIF. Even reading most of the messages here, I'm unclear on what is meant by using the stock device's print. Does that mean just disabling PIF, or does it mean generating a pif.json from the stock image to use with PIF?
[Magisk] pershoot:
It means not spoofing your device's print to DG / GMS, to masquerade as something else. This is done by disabling / not using PIF for its intended purpose, which facilitates that.
[Magisk] CSX321:
Hmm. Without PIF I don't even have Basic. What am I forgetting to do or to clear? Is gms supposed to be in the deny list without PIF? I have a pretty bare bones normal Pixel 6 here, so why don't I have Basic now?
[Magisk] pershoot:
Disable all modules, reboot, then check integrity via Play Store (Developer) and observe.
[Magisk] CSX321:
Yes I just did that and get [] -- not even Basic. With PIF installed and using the default sf print I get Basic and Device.
[Magisk] pershoot:
That's an odd one; you should get BASIC. Are you up to date on your particular privilege escalation method (magisk, etc.)?
[Magisk] DIXES:
I tested it on my old phone, asus zenfone 3 Android 8.0 (stock rom) and it worked too, but now it doesn't, became only basic passed again.
[Magisk] CSX321:
Up to date in Magisk stable channel. Eh, for now I just reenabled PIF, and I'm back to Basic and Device.
[Magisk] borisSweden:
Theory, can a personal print be used at the same time if you keep the older unmodified phone at home but the main modified phones is what you use? It's like what people used for iMessage, a proxy device that is active for controls.
[Magisk] pershoot:
They would be seperate entities with only the masquerading bit being similar in-situation. It wouldn't work as you are intending / wanting it to, IMO.
[Magisk] borisSweden:
Even if there where 2 identical models? Now it would be a expensive fix for RCS and Wallet so it would be the long way.
[Magisk] GeTex:
Device is not required for RCS
[Magisk] pershoot:
Yea; the better option would be to leave BL locked / device un-rooted for full functionality (rcs, wallet / contactless, ... (TBD)).
[Magisk] Aregtheeditor:
DId the new announcement on PIF telegram take effect or is it false? Bc I still have RCS...
[Magisk] pershoot:
That is not referencing anything current to date; this is for previous builds (I myself have not tested; just what has been reported).
[Magisk] 02Victor:
The latest beta rom print from husky displays no integrity [] what's so ever however no pif module the rom does achive basic integrity
[Magisk] cabagekiller:
Mine is still working fine. What root method are you using? I wonder if thst has any effect on it.
[Magisk] binary**#:
So where exactly should we execute the following commands

unzip -l /system/etc/security/otacerts.zip

and

uname -r

While I could take a different route and access the otacerts.zip and extract it via File Manager to get the releasekey.x509.pem and open it via Text Editor to get the Certificate data, however, how could I then verify if it has "testkey" or not?

Apologies if this has already been answered before and any help in this regard will be highly appreciated.
[Magisk] majorfigjam:
In a terminal emulator on your phone.

You will see something like /releasekey.x509.pem

If you see /testkey.x509.pem, then you have a test key
[Magisk] TotallyAnxious:
I have both with that print.
[Magisk] dilligaf56:
@flyoffacliff: I don't post a lot but am following this and other threads associated with rooting the Pixel phones and PIF closely. I've been rooted since the original OG Droid and am currently on a Pixel 6 Pro. I really am very happy with having a rooted phone and *really* don't want to give it up. What Google is doing, IMHO, beyond being a huge PITA, is most likely unnecessary, unless someone can show me reliable evidence that someone's rooted phone caused someone to illegitimately lose money. Currently Wallet is working on my phone (thanks @chiteroman, @osm0sis and also kudos to @badabing2003 for PF) but not RCS. Given a choice, I'd rather have the former. I *very* much appreciate all of the hard work the devs have put into keeping us going. Thanks again!
[Magisk] majorfigjam:
So Chiteroman has adopted Husky Beta 3 in (test version) 16.6 on TG, for RCS compatibility, I imagine.

Hope it lasts!
[Magisk] binary**#:
This is what I was looking for, thanks mate.
[Magisk] Vision:
For the users, with still in v16.3 and ask why key attestation show BL is unlocked.

I had write a simple answer.

(The PIF module can't hook into like the frameworkpatch method, for that the key attestation show the same as before install the PIF).

For spoof a locked BL, users can use this: https://github.com/aviraxp/Zygisk-KeystoreInjection and if have and keybox (you can use the sw for just test, add a keybox.xml in /data/adb), after show you BL is locked.
[Magisk] pershoot:
Good bye print; thank you for your service! ;)
[Magisk] Aregtheeditor:
I still have the thing tho in g messages...
[Magisk] pershoot:
I meant after this is potentially released where it will be just like a public / mass used one in that scenario, if this is the one being used to facilitate.
[Magisk] immortalwon:
Can we please stop relying on chit to provide prints to the public? We will have nothing left at this rate.
[Magisk] Aregtheeditor:
I agree
[Magisk] Aregtheeditor:
Tho his module is pretty good but pifork better
[Magisk] DuskGolem:
We will run out of prints eventually, doesn't matter if chit (appreciate it mate) provides them or not.

I hope someone finds an alternate solution one that doesn't involve relying on device fingerprints / key boxes. Google is not slowing down and eventually this will be the only way going forward, if it is even possible that is. There is apparently no light at the end of this tunnel 😩.

Seems like a one way slaughter at this point than a cat and mouse chase.
[Magisk] Aregtheeditor:
B but I planned to use my rooted device for another 2 and a half or 3 years. Will it last?
[Magisk] DuskGolem:
I think you know the answer to that :ROFLMAO:. A middle finger from GOOGLE.
[Magisk] DuskGolem:
You can use your rooted device and buy a new one for banking apps, wallets, google message RCS, etc. That will be a win-win situation from google's point of view.
[Magisk] Aregtheeditor:
:< ig I have to waste more money now...
[Magisk] osm0sis:
Speaking of which... users on PixelOS shouldn't use PIF v16.6-beta or they'll bootloop because chiteroman took my list but isn't handling overlays correctly:

PlayIntegrityFix/module/customize.sh at main · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com

He's also back to supporting props in the json again, but at least he provided (some) credit this time:

v16.6-beta · chiteroman/PlayIntegrityFix@a5b2422

- Import few code from osm0sis fork - Add support for parsing system props in json - Use service.sh of Shamiko - Update fingerprint to fix RCS - Other improvements

github.com

🤷‍♂️

Edit: And these 2 lines of the latest Shamiko script are actually wrong because those props have never existed on any device: https://github.com/chiteroman/PlayIntegrityFix/blob/main/module/service.sh#L46-L47

I vet every change I make to my scripts. Here's the correct list: https://github.com/osm0sis/PlayIntegrityFork/blob/main/module/service.sh#L7-L9

Edit 2: Lastly, removing the post-fs-data props again like he just did will cause big regressions again for some ROMs. He last did this in February for v15.7 and had to undo it a day later for v15.7.2. Then the last time before that was in November when he kept going back and forth on removing system.prop and putting them all in service.sh and I had to fix it with my last PR before I decided to fork and do things methodically and stable. 🤦‍♂️

😶‍🌫️
[Magisk] Aregtheeditor:
Guys how much will we able to get working fingerprints for rcs and device? 1 year? Or maybe 4?
[Magisk] sawdoctor:
Problem is there are so few left and so hard to find what's the alternative? I've been using this print for quite a while now and gutted it's been shared publicly but if/when it gets burnt I've no more left and I can assure I've looked. I was even given a few really helpful hints from @osm0sis but they've all been burnt now
[Magisk] Aregtheeditor:
Give up ig 😭 😭 😭
[Magisk] Aregtheeditor:
And I rooted my samsung this February. I will probably never root a phone again unless google changes something with Play Integrity
[Magisk] osm0sis:
Just keep switching to the newest Android beta Pixel print for now 🤫

😶‍🌫️
[Magisk] SoulsAssassins:
I mean this story has been going on since November even before that, and the number of times on these 900 pages that people want ready-made solutions and everyone repeats "read the faq" "read first page etc" at some point there is a responsibility that is public but in short I repeat what has already been said.
[Magisk] dknight178:
Considering the end game is for google to eventually ban all fps one way or another, really hope someone can find a way to relock bootloader without a device wipe (or at least backup files and app data without root required)
[Magisk] bluerar:
ROM you are using (and kernel if using custom kernel): not sure how to check

Here is an image: View attachment 6121826

Version of Magisk you are using: 27

Other modules you have installed:

Adb root

Always trust user certificates

Magisk built in busy box

MagiskHide

Patches to android(lucky patcher)

Play intergirty fix

Screencam systemizer

Shamiko

Systemleas host

Zygisk ssl unpinning

A Refer from this help thread Link led me here
[Magisk] kholdstayr:
Don't talk about it!!!!!!

(Partially serious)
[Magisk] Nergal di Cuthah:
Get rid of lp (#5) as it's basically warez and can be a cause of failure to achieving integrity