Develop Bugs

Nailed it!!!!!!!!! My 4g is back again

Last week, I did the most stupid thing on my note 2 (SGH-t889). I saw a rom that i liked for the n7100 and flashed on my 889v. Of course, rom works fine but no DATA OR VOICE :crying:crying:
So I flashed my phone with my previous rom and I had data again. All of a sudden, after installing all my apps, I lost the connection. My phone went completely crazy
i saw unknown baseband on settings / phone status; phone rebooted itself. I tried to flash a stock rom, or even flash the 889v modem on any rom and no luck; i was on a constant boot loop
I had to flash another modem from T-Mobile to get out of boot looping (MODEM: T889UVALL4_Modem-Jan_16_13-teshxx) but i couldn't get on any network even if I my phone could detect them (I'm on Videotron).
I've searched xda and other sitEs for solution on how to fix an almost empty esf folder. On a tmo modem my emei was 0 0 and on videotron modem it was null.
SOLUTION
My efs folder was almost empty; no nv_data.bin and those other files.
I went across this site
http://galaxynote2root.com/galaxy-note-2-tutorials/how-to-enable-t-mobile-3g4g-aws-bands-on-att-galaxy-note-2-sgh-i317/
It's a tutorial on how to enable aws on the AT&T note 2. It had just what i needed: a qcn file. Ive follwed the directions on the site; flashed the qcn file with the QPST software and rebooted the phone. My emei was a bunch of 0. No signal still but the battle wasn't loss.
On this thread
http://forum.xda-developers.com/showthread.php?t=1804117
I've used the EMEI NVitem generator to create en encrypted file of my EMEI
Put it on the the NV reader / writer, reboted the phone
And VOILA!!!!!!!!!!!!!
i got my signal back but with a tmo modem (MODEM: T889UVALL4_Modem-Jan_16_13-teshxx)
my 4g is back and my gps is working flawwless
Now, just to let you know, I'm not a developer and i take no credit for this. Even if this thread get approved or deleted, I just wanted to help other members like me who are stuck on the same situation (especially 889v owners). At the end.... MY PHONE IS BACK !!!!!!!!!!!!!!!!!!!!!!!
ohhhh! i allmost forgot....
I AM NOT RESPONSIBLE FOR YOUR PHONE

demension21 said:
Last week, I did the most stupid thing on my note 2 (SGH-t889). I saw a rom that i liked for the n7100 and flashed on my 889v. Of course, rom works fine but no DATA OR VOICE :crying:crying:
So I flashed my phone with my previous rom and I had data again. All of a sudden, after installing all my apps, I lost the connection. My phone went completely crazy
i saw unknown baseband on settings / phone status; phone rebooted itself. I tried to flash a stock rom, or even flash the 889v modem on any rom and no luck; i was on a constant boot loop
I had to flash another modem from T-Mobile to get out of boot looping (MODEM: T889UVALL4_Modem-Jan_16_13-teshxx) but i couldn't get on any network even if I my phone could detect them (I'm on Videotron).
I've searched xda and other sitEs for solution on how to fix an almost empty esf folder. On a tmo modem my emei was 0 0 and on videotron modem it was null.
SOLUTION
My esf folder was almost empty; no nv_data.bin and those other files.
I went across this site
http://galaxynote2root.com/galaxy-n...3g4g-aws-bands-on-att-galaxy-note-2-sgh-i317/
It's a tutorial on how to enable aws on the AT&T note 2. It had just what i needed: a qcn file. Ive follwed the directions on the site; flashed the qcn file with the QPST software and rebooted the phone. My emei was a bunch of 0. No signal still but the battle wasn't loss.
On this thread
http://forum.xda-developers.com/showthread.php?t=1804117
I've used the EMEI NVitem generator to create en encrypted file of my EMEI
Put it on the the NV reader / writer, reboted the phone
And VOILA!!!!!!!!!!!!!
i got my signal back but with a tmo modem (MODEM: T889UVALL4_Modem-Jan_16_13-teshxx)
my 4g is back and my gps is working flawwless
Now, just to let you know, I'm not a developer and i take no credit for this. Even if this thread get approved or deleted, I just wanted to help other members like me who are stuck on the same situation (especially 889v owners). At the end.... MY PHONE IS BACK !!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
MIKE BROWN FTW!!!!!!
Sent from my SGH-T889 using XDA Premium HD app

I can not download Download ATT_I317_AWSMOD_dumimei.qcn. I just get a blank screen in Chrome, IE and Safari. Can you post it or send me a dropbox link or something. Thanks
edit:
Never mind, never saw that kind of Captchaw before. I thought it was just an ad.

I keep getting a size difference error when I go to write the my imei

Did you generate a txt file with the emei generator?
Sent from my SGH-T889 using xda premium

demension21 said:
Did you generate a txt file with the emei generator?
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Problem was I used serveral tools to try to fix this and they did not not requirer the check digit at the end of the imei. The CDWS imei converter requires it. I'm back up and running !!!

gedster314 said:
Problem was I used serveral tools to try to fix this and they did not not requirer the check digit at the end of the imei. The CDWS imei converter requires it. I'm back up and running !!!
Click to expand...
Click to collapse
so you got data back...if so on what baseband?

demension21 said:
Did you generate a txt file with the emei generator?
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Id really love to talk about your process, as I have used QPST(UPST), CDMA Workshop, etc through varios Android, Blackberry, Palm, etc devices and am trying to confirm (repair steps) for posting... please PM me so I can test
Sent from my SGH-T889 using xda app-developers app

I say (repair steps), I mean restoring from backup... have all the various backups and until my GNII and N4 are picked up im not fixing what isnt broke
Sent from my SGH-T889 using xda app-developers app

demension21 said:
so you got data back...if so on what baseband?
Click to expand...
Click to collapse
Here you go.

Wow. I followed your steps to the letter and it worked, thank you so much!!
Have you flashed back to a VTR modem or would that mess everything up? Thanks again for your help.

From past experience flashing the videotron modem would bring me back to boot loop, wouldnt lose imei or signal but would start then after 30secs reboot.. Im stuck with tmo modem. Works fine but signal seems a little weaker.

i have canadian note2 t889v that i got from craigs the other day. everything seemed fine, didnt have sim to try for mobilicity that im on (aws band), he said he used it with rogers fine
I put the sim card, went to search networks but my provider was not listed there. So I rooted the phone , loaded twrp, flashed prerooted factory rom for t889v ( from mrrobins) , no network, than i flashed original factory rom, still no luck, than i flashed t889v modem and still the same.
My imei is present, and matches one on back of the phone. My efs folder is there and is populated (dont know if anything is missing from there)
I dont have backup of efs or imei. What are the chances it is corrupted ? Does anyone have any suggestion, and should i try this method to try to fix it ?

You may have to put your apn settings manually for your carrier. I would try that to start.
Sent from my ASUS Transformer Pad TF700T using xda premium

Already tryed
Sent from my HTC DESIRE HD using xda app-developers app

Also my emei number is correct in abaut.
What are the files I need to have in efs how can I know if my efs is corrupt ?
Sent from my SGH-T889V using xda app-developers app

Have you check the *#2263# menu to make sure it is on the correct band, also in network setting you can switch to gsm, wcdma, so on. As for imei as far as I know if it were corrupt your imei would be bad. Is it possible the phone has been blacklisted?

That code dont work in stock dialer. And mobilicity dont block imei #
Sent from my SGH-T889V using xda app-developers app

pearse said:
Wow. I followed your steps to the letter and it worked, thank you so much!!
Have you flashed back to a VTR modem or would that mess everything up? Thanks again for your help.
Click to expand...
Click to collapse
yes I've tried flashing the 889v modem and I was back in a bootloop again
man i wiish that I could have an original 889v nv data files; i could find a way to midify the emei and flash it on my phone

knnrsk said:
i have canadian note2 t889v that i got from craigs the other day. everything seemed fine, didnt have sim to try for mobilicity that im on (aws band), he said he used it with rogers fine
I put the sim card, went to search networks but my provider was not listed there. So I rooted the phone , loaded twrp, flashed prerooted factory rom for t889v ( from mrrobins) , no network, than i flashed original factory rom, still no luck, than i flashed t889v modem and still the same.
My imei is present, and matches one on back of the phone. My efs folder is there and is populated (dont know if anything is missing from there)
I dont have backup of efs or imei. What are the chances it is corrupted ? Does anyone have any suggestion, and should i try this method to try to fix it ?
Click to expand...
Click to collapse
you mentioned that the phone was working on rogers before you had it?
did you try any othe sim card... form rogers or mobile city?
try frash custom rom and 889v modem with it?
if that doesnt work try the method in the op

[Q] I747m no network connection

Hi All,
Flashed my phone to CM10.1, lost my IMEI, would not connect to network. Managed to get my IMEI back, but would not connect to network. I attempted to go back to stock- and am running a stock ROM- but still cannot connect to network.
I have an i747m.
Carrier is Bell (I'm in Atlantic Canada)
Android Version: 4.1.1 (ROM: I747MVLDLK4)
Baseband: I747MUMLL1
Kernel is dated Nov 20/2012
Build is JRO03L.I747MVLDLK4
When I plug into Kies, it tells me "Your device's current firmware is not supported to update firmware via Kies."
Kies tells me "Current firmware version : PDA:LK4 / PHONE:LL1 / CSC:LK4 (XXX)"
When I try to do a Firmware upgrade and initialization, it tells me "SGH-I747M does not support initializing.
I'm at a complete loss- and really need help.
Thanks!

Have you tried Odin flashing the latest stock for your phone? You'll have to manually reboot into recovery and do a factory reset when it boot loops

mrhaley30705 said:
Have you tried Odin flashing the latest stock for your phone? You'll have to manually reboot into recovery and do a factory reset when it boot loops
Click to expand...
Click to collapse
Yes. I already have flashed to the latest stock firmware.

on Lockscreen, do you see the "Phone not allowed mm#6" message? it only shows on stock roms
not sure if it's mm#6 or mm#4 but yeah do you see the "phone not allowed"?

pcshano said:
on Lockscreen, do you see the "Phone not allowed mm#6" message? it only shows on stock roms
not sure if it's mm#6 or mm#4 but yeah do you see the "phone not allowed"?
Click to expand...
Click to collapse
I do not. My lockscreen says "Emergency Calls only". Anothing couple things worth noting;
Replaced my SIM card with a new one, and activated at Bell kiosk.
Phone shows I have a signal
When I try and make a phone call, I get message "Not registered on network"
Thanks

DivineKaos said:
I do not. My lockscreen says "Emergency Calls only". Anothing couple things worth noting;
Replaced my SIM card with a new one, and activated at Bell kiosk.
Phone shows I have a signal
When I try and make a phone call, I get message "Not registered on network"
Thanks
Click to expand...
Click to collapse
Another update.
I have managed to get a keys firmware upgrade to work. It indeed restored me to the stock Bell rom, I now have the Bell branding, which I didn't have before.
Phone states are now;
Version: 4.1.1
Baseband: I747MVLDLK4
Mobile network type: UMTS:3 (is this right?)
Service state: In Service (this wasn't the case before)
Mobile network state: Connecting
Device Status: Normal
So, it never seems to connect to network.
So then I swap to Mobile Networks
Network Mode: LTE/GSM/WCDMA (auto)
APN: pda.bell.ca
MMSC: h t t p://mms.bell. ca/mms/wa penc
MMS proxy: web.wireless.bell.ca
MMS port: 80
MCC: 302
MNC: 610
APN type: Internet + mms
Authentication Type: none
Any ideas where I should go to from here?
Thanks!

Bump? Any ideas?

DivineKaos said:
Hi All,
Flashed my phone to CM10.1, lost my IMEI, would not connect to network. Managed to get my IMEI back, but would not connect to network. I attempted to go back to stock- and am running a stock ROM- but still cannot connect to network.
I have an i747m.
Carrier is Bell (I'm in Atlantic Canada)
Android Version: 4.1.1 (ROM: I747MVLDLK4)
Baseband: I747MUMLL1
Kernel is dated Nov 20/2012
Build is JRO03L.I747MVLDLK4
When I plug into Kies, it tells me "Your device's current firmware is not supported to update firmware via Kies."
Kies tells me "Current firmware version : PDA:LK4 / PHONE:LL1 / CSC:LK4 (XXX)"
When I try to do a Firmware upgrade and initialization, it tells me "SGH-I747M does not support initializing.
I'm at a complete loss- and really need help.
Thanks!
Click to expand...
Click to collapse
NV Data got corrupted when you lost your IMEI. How did you inject your IMEI back onto your phone? In order to get data back you will need to restore NV Data back onto your phone. This will reload the correct data that is needed to get your phone back onto Bell networks.
DX

Peoplearmy said:
NV Data got corrupted when you lost your IMEI. How did you inject your IMEI back onto your phone? In order to get data back you will need to restore NV Data back onto your phone. This will reload the correct data that is needed to get your phone back onto Bell networks.
DX
Click to expand...
Click to collapse
Thanks for the response.
A close friend of mine did the injecting for me. So I'm not 100% sure on how he did it. Is there a method to properly restore the NV Data? I don't have a good backup, and my searches have been less than stellar.
Thanks!

DivineKaos said:
Thanks for the response.
A close friend of mine did the injecting for me. So I'm not 100% sure on how he did it. Is there a method to properly restore the NV Data? I don't have a good backup, and my searches have been less than stellar.
Thanks!
Click to expand...
Click to collapse
By the way, not sure if it is relevant- but my ERI Version is "Not Available"

Peoplearmy said:
NV Data got corrupted when you lost your IMEI. How did you inject your IMEI back onto your phone? In order to get data back you will need to restore NV Data back onto your phone. This will reload the correct data that is needed to get your phone back onto Bell networks.
DX
Click to expand...
Click to collapse
Spoke with my friend.
IMEI was restored using http://forum.xda-developers.com/showthread.php?t=1804117

Ended up taking the phone into Bell. They are going to try and see if they can get the problem covered under warranty.

Samsung would not fix it because I have a small crack in the case from when it was dropped the day after I bought it. They said I voided the warranty and wanted $400 to repair it.
Took it to a local repair place, they had it for two weeks- said they cannot fix it via software. They need to replace the board.$120.
Does anyone have any suggestions before I dump money into it?

Settings>more settings>mobile services>access point names. is any of the circles filled? I had a similar problem.
Sent from my SGH-I747M using xda premium

DivineKaos said:
Samsung would not fix it because I have a small crack in the case from when it was dropped the day after I bought it. They said I voided the warranty and wanted $400 to repair it.
Took it to a local repair place, they had it for two weeks- said they cannot fix it via software. They need to replace the board.$120.
Does anyone have any suggestions before I dump money into it?
Click to expand...
Click to collapse
Any updates on your findings?

DivineKaos said:
Samsung would not fix it because I have a small crack in the case from when it was dropped the day after I bought it. They said I voided the warranty and wanted $400 to repair it.
Took it to a local repair place, they had it for two weeks- said they cannot fix it via software. They need to replace the board.$120.
Does anyone have any suggestions before I dump money into it?
Click to expand...
Click to collapse
samsung has no right to void your warranty because there's a crack phones are always going to drop. plus the issue that you are having has nothing to do with the crack.
I better not get turned down of my warranty(s) just because a crack, scratch, ect. or I will sick my lawyers on them plus bring in the media.
MESSAGE FOR SAMSH1T:
if you void warrantys due to cracks
then maybe stop making the damn phones out of cheap plastic caseing. 5-600.00 phone when droped should not crack at all. you $h17 heads.
sorry for bringing this post back to life. just had to say what I had to say.

I've been having a similar issue as the original poster
I was running CM10.2 on Rogers perfectly fine until yesterday when suddenly the device stopped connecting to Rogers network. I made sure the Access Point names and stuff were fine, I rebooted. I then thought it might be an issue with CM and I flashed to latest Nightly, that didn't work so I tried restoring to a different ROM (Task650), wiped dalvik/cache. That didnt work, so tonight I did a full factory reset and used Odin to restore to the latest STOCK Rogers MD5.
And.......STILL won't connect to the network.
Any ideas. I'm out of warranty and rooted, so I'm sure Samsung won't do **** if this is a hardware issue. I'm not sure if its an IMEI issue as the original poster thought. I even changed SIM cards today with my carrier. Nada
Help please please please, thanks

Sianspheric said:
I've been having a similar issue as the original poster
I was running CM10.2 on Rogers perfectly fine until yesterday when suddenly the device stopped connecting to Rogers network. I made sure the Access Point names and stuff were fine, I rebooted. I then thought it might be an issue with CM and I flashed to latest Nightly, that didn't work so I tried restoring to a different ROM (Task650), wiped dalvik/cache. That didnt work, so tonight I did a full factory reset and used Odin to restore to the latest STOCK Rogers MD5.
And.......STILL won't connect to the network.
Any ideas. I'm out of warranty and rooted, so I'm sure Samsung won't do **** if this is a hardware issue. I'm not sure if its an IMEI issue as the original poster thought. I even changed SIM cards today with my carrier. Nada
Help please please please, thanks
Click to expand...
Click to collapse
I had an almost identical experience with my S3, except im i747 on AT&T. Rooted phone randomly started acting up, then nothing. No mobile connection at all.
It's been about four days of constant searching and still nothing. To make matters worse im also stuck on 4.3 because I stupidly updated after returning to stock
I flashed a modem and occasionally ( by occasionally i mean 1 hour out of every day) I'll randomly get 4g/mobile service but no phone calls and be able to use my phone. Not entirely sure if the modem flash really did anything

I had the same problem when I updated to stock 4.3 I didn't have data but could text and call, I also for some reason couldn't go through the APN settings because it thought I didn't have a SIM in but I flashed a modem from here http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 for d2att only! After I flashed and reboot viola! Data working perfectly. Maybe you can find a updated modem for the T-Mobile variant and that should do the job
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

xSharpi said:
I had the same problem when I updated to stock 4.3 I didn't have data but could text and call, I also for some reason couldn't go through the APN settings because it thought I didn't have a SIM in but I flashed a modem from here http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 for d2att only! After I flashed and reboot viola! Data working perfectly. Maybe you can find a updated modem for the T-Mobile variant and that should do the job
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just did this.
Was running stock 4.3
flashed CWM Recovery via Odin
then flashed the modem and bootloader ZIP's
and I now have a HARD BRICKED phone.
:crying::crying::crying::crying::crying:

[Q] AT&T S3 stuck on Edge (not LTE)

My problem:
My galaxy s3 takes a LONG time to connect to AT&T when it boots up (over 5 minutes), and then only has Edge:2 network service.
How I got here:
Had 4.1.2 installed from AT&T
I rooted my phone with the "no countering tripping method" as described here: http://forum.xda-developers.com/showthread.php?t=1739426 to 4.1.1 this downgrade apparently made something not work, I kept getting errors, something about acore process failures.
I re-installed the stock 4.1.2 from AT&T
Still getting process failures
Read that clearing the contacts sometimes works, it didn't
Read that factory reset helps, it did
I still wanted a rooted phone, so this time I used this method: http://forum.xda-developers.com/showthread.php?t=1746665
Again processes started crashing
Again had to reset to factory
Now I noticed my phone wasn't working at all
Found that my IMEI was set to 0
Fixed that by following these instructions: http://forum.xda-developers.com/showthread.php?t=1804117
Note: the link to the sgs3.nv.gen.zip was bad, I found another here: http://forum.xda-developers.com/showthread.php?t=2335951 but my virus checker freaked out on it. I ran it on my kids pc, and it worked, don't know if I infected them or not, but I got my IMEI data back
Decided all this was too much hassle, so I reset my flash count to zero with this: http://forum.xda-developers.com/showthread.php?t=1494114
Reverted to stock 4.1.2 from AT&T and reset to factory
Still stuck on Edge:2
Found this thread: http://forum.xda-developers.com/showthread.php?t=2036891 my phone won't let me change my band preference, also under *#197328640#>SIM>CHECK NV it say "Band perf: Unexpected value"
Question:
Where do I go from here?
Thanks!

thabin said:
My problem:
My galaxy s3 takes a LONG time to connect to AT&T when it boots up (over 5 minutes), and then only has Edge:2 network service.
How I got here:
Had 4.1.2 installed from AT&T
I rooted my phone with the "no countering tripping method" as described here: http://forum.xda-developers.com/showthread.php?t=1739426 to 4.1.1 this downgrade apparently made something not work, I kept getting errors, something about acore process failures.
I re-installed the stock 4.1.2 from AT&T
Still getting process failures
Read that clearing the contacts sometimes works, it didn't
Read that factory reset helps, it did
I still wanted a rooted phone, so this time I used this method: http://forum.xda-developers.com/showthread.php?t=1746665
Again processes started crashing
Again had to reset to factory
Now I noticed my phone wasn't working at all
Found that my IMEI was set to 0
Fixed that by following these instructions: http://forum.xda-developers.com/showthread.php?t=1804117
Note: the link to the sgs3.nv.gen.zip was bad, I found another here: http://forum.xda-developers.com/showthread.php?t=2335951 but my virus checker freaked out on it. I ran it on my kids pc, and it worked, don't know if I infected them or not, but I got my IMEI data back
Decided all this was too much hassle, so I reset my flash count to zero with this: http://forum.xda-developers.com/showthread.php?t=1494114
Reverted to stock 4.1.2 from AT&T and reset to factory
Still stuck on Edge:2
Found this thread: http://forum.xda-developers.com/showthread.php?t=2036891 my phone won't let me change my band preference, also under *#197328640#>SIM>CHECK NV it say "Band perf: Unexpected value"
Question:
Where do I go from here?
Thanks!
Click to expand...
Click to collapse
This just happened to me too. I backed up my IMEI but lost it and had to get a new phone. I used QPST tool to restore my IMEI , which is located behind your battery. I did not work. There is another tool called NV Generate or something like that and still it did not work. I did not like spending the money for a warranty replacement, of course, so looked and tried hard for a fix. Since nothing worked I am also thinking that its possible I had a hardware problem, but I can say that an IMEI issue can be as bad as hardbricking, so proceed with caution and follow to a T. Good luck bro. I hope you can fix it. Let me know if you have a chance.
Edit: I missed the part about you using NV tool. I spoke with a bunch of Att help and a Samsung guy as well. Nobody knew about it. Mine was 5 freaking days past warranty. Still sick from that. If you are under warranty. Take it back.

I'm also having these issues..
Anyone have a true fix? I would go back to Full Stock, but have already tried that and still had the data issues. Something is hosed that needs to be fixed..

Fixed!!
I bought a new phone from AT&T, copied the nv config using the instructions here:
http://forum.xda-developers.com/showthread.php?t=1804117
Changed the IMEI to my phone's IMEI, and EUREKA! It works!
I'm attaching the file I used (with the IMEI blanked out, so be sure to fill in our own IMEI or this won't work for you, it is section 550, see http://forum.xda-developers.com/showthread.php?t=1804117 for more details).
I hope this helps others, and they don't have to pay the $35 restocking fee.

thabin said:
I bought a new phone from AT&T, copied the nv config using the instructions here:
http://forum.xda-developers.com/showthread.php?t=1804117
Changed the IMEI to my phone's IMEI, and EUREKA! It works!
I'm attaching the file I used (with the IMEI blanked out, so be sure to fill in our own IMEI or this won't work for you, it is section 550, see http://forum.xda-developers.com/showthread.php?t=1804117 for more details).
I hope this helps others, and they don't have to pay the $35 restocking fee.
Click to expand...
Click to collapse
This is exactly what I need! Thank you! My usb is corroded so I cannot connect usb and will have to load this manually. Could you please tell me the exact process you used to add your EMEI # to the file? I have opened the text file and went to section 550, but I do not know if i'm properly changing the number.

bweyadn said:
This is exactly what I need! Thank you! My usb is corroded so I cannot connect usb and will have to load this manually. Could you please tell me the exact process you used to add your EMEI # to the file? I have opened the text file and went to section 550, but I do not know if i'm properly changing the number.
Click to expand...
Click to collapse
I fixed the IMEI using the following instructions:
http://forum.xda-developers.com/showthread.php?t=1804117
The link on that page for the utility to generate a new IMEI didn't work, but I found another copy here:
http://forum.xda-developers.com/showthread.php?t=2335951
*WARNING* my virus checker freaked out about this file. I ran in on my kids machine (not mine) and it seemed to work fine, but I want you to be warned about the royal freakout my virus checker gave me.

thabin said:
I fixed the IMEI using the following instructions:
http://forum.xda-developers.com/showthread.php?t=1804117
The link on that page for the utility to generate a new IMEI didn't work, but I found another copy here:
http://forum.xda-developers.com/showthread.php?t=2335951
*WARNING* my virus checker freaked out about this file. I ran in on my kids machine (not mine) and it seemed to work fine, but I want you to be warned about the royal freakout my virus checker gave me.
Click to expand...
Click to collapse
I got almost just the identical problem... However, I checked my phone and my IMEI number is still intact... yet im stuck on EDGE
story was that I brought my rooted S3 from ATT (but not unlocked) to China 2 weeks ago hoping to use the phone on China Mobile's network (though knowing that China Mobile doesnt support the same band for 3g/4g as the US).
It wasn't til after inserting the sim that I realized I havent unlocked the phone yet... and since ATT won't give me the unlock code, I ended up trying to use the *#197328640# method, which was unsuccessful because I was still on ICS and this method requires Jellybean.
So in a hurry I used odin to upgrade to a jellybean version that apparently wasn't compatible with my I747.
After taking to a local shop, the dude repairing my phone was able to get the OS running again but it was weird in that even with an ATT sim card the phone would ask for an unlock code.
So finally after doing the re-flash of the official ATT I747 Jellybean rom, I was able to get into the *#197328640# menu and unlock my phone using
the second method mentioned in here: http://www.wikihow.com/Unlock-Samsung-Galaxy-Siii-(S3)
I was happy to get it to work with China Mobile's sim even though I can only use EDGE over there, but I also realize the dreafully long wait time for the phone to get a signal from power on.
After coming back to the States today and inserting my original ATT sim card, I noticed that it still takes a long time for the phone to get a signal after power on and after it acquires the signal from ATT, Im only getting signal (feels almost like the phone is stuck in the international setting...)
I have tried to reflash to z999 rom with cwm, tried to reflash the modem firmware, nothing is working.
My IMEI is still showing up in the "status" under about this phone, and its the same number as it appears in the back of the phone...
but for some reason I feel like this might have something to do with the fiddling of the secret code menu during my unlock oversea... since I had to go into the UMTS menu (which I believe is for EDGE)...
Since my IMEI isnt lost... anyone have any ideas what could have been the problem? This is getting beyond frustrating... would really appreciate the help!

[Q] vs985 problems after downgrade. advice?

I got my phone around the begining of last month and decided the other night that it was time to root as I have rooted every android device I have owned since the wildfire s. I had previously taken the OTA so I was on vs98512b. I used LG flashtool to downgrade to vs98510b. The downgrade it's self went fine. I then rooted using stumproot again nothing out of the ordinary. I downloaded Supersu and enabled survival mode. I tried to check for New updates and it says "your phone is not registered" I found that to be strange so I checked some other settings and found that my imei was 000000000000000. I found that to be strange. I attempted to make a call and my phone switched to roaming and I lost all my signal bars. I performed a factory reset and after the reset I have all network function, I'm connected to Verizon 4g lte and can make calls, no more roaming. I checked the imei again at this point and it is still showing 000000000000000 and I was still unable to update. So I then reflashed the stock firmware for vs98510b. Again I had the roaming issue that went into being unable to connect to network. Again I performed a hard rest on my phone and got full network function back. I had a new micro SIM tucked away for a rainy day so I put the New SIM card in and activated it with no change to imei. What can I do from here? My phone is working fine with the imei being 000000000000000 it seems like the only issue is not being able to get an OTA, when I try using Verizon's upgrade assistant it won't even list my phone. If I check my Verizon it shows up as a non vow device. Thanks in advanced.

wcallah04 said:
I got my phone around the begining of last month and decided the other night that it was time to root as I have rooted every android device I have owned since the wildfire s. I had previously taken the OTA so I was on vs98512b. I used LG flashtool to downgrade to vs98510b. The downgrade it's self went fine. I then rooted using stumproot again nothing out of the ordinary. I downloaded Supersu and enabled survival mode. I tried to check for New updates and it says "your phone is not registered" I found that to be strange so I checked some other settings and found that my imei was 000000000000000. I found that to be strange. I attempted to make a call and my phone switched to roaming and I lost all my signal bars. I performed a factory reset and after the reset I have all network function, I'm connected to Verizon 4g lte and can make calls, no more roaming. I checked the imei again at this point and it is still showing 000000000000000 and I was still unable to update. So I then reflashed the stock firmware for vs98510b. Again I had the roaming issue that went into being unable to connect to network. Again I performed a hard rest on my phone and got full network function back. I had a new micro SIM tucked away for a rainy day so I put the New SIM card in and activated it with no change to imei. What can I do from here? My phone is working fine with the imei being 000000000000000 it seems like the only issue is not being able to get an OTA, when I try using Verizon's upgrade assistant it won't even list my phone. If I check my Verizon it shows up as a non vow device. Thanks in advanced.
Click to expand...
Click to collapse
have you backuped the efs partition like the rooting thread said

Of course not. That would have been to easy. If I had I would have been able to avoid making a new thread. I really do Google first. Except with the back up of the eds partition. I knew nothing about that until I searched imei problems.

wcallah04 said:
I got my phone around the begining of last month and decided the other night that it was time to root as I have rooted every android device I have owned since the wildfire s. I had previously taken the OTA so I was on vs98512b. I used LG flashtool to downgrade to vs98510b. The downgrade it's self went fine. I then rooted using stumproot again nothing out of the ordinary. I downloaded Supersu and enabled survival mode. I tried to check for New updates and it says "your phone is not registered" I found that to be strange so I checked some other settings and found that my imei was 000000000000000. I found that to be strange. I attempted to make a call and my phone switched to roaming and I lost all my signal bars. I performed a factory reset and after the reset I have all network function, I'm connected to Verizon 4g lte and can make calls, no more roaming. I checked the imei again at this point and it is still showing 000000000000000 and I was still unable to update. So I then reflashed the stock firmware for vs98510b. Again I had the roaming issue that went into being unable to connect to network. Again I performed a hard rest on my phone and got full network function back. I had a new micro SIM tucked away for a rainy day so I put the New SIM card in and activated it with no change to imei. What can I do from here? My phone is working fine with the imei being 000000000000000 it seems like the only issue is not being able to get an OTA, when I try using Verizon's upgrade assistant it won't even list my phone. If I check my Verizon it shows up as a non vow device. Thanks in advanced.
Click to expand...
Click to collapse
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
please note i did it a little different then the instructions...i didnt use a1 or b1 instruction bc it was different for my phone..

crazy4android said:
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
please note i did it a little different then the instructions...i didnt use a1 or b1 instruction bc it was different for my phone..
Click to expand...
Click to collapse
Did it put your imei back in? Or just made it so you can talk and text?

wcallah04 said:
Did it put your imei back in? Or just made it so you can talk and text?
Click to expand...
Click to collapse
i rewrote my orignal imei...u can change it if u want but its illeagal...but who cares...i just fixed mine...and data and everything works perfectly...even using at&t on a verizon phone and it humming like a humming bird... its not hard or complicated....very simple dont even have to get nervous...

That's all I need is to put my imei back in. Lol I'll try it as soon as I get home from work. Thanks.

crazy4android said:
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
please note i did it a little different then the instructions...i didnt use a1 or b1 instruction bc it was different for my phone..
Click to expand...
Click to collapse
No luck. I can't get my phone to diag mode.

suljo94 said:
have you backuped the efs partition like the rooting thread said
Click to expand...
Click to collapse
Is it possible to backup my efs prior to gaining root access?

wcallah04 said:
No luck. I can't get my phone to diag mode.
Click to expand...
Click to collapse
which service provider did u use...with verizon i used ##228378 in the dialer code nd i left it in the menu that pop up nd on my pc it showed up a a serial com port...make sure ur drivers are working properly...nd when connecting to cdma tool u pick serial port...

crazy4android said:
which service provider did u use...with verizon i used ##228378 in the dialer code nd i left it in the menu that pop up nd on my pc it showed up a a serial com port...make sure ur drivers are working properly...nd when connecting to cdma tool u pick serial port...
Click to expand...
Click to collapse
Hmmm... I have verizon. The only thing I can get the cdma tool to to connect to is the modem port. Nothing else replies...

wcallah04 said:
Hmmm... I have verizon. The only thing I can get the cdma tool to to connect to is the modem port. Nothing else replies...
Click to expand...
Click to collapse
hey check out this tool...i also used this once...it worked great..http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546 first open efs professional.exe./qualcomm nv tool/...connect to port for the drop down menu on top...i used serial since thats the only one that responded...then press connect...then try and read phone info to see if it sees ur phone...then go to the secure ops tab.....select the imei(dec) box and enter ur imei and then write it...then select meid(hex) box.....write ur meid...same as imei minus the last digit.... thats the best instruction i can give on the top of my head..i did it a while ago...so if confused feel free to ask questions...

VS985: Lost IMEI, Can't Make Phone Calls
I'm having problems with my VS985 after downgrading including losing the IMEI and especially the ability to make phone calls.
So I got a used VS985W that had 35B installed on it for one of my kids. Having put CyanogenMod on my LG G3 (VS985) successfully, I started down that path. I used the TOT method to flash back to 10B, then used KDZ to upgrade to 12B. Then I rooted, installed TWRP, and then CyanogenMod. But I couldn't make phone calls.
There are numerous things I've tried, but it's still unable to make phone calls, usually giving out of service area, but when trying to use the *#06# code, I get an error of "missing IMMI or such".
At one point I found the IMEI had gone to all zeros. I managed to find a method to fix that. I also switched out SIM cards between phones; same issue - it's the phone and firmware.
The only thing that seems to fix it is to go back to stock 35B. Then it makes phone calls. But then I can't root it and restore the apps/data we backed up from the previous phone (LG Spectrum running CM 11).
I have done hours of searching and reading these forums along with others. I've redone the downgrade and root and TWRP install and tried numerous things but still can't get phones calls in stock versions less than 35B or in CyanogenMod (12.1, not 13, which I did try to install but never could get it to reliably boot back up after an installation, so finally gave up and went back to 12.1).
Anyone heard of this before? I can't find it. I did see in this thread post #4:
Google~Android said:
check this out...this is how i solved mine...its something i did on my own...theres instructiong for the sprint but i did it on my verizon...check out my post... http://forum.xda-developers.com/showpost.php?p=57849643
Click to expand...
Click to collapse
Unfortunately this link doesn't work (moved or deleted). I'm continuing to search, but it almost seems like I managed to royally muck up some partition I didn't mean to? I've tried following the advice of a number of posts, too, on related, similar aspects, but I'm getting to a point of slight insanity. Along with a kid that wants their phone (and the old one has the older style SIM so not just that easy to deal with just switching unfortunately).
Any guidance or thoughts Much appreciated. Am going to continue to try the various things I'm reading about. Thanks, -Mark

Will not register to network

hello ladies and gents I bought a note 3 yesterday from some dude thinking I could fix it and get a note 3 on the cheap. I was wrong the problem is hard to fix.
1 It will not register to network
it is not blacklisted or network blocked.
Ive read somewhere that after you register to many different sims it wont allow it to connect to network anymore.
what can I do I wonder as a last ditch effort if I replace the motherboard if that will work any suggestions please?

darkphate83 said:
hello ladies and gents I bought a note 3 yesterday from some dude thinking I could fix it and get a note 3 on the cheap. I was wrong the problem is hard to fix.
1 It will not register to network
it is not blacklisted or network blocked.
Ive read somewhere that after you register to many different sims it wont allow it to connect to network anymore.
what can I do I wonder as a last ditch effort if I replace the motherboard if that will work any suggestions please?
Click to expand...
Click to collapse
Have you tried updating the firmware? check the APN on the phone once you insert the sim.

You could try taking it to a T-Mobile store to see if they can get it to register. Sometimes they can activate it when you can't.

JSing said:
Have you tried updating the firmware? check the APN on the phone once you insert the sim.
Click to expand...
Click to collapse
bobbyphoenix said:
You could try taking it to a T-Mobile store to see if they can get it to register. Sometimes they can activate it when you can't.
Click to expand...
Click to collapse
I cant take it to the store i bought it from someone or at least i dont think i can it didnt have the knox counter activiated but now it does so im pretty sure the thing that resends and receives the signal is broken but im not sure where it is.
its basically a tablet :/

darkphate83 said:
I cant take it to the store i bought it from someone or at least i dont think i can it didnt have the knox counter activiated but now it does so im pretty sure the thing that resends and receives the signal is broken but im not sure where it is.
its basically a tablet :/
Click to expand...
Click to collapse
Try updating to the latest firmware. Something might have broke the modem during an upgrade. Go to www.sammobile.com

JSing said:
Try updating to the latest firmware. Something might have broke the modem during an upgrade. Go to www.sammobile.com
Click to expand...
Click to collapse
everything else works without flaw it seems just will not register on network when I try the mobile data turns off and then it just never does.
Ive flashed 2 different modems via odin tried using a att sim (still no registering)
The phone is unlocked. I dont know what to do.

Imei blocked.

trim81 said:
Imei blocked.
Click to expand...
Click to collapse
It is most definitely not imei blocked.
It feels like it might be hardware related but I have no idea how to fix that. some piece that deals only with registering on networks.

Corrupted efs folder is my other guess

trim81 said:
Corrupted efs folder is my other guess
Click to expand...
Click to collapse
can that be fixed? Ive flashed different versions of 4.4.2 and nothing seems to help changed basebands

trim81 said:
Corrupted efs folder is my other guess
Click to expand...
Click to collapse
okay I used my working note 3 to copy the efs with samsung tools then uploaded to drive installed samsung tools on the new note 3 and restored the efs from he working phone nothing changed any other ideas?
Notes:
I have 2, note 3s
1 working
1 not working

Sounds like a network block. Post a screenshot of the failing to register device after dialing *#0011#
Sent from my leanKernel 3.16 powered stock 4.4.2 SM-N900T

Here you go and thank you for helping.

Here is the working note 3 also this one is also tmobile variant but on att

Go to www.swappa.com/esn
Check the imei number.
What does it say?

Clean like I said it seems hardware related I can't figure it out.

darkphate83 said:
Here you go and thank you for helping.
Click to expand...
Click to collapse
Well, that's interesting.
If you go to settings, mobile networks, and search for networks, can you select the network and have it register?
Also double check the apn settings. I borked my hidden apn settings once and couldn't get back on the network until i wiped and reflashed full stock.
If none of that works, try also resetting the nv. Look for my thread on 900t service mode for instructions.
Sent from my leanKernel 3.16 powered stock 4.4.2 SM-N900T

I've already rebuilt the nv build. It's a family mobile sim(tmobile)
Also the apn settings I can try that again haven't changed them since I did a flashed back to stock. I doubt it will change anything usually you can still register.
oh the sim doesn't even have service anymore anyhow. Yesterday was the last day but I don't think that would change being able to register anyway.

Notice that it turns off mobile data when I try to register it may be a clue but I haven't been able to make anything of it.
http://forum.xda-developers.com/showthread.php?t=2754957
toastido I ran into your thread yesterday and did that but ill rebuild again maybe ill get lucky?

darkphate83 said:
can that be fixed? Ive flashed different versions of 4.4.2 and nothing seems to help changed basebands
Click to expand...
Click to collapse
Edited
See rebuilt again. Changed apn settings nothing.