yashsingh1/xdaforums huggingface dataset:
[Magisk] V0latyle:
So you aren't passing DEVICE_INTEGRITY. This is likely the cause of the problem you're having, has nothing to do with NFC
[Magisk] pndwal:
Curiouser and curiouser...

So do you pass PI deviceIntegrity or not?!?...

And forget Play Protect certification... (Last time I checked it still checked S/N, not PI!... It may be upgraded by now, but is misleading...)...

And why can't you just say if cleared Play Store data?!? (Fifth time)... But don't bother clearing it unless you actually pass PI deviceIntegrity first... (Nb. basicIntegrity pass is NOT deviceIntegrity pass... You need both.)

To clarify, if you clear Play Store data after fixing PI deviceIntegrity you may fix apps not appearing in Play Store that have migrated to PI and require deviceIntegrity pass... This is regardless of PP certification which is why I hadn't mentioned it... PP cert. only affects apps appearing in Play Store on basis of old S/N unless it uses PI now, and I believe it still doesn't, although it might for devices now getting seperate PP services app, but this may still only affect devices w/ A12+. (Those with new seperate PP app will likely need to clear its data along w/ data for Google Play Services and Google Play Store to device certification etc where needed.)

You really need to try to read and understand what I'm saying to you... 🙃 PW
[Magisk] martyfender:
I edited my post above and added what I left out: MEETS_DEVICE_INTEGRITY. No, I did not clear data and cache in the playstore, becauze it shows that the device is certified.
[Magisk] zgfg:
That's why it's better to attach a screenshot(s) when asking/reporting, to avoid confusion and distractions (people try to help but go into the wrong directions bcs the one who reported did not provide precise info, probably bcs he didn't understand himself the details and their importance)
[Magisk] pndwal:
🤪😂🤣

Finally answered (after 5 times!)... But seems you still haven't understood... Please read my post above!... Again...

(Apps using old S/N API will appear in Store if 'Device is certified', as it simply means you have CTS Profile Match, but it makes no difference to apps requiring PI deviceIntegrity verdict!!!; Clearing Play Store data fixes both S/N and Play Integrity dependant apps not appearing!!!...)

Now that you've confirmed deviceIntegrity, you really should try it... What have you got to lose? PW
[Magisk] martyfender:
the reason I didn't was that I did that a few weeks ago. However, I just cleared a little while ago, and I still get playstore certified.
[Magisk] pndwal:
It's GOT NOTHING TO DO WITH PLAY STORE CERTIFIED... I don't know why you can't understand... Explained the same several times now...

As I just reiterated:

... The operative word is 'may'... If deviceIntegrity has failed at all, apps using that may not appear till Play Store data is cleared... But you'll never know if they would appear again unless you do it! (I'm NOT, repeat NOT speaking about apps still using old S/N API where Play Protect certification is an indication that Play Store tripped flags have been reset properly for S/N... but NOT for Play Integrity!!!)

The app in question is clearly blocked in Play Store by more than S/N CTS Profile match/Play Protect certification failure... Most bank apps are simply requiring PI deviceIntegrity now (which can be fixed as I've said over and over), but it may be that yours is also blocked because of 'hardware limitations' on a per device basis (using model prop? Other?)... I think this would be unusual however...

I'm only really repeating all this at this stage for the sake of other members, but I hope you may finally be able to grasp the concept and divorce Play Protect Device certification from your issue... 😬 PW
[Magisk] m0han:
... along with logs, if/when asked for or deemed necessary. ;)
[Magisk] pndwal:
martyfender

Yup, after you finally said you hadn't and I suggested it for the 6th time, you said:

... And you state "and I still get playstore certified"... Well so what? Did you expect it would suddenly fail???...

What we need to know since clearing the data is: Does the app now appear in Play Store?... You haven't said if that's fixed, and I can only assume you've checked and it doesn't appear... or does it?...

I also gave reasons why it still may not appear... PW
[Magisk] m0han:
There's a new kid in town. Check.
[Magisk] martyfender:
After clearing the data and cache in the play store, the app does not appear. On my work Samsung xcover pro device I used apk extractor to extract the app and uploaded it to dropbox. I then installed it on the Onn 8 1st gen tablet. with Magisk Delta, latest, today. I hid it in the magiskhide list and in hide my app list and then rebooted. I was able to login and access the account with no problems. I did not try to launch the app before hiding to see if it would work without hiding.

Thanks for the support and sorry for the run around as I know you are not a mind reader.
[Magisk] martyfender:
To clarify, other chase apps do show up in the play store. A few months ago I was able to bring it up by clicking on a web link to the chase mobile app.

It stated that it was not compatible with my device and listed the Samsung xcover pro as compatible.
[Magisk] martyfender:
A new beta version of Hide My Applist v3.1.0 was released:

https://github.com/Dr-TSNG/Hide-My-Applist/releases

Fix bugs

Reduce logs when detail logs off

Support system data isolation manage

Don't need to reload config every time when upgrading system service version

Known issues: On some A13 devices, the app may show system service not running after booted sometime, but hide will still work. If changed some config, you need to open app as soon as booted to sync config. We are still investigating this bug.
[Magisk] ipdev:
Not in my town. 🙃

Cheers. :cowboy:
[Magisk] pndwal:
Working in OZ...

Can't you get Eagles 'New Kid' hit on YT in USA at all?... That clip said 'Egles' anyway... Praps they attempted to get past UMPG but failed... 😝

I'd be surprised if a legal egle/eagle like you with an obvious hankering for 70's guitar/California rock doesn't already own it anyway, eh doc? 😜 PW
[Magisk] zgfg:
Btw, Egles blocked even when you use ReVanced (rethinking - probably it doesn't matter)?
[Magisk] 73sydney:
Don Henley now just sits waiting to pounce on anyone posting Eagles links/content, thats his entire life these days

Litigious w_nk_r
[Magisk] pndwal:
Wow... John's 27 today!...

Nice pics of John Wu, Xiaozhen Lin (Googlers) and and Adrian Hsu (working for Elon?)...

Thanks Xiaozhen Lin

https://twitter.com/i/web/status/1609086207086170112

... Some older pics:

👀 👍 🥴 PW
[Magisk] m0han:
Well, he sits up there on his leatherette, looks through pictures of the ones that he hasn't had pounced on yet.
[Magisk] 73sydney:
Let me be the 1st to wish everyone an indifferent turning of a calendar year, essentially a meaningless act and normal progress, from Sydney, where the idiots in charge are burning perfectly good money ($6 million or so), in the sky, because apparently we all have an abundance of money and no country is in a recession or heading that way. All so people can point and gasp at pretty lights in the sky. This is the kind of nonsense Victorian England would do to appease the peasantry of the day to psychologically distract them from the fact theyre were being screwed over and likely to be in servitude their entire lives, and to re-enforce a class system.

Thankfully we dont still operate as a society that way in this day and age...... (sarcasm intended)

I like to pull back the rug on this sort of nonsense, and people ask how i find joy...this is it folks :)
[Magisk] zgfg:
Happy New 2023
[Magisk] xShx72:
Hey guys,

I am currently trying to enable Zygisk on latest stable Magisk, but it just does not turn on. G935F Android 8.
[Magisk] pndwal:
Re. Galaxy S7 edge...

You'll need a custom, ported, fixed or newer Kernel. Notes on (pinned) issue:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-87848951

Nb. This was fixed in LOS 18.1+ using 3.18.140 kernel... Could be a good choice...

👀 PW
[Magisk] HippoMan:
In other words, "Bah, humbug!" by 73sydney McScrooge.

:):):):)

42
[Magisk] 73sydney:
thats more of a xmas reference, but it also demonstrates my pedantry has carried forward to a new year :)
[Magisk] Lughnasadh:
kdragon has released an updated version (v2.4.0) of his USNF mod for his Patreon members. Hopefully will go public in a week or two.

v2.4.0 (early access)​

Repository: kdrag0n/safetynet-fix · Tag: v2.4.0-ea · Commit: 2f18d85 · Released by: kdrag0n

Highlights​

Play Integrity bypass without breaking device checks or causing other issues

Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109)

Other changes​

Updated instructions for newer Android and Magisk versions

Better debugging for future development

It's taken a while to find way to bypass Play Integrity that doesn't require spoofing the build fingerprint permanently, but I wanted to make sure this module doesn't cause any unnecessary breakage. Just like the original goal of Universal SafetyNet Fix, this minimizes adverse effects by spoofing dynamically at runtime only when necessary. Enjoy!
[Magisk] powerman.asdf:
I'd like to buy a new phone, with intent to install LineageOS and Magisk in a secure way:

Magisk in boot.img to ensure occasional reboot won't boot without Magisk.

A way to install LineageOS OTA updates without booting it without Magisk in the middle of upgrade process.

As far as I understand (correct me if I'm wrong, please) to get item 2 working I need phone with A/B, so Magisk app will be able to patch after OTA update but before rebooting into updated version. (BTW, is new "virtual A/B" can work this way too?)

When I look for phones with both LineageOS and A/B support I got just a few dozens, all of which was released in 2017-2018 (e.g. Google Pixel 3). Are there any newer models available suitable for these needs (securely keeping Magisk on occasional reboot and on OTA update)? How can I find out which models are suitable before buying them?
[Magisk] soopx:
So, after getting my phone into a boot loop a few months back by updating Magisk within the Magisk app, and managing to reinstall the boot image with Odin, I want to get root access again. J Michael mentioned at the time that I need to know where Magisk is located. How can I find the location?

Also, do I need to wipe my data to get root access back?
[Magisk] J.Michael:
The thread for your device would be a better place to ask.

Samsung (maybe Google) forces you to wipe data when unlocking the bootloader. When I installed Magisk on my tablet, there was a second data wipe -- I think it had to do with disabling the file encryption.

It may be that you are now free to install Magisk without being forced to wipe data. (Mostly I mean specifically you, because you've done it once. Partially I mean things change, and I assume you will be installing a more recent Magisk than I have.) I just don't know.

If I said you needed to know where Magisk was installed, I meant you need to know/remember whether Magisk was installed in the boot partition or the recovery partition. You say you reinstalled the boot image with Odin, but if you gave Odin the full AP file from the stock ROM, you reinstalled boot, recovery, vbmeta, and others. If you installed Magisk by letting Magisk patch the full AP, I think Magisk mostly patched recovery, with some small changes to boot and vbmeta -- but Magisk is installed in recovery. This is usually followed by a terrible struggle to boot Magisk the first time. Do you remember such a struggle?

In the past few years, some people have found that they can install Magisk in the boot image, even though the install notes say Samsung requires that Magisk be installed in recovery. Again, your device's thread is a better place to find out if other people have gotten away with this. The disadvantage of this approach is that you would have to learn how to extract the boot image from the AP file, patch it, and build a patched AP file. And probably do something about vbmeta. The advantage would be getting Magisk every time you boot, without having to fuss with the buttons.

I wouldn't feel the need to talk so much if you had described how you successfully installed Magisk
[Magisk] Gosbo:
Thanks I will try it!

Edit : it works now I can add card! Thanks a lot, prop of ro.boot.verifiedbootstate is empty now, when I type getprop it returns blank ! Sn helper and playground is green.

Working configuration : Xposed86.2 with module no device check, sr2 systemless, suhide 0.55, latest rootswitch, elementalX

HTC 10 stock rom
[Magisk] Alxoom33:
Yes, you need to uninstall magisk files left in root/data.
[Magisk] G U C C I:
I'm in the same boat. Which files exactly? I've flashed the uninstall zip too and SuperSU is still failing to install
[Magisk] Captain_Throwback:
/data/custom_ramdisk_patch.sh
[Magisk] marcvento12:
Hi. Would be awesome if you can put me the things clear. I have been weeks and weeks trying to install Magisk to disable root for pokemon go. Im a oneplus one user with a cyanogenmod ROM (Sultan). The thing is that now, to be clear, I have a systemless supersu (version sr1 2.78) and I want to use Magisk, or maybe automagisk...what do I have to do?
[Magisk] Captain_Throwback:
Magisk is currently detected by SafetyNet, so don't bother with it right now.
[Magisk] requiiiem:
I do not understand very well, it does not work with Pokémon go?
[Magisk] Captain_Throwback:
No.

And the current version of Magisk also doesn't disable root.

There's an entire thread dedicated to discussing Pokemon Go - look there for an alternative solution.
[Magisk] marcvento12:
Thanks, do you kknow any other solutions?
[Magisk] G U C C I:
There are not any solutions. It was working recently until Google updated the detection method for safteynet. Now Magisk is not working at all and we must wait until it is updated to bypass safteynet.
[Magisk] Captain_Throwback:
You mean there's no working solution using Magisk, right?

Because as far as I know, systemless SuperSU + suhide + RootSwitch still works to bypass SafetyNet.
[Magisk] G U C C I:
Yeah that's what I mean. But I can't get supersu to install. It fails near the end. And whenever I flash Xposed it doesn't show up in the installer.
[Magisk] ss4rob:
Ah - yesterday Android Pay and Pokémon Go! were working (Nexus 6P, 7.1.1.), and today they stopped, and I hadn't rebooted or run any updates. Do you have any further details on exactly what changed, or how Google updated detection without me noticing? I don't think suhide is working with 7.1.1. so I guess I'm out of luck for the time being. Thanks for the info.
[Magisk] Captain_Throwback:
Seems like you should be posting a recovery log in the SuperSU thread ;)

Google updates SafetyNet all the time. My understanding is that it's mostly a server side validation/update, so whenever Play Services updates on your device, it's very possible/likely that SafetyNet is also getting updated. And you wouldn't have any idea it was happening unless you were watching all your active processes all the time :rolleyes:.

There will (eventually) be a Magisk update that passes SafetyNet once again, but as always, that'll only last until Google updates it again....
[Magisk] G U C C I:
How would I go about removing phh's superuser? I have the Magisk uninstaller zip. I want to try the supersu+suhide+root switch method but am not sure how to get rid of phh's superuser
[Magisk] Captain_Throwback:
If you're using the Magisk version, uninstalling Magisk will take care of it (you may have to manually delete /data/custom_ramdisk_patch.sh if present - that may be a Magisk leftover). When you flash SuperSU, it should remove the phh Superuser app for you.
[Magisk] G U C C I:
Do you know if we can use the newest (SR2) version or if we have to use the previous version (SR1)?
[Magisk] Captain_Throwback:
No idea.
[Magisk] fOmey:
Wrong thread.
[Magisk] Tikerz:
Yeah, delete custom_ramdisk_patch.sh if SuperSU fails to install. It's from SuperSU, not Magisk.
[Magisk] soopx:
Ah, thanks for the quick response (and coming to my aid again). Unfortunately, I can't remember exactly how I installed, I was hoping there would be a way to verify. I don't remember there being a struggle to boot it first time. And I know I didn't need to hold down a key combination on startup in order to get root.

Ok, I found this and I'm reading through

How To Root Samsung Galaxy S21 FE with Magisk (No TWRP required) - NaldoTech

If you like to customize your Samsung Galaxy S21 FE and have complete control over its firmware, then the first thing you should do is root it. You can root

naldotech.com

I just booted the laptop I used, and I can see the Magisk APK on there...

Aha! I Can see a boot.img.tar. That means I must have installed it to the boot partition.

Ok, that mystery is solved.

I can see various magisk_patched.....tar files on my desktop. So that means I must have patched it and uploaded to the phone.

I'm fairly confident in this now, but since I haven't uploaded the magisk_patched...tar file this time, I take it it's not installed.

Does this help clarify? Would I need to go through the patch process again now and re-upload?
[Magisk] J.Michael:
I think the most important thing is to be sure you are using the boot image that is part of the current system.

The "patch process" is such a small step, there is no point in skipping it.
[Magisk] soopx:
ok, gotcha - that makes sense. Will the patch wipe data? I guess it's literally just updating the boot partition, right?
[Magisk] zgfg:
Patching the Boot does not wipe Data
[Magisk] Lughnasadh:
Public release now available.

Release v2.4.0 · kdrag0n/safetynet-fix

Highlights Play Integrity bypass without breaking device checks or causing other issues Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109) Other changes Updated instruc...

github.com
[Magisk] TheNixck:
Hello, I need help on choosing which boot.img I need to choose or what to do?

I own a REVVL V+ and managed to get the Stock ROM when I was on the folder so I can patch the img. on Magisk found out that I got two types of boot.img

boot_a

boot_b

I literally researched everywhere but no luck what I can do to get root on my phone?

Thanks.
[Magisk] zgfg:
Intro:

It's about A/B phones with dual slots A and B, introduced (by Google) for seamless OTA upgrades.

Generally, google to find more info about

With the following fastboot commands you can check what is your currently active slot and to switch between them:

fastboot getvar current-slot

fastboot set_active a

fastboot set_active b

fastboot set_active other

(Never force by yourself to switch the slots because on certain phones and ROMs the other slot might not be bootable at the moment - hence you'll cause a bootloop)

By flashing:

fastboot flash boot boot.img

it will automatically flash to the currently active slot

But you can also force to flash to the particular slot, eg slot B:

fastboot flash boot_b boot.img

Btw, if you have a custom Recovery like TWRP, it should also have an Advanced option to switch the active slot

---

Usually, in the ROM zip package there is only one boot.img file that can be applied to both slots or to the currently active one

Hence usually you patch that single boot.img and flash the patched img to your currently active slot:

fastboot flash boot <patched img>

---

But if you really have both boot_a.img and boot_b.img in your zip package, and if they are really different img files (compare their checksums):

Query to find what is your currently active slot:

fastboot getvar current-slot

It will return _a or _b

If eg B (_b) is your currently active slot:

- patch boot_b.img

- fastboot flash boot <patched img>

or equivalently:

fastboot flash boot_b <patched img>
[Magisk] J.Michael:
The installation notes warn against using Odin without specifying a file for each of 4 slots; and against flashing an AP that does not include boot, recovery, and vbmeta. I don't know if those warnings are obsolete.

A stock ROM has two CSC files, CSC.tar and CSC_HOME.tar. Using one of those in the CSC slot resulted in wiping data; using the other did not.

I do not know how you "flashed" the boot image, either to install Magisk, or to recover from your bootloop. If the Odin run included one of the CSC files, you should try to find someone who talks about which will not wipe data.
[Magisk] TheNixck:
Thank you so much!
[Magisk] treier57lol:
Hello, I need some help with spoofing sys.oem_unlock_allowed to 0.

My banking app (Estonian Swedbank app "Swedbank Eestis," package name "com.swedbank") detects sys.oem_unlock_allowed if it is set to 1 and disables specific options in the app (like biometric login). I can confirm that it is sys.oem_unlock_allowed because setting it temporarily with resetprop -n sys.oem_unlock_allowed 0 and deleting the app data allowed me to use the blocked features. The app doesn't complain about root; hiding root with Zygisk works without issue.

However, I am unsure what method I should use to safely spoof this value without bricking my device. Is it safe to use resetprop -n? Does it persist after a reboot? Should I use a different method entirely?

I'm running:

LineageOS 20-20230105-NIGHTLY-kebab on a OnePlus 8T KB2003

Magisk 25.2

Universal SafetyNet Fix 2.4.0

Swedbank version 21440

Passing SafetyNet with YASNAC

I am also spoofing device fingerprint with MagiskHide Props Config to pass SafetyNet.

I really appreciate any help you can provide.
[Magisk] J.Michael:
You said "temporarily". What did you mean if you are unsure whether it persists? Why not reboot to see?
[Magisk] TheNixck:
After I execute the command fastboot flash "patched image" Everything goes ok but at the end it says "

FAILED (remote: 'download for partition 'boot_b' is not allowed')
[Magisk] Lughnasadh:
What phone?

Is your bootloader unlocked?
[Magisk] Arealhooman:
They are re scared it may brick or otherwise harm their device.
[Magisk] zgfg:
Isn't your prop sys.oem_unlock_allowed

about Developer options / OEM unlocking enabled or disabled
[Magisk] TheNixck:
I own a REVVL V+

More info: https://xdaforums.com/f/t-mobile-revvl-v-5g.12393/

No I haven't unlocked the bootloader I had tried but is a hot mess you install programs and I'm unsure which to install, can you link a video to how to unlock the bootloader for Android 11?
[Magisk] Lughnasadh:
Then you got that error because your bootloader is locked. Go to you device forums to find out how to unlock your bootloader and ask questions there.
[Magisk] zgfg:
Fastboot does not allow flashing if Bootloader is locked

Procedures for unlocking Bootloaders depend on the phone vendors.

There might be a page where you have to register and request to unlock your BL.

And/or, there might be tools provided by the vendor needed for unlocking your BL.

In the worst case, you might need to pay for hackers to unlock your BL

You need to google about the specific procedure for your phone.

And be aware that you may loose the warranty once you unlock the BL
[Magisk] treier57lol:
Yes, that's why I came here to ask in the first place. I want to be sure that it doesn't brick my device instead of being a guinea pig and just going for it blindly. Surely someone smarter knows what will happen ahead of time and can warn me from a potential brick.

Yes, the sys.oem_unlock_allowed prop should be the same as Developer options -> OEM unlocking.

Again, I don't want to actually disable OEM unlocking because that's dangerous, I want to spoof it so I can use all the features of my banking app. It's just the how part that I need help with.
[Magisk] zgfg:
You may use Magisk Hide Props Config (MHPC) module to spoof a prop

Since it makes only the systemless changes, when you boot without Magisk or with MHPC disabled, the prop should be back to 1

Moreover, when you reboot to Fastboot, prop should be also set back to 1 (since you are not booted to Magisk with the MHPC module)

Search for another thread about the MHPC
[Magisk] J.Michael:
Does fastboot allow flashing while bootloader is locked if the image is properly signed?
[Magisk] zgfg:
You shouldn't be able to flash even the vendor's official ROM by Fastboot with the locked BL

It will only install through the stock Recovery