yashsingh1/xdaforums huggingface dataset:
[Magisk] SharkyBeAre:
I want to report a bug, I have a phone with an AOSP's custom rom, with 5.8 version specifically, when I installed Magisk Manager it worked nice the option for getting in the app from the settings, now I don't know why when I try to open Magisk from the settings it stops. I don't know if that's because of the updates you gave it or it's a rom issue.
[Magisk] BurnedDrake:
It's because the ROM has Magisk Manager baked in. Not sure why devs keep doing this stuff, seems whenever they make Magisk built in, it screws things up. It's not like it's hard to flash it seperatly.
[Magisk] jhedfors:
Sounds like an issue with the ROM's custom integration - not sure why ROM developers do this.
[Magisk] ramabg:
Of course I do not want my banking apps to be able to detect root because It will make them stop functioning, however I still need my utility apps like kernel manager and tweaking apps to properly detect roots because they need It and I use them on daily basis. The problem is these utilities app no longer be able to detect root after I hide magisk packages manager eventhough they are not in magisk hide list, therefore I cannot have both my banking app(It is dbs btw) and utilities app active at the same time. I have to switch Hide Magisk Package manager on and off in order to use either of them. It is kinda annoying.
[Magisk] martyfender:
So you are having trouble in obtaining root access for those apps, not detecting root. It is your wording of it that confused me. I believe detecting root and obtaining root access are two different things, if I am not mistaken.

I have never had that happen, so maybe someone else will have an idea.

I would suggest though, that you provide at least the minimum information to get help on all of these Magisk forums: device info, Android version, Magisk version, magisk.logs and logcats, as attachments or a link posted to a file sharing site and not in the body of the message.

https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] Charli3M:
So no solution but to<wait and<go back to super su.

Nevermind i fixed the problem of not being able to upgrade to 17.1 by wiping the data partition. It was saying boot partition space was insufficient and also to remove ramdisk backup.
[Magisk] jenslody:
Solution for which issue?
[Magisk] paarnoutse:
Suggestion:

As described by [MENTION=4739170]drmjp93[/MENTION] in https://xdaforums.com/showpost.php?p=77848477&postcount=28223 the Gpay Magisk Hider module seems to be a possible reason why not hided apps may have no root access.
[Magisk] jhedfors:
Based on the information you have provided, that may be the best option for you.
[Magisk] DaystromLIVR:
Could the Patched Image Format be moved out of the Settings page and onto the dialog where it gives the option of 'Download ZIP or Patch Boot Image'.

I find that when prompted to "Install Magisk" (especially after a reinstall), the natural work flow bypasses setting this option, and I've already downloaded the ZIP, patched it, and taken the resulting patched image off the device onto the computer before realising I've got to restart the phone and do it all again, this time with the 'img.tar' setting (I use Odin).

Alternatively, why not just generate both options at the same time. I've tried taring the .img file on the PC, but Odin doesn't like the format for some reason.
[Magisk] DaystromLIVR:
What is GPay Hider Module, and should I be using it?

I just put GPay in MM's Hide list, randomised the MM package, and set it to Deny Superuser. I have never needed a special module for Hiding from GPay and it works perfectly, as do TotalCommander, Termux etc, which gain root perfectly well.

What am I doing wrong ?
[Magisk] yochananmarqos:
No one should be using something called "GPay Hider". If SafetyNet passes, Google Pay will work out of the box. No need to add it to the hide list.
[Magisk] drmjp93:
There was a prior error with Google Tez (Now renamed as G Pay for our country) the module was called TezHider4magisk, so Tez would work only with this module on rooted phone.

But now after it was re-named to G Pay, don't know why it interfered with Magisk.

So I disabled module.

And truly said, it still works.
[Magisk] Gallion:
Nexus 6P on stock 8.1.

I recently did a factory reset of my phone because I was having issues with SafetyNet randomly stopping passing. After making sure it was passing SafetyNet after the reinstall, I have left my phone untouched except for using it to take pictures with it. Well now it's not passing SafetyNet anymore. Again. Both CTS Profile and Basic Integrity fail. The last 2 times my phone randomly stopped passing SafetyNet it was after it had run out of battery. I don't know if that's a coincidence. In any case, I don't want to factory reset again it's a real pain in the ass. What else can I do? I've already gone through all of https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet the last time around so I'd like not to do that again especially since this is basically a fresh install.
[Magisk] kkazakov:
Is it possible to disable Magisk Manager's auto-installation of stub every other day? I keep uninstalling it and every time it appears. I have an application which detects root based on Magisk Manager being present and this is pretty annoying. What I do usually do is - use Magisk Hide and then remove the Manager (don't need it anymore).
[Magisk] ashyx:
Can't you just hide it?
[Magisk] difr:
Magisk Manager v 5... was working with following

Intent rootManagementIntent = new Intent();
rootManagementIntent.setClassName("com.topjohnwu.magisk", "com.topjohnwu.magisk.SplashActivity");
startActivity(rootManagementIntent);

How to handle with v 6... (code above make crash)

?
[Magisk] Indashio:
I did not find the answer. I registered the device on Android/uncertified one more time tomorrow one more time magisk several versions and nothing CTS is false I have the impression that I have tried everything described there.
[Magisk] bemymonkey:
Quick question from a potential new user: What does the update procedure look like when the manufacturer releases an update?

i.e. with SuperSU the process is:

Download full update image in zip format

Flash via custom recovery

Flash SuperSU via custom recovery

Clear caches

reboot

Is Magisk similarly easy to handle?
[Magisk] Nimueh:
Never mind, I misread ... ignore :(
[Magisk] maddoctorgr:
Hello. I have Xiaomi Mi 8. Installed yestarday latest ROM, 8.10.11 and after that tried to root my mobile

With the previous version of ROM didn't had any problem and was installed ok from the magisk app. Now I try the same and it says installation failed.

Update: This time was installed ok from twrp, when previous time was getting error messages. Strange...
[Magisk] guest4711:
Yes. Flash Magisk.zip instead of SuperSU. Wiping caches may not be required, it depends on ROM.

I'm used to wipe system before flashing, too (also if using other root methods than Magisk).
[Magisk] bemymonkey:
Thanks guys - you too, [MENTION=4649623]Nimueh[/MENTION], I saw your info regarding in-app-updating Magisk in the notification e-mail and it was still useful :)

---------- Post added at 06:27 PM ---------- Previous post was at 06:27 PM ----------

Thanks guys - you too, [MENTION=4649623]Nimueh[/MENTION], I saw your info regarding in-app-updating Magisk in the notification e-mail and it was still useful :)

-edit- Why the **** does XDA keep doubleposting my posts? I only clicked once...
[Magisk] Indashio:
PLEASE HELP

I found a solution on CTSProfile: false to true its module DaydreamBypass Unfortunately, there is another problem here. When I flash DaydreamBypass I lose ARCORE

I try change file post-fs-data.sh for oryginal from XZ Premium and XZ3, and XZ2 lines with fingerprint change from dev-keys to release-keys but after flash i lost again CTSProfile true and ARCORE not working too :/

However, when I change the original build.prop with Pixel XL lines in prop. By magisk this does not change CTS to True

How complicated. Currently, I have to choose either ARCore Google or CTSProfile: true

I also need to change Root default.prop?

I did it once and the system fell I do not know whether to take risks

What lines can I change yet?

Why it's working with pixel XL but not with Xperia ?

My device Xperia XZ Premium now I try fingerprint set to Xperia XZ3 release-keys photo:
[Magisk] Stonecaper:
- Detecting target image

- Target image:

- Device platform: x86

- Downloading zip

... 0%

- Extracting files

does not exist!

! Installation failed
[Magisk] TenshoDaijin:
Hey maybe one can help me...

Magisk Hide v17.2 dont work for me..

the wierd part is Magisk give me no error log..

say only "Magisk Hide Manger failed..."

---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------

Hey maybe one can help me...

Magisk Hide v17.2 dont work for me..

the wierd part is Magisk give me no error log..

say only "Magisk Hide Manger failed..."
[Magisk] Speedmaster_102:
Hello Magisk Team! Loved Magisk on my Nexus 6!

I just got a new phone, I upgraded from a nexus 6 to a pixel 2 XL. I decided to flash Magnisk without the TWRP bootloader and retain its stock OS on Pie. After I flashed a couple of modules (Youtube Vanced and Greenify), the boot image became corrupted and I lost everything and had to re-install everything back onto the phone from scratch.

So, please clarify? I can't flash modules, but I can only have root in the stock Android 9.0? How can I flash modules such as youtube vanced and Greenify?

Many thanks team!
[Magisk] martyfender:
If you had SupeSu installed you should flash UnSu.zip first, followed by a flash of your stock boot.img, to be safe, then flash Magisk.zip, all before rebooting.

If you do wipe the system and reflash your rom, of course, you only have to flash magisk.zip. In some cases, after reboot, you may also have to install the Magisk Manager. It should be install after you flash the Magisk.zip, but there are some cases where Magisk Manager is not installed after flashing Magisk.zip.

---------- Post added at 10:48 PM ---------- Previous post was at 10:43 PM ----------

-edit- Why the **** does XDA keep doubleposting my posts? I only clicked once...[/QUOTE]

I wonder as well, why you have double posts?

I have had that only happen occasionally and for me it seemed to happen when I was having trouble saving the post, or attachments and clicked it a second time.

Sometimes, I think xda is just having problems.
[Magisk] evansourav:
Magisk fails in Safetynet after sometime, reboot fixes it temporarily, then again it fails... why? :confused:
[Magisk] FlavioV:
Worth a read for anyone having issues with SafetyNet

https://topjohnwu.github.io/Magisk/tutorials.html#best-practices-for-magiskhide
[Magisk] cipri10:
Same for me, i'm using AEX 5.8 with October security patch with Magisk 17.2 on Lenovo P2
[Magisk] Stonecaper:
Any help?
[Magisk] Homeboy76:
What are you doing, that you need help with?
[Magisk] Stonecaper:
Trying to install magisk on a x86 device
[Magisk] Homeboy76:
Do a search for the device and Magisk-??.?.zip
[Magisk] Stonecaper:
Installed magisk manager apk from XDA labs
[Magisk] bafforosso:
Hello,

don't know if it is the same issue but it sounds similar : Greenify4Magisk module is known to cause bootloops on Pixel phones on Android 9.

Module specific issues are usually discussed in the module's thread, have a look here for Greenify4Magisk : https://xdaforums.com/apps/magisk/module-greenify4magisk-t3606277
[Magisk] xunholyx:
Generally, you only use Magisk Manager to update Magisk. If you are installing it for the first time, it's often best to flash it in recovery.

You can find the instructions here.
[Magisk] martyfender:
What x86 device do you have and do you have TWRP for your device? My Nextbook Ares 8A's with Android 6.0.1 are x86 devices and Magisk installs fine on them. The most reliable way for me is to flash it through TWRP. I sometimes have problems if I use the direct install method. If you don't have a custom recovery, then patching a copy of your stock boot.img and flashing it with fastboot is the other option.
[Magisk] yochananmarqos:
FYI, you didn't need to reinstall everything. All you had to do was uninstall the offending module via TWRP or flash your stock boot.img. See the Unchanged Modules topic heading in my Collection of Magisk Modules v2 thread for more information about uninstalling modules.
[Magisk] Stonecaper:
I have an Asus Zenfone 5 (2014)

I do have twrp installed, however I didn't know about flashing it for the first time through recovery. Doing it now and reporting back
[Magisk] JW19:
Oneplus 6 owner here.

Received a new update today but was rooted so I pressed restore images. No stock image found because I realised I factory reset my phone earlier. So instead I pressed complete uninstall in magisk manager.

After that my phone is bricked. I can access fastboot and recovery but cannot boot. Bootloader warning shows up then just black screen.

Factory reset in recovery does not fix problem. Bootloader is unlocked.

Tried doing "fastboot boot twrp.img" but device then shows qualcomm crashdump

Tried flashing a stock boot image but on terminal it said partition boota not found.

What are my options???
[Magisk] Nebrassy:
I'm not sure if op6 supports seamless update but I think it does, try fastboot flash boot_a boot.img
[Magisk] JW19:
Omg I cannot thank you enough. It worked first time.

I only wish I did that before factory resetting...
[Magisk] Stonecaper:
So I flashed the magisk zip through twrp, gave me an error 1.So extracted the boot.IMG file from my ROM and flashed, but twrp can't see any partitions to mount.:rolleyes:
[Magisk] Gallion:
I am having this issue too even with a fresh install.

I've already gone through the page that everyone links when someone brings up SafetyNet issues. Nothing fixes it.
[Magisk] evansourav:
Disable then Re-Enable Magisk Hide fixes the problem temporarily. Try it and let me know.
[Magisk] Fif_:
If toggling MagiskHide off and then back fixes the problem, have you tried increasing the log buffer size in developer options? What's your log buffer size?
[Magisk] evansourav:
256k Currently, How much should it be? I have no idea!
[Magisk] Fif_:
That's the standard. You can try to bump it up to see if it makes a difference...

Well, if SN fails, it could be because Magisk missed a GMS service starting up. Magisk uses logcat to track app starts. If you had so much logging going on that the logcat buffer was overrun, that could explain how SN suddenly fails.

When you turn Hide off and on, Magisk will rescan all running processes to find GMS and all MagiskHidden apps, and think will work again.
[Magisk] evansourav:
Thanks for the explanation, it seems like it is because of greenify, i do have a bad habit of hybernating most apps including system apps + I hibernate apps that has gms. Can it be the possible reason?
[Magisk] Fif_:
Probably not. You're not greenifying Magisk are you? If so, that may be the cause of your problems.
[Magisk] evansourav:
Nope.... What else can it be, it's keeping me awake at night.
[Magisk] Charli3M:
When i was trying to upgrade /update to Magisk 17.1 it was not able to . It was in a boot loop.
[Magisk] pleclair:
Your device needs additional setup....

I have installed magisk 17.1 on my lemfo lem6 watch. Everything went fine, except that after I flash the .zip file, and install the manager, the manager tells me that my device needs additional setup for magisk to work properly. I see that it wants to download something else, but the screen size is too small to display the whole popup, and I can't scroll it. So I cannot press any buttons (I guess there are some...)

Root checker tells me I have root, I can access root shell, every root app I run, runs fine... but... I tried to install the debloater module, and it says that it cannot see magisk installed. So I think this might be the reason why?

Is there any file I can manually download and install myself to do that additional setup?

I tried searching the forums here for this sentence, and on google, and seems that no one ever had this one. I figure that usually one can click and do something about it, but I can't :eek:

Thanks for helping me out! And thanks for this fine piece of rooting software!
[Magisk] android_smater:
Hello i tried both beta and stable versions 17.1 and 17.2, but when i open magisk hide it crash and there is no log for that

I am using Oneplus6

Oxygenos 9.0

Android pie
[Magisk] guest4711:
So it is missing the correct MagiskManager for your version. Downliad it from the repo where you downloaded magisk itself. If you are using e.g. the unofficial builds by [MENTION=3306843]kantjer[/MENTION]download it from his repo. Otherwise use the link in the op.
[Magisk] juch11111:
I installed a magisk on my phone and everything works. Except for the flashlight. :/ I can't turn on the flashlight from the bar. A message was displayed that another application is currently using the flashlight.

The flash control option has also disappeared in the camera.

When I uninstalled the magisk everything returned to normal. Flashlight works again. Can You/I improve it?

My phone: LG G5 H850

Firmware: H85030a_00_OPEN_EU_OP_0910.kdz (Oreo)

Magisk v17.1
[Magisk] IllUMINATUz:
Hey. I'm running the Xiaomi Pocofone F1 and I'm not able to use Google Pay. Upon checking I found the ctsProfile is false.

Also the selinux status isn't enforced. I'll have to manually do it.

Any help here? I saw many posts about editing the /system/build.prop and edit the fingerprint sensor. Can someone please shed some light here?

Thank you.
[Magisk] Tr4sHCr4fT:
Poco does not have NFC
[Magisk] IllUMINATUz:
I know. But I can do online transfer. I'm not able to sign in also. The app is closing stating security.

I think I need the data in the build.prop file.

As to what to update for the fingerprint sensor.

The ctsProfile is false. It should not be false.

Edit : https://r.tapatalk.com/shareLink?ur...hare_pid=77902183&share_fid=3793&share_type=t

[quote name="IllUMINATUz" post=77901670]Hey. I'm running the Xiaomi Pocofone F1 and I'm not able to use Google Pay. Upon checking I found the ctsProfile is false. <br />

<br />

Also the selinux status isn't enforced. I'll have to manually do it. <br />

<br />

Any help here? I saw many posts about editing the /system/build.prop and edit the fingerprint sensor. Can someone please shed some light here? <br />

<br />

I'm using extreme kernel. <br />

<br />

Thank you.[/QUOTE]<br />

<br />

Install module "universal safetynet fix" and reflash magisk
[Magisk] Speedmaster_102:
Really? That would had corrupted the boot image then?

Am I safe to install other modules such as ad block , YouTube vanced? I am on stock recovery as I want to retain the OTA updates. However, I can install TWRP and and run a back up if need be. But I'd prefer not to install it and the option is available if need be.

Thanks guys for your amazing support. It is greatly appreciated.

-SM102
[Magisk] Fif_:
Have you tried bumping up the log buffer size?

Probably not. There may be something bad with the module. Have you tried to systemize Greenify with Terminal Systemizer instead?
[Magisk] bafforosso:
No idea about bootloader image or why it causes such behavior on Pixel phones on Pie, you could ask the dev in the topic if you're interested in that.

With rooting, Magisk, modules and such things you will never be 100% "safe to install", there will always be use cases that have not been thoroughly tested (or even tested at all) because indie devs don't have the machine- and man-power to test every single one of them (and every combinations of them), because most of it is experimental development and because it is (and probably always will be) a cat-and-mouse game with Google and all the phones manufacturers, some try to actively stop rooting, new version/features breaking things, etc...

If you want to be on the safe-side of bootlooping or soft/hard-bricking : stay on latest stock firmware for your device, keep bootloader locked (/relock) and do NOT root.

If you still want to keep root then you get to be the tester (and can even help the dev by reporting issues with a maximum of info like config info and logs...). Just make sure you have a custom recovery installed (e.g.: TWRP) and use it to keep nandroid backups, look for the module's (or root app's/mod's/...) topic here on XDA and go through to find if there is no issue reported with your device or configuration, then try to install, always one at a time with reboots and testing in-between.

And most of all : KEEP CALM & BE READY TO FACTORY RESET AGAIN & AGAIN IF NEEDED (if you're not: unroot).

YouTube Vanced module works perfectly for me on my Pixel 1 on Pie, I don't know for ad block as I don't use it.

P.S.: Oh and I almost forgot to mention that if you're going to install Magisk modules, it's usually a good idea to install the "Magisk Manager for Recovery Mode" module first, so that you can uninstall specific modules from recovery if they cause bootloops. Here's this module's XDA topic : https://xdaforums.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
[Magisk] juch11111:
I've been denied permissions to the camera for all applications except the stock camera app.

There is still no flash support (pictures).

Version 17.2 Magisk did not help either.

[IMG="flash crash 1"]https://imgur.com/a/oRPQ0IG[/IMG]

[IMG="flash crash 2"]https://imgur.com/a/LI0oGS0[/IMG]

[IMG="flash crash 3"]https://imgur.com/a/4IP1oBT[/IMG]

Is anyone able to help?
[Magisk] evansourav:
Increased the Buffer Size + Un-installed Greenify still..................... :eek:

I am tired
[Magisk] pleclair:
Well, actually, I patched the boot.img, rebooted, and when I clicked on the Magisk icon, magisk told me it would automatically download the manager for me.

But I also tried to download it manually, I have the Magisk Manager 6.00, which I believe is the latest one, isn't it? I got it from the official source, not unofficial.

---------- Post added at 05:40 PM ---------- Previous post was at 05:35 PM ----------

I thought to make an app run as system app, all you needed to do was move the directory from /data/app to /system/app, am I not right? I did that in an adb shell inside recovery, and it worked for me. Is there anything else I should know?
[Magisk] Fif_:
Yes, you could move the app to /system/priv-apps (not apps, Greenify needs to be a privileged app I think), but then your /system would be modified and your OTAs would be gone... That's why the Systemizer and Greenify modules exist.
[Magisk] pleclair:
Oh ok, I see!

But in my case, I don't really care, since I disabled the OTAs. I flashed the russian mod of the lem6 firmware, and they are disabled, since it takes a toll on the battery, and apparently the adupsfota process isn't exactly safe for these chinese devices.

And I was not talking about greenify either. I moved WatchDroid Assistant from /data/app to /system/app, so the app runs in fullscreen, since it's a round smartwatch app, and looks better if it runs fullscreen, instead of in square mode. I let the watch in square mode, since the other android apps I installed doesn't fit nicely in fullscreen. I'm missing parts of the UI.

I'm just curious however, what would be the difference using systemizer to move greenify to system, as opposed to moving it manually to priv-app? I'm not quite familiar with how magisk and the systemless-ly thing works.
[Magisk] Fif_:
Magisk makes the systemized app appear in /system/*apps without ever touching /system. It uses bind mounts, which is a way to make files and directories appear at multiple places without changing their actual physical locations.
[Magisk] uLove:
Security Improvment and Fix Slow working

Hi
[MENTION=4470081]topjohnwu[/MENTION]

I use magisk 17.1 with 6.0.0(147) apk.

Please add Tapjaking protection and Exploit Blocker, i saw some apps automatic grant root permisson. but i cant remmber apps name:(

And another thing when i use magisk root permisson in software like Mix plorer,when i do a transfer or deleting and ... in root partition, magisk periform slow,please fix.

Before i use magisk 17.1 i use 16.4 i was uninstall and install 17.1.

Sorry for bad english.

Best regard