yashsingh1/xdaforums huggingface dataset:
[Magisk] badabing2003:
You need to make sure it runs last.

By the way I tested @osm0sis script by commenting out the line that does not allow update if the new value is larger size than the old value and it worked just fine. (orange > green)

Not sure if in other contexts it should pause an issue, but I suspect not.

redfin:/ $ su
redfin:/ # cd /data/local/tmp
redfin:/data/local/tmp # getprop ro.boot.verifiedbootstate
green
redfin:/data/local/tmp # resetprop ro.boot.verifiedbootstate
green
redfin:/data/local/tmp # sh ./resetprop_hexpatch.sh ro.boot.verifiedbootstate orange
/data/adb/magisk/magiskboot hexpatch /dev/__properties__/u:object_r:bootloader_prop:s0 05677265656e000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000726f2e626f6f742e7665726966696564626f6f747374617465 066f72616e67650000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000726f2e626f6f742e7665726966696564626f6f747374617465
Patch @ 0x000015DB [05677265656e000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000726f2e626f6f742e7665726966696564626f6f747374617465] -> [066f72616e67650000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000726f2e626f6f742e7665726966696564626f6f747374617465]
redfin:/data/local/tmp # getprop ro.boot.verifiedbootstate
orange
redfin:/data/local/tmp # resetprop ro.boot.verifiedbootstate
orange
[Magisk] GN-z11:
View attachment 6052531

I am using my custom build PE 12.1 for my own purposes and did exactly the same to remove Init.rc is modified. Now my mission is to permanently remove that script everytime I rebuild the ROM. And hopefully integrate some bootloader is unlocked bypass once it comes.
[Magisk] DanGLES3:
Hmm, as long as we can guarantee this won't cause an issue I suppose it's fine
[Magisk] pndwal:
FWIW, an LSP associated TG user just gave some context to @canyies comments re. reason for close sourcing MomoHider successor, Shamiko:

... This was a follow-up to the quoted comment from nullptr_dev. (Bolding mine.)

👀 PW
[Magisk] pndwal:
FWIW, for those wanting the official link for Momo, the GitHub page linked in my post above has it... 🤠 PW
[Magisk] ThePieMonster:
How can this be used to pass "strong integrity"? I have the first two passing but interested in the third. I also have Google Wallet working as well.
[Magisk] pndwal:
Can't... Please read OP etc... PW
[Magisk] ThePieMonster:
Seeing some positives 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] GabbyWC:
That's an old post. The exploit shown there is no longer valid as discussed later in the thread and mentioned here.
[Magisk] pndwal:
The original OP said:

Google fixed it...

The current OP is current. 😉 PW
[Magisk] osm0sis:
Since KernelSU doesn't ship magiskboot but every root solution does ship resetprop and busybox, this should hopefully be nice and universal now. 🤘

# resetprop_hexpatch [-f|--force] <prop name> <new value>
resetprop_hexpatch() {
case "$1" in
-f|--force) local FORCE=1; shift;;
esac

local NAME="$1"
local NEWVALUE="$2"
local CURVALUE="$(resetprop "$NAME")"

[ ! "$NEWVALUE" -o ! "$CURVALUE" ] && return 1
[ "$NEWVALUE" = "$CURVALUE" -a ! "$FORCE" ] && return 2

local NEWLEN=${#NEWVALUE}
if [ -f /dev/__properties__ ]; then
local PROPFILE=/dev/__properties__
else
local PROPFILE="/dev/__properties__/$(resetprop -Z "$NAME")"
fi
[ ! -f "$PROPFILE" ] && return 3
local NAMEOFFSET=$(echo $(strings -t d "$PROPFILE" | grep "$NAME") | cut -d ' ' -f 1)

#<hex 2-byte change counter><flags byte><hex length of prop value><prop value + nul padding to 92 bytes><prop name>
local NEWHEX="$(printf '%02x' "$NEWLEN")$(printf "$NEWVALUE" | od -A n -t x1 -v | tr -d ' \n')$(printf "%$((92-NEWLEN))s" | sed 's/ /00/g')"

printf "Patch '$NAME' to '$NEWVALUE' in '$PROPFILE' @ 0x%08x -> \n[0000??$NEWHEX]\n" $((NAMEOFFSET-96))

echo -ne "\x00\x00" \
| dd obs=1 count=2 seek=$((NAMEOFFSET-96)) conv=notrunc of="$PROPFILE"
echo -ne "$(printf "$NEWHEX" | sed -e 's/.\{2\}/&\\x/g' -e 's/^/\\x/' -e 's/\\x$//')" \
| dd obs=1 count=93 seek=$((NAMEOFFSET-93)) conv=notrunc of="$PROPFILE"
}

Plus it also now resets the serial counter that some apps have started to detect as resetprop tampering. 🤠

Thanks to @DanGLES3 and @arda99 for the help deciphering the prop format. 🙌
[Magisk] christantoan:
Another one detecting root. It works in the past. I'm passing Device and Basic Integrity and have tried renaming xlua folder as well.

DANA Indonesia Digital Wallet - Apps on Google Play

A digital wallet (e-Wallet) for all cashless & card-less transactions

play.google.com
[Magisk] QuenTeZia:
Sadly strong integrity didn't pass on my device (poco x3 pro)
[Magisk] DougMG:
No one passes strong integrity. It was a briefly exploitable workaround for the pixel 2 broken keymaster which was patched server side by Google shortly after it was taken advantage of.
[Magisk] pndwal:
Ok, there are several reasons for failing basicIntegrity...

Can you run Play Integrity API Checker check to confirm device meets DEVICEINTEGRITY?... If not, then click < > symbol at top to view Raw JSON response and send screenshot...

Next, can you re-install PIF, run Play Integrity API Checker check again, then click < > symbol at top to view Raw JSON response and send screenshot?... If labels are unevaluated @chiteroman may be able to determine why it's happening... if not, there may be a module conflict or other issue...

Interesting that @chiteroman PIF isn't working for you on Pixel 7A while @Displax USNF 2.4.0 mod 1.3 works... PW
[Magisk] pershoot:
All was ok in API Checker initially (excluding strong, which is expected). No other modules were in place. I did install Shamiko, much much later, but tap to pay setup was already in error well before then. I'm uncertain if Shamiko was also compounding the operability with PIF, when I re-checked with it and noticed error.

When I get some time I'll see if I can re-test (unless someone else with a 7a can re-validate findings). It takes quite a number of hours for things to reset and cannot go and flush things out at this current time as there's much setup involved (adding cards, validating / confirming, etc.).
[Magisk] ykjae:
Not pixel 7 but I'm pixel 6 pro (raven) passing device and basic with latest pif module.

Google pay works perfect - only thing not working perfect at the moment is Microsoft Apps (Company Portal)

I've tried every varient of PIF & USNF.

MOD 1.3 seemed more stable and now the latest PIF is doing fine. I've been on the latest PIF since release.
[Magisk] sawdoctor:
I believe this method is still working for Microsoft

[Tutorial] [Root] How to configure 'Microsoft Intune' to make it work with 'Magisk' (Update: Q3/2023)

Update 04.01.2023: I've added shamiko magisk module to make this tutorial work again. Update 19.07.2023: Some were able to make it work by cleaning the data of Google Play Store and Google Play Services. Added. This question was asked many times...

xdaforums.com
[Magisk] ykjae:
Nope not for me and most others it seems. Some say they can downgrade to July variant and it works but not for me I've tried.

I've been using shamiko and HMA for a while so I can almost say it's 99% not just a small user error I'm making.

Some say magisk alpha works.. Nope. But I got it working by turning off MAM activities. My posts are in there regarding how I got it to work - which credit does not apply to me.
[Magisk] pndwal:
Can you say whats changed? 👍 PW
[Magisk] chiteroman:
Different compiling way + shadowhook is back.
[Magisk] shoey63:
No problem on ROG 3 with Omnirom 13
[Magisk] rctempire:
Thanks for this. Still cannot get the app was needing but thats more a device issue im sure.

OnePlus 8T

But this works and is a key additional mod now.
[Magisk] spida_singh:
I'm using Alpha, plus Shamiko alpha on the latest intune

As well as this latest integrity fix and it runs all ok.

No need for lsposed/ HMA

Using lineage on a pixel 6
[Magisk] zgfg:
Not working on my Xiaomi.eu 12.5 -previous versions worked

CTS fails, showing HARDWARE Backed attestation

And indeed, logcat | grep SNFix

does not catch anything
[Magisk] zaksdk:
I have installed your module only on my infinix ZERO 8 (X687) but I am yet to passed strong integrity
[Magisk] simpleatom7:
You can't pass strong integrity. You don't need to. It was exploitable for a short period of time & then it got fixed from Google server side.
[Magisk] mihalis1983:
Hello,

I can't pass Device Integrity. Also not play protect certified.

Poco F1 - Miui12, A10

Magisk Alpha (26301) + Shamiko (latest alpha) + HMA.

Tried all Play integrity fixes 8.5, 8.6, 8.7, all USNF and mods 1.3 & 2.0, nothing worked. JSON attached.

Any help?
[Magisk] pndwal:
That's not really failing verdict; Unevaluated indicates network or other issues including 'trustworthyness'...

You could try disabling Addaway, VPNs, firewalls etc if you have em to test... I suspect it's mor than that however.

Re. 'Unevaluated' responses, these can mean:

So there's likely abnormal issues with your device causing it not to be trusted; Unevaluated accountDetails and/or appIntegrity apparently results in empty deviceIntegrity result... No deviceRecognitionVerdict is called so you're not getting either Hardware or Basic Evaluation for PI API, just a failed response...

I've had LSPosed modules that cause this, eg early versions of @chiteroman's BootloaderSpoofer XPosed module did this on some devices incl. mine... Nb. current version doesn't do that for my device now... So you may want to try with selected (or all) Magisk and XPosed modules disabled...

Some have needed to install full unpatched ROM to restore device trust for these verdict labels if they messed with system... You could try a dirty flash to keep data, and if that doesn't work try a clean installation... I know flashing full stock ROM clean has fixed this for others

Being a Poco device also raises alarm bells, especially if this occurred after having custom ROMs installed etc... (I think these users usually had basicIntegrity however, so your Unevaluated issue may be a different one...) These cases involve having messed up /persist partitions and even restoring stock ROM images and relocking bootloader doesn't restore integrity verdicts in these cases, but is usually accompanied by other (mobile network, WiFi etc) issues...

If you think this may be your issue, hopefully you backed up this unique partition for your device earlier... Generic persist images in ROMs don't have unique IMEI, Mac, BT, WiFi numbers etc)... There are other ways to fix this however depending on device...

Please see comments/links I put in a thread reporting a similar issue in poco device (and note the thread title):

- https://xdaforums.com/t/cts-fail-even-with-locked-bootloader.4613007/post-88837771

- https://xdaforums.com/t/cts-fail-even-with-locked-bootloader.4613007/post-88839819

Do your due diligence... I'd try the second suggestion before flashing /persist (unless you have a backup from your device as this will include unique numbers unlike the generic /persist image in ROM), especially if you've never actually messed with that... (Nb. Seems issue can occur simply due to downgrading directly from A13 to A11 or similar... Go A13, A12, A11 etc).

Hope this (or clues above) helps... 🙂 PW
[Magisk] iruiz2:
You are using several modules to fake your phones ID. Do you pass Device Integrity after turning them off and rebooting? I would try that first
[Magisk] EuK_V:
So, how do we use it?

P.S.: Looking at the script and miss the times when we just needed to root the phone and install supersu app..
[Magisk] osm0sis:
It's a function, so you can paste it into a shell and run it with the command, but it's more for me and other modders to use in modules. 😛
[Magisk] EuK_V:
Ah, I see..

Is there a new ver. of the module to test?
[Magisk] HippoMan:
View attachment 6052745

I did it!!!!!
[Magisk] osm0sis:
Not yet.. 😛
[Magisk] nek46:
Thanks for the play integrity fix all ok :) hide gpay and some app (y),device htc u ultra rom lineageOS android 12

@Retrial big thanks bro for the info :)

​
[Magisk] huskydg:
@osm0sis https://github.com/HuskyDG/system_properties/commit/f86fe18e365a31e4970bb444cc836524608ba449
[Magisk] linuxares:
So we need to over to Magisk Delta now then? :P
[Magisk] uschipower:
I am using @AndyYan's LOS 20 Treble GSIs, because it's the only opportunity go get a maintained Android on my Lenovo-devices.

When using Treble-GSI, only system partition is replaced. Every other partition is remained from manufacture stock rom (of course /boot have to be modified)

In these images, it seems there is no file "install-recovery.sh" at all. If I search from / over everything, no such file appears.

I am also using chiteroman's Bootloader spoofer, and also no shamiko (shamiko 1.0.290 doesnt work together with Kitsune Magisc at the moment)

My situation:

View attachment 6052862

View attachment 6052865

You see, addon.d is renamed, install-recovery.sh doesnt exists, but Momo still shows custom rom.

I suppose it's because of the fingerprints.

chiteroman's Module PIF and also osm0sis PIF only affects googles GMS. Every other app sees the real values of build.prop

I suppose, official LOS-Images are device-specific - every model gets a own image, right?

So, build.prop can be device-specific with values from stock rom of the device.

A treble GSI Image is universal and is used on different devices.

Is there a tool to spoof values of build.prop for every app, not only for GMS?

I dont understand why the PIF-modules has no option to spoof to every app, not only google.

I think, the developers of Magisk and also developers of modules doesnt respect Treble GSI in their development.

On my samsung SM-T550, I am using a LOS custom rom which is device-specific, from user retiredtab.

You see, Momo shows no custom rom:

View attachment 6052871
[Magisk] purgy:
MHPC spoofs props system wide
[Magisk] uschipower:
I also thought of MHPC, but this mod isnt maintained since 2021.

The intension of MHPC also was to bypass safetynet, so i think it's not a good idea to use both, PIF and MHPC, at the same time.

Because MHPC is not maintained, I think functions should became part of a mod which is maintained, like PIF.
[Magisk] Stillhard:
Indeed

But it's Kitsune Mask now

Download: https://github.com/HuskyDG/magisk-files
[Magisk] osm0sis:
@huskydg

Thanks for your support and effort! 🙌

By the way, I found a flaw in the way official Magisk resetprop writes shorter values currently (I'm on 26404)... It doesn't zero out to the length of the previous value so can leave bytes of the old value behind. 😵

That'll need a patch I think!

Check out unlocked -> locked here:
[Magisk] arda99:
it's OK that's how C String works as the previous \0 terminates the string.

and @huskydg your patch also wipes out the flag byte...should only clean the lower 2 byte or just keep the old serial (remove +1).
[Magisk] osm0sis:
Yeah I know it's terminated still, but the data remaining seems like it could be a bit dirty and potentially problematic if something with system level access were able to check that, DroidGuard for example.
[Magisk] arda99:
I got your point but DroidGuard has TEE already, they don't care about the serial so very unlikely on this dirty byte. Can't say for 3rd party app though, but if we keep the change same length or longer or even 1 byte shorter this isn't a issue, and these cover all(?) props for PIF. Or your script hex patch which cleans all bytes...
[Magisk] osm0sis:
Yeah ro.boot.vbmeta.device_state unlocked -> locked is the only one we use that has a > 1 char difference.
[Magisk] andrew_yousry:
I have a problem with Netflix app on OnePlus 11. it can't connect because of root I think, before rooting it was working. I have your module installed and active but still same problem, any idea how to solve it?
[Magisk] purgy:
Eek idk what happened here, or how to fix it...
[Magisk] Umgak:
Out of scope for this module. You likely fail Widevine DRM, which is a separate thing from Play Integrity and is often lost when rooting/flashing CFW. This module is not meant to help with Widevine and does not help with Widevine.
[Magisk] andrew_yousry:
I'm a noob with these things, is there any workaround to fix it, I tried different magisk modules, like

liboemcrypto-disabler, safteynet fix mod

nothing worked so far
[Magisk] pndwal:
Why?... Looks like resetprop patch can be applied separately from Magisk, and seems Shamiko already fixes these issues for PIF no?...

Well it's still Magisk Delta I believe, just "The Kitsune Mask For Android" instead of "The Magic Mask for Android"...

View attachment 6052929

🤠 PW
[Magisk] Stillhard:
I sensed so much anger, chill out, no race here

[Discussion] Kitsune Mask - Another unofficial mask of Magisk

This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction WARNING! You are using an unofficial version of Magisk that is not officially supported by the Magisk...

xdaforums.com
[Magisk] pndwal:
Anger?! 🤔 NONE my friend!... How do you get that?...

I just like facts and am happy to be corrected!...

To this:

you said:

But Why???

I simply don't agree with that!... TJW Magisk has plenty of life left, and there are ways to work around issues like resetprop detection without jumping ship or herding others off, no?

To be clear, anyone can try forks like Delta/Kitsune, but I'm yet to be convinced that resetprop detection creates a 'need' to do so. 🙃 PW
[Magisk] huskydg:
nullify when update · HuskyDG/system_properties@696d83e

Contribute to HuskyDG/system_properties development by creating an account on GitHub.

github.com
[Magisk] osm0sis:
Brilliant! I believe @arda99 is right about the flags byte too, if you could avoid zeroing that.

👍
[Magisk] Vision:
Yeah, just typical i think
[Magisk] linuxares:
Just asking. Not sure what these sysprop fixes for PIF.

Can someone eli5?
[Magisk] Hybrid Divide:
Well, unless I've done something wrong, the LG V20 fingerprint doesn't work. Passes basic, but not device.

Extremely frustrating. I did notice that the LG V20 build.prop does not have a value for "VNDK_VERSION".

Could that be what's holding me back here? Pixel Flasher loads a value of 30 when the box to add missing keys is checked.

Any insight would be appreciated.
[Magisk] sawdoctor:
Some fingerprints just won't work simple as that. Just Google android devices that updated to Oreo and then look for android firmware dumps on gitlab. Grab a few build props and then test. Probably 1 in 5 will work from Oreo firmware
[Magisk] Vision:
For anyone confused about new Kitsune, because of the old logo, i have some suggestion for @huskydg logo here

Correct information about Logo · Issue #63 · HuskyDG/magisk-files

@HuskyDG I modification again your logo, same icon with my previous and same fonts, i chance it like this because in xda lot of user confused about the the name because the logo and in the README.m...

github.com
[Magisk] Vision:
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] HippoMan:
In traditional Japanese folklore, there actually is something called a "Kitsune Mask".

http://www.historyofmasks.net/famous-masks/kitsune/

"Kitsune" means "fox" in the Japanese language, and in those folklore traditions, the fox can be either a bringer of good or of evil, depending on the context and the situation.

I like this "Kitsune Mask" name for "Magisk Delta".
[Magisk] ipilcher:
Nope
[Magisk] Vision:
Yeah, i read on internet about the legend of kitsune, for that i use this font for the logo, is little spooky

Updating Logo by VisionR1 · Pull Request #17 · HuskyDG/magisk-files

Hi, i add more lively color in fox face, little bigger and i changed the font with more match font for Kitsune (i read what mean), is same dimensions 1500x599. If don't like it just ignored

github.com
[Magisk] pndwal:
Check what that legend has done here:

Post in thread 'Magisk General Support / Discussion' https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-89264381

☹️ PW
[Magisk] Vision:
Bad, and the word "legend" i mentioned for the Kitsune not the person, i read the story what mean, for that use the word legend
[Magisk] pndwal:
I've seen some of his foul mouthed rhetoric before... Hadn't seen those particular comments however... So legend of Kitsune, along with poisonous PixelProps dev etc seem to have killed Shamiko, LSPosed and ZygiskNext for all of us...

Really hope it's an idle threat, or that they rethink for general Magisk modders sakes... ☹️ PW
[Magisk] Vision:
Yeah understand, is bad for our community, we try to do the best the dev etc. and not bad thing
[Magisk] tom1807:
Not sure which model of the LG-V20 you used, but my FP from the V20 has no problem.

Maybe can discuss this private.

Cheers

Tom
[Magisk] sawdoctor:
So few genuine modders/Devs left we can't afford to lose any more.

If you don't like shamiko lsposed alpha etc then just don't use them simple as that. Don't go giving foul mouth abuse to someone who is giving you something for free.

Is there anyway for us to show our support to them and let them know how we feel
[Magisk] poulopoulosa:
I saw a lot of stuff and it is really hard to understand what is happening with all this noise.

From my understanding it seems that a guy who pretended to be the original creator started swearing at LPosed developers?

Also I read somewhere that people who steal OpenSource code have been claiming it is theirs and they are injecting malwares and all sort of other malicious things...

Maybe what I am saying is really silly, but it does prove Google right as to why they don't want to have modders use their Payment/Banking systems...
[Magisk] TotallyAnxious:
Donations are support. Whether it's asked for or not. Check dev pages for donation links. Even a small amount. This is the easiest thing a non dev can do to support a dev.

If you're well versed in android. Help debug and try to join private testing groups, devs do have those.
[Magisk] sawdoctor:
I get all that and regularly donate, test and occasionally develop/release things

I was more talking about this particular incident and to let them know the vast majority of us appreciate thier work and want them to reconsider their decision
[Magisk] TotallyAnxious:
I wasn't implying you don't offer support but you raised a question I bet many of the newer people here have and might be unsure of how to ask. So I answered it.

But I'm sure donations coming in right now would encourage these devs to not give up.

So if someone who knows the dev pages of all these devs. Wanted to post them here or somewhere in the magisk threads, I'm sure people would donate as more people become aware of the stuff going on today.

I personally don't know every dev involved in today's news, as I just use osmosis fork and official magisk. I know some of the lsposed, zygisk next, etc devs do contribute to magisk development.