A warning regarding the Ericsson H5321gw
Bjørn Mork
bjorn at mork.no
Fri May 31 05:23:09 PDT 2013
Just wanted to share my experiences so others don't have repeat my
mistakes...
I recently bought a H5321gw on eBay, hoping that I would be able to
update the firmware so I could test the NCM/MBIM compatible function.
AFAIK, this is the only commercially available device implementing such
a function.
But the device fails the firmware utility revision tests, and I don't
think it's easily worked around. I initially got this error:
"EcpUpdateContainerIsValidForDevice - Device CID 177 is not supported"
which I was able to work around by hex editing the update utility. But
I only ended up with a failing RSA signature check instead. And I
assume this signature is robust enough that I cannot just fix it with an
editor, so I gave up right there.
Based on the initial error, I assume the problem is related to the
Individualization line below. This should probably have been 189.189 for
a production device (got the AT*EEVINFO command from the firmware update
utility):
AT*EEVINFO=99
*EEVINFO:
Model.................... H5321gw
IMEI Data................ 004401700885235
SVN...................... 01
Serial Number............ C37003W0YH
Product Number........... KRD 131 21/141
Revision................. R1B/1
FW Product............... CXC 173 1944/1
FW Version............... R1C08
FW Build Date/Time....... Oct 1 2011 18:09:28
Cust. Product............ CXC 173 1938/14 Page:
Cust. Version............ R1C01
Customization Descr...... TOSHIBA
Format................... 1
Base Product Number...... 1/KRD 131 21/1
Base Product Revision.... R1G
SIMLock Deployment....... 0.0
SIMLock Description...... Unlocked
SIMLock Product.......... CXC 173 0839/01
SIMLock Revision......... R1F
Model Description........ Ericsson H5321gw for TOSHIBA Mobile Broadband Module
Vendor Name.............. TOSHIBA
GD Default Product....... CXC 173 1940/1
GD Default Revision...... RNXX
HW Customization Product. CXC 173 2606/01
HW Customization Revision RNYY
HW Customization Index... 01
Config. Set Product...... CXP 901 8699/1
Config. Set Revision..... R1C09
Network Customization.... Telenor;24201
Customization State...... 0
NDFU Page................ 1
Configuration Product.... CXP 901 8700/1
Configuration Revision... R1C09
Protocol FW Product...... CXC 173 1944/1
Protocol FW Version...... R1C08
Application FW Product... CXC 173 1945/1
Application FW Version... R1C09
Network List Product..... CXC 173 1116/1
Network List Revision.... R1D
Individualization........ 177.177
Domain................... 3.0
Upgrade State............ 1
Volume info.............. 54 MB total / 81.2% free
OK
Anyway, the picture in the ad clearly showed "PROTOTYPE NOT TYPE
APPROVED", so I knew exactly what I bought and am not too surprised.
And the module works just fine as a cdc_ncm device. So there is nothing
to complain about.
Just wanted to let you all known before anyone else get the same bright
idea.
Bjørn
More information about the libmbim-devel
mailing list