So, after doing a little bit of research, I may have found a solution...
Just to make it clear, I don't own any of the same hardware, and have not done any of this myself, so I probably won't be of much use should anything
go wrong, or if anything is different than as written. Proceed with caution.
I'm putting a couple of links at the end of this, so please look through them first, and see if they look like they might be useful. As a last resort,
the following steps should allow you to downgrade the firmware to a version that will allow access to the serial port(s). Please look through the
other links first, though, as the information therein may work, and would probably be less of a headache.
First, you'll need to download 'mobilepartnerforwindows.zip' from
here, unless
you're on Windows 8, then just Google the file name and get a newer version; any version should work.
Unzip that, install the .exe file inside of it (it appears to be clean; I checked), then go to C:program fileshuaweidriversx86 (or x64, if you're on
64 bit). Copy that entire x86/64 directory to C:tempx86 (create it if it doesn't exist).
In that directory, find 'ewser2k.inf'and open it with Notepad or Notepad++ or similar. Search for the section '[QcomSerialPort]', and below it, add
the following:
%QcomDevice01% = QportInstall01, USBVID_12d1&PID_143E&MI_02
%QcomDevice01% = QportInstall01, USBVID_12d1&PID_1442&MI_00
%QcomDevice00% = QportInstall01, USBVID_12d1&PID_1442&MI_01
%QcomDevice01% = QportInstall01, USBVID_12d1&PID_1448&MI_01
Next, download the firmware file from
here, and extract it with 7zip,
but don't install it just yet (this .exe appears clean as well, FYI).
Now, plug in the stick, go to "http://192.168.1.1/" and make sure it shows some connection info, then go to
"http://192.168.1.1/html/switchProjectMode.html" (case-sensitive). It should go offline and windows should start looking for new drivers. When it
can't find any and asks you for a location, point it to the C:tempx86 directory, and if the correct edits were made to 'ewser2k.inf', it should see
the 3 drivers there. After it installs them for 'Huwaei device' or whatever it's called, it will look for drivers for something like
'a65bd63245.b65d654f'. Point it to the same x86 folder, and let it install the same drivers again. Now, back on 192.168.1.1 (I think), you ought to
see some COM ports. Don't remove the stick at this point, or you'll have to start over.
For the next part, you have 2 options:
1) Download '3G Modem Mode Switcher' from
here, extract and isntall, then
click the "1st button on the left" a few times. I haven't installed it, but I believe it is in Cyrillic, and that is the only explanation given
lol.
2) Download Tera Term (ttermpro.exe) from
here and install it (again, looks clean). Open it up,
and point it to the device manager COM port with the description "user gui". Send the following AT command:
AT^2DIAG=0
...And it should give you an 'OK' reply, confirming that you're connected correctly. That AT command will switch it to the default modem mode instead
of the hilink mode, but should you need to switch it back, you would use the following AT command:
AT^2DIAG=119
Next, remove the stick from your PC/laptop, and re-insert it. If it shows COM ports and you're able to re-connect through Tera Term, everything's
good. If so, install the firmware that you downloaded earlier (there should be a .exe in the zip file you downloaded). During the installation, if it
looks for drivers, point it again to your C:tempx86 directory. Once it completes, it should be back on a previous firmware, and you should have access
to the serial port(s)...
source
OTHER LINKS (read these first):
www.riecktron.co.za...
ubuntuforums.org...
www.geekzone.co.nz...
mybroadband.co.za...#
post10250878
Good luck!
Edit: Some of the above links may show different model names (I can't remember for sure; looked at a lot of things lol). If so, don't dismiss the
information just because of that. Even if those sites reference a different model, the discussions that led me to them were about the model you have,
and claimed the information is also valid for your model.
edit on 4/10/2015 by AdmireTheDistance because: (no reason given)