Hello,
After installing bigxies ota jelly bean, I love it everything runs fine, I got a new nexus today and installed everything on that aswell, I was having some screen issues and had to call samsung and i went to give them my IMEI from my phone and it was not a valid IMEI, totally different from the one on the box, which was the correct one, I didn't bother looking when I was stock, but can anyone else attest to this? that something goes wonky with what google displays as the IMEI number in these pre jellybean roms we have?
FYI the IMEI should start with a 35
My IMEI never changed.
Sent from my Galaxy Nexus using xda premium
Just checked mine, same IMEI on the settings screen and on the back of the phone.
Dice62 said:
My IMEI never changed.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hmmm.. very weird, backing up and than going to load stock everything. She also noted that it read my purchase date was not the day i purchased and in face it was last month, something seems fishy.
I just used Nexus toolkit to go back to factory stock rom, it now has the correct IMEI number.. It just dawned on me what could have been the problem. This was a nandroid from my original galaxy nexus, so by restoring it to my new galaxy nexus, maybe that messed some things up? Either way, looks like i will be starting from scratch and not be restoring from that nandroid.
penskyc said:
Hello,
After installing bigxies ota jelly bean, I love it everything runs fine, I got a new nexus today and installed everything on that aswell, I was having some screen issues and had to call samsung and i went to give them my IMEI from my phone and it was not a valid IMEI, totally different from the one on the box, which was the correct one, I didn't bother looking when I was stock, but can anyone else attest to this? that something goes wonky with what google displays as the IMEI number in these pre jellybean roms we have?
FYI the IMEI should start with a 35
Click to expand...
Click to collapse
Sounds like the issue with the Docomo phones..
JaiaV said:
Sounds like the issue with the Docomo phones..
Click to expand...
Click to collapse
and what issue would that be?
penskyc said:
and what issue would that be?
Click to expand...
Click to collapse
Using the special unlock method for Docomo phones, quite often users would get invalid IMEIs.
http://forum.xda-developers.com/showthread.php?t=1570342
http://forum.xda-developers.com/showthread.php?t=1593209
http://forum.xda-developers.com/showthread.php?t=1606982
JaiaV said:
Using the special unlock method for Docomo phones, quite often users would get invalid IMEIs.
http://forum.xda-developers.com/showthread.php?t=1570342
http://forum.xda-developers.com/showthread.php?t=1593209
http://forum.xda-developers.com/showthread.php?t=1606982
Click to expand...
Click to collapse
thanks much, going to try this:
If you have generic IMEI 0049... simply execute the following actions:
1. switch GN to airplane mode
2. del 2 files nv_data.bin + nv_data.bin.md5 from /data/radio/
3. copy 1 file nv_data.bin from /factory/ to /data/radio/
4. change permission & owner execute 2 commands:
Code:
chmod 700 /factory/nv_data.bin
chown radio.radio /factory/nv_data.bin
chmod 700 /data/radio/nv_data.bin
chown radio.radio /data/radio/nv_data.bin
5. reboot phone & switch off airplane mode.
6. check imei by pressing *#06# in dialpad.
Thats all.
same imei for me.
deleted
I just had a moment of panic... read the OP's post, immediately grabbed my phone and the Nexus box on the floor next to my PC and compared IMEI's.
When I saw that they were different, I started to panic.
... when I realized that the box that I had picked up was actually from my long ago broken Nexus S, I had myself a good laugh.
No IMEI issues here.
Whoever unlocked your phone... did it wrong.
They didn't fix up the copy in the efs partition properly (ie. they didn't update the md5), thus when you deleted the one in /factory (likely when you factory reset in CWM), it fell back to the efs which was invalid.
Namidairo said:
Whoever unlocked your phone... did it wrong.
They didn't fix up the copy in the efs partition properly (ie. they didn't update the md5), thus when you deleted the one in /factory (likely when you factory reset in CWM), it fell back to the efs which was invalid.
Click to expand...
Click to collapse
Well I bought my phone unlocked already fromm google, does that mean google unlocked it wrong? lol.. Im sure I did something along the process, like I said using a nandroid from a different nexus to restore on this nexus maybe? anywho, I did the fix I mentioned some posts back and it works fine. Also worked fine when I did a fresh install of JB as opposed to restoring this particular nandroid. my IMEI was good from the start only with this particular one was it wrong.
G'day - I have a similar IMEI problem.
I have a gnex from Vodafone Australia. I have rung them 6x on separate occasions to enquire about my IMEI unlock code, so I can use the phone with another carrier. The IMEI unlock code does not work (it says it is invalid).
What am I supposed to do now?
-Vodafone suggested I post Ph back to them and it could take several weeks. (ridiculous!)
I am using 4.2.2, rooted, with latest Franco kernel.
Ps - I have gone between ice cream sandwich and jelly bean a few times using a combo of OTAs, WUGs nexus toolkit, and ODIN. (I don't know if that has something to do with it).
Also I have read about a possible fix called **** DoCoMo v3, but I am not confident using it as it's thread is full of people who have ended up with phones that do not connect to any network. The instructions aren't very clear, however, and I'm not sure if I should try it (and if so whether it will work with rooted 4.2.2, or whether I should revert to 4.0.4?)
Cheers
same IMEI no.
same problem imei
For some reason i updated to jellybean and now have generic imei i notice when my kid told me she did not have a signal i guess tmobile block generic imei so i found the instruction on how to change it but now when i try to modify it says i dont have permision to change that file. I verify if im root and yes. can someone help
---------- Post added at 10:02 PM ---------- Previous post was at 09:47 PM ----------
[email protected]:/ $ su
[email protected]:/ # chown radio.radio /factory/nv_data.bin
Unable to chown /factory/nv_data.bin: Read-only file system
10|[email protected]:/ #
This is what i get also with the chmod command
ac17 said:
G'day - I have a similar IMEI problem.
I have a gnex from Vodafone Australia. I have rung them 6x on separate occasions to enquire about my IMEI unlock code, so I can use the phone with another carrier. The IMEI unlock code does not work (it says it is invalid).
What am I supposed to do now?
-Vodafone suggested I post Ph back to them and it could take several weeks. (ridiculous!)
I am using 4.2.2, rooted, with latest Franco kernel.
Click to expand...
Click to collapse
ac17 said:
Ps - I have gone between ice cream sandwich and jelly bean a few times using a combo of OTAs, WUGs nexus toolkit, and ODIN. (I don't know if that has something to do with it).
Also I have read about a possible fix called **** DoCoMo v3, but I am not confident using it as it's thread is full of people who have ended up with phones that do not connect to any network. The instructions aren't very clear, however, and I'm not sure if I should try it (and if so whether it will work with rooted 4.2.2, or whether I should revert to 4.0.4?)
Cheers
Click to expand...
Click to collapse
Man, either try the DoCoMo v3 or don't try it, no one can take that risk for you. Either way, create your own thread or post in the DoCoMo thread, don't necrobump threads (this one is almost a year old), especially since they are not the same issue. Other people here lost their IMEI, you want to sim unlock.
gsnex said:
same IMEI no.
Click to expand...
Click to collapse
There's at least one thread that's about these kind of issues and with a lot more to go on.
jordanrules said:
For some reason i updated to jellybean and now have generic imei i notice when my kid told me she did not have a signal i guess tmobile block generic imei so i found the instruction on how to change it but now when i try to modify it says i dont have permision to change that file. I verify if im root and yes. can someone help
---------- Post added at 10:02 PM ---------- Previous post was at 09:47 PM ----------
[email protected]:/ $ su
[email protected]:/ # chown radio.radio /factory/nv_data.bin
Unable to chown /factory/nv_data.bin: Read-only file system
10|[email protected]:/ #
This is what i get also with the chmod command
Click to expand...
Click to collapse
Boot a custom recovery and remount /factory rw. Should work then, as well as it will be safer than doing it from Android (airplane more and all). Create a new thread please if you still need to.
Reported this thread for closing.
a manta wrote this.
Problem solved safely in under 30 secs with an inexpensive app on the Play store called GalaxySimUnlock.
Has unlocked the IMEI, without changing it, and has survived multiple custom roms, and Sims from a variety of carrier's.
I suggest anyone curious about it, read other Play store comments for your phone make. The dev is responsive too if you have questions.
Def worth the buck he charges!
Related
Sir, i flashed my nexus with AOSP rom(4.0.3),everything works well for several hours.but yesterday my phone shows error no service,i tries several sim card but facing same issue.so i tried imei no and guess what it shows nothing.... i checked baseband shows unknown. so i flashed stock rom via cwm (restore),but unfortunately facing same problem. so i flashed few baseband images also but not workrd either. plz help me how should i get my imei number back..... i have no backup file of my EFS folder.
First off, don't call me sir
I've been seeing alot of the same issue and no one seems to have a solid lead on the real problem.
And yes, it has happened to me.
My opinion is that flashing *some* roms is causing the bootloader to become corrupted...as this is exactly the issue I had experienced.
A fubar'd bootloader will screw everything up.
The solution for me was to odin back to stock.
Since you did not state if your gnex is gsm or cdma I am not going to attempt to post directions or even file names for you (you can easily search for odin and get them here in this forum). The directions are completely different depending on the gsm/cdma thing.
Be careful and make sure you have the right version of odin and the correct files to flash. It's actually pretty simple, but it's always the simple things that are easiest to get wrong.
g'luck
mangesh hotkar said:
Sir, i flashed my nexus with AOSP rom(4.0.3),everything works well for several hours.but yesterday my phone shows error no service,i tries several sim card but facing same issue.so i tried imei no and guess what it shows nothing.... i checked baseband shows unknown. so i flashed stock rom via cwm (restore),but unfortunately facing same problem. so i flashed few baseband images also but not workrd either. plz help me how should i get my imei number back..... i have no backup file of my EFS folder.
Click to expand...
Click to collapse
For me the solution was to just flash a suitable radio
Sent from my Galaxy Nexus using Tapatalk 2
There is no 4.0.3 for the nexus the last time i remember..
Mach3.2 said:
There is no 4.0.3 for the nexus the last time i remember..
Click to expand...
Click to collapse
? ... 4.0.3 has been out for GN.
zephiK said:
? ... 4.0.3 has been out for GN.
Click to expand...
Click to collapse
There's no 4.0.3 images for the gnex, at least official ones.
http://www.randomphantasmagoria.com/firmware/galaxy-nexus/i9250/
I had this issue as well. I couldn't get the gnex (GSM) to show up in Odin to even start flashing anything so the only thing I could do was send it in to Samsung.
Sent from my Sensation using Tapatalk 2
sorry my mistake its 4.0.4, i have GSM phone.is ODIN solve my problem to get back my baseband.....
buenso80 said:
For me the solution was to just flash a suitable radio
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i tried ur way but its not working and i have the same problem
haziqshaikh97 said:
i tried ur way but its not working and i have the same problem
Click to expand...
Click to collapse
Any update? have anyone make a warranty reclamation? my phone with cyanogen 9 have the same problem, factory image restoration and radio install don´t work for me.
radiazo said:
Any update? have anyone make a warranty reclamation? my phone with cyanogen 9 have the same problem, factory image restoration and radio install don´t work for me.
Click to expand...
Click to collapse
What methods have you tried to return the device back to stock? You can try fastbooting back to stock which is fairly simple you would just need some knowledge of ADB and must have the Android SDK installed to do so. You can also use ODIN to do this or Heimdall depending on whether you are using Windows, Mac, or Linux. Feel free to PM if you would like some help with this!
PaullieVicious said:
What methods have you tried to return the device back to stock? You can try fastbooting back to stock which is fairly simple you would just need some knowledge of ADB and must have the Android SDK installed to do so. You can also use ODIN to do this or Heimdall depending on whether you are using Windows, Mac, or Linux. Feel free to PM if you would like some help with this!
Click to expand...
Click to collapse
Hi, I went back to stock by odin but had no success! no gsm signal... baseband unknown :crying::crying::crying:
[email protected]:/data/radio/log # cat nv.log
cat nv.log
Sat Jul 28 12:29:43 2012: /data/radio/nv_data.bin does not exist.
Sat Jul 28 12:29:43 2012: /data/radio/nv_data.bin does not exist.
[email protected]:/data/radio/log # cd /data/radio
cd /data/radio
[email protected]:/data/radio # ls
ls
log
nv_data.bin
nv_data.bin.md5
[email protected]:/data/radio #
is problem hardware pba (modem)
http://forum.xda-developers.com/showthread.php?t=1626593&page=5
any updates? I'm having the same problem, only had my GNEX for a week.
Try copying these files from /factory to /data/radio:
nv_data.bin
nv_data.bin.md5
And set the permissions to 700.
efrant said:
Try copying these files from /factory to /data/radio:
nv_data.bin
nv_data.bin.md5
And set the permissions to 700.
Click to expand...
Click to collapse
Then reboot of course.
Sent from my Galaxy Nexus using Tapatalk 2
PaullieVicious said:
What methods have you tried to return the device back to stock? You can try fastbooting back to stock which is fairly simple you would just need some knowledge of ADB and must have the Android SDK installed to do so. You can also use ODIN to do this or Heimdall depending on whether you are using Windows, Mac, or Linux. Feel free to PM if you would like some help with this!
Click to expand...
Click to collapse
I use fastboot, and don´t have luck. EFS partition contents exist, but i don´t have imei or baseband detected. I install google jellybean
Same happened to my GNex after flashing miui 2.11.16.
Common sense suggests that the rom, which doesn't include a radio, shouldn't be the reason for the unknown imei and unknown baseband fault.
This has also happened to others of whom most, including me, indicated flashing the updated recovery either twrp 2.3.2.1 or cwm 6.0.1.5/6 which were rolled out for android 4.2 compatibility.
I went back to stock 4.1.2 everything... GNex Tool and ODIN methods, but the problem remained: still UNKNOWN IMEI and UNKNOWN Baseband.
Common symptom to this fault is the phone/os thinks that Flight Mode is ON. Closer inspection in hidden menu phone information (*#*#4636#*#*) clearly shows the radio alternating On/Off continuously... all suggested tricks to set band to gsm manual or auto failed.
I have also tried the OMAP_Flash tool recently leaked from smsng team... it works as described (fix boot partition) but it wouldn't fix this problem.
Those suggesting it's a hardware fault are simply "just saying" but there's no actual prove or method to such a conclusion.
I'm leaning more to believe the cause to be a bug in the updated custom recoveries for android 4.2.
Hope this helps anyone trying to find a fix.... if you find a fix, please PM me
... and for now, i'm using my good old galaxy s i9000 <= will give it to anyone successfully helps us to fix the GNex
Do you have signal? are you in the same rituation described in this post? http://forum.xda-developers.com/showthread.php?t=1797931
I'm in the same situation, only flashing 4.0.4 firmware Imei and baseband are shown, but no signal...
I really don't know if it's just a solvable software problem or it's an hardware one!
Thanks for any news!!!!
xanadux said:
Do you have signal? are you in the same rituation described in this post? http://forum.xda-developers.com/showthread.php?t=1797931
I'm in the same situation, only flashing 4.0.4 firmware Imei and baseband are shown, but no signal...
I really don't know if it's just a solvable software problem or it's an hardware one!
Thanks for any news!!!!
Click to expand...
Click to collapse
similar problem, but unlike dhuberto, not able to get imei back with any version of a stock image using any method.
My radio keeps going FLIGHT MODE on then off then on continuously... I have tried several apps to force gsm off (turn off radio) to no avail.
I personally still think it is not a hardware issue. Maybe it's me just hoping!
I have reasons to slightly believe that it was caused by a bad custom recovery code while doing fix permissions.
I am still researching and I will update once there's some news, good or bad.
Hello,
I've noticed that my volume buttons have pretty much stopped working. I don't think it's ROM related, I'm on tmcode's AOKP rc2 ROM and tried going back to CM10 stable and the problem was still there.
Sometimes they'll work randomly, but they're pretty much a write off it seems. My phone is under a year old purchased from Bell.
I've unlocked, rooted the phone, flashed CWM and have flashed numerous ROMS.
I'd like to try and see if they'll give me a replacement, or fix it or whatever before I get a new phone, which most certainly won't be an LG phone, too bad about the Nexus 4...
What's the easiest way to bring the phone back to a stock state? Do you think if I just flash Bell's ICS ROM it'll be enough?
Thanks
you haven't given us much info... my p930 works fine (edit spelling) on cm10 stable... if yours still aren't working i'm guessing one of two things.
1. maybe your rom flashing procedure is lacking... ? are you doing proper data wipes before flashing new roms?
2. did you jolt your phone? if you smashed your phone from the side the volume buttons are on its easily the contacts could have been damaged.
either way i think if your flash count is that high your warranty is probably useless, unless there is some way to hide all those custom roms you flashed but there isn't as far as i know.
you can only hope your problem can be fixed by doing a proper wipe... just another thought... have you tried restoring a backup from CWM from before you experienced the problem? this should confirm weather it is a hardware or software issue.
KronicSkillz said:
you haven't given us much info... my p930 works fine (edit spelling) on cm10 stable... if yours still aren't working i'm guessing one of two things.
1. maybe your rom flashing procedure is lacking... ? are you doing proper data wipes before flashing new roms?
2. did you jolt your phone? if you smashed your phone from the side the volume buttons are on its easily the contacts could have been damaged.
either way i think if your flash count is that high your warranty is probably useless, unless there is some way to hide all those custom roms you flashed but there isn't as far as i know.
you can only hope your problem can be fixed by doing a proper wipe... just another thought... have you tried restoring a backup from CWM from before you experienced the problem? this should confirm weather it is a hardware or software issue.
Click to expand...
Click to collapse
What do you mean "flash count is that high?" I mean, if they really care about that, just update through the LG updater tool and they would never know you've been flashing all sorts of custom ROMs.. Which, if you think it MIGHT be a software problem, that might not hurt anyway; but I doubt it's software related..
lordcheeto03 said:
What do you mean "flash count is that high?" I mean, if they really care about that, just update through the LG updater tool and they would never know you've been flashing all sorts of custom ROMs.. Which, if you think it MIGHT be a software problem, that might not hurt anyway; but I doubt it's software related..
Click to expand...
Click to collapse
someone told me there was something can counts rom installs or something, they called it a flash count i'm trying to find the thread i read it on... it might be completely wrong
KronicSkillz said:
someone told me there was something can counts rom installs or something, they called it a flash count i'm trying to find the thread i read it on... it might be completely wrong
Click to expand...
Click to collapse
I see what you're talking about now. From what I can tell, it's on Samsung devices; I can't find any other references to it on any other brand... not saying that it isn't on anything else, but Samsung appears to not like people having full control of their device.
I don't think it's a software issue, I'm pretty sure it's hardware.
I know to do a full wipe when flashing between different ROMs.
My phones been dropped a couple times, nothing drastic though, that could have done it maybe. I've got a TPU (sp?) case on the phone.
What is the easiest way to bring the phone back to a stock state? LG GB/ICS ROM, un-rooted?
Thanks again
Sent from my LG-P930 using xda app-developers app
RealyPssd said:
I don't think it's a software issue, I'm pretty sure it's hardware.
I know to do a full wipe when flashing between different ROMs.
My phones been dropped a couple times, nothing drastic though, that could have done it maybe. I've got a TPU (sp?) case on the phone.
What is the easiest way to bring the phone back to a stock state? LG GB/ICS ROM, un-rooted?
Thanks again
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
You can try running the official LG update tool; I'm not sure if that will work without doing anything else... I KNOW it works if you flash v18f and then update with the official software. Basically, run through steps 1-5 of this guide: http://forum.xda-developers.com/showthread.php?t=2044645 and instead of doing anything after all that, just start the official update software and update to Official ICS.
" just start the official update software and update to Official ICS."
I'm using the Bell phone unlocked on Rogers, will I still be able to update to the official ICS ROM?
RealyPssd said:
" just start the official update software and update to Official ICS."
From within the phone it self? Or is it an application I download and run from my PC?
I'm using the Bell phone unlocked on Rogers, will I still be able to update to the official ICS ROM?
Click to expand...
Click to collapse
http://www.lg.com/us/support-mobile/lg-P930#manuals
B2CAppsetup.exe is the app you'll need.
pretty sure by official lg update software he's talking about the tool you run on your pc that autoupdates your phone.
http://www.lg.com/ca_en/support/mobile-support
is where you would find the tool, i'm not 100% positive on this more like 99% if you want confirmation you should wait for him to verify, but i know this is the official lg update tool.
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
if you blocked the lg site from your hosts file like the (*edit* un) bricking guide tells you to, you'll have to remove that line from your hosts file (127.0.0.1 csmg.lgmobile.com) and flushdns in order to communicate with the lg servers again. just in case you run into this, i'll try to have your answer posted before you can ask the question
to flush dns open the run prompt, type cmd, hit enter, type ipconfig /flushdns
you should get a success message this has refreshed your dns and you should be able to communicate with csmg.lgmobile.com again.
---------- Post added at 06:42 PM ---------- Previous post was at 06:37 PM ----------
as per your 2nd question, i'm pretty sure you'll end up with A T&T but im not positive. however the at&t software will work if you enter your carriers APN settings, if you didn't write them down you can get them with a simple google search, go into mobile network settings on your phone select apn, then push the menu button and push new, then enter all your apn settings and your data should connect in a jiffy.
KronicSkillz said:
pretty sure by official lg update software he's talking about the tool you run on your pc that autoupdates your phone.
http://www.lg.com/ca_en/support/mobile-support
is where you would find the tool, i'm not 100% positive on this more like 99% if you want confirmation you should wait for him to verify, but i know this is the official lg update tool.
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
if you blocked the lg site from your hosts file like the (*edit* un) bricking guide tells you to, you'll have to remove that line from your hosts file (127.0.0.1 csmg.lgmobile.com) and flushdns in order to communicate with the lg servers again. just in case you run into this, i'll try to have your answer posted before you can ask the question
to flush dns open the run prompt, type cmd, hit enter, type ipconfig /flushdns
you should get a success message this has refreshed your dns and you should be able to communicate with csmg.lgmobile.com again.
---------- Post added at 06:42 PM ---------- Previous post was at 06:37 PM ----------
as per your 2nd question, i'm pretty sure you'll end up with A T&T but im not positive. however the at&t software will work if you enter your carriers APN settings, if you didn't write them down you can get them with a simple google search, go into mobile network settings on your phone select apn, then push the menu button and push new, then enter all your apn settings and your data should connect in a jiffy.
Click to expand...
Click to collapse
Yeah, the official update tool. That's the one I'm talking about; both links end up going to the same program - B2CAppSetup.exe
Good point on the hosts file, that's pretty important.
thank you just trying to him this guy get his phone going
Alright, once I find a cheapo phone to use while my Nitro HD / Optimus LTE is being repaired, I'll give this a go.
I just want to bring it back to stock state to remove root so they won't deny my warranty.
I remembered after I posted about the "B2CAppSetup.exe " program on LG's site.
My hosts file is untoched, I'm on a new install of Windows 8, I un-bricked a few months ago.
Thanks again for all the help.
I can't really, reliably, enter recovery any more...
I might try flashing the v20f Bell ROM via ROM manager and then try unrooting with super one click.
I do still have the first CWM backup I made of the stock GB ROM as well that I could restore maybe in ROM manager.
Sent from my LG-P930 using xda app-developers app
So I flashed the original GB CWM / Nandroid backup I had made, then I tried un-rooting with SuperOneClick, but for some reason it wouldn't work.
So I used the LG software and updated to the official ICS release, Bell version, and the now the phone is un-rooted.
Time to send it off to hopefully get fixed.. what are the chances that I'll get my actual handset back? I've unlocked it, I'm betting I don't get mine back, but a locked one...
Thanks again for all the help
first of all you dont want yours back, the volume button issue is probably hardware, unless you flashed the wrong rom or a corrupted wrong or something. secondly if you updated to stock ics, your phone is already has a relocked bootloader, you should be so lucky as to get a brand new phone that you can unbrick in an hour...
*edit* unless there is some new security they are putting on the new ones but i haven't heard of such, it has always seemed to me they only implement security to the point where it will stop an unknowledgeable person from breaking the phone. the amount of software "leaks" suggest to me they don't really care if people that know what they are doing mod the phones. having said that they still won't replace a phone they know has been modded, for valid reasons, they shouldn't be responsible for things they didn't do to the phone.
So I got my handset back and the volume buttons have been fixed.
To get root and CWM recovery back is it easiest to just follow an unbrick guide?
Phone: Samsung Galaxy Nexus GT-i9250TSGGen
I had a stock android version, that I never rooted or flashed. Suddenly the SIM stopped working, I figured out that there is no IMEI number and the baseband is unknown.
I flashed to a custom ROM, and tried to do few things using the Galaxy Nexus Toolkit:
1) custom ROM android 4.1
2) Flashed a custom radio
3) made a copy of the /efs folder, deleted the original and replaced it after restart.
The Samsung service center said the entire board has to be changed, with an estimated cost of $140 USD.
Can someone help me with my options? Is it definitely a hardware problem? is there anyway to know for sure?
samdev09 said:
Phone: Samsung Galaxy Nexus GT-i9250TSGGen
I had a stock android version, that I never rooted or flashed. Suddenly the SIM stopped working, I figured out that there is no IMEI number and the baseband is unknown.
I flashed to a custom ROM, and tried to do few things using the Galaxy Nexus Toolkit:
1) custom ROM android 4.1
2) Flashed a custom radio
3) made a copy of the /efs folder, deleted the original and replaced it after restart.
The Samsung service center said the entire board has to be changed, with an estimated cost of $140 USD.
Can someone help me with my options? Is it definitely a hardware problem? is there anyway to know for sure?
Click to expand...
Click to collapse
If you have a nandroid back up, try and restore with it. This could solve ur problem.
saishyamk said:
If you have a nandroid back up, try and restore with it. This could solve ur problem.
Click to expand...
Click to collapse
Thanks, but I hadn't created a back up before. Is there a way to use a back up from a different phone? where would l find more information?
samdev09 said:
Thanks, but I hadn't created a back up before. Is there a way to use a back up from a different phone? where would l find more information?
Click to expand...
Click to collapse
I had an old nandroid back up and I used the method in this post to fix my IMEI problem: forum.xda-developers.com/showpost.php?p=47048361&postcount=9
And when you said you took a back up of the /EFS folder, you meant pulled the .bin and .md5 files from the /factory or the /radio folders OR did you use something like kTool? Because, as people have pointed out in other threads there is no /EFS folder for the Galaxy Nexus. The IMEI information is stored in the Radio and Factory Folders. For more information on how IMEI works on the GNEx, refer to this post: http://forum.xda-developers.com/showpost.php?p=47045295&postcount=6
But you are saying the baseband is also unknown. A radio flash should have fixed it. Try restoring Stock ICS using Odin. i hear this fixes some problems like this. U can use thus guide forum.xda-developers.com/showthread.php?t=2065470
If Odin is a little complicated, try the Nexus Root Tool kit. U gotta experiment to find the right problem and them fix it. No other go. I doubt that replacing the board will solve it as it looks like a software issue, unless you fried your radios.
saishyamk said:
I had an old nandroid back up and I used the method in this post to fix my IMEI problem: forum.xda-developers.com/showpost.php?p=47048361&postcount=9
And when you said you took a back up of the /EFS folder, you meant pulled the .bin and .md5 files from the /factory or the /radio folders OR did you use something like kTool? Because, as people have pointed out in other threads there is no /EFS folder for the Galaxy Nexus. The IMEI information is stored in the Radio and Factory Folders. For more information on how IMEI works on the GNEx, refer to this post: http://forum.xda-developers.com/showpost.php?p=47045295&postcount=6
But you are saying the baseband is also unknown. A radio flash should have fixed it. Try restoring Stock ICS using Odin. i hear this fixes some problems like this. U can use thus guide forum.xda-developers.com/showthread.php?t=2065470
If Odin is a little complicated, try the Nexus Root Tool kit. U gotta experiment to find the right problem and them fix it. No other go. I doubt that replacing the board will solve it as it looks like a software issue, unless you fried your radios.
Click to expand...
Click to collapse
Thanks again. Yes, the /efs folder is not where it was supposed to be. I did find the correct location and moved it. I will try using your ideas. Just one more question:
Since I had not done anything that would wipe out my IMEI number (neither software hacking nor physical damage). I wonder why this problem suddenly occurred. Just to eliminate a possibility, how can I know for sure that I have not "fried the radios"?
Appreciate your help. If I know that it is a software problem, I can continue to play with the Nexus toolkit and try different solutions.
samdev09 said:
Thanks again. Yes, the /efs folder is not where it was supposed to be. I did find the correct location and moved it. I will try using your ideas. Just one more question:
Since I had not done anything that would wipe out my IMEI number (neither software hacking nor physical damage). I wonder why this problem suddenly occurred. Just to eliminate a possibility, how can I know for sure that I have not "fried the radios"?
Appreciate your help. If I know that it is a software problem, I can continue to play with the Nexus toolkit and try different solutions.
Click to expand...
Click to collapse
I'm not sure how to check if your radio is fried. Basically, it means something's wrong with your hardware, where you experience occasional or complete signal loss. But in your case, you lost your IMEI. So, back up your nv_data files, flash using NRT or ODIN and see what happens.
NRT will push the stock radio while doing the "Flash Stock + Unroot" Option. So, you'll get the stock baseband as well. This should fix it. If your IMEI still doesn't work, try restoring the nv_data.bin and md5 files you backed up as mentioned in the link I posted.
Let me know how it works out. :good:
Always make a backup of /EFS (Support in both PhilZ_CWM & TWRP )for safety, though the IMEI would be only wiped by CWM wipe /factory option......happened to me a few days back, luckily i got my /efs restored & flashing stock doesn't bring any IMEI back since it's actually phone specific plus comes with a proper MD5 !!
the above method should work and here more info on the EFS
Hey guys I bought my sg3 about 3 months ago from a friend who had cynogen mod on the phone and it worked fine but I had cynogen mod on auto update and now my imei shows as 0 via *#06# and I cant call or text etc. Unfortunately I do not have a backup from when the imei worked because I didnt expect it to do this. So far Ive removed cynogen mod and reset it to stock firmware but im having the same issue any suggestions?
Its the SGH1747 version
dolee said:
Hey guys I bought my sg3 about 3 months ago from a friend who had cynogen mod on the phone and it worked fine but I had cynogen mod on auto update and now my imei shows as 0 via *#06# and I cant call or text etc. Unfortunately I do not have a backup from when the imei worked because I didnt expect it to do this. So far Ive removed cynogen mod and reset it to stock firmware but im having the same issue any suggestions?
Its the SGH1747 version
Click to expand...
Click to collapse
Your baseband is probably corrupted. You may try reflashing a stock modem/baseband via recovery. I had a similar problem once, although I was on stock ROM, and re-flashing the modem zip worked.
I, however, tread very carefully here as I am aware the forum is wary about discussions relating to IMEI.
Larry2999 said:
Your baseband is probably corrupted. You may try reflashing a stock modem/baseband via recovery. I had a similar problem once, although I was on stock ROM, and re-flashing the modem zip worked.
I, however, tread very carefully here as I am aware the forum is wary about discussions relating to IMEI.
Click to expand...
Click to collapse
yeah im not trying to change it which isnt allowed just tryin to figure out how to do what you said could you list me some steps or link me how to do this?
dolee said:
yeah im not trying to change it which isnt allowed just tryin to figure out how to do what you said could you list me some steps or link me how to do this?
Click to expand...
Click to collapse
Don't know if you're willing to pay to have this repaired but here's a site that does it. I've done stuff with them before. Very good service.
(no, I don't work for them - just a happy customer.)
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-imei-efs-repair/
dolee said:
Hey guys I bought my sg3 about 3 months ago from a friend who had cynogen mod on the phone and it worked fine but I had cynogen mod on auto update and now my imei shows as 0 via *#06# and I cant call or text etc. Unfortunately I do not have a backup from when the imei worked because I didnt expect it to do this. So far Ive removed cynogen mod and reset it to stock firmware but im having the same issue any suggestions?
Its the SGH1747 version
Click to expand...
Click to collapse
You can look up peoplearmy's method (google it). You will not find help on how to fix IMEI on XDA. I had my IMEI wiped out a while back after flashing a bad rom. I had to get it put back, and then had to get LTE back.
Good luck.
dolee said:
yeah im not trying to change it which isnt allowed just tryin to figure out how to do what you said could you list me some steps or link me how to do this?
Click to expand...
Click to collapse
Can you go to Settings => About Device and see what you have under Baseband version? Whilst you are there, also check what Android version it says and the build number.
Larry2999 said:
Can you go to Settings => About Device and see what you have under Baseband version? Whilst you are there, also check what Android version it says and the build number.
Click to expand...
Click to collapse
android 4.3 base band 1747MVLUEMK5 build # JSS15J.1747MVLUEMK5
dolee said:
android 4.3 base band 1747MVLUEMK5 build # JSS15J.1747MVLUEMK5
Click to expand...
Click to collapse
Everything looks OK as your baseband version would likely read 'unknown' if it's bad. You may, however, still try re-flashing the modem via the method posted in the attached thread ... Please proceed at your own peril as I offer no guarantee that this will work or will not result in damaged phones,
http://forum.xda-developers.com/showthread.php?t=1831898
Please note you will need custom recovery (e.g. CWM or TWRP). You will find instructions for installing custom recovery at the bottom of the thread. If this doesn't work, then you may try doing a hard wipe from recovery and reinstalling everything including system ROM, modem and kernel.
Hope it works out for you.
Simple fix is to reinject imei which located behind the battery.. But sometimes for some reason if you do this, you'll stuck with edge network, can be fix though but you gotta go back to stock in order to do so
Sent from my SAMSUNG-SGH-I747 using Tapatalk
LARMYV said:
You can look up peoplearmy's method (google it). You will not find help on how to fix IMEI on XDA. I had my IMEI wiped out a while back after flashing a bad rom. I had to get it put back, and then had to get LTE back.
Good luck.
Click to expand...
Click to collapse
I'm in the same boat as you once were. I lost my imei and had to inject it back, now I have no LTE service anywhere.. It says LTE but no internet connection. Any help? Sorry if I threadjacked here but I've been dealing with this for a year now and I really need a solution...
karmasblade said:
I'm in the same boat as you once were. I lost my imei and had to inject it back, now I have no LTE service anywhere.. It says LTE but no internet connection. Any help? Sorry if I threadjacked here but I've been dealing with this for a year now and I really need a solution...
Click to expand...
Click to collapse
you will have to google peoplearmy imei lte and find the tutorial on how to restore imei and get LTE back.
You will not be able to find the thread on XDA because XDA deleted it sometime ago. I was like you and lost my imei. Once I re-injected it using a tutorial on XDA, I was stuck on edge. Then I finally found peoplearmy's tutorial, downloaded the programs and followed the steps to get LTE back. I got it back and haven't lost it since.
LARMYV said:
you will have to google peoplearmy imei lte and find the tutorial on how to restore imei and get LTE back.
You will not be able to find the thread on XDA because XDA deleted it sometime ago. I was like you and lost my imei. Once I re-injected it using a tutorial on XDA, I was stuck on edge. Then I finally found peoplearmy's tutorial, downloaded the programs and followed the steps to get LTE back. I got it back and haven't lost it since.
Click to expand...
Click to collapse
I can't find the link, can you PM me it?
I had that happen to me with a 0 on my phone and was able to get it back I had no backup either what I did is go on the NV Data restore or NV writer thread and downloaded the NV writer and put myself back on stock ...I went thru a few pages in the post and someone had a file where you could put your IMEI into that file maybe it was set up thru notepad but you could fill in the zeros with your IMEI and name it I think a txt.file after then open the NV writer and instead of backing it up cause you can't just restore that file where you fill in you're IMEI and it went right back into my phone. There also a video on that page how to do it. You just need basically that file to put your IMEI back in. I might still have it if not keep going thru the post took find it. There a picture of what it looks like to restore if you list it but every time I tried to open that link to restore it wouldn't let me. Hope it wasn't to confusing but it's basically a white box with a bunch of zeros and replace the zeros with your IMEI and save it as atxt. File I believe and just restore it as shown in the video for backing it up but just restore instead it does work cause I didn't have an IMEI on my phone it just had a zero
---------- Post added at 10:53 PM ---------- Previous post was at 10:48 PM ----------
http:// http://forum.xda-developers.com/showthread.php?t=1804117
NV writer
heres the NV txt file to write your IM?EI back to the phone.extract the zip.
britt21 said:
heres the NV txt file to write your IM?EI back to the phone.extract the zip.
Click to expand...
Click to collapse
could you link the video or the thread with the video?
instructions werent so clear
dolee said:
could you link the video or the thread with the video?
instructions werent so clear
Click to expand...
Click to collapse
I believe this is it. http://forum.xda-developers.com/showthread.php?t=1804117
karmasblade said:
I believe this is it. http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
?
I got a message saying failed phone did not answer when writing any ideas
Hey guys, I think I screwed up. I think that I lost my IMEI through flashing it and I didn't make a back up. It says 0 and only very few of the *# codes work, the *#7285# and #22745927 codes do absolutely nothing and the only one that I know of that works is *#*#4636#*#* which doesn't help me at all. Most programs that I use don't detect the phone correctly or my phones just downright wrecked. Example is DFS says CPS N/A in every section and Samsung MEID Repair says "Unhandled exception has occurred in your application" when I try to connect it to my phone.
I'm running CM11 4.4.1 and I had the problem when I was running a 4.3 ROM. Also I have data and I can make calls. Its just that I cant send MMS and I drop to edge over time and stay on edge until I restart.
Any help would be greatly appreciated. Everyone I call is saying it'll cost $65 - $75 IF they can even fix it.
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Note that if you reinject IMEI, it might screw up your network
audit13 said:
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
I wish I could, When I try to use it, it says "Failed.. phone does not answer". Keep in mind that *#7284# doesnt do anything at all.
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
pcshano said:
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
chasetacos said:
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
Click to expand...
Click to collapse
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
pcshano said:
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
Click to expand...
Click to collapse
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
chasetacos said:
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
Click to expand...
Click to collapse
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
Click to expand...
Click to collapse
Cool. I Will do this and I will keep you updated. Itll be just a few moments before I complete the process
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
Click to expand...
Click to collapse
So when I try to flash the stock I get an error status 7. Any advice?
chasetacos said:
So when I try to flash the stock I get an error status 7. Any advice?
Click to expand...
Click to collapse
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Cool. It may not be till tonight or tomorrow till I respond, I'm about to have a project m competition. I'll let you know how it goes as soon as I get a chance.
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So now that Ive restored to stock, I have a transparent window with yellow text in it. it reads a bunch of info on the phone. It also said that it was in factory mode?
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So despite being stuck in factory mode I was able to write the NV and luckily I dont have any new network problems as far as I know. However my IMEI now says / 00 and in the phone info it says "unknown"
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
chasetacos said:
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
Click to expand...
Click to collapse
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
pcshano said:
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
Click to expand...
Click to collapse
Still nothing, im getting the same result. This Nv data bin file is not in there. i mean, unless i dont know where to look, but ive checked the whole EFS folder and its not in there...
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
elcocolo50 said:
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately that did nothing . I might just have to cry about it