yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Why the shotgun messaging? :confused: Ok, since you're spreading this question out there I guess I'll add my answer to you here as well (in case someone finds this later), with a couple of additions:

You're confusing things... 3.18 (three point eighteen) is a lot newer than 3.8 (three point eight).

And there are kernels of version 3.4 around that has had the necessary features backported, so 3.8 isn't set in stone.

If your kernel version is 3.18, you're good to go.

It's perfectly possible to run several different ROMs at the same time. I doubt one of them will seem untampered with though. I have no knowledge of this though since I've never messed with Multi-ROM... So you'll have to look that one up yourself/hope someone has an answer.

And keep in mind that there are numerous apps out there with detection methods that we know nothing about and that neither topjohnwu or Chainfire can circumvent.
[Magisk] jam3972:
"Hide Magisk Manager" issues

So I've got a dumb question/situation. Want to share and ask advice.

In case it matters I'm running Nexus 6p on Android 8.0.0

So I accidentally tapped "Hide Magisk Manager" while in settings, which immediately closed out Magisk and hid it all, as designed. (It would be nice to have a confirmation dialog for this)

Having never used this feature before I didn't immediately know how to re-enable it. In my panic I just uninstalled the only Magisk thing still left in app list.

Turns out this was the "Unhide Magisk" app that was specifically there to undo this. So that's gone, no backup. Woops #2.

I decided I would just re-install Magisk to bring it back. But after re-install it is still hidden and there is still no unhide app to unhide it.

It was definitely still there as I still had root.. but I couldn't get into manager anymore.

So next I run the uninstaller. Thinking that would wipe any trace.

Re-installed Magisk 14.0 and then.. nothing. Now there is no root and no Magisk manager to check it.

Next thing! Ran uninstaller again. Flashed stock system and boot img. wiped dalvik/cache. Still nothing. Same as above.

I really don't want to do a whole factory reset just for this. Any ideas on what else to try? Does anyone know what exactly "hide magisk manager" does? can I manually undo that? Any other ideas on how to bring it back?
[Magisk] Didgeridoohan:
Yeah, this has been an issue for a few users since this feature was introduced.

You could try this: https://xdaforums.com/apps/magisk/m...systemless-t3432382/post73794918#post73794918
[Magisk] jam3972:
Thank you so much! That did it.

I swear I used search first, but too many results for magisk hide to make this easy to find.

Thanks again.
[Magisk] JimZiii:
Magisk xposed

I thought using xposed through magisk modules would help with the safetynet check but it trips it anyways, and if I want to turn off xposed a while to do something, then I have to reinstall the whole xposed app everytime for it to start back up correctly.

Is there a way around this? At least a way to turn it off and on again without reinstalling whole the app?
[Magisk] tdhite:
Rather than all that work, why not just run this as adb shelled in:

su
magiskhide --disable
reboot

?
[Magisk] will5:
Guys, may I know how magisk hide works or what is for?

ie. For super mario run I just installed magisk v14 and it s running fine.

But for other apps, I need to tick them on magisk hide tab because they complain about modded phone. What does magisk hide tick, hide? Magisk itself? Root? safetynet?

Should I tick mario run on magisk hide if its already working fine?

Thanks
[Magisk] Legendary Cryptid:
[MENTION=4667597]Didgeridoohan[/MENTION] Just managed to flash the patched boot image; however, now I'm getting process errors when I try to download Magisk modules. How do I fix this?

Also, should this be considered normal if you flash the patched boot?
[Magisk] olivercervera:
Non entirely true. I have tested the app on a stock MotoE 2015 and works perfectly; on any device with Magisk doesn't. They have "simply" upgraded their root detection and they catch Magisk. Unfortunately there's no easy way to report this: ADB doesn't show much.

I tried decompiling the app and honestly I can't get much out of it: I'm not a developer and this goes beyond my knowledge.
[Magisk] onliner:
Hi, i making my custom module with some settings and apps, but i have a question, in one of my devices some roms have sdcarfs enabled by default (this line in build.prop: ro.sys.sdcardfs=true), so, if i put "ro.sys.sdcardfs=false" in resetprop, would it work? Or could it cause "problems"?
[Magisk] Pkt_Lnt:
I do not use Barclay's app, I just went by what a seemingly knowledgeable user did to fix the problem. Seems you missed this part of what I quoted:
[Magisk] k0m3n9:
Same to mine after flashing patched boot img. What message did you get in the process errors? Is it "zip is not a magisk module"?

Maybe not all type of devices will get this but on my Galaxy J1 Ace (SM-J111F) it seems " Patched boot img" installation method resulting Magisk Manager cannot auto detect the Boot Image location.

---------- Post added at 12:11 PM ---------- Previous post was at 11:47 AM ----------

If Xposed is a must to you, try xposed module "No device Check". At least i'm getting ctsprofile : true on my Galaxy S5 running LOS 14.1 and managed to get/install LOS Updates without problem.
[Magisk] gudenau:
That's got old versions, figured it wasn't needed since it wasn't updated.
[Magisk] Didgeridoohan:
That command is useful if you want to manually disable MagiskHide. We were talking about the new feature that hides the Manager. Different thing...

You've spent some time in this thread, so I would have figured you would have caught one of the most talked about bugs with Magisk v14.0... :laugh:

Try searching for process error...

(Yes, I've deliberately stopped spoon feeding the solution for that one.)

No idea. This installation process is so new that there's gonna be problems and issues that we don't know about yet.

Great you got it working though. Are there options you can pick in the list?
[Magisk] olivercervera:
I saw that indeed. There is some people complaining about app stuck at start screen, but is the minority. The reality is that Barclays put in place an aggressive Magisk detection. False positives will occur, obviously!
[Magisk] Domi14fr:
Hi, i try to update magisk 14 on meizu pro 5. I have a RR rom. When i try, it can't detect the bootimage... So i select the SDA26 and when i click to install, nothing happens....

Help please!
[Magisk] Artim_96:
What do you mean with SDA26?

And if it fails in the app, try either through TWRP or the other method
[Magisk] DodoGTA:
He probably meant /dev/sda26 or /dev/block/sda26
[Magisk] Artim_96:
Ah, ok. Well, I have no clue about partitions on any device
[Magisk] Captain_Throwback:
Maybe you should try reading through that thread, or at least check the last few pages of it...(before assuming there's no up-to-date version there)

People really need to make more of an effort here to read and search.
[Magisk] Domi14fr:
Yes /dev/block/sda26...

With TWRP they are a error "Unable to detect boot image".

All people with a meizu pro 5 it's on 13.3 because the 14 doesn't work... :(:(
[Magisk] Legendary Cryptid:
[MENTION=4667597]Didgeridoohan[/MENTION] I just got the message "This zip is not a Magisk Module!" upon trying to install the Busybox module. Any suggestions on how to fix this?
[Magisk] Artim_96:
See if that problem is an issue on his GitHub page. If not, create a new one with TWRP log

---------- Post added at 02:14 PM ---------- Previous post was at 02:11 PM ----------

You can unzip it and zip it again, often the problem is that the zip file is not properly done
[Magisk] Didgeridoohan:
There's a pull request with a fix for that on GitHub. Not much to do but wait until it's been committed.

What [MENTION=5125527]Artim_96[/MENTION] said... Most of the time this error comes from the zip not being packaged correctly. All the module files and folders need to be in the root of the zip.

If they already are, you have some other issue and a logcat from the module download/installation might show something.

The issue tracker on GitHub has been closed. I guess it was just getting to cluttered with irrelevant stuff...
[Magisk] Deith:
So I'm using OnePlus One with SultanXDA's LineageOS 14.1 and TWRP 3.1.1.0. SELinux is set to restrictive (by default) I just flashed the rom and I unlocked developer options, after installing Magisk I don't seem to get root access (I installed viper4android and it doesn't seem to change sound output at all), the Magisk Manager didn't ask for anything (permissions) when I opened the app (same as viper4android), in android setting > developer options the Root access is greyed out. Here is how I installed magisk:

1. Downloaded Magisk-v14.0.zip from the main topic

2. Connected my phone to PC and coppied the file to the base directory /sdcard

3. Rebooted into TWRP

4. Selected "Install" > picked Magisk-v14.0.zip

5. Installed it

6. Rebooted (I tried skipping wipe cache/dalvik and on second try with wiping cache/dalvik)

7. Opened Magisk Manager

Everything there is green and running, latest version (14:0MAGISKSU (topjohnwu) is green, installed verions is green, in advanced settings keep force encryption and keep dm-verity is unchecked but I don't know what they do and if I should check them. I can navigate through app (Superuser section is empty), I can download and install modules. What am I doing wrong?

I have magisksu_log.txt from https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 but I don't know where to post it

edit: it seems that it actually works but the viper4android is having issues with magisk14 and I just got bad timing with installing it and have to wait for proper fixes (anyone can confirm it?)
[Magisk] DodoGTA:
You're supposed to manage root requests in Superuser section of Magisk Manager if you're using Magisk v11.0+

Also, if you want to change the root access mode, then there's an option exactly like that in Settings section of Magisk Manager

And, V4A module from the Downloads section of Magisk Manager works fine with Magisk v14.0 (at least in SELinux permissive mode)

Note: If you're getting Processing: No in Driver Status menu of V4A app, despite the Master Power and some effects are turned on for the audio playback device you're currently using in the V4A app and you're playing some audio, then disable AudioFX by running "pm disable org.cyanogenmod.audiofx" (without quotes) in a terminal emulator (with root access, of course)

This solution worked for me on LineageOS 14.1 :)
[Magisk] Legendary Cryptid:
What [MENTION=5125527]Artim_96[/MENTION] said... Most of the time this error comes from the zip not being packaged correctly. All the module files and folders need to be in the root of the zip.

If they already are, you have some other issue and a logcat from the module download/installation might show something.

Here's a logcat for when I tried to flash the module through the manager.

Also, the magiskhide daemon isn't starting up when I reboot my phone.
[Magisk] Deith:
So I managed to give root access to the app (it shows up in Magisk Manager in Superuser secion), run the AudioFX command but if I run the app and I see:

Driver Version: 2.5.0.4 (I think it supposed to be 2.5.0.5 but for some reason the app updated the driver and downgraded itself?)

NEON Enabled: No

Enabled: No

Status: Abnormal

Audio Format: Unsupported

Processing: No

Samplig rage: 0

Maybe it's because SELinux is set to restrictive, how do I change that? What can it affect if I change it
[Magisk] DodoGTA:
Try to set SELinux to permissive mode
[Magisk] jenslody:
Can you upload the busybox-zip somewhere and pm me the link to it ?

It might be useful to look into it and compare it with a working one.

Just for the record which phone and rom do you use ?
[Magisk] ShadySquirrel:
V4A doesn't have access to stuff it needs because of SELinux, that's why you get errors. Try with module from my signature, it works fine on SELinux enforced and LOS 14, or find a fix someone posted somewhere in beta threads.

Edit: what-a-hell-happened-to-my-english
[Magisk] am2006:
I cant install modules, it gave me error processor
[Magisk] Didgeridoohan:
Don't post HUGE screenshots! They are extremely annoying! Use attachments... please...

That's the single most discussed bug in Magisk v14.0. Search the thread... You'll find the answer.
[Magisk] Rajkumar-RK:
help

using miui global 8.2, stable

how to remove root access and install Magisk once i tried just uninstalling the supersu but my phone doesnt rebbot,so i restore my backup,

so i wanna do it again with proper guide please

thank you

device redmi 3s prime
[Magisk] Deith:
It works! Thank you very much, I have slight hearing problems and now I can finally balance left-right other apps than PowerAmp (also discovered Viper doesn't work with Poweramp but that's ok) :good: :)
[Magisk] ShadySquirrel:
You're welcome :) Glad I could help. p.s for V4A and PowerAMP DSP, try forcing V4A into compatibility mode. But expect significant battery drain.
[Magisk] hokiealumnus:
Out of curiosity, does your V4A module have provisions for a/b partitioning on Pixels?
[Magisk] Jaizu:
Trying to install/updating a module gives me an error if the folder "MagiskManager" doesn't exist. I did a clean install of OOS 4.1.7 (OnePlus 3T) and clean installing Magisk 14.0 won't create that directory.

So I guess this is a bug [MENTION=4470081]topjohnwu[/MENTION] , if directory /sdcard/MagiskManager doesn't exist when trying to download/update a module Magisk will give an error, to fix is just make MagiskManager check if that folder exists when Downloading/Updating a module, and if it doesn't, just create it.
[Magisk] Legendary Cryptid:
I need some serious help. I accidentally deleted my Google Play Store and Play services, and upon reinstalling them, I was then told that my device does not support the services, despite doing so since 2016.

On top of that, I don't have a stock boot image for my phone anymore. How do I fix this?
[Magisk] broomer68:
(Dirty) flash previous /original rom and reflash magisk

Verstuurd vanaf mijn SHIELD Tablet K1 met Tapatalk
[Magisk] Didgeridoohan:
Already fixed for the next release:

https://github.com/topjohnwu/MagiskManager/commit/53cf11db8cbe63ff7365056f7a9f6e5e14cae46d

Whoa! How did you manage that?

Anyway... Reflash your firmware package/factory image/ROM (whatever's applicable) and you should be good to go.
[Magisk] ShadySquirrel:
TBH, I know nearly nothing about a/b partitioning because I don't have a/b device so never bothered to learn about it, but it should work as long as Magisk is mounting stuff properly and SEPolicy injection works.
[Magisk] Legendary Cryptid:
Thanks. Also, according to an app developer I'm in touch with, my magisk core directory is missing since I flashed the patched boot image. How do I fix this after I'm done reflashing the stock rom?

Also, I still don't know if this will fix my Google play problem or not.
[Magisk] yvesfg:
what folder? where?

Where and the of this folder you have created?
[Magisk] k0m3n9:
Is it possible to edit this manually..?
[Magisk] Didgeridoohan:
Are your sure your just haven't enabled the showing of hidden files and folders in your file explorer. The core folder is a hidden one... It'll be under /magisk/.core (the dot means it's hidden).

And doing a complete reflash of your system should definitely fix your Google problem.

You're sooo close to the answer... :D MagiskManager, in the root of your internal storage. :p

See the first part of this post:

https://xdaforums.com/showpost.php?p=73891765&postcount=19189

Edit: wait a minute... You didn't have a Meizu, did you? :) Anyway... Unless you can select the correct location in the drop-down, there's not much you can do. What it means is that unless there's some kind of fix for it your probably just gonna have to update Magisk by manually patching and flashing the boot image.
[Magisk] Mumtaz77:
Sorry if this bug is in the topic. I'm not find.

So. since V13 version if I tap the "Superuser" option in Magisk Manager menu - to check/set the applications superuser permissions -, the manager is close (equal like windows "crash to desktop")

Do this with all my mobile firmware versions since from B380 to newest B394. Honor 8.

(Sorry my bad english)
[Magisk] DodoGTA:
Clear data for Magisk Manager :)
[Magisk] k0m3n9:
LOL.. I'm not on Meizu :laugh: At this moment for my SM-J111F I just use twrp to install Magisk 14.. then replace twrp with patched boot image. This way it allows Magisk Manager to auto detect the Boot image location. Hopefully this will be solved in next update of Magisk manager esp for those who just wanna use patched boot img to install Magisk. The only thing now is my phone keep prompt 'Unfortunately, Google Play services has stopped" after installing Systemless Xposed sdk 22.. and ota update fails because it detects the operating system has been modified in an unauthorised way (I dont think there will be more official system updates for this phone LOL)
[Magisk] perillamint:
Magisk don't work on Hanabank app (strace log attached & suspicious syscall)

Hello everyone.

Today, I found Hanabank app (com.hanabank.ebk.channel.android.hananbank) detects Magisk hide. I ran strace against Hanabank app, and I got some suspicious openat(2) returns -EACCES and even some files are not filtered by Magisk Hide (returns file descriptor successfully)

Here are openat(2) calls which don't look good.

```

[pid 27855] openat(AT_FDCWD, "/sbin_orig/magisk", O_RDONLY|O_LARGEFILE) = 91

[pid 27855] openat(AT_FDCWD, "/dev/magisk/mirror/system", O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied)

[pid 27855] openat(AT_FDCWD, "/magisk", O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied)

[pid 27855] fstatat64(AT_FDCWD, "99-magisk.sh", {st_mode=S_IFREG|0755, st_size=2011, ...}, 0) = 0

```

(Full strace log of Hanabank app: pastebin dot com slash BUiViAbK , spam filter filters out pastebin link. :'( )

I think they should return -ENOENT to pass that magisk detection routine.
[Magisk] schodoodles:
Just wanted to confirm I've just upgraded a Nexus 5X (rooted but stock nexus image) from Android 7.1.2 to the latest Android 8.0.0 and then re-applied Magisk v14 via TWRP in recovery and all worked a charm. No issues and safety net check passed fine.

Thanks!

Scho
[Magisk] yvesfg:
Dude, thanks a lot, but the error continues. When I try to download a module or install from the same error. MANAGERERROR: ProcessRepoZip: Error!
[Magisk] Didgeridoohan:
So you've created the folder in your internal storage? What about making sure that the Manager has storage permission?
[Magisk] Clonkex:
[MENTION=4470081]topjohnwu[/MENTION] Just want to say..... FANTASTIC work! I'm super happy to have seemlessly-working systemless root WITH adaway support on my HTC 10 :D When I have some more money in a couple of weeks I'll even budget in a donation :good:
[Magisk] WarriorMax:
I also can't seem to download and install from magisk manager. It has suddenly stopped working and shows a toast as "process error". I can install the already downloaded modules easily though. Pls help
[Magisk] brenosnt:
Is possible to mount /system folders in RW mode to integrate GApps updates into ROM with Magisk installed? Titanium Backup and similar isn't working properly because all folders is in RO mode
[Magisk] Didgeridoohan:
Just look back in the posts related to the one you posted. Or search the thread for the error. I'm positive you'll find your answer...
[Magisk] jhedfors:
You should not have to uninstall/reinstall Everytime. Assuming you are using the Magisk xposed module, just disable and reboot should work.
[Magisk] Debix:
From androidpolice (copy & paste) - for the "Toggle On/Off don't work" issue.

"(...)

Also, there's an alternative way to unroot, going direct to Recovery and flashing a script called unSU before everything else:

xdaforums.com|showpost: php?p=63615067 (Link edited)

In some cases, the root toggle does not work (cycles back to ON), so the most guaranteed procedure is:

1) Go to recovery

2) Reflash your ROM

3) Reboot to Recovery

4) Flash on the same queue:

4.0) Custom kernel (OPTIONAL, see details on Magisk topic at XDA)

4.1) GApps

4.2) UPDATE-unSU.zip

4.3) Magisk-v6.zip

4.4) phh-superuser-17-magisk.zip

5) Reboot to system.

6) Go to Play store and Install PHH Superuser app

7) Install Magisk Manager APK"

Works, but PoGo still refuses to run. Seems like Cyanogen is banned, too.
[Magisk] jun_ng_1208:
Toggle root to off and run PoGo again... Should work just fine :)

---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------

Did you install the compatible SuperSU or phh's Superuser as per the OP?
[Magisk] alexpower:
Check with safetynet helper from playstore.

If check is red, Pogo doesn't start

Gesendet von meinem HTC 10 mit Tapatalk
[Magisk] -Happy Feet-:
Is red, but why :(
[Magisk] ken2802:
is there any change it can damage the bootloader while installing ?

S6 Edge
[Magisk] JudgeDread11:
If magisk works but Pokemon not please find out start a tad for Pokemon.

This is the magisk tread.
[Magisk] cdiamond2:
Somebody please tell me if this is a solution to run Good Work on rooted and xposed device.
[Magisk] Captain_Throwback:
Why don't you try it and tell us?
[Magisk] cdiamond2:
Do not have a corporate account yet. But sure I will try later
[Magisk] Captain_Throwback:
I can confirm that Magisk allows me to authenticate with AirWatch Agent with Root and Xposed installed - just have to toggle root in Magisk Manager before going through setup. I'd imagine Good would be similar.
[Magisk] therock11:
I'm installed as per the instructions.

ROM - cyanogenmod 13 (LG G4 H811)

Gapps nano

Magisk

phh's Superuser

xposed Magisk

I then booted in and installed the apk for Magisk manager. When I toggle it I get the message stating "SuperUser granted to Magisk Manager" and then my SU goes away for the system until I reboot.
[Magisk] maiconjs:
Any solution for Moto X1 ? The Touch Screen have issues after flash Magisk.
[Magisk] Turbopuschel:
Thanks, adding the unSU step did the trick for me when I tried out a Nougat ROM on my Xperia Z1 Compact.
[Magisk] geek85:
hello,

It seems that I can't root with magisk on a Zenfone 2 (x86).

I flash a stock (5.0) firmware from Asus website (+wipe cache/dalvik), I flash the TWRP recovery and I flash Magisk then phh's SuperUser (magisk version).

From the magisk manager, I have "Root Status: Not Rooted" in green.

Is it possible to root the Zenfone 2 with Magisk?

edit: I try the unSU trick but nothing appears to change.
[Magisk] psycholyzern:
Hi. Im having a weird situation with magisk. Idk what to tyoe in the search box, so I need someone help.

Whenever I toggle off root, it will kick the toggle to on.
[Magisk] Ella28:
It says unable to detect bootimage wben i flash magiskv6.. how to fix this?
[Magisk] alexpower:
If you turn root off in magisk and safetynet check is red, then your magisk install is not correct.

Maybe some old Su files in system/xbin etc. and other folders, because of that safetynet will fail.

Gesendet von meinem HTC 10 mit Tapatalk
[Magisk] laurorual:
Hi! I'm using MIUI 7 v6.5.30 beta (based on Android 4.4.2) on my LG G3 and I'm facing a weird problem. When I try to install the Magisk Manager I can't even open the apk, it says something about an analysis error. The apk is not corrupted because I've downloaded it many times and the same apk can install fine on my Galaxy S5. I've never installed anything related to Magisk in this phone ever so I don't know what is causing this. Can anyone help me?
[Magisk] Caramon420:
Did u install phh supersu from app store if u don't u can't switch it off or on
[Magisk] Ella28:
Can someone pl help me, dunno what to do im using rr 5.7.2 on zenfone 5 and i cant flash magiskv6 it sys unable to detect bootimage. :confused:
[Magisk] DodoGTA:
Someone else already reported an issue like this in Google's issue tracker: https://issuetracker.google.com/issues/64434571
[Magisk] WarriorMax:
Ohh thx u thx u.. Found it.. No folder issue
[Magisk] friscoboi:
Root App Deleter does Not recognize root any more in 14.0 :(