[Q] Lost my IMEI, recovered it successfully, but I still can't connect to Verizon - Verizon Samsung Galaxy S III

Alright, so I just got my Galaxy S3 about 2 weeks ago. As I can't stand the look of Touchwiz, I rooted my phone, unlocked the bootloader, and put AOKP build 3 on there right away.
Everything was working great, except for my lack of Picasa sync, so I flashed BlackBean 5, then JellyWiz, and eventually went back to AOKP build 4. Wanting to get my Picasa sync, I tried flashing a few custom GApps builds, and then reflashed AOKP b4 fresh with the custom GApps.
After booting my phone back up, the "Activating" screen came for about 5 minutes, before it said that it failed. Checked my phones settings, and my IMEI was at 0. I flashed my phone back to stock, then used QPST to restore my IMEI.
IMEI is now displaying properly, but I am still totally unable to get any sort of connection to the Verizon network; voice or data. Do I have a brick? Furthermore, if I do, will relocking the bootloader, running TriangleAway to reset my flash count, and unrooting/factory reset on the stock rom be sufficient to return the phone to Verizon, or will they be able to tell that I messed with it and void my warranty?

reprovision your device with the dialer code *2767*3855#
next time follow the guides stickied before flashing...if you would of did the nv backup via terminal emulator then you would of never lost imei in the first place.

can terdayou
droidstyle said:
reprovision your device with the dialer code *2767*3855#
next time follow the guides stickied before flashing...if you would of did the nv backup via terminal emulator then you would of never lost imei in the first place.
Click to expand...
Click to collapse
Thanks for this; I can't really tell if it works yet because I put my Fassy back in service on this line temporarily, but I will be able to find out tonight when I have a chance to call Verizon. It has improved my situation, though -- I am now seeing signal whereas before the reprovision I had the Ghostbusters/No Smoking No Sign in place of a signal bar.
I unfortunately didn't see any of the stickies as I found all of the instructions I needed my googling and grabbing things from one place or the other. I did find that thread when looking for a solution to this, though, and I have to say that the people on the Development board for this phone are amazing; they have really done an amazing job getting everything that one would need right on the front page.
Also; *would've

Any flashing you did while your bootloader was unlocked wont be counted in the flash counter.

Related

Can't make calls or have any service

So I recently flashed the CM10 M2 rom on my verizon GS3 and it worked good for a week. Now I can't get any service on the phone.(calls, internet, etc).
I flashed it back to bone stock using Odin and still didn't do the trick. I thought it might be the SIM card but I tested it with my old Droid Razr and it worked fine. Any solutions? I really want this phone functioning again. thank you
Kinda new to Samsung and Verizon but from what I read, u may have list your imei, you can look up tutorials on you tube on how to restore it if u backed it up, or how to install default ones. Happened to me and I had to do a factory reset and re root
Sent from my PC36100 using xda premium
chupafaros said:
Kinda new to Samsung and Verizon but from what I read, u may have list your imei, you can look up tutorials on you tube on how to restore it if u backed it up, or how to install default ones. Happened to me and I had to do a factory reset and re root
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
wasn't sure on how to restore default imei. I did an unroot and re-root and still didnt work. still need help
still in need of help I noticed my IMEI was at 0 so went through a long process to restore it. Now I do have a number under "IMEI" but mobile network still isn't working. I'm currently running stock everything. please and thank you
Well if your like me, you now believe you have a $700 brick. Well I had t he same issue, and I'm rolling done the highway typing this post on my phone. Just fixed it today in fact. This is what I did to fix it. I have a vzw sgs3. Flash it to stock. Flash stock modem fw. Search the forum for restore imei guide tool. Follo those instructions and you'll download a file with a panda icon. after that, when it turns on you will still have no service. This is ok. Search the forums for SIM reprovision. One of the posts tells you to back up everthing including your internal sd. Do that if you want your stuff. Then it will tell you to dial *2767*8858#. (I know these are the wrong numbers but they are in the *xxxx*xxxx# format and it starts with *27.) This should do it.when it reboots it's like a factory reset. But it fixes it. Oh and I also had Verizon give me a new SIM. To 're cap... search Guide imei restore tool and SIM provision.hope this helps.
mrfishjosh said:
Well if your like me, you now believe you have a $700 brick. Well I had t he same issue, and I'm rolling done the highway typing this post on my phone. Just fixed it today in fact. This is what I did to fix it. I have a vzw sgs3. Flash it to stock. Flash stock modem fw. Search the forum for restore imei guide tool. Follo those instructions and you'll download a file with a panda icon. after that, when it turns on you will still have no service. This is ok. Search the forums for SIM reprovision. One of the posts tells you to back up everthing including your internal sd. Do that if you want your stuff. Then it will tell you to dial *2767*8858#. (I know these are the wrong numbers but they are in the *xxxx*xxxx# format and it starts with *27.) This should do it.when it reboots it's like a factory reset. But it fixes it. Oh and I also had Verizon give me a new SIM. To 're cap... search Guide imei restore tool and SIM provision.hope this helps.
Click to expand...
Click to collapse
I would like to first thank you for your input. Although i had that panda icon program i used a different program to restore my imei as well as my eri. After doing that i thought i finally fixed it then realized im still missing some of the numbers under phone status such as MIN. PRL version and ICCID. does the sim reprovision fix this.
Thank you all who have gave me advice to fix this problem. I finally got it fixed and i can't be happier. After going through circles restoring my IMEI and PRL it still wasn't working. What did the trick was dialing *2767*3855# which did a factory reset. My mobile is working again!!!!!!!!!!!!!:highfive:

[Q] Verizon Galaxy s3 roaming only, not activating

So I'm totally at a loss of where to go or what to even search for.
I have a verizon Galaxy s3 that I rooted and unlocked the bootloader on. I flashed a couple ROMs and now it won't connect to the network. It tells me it is in roaming mode only. I called verizon, but they said to just return the phone because it won't talk to their network.
I've read some things about "triangle away" and I kind of tried that. But it kept telling me that my flash count was 0 anyway. So it didn't do anything.
My IMEI and ICCID are correct to my sim card and phone. I originally flashed CM10 for the verizon s3 and it worked great for a few weeks. Then I tried a couple others and they worked also. Then I flashed the euroskank ROM, and that's when it no longer would connect. I went back to a previous nandroid, and still no connecting.
I don't know what the problem is, or what to search for, or where to go.
Should I try to install a stock rom. I know I keep seeing things about odin and installing the stock rom. Should I do that? That's something I haven't tried yet.
So, I tried reprovisioning the phone with *2767*3855#
And when I did that, it said sorry, your phone is not yet activated.
But I know it is, or, at least was activated. And when I call verizon they tell me it has been activated already. I don't know what to do. I'm thinking of trying to go back to stock
Same Problem
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
SpencePatriot said:
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
Click to expand...
Click to collapse
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
sin 7227 said:
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
Click to expand...
Click to collapse
Well that's good to know that you got it back working again. Sounds like it might be just be the ROM and not anything weird that we did to cause the loss of connectivity.
Thanks nertskull
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Input
halfgod85 said:
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Click to expand...
Click to collapse
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the Cyanogenmod update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Mitch90 said:
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the CM update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Click to expand...
Click to collapse
My S3 is having the same issue after a CM10 modification. Reflashing to a stock ROM fails, wiping and reflashing fails, trying a different rom on cwm fails, no backups to flash to (all result in error). So I stumbled upon this thread, read about reprovisioning, and I took it to mean input the numeric code into the phone dialer. I did that, and nothing happened. Can anyone provide insight on reprovision and how to do it? Google search on reprovision isn't giving me any hints.
If the reprovision is just failing and I've been doing it right, does anyone have any other suggestions? Really hoping my phone isn't soft-bricked with no ability to call/text.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Darthbull said:
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Click to expand...
Click to collapse
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
stuck...
I tried all the above, stock, radios, kernels, codes, ##RTN#, none of it works, my radio works cause i tried 911 and it jumped on roaming and began to make call at which point of course i hung up before letting it connect any words of wisdom... at this point just a tablet for wifi
stang68x said:
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
Click to expand...
Click to collapse
Bump
no sd wipe
stang68x said:
Bump
Click to expand...
Click to collapse
neither *2767*3855# nor ##786# wipe sd card, files on sd card stay intact
I have a galaxy note 2 on Verizon. This used to happen to me on CM 10.1 first stages but issue got fixed as the nightlies started. It only happened to me when I sometimes rebooted the phone or when the battery completely drained from 100-0% then when I would charge it and boot the phone it would show me an x and no signal bars. I would have to restore to a TW rom to get it to activate again but going into settings and switching to CDMA/LTE mode. Now I'm on ParanoidAndroid 2.99beta ROM and it still gives me that issue. Hopefully soon it will be fixed.:fingers-crossed:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
This worked for me after trying everything else. I wish I found this 4 hours ago.
wwonka69 said:
This worked for me after trying everything else. I wish I found this 4 hours ago.
Click to expand...
Click to collapse
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
wwonka69 said:
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
Click to expand...
Click to collapse
Ok it only works if you are on 4.04 as far as I can tell.
bump:good:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
Thank you buddy,
This helped me get my phone back in working order -- For those of you wondering why the "*2767*3855# is not working is because you are using the wrong flash. You must use "Official VRALG1 4.0.4" - and currently the link is down on the thread - I just googled it and found it elsewhere. I tried one of the other OTA's and it would not work. Also, do exactly as netskull described - even regarding the antenna. When using VRALG1 4.04 - The second i entered the last "hashtag (#)" it popped up another screen which helped get my phone working. I did not have to press send or anything. Kind of sucks that I lost all data on my internal card, but I DID back it up and now I will have to go through and restore. Since some people were wondering -- It did not mess with anything on the external card... It did unroot my device, however, so I will have to do that again as well.
For some reason, flashing the latest MIUI messed up my phone and put it in roaming all the time. Oh well, happy i got it working, and subscribed . Thanks once again Nertskull.

Dropping data and no calls/texts. Advice please.

Just in case this post gets moved, I want to identify my device as the Verizon Samsung Galaxy S3 (i535).
To give a little background on my issue, I have an issue with the device. When I first got it back in July, first thing I did was root the device. Naturally, since it was a new device, I was working with experimental methods... a couple weeks ago I thought to download CyanogenMod 10.1 (nightly build) to flash it with 4.2 and rid myself of the persistent OTA update that as we all know could not effectively install because of the measures I took to root. So, I boot into recovery and flash my custom rom. BAM! As it turns out, I did not have an unlocked bootloader and my phone was now teetering on the verge of being a $600 paperweight. I got that dumb yellow triangle saying unofficial firmware detected or some nonsense like that... Anyway, I look around the internet and decided that I was going to revert back to a stock rom using Odin, and then proceed to unlock my bootloader and root the device (I followed method 3 here) I used some touch recovery console that I have never heard of before (backups incompatible with ClockworkMod recovery) and something must have failed because my back up would not flash. I took the hit on losing most everything and reflashed successfully the custom rom mentioned earlier.
After about a week, I noticed the device began to drop data. 4G would just stop at random parts of the day, and I would have to disable and enable the data to get it to reconnect. At this point I was still able to make and receive phone calls and texts. After about 3 days of this, I concluded it was more than likely a bug in the custom rom, and that I could not live with it... so I redid the a fore mentioned tutorial and left the phone as a stock/unlocked/rooted device. The data issue continued, but with a twist. I was now unable to make or receive phone calls or texts. No matter what I did, I could not do anything and the 4G would only stay connected for a matter 5 minutes or so. When I logged into my vzw account, it identified my device as an unknown non-verizon device. Customer service walked me through various soft/hard reset techniques and nothing worked. They also suggested I try a new SIM card, which failed to work.
So, I turn to the bright minds of the android community. I have already decided not to invoke the Verizon warranty offered, where the result is they take my malfunctioning phone in flawless cosmetic condition and replace it with a "like-new" phone in working condition, because I think it's garbage that a warranty would give out used crap (should fix or replace). I have not contacted Samsung customer support yet because I wanted to see what my options were. I've already attempted flashing different radios and nothing seem to make any difference. If I have to, I will revert it back to stock again and invoke Samsung's warranty program, but I would much rather keep the phone. As it sits, I am stuck with my Motorola Droid Razr Maxx, and that just doesn't cut it.
So I ask, is there anything that can be done? Anyone know of a fix for my situation? I saw something about this in my quest for an answer and I don't know if my situation is a fit for this fix. If anyone has any knowledge of my issue and a work around for it, it would be greatly appreciated. I am at my whits end.
It sounds like you've done your homework on your problem.. The only thing in your post I didn't see was your sim card.. Maybe pulling it wait 2min restart. Shut down and insert,, or maybe a reprovision of the sim may be in order..
Ahaaaa....!!!
If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.
HHF2 said:
If your IMEI is intact, I would say to flash to ICS and reprovision the phone as suggested above. If it is not, you need to restore it with that backup that you made some time ago.
If it were me, I would reprovision, that is easy to do and I honestly think that it will work for you. If that works for you, reroot and restore your backup for TW ROM and you will be fine.
Click to expand...
Click to collapse
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.
mkruluts said:
Well that's just it... I don't know anything about the IMEI and how to determine if that is the issue. If by reprovision you mean reflash back to stock, that is it's current state, and that did not resolve the issue.
As for the other comment in regards to the SIM card... I have already attempted that method, and it did not work. Also, a new SIM card was also tried, and had no success.
Click to expand...
Click to collapse
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.
HHF2 said:
Google reprovision, it is a number combination that you enter on the keypad that resets your phone. I had a similar problem that you are having and that fixed our for me. You also need to know that when you do this, it will erase all of your information on the phone. It will be just like it was when you unpacked it and powered it on the first time.
You will have to be on ICS because they removed the option to do this with JB. Just search for the code to enter and you will be fine.
Click to expand...
Click to collapse
Ok. So I tried the reprovsioning mentioned above. When my phone rebooted I was on data and able to make phone calls. Score! However, I checked the IMEI and it said 0. So, thinking that it was just a matter of time before my device began to stop working again... I did the IMEI fix. Now my phone is placing calls and holding data without issue. The OTA updates are flooding in and installing without issues.
I would like to point out, while I feel better having done the combination of both reprovisioning and IMEI fix, ultimately the initial reprovisioning did appear to resolve the issue.
Thanks to everyone for the assistance provided.

[Q] Potentially Lost IMEI / Brick

My phone will not recognize Verizon as its carrier or connect to a cellular network in any way. Settings > About Phone > Status > IMEI reads "0." I have, in some capacity, "lost" my IMEI.
I understand their are a lot of threads on this topic, however, I (unfortunately and ignorantly) have done a number of things after the actual losing of my IMEI and I am not sure the current state of my device or if a backup of my IMEI exists anywhere.
First my story. I successfully managed to get one of the early nightly builds of CM10.2 running on my phone and all was well. After updating to a more recent nightly via the CM updater, I noticed I had lost cell service in all capacity. Confused, I decided to not take any chances and revert to a CWM full backup I had made while still running CM10.1 stable. Still nothing. At this point, I thought that something was wrong with my firmware, and so I flashed a zip containing the latest Verizon firmware successfully (same that was installed previously). Nothing.
Not really understanding that one could lose their IMEI or the potentially signs of such loss, I decided to go all the way to stock via odin. The image did unlock the boot loader and grant SU, but did not wipe user data. Thinking it would help, I wiped data/factory reset within the stock recovery and then reflashed the image. Of course, still nothing. This is my current situation.
So my question is this: do I have any hope of recovering or "injecting" my IMEI? From my understanding, the Samsung mechanism designed to backup the IMEI in these such instances is broken. In fact, it probably "restored" it to a bogus null value. I think this means that I now have no IMEI information on my device. If so, does this mean I can manually inject it somehow? I have tried methods that purport to build the files on a pc and then move them to the device but I cannot access any of the Qualcom menu's that necessarily put the phone in a certain USB mode via the phone dialer. I get "no mobile network available."
Also: I still have my CM10.1 full CWM backup from before I lost my IMEI. If this backup contains the information needed to restore my IMEI, is their any way I can retrieve it? I think this is my best shot, but I'm not sure.
I would like to know if my new phone is a paperweight, since I am still within the 14 day return period. If I have indeed bricked my phone, there is a slim change that I can reset everything back to stock and play dumb with Verizon to get an exchange.
I apologize for the ambiguous vocabulary and/or description. I have a good working knowledge of most of the stuff on xda, but a lot of the language used in forums regarding IMEI restoration is foreign to me.
Thanks in advance for any help!
You have to Odin a stock ics image, or restore a backup if you have it, and dial *2767*3855#.
This should fix your imei and eri status by reprovisioning your phone.
Also as soon as you reroot and get up and running again, make an imei backup so you won't have to go back to stock if you have this issue again.
You could manually inject it, but a moderator has to grant you permission to use the thread. However, manually injecting it with qpst will leave your phone in roaming (not actually roaming, but the status icon won't go away) because it won't fix your eri number.
Use this option first, if it doesn't work you can try injecting it.
Sent from my SCH-I535 using Tapatalk 2
I used qpst to restore my imei and then used this method to get back without using odin, if you haven't already done so. I also think you can get your imei and eri back without using qpst with this method. I had already restored my imei and eri wasn't saying 5 like it should.
http://forum.xda-developers.com/showpost.php?p=44871571&postcount=3
Edit : I forgot, once you have your imei and eri restored and backed up. Don't forget to flash your modem back up to the version you want.

Problem after flashing 4.3 rom causing me to be stuck in 2g

I am having a huge issue with my phone. I have been flashing custom roms for the past few years and this is the first time I have ever ran into a issue like this. I flashed SlimRom 4.3 build 2 a couple weeks back, it was taking forever to switch between 3g and LTE sometimes up to 5 mins to lock. Not to mention the signal was super low. I ignored it for the most part as it is a newer rom and figured it was just a bug and would hold off for now till kitkat released.
Then my phone would just start random rebooting about once or twice a day. Then on my way home from work i was bluetoothed to my vehicle when it did a random reboot. After that Ive been stuck in 1xRTT since. I also managed to loose my IMEI and PRL version they are both set at 0 and I do not have a backup. Has anyone else ever had this issue? I don't have a clue how to get it working again. My phone is out of warranty I am in the midst of flashing it back to stock to see if that works. Ive searched for hours trying to find a fix. Thanks.
Reverted back to stock.still no luck. Also play store won't work. No connection wirh retry button even while connected to wifi
What firmware/radio do you have? If you've been on custom roms a while you might need to update your radio baseband (most current is VRBMF1). You can flash an updated radio without regard for the Rom you're using.
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 10:29 AM ---------- Previous post was at 10:25 AM ----------
The imei thing is a separate issue. I lost mine without a backup when I first started flashing roms... I think it was cM at the time. I ended up going all the way back to an early stock image, grabbing the OTA updates and then rooting and flashing all over again. I don't know what part in particular got me my imei back.
Sent from my SCH-I535 using xda app-developers app
Do you mean a backup of efs partition or a nandroid? There is a thread at rootzwiki about recovering your imei-efs items. When u get it back do
Su
Reboot nvbackup
In a terminal then you wont have to worry about this again. If you have a nandroid restore it and you'll b good.
Yes my efs folder was completely empty. I reverted back to stock 4.0.4 still had a "0" for IMEI so i used QPST and entered in the IMEI manually and it stuck. I have signal back now. I just got factory mode off. Now my phone is stuck on "Activating", a factory reset should fix that. So this is resolved. Thanks for the help.
quicksilv312 said:
Yes my efs folder was completely empty. I reverted back to stock 4.0.4 still had a "0" for IMEI so i used QPST and entered in the IMEI manually and it stuck. I have signal back now. I just got factory mode off. Now my phone is stuck on "Activating", a factory reset should fix that. So this is resolved. Thanks for the help.
Click to expand...
Click to collapse
Is this the fix to get everything up and running again (flash back to ICS)? I was about to start my own thread until I read this. I lost my IMEI, ERI and MEID but didn't back it up first (I know I know ... boo). I manually input my IMEI using QPST like you did and was also able to fix my ERI and MEID and now I have data and text, but still no voice connection. I've flashed a stock (rooted) ROM and tried the reprovision code *2767*3855# and the RTN codes ##786# & ##72786# but nothing happens (I've seen in other forums this only works in ICS and not JB). Last night I downloaded a stock unrooted JB ROM (4.1.2) and ICS ROM (4.0.4) and am planning to ODIN back to stock and complete a factory reset to see if it will kick the gears back in motion again.
I'm not meaning to hi-jack this thread but confirm this is the solution to completing a non-backed-up IMEI/ERI/MEID fix.
-Edit-
There are tons of threads out there starting with "I've lost signal, what happened?" and ending with "I'll report back and let you know what I've found." or "Verizon replaced it for me." but none offer a viable user solution. I'd love to see the answer posted so other searchers out there can find help.
I can confirm everything you did will restore your IMEI/ERI and connectivity. I did all the steps you did (manually input IMEI and use the utility to repair ERI and MEID), then reverted back to unrooted stock using odin. I still didn't have signal until I did a factory restet IN THE ROM. Going back to stock using odin and doing a factory reset in CWM didn't fix the issue, but going into the phone's settings and completing a factory reset from there caused my signal and connection to come back.

Categories

Resources