D2+ non-tcctool procedure for DAB D2

[oneforall]

Hi D2 Lovers,
Does the D2+ non-tcctool procedure require special files. For example, does it need a special D2N_159_multiboot_fn or D2N_459_multiboot_fn (folder) file, as described in the steps by Who am I and crashdebug?

Cheers.

[Who Am I?]

Hi D2 Lovers,
Does the D2+ non-tcctool procedure require special files. For example, does it need a special D2N_159_multiboot_fn or D2N_459_multiboot_fn (folder) file, as described in the steps by Who am I and crashdebug?

Cheers.you might want to ask crash about this one. as far as i know there isn't any Modified Files for 1.xx or 4.xx users. if you wanted to use tcctool then that would work.

[m21rt]

i set up a multiboot with the original 3.57 FW and didn't have any problems so I think it should work. If it doesn't work i don't think it would brick your D2 anyway.

[EddieE]

The tcctool way isn't difficult to do and works perfectly anyway.

[Carewolf]

The tcctool method didn't work for me on my D2 DAB. I may try again, but it followed the exact procedure several times, just to make sure I didn't screw up. I would prefer trying the non-tcctool method next.

[Who Am I?]

you need to make sure you Format with the d2.bin File from Folder 0 from Firmware 4.59 or .48 first and then the tcctool method should work.

[EddieE]

The tcctool method didn't work for me on my D2 DAB. I may try again, but it followed the exact procedure several times, just to make sure I didn't screw up. I would prefer trying the non-tcctool method next.

The problem with doing the exact proceedure is the file name of the 1/4.xx firmware is different to that of the 2/3.xx firmware. You need to change the name of it when doing the command prompt business.

Here is a broken down description of the method for DAB users:

-Download Tcctool http://download.rockbox.org/utils/tc...tool-win32.zip (http://download.rockbox.org/utils/tcctool/tcctool-win32.zip)

-After unzipping it, take the folder inside with the contents, rename it tcctool and put it in the C:/ root directory

-Put all of the firmware files for 1.02, or 4.02 into the same folder.

-Connect the D2 normally and take the file from the 0 folder from your current firmware (not the D2+ files, the firmware you are using now) into your D2 root, disconnect and turn on, just like you would with any firmware upgrade. It should turn off automatically when it's done.

-Now, hold onto the M button on your D2 and reconnect it while still holding it down.

-Windows will ask to install and find new drivers for hardware. Press cancel.

-Go to "Control Panel" and find the Hardware Manager. The D2 won't be named, so make sure no other unnamed hardware is conncted to your computer so it'll be easy to identify.

-Right-click on the D2 and select "Update Driver Software"

-Chose to Locate Driver Manually and select the tcctool folder

-Go to Start > Accessories > Command Prompt and then input:

cd C:\tcctool

Hit enter, and then input:

tcctool -d cowond2 d2_p.bin

-Now find the D2 under "My Computer" and delete all Folders. This was a scary bit for me, but don't worry it's fine. Next copy and paste d2_p.bin file into the root and then disconnect the D2.

-Again, connect the D2 at the same time as holding the M button

-Go back to the command prompt prorgramme and do the same as above, inputting: cd C:\tcctool, enter and then tcctool -d cowond2 d2_p.bin enter.

-Disconnect and reconnect without holding any buttons, and you are now essentially at the same place you are after adding the 0 file of any firmware, except your D2 is now a D2+! So add the two firmware files (rs and ft), disconect. Power on and the new firmware will load.

All systems go!

Enjoy [biggrin]

[Who Am I?]

nice one EddieE :)

[oneforall]

Thanks for the hints and suggestion guys. I was infact successful with my transition from 1.59 (D2) to 1.02(D2+) even though I have Vista (without driver issues). However what if I specifically would want to go for a multi-boot possibility? The tcctool method did not mention this. Any ideas?

[Cowonophile]

I've followed your instructions EddieE and after the second common prompt inputting of tcctool -d cowond2 d2_p.bin the D2 briefing appears to be botting with 4.02 showing as the firmware. however when i reconnect it boots showing 0.0 firmware and i just get a white screen with a few lines on it and it then shuts down. I tried deleting all the files, putting in the other two files (rs and ft) to no avail.

What should i do next????

[EddieE]

Sorry Cowonophile idk, the proceedure I laid out (adapted for DAB from WAI?'s instructions) worked fine for me, that's why I was happy to post it. It also worked for someone else who PMed me for help before, so I figured it would work for everyone.

Are you certain you followed it precisely?

[Cowonophile]

EddieE I think I did follow the instructions to the letter but clearly went wrong somewhere. I have now used tcctool to unbrick the D2 using Fw 4.59 and its working fine wth that!

On reflection after the first use of tcctool at the command prompt, the D2 did not appear in 'My computer', I may have disconnected and reconnected to get it to be recongnised. I dont think I reconnected that time by holding the M button! but had to do something as the D2 did not appear!

No need for an apology, I realise we all use the advice on this forum at our own risk and I still have a working D2 it just doesn't have the + yet. I may try again but it would be useful if others could post saying that the process works, or if they replicate my experience.

[jennysmate]

My experience was similar to Cowonphiles. Ended up with a bricked D2. Had to use tcctool on an old pc, as couldnt get tcctool to work on vista ( despite using the F8 trick). Back to 1.59 now.

[luhrm]

First I ended up with a bricked D2 DAB fw 4.59 but I don't accepted it. So I went over and over again. After I'd tried it several times (3 hours later) it suddenly worked.

[EddieE]

Glad it worked, eventually. :-)

Odd that the procedure seems to work perfectly well for some and yet brick others. Guess persistence is the key.

[luhrm]

Hello and thank you for your description.
After I testet the new FW 4.02 I have to say that the effort was worth it.
The new sound is breathtaking. I listen to (mostly .oog) music with (modded) Sony MDR-EX 90 LP.
The quality of Audible books are somtimes not so good. I often got annoying hisses in my ears while I listen to them. Now I can enjoy even the low quality books. With my old FW 4.59 I listen to music only with minimal adjustments because the sound messed up every time when I tried a little more. Now I can play with all the little things the D2 has to offer (BBE; MP; EQ; Bass; Eq, Stereo ...) without any drawback.
So I recommend the FW change.

[mookster]

Fantastic tutorial, worked first time for me, loading FW 1.11. Unfortunately it's in a strange language to me (Korean I guess) so I'll have to try and sort that out.

[flacfiend]

Thanks EddieE! Works great for me. I went from D2 DAB 4.58 to D2+ DAB 4.02.