yashsingh1/xdaforums huggingface dataset:
[Magisk] arcane47:
This has something to do with magisk.img residing in /data folder. This caused issues as /data is the mountpoint of /dev/block/dm-0. Quite possibly because my phone is encrypted.

This can replicated by:

losetup /dev/block/loop3 /data/magisk.img

mount -v -t ext4 /dev/block/loop3 /magisk

You'll see:

trying BLKROSET ioctl on '/dev/block/loop3'

This fails to mount loop device rw, and makes it read-only. Hence the return is "Permission Denied" as per magisk --mountimg (running toybox mount)

Hack workaround:

cp /data/magisk.img /sdcard/

cp /data/magisk.img /sdcard/magisk_merge.img

rm /data/magisk.img

ln -s /sdcard/magisk.img /data/magisk.img

ln -s /sdcard/magisk_merge.img /data/magisk_merge.img

Install Modules... (Will have to repeat on reboot.)

Followed by running:

magisk --post-fs-data

I'm sure there is a cleaner way, but this was a quick PoC.
[Magisk] Psyscope:
Ok will install it and get you a log.
[Magisk] Pkt_Lnt:
Recovery log, Magisk logs (regular and debug) and logcat would all help.

Check the "Asking for help" section in this post.

https://xdaforums.com/showpost.php?p=73145975&postcount=2
[Magisk] brandonsisco:
Yes install custom kernel first before Magisk and all good
[Magisk] fOmey:
I believe your correct about the mounts being read-only... hence the "permission denied" error.

I've never seen forced encryption as aggressive as this mediatek device. It's relentless !

I've wiped the /data partition in TWRP in attempts to remove any encryption on the partition, same story tho...

Thanks for the reply, I'll be sure to give what you suggested a try... Perhaps we can automate the process until a fix in included in magisk..
[Magisk] tgp1994:
So am I the only one who's having problems updating to 5.4.0? I have 5.3.0 since that was what the OP had several days ago. I keep getting notifications to download 5.4.0, but nothing appears to happen when I tell it to update. The Magisk log doesn't have anything helpful.
[Magisk] Pkt_Lnt:
No, many many many posts here about that with 5.3.0, and already fixed. Check this link.

https://xdaforums.com/showpost.php?p=74191153&postcount=4302

Download 5.4.0 from the release thread and install manually.
[Magisk] tgp1994:
Argh, sorry about that. :( Thank you for the help!
[Magisk] zaq21wsx:
I don't really want that

but Magisk 14.3 solved my problem
[Magisk] zaq21wsx:
but there's another problem

MagiskHide can't store list of the apps it should be working for
[Magisk] Didgeridoohan:
If you're using a Moto device and don't want to use a custom kernel that fixes their faulty implementation of f2fs, you'll have that issue.

You should be able to enable Core Only Mode in the Manager settings, but apps added to the Hide list won't be kept on a reboot. You'll have to re-add them...
[Magisk] buggerritt:
Hi, I posted this problem a few pages ago but didn't include a logcat and I think the debug file wasn't right so, I'm going to do it right this time. I'm unable to use 14.3 because the manager fc's. 14.2 works fine. If i update just the manager, that fc's as well. I've flashed magisk Uninstaller before flashing the update, cleared cache/data, deleted everything from MagiskManager folder, wiped cache/dalvik, tried all this in different orders, and still come up short. I'm running lineage 14.1 (7.1.2) on a Moto G5 plus with elemental x 1.12 kernel. Please help me figure out if it's something I can fix. TIA

Edit: solved by dirty flashing my ROM.

happy flashing

http://cloud.tapatalk.com/s/59e8792e13415/logcat.txthttp://cloud.tapatalk.com/s/59e879358716c/magisk_debug.log
[Magisk] dougluna:
I tried with the three versions, 14.0,14.2 and 14.3 before installing I need to flash the zip file of image 2 from this restart and the message of image 1 appears but still the boot continues from there I enter again in TWRP by the command: fastboot boot twrp .Img and I make the Magisk flash it shows again the message of image 1 continues with the normal boot, but if I restart it it appears again the error message and it does not continue with the boot my device is the LG X Power (K220dsf)

My boot file is this: https://drive.google.com/file/d/0BxUolIz_XX34c1ZqX2M5WE56UDA/view?usp=drivesdk
[Magisk] inouext:
Hello.

Magisk V14.0 installed ok without issue,

Magisk V14.3 gives me a fail warning on twrp.

Log attached.

Thanks.
[Magisk] Didgeridoohan:
Interesting. How about you upload your untouched and patched boot images so that [MENTION=4470081]topjohnwu[/MENTION] might take a look at it...
[Magisk] freetushkan:
If it still actual, my Mi A1 is at your service :)
[Magisk] nkay08:
As I see you've been able to install it manually, but in the future check that Magisk Manager has Storage permissions and then it should work.
[Magisk] pulsarone:
hello everybody, excuse my bad english i'm french, i have uninstall Magisk with .zip (Magisk-uninstaller-20170928) and now i have a bootloop on my galaxy samsung S6

Wipe cache and data doesn't work... Only TWRP work i'm blocked... :(

Please help me
[Magisk] chudy_85:
Download firmware for your region Andrzej extract boot.img and flash using twrp
[Magisk] onliner:
I do not know if it is the right place to post this, so I apologize in advance in case it is the wrong place:

I installed Magisk 14.3 on my device with Android 7.1.2 and AOSP Extended but the application Magisk Manager has not been installed, i had to extract the apk from the zip and install it manually, i dont know if the logs can show the problem, but just in case, here the attached:

(root and Magisk Hide works perfectly)
[Magisk] demonoidmaster:
He could just flash the boot img in /data, it's the one magisk copies over as a backup, though you need to extract it first from the archive
[Magisk] counterfeit187:
[MENTION=4470081]topjohnwu[/MENTION] do you still need any files from Oos beta 16 for the Oreo bring-up for op3t?
[Magisk] Riku Azhurlar:
Doubt it'll be that much different put if you need any from the op3 let me know
[Magisk] cvxda:
I'm a bit puzzled that there's no reply at all to my postings. Have I made some faux pax in thread etiquette I'm not aware of? Any help is appreciated.

Thanks,

Corinna
[Magisk] Shadowghoster:
[MENTION=3419717]cvxda[/MENTION] I think it would be more helpful if you open an issue on GitHub with your files. It's more common to give them priority than issues posted here.
[Magisk] Didgeridoohan:
You've done nothing wrong. Unless there are follow-up questions needed, for other logs or info, there's really no need to reply. Except for some kind of recognition that the log has been noted, I guess.

[MENTION=4470081]topjohnwu[/MENTION] have very little time to browse the threads at the moment. Very busy with real life...

Edit: oh yeah... Your logs have been noted. :D
[Magisk] Pkt_Lnt:
Keep an eye out here for what's coming. :good:

https://twitter.com/topjohnwu?lang=en
[Magisk] esun:
It seems the issue section there is closed.
[Magisk] ScottIsMyName:
Trying to install to the Pixel 2 XL and have no had any luck. Since we have no recovery, I'm not sure of a way to any logs (/data/magisk_debug.log).

I have tried with both 14.0 and 14.3. 14.0 boots just fine, but shows not installed. 14.3 boot loops. Of note, is that the patched boot.img file generated by magisk manager 5.4 is about 25mb compared to the original 40mb stock boot.img file.

What can I do to help debug this?
[Magisk] ScottIsMyName:
Here is the stock boot.img file from the Pixel 2 XL (with build number in the file name). I tried flashing the generated patched_boot.img file in bootloader but it just bootloops (and since I have no root, I cannot get the any logs it may have generated).

Uploaded to google drive since it's too big to attach here

https://drive.google.com/file/d/0B9qRrGF_Lbu9eUdGSEJzUm05WDQ/view?usp=sharing
[Magisk] scottysau:
This version of Magisk breaks a OnePlus 5 running 4.5.13 firmware on last build LineageOS 14.1. I've done a clean install and all was fine until I installed Magisk v14.3 (1437) and then it broke. Returned to normal after using the Magisk uninstall zip.
[Magisk] Didgeridoohan:
Details? Logs?
[Magisk] FSMcas:
Anyone tested it with the Pixel 2 yet, since the factory images came up yesterday? I'd try it myself, but it's my daily driver and I don't want to risk it...

EDIT: Yes, someone did. And it didn't work. Too bad :(
[Magisk] zaq21wsx:
but why isn't there /magisk/.core/hidelist?
[Magisk] tag68:
I'd like to know more and test myself, but still do not have Nougat on my own Moto Z Play. The current explanation is:

Motorola did fix the f2fs loopback problem by Android, that mount --bind to f2fs is not possible.

Motorola did implement some new f2fs loopback problem, that mount --bind to f2fs creates a readonly device.

Magisk does mount --bind on /data which is f2fs formatted to create /magisk - this means that /magisk is readonly because something is wrong.

If /magisk is readonly, my guess is that /magisk/.core can't be written.

You may follow the guide how to move magisk.img from /data which is f2fs to /cache which is ext4. See here.
[Magisk] yujincheng08:
Hey! I am facing a problem and I don't know whether it's a bug.

I want to install systemless xposed on my RedMi note 3 onMIUI 9 7.10.19.

And I found that if the I place xposed.prop on /system then I get into bootloop (not booting into system but into recovery). If I don't place xposed.prop on /system but somewhere else, it can boot normally.

Here is my log: https://drive.google.com/file/d/0BwxSJ35Xas7OaFE5cWtJUmJlNkU/view?usp=sharing
[Magisk] ante0:
Actually, do you mean you place xposed.prop manually in /system?

Because Magisk binds it from /magisk/ to /system/xposed.prop, so that might be why.
[Magisk] Jinded:
Did you ever figure out how to get modules to install properly on the Pixel XL with Magisk 14.3? I still haven't been able to figure it out.
[Magisk] ryaniskira:
Nope.
[Magisk] rallyemax:
I am in the same situation: Nexus 5X with Oreo OPR4.170623.009 (Oct 2017) and Magisk v14.3(1437), using the FBE-patched twrp linked in your post.

What worked for me was to set the keep-verity and -forceencrypt flags prior to flashing the Magisk zip. With the phone booted into TWRP (fastboot boot twrp-bullhead-fbe.img), open a shell from the computer (adb shell) and type in the following:

echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk

(source: https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417/post73145975#post73145975)

Then flash the Magisk v14.3 zip, wipe Dalvik/cache, and boot as normal. Worked for me. Root confirmed to be working (at least with Power Toggles and FX so far), haven't checked any modules.

Not sure yet how things will survive an OTA update, but redoing these steps manually should work if the update breaks things. Please reply to this post with your results to make it easier for other Nexus 5X owners to find the relevant info.
[Magisk] valkyrjur:
Anyone tried if it work on Xiaomi MI A1? (A/B partitions)
[Magisk] mightysween:
This is the same thing happening on the new Moto X4 (XT1900)... 14.0 goes through the motions, the patched_boot.img is accepted fine (on both boot_a and boot_b partitions), but Magisk Manager shows that Magisk is not installed. 14.3 causes a bootloop.

Guess we just wait for it to get sorted out... hard to do anything without being able to provide logs.
[Magisk] Didgeridoohan:
https://xdaforums.com/search/thread/3618589?query=Mi A1

Hint: The search function is a pretty nifty little tool...
[Magisk] yujincheng08:
No placing them manally. I place xposed.prop on the zip and it will be mounted to /system/xposed.prop
[Magisk] Didgeridoohan:
It's placed where it is in the module for a reason. Because if it's in /system, it might cause bootloops. :D

Sounds to me like you weren't using the modded Xposed Installer by [MENTION=4470081]topjohnwu[/MENTION]. Check the systemless Xposed thread or the module readme in the Downloads section of the Manager.

Edit: Does systemless Xposed even work with MIUI? :confused:
[Magisk] yujincheng08:
Thanks so much!

But I still have some problems. I referenced to module made by SolarWarez who is also the author of xposed MIUI Version, and he did not place xposed.prop but mount to /system.

I have tried not to place xposed.prop on /system, and it does boot and all modules work well. However the xposed installer by [MENTION=4470081]topjohnwu[/MENTION] says it's not active. And the log says cannot find /system/xposed.prop. How can I fix this issue without mouting it on /system. I have placed it on the module but the installer seems not able to find it.:confused:
[Magisk] Didgeridoohan:
I think you're in the wrong place... :)

Xposed issues should go in the Xposed forums.

About bootloops and Magisk though: On Magisk v14+, if a module mount anything to the root of /system it'll cause bootloops on many devices. And the modded installer by [MENTION=4470081]topjohnwu[/MENTION] works with his systemless Xposed module that you'll find in the Magisk repo. But I don't think that works with MIUI.

But, like I said... You should take any further Xposed support questions to the Xposed forums.
[Magisk] SacredDeviL666:
There i am again :cyclops:

Okay lets get few things clarified.

This thread is for Magisk beta 14.3 bugs reporting only with LOGS

SN fails passes or superflies doesn't matter and don't request it here

If your device isn't supported read the OP on how to proceed.

Imagine every single user posts here stating "hey magisk works on my device and so forth you would have thousands of posts with that irrelevant note here."

You want to acknowledge your happiness click on thanks button of this dev ...not that he needs but will let you be at ease.

If anyone isn't following to whats mentioned above or adhering to OP please ignore and don't respond.

We will be looking into it during our rounds.

Next time i am going to hand personal warnings for each of those users who posts stuffs which isn't related to MAGISK BETA 14.3's BUGS!!!

caps stuck at end :eek:

Thanks

XDA Staff.
[Magisk] Nye-uhls:
Losing root frequently (and massive battery drain while root is lost, could be issues with synapse), sometimes a simple reboot works, sometimes wiping magiskmanager data works... Other times the only thing that works is reflashing magisk. Sometimes even that doesn't work and i have to do full uninstall and reinstall.

Latest magisk beta

Galaxy s6 - g920p (exynos)

Custom stock-based rom by tdhite

Custom kernel, skyhigh port by tdhite (many functions of kernel operate from the skyhigh magisk module)

Installed modules: latest skyhigh module(ill attach the module in case theres any issues in the module itself causing issues... Module is required for normal device functionality), busybox by osm0sis.

Full recovery and kernel logs attached and magisk debug log (logs from a few days ago, taken after root was lost and booted into recovery to save and copy logs)
[Magisk] Gairtial:
So I'm trying this on a Sony Xperia XZ1 Compact and I'm running into SELinux errors. Here's an excerpt from the system log (since Magisk doesn't start and can't generate its own):

<14>[ 11.133768] init: starting service 'magisk_pfs'...
<11>[ 11.133859] init: cannot execve('/sbin/magisk'): Permission denied
<36>[ 11.133919] type=1400 audit(3834592.759:9): avc: denied { transition } for pid=646 comm="init" path="/sbin/magisk" dev="rootfs" ino=15861 scontext=u:r:init:s0 tcontext=u:r:su:s0 tclass=process permissive=0 ppid=1 pcomm="init" pgid=1 pgcomm="init"
<36>[ 11.133927] type=1400 audit(3834597.759:10): avc: denied { transition } for pid=647 comm="init" path="/sbin/magisk" dev="rootfs" ino=15861 scontext=u:r:init:s0 tcontext=u:r:su:s0 tclass=process permissive=0 ppid=1 pcomm="init" pgid=1 pgcomm="init"
<14>[ 11.134071] init: Service 'magisk_daemon' (pid 647) exited with status 127
<14>[ 11.134081] init: Sending signal 9 to service 'magisk_daemon' (pid 647) process group...
<11>[ 11.134125] init: kill(647, 9) failed: No such process

It appears that magiskpolicy should be putting init in permissive mode: https://github.com/topjohnwu/magiskpolicy/blob/master/rules.c#L161

But you can see from the above log that for some reason it isn't. Any ideas?
[Magisk] mightysween:
Posting stock boot image from the Moto X4 (XT-1900-1)... like other A/B partitioned devices, Magisk 14.0 patched boot.img flashes on both boot partitions but shows that Magisk is not installed after boot. And 14.3 beta patched boot.img flashes OK, but bootloops.

Unfortunately, we are at square one with this device and do not have root... so even an adb pull of /data comes up blank. Seems to be no way to pull these logs... is there any other useful info we could be supplying?

https://drive.google.com/file/d/0ByZWXbOZqmVqbUV5T3ZvZEFBZ2M/view?usp=drivesdk
[Magisk] ScottIsMyName:
Can you post 14.3 patched boot.img too?
[Magisk] mightysween:
Yeah... right here:

https://drive.google.com/file/d/0ByZWXbOZqmVqT1o3cC1xVGNBRXM/view?usp=drivesdk

FWIW, Magisk Manager does detect the A/B partitioning and current partition when patching boot.img.

Wish I could get the logs... perhaps troubleshooting in later betas would be served by optionally saving logs to the userdata partition.
[Magisk] biribiribiri:
I am using pixel xl with oreo and magisk 14.3. I have two weird problems. The first is that I would randomly lose magiskhide. When I boot up, I can pass safetynet, but after using it for a while, I can no longer pass safetynet and I need to reboot to restore it. I looked at the log and it seems to have something to do with magisk unable to unmount stuff.

Another problem I have is that the phone would sometimes randomly reboot and stuck at boot screen. I saw someone else posting this problem as well. The other person was also using pixel with oreo, so maybe it is related to pixel?

I have my logs attached.
[Magisk] demonoidmaster:
? safetynet issues of any kind will not get any support, how many times do moderators cleaning up this thread gonna have to say it
[Magisk] biribiribiri:
I am only posting about the first problem because it is related to magisk unable to unmount stuffs after a while. I thought there might be something worth looking at. Sorry if you feel the other way. Can you look at the second problem I mentioned though? I saw someone else having that same issue too.
[Magisk] Didgeridoohan:
[MENTION=7086291]demonoidmaster[/MENTION] I'd say that the post actually falls under the "proper report with logs" category. Something's wrong with MagiskHide, the symptom is that SafetyNet fails and it can be clearly seen in the logs that something's going on. Technically, you're breaking the rules that have been put down by adding to the noise (the irony of me addressing you like this is not lost on me).

[MENTION=8640524]biribiribiri[/MENTION]

I've missed that other mention of random reboots you're talking about. It doesn't seem like a widespread issue.

After a random reboot, could you check for /sys/fs/pstore/console-ramoops and post that? Save the magisk_debug.log from when the device has been stuck at boot and post that as well (if there is one).

MagiskHide randomly failing on the Pixel (and possibly Nexus 6P on Oreo) have been reported a few times and is being looked into.
[Magisk] tron1:
Beginning with Magisk 14.3 my Axon 7 (Version B08, Nougat 7.1.1 Stock Rom, A2017G) isn't able to access my external sdcard (128GB exfat formatted). It's about to format my card... no, thank you android. A fat32 formatted card on the other hand is working. If I switch back to Magisk 14.0(also 14.2) all is fine.

If the log is helpfull...

https://drive.google.com/file/d/0B25sM8MFQfaZUEcxRVJpaUtSb1k/view?usp=sharing
[Magisk] arlyn:
installation failure

Galaxy Tab A (2016) 10.1 Sprint, Snapdragon 625, Nougat.

Hey there, I have tried everything. I will give a little background

On marshmallow I could not get Magisk installed any way aside from manually patching the boot.img via adb. It would boot rooted and I was able to direct install 14.0 from 13.6 beta.

the only thing that correctly identified my boot image and patched it in recovery is phh's superuser.

SuperSU, any version, fails at patching installing and rooting.

when i manually patch this boot image, the magisk install says it is installed and rooted but it seems to not be. root check detects root, but i am unable to copy fonts into the system directory.

patching the boot image from magisk manager results in an "invalid uri" error.

here is my log from an attempted nougat install.

I:operation_start: 'Flashing'

Installing zip file '/external_sd/Magisk-v14.3(1437).zip'

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

I:Update binary zip

I:Zip does not contain SELinux file_contexts file in its root.

E:Legacy property environment did not initialize successfully. Properties may not be detected.

touch: /dev/tmp/bin/b64xz: Permission denied

touch: /dev/tmp/bin/busybox: Permission denied

chmod: /dev/tmp/bin/b64xz: No such file or directory

chmod: /dev/tmp/bin/busybox: No such file or directory

/tmp/updater: line 20: can't create /dev/tmp/bin/b64xz: Permission denied

/tmp/updater: line 26: can't create /dev/tmp/bin/b64xz: Permission denied

/tmp/updater: line 26: can't create /dev/tmp/bin/busybox: Permission denied

/tmp/updater: line 27: /dev/tmp/bin/busybox: not found

Archive: /external_sd/Magisk-v14.3(1437).zip

unzip: can't open 'META-INF/com/google/android/update-binary': Permission denied

sh: can't open '/dev/tmp/install/META-INF/com/google/android/updater-script'

Updater process ended with ERROR: 2

I:Install took 1 second(s).

Error installing zip file '/external_sd/Magisk-v14.3(1437).zip'

Updating partition details...

I:Data backup size is 0MB, free: 9614MB.

Failed to mount '/cust' (Invalid argument)

I:Actual block device: '', current file system: 'ext4'

I:Unable to mount '/usb-otg'

I:Actual block device: '', current file system: 'auto'

...done

I:Can not open /etc/fstab.

E:Error creating fstab

I:Set page: 'flash_done'

I:operation_end - status=1

I:Set page: 'clear_vars'

I:Set page: 'install'

I:Set page: 'main'

I:Set page: 'clear_vars'

I:Set page: 'main2'

I:Set page: 'advanced'

I:Set page: 'copylog'

I:Set page: 'action_page'

I:operation_start: 'Copy Log'

I:Copying file /tmp/recovery.log to /external_sd/recovery.log

if a stock boot is needed, I have one here https://drive.google.com/drive/folders/0BwEy1UqRSifNWGJKNEMxTnVOUjg?usp=sharing

any help would be greatly appreciated.
[Magisk] aer0zer0:
[MENTION=4470081]topjohnwu[/MENTION] Here is a link to the essential PH-1 stock boot image from the NMI81C firmware (latest). Would you be able to look at it and possibly provide supprt for twrp-less patch? thank you

https://download.invisiblek.org/mata/boot.img

No longer the newest.
[Magisk] Delta wolf:
Running a huawei nova plus mla-l03 iv posted in magisk thread itself but coming here to say that modules fail to install on this advice due to a looping issue 6308 E Magisk : mount /dev/block/loop1->/dev/magisk_merge failed with 13: Permission denied

10-30 19:23:31.744 6386 6386 E Magisk : umount /dev/magisk_merge failed with 22: Invalid argument

There's nothing I can do without a kernal I guess any help?
[Magisk] demonoidmaster:
True him having logs beforehand does help but he pointed out that sn failed before talking about magiskmount, anyways sorry
[Magisk] biribiribiri:
I just had another random reboot but I couldn't find /sys/fs/pstore/console-ramoops. /sys/fs/pstore is just an empty folder for me. While I was stuck at boot, I tried using adb logcat, but all I got was a fork error for adb. I guess adb hasn't started at that point yet. I was not sure how to get the magisk_debug.log file for the same reason.
[Magisk] Didgeridoohan:
From my limited knowledge it's probably not a kernel thing in that case, but don't quote me on that. I honestly have no idea. :D

The debug log you get by booting to recovery and copying the file from /data (if there is one). Either with the recovery file manager or adb pull.

Just to make sure: You don't happen to have a case that might push on the power button, causing a reboot. Happens surprisingly often...