yashsingh1/xdaforums huggingface dataset:
[Magisk] Karls0:
Ok, it doesn't matter if it reboot to recovery it to system. I see it crash on building .img but I have no idea why. It still looks like recovery bug, it shouldn't restart no matters how the package is broken. To be sure, check file md5, it should be:

1ec332817b86f276f5e4bc5e144c7049

If it matches, I would suggest to maybe try other recovery version. I know it is extra work, but it's a bit uncommon behavior.
[Magisk] smileyhead:
it does match. problem is, only two versions work with my phone currently. 3.0 and 3.1, and they both encounter this problem.
[Magisk] SacredDeviL666:
Nopes even with 7.1.1 and magisk v11.1 it doesn't let me through. Also my device is blocked already. Because I tried a room without root or magisk preinstalled and still security failed.

I have requested system admin to unblock hope they do. Advise is not to use citrix with magisk specially mdm server I can use regular citrix. Or if someone else can come up with alternative.
[Magisk] Karls0:
We definitely need more data. Check if you could save a log from this error. Look here, I found a tutorial:

http://rootzwiki.com/topic/24120-how-to-get-a-log-from-twrp/
[Magisk] rocky78:
see the post some pages ago, i think there is something

with that, mybe citrix is using the same method to find root.
[Magisk] emensch:
Ok so I got it installed but not I can't get it to pass safety net... Any ideas I'm on a Rooted BLU R1 HD
[Magisk] rocky78:
[MENTION=4470081]topjohnwu[/MENTION]

decided to upload magisk log file, is every thing ok with this? (com.google.android.gms.unstable)

p.s.

needed to zip it because of the Large file.
[Magisk] smileyhead:
it doesn't seem like the log is getting saved. I can only see the one from the session before the install.
[Magisk] tag68:
Motorola (Lenovo) seems to have included a fix for f2fs which mounts loopback device read-only with March 2017 patchlevel nougat for Moto Z Play (don't have the update myself by now) which has data partition with f2fs. Reported was that Magisk can be installed, but Hide does not work. It is probable that other Motorola devices will get the same update.

Is it possible to support Hide under these circumstances?
[Magisk] Karls0:
So we know nothing about why recovery fails. Maybe try to by-pass it? You can use flashfire or something similiar https://xdaforums.com/general/paid-software/flashfire-t3075433

I'm not sure if it will works, and if it is safe way to install magisk so you do it on our own.
[Magisk] rfgamaral:
I currently own an HTC One with Magisk v8, Magisk Manager v2.1 and with 2 modules installed, phh's SuperUser r259 and Xposed Framework (SDK 23) v86.6.

What would be the proper way to update to the latest versions of all of the above without breaking anything?

Sorry if this has been asked before but I've been out of the game for a while now...
[Magisk] Danny94:
My problem:

https://xdaforums.com/showpost.php?p=71891105&postcount=12331

Fix: This working for me meantimes:

https://multirom.me/read.php?tid=1594&fid=72&page=1#86397

But on every reboot i have to start magiskhide manuelly...
[Magisk] Tesla:
Great that you found a fix. Can you please write a translation here?

Do you reboot often?
[Magisk] teddy0209:
Just remove the old version, restore your boot.img and flash the latest version of magisk... Then install the manager, just download updated modules from there...
[Magisk] rfgamaral:
Do you mean remove the old Magisk version or the old Magisk Manager version? If it's the former, should I flash the uninstaller for that?

Following your procedure, can I install the manager from the Play Store after flashing the latest version of Magisk?
[Magisk] Tesla:
1. Flash the uninstaller

2. Restore your boot.img

3. Flash the latest version of magisk

4. Install the manager from the Play Store

5. Live long and prosper.
[Magisk] smileyhead:
it doesn't work without root (obviously), SuperSU won't flash (same problem as with Magisk) and Towelroot doesn't work either (not supported). :(
[Magisk] teddy0209:
Magisk itself... It doesn't matter if you install the manager before or after...
[Magisk] Karls0:
Well you should start with this information. Now it's clear that it is TWRP/Phone issue, if you can't flash even this well-tested SuperSU zip. You have two option:

1. Go to your TWRP forum, post bug report and wait for the fix

2. Try to root your phone in other way (ADB, your manufacturer flash tool etc.) and check if you can push Magisk via flashing app. But here you will have a problem. It is possible to root with SuperSU via ADB (look Here), but i'm not sure about MagiskSU which is nesesery to use MagiskHide. The tutorial I linked is about pushing SuperSU in system mod. But maybe if you will have any system root, you could flash magisk and replace it with this systemless one .
[Magisk] sheyac:
Phone: Samsung i9505

Rom: Optimised Lineage OS 14.1 (7.1.2) by JDC

Magisk SU v12 and also tried v13 (test)

Ok so i have been doing all sorts of tests today. I removed busybox that came with rom to help isolate the issue as much as possible. Basically on boot, safetynet passes, and root checker apps (which I've checked to hide SU) don't ask for SU and don't see SU binary.

1. If i end the app (root checker) and start it again, it sees the SU binary and requests root. Safetynet still passes (checked with 3rd party app).

2. After a random period of time, safetynet fails.

Something is changing or refreshing, but not quite sure how to capture this. I've tried the logger in Magisk but haven't found anything in there that could help.

Any ideas?

I've tried the following:

Full removal of Magisk

Run unsu

After which safetynet shows CTS mismatch (i think because selinux is set to permissive) but root checkers correctly show no root.

Removed SuperSU directory and from device "/"
[Magisk] ballerd:
Its actually busybox mount -o remount,rw /system

You didn't specify the / bit before the partition you want to change :)
[Magisk] Danny94:
I used google translater too.

In general it's necassary to flash magisk 11.6 and on every reboot put in a terminal:

su
sh /magisk/.core/magiskhide/enable

I normally don't reboot much often so it's ok for me (boot up copy paste from text file =) done in few seconds). For others would be useful to make a script wich automatically got excecuted on boot with this lines.
[Magisk] zurik:
Hello to everyone, when I want to install a module from Magisk manager, I have error , in every module that I want to install... Any solution on that?
[Magisk] Didgeridoohan:
Try flashing through recovery instead.
[Magisk] zurik:
I just reinstalled Magisk. Thanks for your time to help me! :angel:
[Magisk] Tesla:
Dude.. you need to send that in a file or hide it.

Like this

Same if you put Magisk on phone, not SD-card?
[Magisk] emensch:
Ok I got it installed but now it won't pass safety net any ideas?
[Magisk] Tesla:
I could be wrong here, but i think you have other root. Under "Properly Rooted" it's says 8:MAGISKSU for me.

Are you completely unrooted?
[Magisk] Citizen_Snips:
Yes, unroot SU completely from the app (Full Unroot option) and flash your boot.img again (unless it is pre-rooted) and then flash Magisk again. Magisk can't hide SuperSU.
[Magisk] emensch:
Ok I'll give it a try thanks
[Magisk] Madreverse:
I did not know that option existed, I'm sorry!

I do not have an SD card on my phone. I have no idea why it reports an error on it.
[Magisk] Tesla:
It's the option to your far right, a button named "hide"

You mark the text and then pres it. Then to see if it's working you press Preview Post.

Yes it's strange.

Maybe restore your boot.img. Download Magisk 12 again and then try?

If nothing works then restore your phone completely and return here.

This is how i do it.

Unroot with superSU app.

In TWRP i flash UPDATE-unSU-signed.zip.

Then i flash Magisk 12.

Boot and install Magisk Manager app from Play store.
[Magisk] TheHeroBilly:
Does anyone have an issue where root is removed randomly after reboots? I can fix it by reflashing the zip, but I have no idea it happens until I try to get root. It's happening on an OP2 and a Samsung S5
[Magisk] Tesla:
Yes, there are reports of that happening.

I have no solution for you though.
[Magisk] Nomelas:
Keep either magisk hide or busybox disabled.
[Magisk] Madreverse:
Thanks for that information, I won't forget about it next time :p

I don't know how to restore boot.img, and I searched google, but I only got results from 2012/2013 and it was in how to backup...

I did the unroot with superSU + flash unSU + flash Magisk12. I still get the same error :(

So, now I don't have a rooted phone, can't install the magisk, and I dont pass the safetynet test. I'm really bad at this lol
[Magisk] TheHeroBilly:
I use Android pay, so I need magisk hide enabled and can I just install a different BusyBox?
[Magisk] Nomelas:
Not sure. You can always try
[Magisk] Tesla:
For root try superSU app.

There might be answers for you here: https://xdaforums.com/huawei-p8
[Magisk] jhedfors:
Please don't depend on HIDE as it does not even work with the official mobile app!

Attach

Attach

Attach

:)
[Magisk] Tesla:
That's so weird haha. I'm always at computer so i didn't think of that.

Good you spread the word.
[Magisk] Didgeridoohan:
I see you found how to save the recovery log. :)

Unless you choose to restore the stock boot image when doing a full unroot in the SuperSU app you'll have to do that yourself. In your device's factory image or ROM zip you can find a file named boot.img. You can flash this easily in TWRP by choosing the "Install image" option and then selecting the file like you would when flashing a zip (and then selecting "boot" when prompted). After that you should have no more issues installing Magisk, assuming that your ROM does not come pre-rooted with SuperSU, but I have a feeling you're using stock ROM and in that case it won't be an issue.
[Magisk] DvLAx3l:
Hi guys, can u help me with Magisk Hide? Can't pass the SafetyNet, I think the issue is the magisk hide daemon because with a root checker and the hide option on it still capable to find root. I'm new in Android world so be patience if I say some bul**** or noob question :P
[Magisk] Didgeridoohan:
Details, details, details... Number one thing when asking for help.

I'd like to see, at least, what device and ROM you're using, if you have a custom kernel and a Magisk log.
[Magisk] DvLAx3l:
Yep, u r right, sorry!

The device is Samsung S4 Galaxy i9505

Rom optimized LOS 14.1 stable 2 android 7.1.2 from JDC team with alucard custom kernel

Rooted with magisk 12

I already try to unroot with magisk uninstaller and then root again from recovery with magisk 12

No adaway installed, no systemless host option activated, just the magisk hide on.

ADB in Dev option is off

Root is activated only for apps
[Magisk] Didgeridoohan:
There's been a couple of reports lately about Magisk Hide issues with that ROM. But I suspect you've seen that as well, since you're bringing up systemless hosts. :)

Probably a ROM issue that might be fixed with future updates. Might be that a boot image copy needs to be uploaded to a relevant issue on GitHub though...
[Magisk] ionel2oo6:
To fix the SafetyNet, enable busybox from settings and restart the phone , this fixed the issue for me
[Magisk] DvLAx3l:
Nope, that didn't work.

The major issue is the hide option that doesn't work, I can't even hide a root checker app! :P
[Magisk] Madreverse:
I did! ^_^ now that I know how to it's pretty simple, but at the time it was very confusing.

It's probably my lack of understanding and knowledge but I searched my phone and I don't find any file boot.img. I searched through the phone itself and through the computer. I also searched google to try and download a boot.img and found this site: https://developers.google.com/android/images#angler but I have no idea if it's suitable for my phone...

I'm sorry that I keep asking these stuff, I don't mean to be a pain, but I really am trying to understand this "new world" and I'm feeling desperate right now :|
[Magisk] joeyfong:
Any idea to solve this?
[Magisk] dahawthorne:
You're not rooted. If you already had SuperSU installed, use unsu to fully unroot, preferably reflash your stock boot image, and install Magisk again. I had better success on my first Magisk installation by flashing it in TWRP rather than via Magisk Manager.
[Magisk] Didgeridoohan:
No worries... Everyone's a beginner at one point or another. What's important is that you do some proper research before doing anything (read, read and then read some more) and be prepared for complete failure. I can't remember the number of times I've soft bricked my devices... :D With TWRP and an unlocked bootloader most issues can be fixed though. ALWAYS have a backup! Reading up on ADB and fastboot is also a good idea.

The stock boot image won't be on your device. Before you flashed unSU, there was probably a copy of it saved by SuperSU, but the unSU zip deletes that. In the link you found, there are factory images for Google's Nexus and Pixel devices. Don't use those... :p What you need is the equivalent for your device. It's important that you find the exact match to your system or you'll have issues.

DISCLAIMER: What follows is from research I did out of my own curiosity on how to fix your issue. I do not own a Huawei device and I've never used any of the firmware files or programs I'm linking. Before you start messing with your device too much, I'd advice you to make a full backup in TWRP (I can't stress this enough). I can try to point you in the right direction, but I'm not responsible for what you do to your device...

In your device's forum (Huawei P8) I see a few threads like this one (just an example, I have no idea if it matches your device): https://xdaforums.com/huawei-p8/how-to/firmware-huawei-p8-gra-l09-b394-29-03-17-t3581039. In there you'll find a link to a full update zip. What you need to do is to find a thread matching your exact device and system version, download the update.zip and inside there you'll probably find a file called update.app. To extract the boot image from it, you'll need a program like this one: https://xdaforums.com/showthread.php?t=2433454. Once you have your boot.img transfered to your device, boot to TWRP and flash away, I hope... :p (you could also use fastboot to flash the boot image)
[Magisk] joachim123:
I just want to +1 this, cause i didnt know how to properly capture the logs while its in the middle of its soft-reboot session.

I have an LG V20 (H918) Running the NATF Rom, also on Magisk v12.

I also notice when it goes into the soft-reboot session, a lot of the start up apps dont start and i dont see the notifications. Such as Pebble (shows if its connected or disconnected), or GSAM Battery monitor, or if i had existing unread messages that normally pop up as a notification, they don't unless i turn MagiskHide back off and do a full reboot.
[Magisk] aik.nayan:
I posted this many thared because I didn't find my answer. & Fortunately all of helpful members. Suggest me same time. & Sorry for Spam
[Magisk] DodoGTA:
[MENTION=4470081]topjohnwu[/MENTION] Magisk v12 is worse than v11.6 (v12 has high CPU usage of magiskhide process and CTS profile mismatch even with Magisk Hide on, but v11.6 doesn't have Magisk v12 flaws)
[Magisk] Ibuprophen:
I just wanted to let you all know that Stericson just pushed an update (via the Play Store) to his BusyBox app and had noted the following regarding what the update was for.

"Enabled logging by default to help debug some issues some users are having with Magisk"

I just wanted to spread the word...

Thank You!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[Magisk] dahawthorne:
[MENTION=6429309]DodoGTA[/MENTION]

Wow, that's disrespectful, especially coming from a dev...

I've been using 12 & 13 for weeks. No battery drain, no hide problems, all working fine. Maybe you should look at your setup before throwing stones.
[Magisk] DodoGTA:
Older devices are having high CPU usage in Magisk v12 because of problematic commits in magiskhide binary
[Magisk] Tesla:
That was a bit to harsh, don't you think? "Magisk v12 sucks"

Magisk v12 works perfectly for most users with no high cpu usage.

It's great that you leave feedback.. but dude...chill.
[Magisk] DodoGTA:
I edited my original post a little bit, by the way

Note: I found another person complaining about that problem:

https://github.com/topjohnwu/Magisk/issues/153
[Magisk] Wawax:
Hello people i'm new in this forum and i have a problem with magisk who doesn't recognize the safety net so i can't play PoGo so can you give me a solution please for this Big problem for me
[Magisk] izeeqo:
Can i keep my custom kernel (xceed kernel) or must i uninstall it and must have the stock kernel??
[Magisk] Fedroid:
You can keep it
[Magisk] izeeqo:
Thank you. Latest question : Is there an installation order to respect? For example: Install Supersu, flash xposed and finally flash Magisk? Or can i proceed in any order? because I don't want to make mistakes :)
[Magisk] Kellwa:
I deleted folder from this location

/magisk/.core/mirror/system/app/calculatorwidget

Now the widget is gone

So does this action edited the system?

If not how to reverse it?
[Magisk] CrazyCypher:
I have a few system apps I disabled using mount /"appname"/.replace do I have to disable this or leave it when trying OTA?

Thanks :)
[Magisk] Fedroid:
From twrp recovery

1. Flash Magisk

2. Flash Root

Reboot and install

1. Shh su apk

2. Magisk apk

3. Material Xposed apk

Reboot to recovery

Flash xposed

And you are done
[Magisk] Kellwa:
Please can you tell me exactly how you disabled your apps
[Magisk] Artim_96:
Well, wiping system was already useless in the first place, since you wanted to get rid of the Magisk version of SuperSU, /system is never touched. You would need to at least run the Magisk uninstaller and reflash the boot.img. when you're then back inside TWRP, look for stuff like /data/Magisk.img and /cache/magisk... But that's all just to get rid of Magisk.

Yes, you always need to reboot of you enable/disable mods in XPosed. Not only in this version, for all I remember it was always so.

And when your apps don't work it's possibly because they detect XPosed. You have to deactivate it and reboot, there is no method to do so like the unmount of root (yet).
[Magisk] CHAMAVELI:
Replacing the build prop does in fact work it's just not the best solution. Seeing as the module was working fine and all of a sudden stopped after a couple reboots means there may be an issue with Magisk.

Another reason why replacing the build prop isn't the best solution is when updating your ROM. Using setprop will only "change" a select few properties inside the file on the fly instead of replacing the whole file, hence not needed to grab the original each time and changing it. This is quite a hassle, as you would need to disable the module, reboot, grab stock file, throw it back into Magisk cache, delete disable file, reboot again. Using the same build prop over and over isn't the best as it contains build number, Android version etc.

Using setprop and scripts the steps would be to simply just apply the update.
[Magisk] chazall1:
Will we be seeing v7 or has development been discontinued.

Thanks
[Magisk] Captain_Throwback:
http://xdaforums.com/android/software/mod-magisk-v1-universal-systemless-t3432382/post68463285
[Magisk] chazall1:
Great to here. I really like Magisk implementation of SU
[Magisk] danielcr12:
Are you planning on supporting more boot.img ?? Magisk isn't compatible with my moto x. I think my boot.img isn't standard or something. I'll attach it later.
[Magisk] Sivat:
Hey! I just magisk'd Dolby Atmos R6.6 from the HTC 10 audio thread.

https://drive.google.com/file/d/0ByRPtdp5OYAXTDd2eFRhaHpPMGs/view?usp=sharing

I ran into a problem though if anyone can help out with it.

If v4a is installed than the audio.confs in /magisk/v4a/etc and /magisk/v4a/vendor/etc need to be patched. Magisk doesn't combine the files from different mods and will use the ones in the very last module in the directory(it seems). I tried to do have it automatically check in the update-binary but I kept getting an error with the if statement because I don't know shell scripts too well.

I had something pretty much like this for the binary-updater but I kept getting errors from it.

V4A=/magisk/v4a
if [-f "$V4A"]; then
CONFIG_FILE=$V4A/system/etc/audio_effects.conf
HTC_CONFIG_FILE=$V4A/system/etc/htc_audio_effects.conf
VENDOR_CONFIG=$V4A/system/vendor/etc/audio_effects.conf
fi
else
CONFIG_FILE=$MODPATH/system/etc/audio_effects.conf
HTC_CONFIG_FILE=$MODPATH/system/etc/htc_audio_effects.conf
VENDOR_CONFIG=$MODPATH/system/vendor/etc/audio_effects.conf
fi
if [ -f "$CONFIG_FILE" ]; then
sed -i 's/^libraries {/libraries {\n dap {\n path \/system\/lib\/soundfx\/libswdap-mod.so\n }/g' $CONFIG_FILE
sed -i 's/^effects {/effects {\n dap {\n library dap\n uuid 9d4921da-8225-4f29-aefa-39537a041337\n }/g' $CONFIG_FILE
fi

if [ -f "$HTC_CONFIG_FILE" ]; then
sed -i 's/^libraries {/libraries {\n dap {\n path \/system\/lib\/soundfx\/libswdap-mod.so\n }/g' $HTC_CONFIG_FILE
sed -i 's/^effects {/effects {\n dap {\n library dap\n uuid 9d4921da-8225-4f29-aefa-39537a041337\n }/g' $HTC_CONFIG_FILE
fi
if [ -f "$VENDOR_CONFIG" ]; then
sed -i 's/^libraries {/libraries {\n dap {\n path \/system\/lib\/soundfx\/libswdap-mod.so\n }/g' $VENDOR_CONFIG
sed -i 's/^effects {/effects {\n dap {\n library dap\n uuid 9d4921da-8225-4f29-aefa-39537a041337\n }/g' $VENDOR_CONFIG
fi
[Magisk] JudgeDread11:
Seeing you are the only one experience this problem I doubt it is a magisk problem or is very device specific.

And without knowing what causes this nobody will ever be able to solve this.

Reproducing and creating logs from the moment in which the mod stops working will likely be the only way to find out the answer to your problem

Meaning bringing back your device to the state where it was working and then log everything until the point where it stops working.

Although good for the development of magisk, if it actually is a magisk problem, that'll be way more of a hassle then using the workaround.

---------- Post added at 03:34 AM ---------- Previous post was at 03:26 AM ----------

I don't have enough scripting knowledge to help you with that, but if I get this right you are trying to run 2 mods which effect the same files?

I don't know if magisk has some priority system (if not it might be a nice suggestion for the mod manager), but you can experiment with renaming the mods to have one load before the other.

Or you can try combining them into 1 mod with scripts in the different boot stages.
[Magisk] Sivat:
They both need to edit those audio.confs only once upon installation (it let's the os know where the effects are located) which is why it's easy enough to piggyback off of the ones that get coppied/patched in viper4android.
[Magisk] CHAMAVELI:
You should never been doubtful of a mod having problems, especially one that is still new ;)

Anyway, the way to log Magisk as per the first post is using the last_magisk.log and magisk.log. Both log files show zero issues and respond correctly indicating the script is being run. Are there any other logs I should be looking at?

My device is a Nexus 6 running stock Marshmallow 6.0.1 and custom kernel (happens on stock kernel too).

Returned everything to stock and reinstalled Magisk and recreated the script = still not working. Also looks like the replacing of build prop is no longer working either. Well it is and isn't. I can see build prop being replaced in system and verify that DPI value is different than stock, but the DPI is not changing.

Edit:

Attached photos showing build.prop value and the value that getprop returns:

http://i.imgur.com/E98wb4v.png

http://i.imgur.com/9jyQ0gY.png

Clicky cause they're way too big for forums