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?

[MaccabeeY]

I have been working with folks here for ideas on getting my phone "cleared", and through careful experimentation (& a bunch of luck), I discovered that chiteroman's BootloaderSpoofer v3.8 does not clear Integrity Check but v1.2 clears the Play Integrity Check (of course except "STRONG" as nothing clears that). I hope a downgrade to v1.2 works for you too.

[KateWasHere001]

I have been working with folks here for ideas on getting my phone "cleared", and through careful experimentation (& a bunch of luck), I discovered that chiteroman's BootloaderSpoofer v3.8 does not clear Integrity Check but v1.2 clears the Play Integrity Check (of course except "STRONG" as nothing clears that). I hope a downgrade to v1.2 works for you too.

tried, but it does not help :(

[N-X-T]

this is zygote problem, not module problem and util now, u can't hide "zygote is injected" if module lsposed is enabled.

[Tobim6]

I have the same issue. With module disabled I don't get zygote injected. Downgrade to v1.2 did not help.

[MaccabeeY]

I have the same issue. With module disabled I don't get zygote injected. Downgrade to v1.2 did not help.

Yeah, seems we're in a "fluid" situation. Today, I saw that I no longer passed DEVICE_INTEGRITY with my configuration that worked just a few days ago.

After some research in @chiteroman /PlayIntegrityFix issues section and some tideous trial & error I discovered a configuration that passes both BASIC & DEVICE_INTEGRITY, at least as of now.

For context, as of this evening, I'm currently successfully passing BASIC & DEVICE running on a Pixel 5 GD1YQ with the following: LineageOS 20.0 (dated 20240129); Magisk canary 26404; Play Integrity Fix 15.7.1 (NO pif.jason in /data/adb); Shamiko 1.0.1; LSPosed 1.9.2; BootloaderSpoofer 1.2; Hide My Applist 3.2

The one thing I think I noticed was that Play Store would not run "correctly" right away, kept getting "Try Again". To get Play Store to run right, seems I had to play around clearing cache & data for Play Store, Play Services, & Google Services Framework - rebooting; rinse & repeat. It also seemed to help by keeping an eye on the "Manage Space" for Play Services to try to tell when the its storage stopped growing.

Hope this works for others too.

[Stillhard]

Kitsune did it! Try Kitsune Magisk

[Tobim6]

I unfortunately use KernelSU

[DevkanKafkas]

Kitsune başardı! Kitsune Magisk'i deneyin

Definitely Doesn't Work to KITSUNE

[Stillhard]

Kitsune başardı! Kitsune Magisk'i deneyin

Definitely Doesn't Work to KITSUNE

https://github.com/chiteroman/BootloaderSpoofer/assets/219005/5daf4a11-2ff4-4b09-a7ea-254b786c54a9

Skill issue, blame your self

[DevkanKafkas]

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

it could be.

I reformatted the phone now

• Kitsune (27001)
• Magisk I hid it (You didn't hide it, but interestingly enough, momo didn't detect it)
• Play Integrity Installed Fix v15.9.4
• LSPosed Installed 1.9.2 (7024)
• Installed BootloaderSpoofer 3.8

Where is the problem here?

[MaccabeeY]

 Installed BootloaderSpoofer 3.8  <=== try v1.2, see if that makes a difference (see above replies)

Where is the problem here?

[DevkanKafkas]

 Installed BootloaderSpoofer 3.8  <=== try v1.2, see if that makes a difference (see above replies)

Where is the problem here?

v3.8 v3.6 v3.3 v3.5 v2.1 v2.0 v1.2

I tried all versions one by one and the result is the same. I get the error "ZYGOTE is injected".

[MaccabeeY]

I tried all versions one by one and the result is the same. I get the error "ZYGOTE is injected". <=== I got the same until I went back to v1.2

[Tobim6]

It can be fixed by setting logger buffer size to Off in developer options

[DevkanKafkas]

It can be fixed by setting logger buffer size to Off in developer options

I can't turn it off, it automatically becomes 64k.

[Tobim6]

I can't turn it off, it automatically becomes 64k.

Weird

[DevkanKafkas]

I can't turn it off, it automatically becomes 64k.

Weird

Now I noticed that when I turn on the "LSPosed" module it automatically becomes 64K. I can only turn it off when I close LSPosed.

[DevkanKafkas]

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

Can you open the other modules and show them all in one video? There is definitely a problem here.

[Joey111332]

Did this ever get resolved I'm having the same issue?

[Joey111332]

I can't turn it off, it automatically becomes 64k.

Weird

Now I noticed that when I turn on the "LSPosed" module it automatically becomes 64K. I can only turn it off when I close LSPosed.

Did you ever get this resolved im having the same issue

[DevkanKafkas]

Brother, I tried it on many phones and there doesn't seem to be a solution to this. I think the friend who claims to have done this does not activate the LPOSED module. When I told him to show all the broadcasts, his voice stopped :) I tried it on 5 different phones (V11,V12,V13)with 3 versions (Regular, Alpha, Beta Kitsune) and there is no way around it, maybe it can be on a phone with Android 10 or below, but I don't have it.

[Charles-IX]

Having the same problem using latest Kitsune Magisk on a OnePlus 11 PHB110 with Official LineageOS 21. The thing is using Zygisk to load BootloaderSpoofer will make my broken TEE fixed and unlocked Bootloader hidden, but Momo will show that Zygote is injected. ...And I can't use fingerprint pay anymore since apps like Wechat and Alipay detects TEE, Bootloader and Zygote ...At the same time. I don't think this is BootloaderSpoofer's bad, but is there a way to make it a Kitsune Magisk mudule instead of a Zygisk one? (I am a noob in Android and I know this might be a very stupid question, but I'd still like to ask out of curiosity. Any helpful interaction would be highly appreciated.)

[Tobim6]

I can't use fingerprint pay anymore since apps like Wechat and Alipay detects TEE, Bootloader and Zygote ...At the same time.

If you set logger buffer size to Off in developer options, you will not get zygote injected detection anymore

[DevkanKafkas]

Wechat ve Alipay gibi uygulamalar TEE, Bootloader ve Zygote'u aynı anda tespit ettiğinden artık parmak izi ödemesini kullanamıyorum.

Geliştirici seçeneklerinde günlükçü arabellek boyutunu Kapalı olarak ayarlarsanız artık zigot enjekte edilmiş algılaması elde edemezsiniz

I tried it on 8 different phones and Android 10 11, but it definitely doesn't work.

[DevkanKafkas]

I can't use fingerprint pay anymore since apps like Wechat and Alipay detects TEE, Bootloader and Zygote ...At the same time.

If you set logger buffer size to Off in developer options, you will not get zygote injected detection anymore

By the way, what you said is impossible because if you activate ZYGISK, the buffer size will automatically be 64K, you cannot turn it off even if you want. If there is another way, I don't know it technically.

[Tobim6]

I can't use fingerprint pay anymore since apps like Wechat and Alipay detects TEE, Bootloader and Zygote ...At the same time.

If you set logger buffer size to Off in developer options, you will not get zygote injected detection anymore

By the way, what you said is impossible because if you activate ZYGISK, the buffer size will automatically be 64K, you cannot turn it off even if you want. If there is another way, I don't know it technically.

I am able to set it to Off with Kitsune Magisk

[DevkanKafkas]

I also use kitsune. But as I said, whenever I activate it, the buffer does not become 0. Can you record screen video and share , kitsune ver. and momo screen etc.

[Tobim6]

https://drive.google.com/file/d/1GByvH_qNvzq8Tg3Ts4wIlt4qu72EIWMm/view?usp=drivesdk

I also use kitsune. But as I said, whenever I activate it, the buffer does not become 0. Can you record screen video and share , kitsune ver. and momo screen etc.

I don't show momo because I don't have the issue anymore with both logger buffer size enabled and disabled. Using a different LSPosed version fixed it. If you want I can send it here.

[whitesnakeftw]

I don't show momo because I don't have the issue anymore with both logger buffer size enabled and disabled. Using a different LSPosed version fixed it. If you want I can send it here.

@Tobim6 Which version is it?

[Tobim6]

@Tobim6 Which version is it?

1.9.3-7261

[olympus9]

@Tobim6Какая это версия?

1.9.3-7261

Where is this version of lsposed to download?

[Tobim6]

@Tobim6Какая это версия?

1.9.3-7261

Where is this version of lsposed to download?

I don't know, got it from telegram

[General110]

https://github.com/mywalkb/LSPosed_mod/issues/76

[HussenXD]

@Tobim6Какая это версия?

1.9.3-7261

Where is this version of lsposed to download?

I don't know, got it from telegram

can you please send the lsposed that you have 7261 i have search for it every where and i didn't found it 😭

[Tobim6]

@Tobim6Какая это версия?

1.9.3-7261

Where is this version of lsposed to download?

I don't know, got it from telegram

can you please send the lsposed that you have 7261 i have search for it every where and i didn't found it 😭

https://drive.google.com/file/d/1-vxugvuG1J5ZMySv7MVbr6QrvNhfERFa/view?usp=drivesdk

[HussenXD]

@Tobim6Какая это версия?

1.9.3-7261

Where is this version of lsposed to download?

I don't know, got it from telegram

can you please send the lsposed that you have 7261 i have search for it every where and i didn't found it 😭

https://drive.google.com/file/d/1-vxugvuG1J5ZMySv7MVbr6QrvNhfERFa/view?usp=drivesdk

thank you too much ☺️ 🥀🥀

[Manasx100]

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.

[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

[Tobim6]

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

What su provider do you have? (Magisk, KSU etc.) Are you applying a module in LSPosed to memory detector?

[MissThee]

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

What su provider do you have? (Magisk, KSU etc.) Are you applying a module in LSPosed to memory detector?

KSU(11838) and applying this module in LSPosed(1.9.3-7261) to memory detector

[Tobim6]

KSU(11838) and applying this module in LSPosed(1.9.3-7261) to memory detector

Why would you apply BootloaderSpoofer to Memory Detector

[MissThee]

KSU(11838) and applying this module in LSPosed(1.9.3-7261) to memory detector

Why would you apply BootloaderSpoofer to Memory Detector

I applied the module to both detectors for one possible reason, because I wanted to check if I passed all the checks at the same time. Otherwise, what do you think is the reason why they applied this module to Momo?

[Tobim6]

KSU(11838) and applying this module in LSPosed(1.9.3-7261) to memory detector

Why would you apply BootloaderSpoofer to Memory Detector

I applied the module to both detectors for one possible reason, because I wanted to check if I passed all the checks at the same time. Otherwise, what do you think is the reason why they applied this module to Momo?

Memory Detector does not detect unlocked bootloader. As for native detector, there's no aay to fix it.

[MissThee]

KSU(11838) and applying this module in LSPosed(1.9.3-7261) to memory detector

Why would you apply BootloaderSpoofer to Memory Detector

I applied the module to both detectors for one possible reason, because I wanted to check if I passed all the checks at the same time. Otherwise, what do you think is the reason why they applied this module to Momo?

Memory Detector does not detect unlocked bootloader. As for native detector, there's no aay to fix it.

So curious why would you install Momo and this module, if only Momo will detect the bootloader, it would be nice to uninstall Momo, Momo has no practical use for your daily life, why use this module instead of uninstalling Momo?

[Tobim6]

KSU(11838) and applying this module in LSPosed(1.9.3-7261) to memory detector

Why would you apply BootloaderSpoofer to Memory Detector

I applied the module to both detectors for one possible reason, because I wanted to check if I passed all the checks at the same time. Otherwise, what do you think is the reason why they applied this module to Momo?

Memory Detector does not detect unlocked bootloader. As for native detector, there's no aay to fix it.

So curious why would you install Momo and this module, if only Momo will detect the bootloader, it would be nice to uninstall Momo, Momo has no practical use for your daily life, why use this module instead of uninstalling Momo?

Some banking apps detect unlocked bootloader. That's all this module is for.

[MissThee]

KSU(11838) and applying this module in LSPosed(1.9.3-7261) to memory detector

Why would you apply BootloaderSpoofer to Memory Detector

I applied the module to both detectors for one possible reason, because I wanted to check if I passed all the checks at the same time. Otherwise, what do you think is the reason why they applied this module to Momo?

Memory Detector does not detect unlocked bootloader. As for native detector, there's no aay to fix it.

So curious why would you install Momo and this module, if only Momo will detect the bootloader, it would be nice to uninstall Momo, Momo has no practical use for your daily life, why use this module instead of uninstalling Momo?

Some banking apps detect unlocked bootloader. That's all this module is for.

KSU(11838) and applying this module in LSPosed(1.9.3-7261) to memory detector

Why would you apply BootloaderSpoofer to Memory Detector

I applied the module to both detectors for one possible reason, because I wanted to check if I passed all the checks at the same time. Otherwise, what do you think is the reason why they applied this module to Momo?

Memory Detector does not detect unlocked bootloader. As for native detector, there's no aay to fix it.

So curious why would you install Momo and this module, if only Momo will detect the bootloader, it would be nice to uninstall Momo, Momo has no practical use for your daily life, why use this module instead of uninstalling Momo?

Some banking apps detect unlocked bootloader. That's all this module is for.

I know that this module is only for the purpose of patching bootoader detection, but using this module exposes another code injection detection. That's really annoying. If the app includes both detection methods, the module will be meaningless. I want to pass all known tests perfectly

[Tobim6]

I know that this module is only for the purpose of patching bootoader detection, but using this module exposes another code injection detection. That's really annoying. If the app includes both detection methods, the module will be meaningless. I want to pass all known tests perfectly

Not possible right now

[DevkanKafkas]

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

However, the application I use somehow detects that the phone is rooted. The only thing that comes to mind is the "MEETS_STRONG_INTEGRITY" check; it might be detecting it from there. As far as I know, there is no way to bypass this, and I am about to lose my mind because of this situation. Supposedly, you can do everything with a rooted phone, but we can't even simulate the data that any application gets from the phone.

@chiteroman did not provide an explanation on the PlayIntegrityFix GitHub page about some devices being able to pass this. Does anyone have information about this?

GitHub - chiteroman/PlayIntegrityFix NOTE: Strong verdict is impossible to pass on unlocked bootloader devices, there are few devices and "exploits" which will allow you to pass it, but, in normal conditions, this verdict will be green only if you are using stock ROM and locked bootloader. The old posts talking about Strong pass was an "exploit" in Google servers, obviously, now it's patched.

[Tobim6]

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

No way you are passing native detector

[Manasx100]

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?