Lanchon
commented
2 years ago hi! i was very much sure i would be the only owner of a hacked TR4400 v2 ever, lol congrats on your hardware hack!!! seems all the pics and text i wrote weren't completely a waste :)
so there are 2 issues here:
(1) your firmware is newer:
yours:
Revision: 1782
Last Changed Author: lucien
Last Changed Rev: 1782
Last Changed Date: 2019-08-05 10:19:11 +0800 (Mon, 05 Aug 2019)
VERSION:
Build from: PD1-build01 /home/rdrelease/TR4400v2/TR4400v2_0719_191108/Source by rdrelease
DATE: Mon Nov 11 10:44:03 CST 2019mine:
Revision: 1418
Last Changed Author: sandy
Last Changed Rev: 1418
Last Changed Date: 2018-03-01 16:54:42 +0800 (Thu, 01 Mar 2018)
VERSION:
Build from: sercomm-QCA-Server /home2/mark/TR4400v2_0419b_0301/Source by mark
DATE: Thu Mar 1 17:10:58 CST 2018as long as my SSH server enabling hack works (it does in your case) and the partition layout doesn't change (it sort of doesn't), then you'd succeed in installing by script. note that in the event of a brick, you can always halt the bootloader and try recovering from there.
but there is a more serious issue here:
(2) your system is booting from the alternate system !!!
this device has 2 copies of the system: for each required partition there are two actual partitions, named "NAME" and "NAME_1". for example: "rootfs" and "rootfs_1". the inactive one has the "_1" in the name. when the bootloader wants to switch to the alternate system, it swaps the names assigned to these partitions. in my case, during install my rootfs was partition mtd11 (see here: https://github.com/Lanchon/openwrt-tr4400-v2/blob/e7d707d6bd7839fbd0b8d0bd180fce451df77e47/check-svn1418.sh#L67). but in your case, rootfs is mtd21 !! this means in your system mtd21 is mounted and the commands needed to execute the install actually reside in mtd21. the problem is: the install needs to wipe mtd21. SO DO NOT TRY IT !!!
what you need to do is:
first: get a full backup of MTDs and UBIs. use my scripts.
then: convince your router to boot from the other system. i don't know how, but you can do it by talking to the bootloader (UBOOT). some of the gurus of the IPQ806x platform surely know how to force the bootloader to switch. it might also switch by itself if you power down the router while booting a number of consecutive times. please let me know how you end up doing this so i can document it.
note that we can't rule out that the other system (the currently inactive one, call it "main") could be corrupted or outdated in your installation, so it might fail to boot. but you can always copy contents of the current "XXX" partitions to their respective "main" ones, that for now are named "XXX_1". but note that writing to bootloader partitions might be dangerous.
please note that in MTD devices, the partition names are given dynamically by the bootloader (in your case) or are embedded in the kernel (in the standard openwrt distribution) but DO NOT EXIST on a table on the device like they do in PC disks. this is why the bootloader can choose which system to boot: it assign the non-"_1" names to the partitions it wants to boot and passes those names to the kernel, which mounts the "rootfs" partition, whatever number might be, as informed by the bootloader.
if you want you can send me your backups to lanchon at gmail, but keep in mind that they contain secret info about your router so don't post them publicly.
uragit
Hi! (Hope this is the right place to raise this):
After the tricky business of opening the case, soldering tiny wires, getting a serial console...
I'm stuck installing openwrt on my RACV21A version Arris TR4400 v2. There's a whole bunch of differences flagged up by check-svn1418.sh (see below).
Does this mean there's a problem with check-svn1418.sh, or can I safely ignore the errors?
emmerson@mingo ~/openwrt_arris_racv21a/openwrt-tr4400-v2-main [9] ssh -l root 10.9.124.4 sh <check-svn1418.sh
This script checks the current state of your router in depth. If all checks pass, you are good to go on installing OpenWRT. The router USB port should be empty when running this script.
checking /proc/cmdline checking /etc/svn.info /etc/svn.info - differ: char 69, line 2
ERROR: /etc/svn.info
Path: . URL: svn://10.10.67.238:36901/svn/Router/TR4400v2/TR4400v2_0719/Source Repository Root: svn://10.10.67.238:36901/svn/Router/TR4400v2 Repository UUID: a6b6dc33-2ea1-44c0-8bf5-3169134277e6 Revision: 1782 Node Kind: directory Schedule: normal Last Changed Author: lucien Last Changed Rev: 1782 Last Changed Date: 2019-08-05 10:19:11 +0800 (Mon, 05 Aug 2019)
VERSION: Build from: PD1-build01 /home/rdrelease/TR4400v2/TR4400v2_0719_191108/Source by rdrelease DATE: Mon Nov 11 10:44:03 CST 2019 BOARD_ID: TR4400-CH
checking /etc/openwrt_release /etc/openwrt_release - differ: char 74, line 3
ERROR: /etc/openwrt_release
DISTRIB_ID="OpenWrt" DISTRIB_RELEASE="Bleeding Edge" DISTRIB_REVISION="r1602" DISTRIB_CODENAME="barrier_breaker" DISTRIB_TARGET="ipq806x/generic" DISTRIB_DESCRIPTION="OpenWrt Barrier Breaker r1602" DISTRIB_TAINTS="no-all busybox override"
checking /proc/version /proc/version - differ: char 24, line 1
ERROR: /proc/version
Linux version 3.14.43 (rdrelease@PD1-build01) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.01 r1602) ) #1 SMP PREEMPT Fri Nov 8 20:42:04 CST 2019
checking /proc/mtd /proc/mtd - differ: char 130, line 4
ERROR: /proc/mtd
dev: size erasesize name mtd0: 00040000 00020000 "0:SBL1" mtd1: 00140000 00020000 "0:MIBIB" mtd2: 00140000 00020000 "0:SBL2_1" mtd3: 00280000 00020000 "0:SBL3_1" mtd4: 00120000 00020000 "0:DDRCONFIG_1" mtd5: 00120000 00020000 "0:SSD" mtd6: 00280000 00020000 "0:TZ_1" mtd7: 00280000 00020000 "0:RPM_1" mtd8: 00500000 00020000 "0:APPSBL_1" mtd9: 00080000 00020000 "0:APPSBLENV" mtd10: 00140000 00020000 "0:ART" mtd11: 04000000 00020000 "rootfs_1" mtd12: 00060000 00020000 "0:BOOTCONFIG" mtd13: 00140000 00020000 "0:SBL2" mtd14: 00280000 00020000 "0:SBL3" mtd15: 00120000 00020000 "0:DDRCONFIG" mtd16: 00120000 00020000 "0:SSD_1" mtd17: 00280000 00020000 "0:TZ" mtd18: 00280000 00020000 "0:RPM" mtd19: 00060000 00020000 "0:BOOTCONFIG1" mtd20: 00500000 00020000 "0:APPSBL" mtd21: 04000000 00020000 "rootfs" mtd22: 00100000 00020000 "fw_env" mtd23: 00800000 00020000 "config" mtd24: 00200000 00020000 "PKI" mtd25: 00100000 00020000 "scfgmgr" mtd26: 00008000 00008000 "spi32766.0" mtd27: 003e0000 0001f000 "kernel" mtd28: 01e08000 0001f000 "ubi_rootfs" mtd29: 0001f000 0001f000 "rootfs_data" mtd30: 00744000 0001f000 "ubi_config"
checking /proc/mounts /proc/mounts - differ: char 300, line 8
ERROR: /proc/mounts
rootfs / rootfs rw 0 0 mtd:ubi_rootfs /rom squashfs ro,relatime 0 0 proc /proc proc rw,noatime 0 0 sysfs /sys sysfs rw,noatime 0 0 tmpfs /tmp tmpfs rw,nosuid,nodev,noatime 0 0 tmpfs /tmp/root tmpfs rw,noatime,mode=755 0 0 overlayfs:/tmp/root / overlayfs rw,noatime,lowerdir=/,upperdir=/tmp/root 0 0 ubi1:ubi_config /config ubifs rw,relatime 0 0 tmpfs /dev tmpfs rw,relatime,size=512k,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 debugfs /sys/kernel/debug debugfs rw,noatime 0 0 ramfs /home ramfs rw,relatime 0 0 ramfs /mnt ramfs rw,relatime 0 0 ramfs /etc ramfs rw,relatime 0 0
checking /proc/bus/pci/devices cmp: EOF on
ERROR: /proc/bus/pci/devices
/proc/bus/pci/devices
checking /etc/fw_env.config Warning: Bad CRC, using default environment checking fw_printenv fw_printenv - differ: char 2, line 1
ERROR: fw_printenv
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm bootdelay=5 baudrate=115200
checking dmesg-ubi-attached dmesg-ubi-attached - differ: char 18, line 1
ERROR: dmesg-ubi-attached
UBI: attached mtd21 (name "rootfs", size 64 MiB) to ubi0 UBI: attached mtd23 (name "config", size 8 MiB) to ubi1
checking dmesg-ubifs-mounted checking ubi0_0-kernel ubi0_0-kernel - differ: char 1, line 1
ERROR: ubi0_0-kernel
1e7876636109535510dd7cee16386d36 /dev/ubi0_0
checking ubi0_1-ubi_rootfs ubi0_1-ubi_rootfs - differ: char 1, line 1
ERROR: ubi0_1-ubi_rootfs
edcd4e0e5732f18e81da7b33892fe784 /dev/ubi0_1
checking ubi0_2-rootfs_data
WARNING: Do not proceed installing OpenWrt if any errors were output! Save the output and seek help in the forums instead.