yashsingh1/xdaforums huggingface dataset:
[Magisk] :
I meant that I am willing to install one of them for my Zenfone 2 which is a x64 device...
[Magisk] Didgeridoohan:
And I meant that you should... :laugh:

Forgot to add one thing though: If I remember correctly, Asus devices need to also sign the boot image, with a tool like this:

https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606

Flash that after Magisk and you should be good to go. Choose v16.0 or v16.3 beta, whichever should work.

And lastly, a tip. Usually, if you have device specific inquiries, it's best to bring those to the device's forum...
[Magisk] :
Ok, in Zenfone 2 there's a thread that have a zip that can help me to sign the boot image :)

But because I was seeing the changelog that about x64 or something... So that I was worried :)
[Magisk] Didgeridoohan:
The 64-bit thing is only for the v16.4 beta, and the issues around that are being solved and tested internally right now.
[Magisk] ketwi15:
Guys I think Snapchat detects Magisk and is handing out temporary bans now.
[Magisk] Didgeridoohan:
Snapchat added to the Hide list, the Magisk Manager hidden (repackaged), and using Magisk v16.4 beta with the improved MagiskHide?
[Magisk] ketwi15:
I've been using 16.0. I'll use the beta and get back if it happens again.
[Magisk] Vinnipinni:
Having a lot of trouble with installing modules. Getting the same error among all modules I try to install.

Pixel 2 XL on Android P DP2
[Magisk] bisherbas:
Repeatedly crashes upon launching the app

Second attempt works all the time. However, if i make another attempt within 2-3 hours, the app crashes immediately without showing the GUI. Again the second attempt is successful. Log is attached.

Device: OnePlus 5T

Root: Yes, Magisk only. No SuperSU. No Xposed.

OS: OxygenOS latest.

Kernel: Default. Whatever comes with the OS. Not overwritten with another one.

Any other information should be I providing?
[Magisk] IscreaMan:
After 2-3 hours (sometimes after several minutes) magisk "dissapears" - no root, safetynet fails, "not installed" shows up.

I have to reset phone, than it gets back to normal, but after another 2-3 hours it's "not installed" so i have to reset my device 5-6 times a day.

Samsung Galaxy Note8

Magisk v16.0 and v16.4

no modules - only root + magisk hide for Google Pay

Thank you in advance for any help!
[Magisk] martyfender:
What is your Magisk Manager version?
[Magisk] bisherbas:
Sorry I forgot to include it.

Magisk v16.0

MM v5.7.0 (115) (ccm.topjohnwu.magisk)
[Magisk] martyfender:
The Magisk Manager crashing is supposed to be fixed in that version, however, I occasionally also have it crash and I am on the unofficial, 5.7.0 180506.
[Magisk] thisguyy:
I haven't been able to use it for the last week now. I keep getting the can't log in message I think they're detecting roots a different way now.
[Magisk] unRevealed:
Anyone knows what I should do to make my Magisk Hide working?

I need to use it to hide the root access from my banking app. I've been listing the app in the Magisk Hide but it still doesn't work.

I've tried any other way like hiding Magisk Manager and downloading MagiskHide Props Configs and then activating the Improved Hiding features but it still doesn't work.

What happens and what should I do?

I use Magisk v16 and Magisk Manager v5.7 (I restored the Magisk Manager after finding out that hiding Magisk Manager wouldn't work). It passes the SafetyNet Check just well.
[Magisk] Didgeridoohan:
Obviously, MagiskHide works on your device, or you wouldn't pass SafetyNet.

I would try two things:

Make sure the app is on the Hide list, hide the Manager, clear data for the banking app, and try again.

If the above doesn't work, try by installing the v16.4 beta (note that you might have some issues with some apps if your device is 64-bit), since it has a slightly improved MagiskHide.

Don't forget to clear data for the banking app every time it has detected root while experimenting. Sometimes apps "remember", and won't work again until you clear their data.

It's also very possible that the app is detecting a different root app on your device, one that Magisk can't hide.
[Magisk] Augustoandro:
Magisk Hide is not working.

Whenever I mark an app in Magisk Hide, it is unmarked the moment I exit Magisk Manager.

How can I fix this?
[Magisk] Didgeridoohan:
Always provide at least a Magisk log when reporting issues. And details about your device, ROM, etc, it's also good.

It could be a number of things (yes, it's been covered before), and it's a lot easier to narrow down with some more info...
[Magisk] Nozomi9090:
Hi man. How to fix ? (Huawei p9 lite, nougat, patch full update) https://preview.ibb.co/nAqpbJ/32508360_10216629198388148_3436485474779136000_n.jpg
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] BurnedDrake:
Y'all have something else going on, I've got Magisk 16.0 and Xposed installed and am using Snapchat just fine. You just have to add Snapchat to the hide list before you even try to login
[Magisk] ketwi15:
I've been able to log in. It's just my account has been getting locked. No Xposed or anything
[Magisk] unRevealed:
I've tried what you told me; clearing the data, hiding the app on the list, hiding the manager and installing the v16.4 but it still doesn't work.

When you said "different root app", does it mean an app like SuperSU (which I don't have) or just an apps that need a root access like Busybox, Termux, SD Maid, etc?
[Magisk] Didgeridoohan:
Yes, apps that need root. Typical ones would be busybox installers, system cleaners, system app uninstallers, Xposed installer, etc etc.

There might also be dependencies on other apps/processes.

Grabbing a logcat when the app triggers might show something.
[Magisk] Nozomi9090:
Nope mate, dont work t.t
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] jacobyo7:
Very intresting website you have there, thanks for all this information ! :D

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

I got locked 3 times, on my main phone with magisk + xposed. I was using an xposed module related to snapchat but removed it after the first lock and updated my snapchat to the latest on the play store, but they locked me 2 more times.. now my account is on my secondary phone, wich have magisk but no xposed and I'm not locked anymore on this one. I Will try to get my account back on my main phone later this week.
[Magisk] :
phh superuser shows SU binary out of date after reboot. But it's not causing any issues.
[Magisk] drew071:
MyEE app has started detecting root even though it is hidden in Magisk. I'm on the latest app and 16.5 installed version. It did the same on 16.4 also.

Hope it can be fixed.

Cheers

Drew
[Magisk] :
Can I downgrade from Magisk 16.3 mido treble to Magisk 16.0 mido treble without any issues?
[Magisk] guest4711:
Did you try by hiding (repacking) MagiskManager? MagiskManager -- Settings -- Hide Magisk Manager
[Magisk] Semela:
Is Universal SafetyNet Fix not available for Magisk 16? Magisk fails ctsprofile check. When I had v14 installed I had to install Universal SafetyNet Fix to deal with this problem.

How do I fix this in Magisk 16?

Thank you.
[Magisk] jenslody:
Use [MENTION=4667597]Didgeridoohan[/MENTION]'s "MagiskHide Props Config"-module from MagiskManagers download-section.
[Magisk] drew071:
Yes I did. Root is still being detected by the app
[Magisk] guest4711:
So see https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post76529018 and https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] ksio89:
My device's stock ROM zip includes the stock boot image, however when I flash stock boot.img, won't I lose access to TWRP?
[Magisk] thisguyy:
I stand by what I said, snapchat is updating their system checks because I've even made a new account to see if it was something wrong on my end and even with 16.0 & Xposed, I've already been locked and logged out.
[Magisk] jcmm11:
No. You would have to flash stock recovery to lose TWRP. Extract the boot image and use TWRP to flash just the boot image.

Alternately you should have a gzipped copy of the stock boot image in /data, placed there by supersu when it was installed.

---------- Post added at 01:43 AM ---------- Previous post was at 01:40 AM ----------

Did you wipe data from the Snapchat app?
[Magisk] thisguyy:
---------- Post added at 01:43 AM ---------- Previous post was at 01:40 AM ----------

[/COLOR]

Did you wipe data from the Snapchat app?[/QUOTE]

I did, I even reinstalled the app to see if that would make a difference.
[Magisk] :
From where can I get the next update for Magisk 16.3 mido treble?
[Magisk] Didgeridoohan:
That's an unofficial Magisk build, so you'll likely find it wherever you found the one you currently have installed.
[Magisk] ketwi15:
Yeah and I got locked the next day. I've been good for 2 days after going stock then rooting again.
[Magisk] Paz9:
magisk keeps tripping sn

wont let my apps run, magisk hide doesnt hide apps properly.
[Magisk] Didgeridoohan:
MagiskHide doesn't hide apps, it hides

from

apps.

More troubleshooting here:

https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] rajkatiyar07:
Do somebody know how to enable logd. Its been disabled somehow and now magisk is not working.
[Magisk] Nikolay1243D:
Possible to install this without removing twrp/xposed?

Hey,

I have a rooted yotaphone 2 and I really dont want to remove those programs.

Actually I'd be fine to remove them if I can add them back after installing magisk.
[Magisk] hoeni:
Note 3, custom rom here.

Did a fresh install, full uninstall via SU app, checked for leftover SU data, Flashed magisk and phh in twrp, installed magisk and phh app.

I opened magisk and was asked by phhs app to grant su permissions.

Still, the toggle keeps switching back to root.

Every time I try to switch root off su tells me that rights were granted do magisk. Yet nothing happens.

I know this has been asked 100s of times before :angel:

Seems like either it works or doesn't :crying:
[Magisk] 640k:
hi - on N6P and phh superuser is having a few issues and maybe i'm just being daft...

early on i could easily toggle root mount off/on through magisk manager, however, apps that were already granted root permission through Chainfire's SU were not re-prompting for root. Now I can't get any apps to prompt and root is not possible.

i'm currently having battery issues so i'm considering a factory reset. should i just try reinstalling phh SU? should i clean it all up with a fresh system img and start over?

thanks.
[Magisk] b00tstrap:
Did you start with a fresh system image before installing Magisk? I have a 6P and it seems to work fine. Before I installed Magisk I downloaded a Factory Image for the 6P from Google and fastboot-flashed the following: boot.img, cache.img, recovery.img, system.img, and vendor.img (NOT userdata.img, as that will erase all your app data and the SD card). After that I fastboot-flashed TWRP, then went into TWRP and flashed Magisk and phh's Superuser for Magisk and it worked fine. I'm a little troubled that you mention Chainfire's SU--you did do a full root uninstall through Chainfire's SU before installing Magisk, right?
[Magisk] 640k:
correct. followed directions that were included with this; uninstall first and when i came back, SU was still there. so i did a cleanup for new app. phh has never registered any requests for root.

manager seems to work. safety net confirms this. but i can't get apps/phh to recognize.

also, i don't see a way to update the binary in phh.
[Magisk] b00tstrap:
On the Nexus 6P I went back to the default recovery before installing Magisk, then flashed TWRP back on right before installing Magisk. I think I had to flash it once more after flashing Magisk and booting into the system; now it persists just fine and things seem to work. In the second post of this thread it talks about how to get Xposed back after installing Magisk--hopefully, you've carefully read both the first and second posts of this thread as there's a lot of important information there.

---------- Post added at 09:17 AM ---------- Previous post was at 09:13 AM ----------

Can you list what you did and what happened in order? Something like:

1. I started with the stock Nexus 6P ROM with Chainfire's SuperSU installed

2. I went into SuperSU and asked it for a full uninstall

3. The full uninstall finished and I rebooted--after I rebooted, SuperSU was still there

4. I then rebooted into TWRP and flashed Magisk

etc.

It's hard to comment on how my experience was different than yours without a lot of details listed in order of occurance
[Magisk] 640k:
first - no xposed. so that's a non-issue. steps are essentially as you list them:

1. System was recently updated to 7.0 using flashfire method.

2. Started with stock N6P ROM/Chainfire Systemless Root/SuperSU.

3. Opened SU and selected "Full Unroot".

4. Restarted in to TWRP. Flashed Magisk v6. Wiped dalvik/cache.

5. Rebooted.

6. Restarted in to TWRP. Flashed Magisk Manager.

7. Rebooted.

8. Installed phh SU. Noticed CF SU was still present. Performed Cleanup/Uninstall.

i'm thinking step 8 is where the problem is... but shouldn't an install of another SU allow this to work? even after #8, i still had the ability to manage root, just was not getting prompts from apps.
[Magisk] b00tstrap:
Thanks! So the first comment I want to make is that I'm on Android 6; that's potentially a big factor that could make our experiences differ.

If I were in your position, what I would do is reflash the boot, cache, system, and vendor partitions from the Android 7 image you had in step 1. I would probably use "fastboot flash" instead of flashfire, since your system is in something of an unknown state and I'm not sure how flashfire will respond to it (if you don't know how to fastboot flash I'll point you to some good resources). After doing that, you should be back to a clean system (hopefully with all your user data intact--on Android 6 I'm able to do that without disturbing my user app data or SD card, but you understand that I can't guarantee any result, so you should backup anything important to you).

After getting back to a clean system, I would reboot into TWRP (which you may have to re-flash in fastboot first) and flash Magisk and then phh's Superuser for Magisk, at the same time but in that order! Then you can reboot and install the Magisk Manager and see if it works. If you were on Android 6, I would be pretty certain it should work by then, but there may be incompatibility between Android 7 and Magisk--I just don't know there.
[Magisk] hoeni:
What would you do, on Android 6, if it's still not working by then? And I already wiped dalvik cache as well :)
[Magisk] 640k:
that's what my next step was going to be, but i wanted to hit the thread to see if anyone experienced anything similar. based on the feedback on reddit's N6P forum, users didn't start to get improved battery life until they really started over clean.

with the amount of flashfire flashes i've performed... it's probably time.
[Magisk] b00tstrap:
Which device are you on? If it's not Nexus 6P, I probably can't help.
[Magisk] hoeni:
Considering Magisks multi device support I think it won't make much of a difference.

Everyone uses twrp, magisk and phh, yet for some it works and for others it doesn't :)

I got an s3 lte and a note 3 which I can't get it to work on.

On my s7 edge I found a rom with everything pre-installed, so it works of course.

I followed exactly the dev's instructions, yet it seems like I'm missing something.
[Magisk] :
Tried on the Xperia C3 stock lollipop rom, won't even boot. Guess that's another thing this phone can't do
[Magisk] Blauhasenpopo:
Hi :)

Followed these steps : http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/

..but choose SuperSu instead of phh's Version...and my question is should i install the SupeSu app through Play Store like phh's one ?

Used the special Version of SuperSu from the first page.

Everything worked fine on my Huawei P9 Lite...had SuperSu root and Xposed Framework before the Magisk Version.

Thanks to all the Developers :)
[Magisk] b00tstrap:
Unfortunately, Magisk isn't yet universal, in the first post there's a section Currently Known Not Working Devices (v6). One of the bullets under that section is Older Samsung devices generally (6.0+): sepolicy issues, should be fixed in v7. I would guess that if you followed the procedure I laid out (removing superuser, flashing a clean version of your ROM; installing Magisk and then Magisk phh Superuser at the same time, but in that order, in TWRP; then installing the Magisk Manager) and it still doesn't work, that it's probably because the s3 lte and note 3 fall under the "Older Samsung devices" category.

However, if you'd still like me to examine what else might be wrong, then please list what you did step by step with a lot of details like I mentioned above, and if I see anything that seems like it should change, I'll point it out.
[Magisk] edensites:
Toogle ON dont work?

Hi my friends,

i have 1 question. I do all as in this video youtube.com/watch?v=TBaZpiIDFQ8

But if i go toogle ON (root off) after 1 second button automaticky go back to the toogle OFF (root ON). Can anyone help me please? thanks.
[Magisk] hoeni:
Re-installing everything does take some time so I'll be back in a bit :)

Does it matter at all then that I chose Mm Roms for both devices? Or is it their architecture that makes them old?
[Magisk] Android-UK:
Just wanted to say thank you for making this mod and what seems to be the new standard for su in the future.

my only complaint? Magisk manager is ugly as sin, needs material styling on it. Also a widget to toggle root without going into it would be a huge benefit.

Keep up the good work
[Magisk] hoeni:
Steps taken on my s3 lte:

Flashed AICP rom

Installed chainfires su from play store

Fully unrooted via app

Reboot

Reboot into recovery

Flash Magisk v6

Flash phh su 17

Flash UPDATED UNSURE.zip (found that somewhere. Supposed to be helpful when you're on cm)

Flash Magisk again

Flash phh again

Upon reboot system NO to "wanna root"

Install magisk app, install phh app

Open su app, nothing extraordinary happens

Open Magisk app - root status mounted, selinux status permissive

Root toggle won't stay off

Cry myself to sleep

Edit1

I rebooted into recovery and re-flashed unSU. Now a notification tells me my su binaries are outdated.

Edit2

Flashed magisk and phh again.

Now the notification is gone.

Either way, the toggle won't stay off.

Interestingly enough, Magisk never asks for root access, which is odd.
[Magisk] Paz9:
That's what I mean

If I restore stock ram disk all works fine

When I flash magisk Google pay works but my banking app stops working

Thanks for the link! Fixed!!
[Magisk] mchlbenner:
Why does magisk break volte icon?

Any fix?
[Magisk] Paz9:
not sure if magisk or twrp issue

but i cant install the magisk uninstaller
[Magisk] Ja_som:
Not enough informations to help you.
[Magisk] Didgeridoohan:
[MENTION=2226643]Evengard[/MENTION] I'm replying to you here, since your query doesn't seem like a beta release issue. Have you given your scripts in post-fs-data.d and service.d execution permission? They won't run without it... Permission 755 is the standard.

Not without you providing a lot more details about your issue, what you've tried to fix it (disable Magisk, run in Core Only Mode, etc), and of course logs.

Sounds like you've encountered the 64-bit issue with the latest uninstaller. But, like already stated, it's hard to know for sure with the little info you've given.

Try using the previous uninstaller.

---------- Post added at 09:01 ---------- Previous post was at 08:55 ----------

Please provide additional info... How do you know it's been disabled? Was it working before? If so, what have you changed with your device inbetween? Provide logs (magisk_debug.log, logcat, etc). Etc, etc...

You can run this in a terminal emulator to confirm if things are running as they should or not:

su
ps | grep log
[Magisk] Buxbaum666:
Has anyone found a solution to/reason for this? The same thing happens with my wife's S7 (Stock Nougat ROM, Magisk stable v16.0 was installed via TWRP). The phone will stop reacting at random times for a few minutes (power and home buttons do nothing but the phone is apparently still running) and then reboot. Afterwards, Magisk shows up as not installed in the Manager app and needs to be reflashed in TWRP. Rinse and repeat.

I'm suspecting some Samsung safety "feature" detects that the device is rooted and restores the original boot image. I've tried freezing everything Knox-related and "SysScope", which seems to be some sort of root detection app by Samsung, but to no avail - it still keeps happening. MagiskHide is on, Magisk is hidden from everything apparently Samsung-related I could find.

I will try the random package ID thingy later today, maybe that will help.
[Magisk] Didgeridoohan:
Just rebooting doesn't solve the issue?

I have a suspicion that some of these reports of Magisk "uninstalling itself" has to do with MagiskHide sometimes not being able to remount everything after hiding itself from some app or service.

Yours sounds a bit different though... If you can save the magisk_debug.log from when it happens that would be good. You'd have to prevent the phone from rebooting though, and boot to TWRP to save it from /data/adb.
[Magisk] Buxbaum666:
I haven't tried that but I don't think so.

I think some sort of Samsung security trickery is really to blame here but I'm not sure. I don't know if I'll be able to get at the logfile before the phone reboots. I'm not even sure it does a full reboot - from what I've observed, it goes directly to the SAMSUNG-Logo after locking up so maybe whatever removes Magisk does a soft reboot only? Does that even make sense? I can't double-check right now, I will get back to you.

Edit: Do you recommend using the 16.4 beta?
[Magisk] Didgeridoohan:
If it's just a soft reboot, it shouldn't be any worries. You should be able to boot to TWRP and save the debug log.

I'm thinking that it might actually be the MagiskHide unmounting issue I mentioned earlier, and that it might be some root app you have that suddenly doesn't have root access freaking out and causing your device to lock up. I'm guessing, of course, but it's a possible scenario. I don't think it's Samsung replacing your boot image on a live system... They'd need root access for that...

I'm pretty sure you should be able to get things working again with a simple reboot.

It does have issues with the 64-bit binaries having been removed. That has, from what I've tested, been fixed but not released yet. You could try out the unofficial snapshot provided by [MENTION=3306843]kantjer[/MENTION]. It has those fixes...
[Magisk] drew071:
I found the culprit but I'm not sure how the EE app is detecting root.

Basically I installed Delerium X clean theme on my s7. When I set the theme EE detects root.

When I set default theme EE app works?

Any ideas?

Drew
[Magisk] Didgeridoohan:
It's not uncommon for apps looking for root to have a list of known root apps/services that they look for and take as a sign of you being rooted, even though you've hidden the fact that you have rooted your device with MagiskHide.

Looking for the ripples rather than the actual splash...

Usually not much to do about it, except disable/uninstall the offending app/service when you need to use whatever app is detecting root.
[Magisk] drew071:
Bit odd considering its a theme and doesn't require root or anything.

Cheers for the reply
[Magisk] jcmm11:
These may help get an answer
[Magisk] jenslody:
You shoud at least try it, before reflashing in TWRP.

But if you reflash anyway, you shoud see if magisk finds a already patched boot-image.
[Magisk] Nozomi9090:
I have a Samsung galaxy A8 (2018) SM-A530F.

In download mode FRP LOCK = OFF and OEM = OFF.

I can install twrp and magisk? Installing magisk, will I receive future android updates, or not?
[Magisk] pote2639:
It's just me or magisk hide crashed all my banking apps, the apps name are: k plus and scb easy.
[Magisk] guest4711:
Are you sure it detects root? Or it is crashing because of an incompatible theme?