Don't start with other docs, please read official Installation Instruction carefully, then ask here if anything is unclear or doesn't work.Dear all,
I am new to this magisk thingy and have follow every single step to install it. I am unable to move forward due to it say the Magisk installed status is N/A. I've tried all the method that can find on the internet but still not working.
May I know how can I solve it and enjoy the Hide feature?
Btw, I am running android 6.0.1 on Samsung Galaxy Note 4 (SM-N910C).
View attachment 5284801
Thank you.
Jeffrey
U can remove magisk directly in magisk itselfHey could anyone tell me where i can find a trust file that i can remove Magisk via TWRP? I find some files in internet but not i official site. Could someone can help me?
Rename the Magisk APK file to uninstall.zip and flash it in TWRP.Hey could anyone tell me where i can find a trust file that i can remove Magisk via TWRP? I find some files in internet but not i official site. Could someone can help me?
The easiest way to uninstall Magisk is directly through the Magisk app.
If you insist on using custom recoveries, rename the Magisk APK touninstall.zip
and flash it like any other ordinary flashable zip.
Hi, Thank you very much for the replied. Please refer to the this here for my feedback:Don't start with other docs, please read official Installation Instruction carefully, then ask here if anything is unclear or doesn't work.
Official Installation Instruction is accessed from Magisk main page on John Wu's GitHub (under Useful Links), where, I hope, you downloaded Magisk App.
From Magisk App, just click GitHub OctoPuss (cat) symbol on home screen.
If you have compatable TWRP (custom Recovery) for your device, you can follow Custom Recovery section (Nb. Magisk in Recovery is something different altogether, and won't apply to your 'legacy' device).
Otherwise, familiarise yourself with Patching Images section before proceeding. Nb. Depending on how your Sammy ROM package archives boot image, some of the information for newer SAR devices in Samsung section may be useful for you if using Patching method.
Read, read, read. Then proceed! PW
Edit: Seems from this:
https://xdaforums.com/t/magisk-22-n...0f-touchwiz-armeabi-v7a.4253113/post-84870675
that you may have actually tried flashing 22100 using TWRP... but it's not clear.
You really need to say what you have tried.
If you did flash (aside from installing App), did you have a previous version? Direct Update within App?
Please give us a clue if you are still facing issues. PW
Hi. It's fine to post here - this is Magisk General Support / Discussion after all!Hi, Thank you very much for the replied. Please refer to the this here for my feedback:
Do let me know where is more appropriate to post my issue so that I won't be consider spamming the forum...tqvm for the help.
Hi,Hi. It's fine to post here - this is Magisk General Support / Discussion after all!
Updates there are clear however.
Yes, Latest 2 Canary builds have fix for Magisk SafetyNet check error, which is not actually indicating a failed result, only an evaluation failure. SafetyNet is actually still passing if PlayStore Settings shows PlayProtect Device is certified result. (Read recent posts here.)
Question: When updating to 22.1 App, did you have Manager hidden? Unhiding is critical due to incompatibility between old Manager and new App, as per release notes.
If you didn't do this, you likely have two conflicting Magisk apps installed. PW
Install latest debug Canary Magisk (fixed), or wait for next public Stable / Beta.how to to use the extension snet.jar guys? to pass safetynet properly?
Ok.Hi,
Question: When updating to 22.1 App, did you have Manager hidden? Unhiding is critical due to incompatibility between old Manager and new App, as per release notes.
Answer: No, I did not hide the Manager when updating to 22.1 App. After the updated and patched the app-debug.apk (Canary) then got the Installed: N/A.
Thank you.
ok, noted with thanks. Will go read through it and because I'm a new user at github I'm not able to post it.Ok.
There have been a number of issues raised on Magisk GitHub recently, relating to Android 6 (Marshmallow) problems, some closed due to insufficient information...
This one for your Samsung Galaxy Note 4is still open:
https://github.com/topjohnwu/Magisk/issues/4174
You may wish to help /provide information / logs for your device there also if no-one else here has suggestions. I think there may well be overlooked regressions in recent builds affecting you. PW
Ah, yes; John has recently been frustrated by issues not following his template / instructions, which waste his valuable time. He recently restricted issues to colaborators only, then opened again, but apparently with restrictions.ok, noted with thanks. Will go read through it and because I'm a new user at github I'm not able to post it.
View attachment 5285915
Is that a Samsung device? Universal SafetyNet fix installed? If so:Hello.
After installing the latest canary channel Magisk APK, which helped to pass Safety Net check. But unfortunately I have observed the issue that any of banking apps refuse to authorize using the biometric fingerprint sensor, only the password. Have anyone noticed such strange behavior?
Best regards.
Witek
Yes, I use Samsung S9 device indeed. I must have somehow missed thread about biometric issue. Thank you. I installed the mentioned Safety Net fix 2.0 test4, and biometric authorization began to work on the banking apps again. But Safety Net check in the Magisk app has changed from working basic evaltype into hardware, which doesn't work on rooted devices. Probably I have to wait until developers will be able to deal with all current problems.Is that a Samsung device? Universal SafetyNet fix installed? If so:
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84746087
Otherwise, please give some details / clues! PW
API error? (If yes, did you follow the previous conversation about the need to install Canary 22104 or to test with a third party SN checker)When I updated the magisk app to 22.1, safetynet basic integrity and cts both are false now. Earlier with 22.0, it worked with magisk hide props config with universal safetynet fix. What to do now?
Known issue. A fix has been merged. You can use the Debug app, revert back to 27001 or wait until 27003 is released.I'm now having a problem hiding the TJW Magisk 27002 app ...
I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.
The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:
(1) Unhide Magisk
(2) Update Magisk (27002 was listed)
(3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
(4) Magisk 27002 indeed came up properly after reboot.
(5) Tried to perform Hide The Magisk App.
I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.
I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.
I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.
What am I missing?
Only v27000 is Stable. (and Beta). v27001 and v27002 are Canary or DebugIs the Magisk 27001 APK/zip still available anywhere? I'd like to downgrade, but I can only find 27000 on Github and 27002 via update. I don't want to go to Canary in case the mounting changes break anything, or Debug as I hear the extra logging etc. causes performance issues (correct me if I'm wrong).
Yep, I told you several times that you need Recovery mode (selected) for your Ramdisk=No device; instructions for this are also clear in official Installation Instruction page too, but apparently you have not been trying to follow official instructions, so it's no real surprise you've messed up firmware too... Please take *extra* care when modding as there are simply so many variables and pitfalls!Direct Install with recovery mode checked worked for me. You were right.
After I flashed wrong CSC firmware my baseband and EMEIs disappeared. Now I have updated bootloader and I cant to flash original CSC firmware anymore. Any ideas how to restore baseband, EMEIs or it is too late?
Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about itI'm now having a problem hiding the TJW Magisk 27002 app ...
I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.
The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:
(1) Unhide Magisk
(2) Update Magisk (27002 was listed)
(3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
(4) Magisk 27002 indeed came up properly after reboot.
(5) Tried to perform Hide The Magisk App.
I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.
I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.
I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.
What am I missing?
Run magisk -c from adb shell and see what version it reports.I actually updated the app from the app itself before doing my OTA upgrade so it get the version 27 of magisk, I tried installing that one again I had in my downloaded folder. But I also downloaded again the app from github.
I do have root, I've modified the boot file with magisk, so I'm not sure what to do now. I'll try installing an older version. But as you see of the screenshot from app manager, I don't know how the app is installed and removed almost immediately. At first I thought it was caused by an android 14 new security change.