Dumping Your own L3 CDM with Android Studio

[charlieorwell]

Hello, I was wondering if anyone is able to help with the error i'm getting?


[Attachment 72845 - Click to enlarge]

I think I'm at the stage of using the dumper-main to get the keys but I'm getting stuck with the error above.

EDIT:

after downgrading protobuf it worked, thanks for the tutorial!

[chinn216]

Thanks a lot! After downgrade Python to 3.10.7 finally I got the two migic files

[Karoolus]

Search this thread, the answer is in here somewhere

[DragunMan]

Hey, new to the site. Im running the latest version of python and pip and frida. however, when I go to install frida, I get the same error message. any help would be appreciated.
[Attachment 73053 - Click to enlarge]
[Attachment 73054 - Click to enlarge]

[qruetry]

does this method still produce working l3 cdm ? , have run the process twice to produce 2 different file sets "client_id" and "private_key.pem" ..... have renamed the 2 files to " device_client_id_blob" and "device_private_key" respectivly and place these files in the folder L3\cdm\devices\android_generic folder. have copied bash url converted to headers.py file , run l3.py am able to enter pssh and licence url both times have run into the following error

no client ID blob available for this device

Header: 

PSSH: AAAAVnBzc2gAAAAA7e+LqXnWSs6jyCfc1R0h7QAAADYIARIQ8hNTzeGOTayckD5Lc4sBSBoNd2lkZXZpbmVfdGVzdCIIMTIzNDU2NzgyB2RlZmF1bHQ=

License URL: https://manifest.prod.boltdns.net/license/v1/cenc/widevine/1555966122001/982ce523-a4b1-4a94-91c6-c7a9a8b082f8/f21353cd-e18e-4dac-9c90-3e4b738b0148?fastly_token=NjRmODdhZjNfZjJjYjY1NmNlNWRiYmQ1MThmMmY3ZTRhNGQ5MTc1NmRhMTFmZDI5NGU4ZGE3ODYwM2VmOTlkMDkxYTAxYTljNg%3D%3D

assuming this error, means script does not like my cdm , for some reason ?

[Magicians]

does this method still produce working l3 cdm ? , have run the process twice to produce 2 different file sets "client_id" and "private_key.pem" ..... have renamed the 2 files to " device_client_id_blob" and "device_private_key" respectivly and place these files in the folder L3\cdm\devices\android_generic folder. have copied bash url converted to headers.py file , run l3.py am able to enter pssh and licence url both times have run into the following error

no client ID blob available for this device

Header: 

PSSH: AAAAVnBzc2gAAAAA7e+LqXnWSs6jyCfc1R0h7QAAADYIARIQ8hNTzeGOTayckD5Lc4sBSBoNd2lkZXZpbmVfdGVzdCIIMTIzNDU2NzgyB2RlZmF1bHQ=

License URL: https://manifest.prod.boltdns.net/license/v1/cenc/widevine/1555966122001/982ce523-a4b1-4a94-91c6-c7a9a8b082f8/f21353cd-e18e-4dac-9c90-3e4b738b0148?fastly_token=NjRmODdhZjNfZjJjYjY1NmNlNWRiYmQ1MThmMmY3ZTRhNGQ5MTc1NmRhMTFmZDI5NGU4ZGE3ODYwM2VmOTlkMDkxYTAxYTljNg%3D%3D

assuming this error, means script does not like my cdm , for some reason ?

You did not rename them properly. Guaranteed your "device_client_id_blob" has a extension on the end.

[qruetry]

hmmm just seeing that myself still associated as a bin file , got the pem off of other file... ok thanks had to show file extensions options and trim file as rename... thanks ... both are "file"file types now

[RandomUser123]

Hi! Thanks for this thread!

I don't know if my problem have already been aswered but I'm stuck at dumper step...
After "Python dump_keys.py" step i got this error: "frida.ServerNotRunningError: unable to connect to remote frida-server: closed"
My frida-server is (16.1.2).
Anyone can help me?

Edit: Nevermind! I solved my problem.

I have the same problem. How did u solve it?


Edit: NVM, found the solution:

[Attachment 72347 - Click to enlarge]

how can i fix "unable to connect to remote frida-server: closed"

You need to have the frida server running in a separate command window in the background as per the instructions in the guide -- do not close this window once you execute the last command in the sequence shown (click to follow the link).
[Attachment 68356 - Click to enlarge]

[Silverselo]

Hey this is what happens when I try to start the frida server.

[Attachment 73182 - Click to enlarge]

[Karoolus]

Hey this is what happens when I try to start the frida server.

[Attachment 73182 - Click to enlarge]

Read the error messages.

The file you're copying to your phone/emulator does not exist (wrong name) so all subsequent commands also do nothing

You also need to be root to do all this, so first of all type

su
mv /sdcard/frida-server-16-1-3-android-x86 / data/local/tmp
chmod +x /data/local/tmp/frida-server-16-1-3-android-x86
/data/local/tmp/frida-server-16-1-3-android-x86

[koberulz]

I can't even get the emulator to open...it says the phone is running, but it errors when I try to stop it and it's invisible and I don't seem to be able to do anything with it.

[qruetry]

if am still getting protobuf errors after running l3.py, "client id failed to parse as protobuf" do i need to downgrade from 3.20.1 to protobuf==3.19.5 ?

[cedric8528]

I can't even get the emulator to open...it says the phone is running, but it errors when I try to stop it and it's invisible and I don't seem to be able to do anything with it.

If you have an Intel Processor, install Intel HAXM via Sdk Manager or Manually.

https://github.com/intel/haxm/wiki/Installation-Instructions-on-Windows

[koberulz]

Didn't help.

[NBA456017]

I can't even get the emulator to open...it says the phone is running, but it errors when I try to stop it and it's invisible and I don't seem to be able to do anything with it.

protobuf==3.20.0
should be ok

[koberulz]

I don't know what that means.

[HJPM]

Greetings, videofriends. I was following the guide, and initially I got the infamous line errors with the dumper script. Using protobuf 3.20.3 and
pycryptodome 3.16.0 seemed to fix that problem. I am able to push the frida sever file, or so it seems. I don't know if I'm supposed to push the dll or the xr, but once I go the SU step of moving and running it, it doesn't work. With either the compressed or uncompressed file.

[Karoolus]

dll or xr file? I'm confused.
Post your commands (and if you can, screenshots as well)

[vladimir1919]

Please! help me download video from kinescope


I will pay money. very urgently needed

[jammesvx]

dump_keys.py
2023-08-18 02:18:00 AM - root - 15 - INFO - Connected to Pixel C
2023-08-18 02:18:00 AM - root - 16 - INFO - scanning all processes for the following libraries
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1, name="init", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=143, name="init", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=144, name="init", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=146, name="ueventd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=168, name="logd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=169, name="servicemanager", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=170, name="hwservicemanager", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=171, name="vndbinder", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=174, name="android.hardware.keymaster@3.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=175, name="vold", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=224, name="redis", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=225, name="su", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=226, name="zygote", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=227, name="cameraserver", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=228, name="drmserver", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=230, name="incidentd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=231, name="installd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=232, name="keystore", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=233, name="mediadrmserver", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=234, name="media.extractor", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=235, name="media.metrics", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=236, name="mediaserver", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=237, name="netd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=238, name="statsd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=239, name="storaged", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=241, name="wificond", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=242, name="android.hardware.media.omx@1.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=243, name="rild", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=245, name="gatekeeper", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=246, name="perfprofd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=247, name="tombstoned", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=249, name="adbd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=271, name="createns", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=318, name="mdnsd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=344, name="simulated_hostapd.conf", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=481, name="local_opengl", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=483, name="local_camera", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=484, name="local_camera", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=485, name="batteryd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=496, name="android.hidl.allocator@1.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=497, name="android.hardware.audio@2.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=498, name="android.hardware.camera.provider@2.4-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=499, name="android.hardware.cas@1.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=500, name="android.hardware.configstore@1.1-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=501, name="android.hardware.drm@1.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=502, name="android.hardware.gnss@1.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=503, name="android.hardware.graphics.allocator@2.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=504, name="android.hardware.graphics.composer@2.1-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=505, name="android.hardware.health@2.0-service.genymotion", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=506, name="android.hardware.light@2.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=507, name="android.hardware.memtrack@1.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=508, name="android.hardware.power@1.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=509, name="android.hardware.sensors@1.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=510, name="android.hardware.wifi@1.0-service", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=511, name="audioserver", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=512, name="diskiod", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=513, name="genybaseband", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=514, name="lmkd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=515, name="network_profile", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=516, name="settingsd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=517, name="surfaceflinger", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=518, name="systempatcher_native", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=519, name="thermalserviced", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=520, name="vinput", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=528, name="genybaseband", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=543, name="system_server", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=629, name="logcat", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=631, name="sh", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=739, name="com.android.inputmethod.latin", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=758, name="com.android.systemui", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=797, name="webview_zygote", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=876, name="wpa_supplicant.conf", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=877, name="com.android.phone", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=894, name="Settings", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=959, name="android.ext.services", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1151, name="com.android.cellbroadcastreceiver", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1185, name="Phone", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1204, name="android.process.acore", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1263, name="Clock", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1309, name="com.genymotion.settings", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1329, name="com.genymotion.systempatcher", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1355, name="com.android.se", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1362, name="com.genymotion.tasklocker", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1380, name="com.genymotion.genyd", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1405, name="android.process.media", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1418, name="com.android.launcher3", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1440, name="com.android.smspush", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1522, name="com.android.printspooler", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1563, name="com.android.providers.calendar", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1578, name="com.android.keychain", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1609, name="Email", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1637, name="com.android.managedprovisioning", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1658, name="Messaging", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1685, name="com.android.onetimeinitializer", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1725, name="com.android.packageinstaller", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1752, name="com.android.traceur", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1771, name="Superuser", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1792, name="Search", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1840, name="iptables-restore", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1841, name="ip6tables-restore", parameters={})
2023-08-18 02:18:01 AM - root - 18 - DEBUG - Process(pid=1863, name="sh", parameters={})
2023-08-18 02:18:01 AM - root - 19 - INFO - Hooks completed

i'm don't see to device_client_id_blob
device_private_key

[HJPM]

dll or xr file? I'm confused.
Post your commands (and if you can, screenshots as well)

The Frida releases from the guide's link are archived dlls. The adb.exe push command doesn't work, at least on my end, without specifying the extension as well. Although both are successfully pushed, archived or not, they give the same type of error:

error: PS C:\Users\**redacted**\AppData\Local\Android\Sdk\platform-tools> ./adb shell
generic_x86_arm:/ $ mv /sdcard/frida-server_yourversionfrida-clr-16.1.3-windows-x86.dll.xr/data/local/tmp
/data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xrmv: Need 2 arguments (see "mv --help")
1|generic_x86_arm:/ $ chmod  +x /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
chmod: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: No such file or directory
1|generic_x86_arm:/ $ /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/system/bin/sh: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: not found
127|generic_x86_arm:/ $ su
rida-clr-16.1.3-windows-x86.dll.xr /data/local/tmp
chmod  +x /data/local/tmp/frgeneric_x86_arm:/ # mv /sdcard/frida-clr-16.1.3-windows-x86.dll.xr /data/local/tmp
ida-clr-16.1.3-windows-x86.dll.xr
/data/local/tmp/frida-clr-16.1.3mv: bad '/sdcard/frida-clr-16.1.3-windows-x86.dll.xr': No such file or directory
-1|generic_x86_arm:/ # chmod  +x /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
windows-x86.dll.xrchmod: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: No such file or directory
1|generic_x86_arm:/ # /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/system/bin/sh: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: not found
127|generic_x86_arm:/ #
PS C:\Users\**redacted**\AppData\Local\Android\Sdk\platform-tools>

[Karoolus]

dll or xr file? I'm confused.
Post your commands (and if you can, screenshots as well)

The Frida releases from the guide's link are archived dlls. The adb.exe push command doesn't work, at least on my end, without specifying the extension as well. Although both are successfully pushed, archived or not, they give the same type of error:

error: PS C:\Users\**redacted**\AppData\Local\Android\Sdk\platform-tools> ./adb shell
generic_x86_arm:/ $ mv /sdcard/frida-server_yourversionfrida-clr-16.1.3-windows-x86.dll.xr/data/local/tmp
/data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xrmv: Need 2 arguments (see "mv --help")
1|generic_x86_arm:/ $ chmod  +x /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
chmod: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: No such file or directory
1|generic_x86_arm:/ $ /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/system/bin/sh: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: not found
127|generic_x86_arm:/ $ su
rida-clr-16.1.3-windows-x86.dll.xr /data/local/tmp
chmod  +x /data/local/tmp/frgeneric_x86_arm:/ # mv /sdcard/frida-clr-16.1.3-windows-x86.dll.xr /data/local/tmp
ida-clr-16.1.3-windows-x86.dll.xr
/data/local/tmp/frida-clr-16.1.3mv: bad '/sdcard/frida-clr-16.1.3-windows-x86.dll.xr': No such file or directory
-1|generic_x86_arm:/ # chmod  +x /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
windows-x86.dll.xrchmod: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: No such file or directory
1|generic_x86_arm:/ # /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/system/bin/sh: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: not found
127|generic_x86_arm:/ #
PS C:\Users\**redacted**\AppData\Local\Android\Sdk\platform-tools>

You are downloading the wrong version.

You need frida-server-android-x86
Not the Windows version

[HJPM]

dll or xr file? I'm confused.
Post your commands (and if you can, screenshots as well)

The Frida releases from the guide's link are archived dlls. The adb.exe push command doesn't work, at least on my end, without specifying the extension as well. Although both are successfully pushed, archived or not, they give the same type of error:

error: PS C:\Users\**redacted**\AppData\Local\Android\Sdk\platform-tools> ./adb shell
generic_x86_arm:/ $ mv /sdcard/frida-server_yourversionfrida-clr-16.1.3-windows-x86.dll.xr/data/local/tmp
/data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xrmv: Need 2 arguments (see "mv --help")
1|generic_x86_arm:/ $ chmod  +x /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
chmod: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: No such file or directory
1|generic_x86_arm:/ $ /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/system/bin/sh: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: not found
127|generic_x86_arm:/ $ su
rida-clr-16.1.3-windows-x86.dll.xr /data/local/tmp
chmod  +x /data/local/tmp/frgeneric_x86_arm:/ # mv /sdcard/frida-clr-16.1.3-windows-x86.dll.xr /data/local/tmp
ida-clr-16.1.3-windows-x86.dll.xr
/data/local/tmp/frida-clr-16.1.3mv: bad '/sdcard/frida-clr-16.1.3-windows-x86.dll.xr': No such file or directory
-1|generic_x86_arm:/ # chmod  +x /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
windows-x86.dll.xrchmod: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: No such file or directory
1|generic_x86_arm:/ # /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/system/bin/sh: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: not found
127|generic_x86_arm:/ #
PS C:\Users\**redacted**\AppData\Local\Android\Sdk\platform-tools>

You are downloading the wrong version.

You need frida-server-android-x86
Not the Windows version

Frida-server-android-x86 appears to only be source files. Regardless, the sample command "adb.exe push frida-server-16.0.2-android-x86 /sdcard" continues to not run unless I also specify the file extension. Once I get to the final, mv command, I get this error:

/system/bin/sh: /data/local/tmp/frida-core-devkit-16.1.3-android-x86.tar.xz: not executable: magic FD37

[Karoolus]

dll or xr file? I'm confused.
Post your commands (and if you can, screenshots as well)

The Frida releases from the guide's link are archived dlls. The adb.exe push command doesn't work, at least on my end, without specifying the extension as well. Although both are successfully pushed, archived or not, they give the same type of error:

error: PS C:\Users\**redacted**\AppData\Local\Android\Sdk\platform-tools> ./adb shell
generic_x86_arm:/ $ mv /sdcard/frida-server_yourversionfrida-clr-16.1.3-windows-x86.dll.xr/data/local/tmp
/data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xrmv: Need 2 arguments (see "mv --help")
1|generic_x86_arm:/ $ chmod  +x /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
chmod: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: No such file or directory
1|generic_x86_arm:/ $ /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/system/bin/sh: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: not found
127|generic_x86_arm:/ $ su
rida-clr-16.1.3-windows-x86.dll.xr /data/local/tmp
chmod  +x /data/local/tmp/frgeneric_x86_arm:/ # mv /sdcard/frida-clr-16.1.3-windows-x86.dll.xr /data/local/tmp
ida-clr-16.1.3-windows-x86.dll.xr
/data/local/tmp/frida-clr-16.1.3mv: bad '/sdcard/frida-clr-16.1.3-windows-x86.dll.xr': No such file or directory
-1|generic_x86_arm:/ # chmod  +x /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
windows-x86.dll.xrchmod: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: No such file or directory
1|generic_x86_arm:/ # /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr
/system/bin/sh: /data/local/tmp/frida-clr-16.1.3-windows-x86.dll.xr: not found
127|generic_x86_arm:/ #
PS C:\Users\**redacted**\AppData\Local\Android\Sdk\platform-tools>

You are downloading the wrong version.

You need frida-server-android-x86
Not the Windows version

Frida-server-android-x86 appears to only be source files. Regardless, the sample command "adb.exe push frida-server-16.0.2-android-x86 /sdcard" continues to not run unless I also specify the file extension. Once I get to the final, mv command, I get this error:

/system/bin/sh: /data/local/tmp/frida-core-devkit-16.1.3-android-x86.tar.xz: not executable: magic FD37

you're not reading what I said.. You need the SERVER files, not the core devkit.

This is the one you're after:
https://github.com/frida/frida/releases/download/16.1.3/frida-server-16.1.3-android-x86.xz

Unpack it first, you need to end up with a file "without an extension"

Then run the adb commands and the shell commands

[XxDarkus101Xx]

ok got a little problem, when I try to use the "dump_keys.py" it just opens and it automatically closes. When I open up cmd in the dump keys directory and type in python3 dump_keys.py in the cmd, it says "Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases." Is there a way to fix this please?

[Karoolus]

ok got a little problem, when I try to use the "dump_keys.py" it just opens and it automatically closes. When I open up cmd in the dump keys directory and type in python3 dump_keys.py in the cmd, it says "Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases." Is there a way to fix this please?

Install Python and make sure it's added to the environment PATH variable.
Google it to get more information, it'll make more sense that way

[XxDarkus101Xx]

ok got a little problem, when I try to use the "dump_keys.py" it just opens and it automatically closes. When I open up cmd in the dump keys directory and type in python3 dump_keys.py in the cmd, it says "Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases." Is there a way to fix this please?

Install Python and make sure it's added to the environment PATH variable.
Google it to get more information, it'll make more sense that way

I have the latest python version installed 3.11.4.. Its in the location "AppData\Local\Programs\Python\Python311"

[Karoolus]

Google how to add it to the PATH, it's not that hard but it'll be easier if you see screenshots or a video

[XxDarkus101Xx]

sorry ignore that last message hopefully I did it right

[XxDarkus101Xx]

[Attachment 73242 - Click to enlarge]
ok Its still saying the same thing. This is what I did as following the video.