i tried to solve my problem for 1 day before i make this thread.i have an unbraded ls ks20 with english rom v10c.i tried to pass a greek rom (v10g vodafone).after flash it and the phone start setup shows me a message "illegal use" so i went back to english rom.since then my phone doesn't conect to the network "no service".everything else works fine .what should i do?did i kill my brand new lg ks20?
i really need help!
Never flashed before - but you need a special file (nv?) that is unique to your phone. If you didn't back that up, yes you killed it ! If you did search XDA for instructions on how to restore it.
You can do this step to find your signal.
1.backup your ks-20 NV file,the file you can backup from firmware.
2.firm ENG rom and chose ERASE ESF.
3.complete the flash,you can go in the system,and find Windag_open.cab install on the device,and open engineer mode.
4.open firmware,only flash nv file,since reset ,you will find the signal.
I do this to find my signal
lol, He loss calibration data from handset!!!! If there is no service after flashing without NV backup, only way to resolve that problem to flash the NVRAM with backup of another handset and correct IMEI and BT address.
To everyone,
If u need .nv2 file, pm me with ur imei no. and email address, i can generate one for you, but the last digit, which is calculated by your phone, would likely to be different and also i can only generate branded .nv2 since i only got branded .nv2 file. It could be work in unbranded phone but just u need to flash a branded rom or hybrid rom to use with it.
thank you raykisi you are the best it works 100%.
LG KS20 Network Problems
Sorry,
My e-mail is [email protected]
I can't help you with only your email address
Read the posts in my signiture pls
LG KS20 Network Problem
I have read it. Again, many thanks, specially to you; everithing from there was very helpfull.
I will give you the IMEI number: 357323-01-137914-1
I have managed to write the IMEI to the phone with QPSt; do i need to do something else?
If i conect back with QPST shows the IMEI (without the last digit)
Unfortunatell i don't have a valid backup for the nv file
Any help will be great
Ths in advance
Hi raykisi,
I still have my .qcn file... but what I'm trying to do is a little bit different: put a KS20 rom on a MS25 mobile (similar mobile that we have here in Brazil).
I tried to recover my network config using my qcn backup but I couldn't...
My phone always shows "No Service".
Tooo bad...
;(
Hope you can help me...
Thanya
What does ERASE EST do? Why would you think this whole procedure will help find the signal? I asked because my KS20 doesn't find any signal in a lot of places but my wife's KS20 does. I am wondering if there is anything I can try to resolve my problem. Thanks.
sam_sun said:
You can do this step to find your signal.
1.backup your ks-20 NV file,the file you can backup from firmware.
2.firm ENG rom and chose ERASE ESF.
3.complete the flash,you can go in the system,and find Windag_open.cab install on the device,and open engineer mode.
4.open firmware,only flash nv file,since reset ,you will find the signal.
I do this to find my signal
Click to expand...
Click to collapse
Hi everyone,
I guess many of you are in huge pain with the KU990 new version, that is, the ones that cannot be unlocked using lg3g or mtty methods.
Here I would like to describe everything I tried so far and the current status I am locked in today.
My biggest mistake was to not backup my phone (the famous .nv2 file) at the very beginning ! I strongly advise people who wish to modify their phone somehow to first backup with LGMDP !! Otherwise you may end just like me...
I started with a SFR (VDF FRANCE) locked phone and, as I did not have the SFR sim card at that time, I tried to unlock it with both the lg3g and the mtty methods. Unfortunately the unlocking procedures did not work at all, although I ensure I tried everything. I finally read somewhere that the newest KU990 had a supplementary protection that could not be overcome.
In parallel I was able to manage to change the firmware to OPEN or VDF (EURO) versions ranging from v10a to v10j (using LGMDP). So it seems that there is no big issue there.
However at some point in the process (I guess the unlocking), my IMEI was changed. And my phone started to ask me to "Insert USIM card" or to refer to "Invalid USIM card" depending on if a sim was in or not. I understood that USIM was referring to international sim cards so I tried to reinstall VDF firmwares with VDF .nv2 and VDF Flex backups (still not mine), but this made my phone unusable as it displayed a nice yellow screen and the fact that some wallpaper file could not be found. Still I could solve this problem by I changing back to OPEN firmwares and .nv2.
Now I recovered the original sim card from SFR and was able to obtain the unlock code from their hotline. But as my IMEI has been changed, the unlock code fails now.
Thus I tried to reset or to change my IMEI back to what is written below the battery using either lg3g, mtty, QPST or NVEditor. This also leaded nowhere as even reading the IMEI with lg3g and mtty failed and as QPST and NVEditor revealed that the NV_UE_IMEI_I parameter was protected (NV_READONLY_S). I tried many different things with these tools but it does not seem possible to break the protection.
I guess my only chance now would be to insert my old IMEI into an existing .nv2 file. I have found some "NV2 - QCN TOOLS V1.4" that can do this but only on the KU20.
Does anyone has a tool allowing to insert a new IMEI in a .nv2 ?
OR
Did anyone go through the same difficulties and did finally find a solution ?
any help will be greatly appreciated )
please do not ask me how i did this or that for the moment, if I can solve my problem I will certainly return the favor to all of you later on.
Hello,
Have you tested the tools for the KS20, because the. NV2 is certainly quite similar.
@+
Thank you for your suggestion.
I tried the tool but first it returns a NV2 Status Error when I load any .nv2 file, second the IMEI is forced into 357323-01-XXXXXX whereas both my original and current IMEIs start with 353638-02, and third, although the tool indeed creates the file (I chose "Branded nv2"), the backup fails (LGMDP reports four NV ITEMs with NV_BADPARM_S with no more information) and I end up in Emergency mode.
A KU990 version of the tool might do the trick, if it is possible to specify the full IMEI of course. I can send my current nv2 file(s) if it can help anyone...
hi,
Can you send me by PM your backup NV2, the original IMEI and IMEI on your phone now.
By.
bl40
hello.sorry for my bad english.
a have a big problem with my lg bl40.
i flash the gsm with new rom , but i not make back up of the nv2 file.
download this file from internet but with different imei.
what can i du, pleas help my.
A valid nv2
Please can someone send a valid nv2 for lg P500, i`m from romania. many thanks
hi,
uses the search function it works fine
http://forum.xda-developers.com/showpost.php?p=22671293&postcount=52
hellp
pleace send IMIE code (nv2) for iran
my email [email protected]
tank you
So I hope this thread isn't too useless. I've been researching how to restore my imei after losing 4g signal when my phone randomly (just sitting there on the desk, not touching it), decided to get stuck in a reboot loop.
Here's my specs:
Network: AT&T
ROM: CyanogenMod 11-20141112-SNAPSHOT-M12-d2lte
Modem: UCUEMJB
Recovery: ClockworkMod 6.0.4.3
Device Model: SAMSUNG-SGH-I747
Product Code: Not Active
PDA Version:
Baseband Version: I747UCUEMJB
CSC Version:
Kernel Release: 3.4.104-cyanogenmod-g9f57632
Kernel Version: #1 SMP PREEMPT Tue Nov 11 22:15:56 PST 2014
ROM Build: d2uc-user 4.3 JSS15J I747UCUEMJB release-keys
Android Version: 4.4.4
BusyBox Version: 1.22.1
SU Binary Version: 2.40:SUPERSU
So here's what I've learned. My IMEI was lost due to a weird Samsung backup procedure that backed up my /efs folder with essentially a blank copy of important information. I have my IMEI, but writing it to the phone is very difficult. From this tutorial I learned to download QPST, and somewhere else I heard about EFS Professional.
So I tried to use EFS Professional first, and have been able to connect my phone (Had to install adb first via the official android sdk). I was able to make a backup of my efs folder. I was also able to change the usb settings to DIAG + MODEM + ADB. Then I launched the Qualcomm NV Tools. From there, by unchecking "Send SPC" and "Read Phone" I was able to connect to the phone, but any other button I pressed didn't accomplish anything except disconnecting the phone again.
This is when I turned to QPST. I knew from EFS Professional which COM port my phone was using each time, and I added the COM ports to the QPST Configuration program for listening. But my phone was never listed as available in the ports tab, nor was it listed in my device manager under COM ports. I tried using the RF NV Item Manager anyway, entering in my IMEI "backwards" with an 8 in the first line and an "a" after the first real number in my IMEI, but my phone was never really connected, so of course nothing happened.
I learned this was probably because I have no IOTHiddenMenu / Qualcomm USB Settings Menu / whatever you want to call it with USSD codes, because I'm using an AOSP ROM (Cyanogenmod). This thread and this thread were useless in enabling DIAG mode, because of broken links and scripts that no longer work on newer versions of CM.
My next plan is to change ROMs to a TouchWiz ROM, but I haven't found a good one yet, especially considering I've upgraded my bootloader and I know that if I flash a ROM with a downgraded bootloader, I'll definitely brick my phone. So is there a ROM I can use with an upgraded bootloader that won't brick my phone and will allow me to enter DIAG mode so that I can connect to QPST via a COM Port, use the RF NV Item Manager, and put in my old IMEI? Or am I just going about this all wrong?
You do have to be on a TW ROM with a stock dialer for ussd codes to work. Based on everything you posted you should be on the mjb boot loader, but confirm that first. Enter this into a terminal or adb shell:
Code:
getprop ro.bootloader
If you are on an mjb bootloader, then this ROM should work for you http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18. It's a rooted deknoxed at&t stock mjb.
Good luck.
---------- Post added at 12:04 PM ---------- Previous post was at 11:57 AM ----------
You probably already discovered this in your research, but just in case. When you get your imei problem solved, before flashing something other than a TW ROM, enter this in a terminal or adb shell:
Code:
su
reboot nvbackup
That will fix Samsung's whoops and give you a working efs backup partition instead of a blank one.
Thanks! I'll try this and get back.
alexalexalex09 said:
Thanks! I'll try this and get back.
Click to expand...
Click to collapse
You were right about the bootloader - when I looked up the ro.bootloader property, it spit back what I thought was my modem identifier, I747UCUEMJB - so yes, MJB. I'll get a chance to flash the new ROM tomorrow or the next day and see how it goes.
So, two steps forward and three steps back. I did install the new ROM. Initially, it appeared to work, because I was able to dial *#7284# to access the service mode menu and change UART to MODEM, and then dial *#0808# to access the USB Settings menu and change that to RMNET+DM+MODEM. After that, the phone showed up under COM5 in the Device Manager. I opened up QPST Configuration and added COM5 (labelled it "COM5") under ports. However, the phone never showed up (Phone column read "No Phone").
I then tried EFS Professional, but it was unable to detect the phone. I opened up the command line and tried an adb shell, but it didn't connect. Of course, the phone was in RMNET+DM+MODEM mode, not and ADB mode. I then went back into USB settings, changed it to DM+MODEM+ADB, and reconnected the phone. The phone wasn't detected by the computer, and hasn't been since.
I've restarted the phone and the computer multiple times (Windows 7 32 bit), uninstalled the phone drivers, reinstalled them in two different versions, uninstalled and reinstalled QPST (removing the relevant registry entries in between installs), and went through a number of combinations of settings on the phone. I tried with UART set to MODEM and PDA, with USB settings set to DM+MODEM+ADB, RMNET+DM+MODEM, MTP, and MTP+ADB. I made sure superuser was installed correctly and that developer mode was enabled. I still have not gotten the phone to charge in that USB port or show up in Device Manager in any way, even though the USB port on the computer still functions (can access flash drives from it). I plan to do some more googling and troubleshooting about this, but I haven't had the time to yet. On Wednesday I'll hopefully have a minute to try using my work laptop to access the phone. I think once I get the phone to be recognized via USB again I'll be able to have QPST Configuration recognize it, then I'll be able to use that RF NV Item Manager to enter in the new IMEI.
Also, in potentially unrelated news, my install of Titanium Backup is unable to recognize any apps I backed up, even ones that have been previously restored. It sees them in the backup folder (backup folder location says this folder contains 52 backups), but no apps wee listed in the backup/restore tab. Maybe this has something to do with the mount namespace separation setting in SuperSU? I'll test that later.
Some newer ROMs will install but not give you cell service without the newest bootloader and modem.
Try flashing the last release of CM11. I would not touch the bootloader, modem, or EFS folder until you try an older ROM.
audit13 said:
Some newer ROMs will install but not give you cell service without the newest bootloader and modem.
Try flashing the last release of CM11. I would not touch the bootloader, modem, or EFS folder until you try an older ROM.
Click to expand...
Click to collapse
Thanks for chiming in, but I don't understand how this applies. I was on CM11 when my IMEI was removed. When you lose your IMEI, the main symptom is that you can't connect to 4g anymore, and you're stuck on EDGE, which is what happened in my case. I can in fact make calls and send texts, and even load web pages without wifi. It's just slow and prone to call dropping.
As for your advice to install an older ROM, I just flashed a stock ROM, the one linked above. It didn't cause my current lack of USB connection, because I had a USB connection for a while until I changed the UART and USB settings.
I definitely will not touch the bootloader - I've been warned about the dangers of downgrading from an MJB bootloader. I'm not sure what you mean by not touching the modem, but I'm going to assume it's as scary/difficult as the bootloader, so I'll be sure to stay away from changing that too.
As far as not touching the EFS folder, as far as I see it, that's my only way out of this hole, because my end goal is to replace the IMEI that I randomly lost last week, and that's part of the EFS folder in some way that hasn't been explained to me (although I know it has to do with NV settings, maybe some file called nvdata.bin that I've never found, or the /EFS/IMEI folder?). So I think I have to ignore that bit of advice, unless you can give me a good reason to change my goal in all this.
alexalexalex09 said:
As far as not touching the EFS folder, as far as I see it, that's my only way out of this hole, because my end goal is to replace the IMEI that I randomly lost last week, and that's part of the EFS folder in some way that hasn't been explained to me (although I know it has to do with NV settings, maybe some file called nvdata.bin that I've never found, or the /EFS/IMEI folder?). So I think I have to ignore that bit of advice, unless you can give me a good reason to change my goal in all this.
Click to expand...
Click to collapse
I should note that I took a look at my EFS folder while writing this last post, and it's completely empty now. So that's fun.
I suggested flashing back to an older ROM because you made some changes since your original post.
I suggested not touching the bootloader, modem, and EFS because flashing an incompatible bootloader/modem combination can hard brick the phone.
Since your bootloader and modem match, I'm out of suggestions other than perhaps visiting a repair shop to have it fixed.
audit13 said:
I suggested flashing back to an older ROM because you made some changes since your original post.
I suggested not touching the bootloader, modem, and EFS because flashing an incompatible bootloader/modem combination can hard brick the phone.
Since your bootloader and modem match, I'm out of suggestions other than perhaps visiting a repair shop to have it fixed.
Click to expand...
Click to collapse
Thanks for the clarifications. I did visit a shop to see if they could fix it, and all I got were blank stares and people who don't want to deal with IMEI repairs. So back to my own attempts! I realized a couple days ago that my problem in connecting to the computer is that I've developed a crack on my phone's USB port. Also, I think my home desktop's messed up. So with a nice, sturdy cable I installed all the necessary program on my work laptop (Samsung Drivers, ADB, ES Professional, and QPST just for fun). I tried ES Professional first and by using the Qualcomm NV tools I was able to restore my IMEI! I rebooted the phone and now by dialing *#06# I see my IMEI followed by "/ 17".
So now onto the next problem: Still no 4g signal. Under Connections > More Networks > Mobile Networks, there are some errors. I only have one APN, named "ATT Phone" with an APN of "phone" and an MMSC of mmsc.mobile.att.net, and under network operator it simply says "Default Setup". Some research later, I realized this is a common problem, and I guess it has to do with my NV Data being messed up. Obviously, item 550 (0x226) is correct, which I was able to verify using a program called NV-items-reader-writer, but something else is screwed up. Peoplearmy has released a tool that can restore a backup up QCN file, which of course I don't have, so I'm in the process of seeking help from a generous soul who has an app that might help me. Apparently I could also use someone else's NV Items backup, replacing their IMEI with my own. But, I don't have one, so I'm stuck waiting on someone to be nice to me
I did try the method posted here: http://forum.xda-developers.com/showthread.php?t=1808408&page=16
But it didn't work. This thread and this thread and this thread were helpful to me for research.
alexalexalex09 said:
Thanks for the clarifications. I did visit a shop to see if they could fix it, and all I got were blank stares and people who don't want to deal with IMEI repairs. So back to my own attempts! I realized a couple days ago that my problem in connecting to the computer is that I've developed a crack on my phone's USB port. Also, I think my home desktop's messed up. So with a nice, sturdy cable I installed all the necessary program on my work laptop (Samsung Drivers, ADB, ES Professional, and QPST just for fun). I tried ES Professional first and by using the Qualcomm NV tools I was able to restore my IMEI! I rebooted the phone and now by dialing *#06# I see my IMEI followed by "/ 17".
So now onto the next problem: Still no 4g signal. Under Connections > More Networks > Mobile Networks, there are some errors. I only have one APN, named "ATT Phone" with an APN of "phone" and an MMSC of mmsc.mobile.att.net, and under network operator it simply says "Default Setup". Some research later, I realized this is a common problem, and I guess it has to do with my NV Data being messed up. Obviously, item 550 (0x226) is correct, which I was able to verify using a program called NV-items-reader-writer, but something else is screwed up. Peoplearmy has released a tool that can restore a backup up QCN file, which of course I don't have, so I'm in the process of seeking help from a generous soul who has an app that might help me. Apparently I could also use someone else's NV Items backup, replacing their IMEI with my own. But, I don't have one, so I'm stuck waiting on someone to be nice to me
I did try the method posted here: http://forum.xda-developers.com/showthread.php?t=1808408&page=16
But it didn't work. This thread and this thread and this thread were helpful to me for research.
Click to expand...
Click to collapse
I got it! Problem solved!!
So what I realized after going back over those research threads quickly was that I was using Peoplearmy's QCN generator incorrectly. Here's how I fixed it.
1. Opened QPST, followed directions here to connect my phone and start up QPST Software Download.
2. Having already injected my IMEI, I used the backup tab to make a backup.
3. I opened Peoplearmy's SG3QCNGenerator and imported the QCN file that QPST just created. I left "inject IMEI" unchecked, since I already had my original IMEI. I clicked Save As to set the directory and name of the new file, and clicked the Verify IMEI button that appeared to verify that it was correct.
This was the step I had missed - because I never had a valid QCN file to import, I never was able to create a new QCN file. My error in thinking was that, since my current QCN file was obviously messed up, I couldn't use it to make a new QCN file, but that's the whole point of this software.
4. Once I had the new QCN file, I went back to QPST's Software Download program and used the Restore tab. The QCN file generated by Peoplearmy's tool didn't match my model number, but I approved it anyway. It restored the QCN file correctly, but it had an error when it tried to reset the phone.
5. I rebooted the phone manually, and I now have 4G signal!
So, to summarize the difficulties I had:
1. I didn't make an nvbackup before I flashed CM a year ago, and it didn't hurt me until now.
2. I lost my IMEI and couldn't restore it because 1) I was on CM, which stopped me from putting my phone in DM + MODEM + ADB mode and 2) The computer/cable I was using to work on my phone, for whatever reason, were being stupid.
3. I didn't understand that in order to fix my phone I needed to restore my IMEI and repair my nv items (.qcn file)
4. I didn't realize that I could use Peoplearmy's tool to take a messed up nv items qcn file, fix it, and restore it to my phone.
All the tools I ended up needing: Samsung Drivers, ADB, ES Professional, QPST, and Peoplearmy's SG3 Data Restorer. Hope this helps someone else out there.
:good: thanks for posting fix.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Great job. Thanks for posting your solution back here so others can find it.