yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Probably. The last factory image for the 6P had security patch 2018-12-05, so the fingerprint from that won't work with any other patch date. You could use my MagiskHide Props Config module and set a custom prop for ro.build.version.security_patch to 2018-12-05.
[Magisk] demonoidmaster:
And did you try an older build of the gpay app or did you just clean flash without trying that?

Tbh for apps that are like these you should use SwiftBackup or whatever other backup app to do an apk+data backup that you can restore at any time if an app that's been updated doesn't work

---------- Post added at 10:17 PM ---------- Previous post was at 10:11 PM ----------

Magisk isn't made for Kitkat, update your rom if possible or flash custom rom
[Magisk] beardymarrow:
Magisk supports down to 4.2, so kitkat is fine.
[Magisk] demonoidmaster:
He should wait until there's a twrp version that decrypt the partition right , because that way he can then copy over everything he wants to keep

However yeah he could do the dm-verity thing to see if it'll work, but if doesn't then well yeah he should wait since right now his only safety net is a twrp that could let him transfer over stuff before nuking his device

---------- Post added at 10:26 PM ---------- Previous post was at 10:22 PM ----------

In 18.1, but then again it could either be that specific kitkat rom made for his phone that could be the problem or the phone itself, he would have to find out what target partition his device has and do the magisk patched boot img manually since the installer cant

---------- Post added at 10:27 PM ---------- Previous post was at 10:26 PM ----------

Enable what you disabled?

Safetynet = google play services and apps
[Magisk] Pkt_Lnt:
You missed the latest updates in the latest release.

https://xdaforums.com/showpost.php?p=78829088&postcount=49
[Magisk] demonoidmaster:
Then just go and disable this

Prevent phone from sleeping

Run in background

Don't disable the app outright *facepalm*
[Magisk] demonoidmaster:
Someone already corrected me about the backwards compatibility change in 18.1
[Magisk] Karthik Karhem:
Marvellous Job
[Magisk] MDV106:
Where exactly are these settings that allow you to toggle on/off those permissions? Mine dont have an option to disable them
[Magisk] demonoidmaster:
Appops
[Magisk] parag60288:
Can any third party app be responsible for triggering safetynet?

My device fails on basic integrity as well as ctsProfile.

Screenshots of magisk as well as list of apps installed.

My device showed safetynet passed for a day. But now it is showing as failed.

Usb debugging is also disabled.
[Magisk] blakegriplingph:
Any idea on what to do with this? I've got a LeapFrog Epic running on 4.4.2 which I had to sign the patched boot image using the Mediatek sign tool due to secure boot check being implemented on the tablet. Magisk did show up as enabled upon flashing said boot image, but for some reason I get request rejected errors whenever I try to invoke root. SuperSU's already uninstalled prior to installing Magisk, btw.

02-20 18:01:56.445 127 127 I Magisk : * Creating /sbin overlay
02-20 18:01:56.468 129 129 I Magisk : * Device API level: 19
02-20 18:01:56.468 129 129 I Magisk : Magisk v18.1(18100) daemon started
02-20 18:01:56.473 129 130 I Magisk : ** post-fs-data mode running
02-20 18:01:56.473 129 130 I Magisk : * Initializing Magisk environment
02-20 18:01:56.633 129 130 I Magisk : * Mounting mirrors
02-20 18:01:56.634 129 130 I Magisk : mount: /sbin/.magisk/mirror/system
02-20 18:01:56.635 129 130 I Magisk : link: /sbin/.magisk/mirror/vendor
02-20 18:01:56.635 129 130 I Magisk : bind_mount: /sbin/.magisk/mirror/bin
02-20 18:01:56.635 129 130 I Magisk : * Setting up internal busybox
02-20 18:01:56.672 136 136 I Magisk : Magisk v18.1(18100) logger started
02-20 18:01:56.703 129 130 I Magisk : * Running post-fs-data.d scripts
02-20 18:01:56.704 129 130 I Magisk : * Mounting /data/adb/magisk.img
02-20 18:01:56.705 143 143 E Magisk : execve /system/bin/e2fsck failed with 2: No such file or directory
02-20 18:01:56.841 129 130 I Magisk : * Running module post-fs-data scripts
02-20 18:01:56.841 129 130 I Magisk : * Loading modules
02-20 18:01:56.872 129 147 I Magisk : * Starting MagiskHide
02-20 18:01:56.872 129 147 I Magisk : hide_utils: Hiding sensitive props
02-20 18:01:56.873 129 147 I Magisk : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]
02-20 18:01:56.895 129 147 E Magisk : proc_monitor: Your kernel doesn't support mount namespace :(
02-20 18:01:57.399 129 286 I Magisk : ** late_start service mode running
02-20 18:01:57.400 129 286 I Magisk : * Running service.d scripts
02-20 18:01:57.409 129 286 I Magisk : * Running module service scripts
02-20 18:01:57.560 129 287 I Magisk : * Starting MagiskHide
02-20 18:01:57.560 129 287 I Magisk : hide_utils: Hiding sensitive props
02-20 18:01:57.561 129 287 I Magisk : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]
02-20 18:01:57.592 129 287 E Magisk : proc_monitor: Your kernel doesn't support mount namespace :(
02-20 18:03:59.521 4167 4167 W Magisk : su: request rejected (10127->0)
02-20 18:04:20.310 4194 4194 W Magisk : su: request rejected (10101->0)
02-20 18:04:52.495 4380 4380 E Magisk : write failed with 32: Broken pipe
02-20 18:05:20.441 4677 4677 W Magisk : su: request rejected (10101->0)
02-20 18:08:59.777 5210 5210 E Magisk : write failed with 32: Broken pipe
[Magisk] KaXaSA:
I downloaded both the kitkat¹ and what I assume it's the lolipop² rom ("Android L"):

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

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

The second one when I tried to 'patch boot image' (Magisk Manager) gave me a different log:

- Copying image to cache
- Device platform: x86
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.029 secs (36673379 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]
PXA_BOOT_HDR
HEADER_VER [0]
KERNEL_SZ [1464750080]
RAMDISK_SZ [1702126437]
SECOND_SZ [1679840844]
EXTRA_SZ [174351732]
RECOV_DTBO_SZ [0]
PAGESIZE [1702126437]
NAME [d
]
CMDLINE [b Version: 1.4 ...
e820 table
]
CHECKSUM [6f756e640a]
Segmentation fault
- Checking ramdisk status
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_0f88936f61def2f10d692ac0beecd3a532e9e0f5.img.gz]
- Patching ramdisk
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]
Segmentation fault
- Repacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
PXA_BOOT_HDR
HEADER_VER [0]
KERNEL_SZ [1464750080]
RAMDISK_SZ [1702126437]
SECOND_SZ [1679840844]
EXTRA_SZ [174351732]
RECOV_DTBO_SZ [0]
PAGESIZE [1702126437]
NAME [d
]
CMDLINE [b Version: 1.4 ...
e820 table
]
CHECKSUM [6f756e640a]
Segmentation fault
! Unable to repack boot image!
! Installation failed

So the first one (kitkat) failed to unpack and this one (lolipop) failed trying to repack the boot image. :confused:

Should I even try to flash the lolipop rom to see if Magisk works or based on this log it would be completely pointless?
[Magisk] demonoidmaster:
Don't know, you should forward that log to someone who knows a bit more about manual boot patching or wait and see if someone replies

But tbh it might just be those roms Asus provides, try patching a boot img from a custom rom for your device (assuming said rom is newer and still being updated), it can be any one.. Just for a test
[Magisk] Didgeridoohan:
Yes, third party apps can definitely be responsible for triggering SafetyNet. But, based on the apps you have and your description of the problem, I don't think that's the issue. Since you did pass SN initially, you're likely experiencing the intermittent failure of MagiskHide bug in Magisk v18.0 and v18.1.

In the current Canary releases (currently 18108), MagiskHide has been completely rewritten and this bug should be gone. You could either try the Canary builds (be warned, they may be buggy, make sure to have a backup) or wait for the next stable release.

If the requests are rejected, are there entries for the app(s) in the Superuser menu in the Manager (that you could toggle to enabled)? KitKat support is in its infancy, and Mediatek devices are often troublesome, so it can be used to say what the actual issue is. A logcat when a Superuser request is rejected might show something...

Based on that log you will not be able to install Magisk on the Lollipop ROM either. It looks like Magisk can't handle Asus' boot image compression (or something similar). Wouldn't be the first time Asus does weird things...

You could upload that patching image log together with the boot image to a GitHub issue (with a detailed description of the problem) for possible future compatibility. Just remember that it might not be high in the priority list.

If you're lucky, some of the recent tweaks that haven't been released yet could fix the problem, but it's far from certain.
[Magisk] blakegriplingph:
The app list on the Superuser menu doesn't show anything, unfortunately. All what I can tell so far is that whenever I try to invoke root in terminal, the terminal simply stalls without any error messages.
[Magisk] Didgeridoohan:
And, just to make sure, the option for Superuser access is set to "Apps and ADB", the Manager is installed to internal storage, and the SuperSU app is uninstalled?
[Magisk] blakegriplingph:
Yes, yes and yes.
[Magisk] Mr.A9323:
Dev please help, I'm on Havoc os, pie ( redmi 3s prime) no matter what rom I try, once I install any magisk module, safetynet breaks, please suggest any fix, I have tried many other roms available for my device but the problem persist.

:(
[Magisk] Didgeridoohan:
Logs it is then...

https://didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] Valeryan24:
Hi, thanks a lot !

So I ran "su props" in Termux, then "ro.build.version.security_patch 2018-12-05" and rebooted smartphone, security patch date well changed to 2018-12-05 and finally Safetynet ctsProfile test in Magisk was successful !

No I learned what to do in case of LineageOS update.

I still have PokemonGo and Ingress (just with root, no spoofing nor GPS app) which fail and refuse to run, but I'll post in the dedicated topic.
[Magisk] asmen5:
Using Dr.Ketan P05 with magisk 18108, my banking "BRI Mobile" still detact root?
[Magisk] Zico 10:
No one?

Device is a HTC U11, and this is extremely frustrating
[Magisk] doomscooter:
Checklist magisk hide BRI Mobile like this
[Magisk] RandomPooka:
I had zero issues using Magisk 18.1 and Manager 7.0.0 on my HTC U11 (Sprint variant) on stock Oreo for nearly 2 weeks. I've since switched to LineageOS, and still not having any problems with signal. Have you tried it on a clean install/RUU? Or by flashing the uninstaller in recovery, making sure the manager app was deleted entirely from your previous magisk setup, and then flashing 18.1 and installing the 7.0.0 manager after rebooting to system?
[Magisk] CritPlusPlus:
Magisk Hide Problems (OnePlus 6T, v 18.1)

Hi guys, loving Magisk so far. I am using Magisk Hide to hide root from a company provided app. It works when I toggle it on, but after a random amount of time (sometimes within a few hours, sometimes not until the next day), the app will detect it again. I can toggle Magisk Hide in the settings (as a whole) to get it to work again immediately. I know its not just the company app because it affects Google Pay too (these are the only two apps I use that don't want root). Any ideas on a fix for this?

Using a OnePlus 6T, stock ROM, with Magisk v 18.1.
[Magisk] akxak:
There is a whole thread on this...

Revert to Magisk 17 or wait for a hopefully working 18.2
[Magisk] habylab:
Latest Canary works, use that if you wish.
[Magisk] blakegriplingph:
I have this if it helps:

02-20 18:01:56.445 127 127 I Magisk : * Creating /sbin overlay
02-20 18:01:56.468 129 129 I Magisk : * Device API level: 19
02-20 18:01:56.468 129 129 I Magisk : Magisk v18.1(18100) daemon started
02-20 18:01:56.473 129 130 I Magisk : ** post-fs-data mode running
02-20 18:01:56.473 129 130 I Magisk : * Initializing Magisk environment
02-20 18:01:56.633 129 130 I Magisk : * Mounting mirrors
02-20 18:01:56.634 129 130 I Magisk : mount: /sbin/.magisk/mirror/system
02-20 18:01:56.635 129 130 I Magisk : link: /sbin/.magisk/mirror/vendor
02-20 18:01:56.635 129 130 I Magisk : bind_mount: /sbin/.magisk/mirror/bin
02-20 18:01:56.635 129 130 I Magisk : * Setting up internal busybox
02-20 18:01:56.672 136 136 I Magisk : Magisk v18.1(18100) logger started
02-20 18:01:56.703 129 130 I Magisk : * Running post-fs-data.d scripts
02-20 18:01:56.704 129 130 I Magisk : * Mounting /data/adb/magisk.img
02-20 18:01:56.705 143 143 E Magisk : execve /system/bin/e2fsck failed with 2: No such file or directory
02-20 18:01:56.841 129 130 I Magisk : * Running module post-fs-data scripts
02-20 18:01:56.841 129 130 I Magisk : * Loading modules
02-20 18:01:56.872 129 147 I Magisk : * Starting MagiskHide
02-20 18:01:56.872 129 147 I Magisk : hide_utils: Hiding sensitive props
02-20 18:01:56.873 129 147 I Magisk : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]
02-20 18:01:56.895 129 147 E Magisk : proc_monitor: Your kernel doesn't support mount namespace :(
02-20 18:01:57.399 129 286 I Magisk : ** late_start service mode running
02-20 18:01:57.400 129 286 I Magisk : * Running service.d scripts
02-20 18:01:57.409 129 286 I Magisk : * Running module service scripts
02-20 18:01:57.560 129 287 I Magisk : * Starting MagiskHide
02-20 18:01:57.560 129 287 I Magisk : hide_utils: Hiding sensitive props
02-20 18:01:57.561 129 287 I Magisk : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]
02-20 18:01:57.592 129 287 E Magisk : proc_monitor: Your kernel doesn't support mount namespace :(
02-20 18:03:59.521 4167 4167 W Magisk : su: request rejected (10127->0)
02-20 18:04:20.310 4194 4194 W Magisk : su: request rejected (10101->0)
02-20 18:04:52.495 4380 4380 E Magisk : write failed with 32: Broken pipe
02-20 18:05:20.441 4677 4677 W Magisk : su: request rejected (10101->0)
02-20 18:08:59.777 5210 5210 E Magisk : write failed with 32: Broken pipe

Do I need more than just the logs above?
[Magisk] demonoidmaster:
His best bet tbh would be to use a custom rom (assuming his device is still getting life in the XDA forums) and then try magisk again.. if not he'd need a new phone
[Magisk] asmen5:
Have done it (biding on magisk hide), but still detact root
[Magisk] ajejawa:
Using Magisk v18.1 work fine on my Xiaomi Mi4s with miui.am rom, SafetyNet pass without bypass, banking app not detect root & spoof location work fine with smali patcher.

Thank's to [MENTION=4470081]topjohnwu[/MENTION] & [MENTION=1620550]fOmey[/MENTION]
[Magisk] Ssnurzel:
Hm. I was never able to pass Safety check. Both points are red colored. Maybe i'm unable to find the right way to fix it...

I'm using a Samsung Note 9 with unlocked bootloader and Dr. Ketan custom Pie rom P06.

Has someone a advice?

Many thanks in advance. ?
[Magisk] Allen_Walker:
Please tell me where to register the code from common/system.prop on device?
[Magisk] Didgeridoohan:
That makes very little sense... Could you be more detailed as to what you're trying to achieve?
[Magisk] Allen_Walker:
I want to found some integrated patch in rom. I have magisk module with system.prop. but I cant found changed/add info in system/build.prop or vendor/build.prop
[Magisk] Didgeridoohan:
Are you saying that you are applying some new prop values with a module and system.prop, but you're not seeing the changes in the build.prop files? You won't...

Magisk doesn't actually change the file, but loads a new value instead of the one from build.prop. Check the new value with the getprop command in a terminal emulator.
[Magisk] kotuamoalt:
Yes. No. No.
[Magisk] OMeliante:
Mi mix 3 here. Miui global 10.0.11.0. Magisk does not get installed version 18 or 18.1. O just can install 17.3 with magisk manager 6.1.0(165). Smartphone lose root when trying to install 18.0 or 18.1 in twrp, and magisk manager says magisk is not installed... Anyone having these issues as well? Thanks
[Magisk] nowster:
Is anyone else having soft reboots (back to boot animation, skipping bootloader) with 18.1 when the system is under stress? (eg. Android Auto, Maps, Phone simultaneously active.)

I'm stuck on 17.3 due to this problem. (Nexus 5X, stock OPM7.181205.001)
[Magisk] heynando:
Even with magisk 18.1 + magisk hide, the app of my bank account (br.com.bradesco.next) is able to detect root and won't let me sign in. Yeah they're that dumb.

This didn't happen with previous versions of magisk though which was hiding root effectively, for instance 17.0 hid root consistently and 17.1 intermittently.

Any suggestions for me? I'd like to login to bank account and maintain root. This is happening on a Motorola z2 play Stock ROM Android 8.0 + unlocked bootloader

I can provide multiple logcats if necessary just let me know what I have to do to help
[Magisk] jcmm11:
Have you hidden Magisk Manager? Stop bank app and delete data+cache after doing that. For more see https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
[Magisk] Didgeridoohan:
Take a look here for possible solutions:

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

Sounds like you might have a whole bunch of unnecessary apps on your Hide list. If so, remove everything from the list that doesn't actually detect root.

https://www.didgeridoohan.com/magisk/Magisk#hn_System_instabilities
[Magisk] wilsonhlacerda:
Besides previous suggestion (the link has good info), try to downgrade to v17.3 or upgrade to newest Canary build, it has some fix / improvements to v18.1

Are you using xposed? Selinux permissive? Developer options enabled? ADB enabled? Next used to check some of those stuff......classic root detection and not SafetyNet. If running xposed, the Root Cloak module used to help.

Anyway, just quick tip: esquece o horrivel Next e vá de Inter, Sofisa, Agibank, Nubank.... e seja feliz.
[Magisk] Klusio19:
Thanks
[Magisk] gopal pipil:
Magisk 18.1 fails safetynet after few mins of reboot. I've tried it on almost all roms, after few mins safety net fails. I have to restart my phone every time to use banking apps. I'm using redmi 3s prime (land)
[Magisk] nowster:
I have:

* All 4 (TV catchup)

* Google Pay

* Halifax (banking)

* My EE (mobile phone company app)

* PayPal

* SafetyNet "Attest"

* UKTV Play (TV catchup)

only. All of the above detect root.
[Magisk] guest4711:
It sounds like the known problems MagiskHide crashes on some devices after a few minutes. After reboot it works some minutes, but then dies again. Toggling MagiskHide off and on again in settings should be enough to make in working again, no reboot needed for me.

Some people report the issue is solved on canary builds (https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337). Last unofficial build of [MENTION=7187684]ianmacd[/MENTION] fixed it for me. See https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901/
[Magisk] Ch3vr0n:
PayPal works fine for me (incl fingerprint login) WITHOUT having it enabled in magisk hide

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Magisk] Didgeridoohan:
Two main options then:

Try the current Canary build and see if there's any improvement. If there isn't see option #2.

Produce some logs that show what's going on.
[Magisk] supersemar:
[Help] i got botloop after uninstal magisk on redmi note 4 mediatek version.. i try flash boot.img original from rom but not fixed
[Magisk] nnaji_blaze:
Thanks [MENTION=3638617]iamelton[/MENTION]

So if say I was to do this;

Uninstall the Apk for phh SuperUser

Boot to recovery

Flash Magisk Uninstaller

Flash Magisk v6 again

Flash SuperUser for Magisk

Then Flash Mr. Bump

I should be golden right ?

Note: I have Systemless Xposed installed but it should still be ok when I'm done right ?
[Magisk] iamelton:
systemless xposed (latest one) is also installed in magisk image, and will be gone along with magisk uninstallation..

also, in the 2nd post of this thread its said that Systemless Xposed does not work well with Systemless SuperSU (i guess you meant this instead)..

you should read that post first..
[Magisk] naeco:
I'm running TWRP 2.8.7.0. You're probably right that twrp doesn't recognize systemless root.

I tested it with roms ported from Artmod , Resurrection Remix, m7 international stock rom. Other than m7 stock rom, the others are heavily modded. None of them passed Safetynet test though. I only install, Magisk and phh's Superuser. No xposed installed. And the stranger things is that whether I mount root or not via Magisk manager, the Safetynet test return the same result.

So I uninstalled Magisk from Artmod rom 5.0.2. No magisk, no root. Safetynet still returned 'red'. I guess the ROM is not compatible with Safety, as you noted.
[Magisk] KyeWalker:
This hasn't been officially confirmed by the developers of Systemless Xposed and Magisk, only users of the apps but look into Google's changelings of Safety Net. Currently there is no patch/workaround.

Apparently by turning off Systemless Xposed Pokémon Go wil work, don't knoww about Android payl but again I can't confirm this.
[Magisk] DerpleNerple2000:
Than I stand correctly. Surprised that worked with all the modifications they list.
[Magisk] Artim_96:
Sorry, but don't get your hopes too high. According to Chainfire, many banking apps use libshield for detection, where even he has no clue how to work it, especially because it is able to detect root under circumstances shouldn't be able to. So as long as you don't find an XPosed module that can disable it, the chances are high you won't be able to use it on a rooted phone in the near future.
[Magisk] H4X0R46:
Do the zips that work with magisk have to be specially made to support magisk? Like for instance, there's no way to use the newer beta version of SuperSU, just the magisk one in the original post? Thanks.
[Magisk] keplenk:
Actually turning off systemless xposed makes Android pay work - but I need to reboot the phone which is a pain. I don't think there is a on-the-fly way of turning on and off xposed without rebooting
[Magisk] izeeqo:
I have an LG G3 and since a long time,, everything worked perfectly,I had Magisk, phh's superuser and Xposed systemless, I managed to login on Snapchat without disabling Xposed, but suddenly, a few days ago, I can't login to Snapchat having Xposed installed and enabled, I tried several times to remove all (magisk, and superuser Xposed) and reinstalling, but I still can not connect. Now I have phh superuser and magisk installed and Xposed but i have disabled xposed. And now i want to install xposed v86.2 to test if it will work. But when i flash it via recovery TWRP 2.8.7.0, i have the the following error message : ! Failed: Unable to extract zip file!. What is the problem ? What can i do please ? Thanks
[Magisk] rollerce:
I figured it out, and holy crap was that a pain in the ass. superSU puts a thing in the FIRMWARE to reinstall itself every time you reboot the phone. it's literally in /supersu. Not /system/supersu or any of that, its in the actual root directory. I only found that by accident.
[Magisk] KyeWalker:
That's not my case on CM
[Magisk] cocchiararo:
Thx for the links (will be useful in the future).

Since root was lost and could not recover it after the reboot, and I needed to modify system anyways, I removed magisk and went with SuperSU again.

Will come back when my tests finish.
[Magisk] JudgeDread11:
Yes they have to be magisk specific. The first few posts PDF this thread explains the modules and with the module template you can make your own.