yashsingh1/xdaforums huggingface dataset:
[Magisk] teshiron:
I'm having the same issue on my Moto G6 (build OPS27.104-15-10). The earlier version of Magisk Manager shows 18.1 installed correctly, while the 7.0.0 APK won't show it installed (and thus has no functionality).
[Magisk] guest4711:
So uninstall both MagiskManager and install the apk from folder "common" in Magisk.zip.
[Magisk] Naveenmalik39:
Please Please Anyone help me.

On 6 Feb 2019 i got a update of magisk 18.1 at that time i had magisk 18.0 so i tap update it ask me to install method i choose direct install (recommended ). I was at 90% battery at that time

After download complete a magisk installation window start After completing it Give me two option Reboot now or later to complete installation i choose Reboot Now option.

After it my device not get booting even not get charged nothing happen even i press power button numbers of time also try volume down + power button but it wont booting please help me. i visit Samsung care they told me to may be your motherboard is dead you have to pay 9200 Rs. Please guys help me device also not get detect by odin. I am a student i not able to pay that much big amount.

My Device :- Samsung Galaxy A9 Pro SM-A910F

ROM :- Official Nougat ROM

Location :- INDIA
[Magisk] djmcnz:
See my post on the previous page with lots of steps. There's obviously a problem but we're not sure what it is. You may need to go back to the beginning and start again.

Can't help you with that I'm afraid, it does seem odd. Perhaps a complete uninstall and reinstall (as above, see my post on previous page).

Naa, I don't mind changes (as long as they're evolutionary) but bouncing back and forward between deprecated and new functionality isn't really a good update strategy lol. And the changelog isn't explicit enough to work out what or why.

---------- Post added at 21:49 ---------- Previous post was at 21:46 ----------

Just patiently try to get into recovery. Certainly Magisk won't make your motherboard fail.

If you can get to fastboot or recovery you'll be okay... just be calm and patient and I hope you'll be fine.
[Magisk] Naveenmalik39:
bro please tell me how can i boot up my device at download mode or recovery from last 8 hours i keep pressing all keys but phone not show any sign of living. i dont care about data or anything just want to see Samsung logo again at my phone boot screen. want to know what happen to it why it not booting even not show charging not detected by usb too:(

:crying:
[Magisk] ManDone.vRs:
Hello . I notice no response from magisk manager after 17.1 versión . I tried the latest versions but only 17.1 pop Up and ask me to alllow an application to Alllow or Denied acces . How to fix this ? Miui 10.2.1.0 oreo 8.1 stock ROM .
[Magisk] gedod:
Hi, I've now got this working on my device, Xperia X

I had the same/similar issues to other users here.

I updated magisk to v18.1 by downloading the zip and flashing it via TWRP. When I booted back into system, magisk manager v6 recognised the new magisk but the safety net would fail even after applying the magisk hide props config. I tried to update magisk manager to v7. Initially the v7 UI displayed where it showed that it did not recognise magisk 18.1 was installed. When it was closed and reopened, it had reverted to v6.

So, rather than try installing v7, I went to the settings on v6 and chose the option to 'Restore Magisk Manager to Original' . It downloaded v7 and applyed it successfully. I have since applied the props config module and all appears to working as designed. All recognised as updated and safety net passed.
[Magisk] Didgeridoohan:
There's no reuse of deprecated functionality... /sbin/.magisk has never been used before, so I'm guessing you're thinking of /data/magisk that was used for the main Magisk files before everything was moved to /data/adb.

The changelog doesn't give much detail, no, but did you read the release notes? They tell you the main reasoning behind the change...
[Magisk] djmcnz:
I'm afraid I have no idea, I don't have a Samsung - head over to the forum for your device here on XDA and check the Q&A/Troubleshooting info.
[Magisk] djmcnz:
:confused:

it's got all the modules in it that I just installed today after completely removing everything. I have no /data/magisk directory.
[Magisk] Didgeridoohan:
Not sure what you mean... Let me clarify my point:

Yes, since Magisk v18.0, everything that was in /sbin/.core has been moved to /sbin/.magisk (with the boot scripts moved to /data/adb). You mentioned that deprecated functionality has been brought back, but /sbin/.magisk was never used before Magisk v18.0, so my guess was that you where thinking of when all the main Magisk files where moved from the /data/magisk directory to /data/adb (to make them harder to detect), which happened in Magisk v14.6.
[Magisk] djmcnz:
Actually that's not quite it but you've prompted me to remember and I'm certainly the mistaken one.

I was incorrectly recalling that /sbin/.magisk had been moved to /sbin/.core (not the other way around) and therefore wasn't expecting to see /sbin/.magisk being used. My bad, sorry for the distraction!
[Magisk] link3r:
hi friends! Does someone have Nubia Z17 Lite [NX591J] with LineageOS 14.1-20190202 ? Does it work with Magisk 18.1 and Magisk manager 7.0 ?
[Magisk] stevphie:
There are two Magisk manager now, latest one wont do anything... need to flash from recovery ?....if so, is it safe to uninstall the old magisk manager after ?

this is the first time the manager still there after the update.....
[Magisk] jcmm11:
See https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post78844093 for probable solution
[Magisk] mixlex:
You can go to play store and download an app that can boot recovery or reboot bootloader or whatever. There are several apps to choose from.

---------- Post added at 03:07 PM ---------- Previous post was at 03:00 PM ----------

Go to play store and download an app. There are several to choose from. With the app you can reboot recovery, fastboot, or whatever. Just search store for reboot, several should pop up.
[Magisk] :
HOW can he download that app when his phone can't boot up? :confused:
[Magisk] dl200010:
I had this same issue with my OnePlus 6T. I held the power button and both volume buttons until it rebooted into the bootloader. Maybe you could hold the Odin button combo and cause it to power off and go into Odin. Does the A9 have a easily removed battery?
[Magisk] kgursu:
It's a random package name. So, this won't be applied on my case.

Where exactly is the installed packages located? I couldn't find anything.

This could be because of a bad removal...
[Magisk] lauralbaby:
If you install AutoNotification, the free version should allow you to block the exact notification that appears. Link https://play.google.com/store/apps/details?id=com.joaomgcd.autonotification
[Magisk] geek.x86:
It's working for me though. I uninstalled the SafteyPatch module and installed this one. I enabled the improved hiding option using terminal emulator and since then I have not encountered any problem. I have been testing it for last 24 hours.
[Magisk] lohanchien:
Interesting. Didn't work for me. Although I only changed the fingerprint and enabled the Device Simulation. Improved Hidding is disabled for me indicating it's not necessary.
[Magisk] maverick_titan:
[MENTION=4667597]Didgeridoohan[/MENTION]

Zeroed down to - MagiskManager is conflicting with Xposed Module - RootCloak -https://repo.xposed.info/module/com.devadvance.rootcloak2

I disabled RootCloack Module, Rebooted.. MM Opens up fine.. Maybe latest MM tries do things which RootCloak was doing earlier...

Logs which I could save from within MM, Do not have any error messages.. just info logs. attaching for your reference.

It was working fine before MM v7.00... Does it needs fix ?
[Magisk] mixlex:
I thought he was saying it was on but buttons didn't work, my bad
[Magisk] Didgeridoohan:
The only thing that log tells us is that you have WAY too many apps on your Hide list. Do not add apps that don't specifically look for root or you risk making your system very unstable.

If you want to go to the bottom of this you'll have to provide at least a logcat (check the link I posted) showing what happens when you can't open the Manager.
[Magisk] DesertEagleSlim:
After updating to 18.1 from 18.0 I lost most of my modules. Especially youtube vanced and greenify. I've tried removing and uninstall YouTube then reflashing but still does not show up at all. So I reflashed 18.0 and still nothing. Any ideas or fix for this mess? Running Resurrection Remix rom on LGV20
[Magisk] Didgeridoohan:
There's a distinct lack of logs attached to your post (which seems to be a very common occurrence lately)... Without knowing what's actually going on it's hard to come up with ideas.
[Magisk] DesertEagleSlim:
Sorry, I understand. Dumb move on my part. Yea logs may not help as I've tried uninstall and reinstall multiple times and rebooted over and over trying to get the icon to show up and work. I'll see what I can pull. Tried to attach txt log gives me this error message

"Your file of 1.60 MB bytes exceeds the forum's limit of 512.0 KB for this filetype."
[Magisk] DesertEagleSlim:
Added as zip file cat txt inside
[Magisk] LordM:
I upgraded from Magisk 18.0 to Magisk 18.1 stable and to february security update on my Pixel 2 with Android 9.0. All went well. Then I downloaded Magisk Manager 7.0.0 and installed it additionally to renamed Magisk Manager 6.1.

The v.6.1 ist detecting Magisk correctly. V.7.0 tells me, Magisk isn't installed. I'd Like to use the newer version.

What do you need to track this down?
[Magisk] Pkt_Lnt:
Upload to pastebin.com or hastebin.com and then post the URL link here. :highfive:
[Magisk] gedod:
I installed v7 successfully by going to settings in v6 and choosing to 'restore original'. I also cleared repo cache first (not sure if that matters)

Edit...

Previous post here

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post78844093
[Magisk] LordM:
That worked faster than I thought. I restored original, Magisk Manager updated automatically to 7.0 and Magisk ist detected.

After that I "renamed" Magisk Manager again, all installed modules are still there.

Thanks for your help!
[Magisk] ahac85:
Delete
[Magisk] hfam:
Pixel 2, no TWRP, no modules, 1 hidden app. Updating from Jan to Feb sec update, then Magisk 18.0 to 18.1 (mm and Magisk) using the full system image method (remove "-w" from flash-all), then updated to 18.1 and patched the boot.img. Worked smooth and perfect as usual.

Love the new MM UI too. Thanks to [MENTION=4470081]topjohnwu[/MENTION], [MENTION=6842057]nathanchance[/MENTION], [MENTION=4667597]Didgeridoohan[/MENTION], and all the rest of you good folks who put in the hard work so we can enjoy the fruits of Magisk. Seriously, you guys are just the best. Thanks again.

.
[Magisk] daigo26:
stop charging after magisk update to latest

Please help my phone is samsung j5 2016 naugat and it stop charging after an update of magisk. But when I turn it off its okay with offline charging.

But when charging while it is on is not.

Please what should i do. :crying:
[Magisk] Bunt007:
Magisk modules not visible on module page

Hi,

I have used magisk on both stock and custom ROM I did the root thing from recovery mode then installed magisk manager, safety net check all passed, clear cache from magisk manager settings, but still modules don't show up,

I used magisk v 18 and magisk manager v 7 kindly advice !

I did uninstall reinstall for 5 times still didn't work for me
[Magisk] jcmm11:
What modules?

What are the contents of /sbin/.magisk/img/? (Other than .core)
[Magisk] Bunt007:
On magiks manager app, there is a modules tab where we can find the list of modules available for download, for me that page is completely blank, I tried reloading, cleated catches... But still its blank..a list of modules should show up there for download!

---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------

On magiks manager app, there is a modules tab where we can find the list of modules available for download, for me that page is completely blank, I tried reloading, cleated catches... But still its blank..a list of modules should show up there for download!

I am on liquid remix ROM.
[Magisk] spicediablo:
Just updated my magisk from 17.1 to 18.1 through twrp flash. However, when I tried to update magisk manager to v7.0.0,it failed. Try to update from app as well as install apk, both doesn't work. Updating from app will get the app installed but it will revert to old version after some time. Installing apk will return error(apk not installed). Anybody has this problem?

Sent from Sagit
[Magisk] Bunt007:
On magiks manager app, there is a modules tab where we can find the list of modules available for download, for me that page is completely blank, I tried reloading, cleated catches... But still its blank..a list of modules should show up there for download!

I am on liquid remix ROM.
[Magisk] jcmm11:
Ah, different situation. I misunderstood. I assume you've verified that you have an internet connection.

Just make sure you're looking in the downloads tab, not the modules tab. Modules tab shows installed modules only. (Modules tab is also what you would use to manually install a downloaded zip via the + button)
[Magisk] Bunt007:
Thank for quick response,

I think there is just one tab available for modules, I have following YouTube tutorial videos, still can you please share a screenshot of the page and tab where you can avail modules to download ?

I am sorry if I am asking a lot.

Thanks in advance!
[Magisk] Pkt_Lnt:
The installed manager has a different signature than the one you are trying to install. Delete the old one first then install the new one.
[Magisk] spicediablo:
Failed safety net after upgrading to new version... Looks like it's the same problem as v18 and I have to revert to v17.1. I thought the problem has been fixed in v18.1
[Magisk] kryshnakishore:
Same here safety net fails. I reverted to 17.1 but it says safety net API error I tired all the methods to solve it even I reflashed rom . Any idea
[Magisk] Trel:
Anyone else have Titanium backup crashing on open since 18.1 and Manager 7.0?

I upgraded Titanium and it would crash on open so I uninstalled and grabbed the old version from apkmirror and had the same issue.

The only other thing that changed that seems related was the recent Magisk/Magisk Manager updates.
[Magisk] djmcnz:
Just tested, no problem. Have you granted in root access since upgrading the MM 7?
[Magisk] Bunt007:
Thanks mate it got sorted, one quick question can I install magisk on stock 8.0 ROM and it won't brick my device or push me into boot loop ? Your advice will be appreciated!
[Magisk] jcmm11:
Based on what you've said:

It won't brick the device. Worst case just flash the stock boot image to undo the Magisk flash (you should always keep a copy of the stock boot image handy), but you should be fine. Stock 8.0 should not cause a problem.

It also shouldn't push you into a bootloop. If it does, same solution as I already mentioned. But again you should be fine (although you don't mention what phone, some may be a little quirky).

Make sure you have a copy of stock boot.img

Make sure you know how to flash that image from your computer.

These are just general precautions that you should know how to do if you do any type of flashing to your phone.
[Magisk] AndrzejDwo:
Try to:

-uninstall titanium backup,

-delete data folder /sdcard/data (it contains only Titanium Backup folder and licensing.xml)

-reboot (may be not necessary)

-reinstall titanium backup

Used to have this problem before (on previous versions of Magisk, and its not caused by it) that was the solution for me.
[Magisk] Bunt007:
I have created a backup of stock moto z play using twrp,

thanks mate for your help!

Cheers!!
[Magisk] martyfender:
Zip the log and you should be fine, if xda is not having any problems when you try to upload.
[Magisk] ahac85:
[MENTION=4470081]topjohnwu[/MENTION] Hi can someone please tell me if its possible to patch a boot.img with an older release of magisk? i dont have TWRP for my device, im randomly failing safetynet with 18.1 and would like to patch my boot.img with Magisk v17.3 which i found very stable....but have no idea how i can achieve this, as magisk keeps forcing me to update to the latest version now???

---------- Post added at 03:46 AM ---------- Previous post was at 03:41 AM ----------

you need to use Magisk Manager v6.1.0 that should fix the api error.
[Magisk] martyfender:
You have to use the downloads tab to see modules available for download. The modules tab only shows modules you have installed. If the modules tab is blank, you don't have any modules installed, yet.

---------- Post added 7th February 2019 at 12:06 AM ---------- Previous post was 6th February 2019 at 11:49 PM ----------

You should be able to skip updating. It should not be forcing you to update, I believe. Yes, an update is available will pop up, of course, but skip it and patch your stock boot.img with the current version (v17.3). Normally it does not force you, you just have to close that dialog. Newer versions of Magisk don't pop that up like that. Just click outside of that dialog and it will go away, if my memory serves me correctly.
[Magisk] Trel:
This wasn't the solution for me, but it pointed me in the right direction. The after that didn't work, I checked logcats to see if it was failing to open or write anything. It couldn't write to its folder under /data/data

Nuked it, uninstalled and reinstalled and it looks like its working again. Still not sure how it broke, but I'm back up and running, and doesn't appear to be related to Magisk then, and is likely just coincidence on the timing.
[Magisk] DumbKing@letthemeatspam:
Anyone know how I can change the Environment variable PATH to add all my programs from Termux into it so that when I run a bootscript it can call programs in that directory?
[Magisk] spicediablo:
I have no issue after reverting to 17.1. Safety net passed

Sent from Sagit
[Magisk] lucki1000:
This works, but now I have again safety net fail. And if I reboot it works again.
[Magisk] tomascus:
Anyone else getting sepolicy denial spam with Magisk installed? Getting these repeatedly spammed:

main : type=1400 audit(0.0:14371): avc: denied { read } for name="u:object_r:adbtcp_prop:s0" dev="tmpfs" ino=16654 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:adbtcp_prop:s0 tclass=file permissive=0
main : type=1400 audit(0.0:14372): avc: denied { read } for name="u:object_r:bg_boot_complete_prop:s0" dev="tmpfs" ino=16657 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:bg_boot_complete_prop:s0 tclass=file permissive=0
main : type=1400 audit(0.0:14373): avc: denied { read } for name="u:object_r:bg_daemon_prop:s0" dev="tmpfs" ino=16658 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:bg_daemon_prop:s0 tclass=file permissive=0
main : type=1400 audit(0.0:14374): avc: denied { read } for name="u:object_r:bluetooth_prop:s0" dev="tmpfs" ino=16659 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:bluetooth_prop:s0 tclass=file permissive=0
main : type=1400 audit(0.0:14375): avc: denied { read } for name="u:object_r:bootloader_boot_reason_prop:s0" dev="tmpfs" ino=16660 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:bootloader_boot_reason_prop:s0 tclass=file permissive=0
....
[Magisk] roscos:
Good morning, I have updated to Magisk 18.1

Now xposed does not appear in the Magisk modules but works well

xposed Version 89

Android 5.1 (lollipot, API 22)

Doogee F5 arm64

Can it be a problem?
[Magisk] chooks06:
Not sure if this works for you..

Open Xposed. Tap in the 3 buttons on top and select reboot. Wait for Magisk to grant super user permission.

It's probably because Xposed is not active yet (no Super User permission), that's why it's not seen in the Super User list.
[Magisk] tommo1982:
Is there a bug in Magisk 18.1 installayion? I have the Magisk Manager 7.0 version and I am trying to install the latest update 18.1, but it says my API is too low. I need API 28. I have Android 7.0, it says it's supported. Did somethig change?
[Magisk] JimmyEatFood:
Barclays app is detecting root even with Barclays app hidden and Magisk manager renamed. Any ideas?
[Magisk] shmykelsa:
Hi,

I am running Magisk 18100 and Manager 7.0.0 (185)

Superuser works just fine. Apps are able to obtain root permissions, but when it comes to module, the installed one actually work but whenever I try to update them they all get stuck at "Found /data/adb/magisk_merge.img" or at "Found /data/adb/magisk_merge.img".

If I install through recovery they work just fine.

How can I fix this? I've already tried re-installing magisk, but no luck.
[Magisk] Archangel:
18.1 updated flawless through direct install on my OnePlus 6T love the new design!
[Magisk] dvhttn:
Back on 17.3 because of the on/off safetynet issues with 18+ but it won't download the foss code to run the safetynet check. I say 'yes' to download the code then all that happens is a 'Safetynet API error'. I have a couple of other apps that run safetynet checks and they work OK, and safetynet is OK, just that MM won't/can't download the foss code.

Any clues as to where to start?

Ta.
[Magisk] ahac85:
The pop goes away like you say but there's no install button, just an update button, so i have to update to latest version in order to patch boot img which i dont want to.

---------- Post added at 11:02 AM ---------- Previous post was at 11:00 AM ----------

Are you running Magisk Manager v6.1.0? as the problem your describing i had on v6.0.1?
[Magisk] koniii:
I manage to install magisk on kitkat

Some modules is working fine but the superuser is not working

su: request rejected

No prompt dialouge are showing
[Magisk] AndrzejDwo:
Yep, you're right about that. It is probably the way I've done that just have mistaken the folders as it was a while ago. Happy to point the good direction.

Cheers
[Magisk] dvhttn:
Bingo! That was the problem. Installed 6.1.0 and all runs as expected now.

Many thanks.
[Magisk] guest4711:
Did you try to raise the timeout for the prompt?

If that does not help, switch "Automatic Response" to 'grant' in settings of MagiskManager.
[Magisk] jcmm11:
Start your script with:

#!/system/bin/sh
PATH=$PATH:<directory you want to add>
<rest of script>
[Magisk] koniii:
I try it both but its no luck
[Magisk] amnher:
I cant seem to find downloads section where i can see the list of modules in repo
[Magisk] FikriWildanNugraha:
Fingerprint Error Xiaomi Redmi 4x Santoni

i had Fingerprint Error issues on Xiaomi Redmi 4x Santoni after update to v18.1 (1800), software:v7.00 (185), cant delete curent fingerprint, and fingerprint doesn't work at all when using to unlock screen.
[Magisk] ahac85:
Figured out i needed to create a custom channel in order to patch boot image with an older version. Heres a link to the custom channel if anyone else needs it to downgrade who dont have a custom recovery.

https://raw.githubusercontent.com/ahac85/magiskfiles/master/Magisk173.json
[Magisk] bmark240:
Edit: solved.
[Magisk] Oswald Boelcke:
For the benefit of other users who might run into a similar issue I'd personally appreciate if you hadn't deleted your original post but amended it with your solution. XDA is about the sharing of knowledge.
[Magisk] bmark240:
I was having problems with Kernel Aduitor.

After updating to Magisk 18.1 & Magisk Manager 7.0 (1.85). Kernel Aduitor wasn't detecting Root. Tried clearing Caches in the Application, then in TWRP Recovery: Art/Dalvik Cache. Reboot.

Resolved the issue by completely removing Magisk Manager 5.30 (which must have confused the App, looking for file location).

Used the newest Magisk Uninstaller to completely clean of older Magisk. Then wiped Caches again to rid of orphaned files.

Reinstalled Magisk 18.1 through TWRP, gave Kernel Aduitor access to Root privileges & it started working again!

I am running CrDroid Oreo on OnePlus One.

I hope that is enough information.
[Magisk] Hitlerzz:
I am actually having a issue with the safety net.... It shows safety net is true after reboot however after sometime the safety net changes into false... I don't have busybox or xposed installed