Avatar Fire and Ash Dump Submitted

[Ralph P.]

Greetings,

MKB20_v82_Avatar-_Fire_and_Ash_7728

I have also loaded the file on to Google Drive for sharing to keydb.


Regards,

[Ralph P.]

Greetings,

This variant now rips using the latest keydb file.


Regards,

[jtscribe]

Interesting. Did you get the Steelbook? Mine is:

MKB20_v82_Avatar-_Fire_and_Ash_BB78

No joy with FindVUK, sent to svq.

[MrPenguin]

MKB20_v82_Avatar-_Fire_and_Ash_BB78

No joy with FindVUK, sent to svq.

Could you also upload this TGZ file into a file host such as Google Drive or OneDrive please, and then reply with a public download link? This would allow people to try adding your disk to the public KEYDB.cfg file.

[CMabrey]

I am still getting this message....The volume key is unknown for this disc - video can't be decrypted
Failed to open disc. I assume this is still not loaded into MakeMkV database yet? I usually haven't run into issues with new releases like this. I guess we just wait and continue to try to rip over the next few days? While I have only been ripping for a short time I have been lucky enough that I haven't run into many hiccups. When people start talking about volume keys I tend to get lost.

Thanks

[CMabrey]

Never mind. It works now.

Regards,

[goestoeleven]

UHD Steelbook didn't work for me on delivery day, but it does work now. This community rocks!

[cpitchford]

Amazon UK order arrived today; 4k + bluray:

TGZ from the UHD rip:
MKB20_v82_Avatar-_Fire_and_Ash_334A.tgz

sent to svq

Update: Resolved for me, now. Thank you

[scallaway]

Amazon UK order arrived today; 4k + bluray:

TGZ from the UHD rip:
MKB20_v82_Avatar-_Fire_and_Ash_334A.tgz

sent to svq

Update: Resolved for me, now. Thank you

I'm also struggling to get Fire and Ash to decrypt.

When it fails, MakeMKV outputs a .tgz that matches yours. How did you manage to get this resolved?

I've tried to install the latest keydb.cfg file but I can't tell whether MakeMKV is using it or not. I'm on Linux but if this feature isn't supported I can swap to Windows for this rip at a push.

[MrPenguin]

I've tried to install the latest keydb.cfg file but I can't tell whether MakeMKV is using it or not. I'm on Linux but if this feature isn't supported I can swap to Windows for this rip at a push.

The KEYDB.cfg file needs to be added to your $HOME/.MakeMKV/ directory, which is also where MakeMKV writes its .tgz files. Also, since Linux file systems are case-sensitive, you might also need to ensure the file is literally named "KEYDB.cfg" and not (say) "keydb.cfg". And then you need to restart MakeMKV.

[bigbwb]

I am also struggling to get this disc to decrypt. Can anyone point me in the right direction on how to make it work or what file to download etc? sorry, only know the basics of makemkv:) Windows user as an FYI.

Thanks so much,

[scallaway]

I've tried to install the latest keydb.cfg file but I can't tell whether MakeMKV is using it or not. I'm on Linux but if this feature isn't supported I can swap to Windows for this rip at a push.

The KEYDB.cfg file needs to be added to your $HOME/.MakeMKV/ directory, which is also where MakeMKV writes its .tgz files. Also, since Linux file systems are case-sensitive, you might also need to ensure the file is literally named "KEYDB.cfg" and not (say) "keydb.cfg". And then you need to restart MakeMKV.

Is MakeMKV meant to output anything in the log window about reading the KEYDB.cfg file? Neither "keydb.cfg" nor "KEYDB.cfg" cause any output to show.

[sergio31]

Key does not still work on MKB20_v82_Avatar-_Fire_and_Ash_DB6C.

[MrPenguin]

Is MakeMKV meant to output anything in the log window about reading the KEYDB.cfg file? Neither "keydb.cfg" nor "KEYDB.cfg" cause any output to show.

No, MakeMKV will just use the KEYDB.cfg file, should it happen to be available in the data directory.

Does MakeMKV's log contain any messages such as these?

Code: Select all

002004:0000 Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT PRESENT' occurred while issuing SCSI command A30..00200740100720..00F7CCDE86DB424533ACC584B19A4CD2F98 to device 'SPTI:\Device\CdRom0'

Because these would suggest that MakeMKV has not managed to enable LibreDrive, and so bus-encryption would still be active. The KEYDB.cfg file can only help you after you have disabled your drive's bus encryption.

[Scarbz]

I’m also having the same problem.
Failed to decrypt the disc, a file dump log was sent to the svg email. My question is, is there anything extra I can install because I have seen a few say theirs is now working. Sorry to be that guy normally I just send the file off to the email and 48hrs later it works so, so have never really needed to install a keyDB I don’t even know where to look for that.