yashsingh1/xdaforums huggingface dataset:
[Magisk] cater2:
Hi

I do not know if here is the right place, but as it is about Magisk ... Anyway I ask the administrators to move the topic to the appropriate place .

I rooted my Phone Galaxy M12 according to this topic.

I was not worried because when I installed it, it was not mentioned that Knox would be burned ...

I used for some time the phone until yesterday, when I decided to uninstall Magisk, thinking about my guarantee that comes until next year.

I was confident that Knox in my phone intact, because Knox Status App showed it. Then I followed the procedure: I uninstalled all my modules

Uninstalled Battery Charge Limit App

I uninstalled root explorer app

I uninstalled Termux App

Finally, I opened Magisk App and did the complete uninstallation.

The Phone was restarted, according to the automatic product of Magisk App.

I decided, then open Knox Status App, and to my surprise he showed that Knox was burned!

I thought so, that since I had lost my warranty, I decided to go back to rooting my phone again using Magisk.

I'm back to my phone as I was.

After doing all the procedure again of Magisk Installation in my Phone, I decided, out of curiosity and intuition, take a look at the Knox Status App, and to my surprise, it showed that Knox in my phone was NOT burned, as shown in the figure attached .

After all, how can I know if Knox is burned or not?

Do Root in Phone Using Magisk Burns Knox?

many thanks
[Magisk] sahil_bhandari:
Bro so you mean i should root my phone again and check whether it gets reset or not... ???
[Magisk] sahil_bhandari:
And one more question bro Does your safety net pass or fails
[Magisk] Philnicolls89:
Knox is a physical fuse that blows when you root your phone, there is no way to fix it once it's been tripped. Most samsung features can still be made to work except for samsung pay which will never work again on that device (google pay will still work).

Going on your screen shot, it must be returning a false result for some reason which is strange, but Knox will indeed have been tripped.
[Magisk] sahil_bhandari:
How false result bro??? Its a glitch or ...
[Magisk] zgfg:
I'm not a Samsung user and I don't know much about the Knox but just some thoughts:

In the thread you linked above there is your post (isn't it?) where you described that you unlocked the Bootloader and by that tripped the Knox

On the other side, Magisk Hide and modules like USNF help to pass the SafetyNet (and therefore mask the fact that Bootloader was unlocked)

Hence you could try now with Magisk, if you turn off Magisk Hide (and disable USNF module if you use it), then after reboot, would it still show that Knox was not tripped?
[Magisk] Philnicolls89:
As @zgfg just stated, it's possible that the app used to check knox is being fooled by magisk or other modules hiding an unlocked bootloader and root status. But I guarantee knox has been tripped if you are rooted, there is no question! Aswell as testing using the method @zgfg described, you could also simply try to use samsung pay as it won't work on a device that had tripped knox
[Magisk] pndwal:
I understand that very early implementations of Samsung Knox actually did use a "resettable" warranty bit, but all late Knox varieties behave as follows...

John is well aware that Knox is tripped by Magisk & warns explicitly in official Installation Instruction:

"- Installing Magisk WILL trip KNOX"

https://topjohnwu.github.io/Magisk/install.html#before-installing-magisk

Samsung users need to understand the Knox warranty bit (e-fuse) before installing any custom firmware:

https://docs.samsungknox.com/admin/knox-platform-for-enterprise/faqs/faq-115013562087.htm

-Use the key combo given here to properly check Knox status.

-Additional lost functionality is described in the "what happens..." link from here.

Simply unlocking the bootloader doesn't trip Knox.

Magisk (current builds) add props to spoof 0x0 Knox from v12.0.

https://topjohnwu.github.io/Magisk/changes.html#v120

A little re. how Knox affects warranty:

https://en.m.wikipedia.org/wiki/Samsung_Knox

🤠 PW
[Magisk] J.Michael:
@cater2 The link you posted *does* say KNOX will be blown. (It says blown by unlocking bootloader; I have read elsewhere it is only blown when an unsigned image is flashed to boot or recovery.)

If you put your device into download mode, does the little block of text in the upper left of the screen say anything about "KNOX Warranty Status"?

When you have Magisk installed, do you enable MagiskHide?
[Magisk] pndwal:
I'm fairly certain that this is just a wrong but oft. repeated fallacy.

Sammy say "The Knox Warranty Bit detects if a non-Knox kernel has been loaded on the device" or a "non-Knox boot loader" or "If you root your device".

https://docs.samsungknox.com/admin/knox-platform-for-enterprise/faqs/faq-115013562087.htm

https://docs.samsungknox.com/admin/knox-platform-for-enterprise/faqs/faq-115013719548.htm

Other reputable sources agree:

https://www.theverge.com/platform/a...axy-z-fold-3-camera-disable-bootloader-unlock

They boast however "Samsung Knox brings defense-grade security"

And: "Why Knox?

- 1 B+ Samsung devices secured

- 70 M+ devices managed daily

- 20,000+ businesses supported worldwide"

https://www.samsungknox.com/en/about-knox

Also, camera is now used for "Knox Capture - Enterprise-grade scanning on your device"!

... Wonder if this justifies the warning when unlocking the bootloader: "Doing so will cause the camera to be disabled" (see Verge article above) on late models / updated firmwares... PW
[Magisk] 73sydney:
All that Knox stuff is why i departed Samsung phones after my Note 4 and went Pixel, and will never go back

If you spend that much money on a device, you should be allowed to do what you want with it, without all that nonsense...
[Magisk] cater2:
You are correct , I did this , and Knox Status app shows Knox burnt (0x1) :(

Well , then one must always inform that , rooting using Magisk on Samsung phones , burning knox permanently , which is not said ....

thanks
[Magisk] Didgeridoohan:
Well... To be fair, in the Magisk installation instructions there's this (and it's linked from the post you claimed that you followed when installing):
[Magisk] nicesoni_ash:
Hi,

I have just recently noticed that my playstore is showing not certified and in magisk cts profile is failing so I tried few steps suggested earlier. I was alreasy on safetynet fix module so I just updated it to latest version but that didn't solve it, so I installed "MagiskHide Props" module too and installed fingerprints for my device K20 Pro (Indian), reboot and it still doesn't pass. So I searched more and then tried XPrivacyLua trick but that also didn't help.

So now I am out of ideas, can you suggest me any solutions, I am on RR custom rom, android 10.

Would appreciate any help.

Thank you.
[Magisk] largo2:
try magisk module safetynet-fix-v2.1.1.zip
[Magisk] cater2:
Regarding the second link. I don't have the "home" key, to do the procedure informed in the link

Pass

install Universal SafetyNet Fix , if you are having problem .You will need to install Riru module as well ..

Releases · kdrag0n/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com
[Magisk] nicesoni_ash:
As stated in my original post, I have already tried its latest version from their git repo and it doesn't work for me.
[Magisk] HippoMan:
I totally agree, and this is the main reason for my ongoing and increasing disenchantment with Android in general. Unfortunately, even as Android gets more and more like iOS in terms of standing in the way of customization by users, it's still the best (i.e., "least onerous") alternative in that regard.

For me, remaining on Android 10 and Magisk 23.0 on a somewhat old device (OnePlus 7Pro) seems to be the best I can do in terms of maintaining the ease of customization ability that I have always desired over the years.

I'm waiting (but not holding my breath, by any means!) for someone to come out with a much-more-customizable alternative to Android.

</opinionated-rant>
[Magisk] pndwal:
Yup, there are a number of different methods to enter special modes for Sammy - need to Google. 🙂

Here's one for Download (Odin) mode on Galaxy M12:

https://www.naldotech.com/samsung-galaxy-m12-recovery-download-mode/ 👍 PW
[Magisk] cater2:
I realized that later , thank you very much anyway and a good coffee for you :)
[Magisk] cater2:
Please has anyone here tried to use Galaxy Store using a Samsung phone in stock , but with knox burnt ?

I tried it now and the message I get when I try to buy (I did a test) is that it is not possible to pay using a credit card, on a rooted phone, telling me to use another payment method.

So I think it might be possible to buy from the Galaxy Store app , using credit card , in stock rom , even with knox burnt ...

thanks
[Magisk] Didgeridoohan:
First thing I'd try is to toggle MagiskHide off and on. Sometimes works...

If that doesn't work and you have the latest Universal SafetyNet Fix module installed (currently v2.1.1) and using a certified fingerprint you've done everything you need to spoof SN. Now you need to figure out what's triggering SN. Could be your ROM, a Magisk module you have installed, etc. Some tips can be found here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] nickster_uk:
Hi,

I rooted my N986B with Android 10 a while back with Magisk 20.3 and Manager 7.5.1.267 and it worked like a charm.

However, a little while ago I noticed that when opening the renamed Magisk Manager, I was prompted to update it. After clicking ok, it would say it was downloading Magisk Manager then prompt me to manually relaunch the app. On doing so, the same cycle repeated. I decided to leave it as I read about issues from users left with bootloops after trying to update to newer versions of Magisk when the manager app has been renamed. Besides, root was working and was hidden from the apps I needed it to be and more importantly, TiBu was working. I just wasn't able to load the manager or change any Magisk settings.

So, rather than try fixing Magisk, would it make more sense to backup, flash the latest OS with a factory reset and root again?
[Magisk] Philnicolls89:
Do you now have two versions of the magisk manager app? One would be the hidden/renamed app and the other would be the normal one. If so just remove the second non renamed app and try again, but unhide the app/restore it to its original state before trying to update.

If you don't see two manager apps installed you could also try just deleting the manager app altogether and re download and install it.

There is no need to backup and reflash OS as your issue is with the manager app not magisk itself. Unless you also tried updating magisk aswell as the magisk manager app.

Magisk will still remain without the app installed, you just need to use the app to configure settings. Think of them as two different things.
[Magisk] OMAKE:
Hello.

Device is Fly FS526 Power Plus 2, Android 7, patched boot, no custom recovery.

After Magisk upgrade to 22.1 i can't access /system/priv-app normally.

Spoiler content hidden.

How to undo?

I don't have custom recovery or even firmware to flash stock.

Everything is working fine but i want normal /system/priv-app directory with Magisk installed.

Thanks.
[Magisk] nickster_uk:
Thanks for the reply.

I had just the hidden version of MM when I first noticed the update prompt when launching it. Even after clicking ok and it downloading and then prompting to relaunch the app, I still only had the hidden version. I installed the same version of MM again and I then had two versions of MM, but it would still prompt to update and after updating it shows that Magisk is not installed.

The only options I can access are for the theme and updates. How can I unhide/restore to its original state if I'm unable to get into Magisk's configuration? My phone is remains rooted, but MM doesn't think Magisk is installed?

The main reason for thinking flashing may be better is that I'm still running OS 10 with an old security patch. As TiBu seems to be working fine, I'm thinking back all my stuff up, get the latest version of 11 with the latest security patch and root again then restore my apps/data. If I was already on 11 with a more recent patch, I'd be more inclined to fix the Magisk issues without reflashing.
[Magisk] zzz2002:
dumb ?

Since John Wu now works for Google he has, understandably, indicated that he will not be continuing the development of Magisk.

I believe I am currently using 23? (f822ca5b).

what should I be using, where do I get it from, how do I configure it (particularly safety net).
[Magisk] Didgeridoohan:
On the contrary, he's very active in developing Magisk (take a look at the Magisk GitHub and you'll see).

There are experimental alpha builds being made and released (look back/search in this thread), but if you're on a working setup there's no need to update until anything official is released.
[Magisk] pndwal:
What version did you update from?

22.1 is now fairly dated. - why not try 23.0? PW
[Magisk] pndwal:
The point is that two (or more) Apps / Managers conflict.

Please locate and remove any renamed Magisk App from device settings, Apps, App info (or equivalent). If you forgot names you may have chosen, go through the whole list... likely it's default choice, 'Settings'!

If that doesn't fix conflict (App says 'Installed N/A' etc), you may need to uninstall / reinstall unhidden Magisk App also.

Nb. Magisk general settings (hidelist, Superuser etc) & modules survive as they are stored in /data/adb instead of in app data.

While updating (App) with App hidden, especially between consecutive builds, is supposed to work (coming from old builds to post 22.0 is an exception), in practice the new App has failed to replace the old one some 50% of the time when not first un-hidden. It is therefore a good practice to 'Restore the Magisk app' before updating. 👍 PW
[Magisk] 73sydney:
As @pndwal says, try upgrading

As for me, i have only this advice as general advice

Before Flashing Anything Rules:

Always have a backup of your stock ROM

Always have a backup of your efs/nvram partition that houses your IMEI (if applicable to your phone model)

Google search for that phone and model for Stock ROM (im not comfy pointing at a specific link as that not a mainstream one so ymmv with any info on those pages):

Fly FS526 Power Plus 2 stock ROM - Google Search
[Magisk] HippoMan:
Yes. He continues to work on Magisk, but no longer on anything which would hide apps from SafetyNet.

Other people, however, are doing a lot of work on MagiskHide-like functionality.
[Magisk] Philnicolls89:
On a side note, TiBu is extremely outdated and most of the time backups will not restore properly. If you do want to make a backup so that you can clean flash android 11 then I suggest using Migrate app instead.

https://xdaforums.com/t/app-root-5-0-1st-nov-2020-migrate-custom-rom-migration-tool.3862763//unread
[Magisk] samsungFanboy85:
Please be calm i know where are the values and edit in notepad build.prop and rest **.prop also how magisk hide config works but iread about hardware is hard to spoof if my chip is exynos hard to spoof or like my edxposed sees note 9 some apps too... But Google account from chrome always shows This device s8 like there but key was post fingerprint set to note9 and also build.prop system.prop defaut.prop checked all but still does get correct device Nevermind got game back xposed also back

Peace
[Magisk] pndwal:
To be fair however, he has done little with hide for some time (years?) now, but at the same time has not removed any framework needed to hide root etc, and arguably has already actually improved such framework support for 3rd party mods such as Universal SafetyNet Fix to be more effective...

Yup. Some Devs like vvb2060 even keep hiding in unofficial Magisk builds (for us modders), but make methods publicly available in the likes of Momo (for banks to improve detection) at the same time! - Go figure...

Here's another Custom Magisk effort that "will spoof/alter/manipulate non-Magisk related signals or traces to circumvent device state detection" by adding these back to latest TJW functionality:

https://github.com/TheHitMan7/Magisk-Files

Thanks to @Stillhard for the pointer. 👍 PW
[Magisk] Soumy1234:
This build doesn't include the changes from Magisk Alpha correct?
[Magisk] pndwal:
I think @TheHitMan selects / adds back 'MagiskHide' commits himself, just as vvb2060 does. However he does include many vvb2060 commits. So do TJW builds. (vvb2060 is one of the most prolific Magisk contributors.) - Just check github.com/TheHitMan7/Magisk-Files commits!

FWIW, I played with a recent build but had issues with webview (flakey / works partially at least on Redmi 8T) so have returned to latest Alpha for now. Others incl. @Stillhard report no problems with this however... YMMV.

Nb. @TheHitMan is also the author of "BiTGApps for Android":

https://xdaforums.com/t/custom-gapps-bitgapps-for-android.4012165/post-81060589ss

🤠 PW
[Magisk] Soumy1234:
Understood. I'll also stick with latest alpha for now.
[Magisk] pndwal:
🤔

I think device-end spoofing may not be the issue here. See below...

What is done by Magisk and most hiding module solutions can be termed 'device based spoofing'.

Aside from props on device however, a device profile datasheet is bound to a GSF ID and uploaded to Google's servers when the first Google account after a factory reset is created... this is a server side ID/profile.

*** The existence of this is likely your real problem. ***

This datasheet includes "your device’s hardware profile. A device profile is an elaborate description of your phone / tablet, listing hardware features, software versions, language options and even carrier information."

Interestingly, server side (ie, Google's server) spoofing also exists, and can, like device based spoofing, allow many features / services to be used on devices that wouldn't otherwise qualify. This too is a complex and diverse subject with security and other implications.

As an example, the quote above is from project documentation (which may be of interest / use to modders here) from Raccoon Onyxbits - Dummydroid's database.

Solutions like this work by altering the device profile datasheet bound to your GSF ID mentioned above.

This won't fix SafetyNet when HKA to TEE is working, but may still allow uncertified devices (China factory stock ROM / bootloader, etc) using ROMs without a device based certified fingerprint (custom or stock) to access PlayStore, and moreover, allow any device to be seen by PlayStore and apps as a different device (eg Racoon Dummydroid defaults to a high-end Samsung device).

Refs here (second half of post):

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85325001

🤠 PW
[Magisk] digger16309:
Strong recommendation for Swift Backup. It's in the Google Play store. There's added functionality with root. It saved me once and restored every app better than TiBu ever did for me, even when it was working.
[Magisk] pndwal:
New 'Yet Another SafetyNet Checker' w/ attestation evalType from @RikkaW (& @vvb2060 contributed). Also can display nounce.

https://play.google.com/store/apps/details?id=rikka.safetynetchecker

Source code https://github.com/RikkaW/YASNAC

Guess this anticipates no Check SafetyNet in upcoming TJW Magisk. 😛

shows attestation resulting from spoofing & fallback to basic.

Here is @vvb2060's (& @RikkaW contributed) earlier demonstration of key attestation API , 'Key Attestation':

https://github.com/vvb2060/KeyAttestation

This shows Chain of trust incl. Device lock (bootloader) and Verified boot states correctly, and many other details.

👍 PW
[Magisk] LNS:
Anyone know how to move back from alpha to stable? I either get magisk manager crash or before that I could not root.

Maybe it has to do something with the 'Hide the magisk app' feature I used. I completely uninstalled it after that but if I go to DenyList configuration there's leftovers there. Any idea?

(I suppose what I'm looking for is a way to completely remove magisk alpha hidden app leftovers)
[Magisk] zgfg:
The easiest way to switch:

- patch images and then flash the one (Alpha) or another (Stable/Canary), together with unstalling one or another app

If you don't have the boot.img patched by old Magisk:

- uninstall Magisk Alpha app

- install Magisk Stable/Canary app

- do Direct install (if you didn't munroot) or patch and flash (or install the old Magisk by flashing zip from TWRP)

You will have to enable MagiskHide and reboot, etc
[Magisk] zgfg:
Yes, it has the useful UI with the JSON answer from SN - attachements
[Magisk] zgfg:
Just tested, not bad

However, yes, WebView is broken (TheHitMan7 released his Magisk 20 days ago, at that time Webview was also broken in Alpha, hence he will need to update/merge and re-release, hopefully)

Otherwise:

It has Zygisk with MagiskHide (not DenyList) and when you enable, GMS is automatically enabled as in the good, old Magisk.

Also, MagiskHide is also still accessible from SuperUser tab

There is also Modules Repo as in the old Magisk

I had to grant roots for the apps again, modules stayed installed (incl. Riru, LSPosed, Viper4Android, etc)

SafetyNet passing

With Native Detector results the same as with Magisk Alpha (Zygisk detected, Riru not)

Issues with Magisk Detector though:

First it shows smaller number of boxes/results (e.g., missing SU detection) then it changes to even less boxes and reports that "app was hacked"

Similarly some issues with Momo app - screenshots attached

Tried by cleaning All data for Magisk Detector and momo app, also by disabling Momohider and even Riru, still the same issues there

Edit: Safely returned to Alpha, as described in this post:
[Magisk] pndwal:
I believe data stored in /data/adb for new TJW commits (merged in Alpha) may no longer be compatible with traditional Magisk. This is certainly the case with TheHitman7 custom builds, and he states:

https://github.com/TheHitMan7/Magisk-Files

I think it would be safest to select Complete Uninstall if reverting to current TJW builds from Alpha also.

Retrospectively (in case of issues) you can delete the whole /data/adb directory before flashing a boot image patched with TJW Magisk... 👍 PW
[Magisk] LNS:
Problem is I can't install old magisk. If I install through magisk and stable channel it throws 'App not installed', if I do it manually- uninstall app, install old, the old one won't open. First time I did that it installed but I couldn't root. Now it just either won't install or crash. That's why I said maaybe it has something to do with hide magisk festure. Damn if I hadn't installed the alpha -_-
[Magisk] pndwal:
Yup, @73sydney and I both confirm webview issues, 'device has been hacked' message in Detector app and other strange issues sadly with latest build... Of course this will likely (hopefully) change ..

The modules repo is @TheHitMan's custom repo, not the official one however. PW
[Magisk] pndwal:
Do you have TWRP? Use that to remove /data/adb directory as I said above...

Nb. You don't need TWRP installed; you can just boot it to use its file manager. PW
[Magisk] zgfg:
If you did Hide Magisk app, then you had to find it in Settings/Apps under the renaned name and uninstall.

When I said "uninstall", that covers both, no matter was it renamed/obfuscated or not

And just a note (not to be messed one with the other), hiding Magisk app is one thing and MagiskHide (DenyList in Alpha) is another

If no other way, install Magisk Alpha app and choose Uninstall Magisk (and opt for full uninstall). Again, this is uninstalling Magisk, not the app

Or rename magisk app (Alpha) to uninstall.zip and flash from TWRP - another way for uninstallaling Magisk (Alpha)