yashsingh1/xdaforums huggingface dataset:
[Magisk] rzwinston:
[/COLOR]I tried latest Magisk 20.1 on Htc M8 Viper 6.1 rom but double tap wake up screen doesnt work.

As well Total Commander: root funkcion dissabled, hanging comand (for ext sd card).With SuperSu all works except new version Youtube background play therefore I tried Magisk instead SuperSu and Xposed.

Any fix?
[Magisk] Tenshii23:
I have a problem with my bank apps.

It worked perfect until a couple of weeks ago. Seem's that now detect root somehow.

The apps are Caixabank pay and Caixabank sign.

I have an OP3 with latest Magisk Canary installed. Safety pass OK (2 green) and others apps that detect root (Pokemon Go for example) works perfect.

Any suggestion?

Thanks.
[Magisk] Ch3vr0n:
The fix? Total commander needs to update their app and not hardcode su binary locations. TC hasn't been updated since october 2018. DT2W is a kernal issue, not a magisk one
[Magisk] rzwinston:
Screen double tap wake- not working after magisk instaled

I tried latest Magisk 20.1 on Htc M8 Viper 6.1 rom but double tap wake up screen doesnt work.

As well Total Commander: root funkcion dissabled, hanging comand (for ext sd card).With SuperSu all works except new version Youtube background play therefore I tried Magisk instead SuperSu and Xposed.

Any fix?

I am sorry thats double post and I cant delete it....
[Magisk] lordlord6:
Xiaomi

I can not update magisk and magisk manager on my xiaomi mi max 2.

It says magisk has been refused superuser rights (translation),

I have link2sd which has super user rights.

And reboot and enter twrp and i try to install from there. And again nothing.

Help please?
[Magisk] PoochyX:
You should revert to stock

([emoji3590]09-09-18[emoji3590])
[Magisk] lordlord6:
You mean change the system?

In the previous update i just update magisk and magisk manager from screen like normal app.

When i starts the instalation of magic manager it says - that some zip package is needed.

So when i try to download it says

There has been problem with the analysis of the package (translation).

Help please?
[Magisk] ktmom:
If you moved Magisk manager to adoptable storage, it needs to be in internal storage.

You should look at/ post logs when troubleshooting install issues.

Doing a complete removal may help in your case. Take a look here.
[Magisk] lordlord6:
1. When i try to install via app,it says

- there has been problem with analysing the package.

2. When i download via this web page, on my downloads folder,

Two magic manager appear, two icons, then when i try to finish the install, it says it need zip file, then it says

Magic has been refused superuser rights.

3. When i reboot, enter twrp

Try to install it says some error too.

Where i can find this logs on my smartphone?

Do i need to be connected to the computer?
[Magisk] ktmom:
Is your Magisk manager hidden? If so, unhide it.

Don't try to describe what the logs say, the actual logs are more informative.
[Magisk] lordlord6:
There was a problem while parsing the package". If you see this message while trying to update the Manager, go to the app settings and choose to "Restore Magisk Manager". The new Manager release will be downloaded and installed with the regular package name and you'll just have to rehide the Manager again afterwards.

This was the solution. For everyone.

Thank you.

Where i can find logs?
[Magisk] martyfender:
That problem has been fixed in the Canary build, at least for me, for some time. Logs are in /cache/magisk.log. If you flashed in twrp, it is in /cache/recovery/last_log.

If you flashed from the Magisk Manager direct install method, there is a button in the upper right of the window where you can save the install log to the download folder.

---------- Post added at 05:32 PM ---------- Previous post was at 05:14 PM ----------

TC has been updated several times since then if you signed up for the beta channel on the Playstore. V3.0 b12 was released on 10/14/19. I did have previous problems with it, but not on the latest betas with the Canary builds of Magisk.

I'm not sure if it is still hardcoded, or not, in the last few betas? I have been on the TC betas for several years now. Maybe hardcoding is why I sometimes loose root with TC, especially after updating Magisk to a new version. When this happens it needs to be re-authenticated. This also happens with Apps2SD, Kernel Adiutor and a few other apps. This has happened for several years with Magisk on my Nextbook Ares 8A, Android 6 devices, but I don't believe it has occurred on my new, Onn 8 Android 9 tablet. I feel like it may have something to do with the magisk.db.
[Magisk] ktmom:
Asking for help/reporting bugs
[Magisk] Sid220:
Hi all, i'm running Magisk on my Poco F1 and it started to deny root permissions even if i toggled "grant" in permission.

It started when i uninstalled then re-installed Adaway, since then i tried to uninstall then reinstall Magisk with wipe dalvik cache but not solved the problem.

Every app i try to have root permission with (terminal emulator, total commander, link2sd) gets "denied superuser permission".

Anyone could help? Running latest stable for both Magisk and Manager

EDIT: installed Magisk Canary and fixed it
[Magisk] MrEzzzkiel:
Hidden Magisk boot after restart

Hi guys. Does anyone know how to fix hidden Magisk booting after restart? I've just flashed a new rom after using the old one for 6 months and I never experienced this with the other rom.

It just started out of the blue.
[Magisk] x0acake:
No apps after reboot

I'm trying to install YouTube Vanced and ViPER4Android FX. Installation succeeds but there are no new apps in the drawer.

YouTube did not come preinstalled in this ROM. So there's no updates to roll back or app to disable. But maybe there's something leftover from the previous ROM? I did a full wipe with TWRP.

I've attached the install log, but sadly can't provide the magisk/boot log because saving the log file results in a 0bytes .log file despite magisk manager showing the log contents. But there are no errors in the log, no permission issues, nothing that would indicate an error. (Can someone tell me where Magisk stores its actual logs so I can adb pull it if necessary).

The contents of /system/app:

Logcat:

Trying to manually install Youtube.apk results in:

Not exactly sure what this means (am I missing certs)? But resigning the APK per these instructions, and retrying install results a successful install and the app appears:

But running the app results in a crash with:

Clearly I'm not supposed to be running this as a userapp, but it's the only way I can get it to install. I've also tried Viper with similar results (installation successful, directories created in system/priv-app, but no new apps installed). Manually installing them results in crashes. My certificates list looks pretty nice and fat. So what's going on here, what to try next?
[Magisk] zgfg:
Unzip the Vanced modul (it should be in Downloads after its installation from Magisk Manager), you will find there the Vanced apk.

Install that apk, not YT apk.

And in Playstore disable auto-updating for YT, otherwise Playstore will 'update' and override Vanced

For V4A make sure it is supported by your device/ROM. Maybe you must also manually install the front-end apk, I don't know about that module (it is not supported by EMUI 8/9, hence did not try myself - only very long ago with Nougat and without Magisk)
[Magisk] pc boy:
Hi everyone

I got a couple of banking apps on my phone all of which wont run if they know that your phone is rooted. I have hidden root from all of them using magisk hide but one app - which is in fact the latest version of a banking app - sees root even though I have selected it in magisk hide. the others still work fine and cant see root. Is it related to magisk or the banking app or something else? Any help is appreciated.
[Magisk] x0acake:
Thanks but there's only a single .apk in the zip file called 'Youtube.apk' , and it's the same one I tried installing earlier. I have since done a full wipe of the internal storage and reformat, reinstalled the ROM and it still says "Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]". If I install with file manager, it says "App not installed." Only way to install is by re-signing it, but then it crashes when I run it.

Disabled auto-update.

Disabled PlayProtect

YouTube was not preinstalled on the ROM so nothing to roll back or disable.
[Magisk] zgfg:
Sorry, cannot follow you about wiping Internal memory and reinstalling ROM, this is your device and ROM specific, not common to Magisk and this thread

Generally, as long as there is no brick and Magisk is active, modules can be installed and uninstalled (best way) through Magisk Manager, Modules tab.

Magisk itself can be uninstalled from Magisk Manager and it also properly uninstalls all modules.

As that, wiping and reinstalling the ROM is not needed

Finally, there is also the XDA thread for Vanced, you can discuss its specific issues there
[Magisk] ktmom:
Magisk and MagiskHide Installation and Troubleshooting guide: Hiding root from apps
[Magisk] pc boy:
Thanks bro, But like I said, I have no problems with 3 or 4 apps checking root state, which means I'm doing fine in adding apps to hide list. I just have problem with one app that sees root access in my phone although I have added it to hide list and also renamed magisk to a different package name.
[Magisk] ktmom:
Then you didn't read the linked page, and the pages linked in that page carefully.

At any rate, it's a cat and mouse game.
[Magisk] Walden0:
Moderator Alert!

Promoting Lucky patcher and apps as such aren't allowed on XDA as it is considered a warez. It is understandable that the users only want to help others and not every time the usage of LP is causing harm to the original developer whose apk is being patched. But it opens the door for the other things that can and do cause harm to the developers. Thus making other members download and use it is not permitted on XDA.

Please cooperate.
[Magisk] cognitivedissonance:
I'm pretty sure that Schwab Mobile is detecting root for me. The app runs but tells me my username or password is incorrect when I enter it. I confirmed that it's actually working properly, so I have to assume that's what it is. I've done some troubleshooting, but can't get it resolved.

Anyone else experiencing this behavior with Schwab?

---------- Post added at 09:01 AM ---------- Previous post was at 08:51 AM ----------

If I toggle OEM Unlocking, isn't it going to essentially do a factory reset? IIRC when I rooted my Pixel 2 XL and ran the command to OEM Unlock, it ran a factory reset immediately after.

Also, isn't OEM Unlocking needed in order to have TWRP installed?
[Magisk] Ch3vr0n:
The toggle only allows to unlock, it's the actual unlocking that forces the factory reset.
[Magisk] 0LDST4R:
A general question about " resetprop " ...

I know how to MODIFY or to ADD a value in a module ( common / system.prop ) to be read by resetprop - no problem so far. But what if i want to DELETE a whole existing entry? Is it even possible?

My device is very well maintained, daily ( official ) ROM updates, and i'm too lazy to modify my build.prop each time after updating.

Thanks in advance... :good:
[Magisk] Didgeridoohan:
Run the resetprop command with -h or --help, in a terminal emulator, and you'll find what commands are available.

(Yes, it's possible)
[Magisk] 0LDST4R:
Answer in light speed - thanks. Will try it. :cool:
[Magisk] jcmm11:
Note that if you create an entry in common/system.prop of the form:

prop=

(With nothing following the =) you'll have a prop with a null value. Practical result is the same as deleting it.
[Magisk] Shaftamle:
I'm gonna assume that Google did something on the back end to break Google Pay? I can't do contactless payments as of 3 days ago. Anyone else?

DU 9.0
[Magisk] Fry-kun:
I keep seeing Magisk open up twice after I reboot the phone and log in. It's there a fix coming for this weird behavior?
[Magisk] martyfender:
If you are on the stable build, that was fixed some time ago in the Canary builds.
[Magisk] Fry-kun:
Yeah, I'm on stable.. I guess I'll wait around for it to get updated, don't want to mess with alpha/beta track unless necessary
[Magisk] Atharkhan101:
The latest Magisk version is not supporting the root hide for following apps:

1. HDFC bank

2. Google Pay
[Magisk] JudgeDread11:
What you probably want to say is; "I can't get Magisk hide to work with HDFC bank and Google pay."

And then you will get the reply that has been posted many many times before for similar questions.

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
[Magisk] rick1409:
Please need help, I am using miui.eu rom on Violet but few apps which needs root Access are not detecting Magisk even though i have done a coean installation. Can anybody help me
[Magisk] zgfg:
Again, pls read the guide/instructions, link in the post one before yours, posted an hour earlier
[Magisk] ktmom:
Try the canary build.
[Magisk] 0LDST4R:
Good tip. Thanks! :svetius:
[Magisk] andrew_yousry:
yes I did that and still application shows same message

---------- Post added at 10:25 PM ---------- Previous post was at 10:20 PM ----------

actually I tried to do reset/ format userdata, reinstalled software with bootloader locked, I checked application was working in both locked & unlocked bootloader states.

it was working even after installing magisk, it only detected root after installing the modules I mentioned in my first post
[Magisk] mbk17:
I restarted my phone and it automatically updated OTA December on my Pixel 3A XL(going to remove auto updates for the future). I tried patching the new stock boot through magisk and flashing it via flashboot but it just gives me the Google logo and I have to reflash stock to get my phone to boot again. Currently no TWRP support for Android 10 for this device. Is there any way I can get magisk and not have to wipe?

Thanks
[Magisk] Atharkhan101:
Yes
[Magisk] Poor Grammar:
Apps force closing...
[Magisk] JudgeDread11:
That is all the information we need, thank you.
[Magisk] Didgeridoohan:
Possibly a Magisk module not compatible with the update that is causing issues. That's a very common cause for this kind of issue...

There's a few ways of getting around this and removing the troublesome module. Foremost being the built-in adb command to uninstall all modules, or using a boot image patched to always have Core Only Mode enabled (that'll soon be a feature in Magisk, but until then you can build your own or find someone that's already done it for your device). Some more details can be found here:

https://didgeridoohan.com/magisk/Magisk#hn_Disablinguninstalling_modules_manually

Taking a look in your device's forum might also be a good idea (especially if you want to go the Core Only boot image route).
[Magisk] Didgeridoohan:
Possible solutions:

https://didgeridoohan.com/magisk/Magisk#hn_Apps_are_force_closing
[Magisk] stormy1777:
[MENTION=4668495]wilsonhlacerda[/MENTION] [MENTION=9248375]lividhen99[/MENTION], all, thanks, quick report back. I mis-understood the "detach" module, turns out i already HAD the detach.txt on the sd-card from prior attempts.. all had to do install the detach module, then stop using sudohide completely (to hide youtube), and blacklist the playstore in EdXposed, then in Magisk the safetynet passes fine. So far, did not need to schedule detach, seems to holding up, this is on Android 9. Thanks all for the support, hopefully it helps someone (as lost as i originally was :).
[Magisk] Dunge2:
I'm having a similar problem with Pixel 2.

Had the November update with Magisk 20.1 and no issue.

I flashed the December firmware the same way I've done a dozen times in the past. It rebooted in system correctly. Then I booted in TWRP, and flashed both TWRP and Magisk (latest) and wiped Dalvik cache and selected reboot to system as usual.

The phone try to boot to system (Google logo), but then reboot and start again and goes straight in TWRP. No matter what I do, it always boot back to TWRP. I tried reflashing TWRP/Magisk it doesn't help.

Reflashing the December firmware again works and I can use the phone without root/Magisk, but why does installing it break my system boot?
[Magisk] forumi0721:
https://play.google.com/store/apps/details?id=com.shinhan.sbanking

This app detect magisk (Canary, Stable, Beta).

Change package name doesn't work.

There's no way to specific package name?

I want to test change package name (Not a random package name)

When I uninstall only magisk manager apk, It works.

I think this app detect magisk, using package name pattern.
[Magisk] fvisagie:
Under the Settings menu you can customise package and app names.
[Magisk] matkwok:
hi, i placed a wrong script to /data/adb/post-fs-data.d and it causes boot loop to fastboot, i can only boot to system by flashing the stock boot.img but i can't access /data without root.

Anyone know how can i remove post-fs-data script or skip it? sorry, yet i don't want to wipe data on my pixel 4... many thanks if you have any advices [MENTION=4470081]topjohnwu[/MENTION]

Update: Solved!!

1. unpack magisk_patched.img

2. add a rc and script to remove /data/adb/post-fs-data.d/*

3. repack img and flash, boot with root again

reference: https://xdaforums.com/showpost.php?p=80991013&postcount=15
[Magisk] ktmom:
Did you read the response to the post you quoted?
[Magisk] mbk17:
Thanks for the suggestion I tried running the command got the following:

/system/bin/sh: adb: inaccessible or not found

There is no core only mode patched image in the forums for the 3A XL. I believe I did see some in the 3A forums.

EDIT: Found a patched image.
[Magisk] ktmom:
Have you booted to recovery and used adb shell?
[Magisk] matkwok:
yes, no device found in recovery mode
[Magisk] ktmom:
That sounds like a driver, cable or USB port issue recognizing your device in ADB.
[Magisk] matkwok:
i can use adb shell when boot to stock, but can't access /data as permission denied
[Magisk] Dunge2:
Yes thank you. The faulty module was "Active Edge Mod for Pixel devices".
[Magisk] mbk17:
Was able to install magisk on Android Q. However, Youtube Vanced & Viper4Android were succesfully installed but the applications are no where to found. Furthermore, I tried uninstalling those modules and it said it would be removed upon rebooting, but the modules still remain.

Anyone have any suggestions?

EDIT: Solution, core only mode was on. Turned it off and everything is good.
[Magisk] bender3019:
Installation failed

I keep getting

! Unsupported/unknown image format

! Installation failed

when trying to patch a boot image.

I'm on a Google Pixel 3a with Android 10 with bootloader unlocked and latest version of Magisk Manager. Downloaded OTA Zip directly from google to my PC, unzipped, transferred the payload.bin file to phone storage. I don't know what I'm doing wrong to get these errors, Ive searched the forums and found nothing on this issue. Have tried several OTA images, changed .bin to .img and tried using a canary build of Magisk all with the same results.
[Magisk] andrea0807:
I have a problem on my xiaomi mi 8.

Every time I update to the latest weekly release of the rom xiaomi.eu, I also flash magisk canary from recovery, but magisk does not install!

When I restart I don't have root access.

I always have to go back to recovery, uninstall magisk with the uninstaller and reinstall magisk version 19.5. Only this version is installed.

Then when I restart my smartphone I can update magisk via the magisk manager app. Why is this happening? It's very annoying, every time I lose all installed modules.

I use Mauronofrio's recovery twrp 3.3.1-2
[Magisk] Badger50:
Instead of using the OTA file, try using the coinciding factory image, pull the boot.img out of the image.zip, and try patching that with magisk :good:
[Magisk] atulclassic:
not able to use standard chartered bank application after updating the app from play store

using magisk 20.1

can anyone help
[Magisk] zgfg:
OMG, every second post is the same/similar.

Please, scroll back, it has been answered/discussed zillion times.

You can also search in the thread for e.g. bank

Need to read Magisk guide, about the tips to hide root for a particular app
[Magisk] BostonDan:
So I'm having a problem. I updated my Pixel 3XL with the December Security Patch. Once done, I copied the boot.img to my phone and patched the file using Magisk Manager. I then copied the Magisk patched boot file back to my computer and fastboot flashed the boot to my phone (both slots).

When I boot my phone, it boots but Magisk says that Magisk is not installed. If I go into terminal and try to use superuser (su command), my phone returns 'no dameon is currently running'). It seems that Magisk is either blocked somewhere or it does not fully install. I have tried this repeatedly with the same results.

Any help is greatly appreciated.

Cheers,

B.D.
[Magisk] bender3019:
Thank you I knew I was doing something stupid being this is my first time with Magisk, but I still have the same problem. Got the factory image and tried patching the bootloader image file and have to same errors. Am I missing some sort of common knowledge step that's not described anywhere?
[Magisk] ktmom:
Are you patching the boot.img? Not bootloader.

The bootloader.img will be at the root of the factory image zip. There is a second zip file which you need to open to get to the boot.img.
[Magisk] bender3019:
There is no boot.img in the Factory Image Zip file, only a bootloader image file. Is boot.img located inside the bootloader image file or the much larger image file also located in the zip and if so what would I use to view/extract this?
[Magisk] Badger50:
You have to extract the secondary image.zip file as well. That's where the boot.img resides :good:
[Magisk] bender3019:
YES, thank you, I found it. I kept thinking that was just the original zip file that I had extracted after downloading. Didn't realize there was a Zip within a Zip. Sometimes I can be really smart and sometimes I can be really dumb.
[Magisk] Badger50:
I definitely know the feeling on the smart/dumb thingy! ???
[Magisk] jcmm11:
Not sure what to tell you. Mine updated fine. I am, however, using the latest Canary. You may want to try wiping the contents of /data/adb/ (in effect removing Magisk) and then installing from scratch, in case there's a problem with the magisk.db

Since normally you'd need root to delete those try this one, rather than trying to boot core-only mode (which I see you tried) https://xdaforums.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867/post81091695
[Magisk] AquilaDroid:
I've been having an issue since installing the December factory OTA on Pixel 3 using the same procedure as the previous month. Here's a link to my post in a Pixel 3 forum: https://xdaforums.com/showpost.php?p=81194245&postcount=44

Magisk is stuck in "Core only mode enabled" now and I'm convinced that the problem is not being able to remove/disable Magisk modules (7 installed - Audio Compat. Patch, AML, Call Recorder, Systemless Hosts, Universal GMS Doze, V4A FX, Substratum). I've tried to remove them via Magisk Manager get the message "Module will be removed at next reboot!", but it never gets rid of them. I tried ".\adb wait-for-device shell magisk --remove-modules" several times, it runs, device reboots but modules are still there.

This is all after having a problem with the original install (possibly caused but a bad module - see post above for details).

Quoting from my post on the P3 forum: "After flashing Image-newpixel3.img it shows "Magisk is installed" but always in "(Core only mode enabled)". When there and clicking on "Install" it has the options to "Download Zip Only", "Select and Patch a File", "Direct Install" (Recommended) and Install to Inactive Slot (After OTA). When I click on "Direct Install" the result is back to "Not Installed" with options of "D/L Zip" and "Patch a File"." What does the "Install to Inactive Slot (After OTA)" do?

Sure wish TWRP was available <G>! This would have been resolved days ago.

Any suggestions would be appreciated before I start over (I'd love suggestions on what to do in that case). Thanks for any help provided.
[Magisk] ktmom:
Responded in linked thread.