yashsingh1/xdaforums huggingface dataset:
[Magisk] waylo:
You need to install the phh-Superuser app from the Playstore.

EDIT: simultaneous reply!
[Magisk] wvcadle:
Thanks, so I need to both install the app from the Play store and flash the phh.SuperUser zip?
[Magisk] N1ghtr08d:
Cool, I'll give it a shot tonight after work. Thanks bro
[Magisk] wvcadle:
Figured I'd respond to each of you. :)

Okay, I downloaded the phhSuperUser from the Play store and have obtained root, and the Magisk app now opens.

Last question (I think).. do I install the Xposed apk and flash the Xposed zip linked in the OP? Also, upon opening the Xposed installer, it says a new version is available. Should I update?
[Magisk] waylo:
Yes. The OP has been incrementally updating the instructions, so some of is this is recently added.
[Magisk] tikizondo94:
Install the xposed version in the OP. Reboot and install the xposed installer apk. Also you can download the latest update via the app. I'm running it as we speak. Works fine
[Magisk] garthybarthy:
Hi all,

All is installed and working here, when I open any apps it automatically provides root and doesn't prompt for root access with phh supersu app.

Also everytime I restart my device it states the su binaries are out of date, I click to update them but nothing happens. Any ideas?

I was going to download supersu zip from phh thread in case it's more updated but the OP on this thread states the supersu is specifically for magisk, so a zip from the phh thread wouldn't work I'm guessing.

Thanks all.
[Magisk] intruder16:
I just installed this on my friend's Moto G 3rd Gen

stock

and it worked !!

All i did is install in this steps:

1. Install phh's superuser app from playstore and reboot to TWRP.

2. Flash Magisk.

3. Flash phh's superuser zip.

4. Flash Xposed 86.3.

SafetyNet Helper showed CTS "false" but when i toggled root from Magisk Manager it showed "true".

If only there was systemless xposed for MIUI, i'd have tried it on my Mi3 too.

Still, kudos dev for this awesome work!
[Magisk] stokholm:
But it won't install unless you have the stock recovery either, which you don't if you flashed Magisk. So I'm having trouble seeing the value in systemless stuff altogether. I'm not trying to be snotty, I'm fairly convinced there's something that I've misunderstood.
[Magisk] Tipika:
Ok so i reflash the stock recovery, then if i apply the ota update, i will lose root or magisk will continue to work?

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Magisk] cthulhu1987:
All is well on my phone (SM-G900F, Stock Android 6.0.1, CSC "DBT"), installed it without a hitch, Xposed works and I was able to circumvent Niantec's use of SafetyNet, too. Thanks you VERY much! I'm gonna try out the same on my Fire Phone (there could be problems with the boot loader, though).
[Magisk] Syoenth:
Will be a fix for Samsung S3? I have sepolicy issue
[Magisk] daleski75:
I am now running my own CM13 builds with root totally disabled so both work now without any issues whatsoever.
[Magisk] Nando_aot:
Hi all,

I do have a LG G2 D802, I am using rom AICP (MM) based on CM13, when I do flash the files I got the security boot screen after reboot, I saw some topics that is necessary another file for LG. [MENTION=4456638]Äptiva[/MENTION] as I saw that you have a G2, there anything necessary to do to install it? Before I flash AICP I have flashed the bootStack file, maybe it is related.

Thank you all
[Magisk] Captain_Throwback:
You'll have to flash (or boot) custom recovery to flash Magisk again (and possibly the root zip), but that's it.

http://xdaforums.com/android/software/mod-magisk-v1-universal-systemless-t3432382/post68656308
[Magisk] qwertyxyz001:
not working on my device lenovo a7-30hc
[Magisk] Captain_Throwback:
http://xdaforums.com/android/software/mod-magisk-v1-universal-systemless-t3432382/post68673459
[Magisk] B6000man:
Thank you post #1906. It is the answer for the locked toggle problem that is now gone on my l720t phone!
[Magisk] smellz:
Have now done the following .

1. Cell unroot per SuperSU ( If only a short note, then the app closed )

2. boot into TWRP manually and flashed Magisk - v6

3. next phh 's systemless superuser ) with Super SU magisk version already tried )

4. Mobile launched new

5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...

Anyone know what I'm doing wrong ?

Have a Sony Xperia Z3 D6603

gerooted and SuperSU ( 2.78 )

TWRP 3.0.2-0

Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )

Locked Bootloader

would be great if he had a solution for me ...
[Magisk] Syoenth:
What files i must delete on Cyanogenmod based ROM to unroot? I only delete /system/su, is there something else i must delete?
[Magisk] Captain_Throwback:
Hmmm...:rolleyes:
[Magisk] Captain_Throwback:
You mean /system/xbin/su?
[Magisk] EdGe7x:
As requested

Device model: T-mobile Samsung J7(SM-J700T)

Android: 6.0.1

Stock rom: Yes

Additionally, I have flash the stock rom and done factory wipe.

Thank you for your continued work!
[Magisk] qwertyxyz001:
i can't open cache folder. I remove my root access to install magisk

when i flash the magisk saying failed to flash
[Magisk] Syoenth:
Yes
[Magisk] midgarsormr:
Has anyone managed to get synapse to work with this method yet?
[Magisk] Captain_Throwback:
Recovery log, like the linked post says.
[Magisk] Äptiva:
I had to pull the boot image using dd after flashing magisk so that I could rebump it. However upon further searching I came across blastagator's cBump script that can be flashed in recovery. As soon as I get done with blastagator's stock stripped LP I will go back to CM13 and test it further
[Magisk] lancespahr:
Sorry if I've posted repetitively but my issue is lock screen does not work once I've installed Xposed (systemless or official). I can see the power menu and some notifications. Any ideas what the issue could be? :/
[Magisk] r0tati0n:
Hi all :)

My device: Lenovo Tab3 7.

I am getting a error 1 when installint Magisk v14.

Normally this would mean, install a original boot image.

But I already did a clean install with SPFT, Including a Firmware Upgrade, which is supposed to wipe the partition and install it completely new. So the boot image should be original, afterwards I flashed a recovery with this tool and installed Magisk, same error 1.

Help? :(
[Magisk] Didgeridoohan:
There are a few similar reports like that for the Pixel. It's under investigation...

Mi A1 support is a work in progress. It doesn't quite function as the Pixel, even though it's an A/B device.

It's on the to-do list, but will require some time.

---------- Post added at 14:28 ---------- Previous post was at 14:27 ----------

That's not necessarily what error 1 means. It just means that the installation failed... The important part as to why it fails is found in the recovery log.
[Magisk] albeltw:
Hi, I'd like to ask for some help. I have an Xperia Z1 Compact (D5503) with unlocked bootloader and latest stock rom (14.6.A.1.236 Lollipop 5.1.1). I flashed Advanced Kernel v19.0 (3.4.25-lp_mr3-Advanced) and then I flash Magisk from recovery and Magisk Manager apk.

When I open Magisk Manager it does not detect magisk installation saying that there's none installed and notifying me the new version (v14) even though this is the one I installed. I have no modules installed.

Tried rebooting after installation, uninstalling Magisk and installing again, different versions from 12 up to latest beta 14.3 and other suggestions from the troubleshooting thread. I even tried searching this thread but to no result.

There is no magisk log in /cache nor in /data that I can attach. I can't provide recovery log and kernel log as I'm a new member with less than 10 posts. Anyway in my recovery log there are a lot of these:

WARNING: linker: ./magiskboot: unused DT entry: type 0x6ffffffe arg 0xfb8
WARNING: linker: ./magiskboot: unused DT entry: type 0x6fffffff arg 0x1

If I try with a kernel extracted from stock rom and then repacked (through pa_toc or repack kernel) I can install Magisk but can't pass SafetyNet check due to kernel version not supporting mount namespace.
[Magisk] r0tati0n:
Ups,

sorry :(

here is recovery log:

https://pastebin.com/h2zSZ5De
[Magisk] :
Where do i see when mi a1 is supported?
[Magisk] Didgeridoohan:
This is your issue:

! Unable to detect boot image

Try the beta, it might work. Or it might not. If it doesn't work, upload your stock boot image for possible future compatibility.

Keep an eye on the release thread and the changelog.

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

The linker warnings are a Lollipop thing.

If you want to share a recovery log from when it doesn't work, use Pastebin and then post the id here. Sounds like that custom kernel isn't compatible with Magisk.

It's quite unlikely though that you'll be able to get your device to work with MagiskHide. If the Linux kernel is too old to support mount namespace, the custom kernel you're flashing need to have the necessary features backported (and that's not very common).
[Magisk] r0tati0n:
Beta did not work.

I attached the boot.img, which I used for flashing.

Most interesting:

Magisk 13.3 is able to find the boot image, but then has an error.

Could you tell me the difference in the logs?

Log with 14.3 beta installation and 13.3:

https://pastebin.com/nNH6dpHp
[Magisk] albeltw:
Yeah, no matter how much I search, there doesn't seems to be a suitable kernel. Since I got a new XZ1 Compact as primary device, I'm using my old Z1C to try things out. Guess I'll try some other roms with kernel fully compatible with Magisk or just stick with stock rom and use Magisk without MagiskHide.

Thanks a lot for your answer.

Anyway these are the Pastebin IDs just in case:

recovery log: kGijyWeD

kernel log: uZ0K6TbK
[Magisk] andrew2432:
You could get lucky and find a ROM with that kernel included, I did for my galaxy s5
[Magisk] impBerlin:
Re-Stock failed: Magisk boot-loop and flash of stock-boot image

I wanted to start rooting with a virgin S7 Edge (Exynos).

First I installed the Magisk Manager and patched the stock boot image and flashed the patched boot image with Odin --> No boot, stuck in boot splash screen "Samsung blinking"

After I wanted a return to stock boot again, flashed stock boot rom and S-Health app complained that my device is rooted (:confused:) but Magisk wasn't installed

Tried again with the app method of patched boot image but resulted in same boot, returned back by flashing the stock boot image

At first I wanted to keep as stock as possible and didn't used a custom recovery. But this time I used twrp to flash Magisk within twrp with a sort of "Samsung AntiRoot Kit" from highonandroid.com (saw it on youtube) --> didn't helped either

Now maybe my greatest mistake: I took the Magisk BETA and ended up in boot loops --> From here I wanted back to stock boot again and flashed it with Odin

Now I am in a boot loop with my stock boot image and nothing helps.

How I can get back to stock boot OR into a working Magisk root environment.

Until now I didn't lost any data and I don't want to loose data. If I use Magisk Uninstaller in twrp I see that I can't mount /data. So I can't provide any logs in /data for you.
[Magisk] impBerlin:
Magisk without loosing data?

Unfortunately I had to format /data and install SuperSU to get into my stock-rom and was forced to install all my apps again.

Now I found a tutorial how to switch from SuperSU to Magisk and will follow that.

BUT does anybody knew a way for not-rooted Samsung Galaxy S7 to get twrp and Magisk on that phone without loosing data?

Honestly I don't even want a custom recovery like twrp, so only Magisk and root. Any ideas?
[Magisk] storm68:
TWRP is necessary. No TWRP, no magisk and possibly root. It's a must honestly. Keeps you from getting a paper weight.
[Magisk] Sparker0i:
Magisk hide not working for IRCTC rail connect app
[Magisk] janres155:
Anyone experiencing this issue? And any solution?
[Magisk] Didgeridoohan:
No issues here (I just tested the command). OnePlus 3T, OOS 4.5.1 (Android 7.1.1), Magisk v14.3(1437) beta.

Might be device specific...
[Magisk] Ciamabhishek:
Some kind of bug..magisk is not detecting root,after i reboot it applies root..any solution for this?
[Magisk] jenslody:
Did you try the latest beta or do you use 14.0 ?
[Magisk] Ciamabhishek:
I use 14.0
[Magisk] jenslody:
Can you try 14.3 beta.

To get it, it should be enough to switch the update-channel to beta in the MagiskManager-settings.

If it does not work, you can download it from the beta-thread and flash it through the Manager (click on the '+'-sign in the Modules-section and chose the downloaded zip to install).
[Magisk] Ciamabhishek:
Done..n thanks.. hoping it won't do the same thing again!
[Magisk] Didgeridoohan:
If it does start happening again, please try to grab some logs. It might be enough with pulling magisk_debug.log from /data (use adb or reboot to TWRP or whatever custom recovery is available for your device), but a logcat might be useful as well.
[Magisk] Craz Basics:
Sooo, got the USA s7. Locked bootloader however we do have root. I was wondering if anyone could help:

The boot.img patch will trigger secure boot so we can't boot. Anyway to get magisk without the edit OR could we put the boot patch script in init.d so it would run on boot? Or anything else that would work.

Like I said, won't boot if boot.img is modified so it can't flash a new boot.img, it would have to edit the existing one.

Thanks!
[Magisk] yochananmarqos:
First, please don't post the same thing twice (aka bumping) in such a short period. It's bad forum etiquette.

Yes, I've never had dumpsys work with MagiskSU on stock Nougat & Oreo on my Nexus 5X. I receive the same error with most terminal emulators, however with NeoTerm it spits out something different which may yield a clue as to why it's not working:

bash-4.4# dumpsys
dumpsys
CANNOT LINK EXECUTABLE "dumpsys": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
Aborted

[MENTION=4470081]topjohnwu[/MENTION] Any idea about this?

Alternatively, you can use adb from your PC or SecureTask with Tasker. Here's an example Tasker task:

Dumpsys SecureTask (162)
A1: Dump log [ Configuration:dumpsys media.audio_flinger Timeout (Seconds):30 ]
[Magisk] robterza:
android 5.1.1 tv box

[MENTION=4470081]topjohnwu[/MENTION] hi,

i bought a android tv box DVB-S2 / DVB-T2 and as you know, they are getting very common, and maybe they will become a standard for tv. My tv box, mounts an amlogic processor S905 and android 5.1.1, and I saw on the net that many people get the root with Supersu. I would like to root it with Magisk, what version could I use?
[Magisk] azazello22:
Xiaomi mi5, latest Lineage 14 build, Magisk 14.0 installed with 5.4.0 Manager. I can't access the Superuser section of the app, it force closes. Root works fine in most apps, except for greenify (su dialog not showing up, permission automatically denied). Can provide logs if needed.

Inviato dal mio MI 5 utilizzando Tapatalk
[Magisk] Didgeridoohan:
No logs needed. Clear data for the Manager.
[Magisk] DenyDarko:
I've made a search in the thread and I've seen plenty of posts regarding failing safetynet after enabling systemless hosts and not failing right after disabling it.

However I've not found any solution for it.

I'm on H850 v20p (yes, p, just came out a few days ago) but the same behavior is noticed on K and on D.

And Magisk 14.3.

Is there any solution I've missed or..?
[Magisk] ivivaitylin:
Sorry for the questions and thanks for all the help.

I've done most of the things you suggested. Weirdly, if I disable all the magisk modules, safetynet passes and I can use android pay fine, but pay+ still detects root. Each time I try I clear out the app cache and user data, and still no luck, plus the fact that it is still detecting when I would have thought everything should be working is a mystery to me. Unfortunately I lack the programming knowledge to start decompiling messing around with the insides of the app :(

Is there anything else I might be able to do, or should I just give up on it now?
[Magisk] user_null:
Modules aren't showing up after reboot? Nor are they working. Trying to reinstall them doesn't show any errors but they still aren't working.

v14.0 and app v5.4.0
[Magisk] Fif_:
That's odd as Magisk does not modify libunwind nor dumpsys. Libunwind is involved in generating backtraces and throwing exceptions. The error you're getting could be a secondary error that happens when trying to get a backtrace from another error. Do you have a logcat?

Edit: also, if you can get it to work with some terminal emulators, but not others, it points to some environmental differences:

1. Check the environment, compare the output of:

env | sort

in the app that works vs. the same command in the app that doesn't.

2. It could be a mount namespace issue. With the app that doesn't work, try running

su -mm

instead of regular su. That will forcibly put you into the " root" of all mount namespaces. Then try dumpsys again.
[Magisk] Didgeridoohan:
It might also be that something else is detected. USB debugging and developer options enabled might trigger some apps and so on... It might also be that the current implementation of hiding the Manager doesn't fool the app in question (if that's what it's looking for). [MENTION=4470081]topjohnwu[/MENTION] is working on a new way of hiding it that might work better.

Logs? Useful ones might include recovery.log, magisk.log, magisk_debug.log, logcat, etc.
[Magisk] ScottIsMyName:
I posted some information in the beta thread, but I was wondering what's the best way of trying to figure out why I'm getting bootloops on the new Pixel 2 XL?

Since there is no recovery or root available, I don't think there's any logs that get created that I have access to. Is there anything I can try?
[Magisk] nocturnoz:
I tired updating from Magisk V13.0 to V14.0 but the ROM (signature) isn't starting. The device freezes right after the splashscreen.

Maybe it's not yet supported. I've attached the Logfiles. :)
[Magisk] Izzysoft:
[MENTION=4470081]topjohnwu[/MENTION] Saw you've switched to the v2 signing API for Magisk Manager. Could you please keep v1 signing in it additionally? Fdroidserver currently seems unable to deal with "v2 only" signed apps, and I'd like to keep the app up-to-date in my repo :D Also, AFAIK if it's signed "v2 only" it also means "Android 7+ only" – as Android before Nougat can't deal with v2 signing either.

Thanks in advance!
[Magisk] yochananmarqos:
Termux gives the same unknown error as the screenshot the guy I replied to posted. I have tried Material Terminal before as well with the same result. Logcat is attached with attempts from both Termux & NeoTerm.

Termux

$ env | sort
ANDROID_DATA=/data
ANDROID_ROOT=/system
EXTERNAL_STORAGE=/sdcard
HOME=/data/data/com.termux/files/home
LANG=en_US.UTF-8
LD_LIBRARY_PATH=/data/data/com.termux/files/usr/lib
PATH=/data/data/com.termux/files/usr/bin:/data/data/com.termux/files/usr/bin/applets
PREFIX=/data/data/com.termux/files/usr
PS1=$
PWD=/data/data/com.termux/files/home
SHLVL=1
TERM=xterm-256color
TMPDIR=/data/data/com.termux/files/usr/tmp
_=/data/data/com.termux/files/usr/bin/env

NeoTerm

$ env | sort
ANDROID_DATA=/data
ANDROID_ROOT=/system
EXTERNAL_STORAGE=/sdcard
HOME=/data/data/io.neoterm/files/home
LANG=en_US.UTF-8
LD_LIBRARY_PATH=/data/data/io.neoterm/files/usr/lib
LD_PRELOAD=/data/app/io.neoterm-Ot7KoC-kc8qxbVWnRl37JA==/lib/arm64/libnexec.so
PATH=/data/data/io.neoterm/files/usr/bin:/data/data/io.neoterm/files/usr/bin/applets
PS1=$
PWD=/data/data/io.neoterm/files/home
SHLVL=1
TERM=xterm-256color
TMPDIR=/data/data/io.neoterm/files/usr/tmp
_=/data/data/io.neoterm/files/usr/bin/env
__NEOTERM=1
__NEOTERM_ORIGIN_LD_LIBRARY_PATH=null
__NEOTERM_ORIGIN_PATH=/sbin:/system/sbin
[Magisk] Fif_:
Well you didn't send the environment from something that works.

Nevertheless, both emulators modify PATH and more dangerously the LD_ variables.

Can you try:

toybox env -u LD_PRELOAD -u LD_LIBRARY_PATH su

Does that work?

Have you tried with su -mm?

Edit: You can also try:

strace -o dumpsys.out -e open,openat dumpsys

and send the dumpsys.out output.
[Magisk] lucius100:
Does magisk only supported on stock rom?

I tried it on LOS https://xdaforums.com/galaxy-s5/development/rom-lineage-os-samsung-galaxy-s5-lte-t3534283/page115

But it stuck on booting.

I need magisk hide root, it's awesome.
[Magisk] yochananmarqos:
I didn't do what now? :confused:

Termux

# toybox env -u LD_PRELOAD -u LD_LIBRARY_PATH su
oybox env -u LD_PRELOAD -u LD_LIBRARY_PATH su

NeoTerm

# toybox env -u LD_PRELOAD -u LD_LIBRARY_PATH su
toybox env -u LD_PRELOAD -u LD_LIBRARY_PATH su
CANNOT LINK EXECUTABLE "/data/data/io.neoterm/files/usr/bin/bash": library "libandroid-support.so" not found
Aborted

I forgot to mention it made no difference.
[Magisk] Fif_:
No it looks like it's the terminal emulators injecting stuff in PATH and LD_*.

I was asking for the output of "env" on a Terminal or adb session where su works.

Try this one:

toybox env -u LD_PRELOAD -u LD_LIBRARY_PATH PATH=/sbin:/bin:/xbin:/su/bin:/su/xbin:/su/sbin:/system/xbin:/system/sbin:/system/bin:/vendor/bin su -c /system/bin/sh
[Magisk] yochananmarqos:
I'm completely lost now. Didn't I already give you the env output? What are these toybox commands supposed to be doing? Any terminal has su access. I don't have an issue with that. The only command I've come across that does not work is dumpsys.

EDIT: Here's env output from Material Terminal:

# env | sort
env | sort
ANDROID_ASSETS=/system/app
ANDROID_BOOTLOGO=1
ANDROID_DATA=/data
ANDROID_ROOT=/system
ANDROID_STORAGE=/storage
ASEC_MOUNTPOINT=/mnt/asec
BOOTCLASSPATH=/system/framework/core-oj.jar:/system/framework/core-libart.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/legacy-test.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/apache-xml.jar:/system/framework/org.apache.http.legacy.boot.jar:/system/framework/android.hidl.base-V1.0-java.jar:/system/framework/android.hidl.manager-V1.0-java.jar
DOWNLOAD_CACHE=/data/cache
EXTERNAL_STORAGE=/sdcard
HOME=/
HOSTNAME=bullhead
PATH=/sbin:/system/sbin:/system/bin:/system/xbin:/vendor/bin:/vendor/xbin
SHELL=/system/bin/sh
SYSTEMSERVERCLASSPATH=/system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar
TMPDIR=/data/local/tmp
_=/system/bin/env
[Magisk] dilshahdirar:
[IMG="magisk error"]https://imgur.com/a/SkRWK[/IMG]

https://imgur.com/a/SkRWK

[IMG="twrp magisk error"]https://imgur.com/a/HRt9P[/IMG]

https://imgur.com/a/HRt9P

Log :

10-25 07:49:09.372 9028 9028 E Magisk : mount /dev/block/loop2->/dev/magisk_merge failed with 13: Permission denied

I have been trying to solve this error. I cant install any modules because of this.

What i have tried so far

* Magisk 14.0, 14.3

* Flashed Firmware Twice

Device is Lenovo P2 (P2a42)
[Magisk] BocaAnts:
Magisk

Does anyone have Magisk working with FBE?

I have tried about everything. Trying to install on Angler; dont care which Android version.

I can sideload Magisk-v14.3(1437) via TWRP, but then get in endless boot animation mode.

I see alot of posts on this topic, but no resolution.

Any ideas?
[Magisk] Didgeridoohan:
You could try keeping dm-verity and forced encryption when installing Magisk. More on that here:

https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417
[Magisk] BocaAnts:
Thanks

Thanks. That worked.
[Magisk] Fif_:
Sorry, I was replying to another thread about a su problem and I got mixed up between su and dumpsys.

Thanks for the output on Material Terminal. This one doesn't muck with PATH or the LD_ variables.

And dumpsys still does not work in Material Terminal?