V3.8 Zygote detection injected

[Hopefaith1]

I'm using the latest v3.8. Before using it, momo only shows that the bootloader is unlocked. After using bootloader Spoofer, momo shows "zygote injected" can you please advise me how to fix?

[MissThee]

Updating to 1.9.3 fixed zygote injected ,but I had to upgrade to v3.8 for it to work v1.2 probably didn't even launch probably because I am running android 14.

But if you use MemoryDetector to detect instead of Momo, it will still display "Found 2 suspicious anonyour memories mapping" when using lsposed

Can you give me the download link?

MemoryDetector2.1 https://drive.google.com/file/d/1u4gP45DqNwPG2GmM2FzOgavCgUktbecJ/view?usp=drive_link

[Manasx100]

@Tobim6 Currently, I can pass all root check applications, including MOMO, without any problems.

No way you are passing native detector

[Tobim6]

No way you are passing native detector

I said Native Detector.

[LostInTheReality]

Thanks. Setting 'Logger buffer sizes' to 0, clearing Lsposed_mod's (by mywalkb) logs and then restarting a device clears detected injected zygote, therefore enabling to use BootloaderSpoofer's injection.

Does anyone know how to bypass 'Partition mounted abnormally'?

[DevkanKafkas]

Thanks. Setting 'Logger buffer sizes' to 0, clearing Lsposed_mod's (by mywalkb) logs and then restarting a device clears detected injected zygote, therefore enabling to use BootloaderSpoofer's injection.

Does anyone know how to bypass 'Partition mounted abnormally'?

When you set the buffer to 0, it shouldn't actually come out. Which version of LSPOSED do you use?

[LostInTheReality]

Thanks. Setting 'Logger buffer sizes' to 0, clearing Lsposed_mod's (by mywalkb) logs and then restarting a device clears detected injected zygote, therefore enabling to use BootloaderSpoofer's injection. Does anyone know how to bypass 'Partition mounted abnormally'?

When you set the buffer to 0, it shouldn't actually come out. Which version of LSPOSED do you use?

https://github.com/mywalkb/LSPosed_mod

[Tobim6]

Native detector is the true best tester t.me/reveny1

[Manasx100]

No way you are passing native detector

I said Native Detector.

[zhnlyn]

Thanks. Setting 'Logger buffer sizes' to 0, clearing Lsposed_mod's (by mywalkb) logs and then restarting a device clears detected injected zygote, therefore enabling to use BootloaderSpoofer's injection.

Does anyone know how to bypass 'Partition mounted abnormally'?

Use this module with magisk: https://github.com/snake-4/Zygisk-Assistant

[zhnlyn]

No way you are passing native detector

I said Native Detector.

Im able to get "The environment is normal" screen after fixing the TEE broken issue that MOMO was detecting. On Native Detector however, it still shows "TEE is broken" anyone know the difference in implementation between the two testing applications?

[DevkanKafkas]

Yerel dedektörü geçmenin imkânı yok

Yerli Dedektör dedim.

MOMO'nun tespit ettiği TEE bozuk sorununu düzelttikten sonra "Ortam normal" ekranını alabiliyorum. Ancak Native Detector'da hala "TEE bozuk" görünüyor, iki test uygulaması arasındaki uygulama farkını bilen var mı?

Momo(io.github.vvb2060.mahoshojo) - "Frida Detection" "Magisk Detection" "Zygisk Detection" "Magisk Modules Detection" "Debugging Mode Detection" "Developer Mode Detection" "Bootloader Detection" "System Files Modified By Magisk Detection" "Package Manager abnormal Detection" "Custom ROM Detection" "SELinux State Detection"

Native Detector; "Apk Signature Verification" "Magisk & Root Detection" "Sandbox & Sandbox Detection" "Frida & IDA Detection" "libc Memory Detection" "Unidbg Detection" "Key function inlinehook & got table Detection" "Anti-Debugging Detection" "ISO strong Detection" "Magisk Hide Detection" "Custom ROM Detection"n"

I think the commonly used root files are being detected by scanning files in memory. Because these files leave a lot of traces. For example, an application called "HUNTER" catches lines that "MOMO" does not.

For instance, since "BOOTLOADER LOCK" is a well-known LSPOSED module, "HUNTER" knows its location in memory. Whenever I activate this module for "HUNTER", it detects it, but when I deactivate it, it only gives a BOOTLOADER error.

[Tobim6]

Momo(io.github.vvb2060.mahoshojo) - "Frida Detection" "Magisk Detection" "Zygisk Detection" "Magisk Modules Detection" "Debugging Mode Detection" "Developer Mode Detection" "Bootloader Detection" "System Files Modified By Magisk Detection" "Package Manager abnormal Detection" "Custom ROM Detection" "SELinux State Detection"

Native Detector; "Apk Signature Verification" "Magisk & Root Detection" "Sandbox & Sandbox Detection" "Frida & IDA Detection" "libc Memory Detection" "Unidbg Detection" "Key function inlinehook & got table Detection" "Anti-Debugging Detection" "ISO strong Detection" "Magisk Hide Detection" "Custom ROM Detection"n"

I think the commonly used root files are being detected by scanning files in memory. Because these files leave a lot of traces. For example, an application called "HUNTER" catches lines that "MOMO" does not.

For instance, since "BOOTLOADER LOCK" is a well-known LSPOSED module, "HUNTER" knows its location in memory. Whenever I activate this module for "HUNTER", it detects it, but when I deactivate it, it only gives a BOOTLOADER error.

Native detector also has injection detection so it detects bootloader spoofer

[DevkanKafkas]

Momo(io.github.vvb2060.mahoshojo) - "Frida Detection" "Magisk Detection" "Zygisk Detection" "Magisk Modules Detection" "Debugging Mode Detection" "Developer Mode Detection" "Bootloader Detection" "System Files Modified By Magisk Detection" "Package Manager abnormal Detection" "Custom ROM Detection" "SELinux State Detection" Native Detector; "Apk Signature Verification" "Magisk & Root Detection" "Sandbox & Sandbox Detection" "Frida & IDA Detection" "libc Memory Detection" "Unidbg Detection" "Key function inlinehook & got table Detection" "Anti-Debugging Detection" "ISO strong Detection" "Magisk Hide Detection" "Custom ROM Detection"n" I think the commonly used root files are being detected by scanning files in memory. Because these files leave a lot of traces. For example, an application called "HUNTER" catches lines that "MOMO" does not. For instance, since "BOOTLOADER LOCK" is a well-known LSPOSED module, "HUNTER" knows its location in memory. Whenever I activate this module for "HUNTER", it detects it, but when I deactivate it, it only gives a BOOTLOADER error.

Native detector also has injection detection so it detects bootloader spoofer

We need a more powerful "Bootloader Spoofer" :) Applications such as U$ER etc. can be detected easily.

[xyychenchen]

Kitsune başardı! Kitsune Magisk'i deneyin

Definitely Doesn't Work to KITSUNE

video_2024-03-07_07-59-20.mp4 Skill issue, blame your self

hey bro, i use Kitsune Mask canary(27001) and bootloaderspoofer, and in the lsp module bootloaderspoffer page, i select momo , when i restart momo, there is no bootloader unlocked detected, but instead there is a zygote is injected, unlike the "environment is normal" as you show in your video, so how did you do that, could you please teach me, thanks so much

[renton16]

I included "System Framework" on BottloaderSpoofer with Momo.

• Momo shows "Environment is normal"

• Developer Option (Mi Unlock Status) is still "Unlocked" though

• Kitsune Mask canary(27001)

• LSPosed 1.9.3_mod (7244) - Zygisk

[DevkanKafkas]

I included "System Framework" on BottloaderSpoofer with Momo.

• Momo shows "Environment is normal"

• Developer Option (Mi Unlock Status) is still "Unlocked" though

• Kitsune Mask canary(27001)

• LSPosed 1.9.3_mod (7244) - Zygisk

Momo is very easy to fool. There is no problem there either. The important thing is to trick applications like "Hunter". Now Hunter directly understands that it is BootloaderSpoof

Try this; https://github.com/rushiranpise/detection/blob/main/Hunter_5.5.0.apk

[renton16]

I included "System Framework" on BottloaderSpoofer with Momo.

• Momo shows "Environment is normal"
• Developer Option (Mi Unlock Status) is still "Unlocked" though
• Kitsune Mask canary(27001)
• LSPosed 1.9.3_mod (7244) - Zygisk

Momo is very easy to fool. There is no problem there either. The important thing is to trick applications like "Hunter". Now Hunter directly understands that it is BootloaderSpoof

Try this; https://github.com/rushiranpise/detection/blob/main/Hunter_5.5.0.apk

Right, it detects error. I wonder why when I disabled BootloaderSpoofer, Hunter does not trigger Bootloader is unlocked. I can't get rid of that "Suspicious root files" and "Boot partition signature" error

Disabled:

Enabled:

[DevkanKafkas]

I included "System Framework" on BottloaderSpoofer with Momo.

• Momo shows "Environment is normal"
• Developer Option (Mi Unlock Status) is still "Unlocked" though
• Kitsune Mask canary(27001)
• LSPosed 1.9.3_mod (7244) - Zygisk

Momo is very easy to fool. There is no problem there either. The important thing is to trick applications like "Hunter". Now Hunter directly understands that it is BootloaderSpoof

Try this; https://github.com/rushiranpise/detection/blob/main/Hunter_5.5.0.apk

Right, it detects error. I wonder why when I disabled BootloaderSpoofer, Hunter does not trigger Bootloader is unlocked. I can't get rid of that "Suspicious root files" and "Boot partition signature" error

Disabled:

Enabled:

BootloaderSpoofer I have played a lot on it to the best of my knowledge, but it catches many banking applications. I could not find the answer to the question "How", "Why", "From Where". I would be glad if someone knowledgeable on the subject could help. Also, if there is anyone who says you can't do this, I'm telling those people now, no. It can be done 100% with paid applications.

[Tobim6]

Also try native detector https://t.me/reveny1