Magisk General Support / Discussion

Search This thread

trax7

Senior Member
May 15, 2012
944
345
Loops

Latest Magisk 18.1 bootloops on latest 9.2.15 beta (MIUI EU) Pie on Poco F1. It worked on the previous version and without Magisk everything boots fine. I tried latest Canary version and i'm still waiting for it to boot, it's not looping, but it's stuck. The weird thing is if right after installing Magisk I try to install a custom kernel, I get Error 1 in recovery with the text "Unzip failed". :eek:
 

Klusio19

Senior Member
Nov 13, 2018
230
61
Tarnobrzeg
Google Pixel 7
My understanding is that whatever I back up now, it will be exactly like this if I restore it correctly, whenever I do it.. So if I restore in the future, I will be going back to the past.

That's what I've been doing.. Just in case something goes wrong with some app/mod that I'm checking, I can go back to just before I installed the app/mod.

To me, it's something like a restore point in Windows for PC users.
So what do you think: better to make backup with or without Magisk?
 

chooks06

Senior Member
Jan 12, 2015
1,096
375
singapore
So what do you think: better to make backup with or without Magisk?
It depend on what you prefer.

Without Magisk, gives the option to install new version when restoring, BUT, if the removal wasn't properly done, you'll end up restoring the problem.

I have more than one backup so if the latest gives problems I can't resolve, I have another earlier one to fall back on.

Usually before I start root, I have one backup, after updating apps and logging in..

After rooting and all is stable with a further setup, I do another backup.

Then the others are as and when needed.
 
  • Like
Reactions: Klusio19

Klusio19

Senior Member
Nov 13, 2018
230
61
Tarnobrzeg
Google Pixel 7
It depend on what you prefer.

Without Magisk, gives the option to install new version when restoring, BUT, if the removal wasn't properly done, you'll end up restoring the problem.

I have more than one backup so if the latest gives problems I can't resolve, I have another earlier one to fall back on.

Usually before I start root, I have one backup, after updating apps and logging in..

After rooting and all is stable with a further setup, I do another backup.

Then the others are as and when needed.
Ok. Thank you for comprehensive answer. :cowboy:
 

blackhawk_LA

Senior Member
Dec 27, 2010
1,558
657
HTC One (m7)
Sony Xperia XZ1 Compact
I have a big problem; I hope someone can help me, please.
I was running Magisk 18.1 on a LG G6, which is encrypted. There's no TWRP version that can handle encryption so I can't acces any data from recovery.
The problem came when I uninstalled Magisk from the app. After rebooting, the phone was in a bootloop. So I went to recovery and magisk again. But when the phone boots, now I have "secure boot-up" enabled, and asks me for a password I have never set (actually, my lock screen was secured with a pattern). I tried restoring stock boot, different magisk versions but still no luck. And every reboot, the number of attempts increases by one. So I have only 20 left to solve this, before losing all my data (which will be a huge pain for me)
Anyone has an idea on how to manage this?
 

tbqstp

Senior Member
Oct 19, 2015
145
43
OnePlus 9 Pro
I'm having some trouble. I opened up magisk manager to do something in there and was going to update magisk while I was at it. Before I could it prompted me to download new apk. I did and now it's saying apk doesn't support magisk lower than 18, manually flash or downgrade app. I've tried downloading older version of app but it just installs it as separate app and doesn't let me do anything. Not sure what to do. I saw someone mention using TWRP but I don't have that installed on my phone. How would I go about fixing this? Pixel XL 2

I had the same problem. Simply uninstall the latest Magisk Manager first and then install the previous one.
 

darwinmach

Senior Member
Mar 30, 2008
124
212
dmach.net
T-Mobile LG G5
HTC U11
I'm having some trouble. I opened up magisk manager to do something in there and was going to update magisk while I was at it. Before I could it prompted me to download new apk. I did and now it's saying apk doesn't support magisk lower than 18, manually flash or downgrade app. I've tried downloading older version of app but it just installs it as separate app and doesn't let me do anything. Not sure what to do. I saw someone mention using TWRP but I don't have that installed on my phone. How would I go about fixing this? Pixel XL 2

This happened to me as well and it's because I had Magisk Manager set to use a random package name.

I fixed it by going into Settings -> Restore Magisk Manager. For me, this loaded the new version automatically. You can then go back in and re-randomize the package name.
 

Cruel_Carlos

Member
Dec 23, 2018
6
0
Bellflower
@X0LARIUM As far as I've seen there's been nothing but people trying to help you here, but from you I've only seen ranting, aggressive posting and what seems like a sense of entitlement. I'll post one last thing trying to help you and then I'm done...

First of all, where did you download the Magisk Manager? Where there no instructions of any kind where you found it? If you go to the official release thread you'll find installation instructions and links to the official documentation (where you'll also find installation instructions), my troubleshooting guide, and more.

I've also posted links to you with instructions and tips on how to gather details and logs that could possibly help us help you with the issues you're experiencing.

Nobody here has been saying anything about Magisk being "THE BEST APP FOR ROOTING", except you... Nobody's forcing you to use it, nobody is saying that it will be completely trouble free, etc.

Remember that this is a community, and a community can only be what you help to make it.

I hope you get things worked out, but if you can't post without (what comes across as) aggressive ranting, I think you'll have a hard time getting help. Good luck.
These kinds of things often escalate to Flame Wars and that's not cool.

I too share the frustration of not being able to root my Samsung S7, but I stop my emotional tendencies and try to rely on logic lest I insult the people for trying to help me. That said I'm in the loop here as I tried this on a older phone it seems to go through. My 7 will not, for example, fully implement magisk 18.1 update. It keeps downloading it and try to install and nothing. Because I know zero about computer programming I have no clue what to do next.
ZERO
sorry, didn't mean to yell, but it is very frustrating when you follow instructions as best you can and nothing works out. I almost started quoting institutionalized by Suicidal Tendencies. Thankfully logic won out this time. It's just that the longer I stay on the more likely it is I'll start quoting things.
for what it's worth, I do appreciate everthing you folks put out there. I'll just keep reading in hopefully it'll make begin making sense.

"Help me, XDA Community, you're my only hope" ?
 
oh, I forgot that bootloader ist still unlocked. Didn't checked SafetyNet status without Magisk



Don't know what to do any more - I loved to pay with my phone, but also need root.

Gpay detects modification whatever I try
On my OP6, I got GPay working with Magisk 17.2. Also SafetyNet and cts are green and MagiskHide does work.

GPay might need a reinstall, means delete its data via app manager and login again.
 

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,300
1
14,848
Gone
Google Nexus 4
Nexus 6
@Cruel_Carlos Sounds like you're having a though time... From what I understand, Sammy devices can be frustrating. Personally I don't do Samsung...

From your post it sounds like you're already rooted, correct? And the issue is that you can't update to Magisk v18.1. What's your current Magisk version? Some more specifics and details would be good...

You could try a few different approaches.

And, most importantly of all, if you continue having troubles try to get logs showing what's going on. It's really hard to help otherwise.
 

masterjp

Member
Sep 12, 2012
43
8
Duesseldorf (NRW)
I flashed the latest Android Oreo 8.0 stock firmware for my Samsung S7 (SM-G930F) with Exynos chip and flashing magisk 18.1 root does not work. With an older Oreo firmware from 12/2018 and Magisk 18.0 I will not get any problems. I used TWRP 3.2.3.0 (latest version) and did not see any error during flashing. I am not a beginner of flashing. Maybe something has changed or Samsung has modified something to prevent rooting!? Are there some other users, which have the same problem?

I used the following instruction to do it:
https://xdaforums.com/s7-edge/how-to/guide-how-to-root-android-8-0-oreo-t3840271
 

demonoidmaster

Senior Member
Nov 19, 2015
1,035
331
How to update old magisk modules??
At least help me to install old magisk
When i install magisk 16.2
It says i have to update to 18.1 until i be able to flash any module

Plz help me i want some of those modules
Do what it tells you to do

---------- Post added at 08:22 PM ---------- Previous post was at 08:13 PM ----------

I have a big problem; I hope someone can help me, please.
I was running Magisk 18.1 on a LG G6, which is encrypted. There's no TWRP version that can handle encryption so I can't acces any data from recovery.
The problem came when I uninstalled Magisk from the app. After rebooting, the phone was in a bootloop. So I went to recovery and magisk again. But when the phone boots, now I have "secure boot-up" enabled, and asks me for a password I have never set (actually, my lock screen was secured with a pattern). I tried restoring stock boot, different magisk versions but still no luck. And every reboot, the number of attempts increases by one. So I have only 20 left to solve this, before losing all my data (which will be a huge pain for me)
Anyone has an idea on how to manage this?
Why did you uninstall magisk via the app instead of via twrp.. actually, which did you encrypt or leave your device encrypted if it's known that twrp doesn't work with it? Before having set up your phone you should of nuked /data then install your rom, gapps, etc

Your only hope is waiting until a future twrp update can decrypt data so you can backup your stuff then restart from scratch
 
  • Like
Reactions: blackhawk_LA

Jannomag

Senior Member
Sep 20, 2015
694
225
Hamburg
Magisk on Huawei P10 VTR with Pie

Hi, I just updated to Pie (EMUI 9, version 9.0.1.157(C432E1R1P9) on my Huawei P10 VTR.
Everything works fine so I tried to install Magisk like this:
- Extracted the recovery "RECOVERY_RAMDIS.IMG" from the UPDATE.APP package
- Patched it with Magisk app (Install --> Install --> Patch Boot image)
- Flashed patched recovery with "fastboot flash recovery_ramdisk recovery_patched.img".
When I boot up by pressing Vol+, like I want to boot into recovery, the phone won't boot.
It stucks at the bootloader screen. I have to turn it off manually.
Normal boot is still possible.

Any solution here?
 

ktingmar

New member
Sep 29, 2018
1
0
I flashed the latest Android Oreo 8.0 stock firmware for my Samsung S7 (SM-G930F) with Exynos chip and flashing magisk 18.1 root does not work. With an older Oreo firmware from 12/2018 and Magisk 18.0 I will not get any problems. I used TWRP 3.2.3.0 (latest version) and did not see any error during flashing. I am not a beginner of flashing. Maybe something has changed or Samsung has modified something to prevent rooting!? Are there some other users, which have the same problem?

I used the following instruction to do it:
https://xdaforums.com/s7-edge/how-to/guide-how-to-root-android-8-0-oreo-t3840271

Yes, I do have the same problem with the same phone right now on every ROM I tried so far! Did you find a solution yet?
 

M1chiel

Senior Member
Hi, I just updated to Pie (EMUI 9, version 9.0.1.157(C432E1R1P9) on my Huawei P10 VTR.
Everything works fine so I tried to install Magisk like this:
- Extracted the recovery "RECOVERY_RAMDIS.IMG" from the UPDATE.APP package
- Patched it with Magisk app (Install --> Install --> Patch Boot image)
- Flashed patched recovery with "fastboot flash recovery_ramdisk recovery_patched.img".
When I boot up by pressing Vol+, like I want to boot into recovery, the phone won't boot.
It stucks at the bootloader screen. I have to turn it off manually.
Normal boot is still possible.

Any solution here?
Magisk can only work on EMUI 9 if you install it instead of the recovery. It is supposed to work in the Canary build. More info is in the release notes of the version that appeared around Christmas.
 

Ps24u

Senior Member
May 21, 2016
174
39
02-17 16:40:30.170 1441 1882 I Magisk : * Running module service scripts
02-17 16:41:31.119 4418 4418 I Magisk : * Device API level: 25
02-17 16:41:31.119 4418 4418 E Magisk : bind failed with 98: Address already in use
02-17 16:41:52.849 1441 1462 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[6598] ns=[4026536757]
Is this error problematic and if so how can I solve it?
Thanks for your insight.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    I can't access superuser and modules they are both lockedView attachment 6081641
    Your phone isn't rooted! The top section of your screenshot shows Magisk "Installed N/A".
    Installing the Magisk app isn't enough to root your phone.
    4
    Latest canary Update 27002 will not let me hide the Magisk app, get a failed toast, tried opening an issue but need to use the debug version,
    Installed the debug version and it works and hides the magisk app?
    4
    I have always have problems with magisk and bug reports think I have even failed with the debug version lol, although its closed I have added that the bug is not present with the debug version
    Just open another with "version code: 27002" somewhere in first post, explain you tested both but issue is with Canary only, not Debug... Supply logs from broken build and wait for further instructions from Devs... Template requires the version code (or bot closes) + logs (or Devs will often close with comment like "no log no fix")...👍 PW

    Edit: Someone opened proper issue following template just now:
    https://github.com/topjohnwu/Magisk/issues/7921

    Looks to me like this commit has issues:

    Always update stub APK when upgrade

    committed5 days ago
    4
    Hello, I'd like to write a module for magisk to transfer in userspace actions like this:
    "echo "16 2048" > /sys/class/leds/aw210xx_led/single_led_br" to allow led control on Nothing Phone 1 to any app, would you suggest me an example module I can take inspiration from?
    Write your service.sh script with whatever commands you need

    Then use any module you already have installed that does not have its service.sh script and add your scriot to that module, eg in case of Systemless Hosts itbwill be:
    /data/adb/modules/hosts/service.sh

    Or use some other module that does have its own service sh script and extend its script with your commands

    You may need to wait booting to finish (you have to debug how yout modifications works if executed earlier or later), in that case script will look like:
    #!/system/bin/sh

    until [ "$(getprop sys.boot_completed)" == "1" ]; do
    sleep 1
    done

    echo "16 2048" > /sys/class/leds/aw210xx_led/single_led_br

    You can add additional sleep if you need to further postpone upon the System finish booting, eg couple of seconds to establish WiFi connection or something

    Or if that is too late (some modifications must be done much earlier, while the System boots), you will have to use post-fs-data.sh script instead of service.sh script but then you must not wait for booting to finish and you must not use sleep

    Read on Magisk GitHub Developer info avout differences in service sh and post-fs-data.sh usage

    Read there generally about the structure of the module scriot, etc

    At the end reboot and test does it work

    Once you make sure that your script does the job properly, it will be an easy step to pack it into your own module

    Similar questions have been asked couple of times (and I responded with instructions and minumalistic sceleton to pack final scripts into the zip installation for a new module)
    4
    Not sure if the fix has been pushed yet but looking at GitHub it's been sorted
    Not pushed yet according to my magisk app.
    Luckily i don't hide or need to hide; this is a sad bug and i hope, for others' sake, it's pushed as soon as the developers can. But that's also why it's canary and not beta or release, it's why (or should be why) we use canary, to squash bugs before the rest experience them.
  • 1103
    This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
    All information, including troubleshoot guides and notes, are in the Announcement Thread
    156
    Hello, I haven't given much support on XDA lately. It can be resulted from
    • University started and I have limited free time. In fact, I mostly develop during midnight
    • I live in Taiwan, which has large time zone differences between my European/American contributors/testers, which usually forces me to stay up late at night to discuss/test stuffs.
    • The new version is about to come, I don't want to spend effort on supporting old releases
    The planned update is delayed again and again, to some point I think I'll shed some light about what has been happening lately, also along with some announcements.

    New Forum!
    As you might have already discovered, Magisk got its own subforum on XDA! Many thanks to all the support you gave me, and much more information/features/support is about to come!
    **For developers supporting all the devices that are not using standard Android boot format, feel free to create threads in this section (actually, PLEASE do so) for your favorite devices after v7 is out. As I currently know, Asus devices require signing the boot image before flashing, and is model dependant; Sony devices seems to use ELF kernel that is unpatchable, or some has two ramdisks (inner + outer), both requires different workarounds; LG bootloader locked devices has to manually "BUMP" the boot image after flashing Magisk..... and there may be lots of other crazy boot image formats that haven't come up to my attention yet.
    It is impossible for me to support all these non-standard boot images, and I hope the community can collaborate to make Magisk running across all the devices. Overall, community collaboration is what XDA about :D

    The Pixel Phone
    Some of you might already know this news, that the next Pixel Phone right around the corner seems like it does not have ramdisk in boot image, which pretty much wrecked Magisk in all ways. However, it pretty much doomed root itself too. Kernel modifications is inevitable IMO, so I'll try to migrate my scripts to C programs that could possibly be included into the kernel itself. Note that I'm not familiar with linux kernel, I'm not even sure if my idea and concept is correct or not. But once the device is available, I think developers will find a way to bypass all the difficulties, and I'll do my best to learn things ;)

    Current Progress
    In the past month, I've spent quite some time learning SELinux, so that I can avoid using SuperSU's sepolicy patches. Thanks to the helps and tips from @phhusson and @Chainfire, I finally have a much clearer understanding of how SELinux works. The Magisk core parts (the scripts, boot image patches, new features, more supports) are actually done some time ago. What is causing all the delays is the Magisk Manager.
    To be completely honest, although I can code in Java without much issues, Magisk Manager is actually my first Android application, I had to reach out for assistance, and fortunately awesome developers like @DVDandroid and @digitalhigh contributed a lot, which makes the current Manager awesome.
    After the repo system and module management is mostly done, I was about to do some adjustments and release, but what we really done is decided to add another feature: auto-unroot with per-app settings. I decided to wait for it to be finished, and then do my adjustments. Due to reasons that'll be mentioned later, this feature will likely not be available for the next release (should come in future updates)

    Safety Net Disaster
    Those who are using Magisk for Safety Net bypass purposes must have known that Google recently updated the detection method of my Systemless Xposed. I still have no idea what Safety Net is detecting, so currently I cannot fix it on my side (also because I'm busy working on the next update). However, suhide developed by @Chainfire is able to hide Xposed and worked fine.
    However, only my Systemless Xposed v86.2, which is based on SuperSU's su.d, is supported using that method. v86.2 and v86.5 (latest, Magisk based) have nearly identical binaries, and the only difference is the path where the binaries are stored.
    I'm still not sure what's the real issue for it not being supported, I just hope it is not done intentionally.

    Conclusion
    Due to the fact that my Safety Net bypass is not 100% perfect now, I do not want to spend any more time waiting for auto-unroot to be polished. What I'm doing now is finishing up all the things I'd like to change in Magisk Manager (it has been a while since I last contributed to Manager, my fellow developers are doing all the heavy job), which might take a little more time, after that, packed with tons of information to be announced in Magisk Section, I'll release the long awaited update.

    Hope this lengthy post gives you the idea of the whole situation, and again thanks for all your support!!
    121
    Ah, some Chainfire bashing, I hope it is not too late for me to exercise additional villainy.

    First, let me make clear I have nothing against @topjohnwu, nor against Magisk. Magisk is an interesting project and it certainly displays @topjohnwu ingenuity and persistence. I don't doubt we will see more interesting things from his hands.

    -------------------------

    What has happened here is not all that dark and complicated, from either end. I returned from holidays, and someone pointed me at Magisk. My first thought: interesting!

    Among other things, the thread lists some issues with SuperSU, which in combination with the phrase The developer also requests users to not bug Chainfire with compatibility requests for SuperSU with Magisk from the portal article, raised my left eyebrow by nigh half an inch. The popular systemless xposed mod is apparently now based on it, and apparently it now no longer works with SuperSU, and apparently I'm not supposed to fix that, nor any of the other found issues. I found that a bit weird. So yes, I have told @topjohnwu that I was a bit surprised he was posting about issues with SuperSU without notifying me about them (I can't fix or help fix issues I'm not aware of, after all).

    He's also spreading a modified version of the SuperSU package, which is not all that uncommon, nor necessarily a problem. I have not looked into what he modified, I only ran a few quick tests on one of my devices, and found some commonly used commands run as root to be broken. I have informed him of this as well.

    It appears the tool of choice for Magisk is phh's Superuser, because of some of the mentioned issues with SuperSU. That's fine by itself, but fixing issues in that superuser by incorporating SuperSU's binaries into it is a somewhat questionable practise. After all, SuperSU is a commercial closed-source package that helps pay for my dinner, and superuser is a direct competitor. I have informed him that I was surprised he did this without asking for permission. I have expressed similar surprise on him spreading a modified version of LiveBoot (which helps pay for a snack now and then).
    @topjohnwu has also stated that Magisk's scripts are largely influenced by mine (I have not checked). Scripts based on mine are used all over the place on XDA, some people have crafted amazing things based on them, I have never made an issue of this (otherwise I would have just made them binaries). But yes, I have also stated to him that I don't think it's very nice to base something on one program, and then using that to (almost exclusively) push something directly competing with that program.

    tl;dr Towards @topjohnwu, I have:
    - expressed surprise he has issues getting Magisk to work with SuperSU, and has chosen not to inform me about those
    - expressed surprise he is using SuperSU binaries in a competing superuser without permission
    - expressed surprise he is posting a modified LiveBoot without permission
    - informed him of issues with the modified SuperSU he has posted
    - let him know I thought it wasn't very nice to be applying my scripts to benefit seemingly exclusively that same competing superuser

    To be crystal clear:
    - I have not asked for an apology
    - I have not asked for Magisk to be abandoned, neither the root hiding nor systemless module parts, and certainly not systemless xposed
    - I have not made an issue of any of this anywhere, until this post
    - I have not even specifically asked for anything to be taken down (though obviously in my opinion the other superuser package mixed with SuperSU's binaries, as well as the LiveBoot package, should go)
    - I have not reported this thread to XDA moderators for copyright violations or otherwise

    While my conversation with @topjohnwu may not win any awards for being friendly (though it may win some for brevity), I think all things considered my response has been rather mild. To be perfectly honest, until the apology post, I thought this was over with already. I think the apology post was triggered because I haven't replied to his last PM for a while - I was in the zone, it happens.

    To emphasize again, I have nothing against @topjohnwu, Magisk, or systemless xposed, and it is certainly not my goal to see any of them go. If it can be made to work together with SuperSU, great.

    I get it though: you think of something, you want to see if you can make it work, you finally get it to work, you publish it, it takes off - enthusiasm gets the better of you. Maybe in the rush some mistakes are made. That doesn't mean you have to just drop it and run. None of my stuff would make it past 0.1 if I stopped at the first big mistake :)

    Aside from said being in the zone coding, I usually regret actually responding to these sort of things the day after, which has made me hesitant to reply. Surprise me.
    76
    Thread temporarily closed so everyone sees this.

    The flood of "SafetyNet isn't working for me either!" posts are not helpful, at all. Please refrain from posting further, it will be looked into. Please do not forget that not passing SafetyNet is 100% NORMAL AND INTENDED when you have an unlocked booloader or running custom firmware. These are workarounds and they will be worked around in turn.

    The Flash
    Forum Moderator

    EDIT: Thread is reopened... I will be cleaning any SafetyNet posts for a while to keep the thread clean for real issues.
    75
    Hello everyone!

    I am aware that Google has updated Safety Net that makes Magisk itself a no go for Android Pay. In fact, I witnessed the change live while I am developing the new magiskhide, which should hide all Magisk modules and Magisk installed root.

    Google is serious about Safety Net now, clearly hunting down all possibility to run Xposed with Safety Net passed. I spend quite some time examining the new security measures last midnight, and fortunately it seems that it is possible to run Magisk and root along with Safety Net if no Xposed is running. I'm glad I removed the old root toggle at the right time lol, that is no longer feasible with the latest detection.

    So stay tuned for the next update, it will come with bug fixes, along with the new magiskhide to bypass that Safety Net.

    Google, how will a few systemless mods do any harm :p:p