RB 433AH Stuck at "jumping to kernel code"

I tried to experiment with the new ROS4 beta, purchased a new RB433AH and uploader the ROS4 beta packages to it. Rebooted but the routerboard will not boot again.

So I attached a console cable and fired up hyper terminal to see what was going on. I discovered that the router board was getting stuck at “jumping to kernel code” stage. I promptly changed the bios setting to allow boot from ethernet and tried to use netinstall to down grade the RB433AH but the same problem persist.

I held down jumper JP301 while powering up in other to boot from the primary boot loader and use netinstall to downgrade but same problem still persist.

Reinstall RouterOS with netinstall

That is exactly what I was trying to do, but the routerboard will not progress past the “jumping to kernel code”. From the attached image, you will see that the RB433 had booted over ethernet and connected to netinstall computer. It had already gotten an IP address, resolved the MAC and started transfer before it got stuck. Netinstall did not work in this instance.

How did you fixed? I got the same problem.

Yes, I fixed the problem by using a different version of the Netinstall software. I cannot remember which version it was that resolved the issue. Try the netinstall 4.6 or 5.0beta1.

Yes I tried, with those versions and did’t work. I will try to find another old version of netinstall.

Thank you

I have the same problem!

How could we fix it? I spent a lot of money in this device. I need to fix it!.

Please Mikrotik Team involve in this issue, and help us.

Thank You

Try to upgrade the bootloader first (Routerboot) over the serial port and then try again with the newest netinstall.

I have been watching for a year now for the answer, and haven’t seen one!

The conclusion I have come to is that its junk! And to throw it away!

I had bought it new and sat on it for two months be for I took it out into the field; it ran for less than a month before it went to shit!

I got stone walled when I tried to return it. Mikrotik said to return it to the vender, the vender refused to accept it back! When I tried to contact Mikrotik to see if they could repair it at my expense I got no answer.

I have only had two boards go bad out of a hundred or so. As long as that percentage doest increase I will have to consider it a cost of doing business. If I see failure rates on these boards get to high I will start looking for another product. Over all I have found Mikrotik gear to be at the top when it comes to reliability, and longevity.

We are living in a disposable world!

It’s a shame that the only response is “Reinstall RouterOS with netinstall”
Well what do you do when netinstall can give the board an IP address, but the board wont show up in the netinstall program? The answer is: YOU CAN’T REINSTALL WITH NETINSTALL!

At the cost of these boards compared to the price of competitors boards. I’m just going to toss it and hope I don’t get to many more that go to shit on me!

Tryed That!

Yes, I did tryed, and did’t work. Another Idea?

which versions of the netinstall you used?

The version is v4.10

The firmware version that Im trying to install is v4.2.

After 1.30 hs installing, this is the message that appears when the routerboard try to boot

"RouterBOOT booter 2.25

RouterBoard 433AH

CPU frequency: 680 MHz
Memory size: 128 MB

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

Another Idea?

Do you hear double beep after “jumping to kernel code” message appears?

No, just one Beep.

I would recommend to run,

  • format-nand;
  • reinstall the router with the latest Netinstall and MikroTik RouterOS 4.10;
    Return RouterBOARD to the warranty, if nothing helps.

hi, i’ve experienced the same problem..

you should change boot order in bootloader.. from console

temuri426, what kind of boot order? what you should put there?

Yes, I already format nand, and reinstall the router. But this did’t solve the problem.

Even I do a memory test, and the result was ok.

Another Idea?