I have it... Only have A11... Wondered if A12+ users still need to take measures... Since readme.md still says it's broken too... PW
Magisk General Support / Discussion
- Thread starter topjohnwu
- Start date
I have not encountered the problem with Termux on my Pixel 3 with LineageOS 19 (Android 12), nor on my Pixel 2XL with LineageOS 20 (Android 13).
I removed Magisk root in recovery with uninstall.zip, and nothing completely solved the problem, still TB checker open error ... I have no idea 
Flash your stock boot.img. This will unroot your device 100%.I removed Magisk root in recovery with uninstall.zip, and nothing completely solved the problem, still TB checker open error ... I have no idea
The link doesn't work. Since you had sought help here and seem to have fixed it yourself, it would be in the fairness of things that you share the 'fix' here so that others are also enlightened.
Attachments
My problem was with LSPosed module. It was displaying "SEPolicy is not loaded properly", "Partially activated" in the manager. The problem was caused by Magisk or a cleared partition. So I had to disable/re-enable the module and reboot. After booting it was fixed.
I've updated my OnePlus 8T (A13) as always to KB2003_11_F.63. But I cannot be able to modify/update the hosts file (via LP to block ads), tried also with terminal but I cannot modify hosts file properties. I've flashed also via Magisk "systemless hosts - unified" by gloeyisk but with no success. Any tips to verify which is the problem?
Last edited:
On A13 and earlier, System is READ-ONLY on the file system level, you can not make any changes on the system partitions
If not familiar with and with the systemless root concept (present in Magisk since 2021 or so), please search, read back, study, there were tons of similar questions and answers
Eg, how AdAway+Systemless hosts mechanism works - no hard changes on the /system/etc/hosts file, Magisk mounts changes on every reboot
Etc, etc. The way how all systemless modules work
I've always used Magisk with systemless, also on A13 until 2 days ago. I think it's changed something
In the first post you wrote:
"But I cannot be able to modify/update the hosts file (via LP to block ads), tried also with terminal but I cannot modify hosts file properties"
That's not systemless approach but hard changes that are not possible on the read-only System As Root (SAR)
yes I've tried also manually to modify (didn't know that was not possible). Then everytime I've used LP that patch/update (I don't know how) the hosts file adding the new lines to block ads, but after this new update seems changed some logic
So again, this Google's concept with read-only System is not new, we all live with that here since 2021 or so (depending on devices, ROMs, Android version, etc). And the corresponding systemless root was introduced to Magisk way back to provide the method to overcome the problem
If it hit you just now, then good (or bad) for you - but you will need to read about, learn and to live with that...
Sorry, it's not a short story to explain you now what can you do, etc, in few lines. Everything what is needed can be found in this thread, AdAway thread, etc
Btw, do not use Magisk Canary 25210, you will never make Systemless hosts (and many other modules) to work - but that was also extensively covered in the posts here during the last three weeks
So maybe it's the latest version the problem, is there a procedure to go back to a previous one?
Without going into detail, 25207 was a bit broken and 25208 worse... some fixes came with 25209 but (livable) issues remain... 25210 was badly broken...
Easy method to roll back (bypass downgrade prevention while retaining root):
Rename 25209 or 25206 .apk to .zip and flash as a module from Magisk App and reboot... Uninstall 25210 Magisk App, then install proper (25209 or 25206) .apk package.
PWTry to understand what you are fixing before you try to fix it.
Make sure you are really doing, now, what you used to do.
When you "edit" a hosts file, exactly what file do you edit? The full path matters.
If you used to get away with editing /system/etc/hosts, you will probably have to change your procedure.
If you used to edit /data/adb/adaway/system/etc/hosts and then reboot:
- if you forgot, and tried to edit /system/etc/hosts, just go back to doing it the right way
- if you did exactly that this time, and it's not working, read about the Magisk versions that are not working -- *now* is the time to "roll back" Magisk
It's that [email protected] you'd be very 'Lucky' to get away with on XDA.
Similar threads
Top Liked Posts
-
2
These posts are from 2020 magisk has evolved greatly since then.
Please layout your question for a modern audience. State your device, magisk version android version and issue clearly.
Thanks it'll be good to provide help to you.
Especially since the first post you quoted refers to a post that at that time hadn't been created -
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
New posts
-
[Tool] [Windows] [Kitchen] 「CRB」 [V3.2.5]- Latest: elfgoktas57
-
