I went through the patch process with the BootCD v. 1.5
Everything was working fine until the last step, Copying to new DMS.
I'm not sure what is going wrong. I have tried the process before but had no success, so I decided to start over using the same HDD and original DMS.
I've already run the dd comand on this HDD before starting over, if that makes a difference.
Please tell me what information I need to post.
Thanks
I propose searching around.. lots of folks have had issues with the VW hacks. its either the ramdisk.sig or bad partition info about 90% of the time it seems.
I've tried this before with the same HDD. I didn't receive a failed to copy error, but the drive would not play in the Phatbox. I followed other instructions for VW/Audi hacks... using the dd command, etc... no avail. So I was using the original DMS for a while. I decided to try again.
Would having run those dd commands on the HDD have any affect when starting the process over? Could it be interfering with this hack attempt?
On the original DMS, there is a bootload.log file, but the file is empty. No text when I open it. I never heard a success sound when applying the patch. I'm not sure the ramdisk.sig fix will work.
Here is the bootload from the new DMS, which failed to copy.
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful
I just updated the firmware, because I think I had the latest firmware, but the wrong box. I updated that, and I'll try the patch and copy again...
the bootload.log looks good from that DMS.. there should be another log file in the root of PHTSYS .. can you post it too? things should be working. have you tried renaming your plugin folder?
please disregard the above posts, since I started over.
Ok, I started over. Updated the firmware on the original DMS. Ran the patch disc, Then I applied the patch, and the 'Phatbox is unlocked' message played this time.
Then I switched the HDD and copied to the new DMS. OK!
Something wasn't right, music wasn't copying to the new DMS in PMM (media manager) Should I be using Music manager instead?
I did the 'dd' command according to instructions from Genesis. There was a bad partition... Then I loaded the new DMS with phatnoise firmware.
My headunit says to 'Check Magazine' and it doesn't play the one song i loaded :-/
DMS doctor says there is no M3U playlist... :(
After sync the DMS, Everything is added to the HDD, but does not show in PMM :-[
You mentions about changing the plugins folder somehow... I can't find a plugins folder!
Here is the bootload.log from the original DMS
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful
This is box_id_log.txt
Unique ID: 0xc4f61a90
Random ID: 0xc4f61a90d76c1fa39e04358e131da1e9
CPU: EP73xx, ver 0x02
Lot Code: 0x3101
%
What is going wrong here.
Should I try to corrupt the ramdisk.sig file?
the bootload.log shows that your phatbox is booting fine.. after that theres another log file created, I not at home so I can't find the file name easy.. but if you search for rc pairs you can get an level 10 debug rc.sh and rc.sig to copy to the phtsys partition and try booting that way.. it should help figure out whats up.
I imagine its a filesystem / pmm issue.
Ok, sorry to be so long in responding.
I put the level10 rc files into the phtsys partition.
Then i put the DMS in the Phatbox, tried to boot...
I can't find any log file. Either on Phtsys or Phtdta.
When I turn on the Radio,Phatbox, Both lights light up for a few seconds (10) then a beep, and Chk Magazine on the headunit.
A couple things differing between new and orig. DMS. Now has profiles.ini in phtsys instead of phtdta. Also, there is a file named forceupdate on the new DMS.
judb,
I read where you say that bootload.log does not auto create itself. So should I put a file on the new Phtsys called bootload.log for to be written to?
Also some files missing from the new DMS in the Phtdta partition are:
PnaActPack
Reserved.dat
These 2 are not on the new DMS.
ran chkdsk, and found no errors.
bootload.log needs to be user created. make a copy of one of the ini files on phtsys and rename it bootload.log
when the system boots it will detect the file and replace the contents with the log output.
I don't know about reserved.dat for sure but the PNAACTPAK seems like an audible file to me. you can copy them off the other DMS if you want but I doubt that is why you are having issues. Everything you should need to run the phatbox would be in the files you extract for your "firmware" (the 4 zip files for that)
Ok, followed your instruction, here is the bootload.log file
[PhatMan]
enable_voice_prompts=1
DMS_DB_version=2
MakeVoicePromptForTitle=0
enable_cover_art=0
SaveVersion3DB=1
remove_leading_articles=1
album_sort_v3_mode=1
create_mode_change_sql_tables=0
allow_v3_aac=0
allow_mpeg1_2=0
allow_ac3=0
allow_above_2gb=0
hmm, nope that isn't the bootload output.. either the file you used was not big enough (try to find one that is around 4k in size at least) or the system isnt booting at all.
Ok, The file wasn't big enough, Now it is really big!
[Phatbox]
modification=1
announce=0
kenwood_digits=2
track_display_250=0
pioneer_99_digits=0
ssa_use_disc_up_down=0
ssahelpfile=/dos/tts/se_help.mp3
list_title_text=%m%n: %t
bad_album_db=on
alpha_file_ext=mp3
sleeptime=300000
bc.0100=6
bc.0101=0
bc.0108=0
bc.010c=0
bc.1102=0
bc.1201=0
bc.1301=1
bc.1302=1
bc.1303=1
bc.2103=0
bc.2104=0
bc.2201=1
bc.2202=1
bc.2203=1
bc.2204=1
bc.2205=1
bc.2206=1
bc.2207=1
bc.3100=1
bc.3101=1
bc.3102=1
bc.3201=1
bc.3202=1
bc.3301=1
bc.3302=1
bc.3401=1
bc.3402=1
bc.6101=1
fw.2200=BMW
fw.2900.*.0000=Honda_DiscUpDown
fw.2900.*.0001=Honda_6Button
fw.3400=Becker
fw.3402=Becker
fw.3800=Volvo
fw.3950.4.0000=VW_Non_Premium6_v4
fw.3950.4.0001=VW_Premium6_v4
fw.3950.4.0002=Audi_I_v4
fw.3950.4.0003=Audi_II_v4
fw.3950.5.0000=VW_Non_Premium6_v4
fw.3950.5.0001=VW_Premium6_v4
fw.3950.5.0002=Audi_I_v4
fw.3950.5.0003=Audi_II_v4
fw.3950.6.0001=VWAudi_v6_3
fw.3950.6.0002=VWAudi_v6_5
fw.3950.6.0003=VWAudi_v6_2
fw.3950.6.0004=VWAudi_v6_3
fw.3950.6.0005=VWAudi_v6_1
fw.3950.6.0006=VWAudi_v6_2
fw.3950.6.0007=VWAudi_v6_2
fw.3950.6.0008=VWAudi_v6_6
fw.3950.6.0009=VWAudi_v6_2
fw.3950.6.000a=VWAudi_v6_2
fw.3950.6.000b=VWAudi_v6_2
fw.3950.6.000c=VWAudi_v6_6
fw.3950.6.000d=VWAudi_v6_2
fw.3950.6.000e=VWAudi_v6_3
fw.3950.6.000f=VWAudi_v6_4
fw.3950.6.0010=VWAudi_v6_2
fw.3950.6.0011=VWAudi_v6_3
fw.3950.6.0012=VWAudi_v6_4
fw.3950.6.0013=VWAudi_v6_3
fw.3950.*.0001=VWAudi_v7_3
fw.3950.*.0002=VWAudi_v7_5
fw.3950.*.0003=VWAudi_v7_2
fw.3950.*.0004=VWAudi_v7_3
fw.3950.*.0005=VWAudi_v7_1
fw.3950.*.0006=VWAudi_v7_2
fw.3950.*.0007=VWAudi_v7_2
fw.3950.*.0008=VWAudi_v7_6
fw.3950.*.0009=VWAudi_v7_2
fw.3950.*.000a=VWAudi_v7_2
fw.3950.*.000b=VWAudi_v7_2
fw.3950.*.000c=VWAudi_v7_6
fw.3950.*.000d=VWAudi_v7_2
fw.3950.*.000e=VWAudi_v7_3
fw.3950.*.000f=VWAudi_v7_4
fw.3950.*.0010=VWAudi_v7_2
fw.3950.*.0011=VWAudi_v7_3
fw.3950.*.0012=VWAudi_v7_4
fw.3950.*.0013=VWAudi_v7_3
fw.3950.*.0014=VWAudi_v7_3
fw.4700=Nissan
fw.4800=Nissan_SAT
fw.0801=Visteon
fw.0802=Visteon_SSA
fw.0e74=Toyota
fw.0a00=Pioneer
fw.02ff=Kenwood_v12
fw.2680=Chrysler_Class2
fw.2e00=Mazda
menu.wait=5
menu.0.numitems=6
menu.1.text=Feature Menu Help
menu.1.audio=/dos/tts/it_help.mp3
menu.1.action=PLAY:/dos/tts/se_help.mp3
menu.2.text=Enable Extra Voice Help
menu.2.audio=/dos/tts/it_extra_help_en.mp3
menu.2.action=VPON:/dos/tts/se_extra_help_en.mp3
menu.3.text=Disable Extra Voice Help
menu.3.audio=/dos/tts/it_extra_help_dis.mp3
menu.3.action=VPOFF:/dos/tts/se_extra_help_dis.mp3
menu.4.text=Randomize All Mode
menu.4.audio=/dos/tts/it_rand_all.mp3
menu.4.action=MAGRANDON:/dos/tts/se_rand_all.mp3
menu.5.text=Randomize Current List Mode
menu.5.audio=/dos/tts/it_rand_cur_list.mp3
menu.5.action=MAGRANDOFF:/dos/tts/se_rand_cur_list.mp3
menu.6.text=About This Firmware
menu.6.audio=/dos/tts/it_about.mp3
menu.6.action=FIRMWARE_VERSION
;Already in SSA mode
audioid.0.0=TITLE
audioid.0.1=PLAY
audioid.0.2=WAIT 5
audioid.0.3=END
;Switch into same SSA mode
audioid.1.0=/dos/tts/beep2.wav
audioid.1.1=CURRENT
audioid.1.2=TITLE
audioid.1.3=PLAY
audioid.1.4=WAIT 5
audioid.1.5=END
;Switch to different SSA mode
audioid.2.0=/dos/tts/beep1.wav
audioid.2.1=BROWSING
audioid.2.2=CURRENT
audioid.2.3=TITLE
audioid.2.4=PLAY
audioid.2.5=WAIT 5
audioid.2.6=END
;Track Audio ID
audioid.3.0=/dos/tts/beep3.wav
audioid.3.1=PLAYLIST
audioid.3.2=ARTIST
audioid.3.3=ALBUM
audioid.3.4=GENRE
I skipped forward to my Radio Type...
[VWAudi_v7_1]
auto_pong=on
menu.wait=5
menu.0.numitems=64
menu.1.audio=/dos/tts/it_help.mp3
menu.1.action=PLAY:/dos/tts/se_help.mp3
menu.2.audio=/dos/tts/it_extra_help_en.mp3
menu.2.action=VPON:/dos/tts/se_extra_help_en.mp3
menu.3.audio=/dos/tts/it_extra_help_dis.mp3
menu.3.action=VPOFF:/dos/tts/se_extra_help_dis.mp3
menu.4.audio=/dos/tts/it_about.mp3
menu.4.action=FIRMWARE_VERSION
menu.5.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/a.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.6.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/b.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.7.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/c.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.8.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/d.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.9.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/e.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.10.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/f.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.11.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/g.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.12.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/h.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.13.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/i.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.14.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/j.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.15.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/k.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.16.action=PLAY:/dos/tts/it_radio_type.mp3;PLAY:/dos/tts/l.alpha.mp3;SLEEP:5;PLAY:/dos/tts/it_radio_type_help.mp3
menu.17.act
right but did you copy the file as bootload.log and then put the DMS into your phatbox? it should look like
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful
see http://wiki.phathack.com/Bootloader_FAQ for more details of the bootloader and bootload.log
OK, What I did was copy the Phatbox.ini file into the phtsys. Renamed it bootload.log. Apparantly, it did not boot at all, because this log is the same as phatbox.ini
So now what?
I should note that both lights on the phatbox turn on for about 30 seconds, then off, BEEP, and then both on again. Unit then switches to radio signal
I did some more...
Ram DMS doctor on the original DMS, got this message:
Checking for system files: Fail: MD5 Checksum Failed |:\aadec.sig
I put the level 10 rc files on the Original DMS, and booted the box with it.
bootload.log looks the same.
there is a long file colled logfile.txt
also a folder named log with 5 logs in it... patchverify, patch, logshere.txt, dmesg, and patchwrite
Should I post one of these?
Thanks for the help, judb
is this the original DMS we are working on?
I would FORMAT the phtsys partition and download the firmware files by hand from http://downloads.phathack.com/firmware/
and extract each into the phtsys partition.
remove the forceupdate and forcesettings files from phtsys after extracting these zip files.
you can backup the contents of the phtsys in a zip file prior to format if you want to.
then recreate the bootload.log file and deploy your rcpairs for level 10 logging and see what happens.
I did what you said to on the Original DMS. There was no forcesettings file, just forceupdate.
bootload.log
BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful
there are four other files that were created.
box_id_log.txt
box_id_mru.txt
logfile.txt -- This is a big file
error_log.txt, which says: CORRUPT_FILE: /dos/Music/flactemp.flac
I'm not sure why the new DMS isn't working, but I cannot get a bootload.log file on it. Like you suggested, It could be a filesystem/PMM problem.
I have PMediaM, and PMusicManager. It seemed that the files were copying to the new DMS in Music Manager, but then would not save/Eject DMS. Original DMS still works fine.
Alright, I've narrowed it down, but I'm not sure how to proceed.
New DMS does not boot in the patched box.
DMS Doctor says:
checking for system files- Fail: could not load XML Document
Checking for Profile & Playlists- Fail: No M3U playlist signatures Found
So I check the file caled DMSPlaylists.xml in PHTDTA:
1.79 KB in original DMS
1.59 KB in new DMS
Is this the file giving me problems?
well you could try copying it over from the working drive... although nothing we do should touch that file. hmmm. it also sounds like pmm isn't signing your playlists on the phtdta parition based off that error
Quote it also sounds like pmm isn't signing your playlists on the phtdta parition based off that error
Could have something to do with this... Before the Hack, I was using the wrong firmware for my box. I had selected the Platinum Edition Phatbox, instead of the VW/Audi box. Although it was working in my box, I did switch back to the VW/Audi firmware as soon as I noticed the mistake.
Ghost won't do what I want it to (trial version), and I don't have Powerquest Drive Image. Perhaps I will try to switch the firmware around. I know others are running various firmwares. Is there a danger to the headunit?
There is no issue that I know of if you load the wrong firmware, it just may not play until you load the correct one.
the flac file that is mentioned as corrupt is how we trigger flacplay script execution which has been replaced by our scripts to flash the firmware bootloader. you can remove that error by editing the ini file under profiles on the phtdata partition. just remove the startup sound path and you are good to go.
I think the firmware selection has nothing to do with the DMS not working. its booting fine, theres just nothing in the database for it to play / playlists. you should delete the profiles folder in my opition on phtdata and all the db files out of the root of the phtdta drive, run chkdsk too, then try making a playlist with one set of songs on it and save / eject the dms to see if it plays.
Hi i was trying to create another dms.
I used the DMS HACK and REPAIR CD posted.
Everything was going fine. I went to the car to insert the original dms to hack the phatnoise. Heard the message the system is now hacked ...
When i came back to my computer to continue with the processes and swap the hard drive inside... horror!!! my wife had rebooted the computer.
What must i do know that i cannot continue with the process.
Thanks in advance
just re-run the process and skip the portion where you go to the car... it doesn't hurt anything.
thanks i'll do that and will let everybody know
Ok i did it this morning but still have one problem
I was able to hack a new drive upload new music with music manager
But when i insert the dms into my phatbox, i get a NO MAGAZINE error message
If i use the original dms, it always start by a a message saying that my system has beeen unlocked.
Ok everything is fine now.
I used the Genesis method and it worked.
Thanks guys ;D :P
Glad it worked for the ecb5,
Ugh, I did the genesis method (dd command) and still cannot get it to work. I am getting the No magazine message from head Unit. Original DMS still works.
This is all my process
I used the latest automatic hack cd
started the hack
removed the original dms to hack the phatbox
Because my wife had rebooted my computer mean time, i had to start all over
after repeating the first steps, swapped the drive
continued with the copying part.
went to the car but it didn't boot ( flashed one long, 5 shorts, 11 shorts, continuesly)
swap to the original but it kept on hacking the phatbox everytime i started the car
uploaded the original with the latest firmware and original worked fine but no boot with hack dms
used genesis method and the first time i turned on the radio, the hacked dms didn't work but the second time it did.
QuoteThis is all my process
I used the latest automatic hack cd I used v 1.5, i think it is the latest.
started the hack
removed the original dms to hack the phatbox
Because my wife had rebooted my computer mean time, i had to start all over
after repeating the first steps, swapped the drive
continued with the copying part.
went to the car but it didn't boot ( flashed one long, 5 shorts, 11 shorts, continuesly) Turn off the radio before removing, i guess
swap to the original but it kept on hacking the phatbox everytime i started the car This is just the startup sound being replayed[/b]
uploaded the original with the latest firmware and original worked fine but no boot with hack dms Did you use PMM to upload the firmware, or the files from Phathack?
used genesis method and the first time i turned on the radio, the hacked dms didn't work but the second time it did. Did you leave the DMS in the box, or take it out between tries?
QuoteQuoteThis is all my process
I used the latest automatic hack cd I used v 1.5, i think it is the latest.Yes that's it
started the hack
removed the original dms to hack the phatbox
Because my wife had rebooted my computer mean time, i had to start all over
after repeating the first steps, swapped the drive
continued with the copying part.
went to the car but it didn't boot ( flashed one long, 5 shorts, 11 shorts, continuesly) Turn off the radio before removing, i guess Yes i did turn off the radio before removing the dms
swap to the original but it kept on hacking the phatbox everytime i started the car This is just the startup sound being replayed[/b] Everytime i started the car the prompt saying i had unlocked the phatnoise played.
uploaded the original with the latest firmware and original worked fine but no boot with hack dms Did you use PMM to upload the firmware, or the files from Phathack?Yes i did use PMM
used genesis method and the first time i turned on the radio, the hacked dms didn't work but the second time it did. Did you leave the DMS in the box, or take it out between tries?Left it in the phatnoise and turned off the radio once. Turned on again and it played
That quote from ECB5 is very hard to read.. can you edit your post and clean that up so it isn't just a quote?
Sorry, didn't realize how hard it was...
to answer last Anton questions...
Yes that's it that is the the cd hack i used
Yes i did turn off the radio before removing the dms after it failed to boot
With the original dms, Everytime i started the car the prompt saying i had unlocked the phatnoise played.
Yes i did use PMM to upload the firmware to the original dms
I left the hacked dms in the phatnoise and turned off the radio once. Turned on again and it played
Now that my new dms has been working fine for a couple of weeks, i was wondering if i can format the original dms and use it in my laptop?
If in the future i would like to set another dms can i do it with the hacked one?
TIA
There is a way to set up a new DMS with the hacked one. It involves the dd command, and I don't know the whole process. I believe you will need the Original DMS to set up the Box to run unassigned drives.
Look around there is more info here in this section.
Be careful!!!! :o
You really should try to keep your original DMS available. If you ever need to hack another Phatbox, you will need your orginal DMS to do it. If your current box dies, and you have reused your disk in a laptop, you have no chance to hack a replacement box unless you also get another original DMS.
It is possible to archive the DMS signature and resore it back later using dd (you must restore to the same physical disk drive if you want it to work in an unhacked Phatbox), but given the low cost of laptop drives these days, I would say it is really not worth the risk unless you are desparate.
You could still use the HD in an external enclosure, just don't change anything. Use whatever space is left to store whatever you need. Put it in PHTDATA, where the music would normally be...
QuoteYou could still use the HD in an external enclosure, just don't change anything. Use whatever space is left to store whatever you need. Put it in PHTDATA, where the music would normally be...
Thanks guys.
That its true, it's only 20gb
I will do what anton says.
I will erase all mp3 and create a folder in phtdata to store stuff using a usb cable and the enclosure my hacked hd came in.
Thanks again.