SamyGO

Why did you read it byte to byte? e2p returns word (double byte) You have to use: iwpriv ra0 e2p 04 iwpriv ra0 e2p 06 iwpriv ra0 e2p 08 and check if it confirms with your MAC address in byte order. Example: if your mac is: 34-08-04-31-85-93 you will get: iwpriv ra0 e2p 04 -> 0x0834 iwpriv ra0 e2p 06...

First 24 bits which identify vendor are E4-7C-F9. I don't know if i will get wis09agbn in my hands this weekend, if i get it i will upload dump immedietly. You can change mac easily - but you have to remeber abut cardinal computer rule - younger byte, older byte. So you have to flash 04 - 4e, 06 - c...

wikidevi says about Samsung_WIS10ABGN it is Ralink RT3572 so it should be easy to clone but ..... does any one know VID and PID for it?

OK. I will experiment with cloned mac of my brothers dongle. I made a vm with drivers and script to make stick with samsung vid and pid accessible again as ra0. I will flash first 6 bytes of mac to his and see what will happend. If i will be able i will try to copy his whole eeprom with script from ...

OK! I flashed it under VBox with Xbuntu 11.10! Used this toutorial http: kaustav. codebinders. com/2011/10/install-dwa-125-driver-on-ubuntu-1110.html However ... i don't see any network and get wrong mac if i put network configuration by hand :/ I have ue40d5500. Any hope? It works also under window...

Pid and vid was untouched. Compiling custom driver will not help.

Is it possible that p2e addresses were wrong and p2e changed some other info or even firmware under this addresses?

VID and PID are visble but dongle is not recognized by its drivers under linux or windows. Windows starts to install driver and finish with communicate that it is not compatible. Already checked .inf and this vid and pid are correct.

I have second one and i hestiate to try whole procedure again

In my case dwa-125 a3 after e2p returned nothing. I had to ctrl+break after few minutes of waiting. Then pid and vid didn't change but dongle was bricked and went to trash.