Barclays app is detecting root even with Barclays app hidden and Magisk manager renamed. Any ideas?
Magisk General Support / Discussion
- Thread starter topjohnwu
- Start date
Hi,
I am running Magisk 18100 and Manager 7.0.0 (185)
Superuser works just fine. Apps are able to obtain root permissions, but when it comes to module, the installed one actually work but whenever I try to update them they all get stuck at "Found /data/adb/magisk_merge.img" or at "Found /data/adb/magisk_merge.img".
If I install through recovery they work just fine.
How can I fix this? I've already tried re-installing magisk, but no luck.
I am running Magisk 18100 and Manager 7.0.0 (185)
Superuser works just fine. Apps are able to obtain root permissions, but when it comes to module, the installed one actually work but whenever I try to update them they all get stuck at "Found /data/adb/magisk_merge.img" or at "Found /data/adb/magisk_merge.img".
If I install through recovery they work just fine.
How can I fix this? I've already tried re-installing magisk, but no luck.
Back on 17.3 because of the on/off safetynet issues with 18+ but it won't download the foss code to run the safetynet check. I say 'yes' to download the code then all that happens is a 'Safetynet API error'. I have a couple of other apps that run safetynet checks and they work OK, and safetynet is OK, just that MM won't/can't download the foss code.
Any clues as to where to start?
Ta.
Any clues as to where to start?
Ta.
The pop goes away like you say but there's no install button, just an update button, so i have to update to latest version in order to patch boot img which i dont want to.
---------- Post added at 11:02 AM ---------- Previous post was at 11:00 AM ----------
Are you running Magisk Manager v6.1.0? as the problem your describing i had on v6.0.1?
Yep, you're right about that. It is probably the way I've done that just have mistaken the folders as it was a while ago. Happy to point the good direction.
Cheers
Bingo! That was the problem. Installed 6.1.0 and all runs as expected now.
Many thanks.
Did you try to raise the timeout for the prompt?
If that does not help, switch "Automatic Response" to 'grant' in settings of MagiskManager.
Start your script with:
Code:
#!/system/bin/sh
PATH=$PATH:<directory you want to add>
<rest of script>
amnher
Senior Member
Fingerprint Error Xiaomi Redmi 4x Santoni
i had Fingerprint Error issues on Xiaomi Redmi 4x Santoni after update to v18.1 (1800), software:v7.00 (185), cant delete curent fingerprint, and fingerprint doesn't work at all when using to unlock screen.
i had Fingerprint Error issues on Xiaomi Redmi 4x Santoni after update to v18.1 (1800), software:v7.00 (185), cant delete curent fingerprint, and fingerprint doesn't work at all when using to unlock screen.
Figured out i needed to create a custom channel in order to patch boot image with an older version. Heres a link to the custom channel if anyone else needs it to downgrade who dont have a custom recovery.
https://raw.githubusercontent.com/ahac85/magiskfiles/master/Magisk173.json
- Apr 13, 2016
- 25,876
- 23
- 59,580
- 67
For the benefit of other users who might run into a similar issue I'd personally appreciate if you hadn't deleted your original post but amended it with your solution. XDA is about the sharing of knowledge.
I was having problems with Kernel Aduitor.
After updating to Magisk 18.1 & Magisk Manager 7.0 (1.85). Kernel Aduitor wasn't detecting Root. Tried clearing Caches in the Application, then in TWRP Recovery: Art/Dalvik Cache. Reboot.
Resolved the issue by completely removing Magisk Manager 5.30 (which must have confused the App, looking for file location).
Used the newest Magisk Uninstaller to completely clean of older Magisk. Then wiped Caches again to rid of orphaned files.
Reinstalled Magisk 18.1 through TWRP, gave Kernel Aduitor access to Root privileges & it started working again!
I am running CrDroid Oreo on OnePlus One.
I hope that is enough information.
After updating to Magisk 18.1 & Magisk Manager 7.0 (1.85). Kernel Aduitor wasn't detecting Root. Tried clearing Caches in the Application, then in TWRP Recovery: Art/Dalvik Cache. Reboot.
Resolved the issue by completely removing Magisk Manager 5.30 (which must have confused the App, looking for file location).
Used the newest Magisk Uninstaller to completely clean of older Magisk. Then wiped Caches again to rid of orphaned files.
Reinstalled Magisk 18.1 through TWRP, gave Kernel Aduitor access to Root privileges & it started working again!
I am running CrDroid Oreo on OnePlus One.
I hope that is enough information.
Similar threads
Top Liked Posts
-
1
Is EMEI IMEI in another language?
Please explain "as long as EMEI".
I can't keep track of your situation. The ROM IDs you posted a week ago do not make it obvious that your device has anything with version 17 while you are trying to install version 16.
I do not understand the country codes. Or the CSC, if that is something other than country code.
Maybe you still aren't trying to install the right ROM. Remember, at this point we don't care what software you wish you had. You are supposed to be finding a ROM that is meant for your device, maybe associated with your carrier, maybe tagged with your location. Possibly complicated by it cannot be older than what is already on your device.
Can you go to your service provider and tell them you need help? (If you bought the phone from someone other than your service provider, start with the person who sold you the phone.) The service provider should have some interest in helping you -- if you can't use the service, you won't keep paying for it.
Maybe you can install a custom ROM. Check other threads to see whether something like LineageOS has been installed on the same device, and whether the device then functions as a phone.1
Mmm. Not sure that will help either... You can open a GitHub issue if you're prepared to install Debug Magisk build and supply logs; Devs might help further.
PW -
5
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'd4
Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about it4
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 instead4
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.4
Not pushed yet... Looks like recent Android Gradle plugin upgrade just didn't build properly... Guess a new build may come once Upgrade AGP is reverted but may not happen till AGP upgrade is redone.
PW -
1103This 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 Thread156Hello, 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
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
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!!121Ah, 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.76Thread 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.75Hello 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
PW
