yashsingh1/xdaforums huggingface dataset:
[Magisk] wolverine978645:
Can't load any Magisk Modules

I got new OnePlus7 pro and I updated it to OOS 9.5.9 with help of Oxygen updater. Have TWRP recovery and Magisk root. Trying to install Youtube Vanced and other modules. Installed various Magisk modules but the apps don't appear even after rebooting. I wonder what I may be doing wrong?

Screenshots:

https__://imgur(dot)com/a/JyaKHI3

I appreciate any help in this regard.

Thanks.
[Magisk] guest4711:
Not to forget that the old kernel version required for S II (i9100) does not support the required functionality for MagiskHide, e.g. MountNameSpace support.
[Magisk] zgfg:
For Vanced, you must uninstall YT app and disable auto-updating of YT in Playstore (regular YT will overwrite Vanced).

BusyBox does not provide any visible app, but you can check from Root or BusyBox Checker was it installed successfully
[Magisk] wolverine978645:
Thank you for the reply.

I just checked busy box via busy box checker. It says I have it installed. Also debloater is working.

So at this moment it seems modules which have GUI app, are missing. I.e. YouTube vanced, app systemizer, terminal modifications.

YouTube was uninstalled. It wasn't system app surprisingly. I posted this issue on vanced forum as well. They suggested going into root system app YouTube directory. And installing app there. I'm not sure how to do that via magisk or twrp. Is there any guide for that?
[Magisk] dope77:
i'm facing those 2 problems on my j6+ (j610f) and they're really annoying,

1- flashing any version of magisk breaks the locksreen,if i put any lock type and attempt to unlock the phone,i will get incorrect password (i'm typing the password correctly)+ rebooting phone while there's a lock would get the phone in endless loop (deleting locksetting.db from twrp file manager fixes the bootloop)

2-whenever i reboot the phone,phone boots without systemui (check the pic below),no statusbar/navbar also since i can't put a lock for the screen,the only way to prevent someone from accessing the device if rebooted is the simlock,which also doesnt work(using third party lockscreen when phone is turned on but it takes sometime to work after reboot,also doesnt work if sustemui isn't working). anyway the only fix i found for the systemui issue was going to magisk hide ,disable then enable hiding from systemui,which will force stop it and then systemui and simlock would work

are there any logs that would help detect the issue? also any suggestions on how to fix this?
[Magisk] martyfender:
App Systemizer does not have a gui with an icon in your app drawer. You have to have a terminal emulator installed to enter it's commands. For that matter, most modules that I have used, don't have a gui to interact with.
[Magisk] brajesh.sharma87:
I tried with hiding the magisk manager and succeeded with the result. Now I dont see the restore magisk manager option. I searched the thread and found no info. Someone please guide me.
[Magisk] wolverine978645:
I finally got Youtube vanced working. I installed it through their root installation method. I was missing the installation zip files from their gdrive link. I just tried installing with the apk alone. Magisk Vanced didn't work but I dont care at least at this moment. Other modules, if I have, will deal individually,
[Magisk] jenslody:
Do I understand correctly, that you have system-ui on the hide list ?

If yes, are there other system-apps on it (except com.google.android.gms.*) ?

If yes again, that's the culprit.

Only a bare minimum of processes should be there, and adding random system services can make the device unstable.

Besides this, logs are always a good idea to be able to find an issue.
[Magisk] Ben100000000:
Hello, I tried to install the Magisk 19.3 on my Xiaomi Redmi Note 7 PRO (Violet) with MIUI 10.3.10.0 India and bootloader unlocked, but just after installing the TWRP the magisk zip 19.3 my device loads up the bootanimation and then restarts and sends me to TWRP, I already tried even patching the boot.img from the app magisk manager more current stable and the same thing keeps happening, just noticed that the patched boot.img was left with 16 mb in size and the original weighs 65 mb, as Can I solve this problem? since I would like to modify some apps of the system and nevertheless I can not. Now if I install the xiaomi.eu 10.3.9.0 from china if it grabs me the root, but at the time of deleting apps from the specific system of the priv-app folder in / system it does not let me, even with root, this I tried both from TWRP and from the root of magisk in the rom xiaomi.eu. What is this about?
[Magisk] zgfg:
Uninstall Manager (repackaged MM).

Reboot and install Magisk Manager.

Reboot again (reboots maybe not necessary).

Magisk Hide, Superuser, Modules, etc., shall remain.
[Magisk] pcportugal:
Hi everyone,

Just updated my VTR-L09C432 (Huawei P10) to Android Pie (9.0.1). And of course I want Magisk, so extracted the ramdisk_recovery.img and patched with magisk manager.

The flashed with fastboot and booted with [VOL+] + [Power], took a while, longer than I was used to but it booted. In Magisk manager everything was ok.

But some things are weird, everything displayed on left and right margins won't answer/react, from top to bottom.

Even tried canary channel and the problem still remains. Anyone else with this (unfairly) infamous phone having this issue?

Details:

Model: VTR-L09C432

Firmware: C432E1R1P9B185

Andorid version: 9.0.1

Magisk Manager version: 7.3.3

Magisk : 19.3

Install method: recovery image patch

If still a log is required, please let me know what logs are needed regarding this kind of issue.

Thanks
[Magisk] Dude_Virus:
Hi I am not sure if this has been reported earlier or not.

If I select "reboot to recovery" from inside magisk, the gui states "factory data reset" . Haven't tried the other options.
[Magisk] zgfg:
When reporting a problem (specially such a specific issue, this option is available since ages and generally works) please provide detailed info about your phone and firmware, Magisk and MM version.

You also need to provide MM log (you will need MM Canary Debug version - Google for XDA Magisk Canary, install MM Canary debug from its OP post #1)
[Magisk] Dude_Virus:
Well I suspect it's more of a MM gui glitch than a device specific issue. Instead of saying booting to recovery it says factory data reset. It's performing the action correctly though and boots to twrp.

Maybe once I have the time to get the logs I may collect them. Thanks for the reply though.
[Magisk] zgfg:
This is not a beta sw, it was long ago polished.

Usually when something does not work it is specific issue on a specific phone, with a specific firmware, etc

Understood that you would need time for logs, but to provide info about the phone, firmware, Magisk and MM version should not be a problem.

It's a generic thread, for all Android makes, models, with various stock or custom firmwarres, from Android 4 till 9, etc.

Usually some thing works for 99+% of users, and doesn't only for 1% or less, for a specific platform/environment

If users don't mind to provide basic info, then why bothering to report (devs cannot help and fix without details) - if only to ask if something similar was previously reported, there is also a Search box on the top-right ..

Attached screenshot showing how it should look (beleiving it works correctly for 99% of users).

If you read a bit previous posts, you will find devs answering - no logs, no problem.

Without even an info about environment, they probably don't mind to read at all :)
[Magisk] Dude_Virus:
Magisk and MM are on the latest stable version. The reason I am stating this is not a device specific issue because same GUI incorrect text I can see on 3 devices 2 different OP6 and OP7 pro. That screenshot which you are displaying is not the issue that I am reporting. That screen is fine, but when you click 9n Reboot to Recovery, the dialog box that comes up shows the text Factory Reset instead of Reboot to Recovery. Please click on Reboot to Recovery and check what it shows.
[Magisk] Didgeridoohan:
[MENTION=437363]Dude_Virus[/MENTION] [MENTION=7786725]zgfg[/MENTION]

https://github.com/topjohnwu/Magisk/commit/b1e63f0f140e9ef88e7bf19bfb266c95e4ae335d
[Magisk] deentky:
I'm using Samsung Galaxy S3. I have TWRP 3.3.0 installed. I installed Magisk through TWRP. That's my first time with Magisk. Before installing a new ROM, I do format data & advanced wipe (everything except external sd card and usb otg). So my stupid question is, do I need to uninstall Magisk (with Magisk-uninstaller-20190604.zip) before I do my routine? or maybe format and wipe will remove Magisk anyway?
[Magisk] zackkiara2013:
[MENTION=268073]top[/MENTION]johnwu.. Why safetynet show 'the respond is invalid' n I can't use banking app coz my banking app know root phone.. I have hide but same... [IMG="magisk safetynet problem"]https://ibb.co/CBMB2r4[/IMG]
[Magisk] iDreamliner:
Ok I'm new with rooting android marshmallow so I need some help with this.

I have a full stock Note 5 ( N920C ) done nothing so far with rooting it but to get this work it should be kinda rooted to open the BL and have TWRP installed but then I read it should be back to full stock.

So what's the walktrough I should do?

First full root it and after that restore it all back to stock or is there another way to get this installed?

My thought is:

Flash this using odin: CF Auto Root for Samsung Galaxy Note 5 SM-N920C

After that install TWRP recovery and then follow the steps in OP.

Is this the right way?

Hope someone can provide me the info what to do
[Magisk] jala9024:
Xposed

I think xposed break the game Again

---------- Post added at 01:19 PM ---------- Previous post was at 01:00 PM ----------

Is Pokemon Go new updates .39.0 working after flashed systemless xposed?

---------- Post added at 01:20 PM ---------- Previous post was at 01:19 PM ----------

Is Pokemon Go new updates .39.0 working after flashed systemless xposed?
[Magisk] WeirdSoup:
Hey, I found that some banking apps are detecting the Magisk itself! For example, the KBStar(https://www.kbstar.com/) banking app detects the Magisk so I can't run it normally. (Unmounting root via the manager app does not help, it still pops up a message "your device has been modified".)

I found a solution for this: install RootCloak "beta" version, add the app both the "Manage Apps" & "Native Root Detection" sections(this is why the beta version is needed), and add the keyword "magisk" using the "Manage Keywords".

I think this will prevent the app from detecting the magisk. Before that, I tried many things(unmounting root, just adding the app in RootCloak without editing the keywords, and disabling the xposed framework using the installer app, etc.), but all of those were useless. Only adding a keyword using RootCloak beta version takes effect.
[Magisk] gk1984:
Are you sure it's not detecting the Superuser app and not magisk? This is how the AT&T Uverse app detects root. Seems a hell of a lot easier than trying to check for certain exploits.
[Magisk] Illogi.xbone:
Only thing keeping me off root on my S7 is Pokemon go, only game my wife likes to play, hope you can get it working!
[Magisk] Hyflex:
I'm having three issues:

- Certain apps are detecting via safety net that my phone has a CTS profile mismatch.

- Certain apps are detecting Magisk Manager and Superuser apps.

- Certain apps are detecting BusyBox being installed.

How to I fix each of them?

With the first one is this because I'm using a custom ROM? Any way to use a custom ROM and still get around it?
[Magisk] Cyber Akuma:
I don't understand what "stock system and boot" is. I mean, I understand what the system and boot partitions are, but I don't understand what information, if any, will be erased if I restore them to stock.

Also, I am pretty sure I don't have xposed installed, but is there any way to check?
[Magisk] WeirdSoup:
Well I'm still testing it, it seems unstable and not always working as expected.
[Magisk] Captain_Throwback:
*sigh*

Please use search: http://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post68797308
[Magisk] Einheit-101:
MY PHONE WONT BOOT ANYMORE.

"fall through from normal boot mode"

What can i do? Droid Turbo XT1254.

€DIT:::: Re-flashed the stock boot that you automatically created (glad you implemented this!) and it works. Can i send you any file to fix that bug for the Droid Turbo?
[Magisk] Paxy:
MTK9520

Hi

For MTK9520 phone (like Zopo998) boot image location is:

/dev/block/platform/mtk-msdc.0/mmcblk0boot0
[Magisk] KaMyKaSii:
I have a MT6753 and mmcblk0boot0 block corresponds to preloader. Install something wrong there and go hard brick your device
[Magisk] Rayman96:
How about dd-ing 4096 kB and modding this image off the device?
[Magisk] Outlinez:
Right ive read instructions and searched the thread for multiple things but cant find any clear answer i have a completely untouched galaxy s7 do i need to root the phone first then follow the steps to unroot and flash magisk?
[Magisk] JudgeDread11:
There is a systemless BusyBox module in the collection of magisk modules thread that will add BusyBox to you system systemless. This should solve your issue. Did it for me at least. :)
[Magisk] davelangmaid:
No need to root first.
[Magisk] Outlinez:
thanks for the reply but just to be 100% clear i can follow instructions here without doing anything else prior to the phone then? might build up the courage to try this out tomorrow :good:
[Magisk] knipp21:
Just need to make sure the bootloader is unlocked
[Magisk] grep_i:
You don't have to root your device at all.

Just unlock bootloader and download right version TWRP for your device and use adb and fastboot to boot to custom recovery.

This way you won't have to install the custom recovery on your device but you can still use it.

When booted in custom recovery you can do as stated here in OP.
[Magisk] Dude_Virus:
Cool thanks....
[Magisk] jcmm11:
Wiping data will remove the files associated with Magisk (modules, settings, etc). When you flash any ROM the boot image that's included with the ROM replaces the existing one, which eliminates Magisk completely.

So no, in the situation you describe there's no reason to run the uninstaller.
[Magisk] xunholyx:
On an earlier Magisk build, I had BusyBox issues. I Installed this and it fixed it. It may work for you too if you think it's a BB problem. I'm not sure it is though, but it can't hurt to try
[Magisk] JudgeDread11:
U installing that BusyBox won't be systemless.
[Magisk] zgfg:
Interesting :)

When I click on Reboot to Recovery, display instantly darks out (rebooting) and I see no dialog box, pop-up, nothing (until Device is Booting and TWRP come out)

Btw, for Reboot and Reboot to Bootloader (they also work fine), I shortly see a pop-up at the bottom, displaying Restarting

Huawei P9, Oreo, Magisk Manager Canary (release) v7.3.3 (228)
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid

and

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] pcportugal:
Anyone?
[Magisk] dope77:
Systemui isn't on the hidelist, when systemui isn't working, i just toggle magisk hide on/off to force stop it so it'll work.

Also no system apps restricted. Only google related apps.

Anw i cleared data of systemui, it's not crashing anymore.

But which logs would help detect the issue with lockscreen? (flashing any version of magisk breaks the lockscreen and causes bootloop if lockscreen is enabled )
[Magisk] pcportugal:
Well, no one answered or the issue is new, but actually there's an answer that I can share, found by another user.

https://xdaforums.com/showpost.php?p=79336874&postcount=11

This is a post of thread discussing and to install Magisk on P10 with EMUI 9, and later a solution appeared for the "touch" issue.

Hope some dev can at least read this, the author of solution already posted this on an appropriate thread.
[Magisk] pnin:
Hi.

Been having a pretty frustrating issue on my new tablet, a Mi Pad 4. I'm currently running HavocOS 2.7 and fairly recent OpenGAPPS, rooted with latest stable Magisk (v19.3 with v7.3.2 Manager).

Now, I've been trying to setup Amip's ClockSync like I have ever done with no trouble on every device I have ever owned, but can't for the frigging daylights get it to work.

ClockSync needs root but I'm not being asked for it at any time so it just silently force closes. I looked for a way to expressly grant it before running ClockSync but couldn't find any. So I'm stuck... :confused:

What am I missing here? All help deeply appreciated.
[Magisk] guest4711:
You may add ClockSyn explicitly to table policies in magisk.db.

Either use an sqlite editor (e.g. the one from Mixplorer) or the sqlite functionality of magisk itself (magisk --sqlite "sql statement")
[Magisk] Suryo75:
how can you hide root from grab driver malaysia, many steps i used but still nothing, it always detects root
[Magisk] Homeless2:
Is anyone using Magiskhide with SAP concur? I have an issue where concur will detect that my device is rooted and not start though it is enabled in magiskhide. I have to go into terminal and disable/enable magiskhide in order for it to work properly. Just wanted to see if anyone else had this issue. One thing to note is that magiskhide should be working properly as it passes safteynet checks before running the disable/enable commands
[Magisk] HTC_FUZE:
Yes, same issue with sap ui.
[Magisk] paarnoutse:
When:

a) SAP Concur is added to Hidelist, and

b) Magisk Manager is hided (random package name)

then SAP Concur always runs OK for me (without the need - eg. after a reboot - to regularly disable/enable magiskhide).
[Magisk] maskotpatriot:
fix install magisk in lineage 14.1 unofficial redmi note 5a prime magisk is only active in core mode, is there a solution?
[Magisk] elimiriel:
Report: This carrier-depending pay app used in S.Korea detects most recent stable build of Magisk. I'm not a developer, so I can only report this. And I feel huge thanks to your work.
[Magisk] Syoenth:
Installing Magisk J6+

I'm trying to install Magisk on a J6+ (J610G) TWRP say it installed but when the system is running I open the Magisk Manager and it says Magisk isn't installed, can anyone help me? I'm attaching the log of twrp installation
[Magisk] dope77:
That's because of defex security blocking magisk. I have j6+ and I'm telling u rooting this device is an extreme pain in the a**.

I jave j610f running pie, rooted it after a senior member removed defex from the kernel. But u should know that flashing magisk breaks the lockscreen (lockscreen no longer works) and causes bootloops if u set a lock for your phone.

Is your lockscreen still working after flashing magisk? Even if maigsk didn't work
[Magisk] Syoenth:
I didn't setup a lockscreen, I'm about to downgrade to Oreo and flash Magisk
[Magisk] JudgeDread11:
No need to be a developer, you can still help by collecting logs. First make sure everything is setup correct. There are some good food on how to stop and collect logs. Looks are posted here regularly so it shouldn't be hard to find
[Magisk] elimiriel:
I thought I have to see logcat and confused, but forgot about magisk log. Here're logcats grapped by the rom I'm using(team Venom's bug report tool), and magisk logs from /cache. Note that magisk log is recorded after I changed the package name of the manager for my failed trying to hide root.(due to xda app cannot cancel attachments once added, so magisk.log is already included to logs.zip)

System: HTC 10 running Android 8.0, Viper10 6.0.0 that is based on HTC stock rom, Cleanslate 3.7.13(linux kernel 3.18.63).

+other banking, pay, vaccine, etc apps are ok-CTS is ok with edxposed. only app named 'SK Pay' detects.

+edit: not only CTS, SafetyNet is OK
[Magisk] ajp_anton:
I have a problem with my Xperia XZ1 Compact with newer versions of Magisk. More specifically, the latest working version is 16.3.

Starting from 16.4, the camera does not work. It shows the live view, but it doesn't focus, the camera app gets stuck when trying to take a photo, and the phone has to be restarted. Other apps have the same problem: no focus, no photos, QR codes not recognized.

I've tried 19.3, 19.0, 18.1, 17.3, 16.7, 16.4, all of them have the exact same problem. 16.3 and 16.0 works fine.

What can I do to help narrow down the problem further?
[Magisk] vonDubenshire:
I hate to ask a repetitive sounding question since I have been rooting only the past month or two with my Pixel 3, but I have reformatted and changed ROMs and Kernels etc on my phone so much I feel I have learned a lot.

Here's one thing I have not quite seen explained:

Why \ how often am I going to need to toggle MagiskHide on and off? I see this referenced all over as a possible way to make a new app or change start to work, but other times I see people toggling it on and off ALL the time -- even after rebooting. Does Magisk not force MagiskHide to work as soon as you start up?

I really understand the point of a toggle after a change, or even a reboot and maybe another toggle on\off\on, but I don't quite understand why it is so commonly mentioned for so many things.
[Magisk] Didgeridoohan:
You should only every have to do that after a Magisk update, and even that should be relatively rare. Anything else is unintended and should likely be considered a bug.

There's a known bug where some users have to toggle Hide off and on after a reboot, but that should be taken care of in a future release.
[Magisk] andy356:
Every time I open Magisk Manager, the Downloads section is blank and the module list has to be downloaded again. Switching to other sections and then coming back to Downloads still shows the list. But the moment I swipe it away from recents, the repo cache is cleared and I have to wait for it to download the next time.

Am I the only one experiencing this or is it a known bug? Earlier versions definitely kept the cache even if the app was swiped away.
[Magisk] temych_p:
NFC not work After installing Magisk

After installing Magisk (16, 17, 18, 19,19.3, 19.4), the NFC immediately stops working. Android 8.1 stock, I do not put any programs. The bootloader is unlocked, installed TWRP. Phone - Asus max M1 pro 4/64.

After unstalling Magisk NFC is working.
[Magisk] Didgeridoohan:
[MENTION=6433025]duh1[/MENTION] Here's a thought on your old Netflix issue:

I recently had a troubleshooting session with a user that had issues with an app that would report that the bootloader was unlocked even though Magisk would successfully mask that state. Turned out that the app in question would look for the OEM Unlocking allowed option. Simply turning that off in Developer Options (not locking the bootloader again or anything like that) would let the app function again.

Worth a shot, I guess...
[Magisk] k4cperu:
On my Asus Zenphone 5Z (ZS620KL) first installation of magisk worked perfectly. Then I broke it with some mod and caused crashing to bootloader so I flashed stock rom. Unfortunately when I installed magisk on new flashed rom (but same as pervious original rom) I had find out that magisk manager behave like I had two magisk managers and magisk hide or magisk repacking did not work. When repacked manager didn't seen root or magisk lib. In log I had error like "could nod write to read-only database". While playing with terminal emulator I have find out, that "magisk --SQLite" crashes daemon, then "magisk --daemon" and "magiskhide --enable" restore full functionality of magisk, even when repacked, until next reboot. So I made script in /data/adb/service.d/ that autoruns above commands and magisk is working fine now. SafetyNet passes too.