VideoHelp Forum




+ Reply to Thread
Results 1 to 14 of 14
  1. Hi everybody,

    I am trying to extract a 640 kbps E-AC-3 (6 channels) audio track from a specific VOD platform for a multi-episode series, as I am only interested in the audio stream.

    Here is my current setup and technical logic:
    • Browsing via Chrome or Firefox on PC only yields Widevine L3 manifest profiles, capped at 192 kbps. Similarly, a freshly generated Widevine L3 .wvd file from an Android Studio virtual device is L3 by definition, so the backend strictly limits it to 192 kbps as well.
    • Since L3 cannot trigger the high-bitrate manifest, my objective was to spoof an Android virtual device to masquerade as a Fire TV in order to force the backend to issue the 640 kbps E-AC-3 manifest URL. The plan was then to decrypt the stream using PlayReady SL3000 keys previously obtained on PC (which currently operate at the software/L3 equivalent level in my setup).
    • However, routing the Android emulator through mitmproxy with Frida scripts targeting OkHttp3, Conscrypt, and BoringSSL fails at the splash screen, likely due to native Cronet pinning or Play Integrity checks. Additionally, attempting web-to-hardware payload spoofing via Python returns HTTP 400, confirming a separation between web session tokens and hardware endpoints.
    • Meanwhile, requests made using my PlayReady SL3000 setup (using .dat files to generate a .prd) still result in L3-restricted manifests, making me wonder if my certificate/setup is revoked or missing platform-specific hardware attestation.

    My main questions are:
    1. Is a PC/L3 environment inherently hard-capped at 192 kbps by the backend, or is there a way to force the server to issue the 640 kbps E-AC-3 manifest URL and decrypt it with software-level keys?
    2. Why would a PlayReady SL3000 setup fail to trigger the 640 kbps stream on this endpoint? Is the certificate likely revoked, or does the API enforce hardware TEE attestation for high-bitrate audio?
    3. Has anyone successfully bypassed native Cronet or BoringSSL pinning to extract hardware auth tokens from memory, or successfully spoofed a Fire TV request for this API?

    I am open to any leads or technical insights. If you have experience with this native pinning or hardware spoofing, please send me a PM. I would be extremely grateful for any guidance!

    Thanks in advance.
    Quote Quote  
  2. You've more or less answered your own question, forget devtools and the web - you need to be sniffing the app with mitm (on a tv preferably)
    Quote Quote  
  3. would be easier if we knew what this mystery service was called
    Bypass HMACs, One-time-tokens and Lic.Wrapping: https://github.com/DevLARLEY/WidevineProxy2
    Quote Quote  
  4. It begins with A
    Quote Quote  
  5. Originally Posted by FIRE_Storm View Post
    Hi everybody,

    I am trying to extract a 640 kbps E-AC-3 (6 channels) audio track from a specific VOD platform for a multi-episode series, as I am only interested in the audio stream.

    Here is my current setup and technical logic:
    • Browsing via Chrome or Firefox on PC only yields Widevine L3 manifest profiles, capped at 192 kbps. Similarly, a freshly generated Widevine L3 .wvd file from an Android Studio virtual device is L3 by definition, so the backend strictly limits it to 192 kbps as well.
    • Since L3 cannot trigger the high-bitrate manifest, my objective was to spoof an Android virtual device to masquerade as a Fire TV in order to force the backend to issue the 640 kbps E-AC-3 manifest URL. The plan was then to decrypt the stream using PlayReady SL3000 keys previously obtained on PC (which currently operate at the software/L3 equivalent level in my setup).
    • However, routing the Android emulator through mitmproxy with Frida scripts targeting OkHttp3, Conscrypt, and BoringSSL fails at the splash screen, likely due to native Cronet pinning or Play Integrity checks. Additionally, attempting web-to-hardware payload spoofing via Python returns HTTP 400, confirming a separation between web session tokens and hardware endpoints.
    • Meanwhile, requests made using my PlayReady SL3000 setup (using .dat files to generate a .prd) still result in L3-restricted manifests, making me wonder if my certificate/setup is revoked or missing platform-specific hardware attestation.

    My main questions are:
    1. Is a PC/L3 environment inherently hard-capped at 192 kbps by the backend, or is there a way to force the server to issue the 640 kbps E-AC-3 manifest URL and decrypt it with software-level keys?
    2. Why would a PlayReady SL3000 setup fail to trigger the 640 kbps stream on this endpoint? Is the certificate likely revoked, or does the API enforce hardware TEE attestation for high-bitrate audio?
    3. Has anyone successfully bypassed native Cronet or BoringSSL pinning to extract hardware auth tokens from memory, or successfully spoofed a Fire TV request for this API?

    I am open to any leads or technical insights. If you have experience with this native pinning or hardware spoofing, please send me a PM. I would be extremely grateful for any guidance!

    Thanks in advance.
    i am not professional, but you can disable pinning and other security checks and splash screens if it's from an app by modifying smali codes
    Quote Quote  
  6. Originally Posted by slayer36 View Post
    Originally Posted by FIRE_Storm View Post
    Hi everybody,

    I am trying to extract a 640 kbps E-AC-3 (6 channels) audio track from a specific VOD platform for a multi-episode series, as I am only interested in the audio stream.

    Here is my current setup and technical logic:
    • Browsing via Chrome or Firefox on PC only yields Widevine L3 manifest profiles, capped at 192 kbps. Similarly, a freshly generated Widevine L3 .wvd file from an Android Studio virtual device is L3 by definition, so the backend strictly limits it to 192 kbps as well.
    • Since L3 cannot trigger the high-bitrate manifest, my objective was to spoof an Android virtual device to masquerade as a Fire TV in order to force the backend to issue the 640 kbps E-AC-3 manifest URL. The plan was then to decrypt the stream using PlayReady SL3000 keys previously obtained on PC (which currently operate at the software/L3 equivalent level in my setup).
    • However, routing the Android emulator through mitmproxy with Frida scripts targeting OkHttp3, Conscrypt, and BoringSSL fails at the splash screen, likely due to native Cronet pinning or Play Integrity checks. Additionally, attempting web-to-hardware payload spoofing via Python returns HTTP 400, confirming a separation between web session tokens and hardware endpoints.
    • Meanwhile, requests made using my PlayReady SL3000 setup (using .dat files to generate a .prd) still result in L3-restricted manifests, making me wonder if my certificate/setup is revoked or missing platform-specific hardware attestation.

    My main questions are:
    1. Is a PC/L3 environment inherently hard-capped at 192 kbps by the backend, or is there a way to force the server to issue the 640 kbps E-AC-3 manifest URL and decrypt it with software-level keys?
    2. Why would a PlayReady SL3000 setup fail to trigger the 640 kbps stream on this endpoint? Is the certificate likely revoked, or does the API enforce hardware TEE attestation for high-bitrate audio?
    3. Has anyone successfully bypassed native Cronet or BoringSSL pinning to extract hardware auth tokens from memory, or successfully spoofed a Fire TV request for this API?

    I am open to any leads or technical insights. If you have experience with this native pinning or hardware spoofing, please send me a PM. I would be extremely grateful for any guidance!

    Thanks in advance.
    i am not professional, but you can disable pinning and other security checks and splash screens if it's from an app by modifying smali codes
    ////
    Last edited by FIRE_Storm; 4th Nov 2026 at 14:12.
    Quote Quote  
  7. Stop using AI. There are ways around the cert pinning.
    Quote Quote  
  8. I am sick of these ai responses
    Bypass HMACs, One-time-tokens and Lic.Wrapping: https://github.com/DevLARLEY/WidevineProxy2
    Quote Quote  
  9. I’ve had a quick read – not the whole thing – but the service you want to download the audio from offers, at least for 1080p, CBR video with 5.1 audio at 192 kbps and CVBR video with 5.1 audio at 640 kbps; these are two different manifests.

    Provided I’ve understood correctly and the service is AMZN
    Quote Quote  
  10. Originally Posted by Goku73 View Post
    I’ve had a quick read – not the whole thing – but the service you want to download the audio from offers, at least for 1080p, CBR video with 5.1 audio at 192 kbps and CVBR video with 5.1 audio at 640 kbps; these are two different manifests.

    Provided I’ve understood correctly and the service is AMZN
    Thank you for taking the time to answer! It means I have the CBR, which is normal on a PC I guess. It's still the same issue: I would need to have L1.
    Quote Quote  
  11. If I remember correctly, 1080p videos in H.265 are only available in CVBR, and in theory, if you use that manifest, the audio should be EAC3 5.1 at 640 kbps, so you’d just need to change the codec setting. I don’t know what you’re using to download them, but with StreamFab, VineTrimmer, Unshackle and all their clones, you can easily download the video, audio and subtitles of your choice.

    I’d just like to remind you that amzn often bans the accounts of people who try to download from their site, so use an account you don’t mind losing
    Quote Quote  
  12. Actually you don't need L1
    Quote Quote  
  13. use unshackle
    or if .mpd comes from a browser (WidevineProxy2), you'll need to modify it to get 640 kbps
    remove
    Code:
    dm/3$....../
    Quote Quote  
  14. Member
    Join Date
    Feb 2026
    Location
    China
    Search Comp PM
    CVBR gets 640k DDP5.1 on AMZN and with SL3000
    Quote Quote  



Similar Threads