Dumping from SDK 34
Closed this issue · 4 comments
I installed ghidra but where can I find the elf binary to load onto it? Searched for 'widevine' and 'elf' in program folder and sdk but cannot find it. The functions.md does not hint at where it can be found.
The binary to analyze in ghidra is the widevine binary of your device. To find out which one it is, you must launch the script for the first time and retrieve the binary indicated locally via ADB.
Sometimes this is not necessary because the SDK may be 34 but the integrated Widevine version is older. Use the script with a functions file only if the script indicates so (puts a warning/error)
The binary to analyze in ghidra is the widevine binary of your device. To find out which one it is, you must launch the script for the first time and retrieve the binary indicated locally via ADB.
Sometimes this is not necessary because the SDK may be 34 but the integrated Widevine version is older. Use the script with a functions file only if the script indicates so (puts a warning/error)
Thanks for that. Retrieving the binary from adb is in itself a seperate step and including that in the functions.md could be of immense help to newbies.
Also the script gets stuck on hooks completed but no key is generated, and chrome/bitmovin page becomes unresponsive.
I plan to do a big update to the library and create a generic way to dump CDMs from an updated version of the player Axinom. The doc will be updated at that time but I will take your comment into account.
Can you send as an attachment the text result displayed in the console of your terminal so that I can look at what is blocking.
Don't hesitate to ping me directly on discord (same username) for live debugging (sometimes simpler)
Problem resolved via discord discussion. The position of the device_id argument for SDK 34 and above needs to be dynamic/auto-detected. Solution to be implemented in the next update.