Hi,
Im on latest .54 firmware with latest Sun kernel en Phh Duperuser.
How can I Replacing Phh Superuser with Magisk?
Tried it a few times. Downloaded the correct files.
Flash in TWRP the Magisk Zip. Installed the Magisk Manager.
But it shows that Magisk isn't installed.
What am I doing wrong?
Do I need to use a stock .54 boot.img?
Related
I'm trying use android pay on my rooted sm-n920t 6.0.1. I've successfully installed Magisk and phh SU. The feature within Magisk that hides root from safetynet isn't compatible with stock Samsung kernel. So what are some recommendations on which kernel would be best suited for a stock rom rooted with Magisk?
Sent from my SM-N920T 6.0.1 using Tapatalk
biggdevon said:
I'm trying use android pay on my rooted sm-n920t 6.0.1. I've successfully installed Magisk and phh SU. The feature within Magisk that hides root from safetynet isn't compatible with stock Samsung kernel. So what are some recommendations on which kernel would be best suited for a stock rom rooted with Magisk?
Sent from my SM-N920T 6.0.1 using Tapatalk
Click to expand...
Click to collapse
Hi, could you tell me how did you installed magisk on your n920t? which version of magisk did you use ? I'm trying to install magisk on my sm-n9200 6.0.1 with stock rom unrooted , but failed . I installed magisk manager and flashed Magisk-v11.1.zip on my n9200 with stock 6.0.1 rom ( unmodified) , but when I opened magisk manager , it said " magisk is not installed ", while the root function showed and worked correctly . I followed the instructions in magisk manager to download and install magisk . After installation, magisk manager said that magisk was installed , but after I rebooted my note5, it showed " magisk is not installed " again.
woyaojizhu8 said:
Hi, could you tell me how did you installed magisk on your n920t? which version of magisk did you use ? I'm trying to install magisk on my sm-n9200 6.0.1 with stock rom unrooted , but failed . I installed magisk manager and flashed Magisk-v11.1.zip on my n9200 with stock 6.0.1 rom ( unmodified) , but when I opened magisk manager , it said " magisk is not installed ", while the root function showed and worked correctly . I followed the instructions in magisk manager to download and install magisk . After installation, magisk manager said that magisk was installed , but after I rebooted my note5, it showed " magisk is not installed " again.
Click to expand...
Click to collapse
You said you're not rooted, how are you flashing the files? Custom recovery, Flashify, FlashFire?
I started from compete stock, fresh.
Flashed TWRP via Odin, booted to recovery
Flashed arter97's v22 kernel via TWRP, booted system
Waited for system to settle (10 min), rebooted to recovery
Flashed osm0sis unSU.zip (Google is your friend), stay in recovery
Wipe dalvik and cache, flash Magisk-v11.1.zip
Boot system.
Forgot to mention the post you quoted was from when I used v10.2. Now using v11.1 so there's no need to install anything from phh. And you'll need the Magisk Manager app from the Play store
biggdevon said:
You said you're not rooted, how are you flashing the files? Custom recovery, Flashify, FlashFire?
I started from compete stock, fresh.
Flashed TWRP via Odin, booted to recovery
Flashed arter97's v22 kernel via TWRP, booted system
Waited for system to settle (10 min), rebooted to recovery
Flashed osm0sis unSU.zip (Google is your friend), stay in recovery
Wipe dalvik and cache, flash Magisk-v11.1.zip
Boot system.
Forgot to mention the post you quoted was from when I used v10.2. Now using v11.1 so there's no need to install anything from phh. And you'll need the Magisk Manager app from the Play store
Click to expand...
Click to collapse
I started from compete stock, fresh too. I flashed twrp, installed magisk manager app , and then flashed Magisk-v11.1.zip using twrp.
woyaojizhu8 said:
I started from compete stock, fresh too. I flashed twrp, installed magisk manager app , and then flashed Magisk-v11.1.zip using twrp.
Click to expand...
Click to collapse
Not sure then. I know the stock Samsung kernel doesn't play well with Magisk so maybe try a custom kernel. Otherwise try reaching out and posting your logs on the main Magisk troubleshooting thread: https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
I am not able to root my Z5 E6653 running the new .160 build
I have already rooted it when Lollipop, Marshmallow and 7.0 was installed but this time it is pretty weird!
bootloader is unlocked of course!
I flashed the patched kernel and TWRP 3.1.1
then i flashed magisk v12 and as SU binaries I chose SuperSU v82...
after booting and opening the SuperSu app it wants me to grant root access for itself, it says "greant for SuperSu" and then the app freezes and keeps crashing :/ reinstalling did not help, is v82 not compatible with 7.1.1 sony rom?
What kernel do you flashed
jpl8910 said:
What kernel do you flashed
Click to expand...
Click to collapse
the patched .160 kernel for e6653. I reflashed the 7.1.1 ftf and wiped everything except data so my system and stuf are back to normal, flashed the kernel and recovery again and this time I only flashed magisk v12 without SuperSu v82
now root is working
it seems like magisk v12 in combination with supersu v82 does not work ^^
First supersu then Magisk, otherwise is wrong.
sceryavuz said:
First supersu then Magisk, otherwise is wrong.
Click to expand...
Click to collapse
Okey thanks
freaky2xd said:
the patched .160 kernel for e6653. I reflashed the 7.1.1 ftf and wiped everything except data so my system and stuf are back to normal, flashed the kernel and recovery again and this time I only flashed magisk v12 without SuperSu v82
now root is working
it seems like magisk v12 in combination with supersu v82 does not work ^^
Click to expand...
Click to collapse
sceryavuz said:
First supersu then Magisk, otherwise is wrong.
Click to expand...
Click to collapse
Magisk has root built-in, there is no reason to flash SuperSU if you've successfully flashed Magisk. You either flash Magisk OR SuperSU, not both.
Devo7v said:
Magisk has root built-in, there is no reason to flash SuperSU if you've successfully flashed Magisk. You either flash Magisk OR SuperSU, not both.
Click to expand...
Click to collapse
Not for noob. If you want to use SuperSU with Magisk Modules, then you have to flash both with this order(SuperSU, Magisk).
Already mentioned on my thread..
Magisk is a module manager like Xposed. If you dont know..
sceryavuz said:
Not for noob. If you want to use SuperSU with Magisk Modules, then you have to flash both with this order(SuperSU, Magisk).
Already mentioned on my thread..
Magisk is a module manager like Xposed. If you dont know..
Click to expand...
Click to collapse
Exactly
At the moment I am using magisk v12 only though
root fail
freaky2xd said:
the patched .160 kernel for e6653. I reflashed the 7.1.1 ftf and wiped everything except data so my system and stuf are back to normal, flashed the kernel and recovery again and this time I only flashed magisk v12 without SuperSu v82
now root is working
it seems like magisk v12 in combination with supersu v82 does not work ^^
Click to expand...
Click to collapse
hello
i have xperia z5 running version 7.1.1 i have tried alot to root it but i couldnt please help me
thanks
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.
Hi, I am trying to flash magisk. I patched my boot.img and flashed it via fastboot. But it didn't work, Magisk app was still showing as not installed. Then, I tried the Recovery method (flashing the magisk zip), it tells that magisk patched to the boot.img file but this method didn't work too. But it said magisk patched to the boot.img. What can cause it?
My rom: Xiaomi.eu 21.12.8, Android 12
My device: Xiaomi Mi 10T (apollo)
CaganAgabey said:
Hi, I am trying to flash magisk. I patched my boot.img and flashed it via fastboot. But it didn't work, Magisk app was still showing as not installed. Then, I tried the Recovery method (flashing the magisk zip), it tells that magisk patched to the boot.img file but this method didn't work too. But it said magisk patched to the boot.img. What can cause it?
My rom: Xiaomi.eu 21.12.8, Android 12
My device: Xiaomi Mi 10T (apollo)
Click to expand...
Click to collapse
Flashing the Magisk patched boot.img only installs the necessary binaries to gain root access, you have to manually install the Magisk Manager app to take advantage of the binaries that it installs. Flashing the patched boot.img does not automatically install the Magisk app on your device as part of the flashing process.
Just updated from 24.3 to 25.1, everything seems fine.
First update of the manager, no problem. In manager tried to update magisk from 24.3 to 25.1. No errors in the log, but my phone (Mi9T Pro) didn't get past the Miui logo. Flashed 24.3 in Recovery again.
Any thoughts on how to update?
Edit: Solved. Dowloaded zip and flashed in recovery. All's well.
I have problem - I followed guide (https://www.xda-developers.com/how-to-install-magisk/)
On my Xiaomi A2 (jasmine_sprout) I've extracted boot.img, patched with app and flashed boot from PC and after reboot I have Magisk app version 1.0. After running it it want's to upgrade but after downloading and confirming upgrade it upgrades, icon is changed to magisk app and then it is fall backed to basic version 1.0. Tried to adb install v25.1 from pc and it says:
adb: failed to install Magisk-25.1(25100).apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.topjohnwu.magisk signatures do not match previously installed version; ignoring!]
After manual unistalling remaining v1.0 new can be installed but when executed it is auto degraded to version 1.0
Could somebody give me a clue what happened?
d3im said:
extracted boot.img, patched with app
Click to expand...
Click to collapse
Did you use magisk 25.1 to patch boot.img? And are you on Android 12?
I'm on android 11 And I've used magisk version 25.1 to patch boot.img
If you have twrp, try flash magisk in twrp.
donkeyman1234 said:
Just updated from 24.3 to 25.1, everything seems fine.
Click to expand...
Click to collapse
Same here
OK, just flashed new custom ROM (Android 12.1), then Magisk 25.1 zip via twrp and finally Magisk apk app and it just works fine
Glad it works.