The death of WD ROM recovery tool: U instruction

[longlife]

Help!!!!!!!!!!!!!!!!!!!!!!

Someone please guide me.....What is written above???

I have WD hdds which i have to " Regenerate rom.........." both of Card and in HDD.

Salvation data / DFL tolls are toooooooooooooo costly....

It seems to be a fair solution.......

[bigman4hacking]

help full but i need it for 15xx pcb
any solutions
i want to know how to enable the external rom with the resistor anybody know about this idea !!

[thatdellguy]

Salvation data / DFL tolls are toooooooooooooo costly....

[louis]

Here is what he's saying
1. Take WD PCB(ARM based) that has erased or incompatible ROM image (bricked PCB)
2. Connect serial port as shown
3. Short some magic pins to start X-Modem sequence in MCU boot code(E112 and 3.3V for PCB 13xx, 1335 for example). The number is etched on PCB as 2060-701335-xxx
4. Select correct ROM image file and flash it to the drive with the program. Program will use special loaders (called EraseL.dll, SystemL.dll) to do so
5. Per my understanding, provided utility supports only 128KB flash files (external flash chips). For 192KB flash the program will look for Erase.dll and System.dll files that are not provided, thus will not work with those.

I have doubts that the code posted here will work. I had a look inside the "spice9ray"-ed code of this Utility. (assuming that the c# I saw it's close to it's origins) When it builds the header for the data to be sent to the xmodem...it gets the memory_address (offset 16 in the header...where to copy the code) form the rom.bin..and patch the eraseL header. in this way...the bootstrap's terminal code..will "map" the code from "eraseL" at the location where it should be the firmware's "kernel loader" mapped...but instead...it executes an entry point for this injected module...which doesn't exist (FFE1F299). Beside..the EraseL code has many branches to nonexistent functions which points inside the bootstrap's code (ie. for my pcb 128k rom 2060-701336-003 REV A) Doesn't fit in my "terminal researches"

Code:

          i1 = System.BitConverter.ToInt32(arrbyt, 16);//arrbyt holds flash_to_upload.bin
            i2 = 0;
            while ((i2 < 4))//patch eraseL.bin at the same location
            {
                arrbyt1[16 + i2] = (byte)(i1 >> ((i2 * 8) & 31));
                arrbyt1[20 + i2] = arrbyt1[16 + i2];
                i2++;
            }
            arrbyt1[20] += 1;//the entryPoint to be called by the Bootstrap after injection points nowhere...FFE1F299+1 (or somwhere inside a working firmware's erase function)




[pepe]

I have laughed my butt off how that tiny terminal code converts hex digits to binary and vica versa... they are braindead at marvel...

[pepe]

btw, did anybody notice that samsung MCUs have very similar loader at a different address?

[SevereK]

thanks alot
but i want explaining about how to connect pcb with serial port ?

QQ370909447

HDD not started if connect RX TX how at this picture...

[Doomer]

btw, did anybody notice that samsung MCUs have very similar loader at a different address?

Majority of Marvell ARM MCUs have tiny console if that's what you are talking about.

[WhitePP]

Excellent work.

[dragon007]

nafangkuaixiu,
Hi I have a brick wd pcb that i want to reprogram the rom.
The rom is corrupted due to a power supply problem.
I have the correct rom.bin file and will like to get this to work.
I have download your demo tool to reprogram the rom, the drive that i have is a
WD500AAJS with PCB : 2061 -701477-10005P

I want to ask ware and how can i get the the registered version as the trail version only supports version 13XX series motherboards, the registered version supports 13XX, 14XX, 15XX series motherboards.
Your reply will be appreciated.

[SANJAY]

I want original ucommand tool sir.
I reply qq but not response

[Amarbir[CDR-Labs]]

I want original ucommand tool sir.
I reply qq but not response

Lol,
You can qq me if you want free services for bricked pcb's

[LoboX]

Seems to be a good solution for bricked PCB. Need to try it and see.