Magisk General Support / Discussion

Search This thread

iamnitsuji

Member
Jul 19, 2017
7
3
OnePlus 5
Google Pixel 5a
Magisk install leads to Shutdown-to-recovery loop

This has me stumped. Today I installed an OTA system update (OxygenOS 9.0.6 on OnePlus 5). I flashed the latest TWRP via fastboot (v3.3.1-x blu_spark v9.101). From TWRP, I flashed Magisk 19.3. Everything was routine...

But I am getting shutdown loops (system reboots, as soon as the lock screen appears a message says "Shutting down..." and the phone boots into TWRP).

The only thing that stops this behavior is running Magisk Uninstaller from TWRP. The uninstaller does its thing and the phone reboots and functions normally.

It appears to be a Magisk-related issue. I haven't tried rolling back my system update.

Does anyone have any ideas?

⁂ ⁂ ⁂

Update: Magisk 19.1 installs and works. Magisk 19.3 still gives me a shutdown loop. Anyone else getting this bug?
 
Last edited:

camer0

Member
Jul 28, 2018
5
0
No matter what I do, Snapchat keeps detecting root. I have tried different versions of Magisk, uninstalling all root apps, using/not using MagiskHide, core mode, MagiskHide props config, etc.
 

kotuamoalt

Senior Member
Jun 23, 2016
210
58
OnePlus 8 Pro
Play store suddenly reports Netflix is no longer compatible with my Pixel 3 XL rooted with magisk. Passing magisk safetynet. Currently running netflix 7.13.0 build 15 34276 and latest STABLE Magisk manager and magisk. Play store still reports "certified", yet netflix app can no longer be found in play store app and PC browser (firefox) reports "incompatible" with my pixel 3 XL.

** edit ** could manually install latest version, kept crashing, restored TiBu backup, now that one crashes too as well as build 13 and i'm without netflix entirely
I tried launching Netflix, and it indeed gave me a device fail message of some kind. Hid Netflix using Magisk Hide, and it is now working again.

Sent from my Verizon Samsung Galaxy S5 using XDA Labs
 

drothenberger

Senior Member
Feb 2, 2011
658
536
Kenmore, WA
Play store suddenly reports Netflix is no longer compatible with my Pixel 3 XL rooted with magisk. Passing magisk safetynet. Currently running netflix 7.13.0 build 15 34276 and latest STABLE Magisk manager and magisk. Play store still reports "certified", yet netflix app can no longer be found in play store app and PC browser (firefox) reports "incompatible" with my pixel 3 XL.

** edit ** could manually install latest version, kept crashing, restored TiBu backup, now that one crashes too as well as build 13 and i'm without netflix entirely

I'm seeing the same thing with my Pixel 2 XL. I have version 7.12.1 build 26 installed, but Play Store says my device is incompatible.
 

drezz2

Senior Member
Jul 24, 2008
405
23
Madrid
Installed 19.2 on my Pixel 3XL and Cerberus is spamming for root permissions when google maps directions is open. Magisk logs is filled with request and toast msg is perma on the screen.

the 19.3 solve the problem with cerberus? or cerberus need to changue something? (the developers of cerberus do not respond to anything)


if I keep going safetynet without updating is it necessary to update?

if I make a backup with twrp of the complete system with the boot .. and the update of magisk does not work for me, restoring the backup would return normally to the previous version, that is to say the changes that I made in the boot
 
Last edited:

Momotani-Hitoshi

Senior Member
Nov 23, 2013
270
95
the 19.3 solve the problem with cerberus? or cerberus need to changue something? (the developers of cerberus do not respond to anything)


if I keep going safetynet without updating is it necessary to update?

if I make a backup with twrp of the complete system with the boot .. and the update of magisk does not work for me, restoring the backup would return normally to the previous version, that is to say the changes that I made in the boot

Cereberus dev told me to use the beta or updated version on their website instead of google playstore version. So far it has fixed my issue with magisk.
 
  • Like
Reactions: kotuamoalt

drezz2

Senior Member
Jul 24, 2008
405
23
Madrid
Cereberus dev told me to use the beta or updated version on their website instead of google playstore version. So far it has fixed my issue with magisk.
the 3.6.3? ok i have the 3.6.2 from their website, i try
I will make an entire backup because if something does not go well I do not know how to go back to an earlier version of magisk, if it is possible
 

Lothgar

Senior Member
Oct 5, 2014
118
17
Rome
Hi, everyone.
I unlocked the bootloader and patched boot.img manually on my Huawei Mediapad M3 lite 8 (CPN-L09).
But after doing so the fingerprint sensor stops working, like there is never been a fp sensor.
Im on latest emui avaible for my device (5.1.3), the android version is 7.0 and kernel version 3.18.31.

Here is the logcat and magisk log.

I also found this issue: https://github.com/topjohnwu/Magisk/issues/862
Is there a way to manually patch the boot.img with an older magisk version?

Thanks in advance.
 

Lazy Rich

Senior Member
Sep 20, 2010
1,037
414
Hamburg
OnePlus Nord
Xiaomi Poco F3
Play store suddenly reports Netflix is no longer compatible with my Pixel 3 XL rooted with magisk. Passing magisk safetynet. Currently running netflix 7.13.0 build 15 34276 and latest STABLE Magisk manager and magisk. Play store still reports "certified", yet netflix app can no longer be found in play store app and PC browser (firefox) reports "incompatible" with my pixel 3 XL.

** edit ** could manually install latest version, kept crashing, restored TiBu backup, now that one crashes too as well as build 13 and i'm without netflix entirely

Yup, exactly the same problem here. Device is Poco F1. I had to sideload the latest stable (6.26.1 build 15) to make it work again. But Play Store still says that the device isn't compatible anymore.

Hope we'll see a fix soon.
 

Momotani-Hitoshi

Senior Member
Nov 23, 2013
270
95
the 3.6.3? ok i have the 3.6.2 from their website, i try
I will make an entire backup because if something does not go well I do not know how to go back to an earlier version of magisk, if it is possible

Yes, I'm using 3.6.3 from cerberus website, don't think it has updated on playstore yet.

There is no way to downgrade magisk which I learned the hardway. Can only upgrade or uninstall. Best to make a backup of the boot.img so you can restore later if things fail.
 
Last edited:

Ch3vr0n

Senior Member
May 6, 2009
1,693
668
41
Yup, exactly the same problem here. Device is Poco F1. I had to sideload the latest stable (6.26.1 build 15) to make it work again. But Play Store still says that the device isn't compatible anymore.

Hope we'll see a fix soon.
That's exactly what I did too

Sent from my Pixel 3 XL using Tapatalk
 

drezz2

Senior Member
Jul 24, 2008
405
23
Madrid
Yes, I'm using 3.6.3 from cerberus website, don't think it has updated on playstore yet.

There is no way to downgrade magisk which I learned the hardway. Can only upgrade or uninstall. Best to make a backup of the boot.img so you can restore later if things fail.

there is no downgrade .. but if it is uninstalled then if I can reinstall a previous one right?
the option to make a full backup with twrp and reinstall the backup would also be valid? (exaggerated but ..)
Is not it necessary to update magisk while passing the safetynet test? I'm using the 18.1 and the test tells me that passes this test


I will try with the version that you indicate of cerberus, if the problem with magisk is solved is a big step, although I had another connectivity problem with lineage and I have never been answered to this problem
 

Momotani-Hitoshi

Senior Member
Nov 23, 2013
270
95
there is no downgrade .. but if it is uninstalled then if I can reinstall a previous one right?
the option to make a full backup with twrp and reinstall the backup would also be valid? (exaggerated but ..)
Is not it necessary to update magisk while passing the safetynet test? I'm using the 18.1 and the test tells me that passes this test


I will try with the version that you indicate of cerberus, if the problem with magisk is solved is a big step, although I had another connectivity problem with lineage and I have never been answered to this problem

Yes you can uninstall magisk and reinstall any other magisk version, but it might affect your other modifications like custom kernel etc & redo you modules. I find it easier to do TWRP backup and restore if needed.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    I'm now having a problem hiding the TJW Magisk 27002 app ...

    I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.

    The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:

    (1) Unhide Magisk
    (2) Update Magisk (27002 was listed)
    (3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
    (4) Magisk 27002 indeed came up properly after reboot.
    (5) Tried to perform Hide The Magisk App.

    I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.

    I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.

    I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.

    What am I missing?
    Known issue. A fix has been merged. You can use the Debug app, revert back to 27001 or wait until 27003 is released.

    EDIT: Ninja'd 🙃
    4
    Is the Magisk 27001 APK/zip still available anywhere? I'd like to downgrade, but I can only find 27000 on Github and 27002 via update. I don't want to go to Canary in case the mounting changes break anything, or Debug as I hear the extra logging etc. causes performance issues (correct me if I'm wrong).
    Only v27000 is Stable. (and Beta). v27001 and v27002 are Canary or Debug

    Set your Update Channel to Stable and you will see (just like you can see also on GitHub) that latest Stable is v27000, there was never Stable v27001 or v27002

    Generally, Stable is always Nx100

    So, you cannot downgrade to Stable v27001 but Canary v27001 should be just like Stable v27000 (same codebase). That's also the general policy, whenever Nx100 Stable is released, then immediately comes Canary Nx100 +1, on the same code-base

    Therefore, downgrade to Stable v27000 instead
    4
    Direct Install with recovery mode checked worked for me. You were right.

    After I flashed wrong CSC firmware my baseband and EMEIs disappeared. Now I have updated bootloader and I cant to flash original CSC firmware anymore. Any ideas how to restore baseband, EMEIs or it is too late?
    Yep, I told you several times that you need Recovery mode (selected) for your Ramdisk=No device; instructions for this are also clear in official Installation Instruction page too, but apparently you have not been trying to follow official instructions, so it's no real surprise you've messed up firmware too... Please take *extra* care when modding as there are simply so many variables and pitfalls! 😬

    Are you flashing patched AP (Application Processor binary) along with all the other package binaries (X4?) for your S10+ (also in Magisk Installation page, Samsung section)??

    CP is Cellular Processor (Nb. Oft repeated references to CP as 'core processor' may be misleading) binary package (also referred to as Baseband Modem) so that should have fixed mismatched baseband etc... correct CSC (Consumer Software Customization; region, APN and carrier specific software packages/settings) and even BL (Bootloader) are most likely also important...

    Nb. BL doesn't always update bootloader version, but if later firmware has been flashed be aware that these can also cause anti-roll back version for bootloader to be incremented (in the event that an update patches serious vulns) so you original firmware may be blocked and you may need to use later packages only...

    If flashing latest complete firmware package via Odin doesn't fix your IMEI / baseband issues it may be that you've messed with partitions that contain unique device values in the past... You may need to ask in Galaxy, S10 or S10+ XDA forums for that. 🤠 PW
    4
    I'm now having a problem hiding the TJW Magisk 27002 app ...

    I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.

    The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:

    (1) Unhide Magisk
    (2) Update Magisk (27002 was listed)
    (3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
    (4) Magisk 27002 indeed came up properly after reboot.
    (5) Tried to perform Hide The Magisk App.

    I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.

    I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.

    I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.

    What am I missing?
    Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about it
    3
    I actually updated the app from the app itself before doing my OTA upgrade so it get the version 27 of magisk, I tried installing that one again I had in my downloaded folder. But I also downloaded again the app from github.

    I do have root, I've modified the boot file with magisk, so I'm not sure what to do now. I'll try installing an older version. But as you see of the screenshot from app manager, I don't know how the app is installed and removed almost immediately. At first I thought it was caused by an android 14 new security change.
    Run magisk -c from adb shell and see what version it reports.
    Then uninstall every copy of magisk app,
    You have more than one (including possibly a hidden one)
    Then reboot and install magisk app matching the version reported by magisk -c command.
  • 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