yashsingh1/xdaforums huggingface dataset:
[Magisk] rignfool:
Ok... Here...

First... If you're not getting prompted by TWRP for your decryption password... You're gonna need to update your recovery... Beat your TWRP dev with a stick...

Second... If you do get prompted... There is a default password... I forget but it's similar to 'default_password'

Third... If you wanna pass safetynet... You need a ROM that can accept magisk... One without a prepatched boot.img... Beat your ROM dev with a stick...

Fourth... If don't wanna use magisk... Go with a CM based ROM... And use iSU... I THINK that might still work
[Magisk] FlyGuyPanPeter:
yes but then i lose my encryption ))
[Magisk] Didgeridoohan:
Yeah... As already suggested (and like I wrote earlier) you'll need to first type su in terminal. Then the commands.
[Magisk] Artim_96:
That's the point... Thank Samsung with their catastrophic alterings of Android causing more problems then solving
[Magisk] rignfool:
But why keep it if you can't fix your phone?
[Magisk] FlyGuyPanPeter:
The only reason I want use Magisk is because of the Hide Root feature. If I need to lose encryption for the Hide Root I will not do it. I can live without hiding root but can not live without encryption ))

SUHIDE and Magisk Hide are the only Hide Roots which I know...
[Magisk] godstriker8:
Sorry, my bad. I redid it and this is what I got:

u0_a98@OnePlus:/ $ su

WARNING: linker: su: unused DT entry: type 0x6ffffffe arg 0x17c8

WARNING: linker: su: unused DT entry: type 0x6fffffff arg 0x1

root@OnePlus:/ # sh /magisk/.core/magiskhide/disable

MagiskHide: Stopping MagiskHide daemon

MagiskHide: Killing com.google.android.gms.unstable

MagiskHide: Killing com.nintendo.zaba

MagiskHide: Killing com.snapchat.android

1|root@OnePlus:/ # sh /magisk/.core/magiskhide/enable

MagiskHide: Removing dangerous read-only system props

MagiskHide: Killing com.google.android.gms.unstable

MagiskHide: Killing com.nintendo.zaba

MagiskHide: Killing com.snapchat.android

MagiskHide: Starting MagiskHide daemon

WARNING: linker: /magisk/.core/bin/magiskhide: unused DT entry: type 0x6ffffffe arg 0xac8

WARNING: linker: /magisk/.core/bin/magiskhide: unused DT entry: type 0x6fffffff arg 0x1

root@OnePlus:/ #
[Magisk] Xephyrex:
Thanks for the response, I actually switched back to an enforcing ROM and safety net passes completely fine with Magisk hide enabled. Since you say that safety net should pass on the permissive ROM, how could I check what is actually causing safety net to fail if I switch back to the permissive ROM? Thanks again
[Magisk] Jarrid42:
I get this same error when trying to install magisk over supersu S3. Any support?
[Magisk] Artim_96:
What about getting rid of supersu first?

But your problem is /system can't be mounted, so maybe try to do so manually. If that's not possible you probably have some other issue. Then we need logs
[Magisk] Jarrid42:
I believe this is the right one.
[Magisk] Jarrid42:
And so what manually? How do I do so?
[Magisk] rignfool:
I'll bet system is pre mounted... So mounting fails...

Main menu... Mounts... Uncheck system...
[Magisk] Jarrid42:
Unchecked and tried to flash, still won't work.
[Magisk] rignfool:
Ok... Then why can't TWRP mount system...

F2FS on system?
[Magisk] Valiante:
I'm trying to run ADB to access a file but it keeps tell me "permission denied".

Within Magisk I have it set to "Superuser access: Apps and ADB".

When I type my command in Windows Powershell, it gives me the denied message. When I type "ADB SU" or "ADB Root" it gives me "adbd cannot run as root in production builds".

No SU prompt appears from Magisk at all.

I have tried the same from Terminal Emulator on the device as well, nothing happens.

Any ideas?
[Magisk] Didgeridoohan:
Magisk Hide should be able to use the pseudo-enforcing mode to mask SELinux being permissive, yes.

What's causing SafetyNet to fail on that other ROM is hard to say without details and logs... Could be a number of things. The most common of which I've collected in the thread I talked about earlier:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] Jarrid42:
What do you mean?
[Magisk] Didgeridoohan:
Hmm. I think I've seen something like that before. Can't quite remember, but I think it has something to do with your kernel... Someone with a bit more knowledge about the inner workings of Android is gonna have to take a look at that one.

---------- Post added at 01:28 ---------- Previous post was at 01:09 ----------

Try running this in terminal emulator before trying ADB root:

su
resetprop -n ro.debuggable 1

It'll make your device seem like it has a development build and ADB root should work.

Since I've never actually tinkered with this myself, the above is pure guesswork from a simple Google search for "adbd cannot run as root in production builds"...

Good luck.
[Magisk] godstriker8:
Bummer, but thanks for the help. I'm going switch back to a previous backup before I installed magisk, because now my battery is draining super fast.

Android OS is somehow more battery intensive than the screen and YouTube since I installed magisk lol
[Magisk] Artim_96:
I bet you run a Samsung device? Encrypted? That would explain everything

---------- Post added at 12:39 AM ---------- Previous post was at 12:37 AM ----------

It seems to be ext4, at least it looks like that in the recovery log. I'd guess encrypted Samsung device. Normally only /data should be encrypted, but then it's Samsung, they love to mess everything up.

Otherwise his TWRP would need to be bugged. But it's v3.1, and system doesn't look like F2FS, so that shouldn't be the problem
[Magisk] SalmiakDragon:
I do believe I was full stock. Just to be sure I uninstalled Magisk, cleared cache and Dalvik and flashed stock ROM. Magisk v11.6 still just wouldn't give itself root permissions.

I tried Magisk v11.1 instead, and it works better than even v12 in the sense that it isn't constantly rebooting my phone. However, I still can't pass SafetyNet. I saw in the logs that Magisk wasnt unmounting folders properly, but I'm out of ideas on how to fix that since I tried the usual stuff already (details:

Never enabled Busybox.

The kernel seems to support logcat since

logcat -b events -v raw -t 10

produces non-error output ("[1,*net_scheduler*]")

Logger Buffer Size is 256 kB.

).
[Magisk] Jarrid42:
Marlin
[Magisk] Artim_96:
That's strange. Then you should go to the TWRP thread of your device and ask them why you can't mount /system
[Magisk] teddy0209:
There is another one, phh hidesu... Passing SN is another story though, aside from hiding root, there are other requirements...

Edit: Have you tried using rootswitch? Download and install that app, it might work with your setup, It can disable root if you need to...
[Magisk] teddy0209:
Look for the tips and tricks thread, most of the issues with magisk, you can find it there...
[Magisk] DodoGTA:
It's a Google Pixel (Google Pixel support for Magisk is in progress)
[Magisk] Didgeridoohan:
You've gotten the same advice four times in a row... Maybe it's time to start heeding it?
[Magisk] Xephyrex:
I have read your signature post but in terms of interpreting the log, how do I know what's causing what

---------- Post added at 07:36 AM ---------- Previous post was at 07:28 AM ----------

I saw the bit about some custom roms that will always fail safety net no matter what you try. I'm afraid if this is the case here, with my current rom (https://xdaforums.com/note-4/development/rom-nemesis-refined-v3-5-n7port-t3587637). How would I confirm this using the logs, I couldn't find anything in the post relating to that. Also, if this is the case, then does that mean that I'm out of luck for this rom ever passing safetynet?
[Magisk] Didgeridoohan:
If you've gone through that thread, tried the applicable tips and still can't get it to work, then I'd ask for you to post details as to what you've tried, the results from that (things like: does Hide work on a root checker, does basic integrity report true, and so on), the Magisk logs, etc. As much details as possible. Makes it easier to troubleshoot...

If you get basic integrity reporting as true on that ROM, but CTS profile mismatch, there's a possibility you won't be able to pass SafetyNet fully at all. It's hard to say for certain though...
[Magisk] teddy0209:
You just have to start reading mate... Read and read... If root hiding is working, and SN still fails, next would be to try all the tips... For example, make SN think you are using an official rom, but actually on a custom one, and finally passing the check... ???
[Magisk] Xephyrex:
Thank you for the clarification! I've reached the limit of XDA likes :rolleyes: I will try and get some info when I do get the chance.
[Magisk] Shen Ron:
WARNING TO ANYONE WITH XPOSED INSTALLED. XPOSED FRAMEWORK WILL CAUSE SAFETYNET TO FAIL NO MATTER WHAT YOU DO UNLESS YOU DEACTIVATE IT OR UNINSTALL IT.
[Magisk] Som3guy:
I tried to uninstall the Magisk Manager and reinstall it but did not help. But where can I find an earlier version of Magisk? I tried searching for it but can't find for example Magisk 11...

Also I don't completely understand this Boot.img file. I don't have one and a google search did not really help me understanding where to get one/create one.
[Magisk] DodoGTA:
See the attachments in post #1 of this thread: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] Tesla:
1. What phone do you have. This is what i get from google when i search for Samsung Note 4 Boot.img

2. Let's take a look at the Magisk main thread. Well.. look at that. There they are, all shiny and chrome.

[2017.4.26] Magisk v12.0 - Root & Universal Systemless Interface [Android 5.0+]
[Magisk] fredfred41:
Hi,

Is there a v12 fix for adopted storage, or a previous version working with adopted sd storage. (and where could I find it)

I have a honor 8 (frd-l09), official rom B380 - android v7.0 - EMUI 5.0.

v12 installation with Magisk manager allways faill

I also tried to reinstall the latest downloaded zip with my twrp recovery, a crash happen during installation process and reboot to system, even when reboot after flash option is not selected.

any help?

thanks
[Magisk] MultiCulti:
Hello friends,

some Huawei Users here maybe?

I rooted my Mate 9 Pro with Magisk v12, BUT as soon as i tick Hide nd reboot, my phone gets unusable, cant enter the Pin anymore!

And also, if i activate Hide, i still can't login snapchat!

Maybe any suggestion for me :highfive:
[Magisk] Didgeridoohan:
There's no unmounting of necessary folders being done... Looks like process monitoring isn't working. Check the troubleshooting link in my signature and scroll down to "Magisk Hide isn't unmounting folders as it should". There's a couple of thing you could check for there... If you're lucky, one of them works.
[Magisk] culiacanazo:
Woah! I'm glad I'm no dev! That's a lot of beating!
[Magisk] ridobe:
Appropriate avatar.
[Magisk] MultiCulti:
Ok, the only thing is, what i found, i got the ro.build userdebug in the build.prop ... can i change this without any troubles?
[Magisk] Didgeridoohan:
That's not your issue... You've got issues with Magisk Hide's process monitoring. It can't hide Magisk for you.
[Magisk] medes22:
Do you have built in busybox checked?

Uncheck it and see that no more problem
[Magisk] MultiCulti:
hm, okei, but thats the only thing i can find on you vuide -.- or i'm blind

may this help to find the issue?
[Magisk] Didgeridoohan:
Like I said, check under "Magisk Hide isn't unmounting folders as it should". I've got three usual suspects listed there. If you're lucky, one of them applies...
[Magisk] MultiCulti:
thx man, got it! Kernel logger wasnt working!
[Magisk] ante0:
Question: How does one build the source?

I mean, I cloned with git, including recursive.

But it only builds and zips 'magiskboot' and 'magisk'... I guess I need su, magiskpolicy and the others as well?

OH, of course, this is v13.

Just checked the unofficial build and that one only has Magisk and Magiskboot, but busybox is there too so I guess that's why there's such a size difference.

Edit: Hmm, doesn't work with my Mate 9 anyway. v12 boots fine, v13 stays at "Your device is booting".
[Magisk] teddy0209:
V13 only works till 0415build... The recent build are not fully working, there has been a lot of changes on the source, so we need to wait until it's ready... Probably snapshot builds will work again when it's getting ready for official release...
[Magisk] Bhujji:
I have magisk manager 4.3.3. I am not sure where the bug is because I can flash some of the modules from recovery and it's working and am also able to delete those one's from magisk manager. But trying to flash it via magisk manager always fails. Magisk hide works and is able to pass safetynet. Some modules when flashsed from TWRP shows error-2, anyone know what it is? Thank you.
[Magisk] V1R4G3:
How are people getting Magisk on the G920T with a lock bootloader?
[Magisk] teddy0209:
You can't, you have to have an unlocked bootloader or a workaround to load modified boot.img...
[Magisk] zeratos:
I am trying to install magisk on my ale l23 with omnirom but every time it installs it from the install button or flash it trough recovery it appears as not

Installed

Can anyone help?
[Magisk] Tesla:
Sorry that i can't help you directly. I have no knowledge of your phone.

But have you asked the developer of your ROM/Kernel about this?

I assume you have unlocked bootloader and meet all required specifikations and have read and search in this and other threads for solutions.

There are link in my sigh that maybe can give some answers.

Provide a logcat plz.
[Magisk] smoothfreeze:
Greetings everyone.

I have a Nextbit Robin device running 7.1.1 and just flashed Magisk. I have root and everything but I still fail the safetynet check. I've tried checking which test I failed and it turns out that I pass Basic Integrity but failed the CTS profile mismatch. I've tried Magisk Hide and rebooted a couple of times - still no go. Root is working normally, though.

Here's the log:
[Magisk] Didgeridoohan:
I already answered your other post.

Tip: don't cross post...

---------- Post added at 09:50 ---------- Previous post was at 09:46 ----------

Recovery log from installation and possibly a Magisk log pulled from /cache might be useful.
[Magisk] ReaperXIII:
My device is Sony Xperia Z2 D6503, I have tried to install Magisk v12 into Stock Based Mod ROM and AOSP Based ROM.

Case 1 : AOSP ROM LineageOS 14.1 + Xtrememusic Sound Mod v8.1

- The ROM only pass Basic Integrity test without root.

- After install Magisk with Magisk Hide enabled, pass both CTS Profile and Basic Integrity.

Case 2 : Stock Based Mod ROM eXistenZ Marshmallow v5.6.5 + Custom Kernel Elite V3 + Cyberian Camera Mod v7.4 + Xtrememusic Sound Mod v8.1

- This combination will fail both CTS Profile and Basic Integrity out of the box

- Able to install Magisk without problem

- Once activated Magisk Hide, the device will reboot after a few seconds boot into home screen.

- The reboot will go away once I disable Magisk Hide (I still fast enough to disable the Magisk Hide before it reboot)

Case 3 : Stock Based Mod ROM eXistenZ Marshmallow v5.6.5 + Cyberian Camera Mod v7.4 + Xtrememusic Sound Mod v8.1

- The ROM only pass Basic Integrity test after permanently unroot (SuperSU pre-installed)

- Able to install Magisk without problem

- Able to activate Magisk Hide, pass both CTS Profile and Basic Integrity :D

- However if I reboot under Magisk Hide activated, the device gets into bootloop (just before gets into homescreen, the device reboot)

- I have tried to uninstall and reinstall Magisk, the bootloop would not go away

I'm currently in Case 3. My problem is if I ever got unlucky when the device reboots with Magisk Hide activated, I can only give up on Magisk and install another root or reflash the whole system. Is there a way undo the changes of Magisk Hide?

p/s: I know I can just go back to LineageOS, but it is the quality of the camera that brings me back to Stock Based ROM ;)
[Magisk] gasaum@hotmail.com:
Hello, my friends!

Extremely newbie question: let's say my device is already rooted. After flashing a new rom, do I need to flash magisk again?
[Magisk] karthik km:
If you do clean flash then the answer is yes you need to flash magisk again

If you do dirty flash the answer is no
[Magisk] gasaum@hotmail.com:
Does that means that the clean flashing unroots your device?

Considering this, wouldn't it be better to unroot before flashing a rom? Does this make any difference?
[Magisk] karthik km:
Firstly clean flashing which means wiping all partition before flashing new ROM

So where is the matter of root or unroot
[Magisk] biggdevon:
Some roms comer pre- rooted. If you want to use Magisk you'd first have to unroot then flash Magisk. If you can find an unrooted boot.img from your ROM flash that after unrooting, then Magisk
[Magisk] culiacanazo:
Doesn't dirty flashing just keep the manager while effectively removing Magisk?
[Magisk] karthik km:
May be in some cases

Because of boot.IMG flashes again over current boot
[Magisk] ante0:
Any of you have the source of v12.0?

I can only find the archived version of 11.6.

I need to change a line in magiskboot... And the current git commits make it impossible for me to boot.

No need anymore. Git checkout worked out eventually, after going through the submodules.
[Magisk] teddy0209:
Yes... Unless the rom comes with magisk...
[Magisk] Rootax:
OnePlus 3T beta 6 => Magisk is not hidden anymore. Was hidden with beta 5. For the record..
[Magisk] culiacanazo:
Cool, cool. Thank you, thank you.
[Magisk] Wwzz:
Magisk v12 safetyNet not working on my galaxy s4 lte-a (android 5.0.1)
[Magisk] Nitrogen:
Same for me. Damn!
[Magisk] Midomad:
Let's just wait for a new update,

It's a known problem with beta 6 Magisk need no be updated to support beta 6 and 15.
[Magisk] Didgeridoohan:
I took a quick look in the OOS Open Beta 6 thread and didn't see anyone providing any details or logs, so I'd like to ask you guys for some info. I'm the curious kind...

Have you made sure that Magisk Hide actually starts on boot? You can see it in the logs... Have you tried the usual solution of toggling Hide off and on again? And, for the kicker: Could anyone provide a Magisk log?

Thanks for the info.

Or, if you're trying to ask for help:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

---------- Post added at 21:24 ---------- Previous post was at 21:20 ----------

For the Manager: provide a logcat from installing through the Manager together with the Magisk log after rebooting.

For error in TWRP: provide the recover log from the failed flash.

The above mentioned info would make it a lot easier to help...
[Magisk] Joshmccullough:
Same with OP3 Beta 16; was working with B15, but whatever they changed broke the SafetyNet 'hide'.

Question to whomever: Would a log of some sort help, or is it one of those things where there'll be enough people with the same problem that it'll just get fixed in the next update?
[Magisk] Bhujji:
I hope these are the logs that you asked for, if not sorry let me know.

Magsisk Manager Log- https://pastebin.com/ZPXNJriy

TWRP Log- https://pastebin.com/cQZ78K3h
[Magisk] Tesla:
Sorry to hear that m8.
[Magisk] laggardkernel:
A/B devices are not supported by Magisk.

---------- Post added at 01:12 AM ---------- Previous post was at 12:59 AM ----------

Try to use this in recovery,

echo 0 > /data/property/persist.magisk.hide

BTW, the only magisk module you were using is Xtrememusic, right?
[Magisk] siuburu:
Does Magisk work on Xiaomi phones with Android N based MIUI? Can't make it work on my mi4s.
[Magisk] ReaperXIII:
Thanks, I will try it when I have time. I didn't install Xtrememusic as magisk module, just a normal flash app.
[Magisk] Artim_96:
At least when he wants to update through OTA
[Magisk] mati_boy:
that reboot shouldn't make a problem for magisk
[Magisk] adrman:
First, I'd download, unzip and study the Magisk Module template from the OP, so you can get an idea of how to make your own modules. Then, you can head over to the Magisk Module thread and check out some of the modules there. For example, there's an Action Launcher module there, but I modified it for Action Launcher Pro. There's a Nexus Launcher module there as well, but I haven't tried it.
[Magisk] foxdog66:
I have a few questions about the cache mode...

Can't all apps write to cache without any special permissions? Cache mode scripts run in boot, correct, with elevated privileges and without any notification? Seems very unsafe. Can cache mode be disabled?
[Magisk] putridfoetus:
I'm on a Nexus 6. I think i still had some remnants of SuperSU left over from before Magisk, so i'm wiping everything and starting fresh.
[Magisk] kryzeK:
Deleted
[Magisk] JudgeDread11:
Magisk is a powerful tool that, like Xposed or any app using root or any flash action, can be misused by people with bad intentions.

If you don't trust a mod, don't install it, or check it first (is all open source)

The safest option is to not modify your phone and only use it as it is out of there box.

This is why every developer states they are not responsible for what you do with your phone.
[Magisk] topjohnwu:
Hmm.... Do you know how SELinux works? :) Nothing in cache has higher privilege.

Magisk scripts always run in higher privilege, there is no difference in which modules it is, where it is stored.

Something similar to root, when you grant root access to one app, you actually created a hole for that app. The modern root solutions also deal with SELinux, so the protection of SELinux is also limited for root granted apps. In most time, the protection of SELinux is removed when you grant root access, as both SuperSU and phh will run the process in permissive mode, and SuperSU also support changing the policy in realtime. I ported similar features to phh in Magisk.

So if you are concerned about security, you shall never mess up your device in anyway :D
[Magisk] soder:
Great. Thanks. To bad I had to re add all icons on the screen since the last time I used Nexus launcher.

With BBS, I know have two apps. Will try to reboot.

Edit: uninstalled and reinstalled the XDA version.

/Söder
[Magisk] stangri:
You may use it to turn the the app/library/module requiring to be written into /system "systemless". Like you can use it to create Action Launcher flashable zip which will not write to /system (allowing you to flash OTAs) but which would still behave as if it was written to /system (access to Google Now side panel).
[Magisk] Basic11:
Have anybody tried logging in snapchat without any problems?
[Magisk] iscaela:
I can confirm my 2013 Moto X XT1058 also does not respond to touch after installing Magisk.

ROM: Stock Android 5.1 (222.201.1.ghost_att.ATT.en.US LPAS23.12-21.7-1), not rooted

Restored system to stock

Flashed Magisk v6 with TWRP, wiped Dalvik cache

Rebooted system, boots to home screen

Touchscreen does not respond, but power and volume buttons work

Always-on Moto Display (Active Display) is missing, screen remains black while asleep instead of showing active notifications

My log has the same contents as Rahh1112.

The problem is probably related to the Moto Display (Active Display) feature of the Moto X. I think this uses a coprocessor to show notifications on the AMOLED display while the phone is sleeping and is able to respond to touch to unlock the phone. Modifying the boot image for Magick probably breaks the Active Display software and causes the phone to stay locked or not forward touch input.

It appears any other modifications to boot.img, such as installing the regular version of phhusson's Superuser, also cause the same problem.

I'm attaching the original boot.img for Moto X XT1058 LPAS23.12-21.7-1
[Magisk] sooyong94:
I did a systemless root and magisk manager shows root status not rooted and selinux enforcing. This should be OK right?