Database Develop

CM-su still being detected by Magisk, Magisk Hide not working

Hi,
I'm currently so confused as to why my Magisk isn't working. I'm currently running the last CM 13 snapshot for the Galaxy S5 (G900F, klte), and root and Xposed work fine via Magisk.
However, what isn't working is Magisk Hide, and I'm not sure why. However, I'm noticing that even though I fully unrooted cm-su (using SuperSU, in a way that means the only root I can select in Dev Options is ADB only), I'm still getting cm-su detected by Magisk.
I'm confused -- is there anyway I can remove it? I've tried looking through TWRP file manager, but whenever I do so, I can't even see /system/ files, and mounting only mounts to USB, but that's unrelated.
Thanks for any help!

intcompetent said:
Hi,
I'm confused -- is there anyway I can remove it? I've tried looking through TWRP file manager, but whenever I do so, I can't even see /system/ files, and mounting only mounts to USB, but that's unrelated.
Click to expand...
Click to collapse
I don't think SuperSU removes the in-built CM superuser. Use the UNSU zip by osmosis instead. https://forum.xda-developers.com/showthread.php?t=2239421
Also magisk hide will NOT hide Xposed. Yes not even systemless 87.1 Xposed.

SuperSU removed its own root only, CM root is unaffected.
Also, Magisk hide only works with Magisk's own phh root.
And, as far as I know, it can't successfully hide Xposed either. Doesn't matter if it is systemless or not.

Cheers for the replies.
I wasn't aware that Magisk Hide didn't hide Xposed, that's my bad.
As for the presence of CM-SU, SuperSU did do something, as the Developer Options root option is now ADB only while previously it offered the option to Apps too. I'll try unsu.
Here's what I'm meaning btw: imgur.com /a /yTOTw (sorry for the link bypass, there's no other way for me to simply demonstrate the issue) (as you can see in the first screenshot, Magisk detects "cm-su" along with phh. When phh was disabled before I removed cm-su, it only detected cm-su, hence leading me to believe cm-su remains).
e: tried unsu, still cm-su remains. At this point, I'll leave it -- I presume that it's permanently ingrained into the ROM. I've gotten around the restriction I was facing anyway, and I'll adjust. Thanks anyway!

intcompetent said:
Cheers for the replies.
I wasn't aware that Magisk Hide didn't hide Xposed, that's my bad.
As for the presence of CM-SU, SuperSU did do something, as the Developer Options root option is now ADB only while previously it offered the option to Apps too. I'll try unsu.
Here's what I'm meaning btw: imgur.com /a /yTOTw (sorry for the link bypass, there's no other way for me to simply demonstrate the issue) (as you can see in the first screenshot, Magisk detects "cm-su" along with phh. When phh was disabled before I removed cm-su, it only detected cm-su, hence leading me to believe cm-su remains).
e: tried unsu, still cm-su remains. At this point, I'll leave it -- I presume that it's permanently ingrained into the ROM. I've gotten around the restriction I was facing anyway, and I'll adjust. Thanks anyway!
Click to expand...
Click to collapse
If there are SU files in /system/bin and /system/xbin, then CM root was not removed. Not completely.
To actually remove it you have to delete those files.

Pwnycorn said:
If there are SU files in /system/bin and /system/xbin, then CM root was not removed. Not completely.
To actually remove it you have to delete those files.
Click to expand...
Click to collapse
@intcompetent Osmosis's unsu zip removes those files. If those files are still there after flashing the unsu zip, I'd ask in his thread.

knpk13 said:
@intcompetent Osmosis's unsu zip removes those files. If those files are still there after flashing the unsu zip, I'd ask in his thread.
Click to expand...
Click to collapse
Or just remove them manually, jeez. It's just two files.
I've been doing it manually for months and everything works as intended.

As an a closer, there's nothing there. I presume that Magisk is picking up something freaky from somewhere, or something's up, but I'm good guys. I won't need anymore help.
Cheers!

I found this zip around somewhere. I believe it works to remove all root (systemless as well) and I've always flashed it before rooting normally. It should also remove CM root afaik.
As a test, after flashing, check and see if you pass safetynet before installing magisk

intcompetent said:
As an a closer, there's nothing there. I presume that Magisk is picking up something freaky from somewhere, or something's up, but I'm good guys. I won't need anymore help.
Cheers!
Click to expand...
Click to collapse
I
L

! /data/adb/magisk_merge.img mount failed

Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!

MasterSheea said:
Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!
Click to expand...
Click to collapse
Hi, Can you attach logs while flashing ?? from both MM and recovery

MasterSheea said:
Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!
Click to expand...
Click to collapse
Known issue on some MTK devices. Loop mounting doesn't work.
There are lots of reports like this for Doogee... There's been some investigating into it in the beta thread, but as of yet there's no solution, I believe.

Hello!
Yes, of course!
Logs of magisk installer and TWRP recovery here:
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Ignore the crittografy error; I have tried to disable the crittografy and all is the same. Same problem.
In more, yesterday I had another annoying problem with magisk: before the options of the magisk app disappeared (there is the pic in the folder I attached. Then magisk is totally disappeared: magisk is not installed anymore in your device.
Tried to re-install magisk: nothing happens.
I have re-flashed the ROM and re- installed magisk: at moment is working.
Root files and SuperSU are not working.
I will open a new forum discussion for this problem.
Thank you in advance.
Greetings

MasterSheea said:
Hello!
Yes, of course!
Logs of magisk installer and TWRP recovery here:
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Ignore the crittografy error; I have tried to disable the crittografy and all is the same. Same problem.
In more, yesterday I had another annoying problem with magisk: before the options of the magisk app disappeared (there is the pic in the folder I attached. Then magisk is totally disappeared: magisk is not installed anymore in your device.
Tried to re-install magisk: nothing happens.
I have re-flashed the ROM and re- installed magisk: at moment is working.
Root files and SuperSU are not working.
I will open a new forum discussion for this problem.
Thank you in advance.
Greetings
Click to expand...
Click to collapse
The file is not accessible

Sorry.
Try now, please.
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk

MasterSheea said:
Sorry.
Try now, please.
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Click to expand...
Click to collapse
Looks like recovery can't decrypt /data, so that's likely an issue there. But it'd be easier to tell if you had provided the recovery log rather than a screenshot (Advanced - Copy log after trying to flash).
And, it would also be very useful if you had provided a Magisk log rather than only installation logs.
But, it's probably a moot point anyway. Like I said earlier, this is a known issue with loop mounting on Doogee devices (and other devices using Mediatek). No solution as of yet...

Didgeridoohan said:
Looks like recovery can't decrypt /data, so that's likely an issue there. But it'd be easier to tell if you had provided the recovery log rather than a screenshot (Advanced - Copy log after trying to flash).
And, it would also be very useful if you had provided a Magisk log rather than only installation logs.
But, it's probably a moot point anyway. Like I said earlier, this is a known issue with loop mounting on Doogee devices (and other devices using Mediatek). No solution as of yet...
Click to expand...
Click to collapse
Same here, provide good logs

Ok, thanks.
I will try to send you good logs.
About encryption, I have tried to disable encryption and to install all without encryption: nothing changes.
Before I must understand why magisk disappears from system, then I will collect logs about modules installation. Magisk is the only way to root this damned phone, SuperSU does not works.
Thank you in advance

MasterSheea said:
Ok, thanks.
I will try to send you good logs.
About encryption, I have tried to disable encryption and to install all without encryption: nothing changes.
Before I must understand why magisk disappears from system, then I will collect logs about modules installation. Magisk is the only way to root this damned phone, SuperSU does not works.
Thank you in advance
Click to expand...
Click to collapse
There was no need to start a new thread about that... You've already got this one going.
The screenshot of the Manager you provided simply showed a Manager without internet access. Completely normal.
About losing root completely, make sure you don't have any aggressive battery optimisation on the Manager. More here:
https://www.didgeridoohan.com/magisk/Magisk#hn_Randomly_losing_root

Ok, good, I close the other thread
Yes true, that is a normal screenshot of magisk offline. Yesterday I did formatted data to disable encryption and I lost all the other screenshots, but was like this: before all options disappeared, then magisk disappeared.
No, no aggressive battery optimization running, but I have installed greenify and amplify... Perhaps one of this app makes problem?

I wish to close the other thread, but I do not know how to do it.
How to do it, please?

MasterSheea said:
Ok, good, I close the other thread
Yes true, that is a normal screenshot of magisk offline. Yesterday I did formatted data to disable encryption and I lost all the other screenshots, but was like this: before all options disappeared, then magisk disappeared.
No, no aggressive battery optimization running, but I have installed greenify and amplify... Perhaps one of this app makes problem?
Click to expand...
Click to collapse
Make sure the Manager is removed from Battery optimisation and that it isn't selected I'm Greenify. It's not certain that this is the issue, but it's worth ruling out.
Other than that, a logcat of it happening, or even just a screenshot of the Manager when things aren't working. A Magisk log is also useful, of course.
MasterSheea said:
I wish to close the other thread, but I do not know how to do it.
How to do it, please?
Click to expand...
Click to collapse
Just let it be...

Oki.
I removed magisk from battery optimization.
I hope that at least the root will work.
But I seen in another thread that there is a solution known as f2fs workaround bug fixer. But is still not working. I hope that someone will fix it soon.
Anyhow, thank you for all

Move to thread https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875. Flash last zip. Move to magisk manager, install updated (2018.3.6) version. All modules should now install fine.

Hello.
Thank you for the answer.
I have tried to flash the zip without success.
No magisk installation found or installed version is not supported.
Error process 1.
The magisk version I have installed is v16. - 5.6.4(112).
The last one, suppose.
Any suggestions, please?
Thank you in advance ?

I made also the this attempt: I have flashed a magisk module using flashify.
The flashing was successful, but the module is not in the magisk list.
Can be a permission problem? Someone knows where is the folder of installed magisk modules, please? Perhaps is a permission problem and changing permissions will work...

Download f2fs-loopback-bug-workaround-2018.1.31.zip from the thread. Place it in Download folder of internal storage. Reboot to recovery. Flash zip in twrp. Reboot. Open magisk manager. F2FS Loopback Bug Workaround should be installed in modules. I hope any module can be installed from now on.

Dear Pragnan Saha,
Thank you for your answer.
I have tried to flash f2fs-loopback-bug-workaround-2018.1.31.zip, but without success.
TWRP says: No magisk installation found or installed version is not supported. Error process 1.
Some suggestions, please?
Thank you in advance

Didgeridoohan said:
There was no need to start a new thread about that... You've already got this one going.
The screenshot of the Manager you provided simply showed a Manager without internet access. Completely normal.
About losing root completely, make sure you don't have any aggressive battery optimisation on the Manager. More here:
https://www.didgeridoohan.com/magisk/Magisk#hn_Randomly_losing_root
Click to expand...
Click to collapse
What thread? And is it about exact the same error ! /data/adb/magisk_merge.img ... What this thread is about?
Do you know if there's a fix already? I'm on ext4 so f2fs loopback makes no sense for me
And @MasterSheea do you have a fix?
I've got exactly the same error with flashing modules, after clean flask is possible to install modules but after 1 reboot it fails

Rooting LN14????

Could someone please point me at instructions on how to root LN14.
I've searched the HD/HD+ forums for 'root LN14' and 'rooting LN14' and got no results (which by itself is suspicious).

have you enabled Developer Options?

I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!

harryzee said:
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
Click to expand...
Click to collapse
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.

digixmax said:
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
Click to expand...
Click to collapse
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.

harryzee said:
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
Click to expand...
Click to collapse
I meant "enable, disable,, then re-enable" the root access option in "Developer Options".

Aha! Will give it a go. Thanks.
5/2/2018:
Okay: I d/l three android root checkers and titanium backup. The first root checker (Clivin Inc. with small green android robot graphic) told me I was not rooted both before following your above instructions and after. The other two (d/l after following the above) both say I am rooted. However, I was not and am still not able to get "TB" to run. It says "failed" and that I am not rooted.
Since the HD+ is running really well now in its stripped down mode, I can "leave well enough alone" or try to get "TB" working so I can remove anything not needed for my chosen minimal functionality (ereader, viewing videos, photo review/minor editing) that would further reduce unnecessary battery drain.
Thanks again for the above clarification and any additional thoughts.

I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

You got it. Use Magisk. Works wonders and way better than SuperSU or any other root permission tool I've came across. It's even akin to, and even has within it, xposed and other magical rooted modules for you to try out for a day or two and then decide you don't need it.
pchc_lx said:
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse

[HELP] Hide Magisk Manager (Repackage) upgrades the version over the internet

I have my Samsung A30 (SM-A305F) rooted with magisk canery (87de0e7a) by flashing patched boot img via odin. Now, If i try to hide magisk with random package , it demands internet connection and install the latest version (9348c5ba). BUT i don't want to upgrade as the updated version has weird bug of rejecting SU automatically (with a very brief pop-up). I then need to ---> uninstall the repackaged app ---> Reboot ---> install 87de0e7a version ---> then it become functional again. I don't have TWRP installed. Re-flashing new patched boot requires wiping data. i don't want to do factory reset
Now I want to hide magisk as PUBG MOBILE might be crashing due to root detection. Please help me achieve solution:
(1) hide magisk manager without updating
(2) update magisk manager without that BUG of rejecting SU automatically

1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions and owner).
Edit: replace the package name above with the one your Manager uses.
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.

Note: i previously managed to hide it successfully when there was no newer version. It would just download the same version from the internet and repackage itself with random package name. But some days ago, i restored original manager and now i can't get it to hide.

Didgeridoohan said:
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions).
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Click to expand...
Click to collapse
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again

Shihabus Sakib Rad said:
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Click to expand...
Click to collapse
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.

Didgeridoohan said:
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Click to expand...
Click to collapse
yes with MiXplorer.
When Manager updated itself , i tried to update the magisk ( not the manager). But it bricked my phone as it won't start. i had to flash stock firmware via odin. It happened what i feared about. Now, i will try to patch boot img with new version.

UPDATE: I patched and flashed boot img using canary 290. after rebooting , this time there was not that Bug of rejecting SU automatically. Root was functional. But when it asked to do additional setups, it was stuck on setup operation forever and when i tried to hide manager, it showed "hiding magisk manager failed". so i uninstalled canary 290 and installed 7.5.1 (267) . This time additional setup was completed and rebooted automatically. But there was some problem with su access. so i uninstalled 7.5.1 (267) and installed canary 290. Root is now functional and it does not ask for additional setup anymore. (meaning setup was complete?). But still shows "hiding magisk manager failed" when try to hide manager. I don't know what is the problem . I was using canary 284 without any problem. PUBG mobile was runnig without problem. Now I am tired......

About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager

Didgeridoohan said:
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Click to expand...
Click to collapse
Disabling Play Protect Worked !!!! Thank you Sir :angel:

Magisk Manager shows "Modules" and "Superuser" grayed out

First, I hope this thread is in the right place and apologize if it is not.
I currently have the problem that the Magisk Manager shows the two categories "Superuser" and "Modules" grayed out at the bottom. In addition, it is also so that the settings of the manager is slimmed down (fewer functions than usual). For this I have 2 screenshots ready: (see attachment and sorry for the German language).
Root itself is still there though (the apps that ask for root still do).
But can imagine that this happened because of the Magisk Hide app. Because I had hid the manager under a different app name, then either accidentally deleted it or restored the original package (can't remember).
In any case, I have already tried to install the manager with an SD card with the TWRP (did not work) and to install Magisk Manager via the apps themselves (pressed install in the first screenshot). This has come the following error message:
Code:
- Target image: /dev/block/
- Device platform: arm64-v8a
- Installing: 24.1 (24100)
! Unable to check signature
! Installation failed
My current status is that this has already happened once with the manager - judging by the bug reports on Github. Can someone please explain me in simple steps how to get this fixed? Thanks!

Bump

JulianKlein said:
Bump
Click to expand...
Click to collapse
No need to bump, your post was only 7 posts down, and only one bump is permitted every 24 hours.
The issue is clear from your screenshots. You don't have root. On the Magisk screen, at the top under the Magisk section, if "Installed" shows "N/A", you do not have working root. Magisk is unable to load modules without root.

V0latyle said:
No need to bump, your post was only 7 posts down, and only one bump is permitted every 24 hours.
The issue is clear from your screenshots. You don't have root. On the Magisk screen, at the top under the Magisk section, if "Installed" shows "N/A", you do not have working root. Magisk is unable to load modules without root.
Click to expand...
Click to collapse
Sorry, didn't know that.
But I don't quite understand. Why should I have no root if apps like Lucky Patcher, Vanced Manager ask for root and I can verify these requests with the manager?

JulianKlein said:
Sorry, didn't know that.
But I don't quite understand. Why should I have no root if apps like Lucky Patcher, Vanced Manager ask for root and I can verify these requests with the manager?
Click to expand...
Click to collapse
I'm not sure. I think you can still manage root permissions if you don't have root but I'm not 100% on that.
I suggest re-rooting with the prescribed method for your device. On the Pixels, we just re-patch and flash the boot image.

i hace the same problem in sm a70, the apps request root acces and i press yes and work but if the same app need request more times for example unloking network , the request are send again and again and again

I just took the leap into Android 12 and we t through the process of patching the boot img and flashing it. I have the same issue as the op. I have patched, repatched, and flashed and reflashed at least 4 or 5 times now. No change.
Edit to note that I do in fact have root, regardless of what Magisk says (installed - N/A). Apps like AdAway have root access and are working properly.

I had the same problem on my (very) old J7 (2015).
Am on android 7, and was trying to update Magisk from v24.3 to v25.1
I had to completely remove Magisk, and restarted from scratch.
Flashed the v25.1 apk in TWRP.

Same problem with Magisk 52.2 on my LineageOS 19.1 (Android 12L) installed on GT-N8000 (Samsung Note 10.1). I already tried re-root, re-flash, re-install apk and nothing!

constrito said:
Same problem with Magisk 52.2 on my LineageOS 19.1 (Android 12L) installed on GT-N8000 (Samsung Note 10.1). I already tried re-root, re-flash, re-install apk and nothing!
Click to expand...
Click to collapse
Do you originally have magisk hidden as another app then install mm anew?

Nergal di Cuthah said:
Do you originally have magisk hidden as another app then install mm anew?
Click to expand...
Click to collapse
I'm not sure about it, but I tried a few versions of Magisk and none worked. I installed both boot.img and magisk.apk via TWRP. The app downloaded and installed by Android always forces an upgrade.

constrito said:
The app downloaded and installed by Android always forces an upgrade.
Click to expand...
Click to collapse
That's because you haveca newer boot than the magisk manager.
Let it upgrade
Then tap the uninstall button
Restore images
Then complete uninstall
Reboot
Install magisk
Reroot

Nergal di Cuthah said:
That's because you haveca newer boot than the magisk manager.
Let it upgrade
Then tap the uninstall button
Restore images
Then complete uninstall
Reboot
Install magisk
Reroot
Click to expand...
Click to collapse

I don't have an uninstall button. I put a print screen in the previous post.

Did you mean to post something if so you didn't
Not sure what to say about no uninstall but i guarantee that you have a double install. Look through your apps. Did you ever hide magisk with a different name, you've got to remember that at some time you did.

Nergal di Cuthah said:
Did you mean to post something if so you didn't
Click to expand...
Click to collapse
Sorry if there was some confusion, here is: https://forum.xda-developers.com/t/...nd-superuser-grayed-out.4409627/post-88379373.

constrito said:
Sorry if there was some confusion, here is: https://forum.xda-developers.com/t/...nd-superuser-grayed-out.4409627/post-88379373.
Click to expand...
Click to collapse
See my edit

Nergal di Cuthah said:
Did you mean to post something if so you didn't
Not sure what to say about no uninstall but i guarantee that you have a double install. Look through your apps. Did you ever hide magisk with a different name, you've got to remember that at some time you did.
Click to expand...
Click to collapse
I removed the Magisk via TWRP by flashing it with the uninstall.zip file. After installing the Magisk via flash with the Magisk.zip file and rebooting the tablet, I patched my boot.img, went back to TWRP, flashed the boot.img selecting the boot option and rebooted. I went back to the Magisk app and the same problem. I checked via
Code:
adb shell pm list packages | grep magisk
and it returns only
Code:
package:com.topjohnwu.magisk
it suggests I have only 1 app installed (none hidden).

Then I'm out of ideas sorry

Nergal di Cuthah said:
Then I'm out of ideas sorry
Click to expand...
Click to collapse
No problem and thank you.