yashsingh1/xdaforums huggingface dataset:
[Magisk] JudgeDread11:
[/COLOR]Uds detection is fixed in the canary builds and will be in the next stable version. For now use canary or you can set a script at bit to fix it (search)

I believe root cloaking apps looks for Xposed and certain modules among other things.

---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------

The list of apps you are taking about are the "potential dangerous apps", which has app quarantine in it. I haven't seen a list of root cloaking apps posted, but might have missed it.
[Magisk] D3m0n1q_733rz:
Magisk modules will not finish installing or removing on reboot

Hello, these last three updates seem to have had issues with finishing installation and removal of modules. I'm running Android Marshmallow on a BLU Life One X2. I would happy include the logs, but I'm not really sure how to upload them here.

I've removed and installed Magisk again, it doesn't fix the problem. I've run the recovery based tool to remove modules, but even it fails to fully remove them. I would like to get Vanced working again, but modules won't finish. It's there anything I'm missing or haven't tried? Or is anyone else having issues?
[Magisk] jcmm11:
public static final String[] knownRootCloakingPackages = {
"com.devadvance.rootcloak",
"com.devadvance.rootcloakplus",
"de.robv.android.xposed.installer",
"com.saurik.substrate",
"com.zachspong.temprootremovejb",
"com.amphoras.hidemyroot",
"com.amphoras.hidemyrootadfree",
"com.formyhm.hiderootPremium",
"com.formyhm.hideroot"
};
[Magisk] JudgeDread11:
I am using sudo hide to hide Xposed installer as will as magisk manager (instead of repacking) and this works for my banking app.
[Magisk] wilsonhlacerda:
Yeah, this works fine. What's weird is that XprivacyLua (hiding all apps) does not do it effectively, at least on my tests. But sudo hide works just fine.
[Magisk] chrccruz:
Hi All,

It is my first time trying Magisk, hope you can help.

I have a CAT S41 unrooted (it seems nobody has it rooted yet). As per my understanding/reading I have two options: Magisk in Recovery or Boot Image Patching. Does anyone tried these on a CAT S41? Does it worked?

Regarding Magisk in Recovery, as per my understanding:

1. Download latest Magisk (Magisk-v19.3.zip).

2. Copy .zip to SD card.

3. Boot into recovery mode (vol up + power).

4. Apply update from SD card.

That's it? Am I missing something?

Thanks in advance. Sorry for noob questions :)
[Magisk] martyfender:
You can't do this in the stock recovery. You must have a custom recovery, such as TWRP.
[Magisk] SonOfTheRain:
Hello,

I was using Magisk wihtout any issue until last update of my Mate 9. Now software version is 9.1.0.252 (C432E7R1P8) and as after every upgrade I re-patch my recovery_ramdis.img and patch from fastboot. In order to boot with root, I used recovery mode and it entered in system with root privileges. After the last update I did the same but recovery mode enters in recovery mode and system shows as non-rooted.

Please help, how to root my Mate 9?
[Magisk] avf90m:
Is there going to be an update with magisk to support the Moto g7 play? I've tried flashing magisk via abd twice but still no root. I was told this is because this is an a/b device. Any help on getting root with my g7 play.
[Magisk] martyfender:
Usually, the best way to flash Magisk is through a custom recovery, such as TWRP. If you don't have a custom recovery, try patching a copy of your stock boot.img in Magisk Manager, copy it to your PC, boot your device to bootloader mode and flash the boot.img through fastboot and not adb. Adb is used only when the tablet is booted normally. The buttons to hold down to boot to fastboot/bootloader mode can vary with different devices, I think. On my devices it is volume down + the power button, when the device is off.

fastboot devices

Hit the enter key to confirm your device is connected. The fastboot serial number should be listed

fastboot flash boot patched_boot.img

Hit the enter key to flash with the above command.

fastboot reboot

Hit the enter key to reboot with the above command.

Also, if your PC is Linux, you must use sudo before the above fastboot commands to run as root. In Widows you just need a root command line window. I usually copy the boot.img to my adb/fastboot folder, right click in an empty spot, open a command prompt here, then enter the commands. The other option is to also put a shortcut for the command prompt in the above folder, then right click, run as admisitrator, to ensure it is actually running as root.

You don't have to do this if you have adb and fastboot set up with a system wide variable, you can have the boot.img copied anywhere, but I find the above method much easier, especially if you don't know how to setup the system wide variable..

Finally, somewhere here on xda there is an adb/fastboot installer for Windows which gives you the option to set up the system wide variable.

https://xdaforums.com/showthread.php?t=2588979

I don't think it has been updated to the latest adb and fastboot though.

The author recommends using the latest for newer devices, available here:

https://dl.google.com/android/repository/platform-tools-latest-windows.zip
[Magisk] avf90m:
Yeah sorry I meant to say I flashed the patched image through fastboot and still doesn't root. From the g7 play forums it seems to be an issue because it's an a/b device
[Magisk] joluke:
Flash via twrp
[Magisk] avf90m:
No twrp available for my device
[Magisk] joluke:
No!? Next time Google it... Google is your friend: https://www.google.com/search?q=twr...j0l3.4593j0j4&sourceid=chrome-mobile&ie=UTF-8

There is twrp for your device..
[Magisk] avf90m:
Sorry man none if those work on the device. I've read every single one of those threads and links. No one has been able to Port it to the g7 play because of the a/b partion
[Magisk] martyfender:
So temp booting that TWRP on your device doesn't work also?
[Magisk] palmbeach05:
So let me get this straight, we just wasted about 2 pages in this magisk support thread dealing with your device, but you don't have twrp available for your device? Why are you wasting our time? Go get twrp first, then come back
[Magisk] avf90m:
I temp booted it but nothing will flash properly due to the a/b setup on the phone.

---------- Post added at 06:44 PM ---------- Previous post was at 06:41 PM ----------

There isn't any TWRP for my device like I just said. The g7 play forums don't have any working twrp if would read through all those threads. That's why I'm asking if magisk will be updated to be manually flashed thru fastboot. Because when I tried manually doing it it didn't work at all because the g7 plays a/b scheme.
[Magisk] varadinum:
Hi guys

Please, I need your help. My Samsung Galaxy A9 SM-A920F is rooted. Now I have found a new update from Samsung. Original firmware update. How can I install this so the root is preserved. Is that even possible? There is no twrp for my Samsung Galaxy A9 2018 SM-A920F. At the time, it has the patched boot.img with odin flashed. How can I flash the original firmware?

Thank you in advance.

Gesendet von meinem SM-A920F mit Tapatalk
[Magisk] palmbeach05:
If you're on a up to date magisk version, it has a survival script built in. Idk wether it will work with firmware updates from the manufacturer though. You can always download the update and flash a patched boot.img via odin to restore root
[Magisk] varadinum:
[MENTION=4895937]palmbeach05[/MENTION] many thanks

So, if I understand correctly:

before the update have to uninstall magisk?

1 / download firmware

(ota update over phone does not work)

2/ flash firmware with odin

(a factory reset is performed)

3/ after the flashing starts a new clean system

(all previous applications are gone)

4/set up a new system

(settings ... and set up)

5/install magisk manager

(patch original boot.img with magisk)

6/ patched boot.img via odin flashing

7/ enjoy

So, I have to reinstall and reset everything.
[Magisk] wilsonhlacerda:
About the bug with Magisk Hide only working after toggleing:

I've just completely clean installed LOS16 (Android Pie) + Magisk 19.3 + Rootbeer Fresh app. Nothing else.

Unfortunatelly the bug is also present this way. Even setting Magisk to Core Only the bug happens. (Rootbeer always detects root)

After toggleing Magisk Hide works as expected, Core Only or not. (Rootbeer never detects root)
[Magisk] palmbeach05:
I would not uninstall magisk at all. Download firmware? So its like a sammmobile download? That makes things easier. Keeping the full download on your computer, extract the boot.img and move it to your phone. In magisk you download magisk (top package, 19.x) and there is an option to patch a boot.img. Pull the patched boot.img off your device and put it on your computer. Flash via odin the update firmware. One it successfully boots up and you do whatever basic setup you want, reboot to download mode and flash patched boot.img via odin. You may need to package the boot.img up in a *.rar file before flashing.

I'd say that should do it unless there is extra security by samsung in newer releases. I have the j500m and we're stuck at 6.0.1, but that hasn't stopped me from hearing and reading things. Check with others in your device community first before doing what i just said to do
[Magisk] dsahai:
Updated bank apps (HSBC and StanC) now detect root with the latest stable version of Magisk :(
[Magisk] mousa el sawah:
Please help me

Magisk hide not shown in the manger app

I tried to hide root with modules but didn't work anymore ... Ctsprofile : false

Basicintegrity: false

No root hide

Please help me i can't use bank app and MacDonals app

Sorry for my bad English
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

https://www.didgeridoohan.com/magisk/MagiskHide#hn_MagiskHide_Issues
[Magisk] mousa el sawah:
I read in your link that magisk hide work in kernel 3.8 my kernel is 3.4.67 so it will work ? ...help me please sir
[Magisk] Didgeridoohan:
Version 3.4.67 is older than version 3.8... It's very likely that your kernel doesn't support mount namespace, which means MagiskHide won't work. Possible solutions are described in the posted link.
[Magisk] kotuamoalt:
It sounds like your bootloader might be locked.
[Magisk] palmbeach05:
No they are still working on getting twrp developed, i checked
[Magisk] wilsonhlacerda:
I have Android Pie (LOS16) with kernel 3.4.112 on a Galaxy S4 and Magisk Hide works fine (without any tricks, besides toggle it after boot due to bug since Magisk v19.3).

Previously I had Android N (LOS14.1) also with old kenel and Magisk Hide was also fine.
[Magisk] kotuamoalt:
I am somewhat amazed that you are able to run Pie on an S4.
[Magisk] wilsonhlacerda:
And it runs fine! Even with Magisk and Xposed. :)

Not for (new) games, but apps in general runs all fine.

My girlfriend also has an S4 *Mini* runing Pie.
[Magisk] martyfender:
That is most likely because the developers of custom roms usually backport the mount namespace to the older kernels.
[Magisk] guest4711:
Pie is running fine on SII (now with Magisk!), S4 and S5...
[Magisk] onliner:
Hi, can you describe the "I've tried flashing magisk via and twice but still no root"?

If you're talking about the fastboot method (patch the boot image and flash it), it works perfectly with A/B devices, always I use that method with my 6T.

I remember some problems with some Motorola devices in the past due to a "broken" F2FS implementation, maybe your device has a new problem, who knows.
[Magisk] Medyredy:
Hey guys, I recently lost root on my bank app, running my s5 that's on the latest havoc. Then I decided to update to the latest build 19.3, still no root..isn't it weird that I lost root out of the blue?
[Magisk] Shalomadepoju:
Core only mode is always enabled... even after reboot. Please help.

Hello,

For a while now, I've noticed that i can't uninstall/remove modules I don't use anymore. It keeps showing "Module will be removed at next boot" or something, and it just stays that way, no matter the number of reboots I do.

I've discovered that "core only mode" is always on, after every reboot, even if I turned it off before rebooting as is recommended in the toast notification.

Apparently, at every reboot, something keeps writing ".disable_magisk" to /cache.

Help.

I've attached what I think are logs from magisk, after reboot

pastebin.com/r3hFVL9L

Thanks.
[Magisk] palmbeach05:
Download magisk module magisk manager for recovery. Reboot to recovery, get into terminal, enter */mm and enter the value for core mode and that should re-enable it
[Magisk] guest4711:
Probably these are old modules from an old installation where magisk used another structure (magisk.img). Use a good filemanager like MiXPlorer to delete them.

If this does not help, save your magisk.db (located in /data/adb), flash magisk uninstaller and magisk again. To restore your hide list and you su list simply restore magisk.db (or recreate it from scratch).
[Magisk] palmbeach05:
I had enabled core mode only and couldn't get out of it through an uninstall/reinstall process. I had to go back, flash the module i mentioned above, disable core mode only, and then i was good to go.
[Magisk] FriendlyNeighborhoodShane:
Hi!

I went through the documentation, but it seems to be outdated, so I had these two questions about v19.

A) How does the latest system-as-root rooting mechanism work, actually? I understand that now there's no ramdisk for Magisk to inject its init script into, and that's why it had to depend on booting from the recovery in Samsung stock ROMs for the last few versions. So how does it do it now?

B) I have a... rather peculiar device, the Galaxy A70 (A only, system-as-root). I managed to root the stock ROM with Magisk using the recovery method, but no thanks, I hate OneUI.

Andy Yan's LOS is one of the few GSIs that it chooses to boot and for that, it needs to disable DM-verity (which I do using the very handy universal disabler by zackptg5). But I can't get Magisk to work with it.

Now that it is using a GSI in system, I guess it's no longer considered a Samsung firmware and is a generic SAR device and the recovery root method doesn't apply anymore.

So what I tried is:

-- flashing clean stock ROM

-- flashing a blanked vbmeta to disable AVB

-- flashing GSI

-- flashing Magisk from TWRP (which shows no errors and succeeds)

-- flashing DM-verity disabler

-- formatting data

But it doesn't even get to the bootanimation, just keeps rebooting on the device logo (like it would've without disabling DM-verity). This process works and the device boots perfectly when I omit the Magisk flashing, but then obviously I have no Magisk.

I would provided logs if needed, But I had a feeling I was just attempting something wrong.

Thanks!
[Magisk] jcmm11:
For GSI you may want to read https://github.com/topjohnwu/Magisk/issues/844

For A I'll defer to somebody else.
[Magisk] _litz:
I'm about at wits end with Magisk. Need it to do tasks, but the thing just plain doesn't work reliably.

Stock OS (Moto X Pure) vanilla Magisk (no modules loaded at all), 3-5 times A DAY no root and "magisk not installed" and have to reboot to regain it. Always works perfectly after boot, until it fails again.

Happens on every OTHER device I own, too, with various OS versions.

This happens ENDLESSLY and it's been happening since v17. didn't get fixed in v18, still isn't fixed in v19.

There are posts all over the place from people having this problem, is there ANY fix? It's DEFINITELY not unique to either myself or my devices.
[Magisk] FriendlyNeighborhoodShane:
Thanks!

Well, that thread is about people booting Magisk on their A (tradition system) GSIs. But it led me to other issues by people trying to boot Magisk on my A/B (system-as-root) GSIs setup! And some of them succeeded. It seems to accomplish this by some sort of boot image patching, but I'm still baffled.

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

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

I figure once I know how it works, perhaps I'll get an idea of how to work it
[Magisk] Didgeridoohan:
As far as I know, nobody with this issue has managed to show why it's happening, which means that there's nothing [MENTION=4470081]topjohnwu[/MENTION] can do to fix any potential issue. Some have success by making sure the Manager isn't killed off by any battery optimisation, but far from all.

But, until somebody figures it out (someone experiencing the issue, and John isn't) your best hope is workarounds like this, but I see you've already considered that.

If it's a matter of the device not working as a Samsung A-only SAR anymore, that's likely the issue:

https://twitter.com/topjohnwu/status/1162042158087434240

---------- Post added at 08:55 ---------- Previous post was at 08:52 ----------

Not sure from your post if this is even applicable (it's a little sparse on details), but make sure that the Manager isn't installed to any external/adoptable storage.

Other than that you might be experiencing a root loss issue that some users keep having. Some have success by making sure that the Manager isn't killed off by some battery optimisation.
[Magisk] JudgeDread11:
You might have done this already, but make sure that magisk is excluded from any battery saving apps, as well as from Android battery optimization.
[Magisk] FriendlyNeighborhoodShane:
Thanks, but both of those solutions are for when root isn't working. Meanwhile, I can't even boot with Magisk :laugh:

I managed to get last_kmsg from a failed Magisk boot. If you guys wanna take a look at it, I can PM the file to you (if you're okay with it, of course)
[Magisk] Didgeridoohan:
Weird... That was not at all the link I had copied. This is what I meant to post:

https://twitter.com/topjohnwu/status/1162042158087434240
[Magisk] FriendlyNeighborhoodShane:
Oh. Yeah. Yes, that is exactly it. But then I wonder what the "Added system-as-root support" in the v19.x changelogs meant.
[Magisk] Didgeridoohan:
Well... That was probably the solution at the time. Now, other stuff has likely popped up and needs new solutions. I haven't looked closely at it, so can't say more than that.
[Magisk] matthias1976:
Hi !!

I got BQ U Plus Smartphone with LOS 14 running and Magisk SU wont work.

Magisk 19.3 over twrp and latest Magisk Manager App installed. Open Manager App says all installed. When open an app that needs root there happen nothing. No asking about su access !?

Manager app gots no entery in SU section.

Im not rooted.....

On stock rom there was no problem with magisk and all worked perfect.

The LOS SU addon works but some apps not as good as in stock rom with magisk.

Any idea !?
[Magisk] heynando:
when I click UNINSTALL -> RESTORE IMAGES, a message shows up saying STOCK BACKUP DOES NOT EXIST.

I have the original boot.img in my computer, in which directory shall I place it for it to be recognized by Magisk Manager so that I can continue with the installation-of-OTA-whilst-retaining-Magisk process?
[Magisk] garylawwd:
You don't need magisk to do a thing. If you already have the stock boot.img just flash the image in custom recovery like twrp.
[Magisk] jcmm11:
Take the original boot image and get the sha1 hash. Rename it stock_boot_<sha1 hash>.img

e.g. stock_boot_f34f217a3eb1dc8d12d987db2c7acdf3bd2df5d1.img

Now gzip it

stock_boot_f34f217a3eb1dc8d12d987db2c7acdf3bd2df5d1.img.gz

Place it in /data/

/data/stock_boot_f34f217a3eb1dc8d12d987db2c7acdf3bd2df5d1.img.gz
[Magisk] heynando:
I think doing it via Magisk Manager is better because it will be less steps to click and I wouldn't need a PC nor cable nor adb. Plus, it will generate the backup necessary to update the next OTA when it comes. The aim is to apply the OTA seamlessly. I just didn't expect the backup to not exist. Here's the log of the installation. It seems it didn't create a backup because it detected an already patched boot.img

Anyways I prefer to do it without needing a PC whilst avoiding TWRP too. Is it possible make Magisk Manager recognize the original boot.img by placing it in a specific directory?
[Magisk] heynando:
Thank you very very very much :fingers-crossed::fingers-crossed:
[Magisk] zputnyq:
My apology if this has been asked before.

I want to activate magisk's systemless host module.

Is it possible to activate it from twrp ? My twrp have a working to execute commands
[Magisk] dd721411:
Why don't you just activate it from Magisk Manager? :confused: I'm not sure about TWRP though.
[Magisk] martyfender:
Is activating it through the Magisk Manager settings and rebooting to make it active, not working for you? There is no longer a toggle switch for it in settings. You just click on it and you should see a toast that states:"added systemless hosts module". Then, just like any other module you install, you must reboot to make it active.
[Magisk] heynando:
After placing it inside /data I was able to continue the process. I checked the Magisk log and there's nothing in it saying the restoration was successful. But I saw a toast message saying "RESTORATION SUCCESSFUL".

Unfortunately I wasn't able to install the OTA, the updater failed to install it even with the original boot partition, even after reboot. I extracted the boot.img from the official firmware I used to install. I'm not sure if this is Magisk fault.

Should I jump to fastboot and flash the original boot.img and then reboot and then try to install the OTA? Suggestions?

How do I check what is causing the updater app to fail? Maybe it is checking something else beyond the boot partition.
[Magisk] zputnyq:
I know about it & It's working fine but I want to do all at once when I do a clean flash.

I did a clean flash & I have already had some modules that I keep, host file & a script. So when I flash magisk in twrp, I could also flash & put all what I need.
[Magisk] jcmm11:
Depends on exactly how you're doing the clean flash. If you're not wiping/formatting /data/media you can, before the clean flash, copy /data/adb/modules/hosts/ to /data/media/

Then, after the clean flash, move the folder back. Other than that you can create a script to recreate it, or create your own Magisk Module zip. There's no built-in way to activate it via TWRP
[Magisk] vonDubenshire:
Can someone help me with my Pixel 3?

There's open issues about this on GitHub.

It's with the Pixel Live Wallpaper module in the repo.

https://github.com/Magisk-Modules-Repo/pixel-complementary-live-wallpapers

It will not download.the wallpapers -- it always stops on no internet connection.

https://github.com/Magisk-Modules-Repo/pixel-complementary-live-wallpapers/issues/7

---------- Post added at 04:17 PM ---------- Previous post was at 04:16 PM ----------

Can someone help me with my Pixel 3?

There's open issues about this on GitHub.

It's with the Pixel Live Wallpaper module in the repo.

https://github.com/Magisk-Modules-Repo/pixel-complementary-live-wallpapers

It will not download.the wallpapers -- it always stops on no internet connection.

https://github.com/Magisk-Modules-Repo/pixel-complementary-live-wallpapers/issues/7
[Magisk] zputnyq:
Ok, I get it. :)
[Magisk] Sarandeep Singh:
Lost magisk

Flashed module busybox android ndk from magisk and after reboot i lost root and open magisk manager its showing magisk is not installed so how can get magisk installed again , should i have uninstalled previous magisk files ? How to do

---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------

Flashed a module busybox android ndk from magisk and after reboot i lost root and open magisk manager its showing magisk is not installed so how can get magisk installed again , should i have uninstalled previous magisk files ? How to do
[Magisk] zgfg:
If you think it's due to Busybox and if you can, boot to TWRP, Terminal or File Manager and delete /data/adb/modules/busybox-ndk
[Magisk] Sarandeep Singh:
Thanks for your response, can u tell me whats the twrp terminal command for this ?
[Magisk] ecksdeeay:
delete /data/adb/modules/busybox-ndk

Isn't it?
[Magisk] dope77:
I have the latest canary running on my android 9, the manager crashes whenever i try to see the su log. Anyone facing this problem?