yashsingh1/xdaforums huggingface dataset:
[Magisk] PoochyX:
I mean that's how that app is programmed you mount read write and then mount it read only when you finish...

([emoji3590]09-09-18[emoji3590])
[Magisk] zgfg:
When posting such questions you need to be very specific, which phone, firmware, updating to which version and so - it's not a common problem happening to everybody (to the contrary), and therefore, potential solution would also depend on your phone, firmware, etc
[Magisk] XtraWater:
Phone: Xiaomi Mi A1. Resurrection Remix 6.2 (Oreo 8.1). Tried to update from Magisk 19.3 to 20.0. Always used stable channel. I made backup with TWRP just before the update. So it was easy to restore everything as it was.
[Magisk] Gitah.:
Thanks, I just did it and everything worked fine.
[Magisk] saoudien07:
Can you please tell me how to patch boot.img with Magisk?? It is not the same as installing Magisk through TWRP??
[Magisk] Gitah.:
Follow the steps I've linked in my post.

You need to put the boot.img on your device, install the magisk .apk, from the app select and patch the boot.img which will create a patched copy of it, move that on your pc and then fastboot flash the patched .img and that's it.
[Magisk] bunklung:
I tried a full uninstall with adb back to factory apk and it took, but the Play Store is just stuck at "installing".

Any other tips?

*update* I performed the above, but did a restart and a new update was available. It took the update from the store and no issues. I restored data with TB and all is well. The crazy thing is that my other Pixel 3 had the same problem, but when I just check after performing the "fix", the other Pixel 3 had a new Chrome update. So I think Google did something.

adb uninstall com.android.chrome is what I used to return to the factory APK.
[Magisk] ktmom:
If I understand your question, you're asking if you should just use the TWRP backup you have and revert back to your last working state. If that's the question, then that should be fine. Or just the backed up boot (or recovery) img depending on where Magisk is installed on your device.

If you take the time to try flashing/patching again, grabbing log(s) would help a big report that may help identify the problem. Asking for help/reporting bugs
[Magisk] guest4711:
On some devices magisk's internal busybox will not be installed (the right way) so installer uses the standard unzip command which does not support -j option (ignore path).

For me it's working if I

1. delete the folder /sbin/.magisk/busybox

2. reboot

3. install module

The problem with busybox will reoccurre again after next reboot but you'll notice if installing another module or version only. Uninstalling Magisk and reinstalling it will also help (cause the contents of this folder will be purged this way, too).
[Magisk] BillGoss:
I'm also on Magisk 20 and using Solid Explorer. My system is mounted ro

u0_a107:~ $ mount | grep /system | head -1
/dev/block/platform/soc/624000.ufshc/by-name/system on /system type ext4 (ro,seclabel,relatime,discard,data=ordered)

I have no problems editing build.prop or other files in /system.

I'm on Los 16 (Android 9).
[Magisk] guest4711:
Did you try to edit the mirror, e.g. /sbin/.magisk/mirror/system/build.prop ?
[Magisk] chrcol:
thanks for the reply, you deserve to know what the cause was.

The phone was unable to write at all to internal storage, so was nothing to do with magisk in the end, but the magisk error message was obviously incredibly misleading.

I eventually figured out what was going on when android told me it was unable to save a screenshot due to lack of space (when I had over 100 gig free).

TWRP made a massive mess when I changed /data to f2fs, there was no /data/media/0 and other issues, after I msm'd the phone all is good again. magisk 19.4 working well :)

---------- Post added at 06:51 ---------- Previous post was at 06:48 ----------

found another way also (on oos)

gboard was stuck as my keyboard, and is installed as system app, it turns out in the battery sub settings for system apps the disable button is "not" greyed out and works to disable. No root or adb needed for that method.

---------- Post added at 06:53 ---------- Previous post was at 06:51 ----------

found another way also (on oos)

gboard was stuck as my keyboard, and is installed as system app, it turns out in the battery sub settings for system apps the disable button is "not" greyed out and works to disable. No root or adb needed for that method.
[Magisk] katrazi:
Note 9

Can I use it to just root my Note ( Verizon)?
[Magisk] chrcol:
found another way also (on oos)

gboard was stuck as my keyboard, and is installed as system app, it turns out in the battery sub settings for system apps the disable button is "not" greyed out and works to disable. No root or adb needed for that method.
[Magisk] zgfg:
When copy/pasting word by word, you can at least provide a link to the source - was https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post80288347
[Magisk] pawelik001:
no, I haven't tried

I have system_root in /sbin/.magisk/mirror and it works
[Magisk] oz42:
Device: Moto X4 XT1900-7

OS: LOS 16.0

Magisk 20.0 works great. But when I update to 20.1, I am getting a boot loop. Any ideas?
[Magisk] kurtn:
Make sure to set update channel to stable. Thatcher a bug in 20.0 to have by default canary.
[Magisk] oz42:
Thanks!
[Magisk] vodkinagdan:
Hello! Does anyone suffer from the 'Magisk is not installed' problem? Try the following:

su

taskset -p 1 `pgrep magiskd`

Should look like this

View attachment 4844119

This will assign the magisk daemon to the first processor core. As I noticed, crashes occur on those kernels where were attempts to optimize energy consumption. And perhaps, processor core management is badly implemented. Because the first core of the Little cluster is always active ... it seems that this at least allows you to delay the crash moment, but I'm still not sure.
[Magisk] XtraWater:
Hello

I followed your instructions and created the file in /data/adb/post-fs-data.d

Then, I installed Magisk 20 (stable channel). Magisk Manager first updated itself and then the Magisk framework. Then the phone tried to reboot. This time it was different. The phone didn't boot into fastboot mode but it showed the boot animation from Resurrection Remix. I waited about 10 Minutes. It stuck there.....

Now, I wanted to attach the log file. But it's too big. It exceed the max file size. Over 5MB. So, not sure what to do now.
[Magisk] _litz:
v20 appears to have a bug ...

It's installed (with Manager 7.3.5) and it runs fine.

but it keeps alerting that there's a new version and offering to reinstall itself.
[Magisk] Wolfcity:
Upload the logfile to a hoster (drive,Dropbox) or paste it on pastebin and post the link here.
[Magisk] palmbeach05:
Upload file to gdrive or something like that, then provide the link here
[Magisk] zisix:
HTC U12+

Installed v20 from the stable channel, now I'm stuck with boot loop. Would anyone have something specific to point me to for a fix? Thanks!
[Magisk] jcmm11:
You can post a link as has been suggested or you can just zip the file and post the zip
[Magisk] jamesfitzes:
any Magisk updates being developed so TWRP recovery can stick? Or is there any way I can make TWRP remain installed ? Issues started after I updated to V20. I'm running Android pie on OP 7 PRO
[Magisk] zgfg:
If so, it should IMO be a problem with Magisk Manager

You can try by deleting Cache or even Data in Settings/Apps/Magisk Manager
[Magisk] smarty8:
Samsung A7(2017) SM-A720F.

[IMG=""]http://fgh130.narod.ru/PICTURES/2019/Untitled_1_2_2.png[/IMG]

I got screen_on delay ~7 sec. after PIN inserting when I updated Magisk to 20.0 and Manager to 7.3.5 (Stable channel). Before the update, the screen turned on instantly. This is undoubtedly related to updating Magisk and Manager since before that I did not install and did not update anything.

What can I do in this situation?
[Magisk] XtraWater:
[MENTION=6617276]ktmom[/MENTION]

Ok, here's the log. I just realized the log contains also older data. I thought I cleared the log file.

The log from today, after Magisk 20 got installed and phone booted starts from this line:

10-14 13:38:48.540 865 865 E Diag_Lib: qpLogDiagInit <== result : 1

https://drive.google.com/file/d/13X2XG__LmSrVbTvQ4KYBiGN3fJcdQVEG/view

As I mentioned before, this time the phone didn't end up in fastboot mode. It started the boot animation but seemed not able to continue from there. Then I entered recovery mode manually by holding power and volume up button.

Thank you.
[Magisk] redplate:
Do you have TWRP? You could try to disable Magisk (AFAIK there is a zip for it on github) or flash another version. 19.3 is very best for me.

If nothing works flash ap + home csc... So you won't lose your data.. If I'm wrong correct me

Edit:

Magisk uninstaller

https://github.com/topjohnwu/Magisk/releases
[Magisk] pacman photog:
Magisk won't update it says target failed. Pixel 3xl. Atm no adb.
[Magisk] zisix:
I have TWRP, but I can't get in to it. The phone is unresponsive to adb/fastboot and the hardware button combination doesn't seem to work.. Likely because I can't get the phone to power off. It just cycles betwee the "bootloader unlocked" screen to the "HTC powered by Android" screen.

Thanks.

Edit:

Was finally able to get it to respond by connecting it to a power source. This caused the battery percentage/charging screen to interrupt the loop. From there I got in to TWRP and am working on the Magisk uninstall. Thanks again!

Edit2: Well, nevermind. Uninstall didn't work and now I'm trying to get back in to TWRP again.
[Magisk] nerosc:
I have to toggle Magisk Hide off and on after every reboot then it works fine with all my banking app until next reboot.

After a rebbot the app RootBeer show "Rooted". Toggle Magisk Hide off and on and RootBeer show "Not Rooted".

Using the latest versions. Is there a fix for this problem? Thanks
[Magisk] Dreamer(3MF):
Download The Module Of MultiFunctions From This Thread https://xdaforums.com/apps/magisk/module-multifunctions-bootloop-t3933386 For Getting The Ability To Use The Sub-Function Of Hide Enabler Under The Main Function Of MagiskHideList Cleaner.

>>>Read The Description & Instructions Carefully Before Use<<<
[Magisk] YoshiFan501:
Safetynet broken for anyone else in 20.0?

even from a complete magisk uninstall and reinstall. core only mode. magisk hide on. everything

both cts and basic fail
[Magisk] IronTechmonkey:
The need (or lack thereof) for "su -c" in shell commands

I use some shell commands, typically through Tasker, to perform tap and swipe input events. In LOS 14.1. In LOS' native SU they look like this: "su -c input tap [coordinates]".

When I switched to Magisk 19 for a Moto X4 running LOS 15.1 I had to remove "su -c" to get those commands working (and to prevent the device from crashing and rebooting) but they worked fine.

Shortly after updating to Magisk from 19 to 20 (using Magisk manager 7.3.5 throughout) the commands with or without "su -c" fail and cause reboot. I've not had time to do proper logging and testing but can anyone say if this might be a known effect of updating from19 to 20?

[EDIT] Welllllll, both command variations, with and without "su -c", work fine (as I somewhat suspected they should) but something coincidental in timing to the past installation of Magisk 19 and again to the upate from Magisk 19 to 20 added spaces into the Tasker shell commands. Very wield but not likely to be a Magisk issue. In fact it is Magisk that saves this device from being a paperweight. Issue possibly related to A-B madness and events which occur in TWRP.
[Magisk] Artim_96:
Not here. But there are two modules in the download section that can hide Magisk from more methods. Try them out and report back.

And maybe deleting app data of Play services might already help
[Magisk] Wolfcity:
Or use the easy way: Put a file with the ending .sh (name doesn't matter) and the content

#!/system/bin/sh
sleep 120
/sbin/magiskhide --disable
sleep 1
/sbin/magiskhide --enable

into data /adb/service.d with the permission 755

(rwxr-xr-x).

After every reboot magisk hide should be enabled.
[Magisk] Danblotter:
Hello everyone. I own a Redmi Note 7 Pro, or the Violet device as its also called. I kept it in full stock condition (stock recovery, stock chinese rom and locked bootloader). I decided to keep things like this for a time, but now I feel the need to root my device to get access to the GPS configuration file and to get some better battery life features.

But still, I want to keep the smartphone as stock as possible. So I found the linked solution. I think it might work, but as some of you should know, the most recent Xiaomi devices comes with a restriction. The bootloader must be always unlocked if you want to use any room other than the officialy destinated for that device. If you relock the bootloader after the instalation, your phone will brick. But I WANT to keep the bootloader locked.

My question is, if I apply the indicated solution with the locked bootloader, will my phone brick? I mean, it might detect that the boot.img has been manipulated and prevent my phone to boot?

Any information would be apreciated.

Regards.

Thank you!

How to Root any Xiaomi Phone without a Custom Recovery! https://c.mi.com/thread-1444861-1-0.html
[Magisk] jcmm11:
Simple piece of advice. NEVER attempt to lock the bootloader on a phone which isn't 100% stock.

You basically have a choice. If you want any type of system mod (custom kernel, root, custom ROM, custom recovery) you leave the bootloader unlocked. If you want the bootloader locked you don't modify the phone.
[Magisk] Danblotter:
Thanks mate. You saved me from screwing my phone.
[Magisk] chrcol:
Dont know if you got an issue in app/browser, but the source was correctly quoted, and the post even has a link in it to link to that source.
[Magisk] martyfender:
Try zipping it and see if you can attach it.

---------- Post added at 09:11 PM ---------- Previous post was at 09:08 PM ----------

If I am not mistaken, [MENTION=4470081]topjohnwu[/MENTION] did push a new silent update to MM.

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

---------- Post added at 09:33 PM ---------- Previous post was at 09:11 PM ----------

The best one, in my opinion, by far, is MagiskHide Props Config Module.

---------- Post added at 09:52 PM ---------- Previous post was at 09:33 PM ----------

I have not read that link, but the conventional wisdom is that there is a risk of bricking a device if you try to root it without unlocking the bootloader.

My, brand new Onn 8 Android 9 tablet has a temp root solution, mtk-su, which I used, however, without the bootloader unlocked, which allowed me to backup the stock boot.img then patch it in Magisk Manager. Next I unlocked my bootloader. Finally, I then fastboot flashed that image to gain full, Magisk root.
[Magisk] YoshiFan501:
I had to go back to Magisk 19.3 to get my safetynet back.

Should i stay there? I have a pixel 2 xl on the latest patch
[Magisk] mrbonine:
I started having what appears to be the low audio volume problem right after installing updates Bixby Button Remapper, BusyBox for NDK, and lib_secure storage companion. Is there any chance this was caused by these Magix extensions? SM-960F 8.0.0/9.0 root, BRH8/BRI1.
[Magisk] JudgeDread11:
Easy to find out, disable the modules and restart, of the problem is still there then it wasn't caused by the modules.
[Magisk] AndroTech:
Magisk Hide Option is not showing all the apps

Hi,

I am having an wired issue. Post Magisk 18.1 the MagiskHide option is not showing the app list for me. I tried all the updates post 18.1 including v20.0

In the Magisk log I can see the apps are hidden which were selected before update to latest Magisk.

I have followed all the solution provided in github for the MagiskHide but still it is not working.

Anyone else facing this issue?
[Magisk] Didgeridoohan:
Do you mean that there are some apps that you can't see in the list, or that the list is completely empty of apps?
[Magisk] jcmm11:
He's probably using the XDA app, which didn't show the quote or the reference. Browser shows it fine.

Try not to include code blocks within quotes, it tends to screw things up in the app (not your fault).
[Magisk] DaveX2012:
Safetynet is not pass in. V 20. Any one.?
[Magisk] Ssnurzel:
Safetynet passes.
[Magisk] josdehaes:
On Huawei P20 pro, with EMUI 9.1 (EROFS as system partition), the messages app crashes with permission denied on the calls and mmssms sqlite databases. But only when rooted with magisk (20.0 or older doesn't matter). When I unroot, it works again. Anybody has any idea how to solve?
[Magisk] AndroTech:
App list is completely empty.

But in the Magisk log I can see -

* Starting MagiskHide

hide_utils: Hiding sensitive props

hide_list: <App hidden before update shows>
[Magisk] Ssnurzel:
Maybe some BuildProp Tweaks?
[Magisk] AndroTech:
It is working perfectly in v18.1 but facing issue after every Magisk update after 18.1.
[Magisk] palmbeach05:
Play store certified device still active for you?
[Magisk] Remmerboy:
magisk manager 7.3.5 is getting detected by one of my security app (app called "NemID), even with the hide magisk enabled. reverting back to 7.3.4 solves the problem.

magisk 20.0 is installed.

anyone have similar or same issue?
[Magisk] FriedOvaries:
I'm having the same issue.

Pixel 2XL. Last month I had September OTA update with SafetyNet passing. I OTA updated to October update and V20 via inactive slot as normal. SafetyNet fails both ctsProfile and basicIntegrity.

Play Store is showing not certified.

I already checked to make sure Magiskhide is working, and toggled it off and on.
[Magisk] palmbeach05:
I was told cts has some kind of connection with play store certification. Here's the fix

https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/amp/
[Magisk] Didgeridoohan:
That's the official way. Those of us that don't want to register too much with Google just change the device fingerprint to a certified one and then clear Play store data.
[Magisk] YoshiFan501:
On magisk 20? No. Confirmed by Netflix not showing up in search

magisk 19.3? yes
[Magisk] :
OnePlus 3, latest Los nightly, magisk 20, passing safetynet successfully, device certified in Google Play Store.
[Magisk] DaveX2012:
hmm. that's strange. What's your setting?
[Magisk] cjmaxik:
With Magisk v20, you can't choose apps to hide, your choice will be reseted after you change the window.
[Magisk] dundee81:
Magisk root hide does not work for pl.nask.mobywatel.

Could you fix it, please?
[Magisk] Listy2021:
I asked this recently but my post got swallowed up and never answered lol

How do I go back to Magisk v19.x from 20.1 as basic integrity and ctsprofile fail since I moved from ianmcd v19.5 to Canary 20.x so would like to go back

Device is Mi Mix 3 with GSI Arrow OS (A/B)

Thanks
[Magisk] ktmom:
Hiding root

Uninstall the current version and install the other one. How to uninstall
[Magisk] Teso79:
I do.

Thanks for the tip
[Magisk] Listy2021:
Cheers, if I run the uninstall from recovery can I flash v19.5 straight away after or do I have to reboot?
[Magisk] ktmom:
I would. If you do everything in one shot, then a problem occurs, you'll never know what caused the problem.
[Magisk] JhinCuatro:
[MENTION=4470081]topjohnwu[/MENTION]

How do I disable magisk from wanting to download updates from within the app when I use the install function? I don't want the latest magisk to be forced on me when it can break my setup, and I don't want to go to TWRP just to flash the magisk.zip to my inactive/active slot.
[Magisk] vMAC:
Hoping someone can help me with this problem. My father was doing an update to Magisk (thought he thought he was just updating Magisk Manager) and he accidentally did an install of Magisk after OTA. The problem is he didn't install and OTA so after rebooting the phone he is now getting an error: (Can't load Android System, your data might be corrupt).

Is there any way to fix this? I tried getting him to switch the boot slot via (fastboot set_active a and fastboot set_active b) but neither of those fixed the issue.

Any help would be greatly appreciated.
[Magisk] ktmom:
You don't say what the device is. The standard next step would include Fastboot flashing the stock boot.img. You could sideload the same OTA in recovery (if you can boot there). If there is a custom recovery on the device, you could try flashing the Magisk uninstaller. If you need help doing these things, the best place is to post in the device forum Q/A.
[Magisk] vMAC:
Sorry the device is a Pixel 2 (walleye). I will try to fastboot the boot.img.
[Magisk] vMAC:
So flashing the boot.img didn't work it still gives me thee same error.

To be clear he didn't install an OTA. What he did was go into Magisk Manager and hit update. When it asked "Select Method" he hit Install to Inactive Slot (After OTA). He then rebooted. This then started the issue where it is saying it is corrupted. He never installed an OTA, only hit that in Magisk Manager.
[Magisk] ant0nwax:
Hi,

https://play.google.com/store/apps/details?id=hu.telekom.telekomapp&hl=en_US

this App cannot launch with Magisk anymore

First worked on 19.3 then Telekom App got updated and did not work anymore, and now notworking on 20.0

see screenshots, i am happy to answer questions.

My phone Huawei P9 with Oreo 540 patch C02 (Tecalote)
[Magisk] jcmm11:
Flash boot image to both slots. You also need to choose the correct slot to be active.

Worst case you should be able to fix things by downloading the latest factory image and applying it after removing the -w from the flash-all bat/sh file.
[Magisk] Ssnurzel:
I use a Note 10+ with the 4th version of Dr. Ketans Rom. Base - N975FXXU1ASJ2 from October. I upgraded Magisk with the manager from 19.3 up to 20. Magisk Hide works.

The only used magisk modules are

"Libencrypto Disabler" and "Single user mod".
[Magisk] oldbear3:
Hello,

I use a Samsung Galaxy S5 Plus (SM-G901F - kccat6) that I recently switched to Android 9 via the latest version of LineageOS. When I was under Android 8 (also LineageOS), I had no problem with my online banking application "LCL Payment" (French bank), which did not detect the root thanks to Magisk.

Since I switched to Android 9, and even after I switched to Magisk 20 this morning, this application detects the Root state of my phone and therefore refuses to launch.

I unchecked and then rechecked the application in Magisk Hide, tried to associate other system applications with it, but nothing works.

The application displays the message: "Threat detected: The security settings of this smartphone (root access) do not allow to offer mobile payment. Error code: 2A0001"

Any idea of what I could do?
[Magisk] JudgeDread11:
Did you clear the app's data?

---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------

Same question.
[Magisk] ant0nwax:
You can be sure that I am reporting only stuff that truly does not work... i reinstalled the app, does that clear the app data? if not, yes i cleared the app data 4 times

The App works on rooted LineageOS 16.0 with Magisk 20.0

But on the UNSUPPORTED Huawei P9 Oreo that is only available officially in China (Tecalote & Team made this possible to be used worldwide) this app does not start anymore
[Magisk] guest4711:
So you should try

1. Hide MagiskManager (in MM->Settings)

2. Install MagiskHidePropsConfig module from Magisk repo and switch to another keyprint.
[Magisk] ant0nwax:
1. I played with Hide already, still does not work not hidden as Manager, and not as Magisk Manager, also reinstalled often during those

2. Installed the MagiskHidePropsConfig Module at Downloads, Device rebooted, App was uninstalled, and how to switch to another keyprint now?
[Magisk] Progressive82:
Hi,

I have a Nexus 6P with android 8.1. If I update to Magisk 20.0, installing zip from TWRP, reinstalling ElementalX kernel from TWRP too and then reboot, it remains stucked on "Google" logo. I had to reinstall Magisk 19.3 in order to reboot and make my phone working.

(The only module installed is Greenify4Magisk 4.3.3.0)

Someone could help me, please?

Thanks.