How to install a 160 GB HDD in the DMS?

[TheJohnny]

But i can't find a patch.log and a patchverify.log in x:\phtsys\log on the old DMS.
There are no existing files.

When there is no 'patch.log' or 'patchverify.log' then your phatbox is not hacked.
Is there a folder 'log' on the old DMS?

I used the DMSHACK and all was ok.
When i put the DMS in the phatbox i hear only my music.

Directly after putting the hacked DMS into the phatbox and starting your stereo, you should not hear any music as far as I am concerned.

Tell us all the steps you went through from the beginning.

Have a good night.

[Devil1978]

Ok here are my steps from the beginning:
On my old DMS are 19 albums of music.

At first i have loaded down the latest Windows PhatBox hack scripts Version 1.2.1

At the first step i run the BackupDMS.bat.
Because i have i german Windows XP Version i edited the files diskpart.dms and diskpart.nodms.
In the files i renamed it how in the exmaple:

  Disk ###  Status      Größe    Frei     Dyn  GPT
  --------  ----------  -------  -------  ---  ---
  Disk 0    Online        93 GB      0 B         
  Disk 1    Online         9 GB      0 B     


Then the backup began to run.

At the second step i ran the DMSHack.bat.
But when i put the old modifieded DMS in the phatbox an put on my radio i can hear the music which is on the DMS. But the phatbox do not find all of the 19 albums. He only find the first 2 albums ant not the other albums on the DMS. I can only choose the first 2 albums.

The result is: The phatbox is not hacked.
Thats my problem.
I tried it yesterday 4 times.
I don't know what i make wrong.

How i wrote yesterday i have the EU-Version of the phatbox.
And i have a VW-Phatbox for Golf IV.
I hope thats not the reason for my problem.

[VorTechS]

I can confirm that PatchWrite.log and PatchVerify.log appear NOT being written by the hack, although PatchVerify MIGHT be.

I say might be, because I'm sure my Wizard was wiping the log directory and I don't have PatchWrite.log.  I do have PatchVerify - although I think this may not have been deleted, nor the patch.log [which still contains references to Patch 0.4]

There appears to still be some issues with the patch, 'No such file or directory' warnings - not sure if this is something I am not copying over?

Code: [Select]

:
: No such file or directory
2048+0 records in
2048+0 records out

hdparm - get/set hard disk parameters - version v3.9

Usage:  hdparm  [options] [device] ..

Options:
 -a   get/set fs readahead
 -A   set drive read-lookahead flag (0/1)
 -c   get/set IDE 32-bit IO setting
 -C   check IDE power mode status
 -d   get/set using_dma flag
 -D   enable/disable drive defect-mgmt
 -E   set cd-rom drive speed
 -f   flush buffer cache for device on exit
 -g   display drive geometry
 -h   display terse usage information
 -i   display drive identification
 -I   read drive identification directly from drive
 -k   get/set keep_settings_over_reset flag (0/1)
 -K   set drive keep_features_over_reset flag (0/1)
 -L   set drive doorlock (0/1) (removable harddisks only)
 -m   get/set multiple sector count
 -n   get/set ignore-write-errors flag (0/1)
 -p   set PIO mode on IDE interface chipset (0,1,2,3,4,...)
 -P   set drive prefetch count
 -Q   print out the drive id only (60bytes\n)
 -q   change next setting quietly
 -r   get/set readonly flag (DANGEROUS to set)
 -R   register an IDE interface (DANGEROUS)
 -S   set standby (spindown) timeout
 -t   perform device read timings
 -T   perform cache read timings
 -u   get/set unmaskirq flag (0/1)
 -U   un-register an IDE interface (DANGEROUS)
 -v   default; same as -acdgkmnru (-gr for SCSI, -adgr for XT)
 -V   display program version and exit immediately
 -W   set drive write-caching flag (0/1) (DANGEROUS)
 -w   flush os cache and wakeup drive
 -X   set IDE xfer mode (DANGEROUS)
 -y   put IDE drive in standby mode
 -Y   put IDE drive to sleep
 -Z   disable Seagate auto-powersaving mode
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
: No such file or directory
: No such file or directory
/dos/backup/patch.sh: kup/p: No such file or directory
However, the hack itself appears to have worked.

[VorTechS]

On my old DMS are 19 albums of music.

<snip>

But when i put the old modifieded DMS in the phatbox an put on my radio i can hear the music which is on the DMS. But the phatbox do not find all of the 19 albums. He only find the first 2 albums ant not the other albums on the DMS. I can only choose the first 2 albums.

Part of the hack process, copies a new Profiles.INI file onto your DMS.  This INI file tells the phatbox that you only have 2 playlists configured.  This indicates that all the files you need to run the hack are on the DMS.

When I first ran the latest hack [slightly modified version of the current one], what I found was that on startup my Head Unit looked like it was playing 'silence' continually ... although showing the 'current track it was playing'.  After 20 minutes I turned off the Head Unit [NOT THE IGNITION] and turned it back on again to then find that I was given the 'hack complete' message.  Then my box allowed me to play from the first two available albums.

But i can't find a patch.log and a patchverify.log in x:\phtsys\log on the old DMS.

You appear to be quoting an incorrect directory name.
Assuming drive X: is your PHTSYS partition, then you should find the logs in:

x:\log

Does the directory x:\log exist on your old DMS?

If not, there might be a small flaw in the scripts, or the directory failed to be created at some point.  It's still possible the hack actually ran.

Try creating the directory if it doesn't exist, re-insert the old DMS into the box, wait the specified time [up to 20 minutes to be safe] and then check the DMS log directory afterwards.  Perhaps, things might look a little different!

[Devil1978]

When i come home i can post the logfiles from the old DMS if existing.

the directory x:\log on the old DMS is existing but the directory is empty.

Yesterday i ran the DSMHack at the old DMS again.

At the morning today when i drove to work (35 minutes from my home) the phatbox played immediately the music on the DMS when i turn on my radio. How i wrote there were only 2 albums available. In the 35 minutes i not heared the "hack complete" message.

When i'm at home i post the logs of the result.

[VorTechS]

On the way home, insert the DMS into the PhatBox turn on your engine and switch your stereo to the Phatbox.

Turn off the stereo [NOT the engine].

Turn the stereo back on and on startup before your music plays you may   hear the hack complete message.

However the fact that no logs exist is a little concerning - but it is still possible the hack worked [it could be the logging that's at fault].

If all things fail, and a second attempt at the hack fails, if you are prepared to try it out I can give you access to my new replacement for the scripts.

[TheJohnny]

You appear to be quoting an incorrect directory name.
Assuming drive X: is your PHTSYS partition, then you should find the logs in:

x:\log

You're absolutely right, my bad.

[Devil1978]

All right. I try it out.

Is that correct:
I have copied the files before the run of DMSHack from my old DMS 1:1 on my new DMS.
After run the NEWDMS programm on the new DMS. Phatbox Music Manager runs correctly with the new DMS.


@TheJohnny:
No problem. I know what you mean.

[TheJohnny]

I have copied the files before the run of DMSHack from my old DMS 1:1 on my new DMS.
After run the NEWDMS programm on the new DMS. Phatbox Music Manager runs correctly with the new DMS.

If you copy all the files from the old DMS to the new DMS and then run 'newdms.bat' on the new DMS, all the copied files will be lost because 'newdms.bat' partitions the new DMS. 'newdms.bat' then tries to unzip the files from 'phtsys.tar.gz' - or you can do that manually.

[Devil1978]

Sorry.
I mean that i used first the NEWDMS program and then i copied the files 1:1 from the old to the new DMS.

[TheJohnny]

I mean that i used first the NEWDMS program and then i copied the files 1:1 from the old to the new DMS.

That should work.

But the more important question for you is, did the hack (finish its) work?

Perhaps judb or sbingner can help here.

[TheJohnny]

What's your firmware version? Do you have the latest firmware on your box?

Did you run patchclean.bat on your old DMS before inserting it into your phatbox before your ride to work?

[Devil1978]

I have always the latest firmware on my box.

No i havent run the patchclean.bat on my old DMS.
Because i have no information about the patchclean.bat found in the Windows_Hack_Procedure-Solution.

My steps were these from the Windows_Hack_Procedure.

In 1 hour a ride at home then i will see if the HACK-Complete Message comes out of the speakers.

And in ca. 5 hours i can post the logfiles.

[sbingner]

If you have no logs, it is possible it didn't run... you should verify that PHTSYS:\flacplay is a TEXT file that calls patch.sh -- if not you need to reapply the hack to the dms so it cal run it.

The version of PhatNoise firmware on your PhatBox does not matter, unless some strange version ignores the startup sound

[Devil1978]

Now here is the result of my old DMS.

bootload:

BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*-X: Failed


x:\log\patch.txt:


: 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: 0033 1a00
Unverified!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0026 1a00
Unverified!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0019 1a00
Unverified!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 000c 1a00
Unverified!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13a0    Actual: 0000 13e0
Unverified!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0000 e350    Actual: 0001 e350
Unverified!
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!
Error MMAP /dev/mem: Invalid argument
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=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: 0033 1a00
Match! Programming...



Now my radio shows the message: NO MAGAZINE.

Whats now wrong?

[VorTechS]

The hack hasn't worked first time around.
Try again.

If it fails a second time, judb or sbingner should be able to sort you out.

[Devil1978]

Now the radio shows no cdchanger.
i don't know what to do next.

[sbingner]

as usual, corrupt ramdisk.sig

[Devil1978]

Yes i have corrupt the ramdisk.sig
But the radio shows: NO CHANGER again.

Now i have wiped the DMS with phatnoise music manager and downloaded the newest firmware for my phatbox.

When i install the DMS in the phatbox is no reaction.
The radio shows NO CHANGER again.
And the red LED on the phatbox is always on and the green LED is blinking.
This status was now for 45 minutes.

I think i have crashed the phatbox.

[TheJohnny]

No, you didn't crash your Phatbox.

Your problem

The radio shows NO CHANGER again.
And the red LED on the phatbox is always on and the green LED is blinking.

seems to be the same I had a few days before.

How did you corrupt your ramdisk.sig? That should help.

Yes i have corrupt the ramdisk.sig
But the radio shows: NO CHANGER again.

Now i have wiped the DMS with phatnoise music manager and downloaded the newest firmware for my phatbox.

Did you corrupt your ramdisk.sig and THEN wiped the DMS with PMM? Corrupt your ramdisk.sig again.

Read this thread and follow the advices I got. It worked for me - my Phatbox is hacked now.