Hello, I don't use dd-wrt. I use another firmware but decided to register/reply to the thread since I used it as source when I first got the router a year ago. I also struggled to get the previous procedure working. After countless tries, I found this works best for me. Maybe it'll be helpful to someone else.
Launch cisco tftp program and set root directory C:\RNX-GX4 Recovery in options with the filename upgrade_linux.trx (Imagine program of choice will work)
Manually set the IP to 192.168.1.30 (30 is random) and subnetmask to 255.255.255.0
Then unplug the power connection and the ethernet connection to the pc at the back of the router.
Press in the reset button and leave it pressed as one reconnects the power.
Wait a few seconds til the lights stop blinking and release the reset button.
Hey guys, I bricked my RNX-GX4, though due to the awesomeness of Newegg support, I got a new one free of charge. I was going to throw the bricked one away, though I thought I would give jtagging a try.
However, I used a pinout I found of the J6 port on the PCB. I did a quick test with an LED and discovered that the diagram could be interpreted as being the wrong direction, so I created the attached image (I found the picture from Google Images, though added the text).
I also discovered the flash chip that's detected by probing it.
Joined: 06 Jun 2006 Posts: 3763 Location: I'm the one on the plate.
Posted: Fri Jun 03, 2011 3:30 Post subject:
You need to repair the 4 cold solder joints on U3 before you do very much else. Prolly more cold solder joints if you look for them. Even for free, this rosewill radio is not worth the price, and should simply be smashed to bits with a hammer so you can get on with yer life. _________________ http://69.175.13.131:8015 Streaming Week-End Disco. Station Ripper V 1.1 will do.
Heh, It's temping. Though the new router is humming along just fine.
That picture isn't mine, the only reason why my router was bricked was because I was on Tomato 1.27, then upgraded to 1.28 through the web interface, unfortunately something must of gone wrong. In any case, I'm very happy with the performance I'm getting out of a router I paid $25 for
- Built-in NAT and DHCP server supporting static IP address distributing.
- Shares data and Internet access for users, supporting PPPoE, Dynamic IP, Static IP, L2TP, PPTP, BigPond Cable Internet access.
- Built-in firewall supporting IP address filtering, Domain Name filtering, and MAC address filtering.
Provides Wireless LAN ACL (Access Control List).
- Supports Flow Statistics.
- Supports Virtual Server, Special Application and DMZ host.
- Supports ICMP-FLOOD, UDP-FLOOD, and TCP-SYN-FLOOD filter.
- Ignores Ping packets from WAN or LAN ports.
- Supports connecting/disconnecting from the Internet on a specified time of day.
- Supports access control, parents and network administrators can establish restricted access policies based on time of day for children or staff.
- Supports firmware upgrade.
- Supports Remote and Web management.
- Establish a 54Mbps wireless connection, sharing Internet Access, download file or play game
IP based bandwidth control allows administrators to determine how much bandwidth is allotted to each PC
The reason I'm trying to get the router working again is because I want to use the serial port on it. I don't wish to buy another router that doesn't allow me to use custom firmwares. Regardless, that router is the same price as the Rosewill (When it was on sale) on Newegg.ca.
I am open to suggestions for inexpensive routers that do support DD-WRT and have a serial port (USB would be awesome too).
However, I would love to get my broken current RNX-GX4 in a working state. Unfortunately, I ran into some trouble.
tjtag now throws this error when I try to probe it:
Code:
*** Unknown or NO Flash Chip Detected **
The LEDs stay lit, except for the system LED and the 2nd LAN LED. The last thing I did was flash a CFE downloaded from that CFE thread. If I add /fc:21 to the regular backup:cfe128, it seems to readout fine!
If I run flash:cfe128 /fc:21, it seems to hang at "Erasing block: 1 (addr = 1fc00000)...".
One possibility that I thought of was that I had been previously using the regular flash:cfe command rather than flash:cfe128 when trying to get it working last night.
When I run the first command, the total blocks to erase would be 4, though with the cfe128 option I would have 2 total blocks to erase. Since the CFE for this router is 128 KB, could using the normal command cause problems?
Another possibility is the cable, which is about 7" and not all the wires are exactly the same length. I could remake it this weekend if someone thinks it's bad enough. I also only have one ground soldered onto the PCB, could that cause problems like this?
tjtag now throws this error when I try to probe it:
Code:
*** Unknown or NO Flash Chip Detected **
The LEDs stay lit, except for the system LED and the 2nd LAN LED. The last thing I did was flash a CFE downloaded from that CFE thread. If I add /fc:21 to the regular backup:cfe128, it seems to readout fine!
If I run flash:cfe128 /fc:21, it seems to hang at "Erasing block: 1 (addr = 1fc00000)...".
Why did you erase your boot loader without having verified first (with a serial terminal connection) that it was needed? The router is fucked now..
Your previous half-brick is now a full-brick. _________________ Kernel panic: Aiee, killing interrupt handler!
Why did you erase your boot loader without having verified first (with a serial terminal connection) that it was needed? The router is fucked now..
Your previous half-brick is now a full-brick.
Yeah, that was a stupid move on my part. I finished making the JTAG cable late in the day and just ran through the JTAG page before bed. When will I ever learn
Though due to me getting the free replacement router (Which is running excellently!), It's not a big deal. However, I may pick a DD-WRT compatible router at some point to mess around with.
I'm posting this here because it's the 1st page that comes up when you google RNX-GX4 bricked
I was running another firmware on this router and tried to upgrade it, and it bricked.
for over an hour i tried the recovery procedures and it failed..
I googled for a while and saw many people give up.
and then I got it figured out and working (repeatable)
so i figured i'd post up to help out others who get in this situation..
1st thing you should know is this router is very time specific in the recovery procedure, you have less than 5 seconds to send the firmware and it has to be a certain time or else you get nothing.
so here is how you do it.
1) set IP to 192.168.1.xx (.33 is suggested, but i dont think it matters)
2) hook cat 5 cable to router port 1 (not wan port) and to your pc/laptop
3) get a KNOWN working firmware or the stock rosewill firmware ready
4) get tftp32 up and running
5) place the .trx file in the root of the tftp32 folder
6) configure tftp32 CLIENT
host 192.168.1.1
select the file you just put in the root
port 69
and dont touch anything else here
7) open a dos box (cmd) and type ping -t 192.168.1.1
note: i saw instructions somewhere, where someone said to do this, but said not to hit enter.. this is wrong. you need to see what's going on to know when to send the firmware
go ahead and hit enter in your dos box.
you'll start seeing destination not founds
9) keep your tftp32 and dos box open and side by side so you can see and interact with them
10) take a saftey pin or other sharp object, unplug in the router, insert saftey pin in default hole in the back, hold it down and plug in the router.. you'll see the led's light up, as soon as they start blinking count to 10 and let go of the saftey pin and the blinking will stop
11) watch the ping window, after about 30 - 60 seconds you will see a respond from 192.168.1.1
AS SOON AS YOU SEE THE 1ST RESPONSE click "put" on your tftp32 window
If you do not do this on the 1st or 2nd response, you will have to start all over.
the router only responds for about 4-5 seconds and then it no longer responds.
which is why if you are doing it blind (no ping windows) you are pissing in the wind with this process
if you did it correctly, you will send the trx file being Tftp'd over in a few seconds.
do NOTHING but sit there and watch your ping window about 1-2 minutes, you'll start to see responses from 192.168.1.1
at this point you can stop thinking about throwing this router in the garbage.
Posted: Mon Aug 29, 2011 8:44 Post subject: Diversity Chip Ectomy? How to run just one antenna reliably?
Well, if this were a linksys, it would take about 5 minutes to put the coax in the spot where the diversity chip was.
And then you get really reliable support for Dish, Biquad, Cantenna, Yagi, Vagi and Collinear.
Unfortunately, this Rosewill / Netcore, has a real mess for antenna hookup. This is seemingly the cause of the short longevity if you happen to use just 1 antenna or anything more elaborate than a matched set of generic China +6 (same as Rosewill's +5). Well I'd sure like to use a collinear instead.
Unfortunately, anything but modest antennas really irritate the radio. The antenna AB selection can change jacks at random after a reboot or power up. That's not good if there's just 1 antenna hooked up.
How do I physically disconnect the diversity feature as well as some of the filter mess to save it from eventual suicide?
Joined: 06 Jun 2006 Posts: 3763 Location: I'm the one on the plate.
Posted: Mon Aug 29, 2011 19:39 Post subject: Re: Diversity Chip Ectomy? How to run just one antenna relia
danielwritesback wrote:
...
How do I physically disconnect the diversity feature as well as some of the filter mess to save it from eventual suicide?
Not sure about a physical mod, but in the firmware you can select either one to always be used. _________________ http://69.175.13.131:8015 Streaming Week-End Disco. Station Ripper V 1.1 will do.