Database Info

Magisk does not root my phone

Please help me!!
So I runned the magisk zip in twrp but in magisk maniger it only says that magisk is installed, not that its rooted
If you know something about this or can help me, please react.
Thanks

Yes it dosnt root thats why i downgraded to maarshmallow...with original super SU...magisk is waste of space and time for nougat

Rubster477 said:
Please help me!!
So I runned the magisk zip in twrp but in magisk maniger it only says that magisk is installed, not that its rooted
If you know something about this or can help me, please react.
Thanks
Click to expand...
Click to collapse
Go to the magisk thread and make sure you have the latest magisk v12.0 zip... also download the uninstaller zip.
Once in awhile with samsung devices you'll lose root with magisk. It helps if you boot into twrp and flash the uninstaller zip (might be best to backup first... Beware, if you try to boot phone after running the uninstaller zip, you will more than likely get bootloop...) Then without rebooting the phone, flash magisk v12 zip.
It should work. Its also good to wipe davlik every so often.

Magisk on Note Edge

Hi Folks
I searched for rooting the new Galaxy S8 (I might get one) and came across an app called Magisk
to root the device and it sounds pretty good.
My question is, would this work on the Note Edge, (in my case the G variant)with 6.0.1 stock rom...

hingerl said:
Hi Folks
I searched for rooting the new Galaxy S8 (I might get one) and came across an app called Magisk
to root the device and it sounds pretty good.
My question is, would this work on the Note Edge, (in my case the G variant)with 6.0.1 stock rom...
Click to expand...
Click to collapse
Yes, it will work on all Android phones. Nowadays, Magisk became a famous root because it has cool features. The best feature of it is that you can hide root for specific games or programs like banking app wich can't open while the phone is rooted. I will write quick and simple below for how to flash Magisk.
1. If your phone is rooted flash unSU.zip
2. Flash Magisk v12.0
3. Wipe Dalvik/cache
4. Reboot and wait to update the programs about 10-15mins
5. When the phone is booted install the MagiskManager v4.3.3. which is not available in PlayStore anymore
6. Open Magisk and go to settings
7. Enable BusyBox and Magisk Hide (This will pass the SafetyNet security)
8. Go back tap to check SafetyNet (It will be green coloured) and you're done
Now u have Magisk with a rooted phone and a lot of features inside

Sweet...Thanks a million... I think I start from scratch anyway with flashing a stock rom...
so, just to be safe, I flash stock (let it boot and make the initial setup)
then flash recovery, and there I flash the Magisk file and at last install the
Magisk app and thats it... or is there something else, I've seen ont the S8 tutorial
that there is another file to be flashed in recovery... but I assume this has something to do with security features from Android 7/Samsung...

So, i have a Note Edge SN 915G stock ROM 6.0.1
Tried to flash in ODIN custom recovery TWRP so I can flash Magisk from recovery. It didn't work, because the reboot restores the stock recovery back.
Tried again by not rebooting and removing the battery after flashing in ODIN the TWRP. The custom recovery remained flashed, this time, but it didn't open: recovery is not seandroid enforcing error.
Flashed CWM second time with ODIN, removed battery, boot into recovery (CWM worked and opened successfully).
Flashed Magisk zip from the custom recovery, but after reboot ended into boot loop, soft brick with error Set Warranty Bit: kernel.
Reflashed stock firmware with ODIN, back to normal.
Any adivce on how to flash that darn Magisk properly?
Thank you.
PS: I did not wipe davlik after flashing Magisk, though. Could this be it?

ufukan said:
Yes, it will work on all Android phones. Nowadays, Magisk became a famous root because it has cool features. The best feature of it is that you can hide root for specific games or programs like banking app wich can't open while the phone is rooted. I will write quick and simple below for how to flash Magisk.
1. If your phone is rooted flash unSU.zip
2. Flash Magisk v12.0
3. Wipe Dalvik/cache
4. Reboot and wait to update the programs about 10-15mins
5. When the phone is booted install the MagiskManager v4.3.3. which is not available in PlayStore anymore
6. Open Magisk and go to settings
7. Enable BusyBox and Magisk Hide (This will pass the SafetyNet security)
8. Go back tap to check SafetyNet (It will be green coloured) and you're done
Now u have Magisk with a rooted phone and a lot of features inside
Click to expand...
Click to collapse
Thanks a lot for the tips I have a question: After installing Magisk, I want to get Xposed installed, but it bootloops me at the Samsung logo every time, with the zip sdk23 of xposed by the official thread of rovo89 (thanks for his great work), and also with the xposed 23 at Magisk Manager. Did you get it systemless Xposed to work with Magisk in our Note Edge?

telefon notum kenar n915f magisk'in en son sürümünü indirmek istiyorum ancak indirmek istediğim sürümü indiremiyorum v 22.0

I want to download the latest version of magisk but I cannot download the version I want to download is v 22.0

Bootloop with OOS 9.0.3 on OP6 when magisk v18 is installed

Installation steps are as follow when updating from 9.0.2 to 9.0.3.
Flashed full zip from bluspark twrp
Immediately flash bluspark twrp zip after that
Reboot into recovery
Flashed Magisk v18 zip (Also tried v17.3 zip)
Reboot system
After that, boot animation is shown and followed by Shutting down dialog with my wallpaper behind it, then rebooted into TWRP itself. I cannot reboot into system until I flash full zip again, but I lost my root now. Above steps were used when I update from older version to 9.0.2 and it was ok at that time. Bluspark latest stable (3.2.3) was used. Any idea how to fix please? Thanks.

xtartrackR said:
Installation steps are as follow when updating from 9.0.2 to 9.0.3.
Flashed full zip from bluspark twrp
Immediately flash bluspark twrp zip after that
Reboot into recovery
Flashed Magisk v18 zip (Also tried v17.3 zip)
Reboot system
After that, boot animation is shown and followed by Shutting down dialog with my wallpaper behind it, then rebooted into TWRP itself. I cannot reboot into system until I flash full zip again, but I lost my root now. Above steps were used when I update from older version to 9.0.2 and it was ok at that time. Bluspark latest stable (3.2.3) was used. Any idea how to fix please? Thanks.
Click to expand...
Click to collapse
flash magisk uninstaller, then reinstall magisk v18 and add one module at a time to understand which one causes bootloop

It worked. Thank you!

Just a heads up next upgrade: disable all (except ROMs maybe) magisk mods, also disable substratum themes before updates. They can make your phone bootloop or system UI crash. Glad it works fine now

For me, flashing magisk uninstall and reinstalling v18 still didn't work. I had to install beta version 17.3 after flashing the uninstall, then I installed magisk manager when it successfully booted and finally updated to v18 through the manager. Not sure why v18 wouldn't work even after flashing magisk uninstall, but 17.3 worked.

I also had this problem on a fresh OS install. Had to install:
Magisk 17 then
Magisk 18 then
Magisk 19
This is a crazy bug

Sepero said:
I also had this problem on a fresh OS install. Had to install:
Magisk 17 then
Magisk 18 then
Magisk 19
This is a crazy bug
Click to expand...
Click to collapse
Have you tried magisk uninstaller and fresh start without any module? In my case one of my custom made module was causing problem because i didn't update it to latest template. Try one module at a time to find the culprit.

You need to disable all magisk modules before doing system update, otherwise it goes in auto shutdown and then you need to flash magisk uninstaller and then re-flash magisk
And remember to remove pin/password lock too

OFFTOPIC:
I have 9.0.3 + TWRP. What are exactly steps do nuke, clean, and reinstall 9.0.3? Need info about correct order and options on Format on TWRP.
Thank you.

Mord0rr said:
OFFTOPIC:
I have 9.0.3 + TWRP. What are exactly steps do nuke, clean, and reinstall 9.0.3? Need info about correct order and options on Format on TWRP.
Thank you.
Click to expand...
Click to collapse
Format DATA from TWRP then boot to system once and when it's ready you can reboot to twrp to install magisk if you want

Unable to Install/Flash Magisk Modules

Hey all,
I am rooted with Magisk 17.3 on global hardware and global ROM stock MIUI 10.2.2.0, but I cannot install any Magisk modules or flash Magisk ZIPs in TWRP. I know root works because I've edited system files and allowed a few apps root permissions. But when I try to install something with Magisk Manager (6.1.0 since 7.0.0 doesn't work < v18) I get this error: /data/adb/magisk_merge.img mount failed... abort or it tells me Magisk 17.x+ isn't installed. (I've tried the Magisk Mod Uninstaller, Youtube Vanced, and LKT). When I try to flash a Magisk ZIP in TWRP it gives me Error: 1
I did some searching and some people were getting this due to their filesystem being formatted as f2fs in the past, but I verified that the Mi Mix 3 uses EXT4 using DiskInfo.
Did I miss something during the rooting process? I unlocked the bootloader, flashed TWRP in fastboot, flashed Magisk 17.3 in TWRP, and verified root was achieved with Rootchecker. The Magisk Manager app also says it's installed and passes SafetyNet. Anyone have any ideas?

Do you use a custom kernel?
Try the latest Magisk canary build and see if that works

JetzNicht said:
Do you use a custom kernel?
Try the latest Magisk canary build and see if that works
Click to expand...
Click to collapse
No it is the stock kernel that came with the MIUI 10.2.2.0 global build. Should I be using one?
Quick update: I am able to install some modules now by downloading them in Magisk, then booting to TWRP and flashing the ZIP there. I was able to get Magisk Mod Uninstaller (mm) and LKT to run for example using this method. YouTube Vanced still gives me the Error: 1 when I do this however.

The try a custom kernel, had the same problems with any modifications to the system with stock kernel.
As far as I know there are only two kernels atm, friendly fire and androplus.

Accidentally Soft Bricked OP6; Recovered But Cannot Re-Install Magisk

Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY

If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815

tvteja said:
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Click to expand...
Click to collapse
Thank you so much for your suggestion, and reply. Magisk and TWRP were up to date (the latest releases); Magisk v20.1, and TWRP 3.3.1.2 ("Enchilada"). My device is a OnePlus 6 running Android 9, last updated August 1st of this year, "ONEPLUS A6003_22_190911"
I will try your suggestion and respond as soon as possible. If there is anything else you need to know, ask. I am new to the concept of forums so I've been kinda flopping around like a fish out of water. :laugh:

Marmalade_Shaws said:
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
Click to expand...
Click to collapse
tvteja said:
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Click to expand...
Click to collapse
Hello, just wanted to update you. I am happy to report your suggestion worked. Sadly I still lost my data, but that's alright; all the important bits were already backed up. Just lost the home screen layout and some application settings. All the same, I am now successfully running my rooted device and couldn't be happier! Thanks! :laugh::good:

Marmalade_Shaws said:
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
Click to expand...
Click to collapse
Hey, I'm in a similar situation you were in and I'm stuck in a bootloop after I flashed/installed busybox from magisk repo, I wanted viper 4android as well and while installing viper it said that I'd need busybox. Soon after I install busy box from magisk I'm in this bootloop, i have access to twrp luckily and i tried deleting this busybox and viper 4android module from twrp file manager but still I'm in a boot loop, can you guide me on how you managed to get out of this bootloop?? Thanks