yashsingh1/xdaforums huggingface dataset:
[Magisk] godofsalt:
Well at first, reading all the problems with Magisk 15.40, thought I better wait.... Seeing how my Manager only seen the App update...

I did for 5 minutes or so. Downloaded 15.40. I also made sure, through Magisk Manager, that I had no updates to any module I use, or have.

In short, went to Recovery, wipe cache and Dalvik. Flashed Magisk 15.40, wipe Cache an Dalvik cache, and rebooted.

Can state, "Boot" did take a bit longer, however that was the only issue that I had.

Working as normal on Samsung Gaxaly S5, on LineageOS 14.1 (latest build for SM-G900P)

Works as it has prior to the update!

Awesome

I Thank you Topjohnwu and all that Dev's, for all the time an work on this. Can't wait to see what you have cooking now! Didn't give out much info other than a teaser...
[Magisk] SimplyCity:
Hi devs. VNS-L29 (Huawei P9 lite), stock rom and kernel (data encrypted), no issues. Great work, much appreciated. SN pass without any patch. :)

Echoe[emoji769] team member / VNS-L29
[Magisk] faz712:
what I always do on mine is:

• pull out latest boot.img from factory image download

• transfer latest boot.img to phone

• create patched boot.img on phone

• transfer patched boot.img back to PC

• adb reboot bootloader

• run flash-all.bat (with -w removed)

• fastboot flash boot patched boot.img

• fastboot reboot

has never failed me
[Magisk] madbat99:
It does indeed say "flash custom kernel last" in the instructions in the first post in the main magisk thread.
[Magisk] lil_ith:
I think alot of people are used to su steps and haven't strayed from it. But I've honestly had no issues flashing Magisk last at least on the devices I have had. But I'll do it that way from now on. Thanks all for the enlightenment
[Magisk] drewski_1:
can't establish an ADB connection with just the "Google" logo.

it looks like since the problem occurs so early, i can't get a logcat via ADB.

any other ways to help provide troubleshooting details? as mentioned, this is on the Pixel C so has the hybrid ChromeOS type boot image.

---------- Post added at 08:00 AM ---------- Previous post was at 07:52 AM ----------

wouldn't it depend on if the Custom Kernel is flashed as a Zip with something like AnyKernel or if flashing a full Boot.IMG?

the former would maintain Magisk RAMDisk changes, while wouldn't the later process reverse / remove Magisk changes?
[Magisk] Rizezky:
Reporting in. Magisk manager 5.6.0 crash upon opening, whether with v15.3 or beta v15.4, try to use 5.5.5 only to granting over and over again on the previously granted app. Currently on CandyRom Oreo 8.1 Oneplus 3, it was fine on 8.0 though
[Magisk] jcmm11:
That's true, but every kernel I know of (there may be some exceptions out there) is using Anykernel. The only time I can think of that you'd be flashing an img file is when applying a stock image. If you back up a kernel to an img file after applying magisk then, obviously, when you restore it you'll still have the magisk patches applied.

I sometimes use this fact to short circuit reapplying root. TWRP backup boot, apply system zip (eg custom ROM) which leaves data untouched. Restore boot. Root preserved.
[Magisk] pWEN:
I've been doing Magisk last on my Pixel.

I flash stock, boot TWRP, flash ElementalX. Then I make a backup of the boot image. Then I install the Magisk Manager app and use that to patch the backed up boot image. Then I flash that patched backup.

I have not tried this with the latest February versions of any of those yet, though, but that's how I plan to do it.
[Magisk] jasonstackhouse:
Curious to know if anyone else is having connectivity issues with Bluetooth after flashing the latest beta 15.4 (1540) update? I can not recall this issue taking place on any previous versions of Magisk and I am currently running version 15.3 (1531) with no problems.

The connection issue seem to be isolated to using Bluetooth in my vehicle. It basically just connects and disconnects over and over, rather than keeping a stable connection. Once I revert and flash an earlier version the problem goes away. I tested my Bluetooth connection with my other devices that i use more often such as fitness tracker and headphones (all connected via Bluetooth) and I am not experiencing any issues. This is obviously not a pressing issue, I am just more curious than anything if anyone else has this issue and if anyone has any idea what might cause the connection problems specifically taking place in automobiles/my automobile? Thanks.

Currently running Pixel 2 XL, stock, rooted (obviously)

Car 2013 Honda Civic SI (HandsFreeLink)
[Magisk] habylab:
Thanks for this post, as it let me know they had a new app! I was previously using SmartBank, which they've removed from the store...

Anyways, this works for me. Maybe try a fresh install?
[Magisk] topjohnwu:
Build Magisk from source and check my compiled binaries before trusting some stupid antivirus app.........

I thought it is common sense that antivirus apps on Android are all BS.
[Magisk] altwu:
sorry [MENTION=4470081]topjohnwu[/MENTION], i just found another thread asking about this. when i searched earlier it wasn't there. please know that i wasn't accusing you of anything. sorry if it came of that way. i was posting what i was seeing and wanted to get clarification.
[Magisk] neekless:
Does magisk beta 15.4 and/or manager 5.6.0 break fingerprint su request? My fingerprint works for unlocking device and other apps but I can't use it to grant su access despite turning on the option in manager; it shows 'grant' instead of the fingerprint icon as if I didn't turn on the option. It worked in previous stable magisk and previous manager version.

Edit: uninstalled and reinstalled manager and fingerprint works fine now
[Magisk] will5:
I had bt problems with all magisk builds that I tried, 14 to 15.3. Sixaxis app just wont sync when using magisk.

Didnt tried 15.4 since I switched to supersu to be able to use that app.

Im using lg v20 h990ds.
[Magisk] jason6g:
-

Hopefully someone can explain what I’m doing wrong here. When I updated to the January ota I uninstalled magisk with restore images, applied the ota update and when it got to step two, I installed magisk to second slot and all worked perfectly.

Now, when I tried to do that for the February update, my stock backup didn't exist so I downloaded the factory image to my computer, took out the -w and successfully updated via flash_all. I then pushed the new boot.img to the phone, patched it with 15.3 and also 15.4 (both boot looped), and pulled & flashed to see a boot loop when restarting. I can flash factory just fine and the phone works without root, but I’d like root =)

Pixel 2xl running taimen-opm1.171019.018-factory-e96a86ae
[Magisk] Badger50:
I'd fastboot the twrp.img, which is temporary, then when you enter twrp, flash magisk 15.3 or 15.4 (your choice) Remove all lock screen security before you do if you choose this method. Also, if your flashing factory images, why bother with OTA's??
[Magisk] jason6g:
Hmm makes sense. I got the sense to avoid messing with recoveries on the newer phones a few years ago. I like the ota method as I can do it on the go without a computer. What's the harm of putting twr on permanently? I mainly want root for adblock and a couple other minor conveniences, what would be an easy upgrade path going forward?
[Magisk] Badger50:
While twrp is a little wonky right now given the lock screen issue on the P2XL, many of us have our own work arounds. Myself, I disable the lock screen and set it to swipe. Others push things with adb, and some just use temporary twrp and leave stock recovery in place. There is no harm leaving twrp on the P2XL, as I do. When the monthly updates come, you already know what to do, since you just did it. You can flash the factory images without wiping data as well. The choice is yours of course, but it's what I have done the past 2+ years and it's really easy as well. Not to mention, depending where you live, factory images come out a little quicker I think ??
[Magisk] martyfender:
[MENTION=4470081]topjohnwu[/MENTION]

I removed Magisk, reflashed my stock boot.img, and flashed the 15.4, beta as was suggested and it still boots into bootloader mode, just the same as before.

The unofficial v15.4 180213 works just fine, as before.

Apparently the official 15.4 beta is not either patching the boot.img properly, or it is not flashing it correctly.

Why is this? They both should be built from the same source code.

Magisk debug log from the unofficial attached this time, after the failure with the official beta.

Here is a link to my stock boot.img:

I believe it is shared properly this time without having to get access authorization through email as before. If not, let me know.

https://drive.google.com/open?id=1u-1a-biMKk7xhQdgEQqONlrta9smVfiC
[Magisk] ptoner:
Yeah, tried all the hide methods, still couldn't get it to work. Do will flash boot img and reflash etc.
[Magisk] habylab:
After a reboot, it isn't working for me now. Not sure what it is, will look into getting logs when possible.
[Magisk] topjohnwu:
Magisk Manager F2FS Crash Fix - Attempt 2

The issue narrows down to Android 8.1 custom ROMs with /data formatted as F2FS. Please test this APK and report, thanks!
[Magisk] Sam Nakamura:
Still FC's, RR6, f2fs...

Tried uninstalling old before reinstalling new, reboot, etc.

Log?
[Magisk] topjohnwu:
Sure
[Magisk] NewKindOfWorld:
Using F2FS, and have magisk manager fc since the first 5.6 release, and latest fix attempt crashes too for me. (RR 6.0 Oreo 8.1, latest magisk 15.4)

Using previous working version keeps asking for root for every app.
[Magisk] Sam Nakamura:
Log

https://drive.google.com/file/d/1_BtdfBcoz-9Q3Fpc78HVCbYwPnRIgOJu/view?usp=drivesdk
[Magisk] topjohnwu:
May you give me the output of the command

mount

Thanks :)
[Magisk] Sam Nakamura:
Sure, here you go...

https://drive.google.com/file/d/1n9msQLn1Y8vTgGF2n-M5f1ji06omvhKM/view?usp=drivesdk
[Magisk] kryzeK:
Still crashing, even after a reboot. Both logs attached.
[Magisk] ATP4:
Still FC

View attachment logcat.txt
[Magisk] KaMyKaSii:
I believe that [MENTION=4470081]topjohnwu[/MENTION] is already aware of this information, but just to confirm, in the link below arter97 talks about SuperSU issues with F2FS filesystem, it may be similar

https://xdaforums.com/showpost.php?p=70492947
[Magisk] SacredDeviL666:
did a little clean up of unwanted bitcoin false reports....

Trust us when we say this if it was even close to having any code of bitcoin or miner we will remove it even before you all get a chance to install :)

So you all can trust and install it without worries and if you cannot stay away from this beta thread as this thread is about troubleshooting of beta builds with logs and not a how to install thread.:good:
[Magisk] Sebastl:
[MENTION=5065917]BertlBrown[/MENTION]

Thanks for you additional ideas.

I have to admit i excluded SELinux as i thought that permissive mode would be kind of global and because i didnt see any avc denials in the logs.

But that could also be because of the dontaudit policies.

Also adding androidboot.selinux=permissive to the boot.img didnt work. But i didnt follow that path further.

Anyway, i dumped all the policies from that phone and those from an older MTK Device where mounting works.

Unluckily the old one doesnt use sdcardsfs, which could be involved. See bottom

Furthermore i adapted VR25's FS Module to use different locations and also setting the exact same owners and SE contexts as magisk.img has in /sdcard (root/sdcard_rw and u_object:sdcardfs:s0).

I symlinked to /sdcard (not mounted yet at initialisation -> magisk creates a new img), to /data/media, to /data/data (dealt with by seapp_contexts) /cache/recovery (handled differently according to the policies) and /data/local/tmp (excluded from restorecon).

Neither worked in TWRP (flashing the Module) nor in booting up.

For getting logs (except strace) i switched to the MTK Logger (available from Engineering mode). Easier to handle and more logs ;)

Another thing regarding logging:

When comparing the boot logs from both phones, AEE_AED throws ipanic_blk_open after get expdb_path.

Did you see anything similar ?

And now to the next finding in this neverending story:

As your successful test showed, maybe sdcardfs is somehow involved.

So i deactivated sdcardfs (corresponding entries show up as fuse afterwards as expected) and was NOT able to mount/write to the img in /sdcard anymore.

Switched back to sdcardfs => works again. But i did also not see fuse avc denials.

Can you replicate that ?
[Magisk] vMAC:
So in reading through this thread I've got a couple other people that appear to have a similar issue as I have had.

I am getting an error

mount /dev/block/loop1->/dev/tmp/magisk_img failed with 22: Invalid argument

I get this error on any module that I try to install.

I am currently trying this on a Pixel 2XL on January Update 8.1.0 and running Magisk 5.6.0 and MM v15.3.

Any advice would be great.
[Magisk] PriPhaze:
I was gonna give up on oreo 8.1 until this was fixed but ... it did for me?

I mean ... last fix attempt still FC but if i extract the magisk apk from 15.3 (1531) and install it then everything is working!

No FC , the SU List is working as intented and the apps that accesed root appear there.

I clean flashed ROM/Gapps/Magisk 15.4/installed attempt 2 apk/tried and failed then rebooted/uninstalled apk/ installed 5.5.5 apk.

(Gotta say that after installing the attempt 2 apk and trying it out it kinda took a little bit of time to force close... it was inmediately before)

Bootleggers 8.1 ROM Xiaomi Redmi Note 4 Data/Cache F2FS.

NVM: Weird but only 2 of my apps got registered , the others won't and keep asking for root everytime i open them. meh :c
[Magisk] martyfender:
This is a follow-up on my previous post. I used the latest Magisk uninstaller just reposted yesterday, in TWRP. I then reflashed my stock boot.img, followed by the Magisk 15.4 official beta and yds busybox 1.28, wiped dalvik cache and cache and once again the device rebooted to bootloader mode with error code 06.

I forgot to point out before that when booted to bootloader with the error, that I must hold the power button down to shutdown, as none of the reboot menu items in bootloader mode will work.

Once shut down I can reboot into the normally seen bootloader mode, where all of the selectable reboot menu items work. I then select recovery, then it reboots to TWRP.

I saved the recovery log and kernel logs, attached here. My stock boot.img was posted in my previous, more recent post.

Finally, I once again reverted to the latest unofficial, 15.4 180213 to work great, once again.
[Magisk] khaytsus:
Have you tried the Feb on Pixel (1 I assume?) yet? Any luck? I haven't tried yet myself.
[Magisk] habylab:
[MENTION=5442704]ptoner[/MENTION] I have had success by choosing the option to hide Magisk Manager.
[Magisk] ptoner:
Yeah that didn't work for me, or a clean install of 15.3 either.
[Magisk] Shadow Waffle:
I tried to install Magisk on my OP3 running a fresh install of AOSP Extended (Android 8.1). Unfortunately, it force-closes every time I try it.

At first I flashed it after system, now tried uninstalling and installed Magisk Manager apk alone. Still, the issue remains.
[Magisk] skawtnyc:
Flashing the unified Tegra kernel for Pixel C *after* flashing magisk 15.4 resolves the frozen boot issue. Apparently it works on most devices using a custom kernel. I'm running 15.4 on my Pixel C and it's functioning properly.

https://xdaforums.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
[Magisk] closedcircuit:
With AEX 8.1 you need to uninstall Magisk Manager 5.6.0 and install 5.5.5. You will still have root prompt issues, but to overcome this problem: After a fresh install start up all apps that require root and grant root, then finally open Magisk Manager. All apps with granted root will stick if granted before 1st start of Magisk Manager upon a fresh install, but after that initial start any additional apps that require root will prompt for root every time.
[Magisk] johnholley123:
Or, you could try this version of Magisk Manager and see if it works properly.

Edit: Click/tap on the post quoted below to go to it and download the attached apk.
[Magisk] khanjui:
Exactly same with my Xiaomi Mi 5s Plus on LineageOS 15.1 (Android 8.1.0) with F2FS /cache and /data.
[Magisk] cdwarak:
The Magisk Manager F2FS Crash Fix - Attempt 2 works. I did the following - uninstalled the magisk manager apk. rebooted to recovery (twrp bluespark) flashed the Magisk Manager F2FS Crash Fix - Attempt 2 zip. Rebooted and the app FC'ed. Uninstalled the magisk manager apk, and installed v5.5.5. downloaded the magisk 15.3(1501) from within the magisk manager. Rebooted to recovery and installed magisk 15.3(1501). Now it works perfectly and the f2fs issue is gone. Root stays for all apps that were granted permissions. I am on omni rom android 8.1 oneplus 3t.
[Magisk] NewKindOfWorld:
I'm not sure I understood everything, but in your case, the fix is not working, because you just use magisk 15.3 with 5.5.5/6 manager ?

I'm using magisk 15.4 and I just installed 5.5.5 apk, working, but sometimes it asks for root :)
[Magisk] Berlino:
Thanks for the hint, but I'm running Dirty Unicorns on my Pixel C and like to keep the built-in unicornblood-kernel.
[Magisk] skawtnyc:
The unified kernel from followmsi has both Unicorn and Xceed. NYCHitman1 actually helps followmsi integrate his code into the unified kernel.
[Magisk] johnholley123:
This is not how you are supposed to use the f2fs fix. The proper way is to have magisk 15.4 with magisk manager 5.6.0 installed and then uninstall magisk manager 5.6.0 and install the Magisk Manager f2fs fix attempt 2 apk. No flashing anything is required. I recommend that you try again with these steps.
[Magisk] jcmm11:
That would remove root. You'll be replacing a patched image with an unpatched one. (As opposed to merging, which is what happens when you flash a zip file built with Anykernel)
[Magisk] NoSpamDan:
Sounds like you have the app but not rooted.
[Magisk] Shadow Waffle:
Unfortunately I had multiple issues regarding AEX performance and was forced to use another ROM.

Just installed Resurrection Remix (OP3, Android 8.1) and the issue remains. I used the latest beta build and flashed it after ROM and GApps.

I am now going to use [MENTION=2922000]cdwarak[/MENTION]'s solution. I will report whether or not it works.
[Magisk] Shadow Waffle:
Can confirm. The latest beta (v15.4/v5.6.0) kept crashing instantly (attached logs from it to this post.)

The F2FS fix attempt 2 apk would still crash but after 1-2 seconds. Didn't save logs from that, unfortunately.

I now completely uninstalled Magisk Manager (with Magisk v15.4 still installed via zip) and installed Magisk Manager v5.5.0 extracted from the flashable zip.

I does start, Magisk Hide works properly, didn't install any apps yet but hey, at least it starts. I hope you can fix all the issues regarding Oreo 8.1 very soon, Magisk is the best!
[Magisk] ticklemepinks:
What steps should be taken to update? Flash the uninstaller or can I enable core mode then just flash the update
[Magisk] smohanv:
Thanks. Are you confirming that safety net works with modules in magisk 13. I am still on magisk 12 and safety net works only of I select core only mode and restart my device.
[Magisk] demonoidmaster:
My guess is yes lol
[Magisk] ryaniskira:
Still failing for me. Even in core-only mode on the latest beta. :(
[Magisk] multi_rom_user:
The download link says ~"couldn't parse URL". How do I get the bundled version?~ edit: I got the link working, it's still not a bundled zip with the latest APK. Where do I find the v5 APK?
[Magisk] Setialpha:
There's not been an new beta posted since that post, so of course not.
[Magisk] Artim_96:
...scroll down to the end of the post? Or just use a different browser? It only gets me that in XDA Labs but then I just tap it and it asks me which browser I want to use
[Magisk] Artim_96:
View attachment 4181179

Me too, since yesterday's play services update. I used to pass at least basic integrity, but now even that is failing. And the Magisk log (from core mode) even mentioned a crash...

Emotion OS, based on LOS 14, 7.1.1 patch level February
[Magisk] Facebooook:
I use oneplus 3 with oxygenos with custom kernel.

Is there any way to update magisk without flash back to stock boot.img every time ?

Because i need to do..

1 flash magisk uninstaller.

2 flash stock boot.img

3 reboot twrp and flash magisk new beta.

4 reboot and check safety net.

5 flash custom kernel.
[Magisk] cafe-creme:
The current version of Magisk (dirty flash over V12) works without any particular worries.

To switch to SafetyNet i have disabled the active modules. To test a search in the Play Store (certified), "netflix" no longer appears. A little feedback.

Magma NX rom (MM) Note 7 ported/Samsung SM N9005/kernel phantom
[Magisk] davidcd13:
If I install Unified Hosts Adblock module on magisk v13 beta, safetynet check fail. No problem with V12.
[Magisk] smartdetodos:
I did a test ... and worked It in my particular case... steps and considerations.. read It (maybe works with Custom ROMs)

https://xdaforums.com/showpost.php?p=72665469&postcount=27
[Magisk] Shished:
I liked old (4.3) app UI more than in the current version.

3 green lines with check marks looks better than bunch of text.
[Magisk] Kloosek:
You will update v12 too? I ask, because v13 doesn't work for me.

Wysłane z mojego LG-H850 przy użyciu Tapatalka
[Magisk] lalitjoshi06:
Confirmed

With Current Beta version 13.0(b3da28e) need to disable modules to pass safetynet. (due to safetynet policy changed By google.)
[Magisk] DarkMi100:
SafetyNet check fails having modules installed in Magisk Beta v13.0

Just ignore my post, I didn't read the last post made by alitjoshi06. :D

I use OnePlus One (bacon) with latest LineageOS 14.1 and latest Magisk Beta v13.0 (b3da28e).

After installing one or all of the following modules SafetyNet check states "Success" but both ctsProfile and basicIntegriy fail.

Android Mic Fix v3

Audio Modficiation Library v1.4

Dolby Atmos r6.5-c

Universal deep_buffer Remover v2.4

I had the same issue with Magisk Beta v13.0 (1e87780).

With Magisk v12.0 I had no issues with SafetyNet check having Magisk modules installed.
[Magisk] de.er:
Guys,

in the light of latest info from [MENTION=4470081]topjohnwu[/MENTION] (see HERE) there doesn't seem to be any need to keep reporting SafetyNet failures. The dev is obviously aware of the problem and already working on it (apparently with some positive outcomes). Be patient, please.
[Magisk] ForgottenDude:
I don't think it was a good idea to tag Google in the tweet. :p
[Magisk] Sytis:
I bet he also smokes a joint directly in front of a police department, he is just too savage and knows he is faster than Google :p

Btw. latest Beta working without problems here on the OP3 with latest LineageOS weekly.
[Magisk] t e i t a n b l o o d:
[SIZE="1"]--------- beginning of main
01-23 09:24:38.068 946 946 D Magisk : client: connect fail, try launching new daemon process
01-23 09:24:38.170 954 957 D Magisk : sepol: Starting large patch thread
01-23 09:24:38.170 954 954 I Magisk : Magisk v13.0(b3da28e) daemon started
01-23 09:24:38.171 954 954 E Magisk : mount (null)->/ failed with 1: Operation not permitted
01-23 09:24:38.171 954 954 E Magisk : chmod /sbin 493 failed with 30: Read-only file system
01-23 09:24:38.171 954 954 E Magisk : chmod /magisk 493 failed with 2: No such file or directory
01-23 09:24:38.171 954 958 I Magisk : ** post-fs mode running
01-23 09:24:38.910 954 957 D Magisk : sepol: Large patch done
--------- beginning of system
01-23 20:24:45.660 954 1024 I Magisk : ** post-fs-data mode running
01-23 20:24:45.686 954 1024 I Magisk : * Mounting /data/magisk.img
01-23 20:24:45.686 954 1024 E Magisk : mount /dev/block/loop0->/magisk failed with 2: No such file or directory
01-23 20:24:47.638 954 1452 I Magisk : ** late_start service mode running
01-23 20:24:47.638 954 1452 I Magisk : * Running service.d scripts
01-23 20:24:47.638 954 1452 I Magisk : * Running module service scripts
--------- beginning of crash[/SIZE]

Getting no root/no magisk installation. Using Sony Xperia Z2 D6503, existenz MM rom, elitekernel.v3 kernel.