yashsingh1/xdaforums huggingface dataset:
[Magisk] Vinnom:
Magisk

Magisk Manager Version: 5.5.1(82)

Magisk Version: 15.0

Device: Huawei Nova

Rom: LOS 14.1

Hi! When I try to install a module, I get the following:

- Copying zip to temp directory
- Installing Module(any module).zip
- Mounting /system, /vendor, /data, /cache
! Magisk is not activated!
Failed!
! Installation failed

The behaviour above can be verified in install_logs attached.

I installed Magisk through recovery, after using the addon to unsu LOS (which has its own su). The installation was pretty ok. I had just clear flashed the ROM.

I captured a logcat too, probably it will be needed.

Just as complementary information, this occured with magisk 14.0 too, as I also tried (I clea flashed ROM so I could have a clean environment to flash 15v).

PS: I split it the logcat in beginning_of_system, beginning of crash and logcat_magisk_module_install. Size reasons. I don't know if everything will be needed, but it better to send a full logcat.

EDIT:

I forgot to mention that flashing module through recovery gave me a similar output (something like that magisk is needed and not found)
[Magisk] songokujames:
After I flash the stock boot image via fastboot, I am still stuck at Mi logo screen. Before that, my phone randomly reboot before enter the system. Any other solution?
[Magisk] theandroidguy:
Try using the magisk uninstaller after flashing the stock boot.img, and if possible go to the data folder using TWRP file manager and delete the magisk folder. I've came across this situation earlier and for me the only way to boot into system was to wipe the data partition
[Magisk] ahse0w:
Anyone using f.lux here? The phone screen becomes unresponsive after the v15 patch. I have to restart the phone and disable f.lux before it starts.

Anyone had this issue? I tried the other blue light filter apps, but I don't like the overlays that the other apps use.
[Magisk] songokujames:
I am using miui global developer. I am stuck at Mi logo Unlocked screen.

---------- Post added at 03:16 PM ---------- Previous post was at 03:09 PM ----------

I was able to boot in the system again after I flash back boot image and magisk v14 installer. But if I uninstall magisk, I will be unable to enter the system. Any reason for it? And adaway unable to request root access at magisk v15, that why I downgraded back to v14.
[Magisk] m7md_ramadan:
I have the same issue after installing magisk v15.0 but with huawei y6 , Rom : Los 14.1

When trying install a moudel , i get this:

- Creating /data/magisk_merge.img with size 64M update-binary[122]: /sbin/.core/mirror/bin/magisk: not found update-binary[125]: /sbin/.core/mirror/bin/magisk: not found

- Mounting /data/magisk_merge.img to /dev/magisk_merge ! /data/magisk_merge.img mount failed... Failed! !

Installation failed
[Magisk] ostralopiteq:
On n6, worked like a charm, thank you a lot.

No problem, no bugs, no issues.
[Magisk] The_Dipster:
I just came here to report v15 causing screen crashes on my nexus 5x on latest 8.1 (it becomes total a graphical hangup), but this right here makes me think that f.lux and magisk might not be playing nice together anymore. I've moved back to v14 and that fixes the issue as well.
[Magisk] Wesley32:
I've seen a few others mention that Huawei phones with Magisk 15.0 have issues with Bootloop. I have Huawei Honor 8 and I get bootloops with 15.0. I can use 14.3 just fine though. Any thoughts?
[Magisk] Hexyl:
I have the same problem. Even after a clean rom install this happens. Does somebody knows a solution for this?
[Magisk] Einsteindks:
Damn! Having trouble with Magisk Manager 5.5.1, and toyed with the idea that Lux is, once more, causing issues. 15 installed OK under 542, updated to 551, crashes at opening the app.
[Magisk] AndrOmega:
the update will appear shortly and will fix all errors(hopefully)

:good:
[Magisk] fishnchips2:
I have a Huawei Honor 5c and my phone boots with the stock android boot animation rather than the Honor one and breaks any graphics intensive apps, the microphone, camera etc...

I rolled back to 14.0 stable and it's functional again.
[Magisk] mrror:
Manager 5.5.1 force close upon launch

Since the latest releases (at least 5.5.1, I tried to revert back to 5.5.0 and same error occurred) Manager crashes upon launch.

From what I can understand from the logcat (attached along with device info) there's some trouble in opening db and/or setting the locale.

I'm on latest stock rom for my device.

I've tried a full cleanup (uninstall xposed installer/magisk manager/xposed framework/magisk, restore stock boot image, reinstall magisk and manager) but that just lead me to the same situation.

EDIT: reverted back to Magisk 14 and Manager works! Should I install Magisk beta to send a debug log or wait for a bugfix?
[Magisk] moderndaycowboy:
I have lost root twice at v15. I Had a similar problem with 14.5 and 14.6

I am using note 8 exynos, stock rom with smurf kernel.

Any advice?

---------- Post added at 07:24 PM ---------- Previous post was at 07:03 PM ----------

I found one issue at v15,

After enabling systemless host support on magisk app, it causes safetynet false, I reverted and safety is true now.
[Magisk] Stallio:
Sorry to comment here but I didn't found any other place, magisk zip 15 is corrupting the whole device when flashes with recommended way from magisk manager app, I have to reinstall the whole is with QIFL, So now I am not installing the zip 15.0 at all, I hope there is some major bug. Device is Lenovo Vibe X3.
[Magisk] Stunherald:
Hello sToRm,

HERE is package with all requested files, logs, etc. I did three tests - details are in "info.txt" inside.

Thank you in advance for your time! I hope you'll manage to fix it (will sent you few beers ^^)

Alex
[Magisk] munchkin40k:
Having trouble on oneplus one with multirom installed. 14 works fine on all ROMs but 15 comes up as not installed on secondary ROMs :(.

Oh well. Back to 14.
[Magisk] yung40oz84:
Same issue I posted above previously on Oreo 8.1, now on Oxygen 4.7.6 for OP5T after the img gets full nothing else will flash, I tried resizing the img, etc. no dice. Back to 14.0

---------- Post added at 02:37 PM ---------- Previous post was at 02:35 PM ----------

I have the same issue here on OOS 4.7.6 magisk 15
[Magisk] supermaus100:
Hello,

is there already Magisk for the HTC U Play?
[Magisk] rom-g:
Same bug for me (motog3 osprey, and stock 6.0.1 ROM too...). See my report here.

Magiskmanager 5.5.1 and Magisk 15.0 is ok until it tries to access the SU database for the first time. After that, the manager always crashes (and su access can never be granted). The only solution working for me was to dirty flash the magisk_v14.3.zip over it.

And, just for fun, i flashed an AOSP Oreo 8.0 ROM on this phone and installed magisk 15.0 on it. Everything was fine with this Oreo ROM... No magiskSU bug at all.. So it really sounds like we're facing an incompatibility between stock 6.0.1 motorola ROM and Magisk 14.6 or 15.0.
[Magisk] mr_shaba:
All works fine on my note 8 exynos (Dr. Ketan N7 rom with included stock kernel), enabled magisk hide and also systemless host support and still successfully passing the safetynet test.

Lost root only once immediately after using root check and safetynet test apps from play store. Two times magisk wasn't found anymore by the manager right after booting the device, another reboot fixed that again.
[Magisk] moderndaycowboy:
Yeah reboot always fixes that situation,

Swiping magisk manager left caused lost root issue too.

I have lost again 15 min ago:laugh:

I will never open magisk again :silly:

---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------

Also busybox magisk module makes the phone laggy.

Did you experience it?
[Magisk] jasio2k:
Oneplus 3T RR 5.8.5 all works fine. No error or problem @ the moment, log clear from any error. Thx
[Magisk] Mezabaru:
Has anyone been getting the error symlink /root/magisk->/sbin/resetprop failed with 17: File exists , I've been trying to figure this one out, but I can't find much online, just did a fresh install of magisk and its still present sadly, Even tried core mode.
[Magisk] Damonzer:
so, after flashing uninstaller and stock boot image (to be safe) then installing manager, then 14.0, i could get safetynet to pass (and without those errors in magisk log), but flashing 15.0/15.1 result in errors and safetynet failing, i flashed the 15.1 through twrp, maybe i will try the option to patch img in manager and see what happen...
[Magisk] Alucard:
Just uninstall magisk and then install v14.
[Magisk] NiTrOwow:
I just updated to Magisk 15.1 and now SafetyNet status is FAILED.

Flashed Universal SafetyNet Fix stable and still didn't fix it..

First it bricked my phone(from v13 to I believe v13.1 or higher) then a bugfix for this came but lost the SafetyNet.

My phone acted strange after a "Complete uninstall" of Magisk, but luckily after 2 reboots the phone started again. First reboot crashed?

Will try v15 again, it worked for me with SafetyNet passed after the universal SafetyNet fix. If v15 works I will probably stay at this version and wait a little bit longer for a version that works and passes SafetyNet.

PS I never touched "MagiskHide". So that's really odd.

Edit: It seems to be fixed now after uninstalling and reinstalling v15.0 and updating to v15.1.
[Magisk] Chinaboy5216:
Note 3 SM-N9008V China model Qualcomm cpu running RRN CHN 5.8.5 vidwhal rom with latest Magisk 15.1 and Magisk Manager 5.5.2 install ok, su ok, safety net passes (use VPN due to being in China)
[Magisk] Gysper:
Almost the same thing happened to me, went to update to 15.1 and SafetyNet failed and it said it was actually uninstalled, but rebooting my phone it went back to normal. Even Chase Pay works now.
[Magisk] TapioH:
You should check which kernel you are using. I went to RadioActive on my OPO because of bootloop. For some reason magisk failed to boot on stock kernel or lightning kernel.. Im on nougat rom though. Also you should find Update-UnSU.zip and use that in recovery aswell before installing magisk and phh su
[Magisk] rick.wardenburg:
I have the j320p and ive used it flashs and works like its saposed to . Flash magiskv6 and then supersu magisk, cant use any android pay with this device so no need to use phhsuperuser
[Magisk] geek85:
no
[Magisk] bedrieglijk:
Hello, Please help me with a complete guide to install Magisk on Xiaomi Mi4c. I try to install on stock ROM Miui but it's not working. sorry for my bad english..
[Magisk] mat1jaca:
j320p uses different cpu
[Magisk] rick.wardenburg:
If you have twrp already installed you would be abler to recover if you have a backup theres people in the j320p thread that have same device as yours and works
[Magisk] DarkLudo77:
Hello,

There was a bootloader update for asus zenfone 2, so new boot image, when after installing magisk zip, phone auto-boots always in recovery, even if I choose system, or turn off or bootloader.

-Asus Zenfone 2, ROM: Dirty Unicorns, TWRP 3.0.2 M1
[Magisk] bw03:
Working great on my Moto X Pure XT1575 running Android 6.0. Had TruPureXMM rom with xposed before hand.

I uninstalled xposed, unrooted, and did the Magisk, systemless xposed, and Magisk Manager install according to the instructions give in each thread.

All works great. Android Pay and Pokémon Go 0.37 works too.

Thanks topjohnwu.
[Magisk] IamIrene:
can I know which xposed framework you installed ?

alt version or normal version ?

I am using normal version for my note 4 (N910C - Exynos processor)

will report result soon as I just fully unroot lol
[Magisk] Neerijus:
Is there a way to install Magisk on LG G3 858HK MM? Anyone?
[Magisk] Äptiva:
Stock MM? If you can bump then yes. If your phone won't accept bumped recoveries and kernels then no
[Magisk] -Happy Feet-:
Look at the Z2 forum
[Magisk] chris9000:
Darn it. I had Magisk up and working earlier, was able to load Android Pay with no issues. Had it on stock rom and ElementalX kernel. Reinstalled everything for an unrelated reason last night, finding today that Android Pay isn't working! Getting the "Android Pay can't be used" message now!
[Magisk] ChefChaudart:
And OP is there for what ??????????????????????

Bloody hell !
[Magisk] Äptiva:
What device?

Knowing the device helps the dev know what devices to look through info. Knowing a process for specific devices can be added to OPs. In the op he added "Some LG Locked bootloaders need something called "bump". That was because of myself and a few other G2 owners finding the way to get around the bootloader like we have been. G3 users that can bump boot images and recoveries I do believe the process is the same for you guys.

Simply saying "Got it working" is as unhelpful as saying "Doesn't work. What do I do?"
[Magisk] chris9000:
Nexus 6P. Sorry about the lack of info!

I'm very much open to the possibility that something I did (or didn't) do during the 2nd install time may have differed. I have xPosed installed. I wish I'd backed everything up, but for some odd reason, my phone has issues sending large files over via USB. Guess I'll be reinstalling everything from scratch.

EDITED to add:

Will using a Toolkit to reinstall everything to stock be sufficient for removing prior roots?
[Magisk] Druboo666:
[MENTION=631273]Chainfire[/MENTION] posted this saying super su might also work with magisk [MENTION=4470081]topjohnwu[/MENTION]

http://xdaforums.com/showpost.php?p=68684253&postcount=403
[Magisk] superjase:
when i try to turn of root in the magisk manager app, phh superuser pops up to grant permission. i allow magisk manager superuse access and the swith to turn off root (root toggle) turns off, but turns back on by itself a moment later.

any ideas!
[Magisk] alanmv567:
What phone are you running?

Did you factory reset your phone, boot into TWRP, flash both the magisk zip and phh su zip then reboot phone? Then once your phone has started installed both the Magisk manager apk and phh su from the google market?
[Magisk] Macmoc16:
when I flasho magisk 15.1, on my oneplus one with linage 15.1 it goes into bootloop. During the installation it seems to be all right, a part of this:

! Installed root system detected, mount rw :(

Despite having worked a wipe system and checking with root checker, and it fails. I do not know what to do, I do not understand what is the error even trying a flash unistall magisk, the device does not share the same saying that magisk is not installed. Sorry if I was wrong but I did not know where to write it and I did not find anything about it. Thanks in advance to those who friend me :)
[Magisk] Josey Wales:
Latest MM v5.5.2 and Magisk v15.1 update will NOT open MM at all. . . "Magisk Manager has stopped working" error.

I cannot open MM, no log generated. . . I tried flashing MM uninstaller in TWRP but failed WTF, first time for everything?!

Galaxy Note 5

Stock rooted 7.0
[Magisk] NiTrOwow:
I have updated my post. My problem with SafetyNet dissapeared after doing ;

Go to Magisk Manager

Hit Uninstall > "Complete uninstall"

Reboot 2 times (first reboot crashed or was canceled?!)

Install v15.0 by TWRP

Open Magisk Manager again after installing v15.0

Update from Magisk Manager to v15.1

Reboot

Now SafetyNet passes.

I assume that something went wrong on the updating process from v15.0 to v15.1.

Not sure what happened but it works now.
[Magisk] Floodland:
A question to understand a little better: what triggers /data encryption even it was clean, without encryption and working fine? I know magisk write to /data, but the partition is not encrypted at that point (if installed from recovery at least), but when Android boots. I know there must be a reason, but I see it unnecessary, risky and harmful...
[Magisk] Simone98RC:
Magisk v15.1 has damaged dm-verity

Just tonight I've upgraded to Magisk v15.1.

Premise: I own a Oneplus 3 with OxygenOS OB28.

The SafetyNet check failed, so I tried to both reinstall OxygenOS OB28 with Magisk itself.

The result for a long while was an unbootable device with the dm-verity warning at every boot (even in recovery mode).

Until I decided, as partial workaround, to reinstall Magisk v15.0 and v15.1 in that order, then wipe cache and reboot.

The dm-verity screen is still shown, but device now boot properly.

[MENTION=4470081]topjohnwu[/MENTION] please note that, according to recovery output, only Magisk v15.0 recognizes properly dm-verity and try to patch fstab.

Probably (I've no free time to try), by reinstalling only Magisk v15.0, the dm-verity screen might disappear.

The dm-verity error persists even by reinstalling firmware, even by installing Magisk v15.0, even by upgrading to Magisk v15.2.

It means I've to lock and unlock bootloader, to fix them... but I prefer to think there's an easier solution.
[Magisk] jhill110:
Ok! Update to 15.1 from 14.0 worked!

Updated through MM 5.5.2 and my Galaxy Tab s2 stock rooted Nougat is working as it should now.

I spent a lot of time trying to get 15.0 going with no luck so this is great!

Thanks [MENTION=4470081]topjohnwu[/MENTION] for the work you and your testers have done. :svetius::svetius::svetius:
[Magisk] Vinnom:
Google for osmose unSu. Flash it before flashing magisk.

This probably occur because you didn't clear LOS built-in su.

HUAWEI NOVA user since 12/2016 =)

---Current ROM: AospExtended

---Kernel:stock

MOTO X user since 03/2015 =)

---Current ROM: Tesla N

---Kernel: Tesla N stock

NEXUS 4 user 2013-2015 =/

Kernel Adiutor Interactive profile: INTERACTIVE

Kernel Adiutor Intelliactive profile: INTELLIACTIVE

Kernel Adiutor Intellimm profile: INTELLIMM

Kernel Adiutor Smartmax profile: SMARTMAX
[Magisk] jackieku:
v15.1: magiskinit: Segmentation fault

I noticed that sepolicy injection tool was moved from magisk to magiskinit after updated from v14 to v15.1.

However, when I attempt to execute magiskinit command in a root shell it always crashes immediately, with any arguments that I think it should accept.

I tried,

# /data/magisk/magiskinit
# /data/magisk/magiskinit --help
# /data/magisk/magiskinit magiskpolicy --live 'allow kernel system_block_device blk_file read'
# /data/magisk/magiskinit supolicy --live 'allow kernel system_block_device blk_file read'

This is the log of the crash:

--------- beginning of kernel
12-29 11:40:47.322 0 0 I magiskinit[5874]: unhandled level 2 translation fault (11) at 0x00000018, esr 0x92000006
12-29 11:40:47.322 0 0 F : pgd = ffffffc01dc7b000
12-29 11:40:47.322 0 0 F : [00000018] *pgd=00000000b127c003, *pmd=0000000000000000
12-29 11:40:47.322 0 0 W : CPU: 1 PID: 5874 Comm: magiskinit Tainted: G W 3.10.103-g5e329b33dbe #1
12-29 11:40:47.322 0 0 W task : ffffffc02a2eeb80 ti: ffffffc028084000 task.ti: ffffffc028084000
12-29 11:40:47.322 0 0 W : PC is at 0x455808
12-29 11:40:47.322 0 0 W : LR is at 0x45369c
12-29 11:40:47.322 0 0 W pc : [<0000000000455808>] lr : [<000000000045369c>] pstate: 60000000
12-29 11:40:47.322 0 0 W sp : 0000007fca7426f0
12-29 11:40:47.322 0 0 W : x29: 0000007fca7426f0 x28: 0000000000000004
12-29 11:40:47.322 0 0 W : x27: 0000000000000003 x26: 00000000ffffffff
12-29 11:40:47.322 0 0 W : x25: 0000007fca7427f8 x24: 00000000004cd000
12-29 11:40:47.322 0 0 W : x23: 000000000048e858 x22: 0000000000000000
12-29 11:40:47.322 0 0 W : x21: 00000000004934d8 x20: 0000000000000000
12-29 11:40:47.322 0 0 W : x19: 0000000000000018 x18: 00000000004f3e08
12-29 11:40:47.322 0 0 W : x17: 0000000000000000 x16: 00000000004f3000
12-29 11:40:47.322 0 0 W : x15: ffffffffffffffff x14: 00000000004f3000
12-29 11:40:47.322 0 0 W : x13: ffffffffffffffff x12: 0000000000000023
12-29 11:40:47.322 0 0 W : x11: 0000000000000003 x10: 0101010101010101
12-29 11:40:47.322 0 0 W : x9 : 7f7f7f7f7f7f7f7f x8 : 0000000000000050
12-29 11:40:47.322 0 0 W : x7 : 6163686e71636d60 x6 : 12050d0230000a0b
12-29 11:40:47.322 0 0 W : x5 : 0b0a0030020d0512 x4 : 0000000000000000
12-29 11:40:47.322 0 0 W : x3 : f35a6d9a85b1755d x2 : 0000000000000000
12-29 11:40:47.322 0 0 W : x1 : 00000000004f0d60 x0 : 0000000000000018

This is a Nexus 9 LTE that is running RR nougat ROM.

I need to inject a policy to get swap on loopback device working, please help!
[Magisk] Vinnom:
After updating to:

Magisk Manager Version : 5.5.2

Magisk Version: 15.1

This still occurs

HUAWEI NOVA user since 12/2016 =)

---Current ROM: AospExtended

---Kernel:stock

MOTO X user since 03/2015 =)

---Current ROM: Tesla N

---Kernel: Tesla N stock

NEXUS 4 user 2013-2015 =/

Kernel Adiutor Interactive profile: INTERACTIVE

Kernel Adiutor Intelliactive profile: INTELLIACTIVE

Kernel Adiutor Intellimm profile: INTELLIMM

Kernel Adiutor Smartmax profile: SMARTMAX
[Magisk] OreoCupcakes:
After updating to 15.1 my phone lost forced-encryption even though I had the box checked to keep it. Now my phone automatically decrypts on boot into recovery and brings me straight to the lock screen.

Device: OnePlus 3T (OOS 4.5.1)
[Magisk] SeishiNui18:
Updated to Magisk Manager 5.5.2, tried to update from v14 to v15.1 through it shows success but after reboot still stays with v14. I tried:

Complete uninstall, run latest uninstaller through TWRP then restored stock boot.img. Reboot back to TWRP to patch v14 again, reboot to system and installed MM 5.5.2 directly. Check SafetyNet and all good. Update through MM to v15.1 is successful but after reboot still stays with v14. Flashed v15.1 in TWRP and no bootloop plus SafetyNet passes.
[Magisk] Sir Backe:
Hi Didgeridoohan,

Thanks really a lot for your efforts. Yes I meant contract code. I do not arrive there due to whatever reasons. The app recognizes root before. So at the moment I don't know what more I should ask. Since it works on your phone it must be a problem of mine. But where to search? What to do else? I don't know.

I also tried hiding the manager already before. It also didn't work.

Anyhow Tks really a lot, I appreciate your efforts. If you have any further idea what I could try, just let me know.
[Magisk] AndreSantoro84:
Hello everyone. Until version 14, the app worked perfectly for me, with no problem whatsoever, but in version 15 the "hide" function stopped working, with applications detecting root normally. I went back to version 14 and it worked again. I have now updated to version 15.1 and the problem persists, the "hide" not working. Has anything changed in this sense? What do I need to do to fix this? Appreciate.
[Magisk] ahse0w:
I am on the Nexus 6P. Trying out the Qualcomm option rather than the composite option for color filtering.

Seems like i am not the only one.
[Magisk] Fild5x:
During installation I see something like installation boot partition detected. Is that a big issue?
[Magisk] ahse0w:
Are you crashing at the opening of f.lux? My issue is with graphical hangups. Screen is working, but the actual graphics is screwed up.

Did you roll back to 542? Did it help?
[Magisk] Einsteindks:
Not exactly. Lux has been a conflict issue before, thought it was why 551 was crashing at opening. I did revert to 542 while the latest snafu played out. Turns out bad Magisk coding at fault, Lux was innocent. I'm fully updated now, although some minor coaxing was involved, nothing advanced.
[Magisk] nuxbag:
I have a Sprint Note 4 6.0.1 stock, I am not getting past the Sprint boot screen. With the new Masky 15.1 with the systemless modified xposed. It will boot without Xposed.
[Magisk] SeishiNui18:
Try the new Manager 5.5.2 and Magisk v15.1, add the app on MagiskHide list then Settings and select to hide Manager which will repackage the Manager app. Tried your app and I can get to the contact number screen. I don't have xposed installed.
[Magisk] matuszp:
Magisk v14 on stock LG G6.

I get notifications about new update but when I click on it nothing happens.

Same situation when I try to update directly from the app.

Nothing happens.

Any clue how to fix it?

Wysłane z mojego LG-H870 przy użyciu Tapatalka
[Magisk] IamIrene:
few days ago update to 15.0, safetynet check failed

tried flash the uninstaller and flash back 15.0 zip file, still same

and just now tried to update 15.1 by flashing it through twrp, unable to check whether safetynet is success or failed as once I boot my phone, lots of process keep pop out show stopped working

reverted back to 14.0 by using previous nandroid backup, working flawlessly

*running on Galaxy Note 4 N910C stock rom 6.0.1