Today has been a very harrowing, confusing and aggravating day!! This morning I woke up, having finished installing Rockbox 3.1 on a newly DIYMODDED ipod 5.5G. I had also installed an after-market 120gb HD on it. I also have 2 other DIYMOD's here at the moment, one mine and one from another member. all of them were working perfectly yesterday and have been all week; mine for months. I had 3.0 on mine (a 32gb CF modded) the other two are 120gb (as mentioned) and an 80gb. all were ipod videos. I also have another 60gb but thats not here thankfully, because something wierd is going on. Anyway I was installing 3.1 on the 120gb one last night and I had a couple of issues because it was a 30gb logic board (sold to him as a 80gb (64mb memory)), so any time I installed the 60-80gb version, it would install but when I would try and play a file, it would play for a few seconds and then spit static. Once the 30gb version was installed everything was hunky dory (or so I thought) so today I turned it on and realized that the hold switch was stuffed, so I opened it up and fixed it. the switch wasnt fixed in place properly so it wouldnt engage. easy fixed; however when I put it all back together it gave me the sad face icon; after some swearing I opened it up again, checked connections and put it back together....same problem. So I thought i'd try the 120gb in mine, I got the same issue, so I thought it must be software issue. meanwhile I had put my CF card in the 120gb and started it up..... same problem . I swapped the drives back.... same problem, at this point I did something stupid and tried it in the other ipod (not thinking it could be infectious at this stage, just trying to eliminate possibilities ) guess what?

>>>> same problem. I switched all the drives back into their original homes and they all have the problem now. if I connect to my mac to restore, it will mount and tell me that the ipod seems to be corrupted and needs to be restored. when I agree it tries to do it and gets to the wait bar, where it would normally unmount the drive to start the process. but it cant do that because it says the ipod is busy and cant be unmounted. there are no processes running on the ipod except this one. So I try it on the PC and after putting it in disk mode and plugging it in; it flashes momentarily on the 'do not disconnect' screen (just long enough to give a guy hope) and then it flashes straight to the tick and 'safe to disconnect screen'. so one it cant unmount and the other it cant mount and instead just sits there charging without coming up in itunes at all. Either waty my efforts to restore, initialize or reformat are flaunted.
the only thing that these three ipods have in common is that they all had the 120gb drive with rockbox 3.1 installed in them today and directly afterwards; all of them malfunctioned. I know it sounds far fetched, but I think I could have an ipod virus/trojan!!! or some other form of corrupt software that has infiltrated the on-board memory. (dont worry they arent plugged in now LOL)
any ides??? this is really screwing with my chi. all were working perfectly this morning; one on rockbox 3.0 (mine) another with rockbox 3.1 and another that only had the apple firmware installed, but briefly had the 120gb (infected??) rockbox drive installed in it
any ideas guys?? has anyone else actually had a malicious virus infect their ipod or does anyone know odf a rockbox 'bug' that would be causing this on all three ipods.
By the way a DIYMOD in case you dont know is a DIY version of the IMOD; so the line-out is modified and a direct path wired to the dock. then you add caps outside the ipod (higher quality than stock of course) and the signal is passed onto a portable headphone amp. I have done this many times and I have been using rockbox 3 on mine for 5 months or so with no problem, and i'm sure there wasnt any hardware issues before this. all were fine.
by the way guys I do love rockbox and have been a very happy user until today I hope you can help me sort this out. its great software and I really appreciate the efforst you guys go to to keep this moving forward; but I dont know what else couldve caused the problem. and the timing is just too related for all 3