Hopefully you'll recover and put this behind you, but as far as using dd-wrt, you'll need to buy a supported router and be sure to read the how-toos first...
i know. i have a linksys e1000 with it on it. know how it works and it actually helped that crappy router a lot... especially on how long it use to boot up.
rightfully so, pending if you were to buy a newer router with more power sufficiently provide all network needs, but ok the E1000 should be fine for you. So do you know if openwrt is on both partitions and how did you verify that?
because i had to install the advanced boot option again and rebooted back to the one i was on/been using.
what are you trying now?
I have just done some testing on my E4200v2 and I see the exact same behaviour as Bobcamo.
Before doing this, both my partitions were on 18.06.
I tried flashing in the Luci UI, and go the same error Bob mentioned.
Then I scp'd the img file over and ran
cd /tmp
sysupgrade -F -n /tmp/FW_E4200v2_2.1.41.164606.img
inspired by this post.
Here is the result from the above command:
# here is the output from that command:
Image metadata not found
Image check 'fwtool_check_image' failed but --force given - will update anyway!
Commencing upgrade. Closing all shell sessions.
Connection to 192.168.1.1 closed by remote host.
Connection to 192.168.1.1 closed.
And same as Bob, the router goes into light breathing mode forever.
1 Like
Are there any MTD expert here that could tell me how to dump my working partition firmware for fbradyirl and Bobcamo? Maybe they can restore my firmware dump after.
(I do not have serial access)
Partition 1: offset 0x200000, size 0x1a00000, name "kernel1"
Partition 2: offset 0x1c00000, size 0x1a00000, name "kernel2"
what do you mean? using the 18.06.1 if that's what your asking.
@fbradyirl
oh thank god i'm not the only one... sucks... but yeah lol.
also, that is the exact command line that shows when i hit enter. but also pops that.disconnect windows
I do believe they'll need certain information regarding board and certain params also that are related to their model. They would need to do a serial connection too, and edit a compatible mtd partition very dangerous if you don't know what your doing.
Edited: Has anyone tried the dd command on the linksys.img image then using the sysupgrade technique?
I believe that these information are stored in another partition than the kernel partition (I assume you are referring to MAC and board info).
I still believe that it doesn't require serial since we would be writing to another inactive partition. Maybe MTD is not the right tool, dd the mounted partition might be the way.
maybe remove the check from keep settings,and do a reset again, or remove check then proceed the flash new firmware image.
that didn't matter on my end. tried both.
Same. Doesn't make a difference.
I also just tried installing the "non-cloud" firmware and get the same results.
root@OpenWrt:/tmp# sysupgrade -F -n FW_E4200_2.0.37.131047.SSA
Image metadata not found
Image check 'fwtool_check_image' failed but --force given - will update anyway!
Commencing upgrade. Closing all shell sessions.
Connection to 192.168.1.1 closed by remote host.
Connection to 192.168.1.1 closed.
Can you tell me what partitions are mounted on your router (I don't have access to my E4200 right now)? There should be "kernel" and maybe something like "alt_kernel".
This any use?
root@OpenWrt:/mnt# cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "u-boot"
mtd1: 00020000 00020000 "u_env"
mtd2: 00020000 00020000 "s_env"
mtd3: 002a0000 00020000 "kernel1"
mtd4: 01760000 00020000 "ubi"
mtd5: 002a0000 00020000 "kernel2"
mtd6: 01760000 00020000 "rootfs2"
mtd7: 04a00000 00020000 "syscfg"
mtd8: 00140000 00020000 "unused"
root@OpenWrt:/mnt#
Yes. I will try to dd my Linksys partition tonight and create a dump. Then I think you'll be able to write this dump using mtd or sysupgrade. I'll check to see if it matches the .IMG file too.
do i just run this command in putty /mnt# cat /proc/mtd
to get that info? was gonna post mine too just in case.
Just
cat /proc/mtd
root@OpenWrt:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "u-boot"
mtd1: 00020000 00020000 "u_env"
mtd2: 00020000 00020000 "s_env"
mtd3: 002a0000 00020000 "kernel1"
mtd4: 01760000 00020000 "ubi"
mtd5: 002a0000 00020000 "kernel2"
mtd6: 01760000 00020000 "rootfs2"
mtd7: 04a00000 00020000 "syscfg"
mtd8: 00140000 00020000 "unused"
should i past that second code mentioned with the fw_printenv?
Not needed right now. And you need to clean up the fw_printenv command to remove MAC if you care about your data.