On 2014/9/20 17:18, swigger wrote:
Openwrt recently adds Qihoo [NYSE:QIHU] C301 router support.
However, this router has a backup firmware in the second flash and the
current trunk can only boot 3 times before u-boot boots into that backup
firmware. This is a stratgy for unbricking.
This
Well, it's a good idea.
But I don't know how to create a wiki page.
QIhoo 360 C301 (http://luyou.360.cn/parameter.html, Simplified Chinese
ONLY), has two 16M flash.
The first flash is full functional, and the second has just a backup firmware.
U-boot will boot into the second flash when it
El 22/09/14 01:51, Claudio Leite ha escrit:
I'm not sure the MediaTek driver still uses the old format from the
Ralink driver. If so, this might be helpful:
https://github.com/WRTnode/openwrt-packages/blob/master/ralink/ralink-wifi/files/lib/wifi/ralink.sh
I think that was for a project
Just got the device... Wow
On 22 September 2014 15:47, swigger swig...@gmail.com wrote:
Well, it's a good idea.
But I don't know how to create a wiki page.
QIhoo 360 C301 (http://luyou.360.cn/parameter.html, Simplified Chinese
ONLY), has two 16M flash.
The first flash is full functional,
NO, not seama. Seama is only a container, not an encrypted format.
The original OEM firmware is encrypted by AES ECB mode and have a
RSA-1024 signuature.
The aes key is base64_decode(lbhySwdj31NGnuebNn9FmQ==);
The oem's upgrade firmware web page ONLY allows encrypted firmware
while the u-boot
Flashing back to OEM through OpenWrt's sysupgrade process is also OK,
but you should cut-off extra seama header from the decrypted OEM
firmware.
then just run:
mtd -r write your-decrypted-oem-firmware firmware
On Mon, Sep 22, 2014 at 4:10 PM, Yousong Zhou yszhou4t...@gmail.com wrote:
Just got
Qihoo C301 has 2 flash chips of which one is used as primary and the
other is used as backup. OEM U-Boot will try to boot an activeregion N
with imageNstatus=0 and imageNtrynum = imagemaxtry. If such a region
is found, bootloader will try to increment imageNtrynum and boot it.
This patch tries
On 22 September 2014 16:42, swigger swig...@gmail.com wrote:
NO, not seama. Seama is only a container, not an encrypted format.
The original OEM firmware is encrypted by AES ECB mode and have a
RSA-1024 signuature.
The aes key is base64_decode(lbhySwdj31NGnuebNn9FmQ==);
The oem's upgrade
From 349a53426c78da1d02ecb8b8ade6b8c4de4057c2 Mon Sep 17 00:00:00 2001
From: Geoffrey McRae ge...@spacevs.com
Date: Mon, 22 Sep 2014 21:49:32 +1000
Subject: [PATCH 1/2] Lantiq: Fix the ath9k pci eeprom init code to use
the
BAR0 base address instead of a fixed address
Fixes support for AR9287
From de6e557c769c29be97a56e909a1b31a0c67625d5 Mon Sep 17 00:00:00 2001
From: Geoffrey McRae ge...@spacevs.com
Date: Mon, 22 Sep 2014 22:48:01 +1000
Subject: [PATCH 2/2] Add target TP-Link TD-W8980
Signed-off-by: Geoffrey McRae ge...@spacevs.com
---
still wandering around the openwrt code base and, every so often, i
come across the explicit use of FORCE prerequisites, like this in
target/sdk/files/Makefile:
clean: FORCE
rm -rf $(BUILD_DIR) $(BIN_DIR)
dirclean: clean
rm -rf $(TMP_DIR)
# check prerequisites before starting
It does NOT run on my router.
root@OpenWrt:~# cat /etc/config/ubootenv
config ubootenv
option dev '/dev/mtd9'
option offset '0x0'
option envsize '0x1'
option secsize '0x1'
root@OpenWrt:~# fw_printenv
Cannot parse config file: No such file or directory
What's wrong?
-邮件原件-
hi, swigger
On Sep 22, 2014 10:04 PM, swigger swig...@gmail.com wrote:
It does NOT run on my router.
root@OpenWrt:~# cat /etc/config/ubootenv
config ubootenv
option dev '/dev/mtd9'
option offset '0x0'
option envsize '0x1'
option secsize '0x1'
root@OpenWrt:~# fw_printenv
This could be used on Netgear R6250 once we get NAND working correctly.
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
target/linux/bcm53xx/image/Makefile| 4
target/linux/bcm53xx/image/ubinize.cfg | 24
2 files changed, 28 insertions(+)
create mode 100644
14 matches
Mail list logo
