audi dms hack not flashing, help? logs inside

[brax]

hey guys, i have followed the faq/dir to a T over and over, the first round it act'd like it flash half way then gave me a "no changer " error" after about 12 secs, so i cycled power then it counted up about 9 more secs, then a high pitched squeal, then another no cd changer error,  after playing around with corrupting ramdisc and aadec, it started playing my old music "without ever having a completed voice"  but the new drive still will not work, i do  not think the patch is flashing to my old drive fully, it finds the drive and selects it, but on the final step after about 5 secs it closes the dos window without saying completed "winxp"  heres my logs, TIA

patch log=


: 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=0001, 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

                                                           



                             and the bootlog, not sure if you need it =

 

<ini_file>phatbox.ini</ini_file>

<property>
<name>Number of Kenwood Display Digits</name>
<ini_field>kenwood_digits</ini_field>
<description>Number of disc digits displayed on your radio.

Certain radios have protocol limitations that restrict disc numbers greater than 10.  If you are experiencing problems with discs greater than 10, please switch to "1 Digit Display".
</description>
<value>
<ini_value>2</ini_value>
<name>Kenwood 2 Digit Display (factory setting)</name>
<description>Displays 2 digits for the track number on your radio.

NOTE: KVT-910DVD, KVT-911DVD, KVT-M700, Double-Din radios; Please use "1 Digit Display"

2 Digit Display includes the following radios:

2003: 300 series radios and up and KCA-R70FM (FM modulator)
2002: 500 series radios and up
2001: 600 series radios and up
2000: KDC-X915, KDC-X815 only

1999 and older: Use "1 Digit Display"
</description>
</value>
<value>
<ini_value>1</ini_value>
<name>Kenwood 1 Digit Display</name>
<description>Displays 1 digit for the track number on your radio.
</description>
</value>
</property>

<property>
<name>Playlist Announce</name>
<ini_field>announce</ini_field>
<description>Uses text to speech to announce the current playlist.</description>
<disable><condition>kenwood_ssa=1</condition><force_ini_value>1</force_ini_value></disable>
<value>
<ini_value>0</ini_value>
<name>Off (factory setting)</name>
<description>Silent disc changes.</description>
</value>
<value>
<ini_value>1</ini_value>
<name>On</name>
<description>Announce disc changes.

NOTE: Disc change announcements are always "On" if running Kenwood SSA.</description>
</value>
</property>

<property>
<name>Track Display 250</name>
<ini_field>track_display_250</ini_field>
<description>Display track numbers up to 250 (if your radio is capable of it).

This only works on 2001+ model years that utilize 2 disc digit displays.
</description>
<disable><condition>kenwood_digits=1</condition><force_ini_value>0</force_ini_value></disable>
<value>
<ini_value>0</ini_value>
<name>Off (factory setting)</name>
<description>Display track numbers up to 100.

NOTE: If head unit is not capable of running "2 Digit Display" code, this functionality will not work.
</description>
</value>
<value>
<ini_value>1</ini_value>
<name>On</name>
<description>Display track numbers up to 250.

Note: If incorrect numbers appear for tracks greater than 100, switch back to "Off".
</description>
</value>
</property>

<property>
<name>List Title Text</name>
<ini_field>list_title_text</ini_field>
<description>Generates custom disc text on your radio.</description>
<value>
<ini_value>%m%n: %t</ini_value>
<name>Abbreviated Mode Disc Number: Disc Text (factory setting)</name>
<description>Abbreviated Mode Disc Number: Disc Text

Examples:
"PLY14: New Encoded Albums"
"ART132: The Beatles"
</description>
</value>
<value>
<ini_value>%M%n: %t</ini_value>
<name>Mode Disc Number: Disc Text</name>
<description>Mode Disc Number: Disc Text

Examples:
"Playlist14: New Encoded Albums"
"Artist132: The Beatles"
</description>
</value>
<value>
<ini_value>%t</ini_value>
<name>Disc Text</name>
<description>Disc Text

Examples:
"New Encoded Albums"
"The Beatles"
</description>
</value>
<value>
<ini_value>%t (%M%n)</ini_value>
<name>Disc Text (Mode#)</name>
<description>Disc Text (Mode#)
This mode is useful for radios with limited text display capabilities

Examples:
"New Encoded Albums (Playlist14)"
"The Beatles (Artist132)"
</description>
</value>
</property>
</properties>

[VorTechS]

A couple of things:

1) The hack has been applied to the box successfully.
2) You don't mention which head unit you are working with, or which version of the firmware you have on the DMS, or if you've loaded up the new DMS with music via PhatNoise MM

[brax]

ok, i have the audi nav+ headunit, "same commands as the concert2 etc"

im not sure of the firmware,  will mm tell me?

as for the new drive, i followed the instructions and did the test for the "invalid track" but it gives me a no changer error almost instantly.

i unpatch'd the old cart. then try'd the new beta sw, it repatch's me, then tells me to insert the cart into my dms to let it update,
so i do this and it plays my first 2 cds as normal instantly, i let it run for 15 mins, still the same, no update and i only have my first 2cds now when i had over 60..

so i re-insert the cart into the base and run the beta wizard as prompt'd and it tells me im stuck at step 6 and to insert my cart back into the dms to update!

:bangshead:

should i wipe the old cart and restart?


p.s.   audi/volkswagen  brand stereos. vs 5.01

[brax]

ps getting a constant "no changer msg"

heres the boot log

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

[brax]

wish someone could help, looks like my system is bricked, constant flashing green light, constant no changer msg, how do i put it back to oem? ive tried unpatch'n as well, i made backups of everything

[brax]

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!

[VorTechS]

The box is hacked, the log you just posted shows this.

Where it says Verified = Box hacked.  There may be an issue with the Beta software looking for a file that hasn't been created - which is an oversight on my part.

Sorry but sometimes because people post here about problems, and don't reply correctly to the Beta mail I send it, I don't pick up the association between your nick here and an e-mail address.

Please send me the contents of My Documents\PhatHack Media Manager\Log so I can take a look to see why it doesn't verify the patch.

Can you tell me which operating system you are using to apply the hack also?

[brax]

well, right as i was about to give up, "murphys law" i started the car and bam, it updated,,...

which makes no sense cause my amps were on, deck was on, dms had power, and i cycled power to all numerous times, "dont ask"


but its working now, thank god!

mental note for all updaters!

[ccobka]

I've been having the same issue for about 6 months not I'm using Audi RNS-E Nav. How did you get it to work. I've done this patch at least 20 times with different drives and no luck. I believe my phatbox is patched but it will not play from the new DMS original works well.

[judb]

there has to be something about the files on the new dms that it doesn't like...  if your patch log shows everything verified then the box will run a non phatnoise dms.. its just getting the right files on the DMS to let it work.

[VorTechS]

You could try the new tools, which I am thinking very hard about making available outside of beta. 

I can certainly use more testing on the New DMS side.
I don't think you've run the Alpha tools before have you?

[ccobka]

i did run the alpha tools but had similar luck as before new DMS wont work.

[VorTechS]

PM sent.  Try the updated tools, and let me know if you are still having problems.