John doe

Enough to reward the boss who find how to get access back to my content. I might mess a step in the process. I don't ask for "hey could you break encrypton algorithms." I ask for common issues ideas. This shouldn't happen but technologies had updates like for windows and Intel usbs.. As exemple you needed in the past to turn off secure boot Intel hyperthreading and fast boot and turning on xhci for usbs sometimes USB legacy mode was better in bios. Same as disabling the turning off mode for inactivity...

Anyone might help? I need to know also if the masterkey is exactly 64 HEX which is the one that shows veracrypt when you create the volume? Because I've seen in veracrypt documentation there are 2 keys of 64 hex each. I don't know if these one are 64 hex both and then splitted in 32 hex for key 1 and key 2 or if each are 64 hex... The problem is that veracrypt only gives 64 hex for the masterkey when you create the volume. Also I don't know how to use these 64 hex. I heard using a .bin keyfile containing...

Anyone might help? I need to know also if the masterkey is exactly 64 HEX which is the one that shows veracrypt when you create the volume? Because I've seen in veracrypt documentation there are 2 keys of 64 hex each. I don't know if these one are 64 hex both and then splitted in 32 hex for key 1 and key 2 or if each are 64 hex... The problem is that veracrypt only gives 64 hex for the masterkey when you create the volume. Also I don't know how to use these 64 hex. I heard using a .bin keyfile containing...

Anyone might help? I need to know also if the masterkey is exactly 64 HEX which is the one that shows veracrypt when you create the volume? Because I've seen in veracrypt documentation there are 2 keys of 64 hex each. I don't know if these one are 64 hex both and then splitted in 32 hex for key 1 and key 2 or if each are 64 hex... The problem is that veracrypt only gives 64 hex for the masterkey when you create the volume. Also I don't know how to use these 64 hex. I heard using a .bin keyfile containing...

Hello, I would like to know how is it possible to mount a volume using masterkey (32 chars + 32 chars). As far as I've seen it's only possible to get them when you create the volume by waiting before they load before processing format. Once you have them, which process do you need to run to mount using the 64 char masterkey? I need all the exact steps. Also since using master keys doesn't refer on pim neither password or keyfile is it really the case? Because I've seen referring to veracrypt 1.19...

I put 5 btc bounty for any help that resolve my issue. It's external harddrive and other USB. Both have pdf and mp3 hidden volume. Entropy is 7,6 at 65543 offset (there is pdf signature at the beginning of pdf hidden volume on the first bytes on hxd and full of F from 0 to 65543 for mp3 hidden volume) which should show that it's really the good veracrypt volumes I had since I also remember 100% it was there and maybe that the hidden header are not corrupted which would let to another error than the...

After further investigating I found 7,6 enthropy on a pdf which still have pdf signature at the begening HxD but has the entropy of 7,6 begining at 00100000 offset(h) which could be the hidden volume I had. My mistake is that I never had a full encrypted partition on any device first I think and it was a security meassure to prevent unknown access to format partition if they ever use the disk and prevent . It's impossible that this pdf would be just an original pdf with such entropy and my mind remembering...

After further investigating I found 7,6 enthropy on a pdf which still have pdf signature at the begening HxD but has the entropy of 7,6 begining at 00100000 offset(h) which could be the hidden volume I had. My mistake is that I never had a full encrypted partition on any device first I think and it was a security meassure to prevent unknown access to format partition if they ever use the disk and prevent . It's impossible that this pdf would be just an original pdf with such entropy and my mind remembering...