Failed hack (linux Disk) - Fixed.

[ajsl001]

Hi there,

I'm having some problems with hacking my Phatbox.

I used the Linux ISO from http://wiki.phathack.com/DMS_Hack_and_Repair_CD on my 20GB DMS and patched ok according to the PatchVerify.log (See below) on my orginal DMS. But after going through the process and building a new 80GB DMS I get the "No CD" message on the headunit with the "new" DMS.

Any ideas?


bootload.log

Code: [Select]

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

PatchVerify.log

Code: [Select]

Starting Patch Process
PhatPatch v0.4 - 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.4 - 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!


[judb]

is the bootload.log here from the new or the original DMS?  the patch log makes it seem like the box is patched properly.

do you have a plugin folder on the new dms?  try renaming it to plugins.bak

[ajsl001]

is the bootload.log here from the new or the original DMS?  the patch log makes it seem like the box is patched properly.

Original DMS.  From memory the "new" DMS had a blank bootload.log

do you have a plugin folder on the new dms?  try renaming it to plugins.bak

I haven't installed any plugins that I know of. I'll check when I get home.

[judb]

make a copy of properties.xml but call it bootload.log
try the drive again and then look in bootload.log

it should have something written to it. 

do the same on the original dms if it doesn't work either (so the bootload log will get updated or not and we'll know where it's failing.)

Post the logs and we'll see whats up.

[ajsl001]

Created a new bootload.log on the new DMS by copying (and renaming) properties.xml, inserted that DMS into the phatbox.

There's a delay then "NO CD" is displayed. The bootload.log has nothing in it (i.e. there's nothing in it bar the original contents of the properties.xml file.

Thanks for the help BTW .

I'll try it again with the original DMS

[ajsl001]

Ok I'm now the happy owner of a working hacked 80G DMS

The solution in the end I got through reading some of judb's other posts was as mundane as it was effective.. I formatted PHTSYS, started with a fresh set of firmware (removed the forceupdate file) and I was up and running.

Thanks to all who put the effort in to get this hack going in the 1st place

Cheers.

[judb]

I need to find out what file is hosing us up that a format fixes..  I'm looking into it.. I ran into that problem building a 160 gig DMS last night in fact.

[sbingner]

What he describe is what I believe to be a problem with phatnoise's bootloader... depending on how or where the "linux" and "ramdisk" files are written to the drive sometimes it refuses to boot.  Putting them down first after a clean format always seems to fix it... so that would be why formatting and using pmm to apply the firmware would fix it.