I have read quite a few posts and tried different things. At first, I tried the sticky for all devices and I could not get into RedBoot. After some searching, I decided to try the other sticky for only EOC-2610. Lo and behold, that got me to the next step.
Given that the method I used does not seem to be the norm, I'm curious as to how I should proceed so as to not brick my device. I'm not sure if continuing with the back door method described in the 2610 wiki and it not working would cripple the device. I'm lead to believe that it is unrecoverable.
When I do actually log in to the device, I am left with a menu and a barely responsive putty session (as seen below, the 'n's appear by themselves once every 3 seconds). I read in a post about a 9500, I believe, that the bootloader needed to be updated. I am not sure if that is accurate or if that applies to my device as well, but if it does, I don't have a serial cable so my quest ends there.
Here's the thing. As helpful as your response was, I made this post because, after reading the guidelines and as per the guidelines, my "problem still exist."
Perhaps I may have missed something, and, if so, would you be so kind as to point out my folly. Otherwise, I'd still appreciate some assistance.
i just searched for "EAP9550 ddwrt" (without the quotes).
looks like someone (probably brainslayer, bless his soul) posted a webflash, that might be usable from their web UI.
I hope that's helpful, I don't know much about the device. I'm still doing research and leaning towards the 3660. I find it hard to believe that they advertise speeds up 300Mbps but only have a 100Mbps LAN connection on the device. Unless i'm not understanding something, seems like 100Mbps is the hard limit, which is the same as the 3660, and the 3660 has more x-mit power.
Posted: Thu Jun 16, 2011 2:11 Post subject: EAP-9550-
ok so here it goes:
I think when I got my first device it had verison 1.1.3 stock senao firmware. I think I was able to get it to flash via tftp uploading firmware.bin. Since then I have gotten a few more of these devices and have not been able to flash them.
1st thing: there is no redboot port on 9000
2nd: no emergency room
3rd: webui is requesting .dlf files, so neither .bin work.... changing file name fails the upload.
4th.. tryed telneting into the device and using the webupg ftp to a local ftp server on my pc... no go.
5th.. Tried rename firmware.bin to firmware.ram and seting up tftp server... no go...
6th.. I have tried upgrading to 1.2.2 and also down to 1.1.3 and nothing flashes to dd-wrt..
I am out of ideas or think I have exhausted the last 2 hours and got nowhere. There is no offical documentation of howto properly flash this device and it has been support since feb 2011 in dd-wrt downloads section... The Chipset is RALINK and after check .dlf files are belkin encrypted files and the stock webui requires these files to upgrade it.
Joined: 06 Jun 2006 Posts: 3763 Location: I'm the one on the plate.
Posted: Thu Jun 16, 2011 3:36 Post subject:
Ubiquity has recently changed their hardware to facilitate improved regulation compliance. With Senao being the stuttering, red-headed bastard half step cousing of Ubiquity, it is not inconceivable that they too have had to make some revisions. _________________ http://69.175.13.131:8015 Streaming Week-End Disco. Station Ripper V 1.1 will do.
yeah something is definatly going that way lol.... I never have any problems with broadcom, and it always works.... once you start stepping out the box and go for looks (aka smoke detector ) it gets complicated and doesnt work 80% of the time..
PS: I tried the bootloader install method as well, no dice there either... get arp packets but it doesnt install bootloader either... I dont think this device is suppose to have a redboot.
Fractal
GeeTek wrote:
Ubiquity has recently changed their hardware to facilitate improved regulation compliance. With Senao being the stuttering, red-headed bastard half step cousing of Ubiquity, it is not inconceivable that they too have had to make some revisions.
I tried the TFTPd32 method, seems the device does not have a bootloader at 192.168.11.1
The device never tries to connect to 192.168.11.2 during startup or after 30/30/reset ect.
I also tried installing bootloader from the forums method and no go.
The device pings @ 192.168.1.1 right from power on, tftp and telnet methods to upgrade firmware fail.. The webui looks for .dlf files to upgrade its software. Senao firmware come in 2 files, 1 is the kernel, and the other is the apps... Not sure what to try next, I think we have to get a bin that will pass encrytion for .dlf files and flash from webui.
Posted: Thu Jun 16, 2011 19:19 Post subject: EAP-9550
ok,
So I decide to call engenius technologies to see if this device has a redboot port or special IP ect that would allow dd-wrt to be written to it. I was on hold for well over and hour and was then able to communicate with there tech "Marcos" Here is the summary of what I was told.
1. Only the EAP-3660 is supported by dd-wrt, the 9550 is not supported.
2. The .dlf files are encrypted WEBUI flash files only and there is no opensource for this router.
3. There are no future plans of releasing source or encryption headers to the community going forward with their products. There products are going to remain closed source... And if you are able to get dd-wrt on the device successfully then you voice the warrenty ect.
In a nutshell he said that engenious took alot of RMA's cause people bricked there router trying to get dd-wrt installed, so an executive decision was made to close source all new products.
so to get this working someone is officially going to have to DUMP the cfe, find the encryption method for webui or alternate redboot. I am doubtful at this point anyone has gotten dd-wrt to work with newer model EAP-9550's. Back to the shelf it goes until I solder a serial up and decide if its worth dumping the cfe.
Fractal.
Incase anyone wants there contact info and doesnt know how to use google.
Please choose the operation:
1: Load system code to SDRAM via TFTP.
1: System Load Linux to SDRAM via TFTP.
Please Input new ones /or Ctrl-C to discard
Input device IP (192.168.99.9) ==:192.168.99.9
Input server IP (192.168.99.8) ==:192.168.99.8
Input Linux Kernel filename (uImageEAP9550) ==:firmware.bin
Using Eth0 device
TFTP from server 192.168.99.8; our IP address is 192.168.99.9
Filename 'firmware.bin'.
Loading: *
ArpTimeoutCheck
Got ARP REPLY, set server/gtwy eth addr (00:23:5a:f1:a2:ad)
Got it
T #
first block received
################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#######
done
Bytes transferred = 3691602 (385452 hex)
File: env_flash.c, Func: saveenv, Line: 300
Un-Protected 1 sectors
Erasing Flash...