BanG Dream! Ave Mujica dump submitted

[hinachan0604]

Hello,

I've been experiencing a 'The volume key is unknown for this disc - video can't be decrypted' for a disc that released today. I've included here the aacs dump file (as well as emailed it).

I've also tried SamuelHL's KeyDB Helper and the Validation results are here

Validating disc...
-----------------------------------------------------------
10:45:58 - ----------- FindVUK 1.82 -----------
-----------------------------------------------------------
To close FindVUK simply press the ESC key
-----------------------------------------------------------
10:45:58 - MODE: ValidateDisc

10:45:58 - DriveLetter : F

[removed information for privacy]
-------------------------------------------------------------------------------
10:46:03 - Get basic AACS data
-------------------------------------------------------------------------------
10:46:03 - AACS folder on disc is reachable - Validate is possible
10:46:05 - VolumeName >BRMM_10925<
10:46:05 - DiscId >BEA866155DE5A6B6E61AE378EDE1CA96C8A7C840< (2025-04-29)
10:46:05 - DiscType >BD<
10:46:05 - MKB Revision >82<
10:46:05 - Disc-BusEncEnabled >0<
10:46:05 - Drve-BusEncCapable >1<
10:46:05 - UnitKeyCount >1<
10:46:05 - >>> UnitKeyENC (1) >EB7375468FB6F253D6BE49150D21372F<
10:46:05 - No entry for discid >BEA866155DE5A6B6E61AE378EDE1CA96C8A7C840< available in keydb >C:\Users\XXXXXX\AppData\Roaming\aacs\KEYDB.cfg< - no validation possible!
10:46:05 - Eject the disc now from drive >F:\<

10:46:09 - Successfully ejected the media in drive F!

The makemkv scan is here:

MakeMKV v1.18.1 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\XXXXXXX/MakeMKV_log.txt
DEBUG: Code 0 at nL7S/S~8]V3nmf3\:121264257
Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
This disc uses newer version of AACS protection. Please let us know about it by visiting http://www.makemkv.com/a/?4zj6YVMERQEwfP...
Saved AACS dump file as C:\Users\XXXXXX/.MakeMKV/MKB_v82_TVアニメ「BanG_Dream!_Ave_Mujica」Blu-ray_下巻_7DDE.tgz
The volume key is unknown for this disc - video can't be decrypted
DEBUG: Code 0 at `{q#WHE]"p5'4|CK:213132721
DEBUG: Code 0 at `{q#WHE]"p5'4|CK:213131341
Failed to open disc

As well as my disc drive information and others.

Drive Information
OS device name: F:
Current profile: BD-ROM
Manufacturer: BUFFALO
Product: Optical Drive
Revision: BN14
Serial number: MO7M1J95330
Firmware date: 2121-06-21 13:33
Bus encryption flags: 1F
Highest AACS version: 82

LibreDrive Information
Status: Possible, not yet enabled
Drive platform: MT1959

Disc Information
Label: BRMM_10925
Timestamp: 2025-04-29 18:24:27
Protection: AACS v82
Data capacity: 41.59 Gb
Disc type: BD-ROM
Number of layers: 2
Channel bit length: 74,5 nm (25.0 GB max. per layer)

I found it quite odd, for this is the second volume of two volumes that released together, I was able to rip the first disc without any problems.

[SamuriHL]

Are you using the disc info button? That's what will find the key. You also have to follow the instructions to add the device key to your keydb.cfg file as my tool does not contain any keys. The instructions are in the post you downloaded the tool from. Use the disc info button to generate the key in the keydb. Then it'll run validate to upload the key for you.

Sent from my SM-S938U1 using Tapatalk

[hinachan0604]

Are you using the disc info button? That's what will find the key. You also have to follow the instructions to add the device key to your keydb.cfg file as my tool does not contain any keys. The instructions are in the post you downloaded the tool from. Use the disc info button to generate the key in the keydb. Then it'll run validate to upload the key for you.

Sent from my SM-S938U1 using Tapatalk

I did do disc info. My apologies for forgetting to include that information. Still wasn't able to rip the disc after it, unfortunately. I have added my device key to my keydb.cfg a while back in April, to clarify, that was for the disk drive I use to rip/read BDs, right?

Getting disc info...
----------
[(Disc Info)]
[DiscID]: 0xBEA866155DE5A6B6E61AE378EDE1CA96C8A7C840
[Volume]: BRMM_10925
[Date]: 2025-04-29
[VID]: 0x940716208FD8069613B2EB4A94A35634
[MKB]: 82
[EncKey]: 1-0xEB7375468FB6F253D6BE49150D21372F
[KEYDB_STATUS]:
[STATUS]: not found
[DiscType]: BD
[MakeMKV SUPPORTED]: FALSE
------------------------------------

[SamuriHL]

Something looks wrong with that. If the device key is in the keydb and the drive is capable of libredrive (this is important because there's no known valid host cert once a drive sees mkb v82) then it should calculate the keys for that title. I see in there it has the vid so that's suggesting that the drive is libredrive enabled. The only thing I can think of is that it's not picking up the device key from your keydb for some reason.

Sent from my SM-S938U1 using Tapatalk

[hinachan0604]

Something looks wrong with that. If the device key is in the keydb and the drive is capable of libredrive (this is important because there's no known valid host cert once a drive sees mkb v82) then it should calculate the keys for that title. I see in there it has the vid so that's suggesting that the drive is libredrive enabled. The only thing I can think of is that it's not picking up the device key from your keydb for some reason.

Sent from my SM-S938U1 using Tapatalk

Hello, I went back to the thread and realized that you had a new version of keydb helper, so I downloaded that and tried to run Disc Info again.

Getting disc info...
Validation Data: A4BE15253ABE1889D868553F1A79A6B7 [FOUND]
Media Key: [NOT FOUND]
Media Key not found!
[(Disc Info)]
[DiscID]: 0xBEA866155DE5A6B6E61AE378EDE1CA96C8A7C840
[Volume]: BRMM_10925
[Date]: 2025-04-29
[VID]: 0x940716208FD8069613B2EB4A94A35634
[MKB]: 82
[EncKey]: 1-0xEB7375468FB6F253D6BE49150D21372F
[KEYDB_STATUS]:
[STATUS]: not found
[DiscType]: BD
------------------------------------

After you mentioned that there is something wrong with it, I now checked if I did put the device key, which I was pretty sure I did, but when I tried to look for steps on how to do so, I couldn't find one. I'm sorry to ask would you be able to link me to steps on where I can find my device key?

[hinachan0604]

Hello,

Please ignore my last post/reply. It seems that I did copy a device key but it was for v72 and not v82. I had to read it over at least 10 times to notice. Self note: never try to rip new pesky v82 CDs without sleep.

My apologies for the trouble. This has been resolved. Thank you!