yashsingh1/xdaforums huggingface dataset:
[Magisk] alexinc:
same here with stock android 8.0 on LG G5. worked before updating to 18.1 without problems, but pushtan was updated on 21. jan too, so maybe they also broke the "hide"-feature!?
[Magisk] Indashio:
New Pokemon go update 0.135 not working with magisk 18.1
[Magisk] Oswald Boelcke:
Unless you already know, for those issues an own dedicated thread exists: https://xdaforums.com/apps/magisk/discussion-pokemon-magisk-discussion-t3465722

Please consider to review para. 1 of the Forum Rules.
[Magisk] Coumodo:
doesn't worked also, in addition various apps claiming missing access to Play Service.

After all it seems that my problem isn't related to Magisk.

I uninstalled Magisk in TWRP with latest uninstaller... gpay still denied all paymethod actions:crying:

---------- Post added at 03:17 PM ---------- Previous post was at 02:56 PM ----------

Same result -> gpay detect rooted/modified device and denied adding payment methode

I start to belive it's related to the latest Gpay update 2.82.xxx on 14th Feb.

before I had no issues at all
[Magisk] lee99:
Hi all!

I wonder it is possible to make this work on thl t6 pro? I tryed to install with old custom recovery twrp but after restart system (kitkat 4.4.2) will not start at all.

Best regards.
[Magisk] Pkt_Lnt:
Here is one post I made on this issue in this Magisk thread, there are others in the various forums for many A/B devices, though it seems random those affected vs those not affected. It is not a universal problem with Pixel 2/3 devices or other OnePlus A/B devices.

If you want to chase this more, I'd suggest a full install of factory images and *only* install Magisk (no other apps or mods) and see if it happens. Then add the apps you need for daily use one at a time and power off to test, add one more app, test. Yes, tedious and time consuming. The option others who suffer this "feature" just keep the phone on 24/7 and charge while on

https://xdaforums.com/showpost.php?p=78796792&postcount=30775
[Magisk] Ch3vr0n:
I flashed the feb factory image after getting it. Cause it was on the october update and couldn't be bothered to instal 5 or 6 consecutive updates. After updating to latest build, flashed magisk, enabled MagiskHide and systemless hosts and that's it. Keeping the phone on while charging is precisely what i've always done, going back all the way to my HTC Sensation XE. Don't plan on stopping now. When i first got the device and charged it (before doing anything else) i was getting the standard charging animation, then after unlocking and rooting no more. So knew it was something that happened between charging it initially and rooting. So started investigating.

Aint dropping root for that, need it for too many things :) Now if only [MENTION=4470081]topjohnwu[/MENTION] would reply if he wants that banking app to take a look at :)
[Magisk] Didgeridoohan:
But do you pass SafetyNet without MagiskHide? Unless you also locked your bootloader you should not be able to pass SafetyNet...

TWRP versions that old can't handle the Magisk installation scripts. You'll need to install the stock boot image, or possible do a dirty (or clean in necessary) flash to get up and running again. After that you can try the patched boot image method instead. Instructions here:

https://topjohnwu.github.io/Magisk/
[Magisk] jcmm11:
unless he's running a custom kernel. Most (by now I assume all, it's been available for ages) have a patch in them to defeat the bootloader check.
[Magisk] Didgeridoohan:
True... I haven't been messing with custom kernels for so long I keep forgetting.
[Magisk] honorfan:
How to update old magisk modules??

At least help me to install old magisk

When i install magisk 16.2

It says i have to update to 18.1 until i be able to flash any module

Plz help me i want some of those modules
[Magisk] Sc4r3Crow:
Hey guys,

after update to Magisk 18.1 ctsProfile states false.

No problem with 18.0...is that a known issue? I'm on OP5 with custom rom.

---------- Post added at 10:01 PM ---------- Previous post was at 10:01 PM ----------
[Magisk] Zico 10:
Hoping someone can assist, I've tried searching the thread but didn't find what I was looking for.

I was running Magisk 16.7 with Magisk Manager 5.9 without issues, but as soon as I update either to anything newer, on the next reboot my network (LTE, 4G, 3G) is completely disabled and I can't enable it.

If I remove Magisk and reboot, it works again.

I disable and remove all modules prior to updating and it still happens.
[Magisk] Okikix:
I'm having some trouble. I opened up magisk manager to do something in there and was going to update magisk while I was at it. Before I could it prompted me to download new apk. I did and now it's saying apk doesn't support magisk lower than 18, manually flash or downgrade app. I've tried downloading older version of app but it just installs it as separate app and doesn't let me do anything. Not sure what to do. I saw someone mention using TWRP but I don't have that installed on my phone. How would I go about fixing this? Pixel XL 2
[Magisk] MDV106:
Is there a module or app that i can use to change the system.accent color of Nokia stock android pie from blue to teal/green like the one in lineage or oxygenOS? I tried substratum and the accent them for P module.....and all of them didnt work.

Also the option to check for SafetyNet pass suddenly disappeared from magisk manager home screen. What could be the cause? Rebooting didnt help at all.
[Magisk] Klusio19:
I'm rooted with Magisk and I have some modules installed. Can I make backup in TWRP? After restoring this backup will I have any problems with root?

Or it's better to uninstall modules and Magisk and then make backup?
[Magisk] chooks06:
My understanding is that whatever I back up now, it will be exactly like this if I restore it correctly, whenever I do it.. So if I restore in the future, I will be going back to the past.

That's what I've been doing.. Just in case something goes wrong with some app/mod that I'm checking, I can go back to just before I installed the app/mod.

To me, it's something like a restore point in Windows for PC users.
[Magisk] Coumodo:
oh, I forgot that bootloader ist still unlocked. Didn't checked SafetyNet status without Magisk

Don't know what to do any more - I loved to pay with my phone, but also need root.

Gpay detects modification whatever I try
[Magisk] trax7:
Loops

Latest Magisk 18.1 bootloops on latest 9.2.15 beta (MIUI EU) Pie on Poco F1. It worked on the previous version and without Magisk everything boots fine. I tried latest Canary version and i'm still waiting for it to boot, it's not looping, but it's stuck. The weird thing is if right after installing Magisk I try to install a custom kernel, I get Error 1 in recovery with the text "Unzip failed". :eek:
[Magisk] Klusio19:
So what do you think: better to make backup with or without Magisk?
[Magisk] chooks06:
It depend on what you prefer.

Without Magisk, gives the option to install new version when restoring, BUT, if the removal wasn't properly done, you'll end up restoring the problem.

I have more than one backup so if the latest gives problems I can't resolve, I have another earlier one to fall back on.

Usually before I start root, I have one backup, after updating apps and logging in..

After rooting and all is stable with a further setup, I do another backup.

Then the others are as and when needed.
[Magisk] Klusio19:
Ok. Thank you for comprehensive answer. :svetius:
[Magisk] chooks06:
You're welcome!
[Magisk] blackhawk_LA:
I have a big problem; I hope someone can help me, please.

I was running Magisk 18.1 on a LG G6, which is encrypted. There's no TWRP version that can handle encryption so I can't acces any data from recovery.

The problem came when I uninstalled Magisk from the app. After rebooting, the phone was in a bootloop. So I went to recovery and magisk again. But when the phone boots, now I have "secure boot-up" enabled, and asks me for a password I have never set (actually, my lock screen was secured with a pattern). I tried restoring stock boot, different magisk versions but still no luck. And every reboot, the number of attempts increases by one. So I have only 20 left to solve this, before losing all my data (which will be a huge pain for me)

Anyone has an idea on how to manage this?
[Magisk] tbqstp:
I had the same problem. Simply uninstall the latest Magisk Manager first and then install the previous one.
[Magisk] darwinmach:
This happened to me as well and it's because I had Magisk Manager set to use a random package name.

I fixed it by going into Settings -> Restore Magisk Manager. For me, this loaded the new version automatically. You can then go back in and re-randomize the package name.
[Magisk] Cruel_Carlos:
These kinds of things often escalate to Flame Wars and that's not cool.

I too share the frustration of not being able to root my Samsung S7, but I stop my emotional tendencies and try to rely on logic lest I insult the people for trying to help me. That said I'm in the loop here as I tried this on a older phone it seems to go through. My 7 will not, for example, fully implement magisk 18.1 update. It keeps downloading it and try to install and nothing. Because I know zero about computer programming I have no clue what to do next.

ZERO

sorry, didn't mean to yell, but it is very frustrating when you follow instructions as best you can and nothing works out. I almost started quoting institutionalized by Suicidal Tendencies. Thankfully logic won out this time. It's just that the longer I stay on the more likely it is I'll start quoting things.

for what it's worth, I do appreciate everthing you folks put out there. I'll just keep reading in hopefully it'll make begin making sense.

"Help me, XDA Community, you're my only hope" ?
[Magisk] akxak:
On my OP6, I got GPay working with Magisk 17.2. Also SafetyNet and cts are green and MagiskHide does work.

GPay might need a reinstall, means delete its data via app manager and login again.
[Magisk] Didgeridoohan:
[MENTION=9638400]Cruel_Carlos[/MENTION] Sounds like you're having a though time... From what I understand, Sammy devices can be frustrating. Personally I don't do Samsung...

From your post it sounds like you're already rooted, correct? And the issue is that you can't update to Magisk v18.1. What's your current Magisk version? Some more specifics and details would be good...

You could try a few different approaches.

If you have a custom recovery, you can simply download the installation zip and flash through there.

You could download the zip and flash it manually from the Magisk Manager (go to the Modules section, press the "+" button and select the Magisk zip).

You could patch the boot image and flash that manually.

And, most importantly of all, if you continue having troubles try to get logs showing what's going on. It's really hard to help otherwise.
[Magisk] masterjp:
I flashed the latest Android Oreo 8.0 stock firmware for my Samsung S7 (SM-G930F) with Exynos chip and flashing magisk 18.1 root does not work. With an older Oreo firmware from 12/2018 and Magisk 18.0 I will not get any problems. I used TWRP 3.2.3.0 (latest version) and did not see any error during flashing. I am not a beginner of flashing. Maybe something has changed or Samsung has modified something to prevent rooting!? Are there some other users, which have the same problem?

I used the following instruction to do it:

https://xdaforums.com/s7-edge/how-to/guide-how-to-root-android-8-0-oreo-t3840271
[Magisk] demonoidmaster:
Do what it tells you to do

---------- Post added at 08:22 PM ---------- Previous post was at 08:13 PM ----------

Why did you uninstall magisk via the app instead of via twrp.. actually, which did you encrypt or leave your device encrypted if it's known that twrp doesn't work with it? Before having set up your phone you should of nuked /data then install your rom, gapps, etc

Your only hope is waiting until a future twrp update can decrypt data so you can backup your stuff then restart from scratch
[Magisk] Jannomag:
Magisk on Huawei P10 VTR with Pie

Hi, I just updated to Pie (EMUI 9, version 9.0.1.157(C432E1R1P9) on my Huawei P10 VTR.

Everything works fine so I tried to install Magisk like this:

- Extracted the recovery "RECOVERY_RAMDIS.IMG" from the UPDATE.APP package

- Patched it with Magisk app (Install --> Install --> Patch Boot image)

- Flashed patched recovery with "fastboot flash recovery_ramdisk recovery_patched.img".

When I boot up by pressing Vol+, like I want to boot into recovery, the phone won't boot.

It stucks at the bootloader screen. I have to turn it off manually.

Normal boot is still possible.

Any solution here?
[Magisk] ktingmar:
Yes, I do have the same problem with the same phone right now on every ROM I tried so far! Did you find a solution yet?
[Magisk] M1chiel:
Magisk can only work on EMUI 9 if you install it instead of the recovery. It is supposed to work in the Canary build. More info is in the release notes of the version that appeared around Christmas.
[Magisk] Jannomag:
Did this, as I said above. I also tried the Canary build - same issue.
[Magisk] M1chiel:
Sorry, I overlooked that. A P20 user solved the same issue by a factory reset and installation of the canary build of Magisk: https://xdaforums.com/huawei-p20/how-to/guide-how-to-finally-root-emui9-t3883295/page9
[Magisk] Jannomag:
Thanks, I will try it when I have time for the long restoring progress.
[Magisk] Ps24u:
Is this error problematic and if so how can I solve it?

Thanks for your insight.
[Magisk] dpsi:
I actually have been having this issue since 18.0 came out. I might give canary a shot if I have time
[Magisk] martyfender:
Did you try deleting app data and cache in settings apps, or uninstalling and reinstalling gpay?
[Magisk] Pablo.x:
I used it 13th february with no problems.

Suddendly, 14th february, I wasn't able to pay with GPay, I've started to get a message like 'You're no longer able to pay'.

Yesterday I was able to pay again, the only thing I did: a clean flash :silly::silly:

Before that I tried: reflashing magisk, dirty flashing ROM, reinstalling Google Pay, add and remove GPay from Magisk Hide...

Nothing worked, now just works after a clean flash and adding GPay to Magisk Hide.

Hope that helps you :highfive:
[Magisk] habylab:
Try latest Canary, fixes a few issues with Magisk Hide.

https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/magisk-release.zip
[Magisk] Pablo.x:
Thanks but after the clean flash I'm not facing it (at the moment).

If problems return, I'll give it a try! :good:
[Magisk] JD_9:
This app somehow detected Magisk

This is my banking app, it's called FriMi and it detects Magisk. So unfortunately, I can't use it anymore. :crying: Any ideas? :confused: I've tried using Core only mode, repacked Magisk with random package name without any luck! :(

The app is available on the Play Store. It's called FriMi. (com.nationstrust.frimi) I can't post the link as I'm new here. :(
[Magisk] habylab:
Try Canary build, link above. Stable and works with all my banking apps.
[Magisk] JD_9:
OK. I'll try Canary builds. Thanks! ;)
[Magisk] guest4711:
And don't forget to put it onto MagiskHide list before starting the app for the first time (and clean it's cache before).
[Magisk] Didgeridoohan:
You could try flashing the Magisk zip again, but this time make sure that dm-verity is disabled properly. You can do this by running a terminal command in TWRP:

https://www.didgeridoohan.com/magisk/Magisk#hn_Disabling_dm-verity_and_forced_encryption

It's far from certain to work, but I guess you have nothing to loose. Is there any way for you to enter your lockscreen pattern when it asks for a password? If you where using a 3x3 grid for your pattern, you could also try typing in the numbers (1-9) that corresponds to the points on the pattern (usuallyl it's 1 in the top left corner and 9 in the bottom right, but you can of course try with 1 in bottom left and 9 in top right as well).

Chances are though that you're going to have to bite the bullet and do that wipe...

No idea... Are you experiencing issues? Looking at that small log snippet it does look like things might be a bit off, actually. It makes me think the boot stages are messed up and coming in the wrong order (but really hard to say without the complete log).

I tested the app on the latest Canary (18108) and on my device it can hide root from it just fine. If you can't get it working, take a look here for tips:

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

It was also interesting to see that it requires Google Play Protect to be enabled... Hadn't seen that before.
[Magisk] Coumodo:
FINALY!:highfive:

With latest Canary build GooglePay works!

flashed uninstaller & Magisk Canary release in TWRP.

Added GooglePay to hide, and activate Magisk Manager hide option.

Added Paypal to payment method:cool:

just need to test money transfer in store this afternoon;)
[Magisk] habylab:
Glad it worked! Working well for me too.
[Magisk] jerryspring:
U can't have xposed and magisk for modules. They conflict
[Magisk] Ps24u:
Thanks for your support. I attach a log from a clean cold boot. The only module I use is Busybox for Magisk. Everything is latest version (magisk, manager, module).
[Magisk] Didgeridoohan:
Why are you quoting a post from 2016?

All the users that have both Magisk and Xposed running at the same time would probably disagree...

Hm... If I had to guess it looks like the Magisk boot process somehow restarts at the end there and that's why the mount fails (since it's already been done). If you're not experiencing any issues I'd say that it's nothing to worry about. If you'd like to investigate further you could install the Canary debug build to get more comprehensive and verbose logs (but it's likely that you won't see the error anymore after a reflash of Magisk, even the stable version).
[Magisk] JD_9:
Thanks! FriMi works with the latest Canary Build. :)

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

Thanks man. :fingers-crossed: FriMi works again with the latest Canary Build. (18108) :)
[Magisk] wurstherpes:
Yeah thanks. With the latest Canary Build works pushtan and root. :)
[Magisk] Jannomag:
I have another weird issue with Magisk on my P10 with EMUI 9.

I managed to get it working after a factory reset.

Now the touchscreen won't recognize everything on the very left and right side in portrait mode (around 5mm) whenever I boot with Magisk enabled.

I tried 18.1 and 18.2 canary build, both with the same issue.

When I boot without Magisk everything works fine.

Is there a solution for this?

EDIT: Also tried latest canary 660e0dc0, same issue.
[Magisk] KaXaSA:
So... I need some help, I'm trying to install Magisk on a Zenfone 5 T00F - Version WW-2.22.40.540(kitkat,MR11.3)

https://dlcdnets.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-2.22.40.540-user.zip

Using TWRP (Recovery) I get: "! Unable to detect target image"

I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:operation_start: 'Flashing'
Installing zip file '/sdcard/Download/Magisk-v18.1.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
1038+1 records in
1038+1 records out
1063528 bytes (1.0MB) copied, 0.009066 seconds, 111.9MB/s
/dev/tmp/bin/busybox: line 1: syntax error: unexpected word (expecting ")")
1567+0 records in
1567+0 records out
1604608 bytes (1.5MB) copied, 0.013533 seconds, 113.1MB/s
Archive: /sdcard/Download/Magisk-v18.1.zip
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: arm/magiskboot
inflating: arm/magiskinit
inflating: chromeos/futility
inflating: chromeos/kernel.keyblock
inflating: chromeos/kernel_data_key.vbprivk
inflating: common/addon.d.sh
inflating: common/boot_patch.sh
inflating: common/magisk.apk
inflating: common/util_functions.sh
inflating: x86/magiskboot
inflating: x86/magiskinit
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
! Unable to detect target image
- Unmounting partitions
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
I:Install took 4 second(s).
Error installing zip file '/sdcard/Download/Magisk-v18.1.zip'
Updating partition details...
I:Data backup size is 1630MB, free: 10754MB.
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1

If I try to use the Magisk Manager 's Patch Boot Image File: "! Unable to unpack boot image"

- Copying image to cache
- Device platform: x86
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.570 secs (1865838 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
! Installation failed

I tried Magisk v18.1 and the new(?) one Canary(?).

Later I will try to download an older version to see if it works.
[Magisk] MDV106:
My safeynet option on magisk manager disappeared after i disabled google play services and other google apps on my Nokia 8 running stock android pie. Is there a reason why this happens and is there a workaround to it?
[Magisk] martyfender:
Why would you disable those, especially Google Play Services?
[Magisk] jerryspring:
Oops. Posted on wrong post. My bad
[Magisk] Didgeridoohan:
Because SafetyNet is a part of Play Services... Can't use something that isn't there.
[Magisk] Valeryan24:
Sorry for being a newbie, but I prefer to ask than blocking my phone: can I just flash in recovery mode the last Canary build (18108) with the current Magisk Manager 7.0.0 (185) or do I need the Canary app-full-release.apk (and in this case should I unhide / uninstall Magisk and Manager before) ?

I'd like to see if the last Canary corrects the ctsProfile SafetyNet test on my Nexus 6P, but if too risky I'll wait for the official update ! Thanks :)
[Magisk] Didgeridoohan:
There are always risks when testing the Canary builds. The current one (18108) seems quite stable though and has the awesome new implementation of MagiskHide. You don't have to uninstall or unhide anything before installing. You don't even have to do it through recovery (unless you feel more comfortable that way). You can just change the update channel in the Manager settings to one of the links provided in the Canary thread OP and update directly from the Manager. Either way if you choose to flash the zip in recovery or update directly in the Manager you should end up with both an updated Magisk and Magisk Manager.

Happy flashing and always make sure to have a backup of anything important.
[Magisk] MDV106:
Because it keeps running over and over in the background and unecessarily eats up battery and heats up my phone. Besides, most of the apps i rub are from fdroid aand dont necessarily require gplay services to start.
[Magisk] Valeryan24:
Thanks ! I didn't find the right link to put in Settings for Canary updates, so I flashed in recovery, reboot OK, I well have last version, cleared cache and datas, but ctsProfile still fails.

I know Magisk is working because smartphone is still certified in Google Play, I can update and install apps, root test works (root detected, but no more if I hide the dedicated app').

Will try to upload Magisk logs…
[Magisk] Didgeridoohan:
If it's just a case of CTS failing while basic integrity passes, you might be able to fix that by using a certified device fingerprint:

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228

Some details:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet_incompatible_devices_and_ROMs
[Magisk] Valeryan24:
getprop ro.build.fingerprint returns a fingerprint which seems OK : angler:8.1.0/OPM7.181205…

But ro.build.version.security_patch value is 2019-02-05

Can it come from that ?