Author Topic: Unable to Patch Audi Phatbox  (Read 12062 times)

0 Members and 1 Guest are viewing this topic.

Offline 01S8

  • Newbie
  • Posts: 11
Unable to Patch Audi Phatbox
« on: March 23, 2007, 08:33:11 pm »
2001 Audi S8
I recall the dealer called me to come buy the first Phatbox available at their parts dept for Audi, as they knew of my interest, so, an early model?  any differences?
20GB DMS

I tried this process first with 1.0.3  same result.  then ran patchclean(hmm, maybe wasn't supposed to do that, but 1.0.3 was not working, wiki said return DMS to original state).
Then, retried with 1.1.3 logs below are from this try....

current state:
1.1.3 patch is on the DMS, DMS is backed up, new 160GB Seagate is here, ready to go
waiting for instructions on how to get past this hitch in the patching process....

Link to copy of current state of my DMS
PHTSYS and PHTDTA(all inclusive except mp3 files/tts wav's) ~10mb
http://www.send6.com/a96faaf9c41267e95e23ccc59cb7a571/
Sent file(s): PHTSYS.zip, PHTDTA.zip



output from backupdms and dmspatch:


C:\dmsutils>backupdms
 
This script will make a backup of your DMS and collect some
information about the config of that DMS that we'll use later.
 

If you are sure you are ready to run this, please press enter
otherwise use CTRL-C to abort.
 
 
 
***************************************************************
Please ensure DMS is NOT connected and press enter to continue
***************************************************************
 
***Scanning Currently Connected Disks***
 
***************************************************************
Please insert stock (original) DMS And make sure that the
DMS drive letters are seen for PHTSYS and PHTDTA in explorer
***************************************************************
 
Press Enter to Continue when ready
 

***Rescanning Connected Disks***
 
***Rescan Complete***
 
***Determining if new DMS drive is seen***
 
Testing disk 2 (19 GB)
* Volume 4     G   PHTSYS       FAT32  Partition    260 MB  Healthy
Found PHTSYS on G: - backing up to phtsys.tar.gz
tar.EXE: Removing drive spec from names in the archive
Backing up drive signature to "DMS-1MB-USB-FS PhatNoise DMS 20 USB Device.bin"
1024+0 records in
1024+0 records out
All done, you may now use newdms to create your new DMS when ready
 
C:\dmsutils>dmshack
**************************************************
         This script will prepare your
             ORIGINAL PHATNOISE DMS
 for modifying the flash based bootloader in your
     Phatnoise Phatbox / Kenwood Music Keg
**************************************************
 
****************************************************
 DO NOT USE A NON PHATNOISE DMS AS IT WILL NOT WORK
    Borrow one from a friend or buy one on EBAY
   Changes to the ORIGINAL DMS are not permanant
****************************************************
 

*** It is STRONGLY suggested that you disconnect all *OTHER* USB storage***
 
 
 
****************************************************
 Press Enter to continue, Press CTRL-C to abort...
****************************************************
 
***************************************************************
Please ensure DMS is NOT connected and press enter to continue
***************************************************************
 
***Scanning Currently Connected Disks***
 
***************************************************************
Please insert stock (original) DMS And make sure that the
DMS drive letters are seen for PHTSYS and PHTDTA in explorer
***************************************************************
 
Press Enter to Continue when ready
 

***Rescanning Connected Disks***
 
***Rescan Complete***
 
***Determining if new DMS drive is seen***
 

***WARNING***
 
Microsoft DiskPart version 5.1.3565
 
Copyright (C) 1999-2003 Microsoft Corporation.
On computer: DELL8200
 
Disk 2 is now the selected disk.
 
USB-FS PhatNoise DMS 20 USB Device
Disk ID: 67E73B3F
Type   : USB
Bus    : 0
Target : 0
LUN ID : 0
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 4     G   PHTSYS       FAT32  Partition    260 MB  Healthy
  Volume 5     H   PHTDTA       FAT32  Partition     18 GB  Healthy
 

This drive will be used as the destination for the HACK process..
***WARNING***
Files will be copied into a backup folder for safe keeping.
 
Press ENTER to continue or CTRL-C to abort
 

mkdir.EXE: cannot make directory `G:/backup': File exists
mkdir.EXE: cannot make directory `G:/log': File exists
mkdir.EXE: cannot make directory `H:/music': File exists
 
******************************************************************
You may now eject your DMS and execute the Flash Bootloader Patch
When this process is completed you should run the patchclean.bat
 
This will restore the backedup files onto your Original DMS
So that you can resume normal playlist operations.
******************************************************************
 
C:\dmsutils>

So, both scripts seem to work.
I follow the procedure at http://wiki.phathack.com/Windows_Hack_Procedure

after inserting the DMS, the Phatbox boots, and eventually (under 40 seconds) just starts playing music as usual.
No hack executed.

There are no log files in /log - empty directory

If I corrupt the ramdisk.sig file with 8 or 9 extraneos letters at its beginning(saving the old one) the phatbox boots, then shuts down and goes to another source on the headunit.  I retry 6 times. Same thing each time.

 bootload.log:

BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*-X: Failed
                                                                                                                         
If I restore the ramdisk.sig to its original, the phatbox boots, does not apply the patch, and plays music as usual, and the bootload.log looks like this:

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

                                                                                                                         
Please see link above to copies of the DMS folders in their current state.

Thanks for your help, in advance....

Offline 01S8

  • Newbie
  • Posts: 11
Re: Unable to Patch Audi Phatbox
« Reply #1 on: March 23, 2007, 11:47:04 pm »
Able to get to patch 6 now, after wiping phtsys dir, and replacing with files from downloads.phathack for audi v7.2
plus, rerunning the 1.1.3 patch...
something wrong with profiles maybe, as suggested elsewhere in the forum....

now, I'm stuck on flashing patch 6- ramdisk..

I assume this is where you need to corrupt the ramdisk.sig file.

I've tried replacing it with another,renamed file, and also entering hash characters into it via a text editor...

the box reboots again and again and does not progress....

any advice?  I'm going to try it more... but maybe I'm doing something wrong at this stage....



: No such file or directory
PhatPatch v0.7 - original code by bushing, additional patches by sbingner
Verifying:
PhatPatch v0.7 - 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=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
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: 0001 e350
Match! Programming...



Offline 01S8

  • Newbie
  • Posts: 11
Re: Unable to Patch Audi Phatbox
« Reply #2 on: March 24, 2007, 12:13:21 am »
Unplugging the cable from the headunit to the phatbox, plus 4 more reboots, and on the final boot, the box stayed on for 15 minutes or so.

Is the patch complete now?


: No such file or directory
PhatPatch v0.7 - original code by bushing, additional patches by sbingner
Verifying:
PhatPatch v0.7 - 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=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
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: 0001 e350
Match! Programming...
: No such file or directory
PhatPatch v0.7 - original code by bushing, additional patches by sbingner
Verifying:
PhatPatch v0.7 - 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=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
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

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Unable to Patch Audi Phatbox
« Reply #3 on: March 24, 2007, 08:07:28 pm »
yes all the patches are applied according to the log.

Offline 01S8

  • Newbie
  • Posts: 11
Re: Unable to Patch Audi Phatbox
« Reply #4 on: March 25, 2007, 11:56:44 pm »
patch Complete, New 160gb DMS working

Put the old phtsys files from stock dms on new dms after running newdms.bat
Replaced the old linux 800kb with the new linux-lba-48, renamed to linux
The new LBA-48 Linux didn't seem to like the phytsys files from the stock 20gb DMS..
Replaced all other phtsys files with the Audi specific ones from http://downloads.phathack.com/firmware/

Phatbox booted after 45 seconds or so, and now works fine.

it appears to be more reliable, both for the initial hack using the old DMS, and, with the new DMS drive, to use the firmware found at http://downloads.phathack.com/firmware/

Thanks guys, for the help...

Offline 01S8

  • Newbie
  • Posts: 11
Re: Unable to Patch Audi Phatbox
« Reply #5 on: March 26, 2007, 12:33:27 am »
more info here, related to this same job
http://forum.phathack.com/index.php/topic,1026.0.html