yashsingh1/xdaforums huggingface dataset:
[Magisk] cousinit99:
Go into Magisk Manager settings, un-tick Magisk Hide, wait a couple seconds, and then re-tick it. For me, Magisk Hide currently has an issue where it stops working after a fairly short, but undetermined period of time. The cause is also undetermined at this point. Just disable and re-enable Magisk Hide, and try the banking app again. If you have to, clear the banking app's cache and data.

---------- Post added at 04:28 PM ---------- Previous post was at 04:09 PM ----------

I have a 3T with the same issue. Like you, I've disabled all doze-related 'features'. See this post: https://xdaforums.com/showpost.php?p=77577417&postcount=27476. It's not a permanent fix, but at least a band-aid for now, hopefully.

---------- Post added at 04:38 PM ---------- Previous post was at 04:28 PM ----------

See this post: https://xdaforums.com/showpost.php?p=77577417&postcount=27476.
[Magisk] cousinit99:
Also not using a Samsung device. Yes, Samsung Pay is still detecting Magisk somehow, even when all Samsung apps are hidden in Magisk Hide and after the old MagiskManager folder has been deleted and related executables renamed. Hopefully [MENTION=4470081]topjohnwu[/MENTION] has a solution.
[Magisk] Apih95:
Why magisk is always missing ?? It happen randomly i cant determine when it is gone . After restart the phone, it is usually there
[Magisk] Denkov:
Hello all. If i use Magisk with patchet boot.image metod will Knox be triggered?

Thanks!
[Magisk] DenyDarko:
Most likely.

If you want Knox intact stay away from any modifications.
[Magisk] DAViiD__:
I've been seeing battery drain caused by root (Magisk AND SuperSU) on my Galaxy S8 (exynos). Every time I root the device, little CPU goes up to max usage with the big CPU idling. This is causing my device to get hot even when doing simple things like browsing Chrome (which admittedly is a ****ty browser) and watching YouTube. Can anyone confirm this happens to their device too? Does anyone have any idea what's happening or what's causing root to become such a battery hogger?

P.S. I'm 100% sure it's not being caused by some rogue app, as I monitored CPU performance in Safe Mode and when I just formatted the device. The adb shell top command doesn't provide any useful information either. Factory resetting, formatting, wiping caches etc. are all solutions I've tried multiple times in multiple sequences, nothing seems to prevent the phone from draining except for when I unroot the device.
[Magisk] otonieru:
Do not disable logd when using magisk. It will cause cpu freq stuck
[Magisk] DAViiD__:
I'm not even touching the Magisk app besides for the Viper4Android module to be honest. I know for a fact that Magisk Hide is always on btw, if that's related to logd.

How can I check if logd is disabled?
[Magisk] otonieru:
You gonna need to provide more info,

ROM ? Kernel ?

Any other tweak or mod installed when rooted ? Greenify ? Xposed ? Etc ?

When the cpu usage is high, what is the top process that running ?

You can try disable magisk hide and see whether the cpu still going rouge
[Magisk] krug3r:
Good question, I will check that tonight :good:

Thx for your reply ;)
[Magisk] DAViiD__:
ROM is stock. Kernel is stock kernel, TGP Kernel, Notorious Kernel, Mad Max kernel, ANY KERNEL.

No tweaks.

CPU usage is always high. That's why I said the top command is useless, it doesn't provide any info. There are several processes taking up more cpu throughout running of the command. Sometimes it's system_server, sometimes it's the top process itself, sometimes it's some Google app, sometimes it's some kernel process.

I'm going to try disabling magisk hide, but I doubt that's gonna change anything, as I've got the same problem when I use SuperSU instead of Magisk. Will keep you posted, though.
[Magisk] Joangarc:
Try Kernel TGPKernel.G95xx.v2.9.0.20180828.zip

It goes perfect in my S8. In Aroma installer say yes to install MTweaks and after installing, open mtwaeks app to choose best battery.

I install this kernel after installing ROM
[Magisk] hmd90:
how about this? xposed with magisk safetynet is work in there
[Magisk] DAViiD__:
I tried that kernel. It's a good kernel, except adb isn't supported or something. Plus, this kernel doesn't fix the little core max cpu frequency problem either.
[Magisk] teddy0209:
As stated in the image, that is just an illusion... [emoji28][emoji28][emoji28]
[Magisk] Deses:
Bankinter's wallet app (https://play.google.com/store/apps/details?id=com.bankinter.bkwallet) just updated and I don't know how, it's detecting root. The manager app is itself hidden and I hid the wallet app with Magisk Hide. SafeteyNet is passing fine. Even Pokémon GO works ok!

Phone is an OnePlus 3T with latest stock beta ROM and stock kernel.

What do you need so I can help debug this?
[Magisk] Dims_Camper:
Do you guys aware there's kinda bug on magisk, enabled modules prevent substratum overlays to be build and stay at /system/app after rebooting? Occurred only on Pie.
[Magisk] axay_ar:
yes man ...even i am facing the same issue in my kenzo....they day when i indtalled 17.1 the safteynet check passed and i was able to run banking apps...but recently i am unable to get the safteynet check..magisk hide is usable but is unable to hide root from apps..i didnt did anything new after i updated to 17.1..dont know why this is happening
[Magisk] zurik:
Hello, when I trying to flash Modules though TWRP, it gives that error mentioned in screenshot, unable to mount. Tried to mount partitions but no luck. Reinstalling Magisk didn't help. I'm using Aosp pie 9.0 gsi on Mi A1 with Magisk 17.1 installed.
[Magisk] Denkov:
But you are not sure about that? I am asking people, who has done it on s9+ and what is the result.
[Magisk] yochananmarqos:
It doesn't happen to me.
[Magisk] Dims_Camper:
Really? what magisk version are you on? you have magisk modules enabled right? using the stable one didn't help. Didn't tried the canary build yet. And I'm sure I'm not the only one who faced this, someone also posted same issue on substratum's g+ page.
[Magisk] jcmm11:
First off try the latest Canary build. If that doesn't work logs will be needed (post logs here rather than in Canary thread since topjohnwu states in the op of the Canary thread:

"SafetyNet / CTS / XXX app won't work after enabling MagiskHide:

Do NOT report here!")

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
[Magisk] mayur.3.92:
So do you mean that performing the above steps will fix apps detecting root? I've the issue with Airwatch app detecting that I'm rooted n i can't access my company's emails
[Magisk] yochananmarqos:
I'm using Magisk 17.1 with just a few modules: Ainur Sauron, BusyBox and Privileged API Booter.
[Magisk] Dims_Camper:
Daym, maybe it's custom rom issue i guess? You're on stock P right?
[Magisk] DenyDarko:
Guys I think you forget Knox is an based on an efuse.

Once tripped it's over. The end. Done.

I wouldn't give advices so easily to people.
[Magisk] yochananmarqos:
It could be. Yes, I'm on stock Pie (September).
[Magisk] paarnoutse:
As posted about one week ago, after upgrading from Magisk 16.0 to 17.1 at my device (OnePlus 5 running OxygenOS 5.1.5), Magisk Hide didn't work anymore.

As a result:

- Even for hided apps, '/sbin' was available in Env. Path

- Therefore root could easily be detected by any app

(eg. by Intune, being a big problem for me)

- For same reason any SafetyNet check failed

- Etc.

Many, many things tried to find why this happened at my device, while Magisk Hide in 17.1 appears to work OK for most other people (although I've seen several other post about root being detected and SafetyNet checks failing after an upgrade to v17.1).

Just found the weird reason for Magisk Hide failing in v17.1 at my device (while all was OK at v16.0).

Described here because it may possibly also be the reason for equivalent issues by other users:

==> If Chrome is included in the Magisk Hide selection,

==> hiding failed for any app, so it seems to break the

==> Magisk Hide functionality of Magisk v17.1.

After removing Chrome from my hide list, no root detection anymore for the other hided apps, and safenet checks (also the Magisk build-in check) OK now!

In the meantime I've checked/verified this at several other devices, and it looks to be a general Magisk v17.1 behavior.

No idea why including Chrome in the hide list is causing this problem, nor why it was OK in v16.0 but is causing issues in v17.1 now.

Nb.

The reason why Chrome was included in my hide list isn't relevant here, and fortunately also not needed (anymore) for me.
[Magisk] Hal9k_:
After installing Magisk v17.1, the device periodically, but not every time, reboots into the bootloader with error:

[ 7.209501] init: starting service 'magisk_startup'...
[ 7.211237] init: cannot setexeccon('u:r:magisk:s0') for magisk_startup: Invalid argument
[ 7.211446] init: panic: rebooting to bootloader
[ 7.211554] init: Reboot start, reason: reboot, rebootTarget: bootloader
[ 7.212880] init: Shutdown timeout: 6

Device: Android Car head unit with Oreo 8.0.0

Processor: Rockchip PX5 (rk3368) arm64-v8a

Any help and ideas ?
[Magisk] cousinit99:
Do you know whether or not it's a known issue that Magisk Hide stops working on its own after a fairly short, but undetermined period of time? Or does someone need to provide logs for that as well? Short of a 10,000+ line logcat, I'm not sure how else to provide one. The Magisk log doesn't appear to be picking up anything anomalous.
[Magisk] martyfender:
You said you had your reasons to hide Chrome, I'm not sure why? I'm just speculating, could it be system webview in Chrome causing problems? Many apps use it and it is uses the one in Chrome by default on newer versions of Android vs the stand alone version such as on My Android 6.0.1. On newer versions of Android the stand alone version can only be enabled in developer options, if I am not mistaken. Could it be some kind of weird interaction caused by that? And to be clear, I am just speculating, here.
[Magisk] TheCheese45:
Same here, trying to update youtube vanced. Pix2XL Pie, August patch
[Magisk] Buckle76:
Thanks:cyclops:
[Magisk] hmd90:
Yes, I think he wants to make a big surprise but he is not aware of making himself an illusion :D:D
[Magisk] patchick:
I need to hide the manager with a random package name so i could play pokemon go

After its done, i cant open the manager any more. It just stops at the loading screen. Only fix is to uninstall it and install the original app. Why does the hidden package not work?
[Magisk] francyesco:
Sorry for repost but someone know where is the problem?

https://xdaforums.com/showthread.php?p=77405862
[Magisk] EthanT09:
Has nobody encountered this RILD error before on any other device?

I find it hard to believe this sim permission issue is tied to J3 2017 only
[Magisk] paarnoutse:
Yes indeed I guess it's related to WebView, which is since Android 7 part of cq. integrated in Chrome. A stand-alone "Android System WebView" is still available (at my device installed as a system app but standard being disabled/frozen), which has to be enabled only in case you're using another browser *and* you want to disable or uninstall Chrome (which obviously also disables Chome's build-in WebView).

I didn't check, but I expect that when Chrome is disabled and therefore the stand-alone WebView was enabled, similar problems may occur with Magisk Hide in Magisk v17.1 when WebView would be added to your hide list (instead of Chrome). Did you already upgrade to Magisk v17.1? When true it would be interesting to check that at your Android 6.0.1, and let us know.

It's true that the reason why I hided Chrome in the past was also related to its build-in WebView: I tried to use an OWA-based email app (Outlook Web Access) for my O365 work account. By hiding Chrome (so WebView) I tried to avoid that it was recognized that my device was rooted, and/or that it triggered the enforcement to enroll my device with Microsoft Intune Company Portal.

Although it didn't help I forgot to remove Chrome from my hide list afterwards, which now caused the described issues in Magisk 17.1.
[Magisk] Blizzard22:
Thanks dude, it worked. Btw. I'm using Xposed but I'm considering removing it to pass safety net (it's not really worth it anymore, most modules are replaceable with root/magisk modules anyway).

If I uninstall xposed framework will I pass it or do I have to reinstall the rom again?
[Magisk] teddy0209:
If you're using systemless Xposed, then just disable it in magisk, reboot and should pass SN... If system installed, you need to remove it...
[Magisk] @srmahunt:
You can disable module to pass safety net, don't have to uninstall it. Xposed is more efficient than root apps in terms of battery and performance.
[Magisk] Blizzard22:
Ok, great. Battery life is more than excellent on my S8+. In my current usage I can use it from the early morning until the night with 20% battery left without charging (low display light, regular performance, high resolution).

If I now can get the exceptionally long boot time fixed after the Samsung logo for no apparent reason the biggest issues would be fixed.
[Magisk] Andy4Shurr:
I'm having a weird issue with magisk manager hanging on the splash screen (the green mask page on launch) but only when I have repackaged and after the first launch/open of the repackaged manager.

If I don't repackage it everything is perfect, when I do repackage it and open it the first time everything is perfect still but then if the repackaged magisk manager is closed and opened again it just hangs! Nothing is being granted root either, even if I set it to auto grant access in settings. I can uninstall then reinstall and it's all working ok again until I repackage the manager app.

I'm on magisk 17.1 and have tried magisk manager 5.9.1 and 5.9.0. I have tried reinstalling Magisk in twrp as well but I still have this issue.

I have attached a log to this post. When searching through the thread I've found people having similar issues with hanging but they're not applicable to having the issue just after repackaging so none of the fixes have worked for me.

Any help would be greatly appreciated :)
[Magisk] jcmm11:
It may fix, not will fix. And that assumes you've already tried everything else.
[Magisk] NagaPujith:
Can anyone fix this magisk safety net say ok but took checker say not safety

Note: Device Lenovo vibe k5 plus rom AEX v5.8
[Magisk] KevMetal:
Your problem is with root checker application

*use magisk 17.2 safety net checker

*downloap APi

*safety net passes

...look at screenshots below
[Magisk] KevMetal:
Here you see your problem
[Magisk] firozpatel:
Could someone help me please

I can't get Google pay to work, it's hidden in magisk, I have cleared cache, I have deleted data, also from Google play services, but keep getting a message something is wrong
[Magisk] martyfender:
I have been on unofficial builds by [MENTION=3306843]kantjer[/MENTION] an [MENTION=7187684]ianmacd[/MENTION] and more recently I have 2 devices on the latest Canary builds.

---------- Post added at 09:03 AM ---------- Previous post was at 09:00 AM ----------

I believe so, especially if xposed was installed as a Magisk Module. I'm not sure, if it was installed directly in the system, though.

If you have trouble passing Safety Net after that, you can try Magisk Hide Props config Magisk module with its basic settings and if it still does not pass, try adding one of its certified device fingerprints.
[Magisk] IamX00T:
Hello. I have an Asus Zenfone Max Pro M1 with Lineage 15.1. A few days after installing Lineage, I flashed Magisk from TWRP. Immediately after this, Truecaller stopped working. As soon as I try to open it, I get the message that Truecaller has stopped; when I try to open it again, I get the message Truecaller keeps stopping. I have tried removing the cache of Truecaller, resetting permissions, uninstalling reinstalling it, and also uninstalling and reinstalling Magisk, but to no avail.

I am a new member so I can't attach any logs, but I posted the contents of a log in a post I made in one of the threads:

https://xdaforums.com/showpost.php?p=77546495&postcount=253

Please help, as I really need to install Truecaller. Thanks.
[Magisk] DAViiD__:
Update on trying to disable magisk hide: Doesn't solve the problem. CPU still going rampant and turning up to the max.
[Magisk] martyfender:
Have you looked here?

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

---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------

Update: I saw info about webview here:

https://www.didgeridoohan.com/magisk/MagiskIssues
[Magisk] masterwishx:
Thanks a lot, the last version 17.1 work FINE on J710f 7.0 with adoptable storage, before it was problem after every restart some apps was like not installed!!! Seems it was fixed..
[Magisk] Skid71:
Images

Good day,

Pixel 2 XL; rooted; Magisk 17.1; August build:

Could someone share which factory images I need to adb/fastboot to get updated to September update/security patch? I rooted last month after receiving Pie.

Thank you
[Magisk] yochananmarqos:
That's a question for your device forum. Hint: It's the one marked September. ;) Don't download the carrier builds unless you use that carrier.
[Magisk] peterlee928:
https://developers.google.com/android/images

taimen 9.0.0 september :good:
[Magisk] Homeboy76:
Flash-all this one:

"taimen" for Pixel 2 XL

9.0.0 (PPR2.180905.005, Sep 2018)

SHA 256

c21252d46416ab94fa4dd22e8f3b13de7b12e817a2a9a3c23a7a2fe805415d2b

Remove -w from flash-all. bat if you want to keep your data.
[Magisk] DAViiD__:
Update on using the link to hide Magisk: logd was disabled, Magisk hide was disabled, same problem. CPU frequencies still go to max. When using Magisk hide AND having logd enabled, problem still persists.

I also changed the kernel from stock to NX Kernel to make sure it was compatible with Magisk hide, it doesn't solve the problem.

I'd like to point out that my phone can enter deep sleep, but when the screen is on and the phone is idling, little CPU frequencies go all the way up to max while big CPU frequencies stay low. When I touch the screen, vice versa happens (big CPU jumps to max frequency, little CPU stays low).

I haven't gotten a step closer to figuring out what's causing the problem, other than that flashing Magisk or SuperSU is the cause for the problem with the CPU frequencies.
[Magisk] Nightshadow931:
MagiskHide won't work for my banking application, somehow it detects that my device has been 'modified', and it wouldn't start the app.

I'm using latest version, 17.1, Android 8.0.

MagiskHide itself does work, I've just tested it by downloading root checker, hiding it(it didn't detect root access), and unhiding it(it did detect root access).

What could be the problem?
[Magisk] nilesh0205:
Hello,

I tried to install version 17.1 but it fails on Nexus 6 (Shamu). I am on lineageos 15.1 (latest nightly). no custom kernel, stock gapps.

1. With magisk manager, it install but after reboot It stays at locked screen no matter what I do. and when I rebooted again, it wont come up at all.

Then I reverted to version 16.0 through twrp and it booted fine.

2. then I downloaded the version through manager but did not install using manager, and tried to install using TWRP. it failed saying corrupt zip.

3. Then I manually downloaded from the Main Magisk thread and tried to install through TWRP. It installed correctly but symptoms from point 1 repeated.

Can anyone please let me know what may be the reason?
[Magisk] greenys':
The reason is that Magisk 17.1 isn't stable unlike it is said

. I mean it could be but the dev itself said that he was rather busy thus he had rushed a bit with the coding and publishing the latest stable version. This way quite huge part or the code became incorrect. This causes quite a lot, differently issues on some devices. Just like mine. Bootloops. Random reboots. Freezes etc. So I reverted to Magisk 16 vcustom and my phone works like charm. Advice: Wait for next stable version. I'm pretty sure the dev already know about the problem and as soon as he can he will fix it. Hopefully.

Sent from: Redmi Note 4 mido
[Magisk] Exorsizer:
Only crashes.

On my OnePlus 6, Magisk just crashes after installing it.

When I do a complete re-install of Magisk (the zip and the manager) it works for a few hours, maybe a few days, but eventually I notice my apps don't get root access anymore, so I check the manager app and it just crashes on start. I have no idea why it does this. I've tried clearing cache, reinstalling, even a fresh Android install but it just doesn't permanently fix it.

I've tried the new Magisk 17.1 and the older 16.7, all with simular results. I'm using an OnePlus 6, the 128GB storage version. No custom kernels, and the Android Pie Beta 2 from the OnePlus open beta program. No Xposed or anything like that either.
[Magisk] Hopie:
Hello, i´m running Viper9.0.0 (lollipop ROM) on my HTC One M7 with Magisk 16.x. This works.

Try to Update to 17.1, but doesn´t boot. bootloop on Bootsplash. :confused:
[Magisk] Dhalsim43:
After each OTA update (I've a Shamu with LOS) Magisk 17.1 installation is lost and I must reflash it. Was working fine with Magisk 16.0.
[Magisk] Larswad2:
Trying to find a simple answer in the thread, but it is so long.

I have Oneplus 5t, had magisk 16 (and twrp installed), the manager updated itself to 5.9.1. But no root any longer since I guess i'm still on the old boot.

So I downloaded the latest stock kernel image zip for OOS 5.1.5. I unzipped and successfully patched the boot image. So I have the patched_boot.img file in the download folder.

Now here the question, all instructions more or less say now that I should use adb to flash it. But why can't I just use twrp to flash the boot partition with my patched boot.img just like that? Of course I would make a backup of everything before, always do.

Then also, why is there suddenly a Magisk Manager with a -patched suffix in my download folder now as well. Should I reinstall magisk manager afterwards with this patched version?
[Magisk] jenslody:
You can flash via TWRP and the "-patched" suffix means your Manager is hidden (by repackaging it with a random name) and this is just the apk containing the repackaged Manager.
[Magisk] Larswad2:
Thanks Jenslody! I was almost certain since twrp has that feature. And later on I found way into the thread a discussion that first gave a negative answer, then a positive one. So, your answer makes me confident.

Now one thing that people confuse others with (if I'm right) is that they many times say that they should flash the magisk zip from twrp directly. But THAT really depends! If the boot partition is already a patched version of an older magisk I guess the magisk zip will "double-patch" the boot by originating from the already patched one in the boot partition likely causing corruption and boot loops.

So as far as I've figured things, there are three alternative ways of doing it properly.

1. Zip the Uninstaller for magisk from twrp (guess it has to be the uninstaller from the prior magisk? never really mentioned). THEN flash the newest magisk zip (in this case 17.1) from twrp which will patch the now "stock-restored" boot partition properly.

2. Flash a complete operating system image from twrp for the exact specific phone which will of course also contain the original boot image along with everything else. Then directly flash the magisk zip that will patch the boot properly.

3. Let the magisk manager create a patched boot.img from the exact model and the same version of the OS you are already running. This patched image can then be installed using either adb tool (or like in my question using twrp in "image mode", in case one doesn't have a pc at hand). . The boot flag in this case is important and selecting the boot partition of course.

ALL alternatives should be preceded by a nandroid backup from twrp of in principle EVERYTHING, for those of course who has that option.

Please correct me if I've gotten anything wrong.
[Magisk] guest4711:
MagiskManager will detect boot images modified by Magisk and can handle it. So normally no need for uninstalling/flashing stock. This can be necessary if something goes wrong.

When updating I'll first give the short and easiest way a try.