The content of this topic has been archived between 12 Mar 2018 and 5 May 2018. Unfortunately there are posts – most likely complete pages – missing.
Might be something is messing your configuration, try to make some cleaning with the command
mtd erase -r rootfs_dataAnd use the command line for scanning after enabling the wifi interface
iw dev wlan0 scanYou can also check the wifi calibration data
cat /proc/mtd4 |hexdumpand compare it with the working one in your other hg655b, I've put this calibration data at the wiki:
http://wiki.openwrt.org/toh/huawei/hg65 … ation.data
Here you go
[ 0.000000] NR_IRQS:256
[ 0.000000] Calibrating delay loop... 397.82 BogoMIPS (lpj=795648)
[ 0.032000] pid_max: default: 32768 minimum: 301
[ 0.036000] Mount-cache hash table entries: 512
[ 0.044000] SMP: Booting CPU1...
[ 0.048000] CPU revision is: 0002a031 (Broadcom BMIPS4350)
[ 0.048000] Primary instruction cache 64kB, VIPT, 4-way, linesize 16 bytes.
[ 0.048000] Primary data cache 32kB, 2-way, VIPT, cache aliases, linesize 16 bytes
[ 0.080000] Synchronize counters for CPU 1: done.
[ 0.080000] SMP: CPU1 is running
[ 0.084000] Brought up 2 CPUs
[ 0.108000] NET: Registered protocol family 16
[ 0.116000] registering PCI controller with io_map_base unset
[ 0.132000] bio: create slab <bio-0> at 0
[ 0.136000] PCI host bridge to bus 0000:00
[ 0.140000] pci_bus 0000:00: root bus resource [mem 0x30000000-0x37ffffff]
[ 0.144000] pci_bus 0000:00: root bus resource [io 0x8000000-0x800ffff]
[ 0.148000] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[ 0.164000] pci 0000:00:01.0: BAR 0: assigned [mem 0x30000000-0x3000ffff]
[ 0.168000] Switching to clocksource MIPS
[ 0.176000] NET: Registered protocol family 2
[ 0.184000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
[ 0.188000] TCP bind hash table entries: 512 (order: 0, 4096 bytes)
[ 0.196000] TCP: Hash tables configured (established 512 bind 512)
[ 0.204000] TCP: reno registered
[ 0.204000] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.212000] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.220000] NET: Registered protocol family 1
[ 0.228000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.232000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.244000] msgmni has been set to 119
[ 0.248000] io scheduler noop registered
[ 0.252000] io scheduler deadline registered (default)
[ 0.260000] bcm63xx_uart.0: ttyS0 at MMIO 0xb0000100 (irq = 10) is a bcm63xx_uart
[ 0.268000] console [ttyS0] enabled, bootconsole disabled
[ 0.268000] console [ttyS0] enabled, bootconsole disabled
[ 0.280000] bcm63xx-rng bcm63xx-rng: registered RNG driver
[ 0.288000] physmap platform flash device: 08000000 at 18000000
[ 0.296000] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x001000
[ 0.304000] Amd/Fujitsu Extended Query Table at 0x0040
[ 0.312000] Amd/Fujitsu Extended Query version 1.3.
[ 0.316000] number of CFI chips: 1
[ 0.320000] bcm63xxpart: CFE boot tag found with version 7 and board type HW65x
[ 0.328000] bcm63xxpart: Partition 0 is CFE offset 0 and length 20000
[ 0.336000] bcm63xxpart: Partition 1 is kernel offset 20100 and length 10ff00
[ 0.340000] bcm63xxpart: Partition 2 is rootfs offset 130000 and length 690000
[ 0.348000] bcm63xxpart: Partition 3 is cal_data offset 7c0000 and length 10000
[ 0.356000] bcm63xxpart: Partition 4 is nvram offset 7f0000 and length 10000
[ 0.364000] bcm63xxpart: Partition 5 is linux offset 20000 and length 7a0000
[ 0.372000] bcm63xxpart: Spare partition is offset 730004 and length 8fffc
[ 0.380000] 6 bcm63xxpart partitions found on MTD device physmap-flash.0
[ 0.384000] Creating 6 MTD partitions on "physmap-flash.0":
[ 0.392000] 0x000000000000-0x000000020000 : "CFE"
[ 0.400000] 0x000000020100-0x000000130000 : "kernel"
[ 0.404000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[ 0.420000] 0x000000130000-0x0000007c0000 : "rootfs"
[ 0.428000] mtd: device 2 (rootfs) set to be root filesystem
[ 0.432000] mtd: partition "rootfs_data" created automatically, ofs=0x730000, len=0x90000
[ 0.440000] 0x000000730000-0x0000007c0000 : "rootfs_data"
[ 0.448000] 0x0000007c0000-0x0000007d0000 : "cal_data"
[ 0.456000] 0x0000007f0000-0x000000800000 : "nvram"
[ 0.464000] 0x000000020000-0x0000007c0000 : "linux"
[ 0.472000] bcm63xx-spi bcm63xx-spi: at 0xb0000800 (irq 9, FIFOs size 542)
[ 0.520000] b53_common: found switch: BCM63xx, rev 0
[ 0.524000] bcm63xx-wdt bcm63xx-wdt: started, timer margin: 30 sec
[ 0.540000] TCP: cubic registered
[ 0.540000] NET: Registered protocol family 17
[ 0.548000] 8021q: 802.1Q VLAN Support v1.8
[ 0.560000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[ 0.568000] Freeing unused kernel memory: 248K (80312000 - 80350000)
procd: Console is alive
procd: - watchdog -
procd: - preinit -
[ 2.584000] bcm63xx_enetsw bcm63xx_enetsw.0: link UP on port1, 100Mbps, full-duplex
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[ 4.072000] usbcore: registered new interface driver usbfs
[ 4.080000] usbcore: registered new interface driver hub
[ 4.084000] usbcore: registered new device driver usb
[ 4.096000] Button Hotplug driver version 0.4.1
[ 4.172000] SCSI subsystem initialized
[ 4.188000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 4.196000] ehci-platform: EHCI generic platform driver
[ 4.308000] ehci-platform ehci-platform: EHCI Host Controller
[ 4.312000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
[ 4.320000] ehci-platform ehci-platform: irq 15, io mem 0xb0001500
[ 4.340000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00, overcurrent ignored
[ 4.348000] hub 1-0:1.0: USB hub found
[ 4.352000] hub 1-0:1.0: 2 ports detected
[ 4.360000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 4.368000] ohci-platform ohci-platform: Generic Platform OHCI Controller
[ 4.376000] ohci-platform ohci-platform: new USB bus registered, assigned bus number 2
[ 4.384000] ohci-platform ohci-platform: irq 13, io mem 0xb0001600
[ 4.448000] hub 2-0:1.0: USB hub found
[ 4.452000] hub 2-0:1.0: 2 ports detected
[ 4.468000] usbcore: registered new interface driver usb-storage
[ 4.476000] input: gpio-keys-polled as /devices/platform/gpio-keys-polled.0/input/input0
No jffs2 marker was found
procd: - early -
procd: - watchdog -
procd: - ubus -
procd: - init -
Failed to connect to ubus
Please press Enter to activate this console.
[ 9.624000] NET: Registered protocol family 10
[ 9.652000] nf_conntrack version 0.5.0 (961 buckets, 3844 max)
[ 9.668000] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 9.704000] fuse init (API version 7.22)
[ 9.712000] usbcore: registered new interface driver cdc_acm
[ 9.720000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 9.728000] Loading modules backported from Linux version master-2014-03-31-1-0-g5c109d2
[ 9.736000] Backport generated by backports.git backports-20140221-0-g8e94650
[ 9.752000] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 9.828000] usbcore: registered new interface driver usbserial
[ 9.836000] usbcore: registered new interface driver usbserial_generic
[ 9.844000] usbserial: USB Serial support registered for generic
[ 9.876000] xt_time: kernel timezone is -0000
[ 9.916000] cfg80211: Calling CRDA to update world regulatory domain
[ 9.924000] cfg80211: World regulatory domain updated:
[ 9.932000] cfg80211: DFS Master region: unset
[ 9.936000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 9.944000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 9.952000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 9.964000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 9.972000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 9.980000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 9.988000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 10.080000] PPP generic driver version 2.4.2
[ 10.088000] NET: Registered protocol family 24
[ 10.136000] ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'rt2x00.eeprom'.
[ 10.280000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected
[ 10.288000] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0001 detected
[ 15.448000] bcm63xx_enetsw bcm63xx_enetsw.0: link UP on port1, 100Mbps, full-duplex
[ 20.020000] bcm63xx_enetsw bcm63xx_enetsw.0: link UP on port1, 100Mbps, full-duplex
[ 20.056000] device eth0.1 entered promiscuous mode
[ 20.060000] device eth0 entered promiscuous mode
[ 20.068000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
[ 20.076000] br-lan: port 1(eth0.1) entered forwarding state
[ 20.080000] br-lan: port 1(eth0.1) entered forwarding state
[ 21.920000] jffs2: notice: (1036) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 22.084000] br-lan: port 1(eth0.1) entered forwarding state
procd: - init complete -
BusyBox v1.19.4 (2014-04-20 18:24:56 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
BARRIER ÉÉ¥ÉBreaker, r40396)
-----------------------------------------------------
* 1/2 oz Galliano Pour all ingredients into
* 4 oz cold Coffee an irish coffee mug filled
* 1 1/2 oz Dark Rum with crushed ice. Stir.
* 2 tsp. Creme de Cacao
-----------------------------------------------------
root@OpenWrt:/# [ 68.580000] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
[ 68.680000] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34
[ 68.788000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 68.796000] device wlan0 entered promiscuous mode
[ 68.816000] br-lan: port 2(wlan0) entered forwarding state
[ 68.820000] br-lan: port 2(wlan0) entered forwarding state
[ 68.824000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 70.824000] br-lan: port 2(wlan0) entered forwarding state
root@OpenWrt:/# iw dev wlan0 scan
root@OpenWrt:/# cat /proc/mtd
dev: size erasesize name
mtd0: 00020000 00010000 "CFE"
mtd1: 0010ff00 00010000 "kernel"
mtd2: 00690000 00010000 "rootfs"
mtd3: 00090000 00010000 "rootfs_data"
mtd4: 00010000 00010000 "cal_data"
mtd5: 00010000 00010000 "nvram"
mtd6: 007a0000 00010000 "linux"
root@OpenWrt:/# cat /proc/mtd4 |hexdump
cat: can't open '/proc/mtd4': No such file or directory
root@OpenWrt:/# cat /dev/mtd |hexdump
mtd0 mtd1ro mtd3 mtd4ro mtd6 mtdblock1 mtdblock4
mtd0ro mtd2 mtd3ro mtd5 mtd6ro mtdblock2 mtdblock5
mtd1 mtd2ro mtd4 mtd5ro mtdblock0 mtdblock3 mtdblock6
root@OpenWrt:/# cat /dev/mtd4 |hexdump
0000000 dead c0de ffff ffff ffff ffff ffff ffff
0000010 ffff ffff ffff ffff ffff ffff ffff ffff
*
0010000
root@OpenWrt:/#Looks like you finally destroyed your calibration data, or it was already empty (probably not). Not a problem, you can recover it from your sane router.
First backup the cal_data from the sane router (the one with the wifi working):
dd if=/dev/mtd4 of=calibration_data.binTransfer this binary to the router with the missing wifi and write it to the cal_data partition (/dev/mtd4)
mtd write calibration_data.bin cal_dataOK, thank youvery much.
Let me tell you how this happened: I flashed the 8mb image, then I reflashed the original stock image and it worked again. Then I tried all openwrt images and didn't work. But I don't understand why it works with the original firmware.
Can you put a limit of size for the squashfs image file when compiling?
Regards
AFAIK, there isn't a default mechanism to limit the size of built images. OpenWrt bots don't create images with sizes > 4MB because with the default selected packages this is almost impossible.
Hi,
i did that and it works now after:
reading/saving caliration data
root@Huawei:/tmp# cat /proc/mtd
dev: size erasesize name
mtd0: 00020000 00010000 "CFE"
mtd1: 0010ff00 00010000 "kernel"
mtd2: 00690000 00010000 "rootfs"
mtd3: 00090000 00010000 "rootfs_data"
mtd4: 00010000 00010000 "cal_data"
mtd5: 00010000 00010000 "nvram"
mtd6: 007a0000 00010000 "linux"
root@Huawei:/tmp# dd if=/dev/mtd4 of=calibration_data.bin
128+0 records in
128+0 records out
root@Huawei:/tmp#writing calibration data
root@OpenWrt:/# cat /proc/mtd[J
dev: size erasesize name
mtd0: 00020000 00010000 "CFE"
mtd1: 0010ff00 00010000 "kernel"
mtd2: 00690000 00010000 "rootfs"
mtd3: 00090000 00010000 "rootfs_data"
mtd4: 00010000 00010000 "cal_data"
mtd5: 00010000 00010000 "nvram"
mtd6: 007a0000 00010000 "linux"
root@OpenWrt:/#
root@OpenWrt:/# cd /tmp
root@OpenWrt:/tmp# mtd write calibration_data.bin cal_data
Unlocking cal_data ...
Writing from calibration_data.bin to cal_data ... [ ][e][w]
root@OpenWrt:/tmp# rebooterasing rootfs
restarting
root@OpenWrt:/# cat /proc/mtd4 |hexdump[Jroc/mtd4 |hexdump[J[17Doc/mtd4 |hexdump[J[16Dc/mtd4 |hexdump[J[15D/mtd4 |hexdump[J[14Dd/mtd4 |hexdump[14De/mtd4 |hexdump[14Dv/mtd4 |hexdump[14D/mtd4 |hexdump
0000000 6230 0100 72d1 5e0d ad6c 6230 1418 0180
0000010 0000 6230 1418 0000 0100 6aff 0c00 ffff
0000020 ffff ffff b092 ffff ffff ffff ffff ffff
0000030 ffff ffff 2208 2400 ffff 1601 ffff d9fa
0000040 cc88 ffff 0dff 0000 0300 0000 0000 ffff
0000050 ffff 0e0f 0f0f 1010 1010 100f 0f0f 0f0f
0000060 0c0c 0c0c 0c0c 0c0c 0c0b 0b0b 0b0b ffff
0000070 ffff ffff ffff ffff ffff ffff ffff ffff
*
00000d0 ffff ffff ffff ffff ffff ffff ffff 5555
00000e0 8888 7777 6666 6666 6666 6666 6666 6666
00000f0 ffff ffff ffff ffff ffff ffff ffff ffff
*
00001f0 ffff ffff ffff ffff ffff ffff ff06 8693
0000200 ffff ffff ffff ffff ffff ffff ffff ffff
*
0010000
root@OpenWrt:/# mtd erase -r rootfs_data
Unlocking rootfs_data ...
Erasing rootfs_data ...
Rebooting ...(Last edited by fratzicu on 10 May 2014, 20:46)
Hi,
It seems I solved the problems, but I have another one. It keeps giving me this error
br-lan: received packet on eth0.1 with own address as source addressHi,
I had trouble connecting to the second wifi I think because the two routers had thevsame mac addresses. How can I restore the original mac address of the wifi that is written on the box?
It might be possible to hex edit the calibration data but there exist two problems:
- you need to know the offset for the mac address
- if you edit the calibration data you you might invalidate the checksum, you'll need to know how to fix the checsum once edited.
But still you may have the possibility to use another mac address configuring it in the file /etc/config/wireless
Example:
config wifi-device radio0
option type mac80211
option hwmode 11bg
option phy phy0
option macaddr BE:BE:CA:FE:08:00
the configuration for for a new mac address is highlighted in green
(Last edited by danitool on 11 May 2014, 13:36)
Hi,
I did that,but is there a possibility for hardcoding the device's mac address?
Also, it seems that even if I put the mac in the /etc/config/wireless I still get the error message.
Another thing: when creating the network devices with the webUI, the mac address is the same in te two routers. But I don't kno where the message comes from:
br-lan: received packet on eth0.1 with own address as source addressMy eth0.1 isa vlan that is bridged with the wifi. i'll do some other tests this week and i'l put the settings
Does not matter
I was able to fix it. I have recompiled a firmware image with the IPv6 Tunnels Brokers packages preinstalled .
http://www.multiupload.nl/B9VFUMD2M6
openwrt-HG655x-squashfs-cfe-2014-05-25.bin (5.31 MB)
"Thanks to all who participated in this project
I have encountered the following problem and I need a little help:
I tried to install several modules for IPv6 tunnel to HE.net (tunnelbroker.com)
I got the following error in the console:
opkg update
opkg install 6in4 ip ip6tables kmod-sit kmod-iptunnel6 radvd kmod-tun gw6c wide-dhcpv6-server
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for 6in4:
* kernel (= 3.10.36-1-ea8f6e4be2fe1c84c4d5d46369797212) * kernel (= 3.10.36-1-ea8f6e4be2fe1c84c4d5d46369797212) * kernel (= 3.10.36-1-ea8f6e4be2fe1c84c4d5d46369797212) *
* opkg_install_cmd: Cannot install package 6in4.
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-sit:
* kernel (= 3.10.36-1-ea8f6e4be2fe1c84c4d5d46369797212) * kernel (= 3.10.36-1-ea8f6e4be2fe1c84c4d5d46369797212) * kernel (= 3.10.36-1-ea8f6e4be2fe1c84c4d5d46369797212) *
* opkg_install_cmd: Cannot install package kmod-sit.
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-iptunnel6:
* kernel (= 3.10.36-1-ea8f6e4be2fe1c84c4d5d46369797212) *
* opkg_install_cmd: Cannot install package kmod-iptunnel6.
You can create a precompiled version which contains that modules ?
You can remove in the firmware these packages? Because they are too big: DLNA , transmission client and OpenVPN
You can insert these packages in the build? : 6in4 , ip , ip6tables , kmod-sit , kmod-iptunnel6 , radvd
libdaemon , kmod-ip6tables , kmod-tun , gw6c , wide-dhcpv6-server
Please help me because I'm stuck in this problem and can not use the router for what I wanted.
I also have a router Huawei HG-533 Vodafone Station with OpenWrt Attitude Adjustment 12.09
I successfully managed to install packages for tunnel brokers , and it works well.
It is possible a firmware for Huawei HG655b based on OpenWrt Attitude Adjustment 12.09 ?"
(Last edited by free4allandall4free on 26 May 2014, 12:41)
Hi,
I have a (spare) Huawei HG655D and I would like to test openwrt on it.
I tried to flash a few of the builds from danitool using the OEM easy install method. It doesn't seem to be flashing anything. When I tried to flash a newer firmware it worked, but the openwrt build from danitool won't flash.
Is there a way to flash this build without serial or jtag acces?
Thanks in advance
Mauritso
(Last edited by mauritso on 23 May 2014, 17:31)
Hi,
I have a (spare) Huawei HG655D and I would like to test openwrt on it.
I tried to flash a few of the builds from danitool using the OEM easy install method. It doesn't seem to be flashing anything. When I tried to flash a newer firmware it worked, but the openwrt build from danitool won't flash.
Is there a way to flash this build without serial or jtag acces?
Thanks in advance
Mauritso
Do you have the firmware it worked flashing your router? I can analyze the header and fix the problem.
BTW sometimes some browsers doesn't work with CFE when loading new firmwares for flashing. Try with another browser or with another browser in another computer.
mauritso wrote:Hi,
I have a (spare) Huawei HG655D and I would like to test openwrt on it.
I tried to flash a few of the builds from danitool using the OEM easy install method. It doesn't seem to be flashing anything. When I tried to flash a newer firmware it worked, but the openwrt build from danitool won't flash.
Is there a way to flash this build without serial or jtag acces?
Thanks in advance
Mauritso
Do you have the firmware it worked flashing your router? I can analyze the header and fix the problem.
BTW sometimes some browsers doesn't work with CFE when loading new firmwares for flashing. Try with another browser or with another browser in another computer.
This is the official firmware that worked:
https://dl.dropboxusercontent.com/u/264 … e_main.bin
I tried build 1, 3 and 9 of yours.
I will try build 9 again in a different browser (in a few hours).
EDIT:
So I tried build 9 with firefox and chrome and sadly the same thing happened. It said that it would take 2 minutes for it to flash and it almost immediately restarts to the normal firmware.
(Last edited by mauritso on 24 May 2014, 11:46)
I didn't see noticeable differences in the OEM firmware header you posted here compared with the openwrt firmwares I built.
Can you confirm the original firmware you posted here works for flashing in the same computer and with the same browsers where the openwrt firmware didn't work?
So this is embarassing. I am not an expert OpenWRT user, but novice-to-low-intermediate range. It appeared this was very cool, as I have two different HG655b from an ISP who did not want them back. So I do need the DSL, and I decided to flash.
So I logged into the router, went right to the the maintenance page, and uploaded the bin (your 11th version, openwrt-HG655x-squashfs-cfe-11.bin), and gave it a spin. Looked like the router reboot after walking away for ten or fifteen minutes. Looks like it did not go so well.
I see default SSID for the ISP/OEM branded image. When I visit the admin interface, I see LUCI written in the corner and the blackground page, but then rapid reloads that crunch CPU and bring my browser to a halt. I tried many times and a few reboots. I cannot get it to load.
I log in via telnet, as I am used to such things going not so hot, and I see the default ATP system. I go to ATP and try equipcmd resetdefault (a la HG612 hacking blog on Wordpress). I reboot the router and the reset appears to leave me where I currently am. Next I do more research run "APT> shell" at the prompt to bring up busybox. I look around and find mtd info like fratzicu found, but not sure how to repair the ROM.
Did I brick this thing? Do I/can I set up TFTPD on my laptop and then flash with TFTP to bring back up.
If not, no biggy. I had two. I thought I was patient, but apparently it is late and I am moron. Thanks for your help.
UPDATE: It appears that the flashing LUCI interface issue is something unrelated. It seems to be browser caching. I am having the same issue reported by the previous post: after two minutes, no flashing is actually occurring. And this is according to the debug log.
Debug log from the default ROM:
Manufacturer:Huawei Technologies Co., Ltd.
Product Style:HG655b
SN:12345678910123456789
Hardware Version:VER.C
Software Version:V100R001C07B019
2000-01-01 03:00:27 User Notice web 1 User admin login from 192.168.1.2 successfully.
2000-01-01 03:00:18 Security Notice cms 1 System up
2000-01-01 03:01:29 Deamon Warning upg 1 Reboot from the LAN side.
2000-01-01 03:01:27 Deamon Warning upg 0 Upgrading fail: File format error.
2000-01-01 03:01:23 Deamon Warning web 1 Upgrading beginning ...
2000-01-01 03:00:47 User Notice web 1 User admin login from 192.168.1.2 successfully.
2000-01-01 03:00:18 Security Notice cms 1 System up
2000-01-01 03:02:59 Deamon Warning web 1 Reboot from the LAN side.So, does this mean TFTP? Some mangling of the ROM to prevent updating? Thoughts?
(Last edited by alh on 24 May 2014, 22:34)
Tried with another computer, still didn't work.
I have the HG655D board rev. A from my previous ISP who didn't want it back (Netherlands, Online)
I flashed an old firmware (http://www49.zippyshare.com/v/66747841/file.html), that worked.
Logs show:
2000-01-01 03:01:23 Deamon Warning web 1 Upgrading beginning ...
And then nothing when I try to upload the OpenWRT firmware.
If you need output from certain commands, that is possible as I do have telnet/ATP/shell acces.
(Last edited by mauritso on 26 May 2014, 17:52)
Tried with another computer, still didn't work.
I have the HG655D board rev. A from my previous ISP who didn't want it back (Netherlands, Online)
I flashed an old firmware (http://www49.zippyshare.com/v/66747841/file.html), that worked.
Logs show:
2000-01-01 03:01:23 Deamon Warning web 1 Upgrading beginning ...
And then nothing when I try to upload the OpenWRT firmware.
If you need output from certain commands, that is possible as I do have telnet/ATP/shell acces.
Have you tried in this way?
Unplug the power cord
Press the button labeled as RESET, don't release it yet!
Plug the power cord
Wait 10 seconds
Release the RESET button
Browse to http://192.168.1.1
Select the .bin firmware file
Upgrade software
Wait for it to reboot
Telnet to 192.168.1.1 and set a root password, or browse to http://192.168.1.1 if LuCI is installed.
mauritso wrote:Tried with another computer, still didn't work.
I have the HG655D board rev. A from my previous ISP who didn't want it back (Netherlands, Online)
I flashed an old firmware (http://www49.zippyshare.com/v/66747841/file.html), that worked.
Logs show:
2000-01-01 03:01:23 Deamon Warning web 1 Upgrading beginning ...
And then nothing when I try to upload the OpenWRT firmware.
If you need output from certain commands, that is possible as I do have telnet/ATP/shell acces.
Have you tried in this way?
Unplug the power cord
Press the button labeled as RESET, don't release it yet!
Plug the power cord
Wait 10 seconds
Release the RESET button
Browse to http://192.168.1.1
Select the .bin firmware file
Upgrade software
Wait for it to reboot
Telnet to 192.168.1.1 and set a root password, or browse to http://192.168.1.1 if LuCI is installed.
That is exactly the method I used, except it reboots within 10 seconds to the normal firmware. When I selected an official firmware (doesn't matter if it was older, current or newer) it flashed normally and it reboots into the newly flashed firmware.
Yesterday i have recompiled a firmware image with the IPv6 Tunnels Brokers packages preinstalled .
without DLNA package preinstaled, without OpenVPN package preinstaled, without NetworkPrinter package preinstaled,
without transmission package preinstaled
Take a trial
http://www.multiupload.nl/B9VFUMD2M6
openwrt-HG655x-squashfs-cfe-2014-05-25.bin (5.31 MB)
Yesterday i have recompiled a firmware image with the IPv6 Tunnels Brokers packages preinstalled .
without DLNA package preinstaled, without OpenVPN package preinstaled, without NetworkPrinter package preinstaled,
without transmission package preinstaledTake a trial
http://www.multiupload.nl/B9VFUMD2M6
openwrt-HG655x-squashfs-cfe-2014-05-25.bin (5.31 MB)
Tried that one too, looks good btw.
Looks like there was a missing flag in the openwrt firmware header: --info1
HG655bV100R001C02B0 for HG556b
HG655dV100R001C02B0 for HG655d
I splitted the firmware for the known two versions, built firmwares are exactly the same, I just added this flag to the firmware header. Give it a try.
openwrt-HG655x-squashfs-cfe-12.zip
Bootlogs are welcome.
Looks like there was a missing flag in the openwrt firmware header: --info1
HG655bV100R001C02B0 for HG556b
HG655dV100R001C02B0 for HG655dI splitted the firmware for the known two versions, built firmwares are exactly the same, I just added this flag to the firmware header. Give it a try.
openwrt-HG655x-squashfs-cfe-12.zip
Bootlogs are welcome.
Still doesn't work.
I made some screenshots and I copied the log from the device itself. Unfortunately I don't have a serial cable, so I can't help you with the boot log part.
Hi,
I did that,but is there a possibility for hardcoding the device's mac address?
Also, it seems that even if I put the mac in the /etc/config/wireless I still get the error message.Another thing: when creating the network devices with the webUI, the mac address is the same in te two routers. But I don't kno where the message comes from:
br-lan: received packet on eth0.1 with own address as source addressMy eth0.1 isa vlan that is bridged with the wifi. i'll do some other tests this week and i'l put the settings
Hi,
I owe you this last thing, but ufortunately I got into some other stuff. I'll return after 13th june. I'mglad this project continues. I just want to tell you that my hg655b woks fine, continuously since then and I use it mainly as a wired bridge repeater and a media server with anexternal usb hdd and it works very fine with no crash.
I hop ethe HG655d does the same.
mauritso wrote:Tried with another computer, still didn't work.
I have the HG655D board rev. A from my previous ISP who didn't want it back (Netherlands, Online)
I flashed an old firmware (http://www49.zippyshare.com/v/66747841/file.html), that worked.
Logs show:
2000-01-01 03:01:23 Deamon Warning web 1 Upgrading beginning ...
And then nothing when I try to upload the OpenWRT firmware.
If you need output from certain commands, that is possible as I do have telnet/ATP/shell acces.
Have you tried in this way?
Unplug the power cord
Press the button labeled as RESET, don't release it yet!
Plug the power cord
Wait 10 seconds
Release the RESET button
Browse to http://192.168.1.1
Select the .bin firmware file
Upgrade software
Wait for it to reboot
Telnet to 192.168.1.1 and set a root password, or browse to http://192.168.1.1 if LuCI is installed.
So I too used this method on previous occasions. Like mauritso, the device does reboot, but boots into the original stock firmware I got from my ISP. When I telnet into the device, I get the ATP shell. This is part of the original firmware obviously. As mentioned above, even when doing the reset and following your instructions, the logs specifically mention bailing and rebooting because the bin image is not in the right format.
I will try the updated firmware when I have a chance, danitool. But the error log I gave you is the only thing available logging-wise on the stock firmware provided on my ISP. Is there some way to debug further, because I use the ATP shell to drop into Busybox. If you want more info, I can get it for you.