Related
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
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?
D855 running blisspop 2.2 (5.0.1)
As above, I had an issue with my G3 losing the home button at the bottom after 5 mins of switching on so I decided to Fix permissions in TWRP
My G3 is stuck in the blisspop boot animation and stupidly I don't have a nandroid backup :crying: . I have then tried to reboot into TWRP and make a nadroid backup of the bootlooping rom so I could try to get data off it, I'm mainly trying to get my SMS and call history data off the bootlooping rom as all my pictures e.c.t are still on the phone. I have dirty flashed the same version of Blisspop 2.2 I had running but no apps or data show up.
I have tried to used Nandroid manager to try getting the SMS and call log off the old rom, but It says file not found.
Can someone please help me, I just want to get my SMS's off the phone
You could try using adb shell commands to pull the sms and mms messages from your phone. See if the commands from this thread are of any help...
http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
redduc900 said:
You could try using adb shell commands to pull the sms and mms messages from your phone. See if the commands from this thread are of any help...
http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
Click to expand...
Click to collapse
I tried doing so, however I seem to have not to have "/data/data/com.android.providers.telephony/databases/mmssms.db" file or the "com.android.providers.telephony" folder in general
I also checked this in TWRP file manager and I don't have the folder let alone the file, it seems other com.android folders are missing too such as dialer, cell broadcast receiver, nfc e.c.t
I've dirtyflashed the same version of the ROM again to see if this also had files missing, however this has "/data/data/com.android.providers.telephony/databases/mmssms.db" and other folders present when I check in TWRP's file explorer and I can use adb pull to get the mmssms file off from the new rom.
Did "Fixing permissions" really cause me to lose all these com.android files?
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
Code:
adb devices
iii) now use the command
Code:
adb reboot-bootloader
In fastboot use this command to unlock bootloader
Code:
fastboot oem unlock
Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
8) Copy these files in some place where it is safe ( I have copied it to Internal Storage in a folder named PartitionsBackup)..
9) Next, go back to root folder again, and open data/nvram/md/NVRAM/NVD_IMEI and copy the MP0B_001 file to internal storage. Do Not copy this file in the same place as the previous files, but remember where you have copied this file.
These are all the partitions that store the device's IMEI .
10) After copying everything mentioned, Reboot to recovery and flash the desired Custom Rom.
11) Make sure the rom is rooted, and again install FX File Explorer from play store, enable root access as above.
Do Not Forget To Backup Everything Before Doing Anything!
12) Now select the files that you have copied in internal storage (Assuming PartitionsBackup). And copy those files. ( Note: Do Not Copy the MP0B_001 file!)
13) Now open root folder, go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder and paste all the files you have copied, and if asked select Merge/Overwrite files.
14) Reboot.
15) Now go back to internal storage, copy the MP0B_001 file where you have saved it. Go back to root folder and open data/nvram/md/NVRAM/NVD_IMEI and copy the file, select Merge/Overwrite. Now long press the file and select Security, update permissions as Read, Write for both root and radio. Dis-select everything else.
16) Reboot aand Done! Voila ! You should get back the IMEI for your device :victory:
I know its a long post, but it works for Custom ROMs.!
Hope it helps!
Hit Thanks If you feel it works! :highfive:
can you please help me on step 13 because every time i reboot the device the by-name folder contents reset to the original value. my by-name folder backup is 72 mb while when i look in the folder after i reboot it is only 170 bytes
---------- Post added at 06:12 AM ---------- Previous post was at 06:07 AM ----------
also when i wait for a while after rebooting for like 4-6 hours when i looked at my baseband and imei it is not unknown anymore
and my sim is restored but when i reboot again the baseband value and imei is set back to unknown. this happened even before im not following your solution. can it be a hardware issue? would really appreciate any help thx
Cyteezy said:
can you please help me on step 13 because every time i reboot the device the by-name folder contents reset to the original value. my by-name folder backup is 72 mb while when i look in the folder after i reboot it is only 170 bytes
---------- Post added at 06:12 AM ---------- Previous post was at 06:07 AM ----------
also when i wait for a while after rebooting for like 4-6 hours when i looked at my baseband and imei it is not unknown anymore
and my sim is restored but when i reboot again the baseband value and imei is set back to unknown. this happened even before im not following your solution. can it be a hardware issue? would really appreciate any help thx
Click to expand...
Click to collapse
I didn't get you. Do not backup the whole by-name folder. Just copy the files mentioned above. And when you go into the custom ROM, just restore the files copied in the same by-name folder.
No. It might not be a hardware problem.
PraneethMv said:
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
Code:
adb devices
iii) now use the command
Code:
adb reboot-bootloader
In fastboot use this command to unlock bootloader
Code:
fastboot oem unlock
Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
8) Copy these files in some place where it is safe ( I have copied it to Internal Storage in a folder named PartitionsBackup)..
9) Next, go back to root folder again, and open data/nvram/md/NVRAM/NVD_IMEI and copy the MP0B_001 file to internal storage. Do Not copy this file in the same place as the previous files, but remember where you have copied this file.
These are all the partitions that store the device's IMEI .
10) After copying everything mentioned, Reboot to recovery and flash the desired Custom Rom.
11) Make sure the rom is rooted, and again install FX File Explorer from play store, enable root access as above.
Do Not Forget To Backup Everything Before Doing Anything!
12) Now select the files that you have copied in internal storage (Assuming PartitionsBackup). And copy those files. ( Note: Do Not Copy the MP0B_001 file!)
13) Now open root folder, go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder and paste all the files you have copied, and if asked select Merge/Overwrite files.
14) Reboot.
15) Now go back to internal storage, copy the MP0B_001 file where you have saved it. Go back to root folder and open data/nvram/md/NVRAM/NVD_IMEI and copy the file, select Merge/Overwrite. Now long press the file and select Security, update permissions as Read, Write for both root and radio. Dis-select everything else.
16) Reboot aand Done! Voila ! You should get back the IMEI for your device :victory:
I know its a long post, but it works for Custom ROMs.!
Hope it helps!
Hit Thanks If you feel it works! :highfive:
Click to expand...
Click to collapse
Can anyone help me in restoring IMEI in stock ROM?
While flashing using SN writer or maui meta tool it says "Have been in meta mode. Long press power button to normal reboot". After that nothing. It boots back and I still see the INVALID IMEI message.
MisledMew said:
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
iii) now use the command
In fastboot use this command to unlock bootloader Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Can anyone help me in restoring IMEI in stock ROM?
While flashing using SN writer or maui meta tool it says "Have been in meta mode. Long press power button to normal reboot". After that nothing. It boots back and I still see the INVALID IMEI message.
Click to expand...
Click to collapse
SN write tool can be a little complicated to do. I personally prefer Maui Meta 3G. You can search for guides on SN write tool. There are many....
Facing problem with maui meta 3g
On my mobile it shows its in "Have been in meta mode. Long press power button to normal reboot".
it won't work ahead .... some error like kernel checksum and no permission grant type.. rather i installed drivers of mediatek its not working...
plz help out
Ni$hant said:
On my mobile it shows its in "Have been in meta mode. Long press power button to normal reboot".
it won't work ahead .... some error like kernel checksum and no permission grant type.. rather i installed drivers of mediatek its not working...
plz help out
Click to expand...
Click to collapse
Do you have all drivers installed correctly? ADB, VCOM, USB Drivers?
Also, That message screen is Meta Mode. From that screen only you can do the IMEI process.
Note: This Only works for stock rom. Use this guide.
https://forum.hovatek.com/thread-12328.html
For custom Roms, use my guide.
Device: Lenovo A2016a40 (MY6735M) also known as Lenovo vibe b
Android Version - 6.0 Marshmallow
I can't find any folder named 'nvram' on 'data' directory of root folder
I need experts review and help to resolve my issue last night i am update my phone s20 ultra G988B/ds to its original software everything working fine except network i was using root phone it was fine on all networks but after updating my imei status goes to NG(not good) sim accepted phone but shows emergency calls both imei shoes but network not working plz give me suggestions and issue solution. I am again root my phone but still not working networks plz help
S20 ultra imei status NG
Why you experts not solving my issue no comments at all?
Bro i've posted same kind of post just now i hope someone replies soon otherwise i'll try z3x software or chimera and let you know about the results, i think if your imei is not corrupted then cert file will do the wonder.
well hey everyone same issue i have s20 plus phone was rooted and i flash the firmware and now imei is NG i trid the chimera tool but no luck if u find any fix please help me.
did you guys resolve it ?
i may have an idea
Any fix
do you guys even search before asking?
First, do a TWRP backup, all partitions including efs & modem.
Open the root explorer app, open the efs folder, delete the files named nv_data.bin
, nv_data.bin.md5 & the folder called imei. Then open twrp, wipe all partitions. Flash the latest firmware with Odin.
That solution work???
juda iskariotsky said:
do you guys even search before asking?
First, do a TWRP backup, all partitions including efs & modem.
Open the root explorer app, open the efs folder, delete the files named nv_data.bin
, nv_data.bin.md5 & the folder called imei. Then open twrp, wipe all partitions. Flash the latest firmware with Odin
Click to expand...
Click to collapse