PhatHack
The Hacking Hoedown => PhatBox Hacking => Topic started by: judb on January 15, 2007, 03:52:12 am
-
We have replaced the hackCD with a new set of scripts, linked below, for you to use on your PC (windows 2000 or XP should work)
If you have a Linux / UNIX system these scripts will work for you too we expect with very little change since they are based on shell scripts front ended by bat files for windows... please open a separate thread on Linux usage if you want support, don't clutter this thread up with that.
The steps to hack your phatbox are documented here:
http://wiki.phathack.com/Windows_Hack_Procedure
This wiki article has the consolidated information from this whole thread.
***I STRONGLY SUGGEST EVERYONE HACK THEIR PHATBOX ASAP***
This is so that WHEN your DMS fails you can just create a new one instead of paying for one from phatnoise.
-
Please read this ENTIRE POST before you download the patcher.
Here are two links to the file:
http://downloads.phathack.com/judb/dmsutils-v1.2.1.exe
http://judb.phathack.com/files/dmsutils-v1.2.1.exe
This will extract into a new folder called dmsutils..
There are several batch files in there that you will want to run for various tasks.
-----
backupdms.bat - Does a Backup of your DMS prior to running a hack or building a new DMS.
DMShack.bat - applies the hack files to your original phatnoise DMS. Only good for a working drive.
patchclean.bat - removes the hack files from your original DMS and returns it to normal.
DMSfilecopy.bat - run after you do a patchclean.bat if you want to put some updated tools and kernel on your drive. also works on hacked DMS drives.
*** DONT USE NEWDMS.BAT ON PHATNOISE ORIGINAL DMS DRIVES!!!!***
newdms.bat does not build your drive with the private area keys or partition offsets, its not needed with the updated hacks.
*** DONT USE NEWDMS.BAT ON PHATNOISE ORIGINAL DMS DRIVES!!!!***
newdms.bat - Creates a new DMS for you, or rebuilds a DMS. Extracts phtsys files that were backed up to start seeding of a new DMS.
-----
Lastly, extract and run these scripts from a local drive, like your boot drive (c: for example), don't extract them to your DMS and then want to know why the scripts quit working. :)
Here is a link to the wiki page with instructions that should help everyone out.
http://wiki.phathack.com/Windows_Hack_Procedure
Please read that whole article BEFORE starting and read it as you go. Don't hurry, read the prompts from the scripts and everything should work out fine.
Before posting a reply, please read this whole thread to see if your question is already answered. The issues that have come up since release are covered in the thread and the wiki article for the most part.
-
I would much prefer if we could someday build this into a win32 app instead of having to push out a bunch of files like this. if anyone wants to try and help me do this I would appreciate the assistance. (mostly don't know how to front end diskpar / diskpart or accomplish the same thing in VB / C# etc.)
-
ATTENTION: Volvo users!!
If you have trouble patching your phatbox, you will likely need to download this file:
{Removed, new patcher has both boxes fixes consolidated}
-
I would much prefer if we could someday build this into a win32 app instead of having to push out a bunch of files like this. if anyone wants to try and help me do this I would appreciate the assistance. (mostly don't know how to front end diskpar / diskpart or accomplish the same thing in VB / C# etc.)
I'll have a look at doing this in PhatHack Media Manager, and incorporate it into the DMSManager class.
Judging by the looks of the scripts, it looks like most of it should work fine directly coded into an application.
-
VorTechS, the other option might be some buttons that you can push that launch the bat files in command prompt windows and we just build an installer package that extracts into a sub folder of the PHMM package directories... That way its pretty easy to maintain in bat form until I learn enough VB.net :)
-
I've noticed a few errors in these scripts, I don't think this will be working on any OS...
I'll try to take some notes and be more specific.
-
Sure, There were portions that I couldn't verify myself since I no longer have a box that isn't hacked, however the scripts do properly recreate my DMS on my workstation. Let me know what you see and I'll try to replicate the issue and fix it.
-
DMShack.sh:
Check lines 94 & 99 (wrong filename)
also, on my particular XP install, this script appears to set ${PHTSYS} and ${PHTDTA} to the same drive letter (lines 80 & 81?). Copying Profiles.ini fails.
I am by no means a scripting wiz, but thats what I got. I realize I said 'these scripts', but this is the only one I dug around in.
I take it you haven't written a script to 'unhack' a box? ;)
-
when you say unhack a box.. do you mean return the flash based bootloader to the factory settings where you have to have a phatnoise DMS to operate it, or do you mean remove the hack files from your DMS?
If you mean removing the files, its patchclean.bat.
If you mean restoring the flash, that is not currently possible..
I have updated the files to v1.0.1 and v1.1.1 ... so please give those a shot.
-
Thanks to poptartking the scripts have been updated again and are now at 1.0.2 and 1.1.2 ...
-
I'm giving this a try. Does this include sbinger's patch.sh or does that have to be run seperately?
I thought I had my box patched, but now it is in a loop, and wont recognize the unit. I ran patchclean, and DMSfilecopy. I might try to install first, and if it doesn't work, then try DMShack.bat
If I can get this working I just may not sell it! ::)
-
Anton, I have discovered an issue with these patches that I think may be the cause of many people's issues and am currently trying to fix it. I would hold off for the moment.. I hope to have something done by tonight. It's snowing in Austin TX and that doesn't happen often so I am getting to sit at home with little to do. :)
-
Okay, the fourth release of these scripts has been done. I am 99.9% sure that this will fix most every user who has a new DMS that wont work in a hacked box and an old DMS that does work.. and new users should be good to go if they follow directions.
I've disabled the LBA48 kernel deployment as its caused some issues with the script I think. you can download the file from http://downloads.phathack.com/sbingner/ if you really need it.
As always YMMV and please let me know if you have issues.
If you already ran the hack but want to fix a new drive up, just run the newdms.bat and then when it's done you'll have to load your firmware onto the phtsys partition and start copying music.
-
I found v1.1.3 only at savageguild, not downloads/phathack.
I have issues with neither orig or hack DMS working. although just a short while back the orig worked fine. SHould I start with the hack again, or just try patchclean.bat, and then plug in?
-Anton
-
Try the patchclean script on the original DMS. check the log directory though and look for the patchverify.log and make sure everything says VERIFIED!
The newdms script will need to be run to wipe your new drive and rebuild it.. but it should work after that.
-
Anton, find me in IRC when I'm there and I can try to help you out...
irc.freenode.net / #PhatHack
-
Here are two links to the file:
http://downloads.phathack.com/judb/dmsutils-v1.0.3.exe
http://judb.phathack.com/files/dmsutils-v1.0.3.exe
Jud,
Hi, I'm new to the forum. I'm cautiously preparing to build a DMS, and I downloaded your package and ran the backupdms script. It reports that it cannot find my PHTSYS or PHTDTA volumes.
I'm on a system with the following characteristics:
P4
Windows 2000 Professional, all service packs and updates
2 physical HDDs, C:, D: and G:
2 CD/DVD drives, E: and F:
PHTSYS gets H:, PHTDTA gets I:
Steps:
1. The script is executed without the DMS connected.
***Scanning Currently Connected Disks***
backupdms.sh: command not found: diskpart [21]
backupdms.sh: command not found: diskpart [22]
2. DMS is connected as instructed, H: and I: appear. Press Enter.
***Rescanning Connected Disks***
backupdms.sh: command not found: diskpart [33]
***Rescan Complete***
backupdms.sh: command not found: diskpart [36]
***Determining if new DMS drive is seen***
Error: multiple or no new drives detected. Restarting Script.
Do you have any ideas? Any help is appreciated.
Ken
-
One further bit of info, just to be complete.
I did use the backupdms.bat file, so the folder was added to the Path statement.
Thanks,
Ken
-
where did you extract the files to? I ran my tests with the scripts extracted to c:\dmsutils
I also suggest that you run the bat file from the command prompt instead of through explorer. diskpart should be in the windows\system32 folder as it is included with windows XP, not with our scripts...
-
Okay, here's what I found out:
Diskpart is apparently not included with Win2k Pro. It is part of the Windows Resource Kit. I downloaded diskpart from Microsoft and installed it. It installed to C:\Program Files\Resource Kit.
Me being the crafty little bugger that I am, I copied diskpart.exe to C:\WINNT\System 32.
I had not extracted your kit to C:\dmsutils, so I moved it there. Ran backupdms.bat from the Command prompt (which I HAD done before), and it worked perfectly.
A couple of questions:
1. Can I assume that this backup is a complete backup of a "pristine" DMS? I don't intend to test this, but if my original DMS tangled with a big huge magnet and got completely erased, this backup can be used to rebuild it (sans music, of course)?
2. So I understand that your process actually irrevocably modifies the firmware on the Phatbox, is that correct? I haven't found a post yet that tells me exactly what is changed in the firmware, or if I have found it, I didn't get that particular piece from it. Can you point me to it?
Thanks for your help,
Ken
-
I don't know if there is a specific post that shows you exactly what is changed, but the source code to the flash program utility called phathack is available on sam's download site at downloads.phathack.com if you want to look at it.
Yes it is a non reversible change, at least for us, because currently we can only flip specific bits to disable checks, we are not writing the whole flash image again due to issues with the box crashing when we write data to flash. We haven't figured out exactly WHY it locks up but this process we settled on works pretty darn well.. some people have to run the hack script (the one on the dms by restarting the phatbox twice) to make sure it is all patched up.. but thats what the patchverify.log is for in the log folder on the phatsys partition.
I think a quick summary is it changes the check in the flash based boot loader code to issue a positive pass of:
phatnoise encryption key check (on the hidden area of the first 1 meg of the physical disk, not in a partition)
checks for the ramdisk.sig / ramdisk file matching
checks for the linux / linux.sig matching
etc most of the files in phtsys that have .sig are checked by the bootloader and we patched it to always pass those checks.
-
2. So I understand that your process actually irrevocably modifies the firmware on the Phatbox, is that correct? I haven't found a post yet that tells me exactly what is changed in the firmware, or if I have found it, I didn't get that particular piece from it. Can you point me to it?
from my source code (http://downloads.phathack.com/sbingner/phatpatch-0.5.c):
struct patch_struct patches[] = {
{"make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]",
0x0BB8, 0x0033, 0x1A00, 0x0000, 0x1A00},
{"make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]",
0x0BEC, 0x0026, 0x1A00, 0x0000, 0x1A00},
{"make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]",
0x0C20, 0x0019, 0x1A00, 0x0000, 0x1A00},
{"make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]",
0x0C54, 0x000C, 0x1A00, 0x0000, 0x1A00},
{"make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]",
0x0354, 0x0000, 0x13E0, 0x0000, 0x13A0},
{"make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]",
0x0C80, 0x0001, 0xE350, 0x0000, 0xE350},
{"make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]",
0x0358, 0x0001, 0x03A0, 0x0000, 0x03A0}
};
That shows exactly what is changed if you understand it... it is, as judb said, for all intents and purposes irreversible, but it is innately benign. I personally could reprogram a chip back to factory settings but it would not be fun since it would be constantly locking up on me as I did it. I did this once because I executed a chip erase on my chip to attempt my original programming and had to put everything back on.
-
Thanks, sbingner.
The code is beyond me, but the explanation offered by you and judb was clear.
Would a future firmware update from Phatnoise undo all this?
-
How are we supposed to run the Flash Bootloader Patch? The script is not changing my playlists and after running DMShack it just plays music.
-
it should be using the startup sound entry in the profiles.ini on the phtdta partition under the profiles directory. we swap out that file with a standard hack profile.ini
-
Sorry for this newbie question, but since the original HackCD scripts and images are no longer valid, I'm a bit lost.
Should I run these procedure in order listed:
1. backupdms.bat - Does a Backup of your DMS prior to running a hack or building a new DMS.
2. DMShack.bat - applies the hack files to your original phatnoise DMS. Only good for a working drive.
3. patchclean.bat - removes the hack files from your original DMS and returns it to normal.
4. DMSfilecopy.bat - run after you do a patchclean.bat if you want to put some updated tools and kernel on your drive. also works on hacked DMS drives.
I have a feeling that I should run DMShack.bat on the orginal DMS before runing BackupDMS.bat
Would some guru here write up a simple doc please. And sorry if it's available somewhere already, I've searched but didn't find anything.
Thanks
Tan
-
You should run it in the order listed, which is why it is listed in that order
-
I have a feeling that I should run DMShack.bat on the orginal DMS before runing BackupDMS.bat
Why would you want to do that? The purpose in taking a backup is to protect you in case something goes wrong. If you run the DMShack first, then changes will be made to the DMS and you won't have a backup available if you should need it.
-
Why would you want to do that? The purpose in taking a backup is to protect you in case something goes wrong. If you run the DMShack first, then changes will be made to the DMS and you won't have a backup available if you should need it.
The reason why I thought DMShack should be run before backup is that it'll put some sort of modified sig on the original drive then run Backup to save it to the PC before transferring to the new drive.
Again, I wish someone would write a simple instruction sheet that lists the steps in order. I'll do that if I can get this working.
Thanks for the tips.
Tan
-
Actually, the backupdms script is really not needed but there for safety purposes if someone feels overly worried.
The dmshack script makes copies of every file into the backup folder on phtsys before it copies the modified files in place so there are no changes that are not quickly recovered with the patchclean batch file. I thought it was laid out pretty simply in my original posts about what scripts do what things.
You run dmshack to hack the DMS and you then put the DMS into your phatbox and let the hack run. There are some issues with the hack process that are well documented on the forums if you run into trouble with the hack not finishing.
the newdms script is to make your new hard drive work as a DMS AFTER you've hacked your phatbox with the dmshack script..
you can run the patchclean script to put your old DMS back to original settings.
How much more plain and simple can I spell out the functions of the scripts?
-
We have replaced the hackCD with a new set of scripts, linked below, for you to use on your PC (windows 2000 or XP should work)
If you have a Linux / UNIX system these scripts will work for you too we expect with very little change since they are based on shell scripts front ended by bat files for windows... please open a separate thread on Linux usage if you want support, don't clutter this thread up with that.
The steps to hack your phatbox are:
extract the files into c:\dmsutils
- run DMSHack.bat to modify your DMS to apply the changes to your DMS for hacking the flashed based bootloader in your Phatbox / Keg
- insert the DMS into your box, follow the normal process of allowing the hack to run. check the phtsys\log\patchverify.log afterward to make sure everything says verified. if it doesn't, run the DMS in your box again until it does. if the DMS does not boot up you need to corrupt ramdisk.sig.. search for how.
- after your box is hacked you can run patchclean.bat to remove the hack files from your original DMS
- when you want to build a new larger DMS you can run NEWDMS.bat. this will prep the drive. After the drive is prepped, load your firmware on it via PMM or via downloads.phathack.com and copy your music onto it. enjoy!
- BackupDMS,bat is not required, it is there for folks who are paranoid.
- after you have finished running the hack scripts I STRONGLY suggest making a backup copy of all the files in the c:\dmsutils directory and saving it just in case.
***I STRONGLY SUGGEST EVERYONE HACK THEIR PHATBOX ASAP***
This is so that WHEN your DMS fails you can just create a new one instead of paying for one from phatnoise.
Making the new DMS appears to have worked. The patch.log shows that the patch was successfully applied, but when I bring up Media Manager, it says 'error retrieving DMS id' . How do I get Media Manager to recognize my new (hacked) DMS now?
-
depending on which version of PMM you are using, a hacked DMS may not work properly. What version of PMM are you using?
-
It's the latest version from the phatbox website, 3.92 I think. Is there an earlier version that will work, if so, is there a link to it? It would suck to be stuck with the Music Manager. Media Manager seems to be alot better.
-
Any suggestions for getting a hacked DMS to work with Media Manager 3.92 software?
-
Sam, I think we will need to update the scripts (i'll try and work on it later today) so that it still copies the keys to the drive so this wont be an issue.. what do you think?
I don't have a link to an older version of PMM handy but I know there was a link to 2.30 somewhere on the forums at one point.
-
http://rapidshare.com/files/12574591/PMM_2.30_PHATNOISE_WWW_WWW.exe.html
try that link.. i dont know if it still works.
-
The thing is I think I've seen that NOT happen without keys... and happen WITH keys... *shrug*
it's just a stupid program! :b
-
I didnt see any interface issues on the forum with a hacked DMS, so it was a surprise that the drive actually worked in the car, and not with the software. I'll try the old version and see if it works. What is the difference between 2.30 and 3.92?
-
lots of stuff.. mostly to do with mCD support and video support for the GM phatboxes if I recall correctly.
-
Thank you for all your hard work! I now have 120 GB in my trunk.
I thought it might help to summarize this thread for those in the back, who might be a little unclear on the concepts. I was a little confused trying to fuse the various instructions / hints in this thread with the old visual instructions on the wiki. This process combines the text by Judb and others, and worked for me on my 2003 VW Jetta / Monsoon V upgrade.
Please respond if there's anything wrong in my description here. After a few days and some feedback, I will move this over to a HOWTO in the wiki if no one objects...
- Get the current dmsutils*.exe from http://downloads.phathack.com/judb/ and unzip them to your c:\ drive.
- With your original DMS, run BackupDMS.bat (you might as well) and follow the onscreen prompts.
- With your original DMS, run DMSHack.bat and follow the onscreen prompts.
- Now insert your original DMS into the PhatBox in your car. You need to turn on the ignition and power up your PhatBox. Attempt to play a song, if you hear a message stating your box is patched remove and continue to next step, otherwise wait a couple minutes then remove and reinsert dms and repeat this step once or twice. Please turn off your head unit and wait a bit to see if the lights on the phatbox turn off. (otherwise you may have corruption issues with the log files and have to run chkdsk on phtsys partition)
- After this is done, remove the original DMS from your car, load it into your computer cradle, and check that everything says verified in phtsys/log/patchverify.log. If not, you may need to corrupt your phtsys/ramdisk.sig file (open it in a text editor and put garbage text in the file), and then stick the original DMS in your PhatBox again to force it to finish the firmware update. Search the forum if you need more info about this.
- After all this, you can put your original DMS back in the computer cradle and run patchclean.bat to remove the hack files from the original DMS and set it back to normal.
- Now perform the actual hardware swap (simply remove the four screws on the back of the DMS, carefully swap the hard drives, and screw it all back together).
- Put the new DMS into the computer cradle and run NEWDMS.bat. It will prepare and format your new drive (may take a while).
- Go to http://downloads.phathack.com/firmware/ and download all the latest firmware for your car type.
- Unzip each of the zip files to the root of your PHTSYS drive, copying over the old files in the process.
- You may now want to load up some test music with Phatnoise Music Manager.
- Finally, take your new DMS out of the cradle and put it in the PhatBox in your car. Let the system run for a while (allow the green light to finish blinking). Then start up your head unit and try to play some music. Hopefully everything will work.
- JudB suggests: After hacking, back up the c:\dmsutils folder. Also, don't do anything with your old drive (like turn it into a mini external HDD) -- you may need the original some day.
Again, thanks for all your help and hard work. It's hackers like you guys that make the world go round...
N
EDIT: Correct some misleading info - sbingner
-
- Now insert your original DMS into the PhatBox in your car. You don't need to turn on the ignition -- unless the PhatBox doesn't power up on its own -- you should hear the quiet whirr of the hard drive and see blinking lights on the front of the PhatBox. Let the system run for at least five minutes, or until the green light stops blinking. The firmware on the PhatBox itself is being updated.
This part is incorrect. You have to turn on the headunit and select the Phatbox as the source (as I just learned the hard way). It only runs the patch when it is active.
-
I have created a new page on the WIKI (http://wiki.phathack.com/Windows_Hack_Procedure) that outlines this procedure as I understand it (leaving out all the random flailing around that I experienced). I'm sure there are items that could use correction/clarification/expansion, but I think it's a good starting point and might help eliminate a lot of the questions people have.
-
I am under the weather, again, so I'm not going to attempt it today, but it should be really simple to fix the DMShack script from overwriting files if they already exist in the backup folder... I didn't think about that when I was working on these and I don't think it crossed Sam's mind either.
Really though there shouldn't be any reason to run the hack script more than one time if people follow the instructions properly, I think. Could be wrong there though.
Also we are talking about merging the versions and just using the newer patcher for everyone. maybe we'll do another release later in the week if we have time to iron out the changes to the patcher and the scripts.
Thanks for the wiki page, I'll add a link to it in the first post.
-
New patcher released today for both volvo and non volvo phatboxes / music kegs.
Version is 1.2.0
This set of scripts includes some updates so that if you run the hack more than one time it will not overwrite the backed up files and it will recreate the bootload.log to default so you can verify the box is booting properly.
phatpatch version 0.8 has been added. We hope this will help more with patching stability. Time will tell.
-
depending on which version of PMM you are using, a hacked DMS may not work properly. What version of PMM are you using?
Are there known versions of PMM (still available!) that work with hacked drives?
I'm assuming there must be, as I doubt everyone who has hacked is doing all DMS updating manually.
-
Making the new DMS appears to have worked. The patch.log shows that the patch was successfully applied, but when I bring up Media Manager, it says 'error retrieving DMS id' . How do I get Media Manager to recognize my new (hacked) DMS now?
I just tried Media Manager 3.30 with a newly hacked 120gb Samsung 5400rpm drive and it has worked for me.
File split into two...use file joiner after downloading
Use HJSplit freeware
http://www.freebyte.com/hjsplit/ (http://www.freebyte.com/hjsplit/)
http://rapidshare.com/files/29289655/PMM_3.30_setup.exe.001 (http://rapidshare.com/files/29289655/PMM_3.30_setup.exe.001)
http://rapidshare.com/files/29301058/PMM_3.30_setup.exe.002 (http://rapidshare.com/files/29301058/PMM_3.30_setup.exe.002)
-
Hi - I just purchased a used phatbox and expect to have it in a week or so. I'd like to pick up a 160GB drive, and reading back on this thread, it looked like 160GB drives were working, but then I saw the below:
I've disabled the LBA48 kernel deployment as its caused some issues with the script I think. you can download the file from http://downloads.phathack.com/sbingner/ if you really need it.
Does the latest release of the files (as of July 2007) support 160GB drives as is, or do I need to snag the LBA48 file? It's not clear to me.
Thanks,
-db
-
you'll need to snag the file yourself. I was having issues detecting if it needed to be installed or not because windows is a Pain In The Neck for scripting sometimes.
-
you'll need to snag the file yourself. I was having issues detecting if it needed to be installed or not because windows is a Pain In The Neck for scripting sometimes.
Got it - THANKS!
-
http://rapidshare.com/files/29289655/PMM_3.30_setup.exe.001 (http://rapidshare.com/files/29289655/PMM_3.30_setup.exe.001)
http://rapidshare.com/files/29301058/PMM_3.30_setup.exe.002 (http://rapidshare.com/files/29301058/PMM_3.30_setup.exe.002)
[/quote]
Does anyone else have access to 3.30? The rapidshare site isn't allowing anymore downloads of part 2.
Or is 3.92 okay for hacked drives?
-
im using 3.92 just fine on my hacked drive.
-
Does anyone else have access to 3.30? The rapidshare site isn't allowing anymore downloads of part 2.
Or is 3.92 okay for hacked drives?
I think you just hit the download limit for rapidshare. For free downloads, it makes you wait a couple of hours between large files. Try again.
-db
-
im using 3.92 just fine on my hacked drive.
Thanks, that's a relief!
Now I just need to backup my drive for safe keeping.
-
what does dmsfilecopy.bat/.sh do?
the original instructions say it should be run an a new or hacked DMS drives.
mine was hacked with the hack cd. do I need to run this to update/fix something?
so what does it do exactly?
-
if you already have a hacked box, don't sweat it. this is just a redo of the CD method that works under windows and has a different process than the CD method.
-
phew. thats a relief. I just wanted to make sure i wasn't missing out on any new features.
my hack'd box is doing great! I went from a 20gig to a 120 gig. which has a larger buffer and a lower power consumption.
thanks guys for all the hard work.
-
First off, let me tell you that I am a complete newbie... I have been reading your web site for a long time and had a few coupons I needed to use at Best Buy, where I picked up a 160 gig Seagate Ultra ATA/100 hard drive. I have read through the instructions for hacking, etc... I think I am almost ready to go. With the exception that I just read through the topic of 160 gig drives, and am wondering, will it work? I haven't been able to locate a clear answer, but is there something special I need to do to use the drive? I really only have about 60 -70 gigs of music, so at this point, if the entire drive is not used, it is not a big deal, but if I can set it up to be able to do that from the beginning, that would be great.
Also, I read something about the Media Manager software not working with a hacked drive... However, when I use the Music Manager, it doesn't seem to recognize the mp4 files I have switched to instead of mp3. In Media Manager, all of my mp4s are recognized, etc. Will I have a problem with this going forward?
Any advice you provide would be fantastic. I am very excited to give this a shot. I work in technology, but this is the first time, besides adding a drive or something to my computer, where I am actually digging into something...
Thanks.
Dippdy
-
Disregard my question about 160 gig drive... I posted before and forgot and found my answer... Thanks!
-
Can I just pay somebody to do this for me.....then send me back whatever I will be puttin in my Phatcradle and Phatbox?
-
Why not use my DMS tools? They're easy to use...?
If they don't work first time, it's because you may need to run the newer version, which I'll look to release on Friday.
-
when you say unhack a box.. do you mean return the flash based bootloader to the factory settings where you have to have a phatnoise DMS to operate it, or do you mean remove the hack files from your DMS?
If you mean removing the files, its patchclean.bat.
If you mean restoring the flash, that is not currently possible..
I have updated the files to v1.0.1 and v1.1.1 ... so please give those a shot.
So is it possible to unhack a Hacked DMS and PB?
-
there is no such thing as a hacked DMS -- and reverting the hack on the phatbox is VERY difficult. The hack does nothing that has any POSSIBILITY of harming your phatbox though, so that's not a problem.