Patch Failed?

[kmh]

I'm attempting to patch my BMW Phatbox (firmware 9.0).  I didn't hear the patch complete audio, so I tried again.  Again no patch complete audio message and the log\patch.log contains the following:

: No such file or directory
PhatPatch v0.7 - original code by bushing, additional patches by sbingner
Verifying:
PhatPatch v0.7 - 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=0020, device id=0057
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: 000c 1a00
Match! Programming...
Segmentation fault

Did it work or do I have a problem?
Thanks!

[judb]

The segfault issue is a common one.  if you rename the log file it will make a new one, if it doesn't make a new one chances are the box isnt booting properly until you corrupt the ramdisk.sig.. as thats usually where the process fails

[kmh]

I HOPE MY PHATBOX IS NOT A BRICK NOW!!

Thanks for the quick reply!  I'm not quite sure what you meant by: "...if it doesn't make a new one chances are the box isnt booting properly until you corrupt the ramdisk.sig..."  Here's what I did:

I reset the DMS and the Phatbox booted normally.  Then I applied the hack to the DMS, ran it in the Phatbox again, did not hear the complete message and received this log\patch.log:


: No such file or directory
PhatPatch v0.7 - original code by bushing, additional patches by sbingner
Verifying:
PhatPatch v0.7 - 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=0020, device id=0057
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: 0001 e350
Match! Programming...
Segmentation fault

So it appears I got father, but not complete.

HOWEVER, I am now not able to get the Phatbox to boot normally.  I've tried patchclean and coping files from the orginial PHTSYS backup and so far I can't get the Phatbot to boot.

I noticed the current version of bootload.log shows:

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


Any ideas??

[sbingner]

No, it's not bricked.  Do a search and you will find answer in a many places.

[judb]

yeah just search for corrupt ramdisk.sig and you'll find instructions.. you should be able to run the hack one last time and be good to go after you do that.

[kmh]

I believe all is well now.  Thanks to both of you for your help and an awesome piece of hacking.  It appears all 9 patches have been successfully installed.  My original 40GB DMS is been restored to clean (pre-hack) state and everything is working.

I had spent a day and half searching and reading all of threads.  It's funny how things make more sense after you've already gone through it yourself.  Corrupting the ramdisk.sig file did the trick (as I now understand it did for many others in the past :-)).

Now I await the arrival of my NBHD 120G|TOSH 5K ATA6 MK1234GAX % - OEM (Qty=1, Price=$82.99) from Newegg!!

Cheers!!