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.
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
hey guys im thinking of installing magisk on shield k1, its running the latest firmware with twrp installed and ive got a custom kernel too, what do i have to do get magisk installed?
That's easy. Just like flashing another root zip, like SuperSU. Just put the zip on the phone. Boot TWRP, select "Install", and pick the zip. Reboot and you are rooted with Magisk! You should have an app installed "Magisk Manager". Open the app, to access the various Magisk functions.
If you are already rooted with SuperSU (you haven't stated), then you will need to unroot, before flashing Magisk. Use the xda search function, for the "unsu" script.
Does this also work on Lollipop?
im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS USING MAGISK UNINSTALLER basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know
sidenote:this supersu does work with magisk not installed and definately keeps root
(stock boot.img is in initial zip for custom rom) select intall imgs in twrp and flash the boot partition as needed)
ALSO YOU CAN ALWAYS DIRTY FLASH CUSTOM ROM same build or higher IF ALL GOES TO **** AND WONT LOOSE APPS OR DATA AT LEAST ON RR
Soft reboot after installing magisk modules. Phone is OOS latest stable & encrypted
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?
bramhc said:
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?
Click to expand...
Click to collapse
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.
yldlj said:
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.
Click to expand...
Click to collapse
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo
bramhc said:
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo
Click to expand...
Click to collapse
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2
yldlj said:
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2
Click to expand...
Click to collapse
Okay. Will try now. Thanks
EDIT: Confirmed. Viper4android works. Maybe it's James DSP that hasn't been updated to work with Pie. Cheers.
As above, I would appreciate it if someone could share a copy of a Magisk patched 11.0.5.1.GM21AA boot image. Thanks!
P.S. - Do not update to Magisk 24 or 24.1 unless you want to have to mess around with your phone!
Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.
Dan3ll1 said:
Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.
Click to expand...
Click to collapse
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?
benengyj said:
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?
Click to expand...
Click to collapse
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.
Frodolo said:
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.
Click to expand...
Click to collapse
Once you've upgraded to 24 or 24.1 it seems that the only way to go back to an older version is to use the built-in uninstall button in the Magisk app. Just trying to flash a new boot image over it doesn't seem to stick.
In my case, I had to:
Uninstall any version of the Magisk app
Install 24.1
Extract the boot image using Payload Dumper
Creating a 24.1 patched boot image to re-root my device
Uninstalling 24.1 using the uninstall button in the Magisk app
Install Canary Magisk (23 should work too)
Create a new 23 patched boot image and root using it
Still have not gotten around to fixing my MagiskHide and SafetyNet failing though, I think that requires some cache clearing and other steps to resolve. Also somehow managed to get rid of my TWRP accidentally along the way too, so I'll have to reinstall that again.
Thanks a lot!
benengyj said:
Uninstalling 24.1 using the uninstall button in the Magisk app
Click to expand...
Click to collapse
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?
¿GotJazz? said:
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?
Click to expand...
Click to collapse
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol
benengyj said:
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol
Click to expand...
Click to collapse
Yep, that's weird. I was having (a ton of) trouble getting my phone rooted at the time, so that's why I didn't see it.