Askey RAC2V1K / RT4230W REV6 Support

@lmore377 if you have spare time, can we try to include this?

someone has a better result there

Thanks

@efsg sure, just credit my GitHub or something

@frustro don't flash openwrt onto a device being rented from an ISP. There's no way to go back to stock on these routers because trying to restore the stock firmware just breaks /overlay which makes it enter a boot loop. Also the routers that have sac2v1k are identical to rac2v1k except for the fact that they have a smaller flash since the sac routers have simpler firmware(mainly no web interface for changing settings and a lot less packages)

@eganov I've been busy with stuff but I'll look into it soon

I'm pausing development for a while until I can get my hands on another router. The one I bought for this is being used as my main router now (Over a month with no problems! The only reboot that happened was when the power cut out) and I don't want to cause any issues with it since my entire family is using it.

1 Like

Very understandable, what I can report, your build is no hiccup at all, I have been using it for 2weeks with full wireguard as VPN client /gateway to the commercial VPN provider. got 240Mbps over 260M line
the wifi coverages are weak for both bands, consider those 4X4 Mimo antennas location inside the unit, but I don't use them anyway.

thanks again

Thank you guys. I finally got this flashed to my Spectrum / Askey RT4230W. Works great.

I tried a few terminal software to communicate using the serial port. https://www.emtec.com/zoc/ finally worked for me.
It was a pain to open the router and get it flashed. But the instructions and commands given worked flawless.

I'm back to working on this. There's not much to do anymore except for trying to get it pulled into the main openwrt repo and seeing if I can get those experimental qca nss drivers working

1 Like

this is great news. i've go 2 of these with stock firmware still, and 2 with openwrt (1 RAC, 1 SAC) -all ready for testing.

Openwrt system has been upgraded. Is there any way to restore the original firmware

Nope. That was one of the first things I tried to figure out but never did. I might still have a copy of the stock firmware somewhere so I'll look into it when I have time (which is rare since school and all).

my neighbors gave me 2 units RAC2V1K
one with FW 1.2.3 no SSH access and the other with weird firmware SAC2V1K even the Physical unit states RAC2V1K no GUI access for setting, only basic router info

I can open those units and access from the serial console
Can you let me know how to dump those stock firmware? via UBoot or UBI command maybe?

Is it OK to backup the mtd20 firmware partition and cover it to another device

@lmore377 -
hello -
i'm using your build r13657 on a rac2v1k.
i opkg updated then opkg installed luci-app-p910nd
a minor dependency error, forced install

i can't get usb printer to be recognized.
usb ports are on /dev/bus/usb/001 ..... /004

changing port setting for p910nd doesnt resolve issue.

questions:
is there a possible build that incorporates p910nd?
is there a build for 19.07.4 ?

the openwrt snapshot process is all messed up for months now with dts conversions, kernel size issues, buildbot issues - so i'm not sure where to go with this 4230w development

best wishes for health and happiness

None of the kernel modules from the main openwrt repo will install because it expects you to be using one of their images. I recently synced up my branch with the main openwrt repo so you can clone that with git git clone -b askey_rt4230w_support https://github.com/lmore377/openwrt.git and build your own image and it'll work fine. I'll see if maybe I can just host my own opkg repo until the pull request gets eventually accepted. Also I just looked again and it looks like a patch just went through that finally lets pci (aka wifi) work without using bootipq so no more red light at boot. I'll look at that over the weekend.

great news and information. thank you

i get an error with your setenv command:

Creating 1 MTD partitions on "nand0":
0x000002400000-0x00001c400000 : "mtd=0"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1024:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1025:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1026:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1027:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1028:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1029:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1030:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1031:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1032:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1033:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1034:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1035:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1036:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1037:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1038:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1039:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1040:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1041:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1042:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1043:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1044:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1045:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1046:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1047:0, read 0 bytes
ubi_io_read[188] not here
UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1049:0, read 0 bytes
ubi_io_read[188] not here
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=0"
UBI: MTD device size:            416 MiB
UBI: number of good PEBs:        3328
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     3
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 3328
UBI: number of PEBs reserved for bad PEB handling: 33
UBI: max/mean erase counter: 2/0
Read 7208960 bytes from volume kernel to 44000000
Wrong Image Format for bootm command
ERROR: can't get kernel image!

What’s the recovery procedure for this device, I enabled DropBear and rebooted. Now its not booting anymore.

Can you interrupt u-boot and run nand bad? It seems like there might be some bad blocks on the nand but I don't know if that should cause any issues or not.

What step did you get up to? Were you ever able to actually ssh into it?

I figured it out. Set static ip on computer to 192.168.1.2 255.255.255.000 192.168.1.1. Unplug router power, plug back up blue light blinks red light comes on, when the red light goes off start repeatedly hitting the reset button when the light starts blinking red instead of blue it’s in failsafe mode. Open up power shell in Windows. SSH 192.168.1.1 -l root hit enter. No password and Faillsafe mode pops up type mount_root hit enter then firstboot && reboot now should load up back up as a fresh install.

Been messing with the Packages installed and ran into some errors running updates and testing some packages earlier today. Updating everything not in the list goes fine except Rpcd
All kmods

Rpcd-mod-file

Rpcd-mod-iwinfo

Libus20191227

Base-files

Busybox

Dnsmasq

DropBear

Firewall

Uhttpd

Uhttpd-mod-ubus

Ubus ones

And thank you for your work I’ve been having a lot of fun tweaking and testing this thing out finally. Fixing to hook it up later in place of my DLink DIR-860L A1 so far from testing it I’m having much better connection speed stability and everything from the Dir-860L on DDWRT.