yashsingh1/xdaforums huggingface dataset:
[Magisk] vMAC:
Anyone know how to fix this?
[Magisk] johnholley123:
Yep, this is the best solution if the f2fs fix apks don't work for you. There's no reason to downgrade magisk if the only issue is in magisk manager.
[Magisk] Pkt_Lnt:
Best advice we can give is you need to supply requested logs (see post #1) to find out what is happening at the installation. Without those, this is the best advice we can offer.
[Magisk] pWEN:
Yep, just did it. Here's my basic process:

1. Flashed the stock firmware, after removing -w from flash_all.bat

2. Removed the lock screen in the phone settings (so TWRP would work)

3. Rebooted to bootloader, then into TWRP 3.2.1.-0

4. Flashed ElementalX kernel 3.02

5. Rebooted to OS, then back into TWRP (probably unnecessary, but wanted to make sure the kernel didn't goof up somehow)

6. Made a backup of the boot partition

7. Rebooted to OS, and used a file explorer to browse to the boot backup

8. Copied the backup to the root of the phone and renamed it from boot.emmc.win to exboot.img (for convenience)

9. Installed Magisk Manager v5.6.0 fix 2 (could have done regular release, but opted for this version just to see what would happen)

10. Made sure MM was set to update from the beta channel, so it would grab Magisk v15.4, then used it to patch the exboot.img

11. Rebooted back to TWRP and flashed the patched_boot.img in the MagiskManager folder

Note that I never installed TWRP, I was just booting into it from Fastboot.

Opened Android Pay to verify it was working and didn't have any issues.
[Magisk] whitehollow:
I got honor 8 with carbon rom and if I install any magisk after the 14.0 fingerprint and locks creen security crashed. What can I do?
[Magisk] khaytsus:
Cool, thanks for the confirmation! BTW, you should be able to sideload Magisk, which allows you to not have to disable the lock screen. One less thing to fool with. And if you don't need ElementalX it's not needed for Safetynet; but it is a fine kernel so you might have other reasons for using it.
[Magisk] Ja_som:
Read the first post.
[Magisk] hogofwar:
Using the systemless hosts option seems to instantly cause safetynet to trip?
[Magisk] FlavioV:
I can't pass safetynet since last week, even disabling systemless hosts or installing the universal fix. But safetynet is off-topic on here. All we can do is wait until they find a way to get it working again.
[Magisk] mipirakas:
Yup. Just toggle systemless hosts on and then toggle magisk hide off and on again. Works for me
[Magisk] preference:
Is magisk supposed to be a system app or user app. On the latest security patch (Oreo 8.1, RR for OP5t), magisk always installs as a user app. It's like I've been locked out of system. I don't know if this affects my ability to install modules, but it has been hit or miss.

Just want confirmation, has magisk in the past been a system app or user app?
[Magisk] norbolt:
Oukitel K10

I have a brand new Oukitel K10, running Android 7.1.1. I'm attempting to patch it using Magisk Manager 5.6.0.

I've grabbed the original firmware from Oukitel and I've attempted to modify the boot image using both version v15.3 and v15.4.

Both cause a reboot loop once the new boot image is flashed using either adb/fastboot or the "Smart Phone Flash Tool" (windows program). The flashing seemingly goes well, but upon reboot it simply hangs for a while with the Oukitel logo, then reboots.

Flashing the original boot.img restores boot functionality.

Any ideas on what I can try?
[Magisk] Hedigehog:
Try v14.0, on K6 it is working
[Magisk] skawtnyc:
You do realize that Magisk has systemless root built-in, right? This method doesn't remove root since you can't remove it from Magisk anyway.
[Magisk] jcmm11:
You do realize that Magisk patches the boot image for a reason? If you lose the boot image patches you lose root. The data structures will still be there, since magisk.img is on the data partition, but it won't initialize properly on boot.
[Magisk] guest4711:
Magisk Manager is a user app.
[Magisk] norbolt:
Ehm... sorry for noobing it up in here, but how do I select a custom version of Magisk to install with the manager? I tried selecting "custom", and entered the URL to a webserver, pointing at the v14 .zip file, but nothing really happens.
[Magisk] guest4711:
You need to point to the file containing the information about the last version, e.g. https://raw.githubusercontent.com/kantjer/MagiskFiles/master/updates/kantjer.json
[Magisk] cimdrap:
The manager keep asking for autorizations everytime i use a root app even if i pick "always" option on the pop up
[Magisk] Sam Nakamura:
Go to settings and choose "Grant" instead of "Prompt", not ideal but there's no better option than this workaround atm, some report that using Magisk 14.x doesn't have this problem, if you feel like downgrading you could give it a go...

---------------

Also please read the first post, where are the technical details, logs, etc. - it's about debugging here at this beta channel....
[Magisk] cimdrap:
Thanks for the hint

---------- Post added at 12:29 PM ---------- Previous post was at 12:27 PM ----------

Exactly!
[Magisk] norbolt:
That worked a treat, and the phone booted just fine with it :D
[Magisk] Phonerix:
I can't install modules on 15.3 1531. It shows error and suggest to install magisk 15.3 ( it's installed!!)
[Magisk] Ja_som:
Logs
[Magisk] topjohnwu:
Great news for those with crashing Magisk Manager, I finally reproduced the bug on my device. Next update should fix the issue.
[Magisk] skawtnyc:
I'm not the only person who recommended this solution. I used it myself and it worked fine. The worst thing that could happen is that you need to flash Magisk 15.3 over the unpatched boot image.
[Magisk] kryzeK:
Can this solve the problem of Magisk not remembering the Superuser permission already granted for X app?
[Magisk] Didgeridoohan:
Probably yes... Wait and see.
[Magisk] jcmm11:
Correct. You will need to flash Magisk to patch the boot image. If you had said that in the first place there would have been no argument at all. But your response implied that that wouldn't be needed

If you had said "extract the boot image, flash it in TWRP, then flash Magisk" you would have been fine. Flashing Magisk before the boot.img is a wasted step that accomplishes nothing. If you did that you would have to flash Magisk again.
[Magisk] skawtnyc:
This is the order of install I used:

System already has Magisk 15.3 and custom Unicorns/Xceed kernel installed.

1. Install Magisk 15.4 in Magisk Manager app.

2. Reboot into recovery mode (TWRP).

3. Flash Unicorns/Xceed kernel.

4. Reboot into system.

I did not need to flash Magisk again after this. I still retained the Magisk install and superuser, and didn't experience the boot failure that occurred when installing Magisk 15.4 last and then rebooting.
[Magisk] jcmm11:
If the system already has the kernel you want them why step 3? And where did you get the image for step 3? It sounds like the image from step 3 is already patched. If it really is an unpatched image there is no way you would keep root. I'll let someone else weigh in on this if needed. I'm pretty much done. Maybe you'll believe them ?
[Magisk] skawtnyc:
You are incorrect.

https://xdaforums.com/showpost.php?p=75564860&postcount=5129

Also this, which is the first line of the installation instructions by the author of Magisk:

"If you plan to flash a custom kernel, flash it AFTER installing MAGISK"

You are flashing a custom rom with a custom kernel. It isn't stock.
[Magisk] jcmm11:
That's if you're flashing a zip (Anykernel based), NOT a boot image. As I said previously flashing an Anykernel zip will merge it's changes with the existing kernel.

And for the record flashing a custom kernel before root would also work, it's just not the normal way to do it. (You're better off if the backup contains the stock kernel that came with your ROM rather than a custom kernel).

Stock means stock for whatever ROM you're running. Obviously if you're running a custom ROM it probably has a custom kernel - but it's stock for that ROM.

And no I'm not wrong. But now I really am done.
[Magisk] skawtnyc:
jcmm11: Added to my ignore list. If you have a custom ROM with a custom kernel, only ridiculous mental gymnastics would allow you to consider that custom kernel to be stock. It's not stock compared to the actual stock code. If you can't flash the custom kernel using an AnyKernel zip, then you either flash the universal kernel like I recommended or you don't flash the latest Magisk.

The author of Magisk provided the answer but you want to tell me I'm wrong. So, please continue being smugly wrong after numerous people pointed out the solution here and elsewhere. It's not my job to cure you of ignorance and arrogance.
[Magisk] night0crawler:
Magisk is getting uninstalled by itself. I used it for around an hour and it got uninstalled automatically. Simply I'm losing root status again and again.

I'm using Moto G4 Plus XT1643 3GB Indian Variant running on Resurrection Remix 6.0.0 Oreo 8.1.0 by Jleeblanch

Earlier I used to encounter this issue with Magisk's previous version as well and in previous builds of Resurrection Remix, Stock Moto ROM, Lineage ROM. I had this issue with Magisk on all ROMS.

Has anyone else faced this specific issue? If yes can anyone please help me out with this.

I'm not sure what logs should I provide for this. Whether Magisk debug file, Recovery log after installation or should I let Catlog run in the background? I don't think Catalog or any logcat app will work. Or do I have to get logcat using PC?
[Magisk] cmattern:
FWIW I've been running 15.4 on Carbon 6.1on a Pixel 2 XL with no issues, safetynet included. I briefly ran Nitrogen OS on the same device also with no problems.
[Magisk] Lizzacore:
G930F - TGPKernel 5.12 (newst)

Won't boot anymore, reboot screen says that the kernel don't support selinux.
[Magisk] abhi021:
Using magisk manager 5.5.6 with Magisk 15.4 not showing any download modules. Any solution?
[Magisk] NewKindOfWorld:
Wait for fix ...
[Magisk] topjohnwu:
Magisk Manager - F2FS Crash Fix Attempt 3

It shall work this time, I've tested on my own device and things are working just fine.

Please test and report, thanks!
[Magisk] agoraphobie:
Works fine here on oneplus3 rr6, THX a lot!
[Magisk] ATP4:
Yes, works fine also here (OP3, RR6). Thank you [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Sam Nakamura:
FC is fixed! Good job!
[Magisk] Sam Nakamura:
Edit:

Plus superuser is fixed, it finally remembers the permissions...
[Magisk] melendi:
Flashing Magisk on Shield TV

Hello gentlemen, I would like to ask you how to flash Magisk on Nvidia Shield TV 2017 16GB (Rom: Full Nougat v1.5) when there is an error CANNOT MOUNT /VENDOR?

In TWRP under the tab "Mount" there is no option to mount /vendor.

Is there any workaround?
[Magisk] xabier-bo:
Now working in Shield Android TV. Thanks!!!
[Magisk] Sam Nakamura:
This is the beta channel for discussing magisk beta related issues or debugging of beta development in general, as your question isn't beta specific but rather a general compatability question I request you to visit the Magisk general support thread:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382

Make sure you read the 1st post of this thread and provide logs and technical description accordingly...
[Magisk] melendi:
Thanks and you are right, I am sorry...
[Magisk] cimdrap:
Everything works great!
[Magisk] Massi-X:
OTA constantly fails

Hi to all, I have a question: following topjohnwu tips for ota update with the latest magisk installed (advanced cryptography and avb 2.0 checked) the ota constantly fails (it reboots continuously, and then switch to the other slot and stay on the G logo indefinitely). The only way to make it boot is to reflash the stock boot image. Searching on the internet doesn't help. Someone has experience this?

Pixel 2 XL with A/B method
[Magisk] Deerar DS:
It didn't work with me :( . . . if I re-flash the room is that will help?
[Magisk] xabier-bo:
But fails to keep granted apps after reboot... :crying:
[Magisk] Didgeridoohan:
Post a logcat.
[Magisk] NewKindOfWorld:
Working fine here, magisk 15.4 /crash fix 3, RR 6.0, latest caesium kernel. Manager is ok, apps root granted shows in superuser tab, and everything sticks. Thanks !
[Magisk] rom-g:
No more FC here on stock moto G 2015 (f2fs).

SuPolicies not remembered are fixed too.

Thank Youuuuuu
[Magisk] PinoF75:
Working fine here on OP3 with z-unleashed rom + magisk 15.4 +app fix
[Magisk] NightHeron:
RN4 with F2FS and custom Nitrogen os, everything works great. Thanks!
[Magisk] Wolfcity:
Crash Fix Attempt 3 working perfectly on Moto G5+ with f2fs data partition and f2fs loopback bug module by [MENTION=5228676]VR25[/MENTION]. Thank you [MENTION=4470081]topjohnwu[/MENTION]!
[Magisk] krabban:
Do I just uninstall magisk and use the fix.apk ?
[Magisk] Hawtpants:
Hi there, guys!

I just got a brand new Moto Z2 Play and I want to install Magisk on it. Is there an easy way to receive OTA updates and whatnot? Do you guys think it's worth to root a new device like this, which is still actively receiving updates?
[Magisk] johnholley123:
No, you uninstall magisk manager and install the fix app.
[Magisk] ryanfraser38:
Deleted comment

---------- Post added at 04:27 PM ---------- Previous post was at 04:06 PM ----------

The app no longer crashes or freezes but when I open root apps magisk crashes :(
[Magisk] khanjui:
Latest fix attempt (3) is working fine on my Xiaomi Mi 5s Plus with LineageOS 15.1 (Android 8.1.0) using F2FS /cache and /data.
[Magisk] BertlBrown:
it still could be selinux to blame, as I can't imagine how to write any device driver allowing regular file access while breaking loop. I don't think the necessary information will be available to the block device driver. on the otherhand sdcardfs is written to replace the security model of the remaing file system with it's own, based on the app accessing /storage/emulated.

I still have to replicate your findings, but I tried something, which worked:

mkdir /sbin/.core/.m
mount -t sdcardfs /data/adb /sbin/.core/.m

looping the image from /sbin/.core/.m allows sucessful writes.

Can you try to integrate this to the script? I don't know if /sbin/.core is available that early, but I guess, it should. Maybe mounting to /cache/.m would work, too ...
[Magisk] martyfender:
Do you only recommend installing this on a device that is on the F2FS file system, or should we install it and test it on other devices? Or wait for a new beta release?

Thanks
[Magisk] Vodderz:
Works perfectly on Oneplus 3T, Resurrection Remix 6.0.0, F2FS. Remembers Super User permissions, no FC so far. Great job, many thanks!
[Magisk] Kuttoosssan:
Finally works fine. Redmi note 4 with f2fs.

Thanks a ton.
[Magisk] raunaqseth:
Works perfectly
[Magisk] Bobbaloo:
6p here. RR Oreo. 8.1 Working great.

Thanks!
[Magisk] Bsanborn:
One plus 3 running omni 8.1 with f2fs. Works perfectly now. Thanks for your hard work
[Magisk] Shriac:
Works perfectly on Galaxy S6 Manager v 5.6.0 and 15.4.
[Magisk] Obi-XDA:
working fine on lg nexus 5, unlegacy rom android N v7.1.2

many many many thanks for your hard work and effort
[Magisk] richard-willes:
thanks..

Great Work!! best root
[Magisk] isosika:
Moto G5 stock ROM works nice. Except I can not install any modules...
[Magisk] monster1612:
It's because of an f2fs issue caused by the stock kernel on Moto devices. Flash this module through TWRP and see if it helps - or flash a custom kernel.
[Magisk] isosika:
Thanks for the tip! That actually did the trick. First flash did not work but when I tried again all is good!
[Magisk] Milanptl603:
Not Working Magisk + Systemless Exposed In My Redmi Note 3

Not Working Magisk + Systemless Exposed In My Redmi Note 3 Miui 9 Stable Global Android v6.0.1....

When i get update of miui 9 after i flashed Magisk 15.3 and it's worked and magisk hide worked, safety net passed too... But not able to use Systemlss xposed ... Tried too many times by flashing different modded verisons for Miui... But not able to work xposed.. Sometimes getting flashed and Not able to active module. And sometimes not able to flash too...

So i tried many fixs from net and after 7-8 trys i am getting boot loop too many times. And after 10-15 flashes of recovery rom again and again.. Finally at the last getting Boot loop every time i flash Magisk 15.3..

Now, i am not able to flash Magisk 15.3 also. Just magisk 14.0 working now but not able to use systemless xposed in magisk 14.0 and also safety net not passed in v14.0....

Tried too many times by fully installing magisk and all.. But every time failed!

Please give me solution.. I want to use Magisk With Systemless xposed and magisk hide for root hiding purpose in my redmi note 3 miui9 android 6.0.1..

Thanks
[Magisk] johnholley123:
I don't know how to fix your issue with bootloops and stuff, but I can tell you that you will not be able to pass safetynet with Xposed enabled, even the systemless version.
[Magisk] SoySergio:
Axon 7 - AospExtended + Hellsgate kernel working fine. Magisk does not fc and su saves the apps.

Many thanks!
[Magisk] simar404:
When will magisk support flashfire? I am on Google Pixel

I am running on magisk 14.2 beta as it is the only version which supports flashfire.

Thanks
[Magisk] Artim_96:
Ask Chainfire when he will support Magisk...
[Magisk] initguru:
I have been trying to install Magisk 15.4 on Android-x86_64 7.1.2.

It is quite uncommon but I have managed to work on this OS until Magisk 15.3.

Somehow installation failed as this: (Magisk Manager log)

- Device platform: x64

- Extracting files

Segmentation fault

Failed!

! Installation failed

Any help is really appreciated.
[Magisk] Didgeridoohan:
Is that really the entire installation log? Or is it just the output from the Manager flash screen? The installation log from the Manager (press "Save log" after flashing), or a recovery log from trying to flash the Magisk zip in recovery, would be immensely useful...
[Magisk] initguru:
Yes, unfortunatelly that is all the log under /sdcard/MagiskManager/log...
[Magisk] Didgeridoohan:
Do you have access to a custom recovery to see if it works there (and don't forget the recovery log if it doesn't)?
[Magisk] initguru:
Android-x86 builds do not have a custom recovery (it is installed on x86 based pc) so I can only patch a boot image in Magisk Manager.
[Magisk] Sam Nakamura:
Maybe a bug with magisk 15.4/magisk manager 5.6 (fix attempt 3) was found, thought I report it, as I wanted to flash the magisk module "front camera fix" (for the 3t android 8, see linked G-Cam thread) for G-Cam Mod via TWRP or magisk manager it returned "can't mount /system, /vendor", even though every other module flashed just fine on this setup/ROM, installation log is attached:

https://drive.google.com/file/d/1r4FEFeBJ58nE_zlW7Gwjsd0nJqfTfafS/view?usp=drivesdk

I first tried to clear the possibility if it's ROM related

https://xdaforums.com/showthread.php?t=3695992&p=75634608 (+ subsequent posts)

and then asked in the magisk module / G-Cam Mod thread which led to following conclusions / assumptions from S4turno

https://xdaforums.com/showthread.php?t=3695992&p=75635657

Nothing urgent or anything :) just thought it might maybe be of any interest...

--------

AND HERE'S THE FIX

https://xdaforums.com/showthread.php?t=3658552&p=75636821
[Magisk] Didgeridoohan:
Has it worked previously? There's an extra "}" added to the config.sh file, which in turn creates a syntax error:

- Copying zip to temp directory
- Installing FRONTCAM_PORTRAIT_FIX_OP3T_1_ (1).zip
- Mounting /system, /vendor
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
creating: common/
inflating: common/post-fs-data.sh
inflating: common/service.sh
inflating: common/system.prop
inflating: config.sh
inflating: module.prop
update-binary: /dev/tmp/install/config.sh: line 91: syntax error: unexpected "}"
Failed!
! Installation failed

Removing it let's the module install just fine...

Edit: Ah... Ninja'd. :D
[Magisk] Sam Nakamura:
Funny enough it wasn't an issue on magisk 15.3...

Thanks for lending your Hawkeyes :highfive:
[Magisk] isoladisegnata:
I followed this..great
[Magisk] korom42:
Very weird magisk 1540 worked once for the first time but after that kept getting onto bootloop

I tried to downgrade and flash uninstaller then upgrading, wiping cache etc.. with no success
[Magisk] korom42:
Another much smaller log (disabled all modules)
[Magisk] vishalpal555@gmail.com:
Call rec feature in 8.1 can u bring it as a module in magisk
[Magisk] initguru:
nvm: I found the tool to simply debug a specific process.
[Magisk] adwaitatre:
Magisk safety net not passed how to fix it
[Magisk] linux.alucard:
Works great with my RR6 :)
[Magisk] Ja_som:
This is Magisk beta thread, not for module requests.

Read the first post.
[Magisk] AceMONKEY:
hey guys ,when I install the 15.4 and using some replace modules,like iYTBP,it made me cant done anything about system profiles ,I cant delete things,cut things. so cant we solve this bug ?
[Magisk] SnakeByte:
The fix apk works on ZenFone 3 Laser (ZC551KL). First, after installing it the app would force close instantly every time, but after reboot, all works great. No more errors installing modules. Doesn't pass safetynet, but i care less as i don't need it. Thank you.
[Magisk] linux.alucard:
Working perfectly! RR6_mido
[Magisk] agstn.tanmay:
same things happens to me!any thing to fix it!
[Magisk] fonfox:
Just confirm :good:

V16 works on oneplus 2 oreo 8.1 aosip and also on Galaxy S3 I9300 with LAOS 14.1/ Koffee kernel. Perfect
[Magisk] Ja_som:
Same answer as well for you, read the first post.
[Magisk] hurray:
I can't update my Samsung Galaxy tab S2 with Lineage OS 14.1 and Magisk 15.3 to 15.4 or 16.0. Direct install and modify boot.img are failing with similar messages:

- Device platform: arm

- Extracting files

boot_patch.sh: ./util_functions.sh: line 15: ps: Permission denied

boot_patch.sh: ./util_functions.sh: line 15: grep: Permission denied

boot_patch.sh: ./util_functions.sh: line 15: grep: Permission denied

boot_patch.sh: ./util_functions.sh: line 16: grep: Permission denied

boot_patch.sh: ./util_functions.sh: line 16: grep: Permission denied

boot_patch.sh: ./util_functions.sh: line 17: id: Permission denied

boot_patch.sh: ./util_functions.sh: line 17: grep: Permission denied

boot_patch.sh: line 75: chmod: Permission denied

boot_patch.sh: line 78: ./magiskinit: Permission denied

- Unpacking boot image

boot_patch.sh: line 87: ./magiskboot: Permission denied

boot_patch.sh: line 117: ./magiskboot: Permission denied

boot_patch.sh: line 148: ./magiskboot: Permission denied

boot_patch.sh: line 150: rm: Permission denied

boot_patch.sh: line 177: ./magiskboot: Permission denied

- Checking ramdisk status

- Patching ramdisk

- Repacking boot image

! Unable to repack boot image!

Failed!

! Installation failed

Magisk 15.3 and my installed modules are running very well.

Has someone an idea why this happens and what I can do to upgrade from 15.3 to 16.0?
[Magisk] rickysidhu_:
V 16 working great on my Pixel 2 XL 8.1 Feb with Xposed 90.1 beta3!
[Magisk] korom42:
Magisk 1600 bootlooop log
[Magisk] Neverendingxsin:
Magisk 16.0 won't boot on my stock Pixel 2 XL running the Feb update, went back to 15.4 and it booted immediately.
[Magisk] Badger50:
Did you try doing a hard restart by holding the power button after you flashed 16.0?? Worked for me on my P2XL ?
[Magisk] Soooperstar:
OG Pixel XL seems to be working fine
[Magisk] sandaljrpit:
Work fine.

But, but there is an error code.

open: /proc/1234/cmdline failed with 2: No such file or directory

My device MI4 LTE ( Cancro ) MIUI 9

Thanks :)
[Magisk] Neverendingxsin:
I flashed it via patching the boot image, should I try just the direct install from the app?
[Magisk] Badger50:
That's what do every time! Hasn't failed me yet :good:
[Magisk] Neverendingxsin:
Just did that and it worked flawlessly, thank you :)
[Magisk] Skull97:
Have you tried to flash the uninstaller then reflash magisk?
[Magisk] chazall1:
All functioning here.nice
[Magisk] CyberpodS2:
Every time I update magisk the first reboot hangs at the google screen and never ever starts the animated line underneath indication it I is loading. It also never times out or bootloop. Holding the power down and forcing it to reboot fixes it every time for me.