This topic will be about the AdfuUpdate.inf file you need to change to get your player as an ADFU Device.
ADFU Device is needed for dead players where you want to update a new working firmware.

You can find the AdfuUpdate file into the download section.

Now, each mp4 Player has its own "ID". To get to know your player's ID; you need to go to :

Control Panel - System - Hardware - Device Manager -

Ther you have to find your MP4 player. normally it's an "unknow device".

right klick on it and choose "properties" - Details -

There you will find teh identification you need. It will look like this :

USB\VID_10D6&PID_6982\2002-78

The VID and PID number is what we need to edit into AdfuUpdate.inf, in order that Windows knows that this file has hardware information for the selected device.

Example:
If your VID is 10D6 and your PID ff51, you have to change adfu file into this :

[Upgrade]
%USB\VID_10D6&PID_ff51.DeviceDesc%=MDisk.install,USB\VID_10D6&PID_ff51

and this last line :

[Strings]
MSFT="MP3 Player"
MfgName="MP3 Player"
USB\VID_10D6&PID_ff51.DeviceDesc="ADFU USB Device"

Good luck

Another question will be; After a wrong firmware flash, a device device can be shown as an Unknown device with the following information :

USB\VID_0000&PID_0000\5&39669908&0&4

Changing the AdfuUpdate.info to VID 0000 and PID 0000 isn't any help. Windows still says that this file doesn't contain any hardware information. so I you can't have your device recognized as an ADFU Device to update another firmware right now.

Isn't there any trick to force windows using this inf file so that you can update the firmware;
or, is there no possibility to edit yourself the VID and PID info on the mp4.
Before changing the firmware, VID has been 10D6 and PID ff51.
It has changed to 0000 afterwords, so it can be changed. Even better, it should be possible to edit it back to what it was before.

Who has got some suggestions

I will post a "how to" later on

A lot of you asked me how the AdfuUpdate.inf file has to be like, so here is one with more players you can copy and paste into your file.
Don't forget to ad your PID number if it's not there

---

[Version]
Signature="$CHICAGO$"
Class=USB
ClassGUID={36FC9E60-C465-11CF-8056-444553540000}
provider=%MSFT%
LayoutFile=LAYOUT.INF
DriverVer=11/22/2006,3.3.0.0

[Manufacturer]
%MfgName%=Upgrade

[Upgrade]
%USB\VID_10D6&PID_8888.DeviceDesc%=MDisk.install,USB\VID_10D6&PID_8888
%USB\VID_10D6&PID_ff51.DeviceDesc%=MDisk.install,USB\VID_10D6&PID_ff51
%USB\VID_10D6&PID_ff61.DeviceDesc%=MDisk.install,USB\VID_10D6&PID_ff61
%USB\VID_10D6&PID_ff63.DeviceDesc%=MDisk.install,USB\VID_10D6&PID_ff63
%USB\VID_10D6&PID_ff66.DeviceDesc%=MDisk.install,USB\VID_10D6&PID_ff66
%USB\VID_10D6&PID_ff79.DeviceDesc%=MDisk.install,USB\VID_10D6&PID_ff79

[PreCopySection]
HKR,,NoSetupUI,,1

[DestinationDirs]
umss.files = 10,System32\Drivers

[MDisk.install]
CopyFiles=umss.files
AddReg=umss.addreg

[MDisk.install.NT]
CopyFiles=umss.files
AddReg=umss.addreg

[MDisk.install.NT.Services]
Addservice = AdfuUd, 0x00000002, AdfuUd_AddService

[AdfuUd_AddService]
DisplayName = %USB\VID_10D6&PID_1160.DeviceDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\AdfuUd.sys
LoadOrderGroup = Base

[umss.addreg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,AdfuUd.SYS

[umss.files]
AdfuUd.sys

[SourceDisksNames]
1000 = "USB Mass Storage Device",,,

[SourceDisksFiles]
AdfuUd.SYS = 1000

[Strings]
MSFT="MP3Player"
MfgName="MP3Player"
USB\VID_10D6&PID_8888.DeviceDesc="USB ADFU Device"
USB\VID_10D6&PID_ff51.DeviceDesc="USB 2.0 (FS) ADFU Device"
USB\VID_10D6&PID_ff61.DeviceDesc="USB 2.0 (HS) ADFU Device"
USB\VID_10D6&PID_ff63.DeviceDesc="USB 2.0 (HS) ADFU Device"
USB\VID_10D6&PID_ff66.DeviceDesc="USB 2.0 (HS) ADFU Device"
USB\VID_10D6&PID_ff79.DeviceDesc="USB 2.0 (HS) ADFU Device"

---

Greetings
Jim

I solved the problem to reset the memory in order that Windows doesn't read from it, but only detects the player hardware in order to be able to get him again into ADFU after a completely wrong firmware update.
This can bring dead players alive again, for example mine, which had a PID and VID with 0000 (see above) after a completely wrong firmware update.
After plugging in your player, your OS (Windows) is reading the firmware details in order to install the required drivers for the USB device. But, the problem is known, that if you have a wrong firmware, this one will give wrong information’s about the device.
The goal will be, to reset the player as it was before any firmware has been put onto the player. To bring him in manufacture status. But for embedded devices, this is way to complicated to discuss here, because the only way will be to make a hardware flash via ICE.
The trick, we will be doing, and which worked very fine in my case, is to shorten 2 or more of the I/O legs during the connection process, so that your OS won’t be able to read from the firmware

The following has only be done on Glacier Like players and will be at your own risk. (Anyway, my player was dead, so… and now it came back to life from the dead). This procedure can burn completely your memory if done wrong, so be careful

Lets go go go,…

First, switch the player OFF with the upside ON/OFF button, remove the battery, and dissassemble your player, but I think, you already have done this
Now, plug in the USB cable ONLY into the player, not in your computer.

http://www.mympxplayer.org/album_showpage.php?pic_id=499

Now, your memory should show up a round mark on the top left. (We use this to count the pins, beginning at NC 1, but this is not important now)
It is important that you count, on the opposite side of the mark, 4 pins beginning at the bottom. This first 4 pins are 4 NC pins, and are NOT to be touched ! The next 4 are I/O pins, an then again NC pins. The I/O legs are the ones we want to work on.

http://www.mympxplayer.org/album_showpage.php?pic_id=500

Let’s resume, you have the battery removed, the player is switched to OFF with the upside button, and the usb cable is plugged into the player only. Perfekt

Let’s take a fine screwdriver now and put him on the 4 pins in order to shorten them.
Note: it is better to shorten only 2 or 3 I/O pins at the beginning, BUT NEVER shorten more than 4 ! or one of the neighbour NC pins ! This can burn your memory !

In fact it is easy, just try to stay in the area of the four I/O pins as shown on the picture. Put your fine screwdriver there, and now, (you will need more hands), ask someone to plug-in the Usb cable in the computer WHILE you are still shortening the pins. Yes, you have to stay with the screwdriver on the pins while the player is connected to the computer. How long ? well, until you see that your OS is detecting an USB device and asks for drivers or (in my case) installs it directly as an ADFU device if you have the ADFU driver already on your system. Then you can remove the screwdriver and open your upgrade utility to upgrade a new firmware.

It is possible, that your old ADFU driver doesn’t work anymore, because the informations now given by the hardware to your OS are different as the ones the wrong firmware has been telling all the time before.

If the ADFU driver doesn’t work, read above how to get your PID number of the player and adapt your AfuUpdate.inf

I hope I made myself as clear as possible, but I want to remind, that this is the last known possibility to get your player back into manufature status in order to load a firmware and that it is not without risk…

Good luck

Best regards
Jim

try using this aduf file instead of your own
it worked for me
http://www.mympxplayer.org/driver-adfuud-sys-files-df364.html

Thank you

but I have no problem with my player, I only try to give advices.
But you are right, this file you mention, is right for 2 players, but most players are not recognized.
So you can use this on player with PID 8888 and ff51 (like mine).

So the goal of this topic is to understand the working of the file, so it can be used by anyone.

Even though, thank you, because your goal was to help, which is very much appreciated around here.

Regards
Jim

_Jimmmmmmmmmmmmmmmmmmmmmmmmmmm

You are the mannnnnnnn

Atleast i sorted out this ADFU even that uxcell chat support not able to help me and said " may be you are using older version of windows " :s


Thanks mann

I think it would be a good idea to have a universal ADFUupdate.inf file that contains all the relevant PID characters. This way, anyone who needs an ADFU file could use the universal one to install the ADFU server.

However, this would need the input from various people as most players are differently configured and uses different PID characters.

Hi Jim!

I`m having quite the same problem as you. My device is shown as USB\VID_0000&PID_0000\ at WindowsXP. But it seems the internal memory of my device is a different one. I`ve tried to shorten the 4 pins as shown in your tutorial but had no success... Could you give me a hand in solving this? The internal chip here is a MIRA P2V28S40BTP. I've found the MIRA DRAM specifications for that and also I'm including a picture of my actual device! You can download them here:
http://rapidshare.com/files/78328671/mira.rar.html





Well, I hope you can help! TIA,

Monkey

Helloa;

@Monkey_@@

First of all, yes, you got another memory as I do. That's why I want to make an important Alert right away to everybody !! I know you are pissed off if your player isn't working anymore, but please, don't try to shorten pins you are not sure off !!
You, Monkey_@@, have been luky not to touch any power supply's during shorting the same pins on your memory. You have been working on Adress inputs, which is no help, so it couldn't work

Second, I have to saw WOW, nice work you did, perfect picture of your chip, nice quality and hey, WOW, finding this paper on your chip on the Internet is a very interesting job, and very helpfully for me to help you right a way. Thanks

Now, let's see what we have to do. First of all, I want everybody to understand and learn something by the way. The goal is to disturb the communication during a boot up. We do this by shorting some (at least 2) pin's (and not any pin's we think of ) We only shorten the "Data I/O" pin's (Data Input / Output). So very simple.
You need at least 2, and ONLY I/O pin's.
These have to be shortened BEFORE the boot-up of the player (before the plug-in, and during plug-in, until Windows has fully understood that there is a new device plugged-in)

If you have found a documentation about your memory, you have to find the Data I/O pin's The pins are always numbered (1-2-3-4-5-...) and the numer 1 is always located nearest the little hole. you count from top to the bottom and then you contine around from the bottom again to the top of the other side.

@ Monkey_@@
You have 6 possibilities:
4 and 5
7 and 8
10 and 11
44 and 45
47 and 48
50 and 51

The only problem I see with your chip, is that all this possibilities are located near to a "power supply" or a "ground" which is bad. You really have to take yourself time and patience to do this to not touch any pin next to. you will need a very good screwdriver

I wish you luck, because you will need some, with all these possibilites you will have to try some more times to get it work. I would even try two at the same time if you have a frind who can do the plu-in job, you can concentrate on shortening 4 - 5 - 50 - 51 at the same time. I think that will be the best solution.

If you are not sure about this, tell me, I can always send you back your picture with the pins market in red. Otherwise, take page 2 of your pdf document on which I worked on.

Best regards;

_Jim_

Well, thanks Jim! I've tried all the 6 possibilities, including two of them together... but no results.

Actually, the device didn't turned on when the pins were shortened! I've isolated the other pins to protect the chip so I could work better, take a look:


But I think I'm gonna try again another time... with a little help from a friend... another question:
The device was working fine before I've made the procedure described here by sableroku but I could connect it to WindowsXP, so I decided to try that upgrade. But when I got that blue "usb drive" screen I still could connect it (0000 device id) to XP. So, is there a way to avoid that blue screen when I turn it on? The reset button seems to do just nothing!!!

ID is

USB \ VID_10D6 & PID_FF66 \ 5 & 154C0453 & 0 & 3


How Adaiqa

I did follow all instructions and worked good until I got error from window stating that the USB 2.0 (FS) ADFU Device did not pass window logo testing and will not be installed...I am logging in as admin and still keep rejecting the installation how can I get around this/
Thank you and god bless
Norman