AsRock G10 DEAD / BRICKED - HELP NEEDED

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware
Goto page 1, 2, 3, 4  Next
Author Message
FireStorm@
DD-WRT Novice


Joined: 12 Mar 2018
Posts: 23

PostPosted: Wed Mar 21, 2018 9:40    Post subject: AsRock G10 DEAD / BRICKED - HELP NEEDED Reply with quote
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.

Any help / advice?
Sponsor
ian5142
DD-WRT Guru


Joined: 23 Oct 2013
Posts: 2135
Location: Canada

PostPosted: Wed Mar 21, 2018 18:07    Post subject: Serial Recovery Reply with quote
I would suggest ordering a USB-to-TTL 3.3V serial device such as this: https://www.adafruit.com/product/954

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.

See this for more info: https://www.dd-wrt.com/wiki/index.php/Serial_Recovery

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.

Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one, I am trying to update them.

Atheros:
Netgear R7800 - gateway, DHCP, QoS, VPN
TP-Link Archer C7 v2 x2 - WDS AP, WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - WDS Station
D-Link 615 C1 x 4 - not used
D-Link 615 E3 x 2 - not used
D-Link 825 B1 - WDS Station
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - WDS Station
UBNT loco M2 x2 - airOS

Broadcom
Asus N66U - backup Gateway
Netgear r6300 v1 - AP
Linksys E2500 - not used
Linksys EA2700 - not used
Linksys 160N v3 x2 - not used
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - not used
FireStorm@
DD-WRT Novice


Joined: 12 Mar 2018
Posts: 23

PostPosted: Wed Mar 21, 2018 18:32    Post subject: Reply with quote
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)
ian5142
DD-WRT Guru


Joined: 23 Oct 2013
Posts: 2135
Location: Canada

PostPosted: Wed Mar 21, 2018 19:15    Post subject: Bricked Reply with quote
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.

Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one, I am trying to update them.

Atheros:
Netgear R7800 - gateway, DHCP, QoS, VPN
TP-Link Archer C7 v2 x2 - WDS AP, WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - WDS Station
D-Link 615 C1 x 4 - not used
D-Link 615 E3 x 2 - not used
D-Link 825 B1 - WDS Station
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - WDS Station
UBNT loco M2 x2 - airOS

Broadcom
Asus N66U - backup Gateway
Netgear r6300 v1 - AP
Linksys E2500 - not used
Linksys EA2700 - not used
Linksys 160N v3 x2 - not used
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - not used
hebeda
DD-WRT User


Joined: 18 Sep 2006
Posts: 412
Location: Leipzig, Germany

PostPosted: Fri Nov 09, 2018 13:01    Post subject: Reply with quote
i made the same experience, innitial flash with r37582 worked almost flawless (exept some wierd WDS AP disconnects) ...

downgrade to r37442 gave me this result: device is totally dead ...

i will solder some pins to the serial connector and see if i can revive the device. is this actually the serial connector as show on the picture?

i will post some photos soon how to open the case, its a bit tricky at first ....


Last edited by hebeda on Fri Nov 09, 2018 14:45; edited 1 time in total
ian5142
DD-WRT Guru


Joined: 23 Oct 2013
Posts: 2135
Location: Canada

PostPosted: Fri Nov 09, 2018 13:16    Post subject: Serial Reply with quote
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.

Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one, I am trying to update them.

Atheros:
Netgear R7800 - gateway, DHCP, QoS, VPN
TP-Link Archer C7 v2 x2 - WDS AP, WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - WDS Station
D-Link 615 C1 x 4 - not used
D-Link 615 E3 x 2 - not used
D-Link 825 B1 - WDS Station
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - WDS Station
UBNT loco M2 x2 - airOS

Broadcom
Asus N66U - backup Gateway
Netgear r6300 v1 - AP
Linksys E2500 - not used
Linksys EA2700 - not used
Linksys 160N v3 x2 - not used
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - not used
valut
DD-WRT Novice


Joined: 06 Dec 2018
Posts: 8

PostPosted: Thu Dec 06, 2018 16:24    Post subject: Dead Asrock G10 experiments Reply with quote
Have the same problem. "Dead" Asrock G10 after some experiments. Router worked OK with original firmware and dd-wrt firmware.


Serial connection is OK (serial connection speed ONLY 115200, 8N1).
Output is:

--------------------------------------------------------------------
U-Boot 2012.07 [Standard IPQ806X.LN,r40331] (Jun 22 2015 - 19:44:46)

smem ram ptable found: ver: 0 len: 5
DRAM: 491 MiB
NAND: SF: Unsupported manufacturer 00
ipq_spi: SPI Flash not found (bus/cs/speed/mode) = (0/0/48000000/0)
128 MiB
MMC:
NAND read from offset 1180000 failed -74
*** Warning - readenv() failed, using default environment

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

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.18.48 (root@seg-desktop) (gcc version 6.1.0 (LEDE GCC 6.1.0 r1009) ) #124 SMP PREEMPT Sat Feb 18 08:47:50 CET 2017
[ 0.000000] CPU: ARMv7 Processor [512f04d0] revision 0 (ARMv7), cr=10c5787d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] Machine model: Linksys EA8500 WiFi Router
[ 0.000000] Ignoring memory range 0x41500000 - 0x42000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] PERCPU: Embedded 9 pages/cpu @ddfd3000 s7552 r8192 d21120 u36864
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pag es: 121920
[ 0.000000] Kernel command line: console=ttyMSM0,115200n8 rootfstype=squashfs noinitrd console=ttyHSL1,115200n8 ubi.mtd=rootfs root=mtd:ubi_rootfs rootfstype =squashfs
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 481228K/491520K available (3854K kernel code, 279K rwdata , 1104K rodata, 184K init, 403K bss, 10292K reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xde800000 - 0xff000000 ( 520 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xde000000 ( 480 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0208000 - 0xc06dfe1c (4960 kB)
[ 0.000000] .init : 0xc06e0000 - 0xc070e000 ( 184 kB)
[ 0.000000] .data : 0xc070e000 - 0xc0753e44 ( 280 kB)
[ 0.000000] .bss : 0xc0753e44 - 0xc07b8b84 ( 404 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000011] sched_clock: 32 bits at 6MHz, resolution 160ns, wraps every 68719 4767200ns
[ 0.000026] Switching to timer-based delay loop, resolution 160ns
[ 0.000430] Calibrating delay loop (skipped), value calculated using timer fr equency.. 12.50 BogoMIPS (lpj=62500)
[ 0.000456] pid_max: default: 32768 minimum: 301
[ 0.000695] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000712] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.001352] CPU: Testing write buffer coherency: ok
[ 0.001615] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.002120] Setting up static identity map for 0x42213180 - 0x422131d8
[ 0.063436] CPU1: Booted secondary processor
[ 0.063564] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.063681] Brought up 2 CPUs
[ 0.063703] SMP: Total of 2 processors activated (25.00 BogoMIPS).
[ 0.063714] CPU: All CPU(s) started in SVC mode.
[ 0.078331] VFP support v0.3: implementor 51 architecture 0 part 4d variant 2 rev 0
[ 0.078867] pinctrl core: initialized pinctrl subsystem
[ 0.089113] NET: Registered protocol family 16
[ 0.089433] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.113851] cpuidle: using governor ladder
[ 0.144866] cpuidle: using governor menu
[ 0.163811] qcom_rpm 108000.rpm: RPM firmware 3.0.16777342
[ 0.163894] qcom_rpm 108000.rpm: failed to mark ack irq as wakeup
[ 0.163954] qcom_rpm 108000.rpm: failed to mark wakeup irq as wakeup
[ 0.199459] pps_core: LinuxPPS API ver. 1 registered
[ 0.199473] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giome tti <giometti@linux.it>
[ 0.199514] PTP clock support registered
[ 0.200644] pcie_init: pcie_init: unable to create IPC log context for pcie0- short
[ 0.200660] pcie_init: pcie_init: unable to create IPC log context for pcie0- long
[ 0.200671] pcie_init: pcie_init: unable to create IPC log context for pcie1- short
[ 0.200681] pcie_init: pcie_init: unable to create IPC log context for pcie1- long
[ 0.201085] Switched to clocksource dg_timer
[ 0.202480] NET: Registered protocol family 2
[ 0.203180] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.203217] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.203270] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.203315] TCP: reno registered
[ 0.203334] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.203354] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.203587] NET: Registered protocol family 1
[ 0.204775] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.204869] Crashlog allocated RAM at address 0x5ff00000
[ 0.205739] squashfs: version 3.0 (2006/03/15) Phillip Lougher
...
[ 0.418719] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.419698] msm_serial 16340000.serial: msm_serial: detected port #0
[ 0.419795] msm_serial 16340000.serial: uartclk = 1843200
[ 0.419852] 16340000.serial: ttyMSM0 at MMIO 0x16340000 (irq = 184, base_baud = 115200) is a MSM
[ 0.419908] msm_serial: console setup on port #0
[ 1.132631] console [ttyMSM0] enabled
[ 1.137423] msm_serial: driver initialized
[ 1.144204] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xa1
[ 1.144702] nand: Micron MT29F1G08ABBEAH4
[ 1.151208] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[ 1.155199] Scanning device for bad blocks
[ 1.600760] random: nonblocking pool is initialized
[ 1.924052] 19 ofpart partitions found on MTD device qcom-nandc
[ 1.924081] Creating 19 MTD partitions on "qcom-nandc":
[ 1.928778] 0x000000000000-0x000000040000 : "SBL1"
[ 1.934952] 0x000000040000-0x000000180000 : "MIBIB"
[ 1.939628] 0x000000180000-0x0000002c0000 : "SBL2"
[ 1.944444] 0x0000002c0000-0x000000540000 : "SBL3"
[ 1.949212] 0x000000540000-0x000000660000 : "DDRCONFIG"
[ 1.954086] 0x000000660000-0x000000780000 : "SSD"
[ 1.959116] 0x000000780000-0x000000a00000 : "TZ"
[ 1.964076] 0x000000a00000-0x000000c80000 : "RPM"
[ 1.968700] 0x000000c80000-0x000000dc0000 : "art"
[ 1.973352] 0x000000dc0000-0x000000ec0000 : "APPSBL"
[ 1.977977] 0x000000ec0000-0x000000f00000 : "u_env"
[ 1.983089] 0x000000f00000-0x000000f40000 : "s_env"
[ 1.987631] 0x000000f40000-0x000000f80000 : "devinfo"
[ 1.992533] 0x000000f80000-0x000003780000 : "linux"
[ 1.997719] 0x000001280000-0x000003780000 : "rootfs"
[ 2.002480] mtd: partition "rootfs" set to be root filesystem
[ 2.006820] 0x000003780000-0x000005f40000 : "linux2"
[ 2.013331] 0x000003a80000-0x000005f40000 : "rootfs2"
[ 2.018303] 0x000005f40000-0x000005f80000 : "nvram"
[ 2.023271] 0x000005f80000-0x000008000000 : "ddwrt"
[ 2.029168] IMQ: autocreate imq0 NS c074e100
[ 2.032606] IMQ: autocreate imq1 NS c074e100
[ 2.036506] IMQ driver loaded successfully. (numdevs = 16, numqueues = 1)
....
[ 3.618128] CPU1: stopping
[ 3.626805] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.18.48 #124
[ 3.629313] Backtrace:
[ 3.637840] [<c021c484>] (dump_backtrace) from [<c021c684>] (show_stack+0x18/ 0x20)
[ 3.637999] r7:00000080 r6:00000000 r5:20000193 r4:c0727308
[ 3.650852] [<c021c66c>] (show_stack) from [<c0384bd4>] (dump_stack+0x90/0xa4 )
[ 3.651210] [<c0384b44>] (dump_stack) from [<c021e8fc>] (handle_IPI+0xe8/0x16 4)
[ 3.658310] r7:de802000 r6:00000000 r5:00000001 r4:c070ba48
[ 3.670987] [<c021e814>] (handle_IPI) from [<c0208628>] (gic_handle_irq+0x64/ 0x70)
[ 3.671330] r7:de802000 r6:dd461f50 r5:c0717cc8 r4:de80200c
[ 3.684179] [<c02085c4>] (gic_handle_irq) from [<c02096c0>] (__irq_svc+0x40/0 x74)
[ 3.684529] Exception stack(0xdd461f50 to 0xdd461f98)
[ 3.691994] 1f40: ffffffed 00000000 00000 000 c020a240
[ 3.697037] 1f60: dd460000 c07178ec c064ec88 00000000 00000000 00000000 fffff fed dd461fa4
[ 3.705194] 1f80: dd461fa8 dd461f98 c0219cc8 c0219ccc 60000013 ffffffff
[ 3.713343] r7:dd461f84 r6:ffffffff r5:60000013 r4:c0219ccc
[ 3.725247] [<c0219c90>] (arch_cpu_idle) from [<c02581c0>] (cpu_startup_entry +0x124/0x250)
[ 3.725605] [<c025809c>] (cpu_startup_entry) from [<c021e598>] (secondary_sta rt_kernel+0x168/0x174)
[ 3.733746] r7:c0754204
[ 3.745118] [<c021e430>] (secondary_start_kernel) from [<422086c4>] (0x422086 c4)
[ 3.745377] r7:c0754204 r6:10c0387d r5:00000015 r4:5f44806a
[ 3.758661] Rebooting in 5 seconds..Reboot failed -- System halted
----------------------------------------------------------



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).

Sorry for long message and thank you in advance.
bumperbozo
DD-WRT Novice


Joined: 05 Aug 2018
Posts: 29

PostPosted: Mon Dec 10, 2018 23:18    Post subject: Reply with quote
you could donate it to a dev so they can try tweaking dd-wrt for the g10
bumperbozo
DD-WRT Novice


Joined: 05 Aug 2018
Posts: 29

PostPosted: Mon Dec 10, 2018 23:51    Post subject: Reply with quote
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.
bumperbozo
DD-WRT Novice


Joined: 05 Aug 2018
Posts: 29

PostPosted: Sat Dec 15, 2018 18:07    Post subject: Reply with quote
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.
atrain
DD-WRT Novice


Joined: 29 Feb 2008
Posts: 5

PostPosted: Wed Dec 19, 2018 22:30    Post subject: Reply with quote
Just helped a friend with this!


So, the .bin images seem to be UBI formatted, but with an offset:

Code:

DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             CSYS header, little endian, size: 0
20            0x14            UBI erase count header, version: 1, EC: 0x0, VID header offset: 0x800, data offset: 0x1000


Simply shift the image by 20 bytes, and you should be able to load it:
Code:

dd if=../img.bin of=../img2.bin skip=20 bs=1


Finally:
Code:

(IPQ) # smeminfo
smem: SMEM_PARTITION_TABLE_OFFSET failed
flash_type:             0x2
flash_index:            0x0
flash_chip_select:      0x0
flash_block_size:       0x20000
partition table offset 0x0
No.: Name             Attributes            Start             Size
  0: 0:SBL1           0x0000ffff              0x0          0x40000
  1: 0:MIBIB          0x0000ffff          0x40000         0x140000
  2: 0:SBL2           0x0000ffff         0x180000         0x140000
  3: 0:SBL3           0x0000ffff         0x2c0000         0x280000
  4: 0:DDRCONFIG      0x0000ffff         0x540000         0x120000
  5: 0:SSD            0x0000ffff         0x660000         0x120000
  6: 0:TZ             0x0000ffff         0x780000         0x280000
  7: 0:RPM            0x0000ffff         0xa00000         0x280000
  8: 0:APPSBL         0x0000ffff         0xc80000         0x500000
  9: 0:APPSBLENV      0x0000ffff        0x1180000          0x80000
 10: 0:ART            0x0000ffff        0x1200000         0x140000
 11: rootfs           0x0000ffff        0x1340000        0x3000000
 12: 0:BOOTCONFIG     0x0000ffff        0x4340000          0x60000
 13: 0:APPSBL_1       0x0000ffff        0x43a0000         0x500000
 14: rootfs_1         0x0000ffff        0x48a0000        0x3000000
 15: hwconfig         0x0000ffff        0x78a0000          0x40000
 16: nvram            0x0000ffff        0x78e0000          0x40000


(IPQ) # tftpboot img2.bin
Mac1 unit failed
Using eth1 device
TFTP from server 100.100.100.1; our IP address is 100.100.100.2
Filename 'img2.bin'.
Load address: 0x44000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #############################
done
Bytes transferred = 16646146 (fe0002 hex)
(IPQ) # nand erase 0x1340000 0x3000000

NAND erase: device 0 offset 0x1340000, size 0x3000000
Erasing at 0x4320000 -- 100% complete.
OK
(IPQ) # nand write 0x44000000 0x1340000 0x3000000

NAND write: device 0 offset 0x1340000, size 0x3000000
 50331648 bytes written: OK
(IPQ) # reset
resetting ...
valut
DD-WRT Novice


Joined: 06 Dec 2018
Posts: 8

PostPosted: Sun Dec 23, 2018 8:55    Post subject: Reply with quote
Thank you for important information concerning firmware image structure. Now my Asrock G10 is working (with the latest DD-WRT 12-20-2018-r38060).

Best Seasons' Greetings!
UncleFword
DD-WRT Novice


Joined: 23 Dec 2018
Posts: 1

PostPosted: Sun Dec 23, 2018 12:38    Post subject: clarification Reply with quote
atrain wrote:
Just helped a friend with this!

Code:

(IPQ) # nand erase 0x1340000 0x3000000

NAND erase: device 0 offset 0x1340000, size 0x3000000
Erasing at 0x4320000 -- 100% complete.
OK
(IPQ) # nand write 0x44000000 0x1340000 0x3000000

NAND write: device 0 offset 0x1340000, size 0x3000000
 50331648 bytes written: OK
(IPQ) # reset
resetting ...


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.
HOYANE
DD-WRT Novice


Joined: 27 Dec 2018
Posts: 3

PostPosted: Thu Dec 27, 2018 11:34    Post subject: Asrock G10 Serial connect Reply with quote
I opened my G10 router and This is my G10 board. but i have no idea where i supposed to connect.

Plz let me know where should i connect serial TX , RX , GND .


Last edited by HOYANE on Tue Jan 01, 2019 9:45; edited 1 time in total
valut
DD-WRT Novice


Joined: 06 Dec 2018
Posts: 8

PostPosted: Thu Dec 27, 2018 15:44    Post subject: Reply with quote
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.
Goto page 1, 2, 3, 4  Next Display posts from previous:    Page 1 of 4
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum