yashsingh1/xdaforums huggingface dataset:
[Magisk] Xenomorphys:
Hello, I have a problem with Magisk.

For no reason, he refuses Root access to applications.

I accepted them well ...

I am on HTC 10 under Viper 5.11 and ElementalX.

And the Magisk Hide does not work on my bank apps ...

Thank you all for your help.
[Magisk] Didgeridoohan:
That's all perfectly normal. The Manager does not need to be a system app since one of the major points of Magisk is to keep /system untouched, that would kind of defeat the purpose...

And when updating your ROM, it'll also update the boot image, which will undo the modifications Magisk does to your boot image.

Manually delete the iYTBP module folder under /magisk and reboot. If it still doesn't work, use the Magisk uninstaller zip from the release thread.

Have you tried clearing out root permissions for the affected apps and granting it again? And does MagiskHide work for any app?
[Magisk] DodoGTA:
But, the Magisk installer touches the /system partition to add an addon.d script (if the ROM has addon.d support) which prevents losing Magisk after an ROM update (like LineageOS nightlies)
[Magisk] Didgeridoohan:
True. I keep forgetting about addon.d since I don't use it...

Which would mean that addon.d in [MENTION=8544687]ankush gairola[/MENTION]'s case doesn't work properly. A recovery log from when flashing the nightly and then the Magisk zip might show why.
[Magisk] blackice000:
So on 14.3 on Essential PH-1 NMJ51B STILL Seeing this error over and over in logs... Any idea what to look at?

E Magisk : bind failed with 98: Address already in use

Rick
[Magisk] Syoenth:
Did this work? Because I have the same problem, please help, can't pass SN
[Magisk] Xenomorphys:
Yes, I even reinstalled Magisk and G4M but that does not change anything.

Yes, on TBP, it works. He tells me he does not have root when I select it.
[Magisk] cristianodk:
the error continues
[Magisk] Didgeridoohan:
If you flash the stock boot image you have completely removed Magisk... There are residue files in /data, but they do nothing without the patched boot image.

Have you also flashed the uninstaller zip? If not, do that and then restore the stock boot image. If there still are issues, dirty flash your ROM. If there still are issues, clean flash your ROM.
[Magisk] coolhandz:
Can you hide BusyBox & Root from Samsung Pay? Want to use SPay on my Gear S3.

I am using a Pixel XL on 8.1. I was rooted before flashing 8.1 w/ SuperSU, but haven't tried Magisk yet. I'm hoping the answer is affirmative.
[Magisk] yuri-rus:
Lenovo TAB 2 A7-30 HC Static firmware 5.0 is not installed Magisk 14 via TWRP 2.8.7.0.

I can not patch boot.img. It turns out to install only if you build a boot.img based on the drain, in the apk itself and flash the resulting boot.img through the spflash tool.
[Magisk] Didgeridoohan:
Yes, that's normal. That TWRP version is too old... Update TWRP or you'll have to use the Manager to patch the boot image and then you can flash that through TWRP (like you've already noticed).

After the first install you should be able to update just fine though the Manager.
[Magisk] DodoGTA:
recovery.log?
[Magisk] yuri-rus:
The problem is that for this device I did not find the TWRP more recent version.
[Magisk] Didgeridoohan:
In that case you patch the boot image with the Manager and flash it manually, like I said...
[Magisk] n-j-f:
No Magisk Manager

I've installed Magisk 14.0 on my Samsung S8 and I have root. A titanium popup also says I have Magisk 14.0. However, I cannot find Magisk Manager in the app drawer. I tried to sideload the latest apk but it will not install as it says it conflicts with an existing package with the same name.

Where's the Manager gone?
[Magisk] Sizzlechest:
I have an old Samsung Tab 4 10.1 tablet running Android 5.0.1. SafetyNet check fails with Magisk installed. I followed the guide here: https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417/post73145987#post73145987

I extracted the clean boot.img from the original firmware and flashed it using TWRP 3.x.x.x. I ran a check using SafetyNet Playground and it passed. I flashed Magisk again in TWRP and checked both in Magisk and in SafetyNet Playground and it fails according to both. I installed Root Checker and verified that I do have root. I attempted to hide Root Checker by clicking the checkbox next to it, but it doesn't hold the setting. I don't see any button or option to "set" the app to be hidden. I'm assuming simply checking the box next to the app should enable hiding? The setting does not persist. I don't have BusyBox or Xposed installed. I did a factory reset and got the same result. It's got to be the boot image since flashing the stock boot.img makes the check valid. I don't know what else to try at this point.
[Magisk] DodoGTA:
Magisk log from Magisk Manager?
[Magisk] yuri-rus:
Log attach google link
[Magisk] ShidqyRR:
When i uninstall magisk with uninstaller.zip, always bootloop ? How to uninstall?
[Magisk] Sizzlechest:
Sorry, I posted before I left for work. I couldn't post the log until I got back.

https://pastebin.com/0qt21wHL

I think my kernel is too old. Not surprising since this is Android 5.0.1. Any suggestions?
[Magisk] yochananmarqos:
You'll need to use /system/vendor/media_profiles.xml instead of /vendor/media_profiles.xml as Magisk cannot mount /vendor directly. In case you didn't already know, /system/vendor is a symlink to /vendor. I'm not sure about /product as my devices don't have it, but there may be a symlink in /system to it as well; i.e., /system/product.
[Magisk] ShidqyRR:
--------- beginning of main

I/Magisk ( 314): Magisk v14.0(1400) daemon started

I/Magisk ( 314): ** post-fs mode running

I/Magisk ( 314): ** post-fs-data mode running

I/Magisk ( 314): * Mounting mirrors

I/Magisk ( 314): mount: /dev/block/bootdevice/by-name/system -> /dev/magisk/mirror/system

I/Magisk ( 314): link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor

I/Magisk ( 314): bind_mount: /dev/magisk/mirror/bin

I/Magisk ( 314): * Mounting /data/magisk.img

I/Magisk ( 314): * Running post-fs-data.d scripts

I/Magisk ( 314): * Running module post-fs-data scripts

I/Magisk ( 314): xiaomi-safetynet-fix: exec [post-fs-data.sh]

I/Magisk ( 334): *** [Universal Hide] Version: v2 Beta 5

I/Magisk ( 338): *** [Universal Hide] Changing build fingerprint value

I/Magisk ( 341): *** [Universal Hide] Hiding dangerous props

I/Magisk ( 314): * Loading modules

I/Magisk ( 314): xiaomi-safetynet-fix: constructing magic mount structure

I/Magisk ( 314): bind_mount: /system/xbin

I/Magisk ( 314): bind_mount: /system/xbin/usnf

I/Magisk ( 314): bind_mount: /system/xbin/antradio_app

I/Magisk ( 314): bind_mount: /system/xbin/busybox

I/Magisk ( 314): bind_mount: /system/xbin/dexdump

I/Magisk ( 314): bind_mount: /system/xbin/miuioneshots

I/Magisk ( 314): bind_mount: /system/xbin/shelld

I/Magisk ( 314): * Starting MagiskHide

I/Magisk ( 314): hide_utils: Hiding sensitive props

I/Magisk ( 354): *** [Universal Hide] Checking information

I/Magisk ( 314): hide_list: [com.google.android.gms.unstable]

I/Magisk ( 314): proc_monitor: init ns=mnt:[4026531840]

--------- beginning of system

I/Magisk ( 314): ** late_start service mode running

I/Magisk ( 314): * Running service.d scripts

I/Magisk ( 314): * Running module service scripts

I/Magisk ( 5785): *** [Universal Hide] Moving and re-linking /sbin binaries

I/Magisk ( 5803): *** [Universal Hide] Starting monitoring process

I/Magisk ( 8513): *** [Universal Hide] Unmounting Magisk mount points:

I/Magisk ( 8518): [0,8477,10013,com.google.android.gms.unstable,service,com.google.android.gms/.droidguard.DroidGuardService]

I/Magisk (11374): *** [Universal Hide] Unmounting Magisk mount points:

I/Magisk (11376): [0,11337,10013,com.google.android.gms.unstable,service,com.google.android.gms/.droidguard.DroidGuardService]

I/Magisk (12460): *** [Universal Hide] Unmounting Magisk mount points:

I/Magisk (12462): [0,12423,10013,com.google.android.gms.unstable,service,com.google.android.gms/.droidguard.DroidGuardService]

I/Magisk (23863): *** [Universal Hide] Unmounting Magisk mount points:

I/Magisk (23864): [0,23829,10013,com.google.android.gms.unstable,service,com.google.android.gms/.droidguard.DroidGuardService]

---------- Post added at 03:25 AM ---------- Previous post was at 03:23 AM ----------

Hello can help me
[Magisk] Pafzedog:
Hello, sorry to double post but, multirom thread is not very active, and my problem is related to both Magisk and Multirom :
[Magisk] DodoGTA:
Your kernel is too old
[Magisk] anasgeo:
Hello to all . I am using a Samsung note n9005 with resurrection remix 5.8.5 vidwhal. I am newbie with magisk but so on it was working great with all e-banking apps I have working also great. Yesterday one of the apps I use made an update and from this time on it can detect the rooted phone so it stops working. I must say that I have enabled magisk hide and also checked the app in the hide menu .

I am using 14.5 but when it start doing this I was in 14.0 , that's why I installed 14.5 in case to solve this
[Magisk] DodoGTA:
It looks like that Magisk can't detect the boot image location (Which in this case is /dev/bootimg)
[Magisk] Didgeridoohan:
Try to uninstall the app through adb:

adb uninstall com.topjohnwu.magisk

After that you might be able to install the app again.

Since it only seems to happen on G4M I'd try running Greenify normally to see if it's the app itself causing issues.

About root hiding, see my reply to anasgeo below.

Also restore your stock boot image after flashing the zip.

Have you also tried hiding the Manager? It's in the Manager settings... After doing that you might also have to clear data for the app since some apps "remember" detecting root.
[Magisk] shoey63:
Sony stock kernels are in elf format and can't be patched. However some custom kernels follow the correct android boot image protocol and can be patched. Others still use the two stage boot process (eg: CM, Omni) and they can't be patched either. This explains the various successes and failures.

Welcome to the wonderful world of Sony. [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] GFXi0N:
Quick question. With a lot of Android 7 roms around the corner, I'd like to know if this is compatible with that system version. Thanks!
[Magisk] Äptiva:
Update on my AT&T G2:

Got it working with stock-ish rom and dorimanx kernel. Got SELinux working properly with a workaround.

AP and PoGo both working.

Will verify process and edit this post with instructions. Mind you this was only tested with one kernel and rom. If I had more stock LP based kernel and rom selection I could verify more of these and perfect the method.
[Magisk] quertiy:
Hi,

I have a nexus 6p. Complete stock.

Steps I have followed.

1. unlock bootloader

2. install twrp latest version

3. install magisk

4. install phh's root

Everything worked as expected.

Today I recieved an OTA and tried to install it but it failed. I'm attaching the details.. Can you help?
[Magisk] :
Just to confirm, this won't work on Xperia 5.1.1 stock roms right?
[Magisk] geek85:
this is because of TWRP, not magisk.

it has changed the fingerprint of the phone and the OTA do not recognize the phone.
[Magisk] McDope:
Any recommendation on which kernel to use (edit: for Z3 / D6603)?
[Magisk] quertiy:
Magisk / phh work with the default recovery right?

So the solution would be to flash the stock recovery of the build I'm currently on?

I can't find my build (nrd90m) in https://developers.google.com/android/nexus/images
[Magisk] McDope:
Z3 / D6603
[Magisk] -Happy Feet-:
Read OP. recommend is stock kernel. With the Elitekernel V3 I have reboots, or no working Magisk Mod. Why ever.
[Magisk] teddy0209:
To be able to take an ota, yes you should have the stock recovery. Aside from the unmodified system. Mounting system as rw in twrp also prevents you from taking an ota.

---------- Post added at 10:07 AM ---------- Previous post was at 10:03 AM ----------

Sony has kernel.elf as stock so it won't work. Read the previous posts, they got it working on some sony devices, you might need another kernel/boot.img...
[Magisk] -Happy Feet-:
The Advanced Stock Kernel works good.
[Magisk] quertiy:
I understand but what recovery should I flash?

I'm on build NRD90M and I can't find it. Am I ok with flashing the recovery from NRD90U?
[Magisk] teddy0209:
You could try, works for me if I use the recovery inlcuded in the ota update...
[Magisk] Artim_96:
It does... But it's not guaranteed to work with every ROM, it depends on how much they where changed
[Magisk] yvgamer94:
Successfully installed on my redmi note 2 running Miui 8.0.1.0 Global Stable version but can't seem to toggle the root enable/disable. Really odd and I don't know how to fix it.
[Magisk] quertiy:
After 3 seconds it just showed .. ERROR.

Anybody knows where I can find the NRD90M recovery.img?..
[Magisk] shoey63:
Elite or Advanced stock both should work. You need stock /system I think. (ie: no recroot).

I personally am using Latest MM concept with my own (as yet unreleased) boot.img. Seems to work fine so far.
[Magisk] bardx:
Root toggle doesn't work here too

Same problem here. When I try to toggle root, the toggle immediately switches back. I found a page where someone says that it happens when you haven't unrooted your phone properly. I guess I made the right procedure to unroot but I still have this issue. Could it be the rom I'm starting from? I don't have a stock rom but a CyanogenMOD 13 (that has built-in root). Should I use some special procedure to unroot it?
[Magisk] anasgeo:
[MENTION=4667597]Didgeridoohan[/MENTION] You mean to enable " hide " in settings ? Yes this is enabled from itself . I will try to uninstall the app
[Magisk] Didgeridoohan:
No. I mean the option called "Hide Magisk Manager". That will repackage the Manager under a random name so that apps looking for the Manager no longer can detect it.
[Magisk] yuri-rus:
Is this problem in twrp?
[Magisk] DodoGTA:
Obviously no

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

Have you applied any Substratum (also known as LibreSubstratum and Bucket on F-Droid) overlays to Magisk Manager?
[Magisk] Bleuzen:
Can't update Manager App

The manager app displays an update (v5.4.3), but when I press Install, nothing happens.

---------- Post added at 01:33 PM ---------- Previous post was at 01:17 PM ----------

I installed the apk manually for now.

But still, if I reinstall Magisk, that comes with Manager App 5.4.2, I can't update to 5.4.3 from within the app.
[Magisk] HalFBlooDPrincE:
Check that the downloads app in phone is working or not and also check that it have storage permissions properly.
[Magisk] Bleuzen:
The Manager App didn't has storage permissions.

But it also never asked for it. So maybe it forgot it somehow? If so, this should get fixed.
[Magisk] rufik:
Thanks a lot, /system/vendor is symlink to /vendor indeed.

But /product partition has no symlink there unfortunately :(
[Magisk] HalFBlooDPrincE:
Goto app info - magisk manager - permissions and grant storage permissions. This worked for many users.

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

3g/4g optiimizer cant detect root. Please help.
[Magisk] yuri-rus:
How can I fix this?
[Magisk] MOVZX:
I'm not using Substratum.
[Magisk] ShaunSmit:
Unable to detect boot image

Having the same problem with S3 Mini (Golden)

TWRP ver 3.1.1-1. / TWRP ver 2.8.1.0*

los13.0_golden.nova.20170328.

Please see attached Jpg

* Originally used 3.1.1-1, then rolled back to 2.8.1.0, and the same problem existed.
[Magisk] ShaunSmit:
I am able to install Magisk v12.0 Boot image patcher. :confused:
[Magisk] DodoGTA:
Quoting my own post:
[Magisk] wserfer:
Where can I write a suggestion? In SuperSU there is an opportunity to set the password on the root request. I would like to see such function and here.
[Magisk] jenslody:
It's already fixed in recent MagiskManager.
[Magisk] KaMyKaSii:
This boot.img problem is common in MediaTek devices with by-num partition layout. Although the boot partition path is /dev/bootimg you will not be able to backup/flash with the DD command for example. TWRP apparently has a workahound for that. In the post below you have a bit of information when I talked to Chainfire about bringing support for by-num devices in FlashFire

https://xdaforums.com/general/paid-software/flashfire-t3075433/post66143356
[Magisk] jenslody:
5.4.3 is not a Magisk, but aMgaiskManager version.

I use microG with Magisk and do not have (SafetyNet) problems, at least it works fine with "SafetyNet Helper Sample". Checking it from inside MagiskManager does not work, because microG's PlayService version is too old.

I use the internal (not yet published) beta, but I never had any SafetyNet issues.

I'm on unofficial GZR validus for J% and have to use a fake fingerprint, because the rom does not pass cts otherwise (even without Magisk).
[Magisk] dark_hawk:
Hello,

I flashed Magisk on a Sony Xperia Z3 phone with locked bootloader "Didn't know it was only available for unlocked bootloaders".

Now the phone won't start, just the red led flashing.

Holding volume up and power enters flashmode and fastboot.

What can I do to recover the phone?

I tried flashing the stock boot.img file through flashtools but it's not working.

Thanks.

Edit: I solved it.

For future reference and for any one having this problem. You need to obtain an FTF file of the same base ROM you are running, and using flashtool you need to flash only the kernel, deselect everything else, the phone should boot.
[Magisk] Bleuzen:
Yes, thats what I did. Now it works. Thanks.

---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------

Ok, great :D
[Magisk] koocha:
Anyone else facing the issue where Magisk manager closes instantly on any version over 5.4.0? Tried allowing the storage permission and wiping data.

OnePlus 5 oxygen os 4.5.14
[Magisk] ShaunSmit:
Have found a solution to the problem, I found that Magisk-v14.2(1420).zip has no issues with finding the boot image, and installed without any of the above problems.

Thanks to all who assisted
[Magisk] Xenomorphys:
No, it's not just G4M, it's on VenomTweak and VenomPie.

I tried to reset my not worked.

And I do not find the option.

It's in the options of Magisk?
[Magisk] adri_360:
I've a issue with Magisk and App2SD. When I mount second partition safetynet not pass and if I unmount second partition safetynet pass.

Any knows a solution?
[Magisk] Lilnib:
Lost modules

When I attempted to install a module, and rebooted to flash it, all the modules I had previously installed, including the new one, disappeared and I am unable to install new ones.

After a few searches I found that this is most likely due to me installing busybox.

People have solved this issue by reflashing magisk through TWRP, and my question is, is there a way to fix this issue that doesn't make me lose the data I have on my phone?

EDIT: Removed busybox, used the magisk uninstaller, reinstalled magisk and everything is working. For about two minutes

Until I eventually reboot to finish installing a module. All downloaded modules are lost and I am unable to add new ones, SafetyNet ctsProfile & basicintegrity is now false.

What am I missing?! Why cant I install modules?

On a HTC U11
[Magisk] Didgeridoohan:
Do you mean resetting superuser requests? In the superuser tab of the Magisk Manager you can click on the app that has been granted root access and then delete it. Try that is you haven't already....

Your missing the all-important step of providing logs. Installation log, Magisk log and Magisk debug log are a few useful ones.
[Magisk] Lilnib:
Could not find all the aforementioned logs, but here's the Magisk log.

Might be worth mentioning that all the .zips for the modules are still in the MagiskManager folder, they just seem to not have been installed?

Also that it has been working for a good 6 hours before I started having issues, have not touched anything permission wise other than installing busybox.

--------- beginning of main
I( 705: 705) Magisk v14.0(1400) daemon started
I( 705: 709) ** post-fs mode running
--------- beginning of system
I( 705: 1088) ** post-fs-data mode running
I( 705: 1088) * Mounting mirrors
I( 705: 1088) mount: /dev/block/bootdevice/by-name/system -> /dev/magisk/mirror/system
I( 705: 1088) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor
I( 705: 1088) bind_mount: /dev/magisk/mirror/bin
I( 705: 1088) Resize /data/magisk.img to 128M
I( 705: 1088) Upgrade module: viper4android
I( 705: 1088) Upgrade module: iYTBP-Vanced-black-Magisk-Repo
I( 705: 1088) Upgrade module: EmojiOne-systemless
I( 705: 1088) Upgrade module: max-resolution-youtube
I( 705: 1088) Upgrade module: unifiedhostsadblock
E( 705: 1088) sendfile failed with 2: No such file or directory
I( 705: 1280) ** late_start service mode running
I( 705: 1280) * Running service.d scripts
I( 705: 1280) * Running module service scripts
E( 705:10650) sqlite3_exec: database is locked
[Magisk] Fif_:
Try clearing data for Magisk Manager in Settings > Apps > Magisk Manager > Storage.
[Magisk] VincentJoshuaET:
Can I use Magisk to patch the stock kernel? I don't want to install root, I just want to push some files into /system (Google Dialer and Lens). That won't trip SafetyNet, right?
[Magisk] daddylonglegs:
I can't get Magisk to work on my Pixel. As a matter of fact, I can't even use my phone after flashing it.

I flashed Magisk-v14.5(1456).zip in TWRP. Now every time I boot my phone I get an error that says "system ui application has stopped" and I can't do anything on my phone.

Does anybody know why this is or how to fix it? I am on Oreo 8.1 (official) on my Pixel. Thank you
[Magisk] Didgeridoohan:
Looks like it could be a corrupt Magisk image, or something along those lines... There are a few ways to fix this. Easiest might be to manually remove the modules (delete the module folder under /magisk) and reboot or reinstall Magisk.

If you patch the stock boot image with Magisk, you will have installed root... Ta-dah! :p

If you just want to muck about in /system you could also just fastboot boot TWRP (or install) and use adb push.
[Magisk] tag68:
You have the possibility to give root access, but who says you ever grant it to anyone? And it won't modify system.

But it modifies system, for me the question looked like that should be avoided in the idea of Magisk "do not touch system".
[Magisk] koocha:
Thanks for that, but as I already mentioned in my post, I've tried that.

Tried upgrading, tried a fresh install, tried wiping data, tried allowing storage...
[Magisk] shooreek:
Hello!

I tried to find description of issue and solution I faced, but witout any seccess. May be someone can help.

I've got Nextbit Robin with ParanoidAndriod 7.3.1 and Magisk 5.4.3 installed. Everything works fine except Android Pay. It allows me to attach cards, but when I put my phone close to the therminal in a supermarket nothing happens. I tried to install app from Tinkoff bank that also allowes to pay with beam, but the result is the same.

It looks like android beam is switched off, but it's on. Beam also works fine when I share information between other phones.

It worked good on Stock ROM anf Lineage OS 14.1.

Any suggestions?

Thanks in advance!

[IMG="PA 7.3.1"]http://i.yapx.ru/j2L7.jpg[/IMG]

[IMG="Magisk SafetyNet"]http://i.yapx.ru/j2L5.jpg[/IMG]

[IMG="Android Pay"]http://i.yapx.ru/j2L6.jpg[/IMG]
[Magisk] DodoGTA:
No Magisk installed = No Magic Mount
[Magisk] Xenomorphys:
Yes, I have already revoked the authorization and accept the request. But it does not change anything
[Magisk] daddylonglegs:
Is there a different guide for installing Magisk on a Pixel? I have been trying for over 10 hours now. Any advice?
[Magisk] Didgeridoohan:
The question was about

installing

root and

pushing

files to /system... That's what I gave answers to... :D

But yes, both valid points and the only question is what [MENTION=7515910]VincentJoshuaET[/MENTION] actually wants. You can use Magisk solely for the systemless modifications, but root will still be installed wether you grant superuser access to any apps or not.

You could start by giving details as to what you've already done, what's not working and post logs. Logs are nice... I like logs...