yashsingh1/xdaforums huggingface dataset:
[Magisk] tera89:
Hello I tried to install magisk manager on my oneplus 2 but it dint work ... i had rooted my phone and running twrp recovery

i provide a log file regarding failed installation pls assist me

since i just wanna install x tether(usb tethering) tru magisk or Xposed(same dint work too cant install xposed framework) where my carrier block it and i dont want to pay pdanet+ just to use this usb tethering feature that rooted member can do it freely

thank you in advance
[Magisk] Didgeridoohan:
You were actually given the answer when the installation failed in the failure message:

Since you are already rooted, Magisk can't do it's thing... Take a look here for some tips on how to fix this:

https://didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
[Magisk] MightySashiman:
Hey all,

Can someone confirm UBS Swiss apps work please? (banking, access, twint). Since the update, all 3 detect root and refuse to work again. All 3 apps have been un installed, dalvik cache cleared from recovery, apps reinstalled, magisk hidden, and magisk manager itself is set as a renamed package. Apps used to not detect root with these settings. Has UBS figured out a new root tampering detection method?
[Magisk] tera89:
i already flash unSU and remove the supersu and tried install the magisk again same thing and same log happen

so basically i need to unroot my device and continue with magisk manager installation ???

even by ready the instruction provided still confused
[Magisk] guest4711:
Follow the description of the module:

Open a terminal window (aka shell) on your device. Enter su followed by props

u0_a64@android:/ $ su
root@android:/ # props

Loading... Please wait.

MagiskHide Props Config v4.0.3
by Didgeridoohan @ XDA Developers

===================================== Updating fingerprints list
=====================================
Checking connection.
No connection.

MagiskHide Props Config v4.0.3
by Didgeridoohan @ XDA Developers

===================================== Select an option below.
=====================================
1 - Edit device fingerprint (active)
2 - Device simulation
3 - Improved hiding (active)
4 - Edit MagiskHide props
5 - Add/edit custom props
6 - Delete prop values
7 - Script settings
8 - Collect logs
r - Reset all options/settings
b - Reboot device

See the module readme or the
support thread @ XDA for details.

Enter 'e' to exit:

Sorry, I meant fingerprint, not keyprint...
[Magisk] Didgeridoohan:
They're probably detecting the Magisk Manager, even when repackaged with a random name. It is almost impossible to completely hide the Manager, but [MENTION=4470081]topjohnwu[/MENTION] is working on a really cool solution that should be able to fully hide the Manager on Android Pie and above.

You can test by uninstalling the Manager and see if the apps still triggers.

It's not enough to just flash the unSU, you also have to (like the message says) restore a stock, untampered, boot image.
[Magisk] engineerchad:
I'll try again to upgrade and see if I can get a boot log on it but 20.0 upgrade from 19.3 on my Xiaomi Redmi Note 7 just won't boot. I have to downgrade or restore backup. I'll go thru the process again and edit to add a log if it catches it.
[Magisk] briandmiller:
S10 stuck in Boot

I rooted my S10 with magisk and it was working fine. I then installed TWRP and however I did that was not good. I then flashed the stock rom via Odin and got stock recovery back but now the phone is stuck in a loop. It powers up, gives the warning, shows the Samsung logo and then restarts. I have done factory reset and wiped cache but can't get past this. Please advise what I can do next. Thanks
[Magisk] tera89:
Actually i dont know what u mean by restore a stock.. i just unroot my device (bricked my phone) flash stock.. then flash twrp.. install magisk manager... Flash magisk 20. Then finally it works.. took 5 hours.. just to use tethering module and it doesnt work... Fml
[Magisk] vMAC:
So this still didn't' work. Here are all the things that I tried in case anyone else has this issue happen:

1) I changed the active boot slot via fastboot (tried both A and B since I didn't know which one it was switched to by Magisk.

2) I then downloaded the full firmware and took the boot.img from that and saved it over both slots in fastboot.

3) I then flashed the system.img and dtbo images in case those were causing issues.

4) Lastly I did the flash all with the -w removed from the file.

Strangely none of those worked still was getting the same error on the phone after rebooting.

Ultimately I had to hit the Factory Reset in Android Recovery......
[Magisk] dreams.sri:
[Noob Question] How to download from Magisk Module from GitHub Magisk Repo?

I am not sure if this is the right place to ask, sorry if it is not.

How to download from Magisk Module from GitHub Magisk Repo? For example, in the below github link of a Magisk Module: https://github.com/Magisk-Modules-Repo/Pix3lify > Which file exactly should I download? How to download?

Any help on it would be appreciated. :)
[Magisk] palmbeach05:
For the modules, you fork it to edit it for yourself, git clone it to build it yourself, or juat use magisk manager on your device to download the compiled and ready to install package.
[Magisk] briandmiller:
RESOLVED: I went into Odin again and flashed all 4 of the zip files instead of just AP and BL.
[Magisk] Progressive82:
Nobody can help me?
[Magisk] zgfg:
Did you search back to find link to instructions how to resolve bootloop and similar issues (like disabling modules first)?
[Magisk] Progressive82:
No, because I've never disabled modules during Magisk update and never encountered bootloop issue. I think this regards Magisk 20.0 version only.
[Magisk] XtraWater:
I red all posts since V20 appeared on stable channel. I think there re quite a bit similar issues reported from users. So far I didn't red a solution which worked. I don't know if the dev will check it. Would be nice to able to disable updates on magisk since it don't work anyways.
[Magisk] Ch3vr0n:
Updating works perfectly for me and many others
[Magisk] aseferfan:
installed magisk manager on my mi 9 lite ( boot loader unlocked, stock rom).

But I see no install option?
[Magisk] Ch3vr0n:
Because the apk itself can't install magisk on it's own. You need to flash the zip file first which installs the su binary and an up to date apk
[Magisk] B__B:
Or patch boot.IMG and flash it by fastboot
[Magisk] zgfg:
MM Settings, disable Check for updates
[Magisk] XtraWater:
I tried this. Update came. Still up. Then I cleared cache and data of MM, Uninstalled it, disabled WLAN and data and installed MM again. But MM won't install without internet connection. My idea was to disable 'check for updates' while there is no internet connection so I had to enable wlan to let MM install itself. I disabled WLAN again and started MM to disable 'check for updates'. As soon internet connecting was established again.... Booom... update available ;)

I guess I could run 'log dns request'. And block the addresses in adaway. But I leave it as it is for now....
[Magisk] jcmm11:
Choose the custom update channel and leave it blank. It'll keep saying 'checking for update' but it won't find anything.
[Magisk] martyfender:
You can download the magisk.zip and install it from the modules tab. To install Magisk Manager only, download the apk or extract it from the Magisk.zip and install it, like any Android app.
[Magisk] JerichoKru:
It seems like the current version of Magisk is breaking Fate GO again. I'm getting an error code 16882567 and it seems to be related.

Edit: Confirmed: uninstalled Magisk and it launched normally. I think it started on v20 (canary affected too)
[Magisk] XtraWater:
That was a good hint. I created a .json fle on my own server. Same magisk version number as installed. Now MM thinks latest version is installed.
[Magisk] doubtfire1:
hey all, im having a problem updating magisk manager.

im running magisk v18.1 and magisk manager 7.0.0

ive been trying to update through the magisk manager app, starting with getting 7.3.5, however when i press update and try install, it downloads and then doesnt do anything. no error message, nothing. so i got the latest manager apk from the thread and manually tried to install through file manager. the screen flashes black for a second and then does nothing again.

anyway afterr trying about ten times i juat got the new v20 magisk zip from the thread and intended to flash it from recovery and hoped it would come with the newest manager installed. however my recovery seems to be bung and just displays a black screen, not allowing me to do anything until i disconnect the battery. its too much work to try and fix that, so are there any other options i can take for updating?

i googled my problem and found people had suggested it could be because magisk hide is enabled in settings. so i went and disabled that and tried again and no luck.

im running android 5.0 if that matters.
[Magisk] martyfender:
I had the original Nextbook Ares 8, Which came with Android 5.0. 5.0 has a major memory leak which was subsequently improved considerably with 5.1 and 5.1.1, etc. 5.0 was horrid. A developer ported 5.1.1 from a newer revision of the device to the older 5.0 device. 5.1.1 made the device run very well in comparison to 5.0

Are there no updates for your device above 5.0?

Regardless, it appears you need to restore your rom, or at the very least, maybe factory resetting it will solve this. Of course, if you do this you will loose all userdata. What about TWRP backups, do you have any older ones you could restore? Finally, I don't believe you stated what device you have and of course, logs could be useful.

https://www.didgeridoohan.com/magisk/MagiskHelp

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] edimarcr:
In version 7.3.5 my bank application started to recognize root even with the "hide" and "hide magisk manager" features enabled.
[Magisk] ant0nwax:
thx, that was helpful, still not working

i chosen the fingerprint of my P9 7.0 cause i cannot chose 8.0 or shall i chose something else?

i add logcat with telekom string filter from the 25 seconds when magiskhide telekom app is started
[Magisk] oldbear3:
[MENTION=5993745]JudgeDread11[/MENTION] > I finally found a way this morning. There is an option in Magisk settings to change the Magisk Manager App Name.

It worked for me.

At the same time, I also cut the ADB superuser, and selected "Applications only" for the root. After my bank application initialized, I put this setting back to "Applications & ADB" and my bank app still works.

Hope that will help you.
[Magisk] NaabKing:
Hello,

so yesterday after some trouble (had to install Pixel Experience with ADB Sideload, cuz i literally had to Wipe everything in TWRP to get the ROM to boot) i managed to get Pixel Experience working. I'm using Xiaomi Mi 8 phone (if it helps).

Now, how do i get Magisk working? If i install Magisk Manager and click "Install" there, it won't complete the install, so i went to TWRP and flash it there (Magisk v20.zip), which was a mistake, since the ROM didn't boot again and i had to use ADB Sideload again.

When i was in MIUI, Magisk worked fine tho, so what am i doing wrong here?

PS: Do i have to wipe dalvik/cache after installing Magisk?
[Magisk] doubtfire1:
ah my bad just checked and i do actually have 5.1. just never upgraded to past 6 since i feel they changed a lot of settings and things i liked, wanted to keep it at 5. My phone is an Oppo F1S, A1601.

I think i forgot to say that i've updated magisk and what not before, and the recovery was running fine last time I went into it which was a fair few months ago now, so not sure what has happened since then that now its suddenly not working. I'd rather avoid having to fix the recovery if I can, cause when I rooted in the first place I remember it being a nightmare to figure out all the right stuff to download and get all the mediatek files and what not, and I dont have the laptop anymore that had all the stuff I used originally. would probably rather just get a new phone but its not a high priority atm anyway.

But i'll attach the log from magisk. Nothing there I can really make sense of that might be causing issues, then again I don't know too much about this stuff
[Magisk] palmbeach05:
I would think that would be fine. I'm just going off of personal experience here. My j5 is on los 16, but i have the fp for my device's stock 6.0.1 set. Everything is working fine.
[Magisk] mauro_cbc:
How to fix safetynet not passing?

My device: Meizu M2 Note, Lineage 14.1 by Moyster (build 25), Magisk 19.3 (tryed to update and got error, rollback to this).
[Magisk] zgfg:
So CTS is failing - please search in this thread for CTS (and device fingerprint). This is also described in Instructions (LOS custom ROM is not certified by Google)
[Magisk] aldyrifal75:
What happen if I replace boot.img patch magisk to boot.img original?
[Magisk] NaabKing:
hey, so i had the same problem, and some friendly dude helped me, here is the thread where i asked and what i did (what he told me to do):

https://xdaforums.com/mi-8/development/rom-pixel-experience-t3871932/post80565907#post80565907

You can see my latest post that actually my phne passes SafetyNet now.

PS: Be carefull since i have a different phone then you, so i can't tell you if sqlite will work on your phone or not, everything else should be the same i guess? Someone more knowledgeable should be able to confirm or deny this, maybe it was just specific for my device.
[Magisk] mauro_cbc:
I'll take a look, hope It work for me.

Actualy I'm not having any problem with this, but I think it's better to solve it...

Thanks!
[Magisk] palmbeach05:
You mean what happens when you replace a patched boot.img with a non patched boot.img? You lose root.
[Magisk] AndroTech:
Any help on this issue is appreciated.
[Magisk] martyfender:
Since you are passing basic integrity, you may be able to use MagiskHide Props Config Magisk module and apply a certified fingerprint which can pass cts profile, also. There is a documentation link in the thread which I highly recommend that you read before setting the module up in a terminal emulator. There is no guarantee that this will work well with all devices, though.
[Magisk] MightySashiman:
I can confirm that UBS apps (access, banking, twint) have a detection mechanism targeting magisk manager (even renamed). Maybe some hash/signature thing? Magisk needs virus/worm grade polymorphism/mutation stealthing. ?
[Magisk] Didgeridoohan:
It's coming:

https://twitter.com/topjohnwu/status/1184729997719687168
[Magisk] XtraWater:
I'm using ubs twint. Even fingerprint authentication works. Good to know. So I continue to stay with magisk 19.3.
[Magisk] Strike3k:
I am a little bit confused about where my system folder went. I have an Xiaomi Mi 9T Pro on Android 10 and I installed Magisk 20. All root-checker apps say that I have root installed and apps with root are almost all working fine.

But I tried EmojiSwitcher and this app switches the NotoColorEmoji.ttf in /system/fonts. The app did not work, so I tried to copy the NotoColorEmoji.ttf with root explorer, but I cannot edit the file in any way. So I installed Magisk 19.3 and everything worked fine.

Now I read that Magisk 20 has this new system-as-root feature and as far as I understand does that mount system as the root directory. So when I open root explorer and go to the root directory, I should see all my folders which are in system, right? But that is not the case for me, so how can I edit files that are in the system folder with Magisk 20? I don't get it...

Ok I found my solution here : https://topjohnwu.github.io/Magisk/install.html#boot-image-patching

So I have to find the recovery.img for my ROM and patch it manually and flash this patched original recovery.img. As far as I understand, I am not able to use a custom recovery anymore...

Is there an update planned, so that devices with system-as-root and no A/B partitions can use Magisk just by flashing the zip? I really want to be able to use a custom recovery. And in advance I cannot use it because I cannot find the original recovery.img.. :D
[Magisk] martyfender:
From my limited understanding of Android 10, the system is no longer writeable , or read only. You have to do system modifications systemlessly with, for example a Magsisk module, that you or someone else creates.

I'm not sure why you can't view them though unless Google has limited this even more so than they did on my new Android 9 device. Many partitions can't be seen in Diskinfo Pro. I get this message in the app:

Could someone with more knowledge please clarify?
[Magisk] ashyx:
Why do you say you cannot use a custom recovery any more? Surely your device still uses a stock recovery?
[Magisk] YMatrix:
Hello!

I am using Magisk on my Samsung S8 android Pie. I updated to v20 but seem to have a strange issue - all apps that I have granted have root rights, when editing the system partition everything seems ok, but on next boot the changes dissappear. I have tried downgrading back to 19.4,but that didn't help.

I was using magisk on Oreo before pie, so I don't excatly know when this started happening.

Anyone have advice on how to solve this? For now every system change I go to TWRP.

Thanks
[Magisk] ktmom:
Have you upgraded Magisk manger to match the version of Magisk you are using?
[Magisk] Ingor59:
I have the exact same problem my tab S5e.

Does anyone have a solution?
[Magisk] ktmom:
Uhm, which issue exactly?
[Magisk] Ingor59:
Rooting Tab S5e (SM-T725) New Magisk 20.0 problem

I did root my Galaxy Tab S5e with Magisk 19.3 and Manager 7.3.2 Without any problem.

Now Magisk is updated to 20.0 rooting gives the following problem:

Error Verifying VBmeta image 0_0 Indiuldum XX_EDRHS_IMTHSGAUEMSAC

the tablet did stay in download modus and the only thing I could do is installing the original firmware.

This happened twice.

So, I can not root it with magisk 20.0.

I saw on the forum that I am not the only one with te same problem

I did root it in this way:

https://xdaforums.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
[Magisk] NameLessThugZero:
Im sorry for such a possibly obvious question.

In moving from Android 10 from Pie on my Pixel 2 (Magisk, Riru, Edxposed, GB), what would be to best way to to proceed? I normally just do the patch boot method:

- Download the Full image

- Rip boot img from that and have Magisk patch it

- Then flash the OTA and then the patched boot

But since this is a full OS update, and due to what I heard about it changing up the partitions (in my limited understanding of any of that stuff) among other things, Im not sure if that same route would work anymore. Is this an incorrect assumption? How have people gotten to 10 safely?
[Magisk] pakophan:
#OnePlus 5, I'm facing boot loop when using the latest OOS 9.0.9 with magisk v20. Currently I'm using the phone without root because it boot loops every time I flash the magisk zip. Have you guys found a fix or maybe I'm the only one experiencing this??? Please help

---------- Post added at 06:59 PM ---------- Previous post was at 06:53 PM ----------

This bootloop issue started because of the OTA update. On the previous version of OOS it worked fine.
[Magisk] YMatrix:
Anyone?
[Magisk] peter_dk01:
Same issue here - NemId suddenly detects Magisk Manager even when hidden. I resolved the issue by hiding the app first and then renaming it to "MM" with apk editor. No issues since
[Magisk] Deurklink73:
The only thing i see in 7.3.5 is when i open Magisk 20, 7.3.5 is red for a second and than turn into green.
[Magisk] ktmom:
This looks like verified boot is failing. It would probably help if full logs were supplied. See below for the link.

In order for anyone to help you, you need to provide logs.

Please review Asking for help/reporting bugs

---------- Post added at 18:54 ---------- Previous post was at 18:43 ----------

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
[Magisk] JDubbed:
Razer Phone 2 Stuck at Logo

I have a Razer Phone 2 running MR1 rooted with arter97. I updated Magisk Manager to latest rebooted and booted fine. Installed latest of Magisk, used the recommended option, rebooted and now phone gets stuck at logo. I am able to boot into TWRP 3.2.1-arter97. I have Magisk-v19.3(19300).zip on my sd which I installed through TWRP hoping it would fix the problem. TWRP installed the zip, rebooted and still stuck at logo. I am not sure how to generate logs if I cannot boot. For some reason the installation of the newest Magisk caused this. I am fine just going back to the older Magisk but I am not sure how to proceed. I'd appreciate any help on this as I am at a loss. Thanks!

I also followed this guide which explained how to install magisk and root in the beginning. So I tried using the fastboot method again using the MR1 boot.img on both partitions and still no dice.

Another addition. I had used TWRP to perform a full backup of system/data/boot when I first got TWRP. I attempted to restore the boot backup, it succeeded, but still stuck at boot logo. What in the world did the Magisk update do? And how do I revert it?

Also tried restoring a system image backup that I created with TWRP couple month ago and now no arter97 TWRP. Great...
[Magisk] LSS4181:
I'm currently at March update (MR1), using Havoc 2.9 GSI, arter97 kernel r11 and Magisk 20.1-59fd38bb and it's currently working without major issues.

You can always try a canary build if stable build has issues.

EDIT: Not sure what's going on with the network but my browser is giving me errors like 502, despite the replies were successfully posted. Cleaning things up. :(
[Magisk] JDubbed:
Thanks for your reply. When you say update I assume your meaning the security update patches? Not sure. I went ahead and reflashed Arter97 kernel r11 and phone booted back up. I assume this happened because Arter97 removes Magisk. So I decided to flash Magisk 20.0 from within TWRP instead of Magisk app and phone boots up now with Magisk 20.0 installed. Either it was a freak accident the first go around or what but phone now works with Arter97 r11 and Magisk 20.0. Thanks for chiming in.
[Magisk] LSS4181:
Usually custom kernel images aren't patched for Magisk, so you can use it as is, or flash Magisk/SuperSU later on, depending on your need.

Magisk will patch the kernel image during the flashing process. If you flash a newer kernel image, the patches will be lost and you'll need to flash Magisk again.
[Magisk] martyfender:
If you are referring to xda, it often has errors like that. When you hit the: Submit Reply button, be patient. If you are impatient and hit submit again, you will often get double posts. I am not sure what causes this, but it is quite irritating. I have never encountered it on any of the many forums I have post to in the past, just xda.
[Magisk] mewbow1:
mAadhar app is not working and is detecting rooted device even if hidden with MagiskHide. Also Magisk Manager is hidden with random package name.

Any suggestions on this?
[Magisk] palmbeach05:
Yeah, wait for the update topjohnwu tipped us off about on twitter
[Magisk] Prone01:
flash magisk but it is not installed in magisk menager

I have a problem, I flash magisk using twrp, the phone is 10 minutes optimizing applications and once done on magisk menager is not installed magisk. the phone is samsung a50. could anyone help me?
[Magisk] YMatrix:
Bump
[Magisk] Ssnurzel:
Yes. Thats right. Maybe a slow loading of the manager
[Magisk] brsteej:
Can i patch samsung firmware with Magisk19.3

Hello

I have problem with magisk 20 when i patch samsung tab s6 or s5e and flash it there is an issue with vbmeta partition and wont boot

So is there any way to patch with magisk 19.3 ? it was fine for me