yashsingh1/xdaforums huggingface dataset:
[Magisk] sga999:
Sorry, I replied to my own last post rather than yours, so I don't know if you get notified.

When you said "Inspect kernel_unpacked to determine the offset", what do you use to do that on Android? I had been using Windows HxD to look at the unpacked file.

Once I know the offset, I'd like to "inspect" again before flashing. But it seems like when I supplied the offset after finding it with a Windows app, which is a pain to copy things back and forth), it created the new image, but kernel_unpacked was gone. I'm sure I'm missing something. I'm trying to look at it without moving it to Windows, patch it, look at it again without moving it to Windows before creating the new image and flashing.
[Magisk] TheFreeman193:
I've been looking into this as well (by stepping backwards/forwards from release string matches to look for adjacent fields/spans). Very few kernels modify the sysname or machine fields, and fewer still lack the UTS stuff entirely, so it's a potentially reliable target.

Once I've done a bit more testing I'll look at making it into a proper offset detection script to share here.
[Magisk] badabing2003:
HxD is good, do it on Windows, find the offset, you only need to find it and patch it once.

Did you follow the steps here?
[Magisk] sga999:
Yes, I did go to Windows inspect it, but it would be "nicer" to not have to do that. I didn't patch it more than once, so I'm sorry if I made you think that. It just seems like there is lots of copying back and forth.. Somehow I thought your method was going to eliminate that.

I did follow all of your steps, but until I learned more about the "inspection", I didn't move forward with actually flashing. That's because I managed to patch too many places a couple of days ago and crashed. So I was trying to be sure before continuing. I mean, I wanted to inspect it again after copying it back, but before flashing it.
[Magisk] badabing2003:
if you don't pass the -flash flag, it will not flash, and no you're not supposed to patch it on windows, just inspect it.

I'm sure there are hex inpsection tools on Android.

The script does everything for you except tell you the offset (for that see the guide provided by @osm0sis and later linked by @Umgak), if you feel more confortable doing all the steps manually, do that.

Use it if you want, throw it out if you don't.
[Magisk] HAHAHAHAHAHAHAHHAHA:
Hi,

I am not 100% sure where to post this but my banking app (K PLUS, thai bank) still detects some modification despite all the PI/root concealment.

View attachment 6064671View attachment 6064670

My setup is this:

Magisk Alpha lastest: d78ee171 (26405)

Shamiko v1.01 on blacklist with GSM&co in DenyList and DenyList NOT enforced

PIF v15.5 by @chiteroman (I also tried @osm0sis 's version)

playcurl v6

_ I tried Magisk Kitsune before, didn't work.

_I tried checking these props, that didn't fix anything

Some kernel strings are blocked by Goolag · Issue #236 · chiteroman/PlayIntegrityFix

For example Sultan kernel on Pixel 7/Pro/a is blocked from Goolag since it has a string named Sultan in it. They are checking for blocked words (case insensitive) in the uname kernel string, so I w...

github.com

https://www.reddit.com/r/Magisk/comments/17ul1nt

_I am using an official A12 kernel unofficially provided by @Surgemanxx because of georestriction on updating AT&T phone: uname -r → 4.19.157-perf+

This app is required to approve all online transactions and I am not getting a new phone in a while so...

Does all this mean that this app requires STRONG_INTEGRITY? 😭
[Magisk] sga999:
I certainly won't throw it out! It is definitely a learning experience for me, and I will examine the script more, maybe do the steps manually. Even If I don't do that, it is still very useful.

I did erroneously say something about moving it to Windows, patching it. I really meant moving it to Windows, looking for the string to patch. I think all I want is to be able to patch it, look at it again before flashing.

Maybe I can just use a similar dd command with if= vs. of= to show about 16 characters around that patch. I don't know enough about the dd command, but I will play with it. This is all probably silly, but once I made the mistake and it crashed because of a bad patch, I want to be more careful. No need for you to respond. I'm sure some people are tired of this conversation!

Thanks again for your help!
[Magisk] rat7lol:
It either requires STRONG integrity or the app checks for root/mods in non-standard ways. For example, something like a "TWRP" folder in the internal storage could cause this. You could try reverse-engineering the app perhaps?
[Magisk] HAHAHAHAHAHAHAHHAHA:
>For example, something like a "TWRP" folder in the internal storage could cause this

No such thing here. TWRP wasn't used, I flashed a custom partition from Qualcomm's EDL mode.

(https://xdaforums.com/t/v60-bootloader-unlock-and-magisk-root.4358785/)

I'm afraid I don't have the skills as far reverse-engineering the app is concerned
[Magisk] chiteroman:
No
[Magisk] xflowy:
thanks! is the strong_integrity pass required for banking apps or should i be good? sorry..new to this :/
[Magisk] pndwal:
I suspect if the Key Attestation indications are erroneous here, they'll still be with bootloader unlocked and if it indicates Verified boot state instead of SelfSigned then data collected by droidguard will probably also reflect that consistently.

If the broken chain of trust / keymaster implementation on your friends device is anything like the ROG Phone 3 (Google already revoked keys for STRONGINTEGRITY), I think he/she would also be able to achieve the same STRONGINTEGRITY verdict with normal root and unlocked bootloader...

Because of both the bad measurements (likely just duplicating the Basic, SW, attestation signals and passing them off as derived from hardware backed keys, ie from TEE, or Droidguard VM simply sees these as hardware backed attestations despite some exception having triggered a fallback to basic only on-device measurement collection) and (evidently) lax implementation of Google server end hardware-backed enforcement for STRONGINTEGRITY verdict, that device was able to achieve STRONGINTEGRITY verdict simply by 1) spoofing an older fingerprint (in MHPC module) to bypass server end hardware-backed evaluationType enforcement (should really work only for DEVICEINTEGRITY by rights but seems G allows STRONGINTEGRITY to pass with this too if Droidguard is passing them off as derived from hardware backed keys, ie from TEE), 2) by using Shamiko (or any solution that adjusts sensitive/'suspicious' prop values, and 3) by hiding root from GMS main and Droidguard/attestation processes (Google Play Services com.google.android.gms and com.google.android.gms.unstable processes)...

Depending on what fingerprint prop your friend's LineageOS ROM implements (I believe official builds simply use latest stock) you may not need to adjust that as latest stock for that device seems to be Android 10 and Google generally didn't enforce Hardware Backed evaluationType verdicts using fingerprint prior to A11... However fingerprint must match security-level date unless very old, and spoofing with MHPC ensures this... It's also possible that you'd need to spoof model prop value in addition as a mismatched model is required for the bypass on many devices...

👀 PW
[Magisk] CiLiBi18:
Hi chiteroman, on my OnePlus 11 it still not working. I tested every patch, nothing worked.. :(

When enabled, the phone freezes on every single Google app, even YANSAC doesn't work, it keeps loading.

Thanks for your hard work and for your response.

View attachment 6021189View attachment 6021190View attachment 6021191
[Magisk] zgfg:
It depends on the bank and their app

Usually not but it may require additional techniques - again, it all depends on that app, your phone, ROM, etc
[Magisk] shoey63:
Before anyone gets excited about AVB Root

I've tried it on Pixel 6, and no, it doesn't take you to the promised land of HARDWARE _BACKED evaluation.

You get verified_boot_state= yellow, but that is not enough. Has to be green. In other words, bootloader locked on manufacturer provided firmware.

Unless of course, you have broken TEE implementation and Google hasn't blacklisted the device 😊
[Magisk] xflowy:
thanks! will the displax mod achieve strong integrity?
[Magisk] DougMG:
Please use the search feature as this has been answered numerous times now however the answer is no and will most likely stay no.
[Magisk] chiteroman:
Maybe you can't use a random generated key. Perhaps using the AOSP private key...
[Magisk] chiteroman:
How he do this?
[Magisk] noobSU:
I'm using Displax safety net mod latest. Playstore is certified. Basic & device passes. Just Meets strong integrity failed. Should i be worry? Everything works fine. Can i use your mod aside with displax to pass Strong integrity?

I'm using custom miui 13 rom based on Android 12. My phone is poco x3 nfc.

View attachment 6021574View attachment 6021575View attachment 6021576View attachment 6021577
[Magisk] bobo_15:
Sorry for asking it here, but I think that is the best chance I have to get a good answer

Does anybody know if there is a custom rom for OnePlus 10Pro, or if there is a chance to get one in the near future?
[Magisk] zgfg:
Ask in the OnePlus 10Pro forum/Thread/Telegram channel - what does PIF module have with that custom ROM

And before asking there, specify which custom ROM you're interested about😁
[Magisk] zgfg:
Please, before asking others to answer you, take a minute and read OP post #1. Or quickly scan few latest posts on this page, like post #1063

There are tons of NEGATIVE answers about Strong Integrity
[Magisk] MeTaLxMaNiAC:
Thank you very much Marcos , it was the only magisk´s module what directly worked for me (android 14 231005.007 pixel 7)

No need of any extra tricks, even too droidguard is complicated ****, i will donate u something ofc

regards

Andi
[Magisk] chiteroman:
Provide module logs, maybe I know where is the problem
[Magisk] chiteroman:
New test build! Now using shadowhook but including it in the zygisk lib! Source code updated.

Release v9.3 · chiteroman/PlayIntegrityFix

Use shadowhook instead Dobby Drop support for x86 and x86_64 (shadowhook doesn't support them) Removed useless code Removed libcxx Using system STL Should work in more devices

github.com
[Magisk] chiteroman:
Check prerelease build: https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v9.3
[Magisk] chiteroman:
I think is your setup, try to use stable Magisk Delta or change to Magisk Alpha.
[Magisk] xcl1pse:
Hmm.. did the warning show before login or after setup? And yes, that app checking Play Integrity but I think passing device integrity is enough tho 🤔
[Magisk] HAHAHAHAHAHAHAHHAHA:
it shows immediately when I open the app before I have the time to do anything

Pinging @ps000000 too as I a saw an old post of him that mention the same app https://xdaforums.com/t/guide-howto-use-banking-apps-on-your-rooted-device.4530801/post-87873417
[Magisk] xcl1pse:
I'm outside now so I stuck in this page. But no warning about root

Edit: well, I can't test that app since even enable cellular data and using another phone with locked bootloader, it still show this page. I don't have Thailand SIM card so maybe that's the issue

View attachment 6064681
[Magisk] zgfg:
Maybe your app really requires Strong but maybe it doesn't but it detects the same as Momo: Restrictions on non-SDK interfaces not working - you should not have it with the stock/certified ROM and kernel

See more about here:

Restrictions on non-SDK interfaces | Platform | Android Developers

developer.android.com

Eg, I have the same detection by Momo with Xiaomi.eu ROM - it comes from Xiaomi.eu custom modifications, not present in the original Xiaomi MIUI ROMs

AFAIK, you can not hide it

PS: It has nothing to do with TWRP...
[Magisk] tom1807:
To my defense, I had only one coffee :p

And now for something completely different, updated the Pixel 6 to the February 2024 version, Google didn't mess up anything, so everything still works with Play Integrity Fork v7 (yes, I am paying now attention) and Magisk 27, Shamiko 1.0.1.

PlaySystemUpdate January 2024

Google Play Services v24.02.13

Cheers

Tom
[Magisk] tom1807:
I suggest you update to Magisk 27. On my mobile before the update, one banking app still detected root and the other not, since the update both are fine and, most surprisingly, I don't have to hide Magisk and still works.

Not familiar with playcurl v6, but is this module necessary?

Maybe this causes the failure.

Cheers

Tom
[Magisk] xcl1pse:
He's using magisk alpha so for now no v27. Actually he doesn't need playcurl with PIF 15.5 since the fingerprint is same. Playcurl used to automatically grab and replace pif.json for PIF module without manually searching if the current one is failing
[Magisk] majorfigjam:
So I tried this app with the latest magisk canary, shamiko etc, and got a - won't run on non-standard devices - message, followed by the app closing itself.

It doesn't require Strong Integrity, as it loaded on my stock oreo moto, but it has some strange validations (like your doesn't like wifi message) there as well, so I couldn't get it to run either. As it's a bank app used for authorisation of payments, it likely has other root or anomoly detecting techniques.

That's unfortunate for OP, and let's hope this doesn't spread to far too quickly. Maybe HMA or equivalent might help.
[Magisk] xcl1pse:
Hmm so my theory seems right. For now every app using and request Play Integrity checking via finsky doesn't need to pass Strong Integrity, just pass Device Integrity is enough
[Magisk] tom1807:
He's using Magisk alpha (26405), and yesterday was the official release of Magisk v27.

That's not for validation, several banking apps require this to bind the account to this specific mobile to confirm the owner by the mobile number.

Cheers

Tom
[Magisk] xcl1pse:
TJW Magisk ≠ Magisk Alpha. Regarding of changes especially of zygisk, Alpha already ahead but for now it's the same. If he's willing to change from Magisk Alpha to TJW magisk, it's his choice
[Magisk] zgfg:
It was responded above, his app probably detects the same as Momo on his ROM/Kernel: Restrictions on Non SDK Interfaces not working

If you don't have that detection in Momo on your Oreo Moto (with unlocked BL - working for you), then it shouldt be that

Apparently Google PI does not look for (although G defines which old APIs are deprecated and specially which old APIs go on their Blacklist) but Momo and some apps do detect
[Magisk] linuxares:
I just take an uneducated guess and think this is the reason why your banking app don't find it.

[Zygisk] Introduce new code injection mechanism
[Magisk] majorfigjam:
It's not that. I used canary 27001, and k-plus still detected root or rather a non-standard device. It's not a PIF issue though, as it doesn't require strong integrity to work.
[Magisk] xcl1pse:
Fun fact: There's no official documented how zygisk work on the background, let alone shamiko. So app detecting root can vary from the weakest detectors which can revoke via denylist or pay root detectors like LIAPP or reverse engineers how root tools like Magisk and KernelSU work
[Magisk] chiteroman:
Install this app and send screenshot: https://play.google.com/store/apps/details?id=io.github.vvb2060.keyattestation
[Magisk] HAHAHAHAHAHAHAHHAHA:
@chiteroman

View attachment 6064793

🤔🤔🤔
[Magisk] chiteroman:
Try using LSPosed and this: https://github.com/chiteroman/BootloaderSpoofer/releases/latest

Maybe the app checks for a valid hardware attestation.
[Magisk] HAHAHAHAHAHAHAHHAHA:
I forgot to mention, I had tried this too but unfortunately no luck (tested on v3.8)

Wait I will retest. I forgot there is a per app activation for module in LSposed
[Magisk] HAHAHAHAHAHAHAHHAHA:
View attachment 6064798

Different result here but same result in K PLUS
[Magisk] Xxthefirr:
what can i do to get mine working correctly? i live off of gpay.... heres the screen grabs... (xt2323-2 stock rom patched with magisk, no twrp/cwm/etc)
[Magisk] xcl1pse:
Already try HMA?
[Magisk] chiteroman:
Did you disable USB debug ?
[Magisk] defroster:
I bought a cheap old android 10 tablet (lenovo m10) to use in the kitchen for music/recipes but google assistant won't launch revanced version of youtube music so I thought, Oh I'll just root it and install a custom rom, I did that ten years ago with my phone and it wasn't too hard.

Well it's too hard.

I've installed LineageOS 21 light and Magisk via TWRP, I've installed Play integrity fix, I've enabled zygisk and enforce denylist, added play services and store to it, wiped cache and storage, but as soon as I connect to wifi it spams the message "This device isn't Play Protect certified" - "Google apps and services can't run on this device"

and indeed they can't.

All I want is a newish version of android and root so I can play my music in the kitchen :(

e: I don't give a rats a** about netflix, banking apps etc.
[Magisk] V0latyle:
Read my Play Integrity Info thread and @osm0sis' PIF FAQ

As an aside, for proper integration with other Google services, I use the ReVanced Magisk modules...although this is on a Pixel where YouTube and YT Music are system apps
[Magisk] HAHAHAHAHAHAHAHHAHA:
@xcl1pse people seemed to say it's not important so I hadn't try, but yeah no luck either.

@chiteroman I even disabled dev options no luck

@Xxthefirr follow instructions page 1 mate
[Magisk] FlexWheeler:
Few days ago I was running Magisk 26.4.

I had no issues at all. I successfully passed each Play Integrity test: Basic and Device integrities.

Yesterday I updated to Magisk 27 via in-app. It was asking for an update and I directly installed it.

After a while I thought to check if everything was still alright.

I started noticing I don't pass any Play Integrity check at all.

I am worried. I don't know how to fix those errors.

I need to pass those Play Integrity tests for safety measurements.

Please, help me fixing all as it has been with Magisk 26.4.
[Magisk] chiteroman:
Did you install a GSI ?

If you did that, read this: https://github.com/phhusson/treble_...w-to-bypass-certified-device-after-first-boot
[Magisk] rodken:
Did you try to revert back to 26.4 to see if you can pass BASIC and DEVICE again?
[Magisk] lupastro82:
I too, but no problem here.
[Magisk] Xxthefirr:
Hey "MATE" I very much did follow the f****** instructions! Why the hell do you think I'm here asking for help...
[Magisk] FlexWheeler:
Can you link to me your Play Integrity fork .zip?

Maybe I can solve my issues with your .zip which is different from "Play Integrity Fix v15.5 by chiteroman".

EDIT: I've found it

https://github.com/osm0sis/PlayIntegrityFork/releases/tag/v7

Im going to install it and see how it goes. I'll keep you updated here posting a new post.
[Magisk] FlexWheeler:
It's too much work. I don't want to revert it 'cause I have no time/will to do whole work.

I should basically formatt my phone then re-installing a brand new Magisk (26.4).
[Magisk] HAHAHAHAHAHAHAHHAHA:
@Xxthefirr You hadn't mentioned it, that's all.

Did you also set the DenyList properly?

You can give a try to the PIF fork above too (osm0sis/PlayIntegrityFork)

If it still doesn't work you can try to combine PIF with a different Magisk build like Magisk Kitsune or Magisk Alpha.

[Discussion] Magisk Alpha (Public Released) fork - @vvb2060

This is the spot for the General Support Discussion of Magisk Alpha "Public Released" fork created by @vvb2060. Disclaimer: This Magisk Alpha fork is not supported by @topjohnwu and is not an official channel for him. Use at your own risk...

xdaforums.com
[Magisk] rodken:
It all depends on what your version of too much work is after combing through this method.
[Magisk] FlexWheeler:
As a worried as I am, I tried to copy your setting 'cause you have no issues (as far as I've seen on your attached pics).

I installed "Play Integrity Fork v7". It solved only one Play Integrity check: basic integrity.

I'm still missing "device integrity" check as you can see on my attached vid.

Any help please?
[Magisk] tom1807:
Is this secret code for, "I don't understand anything, so hand me the solution on a golden plate".

Btw. this is not TG, so chose your words more wise.

Cheers
[Magisk] tom1807:
Then you are 1/3 there, now you need a FP which is not banana-ed.

Easiest way is still the Pixelflasher.

Cheers

Tom
[Magisk] FlexWheeler:
Can you explain to me something more about?

I've not understood what you meant. Sorry. I need something more explicit.
[Magisk] Xxthefirr:
Should I run the LSPosed module too?
[Magisk] tom1807:
Is this easy enough?

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

Don't get distracted by the name, this program developed into a All-in-one tool.

Cheers

Tom
[Magisk] tom1807:
Is anywhere in the guides written to use LSPosed?

The project is on ice, I would not rely on that anymore so much for the future.

Cheers
[Magisk] lupastro82:
Ok, but with Pif fork I used also pickaprint.sh: https://github.com/TheFreeman193/PIFS
[Magisk] defroster:
Yes, Lineage 21 GSI.

I am trying the app and it says not compatible with device (Android 13?) and can't get the adb command to work, from windows I'm getting:

C:\adb>adb root

restarting adbd as root

C:\adb>adb shell 'sqlite3 /data/*/*/*/gservices.db \

"select * from main where name = \"android_id\";"'/system/bin/sh: no closing quote

C:\adb>adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ select * from main where name = \"android_id\"';

/system/bin/sh: sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ select * from main where name = "android_id": inaccessible or not found

C:\adb>adb shell 'sqlite3 /data/*/*/*/gservices.db \ "select * from main where name = \"android_id\";"'

/system/bin/sh: sqlite3 /data/*/*/*/gservices.db \ select * from main where name = "android_id";: inaccessible or not found

e: if I run Terminal from TWRP and enter adb shell "sqlite3" I get

sh: adb: inaccessible or not found

e2: I also see I have garbage showing up via MTP as if it's encrypted but I've Formatted the Data partition numerous times..

e3: installed Android 12 rom so I could run Get ID app but the Google Service Framework Key is blank :'(
[Magisk] rodken:
How long before you hit paydirt utilizing pickaprint.sh?
[Magisk] FlexWheeler:
I donwloaded

.pickaprint.sh

but how can I run it on my Poco F4 android device?

I mean, I don't know how. One thing it came in my mind was about running throught Recovery Terminal... but I don't know how to move on.
[Magisk] lupastro82:
See here 😅

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] V0latyle:
That's weird. I updated to 27.0 and had no issues.

Before you change anything, try wiping Play Services data and reboot.
[Magisk] sawdoctor:
Remove play services from deny list and try again
[Magisk] FlexWheeler:
I did it but it ended upo with no results.

I'm trying to run .pickaprint.sh but it still fails............
[Magisk] defroster:
It wasn't on the deny list the first couple times I tried..

It literally starts spamming the "unauthenticated device" notification as soon as it connects to wifi in the initial setup.. I'm not connecting to wifi to avoid that in all my attempts but I am just getting nowhere

e: also, are you just meant to paste:

adb root

and then:

adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \

select * from main where name = \"android_id\"';

into the command prompt?

I get 'no closing quotes' if I do, and if I change it to one line I get "inaccessible or not found".

even tried copying sqlite3 file to the external_sd/ folder