B1300 Unable to Update to LEDE

mauropasse · 2018-04-09T18:40:13.657Z

Hello Justin, I’m trying to do the TFTP flash, with no success.

I’ve followed this steps:
Installing and Testing TFTP Server in Ubuntu/Debian – Mohamed Thalib's Blog
I’ve set my IP address as 192.168.1.2, gave /tftpboot permisions,
I’ve run tftp server in /tftpboot as:
echo -e "v\nbinary\nrexmt 1\ntimeout 60\ntrace\nput qsdk-gl-b1300.bin\n" | tftp 192.168.1.1
I’ve powered the router, but the file is never sent (after 60 secs, the time out is reached).
What am I missing?

Edit:
After experimenting with 2 PC’s I’ve arrived to the conclusion that the TFTP server in the router is never on, that’s why I never got any responses or error messages. Now I have 2 GL-iNet-B1300 routers that when turning on, enter in a loop in which they end up reseting themselves every 30secs. During this time, I can ping 192.168.1.1 but never send the binary file trough ftpt. Also I can’t do the factory reset to come back to the original firmware!

Edit 2:
Finally I could upload the new firmware. The “problem” was that there’s no acknowledge from the router server that the file is being sent. The TFTP client keeps trying to send it until it fails for timeout, but actually the file IS being sent as soon as the router is powered. It’s a good idea to stop the network manager before initializing the TFTP.
Sorry for all the edits.

mauropasse · 2018-05-10T15:05:14.972Z

Hi, just wanted to share some new things I discovered about how to flashing firmware though an HTTP server, since I started to use a serial-USB converter:
serial-port GL-iNet → USB to my PC. (it’s not necessary to have the serial converter, it just helped me to understand/debug what was happening), so if you don’t have one just go to the step number 5.

Open the cover of the router
Connect serial port to the USB using a serial-usb converter
In terminal, type dmesg to find where is the serial-USB attached:
$ dmesg
The ouput should contain something like:
[784212.385191] usb 2-2: cp210x converter now attached to ttyUSB0
Open picocom to read serial data from the router
$ picocom -b 115200 /dev/ttyUSB0 #use the USB number listed by dmesg ouput, in my case ttyUSB0
Power on the router pressing the reset button for more than 10 seconds, then you can see in picocom that an HTTP server is opened at 192.168.1.1
Go to your browser and type the 192.168.1.1 IP address. Now there should be an option to chose and upload your file (I’ve used the sysupgrade.bin file I compiled in openwrt, but renamed as lede-gl-b1300.bin). Wait some time and the sysupgrade is made, way easier than using the TFTP server!

alzhao · 2018-05-10T15:14:34.244Z

Thanks for the sharing.

nnsense · 2018-05-10T20:30:38.917Z

The current U-Boot web is indeed buggy. We’ll fix it asap.

Hi, I just wanted to check the status of this bug, I’m facing exactly the same issue.
The bug is important, it makes any router recovery using the recovery boot impossible.

alzhao · 2018-05-11T02:36:34.548Z

I think this has been fixed. @hansome should have the uboot.

hansome · 2018-05-11T09:28:39.091Z

@mauropasse Hi Mauro, I upload the fixed uboot binary at https://github.com/gl-inet/uboot-ipq40xx/blob/master/uboot-gl-b1300-20180413-md5-464641c1448b8fca42a3ed8f1295b0ad.bin
You can use uboot comand:
run lu
to flash uboot.

mauropasse · 2018-05-11T13:37:34.860Z

Thanks @hansome. Should I rename the file with a particular new name as uboot-gl-b1300.bin and place it in /tpftboot/ before using the run lu command?

hansome · 2018-05-13T05:53:36.192Z

Yes, you’re correct. The uboot command will also give a prompt for the file name.

t0ny0 · 2018-06-14T16:50:47.128Z

u-boot has most definitely not been fixed. I have flashed the provided uboot, and am trying to flash openwrt .bin file. On previous device it took me 76 (correct, seventy six) times to finally get the .bin flashed. On the one I am trying right now - i am on number 79 and still no luck

So timeout has not been fixed on uboot-gl-b1300-20180413-md5-464641c1448b8fca42a3ed8f1295b0ad.bin

stangri · 2018-08-01T04:53:14.342Z

@hansome – can you please clarify which file should be flashed from http://192.168.1.1/uboot.html ?

The bin file posted on github is different from the openwrt-ipq40xx-u-boot-stripped.elf I get when I make an uboot following directions posted here.

But when I try to flash either file via http://192.168.1.1/uboot.html I pick the file, click the “Update U-boot” button and then the browser immediately says “Site cannot be reached” and the B1300 does NOT update uboot.

Can I still update the uboot from uboot WebUI?

hansome · 2018-08-02T07:37:38.679Z

Both uboot-gl-b1300-20180413-md5-464641c1448b8fca42a3ed8f1295b0ad.bin file or you compile is ok. The uboot bin file is a little oldder than source code compiled one which had some code optimization, eg, put firmware name to update in uboot env.

You can update uboot from uboot WebUI.

You can tell the uboot is updated by uboot command line compiled timestamp.

If you uboot is older than 20180413, it has problem of update failure. That case please use uboot command line to update uboot first.

hansome · 2018-08-02T07:43:36.041Z

I test the uboot a lot times with Fast ethernet and Giga ethernet, or chrome and firefox, it’s ok to update. Have you firstly flash uboot of uboot-gl-b1300-20180413-md5-464641c1448b8fca42a3ed8f1295b0ad.bin successfully.

stangri · 2018-08-02T08:30:07.535Z

hansome:

That case please use uboot command line to update uboot first

You mean by opening the case and connecting to the serial headers?

hansome · 2018-08-02T08:37:00.022Z

Yes, the board shipped with old uboot is very old. But you can update firmware with tftpd, no needing to open the case. please check here:

B1300 Unable to Update to LEDE Technical Support for Routers

Hi jp2012 & justin. Sorry for the inconvenience. HI jolouis, thanks for your reply. The current U-Boot web is indeed buggy. We’ll fix it asap. But the is a way to flash firmware without serial port. You need to start a tftpd server with ip address 192.168.1.2, rename the firmware name to lede-gl-b1300.bin if you flash the openwrt snapshot version. If you’d like to go back to factory firmware, you need to rename file name to qsdk-gl-b1300.bin. Connect the device with ethernet to tftpd server,…

stangri · 2018-08-02T08:42:11.220Z

Thank you for your prompt reply. What does the uboot file need to be named when placing it in the TFTP server?

hansome · 2018-08-02T10:09:23.001Z

uboot can not be updated that way. There is a trick to upgrade uboot in factory firmware, using this image:

github.com

gl-inet/uboot-ipq40xx/blob/master/ipq40xx-nor-apps.img

This file is binary. show original

please do the following step:

ssh to device and run:
sed -i ‘s/mandatory_nor=hlos/mandatory_nor=u-boot/’ /lib/upgrade/platform.sh
upload ipq40xx-nor-apps.img at factory webUI: Firmware->Upload Firmware->Upgrade

t0ny0 · 2018-08-02T15:04:59.908Z

That was a comment for older uboot. All is working good now.

stangri · 2018-08-07T20:28:31.851Z

hansome:

Both uboot-gl-b1300-20180413-md5-464641c1448b8fca42a3ed8f1295b0ad.bin file or you compile is ok. The uboot bin file is a little oldder than source code compiled one which had some code optimization, eg, put firmware name to update in uboot env.

With the new uboot, have the names for the bin files uploaded to uboot WebUI have changed? Are they still qsdk-gl-b1300.bin and lede-gl-b1300.bin? Do I have to name the files built with QSDK image builder qsdk-gl-b1300.bin?

For some reason I can’t get the new uboot to successfully flash the images built with QSDK image builder, it looks like the file has been uploaded and is being flashed, however after the reboot I’m back to the previous firmware.

hansome · 2018-08-08T08:07:59.500Z

Whatever name for the bin files is ok.

grepdude · 2019-06-25T20:01:10.460Z

mauropasse - This worked for me. The button I held down during power-up mode was apparently the WPS button:

Press press WPS button for more than 5 seconds to run web failsafe mode

WPS button is pressed for: 5 second(s)

WPS button was pressed for 5 seconds
HTTP server is starting for firmware update…

eth0 PHY0 Down Speed :10 Half duplex
eth0 PHY1 Down Speed :10 Half duplex
eth0 PHY2 Down Speed :10 Half duplex
eth0 PHY3 Down Speed :10 Half duplex
eth0 PHY4 up Speed :1000 Full duplex
NetOurEther = e4:95:6e:45:18:b0
HTTP server is starting at IP: 192.168.1.1
HTTP server is ready!