The Flashing instruction on this page below can lead to the same problem I just have on my router.
It was only cleared here:
It should be clear that more people will not fall to the same problem.
1 Like
- re-flash uboot first using link http://192.168.1.1/uboot.html
- flash the firmware (.ubi file) using http://192.168.1.1/
Thank you for the additional info. It is too late for me to do that now, the router LED no longer show light when powered on and no flashing light during reset procedure.
If you can come up with some instructions would be more then happy to use them right now I am busy between work and this.
Also which file did you flash to uboot page side?
It is this instruction that I followed:
Release the reset pin and head to http://192.168.1.1 , If you are flashing uboot then head to http://192.168.1.1/uboot.html
Then select openwrt-ipq60xx-generic-glinet_gl-ax1800-squashfs-nand-factory.ubi image and flash.
I thought openwrt-ipq60xx-generic-glinet_gl-ax1800-squashfs-nand-factory.ubi is uboot and should go to http://192.168.1.1/uboot.html
It was out of excitement for this firmware that I did not read any further on other pages of information like how to debrick, it was my biggest mistake.
I am happy to help with the writing of instructions people can use, all I need is the correct info what each file is and where to write them and the sequence if sequence is important.
Right the image files:
- squashfs-nand-factory.ubi (Full image to flash via Uboot http://192.168.1.1 )
- squashfs-nand-sysupgrade.bin (Flash via LUCI)
- initramfs-uImage.itb ( Run via TFTP Server using Uboot CMD commands)
So when you are going to flash my firmware you flash only the factory at http://192.168.1.1 page
Only this file uboot-ipq60xx/uboot-gl-ax1800-20220711-md5-9890c67c3dafa5aec172f3a31583f9a7.bin at master · gl-inet/uboot-ipq60xx · GitHub you flash via http://192.168.1.1/uboot.html
If you have flashed the factory image to the uboot.html page then your device is bricked bricked and can not be debricked.
Also Snapshots on my server are somewhat tested, however experimental folder is not and use at your own risk due to not being tested and a higher bricking risk.
1 Like
I appreciate the details, thank you. I need another device to run this through.
I was getting ready to flash the firmware on the my AX1800 when I noticed the contradiction in the instructions. In the instructions above it states to flash only the factory at http://192.168.1.1 page. Then on the download page I seen this note “IMPORTANT: Please Flash Factory Image via Uboot!.”
Am I understanding correct that the “Factory Image” is NOT the same as the “openwrt-ipq60xx-generic-glinet_gl-ax1800-squashfs-nand-factory.ubi” file?
Bottom line is… Flash the openwrt-ipq60xx-generic-glinet_gl-ax1800-squashfs-nand-factory.ubi file via the http://192.168.1.1 page NOT http://192.168.1.1/uboot.html page. Correct?
To flash Solidus’ image, you will need to use the factory.ubi file, which should be flashed through http://192.168.1.1.
In case you encounter issues, like I did, you should first flash the uboot itself through http://192.168.1.1/uboot.html
You can obtain the uboot file from this link: uboot-ipq60xx/uboot-gl-ax1800-20220711-md5-9890c67c3dafa5aec172f3a31583f9a7.bin at master · gl-inet/uboot-ipq60xx · GitHub.
EDIT: added uboot flasher webpage
1 Like
Misteryoso you also forgot to mention when using that uboot file you should use http://192.168.1.1/uboot.html
But simply put
http://192.168.1.1 (for factory.ubi)
http://192.168.1.1/uboot.html (uboot-gl-ax.bin)
1 Like
You’re right, my bad. I’ve edited my reply. Ty
1 Like
Am I understanding correctly that I will only need install “uboot-gl-ax.bin” using http://192.168.1.1/uboot.html if the install of “factory.ubi” goes sideways?
I really appreciate the responses!
Sorry I am late to this thread. What is the difference between this firmware and the GL official one?
1 Like
Hello Rogers,
Like @y2kbug & others, I’m terribly interested in your project.
I’m having a hard time keeping track of the various topics discussed within this massive thread. Have you considered setting up a presence on something like GitHub? I’d think it be easier to keep documentation, releases, faqs, inquiries/bug reports, etc. better sorted there.
For your consideration.
1 Like
The project is in GitHub just look up my handle on here on github. Not sure how to setup what your talking up but willing to learn.
But to answer the question asked, my builds are openwrt builds and no qsdk builds.
Oh, I see your github link under you ‘top posts’ but it 404’s. I found it: solidus1983 (solidus1983) / Repositories · GitHub
I see 18 repos are there but nothing specific to your AX-1800 distro. found under GitHub - solidus1983/gl-infra-builder . I suggest a cloning/renaming to something a little more distinctive (eg: solidus-AX1800).
Does github not allow the hosting of the the released images instead of using something like Mega or Google Drive, etc?
My primary motivation for posting that comment was I personally find github’s ‘issues’ to be better suited for individual queries … never mind the ability to cleanly partition releases in the ‘releases’ section (and its changelog!).
(That all still ignores the ability to keep scripts protected from any catastrophes, of course.)
I’m currently trying to read it all but IMHO this thread has turned into a rather chaotic mess, a ‘dumping ground’ of sorts that makes it far too cumbersome to catch ‘the signal thru the noise.’
1 Like
solidus1983/openwrt at ipq60xx-devel (github.com)
Is the repo i am talking about. The ipq6018 and ipq8074 was merged to qualcommax so all the stuff for the Slate AX and Flint are present in that repo.
I have at the same time removed the gl-intrabuilder too from my profile to make it easier to find the stuff that’s important.
1 Like
Yep; that’s just about what I’m talking about. There’s no way I would have made that association based solely on ARM architecture. I just caught up to the point where you mentioned you work on the AXT1800, too. I have one of them, too!
(… there’s so much going on in this thread…)
I’ll tell you a specifically selfish reason I also suggest a more fleshed out github for these distros: any github ‘release’ page can be converted into a RSS feed by appending .atom on the end of github.com/projectName/releases
One can do similarly to tracking individual ‘issues’ as well via GitHub - RSS-Bridge/rss-bridge: The RSS feed for websites missing it
I’d love to add a feed to my RSS reader to stay on top developments w/ your progress.
2 Likes
Re: R21362
FYI: A ‘dirty workaround’ might be just to throw those commands into /etc/rc.local until a proper fix is sorted.
1 Like
Just a heads up everyone the next two days as of 22:00 GMT the server will be down due to electricity work.