Rbr50v2 Conversion

[Beach]

After flashing I did full factory reset. I tried to connect satellite to network (all my units are running latest V9.2.5.2.32SF-HW firmware) but it wasnt connecting (likely due to different firmware). So after reset i flashed through TFTP schmellic V9.2.5.2.32SF-HW modified firmware. It went well.
After some dancing (had to use ethernet cable to connect satellite first) new converted unit succesfully connected to the network through 5 GHZ backhaul.

What was involved with your "dancing"? I have been unable to get any of the voxel schmellic firmwares to join as a satellite (tried RBR50_to_RBS50-V9.2.5.2.32SF-HW.img and RBR50_to_RBS50-V9.2.5.2.28SF-HW.img so far on my RBR50 with V9.2.5.2.31SF-HW). Thinking it was something wrong with my process, I tried schmellic RBR50_to_RBS50-V2.7.5.4.img firmware and it immediately joined my network as a satellite, but ideally I would want to stick with the voxel firmwares.

Any ideas what is going on or suggestions on how to get them connected? I have also done a direct ethernet between the RBR50 router and the converted RBR50 hoping it could do a config sync via wire then move onto 5G backhaul, but so far no dice.

Do I have to go back to RBR50-V2.5.2.4.img or RBR50_to_RBS50-V2.5.2.4.img before flashing the voxel firmwares? I know for the non-converted models, that is recommended if not required.

 

[smtelegadis]

For anyone who is looking for the proper way to use TFTP with converted RBR50v2 to RBS50v2 please look at the following link:

https://www.snbforums.com/threads/c...18sf-hw-v-9-2-5-2-18-1sf-hw.76758/post-746486

Cut and pasted relevant content below:

(1) You should power off your RBS.
(2) You have to use some thin stick like toothpick and push the hole near power supply:

(3) Still keeping it pushed power on your RBS using "power on" button. Wait for about 30 seconds.
(4) Your RBS should starts blinking (top oval LED, top of your RBS). Now your may drop out your toothpick.
(5) Continue from NG instruction above, p. 3. Any Ethernet port could be used.
(https://kb.netgear.com/000059634/Ho...FTP-from-the-Microsoft-Windows-Command-Prompt)

I.e. now your RBS has the IP 192.168.1.1 and you can TFTP my or stock firmware to this address.

After that (about 1 min) your RBS will be rebooted automatically and you should be able to pair it again with your RBR.

This process was not in any of the prior posts of this thread and it will supplement the processes required for upgrading or returning a RBS50v2

Thanks @Voxel for this and the great work on the custom firmware. You fixed all of my grips with the Stock Orbi RBK50s GEN 1 and 2.

 

[xsolider]

For anyone who is looking for the proper way to use TFTP with converted RBR50v2 to RBS50v2 please look at the following link:

https://www.snbforums.com/threads/c...18sf-hw-v-9-2-5-2-18-1sf-hw.76758/post-746486

Cut and pasted relevant content below:


This process was not in any of the prior posts of this thread and it will supplement the processes required for upgrading or returning a RBS50v2

Thanks @Voxel for this and the great work on the custom firmware. You fixed all of my grips with the Stock Orbi RBK50s GEN 1 and 2.

That's the instructions for v1 conversion, isn't it? The reason why we are using schmellic's modified v2 firmware is that we can't use the same instructions for v1.

 

[gssjshark]

That's the instructions for v1 conversion, isn't it? The reason why we are using schmellic's modified v2 firmware is that we can't enable putty as we do for v1.

Yes, that is for the V1 only.

 

[alexnev]

@schmellic - Hello Sir! Can you please make a latest version of firmware for v2 conversion? Thank you very much in advance!

 

[schmellic]

Latest version uploaded to google drive

 

[alexnev]

Thank you Sir!!!!

 

[Beach]

Anyone have luck with OTA updates after conversion? I assume it cannot use the base RBS50 firmware, but it also doesn't seem to be taking the schmellic modifed firmwares from his google drive.

 

[alexnev]

You would have to use tftp to upload new firmware

 

[Stirm_]

Hi, please can someone share the order of pins on the v2 board to connect a usb-ttl cable? I bricked a RBR50v2 using v1 telnet method…. Need to unbrick and figure out hot to get RBR50v2 converted into RBS50V2…

 

[Stirm_]

I figured it, if it helps somebody else

 

[xsolider]

Hi, please can someone share the order of pins on the v2 board to connect a usb-ttl cable? I bricked a RBR50v2 using v1 telnet method…. Need to unbrick and figure out hot to get RBR50v2 converted into RBS50V2…

The recovery mode method for v1 should work on v2. No need to open the device and use ttl.