yashsingh1/xdaforums huggingface dataset:
[Magisk] topjohnwu:
Thanks, title changed

Yes, you might want to include phh's root app to prevent confusion.

Could you give more info? Boot logcat etc?

Yes, I can take a look at it. It should be simple to implement :)

I don't use CM roms myself. If you can remove root completely from the PATH, you can take advantage of the Android Pay compatible feature of Magisk

I already stated the method to uninstall Magisk in the instructions. It is simple, and I don't think it requires an uninstaller.

Yes, flash v86.3 in my systemless Xposed thread. It is Magisk compatible (actually only works with Magisk)

1. Anything is possible :)

2. 32 bit binaries will work on 64 bit systems.

Just flash the systemless xposed zip. It is shat simple

This busybox is complete with key features used in Magisk, I think it is good enough
[Magisk] topjohnwu:
Yes I remember your name too :)

I still remember your internal storage swap mods

The good old Senny
[Magisk] mobileman88:
Already answered
[Magisk] ShapeShifter499:
[MENTION=4470081]topjohnwu[/MENTION] I no longer can run a chroot using "Linux Deploy". I get the following error. Any ideas?

/ ... mount: mounting /dev/loop2 on /data/local/linux failed: Input/output error
[Magisk] bumpaneer:
I'm stuck with bootloops on a HTC One M9 developer edition. The log file appears to show a clean install. I have attempted to gather a logcat, but the phone doesn't seem to make it far enough into the boot cycle for adb to connect. I'm not sure how else to gather any logs that may be helpful.
[Magisk] Black_Eyes:
If i understand correctly, after flashing Magisk, if i want a custom rom, then that custom rom must have Magisk support built-in?
[Magisk] N00dle:
So I removed super SU. Uninstalled Xposed installer, flashed through TWRP Magisk, flashed phh, then flashed Xposed from this thread.

Magisk opens but then then when I try and use the toggles to turn off root to try and use Android Pay it doesn't work and can't turn root back on?

Confused
[Magisk] intruder16:
No. Read again. It should work on custom roms as long as they don't have their own superuser like CM. Most of them won't support AP anyway. You can try removing built in su and flashing Magisk.
[Magisk] Ofthecats:
Perhaps a separate help thread?
[Magisk] ianmacd:
[MENTION=4470081]topjohnwu[/MENTION], a question for you:

I'm running systemless SuperSU (2.76) and systemless Xposed (86.2). I have no TWRP on my S7 Edge, so I usually root with CF Auto Root and then do everything else with FlashFire. Obviously, if I follow the instructions above, that's not possible. I would return my device to its standard firmware and then have no way to flash the Magisk ZIP, the SuperSU ZIP or anything else.

So, what would happen if I simply used FlashFire to live-flash Magisk onto my current system? One concern is that that would leave me still running an unmodified SuperSU 2.76, and I have no idea if that's compatible with Magisk. I realise you provide a modified version of SuperSU, but it's unclear -- even after reading everything -- whether its use is optional or compulsory.

I couldn't care less about Android Pay, so all I want to do is continue to use systemless Xposed in the future and reap the other benefits that Magisk has to offer. What is the best way to accomplish that without TWRP?

Thanks in advance.
[Magisk] ChiefIlliniwek5:
Has anyone had success getting this root/xposed method to work with a CM13 build?
[Magisk] elreydenj:
+1 for this. May be a long wait for official Android N.
[Magisk] mykenyc:
Okay so after trial and error, sweat and tears, beers and cheers i got Substratum/OMS to work oh PHH Super SU. (over exaggerating)

This is the steps i did:

1. Install your desired Rom, Stock android preferred, but i prefer almost stock Rom with OMS support and not legacy mode.

2. Install Kernel (if custom unless ElementalX i read stock preferred), then Install Magisk and SuperSU PHH flashable zip version of course all in TWRP.

3. Finish the initial setup by adding your accounts etc, afterwards immediately intall PHH SuperSU app from the Play Store.

4. after Installed open up Magisk app and disable Selinux Toggle to off.

5. Go into all your apps in setting and give full permissions (storage etc) to both Subsrtaum and Masquerade (if your ROM doesn't have Masquerade i believe you won't be able to use OMS support not sure).

6. Now open up Substratum app and it will ask for SU permission, accept of course and Roms with Masquerade should also ask for SU, without disabling SELinux for the time being it never ask for Su for some reason.

7. After all of that both Substratum and Masquerade should both have Su access and can now apply themes as normal, i also re-enabled SELinux and everything was fine.

EDIT Something to note, after restarting my phone and applying another theme i had to disable SELinux again, so it seems when applying themes SElinux have to be disabled before applying.

I'm to lazy to read all the posts here, but i think the issue with the toggles was an issue with Pure Nexus right?
[Magisk] steveo17:
thanks! seems to work, i just don't know how to use tasker very well
[Magisk] DarkN3ss61:
If you go back to my original post with instructions #375 , I added some more to that. So that might help you out
[Magisk] paddy01:
So have the same question as post #43 but can't find a response to that. Having full stock rom(and thus stock recovery) on a Samsung S7 Edge I usually go for cf-auto-root but thought I'd go for this on the upcoming update.. Are there any Odin fladable version of Magisk perhaps ? Or is TWRP flash the only way to go?
[Magisk] helmiazrin:
Hi... i wanted to try Magisk on my Redmi Note 2 running Miui 8 rom lolipop 5.0 but i got bootloop after flashing. Here are my steps:

1- Reflash stock rom to clear any modifications to system

2- Reboot. Device boots up normal.

3- Reboot to twrp and flashed Magisk, phh's superuser and xposed v86.3 sdk21. All at once.

4- Reboot to system but stuck at boot.

Any idea how to get Magisk to work on my phone? Or maybe i did something wrong? Thanks
[Magisk] devilloki:
in log file ,script said "no enough space in device"

also,i found the boot partition'size is 24M,and the patched boot.img is 24M. [MENTION=4470081]topjohnwu[/MENTION] [MENTION=1842686]xd4d3v[/MENTION]
[Magisk] spartan018:
Moto X 2014 (victara) and latest TWRP (3.0.2-2, which fixes some issues I previously had flashing systemless xposed 86). Flashed everything back to stock to be sure, and flashed ONLY the Magisk zip as a test, which appeared to be successful. Powering off/on consistently and immediately sends me to the bootloader with the message "Boot failed" until I restore the boot image from a backup.

Oh well, back to SuperSU + 86.2. Hopefully Magisk v2 fixes the issues
[Magisk] ThomasC1970:
Work with Oneplus 3

Tested buying using Android Pay. It work with Oneplus 3 stock using

Magisk v1

Magisk Compatible phh's SuperUser

Magisk Systemless Xposed
[Magisk] devsk:
I am using compatible phh's SU and I notice that two of Automate's functions are broken: 1. set mobile state and 2. set location state. Both of them fail with:

android.os.DeadObjectException: Transaction failed on small parcel ; remote process died

Note that these 2 operations need root. The root is enabled for Automate and it is able to execute scripts as root user.

Anyone else using Automate around here? Notice the same thing?
[Magisk] anantharam:
I had restored my phone to stock image, and then installed the magisk_modified from your link and here is the boot_magisk.img that was generated from your modified zip : http://www.filedropper.com/bootmagisk

Let me know if it helps to debug the issue...
[Magisk] topjohnwu:
The update is live

News in a nutshell

Android Pay / Root discussion separate to another thread

Android Pay won't work with Xposed enabled, old method is still needed

OP added with rich information for developers

Changelog

v2

- Fix verity patch. It should now work on all devices (might fix some of the unable-to-boot issues)

- All scripts will now run in selinux permissive mode for maximum compatibility (this will NOT turn your device to permissive)

- Add Nougat Developer Preview 5 support

- Add systemless host support for AdBlock Apps (enabled by default)

- Add support for new root disable method

- Remove sepolicy patches that uses SuperSU's supolicy tool; it is now using a minimal set of modifications

- Removed Magisk Manager in Magisk patch, it is now included in Magisk phh's superuser only
[Magisk] qwerfaseeh:
How can we install it on S7 Edge Tmobile?
[Magisk] Pival81:
Does this support caf roms? (nexus5)

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Magisk] dancer_69:
Thanks, I will give it another try soon.

Please add the links of the other threads you created in 1st post so we can have access to them from here.
[Magisk] steveo17:
[emoji106]

Obvious question here:

How do we upgrade from v1 to v2?
[Magisk] gaganit:
Can't wait to try this.. do I need to restore boot.img to upgrade from v1?
[Magisk] topjohnwu:
You can directly flash it over v1
[Magisk] steveo17:
Ok without restoring the stock boot and such? Will I have to flash supersu and xposed again?
[Magisk] lover:
So magisk v7 is fully compatible with latest systemless SuperSU? And all feature works? No need for phh's superuser?
[Magisk] bayran321:
Ok, I deleted the phh in the magisk manager app, but the superuser app is a system app and need root to uninstall it.
[Magisk] WeirdSoup:
Oh... If you installed the magisk correctly, it should be the user app. That means you did something wrong. (maybe installed the system mode version?) Anyway, you can manually remove it by using the twrp's file manager. I think you should also check if there is a su binary in the /system/xbin etc.
[Magisk] soder:
How do I switch super user app? I've tried a few ways, but SuperSU can't find the binarys, and phh is uninstalled.

Magisk still working, but not the manager.

EDIT: I had to remove Magisk, and then root with supersu first. When that was working, I installed Magisk again.

/Söder
[Magisk] kgptzac:
If i'm understanding the announcement thread correctly... magisk v7 is dropping hide root feature and passing the responsibility to the two su developers. It is unfortunate as I think many non-developers who choose to use Magisk is because the easy toggle-able option to bypass root detection. And if I'm reading phh's post correctly, his hidesu's is not ready to bypass su for apps other than Pokemon Go and SafetyNet, all seem to suggest that end users like myself who bypass roots for other purposes should not upgrade, or risk making things that work now won't work afterwards.

Is this the case or am I missing something?
[Magisk] IRatchett:
AP doesn't work for me anymore. When I try to use it it says Android pay not supported. I have Magisk v6 and Phh Superuser. Safety net passes, does it just not work anymore.
[Magisk] NoWayIn:
Does Magisk also give me root? Will some of the apps I am currently using that requires root work if I use Magisk?
[Magisk] CrazyCypher:
Hy guys, I removed root using SuperSU in-app option, after reboot I pass safetynet. Then I reboot to recovery, input terminal command echo systemless and flash SuperSU, I reboot, I flash suhide, I reboot, I do not pass safetynet.... Why, can anyone help me please?
[Magisk] Rhoban:
You root again after flashing Magisk. But it has to be systemless root.

Are you sure the terminal command was correct? If it wasn't, SuperSU will flash in system mode.
[Magisk] WeirdSoup:
Since v6, most apps couldn't detect the (systemless installed) xposed(even if I didn't take any special methods to hide it). But now with v7, the xposed can be detected by those apps again. It's too bad because there are no more old versions...
[Magisk] westeight:
Finally figured out to get Magisk v7 working with Systemless Xposed 86.6 ... and SafetyNet, Android Pay and Pokemon Go WITHOUT needing to reboot :)

1. Latest LeeDroid V2.6.1 stable (Select SuperSu on install)

2. One clean reboot

3. Flash suhide (0.53)

4. Flash Magisk v7

5. Install Magisk v2.apk

6. Install the required modules through the Magisk Manager

7. Reboot & enjoy
[Magisk] zzj0311:
bug report

just flash magisk v7 on my nexus 6p and it's good to use,but a little bug annoying me is that the inline busybox can't be used by titanium backup as well as lucky patcher. Have it tested in the shell and all seems to work but not in the two apps.Tried to flash busybox alone but stuck in booting:( Hope there's a fix,thank you.
[Magisk] Nexus11:
Any reason why Systemless apps aren't showing in the app drawer or in apps settings ? Says Viper4 android is installed but no record of it actually being so. Could it be I'm using Nougat?
[Magisk] NoWayIn:
Thanks for the replies.

How would I go about installing Magisk on my phone? I have never installed it before and I have root with SuperSU by chainfire.
[Magisk] habylab:
Have tried, didn't work for me. A different ROM but did not work all the same.
[Magisk] putridfoetus:
And how does one accomplish this when system is unusable because of systemui fc'ing constantly? Is there something delete-able in recovery? I am getting the same thing, and wiping dalvik+cache doesn't help. All apps optimize, and then immediately get bombarded by systemui stopped working errors.
[Magisk] waylo:
There's no easy fix in these cases when it's not clear what the offending error was caused by and persists. Unfortunately the only true recourse is to do a full wipe and restart. I hope you have a data backup somewhere.
[Magisk] putridfoetus:
I do have backups, it's just frustrating trying to put together a module and when it fails you have to factory reset to get back to a working system. Not to complain, but with v6, i could just remove the offending folders with a remover module and boot back just fine...

Incidentally, has anyone had luck with making a module that uses both post-fs and post-fs-data? I'm really trying to avoid splitting into two mods or mounting a whole build.prop, and if i set the cache module flag to true, the entire mod goes into /cache which doesn't mount the system files i need. My last attempt, I manually created the cache/magisk/$modname folder and copied post-fs.sh to it and set perms to 0755. When I boot up, logcat shows a bunch of errors about unable to set permissions for a bunch of unrelated system apps.... I'll try to capture a proper logcat tonight when I have time to factory reset again.
[Magisk] Portgas D. Ace:
Did you install the phh's superuser app from Play Store after flashing?

Last that I know is that this is required.
[Magisk] :
I had to deactivate Xposed. Works now.
[Magisk] JudgeDread11:
Google play services for install apps and Google play services are not the same.

Google play services for instant said it's not needed to hide afaik.
[Magisk] LeandritoG:
What to do?
[Magisk] Didgeridoohan:
Sounds like the recovery got replaced by the stock one. You should be able to just flash or boot TWRP again. That log you sent earlier contained nothing but a bunch of SELinux denials and a very unexpected and abrupt end to it. If that was indeed the log you got from running "adb logcat" I have no idea how to help you fix that (short of wiping the device and starting over). I really do believe your best bet is to ask the creator of the mod you flashed for help, if you haven't already.

None of that is necessary. The only necessary part of Play Services to add to the Hide list (for passing SafetyNet that is) is com.google.android.gms.unstable, and that is added by default.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] Bxperiaz3:
Ive managed to return to the same state as earlier. Twrp booting to unrooted os w/o magisk. Thanks for your help. I'm going to try and dirty flash the os and magisk once more to see if I can get it to work. And the module I used wasn't a magisk one as such it was a system overlay all of which I've removed so I doubt that's the problem. If I can't get it to work then I'll start from scratch and install a fresh build. Just wish I knew what I'd done wrong so I can avoid it in future.
[Magisk] Redacted Kaos:
I have the lg v40( v405ua)sprint so im unable to install twrp, so i made the bootable image but when i flash it, it goes to the lg logo then just freeezes... any tips?
[Magisk] chisnz:
Magisk seems to work fine, but on every boot I get "Magisk Manager has stopped working" the beginning before the launcher home screen has come up.

Magisk Manager 7.5.1 (267)

Magisk 20.4 (20400)

Xiaomi Mi 9 running Xiami.EU MIUI 12, 20.5.21 (the same error's been present since versions of Xiaomi.EU back for a year)
[Magisk] zgfg:
Why don't you try with Canary - I have EMUI 11 on 9T and don't have a problem with Canary
[Magisk] martyfender:
The latest Canary build, 20415, is out.
[Magisk] ricosf415:
After installing my ID# changes of phone nearly everyday is there a way to stop this TIA
[Magisk] martyfender:
What do you mean ID# changes of phone? I only have Android tablets.
[Magisk] Bxperiaz3:
Hi,back with one last attempt at fixing this before a factory reset. So I figured out that yesterday I wasn't actually in a bootloop which might have been causing some confusion and the reason my logcat looked strange, my kernal isnt booting at all. I get to the first screen that says warning my bootloader is unlocked and then no further. It goes to fastboot then I can get to TWRP and uninstall magisk and then I can boot to system. Apologies if I didn't make that clear yesterday.

Ive probably searched through over 100 different topics on this issue and I couldn't find one proper solution, so this is more just a troubleshooting process at this point to see if there's a way we can fix this issue before I have to wipe and maybe it can help someone in the future. Just to recap, every conceivable module ,overlay etc I could find or think of has been removed.

In summary, flash magisk = no boot. Uninstall magisk = boot to system without root. If you have any last tips I could try that would be awesome. Thank you for your patience.
[Magisk] vandyman:
Have you tried to patch the stock boot. img. TWRP is a no go with most devices using Android 9 and above.
[Magisk] Bxperiaz3:
I havent tried that but I've used twrp to root the phone In the first place. This build was designed especially for android 10 and oneplus 7 pro apparently.
[Magisk] CriseekPL:
After last update of MIUI by xiaomi.eu the newest version of magisk 20.4 flashing properly in TWRP 3.3.1.0, but after successfull boot android magisk manager seems don't see this flashed package.

Send from my Redmi Mi9T with Tapatalk
[Magisk] Lughnasadh:
Have you tried different Magisk versions? For instance, if you are using the latest Stable maybe try the latest Canary, and vice-versa. Or if that doesn't work try a previous version than the one you are using.
[Magisk] Bxperiaz3:
I'm on 20.4 at the moment. I did try 20.3 but had the same result. I'll try canary and report back. Thanks

---------- Post added at 02:15 PM ---------- Previous post was at 01:54 PM ----------

Edit- Flashed Canary ,no boot, flashed 20.3, no boot and flashed 20.2, no boot the exact same results as 20.4. Really strange.

Flash uninstaller and I'm able to boot back to system. Is there some check magisk might be doing on boot thats stopping it from booting to system perhaps, something that's native to all the versions I've listed?
[Magisk] Droidphilev:
Hello all,

I tried to search for an answer but but i guess the keywords are to common:

I need to patch a kernel for a device i don't own. I do know how to patch kernels using Magisk so that's not the problem. The question is:

Does the patching needs to be done on the same device as where the kernel will be used for? Or it does not matter on what Android device i put the boot.img on (for example: can i patch boot.img for a cheap chinese phone with Nougat on a OnePlus with Android 10)?

Thanks in advance!

Phil
[Magisk] sjgoel:
I installed v.20.4 but did not see "Magisk Hide" option in the menu - to hide various apps from Magisk. Went back to 20.3 and it appeared.

What did I do wrong with 20.4?
[Magisk] zgfg:
MagiskHide option is present in Settings, but you must enable it
[Magisk] sjgoel:
Thanks. Sorry for the newbie question: but how to enable? I am now on 20.3 but when in 20.4 I did not find any such option.
[Magisk] zgfg:
Yes, you can patch on the other device, I do it sometines

E.g., I just patched (Canary) boot.img for Xiaomi Mi 9T, Android 10 on the not-rooted Huawei Mate 9, Pie, flashed and all ok

Actually I also checked MD5 checksum for that magisk_patched.img and it matches the checksum for the corresponding image that I patched yesterday directly on the Xiaomi Mi 9T itself
[Magisk] zgfg:
Screenshot but from Canary version (not using Stable but it must be there, too)
[Magisk] sjgoel:
Thanks a lot. Got it.
[Magisk] eustilou:
Yes, I tried everything you mentioned and the app still detects root.

Safetynet is ok with edxposed.

I blocked access to installed apps in XprivacyLua.

Magisk hide.

The app does blacklist ID' s, so I have to change it after every detection.

I also blacklisted Google play/services/framework in edxposed manager.

I also tried in work profile with Shelter.

Thanks
[Magisk] Lughnasadh:
I'm out of ideas. Maybe someone else has some but at this point it may be time to start fresh.
[Magisk] nesoler:
App Popular detects Root

I use the app Popular (Dominican bank) that always detects the root even if I have it in magiskhide. Someone could help me?
[Magisk] surajloharia:
You use edxposed ?
[Magisk] nesoler:
No. How do I use it?
[Magisk] surajloharia:
No its not required to solve the issue but need an extra step to hide app if using edxposed ..

All other apps are hidden successfully except the banking app you mentioned ?
[Magisk] nesoler:
Yes
[Magisk] surajloharia:
Then iam afraid its impossible to hide this app.

As they must be using some souce to detect the root and i think its all server side implementation

You passing SN .?
[Magisk] nesoler:
Any solution?
[Magisk] surajloharia:
Only the person from your country using same app can help as he may have found a way to hide

Just wait for others to notice..

https://xdaforums.com/showpost.php?p=77331765&postcount=99

Just read through may help

Hope for good :svetius:
[Magisk] nesoler:
Thank you
[Magisk] SiC0881:
Hello, i have a problem.

On my Ulefone armor 6e with stock rom i can't flash magisk files...

From magisk manager i don't have the option to flash direct and in bootmode i can't flash zips.

In this case i have to flash in fastboot? And if yes how i can save the original boot image?

Thanks to anyone can help me :)
[Magisk] jenslody:
Magisk Manager hidden ?

No folders with suspect names (like TWRP) ?

No apps that are known to need root (e.g. TiBu) ?
[Magisk] Bxperiaz3:
SOLVED!

In case anyone runs into this issue in future. I'm guessing something must have happened to the boot image because I fired up TWRP, cleared Dalvik, dirty-flashed the stock os, booted straight back to recovery, flashed TWRP again, then magisk 20.2. Then I switched slots and did the same thing and then rebooted. Now I have everything working again, magisk updated to 20.4 and no data or app loss. Very happy
[Magisk] nesoler:
Could you explain yourself better
[Magisk] Lughnasadh:
Glad you got it going :good:
[Magisk] Damianek420:
Hello.

Magisk 20.4 + xposedMod with LckyPth module and patched And10 LineageOs rom

When I restarts the android it gets a bootloop on the logo, but with TWRP -> reebot-> system it boot normaly

Reasons?
[Magisk] Lughnasadh:
Nobody will help you while having any warez installed.
[Magisk] jenslody:
Did you try to hide the manager by repackaging it with a random name (from it's settings).

Do you have folders of apps usually found on rooted devices or devices with custom roms (e.g. TWRP), if yes try to rename it.

Some apps test for it.

Do you have apps that usually need root, like Titanium Backup ?

Some apps check it.
[Magisk] Damianek420:
Warez? You mean LP or what ? So I unpatched android and removed LP. The problem still exists.

Restart

from system->bootloop

From Twrp>reebot>system>booting normally