Windows phatbox hack not working... what to try next?

[rumatt]

I tried the windows phatbox hack tonight, and I'm not having any luck.  It looks similar to rayner's issue.   Here's what happened:

1) I ran DMShack.bat, put DMS in phatbox, and after about 15 seconds got "No Disc"

2) I corrupted ramdisk.sig,  restarted phatbox, and after about 15 seconds, music on the phatbox starts playing.  I get a patch.log file which says the patches were already applied (details below) but I do NOT have any patchverify.log files

3) I tried cleaning the DMS and re-hacking, but now I keep getting the same result as (2), it just starts playing my music, and patch.log says the patches were performed.

4) When I try to use a new DMS, it just hangs at boot, and error_log.txt mentions something about a drive mismatch (I can get the exact error, but I assume this is the standard error given for a non-hacked phatbox)

It seems that the hack is not completing, and it gives up and starts playing music.  Any ideas what I should try next, or how I can debug this?  Thanks in advance.

[rumatt]

Profiles.ini

Code: [Select]

[Default]
num_discs=2
startup_sound=/dos/Music/flactemp.flac
pattern=$TITLE$ - $ARTIST$
album_seek=alpha

[profiles]
active_profile=Default
enable_special_discs=1
enable_voice_prompts=0
num_discs=2

[product]
product_name=PhatNoise Media Manager
product_version=3, 5, 1, 0



[rumatt]

patch.log

Code: [Select]

: 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!
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=0020, device id=0057
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...
Wrote 0000
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0026 1a00    Actual: 0026 1a00
Match! Programming...
Wrote 0000
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0019 1a00    Actual: 0019 1a00
Match! Programming...
Wrote 0000
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 000c 1a00    Actual: 000c 1a00
Match! Programming...
Wrote 0000
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13e0    Actual: 0000 13e0
Match! Programming...
Wrote 13a0
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0001 e350    Actual: 0001 e350
Match! Programming...
Wrote 0000
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0001 03a0    Actual: 0001 03a0
Match! Programming...
Wrote 0000
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: 02db eb00
Match! Programming...
Wrote 0000
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: 02f7 eb00
Match! Programming...
Wrote 0000

: 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!
[continued]


[rumatt]

patch.log continued (software won't let it go in one post!!!)

Code: [Select]

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=0020, device id=0057
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

: 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=0020, device id=0057
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


[rumatt]

bootload.log

Code: [Select]

BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9-X: Successful
BOOTB-X: Successful
BOOTF-X: Successful
BOOT*: Successful
^@


[sbingner]

Your logs say your box is patched -- not only that, they say it did it on the first attempt *pats self on back*

Anyways, sounds like you have a problem with your NEW DMS... couldn't tell you what, but I'd suggest formatting it and putting a clean fresh 'firmware' load on it for your head unit

[sbingner]

Also, for a non-hacked phatbox you'd see absolutely nothing on the new drive since it would never get that far.  If you have something in error.log it measns it actually booted up and executed phatd/51d

[rumatt]

Thanks sbinger.

I re-formated the new DMS, put on the latest firmware, and very quickly I get "CD CHECK" on the head unit.   

The lights on the phatbox alternate between red, and green+orange.     I left it 5 minutes and nothing changes.  It even keeps doing this after they key is turned off.

Looking at the DMS, there are now no log files.  No bootload.log, and error_log.txt remains empty.

I tried a couple times with the same result.  I also tried upgrading the firmware through the media manager instead of manually, but the result was identical.


I found it surprising that I never saw a patchverify.log after the hack.   Anything else to try?

[judb]

okay so you made the new dms with the newdms script right?

you don't see a bootload.log?  Could you create one by making a copy of one of the other files, like the phatbox.ini for example and renaming the copy bootload.log ...  then try it in the phatbox and see if the contents get changed.

I assume you checked to make sure that the drive wasn't jumpered wrong so that the phatbox doesn't see it?

[rumatt]

Yes, I made the DMS with newdms.bat.     I created a file bootload.log like you suggested (by copying phatbox.ini) and tried again, but it was not modified.  There are no jumpers, so the drive claims this is master.    It's a 120 GB western digital drive that works fine in the cradle from windows.  Checkdisk on the phatbox drives succeeds.

I just made a fresh dms with newdms.bat, and here's what happens

 - Disconnect phatbox form car, wait 10 seconds, reconnect
 - Insert DMS into phatbox
 - Red light on phatbox stays lit, does not go out after 30 seconds
 - Put key in ignition, turn on radio, it quickly moves to "CD CHECK"


I'm reinstalling the original drive now, to confirm one more time that it still works.

[rumatt]

My original drive still works fine.      For some reason the phatbox is not happy with the new drive.

Hmmmmmmmmmmm.....

I'm not sure how to debug this if:
  a) The drive works fine on the PC
  b) The phatbox isn't writing anything to the drive
 

[judb]

did you open the bootload.log to verify the contents were not changed?  the phatbox does not update time stamps as it has no internal clock that is synced to any time source.  each power on the clock starts Jan 1 1970 i think.

[rumatt]

Yes, I had verified that it was unchanged because I had emptied out the contents of the file, and it was still empty.   But on the latest run I managed to get a bootload.log by doing the following:
 - run newdms.bat
 - Open Media Manager.  Confirm the firmware is the latest, sync (to put a couple songs on), save and eject
 - Copy a file to bootload.log (and don't empty it out, maybe this was the problem?)
 - Put DMS in phatbox and I get a "Disk 1-" on the head unit, but it just stays there (waited 15 mins)

The bootlog seemed successful (below) and the contents of error_log.txt were unchanged 

Code: [Select]

BOOT0-0: OK
BOOT0-1: OK
BOOT0-2: Successful
BOOT9-X: Successful
BOOTB-X: Successful
BOOTF-X: Successful
BOOT*: Successful
^@


[judb]

do you have a plugins folder? 

if you do, rename it and see if that helps.

Also I strongly suggest getting the rcpairs.zip from downloads.phathack.com under sbingner's folder and use the level 10 scripts.. replace the files on phtsys with them.. that will give you max debug logging.

[rumatt]

It worked!   Sort of.   I still get "audio player not found" for AAC files.

Here's what I did:
 1) ran newdms.bat
 2) Removed everything in drive [phatsys]
 3) Used media manager to download firmware (probably the same as unzipping them myself, as the version was the same)
 4) removed forceupdate from [phatsys]
 5) PMM sync
 6) PMM save/close

I had already done the above several times, but without step #5 (sync)   Does it make sense that this should matter?  It seems to have mattered to me, but it's possible it was coincidental.   It seemed that several times things did not quite repeat the same way.

In any case, the drive is now playing, but I get the dreaded "audio player not found" for AAC files.   I have tried:

 - copying in aadec-hacked and aadec-hacked.sig (and renaming)
 - copying in the original aadec and aadec.sig
 - removing Plugins/plugins.dat

All with the same result.   "audio player not found"

Thanks again for all the help guys.

[rumatt]

OK, I did the following and now AAC files play.       I swear sometimes I think this process was not deterministic, because I know I did this already 

- Move plugins directory out of the way
- Play phatbox and confirm "audio player not found" for aac files
- Put DMS back in cradle and copy in the plugins from the old drive, and also aadec and aadec.sig

Put in phatbox and they play. 

[sbingner]

I really wouldn't haev remove the forceupdate file once... ometimes it seems the phatbox needs its firmware updated

It does sound like originally when you saw the lights on constantly that it was updating your firmware and you needed to let it sit long enough to complete...  either way, glad you're working now

[rumatt]

Thank again for the help guys.