Any help would be greatly appreciated. I have been reading the forums for several days and believe that I am completely stuck. My son rooted his KFHDX 7" and was messing with different apks. It was still working at this point.
He thought it was running slow so he put it into recovery mode (power and volume up) and chose to reset it back to factory settings. Now it just boots to the Gray Kindle Fire bootup screen. Now the ADB is not enabled, he lost his root, and the device is locked.
When I plug the device into my computer (Windows 7) it won't even recognize it. Instead it gives me MTP Devices with error. I have loaded all of the device drives and Android SDK with no luck.
The only adb functions that appear to work are:
adb devices -------> This only gives me the generic serial# 01234569789ABCDE
adb reboot -------> This will reboot the kindle but it won't go past the gray logo
adb reboot-bootloader -------> This will put me into fastboot mode
adb kill-server
adb start-server -------> This will restart the ports but has not affect on the other commands
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
However I can't use the following commands since it says my device is locked:
fastboot -i 0x1949 oem device-info
fastboot flash recovery twrp-2.8.x.x-xxx.img
fastboot boot twrp-2.8.x.x-xxx.img
I tried the 1-Click automated file and it got me all the way through until it asked me to enable the ADB debugging which I couldn't do since I am stuck at the boot screen. And I can't use a tool kit to fix it since I can't downgrade to a lower release.
Therefore I can not unlock my bootloader without downgrading which is impossible without a working system and functioning recovery. I can't root my devices without ADB enabled. And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Please help, I am trying to get this working before Christmas.
Thanks.
DadSteveo said:
Any help would be greatly appreciated. I have been reading the forums for several days and believe that I am completely stuck. My son rooted his KFHDX 7" and was messing with different apks. It was still working at this point.
He thought it was running slow so he put it into recovery mode (power and volume up) and chose to reset it back to factory settings. Now it just boots to the Gray Kindle Fire bootup screen. Now the ADB is not enabled, he lost his root, and the device is locked.
When I plug the device into my computer (Windows 7) it won't even recognize it. Instead it gives me MTP Devices with error. I have loaded all of the device drives and Android SDK with no luck.
The only adb functions that appear to work are:
adb devices -------> This only gives me the generic serial# 01234569789ABCDE
adb reboot -------> This will reboot the kindle but it won't go past the gray logo
adb reboot-bootloader -------> This will put me into fastboot mode
adb kill-server
adb start-server -------> This will restart the ports but has not affect on the other commands
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
However I can't use the following commands since it says my device is locked:
fastboot -i 0x1949 oem device-info
fastboot flash recovery twrp-2.8.x.x-xxx.img
fastboot boot twrp-2.8.x.x-xxx.img
I tried the 1-Click automated file and it got me all the way through until it asked me to enable the ADB debugging which I couldn't do since I am stuck at the boot screen. And I can't use a tool kit to fix it since I can't downgrade to a lower release.
Therefore I can not unlock my bootloader without downgrading which is impossible without a working system and functioning recovery. I can't root my devices without ADB enabled. And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Please help, I am trying to get this working before Christmas.
Thanks.
Click to expand...
Click to collapse
Unfortunately, there is no known recovery from this type of failure. I don't say that casually and wish there was a solution. The symptoms you report are both common and tell tale. The device is bricked.
I just replaced the motherboard on my hdx 8.9
It worked, I had to order a daughterboard also.
Total cost around $50 from where I got them.
Worth looking into. Watch teardown videos on YouTube and get the right tools.
Sent from my SM-N920T using Tapatalk
Too late?
DadSteveo said:
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Click to expand...
Click to collapse
Since fastboot appears to respond as expected on your device,
I'd be **very** interested in testing my long-standing theory
that 'fastboot update' __might__ work even on locked devices.
The "gotcha" is that we'd need to prepare the right package for
your Kindle. So, I gather it's an HDX 7" (3rd Gen?), i.e. "thor" model.
Do you remember what version of Fire OS you had installed?
Hey guys - while trying to unlock the bootloader on my HDX 7, I flashed the older aboot per instructions and now cant get the HDX to boot. It shows a backlit black screen when attempting to boot, IT IS recognized by the computer, and I have ADB composite drivers installed, so thats what it is seen as in device manager. I can't see the system mounted as a file folder, however, I can get it to semi-respond to fastboot commands. fastboot devices lists the serial number, fastboot reboot will reboot it back to the backlit screen, fastboot -w did its thing and wiped it, fastboot flash boot boot.img seems to flash the boot.img, but it still will not boot. Also, NO adb commands are working, and it is not seen when adb shell or adb devices is executed. Am I totally F*cked, or is there hope that I can somehow flash a recovery via fastboot and get a system img flashed? any help or thoughts would be great.
sunapeelakers said:
Hey guys - while trying to unlock the bootloader on my HDX 7, I flashed the older aboot per instructions and now cant get the HDX to boot. It shows a backlit black screen when attempting to boot, IT IS recognized by the computer, and I have ADB composite drivers installed, so thats what it is seen as in device manager. I can't see the system mounted as a file folder, however, I can get it to semi-respond to fastboot commands. fastboot devices lists the serial number, fastboot reboot will reboot it back to the backlit screen, fastboot -w did its thing and wiped it, fastboot flash boot boot.img seems to flash the boot.img, but it still will not boot. Also, NO adb commands are working, and it is not seen when adb shell or adb devices is executed. Am I totally F*cked, or is there hope that I can somehow flash a recovery via fastboot and get a system img flashed? any help or thoughts would be great.
Click to expand...
Click to collapse
Barring a hardware problem your device is likely recoverable. Sounds like you may have flashed the wrong aboot; verify you're using the appropriate image. Aboot-13 is for the 7" (Thor); aboot-14 for the 8.9" (Apollo).
If that's not the issue you will need to coax the device into 'bulk mode' and rebuild from there. Not hugely difficult if comfortable with Android devices and working at the command prompt. There are random posts describing the process in the unlock thread. I'm not in a position to post links ATM so you'll have to do some digging. Read carefully; details and sequence of operations matter.
Davey126 said:
Barring a hardware problem your device is likely recoverable. Sounds like you may have flashed the wrong aboot; verify you're using the appropriate image. Aboot-13 is for the 7" (Thor); aboot-14 for the 8.9" (Apollo).
If that's not the issue you will need to coax the device into 'bulk mode' and rebuild from there. Not hugely difficult if comfortable with Android devices and working at the command prompt. There are random posts describing the process in the unlock thread. I'm not in a position to post links ATM so you'll have to do some digging. Read carefully; details and sequence of operations matter.
Click to expand...
Click to collapse
I flashed aboot 13, but the device never booted after I flashed that and twrp. I figured I could get into twrp since I had flashed it one step previous, but I cant. So i wiped it using fastboot -w thinking I could get rid of the aboot file, then flashed twrp again using fastboot flash recovery recovery.img, it ran through its thing and seemed to flash successfully, but I still cant boot to anything but a blank black screen. no logos or anything. It does respond to all the fastboot commands, of which I only know enough to be dangerous. I've tried changing the drivers around to get adb working to no avail. It seems to be stuck in fastboot mode, even when i fastboot reboot and quickly unplug it. Just not sure where to go from here - it had 4.5.5.2 on it before all of this.
sunapeelakers said:
I flashed aboot 13, but the device never booted after I flashed that and twrp. I figured I could get into twrp since I had flashed it one step previous, but I cant. So i wiped it using fastboot -w thinking I could get rid of the aboot file, then flashed twrp again using fastboot flash recovery recovery.img, it ran through its thing and seemed to flash successfully, but I still cant boot to anything but a blank black screen. no logos or anything. It does respond to all the fastboot commands, of which I only know enough to be dangerous. I've tried changing the drivers around to get adb working to no avail. It seems to be stuck in fastboot mode, even when i fastboot reboot and quickly unplug it. Just not sure where to go from here - it had 4.5.5.2 on it before all of this.
Click to expand...
Click to collapse
Bulk mode and rebuild.
Davey126 said:
Bulk mode and rebuild.
Click to expand...
Click to collapse
Ok, I executed fastboot -i 0x1949 erase aboot and seemingly put the HDX into bulk mode - I can now see a bunch of disk drives on the computer, and it is now recognized as "other devices" "QHSUSB_BULK" in device manager. I still am unable to execute adb commands at this time.
sunapeelakers said:
Ok, I executed fastboot -i 0x1949 erase aboot and seemingly put the HDX into bulk mode - I can now see a bunch of disk drives on the computer, and it is now recognized as "other devices" "QHSUSB_BULK" in device manager. I still am unable to execute adb commands at this time.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post71430759
Davey126 said:
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post71430759
Click to expand...
Click to collapse
ok sick, I was able to execute those commands for aboot and twrp 3.1.1.1 and get the HDX booted into TWRP. now my issue is that I have nothing to install to get a system image going. Any suggestions on something safe?
Got slimrom installed and running 7.1.2 - awesome! Thanks so much for the help!
Hi. Has anyone managed to root Ulefone Armor X5?
The phone is based on MediaTek Helio P23 MT6763, 64-bit Processor.
Baseband: MOLY.LR12A.R2.MP.V91.7.P4
Kernel: 4.4.146#2 wed Sep 25 16:10:16 CST 2019
Build Nr: Armor_X5_MH1_EEA_V01
I have installed the drivers uploaded onto Mega by the Ulefone company here:
https://mega.nz/#F!t64QzRxA!SxZFFl3WrgujTaFshrFuKA!03YnGSYa
I have created the patched boot.img by Magisk Manager 7.5.0.
Enabled the OEM Unlock and USB Debugging thru the Developer options.
Thru ADB, successfully reboots to fastboot by "adb reboot bootloader". The PC recognizes it as typing "adb devices" gives the serial number.
And so far that's all.
Typing "fastboot oem unlock" or "fastboot flashing unlock" gives no result on the phone screen. The ADB says: waiting for device.
I am following most of the steps explained here:
https://forum.xda-developers.com/android/general/root-ulefone-armor-6-tutorial-t3948089
Any advice on what I am doing wrong?
Is it possible to brick it or bootloop by flashing the patched boot.img directly?
Many thanks.
zhekozhekov said:
Hi. Has anyone managed to root Ulefone Armor X5?
The phone is based on MediaTek Helio P23 MT6763, 64-bit Processor.
Baseband: MOLY.LR12A.R2.MP.V91.7.P4
Kernel: 4.4.146#2 wed Sep 25 16:10:16 CST 2019
Build Nr: Armor_X5_MH1_EEA_V01
I have installed the drivers uploaded onto Mega by the Ulefone company here:
https://mega.nz/#F!t64QzRxA!SxZFFl3WrgujTaFshrFuKA!03YnGSYa
I have created the patched boot.img by Magisk Manager 7.5.0.
Enabled the OEM Unlock and USB Debugging thru the Developer options.
Thru ADB, successfully reboots to fastboot by "adb reboot bootloader". The PC recognizes it as typing "adb devices" gives the serial number.
And so far that's all.
Typing "fastboot oem unlock" or "fastboot flashing unlock" gives no result on the phone screen. The ADB says: waiting for device.
I am following most of the steps explained here:
https://forum.xda-developers.com/android/general/root-ulefone-armor-6-tutorial-t3948089
Any advice on what I am doing wrong?
Is it possible to brick it or bootloop by flashing the patched boot.img directly?
Many thanks.
Click to expand...
Click to collapse
If your PC Is not seeing device in fastboot. It may be you need to update your fastboot.exe
In my case there was two possibilities. In Windows 10 I gave myself higher
admin rights clicking right in the folder of my fastboot programm. I tried a little bit, but there is no big thing to get a positive answer writing (before of course I switch on under developer settings usb debugging and gave answer in phone screen) :
fastboot devices
Better and easier is it on Linux, because writing sudo in front of fastboot and ready is it:
sudo fastboot devices
sudo fastboot flashing unlock
or
sudo fastboot flashing unlock_critical
:good:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
waldem88 said:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
Click to expand...
Click to collapse
Thanks for the advice. I am still waiting for someone to give detailed instructions of rooting it.
Did you flash and use TWRP or flashed the patched boot.img straight? Cheers.
waldem88 said:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
Click to expand...
Click to collapse
just got my phone bro. would you be kind in sharing the method you used to root your armor x5.. thanks.
I have the some problem.
In other device, fastboot are work alright.
I try to edit (repack) Zip Rom with replace boot_verified.img with img from magisk, and instal with SP multi port from official site, its error' on boot.img....
Any idea to verify signature boot_verified.img from magisk.???
Sorry for my bad English..
A Solution
Hi, popping in to say I had the same exact problem. After you enter fastboot through the command "adb reboot bootloader", go into device manager and look for Armor X5, right-click update drivers, and then select search for drivers online. It should automatically update with the adb driver.
( I also found the code at the end of the romprovider tutorial titled "How to create a prerooted patched boot.img with magisk" useful, although fair warning it did wipe my device clean )
My input
I'll say this: There is 2, yes, two fastboot 'modes' in this fone, and is provable thus: adb reboot bootloader - shows a black screen with the tiniest of writing, and...
adb reboot recovery - boots us into (origional) recovery, where we can choose to boot into fastboot, however, when booting into this mode, at the top of the screen we see fastbootd - note the 'd' at the end? fastboot commands work, but dont stick, appear to write succesfully.
So when people say they cant use fastboot commands, this is why!
I got as far as:
adb reboot fastboot
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock <-success - bootloader unlocked, and can be relocked.
fastboot -i 0x0E8D flash boot boot.img <- magisk_patched.img (did not show anything to say it worked)
fastboot -i 0x0E8D flash recovery twrp.img <- twrp (tried all available twrp versions, none worked so far, reckon we need a twrp built for this particular fone)
After reflashing the boot, fone bootlooped.
After flashing recovery, fone bootlooped.
So hopefully someone will chip in, because it's not normal that we can apparently flash anything with bootloader unlocked, but now we cant.. I'll point out my fone is an android 10, probably the reason no other twrp's will work, most likely being made on android 9
I have 30 years programming experience, just getting old and cranky...
Seems my thread starter was moved to god knows where, (bang go donations until I see something worth donating to lol), I AM a developer, who buys toys just to hack them!! So may threads in dev section have ZERO useable information, 'scuse the coment :/
Hi, on my side I am stuck in the same way because I found several versions:
- mt6762
- mt6763
i feel all twrp and magisk are for 6763.
Can you confirm which version you have?
Sorry but I'm stuck months too and I really need to root my phone ;-(
Pachacouti said:
I'll say this: There is 2, yes, two fastboot 'modes' in this fone, and is provable thus: adb reboot bootloader - shows a black screen with the tiniest of writing, and...
adb reboot recovery - boots us into (origional) recovery, where we can choose to boot into fastboot, however, when booting into this mode, at the top of the screen we see fastbootd - note the 'd' at the end? fastboot commands work, but dont stick, appear to write succesfully.
So when people say they cant use fastboot commands, this is why!
I got as far as:
adb reboot fastboot
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock <-success - bootloader unlocked, and can be relocked.
fastboot -i 0x0E8D flash boot boot.img <- magisk_patched.img (did not show anything to say it worked)
fastboot -i 0x0E8D flash recovery twrp.img <- twrp (tried all available twrp versions, none worked so far, reckon we need a twrp built for this particular fone)
After reflashing the boot, fone bootlooped.
After flashing recovery, fone bootlooped.
So hopefully someone will chip in, because it's not normal that we can apparently flash anything with bootloader unlocked, but now we cant.. I'll point out my fone is an android 10, probably the reason no other twrp's will work, most likely being made on android 9
I have 30 years programming experience, just getting old and cranky...
Seems my thread starter was moved to god knows where, (bang go donations until I see something worth donating to lol), I AM a developer, who buys toys just to hack them!! So may threads in dev section have ZERO useable information, 'scuse the coment :/
Click to expand...
Click to collapse
error for me too
you are win?
Using win 7 x64,
Phone is on Android 10_Q
Mtk 6765
This is an aarm64, meaning a 64-bit fone, no instructions available so far work, because they are all for android 9, lot's of 'Q' root's, but not for what they call 'A' only boot, which is not the same as A/B partitioning.
All I'm reading now is the same tut's on hundreds of websites giving the same old information... and the fact root is gone. From what I read, My fone is so up to date that I'm where most will be shortly, and with root devs too busy keeping old hat alive... Figure it out: TWRP is actually dead, now. This is why they no longer accept requests here. Twrp cannot be loaded in a dynamic partition setup, (so far) it wont even fastboot boot twrp.img, not happening with ANY twrp. So forget TWRP. Twrp is old hat to my fone.
Magisk, haha, not one version works for true 64bit, (Not implemented yet), and prob never will be, say tata magisk and say tata su, cause we cant write to the deduped ext4 system, root is kinda pointless now, cause if we cant read/write... Overlayfs is the fix I read, in about 5 years...
So its writing custom kernels for the A only tat's the way I read...
Wake up, it's time to experience the cave in to google domination... their AI patc things much quicker than waiting on devs working on what used to work...
Fingers crossed they get round to the new updates instead of concentrating on what works for ONE fone...
Pachacouti said:
Using win 7 x64,
Phone is on Android 10_Q
Mtk 6765
This is an aarm64, meaning a 64-bit fone, no instructions available so far work, because they are all for android 9, lot's of 'Q' root's, but not for what they call 'A' only boot, which is not the same as A/B partitioning.
All I'm reading now is the same tut's on hundreds of websites giving the same old information... and the fact root is gone. From what I read, My fone is so up to date that I'm where most will be shortly, and with root devs too busy keeping old hat alive... Figure it out: TWRP is actually dead, now. This is why they no longer accept requests here. Twrp cannot be loaded in a dynamic partition setup, (so far) it wont even fastboot boot twrp.img, not happening with ANY twrp. So forget TWRP. Twrp is old hat to my fone.
Magisk, haha, not one version works for true 64bit, (Not implemented yet), and prob never will be, say tata magisk and say tata su, cause we cant write to the deduped ext4 system, root is kinda pointless now, cause if we cant read/write... Overlayfs is the fix I read, in about 5 years...
So its writing custom kernels for the A only tat's the way I read...
Wake up, it's time to experience the cave in to google domination... their AI patc things much quicker than waiting on devs working on what used to work...
Fingers crossed they get round to the new updates instead of concentrating on what works for ONE fone...
Click to expand...
Click to collapse
Hello, I have the same phone, any news about rooting etc.. ?
Hi,
I got my Armor X5 P22 Mediatek MT6762, Android 10 phone a couple of days ago to replace an ageing Moto G5S. I have unlocked the bootloader on several previous Android phones, but found doing so on this X5 a bit harder.
Assuming you have enabled 'Developer Options' etc on the phone and installed the Mediatek drivers and 'Minimal ADB and Fastboot' on your PC/laptop, I would suggest that once you are in Fastboot mode and have confirmed that Fastboot recognises your device with the command "Fastboot devices", that you next enter the command
Fastboot /?
This will bring up all the Fastboot commands and options installed on your phone. I then used
Fastboot flashing get_unlock_ability which returned an 8 digit number:-
D:\Minimal ADB and Fastboot>fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.015s]
finished. total time: 0.015s
I have no idea what the 8 digit number means, as I thought it would return '1' or '0' .
However I then did the following:
D:\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: GetVar Variable Not found)
finished. total time: 6.704s
D:\Minimal ADB and Fastboot>fastboot reboot
(bootloader) Start unlock flow
rebooting...
On rebooting the phone, a warning appeared on the Home Screen for 5 seconds stating that the bootloader was unlocked, the phone could not be trusted and my warranty was void. The phone was factory reset.
On re-enabling 'Developer Options' and checking the 'OEM unlocking' option the phone confirms that 'Bootloader is already unlocked'
Don't know whether this helps anyone else struggling to unlock their phone.
The 'fastboot flashing unlock' command might be unnecesary.
regards
bjlabuk said:
Hi,
I got my Armor X5 P22 Mediatek MT6762, Android 10 phone a couple of days ago to replace an ageing Moto G5S. I have unlocked the bootloader on several previous Android phones, but found doing so on this X5 a bit harder.
Assuming you have enabled 'Developer Options' etc on the phone and installed the Mediatek drivers and 'Minimal ADB and Fastboot' on your PC/laptop, I would suggest that once you are in Fastboot mode and have confirmed that Fastboot recognises your device with the command "Fastboot devices", that you next enter the command
Fastboot /?
This will bring up all the Fastboot commands and options installed on your phone. I then used
Fastboot flashing get_unlock_ability which returned an 8 digit number:-
D:\Minimal ADB and Fastboot>fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.015s]
finished. total time: 0.015s
I have no idea what the 8 digit number means, as I thought it would return '1' or '0' .
However I then did the following:
D:\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: GetVar Variable Not found)
finished. total time: 6.704s
D:\Minimal ADB and Fastboot>fastboot reboot
(bootloader) Start unlock flow
rebooting...
On rebooting the phone, a warning appeared on the Home Screen for 5 seconds stating that the bootloader was unlocked, the phone could not be trusted and my warranty was void. The phone was factory reset.
On re-enabling 'Developer Options' and checking the 'OEM unlocking' option the phone confirms that 'Bootloader is already unlocked'
Don't know whether this helps anyone else struggling to unlock their phone.
The 'fastboot flashing unlock' command might be unnecesary.
regards
Click to expand...
Click to collapse
Hello, could you flash twrp on this phone? I have the same one (mt6762, Android 10) and couldnt find a working twrp Port...
Deleted link to unofficial twrp site
maxxvd said:
Hello, could you flash twrp on this phone? I have the same one (mt6762, Android 10) and couldnt find a working twrp Port...
Click to expand...
Click to collapse
You dont have same fone, you have mt6762, I have mt6765
This worked for me (am using a mac so my terminal lingo may be different)
Device: Ulefone X5 2019
Chipset MT6763
Processor: arm64-v8a, A-only system partition
Reset device
Enable developer options, USB debugging, and OEM unlock, then in terminal, do:
adb device
adb reboot bootloader
fastboot flashing unlock_critical
Device is now unlocked and reboots (unlocked warning now appears on reboot screen)
——
Then I installed TWRP & Magisk:
Re-enable developer options, USB debugging, and OEM unlock
To flash the TWRP recovery.img: Copy the TWRP recovery.img into the platform-tools folder, and from that folder, do:
adb reboot bootloader
fastboot flash recovery recovery.img
Then once finished, hold down the power and volume up buttons until it shuts down and restarts (restarts in TWRP recovery)
——
• Download the latest Magisk installer file and put it in the ADB (platform-tools) tools folder (or in your device storage)
• Inside TWRP, go to Advanced > ADB Sideload, then do adb sideload Magisk.zip (replace Magisk.zip with the Magisk zip filename )
Swipe the slider to install Magisk
Tap Reboot System