yashsingh1/xdaforums huggingface dataset:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Chrisy8s:
No

---------- Post added at 04:24 AM ---------- Previous post was at 03:28 AM ----------

Thanks to [MENTION=3659125]joemossjr[/MENTION] for fixing that problem! If it happens to you, remove the app via an app Remover and reinstall via play store.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Bestplayer55:
Whats kind of spell you put on this [MENTION=3659125]joemossjr[/MENTION]?

This is just amazing ??
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
TWRP REV 3.1

Changelog:

reverted to working 4.4.50 kernel due to bootloops

everything else remains

TWRP 3.1

TWRP 3.1 Flashable
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Chrisy8s:
:cyclops:

Gsam and native monitor provide very different numbers here... Next post with SS
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Chrisy8s:
SS
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Chrisy8s:
Ss2
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
if data keeps getting encrypted after formatting....

If your data partition keeps getting encrypted after TWRP formatting (single command in TWRP's terminal):

https://xdaforums.com/showpost.php?p=74540731&postcount=21
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
if you are interested in swappin' slots, here is the solution

For some reason, the TWRP a/b switch wasn't currently working, but that has happened in other a/b phones as well. Here is the solution:

https://xdaforums.com/showpost.php?p=74543389&postcount=10
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
It does work you have to remount the partitions and you can check if you go to terminal and type in df
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
But whenever I switch in TWRP and reboot, fastboot throws an error message? Merely getting TWRP to say a or b doesn't mean anything until you try to reboot.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
Bootloader truly controls which partition is booted. Same on pixel and essential phone. Think of it as a hard lock that keeps you from breaking your phone lol
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] enetec:
New official betas for Pixel 2/2 XL has been released.

They claim improvements on encryption management and other known issues...

Installation is still same way: first setup by booting-only TWRP image and zip (with TWRP) to be flashed. Updates directly by zip to be flashed.

(You already know this is the best solution IMHO... ;) )

Interesting tips for us could be in sources...
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
this is one line that we could try adding for a fastboot boot to TWRP variant

[MENTION=3659125]joemossjr[/MENTION] , this is one line that we could try adding to BoardConfig.mk for a fastboot boot to TWRP variant:

BOARD_USES_RECOVERY_AS_BOOT := true

-------

reference:

https://github.com/TeamWin/android_device_google_wahoo/blob/android-8.0/BoardConfig.mk
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
already added in my local repository that i have

/home/joemossjr/android/omni/out/host/linux-x86/bin/checkpolicy: writing binary representation (version 30) to /home/joemossjr/android/omni/out/target/product/nash/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery.tmp

[100% 6291/6291] Target boot image fro.../omni/out/target/product/nash/boot.img

FAILED: /bin/bash -c "/home/joemossjr/android/omni/out/host/linux-x86/bin/mkbootimg --kernel /home/joemossjr/android/omni/out/target/product/nash/kernel --ramdisk /home/joemossjr/android/omni/out/target/product/nash/ramdisk-recovery.img --cmdline "console=ttyMSM0,115200,n8 androidboot.console=ttyMSM0 earlycon=msm_serial_dm,0xc1b0000 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 sched_enable_hmp=1 sched_enable_power_aware=1 service_locator.enable=1 swiotlb=2048 androidboot.configfs=true androidboot.usbcontroller=a800000.dwc3 androidboot.hab.csv=0 androidboot.hab.product=nash androidboot.hab.cid=21 buildvariant=user enforcing=0 androidboot.selinux=permissive buildvariant=userdebug" --base 0x80000000 --pagesize 4096 --os_version 7.1.2 --os_patch_level 2017-10-05 --kernel_offset 0x00008000 --ramdisk_offset 0x01000000 --tags_offset 0x00000100 --output /home/joemossjr/android/omni/out/target/product/nash/boot.img --id > /home/joemossjr/android/omni/out/target/product/nash/recovery.id"

usage: mkbootimg [-h] --kernel KERNEL [--ramdisk RAMDISK] [--second SECOND]

[--cmdline CMDLINE] [--base BASE]

[--kernel_offset KERNEL_OFFSET]

[--ramdisk_offset RAMDISK_OFFSET]

[--second_offset SECOND_OFFSET] [--os_version OS_VERSION]

[--os_patch_level OS_PATCH_LEVEL] [--tags_offset TAGS_OFFSET]

[--board BOARD] [--pagesize {2048,4096,8192,16384}] [--id]

[--dt DT] -o OUTPUT

mkbootimg: error: argument --ramdisk: can't open '/home/joemossjr/android/omni/out/target/product/nash/ramdisk-recovery.img': [Errno 2] No such file or directory: '/home/joemossjr/android/omni/out/target/product/nash/ramdisk-recovery.img'

ninja: build stopped: subcommand failed.

build/core/ninja.mk:157: recipe for target 'ninja_wrapper' failed

make: *** [ninja_wrapper] Error 1

#### make failed to build some targets (07:10 (mm:ss)) ####

joemossjr@joemossjr-Aspire-VX5-591G:~/android/omni$

and i get this error lol
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
I would ask @Dees_Troy

I would ask [MENTION=912474]Dees_Troy[/MENTION] . I'm not sure why it doesn't play nice. :)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
this is a working modified TWRP installer for our phone (was Pixel 2 XL)

Your kernel stays the same. The working modified TWRP installer for our phone (was Pixel 2 XL) is attached. You have to install Magisk zip (or SuperSU 2.82 beta SR5) afterward or it won't boot normally (only to TWRP) until you flash Magisk. All credit for TWRP goes to [MENTION=3659125]joemossjr[/MENTION] .

-------

Also, if you are interested in using a Magisk daily snapshot, 24NOV2017 is attached, and copy this URL to the custom update URL in settings:

[B]https://raw.githubusercontent.com/kantjer/MagiskFiles/master/updates/kantjer.json[/B]

(I got the attached and that update URL from [MENTION=3306843]kantjer[/MENTION] post https://xdaforums.com/showpost.php?p=74577534&postcount=1346)

I think you may have to uninstall your old Magisk manager before installing this one and adding the update URL. The Magisk zip is flashable in TWRP, and no Magisk uninstall is needed before the zip. Daily snapshots are

unstable

but clearly the most current possible Magisk zip & Magisk Manager apk. :)

If the snapshot updater doesn't download properly tomorrow, you could manually download from web-browser; the files can be manually downloaded from this address (tap view code if mobile formatted, then switch to desktop site to access download button):

https://github.com/kantjer/MagiskFiles

Magisk at XDA (stable, beta, etc.): https://xdaforums.com/apps/magisk
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] byt3b0mb:
updated to august tmo flash all - reflashed twrp and i cant mount or erase oem partition anymore. also when i tried to install titanium backup from zip it wont install no matter how many times i tried. am i doing something wrong? these things did not happen with the june build.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
That's odd what slot are you on
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] byt3b0mb:
i was on slot A, something to note was that i did pull down another update after flashing the august flashall. Also- i kept losing root in between reboots.

I just flashed back to the august flashall and im going to twrp and root again and see what happens.

is it possible to flashall and omit the OEM partition? I tried fastboot erase oem and it said denied.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
You can erase it in TWRP if that's doesn't work go to file manager and erase the folder form there
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] byt3b0mb:
it seems to have let me erase the files, but i still have t-mobile app and lookout, which seems odd.

something is going on with my device or what im doing, because if i flashall the august build, then flash your 3.1 twrp to boot, i can reboot in to recover no problem, if i flash magisk (newest) and boot up, i get tons of force closes.

do you plan on making an NCPRom with August Base?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
We found the october base works for T-Mobile phones just fine. We are working out the kinks and getting it staged. Just give us some time to work out bugs.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] byt3b0mb:
awesome. looking forward to it. i will keep tinkering with what i have now.

ok here is where i am stuck now. Flashed august flashall - formatted data. let it boot. enabled developer options, reboot to bootloader, flash magisk-boot (august) - reboot, have root. reboot recovery to flash titaniumbackup - goes to stock recovery. reboot to bootloader, flash TWRP 3.1 IMG as boot - lose root.

what am i doing wrong? i just want to be on august base with root - dont care about safety net or encryption at this point (although twrp reading encrypted file system would rock).
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
1-4 all in TWRP, all at same time (so-to-speak)

(1 in TWRP) Format again, if necessary, then use this command in TWRP terminal if data keeps getting encrypted after formatting:

https://xdaforums.com/showpost.php?p=74540731&postcount=21

(2 in TWRP) This is a working modified TWRP installer for our phone (was Pixel 2 XL) (TWRP by [MENTION=3659125]joemossjr[/MENTION]):

https://xdaforums.com/showpost.php?p=74594179&postcount=284

(3 in TWRP) Pantheon (kernel by [MENTION=4604067]Uzephi[/MENTION]):

https://xdaforums.com/showpost.php?p=74449397&postcount=1

(4 in TWRP) Re-flash latest Magisk in TWRP.

Reboot, then re-install latest Magisk Manager apk after the successful reboot.

Also, try restoring backed up Titanium apps without data in future to see if that helps.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Flashing TWRP boot image will make you lose root... flashing the installer might as well, haven't tried it personally. need to reroot after TWRP install, also after kernel install.... might as well do root last, lol.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Chrisy8s:
I had some similar problems and used that flash all a billion times.... What helped me after flashall was wiping data then:

1. installing twrp rev2 first, flashing magisk, reboot. 2. Then upgrading to rev3 twrp, flashing magisk, reboot.

3. Then flash pantheon, magisk, reboot. Hope that helps.

All this probably wasn't necessary, but it was the method that finally got me working properly...

The data wipe ditches encryption.. never got everything working right with encryption. Probably close to, if not exact to instructions.. I'm just too lazy to look tonight.

I should add I'm not using stock ROM anymore though but it does work with stock ROM as well.

---------- Post added at 03:41 AM ---------- Previous post was at 03:26 AM ----------

Anyone try the new Magisk update? Work? 5.4.2
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] enetec:
Since of what are my experiences, this should works fine with SuperSU too (which I continue to prefer... :silly:).

I've not tested first hand, BUT to stay on "safe side" this would be my method too... ;)

P.S.: could you check if after all this your /data partition is in f2fs or in ext4 format?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] byt3b0mb:
Here is my current setup. Used the retail zip flashed everything but bootloader, radio and oem. Then flashed twrp and SuperSU.

Encrypted but rooted and with twrp.

Love this phone but looking forward to my op5t. Much easier to hack on.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
There's currently not much point to having our TWRP if your data partition is still encrypted, because you can't modify it correctly. I would format in TWRP (i.e., the typing 'yes' way), then mount system in TWRP, then type only one line in TWRP terminal:

sed -i 's/fileencryption/encryptable/g' /system/fstab.qcom
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] byt3b0mb:
What does that command do?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
sed -i 's/fileencryption/encryptable/g' /system/fstab.qcom

That one line command (ignore word wrap, if wrapped; it's only one line) replaces one word with another. The fileencryption word is changed to encryptable in that one file. Just do the 'yes' format in TWRP, mount system in TWRP, and type that command in TWRP terminal. No more force encryption due to that particular file, but it will still boot if encrypted. Once you do these steps, you will be able to fully use our current TWRP and you will save yourself from lots of potential issues.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
It's ext4 always kernel doesn't support f2fs fully
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] enetec:
Uhm... so my "commented" (#) line on fstab.qcom reporting f2fs could be this way since stock? :confused:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
Yeah it's always be this way even if you enable it it won't boot
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
how to switch to f2fs data; zip attached

I think it is from stock for some reason. As far as I know, our stock Linux kernel supports f2fs.

Here's what to do if you want to guaranteed switch to f2fs:

--Backup data only to external drive in TWRP (does not copy internal simulated sd card, so copy any important files to external drive too).

--Flash f2fs_switch_noencrypt.zip (attached)

--Change data filesystem to f2fs in TWRP (in wipe/advanced/change repair, etc., section).

--Flash twrp-f2fs-data-z2force-installer-nash-3.2.0.zip (attached; TWRP by [MENTION=3659125]joemossjr[/MENTION] )

--Flash latest beta Magisk (attached; or SuperSU 2.82 beta SR5)

--Reboot to TWRP recovery again (choose reboot recovery option)

--Restore your backed up data only.

--Reboot system.

--Install latest Magisk manager apk (if not already installed; attached)

Please see attached files and screenshots. If you ever want to go back to ext4, just repeat the same process but choose ext4 and substitute the attached RemoveEncryption_ext4.zip (ext4 zip from [MENTION=3659125]joemossjr[/MENTION] ) and the attached ext4 TWRP (TWRP by [MENTION=3659125]joemossjr[/MENTION] ). Good luck! :)

(Note: I fixed trivial f2fs flag error and re-uploaded both f2fs zips, but only cosmetic; it works either way.)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
Just an FYI about switching to f2fs in our TWRP:

Samsung invented f2fs. I just looked at my other phone, a Galaxy S8+ (i.e., swap sim every couple days; also Snapdragon 835), via Android terminal command:

cat /proc/mounts

and my S8+ userdata is ext4.

Ask yourself: if f2fs is faster and Samsung invented it, why doesn't Samsung use it for the S8+? I think the answer is compatibility and reliability. :)

https://medium.com/thecyberfibre/f2fs-versus-ext4-our-take-on-the-ongoing-battle-c0324f46d040
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
TWRP F2FS SUCCESS! The results are here. f2fs vs. ext4 for userdata on Z2 force

https://xdaforums.com/showpost.php?p=74627577&postcount=303

(You probably don't need to click link for method, because should be only 2 posts back.)

I am using f2fs for userdata on our phone right now!

Using the instructions I wrote in the link, you can successfully use f2fs for userdata on the Moto Z2 Force. Screenshots attached proving now mounted f2fs (i.e., output from the Android terminal command: cat /proc/mounts) for userdata and two benchmarks: the first benchmark is ext4 userdata, and the second benchmark is f2fs. :)

(Note: I fixed trivial f2fs flag error and re-uploaded both f2fs zips, but only cosmetic; it works either way.)

You will see that f2fs does slightly better on every measurement except sequential read; the latter is insignificant, but database delete is more significant in favor of f2fs (~17.3% improvement).

Sequential Read: ext4 +0.9%

Sequential Write: f2fs +2.0%

Random Read: f2fs +1.7%

Random Write: f2fs +6.1%

SQLite Insert: f2fs +13.0%

SQLite Update: f2fs +1.6%

SQLite Delete: f2fs +17.3%
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
Nice! During initial testing when we were testing we were using the stock kernel. Have you tried it on that. What kernel are you curently using. And by the way the recovery flashes arnt necessary i flashed the f2fs fstab and formatted data and rebooted and it worked fine. (i dont care about my data lol)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
Latest TWRP and just Pantheon 4.4.100 v.1.2 (non-OC). I'm looking forward to EAS (i.e., since EAS 1.4 has already been merged into AOSP 4.4), and would probably do OC then. :)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
[MENTION=3659125]joemossjr[/MENTION] , this is the only file very, very slightly changed in the f2fs userdata TWRP: recovery.fstab (attached; from ramdisk's /etc/).

(TWRP by [MENTION=3659125]joemossjr[/MENTION] )

[B][COLOR="black"]/data	f2fs /dev/block/bootdevice/by-name/userdata[/COLOR][/B]

As for the modified Pixel 2 XL installer, if desired, you could delete our current ramdisk.cpio, and put in zip's base directory a future compiled (then extracted) ramdisk.cpio, but re-named to ramdisk-twrp.cpio (un-gzipped, so no .gz). It's nice it lets us keep our same kernel. Then, flashing latest Magisk (or SuperSU 2.82 beta SR5) allows it to reboot normally.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] enetec:
Very interesting tests guys...;)

Speed results are about what expected... anyway this device is so fast that I think they are not so rilevant for average user.

Anyway I'm really curious about reasons because Motorola decided to opt for ext4 (probably at last, since of the commented line...). Reliability? :confused:

I'm quite sure that this with OC & optimized kernel and f2fs is the fu**ing faster Android device on market at moment! :p
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Well.... Our CPU freq file is the same as the Pixel 2 and OP5, so they probably tie in a sense, since the OC I got was merged from the Pixel 2 as per my kernel source commit.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
F2fs and your kernel lol
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
What's the geek bench score? Antutu doesn't really test the CPU as well as geek bench, just the GPU and memory. With OC, not much difference with Antutu, but Geek Bench showed the expected results and increase in UX that was experienced.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] enetec:
I agree. Antutu is nowdays "a global reference" and it is interesting to be compared, but Geekbench is more sharp in its testing and better to compare steps during development...
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] D<3'SJ2427:
Hi and thank you everybody for the work and testing ya'll have put in for this phone, very much appreciated. I've unlocked the bootloader and trying to flash this TWRP through adb and I get a invalid partition name error. The TWRP after downloading has a specific name, should i keep it like that? I've renamed in the past to just "twrp" for other devices. I'm not the sharpest tac when it come"s to adb and commands. A little help would well.......be helpful:o Thank you!

Stock Moto z2 force/unlocked bootloader

win7 using Adb Min from xda
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
fastboot flash boot (name_of_file).img

Our recovery is in the boot partition unlike other phones

Edit: be sure you're in bootloader. If in system type the below command to get there.

adb reboot bootloader
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] D<3'SJ2427:
Thank you! that was my problem. Now I wish that was my only issue. I have twrp installed (yay) and of course flashed magisk right after installing twrp. Booted the device and upon going to app drawer notice Magisk manager wasnt there. So back to twrp a few times to try and flash again, format data, nothing. I'm absolutely lost with this phone and A\B partitioning. I knew i should have read more before venturing further dammit. I'm bootlooping, can"t get past setup due to multiple fc's and you guys will love this....No nandroid backup:eek: fml.....
[MENTION=3659125]joemossjr[/MENTION] was there mention of a ROM of yours i could flash before i do more damage. Thank you
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
You need to "format data" and flash magisk 14.5 beta
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
If "format data" option doesn't work, try the decrypt zip posted a couple pages back and try again. If that failed, flash all back to stock.

Edit:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] D<3'SJ2427:
THANK YOU SO MUCH! You and [MENTION=3659125]joemossjr[/MENTION] for doing those flash all's. Man are those some life savers:highfive:

Back to the drawing board!

If I may ask to check these steps:

boot to twrp/swipe to allow modifications

select wipe>format data>yes

transfer magisk 14.5 beta and flash

reboot using slot b?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
When you flash all, you go back to slot A. If you wait for the update, then you go to slot B again. I highly suggest flashing the unencryptor zip after magisk before rebooting.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] D<3'SJ2427:
Hello again! These were my steps after having done the flash all:

re flashed twrp>successful

wipe>format data>yes

transfer magisk/unencrypt zip

flash both those and reboot...no magisk in app drawer

I boot to twrp and just flash the 2 zips and whoo hoo magisk is there but I have FC'S in stock apps (messages, playstore ect) Where did I go wrong or what should i be doing I'm not?

I finally felt i was heading in the right direction too darn it! For now i just went back to stock, frustration is setting in. Thank you all for the help, I'll be back after some Wheaties:victory:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
Carrier? What flash all?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] D<3'SJ2427:
T-mobile

I used this one http://https://xdaforums.com/z2-force/how-to/to-stock-roms-t3672859 Thank you for putting it together
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] joemossjr:
Ok so the bug with magisk has to do with with magisk being weird on the latest update and which unencrypt file did you flash
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] D<3'SJ2427:
I used the one located here https://drive.google.com/file/d/1Cr-7SiSiHpUDM9HYpyeXVsPHEB9Z9wym/view?usp=drivesdk

Posted in a reply a page or half page back. Thank you for the info about Magisk. Going to settings and checking security shows as unencrypted or shows the option I can Encrypt. That was where I had left off before starting over again.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jhofseth:
Magisk manager, a separate file inside the zip and located in the zip's common folder, is an apk and can be installed like normal apks; it is bundled with the beta. https://xdaforums.com/apps/magisk

I attached the Magisk manager apk that was inside latest beta Magisk zip, as well as the latest Magisk beta zip. Sometimes uninstalling then re-installing apks can help.