PhatHack

Ok, so I have a nice spanking new 80gb disk, and the ISO.

Booted it, and it appeared to do its thing.

Stuck the (old, valid) DMS in the machine, and it started playing like nothing had been changed.

Went to playlists, albums, artists, genres - selected the first one of all, and nothing.

Tried with the new disk, and of course it didn't recognize it.

Looked at the stuff in the original thread; my PHTDATA\Profiles\Profiles contains:

[Default]
num_discs=15
startup_sound=
pattern=$Artist$ - $Title$

[profiles]
active_profile=Default
enable_special_discs=1
enable_voice_prompts=1
num_discs=15

[product]
product_name=PhatNoise Media Manager
product_version=3, 4, 2, 0


In that directory are several p0 files (p0, p0.pbx, p0.sig), all of which were modified/created when I ran the fix-disk.

Under Default, the p0.* files are all original - the mod times on those are NOT changed.

Looks like aadec and aadec.sig were also modified, along with flacplay and flacplay.sig on PHYSYS.  

However, the patch clearly didn't execute.....

Where do I go from here?

Trying to do this on a VW/Audi system....

For some reason your p0.* files didnt get replaced it seems.  in the phtsys\backup folder there should be 4 p0.* files .. copy those into the profiles\default folder and it should run.  Or your other option would be to change your ini file to have a startup sound of /dos/Data/Music/flash.flac (i think thats the file name.. look in the music folder on phtdta to be sure.

Did that and got the "your phatbox has been unlocked" message (figured that was what was going on.)  It did not go to the next playlist though - just stayed there repeating itself.

Powered down, waited for the light to go off, put in the new DMS (which I formatted with the tool) and it still refuses to recognize it - I get the flashing green for a few seconds, "No cartridge" eventually on the head unit, and it resets.

I'll look at the other option - for whatever reason its not flashing the box.

My disk structure doesn't look like that!

I don't have a /dos directory - anywhere - on either the PHTDATA or PHTSYS volumes.....

I think what I'm going to try is to reinit the DMS using the tool on the CD ISO; maybe the newer Phatnoise DMS management tools (Media Manager) is doing things differently on the DMS or something...

Did a "repair" with no difference in results - the system says it patched it, but it didn't....

I'll do a reload on it, and see what I can get to happen.... but as things stand right now it doesn't appear to be working on my box.

Once I have it back to "normal" with the original DMS I'll try the manual procedure.

the /dos directory is how the phatbox mounts the phtsys stuff.. and /dos/data is where the phtdta partition shows up when the phatbox is using it.

Post a copy of your logs from the logs directory on phtsys on the DMS you did the patch from please.

Ok, will retry it and do it again, then post the logs - I reformatted the disk (using the CD repair tool) so I'll have to go back into the media manager and re-init it.

I strongly suggest going to the phathack channel on IRC..  theres a page in the FAQ section about the IRC channel I think.

Oh, I think I understand what's going on.

My music manager has a base directory of "cd-jukebox", which is the pathname on my systme where the files are.

On the PHDATA partition, that's the directory name for the music files.

If you're dependant on files going in /music, it won't work - that directory does not exist on my DMS!

I think the DMS is rebuilt - I'm going to test the base load (with just one playlist on it), then re-run the patch CD and will then post the logs you're looking for.

I'll go grab MIRC while I'm at it, and be there in a few.  I can chat and work at the same time as I have a laptop and desktop machine, so I can be online while running the Linux kernel disk.

On Mirc.... original DMS is ok/repartitioned, has just one playlist on it..... Will look for 'ya there...

I think I know what was going on, and got the box patched.

I've still got a problem with the replacement disk, in that the signature I pulled off the donor doesn't work, but the patch itself HAS now executed.

The VW firmware apparently requires that a playlist have a VALID voice announcement file, or it refuses to run it.  The patch of course doesn't have it there.

The workaround involved hacking the profile so that it ran as an init sound instead, which worked.

Now the trick appears to be getting a good signature on the new disk for the parts that still have to be there....

SOLVED.

I suspect the new patch disk from judb addresses what was found last evening.... :)

Genesis can you let me know what the extras you added to the profiles.ini file for the VW/Adui Phatbox please to get it to play the patch on startup ?

Just set
startup_sound=/dos/data/Music/flactemp.flac
I think that should work.

Judb has it - just stick that in there and it'll run it on startup.

Its harmless to run it more than once, as it checks to see if the patch is there before it tries to actually do it.

This is definitely to your advantage to do if you have a VW, as their firmware apparently will NOT run a playlist that does not have a valid voice tag.

You won't get any notification that the patch ran this way - just start the system, wait 30 seconds or so, turn it off, and wait for the red light to go off before you remove the DMS.

Then go look in the PHTSYS/log directory on your PC (after re-inserting the DMS in your cradle) and you should see a "patch" file in there.  If the file is there then the patch ran; you can look at it in wordpad (it'll be all run together due to Unix linefeed semantics) if you want to see what it did.

There should also be a dmesg file in there and a couple of others - if the patch did NOT run there will be only a file that says "your logs go here" (more or less) in that directory.

Thanks for the info, I now get the patch to run as it creates the log but the new disk fails to work. I think the patch update failed looking through the logs;-


: 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: 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!
Segmentation fault
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: 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!
Segmentation fault
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: 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!
Segmentation fault
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: 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!
Segmentation fault
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 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!
Segmentation fault

let me guess, you have a 20 gig dms and or a VW phatbox?

The patch ran, you are okay there.. its something with your DMS thats causing the problem.  

You may have a DMS where the signature doesn't transfer.  I've seen that...

However, before you are sure that's it, MAKE SURE you put the proper firmware on the NEW DMS.

This is not real clear in the documentation, but you have to do that.  

So once you do the transfer to the new DMS, reboot Windows, put the cartridge back in, load PMM, and go into the options screen for the DMS.

Tell it to load the firmware on the DMS (same firmware you use normally on the box)

Once that's done (it'll just take a few seconds if you've upgraded before) go into the PHTSYS partition (under "my computer") and delete the "forceupdate" file.  That will prevent the box from rebuilding itself when you insert the cartridge.

If THAT doesn't work, then you've got the signature problem.  If you forgot to put the firmware on the new drive, that will fix it (the system actually runs off the disk - it only boots out of flash memory)

Yes its a 20GB DMS and a VW/Audi version

Downloaded the firmware to the new DMS
Deleted the forceupdate file

Now the red light stays on and the green light is almost continously on like its trying to update, but it doesn't get anywhere, after about 5 mins, both lights go out and nothing else

Does your original DMS still work properly?  Check it (if it doesn't, you may have somehow managed to reload the box with firmware for some other system's version - if so, do a firmware update on the ORIGINAL DMS, leave the forceupdate file alone, and let the box do its thing.)

If the original DMS still works, or you fix that problem, then:

Go back into the patch disk, use ALT+F3, and do a repartition/repair/no-bad-block-check (I think its option 3 or 4 - it will say "fast" near it)  This is the ALL TEXT screen with a list of options - it is NOT ALT F1 or F2.

THEN go back into PMM, reload the firmware, then delete the "foreupdate" file.

Note that after you load the firmware you have to "eject" the disk from PMM.  If you didn't do a save/eject then the disk's indices are corrupt and it won't work.

I recommend ejecting it first, then re-inserting it,  Just close PMM when it comes back up.  Once that is closed now remove the "forceupdate" file - this prevents two things at once from trying to dink around with the disk pack and possibly corrupting something on it.

Thanks, checked the original DMS and that doesn't work either :(. I'll reload the firmware on that and try again without touching anything

I'm in the same boat..  No Help

Have 20gb DMS with VW/Audi Phatbox.

So far ->

Step 1.
Old DMS - Ran V1.3 firmware hack   Completed Ok
Put old DMS in car and get the hack audio message.
      
Step 2,
put new DMS and continue firmware hack and this
completes perfect each section.  

Step 3,
Reboot , put a couple of playlists on the new DMS and then install into the car...
Comes back after 30 seconds "No CD"

Step 4,
Try editing the profiles file adding in line
startup_sound=/dos/data/Music/flactemp.flac
I do have this file located in my phtsys drive under
the folder music.

Install in car  -> fails "NO CD"

Step 5,
Try doing a firmware update and then delete
the forceupdate file.
Install in car  -> fails "NO CD"

Out of Ideas... Need Help

Does the original DMS still work?

Hi ,

I put back my Old DMS back in the car
and yes it works fine..

Still get the phathack message then goes
straight into the playlists.

QuoteStep 3,
Reboot , put a couple of playlists on the new DMS and then install into the car...
Comes back after 30 seconds "No CD"

When you install the new DMS, what do the red/green lights on the PhatBox do?  When you turn on the PhatBox (select it on your stereo), you should see the red light come on and stay on; the green light should come on briefly and then go out, maybe flickering once in a while.

I ask, because when I used the hack CD, I ended up with a new DMS that would cause the red light to come on, and then the green light would start flashing codes at me.  Is this what's happening to you?

(I'm still trying to figure out what's responsible for that.)

Ben

You didn't load the firmware back on the new disk.

(yes, you have to in PMM, and its not really obvious from the instructions.  The new disk is BLANK!  The only thing on there is the signature - and if you stick your music on there, that too.  The head unit boots from the DISK - the firmware has to be put back or it won't run!)

Hi Genesis,
If you read my first reply you will see that I ran the firmware update on the new DMS and then deleted the forceupdate file...  doesn't work.

I plug the new DMS in the car and the red light
comes on then a couple of seconds later the green
light comes on for about 10 -20 sec . Then with
the red light still on the green light will come  of the 1-2 seconds then go off .. it repeats about 10 times before you get the message "NO CD"

QuoteHi Genesis,
If you read my first reply you will see that I ran the firmware update on the new DMS and then deleted the forceupdate file...  doesn't work.

I plug the new DMS in the car and the red light
comes on then a couple of seconds later the green
light comes on for about 10 -20 sec . Then with
the red light still on the green light will come  of the 1-2 seconds then go off .. it repeats about 10 times before you get the message "NO CD"

Could that last part be interepreted as "flashing the   green LED 11 times, then repeating"?  Because that's what I had. Not that that helps. :)

-b

Try not deleting forceupdate and let the Phatbox refresh the firmware.

Neither my original DMS or the new DMS work, the original has the green led on for around 5 mins and then nothing, the new DMS either does the same, or the green led flashes every couple of seconds. the headunit reports NO CD on both.

If the original DMS does not work then it got damaged somehow.

Either the partition data is damaged or the signature was destroyed (you put the wrong cartridge in at the wrong time, and wrote trash to the signature blocks!)

You can try to repair it using the utility (the boot screen or ALT+F3 - two options that both do the same sort of thing) from the repair/hack CD, or you can use the tool in PMM that does the same general thing.

If the partition data got damaged that will fix it.  However, if the signature has been corrupted or destroyed then it will not.

If the signature on the original DMS drive got overwritten then you need someone with a valid signature file to put back on it, or a valid DMS you can copy it from.  That will NOT make the DMS "blessed" again, but it will make it work with a "hacked" Phatbox.

In any event if you have a hacked box then the DMS is recoverable (assuming the disk itself is physically ok) as a DMS that will work in a hacked unit.  However, if the signature is damaged there is no way (other than sending it back to Phatbox and paying whatever they want to "re-bless" it) to get back to where the DMS will work in a NON-hacked unit.

Tried firmware update with the new DMS ..
Doesn't work..
Get "NO CD"

Does not even get to the firmware update

Fixed !!!!!

Whoa whoooooooooo....

Thanks Genesis

Followed the manual diagram under -> topic
VW/AUDI 20gb DMS hack... Help