I'm regular user of Magisk on my Mi5. But it was plagued with the famous issue of losing root after a while.
But while playing around beta ROM, I found that it comes preinstalled with busybox. Somehow felt that's breaking it, so used osmosis's busybox cleaner script from recovery and removed it.
Gave the phone couple of reboots, now Magisk doesn't lose root.
May be you guys can try, make sure you have full flashable ROM zip available in case of any issue or bootloops.
Yup it has, I didn't want to resort to that because I want to keep system unmodified... I'm thinking if it's possible to make use of the magisk busybox to systemlessly replace the inbuilt one...
Sent from my MI 5 using Tapatalk
I haven't seen any issue with removing busybox and i can pass safetynet with Magisk module.
Where you able to take an ota?... With my current setup, I can take ota anytime... V13 is just around the corner now...
Sent from my MI 5 using Tapatalk
I always go for full ROM, handy in case of issues.
chhapil said:
I always go for full ROM, handy in case of issues.
Click to expand...
Click to collapse
Full Rom, Recovery Rom or Fastboot Rom?
Edit: Does it flash via updater app even if the system is modified?
Sent from my MI 5 using Tapatalk
I mean recovery flashable ROM. Yeah the updater app uses recovery flashable.
Full ROM don't check for system modifications
chhapil said:
I mean recovery flashable ROM. Yeah the updater app uses recovery flashable.
Full ROM don't check for system modifications
Click to expand...
Click to collapse
Oh... Okay, thanks for the info... Didn't test that myself because full roms are just too big...
Sent from my MI 5 using Tapatalk
I just tried removing system busybox, the issue still persist after installing modules such as appsystemizer...
Sent from my MI 5 using Tapatalk
teddy0209 said:
I just tried removing system busybox, the issue still persist after installing modules such as appsystemizer...
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
thats issue with the module, for me as well AppSystemizer is breaking the root.
Give it a couple of reboots
Related
Hello fellow Touchpad enthusiasts,
I happened to see TWRP has a version 2.4 available to us - http://goo.im/devs/OpenRecovery/tenderloin
I saw it posted in other device forums, but not ours so thought I'd share the news.
About all I can tell you is it installed without any major problems. Nothing else tested other than boot into it and reboot to CM 10. I just moved ver 2.3 and copy/renamed 2.4 into same directory. Only problem encountered was old ver permissions were messed up so had to mess around before I was able to move the old ver. That and I reset permission on new ver to match - forget what I modeled it after - the other recovery uImage since I have them both installed.
As always ymmv.
Neil
It would be easier for you to install from goo manager, just tap install openrecoveryscript and your done.
Sent from my Nexus 4 using Tapatalk 2
BIGSimon said:
It would be easier for you to install from goo manager, just tap install openrecoveryscript and your done.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Hah - good point - dunno why I didn't do it that way
thx for the reminder for next time I suppose.
Neil
BIGSimon said:
It would be easier for you to install from goo manager, just tap install openrecoveryscript and your done.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Good idea, thanks dawg
I read about incompatibility problems between TWRP 2.4.3.0 and TouchPad.
But does anybody know what about the new twrp-2.4.4.0-tenderloin?
Please fulfill:
TWRP v.________ and ROM ToolBox
CWM v._________ and GooManager
Edit:
Above is false. You should use ...
... TWRP with GooManager and ...
... CWM with ROM ToolBox!
I will stick with CWM. Seems stable enough, it works as it should, and I don't mind to scroll through using my volume rocker.
MerenQue said:
I read about incompatibility problems between TWRP 2.4.3.0 and TouchPad.
But does anybody know what about the new twrp-2.4.4.0-tenderloin?
Please fulfill:
TWRP v.________ and ROM ToolBox
CWM v._________ and GooManager
Click to expand...
Click to collapse
I updated to 2.4.4 but haven't tested yet, but lots of people were having issues on the Nexus 4 on 2.4.3.0 and after the update nobody has any problems. I know the touchpad is a different animal but i bet it works now. No way I'm ever going back to cwm. Twrp has the best setup & all the right features.
Everytime I tried to flash a zip for a bug fix (headphone detection glitch, etc) it would fail in TWRP. Every time. So I went back to CWM. Goomanager is completely unreliable in regards to finding rom updates, etc.
bchampy said:
Everytime I tried to flash a zip for a bug fix (headphone detection glitch, etc) it would fail in TWRP. Every time. So I went back to CWM. Goomanager is completely unreliable in regards to finding rom updates, etc.
Click to expand...
Click to collapse
Are you using the latest version? Twrp is working perfectly for me.
Update:
I take my message back. I backed up, did a factory reset, restored my backup, & everything is there except it twrp didn't restore my app data nor my system settings data.
Update:
I just flashed shumash's new build with success. So flashing in twrp is now working fine for me. Going to have to investigate why my restore didn't fully work on my previous post.
Is anybody else using the latest Twrp?
New twrp 2.5 out. Haven't tested it out yet. But it looks like they fixed the restore issues.
Sent from my GT-P3110 using xda app-developers app
gradular said:
New twrp 2.5 out. Haven't tested it out yet. But it looks like they fixed the restore issues.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Thanks but I going to wait for some feedback after the problems there have been with previous versions and not just on our Roms. I wished they had responded on there thread here after the notifications they were given.
Sent from my Transformer Prime TF201 using Tapatalk 2
gradular said:
New twrp 2.5 out. Haven't tested it out yet. But it looks like they fixed the restore issues.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Nice! Let us know how it goes for you. I had a few issues with 2.4.4 but my last couple backups and restores worked great. Thanks for letting us know!
And it don't work. Its worse. It restored 5 apps out off 250... It booted though. But i also had a cwm backup done right before so its all good.
Sent from my cm_tenderloin using xda app-developers app
So did you have 2.4.4 before & if so did you have success with that?
I did and it had the same issue but I was only missing 20 apps or so
Sent from my GT-P3110 using xda app-developers app
I tried twrp before and not only could I not do good backups but also screwed my tablet to the point I had to resort to this: http://forum.xda-developers.com/showthread.php?t=
Thank goodness for cwm.
http://forum.xda-developers.com/showthread.php?t=1426244
Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Unless you have s-off or have flashed a new kernel, the system partition is right protected, even when you think it isn't. I think that is what is causing your problem.
Why don't you flash a room that already had root/busybix installed?
c2a5nn1o4n said:
Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Click to expand...
Click to collapse
Sent from my HTC6435LVW using Tapatalk 2
c2a5nn1o4n said:
Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Click to expand...
Click to collapse
When first unlocking and rooting my phone, I thought the same thing about busy box. But what you need to do is flash a new kernel first and foremost which will remove write protection.
I'm not really trying to flash a Rom yet personally I was waiting to see if liberty was coming but I guess it wont be coming I'm having a problem with pushing soffbin do I need do fastboot and soffbin in the same folder?
Sent from my HTC6435LVW using Tapatalk 2[/QUOTE]
c2a5nn1o4n said:
I'm not really trying to flash a Rom yet personally I was waiting to see if liberty was coming but I guess it wont be coming I'm having a problem with pushing soffbin do I need do fastboot and soffbin in the same folder?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
[/QUOTE]
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access[/QUOTE]
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?
c2a5nn1o4n said:
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access
Click to expand...
Click to collapse
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?[/QUOTE]
No, again, you need to flash a kernel first so that you have write permissions
c2a5nn1o4n said:
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?
Click to expand...
Click to collapse
Reading your OP and the rest of your comments in this thread, you're all over the place. Things you are doing will not fix your original problem and trying to achieve s-off just because it looks popular and running into difficulties trying to achieve it only adds to problems and confusion. I suggest you step back, slow down and get familiar with terms before you break another phone. While a small portion of the info is EVO 4G specific, you should check these out for general knowledge:
http://androidforums.com/evo-4g-all-things-root/278898-android-partitions-kernels-explained.html
http://androidforums.com/evo-4g-all...ore-information-about-android-partitions.html
Your root is probably sticking in between boots. As we don't have any ROMs that free up the wasted space in the system folder, it's pointless for you to try to delete apps that you don't want installed. You can simply go into Settings\Apps\All and force stop them and then disable. If that doesn't work, you can use Titanium Backup and hit the middle "Backup/Restore" tab. Click on the app you want and Freeze it (this will stop it from running.) If that doesn't float your boat, you can try to uninstall it.
docnok63 said:
Your root is probably sticking in between boots. As we don't have any ROMs that free up the wasted space in the system folder, it's pointless for you to try to delete apps that you don't want installed. You can simply go into Settings\Apps\All and force stop them and then disable. If that doesn't work, you can use Titanium Backup and hit the middle "Backup/Restore" tab. Click on the app you want and Freeze it (this will stop it from running.) If that doesn't float your boat, you can try to uninstall it.
Click to expand...
Click to collapse
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
UrGuardian999 said:
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
Click to expand...
Click to collapse
You're right. I had assumed he had unlocked and flashed an unsecure boot image before attempting to flash su and busybox. Perhaps I did assume too much. I'll refer him to here in that case.
UrGuardian999 said:
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
Click to expand...
Click to collapse
Ok so I have to have busybox? I've downloaded the viper Rom with the boot img I'm downloading cubed 3.1.3 kernal now so I just go into recovery and flash the kernal correct I'm a noon to HTC this is entirely different than by bionic
c2a5nn1o4n said:
Ok so I have to have busybox I've downloaded the viper Rom with the boot img I'm downloading cubed 3.1.3 kernal now so I just go into recovery and flash the kernal correct I'm a noon to HTC this is entirely different than by bionic
Click to expand...
Click to collapse
The Viper Rom has Stock DSB Kernel boot.img zip'd with it. You can flash that rom and flash the Stock DSB modules with it and you'd be good to go
UrGuardian999 said:
The Viper Rom has Stock DSB Kernel boot.img zip'd with it. You can flash that rom and flash the Stock DSB modules with it and you'd be good to go
Click to expand...
Click to collapse
That's actually the opposite of what actually is the case. The modules are packaged with the rom and you have to flash the boot.img manually.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
That's actually the opposite of what actually is the case. The modules are packaged with the rom and you have to flash the boot.img manually.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I downloaded the boot.img and the Rom then went to recovery and only the Rom was there how do I flash the boot img manually
c2a5nn1o4n said:
I downloaded the boot.img and the Rom then went to recovery and only the Rom was there how do I flash the boot img manually
Click to expand...
Click to collapse
Nvr mind I understand but do I fastboot the boot img first or after I flash the Rom
c2a5nn1o4n said:
Nvr mind I understand but do I fastboot the boot img first or after I flash the Rom
Click to expand...
Click to collapse
The order doesn't matter
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
The order doesn't matter
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Also on my other DNA I installed cynogen but not the bootimage and when I would try to reboot I would get messed up lines would that have caused that? If it would my brain has dropped to a new low
If using Cubed 3.1.3 you'll have to reflash the modules though, correct?
UrGuardian999 said:
If using Cubed 3.1.3 you'll have to reflash the modules though
Click to expand...
Click to collapse
Nope still on stock kernal
I'm currently flashing viper as well right now, had to stop and go to work right in the middle of it. My apologies hahah
I have a mtk6572 will installing modules brick my device
Sent from my GT-S5830L using xda app-developers app
no it will not brick your phone but it will do hang or force stop your system ui sometimes
divyamg28 said:
no it will not brick your phone but it will do hang or force stop your system ui sometimes
Click to expand...
Click to collapse
Never had that problem
BenDroid1 said:
I have a mtk6572 will installing modules brick my device
Sent from my GT-S5830L using xda app-developers app
Click to expand...
Click to collapse
keep this on the root of your sd card...
https://www.dropbox.com/s/h0u496vl6vwp79x/Xposed-Disabler-Recovery.zip
havent ran into brick yet but definitely an endless bootloop...flash this zip and it doesnt delete your xposed modules, just switched it off so you can boot
spiral777 said:
keep this on the root of your sd card...
https://www.dropbox.com/s/h0u496vl6vwp79x/Xposed-Disabler-Recovery.zip
havent ran into brick yet but definitely an endless bootloop...flash this zip and it doesnt delete your xposed modules, just switched it off so you can boot
Click to expand...
Click to collapse
The Xposed installer creates that zip on install. So no need to share it. Isn't it device/rom specific too? (it flashes back some original files from before install)
GriffinSauce said:
The Xposed installer creates that zip on install. So no need to share it. Isn't it device/rom specific too? (it flashes back some original files from before install)
Click to expand...
Click to collapse
Never realized that... Thnx
For anyone that thinks it can't brick your phone it can. I had a Note 4 t;mobile, had a custom recovery twrp 2.8.7, had a backup to. I somehow messed it up so bad I couldn't even get to recovery, Odin original rom, recovery, everything even tried baseband/bootloader. Flashed 4 different original roms, tried flashing philz recovery also. Even restored it via Kies3 said it completed but on boot my phone says recovery...booting and then shuts off. It was worth the risk imo.
Please help me ... After I flash the framework from xposed installer i had the problem of the system force stopping how can I fix it without losing my data
How can I flash the uninstaller , I tried by entering the recovery and apply update from my sd card but it does not work can you tell me if there is another way and thanks
I am not responsible for any damage that may occur, you assume all responsibility for what you install on your phone.
This is a custom rom for R1HD, (Zen UI).
This is a rom I ported to my R1HD, I like the rom, thought I would share with community.
Rom is rooted, but doesn't prop per app, if you want prop per app after install go to playstore and install SuperSu https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
The rom works well for me, it's intended for people who want something other than stock rom.
The rom includes gapps, so playstore works correctly. The rom is fast and smooth, nice to look at as well.
You need to have bootloader unlocked, and have twrp recovery.
e1a3216d83e18f99c5f2f5c1b8e415b4 /home/vampirefo/Desktop/R1HD_Roms/zen/R1HD_ZenUi.zip
To install download
https://www.androidfilehost.com/?fid=385035244224382387
place R1HD_ZenUi.zip and sdcard reboot to twrp
factory reset
install R1HD_ZenUi.zip
reboot to system.
this rom will take a while on first boot.
Kernel Source
https://github.com/vampirefo/android_kernel_mediatek_mt6735
Only tested via my twrp.
https://www.androidfilehost.com/?fid=24713784966774807
credits
Lexan
Vampirefo
XDA Developers.
Looks gorgeous vamp. Glad you got all the blob stuff sorted out.
"Updater process ended with ERROR: 7"
Does not flash.
bullet25 said:
"Updater process ended with ERROR: 7"
Does not flash.
Click to expand...
Click to collapse
What recovery you using? I only tested on my twrp recovery.
Sent from my R1 HD using Tapatalk
vampirefo said:
What recovery you using? I only tested on my twrp recovery.
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
TWRP.
bullet25 said:
TWRP.
Click to expand...
Click to collapse
You using my twrp?
Sent from my R1 HD using Tapatalk
vampirefo said:
You using my twrp?
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
No, lopestone's. You don't have a TWRP linked in the OP. Why should there be a difference?
bullet25 said:
No, lopestone's. You don't have a TWRP linked in the OP. Why should there be a difference?
Click to expand...
Click to collapse
I don't use his twrp only tested on my twrp.
Sent from my R1 HD using Tapatalk
vampirefo said:
I don't use his twrp only tested on my twrp.
Sent from my R1 HD using Tapatalk
Click to expand...
Click to collapse
Okay, can you please link to your TWRP?
bullet25 said:
Okay, can you please link to your TWRP?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24713784966774807
Sent from my R1 HD using Tapatalk
Can this port be used as base for others?
Same error even with your TWRP.
bullet25 said:
Same error even with your TWRP.
Click to expand...
Click to collapse
Works perfectly for me.
Sent from my BLU ENERGY X PLUS using Tapatalk
got it to install with lopestorms recovery. needed to mount the /system as writeable first
but it still had an error message during the flash. I t didnt stop the install. It said failed to mount /system (resource busy) then it continued anyway.
mrmazak said:
got it to install with lopestorms recovery. needed to mount the /system as writeable first
but it still had an error message during the flash. I t didnt stop the install. It said failed to mount /system (resource busy) then it continued anyway.
Click to expand...
Click to collapse
Well yes, cause you shouldn't be mounting system at all, mounting system causes the busy error.
You should just wipe data and cache, not mess with system.
That explains why you all have problems, system should never be touched.
All you should be doing is click wipe, slide one time this is factory reset. Do nothing else then click back and install ROM.
Sent from my BLU ENERGY X PLUS using Tapatalk
vampirefo said:
Well yes, cause you shouldn't be mounting system at all, mounting system causes the busy error.
You should just wipe data and cache, not mess with system.
That explains why you all have problems, system should never be touched.
All you should be doing is click wipe, slide one time this is factory reset. Do nothing else then click back and install ROM.
Sent from my BLU ENERGY X PLUS using Tapatalk
Click to expand...
Click to collapse
iknow system being mounted cause the busy message, but recovery was set with system not writeable before and that caused error 7
to get past error 7 needed to take check mark off "mount system read-only"
mrmazak said:
iknow system being mounted cause the busy message, but recovery was set with system not writeable before and that caused error 7
to get past error 7 needed to take check mark off "mount system read-only"
Click to expand...
Click to collapse
Recovery should never be set ro on system.
Anyway you have it figured out.
Sent from my BLU ENERGY X PLUS using Tapatalk
Flashed it and it works sdly oukitel 10000 does not have a Nougat or a cm13 from what i can see or even an MIUI 8(that would of been a sweet rom to this devices)
PS Also avoid using xposed , some xposed modules will crash the system.ui thus forces you to have to boot back to rec. to start over with the rom. Just a heads-up.(specially for Android N-Ify xposed module lovers like me)....but version 615 worked without crashing the systemUI but bugs in icons(quicksettings) some work some crashes the system but it bring you back to the lockscreen without crashing the hole thing. In other words best to avoid xposed with this rom.
Even though we can't get source compiling to work, it's good to see some sort of ROM for this thing anyway. Good job vamp! Downloading now, can't wait to flash it.
EDIT: Hey would you look at that, FM works!!!
EDIT 2: After fairly extensive use, I've found that both LTE and video recording (with the built in app anyway) don't work. I had an issue with Assistive Touch (I think it was called that) repeatedly crashing, but that can be solved by getting a root uninstaller and outright uninstalling it.
jasonmerc said:
EDIT: Hey would you look at that, FM works!!!
Click to expand...
Click to collapse
You mean like FM radio? If so, then I will have to switch: ).
I'll ask here. Has any V30 owner able to successfully flash magisk 19.1 or the newer 19.2?
I flashed both but can't get past the V30 logo.
BROKEN1981 said:
I'll ask here. Has any V30 owner able to successfully flash magisk 19.1 or the newer 19.2?
I flashed both but can't get past the V30 logo.
Click to expand...
Click to collapse
Which rom are you using?
I've had no issues with them.
Same here. No problems installing for me.
tech_infinity said:
Which rom are you using?
I've had no issues with them.
Click to expand...
Click to collapse
Odd, I'm using stock. I even flashed the uninstaller, rebooted that brought me to fastboot, then selected restart, booted into TWRP and tried again. Since it seems it works for the V30, I'll start a fresh flash and just restore data if I can get Magisk to update.
Sent from my LG-H932 using XDA Labs
Thanks for verifying that Magisk works. I'm updated with no issues.
Thanks guys!
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Thanks for verifying that Magisk works. I'm updated with no issues.
Thanks guys!
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
Pay it forward, man. Finish the thread by telling us how you overcame the problem!
ldeveraux said:
Pay it forward, man. Finish the thread by telling us how you overcame the problem!
Click to expand...
Click to collapse
I clean flashed my ROM and restored my stuff via titanium backup.
Sent from my LG-H932 using XDA Labs
no issue with magisk so far, clean flash is worth trying. or try install the older one then update it within magisk app
immns said:
no issue with magisk so far, clean flash is worth trying. or try install the older one then update it within magisk app
Click to expand...
Click to collapse
Exactly.
For posterity purposes; I had trouble flashing newer versions of Magisk (newer than 18.1). But... it turns out the problems could have been
resolved by installing the Magisk manager apk, the same way you would install any apk.
I haven't gone back and done re-testing or anything, like most of us, I just wanted to get something to work, period. But along the way of this process, the flashing of Magisk later versions didn't show up after booting the phone, even though 'success' was indicated in TWRP.
But installing the Manager apk, then rebooting, it would show up, sometimes twice. Then reboot again, then only one Magisk app with both Magisk and Manager in it...
But as immns says, you can definitely just start with flashing 18.x, and then upgrade both within the application and that will work, I've done it that way also.
Cheers