yashsingh1/xdaforums huggingface dataset:
[Magisk] Paschfire:
You must follow, at the very least, these suggested guidelines if you're looking for Support with Magisk issues.

https://xdaforums.com/showpost.php?p=73106884&postcount=17101
[Magisk] teddy0209:
Maybe you added tbu in the hidelist...

---------- Post added at 02:35 AM ---------- Previous post was at 02:31 AM ----------

If you're talking about the store, then no need to add that on the hidelist...
[Magisk] ketwi15:
It's definitely not on enabled in hide lol
[Magisk] Koont:
Lmao. Your so right. And I told someone else the same thing. My bad. H918 (T-Mobile) V20. Weta Ron w/ weta kernel. My apologise.
[Magisk] danilo_scala:
>>>>>> View attachment recovery.log

(logcat) other

build.board: msm8994

build.bootloader: s1

build.brand: Sony

build.cpu_abi: arm64-v8a

build.cpu_abi2:

build.device: E6883

build.display: 32.4.A.0.160

build.fingerprint: Sony/E6883/E6883:7.1.1/32.4.A.0.160/3622372188:user/release-keys

build.hardware: qcom

build.host: BuildHost

build.id: 32.4.A.0.160

build.manufacturer: Sony

build.model: E6883

build.product: E6883

build.radio: unknown

build.serial: CB5A2ALWZV

build.tags: release-keys

build.time: 1495608377000

build.type: user

build.user: BuildUser

version.codename: REL

version.incremental: 3622372188

version.release: 7.1.1

version.sdk_int: 25
[Magisk] tdhite:
Indeed it is Samsung -- S6 Sprint. Others report the same with different carriers. I have to believe it is related to bind mounts, but I've not located the error, nothing in the logs shows anything out of the ordinary. Permissive appears to have nothing to do with the issue.
[Magisk] Paschfire:
Pls do not post entire logs as it clogges up the thread, use the upload feature to share logs.

Pls delete and re-upload your recovery log using a .txt file extension, thank you.
[Magisk] andmail:
Absolutly right. This is the latest beta working on my device.
[Magisk] [iop]wah:
V13.3 works perfectly on my note 3(sm-n9005) running official lineage os..this is the first time it worked without changing kernel..just installed checked safetynet passed, then clear data playstore, from uncertified to certified.
[Magisk] teddy0209:
Then something is wrong with your setup...
[Magisk] jrny99:
FYI, after almost giving up I finally got magisk to work. I uninstalled su , rebooted into recovery and flashed the zip. Not bad for a 58 yo dude. I didn't know u had to uninstall su. First.
[Magisk] matwlodek:
After installing magisk zip i do not have supersu.... So it is not possible to do what you are writing here...

It looks like magisk is not rooting lolipop. I have attached logs several times, log almost always looks the same. Installation is complete, several warnings about sepolicy, nothing more...

More details - what more can I tell? What is needed?
[Magisk] Rafa2745:
LG v20 get error 1 installing zip file flashing 13.3 I uninstalled successfully but flashing 13.3 resulted in that error and attempting to flash the uninstaller results in the same error attached are log from failed install and uninstall
[Magisk] Dominicano2:
Is anyone else having problems with random apps crashing after installing the latest Magisk, for example the Google app or Netflix? These apps only seem to crash when I install Magisk, once I uninstall it they work again. I have already tried returning to full stock by way of factory images and re flashing the rom I'm using, but end up with the same results. I'm using a Nexus 9 running My AOSP rom which is running on 7.1.2. I have attached the log below. [MENTION=4667597]Didgeridoohan[/MENTION] would you mind having a look please.

[IMG="Magisk log"]http://i.imgur.com/6fZqazR.png[/IMG]
[Magisk] ketwi15:
Apparently it's not just me it happened to. It's a problem with Samsung devices
[Magisk] Didgeridoohan:
Do not just repack an old beta and pass it off looking like it's the official installer! If you upload something like that, give proper details as to what you've done and what the file is about and give it a proper descriptive name!

With v13.3 you should not have to do the prop workaround necessary on the earlier versions. You might have other issues... But, just to make sure, run this command in terminal:

getprop | grep magisk

If it comes up with anything, you've got issues. Toggle MagiskHide off and on again and try again. It might be that it hasn't started properly.

It's all you.

I see you're using an Asus specific Magisk installation file. What has the creator changed and have you made sure to follow any specific installation instructions? Also, have you asked in the thread you got the modified zip from?

If it's a matter of the need for the boot image to be signed (I believe Asus devices need this), you could try using the normal installer and then flash this tool (the zip attached to the OP): https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606

No guarantees whatsoever... Make sure to have a proper backup tucked away before starting. I have no idea if that tool will work or if you have to generate your own keys (as described). It might be enough to just flash the zip after Magisk, but... It's up to you.

There is something about your boot image causing the installation/uninstallation to fail ("pathced by other programs"). Have you flashed a stock boot image and tried installing again?

Try disabling MagiskHide. It might be a WebView issue.

Edit: Forgot something. Please don't include screenshots in your post like that. They are the same resolution as your device's screen and that means that it'll take up more than the whole screen for anyone browsing the forum on a computer. It's quite annoying... Just attach it to the post instead.
[Magisk] Legendary Cryptid:
Okay, so as I've found out when checking the logs, Magisk Hide does not start by default when I boot up my phone, even though the switch is enabled. In other words, I have to turn it off, then back on again. How can I fix this so that it properly activates each boot up?
[Magisk] DodoGTA:
This commit will fix your issues: https://github.com/LineageOS/android_vendor_cm/commit/a3a76f5d1cc233ad8024ffdc74bb3a786e1605c3
[Magisk] jenslody:
That's how it looks like, if MagiskManager can not access any network (e.g. flight-mode turned on).
[Magisk] 13680201:
HI . Download twrp v3.1.1 .tar

Whit odin .install twrp .success. after reboot

Turn off tablet sumsung galexcy tab s sm-t805

Hold Power+volume up+home

Oh my good, show massage recovery file not find.

How solved. How install twrp?

فرستاده شده از

فرستاده شده از SM-T805ِ من با Tapatalk
[Magisk] matwlodek:
Flight mode is always off in my Phone, WiFi and sim is in phone.

But after all steps if I now flash SuperSu-v2.82-20170528234214-TEST-1.zip Magisk Manager shows Root - SuperSU v2.82 and Magisk v13.3 installed. From this point Magisk Manager sometimes FC, cannot install any modules and after several reboots root is shown as 13.3:MAGISKSU (topjohnwu)

SaftyNet is working and showing false - but there is information that if Kernel is lower then 3.8 it can be like this - so this not bother me.

I think that mine problem in my device is that MAGISKSU is not rooting my device.
[Magisk] matwlodek:
While trying to install magisk module there is error magisk is not activated
[Magisk] andmail:
I'm sorry! Could you repair the official installer thus it can be installed?

Replacing update-binary file from Magisk-v13.0(a90e8b6) solves the issue.
[Magisk] Polv89:
Solved, flashed boot.img then magisk uninstaller, now it works..

If is possible to install elemental x kernel and magisk, what are steps to install them?

Thanks

Inviato dal mio Nexus 6 utilizzando Tapatalk
[Magisk] lover:
I know xposed does not pass SN but something interesting result with this module "No Device Check"

http://repo.xposed.info/module/com.pyler.nodevicecheck:

ctcProfile:true

basicintegrity:false

I have OP3T OOS 3.5.4 MM Magisk v13.3 and Xposed v87.0 - Universal Systemless Compatibility.

Maybe there is a solution for basicintegrity or not
[Magisk] lekcin18:
please add sort on downloads tab. thanks :)
[Magisk] neolivier:
Hello all!

I 'm unable to install Magisk 13.3 on my SAMSUNG XCOVER 3 VE (SM-G389F).

I'm getting "Mounting /data/magisk.img to /magisk

! Magisk image mount failed...

Updater process ended with ERROR: 1

I:Legacy property environment disabled"

Everything is stock, I just did a full wipe / reset to factory setting.

I did flash a stock boot.img

Any idea why I'm getting an ERROR 1 ?

I already opened an issue on github, where you will be able to find my boot.img and recovery.log

Thanks :) Have a nice day
[Magisk] theandroidguy:
When I'm installing the V4A module its getting installed but after rebooting there is no v4a app in the app drawer
[Magisk] DodoGTA:
https://github.com/Magisk-Modules-Repo/ViPER4Android/blob/master/README.md
[Magisk] theandroidguy:
Deleted
[Magisk] theandroidguy:
Now what?? I've busybox installed
[Magisk] krish@3T:
Just flash the devinebeats from royal seeker

https://www.google.co.in/url?sa=t&s...sg=AFQjCNFb81qkgBi0YtQ5x5rdu6HQIncMDg&ampcf=1
[Magisk] DEVILOPS 007:
Does this need viper installed? I kind of want to try this with ainur sauron but not viper.
[Magisk] theandroidguy:
I don't want to install any soundmod, just v4a and AM3D ZERINE
[Magisk] krish@3T:
No need of anything just flash the zip and don't wipe cache and dalvics

---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------

Flashing this will get you v4a and Dolby Atmos
[Magisk] theandroidguy:
The underlying lib files will consume much space and my phone has very less space left, as far as divine is concerned I've Xtreme music which also installs the v4a driver
[Magisk] dima-82:
I raised the question in the [GUIDE] Magisk and MagiskHide installation and troubleshooting (Magisk v13.3) (post #259), but didnt get an answer :(

Maybe someone here can give me the explanation, why MagiskHide is not enabled permanently? It is an option, which can be disabled. Are there disadvantages of MagiskHide? Is it a performance issue since MagiskHide is a daemon, running in the background? Or are there any other reasons?

(I tried to google this topic and search on xda, but I couldn't find an answer)
[Magisk] DodoGTA:
Because some devices/ROMs have issues with Magisk Hide being on
[Magisk] jenslody:
Your recovery.log at github shows, that it found a magisk.img.

Try the latest uninstaller from main thread first to get a real clean system.
[Magisk] Recycool:
Just to be sure, so there is no way to have xposed+magisk hide?
[Magisk] andmail:
I solved the issue by replacing update-binary file from Magisk-v13.0(a90e8b6) (the lastest official beta can be installed on my device without error 1).
[Magisk] jenslody:
Magisk hide works (hiding root and magisk itself), but not hiding xposed, so passing safety-net fails.

http://repo.xposed.info/module/com.pyler.nodevicecheck, as suggested by @lover in this post, together with systemless xposed-module in magisk, makes ctsProfile pass (by faking the server-response).

BasicIntegrity still fails.
[Magisk] Dominicano2:
Thank you very much :good:
[Magisk] neolivier:
Thx for the tip

I tried to flash your zip, but I still get an error:

ioctl LOOP_SET_FD failed: Device or resource busy

mount: '/dev/block/loop0'->'/magisk': Invalid argument

:eek:
[Magisk] EinsteinXXL:
Hi, I have a little problem with magisk. I do not want to use magiskSU because it has no PIN protection as SuperSU it has. The problem is after flashing magisk and then SuperSU the magisk manager shows the wrong Magisk version. Instead to show v13.3 the manager shows the SuperSU version 2.82. Is there any workaround?
[Magisk] lover:
[MENTION=8340552]jenslody[/MENTION]

With only ctcPeofile pass I got Play Store certified (clearing data and cash and it now shows certified)

I am not sure what is benfit of certified over uncertified
[Magisk] cygery:
OK, it works when I've only one of my toggle apps/widgets installed. However, when I install and create widgets for many/all of them, the issue appears again. Somehow root requests get stuck/fail and the widgets don't load. Especially, this happens after a reboot when all widgets update their state at once. Is there any size limit on the root queue which could lead to root requests being dropped?
[Magisk] andmail:
Try to flash each beta from this thread. If success take "update-binary" file from beta and place it to the final offcial magisk-v13.3.zip (\META-INF\com\google\android) :angel:
[Magisk] Pkt_Lnt:
Hey Einstein, ;)

You need to choose one or the other root method, not both. They are not compatible.

Read the last section, bottom of this post.

https://xdaforums.com/showpost.php?p=72587983&postcount=22

From this thread.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] lover:
Magisk v13.x is not compatible with SuperSU. Try v12.

I myself paid for SuperSU Pro but i find Magisk better but i keep SuperSU in my older device

There is no point of using SuperSU with magisk.

Magisk's SU hide works very well with MagiskSU
[Magisk] Didgeridoohan:
Holy crap you've got a lot of toggle apps/widgets! :laugh:

I think [MENTION=4470081]topjohnwu[/MENTION] logged 15-20 su requests in one second with Toggle Data. So if every one of those apps/widgets do that, I'm not surprised there's gonna be some issues... How many can apps/widgets can you have active before it starts failing?

I don't know the limits of the request queue, but I can try to find out.
[Magisk] woozie.2007:
Hi guys, if i want to enter in superuser the app close instantly, how can i see what app have acces root or not? And safety net sometimes is both green ok, sometimes is both red, i don't know why.

And i tried to install viper4android module and magisk module crashing everytime

Thank you
[Magisk] yochananmarqos:
You'll get no help with that app on XDA. It's a taboo subject that can get you banned.
[Magisk] theandroidguy:
Ohhh I'm really very sorry, I was unaware about this, thankyou mate for the info. Moderators can delete my comment, plz
[Magisk] Pkt_Lnt:
Search for "clear Magisk Manager data and cache". You will find both questions like yours and replies that it works! :D
[Magisk] woozie.2007:
Thanks, i cleared data and now it works superuser, i can see all apps. But still i can't install modules, keep crashing magisk manager
[Magisk] Pkt_Lnt:
Many have reported this. Have you provided the logs and the information requested in all the troubleshooting guides?

Here is one.

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] cygery:
Oh dear, thanks for the info, I'll try to implement a better handling of root requests.

Just tried two widgets (toggle data and toggle cell radio) and it already starts failing (tested after a reboot).
[Magisk] Paschfire:
Yes, as this app is used mainly for stealing paid app content... With patching.

So if you're one of these people using this app for the purpose of stealing paid content, taking money out of the pockets of hard working Developers, then you'd be best to keep this to yourself as most Android forums will ban you, berate you and more than likely shame you out the door for condoning the use of this app for the purpose of stealing.

... Or you could simply just stop using it.

#SupportDevelopers

To the Moderators I apologize for the OT, I just felt the need to speak on this topic.
[Magisk] DodoGTA:
So, why does an app Lucky Patcher exist in the first place?
[Magisk] ShadySquirrel:
Because people owning 400$+ phones can't afford 1-5$ one-time payment for an app or functionality. Or are simply greedy and want everything free.
[Magisk] Paschfire:
Over the years I've heard many reasons(excuses) from users for why they use LP, for example.. "Oh I only use it for YouTube background streaming, I don't use it for stealing paid apps".

While this is true LP does have some less intrusive features(even this being a grey area of discussion). Is that many, if not all of, these less intrusive tasks it does perform in most cases can be easily found amongst other dependable/trustworthy sources of Development.

But really its main design "attraction" is just using it for the purpose of stealing paid content by patching the application.
[Magisk] aaron804:
I didn't find this asked anywhere when I searched and sorry if this is a dumb / obvious question.

Is there / could there be a Magisk module that would fake my "Unlocked Galaxy s8" as an "AT&T branded Galaxy s8"? So I can take advantage of voLTE, HD Voice, and WiFi Calling on AT&T. Or is that all handeled via IMEI #'s in AT&T's database?
[Magisk] bluenote73:
I find your moralizing funny in a thread for an app that enables some significant portion of users to evade ads. How about we just stick to the topic?
[Magisk] divineBliss:
How does one find out which Magisk Manager Module template version a Magisk Module supports and what Module template version each Magisk Manager version requires?

It would seem like this template version information and checking should be part of the Magisk Manager app - unless it's there and I missed it. Thanks :)
[Magisk] Jashane:
Installed

MagiskSU 13.3

Magisk Manager 5.1.1

xposed-v87.0-sdk23-topjohnwu.zip

XposedInstaller_by_dvdandroid_29_04_17.apk

But Xposed modules not working

Any fix?
[Magisk] Legendary Cryptid:
I have Magisk 13.3 and Magisk Manager 5.1.1 installed. I tried inatalling the Unified Hosts Adblock v2.1 through Magisk twice, and it failed both times. Then I tried installing it through TWRP, and it still failed. Is there any way to fix this?
[Magisk] yochananmarqos:
Look at the module.prop in the module ZIP to find out what template version is being used.
[Magisk] theandroidguy:
What apps I use nd what I dont are my personal matter nd as I said I was unaware abt this issue, as this talks abr warez, so sorry once again

---------- Post added at 06:13 AM ---------- Previous post was at 06:10 AM ----------

Did anyone tried the search button on the module downloads section, as soon as I typed the name the manager is crashing. Anyone else who's facing this problem????
[Magisk] Artim_96:
It's even the question if it could work with your ROM or if at&t adds some additionals to their devices firmware to be able to use that.

There is no module for that, but the app Root Essentials can do that.

I don't know what it changes but if it changes something in /system it should be possible to make a module for that.

So I'd recommend to get the app and find out what you need to do to make your device an AT&T one and see if it actually helps
[Magisk] slim.gassara:
i updating magisk 13.3 and magisk manager last version last night however i rebooted my device today .. but i find that magisk manager stopping work !! i tried to reinstall it but the same problem ... so i desinstall magisk with the last desinstaller and i reinstalled again ... it's back to work normally after rebooting my device i find that the same problem exist ... even i check the root but suddenly no root access.... some one can help ?! i really need root access on my phone :(
[Magisk] durbanpoison29:
Hello everyone ;)

Even worries this morning waking up, more root access with Magisk 13.3, so I uninstall and then re installs Magisk.

The root is again accessible for a brief moment, also Safetynet.

It worked properly until morning.

I uninstall and re install again and again but even worries, root present then loss of root shortly after
[Magisk] Didgeridoohan:
You can help find a fix by providing some logs.

Grab a logcat while you're installing the module through the Manager. And then save a recovery log from after flashing the module in TWRP (Advanced - Copy log).

Attach both those files to a post here.
[Magisk] durbanpoison29:
re,

It seems that as long as I do not open Magisk Manager the root remains and SafetyNet is ok, but if I open MagiskManager the root is lost and I have to re-install Magisk.

Strange as a problem, suddenly I do not dare open MagiskManager.

That did not happen yesterday.
[Magisk] jenslody:
Logs, logs, logs and information about your phone, rom, etc.

How should anyone be able to fix it without meaningful information ?

---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------

How did you install, MagiskManager or TWRP ?

I have xposed 87.1 installed through TWRP and wiped Dalvik/Art-cache before reboot, and no issues.

Installing through Manager did not work (for xposed).

And logs please !!
[Magisk] durbanpoison29:
Hi,

Samsung S6 SM-G920F

Android 7 SDK 24

Root with magisk 13.3 via TWRP

For the logs I do not know how to do, about me worries do not bother me since I know that I no longer need to open magiskmanager.

I'm just putting together information about a problem that I'm looking for, without waiting for help to solve it.
[Magisk] Casual058:
Don't know if this is the right place , but oke

Magisk always worked until a week ago. Cant update in the app it's self. i'm getting an error that it only works on lollipop 5.0.- and higher, but i'm on 6.0.1.

And when i try it in twrp after uninstalling magisk it is giving me:

! Magisk process ended with ERROR: 1

Error installing zip file '/data /media/0/MagiskManager/Magisk-v13.3.zip

Anyone know how i can fix this? I have been looking fot days and cant find anything online
[Magisk] Rekesz:
Hi Everyone,

I'm using the galaxy s4 AOSP 7.1.2 by JDCteam. They include Magisk in their newest releases, I've tried stable 7 with the 13.0 beta, but it was giving a Device or resource busy error. I have now upgraded to the new stable and I keep receiving this error. I've actually been using Magisk v12 as none of the v13 versions worked for me. I saw a solution in another post, but it still kept giving this error message. I've attached the logact. I installed appsystemizer first and after a reboot greenify as well, but it keeps doing this and the icons are not shown in the launcher. Any help is appreciated.

Edit: I've tried uninstalling Magisk and reinstalling it, but that did not help. Also, I'm using TWRP 3.1.1.0. I used 3.1.0.0 for previous installations, thought that would be the problem, but nope.
[Magisk] Jashane:
Unfortunately the log files were empty

/data/data/de.robv.android.xposed.installer/log

The log is empty 0.0 bytes
[Magisk] Jashane:
My device is

Aurii Passion

Stock ROM

SDK23

ARM64-v8a

MT6753

Installed

MagiskSU 13.3 (recovery)

magisk Manager 5.1.1(included on magiskSU)

xposed-v87.0-sdk23-topjohnwu.zip (recovery)

XposedInstaller_by_dvdandroid_29_04_17.apk (manual)

The MagiskSU is running properly

The Xposed framework is installed properly

But the Xposed modules don't work

Here's my magisk log tho

Can't remember if I wiped the dalvik and cache

Will try it later
[Magisk] LuthorKid:
Is this only applicable on lineageOS? And can I implement it on samsung touchwiz based roms? Because I'm having the exact same issue on my s7 edge. Thanks.
[Magisk] DodoGTA:
1. No

2. Maybe
[Magisk] hipi0101:
Hello, i can not install Magisk Module, but magisk 13.3 is successfully installed :/

Before that it was wonderful with 12.0 but now does not even work this version 12.0..

Rom: Lineage

Device: Sony Xperia Z3 Compact
[Magisk] CooperBrick:
Has anyone experienced this? It happens everytime I flash latest magisk
[Magisk] TristanDesigns:
Please provide more information about your problem, like what happens when you try to install a Magisk Module. What version of Magisk Manager are you using? Which module are you trying to install? Does it happen on all modules? Are you trying to install it through Magisk Manager or flashing it through recovery? What error do you get? Maybe provide a logcat.
[Magisk] danilo_scala:
only question, i put my problems in install magisk 13x in others post, ok. . i try magisk 12 install (root) but no pass safetynet (red). magisk 12 no pass? need update? try unninstal magisk and no pass safety net.
[Magisk] powerdoesntrun:
Same here. Somehow, overnight, Magisk Manager has completely stopped working and I no longer seem to have root.
[Magisk] durbanpoison29:
Same for my part, I expect this to happen to post the log of Magisk.

This is reproduced just now for no particular reason, as a moron I erased the log Magisk instead of saving it.

The root is unstable.

My device:

Samsung S6 sm-g920f

Android 7 SDK 24

root with Magisk 13.3 and TWRP