D2 stuck on loading after flashing to firmware 3.45

[mymandarin123]

Just updated to firmware 3.45(not beta) from firmware version 2.41. Everything went smoothly in the upgrade process.

After fw upgrade, also had a small look at the new notepad feature, created a small image in notepad as well, tried to access the dictionary and got the usual font error.

So switched off D2, copied the contents of PowerDic Lite to the root of D2 and copied the contents of my MUSIC and TEXT contents. After copy was completed on trying to start D2, the screen hangs on boot up at the circle screen, after two dots are covered it hangs.

Switched Off D2 and connected to the computer, again hangs on the circle part after covering 3 dots. Does not get to the part where the contents of the drive are listed.

Any inputs...tried to start it 4-5 times, tried the reset wich aswell, nothing works.

[Barron]

I have just upragraded to 3.45 aswell from 3.45b and the uprgrade went smoothly it worked striaght afterwards, however once i copied all my music back onto it in the MUSIC folder when i try and turn it on it gets stuck on the boot up. This is exactly the same problem as the first poster i would therefore discourage people to upgrade to the new firmware.

Can anybody help? I cant see what i can do as it wont turn on so the computer wont recognise it.

[slawson]

I've just installed 3.45 and haven't got any problems. How much memory/space do you have left on the unit. It might me worth deleting a few files to see if that fixes the problem.

Sorry, I didn't read the issues regards the D2 not being seen by the PC afterwards, I can't help on that one.

[Dominic]

he cant though, it won't turn on at all...

[addz]

upgraded from 3.45b and it works smoothly, with music and the lite dictionary.

Although this somewhat worries me. Maybe its a fault in the fw. Non beta fw should not perform like this.

How about trying a hard reset using the reset button on the side of the player? Also if you have, try removing the SD card, then see if it boots up. I tried a piece of fw b4 with SD card in and it kept booting and resetting its self, wouldent even connect to my computer.

[Who Am I?]

You can delete files with Jetshell or Explorer. Can you connect the D2 to your computer?

[mymandarin123]

After reading some of the posts on bricked D2, thought of completing charging the D2, maybe that would somehow magically fix D2, but unfortunately the player hangs at the same point even on trying to charge via the AC adapter.

Also tried Cowon Live Chat on this issue, I narrated the entire incident to them, they asked me to RMA the player back(kinda sucks because I had imported the player through a friend in USA because it was not available locally then) however toward the end of the chat the tech support guy said this,

"Since the firmware you loaded was not for US/Canada use, the service department will have to determine if this voided the warranty". Comeon it was not even a beta and I had downloaded it from the official cowon site.
Maybe something to think about before anyone upgrades the firmware.

How about trying a hard reset using the reset button on the side of the player? Also if you have, try removing the SD card, then see if it boots up. I tried a piece of fw b4 with SD card in and it kept booting and resetting its self, wouldent even connect to my computer.

Thanks, but tried reset, no luck the player hangs at the same place. I had removed my SDHC card while flashing so that should not be a problem.

You can delete files with Jetshell or Explorer. Can you connect the D2 to your computer?
No, when connected via usb player hangs as mentioned in the first post and is not recognised in Windows. Tried with Linux as well, same result

Any other tips to revive the player are highly appreciated..

[Barron]

upgraded from 3.45b and it works smoothly, with music and the lite dictionary.

Although this somewhat worries me. Maybe its a fault in the fw. Non beta fw should not perform like this.

How about trying a hard reset using the reset button on the side of the player? Also if you have, try removing the SD card, then see if it boots up. I tried a piece of fw b4 with SD card in and it kept booting and resetting its self, wouldent even connect to my computer.

Tried removing the sd card straight away but to no avail

I also tried charging mine in the wall but it also hangs on startup. I hope what the guy said about using korean firmware and voiding the warrenty is not true, it does not say anywhere that we should not use this firmware on other players. I am starting to feel pretty worried now as i really dont want to have to send it to cowon.

[addz]

^ oh dam this aint sounding gd atm. Im on the brink of reverting the fw 3.45 back to 2.45b. Thats total bull if they say installing this version voids the warrenty.

the whole point of v3.45 is for users without DMB model, hense all users of the D2 outside of korea.

[slawson]

Have you tried a reset whilst its connected to the PC?

[Barron]

Have you tried a reset whilst its connected to the PC?

I have now and it doesent even turn off when plugged into the PC.

Anybody else have any suggestions i would greatly appreciate any help i can get on this matter.

[Barron]

Would it be possible to install the firmware on to my sd card in a hope that that will make it boot up.

[addz]

^
i highly doubt something like that would work. im sure the D2 is programmed to only look at the root of its internal memory for the special fw files.

[terpio]

I don't think so :-(

I just loaded SDHC card with fontpatch and D2 didn't recognize bin file and upgrade font.. so flashing works only when firmware files are in root directory of D2 :-(

[Barron]

I don't think so :-(

I just loaded SDHC card with fontpatch and D2 didn't recognize bin file and upgrade font.. so flashing works only when firmware files are in root directory of D2 :-(
Damn i thought it was a long shot does anybody else have any other ideas or does it look like i am looking at RMA.

Mymandarin have you had any breakthroughs

[mymandarin123]

Mymandarin have you had any breakthroughs

Nope. I guess RMA is only option. It will cost me quite a lot to RMA the player back considering I leave on the opposite part of the globe to US. Never thought the player will die even when I followed the flash proceedure correctly. How can Cowon release such firmware is something that baffles me...even at 3:30 in the morning :(

[Barron]

Yeah it is going to be hard for me as well as i bought it when i was in Singapore but i am in the UK until July. This is my third player from cowon but it is the first serious problem i have ever had with them i am particulaly pissed off as it was when upgrading to their firmware which i did correctly anyway.

May charge it over night just to see if it has any effect i dont have high hopes though

Edit: BTW how would i go about sending it back do i return to the store i bought it from or do i have to send it to cowon

[terpio]

I know that right now the two of you are angry and sad :-( I'm very sorry for you.

But this situation puzzles me and I would like to know as many details as possible.. I too have upgraded to 3.45 and now my D2 could suddenly stop working at any time :-( I'm afraid to load any files to it internal memory..

Barron: Did You too copied PowerDic Lite with your other files after upgrade?

As there was some changes in Dictionary interface, it's possible that PDLite files from 3.45b (or older) won't work properly with official 3.45 - I just want to find cause of this firmware upgrade failure...

(Sorry for errors, my writing English is weak)

[Rosiu]

The things about the old dictionary files: NOT TRUE.

I loaded the new firmware before these issues were raised and installed the dictionary I used on 3.41b, 3.41 and 3.45b.

And ... ?

Everything works perfectly.

Maybe the hang was caused by a problem with creating the music database?
For example by copying a FLAC 1.1.4 -8 with which D2 has some problems.

Just an idea, don't know how much truth's in it.

[terpio]

The things about the old dictionary files: NOT TRUE.

I loaded the new firmware before these issues were raised and installed the dictionary I used on 3.41b, 3.41 and 3.45b.

And ... ?

Everything works perfectly.

Thanks for clarifying that for me :)

[userX]

Have you tried the 1/2 mm reset button in between the charge and TV out hidden behind the small side pane. It's hardly visible because it's very small. You have to press it in using the stylus.

[adr]

Was feeling slightly reckless so I tried upgrading to 3.45. I have all my music on an 8GB Transcend SD card. If I boot it up with the card inserted, it hangs after a while on the loading screen. If I take the card out and start it again, it loads fine. If I insert the card while it's running, it starts scanning it then hangs again. Oh well, back to 2.45b :/

[Dalmane98]

IMHO, I am sure the D2 has a hidden partition where the operating system is loaded.

All the original files on the D2 that we are told to backup are only 42.6MB. The system folder is 9.10MB, with the biggest file in there being the logo.ilb

There are not any files in the system folder in the root that you can see that are the operating system. There is nothing in there to drive that chip that operates the USB port, the display or the audio chips, etc. Nor is there anything in there that resembles a data base of the stuff you load on the D2.

All those files must be somewhere else.

The D2 is the only player from Cowon that does not have a recovery mode, as far I can tell. I wrote Cowon about this and they said there is no recovery mode and the folks at rockbox seem to agree with this. At least not one that Cowon is willing to tell anyone about.

The Sansa e200 series has a recovery mode that allows you to reformat the hidden partition and reload the firmware.

If the hidden partition get messed up during the firmware upgrade you end up with a bricked player and with no recovery mode you have to send the player back so they can reload the operating system.

There must be a way to get in the recovery mode. I find it hard to believe that Cowon has special hardware just to un-brick the player.

[Room101]

IMHO, I am sure the D2 has a hidden partition where the operating system is loaded.

There must be a way to get in the recovery mode. I find it hard to believe that Cowon has special hardware just to un-brick the player.

Well, if the player is freezing during boot, before it loads a USB driver, how would you gain access to the internal memory to wipe and reload the hidden partition. Seems to me you would need something equivalent to a boot disc. Is it so unlikely that this would involve removing the internal memory and plugging it into some other hardware???
How does recovery mode work in other players?

[mymandarin123]

Edit: BTW how would i go about sending it back do i return to the store i bought it from or do i have to send it to cowon

Sorry, I am not sure abt your case since you have bought it form singapore, you may want to talk to them on live chat.
In my case I had bought it form B&H Photo Video and the tech support asked me to RMA it to Cowon US after filling out RMA form http://jetdb.jetaudio.com/RMARequest/Request.aspx

Here's the Cowon RMA policy http://www.cowonamerica.com/support/shopping/return_warranty.html.
Policy is a bit strigent, however I hadn't thrown out any of the original packaging so no harm.


Maybe the hang was caused by a problem with creating the music database?
For example by copying a FLAC 1.1.4 -8 with which D2 has some problems.

Just an idea, don't know how much truth's in it.

I had only one text file and rest all mp3's on my internal drive, all the songs played fine, no issues so it's not related to flac, but could it be caused due to id3 database creation at the start?
Also the only s/w that was never present on my D2 was the Power Dic Lite files, so naturally this is a big supect to me.


There must be a way to get in the recovery mode. I find it hard to believe that Cowon has special hardware just to un-brick the player.

I had asked tech support if there was any means for me to reflash to the old firware without
sending the player for RMA, no luck, they said since this is a new problem with the player, they needed to look into it and I can get it fixed only by RMA.

[Room101]

I'm not optimistic, but I found a couple things you could try, from another thread:

1) keal wrote:
A couple times when I've been messing with language settings, or popping different SD cards in and out of the player, I turn on the D2 and it's either got a garbage screen or the player won't turn on at all. Pressing the reset button doesn't fix it. What works when the player won't turn on is to hold the power switch in the 'off' position for about 10 seconds. Apparently the player is on but the screen isn't, and holding the switch to off actually turns the player off. Then hitting the switch again turns the player on and things are fine.

2) Dalmane98 wrote:
The Sansa e2xx has a recovery mode that lets you install firmware if you brick their player. When you enter the recovery mode (lock the player, hold record button, turn on player) you can see a hidden 16MB partition where the software is that controls the player.

I think we just need to figure out how to view that partition or get into the recovery mode. I would guess that it has to be a combination of using the reset, power button and one of the "- M +". Then connecting the D2 to the computer.
Then it should just be a matter of dropping the contents of folder zero into that hidden partition and restarting the player.


Might be worth a try, but don't hold your breath.



EDIT: On a more positive note, in that same thread, species wrote the following:

I got my RMA number, sent in the player, they received it on thursday, fixed it the same day and shipped it back the same day, i'm supposed to receive it this wensday. GREAT SUCCESS!!
I live in Canada by the way

[mymandarin123]

yes, I read that thread. Had tried the option keal suggested. In my case though holding the power switch in the 'off' position for about 10 seconds causes the player to start and hang after 2 seconds on the starting screen, again reboot and hang and on and on ....

regarding the recovery mode I will try to fiddle with the key combinations, how I wish D2 had supported rockbox. On my friends IRiver h-120, he could dual boot into both the rockbox and default fw. Once due to some problems the default fw refused to start, he used the rockbox fw to boot and now atleast he can use it as a large hard drive.

Thanks for the tips. Greatly appreciated.

EDIT: Just tried holding the M button and tried to start D2. In this case the player does not boot at all. It simply stays dead. After this simply tried to start D2 wihtout pressing the M button and again the player does not boot. This made me wonder if it would cause the player to kick into recover mode...

Unforunately the player no longer boots, even tried connecting it ot AC charger, same no boot screen, no start screen simply dead, finally pushed at the reset button using the stylus and then started the player. It boots up again but hangs at the same position. So I am back to square one now.

[slawson]

Do you remember how much space you had left after copying all your files across?

Could it be something like the D2 is doing its indexing on startup, storing everything in memory and this then takes it over the limit and stops loading?

In reply to below: database size: Thats an interesting question. I haven't got time to do it now, but I'll have a go at finding out when I get a chance. I'd assume it could be worked out by installing the firmware to clear the existing database and then add lots of songs (leaving lots of space just in case)and take a note of the remaining space. Disconnect from PC & switch on the D2 and let it build the database and then hook it back up to the PC and take another reading of the remaining space - difference would give a very rough indication of what gets used after first initialization.

[mymandarin123]

^ Don't remember the exact free space exactly, I have the exact backup on my work comp, I guess maybe around 50mb of free space was available. Any idea if the database take up that much space.

[Barron]

I would like to clarify a few things firstly i dont think this is a dictionary problem as i didint touch that all i transferred over was mp3's however i did transfer them over until i literally had no more space (could be a problem).

Good news about the quick turnover on RMA but again does anybody know how i will send it back in my situation i.e buying from singapore but currently in England.

[Room101]

I'd assume it could be worked out by installing the firmware to clear the existing database and then add lots of songs (leaving lots of space just in case)and take a note of the remaining space. Disconnect from PC & switch on the D2 and let it build the database and then hook it back up to the PC and take another reading of the remaining space - difference would give a very rough indication of what gets used after first initialization.

You might want to reset and do the initialize thing from the manual too, just for good measure.
Anyway, FWIW, I positively remember reading on Cowon's website that you should leave at least 5mb free for OS to save settings etc. I think this was at Cowonglobal > Support > FAQ.

[Barron]

What is the initialize thing, How do you do it? Thx for the reply

[crazymaze]

I think i might have found the recovery button combination, but there seems to be no driver for it.[wacko] When i hold the menu button while trying to turn the player on, it looks like nothing happens, but when I connect my d2 to computer again windows find it as a new hardware and tries to install the drivers for it but it cant find the proper ones.... You think that this might be the hidden firmware partition?

[mymandarin123]

great news...I had tried this key comination before but had not connected the player to PC...I don't have my linux cd with me now, will try if there's any way I can mount it in linux, if windows is not able to recognise it using any of the mas storage device driver....point that using this key combination atleast windows detects it, is assuring. Thanks

[Barron]

I think i might have found the recovery button combination, but there seems to be no driver for it.[wacko] When i hold the menu button while trying to turn the player on, it looks like nothing happens, but when I connect my d2 to computer again windows find it as a new hardware and tries to install the drivers for it but it cant find the proper ones.... You think that this might be the hidden firmware partition?

Thanks for sharing this, it sounds like great news, however i cant get windows to recognise it i turn it on while it is plugged into the pc and hold down the m button but nothing happens. Am i doing this wrong?

[crazymaze]

Thanks for sharing this, it sounds like great news, however i cant get windows to recognise it i turn it on while it is plugged into the pc and hold down the m button but nothing happens. Am i doing this wrong?

Have you tried doing it before you plug it in? Hold the "M" button and flick the power button. Then connect it to your pc.. Windows will recognize it as an usb device but it cant find the drivers for it...

So if this is going to be to any use, either cowon needs to release the drivers for it or someone have to write a new one..

[Barron]

Have you tried doing it before you plug it in? Hold the "M" button and flick the power button. Then connect it to your pc.. Windows will recognize it as an usb device but it cant find the drivers for it...

So if this is going to be to any use, either cowon needs to release the drivers for it or someone have to write a new one..

OMG yes that does work now all we need is someone to write a driver for it (dont even know if it is possible). I feel a lot more confident now that i wont have to send it back.

Edit: Hmm how do i get out of this mode as my D2 wont turn on at all now.

[crazymaze]

Just use the reset button.[wink]

[Barron]

Just use the reset button.[wink]
Ok thx i was worried for a sec i had f***ed it up even more

[addz]

^ if your talking about windows drivers for it to recongise the D2, im sure the Cd included in the Box has these drivers

http://download.cowon.com/data/C08/D2_i6_U3_T2_F2_Win98Driver.zip

[Barron]

^ no they are drivers for windows 98 we need the recovery drivers like the ones that appeared for the U3.

[addz]

My bad. Anyway, there must be recovery drivers; as when cowon receive a messed up D2 how else can they fix it? It would be stupid of the D2 coulld not be recovered.

[Barron]

Yeah there must be but for some reason cowon never likes to release them, like the ones that were posted in the U3 forum were asked to be removed from cowon. It dosent make any sense to me as to why they wont let us have them it dosent benefit them to keep it secret.

[NeoDeever]

Does windows detect the hardware as a USB mass storage or does it detect it as "unknown hardware" or "generic usb" before it fails to install the driver.

My guess is that since the filesystem on the flash memory is itself corrupt, there might be nothing to show up as mass storage. However it might be possible to send commands to the device to reformat the flash mem.

On one hand, I feel for you guys with an unconscious d2 in your hands.
On the other, I am secretly happy [devil] as this thread might just be incubating a rockbox port.

[Dalmane98]

I think part of the problem here is that after pressing and holding the "M" button and turning the D2 on the screen does not display anything.

The Sansa screen displayed a message telling you that you are in the recovery mode and to connect the USB cable, after pressing the right switches.

There must be something else you have to do...Maybe lock the power switch and than press another button. It might even be pressing on a certain area of the touch screen (That works on my Garmin C320 GPS; it brings up system/diagnostic screens).

The TCC78X chip in the D2 (according to Rockbox) is what controls the USB:

http://www.telechips.com/product/p_025.htm#

The process that gets the screen to display most likely enables the USB also. There should be some kind of message telling you that you are in the recovery mode (?) otherwise it would just be guess that you should plug in the D2 in.

The Windows 98 USB drivers might also help, as the teleumss.inf file contains the information about installing the drivers.

Maybe there is a linux driver out there for the telechip? Linux should be better for figuring this out than a Windows machine.

These are just my thoughts on different ways to approach this problem...

[crazymaze]

Does windows detect the hardware as a USB mass storage or does it detect it as "unknown hardware" or "generic usb" before it fails to install the driver.

My guess is that since the filesystem on the flash memory is itself corrupt, there might be nothing to show up as mass storage. However it might be possible to send commands to the device to reformat the flash mem.

On one hand, I feel for you guys with an unconscious d2 in your hands.
On the other, I am secretly happy [devil] as this thread might just be incubating a rockbox port.

Well I got an fully functional d2, so its not because the corrupt file system.
The d2 shows up as an "usb device" and doesn't say anything more about it.

And oh yeah, i would love to see rockbox on the d2!
This might be the reason that cowon has to not release the recovery drivers. They probably want to make it harder for people to write homebrew for their players....

[NeoDeever]

Well I got an fully functional d2, so its not because the corrupt file system.

it would help if you could confirm that.

So let me explain further. There is a three step process taking place here each requiring seperate drivers
1) Detection of the device as usb mass storage (usbstor.sys)
2) Provisioning of the device as a disk drive (disk.sys)
3) Managing the partition (part.sys)


In Device Manager,

When Step 1, suceeds the device is shown up under Universal Serial Bus controllers as a generic usb mass storage device,

When Step 2, succeeds the device is shown up under Disk Drives as Cowon D2 Usb Device, twice for the device as well as the SD Card.

I would like to know where in device manager do you see an exclamation or question mark.

Also if you do get a details tab in the properties of either the USB Mass Storage or Cowon D2 Device, check if you get values for queries like:

Hardware Ids
Compatible ids
Devnod flags
Bus Relations (for UMS Device)

and post them here

Do not post the Device Instance ID 'coz these contain the serial number of your device.

These might help to debug

[mymandarin123]

On Windows 2000:
On connecting got the Found New USB Device Dialog
It tries to serach for a driver and fails.
It gets listed under the other devices as a USB device with an Yellow Exclamation mark.

So there's no details tab :(

I also tried to get it to load in WIndows 98SE, installed the Universal Mass Storage driver utility from here,
http://www.technical-assistance.co.uk/kb/usbmsd98.php
and then connected the D2 with the hope that somehow it would be recognised, but that did not work,
on connecting got the same new usb device found dialog asking for driver.

Thanks to all of you for the tips. Will look into some of the things Dalmane98 mentioned

[crazymaze]

it would help if you could confirm that.

So let me explain further. There is a three step process taking place here each requiring seperate drivers
1) Detection of the device as usb mass storage (usbstor.sys)
2) Provisioning of the device as a disk drive (disk.sys)
3) Managing the partition (part.sys)


In Device Manager,

When Step 1, suceeds the device is shown up under Universal Serial Bus controllers as a generic usb mass storage device,

When Step 2, succeeds the device is shown up under Disk Drives as Cowon D2 Usb Device, twice for the device as well as the SD Card.

I would like to know where in device manager do you see an exclamation or question mark.

Also if you do get a details tab in the properties of either the USB Mass Storage or Cowon D2 Device, check if you get values for queries like:

Hardware Ids
Compatible ids
Devnod flags
Bus Relations (for UMS Device)

and post them here

Do not post the Device Instance ID 'coz these contain the serial number of your device.

These might help to debug

What I meant was that theres nothing wrong with my d2. I am just trying to figure out how to get windows to recognize the d2 in recovery mode.(to help those who has bricked their players, and to make it possible to get a rockbox port on it.[biggrin] )

But anyway, heres the Info you asked for. (in recovery mode) :

The unit is listed under "other units" as "USB Device"


Hardware ids:
USB\Vid_140e&Pid_b011&Rev_0100
USB\Vid_140e&Pid_b011

Compitable ids:
USB\Class_ff&SubClass_ff&Prot_ff
USB\Class_ff&SubClass_ff
USB\Class_ff

Devnod flags:
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_REMOVABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER

Config flags:
CONFIGFLAG_FAILEDINSTALL

[mymandarin123]

There must be something else you have to do...Maybe lock the power switch and than press another button.

Tried many key combinations, no luck so far.


The Windows 98 USB drivers might also help, as the teleumss.inf file contains the information about installing the drivers.

Windows 98SE does not pick up the drivers in the 'recovery' mode. It simply states no suiatble driver found. Manual states that the while installing the drivers for 98, player needs to be connected to the USB and then on providing the path to the Win98 folder on the D2 cd, it should install the drivers, I guess this only works in case of normal mode (player unfortunately hangs in this mode & never gets to the usb device found part)

crazymate, just a bit curious, how did you get all those details. In my case there's no details tab. What OS are you using and under what tab are these details available ?

[crazymaze]

crazymate, just a bit curious, how did you get all those details. In my case there's no details tab. What OS are you using and under what tab are these details available ?

I'm using windows xp pro.
You just right click on the "usb device" and choose properties, then click the details tab. Works for my anyway.

You can use any of the buttons on the top of the player to go into the recovery mode. I think that the display doesn't show anything on the screen is because Cowon don't want you to know that there is a recovery mode.

Someone had the recovery mode drivers for the u3 but Cowon had them to remove the link to it from this forum. Cowon said that the driver were not meant for public release due to licensing issues or something. If someone could find these drivers they'll might work with the d2 too? Or wont they because of the hardware differences?

Well, I think its worth a try.

[Dalmane98]

Try asking parisi. He might still have them.

http://www.iaudiophile.net/forums/showthread.php?t=14555

You could try emailing bbTomas. He said he would help anyone that emails him.

http://iaudiophile.net/forums/showthread.php?t=11086&highlight=recovery

addz might have then too, from his post in the above URL.

As long as we do not post anything or link to anything about the drivers we should not be breaking any forum rules. External emails should be private.

Well that is my 2 cents worth.

[addz]

addz might have then too, from his post in the above URL.

[cool] I say no more.

[NeoDeever]

USB\Class_ff&SubClass_ff&Prot_ff
Class should be 08 not FF for device to be detected as mass storage and load usbstor.sys. AFAIK, Class_ff is reported when device is not responding properly. I have to do more research on this.

On the other hand one can still force a usb mass storage driver to load by expliciting defining the vendor/product id (I think this needs to be done in usb.inf, will confirm)
BTW, Vid_140e = VEndor ID : 140E = Telechips. Interesting 'coz we know that the usb support is provided by the Telechip SOC TCC78x

However, I get a different vendor/product id when connecting my working device connected in normal mode. Can you confirm this crazymate? Also do tell me if the device functions back normally when you reset it out of so called recovery/service mode.

Anybody got any luck with Linux?

[crazymaze]

in normal mode i just get

STORAGE\Volume in hardware ids and compatible ids, and:

DN_DRIVER_LOADED
DN_STARTED
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER

in devnode-flagg.

And yeah it goes back to normal when you push the reset button.


EDIT:

The U3 recovery drivers does not work with the d2..=/ I didnt try the update app but i'm sure if i did it would brick my D2.(if it could find it)

Addz

do you know how it works with the U3? Does the partition show up in explorer or is it only detected by the app?

[NeoDeever]

Just tried the trick,
In recovery mode the usb device returned a hardware id of
USB\Vid_0e21&Pid_0800 ...This is a telechips vendor id

Where as in normal mode, the hardware id is
USB\VID_041E&PID_4028 ... This is a cowon vendor id

What this means is that the usb service is provided by the Cowon Firmware in normal mode and the usual drivers work

But in recovery mode, the cowon firmware is completely by passed and we are direcly accessing the usb services on the TCC7801 [thumbsup] So yes, a recovery should be possible.

And I have a hunch that u3 recovery drivers should work with slight modifications as both the TCC770 and TCC7801 are based on ARM and have an on-chip usb host support.

Addz
do you know how it works with the U3? Does the partition show up in explorer or is it only detected by the app?

I am curious too. Also, is the LCD of U3 blank like D2 while in recovery mode?

One more think crazy, I didn't require to reset my device to comeback to normal mode just powered off and on the device a couple of times while the usb was connected to pc in recovery mode and I was back to normal mode.

[residentour]

I have the same problem my D2 wont start and stuck at the start. Tried eveything but nothing happens. I think we should find the recovery driver.

[addz]

tbh ive never needed to use the U3 recovery files. so really couldent tell ya. sorry.

I would assume the program would do all the work, > recongise the device, and replace particular recovery files.

Edit Added warning on the OP for new fw3.45 to warn users of this problem.

[mymandarin123]

I have the same problem my D2 wont start and stuck at the start. Tried eveything but nothing happens. I think we should find the recovery driver.

Sorry to hear about that. What were the steps that caused the hang, care to elaborate.

[residentour]

I have upgraded from 3.45b to 3.45 . Before i backed up my music,powerdict,video folder to my computer and after upgrading restored them to D2. So this has caused the problem. Cowon should immediately release recovery tools.[mad] This is beacause of untested firmware release from Cowon.

[addz]

Aint this the weirdest thing ever. ^ I did exactly the same thing, backup my stuff, then loaded the stuff + dictionary back on again, and my D2 worked fine. It surely cant be the fw can it? It has worked fine for others. Although i must say i have reverted back to 2.45b.

Out of interest: did you fill up the D2 memory completly? the D2 needs at least 5mb for savings settings etc.

[residentour]

I think we should find a common telechips recovery driver like Sigmatel one. Because Sigmatel has a general driver for recovery. Which players have telechip?

[mymandarin123]

Out of interest: did you fill up the D2 memory completly? the D2 needs at least 5mb for savings settings etc.

not sure if only this fw is buggy or all the fw so far may cause the same scneario when one fills up the internal drive. manual states that for cowon d2 to play properly atleast 5 mb of free space should be there.

Infact it should have mentioned that the player will be rendered useless if one fills up the entire internal drive and this should have been in bold letter with danger mark. Come on any one could accidentally transfer loads of file from the internal drive to sd and back or for that matter incrementally add a few files to the internal drive, causing it to fill up and suddenly you find the player stuck.

This is depressing and can be a disaster that many could face (provided that low disk space on internal drive is the cause for the failure)

[Michalaq]

I hope those who have broken their D2s with this upgrade have written to Cowon. They need to know about this, so that they can take the firmware upgrade off their website and prevent others from getting the same problem.
Also, it increases the probability of Cowon releasing some sort of recovery tool!

[residentour]

How can i contact Cowon? What is the mail adress?

[Michalaq]

Hmm, you could write to the Q&A section of cowonglobal (go to cowonglobal.com, click on the support section, and then Q&A on the menu on the left, you'll have to make an account)
When I had questions about my D2 I did that as well as writing an email direct to the Polish cowon website. I got replies from both.
I know cowonamerica have a live technical support chatline thing, as well.

If anyone knows a direct e-mail contact I would be grateful to know it myself.

[NeoDeever]

The u3 recovery driver looks great, and can seems like it can be very much used for D2. I am quite positive now that the device is entering recovery mode with the method crazy has described

The following changes need to be done to the u3 software to make it work for d2
1) Open the inf file and change the device id string from VID_140E&PID_B021 to VID_140E&PID_B011 at both the places. This will allow the device to be detected under windows.
2) Replace the firmware files in the setup with the D2 firmware files. This would be the bin file in the 0 folder.

Then connect the device to the PC in recovery mode, it should be detected as iaudio 3 or whatever string is written in the inf file. Then we run the exe and viola when the device reboots and is detected as mass storage we copy files from the folder 2 of d2 firmware and then after the next reboot from the device from folder 3.

I think this should work out, but I suggest we can wait for strong reasons from other members of the forum telling us why it won't work.

Take this with a standard warning, that you may make things worse for yourself, since nobody has ever tried out. On the other hand, if it does work out...then you will be thanked with a few [biggrin] faces

I would give it a shot if my device was bricked. Currently it is not [smile]

[NeoDeever]

Okay, I made the above changes to my inf files, started the device in recovery mode and it was detected successfully :) I even could query it right and got the following information for Device Nodes
DN_DRIVER_LOADED
DN_STARTED
DN_DISABLEABLE
DN_REMOVABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER

These drivers are simple file transfer programs that use scsi commands to transfer files to the device. The only problem could be that of addressing, if any at all.

Before running the exe please make sure
1) To delete U3_font.bin and U3_fw.bin
2) To copy D2N.bin from folder 0 into the folder from where the above files were deleted and rename it to U3_fw.bin
3) To copy D2N_font.bin from folder 0 into the folder from where the above files were deleted and rename it to U3_font.bin

WARNING: Since this is a completely untested process and an educated guess try this process if you are sure your device is bricked and you are not going to send it to cowon for RMA! OR else wait for some one else to try it first :)

[Michalaq]

On the rockbox forums (http://forums.rockbox.org/index.php?topic=10164.msg78742), it says that the firmware layout of the D2 is indeed similar to that of the U3. The D2 uses a newer version of the same chipset, so the preloader setup will probably be similar.
Only problem might be that the D2 chipset has a dual core architecture, whereas the U3 was single (the processor of the D23 is the same as the U3, except has a second core dedicated to the video stream). Could this cause incompatibility?
You could well be onto something here!!! If this works, not only will these D2s be fixed, but Rockbox would become a possibility!

Brilliant analysis, NeoDeever!!

[Dalmane98]

Nice job of Reverse Engineering, if it works and without looking at the files I see no reason why it will not work.

Your reasoning seems sound.

If the computer detects the device and you can see the partitions then it should work. May be it will work if you cannot see the extra partition...

I would recommend that no one try to format the hidden partition if it is viewable now. No telling what that would do.

Now if someone that has a bricked D2 will try this, if they can locate the u3 recovery drivers.

[residentour]

I couldn't do. I found 3 VID_140E&PID_B021 and changed to VID_140E&PID_B011 ,then pc recogized d2 as u3. But after changing firmware files and pressing start button of recovery program it gives me an error . Colud you please send me the moded files
mail : atakanozgur@yahoo.com

[Dalmane98]

I couldn't do. I found 3 VID_140E&PID_B021 and changed to VID_140E&PID_B011 ,then pc recogized d2 as u3. But after changing firmware files and pressing start button of recovery program it gives me an error . Colud you please send me the moded files
mail : atakanozgur@yahoo.com

How many drives could you see for the D2 in My Computer or Explorer?

Did you look at the folders/files if there was a new drive?

What did the error message say?

If there is a third drive for the D2 could you post a screen shot of what is inside it?

[residentour]

I cannot reach any drive, recovery program does not flash D2 .It unmounts if i press start button. Have you successfully flashed?
Screenshot : http://img412.imageshack.us/my.php?image=aaauu2.jpg

[Dalmane98]

I am sorry, but my D2 is not Bricked.

None of this may work, but it is worth a try.

[snakebite2]

Does anyone know the cause of this problem? I find it hard to believe that the Final FW can break player.[blink] The hardware is the same for every player. I guess it has something to do with the free space on the Drive. if not the process of the upgrade. Do you guys update the FW with SD in? I don't![no] I hope it won't happen to me on future updates.[unsure]

[mymandarin123]

Okay, I made the above changes to my inf files, started the device in recovery mode and it was detected successfully :) I even could query it right and got the following information for Device Nodes
DN_DRIVER_LOADED
DN_STARTED
DN_DISABLEABLE
DN_REMOVABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER



You mentioned that D2 was detected successfully after making the changes in inf file. Could you see both the drives(contents as well) of D2? I will try to check this out myself as well but don't have XP(I will try in Windows 2000), appreciate your response.

[mymandarin123]

I tried with 3 changes in the inf file and then connected D2. Windows 2000 accepted the driver but did not recognise it as D2, it got listed under universal serial bus controllers as %USB\VID_140E&PID_B011.DeviceDesc%=, also no drives got created. I will try this on a xp machine and see how it goes.

[NeoDeever]

Yes, the drivers get loaded correctly. But the recovery drivers are not mass storage drivers. They provide access to the service interface of the D2. It is a special communication interface where in you can send commands/firmware to the d2. Think of them as serial port drivers.

Anyways, the software fails to upgrade. But the fact that it successfully unplugs the hardware, we know that is able to communicate correctly. Now the exe needs a fix :)

[Room101]

Added warning on the OP for new fw3.45 to warn users of this problem.

FWIW, this problem does not appear to be exclusive to firmware version 3.45:

http://iaudiophile.net/forums/showthread.php?t=13920

http://iaudiophile.net/forums/showthread.php?t=13535

http://iaudiophile.net/forums/showthread.php?t=14261

[residentour]

I think this is the same problem and we should get a recovery tool immediately. I live in Turkey so i cannot send my player to USA because of cargo limits.

[Barron]

Could somebody please send me the U3 recovery drives to mb2222@gmail.com.
Also now when i plug my d2 into my computer in recovry mode windows does not try to install drivers, the d2 also does not show up anywhere on my computer.

[NeoDeever]

I had a word with one of the senior members in the forum, and I was told that the U3 firmware was released after a lot of pressing by owners on U3, who wanted their device software to be fixed without RMAing it to the service centers 'coz they believed they had the right to do so [biggrin]

Maybe, a few members can take that route. Contact me or other senior cowon members for the url, it would certainly help if you can understand/speak czech and check with support engineers for the recovery software for D2, which we are sure exist.

On the other hand, I am putting my best to get the u3 recovery software working for d2. And getting a lot of support for that too.

Thank you Cowon for making a great device, thank you Cowon for bringing us good software, thank you cowon for continuously adding new features to our device. Only place the company lacks is support, and understandably 'coz it's hard to build a worldwide logistics and sales/service network without being as popular as iPOD. But that doesn't stop me from being a Cowon Fan....[cool]

Let's take one route or the other but keep trying. I think our patience is going to be rewarded in the end.

[mymandarin123]

Also now when i plug my d2 into my computer in recovry mode windows does not try to install drivers, the d2 also does not show up anywhere on my computer.
One reason why the install driver option is not being shown, would be cause windows might have chosen some default driver for the device. You could go ahead and delete the entry for the incorect USB device once when D2 is connected in recovery mode and thereafter reconnect and you should get new usb device found message.

Also thanks NeoDeever for your efforts. I too would really like to use the recovery software.

EDIT:
Hmm, you could write to the Q&A section of cowonglobal (go to cowonglobal.com, click on the support section, and then Q&A on the menu on the left, you'll have to make an account)


I just wrote a Q&A article on the above site, detailing the problems that all of us are facing and requesting them to release the D2 service driver. Let's see how this goes.

[residentour]

I have mailed to Telechips, Cowon support and modder of the U3 recovery program and waiting for a solution.

[Dalmane98]

Yes, the drivers get loaded correctly. But the recovery drivers are not mass storage drivers. They provide access to the service interface of the D2.

I agree with you 100%. The next step is to get the mass storage drivers to load.

I tried modifying the files and using the U3 exe. It only gave me an error message after clicking start. I am not sure all the fields were populated correctly since I do not read Czech.

When I execute the U3 exe one of the options in the window that opens is to format the device (formátování pamětí). I think, that would suggest that the mass storage driver should be loaded.

If the mass storage drivers are not loaded than were would the U3 Recovery program load the new firmware to?

Anyways, the software fails to upgrade. But the fact that it successfully unplugs the hardware, we know that is able to communicate correctly. Now the exe needs a fix :)

I agree with the exe needing to be modified.

Someone at Rockbox has seen this thread and posted a link to it.

It would be nice if someone could translate the Czech to English.

It would also be great if someone with a U3 would try the software and post a screenshot of the U3 exe windows populated. Not Use It!!

Cowon USA needs to post a telephone number, so we can talk to their Technical Support people, if they have any in the USA!

Chat and email sucks for somethings...

[residentour]

I found Telechips integrated mp3 player. Maybe one of them can be used to flash D2.


* (1) Telechips TCC73x > CPU 16bit CalmRISC (80 MHz ) + DSP

o Monolith MX-7050 > TCC731Y + Wolson WM 8731
* (2) TCC72x CPU ARM 9 (140 MHz) + DSP

o Safa SR-850F > TCC721Y + codec Wolfson WM 8750
* (3) Telechips TCC76x (140 Mhz)

o M-Bird XY-22 >> TCC767H + codec Wolfson WM8973
o MPIO ONE >> TCC 76x + codec Wolfson WM 8750
o MPIO FG200 >> TCC 76x + codec Wolfson WM 8750
o Sorell (S-cam ) SF3500ZF >>TCC 767+ codec Wolfson WM 8750
o Sorell SF-3700 (S-cam ) SF-3700 (aka Creative MuVo Vidz ) >>TCC767 + codec Wolfson WM 8750
o Samsung YP-T8 + YP-D1 >>TCC766 + Wolfson WM8731
o M-Bird M-Bird XY-22 .>TCC767H + Wolfson WM 8973
o MPIO FG200 >> TCC776
o mobiBLU >> TCC767 + codec Wolfson WM 8750S
o mobiBLU >> TCC760
o Ramos V 20 (w Europie sprzedawany jako Trekstor iBead Vision) > TCC766 +codec Texas Instruments TI TLV320AIC23B
o Stormblue A9 > TCC 776 + codec Texas Instruments TI TLV320AIC23B

* (4) Telechips TCC 77x (ARM946 120 MHz +DSP) technologia 13 mikronowa

o iAUDIO U3 >> Telechips TCC770 + codec Cirrus Logic CS42L51
o Cowon iAUDIO F2 > Telechips TCC770 + codec Cirrus Logic CS42L51 (niepewne !)
o Cowon iAUDIO 6 > Telechips TCC771 (jeden zintegrowany chip - nie wiadomo jaki codec siedzi w srodku)
o Cowon iAUDIO T2 > Telechips TCC772S + Wolfson WM8731L
o LG 20 > TCC771 (taka sama sytuacja co z iAudio 6)
o Teclast T29 > TCC 770 + Wolfson WM8750 (player ten bedzie sprzedawany także pod marką Mobiblu D5)
o Sandisk Sansa M-240-M 260 > TCC770 + codec Texas Instruments TI TLV320AIC23B
o Sandisk Sansa C-140-C150 > TCC770 + codec Texas Instruments TI TLV320AIC23B
o Samsung YP-K5 > TCC770 + Wolfson WM8956
o Samsung YP-K3 > TCC771L ( prawdopodobnie jest to chip zintegrowany razem z codeciem )
o LG FM35 > TCC770 + Wolfson WM8750
o iBead 700 > TCC770 + Wolfson WM8750
* (5) TCC 78x ( 2x ARM9 400 Mhz )

o Cowon D2 > TCC 7801 + Wolfson WM8985
o Iriver Clix 2 > TCC 7800 + codec Wolfson WM 8731S
o iStation Mini DX > TCC 7801 + codec (?)
o LG FM37 > TCC 7801 (?)
* (6) TCC 82x (ARM 9 200 Mhz video playback.30 klatek na sekundę)

o Insignia NS-DVxG > TCC 8200 + codec Texas Instruments TI TLV320AIC23B
o iriver X 20 > TCC 8200 + codec Texas Instruments TI TLV320AIC23B




As seen above Cowon D2,river Clix 2,iStation Mini DX and LG FM37 use the same chip. So we can mode or directly use thie recovery program. But i couldn't find any of their firmware files even :( .

[Barron]

One reason why the install driver option is not being shown, would be cause windows might have chosen some default driver for the device. You could go ahead and delete the entry for the incorect USB device once when D2 is connected in recovery mode and thereafter reconnect and you should get new usb device found message.
How would i go about doing that?


It would also be great if someone with a U3 would try the software and post a screenshot of the U3 exe windows populated. Not Use It!!
I have a U3 but as i said i dont have the recovery files so i cant do this for you.

I would like to say thankyou to everyone who is helping in this project.

[Aevum]

reading the threads related to this issue,
it seems to be a problem with loading the korean firmware on some revisions of non korean players,

i think that if we checked the serial numbers or atleast the production series of the bricked players, we could find a pattern.

[residentour]

Barron your mail adress is wrong written i think beacuse yahoo cannot send to that adress.

[mymandarin123]

How would i go about doing that?
Baron check your PM.

Well, now in my case as well the player is not being recognised in recovery mode, battery drained completely.

I have kept it to charge now, don't know if it will charge cos the palyer has hung at the boot screen even on charging. If that doesn't work I will try to charge by keeping the player in the recovery mode. Could this harm D2 ?


i think that if we checked the serial numbers or atleast the production series of the bricked players, we could find a pattern.

My Serial No: DE0703209830

[Barron]

Addz thanks for uploading the u3 recovery files. Will take screenshot with U3 in a sec

[Barron]

What exactly is it that you want a screenshot of dalmane98 when i click on the .exe is:

http://images6.pictiger.com/thumbs/7a/181f219291d16a31f0585184c625d47a.th.jpg (http://server6.pictiger.com/img/94190/picture-hosting/screenshot.php)

[Dalmane98]

What exactly is it that you want a screenshot of dalmane98 when i click on the .exe is:

http://images6.pictiger.com/thumbs/7a/181f219291d16a31f0585184c625d47a.th.jpg (http://server6.pictiger.com/img/94190/picture-hosting/screenshot.php)

Barron that is the same thing I get.

I wanted to see what it looked like with the field populated with a U3 connected. In particular I wanted to see if the format option had anything in it. I also wanted to know if the drives on the U3 appeared in Explorer or My Computer.

I just downloaded all the firmware updates for the U3. They are all missing the cwusbif.* files (except for the dll), so I guess those are the ones Cowon was upset about.

I assumed that people who had U3 upgraded their firmware and would have an idea of what the fields were populated with.

If you want the driver option to show up you have to uninstall the drivers. You just plug in the device and then under hardware select it, right click and select uninstall and then reboot your machine.

You can also do a search for cwusbif.* and delete them. Those are the drivers associated with the U3 Recovery files. Then after you reboot your machine and plug in the D2 the install driver option should appear as the needed files are gone.

[mymandarin123]

I guess he wants to see how the various fields in the application are populated , when you connect U3 to Pc in recovery mode.

http://iaudiophile.net/forums/showthread.php?t=10931&highlight=recovery+mode
Check the above link as to how to get U3 into recovery mode.

Once windows asks for drivers you can provide the path with the application and inf files. Once windows recognises U3, load up the app ad take a screenshot

Connecting to U3 to PC in recovery mode should not cause any harm I believe but do not perform any other actions, do not click on the Start button on the app,

[Barron]

Okay well i put my U3 in recovery mode then installed the drivers which worked succesfully and xp recognised it as U3. When i run the app with it in recovery mode it looks exactly the same as the screenshot i took before. Also i cannot view the U3 through windows explorer.

Is this of any use?

[residentour]

If we select formating option at the recovery program it takes 50-70 sec and U3 gets 0 file in it. So this option is an RAW formatting from first bit to the last one i think.
Also this program is a moded one from Telechips flasher program which is like this :
http://img339.imageshack.us/img339/2569/u3recoverydlgiq7.jpg
So we should find this program or find firmware tools of player which has the same chip TCC78X


(5) TCC 78x ( 2x ARM9 400 Mhz )

o Cowon D2 > TCC 7801 + Wolfson WM8985
o Iriver Clix 2 > TCC 7800 + codec Wolfson WM 8731S
o iStation Mini DX > TCC 7801 + codec (?)
o LG FM37 > TCC 7801 (?)

[Room101]

reading the threads related to this issue,
it seems to be a problem with loading the korean firmware on some revisions of non korean players,


I'm not so sure about that: see my post above linking to threads where people have discussed similar problems with other versions of the firmware. Or was there something different about the problems they were having that I haven't noticed?

[Dalmane98]

I think I now understand what happened with the U3.

IMHO there really is no Official Recovery Mode for the U3, at least any procedure I can find.

People were bricking their players and there was no recovery mode.

A guy found the drivers for the USB and reverse engineered the U3 firmware updater so that you could format the mass storage and reload the firmware. See attached pictures.

Cowon had issues with the release of the drivers. You have to get a license for them. If you go to Techchips site, everything I tried to look at (FAQ & Documents) asks me for a user name/password. You must have to be a dealer or a company that brought there Chips.

We are trying to use something that was designed by someone, other than Cowon, for the U3 and hoping it will work with the D2.

This may still work if someone could get the source code and modify the exe file that we are trying to use and the dll file.

Well this is my take on this effort so far.

Great job by all.

[Barron]

I have been searching for ages trying to find either a generic recovery driver for the telechips chip or one for the other players which use the chip however i have had no luck. Has anyone else found anything?

[residentour]

I think U3 is the one that we can easily find now but i am waiting for telechips and Cowon 's respond.

[mymandarin123]

Tried to mount D2 in Linux today, not much succes though.
Used a vmware ubuntu 6.X distro, although the player gets recognised in linux as a usb device,couldn't make much headway as it was not recognised as a mass storage device.

Don't have much experience with linux, so was using this link http://www.linuxjournal.com/article/8366 as a reference for the commands.
Will try tomorrow with a native version, I guess since I was using vmware version maybe I could have missed something.

Any suggestions from people using D2 under linux is greatly appreciated.

[userX]

Tried to mount D2 in Linux today, not much succes though.
Used a vmware ubuntu 6.X distro, although the player gets recognised in linux as a usb device,couldn't make much headway as it was not recognised as a mass storage device.

Don't have much experience with linux, so was using this link http://www.linuxjournal.com/article/8366 as a reference for the commands.
Will try tomorrow with a native version, I guess since I was using vmware version maybe I could have missed something.

Any suggestions from people using D2 under linux is greatly appreciated.

I use it under Ubuntu Feisty and it works. Used it under Suse, worked too...

Can you describe your problem?

[residentour]

I use it under Ubuntu Feisty and it works. Used it under Suse, worked too...

Can you describe your problem?


We need linux to recognize D2 with recovery mode and write firmware.[yes]

[Rouge8]

Tried to mount D2 in Linux today, not much succes though.
Used a vmware ubuntu 6.X distro, although the player gets recognised in linux as a usb device,couldn't make much headway as it was not recognised as a mass storage device.

Don't have much experience with linux, so was using this link http://www.linuxjournal.com/article/8366 as a reference for the commands.
Will try tomorrow with a native version, I guess since I was using vmware version maybe I could have missed something.

Any suggestions from people using D2 under linux is greatly appreciated.

Using it in Vmware would require the windows PC to recognize the device, I believe.

[slawson]

I'm using archlinux and like mymandarin123 mentioned, linux picks up the D2 in recovery mode as a USB device but not a mass storage device. The link mymandarin123 gave looks a very interesting page and is a bit to advanced for me, however even on that page linux does actually see the usb stick as a scsi device, unfortunately the D2 doesn't.

I'm not an expert, but my past experience with other usb devices on linux tells me that in order to mount the D2 as a drive in recovery mode will require some sort of bespoke software or driver.

[userX]

I'm using archlinux and like mymandarin123 mentioned, linux picks up the D2 in recovery mode as a USB device but not a mass storage device. The link mymandarin123 gave looks a very interesting page and is a bit to advanced for me, however even on that page linux does actually see the usb stick as a scsi device, unfortunately the D2 doesn't.

I'm not an expert, but my past experience with other usb devices on linux tells me that in order to mount the D2 as a drive in recovery mode will require some sort of bespoke software or driver.

Can't you install ubuntu? Ubuntu has the facility to take up some of your account's setting in the home directory. If you start up the live cd you will see if ubuntu recognizes the device (mine does). Debian runs pretty solid. Unless you're hooked to Archlinux.

[mymandarin123]

Can't you install ubuntu? Ubuntu has the facility to take up some of your account's setting in the home directory. If you start up the live cd you will see if ubuntu recognizes the device (mine does). Debian runs pretty solid. Unless you're hooked to Archlinux.

Are you connecting D2 in the recovery mode? In the normal mode, I believe it will be recognised easily. To get D2 in to recovery mode - Hold the "M" button and flick the power button. Then connect it to your pc, unlike the normal mode, the display would be blank. To get back to the normal mode, simply press the reset switch after disconnecting from PC.

[Barron]

I got a response from cowon today it wasnt positive though, here it is:

Dear Alex Barron,

Thank you for using COWON D2.

We do not release the recovery driver for users because it must be carried out by COWON SYSTEMS.

If it still is not recognized by others, your player needs to check where the trouble is. So please tell us when and in which country you bought it? And let us know where you live in now. After that, we are able to give you the right information. As soon as we hear back from you, we will take appropriate further action. We regret the inconvenience caused and request you for your kind cooperation.

Thanks again for using the customer support at cowonglobal.com.

Regards,


COWON

I guess the positives we can take from this is that they are not denying they have recovery drivers.

[mymandarin123]

If it still is not recognized by others, your player needs to check where the trouble is. So please tell us when and in which country you bought it? And let us know where you live in now. After that, we are able to give you the right information.
What does that mean, would they be willing to let you get it repaired in UK?

I too got a response but mine's even worse, feel that they didn't even read my mail correctly.

---------
Thank you for using COWON D2.

We do not release the recovery driver for users because it must be
carried out by COWON SYSTEMS. And we recommend you to install the firmware
at cowonglobal.com.

Please connect the player to the computer and back up your files, and
format the device. You can format the device with FAT 32 in either
JetShell or Windows Explorer.

JetShell: File -; Format Device Memory
Windows Explorer: My computer ; right click the drive ;
Format…

After formatting, please upgrade the latest firmware again. Click below
to download it, and it will show you the instructions.

http://www.cowonglobal.com/zeroboard/zboard.php?id=C08&page=1&sn1=&divpage=1&bmenu=download&sn=off&ss=on&sc=on&select_arrange=headnum&bmenu=download&desc=asc&no=270&bmenu=download

If you have further questions, feel free to ask us again.
Thanks again for using the customer support at cowonglobal.com.

Regards,

COWON
--------

Duh...after sending such a detailed mail regarding players exact problems, RMA difficulties and a link to this thread, this is what they say :(

[residentour]

Mine is the worst one i think :

"

3.45 is not a supported version for the US release of the D2. Please
load version 2.45 from the Cowon America site to resolve the issue.
Thank You,
Technical Suppport Staff
Cowon America Inc
"Digital Pride"

"


How can we flash to 2.45 if we cannot turn on our players :) .

[Barron]

Well i am not sure if they will repair in the UK i have send another reply to them will see what they say. When i first asked them they also told me to reinstall the firmware so i made it clear this was impossible in my next response, i recomed you guys do the same and also press for that driver.[wink]

[mymandarin123]

On another note tried mounting D2 using a ubuntu live cd...Not much luck

Here's the output of # tail -f /var/log/messages
Just removed timestamp entries like "May 15 17:26:55 ubuntu kernel : [ 17180793.372000]" from the entries below for clarity,

Part 1 is for my 1 gb flash drive and part 2 is for Cowon D2

Part 1:
usb 5-6: USB disconnect, address 3
usb 5-6: new high speed USB device using ehci_hcd and address 4
usb 5-6: configuration #1 chosen from 1 choice
usbcore: registered new driver libusual
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
Vendor: JetFlash Model: TS1GJFV20 Rev: 0.00
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 2015232 512-byte hdwr sectors (1032 MB)
sdb: Write Protect is off
SCSI device sdb: 2015232 512-byte hdwr sectors (1032 MB)
sdb: Write Protect is off
sdb: sdb1
sd 2:0:0:0: Attached scsi removable disk sdb
sd 2:0:0:0: Attached scsi generic sg2 type 0
usb 5-6: USB disconnect, address 4 ...occurs when I removed the player

Part 2:
usb 5-6: new high speed USB device using ehci_hcd and address 5
usb 5-6: configuration #1 chosen from 1 choice
usb 5-6: USB disconnect, address 5 ...occurs when I removed D2

comapring the output of both Part 1 & 2, for D2
usbcore: registered new driver libusual
does not get executead and hence it is not recognised as a mass storage device.
Any suggestions...linux guys

[residentour]

I don't know about linux but i know the recovery mode is a different circuit of flashing EEPROM which has a default non writable ROM so every time it works to flash (if we have any recovery driver). So recovery mode should be only 16 mb hidden partition which has the flash memory so we colud copy the d2.bin to.

[ahbc]

Hay,

I have a question, I just installed 3.45 and when I try to open the dictionary it gives the following error: Acces to font failed
Can I do something about this..?

Thnx

[Rosiu]

First you have to download the dictionary version (FULL or LITE) and copy its files to the D2.

[residentour]

I sent 3 more mails with different email accounts. Every time they say different thing like sending for RMA , flashing to official firmware or not giving the recovery drivers. I think we should make pressure over them.

[Barron]

I sent 3 more mails with different email accounts. Every time they say different thing like sending for RMA , flashing to official firmware or not giving the recovery drivers. I think we should make pressure over them.
Thats quite a good idea yet a bit cheeky. What email address are you using (i am just using the Q&A on cowonglobal)

[mymandarin123]

yeah, I too would like to know if there are any other mail id's I am currently using iaudio@cowon.com This is the id from where the reply came after I wrote a Q&A article

Also did anyone notice, Cowon has released fw 3.46 http://iaudiophile.net/forums/showthread.php?t=14814 and this is just under 4 days after fw 3.45 came out.

I feel cowon realised, that they had goofed up big time with the 3.45 fw and that's why such an emergency patch.

[Barron]

^ yeah i was also thinking that about this new firmware that was released so quickly after 3.45 which f***ed up so many d2's. This annoys me even more how they can release 3.45 when it had such a huge problem with it.

[ManchesterBaby]

On another note tried mounting D2 using a ubuntu live cd...Not much luck

Here's the output of # tail -f /var/log/messages
...
Any suggestions...linux guys

"lsusb -v" will give a vast amount of information about all connected USB devices. Not sure if any of it is any use however. Might be worth a try...

There also appear to be programs out there that "snoop" the USB bus, watching and recording all the packets sent to a device. These could be used to watch what the U3 recovery program does when recovering a U3. This might be a resonable start point for developing a D2 recovery driver, assuming that the process is relatively similar...

Unfortunatly i don't have a U3 so i can't try it...

[Dalmane98]

How can we flash to 2.45 if we cannot turn on our players :) .

I think this part of the problem.

Tech support at Cowon does not seem to understand that the player will not turn on or that they are not being recognized by Windows, Mac or Linux O/S's.

I also find it strange that in the email reply that mymandarin123 got they provided a link to the old firmware that is bricking D2's when they just released 3.46, which IMHO is supposed to fix the problem they created with 3.45b.

Cowon needs to release some telephone numbers that its customers can use.

With all the research I did before buying the D2, that is the one thing I did not checkout...Phone support!

[residentour]

Here i attached what happens(file monitoring) when starting and shut down U3 recovery. second part is what happens when pressing flash button ( no device conencted)

[Dalmane98]

Check this out:

No change compared to 3.45, it is just an emergency patch for people who had trouble getting their D2 to boot when they had songs with certain lyrics...

Cowon quickly released the firmware as fast as possible for such people.

Otherwise, you can safely stick to 3.45.[smile]

WARNING: This firmware is intended for Korean D2's only and there are 2 different versions (DMB & Non-DMB) and the instructions are all in Korean and support will not be provided by Cowon if you install this firmware. Remember that this will VOID your warranty - any issue with compatibility is not guaranteed.

I suggest you wait for the Global Firmware to come out - this usually comes out 24 hours later than the Korean Firmware. Can you wait 24 hours? (That is the question...)

[residentour]

Here is what happens when i do the same thing . This is a precess monitor program. Red bars shows prograss after pressing start button of the recovery program.
http://img513.imageshack.us/img513/8124/u33333iu0.jpg

[Rouge8]

The output when doing lsusb -v

Bus 002 Device 004: ID 140e:b011
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x140e
idProduct 0xb011
bcdDevice 1.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
cannot read device status, Connection timed out (110)

[residentour]

I think they can give us the Recovery drivers because U2 and G3 requires recovery for flashing firmware and always Cowon relesases them. So giving D2 recovery one won't be any problem for them.

[bassoorama]

I'm sorry for my English,and little use "Google" [rolleyes]
I also encountered the same problem when i flash v.3.45 fw ,it hangs on startup.........

I heard similar as U2\G3 ,D2 also have the same Recovery Mode ,but drivers ,i need DRIVERS!!
Who can provide?
----I'm come from China,i don't want to post it to COWON to fix,and Now my D2 is bad [cry]

[mymandarin123]

Thanks everyone for your help.

I think they can give us the Recovery drivers because U2 and G3 requires recovery for flashing firmware and always Cowon relesases them. So giving D2 recovery one won't be any problem for them.
After reading your posts regarding availability of recovery mode drivers for U2 & G3, I downloaded the fw files for the same and man they follow the similar procedure for flashing, that we have been trying for D2 so far, exception being the D2 recovery drivers.
Firmware upgrade steps for G3
1. Download the latest firmware.
2. Unzip the installation file and run 'Setup.exe.'
3. Click 'Agree' -> 'Next' -> keep following steps in the installShiled wizard.
4. After finishing installation, go to Start -> All Programs -> Cowon
-> iAUDIO G3 -> 'Firmware download' to run the firmware upgrade program.
The firmware upgrade program searches the device.
5. Remove the battery from your iAUDIO G3.
6. Press PLAY button on your iAUDIO G3, and keep pressing it.
7. Connect iAUDIO G3 to a PC by using a USB cable.
8. Keep pressing PLAY button until windows begin 'New hardware found'
wizard.
9. The wizard recognizes iAUDIO G3 in Recovery mode, and brings up the
firmware update window on the screen.
10. Click 'Start' to begin installation. Updating firmware also format flash
memory, so make sure to back up all your files before installing.
11. After finishing installation, remove iAUDIO G3 from a PC.
12. Go to Menu -> Information on your iAUDIO G3. You can check the
upgraded version of firmware.
Now why can't Cowon release D2 recovery drivers when they have been giving it out for U2 and G3 baffles me.

I'm sorry for my English,and little use "Google" [rolleyes]
I also encountered the same problem when i flash v.3.45 fw ,it hangs on startup.........

I heard similar as U2\G3 ,D2 also have the same Recovery Mode ,but drivers ,i need DRIVERS!!
Who can provide?
----I'm come from China,i don't want to post it to COWON to fix,and Now my D2 is bad [cry]
I feel extremely sorry for you, we all will try our best to get COWON to release the recovery driver for D2.Considering the quick release of 3.46 and the D2 failures all around, it's been proved beyond doubts that the fw 3.45 was a POS and had serious problems.

Just had a thought after seeing the announcement of X7 today, exity had a thread started long back asking people for their experiences from X5 and what they would like to see in X7 and the thread got lot of responses.Would it be of any use if we start a similar thread, some kind of a online petiton or poll, wherein D2'ers can vote and request COWON to release the recovery mode drivers ?

All suggestion welcome.

[residentour]

I'm sorry for my English,and little use "Google" [rolleyes]
I also encountered the same problem when i flash v.3.45 fw ,it hangs on startup.........

I heard similar as U2\G3 ,D2 also have the same Recovery Mode ,but drivers ,i need DRIVERS!!
Who can provide?
----I'm come from China,i don't want to post it to COWON to fix,and Now my D2 is bad [cry]

Sorry for your player[sad]. We are trying to find a solution. At this point you can send email to Cowon Support as these lots of mails will help us some day.

[matthew_on_the_move]

Has anyone bricked their player through installing the official global Firmware releases 2.41 or 2.45b? That would be worrying. The FW releases for Korea are not intended for worldwide use - the company use the local market as a testing ground for new features where issues can be easily addressed (a pre-beta version if you like). It may void a warranty by installing the non-official FW release so it is probably worth waiting for the globally supported versions (unless you happen to live in Korea, of course).

[mymandarin123]

There's a poll started on whether Cowon should release the recovery drivers for D2? If not done before, please voice your opinions here. http://iaudiophile.net/forums/showthread.php?t=14838

I kinda missed the poll post earlier, since now most of the time I tend to look at the D2 Troubles & Problems / D2 Firmware sub sections, hence this notification here.

[NeoDeever]

I have confirmed with my sources, that D2 has released a recovery software to service centres. However, just like the U3 they are not willing to make it public.

I have also written my own program and have confirmed that the U3 recovery driver will not work for D2.

[Barron]

I have confirmed with my sources, that D2 has released a recovery software to service centres. However, just like the U3 they are not willing to make it public.

I have also written my own program and have confirmed that the U3 recovery driver will not work for D2.
Will your program manage to recover the d2 if so i could kiss you.

Also i got another response from cowon today:
Dear Alex Barron,

Thank you for using COWON D2.

As we mentioned before, the recovery driver is very complicated. So it must be carried out by COWON SYSTEMS. That's why we do not release it for users.

Please install the latest firmware. Please use the USB port (not hub) on the back side of your computer, then press reset button on the player. If it is not still recognized, please try to connect the player to computers other than yours. If it is recognized, please back up your files and install the latest firmware again. Click below to download it.

http://www.cowonglobal.com/zeroboard/zboard.php?id=C08&page=1&sn1=&divpage=1&bmenu=download&sn=off&ss=on&sc=on&select_arrange=headnum&bmenu=download&desc=asc&no=273&bmenu=download

If you have further questions, feel free to ask us again.
Thanks again for using the customer support at cowonglobal.com.

Regards,


COWON

It feels like my discussion is going backwards as they have gone back to telling them to reinstall the firmware[cursing] i am really starting to get annoyed at cowon.

[mymandarin123]

I have also written my own program and have confirmed that the U3 recovery driver will not work for D2.
If you don't mind, could you share the code for your program ?


Also i got another response from cowon today:

As we mentioned before, the recovery driver is very complicated. So it must be carried out by COWON SYSTEMS. That's why we do not release it for users.

I seriously doubt this explanation. Recovery drivers for G3 & U2 were simple click and run apps. Members here have wrote apps for enhancing D2 functionality how complicated can running the recovery program be when compared to this, come on cowon please stop giving excuses and release the recovery software

[residentour]

OK !!! THEY SENT ME RECOVERY DRIVERS and FLASHER program . Now my player is alive. I cannot put them here. Cause they wanted me not to release.

[Dalmane98]

Yes I do...

And a previous assumption of mine was wrong and for that I apologize.

But everything worked out for the best.

Hopefully Cowon will see the results of the poll on Recovery Instructions/drivers and do the right thing.

[Dalmane98]

Great!

What were they going to charge you?

[Barron]

Great!

What were they going to charge you?
I am not sure but this is what they said:

Please remind that we have One-Year Warranty service for an year. The terms and conditions of the COWON's Warranty only apply in the the country that the COWON product was originally purchased. In your case, it is not under warranty. So you have to pay for the sending fee and the repairing cost. The total fee including repairing cost will be not yet fixed.

I think it is ridiculus that they would make me pay when i have a one year warrenty especially as it was not a mistake i caused myself. Anyway i shouldnt complain as my d2 is working again.

[hallix]

does this mean that the people at rockbox could work on it or have i got this wrong.

[ManchesterBaby]

Great news guys! Glad to see this saga has come to a happy end!

[stabbb]

thank you :]

[thebigcheese]

*cough* rockbox *cough*

[Dalmane98]

*cough* rockbox *cough*

What is that supposed to mean?

You got something caught in your throat?[biggrin]

You need to go to Rockbox and register for an account and read their User Agreement. Really read it.

It is very specific about intellectual property.

Rockbox software does not replace the OS on the player it coexists with the original system…It just boots first…It boots before the original OS.

At least that is how it works on the Sansa.

I am sure if someone at Rockbox is interested they will visit this forum and make it known; just like they did at ABI.

[Dalmane98]

For all of you posting your gmail address and asking for the recovery program, forget it.

The following is from the gmail help center:

Can I send or receive zipped attachments?

Gmail allows you to send and receive zipped attachments, as long as they don't contain executable (.exe) files. Gmail rejects all executable files as a security measure to block potential viruses.

Also posting your email address is not the smartest thing to do!

You think spammers do not troll forums for email addresses...Think again.

[man.dovvn]

If you archive the archive gmail accepts it.

[HueMann]

All these people talking about "bricking" their d2 suprises me. I also "bricked" my d2 while upgrading the firmware. But after an hour of investgation I found that by changing the name of the firmware file "0" from d2N.bin to d2.bin fixed it! After that I had my d2 back and was able to upgrade normaly. I don't know why this worked but it did. Maybe this will work for others as well.

[GSV3MiaC]

Cowon would not know HOW the player got bricked (which was actually not by the recovery software anyway - it was bricked BEFORE then) unless you told them.

'Look, the flash memory is full of complete cr&p' does not translate directly to 'someone flashed it using unofficial drivers'.

However the point is still valid that you should NOT be using desperate measures until all else has failed (including reading the manual(s)). 8>.

[banhzam]

Don't know for the term "bricked", but for a description, the player cannot boot (blocks or turns off at the opening screen) and is not recognized by any means if I plug the USB...

Would wish there was a full reset switch but it doesn't seem to exist (and I read the hardcopy and online version of the manual), so I don't actually see any other solution except using a recovery program which wouldn't need any logical drive mapping to access the player.

Taking the risk comes before sending the player back to korea which comes just before dissecting it, which is the last solution I see on my numerous possibilities list. If someone can please help me with this problem I would really be grateful (and sorry if I arrive after the battle, but it just happend, 1 week after I bought the player...).
Thanks in advance if someone can answer, PM or email me for files or any help...

[mymandarin123]

What is the firrmware version you are using ? Would it be possible for you to upload a screenshot of the boot screen of D2 in the hang mode?

[spidermoon]

It's the cursed 3.45 firmware, of course [smile] But i don't know if this happened with other firmware, with the previous firmwares, i have much more free space, about 80 Mo, and no sd card. And my trouble begins when i put a full load of music on sd card and let only 30Mo free on internal. And even when i put the sd card off, the D2 freeze on what it's seem the rebuild of music lib.

[wbbkonrad]

http://forum.mp3store.pl/index.php?showtopic=19660&pid=185225&mode=threaded&start=#entry185225
that my player .when i put plug usb to D2 i see this....

[StanRex]

Same problem here but I'm using 2.45b :

I put a lot of flac1.1.4 files on my d2 to test them (checking if their level is < 2).

I played one. It's level was >2 so it froze the player. Normal


What isnt normal though, is that when I turned it off and restarted it, well, it just wouldn't restart anymore.

I got the loading screen for some time.

Then it "zooms" on the right part of the screen

Then parts of the screen get turned to black.

Resetting the player didnt fix it

Connecting it to the computer doesnt allow me to access it.

So could someone please tell me how to fix it?

Thanks

[Dalmane98]

Someone posted a public link to the recovery files and they were downloaded so many times, that there was a 2 hour wait to download the files unless you purchased an account at the site he posted them on.

IMHO, Cowon probably downloaded them also and will just make a slight change in the firmware and render the files unusable.

The only thing you stated is that your D2 will not start...Anything else happen or not happen?

[torrentseed]

Someone posted a public link to the recovery files and they were downloaded so many times, that there was a 2 hour wait to download the files unless you purchased an account at the site he posted them on.

IMHO, Cowon probably downloaded them also and will just make a slight change in the firmware and render the files unusable.

The only thing you stated is that your D2 will not start...Anything else happen or not happen?
Don't make assumptions without any supporting points.
Those recovery drivers were distributed by COWON to the repairs centres around the globe. You could tell that by looking at the powerpoint manual in the "Driver" folder which is written in Korean, which happens to be my native language. And I'm pretty sure that powerpoint is a scan of 2 pages from the COWON technician manual.

[Dalmane98]

Don't make assumptions without any supporting points.

And who might you be to tell me that I cannot state my humble opinion? [biggrin] This forum is full of opinions and assumptions.

Those recovery drivers were distributed by COWON to the repairs centres around the globe. You could tell that by looking at the powerpoint manual in the "Driver" folder which is written in Korean, which happens to be my native language.

The PowerPoint I saw is all in English, except for one picture. If you ungroup the picture on the second slide on the left hand side you will see that someone just grouped six pictures together. One of which might be written in Korean. I will take your word for it because I do not read Korean.

And I'm pretty sure that powerpoint is a scan of 2 pages from the COWON technician manual.

I do not agree. AFAIK you can not scan anything into PP. I think it was just a simple PP someone made to to show you what you need to do to configure the program that is not written in either the Korean or English language. You should also look at the properties for the PP. It was originally created in 2004. If I was scanning pages from a manual, I would have scanned them into Adobe...[biggrin]

If you look at the post from tay4i (3 before yours) you will see that a link has been removed from his post and the reason why it was removed.

I followed the link when it was first posted and the file had been downloaded so many times that you got a message stating the quota had been exceeded and to try again in two hours unless you created an account and/or paid for the download.

So now we both know what happens when we make assumptions...[smile]

[Dalmane98]

(Replying to my previous post...)

Here's my D2 (with firmware 2.46) after uploading various FLAC 1.13b files and two Ogg Vorbis files containing subsong indexes:
http://www.sendmefile.com/00545525

Michael

Your Link does not work...I tried IE and FireFox.

[Dalmane98]

That one works, but you really should try sharebigfile.com.

It works all the time, with no wait times and none of the junk running in the background...Well not as much anyways.

[ManchesterBaby]

What's the obsession with this video posting lark? Why do you feel you require some kind of 'proof' that their D2 is actually bricked? Does it really matter? (Besides, how is a video any evidence? I could quite easily fake a video that shows a 'bricked' D2.)

Bricked or not, distributing this software is still unauthorised and presumably illegal. Just do it or don't do it - don't require people to 'justify' requiring the software. It's not going to make any difference.

[man.dovvn]

It is my understanding that the Cowon representative said not to spread the software around, not to limit people from recovering their player, but to avoid reverse engineering. I believe that the person who recieved the recovery program does not want to get in trouble, and to respect his wishes, the current system was put in place. Would you want to get sued so that people wouldn't have to make a 30 second video?

[Dominic]

he/she cannot give out the programme to every tom dick and harriette who say their D2 is bricked, just read this thread and you will see why manchesterbaby.

[alec]

This is my video of my player 2 day ago
http://download.yousendit.com/D72485740E82C5FE
But i dont think i still need the file because my D2 became worse. It can not even be turned on. Any suggestion ?
I need the info of warranty service of Cowon korea because i bough my player
there. can someone give me?
Btw, thank all for caring.[sad] [sad] [sad]

[Dominic]

we do care, but we have to be careful, if the recovery drivers get taken from us how can we help anyone?imagine if they had been taken from us and you came looking for help, we'd have to say there is nothing we can do anymore and you'd have to go straight to cowon.

PS sorry for "man.dovvn"'s response to you, it wasn't polite at all.

[mymandarin123]

Check this thread, contains information to contact Cowon Korea, although the thread mentions about X5, IMO it should be same for D2.
http://iaudiophile.net/forums/showthread.php?t=15245&p=133704

What exactly happened during the firmware flashing, could you retry flashing again?

This is my video of my player 2 day ago
http://download.yousendit.com/D72485740E82C5FE
But i dont think i still need the file because my D2 became worse. It can not even be turned on. Any suggestion ?
I need the info of warranty service of Cowon korea because i bough my player
there. can someone give me?
Btw, thank all for caring.[sad] [sad] [sad]

[ManchesterBaby]

I still don't think it's necessary. If cowon said not to distribute the files, and you want to respect their wishes (as you seem to be implying) then do just that: don't distribute the files. If cowon said "you can give the files to people who have bricked D2s, but no-one else" then fair enough, but i very much doubt they would have said that. Posting a video of a bricked D2 doesn't change the legality of the situation: it's still illegal.

Besides, hundreds of people must have the recovery drivers by now. If someone really wanted to get hold of it to 'reverse engineer' the D2, they wouldn't have any trouble. Why cowon would be bothered by this i'm not sure (any 3rd party 'hack' could only benefit cowon's sales in the long run); however if they really were bothered they wouldn't have released the driver to anyone in the first place.

[Dominic]

Potentially this could be a long discussion, if it truly bothers you start a new thread to find answers.

[ManchesterBaby]

I'm not really that bothered. I don't mean to have a go, i just wanted to voice my opinion (and man.dovvn's snappy response in post #204 persuaded me to). After all, that's what a forum is for! [smile]

[Dalmane98]

I wish that mymandarin123 would close this thread or that the Mods would.

It served its purpose.

Anyone that has a bricked D2 should start a new thread for their problem.

Most of the folks here will not read 15 pages of posts to get the history behind the whole thing any way.

[Dominic]

yerp, contact a mod/admin in that case mate.

[Dalmane98]

I sent mymandarin123 a PM about closing the thread...

[mymandarin123]

I don't see any options under Thread tools to close the thread, mod/admin will have to take the call here.

[Dalmane98]

Are you going to ask a mod/admin to close the thread?

I think the originator of the thread has to ask for it to be closed.

[Dominic]

Nope anyone can. Just give a reason.

[wader]

Well, all this discussion about closing the topic, not wanting to revisit old ground, etc. got me reading :) .

So . . . I don't have the recovery drivers because they are not meant for public consumption (well, at least they're not supported in such a manner), but hopefully COWON Support would send them to me if my D2 inexplicably hung within the next year or less and there were no other solutions to try. Otherwise, my little D2 would possibly remain a fish out of water. Got it.

- wader