(Resolved) Lenovo Tab 4 Successfully Roots, Magisk Manager doesn't see magisk running.

[jericotyler]

Factory reset the device, sideloaded mtk-easy-su and Magisk Manager 7.1.1, both installed and easy-su says it's gotten root. M.M. doesn't show that magisk is "installed" and root checker doesn't see it as rooted either.

[jericotyler]

Processor is an MT8163 and it's the 1GB version of the Lenovo Tab4 8"

[JunioJsv]

Try another version of Magisk Manager

[jericotyler]

Tried versions 5.04 up to the latest (7.5.1) and none of them seemed to see magisk running. Seeing as how most of the older versions just crash I don't know if trying to go older than that is a worthwhile endeavor.

[JunioJsv]

Hi dude, try again on latest verdion with magisk v18.1 asset

[jericotyler]

• Uninstalled Magisk Manager and Mtk-Easy-Su
• Installed the new version of Easy-su and MM 7.1.1
• Clicked install on v18.1 in the app, rebooted when it asked me to
• Opened the app again and clicked activate, it asked me to reboot.
• After the second reboot it ran and gave me this log after flashing "success"

param1: 0x3000, param2: 0x18040, type: 2
Building symbol table
kallsyms_addresses pa 0x40b32e00
kallsyms_num_syms 51340, addr_count 51340
kallsyms_names pa 0x40b97400, size 630756
kallsyms_markers pa 0x40c31400
kallsyms_token_table pa 0x40c31b00
kallsyms_token_index pa 0x40c31f00
Patching credentials
Parsing current_is_single_threaded
ffffffc0003433e4+50: ADRP x0, 0xffffffc000e1a000
ffffffc0003433e4+54: ADD xd, x0, 2576
init_task VA: 0xffffffc000e1aa10
Potential list_head tasks at offset 0x340
comm swapper/0 at offset 0x5c8
Found own task_struct at node 1
cred VA: 0xffffffc00c6cbe80
Parsing avc_denied
ffffffc0002e3208+24: ADRP x0, 0xffffffc000f45000
ffffffc0002e3208+28: LDR [x0, 3948]
selinux_enforcing VA: 0xffffffc000f45f6c
Setting selinux_enforcing
Switched selinux to permissive
/mnt/expand/dd54e66f-957b-4534-956c-8235ce5c3d11/user/0/juniojsv.mtk.easy.su/files
armv8l machine
starting /system/bin/sh
UID: 0 cap: 3fffffffff selinux: permissive
source type magisk does not exist
Error in: allow magisk (null) (null) (null)
client: launching new main daemon process
exit value 0 assets-r20

[jericotyler]

Decided to poke around in the shell:

TB-8304F1:/ $ ps | grep magisk
1|TB-8304F1:/ $ ps | grep magisk
root 3902 1 20016 1744 __skb_recv 0000000000 S magiskd
root 3921 1 20664 948 __skb_recv 0000000000 S magisklogd
root 3954 3921 16212 1664 __skb_recv 0000000000 S /sbin/.magisk/mirror/system/bin/logcat
TB-8304F1:/ $ su
Permission denied

Seems to actually start magisk, yet the manager still doesn't like it.

[JunioJsv]

mtk-easy-su/app/src/main/java/juniojsv/mtk/easy/su/AssetsManager.kt

Lines 99 to 103 in d84b2c7

	shell.exec(
	"./mtk-su -c rm -r /data/adb/",
	null,
	directory
	).waitFor()

I'm almost sure that the error is in this line of code, this line erases the residues of the magisk so that a new daemon is started normally, but without a device it doesn't seem to have this folder /data/ like most, do you have any suggestions?

[JunioJsv]

you have to find this folder on your device and delete these files

[JunioJsv]

I think it's in the folder /mnt/expand/dd54e66f-957b-4534-956c-8235ce5c3d11/adb

[jericotyler]

It was in the root level directory as /data/adb deleted the folder, rebooted, and ran easy-su.
Got the same log output and results as before.

[jericotyler]

Soooooooo... I just learned if you have an SD card android installs new apps there by default.
After moving both magisk and easy root to the internal storage everything works!

[jericotyler]

Lenovo Tab4 8" (TB-8404F1) with the MT8163 confirmed to work.

[jericotyler]

I apologize for the run around, It's been 5 years since I've used android extensively and I forgot I should check for that. Would it be possible to add something to check that both Magisk Manager and MTK-Easy-Su are installed in internal storage? Just to solve any future headaches?

[JunioJsv]

Nice!

[3ndlessly]

Factory reset the device, sideloaded mtk-easy-su and Magisk Manager 7.1.1, both installed and easy-su says it's gotten root. M.M. doesn't show that magisk is "installed" and root checker doesn't see it as rooted either.

Open " magisk root granter" and granter in manually