PhatHack
Phatbox / Keg software and support => Phatnoise Media Manager => Topic started by: rjw75 on January 22, 2011, 07:15:33 pm
-
Hi gents, please can someone help me. Recently purchased a B5 RS4 that came with Phatbox fitted. Cradle, cd rom etc came with the car. All working ace, then stopped working (not ace!). The install was v,questionable so the cable looked to have been bent at the Phatbox end. I ordered said cable from the States, fitted & it still doesnt work. After much trawling the internet with my Whiz Kid friend, he came to the conclusion i have managed to loose the drive-sig-1mb.bin file. We have tried rebuilding the DMS on several occasions to no avail. My laptop has also died so i cant access the original backup!
The DMS is recognized by Music Manager but the headunit Audi Symphony doesnt see the Phatbox. I simply get the red light then 4 green flashes then the rapid blinking green light then after some time it repeats this process! Can anyone please shed some light or even email me a good file for my DMS.
Even the 6 cd Audi changer i have borrowed has given up & "ERR 3" me! :'(
Many thanks. Newbie Raoul. ???
-
When you say you have tried re-building the DMS, is this by using the DMS tools? (http://forum.phathack.com/index.php/topic,2605.0.html (http://forum.phathack.com/index.php/topic,2605.0.html))
If so, have you tried using the 'Boot Check' function?
However, with you saying the CD changer is not functioning it's a possible indication there's a problem with the HU itself.
-
Hi. Yes we tied to rebuild the DMS using DMS tools. To be honest from memory i dont think the boot check option was high lighted so we couldnt use it? I havnt seen my friend for a week so i'll check again with him today hopefully. The changer i was using was second hand. I have a brand new headunit its just if i dont have to dismantle my dashboard the better! ;) :D
I shall report back soon.
Thanks again for your help. 8)
-
Hi, checked with my friend. We did try DMS Doctor and it always failed the boot file check. Is this file available on your programme anywhere?
The Phatbox worked fine then suddenly stopped. It was very poorly installed and the cable was badly bent at the plug so i assumed it was the cable & had a new 1 shipped from the States. That is when the trouble started, i may have unplugged the lead when it was still active? To be honest we arent sure what to try next?
The changer i borrowed worked fine for a couple of days before giving me the ERR 3 code so i'm not sure its the headunit. Please help as i'd love it back working, i've only owned the car since August last year.
Thanks again.
Best wishes, Raoul.
-
DMS Doctor?
-
Yes its a file that we found in a download.
-
Don't use DMS Doctor - use my DMS Tools as given in the earlier link which has a boot check function.
If the box is booting, but not correctly, it may give an indication as to what the problem is.
-
Excellent. Thanks for that. I'll try next week when we're back at work (thats where the box is).
Many thanks again, i'm sure we'll crack it eventually! ;D ;)
-
This is what we got after trying the DMS Doctor.
-
This is how we have the drive configured, is this correct?
-
PHTDTA
-
PHTSYS
-
This is the file we think we have corrupted/lost. After formatting & trying to make a new DMS. Can anyone send us the 1st meg of this BIN file?
-
I'm not sure what file DMS Doctor is trying to find, but it won't be the bin file.
Somehow we are getting wires crossed, so could you do the following for me?
Please download the tools located within this thread (http://forum.phathack.com/index.php/topic,2605.0.html), install them, run them and then:
Click on DMS Tools mode
Select your DMS (if not selected already)
Select the appropriate firmware (if not selected already)
Ensure the option 'Install non-hacked firmware' is checked
Uncheck the option 'Reflash box'
Click on 'Update Firmware'
Once complete then click on 'Boot Check', you will get told that a file has been put on the DMS.
Eject the DMS and put it in the car. Start it all up. Give it a few minutes, bring the DMS back to the PC and run the DMS tools again.
Click on 'Boot Check' and then please tell me what it says.
-
Good morning squire. I shall do this later today, as i work shifts i wont be at work til this afternoon. Many thanks again for your prompt help.
-
Hi, followed your instructions as directed & this is what we got.
-
The boot check then said this.
-
Hmm, there has to be a common pattern here as this is getting a bit frequent! ;)
The box should overwrite the bootload.log file when it starts, even if you have lost the magic signature. If the signature is missing, the bootload.log would contain an entry saying so.
The fact that the bootload.log isn't being written could be an indicator that I've done something wrong with the DMS tools though.
Could you open up that file PHTSYS\bootload.log in a text editor, and show me the content?
Once you've done that, could you delete the file and copy an existing file (say ramdisk.sig) and paste it as 'bootload.log' and try booting again.
Then take a look inside the file again, and see if the content has changed.
-
Hi, yes i shall do this. It will be tomorrow though as my friend is off today. I'm just hoping its not the Phatbox itself thats gone kaput! I love the unit, its the best thing ever!
Many thanks again, i'll post my findings tomorrow afternoon. ;) 8)
-
Hi, here is the boot log file when I first checked the DMS.
-
Ahhhhh, that might explain things - I've made a note of that :)
The file shouldn't be empty. Perhaps I've fixed in the version of the tools I'm trying to patch up now.
Hopefully we'll get a bit more once you have copied another file over....
-
Next I deleted the bootload.log file, then copied and re-named the ramdisk.sig file as bootload.log
-
OK. finally moving on... this is the re-named file as requested.
-
and finally after trying the DMS in the car here is the result.
-
Hi, just wondered... does "BOOT0-2 Failed" mean the signature is missing??
-
Run the bootcheck process again on the DMS tools now there is a valid file.
-
This is what happened when i did a boot check.
-
This was the logs when i clicked the details button...
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Index and length must refer to a location within the string.
Parameter name: length
at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
at System.String.Substring(Int32 startIndex, Int32 length)
at VorTechS.DMSTools.DMS_CommonTools.CheckDMSBootLog(Int32 DiskID, String DisplayMessages)
at StandAloneDMSHackWizard.frmStartupWizard.ToolStripButton1_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3615 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
StandAloneDMSHackWizard
Assembly Version: 2.14.0.0
Win32 Version: 0.0.2.14
CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/StandAloneDMSHackWizard.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3614 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
PhatUnzip
Assembly Version: 1.3.3.0
Win32 Version: 1.3.3
CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/PhatUnzip.DLL
----------------------------------------
VorTechS.DMSTools
Assembly Version: 2.0.0.0
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/VorTechS.DMSTools.DLL
----------------------------------------
DMS
Assembly Version: 1.0.0.1
Win32 Version: 1.0.0.1
CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/DMS.DLL
----------------------------------------
UsbEject
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/UsbEject.DLL
----------------------------------------
PhatDriveSnapshot
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/PhatDriveSnapshot.DLL
----------------------------------------
Bass.Net
Assembly Version: 2.4.4.1
Win32 Version: 2.4.4.1
CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/Bass.Net.DLL
----------------------------------------
Interop.WbemScripting
Assembly Version: 1.2.0.0
Win32 Version: 1.2.0.0
CodeBase: file:///C:/Program%20Files/PhatHack/PhatHack%20DMS%20Tools/Interop.WbemScripting.DLL
----------------------------------------
CustomMarshalers
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
-
Doh! Let me see if I can dig out the reason in source...
-
Case "0-2", "0"
knownPoint = "Verify drive signature"
knownCause = "Drive signature not present, or not valid"
Could you send me that copy of the bootfile you have please? I presume you haven't amended it from what as generated by the Phatbox?
-
This is the file which the phatbox generated..... we havn't modified this file since it was removed from the car.
-
Is that the file you meant?
-
Yup, thanks - I want see if I can work out why the application crashed reading it....
So yes, in case you haven't realised you need to get the box hacked or a new original DMS
-
Please forgive my ignorance but can you give me step by step instructions on how to hack the DMS I have using your program. We have tried various combinations but arent 100% sure what we are doing.
-
Do you have another drive to use? Because the drive you are trying to get to work won't be able to run the hack.
You have to use an original DMS that has it's drive signature intact, and the one you've been trying to get working doesn't.
-
No I dont have another drive. :'( Long shot but my laptop has the original back ups from using Music Manager, this wouldnt have the files needed on it would it? My laptop has died but the drive is oki, so if need be I can ge tthe info from it.
-
Unless you ever ran the DMS tools to do a backup, or ran through the hack process before the drive was toasted, then no.
I can put you onto a man for a new drive though ... ?
-
I never ran said program as I didnt know it exsisted til my Phatbox spat its dummy out! :D ;) Please if you could. 8) :)