Magisk General Support / Discussion

[markd89]

It was mentioned previously that TJW stopped maintaining the Repo. For that reason, Magisk Alpha has no more Repo in the UI

You will need to find and download the modules manually (and install from storage) - and save it yourself locally for future

I'm using Magisk 23.0 (21). I actually do want to install a module from storage, but when I do that it does not show any files. That's my question - how to fix Install from Storage not showing any files.

 

[zgfg]

I'm using Magisk 23.0 (21). I actually do want to install a module from storage, but when I do that it does not show any files. That's my question - how to fix Install from Storage not showing any files.

Ok, I'm no more running Stable or Canary (but mAlpha) hence I don't know if modules are still visible in Repo

If they are, you can take Dowload instead of Install (play with the icons), it will download to your Download folder.
Then, on top of the Modules window in Magisk app, you have Install from the storage option

 

[J.Michael]

I'm using Magisk 23.0 (21). I actually do want to install a module from storage, but when I do that it does not show any files. That's my question - how to fix Install from Storage not showing any files.

I'm not sure where you are, but your screenshot says "Recent". Maybe one of the buttons will let you navigate away from "Recent", and then wander to what you call "Storage". (What does the menu offer?)

 

[dcarvil]

Hi, I have Magisk installed and working. However I want to install something from storage. When I do that, I see "No Items". I can't select the download folder.

I'm running Android 11/LOS 18.1/Edxposed/xPrivacyLUA. Magisk is not restricted.

What might I be missing?

Thanks!

Install from storage shows no files for me either, but it shows additional apps that allow me to select a file. See screenshot. Android 11/LOS 18.1/Magisk 23.0/Pixel 3. I think the problem is you are not seeing the additional apps.

 

[pndwal]

Turned back today to Riru-Momohider:

1) By enabling "isolated", Magisk Detector does no more find su in the path.

Good stuff!

Strange thing, it does no more report if Magisk Hide works fine or not (without, it always reported that Magisk Hide worked fine).

This is actually better; no report means 'MagiskHide' (/'MagiskDeny') is not detected...

Everything else is ok (root, Zygisk, SafetyNet, stability, LSPosed, etc) - hence I will keep that configuration (this was the first time for me to succeed masking the su in the path)

Btw, canyie on his Riru-Momohider page recommends against "isolated" but I was kicked to test with by a post on Alpha Telegram channel where the "isolated" option was also praised as good for use

Yeah, just saw those posts too... Not sure canyie 'recommends against', but notes pitfalls:

This feature is deprecated because it will unmount Magisk modified files for every isolated processes, and the unmounting time cannot be well controlled, which may cause some modules to not work. For almost apps, Magisk Alpha or the latest Magisk canary + Riru-Unshare is enough.

setns

Faster new way to hide Magisk in isolated processes. Requires config "isolated" is enabled.

https://github.com/canyie/Riru-MomoHider#background

2) I can not prevent Magisk Detector to detect the modified init.rc - even if I enable "initrc" for Riru-Momohider

You may see 'init.rc has not been modified...' sporadically.

Canyie says this result is unreliable (detects 'init.rc modified' even when Magisk isn't installed!):
https://github.com/canyie/Riru-MomoHider/issues/12#issuecomment-907718098

3) By enabling "setns" in Riru-Momohider, my phone becomes irresponsive upon reboot (it took me 7-10 minutes for weather widgets to load, 3-5 minutes to pass SafetyNet, etc)

4) With "app_zygote_magic" I got system crashes when running Magisk Detector or momo app and upon (soft) reboot Zygisk was no more active

Reflects my results running with Zygisk.

initrc is fine, but I hadn't previously tried isolated w/o setns...

Btw, none of the four options for Riru-momohider make any help for the momo app - it still detects even that Bootloader is unlocked

PW

 

[markd89]

Install from storage shows no files for me either, but it shows additional apps that allow me to select a file. See screenshot. Android 11/LOS 18.1/Magisk 23.0/Pixel 3. I think the problem is you are not seeing the additional apps.

Great clue, thank you!!

Temporarily disabling XPrivacyLua in EdXposed allowed me to see those apps and install what I needed.

 

[zgfg]

Good stuff!

This is actually better; no report means 'MagiskHide' (/'MagiskDeny') is not detected...



Yeah, just saw those posts too... Not sure canyie 'recommends against', but notes pitfalls:

https://github.com/canyie/Riru-MomoHider#background

You may see 'init.rc has not been modified...' sporadically.

Canyie says this result is unreliable (detects 'init.rc modified' even when Magisk isn't installed!):
https://github.com/canyie/Riru-MomoHider/issues/12#issuecomment-907718098

Reflects my results running with Zygisk.

initrc is fine, but I hadn't previously tried isolated w/o setns...

PW

Yeah, I know that for you init.rc modifications are randomly detected and not.
But for me it's deterministic, Magisk Detector always reports init.rc modifications (and no matter what I tried with Momohider, Unshare or without them).
And believe me, I test SN, Magisk Detector and Zygisk/Riru Detectors every day, sometimes couple of times

 

[BillGoss]

Install from storage shows no files for me either, but it shows additional apps that allow me to select a file. See screenshot. Android 11/LOS 18.1/Magisk 23.0/Pixel 3. I think the problem is you are not seeing the additional apps.

Tap on the hamburger menu at the top left of that screen. You can then navigate to your internal storage (in my screen shot it's OnePlus 8T, as that's my phone)

 

[pndwal]

Yeah, I know that for you init.rc modifications are randomly detected and not.
But for me it's deterministic, Magisk Detector always reports init.rc modifications (and no matter what I tried with Momohider, Unshare or without them).
And believe me, I test SN, Magisk Detector and Zygisk/Riru Detectors every day, sometimes couple of times

Have you tried when Magisk is not installed?

... Random / sporadic 'init.rc has not been modified' result may not actually be material.

Canyie seems be fairly certain his module is working to hide init.rc, and that "It's MagiskDetector's issue", stating that it returns 'init.rc has been modified by Magisk' when Magisk is not even installed.

Seems we simply don't have a reliable detector for this.

FWIW, I've only had Passed result for this a few times. IIRC, never when I was actively experimenting / rebooting; only after leaving it entirely alone for some time I'd notice it was suddenly saying 'not modified'.

When I cleared Detectors data and rebooted it was 'modified by Magisk' again and no intervention / efforts would restore 'not modified' other than leaving it for some weeks... PW

 

[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

 

[sahil_bhandari]

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

Bro so you mean i should root my phone again and check whether it gets reset or not... ???

 

[sahil_bhandari]

Bro so you mean i should root my phone again and check whether it gets reset or not... ???

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

And one more question bro Does your safety net pass or fails

 

[Philnicolls89]

Do Root in Phone Using Magisk Burns Knox?

many thanks

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.

 

[sahil_bhandari]

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.

How false result bro??? Its a glitch or ...

 

[zgfg]

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

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

As I did on my sm-m127f (aka galaxy M12)

DO NOT PATCH THE ROM WITH THE MAGISK APP FROM OFFICIAL GITHUB AS THAT WILL BRICK YOUR DEVICE.

1) Download my firmware stock .
I used the "SamFirm_Reborn" program, which the creator says downloads from Samsung servers

2) Unlocking bootloader: I think this is a great guide for it. Keep in mind that you must unlock the bootloader before proceeding with installation, and you WILL trip knox when you do so. Also, unlocking bootloader and installing Magisk will wipe your data + internal storage, so please back up all of your data before installation.

3) I downloaded Magisk patched , shown in the tutorial

https://xdaforums.com/attachments/magisk_patched_for_a21s-apk.5300541/

4) I followed the tutorial on this page (read carefully) to install Magisk .I followed the installation regarding Samsung devices .

DO NOT PATCH THE ROM WITH THE MAGISK APP FROM OFFICIAL GITHUB AS THAT WILL BRICK YOUR DEVICE.

I used Magisk Patched instead of the official magisk !!!

5) By following the part of the tutorial to install Magisk where it says:

"Install the latest Magisk app and launch the app. It should show a dialog asking for additional setup. Let it do its job and the app will automatically reboot your device."

I used the patched Magisk given in this tutorial

6) After everything done , in Magisk app , I disabled updates ...

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?

 

[Philnicolls89]

How false result bro??? Its a glitch or ...

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

 

[pndwal]

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

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:

It is a one-time programmable bit e-fuse, which can only be turned from 0X0 to 0X1 (i.e. tripped).

If a non-Knox boot loader or kernel has been installed on the device, Knox can no longer guarantee the security of the Knox container. As a result, the Warranty Bit is tripped to 0X1, indicating that this device can no longer use the Knox Workspace (container.)

If the Knox bit has tripped:

• A new Workspace can no longer be created on such a device.
• The data encrypted and stored in an existing Workspace can no longer be retrieved.
• Other Samsung services that utilize Knox security stop working (Samsung Pay, Secure Folder.)

...

If the Warranty Bit is tripped, the device displays Knox WARRANTY VOID: 0x01.

If that is the case, there is no way to revert the Warranty Bit and Knox won't work on this device. The only way to get the device back to its original settings is to replace the PBA (Printed Board Assembly) on the device; hardware replacement will be required.

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:

Once the e-fuse is set...

In the United States, this information may be used by Samsung to deny warranty service to devices that have been modified in this manner. Voiding consumer warranties in this manner may be prohibited by the Magnuson–Moss Warranty Act of 1975, at least in cases where the phone's problem is not directly caused by rooting.

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

PW

 

[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?

 

[pndwal]

@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.)

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:

Samsung’s Knox documentation says that, if you root your phone and flash it with an unofficial Android build, anything having to do with its Knox security will be permanently disabled, and will only be restored if you replace the phone’s hardware. This means that, if you root a Samsung phone, features like Samsung Pay and Secure Folder won’t ever work again.

To be clear, this doesn’t happen if you just unlock your phone’s bootloader — it only occurs after you make changes to the phone’s OS (though doing so is the main reason to unlock your bootloader, so it’s perhaps a distinction without much difference).

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

 

[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...