Database Users

Question about TWRP's SuperSU

For the longest time while installing a new ROM or working in TWRP, I have been asked if I want TWRP to go ahead and install SuperSU for me even if sometimes the device is already rooted. Every guide and advice ever, has always said to ignore this completely. This remains true with Heisenberg's guide.
Heisenberg said:
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.[/b]
Click to expand...
Click to collapse
Heisenberg mentions it is not compatible. My question is why is this true? I flashed a 6P specific version of TWRP.
Also, are there specific circumstances where one would want TWRP to install SuperSU? To me it just seems like a handy time saver especially if you forgot to download it or something.

tsuttie99 said:
For the longest time while installing a new ROM or working in TWRP, I have been asked if I want TWRP to go ahead and install SuperSU for me even if sometimes the device is already rooted. Every guide and advice ever, has always said to ignore this completely. This remains true with Heisenberg's guide.
Heisenberg mentions it is not compatible. My question is why is this true? I flashed a 6P specific version of TWRP.
Also, are there specific circumstances where one would want TWRP to install SuperSU? To me it just seems like a handy time saver especially if you forgot to download it or something.
Click to expand...
Click to collapse
Root with marshmallow is different to all previous Android versions, it requires a modified boot.img. The most recent versions of the beta branch of SuperSU patches the boot.img for you, and you get working root. The version that TWRP offers to install is outdated and doesn't perform thief modification of the boot.img, flashing it will result in a boot loop. For the above reasons there are no circumstances where you'd want TWRP to install it for you.
PS. You could have just asked this question in the guide thread.

Heisenberg said:
Root with marshmallow is different to all previous Android versions, it requires a modified boot.img. The most recent versions of the beta branch of SuperSU patches the boot.img for you, and you get working root. The version that TWRP offers to install is outdated and doesn't perform thief modification of the boot.img, flashing it will result in a boot loop. For the above reasons there are no circumstances where you'd want TWRP to install it for you.
PS. You could have just asked this question in the guide thread.
Click to expand...
Click to collapse
Thank you for the clear explanation. I suppose you are correct about that, my apologies. I think I was getting it confused for a different thread which was closed. In case you can't tell, I'm new here. Lol

tsuttie99 said:
Thank you for the clear explanation. I suppose you are correct about that, my apologies. I think I was getting it confused for a different thread which was closed. In case you can't tell, I'm new here. Lol
Click to expand...
Click to collapse
Well, welcome to XDA then! Here's the thread in case you need it:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

ZTE Axon 7 Tenfar's Root and Magisk

Hi all,
let me first start by thanking the good people of xda community for your kind help and contribution. It would not be possible for people like me with extremely limited rooting knowledge to even have the courage to attempt a root if it wasn't for the good people like you here.
I just got my Axon 7 and is trying to work up the courage to attempt a root following tenfar's instruction (I'm extremely scared of bricking my new phone) I also hope that I can continue to play Pokemon Go after I root it, but unfortunately with the latest update, it seems impossible until I discovered Magisk. My question may seem fairly simple but it is extremely confusing to me. In Magisk's instruction it says that in order to install Magisk, one must remove any kind of root and systemless Xposed. Since my phone is not rooted, I do not have to go through the step of removing root and xposed? However, it says that I have to download Magisk and flash it. My confusion rests on the concept on how I can flash Magisk if my phone is not rooted? I thought one can only flash a rom etc after the phone is rooted? So should I follow tenfar's root first and root my axon 7 then try to flash Magisk? or the other way around? Any advice /tips/precautions/high level guides regarding both rooting using the tenfar method and flashing Magisk is greatly appreciate! I may suck at rooting and etc, but what I can do is follow all instructions carefully. Thank you everyone, you are the best!

To flash something (a ROM or an app, like Magisk) you need to have a custom recovery installed (such as TWRP, you boot into the custom recovery to flash the .zip file that contains whatever you want to flash) which generally means having an unlocked boot-loader, neither of those has anything to do with root (other than that they make rooting the phone considerably easier) they don't require it and they don't do it by themselves.

@Nameless One is right, you need a custom recovery (TWRP) to be able to flash Magisk. There is a thread about this in the forums.
However I would advise you to wait until next week when a new update is expected and perhaps some changes to the bootloader unlock policy and hopefully stock ROMs, which will make it much easier to solve any problems.
If you insist on going through with this now, you should take backup images of various partitions so that you can restore your phone to stock to receive the OTA.

How does it work if you have uninstall any kind of root? I would think root would be a requirement.

KyJelly69 said:
How does it work if you have uninstall any kind of root? I would think root would be a requirement.
Click to expand...
Click to collapse
It right on the top of their post
"This mod requires boot image modification, so unlocked bootloaders are required!"
What it does is implement it's own system-less root management module that will not be detected like other root methods. But will conflict with other root methods hence you have to be unrooted
Unlocked bootloader let's you flash custom recovery. That in turn let's you flash anything else including root modifications. In essence tenfar's boot image is modified to allow root. This will do something similar but you have to have the BL unlocked since patching boot image will change the signature.

iirc magisk alters the bootimage, so you need a unlocked Bootloader go get it to work.
And no, root is not a preq, you can use magisk to /aquire/ root though.
What u need:
- unlocked bootloader
- custom recovery
- a somewhat clean and not already modified system

Thank you all for the helpful replies, I greatly appreciate them.
I'm running out of the box ZTE Axon 7 A2017U with 6.0.1 Android. My goal is to install Magisk then eventually root so I can play Pokemon Go on the phone. Please advise on the next step? What are some of the safety precautions I should take? Thank you all very much!
I'm also planning on waiting until the next update [email protected]'s advice. Can anyone please explain to me the reasoning behind mh127's safety precautions? Thanks!

projectseahorse said:
Thank you all for the helpful replies, I greatly appreciate them.
I'm running out of the box ZTE Axon 7 A2017U with 6.0.1 Android. My goal is to install Magisk then eventually root so I can play Pokemon Go on the phone. Please advise on the next step? What are some of the safety precautions I should take? Thank you all very much!
I'm also planning on waiting until the next update [email protected]'s advice. Can anyone please explain to me the reasoning behind mh127's safety precautions? Thanks!
Click to expand...
Click to collapse
If you have copies of the stock images you will probably be able to fix your phone if something goes wrong and you want to go back to stock.
Not having these copies is like jumping out of a plane without a parachute and hoping you'll hit a haystack, without the pitchfork in it...
There are never any guarantees, every phone is different and as you are playing with important partitions there is a chance, generally through users fault, to brick your device...

Hello all,
Do we know if the "stock rom" @mh127 was talking about is available? Am I safe to proceed with the the magisk/root installation? Thanks!

projectseahorse said:
Hello all,
Do we know if the "stock rom" @mh127 was talking about is available? Am I safe to proceed with the the magisk/root installation? Thanks!
Click to expand...
Click to collapse
Well, the stock images have not been released for the B27 update, which would make it much easier to recover if something goes wrong. However, unofficial images are available (look around the forums). So at this point it is your call, just be careful.

No unlock for the A2017G model?

Hey,
I'm thinking about buying the Axon 7 but as far as i can see there is no unlocked bootloader (so no root aswell) for the model A2017G, is this correct?

multimill said:
Hey,
I'm thinking about buying the Axon 7 but as far as i can see there is no unlocked bootloader (so no root aswell) for the model A2017G, is this correct?
Click to expand...
Click to collapse
Its possible. Mine is rooted on unlocked BL but you will need to research a little bit...

Diplodocus123 said:
Its possible. Mine is rooted on unlocked BL but you will need to research a little bit...
Click to expand...
Click to collapse
Would you mind to share how you have done that?

This is the tutorial I have used:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Just follow carefully every step and make SURE you have all your backups ready just in case....

Diplodocus123 said:
This is the tutorial I have used:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Just follow carefully every step and make SURE you have all your backups ready just in case....
Click to expand...
Click to collapse
Thank you. One last question: Can I still receive offical updates when i unlocked the BL and can I just flash SuperSU after installing TWRP?

As far as I'm aware you can still receive updates after you installed TWRP, but not after you unlocked bootloader and/or rooted. You can however flash just about every official OTA via TWRP quite soon after the OTA is released, @DrakenFX and others usually make a TWRP flashable OTA zip within hours of official release.
You cannot install SuperSU without unlocking bootloader via my guide. First install TWRP, then unlock BL, then root. Otherwise you will soft brick your phone.
There are methods around the forum to root without unlocking the BL, but I haven't tried them. Some A2017G users had hardbricked devices when they tried to do this on their devices. G versions seem more prone to get stuck in DFU mode forever.

B03 (or B06) was last version who could be rooted without unlocking. B08 (or B06) added fastboot mode where you can unlock bootloader.

Thank you two

Return to Stock Question

With the impending release of the stable Oreo build, I have a question on how I will update. I'm currently on the NMJ51B build, rooted with Magisk and Unlocked Bootloader. I'm under the impression I won't be able to OTA Oreo when it's released, so what will my process be?
Sent from my PH-1 using Tapatalk

cas239 said:
With the impending release of the stable Oreo build, I have a question on how I will update. I'm currently on the NMJ51B build, rooted with Magisk and Unlocked Bootloader. I'm under the impression I won't be able to OTA Oreo when it's released, so what will my process be?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
If you have stock recovery you should be fine.
Magisk should not stop the OTA, but you will need to re-root.
Otherwise use one of the stock installs in the ROM section.

tech_head said:
If you have stock recovery you should be fine.
Magisk should not stop the OTA, but you will need to re-root.
Otherwise use one of the stock installs in the ROM section.
Click to expand...
Click to collapse
I flashed TWRP Recovery when I rooted the phone

Bump
Sent from my PH-1 using Tapatalk

I'm in the same position as you, rooted on NMJ51B and planning on updating to the official Oreo release. This is the path I plan on taking:
Download the Full Dump (back to stock) zip from here: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681. Run flash-all.bat. This will take you back to stock on your current build.
Take the OTAs to update to Oreo.
Follow the rooting instructions for Oreo from the rooting guide here: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
There may be another way, but reading through the forums I expect that to be a safe path that should work.

bjs339 said:
I'm in the same position as you, rooted on NMJ51B and planning on updating to the official Oreo release. This is the path I plan on taking:
Download the Full Dump (back to stock) zip from here: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681. Run flash-all.bat. This will take you back to stock on your current build.
Take the OTAs to update to Oreo.
Follow the rooting instructions for Oreo from the rooting guide here: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
There may be another way, but reading through the forums I expect that to be a safe path that should work.
Click to expand...
Click to collapse
That is the correct path.
If you are on a stock ROM and running TWRP, you can also just flash the stock boot after uninstalling Magisk.

tech_head said:
That is the correct path.
If you are on a stock ROM and running TWRP, you can also just flash the stock boot after uninstalling Magisk.
Click to expand...
Click to collapse
So I can flash the stock Oreo boot image from within TWRP after uninstalling Magisk? And then I would flash Magisk again from within TWRP before booting? Just making sure I understand correctly, as I'm actually considering doing this with the Beta 3 just released. And TWRP would not remain on the device, correct?

bjs339 said:
So I can flash the stock Oreo boot image from within TWRP after uninstalling Magisk? And then I would flash Magisk again from within TWRP before booting? Just making sure I understand correctly, as I'm actually considering doing this with the Beta 3 just released. And TWRP would not remain on the device, correct?
Click to expand...
Click to collapse
No.
I was just talking about back to stock.
You would need to flash Oreo B3 separately.
You could just connect to a computer and flash Oreo B3 without going back to stock.
The fastboot flashable ROM is in the ROM section of the forum.

I've gotten most of the way there. Went back to stock on 51B, then sideloaded OB3. Now I need to root with Magisk, but it just won't work. I followed the instructions for Oreo in the rooting thread, but TWRP won't accept my passcode. I've tried it several times, making sure to press the right buttons, but TWRP keeps telling me the passcode failed. I've also tried patching the OB3 boot image with Magisk and flashing that, but the spinner keeps spinning and doesn't boot.
I get the feeling that the only way I'm going to get root is by wiping userdata and starting with a clean factory reset. I'm just trying to find a way to avoid that. Does anyone have any idea what's wrong? I really appreciate the help I've gotten so far.
Edit: Even when I remove the pin and flash the boot image and Magisk in TWRP, it's still not booting. I don't think decryption is the problem, but I'm not sure what is. I'm following the same instructions that many have used to root successfully.

bjs339 said:
I've gotten most of the way there. Went back to stock on 51B, then sideloaded OB3. Now I need to root with Magisk, but it just won't work. I followed the instructions for Oreo in the rooting thread, but TWRP won't accept my passcode. I've tried it several times, making sure to press the right buttons, but TWRP keeps telling me the passcode failed. I've also tried patching the OB3 boot image with Magisk and flashing that, but the spinner keeps spinning and doesn't boot.
I get the feeling that the only way I'm going to get root is by wiping userdata and starting with a clean factory reset. I'm just trying to find a way to avoid that. Does anyone have any idea what's wrong? I really appreciate the help I've gotten so far.
Edit: Even when I remove the pin and flash the boot image and Magisk in TWRP, it's still not booting. I don't think decryption is the problem, but I'm not sure what is. I'm following the same instructions that many have used to root successfully.
Click to expand...
Click to collapse
TWRP has a screen image offset.
Look very carefully at the passcode as you enter it.
I have a failure rate of about 50% due to the misalignment.

I just tried returning to stock on my Essential PH-1 and when it reboots, I have no way to interact with the screen.. Side buttons work great, but can't move past the first "Let's get started" screen... no touch? Please help.
thanks!

How did you "return to stock"? Using what method and files? From what are you returning?

drumrjoe said:
I just tried returning to stock on my Essential PH-1 and when it reboots, I have no way to interact with the screen.. Side buttons work great, but can't move past the first "Let's get started" screen... no touch? Please help.
thanks!
Click to expand...
Click to collapse
Which version of the stock ROM?

It originally came with 7.1.1 NMJ32f/436.. which upgraded to the latest version of pie... 9 something.. I have tried using the .bat file on both stock files, NMJ32F_back_to_stock and PPR1.180610.091_BACK_TO_STOCK_OTAFILE with the same result.. see vid please ... https://photos.app.goo.gl/XRUScdV9UYDnx5dn9
Thanks in advance for any help.
DJ

So I've had the idea and its probably been discussed to death because I'm slow. But say now I have pie running on partition a, what stops me from swapping to slot b in fastboot and installing a stock oreo or say custom rom? I've already bricked one essential so I'm gunshy to do anything. But luckily it worked out because I'm sure the one I had before was a sprint "unlocked" one everyone is having issues with.

10.3.0 bootloader unlock + root

I've read the guides on how to unlock bootloader, install twrp & gain root (magisk preferred) with 10.3.0 and I still do not quite understand.
This is the best Android I've had and I'd really like to do this right. Would anyone please help me? Thank you, Stephen

stovo06 said:
I've read the guides on how to unlock bootloader, install twrp & gain root (magisk preferred) with 10.3.0 and I still do not quite understand.
This is the best Android I've had and I'd really like to do this right. Would anyone please help me? Thank you, Stephen
Click to expand...
Click to collapse
You can't go wrong with the guide here https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
It's very simple to follow
Just update to the newest version TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk

clsA said:
You can't go wrong with the guide here https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
It's very simple to follow
Just update to the newest version TWRP and Magisk
Click to expand...
Click to collapse
I thought this was for 9.x.x

stovo06 said:
I thought this was for 9.x.x
Click to expand...
Click to collapse
Nothing has changed but the versions of TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk

clsA said:
Nothing has changed but the versions of TWRP and Magisk
Click to expand...
Click to collapse
Thank you. Definitely need to get this done.
Atm I think I'm gonna stick with stock ROM but maybe a custom kernel.
Any suggestions?

clsA said:
Nothing has changed but the versions of TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help, but I don't think this is entirely correct. The "fastboot boot" command was removed in a10, and an alternative method was eventually developed AFAIK.
I never did get a successful root on this device after spending a whole day on it. It's difficult because little bits of information are scattered everywhere instead of in a single up-to-date guide. And a few months ago, no one could agree on anything. Just look at how many other people got semi-hard bricked.

flyoffacliff said:
Thanks for trying to help, but I don't think this is entirely correct. The "fastboot boot" command was removed in a10, and an alternative method was eventually developed AFAIK.
I never did get a successful root on this device after spending a whole day on it. It's difficult because little bits of information are scattered everywhere instead of in a single up-to-date guide. And a few months ago, no one could agree on anything. Just look at how many other people got semi-hard bricked.
Click to expand...
Click to collapse
Fastboot boot command has been allegedly fixed in 10.3.0 and this fix has been confirmed by several people. So yes the philosophy and method hasn't changed since years. At worse you use 'fastboot flash boot' command instead. That's only one change.
You can still extract boot img from payload.bin on your computer, transfer it to your phone and use Magisk manager to patch it and then transfer and flash it with fastboot from your computer. Then you flash twrp installer as a module in Magisk Manager once your phone is rooted. That also hasn't changed for years, this method has always existed.
Most of people bricking their device are doing one thing or another wrong.

Striatum_bdr said:
Fastboot boot command has been allegedly fixed in 10.3.0 and this fix has been confirmed by several people. So yes the philosophy and method hasn't changed since years. At worse you use 'fastboot flash boot' command instead. That's only one change.
You can still extract boot img from payload.bin on your computer, transfer it to your phone and use Magisk manager to patch it and then transfer and flash it with fastboot from your computer. Then you flash twrp installer as a module in Magisk Manager once your phone is rooted. That also hasn't changed for years, this method has always existed.
Most of people bricking their device are doing one thing or another wrong.
Click to expand...
Click to collapse
This is where I start getting confused lol.
I appreciate the help, but this is not what I'll accustomed to.
Anything you recommend reading to help educate myself?

stovo06 said:
This is where I start getting confused lol.
I appreciate the help, but this is not what I'll accustomed to.
Anything you recommend reading to help educate myself?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...l-oxygenos-beta-1-oneplus-6t-t3881099/page484
Read Cultofluna post
And search Google for it, many tutorials

Striatum_bdr said:
https://forum.xda-developers.com/on...l-oxygenos-beta-1-oneplus-6t-t3881099/page484
Read Cultofluna post
And search Google for it, many tutorials
Click to expand...
Click to collapse
Nice instructions, But I'm curious why you think he needs them ?
all he needs is
unlock bootloader
fastboot flash boot TWRP.img
boot to TWRP / Flash TWRP installer.zip
Reboot recovery
Flash Magisk.zip in TWRP
reboot
done
the guide I linked earlier goes into great detail explaining each of these steps
He could even use the All in one tool after downloading the correct versions of TWRP and Magisk

clsA said:
Nice instructions, But I'm curious why you think he needs them ?
all he needs is
unlock bootloader
fastboot flash recovery TWRP.img
boot to TWRP / Flash TWRP installer.zip
Reboot recovery
Flash Magisk.zip in TWRP
reboot
done
the guide I linked earlier goes into great detail explaining each of these steps
He could even use the All in one tool after downloading the correct versions of TWRP and Magisk
Click to expand...
Click to collapse
I know that it's the way Android works since years....
But a guy warned him about bricked phones and other very alarming prophecies... So I gave him a plan B in case of...

Striatum_bdr said:
I know that it's the way Android works since years....
But a guy warned him about bricked phones and other very alarming prophecies... So I gave him a plan B in case of...
Click to expand...
Click to collapse
That's what I've read as well. And there are many solutions but I find them scattered all over the forms.
And I don't trust YouTube videos lol

I just want to make sure it works with 10.3.0.
I can downgrade if necessary but trying to find the easiest method.
Thanks guys for all your help. Maybe I'll post a 10.3.0 thread after this if it's needed to avoid confusion

stovo06 said:
I just want to make sure it works with 10.3.0.
I can downgrade if necessary but trying to find the easiest method.
Thanks guys for all your help. Maybe I'll post a 10.3.0 thread after this if it's needed to avoid confusion
Click to expand...
Click to collapse
I don't think there is the need of another thread. Many are already talking about rooting and flashing twrp.
What makes people confuse is that perhaps some of them think things have changed... And that methods are bound to an Android version.
Nothing has changed.
Fastbooting TWRP and then flashing it, is the way we do it since years. Patching boot img as an alternative is also a classical way to root.
People are blinded by tiny differences and don't see that the frame hasn't changed. You unlock the bootloader, then boot to twrp and then either you flash only Magisk either you flash twrp then Magisk. Very simple. Always with latest versions.
It's because xda threads are not moderated except for offenses, etc that many users post their 'own' recipe every 2 pages without anybody cleaning and organizing things to make them understandable. And the fact that threads are not well maintained in time, with titles and first posts instructions that can seem obsolete.... Especially on old phones like our when devs are quitting the scene without designating a maintainer

clsA said:
Nice instructions, But I'm curious why you think he needs them ?
Click to expand...
Click to collapse
Thanks for clarifying.
Even for someone experienced with flashing and modding in the past, but I've been away from the flashing world.
There is a lot of conflicting info about this. Some say to patch boot img manually.
The TWRP thread says to install TWRP as a magisk module.
But seriously, Thanks. I'm glad I came across this thread. I thought the old way of doing things was done with Android 10, until I read this.

aaron74 said:
Thanks for clarifying.
Even for someone experienced with flashing and modding in the past, but I've been away from the flashing world.
There is a lot of conflicting info about this. Some say to patch boot img manually.
The TWRP thread says to install TWRP as a magisk module.
But seriously, Thanks. I'm glad I came across this thread. I thought the old way of doing things was done with Android 10, until I read this.
Click to expand...
Click to collapse
You can do that, installing TWRP as a module, since one year or so. So you just fastboot boot twrp, flash Magisk zip, then once phone booted back to Android, flash twrp as a module with Magisk Manager
Same thing if you just want to flash kernels, no need to have TWRP, Ex Kernel Manager or Franco Kernel Manager can do this as long as you're rooted

Striatum_bdr said:
You can do that, installing TWRP as a module, since one year or so. So you just fastboot boot twrp, flash Magisk zip, then once phone booted back to Android, flash twrp as a module with Magisk Manager
Same thing if you just want to flash kernels, no need to have TWRP, Ex Kernel Manager or Franco Kernel Manager can do this as long as you're rooted
Click to expand...
Click to collapse
@Striatum_bdr you've been very helpful person here in a bit.
Since this a/b partition has come around, I have gotten multiple ways to unlock bootloader and root with my moto x4. And before I owned that Motorola, I've never had a reason to use a/b partitions. Long story short, my TWRP got screwed and I've become hesitant about doing anything with a new device. And this is the best device I've owned in many years so I have to do it right.
Unless any further issues arise, I'm going to go for it.
Thank you everyone that's helped guide me thru this.
Edit :I've no idea what patching a boot img is lol.

stovo06 said:
Thank you. Definitely need to get this done.
Atm I think I'm gonna stick with stock ROM but maybe a custom kernel.
Any suggestions?
Click to expand...
Click to collapse
Wait for render zenith

stovo06 said:
@Striatum_bdr you've been very helpful person here in a bit.
Since this a/b partition has come around, I have gotten multiple ways to unlock bootloader and root with my moto x4. And before I owned that Motorola, I've never had a reason to use a/b partitions. Long story short, my TWRP got screwed and I've become hesitant about doing anything with a new device. And this is the best device I've owned in many years so I have to do it right.
Unless any further issues arise, I'm going to go for it.
Thank you everyone that's helped guide me thru this.
Edit :I've no idea what patching a boot img is lol.
Click to expand...
Click to collapse
Yeah, this is an awesome device. Only device I've been happy with since my old Samsung note 4. Biggest thing I miss, it'd be nice to have an SD card slot!
Patching a boot image is what Magisk does when you install it. But you just would manually do this.

Last question, I've been reading too install Magisk 19.4.
Does that still apply?
Apologies for all the questions (and great appreciation for the help), but the information here is scattered and at times contradicting when all I need now is a simple magisk manager and mod ?.
Thank you all for your help.