Hello I want to know if my router which is Netgear Orbi RBR50V1 is a dual partiion router I'm very confused because the git commit page when OpenWrt supported this router said that the SRS60 RBR50 are dual partition routers but the commands they gave me doesn't show normally via telnet on versions that I have tried so I'm not sure if its true if it is which version of stock firmware allowed the use of artmtd commands to see and change the boot partition to install openwrt I already have openwrt installed but i still want to know if its really true and possible if I can get both OpenWrt on the main parititon and stock firmware on the second parititon thanks 
Can you provide that link for reference?
on Line 38
Installation
These routers have a dual partition system. However this firmware works
only on boot partition 1 and the OEM web interface will always flash on
the partition currently not booted.
Working link https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=2cb24b3f3cd89692f3c0bd137f3f560ada359bfa
Comment also talks about switching partitions ?
1 Like
Thanks for posting the link I thought the one I posted works I'm new here 
Yes it does say about switching partitions to install OpenWrt on the other partition or just use nmrpflash to bypass everything it will install it on first partiion the thing is if its really a dual partition router when I first bought the router second hand I installed openwrt via the oem firmware upgrade page that openwrt image got corrupted when i tried to install too many things via the attendedsysupgrade it failed so then I installed openwrt again via nmrpflash so I'm confused here that if its really a dual partition router is the other parition still the corrupted openwrt one or it was corrupted on the first one which I installed openwrt again and it overwrote it
But the instructions say only 1 partition works. I don't understand the inquiry.
Are you asking if the "opposite" partition was flashed?
Yes I'm asking when I flashed OpenWrt for the first time via OEM page did it flash it on the Second Partition? but my main question was if my router is actually a dual partition and if guys have knowledge on which stock firmware allowed telnet access which had the artmtd command avaiable before it was removed I just want to see if its truly a dual partition router
1 Like
Switching partitions would suggest it got at least two ?
1 Like
yes that's what it should be if the openwrt git says it has two and you can switch betwwen them right? I'm just curious at this point not gonna lie I already have a working openwrt router if you think this should not be further discussed I'm okay with it I won't be able to use the dual partitions anyways if I did know it does have it because even the app luci-advanced-reboot doesn't list my router as a dual partition router
Why are you under that impression when the instructions read otherwise?
What is the goal of "switching" to a non working partition?
Or are you assuming you flashed Partition 2, and are inquiring about Partition 1 - since the instructions said "2" shouldn't work?
yes that's what I'm saying if the instructions say that it couldn't be flashed to partiton 2 how did I install OpenWrt from the OEM firmware upgrade page and it worked before I eventually corrupted it oh yeah one more thing after my openwrt got corrupted I searched online and found out you can get back to stock using nmrpflash at that time I didn't knew about the git commit so I got back into stock and tried installing openwrt again but this time it failed I tried twice doing this method whenever I installed openwrt through the oem page it the router wouldn't work it was just stuck at flashing white light so then I got to know that you can install openwrt image directly through the nrmrpflash software and then I got openwrt working again so the meaning of making this post was how it was able to flash openwrt the first time I did it through OEM page and when it got corrupted it wouldn't do it the next time I tried doing it?
1 Like
OK, thanks for the clarification.*
*-Although, it's kinda difficult to follow your inquiry and comments without punctuation, sentences and paragraphs.
I'm sorry.. I'm not really good at writing long paragraphs to explain that others can understand better I will try my best to do those next time
Add a profile to luci-app-advanced-reboot - it should be able to handle this.
1 Like
I'll be very honest here I'm very new to OpenWrt and only know some stuff because I have joined the Reddt page of OpenWrt and see peoples stuff they do and try it myself so doing this is hard or easy if you can guide me on how to do it I would really appericiate it! also a concern of mine is what if the other partition is corrupted still and I switch to it if it lets me how will I go back to the orignal partition where my openwrt is?
I'm asking your help because I already looked into the guide of how to add your own profile and when I ran the commands It just output nothing
root@OpenWrt:~# cat /tmp/sysinfo/board_name
netgear,rbr50
root@OpenWrt:~# fw_printenv
Cannot parse config file '/etc/fw_env.config': No such file or directory
Failed to find NVMEM device
root@OpenWrt:~# cat /proc/mtd
dev: size erasesize name
root@OpenWrt:~#
- First time install of OpenWrt Factory firmware works only on boot partition 1
- There are 2 ways to install Openwrt the first time
- Using NMRPflash - This will always flash Openwrt OR OEM to Partition 1
- Without NMRPflash - This requires you to use Telnet to ensure you are on Partition 2 before Flashing OpenWrt. This tells the OEM firmware to flash first time OpenWrt Factory to Partition 1 because normal flashing from OEM firmware typically follows the same process of always flashing to the Alternate Partition i.e. Flash Partition 2 if currently on Partition 1 or Flash Partrition 1 if currently running on Partition 2.
What is not clear from the commit instructions is whether you can now use a Sysupgrade Image that follows the normal process of flashing to the Alternate Partition (partition 2 in first time Sysupgrade). I suspect it will.
Since you have established that you can use NMRPflash to install OEM or OpenWrt Factory to Partition 1 reliably, try a Sysupgrade from a higher Openwrt Release Version. If this newer version boots normally then you can assume you can just keep upgrading via Sysupgrade to whatever the Alternate Partition is.
As @systemcrash indicates, luci-app-advanced-reboot will require a profile for this particular device to be added to the app. I believe @stangri supports this (https://docs.openwrt.melmac.ca/#luci-app-advanced-reboot)
1 Like
Sysupgrading from 24.10.5 to a higher release of OpenWrt my router got bricked I tried this when I wanted to try the release candidates version
I had to reflash OpenWrt back to the 24.10.5 normal sysupgrades attendedsysupgrade from same branch like 24.xx.xx etc wasn't a issue I was doing that from a long time
I then flashed the factory image of the release candidate via nmrpflash that worked
1 Like
I’m not clear on this. You originally used NMRPflash to flash OpenWrt factory say 24.10.2 then were able to use normal sysupgrade (attendedsysupgrade) without issue on e.g. from 24.10.2 to 24.10.3 to 24.10.4 to 24.10.5?
Then you sysupgrade to a 25.12. release candidate that “bricked” the device but were able to subsequently flash the same release candidate using a Factory image via NMRPflash?
I'll explain again this time hopefully better so you can understand
First Time Installed OpenWrt via OEM Firmware Upgrade Page. It worked and was working fine but then I had a stupid idea to install AdGuard Home and Tailscale at the same time via luci-app-attendedsysupgrade that bricked the router then I found a solution that you can unbrick your router via a tool called nmrpflash designed for Netgear Routers so I did that and flashed the stock firmware again and tried to install OpenWrt back via OEM but same result it bricked so then I found out that I can flash the OpenWrt Factory Image directly without having an issue.
After this I whenever a new update came like 24.10.3 from 24.10.4 the sysupgrade worked and the router would boot to the new version even sysupgrading the same image by downloading the same version image works I have done this many times as I didn't use the Reset to Default button and just flash the fresh sysupgrade image and I can go back to having default settings but when I tried upgrading to the newer release candidate at first I thought It was just starting up and was taking a while but after some time it was stuck on flashing white light then I knew that the router was bricked so I went back to the stable version via nmrpflash thinking that there must be a problem with the new version but after doing the same thing but installing the release candidate version via nmrpflash it booted right up no issues at all
1 Like
In short "yes"
1 Like