Conflict between frida-tools and prompt-toolkit specified in requirements.txt

[tokit3mx]

INFO: pip is looking at multiple versions of frida-tools to determine which version is compatible with other requirements. This could take a while.
ERROR: Cannot install -r requirements.txt (line 9) and prompt-toolkit==3.0.3 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested prompt-toolkit==3.0.3
    frida-tools 5.3.0 depends on prompt-toolkit<3.0.0 and >=2.0.0

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Basically idk how someone got this working/or never had an issue, but on a fresh download and venv i am unable to install the requirements.
I am inside the venv, and I did use venv/bin/pip3 install -r requirements.txt . Please tell me what to change, as I don't want to mess with the dependencies.

[tokit3mx]

so, i managed to get it running by manually disabling version requirements for frida-tools, frida, prompt-toolkit etc. then pip did its job and after some thinking managed to resolve other conflicts as well. btw use python3.7 . then i tried running it but it looks like you also need ruby for some scripts, AND the app somehow stupidly forces you to use it on an emulator, when it just uses adb commands. so i modified the util.py script to just return true when theres an adb devices, doesnt matter if not emulator. my phone is rooted so it should be fine. tried to run it - it got the apk and modified some things that ive requested. failed to install. i got the apk from tmp, decompiled with apktool, force rebuilt even if no sources changed, manually signed with debug key with a cool tool called uber-apk-signer. it installed. sadly, it doesnt launch, even if no frida-server is in the background, so that means that it broke the app... i confirmed this by returning true when checking if app is installed (the same one), so it will not actually install a new,also broken one, but try to launch it. it also failed. so its a fail.