Patch proces on box not complete

[toophat]

Hello All, today I started after much reading on this wonderfull board with the patch on my Phatnoise Unit in my car (a BMW 530i E39 from 2001). The DMS was original from a Volvo but I put succesfully new Firmware on it with the new Phathack DMS tools v. 2.10. And after it worked OK in the car.
After that I put the patch on the DMS and also this went well. But... when I put the DMS in my car the first 5 patches seems OK but patch 6 'till 9 failed 

After that I disconnected the Box in the car as described in several threads and connected it again, but now the headunit in the car give <CD CHECK>. In this situation the red LED is allways on and the green LED goes several times on and off (in a 1 sec. sequence), and between these several times the green LED is a few times ON for 5 seconds. Also sometimes the HD inside the DMS stopped turning and then spinning up again.
Difficult to describe but here is the sequence from the green LED (red is allways ON);

ON 5s, blink 5x, ON 5s, blink 5x, blink 11x, blink 11x,
ON 5s, blink 5x, ON 5s, blink 5x, blink 11x, blink 11x,
and again and again


For extra information and as is adviced I pasted the logfile.txt and the screen information about the Patches.

===============================================================
08.69:phatd:main      : Media Daemon (phatd) $Revision: 1.217 $
09.13:phatd:main      : Debug level = 10
Selected profile is: Default
09.48:phatd:main      : Using /dos/exec.ini for exec.ini
09.61:phatd:fork_if_in: Spawning /dos/51d
09.62:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
10.37:51d  :main      :
--- 51d (Mar  3 2004 18:49:12) --- $Revision: 1.205 $

10.38:51d  :main      : Debug level = 10
10.72:phatd:check_inst: Added PWid 2, value 0
10.72:phatd:main      : Entering Main loop
10.73:phatd:main      : Socket 2 has MSG_ID 2
11.06:51d  :openserpor: /dev/ttyS1 open fd=11
11.06:51d  :main      : Old ISP timeout value set to 50000 uSec
11.06:51d  :main      : Rollins timeout value set to 100000 uSec
11.06:51d  :test_uC_ve:        f9 (249) ------------>
11.07:51d  :test_uC_ve:              <============ 53 (83)
11.07:51d  :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
11.07:51d  :parse_pac : opening /dos/firmware.pac
11.07:51d  :parse_pac : PAC file summary
11.07:51d  :parse_pac :     firmware name h: 22
11.07:51d  :parse_pac :     firmware name l: 00
11.07:51d  :parse_pac :     firmware ver   : 08
11.07:51d  :parse_pac :     firmware base h: 0f
11.07:51d  :parse_pac :     firmware base l: fd
11.07:51d  :parse_pac :     firmware size h: 15
11.07:51d  :parse_pac :     firmware size l: 60
11.08:51d  :send_arm_s: firmware_modification=4
11.17:phatd:check_inst: Added PWid 2, value 0
11.17:51d  :rw_packet : Buffering 10 at 0
11.18:51d  :rw_packet : ########################################################
11.18:51d  :rw_packet :        10 (16) ------------->
11.18:51d  :rw_packet : Expecting HACK
11.19:51d  :rw_packet :              <============ ac (172)
11.19:51d  :rw_packet :        08 ( ------------->
11.19:51d  :rw_packet : Expecting BACK
11.20:51d  :rw_packet :              <============ bd (189)
11.20:51d  :rw_packet :        22 (34) ------------->
11.20:51d  :rw_packet : Expecting BACK
11.21:51d  :rw_packet :              <============ bd (189)
11.21:51d  :rw_packet :        00 (0) ------------->
11.21:51d  :rw_packet : Expecting BACK
11.22:51d  :rw_packet :              <============ bd (189)
11.22:51d  :rw_packet :        00 (0) ------------->
11.22:51d  :rw_packet : Expecting BACK
11.23:51d  :rw_packet :              <============ bd (189)
11.23:51d  :rw_packet :        04 (4) ------------->
11.23:51d  :rw_packet : Expecting BACK
11.24:51d  :rw_packet :              <============ bd (189)
11.24:51d  :rw_packet :        07 (7) ------------->
11.24:51d  :rw_packet : Expecting BACK
11.25:51d  :rw_packet :              <============ bd (189)
11.25:51d  :rw_packet :        bb (187) ------------->
11.25:51d  :rw_packet : Expecting PACK
11.26:51d  :rw_packet :              <============ ce (206)
11.26:51d  :rw_packet :              <============ 11 (17)
11.26:51d  :rw_packet :              <============ 00 (0)
11.26:51d  :rw_packet :              <============ 0e (14)
11.26:51d  :rw_packet :              <============ 13 (19)
11.26:51d  :rw_packet :              <============ 02 (2)
11.26:51d  :rw_packet :              <============ cc (204)
11.26:51d  :rw_packet :              <============ 14 (20)
11.26:51d  :rw_packet :              <============ 22 (34)
11.26:51d  :rw_packet :              <============ 00 (0)
11.26:51d  :rw_packet :              <============ 08 (
11.26:51d  :rw_packet :              <============ 00 (0)
11.26:51d  :rw_packet :              <============ 00 (0)
11.26:51d  :rw_packet :              <============ 00 (0)
11.27:51d  :rw_packet :              <============ c2 (194)
11.27:51d  :rw_packet : ########################################################
11.27:51d  :rw_packet :        ce (206) ------------->
11.27:51d  :rw_packet : ********************************************************
11.27:51d  :processpac: Got Session: mode 0, run type 14, lot 13 02
11.27:phatd:log_bc    : CPUid info:
Unique ID: 0x27e41a90
Random ID: 0x27e41a901102ee7813c39da6035f8175
CPU: EP73xx, ver 0x02
Lot Code: 0x1302
11.31:51d  :processpac: Initializing 1.2 DAC
11.31:51d  :processpac: SSA head unit
11.32:51d  :processpac: Extra help enabled
11.32:51d  :processpac: Force magazine random
11.41:51d  :processpac: Non-text head unit - will not load text
11.50:51d  :rw_packet :        ce (206) ------------->
11.50:51d  :rw_packet : ********************************************************
11.51:51d  :processpac: Got uC ID
12.24:51d  :rw_packet : ********************************************************
12.24:51d  :rw_packet :              <============ 21 (33)
12.24:51d  :rw_packet :              <============ df (223)
12.24:51d  :rw_packet :        ce (206) ------------->
12.24:51d  :rw_packet : ********************************************************
12.24:51d  :processpac: Got Query total disc
12.24:51d  :rw_packet : Buffering 7d at 0
12.25:51d  :rw_packet : ########################################################
12.25:51d  :rw_packet :        7d (125) ------------->
12.25:51d  :rw_packet : Expecting HACK
12.26:51d  :rw_packet :              <============ ac (172)
12.26:51d  :rw_packet :        00 (0) ------------->
12.26:51d  :rw_packet : Expecting BACK
12.27:51d  :rw_packet :              <============ bd (189)
12.27:51d  :rw_packet :        01 (1) ------------->
12.27:51d  :rw_packet : Expecting BACK
12.28:51d  :rw_packet :              <============ bd (189)
12.28:51d  :rw_packet :        82 (130) ------------->
12.28:51d  :rw_packet : Expecting PACK
12.29:51d  :rw_packet :              <============ ce (206)
12.29:51d  :rw_packet :              <============ 20 (32)
12.29:51d  :rw_packet :              <============ 00 (0)
12.29:51d  :rw_packet :              <============ 01 (1)
12.29:51d  :rw_packet :              <============ df (223)
12.29:51d  :rw_packet : ########################################################
12.29:51d  :rw_packet :        ce (206) ------------->
12.29:51d  :rw_packet : ********************************************************
12.29:51d  :processpac: Got Query total tracks 1
12.29:51d  :rw_packet : Buffering 7c at 0
12.29:51d  :rw_packet : ########################################################
12.30:51d  :rw_packet :        7c (124) ------------->
12.30:51d  :rw_packet : Expecting HACK
12.31:51d  :rw_packet :              <============ ac (172)
12.31:51d  :rw_packet :        00 (0) ------------->
12.31:51d  :rw_packet : Expecting BACK
12.32:51d  :rw_packet :              <============ bd (189)
12.32:51d  :rw_packet :        58 (88) ------------->
12.32:51d  :rw_packet : Expecting BACK
12.33:51d  :rw_packet :              <============ bd (189)
12.33:51d  :rw_packet :        00 (0) ------------->
12.33:51d  :rw_packet : Expecting BACK
12.34:51d  :rw_packet :              <============ bd (189)
12.34:51d  :rw_packet :        01 (1) ------------->
12.34:51d  :rw_packet : Expecting BACK
12.35:51d  :rw_packet :              <============ bd (189)
12.35:51d  :rw_packet :        2b (43) ------------->
12.35:51d  :rw_packet : Expecting PACK
12.36:51d  :rw_packet :              <============ ce (206)
12.36:51d  :rw_packet : ########################################################
17.36:51d  :main      : Auto PONG
17.36:51d  :rw_packet : Buffering 70 at 0
17.36:51d  :rw_packet : ########################################################
17.36:51d  :rw_packet :        70 (112) ------------->
17.36:51d  :rw_packet : Expecting HACK
17.37:51d  :rw_packet :              <============ ac (172)
17.37:51d  :rw_packet :        90 (144) ------------->
17.37:51d  :rw_packet : Expecting PACK
17.38:51d  :rw_packet :              <============ ce (206)
17.38:51d  :rw_packet : ########################################################
22.38:51d  :main      : Auto PONG
22.38:51d  :rw_packet : Buffering 70 at 0
22.38:51d  :rw_packet : ########################################################
22.38:51d  :rw_packet :        70 (112) ------------->
22.38:51d  :rw_packet : Expecting HACK
22.39:51d  :rw_packet :              <============ ac (172)
22.39:51d  :rw_packet :        90 (144) ------------->
22.39:51d  :rw_packet : Expecting PACK
22.40:51d  :rw_packet :              <============ ce (206)
22.40:51d  :rw_packet : ########################################################
27.40:51d  :main      : Auto PONG
27.40:51d  :rw_packet : Buffering 70 at 0
27.40:51d  :rw_packet : ########################################################
27.40:51d  :rw_packet :        70 (112) ------------->
27.40:51d  :rw_packet : Expecting HACK
27.41:51d  :rw_packet :              <============ ac (172)
27.41:51d  :rw_packet :        90 (144) ------------->
27.41:51d  :rw_packet : Expecting PACK
27.42:51d  :rw_packet :              <============ ce (206)
27.42:51d  :rw_packet : ########################################################
32.42:51d  :main      : Auto PONG
32.42:51d  :rw_packet : Buffering 70 at 0
32.42:51d  :rw_packet : ########################################################
32.42:51d  :rw_packet :        70 (112) ------------->
32.42:51d  :rw_packet : Expecting HACK
32.43:51d  :rw_packet :              <============ ac (172)
32.43:51d  :rw_packet :        90 (144) ------------->
32.43:51d  :rw_packet : Expecting PACK
32.44:51d  :rw_packet :              <============ ce (206)
32.44:51d  :rw_packet : ########################################################
37.44:51d  :main      : Auto PONG
37.44:51d  :rw_packet : Buffering 70 at 0
37.44:51d  :rw_packet : ########################################################
37.44:51d  :rw_packet :        70 (112) ------------->
37.44:51d  :rw_packet : Expecting HACK
37.45:51d  :rw_packet :              <============ ac (172)
37.45:51d  :rw_packet :        90 (144) ------------->
37.45:51d  :rw_packet : Expecting PACK
37.46:51d  :rw_packet :              <============ ce (206)
37.46:51d  :rw_packet : ########################################################
42.46:51d  :main      : Auto PONG
42.46:51d  :rw_packet : Buffering 70 at 0
42.46:51d  :rw_packet : ########################################################
42.46:51d  :rw_packet :        70 (112) ------------->
42.46:51d  :rw_packet : Expecting HACK
42.47:51d  :rw_packet :              <============ ac (172)
42.47:51d  :rw_packet :        90 (144) ------------->
42.47:51d  :rw_packet : Expecting PACK
42.48:51d  :rw_packet :              <============ ce (206)
42.48:51d  :rw_packet : ########################################################
47.48:51d  :main      : Auto PONG
47.48:51d  :rw_packet : Buffering 70 at 0
47.48:51d  :rw_packet : ########################################################
47.48:51d  :rw_packet :        70 (112) ------------->
47.48:51d  :rw_packet : Expecting HACK
47.49:51d  :rw_packet :              <============ ac (172)
47.49:51d  :rw_packet :        90 (144) ------------->
47.49:51d  :rw_packet : Expecting PACK
47.50:51d  :rw_packet :              <============ ce (206)
47.50:51d  :rw_packet : ########################################################
52.50:51d  :main      : Auto PONG
52.50:51d  :rw_packet : Buffering 70 at 0
52.50:51d  :rw_packet : ########################################################
52.50:51d  :rw_packet :        70 (112) ------------->
52.50:51d  :rw_packet : Expecting HACK
52.51:51d  :rw_packet :              <============ ac (172)
52.51:51d  :rw_packet :        90 (144) ------------->
52.51:51d  :rw_packet : Expecting PACK
52.52:51d  :rw_packet :              <============ ce (206)
52.52:51d  :rw_packet : ########################################################
56.87:51d  :rw_packet : ********************************************************
56.87:51d  :rw_packet :              <============ e2 (226)
56.87:51d  :rw_packet :              <============ 01 (1)
56.87:51d  :rw_packet :              <============ 09 (9)
56.87:51d  :rw_packet :              <============ 09 (9)
56.87:51d  :rw_packet :              <============ bd (189)
56.87:51d  :rw_packet :              <============ 00 (0)
56.87:51d  :rw_packet :              <============ 00 (0)
56.87:51d  :rw_packet :              <============ 00 (0)
56.87:51d  :rw_packet :              <============ 00 (0)
56.87:51d  :rw_packet :              <============ 4e (78)
56.87:51d  :rw_packet :        ce (206) ------------->
56.87:51d  :rw_packet : ********************************************************
56.88:51d  :processpac: uC DEBUG: 01 09 09 bd 00 00 00 00
57.36:51d  :rw_packet : ********************************************************
57.36:51d  :rw_packet :              <============ e2 (226)
57.36:51d  :rw_packet :              <============ 01 (1)
57.36:51d  :rw_packet :              <============ 01 (1)
57.36:51d  :rw_packet :              <============ 01 (1)
57.36:51d  :rw_packet :              <============ 00 (0)
57.36:51d  :rw_packet :              <============ 01 (1)
57.36:51d  :rw_packet :              <============ 01 (1)
57.36:51d  :rw_packet :              <============ bd (189)
57.36:51d  :rw_packet :              <============ 00 (0)
57.36:51d  :rw_packet :              <============ 5c (92)
57.36:51d  :rw_packet :        ce (206) ------------->
57.36:51d  :rw_packet : ********************************************************
57.37:51d  :processpac: uC DEBUG: 01 01 01 00 01 01 bd 00
57.64:51d  :rw_packet : ********************************************************
57.64:51d  :rw_packet :              <============ e2 (226)
57.64:51d  :rw_packet :              <============ 01 (1)
57.64:51d  :rw_packet :              <============ 01 (1)
57.64:51d  :rw_packet :              <============ 01 (1)
57.64:51d  :rw_packet :              <============ 00 (0)
57.64:51d  :rw_packet :              <============ 01 (1)
57.64:51d  :rw_packet :              <============ 01 (1)
57.64:51d  :rw_packet :              <============ bd (189)
57.64:51d  :rw_packet :              <============ 00 (0)
57.64:51d  :rw_packet :              <============ 5c (92)
57.64:51d  :rw_packet :        ce (206) ------------->
57.64:51d  :rw_packet : ********************************************************
57.64:51d  :processpac: uC DEBUG: 01 01 01 00 01 01 bd 00
58.65:51d  :rw_packet : ********************************************************
58.65:51d  :rw_packet :              <============ 30 (48)
58.65:51d  :rw_packet :              <============ 00 (0)
58.65:51d  :rw_packet :              <============ 01 (1)
58.65:51d  :rw_packet :              <============ 00 (0)
58.65:51d  :rw_packet :              <============ 01 (1)
58.65:51d  :rw_packet :              <============ 00 (0)
58.65:51d  :rw_packet :              <============ 00 (0)
58.65:51d  :rw_packet :              <============ ce (206)
58.65:51d  :rw_packet :        ce (206) ------------->
58.65:51d  :rw_packet : ********************************************************
58.65:51d  :processpac: Got Play 1/1/0
59.13:phatd:start_mp3p: FILE: /dos/PhatHack.hack
59.14:phatd:start_mp3p: Authenticating /dos/patcher
59.25:phatd:start_mp3p: Exec /dos/patcher /dos/PhatHack.hack 0 (null)
59.25:phatd:start_mp3p: player started pid 14
59.25:phatd:main      : Queueing PLAYd1t0s0 for end of startfile
59.65:51d  :rw_packet : ********************************************************
59.65:51d  :rw_packet :              <============ 66 (102)
59.65:51d  :rw_packet :              <============ 9a (154)
59.65:51d  :rw_packet :        ce (206) ------------->
59.65:51d  :rw_packet : ********************************************************
59.65:51d  :processpac: Got PING
59.65:51d  :rw_packet : Buffering 70 at 0
59.65:51d  :rw_packet : ########################################################
59.65:51d  :rw_packet :        70 (112) ------------->
59.65:51d  :rw_packet : Expecting HACK
59.66:51d  :rw_packet :              <============ ac (172)
59.66:51d  :rw_packet :        90 (144) ------------->
59.66:51d  :rw_packet : Expecting PACK
59.67:51d  :rw_packet :              <============ ce (206)
59.67:51d  :rw_packet : ########################################################
08.73:phatd:main      : Media Daemon (phatd) $Revision: 1.217 $
08.74:phatd:main      : Debug level = 10
Selected profile is: Default
09.10:phatd:main      : Using /dos/exec.ini for exec.ini
09.23:phatd:fork_if_in: Spawning /dos/51d
09.24:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
10.01:51d  :main      :
--- 51d (Mar  3 2004 18:49:12) --- $Revision: 1.205 $

10.83:51d  :main      : Debug level = 10
10.53:phatd:check_inst: Added PWid 2, value 0
10.84:phatd:main      : Entering Main loop
10.85:phatd:main      : Socket 2 has MSG_ID 2
11.17:51d  :openserpor: /dev/ttyS1 open fd=11
11.17:51d  :main      : Old ISP timeout value set to 50000 uSec
11.17:51d  :main      : Rollins timeout value set to 100000 uSec
11.17:51d  :test_uC_ve:        f9 (249) ------------>
11.18:51d  :test_uC_ve:              <============ 53 (83)
11.18:51d  :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
11.18:51d  :parse_pac : opening /dos/firmware.pac
11.18:51d  :parse_pac : PAC file summary
11.18:51d  :parse_pac :     firmware name h: 22
11.18:51d  :parse_pac :     firmware name l: 00
11.18:51d  :parse_pac :     firmware ver   : 08
11.18:51d  :parse_pac :     firmware base h: 0f
11.18:51d  :parse_pac :     firmware base l: fd
11.18:51d  :parse_pac :     firmware size h: 15
11.18:51d  :parse_pac :     firmware size l: 60
11.19:51d  :send_arm_s: firmware_modification=4
11.28:phatd:check_inst: Added PWid 2, value 0
11.29:51d  :rw_packet : Buffering 10 at 0
11.29:51d  :rw_packet : ########################################################
11.29:51d  :rw_packet :        10 (16) ------------->
11.29:51d  :rw_packet : Expecting HACK
11.30:51d  :rw_packet :              <============ ac (172)
11.30:51d  :rw_packet :        08 ( ------------->
11.30:51d  :rw_packet : Expecting BACK
11.31:51d  :rw_packet :              <============ bd (189)
11.31:51d  :rw_packet :        22 (34) ------------->
11.31:51d  :rw_packet : Expecting BACK
11.32:51d  :rw_packet :              <============ bd (189)
11.32:51d  :rw_packet :        00 (0) ------------->
11.32:51d  :rw_packet : Expecting BACK
11.33:51d  :rw_packet :              <============ bd (189)
11.33:51d  :rw_packet :        00 (0) ------------->
11.33:51d  :rw_packet : Expecting BACK
11.34:51d  :rw_packet :              <============ bd (189)
11.34:51d  :rw_packet :        04 (4) ------------->
11.34:51d  :rw_packet : Expecting BACK
11.35:51d  :rw_packet :              <============ bd (189)
11.35:51d  :rw_packet :        07 (7) ------------->
11.35:51d  :rw_packet : Expecting BACK
11.36:51d  :rw_packet :              <============ bd (189)
11.36:51d  :rw_packet :        bb (187) ------------->
11.36:51d  :rw_packet : Expecting PACK
11.37:51d  :rw_packet :              <============ ce (206)
11.37:51d  :rw_packet :              <============ 11 (17)
11.37:51d  :rw_packet :              <============ 00 (0)
11.37:51d  :rw_packet :              <============ 0e (14)
11.37:51d  :rw_packet :              <============ 13 (19)
11.37:51d  :rw_packet :              <============ 02 (2)
11.37:51d  :rw_packet :              <============ cc (204)
11.37:51d  :rw_packet :              <============ 14 (20)
11.37:51d  :rw_packet :              <============ 22 (34)
11.37:51d  :rw_packet :              <============ 00 (0)
11.37:51d  :rw_packet :              <============ 08 (
11.37:51d  :rw_packet :              <============ 00 (0)
11.37:51d  :rw_packet :              <============ 00 (0)
11.37:51d  :rw_packet :              <============ 00 (0)
11.38:51d  :rw_packet :              <============ c2 (194)
11.38:51d  :rw_packet : ########################################################
11.38:51d  :rw_packet :        ce (206) ------------->
11.38:51d  :rw_packet : ********************************************************
11.38:51d  :processpac: Got Session: mode 0, run type 14, lot 13 02
11.38:phatd:log_bc    : CPUid info:
Unique ID: 0x27e41a90
Random ID: 0x27e41a901102ee7813c39da6035f8175
CPU: EP73xx, ver 0x02
Lot Code: 0x1302
11.42:51d  :processpac: Initializing 1.2 DAC
11.42:51d  :processpac: SSA head unit
11.42:51d  :processpac: Extra help enabled
11.42:51d  :processpac: Force magazine random
11.52:51d  :processpac: Non-text head unit - will not load text
11.61:51d  :rw_packet :        ce (206) ------------->
11.61:51d  :rw_packet : ********************************************************
11.61:51d  :processpac: Got uC ID
12.35:51d  :rw_packet : ********************************************************
12.35:51d  :rw_packet :              <============ 30 (48)
12.35:51d  :rw_packet :              <============ 00 (0)
12.35:51d  :rw_packet :              <============ 01 (1)
12.35:51d  :rw_packet :              <============ 00 (0)
12.35:51d  :rw_packet :              <============ 01 (1)
12.35:51d  :rw_packet :              <============ 00 (0)
12.35:51d  :rw_packet :              <============ 0d (13)
12.35:51d  :rw_packet :              <============ c1 (193)
12.35:51d  :rw_packet :        ce (206) ------------->
12.35:51d  :rw_packet : ********************************************************
12.35:51d  :processpac: Got Play 1/1/13
12.65:phatd:start_mp3p: FILE: /dos/PhatHack.hack
12.65:phatd:start_mp3p: Authenticating /dos/patcher
12.76:phatd:start_mp3p: Re-setting playlist loading values
12.76:phatd:start_mp3p: Exec /dos/patcher /dos/PhatHack.hack 0 (null)
12.77:phatd:start_mp3p: player started pid 14
12.77:phatd:main      : Queueing PLAYd1t0s13 for end of startfile




==============================================================




It would appear the patch failed on your PhatBox, please join the PhatHack Community forums [http://forum.phathack.com] and post the contents of the file PHTSYS/logfile.txt 


Patch 1 OK: Expected: 0000 1a00    Actual: 0000 1a00
Patch 2 OK: Expected: 0000 1a00    Actual: 0000 1a00
Patch 3 OK: Expected: 0000 1a00    Actual: 0000 1a00
Patch 4 OK: Expected: 0000 1a00    Actual: 0000 1a00
Patch 5 OK: Expected: 0000 13a0    Actual: 0000 13a0
Patch 6 Failed: Expected: 0000 e350    Actual: 0001 e350
Patch 7 Failed: Expected: 0000 03a0    Actual: 0001 03a0
Patch 8 Failed: Expected: 0000 eb00    Actual: 02db eb00
Patch 9 Failed: Expected: 0000 eb00    Actual: 02f7 eb00
The hack had already been applied.

==================================================================

I have read somewhere that maybe I have to corrupt the ramdisk.sig file but I think it's better to wait for some suggestions.

Hoping somebody can help me because I see only CD CHECK in the display and no more sound 

greetings from Holland,         .......René......

[S80_UK]

Hi,

One question which may help people to help you...

You say the DMS was ex Volvo.  That's not a problem, but it makes me ask whether the Phatnoise box is also a Volvo one...?  It has been found in the past that Volvo boxes can require a slightly different patching compared to most others.  I think it's been done successfully however, so I'm sure we'll get you sorted soon.

Les.  (with a VW Phatbox in a Volvo)

[toophat]

Hi S80_UK, no the box in my BMW is a normal Phatnoise. I only bought the complete Volvo unit (with DMS ofcourse) as backup unit, and to experiment with hacking the box in my car but till now no luck 
Sorry for the confusing situation but do you think it's gonna work again?

greetings and please help somebody...


                  .......René......

[sbingner]

Looks like it's partially completed... like you said, corrupt your ramdisk.sig and see if that fixes it... the patch needs to complete so the ramdisk.sig no longer matters.

[toophat]

Hello sbinger, thanx for your reply! I have corrupted ramdisk.sig (putting a few extra letters in the beginning after saving the original) and put the DMS directly after changing this file in the Phatnoise unit in the BMW. But; same situation as before with exactly the same light sequence of the LEDS with <CD CHECK> in the display of the radio.
It looks to me that it won't start and it's searching for something or don't want to boot. Ofcourse I tried again to disconnect the connector from the Phatnoise, wait a minute and connect it again but no effect :-(

I did copy and paste the PatchVerify.log file (same content as the one before) in this mail and the content of the logfile.txt but the last one is also identical as before so nothing has changed after corrupting the ramdisk.sig

Other suggestions if you have pleeeease...

p.s. If you want to have more info give me your email adress and I send the nescesary files to you

=======================PatchVerify.log==============================

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: 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: 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!

====================================================================

[sbingner]

You need to corrupt it by copying a different .sig over it... manually corrupting it didn't always work properly for me.  Try copying linux.sig to ramdisk.sig

[toophat]

Hi Sbinger, I made a copie of linux.sig and renamed it to ramdisk.sig and put it in the root of the PHTSYS partition.
When I put it directly after that in the BMW the situation is a bit different then before; 5 times green ON, after that, green LED is OFF for 5 seconds and after that 11 times green is ON. So no long green LED's periods more... During this the red LED is allways ON. After the 5 times ON and 11 times ON follows a period of no activity (I think...), The only thing is a red LED ON and no green LED activity for about half an hour.

One time (I put the DMS a few times when there was no activity again in the Phatnoise unit in the car) the headunit selected itself to the Radio mode (booting ??) so I set it back to Phatnoise mode.

I inspected the content of PatchVerify.log but the content of it was the same as the version before. The bootload.log is also the same. It says that BOOT0-0 and BOOT0-1 are OK, and BOOT0, BOOT9, BOOTB, BOOTF and BOOT* are succesfull.

I'm  feeling a bit fear about the whole situation Sbinger, but thanx so far for trying to solve this problem     

greetings           ........René.......

[sbingner]

When ramdisk.sig is the problem there should be a failed in bootload.log - when you have a valid ramdisk.sig do you get that?

[toophat]

Hi, I do not get a ramdisk.sig failure in bootload.log (eveything is OK and succesful). As you said this is strange when I corrupted just my ramdisk 
In Stage 7 of 8 from the Patcher Wizard I get the message that Patch 6 'till 9 had failed. (ramdisk.sig problem?)


Thanx and grtz and here are some log files;


==============Screendump from Patcher Wizard stage 7 of 8==============

It would appear the patch failed on your PhatBox, please join the PhatHack Community forums

[http://forum.phathack.com] and post the contents of the file PHTSYS/logfile.txt 


Patch 1 OK: Expected: 0000 1a00    Actual: 0000 1a00
Patch 2 OK: Expected: 0000 1a00    Actual: 0000 1a00
Patch 3 OK: Expected: 0000 1a00    Actual: 0000 1a00
Patch 4 OK: Expected: 0000 1a00    Actual: 0000 1a00
Patch 5 OK: Expected: 0000 13a0    Actual: 0000 13a0
Patch 6 Failed: Expected: 0000 e350    Actual: 0001 e350
Patch 7 Failed: Expected: 0000 03a0    Actual: 0001 03a0
Patch 8 Failed: Expected: 0000 eb00    Actual: 02db eb00
Patch 9 Failed: Expected: 0000 eb00    Actual: 02f7 eb00
The hack had already been applied.


=================bootload.log================================

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


==================patch.log==============================

Verifying patch progress

There are  patches not yet applied

Beginning patch process

Corrupting ramdisk
===========================================================

[VorTechS]

I wonder, is there a firmware mismatch somewhere here causing a problem Sam?

René you mention you did a firmware update using the tools, can you clarify:

a) Did you select the option 'Install non-hacked firmware'?
b) Did you select the BMW firmware?
c) Did you select the option 'Reflash box with firmware'?

a) is very important for non-hacked boxes as I'd be surprised if the DMS would work in the PhatBox at all.

If the answer is yes to b) then c) is also very important.

I'm just wondering if all things check out with your answers, if the box only partially completed the firmware update (if that's possible) and perhaps that's why the Patch is having a hard time....?

[toophat]

Hello VorTechs, and others ofcourse ;-) when I started a few days ago with applying the patch I have read the doc file that becomes with the patcher very secure. What I remembered is that I did select 'Install non-hacked firmware'. Normal, because it was a standard DMS with Volvo firmware.
I have printed out the whole procedure and I have accentuated it with a pencil. Also I select the option 'Reflash box with firmware' and I did select the BMW firmware from the drop-down list. Version 9, the last I think. I'm absolutly sure about these three things you mention.
After that the DMS was doing fine in the Phatnoise unit in the BMW and playing music. Normal behaviour.

After aplying the patch on the DMS it seems to me that, when I put the DMS in the Phatnoise unit, it stopped somewhere in the starting (hacking) procedue internally, i.e. it hangs;
Because when I insert the DMS in my car the LED sequence is 5 times green ON, after that, green LED is OFF for 5 seconds and after that 11 times green is ON. After that no activity anymore (green LED OFF and red LED always ON) so it looks to me it stopped somewhere.

F.Y.I. the DMS situation is now so that ramdisk.sig is a renamed linux.sig file (corrupted ramdisk) on advice from Sbinger but maybe you know that already ;-)

Maybe it's an idea to "clean" the whole DMS and started from scrap. Good idea or are there still possibilities to make it working?

Another question; this "LED sequence blinking" is that important and what does it means?


Thank so far everybody for the help   

[sbingner]

The 11 green blinks, are they REALLY fast?

[toophat]

No I think not; 1 second On and 1 second OFF. Same as the "five times ON green sequence"

[sbingner]

It appears to be having issues reading some file then (probably one of "linux", "linux.sig", "ramdisk", "ramdisk.sig", "rc.sh", or "rc.sig") -- I need you to Quick FORMAT your phtsys (FAT32) then copy on those files in the order listed, followed by the rest of the contents of your phtsys.  You can just copy off the files you have there now to a temp directory then put them back.  The ROM bootloader that phatnoise uses kinda sucks sometimes and decides it doesn't feel like reading a file if it's not rigth at the beginning or something.  It could be that it can't handle fragments, but I think I defragmented once and it didn't help.

[sbingner]

I believe this could also be a result of an unsigned DMS in an unpatched box (or possibly missing signature on stock DMS), but you're using an original DMS right?  Also, the first couple patch applied should remove "unsigned DMS" from the equasion.

[toophat]

Hi Sbinger, sorry for that I ask for an extra explanation because my English is not so good as yours...
If I understand everything well I must;

a) Make a backup of all the files on the PHTSYS partition
b) Quick Format de PHTSYS partition (FAT32)
c) After that copy all the files back from the backup that was before on the PHTSYS partition

Or do you mean something different with "copy on those files in the order listed, followed by the rest of the contents of your phtsys". That is not clear for me.

Must I put I put the "renamed" ramdisk.sig file on the formatted PHTSYS or the one before?

Please explain a bit clearly 

Thanx

[toophat]

About your last question (I saw it too late...);
the DMS I use is an original Volvo where I put new firmware on (BMW version 9), and was working well after that in my BMW.  Its a 20 Gig and working normal before the patching with the PatchWizard. After that I put the patch on but patch 6 'till 9 failed as the PatchVerify.log file says.

grtz,    .......René.......

[sbingner]

Or do you mean something different with "copy on those files in the order listed, followed by the rest of the contents of your phtsys". That is not clear for me.

Yes. Put them on in that order followed by the rest of the files

Must I put I put the "renamed" ramdisk.sig file on the formatted PHTSYS or the one before?

I'd try with the "renamed" one first... if that doesn't work, start all over and use a valid ramdisk.sig.

[toophat]

I'll try it this morning and put all the files back after the Quick Format on the PHTSYS partition.
grtz.

[toophat]

Hi Sbinger, the unbelievable has happened. After the things you said a voice spoke at the car radio "your system has now been unlocked, please remove your DMS and ....." The PatchWrite.log file says also that Patch 1 'till 9 is OK and the Hack is applied!!
I'm more than happy now and much compliments for you

          A few things;

a) What shall I do with this 20Gig DMS; put the HD out and put it on a safe place what I have read? And after that put a bigger HD inside?
I'm thinking at a 120 Gb Western Digital Scorpio, WD1200BEVE, a good one you think?

b) Shall I store the files from this 20 Gig DMS on a safe place?

c)Maybe you understood already but I have another DMS, a 60 Gig that belongs with the Phatnoise unit in my car. Ofcourse it's unpatched and original Phatnoise.
What can I do with it. Can I use it normally, or shall I let the wizzard treat it as a new DMS (Create New DMS).

Many, many thanks so far, and uhh, can I put a donation with Paypall somewhere for all the good work you (and your colleages do)?

grtz from Holland,         ..........René.........