Can't decrypt AACS from EU/DE Bluray

[kalli9920]

So, i started by straight up copying the complete Bluray Disc Folders, using a jailbreak PS3. Then i moved it to PC and had MakeMKV read it
Of course it's not possible because it's encrypted, so i used a mix of KeyDB_Helper and FindVUK, so the full encryption data is sent to the official KEYDB.cfg page.

Even with everything donw and multiple times updated, i get the same errors. I get as far as:

Processing BD+ Code with Java,

Failed to add angle #2 for title #32

Title #01123.m2ts has length of 1 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #01125.m2ts has length of 102 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #01126.m2ts has length of 102 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Failed to open disc

The funny thing is, that the biggest m2ts file (00066.m2ts) wasn't even added to MakeMKV at all... why?

I think this is the dump from my european/german Bluray of Prince of Persia: https://mega.nz/file/iUVGmCaC#6iZWOw1tI ... LBCUaeRh0g

(Btw. there will be MANY new posts like this, because apparently there are almost no german blurays active for MakeMKV. How odd)

I also heard i should send an e-mail to svq@makemkv.com? So the Subject name should be "MKB_v17_save" then?

[MrPenguin]

I also heard i should send an e-mail to svq@makemkv.com? So the Subject name should be "MKB_v17_save" then?

I don't think that's the TGZ dump file for your disk.

[kalli9920]

I don't think that's the TGZ dump file for your disk.

This is the actual save that MakeMKV game me. The real save is called "_private_data.tar" inside that are many .bin files and also "MKB_v17_save.tgz". Am i supposed to upload the complete thing?
And as i said, i managed to copy the complete bluray data paths to USB, then over to PC, then made it a .ISO then read it with several programs and MakeMKV (yes i know it's way too complicated. But i don't want to buy a PC bluray drive for 150 bucks)

[MrPenguin]

This is the actual save that MakeMKV game me. The real save is called "_private_data.tar" inside that are many .bin files and also "MKB_v17_save.tgz". Am i supposed to upload the complete thing?

The _private_data.tar file contains the "hashed keys" database and the LibreDrive microcode, whereas MKB_v17_save.tgz is an instance of MKB_RO.inf for MKBv17. Neither of these is a dump file for your disk, and so there is no point uploading either of them. It would be more useful for you to post what MakeMKV's log output is.

[kalli9920]

The _private_data.tar file contains the "hashed keys" database and the LibreDrive microcode, whereas MKB_v17_save.tgz is an instance of MKB_RO.inf for MKBv17. Neither of these is a dump file for your disk, and so there is no point uploading either of them. It would be more useful for you to post what MakeMKV's log output is.

Okay, here is the Log as txt file: https://mega.nz/file/fJsiyJCD#LtvyyKx-E ... rhlSoPjQg4

[MrPenguin]

Okay, here is the Log as txt file: https://mega.nz/file/fJsiyJCD#LtvyyKx-E ... rhlSoPjQg4

At a guess...

Code: Select all

Debug log started at Thu Jan 29 15:47:56 2026 , written by MakeMKV v1.18.3 win(x64-release)
001005:0000 MakeMKV v1.18.3 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file://C:\Users\larsk/MakeMKV_log.txt
Using 262272KB for read cache.
Network access is ENABLED, CURL version 7.72.0/Schannel/1.41.0 (x86_64-pc-win32) , proxy server not set.
WinCdArb=v1.2.0_tiny win(x64-release)
No  SDF v0a5: HL-DT-ST_DVDRAM_GH24NSD1_LG00_201512111522_K42HANF5057
DEBUG: Code 3 at tNjYHe^Zv]scO1k:ka77Z}$W:29395310
SDF id v0a5: HL-DT-ST_DVDRAM_GH24NSD1_LG00_201512111522_K42HANF5057
003006:0000 Opening files on harddrive at file://D:/Spiele download/Prince_of_Persia
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
...
003025:0000 Title #01126.m2ts has length of 102 seconds which is less than minimum title length of 120 seconds and was therefore skipped
005010:0000 Failed to open disc
Application exited at Thu Jan 29 15:50:12 2026

... I would say that the files you have copied to your harddrive are invalid. Try putting your BD into your BluRay drive directly, and asking MakeMKV to rip that instead.

[kalli9920]

... I would say that the files you have copied to your harddrive are invalid. Try putting your BD into your BluRay drive directly, and asking MakeMKV to rip that instead.

Well... that's not possible, because the only BD-Drive i have are inside PS3 and PS4. So the copied data from PS3 is incomplete or invalid? Interesting... but also kinda unfortunate that it's not THAT easy :/
Oh well, in that case i probably should buy a BD-drive for PC then. Gimme like... 6 months xD

[MrPenguin]

Well... that's not possible, because the only BD-Drive i have are inside PS3 and PS4. So the copied data from PS3 is incomplete or invalid?

And that's the problem: A BD contains important metadata in its "lead-in" section which can only be read by an actual BluRay drive, and which is not copied when you copy all its files to your harddrive.

Try downloading the latest KEYDB.cfg file, and copying it into MakeMKV's data directory (i.e. the same directory as your _private_data.datr file. If you're lucky then the KEYDB.cfg file will already contain your disk's metadata, and MakeMKV will then be able to decrypt your disk. Failing that, "yes" you are going to need to put your disk into a different BluRay drive.

[kalli9920]

Hey short update. It somehow worked with a different Bluray, this time Pirates of the Caribbean. I mean... i got plenty of "synch errors" or something like that, but it worked - same method as before, straught up copying the path using PS3 and USB.
As for the keybd.cfg, i tried it many times, but even KeyDB_Helper said something is incomplete. Maybe there was just an error during the copying between PS3, USB and PC.
I'm just happy right now that it somehow worked with a different movie

[MrPenguin]

I'm just happy right now that it somehow worked with a different movie

If either MakeMKV's "hashed keys" database or the public KEYDB.cfg file already contains keys for a disk then you don't need the missing metadata from its "lead-in" section. The problem happens when neither database has seen your particular disk before.