Posted: Fri Nov 19, 2021 16:07 Post subject: TPLINK Archer C9 v5 unlock the protection
I know there is a protection in the v5.
Wonder if it is possible to unlock the protection by write a V4's mtd0(CFE) to V5's mtd0?
they have same SoC, I think mybe it work..
I have the serial console, considering trying... is it possible?
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Fri Nov 19, 2021 18:03 Post subject:
The C9 v5 uses a bootloader to load an image which contains a second bootloader. It's not about unlocking anything. It's about how to work with the way the flash is laid out. AFAIK, the serial only sees the Broadcom CFE, and not the underlying bootloader. I don't know if BrainSlayer has made any progress on the v5 he has in hand, but for now it's a dead horse until he finds the mood and time to work on it. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
The C9 v5 uses a bootloader to load an image which contains a second bootloader. It's not about unlocking anything. It's about how to work with the way the flash is laid out. AFAIK, the serial only sees the Broadcom CFE, and not the underlying bootloader. I don't know if BrainSlayer has made any progress on the v5 he has in hand, but for now it's a dead horse until he finds the mood and time to work on it.
thanks for your reply.
I have anaylized the boot log.
It seems the second CFE resides in the rootfs partition(flash0.os which is mtd3 in linux).
So I think the first CFE is in the boot partition(mtd0).
The first CFE will load second CFE. If replace the first CFE(and replace the rootfs partition with the dd-wrt firmware) maybe boot the dd-wrt firmware.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Sat Nov 20, 2021 18:53 Post subject:
This is information the developer *already* has, as he has a device in hand. And seeing the boot log clarifies things for me as described by BrainSlayer. Just realized the support topic is locked, hence your opening a new topic to discuss things already known, to push for support. It's not going to happen until BrainSlayer decides to do it, or someone submits the patches to port the device... _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Mon Nov 22, 2021 16:47 Post subject:
I wasn't saying that he refused input on porting this from the community. But last I knew, this port wasn't going to happen, and then we were discussing the US-only v4 and he alluded to the possibility of porting it. I still have to get him a flash dump of the v4 on my bench. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net