- #Unlock modem huawei e1750 telkomsel flash drivers#
- #Unlock modem huawei e1750 telkomsel flash update#
- #Unlock modem huawei e1750 telkomsel flash driver#
- #Unlock modem huawei e1750 telkomsel flash archive#
Sorry, dc-unlocker can not help with repairing modems.MODEM TELKOMSEL FLASH HUAWEI E173 DRIVER (modem_telkomsel_5740.zip)Ĭontact HUAWEI service, or just upgrade to step 5. So basically it behaves as if there wouldn't be a SIM card inserted and unfortunately flashing of different FW is blocked. When I try to flash another FW such as the one you linked it can detect the modem, I enter the flash code generated for my IMEI, then I can see by the LED flashing that the modem enters the flashing mode, but then it ends up in the "Backup User's Data Start, Please Wait." state and never gets any further (after some time the "Update Failure" message appears). That never happens with the one with VIETTEL it seems to be somewhat locked to VIETTEL firmware flashing.
#Unlock modem huawei e1750 telkomsel flash drivers#
Mobile Partner ends up in loop detecting device.Īs I wrote, I can compare with another E1750 (non-VIETTEL FW) and that works fine either in Windows directly or via Mobile Partner app - so drivers shouldn't be an issue.Īlso there's one visible difference between those two: when I plug in the VIETTEL one its LED flashes only green, but the non-VIETTEL starts with green but once it finds a network it switches to blue (it can keep flashing green only if I didn't insert SIM card). Windows: OS sees the modem device, but connect attempts fail (Error 678 The remote computer did not respond). Flashing with (non-VIETTEL) 11.126.13.00.00 is still impossible (hangs as it did before) so practically no difference.With unlocked modem you need to use not customized software and enter your new provider connection settings (APN, username and others). I still can't connect with my SIM and still can't do anything useful with the device. I even managed to get the device unlocked by DC Unlocker then:ĭashboard version : TID14.01.10.8.0.21.208.CZ
#Unlock modem huawei e1750 telkomsel flash archive#
I managed to downgrade to 11.126.11.02.439 (VIETTEL) from the following archive I found: Try to downgrade your firmware and try again. i know I probably did a very stupid thing, but please help.!!!! :'(Sorry, DC-Unlocker can not unlock modems with this firmware version, so we can not help you here. i know I probably did a very stupid thing, but please help.!!!! :'( Wrong codes entered : 0 (unlock attempts left : 10) SIM Lock status : Locked (customized firmware)
#Unlock modem huawei e1750 telkomsel flash update#
firmware.īut strangely (!!) when i try to update with the viettel firmware file, the update gets successful and the port gets detected within 1 second. after starting to update, when it searches for the port it is connected to it finds nothing. So i tried to go back to my old firmware and download that from net. so i could not connect to internet with it. and more problem is, now it is not getting detected by mobile partner software. (i'm using windows xp pro service pack 3). then i tried to update the firmware again and it worked fine this time.īut now the problem is, this device is detected as 'network card', previously (before updating) it was getting detected as '3g usb data card'. Then the device got detected and drivers were installed (dont know if those were right drivers or not). then i installed my Mobile Partner dashboard again.
thinking it is updated firmware for 'my device' and tried to update my device.Īt the end of the update when the device was re-detected by my system i got error (driver error).
My mistake without knowing and reading much into it I downloaded a firmware of viettel E1750 version: 11.126.13.00.439 from here ( ). and google search redirected me to this thread. I was having problem with my internet connection with my Huawei E1750 3G Data card (firmware 11.126.13.00.00) & thought updating with latest firmware will solve my problem. Though the problem is similar to the that, but still explaining. I'm having exactly same problem like mag01 (at the end of the thread below).
0 kommentar(er)
