yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
If you haven't already it might be worth a shot...

If you haven't already, take a look at the troubleshooting guide.

Currently, there seems to be a few users afflicted by an issue with the su database. No idea why yet, but logs are always useful.

They're likely still on module template v4. They're gonna have to be updated to 1400+.

The Magisk log is no good for random reboots. See if you have the file /sys/fs/pstore/console-ramoops and post that. Otherwise, trying to capture some kind of logcat from the crash would be very useful.
[Magisk] Mejilan:
Thank you so much for responding... and to so many of us! :)

Here's that console-ramoops file you requested. I changed the extension to .log in order to allow the upload.

I'll install a logcat app and make sure to capture the log when the phone next reboots itself.
[Magisk] JTruj1ll0923:
Thank you! Not sure if this well help, but I got another log of the same thing. I first installed magisk manager 5.4. Then I gave matlog su. Then cleared log and installed manager 5.4.3. Then tried to open magisk manager and it crashed twice before I went back into matlog and saved the log as it allows it to still have su if the app isn't closed. Hope this helps and hope it can get figured out soon! Thanks again
[Magisk] Mejilan:
I hope I did this correctly. First time using a logcat app (Matlog, in this case). I've attached a zip that the app has generated containing my device info and the log itself. I had the thing running, watching a steady stream of incomprehensible gibberish flying across my screen, until the phone rebooted itself. I immediately patterned my way back into the phone as soon as the reboot was complete, re-opened Matlog, let it run for a few (dozen) more lines, then saved the file and created an attachment out of it.

I wanted to take a stab at at shortening the file for you, but opted not to do so because I have no way of knowing what you're looking for.

That said, by far the most repeated message in the log is a pair of lines that read:

Battery Power Supply logging Daemon start!!!!

Cannot run on production devices!

Can't be the issue at hand, but those two lines repeat again and again and again. That can't be good for the phone, can it?

Anyway, thanks again for taking a look at my issue. I hope some of this makes sense to you.
[Magisk] tropicanapure:
I was wondering if anyone had used v14 to keep root during OOS 4.5.1 --> 5.0 migration, on a oneplus 3? I am getting stuck at the 1+ boot logo. :rolleyes: Luckily, i am able to get back to recovery and flash my previous version of the OOS :)

I was wondering if Magisk was the culprit and perhaps I should be using beta Instead (I prefer the stable version)? I thought I should check here first. Worth adding, there are no errors displayed when flashing the zip.

Before you ask, I am familiar with the process of using Magisk to keep root between ROM upgrades - on the OOS :)

Thanks in advance.
[Magisk] JTruj1ll0923:
Oops, forgot to post the log ?
[Magisk] JTruj1ll0923:
So... I did just install the magisk Beta and with that the magisk manager opens just fine. Along with that Kernel Adiutor applied correctly which means it had root. I went into the superuser settings of magisk manager and noticed that these apps already had root access even though I hadn't given them access. It seems as if whenever I had 5.4.3 installed before without being on beta it saved the apps I gave access to but it was different on 5.4 manager. Maybe this is some reason why it was crashing? Also I posted a log from this most recent boot.
[Magisk] Didgeridoohan:
From my limited knowledge I'm going to guess it does have something to do with the power supply. This is the end of your console-ramoops:

[ 3752.903548,0] FG: fg_power_get_property: ESR Bad: 321533 mOhm
[ 3755.547685,2] init: Starting service 'batt_health'...
[ 3755.581076,2] init: Service 'batt_health' (pid 13501) exited with status 0
[ 3755.581125,2] init: Service 'batt_health' (pid 13501) killing any children in process group
[ 3757.013773,0] FG: fg_power_get_property: ESR Bad: 321533 mOhm
[ 3772.133808,0] Watchdog bark! Now = 3772.133799
[ 3772.133830,0] Watchdog last pet at 3750.133360
[ 3772.133841,0] cpu alive mask from last pet 0-3,5
[ 3772.133848,2] Causing a watchdog bite!

That starting and killing of "batt_health" happens hundreds of times in a short time and finally ends with the watchdog bite above.

Have you made sure if this actually is a Magisk issue? Does it happen only when you have Magisk installed? I think your best bet is to look for help in your device's forum. They know the device better...

There was a change with how the Manager handles the su database between v5.4.0 and 5.4.2. Might be that this is causing issues if you update and then downgrade...
[Magisk] ColinMacLaren:
Hey,

I am using an NVIDIA Shield TV 2015 Pro (500GB model) with the latest Android Update (SHIELD Experience 6.2) running Android Nougat 7.0. I can flash Magisk 14.0 in TWRP easily without any issues. However, newer versions fail to install, telling me the it cannot mount /vendor during the flashing procedure.
[Magisk] DodoGTA:
It looks like that your device/ROM doesn't like ro.build.type being set to user
[Magisk] JTruj1ll0923:
I am sure this is probably was it was, but I only downgraded because magisk wasn't allowing any apps to have su even though I had already allowed it. So, I uninstalled magisk and then tried 5.4.3 again and it then started the crashing. So the crashing was probably cause by that, but idk why the previous thing was happening. But anyway, thanks for the help everyone!
[Magisk] Aldericdevir:
Tried it, but still the same :/
[Magisk] njascgil:
I have two devices with Magisk and suddenly, one of them start displaying "# root" on the left side menu of Magisk Manager instead of "# Superuser"...

Everything seems to be otherwise fine, and this detail is probably only relevant to OCD people ;) but it this normal/expected?
[Magisk] topjohnwu:
For those running Android 8.1 DP2 and found out that SafetyNet no longer passes with Magisk installed, I tested on my 100% stock, bootloader locked Nexus 5X, and SafetyNet won't pass.

So Android 8.1 DP2 itself is the culprit, not Magisk.

If you want to have SafetyNet passed, please do NOT upgrade to Android 8.1 Developer Preview 2!!
[Magisk] powerpuff1978:
I have a oneplus 5 that is unmodified other than being rooted and four different times I have lost root. I couldn't figure out why this was happening and one day my partner randomly asked me how theirs lost root. It happened twice to theirs since the upgrade to magisk 14.0 and then I realized that's when mine started as well. I am not sure how to provide additional information since I can't figure out how to recreate it but I'll try to check this thread the moment it happens again
[Magisk] braschlosan:
I am seeing similar random losses of root as Powerpuff78

Looks like this is an ongoing problem https://xdaforums.com/apps/magisk/losing-root-time-magisk-v11-magisksu-t3569008/page7
[Magisk] DodoGTA:
Can you try to run "su" and "/root/magisk su" commands in a terminal emulator when in that root loss state (in the latest Magisk beta)?

If both commands give root access, then you're experiencing Zygote app-only root loss (I actually don't know how it can be fixed)

If the first command doesn't give root access but the second one does, then you're experiencing the same kind of problem as me (I have more info on this issue, but I'll make a new post about it when it happens again)

If something else happens than those issues listed above, then I don't know
[Magisk] Mejilan:
Well, the issue's probably moot since it seems like my phone is dying a slow-ish death.

But would this be a concern otherwise? And if so, would I be able to manually fix it without repercussion or submitting a bug report to the ROM maintainer? (DU builds based on Nougat are essentially dead as they've shifted to adapting Oreo).

I definitely do NOT know that it's a Magisk issue. Sounds like the timing with the Magisk update is entirely coincidental. And I think you're right. I think the phone is finally in its death throes. During my commute this morning, it hard-locked. Had to use the hardware keys to force a reboot. Once rebooted, a solid 20% of my battery life was just gone. Like nothing. Almost 2.5 years, I guess I can't complain. I've never owned a phone this long without upgrading. Time to see if the U.S. non-carrier variant of the LG V30 is available for purchase yet. Was eyeballing that one as my next device, but I'd rather get one that can be bootloader-unlocked and rooted. I just hope my Moto lasts long enough...

Thank you both for your help in diagnosing my issues. But now I'm pretty confident it's imminent hardware failure, and not a Magisk issue.
[Magisk] firoz3321:
Hi i am on Oneplus 5 Oreo 8.0.0 Beta 1.

My safetynet was pass first few days then it fails from morning. Tried re installation of Magisk still fail. I read that 8.1 oreo it fails but mine is 8.0.0. Also i do not use xposed.
[Magisk] DodoGTA:
/data/magisk_debug.log?
[Magisk] Jowhee:
Same here, it has happened on OP5 Beta 1 the leaked beta 2 and even on liquid remix. It's not on reboot either, I was playing pokemon go, and randomly the game stopped responding, my let connection went dead. I closed the game, and sure enough safetynet was failed.

Edit: I've attached the logs, but I'm not sure if they'll be of any use as I tried to reflash magisk.
[Magisk] firoz3321:
Actually i searched in /data/magisk

Thanks for letting me know tge proper path

Unable to attach file here.

https://drive.google.com/file/d/1iR4cWxtCuWEZPwh9iTgKgebUijKEXxsN/view
[Magisk] joeyddr:
Safetynet is now passing for me and i am able to add a card in android pay, google must have fixed it on the back end.
[Magisk] starbright_:
I have installed magisk (via TWRP) and magisk manager latest version on LOS14.1. As a beginner I just used it for root. It works. After a short while I don't get root anymore. Magisk Manager reports that magisk is not installed and not rootet. But it was before. I hava an installed AFWall as for instance. What is happened? Strange!?
[Magisk] DodoGTA:
Have you tried to reboot your device and see if that problem disappeared?
[Magisk] starbright_:
Thank you.

Indeed after a reboot it works again ! Is this a bug or why this happened? I don't really understand this behaviour.
[Magisk] kantjer:
Are you using SD Maid? There was a bug in SD we're it removed magisk.db causing root loss. That issue is fixed in today's SD beta release
[Magisk] starbright_:
Nothing like that. The only I changed was some setting in AFwall...
[Magisk] AnonAlb:
I can not download iYTBP through magisk manager, the app downloads the zip file and then crash. What do I do?
[Magisk] woozie.2007:
anyone knows why titanium give me force close? i tried to update titanium and now not working at all. I removed latest version and installed old version which works before, but now nothing works, no version of titanium backup. Please help me, thank you. I downgraded from magisk 14.5 to magisk 14.0 but i get the some message, titanium backup keeps stopping
[Magisk] NAMZHD4:
Have you disabled youtube and uninstall any updates if so then try flash zip in recovery instead

https://www.google.co.uk/amp/s/xdaforums.com/apps/magisk/module-iytbp-magisk-t3619705/amp/
[Magisk] AnonAlb:
Yes
[Magisk] NAMZHD4:
Try the non root version outher than that I'm at a loss :confused:
[Magisk] Signor Rossi:
Hi, how can get the boot.img if I don't have root ?
[Magisk] Wolfcity:
Unpack it from your rom /firmware.
[Magisk] theburrus1:
I have this problem with Magisk 14.x

I am rooted okay but any module I Download fails within Magisk. Also trying IN TWRP it appears to install successfully but upon rebooting there's no modules still in Magisk. The error log from Magisk reads:

- Copying zip to temp directory - Installing ViPER4Android_FX-v2.2_2.5.0.5.zip Unzipping files... Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip inflating: .gitattributes inflating: .gitignore inflating: META-INF/com/google/android/update-binary inflating: META-INF/com/google/android/updater-script inflating: README.md inflating: common/aml-patches-remove.sh inflating: common/aml-patches-wipe.sh inflating: common/aml-patches.sh inflating: common/aml-xml-patches-remove.sh inflating: common/aml-xml-patches-wipe.sh inflating: common/aml-xml-patches.sh inflating: common/post-fs-data.sh inflating: common/service.sh inflating: common/unity-audmodlib/audmodlib-post-fs-data.sh inflating: common/unity-audmodlib/audmodlibmodule.prop inflating: common/unity-audmodlib/modid.sh inflating: common/unity-audmodlib/util_functions.sh inflating: common/unity-audmodlib/xmlstarlet/arm/xmlstarlet inflating: common/unity-audmodlib/xmlstarlet/arm64/xmlstarlet inflating: common/unity-audmodlib/xmlstarlet/x86/xmlstarlet inflating: common/unity-customrules1.sh inflating: common/unity-files-wipe.sh inflating: common/unity-props-remove.prop inflating: common/unity-props.prop inflating: common/unity-uservariables.sh inflating: config.sh inflating: custom/libv4a_fx_jb_NEON.so inflating: custom/libv4a_fx_jb_X86.so inflating: data/placeholder inflating: module.prop inflating: system/addon.d/audmodlib.sh inflating: system/addon.d/modid.sh inflating: system/app/ViPER4AndroidFX/ViPER4AndroidFX.apk inflating: META-INF/MANIFEST.MF inflating: META-INF/CERT.SF inflating: META-INF/CERT.RSA ******************************************* * ViPER4Android FX * ******************************************* * Universal - Mod * * v2.2 (2.5.0.5) * * by ahrion, zackptg5 * ******************************************* - Mounting filesystems - Mounting /system, /vendor, /data, /cache Found /data/magisk_merge.img Mounting /data/magisk_merge.img to /dev/tmp/magisk_img /data/magisk_merge.img mount failed... Failed! ! Installation failed

Can anyone help?
[Magisk] DiamondJohn:
In recovery.
[Magisk] dantexaiver:
Ok just flash please feel to stock Oreo and magisk fails to install log attached
[Magisk] Fish&Chips:
I have a weird issue. I'm using the current Magisk 14.0 with Manager 5.4.3 on stock Nougat 7.0, everything seems to work fine, I have root, apps can get root without issues, modules work, I pass SafetyNet, I don't lose root, you could say it works as it should. However, since I updated the Manager to 5.4.3 I've been having some issue where it seems the manager crashes in the background, so I see no real error, and it restarts the process again without me having to do anything. I understand this is how it's supposed to work for people who had issues losing root, but when it does that, it causes a very noticeable lag, to the point it can freeze the device for a few seconds and then continue like nothing happened until the crash occurs again. I have a log of Magisk Manager but the option to attach files doesn't appear for me here, so I don't know if I should just post it as text. I already tried clearing the caches, which did nothing, and even uninstalling and reinstalling Magisk, which also didn't fix the issue.
[Magisk] Rhymey:
Hi, I posted this in the beta thread but it got deleted, possibly this is the more correct location to post?

I am having a bit of a weird issue. SafetyNet appears to stop passing completely randomly during use, after about 4-8 hours, whether I am using the phone or not. The app will crash, and will then not reopen. Following this FC, SafetyNet fails. If I test any time after that fail, I receive a message saying "response was invalid". Screenshot attached. Edit: whoops nvm, XDA won't let me upload any screenshots. Image here

The interesting part, to me, is if I use the uninstaller from the main thread, uninstall>boot to system, uninstall the remaining magiskmanager app, reinstall Magisk 14.5 beta, 'hide magisk manager' in settings, I get SafetyNet passing again.

Device info is a XiaoMi RedMi Note 3 Pro (Kenzo/Snapdragon), running Nitrogen OS 8.0.0, with stock kernel. I am not using BusyBox/exposed. The ROM is not prerooted, magisk is the only root on the rom.

I am more than happy to post the logs, but I may need some pointers on how to get the relevant info, as I've been uninstalling/reinstalling Magisk for troubleshooting, I imagine my logs may not indicate any issues. I've attached the logs currently on my phones data/magisk_debug.log, but if you need the logs right after this issue happens instead of post uninstall-reinstall, I'll post again as soon as it happens again.

I appreciate any and all feedback or tips on how to get Magisk passing consistently :)
[Magisk] ZzEzZ:
Safetynet stopped passing & my installed modules disappeared after I installed iYTB from the repo/rebooted. MManager doesn't show any installed modules (& I can confirm the modules I did have installed are not currently active).

If I download/install a module now nothing new appears where installed modules normally would. A restart didn't help. Reinstalling the latest magisk & MManager releases also didn't change anything.

Any ideas as to what happened or how I can fix this?
[Magisk] KevMetal:
I fixed this error in my phone by formatting data to ext4 ... the error is because magisk or twrp can't mount data ( in my case it was because data was in fs2s file format )

*Nobody responded to my post about the above but I found some video on YouTube go figure .
[Magisk] theburrus1:
Ahhh... That makes sense! It is currently f2fs actually! I will try that. Otherwise I will reply back here only if it doesn't work. Thanks.
[Magisk] jenslody:
This looks like a bug of the module, so it should be fixed by it's maintainers.

To regain access to your modules, I would try the following:

first I would try to disable iYTB in recovery, see my post about doing it (it's for xposed, but in general it's the same), and if it does not work, remove it.
[Magisk] firoz3321:
Is the log file accessible? Its a direct link.

I am still unable to pass safetynet.
[Magisk] DiamondJohn:
Crash on SuperUser view

The pop-ups were an issue, as some of my root apps run in the background with the screen off (eg my clock synch on boot). So before I cleared the data, I took a copy of the su.db file to have a record of all the su granted apps so I could manually do them and restore all the su grants. Interesting thing here is that when I looked at the list (unfortunately AFTER I deleted the data), I noticed there were two lines for one of my apps. Ironically, the su grant is only needed on installation, so it is now running with no su permissions, so I cant duplicate the issue if it has something specifically to do with the particular app. They did have unique values for the uid field, which was what the error message would say is the "duplicate key in index" issue :confused:

Next time I am going to try to delete one of the duplicates to see if that manages to avert the issue without having to loose all my other records.:mad: or someone else might give it a go and report back?
[Magisk] Didgeridoohan:
There might be an issue with the Manager and larger modules. It's under investigation...

Meanwhile you can download and flash the zips manually from the respective threads or GitHub (don't forget to repack with all the files in the root of the zip of downloading from GitHub).

Try the v14.5 beta instead.

I like logs. Logs are nice... :p

Upload to Pastebin or similar and provide the link or id.
[Magisk] brenosnt:
I'm getting error when installing modules.

Magisk version: 14.5 ( beta)

Magisk Manager version: 5.4.3

ROM: AICP 12.1 - Android 7.1.2

Sorry, i can't upload logs, but this message is ALL that is on logs generated. All is working fine, except this

- Copying zip to temp directory

- Installing TaskerRootBuildProp-1.0.zip

! Magisk is not activated!... abort

Failed!

! Installation failed
[Magisk] Didgeridoohan:
That's an old module... Which is the reason behind your error. You'll need to update and luckily I've kept it updated. Updated to template 1410 just the other day and you'll find it here: https://xdaforums.com/showpost.php?p=71862904
[Magisk] brenosnt:
I'm getting this error with ALL modules, Tasker Root is only an example

- Copying zip to temp directory

- Installing Android_Mic_Fix-v3.2.2.zip

- Mounting /system, /vendor, /data, /cache

Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip

inflating: common/post-fs-data.sh

inflating: common/service.sh

inflating: common/system.prop

inflating: config.sh

inflating: module.prop

*******************************

* Android Mic Fix *

* by: Nomelas *

*******************************

******************************

Powered by Magisk (@topjohnwu)

******************************

- Found /data/magisk_merge.img

- Mounting /data/magisk_merge.img to /dev/magisk_merge

! /data/magisk_merge.img mount failed...

Failed!

! Installation failed

ALL this modules are previous installed, but after clean my device, i'm getting this error
[Magisk] unkash:
Hi

I cant install modules. I get error Mounting /data/magisk_merge.img to /dev/magisk_merge

If i download module (.zip) and try install it by recovery, i get error mounting /data.

My data partition is ext4 an my phone isnt crypted.

What is the problem?

Thx
[Magisk] veez21:
[MENTION=4667597]Didgeridoohan[/MENTION]

Do you know how magisk modules in a/b devices are structured? Are the directories in /magisk/mod_name/system/system or just /system?
[Magisk] Didgeridoohan:
If you pay attention you'll see that you've got two completely different errors.

First one:

! Magisk is not activated!... abort

Second one:

! /data/magisk_merge.img mount failed...

Provide logs... Magisk log and magisk_debug.log (look in /data) is a good start.

Look above (the part about logs).

Absolutely no idea... Take a look at the modules by [MENTION=5357345]ahrion[/MENTION] and [MENTION=6037748]Zackptg5[/MENTION], they seem to have it figured out.
[Magisk] ZzEzZ:
You were right. I tried out MM in recovery, removed the module, and everything went back to normal.

Great advice. You saved me from having to restore a backup.
[Magisk] unkash:
I dont find magisk_debug log.

I've attached Two logs, magisk.log and install magisk log

And repeat, my /data partition is not crypte and it's ext4
[Magisk] dantexaiver:
With the beta do we still have to use a boot image
[Magisk] Artim_96:
You can patch a boot image and patch it or flash it through TWRP
[Magisk] Rhymey:
Hello! Here is my followup post with the magisk_debug.log from right after this happened.

Same drill - SafetyNet fail, safetynet invalid, uninstall>system>uninstall manager, reflash 1456 and it passes again.

I've tried UniversalHide as well as the previously-suggested 'magisk core only' to no avail. Seems reflashing is the only working step.

Any advice hugely welcomed :)
[Magisk] Zackptg5:
[MENTION=7296895]veez21[/MENTION]

With magisk, it's just /system, no goofy /system/system stuff with v14.x (not sure about older versions but who'd use them anyways).

One interesting thing is that vendor must be /system/vendor regardless of whether or not the device has a separate vendor partition. Just how magisk mount does it's thing I guess
[Magisk] SuperSmashedBro:
Anyone else getting random reboots on their pixel 2 with 14.5(1456)? My phone would randomly reboot, go straight to the Google logo screen and then boot back up. Then after a couple of seconds, it would reboot again to the logo screen. This would keep happening until I force a reboot and it would be okay until it happens again. I've experienced this on 3 different phones
[Magisk] DodoGTA:
Have you tried to reboot?
[Magisk] sonic997:
i am a samsung s5 g900f user. stock Rom

i need root and flashed v6 magisk since i want to play Pokemon go. pokemon go detect my root so i use systemless v6.

however, device comes with contact stopped. media storage stopped, etc.

and my phone fails to work anymore. i love systemless, but what can i do?

please, help me. thanks
[Magisk] mobileman88:
Turn off root in magisk Manager and it will turn green
[Magisk] Didgeridoohan:
Ok, cool. Thanks for getting that cleared up.

Funny thing is, that for me it works sometimes. I haven't been able to work out what makes it work those few times though...

Right now it seems the only people reporting this issue are using a Nexus 6. Seems like it's specifik for our device. Let's hope the major overhaul of v7 makes a difference.