yashsingh1/xdaforums huggingface dataset:
[Magisk] grep_i:
You know you can unlock LG g3 bootloader with bump, if not try to search your device specific thread.

There will be information there to accomplish the task.

Edit: see now that this is an old post I replied to.
[Magisk] andrew2432:
Cbump!!!
[Magisk] snke:
I have some trouble with magisk v8 + phhsuperuser + xSetprop 0.2 + latest elementalX, i can't verify SN or it take too much time to verify that (green)...why?:confused:

EDIT: Solved
[Magisk] AbiDez:
I'm alone with this?

CarHDRom V.25 by Carotix S6edge
[Magisk] jcrompton:
How
[Magisk] jeanxx:
Does Magisk have youtube background play mod, youtube adaway mod, greenify mod and secure settings mod available to install?
[Magisk] janarp:
u can download systemless xposed and then from exposed u can use these mods...
[Magisk] Artim_96:
No. If there are apps for that, build them yourself, otherwise there is no other option than to use XPosed. For AdAway it might be possible to use AdAway since for all I know it should work systemlessly with Magisk, buy especially background play and Greenify are things that aren't possible without manipulating the apps. And that's nothing Magisk does. For YouTube requested stuff you might find a prepared app for that but the rest is impossible without XPosed
[Magisk] Immortalis:
Update: fixed by uninstalling Magisk and installing xsetprop in /su
[Magisk] Alxoom33:
How do you do that and make it work?
[Magisk] erwinsie:
hi Guys, ok this whole magisk is seems to be non noob friendly. i thought once i flash it i can just toggle root on/off.

i dont care about pogo, but please tell me if it is possible to have custom rom, and still use android pay?

is it possible to flash custom rom (rooted) then remove SuperSu/unroot and then all apps including android pay will see my phone as not-rooted?
[Magisk] cridtohs:
how do you know xsetprop fixed it? Also where is xsetprop dl?
[Magisk] Immortalis:
I was affected by the bug, which couldn't enable root after disabling it in Root Switch until rebooting (apps like AdAway kept showing "rooted Android required"), and mods like Magisk_mod (1 and 2) didn't help either. So I removed xsetprop and then tried disabling root and enabling it again - everything worked flawlessly, so I kept searching for a solution. I came across a post from Captain_Throwback, who mentioned that xsetprop can be extracted and installed in /su, so I tried that and now I have installed the module and everything works now, SafetyNet passes even with Xposed enabled.

What I've done:

booted into TWRP and ran Magisk uninstaller

rebooted into fastboot and flashed clean boot.img

in TWRP file manager removed su.img, stock-boot.img and stock_boot_somehexvalue.img.gz

installed (in exact order):

ElementalX

SuperSU 2.78 SR1

Xposed 86.2

suhide 0.55

booted into Android, copied xsetprop binary file and post-fs-data.sh into /su/xbin and /su/su.d respectively and set permissions to 755

That's pretty much it, after rebooting I ran

adb shell
getprop ro.boot.verifiedbootstate

and it returned green.

Download for xsetprop is here. Extract post-fs-data.sh from common folder and binary from system/xbin.

Some screenies in attachments.
[Magisk] Fif_:
You may have been hit by the bug where you cannot upgrade to Magisk 25 with direct install.

If you can get back to Magisk 24, you should be able to upgrade successfully by restoring the boot image with Magisk before performing the direct install to 25.1.
[Magisk] IronStorm84:
ok i have uninstalled magisk via the uninstaller. now my titanium backup says that i have no root access.

seems that is everything uninstalled properly

is there any chance to geht root access back without loosing data?

custom rom, custom BL and twrp are installed.
[Magisk] zgfg:
Installing Magisk does not wipe data.

Recommended way for installing Magisk is to patch and flash the img - please read the installation guide from Magisk Guthub
[Magisk] Detonatte:
Dr.Ketan ROM Q19 (Android 10) has preinstalled with Magisk 24.3.
[Magisk] J.Michael:
Well, there you go. I think if a ROM has Magisk already installed, you cannot update Magisk -- you have to wait for the ROM publisher to release a ROM with a newer version of Magisk.
[Magisk] IronStorm84:
Before Installing Magisk​

Installing Magisk WILL trip KNOX

Installing Magisk for the first time REQUIRES a full data wipe (this is NOT counting the data wipe when unlocking bootloader). Backup your data before continue.

Download Odin (only runs on Windows) that supports your device.

requiers a full data wipe???
[Magisk] zgfg:
This is a general thread here (all kinds of vendors and phone models), while Knox is specific to Samsung

Sorry if you wrote that but I overlooked that you ask specially for Samsung - otherwise, for other phones, there is no Knox and installing Magisk (first or any time) does not trigger wiping Data
[Magisk] IronStorm84:
bl, custom fw etc was already patched/installed.

i install v25 now via twrp and after custom install the app again and reboot my phone my root access is back again :)

so everything works fine.

ty 4 help :)
[Magisk] pndwal:
The wipe requirements you cited apply only after stock is fully restored (using CSC.tar) on Sammy devices launhed w/ Android 9+ (with the inclusion of older devices updated to Android 10 as mentioned below), ie. SAR/2SI devices. Nb this:

Yours, running Android 9, is a Legacy ramdisk boot type device...

However, if you were to upgrade to Android 10 (available for S9) your device will be automatically upgraded to modern 2SI SAR boot type. In that case John's remark above will actually be in error, and Samsung (System-as-root) section will in fact be the correct section for you... the methods and caveats there will then apply... PW
[Magisk] DiamondJohn:
and Detonatte

I would not be so sure. My simple understanding is that Magisk is made of two parts. The modified boot image and the app. I see no explicit reason why he would not be able to flash a differently modified boot image and upgrade the app; unless there is something specific to his device or rom.

Most phones come without magisk installed, and we all do conceptually the same.
[Magisk] Detonatte:
Diamondjohn, one solution???
[Magisk] pndwal:
Yup; depends on dev implementation... @Didgeridoohan's wiki touches on this... Many are able to update.

Android 10 is Automatically using 2SI on all but Legacy SAR devices... Refactoring of 2SI magiskinit injection is a more likely source of issues...

This breaks Direct install even on many stock ROMs as previous patched image is now incompatible, having patched fstab (no longer patched)... Initial patch / flash from unpatched image still works fine...

This may cause a difficulty for you if no unpatched image for DK ROM is available... You may need to wait for a compatible kernel from the dev, or find/use another.

Another reason the dev may integrate Magisk is that the custom kernel may not boot w/o stripping avb_key and avb flags for partitions... Kirisakura custom kernels from @Freak07 (and other configurations) were relying on Magisk to do this, but this function is no longer generally performed for 2SI devices in 25+ as it was only there to facilitate fstab patching.

If DK ROM needed this too, it may be enough to check the “Patch vbmeta in boot image” option if it's offered, or patch the vbmeta partition with command:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img otherwise.

If even this isn't enough, this comment may give you more clues:

https://github.com/topjohnwu/Magisk/issues/5777#issuecomment-1126691707

... I put a lot of information about this magiskinit refactoring here around June 23...

👀 PW
[Magisk] Detonatte:
pndwal, I have no idea how to do this (Patch vbmeta in boot image). :(​

It's something beyond me!
[Magisk] pndwal:
Really? ... Just means follow official instructions... 😜

You should now check vbmeta implementation in any case per:

https://topjohnwu.github.io/Magisk/install.html#getting-started

... If device has no separate vbmeta partition you should be doing this anyway:

https://topjohnwu.github.io/Magisk/install.html#patching-images

If it does, try the outlined option:

With modern SAR / 2SI devices (consider yours modern since Android 10 update to 2SI) it is highly recommended that you use App patch & fastboot flash installation rather than old zip installer custom recovery installation anyway, so you should be set up for/familiar with fastboot...

I've outlined several possible issues that may be breaking your custom installation, so of course there's no guarantee disable-verity --disable-verification alone will fix it...

Please try the above and report results...

😉 PW
[Magisk] 562TOKER:
Has anyone else tried zelle on chase app. It detects root I get security issue on pixel 5 Android 11 app is enforc list I'm trying data/cache wipe see if that helps
[Magisk] super_nooby:
I had the same problem with the Galaxy S9 when I wanted to update Magisk. Uninstalling it completely resulted in a bootloop at the boot screen. The solution was simple: After I reloaded the image and flashed the ROM over it, I was able to install the latest Magisk without any problems.
[Magisk] pndwal:
Can I take it you were on Android 10 also? (Ie. Samsung (System-as-root) Instruction now applies)...

Since you uninstalled, your issue may have been different / this:

Never, ever try to restore either boot, recovery, or vbmeta partitions back to stock! You can brick your device by doing so...

😛 PW
[Magisk] Detonatte:
It's too complicated for me and I don't feel like bricking my phone
[Magisk] zgfg:
Cont. on mental juggling (I wouldn't use the other word) with S-Checker (full Google Play name: Security Check - Device compliance for payments)

Yesterday evening I set from scratch Magisk Delta 25101 to my second phone.

I ended with the followowing configuration:

- MagiskHide with the needed apps (like GMS and mentioned detectors/checkers) enabled

- Zygisk enabled, Shamiko module installed

- LSPosed and its HMA module installed and configured

I have achieved the same (no better/no worse) results than on my other phone.running TJW official Magisk 25101 with DenyList (not enforced):

- Safety Net, Oprek Detector and TB Checker fully passing

- Momo reporting Magisk Found and unlocked Bootloader (plus few others either fixable, or kind of specific to the rooted Xiaomi phones)

And S-Check finding root with the error codes 107/204/606 (again, all the same as on my other phone running TJW Canary)

Frankly, I expected that Delta+MagiskHide could convince S-Check to pass, but to my surprise/disappointment it didn't

Maybe the Second space option would help but my old phone is too slow to run Second Space (I tried once but the responsiveness was beyond my nerves for any practical use)

Few notes about HMA:

- not needed for S-Check and TB Checker since Delta app is already released with a different package name (HMA is needed for TJW Magisk - somebody just complained here that he cannot pass TB Checker: he should eg use HMA to hide the Magisk app from Oprek Detector and TB Checker)

- however, I use two other LSPosed modules (GravityBox and CustoMIUIzer) plus I use HMA for detaching few apps (mainly YT and AndroidAuto) from Google Play

- therefore I need then HMA to hide all the three mentioned LSPosed modules (incl. itself) from Oprek Detector and TB Checker (hence I also enabled hiding in HMA from S-Checker)

Nevertheless, I tried even without LSPosed (and the accompanied modules) installed, but no luck to pass the tough S-Check detector
[Magisk] pndwal:
🙂

Seems there are two principal advantages for users of @huskydg's Delta Magisk fork (besides possibly bypassing the need for obfuscating / hiding the Magisk app due to different app signing keys*) and the second may be more relavent for difficult apps / detections (including S-Check?):

1) Sync with official Magisk adding back MagiskHide. (Allows use of Zygisk compatible MagiskHide and post-Hide era Magisk.):

https://xdaforums.com/t/discussion-...third-party-magisk-fork.4460555/post-87060305

2) Ability to disable zygisk and use only MagiskHide. (Allows use of Riru modules like Riru-USNF 2.1.3, Riru-MomoHider, Riru-LSPosed etc and post-Hide era Magisk while subverting all possible zygisk detection.) Further:

https://xdaforums.com/t/discussion-...third-party-magisk-fork.4460555/post-87060311

*Nb vv's Alpha fork Magisk App is already known/ detected by many banks... Some may well have already added HuskyDG Delta to their security engine lists necessitating Hide the Magisk app use again...

... Of course John would prefer Devs to work on 'hide' modules and support official Magisk builds...

but forks like Delta break no rules...

www.twitter.com/topjohnwu/status/1445598605029482503

😛 PW
[Magisk] pndwal:
Is Shamiko actually working with hide enabled?... I thought it wasn't compatible / conflicts with hide... Perhaps one overrides the other... PW
[Magisk] pndwal:
Making a Magisk Bug Report?

https://github.com/topjohnwu/Magisk#bug-reports

Here's a How To (Capture and read bug reports):

https://developer.android.com/studio/debug/bug-report

👀 PW
[Magisk] zgfg:
Yes, it does. When I had Zygisk + MagiskHide (Delta), Momo was detecting Zygisk. With Shamiko, it stopped detecting
[Magisk] huskydg:
To be honest, Momo is not the strongest tool to detect zygisk, Livin by Madiri is the strongest banking app that detect zygisk (use it when zygisk is enabled or disabled and you will know). Btw you can use whatever you think it work. Just don't rely on momo "mental masturbation" detection
[Magisk] zgfg:
I was actually interested in your opinion about S-Check and Delta.

As said, I expected that S-Check could pass with Delta and MagiskHide

Is there a way to pass (maybe without Zygisk and by using Riru+XLua or something)?

That would prove the advantage of Delta
[Magisk] huskydg:
I don't advertise delta and say and prove that my fork is the best (already repeat many times in my Telegram group and on github that if they are fine with official one, they don't need to switch to my fork), i just say the fact 🥴. You should expected the reality (banking apps to work) instead the false direction. If I am rude here then I sorry.
[Magisk] zgfg:
Sorry if missunderstanding but I was really asking about the method to pass S-Check (without Dual Space)
[Magisk] pndwal:
Ok, that's interesting... Shamiko and MagiskHide enabled!

That's an update on:

I understood users were getting "Shamiko is not Working... message unless MagiskHide was disabled...

Also

and

and

I didn't think that would work either... Perhaps something changed? ... Perhaps Zygisk modules can now override MagiskHide and take control of 'denylist'? PW
[Magisk] zgfg:
And one more note about S-Check

Xiaomi.eu firmwares are custom ROMs, ie Bootloader must be unlocked to install

However, Xiaomi.eu firmwares come with USNF code pre-built into the ROM, hence they pass SafetyNet (ePay, etc), out of the box - without the need for Magisk, modules, etc

Now, the point is:

Xiaomi.eu, clean installation (without Magisk, LSPosed, anything ever been installed and left its files) does pass S-Check.

However, Momo there still detects Bootloader unlocked

That IMO indicates that S-Check does not find unlocked Bootloader (on Xiaomi, like Momo does) - ie, its error codes 107/204/606 hide some other kind of detections

Fully green S-Check screenshot from Mi 11 Ultra, Xiaomi.eu Stable (MIUI 13, A12) attached - tested by a friend of mine (interestingly, he was a vivid hacker and modder here on XDA, providing his custom ROMs for Huawei several years ago, but he does no more want to hear about rooting, etc [it took him long to accept a custom ROM Xiaomi.eu] - since he also abstains from XDA, I will avoid his XDA username 😃)
[Magisk] zgfg:
Configuration on the screenshots
[Magisk] super_nooby:
Yes, I'm on Android 10 with the latest Alexndr ROM. So far I have never had any problems in all these years when I have always restored the complete image.
[Magisk] m0han:
interestingly, shamiko now works (in blacklist mode) - even with magiskhide enabled. i'm on the latest magisk delta.

init.rc not detected in magisk detector; but detected in momo, which also detects zygisk

if font module is enabled

. i don't use Livin by Madiri ..

no root detection in 's check' and 'tb checker' (my device does not have nfc). device is 'playstore certified', safetynet passes, gpay works.
[Magisk] zgfg:
Regarding Shamiko - it's probably due to the fact that now DenyList and MagiskHide are properly separated in Delta magisk.db (different switch to enable one or another and different lists).

(However, no option in Delta 25101 app to manage DenyList and command/option magisk --denylist is not supported. But on clean installation, DenyList is empty and not enforced, and if you go for MagiskHide you don't need DN)

For Momo, make sure you checkmarked all its processes in MagiskHide

Btw, I have Zygisk-LSPosed the same version, and eg V4A but for me S-Checker still reports root☹️
[Magisk] dohanin:
Need some help here. My phone is now stuck at boot logo, possibly due to some Magisk modules mess-up. I used fastboot to flash back the stock boot.img, then it can boot up, but obviously it has lost root. I cannot see what's happening in /data/adb, even with usb debugging, due to lack of permission.

Then I re-flashed the magisk-patched image, and it stuck at boot logo again.

How can I cleanly uninstall Magisk or remove all those modules in /data/adb without root?
[Magisk] V0latyle:
If you're using a newer version of Magisk, holding Volume Down during boot on some devices should boot in safe mode, disabling all modules.

Otherwise, you can open a command terminal and use ADB during boot:

adb wait-for-device shell magisk --remove-modules
[Magisk] zgfg:
Magisk GitHub, Wiki - three methods described how to to disable or delete module(s) in case of bootloop (TWRP if applicable, adb if applicable, Safe Android mode)
[Magisk] dohanin:
Thanks a lot. The 2nd method works on my device. Many thanks.
[Magisk] dohanin:
Thanks. :)
[Magisk] Swapmema6be:
Bootloop After flashing magisk patched boot image​

Device:Vivo 1802

Android version: 8.1

Magisk version name:canary build

Magisk version code:25101

ANDROID - Google Drive

drive.google.com

this folder contains

1. stock image

2. patched boot image

3. magisk log

4. cat /proc/mount

5. full log file….containg last_kmsg
[Magisk] dohanin:
Due to the recent update of Intune Company Portal which detects root (again!) causing so much trouble for me, I have been considering to unroot my phone altogether and go back to the world where I don't need to worry about apps detecting root every now and then. After comparing the pros and cons, I decided to go! Just uninstalled Magisk and relocked my bootloader. Momo is happy now :)
[Magisk] theovero:
Hello guys. I'm extremely layman on the subject and I have no idea what I'm doing, but I need to get my bank app working in the android studio emulator. I already installed magisk, managed to root and followed all the steps in this video, but it still didn't work for me.

1- I would firstly like to delete everything that is magisk registry on my computer and emulator to start the process from scratch, since I made a lot of mistakes and mixed different methods until it "works"

2- Secondly, I would like you to recommend a video of installation and later execution of root camouflage for banking applications by the android studio emulator. Android versions, image versions, magisk version and everything else.

Thank you all.
[Magisk] J.Michael:
If your objective is to run a bank app in an emulator, why install Magisk?

If you want to scrub the emulator, that's a Windows issue. Probably covered on a different web site. Have you tried uninstalling the emulator? Do you have any evidence of traces being left behind?

If your real goal is to run a bank app without a phone, look into android-x86 -- whether you actually boot it on your computer, or run it in a virtual machine, you will have an Android system without a phone.
[Magisk] Swapmema6be:
Post in thread 'Magisk General Support / Discussion'

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87153881 can anyobody look into this please 🥹
[Magisk] huskydg:
You mean Magisk not installed even patching boot images

mountinfo looks nothing
[Magisk] Swapmema6be:
No I face Bootloop after flashing patched boot image….sorry for incomplete question…..edited now!!
[Magisk] huskydg:
But you don't provide dmesg
[Magisk] Swapmema6be:
Oh sorry….I didn’t knew how would I do it?

do I have to grab it in normal working condion?

also can I grab it without root…..I am not rooted yet?
[Magisk] dcarvil:
See item 2 for getting a dmesg.

android-tools/guides/proper_bug_reporting.txt at main · nathanchance/android-tools

Publicly available Android stuff. Contribute to nathanchance/android-tools development by creating an account on GitHub.

github.com
[Magisk] theovero:
I need to pass safetynet checks to access banking apps through android emulator. However, I've tried every possible way with safetynet kdragon, prompconfs and everything else. I've watched all the tutorials available on youtube possible, but the problem is that these tutorials only show how to do this through a real cell phone and not through an emulator. Would you help me?
[Magisk] huskydg:
Not all banking apps use safetynet check but emulator will easily trigger "red flag" of banking apps such as permissive, unsafe environment
[Magisk] theovero:
ok, but I'm SURE that if I can activate safetynet on my emulator, I'll have access to my banking application. Can you help me?
[Magisk] J.Michael:
If you managed to install Magisk in the emulator, why not keep going? There are lots of posts in this thread about problems passing Safetynet, and possible solutions. Try some.

I have not used an emulator, let alone whichever random emulator you are using. If you really managed to install Magisk -- not the Magisk Manager app apk, but you patched and "flashed" and really installed Magisk, as evidenced by the display on the first page of the manager app -- then it should be trivial to try the usual solutions involving Magisk modules.
[Magisk] theovero:
I'm extremely layman on the subject and I don't know if because I'm doing it through an emulator, I should do all the processes I see in the videos teaching how to do it by cell phone.

I believe that because I'm doing it through an emulator, maybe I should do it differently, I don't know, maybe through the CMD itself. But I don't know how to do that, I don't understand.

Here on the forum I only see examples of how to enable by cell phone, just like on youtube...

I just found a tutorial that tells how to install by Ldplayer and bluestacks but I didn't understand anything.

To install magisk I followed this tutorial:

GitHub - newbit1/rootAVD: Script to root AVDs running with QEMU Emulator from Android Studio

Script to root AVDs running with QEMU Emulator from Android Studio - newbit1/rootAVD

github.com

To try to activate safetynet I followed several tutorials, some of them:
[Magisk] lesbianpinkie:
Hey guys, I'm on an SM-F711B (galaxy flip 3). Today when trying to update my rooted OS, I had Odin fail twice while trying to install the patched AP file. I also noticed that the patched AP file was about half the size of the original - 3.2gb instead of 8gb. I then tried to install with the stock AP file, but now (duh) it says the file system is corrupted and Android can't boot. Is there any way I can a) fix the patched AP file without access to my phone, or b) at least recover the files (especially images) from my device before having to system reboot? many thanks