Author Topic: Help - Hack on new DMS for Audi Cradle on Kenwood HU  (Read 11802 times)

0 Members and 2 Guests are viewing this topic.

Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Help - Hack on new DMS for Audi Cradle on Kenwood HU
« on: June 24, 2007, 02:35:31 am »
Ok here goes:  I have a Audi/VW crade I bought on eBay hacked to run a Kenwood HU.  System works great....and then I tried to swap drives. 

I backed up the original DMS using the most recent backupdms script - No Issue.  I applied the DMShack script to the DMS but did not get completed message.:
Quote
****************************************************
 Press Enter to continue, Press CTRL-C to abort...
****************************************************

***************************************************************
Please ensure DMS is NOT connected and press enter to continue
***************************************************************

***Scanning Currently Connected Disks***

***************************************************************
Please insert stock (original) DMS And make sure that the
DMS drive letters are seen for PHTSYS and PHTDTA in explorer
***************************************************************

Press Enter to Continue when ready


***Rescanning Connected Disks***

***Rescan Complete***

***Determining if new DMS drive is seen***


***WARNING***

Microsoft DiskPart version 5.1.3565

Copyright (C) 1999-2003 Microsoft Corporation.
On computer: ASHLEIGH

Disk 2 is now the selected disk.

USB-FS PhatNoise DMS 20 USB Device
Disk ID: 3D71AD8C
Type   : USB
Bus    : 0
Target : 0
LUN ID : 0

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 4     G   PHTSYS       FAT32  Partition    260 MB  Healthy
  Volume 5     H   PHTDTA       FAT32  Partition     18 GB  Healthy


This drive will be used as the destination for the HACK process..
***WARNING***
Files will be copied into the backup folder (on phtsys) for safe keeping.

Press ENTER to continue or CTRL-C to abort

After I pressed enter the window closed on it's own after a few seconds.  I loaded the DMS into the cradle, turned on the power and watched it load for a few minutes.  I after a little popping and hissing from the speakers, I got a "disk empty" voice command.  I figured this wasn't right, so I check ed the bootload log.  I got the
Quote
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*-X: Failed
I checked the patchverify log and it said it was unverified from the 4th script on.  I renamed the ramdisk file ramdisk1, the phatd file ramdisk and made a copy of phatd.  Reran the hack to the DMS and had the same reaction - whereas the window closed on it's own without stating the hack had completed.  So I figured WTF, I'll try it anyway.......now the keg boots (or sounds like a boot) then prompts "empty" and cycles on and off repeatedly. 

Not sure where I read it, but saw someone say to format phatsys and reapply firmware.  Did that.  Loaded the DMS into the keg and got "welcome" audio.  Seemed like a good idea to try and reapply the hack.  But what seemed like a good idea at the time, got me back to square one.  Unfortunately now, I cannot retreive any sort of patch log - it just doesn't exist.  I continue to get the "empty" prompt (no audio) and the keg powers on and off repeatedly. 

I think I need to restore the phatsys from my backup, but not sure how best to do that.  Also really not sure how to get the hack to work once I've gotten that far.  Anybody run into a similair situation?  Is this because I'm using an Audi box with kenwood headunit? 


Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #1 on: June 24, 2007, 02:47:34 am »
This is all I could copy after the DMShack script before the window closes
Quote
mkdir.EXE: cannot make directory `:/music': Invalid argument
cp.EXE: :/Profiles/Profiles.ini: No such file or directory


Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #2 on: June 24, 2007, 06:05:42 pm »
we don't recommend that you run the bat files via explorer and double clicking them.  you should run them from the cmd prompt command line so you can see all the output.

From the looks of the log you need to corrupt the ramdisk.sig on the dms.

Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #3 on: June 24, 2007, 07:23:08 pm »
Ok, ran from cmd prompt.  Got ok to remove DMS message.  Loaded DMS and just waiting for the hack complete message.  The green light is now off, and the red is on steady, but the HU stills says "reading".  Gonna give it a few more minutes and then power down and reinsert DMS. 
« Last Edit: June 24, 2007, 08:05:31 pm by c0ckac0la »

Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #4 on: June 24, 2007, 08:25:36 pm »
I powered down, reinserted DMS and got "Welcome" audio followed by "empty disc" audio.  Here is my bootload.log:
Quote
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful
Here is my patchlog:
Quote
: No such file or directory
PhatPatch v0.8 - original code by bushing, additional patches by sbingner
Finding patch offsets:
Verified standard patch offsets
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!
Patch 8 @ 0330: don't try to read ramdisk.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 0000 eb00    Actual: 02db eb00
Unverified!
Patch 9 @ 02c0: don't try to read linux.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 0000 eb00    Actual: 02f7 eb00
Unverified!
Segmentation fault
So back to the corrupt ramdisk.sig file.  I did open ramdisk.sig with a text editor and typed in "aaaa" at the beginning of the script.  I saved that file as is and closed it.  However I still get the "unverified" in the last 3 patches...where do I stand so far?


Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #5 on: June 24, 2007, 08:46:30 pm »
I removed the "aaaa" from the beginning of the ramdisk.sig script and reinserted DMS into cradle.  Once again got "welcome" audio followed by "empty disc" audio.  The bootload.log remains unchanged, (success).  Here is my patchlog:
Quote
: No such file or directory
PhatPatch v0.8 - original code by bushing, additional patches by sbingner
Finding patch offsets:
Verified standard patch offsets
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!
Patch 8 @ 0330: don't try to read ramdisk.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 0000 eb00    Actual: 02db eb00
Unverified!
Patch 9 @ 02c0: don't try to read linux.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 0000 eb00    Actual: 02f7 eb00
Unverified!
Segmentation fault

: No such file or directory
PhatPatch v0.8 - original code by bushing, additional patches by sbingner
Finding patch offsets:
Verified standard patch offsets
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 8 @ 0330: don't try to read ramdisk.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 0000 eb00    Actual: 0000 eb00
Verified!
Patch 9 @ 02c0: don't try to read linux.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 0000 eb00    Actual: 0000 eb00
Verified!
PhatPatch v0.8 - original code by bushing, additional patches by sbingner
Finding patch offsets:
Verified standard patch offsets
first 2 words of flash=c102 0025
testing offsets 0x555 and 0x2aa
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0004, 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
Detected patch 1 already applied
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0026 1a00    Actual: 0000 1a00
Detected patch 2 already applied
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0019 1a00    Actual: 0000 1a00
Detected patch 3 already applied
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 000c 1a00    Actual: 0000 1a00
Detected patch 4 already applied
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13e0    Actual: 0000 13a0
Detected patch 5 already applied
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0001 e350    Actual: 0000 e350
Detected patch 6 already applied
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0001 03a0    Actual: 0000 03a0
Detected patch 7 already applied
Patch 8 @ 0330: don't try to read ramdisk.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 02db eb00    Actual: 0000 eb00
Detected patch 8 already applied
Patch 9 @ 02c0: don't try to read linux.sig (boot without any .sig files): [bl sector_read_suzy -> bl PC+1]
Expected: 02f7 eb00    Actual: 0000 eb00
Detected patch 9 already applied

Is my box hacked?
« Last Edit: June 24, 2007, 08:50:00 pm by c0ckac0la »

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #6 on: June 24, 2007, 09:46:51 pm »
yes it is.

Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #7 on: June 24, 2007, 09:55:38 pm »
Thanks!  I'm having trouble with my PC recognizing the new DMS run the newdms script.  I have shutdown several times, turned off antivirus, still not recognizing.  What do you think?

Quote
***Rescanning Connected Disks***

***Rescan Complete***

***Determining if new DMS drive is seen***

Error: multiple or no new drives detected. Starting over.
--------------------------------------------------------------------------
| Please temporarily disable any virus protection at this time, This is
| required to obtain exclusive access to the PHTSYS and PHTDTA partitions
--------------------------------------------------------------------------

Please press enter to continue after virus protection has been disabled.


No other mass storage connected.  No hardware connected except cable modem.  Tried changed usb port a few times too.
« Last Edit: June 24, 2007, 09:58:49 pm by c0ckac0la »

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #8 on: June 24, 2007, 11:35:10 pm »
are you running a non English version of windows?

Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #9 on: June 24, 2007, 11:50:36 pm »
No to Non-english.  I disassembled the DMS cartridge and reassembled and tried a few things in device manager.  Some combination of these things worked.  FYI I was getting an error "code 10"  for the mass storage device.  This apparently means that the device could not start, I think maybe I had the screws on the cartridge too tight?  Maybe the case was constricting the drive????  I don't know, but it seems to work now.  I'm loading the firmware on the new DMS now, so here goes!!

Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #10 on: June 24, 2007, 11:54:39 pm »
After the newdms.bat :
Quote
***WARNING***

Microsoft DiskPart version 5.1.3565

Copyright (C) 1999-2003 Microsoft Corporation.
On computer: ASHLEIGH

Disk 2 is now the selected disk.

USB-FS TOSHIBA MK1234GA USB Device
Disk ID: 00000000
Type   : USB
Bus    : 0
Target : 0
LUN ID : 0

There are no volumes.
Drive identified will be completely wiped by this process
***WARNING***

Press ENTER to continue or CTRL-C to abort

Backing up first 1MB in case you ignored the warning about OEM DMS drives
1024+0 records in
1024+0 records out
***Wiping drive and setting up partitions, please wait***
1+0 records in
1+0 records out
Fixing partiton type of Partition 1
Formatting PHTSYS Partition, please wait
:: Unknown error
mkdosfs.EXE 2.8 (28 Feb 2001)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>
Formatting PHTDTA Partition, please wait
mkdosfs.EXE 2.8 (28 Feb 2001)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>
\\.\H: has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 234227637 sectors;
file system has 2 32-bit FATs and 8 sectors per cluster.
FAT size is 228293 sectors, and provides 29221377 clusters.
Volume ID is 467ef5e3, volume label PHTDTA     .
Extracting backup of PHTSYS to PHTSYS partition
newdms.sh: pushd: invalid argument: : [122]
newdms.sh: popd: directory stack empty [124]
All done. Please save DMS-1MB-USB-FS TOSHIBA MK1234GA USB Device.bin
If this was your original DMS or you want to keep your keys.

When I go to load the firmware, the phatsys drive is not named, and it says it is not formatted.  I did not read anywhere about this happening---is this normal?

Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #11 on: June 25, 2007, 12:16:05 am »
I formatted the PHTSYS, renamed it PHTSYS, extracted the firmware to it, loaded it and got loading.....eject.  No bootload.log file to check as suggested by wiki windows hack procedure.  Any thoughts?

Should I run newdms.bat again?


Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #12 on: June 25, 2007, 04:16:58 am »
being that newdms.bat is generating errors I don't know what to tell you. the error listed Unknown Error is not very helpful in locating the problem.

Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #13 on: June 25, 2007, 06:23:55 am »
No idea where to go from here...After the unknown error message, I ran newdms.bat again.  This was the output:
Quote
Disk 2 is now the selected disk.

USB-FS TOSHIBA MK1234GA USB Device
Disk ID: 62421A13
Type   : USB
Bus    : 0
Target : 0
LUN ID : 0

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  -------
  Volume 4     G   PHTSYS       NTFS   Partition    102 MB  Healthy
  Volume 5     H   PHTDTA       FAT32  Partition    112 GB  Healthy
Drive identified will be completely wiped by this process
***WARNING***

Press ENTER to continue or CTRL-C to abort

***Wiping drive and setting up partitions, please wait***
1+0 records in
1+0 records out
Fixing partiton type of Partition 1
Formatting PHTSYS Partition, please wait
mkdosfs.EXE 2.8 (28 Feb 2001)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>
\\.\G: has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 208782 sectors;
file system has 2 32-bit FATs and 1 sector per cluster.
FAT size is 1606 sectors, and provides 205538 clusters.
Volume ID is 467f4c8b, volume label PHTSYS     .
Formatting PHTDTA Partition, please wait
mkdosfs.EXE 2.8 (28 Feb 2001)
Win32 port by Jens-Uwe Mager <jum@anubis.han.de>
\\.\H: has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 234227637 sectors;
file system has 2 32-bit FATs and 8 sectors per cluster.
FAT size is 228293 sectors, and provides 29221377 clusters.
Volume ID is 467f4c97, volume label PHTDTA     .
Extracting backup of PHTSYS to PHTSYS partition
All done. Please save DMS-1MB-USB-FS TOSHIBA MK1234GA USB Device.bin
If this was your original DMS or you want to keep your keys.

Extracted all firmware to drive again, overwriting previous versions.  Got a "Load" response followed by "eject".  Came back to view bootload.log and saw it to be the exact same log as my hacked original DMS, and all hacked files were also on new drive (interesting)  At any rate, bootload.log gave no further assistance as it was not new, so I corrupted the ramdisk.sig file via text of "aaaa" at the front of the script. 

Inserted the DMS into the PB to get immediate "No CD" message.  WTF?

Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #14 on: June 25, 2007, 06:36:38 am »
Vortech any ideas?

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #15 on: June 25, 2007, 07:33:47 am »
Since the windows stuff seems to be having issues, you could try that phatnoise repair ISO

Offline VorTechS

  • Administrator
  • Veteran.
  • *****
  • Posts: 1678
  • PhatHack Media Manager & DMS Tools Wizard Author
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #16 on: June 25, 2007, 07:40:06 am »
Firstly, you mention you 'extracted the firmware'... but you might need to re-do this in a specific order.

Delete the contents of the PHTSYS directory, but leave the partition intact.
I'll assume that you have downloaded the firmware from the relevant PhatHack download links, and that you have chosen the Kenwood one v13.01.

If you haven't, please do that first.

Then:

1) Open up 'system_0x02ff_13_01_RC.zip'
2) Extract the files:

'linux'
'ramdisk'
'linux.sig'
'ramdisk.sig'

onto the PHTSYS partition, in the order listed!

3) Extract the remaining files onto the partition.  DO NOT re-extract the files listed above [in case windows changes where they sit on the disk]

4) Extract the contents of 'daemon_0x02ff_13_01_RC.zip' onto the PHTSYS partition
5) Extract the contents of 'headunit_0x02ff_13_01_RC.zip' onto the PHTSYS partition
6) Extract the contents of 'player_0x02ff_13_01_RC.zip' onto the PHTSYS partition

I'll assume that the PhatBox already has the correct firmware loaded onto it.
So:

7) Delete the file 'forceupdate' and 'forcesettings' from the PHTSYS partition

Now, at this point you might want to fire up PMM and just check that it sees the DMS without any issues.  Don't create a playlist - PMM will create a default one with the PhatNoise startup sound.  Save and Eject to make sure the 'new' playlist is saved on the DMS correctly.

Assuming everything goes smooth up to this point, let's turn our attention to the PhatBox.

1) With your engine off, make sure there is no DMS in the PhatBox and then disconnect the cable from the back of the PhatBox and wait a couple of minutes.
2) Re-connect the cable
3) Insert the DMS into the PhatBox
4) Turn your ignition to power up the Head Unit
5) Use the Head Unit to select the PhatBox

If this hasn't kicked it into gear, just take a look at the lights on the PhatBox - make sure we don't have solid green, and at there is at least some activity.

If necessary repeat the above, waiting at least 30 seconds before removing the DMS from the Phatbox when you do.

If the repeat fails, then stick the DMS back into the Cradle and re-copy the 'forceupdate' and 'forcesettings' files from 'system_0x02ff_13_01_RC.zip' onto the PHTSYS partition and repeat the instructions above, twice if necessary.

If after all this we've gotten no-where, we can still try something else - so don't panic!
Kenwood KDC-W7031 | Kenwood KHD-CX910 | 250GB DMS | PhatHack Media Manager v1.1.4 (Alpha) | VIOT

Catch me weekdays 8am-4pm GMT on IRC @ irc.freenode.net on channel #phathack (aka the chat link!!)

Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #17 on: June 29, 2007, 05:39:31 pm »
Format or delete PHTSYS?  When I try to delete, the "recycled" folder cannot be deleted.  I go in a delete every file one by one, but when I get to the last one....it rewrites all the files back into the "recycled" folder....

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #18 on: June 29, 2007, 06:06:33 pm »
Deleting everything doesn't do you much good... you need to format PHTSYS to load new software on it

Offline c0ckac0la

  • A few posts under my belt.
  • *
  • Posts: 18
  • I didn't sign up for this...
Re: Help - Hack on new DMS for Audi Cradle on Kenwood HU
« Reply #19 on: June 29, 2007, 06:16:35 pm »
Thanks Vortech and Sbinger! 
I formatted the drive (again) and loaded the firmware in the exact manner Vortech described.  I put the DMS in my HU said Disc Changer, then switched to Aux Ext.  After a few minutes all lights went out on the Phatbox.  I removed the DMS, unplugged the cable from the phatbox, reseated the cable, placed the DMS back in the cradle turned the key and got welcome message!!!!  I'm stoked!  Thanks again!!