Related
It appears a lot of people have had this issue where the imei is wiped after flashing back via the TOT method. Not sure about KDZ method, but I wanted to use the TOT method since it's apparently a valid release, so it can take any of the OTAs as they come.
How come this is never identified in the instructions? I would think that would be a very important piece of information. Just curious.
I never backed it up. I do have the original IMEI number from the box, the receipt plus on the barcode sticker in the battery compartment.
I guess I'll have to see how to do it manually, but I'm just curious, why isn't this a warning that something like this could happen? Or, is it because I did something wrong? I know on the first try, in the LG Flash Tool, the instructions in the Verizon forums didn't state to switch from Upgrade DL to Board DL. If I do Upgrade DL, I get the big red 2 instead of the big red 3, so I searched and saw instructions saying to go to BOARD DL instead. That seemed to fix it, but now my IMEI is all messed up with zeroes.
Any ideas as to what else I might have done that could have done this? I've flashed back to 10b twice now.
Thanks!
iBolski said:
It appears a lot of people have had this issue where the imei is wiped after flashing back via the TOT method. Not sure about KDZ method, but I wanted to use the TOT method since it's apparently a valid release, so it can take any of the OTAs as they come.
How come this is never identified in the instructions? I would think that would be a very important piece of information. Just curious.
I never backed it up. I do have the original IMEI number from the box, the receipt plus on the barcode sticker in the battery compartment.
I guess I'll have to see how to do it manually, but I'm just curious, why isn't this a warning that something like this could happen? Or, is it because I did something wrong? I know on the first try, in the LG Flash Tool, the instructions in the Verizon forums didn't state to switch from Upgrade DL to Board DL. If I do Upgrade DL, I get the big red 2 instead of the big red 3, so I searched and saw instructions saying to go to BOARD DL instead. That seemed to fix it, but now my IMEI is all messed up with zeroes.
Any ideas as to what else I might have done that could have done this? I've flashed back to 10b twice now.
Thanks!
Click to expand...
Click to collapse
I don't know why it happened during your restore, but there is a G2 IMEI restore method if you'd be willing to try it on your G3: http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
It looks like a QPST tool and an IMEI converter zip file, but nothing says "LG G2" anywhere so it may work for the G3. But I've never used it though, so if you're up for a gamble...good luck
I don't envy your situation I hope you get it fixed up and if you do please fill us in how you did it. I doubt you'll be the only one this happens to.
startswithPendswithOOH said:
I don't know why it happened during your restore, but there is a G2 IMEI restore method if you'd be willing to try it on your G3: http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
It looks like a QPST tool and an IMEI converter zip file, but nothing says "LG G2" anywhere so it may work for the G3. But I've never used it though, so if you're up for a gamble...good luck
I don't envy your situation I hope you get it fixed up and if you do please fill us in how you did it. I doubt you'll be the only one this happens to.
Click to expand...
Click to collapse
UPDATE:
First off, if you EVER lose your IMEI number, then you MUST flash back to 10B. Reason being is, anything later than 10B no longer gives you access to Modem mode which is the only way I've been able to make this work.
Recently, I was TOT flashing 10b to my phone to downgrade it from MM so I could flash a custom ROM. Once again, the IMEI got lost. But I found that QPST wasn't working anymore! I even KDZ flashed back to 48A and still, QPST wouldn't work. I tried 35B, nothing. I then went back to 10B. I don't know HOW many times I did this yesterday, but my phone was out of commission all day.
Finally, this afternoon, I found this article that I wrote up and read, and re-read what I posted below and it was step 2 that stood out to me. I noticed I couldn't find Modem mode anywhere as it was listed. But, because I saw that I flashed to 10B, I decided to try it once more. So, I TOT flashed back to 10b. I still couldn't find modem mode. Then it dawned on me. I selected "Internet Connect" and viola! There it was! Once I had that, QPST worked again and I was able reprogram my IMEI.
So, if you happen to flash anything, whether it's 10b or later, and you find that your IMEI is gone, you must flash back to 10b. QPST will not work on anything later (at least, 47/48A for sure). I've also tried 35B and it won't work. You MUST have 10b so that you can select modem mode. I was unable to get it to work on any other version.
I was able to find my IMEI on my receipt which is stored in my MyVerizon documents section of my account. But, it's also located on the label in the battery compartment, so if you no longer have your box or receipt, open up the G3 and remove the battery and you'll see the IMEI number on the sticker there.
I skipped the entire portion of the Backup and Restore EFS on LG G2 section. No reason for that since I wiped the IMEI for some reason during the restore.
Next, I followed the steps in the Restore Lost IMEI on LG G2 section as follows:
Here are the files to download:
LG USB drivers
IMEI-Converter.zip [mirror link]
QPST_2.7_378.zip
After downloading all the files (IMEI-Converter and QPST_2.7_378.zip. Didn't install drivers as I already had them) and installing the QPST tools, I followed the directions. I didn't attempt to backup the IMEI since it's gone.
First, I put my phone into debugging mode and switched it to modem mode (on 10b). To do this, you need to ensure your phone is connected. Go to the notifications area and select "USB Connected". From there, select "Internet connect" and then select "Modem". You must do this or QPST will not work.
Connected device to PC and ran QPST configuration and added the new port. Mine was already on port 41 due to the TOT restore, so Ieft it at that.
Skipped all the steps on backing up. I would do this AFTER I restored the IMEI.
Ran the C:\Program Files (x86)\qualcomm\qst\bin\RF_NV_Manager.exe program.
Went to Setting->Comport and set it to 41.
Clicked on File->Read from phone and navigated down to the 550 line which showed the IMEI was blank, which we already know is true.
Clicked on File->Read supported RF NV items.
Ran the IMEI Converter.exe (after extracting it) and typed in my IMEI number for my phone. This converts it into 9 groups of hexadecimal numbers.
In the RV_NV_Manager program, selected the 550 line and put a check mark in the hex check box.
Taking each hex value from the converter program, I entered the numbers into the 9 text boxes. The left-most set went in the first text box, and so on.
Clicked the "Write NV" button to write the values back to the phone.
Clicked File->Read from phone and verified that item number 550 contained my correct IMEI number.
Disconnected the phone from the USB cabled, rebooted and all was golden. Verified on my MyVerizon page that my phone was no longer an unsupported device anymore.
iBolski said:
Thanks for the link. That was actually what I found and used. LOL!
In any case, it DOES work. I was able to fix it. Basically...
Cool. Good info to know. And congrats
Click to expand...
Click to collapse
I have the same problem of vanished imei. I was trying to write the IMEI using RF NV Manager but when I click write I get error NvManager :write to phone- unable to write NV_UE_IMEI_I to phone(parameter is write protected and thus read only).
Somebody please help to bring my phone alive.
---------- Post added at 10:47 PM ---------- Previous post was at 10:16 PM ----------
Well setting the phone USB connection mode to ethernet solved the problem .
Settings>storage>usb pc connection>internet connection>ethernet. Need to be in the 10B version to be able to do this.
iBolski said:
Thanks for the link. That was actually what I found and used. LOL!
In any case, it DOES work. I was able to fix it. Basically, I was able to find my IMEI on my receipt which is stored in my MyVerizon documents section of my account. But, it's also located on the label in the battery compartment, so if you no longer have your box or receipt, open up the G3 and remove the battery and you'll see the IMEI number on the sticker there.
Basically, I skipped the entire portion of the Backup and Restore EFS on LG G2 section. No reason for that since I wiped the IMEI for some reason during the restore.
Next, I followed the steps in the Restore Lost IMEI on LG G2 section as follows:
After downloading all the files (IMEI-Converter and QPST_2.7_378.zip. Didn't install drivers as I already had them) and installing the QPST tools, I followed the directions. I didn't attempt to backup the IMEI since it's gone.
First, I put my phone into debugging mode and switched it to modem mode (on 10b)
Connected device to PC and ran QPST configuration and added the new port. Mine was already on port 41 due to the TOT restore, so Ieft it at that.
Skipped all the steps on backing up. I would do this AFTER I restored the IMEI.
Ran the C:\Program Files (x86)\qualcomm\qst\bin\RF_NV_Manager.exe program.
Went to Setting->Comport and set it to 41.
Clicked on File->Read from phone and navigated down to the 550 line which showed the IMEI was blank, which we already know is true.
Clicked on File->Read supported RF NV items.
Ran the IMEI Converter.exe (after extracting it) and typed in my IMEI number for my phone. This converts it into 9 groups of hexadecimal numbers.
In the RV_NV_Manager program, selected the 550 line and put a check mark in the hex check box.
Taking each hex value from the converter program, I entered the numbers into the 9 text boxes. The left-most set went in the first text box, and so on.
Clicked the "Write NV" button to write the values back to the phone.
Clicked File->Read from phone and verified that item number 550 contained my correct IMEI number.
Disconnected the phone from the USB cabled, rebooted and all was golden. Verified on my MyVerizon page that my phone was no longer an unsupported device anymore.
Click to expand...
Click to collapse
Thnks so much i mean so much, my imei is erased after using the LGFlashtool and imagined the worst, even i think sell it in parts, but I followed your instructions and my IMEI is back in my cell. Now my question is, did he do that was erased, now I'm in stock room 10b and want to put Lollipop, but after this experience and it scares me. at all, especially if I'm in another country and I can not take it to be repaired so easily with Verizon.
Anyway, thnks again works for me into Verizon Wirless Vs985 from México
My English was sponsored by Google translator
Siylar said:
Thnks so much i mean so much, my imei is erased after using the LGFlashtool and imagined the worst, even i think sell it in parts, but I followed your instructions and my IMEI is back in my cell. Now my question is, did he do that was erased, now I'm in stock room 10b and want to put Lollipop, but after this experience and it scares me. at all, especially if I'm in another country and I can not take it to be repaired so easily with Verizon.
Anyway, thnks again works for me into Verizon Wirless Vs985 from México
My English was sponsored by Google translator
Click to expand...
Click to collapse
If you are not rooted yet, then you can take the OTAs all the way to LP. If you do root, you can only get to 12b. You won't be able to go to LP, so you would have to flash back to 10b again. There is a 12b KDZ somewhere that will also allow you to upgrade to LP if you want to go that route. The only thing that has me a little worried about it (and it's probably nothing) is that when you flash back to 12b stock via KDZ, it states the software is modified, but it still will take the LP OTA, so go figure! LOL!
As for the IMEI being wiped again, that shouldn't happen if you are taking the official OTAs. For me, when I did the TOT flash back to 10b, that was the first time I did it and who knows what I did. I probably did something wrong because the second time I flashed back to 10b (so I could upgrade to the official LP OTA), my IMEI wasn't wipe, so I have to think I did something wrong the first time.
In any case, taking the official OTAs should not wipe your IMEI so you should be good to go.
Worse comes to worse, if it does get wiped, just do the steps outlined above and you'll be back in business.
So I had a replacement phone sent to me and this phones ieme is wiped due to a similar experience to yours. My question is, do I HAVE to use the ieme that came with my phone? Or can I use the one that is on my replacement phone right now?
swimmerhair said:
So I had a replacement phone sent to me and this phones ieme is wiped due to a similar experience to yours. My question is, do I HAVE to use the ieme that came with my phone? Or can I use the one that is on my replacement phone right now?
Click to expand...
Click to collapse
You could use either imei as long as they are both for the same model of phone. I have 2 LG G2s. The imei on one got swapped to an imei for some other model. It sort of worked but I kept getting mobile network disconnections (on straight talk). I couldn't update software because the imei wasn't an LG G2. I didn't have a record of my imei for that phone, so I used the imei of my other Lg g2 which was inop with a cracked screen. Once I put a valid lg g2 imei on it everything worked correctly again and I could update software. Still on straight talk with no more network problems.
Awesome! I have been dealing with Big Red for a week now because their Fraud Prevention is meddling in my business. This will make things a little easier in the meantime. Thanks again! I will post and let everyone know how it goes.
Sorry for reviving an old thread but if I tot back to 10b from the xdabbeb version of 35B, will that be the way to go about it? Am I at a risk of hard brick?
nagi_007pk said:
Sorry for reviving an old thread but if I tot back to 10b from the xdabbeb version of 35B, will that be the way to go about it? Am I at a risk of hard brick?
Click to expand...
Click to collapse
Yes to the first question, and every time we do something with our phone that LG and Verizon don't intend for us to do with our phone we risk either soft or hard bricking.
iBolski said:
Thanks for the link. That was actually what I found and used. LOL!
In any case, it DOES work. I was able to fix it. Basically, I was able to find my IMEI on my receipt which is stored in my MyVerizon documents section of my account. But, it's also located on the label in the battery compartment, so if you no longer have your box or receipt, open up the G3 and remove the battery and you'll see the IMEI number on the sticker there.
Basically, I skipped the entire portion of the Backup and Restore EFS on LG G2 section. No reason for that since I wiped the IMEI for some reason during the restore.
Next, I followed the steps in the Restore Lost IMEI on LG G2 section as follows:
Here are the files to download:
After downloading all the files (IMEI-Converter and QPST_2.7_378.zip. Didn't install drivers as I already had them) and installing the QPST tools, I followed the directions. I didn't attempt to backup the IMEI since it's gone.
First, I put my phone into debugging mode and switched it to modem mode (on 10b)
Connected device to PC and ran QPST configuration and added the new port. Mine was already on port 41 due to the TOT restore, so Ieft it at that.
Skipped all the steps on backing up. I would do this AFTER I restored the IMEI.
Ran the C:\Program Files (x86)\qualcomm\qst\bin\RF_NV_Manager.exe program.
Went to Setting->Comport and set it to 41.
Clicked on File->Read from phone and navigated down to the 550 line which showed the IMEI was blank, which we already know is true.
Clicked on File->Read supported RF NV items.
Ran the IMEI Converter.exe (after extracting it) and typed in my IMEI number for my phone. This converts it into 9 groups of hexadecimal numbers.
In the RV_NV_Manager program, selected the 550 line and put a check mark in the hex check box.
Taking each hex value from the converter program, I entered the numbers into the 9 text boxes. The left-most set went in the first text box, and so on.
Clicked the "Write NV" button to write the values back to the phone.
Clicked File->Read from phone and verified that item number 550 contained my correct IMEI number.
Disconnected the phone from the USB cabled, rebooted and all was golden. Verified on my MyVerizon page that my phone was no longer an unsupported device anymore.
Click to expand...
Click to collapse
So I tried the steps inside of here. There was issues with it reading my phone. I am in the process of getting back to 10b so that I can try from there but I am not sure that will help. PM me for screen shots cause I can't attach yet. hxxp://tinypic.com/r/2j5o20o/9 hxxp://tinypic.com/r/2ivz7up/9 hxxp://tinypic.com/r/29ngqoy/9
Darkblaze1 said:
So I tried the steps inside of here. There was issues with it reading my phone. I am in the process of getting back to 10b so that I can try from there but I am not sure that will help. PM me for screen shots cause I can't attach yet. hxxp://tinypic.com/r/2j5o20o/9 hxxp://tinypic.com/r/2ivz7up/9 hxxp://tinypic.com/r/29ngqoy/9
Click to expand...
Click to collapse
So I solved my own issue. Didn't mean to revive an old thread. I am doing kdz to 5.1 then the upgrade to 35b for stock. (Needing to keep stock for work reasons and for Airwatch Agent (unless anyone knows how to make it work on AOSP))
thank u ................................................)(
Darkblaze1 said:
So I solved my own issue. Didn't mean to revive an old thread. I am doing kdz to 5.1 then the upgrade to 35b for stock. (Needing to keep stock for work reasons and for Airwatch Agent (unless anyone knows how to make it work on AOSP))
Click to expand...
Click to collapse
While you're on 10b, root, install twrp, and backup your efs. This will make it painless to restore your imei should you lose it again. I wish I did this the first time.
I realize that this is an old thread but I am hoping that someone can help. I went back to 10b and, in doing so, I lost my imei. I have tried to follow the steps in this guide but I keep getting an error in step 7 when I try to read from the phone in RF NV Manager.
NvManager::getNvItemsFromPHone (const String comPort) - QpstServer::sendSyncImpl - Bad response from phone (DM Packet commants 19 - 24)
If I skip step 7, I can do all the steps until 12. When I try to write to the phone, I get the following error message.
NvManager:::writeToPhone( const string comPort) - QpstServer:::initialize - Unable to attach to the QPST server.
Any help would be greatly appreciated.
hamillp said:
I realize that this is an old thread but I am hoping that someone can help. I went back to 10b and, in doing so, I lost my imei. I have tried to follow the steps in this guide but I keep getting an error in step 7 when I try to read from the phone in RF NV Manager.
NvManager::getNvItemsFromPHone (const String comPort) - QpstServer::sendSyncImpl - Bad response from phone (DM Packet commants 19 - 24)
If I skip step 7, I can do all the steps until 12. When I try to write to the phone, I get the following error message.
NvManager:::writeToPhone( const string comPort) - QpstServer:::initialize - Unable to attach to the QPST server.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Make sure you are back to 10b. You cannot use the tool to fix your IMEI after 10b. It won't find the phone. I wiped my IMEI a few months ago and followed my own directions (since I'm the one that posted this lol) and completely forgot that you had to do it in 10b. I wiped my IMEI, flashed back to 47A and attempted to fix my IMEI that way. Nope. Won't work. The tool requires you to be on 10b in order to be found.
If you are on 10b, make sure you select the correct port. It SHOULD be 41 since that's what was last used when you flashed the 10B tot. Remember, you must also be booted into your phone, not in download mode. Once you hook the phone up, be sure you've selected the correct mode. My G3 has died since then so I can't remember it off the top of my head, but it SHOULD be in here explaining how to get to that mode. I think it's Modem mode.
Then hook up the phone and the software should find it and allow you to fix your IMEI number.
iBolski said:
Make sure you are back to 10b. You cannot use the tool to fix your IMEI after 10b. It won't find the phone. I wiped my IMEI a few months ago and followed my own directions (since I'm the one that posted this lol) and completely forgot that you had to do it in 10b. I wiped my IMEI, flashed back to 47A and attempted to fix my IMEI that way. Nope. Won't work. The tool requires you to be on 10b in order to be found.
If you are on 10b, make sure you select the correct port. It SHOULD be 41 since that's what was last used when you flashed the 10B tot. Remember, you must also be booted into your phone, not in download mode. Once you hook the phone up, be sure you've selected the correct mode. My G3 has died since then so I can't remember it off the top of my head, but it SHOULD be in here explaining how to get to that mode. I think it's Modem mode.
Then hook up the phone and the software should find it and allow you to fix your IMEI number.
Click to expand...
Click to collapse
Thanks for the reply. Yes, I am on 10b. I did use port 41. I was in modem mode. I even tried to do it in ethernet mode as well but that didn't work. It shows an unknown phone connected in the QPST configuration tool. It shows com 41 and that it is enabled. Everytime I get to a step where it has to interact with the phone, however, I get an error.
Anyone know what this error means:
NvManager::getNvItemsFromPHone (const String comPort) - QpstServer::sendSyncImpl - Bad response from phone (DM Packet commants 19 - 24)
More importantly, anyone know how to fix it?
First off, thanks for tolerating this somewhat noobish post, but I've searched through almost the whole internet trying to find answers.
Alright, so here's the dealio.
Sprint Galaxy Note 3. UICC unlocked via idoneapp, then used on domestic T-Mobile through GCF settings. I want to enable more bands as described in the following links: here and here.
I get as far as Step 9 in the second link. Then, I go to select a port, and it's not there. OK, so I uncheck the "diagnostic port only" check box, and select COM12 which is what my phone is on. No big deal, right? So I go to read/backup my NV and I start it; it only gets to 12% and says "Could not Communicate in Diagnostic Mode"
That's it. I've tried different USB ports, different USB cables, other USB modes on the phone, I even have a custom kernel. I really hope it's something obvious that I'm doing wrong instead of something that's a niche error.
Thanks, guys.
I ended up being able to read the LTE bands with DFS and write them with QXDM. The only thing is that there is no LTE/GSM/UMTS mode on the phone, so it's either LTE/CDMA or GSM/UMTS for now until I figure out if I can flash some other ROM to it to let it use the other bands, cause right now it only wants to look at band 25.
So I've been trying to flash the N900T MI7 modem/baseband on my N900P but I can never get it to flash in Odin. I've been able to put the modem and non-hlos in flash able zips and flash those but it never shows up. I've also tried to dd the files directly but that doesn't work either. Ideas?
I am impressed it's not bricked yet.
Sent from my SM-G935F using XDA-Developers mobile app
Same issue
BlockOfDynamite said:
First off, thanks for tolerating this somewhat noobish post, but I've searched through almost the whole internet trying to find answers.
Alright, so here's the dealio.
Sprint Galaxy Note 3. UICC unlocked via idoneapp, then used on domestic T-Mobile through GCF settings. I want to enable more bands as described in the following links: here and here.
I get as far as Step 9 in the second link. Then, I go to select a port, and it's not there. OK, so I uncheck the "diagnostic port only" check box, and select COM12 which is what my phone is on. No big deal, right? So I go to read/backup my NV and I start it; it only gets to 12% and says "Could not Communicate in Diagnostic Mode"
That's it. I've tried different USB ports, different USB cables, other USB modes on the phone, I even have a custom kernel. I really hope it's something obvious that I'm doing wrong instead of something that's a niche error.
Thanks, guys.
Click to expand...
Click to collapse
I am facing same issue regarding back up nv at 12%
vipsy6 said:
I am facing same issue regarding back up nv at 12%
Click to expand...
Click to collapse
So basically what happened was I found a couple other tools to do what I wanted. First was DFS tool. This works well, because it can both read and write bands to the nv of the phone. I forget what the second was, but it could both read and write the raw value of any given value in the nvram. I'll have to dig through my stuff again if you want to know what the second program was. The fact of the matter is that I was never able to get it working right. The phone always looked at band 25 LTE no matter what bands I turned on/off of the phone.
another ?
BlockOfDynamite said:
So basically what happened was I found a couple other tools to do what I wanted. First was DFS tool. This works well, because it can both read and write bands to the nv of the phone. I forget what the second was, but it could both read and write the raw value of any given value in the nvram. I'll have to dig through my stuff again if you want to know what the second program was. The fact of the matter is that I was never able to get it working right. The phone always looked at band 25 LTE no matter what bands I turned on/off of the phone.
Click to expand...
Click to collapse
Please let me know second program
BlockOfDynamite said:
First off, thanks for tolerating this somewhat noobish post, but I've searched through almost the whole internet trying to find answers.
Alright, so here's the dealio.
Sprint Galaxy Note 3. UICC unlocked via idoneapp, then used on domestic T-Mobile through GCF settings. I want to enable more bands as described in the following links: here and here.
I get as far as Step 9 in the second link. Then, I go to select a port, and it's not there. OK, so I uncheck the "diagnostic port only" check box, and select COM12 which is what my phone is on. No big deal, right? So I go to read/backup my NV and I start it; it only gets to 12% and says "Could not Communicate in Diagnostic Mode"
That's it. I've tried different USB ports, different USB cables, other USB modes on the phone, I even have a custom kernel. I really hope it's something obvious that I'm doing wrong instead of something that's a niche error.
Thanks, guys.
Click to expand...
Click to collapse
hi
how did you connect QPST to your phone? i can't do it,
installed QPST under windows 7, QDXM and kies, but in QPST configuration i get "No Phone" when added new port
walidham said:
hi
how did you connect QPST to your phone? i can't do it,
installed QPST under windows 7, QDXM and kies, but in QPST configuration i get "No Phone" when added new port
Click to expand...
Click to collapse
I never did get QPST to connect to my phone. I think I was able to get it to see the phone at some point, but it would never read anything from it or write anything to it. The program always froze up or something when I tried that. If I could remember the second program I used, I'd share it with you all, but for the life of me, I can't think of it.
Edit: Oh hey, the two programs I used are RIGHT IN MY SECOND POST. lol. Yeah, use DFS tool to read the NV and QXDM to write the NV. It'll save you a whole lot of trouble over doing stuff with QPST.
BlockOfDynamite said:
I never did get QPST to connect to my phone. I think I was able to get it to see the phone at some point, but it would never read anything from it or write anything to it. The program always froze up or something when I tried that. If I could remember the second program I used, I'd share it with you all, but for the life of me, I can't think of it.
Edit: Oh hey, the two programs I used are RIGHT IN MY SECOND POST. lol. Yeah, use DFS tool to read the NV and QXDM to write the NV. It'll save you a whole lot of trouble over doing stuff with QPST.
Click to expand...
Click to collapse
Hi
Yes i used only DFS tools and it work fine, also and changed my Bands 4G and 3G to work in Europe with Spint N900P phone,
3G work fine but not 4G, i will install custom Rom and see if it will work.
walidham said:
Hi
Yes i used only DFS tools and it work fine, also and changed my Bands 4G and 3G to work in Europe with Spint N900P phone,
3G work fine but not 4G, i will install custom Rom and see if it will work.
Click to expand...
Click to collapse
Well, 3G will work fine without changing anything anyway. All of the bands are already enabled. 4G is the issue.
BlockOfDynamite said:
Well, 3G will work fine without changing anything anyway. All of the bands are already enabled. 4G is the issue.
Click to expand...
Click to collapse
Yes 4G is the big pb, i found that DFS Tools write 3G bands but for LTE, the issue is in BC Config Div, need SPC code
i tried to find SPC /MSL code but no chance
I will install SPR-N900PVPUBMJ4 rom and after SPR-N900PVPUBMJ3 modem and use DSF tools to set it 000000
hope i will work
walidham said:
Yes 4G is the big pb, i found that DFS Tools write 3G bands but for LTE, the issue is in BC Config Div, need SPC code
i tried to find SPC /MSL code but no chance
I will install SPR-N900PVPUBMJ4 rom and after SPR-N900PVPUBMJ3 modem and use DSF tools to set it 000000
hope i will work
Click to expand...
Click to collapse
Flash the MI3 (that's emm eye three) modem and then use the app included in the zip file to find the MSL code. Here's a link to the zip file: http://bit.ly/1oZDO9t
I was not aware that you could change the MSL code with DFS tools. At least I have a Verizon Note 3 now, so I have a lot more LTE bands than the Sprint version does (although I don't care all that much; I think I may switch to the Nexus 6 soon). But yeah, try the stuff in the zip file from the link, and you should be able to
Find your MSL code
Unlock your phone internationally
Use hidden menus
Most of all, have fun! I know for sure this can be very very frustrating a lot of the time, but if you don't have fun, then I don't think there's much profit in trying stuff like this. Good luck!
BlockOfDynamite said:
Flash the MI3 (that's emm eye three) modem and then use the app included in the zip file to find the MSL code. Here's a link to the zip file: http://bit.ly/1oZDO9t
I was not aware that you could change the MSL code with DFS tools. At least I have a Verizon Note 3 now, so I have a lot more LTE bands than the Sprint version does (although I don't care all that much; I think I may switch to the Nexus 6 soon). But yeah, try the stuff in the zip file from the link, and you should be able to
Find your MSL code
Unlock your phone internationally
Use hidden menus
Most of all, have fun! I know for sure this can be very very frustrating a lot of the time, but if you don't have fun, then I don't think there's much profit in trying stuff like this. Good luck!
Click to expand...
Click to collapse
After many try, finaly i get my MSL code (24 hours).
I have downgrad my phone to 4.4.2, and install custom rom Galaxy-Note-fre3-2.26,
and after using adb and logcat i got my code.
Now how can i activate it for internationally ? i have added all LTE band (3,7,20) but still H+
I will try with QXDM, but i have windows 10 and give me error acces denied.
walidham said:
After many try, finaly i get my MSL code (24 hours).
I have downgrad my phone to 4.4.2, and install custom rom Galaxy-Note-fre3-2.26,
and after using adb and logcat i got my code.
Now how can i activate it for internationally ? i have added all LTE band (3,7,20) but still H+
I will try with QXDM, but i have windows 10 and give me error acces denied.
Click to expand...
Click to collapse
I just did it with my Verizon Note 3 on Windows 10, so I know it's not a Windows 10 issue. Also, QPST seemed to work with my Verizon phone but not my Sprint phone. Weird. Make sure you're running QXDM as administrator. Also, I unlocked all of the LTE bands in this way but I can't seem to get LTE from my GSM sim card, even by going into the service mode and enabling all LTE bands.
BlockOfDynamite said:
I just did it with my Verizon Note 3 on Windows 10, so I know it's not a Windows 10 issue. Also, QPST seemed to work with my Verizon phone but not my Sprint phone. Weird. Make sure you're running QXDM as administrator. Also, I unlocked all of the LTE bands in this way but I can't seem to get LTE from my GSM sim card, even by going into the service mode and enabling all LTE bands.
Click to expand...
Click to collapse
Yes; for LTE i found in hiddn menu, that they use Tri Bands (25, 26 & 41), so for others bands will not work.
I don't know how i can disable this and force it to use bands 3, 7 20.
walidham said:
Yes; for LTE i found in hiddn menu, that they use Tri Bands (25, 26 & 41), so for others bands will not work.
I don't know how i can disable this and force it to use bands 3, 7 20.
Click to expand...
Click to collapse
I honestly couldn't tell you, and I'm not sure how much help I'm going to be in general. I've tried it on both of my Note 3 phones but have had no confirmed success. Sprint especially is the one carrier that sticks out like a sore thumb, and by association, so do their phones. I've had plenty of frustration on that front, that's for sure.
BlockOfDynamite said:
I honestly couldn't tell you, and I'm not sure how much help I'm going to be in general. I've tried it on both of my Note 3 phones but have had no confirmed success. Sprint especially is the one carrier that sticks out like a sore thumb, and by association, so do their phones. I've had plenty of frustration on that front, that's for sure.
Click to expand...
Click to collapse
Thanks for your help,
Just one question if have any idea for it
can i install Firmware N9005 using PIT file for N90005 in N900P?
Because when i received my phone(from china) , the first time i see that BaseBand version is for n9005 and phone name n900 but in download mode i see n900p
i think chines have a method to do it
walidham said:
Thanks for your help,
Just one question if have any idea for it
can i install Firmware N9005 using PIT file for N90005 in N900P?
Because when i received my phone(from china) , the first time i see that BaseBand version is for n9005 and phone name n900 but in download mode i see n900p
i think chines have a method to do it
Click to expand...
Click to collapse
Maybe. Really they have a method to do anything I would advise against trying to do that, although I'm not sure what harm it could do if you can still get back into download mode. I've tried flashing different versions' firmware to the N900P with no success.
Hello,
I'm here trying to get help to solve a LG L65 D280n with the null IMEI problem.
I'm hopping there's no problem with the hardware as it was working ok and didn't fall or something else. It just got that way and it was nw unlocked some months ago.
Well, I've 1srt search and follow many youtube videos and read a lot of threads.
At 1srt I've tried to use official software form LG. LG mobile tool and drivers.
I download and install them everything goes well, phone is detected and after usb connection the firmware download started.
Problem was, after the point that it decompress the firmware and it was supposed to start copying it to the phone, the LG app just hangs with the windows error as it stops responding.
Using a machine with Win7 Pro x64.
From this saved the LG kdz file and the dll file that was downloaded.
I can't get another because the links from:
http://redirect.viglink.com/?format...g-phone-firmware.com/firmwar...-Tutti-50.html
are broken to the Europe/Portuguese version A or B of this phone that was original from MEO/TMN
Then I've tried another LG tool, older I believe. It requires qualcomm software, visual c++ etc.
All went well until I've selected a com port at the QPST configuration and then at the RF NV manager were I would try to write the IMEI it fails.
I select the COM port I've added before at the QPST configuration app but when I select the READ from phone option it just returns error ... DM command 19-24.
I was hopping to flash the modem only or to write the IMEI manually but its getting hard to solve the communication problem even after trying in different computer and with 3 version of drivers and software.
Recovery mode only shows if I wanna do factory reset, I did.
Can someone help?
Tried also EFS Professional now using Qualcomm NV tools, I can select the phone COM port but if I try to connect to it with 000000 Send SPC option on, It returns error, unable to send SPC to the phone.
So i recently decided to unlock my LG G5 H850 bootloader, installed TWRP, backed up everything I could, rooted my device. Thought why not update to Nougat so I wiped my phone and installed LineageOS. I didn't like it to much so I wiped again and installed Fulmics ROM. After flashing this ROM I noticed that my mobile data could not be used so I thought it was a simple bug wiped and flashed again. Switched back to LineageOS then stock still with no mobile data. I am currently on the Fulmics ROM realizing that I no longer have an IMEI number in my phone. In Settings>About Phone>Status my phone number, IMEI and IMEI SV all show as "Unknown." Typing in *#06# comes back as "null."
I have looked all over the place, tried different things such as going to 6.0.1 and installing some modules to change IMEI from xposed but they always crashed. I've looked at fourms from other websites, downloaded exe programs onto my pc. I cant figure out a way to get my IMEI back. This is my main phone, I cant switch the sim card to my Nexus 5 unless i have a sim card adapter so it fits.
Any help would be great since i never knew this was a possibility.
sharks2418 said:
So i recently decided to unlock my LG G5 H850 bootloader, installed TWRP, backed up everything I could, rooted my device. Thought why not update to Nougat so I wiped my phone and installed LineageOS. I didn't like it to much so I wiped again and installed Fulmics ROM. After flashing this ROM I noticed that my mobile data could not be used so I thought it was a simple bug wiped and flashed again. Switched back to LineageOS then stock still with no mobile data. I am currently on the Fulmics ROM realizing that I no longer have an IMEI number in my phone. In Settings>About Phone>Status my phone number, IMEI and IMEI SV all show as "Unknown." Typing in *#06# comes back as "null."
I have looked all over the place, tried different things such as going to 6.0.1 and installing some modules to change IMEI from xposed but they always crashed. I've looked at fourms from other websites, downloaded exe programs onto my pc. I cant figure out a way to get my IMEI back. This is my main phone, I cant switch the sim card to my Nexus 5 unless i have a sim card adapter so it fits.
Any help would be great since i never knew this was a possibility.
Click to expand...
Click to collapse
Try and restore your EFS partition from TWRP with the first backup you made.
mass/cls/ said:
Try and restore your EFS partition from TWRP with the first backup you made.
Click to expand...
Click to collapse
I've done this multiple times already.
sharks2418 said:
I've done this multiple times already.
Click to expand...
Click to collapse
I've just sent you a PM regarding this issue and a possible fix.
@mass/cls/ I have an lg v20 that is having issues with it's cell service, could you point me in the right direction for how to get NV Tools to see the phone(put it in RMNET + DM + MODEM usb mode)
ajairola said:
@mass/cls/ I have an lg v20 that is having issues with it's cell service, could you point me in the right direction for how to get NV Tools to see the phone(put it in RMNET + DM + MODEM usb mode)
Click to expand...
Click to collapse
In order for it to see the phone you need to enable the port check option in the hidden menu first it's under "SVC MENU", after doing this plug your phone into your pc and select File Transfer.
After doing this you will see in the device manager the new usb com port and you will be able to use EFS Professional with it.
To sharks2418
I had this problem too (loosing IMEI) after flashing Nougat 7. For me helped flashing bootloader for Nougat 7. IMEI restored.
http://downloads.codefi.re/autoprime...Bootloader.zip
I have this problem with my AT&t LG G5 H820. Phone is not rooted, as if you didn't already know after reading the first line. I don't know how or what I did but can't figure out a fix.
Sent from my LG-H820 using Tapatalk
I removed my SIM and inserted it into a different phone, works fine and then put the SIM from the different phone into the g5 and get the same result (IMEI null-null, no service, no baseband, and the ins settings in hidden menu are blank. Crc wizard show SIM not inserted. Anyone?Anyone?
Sent from my LG-H820 using Tapatalk
same prolem .unrooted lost imei
If phone on Marshmallow (MM, Android 6), ROM (from 10a till 10g version), bootloader must be from Marshmallow. If phone on Nougat (N, Android 7), ROM (from 20a till 20d version), bootloader must be from Nougat. If ROM from one system, bootloader from another, will be lost IMEI. Bootloaders can find: http://downloads.codefi.re/autoprime/LG/LG_G5/
LG V10 H90121j bricked after update which was successfully completed but phone does not turned on after that. I manage to unbrick through H90020w qfil and get access to update firmware screen. Now again every H901 kdz updated 100% but phone again bricks and not turning on. Please help me to restore my phone. I think I should unbrick with H901 qfil instead of H90020w. Please support.
Shan1122 said:
LG V10 H90121j bricked after update which was successfully completed but phone does not turned on after that. I manage to unbrick through H90020w qfil and get access to update firmware screen. Now again every H901 kdz updated 100% but phone again bricks and not turning on. Please help me to restore my phone. I think I should unbrick with H901 qfil instead of H90020w. Please support.
Click to expand...
Click to collapse
Dear shan, sould have read these forums before updating, I had the same misfortune when i updated my v10 through LG bridge, chances are you have a refurbished phone like me, where the motherboard is of a different version/country/carrier than the software, I have a korean f600l which i came to know after bricking my phone, the only ,method to revive it is to use the h90020w method but it will convert your tmobile to AT&t with fingerprint , vpn issues, unable to uninstall apps and in extreme cases like mine no radio, but atleast it works that fine for me, but if you want to make calls then dont go for it, first identify your board then ask for help from other senior members ,or others who have the same model . andn please do update if you are successful so that others may benefit from your method.
last gspian said:
Dear shan, sould have read these forums before updating, I had the same misfortune when i updated my v10 through LG bridge, chances are you have a refurbished phone like me, where the motherboard is of a different version/country/carrier than the software, I have a korean f600l which i came to know after bricking my phone, the only ,method to revive it is to use the h90020w method but it will convert your tmobile to AT&t with fingerprint , vpn issues, unable to uninstall apps and in extreme cases like mine no radio, but atleast it works that fine for me, but if you want to make calls then dont go for it, first identify your board then ask for help from other senior members ,or others who have the same model . andn please do update if you are successful so that others may benefit from your method.
Click to expand...
Click to collapse
hey, sorry for late reply. Thank you for your answer. I got solution but as you said, with no Radio, I cannot make calls. my imei shows only 0-17. I think my imei totally erased. my methode was to debrick with file H90021w and then flash with H90021w.dz file. I convert kdz file to dz file by using LG_Firmware_Extract_v1.2.6.1. these files are available on internet. I got my phone back to life but without network. Phone is booting with AT&T logo and working fine other then network issue.
can anyone help me with network issue now?