PDA

View Full Version : performed wrong upgrade process - D2 hosed


BluewaterRocket
05-25-2007, 12:26
With 21 years in the software industry you'd think I'd be able to follow simple upgrade instructions for 2.46. Unfortunately for me a couple distractions were enough to mistakenly use the pre-2.41 install process on my 2.41 configured D2. I loaded and rebooted with the D2.bin file from the 0 folder instead of the 1 folder. When I reconnected to my PC I got the white screen, was able to navigate to the root directory, but could not copy to or delete anything from my D2. Powering up the D2 without a usb connection to the PC results the familiar startup screen with 0.00 displayed as the version followed by a white screen.[confused]

Any ideas on how to remedy this situation? I couldn't find Cowon's support e-mail, is it support@cowonamerica.com? Don't suppose they have a support phone number?

Any suggestions welcome.

ETA- Found the support site on cowonamerica - submitted a ticket for the problem.

doniago
05-25-2007, 13:13
Please don't make consecutive posts if you can just edit your original post to include the additional info.

Thank you.

M4psycho
05-25-2007, 13:15
You should update via the folderes 0 -> 1 -> 2.....
I've had a friend who put the 2 folder first, and that kinda messed it up but when she plugged it back in she just started from 0 and followed the procedure and everything was back to normal. Maybe you should try restarting your computer (without the D2 plugged in) and try moving the files over...

snakebite2
05-25-2007, 20:26
BluewaterRocket, if you can still explorer the D2 in windows, then try reinstalling the FW from 0 to 2.
If you can't copy the files than try formating the D2(internal) memory, using windows(FAT16 or 32).
The process should be
1. copy file from FW folder to D2
2. disconnect USB
3. open D2 & wait for update to finish
4. repeat process to the next folder
Note: Plugging in the USB will start the D2 up automatically.
Also, make sure you have at least 5mb of space.
Don't worry about the screen if it look mess up; It's like that because the FW is not completed