Modem was work well only with Билайн sim (100% work)
you dont' inform me about any risk
-
Unfortunately, but DC-unlocker do not repair damaged modems. There is always a risk when flashing different firmware into modem from different operator.Originally posted by cr_8e View PostLeave a comment:
-
Only 1 modem, selected to get information
Getting information from the device...OK
Model: MF667
Application port: COM82
Diagnostic port: COM80
IMEI: 359905018453511
Firmware Version: BD_HDMF667V1.0.0B01
Build Date: Dec 12 201309:48:09
User: 11XXXXXX
User credits: 69000
27.08.2014 15:35:15 Starting to write device...
Process: Normal Update
Verifying port mode: Port COM80
Validating file...
File to write: E:\1\_MODEM\ZTE\MF_667_new\Ucell_BD_MF667V1.0.0B01 .dgtk
File version: BD_MF667V1.0.0B01
Looking for attached port...
Device found
Start prepare
Changing modem to download mode...
Device DISCONNECT detected
Type: @usb.inf,%usb\composite.devicedesc%;Составное USB устройство
VidPid: VID_19D2&PID_0016
Instance id: 6&30639749&1&3
Device CONNECT detected
Type: @usb.inf,%usb\composite.devicedesc%;Составное USB устройство
VidPid: VID_19D2&PID_0016
Instance id: 6&30639749&1&3
Searching ports in diagnostic mode by VID_19D2
Reading settings...
Changing modem to download mode...
Device DISCONNECT detected
Type: @usb.inf,%usb\composite.devicedesc%;Составное USB устройство
VidPid: VID_19D2&PID_0016
Instance id: 6&30639749&1&3
Device CONNECT detected
Type: @usb.inf,%usb\composite.devicedesc%;Составное USB устройство
VidPid: VID_19D2&PID_0016
Instance id: 6&30639749&1&3
Searching ports in download mode by VID_19D2
Device found
Device in download mode
Preparing to write...
Writing armprg.bin...
Loading drivers...
Drivers loaded
Writing partition table...
Writing dbl.mbn...
Writing fsbl.mbn...
Writing osbl.mbn...
Writing amss.mbn...
Writing dsp1.mbn...
Writing dsp2.mbn...
Writing cefs.mbn...
Writing cefs_apps.mbn...
Changing modem to diagnostic mode...
Device DISCONNECT detected
Type: @usb.inf,%usb\composite.devicedesc%;Составное USB устройство
VidPid: VID_19D2&PID_0016
Instance id: 6&30639749&1&3
Device CONNECT detected
Type: @usb.inf,%usb\composite.devicedesc%;Составное USB устройство
VidPid: VID_19D2&PID_0016
Instance id: 6&30639749&1&3
Searching ports in diagnostic mode by VID_19D2
Error setting modem
Detecting modem mode...
Modem in download mode
Searching ports in diagnostic mode by VID_19D2
Device DISCONNECT detected
Type: @usb.inf,%usb\composite.devicedesc%;Составное USB устройство
VidPid: VID_19D2&PID_0016
Instance id: 6&30639749&1&3
Device CONNECT detected
Type: @usb.inf,%usb\composite.devicedesc%;Составное USB устройство
VidPid: VID_19D2&PID_0016
Instance id: 6&30639749&1&3
27.08.2014 15:46:58 Writing device finished with ERROR
modem is damaged now
soft - ZTEQualcommWriter_V15.exe
fw - Ucell_BD_MF667V1.0.0B01.dgtk
Help me plz!
Leave a comment:
-
Repeating unlock for same device won't require more credits.Originally posted by kebon15 View PostLeave a comment:
-
Please refer to my log, i cannot unlock the modem and my credit already cutted down.
Please advise us.
You do not have permission to view this gallery.
This gallery has 2 photos.Leave a comment:
-
Reflash error and half dead modem.
I have just kill few of mine mf667. I don't know what is going wrong because few days ago I have no any troubles with mf667 reflashing. Modem stays in download mode. Do anybody know why is that?
Log
Code:Only 1 modem, selected to get information Getting information from the device...OK Model: MF667 Application port: COM37 Diagnostic port: COM39 IMEI: 359905019748570 Firmware Version: BD_HDMF667V1.0.0B01 Build Date: Dec 12 201309:48:09 User: 01322C90 User credits: 1 17.07.2014 23:05:45 Starting to write device... Process: Normal Update Verifying port mode: Port COM39 Validating file... File to write: C:\Users\Profi\Downloads\Tele2_BD_MF667V1.0.2B02.dgtk File version: BD_MF667V1.0.2B02 Looking for attached port... Device found Start prepare Changing modem to download mode... Device DISCONNECT detected Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device VidPid: VID_19D2&PID_0016 Instance id: 7&3de3839&0&3 Device CONNECT detected Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device VidPid: VID_19D2&PID_0016 Instance id: 7&3de3839&0&3 Searching ports in diagnostic mode by VID_19D2 Reading settings... Changing modem to download mode... Device DISCONNECT detected Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device VidPid: VID_19D2&PID_0016 Instance id: 7&3de3839&0&3 Device CONNECT detected Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device VidPid: VID_19D2&PID_0016 Instance id: 7&3de3839&0&3 Searching ports in download mode by VID_19D2 Device found Device in download mode Preparing to write... Writing armprg.bin... Loading drivers... Drivers loaded Writing partition table... Writing dbl.mbn... Writing fsbl.mbn... Writing osbl.mbn... Writing amss.mbn... Writing dsp1.mbn... Writing dsp2.mbn... Writing cefs.mbn... Writing cefs_apps.mbn... Changing modem to diagnostic mode... Device DISCONNECT detected Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device VidPid: VID_19D2&PID_0016 Instance id: 7&3de3839&0&3 Device CONNECT detected Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device VidPid: VID_19D2&PID_0016 Instance id: 7&3de3839&0&3 Searching ports in diagnostic mode by VID_19D2 Error setting modem Detecting modem mode... Modem in download mode Searching ports in diagnostic mode by VID_19D2 Device DISCONNECT detected Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device VidPid: VID_19D2&PID_0016 Instance id: 7&3de3839&0&3 Device CONNECT detected Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device VidPid: VID_19D2&PID_0016 Instance id: 7&3de3839&0&3 17.07.2014 23:12:20 Writing device finished with ERROR
Leave a comment:
Leave a comment: