How to install a 160 GB HDD in the DMS?

[Devil1978]

I read now all threads completely.

I corrupt the ramdisk.sig. I loaded the file in an editor and wrote some word into the first line.
The DMS Doctor shows me a MD5-Error in this file.
Then i wiped the DMS.
After i loaded 3 Albums to the DMS and the newest Firmware.
Then i have maked a patchclean.

The NO CHANGER message comes when i drived home from work.

[TheJohnny]

I corrupt the ramdisk.sig. I loaded the file in an editor and wrote some word into the first line.

Yeah, that okay I think. Another way is to mark all and overwrite everything with a few characters.

[Devil1978]

But now the ramdisk.sig isn't corrupt.
Shall i corrupt it now an hope that my phatbox reactivate?

And shall i run the DMSHACK again now or when the phatbox is reactivated?

A forceupdate file with 0kb is in the system directory of the DMS.
Can i delete it?

[TheJohnny]

Yes, corrupt your ramdisk.sig now.

Then your Phatbox should work with your old DMS again.

From then on you can try hacking again: hackdms.bat and so on... It also didnt't work for me on the first try.

[TheJohnny]

A forceupdate file with 0kb is in the system directory of the DMS.
Can i delete it?

Yes, delete the files forceupdate and forcesettings.

[Devil1978]

Ok now i have deleted the force files.
Corrupt the ramdisk.sig. I have wrote a word at the beginning of the file.
And at least i have renamed the Plugin-Directory.

I hope its now ok.

I will try it tomorrrow.

[TheJohnny]

Okay, good luck then tomorrow!

Post your log-files: bootload.log and patch.log.

You won't find a patchverfiy.log or a patchwrite.log in the folder /log as sbingner told me. The current version of the hack does not write these files anymore.

Also you won't hear a hack-is-complete announcment since this was deactivated.

But the stereo will start to play your music when the hack is complete.

Before that your stereo will arguably display something like this:
"[...]Tr 1"
"Reading"
"NO MAGAZINE"
"[...]Tr 1"
"Reading"
"NO MAGAZINE"

[Devil1978]

Good morning.
I put the DMS in the phatbox. After 5 Minutes i have turned on the radio.
At first the phatbox shows NO CHANGER again.
At the second try the phatbox played my music.
The music runs for 30 minutes.
I think thats enough time for programming.
But he found only the first 2 albums and not the 4 albums.
Thats ok.

But it was nothing with this:
"[...]Tr 1"
"Reading"
"NO MAGAZINE"
"[...]Tr 1"
"Reading"
"NO MAGAZINE"

At home i will post here the logs.

[sbingner]

By the time the music starts the patch has completed btw... it doesn't run in the background, if you want to be safe you'd be better off turning it on and off a few times, but like i said if you hear music you should be fine.   That is of course assuming your DMS was still configured to apply the patch

[Devil1978]

Hi!
Now the radio shows this:
"[...]Tr 1"
"Reading"
"NO MAGAZINE"
"[...]Tr 1"
"Reading"
"NO MAGAZINE"

Here are the logs:

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

PATCH:

: No such file or directory
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!
PhatPatch v0.8 - 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=0001, 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




I think the phatbox is now hacked.
Is this right?

[VorTechS]

Sure is, all patched and ready to go!

[Devil1978]

  YES after 3 days its now successfull.
Thank you all for your very good help.

[TheJohnny]

Yes, as VorTechS wrote, your box is hacked.

Now use patchclean.bat on your old DMS, insert it into your box and see if it can play all albums.
If so, then your old DMS is in ready to use state again (as a fall-back option).

Follow the instructions to swap your drives and create a new DMS with newdms.bat.
Copy the content of phtsys.tar.gz onto the phtsys partition of your new DMS or take the firmware zip-files from the phathack download section. Don't forget to copy your old config folder.
If there are forceupdate or forcesettings files on your new DMS, delete them.

Then got to your car, insert the DMS into your box and start your stereo.
If you get the message "NO MAGAZINE" on your stereo, everything is allright - your new DMS is able to boot your Phatbox.

Now you can copy music to your DMS and play it in your car.

Have fun!

[Devil1978]

Now there is a message on the radio: NO CHANGER with the new DMS.

[TheJohnny]

Does your old DMS work properly in the Phatbox?

Go through the process of newdms.bat again.

I don't know if corrupting your ramdisk.sig helps you at this point. This is a question up to judb or sbingner or whoever knows.

[Devil1978]

Ok now i courrpt the ramdisk.sig on the new DMS.

Result: NO CHANGER.

I haven't tested the old DMS.

Now i ran NEWDMS again and then i downloaded the firmware files and installed the files on PHTSYS.
Then i deleted the FORCE-Files.

NO CHANGER.

There is no BOOTLOAD on the new DMS.

[sbingner]

Lol, corrupting the ramdisk.sig isn't some magic fix-it-all

The only time it helps is if the patch didn't complete, and hot stuck at/after "Patch 6" and before "Patch 7"

Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]

If you're having problems with the new DMS, you might try formatting PHTSYS and extracting fresh firmware onto it... what size is it?  If it's a 160GB you need to replace the "linux" kernel on there with a modified version

[Devil1978]

Its a 120 GB HDD.
I tried it with new.
NEWDMS, Firmwaredownload.
Not it's going without problems.

THANK YOU FOR YOUR REALLY GOOD HELP. 

[sbingner]

I think that these problems are usually a result of the phatbox bootloader being finicky about fragmentation or something... when I'm working on mine, I often have to re-format and copy my linux kernel on first...  even when the only thing I did was remove the old kernel and replace it with a new one.  Once we have a full replacement bootloader I think these problems will disappear.