yashsingh1/xdaforums huggingface dataset:
[Android Software Development] 73sydney:
Feature Request for native magisk manager superuser/deny list backup and restore added to Magisk Repo Issues here:

[Feature Request] Native Backup And Restore Function For Superuser and Deny Lists · Issue #6543 · topjohnwu/Magisk

As someone who has at times tested up to 5 ROMS a week in times past, having the ability to easily backup and restore the contents of the Superuser and Deny lists are an obvious timesaver, and so i...

github.com

(i borked the first issue request by not filling out the template properly :) )

Lets see how far we get...

A reminder we take no bets on the outcome, or how spicy it may get

Please, no wagering
[Android Software Development] kaefers:
I tried out Hide My Applist - unsual results ?!

In HMA, made a template, added banking, google wallet, detection apps just as per tutorial..

1)

Using recommended settings for HMA in LSPosed (System Framework) and selected all for XPL (sans Google Play Services).

Ruru detected Dev Mode and XPL/TWRP only, everything else is Not Found. YASNAC and Integrity Checker are passed (sans strong integrity). Banking app, google wallet etc work just fine.

2)

Now, when selecting Google Play Services within XPL within LSPosed (i.e. selecting all for XPL within LSP):

- Ruru unchanged (all good aside from stuff mentioned above)

- YASNAC & Integrity Checker failed

- Banking app & Google Wallet are STILL WORKING w/o complaints ... ?!?!?

==> I don't know why that is, how all LSP, Shamiko, USNF, HMA, Google Play Services fit together, but I now seem to have SafetyNet and Integrity Check failed but my banking app and Google Wallet working just fine. Might fail with some other apps, but just installed Netflix and no complaints (applied HMA and XPL).

Will see if I can try some other apps, suggestions welcome.

I wonder if any improvements to how all this works could be derived from the above.

If XPL (eventually) fails with GMS, might have to go to AndroidFaker & AppOps or something...

--

N.B. Having to tick "all apps" for XPL within LSP is correct, based on these:

- https://github.com/M66B/XPrivacyLua

- "LSPosed: please make sure that any app you want to restrict is in the 'scope' of LSposed."

- "Some obsolete modules need to inject into each app. It's so dangerous that LSPosed doesn't support Select All and requires the user to tick each app one by one manually (the same policy as Magisk Hide)."

--

I cannot judge the "obsolete" bit wrt XPL, idk if there'd be a different way for XPL to work, but at this time, it seems to need to have a tick for GMS within LSPosed in order to manage permissions...
[Android Software Development] 73sydney:
Sadly from memory theres not a lot of XPL discussion in recent memory, and thats not because its necessarily off topic, i just dont remember seeing much discussion of it in the recent past.

But youre going to get a big thumbs up on 1) because thats what we consider totally normal (not withstanding the TWRP detection which as mentioned you can resolve by renaming the folder on internal storage and hiding XPL in HMA)
[Android Software Development] kaefers:
Hoping AppOps will be a bit more like XPL in the future in terms of UI and live permission requests / notifications. I guess I will try these out once more as possible (partial) replacement to XPL.

GitHub - Xposed-Modules-Repo/com.android1500.androidfaker: Android Faker

Android Faker . Contribute to Xposed-Modules-Repo/com.android1500.androidfaker development by creating an account on GitHub.

github.com

& https://appops.rikka.app/

OR https://github.com/mirfatif/PermissionManagerX ...

I doubt I will change my opinion wrt to restricting GMS anytime soon.

N.B. XprivacyLUA development has apparently just ended Dec 2022, M66B post #1 & M66B post #2 ... :/

F
[Android Software Development] 73sydney:
Update

Well that issue remained open longer than i expected

The only reply to it said this:

cp /data/adb/magisk.db

and it was closed as "not planned"

Got to love the effort put into communication over there
[Android Software Development] ipdev:
You gave it shot.

At least you got two GitHub idiots to give your request a 👍 before it was closed. 🙃

Most other apps have a backup/restore setting (configureation) options why the hell would Magisk even think of including it?

I mean it is half the fun of testing roms when you have to take 15 minutes or better to configure Magisk. Just so you can test one change and then wipe the device and start clean again. 🤪

Not to mention that will only work if the Magisk database is not corrupted and/or compatible with the new version of Magisk, rom and device.

I would love to see them copy (restore) a Magisk 23 database to a Magisk 26 install cross device and see what happens. 🙃

View attachment 5813011

Cheers. :cowboy:
[Android Software Development] 73sydney:
I did reply and point out the history of magisk.db schema changes in the past, and that a flat file backup option was perhaps safest.....

And this idiot appreciates the support of the thumbs up folks over there

Yo, vvb

Let's kick it...

Spice spice baby

Spice spice baby

All right stop, and give me a tissue

You burned me for submitting a new issue

Something that seemed quite easy and sane

And not a lot of that comes from my brain

Will it ever stop? Yo, I don't know

Or will those github issues continue to grow

Its extreme that you close them with no mention

And yet you seem to wonder why theres tension

And i think thats about all im going to rewrite of that song..i think my point is rather made :)

Further new update after subimitting my rational reply to their first knockback:

"After asking internally, we have no interest in implementing this feature."

To be fair thats punching above the usual reply.....
[Android Software Development] ipdev:
I did not refresh the github issue to see your reply. 🙃

This github idiot just gave you another 👍

Maybe we need pndwal to explain why the request is valid. :unsure:

Cheers. :cowboy:
[Android Software Development] 73sydney:
Cheers, and ....as for @pndwal:

I mean thats who i'd send in to REALLY drive any point home to anyone :)
[Android Software Development] 73sydney:
Just for a bit of levity because apparently while i had decided the cause was lost, another sound post has been made on github....

Recently i acquired a Streamdeck XL, not because im going to start my own channel, but as a monitoring and productivity tool, but well, i did decide id set up a few sounds for zoom chats, and im just setting this back up after a windows reinstall after some troubleshooting malarkey with Elegato folks and so far i have my two most crucial buttons linked to sound effects

the bottom left i like to use this even offline because it makes me feel like life is a show here

the one next door to it for moments of suspense (dun dun)

View attachment 5813091
[Android Software Development] m0han:
We get it; when push comes to shove, he always stands up for you.
[Android Software Development] mrjuniork:
You gotta be kidding me 😅
[Android Software Development] Ingenium13:
I was previously using the Displax mod, which caused my Pixel 7 Pro to be reported as a Nexus 5 everywhere. I updated to the 2.4 version of kdrag0n's module, which claims to not require spoofing the fingerprint permanently. However my phone still reports itself as a Nexus 5 (such as on the About screen, and in the EXIF data on photos, etc).

Is this the intended behavior? Or is 2.4 supposed to bypass this and allow the phone to report as Pixel 7 Pro?
[Android Software Development] topecorm:
Oneplus 8 LOS 20 + microg (through Lsposed and Fakegapps) in the Deny list:

- Regular USNF 2.3.1 and 2.4.0: CTS doesn't pass;

- Your mod very 2.3.1: PASS!

Thank you, keep it going!
[Android Software Development] geokilla:
Seems that SafetyNet 2.4.0 breaks chat features in Google Messages. Removing it fixed it as does reverting to 2.3.1. Currently using a Pixel 7 on Statix ROM.
[Android Software Development] 73sydney:
fwiw no issues here after literally just updating (finally) to test 2.4.0

Including Messages

I am running stock Pixel 6 Pro ROM though,,,, :)
[Android Software Development] 73sydney:
@osm0sis ....

Okay, i might have been too hasty there folks

Because i just went to recharge my Pixel 6 Pro and could not get it to recharge

Sitting it on my wireless charger freaked the charger out, started to do the usual charge LED colour, then went Red, then turned off completely(never done that before), which i believe it only does if it detects a temp overload, sure enough phone was very warm

Rebooted phone

Plugged in via USB... in Battery Guru it would briefly go to Charge tab and languish below 200mA and then switch to the Discharge tab...wtf?

Changed 3 cables (all known good) same result

The only changes i made today: update USNF and HMA

I just reverted to USNF 2.3.2 Mod 2.1 (Displax) and we're back charging again, im like wft?

Hmm.......

Meanwhile my phone has jumped from 15% to 19% in the time its taken to write this

2.4.0.... that defs got issues it seems
[Android Software Development] rodken:
Did you uninstall USNF 2.3.2 before the upgrade or did you flash the newer version of USNF on top of the older version?
[Android Software Development] 73sydney:
should it make a difference?

@Displax s were always designed to flash directly over the top of official - both have same ID - i would assume any relevant files would overwrite
[Android Software Development] rodken:
I ran into a similar scenario and had to completely uninstall, reboot and flash the newer version of USNF

-- Afterwhich, I rebooted 3 times with 5 minute intervals, crossed my toes and said a prayer to the USNF Gods.
[Android Software Development] 73sydney:
Looks like the only file difference is kdrag0n is using different zygisk files and entries in system.prop

The files should safely overwrite each other, unless im missing something ....

I did like 5 reboots in my recharge test to make sure it wasnt a one off event :)

p.s. Pixel 6 Pro is now at 30%, nice to see it not suck battery out In the (from of a rapid rise in heat) when plugged into the charger, thats a first for me :)
[Android Software Development] zgfg:
Aren't the main differences not in the visible scripts but in the native code compiled for the zygisk folder
[Android Software Development] 73sydney:
Yup, and those are replaced when you install one over the other, no?

Unless im wrong :)

p.s. edited my earlier post for clarity, only differences are zygisk files and system.prop entries
[Android Software Development] kaefers:
N.B. I have tried out both App Ops and Permission Manager X, again. No comparison to XPL at this time. Neither provides a decent real-time permission request for all apps overview like XPL Pro, and it's a lot more effort to get things set up vs XPL ([lack of simple] tickboxes, auto-save settings per app, color coding etc), having the app constantly revert permission changes etc. A bit clunky :)

Someone better fork and continue with XPL dev, please 😥
[Android Software Development] MoL_82:
Is it ok to use TaiChi? In this thread it is advised not to use it.

https://xdaforums.com/t/warning-do-not-use-taichi-any-way.4012681/
[Android Software Development] doclucas:
Yeah, Paypal's app fingerprint/biometric login also doesn't work when enabling the safetynet-fix. Disabling it restores the biometric login.

@kdrag0n is there any way to fix this?

p.s. Tested on Galaxy Note 10 Plus N975F with Android 10 and either safetynet fix versions 1.0.2 and 1.1.1, without using MagiskHideProps

Magisk version 20.4 and Magisk manager version 8.0.7
[Android Software Development] Pippolepippa:
Rebounding on doclucas' post: on Samsung S10, biometrics do not work either in 3rd party with this fix. Two things I noticed that could maybe help figure out why:

1) after enabling the fix, one of those 3rd party apps said "the fingerprints have changed, enroll again" or something like that.

2) I've noticed in the system.prop file in the fix's zip that ro.boot.veritymode and ro.boot.vbmeta.device_state are set (to enforcing and locked). However, if the fix is not enabled, getprop returns empty for those properties. @kdragon, are these needed? What if I remove those lines from system.prop?
[Android Software Development] Abolfazl:
Installed Universal Safetynet Fix v1.1.1 on my Pixel 5 with MagiskHide Props Config v5.4.0-v114 installed (did not change fingerprint or anything) and it works great!
[Android Software Development] Deny.Kr:
Module is working passed for CTS profile check and it means fully working Google Pay app, but I've the same problem as guys.

After installation in my internet banking apps (in Czech Republic it's George from Ceska Sporitelna and CSOB app) don't working fingerprint login. In George app after I try to set it again, app will freeze. George key app (for confirmations of paynment), after I try to set it again, is asking me for PIN confirmation. After that it answer me that PIN is incorrect (but it is right) and it not possible to set the fingerprint again..

CSOB app tells me that fingerprint is not able to settings.

After I deleted this module, everything works corretly again..
[Android Software Development] hromanse:
Hi. I have a same issue like my friends from Česko. On my mBank app it says something like Biometric is not activated.
[Android Software Development] tygger:
I'm getting the same error message when trying to install the Safetynet-Fix module on a Moto E6 on Android 9. Everything worked fine on a Pixel 2.
[Android Software Development] zgfg:
Forced Basic was removed from MHPC, latest v5.4.0 (screenshot), since it cannot force anymore
[Android Software Development] KineSight:
I noticed and didn't update the module.
[Android Software Development] zgfg:
Ok, but there is no point of using the defunct option

Why don't you disable and test with USNF alone
[Android Software Development] KineSight:
I went to do just that after replying to your comment. When I flashed the latest version (v1.1.1.) it gave me a bootloop - I flashed this version now and it seemed to work fine and pass and make it basic.

I will retract my previous comment.

Thank you.
[Android Software Development] nampud:
I managed to fix the 3rd party app fingerprint issue on my Samsung w/ Android 10 (commented on this Github issue too). Basically the AOSP keystore is not fully compatible with the Samsung one so I decided to binary patch the one on my phone and ended up with this module. Now both fingerprint and SafetyNet works.

Notes:

- This disables key attestation for every app, idk if it breaks anything, nothing broke so far

- Only change is the replaced system_sdk29/bin/keystore with the Samsung one (8 bytes modified)

- Only works on Android 10

- Might or might not work for you, use at your own risk.
[Android Software Development] KineSight:
I've tried this on my A20 - OneUI 2.0 A10. Its working perfectly. Fingerprint and Basic Attestation. Thanks 💯
[Android Software Development] Pippolepippa:
Thank you @nampud , I confirm this works on Samsung S10, Android 10.
[Android Software Development] Deny.Kr:
Guys, how did you do it? I understand where to find Keystore file, but how to edit it to 8 bytes? I didn't find anything for Android, or PC, that can edit it..

Thank you.
[Android Software Development] MoL_82:
Thank you! This works on a Samsung S9.
[Android Software Development] wyt18:
works great for me on s9 stock oneui 2.5. third party biometrics work, as does GPay. thanks for your work!
[Android Software Development] Yahoo1:
I have Pixel 2 XL on Android 11 with with Magisk 21.4, MM 8.0.7 and latest USNF 1.1.1 module and George banking app is working for me just fine as well as other banking apps.

Do you have Magisk Manager hidden as well as George app checked in MagiskHide? I have in MagiskHide also GPay and Google Play Services.

In this configuration everything works fine for me.
[Android Software Development] Deny.Kr:
I've Galaxy Note20 Ultra 5G and it doesn't work.. I don't understand how guys modify keystore file and combination of this fix is not working on my device although I have checked all apps you're write in MagiskHide..
[Android Software Development] Pippolepippa:
Deny, you need to use @nampud 's version of the module, found here https://github.com/kdrag0n/safetynet-fix/files/5846085/safetynet-fix-v1.1.1-samsungmod.zip

However, this will only work on Android 10 (at the moment). My understanding is if you use another android version, your particular keystore would need to be patched. If that is the case, maybe @nampud can tell you how to do that...
[Android Software Development] ipilcher:
Working well on my OnePlus Nord N200 (dre) with LineageOS 19.1.

I can finally get the American Airlines app to authenticate. (Now can someone please tell me why in the name of all that is holy my device should need to pass a SafetyNet attestation in order to run an airline app?!)
[Android Software Development] 73sydney:
Does the American Airlines app in any way deal with transaction or in anyway perhaps link into secure systems that perhaps access details of things like bookings and customer details?

If yes, then theres your answer...the name SafetyNet or its successor Integrity Check at this point should be rather self-explanatory

Had to laugh last month when a banking app wouldnt run because it detected Teamviewer on my phone
[Android Software Development] osm0sis:
Interesting... I'll revert and see if that helps any of the issues I had been chalking up as Lineage 20 and MindTheGapps 13 being janky. 😲
[Android Software Development] m0han:
The 'Riru' version presented a serious issue and I had to remove it.
[Android Software Development] 73sydney:
@pndwal

Do you think its too soon to put in another issue in over at Magisk github?

.....Asking for a friend
[Android Software Development] Displax:
Oh those nostalgic memories...) The endless war continues ;)
[Android Software Development] evtoofly:
2.4.0 working successfully on my pixel 6a. Passed device and basic integrity,and can download Netflix and use gpay if needed. Thank you
[Android Software Development] pndwal:
... Though you were joking... Now I'm not sure. 😜...

Why?... Do you think there could be GitHub a cooling -off period?! 😹 PW
[Android Software Development] 73sydney:
No, i was 100% joking

I dont go looking to invite drama into my life that much :)
[Android Software Development] pndwal:
@zgfg, anyone...

Did you say somewhere you don't currently need prop changes to get BASIC Evaluation type in YASNAC on your late/up-to-date device?...

I'm trying to get HARDWARE_BACKED Evaluation type to show on either of my two Xiaomi unlocked devices (neither have needed model prop based enforcement bypass but need broken keystore based fallback for S/N Basic evaluationType) ATM...

This should be as simple as disabling USNF on devices that enforce hardware-backed attestation, and should also occur on mine by disabling USNF and using MHPC to fully simulate a device that enforces hardware-backed attestation (as achieved by @ipdev historically)... However I can only ever get BASIC Evaluation type in YASNAC!?...

I'm now wondering if Google has changed something again recently...

Which devices still need old model prop based enforcement bypass for Basic attestation / passing S/N or PI device integrity verdicts? Any?

Thanks! 👍 PW
[Android Software Development] zgfg:
I never achieved (and never expected) Strong-Integrity or Hardware CTS - only the Basic CTS and Device Integrity as on the screenshots

And for them I don't need and I don't use USNF (if I do, I have no benefits or artefacts) but I run Xiaomi.eu custom ROM (A12/MIUI 13 from Nov) that has USNF spoofs integrated (and it passes the same right away with BL unlocked - but of course, if you install Magisk then just additionally putting GMS to MagiskHide or DenyList is again enough to spoof SN/PI)

Same CTS results with Magisk TJW or Delta

--

That was always the case for Xiaomi.eu. As a custom ROM it requires the unlocked BL. But then, devices would appear not certified and users would have generally troubles elsewhere.

With the integrated spoofs, ppl can normally use Playstore, Wallet, banking apps, etc (only those who install Magisk must additionally hide Magisk)
[Android Software Development] pndwal:
I think you've missed my point, but thanks... I think it was your integrated SNF I mis-remembered... So you can't test this easily...

Can anyone else give any device that currently shows HARDWARE_BACKED Evaluation type in (old) YASNAC app after disabling USNF and rebooting?... Thanks, PW
[Android Software Development] zgfg:
No, I cannot test to achieve Strong Integrity - I have no intensions to go to stock and lock the BL

Never in my life passed Hardware CTS - since I always unlock the Bootloaders 😁

And I don't have devices with broken Keystone or so
[Android Software Development] pndwal:
I'm not sure what you think I asked, but it's NONE of those things...

I just want someone with a late/up-to-date device using Magisk and USNF (not integrated SNF) to disable USNF and say if they see BASIC or HARDWARE-BACKED Evaluation type in YASNAC app since I'm wondering if Google has reverted model prop based hardware attestation enforcement recently...

... don't want anyone to flash stock, lock bootloader, try for passing strongIntegrity or try on devices with broken keymaster implementation!??... Not sure why you thought that... 🙃 PW

Edit: Perhaps you thought I meant passing strongIntegrity verdict when I simply said S/N HARDWARE-BACKED Evaluation type ???
[Android Software Development] GT500x:
I'm having a weird issue whereby I pass the MEETS_DEVICE_INTEGRITY and CTS Profile checks sometimes but not other times. It's reflected in Google Pay/Wallet as well that it sometimes tells me my device is incompatible due to root, etc, and other times not. The pattern I've noticed is it passes right after the phone boots. If I leave it alone for a while, say 20 minutes, and run either YASNAC or Play integrity checker both fail those checks but if I then wait 20-30 seconds and run either or both tests again they pass again. This behaviour is pretty consistently reproducible: wait 20-30 minutes, fails, wait 20-30s after failed test and then retest, passes.

My device:

- LineageOS 20 on a Oneplus 8 Pro

- Magisk 25.2 with just Wallet in the DenyList per the other posts I've read here.

- Enforce DenyList On

- Universal SafetyNet Fix v 2.4.0

I've tried with/without Shamiko, with/without enforce denylist on, with/without GMS in the denylist.

Initially when I rooted I had installed MHPC and set a fingerprint (because it's been a long time since I've rooted and thought it necessary). Then I read here that it shouldn't be used so I reset everything, made sure nothing in props showed "active", uninstalled MHPC. So I don't know if I permanently messed things up by using MHPC or what... Play store reports that my device is certified, if that matters... I've cleared app storage on GMS and Wallet. Nothing I do changes this behaviour. Hoping someone might have an idea.
[Android Software Development] zgfg:
What do you want to say - that some 'late' devices (which vendors and Android versions?) could pass Hardware backed CTS in YASNAC with unlocked Bootloaders (as a prerequisite for flashing Magisk and/or custom ROMs)?

It used to be only for (some) OnePlus phones (if I recall correctly).

Where did you see that for Xiaomi (since you asked me to test) - I'd be interested about
[Android Software Development] pndwal:
I recall some devices suffered intermittent loss of root in the past which may be your root (unintended pun!) cause (USNF etc would fail), but I'm really not sure what might cause this... All best, PW