yashsingh1/xdaforums huggingface dataset:
[Magisk] koyera:
Every time I try to install modules I get errors. It doesn't matter if I use TWRP to flash or Magisk Manager. No app will install.

Magisk error:

- Copying zip to temp directory

- Installing App_Systemizer_(Terminal_Emulator)-v13.4.1.zip

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

Please install Magisk v15.0+!

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

Failed!

! Installation failed

TWRP Error:

[IMG="TWRP Screenshot"]https://imgur.com/a/RtYtMRl[/IMG]

My Magisk version is 16.7
[Magisk] reinaldistic:
Magisk hide option is completely empty, no apps show I'm the magisk hide app. I cleared cache and data, I even installed (install button on the main screen) and still nothing, apps I had already did root from still dont see it, but I would like to add more apps... Any suggestions?
[Magisk] jcmm11:
Back in the other thread the log seems to indicate it's trying to set the prop, but the screenshot indicated that the prop wasn't set. The question is why. The only thing that the hide navigation bar mod does is set the property "qemu.hw.mainkeys" to 1

That entry should be in the system.prop file in the module directory.
[Magisk] Lk2:
Hi people!

I'm new to Magisk and I'm trying it on an old phone, Nexus 4.

I took it with the latest official ROM, Android 5.1.1 and perform a factory reset.

I installed TWRP without any problem

I flashed Magisk 16.0 without a problem

I didn't install Magisk Manager because 16.7 is already installed after flashing Magisk 16.0.

But when I perform a SafetyNet check, I always get ctsProfile and basicIntegrity to false.

How can I fix this? Do I need an older Magisk version for older Android versions?
[Magisk] jcmm11:
https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet
[Magisk] andrew2432:
Your kernel needs to support magisk hide: mountnamespace. Sometimes kernels are updated. Some now are saying if they are due to the mass use of magisk hide. You could ask around in your device forums about it, or potentially use a custom ROM.

Only my experience, but on my s5 custom ROMs starting with 7.1.2 all have kernels that work!
[Magisk] mr._.nobody:
It seems like i will have to factory reset my device...?
[Magisk] andrew2432:
I quoted you but I was talking to him. Just being a brat about people finding the beta first and bringing their general discussion issues up there lol sorry
[Magisk] KungFuryy:
hello,

i have a Mi A1 Rooted on may 5 security patch

now i want to update to the latest security patch

when i tap "restore images" the following message appears "Stock backup does not exist". and i have never encountered this issue before and didn't find any solution, yet

thanks
[Magisk] Didgeridoohan:
Hold on... I completely misread your screenshot. Sorry about that.

I would be interested to know what output you get when running the following command in a terminal emulator:

su -c resetprop qemu.hw.mainkeys 1

And what Magisk version do you currently have installed?
[Magisk] wvcadle:
I'm guessing flashing the stock system image would ensure the build.prop was back to stock. As for AdAway and that bind command. Do you know of a way to revert that?
[Magisk] RandomPooka:
You could just try deleting the /data/data/hosts file? But, flashing the system image again might actually take care of that anyway.
[Magisk] adrman:
I had a failed transaction today as well, even though I was passing Safetynet helper. My setup was n6p, stock, rooted via SuperSU 2.76. The only mod I had installed was systemless AdAway. I've since fastboot flashed back to stock and rerooted via phhusson's superuser. For the moment, I've intentionally omitted AdAway. I won't have a chance to try a transaction until tomorrow though.
[Magisk] chazall1:
Thanks for the outstanding work on phh. All functioning fine except for the toggle issue on PN. I will keep following Magisk for updates. Wow very nice.
[Magisk] wvcadle:
I think I'm about done chasing this unicorn of root + AP.. at least until the solutions get a hell of a lot easier and more straight forward.
[Magisk] SilverZero:
Correct me if I'm wrong ( I'm just reading through this thread for the first time) but it sounds like the people having failed transactions are either using a mod that writes to system (e.g. non-systemless AdAway) or are using SuperSU. Both are messing with system, right? So it should still all work if you use true systemless mods and phh's su, correct?
[Magisk] IM0001:
Currently it isn't working for the custom roms (at least Pure Nexus) with either SuperSU or Phh. Still it is early in the process soo we just gotta be patient.
[Magisk] wvcadle:
Correction: I'm not using any system mods. I tried to get systemless AdAway working and am using phh’s SuperUser. As long as we're able to use any Xposed module, including GravityBox, I thought it would work but not for me.
[Magisk] adrman:
In my case, we shall see tomorrow. I was using systemless AdAway with SuperSU. The interesting thing is it was passing a Safetynet check, but the transaction failed. I hope I'm wrong, but I dint think we've seen anyone post a successful transaction with either root method yet.
[Magisk] carlosggb:
Hi [MENTION=4470081]topjohnwu[/MENTION] , first of all CONGRATULATIONS on this achievement, this is simply out of this league.

I have problems installing the v86.3-alt version on my note4, this problem i had it also with the others v86's so i don't know if there is something to be changed there.

Also is there a way to make Magisk boot with Selinux permissive (i know i know, even if you don't recommend so).

Thanks in advance
[Magisk] LakerFam0824:
So does this work with the latest Android N beta? This seems like a very cool thing!! If it doesnt will there be future development for Android N?
[Magisk] ChelseaFan257:
I have been able to get AP to allow me to set up cards. Haven't yet tried paying, but maybe this'll help? I'm running Magisk, Xposed, EX kernel,, and build.prop DPI tweaks.

Before you do anything else, extract the pristine build.prop from the stock/custom ROM image you're using. Keep it on your PC or copy it over to /sdcard, either's fine.

Edit this build.prop file as desired.

Reflash /boot and /system.

Flash the Magisk zip in recovery, followed by Superuser, a (compatible) custom kernel, etc.

In the recovery file manager, or via ADB, copy the edited build.prop file to /cache/magisk/mounts/system.

Boot up.

...

Profit.
[Magisk] VBBoston:
Selinux question

I have Sony Z5 compact on Marshmallow 6.0.1 with AndroPlus v.34 kernel. Flashed all according to the instructions here: Magisk, phh's SuperUser and Systemless Xposed v.86.3. Everything seems to work well.

Now when I try to enable switch SElinux Toggle to "enforced" it jumps back immediately to "Permissive" . Any way to fix it or just leave it as is? What would change in terms of Xposed modules compatability and root apps (like Titanium backup and alike) if there's a way switch SElinux to "Enforced" ? Thank you in advance.
[Magisk] KaMyKaSii:
Currently all systemless mods off that topic (hopefully for a short time) has SuperSU as a base, so will not work with PHH's SuperUser
[Magisk] :
Anyone who wants systemless adblock can you test this:

http://xdaforums.com/android/software/mod-rps-systemless-ad-block-t3433672/page1

Edit: it uses Magisk
[Magisk] AaylaSecura:
I can't get this to work... I'm running XtreStoLite debloated, deodexed ROM based on stock Marshmallow Galaxy S6 ROM. It installs the stock kernel but patches the boot image for a systemless SuperSU. I did a full unroot from within Chainfire's app and it seemed to work: no root checker detects either su or busybox, I can add debit cards to Android Pay (I haven't tried actually paying though). Anyway, I did a nandroid backup at this point and flashed Magisk. then I flashed phh's magsk superuser, and I installed phh's superuser app; but it doesn't really give me proper root: I grant permission to the app requesting it but whenever I try to perform an action, it hangs. For example Titanium Backup freezes upon restoring, FX file manager times out when accessing / as root and says "unable to obtain root access", even though it's listed as being granted in phh's log.

So I restored, flashed Magisk again and this time flashed the Magisk compatible SuperSU, but then I cannot enable the root toggle: it immediately unmounts it again....

I also tried (after restoring) to flash the unmodified boot.img but it fails to boot (goes into recovery automatically)... What else can I try?
[Magisk] FunkeeC:
I can add my 2 cents and say i attempted to make a purchase w/ AP earlier today and it failed. It was passing safetynet check and still said cannot make purchase w/ this device. I would like to see if someone is actually able to make a purchase with this setup running.

I have a moto x pure and was running phh SU only (no xposed). I do have adaway running but that doesnt make AP fail ( i know this as i kept the adaway hosts when i unrooted my phone when safetynet was updated and made many purchases since)
[Magisk] kilowatt95:
Just to check, did you flash the Magisk compatible root package found in post #1? I made the mistake of flashing the original phh superuser.zip which lead to me encountering the same issue.
[Magisk] abun880007:
Hi S7 edge G935F is bootlooping no matter what rom or kernel I use, could you please look into.

Kind Regards,

abun880007
[Magisk] Darke5tShad0w:
Developers cannot look into anything much when limited info and no logs etc are provided.

The developer is aware and has been posted alot, Please search next time.

http://xdaforums.com/showpost.php?p=68050672&postcount=161
[Magisk] AbiDez:
Hello, I have backup my apps with titanium backup. When I install magisk and phpsuperuser is it compatible and work? Or it's better to install rom, reboot, restore apps with TB and after that make total unroot und flash magisk?

Other question, I use Arter Kernel... In Post 1 stand, first flash stock boot image, then custom kernel... Then magisc... A normal boot.img extracted from stock is right? Flash over twrp and then directly custom kernel and magisc?

CarHDRom V.24.3 by Carotix S6e
[Magisk] rollerce:
If I boot to recovery, install PhhSU's binary, then boot into the OS, all of the functions and toggles work fine. If I reboot after that, PhhSU reports that the binary is out of date and needs to be reinstalled and Magisk reports that SU is improperly installed. It also begins rebooting randomly at that point. I'm going to try to do another clean install and see what happens, I'll make doubly sure there's no SU conflicts as well.
[Magisk] Agloxp:
Thx, the su binary was still in the /system/xbin/
[Magisk] broomer68:
Tb is compatible, but with different roms, it is alway better to let Google try to recover your accounts and apps, and after all is finished, restore the apps and settings that are not restored by Google.

Verstuurd vanaf mijn ASUS_Z00A met Tapatalk
[Magisk] :
Hi. I have a bad oroblem with magisk on my galaxy s4, running cm13. I installed magisk, systemless xposed 86.5 and phh supersu. Everytging good, but if i want to turn off root in magisk it switches on again. I can't turn it off.

Any idea why it's not working?
[Magisk] JuergenZ66:
had the same problem with my LG G3 and CM13

use unSU in recovery to remove all SU binaries, see here http://xdaforums.com/showpost.php?p=63615067

and then directly reinstall afterwards magisk and phh su

this worked for me

PS: the reason is CM has its own root binaries which interfere with magisk root
[Magisk] mlavende:
So you're saying I don't need to remove my busybox installation?

Thanks

-Mat
[Magisk] Nkaskaj:
Can someone notice me pleaseee? I tried to install your Magisk, but I am still getting Error: 1 (http://pastebin.com/UimEcwM4) Using TWRP 3.0.2-0, Stock Rom, Un-rooted, SM-G361F. Do you know how to help me?
[Magisk] JudgeDread11:
Works flawless for me on Zenfone 2 laser (Z00ED)
[Magisk] hokey10:
anyone try sideloading pogo back to 0.35.0? any drawbacks to doing this? does it show up in installed apps in google play afterwards?
[Magisk] Deep Diver:
Samsung Galaxy A5 SM-A500F, Android 5.0.1 stock + TWRP

All works fine (Magisk v6 + phh superuser), Pokemon Go works good, but Camera doesn't work.

Tried selinux mode changer - not help.

How can i fix this?
[Magisk] desztan:
I've been using 0.35 to play, din update at all.
[Magisk] Äptiva:
Pretty much. Can you post logs?
[Magisk] rollerce:
I've completely wiped my phone, including external storage using nexus root toolkit. Rather than going back to CM 13, I've installed Stock 7.0, magisk, PhhSU, Viper and systemless exposed. Currently just waiting for everything to install, will update soon.
[Magisk] Äptiva:
Side loading actually breaks updates as it's detached from play store that way do it can b be a double edged sword
[Magisk] lss1977:
Bad news my compuer has gone of will need new psu and i hope its just that.

Psu went off with a loud popping sound its a evga g2 650w.
[Magisk] RandomPooka:
Pretty sure that's the desired result. Remain at the version of an app just before a certain "feature" was implemented. Aren't there several apps floating around out there that have a lot of users who intentionally sit on an old version? File managers and photo galleries that are the last release before the sale of the app to another company both come to mind.
[Magisk] Äptiva:
Yep. I did it with Winamp back in the day. I just wanted to point out that they would have to uninstall and reinstall manually instead of just updating or use TiBu to reattach it to market
[Magisk] arsenal3010:
Hi Äptiva. Could you please help me regarding flashing Magisk

The log is attached. Thanks a ton.
[Magisk] Äptiva:
- Mounting /system(ro), /cache, /data
! Failed: /system could not be mounted!

What device is this?

While recovery is running use adb for this:

adb shell mount -o remount,rw /system
[Magisk] mr._.nobody:
V16.3...the screenshot attached is taken after disabling navigation bar using xposed edge(module of xposed)

Still I'd like to know why I'm unable to disable them through magisk
[Magisk] Didgeridoohan:
And if you now run:

getprop | grep mainkeys

What happens?
[Magisk] mr._.nobody:
Ss attached
[Magisk] GryphonBR:
Meaning I'm actually posting in the right place? Cos honestly I'd love to provide any info that could be helpful in sorting out the issue I mentioned (no network connectivity - WiFi or cellular - upon installation of 16.7.1).
[Magisk] Didgeridoohan:
Magisk v16.3 still has the debug logs. Could you post that one as well (it's found in /data/adb).

And could you run the same resetprop command as above, but add the -v flag to it:

su -c resetprop -v qemu.hw.mainkeys 1

Did you say you've seen this behavior since Magisk v16.0? Did the module work on earlier releases?
[Magisk] mr._.nobody:
I don't know man,i first used 16.0 then flashed all the other beta ones(16.7,16.7,16.3) also I've tried these 2 modules for the very first time so i can't say if they used to work on the earlier versions
[Magisk] andrew2432:
You could follow the instructions to grab a logcat, not the magisk log. This might help the guys looking to help you specifically. Just for fun are you on 7+? I lose service/data and have to reset my network settings ehhhh once or twice a day sometimes? Annoying but fixes connectivity issues. Have you tried the stable version?
[Magisk] CallMeJohann:
Sometimes safety check fails and hidde root is unavailable

I'm using Magisk 16.6 (Manager: 5.8.3) on an OnePlus 6 with the newest Oxygen OS (I think it is 5.1.9). Normally it works great, but sometimes I'm not able to get positive results on performing the safety check. If this happens and I'm looking into the hide list, there is NO entry checked (I set every app, except 5 or 6 like Greenify, Titanium, Root Explorer,... to hide root to it). Is this a known bug? Or am I able to get rid of it by doing something? If I reboot the phone, everything works again as expected, but this can not be the all-day solution. The big problem is, that my phone would get locked from the provider of my banking app, if I start the app and it detects root or the failed safety check. So if I do not recognize that this problem persists before I open the banking app, I have to request for new activation code a.s.o...

Note: I rooted the phone with Magisk without flashing. I booted (not flashed) into TWRP to install Magisk. So everything is kind of "OEM". I did not install any modules, except YouTube vanced. If you need more informations, please tell me :)

BTW: I had to unlock the bootloader (OOS -> enable unlock + fastboot oem unlock) to install Magisk. Can I lock the bootloader now (with Magisk installed) or will this end up in weird bricks or something? I'm asking, because of this unlocked bootloader I'm not able to use some banking / pay apps...

Hope the solution was not posted anywhere. If so, I'm sorry, I didn't find something :-/
[Magisk] jcmm11:
Just 2 points.

First of all you don't want to hide root from almost everything, you should only hide it from those apps that really need that functionality. There's a lot of overhead involved in hiding apps, and having too many apps selected in Magisk Hide may well be the cause (or at least contributing) to your problems.

Second - you really don't want to lock the bootloader on a rooted phone. Try a custom kernel instead. Most (if not all) have a patch that will prevent the unlocked bootloader from being detected.

Beyond that if you need help you'll need to provide logs. Without logs the chances of resolving problems are slim.
[Magisk] CallMeJohann:
Thanks a lot. I didn't mean this would be a problem. So, is there a way to really find out, which one _need_ that functionality? Banking apps, sure. But what about Googles Playstore a.s.o.? Is it "only" try and error?

Ehm, ok... I decided to use Magisk because I (thought) I have NOT to flash a custom rom with it. Is there no way to get rid of this problem instead of flashing a cr? :confused:

Which logs do you/they need? If it happens again, I can provide some Logcat entries (currently not, because of the reboot there's nothing helpful..). Is it enough to filter the log by the word "Magisk" (or xy)? I'm sorry, but I'm only a few minutes member of this group and not really firm with it.
[Magisk] Didgeridoohan:
You don't need to add anything for SafetyNet to pass, that's taken care of by default. After that you only have to add the apps that actually look for root and don't start/work if they detect it. Like your banking app.

Magisk does take care of hiding an unlocked bootloader. This doesn't work on your device? Do you have a way of testing this?

In any case, do

not

lock your bootloader if you have modified your device. It's often a recipe for disaster.

Grabbing a logcat when the issue appears might be the best. Might mean you have to leave the logcat running in the background until you discover that the issue has appeared and then save the log (that might be huge). The Magisk log might also show something (but probably not). Check here for some details on how to save logs:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] jcmm11:
Along with what Didgeridoohan said note that I did NOT say custom ROM. I said custom kernel (which is much simpler, and easy to revert).
[Magisk] CallMeJohann:
Thanks for clearing :)

A app called "Pay direkt" (some kind of banking/financial) says:

Potentiell unsicheres Gerät (potential unsafe device) "Auf diesem Gerät sind Ihre Daten leider nicht vor unberechtigtem Zugriff geschützt....." (On this device your data is not safe from untrusted access)

"Hide root" is active for this app, and usb debugging is off - so it can only be about the unlocked bootloader. If I start the device, I get an message like this one (black screen, caution, ....). And since the OOS update (first seen with 5.1.9 - 5.1.8 there was none) I get nearly the same message right at/before entering the pin...

Ok... I will not do it. :D But I hope to find a way to hide the unlocked bootloader from apps...
[Magisk] Didgeridoohan:
Is it this one: https://play.google.com/store/apps/details?id=com.gimb.paydirekt.app

I played around with it a little, and it's just looking for root and the Magisk Manager package name (com.topjohnwu.magisk). As soon as I hid the Magisk Manager (there's an option in the settings) it didn't complain anymore about a "potentially unsafe device" at start anymore. Try that...
[Magisk] CallMeJohann:
Ah, ok. I misread that. Thx

---------- Post added at 21:15 ---------- Previous post was at 21:08 ----------

Yes, it is this one. Ok, great to know, I'll repack the Manager. Could there be a problem doing this?

Meanwhile I found out, that the boot message is about dm-verity, I think. This can not be enabled in Magisk. Maybe this causes that I have to enter the pin twice on reboot and the android system warning about an "internal error'...
[Magisk] mit900:
Invalid update channel

I have "Invalid update channel" on my mobile data. My operator is YOTA. With VPN all good. It's normally?
[Magisk] Didgeridoohan:
No, there shouldn't be any kind of problem. There used to be a slight risk that malware could hijack the com.topjohnwu.magisk package name, but from Magisk v16.6 that's no longer an issue.

Do you mean this:

That's taken from the troubleshooting section of the release thread OP.

You seem new (:p), so here's another link for you, for future reference. It's a collection of troubleshooting tips and tricks that I've gathered. A lot of the most common issues are covered there:

https://www.didgeridoohan.com/magisk
[Magisk] CallMeJohann:
Yes, thats the message. Thank you so much, I'll read everything right now :)

One (maybe) last question: I think I will not change something on the vendor image. Is this needed to be done by some very urgent magisk modules or so? If not, I will do the mentioned procedure to get rid of this annoying message...
[Magisk] Didgeridoohan:
If you don't know for sure that you're going to mess with the vendor partition, I'd say you are safe getting rid of the message. You can always change it later if needs be.
[Magisk] CallMeJohann:
Ok... The message is gone now. Great! I repacked MM, restored Images within MM, reinstalled Magisk, rebooted. Done :)

But: The Paydirekt app now starts, but crashes after entering the pin :confused:

07-23 21:53:25.819 E/InputDispatcher(960): channel '1ee3ca5 com.gimb.paydirekt.app/com.gimb.paydirekt.app.authentication.activity.AppPinAuthenticationActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
[Magisk] Didgeridoohan:
That kind of stuff is not really my area... A quick web search suggests it might be a memory issue with the app. Restarting your device, or force stopping and clearing data for the app might fix it.
[Magisk] CallMeJohann:
Ok, thank you :) I did that all, even reinstalled it. Before I reinstalled the images, it worked like a charm. I could fix this by your suggestion: deleted data and rebooted. Now you are my personal hero :D Thank you. I wonder why reinstalling this app not had the same effect than deleting data, but ok... It works :fingers-crossed:

BTW: I came across your link in your signature 'bout "MagiskHide Props Config". Very interesting! I read a bit and I wonder if it is possible to get the SafetyCheck back after repacking MM? It now alerts, that SC is not possible after repacking, cause of changes in Googles PlayStore... Is there a way to "re-enable" it? At the articles for troubleshooting, your great guide and the MagiskHide Props article I weren't able to find a hint...

EDIT: Ok, sorry, I found the article: https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet

Please ignore it :)
[Magisk] reinaldistic:
Bump
[Magisk] Pkt_Lnt:
Proved logs if you want help, no logs, no way to help you, we don't have your phone and can not see inside with if you don't upload a logcat.

https://www.didgeridoohan.com/magisk/MagiskHideHelp