yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
Hi [MENTION=4126377]tdm[/MENTION], this maybe away from the scope of this thread, but I'll ask anyway because you seem to have more knowledge than everyone else

I'm trying to have a go at decompiling both systemUI and settings.apk to add the "data rate" (speed of mobile network) option in the status bar.

I remember the stock marshmallow had it, but after upgrading this option disappeared. The nougat setting app still has the strings in it, so I'm trying to compare the differences between both android 6 and 7 apks.

Would you or anybody be able to post the apk for these two apps?

I don't know where to get the old stock rom anywhere.

I found some info about it here

https://xdaforums.com/android/general/mod-status-bar-network-traffic-separate-t3024878

but I think it may be easier for me to implement because there seem to be very little different between the settings apps from android 6 to 7, in fact there is even a chance there are actually the same or at least nearly identical.

Thanks
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Yes it is a bit OT here, but that's okay.

It's really easy to pull stock APKs if you have a backup of your stock system partition (you *did* make a backup, right?) and you have a Linux system available (a VM will work fine). Just loopback mount the system image and copy the file out.

I've done this with my stock system backup (7.1.1 US version). Here's the file:

http://files.nwwn.com/android/axon7mini/SystemUI_ZTE.apk

Enjoy, and good luck!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] countercharge:
tdm, off topic question but any updates on oreo for the mini?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Not yet, I'm pretty busy.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
EDIT: FORGET IT, I FOUND THE OLD SPANISH MARSHMALLOW ROM ON MY LAPTOP. Thanks

-------------

Thanks. But I'm after the APK from M ROM. I don't have a backup from it because you remember I had to upgrade to N ROM before I installed twrp!

I do have a backup of my android 7 system, but nothing of the old marshmallow.

Cheers
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] shinkso:
Radio band problem

Hello guy's

i tried to force the LTE on my ZTE axon 7 mini B2017G ; android 7.1.1 by using the secret code *#*#4636#*#* i switched the radio band to US after that my sim slot 1 no network captured and slot 2 won't capture LTE band ; can someone help me pls to erase the modem to factory . pls help

Best regards
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Gearswar:
Hi, can I get a step by step instructions how to flash the recovery? I used EDL tool and determined my phone is connected. But running that tool to flash recovery or tuliptool doesn't flash nothing.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
During my research to recover my IMEI I read that once you "touch" the radio band via the secret code menu, you can't restore it without a bit of an deep operation. I hope I'm wrong, but that is what I heard.

Go to you twrp and back up your data.

Factory reset. Does it solve the network issue?

Yes. Restore your data.

No. You get your phone back at work for sure by flashing the full edl ROM. The link can be found on this thread a couple of pages back. Once the ROM is flashed you can restore your data.

Cheers

---------- Post added at 06:52 PM ---------- Previous post was at 06:47 PM ----------

The OP is the step by step. But keep reading the following pages 1,2,3.....and you find the correct command line where tuiliptiol has the .exe extension.

What android are you on now?

Can you boot into android?

Is usb debug on?

Can you check your bootloader is actually unlocked using the same tuliptool?

Cheers
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Klimon5:
ZTE Axon 7 mini B2017G running Marshmallow factory

When I boot my phone into EDL mode zadig doesn't detect it as device 05c6:9008. It shows up as Qualcomm HS-USB QDLoader 9008 (COM4) under my devices in the control panel and zadig recognizes it as QHUSB_BULK . I plugged the device in and had it install the MTP drivers while it was in the OS and USB debugging is enabled and it accepts my laptop as a recognized device. I am certain EDL mode is working because the device shows no signs of being on in any way. (not even the LED is on as it should). Could someone please help me get the phone detected properly? I want to unlock the bootlader.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] :
bro, you must update zte axon 7 mini to android nougat before using the tool and

there's also no need to unlock bootloader
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Klimon5:
Ok but I tried using the B12 update zip from ZTE USA website and it failed to update though the settings via micro SD card. Where can I find the B14 update zip file?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] :
your zte axon 7 mini is american or european

https://xdaforums.com/axon-7-mini/development/firmware-stock-firmware-t3696538
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Klimon5:
American. I'm certain. B2017G
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] :
I'll find you

---------- Post added at 02:44 PM ---------- Previous post was at 02:36 PM ----------

better to use adb sideload
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Klimon5:
Adb sideload to the SD card?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] :
not

1 enter recovery and select adb sideload, from your zte axon 7 mini

2 on the PC opens the command window and writes adb sideload (file name)

example: adb sideload update.zip
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Klimon5:
ADB sideload

I tried sideloading the update. I used the B2017G firmware zip you linked earlier and it didn't work. I downloaded the stocksystem.zip
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] :
that's for twrp, I'm sorry

here https://dl.dropboxusercontent.com/s//795e4x4qynloeuc/P852A12V1.2.0B12_RM_data.zip?dl=1

this is the firmware
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Klimon5:
Ok so now I ****ed up and my phone is hard bricked. I went and used an update file from here https://www.ztedevices.com/en/support/detail?id=03743F4E761C475F838D444384791D36. I was impatient. Windows detects it and doesn't recognize it. The phone has no signs of life other than that. It's my dumbass fault.:mad:
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] :
maybe this will help you

https://r.tapatalk.com/shareLink?ur...share_tid=3755112&share_fid=3793&share_type=t
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
Whatever happened to you, is described in this very forum. You just need to read ALL of it, including my Summary of all and any possible brick situation you can find. I went through all of them
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Go into device manager and uninstall any ZTE or android drivers you see. The fact that windows sees the device but doesn't recognize it means the incorrect driver is being used.

Since windows can see the device and acknowledge when it is plugged in means that the device is powering on. Possibly into edl as default. Read over the instructions again. Install the drivers as listed. See what that does for you. If it sees the device in edl successfully then try and flash files as you normally would. I would suggest, trying to get back to stock.

When in possible brick always stop and look at what's going on for a second before blindly screaming help. 9 times out of 10 it's not hard bricked.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
White screen

I went back to stock & when my phone was installing an update, rebooted to the white screen of death. Can tuliptool be used to fix this?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
You should be able to install TWRP and go from there.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
Can't get past the white death mask though. I tried. Also ran several commands through edl mode
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] koktey14:
If you are able to use edl mode there must be a solution for this. Tdm knows better.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
What version of stock were you running? If TWRP won't boot it's usually because you were on android 6.0 (marshmallow).

If you can't get the phone working, you can try this:

http://files.nwwn.com/android/axon7mini/qfpkg_tulip.exe

It will flash the 7.1 nougat boot stack and twrp.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
The tried b14 firmware from here

https://www.google.com/amp/s/xdaforums.com/axon-7-mini/development/firmware-stock-firmware-t3696538/amp/ but, it wouldn't work so I had to go with b12 firmware. The update isn't on ZTE 's Dropbox anymore
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
Tried this but, says device not present. Should I be in EDL or white screen?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Yes edl mode.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
Well that did something... I can now boot to Lineage recovery. Which... I didn't even know was a thing. Problem is, nothing works through it. Tried to do factory reset from there.. Also tried to mount the system but, that didn't work either. I just noticed it also says Android 8.1.0 / LimeageOS 15.1-20180615-UNOFFICIAL-Tulip at the bottom of the recovery screen. I was on Android 7.1 (lineage-14.1-20181022-nightly-tulip-signed) before trying to go back to stock
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Oh interesting, I thought I put TWRP in there. Maybe I'll update that. In any case you should be able to use tuliptool to flash TWRP now and be on your way.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
Funny thing about that. I never could get tuliptool to work. Ended up installing twrp through fastboot the first time. Not that will help me now, since I can't boot
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Well... tuliptool and the one you just used share the same USB code. So it's pretty much impossible for one to work and the other not.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
Weird. This is what tuliptool does

PS C:\Users\zenic\Desktop\Axon Root\tuliptool> write recovery tulip-twrp-7.1-r1.img

recovery

tulip-twrp-7.1-r1.img

PS C:\Users\zenic\Desktop\Axon Root\tuliptool>
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] koktey14:
You must run this code.

tuliptool write recovery tulip-twrp-7.1-r1.img

Not just write you must also run tuliptool
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
Tried that

PS C:\Users\zenic\Desktop\Axon Root\tuliptool> tuliptool write recovery tulip-twrp-7.1-r1.img

tuliptool : The term 'tuliptool' is not recognized as the name of a cmdlet, function, script file, or operable

program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

At line:1 char:1

+ tuliptool write recovery tulip-twrp-7.1-r1.img

+ ~~~~~~~~~

+ CategoryInfo : ObjectNotFound: (tuliptool:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\zenic\Desktop\Axon Root\tuliptool>
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] LeonardoGC:
Hi cinez,

I assume you are using PowerShell on Windows.

Try to run this code:

.\tuliptool write recovery tulip-twrp-7.1-r1.img
(one dot and a back slash before the command itself)

or this one:

..\tuliptool write recovery tulip-twrp-7.1-r1.img
(two dots and a back slash before the command itself)

Regards
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] :
he's really writing it wrong, it's tuliptool-win64 write recovery (file name).

or rename it tuliptool so that it works
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
There's what I was doing wrong! Thanks! However,

PS C:\Users\zenic\Desktop\Axon Root\tuliptool\tuliptool> .\tuliptool write recovery tulip-twrp-7.1.1.img

Sending programmer...Failed to send programmer: Unknown error

PS C:\Users\zenic\Desktop\Axon Root\tuliptool\tuliptool>

a TWRP version of that qfp file maybe?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] :
I do not know what is qfp.y it seems now tulipol is detected the device that is good, but try to write TWRP Oreo or Nougat

---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------

I'm sorry but are you using the edl cable?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
No edl cable
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] :
Mmmm ... I recommend that you buy an edl cable to be able to revive the device if it is very stuck
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] stfn74:
As far as I understand, there are two versions of the Axon 7 Mini - regular one (international?) and USA version. Difference seems to be in the 4G/LTE bands support (according to GSM Arena).

So will this tool work with both versions? Also, does anyone know if the version sold in Canada is the international or the USA version?

Also, can this be used to root?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Yes, I am sure there are more than two versions of the device. ZTE produced at least three versions of the Axon 7 -- USA, European, and Chinese. I would be interested in finding all the device variants and comparing them.

The unlock is generic in that it is based on standard QCOM code in aboot. So it should work on any device that can be put into EDL mode. But there is no guarantee that all models can be put into EDL mode with the key combination. The European Axon 7 cannot do this, and therefore must be put into EDL mode via "adb reboot edl". This makes the device more fragile and it must be updated with more care.

The recovery image is more closely tied to the device because it holds the device model number which is used when verifying compatibility for flashing, but it will very likely boot on all models. The boot image is even more specific, and should only be used with the exact software version specified.

The boot image can be used to root the device. This was the reason for removing the verity flag. Without the verity flag, the system partition can be modified eg. to place the "su" binary in /system/xbin. Alternatively, SuperSU has a systemless root mode that only re-packs the boot partition, and it also has the capability to remove the verity flag during the re-pack operation.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] saymonek:
I would like to add, that there is UK version as well which I own (single SIM, 'Carphone Warehouse' distribution). I believe it is not similar to USA, EU or Chinese version, because I can't update from Android 6.0 to 7.1 using update packages for that countries. You can download official firmware (6.0) for UK version here: http://www.ztedevice.com/support/detail?id=70784AF8D2DF4CE883D0FBE6A95622F3
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] CRAFTER0302002:
Any ideas

This is my errors

Zadig error:

Driver installation: FAILED (Operation timed out)

Administrator cmd error:

Microsoft Windows [Version 10.0.15063]

(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd /

C:\>C:\Users\nicho\Desktop

'C:\Users\nicho\Desktop' is not recognized as an internal or external command,

operable program or batch file.

C:\> cd C:\Users\nicho\Desktop

C:\Users\nicho\Desktop>tliptool

'tliptool' is not recognized as an internal or external command,

operable program or batch file.

C:\Users\nicho\Desktop>tuliptool

'tuliptool' is not recognized as an internal or external command,

operable program or batch file.

C:\Users\nicho\Desktop>tuliptool

'tuliptool' is not recognized as an internal or external command,

operable program or batch file.

C:\Users\nicho\Desktop>cd tuliptool

C:\Users\nicho\Desktop\tuliptool>tuliptool-win64

Usage:

tuliptool-win64 lock <status|lock|unlock>

tuliptool-win64 <read|write> <boot|recovery>

C:\Users\nicho\Desktop\tuliptool>tuliptool-win64 lock status

Cannot open USB device: Bad file descriptor

C:\Users\nicho\Desktop\tuliptool>

any ideas?

Do I need dev mode on?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
I don't normally use Windows, so I'm not familiar with all the fun issues that you can encounter with zadig. I used zadig to install the WinUSB driver a long time ago and I don't really want to mess with it.

Maybe someone else can help...
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Try uninstalling the factory Qualcomm driver. And then try to reinstall win USB.

Ok new issue.

The program is looking for recovery.bin but the included files are .img files. So according to the installer the files are not present.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
You are supposed to copy the file:

copy tulip-twrp-7.1.1.img recovery.bin

The idea was that you could keep the original safe.

I guess the operation isn't clear enough, so I'll post a new version soon that lets you specify the file on the command line.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
You need to add the. Exe file extension. So your command should look like

C:\users\nicho\desktop\tuliptool>tuliptool-win64.exe lock status
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Meme Queen:
it still says failed when it unlocks the bootloader but i don't know why because for all intents and purposes it didn't fail lol
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Can you post what commands you used?

I have bootloader unlocked already. However I guess I'm not grasping the proper commands to use to write the files.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Meme Queen:
be careful because after i did all this and rebooted, it turns out it doesn't have an operating system anymore so it'll just go right back to TWRP and i don't know if that's something i did or what.

so after backing up the boot and recovery with the read command and renaming the boot image to boot.bin and recovery to recovery.bin, this:

D:\Libraries\Downloads\tuliptool\tuliptool>tuliptool-win64.exe write recovery

Sending programmer...Connecting to programmer...log: logbuf@0x08067EB8 fh@0x08064D20

log: logbuf@0x08067EB8 fh@0x08064D20

log: Finished sector address 0

log: Finished sector address 0

log: Finished sector address 0

Writing recovery ...

log: start 1181696, num 65536

Write 33554432 bytes, 65536 sectors

log: Finished sector address 1247232

Success!

D:\Libraries\Downloads\tuliptool\tuliptool>tuliptool-win64.exe write boot

Sending programmer...Connecting to programmer...log: logbuf@0x08067EB8 fh@0x08064D20

log: logbuf@0x08067EB8 fh@0x08064D20

log: Finished sector address 0

log: Finished sector address 0

log: Finished sector address 0

Writing boot ...

log: start 1050624, num 65536

Write 33554432 bytes, 65536 sectors

log: Finished sector address 1116160

Success!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Uhmm, what? Were you running 7.1.1 b12?

Can you flash the backup/stock boot and recover the device?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Thats exactly what im doing and its not working. Hmmmm....

I get :

Writing Recovery:.....

Failed: Can not open Recovery.bin No such file or directory

---------- Post added at 10:49 PM ---------- Previous post was at 10:42 PM ----------

also the 7.1.1 update on my device is showing as a B14 build. NOT B12
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Meme Queen:
yeah, i restored the backups and it's working fine. the OS is still there. like [MENTION=7636441]MrWhite0429[/MENTION] mine's actually b14 which... yeah lol rip
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
There is a 7.1.1 b12 and a 7.1.1 b14.

I'm running b12, I haven't updated to b14. So the boot image in the zip is for b12.

I'll update to b14 soon and provide a corresponding boot image. But I'm busy building Lineage right now...
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
No worries tdm. At least the bootloader is unlocked on my device. Take your time
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] CRAFTER0302002:
YESSS! Me and my friend got it to work. Now unlocked are running perfect on windows with b-14 (not 12)! Took us a little but did it! Thanks TDM, and keep me updated on the rom. Any idea of the date?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Status updates in this thread:

https://xdaforums.com/axon-7-mini/development/calling-mini-owners-t3679120
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Kookstir:
I cant seem to access the /data partition, and install Magisk. Do i have to format data after I install the custom recovery and unlock, because it never asked me. Would that have something to do with my issues? also there are very few options (like no options in the "Mount" menu on the main screen).

Thanks for any assistance! :)

P.S. Great Job on developing this tool. You really kick started this community!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
The initial alpha version of TWRP is rather limited, it's mostly a proof of being able to run a custom recovery. It uses the stock kernel with selinux enforcing and it can't decrypt data.

I'll be building a fully functional TWRP in the next couple of days.

Also note the unlock procedure should have wiped your data.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
yeah probably
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
That looks better. You just need to verify the USB driver is correct and the device is actually in edl mode.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cinez:
Both are good
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] countercharge:
I'm having a little issue. All of a sudden I am not able to use tuliptool. It says "Cannot open USB device: Bad file descriptor". I have used it previously to backup boot and recovery and install TWRP. The last thing I did was install AOKP and Viper4Android and Magisk, but it (Viper4android and Dolby Atmos) didn't work, so I went back to stock. I had some difficulty reinstalling the stock image but was finally able to get it to work, although for some reason the touch screen isn't working.

Anyway, I'm trying to follow the directions in this thread from scratch and I'm at the part where I run zadig to install the WinUSB driver, and I wanted to make sure that everything is correct. I don't see the device labelled "05c6:9008" in the drop down list, but it does say that in the USB ID field. Instead, in the drop down list of devices it says "QHSUSB__BULK". See this image:

Is this correct, or am I going to screw something up if I click replace driver?

And yes, I did hold down the volume buttons to go into EDL mode before connecting usb cable and then release.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
Hi. It is being a long time since I last did this.

Your screen shot shows the process to install the driver only, in your pc, so no risk of damage here.

Once the bulk drive is installed, then you will find this same name "bulk" in device manager.

If this is happening, then it means you can now send "reboot edl" command from command prompt.

After that the tulip tool should work, if your stock is android N.

I think if I'm wrong at least I'm not too far.

Cheers
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] soopamanne:
Root or not root

Hi guys,

I've read tons of subjects and posts, but i did not figured out the answer.

Is the Zte Axon 7 mini rootable or not? (On official versions)

My current version is B2017GV1.2.0B15 - official update.

I've tried many things, thanks to the wonderful tutorials here, but still no root.

I tried downgrade to 6.0, upgrade to 7.0 B09, B12, B15.

I had TWRP installed, but no success with root.

Many thanks!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] k500zm:
[MENTION=9764798]soopamanne[/MENTION]

Yes just install twrp and then install Magisk in TWRP