Problems after (unsuccessful?) Patching - AUDI

[a6_tobo78]

Hi folks,

(sorry if there is something hard to understand, as english isnīt my native language)

today i tried to change the drive in my dms into a bigger one.

I downloaded the CD-Image 1.5 and went trough it following the instructions.

Everything looked fine, but patching my audi 7.02 firmware failed. DMS was inserted, but nothing happened: played the first list as usual - music. tried the second list - same. So i turned everything off (everything as usual), took the dms and resumed the setup process from cd.

The new drive wasnīt recognized, the headunit (audi navigation system) said "no cd magazine".

I Started over.

Now as the first playlist i heard a tone which didnt change. that lasted for about 50 seconds, then the HU said "no cd magazine".
The problem is, that even my original dms is regognized anymore. Always "no cd magazine" - pb turns off then.

I did a backup before i started - all files on sys and data have been copied to my harddrive.

I tried the manual patch then - nothing changed.

The last thing i did was wiping the drive using the pmm and installing the latest firmware from the website. I read something about rebooting the phatbox, so i cancelled power supply by disconnecting the cable. Then i inserted the "fresh" original dms, and reconnected the power supply. The device started flashing green.

That was about 1 hour before. The green LED is still flashing. Nothing changed, except the HU doesnīt say "no cd magazine" anymore. Now it tells "no cd changer".

log files following

If youve got any suggestions, please let me know. is my PB messed? what can i do?

thanks a lot

tobo

[a6_tobo78]

bootload.log:

BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*-X: Failed
                  
error_log.txt

CORRUPT_FILE: TTS.1.1

patch.log


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


patchverify.log

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

patchwrite.log

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=0004, device id=22bf
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: 000c 1a00
Match! Programming...


I didnīt care for the logs on the beginning, so i donīt know wheter they are from the first or second try

[a6_tobo78]

okay, looks like my PB is f***ed up.

The flashing didnt stop. Now, two hours later, i disconnected the power supply to take a look at the dms - nothing changed, no new or changed logfiles.

There must have been something gone wrong while patching.

I think that the PB doesn`t boot because of a broken firmware / software. Is there a way to check the phatbox boot progress?

Any suggestions?

[sbingner]

corrupt your ramdisk.sig as mentioned in other threads here.  Easiest way is to overwrite it with linux.sig (after saving a backup) then re-run the patcher

[a6_tobo78]

Whooohaaa!!!

After the ramdisk.sig procedure my PB stopped that spastic flickering and i heared the real lovely "Welcome to the Phatbox car audio system"....

Thanks to sbinger for this suggestion.

Now i will try to run the manual procedure. After reading some threads here - wouldnt it make sense to change the bootdisk and CD-Image to give a very understandable hint on the first screen to VW/Audi users that the procedure may not work?

I will report when i am finished or run into other problems =)

THANKS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[judb]

Actually the issue could happen on any version of the phatbox.. it just seems to happen to Audi / VW ones all the time but it could be since most people seem to have bought them when they were around 100 bucks that its a stastical issue.

When the patch hangs it usually hangs at the point where its doing the ramdisk.sig check and to get past that you must corrupt that file and re run the patch (just start the old DMS up again a second and optionally a third time in the phatbox) and that should get it where you can have corrupt or valid sig files.

[A543]

@judb
I remember you mentioning something about wanting to have the patch automatically corrupt the ramdisk.sig during the patch process. Is it something that could still be done?

[sbingner]

I've actually updated one to do that but nobody's tested it yet....