Installed Magisk 19.3 using TWRP, seems not installed in Magisk Manager. - Magisk

Hello,
I flashed a stock ROM on my Samsung Galaxy Tab S3 running Android 7.0.
Then I installed TWRP, and with that Magisk 19.3. All were installed successful, however after rebooting there was no Magisk Manager app, so I installed this myself.
When opening the Magisk Manager app it shows that Magisk has not been installed.. how can I fix this?
I've been trying for 10 hours now, I really need help.
Before flashing the ROM I had TWRP installed with SuperSU.

NeroDePero said:
Hello,
I flashed a stock ROM on my Samsung Galaxy Tab S3 running Android 7.0.
Then I installed TWRP, and with that Magisk 19.3. All were installed successful, however after rebooting there was no Magisk Manager app, so I installed this myself.
When opening the Magisk Manager app it shows that Magisk has not been installed.. how can I fix this?
I've been trying for 10 hours now, I really need help.
Before flashing the ROM I had TWRP installed with SuperSU.
Click to expand...
Click to collapse
1. Uninstall Super SU
2. Uninstall Magisk from TWRP (using uninstall.zip)
3. Install Magisk.zip latest version in TWRP
4. Install Magisk Manager latest version using APK
Remember to use both latest versions of Magisk (zip and apk).
It should work for you.
Sent from my SM-N960F via Tapatalk

zencooler said:
1. Uninstall Super SU
2. Uninstall Magisk from TWRP (using uninstall.zip)
3. Install Magisk.zip latest version in TWRP
4. Install Magisk Manager latest version using APK
Remember to use both latest versions of Magisk (zip and apk).
It should work for you.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
The thing is, I did a full clean stock ROM install and there is no SuperSu app left on my device.
If I download the SuperSu APK now it says I don't have ROOT access and therefore I cannot uninstall SuperSu using the APK.
I have used Root Checker Basis (app) to check if there is a ROOT available, but it says ROOT access is not properly installed on this device.
Is it still possible for SuperSu to be installed on my device while I cannot see or find it? Even after a clean install?
Also, I believe 19.3 is the latest version of Magisk. I also tried 19.2, but I am having the same problem with that version.

NeroDePero said:
The thing is, I did a full clean stock ROM install and there is no SuperSu app left on my device.
If I download the SuperSu APK now it says I don't have ROOT access and therefore I cannot uninstall SuperSu using the APK.
I have used Root Checker Basis (app) to check if there is a ROOT available, but it says ROOT access is not properly installed on this device.
Is it still possible for SuperSu to be installed on my device while I cannot see or find it? Even after a clean install?
Also, I believe 19.3 is the latest version of Magisk. I also tried 19.2, but I am having the same problem with that version.
Click to expand...
Click to collapse
I don't know what the smartphone you have but the best way is to get boot.img from stock firmware and then patch it via Magisk Manager (you can install it even if you don't have root). Then after boot.img is patched you can flash it instead of the standard boot.img (any method you are doing it now).
BTW: the latest version of Magisk is 19.4. Check it on Magisk repository.
Sent from my SM-N960F via Tapatalk

zencooler said:
I don't know what the smartphone you have but the best way is to get boot.img from stock firmware and then patch it via Magisk Manager (you can install it even if you don't have root). Then after boot.img is patched you can flash it instead of the standard boot.img (any method you are doing it now).
BTW: the latest version of Magisk is 19.4. Check it on Magisk repository.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
I am using a Samsung Galaxy Tab S3 (T825). I used a stock firmware from SamMobile (which exists of 5 times an .tar.md5 file) and flashed it on my device using Odin.
[EDIT] So here is what I did. Made a back-up using TWRP, and used that boot.img to patch in Magisk Manager.
Now I have a patched IMG file. But when I want to install it using TWRP I have to pick a partition and I am not sure which one to pick.
[EDIT] I tried installing it, and it was successful, yet shows the Magisk manager app that there is no ROOT available.
I guess I just need to start from the very beginning over again. Can you help me with that?
I have stock firmware .zip for my T825 from SamMobile which I can install using Odin.
I also have a working TWRP .zip file that works fine with that firmware on my device.
Other than that I'll need guidance because I keep screwing up :')
Your help is much appreciated

I did a factory reset, flashed TWRP, and installed Magisk using TWRP. After rebooting there was no Magisk Manager app (but it did install a TWRP app).
I installed the Manager app with a downloaded .apk (latest version) and it shows that Magisk is not installed.
So, I want to try patching my .img file using the manager app. The only problem is that I do not have an .img file, as I used . md5 files.
Can I make a back-up with TWRP and use the .img file from there?

Related

After installing latest firmware Samsung S8 fault during installing magisk again

Hi there,
I had Magisk and the Magisk manager on my S8 but after installing the latest firmware for my S8 I can not install the Magisk.zip anymore. SU and TWRP are working fine though. Does anyone knows how get magisk again on my Phone?
I found it here: https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
With SuperSU, most of the times you can simply use the full unroot option in the SuperSU app and let it restore your stock boot image, alternatively use the full unroot option and then flash the stock boot image before installing Magisk.

Magisk manager is installed, magisk itself isn't!

I have huawei mediapad AGS-l09
Installed Magisk manager via Patched boot img
Can't flash anything through TWRP
(Always gives unable to mount '/usbotg despite not using usbotg at all!)
Bootloader is Unlocked ... root is working ... but Magisk itself? I can't install!
Tried to install Magisk via Direct install from within the Manager > Crashes.
Tried doin' it using Flashfire > Black screen to no Avail (waited for 1 Hour)
Using Latest version.
Any help is appreciated.
Flash another recovery then?
Neil_Armstrong_ said:
Flash another recovery then?
Click to expand...
Click to collapse
Meaning another version of TWRP? from what I can tell, there isn't, for that specific device.
It's 3.1.1 Russian version I got from 4pda
Or you meant another recovery entirely?
*Bump*
How can I know which TWRP version suits my device?
Ospider said:
I have huawei mediapad AGS-l09
Installed Magisk manager via Patched boot img
Can't flash anything through TWRP
(Always gives unable to mount '/usbotg despite not using usbotg at all!)
Bootloader is Unlocked ... root is working ... but Magisk itself? I can't install!
Tried to install Magisk via Direct install from within the Manager > Crashes.
Tried doin' it using Flashfire > Black screen to no Avail (waited for 1 Hour)
Using Latest version.
Any help is appreciated.
Click to expand...
Click to collapse
How is root working if magisk isn't? You have another root? Have you mounted data in twrp?

[HELP] Unable to flash magisk zip file nor install the manager apk file on MiX2S

Hi There,
I met some issues when I tried to flash the Magisk zip to my MIX2S.
Phone MIX 2S
OS:MIUI 10.3 by xiaomi.eu 9.2.15
Recovery:TWRP
Situation:
Part 1, at the beginning, I flashed the xiaomi.eu rom to my MIX 2S, and then flashed magisk zip file, everything works well except sometime the saftynet check will fail. After I check the post of saftypatcher , I changed to ianmacd mod. Everything seems fine until then. I need to re-flash the magisk official zip every time after I update my phone, and than update magisk to ianmacd mod in magisk manager.
Part 2,
Today I updated my rom to MIUI 10.3 by xiaomi.eu 9.2.22, I then re-flash the official magisk zip as usual, and then updated to ianmacd mod in magisk manager. I re-boot the phone, then it reboot to recovery when I tried to input my pin. Reboot again, still went to the recovery. So I use ianmacd uninstaller to uninstall the magisk, and tried to flash the official zip. The phone booted into the system, but when I open the magisk manger, it shows that mangisk is not installed. I reflashed again, still the same issue.
I uninstalled the manger, tried to install the offical manger apk file, told the app was not installed.
I downgrade my system to MIUI 10.3 by xiaomi.eu 9.2.15, reflash the offical 18.1 zip file, reboot, no magisk manger on my phone, tried to install the apk file, still failed.
I boot into the recovery to uninstall and install again, still no manger in the system. Now I'm totally lost.
Part 3, some of my app tells me that my phone is rooted, so I guess the magisk is in somewhere of my system?
Attached is the recovery log.
Thank you in advance. Sorry for my English.
You've been mixing Managers with different signatures (the official with unofficial)...
Try this:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager
Didgeridoohan said:
You've been mixing Managers with different signatures (the official with unofficial)...
Try this:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager
Click to expand...
Click to collapse
Thank you very much for the help. It fixed my issue.
Now I need to investigate the "boot to recovery" issue.

How to update pre-installed Magisk im custom rom

Hello
Recently i changed stock ROM on my HTC 10 Evo to debloated ROM with Magisk pre-installed
https://forum.xda-developers.com/bolt/development/rom-stock-ish-7-0-nougat-debloated-t3519195
Code:
Stock 7.0 Magisk Debloated/Deodexed + Mods
Whats Included:
Magisk Version 13.xx <- Passes Safety-net As of 8/19/17
Magisk Manager couldn't check updates or check safety net test so i decised to update it.
Downloader 7.3.1 Magisk Manager but couldn't update app so i uninstalled it and then tried to install the fresh one.
It ended up that the old one is gone and new downloaded app hangs while i try to i install it.
Could anyone tell me what to do?
Should i run uninstaller.zip in recovery and then install both Magisk and Magisk Manager?
I couldn't find updating guide for pre-installed Magisk anywhere...
pasiasty29 said:
Hello
Recently i changed stock ROM on my HTC 10 Evo to debloated ROM with Magisk pre-installed
https://forum.xda-developers.com/bolt/development/rom-stock-ish-7-0-nougat-debloated-t3519195
Code:
Stock 7.0 Magisk Debloated/Deodexed + Mods
Whats Included:
Magisk Version 13.xx <- Passes Safety-net As of 8/19/17
Magisk Manager couldn't check updates or check safety net test so i decised to update it.
Downloader 7.3.1 Magisk Manager but couldn't update app so i uninstalled it and then tried to install the fresh one.
It ended up that the old one is gone and new downloaded app hangs while i try to i install it.
Could anyone tell me what to do?
Should i run uninstaller.zip in recovery and then install both Magisk and Magisk Manager?
I couldn't find updating guide for pre-installed Magisk anywhere...
Click to expand...
Click to collapse
Preinstallation doesn't change general rules. It's like the manual patching the bootloader so do exactely what you wrote. Uninstall it in custom recovery via uninstall.zip and then install any version of Magisk you want using the magisk.zip and manager.apk.
Sent from my SM-N960F via Tapatalk
Thank you for help. Just wanted to make sure that I won't damage my rom. The uninstallation and then installation of newest Magisk went perfectly fine and the updated Magisk Manager were already in the drawer.
Internet connection in Magisk Manager is back and safety net test is passed.

Magisk not showing root after patching boot

I just patched boot.img using latest ver of magisk and flashed to device Samsung m01 core (android 10(Q) go edition)
Magisk simply showing all done!
But after flashing magisk_patched_boot
Application is not detecting root i ve repeated steps but no use still it showing device not rooted
Can anyone help me.
I ve tried same procedure on other devices it worked perfectly but i don't know what happened this time...
Problem solved. The hidden magisk just renamed it to magisk...
What?
Renaming magisk solves problem?
Did u mean rename apk file
My problem is magisk not detecting rooted boot.img or recovery.img that i ve flashed to my device
Wait, what.. I thought I replied to another post. Sorry
MasterGmind said:
I just patched boot.img using latest ver of magisk and flashed to device Samsung m01 core (android 10(Q) go edition)
Magisk simply showing all done!
But after flashing magisk_patched_boot
Application is not detecting root i ve repeated steps but no use still it showing device not rooted
Can anyone help me.
I ve tried same procedure on other devices it worked perfectly but i don't know what happened this time...
Click to expand...
Click to collapse
Which magisk version?
Selvam_2568 said:
Which magisk version?
Click to expand...
Click to collapse
Here is the solution...(It will work for all magisk versions)
1.Uninstall magisk manager.
2.Reboot to twrp recovery. Then Advanced > File manager > /data/adb/
3.Delete the "adb" folder which present inside the /data.
4.Restore stock boot.img
5.Now flash magisk via recovery...it will work now.

Categories

Resources