Author Topic: Ford CDDJ New DMS not working after hack  (Read 10581 times)

0 Members and 1 Guest are viewing this topic.

Offline djc122

  • Newbie
  • Posts: 2
  • PhatHacker
Ford CDDJ New DMS not working after hack
« on: June 03, 2006, 01:27:06 am »
Hi, i have run out of things to try so have to ask for help. I have a Phatbox for a Ford woth a 20 gig original DMS. When I originally installed the phatbox none of the buttons worked that controlled playing functions (I have a navigational head unit) so I wrote Phatnoise and then sent me what they called "beta" firmware (Although the date stamp on the files were from 2003) and instructions. I followed the instructions and it did resolve my problem. Now I'm trying to get an 80 gig drive into the DMS. It's a toshiba MK8025GAS drive. I have used the boot cd and followed the process about 8 times and although the phatbox appears to be patched, I'm getting the Red solid light and green blinking light which reboots after about 20-30 seconds when I use the 80 gig drive.
Here are the logs from my original DMS that I have seen posted in other requests for help.

bootload.log
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful

patchverify.log
Starting Patch Process
PhatPatch v0.4 - 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.4 - 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!

patch.log
PhatPatch v0.4 - 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!
done

nothing is being written to the bootload.log on the new DMS.
I've check the file partitions, reformatted and ran out of ideas.
Are there any other ideas or more information I can provide?
thanks!

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Ford CDDJ New DMS not working after hack
« Reply #1 on: June 03, 2006, 03:13:06 am »
i suspect that there is something up with that drive.. like the jumper settings are wrong.

Offline djc122

  • Newbie
  • Posts: 2
  • PhatHacker
Re: Ford CDDJ New DMS not working after hack
« Reply #2 on: June 03, 2006, 05:42:18 pm »
the drive is fresh out of the static bag and has no jumpers installed on it which matches the original DMS 20 gig toshiba drive. do the newer drives require specific master drive jumpers?

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Ford CDDJ New DMS not working after hack
« Reply #3 on: June 03, 2006, 11:12:09 pm »
depends on your drive. but i dont think so.  if you get nothing in the bootload.log and the filesystem passes a chkdsk could be a connection issue.. not sure really.

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Ford CDDJ New DMS not working after hack
« Reply #4 on: June 04, 2006, 10:59:51 am »
try using just the PhatNoise DMS Repair CD on the new drive, then loading your firmware on it fresh