Hey everyone,
I`m running LineageOS on my phone and am rooted using SuperSU which seems to work, according to Rootchecker and the feww apps I use, which make use of root privileges.
But I`m not entirely happy with my current situation, since it seems that more and more apps don`t tend to work with my rooted phone. So what are my ways out of this?
Can I easily unroot my phone, while keeping LineageOS?
Is there a working alternative to SuperSU, which would enable me to stay rooted on LineageOS without reflashing the OS and use Banking-Apps?
I`ve heard of Magisk, but I am unsure of how to switch over from my current state and I`am not sure whether or not it would solve my problems
Thanks for any help in advance!!
Magisk
You just have to go to SuperSU, then Full Unroot, then download Magisk 13.3 and flash it from TWRP. After that you should have Magisk Manager, if for some weird reason you don't, install it via apk
Then you just go to the settings, tick MagiskHide, then go back and open the side panel, MagiskHide - select the apps that you want Magisk to hide itself from
So I tried to do what you said.
I did the full unroot in the SuperSu App,
My phone rebooted
I shut it down again and booted into recovery
Tried flashing Magisk
But it failed, apparently due to my Boot image being patched by another program and told me to go with stock image
What do I do now? And will I lose any data by doing so? Thank you so much for any help!
Weird, but you can simply dirty flash LineageOS (the same one that you have now, or an update, doesn't matter) and it should let you install Magisk.
I did what you said and installed a delta update using LineageOS Downloader. Had to manually flash it in TWRP since I had no root permissions anymore. But I was able to install Magisk like a charm! Now I have to questions:
1. How do I update Magisk? Using the app?
2. Do I have to flash it again everytime I'm updating LOS?
Thanks for the great help so far!
And what exactly are those moduls? Should I be messing with them?
If updates come they will appear on the status bar and you can download them, and they'll install with the phone on. after that you have to (not quick) reboot your phone.
and about the modules, seriously? what do you think??
I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?
Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?
deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!
Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148
I just bought a Moto g5 plus and rooted it, evidently successfully. Every time an app tried to access the system folder, root access was lost. I could not access the system folder myself to fix the problem without losing root.
Magisk did nothing. Every time I tapped it, it showed nothing but ads.
So I switched to Resurrection Remix 5.8.4 2017-09-17. The versions with Oreo did not work on my phone so I got the latest one with Nougat.
The phone app crashes repeatedly. I wiped/reflashed this time leaving the Google dialer out in the GApps install, I cleared cache after cache, turned off battery optimization for Phone and SIM toolkit, nothing helps
The latest problem I've had is that no apps will download files directly to the SD card. I can access it and move files over, but the whole point of purchasing a large SD card is in case something goes wrong (like installing a faulty rom or breaking the phone on a dryer), my files are safe and accessible once the problem is fixed. It also prevents the phone's internal storage filling up.
The phone this replaced is a Moto g4 play, on that phone I ran a stock room, root stuck like gum on a shoe, and the SD card worked properly.
I have already googled fixes for my issues, nothing in the first page of any search worked.
What I need is a way to make keepvid, Firefox, ACR, and any other program that downloads stuff save it to the SD card AND a working dialer on Resurrection Remix, or instructions on how to make root stick on the stock room, or a *reliable* custom ROM recommendation.
shadow460 said:
.....Magisk did nothing. Every time I tapped it, it showed nothing but ads.....
.
Click to expand...
Click to collapse
This sentence makes me attentively.
I use magisk a long time now and I NEVER saw any ads in it because there aren't any. Where did you download the file?
Also I never heard of losing root when accessing system. How do you realize that an app tries to access system? It seems your device isn't properly rooted, maybe because of a wrong magisk installation. Btw, instead of opening a new thread I would post the problem in the Magisk thread:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page2721
The only place to download magisk.zip and Magisk Manager is here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Sent from my Moto G5 Plus using XDA Labs
https://forum.xda-developers.com/showpost.php?p=75114774&postcount=236
This is the guide I used to root the phone. All the files I needed came from the links there. I went through step by step and, once I finished I ran Root Checker to verify root. Next I flashed super su and went about installing apps until I realized root access had been lost. I found out by trying to run Root Explorer. At the time Super SU was handling all root access requests normally.
The next day I wiped and tried again. I tried several ways to retain root access, with and without Super SU. When I clicked Magisk, it prompted me to update it and sent me to the Play Store for something called Magisk Manager. That appears to be the only update available for whatever's in that guide. I installed it, but it's straight up adware.
Root Explorer, ES File Explorer, and any app that attempt to access the phone's root (system?) folders will cause root access to disappear when they try.
So I gave up on the stock ROM, backed up that install to my SD card, wiped the phone's memory, and flashed Resurrection Remix with Oreo. It was the first thing that came up by searching "best custom rooms for Moto g5 plus". The SD card access in that rom is completely broken, making it useless to me. I wiped that one too and installed the ROM listed above. I ran that without really setting up any of my apps... I downloaded them and left them on their stock settings. I installed the Google dialer with the Aroma GApps, and was later shown this would cause the phone app to crash, which it did.
Wipe and reflash AGAIN, this time sans Google dialer. Turn off battery optimization for phone and SIM toolkit. Wipe cache and data for both. Boot to TWRP and wipe cache/dalvik. NO CHANGE, phone app *still* reports it has crashed but will allow a conversation.
I decide I can live with that and start customizing apps. That's when I find out the *only* apps with write access to my SD card are the camera, the stock file browser, and ES File Explorer. Another app, FX explorer, shows write access is enabled on the SD card. Firefox, AdBlock Browser, and keepvid all need access to it. I grabbed Firefox hoping the issue was just that the others were simply too outdated to work with Nougat, but evidently that's not the case.
The camera and ES went through some kind of weird dialog telling me to select the root directory of the SD card before they would write to it. It's almost as if ES is functioning as a skin for the stock file browser and those other programs have no permission for that.
BTW, the forum chucked me an error about my IP address already being used once today when I tried to reply to this the first time. I was steamed already and about to Chuck the phone out in the freeway.
Basically what I need is advice on a custom ROM that, as Microsoft puts it, just works.
In case it matters, the SD card is a 200GB SanDisk model, A1 / V10 rated (the phone can't transfer data to it that fast anyway) and there's a ~2500 mAh Newdery battery case attached. There is no USB OTG in the battery case... just a cheap Chinese battery.
shadow460 said:
https://forum.xda-developers.com/showpost.php?p=75114774&postcount=236
This is the guide I used to root the phone. All the files I needed came from the links there. I went through step by step and, once I finished I ran Root Checker to verify root. Next I flashed super su and went about installing apps until I realized root access had been lost. I found out by trying to run Root Explorer. At the time Super SU was handling all root access requests normally.
The next day I wiped and tried again. I tried several ways to retain root access, with and without Super SU. When I clicked Magisk, it prompted me to update it and sent me to the Play Store for something called Magisk Manager. That appears to be the only update available for whatever's in that guide. I installed it, but it's straight up adware.
Root Explorer, ES File Explorer, and any app that attempt to access the phone's root (system?) folders will cause root access to disappear when they try.
So I gave up on the stock ROM, backed up that install to my SD card, wiped the phone's memory, and flashed Resurrection Remix with Oreo. It was the first thing that came up by searching "best custom rooms for Moto g5 plus". The SD card access in that rom is completely broken, making it useless to me. I wiped that one too and installed the ROM listed above. I ran that without really setting up any of my apps... I downloaded them and left them on their stock settings. I installed the Google dialer with the Aroma GApps, and was later shown this would cause the phone app to crash, which it did.
Wipe and reflash AGAIN, this time sans Google dialer. Turn off battery optimization for phone and SIM toolkit. Wipe cache and data for both. Boot to TWRP and wipe cache/dalvik. NO CHANGE, phone app *still* reports it has crashed but will allow a conversation.
I decide I can live with that and start customizing apps. That's when I find out the *only* apps with write access to my SD card are the camera, the stock file browser, and ES File Explorer. Another app, FX explorer, shows write access is enabled on the SD card. Firefox, AdBlock Browser, and keepvid all need access to it. I grabbed Firefox hoping the issue was just that the others were simply too outdated to work with Nougat, but evidently that's not the case.
The camera and ES went through some kind of weird dialog telling me to select the root directory of the SD card before they would write to it. It's almost as if ES is functioning as a skin for the stock file browser and those other programs have no permission for that.
BTW, the forum chucked me an error about my IP address already being used once today when I tried to reply to this the first time. I was steamed already and about to Chuck the phone out in the freeway.
Basically what I need is advice on a custom ROM that, as Microsoft puts it, just works.
In case it matters, the SD card is a 200GB SanDisk model, A1 / V10 rated (the phone can't transfer data to it that fast anyway) and there's a ~2500 mAh Newdery battery case attached. There is no USB OTG in the battery case... just a cheap Chinese battery.
Click to expand...
Click to collapse
In the rooting thread you mentioned it says "Chose your preferred rooting app, superSU OR magisk".
Never use both.
I recommend to use this guide:
https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659/post74673573
As superSU is abandoned and not supported anymore I recommend magisk.
If you say "when I tap magisk" than it's the magisk manager you're using. Magisk consists of two parts: The magisk.zip for flashing through TWRP and the Magisk Manager which is the interface.
Nor magisk neither Magisk Manager is in the playstore! Only use the files from the thread I mentioned above. The Magisk Manager apk is inside the zip and also downloadable in the magisk thread. Normally the manager is present when you have flashed the magisk.zip. Sometimes it is not, than install it just like any other apk. But don't use any other sources than
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
So my advice is flash your actual stock ROM (the one you were on) via fastboot.
Hopefully you made a backup in TWRP because if you don't have a backup of EFS and persist you have a big chance of losing your IMEI/4g/voLTE if you switch from an Oreo custom ROM back to stock.
If you have a backup of EFS save it for your life!
If your IMEI and/or 4g is gone after flashing stock restore EFS and if you have it persist when you have TWRP after the next step.
Flash latest TWRP 3.2.3.1.
Boot into TWRP and flash magisk 16 (it's the most stable one at the moment).
If the Magisk Manager is there don't update it if it prompts you to. If it's not there install the apk found in the magisk 16.zip.
This is it in short form, the rooting guide I posted is more detailed.
I think most of your problems result from the not complete rooting solution.
And one hint: Forget ES, it's a data thief.
Use Solid Explorer, Total Commander or imho the best: MIXplorer. This one is not in the playstore, you find it on XDA:
https://forum.xda-developers.com/showthread.php?t=1523691
Sent from my Moto G5 Plus using XDA Labs
I have two backups: one with the stock rom that was losing root and one with the custom ROM above that I took an hour ago. The phone has had Oreo on it and gone back to Nougat, I think with the stock rom.
I took the first backup when I thought I had everything running stable on the stock rom. Is there a way to unroot it and try again?
Not sure what version TWRP is, whatever was linked to in the root guide.
I'm not sure what EFS refers to and I don't yet know how to flash a room via fastboot. I assume it's similar to installing TWRP.
Ok. TWRP is version 3.2.3-1.
I went into the thread above and downloaded Magisk 17.1, which is claimed to be the most stable release. I downloaded the Magisk uninstaller. Next I booted into recovery mode to restore the stock ROM I had used at first (with my apps loaded on it) and uninstall Magisk 16.7.
The uninstaller refused to "install".
Magisk 16.7 refused to install. (Error 1, failed to install from zip)
Magisk 17.1 refused to install. (Same error)
Super SU installed perfectly, though I didn't load into the OS to play with it.
Now is it sinking in that Magisk is CRAP??
I found the stock ROM over at androidfilehost, matched it to the version I have, and attempted to flash that with TWRP. Another error... this one said invalid zip file format.
I'm back on Resurrection Remix, wondering exactly what else I will find broken in it.
The solution here isn't going to be the stock rom, and I will NEVER attempt Magisk again. It's going to be answering three questions:
1. How do I set global permissions for *every* app on this phone to write to the SD card?
2. How do I keep com.android.phone from crashing?
3. Is there a custom ROM that has these issues addressed?
shadow460 said:
Ok. TWRP is version 3.2.3-1.
I went into the thread above and downloaded Magisk 17.1, which is claimed to be the most stable release. I downloaded the Magisk uninstaller. Next I booted into recovery mode to restore the stock ROM I had used at first (with my apps loaded on it) and uninstall Magisk 16.7.
The uninstaller refused to "install".
Magisk 16.7 refused to install. (Error 1, failed to install from zip)
Magisk 17.1 refused to install. (Same error)
Super SU installed perfectly, though I didn't load into the OS to play with it.
Now is it sinking in that Magisk is CRAP??
I found the stock ROM over at androidfilehost, matched it to the version I have, and attempted to flash that with TWRP. Another error... this one said invalid zip file format.
I'm back on Resurrection Remix, wondering exactly what else I will find broken in it.
The solution here isn't going to be the stock rom, and I will NEVER attempt Magisk again. It's going to be answering three questions:
1. How do I set global permissions for *every* app on this phone to write to the SD card?
2. How do I keep com.android.phone from crashing?
3. Is there a custom ROM that has these issues addressed?
Click to expand...
Click to collapse
Stock ROM has to be unzipped in your Fastboot folder on PC and flashed from there. That's why you've got an invalid zip error message.
If you think magisk is crap you will have problems in the future as superSU is dead.
You should read the instructions for installing magisk and how to use the uninstaller.
You have such a lot of problems that I recommend to do a full wipe and install any Oreo custom ROM you want, they all are stable. AOSP Extended or Pixel Experience are good choices. If you want to root them try superSU 2.82 SR5 (the latest stable) or use magisk 16 (I said before that it's the most stable, not 17.1). Do a full unroot if you change from one rooting method to the other. There's a script called unsu.zip from Osmosis which deletes all traces of every rooting method:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067
If you know what you're doing it's an easy job and magisk is a very cool piece of software if you use it correctly.
Sent from my Moto G5 Plus using XDA Labs
Will look into those when I get home. I patched up the g4 play that got crushed by a clothes dryer (oops) and will run it a few days while I work out the g5 plus.
For full unroot do I need to return to stock recovery or can I keep TWRP?
Does Pixel experience have anything to do with the Pixel launcher?
Last question... if I flash the stock room do I still need to unroot?
I actually patched up the g4 play that got crushed when I was moving a clothes dryer and am running it, so I have some time now to work out any issues with the g5 plus. I'll probably go ahead and try one of those custom rooms with SuperSU. I don't use any apps that require non-root and by the time I need to root something again there will probably be a new Superuser type app out there. If I go with the stock rom, I don't see much of a choice, but I'm not thrilled about Magisk.
Let me get on the download for one of those custom rooms you listed...
I hear bad things about 17.1 for Magisk. Find the Magisk 16.0 and you will be fine. But follow the instructions first.
Also there's a thread somewhere for flashing actual stock Nougat zips according to your version (may it be RETUS or RETEU) if anything has gone horribly wrong as it sounds you have at least a working TWRP. Once you got that going, then reboot into recovery, back it all up.
Then format system, cache, data and dalvik (MUST always be done on clean flash). Then flash desired Oreo rom. Then flash Gapps. Then flash Magisk. Then boot it.
I found the thread on TWRP flashable stock roms and am downloading one now. I also found my credit card statement, which reminded me how much I spent on that electronic curse... and I ought to actually put some software on it and use it. Been running the g4 play (harpia) for a bit as I got a semi decent quality screen to replace the broken ones. Parts are getting harder to find... which is the same reason I retired my last Galaxy. (actually I think that one is just missing the ROM...)
Anyway, I backed up the EFS on the G5 plus using TWRP. I plan to try to TWRP flashable stock rom and give Magisk another shot since I have a working phone I can use while I set the G5 up (I have all the time I need).
I think I understand how to recover the imei if it gets deleted.
Update: TWRP flashable stock room appears to be working. Gonna make a nandroid backup of it, grab the Magisk 16 download on *this* phone and then head off to bed. Will attempt root again later this week.
Thanks ya'll!
Next step was getting Magisk 16 on there with the TWRP flashable stock ROM. That was a simple process. I put Joey krim's Root Checker and Root Explorer on also and ran them both to try and remember create the loss of root problem. Root stuck like duct tape... for now.
I looked through Magisk 16's settings using it's manager. I'm not 100% sure what all of that does so I left them alone.
There were some tweaks in RR I liked such as the battery var and swipe the status bar for brightness. If there's a way to run that kind of thing, I'm all ears.
Going for round 2 with the Moto G5 plus. I haven't had any trouble since September 20 aside from needing a screen replacement (I dropped it).
Wife broker HER screen on a Galaxy J3, so she's getting a G5 plus. It's backing up its stock ROM now. I made a backup of the install on my phone with what I consider essential apps. I'll flash that in but put her efs on it from the new to us G5 plus not mine from my phone.
From there everything should be the same save for the phone number, esn, and SD card, plus whatever she puts on it.
Should be a lot faster than her in rootable AT&T J3.
Good day fellow XDA members,
I recently updated my 8 Pro to 11.0.5.5 and forgot that i should not have rebooted it. (Worst idea ever, i know)
I had Root with Magisk before, but now I don't obviously.
So I thought to myself, that this shouldn't be a problem just flash the patched_boot.img anew and i'll have Root again.
Well that was certainly not the case.
I tried just about anything I could find on some Forums the last two days, but couldn't get the device rooted.
What i tried:
Several boot.img from XDA and also patched my own boot.img from the extracted payload with every Magisk apk from 21 onward(Also beta and Canary).
The old patched boot.img i used before the update.
Horizon bootloader
There is obv no Magisk module present anymore to disable/delete.
I also have EdXposed installed.
Everytime i tried something other than the original boot.img i got either a bootloop or a crashdump screen.
Can i get root back without fully wiping my 8 Pro?
If yes, how?
If not, how can i backup everything because some Data from some Apps is crucial to me and is not saved in the Cloud.
Thanks in advance
Dead1y_Wolf
I'm on the same boat I did direct install instead of install to inactive slot
Just follow my guide, change the payload dumper you're using, use the latest version of magisk
Bare in mind that you need to match the version used to create it.
Also don't flash the image. Just boot it.
Make sure modules are removed beforehand.
If that still fails then use the ADB magisk removal command then proceed.
I've booted, flashed, directly installed and updated then installed a lot and have never had a single problem..
So the process is correct..
Hey! haven't seen anyone in this section for a while....
Why I am making this thread
So lately, I was looking through my old phones only only to find my old dusty Samsung Galaxy Note 2 lying around. It had already been rooted with kingroot... Needless to say, it's a spyware and my phone was drastically slow probably because of it.
Long story short, kingroot messed up all the files. Trying to install a working version of SuperSU gave me a headache. Finally, Magisk(v22.1) was supposed to work on the phone as it stated that it's the last version to support v4.4.2 but it doesn't actually work. It keeps on showing N/A whenever I launch it and a million different permutations that I had done in the process of rooting it using Magisk never worked.
This took me days, just jumping from one rabbit hole into another, finding old dead links which really made me so frustrated that at some point I wanted to throw the whole phone away.
That's why I'm creating this thread, so that I save the hassle for myself in the future and hopefully anyone who comes across this.
Updated rooting guide
This guide worked for my GT N7100 android version 4.4.2. It'd also probably work on other devices on other old phones which have an android version less than 5
Just make sure to backup everything before trying it.
Step 1. Flashing TWRP
Download the files from the following link
[TWRP]N7100 TWRP v3.3.1-0 ODIN FLASHABLE [23/05/2019]
Ok there we go this recovery is the latest 3.2.3-2 for t03g only don't flash this on t0lte(N7105). UPDATE: 12/04/2019: official support: https://dl.twrp.me/t03g TWRP 3.2.3-2 for N7100. Bugs: Format as F2FS doesn't work because the option isn't...
forum.xda-developers.com
Download ODIN
https://samfw.com/Odin/Odin3_v3.13.3.zip
Boot the phone into download mode(VOLUME DOWN + POWER KEY + HOME KEY)
Open ODIN and in BL choose the file that you've downloaded whose extension is or is similar to ".tar"
Click start
Step 2. Downloading and flashing Magisk
In here, you need to download a very specific version of Magisk, because anything above this version won't work.
NOTE: If you have installed any later versions of Magisk then make sure to uninstall them first, you can find out how to uninstall it from here(https://topjohnwu.github.io/Magisk/install.html#uninstallation)
Download THESE VERY SPECIFIC VERSIONS of Magisk and Magisk Manager from here
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Get into TWRP recovery mode and then flash Magisk-v21.4.zip
Reboot back into the device and install MagiskManager-v8.0.7.apk
That's the end of it, your device is rooted now
HOWEVER, once MagiskManager has been installed, it would say that there's an update available(a newer version) available that you could upgrade to.
NEVER EVER UPDATE!! Updating your Magisk version to ANYTHING above v21.4 will cause it not to detect root. This is a bug with Magisk and it would probably never get fixed because support for android <5 had been discontinued a long time ago.
In case you ever do accidentally update Magisk, you will have to uninstall the Magisk app and then install MagiskManager-v8.0.7.apk again.
To uninstall and unroot your device, download this file and flash it with TWRP
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip
Where I got the links above from
https://github.com/topjohnwu/Magisk/releases/download/v21.4/
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/
Magisk v22.1
This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.
Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.
ze7zez said:
Magisk v22.1
This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.
Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.
Click to expand...
Click to collapse
Nope doesn't work as it wont be able to detect root at all, this is what had initially caused my headache to begin with
The last version of magisk that actually works on GT N7100 and probably any other old phone is the one that I linked in the thread
EDllT said:
(...)
Get into TWRP recovery mode and flash Magisk-v21.4.zip
Reboot back into the device and install MagiskManager-v8.0.7.apk
(...)
Click to expand...
Click to collapse
Thank you for the information.
I checked on Samsung Galaxy S4 Mini LTE i9195 (stock KK 4.4.2) and it works indeed at most version 21.4.
It is not possible to install MagiskManager-v8.0.7.apk because it is installed together with Magisk-v21.4.zip.