Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support KernelSU & fix broken Frida server launch #46

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

enovella
Copy link
Contributor

Screenshot 2024-01-27 at 23 15 36 Screenshot 2024-01-27 at 23 08 46

@enovella
Copy link
Contributor Author

@ViRb3 for viz

@ViRb3
Copy link
Owner

ViRb3 commented Feb 12, 2024

Will take a look the next few days, sorry been very busy.

@ys1231
Copy link

ys1231 commented Feb 12, 2024

Understand, the Chinese New Year is busy.

@ViRb3
Copy link
Owner

ViRb3 commented Feb 14, 2024

@enovella Why does the auto restart loop not work for you? I see no reason why it wouldn't work.

@enovella
Copy link
Contributor Author

@enovella Why does the auto restart loop not work for you? I see no reason why it wouldn't work.

It doesn't work in any of my devices (7-8 laying around). Frida is simply not available after boot with the while-true loop.

@enovella
Copy link
Contributor Author

@ViRb3 Any plans to review this PR? Otherwise, I can create a fork and continue adding changes over there. Let me know.

@ViRb3
Copy link
Owner

ViRb3 commented Apr 10, 2024

@enovella Sorry, meant to test myself but got side tracked. I just pulled out my OnePlus 5T running Elixir OS 2.1 (Android 12L), Magisk 27.0, MagiskFrida 16.2.1. It works perfectly as I can debug applications from my computer over USB, and I can also see the process inside a shell in the phone:

$ adb shell
OnePlus5T:/ $ pgrep -l frida
3938 frida-server

What exact setup did you test across your devices? I honestly find it very strange for the daemonization to work and regular blocking mode not.

@liangjaden
Copy link

这个PR会继续跟进不?期待能支持kernelsu

@sha3rawi33
Copy link

bump

@nEdAy
Copy link

nEdAy commented May 24, 2024

looking forward to it supporting KernelSU.

@ViRb3
Copy link
Owner

ViRb3 commented May 24, 2024

Can all of you please let me know whether the current MagiskFrida with auto restart loop works for you, and you are able to debug apps on your phone using Frida on your PC? I am happy to merge this PR but I want to figure out the problem @enovella is experiencing.

@enovella
Copy link
Contributor Author

Can all of you please let me know whether the current MagiskFrida with auto restart loop works for you, and you are able to debug apps on your phone using Frida on your PC? I am happy to merge this PR but I want to figure out the problem @enovella is experiencing.

I already mentioned several times that this auto-restart loop didn't work for me. The phone didn't respond to Frida upon booting and this was tested in so many devices. The idea is to use the flag to daemonize Frida (-D) instead of blindly restarting Frida.

@ViRb3
Copy link
Owner

ViRb3 commented May 24, 2024

Yeah, I know it doesn't work for you, but it works for me this is the confusing part. So I am asking other people, apart from you and me, to test as well and we can get a better picture. I don't want to make changes without fully understanding them. There's no reason why daemonizing or not should make a difference. If you have a theory, I am happy to hear it.

@liangjaden
Copy link

liangjaden commented May 24, 2024 via email

@ViRb3
Copy link
Owner

ViRb3 commented May 24, 2024

@liangjaden can you test the latest official magisk-frida release, not this PR? Link: https://github.com/ViRb3/magisk-frida/releases/download/16.2.5-1/MagiskFrida-16.2.5-1.zip

@liangjaden
Copy link

liangjaden commented May 24, 2024 via email

@ys1231
Copy link

ys1231 commented May 27, 2024

@enovella His problem can be solved by ending the server process once, and the loop can also work normally

@liangjaden
Copy link

@ViRb3 After testing, the latest version is working on my phone

@enovella
Copy link
Contributor Author

@ys1231 "his" problem? Do you mean the current loop? I don't have problems with the PR in so many devices (many running Pixel OS or Experience).

@ViRb3 Have you tried your loop in more devices and ROMs?

@enovella
Copy link
Contributor Author

@enovella His problem can be solved by ending the server process once, and the loop can also work normally

But this would be ugly, wouldn't it?

@ys1231
Copy link

ys1231 commented May 28, 2024

This is a probability problem. Sometimes it won't happen, as long as it works,My mobile phone models are pixel3xl and pixel6.

@ViRb3
Copy link
Owner

ViRb3 commented May 28, 2024

@enovel unfortunately I only have one device at hand. The stable version of this package has used the loop for over a year and you're the first person to say it doesn't work, so I am just very confused why. I really want to get to the bottom of this before making any changes. I will try to run a different ROM over the next few days, also I'll also try an emulator.

For anyone reading this ticket, please also test and let me know.

@enovella
Copy link
Contributor Author

@ViRb3 In this case, you can merge the PR with changes and leave your loop until we find a working 100% solution for everyone. Is my PR working on your device?

@enovella
Copy link
Contributor Author

@ViRb3 any news?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants