Dead Player wont power up after fw upgrade

zacspeed · #1 (**permalink**) 9th Oct 2006, 11:08 am

To start with I had the same problem as many others here have had with the Players. I was unable to upgrade the firmware and it wouldnt recognise my device and thanks to Tadad his advice helped me overcome that.
Now I have upgraded with version 3.2.xxx firmware when I know I should have used 3.5.37 fw and after I upgraded the screen flashed for a while and now its blank. The screen now doesnt power up and I cant do anything to power it back up. I tried shorting the chip out with tweezers but it is no longer recognised.
What can I do to solve this?

tadad1 · #2 (**permalink**) 9th Oct 2006, 4:43 pm

zacspeed, "ok1" found that shorting the cpu chip fixed the problem for him. I have not tried it myself. Also connect to another USB port, one you have not used the player on before if possible.
Also If you have shorted your player before and it has been recognised as an adfu device and your player has gone to recovery mode Windows may remember the device and give you no notification of connection so after shorting try the upgrade tool to see if it detects the device.

zacspeed · #3 (**permalink**) 9th Oct 2006, 8:33 pm

Hi Tadad,
Thanks for your help,
I've tried all those suggestions. It just simply isnt responsive anymore.
Ive tried varying USB slots and shorting out different areas of the board.
My pc recognises another player that is functional but not mine.
Im at a loss now.
It's like its dead now as i get no response, no display picture but its only been doing it since I tried upgrading with 3.2.xx firmware.
Any ideas?
Many thanks

tadad1 · #4 (**permalink**) 9th Oct 2006, 9:05 pm

zacspeed,
If it is cactus, I doubt if it is due to the firmware it is more likely a component failure. But some times they can be stubborn to reset. The other thing that I have done on occassion is to connect the tweezers across the chip from side to side and drag them across all the pins. I doubt if this is a good thing to do but I have not killed a chip yet but do this at your own risk.

zacspeed · #5 (**permalink**) 9th Oct 2006, 9:31 pm

Yeah ta,
Im starting to think theres nothing else that can be done.
Im sure its not cactus as it happened immediately after the firmware upgrade to 3.2 when i should have only used 3.5
I'll keep persisting, but the lesson learnt is if it aint broke dont fix it.
Just was hoping to get the flashier features as some other 1s did.
oh well.
thanks again