yashsingh1/xdaforums huggingface dataset:
[Magisk] tinbilly:
Many thanks for your time.

Upon clicking "Install from storage", the File Manager opens for me to choose an already-downloaded module. However, after I click to select a zip file, nothing happens. This is unlike before when I can successfully install a module using "Install from storage". Yet, I was able to install a module from Repo.
[Magisk] pndwal:
Bit further:

Seems this is a fix for hiding isolated processes (difficult to hide from bank apps etc):

https://github.com/topjohnwu/Magisk/issues/2406#issuecomment-634585257

https://github.com/topjohnwu/Magisk/issues/2406#issuecomment-636430282

https://github.com/topjohnwu/Magisk/issues/2406#issuecomment-759915159

https://github.com/topjohnwu/Magisk/issues/2406#issuecomment-787059513

👌 PW
[Magisk] pndwal:
This may be useful too:

https://github.com/vvb2060/riru-unshare

And this (Use it like Rootbeer?):

https://github.com/vvb2060/MagiskDetector

Details (Good technical overview for any wishing to understand detection methods as well as MagiskHide mechanism):

https://github.com/vvb2060/MagiskDetector/blob/master/README_ZH.md

Translated:

👍 PW
[Magisk] pndwal:
Bit sad to see John's Pinned Tweet re. Magisk unpinned, so I'll put link here:

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

Not a good sign AFAICS. 😬 PW
[Magisk] zgfg:
Please test by installing a module from Repo - install e.g. MagiskHide Props Config - just installing (and not running Command Line Interface command props from terninal app will not make any changes to your system - want to see can you install a module without taking your File Mngr issues

Problem with Install from storage looks exactly as answered you in the previous post - problem with your File Mngr that Magisk opens and that does not properly communicate with Magisk

Do you have any other File Mngr installred (Like MiXplorer)?

Although it works for me with default Files, I can switch from Files to MiXplorer and also pick-up a zip file there

There could be also a problem with your downloaded zip file.

When you take Install from Repo for MHPC, you will also have its zip in Downloads folder
[Magisk] YLNdroid:
Esteemed members; seeking your valuable opinion(s).
[Magisk] pndwal:
I'm not sure about proper switches here sorry...

Disabling is generally enough.

Sounds like it may be a different problem in any case. Have you checked other modules by disabling all... And removing all from MagiskHide list.... Re-enable one at a time to identify problem mod.

I don't think you responded to my advice re. processes in MagiskHide list previously. Did you try deselecting these?

See also:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85080283 PW
[Magisk] pndwal:
I don't have Sammy, but I believe that's correct.

For newer Samsung device, other images need flashing together, but that is apparently for Android SAR = yes (Android 9+?), as detailed in official GitHub Magisk Installation Instruction page.

Sammy users may be of more help. PW
[Magisk] tinbilly:
I successfully installed MagiskHide Props Config from Repo and was able to find its zip in the Downloads folder. However, installing from the zip file failed. I switched to other File Explorers like Fx, Amaze, but got no luck.

Not a big issue then. But it's very strange, since "Install from storage" works fine for me until 2 days ago. Btw I am running crDroid 7.4 with nanodroid and microG installed.

Many thanks for your advise.
[Magisk] dpiehl1:
I appreciate any help or direction. Is there additional information that I can provide?
[Magisk] ipdev:
It is just a guessing game without LOG files.

Your Magisk install could have become borked or something is interfering with Magisk.

One of your other modifications.?

This would include a change in (or made by) the custom rom.

Did you change any setting or update anything in your rom?

Log(s) are the only way to know what is actually happening.

Magisk and MagiskHide Installation and Troubleshooting guide - WebSite - Asking for help/reporting bugs - Link

The more information we have, the more we can help. ;)

Cheers. :cowboy:
[Magisk] ipdev:
I have not been a Sammy guy in a long time.

SuperSU was just becoming Systemless root.​

Unless I am mistaken, Samsung only used fastboot on their older Nexus devices.

Nexus S, Galaxy Nexus and Nexus 10

Download mode is not the same as fastboot, so you will not be able to use fastboot commands.

You get <waiting for any device> since no fastboot device is recognized.

Download mode is different depending on device. In the Samsung world you would use Odin.​

(I think Keys was the name of the consumer version they offered to factory restore a device the last time I used Samsung.)​

If you have TWRP installed, you can flash both zip and image files.

TWRP defaults to Install Zip

To switch to image files, toggle to Install Image.

TWRP-> Install-> Install Image

The button will then switch to Install Zip​

Navigate to the image file you want to install, select it and Swipe to install.

TWRP will ask what partition to install it to.

I am not sure if your device only needs a patched boot image or not.

If it will work with just a Magisk patched boot image..

Install the Magisk app.​

Patch the boot image.​

Reboot to TWRP and Install (flash) the patched boot image.​

I am not currently familiar with Samsung so it is just some general TWRP (and my out of date Sammy) knowledge. ;)

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Magisk] pndwal:
Should do; Samsung Galaxy J5 2016 LV 6.0, now on 7.1.1 should be fairly old school. 😉

@YLNdroid

... Interesting that it has SD 410 n launched 2016. I had same soc in Huawei Y550 launched 2014.

FWIW, all I know about it is need to take care not to allow it to overheat. Many devices w/ that soc series suffered various memory / USB / other hardware failures due to inadequate thermal protection... At least running 32 bit OS.

Seems J5 runs 32 bit also, despite Cortex-A53 64bit ability and late launch date for that soc. Seems very few OEMs utilised ARMv8-A in SD 410. PW
[Magisk] ChefMithandir:
Hi, can someone help me with my issue: My Basic Integrity fails + EvalType is N/A. Not to speak about ctsprofile...

I`m on:

Oneplus 8 pro (IN2023)

Android 11, OxygenOS 11.0.5.5

Magisk 23.0, with patched Boot.img

What I did:

Magisk Hide enabled incl. Google play & service (complete)​

Hide Magisk (rename)​

Mode installed: Universal SafetyNet Fix 1.1.1​

Mode installed: MagiskHide Probs Conifig (But thats not working anymore i think)​

As i understood even without the modules, at least basic integrity should pass, but it doesnt. And i cant find anything regarding evaltype N/A aswell. Please help. Thank you
[Magisk] pndwal:
SafetyNet attestation is server based.

You appear to have no mobile data, and wifi connection problem, so evalType is N/A.

With no evalType engaged, clearly no evaluation of ctsProfile or basicIntegrity is done, and no attestation is returned, but neither component has in fact failed.

Nb. This can be reproduced with working data connection by Clicking Check SafetyNet, then turn off data (eg mobile data), then click Try again. 😛 PW
[Magisk] pndwal:
Mmm.

Did you restore all read-only partitons such as /system, /boot or /recovery before taking OTA?

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md

Are you certain you extracted / patched / flashed boot.img from new beta ROM?

Were you able to boot and unlock before flashing patched image?

If you didn't try, flash unpatched image and see if you can complete bootup.

It's also likely a Magisk module is causing issue with Lockscreen etc or is not compatible with A12 / A12 beta (eg Universal SafetyNet Fix).

If you didn't disable all modules before this major Update, try disabling them and booting. There are several methods, easiest probably being boot to Safe mode (automatically disables modules) then simply boot normally.

https://www.didgeridoohan.com/magisk/MagiskModuleIssues#

Nb. Seems normal USNF module breaks on Pixel 3 XL with Android 12, but experimental "Shim the keystore service instead of replacing it" module is working:

https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-781882649

This may be a common issue w/ Pixels. This report is for Android 11:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-84320703

So you probably need to disable modules, boot (fix lockscreen issues if necessary), then apply test2 module for SafetyNet pass. Download is here:

https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-767863635

Nb.2. It further seems F2FS loopback bug is causing 'locking of the system' w/ Magisk especially on Pixels. If this is not fixed in your A12 Beta (I've no idea), you may also need a custom kernel, such as ElementalX.

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-84415647

Hope it helps. PW
[Magisk] ChefMithandir:
Worked! Thank you very much... Hours of reading threads for nothing :D
[Magisk] andruyd:
I'm not sure what the toggles do on the "Modules" section. Do I have to reboot after disabling the module through the toggle or is it automatically disabled in the system?
[Magisk] zgfg:
On installing, uninstallimg, enabling, disabling a module you have to reboot

Disable : adds an empty file named disable to the /data/adb/nodules/<module_folder> folder

Enable: removes that disable file

Uninstall: adds a file named remove to the module's folder

On the next reboot, Magisk checks those files and performs the actions

You can use a root explorer and check those files when you disable/enabl a module from Magisk app. You can also manually create/remove those files and on the next reboot, Magisk will act
[Magisk] YLNdroid:
@ipdev: Thank you very much for expanding my knowledge and the vital information.

:cool: 🙌

Initially, I attempted flashing the patched TAR file via Odin3, but the Magisk card continued to display N/A in the app.

I attempted patching again the TAR and IMG files of the raw boot image on separate instances, but the activity progress indicated installation failure on each instance.

Consequently, I flashed the IMG file of the raw boot image via TWRP; then uninstalled the Magisk app and re-installed it.

I successfully patched the IMG file of the raw boot image and subsequently flashed it via TWRP (selecting the boot partition within TWRP).

However, the Magisk card within the app still displays N/A within the app.

😞

What am I doing wrong or incorrectly?

😔
[Magisk] pndwal:
Ah... now you say! 😜

Looks like you may have this known issue (Regression, affecting Android 6, 7):

"Magisk 22101 (22.+) not detected by Manager ("N/A"), but SU still working on Android 6.0 (+) Marshmallow with Samsung Note 4 SM-N910F TouchWiz, armeabi-v7a and other devices #4174"

https://github.com/topjohnwu/Magisk/issues/4174

Seems no fix / diagnosis on horizon, but Magisk 21.4 + Magisk Manager 8.0.7 and earlier are working for these users.

Hope it helps. PW

Edit: I'm guessing that if you move to custom ROM, this issue may be gone.

Like the look of this (A10) one:

https://xdaforums.com/t/derpfest-10-q-for-j5-2016-sm-j510x-vanilla-unofficial.4147719/

Or blissfully move to Android 11 (few issues extant):

https://xdaforums.com/t/blissroms-14-3-r-for-j5-2016-sm-j510x-vanilla-unofficial.4199195/

Many more here:

https://xdaforums.com/f/samsung-galaxy-j5-2016-roms-kernels-recoveries.6155/

Galaxy J5 XDA resources:

https://xdaforums.com/c/samsung-galaxy-j5.5701/

Your call. (Big Jump.) 😉 PW
[Magisk] flatz1235:
I have a problem,

Device : Redmi Note 4

Android version : 7.0 NRD90M

"Magisk has/keeps stopping". Anything related to Magisk, it will appear that error message. Can someone help me? I'm newbie here. Any advice would be appreciated.
[Magisk] tinbilly:
I send attached the log file. Hope this is what you need. Many thanks for your help!
[Magisk] flatz1235:
I'm sorry, what LOG is? I'm really kinna new about this. Is this log?

This error message keep appear whenever I opened Magisk.
[Magisk] pndwal:
[Not sure logs will help much here. General app problem.]

Edit: Actually, seems "java.lang.RuntimeException: Unable to instantiate application" may be fixed simply by rebooting if reason for this issue was due to previous app activity wrongly halted.

Generally for App Keeps Stopping error:

Try Force stop the app, Clear app data, Uninstall/reinstall the app, Check app permissions (none denied), Clear cache (phones cached data), Free up storage space. PW
[Magisk] flatz1235:
Okay, thank you so much. I just uninstall Magisk, now I can open it.
[Magisk] pndwal:
FWIW, as there is no news of updated Magisk from John Wu, I'm now running Alpha Magisk and Magisk App from dev @vvb2060 (Nangong Xueshan).

Seems his App maintains connection to standard Stable / Beta / Canary channels from topjohnwu, but adds his Alpha (Bleeding edge) channel:

https://github.com/vvb2060/magisk_files/tree/alpha

Click View code, Download / install app-release.apk 👍

No problems running this Alpha so far. 👍

- Nb. Unhide Magisk App if changing to this. Conflict with hidden Apps are still occurring.

Alpha adds new / experimental commits. Some of these already have pull requests in John's Magisk GitHub.

Nb. John Wu recently changed his description of debug Canary builds from 'Bleeding Edge' to 'Cutting Edge'...

WARNING

If you move to Nangong Xueshan's Alpha, my advice is to consider yourself on the Bleeding Edge again... and to understand what this means!

Changelog for Alpha, next post. PW
[Magisk] pndwal:
Latest @vvb2060 Alpha build (May 16, 2021).​

Changelog and Release Notes:​

Chinese text Translated:

# alpha update log

## Magic (1eb83ad8-alpha)

-Based on 1eb83ad8, please refer to the upstream update log for related modifications

-Properly process any data from magiskd

-Support SharedUserId

-Delete the backup file after restoring the boot image

-Built-in current version update log

-Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline

-Support bootimg v4 format

-Support bootconfig

-Detect /data/adb/magisk/ not updated and prompt to fix

### How to use APK files in Recovery?

Generally, it is recommended to install and uninstall Magisk through the Magisk application.

If you insist on using custom Recovery, change the `.apk` extension of the Magisk APK file to `.zip` to flash in.

To uninstall Magisk, the zip file name needs to include `uninstall`, for example, rename the apk file to `uninstall.zip`. If the file name does not contain `uninstall`, the installation operation will be performed.

# Upstream update log

## 2021.5.12 Magic v23.0

This release is focused on fixing regressions and bugs.

Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher.

### Bug Fixes

- [App] Update snet extension. This fixes SafetyNet API errors.

- [App] Fix a bug in the stub app that causes APK installation to fail

- [App] Hide annoying errors in logs when hidden as stub

- [App] Fix issues when patching ODIN tar files when the app is hidden

- [General] Remove all pre Android 5.0 support

- [General] Update BusyBox to use proper libc

- [General] Fix C++ undefined behaviors

- [General] Several `sepolicy.rule` copy/installation fixes

- [MagiskPolicy] Remove unnecessary sepolicy rules

- [MagiskHide] Update package and process name validation logic

- [MagiskHide] Some changes that prevents zygote deadlock

### Full Changelog: [here](https://topjohnwu.github.io/Magisk/changes.html)

See notes:

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

😬 PW
[Magisk] scandiun:
How do I root LineageOS-18.1? I have already custom recovery and installed LineageOS 18.1 + MindTheGapps-11.0.0-arm. It must be rooted using the app Magisk-v23.0.apk or must I root it from TWRP Recovery using Magisk-v20.4.zip?
[Magisk] pndwal:
https://topjohnwu.github.io/Magisk/install.html 👍 PW
[Magisk] J.Michael:
@pndwal Any idea why deleting the backup file is a good thing? Isn't the backup file the unpatched boot image?
[Magisk] zgfg:
You may have several of them (/data/magisk_backup_*) and you don't need the old ones.

Hence you can clean some space - but IMO, it shouldn't be a lot, they are gzipped hence even if you have the full size image (filled with zero bytes to the top), they shouldn't occupy that much space (for me backup files are cca 17 MB, but my boot.img is 20 MB, not the full size 128 MB)
[Magisk] centodue:
Hello to all.

I have a head unit with T3P1 processor and I used a boot_patched.zip file prepared just for my device (android 8.1.0) and it results correctly rooted with root checker, but every time that I open Magisk I have the next warning message:

" Abnormal status found. It is found a "su" command not belong to Magisk. Remove it to avoid malfunctions. "

I don't know how to find and remove it.

Control Safety Net is failed and checking in Play store settings the device is not certified.

Are all the things correlated ?
[Magisk] DiamondJohn:
regarding finding a superfluous su, one idea is to try the command which su; from various locations in a shell.
[Magisk] pndwal:
There is little documentation on @vvb2060's methods, and what is found often needs translating from Chinese, so I'm guessing:

On my system NO backup was preserved from 29 May Installation (direct Install) of Magisk 1eb83ad8-alpha, but previous backups remain.

The remaining ones contain only boot.img.gz file.

It does seem to me that the backup image is generally superfluous as users generally have unpatched boot image for initial setup patching extracted from ROM (or from TWRP nandroid backup), and likely flash this from PC in event of issues in any case.

Also, while I don't think non-root apps are able to see file/folder structure in /data

https://developer.android.com/training/data-storage/app-specific

I do wonder if this commit may somehow be related to @vvb2060's efforts to fix MagiskHide issues / methods of detecting Magisk. He seems to have done much work on this, even producing Magisk 'Lite' builds to effectively hide isolated processes.

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

Of course, if magisk_backup_xxx folders from previous Installations are removed, no folders with 'magisk' identifyer remain.

I'm not across different access permissions for folders in /data, but understand John chose /data/adb as location for Magisk related files for its inaccessibility. Ref:

https://xdaforums.com/t/magisk-the-magic-mask-for-android.3473445/post-74923643

From that, I deduce that it may well be possible for non-root processes to detect newly created folders somehow.

I'm not sure why backup folder is not simply created in /data/adb also, but I'm sure it's been considered. PW
[Magisk] tinbilly:
[SOLVED] I turned OFF System > Developer options > Don't keep activities. Now I am able to install zip modules using "Install from storage".
[Magisk] F308:
This is general magisk support then I am asking about such thing:

What should I think and what meaning have lines from Magisk log like the below?

"* Device API level: 30

** post-fs-data mode running

unlock mmcblk0p42 failed with 13: permission denied"

There are more similar lines about failing unlock concerning devices:

mmcblk0p28

mmcblk0p15

mmcblk0p43

mmcblk0boot0

and more yet.

Generally everything works, SafetyNet passes, root access works.

I just wonder because there may exist hidden risk behind this information, I simply don't like messages like those.

Details about system:

Galaxy A41.

Android 11 (but on 10 there was the same message, too).

Magisk 23.0 (23000) (21).

Ramdisk - YES.

SAR - YES.

I may attach the whole log of course, if needed.
[Magisk] pndwal:
For anyone interested:​

Nb. It seems this will likely be of interest only to those wanting basic superuser privileges, and a way to hide root from bank apps that detect isolated processes, at least at this stage:

Latest @vvb2060 Lite build (May 15, 2021).​

Changelog:​

Chinese text Translated:

Magisk Lite

In Magisk in the whitelist mode, all applications are hidden by default, and only the applications ticked in Hide can obtain super user permissions.

adb shell automatically has super user privileges. Module function is not available.

`magiskhide add UID package name` to add a super user application

`magiskhide rm UID package name` remove super user application

`magiskhide ls` lists super user applications

Magisk (7717f0a6-lite)​

Based on 7717f0a6, please refer to the upstream update log for related modifications

Properly process any data from magiskd

Support SharedUserId

Delete the backup file after restoring the boot image

Built-in current version update log

Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline

Support bootimg v4 format

https://github.com/vvb2060/Magisk/b...app/src/main/res/raw/changelog.md#magisk-lite

Notes:

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

👍 PW
[Magisk] zgfg:
Did you try maybe?

Sad, if modules not supported, I hope not by design but for this first release.

Not supported only installation of new modules or even the modules pre-installed by the 'regular' Magisk will not work?

Hence Magisk hide works kind of opposite to the 'regular' Magisk? All apps by default enabled for, and for root one must be manually disabled from Magisk hide?
[Magisk] pndwal:
- No.

- That's why I haven't / aren't personally interested in doing so.

I am interested, as mentioned, in trialing Alpha builds, which seem at this stage to be the natural progression from Canary, ie complete functionality with experimental changes / fixes, that so far has worked fine for me.

- Seems it's something like that. I've added link to my previous notes re. Lite build in Changelog post above (you were too quick for me!).

Seems this will likely be of interest only to those wanting basic superuser privileges, and a way to hide root from bank apps that detect isolated processes, at least at this stage.

I have no idea if Lite build's anti-detection abilities can be incorporated into regular Magisk, if they are experimental only, can be made to work with module framework, etc, etc. That will be for maverick / intrepid users to ascertain. 😜 PW
[Magisk] zgfg:
Seems to be the Lite alpha release, though

Btw, I'm kind of lost there, cannot find the corresponding apk to download and to try (and I'm not going to fork and build myself).

But no rush yet, original Magisk v2300+ is still great for me
[Magisk] pndwal:
Latest @vvb2060 Alpha build (May 30, 2021).​

Changelog only:​

Chinese text Translated:

# alpha update log

## Magisk (1eb83ad8-alpha)

- Based 1eb83ad8, modify the reference correlation upstream update log

- proper handling of any data from magiskd

- Support SharedUserId

- delete the backup files to restore boot image

- Built-in current version update log

- use the local version when you can not download stub, can be completely offline now Magisk

- Support bootimg v4 format

- Support bootconfig

- Detection / data / adb / magisk / not update the situation and prompt repair

https://github.com/vvb2060/Magisk/b...66fb47d77df/app/src/main/res/raw/changelog.md

My notes:

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

Edit:

I've just updated to this from previous Alpha release with no apparent issues.

Interestingly, I got no Update button notice in Magisk App for this as Version has not changed from "1eb83ad8-alpha".

I'm not sure if this is intended, but can confirm that app-release.apk is different (10,353,541 bytes) from previous APK (10,353,384 bytes).

Previous update was a Version change from "7717f0a6-alpha", and all 3 are updated builds based on (John's) VersionCode 23001.

😬 PW