Posted: Wed Mar 21, 2018 9:40 Post subject: AsRock G10 DEAD / BRICKED - HELP NEEDED
Hi I updated my router to the newest firmware. Before I expeirenced issues that DLNA Server was not working. Therefore, I decided to go for a firmware update.
Since then, my router is DEAD, NO LED lights turning on nothing!
What I have tried so far:
30/30/30 reset
Unplug and leave for a few hours
Result: NOTHING, it is just dead. The USB hard drive receives power. However, no lights or networks or anything, just dead/bricked.
Then open up the router and look for the serial port. Don't connect the 3.3V or 5V (red) wire ever, just connect Rx, Tx and Ground. If you have trouble take a picture of the board and zip it, and upload it to this thread.
I would suggest going back to Factory firmware first, then go to dd-wrt. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
So you think it is bricked? I just do not know HOW it could happen? I just made a firmware update. I mean is dd-wrt so buggy that it bricks a device just by firmware update?
Any other method to give life to the router? I even do not know if it is really bricked, but it seems so as no LED light just nothing.
A stable DD-WRT Version would be so great (for the AsRock G10)
Posted: Wed Mar 21, 2018 19:15 Post subject: Bricked
The best way to tell if a router is bricked is to hook up a Serial cable, like I already described.
I suspect it is bricked, No LEDs flashing is not usually a good sign.
DD-WRT is in perpetual Beta, what that means is that there is never a truly stable build (not since 2010 at least). All of them are released as beta, the users are notified it is beta software. Expect bugs. I have bricked all of my routers at some point due to DD-WRT, I have since debricked all of them. Some are easier to debrick than others it depends on the manufacturer. TP-Link is the easiest to debrick, Asus is also fairly easy on the Broadcom side. Don't even try to debrick a Belkin, they are a pain. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
Posted: Fri Nov 09, 2018 13:16 Post subject: Serial
That looks like it should be serial. Make sure to find where GND and VCC are. The other two will be Tx and Rx. Don't solder anything to VCC (3.3V), it is not required.
PS: Make the photo smaller or attach it as a zip file. Other users will flip out, Malachi, etc.
Settings, no idea. Could be 115200 8N1, or 57600 or just about anything. Most likely 8N1 though. Document which pins are what though. I will start a wiki on the dd-wrt wiki site when you know. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
PCI0 Link Intialized
PCI1 Link Intialized
In: serial
Out: serial
Err: serial
cdp: get part failed for 0:HLOS
Net: MAC1 addr:0:3:7f:ba:db:1
athrs17_reg_init: complete
athrs17_vlan_config ...done
S17c init done
MAC2 addr:0:3:7f:ba:db:2
eth0, eth1
Hit any key to stop autoboot: 0
MMC Device 0 not found
MMC Device 0 not found
Creating 1 MTD partitions on "nand0":
0x0000048a0000-0x0000078a0000 : "mtd=0"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=0"
UBI: MTD device size: 48 MiB
UBI: number of good PEBs: 384
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 377
UBI: total number of reserved PEBs: 7
UBI: number of PEBs reserved for bad PEB handling: 3
UBI: max/mean erase counter: 1/1
Volume kernel not found!
UBI: mtd1 is detached from ubi0
---------------------------------------------------------------
Available commands is this release of U-Boot are:
--------------------------------------------------------------
(IPQ) # help
? - alias for 'help'
base - print or set address offset
bootipq - bootipq from flash device
bootm - boot application image from memory
bootmbn - bootmbn from flash device
bootp - boot image via network using BOOTP/TFTP protocol
bootz - boot Linux zImage image from memory
chpart - change active partition
cmp - memory compare
cp - memory copy
crc32 - checksum calculation
dhcp - boot image via network using DHCP/TFTP protocol
dumpipq_data- dumpipq_data crashdump collection from memory
echo - echo args to console
env - environment handling commands
exit - exit script
false - do nothing, unsuccessfully
fdt - flattened device tree utility commands
go - start application at address 'addr'
help - print command description/usage
i2c - I2C sub-system
iminfo - print header information for application image
imxtract- extract a part of a multi-image
ipq_nand- Switch between SBL and Linux kernel page layout.
loop - infinite loop on address range
md - memory display
mii - MII utility commands
mm - memory modify (auto-incrementing address)
mmc - MMC sub system
mmcinfo - display MMC info
mphyrd - qca8511 packet processor PHY register display
mphyrw - qca8511 packet processor PHY register write (fill)
mprd - qca8511 packet processor register display
mprw - qca8511 packet processor register write (fill)
mtdparts- define flash/nand partitions
mtest - simple RAM read/write test
mw - memory write (fill)
nand - NAND sub-system
nboot - boot from NAND device
nm - memory modify (constant address)
pci - list and access PCI Configuration Space
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
sf - SPI flash sub-system
showvar - print local hushshell variables
smeminfo- print SMEM FLASH information
source - run script from memory
test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
tftpput - TFTP put command, for uploading files to a server
true - do nothing, successfully
ubi - ubi commands
usb - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version
(IPQ) #
-------------------------------------------------------------------
TFTP download is OK.
But the problem that .bin files (both original Asrock firmware and dd-wrt firmware)
failed to boot (load linux kernel) after TFTP download.
Below is small final part of serial output:
---------------------------------------------
...
Bytes transferred = 16646166 (fe0016 hex)
Automatic boot of image at addr 0x44000000 ...
Wrong Image Format for tftpboot command
ERROR: can't get kernel image!
(IPQ) # iminfo
## Checking Image at 44000000 ...
Unknown image format!
---------------------------------------------
NO (access to) KERNEL?
One more experiment was to download .img file instead of .bin file.
Unfortunately, I failed to find .img version of firmware for Asrock G10.
That is why for TEST PURPOSES .img file for Linksys EA8500 (as it has the same processor
but another structure, memory etc.) was downloaded via TFTP (BUT NOT FLASHED) to Asrock G10.
Image file for Linksys EA8500 contains kernel; it immediately starts to boot; and of course
finally halted due to the large number of errors.
Below is the part of output:
---------------------------------------------
(IPQ) # tftpboot
Using eth1 device
TFTP from server 10.101.0.5; our IP address is 10.101.0.3
Filename 'factory-to-ddwrt_EA8500.img'.
Load address: 0x44000000
Loading: #################################################################
..........
###
done
Bytes transferred = 35344639 (21b50ff hex)
Automatic boot of image at addr 0x44000000 ...
Image Name: Linux-3.18
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2097023 Bytes = 2 MiB
Load Address: 42208000
Entry Point: 42208000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
device nand0 <nand0>, # parts = 1
#: name size offset mask_flags
0: fs 0x03000000 0x048a0000 0
active partition: nand0,0 - (fs) 0x03000000 @ 0x048a0000
defaults:
mtdids : none
mtdparts: none
Using machid 0x1260 from environment
I have few questions.
May be somebody know where I can find .img firmware for Asrock G10 ?
Or the only solution is to build .img file for Asrock G10 from source files?
Or may be somebody know another solution(s).
it appears i may have just done the same thing. so, somebody please update the router database so it doesn't send you to firmware that bricks your g10.
did you guys figure out how to unbrick this thing? hebeda, the picture you posted is gone. can you shrink it and repost it? i'd like as much guidance as possible if i'm gonna mess with it.
For guys like me who are not into firmware and UBoot business, those strings:
# nand erase 0x1340000 0x3000000
# nand write 0x44000000 0x1340000 0x3000000
require you first issue 'smeminfo' command to the router, then look for this string:
11: rootfs 0x0000ffff 0x1340000 0x3000000
and then use last 2 hexadecimal digits as arguments to nand erase and nand write.
And in case of nand write first argument is output of 'tftpboot img2.bin' command which was:
Load address: 0x44000000
This all is important because in my case this line from smeminfo looked like this:
11: rootfs 0x0000ffff 0x48a0000 0x3000000
Thank you atrain. I've helped my friend with his dead router.
UART connector J6: from left to right are TXD GND RXD.
TXD should be connected to RXD of your 3.3V USB-to-TTL cable.
GND should be connected to GND of your 3.3V USB-to-TTL cable.
RXD should be connected to TXD of your 3.3V USB-to-TTL cable.
Only THREE wires should be connected.
Serial connection speed ONLY 115200, 8N1, no flow control.