Related
i flashed my p4000 to the new rom, and my pst info cleared, which i have written down, but when i go to enter the new info in, it asks me for a unlock code...
in all the tuts i read it never told me how to check it or anything i dont know what the unlock code would be, i also bought it used, anyone know?
i cant use my phone until i fix this, and i really need my phone tonight.
Unlock code for the SIM or the phone? I presume theres nothing on your device till now, why not hard-reset or upgrade to another ROM?
Regards,
Carty..
htc p4000 have no sim cards.
im doing the ##778 to get into the PST menu, then when i try to edit it, to input my #, it asks me for an unlock code... :S
have you tried all 0s or 123456 or your phone number?
yes i tried a couple.
000000
123456
654321
i havnt changed the code...anyone know how to change it through an app or the default code?
arg!
i need my phone tonight.
Berserk87 said:
yes i tried a couple.
000000
123456
654321
i havnt changed the code...anyone know how to change it through an app or the default code?
arg!
i need my phone tonight.
Click to expand...
Click to collapse
If it's anything like sprint, then a simple call to your carrier should remedy the problem. with sprint it's called an "MSL" and they give it to you when programming your phone. So if you call and tell them that you need to 'reprogram' your phone, they should walk you through the steps along with giving you the code.
if i reflash it with the nueROM v2 build 5022, its a sprint rom...so that would mean i could use the 000000 as the unlock code?
also, after flashing to the new roms, my phone continually reset...would go on for a minute then reset... thats why i went back to my default rom, but now its asking for an unlock code >.>
Unzip this to your phone. Take your battery off and write down your Hex ESN. Run GetSPC.exe. Type your Hex ESN in the first box. The second box will be your unlock code.
*edit - removed file, missing keygen and someone linked to it on the next page.
k ill try that out, thank you.
any reason why my phone would be constantly reseting after installing the new roms?
k.
my EST is
but when i type that in, its saying "could not link to dll"
?
If I were you I would edit that post and remove that ESN # ASAP, people can use that to steal your service.
jjlwork said:
If I were you I would edit that post and remove that ESN # ASAP, people can use that to steal your service.
Click to expand...
Click to collapse
****, i was worried something like that could happen.
it should be the hex of that number though right?
do i include the first 3 letters?
k i converter the esn to hex and its still not working >.>
Berserk87 said:
k i converter the esn to hex and its still not working >.>
Click to expand...
Click to collapse
you might try the program found here:
http://forum.xda-developers.com/showthread.php?p=1541466 (it's the program called GetSPC)
i tried it on my phone and it provided an MSL number. hafta admit, tho - the MSL it gave me didn't work (and it differs from the MSL i have written down for my phone).
i might also suggest that you SEARCH...it's what I did to find the above. you might also try calling your carrier and ask them what the unlock code is.
OH -- use a HEX version of the ESN, and use ALL CAPS for any letters in the HEX version. It still may provide you with an invalid MSL...but worth a shot.
Make sure you are using the correct number for ESN, just converting the number from the back of your phone to hex will not work. Click program settings and device information on the bottom it will say ESN followed by a 8 digit hex number..that is the hex esn, you then put that in GetSPC and it will give you your 6 digit master unlock code. Dial ##6digitcodeSEND and it will open up to a place with 2 settings that can be changed, enter your 10 digit phone number for these two settings.
If you still can't get it, call Telus & tell them you can't make any calls, they will walk you thru the reprogramming process.
jjlwork said:
Make sure you are using the correct number for ESN, just converting the number from the back of your phone to hex will not work. Click program settings and device information on the bottom it will say ESN followed by a 8 digit hex number..that is the hex esn, you then put that in GetSPC and it will give you your 6 digit master unlock code. Dial ##6digitcodeSEND and it will open up to a place with 2 settings that can be changed, enter your 10 digit phone number for these two settings.
If you still can't get it, call Telus & tell them you can't make any calls, they will walk you thru the reprogramming process.
Click to expand...
Click to collapse
ahhhh
thats what i was doing :loollll
k, i entered my hex number and its still saying "cant link to dll"
i got like 15 minutes to figure this out :O
k the "phonetools" the other guy linked too was missing files, so it wouldnt work either way, lets try the real one >.>
WORKED, AWESOME.
now to test it out
Berserk87 said:
k the "phonetools" the other guy linked too was missing files, so it wouldnt work either way, lets try the real one >.>
Click to expand...
Click to collapse
Don't know why it didn't work, it's the exact same program. The only thing I took out was the PPC 2003 version so you wouldn't run that by mistake.
*edit - just downloaded it & it's missing the keygen. I don't know how that happened, sorry. I would've just linked to the original but I couldn't remember where I'd gotten it initially.
to properly break your esn for a optimus v for boost moble
follow directions found here
http://forum.xda-developers.com/showthread.php?t=991668
skip the prl part you dont care you wanna frag your phone to never work again to make phone calls
<i chose method 2 for getting SPC>
goto security tab
in a drop down menu obvious choice would be to choose LG method
choose read ESN change the esn and press write
this shoulD produce a message saying you suck this failed but you a hacker try the other methods
so try the other methods when you get to the EFS method this should say sucseed --you think yeah im awsome now go back to the lg method and choose read ESN and it should now read 000000
you have now successfully ruined your phone congrats
by the way you can have this esn i dont need it
Any tips and suggestion are welcome
this is a great tool alternative to the tut http://www.cdmatool.com/
register run app log in -it keeps a data base of phone types
i dont like the login part but it works
wethecom said:
to properly break your esn for a optimus v for boost moble
follow directions found here
http://forum.xda-developers.com/showthread.php?t=991668
skip the prl part you dont care you wanna frag your phone to never work again to make phone calls
<i chose method 2 for getting SPC>
goto security tab
in a drop down menu obvious choice would be to choose LG method
choose read ESN change the esn and press write
this shoulD produce a message saying you suck this failed but you a hacker try the other methods
so try the other methods when you get to the EFS method this should say sucseed --you think yeah im awsome now go back to the lg method and choose read ESN and it should now read 000000
you have now successfully ruined your phone congrats
by the way you can have this esn i dont need it
Any tips and suggestion are welcome
this is a great tool alternative to the tut http://www.cdmatool.com/
register run app log in -it keeps a data base of phone types
i dont like the login part but it works
Click to expand...
Click to collapse
IS there a way to recover from a bad esn???
i would say not by any means i have found but this probably works on other models but the optimus v it frags it -let me know if you do find a way
wethecom said:
i would say not by any means i have found but this probably works on other models but the optimus v it frags it -let me know if you do find a way
Click to expand...
Click to collapse
I just tried it with Optimus S and no success. I tried LG METHOD and it gave me the .... Fail cannot change esn error.
Now the esn on the phone shows zeros.
prominator said:
I just tried it with Optimus S and no success. I tried LG METHOD and it gave me the .... Fail cannot change esn error.
Now the esn on the phone shows zeros.
Click to expand...
Click to collapse
wow so i take it you didnt read the title or the message atleast now we know it dosnt work for the optimus s either thank you
omg i used dfs a cmda tool that requires a login and it fixed it
last time it didnt work but now it dose omg
edit-------------------
premature post sorry it can change to 000001 or 000002 or others thats all others fail
WS 3.7 will fix it, and I think 3.5, I've repaired quite a few!
i used a version of cmda workshop but it didnt allow the original to go back in-but it allowed other sen ranges -i will check my version and try again with a newer version if mine was old..if it is built into the software to block ranges i will definitly try to crack it so it will allow any ..but i sorta lost intrest because i solved my esn problem and can now register with google email now that it has a valid esn other than 00000000
You can fix your ESN using the NV items write feature.
NV items 0 and 5597 are both your ESN but written backwards in pairs.
NV items 1943 and 5598 are both your MEID but written backwards in pairs.
By backwards in pairs I mean if your real ESN is 12345678, then NV item 0 and 5597 is:
78 56 34 12
If your MEID is A10000009296F2, then NV item 1943 is:
F2 96 92 00 00 00 A1
Read NV items 0 to 5598 from your phone. The items listed above should all be 0's if you accidentally wiped them out. Fix the values in the way I described above so that they match up with your original ESN and MEID. Then write the entire NV file back to your phone. This should repair your ESN to its original value.
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?
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.