yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc

Yes.
[Magisk] guest4711:
If you can boot into recovery you should be able to find the viper folder in /data/adb/modules. If you can delete it your fine.

If your recovery does not allow this (TWRP has a built-in filemanager) you could try that using adb shell.

Booting into core-only mode of Magisk is a way too. Use any method to put .disable-magisk into /cache

If all of this is not possible you can try a special core-only Magisk somebody has build (don't know whether it was in Magisk main thread, in Magisk canary thread or in Magusk unofficial thread. But the search funktuon should be helpful.)
[Magisk] ilsaggio73:
then

xiaomi redmi note 4x / twrp 3.2.2-0 / MIUI 10.3 / Android 7

I can't install universal-safetymet-fix-v1.10.1.zip (error in twrp magisk is not installed)

but the check in magisk seems to pass ( see Attach )

and google tells me to be certified

I hid the root of the bank app via a special "hide" function and I also hid magisk, but the bank's app still detects the root. Is it possible that he is so "intelligent"?
[Magisk] Florhoff:
Bug on S10 G973F

Hi.. I've had a bug with stock rom rooted ASF3.

The installation was properly made but after the last reboot the device isn't root anymore. I've to flash Magisk 19.3 zip each time and so can I have back Edexposed and Modules going right.. what's wrong? Thanks for help..
[Magisk] Sjhingan:
Semi noob here. Running os5.0.8 on my op3t with TWRP and MAgisk. Trying to update to 9.0.4 using a modded firmware so that i dont lose data. Everything works well till i flash Magisk 19.3. if Anyone facing this issue can help me it'll be appreciated.
[Magisk] AZURDZ:
recovry data mod
[Magisk] Didgeridoohan:
Don't use Universal SafetyNet Fix. It was broken to start with... You don't need it anyway since you're already passing both CTS and basic integrity.

The app is looking for something that Magisk can't hide. The version you're using doesn't circumvent the UDS detection method, for example. For that you would have to use workaround described in the links you've been given, or use the Canary where it's been fixed (and will eventually make it to beta/stable).

Take a close look at the tips and tricks described in the link that's been posted several times, you'll likely find what you need there.

Are you booting with the recovery key combo? If not you'll boot to an unrooted system... Details: https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

Unfortunately noone here is clairvoyant (:laugh:), so in order to get any help you're going to have to describe what's going wrong, preferably with logs:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] ilsaggio73:
I mean are you telling me to use this?

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

But do I have to uninstall magisk completely?

Which guide are you referring to?

Is there not a way to understand which control the bank's app performs?
[Magisk] Didgeridoohan:
Me and [MENTION=4668495]wilsonhlacerda[/MENTION] have been posting links for you, left and right. I suggest you take a look there...

And you might want to stay away from the Canary builds if you don't know what you're doing.
[Magisk] ilsaggio73:
You say you don't recommend using canary? How else can I solve?
[Magisk] Didgeridoohan:
I'm saying that it's a good idea to know what your doing if you're going to start using the Canary releases. They are sometimes buggy... It's entirely up to you if you want to use them or not.

I've already given you the tools on how to (likely) solve your issue. It's all described in the link you've been given. Again, I really suggest you take a look at it before posting anything further.
[Magisk] lebeneur:
Hi,

Got a LG G3, unlocked on MM, TWRP 3.0.2.0.

Each time I try to flash magisk, go a secure message error next boot.

It seems like a missing something , a signature or something like this ?

I understood that it could help to submit boot.img to topjohnwu.

Where can I upload it ?

thanks !
[Magisk] Paxy:
Yea, I was wrong, it is not boot location. It has not bricked my device, but did not load Magisk at boot time either.

---------- Post added at 09:52 PM ---------- Previous post was at 09:17 PM ----------

As I could not find boot partition, so I have tried to modify 'update-binary' script to use my ROM boot.img to create new-boot.img and than reflash it over fastboot.

That worked !

Both Magisk Module and XPosed framework was detected. SupserUser had some issues (could not switched SU prompt).

BUT ! This boot image made an issue with phone, wifi and bluetooth, so none of wireless devices worked anymore.

Everything was back and fine again when I reflash original boot.img with fastboot.

MTK9520 phone (Zopo998)
[Magisk] Ph0z3:
I'd like to use this, but I'm on 4.4.4

What can I do?
[Magisk] Captain_Throwback:
Update your OS, or upgrade your device.
[Magisk] sanzNya:
i have xiaomi mi4s with xiaomi.eu miui 8. i cant instal magisk v6. it say installed/flashed on twrp but when i install superuser phh modules it say "you need magisk to instal this mod". i dont know why. is my device not supported?
[Magisk] DaGWaR:
Unroot

Instruction said i need to unroot an using cm 12 any have a thread on how to unroot cm 12 am not finding any.
[Magisk] tinymiata:
Nexus 5x with CM13 stable

Set this up on a nexus 5x running stable cm13 with twrp cm root turned on.

I coppied over the 2 files. phh su, magisk manager v1.2 and magisk v6

I installed super su and did the unroot all. it crashed when it was finished. and I uninstalled super su. Then I rebooted into twrp. I installed magisk and phh's su zips.

I rebooted and went to the play store and installed phh's su and then ran the magisk manager v1.2.apk.

when it started it asked if It could have root access and I gave it after I toggled it a few times to make sure it was happy. It seems to take a few after you toggle it then you see the status change.

After I installed poke-go and android pay with root toggle off and selinux toggle on.

Both apps turn on just like normal and so far work. I shut them down and remove them from background, go back to magisk manager and toggle root on. I fired up ti-back up works like always no issues at all.

Big Thanks.

:good:
[Magisk] JuergenZ66:
You need to bump your boot partition.

Just use cbump directly after flashing magisk and phh in recovery before you reboot.

You can find cbump here http://xdaforums.com/lg-g2/development/cbump-bump-current-boot-image-t3325186

follow the link, download is under Miscellaneous.
[Magisk] andrep182:
did you toggle root or the SELinux as well? because agent still detected my device as 'compromised' when I have root toggled.
[Magisk] mathy007:
Help

Still unable to get it working on HTC one M7 dual sim running stock lollipop 5.0.2 unable to detect boot image,is there anyway I can edit the binary script to detect my boot image? as I read some posts back
[Magisk] thomasyke:
Is it normal for phh + magisk to turn root on upon boot? even if i toggled root to be off and restarted my phone
[Magisk] gk1984:
As far as I know, yes.
[Magisk] RandomPooka:
Confirmed here. Root enabled by default so that root apps that run at boot can actually have their root, such as kernel management software.
[Magisk] Bamfist:
Android Pay doesnt work for me (cant add cards) on my oneplus 3 with magisk running? I have superSU installed as well would that affect it?
[Magisk] ilmank:
Hello guys, can anyone please tell me how to unroot my phh superuser?

I rooted with "phh superuser 17 magisk"

I really couldn't find a guide in how to unroot and dont want to do nothing wrong :(

Thanks!
[Magisk] Javs2010:
Sorry sent a message in wrong thread
[Magisk] putridfoetus:
Pretty sure you just create a new empty file called ”remove” in the /magisk/phh folder and reboot.
[Magisk] ilmank:
For real?

Anyone can confirm this?
[Magisk] lebeneur:
Thanks for replying ! Is this tools works as well with G3 ?
[Magisk] Didgeridoohan:
Confirmed. That's how you remove Magisk modules. At least until the new Magisk Manager is released.
[Magisk] ilsaggio73:
ok, i'm trying the UDS detection terminal procedure, but it doesn't work
[Magisk] Didgeridoohan:
UDS is merely one of the things that may be triggering the app. If that doesn't work, you try the next thing. And so on...

You have the guide, with a whole bunch of tools at your disposal. My handholding is now done for today. Good luck.
[Magisk] Nimueh:
Sorry to "push" the issue again [MENTION=4667597]Didgeridoohan[/MENTION] - the Magisk crashes I reported HERE last month are still happening and I posted the log HERE yesterday. I'm not sure if it got overlooked with all the other stuff that was going on? :angel:

Please help if you can, the random crashes are driving me nuts :eek:

Thanks :fingers-crossed:
[Magisk] Didgeridoohan:
I was gonna look at that, but none of the file explores I have on my daily driver seemed to be able to open the rar... Might try again later.
[Magisk] Nimueh:
Oh you should've said something - I'm so used to using .rar I didn't even consider that :angel:

I've attached it as a .zip now - I hope that's better? :fingers-crossed:
[Magisk] boogiepopfred:
So I really wanted to post a log but MatLog requires root access which I cannot grant without Magisk running...
[Magisk] Didgeridoohan:
It doesn't, but if you don't have root it takes a little more preparing:

https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/

And just using plain old ADB logcat doesn't require root:

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

---------- Post added at 19:22 ---------- Previous post was at 19:18 ----------

I was just browsing by, so I put it at the back of my mind for later. Far more important matters have been forever lost in those mists...

Will try to take a look when I have an opportunity, but be warned that my log-reading skills are somewhat limited.
[Magisk] Nimueh:
I appreciate you trying - those random crashes are driving me bananas lol. Maybe I'll get lucky and you (or someone else) finds the cause hiding in that log :fingers-crossed:
[Magisk] hga89:
Bootlooping with Magisk 19.3 on stock pie Pixel 3a XL

I have installed TWRP 3.3.1-6 on a stock android Pie 9 Pixel 3a XL followed by ElementalX kernel 1.05. I have multiple times then tried to root it using Magisk 19.3 but always end up in a bootlop back into TWRP recovery. Installing the factory image from 190705 made no difference.

I downloaded Magisk-uninstaller-20190604.zip and flashed it in TWRP. When rebooting, the phone booted into the Google setup screen. It thus seems the problem lies with Magisk.

To adress a potential faulty downloaded, I have downloaded Magisk 19.3 a second time, the size is the same but flashing it also results in bootlooping into TWRP recovery.

Does anyone recognize this problem?
[Magisk] dope77:
I have latest canary installed and magisk hide enabled, what does it mean with dangerous props?
[Magisk] plammekrog:
SM-N950F cihazımdan Tapatalk kullanılarak gönderildi
[Magisk] guest4711:
Something like debugging enabled or selinux disabled. If you really care use MagiskHide Props Config module to hide these settings.
[Magisk] Didgeridoohan:
That checks for ro.debuggable and ro.secure and if they're set to 1 and 0 respectively, the app will trigger.

Source:

https://github.com/scottyab/rootbee...java/com/scottyab/rootbeer/RootBeer.java#L251
[Magisk] feltan29:
Is it necessary to flash no-verity-opt-encrypt zip file while flashing magisk on MOTO G5s XT1795?
[Magisk] ilsaggio73:
I solved using UPDATE-unSU-signed.zip

Evidently the supersu folder remained when I was possessed by magisk

tnx ;)
[Magisk] philippze:
Hi,

I've got a problem since my banking app decided to auto update itself without it being enabled because now it detects the root. Although magisk hide being enabled for that app and also the random package name for magisk but it still detects it.

The app is called "vr securego" and I have got no idea what to do now.

Thank you for your help. :)
[Magisk] tribalfs:
Thank you. Finally got it to work even when connected to internet.

https://youtu.be/5hEC-L3TzN8
[Magisk] philippze:
Thank you! It works with the magisk canary version. :)
[Magisk] jcmm11:
I suggest one (or both) of

https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver

https://play.google.com/store/apps/details?id=com.rarlab.rar

File explorers with built-in compression handling are great but sometimes you need a more specialized tool. I have both of these installed. I prefer zarchiver but rar is a good backup for some issues.
[Magisk] AhmedPower:
Hello, I need to hide the root of magisk but every time I press the (hide magisk manager) button, a message of ( hide magisk manager failed) appears... Any help please?

Edit:Resolved
[Magisk] honki24:
Anyone know how to prevent Samsung Family Hub app from recognizing root? Screenshot of my log showing the app uses the command D/FamilyHubApplication(18419): isENGBinaryDevice

Of course I'm using magisk hide.
[Magisk] bafforosso:
Have you tried following the tips from this page : https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

If you haven't, please do
[Magisk] djdelarosa25:
Magisk seems to keep re-enabling USB debugging after every reboot even if I manually disable it.
[Magisk] garylawwd:
What version of magisk? What device? What android version? Custom rom? Logs?

Seeing as you're the first to report this maybe this isnt a magisk problem but something on your end.

Nevertheless there's no magicians here who can fix it without logs or some kind of info
[Magisk] djdelarosa25:
Magisk 19.3 on Poco F1 running LineageOS 16.

Talked to the ROM maintainer and he said that it's an old and known(?) issue. He said that he also experiences it and running Magisk in Core Only mode fixes the issue. Weird 'cause it's never happened to me before.

I'll try to send logs tomorrow.
[Magisk] garylawwd:
Oh so its something to do with your specific device?

Maybe try opening a question on your "questions and answers" thread in poco forums?

Your own device users maybe able to help you out a bit more seeing as they use the device daily.

Logs will surely help the cause.

Sorry for not being more helpful but I hope this issue gets fixed in either a future update of your rom or magisk but I would seriously consider reaching out to the poco users who use the device daily
[Magisk] guest4711:
When running in core-only mode fixes it it is probably a function of one of your modules installed.

Try core only mode whether it fixes it. If yes. return to normalode but disable all modules. Check again.

If still working enable one module per time and try again. So you should find the 'culprit'...
[Magisk] garylawwd:
Probably not seeing as he mentions its a known issue with the device
[Magisk] Didgeridoohan:
It's always a good idea to also write how the issue was resolved, so that it might help someone finding your post on the future.

You've already been given some info and tips, so I just want to add that Magisk has nothing to do with enabling or disabling USB debugging. If it's a ROM issue that's being exposed by having Magisk installed it's something that the ROM developer needs to look at...
[Magisk] dope77:
Disabled edxposed and rebooted, dangerous props was green, when enabling edxposed, it was red again
[Magisk] Didgeridoohan:
EdXposed is known to break the Magisk boot sequence. Probably messed up MagiskHide changing the prop values..
[Magisk] alphamale:
I'm using version 19.3 on pie rom. Wake gestures app by flair keeps losing root after the screen has been off for a certain amount of time and wake gestures quit working until a reopen the app. Just wondering if anyone knows of a fix or workaround
[Magisk] dr4go:
Keep in mind, that there also is a - so called - Blacklist feature, which you can find either in EdXposed Installer or Manager. Personally I'm using the Installer, but the same feature exists in the Manager as well though it might be differently named... Anyway...

First you need to activate that feature in the EdXposed Installer's EdXp Settings followed by a reboot... After that you'll find a Black/Whitelist tab there where you can decide if you're going to whitelist the apps, which you want to use the EdXposed features for, or blacklist them instead... personally I'm having the same Apps in the Blacklist than in MagiskHide... Everything green in Rootbeer...
[Magisk] blackbirdsinging:
It's been a few years since I've rooted anything, now I've purchased a refurbished Galaxy S7 (Sprint, SM-G930P) which much to my chagrin is running 8.0 with baseband G930PVPSACSF1. (I had been hoping for a phone that hadn't had all the updates run on it) Is it possible to root using Magisk or should I return this phone and get something else?
[Magisk] dope77:
Nah, this won't do the trick. Edxposed as seen in many issues on github, is having conflicts with magisk and the modules. If I systemize an app, edxposed stop working. If i delete a system app(debloat), edxposed stop working. If I install a module that install an app as system(like viper4android, greenify4magisk) edxposed stop working. Tried installing module to change font, guess what happened? You guessed it right, edxposed stopped working. I mean by edxposed stopped working getting Edxposed not installed in edxposed manager.
[Magisk] jhford:
Magisk Hide

I can only get it to work if I open Manager (it's new name), switch off hide, close manager, open Manager, and switch on Hide.
[Magisk] dr4go:
If you say so...View attachment 4800483
[Magisk] Ilyana322:
Hi, I'm pretty new to rooting and I have a question regarding renaming Magisk Manager. Is there any way to have it named something else besides "manager" or "magisk manager"? I tried cloning the app but it wouldn't detect root, is it possible to fix that? Thanks!
[Magisk] palmbeach05:
I would refrain from attempting to do something like this, else you mess up things. Leave it alone.
[Magisk] zgfg:
To help hiding root use Hide (repackage) MM (from its Settings). However, that is only one thing you can try.

Depending on which method(s) particular apps use to search for root, you will need to try several other things (probably you will hide the root but no guarantee)

Search back in this thread, every day somebody asks the same/similar questions - you will find discussins (regarding particular apps - although off-topuc here), suggestions and a link to ("official') Magisk wiki how-to (try to) hide root.
[Magisk] Ilyana322:
What are the repercussions of doing something like this? It's pretty important to my project.

I only need to change the manager's actual name and the package name (which is accomplished by hiding Magisk Manager), but I need the name to be malleable.
[Magisk] palmbeach05:
I can and have downloaded mx player pro from a torrent. It was not just called mxplayer.apk, it had its version number and stuff in it. When installed, it still shows up as mx player. So no, your project will still reflect magisk manager as magisk manager. Stop trying to mess with magisk manager. Use it as it was intended.
[Magisk] blackbirdsinging:
One other quick question- I've been reading on XDA and other websites for about two days now and keep finding conflicting information- will Magisk allow me to root a Sprint Galaxy s7 if I don't have a custom recovery available for it? TWRP seems to only have ones for the international variant of this phone...
[Magisk] Didgeridoohan:
I'm curious what your project is...

When the Manager is repackaged, the new package name is saved in the Magisk database, so that Magisk for sure knows what app is the real Manager. That's why your cloning attempt failed.

You can always build a Manager yourself, with the app label of your choice (both when hidden and not). Magisk is open source after all:

https://github.com/topjohnwu/Magisk

---------- Post added at 06:45 ---------- Previous post was at 06:42 ----------

You can install Magisk without a custom recovery, by patching the boot image in the Manager and then flashing that to your device manually:

https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
[Magisk] iamnitsuji:
Update: General solution found!

My problem appears to be a variant of the general bootloop problem that can occur after ROM updates. It's most likely the Magisk modules causing the problem. They need to be uninstalled first for this to go well.

This is what works for me:

(1) Before installing the ROM update, make sure you are using the latest TWRP for your device and uninstall Magisk with the latest Magisk uninstaller.

When I had a problem, the latest Magisk uninstaller was two months older than the latest Magisk. For whatever reason, only the Magisk version that was also two months old worked and upgrading it triggered the bootloop.

(2) Reboot to system and verify that you are not rooted.

(3) Reboot to TWRP. Flash the ROM update. Flash TWRP recovery, if your ROM update overwrote it. Flash the Magisk version that was released around the same time as the Magisk uninstaller. Reboot to system. Reinstall your Magisk modules :(.

Eventually, the wonderful Magisk devs released an updated uninstaller. From TWRP, I used it to uninstall 19.1 and then installed 19.3. Previously, upgrading always gave me the bootloop. This worked perfectly! :victory:
[Magisk] kancrutt:
anyone knows why some apps not works with Magisk Hide? but works when uninstalled Magisk Manager
[Magisk] zgfg:
Magisk hide is not the same as uninstalling MM. But there is an option to hide/repackage MM

Various apps detect root by various methods. Same Q/A every day, please roll back posts up to one or two days back and you will find much more about
[Magisk] Ilyana322:
I'm testing a security system and it knows to look for the name "manager" for when Magisk Manager is hidden, so I need to change the name of it.
[Magisk] blackbirdsinging:
Thanks for the link, I'll go over that info. Now I just gotta wait and see if anybody figures out the v10 bootloader, lol.
[Magisk] Didgeridoohan:
What system is that? Sounds like looking for "Manager" in the app name would have the possibility of generating a whole bunch of false positives...
[Magisk] Adityas95:
Magisk v19+ working only in coreonly mode

Hi

Magisk v19.3 only works in Core only mode in Realme 2 pro in Color OS 6 (Pie), i tried everything to fix this issue but it always remains in Core Only Mode no modules works, however Magisk v17.1 works fine but many modules supports only v19+ so please suggest solutions, i tried v18, v19, 19.2, 19.3 these all works in Core Only mode but no full support i cant run any modules, only v17.1 is supported but most of the modules only supports magisk v19+.

i tried my best but no luck.

please help seniors

thank you
[Magisk] Didgeridoohan:
When you say that it only works in Core Only Mode, do you mean that you can't exit Core Only or that Magisk doesn't work at all unless you activate it? Details are important...

And what do you mean by "tried everything"? More specifics would be good for anyone trying to help.

Lastly, it's also a good idea to provide logs when asking for help:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] Adityas95:
Yes it always remains in Core Only Mode, Cant exit from Core Only mode.

i tried v18 to 19.3 and even i tried Canary builds but nothing worked.

v17.1 ver code- 17100 only works with full support.

Tried to exit from Core Only Mode but unable to exit, it remains in Core Only Mode always.

Is magisk log helpful?

---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------

Yes it always remains in Core Only Mode, Cant exit from Core Only mode.

i tried v18 to 19.3 and even i tried Canary builds but nothing worked.

v17.1 ver code- 17100 only works with full support.

Tried to exit from Core Only Mode but unable to exit, it remains in Core Only Mode always.

Is magisk log helpful?
[Magisk] Didgeridoohan:
Canary (debug release) log, please.
[Magisk] Adityas95:
please check this is what i get after saving logs

please check - https://pastebin.com/R7V6hja9

thanks