yashsingh1/xdaforums huggingface dataset:
[Magisk] toolateboy:
Magisk is OK with V14 but not for V16.V16.3

I have searched through the thread and tried many times but still failed. Hope anyone of you can assist me.

Detailed description

Magisk V14 was working perfectly in my device. Magisk hide and Magisk Log etc all working fine.

After upgrade to newer version like V16 / V16.3, Magisk Manager (lastest version V5.6.4) just hanging (is not responding) at the first page.

Tried to upgrade from V14 >V16/V16.3 by TWRP or Magisk Manager (patch directly) also the same result.

Fresh TWRP install of V16/V16.3 also having the same issue.

Details about my device

Samsung Note 3 (N9005), Android 6.0.1, ROM is Magma NX VX1, Phantom Kernel V1.2x, no any modules installed in Magisk Manager.

Logs attached

TWRP recovery log V14 > https://drive.google.com/file/d/1PNhT_YX27GQu1oK3ESBPOa50f_wjchXU/view?usp=sharing

TWRP recovery log V16 > https://drive.google.com/file/d/1Tw9JHyoLgVQ39La8C09C9MwLBXM9Wvvi/view?usp=sharing

matLog V16 > https://drive.google.com/file/d/1SD3HsMxaV1oQprwM4KDPKparHtAo8HPc/view?usp=sharing

Magisk Debug Log V16.3 > https://drive.google.com/file/d/1MooUqSkL6tzjdkjkHZPaMtxcciY4Fytq/view?usp=sharing
[Magisk] tattmann:
Hello, I am having a little trouble and hope someone can help me here or pm if necessary. I am currently running 15.3 and 5.6.4. My phone is a samsung note 4, with the modestrom os with flashpoint kernel made to work with magisk. I would like to upgrade to magisk 16.0, or a beta, however every time I use magisk manager to install the 16.0 update, it ALWAYS fails. However, if I uninstall magisk, go into twrp and flash there, it successfully installs with a hitch. It NEVER passes safetynet. Until I can find out how to upgrade to 16.0, I am stuck on 15.3. I have an s5 that works fine on 16.0, just not the note 4. I saw on the beta op, the instructions to upload log file if needing help, but when I go to the place in my root folder, the log simply is not there to post. The only files at /data/adb/ are, a magisk folder, and 2 files. magisk.db which I believe are database not debug logs, and the other is magisk.img. So, I AM trying to give the log info but cant find it. Any help would be greatly appreciated. Thank you.
[Magisk] Didgeridoohan:
You're having su database issues... Use the option in the Manager to uninstall the app (Uninstall - Uninstall App) and then install the latest version of the Manager. If that doesn't fix the database issue, use the complete uninstall option in the app, reboot once (keep in mind that this may encrypt your device) and then install v16.3 (patch with the Manager or flash in TWRP).

This is the beta thread, so switch to the beta channel in the Manager settings and try again (the magisk_debug.log is only generated on the beta release). Also try switching MagiskHide off and on before reporting back (in the general support thread, please) and you can also check here for tips and tricks:

https://www.didgeridoohan.com/magisk

Please also mind that this is not a place to discuss SafetyNet issues, unless you can clearly show a way to improve MagiskHide. Like I already said,please keep it in the general support thread.
[Magisk] toolateboy:
Manager crash (not responding) issue with Magisk V16/16.3

Thanks [MENTION=4667597]Didgeridoohan[/MENTION] for your reply.

Tried both your suggested methods but still no luck. Manager V5.6.4 still crashing (not responding) with Magisk V16/16.3.

This is the log when i tried > complete uninstall > reboot > flash V16.3 in TWRP > https://drive.google.com/file/d/1FtSgL1cKztdt5hYYLZVG7rCX58AFdA6A/view?usp=sharing

Noticed 1 thing in the magisk log...Although "Magisk V14 + Manager V5.6.4" working perfectly (passed SafetyNet too) but i always see this error in Magisk Log

04-01 09:06:56.351 299 5668 E Magisk : stat /data/data/com.topjohnwu.magisk failed with 2: No such file or directory

Full magisk log > https://drive.google.com/file/d/1ZiE9VgbT2a6_7jNfJ6WsBkMzf0Rkz0SJ/view?usp=sharing

Not sure whether solve above error can eliminate my Manager crash (not responding) issue with Magisk V16/16.3?

Hope you can provide me more clues. Have been digging around couple of days on this issue. Thanks! :)
[Magisk] Zik:
Error after running Android :(

But magisk works.

OS: AICP from 29.03.2018

Kernel: BlackScreen 3.8 (beta1)
[Magisk] Asv97:
Sorry if it has been already asked.

I'm aware that the 16.3 version won't support outdated modules.

Am I the only one whose phone doesn't have Magisk and /data/Magisk folder in the root directory?
[Magisk] Didgeridoohan:
Did you by any chance use the old Manager hiding feature? The one where it "installed" a different app called "Unhide Magisk Manager"? If so it's quite likely that there are remnants of that old, and not too good, hiding method that's causing issues. You might have to uninstall the Manager through adb and then reinstall:

adb uninstall com.topjohnwu.magisk

Also check in /data/app if there's an app with a completely random and weird package name. Use the same adb method to uninstall that.

In either case, it seems like the uninstallation is failing for you. That v16.3 recovery installation log reports that a Magisk patched boot image is detected...

So, try uninstalling the Manager as above, flash the uninstaller zip in TWRP (save the recovery log afterwards, it might show something interesting), flash your stock boot image, and then try to install v16.3 again (and of course, save the recovery log).

You're not alone... That's by design on v16.3. Those are the backwards compatibility symlinks talked about in the release notes. And like you already surmised, it's been asked before so you would likely have found something if you'd searched...
[Magisk] Asv97:
I did search..

My next question is:Since there is no /magisk,;where am I supposed to paste the script files now?(The files which I earlier used to put in /Magisk/post-fs.data.d)
[Magisk] Skull97:
/sbin/.core/img/.core/post-fs-data.d
[Magisk] Didgeridoohan:
In that case I think you need to work on your Google-Fu... :p

You've already been given the answer, but in the search link I posted, the third result has info that would have pointed you in the right direction. It's also useful to read the documentation (RTFM :laugh:) when trying to figure out how to use something.
[Magisk] windwaver:
Please read this if you plan to use the "Hide Magisk Manager" feature: When using the hide Magisk Manager feature, the app will generate a random package name, repackage, and replace itself. If the repackaged manager and the original "com.topjohnwu.magisk" both exist on your device (you got 2 Magisk Managers installed, which in theory should not happen), only "com.topjohnwu.magisk" will work properly. This means that when you install an update, you are required to re-hide Magisk Manager.

I've got 2 Magisk icons now and only 1 of them works but how do I get back to the original un-hide version?
[Magisk] Didgeridoohan:
Is your Manager installed as a system app? This can happen in that case... I don't get why some ROM creators insist on doing this, it only messes things up. Hiding the Manager doesn't work, for one thing...

If you check "About" for the app that works, does it say "com.topjohnwu.magisk"? If so, just uninstall the app that doesn't work by long-pressing it and either selecting uninstall or going to "App info" and uninstalling from there.
[Magisk] jenslody:
System apps can not be uninstalled, just disabled.

I removed it from /system/{,priv-}app manually from inside TWRP in a similar case.
[Magisk] Didgeridoohan:
I was unclear... I was making the assumption that the app that wasn't working was the repackaged Manager. That should be able to be uninstalled. Although, thinking about it, it should be uninstalled when opening the working proper Manager, no?
[Magisk] jenslody:
In my case it was almost always immediately auto-uninstalled, but if I remember correctly not always.
[Magisk] windwaver:
I've uninstalled the icon that doesn't work but hiding Magisk creates 2 icons every time I do it. I've decided to use Magisk the way it was without hiding.
[Magisk] Elaugaufein:
There seems to be some kind of issue with the magisk re-install following OTA. My phone bootloops endlessly whenever I do this (it can be fixed by dirty flashing the correct factory image). And manually installing through twrp works as well, as do in place magisk updates once it's installed. It also used to work before the first weaver update that broke twrp the first time. So I'm guessing it's something to do with the encryption not being redone properly following an OTA update. I'm happy to provide logs etc , if you want me to and can let me know what you need. The major problem here is of course that I only get 1 shot per month and I have to at least dirty flash the phone to get access again after the issue happens.

I haven't checked for this month yet (since next months system update isn't out) but in the past it has left my phone in a position where I can't install future OTA's without first clean flashing the phone (dirty flashing still worked for updates but left it in the same position where future OTAs wouldn't work).

ETA - Sorry to clarify this is a taimen phone (from the Google Store for Australia)
[Magisk] toolateboy:
sqlite3 open failure: unable to open database file

Tried ADB uninstallation > flash uninstaller zip in TWRP > Recovery log = https://drive.google.com/file/d/1VjRMegfh7H9JOoEQ2F-yyCzDzG34VX6u/view?usp=sharing

Flash stock boot image > TWRP flash V16.3 > Recovery Log = https://drive.google.com/file/d/1PtZi7t-sXV5QeMwtV_cZN5aCb2vvYYg7/view?usp=sharing

Magisk manager somehow not installed automatically after reboot. I had to installed it manually with apk. Manager is still crashed and i found below errors in logcat. Searched XDA and found some people having the same error but no proper solution found.

04-03 10:59:07.002 303-22015/? E/Magisk: sqlite3 open failure: unable to open database file

04-03 10:59:07.002 303-22015/? E/Magisk: su: cannot find requester

Full logcat = https://drive.google.com/file/d/1wPTMFcyvFkjCryyXkPvSRPvFzs-dIe8z/view?usp=sharing
[Magisk] jineshpatel30:
How to manually add scripts in .core now ?

I was using my own post.fs & service.d scripts in .core with Magisk 16.0 then i clean install Magisk 16.3 beta and now i can't find Magisk mount point in root directory, as you pointed out it was removed in 16.3, so what should i do to get manual script adding functionality back ?

I'm pretty new with magisk, i started using it with 16.0 only. I have read guides in OP but i'm still not familiar with all the aspects.

I'm using Nexus 5 Hammerhead with LOS 14.1, if it matters.

EDIT : I think i found the answer.

From here & here

I need to put scripts in /sbin/img/.core , right ?

Please add this info in release note when this version go out as stable release so that new users like me don't get confuse :)

Thanks !
[Magisk] Didgeridoohan:
The /magisk mount point was replaced with /sbin/.core/img in v14.5, not v16.3. This update merely removed the backwards compatibility...

Always a good idea to RTFM: :p

https://github.com/topjohnwu/Magisk/blob/master/docs/README.MD

And more precisely, for this case:

https://github.com/topjohnwu/Magisk/blob/master/docs/details.md

Edit: Ninja'd! Nice searching...
[Magisk] jineshpatel30:
Yes i found it.

Please refer my edited comment :)
[Magisk] SacredDeviL666:
Did the usual clean up :highfive:

This is not a How To or Where To but a beta thread for reporting bugs if you know How To & Where To.

How to & Where to thread https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382

Guides & Basic troubleshooting thread https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417

Thank you all for all your time and contribution

---

SacredDeviL666

Forum Moderator
[Magisk] Chrifister:
Fun with updates. I'll try to be short and concise. Taimen running March firmware.

-Couldn't originally install March OTA probably cause of AdBlock modification of system but not sure. Had to flash March firmware. Magisk installed fine.

-Seen April OTA last night. Since no AdBlock this time, figured topjohnwu's update method would work this time.

-Started the OTA and it actually started installing this time. So the update guide says to switch to Magisk when step 2 starts. Noticed I can pause the OTA. Maybe I'm supposed to? Not sure how long step 2 takes. Better pause so I don't miss it.

-Step 2 starts and I pause it. Installed Magisk in second slot.

-Resumed OTA and installation failure. Awesome. Probably not supposed to pause it. Hit try again.

-Step 2 starts so switch to Magisk and install in second slot. No problems. Back to the OTA. Hmm step 2 takes a long time.

-OTA finished so reboot. Bootloop. Great.

-On vacation and Internet crappy here so grabbing the April firmware would take forever. Still have the March one though.

-Dirty flashed March. Stuck on loading screen. Think I'm having fun now but not sure.

-Flashed March. Booted fine. Started pulling cloud backup and went to bed. Finished by morning.

-Downloaded Magisk using download button from first thread in this post. Installed and Magisk says invalid update channel or something. Curious. Switched to beta and says 16.3 installed. Different than what I had before.

-Patched then flashed boot image. Bootloop. Arggg.

-Flashed stock boot image and stuck at loading screen.

-Dirty flashed March firmware and boots fine.

I gather two things from these steps. The first is that whatever version of Magisk I was on, 1600 or 1610 maybe, causes bootloops with April firmware. The second is that Magisk 1630 is causing bootloops on March firmware. Unless I missed something? Since we're on vacation with a 2 year old, I don't have time to do much.
[Magisk] killerBRs:
Magisk is not working after reboot, sometimes Magisk Manager alert says "Magisk is not installed"

I tried everything.

Samsung Galaxy S6 Edge, Stock Samsung ROM.

Logcat: https://drive.google.com/file/d/1bS44bgVMAtKy0n5yrWj1Sl9Pv1IRKckt/view?usp=drivesdk
[Magisk] jakson7474:
View attachment 4469020

help all the modules I try to install from this error:chorando

moto G5s plus sanders

stock ROM

Sorry for asking, I already found the solution.

https://xdaforums.com/apps/magisk/g...-including-t3577875/post71554247#post71554247
[Magisk] Niksunen:
I have same issue. After every reboot i have to go and un-tick that magisk hide button, wait about 10 seconds and put it back on. After that it passes safetynet and work fine until next reboot. I use magisk 16.3 on Oneplus 5T (Oxygen 5.0.4, Android 8.0)

I can attach logs later today when i have to time.
[Magisk] asd13751418:
When I use magisk 16.3 or 16.0,log is always empty and magisk hide doesn't work.

But I use 15.3 version now,it work perfect,log output and hide root work.

It's strange and I want use new version,I need some help.

My phone is lenovo vibe x3,android 6.0

Sorry for my bad English.

Thanks in advance.
[Magisk] Didgeridoohan:
Known issue, fixed on GitHub, will probably be in the next release.
[Magisk] Timmmmaaahh!:
Anyone seeing this? I just noticed that everything except 'version' and 'uninstall' disappeared...

I noticed the exact same on a friend's Elephone earlier today.

Just going into settings and rebooting seems to fix it. Still can't find any module though...

Edit: wait, could this be related to a connection issue? I'm always online otherwise but some app seems to interfere today...
[Magisk] Zacharee1:
Just tested turning on Airplane Mode before opening...it thinks you're offline.
[Magisk] Sam Nakamura:
Hello [MENTION=4470081]topjohnwu[/MENTION], I'm aware of your limited time atm but if you might want to have a look at this post, the module author asked me to forward this issue to your beta thread...

https://xdaforums.com/apps/magisk/module-cloudfaredns4magisk-t3772375/post76175678
[Magisk] guest4711:
Yes, you see this main screen if you have no internet connection. But the hamburger menu should show you the usual menu entries (all but downloads).
[Magisk] Indashio:
I have the same problem. When I close Magisk manager Magisk hide stopped I need open Magisk again and active Magisk hide. I need to have Magisk open in the background all the time
[Magisk] jenslody:
Can you provide logs (magisk_debug.log or better a logcat)?
[Magisk] Indashio:
My log
[Magisk] jenslody:
This (and it's predecessors) might be related (a possible solution/workaround included):

https://xdaforums.com/showpost.php?p=76183798&postcount=24165
[Magisk] Didgeridoohan:
Could we please keep the Tez troubleshooting posting out of the Magisk beta

development

thread? There's a thread perfectly suited for it right here: https://xdaforums.com/apps/magisk/tez-app-custom-rom-root-device-t3722018
[Magisk] DenyDarko:
Remove me please
[Magisk] SacredDeviL666:
Thread Cleaned.

Stay on topic and respect the OP
[Magisk] shadavis08:
Just so I'm clear if I want to install magisk version 13 all I have to do is uninstall the 11.6 through the app and then flash magisk 13 correct?

LG V20 - NATF 5.0 - Magisk 11.6
[Magisk] ahmedraza:
I m using magisk 12 so 1st i need to magisk uninstaller after that flash magisk13 right and do i separate download magisk manager
[Magisk] cafe-creme:
Yes, thanks i already had wipe Play Services and Play Store by installing this version.

The applications reappeared automatically after a waiting period (about 15 minutes)

:good:
[Magisk] Alucard:
Alright there definitely an issue with magisk beta and installing modules maybe there not all supported cause viper4android says driver status not supported and driver 2.5.0.4 and when flashing gltools i have bootloop,could you fix please in next update.
[Magisk] kaw900r:
MagisK v12 set to core only mode is working. Once MagisK is fixed I think I will do a fresh install and see if I get the option back to use SD card as storage for pictures since that option seems to have gone away for some reason...
[Magisk] shadavis08:
Woohoo magisk 13 installed and working fine so far no modules

LG V20 - NATF 5.0 - Magisk 11.6
[Magisk] -ION-:
Hi there, just installed v13 on my Samsung Note 3 but when enabling core mode it doesn't load the required resetprops to pass SafetyNet. Is this by design, or should it load these resetprops?
[Magisk] zelendel:
All of these posts about saftynet. People need to accept that it is coming down to a choice. Root and mod or passing safty net and using things like Google Pay or those other payment apps (not sure why people would use such a insecure method but to each their own)
[Magisk] Alucard:
[MENTION=4470081]topjohnwu[/MENTION]

Sir i love your work,but with v13 i have problems with modules not working properly,viperandroid says not supported on driver info and gltools bootloop phone.
[Magisk] veez21:
Yeah. Paying using a rooted phone (which means unlocked bl) is insecure as heck. I'm only on magisk (though I'm currently using supersu :p) for the Systemless part of it. Haven't even used magisk hide that much :silly:
[Magisk] shadavis08:
I don't use payment apps with my phone! It's cash or card.

LG V20 - NATF 5.0 - Magisk 13
[Magisk] zelendel:
It's not even just rooted. All the retail shops here banned mobile payments after a security expert was able to high jack it just by being in the area with the right setup.
[Magisk] kishd:
Safety net will most likely be used in the future for blocking all sorts of apps. Apparently Netflix does not appear on Google play if the phone does not pass safety net so it is probably a good idea to get it working as we might need it for other reasons in time to come.
[Magisk] veez21:
Lol, wth. At least your community learned it's lesson.
[Magisk] zelendel:
You are right more and more apps will start using it but also google will go further to prevent things like this. Keep in mind Google knows what is done here and watches closely as they hate what we do and work very hard to counter it. Mainly if the porject is open source. That just makes it alot easier for them to block it.

---------- Post added at 05:32 AM ---------- Previous post was at 05:30 AM ----------

Yeah to the point that they even removed the chips in their debt cards. It ticked off alot of people when they found they couldnt use apple pay or any of the other mobile payment options. Some have even moved the card reader behind the counter to prevent people from trying.

Doesnt matter to me personally as I would never use it myself but I am sure alot of people do use it.
[Magisk] stanleyopar2000:
Lg v20 MegaRom SafteyNet fails on v12, and v13
[Magisk] DSDONE:
I can't update...
[Magisk] sacredsoul:
How does one go from Magisk V12 to V13 beta? I've gotta unroot first and then reroot with v13?
[Magisk] ZeOnEscofet:
Right now updated Magisk-v13.0 (1777d9f) to (b3da28e)

Safety net + magisk hide + FPR + root working ( modules, i don't know ) Huawei P9 lite VNS-L31C432B380 ( with Rocatex v7 by simo255) + TWRP T3.1.1-0-venus by OldDroid.

Congratulations.

Donation coming soon <3
[Magisk] Jleoz:
Hi,

I have an issue that after roughly 23-24 hours, Magisk stops working (sometimes it says not installed or does not pass SafetyNet) and outputs this error from the Magisk Log: "Magisk : readlink /proc/XXXX/ns/mnt failed with 2: No such file or directory" where XXXX = different four numbers.

Only restarting fixes this issue for another roughly 23-24 hours.

Attached is the Magisk debug output using the latest beta. Does anyone know why this occurs?

Thanks,

Jleoz.
[Magisk] Sizzlechest:
I attempted to install Magisk 16.3 on a bootloader unlocked FireTV. The device wouldn't boot. I tried to get a hold of any logs as specified in the OP, but there are none to be found. It seems to install in TWRP without issue. Since I have the necessary cable to restore the boot partition, I can experiment, but there's not much I can do at this point. Earlier versions of Magisk would just cause bootloop.
[Magisk] Artim_96:
Tried playing around with different combination of enabling or disabling force encryption and dm-verity? Other than that there isn't really anything you can do other than go to a device specific forum. FireTV might be Android at it's core but it's probably as much Android as Android is Linux. Amazon is even worse than Samsung in their worst days with crippling down Android so the chance of any official support in the future isn't that big
[Magisk] Jaymin.0.1910:
Aware people of their responsibilities

Hello people over here,

Please be aware of what you should post here or not and how would you post here.

If you are asking for some fixes or improvements from developers, posting whatever you could have done to troubleshoot and also logs is a nice idea.

Posting things like It didn't work for me without required information is like a headache.

And if you are willing to discuss something, using the support thread instead is always the best idea.

JayminSuthar (formerly MCMotherEffin')
[Magisk] Dinolek:
Delete this post, thanks.
[Magisk] KaMyKaSii:
The mod deleted my post just because I did not post any log? So far I was not asking for any fix, just wanted to know if the issue was generalized or it was only in my setup. I admit I should have searched the topic before, since the issue had already been reported. Anyway, here are the logs (Magisk Manager when open disable Magisk Hide):
[Magisk] SacredDeviL666:
Thread cleaned.

The purpose of this thread isn't for troubleshooting, instead to share bugs if you know how to along with logs/detailed steps for Beta versions only!

Thanks

SacredDeviL666

Forum Moderator
[Magisk] fanaticgamer:
Sorry for my late response, it's stock firmware, stock kernel, twrp-3.2.1-0-klte