Phatbox hacking help - Just wont work -Help please

[bazmk2]

Hi need some help

Have tried flashing my phatbox with no luck.

I am using V4 of the hack, but executing it manually (have copied the backup directory from my new drive, and the flacplay and aacdec from there and try to play a flac, Have also move plugins)

Here are my logs

Patch Verify

Code Select Expand

Starting Patch Process
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!


[bazmk2]

PatchWrite.log

Code Select Expand

PhatPatch v0.4 - original code by bushing, additional patches by sbingner
first 2 words of flash=c102 0025
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=c102, device id=0025
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...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...
Waiting...


Continues loads more waiting

[bazmk2]

Patch.log

Code Select Expand

: No such file or directory
: No such file or directory
: No such file or directory
: No such file or directory
: No such file or directory
: No such file or directory
: 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
: No such file or directory
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!
2048+0 records in
2048+0 records out
2048+0 records in
2048+0 records out

And continues on like this

[bazmk2]

I have now repartitioned the original DMS, reloaded the cd onto it and nothing

A few extra things I have noticed

dms-serialnumbeumber.txt is empty

the 1024 signature file that is at the beginning of the script is very rarely 1024kb long

still getting the waiting...

[bazmk2]

Does it matter what firmware I am running, I currently have the 7.2 any idea how to get an older one back on it??

[A543]

It shouldn't matter what firmware you are running.  What headunit type is your box set up for?
Is there a reason that you haven't tried the fully automated method? When you reformatted, did you reformat both partitions? When you attempted the patch after that did you get logs similar to the ones you got the first time?

[bazmk2]

The DMS was repartitioned so both were reformatted

I have tried the patch a lot!  Both before the repartition and after.

I have tried the script method, and the cd, and also using the files off of the CD.

The head unit is set up for the Audi Symphony 2

I tried the automated CD initially, and got similar logs to what I have now


All I seem to get is a "waiting" in patchwrite.log, seems as if it is not actually writing the code to the flash bootloader but I don't know why

If I was able to get a serial connection into the box, would I be able to write the code using that?

[judb]

isnt there another log file in that directory with patch in the name?  please post the contents of that log too.

[bazmk2]

no the only files in the log directory are those 3

Will have another go tomorrow and check tho'

[bazmk2]

Ok I have just repeated the exercise, using the cd

Follow instructions as per cd

put dms with code into box

get silence then broken stuttering as it tries to play the next playlist (waited 1 min)

turn off ignition

Go to boot wait for box to stop spinning ang when all lights off pull dms

look in log directory  Have patch.log, patchverify.log and patch write.log, with the same contents as I have posted

dunno what else to do

Will reformat and try again

[bazmk2]

OK Reformatted

Used CD

Doesn't work, doesn't appear to copy over playlists ?? why; does copy flacplay aacdec and sigs, makes log directory, when try to use in car just get patch.log with

Code Select Expand

no such file or directory

So removed startup flac from profiles, copied a ripped flac onto dms

goto car, load dms, plays normally, try to play flac, no noise, then goes on to play mp3, get usual stuttering.

Same log files as above

ANy ideas

Am I missing a file from the patch somewhere, or is it missing from the linux distro on the dms ( hence the missing file lines?)

I also have a dms-serialnumbeumber.txt that is empty and a drive-sig-1mb.bin in the backup folder that is not 1mb (899Kb)

is this significant?

Contents of my backup directory following the cd adding stuff and being run on the box

Code Select Expand

26/07/2005  21:51                 8 P0.idx
26/07/2005  21:51            25,327 aadec-hacked
26/07/2005  21:51               237 aadec-hacked.sig
26/07/2005  21:51           119,614 patchcomplete.mp3
26/07/2005  21:51                58 flacplay-hacked
26/07/2005  21:51               242 flacplay-hacked.sig
27/07/2005  17:28           440,300 phatpatch
26/07/2005  21:51             1,156 patch.sh
26/07/2005  21:51               234 p0.sig
26/07/2005  21:51               137 p0.pbx
26/07/2005  21:51               101 p0.m3u
26/07/2005  21:51                22 version.txt
26/07/2005  22:51            24,838 phatpatch-v2
17/01/2003  11:24           102,912 flacplay
03/11/2004  15:20               239 flacplay.sig
04/10/2004  18:55           110,000 aadec
03/11/2004  15:20               242 aadec.sig
01/01/1980  00:00           920,064 drive-sig-1mb.bin
01/01/1980  00:00                 0 dms-serialnumbeumber.txt


[judb]

The CD uses a method that modifies your profiles.ini to have a startup sound that is FLAC ... so having a playlist is not required.

Perhaps you should do it with the manual method?

[bazmk2]

ok now have cleared the backup directory.

Downloaded script method from wiki

Copy files over

copy flacplay-hacked to flacplay and sig

Still no go

Latest logs are only  patch.log and phatpatch.log

Code Select Expand

PhatPatch v0.2 -bushing
first 2 words of flash=c102 0025
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=c102, device id=0025
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...
Waiting...

and continues

I do now have a valid drive signature backup tho' as it is 1024kb

I have tried to edit the drive signature bit out of the script to see if that helps but it don't

How important is case, ie Backup or backup.  Does this also apply to the files? ie Phatpatch

still no joy

[judb]

case wont matter because its mounted a fat32 filesystem.

I am begining to think its something with your flash chip causing the issue..

Bushing, where have you been?

Sbinger?  any ideas?  I am stumped.

[bazmk2]

do you want me to look inside the thing to see what the chip is?? and post some photo's

What part do you need to see?

[judb]

no no, thats okay.  I need someone smarter than I am to help out as I am at a loss as to why it always hangs trying to write the first update. (that and I don't have a dev setup anymore, the keg is no longer in the house on the desk heh.)

[A543]

judb, you had the same problem,
http://forum.phathack.com/cgi-bin/yabb/YaBB.cgi?board=dmshack;action=display;num=1122187002;start=48#48
Maybe you remember how you fixed it?

[judb]

mine was able to get past the first item and would hang.  I ended up just having to run it three times to get all 7 patches to apply.

Your situation is it wont program the first block correctly every time you try it (at least from the logs)

if it says "Match! Programming" that means the block is set to the original code from phatnoise and needs to be changed.

How long have you had this box anyhow?

[bazmk2]

its in the newly bought car car, which is 11 months old and was a demonstrator for the Audi Dealer


Its from audi, but the fins are not the vw/audi shape, they look like a normal phatbox, don't know if it was factory fitted or an add-on from the dealer

[A543]

judb, I posted your old entry because your log was exactly the same as bazmk2's log, with the "waiting". If it's adding waiting to the log, then the box itself isn't locked up, maybe just the eprom programming thread? I also noticed that both of your logs had the same entry for the flash chip manufacturer. That chip code isn't on the Wiki page that lists the know chip IDs. Based on sbingners answer to judb's log, I would guess that the chip isn't responding to commands.  judb, did you have those same entries in the log when you had a successful patch? I suspect they were different.

Wasn't there a "Phatbox Elite" or something similar? A limited edition box. Maybe, since this appears to be a Phatnoise demo, it's that model, and has different guts?

basmk2, do you have any plugins installed on the box? If so maybe removing them before running the patch might do it.
Also, it seems that people have had problems with disk corruption (I did with both boxes I ran the patch on) during the patch.  I think it is mostly problems with bootload.log. If you are using bootload.log, try it without it. For the patch logs, erase the logs folder, run chkdsk to make sure everything is ok, then run a full defrag of the PHTSYS volume. Then create the logs folder manually, and add a blank log file phatpatch.log as the last thing you do, so its FAT entry is at the very end of the used space.
I know these things are really grabbing at straws, but until sbingner or bushing show up, it's something to try, if you want.