[BETA] Rescue System V4, using a custom LEDE firmware September 09, 2016 04:11PM |
Registered: 9 years ago Posts: 298 |
root@lede:/# ls /bin ash egrep mknod sed board_detect false mktemp sh busybox fgrep mount sleep cat fsync mv sync chgrp grep netmsg tar chmod gunzip netstat touch chown gzip nice true config_generate ipcalc.sh pidof ubus cp kill ping uclient-fetch date ln ping6 umount dd lock ps uname df login pwd vi dmesg ls rm wget echo mkdir rmdir zcat root@lede:/# ls /sbin askfirst init mtd sysupgrade block ip netifd ubusd cgdisk jffs2mark pivot_root uci devstatus jffs2reset poweroff udevtrigger firstboot kmodloader procd udhcpc gdisk led.sh reboot upgraded halt logd reload_config urandom_seed hotplug-call logread route validate_data hwclock mdadm sgdisk wifi ifconfig mkfs.xfs start-stop-daemon xfs_db ifdown mkswap swconfig xfs_growfs ifstatus mmc switch_root xfs_repair ifup mount_root sysctl root@lede:/# ls /usr/bin [ du mkfifo tar [[ env mkfs.btrfs tee ar expr mount test attr file mountpoint time awk find nano top basename findmnt nc tr bc flock ncdu traceroute btrfs free nslookup traceroute6 btrfs-debug-tree fsck.btrfs passwd umount btrfs-find-root funzip perl uniq btrfs-image getfacl perl5.22.1 unlzma btrfs-map-logical getfattr pgrep unxz btrfs-show-super getrandom pkg-config unzip btrfs-zero-log head printf unzipsfx btrfsck hexdump readlink uptime btrfstune id reset usign bunzip2 jshn rsync uuidgen bzcat jsonfilter scp vim bzip2 killall seq wc chacl ldd setfacl wget chattr less setfattr wget-ssl chroot lftp sha1sum which clear logger sha256sum xargs cmp lsattr signify xz crontab lsblk sort xzcat cut lsof spi-config yes dbclient lzcat spi-pipe zipgrep dc lzma ssh zipinfo dirname mc strings dmesg mcedit systool dropbearkey md5sum tail root@lede:/# ls /usr/sbin atftp fsck.ext4 mkfs.fat swaplabel atftpd fsck.f2fs mkfs.msdos swapoff badblocks fsck.fat mkfs.vfat swapon blkid fsck.msdos mkswap tune2fs brctl fsck.vfat modinfo ubiattach chroot fw_printenv modprobe ubiblock crond fw_setenv mtdinfo ubicrc32 debootstrap insmod nanddump ubidetach dnsmasq ip6tables nandtest ubiformat dosfsck ip6tables-restore nandwrite ubimkvol dropbear ip6tables-save ntpd ubinfo dump.f2fs iptables ntpd-hotplug ubinize e2fsck iptables-restore odhcp6c ubirename f2fstat iptables-save odhcpd ubirmvol fatlabel lsmod odhcpd-update ubirsvol fdisk mke2fs resize2fs ubiupdatevol fibmap.f2fs mkfs.ext2 rmmod wipefs findfs mkfs.ext3 sensors xtables-multi fsck.ext2 mkfs.ext4 sensors-detect fsck.ext3 mkfs.f2fs smartctl
recovery_bootargs=setenv bootargs console=ttyS0,115200 rootdelay=10 $mtdparts_lede
bootcmd_recovery=run recovery_bootargs; nand read 0x800000 nand0,7 ; bootm 0x800000 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_recovery;here the "nand0" is the NAND chip onboard, and "nand0,7" is like saying mtd7, or whatever hex offsets the partition sits in and none really feels like figuring out on this side.
mtdparts_lede=mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(nope_kernel_1),0x2FC0000(nope_rootfs1),0xA00000(kernel),0x2FC0000(rootfs)
Re: [BETA] Rescue System V4, using a custom LEDE firmware September 09, 2016 07:27PM |
Admin Registered: 13 years ago Posts: 18,898 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware September 10, 2016 06:34AM |
Registered: 9 years ago Posts: 298 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware September 10, 2016 03:58PM |
Admin Registered: 13 years ago Posts: 18,898 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware September 14, 2016 09:21AM |
Registered: 11 years ago Posts: 42 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware October 02, 2016 12:19PM |
Registered: 9 years ago Posts: 298 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware October 26, 2016 07:31AM |
Registered: 11 years ago Posts: 1,303 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware October 26, 2016 12:34PM |
Registered: 9 years ago Posts: 298 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware April 14, 2017 09:10PM |
Registered: 7 years ago Posts: 67 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware April 14, 2017 11:53PM |
Registered: 7 years ago Posts: 67 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware April 15, 2017 02:17AM |
Registered: 12 years ago Posts: 32 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware April 15, 2017 09:16AM |
Registered: 9 years ago Posts: 298 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware April 15, 2017 11:41AM |
Registered: 12 years ago Posts: 32 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware April 15, 2017 01:07PM |
Registered: 9 years ago Posts: 298 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware May 09, 2017 01:24PM |
Registered: 7 years ago Posts: 22 |
flash_erase /dev/mtd2 0 0 Erasing 128 Kibyte @ 2e0000 -- 100 % complete nandwrite /dev/mtd2 uImage-kirkwood-pogoplug_v4
Input file is not page-aligned. Use the padding option. nandwrite: error!: Data was only partially written due to error error 0 (Success)
** Bad device usb 0 ** loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ... ** Bad device usb 0 ** ## Booting kernel from Legacy Image at 00800000 ... Image Name: recovery-pogoplug_v4 Created: 2016-09-09 19:17:21 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1871182 Bytes = 1.8 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! NAND read: device 0 offset 0x500000, size 0x300000 NAND read from offset 500000 failed -74 0 bytes read: ERROR ## Booting kernel from Legacy Image at 00800000 ... Image Name: recovery-pogoplug_v4 Created: 2016-09-09 19:17:21 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1871182 Bytes = 1.8 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! Pogov4>
Re: [BETA] Rescue System V4, using a custom LEDE firmware May 09, 2017 03:40PM |
Registered: 9 years ago Posts: 298 |
nandwrite -b 1 -n /dev/mtd2 -p uImage-kirkwood-pogoplug_v4
Re: [BETA] Rescue System V4, using a custom LEDE firmware May 09, 2017 04:04PM |
Registered: 7 years ago Posts: 22 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware May 11, 2017 03:59AM |
Registered: 7 years ago Posts: 7 |
/e-data/ # nandwrite /dev/mtd0 kirkwood/generic/u-boot-nsa325/u-boot.kwb Input file is not page aligned Data did not fit into device, due to bad blocks : Success
/e-data/tools # dmesg | grep -i bad Scanning device for bad blocks
Re: [BETA] Rescue System V4, using a custom LEDE firmware June 17, 2017 03:39AM |
Registered: 9 years ago Posts: 298 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware October 27, 2017 06:15AM |
Registered: 9 years ago Posts: 6 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware October 30, 2017 02:25PM |
Registered: 9 years ago Posts: 298 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware March 09, 2018 06:10PM |
Registered: 12 years ago Posts: 28 |
root@debian:/etc# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors # pogoplug pro /dev/mtd0 0x00100000 0x20000 0x20000 root@debian:/etc# cat /proc/mtd dev: size erasesize name mtd0: 00e00000 00020000 "boot" mtd1: 07200000 00020000 "data"
Romain
Re: [BETA] Rescue System V4, using a custom LEDE firmware March 30, 2018 10:14AM |
cat /proc/mtd dev: size erasesize name mtd0: 000c0000 00020000 "uboot" mtd1: 00080000 00020000 "uboot_env" mtd2: 07ec0000 00020000 "ubi" cat /proc/cpuinfo processor : 0 model name : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 1196.85 Features : swp half fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Marvell Kirkwood (Flattened Device Tree) Revision : 0000 Serial : 0000000000000000 cat /proc/partitions major minor #blocks name 31 0 768 mtdblock0 31 1 512 mtdblock1 31 2 129792 mtdblock2
Re: [BETA] Rescue System V4, using a custom LEDE firmware May 04, 2018 04:21PM |
Registered: 7 years ago Posts: 9 |
dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00400000 00020000 "uImage" mtd2: 02000000 00020000 "rootfs" mtd3: 05b00000 00020000 "data"
cd /tmp #use nand_erase or flash_erase, what you have. flash_erase /dev/mtd1 0 0 nandwrite -p /dev/mtd1 uImage-kirkwood-pogo_e02 flash_erase /dev/mtd2 0 0 nandwrite /dev/mtd2 lede-kirkwood-generic-squashfs.img
fw_setenv recovery_bootargs 'setenv bootargs console=ttyS0,115200 rootdelay=10 $mtdparts_lede' fw_setenv bootcmd_recovery 'run recovery_bootargs; nand read 0x800000 0x100000 0x400000; bootm 0x800000' fw_setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_recovery;' fw_setenv mtdparts_lede 'mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)'
Re: [BETA] Rescue System V4, using a custom LEDE firmware June 02, 2018 10:35AM |
Registered: 7 years ago Posts: 337 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware June 06, 2018 02:51AM |
Registered: 7 years ago Posts: 337 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware July 06, 2018 12:06PM |
Registered: 6 years ago Posts: 11 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware March 08, 2019 07:41AM |
Registered: 12 years ago Posts: 28 |
Re: [BETA] Rescue System V4, using a custom LEDE firmware October 16, 2019 10:27PM |
Registered: 11 years ago Posts: 18 |
jake
Re: [BETA] Rescue System V4, using a custom LEDE firmware January 22, 2021 02:52PM |