yashsingh1/xdaforums huggingface dataset:
[Magisk] DanielF50:
Sorry if this has been mentioned before, but I couldn't find anything on here - Is anyone else having issues with 7.1.1 and phh's SU (r266-2)? (Nexus 6P, MegaPixel6P ROM)

Magisk was working perfectly for a couple of hours but now I keep losing root and it's driving me crazy - once root is lost, I have to re-flash my original boot.img, my kernel then magisk & phh's su to get it back.

Also having issues with a couple of modules - setDPI (just doesn't work at all), v4a ('no driver installed') & appsystemizer 1.3 (again, doesn't do anything) - maybe it's an issue with magisk.
[Magisk] Didgeridoohan:
This sounds like it could be the Magisk Hide root bug. If you have Magisk Hide enabled, try disabling it and see if there's any difference. It's a known bug and being worked on.

If you're talking about SetDPI from the Module Collection thread it won't work anymore. It's a cache module and those were removed in v9. See the Official announcement thread for details.

No idea about those other modules.
[Magisk] ammar18:
did you install the apk from magisk manager (tap the module [not download] and press that question mark icon)?
[Magisk] DanielF50:
Thanks, I do in-fact have that enabled so that's probably the issue. I'll just have to wait that one out then, thank you for the info - I couldn't find any reason why it should be losing root at all. I've left it alone now and seems to be working fine currently :)

I just read that and came to edit my post but saw that you'd already replied, thanks. I'm just going to have to adjust my screen density with 'wm density' then just reset it every time I want to use Pay/PoGo.

Thank you, that was the ticket! Last time I used V4A with Magisk (v6) I had to flash topjohnwu's zip & another to enable deep_buffer to work on the 6P so assumed the method was the same, apparently not - ignorance is bliss :o
[Magisk] immi803:
New to magisk

All Mount points created right? Can someone guide please? See screenshot
[Magisk] immi803:
Also see this log if required
[Magisk] oreo27:
Cool. I suppose I can test it there. I actually just made the edit manually but it didn't enable the navbar as I had hoped. Perhaps MIUI is missing some resources that need to be added to the firmware.

Oh. Thanks for pointing that out. This is shell scripting, correct? Is there a reference for the syntax which I can check?

Thanks for all the responses. Much appreciated.
[Magisk] culiacanazo:
Dude, I've read all the posts that follow yours and even tho it's been answered to some extent, I'd like to share my share: I'm AICPing it on a T-mo S5, also 7.1.1, and what has worked for me (I've never had a problem) is flash magisk, then phh's, then kernel... And, your rom being unbeknownst to me, the following could help, but then again.... V4A the only way I've been able to make it work in Nougat, is downloading the "dark" edition from the module thread, flashing it, selinux permissive, and NOT updating from the module manager, go figure!

Hope i have helped

Oh and by the way, my hide magisk is enabled
[Magisk] UltraM8:
How can i resize /magisk partition? My test module is almost a 1gb size, when i zip it TWRP errors 1.
[Magisk] Hossamd:
Hello,

I am having the same issue on my Google Pixel XL. I have tried V7, V8, V9 all with the same error.

! Failed: /system could not be mounted!

Can someone please help?

Thanks!!
[Magisk] UltraM8:
Add mount system by adding this to the top of the script:

unmount /system
mount / system
[Magisk] Hossamd:
Thank you, but I do install this via the zip file on TWRP. Which script file do I need to edit?

---------- Post added at 08:08 PM ---------- Previous post was at 08:08 PM ----------

Thank you, but I do install this via the zip file on TWRP. Which script file do I need to edit?
[Magisk] UltraM8:
So i cleaned my zip, 40mb now - so it should flash in /magisk, but I still get "error 1" in TWRP.
[Magisk] Didgeridoohan:
No need to use wm density. The setprop tool works perfectly with changing density.
[Magisk] UltraM8:
Stuck at boot with this. Installer script should be ok now, but i can't boot. Can someone take a look at mine mistakes?

https://drive.google.com/open?id=0BxuowmOLOTG1bHZWQU05aDc5WXM
[Magisk] immi803:
No one ready to guide? Newbie to something is so bad :eek:
[Magisk] Artim_96:
Then probably you did something wrong. I already started to wonder since I thought the image size is set dynamically.

What does the log say before the error 1?
[Magisk] Hossamd:
Found out what the issue is and I don 't know how to fix it :(

The script that you mentioned does indeed mount /system, but it fails to find /system/build.prop because it does not exist in that location.

The correct location of that file is /system/system/build.prop for some reason. What should I do?

Thanks!!
[Magisk] DanielF50:
I've found that it actually doesn't trigger SafetyNet (or so says SN helper) and I've seen no downsides so far, so no complaints here - I'm going to attempt to use Pay tomorrow! If it doesn't work, I'll keep that in mind and switch to a setprop setup though, thanks :)
[Magisk] UltraM8:
Ok i fixed my setup, but now another qusetion - how to debug /magisk linked system? cause it seems su.d still better be placed in /su
[Magisk] chudy_85:
I move mahisk manager and phhs superuser 2.0.9 beta to system/app and I don't lose very long my root and magisk work to
[Magisk] DanielF50:
Thanks, I read that you have to flash ROM+Kernel first though as magisk modifies the ramdisk/boot image, so that's the way I did it, though I did flash in that order before I read that info though and it didn't help - the ROM I'm flashing is basically stock pixel xl software, so it shouldn't make much difference to be honest.

I got Viper working by flashing the official magisk zip, then hitting the "?" to download the apk as suggested and that worked perfectly, so I'll be using that until someone can modify the ARISE installer to install via Magisk! :laugh:

If I switch off magisk hide and reboot, then switch on and reboot it fixes my 'su binaries' problem, so it's not that much of a problem now anyway, but thanks! :)
[Magisk] yochananmarqos:
To save you from rebooting twice, just reflash Magisk & the phh superuser module.
[Magisk] oreo27:
Edit:

Edit - I think the problem lies with MIUI itself. I edited the build.prop manually and changed the line:

qemu.hw.mainkeys=0

However, upon inputting the terminal command:

getrprop qemu.hw.mainkeys

still returns with:

1

I believe that the problem lies not within Magisk but with MIUI itself.

Alright. So I've tried fixing it thanks to your suggestions.

post-fs-data.sh:

/data/magisk/resetprop qemu.hw.mainkeys 0

Terminal Emulator Command:

getprop qemu.hw.mainkeys

Returns with:

1

Maybe MIUI is not using a standard build.prop or something? Have their been devices which don't utilize the standard build.prop?
[Magisk] MBariya:
Check your zip file.

First no need to use Replace in config.su if you have system folder in zip file.

You can't create dir or file in /system/ magisk will remove that. So you have get work around for su.d.

Your script for postfs-data is for older version, from magiskv9 onwards us /data/magisk/resetprop instead setprop.
[Magisk] Rhoban:
Viper4Android can be installed in system mode too, SafetyNet doesn't care about it.

What exactly is it that you need?
[Magisk] MBariya:
[MENTION=4863028]oreo27[/MENTION]

Check PM.
[Magisk] MMFreax:
Good Morning

Is under Android N Xposed working at Moment. The Download is no Magisk Modul for Install.

Gesendet von meinem Pixel XL mit Tapatalk
[Magisk] culiacanazo:
No magisk module = no xposed API 24/25
[Magisk] Artim_96:
Why? To check if they are right is senseless. Either it works or it doesn't. If the latter is the case, make a proper bug report
[Magisk] UltraM8:
Ok. I made lots of fixes, but anyways how do i know which files catched up, which not? For example mixer_paths are not working syslessly.

How do i debug, that sysless policy. configs, for example are working?
[Magisk] Biz92k:
I can't find it anywhere... Is magisk compatible with cm14.1? I guess it is, but just to be sure!
[Magisk] Artim_96:
1. It is

2. Use search function
[Magisk] 127cwho:
on my htc one m9, cyanogenmod 13, no matter which version of magisk i flash, it will bootloop.
[Magisk] italia0101:
I know we're fighting a losing battle with root and Android Pay , but at the moment its actually working with magisk v9 :) . just wondering which modules break it ?
[Magisk] rignfool:
You would need to know some values or the modified date of the original file... Then after boot... Check the contents of the replaced file... Or the modified date... It will have changed...

Also... You do have an 'auto_mount' file in your magisk mod directory... Right?
[Magisk] UltraM8:
Yep, automount running. So i go /system/*replaced file* & check it's data right?
[Magisk] rignfool:
I replace a couple of files in /system/etc/

They are .conf files for V4A... And a thermal throttle config file device specific... They replace no problem... And I built the modules on device
[Magisk] UltraM8:
Here is my module

I'm having problems with booting. I made changes for Mgskv9 - & now i can't boot up, i guess i messed up post-fs-data script)

But the main thing is - what stuff can be executed at post-fs-data? I have several switchers, that were previously loaded by /su - can i place them in postfs-data?
[Magisk] rignfool:
Oh... Uhhh...

I think you went over my head... Resetprop questions... I just 'flash the mod' with those...

See if you can boot without executing the post-fs-data.sh

I'm a little skeptical of some of the places you're putting stuff... Like lib and lib64... And usr... Dunno if those are places magisk can touch...

Magisk can't replace .jar files... That's what keeps ARISE from being one
[Magisk] UltraM8:
I don't need jar) I have to fix resetprop stuff now
[Magisk] putridfoetus:
I've had the same trouble you're having with audio mods. Viper/Atmos in my case. The problem is either of (or both) 2 things: adding files into /system/bin and /system/lib at the same time, or having a bunch of properties set in post-fs-data.sh that, without magisk, would normally be added to build.prop.

When cache modules were still supported (v6 is the last version my Viper/Atmos mod worked on), you could just replace the build.prop, but obviously we can't do that anymore. V7 and later somehow killed any really heavy mods like yours and mine.

Pretty sure these are known issues, and magisk is still in its infancy, so we'll just have to wait until these issues are addressed.
[Magisk] UltraM8:
Well, my previous build is cache one - & it installs perfectly. But the latest v9 causing bootloop. Even without "post-fs" files (i got scripts running from /su)
[Magisk] laggardkernel:
Mounting binaries with v7-v9 will cause a boot stuck. Don't try it.

Setting props works well now with the help of resetprop. I recommend you use resetprop in service.sh with phh superuser. Yes, phh's superuser not chainfire's SuperSU. If you're using chainfire's SuperSU, property settings will cause su loss.

In fact, resetprop in post-fs-data will also work, but from the magisk.log, it causes a log overlap between post-fs-data mode and service mode, which means when service mode starts the post-fs-data mode does not complete yet. I guess setting properties is time-consuming.

---------- Post added at 05:36 PM ---------- Previous post was at 05:32 PM ----------

There is binary files in your mod. All mods with binary files will cause boot stuck after v6.
[Magisk] UltraM8:
Is this the major issue? maybe i can mount it /su

But the official v9 says
[Magisk] laggardkernel:
Yes, it must be the binaries. And v9 doesn't fix mounting binary files. This is a logical oversight in the mechanism of Magisk. I tested this with copying an existing binary file as Magisk model. Resulted in boot stuck.

If you really need mounting binaries, don't put them in the /Magisk/$MODID/system folder. I mean just don't let binaries to be mounted automatically since this is a logical oversight during the dummy file cloning process. Try to mount the files manually, like how Xposed does. Because you have to give a mounting position for the file to be mounted, mounting new binary directly won't succeed. Create a folder, let's say /magisk/$MODID/bin_bind, then copy all files under /system/bin to /magisk/$MODID/bin_bind. After this, mount /magisk/$MODID/bin_bind back to /system/bin. Maybe this will work. Oh, Don't forget the permissions.

Note: The method works with xbin folder, I haven't test it with bin folder.
[Magisk] UltraM8:
Can u send me this xbin mount script?
[Magisk] TBas:
Is it just me?

Hi guys, just a question...yesterday i installed Magisk v9, phh root and Xposed latest version. Until now everything worked fine...but now, and i dont know why, Magisk gives me this message "NO ROOT ACCESS, FUNCTIONALITY LIMITED"...even FB and Xposed dont work anymore, even the Root Checker App doesnt recognize my root anymore..

Any fix? Any help?

Thank u guys.
[Magisk] Captain_Throwback:
Did you searching the thread before posting this question? "Search before posting" is XDA Rule #1, you know...:rolleyes:

P.S. Try rebooting your device.
[Magisk] TBas:
I know man, i searched and i just found "try rebooting your device" and "try removing any Greenify-like module or app"...these 2 tricks dont work with me man..:rolleyes:
[Magisk] Didgeridoohan:
I don't know what you searched for, but searching this thread for "no root" or "lost root" shows quite a few posts mentioning the issue... (although the Greenify thingy was a new one for me, can't recall anyone mentioning that)

And what do you mean when you say that rebooting doesn't work? Does root not return at all, or does it keep disappearing after a while? Details always help...

And lastly: do you have Magisk Hide enabled?
[Magisk] TBas:
Root doesnt return at all...and Magisk Hide is disabled when Magisk cant find your root..
[Magisk] Didgeridoohan:
Ok... But you did have Magisk Hide enabled? You should probably do some more searching and reading. This is a known problem and has been discussed numerous times.
[Magisk] DanielF50:
Even ARISE V4A? I would have thought all of the additional files would trigger it.

Thanks, this helped a couple of times today!

On the plus side, I used Android Pay for the first time today and it worked flawlessly, fantastic! :D
[Magisk] laggardkernel:
https://github.com/laggardkernel/phh-superuser/blob/master/common/post-fs-data.sh#L47-L58

https://github.com/topjohnwu/Magisk/blob/master/scripts/magic_mask.sh#L416-L424

Use "cp" instead of "ln" since /system/bin will be replaced in your case.
[Magisk] culiacanazo:
As didgeridoohan mentioned, details help ppl help others... For example, if i knew you to be on a certain device (that i own) and certain Android version (that i would run) i could pinpoint you to a solution... As of know, we have nothing.

To be more thorough, info such as device, android version, what you have flashed that would be conflicting (i.e. SuperSU prior to phh's, kernel, xposed's details, selinux state, Knox if applicable, magisk's details)... etc is what we need.

Sometimes they're neatly packaged in an elusive "thing" they like to call "logs"
[Magisk] Rhoban:
I'm currently using Deuteronomy 2.3.3 and I'm passing SafetyNet. I mean, can play PokÃ©mon GO, don't know and don't care about Android Pay.

I think SafetyNet only cares about root, Xposed, and possibly selinux and bootloader state.
[Magisk] IzaacJ:
Been a while since I tried to install Magisk on my Lenovo Tab3-710F, but still unable to find the boot image. :(

Info from the recovery log is found below.

Magisk installation:

Installing zip file '/external_sd/Magisk-v9.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /external_sd/Magisk-v9.zip
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: arm/bootimgtools
inflating: arm/busybox
inflating: arm/magiskhide
inflating: arm/resetprop
inflating: arm/sepolicy-inject
inflating: arm64/bootimgtools
inflating: arm64/busybox
inflating: arm64/magiskhide
inflating: arm64/resetprop
inflating: arm64/sepolicy-inject
inflating: chromeos/futility
inflating: chromeos/kernel.keyblock
inflating: chromeos/kernel_data_key.vbprivk
inflating: common/custom_ramdisk_patch.sh
inflating: common/file_contexts_image
inflating: common/init.magisk.rc
inflating: common/magic_mask.sh
inflating: common/magiskhide/add
inflating: common/magiskhide/list
inflating: common/magiskhide/rm
inflating: x64/bootimgtools
inflating: x64/busybox
inflating: x64/magiskhide
inflating: x64/resetprop
inflating: x64/sepolicy-inject
inflating: x86/bootimgtools
inflating: x86/busybox
inflating: x86/magiskhide
inflating: x86/resetprop
inflating: x86/sepolicy-inject
*****************************
Magisk v9 Boot Image Patcher
*****************************
- Mounting /system(ro), /cache, /data
- Device platform: arm
chmod: /futility: No such file or directory
sh: missing ]
! Unable to detect boot image
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
Error installing zip file '/external_sd/Magisk-v9.zip'
Updating partition details...
I:Data backup size is 4031MB, free: 487MB.
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
I:Unable to mount '/usbotg'
I:Actual block device: '', current file system: 'auto'
...done
I:Set page: 'flash_done'
I:operation_end - status=1

And information about the boot partition:

/boot | /dev/bootimg | Size: 16MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/bootimg
Display_Name: Boot/Kernel [boot]
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot/Kernel [boot]
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

Attaching the full recovery log for those interested in seeing more of it.
[Magisk] Didgeridoohan:
I don't think there's been any updates on that part. Did phhusson manage to solve it? You could open an issue on github and provide your boot image for troubleshooting... Also, does other boot image mods succeed, like Chainfire's SuperSU?
[Magisk] Fild5x:
Ok. However, even after installing it I still cannot see it in applications. Do I still need to install the APK version?
[Magisk] TubbyStubby:
i downloaded phh's root for magisk from downloads in magisk manager it said enable to flash, flash it manually with custom recovery. so i tried to flash it with cwm, it goes on without any error but when i restart my phone and open magisk i find that my phone is not rooted. And yeah root checker says root not installed properly. what to do?

using Galaxy S4(GT-I9500) running lollipop.
[Magisk] MBariya:
Yes you still need to install V4A apk file. Module is just for drivers installation
[Magisk] italia0101:
I can't seem to mount the magisk.img to /magisk in twrp . any help ?

I'm putting this " mount /data/magisk.img /magisk

im getting this error ; mounting /dev/block/loop0 on /magisk failed : no such file or directory
[Magisk] Rhoban:
Yes. The Magisk module only installs the driver, the app is still needed to control it (turn it on/off and other stuff).

---------- Post added at 03:52 PM ---------- Previous post was at 03:50 PM ----------

Did you also install the phh app?

And I would recommend changing to TWRP. CWM is outdated.
[Magisk] TubbyStubby:
yes i installed the phh app still no good.

Moreover i switched from TWRP to CWM because former was not flashing magisk. anyways i will try it out once with twrp.
[Magisk] Captain_Throwback:
The error is telling you the problem. So first mkdir /magisk ;).

Or just grab the flashable zip that mounts Magisk for you.
[Magisk] italia0101:
I'm dumb. Thanks
[Magisk] Rhoban:
How about downloading the root zip from the thread and flashing it yourself.

Automation doesn't always make the job easier.
[Magisk] meistr91:
Sorry for dumb question, can I use this method on xperia z5 compact running 6.0.1?

Im on xpower5.0 rom rooted with superSU 2.78 + xposed v86?
[Magisk] TubbyStubby:
no good tried it from the app, from the post, with CWM, with TWRP, nothing is doing anything don't know whats going wrong. :confused:
[Magisk] DanielF50:
Thank, I'll have to make a nandroid backup and give it a go.

Funnily enough, I've seen issues with passing SafetyNet with all of the above, & hosts file modifications, but no matter what I set my selinux policy too, i always pass.
[Magisk] Artim_96:
Does the Magisk manger show phh in the installed modules? Otherwise you have the same problem as many, that it won't stick in many cases. The way I just fixed it was to uninstall Magisk, reinstall it and only install phh's SuperUser. For me it won't stick too if I install any additional module (tried with my own to put the WakeLock Detector to /system and the one from repo to enable Google assistant)
[Magisk] JJXB:
I'm getting seriously frustrated trying to get V4A working (Samsung A300FU - Galaxy A3 on 5.0.2) and want to know what i might be doing wrong.

I have phh su266-2 with Magisk v9 and Magisk Manager 2.5 and whenever i go to get V4A working (tried installing the driver via MM before AND after installing V4A 2.4.0.1 from the apk in the official v4a thread), it doesn't want to detect the driver after reboot. I also have SELinux Mode changer on to change into permissive on startup but i don't know if that's too late for it to help/hinder V4A's drivers loading. i also tried the material design version of V4A and had the same results so i'm not sure what i'm doing wrong here.

Also: is there any chance of getting Xposed for samsung api 21 since the A3 never got an update past 5.0.2 to my knowledge (and i have checked multiple times) and the last time i tried installing the api 21 version with magisk v6 it only caused problems booting until i uninstalled xposed via TWRP.

Edit: using V4A 2.5.0.5 seemed to solve my problem with getting it working (having to tap the V4A entry and go to the question mark to get the right version of V4A was counterintuitive though, no wonder i didn't find the 2.5.0.5 apk until after posting this) my xposed question does still stand though.
[Magisk] Danny94:
Installed Magisk Manager

Magisk v 0.9

[magisk] phh user

phh user app

picked "activate magisk hide"

Edited:

Works fantastic, thanks a lot !!
[Magisk] Didgeridoohan:
Root, Magisk, Xposed, permissive SELinux and unlocked bootloader are all things that mat trigger Safety Net. Magisk Hide takes care of root and Magisk. Do you have any of the others? Also, leftovers of previous root may interfere.

Edit: Oh... nevermind. :D
[Magisk] Danny94:
[MENTION=4667597]Didgeridoohan[/MENTION]

Yeah there was a problem with root at beginning. Magisk manager didn´t asked for root rights this way "activate hide root" doesn´t worked.

Reboot helped =).
[Magisk] Zaryabb:
Wait what???!! What's the point of this guys I can't toggle root anymore so I don't understand what can i do with magisk now? I haven't opened Pokémon go in like months and I got a new ROM and it allowed me to install magisk so I did only to realise the manager doesn't allow root toggle so is there a point to this cuz the device is always going to be rooted isn't it
[Magisk] gstanke:
Enable magisk hide and you will still be able to play pogo
[Magisk] Zaryabb:
How do I get magisk hide
[Magisk] gstanke:
That is something I will allow you to read about, which obviously has not been done
[Magisk] Kany3:
Good eveing guys how can i check if my bootloader is locked or unlock? I got the t-mobile note 5 with note 5 grace ux rom install.

Thanks for your help in advance
[Magisk] culiacanazo:
Don't take my word for it, as i have a TMO S5, but my understanding is that at least back then TMO was the most lenient and accessible in those matters.

How I've gotten by in the past is Google my exact model with just keywords, in this case bootloader, followed by (ALWAYS!) Xda but I'm sure somebody will soon give you the answer, perhaps first scolding you for not searching and not being in your devices forum lol