you seems to need
kmod-usb-storage
and some other kernel package  that match your Fs on your usb key
I use ext4 on my key, so I installed : kmod-fs-ext4

please try to install the previous packages
then do "block info"

ok!

i have some errors on install need it package...

root@OpenWrt:~# opkg install kmod-usb-storage
Installing kmod-usb-storage (3.10.36-1) to root...
Downloading http://downloads.openwrt.org/snapshots/ … c85xx.ipk.
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-storage:
*      kernel (= 3.10.36-1-851349b88c44e84d3a3b7f6ebee6e63f) *         kernel (= 3.10.36-1-851349b88c44e84d3a3b7f6ebee6e63f) *
* opkg_install_cmd: Cannot install package kmod-usb-storage.

root@OpenWrt:~# opkg install kmod-fs-ext4
Installing kmod-fs-ext4 (3.10.36-1) to root...
Downloading http://downloads.openwrt.org/snapshots/ … c85xx.ipk.
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-fs-ext4:
*      kernel (= 3.10.36-1-851349b88c44e84d3a3b7f6ebee6e63f) *         kernel (= 3.10.36-1-851349b88c44e84d3a3b7f6ebee6e63f) *         kernel (= 3.10.36-1-851349b88c44e84d3a3b7f6ebee6e63f) *
* opkg_install_cmd: Cannot install package kmod-fs-ext4.

something is not ok with versions?

type "uname -a" to check your kernel on your routeur, guess it's version < 3.10.36...

unless you have the kernel packages that was build on 24.04.2014, you have to wait for other trunk version more stable and install packages needed at same time

really...if you download opnwrt image, donwload also all the packages at same time to avoid such issue

If you want, I  could upload you my download  firmware + needed packages from 12/02/2014 somewhere...

Brice

ok.
root@OpenWrt:~# uname -a
Linux OpenWrt 3.10.36 #1 Fri Apr 25 11:54:34 UTC 2014 ppc GNU/Linux

if you cand upload somewhere your working combination (firmware+packages needed) woud be nice.
if is needed my email is: gtdaniel@gmail.com
from now i have learn the rule: firmware+packages from same date always toghether!

i am wondering if you try actual date firmware and if is working...

thanks in advance!

if you know & be sure to unbrick if necessary, you can try with the latest one... me no, the build I use is fine..

anyway, I will upload in a couple of hours, need to go to park with children and wife.

B

ok!

take your time and have a nice day!

Development snapshots aren't built with a web interface (as far as I know), so your router is working as intended. You can telnet or SSH to it (when you set a password, telnet access will be disabled), configure internet access, then see LuCI essentials for installation and startup of LuCI. It also suggests a way to install it offline, if you are unable to get internet access on it without a web interface.

I prefer building my own images so I don't have to reinstall LuCI (and everything else I need anyway) everytime I reset. If you look around the forum there are many people who post their custom built trunk images, most of them include LuCI.

(Last edited by makro on 4 May 2014, 17:13)

https://forum.openwrt.org/viewtopic.php … 63#p227163

That link should help.  if the interface is up and dhcp working then you should be able to telnet/ssh in and get uhttpd going. Telnet if no ssh set-up, set password and that disables telnet and gets ssh daemon going.  Search wiki if detail needed.

gtdaniel:

for firmware:
https://dl.dropboxusercontent.com/u/834 … rmware.zip

all packages kernel module :
https://dl.dropboxusercontent.com/u/834 … el-pkg.zip

the 2 userland Tools I think you need
https://dl.dropboxusercontent.com/u/834 … nd-pkg.zip
if you need more due to dependency, let me know the names, as all packages take around 300 MB, would take time for upload
will try to do it later...

Brice

thanks for assistance and upload, Brice!
i will let you know about results!

Daniel

Brice, now everything is fine!

[    3.782831] usbcore: registered new interface driver usbfs
[    3.788503] usbcore: registered new interface driver hub
[    3.794009] usbcore: registered new device driver usb
[    4.176369] usb 1-1: new high-speed USB device number 2 using fsl-ehci
[    4.596676] usb 1-1.2: new high-speed USB device number 3 using fsl-ehci
[    6.401954] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[    6.408359] scsi0 : usb-storage 1-1.2:1.0
[    6.412935] usbcore: registered new interface driver usb-storage
[    7.445078] sd 0:0:0:0: [sda] 31690752 512-byte logical blocks: (16.2 GB/15.1 GiB)
[    7.459414] sd 0:0:0:0: [sda] Write Protect is off
[    7.464253] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[    7.470968] sd 0:0:0:0: [sda] No Caching mode page found
[    7.476319] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    7.504317] sd 0:0:0:0: [sda] No Caching mode page found
[    7.509667] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    7.532988]  sda: sda1 sda2
[    7.553446] sd 0:0:0:0: [sda] No Caching mode page found
[    7.558791] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    7.564903] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    8.515600] Adding 158448k swap on /dev/sda2.  Priority:-1 extents:1 across:158448k

block info
/dev/mtdblock3: UUID="a2626fad-87abd0df-9f947195-ffe01b1b" VERSION="4.0" TYPE="squashfs"
/dev/mtdblock4: TYPE="jffs2"
/dev/sda1: UUID="58ff-eb68" LABEL="USB-1" VERSION="FAT32" TYPE="vfat"
/dev/sda2: UUID="9c9e63d0-fb4a-4423-91ea-3a6567c8e594" VERSION="2" TYPE="swap"

fdisk -l /dev/sda

Disk /dev/sda: 15.1 GiB, 16225665024 bytes, 31690752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc25db752

Device    Boot     Start       End   Blocks  Id System
/dev/sda1 *         2048  31373844 15685898+  c W95 FAT32 (LBA)
/dev/sda2       31373845  31690751   158453+ 82 Linux swap / Solaris

Thanks again!

Hi,

I see this topic is active, so using it for my problem.

I just bought this device today (v1.3 EU). I followed the instructions in the wiki for installing openwrt, uploading the factory.bin using the OEM web interface, but something seems to have gone wrong. The device won't boot, after the initial flash of all leds only the switch led lights up, the system led never goes back on.

I've tried resetting using the tftp server method, and the device does connect and download the firmware, but it never reboots. After waiting 15 minutes and cycling the power button, the symptoms stay the same.

I've tried the image on the wiki page, the snapshot openwork sysupgrade image, and also the image from http://www.tp-link.com/en/support/downl … version=V1 after cutting off the header with dd as per this thread.

Fot tftp server I've tried the stock OS X one, it complains at the end of transfer:

tftpd[65304]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
tftpd[65304]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
tftpd[65304]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
tftpd[65304]: dnssd_clientstub ConnectToServer: connect() failed Socket:4 Err:-1 Errno:2 No such file or directory

and also the one called

tftp-hpa

. It doesn't say any error, but doesn't say much else either.

Now I'm stuck, so I wonder if someone can help me figure out what the next steps would be. I'm horrible at soldering, I'm far more likely to mess that up than not, so I really would like to avoid that as far as possible.

I just flashed mine too with self-built r40694, wouldn't boot either. I recovered just fine with the TP-Link 130424 firmware, cutting off the bootloader first. I used Tftpd32 on Windows 8.1 64-bit, tried the 64-bit variant first which flat out didn't work. I had Wireshark running and the WDR4900 repeatedly sent the request for wdr4900v1_tp_recovery.bin, but Tftpd64 didn't respond at all. Tftpd32 responded instantly, and it all went flawless. Don't know if it's just picky about what server it is.

Edit: Did you rename the file to wdr4900v1_tp_recovery.bin, and is it located where the TFTP server will find it? Since it errors with "No such file...".

(Last edited by makro on 4 May 2014, 19:13)

thanks gtdaniel

here is *ALL* packages corresponding to the firmware I uploaded (OpenWrt Barrier Breaker r39574 / LuCI Trunk (svn-r9953)
https://dl.dropboxusercontent.com/u/834 … ckages.zip

keep it mind that some Security hole may exist with theses packages, like openssl
guess most userland packages Can be updated with the one from trunk without too much issue... especially if you open some services to internet.

Brice

Thanks for the help makro. Unfortunately I don't have any Windows machine available... I should try on linux though (another openwrt machine). Yeah the file is named correctly and in the right dir. It is sent to the router according to tcpdump. I was wondering though if there's some EOF marker or some such missing in my server since it seems like the router doesn't react to it.

(Last edited by Jhime on 4 May 2014, 19:57)

hi Jhime

you may install virtualbox & use a linux vm do do tftp stuff if you are not sure of your tftp Under macosx
also have you checked if the md5sdum off TP-Link 130424 firmware cutoff is the same as the one you saw in  this post
( 55c925df26e9408aa6357c39d89b45d6 if I noticed it correctly) ?

Brice

Just to confirm, that hash is correct (I just checked my own .bin that I used successfully.)

MD5: 55C925DF26E9408AA6357C39D89B45D6
SHA-1: B328D9590C8ABF339D48257716D7CEFF3736966A
SHA-256: 1EFFE1D8F28A581623E28200472AFDF32B9C872D9B43213F62C25CEC2C0AF5F7

Thanks guys. Yeah, I have the right checksum. I actually had a linux vm installed, so trying using it. Still no reboot... this time I noticed the linux box sent an ARP request right after the transfer, and the router didn't reply... so I guess it does do something. I'll give it a few more minutes but not too high hopes.

21:28:25.397790 IP 192.168.0.66.49476 > 192.168.0.86.1514: UDP, length 1472
21:28:25.397916 IP 192.168.0.86.1514 > 192.168.0.66.49476: UDP, length 4
21:28:25.398050 IP 192.168.0.66.49476 > 192.168.0.86.1514: UDP, length 704
21:28:25.398179 IP 192.168.0.86.1514 > 192.168.0.66.49476: UDP, length 4
21:28:26.775658 ARP, Request who-has 192.168.0.86 tell 192.168.0.66, length 46
21:28:27.776481 ARP, Request who-has 192.168.0.86 tell 192.168.0.66, length 46
21:28:28.778270 ARP, Request who-has 192.168.0.86 tell 192.168.0.66, length 46

Still no luck... I guess it's time to get this thing opened... I'll probably try something like this guy: https://forum.openwrt.org/viewtopic.php?id=50385

jhime
have you tried to ping 192.168.0.1 after fallback to tplink original firmware ?
also,your wan link is connected to something?
did you get confirmation by  the tftp server log that your device downloaded completly the firmware?

if no way, good luck for serial recovery.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 BARRIER BREAKER (Bleeding Edge, r39430)
 -----------------------------------------------------
  * 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
 -----------------------------------------------------
xxx@xxxxx:~# uptime
 12:14:00 up 74 days, 20:10,  load average: 0.10, 0.45, 1.63

Happy with the stability!

Hello again... I managed to make a read only serial console, but my typing is not registered... I guess my electronics skill is not up to the task... (here's the graph i used btw, except i didn't have any 4k7 resistors nor 1k so i used 2x10k(for 5k) and 1.6k instead: http://plischka.at/images/ARM-rs232-ttl.jpg)

Anyway, here's the output of a tftpd load (boot with reset button hold)

U-Boot 2010.12-svn19826 (Apr 24 2013 - 20:01:21)

CPU:   P1014, Version: 1.0, (0x80f10110)
Core:  E500, Version: 5.1, (0x80212151)
Clock Configuration:
       CPU0:800  MHz,
       CCB:400  MHz,
       DDR:333.333 MHz (666.667 MT/s data rate) (Asynchronous), IFC:100  MHz
L1:    D-cache 32 kB enabled
       I-cache 32 kB enabled
Board: P1014RDB
SPI:   ready
DRAM:  128 MiB
L2:    256 KB enabled
Using default environment

PCIe1: Root Complex of mini PCIe Slot, x1, regs @ 0xffe0a000
  01:00.0     - 168c:abcd - Network controller
PCIe1: Bus 00 - 01
PCIe2: Root Complex of PCIe Slot, x1, regs @ 0xffe09000
  03:00.0     - 168c:0033 - Network controller
PCIe2: Bus 02 - 03
In:    serial
Out:   serial
Err:   serial
Net:   initialization for Atheros AR8327/AR8328
eTSEC1
auto update firmware: is_auto_upload_firmware = 1!
SF: Detected S25FL128S_64K with page size 256, total 16 MiB
16384 KiB S25FL128S_64K at 0:0 is now current device
SPI flash read successful
Check for phy link status
Speed: 1000, full duplex
Using eTSEC1 device
TFTP from server 192.168.0.66; our IP address is 192.168.0.86
Filename 'wdr4900v1_tp_recovery.bin'.
Load address: 0x1000000
Loading: T #################################################################
     #################################################################
...
     #################################################################
     #######################################################
done
Bytes transferred = 16252928 (f80000 hex)
auto update firmware: product id verify fail!
Autobooting in 1 seconds
SF: Detected S25FL128S_64K with page size 256, total 16 MiB
16384 KiB S25FL128S_64K at 0:0 is now current device
SPI flash read successful
SPI flash read successful
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=> 

I guess this part is preventing the flashing:

auto update firmware: product id verify fail!

(Last edited by Jhime on 5 May 2014, 18:11)

What image do you put in tftpd folder?
In my case works with this: ftp://everbest.ftpserver.biz/Share/TP-L … )_beta.bin
Or maybe firewall block the transfer...
BTW, recent images on downloads on /snapshots/trunk/mpc85xx/ from 3,4,5 may are not bootable and brick again the device...

(Last edited by gtdaniel on 5 May 2014, 19:26)

I've tried various images, most lately the same one as mentioned above, which worked for some other people (same checksum)

Maybe related - maybe not: most of my self-built images (built on Gentoo x86_64) have stopped working a few days ago. Even the simplest ones refuse to do anything. Will attach a serial console in the near future to try and find out what the problem is.

Does anyone have an idea whether jffs2 images have ever worked on the WDR4900?