Magisk General Support / Discussion

Search This thread
By:
Advanced…
Didgeridoohan

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,300
1
14,850
Gone
Google Nexus 4
Nexus 6
jean marc said:
On Mi 9 pro Android 11 lastest developer Rom, installed magisk fix master and I got this result. The fact is that after updating magisk from 20.x to 21.x I get error while trying to get API google file, it cannot connect to the server. I cannot even see any module on line, I have to find them on the net, download through browser and after install with magisk. Beside that it passed Safetynet from third app. Magiskhide is installed and enabled.
View attachment 5187359View attachment 5187361View attachment 5187363View attachment 5187365View attachment 5187373
Click to expand...
Click to collapse

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet_API_error

The fact that you do not see any modules suggest that there is something that is blocking some parts of the Manager getting access to the internet. In the past that has usually been because of a custom hosts file.
 
  • Like
Reactions: woozie.2007
Didgeridoohan

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,300
1
14,850
Gone
Google Nexus 4
Nexus 6
AndDiSa said:
Only an idea: you could youse a user defined update channel which is pointing to 20.4 .... but currently I have no clue about the preconditions to a user-defined channel :-(
Click to expand...
Click to collapse
woozie.2007 said:
i don't know what is the channel for 20.4
Click to expand...
Click to collapse
Lughnasadh said:
You would have to find the json of the older magisk version you want (somewhere in Github maybe) and set a custom channel using that json.
Click to expand...
Click to collapse

Oh yeah... I forgot. The stable releases still have their update channels available through GitHub history (I was thinking about the Canary releases that have had their history cleared). This should be Magisk v20.4:
https://raw.githubusercontent.com/t...5ffa9b079f3a411dd2c00a80a3d985ccc/stable.json
 
  • Like
Reactions: dcarvil, J.Michael, AndDiSa and 2 others
D

Deleted member 8425317

Guest
2ISAB said:
Android 9 TWRP Magisk ctfs failed (was working a few days ago)
Samsung Galaxy A70 SM-A705YN

I tired Termux method and selected the closest to my device was SM-A705YNXSA
Fingerprint
su
props
“Edit Device Fingerprint”.
and selected the one mentioned above.
ctfs etc failed

Using latest Magisk Manager Magisk-21.2(21200)
Tries installing it within TWRP, however i cant pass
Would be very appreciative.
Click to expand...
Click to collapse


SOLVED using Termux fingerprint, downgraded Magisk, as follows

Iba5fe0791622839e1bad4730593a319ea03661f2

 

Attachments

  • Screenshot_20210115-064032.jpg
    Screenshot_20210115-064032.jpg
    284.7 KB · Views: 72
G

Ghisy

Senior Member
Mar 27, 2010
2,256
1,138
HTC Desire
Google Nexus 4
Hi there,

Trying to update from 20.4 to 21.2 (stable) on a Pixel 4 XL (still on Android 10) and I'm getting an "Unable to detect target image" error.

I usually have no problem updating Magisk. Is there something I'm missing here?
 
J

jean marc

Senior Member
Nov 5, 2006
114
4
Limassol
bilal91

bilal91

Senior Member
Jul 25, 2012
242
40
revolut is detecting root on my realme x3 superzoom (android 10)...no problems with Google pay or other banking apps, just revolut...anyone else with similar problem or any solutions?
passing all checks and have mhpc and safety net fix installed too
 
J

J.Michael

Recognized Contributor
Jan 20, 2018
2,494
3,049
Samsung Galaxy Tab A series
Didgeridoohan said:
Picking a different hosts file provider would be one solution. There are other ways too, but you'd have to search for those since I don't have the details...
Click to expand...
Click to collapse
Why would anyone be blocking wherever it is that Magisk goes to get files?
If @jean marc was happy with everything else about that hosts file, couldn't he just delete the lines referring to github (or wherever)?
 
  • Like
Reactions: jean marc
Didgeridoohan

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,300
1
14,850
Gone
Google Nexus 4
Nexus 6
J.Michael said:
Why would anyone be blocking wherever it is that Magisk goes to get files?
If @jean marc was happy with everything else about that hosts file, couldn't he just delete the lines referring to github (or wherever)?
Click to expand...
Click to collapse

Why? Very good questions, but there have been many reports of this. And yes, one solution is to whitelist the affected addresses in the hosts file, but you'd first have to figure out which ones. This kind of issue mainly started after @topjohnwu started using the JSDelivr CDN for downloads, but that usually didn't manifest like this (downloads of Magisk of modules would fail), so I guess there are other addresses involved here.
 
  • Like
Reactions: J.Michael
zgfg

zgfg

Senior Member
Oct 10, 2016
10,761
9,384
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11
jean marc said:
It works, I also cleaned the cache. Only that now I receive all advertising. What good adblocker can I use?
View attachment 5187477
Click to expand...
Click to collapse
It's all about the hosts sources you use (list of blocked sites), not the add blocker itself

E.g., if you use AdAway, with its three default hosts sources it would not affect Magisk Manager.
If for some reason you want to add additional hosts sources and if you observe they block Magisk Manager, you can debug DNS to find which sites must be whitelisted - but that's off topic for this thread

See also the post above, about JSDelivr (probably a site that might be blocked by some hosts sources they are heavy to block all analytics tools, and you would need to whitelist)

But again, there is no problem with the three default hosts sources coming preinstalled with AdAway
 
Last edited:
  • Like
Reactions: J.Michael
A

akhil093

Senior Member
Jun 22, 2013
212
279
Los Angeles C.A
New versions of google play services keep messing with my magisk and device. Is there any way to stop google play services from updating itself ? I want to keep old version of gms. That works best with magisk I installed.
 
Sid220

Sid220

Senior Member
Jul 31, 2012
97
32
Como
LeEco Le 2
Xiaomi Poco F1
My banking app detects root after i installed Magisk 21.2, with version 20.4 does not detect root. Manager version 8.0.5, MagiskHide enabled and app added to list. I'm not doing something wrong since MagiskHide works with older version. What can i do to fix this?
 
dope77

dope77

Senior Member
Aug 8, 2018
401
125
installed latest magisk canary update and rebooted,now my phone is constantly rebooting on Samsung Galaxy J6+ Logo,
where can i find version history of magisk? i need to downgrade
 
You must log in or register to reply here.

Similar threads

T
  • Locked
  • Sticky
Magisk - The Magic Mask for Android
Replies
56
Views
6M
T
topjohnwu
T
  • Locked
[CLOSED][BETA][2018.7.19] Magisk v16.7 (1671)
Replies
7K
Views
3M
T
topjohnwu
Heisenberg
[Discussion] PokeMon Go Magisk Discussion Thread
Replies
5K
Views
649K
beneditodragon
beneditodragon
Didgeridoohan
[Discussion] Google Pay Magisk Discussion Thread
Replies
3K
Views
572K
I
ihavenolifee
yochananmarqos
Collection of Magisk Modules v2
Replies
1K
Views
1M
あなたの
あなたの

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 5
    Lughnasadh
    Lughnasadh
    HippoMan said:
    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?
    Click to expand...
    Click to collapse
    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 🙃
    View
    4
    zgfg
    zgfg
    Jaitsu said:
    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).
    Click to expand...
    Click to collapse
    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
    View
    4
    P
    pndwal
    forserg said:
    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?
    Click to expand...
    Click to collapse
    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
    View
    4
    bombadier
    bombadier
    HippoMan said:
    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?
    Click to expand...
    Click to collapse
    Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about it
    View
    3
    badabing2003
    badabing2003
    Elvara said:
    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.
    Click to expand...
    Click to collapse
    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.
    View
  • 1103
    T
    topjohnwu
    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
    View
    156
    T
    topjohnwu
    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!!
    View
    121
    Chainfire
    Chainfire
    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.
    View
    76
    nathanchance
    nathanchance
    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.
    View
    75
    T
    topjohnwu
    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
    View

New posts