yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Was whoever provided that patched boot image successful in getting things working?

I'd try installing again, by patching the boot image with the Manager yourself. Instructions are found in the release thread.

Some Moto devices have a history of using a flawed implementation of the f2fs file system. This might also cause issues where modules don't install and MagiskHide only works in Core Only Mode (found in the Manager settings).

Edit: oh yeah. If you're gonna paste the log in the post, at least use hide tags.

Why no log (magisk.log and magisk_debug.log at least)?
[Magisk] nikhil_1991:
Can anyone please tell whether we can uninstall magisk/unroot with the UNINSTALL button in Magisk manager.

And there are 2 option when I click on UNINSTALL button in the MagiskManager app

1.Restore stock

2.complete uninstall

What's the difference between the two ?
[Magisk] Sirshark10:
I have a Pixel XL with 7.1 installed as of right now and i cannot get Magisk working. IS there something special i need to do?
[Magisk] caeter:
I don't have a file like that in the lib folder
[Magisk] Shtiff1:
Weird!, I don't remember posting a quote like that. Maybe [MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] Didgeridoohan:
I remember it... Those are indeed my words, but you posted them. IIRC you couldn't quite get linking to another post working in the xda app. :D

[MENTION=4126521]caeter[/MENTION] If you're having issues with Netflix you're probably better off doing a web search for your issue...

Unless it's the issue with it not installing from or not showing up in the Play store. In that case there are troubleshooting tips for that here:

https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417
[Magisk] Shtiff1:
Lol, thanks
[Magisk] lzanoni:
Hello,

I'm using Magisk 14.0 on Marshmallow (Nvidia Shield tablet).

Some apk refuse to install: from the logcat, the vold is unable to create the secure container (asec) on the SD card.

When I enable the SELinux Permissive script, it then can install the apk (creating the .asec in /mnt/secure/asec I think), but then I don't pass safetynet.

Apparently, the vold (or another component related to the ASEC thing) doesn't have the correct contexts, I get access denied in logcat.

0-09 14:26:11.505 862 898 D VoldConnector: SND -> {10 asec create smdl1636995937.tmp 98 ext4 [scrubbed] 10005 1}
10-09 14:26:11.510 182 210 E Vold : Error creating imagefile (Permission denied)
10-09 14:26:11.510 182 210 E Vold : ASEC image file creation failed (Permission denied)
10-09 14:26:11.510 182 210 W Vold : Returning OperationFailed - no handler for errno 13
10-09 14:26:11.510 862 1714 D VoldConnector: RCV <- {400 10 asec operation failed (Permission denied)}
10-09 14:26:11.513 7320 7331 E PackageHelper: Failed to create secure container smdl1636995937.tmp

Anyone experienced it also ?

Laurent
[Magisk] Simonex16:
Thanks !

So,i only have to update magisk with a version => 13.3?With recovery flash?And of topjohnwu?
[Magisk] Rush94:
The output is same as 14.0

fopen: /magisk/.core/hidelist failed with 2: No such file or directory

I had same issue every time can you tell me what can I do

I guess the magisk folder is read-only I have to set it to rw

You tell me the steps I will execute it manually
[Magisk] Didgeridoohan:
You misunderstood... I wanted to know for sure if your Magisk image is mounted ro. That's why I wanted you to run the mount command in terminal:

mount | grep " /magisk "
[Magisk] The_Juus:
I think I use an other rom....now xposed is on android 7.x.x and I only go back from Android 7 to android 6 super stock to use xposed modules like kmod^^ but thanks to you....it's too much work to fix without knowledge.... and my bad English would not make it better^^
[Magisk] image45:
https://play.google.com/store/apps/details?id=com.microsoft.windowsintune.companyportal

Magisk hide does not work on the above app. Any other models or possible solutions please?
[Magisk] Rom:
Hello,

From around 1 or 2 days, i get an install error toast message when i i try to install any module in download section from Magisk Manager (last version), there is the error:

MANAGERERROR: ProcessRepoZip: Error !

Idk why i get this message, when i try to install manually any module via document provider no error.

Tell me if a loggcat is needed.
[Magisk] bflmpsvz:
Hello, to make clear, if I already have SuperSU and Xposed installed to system, can I install Magisk along them?

I mean if it will clash with something. Thanks for clarifying.
[Magisk] nathanchance:
Uninstall SuperSU.
[Magisk] bflmpsvz:
Thanks, what will happen if I keep SuperSU and install Magisk?

Can I use SuperSU for root and Magisk only framework for modules?
[Magisk] nathanchance:
It won't let you install.
[Magisk] WeUseLord-:
Well it's fine now I found out the problem was magisk itself so I flashed the stock boot image while installing SuperSU with the flashfire app. From what I have experienced so far is nougat 7.1.1 ( moterola and sony) devices have a issue with magisk so it would be better off with SuperSU instead.

Note: compatability with sony and moterola devices running nougat need to be looked into.
[Magisk] Eng.Raman:
Hello Devs

Please, is there any magisk module or script which let me get rid of USB connection message in marshmallow and nougat?

( to enable MTP by default without the confirmation message every time when connect my phone to the pc ).

Thanks in advance.
[Magisk] Captain_Throwback:
The app? Yes.
[Magisk] Immortal Knight:
updated recently, have the same issue. will make a bug report and add boot recovery.
[Magisk] cdiamond2:
I have successfully started Good Work and reached its registration form so I hope it means Magisk with phh's SuperSu is a solution :) To full test I have no account.

And another question: should I stop background services of protected application such as Good when root is enabled in Magisk?
[Magisk] brickhayabusa:
deleted
[Magisk] topjohnwu:
The thread has been flooding with tons of posts :eek::eek:!!

I'm gonna thank Pokemon GO for more users, but blame it for cluttering this thread lol

I'm still working on the next version, which will have substantial difference in many ways how things work (the API won't be changed).

Until v7 is released, there is not much I can do to fix current issues, since the whole backend of Magisk is totally changed.

Some current issues will be fixed, and new issues might appear. So right now just be patient till I figured out everything ;)

I'll add a list of devices that is currently not working to the OP, since the reports are repeating again and again and again lol

The last is good news, it seems that [MENTION=3400685]digitalhigh[/MENTION] has finished the repo part of Magisk Manager, so the only left is for me to finish the core Magisk stuffs, and it shall be ready for a massive update!

Side note: [MENTION=3400685]digitalhigh[/MENTION] is now polishing the auto-unroot per-app feature to Magisk Manager. Depending on whether it's done, you may or may not see it in the next update.

So just be patient and stay tuned!
[Magisk] raptoro07:
Sorry for the question but search is not working on xda site today.

I Another Pokemon Go user :P looking into Magisk, one thing is not clear to me though. I'm on Nexus 6 that has been decrypted. Does installing Magisk and the associated parts re-encrypt the phone. I understand that the script changes the flag, is that just to remain decrypted and fake to the boot img or whatever? TIA
[Magisk] igoticecream:
Please help LG users with stock based ROMS

LG user with CM13 can flash the script and bump the image without problems, but stock based ones cannot boot.
[Magisk] Äptiva:
Secure boot error?
[Magisk] igoticecream:
Security boot error if you dont bump the new boot.img... After bump it, bootloader shows "fastboot mode started" and simply wont boot.
[Magisk] Äptiva:
That's a bootloader issue. Reflash your rom without Magisk and report back
[Magisk] Captain_Throwback:
Magisk will not re-encrypt anything.

Donate him a device so he can test.
[Magisk] igoticecream:
Reflashed my boot.img backup... now it boots
[Magisk] Äptiva:
What are you using to bump your boot.img?

---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------

I'd be happy to throw my own G2 under the bus for them. I can recover most anything that won't require a jtag
[Magisk] igoticecream:
With this flash script http://xdaforums.com/lg-g2/development/cbump-bump-current-boot-image-t3325186

And tested with this too http://xdaforums.com/lg-g3/general/bump-window-version-t2956829

All of them leads to fastboot mode started message after bumping an magisk image
[Magisk] Äptiva:
I used OpenBump personally as I have access to Linux. Are you using a stock kernel?
[Magisk] Konsumhaus:
Hi @ all.

My Nexus 6 runs Android N with OMP Rom (which is based directly on google open master).

Superuser by phh.

Is there a possiblity to get A.R.I.S.E. working? If yes: A desription would be great :)

If not: What Viper Version would be working?
[Magisk] Captain_Throwback:
[MENTION=4470081]topjohnwu[/MENTION]
[Magisk] topjohnwu:
Please spread this info to developers with all kinds of devices!

I'm only one man and do not own tons of different devices for all brands!

For developers, you can take a peek in my updater-script to know how to use the included boot image tools, and check whether the boot image has been unpacked/repacked correctly for your device

Currently Known Not Working Devices (v6):

Sony devices generally: Haven't investigated why it won't work, if you know any addition quirks about Sony boot image modifications, please contact me

Moto devices generally: I suspect it is something to do with dtb image not unpackable

HTC One M9 (yes, this particular device): sepolicy issues, should be fixed in v7

Older Samsung devices generally (6.0+): sepolicy issues, should be fixed in v7

Newer Samsung devices (Note 7 or maybe more): sepolicy issues + kernel issues, still investigating, should be fixed in v7

LG locked bootloader devices: Seems that you need something called "bump", I'll see what I can do

Some Asus devices: Asus seems to require some additional work to modify boot image. If you know any detail, please contact me
[Magisk] cire27rn:
No problems on my samsung S6 G920i. My PoGo works fine. Thank you
[Magisk] gk1984:
From what I've tried and read, Viper4android and ARISE don't work as magisk modules. In the meantime you can do what I've done and just install ARISE normally. It kind of defeats the purpose of magisk and Viper won't process anything unless you switch SELinux to permissive in the Magisk Manager app. I saw a couple of people were working on getting ARISE to work as a module but it's not there yet.

Also, so far,flashing ARISE hasn't interfered with magisk or anything else on my Nougatty Nexus 6. Just don't let it install drivers if it prompts you too.
[Magisk] hal2100:
No module install works - no errors, but also no modules

Hi,

whatever way I try, I cannot install any magisk modules. I tried with recovery, through downloaded zips or the repo.

The only hint I have is that the log says something about "sendfile failed", which was also reported earlier by a user in this thread. Please see the attached screenshot.

Fun fact: It was working earlier, and I remember that there was a reason not to upgrade Magisk to v14, but I forgot why.

I am running Renovate Ice on a Galaxy S8. Which versiopn would work for this? Any ideas?
[Magisk] Rom:
@Didgeridoohan

Hello :)

I have an issue with the storage permission of Magisk Manager on my Resurection Remix 7.1.2 ROM, i am arrive to spread any assumptions but idk if i must send my issue on XDA or on github.

Initially i wanted to install the last Greenify4Magisk update, so far no worries but the document provider ask me if i ganted the storage access for Magisk Manager or not, so i accept the permission request.

Magisk Manager started to download and install the update but i get an install error, in my logcat i saw that the Magisk Manager wasn't really the storage access, so it wasn't downloaded correctly the Maigks module zip so the install failed.

As the new android permissions system is really ****ty and as the extras permissions settings in documents provider can't be reseted easily i would like to know if there is a way to reset completly the permissions settings ganted ?

The craziest thing is that as Magisk Manager is setup to download by default its downloads in the internal storages, i thinked that the new system permissions was only make for apps that save files on the external storages so apparently its wrong or there is another things to consider.

Maybe an flashable zip or something like that is designed to reset theses permissions settings in the document provider app idk.
[Magisk] Eng.Raman:
Uninstall your current magisk then install the latest beta 14.2.
[Magisk] hal2100:
This did not help.

The same error with sendfile in the logs.

[EDIT] I checked the debug log. It does not state which file is not there when sendfile is executed.
[Magisk] SignetSphere:
Hello devs... just a question... is there a module that can disable speakers when a headset is plugged in? Can't seem to find any... my search skills are lacking as I've not been to XDA for a long time until Xposed for Nougat was released lol. Please help me. Thanks a lot.

(Or is it kernel based. Please do enlighten me. Still kinda new to magisk)
[Magisk] ballabdhakal:
in download section arranging the module as latest updated module will come first or some other way of arranging like in xposed manager will be great idea to impliment..
[Magisk] jbaumert:
Is this still the error with the directory "MagiskManager" not being created when installing Magisk?
[Magisk] faisalsiddiqui:
I have installed magisk via the magisk manager keeping the stock recovery and by flashing a modified boot image.

Root works perfectly, however, i am unable to install any modules. Even if I try to download a module from the downloads section I get the same error "/data/magisk isn't setup properly". Please advise what to do? Thanks
[Magisk] Wesden2017:
Lenovo bootloader TB3-710F unlock
[Magisk] Domac5:
how to update magisk to v14.0 if I already have rooted device with modified boot image?
[Magisk] rayalon:
Here as well....frustrating :crying:

OP5 with stock recovery running OOS 4.5.12.

Any solution would be appreciated.

Thanks :angel:
[Magisk] faisalsiddiqui:
Same with me OnePlus 5 4.5.12
[Magisk] thetac0:
Custom Repos

Has the topic of custom repos already been discussed?

Would be nice to add different sources for modules.
[Magisk] Anas Rahman:
Can anyone confirm if i can install an OTA update while being rooted(with magisk) or should i revert to stock first?
[Magisk] bmg002:
Ah, good thinking. I just restored the ROM (dirty flashed over top of my existing ROM) with no problems. Instead of restoring my stock boot partition, I installed magisk 14.2 fresh. I did this just in case my magisk version 12 install did something bad to the boot partition and that the upgrade was what was causing my headache.

It booted up successfully, magisk manager 5.3.5 says I am up to date. I made no other changes and checked SafetyNet which failed both basic integrity and cts profile. I then ran Root Checker to check if it could detect root and it says I am not rooted, but that it found the SU binary and 1 SU app. I then turned off magisk hide in the magisk manager options and turned it back on.. Repeated the Root Check and same thing. It still finds su in /sbin/su. If I completely remove Magisk, then it no longer sees /sbin/su.

On the plus side, the magisk manager log no longer shows "beginning of crash". I can see the su request was denied (because I denied it in root checker), but the hide_list shows com.atominvention.rootchecker which is the app I am checking root with. I am uncertain as to what to try next.

Also, with magiskhide, in magisk manager, it auto-adds some apps such as android pay and pokemon go. When I look at the logs, these apps are not showing up with a hide_list tag. Is that normal?
[Magisk] DodoGTA:
What's your device and ROM? And, do you have Xposed installed?
[Magisk] bmg002:
Device is the Xiaomi Mi 5s Plus and the Rom is the Global Stable 8.5.2.0.MBGMIED.

I have unlocked the bootloader and have installed magisk, but otherwise everything is stock.

I do not have Xposed installed.

On the plus side, reinstalling the ROM and then reinstalling Magisk allowed modules to install and work (I have Viper4Android installed now and it seems to be working). But I'd like to have magiskhide working and (if possible) safetynet passing both basic integrity (which passes if I don't install magisk) and CTS profile (which fails because my bootloader is unlocked).

EDIT - this is on android 6.0.1 on an arm64-v8a CPU if that helps any. The fingerprint is Xiaomi/natrium/natrium:6.0.1/MXB48T/V8.5.2.0.MBGMIED:user/release-keys. Don't think the fingerprint is the issue though as the problem seems to be with magiskhide on this particular phone/ROM combo. I can't seem to get it to hide root apps or busybox.

EDIT 2 - is there a safe way to downgrade to an older magisk? I'm reading that 13.3 seems to work on my device. I don't see where to get 13.3, but going to download 13.5 and 13.6 to see if that helps.

I am just wondering if I should be dirty flashing my ROM over top and then install magisk again or if there is a better way to downgrade?
[Magisk] Artim_96:
This is XDA, not Google...
[Magisk] samz2:
Facing a strange issue, SafetyNet Check fails after updating Magisk to 14.0, even though it used to pass with 13.3. Also, Google Play Store is FCing every time I try to launch it. Help [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Fif_:
Did you debloat your ROM or gapps?

I had the exact same problem, and that was because my debloating hit an app that shouldn't have been debloated...
[Magisk] andrei9270:
Hi, does anyone know how to get boot.img for s8?
[Magisk] shaggyskunk:
Not sure exactly why you are asking - But If you're Rooted & have TWRP installed on your phone - The boot.img is there - You can also use Flashify (again if you're device is rooted) to backup or Flash the boot.img ?
[Magisk] andrei9270:
I understod that is posible to root with magisk even without TWRP so I was thiking that is just needed to have the stock boot.img file. I tried to extract it from official firmware and also tried to pull it using adb, but had no luck without root.
[Magisk] silentheero:
Magisk app has been reporting that a new update is available, v14, which is the one I installed through recovery on my S8. When it does that, root breaks til I flash again. It seems to be unrooting itself? What is happening?

I apologize if that sounds stupid. I am used to supersu methods and this is the first time using Magisk.
[Magisk] Anas Rahman:
Did you remove SuperSu completely before installing magisk?
[Magisk] silentheero:
I never installed supersu on this phone, just others I had.
[Magisk] Anas Rahman:
Maybe try direct install from within the manager itself
[Magisk] silentheero:
I tried that and you choose the two options, zip or modify stock img. I chose to download zip and it doesn't do anything, no downloading, no rebooting, nada. From what I can tell, I'm doing the same thing manually that it (tries) to do automatically and fails. I haven't tried leading it to the stock img because I didn't grab it before modifying it.
[Magisk] Anas Rahman:
Try direct install
[Magisk] SignetSphere:
Anyone?
[Magisk] veez21:
Won't speakers get disabled when headset/headphones are plugged?
[Magisk] silentheero:
Weird. I only have 2 options. Download zip and patch. What's different?
[Magisk] samz2:
Nope. Facing the issue after updating Magisk to 14.0. Though I had uninstalled play services when it started crashing randomly 2 weeks back after which I restored a backup. The Magisk version then in use was 13.3 and was in use about 2-3 days back (Had no issues with Play Store). Then I updated to 14.0 after I noticed that SafetyNet check was failing, but after update, can't launch Play Store.
[Magisk] k0m3n9:
Not sure about s8.. but for my j1 ace, i just download the full firmware .tar (which flashable via Odin) & using 7zip just extract boot.img from there. Since this installation method causing magisk partially works on j1 ace running lolli 5.1.1, i have to use the 1st method of installation which is flash magis14.zip via twrp.

p/s. The patched boot.img method is just to make my device rooted & to allow installation of twrp (at least on j1 ace). S8 might get different results.
[Magisk] hal2100:
Dirty flashing my ROM did not fix it (it contains magisk).

I fixed it by:

- deleting magisk.img in /data/

- running the uninstaller through recovery (just to be sure)

- installing:

- 12.0

- 13.1 - here my module started to work again

- 13.3

- 14.0

Now my log also looks quite different, and all seems to work.
[Magisk] deepak3048:
any one help me after instal xpose magisk fail to bypass sefty net any one help me and is their any way to bypass sefty net without unindtal xposed module
[Magisk] aaargh777:
Disable xposed module. No way to bypass safety net with running xposed.
[Magisk] deepak3048:
if i desable my xposed module are work or not and how can i desable xpose in magisk where the option
[Magisk] Shished:
I have a problem with magisk manager 5.3.5.

After installing a module from the manager reboot button appears but it does not works, pressing it does nothing.

I have magisk 14.2 installed.
[Magisk] SignetSphere:
On some apps yes but not when you're playing music files then someone calls you, your speaker also rings instead of just the headphones.
[Magisk] veez21:
I don't think magisk can do that though
[Magisk] ananthakrshnan10:
How come when during the initial boot and check up, SafetyNet passes and after a while fails? without changing anythings? I have checked with Resurrection Remix OS; LineageOS; ViperOS with the 14.0 and facing the exact same issue. In some case, the SafetyNet failed with i changed the Magisk manager in app langauge? Experiencing this issue in post version 14.0. Even tried with beta versions, but not sure about their functioning. Through the forum, i found many have these similar problem. This might sound silly but i am unable to play Pokemon with my friend as the app is not authenticating SafetyNet failed acount / device. It's time for some official announcement from the dev or some solution for this. Hope [MENTION=4470081]topjohnwu[/MENTION] reads this in time.

Update 1:

"Safety Net Disaster

Those who are using Magisk for Safety Net bypass purposes must have known that Google recently updated the detection method of my Systemless Xposed. I still have no idea what Safety Net is detecting, so currently I cannot fix it on my side (also because I'm busy working on the next update). However, suhide developed by [MENTION=631273]Chainfire[/MENTION] is able to hide Xposed and worked fine.

However, only my Systemless Xposed v86.2, which is based on SuperSU's su.d, is supported using that method. v86.2 and v86.5 (latest, Magisk based) have nearly identical binaries, and the only difference is the path where the binaries are stored.

I'm still not sure what's the real issue for it not being supported, I just hope it is not done intentionally."

https://xdaforums.com/showpost.php?p=68797308&postcount=3177

Hope this is solved in the upcoming release ; )
[Magisk] Didgeridoohan:
Do you have the Universal SafetyNet fix module installed? If so it's likely the culprit. It actually replaces Magisk's built-in busybox with an incompatible one... The solution is to do a "dirty" install of Magisk (easiest is to just press "Install" in the Manager).

If you don't have it installed, try clearing data for the Manager.
[Magisk] Shished:
I actually have USNF installed. Thanks for the advice.
[Magisk] jenslody:
And remove usnf or comment out the part where it overwrites Magisk's busybox in the module's post-fs-data-sh or it overwrites the busybox again on next boot.
[Magisk] ngtung84:
Xposed framework SDK 88.0 systemless incompatible with some xposed module which work well with Xposed framework SDK 87.3 systemless
[Magisk] Didgeridoohan:
Oh... Hadn't looked more into the code... Thought it was replaced at installation.