yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
Did you do the obvious and clear the apps data and cache?
[Magisk] jcmm11:
Make sure that on the one it's not working on (your build) the symlink between cache and /data/cache is properly created.
[Magisk] DiamondJohn:
Your "some ROMs clear out /cache during boot" does have some merit. When I looked at the log (from my modified working script) it had three entries with the text of something like "clearing cache". However, I chose to ignore these, as when I used the path /data/cache, it worked perfectly fine (and thats the log that had the "clearing cache" log text).:silly:

Anyway, my plan is to test with 3 scripts.

1. Do the logcat to /cache after 10 seconds

2. At 20 seconds, just before it does the log, switch to SELinux Permissive, then do the logcat. This one also to /cache

3. At 30 seconds, do the logcat using the working path of /data/cache
​

I am hoping the logcat at 30 seconds will capture the logcat info of what is failing at 10 seconds (ie point 1), and as for point 2, if SElinux has anything to do with it.

I'll let you know how I go. Maybe the last logcat will also have something in it explaining why the Magisk logs are not present.
[Magisk] MrPhilo:
It was working before just using Magisk Hide but now they seem to be able to detect it regardless what I do.
[Magisk] ktmom:
In this process, did you add modules, xposed, build.prop edits or any other mods? There is a lot an app can do to infer the device is "rooted".

There is a large amount of information on this in Didgeridoohan's documentation
[Magisk] TENlll423:
Is there any possible way to keep this from constantly popping up it's to the point where it's never gone it's at the bottom of the screen I'll show a screenshot about SD maid having superuser rights
[Magisk] Badger50:
Do you have SU notifications set to none in magisk manager settings?
[Magisk] MrPhilo:
I was able to find the reason. I had a module which put the SeLinux to Permissive, changing it to enforce fixed it!
[Magisk] bsports666:
Sure
[Magisk] testz:
Samsung A51 always makes error following tutorial in magisk. I cannot install magisk with bootloader unlocked. Is there some way to achieve root?
[Magisk] guhvanoh:
Does your device have a forum on XDA? If yes, try asking there. You'd have a bigger audience there and a better chance of getting help.
[Magisk] testz:
Well I did, and check the audience there is only one post regarding root!

I would like to see if there is a solution, and could do what someone with knowledge asked. Was wondering if [MENTION=4544860]osm0sis[/MENTION] can check this problem
[Magisk] ktmom:
This is a secure boot (also called dm verify for other devices) problem. It's not a Magisk problem. I'm not experienced with Samsung devices so I can't give specific advice. If you look through other Samsung forums, I'm sure it's been addressed many times.

Tagging osmOsis is a bit overkill [emoji6]
[Magisk] Didgeridoohan:
Great to hear that you got things sorted. I was kind of close to target then... :good:

I'll make sure to take a look at your excellent tips and see about improving the script (I'm not much more than a glorified script kiddie, so I take all the advice I can get).
[Magisk] DiamondJohn:
I have a couple more ideas on editing the script I have yet to implement, so if you are really interested in my input, maybe hold off a little while longer till I finalise it, i'll let you know when I'm done.
[Magisk] thunderteaser:
Magisk 20.3 completely broke Viper4Android on my Redmi Note 7 with MIUI 11 (Pie). I'm reporting this on this thread because I think it has something to do with how Magisk 20.x handles selinux policies (or scripts in general) since any module like Magisk SELinux Manager would just refuse to work with Magisk 20.3, so V4A is never able to install drivers. Any workaround I tried (even the rootless zip people are using to enable v4a on Android 10) would just fail. Reverting Magisk to the previous known compatible version (19.3) made selinux modules work again and I could install V4A drivers. Am I supposed to wait for V4A team to update their support to Magisk 20+ or am I "doomed" to stay on 19.3 because I heavily rely on permissive selinux to make things work properly?
[Magisk] guhvanoh:
You need to get the V4A team to write enforcing Selinux policies for V4A. That way you stay secure. Permissive is not the way to go. That's the whole point of Selinux, staying secure.
[Magisk] phelite2015:
buy a headset with apt/aptxHD then install poweramp full version...you will not need viper4android anymore...v4a for older phone models only
[Magisk] lexobys01:
No..not magisk nor viper, it might be the rom you are using? I have mine working in my redmi note 8, miui 11 with the latest magisk but legacy viper4android
[Magisk] Yus86:
Hello everybody, my Huawai P10 Lite "WAS-LX1A - 4GB - Kirin 658 - 2x IMEI - 32GB" has cost me a lot of nerves Roolback to Android 7, bought the unloocker with DC-Unlocker, installed this TWRP 3.3.1-0 and now this Rom.

Unfortunately I can't get Magisk 20.3 to set the Safetynet status to green. I've already tried a few devices as fingerprint, unfortunately without success. Does anyone have an idea where I can start next?

Why Magisk? I cannot start PokemonGo/Ingress.

Thanks!
[Magisk] ktmom:
On a stock ROM, does this device pass safety net? Not all devices do even new from the manufacturer. There's a substantial discussion of passing safetynet here
[Magisk] xunholyx:
Poweramp only works with your own stored music files. V4A is system wide, and works with music services like Spotify, Pandora, Youtube/Google Music, etc., and also while streaming video. That's why people like it so much.
[Magisk] thunderteaser:
Well I don't think it's the ROM. I'm on stock global stable and I was using latest Viper 2.7.1.0 before 20.3 made it incompatible. I think I tried installing Legacy but it has more installing options, so eventually one of them would have worked, but it failed on default settings for me.

EDIT: Have you upgraded Magisk while Viper was already installed? That would corroborate my thoughts. I'm talking about a fresh V4A install under Magisk 20.3.

I do understand what SELinux means for security, but here I'm reporting something odd about Magisk handling SELinux policies. For example, let aside Viper for a moment. Once I realized that modules that set Selinux as permissive at bootup wouldn't work anymore, I manually "setenforce 0" and made sure that "getenforce" would return "Permissive". On a regular basis, I should have been able to run "unsafe operations" but Viper

still failed to copy driver libs under Magisk 20.3 even when SELinux is not enforcing

.

Idk about other roms and devices, but the only working combo on my phone is Magisk 19.3 + Permissive SELinux.

At the end of the day what I really want to know is: is this how Magisk 20+ is supposed to work? Does it totally break SELinux manipulations or should modules that change SELinux status need to be updated to reflect changes in 20+?
[Magisk] Dreamer(3MF):
Regarding SELinux Mode Changer, Download The Module Of MultiFunctionsPlus From This Thread https://xdaforums.com/apps/magisk/module-social-media-cache-advanced-t3799155 For Getting The Ability To Use The Function Of SELinuxMode Inverter To Invert The Default Android SELinux Mode ([From Permissive To Enforcing] Or [From Enforcing To Permissive]).

For ViPER4Android, Give A Try To The Beta Version Of AML Module From This Post https://xdaforums.com/apps/magisk/mod-audio-modification-library-t3745466/post81529717 And After Rebooting The Device, Try To Install The Driver (P.S. There Is An Available Option In ViPER4Android Which Is Called Compatible Mode So Try To Use It).
[Magisk] Tom_Scott:
Hi again,

now I have installed MAGISK on my Samsung S4 Active running with Lineage 14.1.

I have two issues so far:

(1) The ctsProfile check fails everytimes

(2) The basicIntegrity check passes only then when the "Hide Root" Option is disabled and enabled again manually in the Magisk-Manager after every system reset.

For playing Ingress it seems to be sufficient when the basicIntegrity check passes.

But on the other hand I'm interesting in why the ctsProfile check doesn't pass. I know that there are several reasons, maybe its because of the custom ROM LineageOS or other reason. Does there an APP that give the specific reason why the ctsProfile check does not pass?

Thanks

Tom
[Magisk] thunderteaser:
I tried your module among other ways to set SELinux permissive on boot, but it didn't work on Magisk 20.3 on MIUI. AML is needed to enable compatibility when you have multiple audio plugins, this is not my case. As I stated earlier, even when manually setting SELinux as Permissive won't enable Viper to copy drivers. If it is working for you, then maybe the problem lies within Magisk 20+ on MIUI only.
[Magisk] Denver3D:
did you find any solution ?
[Magisk] Didgeridoohan:
Adding the app to the Hide list, repackaging the Manager with a random package name and giving it a custom app label doesn't help?

No issues here, using Canary build 20302.
[Magisk] Didgeridoohan:
Likely caused by the ROM not using a certified device fingerprint. That can be fixed: https://didgeridoohan.com/magisk/MagiskHide#hn_Spoofing_device_fingerprint
[Magisk] PC400:
Help me?

Bluetooth problems.

https://xdaforums.com/Mi-9/help/bluetooth-problems-install-audio-patch-t4037187
[Magisk] lexobys01:
Yes, you're right, was on 20.1 with a working viper, then decided to update the latest 20.3 to see it is still working. I happen to use my old downloaded viper installer, which I have known always work for me, and have been using it till now, not sure if it matters though

Edit : This is actually my 2nd attempt to intall viper, previously I was on Havoc OS (Q) and have a bootloop after reying ro downgrade back to P. I'm pretty sure that I was having newest version 20.3 and legacy viper working with fresh install too, so ...
[Magisk] amk316:
after magisk v20 it worked
[Magisk] TENlll423:
OMG wow I feel like an idiot and at the same time I am so appreciative... thank you I totally forgot about that it was driving me nuts...???
[Magisk] DiamondJohn:
I am running HavocOS Oreo. I had a working Viper with 20.1, and when I upgraded to 20.3 it also worked. NB, All this with "ViPER4Android FX 2.7.1.0 20190503.apk"

However, today I noticed that viper was not working. When I started the app, it asked me to install the drivers:confused: So I did, and after a reboot, it still asked again to download the drivers.:(

Anyway, I had a bit of a play with the Magisk module (it was a few hours ago so I don't remember all I did), and then after a reboot, it started to work :highfive: So I went for another reboot, and again it asked me to install the drivers.:mad: I had a play again, but couldn't repeat the previous success in the one or two attempts I made, so I uninstalled Magisk v20.3 and re-installed v20.1. Viper is now working.

Moral of the story, its a bit flakey if/when it works under v20.3 ie sometimes it teases and starts to work and you think you're all good, but a reboot gets you back to not working.:crying: For me the real test was if it still worked after a couple of reboots.:confused:

Viper is a deal breaker for my phone, so its back to v20.1 for me, for now.
[Magisk] thunderteaser:
A few posts ago I also stated how 20.3 broke Viper on my phone. I thought it was because of some sort of compatibility with MIUI, but you're using a totally different Rom, so the problem must be how Magisk 20.3 deals with SELinux policies.

Glad to know it works on 20.1 as I downgraded to 19.3, so maybe I can try 20.1 as well.
[Magisk] DiamondJohn:
It may not be the SELinux policies, as I tried.

1. Deleting the SELinux policies adjustments within the module does not solve the issue. These were causing a bootloop straight into the bootloader on a spare phone running Android 10. However, deleting them stopped the bootloop on the other phone, but did not stop the driver install loop. It could actually be something specifically missing in the ViperFX Magisk module. Viper is closed source, but it would be interesting to see the actual check performed in code, deciding if to pop up the driver install, to see what it *thinks* its missing.

2. I tried running permissive, and still the driver install re-occurred. ie every SELinux policy restriction was allowed to pass.

FYI: I originally got Viper to work on my test phone, running LOS Android 10, but I just noticed it too is now not working, and asking to install the driver.

Just had a thought, might give the flashable ZIP version a go :fingers-crossed: I am sure I have seen one floating around, and even think I already have a downloaded copy on my disk.
[Magisk] thunderteaser:
Your testing actually tells me that it is indeed something related to how Magisk is now treating SELinux, as it acts like it's never changing to Permissive properly.

FYI I have just created an issue on github, hoping it gets some attention.
[Magisk] testz:
I am a bit frustrated because I did not found any solution in other threads. If the bootloader is unlocked maybe the patched recovery is lacking some checksum to pass. Could someone with samsung experience check this and help to solve this problem (this phone first firmware is android 10).

:good: thanks
[Magisk] netcracker:
My device is not passing safetynet, bot basic integrity and cts profile are false. I'm using resurrection remix rom and android version 7.1
[Magisk] Ekagra69:
Using AEX pie and got the same problem dude, my kernel requires SELinux to be permissive to work properly although i checked another versions and last version working for me is v20.1
[Magisk] Tom_Scott:
Thank you for the hint. Unfortuately I dont know a valid fingerprint working with LineageOS. I do not have a clue what shall be the right fingerprint to fill the 'ro.build.fingerprint' property.
[Magisk] surya_27895:
my banking apps is not listed on magiskhide so i can't hide it, any solution for this?

i installed the apps defaultly from the play store

use magisk 20.3 and manager ver 7.5.1
[Magisk] Didgeridoohan:
Then use the module mentioned in that link and pick one from the included list. Any fingerprint works, as long as it's certified.

What app is that?
[Magisk] surya_27895:
this one

https://play.google.com/store/apps/details?id=src.com.bni

but already solved by disable the app from realme payment protection apps, maybe another oppo/realme user that get this error can try this if had same issue

Thanks before :D
[Magisk] Didgeridoohan:
That's great to hear. But, now I'm curious... What is the Realme payment protection app? Never heard of it before. What does it do?
[Magisk] surya_27895:
It's a built-in app from realme that include in one phone manager ( i think oppo have it too since it also use colorOS)

this is some ss from the apps

I don't know how it works but i think it somehow protecting user before do payment or anything like that

also an icon will show on the notification bar and say that you is at "Secure Environment" if the security check passes
[Magisk] Tom_Scott:
Thanks, I will use that module and one of the proposed fingerprints. I will inform about the result. Thank you.

Update... 2 hours later: Now it works. The ctsProfile check is now passed. Thank you :)
[Magisk] pranjal_3029:
Hey guys,

I think I discovered a bug, if you can recreate the steps let me know.

Steps to recreate the alleged bug:

Wait for a Magisk Manager & Magisk update(both should be available to update)

Click on Magisk Manager update button

Click on Changelog

Click on cancel

Click on Magisk Update

Now check if the info box is showing Magisk Manager update details or Magisk update details?

For me it's showing Magisk Manager's details again and never the Magisk update details.

Device used: OnePlus 3 on OOS 5.0.8(8.0)

Magisk Installed: v20.1

Magisk Manager installed: v7.4.0(253)
[Magisk] ktmom:
I think that is designed behavior. If you try to update Magisk from within the manager, before updating the manager, it directs you to update the manager instead.
[Magisk] Yus86:
Hi everyone, I have a OnePlus6T with LOS16.

Why don't I have the SafetyNet test here?

Thanks :)

https://framapic.org/YmJIYTHWYZRQ/BY6On66VVIFz.png

https://framapic.org/DijocTRADurY/7JQl3NDLTh9T.png
[Magisk] Didgeridoohan:
Do you have Google services installed on your device? If you don't (and specifically the Google Mobile Services, com.google.android.gms) the SafetyNet check won't show...
[Magisk] Yus86:
True. No Google Apps installed. Thanks
[Magisk] Tom_Scott:
Now all works fine for me. Also ctsProfile check is ok. But one marginal thing is left: Everytimes when my Smartphone is reset I have to disable and enable 'MagiskHide' in the MagisManager settings. Maybe this is an issue and can be solved in one of the next releases?

Greetings

Tom
[Magisk] thunderteaser:
When you are on 20.3 if you manually set SELinux as Permissive (open a terminal, type "su", grant superuser permission, type "setenforce 0") will the kernel features you are talking about start working again? If you could test this I could report that in the Magisk issues thread.
[Magisk] guest4711:
That's a know issue on some devices but hard to analyze without logs. And (for me) it is a intermittent problem: Whenever I try to catch proper logs everything works as it should.
[Magisk] robbyoconnor:
Magisk Manager is weird on Canary...
[Magisk] jcmm11:
New manager design. Bugs or ui suggestions should go in Canary thread.
[Magisk] BigJeff:
Looks like on my Ulefone Armor 7 is non A/B and is using system-as-root according to my results from here https://topjohnwu.github.io/Magisk/i...sk-in-recovery

I can't get a modified recovery.img (our devices only option) to successfully boot, Any advice? Once I modify it with magisk, making sure the box is ticked that its a for recovery.img, it just boot loops until I reflash a stock recovery.img

---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------

Looks like on my Ulefone Armor 7 is non A/B and is using system-as-root according to my results from here https://topjohnwu.github.io/Magisk/i...sk-in-recovery

I can't get a modified recovery.img (our devices only option) to successfully boot, Any advice? Once I modify it with magisk, making sure the box is ticked that its a for recovery.img, it just boot loops until I reflash a stock recovery.img
[Magisk] BigJeff:
Looks like on my Ulefone Armor 7 is non A/B and is using system-as-root according to my results from here https://topjohnwu.github.io/Magisk/i...sk-in-recovery

I can't get a modified recovery.img (our devices only option) to successfully boot, Any advice? Once I modify it with magisk, making sure the box is ticked that its a for recovery.img, it just boot loops until I reflash a stock recovery.img
[Magisk] Slim2none4u:
Upgraded manager, rebooted and then did a direct install to upgrade to the latest Canary and this was my result. Gonna try flashing the latest firmware and patch the boot image and flash in fastboot to see if it fixes it. Fingers crossed.
[Magisk] ktmom:
Give the canary build a try.
[Magisk] kamikaze702k:
New ui update.... Previous was perfect, this will take some getting used to I guess
[Magisk] warrencoakley:
Yeah not feeling the layout of the new Magisk Manager. It's to busy and cluttered looking. Please put it back the way it was John.

---------- Post added at 08:24 AM ---------- Previous post was at 08:19 AM ----------

Hey can you put back Magisk Manager the way it was? The new version is very busy looking and cluttered. Not feeling it at all.

---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------

Hey can you put back Magisk Manager the way it was? The new version is very busy looking and cluttered. Not feeling it at all.
[Magisk] Ubimo:
I also don't like the new Manager.

Where can I find the changelog in new Manager?
[Magisk] stathis95194:
It's on the download button of manager
[Magisk] JudgeDread11:
If the new ui feels too cluttered change the rows in settings to 1.

This made feel much better for me at least.
[Magisk] aurocha:
I recently found out a few files and I don't know where they are located.

Steps to reproduce:

* Magisk Manager > swype right for Modules > press the "+" (plus sign) > fires up DocumentsUI in the Recents tab. A list of files that aren't anywhere on the internal memory appear.

Example, I have a kernel file, I tried to decompress it and install it but it obviously failed.

These files are somewhere, maybe in some Magisk mountpoint I can't discover. And even if I install, lets say, Miui, and repeat the steps, there are the files again.

Screenshot of said files attached.

Any ideas?
[Magisk] Didgeridoohan:
That doesn't have anything to do with Magisk. It's just the standard Android file explorer and you're seeing recently used files, that's all.
[Magisk] kamikaze702k:
I would also agree that the new ui is not eye friendly nor easy to navigate as it was previously, simple, fast, effective, not sure why it needed to be changed but I hope it does go back to what it is also.... New changes I feel should be an improvement on previous designs, seems this took a step back
[Magisk] SketchSlayer:
Anyone Who is familiar with differences in features across android builds know which builds magisk will show the option to rename magisk in? (Pretty sure it was there in 6.x but recovered my OPO to a default 4.4 after a bootloop & I cannot see it so I'm guessing the option isn't available for 4.4 and is for 6.)

Just asking so I know which roms to consider using since being able to properly hide magisk from various applications is kinda useful.
[Magisk] dcarvil:
One of those looks like a LineageOS update files. Those files are in /data/lineageos_updates. You won't see them unless your file explorer can access root files.
[Magisk] zgfg:
Aren't you talking about renaming Magisk Manager, not Magisk?

That has nothing with the Android version but about the version of Magisk Manager - if you have a pretty old Magisk Manager, there was only the option to repack MM, but it was not possible to define how to rename it
[Magisk] SketchSlayer:
I am referring to renaming the manager as many things detect it by checking app names and do have the latest version (I had it self update because the files I had on hand were 1 version older), the repack or renaming or whatever option doesn't appear to be there which is why I'm assuming it relates to the rom being droid 4.4
[Magisk] zgfg:
Ok, but again, MM is an application with various options, one of them being to repack and rename itself.

That option does not depend on your Android version.

Check what is your MM version (old MM versions did not have that option), latest Canary MM has completely new design (and people reported problems about repacking), also if MM is already repacked and renamed the option will be disabled
[Magisk] BigJeff:
Tried it, still bootloops until a stock recovery.img is flashed... guess ill wait till someone hopefully ports TWRP
[Magisk] RandomPooka:
This might be a stupid question, but is your bootloader unlocked already? Many, if not all devices won't boot an image that isn't signed with the factory key, so it wouldn't matter what method you used to flash a modified image. The fact that it's a modified image at all would be your problem here, and that's device dependent at that point, and not really a Magisk issue.
[Magisk] Jiggs82:
Hey is anyone getting fc's on module's section in the bottom on the new Magisk Manager canary apk? TIA
[Magisk] hw-schrauber:
Hi, I've tried to install magisk. APK (7.5.2) installed on Android 9 (Kernel 4.9.117). Then I patched the boot.img. Why the patched image is only 7,34 kb but the original boot.img is 16.385kb? What's wrong to me?
[Magisk] Tulsadiver:
I don't seem to be able to install magisk modules that are not in the download sections, like from my phone in file manager...
[Magisk] Didgeridoohan:
Do you mean on the Canary Manager with the new experimental UI?

If so you're going to have to provide more than that, because I've had no issues with manual installation when testing.
[Magisk] jcmm11:
Nothing wrong. Original boot image is padded with binary zeroes to the size of the boot partition. The patched image removes the padding