Wrong, do not follow this thread

Hello,

I thought it would be interesting to report how an end user can successfully run an image on the S1300.

I succeeded by downloading the gl.inet imagebuilder (URL in git clone below). I already have a good build environment set up so you may need to install compilation tools.

git clone https://github.com/gl-inet/imagebuilder
cd imagebuilder
./gl_image -l
<lists platforms>
./gl_image -p s1300
<creates the binary file>

Then I followed the instructions at https://github.com/gl-inet/openwrt/tree/openwrt-18.06-s1300

  1. Push reset button and plug in power, wifi led will blink, release button when middle led light on
  2. Set ip to 192.168.1.0/24 and use web browser to access 192.168.1.1
  3. Choose file s1300-factory-to-openwrt.img and click “Update Firmware” (Steps 3 will consume about 30 seconds, then):

Now the router repeatedly shows:
A: Left light on for a few seconds
B: All lights off for 1 second
C: All lights on for 2 seconds
Repeat at A

  1. Poweroff router
    (After a few cycles of this I powered off the router according to the instructions.)

  2. Push reset button and plug in power, wifi led will blink, release button when middle led light on
    (If you do not hold down the RESET button the ABC above light cycle repeats. )

  3. Use web browser to access 192.168.1.1/

  4. Choose the file (mine was on Dec 18, qsdk-s1300-3.029-1218.img) and uploaded it.

At this point the router still followed the ABC light pattern above. I then had to apply the reverse img to make my update stick.

  1. Poweroff router
    (After a few cycles of this I powered off the router according to the instructions.)

  2. Push reset button and plug in power, wifi led will blink, release button when middle led light on
    (If you do not hold down the RESET button the ABC above light cycle repeats. )

  3. Use web browser to access http://192.168.1.1/

  4. Upload the s1300-openwrt-to-factory.img — note that this is the OTHER image file from before.

When the router rebooted, my new image was running. Based on compile time and version number, I could tell by the Admin Panel upgrade that it was using my new image. I’ll update this with additional information, but so far this is looking good.

This is completely wrong. After you have built an image using the GL-Imagebuilder from here (this assumes you followed all steps and succeeded):

You can flash the firmware directly in the GL UI.

Do not keep settings when flashing.

If it’s completely wrong, then why did they put those instructions into Github? What is the purpose of those instructions?

You mixed up the “Vanilla” OpenWRT with the GL-iNet OpenVRT.

The GL-iNet OpenWRT runs from the EMMC partition and requires changes. That is why if you want to flash “Vanilla” OpenWRT you need to revert those changes to be able to flash. “Vanilla” OpenWRT runs from the smaller 16mb partition. That is what the transition s1300-factory-to-opemwrt.img is for. If you try flashing “Vanilla” OpenWRT without doing it, you end up with a soft brick. Going the other way is also the same, and you need the second s1300-openwrt-to-factory.img.

However, using the GL-Imagebuilder to create a custom image does not require any changes, it is just flashed ontop of the existing firmware, via the UI upload or via uboot.

Also notice that “openwrt” and “imagebuilder” are separate repositories and the instructions are not to be combined. That is the mistake you made.

3 Likes

Thanks—that was a helpful answer.

I am still stuck on what artifact the “vanilla” OpenWRT compile should be deploying to the device without bricking it. I’m afraid if I install the wrong thing, it will brick my device again. So I’ve compiled according to the instructions, but what is the name of the binary artifact I pull out of the build directories and upload AFTER uploading s1300-factory-to-opemwrt.img ?

This is related to Bricked S1300 where I haven’t gotten an answer there either.

Ok so first off. What are you trying to do?

A. You want to have your own image with the GL OpenWRT and some custom packages? Like the router came from the store, but with extra config or packages?
B. You want to run OpenWRT without the GL UI.

Notice you will have better performance with option A, and you have Mesh.
With option B, you have your own compiled firmware, but since the GL firmware contains proprietary drivers, you loose Mesh and some speed.

I think we would be happier with extra mesh and speed if the packages are compatible, but if they are not compatible then I would need to go with Option B. The GL OpenWRT for the S1300 looks like it’s based on Chaos Calmer which is pretty old.

Yeah its based on 15.05 OpenWRT with all the Qualcomm proprietary drivers and fixes. Also some critical packages were updated to newer versions.

What packages are you thinking about? It is also very easy to compile a package that is not available using the GL SDK. Most other packages should be there already. Try generating an image following the guide in the GL Imagebuilder github, including the packages you want.

1 Like

I used both img’s from your git repo, still my device seems “softbricked”, can you might help me?
I just want back to stock GL-inet stock firmware and stay there.

https://forum.gl-inet.com/t/need-urgent-help-my-gl-s1300-seems-bricked/10586/2