I upgraded my new 6800 yesterday using the directions Here.
I upgraded to Olipro 2.40, CDMA Radio 3.42.02 , and DCD Titans 3.20 ROM. The upgrade went smooth enough. I was unable to use my 1GB microSD card but I was able to use USB. When I was finished I installed the verizon carrier cab. I called *228 to program my phone. Programming failed and it failed because my ESN was now set to all zeros. I attempted to reset the ESN using CDMA workshop and the instructions in the troubleshooting section of the wiki. It failed and now CDMA workshop is unable to access my ESN at all. See my previous post. When CDMA workshop reads from the phone it pulls all the info except for the ESN and the Number fields . It says ':: Failed ::" in the phone information box on the left for both of those fields. It also gives me an error "Cant read EFS" when I try to pull up the phones setting using ESF. It is like some portions of the phone are now locked (or deleted).
I decided to try to flash back to the original stock ROM and I am unable to do so. I am unable to reflash my bootloader, the radio, or the DCD ROM. I cant do it using the microSD and when I try doing it via USB I get an Error 328, Invalid Command. My phone boots fine but I cant change any of the ROMS. I can also see all my phones programming settings using ##3424, using CDMA workshop, and QPST) but I am unable to change any of them. It is like my phone is partially locked.
My current bootloader says
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
and during startup it says:
M 09
B03
P DCAAXAM-4350H
R 3.42.30
D 3.20
Since I cant access the ESN to change it, my phone is not usable. Can anyone help me reset my esn to the correct value? Any suggestions on what to try myself or do I need to send it to someone with the correct tools? or is my phone beyond repair? If you need additional information, I can provide that as well. Thanks.
I'm looking into it for you. Give me a little.
gc14 said:
I'm looking into it for you. Give me a little.
Click to expand...
Click to collapse
Thank you very much for any assistance you can give me.
Have you tried ##778 enter 000000 for the unlock code. Use edit. Just a thought, we may be talking about 2 different things.
Ga. Medic said:
Have you tried ##778 enter 000000 for the unlock code. Use edit. Just a thought, we may be talking about 2 different things.
Click to expand...
Click to collapse
I did try that but when I had EPST in edit mode, I could only change a few of the values and the ESN was not one of them.
I was able to fix my phone. I tried to re-flash my phone again back to stock but this time I tried it using my laptop. I still could not get the microSD method to work but USB did work this time. When I was finished, my esn was reset again to all zeros (previously it had been a mix of my real esn and zeros like 35782000). I ran CDMA workshop again and this time the change from all zeros to the correct ESN was successful. My phone also activated successfully using *228.
Hey everyone,
After finally getting my S3 I wanted to check out some stuff in QPST, but I can't seem to get the phone to be properly recognized by the program.
I was able to use the dialer code *#7284# to get into PhoneUtil but I'm not exactly sure what to do from there. It won't let me set UART to modem and I'm not sure which option to set it to under "USB," but I was able to get the computer and QPST to recognize the phone as modem-serial thingy in a COM port.
QPST sees it but a question mark shows up under the phone column and I can't see anything for it in "service programming."
Thanks in advance!
Which version or company is you're gs3 from... I used ##3424# brought me to phone utl. chose first option cdma modem, I haven't tried qpst but read somewhere that 266v is the one to use.. I will update with you in a few to let you know if I was able to connect and read phone!
Use the debug + modem setting, you can read phone and get some info but Not the akey with cdma workshop. That is obtained another way...........
Thanks, this was before I tried CDMA Workshop, which actually works.
It would be nice getting it to work in QPST too, though...
Sent from my SPH-L710 using xda app-developers app
What version of CDMA Workshop did you use?
z4k said:
What version of CDMA Workshop did you use?
Click to expand...
Click to collapse
I'm on vacation so I can't go home and tell you and I don't remember, sorry.
Sent from my SPH-L710 using xda app-developers app
The only on I can get to recognize the Slll is QPST 2.7 Built 3.74 but when you try to read it, it stops in the middle of it and gives an error message.
cdma ws sees/reads, but i suspect the drivers arent correct because only limited functionality with that program
I was able to read the nv items 465, 466, 1192, and 1194 using efs browser in QPST 2.7 Build 378 setup on a Windows XP machine. Then I used CDMA Workshop 3.8.0 to change what I needed to change.
grimmace4 said:
I was able to read the nv items 465, 466, 1192, and 1194 using efs browser in QPST 2.7 Build 378 setup on a Windows XP machine. Then I used CDMA Workshop 3.8.0 to change what I needed to change.
Click to expand...
Click to collapse
not verizon though right? also, what settings did you have for usb? debug modem? ty
need help please! so on cdma workshop i did a nv items read from a galaxy s2 from sprint the range in dec from 0 to 4122 range in hex 0 to 101A then I wrote those nv items to my galaxy s3 now my signal goes on and off and cant make any calls please if someone can tell me what to do or if you can dump the memory on the nv items so i can restore my phone would highly appreciate it.
jbrolo said:
need help please! so on cdma workshop i did a nv items read from a galaxy s2 from sprint the range in dec from 0 to 4122 range in hex 0 to 101A then I wrote those nv items to my galaxy s3 now my signal goes on and off and cant make any calls please if someone can tell me what to do or if you can dump the memory on the nv items so i can restore my phone would highly appreciate it.
Click to expand...
Click to collapse
wouldnt that include the personal info? why didnt you backup that range before writing to it?
I know I was dumb for not doing that i did a backup on CW thinking that backup would include those files but tried to go back to that backup and still having the same issue signal goes on and off couple seconds after phone resets by itself unless i put it on airplane mode
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?