Hi @nebbia88, yes I'm aware that topic is on tftp recover mode from uboot. I was just assuming that the uboot firmware check method would be the same used in the web gui.
After some more research last night, I don't think the product id and version check is new. It looks like that have been there for a while now and OpenWRT was already handled it.
I found this TP Link firmware checker/editor tool and checked the new TP-Link 140120 firmware with the OpenWRT version and they are the same.
nebbia88 wrote: King0fK0ng wrote:
So from this thread (https://forum.openwrt.org/viewtopic.php … 83#p222183) I believe the new firmware is doing a product id and product version check.
if ( (original_product_id == recovery_product_id)
&& (original_product_ver== recovery_product_ver) )
that topic is about tftp recovery mode from uboot, and has nothing to do with the check during firmware upgrade from web GUI
I also re-read your post above about the web gui not accepting the TP-Link 140120 firmware with the U-Boot trimmed out.
I guess it would help if someone with serial console access to upgrade to the 140120 firmware and maybe see if the console would give us an hints. Maybe access to the web gui files to see the check is being performed?
I have another 703n router with pepe2k recovery firmware. I'm wondering if it's possible trim out the Uboot from the 140120 firmware and load it on my 703n router with pepe2k recovery firmware? That way I can use the netconsole to see what's going on.
Also, not sure if this 140120 firmware include the tftp recover mode in uboot mentioned in the other thread. I tried plugging in the router with the reset button pushed and wiresharked the connection, but didnt see any tftp packets. I'll be honest though, not sure if I did it right.
For the record, I don't have the solder skills to add a serial console to the 703n (those darn tx/rx pads are super tiny and I lifted the contacts attempting). I've totally messed up two 703n attempting
(Last edited by King0fK0ng on 7 Jun 2014, 18:44)