xt1662 imei repair problem - GSM-Forum

Tahirasif31 · 05-12-2019, 12:08

logs say imei repair done but phone is still on invalid imei
Selected connection metod: Meta Connection
Exe version: Avengers Box MTK 0.6.1
Selected phone: XT1662
Action : IMEI REPAIR.
IMEI[1] for write : 357556456465468
IMEI[2] for write : 356778453465687
Scanning for presents meta ports...
Phone must be off with battery inside.
Please insert USB cable now...
In some phones need to keep VOL- button untill inserting USB cable.
[28]Detected: MediaTek USB Port (COM28)
\\?\usb#vid_0e8d&pid_0003#6&3af1eaa2&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Starting META mode, wait...
Restarting to meta,wait....
If drivers missing, please install CDC drivers.
This can take up to 5 min on slow phones.
If take too long, check device manager for drivers.
[12]META Port Detected: Android Gadget VCOM Driver (COM12)
USB\VID_17EF&PID_74ED&MI_02\7&2BD703A4&0&0002
Start sync target, waiting responce.....
[AP]BaseBand CPU : mt6755,S01
Rebooting to meta, wait....
[META]BaseBand CPU : MT6755
[META]SW_VER : XT1662.N.V11
[META]HW_VER : LENOVO6755_66_N_HW
Meta mode conected ok, start reading phone....
IMEI to repair: [1] 357556456465468
IMEI to repair: [2] 356778453465687
Clean Boot flag ok.
[0]All done.

**orbita** · 05-12-2019, 12:39

In mtk phone imei null can be caused by

1.Damaged firmware
2.Damaged hardware
3.Damaged security
4.Erased imei.

If phone have erased imei, you can write imei back, if phone have other problem, need to solve first problem what cause null imei(after usually imei come back if was not "..repaired" before)

Tahirasif31 · 05-12-2019, 12:46

xt1662 imei erased after factory reset
factory reset is the cause of erase imei

**orbita** · 05-12-2019, 16:27

Quote:

Originally Posted by Tahirasif31

xt1662 imei erased after factory reset
factory reset is the cause of erase imei

This even teoreticly is not posible.
In this phones dinamic imei not anymore in userdata it's inside special partition called nvdata.
Static imei is hold in nvram partition.

And this partitions can be erased only if you will erase it manually.
After factory reset even teoreticly is not posible to erase this 2 partitions.

Tahirasif31 · 05-13-2019, 12:44

but this phone is totally ok from hardware.. baseband is also ok.. avengers says imei write ok but still on invalid imei... i thought i cant write nvdata from avengers..

**orbita** · 05-14-2019, 07:23

Instead of check what problem have phone, you started to spam with multiple threads.

In second thread what you started, no idea why, you post this log.

Code:

Selected connection metod: Meta Connection
 Exe version: Avengers Box MTK 0.6.0
 Selected phone: ELBRUS
 Action : IMEI REPAIR.
 IMEI[1] for write : 358217071665176
 IMEI[2] for write : 358217071717159
 Scanning for presents meta ports...
 Phone must be off with battery inside. 
 Please insert USB cable now...
 In some phones need to keep VOL- button untill inserting USB cable.
 [5]Detected: MTK USB Port (COM5) 
 \\?\usb#vid_0e8d&pid_0003#5&28b2efbf&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 
 Starting META mode, wait...
 Restarting to meta,wait....
 If drivers missing, please install CDC drivers.
 This can take up to 5 min on slow phones.
 If take too long, check device manager for drivers.
 [66]META Port Detected: %VCOM% (COM66) 
 USB\VID_17EF&PID_74ED&MI_02\6&2BD703A4&0&0002 
 Start sync target, waiting responce.....
 [AP]BaseBand CPU : mt6755,S01
 Rebooting to meta, wait....
 [META]BaseBand CPU : MT6755
 [META]SW_VER : KUNGFU.ROW.N.V13
 [META]HW_VER : LENOVO6755_66_N_HW
 Meta mode conected ok, start reading phone....
 IMEI to repair: [1] 358217071665176
 Phone imei[1] : 358217071665176
 IMEI to repair: [2] 358217071717159
 Phone imei[2] : 358217071717159
 Clean Boot flag ok. 
 [0]All done.

here you can see phone imei exists and cause of null imei is other.

Will tell you again, for phone really not matter what you think.
If problem exists, you must solve this problem, and really not matter what you think.
You can do what you want, really can't help you more.
You can continue with "i'am think in phone is all ok" or you can solve problem and have repaired phone.
Finally is your choise.

**orbita** · 05-14-2019, 07:39

Also...from what i'am see, you not performed first basic check what need to do in this case.

Try to read simlock info in meta mode and see what display exe.
Damaged security is also a cause of null imei.

Tahirasif31 · 05-14-2019, 10:30

Quote:

Originally Posted by orbita

Also...from what i'am see, you not performed first basic check what need to do in this case.

Try to read simlock info in meta mode and see what display exe.
Damaged security is also a cause of null imei.

i will check and post the report... thanks for still helping me

Tahirasif31 · 05-14-2019, 10:54

Quote:

Originally Posted by orbita

Instead of check what problem have phone, you started to spam with multiple threads.

In second thread what you started, no idea why, you post this log.

Code:

Selected connection metod: Meta Connection
 Exe version: Avengers Box MTK 0.6.0
 Selected phone: ELBRUS
 Action : IMEI REPAIR.
 IMEI[1] for write : 358217071665176
 IMEI[2] for write : 358217071717159
 Scanning for presents meta ports...
 Phone must be off with battery inside. 
 Please insert USB cable now...
 In some phones need to keep VOL- button untill inserting USB cable.
 [5]Detected: MTK USB Port (COM5) 
 \\?\usb#vid_0e8d&pid_0003#5&28b2efbf&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 
 Starting META mode, wait...
 Restarting to meta,wait....
 If drivers missing, please install CDC drivers.
 This can take up to 5 min on slow phones.
 If take too long, check device manager for drivers.
 [66]META Port Detected: %VCOM% (COM66) 
 USB\VID_17EF&PID_74ED&MI_02\6&2BD703A4&0&0002 
 Start sync target, waiting responce.....
 [AP]BaseBand CPU : mt6755,S01
 Rebooting to meta, wait....
 [META]BaseBand CPU : MT6755
 [META]SW_VER : KUNGFU.ROW.N.V13
 [META]HW_VER : LENOVO6755_66_N_HW
 Meta mode conected ok, start reading phone....
 IMEI to repair: [1] 358217071665176
 Phone imei[1] : 358217071665176
 IMEI to repair: [2] 358217071717159
 Phone imei[2] : 358217071717159
 Clean Boot flag ok. 
 [0]All done.

here you can see phone imei exists and cause of null imei is other.

Will tell you again, for phone really not matter what you think.
If problem exists, you must solve this problem, and really not matter what you think.
You can do what you want, really can't help you more.
You can continue with "i'am think in phone is all ok" or you can solve problem and have repaired phone.
Finally is your choise.

the other thread is not belong to me.. which u are talking about

Tahirasif31 · 05-14-2019, 10:56

Quote:

Originally Posted by orbita

Also...from what i'am see, you not performed first basic check what need to do in this case.

Try to read simlock info in meta mode and see what display exe.
Damaged security is also a cause of null imei.

orbita can u shere the sec_nvram.bin file for this phone ! i thought this is one of the last solution for this !

**orbita** · 05-14-2019, 12:42

Your solution can be damaged secuity(i'am already sayed how to check this)
Can be firmware, or can be hardware.
What meen sec_nvram.bin i'am not know

and i'am not have this file.
We make very long thread for easy to solve problem, not need to think here if is ok or not, simple need to check this parts.

05-12-2019, 12:08	#1 (permalink)
Tahirasif31 Freak Poster Join Date: Dec 2015 Posts: 114 Member: 2495033 Status: Offline Thanks Meter: 21	xt1662 imei repair problem logs say imei repair done but phone is still on invalid imei Selected connection metod: Meta Connection Exe version: Avengers Box MTK 0.6.1 Selected phone: XT1662 Action : IMEI REPAIR. IMEI[1] for write : 357556456465468 IMEI[2] for write : 356778453465687 Scanning for presents meta ports... Phone must be off with battery inside. Please insert USB cable now... In some phones need to keep VOL- button untill inserting USB cable. [28]Detected: MediaTek USB Port (COM28) \\?\usb#vid_0e8d&pid_0003#6&3af1eaa2&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed} Starting META mode, wait... Restarting to meta,wait.... If drivers missing, please install CDC drivers. This can take up to 5 min on slow phones. If take too long, check device manager for drivers. [12]META Port Detected: Android Gadget VCOM Driver (COM12) USB\VID_17EF&PID_74ED&MI_02\7&2BD703A4&0&0002 Start sync target, waiting responce..... [AP]BaseBand CPU : mt6755,S01 Rebooting to meta, wait.... [META]BaseBand CPU : MT6755 [META]SW_VER : XT1662.N.V11 [META]HW_VER : LENOVO6755_66_N_HW Meta mode conected ok, start reading phone.... IMEI to repair: [1] 357556456465468 IMEI to repair: [2] 356778453465687 Clean Boot flag ok. [0]All done.

05-12-2019, 12:46	#3 (permalink)
Tahirasif31 Freak Poster Join Date: Dec 2015 Posts: 114 Member: 2495033 Status: Offline Thanks Meter: 21	xt1662 imei erased xt1662 imei erased after factory reset factory reset is the cause of erase imei

05-12-2019, 12:39	#2 (permalink)
orbita Product Manager Join Date: Apr 2002 Location: nckDongle Posts: 13,325 Member: 11170 Status: Offline Sonork: 1603694 Thanks Meter: 6,944	In mtk phone imei null can be caused by 1.Damaged firmware 2.Damaged hardware 3.Damaged security 4.Erased imei. If phone have erased imei, you can write imei back, if phone have other problem, need to solve first problem what cause null imei(after usually imei come back if was not "..repaired" before)

05-13-2019, 12:44	#5 (permalink)
Tahirasif31 Freak Poster Join Date: Dec 2015 Posts: 114 Member: 2495033 Status: Offline Thanks Meter: 21	but this phone is totally ok from hardware.. baseband is also ok.. avengers says imei write ok but still on invalid imei... i thought i cant write nvdata from avengers..

05-14-2019, 07:39	#7 (permalink)
orbita Product Manager Join Date: Apr 2002 Location: nckDongle Posts: 13,325 Member: 11170 Status: Offline Sonork: 1603694 Thanks Meter: 6,944	Also...from what i'am see, you not performed first basic check what need to do in this case. Try to read simlock info in meta mode and see what display exe. Damaged security is also a cause of null imei.

05-14-2019, 12:42	#11 (permalink)
orbita Product Manager Join Date: Apr 2002 Location: nckDongle Posts: 13,325 Member: 11170 Status: Offline Sonork: 1603694 Thanks Meter: 6,944	Your solution can be damaged secuity(i'am already sayed how to check this) Can be firmware, or can be hardware. What meen sec_nvram.bin i'am not know and i'am not have this file. We make very long thread for easy to solve problem, not need to think here if is ok or not, simple need to check this parts.