Author Topic: Kenwood Keg hack issues.  (Read 9456 times)

0 Members and 2 Guests are viewing this topic.

Offline scooter1425

  • Newbie
  • Posts: 3
Kenwood Keg hack issues.
« on: March 02, 2007, 03:55:37 pm »
New to the board......

Ran all the scripts against an OEM DMS....but not the newdms.bat  ;)
the only log that shows up is the patch.log and not a patchverify.log.
The output from the patch.log is below.
I put the hacked DMS back into the unit, let it sit there for 15-20 minutes and nothing changes.
Any thoughts on what to try next?
Thanks!

: 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: 0000 03a0
Verified!
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=0020, device id=0057
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: 0000 03a0
Mismatch!



Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Kenwood Keg hack issues.
« Reply #1 on: March 02, 2007, 08:42:55 pm »
You may note it pased all of the verification -- that means your box is patched

Offline scooter1425

  • Newbie
  • Posts: 3
Re: Kenwood Keg hack issues.
« Reply #2 on: March 03, 2007, 02:42:31 pm »
Even though this is the patch.log, and not the patchverify.log?


You may note it pased all of the verification -- that means your box is patched

Offline scooter1425

  • Newbie
  • Posts: 3
Re: Kenwood Keg hack issues.
« Reply #3 on: March 03, 2007, 03:28:39 pm »
Not sure why.......but I got it.  ;D
I went back and started from scratch again on the OEM DMS.
I think there was an issue of getting the Kenwood firmware back onto the new DMS originally.

Time to get the music reloaded......

Thanks Guys!