Skip to content

Releases: hiddenpalaceorg/DVDRawBruteforce

2023-12-12a

13 Dec 03:18
@ehw ehw
cc64283
Compare
Choose a tag to compare
  • Reread LBA 0 because apparently there are values of 'read' buff that can actually alter the cache too! Yay!

2023-12-12

12 Dec 05:18
@ehw ehw
f899e3b
Compare
Choose a tag to compare
  • Fix bug when no 3C values were found before using the 3C memory dumper.

2023-12-11a

11 Dec 23:24
@ehw ehw
f1ae016
Compare
Choose a tag to compare
  • Have the drive reread LBA 0 each iteration of F1 bruteforcing to see if I can prevent F1 from modifying data already on the cache.
  • Change compression from .zip to .7z for better compression ratios.
  • Add cleanup function to clear duplicate files.
  • Print file hash (SHA256) for every file in the log.

2023-12-11

11 Dec 06:52
@ehw ehw
f8b2126
Compare
Choose a tag to compare
  • Fix bug with interrupt handlers so that contents of the discovered values array are retained after getting out of the function.
  • Potentially fixed a bug where drives that don't rotate back to the beginning of memory when the offset is set too high and thus don't create the files for the memory dump occurs. I couldn't test this personally but I know someone tested a drive that this occurred.
  • Moved mem_dump_3c to before bruteforcing f1 just in case bruteforcing f1 writes to cache.
  • Reread lba 0 after f1 bruteforcing but before testing other commands just in case bruteforcing f1 wrote to the cache.

(TODO: Finish testing 7z support, look into adding a general cleanup function to clear duplicate files.)

2023-12-10

10 Dec 21:12
@ehw ehw
d2274cb
Compare
Choose a tag to compare
  • Add interrupt handlers (CTRL+C) for scanning 3c/f1 values just in case drives hang or take too long.
  • Added an experimental RAM dumper. This will take the first 3C opcode discovered that returned valid sector data with a valid PSN. This will try to dump 16MB with the command, which should be close to the start of DRAM. This process can also be interrupted with Ctrl+C. Note, how drives handle CDBs with invalid offsets is up to the drives I think. For my PX-716A, it didn't complain when I used a high offset value. Commonly, it should 'loop around' to the start of DRAM if the offset is beyond the size of available RAM but it might be up to the firmware so expect something to happen if they dont.
  • Small spelling mistake changes.
  • 3C bruteforce values are now stored in an array so that they can have some applicable use.

2023-11-26

26 Nov 23:18
@ehw ehw
0c72b58
Compare
Choose a tag to compare
  • Fix typo for READ LONG
  • Fixed assumption that the PSN was 4 bytes long rather than 3. Adjusted the script so that it treats the PSN as 3 bytes.
  • Add sector id description (which is the first byte in the sector)
  • Pretty up the log a little.
  • Update sg_raw to the latest version.
  • Dump PFI/DMI/BCI/etc from the disc (todo, decode the information and dump it raw using the found commands).

2023-10-01a

01 Oct 21:38
@ehw ehw
fbccedc
Compare
Choose a tag to compare
  • Add a condition for when timeouts occur by using a temp file. To prevent the drive from resetting, potentially causing cache to be cleared, reread LBA 0 if the drive was suspected to have been restarted from a time out.
  • Save LBA 0's 2048 byte user data into a binary file for analysis.

2023-10-01

01 Oct 16:04
@ehw ehw
1d385a5
Compare
Choose a tag to compare
  • Add a timeout of 20 seconds for sg_raw.exe calls in case they take too long to return data for that value.
  • Fix a copy pasta error for the progress bar for F1 bruteforcing (was meant to cover 256 possible values, was showing a bar for 256 * 256 possible values)

2023-09-30

01 Oct 02:29
@ehw ehw
6136513
Compare
Choose a tag to compare

Adds progress bars for 3c and f1 bruteforcing.

2023-07-09

01 Oct 01:55
@ehw ehw
bd8396b
Compare
Choose a tag to compare

Initial public release.