yashsingh1/xdaforums huggingface dataset:
[Magisk] Denkai:
Logs?

And why I am posting:

I have OOS 4.5.10 on One Plus 5.

Installed 14.2 over 14.0, still went straight to bootloader (bad boot image, no boot, no adb. Most importantly: NO LOG. So don't ask.)

I completely wiped and did a fresh OS install with 14.2 and no issues. Reinstalled my Nand backup, wiped all traces of magisk off the device via magisk uninstall file on the main thread. Reinstalled 14.2 and it booted fine. Rebuilt with all the same mods and no issues. Not sure why but I think OnePlus devices might be getting corrupted boot.img files from stock backup for the update files, or something else is going on, but again, I can't pull log as the bootloader is what instantly comes up.
[Magisk] wiggmpk:
My bad, uploaded them
[Magisk] gaww:
Oops have done that before but forgot about it- thanks.
[Magisk] Arastha1995:
Where i can find recovery.log .. If to late to get.. Sorry..

I success dirty flash magisk 14.2 from magisk 14 on my Asus Z00LD running LOS 14 last update ::fingers-crossed:
[Magisk] micgeb:
I have the same error on a LG G6.

With twrp don't work too.
[Magisk] micgeb:
Here is the log.
[Magisk] arcane47:
Same issue... Hope to post logs. There was talk of this around Sept 8th.
[Magisk] Tylog:
For me all is fine.

Android 8.0 Pixel XL , Root works, Module works , TWRP sticks , perfect.
[Magisk] gudenau:
Made it work. I now have Magisk. ^^
[Magisk] wiggmpk:
Just curious, what version of Magsik Manager are you using?

Did you install v14.2? Clean install or over and existing install?
[Magisk] EstiR86:
Also curious how did you get twrp to stick
[Magisk] wiggmpk:
The official 3.1.1-0 TWRP boot IMG and flashable zip works for me on Stock Android 8 Pixel XL (Google edition)
[Magisk] EstiR86:
Ah okay thanks and when I tried to unroot using SuperSu and tested to see if im still rooted I am, do you know how to unroot using super su?
[Magisk] wiggmpk:
That I do not, I haven't used SuperSu in a long while. I rely on Magisk for a root solution.
[Magisk] EstiR86:
I did too but Magisk wasn't supported on the pixel until recently so I am trying to unroot and reroot using Magisk
[Magisk] dahawthorne:
Search the site for Osmosis' unsu.zip, which you can install in TWRP followed by installing Magisk. Check the unsu.zip log in TWRP for a line saying that it has restored the stock boot image. If not, to be sure that Magisk has a clean boot image to work with, flash your ROM's stock boot image and then Magisk.
[Magisk] Bryanx86:
Will magisk restore stock boot Image on pixel XL? I think you have to reflash factory image, minus the -w and you'll keep your data. This will unroot you, (recovery is stored in boot image), I wasn't able to get it to boot fastbooting stock boot img on pixel xl [MENTION=7722355]EstiR86[/MENTION]
[Magisk] Tylog:
When in twrp ( fastboot install )

in this order ,

Flash twrp 3.1.1-0 ( Even though previously done with fastboot) , flash boot img or ElementalX or whatever kernel, flash magisk 14.2 , then reboot.

Btw.

Flashing the boot img remove superSU , no unSU necessary to remove superSU.
[Magisk] heri1978:
V14.2 run flawlessly ,GT-I9205 - RROS 5.8.4, flash over v14.0 within magisk + YDS busybox.
[Magisk] skulldreamz:
[MENTION=631273]Chainfire[/MENTION] is aware that this issue is extremely early in the boot process. Liveboot is a app developed by him that you should check out
[Magisk] Didgeridoohan:
What do you mean by this? Did you use a different root solution than Magisk on A? I'm not familiar with A/B devices (so it might be worth ignoring me on this :p), but that sounds like it could cause some issues...
[Magisk] mobadass:
I'll see if I can get this working but it's a bit complicated as I have to install it to B while on A.

Edit: Actually this seems very hard to do as Liveboot will write logs to /cache, which doesn't exist on this phone.

I used CF-Auto-Root on the boot.img of A and "fastboot boot"ed that on A.

That'll modify /system on A and get me root.

I don't believe it would cause problems as it won't touch the B system partition/B boot at all.
[Magisk] skulldreamz:
Are you trying to use A/B as sperate ROMs?? 1 stock & 1 custom? If so then make sure 1st of all you have the aboot flashed to each part.... Then come back and flash the boot.img from whatever firmware your using to each A - B partition. From there you'll be good. Especially now that TWRP is not just bootable but dependant
[Magisk] mobadass:
I'm just trying to use A to bootstrap B with Magisk then restore the A to stock so I'd have a system that's rooted and can do OTAs.
[Magisk] Didgeridoohan:
You shouldn't have to go through all that trouble. From what I understand it's very easy to keep OTA functionality on A/B devices.

Have you looked at the OTA tips in the official Magisk docs?
[Magisk] bl8demast3r:
Magisk crashes whenever I try to open superuser or try to open an app that requires root. I'm on a Pixel XL.

--------- beginning of main
I( 469: 469) Magisk v14.2(1420) daemon started
I( 469: 471) ** post-fs mode running
--------- beginning of system
I( 469: 612) ** post-fs-data mode running
I( 469: 612) * Mounting mirrors
I( 469: 612) bind_mount: /system_root/system -> /dev/magisk/mirror/system
I( 469: 612) mount: /dev/block/platform/soc/624000.ufshc/by-name/vendor_a -> /dev/magisk/mirror/vendor
I( 469: 612) bind_mount: /data/magisk -> /dev/magisk/mirror/bin
I( 469: 612) * Mounting /data/magisk.img
I( 469: 612) * Running post-fs-data.d scripts
I( 469: 612) * Running module post-fs-data scripts
I( 469: 612) * Loading modules
I( 469: 635) * Starting MagiskHide
I( 469: 635) hide_utils: Hiding sensitive props
I( 469: 635) hide_list: [com.google.android.gms.unstable]
I( 469: 635) proc_monitor: init ns=mnt:[4026531840]
I( 469: 787) ** late_start service mode running
I( 469: 787) * Running service.d scripts
I( 469: 787) * Running module service scripts
I( 469: 635) proc_monitor: zygote ns=mnt:[4026534246] zygote64 ns=mnt:[4026534247]
--------- beginning of crash
I( 469: 635) proc_monitor: com.google.android.gms.unstable (PID=6392 ns=mnt:[4026534467])
I( 6397: 6397) hide_utils: Re-linking /sbin
I( 469: 635) proc_monitor: com.google.android.gms.unstable (PID=8954 ns=mnt:[4026534514])
I( 469: 635) proc_monitor: com.google.android.gms.unstable (PID=10179 ns=mnt:[4026534534])
[Magisk] Flippy498:
The thread got cleaned a bit.

Please use the report button if you think a post is breaching the rules. If you comment on such posts you only increase the workload of the mod team. Thanks for your understanding!
[Magisk] LinoX:
bug in latest beta (14.2 / 5.3.5)

when I ask for "su" in an "ADB shell" magisk identifies it incorrectly.

I was really surprised when I got the "Gear VR Shell has obtained root permission".

also...in the SU enabled app list it appears the wrong program.

PID requesting shell is 2000

D( 3147: 9205) su: request from client: 14

D( 3147: 9205) su: request from uid=[2000] (#1)

D( 3147: 9205) su_db: query policy=[2]

D( 3147: 9205) su_db: query root_access=[3]

D( 3147: 9205) su: waiting child: [9206]

D( 9206: 9206) su: child process started

D( 9206: 9206) su: argc=[1]

D( 9206: 9206) su: argv[0]=[su]

D( 9206: 9206) su: cwd=[/]

D( 9206: 9206) su: pts_slave=[/dev/pts/1]

D( 9206: 9206) su: stdin using PTY

D( 9206: 9206) su: stdout using PTY

D( 9206: 9206) su: stderr using PTY

D( 9206: 9206) su: use namespace of pid=[9203]
[Magisk] GingaB:
Magisk is just brilliant. Wayyyyy better than SU!
[Magisk] AlexBurnout77:
Thanks

Let's go
[Magisk] LinoX:
clean installation through odin doesn't create magisk.img

also....

if installed through ODIN on a CLEAN data (Samsung S8 950F) the setup isn't done properly:

/data/magisk.img isn't created and I can't install modules

...
D( 3154: 3250) e4crypt_init_user0
D( 3154: 3250) e4crypt_prepare_user_storage for volume null, user 0, serial 0, flags 1
D( 3154: 3250) Preparing: /data/system/users/0
D( 3154: 3250) Preparing: /data/misc/profiles/cur/0
D( 3154: 3250) Preparing: /data/misc/profiles/cur/0/foreign-dex
D( 3154: 3250) Preparing: /data/system_de/0
D( 3154: 3250) Preparing: /data/misc_de/0
D( 3154: 3250) Preparing: /data/user_de/0
D( 3154: 3250) e4crypt_unlock_user_key 0 serial=0 token_present=0
D( 3154: 3250) e4crypt_init_user0 completed
I( 1: 1) 200 3369 Command succeeded
I( 3371: 3371) tzdata file /data/misc/zoneinfo/current/tzdata does not exist. No action required.
I( 3153: 3178) Exiting registry update open thread [hardware/samsung_slsi/exynos8895/mobicore_kinibi400/Daemon/src/RegistryUpdate.cpp:143]
I( 3148: 3375) ** post-fs-data mode running
I( 3148: 3375) * Mounting mirrors
I( 3148: 3375) mount: /dev/block/dm-0 -> /dev/magisk/mirror/system
I( 3148: 3375) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor
E( 3148: 3375) mount /data/magisk->/dev/magisk/mirror/bin failed with 2: No such file or directory
I( 3383: 3383) Service started: /system/bin/bootstat -r post_decrypt_time_elapsed
D( 3154: 3273) post_fs_data done
D( 3154: 3273) Just triggered restart_framework

Verbose logs:
--------- beginning of main
I( 3148: 3148) Magisk v14.2(1420) daemon started
D( 3148: 3149) sepol: Starting large patch thread
I( 3148: 3150) ** post-fs mode running
--------- beginning of system
D( 3148: 3149) sepol: Large patch done
I( 3148: 3375) ** post-fs-data mode running
I( 3148: 3375) * Mounting mirrors
I( 3148: 3375) mount: /dev/block/dm-0 -> /dev/magisk/mirror/system
I( 3148: 3375) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor
E( 3148: 3375) mount /data/magisk->/dev/magisk/mirror/bin failed with 2: No such file or directory
I( 3148: 3470) ** late_start service mode running
I( 3148: 3470) * Running service.d scripts
D( 3148: 6670) su: request from client: 9
D( 3148: 6671) su: collector started
D( 3148: 6670) su: request from uid=[10323] (#1)
D( 3148: 6670) su_db: query policy=[2]
D( 3148: 6670) su_db: query root_access=[3]
D( 3148: 6670) su: waiting child: [6677]
....

Workaround found:

You solve the problem by opening magisk manager after you flashed the odin image and doing a "direct install" despite magisk manager says it's already installed.

You should edit the installation instructions here: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

to take this into account
[Magisk] Ex-Hunter:
Sorry for hijacking but I'm also facing the same issue. There is no TWRP for Mi A1 (It uses a/b partitioning). So,

I flashed the patched boot.img to the active slot --> Bootloop

Rooted slot a using CFRoot method and installed MagiskManager and followed the instructions as per official docs --> Bootloop

Flashed Magisk to slot b (which has the OTA update) using FlashFire --> Bootloop

Had to flash the stock boot.img or the one patched with CFRoot to get out of bootloop.

I think it has to do something with patching process in Magisk but I am no expert. Also, can't find any way to get logs.

Feeling frustrated :(
[Magisk] Cristiano Lira:
MagiskManager won't show up on APP drawer and I can't install via the apk. Any tips?
[Magisk] guest4711:
What happens if you try to install it? Please provide error-message(s) and logs.
[Magisk] majee12:
Bootloop after flashing the new update.
[Magisk] guest4711:
Had the same issue on my SG4 i9505. Wiped system and cache+dalvik, reflashed ROM & magisk - and all was fine again. I think the saved bootimage was corrupt...
[Magisk] Cristiano Lira:
Note to devs: Package installer simply states that is wasn't installed. The thing is the flashable zip installer isn't working properlly. It installed (via apk) after I uninstalled magisk and wiped and reinstalled my rom.
[Magisk] Bhagyesh19:
can i install magisk on XIAOMI MI A1(Stock Android 7.1.2) ?
[Magisk] Artim_96:
You can install it on every device
[Magisk] Spartacus500:
[MENTION=4470081]topjohnwu[/MENTION]

The Samsung Galaxy S7 edge nougat 7.0 Stock Rom works, but why do you write that the latest version is v14.0 ?

https://postimg.org/image/8nyxs7ssr/
[Magisk] m.atif:
Not booting yet on mi A1, reboots after splash screen so no logs are generated.
[Magisk] @ Ayush Garg:
In stable version V14.0 is latest version.... To see latest beta version you need to change update channel from stable to beta...
[Magisk] Horgar:
You have to change to beta channel in magisk manager settings. 14.2 will then appear.
[Magisk] Spartacus500:
[MENTION=4334716]Ayush Garg[/MENTION]

[MENTION=4932363]Horgar[/MENTION]

Simple solution, Thanks ???✔️
[Magisk] Artim_96:
See if the log file mentioned in op is created
[Magisk] Captain_Throwback:
Please provide stock boot.img and patched boot.img produced by Magisk so [MENTION=4470081]topjohnwu[/MENTION] can look into it.
[Magisk] TheKnux:
Would someone have to do that same thing in order to Kickstart TWRP on the Z2 Force?
[Magisk] m.atif:
[/COLOR]

I could not find it sorry.

[MENTION=4470081]topjohnwu[/MENTION]

Here are files,. Also no twrp for mi A1 is present at this time.

Stock Boot

Patched by Magisk 14.2
[Magisk] dardack:
I'm getting Failed to unpack boot image when trying to install to slot b on Pixel XL.
[Magisk] Eng.Raman:
Working well on my zenfone 2 .

Big thanks :good:
[Magisk] dirtyreturn:
Hey XDA,

stupid question I guess...

Does Magisk work on 4.*.*??
[Magisk] Bhagyesh19:
Is there anyone tried this pached image on mi a1 ?
[Magisk] Pkt_Lnt:
[2017.9.6] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+]

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] k0m3n9:
Just tried on my Galaxy J1 Ace Neo (SM-J111F) just to see if the beta manager works via patched boot image (after flashed stock boot & recovery img) unfortunately, it seems manager still can't autodetect Boot Image Location causing error when try to install any modules.. error shows "Zip is not a Magisk Module". If installed via TWRP method it works: Boot Image Location is auto detected & no error when installing any module.

Abit off topic question: Is there a way flashing TWRP or Patched Boot Image via Odin without triggering Binary or System change from Official to Custom?

ps. When installing via patched boot image from Magisk manager (beta) it seems it downloading Magisk 14 & not Magisk 14.1.
[Magisk] npjohnson:
[MENTION=4470081]topjohnwu[/MENTION] Have you looked into LOKI Boot image support for devices that need it? Bootloader locked devices that require specially crafted loading addresses that load shellcode over aboot. They're easily converted back to standard android boot images, dealt with, and then re-LOKI'd.

Link here: https://github.com/djrbliss/loki
[Magisk] Akomack:
I can't get titanium to restore on 14.2, Pixel XL.. Anyone know what might be the issue?
[Magisk] jenslody:
Did you change update channel to beta in the settings of MagiskManager ?
[Magisk] fOmey:
Some more relevant information:

MIX:/ # ls -lh /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
total 0
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 boot -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2017-10-01 09:00 boot_para -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2017-10-01 09:00 expdb -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 flashinfo -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2017-10-01 09:00 frp -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 lk -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 lk2 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 logo -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 md1arm7 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 md1dsp -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 md1img -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 md3img -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 20 2017-10-01 09:00 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2017-10-01 09:00 nvcfg -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2017-10-01 09:00 nvdata -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 nvram -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 2017-10-01 09:00 para -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 proinfo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2017-10-01 09:00 protect1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 protect2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2017-10-01 09:00 recovery -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 sec1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 seccfg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 system -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 tee1 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 tee2 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2017-10-01 09:00 userdata -> /dev/block/mmcblk0p27
[Magisk] EstiR86:
Can someone help me install Viper4Arise I can't seem to install no matter what I'm on Oreo latest secruity patch, with Magisk 14.2 I can install core and ice config but it won't download Viper4Arise.
[Magisk] partridge79:
Latest beta working great had a problem updating thru app (had to download via browser and flash in recovery but all as it should be :good:
[Magisk] tdhite:
Well, you have to admit this is a funny result ( image attached ). I've sent lots of logs on this, no reason to repeat log info, but it is funny to see the thing in such a state. ;)

I'll look into it in code when I get time.

Galaxy S6 for those wondering.
[Magisk] simar404:
Flashed Magisk using flashfire, its just awesome,

Remember to restore stock boot image through magisk manager before u flash Magisk

I am on 14.2 on my Google pixel.

Thanks [MENTION=4470081]topjohnwu[/MENTION]

Really appreciate ur immense work on it :)
[Magisk] cantenna:
thanks, link?
[Magisk] IlD4nX:
Upgraded from stable, using Magisk Manager, with no problem. Works flawlessly as a stable.

I would love to see some more modules in the app, sometimes it's not easy to find them...
[Magisk] Zwhlol-Zniper:
Can't install new version of Magisk manager. Ideas?
[Magisk] Didgeridoohan:
You don't happen to have an unofficially built version of the Manager installed, by any chance?

Anyway... It'd be a lot easier to help if more details were provided.
[Magisk] nogaff:
Sony Xperia Z3 Compact

My device is a Sony Xperia Z3 Compact with unlocked bootloader and stock Marshmallow 23.5.A.1.291.

I'm flashing Magisk v14.2 via BootBridge which results in an "Installation completed!" message in the recovery log. However, Magisk Manager states that Magisk is not installed when I boot back into Android.
[Magisk] nilkanth.marshiwane:
Not working on Xiaomi Mi A1.
[Magisk] r.Ry4N.05:
[MENTION=4470081]topjohnwu[/MENTION], Sir, is it possible to add full-content logging feature in Magisk Manager like in SuperSU? Magisk and Magisk Manager are working fine on my Xiaomi Redmi Note 4 on RR Nougat v5.8.5 (BrateloSlava's build), but I'm missing the full-content logging feature from SuperSU.
[Magisk] Zwhlol-Zniper:
I really don't know what to tell you. As soon as I open the package installer and hit next to install the app, the installer gets stuck and does not install the app.

I have tried rebooting my system to see if I can override this issue but it remains stuck at the "cancel next" screen.

Edit: Never mind. I checked about section and it's shows that it's updated to the latest version.
[Magisk] wiggmpk:
I just wanted to share my experience with upgrading to v14.2(1420)

Google Pixel XL (Google Edition)

Stock Android Oreo 8.0.0 (Sept)

TWRP 3.1.1-0 (Installed Recovery) <-- IE: Not bootable img

Earlier in the thread I had some difficulty updating Magisk Manager to the bundled v5.3.5 I was coming from a (self) compiled v14.0 and updated to v14.1 (flashed from recovery with no issues). I would assume that Magisk Manager remained at v5.3.0 but I had not specifically noted the version number after updating before I had seen that v14.2 was available for testing.

I attempted to flash v14.2 from recovery and everything appeared to finish as expected. Once I booted up, I opened Magisk Manager and it reflected the expected v14.2 of Magisk installed but it still showed Magisk Manager at v5.3.0. So I tried to install the updated version of Magisk Manager manually (several ways). Through Magisk Manager app (by switching to the beta channel) the update would download, attempt to install (after granting unknown source priv) and just fail "App not installed". I unzipped the flashable zip, extracted the Magisk Manager apk and tried to install, same result.

Flashed stock boot.img (both A/B) from fastboot, reflash Magisk from recovery (everything looks good), boot up, Magisk Manager not even install (at all). I also tried (for the sake of trying) using Magisk Uninstaller, then restoring stock boot.img (again), reflashing Magisk from recovery, boot up, Magisk Manager not installed (at all)

At this point I went back to my (self) compiled v14.0 (as I could not find v14.1 again) and installed it from recovery. Rebooted back into recovery and updated to v14.2. So I had Magisk installed (v14.2) and Magisk Manager (still v5.3.0).

What worked for me...

I manually uninstalled Magisk Manager v5.3.0 from inside the Stock ROM, rebooted into recovery and dirty flashed Magisk v14.2 again. Rebooted into ROM (expected no Magisk Manager) and found Magisk Manager v5.3.5. I have no idea why that worked, or what could have stopped it from updating itself. It could be related to my (self) compiled version, who knows.

I hope this helps someone that may be having the same difficulty.
[Magisk] bioshacker001:
14.1 and 14.2 cause the phone to kick to bootloader when trying to boot on oneplus 5, running latest OOS.

EDIT: additional information: Running latest OOS with custom kernel (lightning kernel v9). Installation reports success. Tried restoring stock boot and installing Magisk and kernel again, in either order, same issue. No logs are created indicating boot failure, because boot isn't attempted, indicating that it's seeing the boot image as corrupt.
[Magisk] zagzag99:
I'm using original kernel and it works fine with 14.2.

Perhaps try first with 14 and then jump to 14.2.
[Magisk] bioshacker001:
I've been running 14 up until now. Works fine. 14.1 and 14.2 don't.

EDIT: corrected multipost. App stated post failed.
[Magisk] zagzag99:
Can't think of a difference but kernel. I have 14.2 working fine.
[Magisk] bioshacker001:
I'll stick with 14, then, unless newer versions start working. Smartmax has been a WONDER for battery life.
[Magisk] guest4711:
Android does not allow an update with different keys used for signing the apk. So you have to uninstall your homemade MagiskManager before you can install one made by others and signed with another key...
[Magisk] wiggmpk:
Seems logical and forgive my ignorance, but wouldn't the Magisk Uninstaller take care Magisk Manager apk installed?

If it does not, then I arrived at that conclusion the long way and will write it off as a learning experience.

Either way, thank you for an explanation of the situation I came across.
[Magisk] EstiR86:
Has anyone got Viper4Arise to install on Oreo? I can't get viper to install no matter what I do, tried the buildprop method the Aroma method and nothing. It says it flashed and i reboot but no Viper4Arise app is installed.
[Magisk] Golf c:
Yes, but not with Magisk yet. Just with SuperSU.

https://xdaforums.com/pixel-xl/how-to/guide-how-to-install-arise-pixel-xl-t3677238/post73883462
[Magisk] anandverma458:
I have a vivo 1603 (marshmallow). The installation from twrp fails (says error accessing boot.img partition: permission denied), but I managed to modify the updater-script to read the image from /data/boot.img. But my problem is that after installing magisk, the device doesn't boot up. It leads to a kernel panic. Looking at the kernel logs, I saw something like 'process magisk tainted'. It happens with every version of magisk. Do you know what's going on?
[Magisk] Strephon Alkhalikoi:
How about posting said logs?
[Magisk] Didgeridoohan:
Have you tried recoveryless installation? Installation instructions are found in the release thread.