Mate, you've got it in this screenshot. Now comes the easy part. Forget about gaining root access. You don't have to do the commands you post afterwards. Once you've loaded the predator.bin file, you can do this part: https://openwrt.org/toh/acer/predator_connect_w6x#backup
Always use WinSCP, which works very well, and copy the backup files to your computer for security.
Once copied, using winscp, copy the file openwrt-mediatek-filogic-acer_predator-w6x-stock-squashfs-sysupgrade.bin to /tmp/ and run this command: sysupgrade -n /tmp/sysupgrade.bin
The Ubootmod Layout PR has been merged and related files are now available for download. The device now has (Stock Layout) and (OpenWrt U-Boot Layout) as suffix in the name to differentiate the variants according to the storage layout in the firmware-selector site.
Thank you very much for your work. I will try the new u-boot this weekend. On the other hand, I can build a development environment to test 24.10. What should I keep in mind when testing it? Any instructions?
Going from snapshot to 24.10, at least with ubootmod, requires reflashing all the mtd partitions, not just ubi. So in other words, youād need to rerun all the steps in ubootmod section of the wiki going from snapshot to 24.10 and vice versa.
Iāve havenāt tried going from snapshot to 24.10 on stock layout. However, I have tested 24.10 stock layout in isolation.
Make sure you have backups in case you need to unbrick. Iāve bricked mine a few times during dev and it was relatively easy to recover.
Updating info. I installed ubootmod + SNAPSHOT (OpenWrt U-Boot Layout) and everything worked fine. I created the partitions and had no problems. Everything works as expected.
On the other hand, I don't know how to install version 24.10. I cloned the 24.10.4 repository and, as I expected, our model is not there. What am I doing wrong?
Updating info. I created firmware version 24.10 (U-boot Layout version). It works correctly. I updated from the SNAPSHOT version (U-boot layout version) by restoring the default settings, and it worked fine. I did not have to repartition, nor did I reload the U-boot layout:
That's great to hear the 24.10-SNAPSHOT works for you as well. I find it odd I needed to repartition but I could have done it in a rush and missed something.
I'm not sure if I find a necessity to create a 24.10.4 repo, although the source code is available and we can probably add the necessary commits to it.
I think a better approach is to hopefully get this PR merged to the openwrt-24.10 branch to get support for the device for 24.10.5 when it comes out.
First Round:
W6x 1 x 0 Me
I couldn't find a good electronics technician in my city, so I went to another one. He did the soldering. I came home and tested it, but the Putty can't capture any information.
Tomorrow, I'll take it back to a good technician and ask him to redo the soldering.
Believe me, there are plenty of "professionals" like that.
The recommended professional was out of town for work.
Today I'll go see him and see if he can clean up the mess.
You mentioned you did not get any data in PuTTY... what is on the other end of that cable? can you reverse TX and RX and see if you can get data?
Edit:
by looking at your pic, white is TX and green is RX, if it's directly to a UART USB cable, I'm pretty sure you need to reverse that based on typical color coding.
I tried every possible way, but it still wouldnāt read.
I took the motherboard to a skilled technicianāitās been with him for days. He should release it tomorrow, and only then will I be able to test it.
I bought a PI2303HX UART adapter, but just to be safe, I also ordered another one: CH340G.
Today, Iām migrating from Windows 11 to Ubuntu 24.04. As soon as I have the routerās motherboard in hand, Iāll begin the work.
Press UP/DOWN to move, ENTER to select, ESC/CTRL+C to quit
Reading 'dual' from 0x0 to 0x7f7fb9d8, size 0x24 ... OK
Current bootnum[2]
Boot ubi name[ubi1]
ubi0: attaching mtd10
ubi0: scanning is finished
ubi0: attached mtd10 (name "ubi1", size 100 MiB)
ā¦
W6x login:
I press 0, arrow, enter and nothing happens for this boot. I tried with Putty and MobaXterm and nothing...
After booting it always ends at W6x login:
Is it possible that my laptop keyboard isn't being recognized by PuTTY?