Develop Bugs

|SOLVED]IMEI pROBLEM|for]any mtk phone

AsslamoAlaikum to Qmobile A2 users,
After flashing my ICS themed custom rom*THUNDERSTORM1* some users of A2 v2 complain about IMEI problem so here i am telling u the easiest method to resolve this issue.(others can also try on their own risk]
I m not responsible for any damadge u done to ur phone
Instructions for restoring IMEI
1. Download the program MTK Droid Root & Tools
2. Go with your phone to the program Root Explorer
3. We put a resolution on the r / o, and go through the path data / nvram / ​​md md folder and delete the folder NVRAM.
4. We go into the settings on the phone - application - development and put a check on USB debugging
5. Write off your IMEI in a notebook or anywhere else.
6. Turning on the phone,go into the program MTK Droid Root & Tools, and then the program searches your phone
7. click on Change IMEI and type the numbers you wrote down (That is your IMEI).
8 done :victory:
9 now reboot nd if changes doesnt appears then u hv to flash ur stock system.img via sp flash tool nd after flashing u will get ur networks back
10 HIT THE THANKS BAR
<edit>
This method can be used for other mtk phones!

Invalid IMEI
qmobilea2 said:
AsslamoAlaikum to Qmobile A2 users,
After flashing my ICS themed custom rom*THUNDERSTORM1* some users of A2 v2 complain about IMEI problem so here i am telling u the easiest method to resolve this issue.(others can also try on their own risk]
I m not responsible for any damadge u done to ur phone
Instructions for restoring IMEI
1. Download the program MTK Droid Root & Tools
2. Go with your phone to the program Root Explorer
3. We put a resolution on the r / o, and go through the path data / nvram / ​​md md folder and delete the folder NVRAM.
4. We go into the settings on the phone - application - development and put a check on USB debugging
5. Write off your IMEI in a notebook or anywhere else.
6. Turning on the phone,go into the program MTK Droid Root & Tools, and then the program searches your phone
7. click on Change IMEI and type the numbers you wrote down (That is your IMEI).
8 done :victory:
9 now reboot nd if changes doesnt appears then u hv to flash ur stock system.img via sp flash tool nd after flashing u will get ur networks back
10 HIT THE THANKS BAR
<edit>
This method can be used for other mtk phones!
Click to expand...
Click to collapse
Thanks bro but i have tried all options but my Noir A2 still showing invalid IMEI. I will try this method and I hope to get my phone working with the sims. Thanks

Help
Hi,
Can you please guide me how to flash system.img (Noir A2). I m new to all of these terms though i know how to root a mob using Sp flash (CWM.img).
Can you please guide me re system.img because i have bricked my Noir A2 and want it to be back in a state where I can use it for calling messaging purposes.
Looking forward for your kind reply.
Bilal

Thank you, deleting NVRAM folder and creating IMEI worked for me
I did this in Custom rom Thunderstorm

Bro come to our page, there u get all ur issues fix
Sent from my A2 using xda app-developers app

don't understand a couple of the step or at least no precisely
qmobilea2 said:
AsslamoAlaikum to Qmobile A2 users,
After flashing my ICS themed custom rom*THUNDERSTORM1* some users of A2 v2 complain about IMEI problem so here i am telling u the easiest method to resolve this issue.(others can also try on their own risk]
I m not responsible for any damadge u done to ur phone
3. We put a resolution on the r / o, and go through the path data / nvram / ​​md md folder and delete the folder NVRAM.
?
Click to expand...
Click to collapse

aqeel1978 said:
Thanks bro but i have tried all options but my Noir A2 still showing invalid IMEI. I will try this method and I hope to get my phone working with the sims. Thanks
Click to expand...
Click to collapse
that imei will missing after do factory reset , any solution?

Best Working Solution
Mahn I just love you
You just saved me.
I've tried every possible solution but your's worked for me.
I had lost my lenovo a3300 hv 's imei when flashing official rom, but now its working fine.
agian Thakns a Lot !!!!!!!

Cannot connect to mobile network???

Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.

First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...

Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore

jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
I tried a simple way which is format everything and flash another ROM but the problem remains.

TRS_80 said:
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
Click to expand...
Click to collapse
I don't know that we are in the same situation since at home I often got a good signal and this happened to me only since yesterday.

jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.

Dan Law 001 said:
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Click to expand...
Click to collapse
Results..??
Sent from my GT-I9001 using xda premium

jabrif said:
Results..??
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I need to get the firmware first... since I already passed the download quota for today... need to wait until tomorrow...

Mmm... I heard that you mentioned clearing the EFS in your given procedure, but I do not think that I modified that folder... However, about few days ago, since I want to gain better control on the volume on my headphone remotes, I did modify the file called Generic.kl in system/usr/keylayout, but I restore it after since it didn't work. However, I don't think that this modification will trigger something in the efs folder since it has different directory. By the way, I did some research online and they say that the efs contains information about the carrier on the phone, so will there's a greater chance that the problem is caused by the possible modification on the efs than any other factor and will there also something else that possibly trigger the similar effects?
Sent from my GT-N7100 using xda premium

Still nothing

imei null on n7100 4.4.2

My phone was working fine before battery drained and it get switched off. But when i restarted the phone imei was null.
I have efs backup of 4.3 ( mj9 modem) but now i am on 4.4.2 . I tried restoring it but did not worked .
any help please..

sachinwadhwa46 said:
My phone was working fine before battery drained and it get switched off. But when i restarted the phone imei was null.
I have efs backup of 4.3 ( mj9 modem) but now i am on 4.4.2 . I tried restoring it but did not worked .
any help please..
Click to expand...
Click to collapse
try what i did here buddy. . post #3512
http://forum.xda-developers.com/showthread.php?p=57661153#post57661153
do it at tour own risk. goodluck!

edong23 said:
try what i did here buddy. . post #3512
http://forum.xda-developers.com/showthread.php?p=57661153#post57661153
do it at tour own risk. goodluck!
Click to expand...
Click to collapse
Thank you for your reply. Please help me to do this step wise

sachinwadhwa46 said:
Thank you for your reply. Please help me to do this step wise
Click to expand...
Click to collapse
this method works for me, but I am not sure if it will work for you. I have to warn you that I am not a dev, I am just a basic android user. I came up with this idea out of desperation because my phone cannot receive and make calls for almost 4 days. so do this at your own risk.
note:
* make sure your phone is rooted.
* make a copy of your old efs backup and all your important files in your computer or in a flash drive.
1. copy and write on a piece of paper your imei # which will be found at the back of your phone. it is 15 digit
2. copy your efs.img (not the folder that contain the efs image) to your internal storage. it is about 20mb. if there are two files then copy both.
3. connect to wifi and go to playstore and then download and install the IMEI Tool N7100 by Dr Ketan
4. download and install xposed installer and make sure to install update.
5. go to this thread and download and install imei changer
http://forum.xda-developers.com/xposed/modules/xposed-imei-changer-t2847187
make sure to activate it in exposed. then reboot your phone.
6. using ES File Explorer or any file manager with root privelege, go to /efs and delete all files
7. open imei changer then input your imei # (the one that you copied at the back of your pbone) then save. to make sure that your imei has changed dial *#06#. check if your imei if its the one you have written. if not go again to imei changer and change then make sure to save.
8. open IMEI tool by dr. ketan and restore efs backup. it will ask for root privelege so click grant.
9. after restoring efs, reboot to recovery and wipe cache and dalvik then reboot. check if you have data connection.
10. if its not working then go to recovery and make a full wipe and install new touchwiz rom (i used DN4 when I did this, but its up to you whatever you like). and repeat the steps.
* that's all I did mate. there is no scientific explanation about the process that I made, but when I did those things, my phone is working fine again. hopefully it will work for you brother. Good luck and God bless!

edong23 said:
this method works for me, but I am not sure if it will work for you. I have to warn you that I am not a dev, I am just a basic android user. I came up with this idea out of desperation because my phone cannot receive and make calls for almost 4 days. so do this at your own risk.
note:
* make sure your phone is rooted.
* make a copy of your old efs backup and all your important files in your computer or in a flash drive.
1. copy and write on a piece of paper your imei # which will be found at the back of your phone. it is 15 digit
2. copy your efs.img (not the folder that contain the efs image) to your internal storage. it is about 20mb. if there are two files then copy both.
3. connect to wifi and go to playstore and then download and install the IMEI Tool N7100 by Dr Ketan
4. download and install xposed installer and make sure to install update.
5. go to this thread and download and install imei changer
http://forum.xda-developers.com/xposed/modules/xposed-imei-changer-t2847187
make sure to activate it in exposed. then reboot your phone.
6. using ES File Explorer or any file manager with root privelege, go to /efs and delete all files
7. open imei changer then input your imei # (the one that you copied at the back of your pbone) then save. to make sure that your imei has changed dial *#06#. check if your imei if its the one you have written. if not go again to imei changer and change then make sure to save.
8. open IMEI tool by dr. ketan and restore efs backup. it will ask for root privelege so click grant.
9. after restoring efs, reboot to recovery and wipe cache and dalvik then reboot. check if you have data connection.
10. if its not working then go to recovery and make a full wipe and install new touchwiz rom (i used DN4 when I did this, but its up to you whatever you like). and repeat the steps.
* that's all I did mate. there is no scientific explanation about the process that I made, but when I did those things, my phone is working fine again. hopefully it will work for you brother. Good luck and God bless!
Click to expand...
Click to collapse
I followed the same procedure but did not worked.
One more thing i would like to mention that in recent past i got my complete pcb replaced by samsung service center but imei was same. and the backup of efs which i did was on previous pcb/motherboard. could that be the reason i am not able to restore imei?

[REQUEST] Anyone willing to extract and share qcn / xqcn backup ?

Hi,
I recently tried to flash qcn on my OnePlus 7T and it seems that I lost efs data (some sensors aren't working now).
To extract qcn or xqcn file you need to enable usb diagnostic port (in phone app dial *#801# and click the second and fourth buttons).
Doing so will make your phone detectable in Qualcomm softwares.
To extract qcn, use QFIL and click Tools>QCN Backup/Restore. In the field "QCN file path" write the path to the directory you want to save the backup, and also write the name of the file that will be created. Then click Backup QCN.
To extract xqcn, use QPST Software Download, and go to the Backup tab. Click Browse to select the destination for the xqcn backup, and set a name to the backup that will be created. Then click start.
Doing this process is quick and should take approximately 5 minutes if you already have the QPST software.
In case you need it, I have the installer from Qualcomm for QPST 2.7.480 :
http://www.mediafire.com/file/nm0zlac003tn41j/qualcomm_qpst_setup_2.7.480.zip/file
Also you have to know that your IMEI will be visible in these backups, and you should remove them using an hex editor to replace it with some random numbers or zeros before sharing it with me or anyone.
If you need informations on how to find your IMEI in your qcn or xqcn backup using an hex editor, I will explain it in this thread too.
Thank you

Are you saying with these same methods you lost efs data or you did a mistake while flashing ?

Thanks @egekonuk for your reply.
In fact I was trying to flash international rom version on my TMobile Oneplus 7T by editing MSM download tool (using x64dbg which is a software sharing many functionalities with IDA Pro).
I did not managed to flash international but yes, I lost efs in the process.

Superboy58 said:
Thanks @egekonuk for your reply.
In fact I was trying to flash international rom version on my TMobile Oneplus 7T by editing MSM download tool (using x64dbg which is a software sharing many functionalities with IDA Pro).
I did not managed to flash international but yes, I lost efs in the process.
Click to expand...
Click to collapse
Just curious why you didn't do the other posted method to go from TMO to international? I did the other method and it worked out just fine. Of course I don't know if that very friendly person is still doing unlocks or not.
Is there a difference between the QCN and XQCN between ROMs?

@amcferrin90 yes I didn't mentioned that but it's because my device was not SIM unlocked by T-Mobile. I bought it on ebay and I was not aware it was not paid off, and seller refused a return.
If I was SIM unlocked, I'd be able to unlock the bootloader and flash the international rom using fastboot.
I did not understand what you meant about qcn, xqcn and roms.
To me, qcn and xqcn are different because xqcn backups are larger than qcn ones.
I think xqcn contains some efs data, but I'm not sure about this.
Would you be ok to make a xqcn backup and share it with me?
Thanks

I also need a backup of QCN.(please)

No SIM recognition after OOS 10.0.1 update - EFS problem??

Hi,
I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full nandroid backup before.
Everything went fine until I noticed that during the booting of the phone after the flashing, it didn't ask for the SIM code as it used to. And once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network.
I tried switching Sim cards with another mpbile. My SIM worked fine in the other mobile and the other SIM was not recognized by my mobile.
I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done before. Nothing. Same thing with the modem partition. Nothing.
I tried then to restore the EFS from a safety backup that I had using Fastboot. Nothing.
I could still try to restore the full nandroid backup done at the beginning, but I forgot to take out pin protection code before taking the Nandroid, and I've read somewhere that it could be an issue after restoring the system. I might not be able to restart the phone and be obliged to factory reset, witch I would really like to avoid. And anyway, if restoring with Fastboot did not work, I wonder if the full restore would change anything.
Anyway, anybody has a magic idea about might be happening? A little help please??

Same problem!
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.

Working on this
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
rootlessabroad said:
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.
Click to expand...
Click to collapse

Hi
I've found a code (*#06#) in a page that gives you the MEID. It worked for me. Hopefully, I have the correct MEID too. The code for the IMEI did not show anything. I'll check the lynks you posted later today.
Thanks for sharing!!
PS. I can not include the lynk to codes page as I'm too junior a member and XDA forums won't let me.
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse

So I've tried te rebuild the QCN file. But my issue is that I can't make the ADB comunicate with my mobile. It is as the mobile was not plugged in?? The usb debugging is activated. I can browse the mobile memory from the computer. But the ADB doesn't lynk with the mobile; when you type adb devices, it says List of devices attached and nothing after. Any idea what might be happening?
What about you rootlessabroad? could you fix it?
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse