osm0sis
Senior Recognized Developer / Contributor
No haven't seen that one yet, but you could experiment by adding one with Magisk and see if anything respects it. 
Magisk General Support / Discussion
- Thread starter topjohnwu
- Start date
I did test on my two Xiaomi phones, MIUI 12.5/A11 and MIUI 13/A12No haven't seen that one yet, but you could experiment by adding one with Magisk and see if anything respects it.
None of them had the /etc/nsswitch.conf file, or anything similar
I created the conf file as zipped and attached (XDA does not allow conf extension attachments) and copied the conf file to:
/data/adb/modules/hosts/system/etc
After reboot, the conf file was mounted to /etc (as 'required')
Initially, the conf file defines:
hosts: files dns
Then I tested the opposite (both options are prepared in the same conf file, one must be commented out, the other un-commented):
hosts: dns files
and rebooted - but the conf file seems to be ignored, /etc/hosts file has always the precedence over DNS (ads are always blocked for me via the hosts file)
PS: Maybe if somebody with A13 (latest Pixel update) would like to test
Last edited:
Thanks again for your whole advice.
However, still nothing of this would explain my first problem back here:
Magisk General Support / Discussion
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
forum.xda-developers.com
That was from a while ago (many magisk canaries). So lets start with basics.
What device
What android version
What other mods do you have
What version of magisk (canary stable beta and number)
What version of usnf are you running
What's in your deny list
All of that will make finding what is being seen by the apps easier . It is HIGHLY UNLIKLY that it is belching on strong integrity nobody to date uses that one, and if, by slight chance they are -which they're not - then the only remedy is to unroot and relock your bootloader and turn off oem debug.
Last edited:
Fastboot temp booting images doesn't work on all devices... Did you try flashing? PW
My answer has not changedHowever, still nothing of this would explain my first problem back here:
Magisk General Support / Discussion
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
Inspect the boot file you generated and see how it differs from the expected patched boot file.
incomplete boot image downloadedThis should be a clue.
Check app prerequisites and see if it can run with Android 7 or earlier... If it can they're not enforcing strongIntegrity...
Test if app can run on any unmodded (stock, locked) device launched with Android 7 or earlier (can be running later stock Android) or any later device known to have broken keymaster implementation (eg. many OnePlus devices)... If it can they're not enforcing strongIntegrity...
Nb. It is conceivable that an app requiring strongIntegrity might not check for this on certain (whitelisted) devices. However if this behaviour did exist the App would really be compromising the strongIntegrity attestation itself since there should be no way to bypass a failing verdict... Implementing such behaviour would allow any device to bypass the verdict simply by spoofing the device properties of any whitelisted device, rendering strongIntegrity really no better than deviceIntegrity...
PW
Last edited:
Moto edge 30 ultra
Android 12
I have magisk alpha 25210 + latest lsposed
I have shamiko and all apps that don't require root added to denylist + google services and store
I use unsf 2.4.0 mod 1.1
I also have hide my applist
snb used to work but stopped after a recent update
Attachments
Magisk 25210 is flawed, no mods are enabled or can run. Switch to 25209 or stable. Don't forget to roll back your boot.img too.
Usnf mod 1.1 was flawed did not kick in soon enough switch to 2.4.0 mod 1.2
Then try and see if apps still are blocked
He mentioned Magisk Alpha 25210..Not sure do we have active Alpha users who know the up-to-date situation there, bugs and fixes in the recent Alpha releases, etc
Oops i read alpha as canary and forgot that there are forks (poorly named imho) alpha and delta. Figured since this is the general thread they were using the general magisk, at my likely mistake.
Probably you forgot that I did mention that I tried with ALL the imgs: the bad patch, the good one, and even the original unpatched one. All of them gave that result.My answer has not changed
Inspect the boot file you generated and see how it differs from the expected patched boot file.
incomplete boot image downloaded
This should be a clue.
-Device: OnePlus 8 Pro
-Android Version: stock OOS 11
-Other mods: for magisk modules I disabled them all and tried but no luck, also using HMA (in the log it doesn't seem they check tho) and shamiko (tried with & without)
- Magisk version: stable 25200
- USNF: 1.2 (I tried Kdrag0n & Displax mod 1.2
- Deny list: play services, store, Android service library, android setup, device health survices, support component, package installer and a bunch of apps that need root hidden to work. I know I added a lot of unecessary apps to the list but I did that when I got fedup with those apps before
I don't believe they are checking for strong integrity but it seems like there's nothing working with them right now. Worth noting that few months ago they had an update and they were not working with denylist and shamiko fixed the problem. Also from play store info absher supports (android 5.0 and up), while SNB & Nafath supports 8.0 and up
From play store info "absher" supports (android 5.0 and up), while "SNB" & "Nafath" supports 8.0 and upCheck app prerequisites and see if it can run with Android 7 or earlier... If it can they're not enforcing strongIntegrity...
Test if app can run on any unmodded (stock, locked) device launched with Android 7 or earlier (can be running later stock Android) or any later device known to have broken keymaster implementation (eg. many OnePlus devices)... If it can they're not enforcing strongIntegrity...
Nb. It is conceivable that an app requiring strongIntegrity might not check for this on certain (whitelisted) devices. However if this behaviour did exist the App would really be compromising the strongIntegrity attestation itself since there should be no way to bypass a failing verdict... Implementing such behaviour would allow any device to bypass the verdict simply by spoofing the device properties of any whitelisted device, rendering strongIntegrity really no better than deviceIntegrity...
I know it is highly unlikely that they are checking for strong integrity but because I tried alot to make them work with no luck I am starting to think of the extreme cases they may use
I do not have a device running android 7 or earlier to check on them unfortunately but my device is oneplus 8 pro stock OOS11
Praps not a flashing issue... Not sure if flashing was actually tried... I said:
... Sorry, I only saw the reference to temp booting magisk-patched image also, per:
... If by "I tried with ALL the imgs: the bad patch, the good one, and even the original unpatched one. All of them gave that result" you mean with
fastboot boot xxx.img then you should try flashing... 
PWMagisk Alpha is maintained by one of the devs for lsposed and contributes to Magisk Official. The Alpha Canary is the same as the Canary Official, FYI.
With Magisk installed, in order to make banking app work I had to:
enable Zygisk, install universal safetynet fix module, and also enable deny list and add banking app to it (I thought this last one was no longer needed...)
Infamous banking app finally ran and began registration stuff. But the app is unable to scan the needed qr code: the "screen" is just complete black instead of the camera looking for qr code.
Do you think this could be related to Magisk further settings, or is it purely app's fault?
Thanks.
(I read that, supposedly, there were 3rd-party qr code apps which were able to scan the qr code and open it with another installed app, which supposedly could work for cases like this. Do you know something about this?)
enable Zygisk, install universal safetynet fix module, and also enable deny list and add banking app to it (I thought this last one was no longer needed...)
Infamous banking app finally ran and began registration stuff. But the app is unable to scan the needed qr code: the "screen" is just complete black instead of the camera looking for qr code.
Do you think this could be related to Magisk further settings, or is it purely app's fault?
Thanks.
(I read that, supposedly, there were 3rd-party qr code apps which were able to scan the qr code and open it with another installed app, which supposedly could work for cases like this. Do you know something about this?)
Similar threads
Top Liked Posts
-
2
I have run into it (every now and then) updating Magisk using a previously patch image.
- Magisk patched boot image detected
Bootloop and/or a forever (infinite) boot.
If it is just updating Magisk, use a clean (stock) boot image.
In your case, the stock Lineage 18.1 boot image.
For me, if the update failed..
- I normally flash the stock boot image back and reboot.
Since I still have the newer Magisk app (Manager) installed.
- Push the stock boot image to the device (if it is not already there).
- Use the "Select and Patch a File" option to patch the stock boot image.
- Pull the new Magisk patched boot image.- Stock boot image detected
- Flash (install) the new patched boot image.
---
To complicate my reply.
Depending on the device..
I use the hardware key-combo to boot into bootloader.
- Flash the current stock boot image to the device.
- Use fastboot to 'boot' a previously patched boot image.
- Then use the "Direct Install" option to install.
- Stock boot image detected
Hope it helps more than confuse.
Cheers.
1
I have run into if once or twice.
Sorry I do not remember exactly how I fixed it.
Might have been fixed in Magisk.
The message comes when the current Magisk (demon) is out of sync with Magisk.
The last time I ran into it, I do not remember what fixed it.
Try clearing cache and data of the Magisk app.
Assuming it is the same version that is patched into your boot image.
Clear the cache and data of the Magisk app and uninstall the app.
Reboot and install the Magisk app again.
Delete/data/adband let Magisk recreate it.
This will kill all modules and Magisk settings.
Good luck.
Cheers.1
Null pointer exception for me with this latest v1.4.0 and v1.4.1Yeah, I tried that last night... Either the fix is incomplete or I'm missing something as B/L status is still bypassed using LSP TEE Hide module...
PW
1
The old module TEE Hide just throw an exception in getCertificateChain method, so apps can't know if bootloader is locked or not. I will try to update AttestationSpoofer to bypass (again) the locked bootloader. They are using another cert class, because it doesn't call this method like previous versions.Yeah, I tried that last night... Either the fix is incomplete or I'm missing something as B/L status is still bypassed using LSP TEE Hide module... PW
-
8
Others have already addressed your question, but for me, the biggest benefit here is to have a safety valve in place where your inactive slot is bootable (without first having to flash the firmware) in case you get into a hairy situation where your active slot becomes unbootable for whatever reason. May be useful in some situations.87
Thanks, I realize it is only needed for custom Kernel cases.
I should add extracting vbmeta from payload.bin then in addition to boot.img / init_boot.img so that the step can be performed if the options are selected.6
Your wish is my commandI think it would be good to support, and I posted disambiguation due to some confusion above.
Rather than being 'highly discouraged' (it's not; it's plum necessary
) patching recovery partition is actually the only option for most A-only devices launched with Android 9 (legacy SAR, circa 2018, 2019) other than Xiaomi models!
Hope you reconsider... PW
Although with one caveat,
Yes I can tell if it is Ramdisk yes or no by running a script, but that requires unpacked Magisk, (for not rooted phone, I would need to unpack)
And although it is true that PF eventually unpacks to create a patch, but within the workflow, that stage is much later, and that stage is dependent on choices a user makes in the above screen.
Of course it could be worked out and workflow changed to automatically offer / not offer the choice.
Considering that the target audience is really minute if at all existent, specially considering that the tool has Pixel in its name, and people who have Pixel phone don't need it, and people who need them wouldn't be looking to tools for Pixel Phones ... lol
I decided the leave it up to the user the choice to have that option visible or not. (no auto detection)
The tooltip on option suggests not to turn it on unless ...
I hope that should be enough.6Update:
On a Pixel 5 device, I managed to have both slots bootable.
One slot rooted, and the other not, both on the same 2023-05 firmware.
The process is as follows (which PF will support OOB in the next release)
- Sideload full OTA
- Reboot to bootloader
- Flash patched image.
- reboot to system (observe root)
- Sideload full OTA
- Reboot to System (no patching, observe no root)
- Switch slot (observe root)
With Pixel 5, one is able to make changes to boot after sideload but before reboot.
It still needs to be tested if this works on Pixel 6, 7 * devices
I find flashing full OTA is slower than flashing full factory, but the benefit of having both slots bootable is a big bonus. -
1094This 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
