NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Accessing Bootloader via Putty on RBR50
My orbir router got bricked while I was at the office and when I got home, I was greeted to magenta lights on my satellite. I was able to factory reset the satellite, but my router is unresponsive to...
CR4 Thanks for the info of switching the Tx and Rx. After that I am able to see info output in Putty. I am having the same issue that Plomo mentioned where it's just a green power light and nothing else. The Putty output goes for about 2 seconds and then stops after DDR Frequency, 672 Mhz. It doesn't let me type or do anything. Anyone have any ideas if this is salvageable?
You need to break the boot process by pressing ctrl + c after about 2 seconds.
This should give you access to the commands in putty to enable you to write the new values to the router
This should give you access to the commands in putty to enable you to write the new values to the router
- I found this video helpful (not for Orbi but nighthawk, though the procedure is similar)
https://youtu.be/c40x4avo8GU?si=oSVzId9cId9DsZEdThanks, yeah I had tried that initially before posting on here. Nothing seems to break the initial load, this is the only data that displays after powering the RBR50 on and then it just sits there.
Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.1-00110
S - IMAGE_VARIANT_STRING=DAAAANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x00000023
S - Reset status Config, 0x00000000
S - Core 0 Frequency, 0 MHz
B - 261 - PBL, Start
B - 1339 - bootable_media_detect_entry, Start
B - 232628 - bootable_media_detect_success, Start
B - 232642 - elf_loader_entry, Start
B - 336878 - auth_hash_seg_entry, Start
B - 339027 - auth_hash_seg_exit, Start
B - 513175 - elf_segs_hash_verify_entry, Start
B - 627575 - PBL, End
B - 627599 - SBL1, Start
B - 719621 - pm_device_init, Start
D - 9 - pm_device_init, Delta
B - 721124 - boot_flash_init, Start
D - 675001 - boot_flash_init, Delta
B - 1400473 - boot_config_data_table_init, Start
D - 105563 - boot_config_data_table_init, Delta - (419 Bytes)
B - 1508632 - clock_init, Start
D - 7530 - clock_init, Delta
B - 1519594 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:0,Subtype:1
B - 1522999 - sbl1_ddr_set_params, Start
B - 1528092 - cpr_init, Start
D - 2 - cpr_init, Delta
B - 1532475 - Pre_DDR_clock_init, Start
D - 4 - Pre_DDR_clock_init, Delta
D - 13171 - sbl1_ddr_set_params, Delta
B - 1545771 - pm_driver_init, Start
D - 2 - pm_driver_init, Delta
B - 1616957 - sbl1_wait_for_ddr_training, Start
D - 27 - sbl1_wait_for_ddr_training, Delta
B - 1633350 - Image Load, Start
D - 869508 - QSEE Image Loaded, Delta - (262104 Bytes)
B - 2503286 - Image Load, Start
D - 899 - SEC Image Loaded, Delta - (0 Bytes)
B - 2513133 - Image Load, Start
D - 676665 - APPSBL Image Loaded, Delta - (414279 Bytes)
B - 3190225 - QSEE Execution, Start
D - 60 - QSEE Execution, Delta
B - 3196404 - SBL1, End
D - 2570918 - SBL1, Delta
S - Flash Throughput, 402 KB/s (676978 Bytes, 1681720 us)
S - DDR Frequency, 672 MHzOther forums mentioned something similar and no one seems to have been able to fix it from what I have been able to find. I am thinking that this thing is toast.