Recovery

Unbricking procedure for WLX-652 and NS-K330

READ: This unbricking procedure is intended to work when you have a serial connection AND your NAS enter at least into bootloader. It will rewrite the default stock firmware back to your WLX-652 or NS-K330 NAS. If your NAS is unresponsible with the serial connection, chances are that you will have to rewrite the flash.

To download the files, right-click on the links and use "Save as".

1. Get a serial interface connected through a RS232-TTL converter. The serial parameters are 38400-N-1. The board have some holes in which the pins can be connected, next to the processor.
2. Set your computer IP address to 192.168.0.100, and have tftp server running (I do like tftpd32 in Windows or tftpd-hpa in Linux) with the file recovery.8132 in the root directory.
3. Start the system and interrupt the boot process with any key to get in the "Star Equuleus #" uboot prompt.
4. Use these commands:

     setenv ipaddr 192.168.0.10
     setenv serverip 192.168.0.100
     tftpboot 0x1000000 recovery.8132
     go 0x1000000
   

The recovery image should boot. You must be able to use the NAS prompt now.

1. Download and unpack fw_def_mtd.zip. Copy the files fw_def_mtd1_config.bin , fw_def_mtd2_kernel.bin and fw_def_mtd3_initrd-and-web.bin to an usb drive (prefer fat, ext2 or ext3) and connect it to the NAS. It will mount automatically.
2. Type the command "mount", to check that the pendrive got mounted on /usb/sda1. We will assume this mount point for the remaining of procedure, change it accordingly, if necessary.

3. Write the files back to the correct flash partitions with the following commands (the kernel and initrd-web will take some time):

   /bin/dd of=/dev/mtdblock1 if=/usb/sda1/fw_def_mtd1_config.bin
   /bin/dd of=/dev/mtdblock2 if=/usb/sda1/fw_def_mtd2_kernel.bin
   /bin/dd of=/dev/mtdblock3 if=/usb/sda1/fw_def_mtd3_initrd-and-web.bin
   

4. Remove and reconnect the power cable. Remember that your NAS will return to the default factory settings.

NOTE: Depending on the working state of your NAS, this procedure may not work. Feel free to ask for info.

Gazineu

[Anonymous]

Originally posted by: stefansc...@googlemail.com

The web interface is also available when booting the recovery image. From there it's possible to flash snake os images.

[Anonymous]

Originally posted by: edu1...@gmail.com

Steps to recovering a NS-K330: http://entrebits.com.br/post/2012/01/21/recuperando-um-nas-ns-k330 (portuguese)

[Marcelo Adans]

hello, I'm Brazilian, I'm trying to recover my In the K330, but I can not download the necessary files. you could kindly resubmit or send by email. Thank you very much in advance.
madans@globo.com

[Anonymous]

Originally posted by: edu1...@gmail.com

Steps to recovering a NS-K330: http://entrebits.com.br/post/2012/01/21/recuperando-um-nas-ns-k330 (portuguese)

[Anonymous]

Originally posted by: cadastro...@gmail.com

Hi Dear,

My name is Weymar, and i´m from Brazil. I did the procedure, but a message appears. "Retry count exceeded; starting again". Can you help me? I used the circuit http://pinouts.ru/Converters/rs232-TTL_cable_pinout.shtml, Windows Vista, putty (serial) and SolarWinds?_TFTP-Server.

Thanks

[Anonymous]

Originally posted by: tunayuya...@gmail.com

My wlx-652 stopped working after upgrade, and its ethernet interface lights(green and orange) is lighting up 2 times when I start device. Then nothing happens. Did my device bricked ? Which way I should try to unbrick it ?

I have arduino mega 2560 device if that helps solving problem.

[Anonymous]

Originally posted by: tunayuya...@gmail.com

Fyi if i connect cables from arduino's tx rx ground and 3.3v to wlxkj-652 v1.0 board with 4 holes below star chip, it powers up board without adapter. So I assume i can do something with using tx rx cables(i see they are connected to star chip??).

Any help ?

[Anonymous]

Originally posted by: javiercr...@gmail.com

I need help with my wlx-652. The problem is the wlx-652 is not detected by the router, I do test with two routers a Netgear and Airport a1143, but the NAS not show up in the DCHP clients but the usb light on the WLX stay on and the system light just blink. Please what I need to do to resolved this issue.....Thanks in advanced......

[Anonymous]

Originally posted by: jp42k...@gmail.com

Hello friends: I have used this procedure succesfuly with my RITMO LN-86BT (from dealextreme). I am running OpenSuse? 12.1, I have used Yast-tftp-server, Minicom and a FT232RL USB to Serial Module (from ebay). I had some problems in the step 4 ("tftpboot 0x1000000 recovery.8132" returns: "T T T T T T", "Retry count exceeded; starting again"). I tried turning off the firewall at ethernet adapter and it worked. My NAS is alive again!!!! Thanks a lot.

[Anonymous]

Originally posted by: langl...@gmail.com

Hi please help me someone.how to configure this programs and how to use this? Get a serial interface connected through a RS232-TTL converter. The serial parameters are 38400-N-1. The board have some holes in which the pins can be connected, next to the processor. Set your computer IP address to 192.168.0.100, and have tftp server running (I do like tftpd32 in Windows or tftpd-hpa in Linux) with the file recovery.8132 in the root directory. How to use TFTd32 windows version ? please help me. thank you.

[Anonymous]

Originally posted by: ohnos...@hotmail.com

I also have a Ritmo LN-86BT mini-LAN server I picked up the other day, as I got sick and tired of watching the Raspberry Pi wait queue get longer as the year progressed (now 19 weeks!!!). True vaporware! I wish them all the luck in the world with their venture, but I'm one of the NOW generation. I have verified the Ritmo works by connecting it to my local LAN, printer, etc and it appears to be fully functional.

LAN, USB, memory card slot, all rolled into one with a 2Amp power supply, Ethernet cable, bilingual manual and a sexy case with flashing colored LEDs. Great value.

I have many plans for this little critter! I'm deft with a soldering iron and intend to polish up my programming skills and learn about custom firmware and running a minimum Linux on small boards. I have the luxury of using an external memory card plugged in if I start to run out of room to store code. The different I/O options from the CPU for one-wire and SPI connectivity are going to be explored! If the Raspberry Pi finally becomes available, the power supply of this unit can be used for the Pi (it supplies 2Amps which is ample) or I can use it as an intelligent peripheral or pre-processor for real world applications that can be remotely accessed and controlled.

I've already opened the little box by poking a Philips screwdriver under a corner of each rubber foot and undoing the screw. If you are careful, the rubber foot will still adhere to the box and trap the screw under it, so nothing is lost. The four little screws that hold the PCB (printed circuit board) to the inside of the case are easily lost so make sure you put them somewhere safe while working on the PCB.

I found the four holes on the PCB marked J1 are the serial port and have verified the square pad hole is +3.3volts, the next one is the TX pin, the third is the RX pin, and the fourth is Ground. The TX and RX pins go directly to the CPU, so beware of any voltage loops or static electricity.

Careful and quick soldering of a four right angle mounting PCB pins strip as a serial port breakout is strongly recommended rather than just wire direct to the PCB. Use a hot iron, freshly wiped to remove any oxides and make sure it has a good coating of fresh solder on it, make a quick dab on the pin with the iron first and put the resin cored solder to it and let it flow before removing the iron. Watch the pins don't move while the solder is going hard. It takes about half a second if you are good and you can tell if it is a good solder joint as the solder has flowed all around the pin, has wicked up from the circuit board to the pin, and has a shiny look similar to the other solder joints around it. If you have a bubble of solder on the top of the pin or it has a dull look, you need more flux and a clean iron to re-do the joint. Avoid too much solder as you will end up bridging the circuit pad to the one adjacent. Too much heat will result in the solder pads lifting and breaking, and possibly wrecking the multi-layer circuit board. Better get it right the first time rather than have to re-heat the joint - experiment on something else if you are paranoid.

The 5volt power is filtered and regulated in both voltage and current on the circuit board, so I wouldn't be too worried about stealing a little current for a little adapter to buffer the serial data for external RS232 connectivity, hence use of four rather than three pins on the PCB in case I want to use the 3.3V pin. The case doesn't have a lot of ventilation, so I would possibly monitor the temperature rise before locking it away in a cupboard or out of the way.

Before I go and start modifying it, I would like the comfort of knowing I can unbrick it back to the ORIGINAL firmware that comes from the factory using the procedure outlined in the comments above. Ritmo and associated websites have no firmware updates or even open-source GPL code to start from and the only firmware that seems compatible is the Snake one here. This has been my only point of discomfort in making the purchasing decision.

Question: The device is intact, factory fresh, and fully functional. How do I extract the firmware and configuration settings as it currently is so I can later unbrick it when things go wrong? (they will, I'm sure!)

Step by step (cut-n-paste preferred) is all I can muster at this time as a complete newbie.

Hint: A successful procedure will result in me posting the firmware back here for others to download that may encounter problems down the track.

[Anonymous]

Originally posted by: stefansc...@googlemail.com

Oh, a dump of the Ritmo firmware would be handy. I didn't do a backup before starting to mess around with mine. I have a programmer and the chip is sitting on a DIP adapter so I could test the result fairly easily.

Start by setting up serial connection. Details for doing so under linux are here: http://code.google.com/p/snake-os/wiki/SerialConnectionHowToNSK330 Since you didn't mention it, don't wire the board directly to the serial port. You need to use an converter like the MAX232 or PL2303.

Minicom should be showing you some output when you power up the board.

Follow steps 1 to 4 on this page. That should get you to the shell. I'd suggest not to interact with the web interface from the recovery image, because some functions could trigger writes to the flash..

Now do "dd if=/dev/mtdblock5 of=/usb/sda1/fw.dump" to dump most of the flash to the memory card. For some reason the last 65K are not mapped to any flash partitions in snake so there's no easy way to get at them. With some luck they aren't used by the original firmware either.

[Anonymous]

Originally posted by: cesarhen...@gmail.com

Hello, I got my NAS yesterday and bricked it today trying to replace the firmware to the SnakeOS. I didnt read carefully and tried to make the update with the wrong version..

Now I got the NAS bricked and ethernet adaptor dead... When I plug the ethernet cable, not even the LEDs lighs on. When I power it on, the USBs and Power LEDs turns on and the System keeps off. Will I be able to unbrick with the serial procedure?

Thanks, Cesar

[Anonymous]

Originally posted by: skalee...@gmail.com

Hello:

I am in the same boat as per cesarhen...@gmail.com. My NAS was fine until I replaced the firmware to SnakeOS. My NAS is bricked and ethernet adapter is not connecting to the network. My Power light is bright, and other 3 lights are lit, but not bright.

I have a serial to USB adapter. My laptop works with it just fine (I've used connecting to SUN servers serial port). I currently have it connected to the NAS using just 3 wires. Tx, Rx, and Gnd as listed by ohnos...@gmail.com. However, if I want any connectivity, only 2 wires work - Tx, and Rx. If I connect Signal Ground, I loose my connection. With just Tx, and RX my terminal software seems to work. Whatever I type, is echoed back. However, I do not see a boot process, or get to a # prompt.

Any advise as to how to go to the next step? ie: How do I get to a boot prompt if NAS is not even booting?

-- Sam

[Anonymous]

Originally posted by: hgna...@gmail.com

hello

can you share a link where can i buy a converter? or share a picture about it. i have no ide how it looks...

[Anonymous]

Originally posted by: drewt...@gmail.com

Hello Can someone tell how to connect RS-232 ME-752GNS

https://skydrive.live.com/embed?cid=9ED7B1F36E80CEF6&resid=9ED7B1F36E80CEF6%211322&authkey=AIaplnsUIBSUVOw

[Anonymous]

Originally posted by: stefansc...@googlemail.com

Connect the converter to the marked holes (bottom right) second from left should be tx.. third rx.

More details are here (instructions for windows are in the manual) http://code.google.com/p/snake-os/wiki/SerialConnectionHowToNSK330

Note: the str8183 has a different NIC (it uses external phy chips.. the str8132 has an internal one). Support for it is in the kernel and u-boot but you have to set the type at compile time to get networking.

[Anonymous]

Originally posted by: stefansc...@googlemail.com

Oups .. I didn't mean to embed the image. Sorry about that.

[Anonymous]

Originally posted by: marc.r.p...@gmail.com

Hello, Just in case it may help someone. My NS-K330 was bricked and I tried to use the above procedure to recover. However for some reason loading the file via tftpboot was impossible, altough I had a tftp server running (tested with another computer). What I did was to use the loadb command instead of the tftpboot command. More precisely I entered: loadd 0X1000000 Then the NAS is waiting for a file to be transmitted through the serial line with the Kermit protocol. I did this using Tera Term on Windows 7. It took about 1 hour to transfer the recovery.8132 file. I followed the rest of the procedure starting with go 0x1000000. It worked well, although the stdout was a bit messy after the Kermit transfert.

[Anonymous]

Originally posted by: aguirre....@gmail.com

the problem surely was the firewall of the system

[Abhishek Sharma]

Hello every one I am a great fan of wlx 652 a nice and cheap multifunctional box, I purchased it from a china seller and it was working fine with its stock os bus when I uploaded snake os to it, It became no use to anyone its booting up as I guess as its showing up lights blinking but its not picking up the IP and network. I tried to reset my router and even connect it directly to my pc and provide a static ip and tried every possible thing but no effect. As I googled uput and find the following link: https://dzrmo.wordpress.com/2012/06/13/wlx-652-lan-storage-flashed-with-linux-snake-os/

As I tried to connect it via serical interface but then too there is no holes or pins near to its cpu to connect. Please any one help out I guess its the cloned one. Will be really thankful if you help me out.