Missing IMEI - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

Recently I noticed that the IMEI on my Turbo had been cleared to 0. I am not 100% sure when this happened and the device still worked fine in this state. At some point I flashed the newest radio package SU4TL-49. I was having some issues after that so I flashed the SU4TL-44 package to see if I could switch back. It seemed to work. Later I switched back to SU4TL-49. Could this have caused the issue? Recently I flashed the full Verizon Retail Stock Lollipop 5.1 /// XT1254_QUARK_VERIZON_5.1_SU3TL-38_38_CFC.xml.zip. Then I updated to the latest OTA. Still no IMEI. Any ideas how I can restore it?

thecaptain0220 said:
Recently I noticed that the IMEI on my Turbo had been cleared to 0. I am not 100% sure when this happened and the device still worked fine in this state. At some point I flashed the newest radio package SU4TL-49. I was having some issues after that so I flashed the SU4TL-44 package to see if I could switch back. It seemed to work. Later I switched back to SU4TL-49. Could this have caused the issue? Recently I flashed the full Verizon Retail Stock Lollipop 5.1 /// XT1254_QUARK_VERIZON_5.1_SU3TL-38_38_CFC.xml.zip. Then I updated to the latest OTA. Still no IMEI. Any ideas how I can restore it?
Click to expand...
Click to collapse
better question is how did you obtain this phone? usually, the IMEI never changes, regardless of ROM, SIM Card, radio, etc. this is used to identify to the carriers that your phone is valid (not stolen). can you confirm that you are able to make phone calls?
otherwise, you might want to search for "Fix IMEI"

jco23 said:
better question is how did you obtain this phone? usually, the IMEI never changes, regardless of ROM, SIM Card, radio, etc. this is used to identify to the carriers that your phone is valid (not stolen). can you confirm that you are able to make phone calls?
otherwise, you might want to search for "Fix IMEI"
Click to expand...
Click to collapse
I bought it from Verizon when it was released and have had it since. I had a SIM in it until a couple of days ago when I picked up the Pixel. I had it on Verizon with no issues. On My Verizon it said it was a non Verizon device and showed the 0 IMEI too. I'm kind of surprised it was working. I was wondering if it was hardware related. From what I was reading you can't typically change it like you said.

thecaptain0220 said:
I bought it from Verizon when it was released and have had it since. I had a SIM in it until a couple of days ago when I picked up the Pixel. I had it on Verizon with no issues. On My Verizon it said it was a non Verizon device and showed the 0 IMEI too. I'm kind of surprised it was working. I was wondering if it was hardware related. From what I was reading you can't typically change it like you said.
Click to expand...
Click to collapse
Google search. There's lots of posts on how to fix IMEI as long as you have the original box with your original IMEI.

ChazzMatt said:
Google search. There's lots of posts on how to fix IMEI as long as you have the original box with your original IMEI.
Click to expand...
Click to collapse
I do have the original IMEI. I cant find the correct process to update it however. I've done a lot of research, but all I can find is bits and pieces relating to other devices.
http://forum.xda-developers.com/showpost.php?p=55443848&postcount=1
This is the best info I got, but I cannot get the device to be recognized properly. The setprop command didn't work until I installed CM12. Then i can get as far as having a Marshall London HS-USB Diagnostics 901D device show up. I cant do anything with it at that point.

thecaptain0220 said:
I do have the original IMEI. I cant find the correct process to update it however. I've done a lot of research, but all I can find is bits and pieces relating to other devices.
Click to expand...
Click to collapse
There's also other specialized software like this.
https://www.quora.com/I-lost-a-Moto-IMEI-after-rebooting-It-is-showing-null-now-What-can-I-do
http://www.cdmatool.com/motorola
Just a couple of examples. Doing a Google search for "fix IMEI Motorola"

Related

HELP: No signal (voice or data)!! =(

Hi, I bought a Cappy in december, I rooted, unlocked it (I'm not in the US) and installed Cognition 2.3b8 first, then moved to 3.X, everything was perfect, but yesterday I started with dropdowns in data service then the whole service, I have signal (changing to out-of-service), but I can't make/receive calls, send messages or get data connection, today I flash the phone back to stock and even in stock I have the same problems, also I already try different modems without luck.
Is this a hardware issue?
Thanks!
Give this a try
http://forum.xda-developers.com/showthread.php?t=884364
Thanks...but I know how to install a custom ROM, I already tried Serendipity, Cognition and changing Kernel to SpeedMod and Firebird and different radios (ZNKP1, JK4, JL2, JL1, JL3) and no luck
Have you confirmed that your phone is still unlocked after flashing back to stock?
Check your IMEI number to see if you don't have the generic one.
Check product code to see if it's not botched also.
Xstop said:
Have you confirmed that your phone is still unlocked after flashing back to stock?
Check your IMEI number to see if you don't have the generic one.
Check product code to see if it's not botched also.
Click to expand...
Click to collapse
Well, after installing stock, I insert my SIM back and did not ask for the unlock code, so I assume it's still unlocked.
My IMEI is the same as in the box and IMEI SV = 01
Where can I check product code??
Try *2767*4387264636#
Thanks! Product code is SGH-I897ZKAATT
Everything seems right, if I had to guess... It's more on the unlocking issue after you flashed Froyo with your network.
Try referring to this: http://forum.xda-developers.com/showthread.php?t=831569
I just checked network status screen and everything is off, so the phone it's unlocked :S
Sorry I can't provide you with any more help brotha.
You don't have a corrupted nv_data.bin file, which is good.
Your IMEI number is correct, which I suspected first, cause there were discussion of the generic IMEI number not working on other networks besides AT$T.
Since it doesn't matter what rom, kernel, modem combination you use with no avail.
I would wait to see if someone else chimes in here that might have other ideas.
Things I would do though: Call to see if there is any outages.
Update through kies to see if you get service from the update.
Hope its not hardware related.
Sorry again and good luck. I will keep on searching for ya though
Xstop said:
Sorry I can't provide you with any more help brotha.
You don't have a corrupted nv_data.bin file, which is good.
Your IMEI number is correct, which I suspected first, cause there were discussion of the generic IMEI number not working on other networks besides AT$T.
Since it doesn't matter what rom, kernel, modem combination you use with no avail.
I would wait to see if someone else chimes in here that might have other ideas.
Things I would do though: Call to see if there is any outages.
Update through kies to see if you get service from the update.
Hope its not hardware related.
Sorry again and good luck. I will keep on searching for ya though
Click to expand...
Click to collapse
Thanks for your help!!

ATT blocked my device

So, just a heads up guys (and gals); it looks like ATT blocked my device (reported it stolen) and now I'm locked out of the wireless network.
I still need to call them to see if I can resolve this issue, but it happened after I flashed the latest nightly CM10 and was running it all weekend with no problems, wake up this morning and I can't text, get no data. Try making a call and it states; "This device has been blocked". After using Google, that message is one that happens when a device is reported stolen.
Since I've had this device for it's entire life, there is no chance someone else reported it stolen.
I'll keep this thread updated with what ATT does, if they re-enable my device, etc.
Somebody else had this happen to them on CM10, and it was because their IMEI became generic overnight. You can read about it in the Helly Bean thread.
korockinout13 said:
Somebody else had this happen to them on CM10, and it was because their IMEI became generic overnight. You can read about it in the Helly Bean thread.
Click to expand...
Click to collapse
Huh. How does it overwrite the IMEI on it's own?
I did have a backup of my IMEI from last october (the entire EFS folder) I used ES File explorer to copy it over... But forgot to fix permissions... SLAP forehead.
(Fixed Permissions)
Now I'm back on ATT, guess it wasn't there fault.
:cyclops:
So after reading the other thread, I have to wonder if changing /System to RO mode (via SGS Toolbox) will prevent the EFS folder from being overwritten again? Or am I going to run into this again? The problem seems pretty clear, the EFS folder for some reason has R/W privileges, when it should be RO.
The second part of the equation, is _what_ in JB is deleting that folder?
scythekain said:
So, just a heads up guys (and gals); it looks like ATT blocked my device (reported it stolen) and now I'm locked out of the wireless network.
I still need to call them to see if I can resolve this issue, but it happened after I flashed the latest nightly CM10 and was running it all weekend with no problems, wake up this morning and I can't text, get no data. Try making a call and it states; "This device has been blocked". After using Google, that message is one that happens when a device is reported stolen.
Since I've had this device for it's entire life, there is no chance someone else reported it stolen.
I'll keep this thread updated with what ATT does, if they re-enable my device, etc.
Click to expand...
Click to collapse
This same exact thing happened to me, but I'm on CM9 Stable... Still trying to figure out why my IMEI is the generic one...
I had this happen to me also,,and when I called att customer service they told me that the emei belonged to an iphone that was stolen,,in my case this actually happened three times,,I finally flashed back to stock to reset the emei and it seems to be holding,, I was running helly bean v24 and had been on the rom for a day or something ( well since that version came out ) in fact I have two captivate handsets and one was on v23 and they both switched the emei to the same one,,I have no idea what caused the emei to change but it sure caused some hair pulling on my part lol,, all seems well now
wilson735 said:
This same exact thing happened to me, but I'm on CM9 Stable... Still trying to figure out why my IMEI is the generic one...
Click to expand...
Click to collapse
Same here, but on CM 7.2.0 RC2. I'm not sure if the IMEI just now changed or if it was this way since I flashed CM and AT&T is now cracking down.
The above posts, kind of confirm what I'm sensing is ATT doing something that flashed a stolen IMEI onto rooted android devices.
1) What was the timing of your problem? - For me this happened yesterday morning, or Sunday night after 9 PM PST. I restored my IMEI about 9 AM, and the service restored itself around 13:32 8/20/2012 PST
2) It makes me wonder IS this the custom ROM that changed the IMEI to a stolen iPhone? Why would the ROM choose an iPHONE IMEI? I think this was pushed by ATT. Was it a mistake or was it intentional? Proof? CM 7.2, CM9, CM10 and HellyBean (which is based on CM10 with custom kernel, partitioning). ALL of them set the IMEI to the stolen iPhone THIS last weekend though?
For those of you still needing to restore your IMEI and you don't have a backup, use this thread;
http://forum.xda-developers.com/showthread.php?t=881162
EDIT:
You can also flash back to stock via ODIN to restore your IMEI.
So it looks like the CM10 flash I did Saturday did muck up my IMEI. I was logging into the Google Play store to try and restore my apps from the web, and found out I have two captivates registered.
One with the correct IMEI, the other with this bogus IMEI:
IMEI: **********640000
Here's the whole story:
On Sunday, in the course of 5 hours: 3 times AT&T blocked my device, I called them and got in unblocked. In one of those times, the guy says that the system logs say that my sim card was in an iPhone 3gs that was reported stolen. They also credit me with $25 for each of the 1st 2 times I called.
Anyway, on the 3rd time I ask to speak to a floor supervisor. She is able to tell me that because my phone is reporting an IMEI of a stolen phone, she'll forward it to the Stolen Devices team/department, and that they would get back to me on Tuesday. She can unblock it again on the spot, but eventually it'll get read by the system and blocked again.
I confirm with her that the IMEI that my phone software is showing is the Generic one (004999010640000), and not my actual one that I read to her from underneath the battery.
I was reading through the forums all day on Monday and came to the following conclusions:
1) That Generic IMEI may be what a ROM is mistakenly putting in place, it must use this as a failsafe of some sort, so it can have an IMEI, any IMEI. In reality it should be reading the hardware's IMEI.
2) Our IMEI's did not necessarily get changed this weekend. Last time I flashed, it was when CM9 Stable was released, and that was a couple of weeks ago. So, we may have had this IMEI for weeks, if not months. I know I may have. 1 month ago, my phone got blocked. They said that someone reported it stolen. I called, got my $25 credit, and the service reinstated. I may have had that Generic IMEI at the time.
Last night a technician from the Stolen Devices team instructed me to remove my SIM card from the device for 24 hours so that the network can refresh the IMEI (his exact words, I don't know exactly how the network works, but...) and that this was necessary. Yes, I could ignore him and put by SIM card back into my Captivate, but eventually it would get blocked again. So leave it out of the Cappy, he said, use it in any other device, and after 24 hours you can slip it back in. He said that recently (in the past day or two), many users had been calling about the same problem.
Anyway, just to be on the safe side, I'll be following fohdeesha's instructions here:
http://forum.xda-developers.com/showpost.php?p=30563493&postcount=1780
Flashing back to stock 2.3.5, and seeing if I can get the correct IMEI. If so, I'll backup that EFS folder in 10 different places, revert back to ICS or JB, and if the IMEI is messed up there, I'll restore my EFS backup.
wilson735 said:
Here's the whole story:
On Sunday, in the course of 5 hours: 3 times AT&T blocked my device, I called them and got in unblocked. In one of those times, the guy says that the system logs say that my sim card was in an iPhone 3gs that was reported stolen. They also credit me with $25 for each of the 1st 2 times I called.
Anyway, on the 3rd time I ask to speak to a floor supervisor. She is able to tell me that because my phone is reporting an IMEI of a stolen phone, she'll forward it to the Stolen Devices team/department, and that they would get back to me on Tuesday. She can unblock it again on the spot, but eventually it'll get read by the system and blocked again.
I confirm with her that the IMEI that my phone software is showing is the Generic one (004999010640000), and not my actual one that I read to her from underneath the battery.
I was reading through the forums all day on Monday and came to the following conclusions:
1) That Generic IMEI may be what a ROM is mistakenly putting in place, it must use this as a failsafe of some sort, so it can have an IMEI, any IMEI. In reality it should be reading the hardware's IMEI.
2) Our IMEI's did not necessarily get changed this weekend. Last time I flashed, it was when CM9 Stable was released, and that was a couple of weeks ago. So, we may have had this IMEI for weeks, if not months. I know I may have. 1 month ago, my phone got blocked. They said that someone reported it stolen. I called, got my $25 credit, and the service reinstated. I may have had that Generic IMEI at the time.
Last night a technician from the Stolen Devices team instructed me to remove my SIM card from the device for 24 hours so that the network can refresh the IMEI (his exact words, I don't know exactly how the network works, but...) and that this was necessary. Yes, I could ignore him and put by SIM card back into my Captivate, but eventually it would get blocked again. So leave it out of the Cappy, he said, use it in any other device, and after 24 hours you can slip it back in. He said that recently (in the past day or two), many users had been calling about the same problem.
Anyway, just to be on the safe side, I'll be following fohdeesha's instructions here:
http://forum.xda-developers.com/showpost.php?p=30563493&postcount=1780
Flashing back to stock 2.3.5, and seeing if I can get the correct IMEI. If so, I'll backup that EFS folder in 10 different places, revert back to ICS or JB, and if the IMEI is messed up there, I'll restore my EFS backup.
Click to expand...
Click to collapse
Good information. I've restored my EFS from a backup I made last october when I first rooted and flashed CM7.
Not sure what leaving the SIM out does? Does it correct the IMEI folder on it's own?
Sooo, I ended up having this situation for first time last night.
What I did was:
1) One click kk4 stock
2) Flash Devil's kernel to get CWM
3) Flash Helly Bean 8/13.
4) Flash ugjk4 modem.
Bam wrong IMEI.
Did the whole thing again, this time using ugjk3 modem - bad IMEI again.
Then I just copied back my efs folder, chown to radio:radio, chmod to 0700 and reboot - IMEI got fixed.
What is really shady is when is this happening? After the initial devil kernel flash? Or the initial helly bean flash when it does the partitions and reboots you back into recovery?
scythekain said:
Good information. I've restored my EFS from a backup I made last october when I first rooted and flashed CM7.
Not sure what leaving the SIM out does? Does it correct the IMEI folder on it's own?
Click to expand...
Click to collapse
Leaving the SIM card out cannot change, reset, or fix your imei, it can't effect it at all.
Leaving the sim card out simply blocks your phone from being able to "phone home" to att, and report the incorrect imei to att. Because when att sees this, that is when they block your device.
This is why I suggested in other posts that when you are flashing a new rom, leave your sim card out. This way if the rom flash does reset your imei, you can repair it and THEN put your sim card back in, without the phone automatically phoning home to att with the wrong imei right off the bat and getting your phone blocked
Ok I have a quick question. I copied my entire EFS folder and copied it into my external SD card. Do I need to do anything else to back it up? I have the correct IMEI and want to make sure it stays that way. I noticed one person mentioned the need to fix permissions. Is that all I need to do. Thanks.
I would make a copy and put it on ur computer as well.
Sent from my SAMSUNG-SGH-I897 using xda premium
Has this been figured out yet? Anyone have any idea why this is happening to some people and not others? What's the common factor here? After several initial failed flash attempts I went from one click froyo, to several cm9 nightlys, to hellybean 8/13 , to cm10 nightly 8/18, to cm10 nightly 8/22. So far I've had zero imei issues. My number still matches the back of the phone. Is this something att is sending out, an app, or one of the ROMs being flashed? I just checked and the permissions for my efs folder are set to rwx r-x r-x. It may help if everyone lists their history.
Sent from my SGH-I897 using xda app-developers app
rickneworleansla said:
Has this been figured out yet? Anyone have any idea why this is happening to some people and not others? What's the common factor here? After several initial failed flash attempts I went from one click froyo, to several cm9 nightlys, to hellybean 8/13 , to cm10 nightly 8/18, to cm10 nightly 8/22. So far I've had zero imei issues. My number still matches the back of the phone. Is this something att is sending out, an app, or one of the ROMs being flashed? I just checked and the permissions for my efs folder are set to rwx r-x r-x. It may help if everyone lists their history.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
1) I used one click root, to root my phone back in October, then backed up my EFS.
2) Odin CM7 CWM.
3) Flashed CM 7.1 stable, got fed up with the /datadata limitation pretty quickly. Tried Miui. (had same problem)
4) November, flashed last available nightly for CM 7.1 (till march of this year) this change the structure of /datadata to have about 400 Megs and to warn when it's getting full.
5) January, started flashing nightly kangs weekly.
6) Mid March, flashed CNA 4.0.3 - Horribly laggy.
7) Flashed AOKP, CM9 nightlies etc. Ended up sticking with CM9 nightlies.
8) 8.18 flashed CM9 nightly.
9) 8.18 flashed UXKH2 modem (awesome voice quality)
10) 8.20 no wireless data/signal - device blocked.
According to the Google Play store, the incorrect IMEI was registered on Monday. Which means something deleted it Sunday night Monday morning while I was sleeping.
(if you want to you can view your account history and registered devices here
https://www.google.com/dashboard/
IMEI
this recently happened to me over the weekend. I simply flashed back to stock KK4 and i had my IMEI number back to what its supposed to be. I never had to call AT&T to unblock it. once I got my IMEI back, I flashed a custom corn kernel and installed root. while I still had the original IMEI I downloaded an app called Galaxy S Unlock and in this app there is an option to back up only your efs folder and its contents. after making two back ups I decided to flash the latest Helly Bean from Der Teufel whilst leaving my SIM out. once all was said and done I still had my stock IMEI number with CM10 Helly Bean. the only number that I notice changed is the IMEI SV. it went from 00 at stock KK4 to 05 on cm10. I don't know what that number represents but it doesn't seem to affect me. good luck to anyone with this issue.
cheeesboiger said:
this recently happened to me over the weekend. I simply flashed back to stock KK4 and i had my IMEI number back to what its supposed to be. I never had to call AT&T to unblock it. once I got my IMEI back, I flashed a custom corn kernel and installed root. while I still had the original IMEI I downloaded an app called Galaxy S Unlock and in this app there is an option to back up only your efs folder and its contents. after making two back ups I decided to flash the latest Helly Bean from Der Teufel whilst leaving my SIM out. once all was said and done I still had my stock IMEI number with CM10 Helly Bean. the only number that I notice changed is the IMEI SV. it went from 00 at stock KK4 to 05 on cm10. I don't know what that number represents but it doesn't seem to affect me. good luck to anyone with this issue.
Click to expand...
Click to collapse
The "SV" is the Software version, it doesn't affect your IMEI (your device identifier).
http://imeimobile.blogspot.com/2009/11/structure-of-imei-and-imeisv.html
Your sim card has been blocked after put in the lose/stollen AT&T phone .
Your sim card has been blocked after put in the lose/stollen AT&T phone .

[Q] Unrooting HTC One running 3.04.651.2 with hboot 1.55

Hi All ,
My apologies if there is a solution to my problem in another thread. I have spent countless hours looking for a way to unroot my Sprint HTC One because the Sprint network can't seem to activate it until I do. Or I need to figure out a way to force the Sprint network to accept my MDN and MSID which can "sometimes" be problematic with rooted devices. It might be easier to just unroot and see if that helps getting the phone to properly activate.
Other than the network connectivity issues, the phone is fully functional. Just cant make calls or send texts.
I am running this ROM based on benny's system dump: http://forum.xda-developers.com/showthread.php?t=2467607 so my device information is:
Android version - 4.3
Sense version - 5.0
Software version - benny's 4.3
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
I've tried everything I can think of to get my device unrooted, but none of the RUUs work due to being on hboot 1.55 s-on or having an older firmware version (1.29.xx or 1.39.xx.)
Is there any method I can use to get completely back to un-rooted stock rom with, relocked boot loader (know how to do that part), stock recovery, etc?
I've looked at so many different threads and google searches and all say you need to be s-off and run RUUs of versions that will either cause my touch screen to not work or worse. If anyone can help me it would be amazing and I would be much obliged.
I am having similar issues. I'm about to try this method - http://forum.xda-developers.com/showthread.php?t=2470569&page=3 Read OP and see post#27
jharre08 said:
I am having similar issues. I'm about to try this method - http://forum.xda-developers.com/showthread.php?t=2470569&page=3 Read OP and see post#27
Click to expand...
Click to collapse
Ah yes! The 3.04 version wasn't available the last time I read that post! I can confirm that the other that using the 1.29 and 1.31 versions caused serious issues for me and my phone. This post is actually what led me to learn about the issues due to different firmware and file structure between new and older versions.
I'm downloading now. Let me know how it goes!
tuckprodigy said:
Ah yes! The 3.04 version wasn't available the last time I read that post! I can confirm that the other that using the 1.29 and 1.31 versions caused serious issues for me and my phone. This post is actually what led me to learn about the issues due to different firmware and file structure between new and older versions.
I'm downloading now. Let me know how it goes!
Click to expand...
Click to collapse
Also, check this out - http://qbking77.com/development/how-to-unrootunbrick-the-htc-one-to-stock-2/
It's a bit dated, but I am going to try this method if I can find a 3.04 RUU. Note, he is doing this to an S-On phone, which is what we have. So it SHOULD work:good:
Nothing against the first method I posted, but I'd much rather do a RUU and get a clean slate...
There is no RUU for 3.04 yet ( that I know of)...
this is your best (and pretty much only) option: http://forum.xda-developers.com/showpost.php?p=46565593&postcount=27
Did you ever find a way to resolve this issue? Also did this start after flashing Cyanogenmod? I have the exact same issue and it seems I have exhausted all available resources. Currently have the following setup:
Android version - 4.3
Sense version - 5.0
Software version - 3.04.651.2
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
Noticed that the phone is unable to update PRL correctly. Version will switch from 00000 to 1 to 55016. I am also unable to commit changes to any EPST settings (which is the first thing sprint tried to do). MDN and MSID both currently say 'no' and I can't update.
I'm having the exact same issue with everything working fine but no calls/texts.
I flashed the Guru reset for 3.04 but still no calls/text.
Any other solutions?
kindabizzie said:
I'm having the exact same issue with everything working fine but no calls/texts.
I flashed the Guru reset for 3.04 but still no calls/text.
Any other solutions?
Click to expand...
Click to collapse
Try the following:
Full wipe. Flash the newest stable CM.
Go into Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
Confirm the following settings:
Network mode = LTE/CDMA/EvDo
CDMA subscription = NV
After you confirm these settings, switch the network mode to CDMA/EvDo only and then back to LTE/CDMA/EvDO.and give it a minute or so, you should see 3G/Phone availability come back. You can test this by dialing a number. You should be able to make a call, or at least get the default Sprint "device is not activated" recording. After confirming this, you can do another wipe and flash back to a stock ROM. You should now have mobile network connectivity back. You may need to Activate the phone again and update the profile/PRL to get back to 100%.
jjmckaskie said:
Try the following:
Full wipe. Flash the newest stable CM.
Go into Settings > More... (under Wireless & Networks) > Mobile networks > CDMA subscription:
Confirm the following settings:
Network mode = LTE/CDMA/EvDo
CDMA subscription = NV
After you confirm these settings, switch the network mode to CDMA/EvDo only and then back to LTE/CDMA/EvDO.and give it a minute or so, you should see 3G/Phone availability come back. You can test this by dialing a number. You should be able to make a call, or at least get the default Sprint "device is not activated" recording. After confirming this, you can do another wipe and flash back to a stock ROM. You should now have mobile network connectivity back. You may need to Activate the phone again and update the profile/PRL to get back to 100%.
Click to expand...
Click to collapse
Didn't work man, thanks though. My data is fine, I just can't call/txt...it's really bizarre...
kindabizzie said:
Didn't work man, thanks though. My data is fine, I just can't call/txt...it's really bizarre...
Click to expand...
Click to collapse
Hmm. That's pretty much the issue that I had except 4G/Wifi was working and 3G/Call/Text didnt seem to be. You might try switching the CDMA mode to SIM and then back to NV to make sure the setting takes. I know CM can be really finicky with network changes.
tuckprodigy said:
Hi All ,
My apologies if there is a solution to my problem in another thread. I have spent countless hours looking for a way to unroot my Sprint HTC One because the Sprint network can't seem to activate it until I do. Or I need to figure out a way to force the Sprint network to accept my MDN and MSID which can "sometimes" be problematic with rooted devices. It might be easier to just unroot and see if that helps getting the phone to properly activate.
Other than the network connectivity issues, the phone is fully functional. Just cant make calls or send texts.
I am running this ROM based on benny's system dump: http://forum.xda-developers.com/showthread.php?t=2467607 so my device information is:
Android version - 4.3
Sense version - 5.0
Software version - benny's 4.3
Kernel version - [email protected] #1 SMP PREEMPT
Baseband version - 1.00.20.0913_3
Build number - 3.04.651.2 CL251863 release-keys
I've tried everything I can think of to get my device unrooted, but none of the RUUs work due to being on hboot 1.55 s-on or having an older firmware version (1.29.xx or 1.39.xx.)
Is there any method I can use to get completely back to un-rooted stock rom with, relocked boot loader (know how to do that part), stock recovery, etc?
I've looked at so many different threads and google searches and all say you need to be s-off and run RUUs of versions that will either cause my touch screen to not work or worse. If anyone can help me it would be amazing and I would be much obliged.
Click to expand...
Click to collapse
You may need to flash a stock rom and manually enter you MDN and MSID using the epst menu
no luck
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
tuckprodigy said:
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
Click to expand...
Click to collapse
Dang, and I was gonna go to a Sprint store after work. *Sigh* guess I have NO CHOICE but to get a Nexus 5 now, lololol
kindabizzie said:
Dang, and I was gonna go to a Sprint store after work. *Sigh* guess I have NO CHOICE but to get a Nexus 5 now, lololol
Click to expand...
Click to collapse
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
jjmckaskie said:
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
Click to expand...
Click to collapse
I still took it to Sprint just to see and they fixed it. Downside is my GPS and LTE is messed up again (Me trying to fix those things is the reason all this happened in the first place) but I'd rather not have GPS than not have phone capabilities on my phone (And LTE in Los Angeles is garbage anyway). I think I'm gonna leave my phone alone for a while tho, lol.
jjmckaskie said:
As a last resort you could also try the hard reset code from your dialer by entering ##72786# . You will need to be on a stock rom. You will also need your MSL code (you can usually get this from Sprint support). This will reset EVERYTHING so be mindful. It will also force a hands free activation/Profile/PRL update after the phone reboots which is sometimes useful.
Click to expand...
Click to collapse
Looks like I am going to go this route. I hit ##72786# and it takes me to SCRTN screen. I'm guessing I just hit menu in the top right, then reset? Then it will prompt me for my MSL code?
jharre08 said:
Looks like I am going to go this route. I hit ##72786# and it takes me to SCRTN screen. I'm guessing I just hit menu in the top right, then reset? Then it will prompt me for my MSL code?
Click to expand...
Click to collapse
Yup. I actually dont remember if it does a full wipe, or just forces an activation/profile/PRL update. But either way it's worth a shot.
tuckprodigy said:
At this point I have not had any luck solving this issue. I used Guru's reset tool as well and believe the problem is the radio firmware. I spent a good deal of time on the phone with Sprint support and with a surprisingly competent technician in the store. He tried to work with multiple different systems they have available to get the phone to recognize the Sprint towers with no success.
He said that the phone just isn't recognizing them in any way and commented that a phone that isn't activated will still show bars of service because the phone gets the signals from nearby towers, but just doesn't know what to do with the signal until activated. In my case, all I see is the "X" above the signal bar graphic.
If you're experiencing the same issue as me, there is nothing Sprint can do to make the phone recognize their towers based on the conversations I've had. I saw my options as:
1. Wait for an RUU to come out or something like that
2. Try out different ROMs - jjmckaskie suggested the newest CM, but I would think others might be worth trying as well. Basically anything that uses different radio firmware
3. Get a new phone - This is the option I've gone with. Since my phone is running a stock ROM and the guy at Best Buy where my insurance is from, didn't check the bootloader (would have said "tampered" and "unlocked"), he assumed I never voided my warranty and sent out for a refurb. This may not work if your insurance is through Sprint though. I'm not sure how thorough they are.
Click to expand...
Click to collapse
Sounds like you solved your issue, but for anyone else having trouble....
I re-tried GURU's reset and it worked. The first time I downloaded it over the 4G network. I also downloaded the OTA over the 4G network. My radio has been giving me fits ever since. Finally, I downloaded GURU's reset over WIFI, then made sure the OTA downloaded over WIFI, and my phone is like new again! No radio issues, everything is perfect. Hope this helps some people...

no service?

I just got the note 4, rooted it and flashed a rom, however I have no service it shows. I am using Metropcs and it shows "no service" no matter what I try, if I take the sim card out then it will show the logo that there is no sim card inserted so it does recognize it at least. The sim card and service works fine in my other phones but I can't figure out how to get it to work on here.
Check ESN on Swappa??
macasus76 said:
Check ESN on Swappa??
Click to expand...
Click to collapse
I have checked the ESN and it comes back as clean.
theinspector said:
I have checked the ESN and it comes back as clean.
Click to expand...
Click to collapse
What is the model number? And in "settings/ about device/status" does your number, IMEI, Network state or network show up?
macasus76 said:
What is the model number? And in "settings/ about device/status" does your number, IMEI, Network state or network show up?
Click to expand...
Click to collapse
The model number is the N910T3 version, it does show my number, it lists the IMEI and for all of the network state related stuff it lists it as "UNKNOWN."
Are you still on TEKXodus? If you came from an older version ie..4.4.4 or whatever then I'd suggest Odin flashing 5.1.1 stock, see if you get service then try flashing the custom rom again. Might be a mismatch in baseband and all that. Open dialer and punch in these numbers *#12580*369#*and make sure everything matches. Also run thru the thread you found the rom and make sure you flashed everything suggested.
macasus76 said:
Are you still on TEKXodus? If you came from an older version ie..4.4.4 or whatever then I'd suggest Odin flashing 5.1.1 stock, see if you get service then try flashing the custom rom again. Might be a mismatch in baseband and all that. Open dialer and punch in these numbers *#12580*369#*and make sure everything matches. Also run thru the thread you found the rom and make sure you flashed everything suggested.
Click to expand...
Click to collapse
I tried Odin flashing the stock 5.1.1 firmware and had no luck, also used Samsung Kies firmware to try and go back to stock as well just in case that would solve anything and I have no luck. It just shows " (No Service) " When I look in the status bar, and it still says it isn't registered.
And when you open dialer and input this *#12580*369# everything matches?
macasus76 said:
And when you open dialer and input this *#12580*369# everything matches?
Click to expand...
Click to collapse
I'll go ahead and attach an image as well to show. Yes everything seems to match up when I input that in the dialer.
Sorry I wasn't doubting your word lol, honestly I'm kinda stumped as well, almost seems to be network locked. Is it a Metro branded phone or Tmobile? I wouldn't think that would matter. Wish I was more help fella
macasus76 said:
Sorry I wasn't doubting your word lol, honestly I'm kinda stumped as well, almost seems to be network locked. Is it a Metro branded phone or Tmobile? I wouldn't think that would matter. Wish I was more help fella
Click to expand...
Click to collapse
It is a T-Mobile brand phone, which I figured wouldn't matter much anyways, I've owned a few T-Mobile phones in the past and have had no issues using Metro Pcs even if the phone was locked because T-Mobile does own them. That's perfectly fine, thank you for giving some suggestions anyways that I hadn't thought of.
The Apn checks out? In settings?
U could also try flashing a data fix for the international roms. Maybe last resort try a new sim
Like the guy above said have you checked apn settings? You could also try in the mobile setting where it says Network Operators and then Search Now and let it search. Choose Tmobile if it pops up or if MetroPCS pops up choose that. If you need MetroPCS apns I have them since I'm on MetroPCS. Let me know if you've fixed this because I haven't rooted yet and plan to root and install Tekxodus rom but if this is a problem then I'll just stick with stock unroot. I have the N910T tmobile brand if that matters
APN settings have really nothing to do with his dilemma, my question would be this for the OP. Please check if the IMEI number matches the one that's on the back of the phone under the battery. I have a work around but i need to verify.
I went through the same problem coming from TekXodus rom. I tried everything and no luck. Flashed 5.1.1 stock and called tmobile about it. after their tech guy didnt know anything else i could try they sent me a replacement.
And now here I am again
I also flashed tekxodus from my wifes 4.4 phone. Now no sim card issue. Same as op.
Edit: flashed the correct baseband. All good over here.
Sent from my SM-N920T using Tapatalk

pixel 4 xl mobile network problem

need some help here , my pixel 4 xl just updated to jan 2021 update
, post update im unable to connect to mobile network .
already tried hard reset not working
also flashed previous factory image still aint working
is any other thing i can try to solve the problem or im doomed?
capayam said:
need some help here , my pixel 4 xl just updated to jan 2021 update
, post update im unable to connect to mobile network .
already tried hard reset not working
also flashed previous factory image still aint working
is any other thing i can try to solve the problem or im doomed?
Click to expand...
Click to collapse
Who is your provider? Are you using SIM or eSIM? Are you rooted? Did you disable all the Magisk modules before the update? If you forgot that step, have you since disabled all Magisk modules and started over?
While you may be out of commission on the phone side (although, Google Voice would be a good band-aid), you may not be out of commission on the SMS side. Google's text app, Messaging, recently went live with RCS messaging and it can send texts via WiFi.
Incidentally, if it's Google Fi that's giving you fits, the same thing happens to me every time I do a clean install. Fi refuses to connect until I've rebooted two or three times and then the final confirmation comes several hours later.
im in malaysia bought secondhand 1 year ago on grey market , check my sim with another phone , working well on that phone. had been running my phone on regular stock since bought.
capayam said:
im in malaysia bought secondhand 1 year ago on grey market , check my sim with another phone , working well on that phone. had been running my phone on regular stock since bought.
Click to expand...
Click to collapse
Okay, you answered almost none of my questions but it's irrelevant at this point because it sounds like the phone was stolen. If the IMEI is reported as stolen, it's flagged in a database and alerted carriers will shut off the service.
If that's the case, at this point, I'd be more concerned about the police knocking on my door than lack of mobile service. I'd send you over to IMEI.info to verify but I'm guessing I haven't told you anything you didn't already know.
imei number legit not reported or blacklisted, but yeah i think this phone is doomed unless there some magic update resolved this
capayam said:
imei number legit not reported or blacklisted, but yeah i think this phone is doomed unless there some magic update resolved this
Click to expand...
Click to collapse
Why don't you try to reset using the last official 10 firmware (to reset all partitions), then activate through setup, then flash and test a custom rom. This is of course only possible if it's an unlocked bootloader (which you didn't mention) but that's where I'd start especially if it worked before the update. You say is legit and sounds like it worked BEFORE the last update so roll back and then use a custom rom.
GROOVYJOSHCLARK said:
Why don't you try to reset using the last official 10 firmware (to reset all partitions), then activate through setup, then flash and test a custom rom. This is of course only possible if it's an unlocked bootloader (which you didn't mention) but that's where I'd start especially if it worked before the update. You say is legit and sounds like it worked BEFORE the last update so roll back and then use a custom rom.
Click to expand...
Click to collapse
will try it later dude
capayam said:
will try it later dude
Click to expand...
Click to collapse
Unfortunately it's my best guess because I can't reproduce it myself but if it worked prior to the firmware upgrade, it should work by reverting the firmware to the previous firmware in my opinion. I'd take it the step furtherand go with a custom 10 ROM to remove Google firmware updates messing with it in the future (assuming we get it working again).
Interestingly enough, I searched other forums and found other users reporting the same issue. Again, assuming it worked on the previous firmware, I would roll bak to it. Ideally, I would rollback to 10 because I know 10 works (not sure how well it works for you in your local and provider), but thats where I would start. Backup everything you need, then use the last 10 firmware to -w the device and activate then start over.
Why is this posted in development?
shiftr182 said:
Why is this posted in development?
Click to expand...
Click to collapse
who knows

Categories

Resources