where this my Phatverify.log in my Music Keg 710?

[galileofigaro]

Hello, iīm trying update my music keg up 120gb. but i have a problem.

I have been following the passages of the guide wiki:
I made the backup, executes dmshack, all the correct, the problem is when I put the dms in the pathbox, if it has music, reproduces music to me, if disc does not have music, begins to say to me disc 1 not found, disc 2 disc not found in loop. if I watch the bootload.log file it appears the following thing to me:

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

and in patch.log the following thing:

: 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: 0033 1a00
Unverified!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0026 1a00
Unverified!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0019 1a00
Unverified!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 000c 1a00
Unverified!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13a0    Actual: 0000 13e0
Unverified!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0000 e350    Actual: 0001 e350
Unverified!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0000 03a0    Actual: 0001 03a0
Unverified!
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: 02db eb00
Unverified!
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: 02f7 eb00
Unverified!
and I donīt have any patchverify.log file and i never listened any track silence or hack complete

 if corrupt ramdisk.sig at 10 seg to turn on the dms in my car, in the display appear eject and in bootload.log appears:

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

and I do not have the pathverify.log file either.

How can i do? thanks

P.S: My Windows this in Spanish
   
      

[VorTechS]

Re-insert the DMS into the PhatBox and try again.
You might also try disconnecting the box from the head unit - sometimes this helps kick things along.

Try, and try again - eventually the patch should apply itself.

Not sure if jud has updated the old style patches to the latest versions - although even in the beta tests there are some issues where PatchVerify is not being created.  Keep an eye on that other log file for Verified!

[judb]

if you are getting the Boot-X failed then your phatbox won't finish booting.. you need to try the ramdisk.sig corruption technique.

[VorTechS]

jud: the tools might need updating, Sam built the corruption technique into the latest version of the hack.

Having said that, I might well release my stuff in the next few days.

[judb]

the problem is people never tell us which tools version they are using so its kinda hard to just make unilateral statements about functionality. 

[sbingner]

PhatPatch v0.8 - original code by bushing, additional patches by sbingner


^^ we should add a tools version line to the logs too...

[galileofigaro]

Thanks at all, my music keg is hacked and work fine.