Poltergeist 4K Dump submitted

[javicozarcastillo]

Hello,
dump submitted on Poltergeist UHD Spanish Edition.

Thanks.

[MrPenguin]

dump submitted on Poltergeist UHD Spanish Edition.

Have you tried downloading the latest KEYDB.cfg file, copying it into MakeMKV's data directory (i.e. where MakeMKV also writes its TGZ dump files) and restarting MakeMKV?

If this doesn't work, could you upload your TGZ dump file into (say) OneDrive or Google Drive please, and then reply with a public download link? This would allow people to try adding your disk to the public KEYDB.cfg file.

[javicozarcastillo]

Yes, I've tried, and it's not working. This is the link to the TGZ dump file, as you request:

https://drive.google.com/file/d/1SfUar8 ... sp=sharing

Hope someone could help me.

Thanks in advance,

Javi

[javicozarcastillo]

I don't know if it helps, but inside latest KEYDB.cfg I found these:

0x5F42B478EEA764438B44702E0018D4FCC497998F = POLTERGEIST [Poltergeist (1982) - 4K Ultra HD] | D | 2022-07-29 | U | 1-0xF709D194A475FE6D2D970B178827022C ; MKBv76/BEE (UHD) (LEGACY) (NOTVALIDATED) (BD)
0x2B3A6AF6246224FACB414316722FA7D3E425A459 = POLTERGEIST [Poltergeist 4K Ultra HD] | D | 2022-07-29 | U | 1-0xF709D194A475FE6D2D970B178827022C ; BEE (UHD) (LEGACY) (NOTVALIDATED) (BD)
0x46FB504BF9473BE12164F7BFE3D355581D390B4E = POLTERGEIST [Poltergeist 4K Ultra HD] | D | 2022-07-29 | M | 0xA8E726C2955F431306309367F6AE00D8 | I | 0x9C5F3C7824FBDA6A2B9612B9A0981907 | V | 0xB8C28DC690FE0D6DD05213F23C1ABECA | U | 1-0xF709D194A475FE6D2D970B178827022C ; BEE (UHD) (LEGACY) (NOTVALIDATED) (BD)

2022-07-29 is exactly the timestamp of my UHD Blu-ray, so I understand that these refers to it. Not sure what it means "not validated", I guess maybe it has something to do with my problem, but again, I'm very lost in that garden. Any help will be appreciated....

[javicozarcastillo]

I would also add that this is the only issue I had in a very long time. Recently I made backup copies of a lot of UHD Blu-rays without any single problem, so I understand thet the Blu-ray reader (ASUS BW-16D 1HT) is not part of the problem...

[MrPenguin]

I don't know if it helps, but inside latest KEYDB.cfg I found these:
...
2022-07-29 is exactly the timestamp of my UHD Blu-ray, so I understand that these refers to it. Not sure what it means "not validated", I guess maybe it has something to do with my problem, but again, I'm very lost in that garden. Any help will be appreciated....

The format of these entries is

Code: Select all

<DISCID> = <VOLUME NAME> (<META TITLE>) | D | <date> | ... etc

where <DISCID> is the SHA1 hash of the disk's AACS/Unit_Key_RO.inf file. And MakeMKV can only use KEYDB entries which contain a "| V |" field anyway. So unless your own disk's ID matches 0x46FB504BF9473BE12164F7BFE3D355581D390B4E, I can understand why KEYDB isn't helping you atm. However, you have also provided your TGZ dump file and so there's a good chance that might now change.

I recommend using SamuriHL's Keydb Helper Tool (see link in my signature) to keep your local copy of KEYDB.cfg up-to-date, as this will save you from needing to re-download the entire ZIP file each time.

[MrPenguin]

I would also add that this is the only issue I had in a very long time. Recently I made backup copies of a lot of UHD Blu-rays without any single problem, so I understand thet the Blu-ray reader (ASUS BW-16D 1HT) is not part of the problem...

Yes, the problem is definitely that someone always needs to be the first to try decrypting a particular disk variant, and in this case that someone is you .