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 .
Related
Hey, i messed up my efs files awhile back when froyo was first getting leaked onto I9000 and flashed to my samsung captivate. So i have the generic fake samsung EMEI code of 004999010640000 so that i can use the AT&T network. I never made any back up of efs files and i recently tried to restore my emei using the two methods in android development but still no luck getting my original IMEI. I need get a warranty exchange through samsung due to search button randomly engages on its own and am worried that samsung will see that the EMEI code is different and try to void my warranty since it would be evidence that i messed with the software. I have my original box so i know my original IMEI code so is there a way to manually enter my code or any other way to restore my EMEI. Or do u think samsung would even notice anything with the android software?
Fix IMEI
OP, ODIN3 One-Click Master Clear will get it all back 4 U. I just posted on another thread about this same issue. I went through hell trying anything I could find, was ready to go to AT&T for a swap out. I gave ODIN3 One-Click Master Clear a try and it did it for me. So give this a try, you'll kiss your phone after You done
Just flashed back to stock and turn in your phone. Don't think the warranty dept are gonna be that anal for the exchange.
If they have questions on the IMEI number, tell them all you did was the kies update to JH7.
You shouldn't have any problems. It's been done before
edit: Btw, make sure you have JH7 installed
People assume that the rep at at&t has any clue what they are looking at.
Put a sticky note that says "phone" on it before you pack it up so the AT&T people will know what it is.
lol ok ill be sure to do that when i exchange it. But ill be dealing with samsung warranty on this one. I tried AT&T when my imei got messed up the first time, and i needed an network unlock code to use my captivate that didnt exsist and they wouldnt exchange me phones cause i was past 30 day return by 2 weeks, assholes.
If i do the master clear with odin will all the at&t network settings be erased and have to input them manually? Hopefully i can find the settings online if thats the case. A smart phone with no network is an expensive paper weight, lol.
Are you not able to get on the ATT network with the generic IMEI number? I have the generic IMEI number running on my phone now with it ending 40000 and I'm having no trouble getting on the the ATT network.
Edit: I do have a backup of my efs with the correct IMEI number too, just lazy sometimes on restoring the original efs. Just make sure your product code is correct and you should be able to update through kies to get back to JH7.
I have a factory unlocked P1000 that recently started having some issues. When I first got it two years ago, I had flashed it with the following:
PDA1000DXJK2
PHONE1000DXJJ2
CSC1000OLBJJ2
During all that time, everything was working fine everywhere I had been (Asia and North America), with at least three different SIM cards and carriers.
About three weeks back, I suddenly lost voice/data. At first, I thought it was a SIM/carrier issue, but some swapping with a friend revealed that it was my tab that was the problem. Searching here and elsewhere, all I could come up with was that my IMEI was showing as the generic 0049990106400 and not the one listed on the back of my tab. I had been aware of them not matching, but it had never caused problems in the past. I was able to confirm, however, that the radio/modem was still working. I could place emergency calls, I could see that the networks were there, I just could not connect to any of them.
In my attempts to restore the original IMEI, following a guide here, I managed to lose my broadband entirely. I have been researching and trying to get it back ever since, so far to no avail. Unfortunately, I haven't been able to find a copy of the P1000DXJK2/DXJJ2 firmware I used the first time. However, I have tried multiple stock ROMS, different tutorials, and most recently, flashing with Overcome 4.1. The result is always the same: everything works except for the phone. Phone, broadband, and IMEI list as unknown.
Currently:
PDA: P1000XXJQ1
PHONE: Unknown
CSC: P1000OXAJQ1
Model number: GT-P1000
Firmware version: 2.3.3
Baseband version: Unknown
Kernal version: 2.6.35.7 [email protected] #2
So, here I am desperately appealing for any help anyone might be able to provide. My tab has been my only phone for years and often my only internet access, so I am feeling pretty lost without it. I am fairly tech savvy and I follow instructions very well, but I have never really messed around much with Android, so I am hoping the experts here are going to be able to come up with something.
So, you said you most recently use overcome 4.1.
When you first use Odin to flash GB-stock-safe-v5, before you put overcome kernel, what is the IMEI?
No point to proceed to Overcome ROM if GB-stock-safe-v5 didn't bring back the IMEI.
Yes, that is what I assumed, but I gave it a try anyway. If nothing else, it gave me better recovery mode tools.
As I said above, nothing has worked so far. My IMEI was unknown before flashing with GB Stock, as it is now. However, at this point, I would be happy just to get a working modem again, even if the IMEI remains messed up... One thing at a time.
the fact that the IMEI suddenly is gone, and on further tweaking the radio/baseband is gone, I think your internal storage is failing.
first it hits the EFS area, then the baseband area.
That is my suspicion.
You could probably proceed to flash latest CM/AOKP or whatever, which repartition your internal storage.
You should get your baseband, because the /radio/modem.bin in those MTD partitioned ROM sits on a different part of the storage.
But since you never have a backup of your EFS, those ROM will not give you your IMEI either.
Only flashing a stock ROM will give you the right EFS (assuming the area it writes into is writable)
I also wonder if there a person expert enough to rewrite the pit file, so that your EFS and baseband is shifted from its original position, and use that with the GB stock safe v5
This is an interesting idea. To clarify, though, my IMEI did not suddenly go, to my knowledge. For at least the last year and a half, the IMEI listed did not match the one printed on the back. Everything worked fine, so I never gave it much thought. What I do not know is if it changed again, or if it has been the generic one I listed above all along.
Could it be that something is simply wrong with the EFS, preventing the modem.bin from flashing correctly? One of the IMEI restoration tutorials I attempted early on involved messing with the EFS. I believe this was the same night the modem stopped working, though I did not notice a direct cause-effect relationship. There were other (failed) attempts between that and broadband coming up "unknown." I will admit I was a little hasty in those first few days. I was traveling, crunched for time, and panicked that I would have no phone.
Hi!
Resume:
My note has some weird problem with the modems. I'm getting "Unknown" baseband, modem verison, phone number, IMEI etc. with all the modems I tried except one, which shows the correct IMEI and modem version but still not working(I can even see the mobile networks with that one, but I it doesn't connect and gives me "Refresing SIM data" messages).
Click to expand...
Click to collapse
I always have been using custom roms(only TW) and updating my note to the latest version and I never had a problem.
One day, some months after the last rom update, started to lose the phone network conection and I was getting pop-ups with "Refreshing SIM data"(was very annoying because that was turning on the phone screen every few minutes). Sometimes I had phone network and sometimes I hadn't. The disconnections became more frequently. The phone also started to eat up the free space for apps, so I had to remove several apps to install or update even a small one.
So I decided to change to a different ROM to see if that fixes both problems, but I got the actual problem.
I was in AllianceRom v3 JB when that happened.
I flashed this AryaMod 5.5 JB following their instructions and I got this weird problem. In the "About phone" says that the Baseband version, IMEI, IMEI SV, Network and My phone number are "Unknown". I can't even search for mobile networks because it says "Insert SIM card" when I try to open the Mobile networks menu. Tehre are no signal bars, only a "denied" icon on the status bar.
I tested all JB modems and some from ICS from the "all modems" thread, but I was getting the same "Unknown" things in each one, except the XXLSO, where the Baseband version, IMEI and IMEI SV were okey. I could also find mobile networks with this modem, and the "Refreshing SIM data" thing returned, but it was not possible to connect to a network. With this one, there aresignal bars, but they are empty.
I flashed the AllianceRom and even the old ICS rom I had before, but the problem persisted, even with the modems they came with.
Now I'm on the latest Samsung rom(LT4), unmodified and flashed with odin and the problem persist.
I found this old thread. His initial problem is very similar to mine, but they don't know what caused it nor how to fix it.
I have also found something about corruped IMEIs that you can fix doing something with the ADB and restoring EFS folder, but I think that is not my case because I can see my original IMEI with the XXLSO modem (and I my EFS folder looks OK, anyway I have no backup of that).
I don't expect to get a step-by-step tutorial about how to fix this, but I hope somebody can put me in the right direction. I will post the solution if I find one!
What are the first 4 digits of your imei
Sent from my Nexus 5 using Tapatalk
Thanks for reading, the four first digits are 3595.
Maybe this is a stupid question, but have you tried re-seating your Sim card, or even a different Sim?
Sent from my Nexus 5 using Tapatalk
I tried both. Also I have been using the SIM with another phone for weeks and works fine. Tried to take out the battery and wait few minutes and other "stupid" things like re-flash a ROM, re-wipe all, etc..
Maybe it's the programed obsolescence, you can use the Note as PDA but if you want a phone, go and buy another...
@ThaiDai or @nokiamodeln91 I believe knows of a way to fix this if its an EFS issue...but you don't have a developer imei
Did you have an old efs backup from when u first rooted your phone?
Sent from my Nexus 5 using Tapatalk
AndroidSlave said:
@ThaiDai or @nokiamodeln91 I believe knows of a way to fix this if its an EFS issue...but you don't have a developer imei
Did you have an old efs backup from when u first rooted your phone?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
If it was a corrupted IMEI issue then it should not come back when the xxlso modem is flashed.. And also not sure why it goes to unknown when any other modem is used.. Could there be any physical damage to the sim tray? Dropped the phone?
I have no backup of efs... I had one "nandroid" but deleted it after everything was okey...
I could delete the efs folder, so this unknown problem will turn a known one :victory:
I dropped the phone a very few times, maybe in one of those something broke a little and has increased more with the usage? (the disconnections from the network became spontaneus and progressively).
I found this other thread, I could try the same but I can't find the original GB firmware, every link I find is in hotfile.
Check in Samsung-updates.com firmware section. There are 2 GB roms there..
I found a efs backup from may 2012, probably auto-created when first installed ICS.
I flashed the stock GB rom and restored it following this tutorial for my .tar.gz file, but didn't work, so the device may be lost. I only have 3 more backups: boot.img, data.ext4.tar and system.ext4.tar. I guess they are useless to fix this...
Thay you for you support!
Earlier this week I had an unsuccessful install of the alpha CyanogenMod 13.0 rom - didn't want to be encrypted so I substituted the latest HC M kernel. wasn't the first time I couldn't get a new rom to boot so didn't initially think much about it but following that flash I couldn't get any new rom to install and successfully complete setup. Each try would get stuck at step right after wifi was set up. I eventually determined there was an issue trying to connect with Google servers. Tried a multitude of fixes but nothing worked. Ultimately I found that my IMEI and IMEI ID had been hosed and both were now 0's rather than the original IMEI number. I unfortunately did not have the efs partition backed up (at least that I could find). I have tried every method, tool, etc. I have been able to locate to repair or to re-write the IMEI to the phone but so far to no avail.
I restored the original stock software (going back to the original lmy47e on the phone when I purchased it) as well as subsequent releases with a hopeit could somehow restore the IMEI but nothing has worked. I have managed to getto where I can make and receive calls and SMS/MMS but once I'm out of wifi range, no internet access. I even have trid a new SIM from Verizon but tha made no difference. Still a bit confused as to where the IMEI value is stored (and how it could be corrupted) but at this point it looks like new phone time (already ordered a new N6 from Amazon).
Hoping maybe someone might have some suggestion that might help me out. Seems like the N6 is new enough and different enough that the usual fixes don't seem to work. I know discussions around flashing IMEI's isn't really legit on xda but I'm just trying to get back my original IMEI rather than trying to mask a problem phone.
The only accepted way to get it back is to restore a back up. Having the IMEI corrupted happens when roms flash the wrong partitions. Samsung is known for storing the IMEI in a partition that is easily corrupted or erased when flashed. Not normally a nexus issue and I'm not sure which partition the IMEI is stored under.
It is not unheard of that cm roms have some issues like this. It wasn't to long ago that they bricked some nexus.
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"