Magisk General Support / Discussion

Search This thread

mel2000

Senior Member
Apr 26, 2011
188
26
My phone won't boot flashing the latest Magisk v14 zip. I just updated to the latest June OTA for my Moto G4+ xt1644. Also successfully reinstalled TWRP 3.1.1.0 and ElementalX 1.04 kernel.

I uninstalled previous Magisk Manager and also flashed the Magisk uninstaller.zip via TWRP. Then I installed Magisk-v14.0.zip and wiped cache/Dalvik, then rebooted. Phone stayed stuck at the 'bootloader unlocked' screen for more than 20 minutes. I gave up and rolled back to a non-Magisk archive. System is now fine but without root.

I haven't found others with the same issue. Since my phone doesn't have NFC anyway, and since I doubt there will be another G4+ update, would it be better for me to try an alternative root process instead? Or does anyone have troubleshooting tips for my Magisk issue? Thanks.

EDIT: I flashed with Magisk v13.3, which worked for me before. It flashed and booted without a hitch. I hope Magisk v14.0 gets fixed soon because Magisk Manager 5.1.1 keeps prompting me to install Magisk v14.0 after every step I take within the app.
 
Last edited:

abced123

Senior Member
Jun 18, 2007
378
15
installation question

What is the real difference for the installation between flashing thru TWRP and the magisk manager ? If i do not have stock boot image dump, and install by the manager; will I have problem later if I uninstall magisk ? TIA
 
Last edited:

Didgeridoohan

Forum Moderator / Developer Relations
Staff member
May 31, 2012
11,423
11,632
Gothenburg
Google Nexus 4
Nexus 6
I just flashed September update + magisk 14.0 using flashfire, but now ctsProfile is false. Anybody knows why this is happening?

Same issue after installing the Sept update. I tried all the troubleshooting tips from the guides.

Same issue with me, just flashed the September Oreo update on my Nexus 6P as well.

Maybe Google messed up the certification on the update. Wouldn't be the first time... :p

What is the real difference for the installation between flashing thru TWRP and the magisk manager ? If i do not have stock boot image dump, and install by the manager; will I have problem later if I uninstall magisk ? TIA

If you want to install Magisk (from a clean slate) through the Manager without a stock boot image file available you won't have any issues uninstalling later, because you won't be able to install Magisk at all... :D

If you already have Magisk installed it's a different matter through. There shouldn't be any issues updating through the Manager.
 

DodoGTA

Inactive Recognized Developer
Feb 18, 2015
2,943
1,143
Magisk FTW!
 

Attachments

  • Screenshot_20170914-092721.png
    Screenshot_20170914-092721.png
    69.2 KB · Views: 494

Didgeridoohan

Forum Moderator / Developer Relations
Staff member
May 31, 2012
11,423
11,632
Gothenburg
Google Nexus 4
Nexus 6
I have Magisk v13.3 currently installed, can I install v14 and keep running all my modules or will they stop working until they are updated to the new module template?

They'll most likely keep working. Some modules using boot scripts or similar might need updating...

There might be some issues requiring clearing data for the Manager or a clean install off v14.0, but I'd say cross that bridge if you get to it...
 
  • Like
Reactions: rfgamaral

anandverma458

Member
Nov 1, 2016
31
2
So I have a vivo y55 (6.0.1), with a locked bootloader,but with twrp 3.1.1 installed. When I try to dorectly flash the magisk.zip, it fails at unpacking boot image (twrp logs say error 13 while getting boot image:permission denied). So I used magisk manager to patch the boot image and flashed it, but it resulted in a bootloop.

After that, I decompiled boot image and manually placed files one-by-one and booted it, and I found that the bootloop occurs when I place magisk file in /sbin, EVEN IF I DON'T PLACE INIT.MAGISK.RC AND SEPOLICY IN IT. Do you think you can help me? I think placing magisk in /system might work (I don't care about safetynet and ota). If so, would anyone provide the steps for it?
Thanks in advance btw.

Anyone with an answer?
 

SB13X

Senior Member
Jun 14, 2010
694
203
England, UK
My issue on GitHub appears to have been closed with the enclosed boot.img from my Samsung S7 Edge has anything been done again or statement made regards the installation of Magisk via the new ODIN Manager patched_boot.img.tar method? @topjohnwu

---------- Post added at 07:09 PM ---------- Previous post was at 07:09 PM ----------

My issue on GitHub appears to have been closed with the enclosed boot.img from my Samsung S7 Edge has anything been done again or statement made regards the installation of Magisk via the new ODIN Manager patched_boot.img.tar method? @topjohnwu
 

DeathHacker

Senior Member
May 2, 2017
145
56
My issue on GitHub appears to have been closed with the enclosed boot.img from my Samsung S7 Edge has anything been done again or statement made regards the installation of Magisk via the new ODIN Manager patched_boot.img.tar method? @topjohnwu
It seems to me that he completely removed the issue tracker on GitHub.
 
  • Like
Reactions: SB13X

Top Liked Posts

  • 9

    Latest Debug (Canary)​

    Changelog and Release Notes:​

    Magisk (f49966d8) (22103)​

    • [App] Update snet extension. This fixes SafetyNet API errors.
    • [App] Fix a bug in the stub app that causes APK installation to fail
    • [General] Fix a C++ bug that causes undefined behavior
    • [MagiskHide] Update package and process name validation logic

    Diffs to v22.1​

    • [General] Remove all pre Android 5.0 support
    • [MagiskPolicy] Remove unnecessary sepolicy rules
    • [App] Update snet extension. This fixes SafetyNet API errors.
    • [App] Fix a bug in the stub app that causes APK installation to fail
    • [General] Fix a C++ bug that causes undefined behavior
    • [MagiskHide] Update package and process name validation logic
    👍 ...And things are all Rosy 'n Safe in the Custom Mod. world once again... but ironically, only on the bleeding edge... (Confirmed on my RN8T. 🙂 )

    News for those not wanting to get cut (Public Stable / Beta users) below. 😜

    Thanks John... And other collaborators for additional fixes! PW
    5
    Fix and news:
    John Wu, 1h

    Just pushed a new canary build with SafetyNet checking functionality restored. Considering pushing a new early public release after a few more bug fixes.
    ... So imminent SafetyNet checking fix for public Stable / Beta (still has SafetyNet API errors) users is likely... No ETA of course! 😉

    👍 PW
    1
    How can I check for updates manually in Magisk app 22.1 ?
    In Manager 7.51 that I updated from, you could pull down the screen to manually check whenever you wished. I can't find the equivalent in 22.1...?

    Also who designed 22.1 app and thought it'd be a good idea to have a big "uninstall magisk" button 3 milimeters from the big "check safety net" button. Does the designer want people to remove Magisk by mistake ?
    Imho "uninstall magisk" should be at the bottom of the settings page, not the first thing you see when you open the app.

    I really wished there was an updated 7.51-style Manager/App with the new hiding stub technique.
    1
    I'm on oos11 and today I got an API error in the magisk. Any ideas ?
    Yes. Just read last page! 😉 PW
  • 12

    Latest Public (Stable / Beta)

    Release Notes and Changelog:


    2021.4.9 Magisk v22.1​

    This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.

    Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.

    Bug Fixes​

    • [App] Prevent multiple installation sessions running in parallel
    • [App] Prevent OutOfMemory crashes when checking boot signature on PXA boot images
    • [General] Proper cgroup migration implementation
    • [General] Rewrite log writer from scratch, should resolve any crashes and deadlocks
    • [General] Many scripts updates fixing regressions
    • [MagiskHide] Prevent possible deadlock when signal arrives
    • [MagiskHide] Partial match process names if necessary
    • [MagiskBoot] Preserve and patch AVB 2.0 structures/headers in boot images
    • [MagiskBoot] Properly strip out data encryption flags
    • [MagiskBoot] Prevent possible integer overflow
    • [MagiskInit] Fix sepolicy.rule mounting strategy
    • [resetprop] Always delete existing ro. props before updating. This will fix bootloops that could be caused by modifying device fingerprint properties.
    🎉 👍 PW
    9

    Latest Debug (Canary)​

    Changelog and Release Notes:​

    Magisk (f49966d8) (22103)​

    • [App] Update snet extension. This fixes SafetyNet API errors.
    • [App] Fix a bug in the stub app that causes APK installation to fail
    • [General] Fix a C++ bug that causes undefined behavior
    • [MagiskHide] Update package and process name validation logic

    Diffs to v22.1​

    • [General] Remove all pre Android 5.0 support
    • [MagiskPolicy] Remove unnecessary sepolicy rules
    • [App] Update snet extension. This fixes SafetyNet API errors.
    • [App] Fix a bug in the stub app that causes APK installation to fail
    • [General] Fix a C++ bug that causes undefined behavior
    • [MagiskHide] Update package and process name validation logic
    👍 ...And things are all Rosy 'n Safe in the Custom Mod. world once again... but ironically, only on the bleeding edge... (Confirmed on my RN8T. 🙂 )

    News for those not wanting to get cut (Public Stable / Beta users) below. 😜

    Thanks John... And other collaborators for additional fixes! PW
    8
    Update snet.jar extension
    The existing API key was revoked for some reason.
    Release an updated extension jar with a new API key.

    In addition, add some offline signature verification and change how
    results are parsed to workaround some dumbass Xposed module "faking"
    success results, since many users really don't know better.

    @topjohnwu

    topjohnwu committed 19 minutes ago
    8
    @osm0sis
    Thank you for having an eye on that.
    Did the "ls" twice, first from a TWRP-terminal in recovery, second from a terminal while phone is "up and running".
    Looks like you have /dev/bootimg as your real partition location and it is still higher in the list in util_functions.sh like how I fixed it in the linked commit, so this is definitely a regression from some other recent change to Magisk.. sigh, I'll look into it. 🤔😕
    6
    No, the phone is an Estar Takee1.
    ROM is from here: Mikel Android 7 for Takee1
    and is itself a port from this ROM: RidonOS for Micromaxx A311

    You're right, sorry for that. Now here the installation log for canary-version:

    - Target image: /dev/BOOT
    - Device platform: armeabi-v7a
    - Installing: f152b4c2 (22005)
    nanddump: MEMGETINFO: Not a typewriter
    Parsing boot image: [boot.img]
    - Unpacking boot image
    ! Unsupported/Unknown image format
    ! Installation failed

    😛

    /dev/BOOT is known (usually) not an actual boot partition, hence nanddump failing.

    I had originally fixed this back here: https://github.com/topjohnwu/Magisk/commit/2aede97754fec67d393bde0c7725ed84d8c3c112

    So not sure if we're looking at some kind of a regression, or just a further edge case.

    @io2345 what's the actual, correct location of your boot partition? Please give me the output of `ls -alR /dev`
  • 1046
    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
    155
    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!!
    119
    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.
    74
    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
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone