Develop Bugs

[FIX/TOOL] Backup/Restore/Fix IMEI & Data Restore Tool v3.5 - Updated 03/22/2013!!!

[FIX/TOOL] Backup/Restore/Fix IMEI & Data Restore Tool v3.5 - Updated 03/22/2013!!!
USE THIS AT YOUR OWN RISK AS QPST WILL FLASH JUST ABOUT ANYTHING YOU TELL IT TO. I AM NOT RESPONSIBLE IF YOUR PHONE BECOMES MORE BRICKED THAN IT ALREADY IS, EXPLODES, OR TRANSFORMS INTO A SITH LORD AND ATTACKS YOU WITH A LIGHT SABER!
Verizon Users please refer to this thread HERE for IMEI and Roaming fix.
Click for Screenshots in Post #4
FILES YOU WILL BE NEEDING
DOWNLOAD QPST V2.7.378 from HERE
(if you have build version 2.7.385 please let me know)
Fix for Data Issues (Stuck on EDGE/2g) see Post # 3
(Sasktel users custom App has not been updated for you guys cause I am still in need of additional data)
How to get to DIAG Mode
**AOSP ROMs to get to DIAG Mode see Post #2
Option1:Stock ROM (Stock Dialer) dial *#7284#.
Option 2: Stock ROM (No Stock Dialer) flash this file HERE!
Install QuickShortcutMaker.
Open it and type IOT in the search box.
Click on the entry that says IOTHiddenMenu / IOTHiddenMenu / com.android.hiddenmenu/com.android.hiddenmenu.IOTHiddenMenu
Click OK
STOCK ROMS: In the hidden menu or PhoneUtil menu select USBSettingsMenu choose the correct mode and click ok.​
To get started put phone into RMNET + DM + MODEM mode (DIAG Mode)
Connect your phone to your computer using your USB cable (Stock cable will work best no guarantees with any other cable).
You might need these if your phone won't connect USB Drivers.
Look in device manager under ports and serials you should see your phone there.
Now open QPST Configuration click on ports tab and then on Add new port button type in COM## where ## is the port number your phone is connected to.
To make a backup:
Open Software Download from the Start Clients menu.
Click on the Backup tab.
Make sure your phone is listed under port.
Select a location to save your backup (recommended).
Click Start and wait for it to finish.
You should now have a QCN file of your NV Data.
Save the file in a safe place.
To restore:
Open Software Download from the Start Clients menu.
Click on the Restore tab.
Make sure your phone is listed under port.
Select the location you saved your backup to.
Click Start and wait for it to finish.
The phone will attempt to restart if it fails don't panic just manually reboot your phone it may take longer than usual but you should be fine.
IMEI Injection:
Please see Post #3 for IMEI Injection + Data Restore All in one App and Instructions
or
Inject IMEI with QPST
Open RF NV Item Manager from the bin folder found in Program Files folder/Qualcomm/QPST
(RF NV Manager is no longer accessible from the start menu or from inside QPST Configuration).
Click on Setting menu in RF NV Item Manager and select Comport.
Select your phone from the list of ports and click ok.
Go to File menu and select Read From Phone.
You will get a list of NV items and their values from your phone.
Look for item NV_UE_IMEI_I it will be item number 550 you can do a search for it using the search.
If you are unable to find it you will need to add it in
Go to Option => Customize NV Item List.
Then look for the item on the left and move it to the right.
Click OK now you should be able to find it.
NEVER ADD AN ITEM THAT YOU DO NOT KNOW THE CORRECT VALUE FOR YOU CAN DAMAGE YOUR PHONE IF YOU DO SO!​
On the right you will see a set of 9 text boxes this is where your IMEI should be.
Click the Hex Check Box.
The Hex values for your IMEI will consist of no more than 2 characters per a box and must match your IMEI or it will not take the values you enter. The IMEI is also listed in a special order so you must follow this guide to ensure your IMEI is correct. The first box will always be an 8.
Example if your IMEI was: 954091051099226 then the boxes would look like this:
8
9a
45
90
01
15
90
29
62​
Click on the button Write NV to write the values to your phone.
Once they have been written reboot your phone and check to see if your IMEI has been restored.
If IMEI is correct and you are stuck on EDGE/2g go to Post #3.
Remember to go back into the Hidden Menu and set your USB Settings back to MTP + ADB once you are done!!!!
________________________________________________________________________________________________
Thread Rules:
Do not ask how to spoof IMEI or how to clone IMEI you will be ignored!
Do not answer someone who asks for information on IMEI spoofing or cloning!
Please do not ask questions unless you have used the Search option!!
Please do not use this thread as a place to settle out any ill feelings towards each other or any other developments!!!
Please do not ask questions that have already been answered!!
Please do help each other when at all possible!!
Don't hesitate to have fun while we all try to figure this problem out!
If I do not answer you right away it's not because I don't like you it's because I have a family, a job, a life outside of development that needs tending to!!
Also thanks to jroyalty, zmore, drothenberger, David Dee, PureMotive, Bigbyte.me, GerardAnthony, Amoamare, <>, XDA, and everyone who donated their phone data for research =)
DX
I don't ask for donations (I do this cause I enjoy it) but a nice latte every now and then late at night is quite refreshing while developing...lol

________________________________________________________________________________________________
AOSP Roms
Added scripts as downloadable files for those who may want them that way.
Place phone in and out of DIAG Mode by running these scripts.
Script to enter DIAG Mode (RMNET + DM + MODEM Mode)
Code:
echo 0 > /sys/class/android_usb/android0/enable 0
echo smd,bam > /sys/class/android_usb/android0/f_rmnet/transports
echo diag > /sys/class/android_usb/android0/f_diag/clients
echo 1 > /sys/class/android_usb/android0/f_acm/instances
echo rmnet,acm,diag > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
Script to return to MTP(eject first)
Code:
echo "" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun_ex/file
echo 0 > /sys/devices/virtual/android_usb/android0/enable
echo "mtp,acm,adb" > /sys/class/android_usb/android0/functions
echo 1 > /sys/devices/virtual/android_usb/android0/enable
vold

Custom App updated current support is for AT&T, T-Mobile, Bell, Telus, and Rogers. I am in need of anyone with a working Sasktel phone in order to get this working for Sasktel.
Updated to version 3.5. Added IMEI Injection Checkbox.
Download - SGS3 Data Restorer App
This custom app will create a QCN file that can be restored to your phone after you inject your IMEI back into your phone and find yourself with data connection issues. This is only used if you had lost your IMEI and did not have a backup created!!
Instructions:
Create a QCN backup of your phone using QPST (see OP for instructions).
On a Windows Vista or higher computer download the app and install it.
Once installed, close the app.
Go to start menu, you will find app under DanX and run it.
(If there are any new updates the app will find it.)
Select your Carrier
If you need your IMEI injected then click the checkbox next to "Inject IMEI"
Upload your QCN backup into the app.
If you clicked the checkbox a window will pop up at this time asking for your IMEI.
**Enter it exactly how you see it on the back of your phone.
Select a save location and create a save name.
Verify that your IMEI is correct.
Click "IMEI Verified" button.
Wait and the QCN should be generated.
Go to the location where you saved the QCN.
Go to QPST and restore file into your phone (see OP for instructions).
Manually reboot your phone.
If you have a slow connection still but you're no longer on 2g reboot again.
If you still a have slow connection after that consider flashing stock again through Odin and then generate another backup using this app.
You can also try flashing a different modem and then generate another backup using this app.
If it still is not working respond to this thread.
I do not guarantee any success and results may vary on how badly you have screwed your phone!
I am not responsible if you screw your phone worst than it already is as QPST is a deadly phone weapon use it at your on risk.
DX
I cannot guarantee release times as I do this on my spare time but I promise I will try to keep this updated as long as I can. Though the coffee may keep me up I do sleep every now and then if you used the app and you liked it please donate it pays for coffee.

Screenshots
Great emergency resource.
Now everyone can start flashing again like it's going outta style.
--------------------------------------------------------------------------------------------------
EDIT: Added some screenshots of the process to reassure whomever it helps:
1_SAM_GS3_EXPLOITER_By_GeeK_finished.png
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1b_Hidden_menu_screenshot_montage.jpg
2_win7_drivers_after_changing_to_RMNET_DM_MODEM.png
3_QPST_InstallShield.png
4_Device_Manager_Phone_COM_Port.png
5_QPST_Add_New_Port.png
6_QPST_Port_Added.png
7_QPST_Software_Download_BackupNV.png
8_QPST_RF_NV_Manager_WRITE_IMEI_TO_NV.png
This last screenshot is for people who haven't already backed up their IMEI but want to try forcefully writing it back. The example 15-digit IMEI number I used (but didn't actually write) was: 123456789012345

Awesome.
If confirmed, please make an app that we can all donate too. This will be most beneficial to you and the community.
Thank you for the countless nights
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

I'm more interested in the IMEI injection. If someone has already lost their IMEI and can simply inject their original IMEI back into the phone then we're golden (not that you shouldn't have a backup just in case, but it's nice nevertheless).

Haha look whose got their own thread! great work man look forward to this being confirmed so we can all breathe a sigh of relief!
Sent from my SGH-I747 using Tapatalk 2

Thanks man! You are a life saver for many. Your work is much appreciated.

The only thing I'm confused is secured and unsecured kernel.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

As soon as this is confirmed working I think it will be time to fulfill our promise of donating to the one who solved this issue

We need links to insecure kernels for Canadian carries unfortunately

rgoyena said:
The only thing I'm confused is secured and unsecured kernel.
Click to expand...
Click to collapse
An "insecure" kernel is one in which adb automatically gets root access. This is required for GeeK's mod to work. If you are on UCALEM, you can flash the one from here. (There are others, too.)
If you're running the LG1 stock kernel, you can install the "adb insecure" app. Run it and click the box to make your kernel insecure, then use GeeK's mod. This is what I did and it worked perfectly.
EDIT: "adb insecure" should work for any kernel, including the Canadian ones.

rgoyena said:
The only thing I'm confused is secured and unsecured kernel.
Click to expand...
Click to collapse
Just to add to what drothenberger said: in secure mode, when you adb shell into your phone, you have to use 'su' post-login to become root:
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ #
This is a pain, because you can't directly do stuff like "adb push foobar.apk /system/app/" without being root first, which is what the insecure mode fixes. Newer versions of CyanogenMod also now have a root settings menu that gives you even finer grained control of this.

It does work for Can carriers, I confirmed that in the other thread. Take a look at my mini guide there: http://forum.xda-developers.com/showthread.php?p=29462669
Sent from my SGH-I747M using XDA Premium HD app

I'm running faux kernel for att.
About adb. Now this is a problem for me. Never used it and always tried to avoid using it. Lol
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

rgoyena said:
I'm running faux kernel for att.
About adb. Now this is a problem for me. Never used it and always tried to avoid using it. Lol
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
kernel doesn't matter as long as it is stock. The app will make it insecure. Adb is something essential if you are flashing.
Sent from my SGH-I747M using XDA Premium HD app

Hey this is awesome! I hope it is confirmed working! I have one quick question. When you say that you have to be on a stock rom, do you mean "stock" stock as in, the stock rom the phone came out of the box in, or does it still work on a stock based rom (like a debloated/deodex rom, with mods etc?)

drothenberger said:
An "insecure" kernel is one in which adb automatically gets root access. This is required for GeeK's mod to work. If you are on UCALEM, you can flash the one from here. (There are others, too.)
If you're running the LG1 stock kernel, you can install the "adb insecure" app. Run it and click the box to make your kernel insecure, then use GeeK's mod. This is what I did and it worked perfectly.
EDIT: "adb insecure" should work for any kernel, including the Canadian ones.
Click to expand...
Click to collapse
I'm on LG1 and I used adb insecure, purchased from the Market (gotta support Chainfire, the man rocks!). It all worked flawlessly for backing up my IMEI.

ViralCipher said:
Hey this is awesome! I hope it is confirmed working! I have one quick question. When you say that you have to be on a stock rom, do you mean "stock" stock as in, the stock rom the phone came out of the box in, or does it still work on a stock based rom (like a debloated/deodex rom, with mods etc?)
Click to expand...
Click to collapse
stock based, not aosp. I am on k747 Sammy kernel and it worked
Sent from my SGH-I747M using XDA Premium HD app

SOOOO happy now I can start flashing away when i get my s3 on monday!

[Q] Product code: "Not active" / Kies won't update / N7100

Hi,
My problem is Kies won't update my phone - GT-N7100 (a well known message that the device is not supported, with triple (xxx) in place of the CSC code at the end of this message). Also when I use Check Fus on my phone, in the Product Code field it says "Not active" like below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And this is what Kies says:
I think the lack of Product Code might be the reason why Kies doesn't update. I don't care about Kies so much but I just want to know what's wrong and try to resolve it.
What I did:
1. I bought the phone unbranded, unlocked, and it came with XEF CSC (FW: XXALJ1).
2. I changed the CSC to XEO with CSC Select (from Google Play) --> Phone wiped.
3. After this I upgraded to the newest XXALJ3 FW.
And then when trying to update with Kies it displays the message as above and Check Fus reports PC Not Active. As far as I know it should display full product code in the PC field so in this case: GT-N7100TADXEF (I don't know if the PC also changes when changing the CSC, in case it changes it should of course display GT-N7100TADXEO). I wiped the phone a few times, went back to the original FW (XXALJ1), changed the CSC back to XEF but no luck.
I've gone through many sites/forums but didn't find the answer. Also I didn't mess with EFS folder, I have my proper IMEI. Is there a possibility that CSC Select app did something wrong to the phone? I don't think so because if I'm right it only triggers Samsung's built-in Preconfig menu, so it should't do any harm. I regret not checking if Kies works properly before changing the CSC.
So the big question is: where the phone reads the PC from (where it's stored?) and how to make the Product Code appear as it should?
EDIT:
I figured out the problem lies within the nv_data.bin file in EFS folder. Inside of this file there's a string "Not active". The same string is present in the backup copy (.nv_data.bak). I tried to edit the file with hex editor and put the right product code in place of "Not Active" string but I can't generate proper md5 hash for it (it seems it's not a regular md5 hash that Samsung uses). And when you delete nv_data.bin.md5 it won't recreate one automatically as it was the case in earlier phones. It will just use the backup file. Even when I deleted .nv_data.bak, .nv_data.bak.md5 and nv_data.bin and nv_data.bin.md5 and uploaded only the modified nv_data.bin with proper product code - it somehow restored the files from somewhere else (I heard there is a hidden partition or something with another backup files) and again I have PC: Not active.
I think the solution would be to somehow create md5 hash of that modified nv_data.bin file that's accepted by the phone but I don't know how.

Great Work
Hi brother im also facing the same problem can you please help me.
tom369 said:
Hi,
My problem is Kies won't update my phone - GT-N7100 (a well known message that the device is not supported, with triple (xxx) in place of the CSC code at the end of this message). Also when I use Check Fus on my phone, in the Product Code field it says "Not active" like below:
And this is what Kies says:
I think the lack of Product Code might be the reason why Kies doesn't update. I don't care about Kies so much but I just want to know what's wrong and try to resolve it.
What I did:
1. I bought the phone unbranded, unlocked, and it came with XEF CSC (FW: XXALJ1).
2. I changed the CSC to XEO with CSC Select (from Google Play) --> Phone wiped.
3. After this I upgraded to the newest XXALJ3 FW.
And then when trying to update with Kies it displays the message as above and Check Fus reports PC Not Active. As far as I know it should display full product code in the PC field so in this case: GT-N7100TADXEF (I don't know if the PC also changes when changing the CSC, in case it changes it should of course display GT-N7100TADXEO). I wiped the phone a few times, went back to the original FW (XXALJ1), changed the CSC back to XEF but no luck.
I've gone through many sites/forums but didn't find the answer. Also I didn't mess with EFS folder, I have my proper IMEI. Is there a possibility that CSC Select app did something wrong to the phone? I don't think so because if I'm right it only triggers Samsung's built-in Preconfig menu, so it should't do any harm. I regret not checking if Kies works properly before changing the CSC.
So the big question is: where the phone reads the PC from (where it's stored?) and how to make the Product Code appear as it should?
EDIT:
I figured out the problem lies within the nv_data.bin file in EFS folder. Inside of this file there's a string "Not active". The same string is present in the backup copy (.nv_data.bak). I tried to edit the file with hex editor and put the right product code in place of "Not Active" string but I can't generate proper md5 hash for it (it seems it's not a regular md5 hash that Samsung uses). And when you delete nv_data.bin.md5 it won't recreate one automatically as it was the case in earlier phones. It will just use the backup file. Even when I deleted .nv_data.bak, .nv_data.bak.md5 and nv_data.bin and nv_data.bin.md5 and uploaded only the modified nv_data.bin with proper product code - it somehow restored the files from somewhere else (I heard there is a hidden partition or something with another backup files) and again I have PC: Not active.
I think the solution would be to somehow create md5 hash of that modified nv_data.bin file that's accepted by the phone but I don't know how.
Click to expand...
Click to collapse

bevybeast said:
Hi brother im also facing the same problem can you please help me.
Click to expand...
Click to collapse
I haven't find a solution yet so I can't help you but I'll post here in case I fix this. I'm rather counting on others' advice because I've already spent many hours trying to find the solution without success.

product code
tom369 said:
I haven't find a solution yet so I can't help you but I'll post here in case I fix this. I'm rather counting on others' advice because I've already spent many hours trying to find the solution without success.
Click to expand...
Click to collapse
You can try FREE SRS PRODUCT CODE CHANGER SAMSUNG FOR KİES UPDATE program.

ersan19 said:
You can try FREE SRS PRODUCT CODE CHANGER SAMSUNG FOR KİES UPDATE program.
Click to expand...
Click to collapse
you did try that program?

ersan19 said:
You can try FREE SRS PRODUCT CODE CHANGER SAMSUNG FOR KİES UPDATE program.
Click to expand...
Click to collapse
Thanks for the tip, unfortunately I can't check it because being helpless and with no clues how to resolve the issue I've sent the phone to the service center before I saw this message. But maybe bevybeast who's also facing this problem as written above can check it and report back if it works.

thanx for sharing this, OP
I had this exact same problem. I messed up with GalaxSim Unlock from Play to see if I'd be able to unlock my phone so my EFS files were changed. I decided I don't need it yet so I restored a backup (with the tool described in this thread: http://forum.xda-developers.com/showthread.php?t=1922473 ) and I was pretty sure I got it back to the original.
after I read your description I decided to take another look and found that my NV_DATA.BIN contained a "Not Active" code as it appeared to have been written a very long time ago. I tried again and again and wasn't able to restore the backup, after restart nv.log was showing:
Code:
Tue Dec 18 14:08:49 2012: cracking detected
Tue Dec 18 14:08:49 2012: NV backup has been rebuilt
Tue Dec 18 14:08:49 2012: NV restored
well, luckily I had a backup made with GalaxSim Unlock itself and when I tried restore from the application it worked.
I don't get what "Not Active" is doing there in the first place but it's quite dangerous in case anything goes wrong with the current nv_data.bin, the system will restore to some data that is fishy to say the least. So far I only noticed the "Product Code" was wrong inside but who knows what else is not that obvious

ersan19 said:
you did try that program?
Click to expand...
Click to collapse
Hi ersan19,
I did try it but unfortunately it seems to do nothing - I get the message that product code changed successfully but nothing more really happens. Even after restarting the phone. It won't even change the CSC, not to mention the complete product code. I even disconnected the phone and tried to change the code and it said product code changed OK
@primusmagestri: I'm happy this topic helped you.

i am having the same prob ... so did anyone have a solution to this prob .. or should i send my phone to service center ..... ?

but this happened to me after restoring animage of the efs .. which was taken when the phone was normal

can any one give me the product code of note 2 (n7100) uae ..

Hi,
If you really don't want to send the phone to the service centre the only way I see is to change the nv_data.bin file content (in EFS) folder and put the proper product code string for your phone. The problem is - you also have to calculate md5 hash for it, which is NOT a regular md5 and I don't personally know how to calculate it. In older firmwares you could just delete the .md5 file and the system would calculate the md5 but now it's not this way and you have to put the correct md5 checksum file. If you don't, the nv_data.bin will be recreated from nv_data.bak file. And in case you deleted both these files, the system will recreate them from nv_core.bak file.
There's still chance you have proper product code in either nv_data.bak or nv_core.bak file. If you find the right product code in nv_data.bak just delete nv_data.bin and you should be ok. If only nv_core.bak has good product code, you delete both nv_data.bin and nv_data.bak. You can check the contents of the files with hex editor. Remember to make EFS folder backup before doing anything, and remember that messing with those files can lead to serious trouble if you do something wrong. And of course you need root access for it.
Or maybe there's someone here who would like to share with us the md5 calculation method Samsung is using?

tom369 said:
Or maybe there's someone here who would like to share with us the md5 calculation method Samsung is using?
Click to expand...
Click to collapse
Big thanx for the info ..and waiting for some to tell us how to fix it

devil_slayer said:
can any one give me the product code of note 2 (n7100) uae ..
Click to expand...
Click to collapse
gt-n7100rwdxsg

I am also having the same issue. This happened to my phone after I used CSC Changer app from Play store(In root mode)..
Now I have to update my phone using ODIN only.. Hope somebody will come up with a solution.

AlanDS said:
I am also having the same issue. This happened to my phone after I used CSC Changer app from Play store(In root mode)..
Now I have to update my phone using ODIN only.. Hope somebody will come up with a solution.
Click to expand...
Click to collapse
You have to repair product code with any service box,ex- z3x ,and after that use CSC Galaxy S/s2/s3 from Google Play in ROOT MODE and choose your product code.
All data will be erased. Now flash your phone with odin again,star phone and wipe data again in recovery.

Bruno_rv said:
You have to repair product code with any service box,ex- z3x ,and after that use CSC Galaxy S/s2/s3 from Google Play in ROOT MODE and choose your product code.
All data will be erased. Now flash your phone with odin again,star phone and wipe data again in recovery.
Click to expand...
Click to collapse
can you please explain in detail?

I'm having the same problem with my note 3. Anyone found the solution yet?
Sent from my SM-N9005 using XDA Premium 4 mobile app

Same problem. Any fix for this ?

Same issue.
Sent from my GT-N7100 using XDA Premium 4 mobile app

[GUIDE] Backup/Restore/Repair Your EFS Partition [LS970]

LS970 EFS Backup/Restore/Repair
Every rooted Optimus G user should backup their EFS partitions!
Thanks goes to interloper, toastcfh and everyone in #lg-optimus-g that helped out.
PM me if interested in my Sprint LGOG LS970 EFS repair service.
Contents
1. Flashable EFS for backing up your EFS partitions and packing them into a new flashable .zip.
2. Commands for backing up/restoring EFS manually with terminal or ADB.
3. Flashable "ZERO EFS" with guide for repairing your EFS. This EFS needs to be reprogrammed but could be used in a "worst case" scenario where you didn't backup your EFS and the phone cannot be replaced by any LG/Sprint warranty.
Backup script/commands also work on the ATT/Telus variants. ZERO EFS zip is ONLY for Sprint LS970 users. ATT/Telus users, if you would like a ZERO EFS, please send me your efsbackup.tar in a private message. It is not suggested to publicly post your EFS file. ​
Background
You never know when your NV/EFS/PRL/RADIO may stop working. Restoring your WORKING EFS may save the day. A few users in the #lg-optimus-g IRC channel have run into issues and found their phone unusable, myself included. A few users who flashed the test/Korean JB builds found 3g not working.. or calls/text not working. Some users ran into radio issues after PRL writing failures. My own issues was a missing ICCID which resulted in no 4G. Data wipes, reactivations, ##786# resets were not helping. All of the above issues could have been fixed if an EFS backup was made while the phone was still in working order.
m9kefs1 seems to be radio related
m9kefs2 contains your unique phone identifiers: MEID, IMEI, phone number, MSL, data profiles etc
m9kefs3 seems to be blank 00s​
Backing up EFS
It's easiest to run the Optimus_G_Create_Flashable_EFS.zip attached to this thread. Run in recovery. Optimus_G_Create_Flashable_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/(instead of just a .tar).
If you don't like convenience this can also be done manually with adb or terminal with the commands below.. root required.
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/sdcard/m9kefs1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/sdcard/m9kefs2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/sdcard/m9kefs3.img
Restoring EFS
To restore your original EFS just boot into recovery and flash the efsbackupflash.zip in your /sdcard/EFS_Backup folder.
If you don't like convenience this can also be done manually with adb or terminal with the commands below. Adjust the "dd if=/sdcard/" command depending on where your backup EFS .img files are located.
Code:
su
dd if=/sdcard/m9kefs1.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1
dd if=/sdcard/m9kefs2.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2
dd if=/sdcard/m9kefs3.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3
Repairing EFS
YOUR EFS IS *NOT* BROKEN IF YOU FLASHED AN AOSP ROM AND NO LONGER HAVE SIGNAL BUT STILL HAVE YOUR MEID AND PRL SAYS "40000"...
GO BACK INTO AOSP ROM > SETTINGS > MORE... > MOBILE NETWORK SETTINGS > CDMA SUBSCRIPTION > SET TO "NV"
YOU SHOULD NOW HAVE A SIGNAL AGAIN... NO EFS REPAIR NEEDED!!
If you have a messed up PRL/Radio/EFS(no signal.. calls/text doesn't work.. no PRL showing.. no 3G) then you should first confirm there are no outages in your area. After confirming no outages you may want to try a factory data reset(settings > backup & reset) or perform a ##786# reset(MSL required). If you are feeling daring you could even try a lgnpst reset which involves installing lgnpst(automated install on IRC suggested) and flashing a stock .tot to your phone while it's in download mode(power off phone > plug phone into USB cable/computer > vol up + vol down + power buttons). If none of the previous suggestions work you could see if Sprint/LG will warranty repair your device.
If NOTHING ABOVE works your final option is to flash a new EFS. Technically you could possibly look through each and every NV item with QXDM and see what's incorrect but that may take forever... so I have included a flashable zip at the bottom of this thread which flashes a fresh LS970 EFS to your device. This EFS is clear of all personal data and any previous phone identifiers. Below are directions on how to reprogram your EFS to the Sprint network after flashing the LS970_ZERO_EFS.zip. I'd rate this as medium-hard difficulty for those that are unfamiliar with how (Sprint)CDMA phones are programmed. For those that have flashed a phone in the past, this ZERO EFS zip just made your day even easier.
The ZERO EFS has a zero'd out SPC/MSL, zero'd out IMEI/MEID, zero'd out MDN/MSID and all data profiles emptied.
NV item 114(NV_FACTORY_INFO_I) has been "anonymized" and no longer identifies to anyones real account.
In recovery, flash LS970_ZERO_EFS.zip then wipe data/cache(factory wipe in TWRP). LS970_ZERO_EFS.zip backs up your current EFS partitions to /sdcard/EFS_Backup and then replaces your EFS with the ZERO EFS.
You will have to manually program your phone to get it working again.
READ EVERYTHING BELOW IF YOU DON'T KNOW WHAT YOU'RE DOING.
After flashing LS970_ZERO_EFS.zip:
For talk/text working - use DFS(www.cdmatool.com) or other known working CDMA tools.
a1. Set LS970 into diag mode.. open the dialer and hit ##3424# . Also make sure phone is set to "Charge only"
b1. Connect phone to DFS and set correct COM port. Use the diag port NOT the serial port.
c1. In DFS send SPC(MSL) to phone using "SPC" button(under the green ports button, top left). SPC = 000000.
d1. On Programming > General tab... Write desired IMEI with DFS. Hit "status" button to make sure it stuck. IMEI = MEID + 1 extra digit.
e1. After writing IMEI.. write the matching MEID. Hit "status" button to make sure it stuck.
f1. On your phone, open dialer and hit ##000000# and program in your MDN/MSID. Hit done. Phone will reboot.
Talk/text will now work!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For 1X/3G working - use DFS
a2. Connect phone to DFS and send SPC using above methods.
b2. In DFS, open the Programming > Data tab and hit the read button.
c2. Set the UID under HDR AN LONG to your [email protected]
d2. Set the Pwd to your 32-char hex password, no spaces between hex bytes. Make sure box is checked next to Pwd!!
e2. In DFS go to the Programming > Mobile IP tab. Hit the blue "Read" button in the lower left.
f2. Set the username(NAI) to the same username you just wrote in step c2... [email protected]
g. Set the AAA Shared Secret password. The same 32-char password used in step d. Make sure box is CHECKED for AAA!!!
h. Set the HA Shared Secret password to: secret . Yes, the word secret. MAke sure the box is UNCHECKED for HA!!!
i. Hit the red "Write Current Profile Settings" button.
j. Back on your phone, open the dialer and press ##3282# and click "Data Profile" then "edit". Enter 000000 for code.
k. Once inside Data Profile menu, set up your Sprint username and password(AAA password).
[email protected] and the AAA password is a 6-char password.
l. Once data profile is written back out of the menu and the phone should reboot.
1X/3G will now work!! [as long as ALL usernames and passwords were written correctly with the 100% correct info!!!]
*Notes*
1. If a ##786# reset is ever done, the 1X/3G data passwords will be wiped and have to be rewritten.
2. Dialer code 3845#*970# > Data -LG menu has a PPP setting. Never set this to Sprint... always leave on "Undetermined"
3. You shouldn't have to do anything for 4G to work.
Now you may say "yeah, that's great... but I don't know my MEID, IMEI, MDN, MSID, 32-char AAA password, Data Profile username... now what?"
Good question.
IMEI - Hopefully your phone isn't TOO messed up and you can still view your IMEI via Settings > About Phone > Phone Identity.
If you can't read it, call Sprint and ask them for it, mention your phone acting up or blah blah. The IMEI is your MEID + 1 extra digit.
MEID - MEID is on your LG OG box. You can also see this by viewing the current phone on your plan using Sprint.com
You want to use the MEID HEX not MEID DEC. If you can only find the DEC you can use online converters to convert MEID DEC to HEX.
MDN - MDN is your phone number. You should know this.
MSID - MSID is sometimes the same as your phone number, but sometimes not. You can view this info in Settings > About Phone > Phone Identity
You can call Sprint to get this info if you can't view it on your phone.
Data Profile username/password - You can get this info by calling Sprint. You may be able to view the username with ##3282# > Data Profile > View
32-char AAA Password - If you are unable to acquire your 32-char AAA password(NV item 466 and 1192), ask Sprint. You may have to speak to some form of advanced tech support.
​
Code:
[B]My other LS970 threads..[/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2049701"][How-To] Enable DIAG mode without Service Code(MSL)[/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2052816"][Info] LS970 Hidden Dialer Codes[/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2058506"][WIP]Optimus G AT Commands[/URL][/B]

although i didnt really help much, glad we figured out what partition it was on

Re: [GUIDE] Backup/Restore/Repair Your EFS Partition
So if I'm reading this right, for simple minded people like me, make a backup with the backup zip. Then to restore, just follow that paragraph about restoring?
Does this mean that if I mess up my phone as far as reception, I could just use my backup to restore it? This stuff is way beyond me, so I gotta pick your brain.
Sent from my LG-LS970 using xda premium

engine95 said:
So if I'm reading this right, for simple minded people like me, make a backup with the backup zip. Then to restore, just follow that paragraph about restoring?
Does this mean that if I mess up my phone as far as reception, I could just use my backup to restore it? This stuff is way beyond me, so I gotta pick your brain.
Click to expand...
Click to collapse
it doesn't touch the actual modem/baseband... but it backs up your entire EFS/NV. NV items are sort of like Windows Registry... but lower level than the Android filesystem. The PRL is also contained in the EFS.
If you ever go into a hidden menu and set a weird setting which kills 3g... if you write a PRL and it goes wrong and you lose all reception.. if you flash a rom and all of the sudden your MEID is gone(etc etc etc).. then having an EFS backup would help.
Backing it up saves the current state of the EFS. So yes, if you had a working backup and then ran into issues down the road... you could reflash your backup EFS and you'd have a fix(hopefully).
The EFS contains all the unique parts of your phone... MEID, IMEI, Data Profiles, Phone number.. etc etc. Its the one thing that can't be replaced if it gets screwed up. If you don't have a backup and replaced all partitions from someone elses phone you'd have their meid, imei, phone number data profile etc.. instead of your own. This is where the 2nd half of my guide comes in. In the extreme case that you have no EFS backup and you can't get your phone replaced by Sprint/LG.. the ZERO EFS zip + guide can get your phone working again.

Wish I new about this a week ago....
Sent from my LG-LS970 using xda premium

Thanks to you autoprime and to all involved that made this possible, this fix worked like a charm!

So crazy question.... Can you use this to correct the radio in the Korean JB rom?
Sent from my LG-LS970

kc_exactly said:
Wish I new about this a week ago....
Click to expand...
Click to collapse
your broken EFS + skullzaflare's broken EFS + my broken ICCID were the reasons I put this together. Wish I put it out sooner
cxdatl said:
So crazy question.... Can you use this to correct the radio in the Korean JB rom?
Click to expand...
Click to collapse
I don't know enough about the Korean JB rom to answer that correctly. I do know it fixes the efs issues if you flash back to a Sprint rom after flashing the korean rom.
is the Korean JB rom CDMA or GSM? I'm not even sure it matters.. but if it's also CDMA I'd have a better feeling about it maybe being possible.
could you tell me the exact issues people were facing after flashing and using the Korean JB rom? was it working minus radio? was radio "active" but not working? etc etc.
as long as you make a backup of your working efs first.. you can always restore back to it. I've flashed bad data to both efs partitions just to see how well this worked. my phone had no baseband.. no working radios... flashed my backup.. all working again. :good:

Hey, I was just attempting to be funny. I truly appreciate this guide. Thanks.
Sent from my LG-LS970 using xda premium

autoprime said:
your broken EFS + skullzaflare's broken EFS + my broken ICCID were the reasons I put this together. Wish I put it out sooner
I don't know enough about the Korean JB rom to answer that correctly. I do know it fixes the efs issues if you flash back to a Sprint rom after flashing the korean rom.
is the Korean JB rom CDMA or GSM? I'm not even sure it matters.. but if it's also CDMA I'd have a better feeling about it maybe being possible.
could you tell me the exact issues people were facing after flashing and using the Korean JB rom? was it working minus radio? was radio "active" but not working? etc etc.
as long as you make a backup of your working efs first.. you can always restore back to it. I've flashed bad data to both efs partitions just to see how well this worked. my phone had no baseband.. no working radios... flashed my backup.. all working again. :good:
Click to expand...
Click to collapse
interpoler needs credit too lol, if it wasnt for his backed up EFS partitions i wouldnt have figured out it was those and got mine working lol.
even though i got mine working aside from 3g, sprint replaced it for free (i just got impatient) but atleast we have a fix now, and you got a blank efs to use for it
edit- oh i didnt see that you edited the post and added info lol

skullzaflare said:
interpoler needs credit too lol, if it wasnt for his backed up EFS partitions i wouldnt have figured out it was those and got mine working lol.
even though i got mine working aside from 3g, sprint replaced it for free (i just got impatient) but atleast we have a fix now, and you got a blank efs to use for it
edit- oh i didnt see that you edited the post and added info lol
Click to expand...
Click to collapse
I actually signed the 2 year contract, I have gotten my first LG through craiglist, then got home and saw this, I did it and the radio worked right away, again great job guys.
Edit: I will start theming this baby soon.
Sent from my LG-LS970 using Tapatalk 2

Updated the Optimus_G_Create_Flashable_EFS.zip in the OP
Now creates a flashable EFS backup instead of just a .tar. Just flash the "efsbackupflash.zip" in recovery to restore.
m9kefs1.img, m9kefs2.img and efsbackupflash.zip are stored in /sdcard/EFS_Backup
I suggest remotely backing up the zip somewhere(Dropbox, PC, etc) just in case /sdcard gets erased.

autoprime said:
your broken EFS + skullzaflare's broken EFS + my broken ICCID were the reasons I put this together. Wish I put it out sooner
I don't know enough about the Korean JB rom to answer that correctly. I do know it fixes the efs issues if you flash back to a Sprint rom after flashing the korean rom.
is the Korean JB rom CDMA or GSM? I'm not even sure it matters.. but if it's also CDMA I'd have a better feeling about it maybe being possible.
could you tell me the exact issues people were facing after flashing and using the Korean JB rom? was it working minus radio? was radio "active" but not working? etc etc.
as long as you make a backup of your working efs first.. you can always restore back to it. I've flashed bad data to both efs partitions just to see how well this worked. my phone had no baseband.. no working radios... flashed my backup.. all working again. :good:
Click to expand...
Click to collapse
Well everything worked for me. But the radio quit after 10min.
Sent from my LG-LS970

cxdatl said:
Well everything worked for me. But the radio quit after 10min.
Sent from my LG-LS970
Click to expand...
Click to collapse
you mean after flashing the korean jb.. it all worked?
was this stock korean jb.. or something modded for sprint users? i saw a few "jb test builds"... are we discussing them or the real korean build?
for the 10 min it worked.. calls/text/3g worked?
were you able to get the radio working again after it quit on you 10 min later? did you have to flash back to sprint? everything working again?

thank you so much for this. i dont know if this is to much to ask but could somebody possibly make a zip that would restore them for you because i have absolutely no idea on how to use abd or terminal lol

I'm not positive, but I think that's just what the new update does. It created a flash able zip with all the info.
Sent from my LG-LS970 using xda premium

javskies said:
thank you so much for this. i dont know if this is to much to ask but could somebody possibly make a zip that would restore them for you because i have absolutely no idea on how to use abd or terminal lol
Click to expand...
Click to collapse
engine95 said:
I'm not positive, but I think that's just what the new update does. It created a flash able zip with all the info.
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
engine95 is correct. the latest backup efs zip extracts your EFS partitions, zips them into a new flashable zip and stores the zip in /sdcard/EFS_Backup.
also in the efs_backup folder are the loose efs partition files... just cause.

The zip creates the back up but from what I read from the guide it says you have to use terminal to restore them
Sent from my LG-LS970 using xda premium

javskies said:
The zip creates the back up but from what I read from the guide it says you have to use terminal to restore them
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
reread, he forgot to add a word
To restore your original EFS just boot into recovery and flash the efsbackupflash.zip in your /sdcard/EFS_Backup folder. OR To manually restore use the commands below. Adjust the "dd if=/sdcard/" command depending on where the backup .img is located.

It's been updated. Autoprime mentioned it about 8 posts up. Updated file in the op.
Sent from my LG-LS970 using xda premium

[Q&A] [GUIDE] Backup/Restore/Repair Your EFS Partition [LS970]

Q&A for [GUIDE] Backup/Restore/Repair Your EFS Partition [LS970]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

autoprime said:
LS970 EFS Backup/Restore/Repair
Every rooted Optimus G user should backup their EFS partitions!
Thanks goes to interloper, toastcfh and everyone in #lg-optimus-g that helped out.
PM me if interested in my Sprint LGOG LS970 EFS repair service.
Contents
1. Flashable EFS for backing up your EFS partitions and packing them into a new flashable .zip.
2. Commands for backing up/restoring EFS manually with terminal or ADB.
3. Flashable "ZERO EFS" with guide for repairing your EFS. This EFS needs to be reprogrammed but could be used in a "worst case" scenario where you didn't backup your EFS and the phone cannot be replaced by any LG/Sprint warranty.
Backup script/commands also work on the ATT/Telus variants. ZERO EFS zip is ONLY for Sprint LS970 users. ATT/Telus users, if you would like a ZERO EFS, please send me your efsbackup.tar in a private message. It is not suggested to publicly post your EFS file. ​
Background
You never know when your NV/EFS/PRL/RADIO may stop working. Restoring your WORKING EFS may save the day. A few users in the #lg-optimus-g IRC channel have run into issues and found their phone unusable, myself included. A few users who flashed the test/Korean JB builds found 3g not working.. or calls/text not working. Some users ran into radio issues after PRL writing failures. My own issues was a missing ICCID which resulted in no 4G. Data wipes, reactivations, ##786# resets were not helping. All of the above issues could have been fixed if an EFS backup was made while the phone was still in working order.
m9kefs1 seems to be radio related
m9kefs2 contains your unique phone identifiers: MEID, IMEI, phone number, MSL, data profiles etc
m9kefs3 seems to be blank 00s​
Backing up EFS
It's easiest to run the Optimus_G_Create_Flashable_EFS.zip attached to this thread. Run in recovery. Optimus_G_Create_Flashable_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/(instead of just a .tar).
If you don't like convenience this can also be done manually with adb or terminal with the commands below.. root required.
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/sdcard/m9kefs1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/sdcard/m9kefs2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/sdcard/m9kefs3.img
Restoring EFS
To restore your original EFS just boot into recovery and flash the efsbackupflash.zip in your /sdcard/EFS_Backup folder.
If you don't like convenience this can also be done manually with adb or terminal with the commands below. Adjust the "dd if=/sdcard/" command depending on where your backup EFS .img files are located.
Code:
su
dd if=/sdcard/m9kefs1.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1
dd if=/sdcard/m9kefs2.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2
dd if=/sdcard/m9kefs3.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3
Repairing EFS
YOUR EFS IS *NOT* BROKEN IF YOU FLASHED AN AOSP ROM AND NO LONGER HAVE SIGNAL BUT STILL HAVE YOUR MEID AND PRL SAYS "40000"...
GO BACK INTO AOSP ROM > SETTINGS > MORE... > MOBILE NETWORK SETTINGS > CDMA SUBSCRIPTION > SET TO "NV"
YOU SHOULD NOW HAVE A SIGNAL AGAIN... NO EFS REPAIR NEEDED!!
If you have a messed up PRL/Radio/EFS(no signal.. calls/text doesn't work.. no PRL showing.. no 3G) then you should first confirm there are no outages in your area. After confirming no outages you may want to try a factory data reset(settings > backup & reset) or perform a ##786# reset(MSL required). If you are feeling daring you could even try a lgnpst reset which involves installing lgnpst(automated install on IRC suggested) and flashing a stock .tot to your phone while it's in download mode(power off phone > plug phone into USB cable/computer > vol up + vol down + power buttons). If none of the previous suggestions work you could see if Sprint/LG will warranty repair your device.
If NOTHING ABOVE works your final option is to flash a new EFS. Technically you could possibly look through each and every NV item with QXDM and see what's incorrect but that may take forever... so I have included a flashable zip at the bottom of this thread which flashes a fresh LS970 EFS to your device. This EFS is clear of all personal data and any previous phone identifiers. Below are directions on how to reprogram your EFS to the Sprint network after flashing the LS970_ZERO_EFS.zip. I'd rate this as medium-hard difficulty for those that are unfamiliar with how (Sprint)CDMA phones are programmed. For those that have flashed a phone in the past, this ZERO EFS zip just made your day even easier.
The ZERO EFS has a zero'd out SPC/MSL, zero'd out IMEI/MEID, zero'd out MDN/MSID and all data profiles emptied.
NV item 114(NV_FACTORY_INFO_I) has been "anonymized" and no longer identifies to anyones real account.
In recovery, flash LS970_ZERO_EFS.zip then wipe data/cache(factory wipe in TWRP). LS970_ZERO_EFS.zip backs up your current EFS partitions to /sdcard/EFS_Backup and then replaces your EFS with the ZERO EFS.
You will have to manually program your phone to get it working again.
READ EVERYTHING BELOW IF YOU DON'T KNOW WHAT YOU'RE DOING.
After flashing LS970_ZERO_EFS.zip:
For talk/text working - use DFS(www.cdmatool.com) or other known working CDMA tools.
a1. Set LS970 into diag mode.. open the dialer and hit ##3424# . Also make sure phone is set to "Charge only"
b1. Connect phone to DFS and set correct COM port. Use the diag port NOT the serial port.
c1. In DFS send SPC(MSL) to phone using "SPC" button(under the green ports button, top left). SPC = 000000.
d1. On Programming > General tab... Write desired IMEI with DFS. Hit "status" button to make sure it stuck. IMEI = MEID + 1 extra digit.
e1. After writing IMEI.. write the matching MEID. Hit "status" button to make sure it stuck.
f1. On your phone, open dialer and hit ##000000# and program in your MDN/MSID. Hit done. Phone will reboot.
Talk/text will now work!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For 1X/3G working - use DFS
a2. Connect phone to DFS and send SPC using above methods.
b2. In DFS, open the Programming > Data tab and hit the read button.
c2. Set the UID under HDR AN LONG to your [email protected]
d2. Set the Pwd to your 32-char hex password, no spaces between hex bytes. Make sure box is checked next to Pwd!!
e2. In DFS go to the Programming > Mobile IP tab. Hit the blue "Read" button in the lower left.
f2. Set the username(NAI) to the same username you just wrote in step c2... [email protected]
g. Set the AAA Shared Secret password. The same 32-char password used in step d. Make sure box is CHECKED for AAA!!!
h. Set the HA Shared Secret password to: secret . Yes, the word secret. MAke sure the box is UNCHECKED for HA!!!
i. Hit the red "Write Current Profile Settings" button.
j. Back on your phone, open the dialer and press ##3282# and click "Data Profile" then "edit". Enter 000000 for code.
k. Once inside Data Profile menu, set up your Sprint username and password(AAA password).
[email protected] and the AAA password is a 6-char password.
l. Once data profile is written back out of the menu and the phone should reboot.
1X/3G will now work!! [as long as ALL usernames and passwords were written correctly with the 100% correct info!!!]
*Notes*
1. If a ##786# reset is ever done, the 1X/3G data passwords will be wiped and have to be rewritten.
2. Dialer code 3845#*970# > Data -LG menu has a PPP setting. Never set this to Sprint... always leave on "Undetermined"
3. You shouldn't have to do anything for 4G to work.
Now you may say "yeah, that's great... but I don't know my MEID, IMEI, MDN, MSID, 32-char AAA password, Data Profile username... now what?"
Good question.
IMEI - Hopefully your phone isn't TOO messed up and you can still view your IMEI via Settings > About Phone > Phone Identity.
If you can't read it, call Sprint and ask them for it, mention your phone acting up or blah blah. The IMEI is your MEID + 1 extra digit.
MEID - MEID is on your LG OG box. You can also see this by viewing the current phone on your plan using Sprint.com
You want to use the MEID HEX not MEID DEC. If you can only find the DEC you can use online converters to convert MEID DEC to HEX.
MDN - MDN is your phone number. You should know this.
MSID - MSID is sometimes the same as your phone number, but sometimes not. You can view this info in Settings > About Phone > Phone Identity
You can call Sprint to get this info if you can't view it on your phone.
Data Profile username/password - You can get this info by calling Sprint. You may be able to view the username with ##3282# > Data Profile > View
32-char AAA Password - If you are unable to acquire your 32-char AAA password(NV item 466 and 1192), ask Sprint. You may have to speak to some form of advanced tech support.
​
Code:
[B]My other LS970 threads..[/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2049701"][How-To] Enable DIAG mode without Service Code(MSL)[/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2052816"][Info] LS970 Hidden Dialer Codes[/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2058506"][WIP]Optimus G AT Commands[/URL][/B]
Click to expand...
Click to collapse
Can any body held me . I have lost my cell fone service after installing kitkat zip rom V20A of vodafone in my LG optimus f180L. After that I flashed European KDZ back which I was uning previously V10h but after installing baseband I lost signals on my device. no data ne any service . and after inserting sim card my IMEI number shows unknown.. Please held me how can i get out of this problem..

gm sheikh said:
Can any body held me . I have lost my cell fone service after installing kitkat zip rom V20A of vodafone in my LG optimus f180L. After that I flashed European KDZ back which I was uning previously V10h but after installing baseband I lost signals on my device. no data ne any service . and after inserting sim card my IMEI number shows unknown.. Please held me how can i get out of this problem..
Click to expand...
Click to collapse
try to find proper kdz for your model phone, f180L. flash f180L kdz or tot.

autoprime said:
try to find proper kdz for your model phone, f180L. flash f180L kdz or tot.
Click to expand...
Click to collapse
I flashes peoper KDZ for F180L but same problem i am facing no signals no GSM service no IMEI showing. Plz help .
I think i have efs messed up problem. Guide me to fix this problem

gm sheikh said:
I flashes peoper KDZ for F180L but same problem i am facing no signals no GSM service no IMEI showing. Plz help .
I think i have efs messed up problem. Guide me to fix this problem
Click to expand...
Click to collapse
if you did not backup your efs BEFORE you lost signal.. then there is no fix.
if you made a backup of your efs BEFORE you lost signal... you can restore it to fix the problem.

autoprime said:
if you did not backup your efs BEFORE you lost signal.. then there is no fix.
if you made a backup of your efs BEFORE you lost signal... you can restore it to fix the problem.
Click to expand...
Click to collapse
Now there is no way to get it Back? there will be any way to make my cell fone alive to make calls,sms 3G rtc??? If you Know any way Plz guide me??

It's easiest to run the Optimus_G_Create_Flashable_EFS.zip attached to this thread. Run in recovery. Optimus_G_Create_Flashable_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/(instead of just a .tar).
Run a .zip? i dont get it. The .zip folder creates a flashable zip?

ryblade said:
It's easiest to run the Optimus_G_Create_Flashable_EFS.zip attached to this thread. Run in recovery. Optimus_G_Create_Flashable_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/(instead of just a .tar).
Run a .zip? i dont get it. The .zip folder creates a flashable zip?
Click to expand...
Click to collapse
Yes, that's correct. The create flashable efs zip does that, then you can just flash the efs zip it creates if you ever need. I create one every time there is a prl update from sprint just because. (Prl is stored in efs partition with all the imei and carrier stuff specific to your phone.)

so i updated to the 02/11 update to my phone and all of the sudden out of the blue my prl says 40000 and i cant make calls and i cant use lte i need help asap please i already put it in NV mode and nothing happens . i have the efs backed up but when i try to flash them the recovery wont let me for some reason
Update i actually got it to work after 5 hours of trial and error . what since all of my backups got corrupted i managed to find one of the early versions of when i first backed up my efs and made a flashable zip of it then i got my cellular network and voice to work but as i am replying to this message now the efs got deleted after i made a call on the 2/11 version of cm12 so i think im going to revert back to an earlier build . thanks for the help .

will this work for f180 converted to e975
ihave f180 converted to e975 and it is showing imei 0 will your method work to restore imei , please reply so i should go with the procedure need help

[IMEI GUIDE] Restoring your lost IMEI in MTK phones

A common problem many face in their phone is loss of IMEI no. This is results in no network detection by your phone. U can come to know you have lost your IMEI by checking Settings->About phone->Phone information. There under IMEI section you won’t be finding your mobile IMEI numbers displayed.
Don’t worry you can restore your IMEI’s. Just follow this guide and you will be able to restore your IMEI. I will split the tutorial into two parts.
BACKING IMEI :
-First step before performing all these things is that your phone should be rooted.
When your phone is in normal state with everything functioning install Root explorer and navigate to the below location
Code:
>ROOT>DATA>NVRAM>MD>NVRAM>NVD_IMEI>MP0B_001
-Now copy this MP0b_001 file to your SD card or PC whichever place you feel the file we be safer.
-Now download MTK Droid tools .
-Now extract the zip file and open the MTK droid tools exe file.
-Now in your phone turn on USB Debugging by going to Settings->About phone-> Developer options and there turn on USB debugging.
-Now connect your phone and MTK droid tools should be able to detect your phone. U should see a window like this appearing after your
phone has been detected.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Now press the ROOT button present in lower right corner. When it asks Supersu grant in your mobile click allow. After MTK droid gets
access u should see a green colour box appearing in the lower left corner which means u have correctly granted access to MTK droid.
-Now click on the IMEI/Nvram tab. A window should open and click backup NVRAM and MTK droid tools would take a backup of NVram in
its folder.
RESTORING IMEI :
-Now when you lose IMEI first try this method. Now take the MPDB_001 file which you took backup at the first step and navigate through
Root explorer to this location ->ROOT->DATA->NVRAM->MD->NVRAM->NVD_IMEI.
-Now paste that file and replace the one present there. Set the permissions for that file as RWER-ER-E. Now reboot your phone and you
should be able to get your IMEI back.
If you still haven’t got IMEI open MTK droid tools and connect your phone and press ROOT again and give MTK droid tools root access.
-Now click on IMEI/Nvram tab and select Restore option and restore the NVram backup which you took earlier. Now reboot your phone and
you should be able to get your IMEI.
Extreme method :
-After performing all the above if you haven’t still got IMEI. Now switch off your phone and open SP Tools and connect your phone.
Click on format and format your whole phone. ( This wipes whole of the phone including NVram region ).
-Now flash stock ROM through SP Tools and after it completes start up your phone. ( Don’t be surprised. Your IMEI will still be in lost state
only ). Now root your phone.
-After successful rooting now connect your phone to MTK Droid tools and again press ROOT button and grant root access to MTK Droid
tools. Now click on IMEI/NVram tab.
-Now as you see in the image above you can see two boxes IMEI1 and IMEI 2. Now enter your device IMEI numbers manually in those two
boxes.( You can get your IMEI no’s from your phone box ). Now click replace IMEI. Now reboot your phone and you should be definitely able
to get your IMEI restored.
MTK DROID TOOLS LINK : https://www.androidfilehost.com/?fid=24438995911972546
found: http://www.androiddevs.net/restoring-lost-imei-mtk-phone/

Please Help IMEI on my micromax a63 became invalid now mobile uncle tools does not restore it, i used mtk droid tool but when i click on root button on mtk droid tool it says data/local/tcp/ permission denaid , please help how to restore my imei on micromax a63
Sent from my GT-I8552 using xda app-developers app

sim 2 imei not restoring
I recently flahsed phone by mistake i lost both imei number but using uncle tools i was able to restore my sim1 imei but my second sim imei is not restoring ,when i try restoring second imei this replaces the oldersim1 imei and sim2 imei remains invalid i have tried uncle tiol and mtk droid tool but not working due to this problem i am only able to use one sim , now how can i restore the second sim imei please help

Here is a guide for restoring your IMEM from me, that works 100%
http://forum.xda-developers.com/showpost.php?p=67724424&postcount=53

Restoring IMEI with "build in IMEI Tool"
With a lot of thanks to user @ardrift :
with *#*#6813#*#* entered on the stock dialer you can acess the "IMEI-Tool" which allows you to enter a new IMEI for both SIM cards. The new IMEI stay permanent even after reboot. This also works on 'new' P8000 with Android 6.0 out of the box.
first I thought this is a joke but actually it worked - sometimes life can be so easy

My phone is not recognized with this program. I have installed all the usb drivers.

stefandavcev said:
My phone is not recognized with this program. I have installed all the usb drivers.
Click to expand...
Click to collapse
Do the step above.
The Program dont work anymore..
Gesendet von meinem P9000 mit Tapatalk

hello ! Imei ?? ha ha .. Írd be (*#*#6813#*#*) !!

FrauHofrat said:
Restoring IMEI with "build in IMEI Tool"
With a lot of thanks to user @ardrift :
with *#*#6813#*#* entered on the stock dialer you can acess the "IMEI-Tool" which allows you to enter a new IMEI for both SIM cards. The new IMEI stay permanent even after reboot. This also works on 'new' P8000 with Android 6.0 out of the box.
first I thought this is a joke but actually it worked - sometimes life can be so easy
Click to expand...
Click to collapse
Great!!! Thmks a lot for sharing