yashsingh1/xdaforums huggingface dataset:
[Magisk] Roll3r:
*.uber.com

Edit - I use adguard, a VPN, a firewall, and custom DNS. I whitelisted *.uber.com on everything, so I'm not sure which of those made it start giving me the app UI vs the web UI
[Magisk] HippoMan:
I'm not using any firewall nor custom DNS at all on my device, and I have no domain name whitelisted anywhere, and Uber Rider works fine for me (see my earlier message here for details). I do use AdGuard in standard configuration with nothing whitelisted there, either.

Perhaps the presence of a firewall and/or custom DNS can mess up Uber Rider unless whitelisting is implemented for the firewall or DNS ... ???
[Magisk] SOCOM-HERO:
Tried those methods in the linked post, no luck unfortunately!

I'm only running AdAway, whitelisted *uber.com, using HMA blacklist, IAmNotADeveloper 1.2 and BootloaderSpoofer 3.8. No luck so far.

There is an issue posted on BootloaderSpoofer's github: https://github.com/chiteroman/BootloaderSpoofer/issues/11

Hopefully there is a solve for this, other users have suggested using KernelSU but I have never used it and don't really want to go through all of the hoops if it won't work for me in the end.
[Magisk] HippoMan:
I'm wondering if your problem might be region-specific. I had the same problem as yours for a long time, even with the installation of Uber Rider upgrades. But then it just started working.

If there is a region-specific issue here, perhaps in my case, Uber might have changed something about how the Uber Rider app works in the New York City area.

What region are you in?

And what OS are you using? And which version of Magisk? And are you using Zygisk with Magisk?
[Magisk] SOCOM-HERO:
Magisk w/ Zygisk (Canary 27004 and new Shamiko 1.1/HMA require canary)

Ohio

Pixel 7 A14 AP2A.240705.004, Jul 2024
[Magisk] majorfigjam:
Is this on topic here now?

Whatever is causing your issue with Uber, be it root detection, firewall or whatever, it's clearly NOT due to having (or not having) Play Integrity.
[Magisk] HippoMan:
Hmm ... I'm using Magisk Alpha 27004 without Shamiko. But I kind of doubt that Shamiko would affect this, and I doubt that Magisk Alpha versus TJW Magisk would make a difference, either.

I wonder if Ohio versus NYC area could make a difference. In my case, Uber Rider just started working all of a sudden, and I'm not sure if this was or wasn't in conjuction with an app update.

If indeed there's some sort of region dependency, it might be that the Uber people could have simply changed how the app works in my region. If this is the case, then unfortunately I don't know what options you might have.

I'm sorry that I don't have any more useful information.
[Magisk] SOCOM-HERO:
probably not, I'll open a thread elsewhere, although there has been speculation it could be due to some of the things spoofing the prints could affect (like strong) t isn't confirmed based on what I've read.

Edit: after letting the phone sit for a little while, I checked the Uber app again and it is working! Must have been some kind of delay between applying the new lsposed module. Even survived a restart. Hopefully it stays that way. Thanks for the help @HippoMan
[Magisk] flyoffacliff:
Are we talking GIMP as in the photo editor, or GIMP as in the Google Integrity Master Plan?

My searches turned up both possibilities.
[Magisk] flyoffacliff:
I've been seeing this mentioned a lot. Not well documented but seems to be just yet another way of using a spoofed Keybox.

If I understand the current state of things correctly there have been no "public" keyboxes able to pass strong on their own for a long time. And the only known way to get strong is to use a key box from a device that shipped with A11 or older, along with spoofing a locked bootloader state.

Other than that I am not sure why people are messing with keyboxes at all still, given that the simple FP change in PIF gets you everything except for strong.

As far as I am aware a keybox does not include a FP. Basically a certificate is to a certificate authority, just as a fingerprint is to a keybox.
[Magisk] zgfg:
Not Master Plan but Manipulation Program
[Magisk] emmanuelcassar:
I am having boot loops with latest 16.6. I am rooted via Magisk, Pixel OS ROM, Poco F4. Also tried to uninstall module and reinstall with 16.6 but the issue persisted unfortunately.
[Magisk] frank93:
i wish. :/

berlin/germany area, for me it started in late 2023 when the whole fingerprint-thing began. so i assumed it had something to do with device integrity!? it worked for me SOME time during the last months for around 2-3 weeks, but now i’m back at "basic web experience" within the app. it starts as a full app, then "restarts" with the basic mode.

(magisk 27 (TJW) with zygisk enabled (for lsposed). PIFork by osm0sis, private fingerprint resulting in basic & device integrity, RCS working.)

i tried downgrading to the version you mentioned, a few others inbetween as well. tried having uber on the denylist and removing it, using shamiko, not using shamiko, using zygisk assistant, not using zygisk assistant, tried "hide my applist" .. nothing makes a difference for me. :(

at this point i’m happy to use the "basic" version of uber, but still i kinda feel defeated and want this damn thing to "work".

sorry, just ranting/venting here.
[Magisk] sawdoctor:
Osmosis posted something about pixelos and boitloops a few weeks ago so looks like the issue is still there. Perhaps take the fingerprint from 16.6 and use it with osmosis pif fork
[Magisk] emmanuelcassar:
Actually 16.5 is working fine, even RCS.
[Magisk] HippoMan:
That's great news! And I'm glad I could help.

My experience was similar in that Uber Rider just seemed to suddenly and mysteriously start working for me at one point, also. Since then, it's been consistently functional. I hope it's the same for you over time.
[Magisk] chiteroman:
Experimental PlayIntegrityFix with system signature spoofing to pass Device verdict on custom roms signed with test keys! Also it should fix the bootloop issue on PixelOS.

https://nightly.link/chiteroman/PlayIntegrityFix/workflows/android/main/PlayIntegrityFix.zip
[Magisk] casouzaj:
Tried the experimental (signed) build. Faced Google Play Services crashing all the time. Sticking to the stable release from yesterday. I still have RCS working with it.
[Magisk] n0stop:
I read the source code, it's a good project
[Magisk] sensui123:
Seems working on the non signed custom rom I'm running. 16.6 that is.
[Magisk] sawdoctor:
16.7 has just been released
[Magisk] fleamour:
playcurl was uninstalled with penultimate module?
[Magisk] Dr0n3r:
Works fine on a non-signed A10 rom, thanks!

View attachment 6125880
[Magisk] casouzaj:
Everything seems fine with PlayIntegrityFix v16.7. RCS, Device Integrity, certified in Play Store, all of them check! And no Play Services crashing. Thanks, @chiteroman!
[Magisk] efgx04:
Hello chiteroman, thanks to your pif but after flashing the latest pif 16.7 the su was exposed and detected, at 16.5 version there's no the same issue on kernel Su
[Magisk] Whoajoo89:
Thank you so much for this update! Tested and working: I'm finally passing DEVICE_INTEGRITY again on my device that runs an unsigned LineageOS 17.1 ROM.

Sent from Swift 2 X using ReLabs
[Magisk] sga999:
Something interesting occurred for me, but it may be for boring others. I have a Leeco Le Pro 3 with AICP 16 (Android 11) installed. I had 2 problems with it, never thinking the test key issue might be the cause. But it is!

I have used the excellent osm0sis fork, currently v9, until now. Once I saw the post about Chit 16.7, I decided to try it.

Here is what Chit 16.7 fixed (vs. osm0sis v9).

1. Both Boudin and Corner Bakery (restaurant apps) would crash unless I hid Magisk. Now with Magisk unhidden and Chit 16.7, they work well.

2. Sailfish json failed DEVICE with osm0sis fork, but husky worked. Now with Chit 16.7, Sailfish works. (Maybe changing some parameters in it would have made it work for osm0sis, but I didn't try).

I have other devices with different ROMs with official key, and I did not have either of those problems. So I was never really concerned, especially since I could fix them on the Leeco AICP. But "for fun", I guess I'll go with Chit on this old Leeco and keep osm0sis on my others.
[Magisk] fbirraque:
I confirm that Play Integrity Fix 16.7 by chiteroman works fine on a non-signed EvoX A13 (Redmi Note 8 Pro)
[Magisk] Zytrel:
@chiteroman Testkey builds only pass device due to the beta FP (which is the expected behaviour). Any non beta FP will still fail device with testkeys (at least sailfish does).

EDIT: Also, the spoofkey is right there in the source code, which means it will just as easily get banned as the fingerprints. Maybe instead you might consider generating real private keys on runtime.

Regards,

Zy.
[Magisk] fbirraque:
I confirm that Play Integrity Fork CI #248 by osm0sis works fine on XiaomiEU MIUI14 (Poco F3)
[Magisk] borisSweden:
Which is present in alt Gapps, I and many only need a real store to test PI.
[Magisk] Vision:
You mean like McDonald's app? 🤔
[Magisk] osm0sis:
This right here. 👍
[Magisk] trevtdogg:
seems like we do have a case where sailfish (non beta fp) works with test keys now.
[Magisk] badabing2003:
Is this the case of the user assuming that 16.7 is shipped with sailfish and stating that it woks?

Did the user explictly change the 16.7 print to use sailfish and confirmed that it works?

Hard to tell from the comments.
[Magisk] sga999:
For my Leeco AICP, 16.7 started at husky and passed both, but I specifically wanted to see if sailfish passed DEVICE since it did not before. Now sailfish does pass both.

testkey.x509.pem is the result of the unzip command.
[Magisk] osm0sis:
Does husky_beta print on PIFork also resolve your app issues or is whatever 16.7 does more system-wide?
[Magisk] fbirraque:
I confirm that PI Fix 16.7 gets Basic and Device with the default pre installed PIF or even with sailfish on Redmi Note 8 Pro (non-signed EvoX, A13)
[Magisk] sga999:
Sorry, I was inaccurate. Without ANY PI module, those food apps crashed unless I hid Magisk. I set it up that way "a long time ago", even before installing any PIF module (I may have had the old SafetyNet module installed). Now, I tested those apps with your v9, husky or sailfish, and they do not crash. The only issue is that with your V9, sailfish fails DEVICE.

Logcat is attached with sailfish working with 16.7, if anyone wants to see it. I don't know what "Throwing exception" means. Please let me know if that is interesting. If you need the logcat with v9 and sailfish failing, let me know.
[Magisk] osm0sis:
Yeah give me a full fail log for comparison please, with verboseLogs 100. We know not all prints are universal, but sailfish seems pretty widely working (minus RCS), so I wouldn't expect any difference between PIF and PIFork that would cause that for you.
[Magisk] sga999:
Apologies for not knowing this. I usually do:

adb shell

su:

killall com.google.android.gms.unstable

logcat | grep 'PIF'

Can you show me exactly how the logcat line should look?

EDIT: Never mind. I think I see how to do it.
[Magisk] fbirraque:
GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com
[Magisk] osm0sis:
Follow the link in my post there, it has it. Also, make sure it's directly after a reboot so I can see any ROM interference. Thanks!
[Magisk] fbirraque:
I'm on PI Fork CI #248 running flawlessly.

Is it expected in the future CI builds to support non-signed ROMs?
[Magisk] osm0sis:
If you're using a Pixel beta print then you're already exempt from the testkey ROM ban, nothing new required. 🤫
[Magisk] sga999:
When I first tried, I had the verboselogs after the grep. Silly me.

Anyway, there are lots of extra "ro." lines in the json, some of them are delayed a little. You'll see in the timestamps. I'm sure I deleted those at some point, and it didn't make a difference.
[Magisk] osm0sis:
That's definitely not with verboseLogs 100 in your json and not directly after a reboot with DroidGuard starting naturally.

Please follow the instructions: https://github.com/osm0sis/PlayIntegrityFork?tab=readme-ov-file#read-module-logs
[Magisk] fbirraque:
Okay... I'll not tell anyone! :cool:

Thanks for the clarification I didn't know that.

(*) But how could I get the Basic and Device cert on an unsigned ROM with Sailfish when PI Fix 16.7?
[Magisk] Mitezuss:
So, only need beta fp to pass "device" on rom with testkey ? (maybe for now)
[Magisk] osm0sis:
Yeah dude, we've been talking about it, it's in his changelog and his commit history. 😛

Implement system signature spoofing · chiteroman/PlayIntegrityFix@fa8f539

Devices with unsigned custom ROMs (signed with test keys) should pass Device verdict. Co-authored-by: 4h9fbZ <7454974439@proton.me>

github.com

But it also seems to have destabilized PIF yet again.

Issues · chiteroman/PlayIntegrityFix

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

github.com

I'm just saying all that's not super necessary when we know just using a readily available Pixel beta print with PIFork also works, and no risk of crashing your device. 😉
[Magisk] sga999:
Sorry again, I didn't read the description well enough and thought the verboselogs went on the logcat command line. I'm still not sure if I did it "with DroidGuard starting naturally". I think I did because after reboot, I did adb shell, su, logcat, and it didn't show anything. But in several seconds, maybe 10-15?, it started displaying. Let me know if it's still wrong, and I'll continue tomorrow.
[Magisk] osm0sis:
That's perfect. Thanks! I'll see what I can see. 🙂

Edit: A full log after boot from PIF 16.7 with his debug option enabled in the json would be better for comparison when you get the chance. 👍
[Magisk] matfcb:
16.7 not getting past MIUI logo, 16.6 worked fine. Xiaomi Mi 9 Pro 5G Android 11. I deleted PIF in TWRP but it's still stuck at logo, maybe I will go in module updates folder, and delete it too if it's there.
[Magisk] osm0sis:
If you get it working again I'd say try this CI build of 4h9fbZ's fork of PIFork which also adds the ROM signature feature: https://github.com/4h9fbZ/PlayIntegrityFork/actions/runs/10024548087

If your ROM still dies with that then I guess we'll know for certain that's what destabilized PIF 16.7.
[Magisk] matfcb:
I deleted hosts module and it still doesn't boot. Why would anyone release so problematic 16.7? I will delete another module now, but I fear my phone is bricked :(
[Magisk] borisSweden:
We can't have this conversation again but it's not for passing, it's for functionality. I tried to add Phonesky to be the shell to test PI, as of now (knocks on wood), RCS works on a present stable lax state. Wallet and fast food company that abuses SN/PI because of coupon cloning is least of my problems. If PI is a several steps ahead of alternatives Google Services, well sandboxed Google Services is the next best thing.
[Magisk] osm0sis:
Why indeed. 😕

From the similar (Mi 11 Ultra) Issue on chit's GitHub I see not even fully unrooting the device completely helped, so I fear wiping data might be the only way out. 😔

Bootloop miui 14 /PlayInt16.7 · Issue #380 · chiteroman/PlayIntegrityFix

Hello, Everything was working with play integrity 16.5 Today saw cts failed. Updated to 16.7, then bootloop cannot solve it. Im on mi 11 Ultra with miui 14 and android 13. Im still in bootloop cann...

github.com
[Magisk] matfcb:
My phone somehow booted into Safe Mode. What should I do now? Delete the last module (Viper4 android and reboot)? Or do something else? I deleted all the modules but Viper4android. Help me.
[Magisk] osm0sis:
My guess would be the signature spoofing made MIUI corrupt your ROM data. Why it only bootloops when rooted is confusing, but I think wiping data might be the only way out.
[Magisk] osm0sis:
Wait, had a thought.. go into Developer Options and check your OEM unlocking toggle. Toggle it off and on again if you can. See if that makes a difference.
[Magisk] matfcb:
It booted into system after I deleted Viper4android. After deleting hosts, Shamiko, Zygisk it didn't boot. I will try to install all the modules but no PIF, but later. I won't try to do anything now, I have to go to work in 3 hours. I am most angry about losing my Viper4android settings. Why this 16.7 version wasn't called off after users said it's problematic?
[Magisk] osm0sis:
Great question for chiteroman to answer. 🤷‍♂️

I wonder if that user on GitHub also has Viper4Android.. 🤔
[Magisk] spida_singh:
I get the same issue

Pixel 6

LOS 21

KSU
[Magisk] matfcb:
In what order would You suggest to install following modules and reboot after each one or one reboot after all installs? Shamiko, Zygisk LSPosed, Viper4android. I will do it later at evening, for now only Magisk is installed.
[Magisk] osm0sis:
No clue, of those I only use Shamiko.
[Magisk] sawdoctor:
He does tend to release beta versions on telegram 1st for testing but for some reason this went straight to public release unless it's based on the previous beta, i haven't checked
[Magisk] xcl1pse:
Which viper? OG, programminghoch or wstxda?

Btw, wavelet ftw
[Magisk] matfcb:
RepackagedHoch87​

It still has icon of Viper4android and it's in the autostart but no module in Magisk. I don't know if I should reinstall zip module first or open the app and try it to download the driver. After work I will get Viper4android to work then other modules.
[Magisk] pershoot:
If you do not intend to test and do not have contingency to back out should an issue arise, then you should stay with what is known working on your specific device and take a pause to observe before jumping to upgrade.
[Magisk] xcl1pse:
Oh then its by programminghoch. By any chance using MIUI mod like EU? I only think the problem related to hide/disable injector that chiteroman used. I found nothing suspicious between 16.6 and 16.7

Edit: I realize chiteroman rebasing the source again, hmmm
[Magisk] Vision:
About PIF, which does not tell us about the other apps conflicting.

View attachment 6126060

Update customize.sh by VisionR1 · Pull Request #381 · chiteroman/PlayIntegrityFix

A little clarification, according to this: #378

github.com
[Magisk] osm0sis:
Worked when I did it all properly in PIFork. 😄
[Magisk] xcl1pse:
It does conflicting, the real question is does injector stop working after patch boot/init boot img with magisk? Does the rom include specific injector to pass play integrity or not? Does the rom that you are used stop updating but you still want to use it? Honestly, for specific injector i think only hOS a bit rational for implementation, other are just copy pasta or just messing with apex or use unnecessery step. The only reason I see more custom rom using injector is if the rom discontinued or not maintained, you still can pass device integrity with just updating the injector but this approach only buy us a time. We dont know what google is doing right now, even play integrity still have flaws
[Magisk] Vision:
Unfortunately, the parameters is lot.

That's for sure, play integrity have flaws.

Here I have see so many intelligence people, who have know much more, from entire Google.
[Magisk] xcl1pse:
The question is really simple. User should know before flashing this module. Even just pputils work just fine, I dont see any reason including this unnecessary injector just for play integrity
[Magisk] Vision:
Yeah I get your point.

For that @chiteroman decided to remove all this, plus lot of bugs cause of this.
[Magisk] CZ.Kostra:
There are many custom ROMs users who don't want to ROOT. Built in injector is probably only way such a user can pass PI.
[Magisk] xcl1pse:
If using AOSP as base, pputils work just fine as already state, it work not or with root. I dont see any point to implement any injector at all. As for using stock rom as base (modded stock), is there any problem if it not passing play integrity? Most of the solution for not wanting to root their device is just to make a mess rather to fix it. Also what happen to people that want to root their device but got another problem because of the rom implementation? Back to early question, does the injector working when using magisk etc? If yes then forget this module. If not then read the caution and what this module does, dont just listen to what other people say. I'm sick off to see dev fulfill user request which goes beyond the original goals of the project their created
[Magisk] CZ.Kostra:
I agree with you and would never blame the developers. On the contrary. I am very grateful to them. I just wanted to explain presence of injector in ROM.
[Magisk] pndwal:
Many ROMs have included means to pass S/N and PI DEVICE_INTEGRITY for years, even @microg... Some used @kdrag0n's method from his Proton ROMs and the more advanced injection methods have also been developed...

If up to date and working, these will also work with root and without PIF just by adding GMS DroidGuard (unstable) and main (for A11+, other?) processes in denylist (best to use Shamiko or other proper hiding solution, but it's not needed for integrity verdicts) to hide root from GMS. Many users just don't know this.

The problem is that when the integrated solutions become outdated and failures can no longer be fixed, users must rely on/wait for the Dev(s) to update the ROM or use alternatives like PIF. Also, some Devs may not have gotten the thing working properly in the first place.

Some ROM PI solutions conflict with PIF and some don't... If such solutions can be disabled however, there should be no issue using root and PIF as an alternative. 🙃 PW
[Magisk] xcl1pse:
OG kdragon method in ProtonAOSP was great but google wasnt happy. The original plan was to block safetynet attestation using key attestation via keystore, but after google put hardware attestation for checking safetynet, the plan change from blocking to altering the name and model device that use hardware attestation to device that still use software attestation so safetynet can pass again. This method still use until today. Even PIF still using this method with some modification. From this rom implementation (in this case ProtonAOSP) jhenrique, dyneteve etc improve the method and create new method. Its call pixelproputils or pputils for short. The only problem with this method was we dont know what next step google do in future, so the method is need to refined for latest update. So update custom rom is needed. The injector come when chiteroman PIF's module was update more once a week because fp banning so to prevent numerous updating and keep fp isnt burn quickly (it still useless tho) is to create another injector just for pass play integrity. But this unnecessary step just to make another problem rather to fix it, from messing with apex, create loophole to make banking app not working, etc. Even more, if there is huge rebasing or method to pass play integrity, happy or not you need to update again you rom and the old method injector is obsolete. Theres nothing wrong with pputils, just update sp, make some refinement and you are set. No need separate injector to make same fuction just to prevent if the rom their use is unmaintained. If people want to see pputils working just fine without injector, just see derp and other
[Magisk] Zytrel:
Since there are now reports of testkeys actually working with sailfish, maybe I was a bit too quick with my verdict.

I tested it on two (rather old) devices: Samsung Galaxy S5 (klte) and Galaxy Tab Pro (picassolte). Both with the same configuration of LineageOS 18.1 (A11), Magisk 27 and PIF 16.7. No other modules which might interact. Both failed with sailfish.

The interesting thing is that the S5 actually has releasekeys but still fails. I just assumed that key got banned, but maybe there's some other underlying issue regarding sailfish and Samsungs.

Update: I just tested the S5 with my own build and private keys, and sailfish still fails. So there's definitely an issue with my specific configuration and sailfish. Unfortunately I don't have any other working prints to test with.

Regards,

Zy.
[Magisk] immortalwon:
Did anyone's "hey google" voice assistant stopped working?