Database Develop

a question about flashing magisk

I have the latest hydrogen OS and unlocked bootloader , and i want to root my phone but i just wants to know if theres any other files I need to flash other than magisk.zip

Nope, just flash the latest magisk zip and it's done. But yes, you also have to install the Magisk Manager when you boot up after flashing the zip.

I installed the latest one that came out today and my phone took a crap! Phone became very laggy and would freeze and sometimes not even detect root. I had to restore my phone back to last weeks version.

equlizer said:
I installed the latest one that came out today and my phone took a crap! Phone became very laggy and would freeze and sometimes not even detect root. I had to restore my phone back to last weeks version.
Click to expand...
Click to collapse
Hm... Absolutely no issues on my OP3T, OOS 4.1.6 and Franco Kernel r25 with Magisk v13.1. Maybe you have a module causing issues (long shot, I know)?

No issues here with Open Beta 10, Stock Kernel, Magisk 13.1 and Manager 5.0.4.
Root is working, passes SafetyNet with all modules activated and properly hide root from my Banking App. All good!

Akhayev said:
I have the latest hydrogen OS and unlocked bootloader , and i want to root my phone but i just wants to know if theres any other files I need to flash other than magisk.zip
Click to expand...
Click to collapse
Just Simple flash the Magisk v13.1 and install the latest magisk manager v5.0.4.

I feel you should flash magisk immediately, while flashing the ROM through custom recovery. Install magisk manager after first boot.
You can do a dirty flash without formatting anything to get rooted.
Sent from my OnePlus 3T using Tapatalk

How do I save my root after flashing miui10 beta Rom?

I am using Redmi 4a . Rooted with magisk and recovery is Twrp. It. I don't want to lose root access after update. tried FlashFire but it crashes when I open it .
Help appreciated !

I'm using miui10 (beta) developper Rom (miui_HM4AGlobal_8.10.25_d36c3e7df5_7.1.zip) and it is true that a big update (mean when it's the entire ROM) replaces twrp and crashes root.
You just have to install again twrp with fastboot method in order to flash SuperSu (the one i use) in order to retrieve root.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Hi, when used to use MIUI i installed pitchblack recovery and after the miui update it didn´t dissapeared so there is no need to always flash the recovery but the magisk fil you have to install again because the update flashs the stock boot img.

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

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?

Downgrade to 20.4 without custom recovery

I have a car Android device in which I am able to install magisk extracting boot.img and then patching it. I was having some problems and have reset, and now I am having some issues:
I flashed latest magisk and got bootloop, so I managed to install 20.2 version and it gives superuser access, but I can't install no modules (it seems to install them but they are not there after a reboot).
I think before the reset I had 20.4 installed, but I don't know how to update my version to 20.4, it always offers me latest version, which ends in bootloop. I don't have access to any custom recovery, so I think the only way to make it work is to update through a custom channel pointed to 20.4, but can't figure out how to set it.
Any help would be appreciated.

Ok, I realized a simpler way to do it: I downloaded 20.4 zip and flashed it through magisk. Now it works perfectly, but when I use Viper4android together with sygic, sygic crashes.

Root not working after flashing Magisk patched boot.img on Samsung GT-I9300

It's a bit of an older phone but I cannot get root properly working on my Samsung GT-I9300 using Magisk. I need Magisk to hopefully get some banking apps working again on my LineageOS 17.1 custom ROM. I downloaded Magisk v25.2 (Latest) from github, patched the boot.img from the installed ROM: lineage-17.1-20200717-UNOFFICIAL-i9300.zip, all with no errors.
Instead of using fastboot I renamed the patched magisk_patched-25200_eb1Em.img to boot.img and created a tar file from it so I can flash it with Odin3 v3.14.1.exe (AP checkbox) as I did for the twrp recovery image. After this some signs of root access are visible. Root Checker Pro even shows my device as rooted. Still it says that the su binaries are missing and Magisk keeps showing as not installed. I even tried CF-Auto-Root-m0-m0xx-gti9300.tar through odin and/or flash UPDATE-SuperSU-v2.46.zip through the installed twrp recovery but the results stay the same.
Wat can I do more to get it working?