yashsingh1/xdaforums huggingface dataset:
[Magisk] Peter12205:
Mod edit - translated by https://translate.google.com/. Oswald Boelcke, Senior Moderator.

good evening dear developer @osm0sis , you created this kernel, I just saw your name when installing it through twrp, if so I want to say thank you very much, since it works on android 14 even though the kernel was created 1 year ago :)

I found the kernel in the fbs developers telegram group in case you're curious where I got it from.

*********************

buenas noches querido desarrollador @osm0sis , usted creó este kernel, acabo de ver su nombre al instalarlo a través de twrp, si es así quiero decirle muchas gracias, ya que funciona en android 14 incluso aunque el kernel fue creado hace 1 año:)

Encontré el kernel en el grupo de telegramas de desarrolladores de fbs en caso de que tengas curiosidad por saber de dónde lo saqué.

https://drive.google.com/drive/folders/19uT7QII-fUo9z-M3XjRq7um8D85U4voC

https://xdaforums.com/t/tuned-kerne...ging-no-flickering-correct-ma-values.3893954/
[Magisk] osm0sis:
I have never made a kernel, please read again. Also not sure why you're telling me any of this or the relevance to this thread. 🤔
[Magisk] CityKev:
I follow this thread out of interest currently and I've noticed that there are less and less posters asking for help / advice and increasingly it's more developers / highly technical posters offering opinions and comment. My feeling is that a lot of less knowledgeable people have given up trying to keep up with the new methods needed after each Google change in requirements and it's now becoming a binary choice of staying on stock with locked bootloader for all Google applications or accepting that you probably won't have some of them if you do unlock the bootloader and customise.

I have two tablets with two different custom ROMs and one passes device integrity without me doing anything and the other doesn't. It doesn't matter to me either way. My phone is my primary device and I've kept the bootloader locked and stayed on stock.

This is just an opinion but I'd be interested if others agree with this.
[Magisk] 4sz0m:
Or, it's possible that this PI topic matured enough over time so that less technical people can also successfully achieve the workaround.

This is also just an opinion as I don't believe we have any meaningful data to prove either assumption.
[Magisk] CityKev:
That's also something I considered but it's less likely I'd say.

Opinions eh :)
[Magisk] jrotaetxe:
The ability of people to learn vs the confirmation we are lazy animals...

C'mon. Is basically extract info from a text file and put it in a correct form using a template... You do not need to enter in the details of howtos. Very nice people have done that for us and the only effort they ask is to finish the job ourselves for the sake of the community. No need to be an Android Goddess to finish...
[Magisk] CityKev:
I'm absolutely not criticising the huge amount of work that has been done by lots of people. It's more that I feel that Google will be happy that they are reducing the pool of others that will want to customise their devices. There is no doubt that firstly it has become more difficult and secondly there is no guarantee that any fix will last.
[Magisk] osm0sis:
This.

I've put a ton of effort into documenting basically everything for people in the last few weeks, so I'd like to think that hopefully has been helping. 🙂

Numbers seem about the same, if not more, honestly!

I've got significantly growing numbers on my fork and chit's user base somehow also remains massive as always. 💪

Etc/PIF.md at main · zgfg/Etc

Et cetera. Contribute to zgfg/Etc development by creating an account on GitHub.

github.com
[Magisk] frasca61:
I am still using my first fingerprint since the beginning of December. Thanks to all of you who have worked a lot. :)
[Magisk] ablak44:
I agree with the opinions in previous posts. Keeping your unlocked smartphone in optimal condition to run all your apps is becoming more and more difficult. I remember what rooting was like 10 years ago. It was ridiculous compared to what it is now. Personally, I'm still having trouble keeping Google Payments working. One day it works, the next day it doesn't work. I also don't understand what to do with the FP downloader application. I run it, a notification pops up and that's it. I currently have the following modules installed; Play integrity fix 15.8. playcurl. V6. profit lsposed. shamiko. Today I get a message again that the device does not meet security requirements. The Play Store is certified.
[Magisk] Spartacus500:
Same thing for me today, Meets integrity devices pass and the Play store has a certificate 😳
[Magisk] 4sz0m:
I don't necessarily agree that rooting was so much easier back then. It was certainly different. But I'd argue that if you are able to follow instructions, research the Internet and comprehend well your learnings, nowadays at least you have a better chance of not f-ing up (like bricking your device).

Re your issue with payments not working again. Based on some recent comments, it's possible the shared print of 15.8 has been b-d. I have to assume, because it's not clear if you're using your own print or not. And I'm using my own print.
[Magisk] CZ.Kostra:
I just tested the FP from Xiaomi.eu which is included in PIFix 15.8 and it still works.
[Magisk] 4sz0m:
Ok, so that assumption is obsolete then, thanks for the effort!
[Magisk] CZ.Kostra:
I restarted my phone and Xiaomi.eu FP is not working. My fingerprint doesn't work either. It looks like the next wave of fingerprint bans. 🤔
[Magisk] 4sz0m:
My FP also just died. RIP.
[Magisk] Spartacus500:
Now 🤷 15.8
[Magisk] HippoMan:
Same here with my FP that had been working for several weeks.

And some other FP's of mine that I had downloaded and which were previously working to give DEVICE integrity are also no longer doing so. Only BASIC integrity now with all of those I've tested so far.

The Googlefrinchian Telephone Sanitizers are continuing to do their jobs, apparently. Even if only one of them follows this thread, that should give them enough information to be able to "improve" (ha ha!) the usability of Android for modders.
[Magisk] CZ.Kostra:
I checked my collection of FPs and none are working.
[Magisk] aerotox:
G Wallet and google play tells me device is certified and everything OK. But SPIC is now failing device. Been on same PIF (developer v2 version) with custom FP since december

Edit: Happened today
[Magisk] osm0sis:
Yep, something new is up. Mine from November was working an hour ago and now also fails DEVICE.
[Magisk] 4sz0m:
I confirm ALL my prints mined in December are failing. This is after last round of "raising the floor" only killed 3/10. Now 10/10 dead. @osm0sis this time it feels more like "removing the floor to stand on"...
[Magisk] 4sz0m:
Exactly, this is a serious round.
[Magisk] HippoMan:
Does this mean that you can actually still make payments with G Wallet, even though your phone's integrity is only at BASIC level?
[Magisk] 4sz0m:
It's just a matter of time to start failing.
[Magisk] aerotox:
So far yes, let's see how long it lasts
[Magisk] CityKev:
What is being reported now was what I was getting at in my post earlier. Trying to keep device integrity is a constant battle as Google keep moving the goalposts. Many people will have given up unfortunately.
[Magisk] TheEnekaign:
Also something I found (and it may have already been mentioned here, so apologies if so), but RCS stops working (at least in Google Messages) if your phone isn't passing Device. Found that out yesterday from a reddit thread when I was trying to figure out why I couldn't send any RCS messages even tho the app said I was connected.

Also both my keys I pulled from stock firmware images of both my old LG phones died as well....
[Magisk] AstronxD:
Do I need to get a fingerprint if I am using stock ROM with unlocked bootloader?
[Magisk] 4sz0m:
We shall see how this ends up. You're right about this cat and mouse game deterring some people. For me rooting is still worth it, even without PIF. For now.
[Magisk] CZ.Kostra:
It's perfectly timed. 😁
[Magisk] AiM2LeaRn:
guess im here for the same reason everyone else is here... latest google update killed the fix.

now passes MEETS_BASIC_SECURITY

but fails MEETS_DEVICE_SECURITY

:-(
[Magisk] Flr Power:
Same for me, no FP working at the moment 😕
[Magisk] HippoMan:
I believe that by all of our public discussion and public posting of fixes, we have helped the Googlefrinchian Telephone Sanitizers to more quickly come up with ways to thwart our efforts.

Luckily for me, my wallet still works flawlessly when my phone only has BASIC integrity, and even when it has no integrity.
[Magisk] CZ.Kostra:
As @osm0sis said. There is something new in the game.
[Magisk] 4sz0m:
So perfectly, I'm getting a bit suspicious ;)
[Magisk] :
Confirmed. Lost DEVICE attestation on all devices. I couldn't find a working one with pickaprint.sh within about 50 tries.
[Magisk] HippoMan:
The Googlefrinchians could also just as easily run pickaprint.sh and then simply banana all of the FP's that it returns. Perhaps something like this is what has occurred.
[Magisk] 4sz0m:
You must've been waiting for a while to repost this :ROFLMAO: Let's not give up so easily! :alien:
[Magisk] :
They could have done that much earlier.
[Magisk] 4sz0m:
While we're facing something new here, I'm not sure that's how it's supposed to work. And if it's not a new approach, they possibly "raised the floor" fully on all old devices.
[Magisk] :
Looks like the integrity of your wallet is also slowly fading... 😉
[Magisk] AstronxD:
Do device need to spoof fingerprint if they are on stock ROM with unlocked bootloader?
[Magisk] FrogMaster-:
I can also confirm that all my FPs are currently dead my originally manually mined FP died yesterday, today all of the FPs i had are now burned.
[Magisk] 4sz0m:
Yes, if you want to pass 2/3 PI.
[Magisk] 4sz0m:
IF the FPs are actually "burned". I wouldn't be surprised they're doing something different this time.
[Magisk] zgfg:
It will work, powered by cache, but no longer than up to 24 hrs
[Magisk] immortalwon:
I don't think they blacklisted every print, they changed something with droidguard
[Magisk] CityKev:
Google made me an offer I just couldn't refuse....
[Magisk] HippoMan:
I haven't given up on the cat-and-mouse game. It's just that I never wanted to rely on my phone for any kind of payments, ever since I first started using Android ages ago.

As for the cat-and-mouse game, even though I haven't given up yet, I think that we will inevitably lose that war as more and more app developers get on the bandwagon for requiring DEVICE integrity ... and as more of them even start requiring STRONG integrity.
[Magisk] FrogMaster-:
Agreed, it seemed all to fast for them to stop working back to back the way they did.

I need device to access some work apps, so this has been pretty inconvenient to say the least.
[Magisk] 4sz0m:
I'm with you. My concerns starts at the level of banking and other payment related apps, that require a very inconvenient workaround. Google Wallet isn't a necessity today.
[Magisk] zgfg:
I was afraid for some time seeing that they slowed down by burnung prints

As commented earlier, I had over two hundred working prints, and I expected there must have been few times more, hence burning one by one was pointless. On the ither side there are many other info thaey could use (and maybe they do now) to find that we're using fake prints or directly finding the modified device

Or there are just some temporary operating issues on their side
[Magisk] 4sz0m:
Could they just disallow device integrity for any bootloader unlocked device, FP valid or not?
[Magisk] HippoMan:
I think you mean "boot-UN-locked", correct?
[Magisk] 4sz0m:
Yep, corrected thanks.
[Magisk] kornball:
FP i had which worked for quite some time no longer functions. I could tell something was wrong because RCS was broken on my phone. I checked Integrity Tester, and it no longer meets Device.
[Magisk] AstronxD:
Anyone has working FP? Not asking you to share but just wanted to know, if its working for some?
[Magisk] V0latyle:
Same
[Magisk] zgfg:
You could try hiding by Bootloader Spoofer (I'm on the game now and I can still buy beer) but not sure if is it possible to apply to the System Process gms
[Magisk] FrogMaster-:
Is that same print still functional even now? I'm not looking forward to hunting down yet another print but I will if there are still valid prints to find.

Edit:

Disregard I see you mentioned your print is also failing device integrity.
[Magisk] chiteroman:
Seems like Google did something...

If they fixed the exception "bug", maybe I can do smth 🤔
[Magisk] g33gz:
I have a buddy who is running an unmodified pixel 7 and he's also failing failing the integrity checks...

EDIT: Looks like he's running stock android 14 on there
[Magisk] :
Yep, my fp seems to have been burned too. My device only has basic integrity now. I used the wallet Tuesday and I can open it still and view my cards. What notification do I get when Wallet too fails?

Tbh, I've waiting for this day (not eagerly, I hasten to add) as a kind of crunch decision time; either return my phone to stock and lock it OR forego wallet and go back to using cards (1st world problem or what eh?) I'm tired of the cat and mouse game now.
[Magisk] Flr Power:
Really 😲 If it is then the ban would be temporary 🥳
[Magisk] Samg381:
This is breaking RCS for me too. That is absolutely insane.
[Magisk] majorfigjam:
It would be too much to hope that this was a 29 February bug.
[Magisk] Vision:
Me to i don't want payments and bank in my phone, i need this for apps

Like @HippoMan say more and more app developers get on the bandwagon for requiring DEVICE integrity ... and as more of them even start requiring STRONG integrity.

That i'm afraid is, if Google can add in DroidGuard to send the info in all other apps, and our phone detect as the spoof FP we have with PIF and this break all the feature for the app take the info like Google Play etc. regardless of whether it will Pass 2/3
[Magisk] vldrs:
I wouldn't count on what is now just a bug... I specifically checked on two unmodified devices right now, Pixel 4a - passes everything; and Mi A1 - passes basic and device.
[Magisk] BrimoFan123:
I don't think so it is...

Since beginning of December 2023 I used FP which I took from my old phone that I upgraded from Android 9 to Android 10.

FP from Android 9 was not working, the one from Android 10 does.

It means this FP from Android 10 was not available to be found in stock firmware databases.

Now this FP doesn't work like for other people with their FPs.

It's time to uninstall Wallet and Play Integrity Fix magisk's module and start counting days when we will be kicked off from using bank applications... G-bastards!
[Magisk] Claus….:
I really hope! :) please keep us posted
[Magisk] V0latyle:
Unmodified meaning...? If his bootloader is unlocked, he's going to fail everything, regardless of stock or custom ROM. Only locked bootloader on factory firmware will pass everything.
[Magisk] g33gz:
Youre right!

I misread his messages with all the commotion going on 😬
[Magisk] Samg381:
I created a Google Support thread to voice my opposition to RCS messages being broken by this update.

If this affects you, please leave a comment and upvote it.
[Magisk] dr.ketan:
MEET_DEVICE_INTIGRITY started failng (Was OK few hrs ago). Updated fingerpring and it's back and passing now.
[Magisk] V0latyle:
What's the point of this, honestly?

This is like complaining about Google Pay not working in an abnormal security environment. RCS is end to end encrypted so of course it depends on the same factors. You're essentially telling them that you don't like how the secure aspects of their app depend on the security environment of the phone. You can disable RCS and carry on, or you can use a third party solution like Signal.
[Magisk] :
Interesting. Although I lost DEVICE attestation today (just checked again), I would be able to install Netflix. Even after reboot. I'm sure it was gone before. Anyone?
[Magisk] V0latyle:
Some of y'all REALLY need to read the relevant posts
[Magisk] bakaekze:
It's cached result. Will be gone after ~12 hours
[Magisk] bakaekze:
New XEU print is working btw.
[Magisk] gamemaster9641:
DEVICE attestation is back for me. Reloading the playcurl application enabled a valid FP and it works now. Weird, I wonder what that was all about?
[Magisk] Claus….:
Really? How come? Which phone fp do you use?
[Magisk] 4sz0m:
With RCS they are responsible delivering and caching your confidential comms. They don't want you to potentially spoof another device and get access to someone else's messages.
[Magisk] :
Some of you really need to read the post.

Netflix - as an indicator of DEVICE intetegrity before - was gone today and is now again available.
[Magisk] :
Wow, wtf just happened?? I rebooted and loaded another fp, and I'm back to 2 green lights. Crunch decision delayed! :)
[Magisk] aerotox:
@xSnowLeopardx been real quite since the new G update dropped :)
[Magisk] :
@4sz0m so pleased you're amused. Have you a helpful response?
[Magisk] 4sz0m:
@pancakenow I'm happy that you're back on 2 green and there's no need for any rushed decisions. I'm not yet green btw. Hope this was helpful.
[Magisk] 4sz0m:
@pancakenow To be clear, I am amused by what seems to be happening hopefully turning out to be some kind of Google f-up. Maybe too early...
[Magisk] xSnowLeopardx:
Well, to be fair, I only looked when you tagged me -> it only passes basic right now.

But, when I paid for some things today, hours and hours ago, all worked well. Rip. Gonna check my other FPs now. It was a long run with my 1st found one, almost 3 months.
[Magisk] :
My apologies, I misunderstood you. A laughing emoji to me in that context was baffling. To me, a smiley one would have seemed more appropriate :)
[Magisk] 4sz0m:
No need to apologise, I wasn't clear. I'll be laughing at Google every time they fail to deter one of us.
[Magisk] linuxares:
Mine got caught today as well
[Magisk] xSnowLeopardx:
Well, just tried all 20 of my prints. All give either basic or nothing. Fun...
[Magisk] 4sz0m:
Some are reporting success after changing print after a reboot, etc. We'll get to some kind of conclusion on a pattern soon I hope, but so far I am also out of prints.
[Magisk] xSnowLeopardx:
Would it be worth it if I am killing GMS via PixelFlasher anyways?
[Magisk] osm0sis:
Can confirm! Switching to the new 2024.02.29 Xiaomi.eu print got things working. So it's just a new VERY sweeping wave of bans.

Sad to see my very first print from Nov 19th finally go; Time to hunt for another working one!
[Magisk] HarryTurney:
Mine also got hit today, if anyone wants to share a working one or where they find theirs via DMS that would be great. For now, it's back to searching dumps that probably won't work.
[Magisk] Nergal di Cuthah:
You were saying? Lol all the thread needed was a mass ban and it's jumping again
[Magisk] CityKev:
Well sort of but not in a good way unfortunately.

My point was that Google are picking off the less committed / less technically able and it looks like what has happened today will accelerate that process.

Just call me Nostradamus :)
[Magisk] TPelangi:
All my print got burned 😂
[Magisk] CZ.Kostra:
I also have 20 dead today. 👎
[Magisk] 4sz0m:
All 20 mined from the same source maybe?
[Magisk] osm0sis:
I wonder if they finally harvested some of the big dumps...

I used my autopif.sh and migrate.sh to switch to Xiaomi.eu's for now on my daily driver until I can find another unique one.
[Magisk] 4sz0m:
Based on @osm0sis confirmation, it seems we need to find new working prints.
[Magisk] LuisNara28:
Isn't basic enough? I paid a while ago just passing device and basic.
[Magisk] 4sz0m:
I have to admit all 10 of mine were from the same dump source.
[Magisk] xSnowLeopardx:
Well, I know what I'll be doing on sat-sun :oops:
[Magisk] CZ.Kostra:
They were from several publicly available dumps.
[Magisk] osm0sis:
Finally upgrading to my fork? 😜
[Magisk] sawdoctor:
I was lazy and just reflashed you PIF module lol.

Would it be possible to get pif next or whatever it's called compatible with your fork as well as chiteromans? Maybe a pull request or something or is that not possible/defeats the objective of your fork anyway lol

It's mere mortals don't necessarily know how to easily find the Xiaomi prints. It would certainly stop the number of repeat posts in the thread
[Magisk] chiteroman:
Nah, they just banned fingerprint.

Module updated but as prerelease: https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v15.9

Report any issue here or on Github.
[Magisk] Claus….:
What do you mean by 2024.02.29 ziaomi.eu? Sorry for maybe stupid question, but is it some public known dumb of fps?
[Magisk] ionut310:
I started replacing prints after i saw that the one i was using from mid december stopped working. Decided to also check this thread and gave up afterwards :ROFLMAO:

I have 20 prints and tested almost half and of course none of them are working anymore.
[Magisk] bakaekze:
Some of my prints that were banned weren't on any public source and were very obscure.
[Magisk] xSnowLeopardx:
Nah
[Magisk] osm0sis:
autopif.sh is in the Resources in my README, and PixelFlasher supports using it as well. All pretty straightforward.
[Magisk] HarryTurney:
I will say I just used autopif.sh and yes it was very easy, just had to install Java and get apktool set up. Still will need to find my own key soon.
[Magisk] osm0sis:
Per the instructions, you run autopif.sh on your actual device and don't need to do any of that.
[Magisk] HarryTurney:
Right, sometimes reading is not my strong suit 🤐 (I didn't read anything I just grabbed the file)

Even so, it only took 5 min and some Google searching to get those running locally on Debian.
[Magisk] 4sz0m:
As a quick fix I changed to xiaomi eu print, working. Me not likey though, as it won't last long... Weekend mining coming soon.
[Magisk] V0latyle:
I must be doing something wrong, Termux is returning autopif.sh: inaccessible or not found

but I can see the script using ls and I chmod'd to 0755

I'm an idiot
[Magisk] linuxares:
Clear DG seem to bug out Droidguard so it report no fingerprints as valid xD
[Magisk] badabing2003:
Run YASNAC once or reboot
[Magisk] HippoMan:
All of the FP's that I tested earlier today are still not working, even though some people are reporting a reversal of today's banana-ing for their FP's.

It's OK for me, because of my hardware wallet. I just want to report my own findings.
[Magisk] linuxares:
Yepp or just wait 2 mins and it works :)
[Magisk] bombadier:
I got about 6 prints from the same well known source which were working up to today including a couple I consider "rare" from obscure devices but like everyone else they are all no longer working, tried running the autopif.sh script on my phone and now have a working xiaomi eu print for the moment..........
[Magisk] linuxares:
I think we all should just use the xiaomi.eu now and wait until tomorrow so the database gets refreshed. I suspect they vacuumed everything in there at the moment in the "known" one.
[Magisk] Vision:
Xiaomi Poco X3 NFC A11 MIUI 12.5

My official rom say: ro.build.keys=test-keys before unlock BL Pass 3/3

can i add a spoof and make it say ro.build.keys=release-keys ?

And can i add it inside in the PIF Module and working global only this line ?
[Magisk] osm0sis:
I haven't seen anyone report that yet. Everyone said they switched prints.
[Magisk] FrogMaster-:
You can also tell when things start to get heated up again because most of the Play Integrity Checkers start timing out from an overload of requests. 😂

I'm up again with the Xiaomi print as well. For now.
[Magisk] osm0sis:
You can edit the module .sh script, or my fork supports spoofing that prop only to DroidGuard.
[Magisk] Eclipse1991:
Has anyone tried if PlayIntegrityFixNEXT is still working and getting a working FP ?
[Magisk] heathrow1:
I am using a random print from thefreeman collection for two weeks and it still passes basic and cts profile im YASNAC.
[Magisk] MajicDroidPirate:
Thanks! I actually figured it out shortly after posting this question. After some effort downloading fingerprints i am now fully certified 🥳🥳🥳. Appreciate the reply