Related
Hello guys,
Whilst searching on google for some kernel flashing methods I saw an app named flashify...
Since I can't use flashtool on my pc for flashing stuff, luckily got my bootloader unlocked via fastboot and half root turned into full root...
Well, cutting the crap...
Test this app... Flashify on both locked and unlocked bootloaders....
Get it from here -
http://forum.xda-developers.com/showthread.php?t=2349847
Bugs--
Locked bootloaders--
None yet
Unlocked Bootloaders --
Recovery image can't be flashed...
Warning -- Half/Full root is needed in order to use this app..
Test and report back.. I will contact the developer to add support for our device too... So people without pc can have custom kernels with recoveries..
Thanks.
kaustubh.rockstar said:
Hello guys,
Whilst searching on google for some kernel flashing methods I saw an app named flashify...
Since I can't use flashtool on my pc for flashing stuff, luckily got my bootloader unlocked via fastboot and half root turned into full root...
Well, cutting the crap...
Test this app... Flashify on both locked and unlocked bootloaders....
Get it from here -
http://forum.xda-developers.com/showthread.php?t=2349847
Bugs--
Locked bootloaders--
None yet
Unlocked Bootloaders --
Recovery image can't be flashed...
Warning -- Half/Full root is needed in order to use this app..
Test and report back.. I will contact the developer to add support for our device too... So people without pc can have custom kernels with recoveries..
Thanks.
Click to expand...
Click to collapse
"Your device didn't pass the compatibility test, therefore it isn't fully supported yet. Flashing boot/recovery will not work. I'll work to try to support as many devices as possible."
kaustubh.rockstar said:
Hello guys,
Whilst searching on google for some kernel flashing methods I saw an app named flashify...
Since I can't use flashtool on my pc for flashing stuff, luckily got my bootloader unlocked via fastboot and half root turned into full root...
Well, cutting the crap...
Test this app... Flashify on both locked and unlocked bootloaders....
Get it from here -
http://forum.xda-developers.com/showthread.php?t=2349847
Bugs--
Locked bootloaders--
None yet
Unlocked Bootloaders --
Recovery image can't be flashed...
Warning -- Half/Full root is needed in order to use this app..
Test and report back.. I will contact the developer to add support for our device too... So people without pc can have custom kernels with recoveries..
Thanks.
Click to expand...
Click to collapse
Hey people I thinks this app is good but the negative you need custom recovery to flash zip files "then what's the point", I suggest you use this app Flash Gordon you don't need a custom recovery to flash zip file meaning those with locked bl can use this app to flash mode etc.
In the current release of Flashify and with my XM dual (locked bootloader) I can only backup the Kernel... none of the flashing options work, gives the "Your device didn't pass the compatibility test, therefore it isn't fully supported yet. Flashing boot/recovery will not work. I'll work to try to support as many devices as possible." message =/
Deleted
YouColdYet said:
Hi. I've been searching for this for quite some time now haven't get any result so I'm wondering if I can be helped by rooting my m8 .. The os is Marshmallow ... Don't wanna brick my phone so its best i asked before i do anything risky
Help!!
Click to expand...
Click to collapse
Hi. you have TWRP?
YouColdYet said:
Hi. I've been searching for this for quite some time now haven't get any result
Click to expand...
Click to collapse
The question was just recently asked and answered (answer applies whether you are GPE or Sense, you haven't specified): http://forum.xda-developers.com/htc-one-m8/help/root-htc-one-m8-gpe-t3285356
So briefly:
1) Unlock the bootloader by HTCDev.com
2) Install TWRP 2.8.7 by fastboot
3) Flash SuperSU 2.64 or later in TWRP
redpoint73 said:
The question was just recently asked and answered (answer applies whether you are GPE or Sense, you haven't specified): http://forum.xda-developers.com/htc-one-m8/help/root-htc-one-m8-gpe-t3285356
So briefly:
1) Unlock the bootloader by HTCDev.com
2) Install TWRP 2.8.7 by fastboot
3) Flash SuperSU 2.64 or later in TWRP
Click to expand...
Click to collapse
Okay thanks, I'm using sense forgot to mention that
Hi. I was s-on, rooted with twrp 2.8.7 on lollipop. went stock, bootloader and rom, updated to MM, wanna do root again. I remember I unlocked bootloader before - was it relocked in the process of going stock? How to check if it is unlocked? other steps 2 and 3 are quite clear by redpoint73
EDIT: yes the unlock was still intact. Managed to get twrp, made backup (thanks for advises), and when it prompted to install or not root, i decided yes... Stuck on boot logo, managed to restore. Now searching for 2.66 supersu and will try to root via twrp again. my m8 is not GPE. fingers crossed
edvinb said:
I unlocked bootloader before - was it relocked in the process of going stock? How to check if it is unlocked?
Click to expand...
Click to collapse
The only way for it to become locked/relocked again, is if you do so manually.
The bootloader screen will tell you the bootloader status: LOCKED, RELOCKED or UNLOCKED
edvinb said:
EDIT: yes the unlock was still intact. Managed to get twrp, made backup (thanks for advises), and when it prompted to install or not root, i decided yes... Stuck on boot logo, managed to restore.
Click to expand...
Click to collapse
The automatic root in TWRP isn't updated for MM, therefore doesn't work, and as you see results in no-boot.
edvinb said:
Now searching for 2.66 supersu and will try to root via twrp again.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
edvinb said:
Hi. I was s-on, rooted with twrp 2.8.7 on lollipop. went stock, bootloader and rom, updated to MM, wanna do root again. I remember I unlocked bootloader before - was it relocked in the process of going stock? How to check if it is unlocked? other steps 2 and 3 are quite clear by redpoint73
EDIT: yes the unlock was still intact. Managed to get twrp, made backup (thanks for advises), and when it prompted to install or not root, i decided yes... Stuck on boot logo, managed to restore. Now searching for 2.66 supersu and will try to root via twrp again. my m8 is not GPE. fingers crossed
Click to expand...
Click to collapse
You rooted your M8 succesfully? @edvinb
I wanna root on marshmallow , i wasnt rooted at all, so i just unblock bootloader, install twrp then flash that supersu 2.67 ?
Is this the correct procedure ? @redpoint73
Stock, S ON, locked bootloader, M8y 2.5 ghz asian version
yes, proceed, I successfully rooted my htc
So, after twrp you installed the newest supersu from redpoint link? @edvinb
Sent from my HTC One_M8 using Tapatalk
Callliope said:
So, after twrp you installed the newest supersu from redpoint link?
Click to expand...
Click to collapse
SuperSU 2.65 is marked as "stable", although any version after that are probably fine, as well.
http://forum.xda-developers.com/apps/supersu
Alternately, if you installed TWRP 3.0.0.0 or later, the built-in root will probably now work correctly on MM. This was not the case at the time of my last post (Post #6 above) where TWRP 2.8.7.0 was the latest version (and not updated to properly root MM).
true, it didn't boot when i tried supersu through the old twrp.
Is there any way available (mode or something) to enable native wifi tethering / wifi tethering on verizon htc one m8 (marshmallow)? I'm using non verizon gsm sim card, unlocked bootloader, s-off, rooted.
mamun.srdr said:
Is there any way available (mode or something) to enable native wifi tethering / wifi tethering on verizon htc one m8 (marshmallow)? I'm using non verizon gsm sim card, unlocked bootloader, s-off, rooted.
Click to expand...
Click to collapse
I answered you in your other post. Please don't post the same question in multiple places.
redpoint73 said:
I answered you in your other post. Please don't post the same question in multiple places.
Click to expand...
Click to collapse
Thanks. I was kind of desperate
Hi. I've been looking for a dummy's guide to rooting my m8. I'm in New Zealand so I'm guessing I have the international version, though I don't actually know how to check. I'm running marshmallow and sense 7. Redpoint73 Can you tell me if the brief instructions from your post on the first page will gain root for me without bricking my phone? I want to be able to install some of the flashy roms from the android development section. Thanks
bryce-bubbles said:
I've been looking for a dummy's guide to rooting my m8. I'm in New Zealand so I'm guessing I have the international version, though I don't actually know how to check. I'm running marshmallow and sense 7. Redpoint73 Can you tell me if the brief instructions from your post on the first page will gain root for me without bricking my phone? I want to be able to install some of the flashy roms from the android development section.
Click to expand...
Click to collapse
You won't brick the phone rooting or flashing a ROM. At least, the chances of bricking are so slim, its probably less likely than bricking from an official OTA update on a stock device. If you start messing with s-off mods, that is a different story. But s-on (and that is all you probably need) its nearly impossible to brick.
Yes, the process I described briefly in Post #3 above will work for just about any M8 variant, with the exception of Verizon.
Vomer's guide is pretty good, although not updated: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
You only need to follow the first parts of the guide that pertain to unlocking the bootloader, and installing custom recovery. And for those parts, I think the only thing that is outdated, is that (depending on your current firmware version) you should probably use a more recent version TWRP: https://dl.twrp.me/m8/
You actually don't need to root to install a custom ROM. Once you have custom recovery TWRP installed, just put the desired ROM on the phone, do a default wipe in TWRP, and flash the ROM.
For more specific help, and determining what M8 version you have: figure out how to use fastboot, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If all this is new to you (and it sounds like it is) my advice is to start reading the available guides and starter threads. I don't personally like "dummy's guide" approaches. Reading and understanding fully, before doing anything, is a much better idea. You actually learn something that way, as opposed to "step-by-step" guides which do the opposite (you accomplish the task, but probably don't really remember or understand what you even did).
And if you have specific questions, just come back here; and we'll be happy to try and help.
redpoint73 said:
You won't brick the phone rooting or flashing a ROM. At least, the chances of bricking are so slim, its probably less likely than bricking from an official OTA update on a stock device. If you start messing with s-off mods, that is a different story. But s-on (and that is all you probably need) its nearly impossible to brick.
Yes, the process I described briefly in Post #3 above will work for just about any M8 variant, with the exception of Verizon.
Vomer's guide is pretty good, although not updated: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
You only need to follow the first parts of the guide that pertain to unlocking the bootloader, and installing custom recovery. And for those parts, I think the only thing that is outdated, is that (depending on your current firmware version) you should probably use a more recent version TWRP: https://dl.twrp.me/m8/
You actually don't need to root to install a custom ROM. Once you have custom recovery TWRP installed, just put the desired ROM on the phone, do a default wipe in TWRP, and flash the ROM.
For more specific help, and determining what M8 version you have: figure out how to use fastboot, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If all this is new to you (and it sounds like it is) my advice is to start reading the available guides and starter threads. I don't personally like "dummy's guide" approaches. Reading and understanding fully, before doing anything, is a much better idea. You actually learn something that way, as opposed to "step-by-step" guides which do the opposite (you accomplish the task, but probably don't really remember or understand what you even did).
And if you have specific questions, just come back here; and we'll be happy to try and help.
Click to expand...
Click to collapse
Thank you so much for the detailed reply. It's given me the confidence I needed to go ahead with this.
I've had some experience. A few years ago I rooted and s-offed a htc sensation. Problem is its so long ago I've forgotten most of what I learned. Hopefully it'll come back to me as I get into it.
I wasn't aware you could flash roms without rooting. Would you be able to tell me what advantages rooting would allow me over simply flashing a rom?
bryce-bubbles said:
I've had some experience. A few years ago I rooted and s-offed a htc sensation. Problem is its so long ago I've forgotten most of what I learned. Hopefully it'll come back to me as I get into it.
Click to expand...
Click to collapse
I bet you'll do fine. The process isn't terribly complicated or difficult. And if you've done it before, then you know how to follow instructions properly, which is really all it takes.
If you get stuck, or have any specific questions; just come back here and ask, and we'll be happy to help.
bryce-bubbles said:
I wasn't aware you could flash roms without rooting. Would you be able to tell me what advantages rooting would allow me over simply flashing a rom?
Click to expand...
Click to collapse
Some folks like to stay on the stock ROM, but have root (such as for using apps that require root). Other than that preference (to stay on the stock ROM), I wouldn't say there are any "advantages". In the past, this setup (stock ROM, but rooted) may have allowed official OTA updates. But that is no longer the case, as even unrooting will still cause an OTA to fail due to "modified" software. Forcing you to restore the appropriate stock (never rooted) ROM in order to OTA. So that negates any advantage of staying on the stock ROM (and rooting) for OTA purposes.
Flashing custom ROM is for folks wanting something different from the stock ROM (and that sounds like your goal). All the custom ROMs are pre-rooted. So you have root, once you flash the ROM.
@redpoint73: i have a HTC one M8 eye. I try to flash twrp and it says success
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20046 KB)...
OKAY [ 2.139s]
writing 'recovery'...
OKAY [ 0.739s]
finished. total time: 2.883s
But then I cannot enter recovery. It keeps going to bootloader. Do you have any idea?
Hi,
So I'm new to these forums and have been browsing all of the rooting guides for my HTC M8. I am running official Marshmallow and really want to root my phone (again) as far I know I have unlocked boot loader. I had to factory reset my phone last year and never got round to re rooting, but now with marshmallow I wish to do so again.
My issue is I can't seem to understand the steps the guides are outlining. I download the links and try and open them, but nothing happens. Is there a step by step fluid guide in rooting my phone? As all the guides I have found have basically blown over my head. I used a toolkit in the past which did everything for me automatically. If no such post exists would someone be able to explain the steps in a simplified manner? (If possible)
Many thanks in advance to any who help
Optcpsi said:
as far I know I have unlocked boot loader
Click to expand...
Click to collapse
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.
redpoint73 said:
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.
Click to expand...
Click to collapse
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?
Schmix said:
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?
Click to expand...
Click to collapse
You need to allow modifications for root. At least traditional root. Systemless root, I would think would work if you stay read only - but do the research especially if you don't know the difference between traditional root and systemless root.
You can't install OTA updates with a rooted device in any case, so that point is irrelevant.
If/when ever an OTA comes, you would need to return to stock never rooted ROM and stock recovery, in order to OTA update (there are guides on this forum). This would remove any modification by TWRP.
But that's mostly just FYI/academic. Its extremely unlikely we'll get an OTA update to Nougat. Your best bet for Nougat will be custom ROMs, anyway.
1. UNLOCK bootloader with HTC Dev site.
2. Flash latest twrp recovery
3. Flash Stable v2.65 SuperSU
4. Flash wp mod.
5. Update SuperSU on Play Store.
Latest SuperSU 2.76 zip kills Boomsound. Permissive zip can fix that.
Hey everyone,
I apologize in advance if this is breaking any forum rules or if it's a super noob question, but here goes.
I've got a stock AT&T V410 running Lollipop (had I known it would be such a hassle to root, I would've stayed on KitKat).
It's no longer under warranty so I'm thinking about rooting. Unfortunately, the only option that might work is KingRoot. Taking into consideration the possible "shadiness" of KingRoot, here is my idea:
1) Remove microSD and factory reset my V410. This is to have as little info on my V410 as possible before running KingRoot. If I can, I'll even skip adding my Google account.
2) Run KingRoot and see if the root is successful.
3) If successful, install Flashify and flash TWRP (which version should I flash?)
4) If not successful, do another factory reset and continue using my V410 like before.
5) After successfully flashing TWRP, I'll probably do another factory reset, if necessary, to have a clean OS without KingRoot.
6) With TWRP installed, I should be able to make a backup of my current V410 OS, right? I'd like to have this in case I try out CM and want to go back.
I think that's it. Assuming KingRoot can root my V410, does everything here seem viable? I know when I unlocked the bootloader on my OPO it basically did a factory reset anyway, but I want to be safe with KingRoot.
TL;DR
Will a factory reset remove KingRoot? Can I install TWRP and keep the original LG OS?
Won't work. The lollipop bootloader can't be unlocked, and I'm not aware of any exploits. TWRP won't boot. Stay on the lollipop bootloader and you're stuck with kingroot, stock rom, and stock recovery to the best of my knowledge.
I have heard of some methods to try to swap kingroot for supersu once you gain root, but I've also heard of that making a colossal mess with this tablet. Never dug into it, but I suspect supersu attempts to patch the boot image, messes up the signature, then the tab won't boot due to the locked bootloader.
The kitkat bootloader was locked too, but it was susceptible to the bump exploit that let us sign our own boot images.
If you're interested in TWRP and custom roms there is a route to downgrade back to the kitkat bootloader, but it sounds like a giant hassle.
Another random thought, there is a way to enable fastboot on this tablet (you would need root to do it). This method is for the LG G2, but it works fine on my V410. Maybe you could extract the partition images from the kdz in that thread linked above and flash them manually with fastboot instead of LG Flashtool, and get back to kitkat without making such a mess of the internal storage. Disclaimer: I haven't tried this and it could end poorly!!! :silly:
jason2678 said:
Won't work. The lollipop bootloader can't be unlocked, and I'm not aware of any exploits. TWRP won't boot. Stay on the lollipop bootloader and you're stuck with kingroot, stock rom, and stock recovery to the best of my knowledge.
I have heard of some methods to try to swap kingroot for supersu once you gain root, but I've also heard of that making a colossal mess with this tablet. Never dug into it, but I suspect supersu attempts to patch the boot image, messes up the signature, then the tab won't boot due to the locked bootloader.
The kitkat bootloader was locked too, but it was susceptible to the bump exploit that let us sign our own boot images.
If you're interested in TWRP and custom roms there is a route to downgrade back to the kitkat bootloader, but it sounds like a giant hassle.
Another random thought, there is a way to enable fastboot on this tablet (you would need root to do it). This method is for the LG G2, but it works fine on my V410. Maybe you could extract the partition images from the kdz in that thread linked above and flash them manually with fastboot instead of LG Flashtool, and get back to kitkat without making such a mess of the internal storage. Disclaimer: I haven't tried this and it could end poorly!!! :silly:
Click to expand...
Click to collapse
Thanks for the reply jason2678
Good to know that even if I could root my V410, I wouldn't be able to unlock the bootloader, which is my whole reason for rooting. And yeah, current methods to downgrade to KitKat seems like a real pain; for the time being it seems like I shouldn't mess with what works
Hi,
I recently had to return my phone back to stock because of a warranty issue. (battery dying between 25% and 40%)
So chances are high that I will get the phone back with Marshmallow instead of Lollipop.
is there a guide or can anyone give some pointers how to root this device? After a bit of reading I still have a few specific questions, so maybe someone here can help.
A) What TWRP version will I need for the M8s on Marsmallow?
B) Will Magisk systemless root work on this device?
C) If the rooting has succeeded and I remove some bloatware apps from /system/vendor and /privapp and such. Will this trip the Google safety net? Or is safety net not yet applied to our M8s devices?
Thanks!
I don't personally have the M8s version specifically. But as the device forum sections for all the M8 versions in general are becoming pretty quiet; I'll try to help you to the best of my knowledge.
A) The TWRP recovery posted in this (M8s) forum section should work fine on Marshmallow. Looks like it's only updated to 2.8.6
B) Should work, yes. I would suggest the current stable Magisk version, which is 14.0
Backup your stock (unrooted) ROM before trying to root (as you always should - this is best practice and just good common sense). Then if anything goes wrong, you can easily restore to stock.
C) Not sure. But I can tell you on my current device (OnePlus 3T) that removing system (bloat) apps does not trip safety net.
Hi @redpoint73,
Thanks. That takes away some worries and gives me some confidence for giving it a third shot . Nandroid's don't work on the M8s unfortunately, I've tried this once since I botched something up during my first root attempt, put back the Nandroid and my Bluetooth was dead. (and probably more, but I didn't investigate it further back then.)
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Thanks so far and I'll report back my results in this topic. Now I first have to wait to see if they give me my warranty, since the bootloader said relocked and the firm I had to send it to is notorious for blaming factory faults on rooting of the phone. Fingers crossed!
Thijs_Rallye said:
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Click to expand...
Click to collapse
Should be the same, yes.
The reason for this, is that the system is write-protected, even with root. On the M8, there is a kernel mod which disables the write protection (allows you to modify system while booted to OS), but I don't know if there is such a mod for the M8s. But if you were able to do it in TWRP, the same should apply on Marshmallow.
So I finally got my phone back, or well, to be accurate, I got another phone (albeit another M8s) back under warranty. I guess they f'd it up during repairs or something. And as expected my phone was upgraded to Marshmallow.
Anyhow, the more I read about Magisk and systemless rooting the more lost I seem to get lost. Is there somewhere a step by step guide for obtaining root on this phone?
Let me recap from what I've understood so far (SOURCE 1, SOURCE 2 and SOURCE 3)
1) Backup my boot partition, I am still searching how to accomplish this without rooting the phone first. Booting to TWRP without installing resulted in mangling some data in the boot partition, so unfortunately that is not an option. (blanks the OS version)
2) Boot to TWRP and flash the Magisk zip file. There should be an option somewhere in TWRP to enable systemless rooting.
3) ?
So if anyone knows if I am on the right (or wrong) track please let me know .
Thijs
Edit: I can't seem to get the phone boot TWRP for some reason (from my harddrive htc_fastboot boot twrp.img). This used to be possible on my old M8s which I had send in for repairs. Do I really have to flash it because I have no way of backing up the old original recovery .
Okay, since it is kinda dead in here let me bump this for anyone in the same situation. I've managed to install Magisk successfully. The steps involved
1) unlock bootloader
2) flash twrp (htc_fastboot flash recovery twrp.img) I've used the latest version from Captain Throwback which I've found in the OP of the Void_Zero Lineage OS thread.
3) boot the phone and copy magisk systemless root zip and the apk file to your internal storage Grab the uninstaller as well in the topic.
4) reboot to recovery (adb reboot bootloader)
5) flash the zip from within recovery
6) reboot the phone and install the Magisk app.
7) done
Use this guide on your own risk. It worked flawlessly for me but no guarantees .