yashsingh1/xdaforums huggingface dataset:
[Magisk] Wolfcity:
Your device has the so called loopback bug.

Your data partition is f2fs formatted and in correlation with your kernel img files can't be mounted r/w.

Three ways to solve it:

- Flash a custom kernel like ElementalX.

- Reformat your data partition to ext4

- Use the Loopback bug module by [MENTION=5228676]VR25[/MENTION]

I did the last, just flash the module through TWRP, maybe twice until it shows up in the modules of Magisk Manager. It moves magisk from data to cache partition and is working well.
[Magisk] glewo45:
Thanks brother, yes it's works using loopback bug module

One question if data formating to ext4 without flashing custom rom does it's not causing bootloop?
[Magisk] Wolfcity:
You're welcome.

I'm not sure. As /data is decrypted and will be encrypted while flashing stock it may work, some users posted that they successfully reformatted to ext4 but I'm not sure on which device.

I never tried it and until there's no need I won't do it.
[Magisk] bennebartsch:
Magisk 16.1 on my Galaxy s9 (sm-g960f) ends in boot loop.

Log: file-upload. net / download-13030771 / recovery.log.html

Please remove spaces, i cant post links....
[Magisk] _alexndr:
Above link has been detected as dangerous and blocked in my web browser. Could you just zip your recovery.log and then attach as zip file to your post?
[Magisk] bennebartsch:
oh, i'm sorry! I'm new to XDA and i can't find the option to attach files (maybe because i have less than 10 posts?)

I uploaded the log as zip file, maybe this works: https: // ufile.io/ u6cpe
[Magisk] _alexndr:
Your recovery.log does not contain any information related to installing Magisk

Try again, then go to "Advanced" in TWRP -> Swipe "Copying Logs to SD card..." (you do NOT need to tick "Include Kernel Log")
[Magisk] bennebartsch:
Thank's i'll Post my logs later!
[Magisk] bennebartsch:
Next try: https: // ufile.io/uxtvb
[Magisk] Normola:
Would appear that all s9 users are having this same issue. Attached logs.

Additional note: We're running a slightly altered boot image that disables dm-verity and forced encryption. Not sure if it might cause issues.
[Magisk] Jaymin.0.1910:
There is nothing related to Magisk in your logs

Recovery logs did not say anything, grab logcat
[Magisk] MysteryIII:
On Galaxy S5, and as I read in another forum for some other Samsung Devices, Magisk hide stopped working beginning with v15.4. 15.31 is the last working Version on my S5.

In /data/adb/Magisk is no debug log, no matter which Version (v15.3-16.1). Magisk log stays empty beginning with 15.4.

If I choose anything in Magisk hide section, the hook is gone once I leave the section. Also de- and reactivating Magisk hide doesn't change the fact and Magisk log stays empty.

As I don't really know what you need to know to look into it I made logs of working 15.3 and not working 16.0 to compare if necessary. Also I saved file on "debug" log level and "warning" log level, so you you might get more information if necessary.

All this happens on a fresh and totally unmodified G900F Stock ROM (latest Version CRA2). Nothing beside Recovery (TWRP v3.2.1), matlog and file explorer installed.

Here you get all logs. Couldn't attach them because of size limit.
[Magisk] SacredDeviL666:
Few posts moved to https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page2362 :highfive:
[Magisk] chicato83:
Recovery log after install magisk beta 16.2 on my Doogee Mix 6/64GB Android 7.0.

The second one I was trying to install ANUIR Audio and I got the same error that I have with other magisk zip.

It said the magisk img couldn't mount.
[Magisk] godofsalt:
Well I know for fact the Galaxy S5 (sm-g900p) does work on the actual "Updated" Magisk, which in this case is actually 16.2 (at this posting) IS working just fine.

Not 100%, but I thought that IF on stock, you need to also install a different Kernel. I always have. Plus I need to note, I am on LineageOS 14.1 w/ different Kernel. At present also have GApps an just updated to Magick 16.2... All is well.

Might want to look into a "Newer" ROM.
[Magisk] MysteryIII:
I just uninstalled 16.0 and flashed 16.2. Beside Magisk hide being deactivated as default (because Log is empty as Changelog says), nothing changed. 15.31 is the last working Version for S5 Stock.

Well if you are using LOS, it's almost as if you are using a different phone. LOS is beside of driver necessary mostly generic. You could say you're on a LOS 14.1 phone, as there mostly won't be any big differences between the manufactures.

Especially Samsung changed many things of there ROMs like Art-Cache itself, these changes get "lost" on all AOSP/LOS based ROMs. I again added Logs, but it's the same for all Magisk versions starting with 15.4.

Don't get me wrong, I also looked into LOS (actually RR) ROM and I don't dislike it, but when it comes to software you can't say you are on a Samsung Phone any longer.

Beside: of course you must have Gapps installed as they are part of the SafetyNet. No Gapps = no SafetyNet check = no working App checking for/by SN.

Here are some detailed information about SafetyNet if you're interested in it.
[Magisk] Sam Nakamura:
Magisk 16.2 finally successfully patches my mediatek boot image but when I later flash it (without errors in TWRP) it hangs straight at the lenovo splash screen without reaching the boot animation....

Someone successfully patched mtk on magisk 16.2?
[Magisk] NevaFreeze:
Pixel XL Bootloop on 16.2

Hi,

I've flashed both magisk 16.1 and 16.2 and both flash perfectly fine with no errors but upon restart android hangs at the Google Loading screen and crashes to twrp. Attached are the Recovery.log and Magisk.log

Edit. Currently not allowed to post my outside link to drive
[Magisk] Telperion:
Similar issue here, except for me 16.2 booted properly the first time, then went into a bootloop after I updated Ainur Sauron and installed Greenify4Magisk. I had to re-flash the factory image to get my phone to boot. Each time I try to flash 16.2, I bootloop and have to re-flash the factory image. Flashing a stock boot doesn't even work.

My TWRP can't decrypt /data/ so I can't purge the modules either.
[Magisk] imaverik:
16.2 Does work.

All,

here is how i was able to successfully get magisk on my Pixel2 XL (taimen).

1. Download the P -DP1 factory image

2. Yes - wipe data (leave -w in flashall.bat)

3. Run flashall.bat (or flashall.sh for Mac/Linux)

4. Let it boot and setup the basics.

-----dont setup your apps yet... as in... you can download/restore but do NOT run them.

5. you can either transfer your magisk and twrp files via normal usb mount or you can us ADB.

6. reboot to bootloader

7. fastboot boot twrp-3.2.1.2

8. --OPTIONAL-- Flash twrp, then reboot to bootloader again.

9. Flash magis16.2 zip.

10.boot phone...

We aren't done yet....

11. on your computer... open the magisk zip file with 7zip or preferred.

12. extract the magisk.apk and copy it to your "platform tools" folder in android sdk

13. copy file to phone under "Downloads"

14. enable ADB

15. COMMAND--- adb devices (if you see your phone then you will have to touch allow on the screen of your phone.)

16. COMMAND--- adb install magisk.apk (this assumes that the apk file is in your platform-tools folder.)

17. Check to see if Magisk app shows up in launcher. (may take a minute or two.)

18. reboot phone

19. try to run any app that needs root. You should be prompted to "Grant" access.

20. If you got this far then you're welcome. The modules all will download.

21. IF YOUR MAGISK Modules do not work... then the module maker needs to update the module.
[Magisk] laclac:
hi

I updated the 16.1>16.2 on my device (android 510F/ Nougat).

But I have a problem. Now it's impossible to start correctly my device.

My device boot in loop in the download mode.

Only the recovery mode works. it s terrible :(

recovery.log: https://ufile.io/56lsx

magisklog: https://ufile.io/1crmt

Note: it's not better with .disable_magisk
[Magisk] guest4711:
Restart into TWRP. Open the shell and create a file named ".disable_magisk" (mind the dot, it's necessary) in /cache.

touch /cache/.disable_magisk

. Reboot. Magisk should start in core-only mode (without loading any module).
[Magisk] Telperion:
I tried that per [MENTION=4667597]Didgeridoohan[/MENTION]'s suggestion and it didn't work. Verified that the file (with dot) was in /cache/ but it didn't actually disable it on boot.

I ended up having to open up a root shell while the device was stuck at the boot screen and delete the Greenify4Magisk module folder, at which point the boot proceeded. It appears that there's a security change in P.

When checking the menu item from a booted Android, Core Only works, but it didn't work from TWRP.
[Magisk] sushant_:
I cannot install any app after installing the magisk.

When I try to install any app it shows app not installed.

This happens in any oreo rom.

Here is the log
[Magisk] silas67:
I can't seem to be able to download 16.2. Every time I click on the download link I get a parsing error and a couldn't download from browser error. Anybody have a different link or what am I doing wrong? Any help please.
[Magisk] Badger50:
You can use mine if you'd like :good:

https://drive.google.com/file/d/12yG0amnFoAGumpl3_Z07JwRFl9XMdTGQ/view?usp=drivesdk
[Magisk] arunsai123:
File replacing modules like font modules and YouTube vanced modules stopped working in latest update.

Those files are mounted in /magisk but still they are not in target directories.

There are only 10 lines in magisk log.
[Magisk] Didgeridoohan:
From a quick look at the debug log it looks like the fbind module might be messing something up. Try disabling it.
[Magisk] arunsai123:
Thanks. I disabled fbind module, now other modules are working. But all modules worked flawlessly before magisk manager update. :confused:

Is there any way to change module priority?
[Magisk] Didgeridoohan:
Check in the module thread for help. Might be something needs fixing or updating. Make sure to provide the logs (there's also a module log, check the OP).
[Magisk] SickCuriosity:
I'm on a Nexus 5x running LOS 15.1 and EX Kernel, I'm getting occasional bootloops about 1 every 2/3 boots, restarting the boot almost always does the trick. I have tried magisk 16.0 and 16.2 with no difference. It's not a serious issue but it's kinda annoying and I haven't been able to find any solution except for understanding that it's likely magisk related. Thanks in advance to anyone ho can help.
[Magisk] flipmode_11:
Please check my FAQ. https://xdaforums.com/android-stick...logic-s905x-s912x-faq-backup-switch-t3752897/

Look at the solution for Magisk Hide issues at end of post #2.

Good luck.
[Magisk] Didgeridoohan:
From the description it's actually more likely that the issue is because of Magisk checking if logd is running, since v15.4. Devices not using logd for logging will then not have a functioning MagiskHide. Hopefully [MENTION=4470081]topjohnwu[/MENTION] can take a look when (if) he has time...
[Magisk] fanaticgamer:
Cheers mate, I managed to install 15.3 and now everything works just fine!

I had the same issues with CRA2 on G900F stock ROM and magisk 16.0.
[Magisk] flipmode_11:
Well done. I was thinking it was perhaps more along the lines of Kernel v3.8+ or higher being required for Magisk Hide. :good:

---------- Post added at 23:07 ---------- Previous post was at 22:47 ----------

Out of interest, can you please provide me with all your kernel details?

Stock, Custom ROM, Custom Kernel, Kernel version, etc...

Thanks

I'm on G906S OS 5.0. I also had issues with Magisk Greenify on TV boxes, not with empty log tho...
[Magisk] MysteryIII:
For now, I have hands on a second S5 which I'm using for testing stuff. As written before it's totally clean Stock ROM (CRA2)/Kernel (v3.4.0-12884729) + TWRP 3.2.1 + Magisk. On my daily use phone I use Boeffla kernel v2.5(also v3.4.0). As mentioned last Magisk hide that works is v15.3.1, starting from 15.4 it stopped working.

Here are my related posts: first & second.
[Magisk] flipmode_11:
I think I was right... Your Kernel is too old and not compatible with Magisk Hide in Magisk Manager 15.4+.

My Galaxy S5 (G906S) has stock F/W 5.0.1 and stock Kernel v3.10.40-5894670. It's a Korean firmware and released a year later than standard S5. I.e. Better CPU, better SnapDragon, better Adreno, more RAM, etc.

Glad I could help identify your Magisk Hide issue.

Check the device's forum or the custom ROM topic and see if there is a stable Kernel available,

newer than version 3.8.x

.

Magisk Hide in Magisk Manager 15.4+ requires newer kernel versions.

Magisk Hide in Magisk Manager 15.31 (and older) appears to support older kernels versions.

Good luck! :good:
[Magisk] Didgeridoohan:
Well... Yes, and no.

The requirement for a Linux kernel of version 3.8+ has always been a thing. It's not why MagiskHide suddenly stops working with Magisk v15.4. If a kernel with a lower version works, it's simply because mount namespace support has been backported to it and that did not change with v15.4.
[Magisk] SickCuriosity:
Honestly I'm quite a noob and I'm not sure how to get a logcat of a bootloop, do I necessarily need to get it via adb? (Sorry for the ignorance)

Anyway a updating to latest nightly and changing kernel seems to have fixed the issue, at least for now.
[Magisk] AndroidFL:
Can someone share the zips from magisk 12 to 14.5 because on my Note 4 the new ones automatically disable themselves after installing with TWRP?
[Magisk] Didgeridoohan:
Better idea:

Provide details and logs to possibly improve future releases of Magisk.
[Magisk] jenslody:
Can you check the superuser menu in MagiskManager and see if the shell is already listed, but ha root access denied ?

If that's the case, it might be caused by the way TotalCommander requests root access, or by automatically denying root access (check the aettings in MagiskManager).
[Magisk] xdarasc:
I cannot use Magisk Manager - when starting it it hangs at the initial green(?) screen /w the Magisk logo, I don't get beyond that.

Back from the time I had a rooted Note 1 I remember that this is the point where the dialog came up asking to grant root access.
[Magisk] tattmann:
deleted
[Magisk] oTeMpLo:
Reboot
[Magisk] tmviet:
Me too I remain in 15 stable
[Magisk] :
00
[Magisk] edzamber:
Hi all,

After a while i loose root. It happening after let screen off a long time or suddenly without any reason. Magisk returns not installed. I have to reboot, sometimes twice for root comes back.

Any idea how to fix ?

Many Thanks.
[Magisk] ATZ-007:
Did a quick search but couldn’t find any solution.

I’m on Magisk v16.3 (beta) (LG G5, Android 7.0) and after choosing the option to hide magisk manager, it stops working (phone shows “Magisk Manager keeps stopping”.

I’ve tried clearing data before and after hiding magisk manager, still no success.

Also tried the stable version of Magisk Manager
[Magisk] siealex:
I couldn't obtain any logs, it hangs immediately after the bootloader.
[Magisk] SoMeiBoL:
I'm having this problem when I swipe to update the downloads. The app is closed [MENTION=4470081]topjohnwu[/MENTION]

Version 5.6.4 - Magisk 16.3
[Magisk] guest4711:
Without proper logs it's hard to help... Missing "storage permissions" for MagiskManager?
[Magisk] SoMeiBoL:
Has permission activated yes. It's funny but now it works when I wanted to record a log.
[Magisk] krkhaha:
Where is version 16.3 and uninstaller. Can't found it.
[Magisk] Badger50:
Have you updated it from within the MM app on beta channel?? The uninstaller zip should be in your MM folder on your internal storage.
[Magisk] jwds1978:
I've noticed this myself…
[Magisk] skyknife93:
Google tez (payments app) doesn't work anymore. I've read a post saying that if an app that used to work before stops working, upload the debug file so I've done that.

Device - OnePlus 5 with OB7 (stopped working on ob6) with bluspark kernel
[Magisk] Wolfcity:
Is that app in your magisk hide list? The changelog for 16.3 says that apps that were hidden by default before (like pogo) have to be set in magisk hide now.
[Magisk] Neverendingxsin:
16.3 working great on stock Pixel 2XL
[Magisk] skyknife93:
Tried everything, magisk core mode only, checked it in magisk hide along with play store and Google framework as well, cleared it's data and cache, even uninstalled and reinstalled it. Nothing worked. Actually quit working on 16.2 but I waited for an update to fix it. Only thing that helped was uninstalling magisk, but even after registering again and reinstalling magisk, it again quits and says can't be used on this device as it isn't certified (which it shows certified).
[Magisk] krkhaha:
Yes I have update from MM. I have magisk 16.3 in internal storage in MM folder but I don't have uninstaller there. Always I can found this everything in fierst post that why I asking.
[Magisk] Didgeridoohan:
The uninstaller has always been found in the release thread. And it's still there...
[Magisk] an0therus3r:
Magisk Hide is broken in 16.3.

My apps like Blackberry Work and Access stopt working, reverting back to 16.2 resolved it.

Will upload debug log when I found time for another test.
[Magisk] amppcguru:
Safety net flx
[Magisk] MysteryIII:
No changes with 16.3/5.6.4 on GalaxyS5, as expected. Just sharing logs again if it may be helpful.
[Magisk] phuhcue:
Anyone getting "data/magisk is not installed correctly" errors trying to install modules?
[Magisk] monsterkruemel:
Bootloop after installing 16.3 on leeco le max 2 los 7.1.2 14.1-2018-03-25 nightly. Flashing 16.2 fixed it.
[Magisk] pkgnex:
Doing the self-install of 16.3 seemed to work... until I rebooted the phone.

On my stock-ROM Pixel2 XL Magisk 16.3 is no longer creating the /magisk folder or any of the post.fs or service.d sub-folders during start up, so my modules and scripts didn't load, and several other things went sideways. The log was literally 200 lines of "mount..." / "creating link..." stuff that was never there before (but of course I didn't save it). I kept root and basic functionality, throughout, though.

Tried every combo of uninstall / reinstall / flash over, etc. No dice. Reverting to 16.2 got everything back to normal on the first try, though.
[Magisk] siavash79:
Since update to Android P I was not able to install modules:

In 16.1 there was this magisk manager bug not installing modules, but now it seems it's not able to mount them during boot.

I've attached the log file. Anyone can help me out?

Thanks
[Magisk] innocentone1:
Everything Seems okay on the latest magisk and magisk manager no more pokemon go crashes but now I am getting This software OS device is not compatible with pokemon go. Please help :C also I am having a weird issue where every time I reboot my phone it fails safety net and I need to go into settings and toggle magisk hide off for 15 seconds then turn it back on for it to pass. Any ideas? Thanks!

Edit: Problem solved PoGO not hiding by default anymore just had to rehide it. I am still having the safety reboot issue though if anyone can help me with that. There are no logs on this issue that I can create. I am using a PH-1 Mata if that means anything.
[Magisk] Seagold:
I'm using version 16.0.

My phone ? is now running ? fine like am using brand new high-speed phone. Everything is smooth and fast.

Samsung Galaxy J200H 3G

Rooted

Resssurection Remix Rom 7.1.2 Final

?
[Magisk] ashu01:
I had only one module with magisk that is edge sense

After updating magisk to 16.3 my module stopped working

Everything else working fine

Tried reflashing the module and re-installing the app

Anyone with modules not working issue on 16.3?
[Magisk] Didgeridoohan:
If modules stop working after updating to v16.3, it's very possible that you need to contact the module developers and let then know they need to update their modules.

Up until know, Magisk kept symlinks to old file and folder locations (/magisk, etc), for some backwards compatibility. That backwards compatibility has now been removed. Read more about it in the release notes.
[Magisk] Seagold:
ADD SOFT REBOOT.

Thanks
[Magisk] Didgeridoohan:
Stop shouting please.

Thanks

If you're trying to make an actual feature request, you're going about it completely the wrong way... Besides, why on earth do you feel that Magisk needs a soft reboot option?
[Magisk] cpt.macp:
/data/magisk isnt setup properly,

this thing persists only with 16.3 and not 16.2 , i wonder why

also with some modules like systemless fonts

and xposed , busybox were fine
[Magisk] Didgeridoohan:
/data/magisk isn't supposed to be setup at all on v16.3. Read about backwards compatibility in the release notes.

If you wonder about the details for the moved files, read the release notes for v14.5 (yes, it was that long ago it changed).
[Magisk] guest4711:
How should someone help with this issues if you give no logs and no related information?

But probably your modules are outdated, see https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post76052670
[Magisk] Tecalote:
[MENTION=4470081]topjohnwu[/MENTION]

[MENTION=4667597]Didgeridoohan[/MENTION]

Just a wish /suggestion if it is feasible:

It would be great if Magisk Manager would detect during update to newer version if someone have previously used the feature of repacking under a randomly generated name and keep that name...

And it would also be great - if it would possible to disable update notification really in settings (it's there, but update notifications always shown for Manager /Magisk if disabled) cause as long everything is working fine, there's no need to update.

In this case the User could enable or disable Updates for his needs and enable if necessary...

Thanks for the great work :)
[Magisk] Shaikh Arbaaz:
Facing an issue after flashing Magisk on Moto E only on "Oreo Roms" that Package Installer doesn't

let Install any apk In short it breaks Package Installer. Not even able to installing Apk via ADB.

Here is the log:-

https://hastebin.com/isopifoyiq.sql

Waiting for solution.
[Magisk] cpt.macp:
I was not asking for a solution , I know it happens when config.sh is outdated and some meta files are mismatched .
[Magisk] m+a+r+k:
Is this safe for Pixel C yet?

Don't dare go through the bootloop fiasco again that I had with 16.0.
[Magisk] Sam Nakamura:
What fiasco? Just store your stock boot.img somewhere so you can flash it "in case of bootloop", pressing power button for as long as it takes to shut the engine off and restating into recovery mode via button combo isn't witchcraft at all...
[Magisk] xdarasc:
still the same after updating to Magisc Manager 5.6.4 (112), (re)downloading Magisc 16.3, (re)patching, (re)flashing.
[Magisk] SacredDeviL666:
And cleaned the thread again ( a very minor one ) :good:

Stay on Topic will be the mantra as mentioned in OP :o
[Magisk] Didgeridoohan:
Logcat when Manager fails to open, please...
[Magisk] xdarasc:
Here you go.

Thank you.
[Magisk] Didgeridoohan:
Looks to me like Magisk isn't set up correctly on your device. There are probably a whole bunch of files missing or they can't be created. Like the su database... That's likely why the Manager won't start, because it can't open the database.

If you ask me why, I (personally) have no good explanation apart from the fact that Mediatek devices often have issues like this with Magisk... They're simply incompatible. :(
[Magisk] Sam Nakamura:
Yet another MTK error log,

till magisk 15.6 patching the boot image was working fine, now Magisk Manager doesn't even start the patching process, if I patch the boot image on another device it seems alright but gives bootloop after transferring it back and flashing it...

When flashing Magisk 16.3 via TWRP it says "can't repack boot image" but flashing in TWRP never worked for me...

Recovery log:

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

Here's a log from magisk manager failing to start the download/patching process, the magisk logs show nothing, like nothing happened at all, which is actually true for the most part...

Logcat:

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

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

I know this whole Mediatek story is somewhat pointless as it seems more like a general incompatibility but as it worked for quite some time (via patching boot) I still got hopes....