Original DMS dead

[ccobka]

 

I've tried in the past to upgrade my Audi DMS drive to a bigger and had no luck. Now my original DMS 20GB is dead and i have a 40GB drive that i can use instead. My Phatbox should be patched as I've went through this process before but could get the unit to recognize my new drive.

Is there a way for me to create new DMS without having the original drive? I miss my music

[judb]

well it depends on if the hack really finished or not..  you should be able to download the new windows scripts (thread at the top of this forum) and run the newdms bat file and it will set up the new DMS drive for you..

you'll have to add the firmware and whatnot to it, and see if it works.  also you may have to corrupt your ramdisk.sig to have the drive recognized if it didn't complete the hack previously

[sbingner]

Actually, if it didn't complete... you'll need to put the 1MB of 'signature' code on the new DMS so it can pass whatever checks it hasn't completed removing; when the keys are missing it fails every signature check, because the private keys are corrupted.  If the hack had completed to the point of the ramdisk sig needing to be corrupted on the VALID DMS, it should still boot an INVALID DMS since that is the last check being removed.  The only step after that is removing the places where it tries to read the .sig files.

[ccobka]

How do i know for sure if the patch completed before. I did get the prompt stating that it was unlocked but that was a while ago and i couldn't get the new drive to work but my original was working fine so i left it alone. Now my original DMS is dead and I'm not sure where to start i have a 40 GB Toshiba drive that i can use. i ran Repair Doctor and it showed no errors, I also installed firmware from scratch on it and no luck. I've tried the ramdisk method and no luck either. Please help!!!! where do i begin?

[sbingner]

Do you know what version of the patcher you used?  Or do you have the logfiles?

You should be able to just set up the DMS using either the windows scripts or a phatnoise DMS repair CD and load music/firmware on it... if that's not working you'll want to have a bootload.log so you can see if there are any errors.  You can copy an xml file to bootload.log to create it.  You need to have something in bootload.log so it can be written to.  It can not be blank.

[ccobka]

i think i might've been ver 1.18 or i might be wrong it the latest version about 8 months ago but I haven't tried Windows patching i will give it a try and see what happens. It seems that no matter what i tried i was getting both green and red light on the phatbox and it would restart itself every 30 sec or so.

[ccobka]

is there anyone in New York that can assist me with getting my new drive working. My original DMS is dead and i can't get my new one to work no matter what i tried.

PLEASE HELP

[J^2]

This may be a pretty dumb suggestion as I've only been playing around with this for a week or so (and don't even know whether I've successfully patched my own keg yet!) so feel free to shoot me down in flames if it is! 

Have you tried disconnecting and then reconnecting the phatbox itself?

The reason I ask is that I was getting constant green and orange lights on my keg (along with a message saying "NO CHANGER" on the head unit) which didn't go away even when I tried the corrupt ramdisk.sig trick but which eventually went away when I disconnected the keg entirely and then reconnected it.

[ccobka]

i decided to give patching one more try . Borrowed my friends original DMS drive went to through the whole process again. One thing i noticed is that i can't find patchverify.log anywhere. I do however see patch.log file in the log folder and it reads as follows:


: 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

My bootload.log reads:

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

And i still can't get the new DMS to work.

Please help

[judb]

clean all the files out of the phtsys partition, chkdsk it, then extract the firmware files for your head unit onto it.  Then remove the forceupdate and forcesettings files and try again.

[ccobka]

i just did what you suggested. Deleted everything in phatsys partition ran chkdsk and the used PMM to get the latest audi firmware, deleted forceupdate file and still no go 
When i insert new DMS all I see is red and green lights stay lit for about 15 sec and the it restarts and keeps doing same thing over and over again. Based on my previous past can you tell me if my phatbox is patched?

Is there anything else i can try ?

Thanks

[sbingner]

Your phatbox is definately patched... I'd reccomend using the DMS repair boot cd to repartition your drive from scratch (or something else if you know how)... and extract the firmware manually.  Make sure you have no Plugins folder...

you could also try changing your rc.sh to have debugging on so you can get some other output... look for rc_pairs.zip on downloads.phathack.com (google will find it)

[ccobka]

OK so I gave it another try and no luck. I used DMS repair CD to recreate partitions and manually copied firmware files. When i plugged my DMS to my PC PMM told me that i need to update my firmware as well I ignored it just added some music and tried it in my car. That didn't work I connected back to my PC and this time again added the firmware with PMM and still same issue, when i connect it to my phatbox i get Green and red light both on for 10 sec and then it just restarts.  I don't understand what I'm doing wrong I tried with 2 separate drives and i get same result.  ANY other suggestions i can try 

[sbingner]

use debug rc.sh files (see rc_pairs.zip) and see if it's booting up...

[ccobka]

how do i use those files?