Did you try make a reset?
Keep reset button 10sec

Yes tried that but it still doesn't work

Nobody can help me?

Unfortunatelly I can't I have also problem with my box and no one want help me:(

@shadow3264
Which firmware you have on your box now ? Did you try to flash the "opened" image 3.17 ?

@wafuli
Sorry, I don't know what to do and my box is 904 xDSL.

@stefan-koch
I will try a serial connect, my serial-usb adaptor which worked with a tp-link 710n should do it ?
When the connection is established, is it possible to cofigure LAN and/or WIFI from there ?
Do you have a detailed description how to flash openwrt with the modified bootloader ?

Did someone know how to open the f****** case without destroying it ?
--------
OK I did it there is another clamp under the slots on each side
Now I need to find the connector, I can see one only, it's J8, that's right ?

(Last edited by erz on 25 Aug 2015, 15:13)

I think this is the connection. OK ?

Right ??

full view

------------------------------------------------------------------------------------------------------------------------------------

The connection was right, but after changing something in /etc/config/network it stucks at

ROM VER: 1.1.4
CFG 06
NAND
NAND Read OK

ROM VER: 1.1.4
CFG 06
NAND
NAND Read OK
nand_read_page - 00000008
DDR autotuning Rev 0.3c
DDR size from 0xa0000000 - 0xa7ffffff
DDR check ok... start booting...

U-Boot 2010.06-Lv2.0.40-A0.5 (Nov 22 2012 - 15:40:12)

CLOCK CPU 500M RAM 250M
DRAM:  128 MiB
NAND:  NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
512 MiB
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
nand_read_bbt: Bad block at 0x00000f5e0000
nand_read_bbt: Bad block at 0x00001ade0000
nand_read_bbt: Bad block at 0x00001f2e0000
In:    serial
Out:   serial
Err:   serial
Net:   Internal phy(GE) firmware version: 0x040b
vr9 Switch

Type "run flash_nfs" to mount root filesystem over NFS

Hit any key to stop autoboot:  0
Uncompressing LCD bootup images ...............
NAND read: device 0 offset 0x0000000004700000, size 0x0000000000300000
0x300000 bytes read: OK
1. bootid : 2, bootnum : 12
Uncompressing LCD bootup images ...............
NAND read: device 0 offset 0x0000000004700000, size 0x0000000000300000
0x300000 bytes read: OK

please input password :

while booting

(Last edited by erz on 25 Aug 2015, 18:15)

I tried every Firmware i could find on the Internet, it fails every time

(Last edited by shadow3264 on 26 Aug 2015, 13:56)

@shadow3264
Which firmware is actually on your box ? Firmware and bootloader are stock version ?

I found a few .dts files in the git openwrt folder but I don't know the one for EB904xDSL, there are a few, EASY*********.dts,
but none of them is named like EASY904****.dts

F*** !

I flashed again and have access to the openwrt serial console, but how to mount
the usb disk to copy the modified bootloader in openwrt ?

It has to be an ext4 partition, or is ntfs or fat32 OK ?

(Last edited by erz on 27 Aug 2015, 19:44)

Firmware was the newest one available. Bootloader is stock

Cześć,
Widzę, że walczysz z tym samym problemem co ja.
Czy udało Ci się uruchomić kartę z Play w Easybox 904 LTE?

I'm sorry that I write in Polish, but I know English poorly.

@erz

the usb stick will automatically mount (use FAT) to /tmp/usb/a1

The detailed description is here:
https://forum.openwrt.org/viewtopic.php?pid=284534

See bootloader section.

I have not opened the case. I drilled a hole into it.

The network connection will only work because u-boot sets the correct settings (I think for the PHYs). That has nothing to do with wifi.
Just load your openwrt kernel via tftp then the network is enabled correctly.

But anyway the dts file for openwrt must changed for correct network settings, etc.

Thank you for your answer but there is a problem with openwrt, I changed nothing, only tried to
boot a few times to see the output and cat a few files, but now the booting progress stucks
again with bad block errors. I will try one more time and copy the modified bootloader after the
first boot before the system destroy itself

----------------------------------------------------------------------------------------------------------------------------

ROM VER: 1.1.4
CFG 06
NAND
NAND Read OK
nand_read_page - 00000008
DDR autotuning Rev 0.3c
DDR size from 0xa0000000 - 0xa7ffffff
DDR check ok... start booting...

U-Boot 2010.06-Lv2.0.40-A0.5 (Nov 22 2012 - 15:40:12)

CLOCK CPU 500M RAM 250M
DRAM:  128 MiB
NAND:  NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,                                                                                        3V 8-bit)
512 MiB
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
nand_read_bbt: Bad block at 0x00000f5e0000
nand_read_bbt: Bad block at 0x00001ade0000
nand_read_bbt: Bad block at 0x00001f2e0000
In:    serial
Out:   serial
Err:   serial
Net:   Internal phy(GE) firmware version: 0x040b
vr9 Switch

Type "run flash_nfs" to mount root filesystem over NFS

Hit any key to stop autoboot:  0
Uncompressing LCD bootup images ...............
NAND read: device 0 offset 0x0000000004700000, size 0x0000000000300000
0x300000 bytes read: OK
1. bootid : 2, bootnum : 12
Uncompressing LCD bootup images ...............
NAND read: device 0 offset 0x0000000004700000, size 0x0000000000300000
0x300000 bytes read: OK

please input password :

openwrt does NOT mount my FAT formatet usb memory to /tmp/usb/a1, it does nothing, dmesg output is only

[   30.716000] usb 1-1: new high-speed USB device number 2 using dwc2

How to mount (or find) the usb memory in openwrt to copy the modified bootloader ?

Do I have to copy the bootloader file from the opened image/ssh, not from openwrt/serial ???
This could be my misunderstanding.

--------------------------------------------------------------------

I think that's it In your description the optional bootloader section is under the part how to
flash openwrt so I thougt it has to be changed from openwrt and not before. But I was wrong.

Am I right ?

-------------------------------------------------------------------

OK, now I have bootloader access without password but don't know how to flash the two files
from there. Or is it enough to do it with ssh like before ?

--------------------------------------------------------------------

I read your post again and found
"Just load your openwrt kernel via tftp then the network is enabled correctly."

Perhaps you can specify this a little bit more for a noob like me I'm afraid to brick it or is it save to
trial and error ? I don't know nothing about u-boot and it's commands

How to load and flash openwrt-lantiq-xrx200-VGV952CJW33-uImage with u-boot ?

(Last edited by erz on 30 Aug 2015, 11:35)

Just as a small beacon of hope for the people with bricked devices, I unbricked a 904 xdsl that couldn't be rescued with the reset-rescue method.

Essentially, I flashed the passwordless u-boot and flashed the kernel and rootfs from there via tftp. I'll add the information to the wiki page once I can repeat it.

Still can't flash any firmware

Is the dts config file still in work - aka no network access after reboot? Or does the tftp patch process write to nand and I can fully use openwrt after a reboot without loading the kernel via ftp on each boot?

@ganzi
Niestety nie odezwij się na maila thioby@gmail.com

@snuffi, can you give us link to wiki page?

@snuffi (or others)
please give us a short description of the commands you used to flash the kernel via the u-boot loader or even edit the openwrt wiki.
We don't want to push you but a few guys here have big problems because their devices are bricked or they can't use the network in openwrt.
It would be very kind to help us

Can somebody give me a hint?
I did, what in Post 132 was told:
I have current firmware Version AT904L-3.05

I Configured my computer with IP: 192.168.2.2 , MASK: 255.255.255.0 , GW: 192.168.2.1 , DNS: 192.168.2.1
Accessed to 192.168.2.1 and set one password
Accessed to 192.168.2.1 > Status & Support > Diagnostic Utility > Ping Test > "192.168.2.2 & telnetd" > Ping
Opened terminal and made a new telnet connection to host 192.168.2.1 and port 23
Login with user "root" and my setted "password"
Edited the file
    a. "vi /tmp/etc/config/dropbear"
    b. change "option PasswordAuth 'off'" to "option PasswordAuth 'on'"
    c. save and exit vi

I have telnet access, but with ssh i still get "Connection refused"

Edit:
I managed to get ssh access, i forgot the:
ccfg_cli commitcfg

(Last edited by icho40 on 15 Sep 2015, 14:25)

Good morning,

I also did not have any luck getting fullimage-3.17-opened.img on my xDSL box: After rebooting, LCD messaged "Die ausgewählte Datei ist keine gültige Firmware" ....

I managed to
- start serial console in UART mode
- sent file u-boot.asc (904xdsl-uboot-maybe-no-passwd.zip)
- run update_uboot (904xdsl-uboot-maybe-no-passwd.zip > u-boot.lq)
u-boot accepts any password now

Then I renamed self compiled
- openwrt-lantiq-xrx200-VGV952CJW33-uImage to uImage
- openwrt-lantiq-xrx200-VGV952CJW33-squashfs-ubinized.bin to root.squash
(according to system variabels named in printenv)

and tried to write these to flash:

VR9 # run update_kernel
Using vr9 Switch device
TFTP from server 192.168.2.100; our IP address is 192.168.2.1
Filename 'uImage'.
Load address: 0x80800000
...
Bytes transferred = 1536892 (17737c hex)
NAND erase: device 0 offset 0x0000000003c40000, size 0x0000000000500000
....
OK
NAND write: device 0 offset 0x0000000003c40000, size 0x000000000017737c
Attempt to write non page aligned data
 0x17737c bytes written: ERROR

VR9 # run update_rootfs
Using vr9 Switch device
TFTP from server 192.168.2.100; our IP address is 192.168.2.1
Filename 'root.squash'.
Load address: 0x80800000
...
done
Bytes transferred = 2228224 (220000 hex)
NAND erase: device 0 offset 0x0000000000040000, size 0x0000000003c00000
....
OK
0x80800000 + 40 = 80800040
220000  -40 = 0021FFC0
NAND write: device 0 offset 0x0000000000040000, size 0x000000000021ffc0
Attempt to write non page aligned data
 0x21ffc0 bytes written: ERROR
0x80800040  -40 = 80800000

After rebooting, this is shown:

ROM VER: 1.1.4
CFG 06
NAND
NAND Read OK
ROM VER: 1.1.4
CFG 06
NAND
NAND Read OK
nand_read_page - 00000008
DDR autotuning Rev 0.3c
DDR size from 0xa0000000 - 0xa7ffffff
DDR check ok... start booting...
U-Boot 2010.06-Lv2.0.40-A0.5 (Feb 12 2015 - 23:05:42)
CLOCK CPU 500M RAM 250M
DRAM:  128 MiB
NAND:  NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,
3V 8-bit)
512 MiB
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
In:    serial
Out:   serial
Err:   serial
Net:   Internal phy(GE) firmware version: 0x040b
vr9 Switch
Type "run flash_nfs" to mount root filesystem over NFS
Hit any key to stop autoboot:  1 0 
1. bootid : 2, bootnum : 12
Uncompressing LCD bootup images ............... 
NAND read: device 0 offset 0x0000000004700000, size 0x0000000000300000
 0x300000 bytes read: OK
wrong image ID
please input password : 

Thanks for your help, Dirk

Can someone explain me how to flash the uboot with no password? I have a UART to USB adapter and I would like to flash the uBoot without password

In case your box is bricked:
- start serial console in UART mode (shortcut R184 while booting, see post 87 in this thread)
- sent file u-boot.asc via your serial-terminal-program (out of 904xdsl-uboot-maybe-no-passwd.zip)
- start TFTP-server and provide file u-boot.lq (also part of 904xdsl-uboot-maybe-no-passwd.zip)
- "run update_uboot" at serial console (this will start TFTP, NAND erase, NAND write, see printenv for details)

I did this with http://realterm.sourceforge.net/

OK, you described to flash the u-boot loader to a bricked box, but how to flash (or load) the kernel and rootfs image with u-boot ?

As outlined in my post #171, I had no luck flashing my self compiled kernel and rootfs to NAND...

Got myself a second box:
+ flashing fullimage-3.17-opened.img via rescue-mode worked well
- no luck writing kernel and  rootfs to nand (post #120, step 9 and 10)
One thought: My self-compiled openWRT files might be corrupt!?

Questions:
- can someone provide working openWRT kernel and rootfs?
- how do I backup NAND of my working 2nd box
- how do I restore NAND on my uboot-no-passwd-only 1st box?