yashsingh1/xdaforums huggingface dataset:
[Magisk] anz563:
My oneplus 3t on oxygen 5.0 with stock kernel and Magisk 14.6 heating without a reason :( Can Magisk be cause of heating?
[Magisk] dunjamon:
Just updated my OP5 to Oreo and using the beta magisk I'm unable to install modules and apps keep asking for root access even when I select forever on the popup.
[Magisk] yung40oz84:
Is there any logs I can provide to pin this down? It's not an overly worrying issue but every time I uncheck this and open Magisk back up it's automatically checked and I'm definitely not encrypted and don't want to be, which it isn't forcing. So it's probably wither not looking in the right place it it's a graphical glitch. Omni, OnePlus 5T, Android 8.1.
[Magisk] pWEN:
Guess you can't believe everything you read on the Internet! :silly: Renamed the backup to end in .img, patched with Magisk, then it crashed when loading Android and rebooted to recovery. Selected "try again" and it booted okay. Still get "internal problem" error (I just HAD to try it), but everything seems fine, so whatever. I'll stop messing with it... for real this time. lol
[Magisk] chudy_85:
If now you update your magisk to 14.6 it's good for you. Now we must wait for next people who confirm my screen and update method.

Wysłane z mojego EVA-L09 przy użyciu Tapatalka
[Magisk] apophis9283:
On OnePlus 5t, I am decrypted. Yet when I flash Magisk it says encrypted data found. Is it possible its not seeing /data as it should?
[Magisk] lettucecube:
Apps keep asking for root access even when I select forever on the popup.

What I can do ??
[Magisk] alryaz:
Error in 14.6

I have found it to be a problem with 14.6, within the Magisk Manager logs it keeps spamming how the sqlite3 database can't be accessed.

One possible solution would be install 14.6 on top of an active (and complete) 14.5 installation (or earlier).
[Magisk] anz563:
Anyone else has heating issue?..
[Magisk] xclub_101:
That is more like a dirty workaround until some ugly problem is fixed in the code :(
[Magisk] wackygoose:
Just don't try to flash 14.0 without uninstalling it first, I dunno why but it results in a soft brick
[Magisk] starbase64:
Not here, booted without problems. 14.0 to 14.6
[Magisk] Revertron:
I've had a bootloop on Xperia XZ.
[Magisk] saggiboy231:
Not able to install many modules.

get this error "magisk merge img mount failed"
[Magisk] wackygoose:
I talking about 14.6 to 14.0
[Magisk] brqndon:
I'm sorry! I was trying to attach it but it wouldn't from my phone for some reason.
[Magisk] DodoGTA:
/data/(adb/)magisk_debug.log and module install log (If you're installing it in Magisk Manager, then click the Save log button at the bottom (when in the installation failure screen) and a toast message will appear telling where the log is, and if you're installing it in TWRP, then go back to its main menu after the installation has failed (Don't reboot yet), tap Advanced > Copy Log to SD and the message will appear telling where the log is)?
[Magisk] gh2923:
all the modules installed on 14.5beta are missing, and cannot install any modules, with the warning "unable to extract zip file".

i uninstalled magisk with "restore stock boot" and then flash OTA. after that i flashed magisk 14.6, and then the problem above come out.

My device is Xiaomi 6, with alpha miui 9 of Oreo.
[Magisk] starbase64:
sorry
[Magisk] wackygoose:
No need to apologize man, it's all good
[Magisk] kgjel:
I've been trying to install the Magisk beta — tried: 14.3, 14.5, 14.6 — on my Pixel XL running unofficial LineageOS 15.0, but am getting bootloops.

Issue:

The device bootloops when trying to boot after flashing the Magisk ZIP. It appears as if there is some sort of kernel panic (check the `2017.12.25_console-ramoops_trimmed.txt` file below, around line 45) .

Steps to Reproduce

Boot into installed TWRP and flash the Magisk ZIP file.

Installer log completes without errors.

Reboot into System.

Device boots to the Google logo, but then shuts off after that.

Device will bootloop until Magisk is uninstalled.

I have included the recovery.log and a trimmed ramoops file (it wouldn't let me attach them, and the contents were too long to include inline. Apologies for the links, and let me know if you'd like me to provide the files in a different way.).

Also, please let me know if I can provide any more info (or if you'd like the complete, untrimmed ramoops file).

2017.12.25_recovery.log

https://hastebin.com/raw/ohuzuqozeb

2017.12.25_console-ramoops_trimmed.txt

https://hastebin.com/raw/iyoqahomof
[Magisk] TonikJDK:
Did you flash a clean boot img before flashing Magisk?
[Magisk] kgjel:
No, but according to the Magisk installation log, it looks like it checks to see if the existing boot.img is the clean one. If it detected that it was not the stock boot.img, I would imagine it would throw an error. Am I incorrect?

How can I get a clean boot.img file for the ROM?
[Magisk] TonikJDK:
Sorry, my mistake. You are on Lineage. That is pre rooted.
[Magisk] kgjel:
It is not pre-rooted, unfortunately — they have not yet released a su addon for v15.0+. Please see the `Extras` section, linked on the bottom left of the LineageOS downloads listing page (sorry, can't link it due to post restrictions). The highest version they have su for is 14.1.

That's why I'm trying to install Magisk.
[Magisk] TonikJDK:
In that case, dirty flash the whole rom. A clean start is best.
[Magisk] kgjel:
While my install of the ROM is not currently fresh (I've been using it for a week), I had the same issues when trying to install Magisk when the ROM was clean and freshly flashed. Other people have reproduced the issue using a fresh install of the ROM too. :/
[Magisk] wackygoose:
I'm also on LineageOS, I will never try magisk beta again XD
[Magisk] FlavioV:
Worked for me, thank you! :highfive:
[Magisk] wackygoose:
Magisk 14.0 is working very fine for me on Z3 Los 15
[Magisk] kgjel:
I don't believe I can use v14.0, due to it not supporting the Pixel's partitioning format.
[Magisk] vortex-5:
It would seem like 14.6 has an issue with the OnePlus 5 on oxygenOS 4.5.15 it doesn't seem to detect the dm-verity correctly for an non ecrypted data partition and on startup it says "Encryption unsucessful" with the latest Oxygen OS 5 it will do the same thing (fresh installed from recover then wipe + dm verity mod). To be fair I'm not sure of the OOS5 DM-verity mod is working as without magisk and only using the DM-Verity mod it would appear that OOS5 will bootloop.

or end up with a blue led (of death).

14.0 works fine with OOS 4.5.15 for the time being I would advise others to not upgrade to 14.6 for the moment.

If anyone here has success with OOS5 + Magisk 14.6 I would like to know your process also important if you're already decrypted or are running encrypted. 14.6 seems to always think it's encrypted even on OOS 4.5.15 which according to the security tab it is not (it should say encrypted phone in small letters)
[Magisk] dpk24mt:
On my Moto X Play (lux) AICP 12.1(nougat), I was able to solve 14.6 beta issues by dirty flashing the rom again (cache and dalvik cache/art cleaned). The 14.6 magisk got automatically installed again along with the ROM without any additional steps. Now everything is working normally. No more repeated su access prompts for apps and no more heating or bootloops.
[Magisk] Pkt_Lnt:
logs Logs LOGS! *nothing* gets fixed without *LOGS* :good:

logs Logs LOGS! *nothing* gets fixed without *LOGS* :good:

logs Logs LOGS! *nothing* gets fixed without *LOGS* :good:

logs Logs LOGS! *nothing* gets fixed without *LOGS* :good:

logs Logs LOGS! *nothing* gets fixed without *LOGS* :good:

logs Logs LOGS! *nothing* gets fixed without *LOGS* :good:

Got it?

logs Logs LOGS! *nothing* gets fixed without *LOGS* :good:

:D

Oh, yeah, and Merry (logs) Christmas (logs)
[Magisk] Dinerve:
I'm all good here, running 14.6 on a fresh install of OOS5 on the OnePlus 5.

I first wiped everything in latest blu_spark twrp.

Restarted in fastboot, flashed stock recovery.

Restarted in stock recovery, wiped to factory just to be sure then ADB sideloaded OOS5.zip

After OS restart, downloaded 14.6 zip, rebooted in fastboot to flash latest blu_spark twrp then rebooted into it.

Flashed Magisk 14.6 zip file, cleared dalvik&cache and..

Voila, encrypted still, no dm-verity mod for me.
[Magisk] Devpindoriya:
bank apps google tez android pay doesn't work safety net problem..?? how can i use this apps in my phone
[Magisk] Akhilesh S V:
Well it works for me, just clear Tez data and reinstall. I might work.
[Magisk] :
Got my Pixel 2 XL running December Security 8.1 and patched the boot.img using the Magisk Manager v14.6... On reboot, I got a vendor mismatch (I believe) or an error message at the beginning after a reboot, but other than that, everything seems alright... Anyone get this and know whats going on? Thanks!
[Magisk] Diesel_Jeremiah:
Pop up is talked about over the threads. Doesn't harm anything.
[Magisk] vortex-5:
Ok it must be the DM Verity then most non encrypted people are getting stuck.
[Magisk] :
Appreciate it
[Magisk] kgjel:
I put my (yule) logs in the fire (of my original post), for all to enjoy, and will happily add more upon request :p
[Magisk] Devpindoriya:
I m use Redmi 4x custom rom rr their is problem for this apps will not run rooted device thats type msg show me how can hide root
[Magisk] Sreekantt:
can i have magisk 14.3 & 14.5 zips ? 14.6 is removing my fingerprint
[Magisk] 127cwho:
Manager fc when press supersu in the meun.
[Magisk] DenyDarko:
Clear its data
[Magisk] Didgeridoohan:
PSA - Don't forget what this thread is about.

Spoiler: it's logs!

There's a big nice BETA tag added to the title of this thread. That means something...

It means that anyone downloading and using the software provided here are expected to help out with providing information about issues that might arise when developing Magisk and the latest beta release.

It means that there might be bugs, but that's expected, it's beta software after all...

It means that anyone having issues need to provide lots of details and relevant logs.

Just posting "it doesn't work" or "it bootloops" or "I'm going back to version xx because it works" does not help. It actually hurts development because useful and relevant posts get lost in the noise of uselessness.

And talking of logs: Logs are not supposed to be posted straight into your post... Attach it to the post, upload it somewhere and provide the link or use a service like Pastebin, Hastebin or similar.

The OP (that means Original Post for those of you that are new to all of this) of this thread has several useful tips on what kind of logs to grab and provide. The OP is always, ALWAYS a good place to start.

If you don't know how to grab a logcat, here are two links for that, but remember that the xda search tool and a web search can get you very, very far. Always search before posting.

https://xdaforums.com/showthread.php?t=1726238

https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/

A logcat can be used for lots of purposes. Crashing apps, bootloops, etc. Please use the tools available and you'll make it so much easier for [MENTION=4470081]topjohnwu[/MENTION] to fix whatever issue you're having.

Also make sure to heed my good friend [MENTION=1205214]SacredDeviL666[/MENTION]'s great posts. They're always a good read. If you do, you won't have to deal with the embarrassment of getting your posts deleted...

What it means when the above advice isn't followed, is that your issues won't be fixed. Android is way to fractured and there are way to many manufacturers and versions for [MENTION=4470081]topjohnwu[/MENTION] and those of us trying to help him out to test all possible setups.

Help the community. You'll get all nice and fuzzy inside when that bug you properly reported about gets squashed.
[Magisk] gothicVI:
Thanks! That did the trick.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] bggold:
Same here. Pixel 2 xl v8.1 & ElementalX

Uninstalled MagiskManager APK and even reflashed in recovery.

Have root and safetynet passes. Just can't load the manager.

Here is the log sorry had to zip, too large for forum upload.

Thanks
[Magisk] Veid71:
so when i install magisk and reboot i the magisk manager isnt installed with it even though i downloaded and flashed the bundle so i copied the log and here it is i was looking at it and it looks like its unable to mount because i found this in the log, ive attached the log also [MENTION=4470081]topjohnwu[/MENTION] i have a pixel XL which is the same phone as you so it should work correct? the only difference is im running 7.1.2 instead of Oreo

also when i install the manager manually it says i have 15.0 installed but at the bottom where it says install it usually has uninstall when it is installed but on mine it does not,

and when i hit the three side button to change where i wanna be like magisk hide or SU or root or whatever the only things that show up are magisk manager, settings, and about,

also my safety net check pops up as false on both so obviously root installed but when i check to verify if root is installed using an app it says its not i have attached screenshots to show you what i mean incase it is easier to see what i am talking about

it also asks me to install magisk 15.0 when i refresh or open the app for some reason edit: i fixed this one specific issue by switching the update channel to beta

I:Mount: Unable to find partition for path '/cache'

I:Copying file /data/cache/recovery/log to /data/cache/recovery/last_log

I:Mount: Unable to find partition for path '/cache'

tw_get_context got selinux context: u:object_r:media_rw_data_file:s0

I:Got default contexts and file mode for storage files.

I:Attempt to load settings from settings file...

I:InfoManager loading from '/data/media/0/TWRP/.twrps'.

I:Backup folder set to '/data/media/0/TWRP/BACKUPS/HT68R0207422'

I:Mount: Unable to find partition for path '/cache'

I:Unable to mount '' to write version number.

I:Unable to mount '/usb-otg'

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

__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!

__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
[Magisk] rober_arro:
I was using Magisk 14 and all perfect, I installed version 15 from twrp recovery and all ok, no error message but when I reboot the phone is like Magisk wasn't installed.

I tried install v15 again but it's the same and with beta 14.6 it's the same

If I install Magisk 14 or beta 14.3 is all ok.

I'm using a Xiaomi Redmi 4 Prime with miui global rom with android 6.0.1.
[Magisk] terryhau:
Still stuck on boot logo with 15.0, same as 14.6.

Galaxy S8 International.

Log attached.

I'll try a clean install later.
[Magisk] leo.riv:
[MENTION=4470081]topjohnwu[/MENTION]

I am having issues with v15.0 on my Lenovo VIBE X3 (X3a40) 64bit android 6.0.1

I was able to flash Magisk 14.3 via TWRP with no issues.

after fash 14.5 or 14.6 or 15.0 have stuck on bootloop

I am uploading the recovery logs

View attachment recovery.log
[Magisk] chudy_85:
I update form magisk 14.5 to 14.6 only if I select this 2 option :

Preserved force encryption

Preserve AVB2.0/dm-verity

When I have 14.6 I update to 15.0 using this method Direct Install

Now I have magisk 15.0 and magisk manager 5.5.1 and installed mod on screenshot

My firmware it's Eva-L09c432b394 stock with TWRP 3.1.1-1

---------- Post added at 08:38 AM ---------- Previous post was at 08:23 AM ----------

It's not change regional model number and keys. My sound on camera work normal but I use magisk Viper4Android

Wysłane z mojego EVA-L09 przy użyciu Tapatalka
[Magisk] Sreekantt:
ok...let me try with 2nd option ticked and direct update

is the viper by ahrion not working on v15 ?
[Magisk] copota:
My Phone:

Samsung Note 5 SM-N920P (sprint)

Nougat 7.0 Stock Touchwiz rooted with TWRP 3.2.1-0

PROBLEM: After installing Magisk 15.0, phone gets stuck at SAMSUNG logo and won't boot. I had the same problem with 14.6(1468). I flashed via TWRP recovery, and flashed with a direct install from the app. Problem occurs both methods of installation.

14.5(1456) works fine.

Interesting note. Flashing 14.6 would wipe out my recovery upon reboot. Flashing 14.5 does not wipe out recovery.

I cannot provide a magisk_debug.log, since no log appears in /data/adb/. Only the magisk.img appears.

I did attach my TWRP recovery.log.
[Magisk] Teddy01:
Thx chudy_85.

Without setting these both options I get a bootloop (even with clean install)

Setting both options it works without problems when updating from 14.0 to 15.0.

I'm using a Honor 8 Premium.
[Magisk] ivan47:
Not working htc m9+ 6.0
[Magisk] korom42:
[MENTION=4667597]Didgeridoohan[/MENTION] [MENTION=4470081]topjohnwu[/MENTION] Magisk V15 Installation success but got in botloop

Device : Xperia XZ

ROM : Official Stock Oreo 8.0

Bootloop log attached below

V14.3 and 14.5 works fine , V14.6 breaks DRM keys verification for Sony kernel aka stimulating TA partition lost keys after unlocking bootlader fails (log in #4652 )
[Magisk] rober_arro:
I was using Magisk 14 and all perfect, I installed version 15 from twrp and all ok in the recovery, no error message but when I reboot the phone is like Magisk wasn't installed.

I tried install v15 again but it's the same and with beta 14.6 it's the same too.

If I install Magisk 14 or beta 14.3 is all ok.

I'm using a Xiaomi Redmi 4 Prime with xiaomi.eu rom with android 6.0.1.

Now I upload the recovery log.
[Magisk] Didgeridoohan:
99 posted logs in the thread,

99 posted logs.

You take one down, realise there are none,

Cause no-one is posting logs in the thread.
[Magisk] störte:
On the Note 8 with Echoe 3 and AEL v15 is working without problems.

On the S7 Flat G930F with Echoe v24 and AEL it isnt is not working. Magisk 14.5 is working. Will try to load some logs when i get the phone in my hands again.

Added the install log
[Magisk] Ja_som:
EDIT: issue solved

https://xdaforums.com/showpost.php?p=75204188&postcount=11

Hey [MENTION=4470081]topjohnwu[/MENTION] thanks for your work.

I have issue with v15 on my Nexus 5X with Android 8.1, flash was OK, w/o error, but boot was stuck on the Google logo, after few manual hard reboots it booted to system. It was OK for few hours, but then my device stopped responding when I unlocked it, I had to hard reboot it again. I have this issue randomly after some time, sometimes it is sooner after reboot, sometimes later, so it was a bit hard to catch a log. So I let my device to record log for longer time, for that reason it is so big, but I hope it will help you to fix this issue.

(I also tried to disable all modules, but it was same)

v14.5 was working fine and v15 works fine on my second device Nexus 7 II with LOS 14.1
[Magisk] Didgeridoohan:
PSA - Magisk v15.0 issues

I posted this in the general thread, but might be useful here too...

Gonna recap possible solutions for some issues that have arisen from Magisk v15.0.

Samsung devices that experience bootloops, try flashing a dm-verity zip together with the Magisk zip. See here for more details (thank you [MENTION=5566313]Aria.A97[/MENTION]):

https://xdaforums.com/apps/magisk/fix-bootloop-issue-magisk-14-6-15-0-t3725962

Huawei devices that experience bootloops or weird issues like changed model number etc, before installing v15.0 make sure to enable "Preserve AVB 2.0/dm-verity". This has been known to work for some. Might possibly also work for other devices experiencing similar issues...

Users experiencing su issues and/or the Manager crashing, if you can open the Manager, uninstall it by pressing Uninstall -> Uninstall App and then reinstalling the Manager (download from the release thread).

If you can't open the Manager or if the above doesn't work, flash the latest uninstaller zip (download from the release thread) in recovery and reinstall Magisk.

If you can't open the Manager and don't have access to a custom recovery, I'm currently at a loss as to how you should continue... Open to suggestions.

Users experiencing SafetyNet issues, read through the troubleshooting guide. It's not yet updated for v15.0, but the SafetyNet tips should still apply. If you can't get it working, make sure to post logs (take a look at the "Asking for help" section).

And, more to test for Manager and su issues:
[Magisk] AndroMani:
Hi All,

Even I also had the same issue of root lost for few minutes after upgrade to Magisk 15. Both RootChecker and Titanium back up failed to verify root with the new Magisk version and eventually timed out, rather I closed them. However, the install was stable. So, I just opened my ES file explorer and enabled the root explorer option. After some time, I got the pop up for granting root permission. At that time, I was sure that MagiskSU was working alright. Then I again verified with RootChecker and Titanium. They were granted root access and confirmed my root. I also verified the SafetyNet Check. It turned out to be a success. So, all in all my upgrade to Magisk version 15.0 was a grand success.

For the benefit of others, who may have the issue of boot loop because of the steps they followed and initial root loss, I am giving below the steps I followed for the upgrade.

1. Remove ALL installed magisk modules from Magisk Manager and then reboot into the system.

2. Boot into recovery and uninstall Magisk 14.0 from TWRP thru' the old uninstaller zip provided.

3. Boot back to system to check Root is lost and everything is working alright.

4. To be on the safer side, booted back into TWRP recovery and took a Nandroid back up of my stock rom to my USB OTG drive.

5. Flashed the Magisk V 15.0 zip from TWRP recovery and booted into the system. No issues found in booting back.

6. Manually installed the Magisk Manager Apk version 5.5.1 that I had already downloaded.

7. Open it to verify SafetyNet status and also checked the download section of available modules

My device is: Moto G2 4G LTE 2014 edition running stock Marshmallow ROM.

I guess some people may have issues understanding the two options provided under the "Advanced Settings" in the Magisk Manager UI (that is, Preserve force encryption and Preserve AVB 2.0/dm-verity) while upgrading to Magisk 15 directly from the Magisk Manager and checking one or two of these two options.

May I suggest to have some kind of a Toast message to be shown when people check these boxes in the Magisk Manger to let them know its purpose and what they are getting into. So, they will know if they need to check them or not before upgrading to Magisk 15. Not sure if it can be done OR really required if people have read the

updated OP and what these two options are supposed to do. But I found success thru the TWRP route.

And thanks a lot to [MENTION=4470081]topjohnwu[/MENTION] and the entire team of Magisk for providing the next stable version before

the New Year. By the way, advance Happy New Year 2018 to the entire Team of Magisk and expecting more robust features in future. Thank you all :) :highfive: