yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
That's good... :p

Means I can throw that factory image on my old N6 and do some testing myself.

You can also try hiding the Manager (it's in the Manager settings). Since it seems to work for a while, it could be that your Hide randomly stops working on your device... Some more testing and, if possible, logs would be nice. Install the beta version of Magisk v15.3 and save the magisk_debug.log (/data/adb) after the app starts complaining about root. If we're lucky it'll show something...

There's a fatal error 6 in there, for the Manager. Hm... I'm running the same setup on my N6, but haven't seen this. It's not my daily driver though... More details about your device and setup, please.

Could you also install the beta version of Magisk v15.3 and save the magisk_debug.log (/data/adb) after the crash. You'll have to save it before the phone boots again, from recovery.

It's often possible to hide root and an unlocked bootloader with Magisk. It depends a bit on your device and setup though.

Take a look in the installation and troubleshooting guide for some tips.

Logs, please...
[Magisk] admiralspeedy:
That'd be awesome, because I actually noticed that every version from 14.5 to 14.6 (including betas) randomly loses root all the time on me or doesn't work at all, so I'm kinda just stuck at 14.3 for now. If you need me to test anything else, let me know!
[Magisk] elandroido:
Hey,

I have exactly the same problem (even the same device).

Magisk worked perfectly until I switched to f2fs. Now it cannot remember granted permissions.

I have attached log screenshots.

The loopback module would not work for me because I have data and cache f2fs formatted.

Have you (or anyone else) found a solution?

I really want to stay with f2fs, because it improved performance for my usecase quite a bit.

(I probably have to try other kernels).

Gr33z
[Magisk] etmatrix:
I have updated Magisk to lastest stable version 15.3 my previous version was 14. I see strange char appears in file /init.rc after last line

00006950: 2020 2067 726f 7570 2072 6f6f 740a 05c3 group root...
00006960: 043a 03f2 037a 0420 04ff 03ff 0320 040a .:...z. ..... ..

I tried to dump boot.img and unpack it but these chars there are not in file /init.rc

Why? Someone has some suggestions?
[Magisk] siealex:
Where can I get them if it even does not boot up to the boot animation???
[Magisk] EmiRus:
You have to pull them during the booting process directly via adb, i think.

Just google you will find..
[Magisk] siealex:
It stops booting before ADB connection, in this state it is not recognized by PC.

PS, after a clean flash ADB starts working only after full boot.
[Magisk] Didgeridoohan:
There was a commit made recently for the Manager that might fix this issue. You could build it yourself or test one of the unofficial snapshots provided by [MENTION=3306843]kantjer[/MENTION].

You mention that Magisk causes your phone to crash. Try to grab a logcat of the crash.

And if it's not too early in the boot process a logcat when it's looping might show something. Sounds like it's a bit too early though, but worth a shot...

If nothing else works, a recovery/installation log for Magisk and a copy of the boot image might be useful.
[Magisk] siealex:
Yes, it's too early. Where can I get this log?

It's not looping, it simply stops at Google logo and that's all.
[Magisk] elandroido:
I flashed the latest unofficial build from your link, but unfortunately the behavior did not change.

Let me know if there is anything I can provide in order to help.
[Magisk] brag288:
Doesn't work for the app(BT Pay) that the other user is talking about,tried with hiding it and even hiding magisk,still shows as rooted
[Magisk] EmiRus:
[MENTION=1097461]siealex[/MENTION]

If you can try this with adb :

adb.exe logcat -v long > somefile.txt

If not grab twrp log using twrp advanced tap and then log

Log is on sdcard now

Boot img can be grabed from images n5x google site
[Magisk] brag288:
did you manage to get it to work?
[Magisk] Quark^2:
I just got an update notificatation on my Moto G5S (7.1.1 december security update). and thought to follow a procedure I read about before.

Unfortunately it did not work, giving me a scare, but got the phone working again, can anyone tell me what I did wrong?

Disabled automatic updates in developer options

Download OTA by checking for updates (but don't reboot) - it was about 45MB, a small security update.

Magisk Manager: restore images (= restored boot image i assume)

Setup Flashfire to flash:

- OTA update from /cache

- Magisk-15.3.zip

- Disabled Everroot

- Restore recovery

What happened is that Flashfire told me that my system image was modified and I said "ignore". I assume this was my mistake.

I pressed ignore and the phone rebooted immediately. Stayed completely black for 5 minutes.

Restarted the phone by holding the power button. After booting the initial loader screen kept showing, phone did not boot further.

Only by reflashing TWRP in fastboot and clearing cache + dalvik cache did the phone boot again.

What was my mistake? My steps to flash the OTA seemed okay to me....
[Magisk] siealex:
ADB does not connect at all in this situation. I'll try with TWRP.

I'll try with TWRP tomorrow. I need to reflash the ROM, I'm now on SuperSU.
[Magisk] siealex:
Boot image:
[Magisk] DB126:
In your shoes I would reformat cache back to ext4 and go with the loopback module. Cache partition isn't accessed that frequently once ROM boots; performance difference will be negligible. Custom kernels are fine but why change everything just to solve one issue. Just my two cents ....
[Magisk] siealex:
I got these files...
[Magisk] siealex:
Is it safe to try earlier versions of Magisk? What versions run on Oreo?
[Magisk] EmiRus:
Yes it should as somewhere said here in thread

Try and report us ;)
[Magisk] siealex:
The latest beta (1531) also freezes. I'll try other versions later.
[Magisk] petryrety:
nop.... app banking still locked because i don't know how but this app can see root :( :( :( i tried all option... clear data... hide magisk... hide all ... hide life :( :crying: :eek:

PS: i expect to receive a magisk update, hoping the problem will be solved... maybe...
[Magisk] brag288:
same here..no idea what's causing this...using magisk hide and hiding the manager as well
[Magisk] fw190:
Hi! Latest Magisk gives file coruppted in twrp.

I have downloaded twice with the same results. Before this I have unrooted the phone with lineage unroot zip. I'm on nexus 4,lineageos 14.1 latest with xposed for xprivacy lua
[Magisk] BillGoss:
I had to hide the app as well as hide Magisk Manager, wipe the banking app data and reboot the phone. Only then could I set up the banking app.
[Magisk] brag288:
Still detects it as rooted :'(
[Magisk] Didgeridoohan:
If your system image has been modified you can't update with an OTA file. You'll have to update with a full factory image/firmware package/ROM. It's enough to just mount /system rw once to mess it up...

That recovery file is unfortunately unusable, since it's not saved right after flashing Magisk. The recovery log resets every time you enter TWRP.

First, just to make sure, are you downloading from the release thread? Second, try downloading with a different browser. Third, here's the md5 for the Magisk v15.3 zip from the release thread: 93ecc284b92d3f1b7355ad7d0ca3d2df
[Magisk] elandroido:
Thanks for the hint. I tried with ext4 cache and loopback module, but still the same problem. App permission choices are not remembered. So obviously the issue seems a bit different in my case.

This is kinda uncool for me, since I have to go with "always allow" for all Apps so that my desired setup works.

Anyhow I am not an Android noob, so if I can help, any hint would be appreciated.

Also maybe there is a workaround:

Can I manually maintain the "allowed apps" list somehow? Text editor, SQLite editor or whatever format it has?
[Magisk] Didgeridoohan:
I just did a clean install of the October 7.1.1 factory image on my Nexus 6. Started it up, set everything up, installed TWRP, flashed the v15.3(1531) beta zip, aaaaaand... *drum roll*

Sorry mate, but it works perfectly. No issues at all. I don't know what's wrong with your setup, but it's looking like it's something on your end.

---------- Post added at 22:15 ---------- Previous post was at 22:14 ----------

Could you post the entire log that you showed a screenshot of earlier. Easier to make something of it that way.
[Magisk] elandroido:
I attached a complete logcat from the following process:

- start root check app

- allow root in magisk popup "forever"

- open magisk manager and display superuser app list

Magisk superuser log is empty, magisk standard log has not entries in the last 20 min.

Edit: Upload failed, link follows
[Magisk] elandroido:
Added zipped log, had exceeded text file limit.
[Magisk] Didgeridoohan:
Is this with the official release or the unofficial snapshot I posted about earlier. And by the way, did you do a clean install of the snapshot when you tested it? If not, it'd be preferable if you tested by first uninstalling the official release.
[Magisk] petryrety:
I believe this is new type of protocol for protection for banking app. Maybe this type of banking app can scan what app request in past acces for root [emoji848][emoji848][emoji848]
[Magisk] elandroido:
This is with official release.

I did wipe boot, caches and system and reflashed rom, kernel and gapps prior to snapshot when testing, but I kept data.
[Magisk] Didgeridoohan:
All Magisk files are in /data... :D Just run the latest uninstall zip or choose the "Complete Uninstall" option in the Manager.
[Magisk] fw190:
I've downloaded it via pc and it werks ;)
[Magisk] Geowani12:
Friends I need your help, this happens to me every time I try to install a module.
[Magisk] Wolfcity:
Device? Rom? Magisk version? Maybe filesystem of data partition?

Provide some information..
[Magisk] Geowani12:
Moto G5 Plus

Stock

15.3

I dont know
[Magisk] admiralspeedy:
I really doubt that. Two devices with fresh installs of stock ROMs doing the exact same thing, yet 14.3 works totally fine? Which version of TWRP?

EDIT: It turns out I was flashing an older image to Nexus 6 than I thought, and 15.3 does work on the latest Nougat image, but it still does not work on my Pixel XL. I can do whatever testing you need to determine the issue. If you want to recreate the issue on the Nexus 6, flash the June image.

EDIT 2: And now it works on the June image just fine. Idk what is going on.

EDIT 3: Let's just ignore the Nexus 6 stuff. It still does not work on my Pixel XL.
[Magisk] sricks3:
Trouble updating to v15.3

With previous updates, I'd choose "Install" in Magisk Manager, and it would give me three options. I'd choose the one marked as recommended which would basically do the work for me and then reboot my device. However, when trying to update to v15.3, choosing "Install" only gives me two options, 1) Download Zip Only and 2) Patch Boot Image File. When I try to "Patch Boot Image File" it takes me into LineageOS's default file manager (my only installed file manager) and asks me to select the boot image. However, I'm not sure where to find the boot image, and the file manager doesn't seem to have root access anyway, so I'm not sure it would be able to find the boot image.

Can someone help walk me through this? I'm running LineageOS 14.1 (the January 29, 2018 build) on a Moto G4 if that makes any difference.
[Magisk] Quark^2:
I assumed that it was something like that.

Unfortuntately as far as I know:

- I never mounted /system RW

- I only installed Magisk + Busybox (from Magisk modules)

So my system should be clean AFAIK. But since I'm new to systemless I may easily have made a mistake.

Questions:

Is there a tool or something to check WHAT exactly was modified on system? I'd like to prevent similar mistakes in the future.

I assume/hope that I can safely flash ONLY system from the exact version of the stock ROM that I am using. Keeping all my data and apps, right?
[Magisk] Didgeridoohan:
:D Man oh man... I know that frustration when you're trying to recreate some issue and it just doesn't work...

I can't really help you with your Pixel, except there was users mentioning it works fine on theirs... Maybe you could start out completely fresh. Download everything again, factory image and Magisk zip, and start over. Whatever you did on your N6 right now... :D

That means your device isn't rooted. Did you also update LOS at the same time? That could be why...

When it wants you to find the stock boot image, you're supposed to have already extracted that from your ROM zip and placed it somewhere accessible on your internal storage (so you can find and select it). After that you can flash the patched boot image to your device, with fastboot or TWRP. Or you can just flash the Magisk zip in recovery.

It's not necessary that you yourself have done anything. Every single app you've given root access to have the ability to modify your system or mounting it rw... Finding out which one, after the fact, isn't possible. But you could of course take a look at what your apps do and try to figure it out.

It's perfectly fine dirty flashing your system. That way you know it should be fine.
[Magisk] Anas Rahman:
Need help with this error. Log attached
[Magisk] Hirishiolo:
hello, nice work! is it possible Magisk for kitkat 4.4.4 and xposed on Nexus5? thanks
[Magisk] IamIrene:
so basically if flash xposed then it won't work right:crying:
[Magisk] Android-UK:
You can still have Xposed, just install systemless one and then turn off root in Magisk Manager before loading Pokemon go.
[Magisk] JudgeDread11:
Probably not.
[Magisk] A.Shin88:
Sometimes Magisk automatically turn off root on my phone ( nexus 4 with pure nexus rom + hellspawn r18 kernel ).

Someone knows what cause the "auto turn off root" problem?
[Magisk] anhtuan.uct:
I cant install in TPWR on CM13 (It error)? pls
[Magisk] wagerer:
Hi, while trying to flash magisk, I got an error telling me it was unable to detect boot image, and I'm not quite sure what to do now... I've already tried reflashing my boot.img to no avail.

On the PokemonGoDEV reddit, OP suggested I try "pointing out the name of your boot image in /dev/block/...." but I don't quite know what was meant by that.

Device: HTC One (m7)

Android 5.0.2

ROM: NuSenSeveN v4.02
[Magisk] geek85:
no, not possible for now.
[Magisk] benengyj:
Managed to get it working correctly on my Sony Xperia Z5 Premium E6853 + RomAur 4.2.1 + Aur Kernel v4.0. For some reason other kernels didn't work with Magisk for me (modified stock kernel didn't detect my SIM and Zach's kernel didn't make Magisk work correctly but that might have been my error during installation). I figured it out by reading the other helpful posts and via trial and error and testing it with SafetyNet Playground app after every step. I'm not an expert but I hope this helps someone else. :)

Flashed RomAur (choose not to install xposed via built-in Aroma setup)

Let it boot fully

Removed SuperSU using the app

Rebooted to TWRP > Removed stray SuperSU folders/files

Rebooted to TWRP again > Flashed Magisk v6 + phh's SuperUser 17 (Magisk Version) .zip files from OP

Rebooted normally

Installed phh's SuperUser app from Google Play

Installed XposedInstaller APK + Magisk Manager APK

Rebooted into TWRP > Flashed xposed-v86.5-sdk23-topjohnwu.zip

Reboot

Done
[Magisk] Thumaroil:
Ok - I fixed my situation with root constantly switching on again.

I deleted manually (using ES-File-Explorer on root-mode) the following su - files /data/su.img, /sbin/su and system/bin/su and system/xbin/su.

After that I installed according to the instructions in OP and from here:

Now I have a running and working Magisk Manager and working PoGo 0.37 when root is switched off.

I have done this on the Moto G Falcon with CM13 and a Moto G Osprey with CM13. Not all files where present on the different devices.

Hope this helps someone

Regards

Thumaroil
[Magisk] dzikk:
Hi

Is it possible to toggle Magisk with Tasker?
[Magisk] mobileman88:
I recall reading this. It's possible

Check out

http://xdaforums.com/showthread.php?t=3435921

It's one of the posts on this couple of days this week of I recall correctly. Can't search well on Tapatalk unfortunately
[Magisk] Nezorflame:
Hey guys. [MENTION=631273]Chainfire[/MENTION] has just released new SuperSU with fixes mentioning Magisk compability. His post on G+: https://plus.google.com/+Chainfire/posts/8mPirmjhgqT

Question to the [MENTION=4470081]topjohnwu[/MENTION]: will this be supported now too?
[Magisk] Ice_machinE:
Thanks for this however I do have one reservation.

In order to use Android Pay, I need to un-mount using the magisk manager every time?

If no, then tell me how.
[Magisk] parthm6:
will i be able to use all root apps without problems (like titanium greenify etc)

ps.saw somewhere had problems with binaries

if it works what config should i use?like which su?

sorry a noob here but could you answer these questions.tried searching but didnt get a satisfactory answer.
[Magisk] yah7733:
note 2 n7100 custom rom how to get enable the selinux toggle . thank advance .
[Magisk] grep_i:
No way, no one can guarantee that everything will work at forehand without knowing everything about your phone your rom and all the software on it.

You have to be very specific about it one piece of software can make the difference in success or not.

You just have to try and see how far you come, make a backup in case you want to revert back, if you get stuck you can post your problem here but be very specific or you will get a lot of answers not being specific to your situation.

So now you must decide are you up to the task do you feel good about trial and error if not well you know what not to do than.
[Magisk] gk1984:
I feel like 80%sure of users in this forum are doing the same thing...
[Magisk] Joshmonster995:
I'm not sure if you have or haven't, but make sure to uninstall busybox if it was installed. (it is included as removing all roots). I have a z2 and forgot, and now after uninstalling I can at least boot into android after flashing. The Op states that Xperia devices aren't too compatible atm, so it's not looking too good for us.

Hope this helps [MENTION=3449261]shark300[/MENTION] might also help him
[Magisk] gk1984:
Where do you get the impression this is a root hiding tool? Pay will fail if root is detected. To get past this, you need to unmount su. You can either use the toggle in the Magisk Manager which doesn't require reboot or you can use Chainfire's that requires a reboot and flash SuperSU again in TWRP to regain root access.
[Magisk] gothicVI:
Look it up then...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] jenslody:
Where did you get the module from ?

This is not the version from Magisk's module repo.

I just tried it and it from inside MagiskManager and it installs fine.
[Magisk] Anas Rahman:
I got it from a forum on XDA. I tried the one from the repo too it didn't work either
[Magisk] siealex:
Uninstall Magisk Manager and install it again. If it does not work, try to reinstall Magisk completely.
[Magisk] elandroido:
Oh seems to make sense. :angel:

I actually though I ran the uninstaller, too, but I rechecked and, tataaaaaaa, it works!

Small remark: Magisk Manager from Snapshot force closes, but after uninstalling it and installing the release version of Manager, all works as desired.

Thanks a lot for the help! :good:
[Magisk] siealex:
Does anyone use Total Commander here? After installing Magisk it gets file lists in /data and /system very slowly, sometimes up to 15 seconds. On SuperSU it reads the lists immediately.
[Magisk] Ja_som:
On Nexus 5X I have sometimes issue to open them and yes, it tooks forever, also the download shortcut from the main view does not work.

But on my Lenovo Tab 4 it works fine, about second or two to display folders in /system.

So probably another issue with N5X, I think I will replace it soon, I don't like that device anymore.
[Magisk] jenslody:
Do you have any other modules installed ?
[Magisk] siealex:
One more person from our local forum reported that Magisk 15 (all versions 15.0..15.3, but not 14.x!) makes his Nexus 5X randomly freeze at the very beginning of the boot process. He has only Magisk as a root utility and NO modules.
[Magisk] EmiRus:
Yeah,me too.
[Magisk] elandroido:
Okay, let me correct my last post.

After clean flash (after magisk uninstall) the snapshot version seems to work at a first glance. I can add 1 or 2 or even 3 apps to the allow list.

Strange thing: Suddenly it stops working and cannot write to ignore list anymore.

Actually I have not been able to find out the trigger yet. I did a couple of clean installs and there seems to be some action that stops the database from working and then it cannot be fixed again. Weird.
[Magisk] Wolfcity:
You're suffering from the loopback bug, a known bug of Moto devices.

Three ways to solve that:

-Flash a custom kernel

-Reformat data to ext4

-Use the loopback bug module ( https://xdaforums.com/apps/magisk/guide-magisk-official-version-including-t3577875 )

I own a MotoG5+ myself and for me the loopback module did the trick. Just flash it through recovery and be sure it's the latest one.
[Magisk] brag288:
I even uninstalled magisk and it still shows my device as rooted...maybe it looks at the bootloader too?
[Magisk] elandroido:
Maybe it also checks for custom rom installation?
[Magisk] brag288:
Shouldn't be a problem tho..
[Magisk] unhappybirthday:
Yes, but for me it can take closer to a minute on my 1st gen Pixel.
[Magisk] siealex:
It's very strange. Other explorers (even 3C Toolbox in explorer mode) get these lists very quickly.
[Magisk] admiralspeedy:
I have already done that, including switching over to my Linux side and doing everything from there, just in case Windows was being stupid.

Also, I have not seen anyone confirm that 15.X is working on Nougat at all actually, because almost everyone jumped to Oreo already. I could install Oreo and see if it works just to confirm that it's a Nougat issue.
[Magisk] buggerman:
This is on a tissot on Oreo.

I unlocked my bootloader, flashed the patched boot image and started the phone, but now Magisk won't start. I am stuck at the Green screen with the mask (Magisk splash). Is there anything I'm doing wrong? I am trying to avoid installing TWRP.
[Magisk] Badger50:
Maybe try....

1. Clearing app data and cache.

2. Uninstall, reboot, install the app again.

3. Look for help in the Q A.
[Magisk] buggerman:
The app starts fine if the phone is started with an unpatched boot.
[Magisk] Didgeridoohan:
I'm assuming you mean Nougat on the Pixel, because v15+ works fine on Nougat for a whole bunch of other devices...

A logcat when the app is stuck might tell us what's wrong.
[Magisk] buggerman:
Sure. Will post it in a bit.
[Magisk] Cybertom3000:
Just reporting, updating magisk to version 15.3 causes bootloops on Samsung Tablets Tab A 10.1 running with [ROM][SM-T580][SM-T585][UNOFFICIAL][ResurrectionRemix-N-v5.8.5] by followmsi. Magisk 14.5 is latest version that works with this ROM.
[Magisk] admiralspeedy:
Yes, on the Pixel. I've already confirmed by my own stupidity that it works on Nougat on my Nexus 6, so it's a either a Pixel specific issue, or an A/B device specific issue. Do you have a first gen Pixel?
[Magisk] lgawe94:
Samsung Galaxy J7 2016

https://xdaforums.com/showpost.php?p=75328983&postcount=22415

I have the same phone model and custom rom. Magisk manager displayed information that magisk is not installed. Magisk now works properly thanks to this. I had this problem only for ROM based on AOSP.