To get to the ECI's GUI you need to open it, solder some pins to the board and then follow the guide here.
TBH, if you have read all the posts here and still don't follow what to do, I would respectfully suggest that this is not an avenue that you should be exploring.
At some time, perhaps all the relevant docs for unlocking the ECI VDSL2 modem (via the UART port) could be placed together in one place. Maybe the Kitz wiki?
Burakkucat made a fascinating discovery in an Openreach tarball of GPL'ed firmware source code for another ECI VDSL2 modem. This firmware was built by the Taiwanese company,
Arcadyan. [1]
It is not even clear that these
Arcadyan modems have ever reached our shores. However, the GPL'ed source code for them is still interesting because it includes a small section of code for the
TR069 framework for remote management. [2]
In-house, BT calls this framework
btagent. It comes in two parts. One part, the daemon, a.k.a. the network server, runs on the modem itself. The second part, the client, runs on a host PC. The framework has functions for remotely pushing firmware upgrades onto modems, for monitoring line characteristics and connection quality, and functions for getting and setting the real-time parameters of the modem, etc, etc.
btagent is found in much the same form in all recent models of BT Home Hub, as well as the current models of VDSL2 modem from BT Openreach - the
Huawei HG612 and the
ECI B-Focus.
The option for pushing a new firmware onto the ECI is perhaps the most interesting, since it could be used to non-invasively unlock it. However, there is a security obstacle preventing that which may never be overcome.
btagent uses 2048-bit PKI cryptography for authentication. Before a new (unlocked) firmware could be uploaded to the ECI, or to the Huawei, or the HomeHubs,
using the btagent daemon, the corresponding private key has to be discovered first. ... And for that.. don't wait up!
cheers, a
[1]
http://www.openreach.co.uk/orpg/home/products/super-fastfibreaccess/super-fastfibreaccess/landrgnu.do[2]
http://www.broadband-forum.org/technical/download/TR-069_Amendment-4.pdf