no, I didn't, it isn't available for 23 anyway I thinkWere you using Zygisk USNF module?; Won't be working w/ 23.0... PW
no, I didn't, it isn't available for 23 anyway I thinkWere you using Zygisk USNF module?; Won't be working w/ 23.0... PW
I meant 'were you using' as in before you downgraded... Also I've added to last post... PW
Getting black screen on latest v1.7.86 of this app. Suspect is new detection mechanism. Anyone can test?
Before this version is fine (v1.7.84). Pass safetynet, Shamiko, Added to deny list it just wont work on latest version.![]()
Pixel 6 Pro Latest Nov patch, Magisk 25.2
It's not normal but there are SO MANY differences in Magisk v25 (starting with v24) compared to your old v22 or v23) that I really suggest you:A few years ago I installed Magisk v. 22 on my Note 9 (Android 10). Today I tried, using Magisk Manager, to update both the app and Magisk to the latest version (via direct installation).
However, while the app updated to v. 25.2, instead, Magisk updated to v. 23. Is this normal?
I thought Magisk would also update to v. 25.2 just like Magisk Manager.
Thank you for your response.It's not normal but there are SO MANY differences in Magisk v25 (starting with v24) compared to your old v22 or v23) that I really suggest you:
- search on XDA for Magisk Zygisk thread and carefully read OP posts to be aware what has changed, and what would you need to configure manually from scratch , etc
- since you have happily lived so far with that ancient Magisk v22, maybe you don't need to jump to all the new things (Zygosk, DenyList instead of MagiskHide, no more Modules repository, optional Shamiko, USNF, Hide My Apps), and/or maybe you have an old version of Android that Magisk or important new modules (Shamiko, LSPosed) will not support
Hi Guys,
I found the checks the HDFC Bank_11.1.5 app is performing for checking the root status, most of the stuff is obfuscated but we can get a glimpse of what is going around in the background.
Any suggestion to bypass this is much appreciated.
C++:package com.backbase.android.core.security; import android.content.Context; import com.backbase.android.core.utils.DoNotObfuscate; import com.backbase.p006a.C0843b; import lxl.C6232aa; @DoNotObfuscate /* loaded from: classes2.dex */ public class RootVerification { private C0843b rootUtils; private boolean rooted; public RootVerification(Context context) { this.rootUtils = new C0843b(context); } public boolean isRooted() { return this.rooted; } public RootVerification withBinaries(String[] strArr) { int length = strArr.length; int i = 0; while (true) { if (i >= length) { break; } else if (C0843b.m10159a(strArr[i])) { this.rooted = true; break; } else { i++; } } return this; } public RootVerification withBusyBoxBinary() { this.rooted = C0843b.m10159a(C6232aa.m1119a(22896)); return this; } public RootVerification withDangerousProps() { this.rooted = this.rootUtils.m10156b(); return this; } public RootVerification withDefaultCheck() { C0843b c0843b = this.rootUtils; this.rooted = c0843b.m10157a((String[]) null) || c0843b.m10155b(null) || C0843b.m10159a(C6232aa.m1119a(22897)) || c0843b.m10156b() || c0843b.m10154c() || C0843b.m10160a() || C0843b.m10152d(); return this; } public RootVerification withPotentiallyDangerousApps(String... strArr) { this.rooted = this.rootUtils.m10155b(strArr); return this; } public RootVerification withRootCloakingApps(String... strArr) { this.rooted = this.rootUtils.m10153c(strArr); return this; } public RootVerification withRootManagementApps(String... strArr) { this.rooted = this.rootUtils.m10157a(strArr); return this; } public RootVerification withRwSystem() { this.rooted = this.rootUtils.m10154c(); return this; } public RootVerification withSuBinary() { this.rooted = C0843b.m10159a(C6232aa.m1119a(22898)); return this; } public RootVerification withSuExist() { this.rooted = C0843b.m10152d(); return this; } public RootVerification withTestKeys() { this.rooted = C0843b.m10160a(); return this; } }
Thank you for your effort, at least I know that its not my problemill have a crack, also Pixel 6 Pro, though on A13
Update:
No bueno...even with Hide My Applist
Perhaps a Magisk Delta user will test for you.....
Fellow Malaysian here, and also before this new update, there are error code keep popping up, u notice? Like not even 1 second then it closed, maybe that was the detection mechanism but its not working yet, I installed the previous version of it for it to work temporary lolThank you for your effort, at least I know that its not my problem
Hey, u mean the stopped working dialog that appears and gone in seconds right. I solved that one by hiding all process in denylist, if not mistaken by default it only tick the first one.Fellow Malaysian here, and also before this new update, there are error code keep popping up, u notice? Like not even 1 second then it closed, maybe that was the detection mechanism but its not working yet, I installed the previous version of it for it to work temporary lol
My one still popping out even tho I alredi deny all the processes lol, even game like undecember still detected the root even I hide it alsoHey, u mean the stopped working dialog that appears and gone in seconds right. I solved that one by hiding all process in denylist, if not mistaken by default it only tick the first one.
fine hereMy one still popping out even tho I alredi deny all the processes lol, even game like undecember still detected the root even I hide it also
I only can hide it with shamiko, was on normal zygisk previously
I am on shamiko too, maybe they strengthen their security.I only can hide it with shamiko, was on normal zygisk previously
Still haven't been able to do this on Xiaomi RN8T... Please say your device / OS... Thanks, PWHello Guys,
[UPDATE]
I was able to bypass the root detection of this app using the following magisk module.
Magisk Module Name: InitRcHider
Reference URL:XDA Download Link: https://forum.xda-developers.com/attachments/initrchider-zip.5472273/![]()
[MODULE] InitRcHider
Several banking and security apps discover system modifications that Magisk injects through the init.rc file. These modifications can be successfully hidden with MomoHider (https://github.com/canyie/Riru-MomoHider), however, that module requires...forum.xda-developers.com
Another TNG user here, I submitted a report to their developer team because I think it is app issues on latest version of TNG.Model: Xiaomi Mi A1 (tissot)
OS: Lineage (19-20221206-NIGHTLY-tissot)
Magisk version: 25.2
Magisk Modules:
LSPosed Module: Hide My Applist
- Advanced Charging Controller (ACC)
- Shamiko
- Systemless Hosts
- Universal SafetyNet Fix (Displax)
- Zygisk - LSPosed
Tested with Ruru and Momo (attached)
Not working with TnG ewallet (stuck at logo)
Will find resolution on Momo's findings and update here.
I have just recently came across shamiko since undecember, sword art online VS, TnG being detected, previously the old magisk hide and zygisk had no problem for me
Much in this section of @Didgeridoohan's Wiki:Hello
I have had a problem with various complications (I won't explain them all), and now I have a working mobile, but I can't re-root again.
Device:
- Xiaomi Lisa
- It was rooted with Magisk 25.2
- And various modules
- It does not have TWRP recovery, and Orange Fox does not decrypt data on Android 13
Situation:
- I received the OTA Android 12-> 13 (MIUI 13->14) (stock EU).
- I decided to download it to extract boot.img and patch it.
- Against the usual (and configured), instead of waiting for confirmation to install (time to apply the standard OTA update procedure: restore stock images and flash Magisk to empty slot), it started the process.
- When I realized I did the restore images, and let it reboot
- It ended up in a strange bootloop (at least for me): a few seconds after booting, showing the launcher, and even being able to open some app, the phone reboots and ends up in MIUI recovery.
- (...)
- Finally I manage to reflash the new ROM ("except storage"), and the phone boots fine.
- I patch the new boot
- But when I do the standard boot on the patched image, the problem of that "strange" bootloop is reproduced.
- Attempts to apply uninstall.zip fail because the recovery does not mount data.
- ((Finally, at home we have another Lisa. I opted to completely uninstall Magisk, flash the new ROM, then boot with the patched image and install Magisk, and it did not give any problems. I'm thinking to do the same in future...)).
The questions begin. I will also appreciate any rectification if something I say is not correct, to continue learning:
- It seems that there was something left of Magisk that creates a conflict, no?
- Since the modules and Magisk are inside \data, it is not possible to uninstall with uninstall.zip, is it?
(in fact in one of the tests with OFox (which does not see \data) it instead installed Magisk, giving the same problem
- as the mobile is not really rooted, there is no chance I could delete modules folder, right?
- And only with the mobile rooted I could ask the Magisk Manager to uninstall completely, no?
But as it does not give me time to run it because the phone restarts, and when it does is without rooting, I can't
- The time to reboot with the mobile temporarily rooted begins once I have entered the unlock pin. As I said, it doesn't give me time enough to interact with the applications.
Would there be any script (I'm not a developer) that I can run from terminal as soon as I have unlocked the phone, so it has effect before the device restarts? (stop process, remove folder...)
- Any idea (that does not involve formatting data...)?
Thanks
I use Payload dumper go by @osm0sis .I use payload-dumper. You cannot select only a single img file to extract but you can kill it once it extracts what you needed
[ ... ] Read Permissive ROM = experimental, insecure, half-baked ROM not fit for daily use [ ... ]
But it's NOT a preference! ... It's a fact!Actually, that is perfectly fit for my own daily use, and I doubt that I'm the only person who has this preference.
So you're talking about something completely different!I want to be able to turn permissive mode on and off as part of my own ROM usage, depending upon the tasks I want to perform and the software I wish to run. In the past, I was able to do this in one or more ROMs, and there was nothing half-baked about my user experience.
Sure you're not... Point is, You don't need a permissive ROM to do that...I'm willing to take the associated risks, and I don't want to be paternally "protected" against those things against my will. Again, I'm sure I'm not the only Android user who feels this way.
Yeah, I'm aware that back in June vvb2060 stated that the OTA feature in Magisk doesn't work on Pixels because the partition digest calculations were not overwriting the original values . To my knowledge, no one has submitted a PR for that issue. Nor am I aware of any changes since then to the digest checks.That's interesting...
This was broken for Pixel 6 and 7 at least for late A12 and A13 updates due to new partition digest checking by update engine... The linked Google documentation doesn't seem to have changed... Still says:
... This new check was identified as the issue because boot.img partition digest doesn't match after Magisk flashing so dm-verity devices indicate corrupt boot image and update/slot will be marked as failed/corrupted... I believe disabling verity/verification can't help since vbmeta can't be tampered for delta updates using update engine either...
I mentioned this here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-87762979
The issue is still marked in GitHub as wontfix...
Do you know if Google has in fact changed/reverted their digest checks, or if this actually works w/ up-to-date releases for some?... And perhaps you could link a user's success story?... Thanks, PW
notes.md
file is the change log.app-debug.apk
is Magisk canary.app-debug.apk
and choose View Raw or click on the Download option.