yashsingh1/xdaforums huggingface dataset:
[Magisk] nfsmw_gr:
I did that, it was actually a webview related error, fixed it by updating to the latest beta.

Guess I had a really old version or something by default.
[Magisk] qwer222:
Hi, because I need to root and unroot the phone frequently using the magisk manager patch boot img method, so either I download the latest version or old version of magisk manager, it will still point to download latest version of magisk before it patch the boot.img, unless I found the way to change the download channel settings to custom, I do found it in this forum. And of course I will continue to use the old version magisk because latest magisk not working on my phone.
[Magisk] martyfender:
[MENTION=4470081]topjohnwu[/MENTION] and others:

I personally know that to post on the github issues page that one must be on the Canary debug build, but no where on the release thread OP or on the OP of this page is it stated that is a requirement.

Why not change the OP of at least these main Magisk threads to point this out to people, especially considering there are many new users of Magisk.

Wouldn't it save considerable time sorting thru the issues?

And, yes I do know that there are always users who never read this stuff, go to the end of the thread and post questions that were answered on the last few pages, but maybe it would help?

Thanks to all here who try to provide great support during your free time.
[Magisk] jcmm11:
Try the latest Canary build. From the Canary thread:
[Magisk] Sagar Sharma01:
[MENTION=4667597]Didgeridoohan[/MENTION]

Magisk isn't authenticating superuser permission after installing Magisk v18.0 (via patched boot image method usin' MM v6.1.0 ).

I have a few questions.

1. How can i solve this issue. ( Root checker says root access isn't properly installed)

2. After flashing Magisk patched boot image, i switched on my phone , boot logo appears and then device restart but after this phone swithed on properly. So should i flash it again or not.

3. When my device switched on properly i installed a YT Vanced module (it installed and worked properly). But everytime when i reboot my device it shows optimizing 1 of 1 app. After deleting the module i didn't get that message.

I attached a log file and a screenshot

I am currently on mt6582 soc , Kernel v 3.10.54. , Android 5.0 lollipop.
[Magisk] avik735:
Facing a weird issue with Magisk 18. First time, I upgraded from 17.2 via Magisk Manager. A few days later, when entering Magisk Manager, it suddenly showed that Magisk was not installed at all, asking me to download Magisk 18. I already had it downloaded, so assumed a random glitch, and flashed Magisk uninstaller and then Magisk 18 via TWRP (I am on 3.2.3).

Then I reinstalled the OS (on Kenzolo's RR 5.8.5 on my Mi Max 2). Every now and then the issue reoccurred. Now, when the issue shows up, right after installing via TWRP and rebooting, it shows Magisk not installed.
[Magisk] RyTekk:
Does it mean that I won't have root?
[Magisk] Badger50:
Depends on your device and kernel. Some kernel Devs have a patch that doesn't require you to flash magisk again.
[Magisk] Dingo_HR:
I noticed problem with Magisk 17.x on my OnePlus5 on Oreo now I am on Android Pie and again o notice it with Magisk 18.

I am rooted but from time to time I have to go to Magish setting and disable SU and again to enable it.

Just that app that need root access to get popup to grant SU access.

Apps like Adaway with already granted SU note me that I am not rooted and have to do the same procedure.

1. I disabled battery optimisation

2. I need Magisk hide as some of my apps do not want to work on rooted devices.
[Magisk] ew:
For anybody that is passing SafetyNet right after reboot, but failing later (with v18) - I had the same issue. I reinstalled Magisk v18 in TWRP, erase cache & dalvik cache and all seems to be good now - passing SafetyNet all the time. See if that helps for you.
[Magisk] ahamling27:
The canary build boot loops too. :'(

I let them know in the canary thread, so hopefully they can look into it soon. Thanks anyway!
[Magisk] Pkt_Lnt:
"Telling" does nothing at all, zip, zilch, zero, nada. Getting logs (log how to) provides help to find and fix problems. Thanks! :good:
[Magisk] ahamling27:
I'm not asking anyone to fix my problems and I'm not here to whine, so I'm sorry if sharing my experience will just go unnoticed. So be it.

FWIW, I said in the canary thread that I will try and get a log for them. So maybe try not to assume too much, I just replied here to share what I found. :rolleyes:

Update: I got magisk v18 working on OS 9.0.3 for op6 by flashing magisk uninstall, then flashing magisk 17.3 and it successfully booted. From there I installed magisk manager and installed v18 just fine. Got all my modules installed again and everything seems to be working fine again. ?
[Magisk] zohair_:
Magisk damaged my recovery partition!

hello,

I have a px5 head unit. I was trying to get root access because I wanted to use 4G usb dongle on the unit.

I used Magisk, the offline patch option and flashed the image. Now I can't access the recovery options and I can't update the head unit. The patching process went very well: Magisk detected my recovery.img and showed me it was for arm64. I still have the log file it created during he patching process. When I try to reboot in recovery all I see is a black screen...!

Using the command: "setprop persist.adb.tcp.port 5555"

starts adb server lisening on that port but showes devices unauthorized when I tried to connect.

The command "setprop sys.rkadb.root 1" doesn't work.

I tried using adb over usb but it doesn't work.

If this post is out of place then I am sorry I don't see "post new topic" anywhere...!

thanks...!
[Magisk] Ibuprophen:
Just a personal thought/opinion...

There's nothing wrong with reporting what you had experienced, noticed, seen, etc... since knowledge is power. :thumbup:

Never feel that, what you had done, is wrong. Sometimes it's a challenge to express something in a way that you had intended. This is especially true for those who has a basic knowledge and isn't as familiar with the subject matter being expressed.

I also experience this challenge as well. I may be knowledgeable and experienced in various topics, I'm still learning too.

I just wanted to help pick up your spirits with a (positive) personal thought in response to your post.

I do wish you the best of luck! :)

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Magisk] ahamling27:
Thanks! I updated my post with a work around, got it working anyway,just weird that it took 17.3 to be flashed first, but it's all good now. I did save a log, but again I'm not even sure what to upload because it looks like it logged everything my phone did from a couple boots including the bootloops. Learned quite a bit, although I'm still a super noob when it comes to system logs.
[Magisk] blackthund3r:
+1 to this workaround.

Did you happen to have ViPER4Android installed before you uninstalled / installed 17.3 / upgraded to 18.0? I've just started installing my modules again on v18 after doing uninstall => 17.3 => 18 direct install upgrade, and since there is Bluetooth audio tuning built into OOS 9.0.3 now I wasn't sure whether to bother installing V4A again too.

So far I have Emoji One, OOS Native Call Recording Enabler and Systemless Hosts (+ hosts from AdAway applied) installed. The phone has been rebooted and all seems okay, and SafetyNet passes.
[Magisk] ahamling27:
I did not have V4A installed before or now. Sorry!
[Magisk] blackthund3r:
No worries at all, and thanks anyway! I was just trying to isolate the conflict between Magisk 18 + whatever modules were installed and OOS 9.0.3.

Ah well, at least it all works now. Having to install my modules again is a small price to pay to get Magisk 18, SafetyNet passing and the latest OOS.
[Magisk] Pkt_Lnt:
So sorry, I did not think you were whining, I apologize. My attempt was to nudge you along to offer more support to solve what was going on. I'm pleased you found a workaround, but that is not a solution to the bootloop issue to help additional people who will run into the same bootloop problem. I made no assumptions, I even thanked you for what you did and hoped you would provide logs if I helped you learn how. With over 9 million users on XDA, it is tough to follow all posts that someone makes in multiple threads, so again, I apologize for making you think I was giving you a bad time, I only meant to encourage you to use the info you had to learn more and provide more assistance to others.
[Magisk] ahamling27:
You are alright. I think I was just more frustrated in myself and took your comment as harsher than it was. I found a workaround that I was able to share for others and hopefully what was causing the bootloops will be investigated by more knowledge folks so no workaround is needed.

Sorry for getting defensive. Thanks for pointing me to the "how to logs" post, even if I was still unable to get any logs to help out.

Cheers!
[Magisk] NinjaBoyLao:
I'm not sure where else to post but several searches have come back with useless results, so I figured I'd just ask here.. I'd like to be able to use superuser privileges from an ADB shell while my phone is in recovery mode. TWRP is my recovery image, and I have the latest Magisk installed in "core only" mode, everything works as it should. The problem is that I recently broke my digitizer, so I can't touch anything at all on the phone. I'm trying to get the dumb pattern lock off so that I can try to use ADB while it's booted normally, instead of being stuck playing around in recovery mode.. ADB can simulate taps and touch events from the command line so I'm hoping I can swing something with that, otherwise I will be attempting to get a mouse connected in some way to use USB OTG stuff and maybe control it that way.

Please let me know if there is a more appropriate place for this question, it is directly related to magisk and the correct way to call it from an adb shell in twrp's recovery mode.
[Magisk] paarnoutse:
Magisk issue #907 in GitHub was created by [MENTION=4470081]topjohnwu[/MENTION] himself, to combine various submitted issues regarding Magisk Hide not working reliably. One of these referred (and now closed) issues is #900, which I submitted at 2018-12-22. That entry has logs attached to illustrate the problem:

- Magisk Hide working

- Magisk Hide NOT working (root detected)

The 2nd log just a few minutes later, for same (hided) app.

These logs were created while running the Canary v18.1 Debug version.

Nb.

At the moment I created these Canary v18.1 logs I still had included various entries in the hidelist as I used with older Magisk version for hiding Microsoft Intune Company Portal related stuff, like Google Play Store, Google Play Services, Google Services Framework, Phone, Phone and Messaging Storage and Phone Services. With Magisk v18 these magiskhide entries seems to be not required anymore. I later removed them from the hidelist in Magisk v18, but the MagiskHide issues in Magisk v18 appeared to be not related to these entries: even after removing them (and rebooting with clear dalvik/cache before) the problem still exists.
[Magisk] The Analog Kid:
After a lot of thinking as well as learning the basics on how to fix things (just in case) beforehand, I've just updated from v17.1 to v18 (stable) directly from Magisk manager 6.1.0... well, it updated smooth and beautifully with apparently no side effect issues after reboot. I'll keep in touch if anything stops or refuses working as expected. Happy 2019 to everyone!
[Magisk] chooks06:
Have you tried using a mouse? It would be better easier. I had touch issues before and the mouse helped a lot.

You can connect a USB mouse using an OTG adapter, or a wireless mouse, by plugging the receiver via OTG adapter.

Bluetooth mouse is out of the question unless already paired.
[Magisk] ashyx:
TWRP Recovery always has a root shell by default. Magisk su isn't required or even loaded in Recovery.

https://xdaforums.com/showthread.php?t=2786395
[Magisk] Didgeridoohan:
[MENTION=5761039]paarnoutse[/MENTION] Yes, I've seen your logs (and they're the best ones I've seen for the issue), but even those doesn't show much besides that proc_monitor sometimes doesn't seem to trigger for some apps/processes. Why? That'll likely need some more digging...
[Magisk] paarnoutse:
(deleted)
[Magisk] Didgeridoohan:
[MENTION=5761039]paarnoutse[/MENTION] I saw... That shouldn't have anything to do with the issue at hand and is normal behaviour.

[MENTION=6688529]Yak Batta[/MENTION] The fix for the issue that [MENTION=7934452]mrspeccy[/MENTION] found has not yet been introduced to the official builds. It's on the to-do list and you'll see it eventually (keep an eye on the GitHub commits and release notes).
[Magisk] malaysia_sWat:
To fix this issue ( apps with web view keep crashing ), you need to install chrome beta.

After installation go to, Setting> Developer Options> Webview Implementation> Select Chrome Beta.

Try open some apps :D, it works.
[Magisk] NinjaBoyLao:
TWRP Recovery mode ADB shell does not have root, I can't do any of the commands listed in this thread https://www.reddit.com/r/Android/comments/1r2zha/how_i_managed_to_use_my_android_device_with_a/

[MENTION=6323980]chooks06[/MENTION] I have done just that, the mouse lags like crazy and can't even be used to draw the unlock pattern. it barely clicks either i don't know what the problem is but it looks like the light on the mouse only comes on every other second or so, based on how it flashes just plugged into the phone.
[Magisk] jcmm11:
What commands, specifically, don't work?

What's the result of "whoami"?
[Magisk] mobileman88:
It will only have root if you are already unlocked.
[Magisk] Homeboy76:
Happy New Years everyone :)

Friendly reminder for the New Year

XDA etiquette

If someone helps you, etiquette requires you thank the person that helped you.

The way to do that on XDA is tap the thanks button/icon or tap the Developer's donate link.
[Magisk] chteh0721:
This is one of the module that i wish to install. After reboot my phone it never show up in my list of modules
[Magisk] martyfender:
Have asked here?

https://xdaforums.com/apps/magisk/xz-lxt-1-0-insane-battery-life-12h-sot-t3700688

Also, is your cpu listed in the supported devices?

If your device has TWRP try installing it booted into it. I have had some modules in the past that would not install directly, but installed fine in twrp.

Finally, I have been using lspeed and Kernel Adiutor to do this for some time.

Reading the description in the thread, it does sound good, though, for supported cpu's Mine is not: Intel x86 Cherry Trail Atom x5-Z8350.
[Magisk] chteh0721:
This is not the only module that I facing problem, magisk allow me install up to 7 modules only, and my phone is supported. This issue arise after recent update to Android 9, preciously I have no such problem so I'm wondering magisk support can give some clue how to solve this
[Magisk] Didgeridoohan:
That installation is quite broken, yes. But, you're gonna have to provide more info...

Does that module always fail, or only if it's the 8th module you install? Does it matter what order you install the modules, or does it always fail after 7 modules?

Try different modules, different flashing order, different variations to show if it's actually a Magisk, module or device issue. And make sure to provide logs as well (follow the advice and instructions in the link I posted earlier).
[Magisk] tezukaryoma:
Magisk hide wont work on miui dual apps, only 1 app of dual apps can hide under magisk hide v18, once revert to 17.3 all work again, both dual apps can hide ! Pls kindly help me. tq~~
[Magisk] martyfender:
https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] NinjaBoyLao:
the initial cp command to (i assume) get the database fails with a permissions problem.. very very weirdly, whoami returns "root" as the result, which i don't understand at all, since i should then theoretically be able to do whatever i need to with these database files
[Magisk] NinjaBoyLao:
I have solved my problem, albeit very roundabout way.. TWRP was in fact alreayd superuser, and the guide I was attempting to follow was very old. MY pattern settings database was located in a different directory, and I was able to delete my screen pattern and reboot to the default swipe up to unlock configuration.. however, i was still not able to see my device in ADB afterward. I was however, able to very buggily and laggily plug a usb mouse into my phone to somewhat control the screen, enough to double click on a notification and get the screen opened. after that, adb immediately found my device as i knew i had left usb debugging enabled, and i then went to settings through the android screen control program here https://xdaforums.com/showthread.php?t=2786395 and turned off any screen lock whatsoever. my next step is to buy or find a bluetooth mouse and pair it so that i can still make limited mobile use of my phone
[Magisk] soder:
Happy New Year! But, for me is started kind of bad. I got a OP3T with Magisk 18, and I flashed the Pix3lify module to just try it before I get my OP6T. After that the phone went in to a boot loop and I can't manage to boot my phone.

I tried to flash the Pix3lify module again in recovery, but the uninstaller didn't go through. I even try to disable it with some kind on Magisk manager for recovery mode, and also to uninstall Magisk with the latest uninstaller, but I get an Error.

Is there someone that might know what I shall try next?

I want to get back in the phone to do a Titanium Backup to prepare for the next phone.

/Söder

---------- Post added at 11:01 AM ---------- Previous post was at 11:00 AM ----------

Happy New Year! But, for me is started kind of bad. I got a OP3T with Magisk 18, and I flashed the Pix3lify module to just try it before I get my OP6T. After that the phone went in to a boot loop and I can't manage to boot my phone.

I tried to flash the Pix3lify module again in recovery, but the uninstaller didn't go through. I even try to disable it with some kind on Magisk manager for recovery mode, and also to uninstall Magisk with the latest uninstaller, but I get an Error.

Is there someone that might know what I shall try next?

I want to get back in the phone to do a Titanium Backup to prepare for the next phone.

/Söder
[Magisk] Didgeridoohan:
[MENTION=2438781]soder[/MENTION]

https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc

And don't forget:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] chteh0721:
Now getting worst, I can't disable or unistall any of the modules, i planning to flash with older version of magisk, any possibility it will brick my device since I already updated to Android 9?
[Magisk] jcmm11:
Modern phones are pretty much un-brickable as long as you don't do something totally stupid. I'm not sure if older versions will have a problem with 9 or not. I can tell you how to delete your modules.

Get the sumount zip from https://xdaforums.com/showthread.php?t=2239421 flash that zip in TWRP and it will mount magisk.img You can then go in with the TWRP file manager and delete any modules you want to remove.

I suggest you then flash a stock boot image, take a nandroid (just in case) and you can then attempt to flash any Magisk version you want to try.

Flashing a stock boot image will always remove Magisk, although its files in /data/adb/ will remain unless you also either manually delete them or flash the uninstaller.

There have been some structural changes within Magisk so you're probably better off removing Magisk completely and starting over. If you're willing to try the latest build (I'd recommend the canary build) again keep all logs and post them if things fail again.
[Magisk] Didgeridoohan:
[MENTION=1229373]chteh0721[/MENTION] apart from the great advice from [MENTION=4487388]jcmm11[/MENTION], as long as you can boot your device you can also use a root file explorer to delete the modules you want to remove by navigaing to /sbin/.magisk/img (note that .magisk is a hidden folder) and simply deleting the module directories you'll find there. After reboot they should all be gone.

After that you should be able to provide the information I've previously asked for. No info = no possibility to help...

[MENTION=7664328]Sagar Sharma01[/MENTION] For the first question: I have no idea... If you need help I'd suggest that you get debug logs instead (see here). Also make sure that the Magisk Manager isn't installed to external storage or something along those lines.

For the other questions it's likely things you'll just have to live with...
[Magisk] martyfender:
With the latest Canary build, when updating MM, is the installer deleted after an update and or reboot? I don't find it in the downloads folder or the cache folder. However, the latest Canary zip is in the downloads folder.

Thanks

I just saw your answer in the Canary thread and responded, there.

Thanks
[Magisk] tag68:
Please be careful with such statements. Quite some Moto devices will brick if you

1. Downgrade stock ROM

2. Update via OTA

Problem seems to be that the bootloader does never get downgraded. But the OTA update does not check for correct bootloader and may brick the device in a way which is not solvable without a blank flash at least as new as the bootloader - which often isn't available.

So it is not the right way to downgrade a ROM if you find the wanted Magisk version does not run on a newer one, because you risk a brick when OTA gets installed - but would you call this a totally stupid action?
[Magisk] IODroids:
Please Lock this topic and start new support topic for latest version.

There has to be end of life for old stuff.
[Magisk] ashyx:
Exactly what are you referring to? This is the General support and discussion forum for ALL versions.
[Magisk] lucki1000:
Hello,

is there any module to fix drm-secure from video player apps like prosieben maxx and netfilx, for magisk?
[Magisk] casouzaj:
There's a module called liboencrypto disabler which claims to do what you wish. Haven't tested it myself, since the CR 7 ROM I run brings the Google Widevine key, which allows Netflix and such to work fine.
[Magisk] Pedroc1999:
Anyone getting random times when MagiskHide fails and therefor SafetyNet doesnt pass? Reboot normally fixes it for a few hours, maybe just minutes.

Exynos S8+ with a handful of modules, running latest V18
[Magisk] Deadlights:
Magiskhide Bootloader without Root

Hi! I have an unlocked bootloader without root anymore on a Pixel 2 XL. I wanted to start using Google Pay, but don't want to have to lock bootloader and reset phone. Is there any way to have Magisk Manager hide the bootloader unlock without rooting again? Without Root the Magisk Manager doesn't show the MagiskHide option in Settings.

Sorry if this has been covered, I searched and couldn't find an answer. Thanks!
[Magisk] ktmom:
This has been reported multiple times within this thread. Reports without logs covering the occurrence prevent the problem from being addressed.

You could use logcat through ADB to a PC to grab what will undoubtedly be a large file.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] jcmm11:
Try a custom kernel. Most kernels used to include a patch to hide the unlocked bootloader and I assume they still do.
[Magisk] ew:
For those that just brought this up.
[Magisk] 0firuz:
Hey,

anybody having problems with SwiftKey on Android Pie? I'm using Xiaomi Mi A2 and following the Pie update, SwiftKey now looks huge. I tried Magisk Hide to no avail.

Any ideas?
[Magisk] RandomPooka:
Why would you use Magisk hide to adjust the keyboard size in SwiftKey? That makes less than zero sense.

Just adjust the keyboard size with the SwiftKey settings.
[Magisk] 0firuz:
It's the "medium size". It was the medium size proper before flashing Magisk back.
[Magisk] tag68:
If you root using Magisk and let it deny any root request, what is the problem? No app is able to get root, everything should be fine like you want.