yashsingh1/xdaforums huggingface dataset:
[Magisk] OreoCupcakes:
15.1 has been causing non-stop issues on my OnePlus 3T (OOS 4.5.1). After updating the first time from 15.0 to 15.1, it changed the way my password worked. Instead of making me type my password in at boot to decrypt my storage, it sent me straight to TWRP with my storage mounted or booted up and sent me to the lockscreen. After installing a module from Magisk Manager and rebooting I lost root access to the apps I already granted access. The apps wouldn't popup a message to grant access even after I removed the original permissions.
[Magisk] sidelsky18:
Updated to latest a couple of hours ago on my Nexus 5X and it was all fine. Restarted phone an hour ago and it get stuck on Google logo splash screen :/ Have tried restarting, nada. Any help?

I can get into TWRP Recovery fine.

I don't think it's bootlooping, it just sits on the splash screen. I can still go to the bootloader and TWRP recovery. What's the best course of action?
[Magisk] ivanich:
Unfortunately magisk-15.1 causes bootloop on Oneplus3 with latest OpenBeta29

Edit: magisk-15.0 works, after flashing booted into android and update magisk to 15.1 via Magisk manager, after reboot all works fine. Most likely latest magiskboot fix causing this.
[Magisk] alexbk66:
V15 on Samsung Galaxy Tab A (SM-T280)

I've got a new SM-T280, tried to install Magisk v15, but it fails, also latest v15.1 doesn't install. I was able to install v14.0 though. Recovery.log attached

View attachment recovery.log
[Magisk] F4JL0:
As I see I'm not only one who has problems with Magisk v. 15.0.

After installing v. 15.0. I couldn't start Magisk Manager and root wasn't working so I restored my nandroid backup and then flash v. 14.0. again and everything works perfectly

I don't recommend to update to v.15!!
[Magisk] DodoGTA:
That signature/byline though... :laugh:
[Magisk] QkiZMR:
Moto G5S Plus, Android 7.1.1, Magisk 15.1, Xposed 89, V4A 2.5.0.5. Everything works fine for now.

Question: where I can make feature request? It will be nice if Magisk SU manager will show what commands apps are doing when they use SU. Like in SuperSU.

Sent from Moto G (5S) Plus via Tapatalk
[Magisk] ahse0w:
Did you have the graphical hangups? If yes, please share how you fixed it! :fingers-crossed:

Oh wait.. are you using Lux or f.lux?
[Magisk] mr_shaba:
Nope, all smooth here, busybox came preinstalled along with the rom, don't use it as a magisk module.
[Magisk] moderndaycowboy:
I installed busybox via google play, and It says busybox is not installed, Why is that happening so?
[Magisk] Serris:
Same with Oneplus 5 official Oreo
[Magisk] moderndaycowboy:
confirmed.

on Note 8 exynos, on magisk v15.1, enabling systemless host option makes safetynet false. If I close systemless host, safety net becomes true.
[Magisk] adarshm4you:
Everything works fine,but some games like clash of clan not opening or it keep closing.I found out it is because of the kernal patch while flashing.I am using custom unofficial resuurection remix 5.8.3 version.If i flashed custom kernal again,all systemless xposed frameworks and magisk frameworks uninstalled or not detected.Some posts says flashing stock kernals solves it,in my case since its a custom os,i cant.Any solution?:confused:
[Magisk] Didgeridoohan:
Grab a logcat when the Manager is crashing and then try clearing data for the Manager.

Are you saying that your phone gets encrypted even if the option of preserving forced encryption is turned off and your phone is not encrypted? A Magisk installation log (recovery or Manager) might show something.

Installation logs (recovery or Manager) would be useful. And probably a copy of your boot image as well.

Your installation logs are showing somewhat outdated modules. They might be based on old templates and are no longer compatible with the current version of Magisk.

I'm not sure you understand what the forced-encryption option does... If your device is not encrypted, you need to remove that to stay decrypted. If your device is encrypted and you want it to stay that way, the option doesn't really matter if it's set one way or the other (unless you format data with it disabled, because then you'll have a device without encryption).

Anyway... I've tested a couple of stuff on my OP3T and had no issues (on OOS 5.0 though). Some logs might be helpful (recovery log, Manager installation log, if possible a logcat during boot, magisk_debug.log, etc). You might be successful if you just install a clean boot image (extract it from the OTA file) and install the Magisk zip again.

About the superuser access issue: try uninstalling the Manager, from within the Manager (Uninstall -> Uninstall App) and then install it again.

Installation log (recovery of Manager) plus a magisk.log or magisk_debug.log might be useful.

Logs... Start with the Magisk log and if you have it in /data/adb, the magisk_debug.log might be useful (if you don't have it you can install the beta version of Magisk v15.1, it has more verbose logging for troubleshooting).

Try toggling MagiskHide off and on again. That usually works...

Make sure the Magisk Manager has storage permissions.

Logs when stuff are crashing is the only thing to show anyone that can do anything about it what's going on.

An installation log (recovery or Manager) plus a copy of your boot image might help with the debugging.

Unrecognized ramdisk... Hm... The next step for Magisk development is stability and device compatibility. Upload your boot image somewhere so that [MENTION=4470081]topjohnwu[/MENTION] can look at it (when an opportunity for that arises).

You don't mention if you tried Magisk v15.1 and Manager v5.5.2... Did you? There's been some work on fixing issues. If there still are issues, logs would be helpful when trying to troubleshoot and debug.
[Magisk] Einsteindks:
No graphical issues, Lux; the auto-brightness app. Phone is xt1254.
[Magisk] QkiZMR:
There is no Magisk for specific devices.

Sent from Moto G (5S) Plus via Tapatalk
[Magisk] update.freak:
Does the Magisk v15.1 work with Resurrection Remix OS (v5.8.5-20171217) on I9300?

A few month ago, there was the problem that the device can not be woken up by the power button, after it is not used for a specific time.
[Magisk] nuxbag:
That's what happened to me, after I flashed the uninstaller it booted again
[Magisk] BurnedDrake:
Did you just install it from the play store and do nothing after? If that's the case, you need to open the busybox app (the app is the busybox installer) just run it and follow the instructions to actually install busybox.
[Magisk] SeishiNui18:
I'll try to grab magisk.log or magisk_debug.log but here's the install log.

EDIT: magisk and magisk_debug attached for v15.1 beta
[Magisk] stefano91av:
Hi, why have I this situation?

Thank you. ;)
[Magisk] teddy0209:
Might be some props... Find the troubleshooting thread...
[Magisk] fishnchips2:
Tried magisk 15.1 on my honor 5c with dm-verity turned on. It booted but I had huge performance issues so I'm still using 14.0.
[Magisk] Alucard:
Is encryption after flash fixed,should i update it to 15.1?
[Magisk] Abraham_T.:
about preserve force encryption

hi

i am really very new to Magisk

i flashed rr rom and updated magisk to 15

at first the preserve force encryption was unchecked

then i got an ota update to 15.1

after the update it got check automatically and every time i uncheck it and reopen Magesk

its still checked

is this a bug?

is it necessary to have preserve force encryption checked that is on my op3t

the very opposite thing is on my mi mix and op3

meaning if the preserve force encryption checked i cant uncheck it and so the opposite

is it necessary to have preserve force encryption? is this a bug?
[Magisk] EthanChrisp:
v15.1 Boot Loops

Hi,

I'm experiencing a Boot Loop after updating to Magisk v15.1 via Direct Install (Recommended) on my SM-S975L running 7.1.1. I've made a Reddit Thread with all of my details and attempts: redd.it/7mws45 - Below is a copy of my Device and Magisk information. Any help or solutions would be greatly appreciated.

Device

Experiencing this on a Samsung Galaxy S4 (SM-S975L) with JDCTeam's AOSP Nougat 7.1.2, TWRP 3.0.0-0 F2FS.

Magisk Version: 15.1, successfully installs via Direct Install and Recovery

Magisk Install Method: Direct Install (Recommended)

Magisk Manager Version: 5.5.2, successfully updated via APK prior to updating Magisk

Magisk Manager Install Method: APK

Install Order: Prompted for Magisk Manager v5.5.2 Update, Install via APK, Prompted for Magisk Update v15.1, Direct Install (Recommended), Reboot.

Symptoms

Boot Loop on Samsung Logo

2 vibrations upon Boot

Still able to access Recovery and Odin Mode

KERNAL IS NOT SEANDROiD ENFORCING and Set Warranty Bit : kernel in top-left corner upon Boot

RECOVERY BOOTING...., RECOVERY IS NOT SEANDROID ENFORCING, and Set Warranty Bit : recovery in top-left corner upon Boot to Recovery
[Magisk] leonekmi:
Hi,

The SystemUI crashes when unlocking the phone (with password/scheme or without) with Magisk v15.X.

magisk.log : https://ghostbin.com/paste/d2xrd

liveboot.log (recorded with LiveBoot) : https://up.twittolabel.fr/liveboot.log

ROM : RROS 5.8.5 builded by sudru_petru

Phone : Huawei P9 (EVA-L09)

Substratum : Active with 4 overlays

No other modifications
[Magisk] exico91:
So, everything started when i updated Magisk to 15.0:

I got my phone encrypted and i have no way to disable that (i tried to even use dd to wipe the partition "LUKE" bits? i believe is called that way)

Now doesnt matter wich stock rom i flash i cannot pass safetynet CTS and the Basic integrity pass only if i dont install magisk (yeah i tried to troubleshoot that all day to no avail)

My phone is a Asus Zenfone 3 Deluxe ZS570KL TIM branded and i tried the only TIM rom available on asus.com and every WW non pro.

I opened a thread also on the Zenfone section. Since this started with magisk i tought ill just write there as well
[Magisk] underd0g:
I had an issue installing magisk since 14.6 newer.

Update through twrp it say success, but after boot magisk isn't isntalled.

Uninstall old magisk and then install newer version isn't working too.

Log said segmentation fault when patching boot.img.

But installing magisk 14.5 is working fine.

Here's the log.
[Magisk] Sudeep:
I have internet but it shows no internet

I am getting internet prmbls in magisk manager..I have internet then also. It shows no internet .and if I give root permission. To magisk manager then it shows unfortunately stopped magisk manager...I am using xolo era 4g 5.1 android version
[Magisk] adarshm4you:
Any solution?
[Magisk] Fild5x:
Magisk v15.1 working well on Galaxy a500h.
[Magisk] beast_drc:
Hi, guys! I have encryption problem. I have Mi5 and Mi6 with lineage 14.1 installed/ after flashing Magisk boot pattern dissapeared so phone can be booted without pattern drawing. As a effect TWRP dont ask me for the pattern either and Data partition is encrypted, so i cant flash anything with twrp. same situation on both phones

Please help ^)
[Magisk] makimo2989:
One plus 3 (with latest OOS5.0.1)

Bootloops after flashing full ROM, and then Magisk 15.1. Had to reflash full ROM again (without Magisk), to boot successfully into phone.
[Magisk] mctiew:
Still get the same error with Magisk 15.1 when trying to install in TWRP.

No problem in 14.0.
[Magisk] jhill110:
Screenshot says your trying to install 15.0. Try 15.1. Or try updating from MM.
[Magisk] [Alien]:
Can't install modules from Manager (15.1)
[Magisk] mctiew:
Both gave same error.
[Magisk] SeishiNui18:
Verify that you allowed MM to have access to storage.
[Magisk] alienware777:
Every time I reboot magiskhide is turned off and I fail safetynet. I turn it on, it passes again, until reboot.

Using pixel 2 vzw 8.1, TWRP, Magisk 15.1.
[Magisk] spiritflare01:
Hi

Flashed Magisk 14.1 under Lineage 14.1. when trying to update from within the app, it says downloading 15.1, but it never does. I see the toast to download, clicking on it is never successful.

So I just flashed 15.1 from TWRP and it works fine...

Side note:

cts profile always: false
[Magisk] DodoGTA:
It looks like that Magisk is incorrectly detecting your TV box as an A/B device (because Magisk v14.0 wouldn't even install if your device had the A/B partition scheme)

Also, can you run

find /dev/block

in a terminal emulator with root access or the TWRP root shell (TWRP main menu > Advanced > Terminal) and give the output of that command?
[Magisk] suleymanov_aydar:
Problem with the latest Magisk Manager build

Today I've updated the Magisk and Magisk Manager to the latest versions (by the Magisk Manager update option).

But after update I cann't open the Magisk Manager app. It's closing with error.

Previous version works perfectly.

Device: Highscreen Boost 3 SE Pro

OS: Android 6.0
[Magisk] cenovita:
[/COLOR]

Came here to post this very same problem, with the same phone and latest Oxygen.

Any help please?
[Magisk] ivanich:
Flash Magisk-15.0 from twrp and it'll work, after that you can update to 15.1 with MagiskManager.
[Magisk] Orka82:
Confirmed working on my OnePlus 3 with the latest beta. Thanks!
[Magisk] aaargh777:
Happened to me as well when coming from magisk 14.5, solved it by uninstalling magisk manager and flashing stock boot image, then flashing magisk 15.1 again.
[Magisk] gbeardmore:
No WiFi with 15.1 Update

OnePlus 5T on Oxygen OS 4.7.6 and blu_spark TWRP 3.2.1. When I try to update thru the MM app from 14.0 to 15.1 WiFi simply won't turn on. All is OK on 14.0. Tried clearing caches in TWRP, and re-booting... no joy. Ideas?
[Magisk] cenovita:
Thanks!

It worked!

And fast replied it was!!! :)
[Magisk] mctiew:
The system terminal emulator output and the twrp terminal output are different, attached
[Magisk] Shadear:
I have a problem when try to install a module in magisk manager (magisk 15.1) it give me error i have a logView attachment install_log_20171230_235737.log

View attachment install_log_20171230_235800.log
[Magisk] Codeacious:
Magisk 15.0 and 15.1 exhibit a strange issue where it causes an app to become unable to mount its OBB file. The app in question is FFT: WotL from the Google Play store.

I tested on a stock Oneplus 5T; when loading Magisk 14.0 via TWRP, the app works as expected. When loading Magisk 15.0 or 15.1 through Magisk Manager or TWRP, the install is always successful with nothing strange shown in the logs. The app can still download and write its OBB file to storage, but fails to mount it to /mnt/obb afterwards. Uninstalling Magisk 15.0/15.1 via the uninstaller and reflashing 14.0 fixes the issue.

I checked the filesystem permissions/ownership of the OBB file and /mnt/obb, and everything looked normal. Another app that uses an OBB had no issues and could mount its OBB file. The only difference between the two that I could discern is that the malfunctioning app was developed for an older version of Android.
[Magisk] Ludovicovan:
fail to upgrade from magisk 14 to magisk 15.1

hi i cannot upgrade/install magisk 15.1.

When I try to upgrade i get this message

java.lang.RuntimeException: An error occurred while executing doInBackground()

at android.os.AsyncTask$3.done(AsyncTask.java)

at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)

at java.util.concurrent.FutureTask.setException(FutureTask.java:223)

at java.util.concurrent.FutureTask.run(FutureTask.java:242)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)

at java.lang.Thread.run(Thread.java:818)

Caused by: java.lang.OutOfMemoryError: Failed to allocate a 134209548 byte allocation with 16765168

free bytes and 113MB until OOM

at java.io.ByteArrayOutputStream.expand(ByteArrayOutputStream.java:91)

at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:201)

at com.topjohnwu.crypto.ByteArrayStream.readFrom(Unknown Source)

at com.topjohnwu.crypto.ByteArrayStream.readFrom(Unknown Source)

at com.topjohnwu.crypto.SignBoot.verifySignature(Unknown Source)

at com.topjohnwu.magisk.asyncs.InstallMagisk.doInBackground(Unknown Source)

at com.topjohnwu.magisk.asyncs.InstallMagisk.doInBackground(Unknown Source)

at android.os.AsyncTask$2.call(AsyncTask.java)

at java.util.concurrent.FutureTask.run(FutureTask.java:237)

... 3 more

i cannot install it also from TWRP. My smartphone is xiaomi redmi 4 pro, my rom is MIUI9|V9.2.2.0 (xiaomi.eu)
[Magisk] sdz2:
Question: Where can I find magisk_v14.3.zip?

I have the same MagiskManager su database issue. I want to try dirty flashing 14.3, but I can't find it.

The releases page (https://github.com/topjohnwu/Magisk/releases) has a tag for 14.3, but the only files are source code.
[Magisk] alienware777:
Worked great. I actually went a step farther and fully reinstalled a new factory image tho haha. Go big or go home but the idea worked out thanks :D

New issue, I am passing safetynet consistently on a brand new android install, however I just downloaded lastpass and on start it told me "It appears you are using a rooted device..."
[Magisk] ManikandanGuru:
Magisk Manager is crashing on launch in Lineage OS 15.1 OP3T

Tried both Magisk 15 and 15.1 same issue.
[Magisk] gothicVI:
From the logs you posted I can see...

Oh wait there ain't none...

Some more information on your device and the used software could be helpful as well. Also how did you install magist and most importantly: which version of the manager are you using. You're only mentioning magisk itself.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] realthrash:
Hello, with the latest update (15.1)i had a big problem

If i update through Magisk Manager i got a brick, if i flash the zip on TWRP i got a bootloop (but i made a bootloop.img backup) too already patched the image but i got the same

I just rolled back to Magisk 14.0 and works great

Sent from Huawei CAM-L03
[Magisk] DodoGTA:
And, can you also run

cat /proc/cmdline

?
[Magisk] ManikandanGuru:
With Magisk 15.1 MM's version is 5.5.2

with Magisk 15 I don't know the MM's version sorry about that.

Regarding the log most of the logcat apps didn't work for me without the root obviously with the magisk manager getting crashed in launch. But managed to install a rootless log cat app and got the following log.

I don't know if it would be useful I am posting that here.
[Magisk] chudy_85:
I have only problem with grafic when open magisk manager. Lock on screenshot but when I close and open again the grafic it's correctly. I have this problem on Magisk Manager 5.5.0-5.5.2

Wysłane z mojego EVA-L09 przy użyciu Tapatalka
[Magisk] Didgeridoohan:
Looks like a broken Magisk installation. Could you upload your Magisk log? And maybe give some details about your device, ROM, etc...

Have you tried a fully clean install of Magisk? By that I mean use the Uninstall function in the Manager or the uninstall zip in recovery, possibly restore a stock boot image and then reinstall Magisk again.

Have you tried a clean install of v15.1 instead? By clean install I mean use the Uninstall function in the Manager or the uninstall zip in recovery, possibly restore a stock boot image and then reinstall Magisk again. You can make a backup of your Magisk image (it's in /data or /data/adb, depending on your installed Magisk version) and restore it after (on v15+ it's location is /data/adb).

That message in Lastpass is just information and shouldn't matter. If you're worried, you can hide root from the app by adding it to the Hide list and also hiding the Manager (option in the Manager settings). Most apps use other root detection methods than SafetyNet.

Logs would be nice...

Installation log from the Manager and the recovery log from the installation is a good start. If you can, a logcat during boot would be great. If it loops too early for a logcat, the recovery log and a copy of your boot image might be enough.

You can also use adb to capture logs from a computer without root permission. And an actual file rather than a screenshot is always appreciated.

Do you experience the same thing on a clean install of the Manager and Magisk (see above)?
[Magisk] mctiew:
There it goes :-
[Magisk] Shadear:
How to get you a log of magisk,my device is s5 900h lightwiz rom based on stock,stock kernal, i flashed the uninstaller zip and re installed magisk same ?
[Magisk] Sudeep:
My safety net fails..mycts profile is true..butbasicinterigty false...I am using magisk v15..and usingxposed framwork too(no system less one)

Is there anyway without uninstalling xposed ??
[Magisk] jenslody:
No, except for a workaround with systemless xposed.

If you have this, you can temporarily disable it in MagiskManager and reboot to bypas safetynet.
[Magisk] Didgeridoohan:
You can save the Magisk log from within the Manager.
[Magisk] Shadear:
View attachment magisk_log_20171231_143420.log
[Magisk] Didgeridoohan:
No... I just tested on v14.0, v14.5, v14.6 and v15.1. None of them create the Magisk image when installing fresh.

The Magisk image only gets installed when rebooting or when flashing a compatible module in TWRP. On Magisk v15+ this means a module based on the 1500 template. Flashing a 1400 template does not work in TWRP on Magisk v15+... Have you updated your kernel boot support module to template 1500?

P.S. I moved the discussing to the general thread. It's a better location for it...

---------- Post added at 13:33 ---------- Previous post was at 13:30 ----------

That, my friend, is a very broken Magisk installation...

I didn't see you posting any details about your device and setup. Device, Android/ROM/firmware version, kernel, what filesystem does your data partition use, any other modifications, etc. All of that could pertain to your issue.
[Magisk] Shadear:
My device is Samsung Galaxy S5 SM-G900h, lightwiz rom based on stock with stock kernal (dpi)
[Magisk] tdhite:
Hmm, interesting, the kernel flash always has installed its supporting magisk module directly after installing Magisk itself, and it is currently 1450 on the (older variable name) template. I'll update that and see where we land.

Regardless, thanks for your diligence, my readings to date suggested 15.x was supportive of 14.x module templates.
[Magisk] velss:
I need help guys... Yesterday i rooted and installed magisk on my htc one a9s.. Installed some modules and so, during today they just stopped working, just poof and they all arent working, however i can install and download them from magisk manager no problem, it says that everything is working, but they for sure are not.. Also my safety check says that ctsProfile and basicIntegrity is false.. Does that affect anything? How do i fix it? Any help appreciated.
[Magisk] Didgeridoohan:
No worries... Module template 14xx is still compatible with Magisk v15.x, but only when installing through the Manager.
[Magisk] Orjakone:
I am using the original firmware of my device, moto g4 play (6.0.1) and in this latest version of magisk, when the application requests root, when it allows, magisk manager warns that it crash.
[Magisk] tdhite:
Thanks a bunch, [MENTION=4667597]Didgeridoohan[/MENTION] -- in fact updating the modules indeed worked as suggested. I have no clue why I didn't think of that, sometimes just takes two pairs of eyes. :cyclops:

Anyway -- so with that, means the folks I dev for can now update their stock ROM, flash my kernel, wipe data, flash my latest debloating magisk module and presto: clean machine, no bloat at all (extremely debloated), safetynet passes like a champ and the phone is ridiculously efficient (speed and battery). That's why I was really working all this.
[Magisk] Damonzer:
i have basically the same magisk log when i flash 15/15.1,

i have those errors, root work, safety net fail on both item

samsung Galaxy S5 SM-G900F,

android 6.01,

stock kernel (as shown in phone info) :

3.4.0-9493471

dpi@SWHE8813 #1

32-bit

no module, nothing special done except installing magisk and running it in core mode

phone rooted to be able to mode heavy apps on sd card (apps2SD)