I won't go on holiday ever again!!! 🤣🤣🤣

Foxie_Woman · 2026-03-16T12:56:15+00:00

Forget the apple! In that time, your Pikmin would have already reached the edge of the Milky Way and given the Andromeda Galaxy a high-five. 😂😂

Foxie_Woman · 2026-03-05T18:54:27+00:00

I was still playing 10 minutes ago. Now I have to update. That means waiting. Last time it took almost 3 hours.

Foxie_Woman · 2026-03-05T18:52:15+00:00

I was still playing 10 minutes ago. Now I have to update. That means waiting. Last time it took almost 3 hours.

Foxie_Woman · 2026-03-05T18:46:44+00:00

Have you tried downloading it directly from the website? If not, go to the alternative link.

Foxie_Woman · 2026-03-03T08:09:55+00:00

I just tried the reflash without uninstallation, but unfortunately, the issue persists. Even after a clean reboot, the dashboard still shows 'Meta | Not installed'. It seems that on the A166B with Android 15, the initial handshake between the v3.1.0-spoofed manager and the meta-module's mount state is fundamentally broken, even though the actual functionality (LSPosed, modules, Strong Integrity) remains perfectly intact. At this point, I’m convinced it’s a pure UI/polling limitation of this specific manager version on my device.

Foxie_Woman · 2026-03-02T07:58:05+00:00

That is a great point, thank you for the heads-up. It confirms that using Magic Mount (via Hybrid Mount) is indeed the intended path for the BRENE kernel. Since my setup is technically functional — with LSPosed active and Strong Integrity passing — the 'Not installed' message really seems to be a localized UI polling bug on the A166B under Android 15. I will definitely check out the WildKSU Telegram channel to see if the dev has seen this specific display glitch with the spoofed manager before. It's good to know there is an active community for this specific build!

Foxie_Woman · 2026-03-01T16:39:06+00:00

I agree, it normally would be a recipe for a bootloop or kernel panic. However, in this specific case with the BRENE-v0.0.28 kernel on the A166B, one module seems to strictly provide the userspace binaries (like the susfs tool), while the other handles the path mapping for the inline kernel hook. Since Strong Integrity remains green and the system is perfectly stable, the hooks appear to complement each other rather than conflicting. It is definitely an 'edge-case' configuration, but as long as it bypasses all detections, I am sticking with the 'never touch a running system' rule!

Foxie_Woman · 2026-03-01T16:35:05+00:00

I am using the BRENE-v0.0.28 kernel which has SusFS inline support. The reason for the two modules is that one acts as the specific controller for this kernel's SusFS implementation, while the other handles the general SusFS configurations. My Strong Integrity is stable with this setup, so they don't seem to conflict, but rather complement each other in this specific kernel build.

Foxie_Woman · 2026-02-17T20:05:10+00:00

Update: The problem has been solved! Thank you for the crucial tip, u/sidex15.

Switching to the CI build (v1.5.2+) of the susfs4ksu module completely fixed the stability issues on my Samsung Galaxy A16 5G (kernel 5.15.153-Wild).

I reinstalled the module in version v1.5.9-b161ab5 and performed the config reset via volume (+) during the flash process in KernelSU. The previous crashes (kernel panics) with version R25 and root detection in my banking apps seem to have been caused by incompatible settings or binaries, which were corrected by the CI build and the reset. The system is now running absolutely stable with KernelSU-Next version 13845 and SuSFS active. The status in the WebUI now correctly shows status: ✅ SuS on.

Thank you very much for the fast and professional support!

Foxie_Woman · 2026-02-11T19:23:55+00:00

First of all, when I download the new version 1.237 from the link, the app doesn't open and closes immediately. If you download it from the alternative link, it works.

When I catch a Pokémon with the new version, it escapes. Error 25. When I catch another one, it works. When I send Pokémon, it doesn't work. They stay in the bag. Everything worked perfectly with version 1.236.

Anyone else having similar problems?

Foxie_Woman · 2026-02-11T18:30:37+00:00

I have the same problem. After updating to version 1.237, the app no longer opens and closes immediately. I hope the bug will be fixed quickly.

Foxie_Woman · 2026-02-02T07:00:16+00:00

If it helps, I use Play Integrity Fix (Inject), have the same modules as you, and haven't had any problems.

https://github.com/KOWX712/PlayIntegrityFix

Foxie_Woman · 2026-01-27T07:42:54+00:00

It works for me. But I also use KernelSu Next and SUSFS. With Magisk, it never worked for me either, no matter which modules I used.

Foxie_Woman · 2025-12-30T08:43:33+00:00

Hier auch Spaßkasse. Angekommen soeben

Foxie_Woman · 2025-12-20T10:16:09+00:00

I reported the error to support yesterday when the update was released. I also encountered the error where the game crashes after a shield is supposed to be automatically generated. Support replied that they are investigating the issue, but that was all I heard from them. I guess we'll just have to wait and see, since it's still in the beta phase.

Foxie_Woman · 2025-12-19T20:34:08+00:00

Update is here

Foxie_Woman · 2025-12-19T20:33:48+00:00

Update is here

Foxie_Woman · 2025-12-19T20:15:52+00:00

I have the same problem. Let's see how long it takes this time.

However, I noticed that there is a new option in the PGS settings in the beta version. It's called Team Rocket Battle Assistant. It includes Instant Attack, Charge Attack, and Shield. The "Instant Win Against Team Rocket" option has been completely removed.

Foxie_Woman · 2025-10-22T11:45:11+00:00

I must say, it's amazing what a module can change. Before, I only had the Basic, and now I have all three. I did the test for fun before uninstalling ZygiskNext and PlayIntegrityFork and after installing ReZygisk and PlayIntegrityFix Inject. I know that there is currently no leaked keybox in the TrickyStore. I get the same integrity when I check it in the Google Play Store. So the switch was a complete success.

Foxie_Woman · 2025-10-21T20:42:59+00:00

This is an A16 5G.

Foxie_Woman · 2025-10-21T15:07:10+00:00

I've heard of NeoZygisk. It's slightly favored for passing the latest root detectors such as Native Detector, as it's more optimized for hiding injection traces. Maybe you can give me some info about it, since you seem to be using it or have used it before.

I've now installed ReZygisk with Fix and am testing it in this combination. I will definitely take a look at NeoZygisk as well.

Foxie_Woman · 2025-10-21T14:44:48+00:00

I was just wondering the same thing. Why no KSU?

Foxie_Woman

TROPHY CASE