« previous next »
Pages: [1]   Go Down

Author Topic: "No magazine" message  (Read 16302 times)

0 Members and 3 Guests are viewing this topic.

Offline beckfield

  • A few posts under my belt.
  • *
  • Posts: 35
  • PhatHacker
"No magazine" message
« on: February 25, 2007, 01:18:23 am »
I have an '03 Jetta with a working Phatbox 20GB DMS.

I ran the DMSHack.bat from c:\dmsutils, and it appears to succeed.  Booting the PB with this, I get the "No magazine" message on the head unit.  I checked that the lights on the PB were flashing once I turned on the HU, but I think they stop once the HU decides there's no magazine.  I have left the DMS in the box for as much as 20 minutes anyway, just in case, but no joy.

I have done the following:
1.  Renamed ramdisk.sig to .bak, replaced it with a renamed copy of phatd.sig.
2.  Renamed the bootload.log.

Neither of these steps has made a change.  I looked around for other ideas.  I found the "genesis" method, but it starts out "If the box is patched..." and I don't think I've gotten that far yet.

Restoring the original ramdisk.sig and running patchclean.bat restores my DMS to normal.

I'm not sure what else to try to get the patch to actually run.

Any ideas?

Oh, my bootload.log shows the following:
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*-X: Failed

Thanks,
Ken
Logged

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: "No magazine" message
« Reply #1 on: February 25, 2007, 01:56:49 am »
So your DMS works after patchclean is run?
Logged

Offline beckfield

  • A few posts under my belt.
  • *
  • Posts: 35
  • PhatHacker
Re: "No magazine" message
« Reply #2 on: February 25, 2007, 02:30:54 am »
Quote from: sbingner on February 25, 2007, 01:56:49 am
So your DMS works after patchclean is run?

Yes, and having restored the original ramdisk.sig.
Logged

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: "No magazine" message
« Reply #3 on: February 25, 2007, 04:51:53 am »
what does the patchverify.log have in it?
Logged

Offline beckfield

  • A few posts under my belt.
  • *
  • Posts: 35
  • PhatHacker
Re: "No magazine" message
« Reply #4 on: February 25, 2007, 07:08:56 am »
Quote from: judb on February 25, 2007, 04:51:53 am
what does the patchverify.log have in it?

Oh, sorry, I meant to mention that.  The patchverify.log was not created.  That was part of the reason I'm assuming that the patch was not run.  The log folder was created, but no files in it.
Logged

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: "No magazine" message
« Reply #5 on: February 25, 2007, 02:53:27 pm »
I would extract a copy of the firmware files onto phtsys and remove the forceupdate and forcesettings files after you extract them and see if it boots.
Logged

Offline beckfield

  • A few posts under my belt.
  • *
  • Posts: 35
  • PhatHacker
Re: "No magazine" message
« Reply #6 on: February 25, 2007, 07:14:37 pm »
Quote from: judb on February 25, 2007, 02:53:27 pm
I would extract a copy of the firmware files onto phtsys and remove the forceupdate and forcesettings files after you extract them and see if it boots.

Did that, and it boots fine.  But it was booting before, as long as the patch wasn't applied.  I re-applied the patch after extracting the firmware, and I still get the "no magazine" error.

Ken
Logged

Offline beckfield

  • A few posts under my belt.
  • *
  • Posts: 35
  • PhatHacker
Re: "No magazine" message
« Reply #7 on: February 25, 2007, 09:16:30 pm »
Okay, a little more progress:

I realized that, after extracting the firmware files to the DMS, I forgot to replace ramdisk.sig with the copied/renamed phatd.sig.  So, I did the following:

1.  Extracted the firmware to the DMS.
2.  Renamed ramdisk.sig to ramdisk.bak, copied phatd.sig to my hard drive, renamed it to ramdisk.sig, and copied it back to the DMS.
3.  Deleted bootload.log (I have a previously-created bootload.bak).
4.  Put the DMS in the Phatbox and turned it on.

I again got the "no magazine" message.  In frustration, I hit the seek buttons a couple of times.  This seemed to be significant, because the track timer began rolling, and I watched it for about 10 minutes.  I turned off the stereo and went inside, leaving the DMS in the PB.  About 30 minutes later, I went back out and turned on the HU.  The track timer began counting again, picking up where I left it, at 10 minutes and change.

The lights on the PB were on as long as the HU was on.  The red was steady, and the green blipped about every 5 seconds.  Turn the HU off, and the PB lights go off.

As the Phatnoise manual says that the firmware update will continue I surmised that it had had plenty of time to complete the patch, so I turned everything off and brought the DMS back to the computer.

There is now a patch.log in the log folder, and the contents are below.  There is no patchverify.log.  Do I need to give it more time?  How long should this patch take?


PATCH.LOG
: No such file or directory
PhatPatch v0.5 - original code by bushing, additional patches by sbingner
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!
PhatPatch v0.5 - original code by bushing, additional patches by sbingner
first 2 words of flash=c102 0025
testing offsets 0x555 and 0x2aa
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0004, 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
Mismatch!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0026 1a00    Actual: 0000 1a00
Mismatch!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0019 1a00    Actual: 0000 1a00
Mismatch!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 000c 1a00    Actual: 0000 1a00
Mismatch!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13e0    Actual: 0000 13a0
Mismatch!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0001 e350    Actual: 0000 e350
Mismatch!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0001 03a0    Actual: 0000 03a0
Mismatch!
: No such file or directory
PhatPatch v0.5 - original code by bushing, additional patches by sbingner
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!
PhatPatch v0.5 - original code by bushing, additional patches by sbingner
first 2 words of flash=c102 0025
testing offsets 0x555 and 0x2aa
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0004, 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
Mismatch!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0026 1a00    Actual: 0000 1a00
Mismatch!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0019 1a00    Actual: 0000 1a00
Mismatch!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 000c 1a00    Actual: 0000 1a00
Mismatch!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13e0    Actual: 0000 13a0
Mismatch!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0001 e350    Actual: 0000 e350
Mismatch!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0001 03a0    Actual: 0000 03a0
Mismatch!
: No such file or directory
PhatPatch v0.5 - original code by bushing, additional patches by sbingner
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!
PhatPatch v0.5 - original code by bushing, additional patches by sbingner
first 2 words of flash=c102 0025
testing offsets 0x555 and 0x2aa
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0004, 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
Mismatch!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0026 1a00    Actual: 0000 1a00
Mismatch!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0019 1a00    Actual: 0000 1a00
Mismatch!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 000c 1a00    Actual: 0000 1a00
Mismatch!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13e0    Actual: 0000 13a0
Mismatch!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0001 e350    Actual: 0000 e350
Mismatch!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0001 03a0    Actual: 0000 03a0
Mismatch!
Logged

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: "No magazine" message
« Reply #8 on: February 25, 2007, 09:28:28 pm »
That says it's patched...

You should not replace the ramdisk.sig if you have a DMS that is working with the valid ramdisk.sig -- that should ONLY be done when nothing will work with a valid ramdisk.sig... but somehow it appears that your patch did apply
Logged

Offline beckfield

  • A few posts under my belt.
  • *
  • Posts: 35
  • PhatHacker
Re: "No magazine" message
« Reply #9 on: February 25, 2007, 10:32:22 pm »
Quote from: sbingner on February 25, 2007, 09:28:28 pm
That says it's patched...

You should not replace the ramdisk.sig if you have a DMS that is working with the valid ramdisk.sig -- that should ONLY be done when nothing will work with a valid ramdisk.sig... but somehow it appears that your patch did apply

Ah, alrighty then!

I'll put the correct ramdisk.sig back in place, run patchclean, and then wait for the parts for the new DMS to arrive.

Thanks for the help!

Ken
Logged

Offline beckfield

  • A few posts under my belt.
  • *
  • Posts: 35
  • PhatHacker
Re: "No magazine" message
« Reply #10 on: February 26, 2007, 01:43:06 am »
Success!  I am loading up my new 120 GB DMS as we speak.  I've already tried it in the car, and it works just great.

Thanks for all the help, and for putting this process together.

Ken
Logged
Pages: [1]   Go Up
« previous next »