My testing unit (RB1100AHx4) was bricked today with RouterOS 6.43rc5.
I used WinBox to repartition for 2 partitions (primary and backup)
The router went into a reboot loop with no way to stop it.
Netinstall will not work, as the console shows that system reboots before the interfaces are initialized and therefor can not do bootp.
Console doesn’t appear to provide any way to intrude the boot and force a reformat or anything else.
Anyone know any tricks to recovering the RB1100AHx4?
-from the manual -
If you start holding the Reset button before applying power, it will also load the backup RouterBOOT loader, in addition
to the above actions. This may help to solve RouterBOOT issues and give you the opportunity to downgrade/
upgrade it while in backup loader mode.
No backup loader.. The router had just rebooted after partitioning, so the backup was still blank.
Also, you can see in the console log, it tried booting from partition 1 and 0.
That’s unfortunate. Crazy that its possible to brick the unit doing that. Its doubtful they include any JTAG ability. Their default response is to contact your supplier and arrange a RMA. On a side note I am curious what you think of the x4 aside from the current issue.
You will have to Netinstall your router. If you are not being able to do that, then provide serial console output which would be made during Netinstall process.
I do not see on serial output how you did determine something like this - “Netinstall will not work, as the console shows that system reboots before the interfaces are initialized”. Netinstall should work just fine.
Mikrotik products are great when they work and if they stop working your soon in a pin ball machine being bounced around aimlessly. Perhaps things will improve with v7
After about 6 hours, I finally got the Routerboot menu. I’m not sure why I was never prompted (press any-key…) before. I ended up getting a stopwatch and power strip. I was powering the router and timing how long to press the reset. It ended up needed to be pressed for no less than 15 minutes. (why?) After I got the menu, I was able to partition, format, and set the boot to ethernet. After that, the menu prompt is displayed every boot.
is this related to / a fix for the issue u encountered possibly ? :
What’s new in 6.43.2 (2018-Sep-18 12:12):
Changes in this release:
*) routerboot - fixed RouterOS booting on devices with particular NAND memory (introduced in v6.43);
Annapurna Labs stage 2: stage2_eth3_ram_loader v1.65.1
Executing next!
Annapurna Labs stage 2: stage2.5_loader v1.65.1
SPD I2C Address:00000050
Executing next!
-----------------------------------------------------
Stage 3 version: 1.65.1
Commit ID: e88c9c4
CVOS commit ID: d32367c
HAL commit ID: 8b8f7b5
Build date: May 20 2015 19:57:35
-----------------------------------------------------
EEPROM Revision ID = 37
Device ID = a314
Device Info: AL31400X-140
Loading DT to 00100000 (18676 bytes)...
Board config ID: alpine_db (AL-214)
Loading application to 00100000 (43880 bytes)...
Executing application...
RouterBOOT backup booter 3.36.3
RouterBOARD 1100Dx4
CPU frequency: 1400 MHz
Memory size: 1024 MiB
NAND size: 128 MiB
loading kernel... OK
setting up elf image... OK
jumping to kernel code
eFuse hashed modulues does not match the EEPROM hashed modulus
in 13-th port POE/BOOT with clamped reset for 30 sec leds start blinking but in Netinstall device do not appear , What addresses to register in the settings?
192,168,88,1 does not fit. Thank you
sorry for my english.