yashsingh1/xdaforums huggingface dataset:
[Magisk] ctsuresh:
Hi, thanks for your reply. Are you talking Hide magisk manager. If yes, it is not activated. Still I could not find app to clear data and cache. Refer screenshot
[Magisk] martyfender:
Did you go into Android settings, apps and look for it there? That is where you clear it's data.
[Magisk] ctsuresh:
Yes, you are correct. I am going to setting>manage apps but couldn't find magisk manager. All other apps available. I don't know why this happening.
[Magisk] mixlex:
I only responded to him in that way because his post was "19.1 has issues, staying with 18.1, it rocks". So I responded to a completely useless post with an equally useless post.
[Magisk] tech_head:
Already fixed.

I thought I was editing the systemless version.

Turns out I wasn't.
[Magisk] Ingan121:
It looks 19.1 made a new detection method to be possible, which cannot be bypassed even with my UDSBypass script.

In 19.0, this was detected only when I was using EdXposed module, but since 19.1, it is detected at all.

I think it is searching for 'magisk' string in all system files, since all of the detection name is in small case (unlike other Magisk detections.)
[Magisk] Poppeye0:
Oh great, an old testament kind of guy. It will all end in bloodshed and tears this way, you know.

Gesendet von meinem Redmi Note 4X mit Tapatalk
[Magisk] mixlex:
Yes I agree. Sometimes it's better to just say nothing, but I couldn't help myself.
[Magisk] Tommasoleone:
Hi, sorry for my english. I have write many post but i dont receive answer. I have try to root many device but with android 9, after root fingerprint won't work, screen won’t unlock and PIN not working. I’ve entered the correct PIN code but it’s still not working. Root and magisk working. Only device rooted with dr.ketan fix working. How to fix this issue? Thanks!
[Magisk] remi13014:
Hello,

I have an Honor 8 ( FRD-09C432B394) with a old Magisk version(V14). Today I uninstalled it and now I wanna try to install the latest version

I extracted boot.emmc.win from my nandroid backup (TWRP), should I install/patched with this file ? is it like boot.img ?

Thanks for help
[Magisk] jcmm11:
That should simply be a renamed img file. Make sure you made a copy (so you don't lose the version in your nandroid). Rename it to boot.img and patch it. Or, even easier, just flash the Magisk zip via TWRP. Either way make sure you keep a copy of the install log so if you have problems after rebooting you have a log to post instead of just saying "it's boken. Fix please"

One question - is the boot file from before or after you removed Magisk? Stock would be better - especially upgrading from such an old version.
[Magisk] M madheswaran:
Already install magisk manager.....

How to install magisk app
[Magisk] remi13014:
Thanks for you help,

my backup is from after I uninstalled Magisk . I uninstalled using TWRP so i guess it restored an old boot.img but i' don't know if it's stock or not :/

Tomorrow, I will try to just flash with TWRP the latest version of Magisk. If I have problems I will flash the patched boot from Magisk else I will uninstall it or even use my nandroid backup
[Magisk] dr4go:
Not sure if that is related, but I use an app, which suddenly wasn't working anymore (Payback, at.payback.client.android, see apkmirror for an older version of Payback [de.payback.client.android], which is affected as well), because it was detecting root...

I read a lot and found out, that many users think / believe, that the gms service higher than 14.7.99 causes problems. So I wrongly believed this and was mislead... Long story short: the reason for the root detection was EdXposed v0.4.1.2 (both Sandhook and yahfa), whereas v0.3.1.7 is working fine... What i believe now, is, that it is related to the re-added resource hooking functionality, which would make version >= 0.4.1.2 less favorable regarding detection...
[Magisk] FoOlKeN:
Rooted A600FN on android pie

I have a problem on my rooted Samsung A600FN (android 9).

So when i want to set up face unlock or Fingerprint it ask to put a PIN code when i put it and confirm,PIN request show and when i put my PIN code that say incorrect i try several times but stay same...But its not all when i connect on samsung account it say processus failed
[Magisk] pkgnex:
YES.

I am also experiencing this.

Stock pixel 2 room.
[Magisk] martyfender:
Yes, magisk has built in exe files, but there is no Magisk app, per say.

The best way to install Magisk is through TWRP if your device has a version of this custom recovery available for it. If not, you can copy a stock boot.img to the device and patch it with the Magisk Manager. you would then flash that patched boot.img through fastboot, or in the case of Samsung devices, with Odin. If you can't use either of those methods, you may not be able to use Magisk to root your device. There is a third method, but your device must already be rooted to use this option: direct install in the Magisk Manager.

It is also hard to help you when you didn't provide even basic information as noted here:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] Tommasoleone:
I have the same issue, issue its only with Android 9. I tried with Magisk 18, 18.1 and 19.1, with various Manger and with different noverity patches but the problem does not resolve!
[Magisk] HpNoTiQ:
Hi,

Since users reported problem with encryption, I've flashed no-dm verify zip (https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip) and I've got no bootloops now : i've installed last canary build 19.2 with no problem!!
[Magisk] Ingan121:
It looks Magisk 19.1 is leaking its running state!

If there are any su processes running, Liapp(http://lockincomp.com) will detect them and throw 'RSH MAGISK' and 'ROOTED magisk' errors. If they're not running (or killed by 'killall su'), it will throw just a 'ROOTED MAGISK' error by using a stupid socket name detection, and it can be bypassed by my UDSBypass script. However, the script must be run as root, so it cannot be bypassed. (It still can be bypassed by adding 'killall su' in the script, but reboot is required to get root back.)

19.0 didn't have this issue unless EdXposed module is installed and enabled.
[Magisk] Yippee-ki-yay:
Thanks, I'll try this next time (bootloop whyred)
[Magisk] samz2:
Facing a strange issue here, I have version 18.0

SafetyNet check shows pass

But play store shows device not certified

Also updating to 19.1 on Skydragon ROM 9.0 on OP3 causes blank screen after reboot and pin entry. Any ideas?

---------- Post added at 12:16 PM ---------- Previous post was at 12:16 PM ----------

Facing a strange issue here, I have version 18.0

SafetyNet check shows pass

But play store shows device not certified

Also updating to 19.1 on Skydragon ROM 9.0 on OP3 causes blank screen after reboot and pin entry. Any ideas?
[Magisk] guest4711:
Clean Cache and Data of playstore app. Reboot. Try again...
[Magisk] WoltreX:
Magisk v19.1

- [General] Support recovery based Magisk

- [General] Support Android Q Beta 2

- [MagiskInit] New sbin overlay setup process for better compatibility

- [MagiskInit] Allow long pressing volume up to boot to recovery in recovery mode

- [MagicMount] Use proper system_root mirror

- [MagicMount] Use self created device nodes for mirrors

- [MagicMount] Do not allow adding new files/folders in partition root folder (e.g. /system or /vendor)

Magisk Manager

v7.1.2

- Support patching Samsung AP firmware

- Much better module downloading mechanism

BUG #1: Can not mount modules folder. (data/adb/modules -> sbin/.magisk/modules) Error: No such folder or directory.

*Installed modules are working fine. But users cant see installed modules in manager.

BUG #2 - To avoid this problem, you need to use the old version. However, this time there are errors due to required addional installation.

*I think the additional installation was rearranged according to 19.1. Due to this problem, older versions cannot be installed properly and do not work. (v18.1 - v17)

Solution proposal: An arrangement is required for manual installation of files required for additional installation.

[MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Didgeridoohan:
Known: https://github.com/topjohnwu/Magisk/issues/1407

Did you also downgrade the Manager? If not, try that. At the very least, no matter what Manager version you have installed: https://www.didgeridoohan.com/magisk/Magisk#hn_Additional_setup_failed
[Magisk] FoOlKeN:
I need a solution:crying:..don't want to go back to oreo experience
[Magisk] ctsuresh:
Yes, you are correct. I am going to setting>manage apps but couldn't find magisk manager. All other apps available. I don't know why this happening.

Edit: I found the causes it is with Edxposed manager. Now, I changed to Edxposed installer its working fine. Passing safety net.
[Magisk] zgfg:
The same probllem on Huawei P9 and P9 Plus with Nougat (no problem with Oreo)

https://xdaforums.com/showpost.php?p=79475866&postcount=1467

https://github.com/topjohnwu/Magisk/issues/1390

https://github.com/topjohnwu/Magisk/issues/1409

Magisk v19.x (19.0 Beta, 19.1 Official, 19.2 Canary Debug), clean install or update from v18.1 (no problem on v18.1 or earlier):

- On first boot, it asks for Password to Decrypt Storage

- Entered PIN, it says Password is ok but Storage was corrupted

- No way to boot to System, it only offers Factory Reset

However, rebooting to TWRP and flashing back Magisk v18.1 patched Boot image, and everything is ok again (no Password needed, Storage not corrupted).

Cannot capture bootlog by putting a script to /data/adb/post-fs-data.d.

IMO, v19.1 cannot mount Cache partition to save the log while it complains that Storage is corrupted.

(Reverting back to v18.1 and bootlig.log is successfully created on the first boot)
[Magisk] Ingan121:
It is not being detected again. I don't know why. It's just very wierd.
[Magisk] WoltreX:
Yes, compatible managers were used.

*v 18.1 - 7.1.1

*v 19.1 - 7.1.2 (current version)
[Magisk] Wolfcity:
On 19.1 without bigger problems, installed MM 7.1.2 and flashed zip from TWRP, first magisk 19.1 after that Cerberus kernel, all on my testing device (Moto G 2014 / AEX 7.1 2 /Cerberus kernel). Just two of my modules vanished (Viper4Android / YT Vanced), had to reflash them, all other modules stayed intact. Btw, beta 19 caused reboots to the bootloader.

Next step would be to update magisk on my daily driver (Moto G5+ /Oreo stock).

There's one thing in the changelog that I don't understand (or maybe misinterpret):

- [MagicMount] Do not allow adding new files/folders in partition root folder (e.g. /system or /vendor)

Does that mean it's not possible anymore to change things like (for example) bootanimation?

I know that can be done systemless but can cause problems too because it's very early in the boot process. Why not leave that option to the user?

For me those things never caused problems.
[Magisk] AndrzejDwo:
You still can make changes in /system but modules can't. I think this change is made to ensure Magisk being undetected.
[Magisk] x_crys_x:
someone please help me, I flashed 19.1 like 6 days ago and my battery drainage is so bad, normally I'd go home with at least 60% after 6h of school (no i don't use it) but now I come back with max 25%, yes this started as soon as I flashed the update, no problems with previous version of magisk.

Using Samsung s8, android 8
[Magisk] guest4711:
It means that you cannot put files into the directory /system, but you can put them into any subdirectory of /system, e.g. /system/media/ . So you may still exchange the bootanimation.zip or any app in /system/apps or /system/priv-app or any setting in /system/etc. But you may not systemless create /system/foo
[Magisk] Ersid Kapaj:
I have updated magisk to the lastest version and it won't install on my Doogee Mix 6/64
[Magisk] Dant9900:
Sorry if this has been asked before. I currently have an LGv30+, on Oreo. I have Magisk v17.3 and Magisk Manager 6.1. What is the recommended method to get to the latest stable versions of both? I have read about flashing the Magisk uninstaller then reflashing with new version and upgrading within the Magisk Manager but just unsure which is the best method and the exact steps for each. TIA.
[Magisk] celloh123:
Can watch stuff from netflix but can't download stuff from netflix
[Magisk] Ersid Kapaj:
Help Doogee Mix 6/64
[Magisk] drezz2:
when you enter into cerberus app..is not requesting the root continuously? you see if the toast does not disappear and the app is very slow
[Magisk] Jhonn1012:
Hola tengo un problema al actualizar magisk a la versión 19.1 (19100) al reiniciar mi celular me dice que hubo un problema al desencriptar algunos archivos y me dice qué restablesca de fabrica gracias
[Magisk] AndrzejDwo:
It's international forum, please use English next time if you want any support.

Translation by G:

"Hi, I have a problem updating magisk to version 19.1 (19100) when I rebooted my cell phone and it tells me there was a problem decrypting some files and it tells me what. Factory reset thank you"
[Magisk] jcmm11:
1 - make sure you have backups, just in case.

2 - first try just upgrade from within Magisk Manager (install, direct install, after updating Manager)

3 - if that doesn't work flash the un-installer and then flash the new Magisk zip via TWRP.

Keep all logs so if you do run into issues you can post them.
[Magisk] Holzknoten:
https://xdaforums.com/showpost.php?p=79454036&postcount=33058

same Problem here:

I was updating magisk to version 19.1. After rebooted my HUAWEI mate 8, it tells me my password of decrypting is correct but the decrypted file is maybee damaged. I have to do a Factory reset.

Is there an option to downgrade to my pre version i have used (18.1)? i dont want to Factory reset and recovery all stuff.
[Magisk] zgfg:
Known problem with Magisk v19.x on Huawei phones (P9, P9 Plus, P9 Lite and now your Mate 8) with Nougat, see

https://xdaforums.com/showpost.php?p=79457797&postcount=1728

Do not accept Factory Reset, it's not needed !!!

You have to reboot to TWRP and restore a backup of your previous Boot partition - then just reboot and continue using your older Magisk (v18.1)

Or, flash by TWRP (or from Fastboot) Boot.img, patched with the older Magisk (v18.1)

If you don't have either the backup or image of your patched Boot, then download (Firmware Finder on PC) update.zip for your current stock firmware, unzip and extract Boot.img from update.app by Huawei Update Extractor (procedure for Huawei, IMO should apply also to Mate).

Flash by TWRP or Fastboot, reboot and reinstall Magisk v18.1 from the zip

---------- Post added at 07:55 AM ---------- Previous post was at 07:38 AM ----------

First, please write in English here.

Second, you must always specify your phone make, model, firmware (and custom modification, if running custom ROM, etc)

If your phone is Huawei with Nougat, see above
[Magisk] Holzknoten:
Well done. "Do not accept Factory Reset, it's not needed !!!"

Thanks for the step by step intoduction. :):good:

Now i am back with working boot image and magisk (v18.1).

New Problem: I can't unlock my screen. I have to draw my sign to unlock but it does'n match anymore. :(

:angel: Solution: (link)

1. Start TWRP

2. Advanced > File Manager, and go to the /data/system folder

3. rename these files

locksettings.db

locksettings.db-shm

locksettings.db-wal
[Magisk] Archangel:
Magisk V19 working perfectly on my Pixel 3a!
[Magisk] tramp20:
Are there any news for this problem?
[Magisk] Wolfcity:
I have flashed a kernel called Cerberus. Has nothing to do with the app of the same name.
[Magisk] lordalireza:
after version 19 i cant boot into recovery. when i press volume up it just restarts and gets stuck in boot. i have to restart to boot again. phone is xperia z2.
[Magisk] samhhmobil:
This is a known bug in 19.1 and affects all SONY Xperia-Models with S1-Bootloader. (I tested it with Xperia Z, C6603, Yuga).

The only workaround is to reflash the boot partition with a backup (boot.img), you probably made before, and install magisk 18.1 again. TWRP is in FOTAKernel partition, and should be accessible again (if not, reinstall the image of TWRP again).

Hope, this bug will be fixed soon in magisk.

samhhmobil

PS

Of course you can recover from your youngest NAND-backup, made in TWRP, but for that you must flash twrp.img via fastboot into your boot-partition (be careful: as long as this is done and nothing is recovered, the phone will just ONLY boot into recovery now).
[Magisk] drezz2:
sorry
[Magisk] alex70italy:
hi, i upgrade my 18.1 on 19 with app on the phone.

My lg g6 going in bootloop, it's possible resolve this problem without reflash all firmware?

My rom it's stock, i enter into twrp.

I try refresh magisk 18.1 but notingh, bootloop it's present
[Magisk] VampiruX:
I have exactly the same trouble as Looki75.

But, for me (Galaxy S8, TWRP, Android 7 stock ROM), after disabling journaling and notifications, it doesn't work. When I install V19.1, either by direct install via Magisk Manager or via Zip file in TWRP, the result is always the same "Magisk is not installed " message in Magisk Manager and no appli can get root status.

Go back to V18.1 one more time.

BR.
[Magisk] Dant9900:
Thanks jcmm11 for your response. What if I want to go to v18.1 instead of v19.1? Do I upgrade Magisk Manager to v7.1.2 then flash Magisk Uninstall and reflash Magisk v18.1 via TWRP? Just a little worried about v19.1 as some people are having issues with it. Thanks
[Magisk] zgfg:
As mentioned in several previous posts, before trying to update Magisk, make a backup from TWRP.

If anything goes wrong with the new Magisk, restore your backup with the older version of Magisk.

Usually, it will be enough only to restore backup of the Boot/Ramdisk partition.

You can also do. the following:

- have the image file of your stock boot/ramdisk

- every time before you update Magisk, apply Magisk patch to the stock boot/ramdisk file and save it with a new name, indicating by which version of Magisk it was patched

- if anything goes wrong with the new Magisk, flash from Fastboot or by TWRP the boot/ramdisk file patched by an older version of Magisk
[Magisk] panchogg:
Making a simgle module Magisk 19.1 can't mount /system/vendor/etc/any-folder by example:

/system/vendor/etc/dolby

Heeeellp
[Magisk] siiie:
Can't install Magisk after updating to OxygenOS 9.0.5

I have Oneplus 5

I had 19.1 on 9.0.4 - Uninstalled it before flashing 9.0.5 and tried reinstall it

I'm getting "Unsupported/Unknown image format" when trying to install Magisk 19.1 via Magisk manager 7.1.2

When trying to install Magisk via recovery, i'm getting a bootloop

I tried to extract boot.img from previous version 9.0.4

Both boot.img versions (9.0.4 & 9.0.5) gained the same result - "Unsupported/Unknown image format"

Attaching 9.0.5 boot.img

https://drive.google.com/file/d/1sq1kDkgGWUoFOZlFk3hEueWr8mmruibk/view?usp=sharing
[Magisk] jcmm11:
Some people are having issues, most people aren't (remember that the people that aren't you're probably not hearing from. Since the people that do have an issue are making all the noise it always seems worse than it actually is)

If you want the most foolproof method (this applies for any version).

1) make a backup, that way no matter what happens you can get back to where you are. No backup = no excuse if something goes wrong (and that's always possible, even if not probable. A bolt of lightning might come and fry your phone while you're upgrading it.)

2) download the zip of whatever version you want to install.

3) extract the magisk.apk from the common subdirectory of the zip file

4) make sure you have a copy of a stock (unrooted) boot image.

Boot into TWRP

5) flash the un-installer.

6) flash the stock boot image.

7) flash the Magisk zip

8) save a copy of the TWRP log.

9) reboot.

10) if the manager didn't get installed install the apk you extracted in #3.

If you have any problems and you expect help make sure you post #8

#6 should be redundant. #5 should theoretically restore stock, but you want as foolproof as possible.
[Magisk] eliotargy:
I have tbe Galaxy Note 9 N9600 Snapdragon. I can't get boot.img to patch with magisk. Is it impossible to patch with this version? See attachment.
[Magisk] SebaS-DG:
Magisk is making Repetitouch app, freeze everything for 1 second for every action (play/pause/record) the app does.
[Magisk] wozhere:
Many magisk users globally, do not know of this thread.

If fellow users of your various Android devices are having issues with Magisk on other xda sub-forums or other forums or elsewhere online, please post Links of this thread in those places.

And tell them to read and post here. So Magisk users know about this thread and post their feedback here.

Thanks.
[Magisk] Fauzannicely:
I installed magisk v19.1 before, but sometimes this happens, and I have to reinstall it again ,how to fix it ?
[Magisk] Grin59:
Edit: after several reboots and a few reinstalls everything is working well

My modules don't seem to work even though, they're enabled. Anyone have a fix?
[Magisk] Ps24u:
After updating to 19.1, I notice a strange behavior: some apps are just failing to launch.

I'll see the launch screen (exemple Youtube) and it hangs there for 20+ seconds.

It's random, happens once in a while. All apps are affected (not only root apps).

Sometimes it'll eventually load, sometimes I have to terminate the app manually.

Restarting the same app right after always works normally.

Sadly it doesn't generate anything in Magisk log..

Never had such issue on 18.1 with same settings and modules. On Xperia Z5C / 7.1.1.

So I would like to downgrade back to 18.1. What is the recommended procedure to do so?

I would like to keep settings and modules if possible. (my modules haven't changed between 18.1 and 19.1)
[Magisk] zgfg:
It's the same/similar procedure for all phones/users who have problems with v19.x and want to go back to v18.1.

Discussed in this thread last two days, please read.

You may just restore Boot/Ramdisk with v18.1 backup in TWRP (or restore complete Nandroid backup if you did more changes by experimenting with v19.1 and you want to revert).

Or flash from Fastboot or by TWRP the image file of Boot/Ramdisk partition patched with v18.1.

Or uninstall Magisk (and/or flash the original/stock Boot/Ramdisk) and install Magisk v18.1 by TWRP, and reinstall the modules.

It depends did you keep up to date TWRP backups, and/or do you have image file of your Boot/Ramdisk patched by v18.1
[Magisk] wyt18:
Magisk module to edit /oem folder

I'm just starting to learn how to write my own modules to execute file replacements systemlessly. All going well but I have a file in /oem/media that I need to either delete or replace. I'm finding that my modules can only edit folders that are from the /system tree. Is there any way to edit the /oem folder?

I used the symlink method to edit the /data folder, but that only seems to work for file replacements, not deletions ...
[Magisk] vladone97:
I'm having issues with the latest Magisk version. Previously, I had Magisk 18.0 and Magisk Manager 6.1.0. I updated Magisk Manager to 7.1.2 then I tried to install the latest Magisk. I tapped direct install, then rebooted when it was done and now I lost my root. Magisk Manager says that Magisk isn't installed. If I try to flash the Magisk 19.1 zip in TWRP, it says zip signature verification failed.

I'm using a Samsung Galaxy S8 with Android 7.0
[Magisk] RMarques:
OP5 latest Magisk & Magisk manager. I've lost root twice in the last 4 days...anyone else having this problem?
[Magisk] jcmm11:
Turn off zip signature verification in TWRP. There's nothing to verify against so it'll always fail. This applies to almost all zip files that you'd attempt to flash