yashsingh1/xdaforums huggingface dataset:
[Magisk] chostarman:
CtsProfile Error

So I have a Samsung Note 4 with a Note 7 port rom, but the safetynet check returns with a false ctsprofile but a true for basic integrity. Is there a fix for this? I have installed the module for safetynet but it doesn't work
[Magisk] josdehaes:
Hi, I've been using magisk for quite some time, but now on my P20 pro, I tried to get Google Pay to work. As I run a treble ROM, I flashed the huawei stock camera, but that changes the system partition, so pay refused to add my card. I tried to make the huawei camera into a magisk module (using the template from github), which seems to have worked (camera is still available and works fine, although now systemlessly) but now cts profile checks seem to hang. All sensitive apps (my banking apps, and google pay, and also the cts check in magisk manager) hang. The apps don't start.

Anyone has a clue?
[Magisk] TheFixItMan:
Try module in link below

Once installed & restarted

Open terminal emulator (playstore app)

Type

su

props

Select option 1 for selecting a fingerprint

Choose a fingerprint that's related to your device

Restart

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Magisk] maybeme2:
Where can I download the 16 version before the 17.1 update? I would like to revert to it.

If I find it and download it do I just flash it in twrp to revert to it?

Thanks
[Magisk] TheFixItMan:
All versions are available on the github website

https://github.com/topjohnwu/Magisk/releases

Flash the Uninstaller first if downgrading
[Magisk] Tacio:
I have a constant FC while tapping to start SafetyNet check in Magisk Manager 17.1.
[Magisk] Himpaji:
Bug in Magisk 17.1

After updating to Magisk 17.1, when I install a new module or update an existing module, it installs successfully but after rebooting all the apps changes to default system apps, and default setting. Again i reboot, then everything comes back except that xposed framework gets deactivated along with all its modules(like gravity box etc.) then i again reboot to activate it, then again reboot to activate its modules. Thus the complete process involves 4-5 reboots to function everything back to normal. This didn't happened before. I'm using Lenovo K8 note, Android O(8.0). Any solution?
[Magisk] ReZzA_No.1:
I figured out that if magisk.img size goes over 96 (in my case it gets resized from 96mb to 160mb after installing specific amount of mods) none of modules won't work.

But the thing is it's not a matter of space because i've got 2gb free internal storage and 900mb system, and all those mods do not make 150mb overall.
[Magisk] chostarman:
wow, it worked! thanks dude!
[Magisk] wolftou:
Hi, the main release thread states 17.1 supports Note 9. I have the SM-N960U1 running N960U1UEU1ARH2. I extracted the boot.img from here https://xdaforums.com/galaxy-note-9/how-to/stock-sm-n960u1-usa-unlocked-firmware-t3833566 and followed the installation instructions from the release thread. When I try to flash the the patched boot.img using the included patched Odin from the link, I get "FAIL! (Auth)."

Does Magisk support SM-N960U1?

Thank you for your help.
[Magisk] Aid777:
You know what? a funny thing happened with my SD card, I flashed 17.1 Magisk and got into a boot loop and in the end I just flashed Fumics again and restored some back ups and so on. However there are a couple of folders on my external sd card that disappeared and with them all the files inside. Most of the foldes on the sd card are okay but about two are gone! Might not have anything to do with Magisk and the re-flashing of the rom but sure is strange.
[Magisk] yochananmarqos:
Clear the app cache & data for Magisk Manager.
[Magisk] Tacio:
I that case I lose all installed NanoDroid modules?
[Magisk] datecruz:
Request superuser permission

Hello, I have a jiayu s3 (ROM madOS 7.1.2) with magisk 17.1. When I want to perform a root action, the small window does not appear to accept or deny the permission. Nothing appears to me. When I do a test "root check" it remains about 10 seconds processing and finally it appeared "without root permissions". There must be a problem because if I uninstall magisk, the "root check" test is instantaneous
[Magisk] skyknife93:
Is the Google pay/ Tez issue resolved now?
[Magisk] jcmm11:
No
[Magisk] Tacio:
Thx, it works now!
[Magisk] jauhari:
How to pass Safety?
[Magisk] gothicVI:
Has been answered thousand times already! Search!

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[Magisk] FullWipe:
Clean flash has solved my problem but now safetynet fails to pass --> "The answer is not valid".

I will look for a solution.
[Magisk] Soumy1234:
I forgot to change script settings in props tool. SN is back!
[Magisk] daniu:
Hi

I wonder if ever someone reported a bug on Asus Zenfone (zoot - not sure about zoom) which causes the device to reboot upon shutdown and (at least) not reboot upon reboot? (Not sure if it just lack of patience but the display stays black for quite long when trying to reboot)

It is reproduceable that this behaviour exists with the later magisk versions (tested 16.7 and 17.1) while with v16 everything is OK.

Are there device specific threads? If so - sorry - please tell me where

Regards
[Magisk] superedit86:
issue: magisk hide = reinstalling magisk with random package name fails

hello. i hope to find a solution to my problem. apparently this is not so common.

I have the pokemon go lockout issue, therefore I tried several times to use the function to reinstall magisk with a random package name.

with magisk 16, 16.7 and 17.1 i get the error that it was not possible to perform the operation

phone: jiayu s3, android 7.1 madOS

can someone help me?

I also did a clean install of magisk and also a new rom flashing. no improvement

open to ideas

thanks
[Magisk] DonQuixote77:
is anyone having issues installing 17. 1 on the September patch on a pixel? I tried to flash it three times in twrp and I am not being successful. Flashing procedure shows as successful but when I boot up the manager app doesn't show up and there is no root access
[Magisk] yochananmarqos:
No issues here. My monthly procedure is as follows:

- Flash original boot.img via fastboot

- Sideload OTA via stock recovery

- Boot TWRP, install TWRP & reboot recovery

- Flash Magisk & ElementalX kernel
[Magisk] socali:
I'm having trouble with Essential PH-1 and the September update. Phone boots fine with the original boot image, but fails to boot (gets stuck in fastboot screen) with v17.1 patched boot. Magisk v17.1 was working fine before the September update.

Anyone else facing same issue? Anyone has an idea how to resolve it?
[Magisk] abaddon37:
I'm having issues patching the boot.img with 17.1 through the Magisk app. The boot.img is from the Verizon Sept. patch for Pixel XL (marlin). Attached is log
[Magisk] Badger50:
Did you fastboot the patched boot.img? :confused:
[Magisk] RandomPooka:
I haven't updated to the September patch yet, but have you tried flashing 16.0 and then updating it to 17.1 from the Magisk Manager app?
[Magisk] DonQuixote77:
I fastbooted the full factory image. Wiped clean, booted into and installed TWRP, booted up and set up. Booted back into recovery, flashed Magisk, but no joy.

First time with this issue. Tried again and no dice.

---------- Post added at 02:35 AM ---------- Previous post was at 02:10 AM ----------

Seems that Magisk 16.7 is working fine. Curious why 17.1 didn't seem to want to work... Very odd
[Magisk] vandyman:
Just a note to all;

Use the Magisk uninstaller before applying the updated security patch.

It will help installing Magisk easier when the ota is installed. No boot loops.
[Magisk] socali:
I finally got Essential PH-1 with the September update and Magisk v17.1 to boot up!

After multiple trial and error cycles, I think what did the trick was uninstalling magisk manager, then I fastboot flash the magisk patched boot and then phone booted up.

I then installed magisk manager, and just to make sure, I did "Complete Uninstall", booted up with original image and then flashed magisk patched boot again.

Things look fine now. Magisk release notes mention bootloops on update from v16 to v17, but since I already upgraded from v16.7 to v17.1 before the September update, I didn't think it's relevant. I guess it is.
[Magisk] bohemist:
Do you mean flashing Magisk installer via TWRP?
[Magisk] socali:
Yes, "Restore Images" worked fine for me in prior updates, but not this time. Had to uninstall magisk manager as well.
[Magisk] vandyman:
Yes..
[Magisk] socali:
I don't use TWRP, so here's what worked for me:

1) Magisk manager - Create a patched boot image for the September boot

2) Magisk manager - do Uninstall -> Complete uninstall.

3) Install September OTA update (including a full boot after update)

4) Fastboot flash the patched boot

5) Install manager again
[Magisk] mobileman88:
Should I be concerned with this error in logcat?

.695697] EXT4-fs: 30 callbacks suppressed

[ 214.695706] EXT4-fs (loop64): errors=remount-ro for active namespaces on umount 2

[ 214.695776] EXT4-fs (loop64): errors=remount-ro for active namespaces on umount 2
[Magisk] xunholyx:
You have to patch the boot.img with Magisk Manager, transfer it back to your PC, and flash it in fastboot.
[Magisk] abaddon37:
I'm sorry, this log is from trying to patch the boot.img

---------- Post added at 06:21 AM ---------- Previous post was at 06:14 AM ----------

I just tried patching the original boot.img now, and it worked ?*♂️
[Magisk] Turbopuschel:
Did someone find a solution to the Payback app (https://play.google.com/store/apps/details?id=de.payback.client.android&hl=en_US) not working because of "unsafe device", even with Magisk Hide applied to it and Magisk Manager hidden? Still worked for me with Magisk 16 but not anymore with Magisk 17.1.
[Magisk] hfam:
For those of us who run a stock Google image and Magisk to root, and do NOT use TWRP, wanted to share the order of my steps as I had a successful update of Magisk and Sept update.

I used 17.1 when i updated from 8 to Pie 9 release. Installed Pie using Nathanchance tutorial and the full system image (edit flash-all so no user overwrite), and then updated to what was beta 17.1 Magisk. It worked but it was flaky and frequentl boot loops, made me queasy to reboot so I waited until Sept image before I messed with updating MM.

Before updating to Sept, I allowed the MM update to current but did not let it do anything else.

- Pushed Sept update using full system image no user overwrite

- Pushed boot.img to /sdcard/Download

- Opened MM and then chose to update to 17.1, patched boot.img in Download

- Pulled patched_boot.img to adb machine

- Flashed patched_boot.img to Pixel 2

- it's flawless.

The sketchy boots and bootloops are gone. MM recalled all root apps.

TL/DR Using Nathanchance tutorial to update to Sept and to update to latest MM, I enjoyed success by updating to latest MM, then Sept update, then from MM update to 17.1 stable, patching boot.img, and then flash patched_boot.img. Just remember the patched_boot is in Download, not the MagiskManager dir.

Thanks to topjohnwu and his crew, nathanchance, and all you kind folks who are in here day in and day out offering help selflessly, you know who you are.
[Magisk] DiamondJohn:
FYI: Script issue fixed/averted

OK, I worked it out, and got it working as a boot script. I must of tried at least 50 iterations:eek:, slowly adding in a few lines to see at which one it failed on. The thing that made it extra confusing is that the script ran perfectly when manually called from a shell, but failed when used in service.d :mad:

Anyway, it came down to changing the following line

vSCRIPTS=$($bb ls "$vSCRIPT_PATH/") &> $sLOG;

to

vSCRIPTS=$( $bb ls "$vSCRIPT_PATH/" );

where bb=busybox and sLOG is my logfile location and name. The script has been running for a few years now, and I think the logging on the line was to redirect errors, which was OK previously and from a shell, but somehow caused the script to not compile in service.d and hence hard to see which line it failed on. NB: two changes, the space after & before () and the redirect of errors to log file.

So the moral of this story is that service.d processes a script differently to manually running it in a shell?:confused:
[Magisk] Didgeridoohan:
Nice you got it working. I'm nowhere near knowledgeable enough about scripting to give any kind of comment on the whats or whys...

[MENTION=4544860]osm0sis[/MENTION] Could you maybe provide a little insight?
[Magisk] francyesco:
https://xdaforums.com/showthread.php?p=77405862

It's a magisk fault or twrp?
[Magisk] osm0sis:
The spacing shouldn't matter, but I know &| so probably also &> is a (m)ksh-specific feature. Maybe Magisk's post-fs-data.d/service.d is run in busybox's ash shell instead, which does not support these conventions.
[Magisk] Dims_Camper:
App still can detect root D:

Seems like This app is still can detect root even after checked at magisk hide. Hiding magisk manager via settings (those randomized package name things) does fix the issue tho, but maybe you can look after this issue so it doesn't require workaround to run. Thanks!

ps. this issue is just like that pokemongo thing right? it scans the package name contains magisk..
[Magisk] DiamondJohn:
Do you by any chance know if it could of changed between v16.0 and 17.1? as the script was working previously in 16.0. From what I understand, the &> is also available in most bash shells ie not just ksh.

Regardless of the fact it ran ok before (and within shell now) the line actually looks incorrect to me now, as the &> re-directs stdout and stderr to the named destination (ie not just stderr), but i would of expected stdout to be going into the variable. The script was first written many years ago.
[Magisk] :
Do you use hash-bang to define the interpreter to be used for the script?

I have three guesses to offer:

sepolicy denies writing to the logfile - should be as avc: in the logcat. This is avoided on the interactive shell because of roots namespace and sepolicy context.

the script is executed in different shells (i.e. /system/bin/sh for service.d; /system/xbin/bash for interactive)

the shell has differnt behavior (aka different environment) for service.d and interactive use

---------- Post added at 11:28 ---------- Previous post was at 11:17 ----------

Good point.

Posix shell standard would require

command >/path/to/logfile 2>&1

I would also recommend to redirect the output of the command in the subshell and not the output of the subshell, because if the subshell is crashing all output but the crash itself will not make it to the log file. But this is only my paranoia...;)
[Magisk] master64nl:
I can not find the boot.image. In which map is it located?
[Magisk] DiamondJohn:
First line is

[COLOR="Green"]#!/system/bin/sh[/COLOR]

I build my own unofficial ROM(s) from source, so I am often monitoring it for SELinux failures, and I have not seen any that i could relate to my boot script. Also, the amount of logging I do is pretty full-on, so it would of failed on nearly every line, not just this one.

As provided above, when I run it from a shell, I run it using "sh".

After spending so much time trying to work out why it was failing, I have accepted that this one line, does not get the error logged.;) its pretty safe with it simply being an "ls" against a directory that I checked the existence of previously, and logged if it does not exist. I assume permissions are ok if I have created it.
[Magisk] thevalos:
Hi y'all,

a few days ago I updated Magisk to the latest version at that time (v17.0, if I recall correctly), and when I tried to open Magisk, it stuck on the loading screen of Magisk... forever. Anyway, lurking through some posts here, I saw there was a positive flux of posts acknowledging that latest update caused bootlops. Fine, I didn't touch anything and kept using my device.

Tonight, I opened Magisk once again, and I saw the Magisk is gone! Updated the Magisk Manager to v17.1 , and now it prompts me to download Magisk as a zip or img format.

"Alright then, time to re-install Magisk", I thought. However, when I went to TWRP (after downloading Magisk into sdcard/Downloads), the 'Data' partition is not mounted and TWRP is showing 0Mb on the internal storage.

Does this mean that device is encrypted and device is unrooted? Do I have to go from the first step to re-install Magisk, from wipe data and so? What really happened to Magisk?

Thanks.
[Magisk] Galaxy Y User:
Can anyone test to see if the lastest version got detected by Fate/Grand Order. My phone got a full update and lost Magisk, though the Magisk Manager is still presented in the system, and not get detected by Fate/Grand Order, though the previous version was detected. I will try to flash magisk again once I know that it is not detected by FGO
[Magisk] kryshnakishore:
Uninstall magisk through magisk uninstaller, flash boot image , flash magisk zip , done
[Magisk] Killua96:
It's still detected, after all nothing has been done to prevent it for now and afaik John is waiting for a new MacBook to start developing again...

For now there are two solutions:

1) Keep the phone unrooted

2) Root, hide FGO and Magisk, freeze FGO with titanium backup and do the time trick (it should still works on 1.20.1)
[Magisk] jenslody:
Did you already reboot after updating the manager ?

This might bring Magisk back.

Besides this, if /data is encrypted (and it looks like this) and TWRP can not decrypt it, you can flash the stock boot-image with MagiskManager and flash it through TWRP.

If you can not get a stock boot-image from your device, Just make a backup of your boot-image in TWRP, restart into your OS and use the boot-image backup for patching (on my device it's called boot.emmc.win), it's just a simple boot.img with other name.

After patching copy the "patched_boot.img" from your downloads-folder to the external sd and flash it through TWRP.
[Magisk] beardymarrow:
Hiding magisk manager is not a work around, it's the proper solution.
[Magisk] paarnoutse:
In case you have a OnePlus device and your device is encrypted, it's a known problem that the latest official TWRP versions (3.2.2.0 and 3.2.3.0) aren't able to decrypt your data, and therefore show your data partition as 0MB.

In that case, either install the official TWRP 3.2.1.1 for your specific device, or install the codeworkx TWRP 3.2.3 version (search 'codeworkx TWRP' on XDA).
[Magisk] thevalos:
Yes, I rebooted it several times. Magisk is not getting back.

TWRP is not asking for any password to decrypt it. I don't know why this happens, though. I've set a 1234 PIN to see if TWRP asks for password to decrypt /data, but it doesn't.

So I should go to TWRP, make backup of boot image, then use Magisk's feature of Patch Boot Image, locate file I saved with TWRP, then use TWRP again with an external SD card to flash it?

---------- Post added at 03:25 PM ---------- Previous post was at 03:24 PM ----------

I have a SM-G935F, Oreo.
[Magisk] andresurbakti21:
Im still bootloop after flashing magisk v17.1.

Plz help.
[Magisk] MC_Ohr:
I'm using the previous version of payback app and disabled auto update in play store. Version is 5.18.10090 I found it via Google.

Gesendet von meinem HTC U11 life mit Tapatalk
[Magisk] Badger50:
Device? Stock or custom rom? Oreo or Pie?
[Magisk] jimger:
Does anyone have the problem that Magisk doesn't show a systemfied app installed? I tried to install latest youtube vanced to magisk 17.1 and it always seems as not installed. I can see the apk in the sbin folder though.. Does anyone else has that problem? I am on miui 9 device (mido)
[Magisk] andresurbakti21:
Xiaomi Redmi Note 5a Ugglite, im using cusrom. ViperOs. 7.1.2 Sorry for my bad english
[Magisk] Badger50:
No biggie about the English my friend. Now someone with your device can help you out. Unfortunately, it's not me. However, someone will likely help out. That's why when you post a problem, the more info you provide, the more likely you are to get a solution :good:
[Magisk] ameshiya:
Hii, i dont know if some ond else is facing the same bugs im facing

Every time i tried to hide any app on magisk hide my phone reboots and i cant pass the screen lock ..once i entred the pin the ui restarting and ask me to enter it agan

The only solution for this is to completly uninstal magisk and install it again
[Magisk] HemanthJabalpuri:
Hi... it is not a big thing ... but i think Magisk-v17.1 is not signed correctly since it does not verified successfully when zip signature verification is enabled...
[Magisk] bafforosso:
Question about specific apps should be searched for and asked in the app's topic, in your case here : https://xdaforums.com/android/apps-games/app-youtube-vanced-edition-t3758757

Did you Uninstall original YouTube updates ? If not : go to the YouTube page on the Play Store, click Uninstall and accept, then click the three dots on the top-right and unselect "Enable auto-update", if YouTube Vanced was installed without error it should be enough to have the original YouTube replaced by the Vanced version in your launcher.
[Magisk] jimger:
Thanks, I asked here because youtube vanced installation doesn't give an error, and youtube is not installed at all. I can see through titanium backup it is uninstalled. But I can see in sbin folder that youtube vanced is installed as it should. So it seems like a problem with magisk to bind that "system" app to the installed apps. Official youtube app is uninstalled. Also had youtube vanced working correctly with magisk 16.x (and before). Most probably if it does that for youtube vanced will do it with other systemized apps too. Can't confirm though cause at the moment it is the only I have installed. Other modules like unified hosts adblock work correctly
[Magisk] bafforosso:
Alright, seems you thought that through, please accept my apologies, I'm may be a bit too used to people thinking that the time of other is less valuable than theirs.

So it does not seem to be the issue I thought and it seems to be out of my expertise, but you may want to post the install log from Magisk and some information about your device (brand, model, Android version, custom rom,...) for others more knowledgeable than me to be able to help.

On my side I've updated my Google Pixel to stock Android 9.0 rooted with Magisk 17.1 (clean install) a few days ago and YouTube Vanced module from Magisk repo works perfectly.

Hope you eventually manage to solve your issue.
[Magisk] jimger:
Thanks... I have got a miui 9.5 version so unfortunately far from stock :P. Let's see if someone has the same problem as me. I have the problem both with root installer and from magisk repo
[Magisk] :
I'd suggest being more careful with such generalizations in public! Imagine people belive this - a new hoax is born. Screenshots are taken from op3t with twrp-3.2.3-0 with f2fs encrypted. It also works with ext4 encrypted.

EDIT:

Tried to upload the second pic three times, but it is still broken.

https://drive.google.com/open?id=15TVkhYnmG7L1OwwJ4of3p2hlj-lk2njw

https://drive.google.com/open?id=1A2vSn3KtUC99l0ctbSpML7oJeO7KklMS
[Magisk] TiZiO.Cover:
The App Paydirekt is being detected, I don't know since when since I only just installed it myself.

The error message is "Potentially Unsafe Device".

https://www.google.de/url?sa=t&sour...BMAB6BAgKEAI&usg=AOvVaw3U_ugR9YQhZY2H7X-KGnxo
[Magisk] mupet747:
After update to 17.1 my Samsung note 8 screen were stuck after the screen standby...i had to keep restarting my phone to get it work but after the screen time out again..it get stuck again

PS: only the screen touch were not working, i can receive calls or text but cant answered it
[Magisk] bafforosso:
You probably did, but let's start at the beginning nevertheless. Have you tried :

- checking the app in Magisk Hide list?

- "Hide Magisk Manager" in Settings? (while still keeping the app checked in Magisk Hide list)
[Magisk] Aid777:
This happened to me when I flashed from TWRP. I just reflashed my ROM, but I heard you should uninstall Magisk using the most new uninstaller. Reboot and you won;t have root then go back into TWRP and flash again. Not sure if you need to install the APK first though. I assume you have TWRP and you know how to boot into recovery. I guess it cannot make it any worse.