Related
Hi all,
The original credits for the root go to SuperPichu for the following post: http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
I simply "modified" his process, to make it even more "hassle free"
The process will wipe your data, so remember to backup it.
Besides, I'm not responsible if warranty voids or whatever. Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it. The fastboot unlock procedure has been taken directly by the NVidia Developer's site, so they actually expect the users to do that - but what you will do next, it's all your responsability
So, the overall procedure looks like:
Download&Install the "Mini" ADB/Fastboot from here: http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 (remember to say yes to create the link on the desktop - it will be useful later)
Download&Install NVIDIA ADB Drivers from the official Nvidia site: http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip
Enable "Developer Mode" on the Nvidia Tablet (Settings -> About tablet -> Tap many times (5+) the "Build number" until the Developer Mode is activated
Developer Mode -> Enable USB Debugging
Copy the CWM image and SuperSU (rename it to supersu.zip) where you installed the Mini ADB/Fastboot (default: C:\Program Files\Minimal ADB and Fastboot)
Click the link created by the Mini ADB/Fastboot installation. It should open a DOS console already at the install folder.
(In the Windows console) Type "adb reboot bootloader"
From the rebooted tab, select "Load fastboot protocol" with Volume Keys and push the power switch to confirm
(In the Windows console) Type "fastboot oem unlock"
[ATTENTION: This step will wipe your device] Press the "Volume Down" button to select, with the "Power" button, the "Unlock bootloader" option on device
(In the Windows console) Type "fastboot flash recovery recovery.img"
On the tablet, select "recovery reboot"
You should be now on CWM. Simply select "install zip from file" -> install from sideload
In the console, type "adb sideload supersu.zip"
On CWM select "reboot system", CWM will ask to keep root => say yes
Enjoy your rooted tablet
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
Well first off I havent had any issues with ota updates on CWM (took kitkat otas). Second, if you really don't want a custom recovery why not just obtain root then flash back the stock recovery??
wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
To be honest with you, I haven't updated yet - but the OTA seems to work (i.e. it's currently saying that my Firmware is up-to-date, no errors). Just wait a couple of weeks (NVIDIA released a firmware update every month until now :good: ) and I'll let you know if it works
Btw, even if I loose the the root/CWM, it's not a great deal to install it again
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Good to know. ?But we should be able to flash the ota zips via recovery and flash super su and possibly recovery (locked bootloaders, ota can overwrite recovery) just like we did to update to lolli. I usually see zips before I see the ota anyways.
sandrodjay said:
Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it.
Click to expand...
Click to collapse
I have contacted NVIDIA today, asking steps to move back to Kitkat. I was given instructions to unlock the bootloader, and was assured it will not void the warranty. The assistant was being meticulous regarding this, since she asked around for her colleagues' advice before giving me the information.
So if I ever need to send in for warranty, all I have to do is reflash the factory image to get rid of the root and I'll be all set. If they make a fuss about me having an unlocked bootloader, I'll have a chat transcript to back me up. You guys may want to do the same too.
Thank you worked great!
An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Just took 5.0.1 (wasn't rooted or anything). So I was thinking if I flash the CWM, then do a stock backup, then proceeed to root I should be able to restore the backup when a new OTA comes out since it will be unrooted and stock. Then I can update, install recovery if needed, make another unrooted stock backup, for the next time then reroot, right?
Should work, but after restoring your stock backup you will need the stock Recovery too to update ota.
Hi
There is no need to flash the custom recovery if you don't want to. Just do a fastboot boot recovery <recovery.img>. I did that because i didn't want to change to another recovery.
After the reboot you will revert to stock recovery.
\Sorenjul
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)
Help
Anyone else not able to download supersu.zip the page wont load
Granger77 said:
Anyone else not able to download supersu.zip the page wont load
Click to expand...
Click to collapse
NM sorry just went it opened instantly, maybe to much traffic
eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!
root method LTE compatible
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.
Driver issues
I cant for the life of me get my win 7 64bit pc to install the drivers I've tried uninstall and going through manually with the naked driver method and it still says the device doesnt need it his tutorial is for win 8 am I missing something, I'm losing my mind over here I want this thing rooted so bad I'm losing sleep, and google has been useless
cyraxx84 said:
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!
Click to expand...
Click to collapse
Ty for info and reply.
Bogdacutu said:
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)
Click to expand...
Click to collapse
Got it. Thanks!
oleg77 said:
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.
Click to expand...
Click to collapse
Same here. I got mine on sale with the controlller. I suspect its the same on both wifi only and LTE version.
Can i follow this guide to unlock and root 5.0.1?
I can't find a guide for dummies for it, nor any compatible automatized program or a rom created for it...
Pizzadelivefr said:
I can't find a guide for dummies for it, nor any compatible automatized program or a rom created for it...
Click to expand...
Click to collapse
Been away for a while now so can't vouch if there is a custom ROM available at this moment for your specific K2 variant. However, rooting is very possible. Simply unlocking your bootloader and booting up TWRP recovery is enough to do the job since TWRP will root the device for you. TWRP will or should detect if the device is rooted or not. If it is not then when you select to reboot your system it should ask if you would like to install SuperSU or in lamen terms, to root your device. Obviously you will say yes at this point. When the device reboots then go to the play store to update SuperSU. Once it is updated open the SuperSU app so it can update the su binary. It will ask to update the su binary either normally (by writing to your system with write permissions) or via twrp\cwm. To select the normal option you must either be S-Off or have a custom kernel specific to your K2 variant which has write protection removed. Otherwise, you must select the twrp\cwm method where it will reboot back to the custom recovery and make the change from there. Once the su binary is successfully updated then you are now properly rooted. Do not EVER flash a custom ROM unless the ROM Developer states that it is compatible for your device.
My device is European L04, currently running North Africa release (the earliest Marshmallow build uploaded) - L04_2016_0316_0900 (B820)
I'd like to unlock the bootloader and root my Honor 6. I've never done it (on this particular device), because I've read enough here to know it's slightly more risky than on other devices, especially when you plan to update the stock rom soon, so I preferred to wait until I have the last important update the device is likely to receive - Android 6.0.
What I want to know (some of the answers are in the topics which I listed below):
MultiTool - I've seen reports of bricks when using MultiTool with EMUI4/Marshmallow - why does it happen? My understanding is that MultiTool is a bundle of adb/fastboot and some recovery images for older Android versions, so my theory is that instead of using MultiTool, I should simply get the proper recovery for Marshmallow and flash it manually with fastboot, right?
unlocking bootloader, rooting, flashing recovery - I think I understand the process; in a nutshell: 'fastboot oem unlock X', 'fastboot flash recovery imagename.img', then flash the proper SU.zip in recovery. Where do I find the code, the Marshmallow recovery image, the SU.zip file?
will recovery backup in TWRP work without any problems?
what is the procedure to go back to stock completely after rooting? Unroot, (then wipe if it's needed?) so I am able to safely flash stock firmware again (since, from what I know, flashing stock on a rooted phone makes itself brick permanently, right? or is it just a soft-brick and it can be fixed?)
is there anything else I should know before proceeding?
What I found so far:
http://forum.xda-developers.com/showpost.php?p=66615082&postcount=502 - two recovery images, TWRP and another one (stock?) for the Marshmallow release
http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060/page50 some rooting instructions for the L02 beta, see posts 494 and 498; no idea whether this is applicable to final Marshmallow or L04 at all
http://forum.xda-developers.com/honor-6/general/huawei-honor-6-plus-unlock-bootloader-id-t3357259 an app to get the unlock code, seems a bit shady to me though on the first glance
http://forum.xda-developers.com/honor-6/development/honor-6-rooting-method-t2962795 alternate methods for bootloader (through a website or by email), in case the app won't work; also, detailed instructions on unlocking and rooting
Basically, I need to know whether my procedure is more or less right before I proceed. I think the information is quite hard to find and the risks are quite high, so I'd like to make a promise - when I'm done rooting it and I know the correct process, I'm going to make a "Update to Marshmallow, unlock, root" how-to thread for all the people that will need it in the future.
Another two questions...
1. Where do I get proper SuperSU for Marshmallow? I get a boot loop (yeah, I know I have to wait and I did, but it's a pretty obvious bootloop from watching the logcat content, and nothing new happens...) after flashing http://download.chainfire.eu/supersu-stable (2.65).
2. I have unlocked my bootloader and installed TWRP, so recovery and fastboot are functional. I didn't make a backup before flashing the zip and now I'm in a bootloop. How do I restore working Marshmallow? I assume I can either beg somebody to upload a TWRP backup for my H60-L04, or somehow flash the stock over what I have now. Can I simply use manual update from SD? Can I somehow flash Marshmallow again with fastboot? I'm too scared of bricking my device right now so I guess I'll brace myself for a few days without a phone until somebody helps me :/
I just flashed the Marshmallow release I had before the bootloop (I used Huawei Update Extractor and flashed boot, cust, system and recovery with fastboot; then open up Huawei recovery and factory reset for good measure, I'm not sure it was even needed) and the device is working. I'll restore my stuff, install TWRP, make a backup then try out your ZIP. Thanks
edit: thanks again - your zip works indeed. So after the initial hurdles, now I've got working root and a reasonable way of restoring in case I screw something up along the way.
Before making a new topic with the tutorial I have a few more questions.
First of all, why exactly we weren't supposed to update the rooted devices? I'm not currently interested in OTAs (it's pretty obvious that it needs a functional Huawei recovery, and you need to unroot cause an update can make a mess in a rooted system, making it bootloop for example), but can we flash extracted images with fastboot on rooted devices? Logically, we should be able to... How about sdcard update method?
Can we flash Marshmallow on Kitkat? (fastboot, sdcard, local update methods?) Or do we need to update to Lollipop along the way?
Can I flash stock roms in general (evenbetween different Android versions) by using fastboot with {boot, cust, recovery, system} images only? There's a lot of images that you can extract with Huawei Update Extractor - why there's so many if they're not needed?
So i was thinking that we dont have any thread to this device so i made this.
Can someone help me to unlock bootloader to this beatiful device. i cant get it open.
when im trying to unlock it with the code(adb or flashtool) it gives me error saying "command not allowed" i have tried many times and re installing the drivers and tried different os and nothing helps.
tried to make some research from google etc like stackflow but just cant find nothing. i have the imei right and everything. and tried to unlock with the sonys dev site. and i did out the device as e4g or e4. nothing
command not allowed
to my device xperia e5 f3311 but it also writes in the service menu * # * # 7378423 # * # * service info\configuration is line "rooring status:" bootloader unlock alloved: yes
I'm now looking for a custom recovery for my xperia e5 f3311 and install an supersu.zip and rooting proces is complete but
GameboyZA said:
to my device xperia e5 f3311 but it also writes in the service menu * # * # 7378423 # * # * service info\configuration is line "rooring status:" bootloader unlock alloved: yes
I'm now looking for a custom recovery for my xperia e5 f3311 and install an supersu.zip and rooting proces is complete but
Click to expand...
Click to collapse
Solved the command not allowed proplem . just go in your phone top the developer settings and enable the oem thing. and make sure that usb debugging is on. thats it! hope it helps you out
pottu221 said:
Solved the command not allowed proplem . just go in your phone top the developer settings and enable the oem thing. and make sure that usb debugging is on. thats it! hope it helps you out
Click to expand...
Click to collapse
pottu221 thanks....
Hey, does the root works with your method?
If this work how do you proceed for that (Install CWM and install super su ?)?
Thanks
toinedu27 said:
Hey, does the root works with your method?
If this work how do you proceed for that (Install CWM and install super su ?)?
Thanks
Click to expand...
Click to collapse
aint gonna happen. none of the tools doesnt support mtk 6735 with android 6.0. so we should have rooted phone to get recovery.img so i think that our only hope is to wait that kingroot or something will work on our device
You don't need to wait for the Kingroot as it is not possible to root locked bootloader with drm-verify enabled.
What You need is to create recovery.img to flash on /recovery partition (it should exist, as Sony started to adding them before E5).
There are autotools for MTK devices (they create recovery for specific SoC/CPU not model), but I'm not sure if it is safe to flash on Sony firmware as it is different than generic firmware used on standard (Chinese) devices.
Than using it should be possible to root it by flashing SuperSU zip.
ch3mn3y said:
You don't need to wait for the Kingroot as it is not possible to root locked bootloader with drm-verify enabled.
What You need is to create recovery.img to flash on /recovery partition (it should exist, as Sony started to adding them before E5).
There are autotools for MTK devices (they create recovery for specific SoC/CPU not model), but I'm not sure if it is safe to flash on Sony firmware as it is different than generic firmware used on standard (Chinese) devices.
Than using it should be possible to root it by flashing SuperSU zip.
Click to expand...
Click to collapse
The proplem is that cant get the recovery.img out from anywhere :/
So there's still no way to root this phone ? I really need to install Viper4Android on it ^^
Hey,
I saw the "Dirty Cow" fault on the Linux systems.
I also saw that fault should works on Android, I will see if I can root my device with that
I will be back soon
toinedu27 said:
Hey,
I saw the "Dirty Cow" fault on the Linux systems.
I also saw that fault should works on Android, I will see if I can root my device with that
I will be back soon
Click to expand...
Click to collapse
Have you managed to root your device?
I've been trying to make a working cwm or twrp recovery, but I need to extract the stock recovery.img to do so.
And that requires root.
Can you send me a dm if you managed to root it with the dirty cow exploit? Thanks.
Hey,
I didn't find time to try this exploit but the thing I should do is just install the package dirty cow for android (released on github) and after use the "run-as" command for install super su...
I'm not certain that can work but it should if Sony didn't correct this fault, else I will always can recover via FlashTool to a factory version.
toinedu27 said:
Hey,
I didn't find time to try this exploit but the thing I should do is just install the package dirty cow for android (released on github) and after use the "run-as" command for install super su...
I'm not certain that can work but it should if Sony didn't correct this fault, else I will always can recover via FlashTool to a factory version.
Click to expand...
Click to collapse
Can you check if it works?
I just need a confirmation that you got your phone rooted safely with that fault, then I'll start working on twrp and hopefully we'll have our first rom on this device soon.
But since I recently bought this phone and I can't get my pc to work (for flashtool, in case anything goes wrong), I need someone to test if the dirty cow fault still works on our devices.
If you have time, please check it out.
Hey,
I try but I need to install a tool called "NDK" for the "NDK-Build" command
I'm progressing
I am waiting for a miracle. I also installed Kingroot and in it I found that in 1497 people have applied for root so that we are not alone. ?
Hey there,
I've managed to set up fastboot and finding alternative drivers to work on our device.
Finally, I can now use adb with full fastboot access.
I've also managed to unlock my bootloader, so now I will have to find a recovery that will work on our mediatek 6735 chipset, build based on API 23 (marshmallow).
If necessary, I can try to port cwm from some different device.
When we have a working recovery, we can most likely flash anything, so I might make a prerooted version of the stock firmware.
Expect the first development for this device any soon.
Edit1: Due to health reasons, I might have to delay this for a week, my appologies.
I'm sorry I don't have the time to exploit the Dirty Cow fault (lot of Home Work) and I don't have the knowledges that I need :/
I hope @mrmarvin_16 will got the root access (Thanks a lot )
Hello. Excuse me for my English writing through translayte google. I am writing with Russian Forum 4PDA. We were able to unlock bootloader is a link to my post on this forum 4pda.ru/forum/index.php?showtopic=753685&st=160#entry54277601 . And TWP recovery we also gathered, the download link yadi.sk/d/Vq0jgohxymPCG . Problem Only here we do not know how to sew it into the phone itself.
I flash recovery but i dont have boot to recovery menu
And as you flashed? I just have all the time an error in piercing through ADB.
Hi everyone, I hope I am posting this in the correct section, and if not, can an admin move my post to the appropriate place? I am a geek with PC's but mobile is new to me and I would like to root my device which is a Samsung Galaxy J3 (2018) version. I cannot find info here after searching. Here is what I achieved thus far. I downloaded what I think is the firmware file named FirmwareX.Net_J337WVLS2ASC1_J337WOYV2ASC1_PCM_8.0_Full which has my model number SM-J337W and part of build number in the filename. My build number fully is R16NW.J337WVLS2ASC1. The IMEI is 359229091474959.
I downloaded latest odin tool and just about to download TWRP and my model is not in their list and thats where I'm at. Can someone confirm if this is the actual stock firmware rom, and if I am ready to proceed and some steps would be appreciated. I was told by Oneclickroot service that they have a different stock firmware, and just wanted me to pay for something I can probably do on my own, so I'm puzzled by their reply as I had a very hard time finding this firmware which seems to be the closest match. Has anyone here ever rooted this particular device and provide me a sure step by step way to root it? I do have the setting options OEM Unlock and USB Debugging if that helps.
Bernard St-Pierre
ben480 said:
Hi everyone, I hope I am posting this in the correct section, and if not, can an admin move my post to the appropriate place? I am a geek with PC's but mobile is new to me and I would like to root my device which is a Samsung Galaxy J3 (2018) version. I cannot find info here after searching. Here is what I achieved thus far. I downloaded what I think is the firmware file named FirmwareX.Net_J337WVLS2ASC1_J337WOYV2ASC1_PCM_8.0_Full which has my model number SM-J337W and part of build number in the filename. My build number fully is R16NW.J337WVLS2ASC1. The IMEI is 359229091474959.
I downloaded latest odin tool and just about to download TWRP and my model is not in their list and thats where I'm at. Can someone confirm if this is the actual stock firmware rom, and if I am ready to proceed and some steps would be appreciated. I was told by Oneclickroot service that they have a different stock firmware, and just wanted me to pay for something I can probably do on my own, so I'm puzzled by their reply as I had a very hard time finding this firmware which seems to be the closest match. Has anyone here ever rooted this particular device and provide me a sure step by step way to root it? I do have the setting options OEM Unlock and USB Debugging if that helps.
Bernard St-Pierre
Click to expand...
Click to collapse
The stock firmware that you downloaded is for your model number but you need to verify that it works with your mobile carrier. If you downloaded the correct firmware for your region and your carrier.
There isn't a TWRP recovery or a known rooting method for your model number. You'll have to try the various universal rooting apps and the various rooting programs for PC and hope of them works.
Or you might can extract the boot.img from the stock firmware that you downloaded then use Magisk on PC to create a modified boot.img then flash that modified boot.img via Odin then reboot the device and install the Magisk root manager app on the device to gain root. If your bootloader is locked, you won't be able to flash the modified boot.img, you'll have to find a method to unlock your bootloader, if one exists for your model number, android version and build number.
Sent from my LGL84VL using Tapatalk
Droidriven said:
The stock firmware that you downloaded is for your model number but you need to verify that it works with your mobile carrier. If you downloaded the correct firmware for your region and your carrier.
There isn't a TWRP recovery or a known rooting method for your model number. You'll have to try the various universal rooting apps and the various rooting programs for PC and hope of them works.
Or you might can extract the boot.img from the stock firmware that you downloaded then use Magisk on PC to create a modified boot.img then flash that modified boot.img via Odin then reboot the device and install the Magisk root manager app on the device to gain root. If your bootloader is locked, you won't be able to flash the modified boot.img, you'll have to find a method to unlock your bootloader, if one exists for your model number, android version and build number.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply Droidriven, I thankfully have the option in settings to unlock the bootloader called "OEM Unlock" unlike most other J3's who do not. So basically, you are saying that I can root this device with Magisk with your suggested Magisk method correct? Could you elaborate this method step by step?
Bernard St-Pierre
ben480 said:
Thank you for the reply Droidriven, I thankfully have the option in settings to unlock the bootloader called "OEM Unlock" unlike most other J3's who do not. So basically, you are saying that I can root this device with Magisk with your suggested Magisk method correct? Could you elaborate this method step by step?
Bernard St-Pierre
Click to expand...
Click to collapse
I'll explain the "OEM unlock" setting a bit first. The OEM unlock setting does not necessarily unlock your bootloader. On some devices, enabling this setting unlocks bootloader but on most devices it does not actually unlock the bootloader, it only puts the device in a state that the bootloader "can" be unlocked using some form of unlock method after enabling the setting. In these cases, the unlock method would not work without enabling OEM unlock setting before implementing the unlock method.
So, basically, what I'm saying is that even though you have the OEM unlock setting, this does not necessarily mean that your bootloader is unlocked just by toggling this setting, it may still be locked even after toggling the setting. You'll have to verify whether your bootloader is actually unlocked or not. Do some Google searches for:
"Check bootloader status on Samsung devices"
This should give you results to find a method to verify your bootloader status.
Once you have verified that your bootloader is unlocked, you can use the Magisk rooting method. Read the "Boot Image Patching" section in the link below, there are also several other guides all over the internet and videos on YouTube that give instructions on patching your boot.img. As for actually flashing the boot.img, you will be flashing it using Odin. Use 7zip to compress the patched boot.img into a .tar compressed file. When you flash the file using Odin, place .tar file in the AP slot in Odin.
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
Sent from my LGL84VL using Tapatalk