[Need urgent help] My GL-S1300 seems bricked

surabi · 2020-04-27T06:13:09.589Z

Hey, I followed this tutorial: Wrong, do not follow this thread

exactly, but unfortunately after the upgrade then the device isn’t starting anymore, no lights, nothing. I can’t get into uboot (web), tftp recovery might be possible, but I don’t know the IPs (and no one else on search engines to find as it seems), is it possible that if I use the GL-inet image builder in a VM that there’s a possibility to flash it through that again? I have the device a week or so, it’s not my first GL-Inet device therefore I didn’t expect that I could brick it and I don’t think its really bricked, but the standards like 192.168.1.1 or 192.168.8.1 aren’t working. I did nothing else as the guy in the above linked post.

Proof of ownership can be provided to GL-Inet Stuff I have the packaging. Telnet, SSH etc. not working, but I also don’t know any rescue ip other than 192.168.1.1 so I hope anyone can help me out. Thanks.

Johnex · 2020-04-27T10:12:35.891Z

Did you follow this guide?

docs.gl-inet.com

Debrick via Uboot - GL.iNet Docs

Documentation for GL.iNet Productions

limbot · 2020-04-27T10:25:18.154Z

surabi:

exactly, but unfortunately after the upgrade then the device isn’t starting anymore, no lights, nothing.

Have you checked the AC Adapter power supply? Just did some test/recoveries on some Amazon AU returns and one of the B1300s worked fine EXCEPT for a dead AC Adapter power supply

surabi · 2020-04-27T16:34:38.423Z

Yes, I already did test it with two (ofc also 12V) others, didn’t help unfortunately. I think it’s on when the power is attached, since the network statistics are suggesting that it’s at least not dead. But there ends my knowledge also, I don’t know how to recover it without the uboot-recovery interface or how to use TFTP properly or if that’s even if possible via the wan port. Next problem would be, I have no usb to serial adapter, never used such a thing and wouldn’t know how. Also, yes I did try the debrick tutorial, the problem is I can’t access the uboot-http after flashing the img file s1300-factory-to-openwrt.img, all LEDs are staying off. @limbot @Johnex

hansome · 2020-04-28T02:18:12.836Z

Hi, are you trying to flash openwrt compiled by this repo：

github.com

GitHub - gl-inet/openwrt at openwrt-18.06-s1300

openwrt-18.06-s1300

This repository is fork from openwrt official repo, we will update the latest tag and release GL.iNet firmware based on it.

Did you check the README.md for flashing guide

github.com

gl-inet/openwrt/blob/openwrt-18.06-s1300/README.md

# Install openwrt via uboot web:

### **NB: need to flash transition image firstly, or it will be brick.**

The transition image is [**s1300-factory-to-openwrt.img**](https://github.com/gl-inet/openwrt/blob/openwrt-18.06-s1300/s1300-factory-to-openwrt.img)
when you install openwrt. So first time installation you need to access uboot web twice.
Afterwards, openwrt sysupgrade can be used.

- **Steps:**

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 http://192.168.1.1
3. Choose file [**s1300-factory-to-openwrt.img**](https://github.com/gl-inet/openwrt/blob/openwrt-18.06-s1300/s1300-factory-to-openwrt.img) and  click "Update Firmware"
  (Steps 3 will consume about 30 seconds, then):
4. Poweroff router
5. Repeat step 1, 2, and when step 3 choose your compiled openwrt firmware file and update firmware
  (When update finished, router will reboot automatically)

- **Why need transition image**

This file has been truncated. show original

surabi · 2020-04-28T03:24:32.509Z

@hansome Hi, yes, I did. At least to the extend it’s overlapping with the tutorial I posted in the first post. //edit I Just noticed that they are not the same, I followed the wrong one posted in the first post.

I wasn’t able to get to the OpenWRT sysupgrade part; the LEDs stopped working at the second flash, aka point 5 on the github tutorial. The first flash was done in the way its described, worked. After that I followed the other tutorial, so I used the factory-to-openwrt-, rebooted into uboot-http without problem, and flashed then flashed the wrong image. The LEDs went down while flashing.

But after the explanation on your Github,

“The kernel and rootfs of factory firmware are on eMMC, and OpenWRT firmware is on NOR flash. The transition image includes U-boot and partition table, which decides where to load kernel and rootfs. After you install OpenWrt image, you can switch between factory and OpenWrt firmware by flashing transition image.”
This would have just brought me in consequence back to the partition on the eMMC, or not? I’m using GL-Inet routers for quite a while now daily and never managed to soft-brick or brick any of them. At max, a few restarts where necessary or at worst I couldn’t explain myself why it’s working again after a few hours, but bricking it seemed for me as of yet impossible, that’s why (in theory) the only explanation for myself would be the above written, but still, theoretically I would then be just back on the eMMC, which should have the uboot partitions and all that.
Now, how mandatory is it to use “192.168.1.0” as IP address in the case we have tracked it down now since I always used 192.168.1.11 or 192.168.1.2 for the computer and 192.168.1.1 for the router/gateway, is it worth a try / safe to try to boot it with these parameters?
If it helps/is necessary I can share a Debian VM via any desk or alike, we configure there the image builder, I use my Gigabit switch (if we must do something while booting, this is a great help IMO). You could maybe take over the control and see what you can get?) As said, there are no lights on the router, but the macOS network utilities are showing that there is something. That’s why I’m thinking of telnet or alike for recovery.
If you think that has all no point, please tell me asap what I could do else, and if the only thing is opening the unit and connect via an USB to serial adapter, I’ll just order one, just in case… “RS232 3.3V / 5V PL2303 Module Serial TTL USB UART Board”

Nevertheless, I really hope theres any other possibility.
I’d feel a lot safer to not soft- but really brick it this time, if I could use familiar (aka software only) methods.

Thank you very much!

/edit again:
I tested it now again after having it for almost a day turned off and was using the ethernet, not the wan port and saw that the S1300 is definitely reachable. Just not for me or the uboot-web

hansome · 2020-04-28T07:18:11.545Z

Really sorry for the inconvinience.

This would have just brought me in consequence back to the partition on the eMMC, or not?

==> Only if you flashed s1300-openwrt-to-factory.img.

Now, how mandatory is it to use “192.168.1.0” as IP address in the case we have tracked it down now since I always used 192.168.1.11 or 192.168.1.2 for the computer and 192.168.1.1 for the router/gateway, is it worth a try / safe to try to boot it with these parameters?

==> set PC ip to 192.168.1.11 or 192.168.1.2 both okay when using uboot web.

There was a old version of buggy uboot that will erase the whole nor flash when flashing openwrt/lede image. And the nor flash has the uboot bootloader while the eMMC has only filesystem, so that bug will cause to truely brick the device.

It seems that you haven’t manged to flash s1300-factory-to-openwrt.img or s1300-openwrt-to-factory.img image, they have the right uboot. If device bricked, no software only solution is available. How can you tell S1300 is reachable, could you show some picture?

surabi · 2020-04-29T00:38:08.671Z

Answered your mail and for sure I have only s1300-factory-to-openwrt.img these used. That was the problem in the other tutorial apparently, sounded like you should use both and then flash OpenWRT, I test it again to be sure but theres a connection reset after pressing the power button, just only the network logfiles, which doesn’t help much. 100% I’m not yet.

@fellow gl-inet-users just a PSA:
If one of you has the idea to try this also, the “wrong” tutorial by a user I posted above is now flagged correctly as wrong, it’s highly probably correct what @hansome posted and I’m sure if you follow his tutorial exactly it will work. But remember apparently is it relatively easy to brick your device compared to the “undestroyable” travel router ( & all with older chipsets basically) series. The official firmware is for both the B1300 and S1300 to find here just update this, just my advice because it’s apparently IMO not worth it. They get regularly updated, including a clean openwrt release.

hansome · 2020-04-29T02:00:39.780Z

surabi:

for sure I have only s1300-factory-to-openwrt.img these used. That was the problem in the other tutorial apparently, sounded like you should use both and then flash OpenWRT,

If you used s1300-factory-to-openwrt.img before flash OpenWRT, that will be okay. No need to use s1300-openwrt-to-factory.img. So maybe it’s the s1300-factory-to-openwrt.img not suceccesfully flashed.

I’ll send you a 16MB bin file to reprogram the flash.

surabi · 2020-04-29T09:37:40.311Z

Got it, I’ll update here when my tools have arrived. And yes, it sounds very much like you’re right, for some reason it’s probably not successfully flashed.^^ But I won’t try it again I’m happy when I managed to fix it and stay then rather on stock firmware

Johnex · 2020-04-29T10:16:42.025Z

Yeah i flagged it as wrong and closed it. Didn’t expect anyone to not read the entire thread and read the posts i made saying it was wrong.

Sorry for that.

surabi · 2020-05-03T01:03:34.659Z

Update for the support @hansome
My set I send you is arrvived, I’ll get it tomorrow and try to document the recover procees and hope this is at least if I can’t make it maybe in the realm of possibilities I get to send it then back to HK, but with the data I have and the video tutorial etc. I’m optimistic I can solve it and document it for everyone who might for whatever reason wants to do that as well.

Lolo_Bee · 2021-10-07T08:04:12.537Z

hansome:

16MB bin file to reprogram the flash

Sorry for bumping an old post, but I’m in the same situation.
My device was fully working with a customized-firmware I built from your repo. Two days ago, I performed some modifications (adding new drivers), and after flashing, no lights and no serial access, so It might be a dead EPROM.

I have the tools to reflash it even without desoldering, but I can’t find the file anywhere, only references to it in forum threads.

So, how can I get the magic 16MB bin file to reprogram the flash?

Very many thanks, Manuel

hansome · 2021-10-07T14:44:04.288Z

Please send me a picture of your device’s mac address and sn label, to email handongming#gl-inet.com

Lolo_Bee · 2021-10-09T08:43:09.927Z

Email sent, anywsy I have ordered a new s1300.
Can I “copy” flash from one device to another? Or it is linked to serial numer or mac address?

Very manu thanks, manuel

hansome · 2021-10-09T12:34:14.335Z

Hello Lolo_Bee, I replied your email yesterday, maybe check your spam.
Yes it is linked to serial numer or mac address. Every devices have it’s own ART partition, copy to another will cause performance loss to some extent.

Lolo_Bee · 2021-10-11T05:48:39.400Z

Hello hansome, email reached SPAM…

I have been able to flash your file with a clip-on adapter, and my s1300 is working again.
If i get a poor wifi performance, because of a missing ART partition, I will use it as a VPN server
Anyway I will try another think and if it works, I will post it here for any others looking for help.

Very many thanks and great support!!!

levelw · 2023-07-25T17:51:44.030Z

I’m very sorry, I replied to a post from two years ago. I encountered the same S1300 firmware issue. I have already sent images of my device information to your email. Please help me build the CH341a SPI sop8 programmer firmware for two devices. Thank you.