yashsingh1/xdaforums huggingface dataset:
[Magisk] Badger50:
Yep, that's about right. After it boots to the OS, do a minimal setup, and leave the lock screen set to swipe. Then, go back into bootloader/fastboot mode and install the twrp.img. Once in temporary twrp, flash the twrp installer zip, then a custom kernel(highly recommend) then the magisk.zip. As far as the OTA mishap, I'm not sure if you were on stock kernel/recovery before you started. The good thing is, that going forward, you won't have to mess with OTA's anymore, and the procedure is petty simple and much more reliable than messing with prepping for OTA's after you've been rooted :good:
[Magisk] kmccmk9:
Interesting, previously I wasn't using TWRP (mainly because it wasn't available at the time). Is this required? Also why do you suggest custom kernel? I was on stock kernel and stock recovery but rooted with Magisk previously. Also how is the OTA update process going forward then?
[Magisk] Badger50:
You won't need to worry about updating via OTA, you'll fastboot the monthly updates just like your getting ready to do. Twrp isn't necessarily required, it's just easier flash kernels and such. You could root the way you did before with a patched boot.img if you wanted to.
[Magisk] kmccmk9:
Thank you for all the help. So next time there is an OTA I shouldn't bother trying to do it the way I did it before and just download the full image and flash-all without the -w?
[Magisk] Badger50:
Bingo! You got it????
[Magisk] ahhl:
You know what. Now it work. I flash magisk again using magisk manager then I test safety net. It passed. Previously it failed.

Then I tried flashing one of the module. It works.

Another question if you don't mind,

I have island and icebox installed.

I noticed I have magick manager for island too. Should I enable enable multiuser mode to device owner managed? At the moment

It set to device owner only.

What should I do? Magisk manager not fully installed inside island. No full menu.

The apk I want to run, stall inside island. Log attached
[Magisk] David_#27:
Hi again everyone!

I was lately trying to flash magisk on my redmi Note 4(mido) using any recovery( either Redwolf TWRP or standard TWRP) and the result of flashing was an error which said that it had failed to mount vendor...

Do you know why it asked me to Mount vendor, because it is the first time it did!
[Magisk] Didgeridoohan:
Worth a shot, no? No need to ask really, best way to know is to test... With "owner managed" it'll only allow the apps already in the su database. With "user independent" it'll keep a separate database.

Logs...
[Magisk] David_#27:
Do you want me to post any log of the list?

These are the only logs I can give you:

1. Recovery log: https://drive.google.com/file/d/1f_BIHnpqt4rgWUiDup8z_hXKwtQL8t2E/view?usp=drivesdk

2. Kernel log: https://drive.google.com/file/d/1hfO3kpZ6xc6dIEl4SRd6jRJncLJtwNvj/view?usp=drivesdk
[Magisk] kutysam:
nope. never got it to work :(
[Magisk] jenslody:
Did you try to hide the app and hen repackage the manager and clear the app's data ?

If I do it, the app does no longer stop immediately after start, see the screenshot.
[Magisk] Didgeridoohan:
The recovery log is the one...

Questions:

You said it's the first time it mounts /vendor. Does that mean you've installed Magisk before, without issue?

If so, what's changed? Have you updated your device? Updated TWRP? Or are you only trying to use an updated Magisk zip?

Does an older Magisk release work?

Have you tried using the v16.3 beta?

Have you tried patching your boot image with the Manager and then flash that manually?
[Magisk] patrickdass:
Hey, figured but out. The app searches for the magisk package name along with the usual safety net stuff.

There's an option in the magisk app to change package name or hide the app. The UOB app will then work.
[Magisk] demonoidmaster:
Js but if you're able to boot into twrp (if you don't have that then flash it via cmd in windows) and then it'll be and to connect to your pc like any other storage, copy over your important stuff before you nuke your device with the -w command lol
[Magisk] alien.baba:
after flashing "patched_boot.imag.tar" with odin successfully, my device shows

"Verification Failed"

Need to reset

what should i do now?

Please reply soon
[Magisk] AjOzzo:
How Can i fix crash of Pokémon go?

Pokemon go find to magiskroot?

Inviato dal mio SM-G920F utilizzando Tapatalk
[Magisk] alien.baba:
Open Magisk, go to settings and tick "Magisk Hide"

Now select your app you want to hide root access then run your app.

Boom. it works for sure.
[Magisk] AjOzzo:
you used pokemon go??

Im use magisk 16.0 but Pokémon go find the robot

Inviato dal mio SM-G920F utilizzando Tapatalk
[Magisk] jenslody:
You need the 16.3 beta to be able to hide root from recent PoGo.
[Magisk] AjOzzo:
do i need terminal emulator script?

Inviato dal mio SM-G920F utilizzando Tapatalk
[Magisk] usernametaken53:
So i don't know if anyone can help me but i'm gonna try anyway.

Rooted my Pixel 2 with the latest stable Magisk, install went fine and my device is rooted.

I can't install any modules though, it fails everytime. (I don't want to flash via TWRP because it's unstable af at the moment on the Pixel 2)

Error message looks like this

Flashing

- Copying zip to temp directory

- Installing Multi_Touch_Fix_8.1_P.zip

****************************************

Please install Magisk v15.0+ !

****************************************

Failed !

! Installation failed

Any idea on how to fix this ? Busybox is installed :rolleyes:

Any help would be appreciated !
[Magisk] jenslody:
For MagiskHide ?

No !
[Magisk] AjOzzo:
su

magiskhide --add nianticlabs.pokemongo

Ye for magiskhide

Inviato dal mio SM-G920F utilizzando Tapatalk
[Magisk] Didgeridoohan:
Usually fixed by reflashing Magisk. Just install again from the Manager.

Not necessary of you've updated the Manager to v5.6.4. You might have to do it for PoGo+ though. And it might also be detecting other root apps on your device. Look for advice in the Pokemon Go thread.
[Magisk] David_#27:
Thanks for your time, but in a strange way, I fixed it!
[Magisk] Didgeridoohan:
Care to share this "strange way"? Might help someone else... :good:
[Magisk] alien.baba:
I need some help if anyone can?
[Magisk] jhedfors:
You will need to provide information first, only then will you know!
[Magisk] alien.baba:
I have samsung galaxy On5 SM-G5520 G5520ZU1BRB1 Nougat

after flashing "patched_boot.imag.tar" with odin successfully, my device shows

Verification failed!

Unable to restart your device. The intergrity verification has failed. You must need to reset your device to factory default settings. This will erase all your data.*

Reset (button)

what should i do now?

---------- Post added at 06:29 PM ---------- Previous post was at 06:25 PM ----------

I have samsung galaxy On5 SM-G5520 G5520ZU1BRB1 Nougat

after flashing "patched_boot.imag.tar" with odin successfully, my device shows

Verification failed!

Unable to restart your device. The intergrity verification has failed. You must need to reset your device to factory default settings. This will erase all your data.*

Reset (button)

what should i do now?
[Magisk] Saint Wacko:
I'm having an issue with MagiskHide that hopefully someone can shed some light on. When I restart my phone, the SafetyNet check fails and the MagiskHide list doesn't have anything checked. I have to toggle MagiskHide off and back on in the settings before it will pass SafetyNet and show the apps it's supposedly hiding from. However, even after doing that, the Play Store (which is checked in the list) still won't let me install apps that require SafetyNet. Any ideas?
[Magisk] mtkmanjaro:
Hi there, i have a trouble with magisk, i don't wy but always i install magisk my device become lagui, if i install any module is turning worse. I use the last build of magisk

My device is Lg g3 d851 runing Lineage 14.1
[Magisk] Didgeridoohan:
First issue: Sounds like there's an issue with the setting for MagiskHide and the Hide list. Post a Magisk log or a magisk_debug.log.

Second issue: https://www.didgeridoohan.com/magis...and_other_apps_wont_install_or_doesnt_show_up

If you can't provide anything to go by (logs, etc), that's gonna be a hard one to troubleshoot. Haven't heard about that one before... Could be that you have a root app that's poorly written and doesn't work well with Magisk, but that's just a wild guess...
[Magisk] David_#27:
I fixed it and the solution is in that thread: https://xdaforums.com/redmi-note-4/help/device-t3772944
[Magisk] edzamber:
Hi,

I havn't Any Magisk.img into /data but all stuff is in /sbin/.core

Magisk working but i can't use this script witch need Magisk.img into /data

https://www.google.fr/amp/s/xdaforu...h-market-links-theme-ready-apps-t3447494/amp/

Does someone have an idea why and how to solve this ?
[Magisk] Didgeridoohan:
That's normal if you've updated you v16.3. All backwards compatibility symlinks (/magisk, /data/magisk.img, etc) have been removed, since they cause more problem than it's worth.

The script need to be updated to work with Magisk v16.3+.
[Magisk] edzamber:
Thanks :good:

I solve it by updating script myself.

Change

MAGIMG=/data/magisk.img

To

MAGIMG=/data/adb/magisk.img

:cool:
[Magisk] alien.baba:
I have samsung galaxy On5 SM-G5520 G5520ZU1BRB1 Nougat

after flashing "patched_boot.imag.tar" with odin successfully, my device shows

Verification failed!

Unable to restart your device. The intergrity verification has failed. You must need to reset your device to factory default settings. This will erase all your data.*

Reset (button)

what should i do now?
[Magisk] Didgeridoohan:
You sure you meant to quote that post? :p

I have practically zero knowledge of Samsung (refuse to touch the damned things), but it might be a dm-verity thing. Did you keep it enabled or did you let Magisk disable it (default behavior)?

It's possible that you need to flash this zip after Magisk to properly disable verity:

https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
[Magisk] jcmm11:
You should also change

MAGISK=/magisk

to

MAGISK=/sbin/.core/img
[Magisk] tejaskadaskar:
I am on latest stable magisk 16 .I have enable magisk hide for my banking app but it still detects root.Please help.

Thank you.
[Magisk] Goutham Ganesh:
does it pass safetynet test?
[Magisk] alien.baba:
I tried both ways but still same error
[Magisk] princeofhuwaii:
Is there any module to enable call recording feature in android Oreo?
[Magisk] Ibuprophen:
I don't use this feature but, the following may be helpful for what you are looking for.

https://play.google.com/store/apps/details?id=com.killermobile.totalrecall

https://xdaforums.com/showthread.php?p=75310061

https://xdaforums.com/showthread.php?t=3740844

https://xdaforums.com/showthread.php?t=3692391

These are just helpful suggestions that can be a good start for what you need.

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Magisk] Tuxedo.Bond:
It does not work for me.
[Magisk] alien.baba:
Did Magisk Grant root access for sure?

if Yes then Download Root Switch

https://androidfilehost.com/?fid=817550096634777108

and grant root access.

Now untick the switch and try your app now.

---------- Post added at 05:17 AM ---------- Previous post was at 05:08 AM ----------

I don't have twrp. i used "patched boot.image.tar" with magisk.

I used with and without dm-verity both files.

I flashed it with odin successfully. but after reboot it shows this error

Verification failed!

Unable to restart your device. The intergrity verification has failed. You must need to reset your device to factory default settings. This will erase all your data.*

Reset (button)

now should i reset my phone?
[Magisk] Stoov:
After updating resurrection remix on Redmi note 4 I cannot install magisk anymore as twrp always gives the error cannot mount system/vendor and error code 1 tried the patched boot image sent me into a bootloop tried restoring the boot.img then installing magisk still the same error

I don't use suspersu & also tried magiskuninstaller
[Magisk] alien.baba:
Reinstall your updated official firmware then unlock debugging and oem. After that try to install magisk without twrp with patched boot.imag
[Magisk] Didgeridoohan:
If you mean Pokemon Go, it might be detecting other root apps you have installed, etc. Take a look in the PoGo thread, it's been discussed thoroughly...

For more on hiding root from apps:

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

In that case I'm no help. Like I said, I don't do Samsung.

If you want to reset your phone or not is up to you. I don't think it'll help in this case...

Log from patching the boot image would be nice to see.
[Magisk] AndroidHtc101:
Guys I cant flash magisk 16 with my BLOD patches nexus 6p any help please?

I'm on 8.1.1 rooted with su, the patched BLOD boot image and the 4core fix and patched TWRP.

Here the screenshot error I get. Thanks all for help
[Magisk] Didgeridoohan:
You answered your own question:

Read the output from TWRP again, and then go here:

https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
[Magisk] AndroidHtc101:
Thank you my first time installing and I should of read the FAQs! .
[Magisk] Stoov:
Do u mean I install the miui ROM or reinstall resurrection remix I guess its an issue with resurrection remix and if I install using adb the mi bootloader will be locked again and I won't be able to unlock it without the whole request process

Is
[Magisk] AndroidHtc101:
Diger I'm slightly confused. I uninstalled su as you stated in the post and I still get the same error...

If I flash another non 4core boot image so magisk can work my nexus 6p won't boot.

Thanks for your help
[Magisk] Didgeridoohan:
Are you sure you have a boot image free from other su patches? Looking in the N6P forums it looks like the BLOD patches should be compatible with Magisk.

https://xdaforums.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
[Magisk] Sagar Sharma01:
Just flash your stock boot img with odin
[Magisk] alien.baba:
No Need to flash full stock rom. I just flash original boot imag and my phone goes to normal again. but i ant to install gapps in my phone. that's why i need to root my phone. I tried everything but still no result

Link: https://xdaforums.com/samsung-galaxy-on5/help/sm-g5520-g5520zcu1brb1-nougat-root-twrp-t3772104

Check this thread no one helps me.
[Magisk] Sagar Sharma01:
[MENTION=4667597]Didgeridoohan[/MENTION] . I am facing problem with patched boot img method via MM.

It creates a patched boot img of v16.0 having 6 kb size in MM folder.

But with stable v15.3 and beta v16.2 or 16.3 it creates patched boot image of normal size.

And I also like to know that is flashing stock boot.img is enough to completely uninstall magisk without any of its traces left behind.
[Magisk] RandomPooka:
You were literally told to flash your stock boot image, and you corrected the advice by saying that you instead flashed your stock boot image and not the whole ROM.

I'll have to go back and see what device you're running, and use Google for you to see if what you are trying to do with your phone is possible or not.
[Magisk] Didgeridoohan:
The 6kb image is a known issue with v16.0. Use v16.3.

Flashing a stock boot image will disable Magisk, but all files will still be present on the device. Use the Complete Uninstall option in the Manager or the uninstall zip in recovery to remove everything.
[Magisk] Sagar Sharma01:
Both installer and uninstaller zip don't support my boot img says unable to detect boot img when i try to install it through philz recovery may be that's why direct install method isn't working 4me ( i discussed this porblem with u and you told to me to upload my stock boot img with recovery logs which i uploaded it in thispost but u didn't reply please submit it for future support and please tell me how many days or months or years it will take to support my boot img. Because for me only the patched boot img method is working 4 me.

Sorry , now the main topic, After flashing stock boot img and then osmosis unsu zip will completly uninstall the magisk without any of its traces left ?
[Magisk] Didgeridoohan:
With the new information that you're using Philz, you can probably stop waiting for it to work. Since you can patch your boot image with the Manager it's an issue with the recovery rather than Magisk. I remember our conversation, and I probably should have caught up on that at the time, but didn't... Sorry. Your device is supported, your recovery isn't.

The unsu zip should work as well. Best way is to use the option in the Manager though.
[Magisk] Didgeridoohan:
If you're on Magisk v16.0, why are you posting in the v16.3 beta thread? Answering here, since that's not quite the place for it...

Disable "Core Only Mode" in the Manager settings.
[Magisk] alireza_simkesh:
Hi, I just upgraded my Samsung S8 from Nougat to Oreo. can I simply use MM to root my Samsung S8 running Oreo stock ROM?

Or do I need to install TWRP beforehand and flash through recovery?
[Magisk] SXS4:
sure can't. u need to flash TWRP through Odin3 then flash root through recovery.
[Magisk] alireza_simkesh:
Tried that but it doesn't work. After flashing TWRP and flashing no-verity-op and Magisk through TWRP, my phone doesn't boot up. Its stock on Samsung logo (no bootloop, its just stock) and the phone gets very hot.

So I had to go back to 7.0 again.

This method also required me to format everything to change the encryption method. That's why i am wondering whether there would be a simple method for rooting Oreo with Magisk, something similar to Android 7.0.
[Magisk] sk8223:
Fate/Grand Order was running properly just 1 hour back, with one module (Vanced for Youtube) and Superuser permissions enabled. Something seems to have caused it to detect Magisk. I don't know if this is a Magisk issue or if the app was suddenly updated to detect Magisk... I don't think so, because neither the English nor Japanese version works (from Canadian and Japanese Play Stores).

I had recently changed the namespace in Magisk to Global, but changed it back to Inherit after FGO crashed for the first time. Then I rebooted.

I deleted the FGO and redownloaded it. I always force stop the app before going into Magisk, then clear Magisk from my recents before starting FGO. Still detects root and crashes upon starting it.

Then I disabled all of my root app permissions in Superuser (CF.Lumen, SD Maid, Solid Explorer, Titanium Backup, Internal Audio Plugin for RecMe) but the app continues to crash on start. I deleted data for the app again, but crashing persists. It's still able to detect root, even though the Magisk app is hidden properly.

I tried restoring Magisk, and then re-hiding it, then deleting the FGO app and reinstalling it. Then I added it to MagiskHide, force stopped the FGO app and entered it again. Still crashes. What's causing this?

I attached my log to this post. I checked /data/app and Magisk is hidden under another package name. Maybe the package name is too easy to detect? IDK.

04-07 17:31:42.204 472 517 I Magisk : proc_monitor: com.aniplex.fategrandorder (PID=8711 ns=mnt:[4026533769])

04-07 17:31:42.207 8717 8717 I Magisk : hide_daemon: Permissive detected, hide the state

I am using a treble-compatible version of Magisk 16.3 for my device from here. I'm on unofficial LOS 15.1 (treble support, 8.1.0) for Redmi Note 4 Global (mido).

Magisk passes SafetyNet and all 3 of my accounts show up as Certified in the Play Store. Greatly appreciate any help I can get. Thanks.

EDIT: I fixed my issue by restoring an earlier backup I had made of my ROM before messing about in TWRP (TWRP Restore > System Data, Boot, Vendor) and then flashed Magisk mido treble 16.3 again, since that's what you need to do to avoid a bootloop. Doing so resets Magisk settings, but keeps your modules and Superuser permissions. I'll leave this up to help others.

I don't know what caused FGO to stop working. Probably changing the namespace in Magisk to global and then back to Inherit again?

Here's what Magisk log reports now that the game is working again:

477 523 I Magisk : proc_monitor: com.aniplex.fategrandorder (PID=8010 ns=mnt:[4026533771])

8016 8016 I Magisk : hide_daemon: Permissive detected, hide the state

Basically the same thing as before. How odd. How did it start detecting Magisk in the first place? Any ideas?
[Magisk] wrongway213:
Hey everyone - question I can't figure out and not seeing anything in search either.

Flashing Magisk 16.3, even over an existing 16.0 installation, results in not seeing a /magisk folder in /root when I'm booted. If I use 16.0 it's there in MiXplorer, for instance. Magisk is still working and if I mount Magisk via TWRP I in fact see /magisk exists, but I can't see them when booted. Does anyone know why that could be?

I would just stay on 16.0 but I'm getting an issue with modules occasionally disappearing and I'm hoping upgrading Magisk will fix it as clean flashing did not. If anyone has any idea what's up, I'd appreciate it.
[Magisk] psychoela:
I think this future changelog for 16.3, new location root/sbin/.core/img
[Magisk] Didgeridoohan:
That's intended and is what [MENTION=4470081]topjohnwu[/MENTION] is talking about with backwards compatibility in the release notes.

The path for the Magisk image has been /sbin/.core/img for quite some time now and /magisk has only been kept as a compatibility symlink. Causes more issues than it's worth, so from v16.3 it's gone.

Any scripts or modules using /magisk will have to be (and should have been a while ago) updated.

That's in the changelog for v14.5(1455) already...
[Magisk] MasterSheea:
Hello to everyone!

Doogee Mix 2, error install magisk modules.

No possible to install any module.

! /data/adb/magisk_merge.img mount failed...

I have tried: ln -s /sbin/magisk /sbin/.core/mirror/bin/magisk, f2fs-loopback-bug-workaround, to reinstall magisk, to reinstall Boot partition, to flash modules via TWRP, to flash modules via flashify.

Nothing works.

Someone helps, please?
[Magisk] Ollibolli85:
Good morning everybody,

the hidden-mode from the current Magisk don't work with the newest version of my internet-banking-app, so i can't use it anymore because of the integrated root-check!

With the older version(s) of the internet-banking-app and the enabled hidden-mode of the current Magisk everything works fine!

What can i do?

Many thanks in advance!
[Magisk] Didgeridoohan:
Been reported before, but there's no solution. Seems like Doogee devices aren't compatible with Magisk.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] cry00:
ask,

can anyone help me, is there any tutorial to make a module from xposed into a module for magisk manager, i am very grateful for that help me
[Magisk] Ja_som:
You can't in most cases.
[Magisk] cry00:
Thx a lot bro..
[Magisk] Ja_som:
I'm not your bro...
[Magisk] gothicVI:
You're aware that magisk and xposed are two completely different things that work in completely different ways, are you?

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] cry00:
I have not understood much about this subject, thank you very much for helping me answer my question (y)
[Magisk] Sagar Sharma01:
So u r saying that my philz touch recovery(attached a screenshot) has the fault not MM.

But i like to know why MM v5.4.0 can't detect my boot img (screenshot attached) and it always doesn't give me 'unfortunately manager isn't working' message when i first open it after installing the app(attached log) But in case latest MM it gives the above error in its first opening after installion of app and after that app doesn't crash.

And Why D.I. isn't working 4me.

Clicking Update Magisk > Install > Direct Install (Recommended). Menu closes and I'm back to Magisk Manager "home" and nothing happens. Logs from me only pressing Direct Install (Recommended).

Direct Install log

MM 5.4.0 crashes

MM 5.6.4
[Magisk] Paschfire:
I suggest you try using a supported recovery, like TWRP.