dbisoi wrote:Hi,
I have been using a TEW 652 BRP which is fine but boots very frequently.Which is very annoying.Has anyone found a solution?I have tried keeping it upright but do not think helps a lot.Will flashing it DIR 615 fw make it better?
Has anyone found a solution to this problem?
Thanks,
Dbisoi
Hi dbisoi,
I also have a TEW 652-BRP v1.1 (got mine from Fry’s, so yours maybe a 1.0, or 1.1, i can't speak for the 2.x line) which would reboot every 10 seconds after a failed attempt of upgrading from 1.10.08 to 1.10.14 of Trendnet's factory firmware. From what i read, when that happens, your router is "bricked" / hosed whatever you want to call it and needs to be re-flashed. Here's the process i followed to get it working again w/ the original tew-652brp firmware (as well as OpenWrt and DIR all on the same tew-652brp unit).
Getting to uboot / recovery flash mode:
0) unplug your router
1) Press in and hold your reset button and do NOT release
2) While holding the reset button, plug the power back into your router and continue to hold the reset button
3) The status light will come on and hold and eventually it will start blinking ever 1/2 - 1 second. Once it starts to repeatedly flash, release the reset button and connect an ethernet cord to your PC (if you haven't already).
4) Go into your PC's network settings and assign yourself the private IP of 192.168.0.2
5) The router is now in recover mode and is listening to HTTP request on 192.168.0.1
6) Open up Internet explorer (or Firefox, just make sure you clear your caches in both) and navigate to 192.168.0.1
7) You are now in the recovery flash GUI
Re-flashing your tew-652brp to original settings:
This gets tricky as each unit was "initially" flashed differently depending on when it was released. In my case, i actually had to flash it back to a 632BRP flash (because my unit was expecting a tew632-BRP product ID, i still wonder if the hw is the same in these units). You can try various flash files and the recover flash will tell you if the file is valid or invalid. What i learned for me is you should first try the following flash files to recover to factory settings.
1) Try the original FW 1.10.B08 (1.10.08) TEW652BRPA1_FW110B08.bin
2) If it says this is an invalid image file, before trying something else, open the file in Notepad++ (or another hex editor) and go the very end of the file and try changing it to one of the following PRODUCT ID's depending on your product (See Product Identity Codes below).
(For example, if the TEW-632 BRP firmware is what works for you to get out of recovery mode and recover your router, then you need to use the TEW-632BRP Product ID in the TEW-652BRP 1.10.B08 file in order for it to load successfully when you convert back to 652brp firmware. If the TEW-652BRP 1.10.08 worked for you without having to back to the 632 firmware, then more than likely you can just bypass the product ID changes. Hope that didn't confuse you)
3) If this was successful, it will begin to download the firmware (DO NOT STOP THE PROCESS even if your PC says you're LAN is unplugged. DO NOT HIT BACK OR FORWARD OR STOP OR ANYTHING).
4) When the update completes successfully and the router reboots, it will come back w/ the Trendnet 1.10.08 firmware. I recommend pressing the reset button again to restore factory settings. You will need to re-configure your network settings to obtain IP address automatically as your DHCP server on your unit is now enabled and is listening on the factory IP of 192.168.10.1. If your router isn't listening on 192.168.10.1, press and hold the reset button while the unit is on to restore factory settings OR try to go to your most recently configured LAN settings as the flash process may have retained those settings if you changed them before your router got hosed.
5) If step 3 failed OR the recovery flash UI indicated the 652BRP file is still invalid after changing the product ID, try using the TEW-632BRP 1.10.B13 (1.10.13) Firmware (TEW632BRPA1_FW110B13__652.bin )
6) If this file works, afterwards you can then repeat steps 1 - 3 above using the 652 1.10.08 file but before you do, modify the product ID at the end of the bin file to match the product ID in the TEW 632 file you flashed previously.
7) When the router reboots, you'll now notice it says its a 652 router
8) At this point, you can re-flash from the Trendnet Firmware Update GUI (not the recover flash mode) an up-to-date factory firmware. OR you can flash to OpenWrt using the OpenWrt-ar71xx-tew-652brp-squashfs.uni or the DIR 615 rev C 3.11 firmware (obtained from Dlink site).
NOTE:.uni files work, if you get an invalid file error during the flash process edit the file and change the product ID to match your tew-652brp unit (u can also copy and paste it from the last working flash file you used).
NOTE: To put on the DLink DIR-615 REV C firmware, I had to start with 3.01 version of the firmware first (remember to update the flash file with the TEW-652 product ID using a hex editor like Notepad++). Use the recovery flash mode to flash the unit to 3.01 and after the unit has been flashed and reboots, you can use the DLink GUI to upgrade the firmware to 3.11.
Long story short, to recover a bricked TEW-652 to stock firmware, you need to use the recovery console and flash to the original 652 1.10.08 firmware or 632 firmware and then convert back to 652. After which you can then flash to OpenWrt or DLINK DIR Rev C (earlier revisions are not Atheros based, so make sure its rev C 3.11) firmware (using the regular admin UI or the recover flash UI.. I can't quite clearly remember, but i think the DLink firmware has to be done via recovery mode, but i think i got OpenWrt firmware to work using the normal UI).
If i've misreported anything, someone please correct me, but this is the best i could remember on what I did . I didn't take much notes along the way because i was trying to hit a moving target. It took hours of reading through these forums to figure how this all works. I hope this sums it up for people who run into this issue or just want to know how to put an open source firmware on their TEW-652BRP router. Also, if something doesn't seem clear, i recommend reading through RoundSparrow's and armchair's postings on this thread... it helped me out tremendously.
FILE LINKS:
OpenWrt TEW-652BRP Firmware snapshot: (i believe the only other option is to compile one yourself)
http://downloads.OpenWrt.org/snapshots/ … uashfs.uni
After flashing to OpenWrt to get the web GUI working perform the following:
0. After flashing to OpenWrt firmware, recycle the power on the TEW-652 unit and hold the reset button for about 30 seconds (perform a factory reset).
1. Open a command prompt and type "telnet 192.168.1.1"
2. You'll now be at the openwrt console and need to type the following (make sure your router's WAN connection is connected to a live internet connection).
3. at the prompt type opkg update
4. After the list update completes, type opkg install luci-admin-full
5. opkg install luci-fastindex
6. opkg install luci-theme-openwrt (or luci-theme-openwrtlight for retaining more flash space for additional packages)
(more details can be found on armchair's posting earlier in this thread).
DLink DIR-615 REV C 3.01/3.11NA: (must start with 3.01 first on TEW-652BRP hardware)
ftp://ftp.dlink.com/Gateway/dir615_revC … _311NA.zip
Trendnet TEW-632/652BRP Firmware downloads: (must start with 1.10.08 first to recover a TEW-652BRP unit)
http://downloads.trendnet.com/tew-652brp/firmware/
http://downloads.trendnet.com/tew-632br … r_Utility/
(on some TEW-652 units you may have to use the TEW-632BRP firmware first to recover a bricked unit and then use the TEW-652 firmware; or try changing just the identity code in the TEW-652 firmware .bin file to the 632 identity code)
Identity codes:
Trendnet TEW-632BRP version A1.1R, AP81-AR9130-RT-070614-00
Trendnet TEW-632BRP version A1.0R, AP81-AR9130-RT-070614-00
Trendnet TEW-652BRP, AP81-AR9130-RT-080609-05
DLink DIR-615 revision C1, AP81-AR9130-RT-080609-05. (IMPORTANT: Earlier revisions of this router are not Atheros based, a major change was made.)
(on some TEW-652 units, you may have to modify the identity code in the firmware file to get the recover flash console to recognize the file as a valid image).
(Last edited by oddjob on 30 Jan 2010, 23:44)