yashsingh1/xdaforums huggingface dataset:
[Magisk] topjohnwu:
The latest beta is now online!

I am aware of Xperia issues, can anyone point to anything I can look up to fix the issue? Thanks!
[Magisk] Black-FR:
Hi John... Maybe this posting here:

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post75017258

The same user had another post on the 5th January, with some more logs included.
[Magisk] SnakeByte:
Hello [MENTION=4470081]topjohnwu[/MENTION] the link for 15.4 doesn't work and the direct zip download crashes Xda app.

Update: link works, thank you.
[Magisk] Josevega:
Can you add fix for magisk not mounting data in twrp for Samsung oreo the issue is in fstab
[Magisk] SnakeByte:
Confirmed successfully flashed magisk v15.4 via twrp on ZenFone 3 Laser ZC551KL running on stock 7.1.1, with Magisk Manager 5.6.0.

No issues so far. :svetius:
[Magisk] ATP4:
v15.4 work fine, but Magisk Manager 5.6.0 FC.

I'll post a logcat tomorrow.

OnePlus 3 / Resurrection Remix 6 (Oreo 8.1)
[Magisk] Skull97:
Umm, there should be a new 5.6.0 Magisk Manager version, so check your version one more time to see if it already up-to-date.
[Magisk] ATP4:
Oops, typing error on my part, I was talking about version 5.6.0
[Magisk] johnholley123:
+1
[Magisk] _f0xx:
Same here.

OnePlus 3 / Validus (Oreo 8.1)
[Magisk] ]grimm[:
v15.4 installs successfully on the Pixel C but hangs at boot. I've reverted back to the stable channel and reinstalled v15.3 which is still working without issue.
[Magisk] ignitionnight:
OP3T - Omni Rom 8.1 - 2/11 Build

Installed Magisk Manager 5.6.0 and immediate force closes.
[Magisk] russel5:
Sony XZ1 Compact, android 8.0

All works, no issues
[Magisk] SnakeByte:
I had this issue. Uninstall 5.6 reinstall 5.5, open and wait for Magisk to ask you to update to 5.6 within the app. That should fix it.
[Magisk] ignitionnight:
I installed 5.6 using 5.5 in the first place, but just in case tried again and 5.5 works fine but as soon as I upgrade to 5.6 nothing but FCs. Thanks for the suggestion though, worth a shot.
[Magisk] khanjui:
Same on my Xiaomi Mi 5s Plus using LineageOS 15.1 (Android 8.1.0) with /cache and /data as F2FS.

5.5.5 (91) is the latest working version for me.
[Magisk] martyfender:
I have been using Magisk with no issues since the V15.0 train wreck that was quickly resolved with v15.1. I have also used the last beta 15.3 with no issues and [MENTION=3306843]kantjer[/MENTION] 's unofficial builds with no issues, up to and including his V15.3.1 (180211), released yesterday.

Today I saw your new beta release and first downloaded it and flashed it through TWRP and it failed to boot, taking me eventually to bootloader mode with an error code about the problem with the bootloader.

I then rebooted to TWRP, flashed my stock boot.img and and older, unofficial build that I had on my SD card. I rebooted and worked perfectly once again.

As I am apparently a glutton for punishment, I changed the update channel in the Magisk Manager to the beta channel and tried to install v15.4 through the direct install method and the tablet once again failed to boot to Android and booted to a strange, not seen before error code in the android fastboot/bootloader mode.

So I once again booted to TWRP, reflashed my stock boot.img and flashed an older, unofficial build to get back to a working Android.

Once I get back to my tablet from this desktop I will upload the Magisk Manager log I saved from the direct install method.

The device is the one in my signature.
[Magisk] martyfender:
I have attached install logs for v15.4 and the unofficial build also.

It would appear v15.4 is either not patching my boot.img correctly, or not flashing it properly.

I can provide a Magisk debug log from the [MENTION=3306843]kantjer[/MENTION] build, if needed, but obviously, I can't for the v15.4, since it will not boot to Android.

Thanks for your input.
[Magisk] SourPower:
I installed new manager 5.6 on 3T, latest stable oos with xposed. No FC
[Magisk] MrBrady:
This fixes the issue with Samsung Pay (Gear) detecting Magisk. At least for me on Pixel 2 XL.
[Magisk] d.j.byrne.51201:
Yesterday, when I was on v15.3, I noticed that my SafetyNet kept failing, so I just updated to the latest Magisk and Magisk Manager, and it's still failing. Did Google patch it again?

Btw, this is on my Galaxy S5 running SkiesROM v3.2
[Magisk] Didgeridoohan:
For everyone posting about issues, provide logs or it didn't happen.

For users with FC issues for the Manager, make sure to not have any themes applied when updating, try clearing data, and if nothing else uninstall the old Manager and reinstall the new one clean (it can be found in the release thread). If it still crashes, a logcat is necessary.

For boot issues, a logcat during boot (if it doesn't loop to early) or the magisk_debug.log (/data/adb) might show something. Try a clean install (uninstall and then reinstall), and if nothing works provide installation/recovery log and a copy of your boot image.

You don't mention anything about doing a clean install of v15.4(1540)... What about that?

Nope...

Please bear in mind that this thread is not for SafetyNet issues, unless you can clearly show that there is something that can be improved upon.
[Magisk] martyfender:
I did a direct install through Magisk Manager on an older version of the same tablet in my signature and it failed in the same way,

This time I have noted the error code in bootloader/fastboot mode that it reboots to:

BOOTLOADER ERROR CODE 06

WARNING:

Multiple crash events have been reported.

Initially I flashed my stock boot.img and the previous v15.3 beta in TWRP, I had on that tablets SD card, then changed the update channel to custom to reinstall the unofficial build..

I have reverted to [MENTION=3306843]kantjer[/MENTION] 's unofficial build v15.3.1 (180211) built yesterday, until this is all sorted out.

Update: Installed Magisk Manager v5.6.0 from the Magisk-v15.4(1540).zip and it appears to function ok. I had to uninstall the the unofficial,v5.5.5 Manager version, signed with a different key, for me to be able to install v5.6.0

Thank You

UPDATE: RECOVERY LOG ADDED FOR A 3RD NEXTBOOK ARES 8A DEVICE.
[Magisk] Didgeridoohan:
By clean install I mean uninstalling any other Magisk release completely before installing v15.4(1540).
[Magisk] trax69:
Magisk Manager 5.6.0 FC. Oneplus 3t 8.10_r11 data f2fs

Back to 5.5.5, superuser not saving root pemission.
[Magisk] swat4samp:
Unfortunately this didn't work either :( Guess I have no other option but to reformat partition to ext4
[Magisk] gothicVI:
You're providing no valuable input whatsoever. Do you even follow the thread?!

LOGS of you want help...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] martyfender:
I posted a recovery log above.

Just saw this post, late, unfortunately. I tried The uninstaller I had on my older device at the time: Magisk_uninstaller-20180101.zip and it failed in TWRP for the latest unofficial build v15.3.1 (180211).

Thanks for your help. I have already spent much time on this, may try again sometime tomorrow when I am not so tired, in the mean time will stay with the working unofficial build, based on topjohnwu's commits, yesterday.

Still don't understand why the released, official beta does not work? Was it new code changes committed today, or does the unofficial build conflict needing an uninstall?

I can't give a Magisk debug log since the system won't boot with V15.4 installed, or a logcat, for that matter since it shows the splash screen twice, fails, and goes to the bootloader mode screen with the above posted error code.

Stable, 15.1--15.3, 15.3 beta and all recent unofficial builds, work perfectly on my devices.

Thanks
[Magisk] habylab:
15.4 works for me after flashing the zip directly through recovery. No FC in Magisk Manager either, 5.6 version. OnePlus 3, Oreo update.

Working for me still.
[Magisk] martyfender:
I uploaded a boot. Img from the device in my signature:

https://drive.google.com/file/d/1u-1a-biMKk7xhQdgEQqONlrta9smVfiC/view?usp=drivesdk
[Magisk] jurgenmmehja:
Nexus 5x using AICP rom with elementalx kernel. With 1540 getting a bootloop, with 1530 everything ok. Hope logs are enough!
[Magisk] ante0:
recovery.log is incomplete.

flash magisk then go back, without rebooting, to advanced and copy log.

If you reboot between the log will only show twrp booting up :P
[Magisk] yo_honey:
is LP can gain root using magisk???
[Magisk] jurgenmmehja:
You are right, uploading new recovery log.
[Magisk] XDAMaxe:
OnePlus 5, Nougat OOS, Boeffla Kernel, Substratum themes - no issues flashing to latest Magisk beta 15.4 - 1540 via (updated) MagiskManager 5.6 (as recommended).

After flashing I wiped cache and dalvik via twrp and re-themed Magisk Manager via substratum.

Voila!
[Magisk] ander3:
Magisk 15.4 beta doesnt work the Apk crash when I open, I have Resurrection Remix 6.0 Android Version 8.1 and I install like this with FC issues for the Manager, make sure to not have any themes applied when updating, try clearing data, and if nothing else uninstall the old Manager and reinstall the new one clean.

I try with 15.3 stable and the last apk of magisk 5.6.0 and crash so the problem is on the apk no on the Magisk zip.
[Magisk] Kuttoosssan:
Magisk manager 5.6 fc on 15.4.
[Magisk] Ikzy:
No problems with 15.4 and 5.6 manager on Xperia X compact running nougat 7.1 + genesis kernel 1.11
[Magisk] topjohnwu:
Edit: remove
[Magisk] ATP4:
Question a little silly: I usually use MatLog to generate logcat, but here, just after the update 5.6.0 Magisk Manager, MatLog also begin FC.

Also what other solution or application can I use to generate an logcat of the FC generated by Magisk Manager Update 5.6.0, please ?
[Magisk] swat4samp:
I'm having the same FC issues like others on latest magisk manager. I'm running Omni ROM 8.1 on my OP3. Here's logcat which I captured before opening app. Hope this helps:

https://pastebin.com/iSV6kzjf
[Magisk] Kuttoosssan:
You can use pc. But I think matlog fc because it is not getting root. Happened with me also.
[Magisk] Tecalote:
Huawei P8 GRA-L09/C432B399 - Update by direct install 15.3 - 15.4

[MENTION=4470081]topjohnwu[/MENTION] First of all - thanks for your work!

Report for Huawei P8 - rooted with Magisk 15.3 (2 installed modules: Busybox yds and SELPerm script) - installed new MagiskManager 5.6.0 (works perfect)

Changed for testing to Beta-channel

Flashed Magisk 15.4(1540) with Direct Install method

- First flashing with direct install has error (It was same during updating 15.2 to 15.3): "Insufficient boot partition size detected" - see log. I did not reboot (cause of the error), went back to the main menu and flashed 15.4 again with direct install

- Second flashing with direct install (without reboot between) was successful - see log

Found debug.log in adb after Reboot.
[Magisk] topjohnwu:
For all devices with crashing Magisk Manager, is your device running with F2FS? I've dug into SQLite source code, and found out that the error code could only be caused by requesting an atomic db ioctl only available on F2FS filesystem. I might have a solution for that but I need to first confirm the issue, thanks!
[Magisk] swat4samp:
Yes, my OP3's data partition is f2fs and I'm getting crash.
[Magisk] ATP4:
OK, thanks. I'll search to generate a logcat from the PC then.
[Magisk] Kuttoosssan:
Yes. Mine is also f2fs. Sorry for not pointing out earlier itself.
[Magisk] pkgnex:
I am on 8.1 (Pixel 2 XL) - formatted EXT4 - and both the new Magisk Manager and Magisk zip installed flawlessly with the direct install method, and I am not getting any force closes with the new 5.6 app.
[Magisk] a.vorodin:
I also have F2FS and the same apk crash. And another problem... when i tried to install Magisk 15.4 on the last LOS 15.1 from 13.02, i had an error like "can't mount vendor". The same error with 15.3. As i saw a changelog, it was many changes with vendor partition...
[Magisk] ryanfraser38:
I also have force close issue on the app, I'm on nitrogen OS android 8.1. managed to flash the zip in twrp. I don't have any themes on magisk manager. Probably doesn't help but thought I'd contribute haha
[Magisk] puschkin:
Do you use substratum theme? If so you have to use rescue zip in TWRP and then no more force close.

---------- Post added at 01:04 PM ---------- Previous post was at 01:03 PM ----------

Edit did not see you don't use theme
[Magisk] Tecalote:
The Magisk uninstaller is not available in official Thread at the moment
[Magisk] 8166uy:
I can confirm I have problems with my phone with the F2FS partitioned Data.
[Magisk] InfinityFath:
After flashing magisk 15.4, i have stuck at boot logo on asus zenfone 2. My friends tried too, and results are same. Even with verified bootsigner still stuck. Had to revert back to 15.3 :(

Btw, magisk manager is working well.
[Magisk] johnholley123:
Yep, I'm on f2fs. Interestingly enough, I've had no issues on DU but I get the crash on RR.
[Magisk] arifqur:
I am also on f2fs and get magisk manager crashes
[Magisk] Datiree:
Same here on my OP3T on Nitrogen OS Oreo with f2fs, latest magisk manager FC, previous one works ^^
[Magisk] zen2fans:
Which version for support with treble ROM?
[Magisk] ATP4:
deleted
[Magisk] Pkt_Lnt:
https://xdaforums.com/showthread.php?t=1726238
[Magisk] ATP4:
[MENTION=4470081]topjohnwu[/MENTION] , here is my logcat :

View attachment alogcat.2018-02-13-15-03-05+0100.txt
[Magisk] topjohnwu:
Thanks for the report of Magisk Manager crashing, I know the cause of it. People can stop posting logs about it now, stay tuned for a fix :good:
[Magisk] targitay13:
Sorry for long response

Magisk (patched by me boot.img) is working perfectly on my sm-g388f (galaxy xcover3)

I'm using Link2SD, Android Pay, and Root Browser sometimes.

The only thing to note is the security notification in the notification bar.
[Magisk] khanjui:
Deleted.
[Magisk] :
Is the clean installation on oneplus 5 fixed ?
[Magisk] martyfender:
[MENTION=4470081]topjohnwu[/MENTION] The unofficial [MENTION=3306843]kantjer[/MENTION] build v15.4 180213 is working on the four devices I installed it on.

However the official 15.4 beta will not, as noted in my previous posts with Magisk Manager log, recovery log and boot.img, provided.
[Magisk] Didgeridoohan:
You're really going to have to try a clean install of the official build before anything more can be said about it...
[Magisk] Marc0601:
Hey the latest magisk v15.4 is working with me on galaxy note 2 n7100 in Colt-OS rom and with the latest manager app and no problems happen with me
[Magisk] siealex:
Nexus 5x, stock 8.1, Magisk 15.4 works fine.
[Magisk] martyfender:
Ok, but the previous v15.3 beta flashes fine over the unofficial builds without the uninstall first. How should I do that, in the Magisk Manager?, as the Magisk-uninstaller-20180101.zip had an error in TWRP. The latest uninstaller link in the official thread is dead, giving a: Invalid Attachment specified. error.
[Magisk] Didgeridoohan:
The uninstaller link hasn't been updated (that will be fixed), yes, but the uninstaller is still attached to the OP...
[Magisk] siealex:
I flashed 15.4 over 15.3 beta in Magisk Manager, everything works fine.
[Magisk] sukesh pabolu:
Latest magisk launcher is not working on OP3

BTW I am using PE 8.1 rom
[Magisk] Didgeridoohan:
Number one rule of xda, search before posting...

https://xdaforums.com/showpost.php?p=75553143&postcount=5067
[Magisk] Ja_som:
Also booting?
[Magisk] topjohnwu:
Magisk Manager F2FS Crash Fix - Attempt 1

Can anyone with Magisk Manager crashing test out the APK in the attachment and report whether it works or not? Thanks!
[Magisk] txuki2005:
Working in OP3t with Nos 8.1

Thanks man!!

With f2fs data ☢️
[Magisk] ATP4:
I just tested, it crash again.
[Magisk] siealex:
Yes, everything works.
[Magisk] txuki2005:
Not luck now, i Reboot my device and app crashing...then.

Sorry.
[Magisk] Ja_som:
Nope, boot still hangs on Google screen, need reboot again and again to boot to system.
[Magisk] siealex:
I'll check it, but today my phone started bootlooping, it needs hardware repair...
[Magisk] Mkkt Bkkt:
Working perfectly on my Mi5 Running AEX Mod 5.2 Android 8.1 today build with F2FS.

Thank you
[Magisk] swat4samp:
Still crashing with same database related error on OP3 running omnirom 8.1
[Magisk] miksontije:
Im on ABC rom,only magisk work for me is 14.5,with stock apk.

Every new version i try,i cant pass boot,or manager cant save superuser aplications
[Magisk] kryzeK:
Still crashing on my OnePlus 3T running Omni 8.1 and Magisk v15.4. Logcat attached.
[Magisk] topjohnwu:
May you try reboot and see if it works?
[Magisk] Nelinski:
Still crashing for me even after a reboot. Oneplus 3t with lineageos.

Let me know if you need any more logs.
[Magisk] kryzeK:
Still crashing unfortunately. Need a more logcat?
[Magisk] Sam Nakamura:
Still crashes on f2fs, RR6, even though I can run magisk 15.4 with magisk manager 5.5.4, it's just magisk manager 5.6.0, of course no theme, uninstalled old before installing 5.6, cleared app data, rebooted, dirty flashed ROM & magisk 15.4, no matter what it keeps FCing...

I gladly provide logs if needed but I think you already found the potential issue - thanks for the awesome support!
[Magisk] BertlBrown:
deleted.

(Reason for failing may be things having another reason and writing to a looped image on /cache is failing too these days).
[Magisk] 8166uy:
Fix also not working for me, even after clearing caches in TWRP.
[Magisk] BertlBrown:
I tried "setenforce 0" before, but I wondered about that I could go with it. If I would do such an obscure security thing, I wouldn't let people turn it off that simple. I guess, that it has an effect on your own context, but not on the kernel's. So it keeps failing because it's the kernel writing to the file.

Next thing i did was taking a look at /sepolicy. Without understaning anything I could make some observations:

- adb_data_file belongs to a group data_file (it's called attribute data_file), sdcardfs does not

- it says, that theres only one permissive type (su), all other place restrictions

I tried some things and found out:

- it needs setenforce 0 to change the context (chcon) of magisk.img to sdcardfs

- this doesn't help. I guess it's because the restrictions of the /data directory still apply as sdcardfs isn't that single permissive type

- /cache is locked, too. Thats why the F2FS Loopback Bug Workaround from [MENTION=5228676]VR25[/MENTION] mentioned by [MENTION=8126387]martyfender[/MENTION] won't help

- simply moving magisk.img or magisk_merged.img does not work, as magisk is recreating those files at startup

[MENTION=4470081]topjohnwu[/MENTION]

So this will need support for relocating img files via magisk itself.

Or it needs something like the F2FS Loopback Bug Workaround, but moving files to /data/media and using /storage/emulated as symbolic link target.
[Magisk] Wolfcity:
deleted
[Magisk] BertlBrown:
deleted
[Magisk] Wolfcity:
Ok, deleted my post already too.
[Magisk] ryanfraser38:
Doesn't work for me on Nitrogen OS it freezes on opening screen. Have tried reboot
[Magisk] cimdrap:
I'm on RR 6.0 and magisk manager 5.5 works, but 5.6 crashes
[Magisk] DeeZZ_NuuZZ:
[MENTION=4470081]topjohnwu[/MENTION] I flashed magisk v15.4 directly from app on my Huawei mate 10 pro. But it always kept rebooting into bootloader and I couldn't Catch a log, even the kernel log was empty. Is there another thing/way I can get a lot for you?
[Magisk] samTRG:
Dirty flash NOS OP3t 12/02 from 10/02, with nano gapps + magisk v15.4 + latest caesium kernel. Use more than 24h w/o error.
[Magisk] Neverendingxsin:
What's the proper way to update a stock pixel 2 xl with magisk root to the latest factory image?

Would it be:

-Uninstall magisk through app

-Flash factory image with -w removed

-Put latest boot.img on phone and patch with magisk

-Flash the patched boot through bootloader.

I tried just straight flashing the factory with -w removed but it wouldn't boot fully, just said it was corrupt and sat at the G logo, so I'd like a little guidance before tinkering again.
[Magisk] eternal70:
On AEXMod gemini, oreo 8.1, magis 15.4 are causing heavy lags and black screens.
[Magisk] otonieru:
I just flash factory without W and reflash everything back on. Works just fine.
[Magisk] Neverendingxsin:
I've tried that and it won't seem to work properly :(
[Magisk] drewski_1:
+1 for issue with v15.4(1540) on the Pixel C.

it hangs on the "Google" logo and never reaches the next stage with the boot animation.

reverted back to v15.3(1531). i'll see if i can grab a logcat during boot tomorrow.
[Magisk] martyfender:
My device did not hang on the bootlogo, it just errored out and went to bootloader mode with a 06 error code. The unofficial, 15.4 180213 works great, though. Anybody have any clues why? It appears that the official beta did not patch or reflash the boot.img properly.
[Magisk] habylab:
I am on F2FS, no issues.
[Magisk] ptoner:
Was hoping v15.4 woul dhide the new Santander Banking app, but it doesn't, it used to work fine with the old Santander app. Is there any way to get it working again?"Santander UK version 4.0.0 (17)
[Magisk] Kuttoosssan:
Crashes.
[Magisk] Ja_som:
Read OP:
[Magisk] EViollet:
Using a custom kernel? Is so, reflash the kernel after flashing Magisk.

Regards
[Magisk] lil_ith:
Don't you lose magisk if you do that because it's not on a modified boot.img anymore?
[Magisk] Berlino:
+1 here as well with 15.4 on the pixel c stuck on google splash screen...back to 15.3 for the moment.
[Magisk] lorenzo.pierini:
Test performed with RR v.6.0.0 (Oreo) + Magisk 15.4 Beta : crash again
[Magisk] Hedigehog:
OUKITEL K6 bootloop Magisk v15.4 (1540)

On flash Magisk v15+ OUKITEL K6 catches bootloop, but at v14 it's ok. How to solve a problem?
[Magisk] DeeZZ_NuuZZ:
like I said, this won't work, as it only goes to bootloader, not even bootanimation. can't grab a logcat

EDIT:

okay nvm, found the magisk zip for Huawei treble enalbed devices :P
[Magisk] sd11aa:
fc on f2fs file system，magisk manager 5.6.0
[Magisk] Ja_som:
You are in the beta thread, so if you want to report an issue, you should do it in proper way.
[Magisk] EViollet:
No. And it's even necessary.

If you don't do it, you won't be using the correct boot.img for your kernel and will face multiple issues.
[Magisk] cmattern:
FWIW using 15.4 on Pixel 2XL running Carbon 6.1 with no issues.
[Magisk] lil_ith:
I'm not sure what phones have to do that but and I'd really like to know/proved wrong but the correct order for every device I have owned has been rom>gapps(optional) >kernel(custom choice) >magisk. So magisk applies on the boot.img....have had no issues doing it this way. If you restore boot.img or flash kernel zip again. You are basically flashing an untouched kernel without magisk (at least for every device I have been on)

Unless magisk persists through kernel flashes which would make sense. But the boot.img doesn't change since the kernel is just patched?
[Magisk] dr4go:
Please see https://xdaforums.com/showpost.php?p=75257893&postcount=4924 or ask master [MENTION=3989065]serajr[/MENTION] directly... Long story short: I'm pretty sure there are no issues left.
[Magisk] EViollet:
The correct order is custom kernel LAST.

You can find complete instructions here: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] lil_ith:
I am going to restore my stock boot.img...flash magisk and then custom kernel just to see. But if that's the case, I have been wrong all this time. I will respond with an edit to this post.
[Magisk] bnwg:
I want to report my problem of stock camera with latest Magisk Manager 5.6.

My devices is HTC U11+. Stock recovery. Rooted by Magisk via Fastboot flashing patched boot.

After updated Magisk Manager from 5.5.5 to 5.6, it took around 5s - 6s for stock camera app to response. I confirm that the camera works fine by restoring stock image and uninstalling Magisk Manager.