If I couldn't boot the device, A windows machine in a perfectly working state couldn't recognise the device, and my Linux laptop (arch linux, configured from scratch) could not recognise the device, how could I have wiped the device? I'm not a stranger to tinkering either - I previously owned a Sony Ericsson phone, which I flashed and configured to run Walkman firmware. I flashed a PSP for custom firmware, recently set-up a personal home file and media server running Arch Linux. But for this one I'm stumped. And I'm quite frankly sick of trying. I could ask for a replacement from PLAY.com, but eventually they'll start asking questions about why they keep breaking. Questions that I seriously cannot answer. And so, they'll refuse to refund or replace the P3 - In which case, I'll be £100 down. A £100 that I could have saved to spend on a different device.

So you see my problem.
I really do wish the P3 worked for me - I found it a beautiful device, even pitched up against my friends Cowon S9 - I much preferred the P3. And he admitted, that he kind of did too, apart from the S9's AMOLED screen (which is stunning, btw).

I got the problem on two different P3. The first one was returned to the shop, the second is between my hands...
I am going out for a week, but I will definitely investigate the problem. Hardware failure or firmware problem.

It happened when I tried to load more than 20GB at once in my 32GB P3 player.

You cannot load more than 20Gb on your mp3 player in one go and then complain because it broke.
That's not recommended on any mp3 player!! That is a challenge for the library!
If it still works, okay, you're lucky, but if it breaks, that's your fault

I loaded quite a bit of music on my P3 and had no issues, and I do it all the time - I did it with the Cowon S9 as well. The player has no real issue with this AFAIK, and it's not something people should be warned about.

Exactly the same problem was with my YPT9. Some mp3 tags (in russian) were the issue.

The device locked up during library update and was unable to boot up correctly afterwards. But it was possible to unplug it, reset and reconnect to the pc before it boots up - it went to UMS mode and it was possible to delete the "corruppted" mp3`s.

sad that nothing changed since than, Samsung should consider such issues.

this is one of them moments where a compatable version of FWDN would come in handy (samsung? Will you help?),

For advanced people:
Use the dissassembly guide to get inside the player,
try disconnecting the battery for a day then re-connect,
Power up,
if this fails, return...

For the hacker(-ish) people:
try battery method or next method:
This assumes that samsung has left debug code in their firmware...
Open up player using the guide,
There is a (likely serial)debug port next to the button/speaker connector inside the player,
find out which pin is which (should be similar to P2's, but i don't trust),
hook debug port to com port and ssh/telnet/hyperterminal into the port,
hold down reset,
attach usb to p3 and pc,
press power and release reset before releasing power
see if you can get a reading from debug port via ssh/telnet/hyperterminal,
If not, try inserting a 'newline' or 'carriage return' character to the port,
if there is still no response then I wont be able to help further,
if there is a response, please upload the response(s) even if they don't seem important(thanks in advanced).

i hope this fixes the problem, or that any info gathered helps fix the problem,
else it's likely dead/defective hardware.

I'm furious. I plug it in to update music, or re-sync songs aftering update their ID3 tags. It goes okay. I disconnect. It says it's updating the library. Then - Nothing. No reset, doesn't charge. Just a black screen, and reset button that obviously does nothing, even when I hear the click.

The first one I sent back to play.com who replaced it, eventually. But after this, I'm sick of it breaking.

Anyone have any idea on how to fix this? If not:

What else is there in the market? Cowon S9 - a bit too expensive, and it uses mainly MTP (I'm on linux - dodgy compatibility there). Ipod Touch - wouldnt touch it with a barge pole tbh. Samsung P3 - ehm, no thanks.

Ideas?
Thanks.

Sorry to hear that - the same happened to me last Saturday. My player was 1 week old then and before it worked perfectly well. I contacted Samsung-support, but all they said was, that I should return it - so I do now.

However I'm using a SanDisk Fuze player with the same machine and there never was any similar problem like that with Samsung. So I guess it has something to do with the player itself...