Phatbox fails to boot from new dms

[bpahlke]

Hello,

I hope somebody can help me.

I've recently bought a used PhatBox, she is working properly with the DMS that came along.

Now I've decide to replace the hardrive with a CF card (32GB; using an IDE adapter), created a new DMS using the DMS Tools (V2.14).
Setup it up with the same firmware (Volkswagen V6.00), and tried it in my Phatbox, without luck.
The box starts, and after a while the green led starts flashing quickly and never changes. I can't tell exactly if the red led is on.

If I compare the two disks, one thing catches my eye.
The phatsys of the original DMS is 260MB big, the new one only 63MB?

The bootload.log file is not modified after I pulled it out, sitting in the Phatbox for about an hour.

(I've also tried the same procedure with an 30GB 2,5" HDD, same result as with the CF card)


Does somebody now what's going wrong, or if I have done something wrong?

Thank you!
Benni

(I've tried some tips from the forum already, but they didn't work out, too.)

[bpahlke]

Does no one have a clue or an idea?

[S80_UK]

Hi Benni,

Three possibilities spring to mind...

1) Is your Phatbox hacked to work with any disk drive?  If not then you need to do that first using the hack tools with your original DMS.

2) It is possible that the Phatbox firmware is using a disk access method (different PIO or DMA access mode) that is not supported by your Compact Flash card or by the adaptor.

3) Is the CF card / adaptor combination set to operate in Master, Slave or Cable Select mode?  If I recall, I think it has to be in Master mode.

Even then it is possible that it won't work - I am not sure if it has ever been done.

Oh - and don't worry about the difference in size of the PHTSYS partition - 63MB is more than enough.

Regards,

Les.

[VorTechS]

As S80_UK suggests, 'we' have tried to get CF cards to boot from the PhatBox and haven't had any success.

PhatNoise perhaps expected to use more of the original space for the system partition over time.  Therefore, when designing the tools it seemed appropriate to stop wasting that space to free up a bit more for your PHTDTA/Music!

[bpahlke]

Thank you for your replies!

1.) I patched my PhatBox with my original DMS
The text-to-speech lady told me that my box is gonna be patched
(told me the patch starts, it skips some tracks, then announced the playing track followed by the track)
after that the dmstools told me that my box is patched.

2.) I then created a new DMS (with my 2,5" 30GB HDD)
Selected "VW V6.0" (No "Non-hacked FW"; No "Reflash firmware") [FW V6.0 was on the original DMS]

3.) Created the bootlog.txt

4.) Put some music on it with the phatnoise mm, and gave it another turn.

=>
It doesn't boot nor is the bootlog touched.

The led order on the phatbox (in order of appearance):
-Solid Green
-Solid Red
-Solid Green / Red
-Slow Green [Blinking; 1s delay]
-Fast Green [Blinking; instant on/off]

Do you know the meaning of the led signals?
Is my box really patched? (No "Your box is patched"-text)
Or do you need any more information from me?


Every time I put my original dms back in, my cd-"changer" is available.
(I've put the "CF-card project" on hold, 'til the hdd works. )

[bpahlke]

Hello,

is the PhatBox firmware version information correct? (Changer key 6, Track 3 [or something near that])

Because this differs, to what firmware is on my DMS.
I can't recall the correct version number, but it was lower than the DMS-V6.0.
I'll write it down tomorrow.

Or should I rerun the patch? Is there a chance that the patch wasn't successful?


Thank you!
Benni

[S80_UK]

The firmware version number has no direct relationship to the patch.

Also, the number reported is the number as contained in the phatbox.ini file in the system folder on the DMS and is not the same as the version number used outside the software to distiguish between different versions.

Example - my Volvo 4.01 firmware reports version 3800 when I access the menus and that is the same as in the phatbox.ini file.

Les.

[VorTechS]

Have you tried leaving the phatbox for a while?  I wonder if it's doing a firmware update and you're not being patient enough (15 minutes)....

[bpahlke]

You mean create a new DMS and then leave it in the phatbox for 15 or more minutes?

If I'm going to patch the firmware should I turn on the ignition? Or just disconnect the phatbox, insert the dms and then reconnect the phatbox?
(My vw supplies the phatbox with power, even if the car isn't running.)

And can you tell me what should happen? Like the LEDs, or any sign that indicates the end of the patch progress.


Thank you!
Benni

[VorTechS]

I have to admit, I've never actually sat and watched a box do a firmware update!

Update the firmware on the DMS to whichever version, leaving the options 'Reflash Box' checked, and by the sound of it, uncheck the 'Install non-hacked firmware'.  Put a single playlist on the DMS, deleting anything the DMS tools creates using PhatNoise MM or your chosen software, and then go stick it in the box.

Wait 15 minutes but keep an eye on tose lights, if in the first 30-40 seconds you see BOTH lights go off, and this repeats itself - then the box isn't booting.  Otheriwse it's updating firmware.  You should be able to the update with the ignition set to 'accessories'

[bpahlke]

Hi,

a small update from my phatbox.

I patched my box, without an another attempt to hack it.
The patch went through.
PhatMusic Manager says my box has VW V7.02, and it plays the music just fine.

But the patch progress it self is a bit odd.
1.) DMS Hack Tool says that it failed to verify my hard drive as an original one
2.) The patch progress on the PhatBox doesn't end properly (No end-announcement, just starts playing music), if I skip a track afterwards, my head unit can not find the PhatBox ("NO CD CHANGER", only unpluging the box brings it back to life)

I've attached a directory listing of my PhatSys volume.
Maybe you see something strange on my phat-dms, which doesn't belong there.

[jesus marion joseph]

I was having a similar issue. See this thread:  http://forum.phathack.com/index.php/topic,2721.0.html

[VorTechS]

Unfortunately the DMS tools as they are, does not correctly generate the 'disc indexes' in the data files... and I am no longer maintaining the code the DMS tools uses to generate these files.  (PhatHack Media Manager uses a different code base, which is reliant on a database).  This is probably why your skipping causes problems. 

To repair this problem, drop back into PhatNoise Media/Music Manager, delete the 'hack' playlist, save/eject and everything should be back to normal.

[bpahlke]

I'm goping to test my "new" test-dms soon.
Unfortunately my cars in for service (broken front suspension spring), so tomorrow evening I'm going to give it another spin!

Thank you for your answers!

[bpahlke]

Hi,

it's me. Again.

I've repatched my box, and now something new happens!
My box is constantly rebooting.

but I've searched my "original" dms and found the "log". With two files in it.

• patch.log
• PatchVerify.log

Is this from the Phathack DMS Tools?
The content of the patch.log:

Code Select Expand


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!


Is this helpful in anyway?
Does it help to solve my problem?

[VorTechS]

You have a hacked box.  Congratulations!

So, load up your new DMS with the appropriate firmware files and use your favourite software to load some music on it and see how things go!

[bpahlke]

I've repatched my box, and now something new happens!
My box is constantly rebooting.

Unfortunaly not.
My box goes does the following: red, green, green-slow-flashing, green-fast-flashing, off. This process repeats until I turn my head-unit off.

I'm trying to duplicate my "original" dms, with a hardware duplicator.

[VorTechS]

There's no point in duplicating the original DMS really.  Use the DMS tools 'Boot Check' function that will give us a first clue as to whether the box is trying to boot.

Out of interest, what new drive is it you have in the DMS?

[bpahlke]

Well no luck, the bootload.log is left unmodified.

So far I've tried a 2,5" 30GB IBM and my 32GB CF-card in a ide-adapter.
I'm going to try a brand new 120GB WDC today/tomorrow.

[VorTechS]

The box isn't even attempting to boot.  Try re-seating the connector, there's something odd going on with it as that's a similar problem I'm having with another members 120GB disk.  Replacing the connector with one of my own seems to have gotten further.