Related
So I just received a replacement phone via warranty from T-Mobile.
I have upgraded to Gingerbread 2.3.6 and am rooted.
I just realized now that the IMEI number in Android is 00000000.
I'm not sure if it was like this before I started tinkering with it or if it happen as a result of the root/upgrade.
Anyways, I have the sticker that gives me the IMEI number under the battery, I just need to know if/how I can get this back into my phone. I've read something involving a HEX editor? But I don't know what or how.
Any advice and links would be greatly appreciated.
A little more information. I originally noticed that the IMEI was set at 0000000 because I tried to install Swype beta and it says cannot install on an android emulator. Further googling of this lead me to realize that swype wasn't recognizing my phone as a legit android OS because the IMEI number was missing...so yea. This is where I am now.
CoBfan1987 said:
A little more information. I originally noticed that the IMEI was set at 0000000 because I tried to install Swype beta and it says cannot install on an android emulator. Further googling of this lead me to realize that swype wasn't recognizing my phone as a legit android OS because the IMEI number was missing...so yea. This is where I am now.
Click to expand...
Click to collapse
Did you make any backups before upgrading to Gingerbread 2.3.6?
ADD: Here is a quote off another thread with this problem:
I got my IMEI back. I had my nv_data.bin.md5 and nv_data.bin backed up when I unlocked my phone after I got the new one from Samsung. I just coppied them the the efs folder and my IMEI is back."
Hope it helps! And hope you have a back up... maybe even from your other phone?? Or before you upgraded the phone you have.
Should they be in this directory?:
/efs/root/afs/settings
because those are the only ones i can find
Sent from my SGH-T959V using XDA App
CoBfan1987 said:
Should they be in this directory?:
/efs/root/afs/settings
because those are the only ones i can find
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Yes.
10char
So I have the nv_data.bin and nv_data.bin.md5 files from my old phone and from my new phone. Sorry, I wasn't thinking enough to make a backup of these files when I upgraded to Gingerbread using Samsung Kies.
So now, with these two sets of files. Do I want to take the old (and good) files from my old phone and replace the files on my new phone. Won't that transfer the old phone's IMEI though?
CoBfan1987 said:
So I have the nv_data.bin and nv_data.bin.md5 files from my old phone and from my new phone. Sorry, I wasn't thinking enough to make a backup of these files when I upgraded to Gingerbread using Samsung Kies.
So now, with these two sets of files. Do I want to take the old (and good) files from my old phone and replace the files on my new phone. Won't that transfer the old phone's IMEI though?
Click to expand...
Click to collapse
First - Is your phone working?
Second - Have you tried a factory reset if your phone is working?
Third - Try a factory reset and reflash a stock rom.
Fourth - If you phone is not working give it a shot and let us know
Yes the phone is working fine. Just with the IMEI missing, I can't get Swype beta to install (I'm assuming that is the problem)(That the only problem I've found so far). Would a factory reset restore the bin files and IMEI number then?
CoBfan1987 said:
Yes the phone is working fine. Just with the IMEI missing, I can't get Swype beta to install (I'm assuming that is the problem)(That the only problem I've found so far). Would a factory reset restore the bin files and IMEI number then?
Click to expand...
Click to collapse
What I have read is a factory reset or reflashing a ROM (or both if all else fails) should restore your IMEI. I have also read flashing the original ROM that came on the phone has worked. You may try that if the factory reset does not restore it.
Since your phone is working don't copy the files over from your other phone
Do let us know your progress.
How do I obtain the original rom, is it posted here in the forum?
CoBfan1987 said:
How do I obtain the original rom, is it posted here in the forum?
Click to expand...
Click to collapse
Did you do the factory reset yet?
resetting as we speak. Report back in a sec
okay reset is done and IMEI is still 0000000000
CoBfan1987 said:
okay reset is done and IMEI is still 0000000000
Click to expand...
Click to collapse
Try doing the factory reset again and flashing back to froyo
http://forum.xda-developers.com/showthread.php?t=1106822
assuming the was what came with the phone?
I'm hitting the same very disgruntling problem that I did in the past when I tried to use CWM. When I try apply update from sdcard and I choose my update.zip file I just get E:signature verification failed and I can't proceed from there....
CoBfan1987 said:
I'm hitting the same very disgruntling problem that I did in the past when I tried to use CWM. When I try apply update from sdcard and I choose my update.zip file I just get E:signature verification failed and I can't proceed from there....
Click to expand...
Click to collapse
What color is your recovery?
blue
"Android system recovery <3e>
Samsung Recovery Utils
- for BML -"
CoBfan1987 said:
blue
"Android system recovery <3e>
Samsung Recovery Utils
- for BML -"
Click to expand...
Click to collapse
You need a custom kernal to flash from CWM. That is why you are getting that error. Let me look for an odin flash back to froyo stock for you.
On a side note - I have read taking your battery out for 10 mins has worked for some. Since your phone is working you may try that while we continue to look for a fix.
Sucks that this kind of problem would happen from following these instructions. I figure it would all automated and such...
http://support.t-mobile.com/docs/DOC-1810
and my battery is out now.
CoBfan1987 said:
Sucks that this kind of problem would happen from following these instructions. I figure it would all automated and such...
http://support.t-mobile.com/docs/DOC-1810
and my battery is out now.
Click to expand...
Click to collapse
I say before going back to froyo try raver's ROM-ODIN-2.3.6-Gingerbread Offical Maybe a stock reflash will work. I have read a thousand ways that have work for different people now. You have done a few. Try this as it is easier than going back to froyo for now. Let your battery charge first.
Maybe kies just f-ed up your imei. And where are the big dog's when you need them? bhundven/FBis251?
Did you just root? Or did you use an app to unlock your phone as well?
Guys, need some help here.
I´m noob, After try some custom Roms, scripts, kernels, etc, I lost my IMEI. Device is working fine, but can make emergency calls.
Try many things to recover it, i flash a froyo stock rom, GB stock, try diferent programs and read a lot here in XDA.
Cant find EFS folder, even using Root Browser.
I didn´t know that was need to back up the EFS folder. I only had CWR backups, and even this not works.
Maybe there something especific for Galaxy Fit?
Thanks for any help!
nisiomorais said:
Guys, need some help here.
I´m noob, After try some custom Roms, scripts, kernels, etc, I lost my IMEI. Device is working fine, but can make emergency calls.
Try many things to recover it, i flash a froyo stock rom, GB stock, try diferent programs and read a lot here in XDA.
Cant find EFS folder, even using Root Browser.
I didn´t know that was need to back up the EFS folder. I only had CWR backups, and even this not works.
Maybe there something especific for Galaxy Fit?
Thanks for any help!
Click to expand...
Click to collapse
Try install stock ROM with 4 files via ODIN, after CWM via ODIN and after custom ROM which you want.
Tried exactly this using a stock froyo rom, doesn´t work...
nisiomorais said:
Tried exactly this using a stock froyo rom, doesn´t work...
Click to expand...
Click to collapse
Are you tried Gingerbread with 4 files?
No, i tried Gingerbread (one package) and Froyo (4 files). Is there any diference?
nisiomorais said:
No, i tried Gingerbread (one package) and Froyo (4 files). Is there any diference?
Click to expand...
Click to collapse
I do not know. After this what I suggested, custom ROMs should work normally.
I will try again, where i can find GB in 4 files?
thanks!
nisiomorais said:
I will try again, where i can find GB in 4 files?
thanks!
Click to expand...
Click to collapse
Here: http://www.sammobile.com/firmware/
In Search write s5670, and download ROM for your location.
Ahhh this is something that even I was perplexed with...
A lot of people have reported this already, but we haven't made headway in this area...
In samsung phones, IMEI is either in efs or in csc, but none of us have had a closer look at this...
Hopefully, we'll be able to have ways to backup imei in the future...(no promises, though)
I hope too, for now I'm trying many ways to recover my IMEI, nothing works...
Updating: I use EFS Pro V2 http://forum.xda-developers.com/showthread.php?t=1308546 , and finaly have my IMEI back. I post it cause coud be helpful for others.
nisiomorais said:
Updating: I use EFS Pro V2 http://forum.xda-developers.com/showthread.php?t=1308546 , and finaly have my IMEI back. I post it cause coud be helpful for others.
Click to expand...
Click to collapse
Can you be a bit detailed?
Maybe list the steps.
This would help a lot of people.
Well, sorry for my bad english, will try to explain step-by-step: i instaled the app (EFS Professional) in my notebook, conect my device via USB, debuggin, ADB too.
Open the app on computer, select Qualcom.
Click on Qualcom NV Tools, a new box will apear.
Click Connect.
First i try Imei Repair box, insert manally the IMEI number and click Write IMEI,doesn´t work (and i don´t know if to digit IMEI number was neccessary, but just in case)
Close this box, go back to initial box and click NV Restore. The fone will reboot and it´s done. IMEI original number was restored.
I don´t know if maybe just clicking NV Restore as first step will do all the job, maybe. But I was "exploring" the options and thats works for me.
I hope it be helpfull
nisiomorais said:
Well, sorry for my bad english, will try to explain step-by-step: i instaled the app (EFS Professional) in my notebook, conect my device via USB, debuggin, ADB too.
Open the app on computer, select Qualcom.
Click on Qualcom NV Tools, a new box will apear.
Click Connect.
First i try Imei Repair box, insert manally the IMEI number and click Write IMEI,doesn´t work (and i don´t know if to digit IMEI number was neccessary, but just in case)
Close this box, go back to initial box and click NV Restore. The fone will reboot and it´s done. IMEI original number was restored.
I don´t know if maybe just clicking NV Restore as first step will do all the job, maybe. But I was "exploring" the options and thats works for me.
I hope it be helpfull
Click to expand...
Click to collapse
Have a couple of thanks, coz this was helpful.
I'll ask around if somebody has lost their imei and we'll try to cross check this, make it noob proof and then have it added to my guide to help the poor souls who might need this in the future
a.cid said:
Ahhh this is something that even I was perplexed with...
A lot of people have reported this already, but we haven't made headway in this area...
In samsung phones, IMEI is either in efs or in csc, but none of us have had a closer look at this...
Hopefully, we'll be able to have ways to backup imei in the future...(no promises, though)
Click to expand...
Click to collapse
We do not hav EFS partition in ROM's that are released now and i dont see that y..... But afaik for the OP's concern he could flash some old FW which has csc file in it which might help him regain his IMEI
[Q] WiFi/BT broken, stuck at "Starting Services" in ALL ROMs and Stock? Help please!
Hello! After a misadventure I managed to get CM 10.2 to run on my Photon Q, and it was fantastic! Wifi and BT work great. However, accidentally flashing the wrong kernel, I got stuck at the bootloader unlocked screen forever.
So, I reinstalled CM 10.2 and all seemed to be well. (I did this from CWM using a ZIP.) However, I quickly discovered WiFi and BT are both broken! If I hit ON, it goes gray for a second and tries to enable, and goes back to OFF with no error or other response. If I open the WiFi or BT menu and hit ON or SCAN, same result or it just does nothing.
So, I tried to downgrade to something older, something with ICS and not JB, which is what I prefer anyway. TwistedAsanti gets stuck forever at "Starting Services..." and the home screen never comes up, even if left overnight. I get a message that no cell networks were found asking if I want to switch to GSM. It's covered by STARTING SERVICES ... so I can't hit "No", but either way I don't have a carrier, so that's no issue. I use WiFi only. I can pull down the notification bar and go into settings. While there, I see the same problem with WiFi and BT, both are broken. I can't run any apps or get to the homescreen, still.
So, I tried to install 10.1, same result. Then MIUI, Carbon and SlimBean. Same result! I installed TWRP and flashed a backup of Stock JB from WIN files I found here on the forum. It boots up, but this time it's stuck at "Starting Services..." just like TwistedAsanti was. Notification bar works, settings menu works, homescreen won't appear, Starting services never goes away, can't run any apps. Wifi and BT still broken in the same manner.
Now downloading a backup of ICS Stock to see if that works any better, but I'm not holding my breath.
Has anyone ever experienced this? Thanks for any advice. I attached some photos that might help. I had to use my Tracfone because now that is the best camera I have access to, so sorry for the blurriness. I hope it gives you the general idea of what is going on.
EDIT: For each flash, I am wiping data, cache and dalvik cache. I also wiped modem and pds by mistake, could that be the problem? If so, how would I restore those? Thanks
Again, thanks for your time!
Jeez, how many threads do you need to post in? I have responded to all your posts in all of the various threads, INCLUDING your PM's.
Let's focus here, if you want custom we can do that. If you want stock we can do that. Please focus, what do you want.
If you want custom, perhaps you're not wiping everything properly... So boot recovery. Wipe system. Factory reset - wipe data, cache, dalvik-cache, sd-ext. Best to do the actual "factory reset" option than wiping all of those by hand, because wiping /data will wipe /data/media (internal SD) while factory reset will preserve /data/media.
Next, flash ROM of your choice. Twisted Asanti is kinda outdated, hasn't had any attention in a loooong time. Let's try something stable, CM10.1. Flash it. Flash gapps. Boot, do you still have the same issues?
Probably the wrong kernel is still flashed, you need to flash the stock kernel.
Wiping modem and pds could be the problem.
The first I would do in your position is to flash with RSD the stock ROM. This Thread -> http://forum.xda-developers.com/showthread.php?t=2095536
edit: If you post in several threads and try different things "in" different threads we won't be able to help you.
EVERYTHING in one thread and we may see what you have done and where you have had problems.
You should keep it simple and give all information in one good structured post so we don't have to read pages to see what you did.
Loader009 said:
Probably the wrong kernel is still flashed, you need to flash the stock kernel.
Wiping modem and pds could be the problem.
The first I would do in your position is to flash with RSD the stock ROM. This Thread -> http://forum.xda-developers.com/showthread.php?t=2095536
edit: If you post in several threads and try different things "in" different threads we won't be able to help you.
EVERYTHING in one thread and we may see what you have done and where you have had problems.
You should keep it simple and give all information in one good structured post so we don't have to read pages to see what you did.
Click to expand...
Click to collapse
Sorry about that. I'll keep it in one place. Thanks Still trying to get RSD to work, but it won't detect the phone for some reason. Well, on one PC it will, but then it fails to flash saying there was a Remote error (FAIL). On another PC, it won't detect. In BOTH cases, fastboot devices successfully shows the phone. I can even format partitions and flash files. I have successfully flashed TWRP this way.
trying to flash the system image doesn't work with the error "invalid sparse file format at header magi", then fastboot crashes. (What?) So, RSD doesn't work and fastboot kinda works, but not for all the images.
I got a copy of all the kernels I could find .. arrrghhh's for every FW I can think of. Searching out a stock kernel now. It says on the Peas and Q's post that it's just a stock FW with a new name, so I grabbed that too, might be worth a shot...
got CM 10.1, I guess I'll try installing that, and then what do I want, the STOCK kernel? or just use the one that it came with? (How confusing.)
To be more clear, either Stock or Custom is fine. I'm happy with either so long as it boots properly and WiFi works again. Root would be nice but I can worry about that later.
You don't have to quote whole posts (just press "QUICK REPLY").
The most important thing is to get RSD to work.
I'm not the guy where you get information about RSD and kind of. I know where to look for and show the right direction.
In the thread I posted you might get help for RSD and you could get help there.
Ask there for help as the more experienced users are reading only the "important" threads and not the "smaller" ones.
(I know this, I do this most time, but I'm not the "know-everything" guy )
As I never needed those FXZ method, I never used it and my RSD Lite experience is rather small.
You might need to install motorola drivers to get it to work but I'm not sure, you should ask in that thread.
PS: If Stock will work again, Custom will work too.
To avoid problems it might be needed to wipe data/cache/dalvik before and after flashing a ROM.
Loader009 said:
You don't have to quote whole posts (just press "QUICK REPLY").
The most important thing is to get RSD to work.
Click to expand...
Click to collapse
I got RSD to see the phone using a different PC. When I try to flash "asanti_c-user-4.0.4-7.7.1Q-6_SPR-89_ASA-36-42-release-keys-Sprint-US.xml" it gets all the way up to flashing "system", which is one of the last steps, then it says the device reported FAIL. This is the same file I couldn't get to flash with fastboot when I was trying to do it manually. But in that case, fastboot crashed entirely.
Not sure what to try now ...
Did you read the following?
Skrilax_CZ said:
NOTES
- use at least RSD Lite 6.1.5 (maybe 6.1.x will work too) or you get an error on flashing system.img.ext4
- you may have to open the zip and edit the xml, and delete the 2 lines "<step operation="getvar" var="max-download-size" />" if you get unknown command fastboot getvar max-download-size
- do not flash Sprint firmware to phone from Cellular US and vice versa unless you know what are you doing!!!
Click to expand...
Click to collapse
As I said, I never tried the FXZ method and I have no experience on error which could appear.
Ask in that FXZ thread and you may get it work soon.
Epicenter714 said:
I got RSD to see the phone using a different PC. When I try to flash "asanti_c-user-4.0.4-7.7.1Q-6_SPR-89_ASA-36-42-release-keys-Sprint-US.xml" it gets all the way up to flashing "system", which is one of the last steps, then it says the device reported FAIL. This is the same file I couldn't get to flash with fastboot when I was trying to do it manually. But in that case, fastboot crashed entirely.
Not sure what to try now ...
Click to expand...
Click to collapse
Try a different port? Different cable? Different computer? Are you using the stock cable?
Perhaps something else is broken... I'm not sure at this point. Do you have any screenshots of the failure? Any specific output from the software?
Did you edit the XML file properly? I think you did, but you said you were downgrading too - are you always trying ICS or have you tried the FXZ file for JB as well?
Useless thread bump.
Another fellow had the same issue, and was using an old version of RSD Lite. What version are you using?
I faced same problem.
Just use latest veersion of RSD lite, 6.0 is ok
and do not forget to remove two getvar commands from xml file.
I tried same and now my phone is alive. But now.IMEI/MEID is gone (zero)
WIFI and bluetooth is now connecting but not receiving any data (useless).
I tried many cdma tool to recover MEID but failed.
I thing we lost EFS partition.
Please look at my thread
http://forum.xda-developers.com/showthread.php?t=2429609
i also need help on that
If any one have EFS backup or something?
lovepreet39 said:
I faced same problem.
Just use latest veersion of RSD lite, 6.0 is ok
and do not forget to remove two getvar commands from xml file.
i also need help on that
If any one have EFS backup or something?
Click to expand...
Click to collapse
The problem WAS RSD's version! Thanks to everyone for your help. I had 5.6.4 running before and it would always die at System.img.ext4 and one other partition later on. That's on the WinXP system that would see the phone in RSD. The Win8 machine wouldn't see it at all, even in XP compatibility mode with admin rights. Go figure. I'll take this as another excuse to not be fond of Win8.
I checked and my phone has boot, system, recovery, data, pds and modem, but no EFS. I'm not familiar with that .. Isn't EFS a filesystem type, not a partition? Like EXTFS?
Epicenter714 said:
I checked and my phone has boot, system, recovery, data, pds and modem, but no EFS. I'm not familiar with that .. Isn't EFS a filesystem type, not a partition? Like EXTFS?
Click to expand...
Click to collapse
I don't understand, are you still having issues? Why are you asking about EFS?
arrrghhh said:
I don't understand, are you still having issues? Why are you asking about EFS?
Click to expand...
Click to collapse
I was replying to lovepreet39 about the EFS thing.
Epicenter714 said:
I was replying to lovepreet39 about the EFS thing.
Click to expand...
Click to collapse
EFS is a partition which contain your IMEI/MEID and Mac address information.
Please check in your settings is your IMEI/MEID there.
I gone from same problem and now IMEI/MEIS is zero.
---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------
@arrrghhh
Please look at my thread, i also need help
Epicenter714 said:
I was replying to lovepreet39 about the EFS thing.
Click to expand...
Click to collapse
Yes, but he is having an issue with EFS. You, on the other hand, are not... correct?
You post seems to indicate that despite getting RSD to work, you are still having issues. I want to make sure that is not the case...
lovepreet39 said:
EFS is a partition which contain your IMEI/MEID and Mac address information.
Please check in your settings is your IMEI/MEID there.
I gone from same problem and now IMEI/MEIS is zero.
---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------
@arrrghhh
Please look at my thread, i also need help
Click to expand...
Click to collapse
Hey buddy, I would love to help but that is way above my pay grade. I used my Q on Sprint, never liked mucking with that stuff personally.
@arrrghhh
Dear sir
Problem is that i wasted approx $250 on this device.
I am indian and $1 = Rs65 and $250 = Salary of one month.
I am here on XDA to save my $250.
There is no support on this phone in indian market,
If there any solution please help.
You can post here or PM me.
Or there is only by which i can only get my IMEI back, then i will apply GSM addon on it,
I do not care much about CDMA.
I know IMEI/MEID repair is illegal in USA.
For proof I can provide you original images of phone showing Zero Imei/meid
I do not want to change, only i want to restore original one.
Hi everyone & thanks for reading this!
I bought 2 new, unused Nexus 5 as presents for my sisters for Christmas (not via playstore, but via a reseller. Still: new, sealed, unused.)
I unlocked, installed a custom recovery, rooted both devices without problems, then set up one in a smartphone-newbie-friendly way, which took quite some time. Then, to save me some time, I fear I made quite a big mistake: I made a nandroid-backup of the newly-setup device and restored/installed it on the second nexus (so I wouldn't have to change all the settings again, install apps, etc).
Unfortunately, this seems to have erased the IMEI on the second device (it shows as IMEI=0), so I can't connect to any cell service. Some googling leads me to believe that this might be due to a corrupt/missing EFS-folder, which, second mistake, I did NOT make a backup of beforehand. I know, it's my own fault - my thinking was: why backup, there's nothing backupworthy on the device *yet*.
FML. :crying:
I am not sure if the phone is still in warranty (and even if it was - I guess I voided that by unlocking/rooting?!). I want to re-iterate that I own both devices LEGALLY, I have the bill, I have the original sticker with the original IMEI - I just need a way to re-enter it. Any dialer-code for that? Any modify-able EFS-backups? Any other way?
Thanks in advance!
PS: tried so far & found useless: other simcard (not working) & simcard in other phone (working), so it's a device-issue; factory-reset;
Try fastboot flashing the cache.img from the factory image.
jd1639 said:
Try fastboot flashing the cache.img from the factory image.
Click to expand...
Click to collapse
thanks for the super-quick reply jd1639!
to make sure I understand you correctly:
I can use the factory image from
https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz
(nexus 5, android 4.4.2), extract the cache.img from there & flash that via fastboot? (or would it have to be a factory image of this very device - which I do not have, unfortunately)
and, just for my understanding: how does that restore the imei? I mean, the factory image itself (or it's cache) can't really contain MY imei. does this just delete the invalid imei & force the phone to get it's original imei from some other, not yet overwritten source? e.g. hardware?
Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk
Thank you for clarifying, rootSU - that gives me hope.
I will try tomorrow & hopefully report success
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...
RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato
charesa39 said:
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...
Click to expand...
Click to collapse
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).
CellPhish said:
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato
Click to expand...
Click to collapse
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
If all fails you can try to contact LG service and tell them your situation. Though its not good to lie, just tell them you got the IMEI=0 problem, they'll say its a hardware problem and will replace the motherboard(if your device is on warranty)
Sent from a potato
You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.
rootSU said:
Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The IMEI is stored in the EFS partition, not the cache partition.
RogerG said:
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).
Click to expand...
Click to collapse
Sounds like you turned the phone into a $400 paperweight. TWRP backs up and restores the EFS partition by default, and each device has a unique EFS partition, which contains the IMEI among other things. I don't know of a way of manually restoring the EFS data. This is unfortunately a $400 lesson for people who tinker without first doing their homework.
Hey guy. Let's not be so judgemental. There's always a risk of the imei being corrupted when you flash a ROM. As a matter of fact just before I even unlocked my nexus the imei got corrupted and I had to factory flash my phone to save it. Its scary but op, if you manage to get your phone working again make a backup and store it on your PC and or email yourself the backup.
BirchBarlow said:
The IMEI is stored in the EFS partition, not the cache partition.
Click to expand...
Click to collapse
Ha ha thanks! Can't believe you think I don't know that :/
Actually the "EFS partition" is 2 partitions..
/dev/block/platform/msm_sdcc.1/by-name/modemst1
And...
/dev/block/platform/msm_sdcc.1/by-name/modemst2
That doesn't change the fact that reflashing the cache.img is a known fix for missing IMEI. Corrupt cache can make the imei appear as 0 even when the EFS imei is in tact so reflashing the cache.img can resolve this.
Unfortunately though, I didn't read the OP fully. I just elaborated on an earlier response for the OP
jd1639 said:
You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.
Click to expand...
Click to collapse
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk
rootSU said:
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes but all talks about how to change it in any way are not allowed here. Legally the only people that are allowed to do so is the OEM. You can look at international news reports of cellular dealers that are doing so are being closed down and arrested.
That is why it is well know to back up the efs before you do anything.
Bat cave One
My newly bought Nexus 5 shows IMEI 0 also
RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
i just update my newly bought nexus 5 from initial 4.4.2 to 4.4.4 which is appear at update section but then my IMEI appear =0 .. dont understand what to do..
if your problem solved, pls tell me the detail procedure to recover my IMEI no.
RogerG, did you ever get this working? I'm on 6.0 and having the same problem, flashing cache.img also does nothing.
Thanks.
First things first, I'm sorry for opening another thread on this but I feel the other ones weren't headed exactly in the correct direction.
A little background:
I was trying to downgrade my XT1541 to Lollipop since 6.0 was really bad and I got frustrated and used
Code:
fastboot erase all
The result was I erased my IMEI and I haven't been able to connect to a network carrier since. The problem can be solved by re-writing my IMEI but that's the difficult part.
What I gathered so far is I can use QPST, backup QCN, go into HEX and change IMEI there, then restore the QCN back to my device. The problem is I can't locate the IMEI in my QCN since my IMEI is now simply 0.
So in all, could someone make a backup of THEIR QCN and send it to me? I would flash it to my XT1541, locate the IMEI (since now I would know what I'm looking for), then change it back to my own.
Does that sound like something that could work? Can anyone help?
UPDATE1: Noone sent me their QCN however I did try to restore the one I backup up (which still has an IMEI=0). QPST Software Download reports
Received an invalid command from the phone.
Click to expand...
Click to collapse
I tried using Qualcomm NV Tools (from EFS Professional), which reads all the information correctly, however when attempting to write the following appears
Cannot Write: NV_UE_IMEI_I
Error: NV_ERR_BAD_SECURITY_STATE
Click to expand...
Click to collapse
So getting another QCN won't help as it seems that I can't write the IMEI (qcn) back to the device...
There are only two possibilities of fixing this... a 50/50 chance that a full factory flash will restore it (don't know how, but it does sometimes). If that doesn't work, then you need to send it to Moto for repair.
acejavelin said:
There are only two possibilities of fixing this... a 50/50 chance that a full factory flash will restore it (don't know how, but it does sometimes). If that doesn't work, then you need to send it to Moto for repair.
Click to expand...
Click to collapse
I have already tried with a full stock rom flash which didnt work...
zeusalmighty said:
I have already tried with a full stock rom flash which didnt work...
Click to expand...
Click to collapse
Well, unfortunately that leaves option 2... or turn it into a media play and buy a new phone.
Funny how `fastboot erase all` causes such a pain for some and not others... but once your IMEI is gone, there isn't much you can do. Moto kinda screwed the pooch on that one.
Hello, did u try Xposed IMEI changer? Maybe that will be a native fix for this issue.
Try this >http://forum.xda-developers.com/moto-g/help/info-moto-g-imei0-t2925970/post61725547#post61725547
Henriquefeira said:
Try this >http://forum.xda-developers.com/moto-g/help/info-moto-g-imei0-t2925970/post61725547#post61725547
Click to expand...
Click to collapse
Thanks but the dd commands wont work since it appears the folder structure is different on the XT1541...any help?
Forever Alone said:
Hello, did u try Xposed IMEI changer? Maybe that will be a native fix for this issue.
Click to expand...
Click to collapse
Hey, couldn't get any results with the xposed module
Just one bump
One last effort, not a bump. If anyone can direct me to commercial services for repairing the IMEI i'd be very greatful. Official Motorola Service wont repair it for me btw.
Thanks
try this guys
http://forum.xda-developers.com/2015-moto-g/help/tuto-fastboot-erase-signal-t3451362#post68445534