Kenwood Music Keg problems

[J^2]

Just got a new DMS from Phatnoise (as the disc on my original one failed before I discovered that it's impossible to create a new one - locking the stable door after the horse has bolted, I know!), planning to use that as the basis for running the hack.

Checked that the new DMS worked in the keg - all ok.

Manually backed up all the files from PHTSYS and PHTDTA (because I'm paranoid!).

Ran backupdms (because I'm paranoid!).

Ran DMShack and put the DMS back in the keg to run the patch.

On checking patch.log, all the patches were showing as unverified.

Tried running the patch again several more times with no difference in the result.

Ran patchclean to restore the DMS back to its original state.

Checked that the DMS worked in the keg - all ok.

Re-ran DMShack and put the DMS back in the keg to run the patch. Head unit displayed "T01 - LOAD" for several seconds before displaying "EJECT". Tried this a couple of times with no change in the result.

On checking patch.log, it hadn't been created - the log was empty.

Ran patchclean to restore the DMS back to its original state.

Checked that the DMS worked in the keg - not ok - head unit still displaying "01 - LOAD" for several seconds before displaying "EJECT".

Restored the back up files I took before making any changes.

Tried the DMS in the keg - not good - the head unit is not displaying "NO CHANGER".

Help!?

[judb]

run a chkdsk on it, then delete all the files in phtsys and reextract the firmware to it, remove the forceupdate and forcesettings files and see if that works.

there should have been a patchverify.log and that is what we are interested in mainly.

Before you nuke everything though, post the bootload.log if you have one..

[J^2]

I'll give this a go when I get back from work tomorrow (it's getting late here on the right-hand side of the pond!).

When you say to delete all files in PHTSYS, does that include the folders (Data, images, system_sounds and tts)?

Does http://downloads.phathack.com/firmware/system_0x02ff_13_01_RC.zip contain the firmware you want me to extract to PHTSYS?

Definitely no patch.log on PHTSYS at the moment.

There is no bootload.log on PHTSYS at the moment.

The bootload.log that was present when I backed up the files after applying the hack was:
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*-X: Failed

chkdsk doesn't report any problems - output is:

PHTSYS:
The type of the file system is FAT32.
Volume PHTSYS created 28/02/2007 15:36
Volume Serial Number is 45E6-121B
Windows is verifying files and folders...
File and folder verification is complete.

  272,080,896 bytes total disk space.
       73,728 bytes in 4 hidden files.
       77,824 bytes in 17 folders.
   20,021,248 bytes in 329 files.
  251,899,904 bytes available on disk.

        4,096 bytes in each allocation unit.
       66,426 total allocation units on disk.
       61,499 allocation units available on disk.

PHTDTA:
The type of the file system is FAT32.
Volume PHTDTA created 28/02/2007 15:36
Volume Serial Number is 45E6-121B
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no problems.
   38,792,928 KB total disk space.
          128 KB in 4 hidden files.
        2,208 KB in 69 folders.
      213,600 KB in 244 files.
   38,576,960 KB are available.

       32,768 bytes in each allocation unit.
    1,212,279 total allocation units on disk.
    1,205,530 allocation units available on disk.

[judb]

based off the error in the bootload.log its likely you need to do the corrupting the ramdisk.sig and try finishing the patch that way..

[J^2]

Ok - disconnecting and reconnecting the keg plus corrupting ramdisk.sig has allowed me to get the unit working again. 

Backed up the files from PHTSYS again! /paranoid

Tried running the hack again and seem to have a nearly successful patch.log this time:

: No such file or directory
PhatPatch v0.5 - original code by bushing, additional patches by sbingner
Verifying:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13a0    Actual: 0000 13a0
Verified!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0000 e350    Actual: 0000 e350
Verified!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0000 03a0    Actual: 0001 03a0
Unverified!
PhatPatch v0.5 - original code by bushing, additional patches by sbingner
first 2 words of flash=c102 0025
testing offsets 0x555 and 0x2aa
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0001, device id=22bf
offsets 0x555 and 0x2aa verified
Resetting flash.
Testing patch locations:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0033 1a00    Actual: 0000 1a00
Mismatch!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0026 1a00    Actual: 0000 1a00
Mismatch!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0019 1a00    Actual: 0000 1a00
Mismatch!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 000c 1a00    Actual: 0000 1a00
Mismatch!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13e0    Actual: 0000 13a0
Mismatch!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0001 e350    Actual: 0000 e350
Mismatch!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0001 03a0    Actual: 0001 03a0
Match! Programming...
Wrote 0000

Presumed the "Unverified" for patch 7 meant that I needed to run the hack again so tried that and I was back to "NO CHANGER" message on the head unit.

Restored back to the previously backed up files and still getting the *NO CHANGER* message on the head unit.

Disconnected and reconnected the keg and it seems to be working again!

I presume I need to keep going through this until I've got a patch.log showing all the patches as being successful so I'll try that later in the week when I've got some more time on my hands.

Ta for the help BTW! 

[judb]

the patchverify.log should be easier to read.. it looks like it patched the last location in that log but you will need to check the patchverify.log to be sure.

[J^2]

I haven't seen a patchverify.log anywhere. Should it be in PHTSYS/log or somewhere else?

I'll stick an empty notebook HDD in my original DMS case, run the newdms script against it and see whether it works...