- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Check the connections on both ends to make sure they are attached securely. If the MP3 player is still not recognized, go into the player settings and change the Online Device from Media Device to USB Disk. Use a different USB cord if you have one because it could be broken and not allowing your computer to recognize it.
connect the device to a different USB port on your computer. If the MP3 player is still not charging, plug it into a wall charger. Try charging the Coby device overnight. If it still will not charge, the battery may be bad and you'll need to contact Coby for assistance
when that happened to me i plugged it into the BACK USB port of the computer and let it charge for three hours it sould be fine
no clue y the back works and the front doesnt when that happens but it does :P
Try plugging your device to the USB port in the back of the computer. On older computers, the front USB ports are USB1 while the ones in the back are USB2, and I've seen it happen when some devices would go completely unnoticed if they were plugged into USB1.
If that doesn't help, try plugging it into a different computer. If that computer also doesn't recognize it, the problem may lie in the device.
Hi. My Inovix mp3/4 player suffered a similar fate when it crashed during a Firmware reload. The player went completely dead and wasn't even recognised by the computer when plugged into the USB port.
I basically kept on trying - a couple of times whenever I used the computer - using different ports.
2 days later - 'ding-dong' - Windows XP suddenly recognised something was in the port, and I tentatively attempted a Firmware reload.
Success! (Don't ask me to explain it tho'...)