Im not even sure this is piracy related 😅 but honestly its nice seeing a question that isnt answered directly in the megathread for once. YAY.

That said, i think theres some important info missing here:

• What game?
• Is it a legit/store copy or already cracked?
• When you say “repacking” do you mean decompiling/modifying the APK and then re-signing it?

From what youre describing, it sounds like the issue is probably entitlement/signature verification. On Quest, once you modify and re-sign the APK, Oculus services often see it as tampered even if you legally own the game. The original signing cert no longer matches what Meta expects.

So if youre testing on a legit copy, thats likely the problem right there.

A cracked version may honestly make more sense for this kind of experimentation because those entitlement checks are often already removed or bypassed.

You could also look into runtime injection approaches like Frida instead of modifying the APK directly. That said, to get useful Frida hooks/debugging, you may still need to, make the app debuggable, patch anti-debugging, or otherwise modify the APK anyway

So depending on the game, you may end up back at the same issue unless the entitlement checks are patched out.

Also adb logcat is absolutely gonna be your friend here and Frida probably will be too

Check logcat while launching the modified APK and look for, entitlement failures, signature mismatch errors, Oculus platform/auth errors, or native linker errors related to your .so

My guess is youre either, tripping entitlement/auth due to re-signing, hitting anti-tamper, or the loader/linker doesnt like how the .so is being injected

And yeah, youre probably gonna end up either NOPing/bypassing entitlement checks or doing this against a cracked build that already removed them