News:

I have updated the spam detection on registrations, and as such I am enabling new users.  If we have spam, I will change it back to by approval.

Main Menu

HELP...!! replace disk on Audi PhatNoise

Started by Trey, December 08, 2005, 07:39:57 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Trey

First like to thank the owners and programs of this site for the bootable CD - spent 2 evenings trying upgrade the disk using ghost and other utils only to find your site that could save me that time.

I got the CD booted and followed the step-by-step instruction.  The original DMS was flashed, this was put into the car and I go the voice telling me that its been flashed/un.... successfully.  I then replaced the disk with the new one and type YES to proceed with the restore to the new disk.  at the end I rebooted the PC, and the DMS all seemed great.  put it into the car and I still am getting NO CD FOUND on the unit.

The green light is flashing away like mad, then after a few mins it stops and then starts again.  I also tried pulling the power to reset the PN and still the same issue...

I put the original DMS back in and this works

The instructions seem great, I got no error messages using the CD and seemed to go fine with the disk swap.  HELP...!!!!

One bit I seem to be missing or not sure if I should be doing is this dd command dd if=/dev/sda of=/tmp/image bs=512 count=2048.  isn't this done on the bootCD.?


Trey

Just tried the manual way which seems to work for others...  

no luck here, still not working.  I did change the disk label to sdb from sba as per instructions.

any suggestions...????????????????????????

judb

if you start over with the manual method you have to do all the steps.

it sounds like the box needed to be flashed more than once to finish.. do you know if the original DMS still works in your box?

Trey

Tried the original DMS this morning and it started working after a few minutes.?  (heart stopping moment)

I will flash the unit again, do I also need to do the bootable CD or the manual steps again...?

judb


Trey

Log DAY4:

Thanks judb

Just wiped the new disk - deleted both partitions from Windows and started the bootCD again, the patch took no time at all to do, the PN boots and then powers down and reboots.  just some info - new disk is only 40Gb which is plenty for me.

I used the bootCD procedure, have not done the manual one again.  The bootCD creates a 260ish Mb PHTSYS drive but the manual only creates a 64Mb drive...? is this enough...?

is there any log file you need from me or am I just doing this all wrong.  all Iam doing is booting the CD and following the instruction for the CD and nothing else...?

H E L P !!!!!!!!!!!!!

judb

Using the original DMS you need to make sure the patch is really running.  we need to see the bootload.log and the log files found in the backup folder from the DMS you are using to try and hack the box before using a non phatnoise drive.  I don't think your box has updated the firmware properly.

Trey

#7
From 20Gb:

bootload.log:

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


On the original DMS backup\ no log files found, I do have some txt files but their not log files.?

I do have a log dir with 5 log files.  do you want any of them.?




judb

duh yeah its in the log directory.. im a doofus today. yes whats in there.

Trey

Hope these logs help.?   (Mr Admin - you may want to delete this log info later)


patch.log >>>> (last few lines)

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!
done
: No such file or directory
: No such file or directory
/dos/backup/patch.sh: kup/p: No such file or directory





Patchverify.log >>>> (last few lines)

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!




Patchwrite.log  >>>> (last few lines)

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: 0001 03a0
Match! Programming...

judb

Okay so the 20 gig original DMS still works but you did the hack and the new drive does not work?  you've tried the manual method genesis posted as well?


Trey

YES but I can try again, if there is anything you want me to change...?   I have just seen a new post about an Audi way of doing this by amb.  does this make any sense to you, as I understand all I need to do is copy some files..?  do I not also need to put the forceupdate file in the root

judb

no the force update  is not required.  find genisis' post and follow it closely for vw/audi units.

Trey

LOG DAY5:

well this one is like that washing maching - on and on and on and on...

Nop didn't work.  [smiley=thumbdown.gif]

-  cleared the disk and did the manual way - no luck
-  cleared the disk and did the bootcd way - no luck  
-  I repeated both of the above but this time using my laptop, not PC with lots plugged in. - no luck
-  I then wanted to throw it to see how far it would fly - but didn't

-  I have done disk checks with no problems found, tried looking for a disk hard-level cloaning with no luck - not sure if this would work

is this getting to the point where we scrap the idea of an upgrade - NO - I will not give up in the name of PhatHack and I will proceed but I do need some more suggestions or help.!!!!!!!!!!!!!!!!!!

sbingner

I can try working with you on this if you like... should be around in #phathack on irc.freenode.net this evening if you want to try (afternoon in GMT-10)

Trey

Thank you for the offer, I missed it, just picked up the reply.  Saturday night - I was out. Iam here today if your online.

I noticed that when I add new songs to the new disk it runs very fast, but the old (original) disk takes ages to add songs.  the drive transfer rate are the same, so not sure why the original one is so slow (no errors and fully defraged)

sbingner

I might have time tonight, going rock climbing during the day today

Trey


Trey

sbingner thanks for the offers, time difference being abit hard, will be up late tonight if your around, let me know in advance.

I had a 6Gb disk and tried the same process just in case the new disk was naff, and had the same results either using bootCD or manual process - not working.

Trey

Took the plung and used my works laptop harddisk 60Gb - tried this using the bootcd and manual process and still I get "no cd found".  >:(    I did take a copy of the disk and got the laptop back up and running OK.  

sbingner - will be very interested in what you find out - please keep us updated   ::)

http://forum.phathack.com/cgi-bin/yabb2/YaBB.pl?num=1134537253