help hacking dms - phatbox dead?!? ***PATCHED***

[strictly_biz]

I have the vw/audi phatbox in an audi with symphony head unit.

I was following the pinned instructions.

After doing back up script, ran hack, put dms into phatbox and let it run for a while.

When I went to take it out I turned the stereo on first rather than just pull dms cartridge.

For a second it tried to play something, it announced the album, but no music played and then the cd changer powered off and switched to "cd in". I turned stereo off and checked phatbox, no lights on, so I removed the dms.

When I try to check the log file. It says that the file is corrupted and unreadable. My phatbox will not power on.

please help
thx

[judb]

that happens frequently when the phatbox segfaults during patching, which isn't a major issue.

Run chkdsk on the phtsys drive and that should clean it up.

You will likely end up having to corrupt the ramdisk and rerun the patch (the patch requires the head unit to attempt to play from the phatbox) and then it should be good to go.

[strictly_biz]

I did chkdsk, no luck, repaired/wiped dms with PMM utility, no luck

Pulled/reconnected plug connecting phatbox to head unit and it powered right up...

I guess I'll try running the hack again tonight.

Should I mess with the ramdisk before running hack?

[SteveC]

One thing you need to know is that the patch only runs _when your headuinit is turned on_. This isn't like a normal firmware patch, which is applied while the system is turned off.

Patch the DMS, put it into the Phatbox, turn on your stereo and select the Phatbox as your input. It will look like a song is playing, but there will be no sound. It may reboot a couple times - if your headunit switches to another input, give it a few seconds then switch back to the Phatbox.

After about 1 and a half minutes (at least that's how long it took for me), you should hear the "Your phatbox has been hacked" message. But if it takes longer, let it go for at least 5 minutes. The more reboots it goes through, the longer it will take.

[strictly_biz]

Not sure what I am doing wrong.

Previously I ran patch, then used text editor to add some characters to ramdisk.sig, ran patch again and the patch.log still indicated a problem with ramdisk.sig

So replaced audi firmware, then I replaced ramdisk.sig with a copy of firmware.sig ran patch and this was the result

here is my patch.log


: 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=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
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!

[sbingner]

There are no problems, your box is patched.

[strictly_biz]

Ok, I put the new hitachi 160gb HD into the dms case, ran newdms.bat

copied firmware files from this site and put some music on

put into car and the phatbox has fast blinking green light???

EDIT: ***************

So I let it blink for a while and went to check on it, power on and it worked!

as borat would say, "Success!"

Thanks for your help guys, I now have a huge HD in my phatbox