PhatHack
The Hacking Hoedown => PhatBox Hacking => Topic started by: 16vpup on February 13, 2008, 01:18:36 pm
-
I originally started w/ a Kenwood Music Keg 10GB Magazine and aquired a Nissan Phatbox interface cable that is setup to operate through the Satellite radio of the factory radio. I own a 2005 Nissan Frontier King Cab w/ the uprated OEM 6 disc in dash stereo. I also got 2 originally sold Nissan Phatbox players to work with. I tried the magazine in the player and had no results w/ operation before the hack. I had a friend of mine help me originally w/ the hack process on the Kenwood magazine. When the magazine was 1st installed in the player w/ the hack the display on the radio showed up as if the Phatbox took the place of one set of presets and it was trying to play but all it said was (empty disc, empty disc, empty disc, on and on.......). I tried corrupting the ramdisk.sig file and still had no results. The Phatbox showed to be booting properly but the last parts of the log showed to be unverified when I was working w/ my friend on the process. After that I restored the magazine to it's original state and I didn't get any response again. Now I have the 10GB Kenwood magazine duplicated onto a 120GB updated harddrive. I don't currently have the logs that showed unverified because that was when my friend had helped me and I don't know if he still has them. I have 2 other working sytems in 2 different Volkswagens at this time so I have other unhacked magazines to work with. I would love to get the system working in my truck if anyone can help. The other 2 systems are original and unhacked currently, 1 of which I bought NEW for my 2003 VW GTI and both of them work perfectly. I decided to start using 1 of the VW cartridges for a hack and below are the results of the 1st hack process w/ out the ramdisk.sig modified.
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful
after modifying the ramdisk.sig file by just typing in a few extra characters in the file this is what I got
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*-X: Failed
Neither times above did I ever get an actual log file like before w/ the Kenwood magazine. I need to know if I'm going to have to put firmware on my magazine in order for the player to receive firmware to play through the radio again. As of the last of the 2 times I heard the player repeat empty disc, empty disc, over and over the system has not recognized the player again at all. I did also put music on the magazine in the thought that it said empty disc, empty disc, because it was empty. I'm not sure where to go from here because I have also disconnected the cable from the back of the radio to try to reset the player functions and have numerous times tried to plug up the player w/ the magazine in it in hopes it would start working again. I have tried both players I have now but only one of them originally worked w/ the setup I had, now neither of them work(play that is). I do get red and green lights coming on but can't tell what's really going on because they either both come on and stay on or the red light comes on then the green blinks slowly then goes into a really fast blinking state. I hope the boot logs help some, but I don't have the other logs that originally showed unverified because my friend who was helping me has already gotten discouraged from just 2 days of working w/ it. I am determined to get the system working in my truck because I love my systems in the other 2 VW's I have. Please help if anyone can. Thank you.
-
If you see "BOOT*: Successful" - DO NOT CORRUPT YOUR RAMDISK
This means it completed the bootloader process, and yor error lies somewhere past there... you can load the debug rc.sh pairs to find where the error is from there. see http://downloads.phathack.com/bushing/rc_pairs.zip
-
Do I just overwrite the 2 files that match the 2 you mentioned? After that are the logs created or is the answer stored in the 2 files you mentioned? At this time I am working with a 20GB hacked VW magazine. That's the one that had the boot logs I listed. I, of course was using it in an originally setup Nissan box. Do I still need to wait til after the boot process gets fixed before I load the Nissan firmware? Is the Nissan firmware that's available made to work with a satellite radio type setup wiring or a cd changer type setup wiring? Mine is for sure setup for wiring to the satellite radio plug and I was originally able to access the phatbox through the radio button not the CD button since I have an in dash OEM CD Changer. As of recently I have had no interaction w/ the radio since 2 or 3 hack attempts with my other 10GB Kenwood
Music Keg magazine (of which now it has a 120GB hardrive in it that's mirrored to match the original Kenwood Magazine). The 120GB magazine is only being recognized in MY Computer as a 10GB magazine, is there something wrong with what my friend did in the partition process? I am most likely on my own w/ the hack process since my computer friend has become frustrated after 2 days of getting the Phatbox working and it's still not working. I have 4 players currently: 2 Original Nissan players in silver that may have corrupt firmware now, 1 original VW player that has not been messed with in silver and 1 other older version vw setup player in crimson red. I have 2 working VW systems, 1 completely unhacked system that I bought new and 1 that I have just begun to use the magazine to try to run the hack on in attempts that it may work better than my Kenwwod magazine. I am just ok with computer stuff, so I may not understand everything you write, but please have mercy and patience with me. I'm willing to do what it takes to get the system working. Thanks for any help you can offer.
-
You can load the nissan firmware at any point. You just replace rc.sh and rc.sig and logfile.txt is auto created.
-
Oh, and the hack process is designed so that it is impossible for it to actually corrupt your firmware.
-
I restored my ramdisk.sig to original as before and this is what I got again:
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*-X: Failed
It showed just as displayed above w/ BOOT0-0: OK offset from the others but still I got no regular logs even after replacing rc.sh and rc.sig w/ the ones you listed. Are there any clues in what I sent you so far as to what the problem is? Am I looking in the wrong place for the other logs or are they not supposed to be there yet because the boot didn't complete this time? I am thinking of just restoring my girlfriends magazine back to its original state because I just got another 20GB VW magazine from a friend of mine today to do w/ it what I please. What is the right way to restore it to the undisturbed state. I still have her music on it and I want to get it back to her. So I would just like to start from scratch w/ proper instruction so I know for sure I'm doing the hack right. I would like to know if you are aware of any other different ways to approach a Nissan system because what I've done so far hasn't quite worked. I still have the other original 10GB Kenwood Music Keg magazine that I started with that I would really like to get working because it has the 120GB harddrive in it now. Should I start w/ that one though it might not be in the best state, or should I use the other 20GB magazine I just got from my friend that most likely has never been messed with. The player does not register on the radio at all anymore whether the magazine is inserted or not. Nearly evertime I hookup the cable to the phatbox I normally have always had the magazine in the box 1st before powering it up. This time I got the red light 1st, then the green light blinked 3 times, then green went out, then came back on and just constantly blinked til I got to work about 25 minutes later. When I got to work the red light was still on and the green light was still blinking constantly and didn't stop when I turned the truck off. I left the magazine in for about 1 hr longer and lights were still blinking so I pulled the magazine out for fear of my battery getting drained. Please, whatever you can do to help I would appreciate. Thanks for the input so far.
-
Oh, I think I see yourproblem... you can't corrupt it but "typing in the file" -- you need to copy linux.sig or some other signature over ramdisk.sig
If you see BOOT*: SUCCESSFUL you don't need to... but if you're seeing logs written and seeing failure there, you need to corrupt it the way I said above.
-
I want to restore my girlfriends 20GB VW magazine that I started the hack on, so I can give it back to her because it has her music on it. Then I am going to start completely over again w/ the updated hack utilities on a completely original 3rd VW 20GB magazine that I just got from a friend of mine. Do I run the patchclean.bat to restore the magazine to original unhacked state? Or is there another way? I just want to start over w/ the possibility of a more reliable way w/ the other newer utilities. I still have my 1st magazine that my computer bud has the backup of on his computer but that magazine now currently has the 120GB drive in it and that is the one I ultimately want to be using when all of my work is done. Can you point me to a step by step instruction on the DMS restore utility using the backup I created from my girlfriends original DMS. I have begun to get a little confused through the steps since I have had to change so many things on both drives and I just look forward to the day when it actually works in my Nissan. I have gotten to the point where I'm considering putting a VW radio in my Nissan just to have the possibility of it actually working, but that would be nearly the same amount of work and would be like starting from scratch on the install. I also want to retain my steering wheel hand controls in my Nissan and if I put a VW radio in it I would probably lose that function, and would therefore force me to wonder why I didn't just buy an IPOD. I really like the Phatbox systems in the other 2 cars in the family and I am not completely sold on the IPOD since I already have a small MP3 player for running and riding bikes. I didn't originally use the most recent hack utilities since they either just weren't posted yet or my friend didn't happen upon them when he looked it up for me. My Nissan player has not recognized/played since the 2nd attempt at the hack procedures, and it also has not stored a patch log since that time. Whatever has happened to the player to allow it to not respond is what I'm thinking needs to be fixed 1st or am I wrong? You guys I'm sure know alot more about this than I do, any help you can offer I would definitely appreciate. Thanks for everything so far.
-
patchclean should do it
If you could hit enter once in a while in your post, so as to make it actually readable we'd be able to help you much more easily. Reading a giant block of text is kind of not something I look forward to when I wake up in the morning.
-
Sorry about the long blocks, just wanted to put down some good detail so you knew what I've done so far.
I tried patchclean twice and it didn't work; that is, it didn't allow it to play in the player. Then I moved my dock and the original DMS backup file phtsys.tar.gz to another computer w/ winzip on it and I used winzip to extract the old files and installed them on the DMS then ejected the magazine from the computer and system played again in the 2nd VW.
Now that I have my girlfriends mag restored I would like to use the untouched original extra 3rd 20GB VW mag to start from scratch. Are the newest windows hack utilities the most stable and most reliable to use for my Nissan system. Since I have already had 2 mags be unsuccessful in hack attempts I need to be sure that it's not operator error (meaning me). What's the best 1st thing to do to prepare my mag to plug into a slightly questionable box. My PB does respond w/ multiple lights coming on and off but last nights attempt the red light stayed on constant then the green light flashed all night, but sporadically system shut down. Like I said I left it all night and in the morning both lights were still on. Now I'm starting from scratch. Please help and sorry about the long blocks above again.
-
The new tools shouldn't cause any irrepairable damage to your DMS, in fact quite the reverse, it keeps a backup of files replaced on your PC and only modifies the startup sound instead of replacing the profiles file.
I don't know the true number of failures, but AFAIK there's about a 90% success rate, but it's really about 95% as we can usually help those who can't get it running to run. The remaining 5% tend to be people who can't make the hack run using v2.10 of the tools but I have an alternative alpha version of the tools available for those. Only 1 person ever got back to me to tell me this version worked okay.
If you have a questionable box, I'd suggest you use an original DMS and make sure you are able to use the box using the original firmware. If you want to upgrade the firmware on the box then you can use the DMS tools to do this, by using the 'Create New DMS' -> 'Upgrade firmware' button and ensuring you choose the option 'Install non-hacked firmware'.
Once you have the box working as you'd expect, then run the hack tools. There's full documentation in the hack tools ZIP file, so make sure you read through these before you get started.
Good luck.
-
Well if it's not working with the patch on it, taking it off isn't going to make it start working ;) The patch is not to the DMS, it is to the Player. You probably need to corrupt the ramdisk.sig (by copying linux.sig over it) and let it complete. Did you do that yet?
-
Yes, I did try that exact way of corrupting it and it still showed unsuccessful on the last boot log line.
Since I have tried multiple ways w/ the earlier utilities, what do you think is my best bet at getting it booting up on 1st try w/ my 3rd DMS that hasn't been messed w/ yet? I was planning on using the most recent DMS hack utilities this time. Since I have had so much bad luck w/ previous attempts I just want the advise so I start the procedure correctly.
-
Which DMS you use isn't going to matter. But I'd just have it apply the patch normally, see if that works... and check bootload.log then show me what it says in the bootload.log from the new DMS when you get it.
-
I started over on my 3rd 20GB VW original PB magazine. I went through the firmware update to Nissan 3.00 firmware and it looks as though the magazine for sure held the firmware because PMM recognized it and listed it as Nissan firmware.
I put the magazine in the player and the red light was on and the green light flashed steady for a little while instead of flashing really fast like before. I waited til the lights went out, removed the magazine then put the magazine back into the player and tried to access the player through the radio and still could not access it. The red light came on and the green light I think flashed 3 times then went out and the red light just stayed on solid til I turned the radio off. Then the red light went out and I pulled out the cartridge. I've tried this several times and now just get the same results, the red light just stays on solid after the green light flashes a couple times. I need to know if the firmware I need for my player to operate is something that may not be available.
The cable I am using hooks up to the satellite radio plug on the back of the radio and most people talk about CD changer interaction just like both my VW's use. Is there a way around this if the firmware I originally had on my player can't be had. Do I have to buy another Nissan Radio w/ no CD player in the dash or one w/ a SAT button on it to get it to work? Do you know anyone else who has a Nissan system that can shed a little light on proper sequence for player hookup and proper setup to get system working?
I really need some help before I screw up every resource I have in my possession. I now have no idea if the 2 players I have are ever going to work or if my magazines are in recognizeable state for a Nissan system. What should I do next? Start the hack again?
-
I used the 2.10 Hack tools on my 20GB mag and ran the hack wizard on it. The red light came on then the green flashed I think 1 time then a couple more times then the green light went out and the red light stayed on constant. What does it mean when the red light stays on constant? because both of the original Nissan players did the same thing when the mag was inserted. The boot log showed this though:
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful
Is that a good sign? What next? Where exactly are the other logs supposed to be created, because I don't think they exist? I am ready to get this thing working and I have 2 other vw players to use if there's a possibility that the Nissan ones may be screwed up in some way. I still need to know if the firmware 2.0 or 3.0 supports Satellite radio hookup or if it needs to be hooked up CD changer style. Does anyone know that? My player originally did play or show a display on the radio but now it doesn't at all after a few or multiple hack attempts. Can you guys help, please?
-
Do you have music on it? --- What you describe is normal operations, except for the whole not playing music
-
Ph, generally the Sat radio connection and the CD Changer connection are the same thing... but I'm no expert on Nissan
-
I still get this bootload.log
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful
but still no regular patchlogs unless they are under some other file I am not aware of. Will there be a patchlog file generated when it completes the patch? I still haven't gotten that answered from anyone yet. Here are some samples of my ramdisk file:
<removed irrlevant ramdisk excerpt>
Why is this all in here and does that info help at all. I still need to know where to look for the patchlog files in case I am not looking in the right place. I would assume if it booted properly then there should be patchlog files. Still no music from PB playing on my radio and no PB display or recognition of PB on my radio. I have tried nearly everything I can think of to get this working, any other suggestions?
I do have music on the PB magazine and the PMM recognizes that it has Nissan firmware on it now.
-
Sorry this is soooo long but here it is, the logfile.text:
07.89:phatd:main : Media Daemon (phatd) $Revision: 1.217 $
07.91:phatd:main : Debug level = 10
Selected profile is: Default
08.19:phatd:main : Using /dos/exec.ini for exec.ini
08.31:phatd:fork_if_in: Spawning /dos/51d
08.32:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
09.21:51d :main :
--- 51d (Mar 3 2004 18:49:12) --- $Revision: 1.205 $
09.21:51d :main : Debug level = 10
09.28:phatd:main : Entering Main loop
09.29:phatd:main : Socket 2 has MSG_ID 2
09.58:51d :openserpor: /dev/ttyS1 open fd=11
09.58:51d :main : Old ISP timeout value set to 50000 uSec
09.58:51d :main : Rollins timeout value set to 100000 uSec
09.58:51d :test_uC_ve: f9 (249) ------------>
09.59:51d :test_uC_ve: <============ 53 (83)
09.59:51d :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
09.59:51d :parse_pac : opening /dos/firmware.pac
09.59:51d :parse_pac : PAC file summary
09.59:51d :parse_pac : firmware name h: 47
09.59:51d :parse_pac : firmware name l: 00
09.59:51d :parse_pac : firmware ver : 01
09.59:51d :parse_pac : firmware base h: 0f
09.59:51d :parse_pac : firmware base l: fd
09.59:51d :parse_pac : firmware size h: 17
09.59:51d :parse_pac : firmware size l: d8
09.60:51d :send_arm_s: firmware_modification=2
09.61:51d :rw_packet : Buffering 10 at 0
09.61:51d :rw_packet : ########################################################
09.61:51d :rw_packet : 10 (16) ------------->
09.61:51d :rw_packet : Expecting HACK
09.62:51d :rw_packet : <============ ac (172)
09.62:51d :rw_packet : 01 (1) ------------->
09.62:51d :rw_packet : Expecting BACK
09.63:51d :rw_packet : <============ bd (189)
09.63:51d :rw_packet : 47 (71) ------------->
09.63:51d :rw_packet : Expecting BACK
09.64:51d :rw_packet : <============ bd (189)
09.64:51d :rw_packet : 00 (0) ------------->
09.64:51d :rw_packet : Expecting BACK
09.65:51d :rw_packet : <============ bd (189)
09.65:51d :rw_packet : 00 (0) ------------->
09.65:51d :rw_packet : Expecting BACK
09.66:51d :rw_packet : <============ bd (189)
09.66:51d :rw_packet : 02 (2) ------------->
09.66:51d :rw_packet : Expecting BACK
09.67:51d :rw_packet : <============ bd (189)
09.67:51d :rw_packet : 01 (1) ------------->
09.67:51d :rw_packet : Expecting BACK
09.68:51d :rw_packet : <============ bd (189)
09.68:51d :rw_packet : a5 (165) ------------->
09.68:51d :rw_packet : Expecting PACK
09.69:51d :rw_packet : <============ ce (206)
09.69:51d :rw_packet : <============ 11 (17)
09.69:51d :rw_packet : <============ 00 (0)
09.69:51d :rw_packet : <============ 06 (6)
09.69:51d :rw_packet : <============ 13 (19)
09.69:51d :rw_packet : <============ 02 (2)
09.69:51d :rw_packet : <============ d4 (212)
09.69:51d :rw_packet : <============ 14 (20)
09.69:51d :rw_packet : <============ 47 (71)
09.69:51d :rw_packet : <============ 00 (0)
09.69:51d :rw_packet : <============ 02 (2)
09.69:51d :rw_packet : <============ 00 (0)
09.69:51d :rw_packet : <============ 00 (0)
09.69:51d :rw_packet : <============ 00 (0)
09.70:51d :rw_packet : <============ a3 (163)
09.70:51d :rw_packet : <============ 21 (33)
09.70:51d :rw_packet : <============ df (223)
09.70:51d :rw_packet : ########################################################
09.70:51d :rw_packet : ce (206) ------------->
09.70:51d :rw_packet : ********************************************************
09.70:51d :processpac: Got Session: mode 0, run type 6, lot 13 02
09.70:phatd:log_bc : CPUid info:
Unique ID: 0x72cc1a90
Random ID: 0x72cc1a907ebaff74f561c33f02617836
CPU: EP73xx, ver 0x02
Lot Code: 0x1302
09.71:51d :processpac: Initializing 1.2 DAC
09.72:51d :processpac: SSA head unit
09.72:51d :processpac: Extra help enabled
09.81:51d :processpac: Non-text head unit - will not load text
09.90:51d :rw_packet : ce (206) ------------->
09.91:51d :rw_packet : ********************************************************
09.91:51d :processpac: Got uC ID
10.73:51d :rw_packet : ce (206) ------------->
10.73:51d :rw_packet : ********************************************************
10.73:51d :processpac: Got Query total disc
10.73:51d :rw_packet : Buffering 7d at 0
10.73:51d :rw_packet : ########################################################
10.73:51d :rw_packet : 7d (125) ------------->
10.73:51d :rw_packet : Expecting HACK
10.74:51d :rw_packet : <============ ac (172)
10.74:51d :rw_packet : 00 (0) ------------->
10.74:51d :rw_packet : Expecting BACK
10.75:51d :rw_packet : <============ bd (189)
10.75:51d :rw_packet : 04 (4) ------------->
10.75:51d :rw_packet : Expecting BACK
10.76:51d :rw_packet : <============ bd (189)
10.76:51d :rw_packet : 7f (127) ------------->
10.76:51d :rw_packet : Expecting PACK
10.77:51d :rw_packet : <============ ce (206)
10.77:51d :rw_packet : <============ 20 (32)
10.77:51d :rw_packet : <============ 00 (0)
10.77:51d :rw_packet : <============ 01 (1)
10.77:51d :rw_packet : <============ df (223)
10.77:51d :rw_packet : ########################################################
10.77:51d :rw_packet : ce (206) ------------->
10.77:51d :rw_packet : ********************************************************
10.77:51d :processpac: Got Query total tracks 1
10.77:51d :rw_packet : Buffering 7c at 0
10.77:51d :rw_packet : ########################################################
10.78:51d :rw_packet : 7c (124) ------------->
10.78:51d :rw_packet : Expecting HACK
10.78:51d :rw_packet : <============ ac (172)
10.78:51d :rw_packet : 00 (0) ------------->
10.78:51d :rw_packet : Expecting BACK
10.79:51d :rw_packet : <============ bd (189)
10.79:51d :rw_packet : 02 (2) ------------->
10.79:51d :rw_packet : Expecting BACK
10.80:51d :rw_packet : <============ bd (189)
10.80:51d :rw_packet : 00 (0) ------------->
10.80:51d :rw_packet : Expecting BACK
10.81:51d :rw_packet : <============ bd (189)
10.81:51d :rw_packet : 01 (1) ------------->
10.81:51d :rw_packet : Expecting BACK
10.82:51d :rw_packet : <============ bd (189)
10.82:51d :rw_packet : 81 (129) ------------->
10.82:51d :rw_packet : Expecting PACK
10.83:51d :rw_packet : <============ ce (206)
10.83:51d :rw_packet : ########################################################
07.87:phatd:main : Media Daemon (phatd) $Revision: 1.217 $
07.88:phatd:main : Debug level = 10
Selected profile is: Default
08.15:phatd:main : Using /dos/exec.ini for exec.ini
08.27:phatd:fork_if_in: Spawning /dos/51d
08.27:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
09.09:51d :main :
--- 51d (Mar 3 2004 18:49:12) --- $Revision: 1.205 $
09.09:51d :main : Debug level = 10
09.25:phatd:main : Entering Main loop
09.26:phatd:main : Socket 2 has MSG_ID 2
09.60:51d :openserpor: /dev/ttyS1 open fd=11
09.60:51d :main : Old ISP timeout value set to 50000 uSec
09.60:51d :main : Rollins timeout value set to 100000 uSec
09.60:51d :test_uC_ve: f9 (249) ------------>
09.61:51d :test_uC_ve: <============ 53 (83)
09.61:51d :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
09.61:51d :parse_pac : opening /dos/firmware.pac
09.61:51d :parse_pac : PAC file summary
09.61:51d :parse_pac : firmware name h: 47
09.61:51d :parse_pac : firmware name l: 00
09.61:51d :parse_pac : firmware ver : 01
09.61:51d :parse_pac : firmware base h: 0f
09.61:51d :parse_pac : firmware base l: fd
09.61:51d :parse_pac : firmware size h: 17
09.61:51d :parse_pac : firmware size l: d8
09.62:51d :send_arm_s: firmware_modification=2
09.63:51d :rw_packet : Buffering 10 at 0
09.63:51d :rw_packet : ########################################################
09.63:51d :rw_packet : 10 (16) ------------->
09.63:51d :rw_packet : Expecting HACK
09.64:51d :rw_packet : <============ ac (172)
09.64:51d :rw_packet : 01 (1) ------------->
09.64:51d :rw_packet : Expecting BACK
09.66:51d :rw_packet : <============ bd (189)
09.66:51d :rw_packet : 47 (71) ------------->
09.66:51d :rw_packet : Expecting BACK
09.67:51d :rw_packet : <============ bd (189)
09.67:51d :rw_packet : 00 (0) ------------->
09.67:51d :rw_packet : Expecting BACK
09.68:51d :rw_packet : <============ bd (189)
09.68:51d :rw_packet : 00 (0) ------------->
09.68:51d :rw_packet : Expecting BACK
09.69:51d :rw_packet : <============ bd (189)
09.69:51d :rw_packet : 02 (2) ------------->
09.69:51d :rw_packet : Expecting BACK
09.70:51d :rw_packet : <============ bd (189)
09.70:51d :rw_packet : 01 (1) ------------->
09.70:51d :rw_packet : Expecting BACK
09.71:51d :rw_packet : <============ bd (189)
09.71:51d :rw_packet : a5 (165) ------------->
09.71:51d :rw_packet : Expecting PACK
09.72:51d :rw_packet : <============ ce (206)
09.72:51d :rw_packet : <============ 11 (17)
09.72:51d :rw_packet : <============ 00 (0)
09.72:51d :rw_packet : <============ 06 (6)
09.72:51d :rw_packet : <============ 13 (19)
09.72:51d :rw_packet : <============ 02 (2)
09.72:51d :rw_packet : <============ d4 (212)
09.72:51d :rw_packet : <============ 14 (20)
09.72:51d :rw_packet : <============ 47 (71)
09.72:51d :rw_packet : <============ 00 (0)
09.72:51d :rw_packet : <============ 02 (2)
09.72:51d :rw_packet : <============ 00 (0)
09.72:51d :rw_packet : <============ 00 (0)
09.72:51d :rw_packet : <============ 00 (0)
09.73:51d :rw_packet : <============ a3 (163)
09.73:51d :rw_packet : ########################################################
09.73:51d :rw_packet : ce (206) ------------->
09.73:51d :rw_packet : ********************************************************
09.73:51d :processpac: Got Session: mode 0, run type 6, lot 13 02
09.73:phatd:log_bc : CPUid info:
Unique ID: 0x72cc1a90
Random ID: 0x72cc1a907ebaff74f561c33f02617836
CPU: EP73xx, ver 0x02
Lot Code: 0x1302
09.74:51d :processpac: Initializing 1.2 DAC
09.74:51d :processpac: SSA head unit
09.74:51d :processpac: Extra help enabled
09.83:51d :processpac: Non-text head unit - will not load text
09.93:51d :rw_packet : ce (206) ------------->
09.93:51d :rw_packet : ********************************************************
09.93:51d :processpac: Got uC ID
82.34:51d :rw_packet : ********************************************************
82.34:51d :rw_packet : <============ 61 (97)
82.34:51d :rw_packet : <============ 9f (159)
82.34:51d :rw_packet : ce (206) ------------->
82.34:51d :rw_packet : ********************************************************
82.34:51d :processpac: Got Shutdown
06.89:phatd:main : Media Daemon (phatd) $Revision: 1.217 $
06.90:phatd:main : Debug level = 10
Selected profile is: Default
07.16:phatd:main : Using /dos/exec.ini for exec.ini
07.28:phatd:fork_if_in: Spawning /dos/51d
07.29:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
08.04:51d :main :
--- 51d (Mar 3 2004 18:49:12) --- $Revision: 1.205 $
08.04:51d :main : Debug level = 10
08.29:phatd:main : Entering Main loop
08.30:phatd:main : Socket 2 has MSG_ID 2
08.62:51d :openserpor: /dev/ttyS1 open fd=11
08.62:51d :main : Old ISP timeout value set to 50000 uSec
08.63:51d :main : Rollins timeout value set to 100000 uSec
08.63:51d :test_uC_ve: f9 (249) ------------>
08.64:51d :test_uC_ve: <============ 53 (83)
08.64:51d :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
08.64:51d :parse_pac : opening /dos/firmware.pac
08.64:51d :parse_pac : PAC file summary
08.64:51d :parse_pac : firmware name h: 47
08.64:51d :parse_pac : firmware name l: 00
08.64:51d :parse_pac : firmware ver : 01
08.64:51d :parse_pac : firmware base h: 0f
08.64:51d :parse_pac : firmware base l: fd
08.64:51d :parse_pac : firmware size h: 17
08.64:51d :parse_pac : firmware size l: d8
08.65:51d :send_arm_s: firmware_modification=2
08.66:51d :rw_packet : Buffering 10 at 0
08.68:51d :rw_packet : ########################################################
08.68:51d :rw_packet : 10 (16) ------------->
08.69:51d :rw_packet : Expecting HACK
08.69:51d :rw_packet : <============ ac (172)
08.69:51d :rw_packet : 01 (1) ------------->
08.69:51d :rw_packet : Expecting BACK
08.70:51d :rw_packet : <============ bd (189)
08.70:51d :rw_packet : 47 (71) ------------->
08.70:51d :rw_packet : Expecting BACK
08.71:51d :rw_packet : <============ bd (189)
08.71:51d :rw_packet : 00 (0) ------------->
08.71:51d :rw_packet : Expecting BACK
08.72:51d :rw_packet : <============ bd (189)
08.72:51d :rw_packet : 00 (0) ------------->
08.72:51d :rw_packet : Expecting BACK
08.73:51d :rw_packet : <============ bd (189)
08.73:51d :rw_packet : 02 (2) ------------->
08.73:51d :rw_packet : Expecting BACK
08.74:51d :rw_packet : <============ bd (189)
08.74:51d :rw_packet : 01 (1) ------------->
08.74:51d :rw_packet : Expecting BACK
08.75:51d :rw_packet : <============ bd (189)
08.75:51d :rw_packet : a5 (165) ------------->
08.75:51d :rw_packet : Expecting PACK
08.76:51d :rw_packet : <============ ce (206)
08.76:51d :rw_packet : <============ 11 (17)
08.76:51d :rw_packet : <============ 00 (0)
08.76:51d :rw_packet : <============ 00 (0)
08.76:51d :rw_packet : <============ 13 (19)
08.76:51d :rw_packet : <============ 02 (2)
08.76:51d :rw_packet : <============ da (218)
08.76:51d :rw_packet : ########################################################
08.76:51d :rw_packet : ce (206) ------------->
08.76:51d :rw_packet : ********************************************************
08.76:51d :processpac: Got Session: mode 0, run type 0, lot 13 02
08.77:phatd:log_bc : CPUid info:
Unique ID: 0x9bf51a90
Random ID: 0x9bf51a903e8771e463dcdb279223c3c8
CPU: EP73xx, ver 0x02
Lot Code: 0x1302
08.77:phatd:log_bc : Writing CPUid MRU
07.85:phatd:main : Media Daemon (phatd) $Revision: 1.217 $
07.86:phatd:main : Debug level = 10
Selected profile is: Default
08.12:phatd:main : Using /dos/exec.ini for exec.ini
08.24:phatd:fork_if_in: Spawning /dos/51d
08.25:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
09.06:51d :main :
--- 51d (Mar 3 2004 18:49:12) --- $Revision: 1.205 $
09.06:51d :main : Debug level = 10
09.24:phatd:main : Entering Main loop
09.25:phatd:main : Socket 2 has MSG_ID 2
09.57:51d :openserpor: /dev/ttyS1 open fd=11
09.57:51d :main : Old ISP timeout value set to 50000 uSec
09.57:51d :main : Rollins timeout value set to 100000 uSec
09.57:51d :test_uC_ve: f9 (249) ------------>
09.58:51d :test_uC_ve: <============ 53 (83)
09.58:51d :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
09.58:51d :parse_pac : opening /dos/firmware.pac
09.58:51d :parse_pac : PAC file summary
09.58:51d :parse_pac : firmware name h: 47
09.58:51d :parse_pac : firmware name l: 00
09.58:51d :parse_pac : firmware ver : 01
09.58:51d :parse_pac : firmware base h: 0f
09.58:51d :parse_pac : firmware base l: fd
09.58:51d :parse_pac : firmware size h: 17
09.58:51d :parse_pac : firmware size l: d8
09.59:51d :send_arm_s: firmware_modification=2
09.60:51d :rw_packet : Buffering 10 at 0
09.60:51d :rw_packet : ########################################################
09.60:51d :rw_packet : 10 (16) ------------->
09.60:51d :rw_packet : Expecting HACK
09.61:51d :rw_packet : <============ ac (172)
09.61:51d :rw_packet : 01 (1) ------------->
09.61:51d :rw_packet : Expecting BACK
09.62:51d :rw_packet : <============ bd (189)
09.62:51d :rw_packet : 47 (71) ------------->
09.62:51d :rw_packet : Expecting BACK
09.63:51d :rw_packet : <============ bd (189)
09.63:51d :rw_packet : 00 (0) ------------->
09.63:51d :rw_packet : Expecting BACK
09.64:51d :rw_packet : <============ bd (189)
09.64:51d :rw_packet : 00 (0) ------------->
09.64:51d :rw_packet : Expecting BACK
09.65:51d :rw_packet : <============ bd (189)
09.67:51d :rw_packet : 02 (2) ------------->
09.67:51d :rw_packet : Expecting BACK
09.68:51d :rw_packet : <============ bd (189)
09.68:51d :rw_packet : 01 (1) ------------->
09.68:51d :rw_packet : Expecting BACK
09.69:51d :rw_packet : <============ bd (189)
09.69:51d :rw_packet : a5 (165) ------------->
09.69:51d :rw_packet : Expecting PACK
09.70:51d :rw_packet : <============ ce (206)
09.70:51d :rw_packet : <============ 11 (17)
09.70:51d :rw_packet : <============ 00 (0)
09.70:51d :rw_packet : <============ 06 (6)
09.70:51d :rw_packet : <============ 13 (19)
09.70:51d :rw_packet : <============ 02 (2)
09.70:51d :rw_packet : <============ d4 (212)
09.70:51d :rw_packet : <============ 14 (20)
09.70:51d :rw_packet : <============ 47 (71)
09.70:51d :rw_packet : <============ 00 (0)
09.70:51d :rw_packet : <============ 02 (2)
09.70:51d :rw_packet : <============ 00 (0)
09.70:51d :rw_packet : <============ 00 (0)
09.70:51d :rw_packet : <============ 00 (0)
09.71:51d :rw_packet : <============ a3 (163)
09.71:51d :rw_packet : <============ 21 (33)
09.71:51d :rw_packet : <============ df (223)
09.71:51d :rw_packet : ########################################################
09.71:51d :rw_packet : ce (206) ------------->
09.71:51d :rw_packet : ********************************************************
09.71:51d :processpac: Got Session: mode 0, run type 6, lot 13 02
09.71:phatd:log_bc : CPUid info:
Unique ID: 0x9bf51a90
Random ID: 0x9bf51a903e8771e463dcdb279223c3c8
CPU: EP73xx, ver 0x02
Lot Code: 0x1302
09.72:51d :processpac: Initializing 1.2 DAC
09.72:51d :processpac: SSA head unit
09.73:51d :processpac: Extra help enabled
09.82:51d :processpac: Non-text head unit - will not load text
09.91:51d :rw_packet : ce (206) ------------->
09.91:51d :rw_packet : ********************************************************
09.91:51d :processpac: Got uC ID
10.73:51d :rw_packet : ce (206) ------------->
10.74:51d :rw_packet : ********************************************************
10.74:51d :processpac: Got Query total disc
10.74:51d :rw_packet : Buffering 7d at 0
10.74:51d :rw_packet : ########################################################
10.74:51d :rw_packet : 7d (125) ------------->
10.74:51d :rw_packet : Expecting HACK
10.75:51d :rw_packet : <============ ac (172)
10.75:51d :rw_packet : 00 (0) ------------->
10.75:51d :rw_packet : Expecting BACK
10.76:51d :rw_packet : <============ bd (189)
10.76:51d :rw_packet : 04 (4) ------------->
10.76:51d :rw_packet : Expecting BACK
10.77:51d :rw_packet : <============ bd (189)
10.77:51d :rw_packet : 7f (127) ------------->
10.77:51d :rw_packet : Expecting PACK
10.78:51d :rw_packet : <============ ce (206)
10.78:51d :rw_packet : <============ 20 (32)
10.78:51d :rw_packet : <============ 00 (0)
10.78:51d :rw_packet : <============ 01 (1)
10.78:51d :rw_packet : <============ df (223)
10.78:51d :rw_packet : ########################################################
10.78:51d :rw_packet : ce (206) ------------->
10.78:51d :rw_packet : ********************************************************
10.78:51d :processpac: Got Query total tracks 1
10.78:51d :rw_packet : Buffering 7c at 0
10.78:51d :rw_packet : ########################################################
10.79:51d :rw_packet : 7c (124) ------------->
10.79:51d :rw_packet : Expecting HACK
10.79:51d :rw_packet : <============ ac (172)
10.79:51d :rw_packet : 00 (0) ------------->
10.79:51d :rw_packet : Expecting BACK
10.80:51d :rw_packet : <============ bd (189)
10.80:51d :rw_packet : 02 (2) ------------->
10.80:51d :rw_packet : Expecting BACK
10.81:51d :rw_packet : <============ bd (189)
10.81:51d :rw_packet : 00 (0) ------------->
10.81:51d :rw_packet : Expecting BACK
10.82:51d :rw_packet : <============ bd (189)
10.82:51d :rw_packet : 01 (1) ------------->
10.82:51d :rw_packet : Expecting BACK
10.83:51d :rw_packet : <============ bd (189)
10.83:51d :rw_packet : 81 (129) ------------->
10.83:51d :rw_packet : Expecting PACK
10.84:51d :rw_packet : <============ ce (206)
10.84:51d :rw_packet : ########################################################
64.26:51d :rw_packet : ********************************************************
64.26:51d :rw_packet : <============ 61 (97)
64.26:51d :rw_packet : <============ 9f (159)
64.26:51d :rw_packet : ce (206) ------------->
64.26:51d :rw_packet : ********************************************************
64.26:51d :processpac: Got Shutdown
07.89:phatd:main : Media Daemon (phatd) $Revision: 1.217 $
07.90:phatd:main : Debug level = 10
Selected profile is: Default
08.18:phatd:main : Using /dos/exec.ini for exec.ini
08.29:phatd:fork_if_in: Spawning /dos/51d
08.30:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
09.07:51d :main :
--- 51d (Mar 3 2004 18:49:12) --- $Revision: 1.205 $
09.07:51d :main : Debug level = 10
09.28:phatd:main : Entering Main loop
09.29:phatd:main : Socket 2 has MSG_ID 2
09.59:51d :openserpor: /dev/ttyS1 open fd=11
09.59:51d :main : Old ISP timeout value set to 50000 uSec
09.59:51d :main : Rollins timeout value set to 100000 uSec
09.59:51d :test_uC_ve: f9 (249) ------------>
09.60:51d :test_uC_ve: <============ 53 (83)
09.60:51d :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
09.60:51d :parse_pac : opening /dos/firmware.pac
09.60:51d :parse_pac : PAC file summary
09.60:51d :parse_pac : firmware name h: 47
09.60:51d :parse_pac : firmware name l: 00
09.60:51d :parse_pac : firmware ver : 01
09.60:51d :parse_pac : firmware base h: 0f
09.60:51d :parse_pac : firmware base l: fd
09.60:51d :parse_pac : firmware size h: 17
09.60:51d :parse_pac : firmware size l: d8
09.61:51d :send_arm_s: firmware_modification=2
09.62:51d :rw_packet : Buffering 10 at 0
09.62:51d :rw_packet : ########################################################
09.62:51d :rw_packet : 10 (16) ------------->
09.62:51d :rw_packet : Expecting HACK
09.63:51d :rw_packet : <============ ac (172)
09.63:51d :rw_packet : 01 (1) ------------->
09.63:51d :rw_packet : Expecting BACK
09.64:51d :rw_packet : <============ bd (189)
09.64:51d :rw_packet : 47 (71) ------------->
09.64:51d :rw_packet : Expecting BACK
09.65:51d :rw_packet : <============ bd (189)
09.65:51d :rw_packet : 00 (0) ------------->
09.65:51d :rw_packet : Expecting BACK
09.66:51d :rw_packet : <============ bd (189)
09.66:51d :rw_packet : 00 (0) ------------->
09.66:51d :rw_packet : Expecting BACK
09.67:51d :rw_packet : <============ bd (189)
09.67:51d :rw_packet : 02 (2) ------------->
09.67:51d :rw_packet : Expecting BACK
09.68:51d :rw_packet : <============ bd (189)
09.68:51d :rw_packet : 01 (1) ------------->
09.68:51d :rw_packet : Expecting BACK
09.69:51d :rw_packet : <============ bd (189)
09.69:51d :rw_packet : a5 (165) ------------->
09.69:51d :rw_packet : Expecting PACK
09.70:51d :rw_packet : <============ ce (206)
09.70:51d :rw_packet : <============ 11 (17)
09.70:51d :rw_packet : <============ 00 (0)
09.70:51d :rw_packet : <============ 06 (6)
09.70:51d :rw_packet : <============ 13 (19)
09.70:51d :rw_packet : <============ 02 (2)
09.70:51d :rw_packet : <============ d4 (212)
09.70:51d :rw_packet : <============ 14 (20)
09.70:51d :rw_packet : <============ 47 (71)
09.70:51d :rw_packet : <============ 00 (0)
09.70:51d :rw_packet : <============ 02 (2)
09.70:51d :rw_packet : <============ 00 (0)
09.70:51d :rw_packet : <============ 00 (0)
09.70:51d :rw_packet : <============ 00 (0)
09.71:51d :rw_packet : <============ a3 (163)
09.71:51d :rw_packet : <============ 21 (33)
09.71:51d :rw_packet : <============ df (223)
09.71:51d :rw_packet : ########################################################
09.73:51d :rw_packet : ce (206) ------------->
09.73:51d :rw_packet : ********************************************************
09.73:51d :processpac: Got Session: mode 0, run type 6, lot 13 02
09.74:phatd:log_bc : CPUid info:
Unique ID: 0x9bf51a90
Random ID: 0x9bf51a903e8771e463dcdb279223c3c8
CPU: EP73xx, ver 0x02
Lot Code: 0x1302
09.74:51d :processpac: Initializing 1.2 DAC
09.74:51d :processpac: SSA head unit
09.75:51d :processpac: Extra help enabled
09.84:51d :processpac: Non-text head unit - will not load text
09.93:51d :rw_packet : ce (206) ------------->
09.93:51d :rw_packet : ********************************************************
09.93:51d :processpac: Got uC ID
10.75:51d :rw_packet : ce (206) ------------->
10.76:51d :rw_packet : ********************************************************
10.76:51d :processpac: Got Query total disc
10.76:51d :rw_packet : Buffering 7d at 0
10.76:51d :rw_packet : ########################################################
10.76:51d :rw_packet : 7d (125) ------------->
10.76:51d :rw_packet : Expecting HACK
10.77:51d :rw_packet : <============ ac (172)
10.77:51d :rw_packet : 00 (0) ------------->
10.77:51d :rw_packet : Expecting BACK
10.78:51d :rw_packet : <============ bd (189)
10.78:51d :rw_packet : 04 (4) ------------->
10.78:51d :rw_packet : Expecting BACK
10.79:51d :rw_packet : <============ bd (189)
10.79:51d :rw_packet : 7f (127) ------------->
10.79:51d :rw_packet : Expecting PACK
10.80:51d :rw_packet : <============ ce (206)
10.80:51d :rw_packet : <============ 20 (32)
10.80:51d :rw_packet : <============ 00 (0)
10.80:51d :rw_packet : <============ 01 (1)
10.80:51d :rw_packet : <============ df (223)
10.80:51d :rw_packet : ########################################################
10.80:51d :rw_packet : ce (206) ------------->
10.80:51d :rw_packet : ********************************************************
10.80:51d :processpac: Got Query total tracks 1
10.80:51d :rw_packet : Buffering 7c at 0
10.80:51d :rw_packet : ########################################################
10.81:51d :rw_packet : 7c (124) ------------->
10.81:51d :rw_packet : Expecting HACK
10.81:51d :rw_packet : <============ ac (172)
10.81:51d :rw_packet : 00 (0) ------------->
10.81:51d :rw_packet : Expecting BACK
10.82:51d :rw_packet : <============ bd (189)
10.82:51d :rw_packet : 02 (2) ------------->
10.82:51d :rw_packet : Expecting BACK
10.83:51d :rw_packet : <============ bd (189)
10.83:51d :rw_packet : 00 (0) ------------->
10.83:51d :rw_packet : Expecting BACK
10.84:51d :rw_packet : <============ bd (189)
10.84:51d :rw_packet : 01 (1) ------------->
10.84:51d :rw_packet : Expecting BACK
10.85:51d :rw_packet : <============ bd (189)
10.85:51d :rw_packet : 81 (129) ------------->
10.85:51d :rw_packet : Expecting PACK
10.86:51d :rw_packet : <============ ce (206)
10.86:51d :rw_packet : ########################################################
16.69:51d :rw_packet : ********************************************************
16.69:51d :rw_packet : <============ 61 (97)
16.69:51d :rw_packet : <============ 9f (159)
16.69:51d :rw_packet : ce (206) ------------->
16.69:51d :rw_packet : ********************************************************
16.69:51d :processpac: Got Shutdown
07.85:phatd:main : Media Daemon (phatd) $Revision: 1.217 $
07.86:phatd:main : Debug level = 10
Selected profile is: Default
08.15:phatd:main : Using /dos/exec.ini for exec.ini
08.27:phatd:fork_if_in: Spawning /dos/51d
08.27:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
09.05:51d :main :
--- 51d (Mar 3 2004 18:49:12) --- $Revision: 1.205 $
09.05:51d :main : Debug level = 10
09.29:phatd:main : Entering Main loop
09.29:phatd:main : Socket 2 has MSG_ID 2
09.62:51d :openserpor: /dev/ttyS1 open fd=11
09.62:51d :main : Old ISP timeout value set to 50000 uSec
09.65:51d :main : Rollins timeout value set to 100000 uSec
09.65:51d :test_uC_ve: f9 (249) ------------>
09.66:51d :test_uC_ve: <============ 53 (83)
09.66:51d :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
09.66:51d :parse_pac : opening /dos/firmware.pac
09.66:51d :parse_pac : PAC file summary
09.66:51d :parse_pac : firmware name h: 47
09.66:51d :parse_pac : firmware name l: 00
09.66:51d :parse_pac : firmware ver : 01
09.66:51d :parse_pac : firmware base h: 0f
09.66:51d :parse_pac : firmware base l: fd
09.66:51d :parse_pac : firmware size h: 17
09.66:51d :parse_pac : firmware size l: d8
09.67:51d :send_arm_s: firmware_modification=2
09.68:51d :rw_packet : Buffering 10 at 0
09.68:51d :rw_packet : ########################################################
09.68:51d :rw_packet : 10 (16) ------------->
09.68:51d :rw_packet : Expecting HACK
09.69:51d :rw_packet : <============ ac (172)
09.69:51d :rw_packet : 01 (1) ------------->
09.69:51d :rw_packet : Expecting BACK
09.70:51d :rw_packet : <============ bd (189)
09.70:51d :rw_packet : 47 (71) ------------->
09.70:51d :rw_packet : Expecting BACK
09.71:51d :rw_packet : <============ bd (189)
09.71:51d :rw_packet : 00 (0) ------------->
09.71:51d :rw_packet : Expecting BACK
09.72:51d :rw_packet : <============ bd (189)
09.72:51d :rw_packet : 00 (0) ------------->
09.72:51d :rw_packet : Expecting BACK
09.73:51d :rw_packet : <============ bd (189)
09.73:51d :rw_packet : 02 (2) ------------->
09.73:51d :rw_packet : Expecting BACK
09.74:51d :rw_packet : <============ bd (189)
09.74:51d :rw_packet : 01 (1) ------------->
09.74:51d :rw_packet : Expecting BACK
09.75:51d :rw_packet : <============ bd (189)
09.75:51d :rw_packet : a5 (165) ------------->
09.75:51d :rw_packet : Expecting PACK
09.76:51d :rw_packet : <============ ce (206)
09.76:51d :rw_packet : <============ 11 (17)
09.76:51d :rw_packet : <============ 00 (0)
09.76:51d :rw_packet : <============ 06 (6)
09.76:51d :rw_packet : <============ 13 (19)
09.76:51d :rw_packet : <============ 02 (2)
09.76:51d :rw_packet : <============ d4 (212)
09.76:51d :rw_packet : <============ 14 (20)
09.76:51d :rw_packet : <============ 47 (71)
09.76:51d :rw_packet : <============ 00 (0)
09.76:51d :rw_packet : <============ 02 (2)
09.76:51d :rw_packet : <============ 00 (0)
09.76:51d :rw_packet : <============ 00 (0)
09.76:51d :rw_packet : <============ 00 (0)
09.77:51d :rw_packet : <============ a3 (163)
09.77:51d :rw_packet : ########################################################
09.77:51d :rw_packet : ce (206) ------------->
09.77:51d :rw_packet : ********************************************************
09.77:51d :processpac: Got Session: mode 0, run type 6, lot 13 02
09.77:phatd:log_bc : CPUid info:
Unique ID: 0x9bf51a90
Random ID: 0x9bf51a903e8771e463dcdb279223c3c8
CPU: EP73xx, ver 0x02
Lot Code: 0x1302
09.78:51d :processpac: Initializing 1.2 DAC
09.78:51d :processpac: SSA head unit
09.78:51d :processpac: Extra help enabled
09.87:51d :processpac: Non-text head unit - will not load text
09.97:51d :rw_packet : ce (206) ------------->
09.97:51d :rw_packet : ********************************************************
09.97:51d :processpac: Got uC ID
40.20:51d :rw_packet : ********************************************************
40.20:51d :rw_packet : <============ 61 (97)
40.20:51d :rw_packet : <============ 9f (159)
40.20:51d :rw_packet : ce (206) ------------->
40.20:51d :rw_packet : ********************************************************
40.20:51d :processpac: Got Shutdown
06.85:phatd:main : Media Daemon (phatd) $Revision: 1.217 $
06.86:phatd:main : Debug level = 10
Selected profile is: Default
07.15:phatd:main : Using /dos/exec.ini for exec.ini
07.27:phatd:fork_if_in: Spawning /dos/51d
07.27:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
07.79:51d :main :
--- 51d (Mar 3 2004 18:49:12) --- $Revision: 1.205 $
07.79:51d :main : Debug level = 10
08.28:phatd:main : Entering Main loop
08.29:phatd:main : Socket 2 has MSG_ID 2
08.63:51d :openserpor: /dev/ttyS1 open fd=11
08.63:51d :main : Old ISP timeout value set to 50000 uSec
08.63:51d :main : Rollins timeout value set to 100000 uSec
08.63:51d :test_uC_ve: f9 (249) ------------>
08.64:51d :test_uC_ve: <============ 53 (83)
08.64:51d :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
08.64:51d :parse_pac : opening /dos/firmware.pac
08.64:51d :parse_pac : PAC file summary
08.64:51d :parse_pac : firmware name h: 47
08.64:51d :parse_pac : firmware name l: 00
08.64:51d :parse_pac : firmware ver : 01
08.64:51d :parse_pac : firmware base h: 0f
08.64:51d :parse_pac : firmware base l: fd
08.64:51d :parse_pac : firmware size h: 17
08.64:51d :parse_pac : firmware size l: d8
08.65:51d :send_arm_s: firmware_modification=2
08.66:51d :rw_packet : Buffering 10 at 0
08.66:51d :rw_packet : ########################################################
08.66:51d :rw_packet : 10 (16) ------------->
08.66:51d :rw_packet : Expecting HACK
08.67:51d :rw_packet : <============ ac (172)
08.67:51d :rw_packet : 01 (1) ------------->
08.67:51d :rw_packet : Expecting BACK
08.68:51d :rw_packet : <============ bd (189)
08.68:51d :rw_packet : 47 (71) ------------->
08.68:51d :rw_packet : Expecting BACK
08.69:51d :rw_packet : <============ bd (189)
08.69:51d :rw_packet : 00 (0) ------------->
08.69:51d :rw_packet : Expecting BACK
08.70:51d :rw_packet : <============ bd (189)
08.70:51d :rw_packet : 00 (0) ------------->
08.70:51d :rw_packet : Expecting BACK
08.71:51d :rw_packet : <============ bd (189)
08.71:51d :rw_packet : 02 (2) ------------->
08.71:51d :rw_packet : Expecting BACK
08.72:51d :rw_packet : <============ bd (189)
08.72:51d :rw_packet : 01 (1) ------------->
08.72:51d :rw_packet : Expecting BACK
08.73:51d :rw_packet : <============ bd (189)
08.73:51d :rw_packet : a5 (165) ------------->
08.73:51d :rw_packet : Expecting PACK
08.74:51d :rw_packet : <============ ce (206)
08.74:51d :rw_packet : <============ 11 (17)
08.74:51d :rw_packet : <============ 00 (0)
08.74:51d :rw_packet : <============ 00 (0)
08.74:51d :rw_packet : <============ 13 (19)
08.74:51d :rw_packet : <============ 02 (2)
08.74:51d :rw_packet : <============ da (218)
08.74:51d :rw_packet : ########################################################
08.74:51d :rw_packet : ce (206) ------------->
08.74:51d :rw_packet : ********************************************************
08.74:51d :processpac: Got Session: mode 0, run type 0, lot 13 02
08.75:phatd:log_bc : CPUid info:
Unique ID: 0x72cc1a90
Random ID: 0x72cc1a907ebaff74f561c33f02617836
CPU: EP73xx, ver 0x02
Lot Code: 0x1302
08.75:phatd:log_bc : Writing CPUid MRU
07.87:phatd:main : Media Daemon (phatd) $Revision: 1.217 $
07.89:phatd:main : Debug level = 10
Selected profile is: Default
08.18:phatd:main : Using /dos/exec.ini for exec.ini
08.29:phatd:fork_if_in: Spawning /dos/51d
08.30:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
09.13:51d :main :
--- 51d (Mar 3 2004 18:49:12) --- $Revision: 1.205 $
09.13:51d :main : Debug level = 10
09.28:phatd:main : Entering Main loop
09.29:phatd:main : Socket 2 has MSG_ID 2
09.59:51d :openserpor: /dev/ttyS1 open fd=11
09.59:51d :main : Old ISP timeout value set to 50000 uSec
09.59:51d :main : Rollins timeout value set to 100000 uSec
09.59:51d :test_uC_ve: f9 (249) ------------>
09.60:51d :test_uC_ve: <============ 53 (83)
09.60:51d :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
09.60:51d :parse_pac : opening /dos/firmware.pac
09.60:51d :parse_pac : PAC file summary
09.60:51d :parse_pac : firmware name h: 47
09.60:51d :parse_pac : firmware name l: 00
09.60:51d :parse_pac : firmware ver : 01
09.63:51d :parse_pac : firmware base h: 0f
09.63:51d :parse_pac : firmware base l: fd
09.63:51d :parse_pac : firmware size h: 17
09.63:51d :parse_pac : firmware size l: d8
09.64:51d :send_arm_s: firmware_modification=2
09.65:51d :rw_packet : Buffering 10 at 0
09.65:51d :rw_packet : ########################################################
09.65:51d :rw_packet : 10 (16) ------------->
09.65:51d :rw_packet : Expecting HACK
09.66:51d :rw_packet : <============ ac (172)
09.66:51d :rw_packet : 01 (1) ------------->
09.66:51d :rw_packet : Expecting BACK
09.67:51d :rw_packet : <============ bd (189)
09.67:51d :rw_packet : 47 (71) ------------->
09.67:51d :rw_packet : Expecting BACK
09.68:51d :rw_packet : <============ bd (189)
09.68:51d :rw_packet : 00 (0) ------------->
09.68:51d :rw_packet : Expecting BACK
09.69:51d :rw_packet : <============ bd (189)
09.69:51d :rw_packet : 00 (0) ------------->
09.69:51d :rw_packet : Expecting BACK
09.70:51d :rw_packet : <============ bd (189)
09.70:51d :rw_packet : 02 (2) ------------->
09.70:51d :rw_packet : Expecting BACK
09.71:51d :rw_packet : <============ bd (189)
09.71:51d :rw_packet : 01 (1) ------------->
09.71:51d :rw_packet : Expecting BACK
09.72:51d :rw_packet : <============ bd (189)
09.72:51d :rw_packet : a5 (165) ------------->
09.72:51d :rw_packet : Expecting PACK
09.73:51d :rw_packet : <============ ce (206)
09.73:51d :rw_packet : <============ 11 (17)
09.73:51d :rw_packet : <============ 00 (0)
09.73:51d :rw_packet : <============ 06 (6)
09.73:51d :rw_packet : <============ 13 (19)
09.73:51d :rw_packet : <============ 02 (2)
09.73:51d :rw_packet : <============ d4 (212)
09.73:51d :rw_packet : <============ 14 (20)
09.73:51d :rw_packet : <============ 47 (71)
09.73:51d :rw_packet : <============ 00 (0)
09.73:51d :rw_packet : <============ 02 (2)
09.73:51d :rw_packet : <============ 00 (0)
09.73:51d :rw_packet : <============ 00 (0)
09.73:51d :rw_packet : <============ 00 (0)
09.74:51d :rw_packet : <============ a3 (163)
09.74:51d :rw_packet : <============ 21 (33)
09.74:51d :rw_packet : <============ df (223)
09.74:51d :rw_packet : ########################################################
09.74:51d :rw_packet : ce (206) ------------->
09.74:51d :rw_packet : ********************************************************
09.74:51d :processpac: Got Session: mode 0, run type 6, lot 13 02
09.74:phatd:log_bc : CPUid info:
Unique ID: 0x72cc1a90
Random ID: 0x72cc1a907ebaff74f561c33f02617836
CPU: EP73xx, ver 0x02
Lot Code: 0x1302
09.75:51d :processpac: Initializing 1.2 DAC
09.75:51d :processpac: SSA head unit
09.76:51d :processpac: Extra help enabled
09.85:51d :processpac: Non-text head unit - will not load text
09.94:51d :rw_packet : ce (206) ------------->
09.94:51d :rw_packet : ********************************************************
09.94:51d :processpac: Got uC ID
10.76:51d :rw_packet : ce (206) ------------->
10.77:51d :rw_packet : ********************************************************
10.77:51d :processpac: Got Query total disc
10.77:51d :rw_packet : Buffering 7d at 0
10.77:51d :rw_packet : ########################################################
10.77:51d :rw_packet : 7d (125) ------------->
10.77:51d :rw_packet : Expecting HACK
10.78:51d :rw_packet : <============ ac (172)
10.78:51d :rw_packet : 00 (0) ------------->
10.78:51d :rw_packet : Expecting BACK
10.79:51d :rw_packet : <============ bd (189)
10.79:51d :rw_packet : 04 (4) ------------->
10.79:51d :rw_packet : Expecting BACK
10.80:51d :rw_packet : <============ bd (189)
10.80:51d :rw_packet : 7f (127) ------------->
10.80:51d :rw_packet : Expecting PACK
10.81:51d :rw_packet : <============ ce (206)
10.81:51d :rw_packet : <============ 20 (32)
10.81:51d :rw_packet : <============ 00 (0)
10.81:51d :rw_packet : <============ 01 (1)
10.81:51d :rw_packet : <============ df (223)
10.81:51d :rw_packet : ########################################################
10.81:51d :rw_packet : ce (206) ------------->
10.81:51d :rw_packet : ********************************************************
10.81:51d :processpac: Got Query total tracks 1
10.81:51d :rw_packet : Buffering 7c at 0
10.82:51d :rw_packet : ########################################################
10.82:51d :rw_packet : 7c (124) ------------->
10.82:51d :rw_packet : Expecting HACK
10.83:51d :rw_packet : <============ ac (172)
10.83:51d :rw_packet : 00 (0) ------------->
10.83:51d :rw_packet : Expecting BACK
10.84:51d :rw_packet : <============ bd (189)
10.84:51d :rw_packet : 02 (2) ------------->
10.84:51d :rw_packet : Expecting BACK
10.85:51d :rw_packet : <============ bd (189)
10.85:51d :rw_packet : 00 (0) ------------->
10.85:51d :rw_packet : Expecting BACK
10.86:51d :rw_packet : <============ bd (189)
10.86:51d :rw_packet : 01 (1) ------------->
10.86:51d :rw_packet : Expecting BACK
10.87:51d :rw_packet : <============ bd (189)
10.87:51d :rw_packet : 81 (129) ------------->
10.87:51d :rw_packet : Expecting PACK
10.88:51d :rw_packet : <============ ce (206)
10.88:51d :rw_packet : ########################################################
68.97:51d :rw_packet : ********************************************************
68.97:51d :rw_packet : <============ 61 (97)
68.97:51d :rw_packet : <============ 9f (159)
68.97:51d :rw_packet : ce (206) ------------->
68.97:51d :rw_packet : ********************************************************
68.97:51d :processpac: Got Shutdown
Does this info help at all? If I shut it down it would've been because the red light just stayed on constant w/ no green light activity again. But I only pulled the magazine after the radio was turned off and the red light went out.
-
It's doing like I said, it's working fine but not actually playing music. That is usually caused by the incorrect firmware or a bad or incorrectly seated cable.
The patch may, or may not have completed.... once you get it playing music we'll know ;) -- I'm not sure if it plays the startup sound without any "Play" command, but I can see from your logfile that it never tried to do so. When it executes the startup sound the patch is run.
Don't worry about the contents of your ramdisk.
-
If the red light is on solid can that still mean it is applying the hack? I just got finished putting the magazine in my truck and leaving it w/ the key on to see if the hack would restart and complete even w/ the red light only on constant and no green lights coming on after original startup. Can I apply Nissan 2.00 unhacked firmware on a hacked magazine? Currently it has Nissan 3.00 firmware unhacked before running the hack on it. I wanted to try and see if the other version 2.00 would allow it to play this time. Just curious and wanting to try anything I can to get it working.
-
You can put anything you like on there. Like I said, it did not run any sounds in your logfile.txt which means it didn't try to run anything. You need to get your player to play music, I would use whatever firmware worked before.
-
The firmware that was on the player originally is what worked because it was Nissan original. Now after the few hack attempts at getting a 120GB magazine usable I have not been able to get the radio to recognize the Phatbox once plugged up and the magazine put into the player. I have tried disconnecting the player, installing the magazine, then plugging up the player. And I have also tried plugging up the player and then inserting the magazine, still no radio interaction. Do you guys have any kind of failsafe way to for sure get the system to boot and run by the looks of my log info.
I have read and read and read as much as I can about the process but everyone else seems to have better luck than me on getting their systems working. Is there any way to verify that the firmware that I have been constantly trying to install works w/ a system that goes through the SAT radio wiring plug? My radio does not have a separate SAT radio button, but my system when it was 1st plugged up and working used one of the 3 sets of presets to access the phatbox. When toggling through the presets A,B, and C one of them was used by the Phatbox, that was fine with me as long as it was working but now it's not.
I am wondering if I bought another Nissan radio w/ the separate SAT button on it like the BOSE system if the Phatbox would have it's own button and all of a sudden work. Any thoughts on that? or should I just try to work w/ what I've got. I still have 2 VW players that have not been screwed up at all, but I would prefer to use the Nissan ones since that was my reasoning for buying them. I am also not sure if the BOSE system would even work in my truck at all w/out rewiring the whole system.
I don't want to screw up the other 2 players but would be willing to use one of them if you think that would help. I would very much want the most detailed instructions before attempting to hack them. Otherwise I may end up w/ 4 different shaped and colored bricks that won't match anything in my house, the Phatboxes that is. Still need help and after leaving the system w/ the key on and red light on I did not get any different results. Still no interaction.
-
What is the right thing to do after the new firmware looks to have been installed? Unplug the unit, then apply fresh hack utilities, then put the magazine in the player and plug it back up? Or just leave it plugged up, apply the fresh hack utilities, and hope it works. I need some more suggestions or some other way around my problem. At this point, do I need to delete the contents of the Phatsys partition or maybe run patchclean.bat to clean out the hack in hopes that the firmware took this time. Or should I consider starting w/ another player and restoring my original mag., then applying the firmware again and then possibly screwing up the 3rd of the 4 players I have. I'm definitely running out of options and I really need some info from anyone who may have a Nissan system that is working w/ the hack on it. Do you know anyone who does?
-
First Commandment: Thou shalt not hack until thy phatbox doest play music.
Get it to play music, then worry about finishing the hack. Does it play music now?
-
Like I said, it did not run any sounds in your logfile.txt which means it didn't try to run anything. You need to get your player to play music, I would use whatever firmware worked before.
I think what sbingner was trying to get you to do was:
1) Using an existing original DMS, loading the 'non-hacked' firmware version (based on the version last loaded into the PhatBox)
Easiest way of doing this is to run v2.10 of the Windows DMS tools.
Select the top toolbar button 'Create New DMS', select your DMS and select the correct firmware version.
DO check the option 'Install non-hacked firmware' and DO NOT check the option 'Reflash box'
Click on the 'Upgrade Firmware' button to begin the process of patching the firmware on the DMS.
2) If there's no music on the original DMS, put some music on the new DMS
Use whatever you normally use to create new playlists, and creating just one playlist of music should be enough to test with.
Now....if when you insert the DMS the box doesn't work, then something isn't right.
If it works then you may need to try v2.11 of the tools as like my Kenwood Keg and a few other boxes, when the box boots up it's not running the startup sound (which then applies the hack).
v2.11 of the Windows tools, which is NOT publicly available, fixes this problem by inserting a playlist onto an original DMS, as the first playlist...so when you start your PhatBox the first playlist will play and run the hack. I can send you a URL to these version of the tools, and as I think I've mentioned it before somewhere, these tools are NOT publicly available because only one person has tested, and verified that they work.
-
VorTechS pretty much interpreted everything right except:
DO check the option 'Reflash box' <--
The point is to have the same firmware version on there that was working before... so you'll want it to reflash
-
Oh and stop worrying about the fact that it's nissan... that doesn't matter, the patch tests to be sure that the ROM matches a signature before it even starts to patch it... if it didn't match it wouldn't start
-
VorTechS pretty much interpreted everything right except:
DO check the option 'Reflash box' <--
The point is to have the same firmware version on there that was working before... so you'll want it to reflash
Well I used the phrase 'select the correct firmware version', meaning select the version that's known to be on the box. If you don't know the version on the box then DO choose the 'Reflash box' option.
-
I do not know the version that was on the Nissan box originally that worked. I am going to try the other original Nissan player in a VW I have for sale to see if that player will respond to its firmware being changed to VW then try the VW magazine I have been using lately to see if that setup would play correctly in the VW. Now that I have the hack on the magazine, what is the proper way to remove the hack files to try that setup in the VW I have? Should I use patchclean.bat or should I delete the phatsys partition files and manually load the backup info onto the magazine?
I have tried both 2.00 and 3.00 versions of Nissan firmware and still have gotten no response out of the player into the radio since the original couple of attempts of hacks. What is the right thing to do after the frimware upgrade? Leave the box hooked up, pull the magazine, then reinsert it to check it? Or, remove the magazine, unplug the box, then plug the box back up and insert the magazine. I still wish there was someone who had another Nissan system working that I could get other original sequence setup info from, just in case the sequence of hookup is different from the VW sequence. Let me know if you think of anything else about the Nissan operation, I will be working on the other player in the VW next for verification that the other player actually will work or operate (not the one that's in my truck now).
-
There's generally no need to actually unplug the PhatBox after the update... but it doesn't hurt, so you can if you want to see if it makes any difference.
VorTechS posted above a good way to make sure you have a clean DMS...
-
I deleted all of the contents of the Phatsys partition, then unzipped the backup of my original contents into the phatsys partition. I inserted the magazine into the 2nd original Nissan player that I had, but I used my other VW PB cable and hooked it up to the 2003 GTI I am selling(my other GTI). the 1st time mag was plugged in it booted but just said no CD and cycled back to the radio. Then I used the Phathack utilities to load on VW firmware 7.02 onto the player. Plugged the magazine back into the player and it did the steady green blinking light (updating firmware). I came back to the car 20 minutes later, unplugged the magazine then plugged it back in and checked the radio.
The original Nissan system took on the VW firmware and started working perfectly, but at the very beginning when it starts up it says "corrupt disk". What does that mean? and can I get rid of it? and of course since the 1 player that never worked in my truck originally, now works in the VW, I'm kind of back to square one w/ the need for proper Nissan firmware to operate my Nissan system.
Is there any way to check to see if the 2 versions of the Nissan firmware you have listed will even work w/ a SAT radio type install. That may put me back to the easiest thing to do, either get the proper firmware to get it working or buy a radio that just may allow the system to operate easier w/ it's own dedicated button(a SAT button radio maybe).
Still need help from you guys, I just hope this info may shed a little light on what may be my easiest next option for me. Do you know anyone who has a Nissan system working in their vehicle hacked or un hacked?
All I've been used to is VW systems which I don't have many problems getting working but seems like Nissan is a little bit different.
-
OK, you have two vehicles and one works. Have you gotten the other one to work yet? Don't try to hack it until it is -- the hack won't help it work, it'll just let you use larger and unsigned DMS drives. There ARE certain head units that require newer hardware than the VW hardware, I'm not sure if Nissan is one but you may want to check into that if it has never worked in the Nissan. Alternatively you could just hack both of them while they're connected to your VW head unit, since you obviously have firmware that works properly with it.
the one that is working -- you should be fine applying the hack to that one.
-
Oh, as to "Corrupt Disc" -- you probably have a bad playlist or something. debug rc.sh + logfile would help fix that but don't screw with it till you've got things working the way you want them otherwise. It won't hurt anything.
-
I ran through and deleted a couple of the sample music parts loaded by PNoise and then ran PMM clean DMS, then regenerated voice prompts etc. etc. and then I'll try it again in the VW player before I do any other modifying. If I hack it connected to the VW do you think I'll be able to come up w/ the SAT operation firmware to get my Nissan working? I think that may be why it doesn't play through the radio because the original firmware that was loaded on the player (still connected to my truck) may not be the firmware you guys have available in the hack utilities, but I'm still not sure. All I know is that it at least did show a CD type playing display under one set of my radio presets on the 1st couple of attempts at the hack in my truck. Let me know if you can verify the types of firmware offered, my truck is a 2005 model and both firmwares looked to be dated older than that. I am still willing to buy another OEM Nissan radio if there is a chance at getting it working and retaining the steering wheel hand controls.
-
I don't know what firmware you had. Whether the phatbox has the patch applied to it or not will not and will never in any way whatsoever affect whether or not it works in your Nissan. There won't be a "SAT operation firmware" - there is a NISSAN firmware. Feel free to go through and try every version to see if one works, but odds are the newest one - which should be the one used by the hack tools by default - is your best bet. They don't change the protocol daily, so there's no reason an older firmware wouldn't work. Did it ever PLAY MUSIC in your NISSAN before you started trying to hack it?
-
I don't think I had music on it the 1st couple times attempting the hack because it said empty disk, empty disk...... But it did transfer info into the radio in the form of CD type display under the radio mode. I never did get it to actually play music because when it did say empty disk the last time, I did put music on it and it didn't actually play anything and at that point it never showed a display again and for sure did not play any music up until now.
-
OK, work on that... when it's playing music we can look at the hack side.
-
I erased the Phatdta contents and replaced it with the backup of the original contents and got rid of the corrupt disk error message. Now it's time for the hack because the car I'm using as an experiment may be sold by the weekend. I'm prepared to run the hack on the VW so I can try to get it to work in my Nissan. Any special notes or advise you may have going from one car to another w/ the hack on it I would appreciate. I'm running the hack utilities on the 20GB right after I end this message. I'm guessing I shouldn't put Nissan firmware on until it is going to be put into the Nissan is that correct?
I'm going to start the hack now and check in the a/m if I get a successful message.
-
what are these strange keys labeled with funny white symbols that I keep banging upon? Why am I doing this? I'm so confused.
-
Okay, I think we are all getting a little confused here, and we need to step back right to the beginning. It's getting frustrating no doubt from all sides and it's because we are all not articulating ourselves particularly well.
So let's see if we can start again... and I'm going to make this post as un-ambiguous as possible, so to that end please forget absolutely everything you've done up to this point.
Let me start by clarifying something for you, just in case you were not aware of it:
*DMS' cartridges, irrespective of the PhatBox, are GENERIC. This means you can use any ORIGINAL DMS, in any PhatBox providing it has the correct firmware loaded onto it.
*You can ONLY use an ORIGINAL DMS in an unhacked Phatbox. (Clones of original DMS' are not the same as an original DMS and will NOT work)
Okay, to business....
I've re-read your first post, as I understand it you have:
2 x VW PhatBoxes, which are both hacked.
2 x Nissan PhatBoxes that are NOT hacked.
1 x Original Kenwood DMS
1 x 120GB DMS (onto which you've copied the original DMS contents)
First thing is first. Is this correct, or is there more? Don't give us history, just facts. What other PhatBox hardware do you have, and is it original/hacked?
Secondly, we understand that you are trying to hack your Nissan PhatBoxes. I'm sure we don't need to spell this out to you.... but the hack process will ONLY work using an ORIGINAL PhatNoise DMS. You CANNOT use a non-phatnoise disk-based DMS in an unhacked box.
To this end, FORGET THE VW BOXES. They are hacked, they cannot help you hack the Nissan boxes. No amount of running the hack on the VW boxes will help you hack the Nissan boxes. If the VW DMS' are original, then these can be used to hack the nissan boxes once we can prove the nissan boxes work. To that end:
Thirdly, right now we DONT want you run the hack on the Nissan boxes. We want you to USE AN ORIGINAL DMS, to load on the NON-HACKED FIRMWARE to it, PUT SOME MUSIC ON IT (if it doesn't have any) and then verify that the ORIGINAL DMS in the NON-HACKED BOX works without any major issues.
For absolute clarity:
1) USE AN ORIGINAL DMS (it doesn't matter if it's an original one that came with the Nissan boxes, or the VW box or any other box as long as it is an original PhatNoise DMS)
2) DO NOT LOAD THE HACK ON TO IT
3) LOAD THE NISSAN FIRMWARE ON TO IT (use the tools, to do FIRMWARE UPDATE and check the options non-hacked firmware, reflash box)
4) LOAD SOME MUSIC ONTO IT
5) PUT IT IN THE NISSAN PHATBOX
Please forgive the caps. We just want to make sure that you follow the above 5 steps without any deviation. If the box doesn't work from there, then we need to work out why - and that will then lead us to help you get to the end goal of hacking the boxes.
-
You actually do have it wrong.
I have 1 10GB Kenwood Music Keg original DMS
1 120 GB Notebook harddrive that is destined to be in the 10GB DMS magazine
1 20GB VW original DMS that I have started into the hack procedures
(I have backups of both of the above drives in zip format.)
I have 2 unhacked VW Phatboxes/ 1 silver and 1 red older style w/ RCA's also on it
I have 2 possibly half hacked Nissan original players/ 1 showed a display on my radio when 1st hooked up but now it doesn't after attempting the hack (It never actually played music though; it just said empty disc, empty disc constantly, now I don't get any response at all. The other Nissan player never showed a display on my Nissan radio so I used it in the VW I am selling as an experiment. I got the Nissan player that didn't originally respond in my Nissan working in the VW by hooking it up w/ an extra VW cable I had and using the VW original DMS. I transfered the VW updated firmware onto the Nissan box and after doing that the Nissan box did work in the VW. I feel like I have been as descriptive as possible so I could cut out any confusion but the comment about the typing too many words by sbingner I didn't quite appreciate. The reason why I have been descriptive is because I told my friend that was helping me originally that I did have 2 original Nissan boxes and had he listened to me the 1st time I probably would not have continued to put the Kenwwod magazine into the Nissan players w/out putting Nissan firmware on it 1st. The hack was done and no Nissan firmware was installed on it originally so the Kenwood firmware must have been trying to force itself onto the players multiple times and that is where I am now.
I don't know what is up with the firmware or what version was ever on the player originally because now
the radio doesn't recognize the player at all in my Nissan. I have tried nearly everything to get the player working in my Nissan for about 3 weeks and was able to get the VW system working in about 1hour. If I thought this was going to be easy I would have done it myself but it hasn't been and that is why I need the help. Is that not what you're here for. All I ask you to be is patient. I am a VW tech for a living, I know a pretty good bit about computers but not everything, so please don't assume I know what you're talking about everytime. That's where the confusion has come into the play. I guess I'll have to leave it at that but I still don't know what is the best thing to do from here, so I guess I'll wait til I hear back from you after you are able to read the Phatbox items list I have above. I apologize about the novel but all I want to do is get it working w/out months of wasted time.
-
OK, so you have a Nissan system working in a VW now? I'd get the other Nissan system working in the VW also so you know both are in a working condition, then load the Nissan firmware on it and try to get back to where you were... assuming you're trying to get it working with Nissan. It is possible that your Nissan got flashed with Kenwood, which would explain what you described. I'm sure you could hack the one connected to the VW quite easily now... but I'd just wait till I got everything working the way you want it to be in an end state anyway.
1. Connect the unknown-state Nissan PhatBox to any Known-working-with-Phatbox headunit. The VW would be ideal, and get it working with that head unit.
2. Connect the Nissan PhatBox to a Nissan headunit, and flash it with the proper Nissan firmware. Get it working with the Nissan headunit.
3. Now, patch the phatboxes (that are known-working with the HUs they are connected to)
4. Create your 120GB DMS
-
Oh, and don't even bother trying to hack the "1 red older style w/ RCA's also on it" -- those don't have anything to hack, they will work with any HDD already as I understand it.
-
Are you saying that the red Phatbox would have less restrictions than the others? Would that mean that it would be easier to get it working than the others? (not that I want to use it)
I completed the patch on the 20GB original VW DMS last night, all the logs show complete and the wizard stated all was complete. Can I now use it in my Nissan after putting Nissan firmware on it?
or
If it is in completed hack state and it's easier to not turn back then I can use this completed hacked DMS in my other VW GTI that I am keeping and then use the unhacked original that's in that car to get my Nissan working. Now that this DMS is hacked I can put the 120GB harddrive in it, correct?
Let me know if that would be better to do now that the 20GB DMS took the hack. I don't care which vehicle I'm keeping has the 120GB DMS in it, as long as I have one w/ the 120GB in it. Otherwise I would've wasted my money buying the larger drive.
I know the Nissan system seems to be harder to get working, but I still need to try everything I can to get it working since I've commited so much to it. After it is all said and done I want the other players in workable condition to possibly sell them, although I might keep 1 as a backup. Thanks for your help so far.
-
Put the Nissan firmware on the DMS and then check it works in the Nissan PhatBox.
If it does, then re-apply the hack, and see if it completes okay on the Nissan.
-
It shouldn't matter which one you get working with the Nissan -- either the one you patched in the VW or the other. We just want to know for sure that it's working before you start working on getting it in the Nissan. I only said to wait to patch till after because I didn't want to get hung up on trying to apply the patch instead of getting your PhatBox working with your HU.
-
The patch is complete on the 20GB Original DMS and it does play in the VW at this point. I am thinking now that that's complete I am going to put the 120GB harddrive in it and use it in my VW that I am keeping, not the test VW. I got a hold of the person who bought the original Nissan DMS that was in the player that I bought that was in the same year vehicle as my Nissan truck. I am going to swap DMS's w/ him to get the original Nissan DMS w/ most likely the proper original firmware. When I get that one, I think that would be the best time to see if the other player just accepts the proper firmware and starts working. If it doesn't accept it then I guess you'll be hearing from me pretty quick, right after I get that one. Thanks so far, time will tell.
-
When you get the DMS from him, make an empty file in PHTSYS called "forceupdate" - this will make it reflash to the firmware that is on his DMS
-
Thanks, I'll reference this back when I get the DMS from him.
-
I got the original Nissan DMS from the guy that bought it and I'm sending him my other original VW DMS in trade. You said add a file in PHATSYS called "forceupdate" I have done that and plan on inserting it into the box then plugging it up to the cable in the truck. I added one playlist just to make sure it had music on it to start playing. I also ran the backup on PHATSYS and made backups of ramdisk.sig and linux.sig and then also made a backup of PHTDTA. I'll get back to you on that.
New news on my other hack attempt w/ the VW. I did get the 120GB harddrive working in the VW using the other questionable original Nissan player. I plan on leaving that system all intact for use in the other car that I normally drive all the time. Thanks for the help w/ that even though it just happened to work w/ my experiment. I owe it all to you guys for at least producing the new hack utilities that I used. All I wanted to do was get 1 120GB drive working so I can put all of my music on it. Now, I'll just be happy if I can get the original Nissan 20GB DMS working in my Nissan. I'll get back to you on that one.
Is something wrong w/ Gracenote on PM Manager? It doesn't seem to be working on my main music computer.
-
I think Gracenote is a subscription-type service... if PhatNoise stopped paying them royalties they may have cut us off from using it. I haven't tried using it since my PhatBox is still in my closet, so I could be way off but that's the first explanation that comes to mind.
-
There's always PhatHack Media Manager, which uses GraceNote or FreeDB and will never get cut off because it uses a free, non-royalty license. Latest version includes an auto-CD rip function to a specified device (Local PC folder, DMS, or DMS with copy to local PC folder if you set the options right).
But let's stick to topic here ;)
-
I made the empty file called "forceupdate" in PHATSYS on the original Nissan DMS after doing a backup on the original magazine. I inserted the magazine into the player then hooked up the cord to the player. It looked like it was taking the firmware so I let it load up and left it for a while w/ the green light blinking steadily. I came back later and both lights were off so I turned the ignition to the on position and the player powered up but it acted like it was running the firmware update again. The red light came on and the green light started blinking steadily again. I waited about 15-20 min and the player cycled off and on about 5 times with constant steady blinking green light. I checked the radio and found that the interactive display was back after putting the original magazine into the half hacked player. During the cycling off and on the speakers pop as if music is about to be played but it never did play music.
The display I get on the radio is CD-- -- -- and it is located under OEM radio preset "B" or by pressing the RADIO function button which cycles through A/M, F/M, Phatbox/SAT. I tried pulling the magazine out again and reinserting the magazine and all it does is look like it starts the firmware update everytime I turn the key on. Should I now delete the forcesettings and forceupdate files to keep it from constantly running the update? or is there something else I should do? Any suggestions would be appreciated.
-
forceupdate should have been removed by the phatbox when it completed. Is it gone?
-
No, it was still there when I checked after several times of attempting to boot up fully.
-
You MAY need to corrupt your ramdisk.sig then... you need to get a bootload.log file and see what it says
-
I got the player to play music for the 1st time by deleting the forceupdate file manually after previously creating it in the PHATSYS partition and after it had tried to run through several attempts at firmware reupdating everytime I turned the key on.
This is the firmware type that was on the original magazine that was in the player I bought that allowed it to actually play in the truck:
- <firmware>
<long_brand>Nissan-SAT</long_brand>
<headunit_code>0x4800</headunit_code>
<description>All supported models</description>
<type>HU</type>
<model_group>Brand Stereos</model_group>
<years>Version 2.00, Released 4/21/2004. Includes Models:</years>
<image>/images/pm/nissan-sat.jpg</image>
<firmware_version>2.00</firmware_version>
<firmware_date>4/21/2004</firmware_date>
<comment>New binaries. General improvements.</comment>
<headunit_files_url>/files/headunit_0x4800_2_00.zip</headunit_files_url>
<headunit_files_version>2</headunit_files_version>
<headunit_files_date>4/21/2004</headunit_files_date>
<player_files_url>/files/playerfiles_2004_04_21.zip</player_files_url>
<player_files_version>2.00</player_files_version>
<player_files_date>4/21/2004</player_files_date>
<daemon_files_url>/files/daemonfiles_2004_04_21.zip</daemon_files_url>
<daemon_files_version>2.00</daemon_files_version>
<daemon_files_date>4/21/2004</daemon_files_date>
<system_files_url>/files/systemfiles2004_04_21.zip</system_files_url>
<system_files_version>2.00</system_files_version>
<system_files_date>4/21/2004</system_files_date>
<required>Y</required>
</firmware>
I'm going to try to update it w/ newer firmware now beacuse I only have one knob that I turn to go from one song to the next. When I hit buttons 1-6 for the other search types it just jumps to a radio station since it's operating through the XM radio plug on the back of the radio, then I have to cycle the RADIO button a couple times to get back to the Phatbox player. I can get ID3 tag info to come up though by pressing the DISPLAY button but those are the only buttons that are currently available. Now that I have it playing I guess that rules out a blown fuse or faulty wiring to the headunit. Now I just have to figure out if it's the radio or the firmware that's causing it not to operate properly. Any suggestions????
-
Well, it's always possible that the firmware doesn't fully support your HU and that's the extent of the functionality you're going to get. Otherwise, like you said... you can try updated Nissan firmware.
You will want to apply the hack at some time (at which point it was working properly before you began the process of doing so), otherwise once you're all happy it'll work great for a while.. then your original DMS will fail and you'll be all bummed out again.
-
That's true I will be bummed out when it stops working again. I put regular 2.00 firmware on it last night off of the Phathack utilities. I'll try it today and see if it works, if not I'm going to try another OEM radio w/ a SAT button on it to see if splitting up the radio functions allows the SAT preset 1-6 buttons to operate the Phatbox functions. I may even try Nissan 3.00 firmware again now that the audio into the radio has recovered. After that I guess I'll return the DMS to original state and start w/ another radio altogether. At least I got the Phat audio to go into thew radio. I'll let you know if it works today.
-
Oh, I also can't find the firmware you had on it anywhere... it looks like it's different from the normal Nissan firmware - make sure you have a copy somewhere you can copy back manually
-
I ordered 2 different Nissan radios and when they come in I'll be starting somewhat over w/ them to see what firmware will work w/ those radios since my original one doesn't seem to work right w/ any of the firmware available. I'll be in touch.