Bricked RB433 :/

Hardware MikroTik hardware general
1

Today i tried to upgrade my new RB433, i choose combined package for rb 400 series but after reboot RB doesn’t stand up :frowning:

RouterBOOT booter 2.14

RouterBoard 433

CPU frequency: 300 MHz
  Memory size:  64 MB

Press any key within 2 seconds to enter setup..
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code

netinstall doesn’t see hardware on serial console :frowning:

when I tried to send firmware file via serial Xmodem I have only message “invalid upgrade file id”

Please help :slight_smile:

2

I fix it. RB433 doesn’t work with 3.7 mipsbe package. I install back 3.6 and it works again :slight_smile:

3

I have the same problem with RB433 and MT 3.7.

MikroTik 3.6
MikroTik Login:

Rebooting…
Stopping services…
installed system-3.7
Restarting system.


RouterBOOT booter 2.14

RouterBoard 433

CPU frequency: 300 MHz
Memory size: 64 MB

Press any key within 2 seconds to enter setup..
loading kernel from nand… OK
setting up elf image… OK
jumping to kernel code

and … NOTHING !!!
The only solution was installing MT3.6 from Netinstall.

4

I guess they figured it out…

What’s new in 3.9:

*) bridge could make router busy even without traffic;
*) fixed route redistribution in RIP (bug introduced in 3.:sunglasses:;
*) fixed AR5212 kernel crash on setting change;

What’s new in 3.8:

*) fix B mode rate reporting for Atheros 5211 cards;
*) IPv4-compatible addresses as IPv6 route gateways now require
manually specified interface;
*) fixed removing external routes from OSPF;
*) added initial version of layer-2 mesh routing protocol;
*) fixed problem - OVPN server sometimes crashed;
*) fixed problem - torch could fail to aggregate connection data;
*) fixed problem - RB500 on high ethernet load rebooted sometimes;
*) fixed problem - if PPP (ISDN) client requested it’s own address, then server
did not report it in logs correctly;
*) fixed problem - if PPP (ISDN) client has it’s own address, it was
not used allways as on-demand ip address;
*) fixed problem - PPPoE, PPTP & L2TP stops receiving packets, if
MRRU is set and multiple packets get lost;
*) added support for Intel Gigabit PCI-Express cards;
*) fixed problem - RB433 did not work with v3.7;

5

And I remember some “smart guy” said that RouterOS was not board specific…hmmm…not the RB433. That sounds pretty specific.

ADD: I trust the opinions of those who buy these boards over the opinions of those who sell them. Nothing personal…

6

RouterOS is an operating system. RouterBOARD is a hardware device. There are drivers in Operating Systems that make the Hardware work. If the driver has a problem, the hardware will not work correctly.

I hope it’s not news for you

7

Not news to me, normis. That was my arguement with the smart guy. Can’t remember who. The OS is not “board specific” as in you don’t need a special version for each board. But still possible to have bugs with only one board due to hardware differences.