yashsingh1/xdaforums huggingface dataset:
[Magisk] hofopds:
I collected a logcat of what ocurred when I clicked the 'Root Mount Toggle' button on PureNexus on a 6P (in this case I did it three times!). It sounds like an issue common to PureNexus, but maybe this will help us figure out what is going on.

Logcat link: http://pastebin.com/vsNFgT17

Each time I click "Root Mount Toggle" I see the following block of messages in the log:

08-04 18:16:02.981 20179 20179 D su : starting daemon client 10140 10140
08-04 18:16:02.992 20181 20181 D su : connecting client 20178
08-04 18:16:03.004 20183 20183 D su : remote pid: 20178
08-04 18:16:03.014 629 2789 D AudioFlinger: mixer(0xf3e80000) throttle end: throttle time(12)
08-04 18:16:03.015 20184 20184 D su : remote pts_slave:
08-04 18:16:03.027 20185 20185 D su : remote uid: 10140
08-04 18:16:03.038 20186 20186 D su : remote req pid: 19707
08-04 18:16:03.049 20187 20187 D su : remote args: 1
08-04 18:16:03.062 20191 20191 D su : su invoked.
08-04 18:16:03.062 20189 20189 D su : waiting for child exit
08-04 18:16:03.073 20192 20192 W su : hacks: Testing (com.keramidas.TitaniumBackup:0:10069)
08-04 18:16:03.087 20193 20193 D su : db allowed
08-04 18:16:03.098 20194 20194 W su : hacks: Testing (com.keramidas.TitaniumBackup:10140), 44451
08-04 18:16:03.110 20197 20197 D su : 10140 /magisk/phh/su executing 0 /system/bin/sh using binary /system/bin/sh : sh
08-04 18:16:03.161 20201 20201 D su : sending code
08-04 18:16:03.170 20202 20202 D su : child exited
08-04 18:16:03.176 20203 20203 D su : client exited 0
08-04 18:16:03.413 20195 20195 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
08-04 18:16:03.418 20195 20195 D AndroidRuntime: CheckJNI is OFF

Interesting that there is a message about TitaniumBackup each time. That is the one definitely-root app that I use on a day-to-day basis. In this case though I made sure I stopped it from running by both holding back to kill it and swiping it away from the task browser.

As an additional test, I uninstalled TitaniumBackup just in case it had some background elevated process running but go the same result. I'm guessing this is actually probably phh-su remembering that I had whitelisted TitaniumBackup and was checking to see if Magisk Manager (elevating to un-su) was that?

Hope this helps!
[Magisk] mykenyc:
Doesn't work as in you attempted to make a purchase or doesn't work as in you tried adding or editing a card?
[Magisk] MrBrady:
Wanted to report the same issue as others on Pure Nexus, but my device is a Nexus 6 (Shamu). Root is working fine. It appears Xposed is working fine (haven't added any modules). But when I try to unmount root, nothing happens. The toggle simply toggles back to enabled automatically.
[Magisk] mobileman88:
The best way to clean up is to flash the stock boot image
[Magisk] N00dle:
I never used phh super user before until now and AdAway works just fine for me. Once I flashed everything properly it's working fine with Android Pay too

---------- Post added at 07:18 PM ---------- Previous post was at 07:15 PM ----------

Is anyone running N also able to use Xposed even testing? Just curious I'm assuming not based on a few comments
[Magisk] EpicFroze:
Will this work with deoodexed mod?
[Magisk] harpin14789:
Which zip did you flash, will the magisk phh zip encrypt your device. Because on Phh's thread there is a config file where I can specify noencrypt while on magisk phh zip there is no config file.
[Magisk] xd4d3v:
Great work, however, I'm having some issues with Bootloop on huawei Ascend Mate 7, on stock MM rom.

Just flashing Magisk causes a bootloop.

How can I help troubleshoot this?
[Magisk] KaMyKaSii:
It seems that guys did not understand that systemless was not made just for AP work, but to not modify /system, since virtually all manufacturers have adopted block-level otas with the arrival of Marshmallow, which do not install if /system has been mounted as read-write, even if no file has been modified. And a feature request is that the power of Magisk is not only used by developers, but also for ordinary users. Something interesting would be to add on app a mount function for any file (that would be copied to "/magisk/*/") in the system, as download a bootanimation and mount it in /system/media/" or files that do not exist on /system, which in this case must also be configured the folder/file destination
[Magisk] mmoogle:
I already had a card that worked until Google updated the Safety Net checks last week. I get the "unroot your device" message when I go to pay. Nexus 5x, stock, with open source SU and systemless Xposed installed. Went into the Magisk control panel and disabled root before trying to make a payment.
[Magisk] Fedroid:
100% success after Ota because everything is on data partition and Ota modifies system.

Steps to follow after installation are

1. Flash custom recovery

2. Flash custom kernel (optionally)

3. Flash magisk

4. Flash shh su

5. Reboot (Maybe first boot could take long up to 30 mins because of xposed)

You will see you have everything as it was, xposed installed and configured with your mods, viper4android, etc...

It is amazing!
[Magisk] Captain_Throwback:
You only need to flash the Magisk zip - no need to flash Superuser again.
[Magisk] cawpin:
I've encountered a new error in the last couple of weeks. Before Magisk was updated, I'd get the "OS cannot be verified" error even after switching off root. Now, I'm getting an error saying something like "card cannot be used with Android Pay." I haven't changed anything, have been using this card, Amex, since Wallet was out and Amex is good for Android Pay. I didn't take a screenshot of the error, unfortunately. Any ideas? Should I try removing and re-adding the card?
[Magisk] Nomelas:
Use chainfire's FlashFire app (skip the root option) and you will also preserve your recovery (maybe kernel too?)

It would be really epic to see a collaborative effort between [MENTION=631273]Chainfire[/MENTION] and [MENTION=4470081]topjohnwu[/MENTION] here to get magisk supported with FlashFire!
[Magisk] Fedroid:
As I own a Huawei I prefer not to use FlashFire :D

By the way, good advice
[Magisk] fmotta:
I really think Magisk is magic!

And I can't wait to be able to use it on my Note 7 SM-N930F with stock kernel.

Keep up the great job and thanks!

Inviato dal mio SM-N930F utilizzando Tapatalk
[Magisk] JudgeDread11:
It's modifying the system systemless.
[Magisk] grep_i:
You know you need to be rooted for flashfire to work it's magic ?

So the flashfire way won't fly without rooting first.

Why not, is flashfire not working with Huawei devices than, never heard about it.
[Magisk] soder:
Also, i get this screen when rooted with phh's root.

/Söder
[Magisk] JudgeDread11:
Set selinux to permissive in magisk manager and it should work.
[Magisk] soder:
Aha. Nice.

BTW, what file in a full ROM .zip , signed, is the recovery? I guess I need that file to first restore stock recovery when a OTA is going to be flashed.

/Söder
[Magisk] JudgeDread11:
Should be boot.img
[Magisk] soder:
OK. Next question. Is FlashFire like a que list? That I first tell it to flash stock recovery, then the OTA zip, then TWRP, (then Magisk)?

/Söder
[Magisk] JudgeDread11:
Yes should be.

I haven't used FlashFire much so no guarantees. I don't see the big advantage over just flashing in recovery.
[Magisk] hgoldner:
Time out, [MENTION=2438781]soder[/MENTION] and [MENTION=5993745]JudgeDread11[/MENTION], recovery is typically "recovery.img", not "boot.img". You better know where that image file is. You put the wrong image file in the wrong place you own an expensive brick.
[Magisk] CrazyCypher:
Hy guys, can anyone explain to me when do you use cache and when magisk directory? I know that they both can replace file so how do we know which one to use?

I wanted to apply pnp script and I thought that I have to auto_mount and put it in cache directory, that way it will be loaded before phone starts... but it didnt work, it worked and successfully mounted the file when I put it in magisk folder and auto_mount...

So how do we know for which action do we use which path?

Thank you, I appreciate it.
[Magisk] Captain_Throwback:
You almost never need to use Cache Mode. Only very specific mods, such as replacing the boot animation or replacing read-only props in build.prop require the use of Cache Mode. All other mods should be done using the standard Magic Mount.
[Magisk] dr_hard9999:
Anyone guys can explain in steps how to install the systemless xtrememusic
[Magisk] jemyzhang:
[MENTION=4470081]topjohnwu[/MENTION]

I think it is a good idea if the gapp flash over magisk can be support.:D

Or I can change the gapp package to support magisk manually?!:laugh:
[Magisk] kerbiii:
I flash the viper4android but I can't find the app, how can I access it?
[Magisk] phillibl:
If you use SuperSu then you don't use Magisk
[Magisk] teddy0209:
Actually not true...

---------- Post added at 05:24 AM ---------- Previous post was at 05:22 AM ----------

About supersu, just update it... If the latest will work with magisk, you just test it and report... Though it is advisable to use magisksu so you can benefit from using magiskhide... ???
[Magisk] dahawthorne:
If you're using SuperSU then why are you dabbling with Magisk, and why ask about updating SuperSU in a Magisk thread? And surely you've updated apps from the Play Store before - why would SuperSU be any different?

Edit: that comes acoss as a bit sharp - not intended. Magisk is itself a root solution for most devices and doesn't need SuperSU, as you probably know. If you decide on Magisk, uninstall SuperSU (internal function which will restore your original boot image, or Osmosis' Unsu.zip, which won't), restore a clean boot image - you can then either flash Magisk in TWRP and then install Manager, or install Manager and use its update function to install Magisk.

From what I read in the SuperSU thread, the new version 2.82 works, though if you have an Experia you might want to read the thread for yourself.

---------- Post added at 06:16 ---------- Previous post was at 06:13 ----------

I had the same bad moment once, though I was never near collapsing... :)

Have you ticked Settings/MagiskHide?
[Magisk] Didgeridoohan:
That just means that Magisk Hide can't set the SELinux pseudo-enforce mode and instead uses a workaround for Samsung custom ROMs.

About the app, it's probable that it checks for more than just root. So you're gonna have to figure out what. It could be certain prop values, it could be using other processes/apps on your device to do it, it could be using it's own detection methods (that you're probably not gonna be able to fool), etc. Check my troubleshooting thread for some possible tips.

Try flashing through recovery instead.

You can't take a regular OTA update with a modified device. You'd have to restore the stock recovery and boot image first. It's possible to only boot the recovery, so if you use it that way you'd only have to restore the boot image. After that you could update through the regular OTA and then just reflash Magisk and you'd be back in business. All your Magisk Modules would be intact since they're stored in the Magisk image on /data. This is also true if you use any other way to update that doesn't wipe /data.

It doesn't need SuperSU, but it can use it... [MENTION=4470081]topjohnwu[/MENTION] has given us a choice there, for those that want to stay with SuperSU but get the systemless features of Magisk (minus Magisk Hide).
[Magisk] Imp_GL:
u0_a376@kingdom_row:/ $ su
root@kingdom_row:/ # sh /magisk/.core/magiskhide/enable
MagiskHide: Moving and re-linking /sbin binaries
chcon:* Could not label u:object_r:system_file:s0 with -h:* No such file or directory
MagiskHide: Removing dangerous read-only system props
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
root@kingdom_row:/ #

chcon:* Could not label u:object_r:system_file:s0 with -h:* No such file or directory - problem? Android 5.0.2, ROM and KERNEL - original.
[Magisk] marcolino7:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

flashing downloaded zip from recovery, i got an error:

Invalid zip file format!

I tried to open ZIP file with WinRar and I can open it and Repack, but same issues.

Perhaps I miss something, but I cannot understand what.

Regards

marco
[Magisk] Didgeridoohan:
I don't think Magisk Hide is going to be compatible with your device unless you update the ROM, or at least the kernel.

Where are you getting the zip from? Open up the zip and see if you have all the module files in the root of the zip. If there's a folder with all the files, you'll need to rezip with the files in the root. If you continue having issues, upload the zip file...
[Magisk] Imp_GL:
The firmware is the last and the manufacturer no longer produces.

13 version can help? At me any of 13 does not give root and does not conduct logs.
[Magisk] Didgeridoohan:
I guess it's time to go down the custom ROM route then: https://xdaforums.com/k920/development
[Magisk] Imp_GL:
There not all works. Andriod pay is not worth it.
[Magisk] marcolino7:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

I download the zip directly from Magisk Manager->Downloads

It download zip from repository and then fail to install, from Magisk Manager and from recovery.

Attached one zip, but issue is with all of them I tried.

Marco
[Magisk] ahse0w:
i just converted from SuperSU to Magisk on my Nexus 6P. Luckily for me the process was quite smooth and easy.

In preparation for the incoming OTA, can I know how would I update OTAs now? I came from using Flashfire and SuperSU so the entire OTA process was quite easy.

Can I still use Flashfire even if I am using MagiskSU? Would it be just not letting Flashfire flash SuperSU after updating and manually flashing Magisk through TWRP after updating the OTA?
[Magisk] Didgeridoohan:
Yup... It's exactly the issue I was talking about. If you downloaded that zip from the Magisk Manager there's something wrong with your setup. It's supposed to repack the file in the way I described earlier.

You could try uninstalling the Manager and reinstalling it to see if that helps. It's also possible it'll work in the next update so you could also try an unofficial beta snapshot (you'll need to update both Magisk and the Manager).
[Magisk] D-m-x:
Just a basic Question for most I believe. I want to try Magisk over SuperSU on my Shield Tablet, but I'm asking myself what i need to do about already installed System Mods like Arise etc.

Is it recommended/necessary to reflash the System Image to get it working properly? Otherwise I would just flash unzu.zip and install Magisk like it should be installed.
[Magisk] Didgeridoohan:
Flashfire should work with MagiskSU and you could add the Magisk zip to the flash que, after the OTA file. I've never tried it though, so someone else'll have to confirm if that's correct.

Unless you care about those system mods being systemless you can leave them as is. If you wan't to switch to using them systemlessly you'll most likely need to flash your system image before.
[Magisk] marcolino7:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

I unpacked ZIP and repacked having all files in the root directory, now I'm able to flash VIPER4Android from recovery.

I can see VIPER module in Modules List in Magisk Manager and VIPER is enabled, but I cannot see app installed, and there is not VIPER icon in app drawer.

Marco
[Magisk] Didgeridoohan:
Go back to the Downloads section in the Magisk Manager. Click the V4A module (not the download arrow).
[Magisk] marcolino7:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

here is a screenshoot of what i got.

Nothing happen. Screenshoot is in Italian, let me know if you need translation

Marco
[Magisk] Didgeridoohan:
You forgot the screenshot...

What you should have seen is a link to the V4A apk. You'll need to download it and install it manually.
[Magisk] marcolino7:
Hi,

fixed VIPER, I have issue with XPosed. I installed Downloaded and repacked zip from recovery and installed Xposed apk.

I got XPosed framework not installed and after installed XPosed Framework I got SafetyNet error: CTS profile does not match

Marco
[Magisk] DodoGTA:
Disable or uninstall Xposed if you want to pass SafetyNet
[Magisk] marcolino7:
Hi,

thanks for answer. At this point, Xposed does not work, app told me that framework is not installed, but I can see framework installed into Magisk Manager.

Thenk what happen if Magisk do not pass SafetyNet ?

Thanks
[Magisk] DodoGTA:
https://android.gadgethacks.com/how...le-actually-cares-about-android-root-0177638/
[Magisk] Didgeridoohan:
Do you have the correct app? Check the Xposed support thread: https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268
[Magisk] DICKO1984:
Hello ! I am on xiaomi.eu rom the latest update 7.5.25 on mi 5 and i have a root drop with magisk v12. After flash the zip and install the zip pro to hide root for safetenynet it's show that anything is OK. But later i have lost root ! Thanks for your help!
[Magisk] marcolino7:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

thanks for precious help.

Marco

---------- Post added at 04:24 PM ---------- Previous post was at 04:08 PM ----------

Hi,

I tried to install app to watch Italian Pay TV, Sky Go. This app check for root. I checked app into Magisk Hide, but SkyGo always detect root.

All 3 test on Magisk Manager are green.

I miss something?

Thanks
[Magisk] Imp_GL:
I update kernel https://xdaforums.com/k920/development/kernel-custom-kernel-lenovo-vibe-z2-pro-t3162383

CTS mismatch.

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Running post-fs-data.d
* Loading core props
* Preparing modules
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
* Stage 3: Mount module items
* Stage 4: Execute module scripts
* Stage 5: Mount mirrored items back to dummy
** Magisk late_start service mode running...
* Enabling systemless hosts file support
* Enabling BusyBox
* Linking binaries to /sbin
* Starting MagiskSU
* Running service.d
* Starting MagiskHide
MagiskHide: Moving and re-linking /sbin binaries
MagiskHide: Removing dangerous read-only system props
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.debuggable'='0'
Existing property: 'ro.debuggable'='1'
Recheck property: 'ro.debuggable'='0'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.secure'='1'
Existing property: 'ro.secure'='0'
Recheck property: 'ro.secure'='1'
Done!
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=�
MagiskHide: com.google.android.gms.unstable(PID=4634 ns=[0 4634 10009 com.google.android.gms.unstable service com.google.android.gms/.droidguard.DroidGuardService]
)
[Magisk] xsycox:
What to do with the file, mate? I renamed it to .apk and tried to install it, but it tells me "parsing error".
[Magisk] Didgeridoohan:
Some apps look for more than just root. And some apps just can't be fooled... I've collected some tips to try here:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

That kernel is based on Linux kernel 3.4.0 (too old). Unless they've added support for setns and mount namespace it's not going to work...

It's a Magisk module, you install it through the Magisk Manager or flash it in TWRP.
[Magisk] callumbr1:
Is this compatible with galaxy S8 7.0? Thanks
[Magisk] MultiKoopa:
I also would like to know about this. I switched from SuperSU to MagiskSU on my Nexus 6P, too. I'm guessing for the same reason a bunch of other people did: SuperSU app update somehow removed root functionality. Which I didn't even think was possible.
[Magisk] Didgeridoohan:
You know... It's just a matter of making a backup and go for it. If it works, it works. If it doesn't you have the backup.

Luckily for you guys I have a very inquisitive nature and just had to give it a try myself. :D Spoiler: It works fine.

Added a ROM update, gapps update, custom kernel and last the Magisk zip to the flash cue in Flashfire on my N6 with MagiskSU. No issues.
[Magisk] MultiKoopa:
Sounds good, thanks for testing! Looking forward to trying it next week with the June security patch.
[Magisk] Artim_96:
As long as you are able to flash stuff from TWRP it should, but Samsung is always a problem, do just try it. If it's not working try v13 snapshots (if the latest is not working try from 041517, is more stable for most). Of even that isn't working fine back with logs, then future support is at least possible
[Magisk] sirs2k:
Hey guys, for some reason tasker is not prompting for superuser permission (popup), and I cant find a way to add an app manually in magisk manager

Any ideas?
[Magisk] RandomPooka:
Look at Didgeridoo's signature for the module you need
[Magisk] ahse0w:
Thanks for trying it out! :good:
[Magisk] xsycox:
Thanks a lot, mate.
[Magisk] teddy0209:
That's a known issue (with most devices running MIUI)... Clear the magisk managers data, remove magisk and reinstall... Tip (keep modules to minimum)... I only use one (props module)...
[Magisk] xsycox:
Had the same issue. Turned off Busybox in Magisk and now it is gone.
[Magisk] sirs2k:
Thanks. I flashed it, but I still can't see tasker under magisk superuser and tasker still can't kill apps using root.

Still no prompt either
[Magisk] dahawthorne:
I'm not sure which task you're setting in Tasker which requires root, but have you tried setting one which you know for sure will provoke a root request, such as switching on GPS?
[Magisk] Didgeridoohan:
Are your sure the module did it's thing? Can you see in build.prop if it's added the comment line in the beginning of the file? What does it show in your Magisk log?
[Magisk] teddy0209:
How did you turned off busybox in magisk if the manager has no root access?
[Magisk] sirs2k:
I don't know what you mean by looking at the build.prop for the comment in the beginning of the file

Lookin at magisk log, it looks like it did do its thing:

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

* Running post-fs-data.d

post-fs-data.d: /magisk/.core/post-fs-data.d/buildprop_edit

* Loading core props

* Preparing modules

Analyzing module: /magisk/TaskerRootBuildProp

Replace: /system/build.prop

Analyzing module: /magisk/busybox-ndk

But still isn't functioning
[Magisk] marcolino7:
Hi [MENTION=4667597]Didgeridoohan[/MENTION]

Here is debug log for Magisk Hide. I try to restart Daemon but as I understand from log, Hide is not able to operate:

* Starting MagiskHide
MagiskHide: Moving and re-linking /sbin binaries
MagiskHide: Removing dangerous read-only system props
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.boot.warranty_bit'='0'
Existing property: 'ro.boot.warranty_bit'='1'
Recheck property: 'ro.boot.warranty_bit'='0'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.warranty_bit'='0'
Existing property: 'ro.warranty_bit'='1'
Recheck property: 'ro.warranty_bit'='0'
Done!
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.secure'='1'
Existing property: 'ro.secure'='0'
Recheck property: 'ro.secure'='1'
Done!
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Killing it.sky.go
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
MagiskHide: [it.sky.go]
Zygote(0) ns=mnt:[4026544621]
MagiskHide: it.sky.go(PID=9006 ns=mnt:[4026544752])
MagiskHide: Permissive detected
MagiskHide: Unable to set to enforce, hide the state
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/system/lib/soundfx)
MagiskHide: Unmounted (/system/priv-app)
MagiskHide: Unmounted (/magisk)
MagiskHide: Unmounted (/system/etc/hosts)
MagiskHide: Unmounted (/system/etc/audio_effects.conf)