WD Community

Debricking My Cloud Mirror gen1

Hi,

I inherited a My Cloud Gen1 without disks. I’ve put 2 WD 3TB disks in. Now I want to debrick it - preferably with Debian. Can someone point me to a good tutorial and files I need? I found a tutorial by fox_exe but that’s only for mycloud (not the mirror edition).

EDIT: I found someone who installed debian 10 on a similar device (mycloud ex2 is similar right?) here: Unbrick my My Cloud Ex2 from blue blink after using self compiled kernel . Can someone tell me which pins I should connect VCC/GND/TX/RX to? And maybe a bit more help in how to boot it with the files given uImage/uRamdisk, not too sure how to supply them while booting.

EDIT2: if someome could tell me how I can login on the web console? Somehow it still boots to some console but I can’t log in. I guess this is a firmware chip booting. If I can “debrick it” from there, that’d also be cool.

Thanks a lot

OK so got a little further :slight_smile: . I decided I wanted to build my own kernel (linux-stable 5.15.11 at the time of wrinting) so I downloaded the .dts file and started building. I got to the point where I’ve got the lib/ directory with modules and an uImage file.

Some (a lot of) questions I have now, because I’m not sure how to proceed:

  • How should I connect the pins of the serial console? There are soldering connections named JP2 then another one, then 1 to be left empty and then another one. Which pin is which?
  • I think I need a ramdisk of some sort, how do I create it? This should be something like this?

I downloaded an old uRamdisk from 3.2.40 from the website of @Fox_exe . I have no idea if I’m doing something useful (using an old ramdisk image) on the last line in the code below, but at least the command was successful :slight_smile:

user@htpc:~/Documents/wdmcm-compile/linux-stable$ mkimage -A arm -O linux -T ramdisk -C gzip -d init.cpio.gz initramfs.uImage
mkimage: Can't open init.cpio.gz: No such file or directory
user@htpc:~/Documents/wdmcm-compile/linux-stable$ mkimage -A arm -O linux -T ramdisk -C gzip initramfs.uImage
mkimage: Can't open (null): Bad address
user@htpc:~/Documents/wdmcm-compile/linux-stable$ mkimage -A arm -O linux -T ramdisk -C gzip -d ramdisk-of-mybooklive-linux.3.2.40-not-sure-if-useful initramfs.uImage
Image Name:   
Created:      Sat Dec 25 08:35:12 2021
Image Type:   ARM Linux RAMDisk Image (gzip compressed)
Data Size:    2680272 Bytes = 2617.45 KiB = 2.56 MiB
Load Address: 00000000
Entry Point:  00000000
user@htpc:~/Documents/wdmcm-compile/linux-stable$ binwalk initramfs.uImage

DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             uImage header, header size: 64 bytes, header CRC: 0x6352C42D, created: 2021-12-25 09:01:53, image size: 2680272 bytes, Data Address: 0x0, Entry Point: 0x0, data CRC: 0xC998FD87, OS: Linux, CPU: ARM, image type: RAMDisk Image, compression type: gzip72 bytes, Da, image name: "": ""       a Address: 0x0, Entry Point: 0x0, data CRC: 0xC998FD87,OS: Linux, CPU: ARM, image type: RAMDisk Image, compression type: gzip
64            0x40            uImage header, header size: 64 bytes, header CRC: 0xEA7F7217, created: 2016-04-13 00:40:12, image size: 2680207 bytes, Da                                07 bytes, Data Address: 0xE00000, Entry Point: 0xE00000, data CRC: 0x8B2C08D7, OS: Linux, CPU: ARM, image type: RAMDisk Image, compressionimage name:a Address: 0xE00000, Entry Point: 0xE00000, data CRC: 0x8B2C08D7, OS: Linux, CPU: ARM, image type: RAMDisk Image, compression
type: lzma, image name: "Ramdisk"
128           0x80            LZMA compressed data, properties: 0x5D, dictionary size: 16777216 bytes, uncompressed size: -1 bytes

After the creation, do I

  • uImage and uRamdisk should go inside a boot/ folder on a FAT32 formatted usb stick. Is that correct?
  • If I want to make the boot permanent, on which partitions do I install uRamdisk and uImage?
  • Once I got it to boot, how do I put on a “vanilla” debian on it?

parted /dev/sdb
mklabel gpt
mkpart primary 1049kB 2149MB
mkpart primary 8591MB -1MB
mkpart primary 7517MB 8591MB
mkpart primary 2149MB 3222MB
mkpart primary 3222MB 4296MB
mkpart primary 4296MB 6443MB
mkpart primary 6443MB 7517MB

Hi @buco,

Please contact the WD Technical Support team for best assistance and troubleshooting:
https://support-en.wd.com/app/ask

@Keerti_01 : Are you a bot or a real person. In case of the former. Did you actually read the thread thoroughly? I highly doubt whether WD Technical Support will assist me with installing Debian ~Vanilla over the original OS.

I take it this is the link you were referring to?

It’s for the MyCloud Mirror (which is identical to the EX2 except for one software feature).

1 Like

thanks for the tip :slight_smile:

Hello,

I have a WD My Cloud Mirror Gen1 (model WDBZVM0040JWT-20) that is stuck in boot and no longer accessible via the web interface. I want to perform a full “unbrick” using the Fox_exe recovery method, but the original recovery files are no longer available from the usual mirrors.

Specifically, I’m looking for:

  • uImage-wdrecovery (Mirror Gen1)
  • uRamdisk-wdrecovery (Mirror Gen1)

The original files were in the Fox_exe repository under:
WDMyCloud/WDMyCloud-Mirror/Developing/
but the links are now offline.

If anyone still has a copy of these two files (or the full recovery ZIP/tar.gz for Mirror Gen1) and could share them via a cloud link or attachment, it would be greatly appreciated.

Thank you in advance for your help.

Man, it’s been a couple of years with this :slight_smile:

I guess these might be the files you’re looking for. But to be honest, I have no idea what exactly these files contain. Is it a backup of the original disks (I guess so) or is it a backup of me after I flashed Debian over it? I don’t know :slight_smile:
root@zed:/unicorn/documents/nanddump-backups-wd-mcm-gen1# ls -lah total 446M drwxrwxrwx 2 1024 users 11 Dec 29 2021 . drwxrwxrwx 25 root root 37 Apr 17 21:07 .. -rw------- 1 1024 users 255M Dec 29 2021 mtd0-pxa3xx_nand-0.dmp -rw------- 1 1024 users 5.0M Dec 29 2021 mtd1-u-Boot.dmp -rw------- 1 1024 users 5.0M Dec 29 2021 mtd2-uImage.dmp -rw------- 1 1024 users 5.0M Dec 29 2021 mtd3-ramdisk.dmp -rw------- 1 1024 users 201M Dec 29 2021 mtd4-image.cfs.dmp -rw------- 1 1024 users 15M Dec 29 2021 mtd5-rescue-firmware.dmp -rw------- 1 1024 users 19M Dec 29 2021 mtd6-config.dmp -rw------- 1 1024 users 5.0M Dec 29 2021 mtd7-reserve.dmp -rwxrwxrwx 1 1024 users 220M Dec 29 2021 nanddump-all-partitions-wd-mcm-gen1.bz2 root@zed:/unicorn/documents/nanddump-backups-wd-mcm-gen1#

Are you sure those two files (uImage-wdrecovery and uRamdisk-wdrecovery) were in the Mirror Gen one Developing subfolder on the old Fox_exe repository? From what I remember, those two files were in the My Cloud Gen 2 Developing subfolder. Both files are still available in the My Cloud Gen 2 Developing at the following links:

https://fox-exe.ru/WDMyCloud/WDMyCloud-Gen2/Developing/
https://wd.hides.su/fox_exe/WDMyCloud-Gen2/Developing/

Those two files are what one used to get the My Cloud (possibly the single bay Gen 2 version) to boot into a “recovery” web page from which they could upload the firmware.

See the single bay second gen My Cloud unbrick directions here:
https://fox-exe.ru/WDMyCloud/WDMyCloud-Gen2/_Unbricking_en.txt
https://wd.hides.su/fox_exe/WDMyCloud-Gen2/_Unbricking_en.txt

If restoring the original My Cloud firmware to a new hard drive, one likely has to partition and format the hard drive exactly for the specific My Cloud model. The prior two links have directions for partitioning and formatting a single bay second gen My Cloud. No idea if other My Cloud models like the first or second gen My Cloud Mirror use the same partition values and format values.

Support for Western Digital Hard Drives | Western Digital

Still Need Help?

Reach out to Support for more assistance.

Sign in to Your Support Account

Get up-to-date information about your products.

Western Digital Business Portal

Unlock benefits and tools for your business such as enterprise support, pricing and rebate tools, marketing, loyalty, rewards, and more.