Author Topic: MUSIC KEG Hack succesfull but DMS is always Eject no Music is playing HELP ME (Read 19442 times)

Danizan · « **on:** December 06, 2007, 02:27:09 pm »

Hi I'm Daniel from Germany, I have a problem. I'm not so good in hacking but your tutorial is very fine. My problem: the HDD in my Music Keg (10GB) was very slowly. Now I bought me a 20 GB HDD in Ebay.

I have installed the DMS Hack Tool v.2.10 and I hacked my original DMS. Then the Hacktool said me "Please insert in your BOX".
OK, I did it. Then my Radio said me: "Patch OK and allright [a female voice], please put out your DMS"

Then I going to the DMS Hacktool and finished it.

Now I took my new HDD 20GB and put the 20GB HDD in the DMS.

Then i started the HackTool and create a NEW DMS with Kenwood Music Keg v.13.1 Image with active Plug in and active Flash Box and inactive "NON-Hack". Them the tool create PTHSYS and PTHDTA. Now i started the Music Manager and created a new Music Album. That was no problem.

Then I went to my car and put the DMS in the Phatbox(Kenwood) but the Phatbox/Radio wrote Eject and no Music was playing.

I think the patch was OK, but the Phatbox doesn't play the new HDD.

What is the problem?

Thanks for answers

PS: Sorry for my English but my German is better

Anton · « **Reply #1 on:** December 06, 2007, 02:44:32 pm »

Please post the Log files.

you can find them on your DMS.

copy them here. it would be helpful for those who can help.

VorTechS · « **Reply #2 on:** December 06, 2007, 02:53:25 pm »

When you created the new DMS, you mention which firmware you chose (the correct one) but which tick boxes did you have checked/ticked/selected?

Danizan · « **Reply #3 on:** December 06, 2007, 03:43:32 pm »

Hello, thanks for answere:

So, the LOGFILES in PHTSYS\LOG\

-bootload.log:

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

-patch.log:

Verifying patch progress
This system is already patched

-Patchverify.log:

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!

This are the LOG-Files from the Original 10GB DMS.

When I create a new DMS with Phat Hack DMS Tool, then I select:
- Firmware: "Kenwood v.13.01",
- Reflash Box with Firmware YES SELECT
- Install SSA/VIOT YES SELECT
- Install Non-Hacked Firmware NO-SELECT

-CREATE NEW DMS - Button

This is all

VorTechS · « **Reply #4 on:** December 06, 2007, 03:54:39 pm »

Ah, your PhatBox is probably updating the firmware.
You only need to choose the option 'Reflash box with Firmware' if your PhatBox is not currently running that version of firmware.

You'll probably find giving it ten minutes or so with the ignition on will complete the update.
If you already have the correct version of firmware - remove the files 'ForceSettings' and 'ForceUpdate' from PHTSYS.

Danizan · « **Reply #5 on:** December 06, 2007, 04:09:26 pm »

At the monent I create a new DMS with:

- Firmware: "Kenwood v.13.01",
- Reflash Box with Firmware YES SELECT
- Install SSA/VIOT YES SELECT
- Install Non-Hacked Firmware NO-SELECT *EDIT: Or must I have to select YES?*Edit

Can you tell me whether a file exists, which indicates to me the status of the new DMS? A Start Log-File wath Errors stores and which I can show here in the Forum.

Thanks

VorTechS · « **Reply #6 on:** December 06, 2007, 04:22:22 pm »

Your box is performing a firmware update, I do not think there are any log files for this procedure.
Selecting the option 'Reflash box with firmware' leaves the files:

PHTSYS\forcesettings
PHTSYS\forceupdate

...on the disk and the PhatBox picks these up and then starts the firmware update procedure.

If you look at the PhatBox you should see the red light on, and the green light flashing intermittently.

Just remove the files I mentioned before (forcesettings, forceupdate) from the PHTSYS drive and the DMS should start working.

Danizan · « **Reply #7 on:** December 06, 2007, 04:35:28 pm »

Ok, I try my luck

I rise later

Danizan · « **Reply #8 on:** December 06, 2007, 05:46:45 pm »

Sorry, but it's still not.

If I use the DMS in the box load, it is only first loading (Display) and after 1 minute, the HDD briefly. The display will then Eject, and the HDD repeatedly starts new. And there is no music playing. In the radio display top left as a music source "HDD-Extern".

I removed the files -forcesettings, forceupdate from the PHTSYS drive but the DMS is not start working. It is just as above.

I seen, that the LED with the original DMS become the colour red. With the new DMS the LEDs become the colour 1 green and 1 red for 1 minute, than the box is starting new. What is the Problem???

I have patched the Box before 5 min again and the log files said that the patch was successfull. But the new dms is not running

Please help me please

VorTechS · « **Reply #9 on:** December 07, 2007, 07:36:24 am »

Did you load any music on to the new DMS?

Danizan · « **Reply #10 on:** December 07, 2007, 07:50:56 am »

Yes I did. One album wiht MusicManager but the Keg don t play it. Only Loading (1min) + Eject.

The original DMS (10GB) works without problems. Music is playing. Only the new DMS is out of function. What is the problem??

VorTechS · « **Reply #11 on:** December 07, 2007, 08:10:54 am »

No idea, please ZIP up the contents of PHTSYS and mail it to me (e-mail address is on my profile).

Danizan · « **Reply #12 on:** December 07, 2007, 08:30:00 am »

OK, in 4 hours I will be at home, then I send you the Zip from PHTSYS. I will send you the PHTSYS from the Original 10GB DMS and from the new 20GB DMS.

Yesterday I had seen that the Power Lamps on the KegBOX are red with the original DMS and 1 Lamp green and one Lamp orange with the new 20GB DMS. The original DMS is immediately playing. The original and the new DMS has the Firmware 13.01 Kenwood.
While the original DMS have the Non-Kack-Firmeware from Hack Tool and the new DMS have the Firmware with the Plugin from Hack-Tool!

It is possible to make back the Patch from the KegBOX, so that I can try again?

VorTechS · « **Reply #13 on:** December 07, 2007, 08:32:47 am »

The problem lies somewhere with the new DMS. The patch has worked and does not affect operation of the box in anyway (otherwise your original DMS would not work).

I just need to take a look at the PHTSYS files on the new DMS to see if something is screwed, and if necessary we can put the Level 10 RC logging files on.

When you get to it, can you also take a note of the blink sequence so that if we get to the bottom of the problem, we can start getting a list of what the blink sequences mean.

Danizan · « **Reply #14 on:** December 07, 2007, 08:36:56 am »

Ok i will be back at 1:00 o clock PM

Then i look to the note of the blink sequence

cu

Danizan · « **Reply #15 on:** December 07, 2007, 11:56:25 am »

EDIT: Oh your Mailadresse is wrong: vortechs@blueyonder.co.uk

?

Now I sended 2 Mails (a 6,5MB). I hope your Mailadresse is ok for 13MB

I am online for the next time. Hope for a solution.

I have to go in my car to show the blink sequence. I´ll be back

VorTechS · « **Reply #16 on:** December 07, 2007, 12:05:44 pm »

Yes, and unless it's changed the limit is 30 MB

Danizan · « **Reply #17 on:** December 07, 2007, 12:19:53 pm »

Ok in 5 min i send the mail again.

So the blink sequence:

1.- 30sec always shine the left led = green + always shine the right led = red
2.- then 1sec the left go out and the right blink red
3.- then 1 sec blink the left led = green + blink the right led = red
4.- then 1sec the left go out and the right blink red
5.- then restart the BOX and it comes again 1

VorTechS · « **Reply #18 on:** December 07, 2007, 12:53:02 pm »

Okay, I thought I'd seen this sequence somewhere before:

Quote from: sbingner on May 13, 2007, 10:11:43 pm

that's probably a 3-blink error code... followed by the flashing LED of death (really fast blinking green)

3 blinks generally indicates an IDE communication problem... you may have managed to unseat your IDE cable inside the phatbox. Open it up and make sure everything's still making good contact. check the connection of the DMS to while you're at it...

Perhaps Sam can comment on this a bit further in your case.... in the meantime when I get your files I'll just check them out to be sure I'm happy the tools have done what they are supposed to have done.

VorTechS · « **Reply #19 on:** December 07, 2007, 12:55:01 pm »

Oh also, something that seems to be commonly popping up, make sure you've pushed the DMS cartridge all the way in to the box. I think the newer cartridges require you to put a use a little more force when connecting it to the PhatBox.

News:

Author Topic: MUSIC KEG Hack succesfull but DMS is always Eject no Music is playing HELP ME (Read 19442 times)