yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
Safetynet related issues should be posted in the Magisk General Support / Discussion thread along with device info, Android version, Magisk version and logs. You can also look here:

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] andrew2432:
Install your rom clean as you normally would. Wipe whats needed, flash your rom. Do not flash any root solution, su or otherwise during the procedure. Flash gapps and vendor or whatever is needed specific to your device. Boot to system once and let everything load up. Check safety net on stock ROM no root. Pass? Good, doesn't pass? Grab [MENTION=4544860]osm0sis[/MENTION] unsu script, google or search threads for link. Flash it in twrp and check again! Once native root is removed, you can flash magisk without much effort on most devices. If you currently have a root, you're going to run into issues!

On my pixel xl, RR 8.1 may patch I'm having some crashing issues in 16.0, so I'll need to update to share correct logs. Posting here not beta as I'm not sure what I'm going to do about it other than flash 16.4 and attempt to reproduce.

I've used app systemizer terminal emulator module to move a good old gps app to system, no reason really...and now magisk mounts and links ALL of my system apps in the log? Every app previously installed is binded/mounted/linked to /system/priv-app. Each boot it does this, I'll try to get the magisk log uploaded!

Magisk log:

https://pastebin.com/G2wuc9VT
[Magisk] MrFreek:
Hi guys, having issues with SkyGo app, getting this error 'This app is not supported on rooted android devices, error code: 99z'

The app is hidden using Magisk hide

Using an Samsung S9 - dual sim version

TWRP

Custom ROM from Alexndr https://xdaforums.com/galaxy-s9/samsung-galaxy-s9--s9-cross-device-development/rom-u1arc5-devbase-v5-2-t3764822/

Which includes an edited version of Magisk (16.5)

I've renamed liboemcrypto.so so that Amazon Prime & Netflix work fine (I've also used Magisk hide for those apps & banking apps)

Yet SkyGo & SkyQ just won't work, I've uninstalled them, cleared data but it just doesn't happen.

Has anyone got it working?

Any help is appreciated!
[Magisk] cruse2382:
getting a ctsprofile error with safety net on latest android p dp4 anyone else getting this
[Magisk] Pkt_Lnt:
There are many posts in the Pixel 2 forums stating the same, I've seen probably 20 so far...
[Magisk] cruse2382:
ah did not think to check the pixel 2 forum as im only on the pixel one will nip over and look
[Magisk] pawelik001:
In magisk it passing safetynet, but in Google play says device not certified. Any solution?

Wysłane z mojego ALE-L21 przy użyciu Tapatalka
[Magisk] madbat99:
Safetynet and device certified in playstore are separate. You still need a certified device. Have you cleared data for playstore?
[Magisk] xunholyx:
With gesture navbar set, the back button is visible in home screen after Magisk is flashed on DP4.

Otherwise, no problems really. SafetyNet Check shows "ctsPofile:false", but Magisk hide takes care of that and my bank payment app works, and Google Pay works as well.
[Magisk] xunholyx:
Also getting this lol:

Wallpaper is messed up as well occasionally, and won't scroll proper. Going to pages on the right shows a black space instead of the wp scrolling.

I'm going back to not rooted until John updates.

Just a heads up
[Magisk] yochananmarqos:
Nothing is required to add to Magisk Hide to get Google Pay to work.
[Magisk] €caust:
Select Play Store and Google Play Services in Magisk Hide and reboot system.
[Magisk] Didgeridoohan:
Since it sounds like you've completely wiped your device (Magisk is no longer installed) and it still can't boot, it's probably better if you ask for help in your device's forum. Have you tried doing a completely clean flash of the stock ROM?

That's just Magisk creating the mirror of /system. Completely normal.

Have you tried hiding the Manager? More tips here: https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

It's also possible that there's something about that ROM, that Magisk doesn't hide, that the app doesn't like.

It's not unheard of that the preview releases can't pass SafetyNet. Might simply be that Google didn't bother to add the release to the certification database.

https://www.didgeridoohan.com/magis...and_other_apps_wont_install_or_doesnt_show_up
[Magisk] yochananmarqos:
Again...

Same goes for the Play Store certification status.
[Magisk] aostrom:
Worked this time. Strange...
[Magisk] YK RAJ:
I flashed an incompatible magisk modules on Xiaomi RN5P device and after that getting bootloop.So i flashed Magisk Uninstaller and device rebooted without root.And the problem is that now when i want to install magisk again through TWRP then again getting bootloop.Are modules getting restored or what ??That causing bootloop.Help me ASAP.

THANKS.
[Magisk] xunholyx:
You should probably ask in a Xiaomi thread/forum, don't you think?

EDIT: Just came back to this post and realized it wasn't a P2XL thread. I got here by clicking in a thread there so I thought it was in the P2XL forum.

My appologies.
[Magisk] guest4711:
Restart into TWRP. Open the shell and create a file named ".disable_magisk" (mind the dot, it's necessary) in /cache.

touch /cache/.disable_magisk

. Reboot. Magisk should start in core-only mode (without loading any module). Then you can manage your modules within MagiskManager...
[Magisk] pntba:
hey Guys ,

could anyone say if magisk is currently supported for Xiaomi MI8 ?
[Magisk] YK RAJ:
Did you mean Terminal(Open terminal in twrp)...I dont know much about terminal commands.How to create file name .disable_magisk in /cache??Could you please help me ...Thanks
[Magisk] prot-:
Yeah updated to new Android P beta 3 and safetynet not passing and Android pay not working even though it says it's hidden. Same deal as others
[Magisk] pawelik001:
No

Wysłane z mojego ALE-L21 przy użyciu Tapatalka

---------- Post added at 08:05 AM ---------- Previous post was at 08:04 AM ----------

I already do it

Wysłane z mojego ALE-L21 przy użyciu Tapatalka
[Magisk] guest4711:
As written in my post: Use the touch command...

Enter the command as shown. Finish by pressing enter/return

touch /cache/.disable_magisk

. and yes, the menu point could be named terminal.
[Magisk] Malz01x:
Fixed yet?
[Magisk] Ja_som:
Tweet from topjohnwu:

https://twitter.com/topjohnwu/status/1014059549643247616?s=19

---------- Post added at 09:59 AM ---------- Previous post was at 09:57 AM ----------

Add your device informations to the certification page, then delete data for the Play Store.
[Magisk] TonikJDK:
This is pretty common on previews. Takes a day or two for the server guys to remember to list the new beta as certified on the server side.
[Magisk] prot-:
How do I do that ?

The first part
[Magisk] Ja_som:
http://bfy.tw/IsAz
[Magisk] wogooo:
Tried to install this one on Galaxy A3 2017 but i get error 1. I have debloated Oreo. Link: https://xdaforums.com/samsung-a-ser...3-2017-oreo-minimal-stock-rom-rooted-t3793694

First unrooted with SuperSU uninstaller then flashed 16.0 and 16.4 but both error 1. Any ideas?
[Magisk] MrFreek:
Thank you @Didgeridoohan, Hiding the Magisk manager fixed the issue! :)
[Magisk] ericardo:
Unfortunately, no.
[Magisk] LLStarks:
I had to uninstall Magisk for DP4. It was causing all kinds of soft-resets and visual oddities.
[Magisk] Didgeridoohan:
Since you're passing SafetyNet, you don't need to add your device to the certification page. Just clear data for the Play Store.
[Magisk] metropical:
Having trouble getting Magisk to install on my rooted LG H811 (G4 T-Mo US, MM).

Log follows:

- Device platform: arm64-v8a

- Extracting files

- Patch boot/ramdisk image: /dev/block/mmcblk0p38

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]

KERNEL [21227880]

RAMDISK [5945340]

SECOND [0]

EXTRA [1167360]

PAGESIZE [4096]

NAME []

CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 androidboot.selinux=enforcing msm_rtb.filter=0x37 androidboot.hardware=p1]

CHECKSUM [8d6314b6e7422e42bf42017067c822f026de6f0f]

- Unpacking boot image

KERNEL_FMT [raw]

RAMDISK_FMT [gzip]

- Checking ramdisk status

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Loading cpio: [ramdisk.cpio]

! Boot image patched by other programs

! Please restore stock boot image

Failed!

! Installation failed

This is what I saw:

"Boot image patched by other programs . Please restore stock boot image."

I figured that meant that SuperSU had to go. I removed it with a script I found on XDA.

Now I needed to get to recovery via adb command. Still NG.

Someone suggested Magisk Manager 1st then Magisk from that .apk.

That resulted in:

"Select stock boot image dump in .img or .img.tar format."

Dunno where that is.

Tried this method.

Nope.

What do I have wrong?
[Magisk] Didgeridoohan:
You're on the right track, but you'll also have to restore your device's stock boot image. The script only removes SuperSU files...

Take a look here:

https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs

Again, you'll have to use your device's stock boot image and let the Manager patch that for you, if you opt for this method.

https://www.didgeridoohan.com/magisk/Magisk#hn_Wheres_my_boot_image_for_the_Manager_to_patch
[Magisk] martyfender:
You can usually extract your stock boot image from a rom download if it is available for your device.

Or, if TWRP is available for your device, you can back it up in TWRP and use that image, renaming a copy of it: boot.emmc.win to boot.img.
[Magisk] StuttgartKiwi:
Magisk gets removed during the monthly OTA update on my Pixel XL

Hi, I'm having trouble doing OTA updates while Magisk is installed on my phone.

I've got a 1st-gen Pixel XL (Marlin) running Android 8.1 with stock recovery. I successfully rooted it with Magisk a few months ago, and everything works perfectly fine. The only root app I use on it is AdAway.

However, each month Google publish their monthly OTA update and I can't get Magisk to remain in place during the update. I've tried and failed for the past three monthly OTA updates, and have had to manually re-flash Magisk afterwards, as I lose root each time.

I'm following the instructions at https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md to the letter.

Specifically, today:

1) When the notification for the new OTA update appeared on my phone, I went to Magisk Manager > Uninstall > Restore Images. A toast informed me that the restore was successful.

2) Then I went to the System Updates page and started the update. Step 1 completed, and Step 2 began.

3) At that point I switched back to Magisk Manager and tapped Install > Install > Install to Second Slot. The black console window appeared and showed that this was successful - I've attached a screenshot of this, as well as the log file it generated.

4) Then I switched back to the update page and waited for Step 2 to finish. Then I rebooted the phone as instructed.

5) The phone actually restarted itself 3-4 times - it would get to the white screen with the Google "G" logo on it, then reboot. But after 3-4 times it booted correctly into Android, and I logged in.

6) Then I got an error notification saying that the update hadn't worked. Tapping on this notification gave me an error, "Couldn't Update - installation problem" (see screenshot).

7) Checking the About Phone page showed that it still had the previous version (June 2018) rather than the new version (July 2018). Additionally, I now had lost root - Magisk was no longer installed. So I had to manually reinstall Magisk to root the phone anew.

Not sure what I'm doing wrong here, as I'm following the instructions carefully.

Does it matter exactly when, during Step 2, I go to "Install to Second Slot"? Or can I safely do that at any stage during Step 2?

Any ideas?
[Magisk] andrew2432:
[MENTION=4803251]StuttgartKiwi[/MENTION]

I think you need to fully update first before installing magisk related things, it sounds like you installed it before letting the update finish?
[Magisk] StuttgartKiwi:
By "fully update", do you mean waiting for Step 2 to completely finish (but not reboot) before I switch to Magisk Manager > "Install to Second Slot"?

The instructions at https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md state:

Do you think that's not correct? Maybe the instructions need to be adjusted?
[Magisk] andrew2432:
[MENTION=4803251]StuttgartKiwi[/MENTION]

I thought for pixel we needed to uninstall root and twrp completely to take the ota. Uninstall, ota, reboot, retwrp, reroot.

Reading that though I am not entirely sure!
[Magisk] aznsensazn29:
How did you get GPay to work? My banking apps work fine and it seems like Magisk Hide is working for them, but I just can't seem to get Google Pay working. Whenever I try to add a card it always throws the "Couldn't finish setup to pay in stores, This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way." I just updated to Dp4, but Magisk 16.4 had been working with Dp3 for Google Pay. Any thoughts?
[Magisk] EstiR86:
I think it's a Google Pay problem on DP4 don't think we can do anything but wait for a fix.
[Magisk] Pkt_Lnt:
After the SU uninstaller you need to flash a stock boot image. Copy the full recovery log in TWRP and post it here. Error 1 is not helpful, the recovery log will have hundreds of lines and give all the fine details we need to see to help you.
[Magisk] wogooo:
How do i flash a stock boot image? I don't even know what it is.

And where do i find recovery log? Or do you mean the text of the installation?
[Magisk] metropical:
OK, thanks digieridoohan. I think I get it. I'll work with TWRP.

---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------

thanks Marty. Gonna give TWRP a shot now.

---------- Post added at 02:22 PM ---------- Previous post was at 01:40 PM ----------

Ran the SuperSU removal script. Rebooted.

Then TWRP'd a back up of just the boot partition. Rebooted.

Copied boot.emmc.win to Magisk folder, then renamed it boot.img. Rebooted.

Tried the install again from MM.

Just to reiterate, this H811 is rooted, but it is stock 20x ROM.

log:

- Device platform: arm64-v8a

- Extracting files

- Unpacking boot image

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]

KERNEL [21227880]

RAMDISK [5945341]

SECOND [0]

EXTRA [1167360]

PAGESIZE [4096]

NAME []

CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 androidboot.selinux=enforcing msm_rtb.filter=0x37 androidboot.hardware=p1]

CHECKSUM [ee3ce47c1d003613509e9221d331ca6c6831784f]

KERNEL_FMT [raw]

RAMDISK_FMT [gzip]

- Checking ramdisk status

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Loading cpio: [ramdisk.cpio]

! Boot image patched by other programs

! Please restore stock boot image

Failed!

! Installation failed
[Magisk] Pkt_Lnt:
With these basic questions it shows you are in the wrong thread, this is for *Beta Testing*, please move your questions to this thread. Thanks. I'll answer this over threre.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
[Magisk] Pkt_Lnt:
Moved from beta thread>

You can find the stock boot image in the stock ROM for your device or in your device forum and flash it in TWRP.

Recovery log is in TWRP under Advanced menu, and then it will have an option to copy to sd card (or internal storage).

Try this for more info in all sections.

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] metropical:
I found a stock boot.img elsewhere on the interwebs.

Tried MM with it. Seemed to go OK>

Log:

- Device platform: arm64-v8a

- Extracting files

- Unpacking boot image

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]

KERNEL [21227880]

RAMDISK [5738882]

SECOND [0]

EXTRA [1167360]

PAGESIZE [4096]

NAME []

CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 androidboot.selinux=enforcing msm_rtb.filter=0x37 androidboot.hardware=p1]

CHECKSUM [1cba0e6ce8511bcc04460b87ee42883cc1f6e221]

KERNEL_FMT [raw]

RAMDISK_FMT [gzip]

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Loading cpio: [ramdisk.cpio]

- Checking ramdisk status

- Stock boot image detected

- Backing up stock boot image

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Compressing to [stock_boot_c8412c82a4448a7bc78936bce4813c7cc26d3e8e.img.gz]

- Patching ramdisk

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Loading cpio: [ramdisk.cpio]

Add entry [init] (0750)

Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]

Remove [verity_key]

Save SHA1: [c8412c82a4448a7bc78936bce4813c7cc26d3e8e] -> [.backup/.sha1]

Loading cpio: [ramdisk.cpio.orig]

Backup mismatch entry: [init] -> [.backup/init]

Backup missing entry: [verity_key] -> [.backup/verity_key]

Dump cpio: [ramdisk.cpio]

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Patch @ 0124E6CE [736B69705F696E697472616D6673]->[77616E745F696E697472616D6673]

- Repacking boot image

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]

KERNEL [21227880]

RAMDISK [5738882]

SECOND [0]

EXTRA [1167360]

PAGESIZE [4096]

NAME []

CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 androidboot.selinux=enforcing msm_rtb.filter=0x37 androidboot.hardware=p1]

CHECKSUM [1cba0e6ce8511bcc04460b87ee42883cc1f6e221]

KERNEL_FMT [raw]

RAMDISK_FMT [gzip]

Repack to boot image: [new-boot.img]

KERNEL [21227880]

RAMDISK [6113614]

SECOND [0]

EXTRA [1167360]

PAGESIZE [4096]

NAME []

CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 androidboot.selinux=enforcing msm_rtb.filter=0x37 androidboot.hardware=p1]

CHECKSUM [321e4743e913a80dbd85f78c25f7cbd233bb9e6d]

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Cleaning up...

*********************************

Patched Boot Image is placed in

/storage/emulated/0/MagiskManager/patched_boot.img

*********************************

- All done!

But MM still shows "Magsisk is not installed.
[Magisk] milomak:
is it significant that persist.magisk.hide gets seemingly removed

07-03 20:28:38.812 1951 1958 D Magisk : resetprop: getprop [persist.magisk.hide]: [1]
07-03 20:28:38.812 1951 1974 D Magisk : resetprop: deleteprop [persist.magisk.hide]
07-03 20:28:38.812 1951 1974 D Magisk : resetprop: unlink [/data/property/persist.magisk.hide]

07-03 20:35:07.066 9380 9380 D Magisk : resetprop: prop [persist.magisk.hide] does not exist
07-03 20:35:07.474 9421 9421 D Magisk : resetprop: prop [persist.magisk.hide] does not exist

my absa banking app detects magisk even though it is included in magiskhide

$ cat magisk_debug.log | grep barclays -b5 -a5
504534-07-03 20:28:38.816 1951 1974 I Magisk : hide_list: [com.google.android.gms.unstable]
504622-07-03 20:28:38.748 477 481 I chatty : uid=0(root) /system/bin/vold identical 1 line
504711-07-03 20:28:38.805 477 481 D vold : Disk at 7:0 changed
504774-07-03 20:28:38.863 477 1930 D Cryptfs : post_fs_data done
504835-07-03 20:28:38.865 477 1930 D Cryptfs : Just triggered restart_framework
504911:07-03 20:28:38.915 1951 1974 I Magisk : hide_list: [com.barclays.absa.banking]
504993-07-03 20:28:38.921 1975 1975 I bootstat: Service started: /system/bin/bootstat -r post_decrypt_time_elapsed
505104-07-03 20:28:38.978 1951 1974 I Magisk : hide_list: [za.co.fnb.connect.itt]
505182-07-03 20:28:39.023 1951 1974 I Magisk : hide_list: [com.snapchat.android]
505259-07-03 20:28:39.044 1981 1981 E /system/vendor/bin/adsprpcd: vendor/qcom/proprietary/adsprpc/src/adsprpcd.c:29:adsp daemon starting
505392-07-03 20:28:39.044 1977 1977 E QCNEA : Cne Version 4.9
--
614578-07-03 20:31:39.167 6176 6176 D Magisk : resetprop: deleteprop [init.svc.magisk_service]
614669-07-03 20:31:39.167 6176 6176 D Magisk : resetprop: deleteprop [init.svc.magisk_startup]
614760-07-03 20:31:39.168 6176 6176 D Magisk : resetprop: deleteprop [ro.boottime.magisk_service]
614854-07-03 20:31:39.168 6176 6176 D Magisk : resetprop: deleteprop [ro.boottime.magisk_startup]
614948-07-03 20:31:39.170 6176 6176 D Magisk : hide_daemon: Unmounted (/sbin)
615022:07-03 20:32:48.432 1951 1974 I Magisk : proc_monitor: com.barclays.absa.banking (PID=7389 ns=mnt:[4026534404])
615136-07-03 20:32:48.435 7396 7396 D Magisk : hide_daemon: start unmount for pid=[7389]
615221-07-03 20:32:48.435 7396 7396 D Magisk : hide_utils: Cleaning magisk props
615298-07-03 20:32:48.443 7396 7396 D Magisk : hide_daemon: Unmounted (/sbin)
615372-07-03 20:33:10.676 1951 1974 I Magisk : proc_monitor: com.snapchat.android (PID=7603 ns=mnt:[4026534384])
615481-07-03 20:33:10.682 7609 7609 D Magisk : hide_daemon: start unmount for pid=[7603]
[Magisk] wogooo:
is it the AP_A320FLXXU1AQE1_CL10926218_QB13484362_REV00_user_low_ship.tar.md5 file which is 3.8 gb?
[Magisk] Pkt_Lnt:
I do not know, best to ask in your device forum here on XDA.

I use a Nexus 6 with Magisk and have a Pixel 2 XL.
[Magisk] wogooo:
ok, thanks a lot for help! :)
[Magisk] ianmacd:
Yes. Amongst other things, that tar archive will contain either a boot.img or a boot.img.lz4. Extract that, un-lz4 it if it's a compressed image, and use TWRP to flash it to your boot partition.

At that point, without rebooting, you can (re)install Magisk.
[Magisk] wogooo:
Thanks a lot! Now im in TWRP...selected the boot.img. I guess i select "BOOT" as the partition to flash, right? :) just to be sure :highfive:
[Magisk] panchogg:
Samsung Galaxy GT-i9300 Lineage 14.01 with Magisk 16 issue

Hi, i need help

Using:

1.- Recovery TWRP version 3.2.1-0.

2.- Lineage-14.01-20180628-nightly.i9300-signed.zip.

3.- Magisk 16.

4.- OpenGApps.

5.- Samsung Galaxy GT-i9300 Intl

Flollowing this steps:

1.- Full wipe Phone (Everething).

2.- I installed Lineage 14.1 For I9300 (Lineage-14.01-20180628-nightly.i9300-signed.zip) (no reboot).

3.- Installed magisk16.zip.

4.- Installed OpenGApps.

5.-Reboot.

The problem is:

1.- Charging phone with data mobile activated, after few minutes it do not response, do not wakeup, simply hangs.

2.- Standby phone with data mobile activated, after few minutes it do not response, do not wakeup, simply hangs.

3.- with wifi and data mobile activated, after few minutes it do not response, do not wakeup, simply hangs.

4.- with wifi activated or deactivated phone works fines.

why i need Magisk?.

Because i need modules Dolby Atmos Axon 7 and others. (Dolby Atmos By ahrion no work without Magisk)

I tried full clean installation, same issues. testing now Magisk 16.4 beta.

Magisk's log only show this error: " proc_monitor: Your kernel doesn't support mount namespace "

can some one help me?
[Magisk] ianmacd:
Yes, that's the one.
[Magisk] wogooo:
It didnt work. I use a debloated rom of android 8.1. Someone made a rom that i flashed using the Restore function in twrp.

I flashed boot.img from stock Android 8.0, because Samsung didn't release 8.1 yet. But didn't work.

Then i tried to extract boot.img from the rom of the guy who made this, also didn't help :(

https://xdaforums.com/samsung-a-ser...3-2017-oreo-minimal-stock-rom-rooted-t3793694

Thx for help anyway. If you have any further suggestions... :)
[Magisk] martyfender:
You need a newer kernel.
[Magisk] panchogg:
Ok, wich Kernel? Can your tell me wich?

Magisk 14.5 works fine, but id old.

Namespace is nesscesary?
[Magisk] spyjoshx:
I'm sorry if this is way off base, but your link in the main thread (tiny.cc/latestmanager) to download magisk manager goes to a very scammy looking site. Can you confirm this?
[Magisk] Artim_96:
From the announcement thread: