Support for Easybox 904 LTE

RENErica · May 4, 2020, 8:53am

Sorry for the late reply

An outdated driver could be the cause of the performance of internet speed.
A search for vr9-B-dsl.bin or vr9-A-dsl.bin and the use of a newer could
solve the problem.

As far as I know there was never an official version for the EasyBox 904xDSL.
https://openwrt.org/toh/astoria/arcadyan_astoria_easybox_904xdsl_r01

The last version i found is Plonkbongs from dec 2019

Since March i am creating newer firmware images for my own use which
i want to share.

Just try changing the settings in customfeeds.conf which is also possible via luci.
One way is to load the packages onto the box and install them with opkg install.
All available packages can be found at mega and mediafire where I uploaded it.

s_2 · May 5, 2020, 5:50pm

I have been following this thread for a couple years now, still wondering why the title was never changed to "xDSL", for there is not really much more information available about the LTE variant by now than it was back then

So I grabbed my old LTE box and eventually managed to find the bootsel Pin that would allow to unbrick via UART: It is the resistor R151 (instead of R148 with the xDSL variant).

However it would not boot the modified 904xdsl-uboot-maybe-no-passwd:

ROM VER: 1.1.4
CFG 04
UART
**********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************

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
nand_read_bbt: Bad block at 0x0000002e0000
nand_read_bbt: Bad block at 0x00001e680000
In:    serial
Out:   serial
Err:   serial
Net:   bad image magic number
cannnot find gphy firmware!
Internal phy(GE) firmware version: 0xffff
vr9 Switch

Type "run flash_nfs" to mount root filesystem over NFS

Warrning : rtl8367rb reset failed!!!

Then I tried to modify a stock image according to https://github.com/majuss/easybox904/blob/master/guides/create.md, but it was not accepted via Web UI or TFTP (I wonder if I should at least fix the uImage header checksums etc.?). However the error printed to the console when using TFTP says nothing about the uImage checksum:

U-Boot 2010.06-Lv2.0.40-A0.3  (Jul 12 2012 - 22:00: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 0x0000002e0000
nand_read_bbt: Bad block at 0x00001e680000
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

reset button pressed --> 1
reset button pressed --> 2
reset button pressed --> 3
enter rescue process ...
Uncompressing LCD bootup images ...............
NAND read: device 0 offset 0x0000000004700000, size 0x0000000000300000
 0x300000 bytes read: OK
Using vr9 Switch device
TFTP from server 192.168.2.100; our IP address is 192.168.2.1
Filename 'fullimage.img'.
Load address: 0x80800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########################################################
done
Bytes transferred = 31383681 (1dee081 hex)
verify firmware validation: loadaddr = 0x80800000, filesize = 31383681
0x81af5040 magic number not found
Uncompressing LCD bootup images ...............
NAND read: device 0 offset 0x0000000004700000, size 0x0000000000300000
 0x300000 bytes read: OK

I could not find that magic number anywhere in the stock image either, but google just showed one result for it: https://forum.archive.openwrt.org/viewtopic.php?id=44676&p=13

That was my post from the old forum, and now I'm basically at the same point again after three years Apparently there are different firmware formats, since even the latest official one from the vodafone website is apparently no longer accepted via tftp.

So I wonder if anyone has a clue, or could help create a modified version (with dropbear enabled) of the LTE version image (could it really be just the uImage header checksums!?)

Looking forward to any advice

RENErica · May 6, 2020, 11:39am

If I understand it correctly you use the u-boot of the 904xDSL but has a 904LTE.

„However it would not boot the modified 904xdsl-uboot-maybe-no-passwd : „

I think the bootloader is probably now expecting an image of the 904xDSL.

904xdsl

In my memory the LTE version has no WAN interface. Even if the xDSL
image is on the box, only LAN and wifi can be used.

https://forum.openwrt.org/t/support-for-easybox-904-lte/14478/209

So that the stock image can be imported again, the LTE u-boot is
probably required.

T3mp0 · May 17, 2020, 11:39am

Hi guys,

So I decided to flash my 904xDSL after all. What steps should I take in order to flash it correctly? It has the latest Vodafone (DE) firmware.

Thanks in advance.

mindsolve · May 18, 2020, 1:42pm

Just a little FYI here: There is an upcoming firmware update (version 04.15) for the Easybox 904 xDSL.
First test-rollout between 26.05. and 10.06. (up to 19.000 customers), full rollout between 22nd and 26th June.

No real information on what is new just "Bug fixes and stabilitiy improvements".

T3mp0 · May 18, 2020, 9:27pm

That's nice but I'd try some stabe version before that one is released. So if someone could point me to the right place with flashing instruction (or write it here) I'd really appreciate that.

QAuge · July 8, 2020, 9:04pm

Hi, a short hello from me. I tried to port our device to the newest openwrt changes which moved to kernel 5.4. For these which have some interest on developing it further ( @Plonk34 ^^ <- I included some of your patches ), I just wanted to drop a quick info for you. This is my developing branch:
Easybox-904-XDSL 5.4

(
I build my image this way:

rm -rf bin build_dir/target-* staging_dir/target-* tmp ; \
cat config/eb904xDSL_minimal.in config/eb904xDSL_additional.in >.config && \
make defconfig && make -j8 2>&1 | tee build.log

)

And I have adapted the packages in my feeds ( lede-feeds-easybox904 ) to compile with new kernel.
(It may be needed to delete ralink_inic-1.0.0_mips.tar.bz2 in the dl folder.)

....and I hope I found a crude workaround for the sporadic reboots on startup.
VGV952CJW33-E-IR: Fix sporadic reboots on mtd access.

@arnysch / @kovz Maybe you have an idea whats going wrong here?

Update some hours later.... The box rebooted overnight. So it seams it's not the right workaround

Hopefully we can go with the transition to the DSA network device, but I don't know how we can handle the fixed links, which are connected to the realtek switch...This seems the next adventure to keep the device alive...

QAuge · July 22, 2020, 8:05pm

To reply myself: I think I found the reason cond_resched wasn't working correctly.
I tried to explain it here: https://github.com/Quallenauge/Easybox-904-XDSL/commit/ea069c7b6fef1e5b234ecedf095d5865a1173375
Maybe this affects not only our device but other lantic ones with multiple devices on the ebu bus.

Hopefully, I'm able the other cases also...

Ygreck · July 24, 2020, 6:51am

I can't continue after flashing fullimage.img.

I tried both fullimage-files from the common instructions and that from Zuzia's post.

After reading Stewori's post, I know that, although the LCD shows the same "this may take a few minutes", the device is not necessarily in a boot loop.

I tried it with a windows 10 pc in chrome and with a raspberry (my only devices with ethernet port)

someone an idea?

Jai_roberts · July 25, 2020, 8:14pm

Hi, sorry if this sounds really nooby, bought an easybox 904 not realising the APN was locked, I don't suppose someone could help me change the APN via telnet? I've found a few guides but all have had dead links to the image files that (I think) I need to gain access to the telnet, again sorry for my inexperience, any help is greatly appreciated

Jai_roberts · July 26, 2020, 12:07am

On top of what I said previously a friend who is supposedly very good with cracking devices managed to follow a guide for the dsl version not the LTE version and bricked the router, when it powers on it just displays a white screen, so if anyone can help me unbrick it that would also be much appreciated

michag86 · July 29, 2020, 8:27pm

I have a hard bricked 904 LTE. I can start into UART mode like described here: https://openwrt.org/toh/arcadyan/easybox_904_lte#debricking1

But when I try to start the ascii uboot, I always get this error:

Warrning : rtl8367rb reset failed!!!

I also tried this guide

https://github.com/majuss/easybox904/blob/master/guides/hardbrick.md

which ended up in the same error message.

Is there anywhere a method to unbrick a hard bricked 904 LTE?

s_2 · July 29, 2020, 10:26pm

There is currently no uboot for the LTE variant that could be loaded via uart (ascii), the one for the xDSL variant unfortunately does not work (trying to initialize the Realtek ethernet switch, which is not present on that device).

I'm also still waiting for someone to build an appropriate uboot for the LTE variant before I would dare to flash my device and further experiment with porting OpenWRT to this device, which - despite the title of a thread that has more than 250 replies - has not yet happened ...

QAuge · July 30, 2020, 9:46am

At least the sources are here located: https://github.com/uwehermann/easybox-904-lte-firmware/tree/master/package/infineon-utilities/feeds/ifx_feeds_uboot/open_uboot
It should be possible to build an selfbaked uboot which can be loaded over the serial connection.

s_2 · July 30, 2020, 5:51pm

That's good to know, thanks! While building did not work for me right away (prereq checks fail due to supposedly missing shell.sh include, though it is there), I'll check that later... The device is still in my backlog, though for the moment not at the highest priority.

michag86 · July 30, 2020, 8:50pm

While running this command from the top directory

make package/infineon-utilities/feeds/ifx_feeds_uboot/open_uboot/install V=s

I had the same error:

easybox-904-lte-firmware/include/shell.sh;: No such file or directory

after editing line 19 of rules.mk (add a space before the ";") this error was fixed.

I also had to modify scripts/config/lex.zconf.c as written here

Now it looks like this:

ollecting package info: done
Collecting target info: done
make[2]: Entering directory '/home/michael/904/easybox-904-lte-firmware/scripts/config'
In file included from zconf.tab.c:2170:
confdata.c: In function 'conf_write':
confdata.c:414:19: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 128 [-Wformat-overflow=]
  414 |  sprintf(newname, "%s.tmpconfig.%d", dirname, (int)getpid());
      |                   ^~~~~~~~~~~~~~~~~
confdata.c:414:2: note: 'sprintf' output between 13 and 150 bytes into a destination of size 128
  414 |  sprintf(newname, "%s.tmpconfig.%d", dirname, (int)getpid());
      |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[2]: Leaving directory '/home/michael/904/easybox-904-lte-firmware/scripts/config'
 make[1] package/infineon-utilities/feeds/ifx_feeds_uboot/open_uboot/install

I think this looks good, but I don't know what to do next.

suppenkasper0815 · August 6, 2020, 9:55am

@QAuge thank you very much for your hard work and that you keep our device alive!

could you maybe conclude the new situation for those people who wanna Start flashing the device which means could you please show which image is working at the moment and what's your opinion of the development state.

@Plonk34 also thank you very very much to you for you hard work on this project. Maybe you can give us also an update of your view.

Thank you also for the whole community for keeping on the development for this device.

Zuzia · August 17, 2020, 10:52am

**Images with kernel 4.19.138. **

=> Full VPE version with Asterisk, DSL port as a WAN

=> Full VPE version with Asterisk, DSL port as a xDSL

=> Minimal VPE version without Asterisk, DSL port as a WAN

Click on the button "Pobierz". The download is free.

The default configuration /etc/config/wireless is as below:

#WiFi 5 GHz:
config wifi-device 'wl000'
	option type 'ralink'
	option channel '36'
	option legacy_rates '0'
	option htmode 'VHT40'
	option disabled '1'

config wifi-iface 'default_wl000'
	option device 'wl000'
	option mode 'ap'
	option ssid 'EasyBOX'
	option encryption 'psk2+aes'
	option key 'WiFipassword'
	option network 'lan'
	option disabled '1'

#WiFi 2.4 GHz:
config wifi-device 'wl010'
	option type 'ralink'
	option channel '11'
	option legacy_rates '0'
	option htmode 'VHT40'
	option disabled '1'

config wifi-iface 'default_wl010'
	option device 'wl010'
	option mode 'ap'
	option ssid 'EasyBOX1'
	option encryption 'psk2+aes'
	option key 'WiFipassword'
	option network 'lan'
	option disabled '1'

Wireless settings must be made in the command line with vi (or mcedit). First, change the default WiFi password.

Important - do not use Luci WiFi configuration. You can only turn ON/OFF WiFi in Luci.

Opkg is able to update, all kmods are available in the online repository.

gschwarz · August 17, 2020, 10:10pm

I just installed via tftp the fullimage.img linked at https://github.com/Quallenauge/Easybox-904-XDSL, then tried adding a sysupgrade snapshot image via LuCI. The one from 2019-08-31 installs fine, but when I try the one from 2020-07-10 I get an error message "The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform. Select 'Force upgrade' to flash the image even if the image format check fails. Use only if you are sure that the firmware is correct and meant for your device!"
Any ideas what's wrong?

Zuzia · August 18, 2020, 11:58am

I'm sharing a new file fullimage.img. Version with Luci & DHCP server, USB support (ext4, fat32). DSL port as a WAN (Internet connection possible).

=> Link [Click on the button "Pobierz"]