Phatbox problems

[ccobka]

I've read the site did the update but i can't get my Audi radio to recognize the new drive. I've done the update 3 times. I got the message the system has been unlocked and i can the original DMS to work but not the new one. I've checked the jumper settings and that is correct too. Not sure what i'm missing please help  

[Anton]

Have you loaded the firmware onto the new DMS,  Deleted the force update/settings files?

Use Music Manager 2.3 to work with the DMS on your PC.  Media Manager Doesn't seem to work.

What does the Doctor say?

[ccobka]

thanks i will try that when i get home today. where do i find media doctor?

[sbingner]

Best place to start from then is to generally reformat the new DMS from scratch with the phatnoise repair CD or the hack CD and load the firmware from PMM.  You can then remove forceupdate and forcesettings if you so desire.

[ccobka]

ok i've tried all the suggestions above and still no luck it wont recognize my new HDD. Both lights on the phatbox stay lit and nothing happens. Phatbox keeps restarting every 10 sec. By the way the new drive I'm using is Toshiba mk6026gax.
 
Please help  

[ccobka]

I've done all i can think of and no luck, i checked hard drive manufacture site just to make sure no jumpers needed it. Any other suggestions i can try? Anyone in NY that succesfully did this please HELP!!!!

[lwen]

Hello:

I am having this problem too... After 3 tries, the same error. Followed as described:
* Boot with Linux imaged CD;
* plugged old good DMS (Toshiba MK2018GAP) into cradle when asked;
* Removed old good DMS from cradle when backup finished;
* Plugged old good DMS to Phatbox on car;
* Turned on the stereo and heard: "Your Phatnoise is hacked... more information... "
* Removed old good DMS from Phatbox;
* Dismounted the DMS and replaced with a NEW bigger HD (Toshiba 6026GAX);
* Plugged new DMS on cradle;
* All steps concluded;
* Plugged new DMS on Phatbox;
* Turned on the ignition;
** The red led is always on
* The green lled flashes for a while (about 20 times in 20 seconds)
* Then the Phatbox turns off and 2 seconds later, restarts and loops the step above (**).

Any suggestions?

Other clue: I openned the patch.log and the lasts lines are:

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!
done
: No such file or directory

: No such file or directory
/dos/backup/patch.sh: kup/p: No such file or directory


Appreciate if big boss or someone could help...

By the way, if it works (it will work!!) I would like to thank from everybody about this patch! It's simply fantastic!

Waiting for answers...

[lwen]

Just to add some information that could help:

The new DMS bootload.log has just 1 line with a lot of squares (exactly 4096 bytes) of non ASCII

Rgds,

Lee

[lwen]

Guys:

I solved the problem. Searching the forum, I found that somenone had problem similar to mine...

I checked the bootload.log file and mine was in bynary mode (4096 bytes). I just deleted this file and worked fine!

Thanks for existing this forum!

Rgds,

Lee

[ccobka]

you just deleted bootload.log from your new DMS? Does it get recreated when you inserted in the phatbox?

Thanks

[sbingner]

bootload.log is a debugging file.   It is not required on the DMS, so it would not be re-created automatically.

[analgravy2]

I'm drunk, and I think my hard drive is shot.   When we run the phathack boot disc, it says "reading drive failed!" in bold red letters.  Oh well, I'll try some other magic.  We're gonna run a diagnostics for bad sectors and try it again.  I will try my best to not use profanity.  If I do, just kick me in the "jewels".

[jeremyaudio]

Why did you guys make me an ex member?  Was it something I said?  I dont get it....

[sbingner]

I couldn't say for sure, but I suspect that somebody may have found your original name objectionable

[shack]

FYI - I was having issues with a DMS I had created as well (red and green lights would both light up and stay lit solid).

Removing the bootload.log and switching the jumper from cable select to drive 0 took care of the problem.  Not sure if it was one or the other or both that did it since I didn't try reinserting the DMS each time, but it's working now.  

Thanks!

[S80_UK]

FYI - I was having issues with a DMS I had created as well (red and green lights would both light up and stay lit solid).

Removing the bootload.log and switching the jumper from cable select to drive 0 took care of the problem.  Not sure if it was one or the other or both that did it since I didn't try reinserting the DMS each time, but it's working now.  

Thanks!

Hi - Moving the jumper would definitely have made a difference.  The Phatbox does not seem to like cable select.  The file deletion may/may not have made a difference but wouldn't do any harm.