Problems with all 4.2.2 roms! - Verizon Samsung Galaxy S III

I was running slim 4.2.1 for quite some time with no problems, i loved it. I flashed 4.2.2 and my phone got stuck in NV and my phone number would come up as 000-000-3370. On first boot everything seems to be fine except that i get an error when i try to open up the play store. On my next boot is when I would see these problems. I tried everything from dirty flashing from a working 4.2.1 rom to completely formatting everything, even my external sd, and the same thing happens. This happens with every 4.2.2 rom out there. When i reboot i get stuck on the activating screen and my phone will get stuck in NV and ruim/sim wont stick no matter what i do. i don't know what else to do. someone please help!

It isn't a rom issue it is an S 3 issue that randomly occurs when flashing ROMs. You will have to flash the stock rom and reprovision your phone. I know because it has happened to me twice and both times it was with a Touchwiz ROM. You should have backed up your IMEI just in case this happens.

my imei is backed up. but why is it only 4.2.2 roms that do this?

I was able to flash back to a 4.2.1 Rom, namely pure Google for now, with no problems. but when I flash any 4.2.2 Rom the same thing happens.

All 4.2 ROMs used to do this to me.
However.
Only also happened when I flashed miui.
Now I run liquid smooth and haven't had the problem since.
sent from that young galaxy.
God bless the American people!

do u guys think I should Odin back to stock, then root, unlock, and try to flash 4.2.2?

Actually, there is an easier way
I have had this happen numerous times and it lef me to mess with my phone a little bit. I originally thought that setting it to CDMA/SIM and then rebooting would fix the problem, but I found a simpler solution to that. The last time I encountered the problem I simply set the phone to RUIM/SIM under mobile networks and then Turned on airplane mode for a few seconds then turned it off and I found my number under phone settings and everything. Try that and let me know how it goes.
Edit: Sorry, the term is RUIM/SIM, not CDMA/SIM. My bad.

hmmm, I'll definitely give that a shot later on tonight.

well I tried it, it works. but only temporarily. once I reboot it reverts back to how it was. any other thoughts?

anyone?

Chitala383 said:
anyone?
Click to expand...
Click to collapse
try this. i had the same problem. http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2

nope, none of that works either. no matter what I do ruim/sim will not stick on a reboot on any 4.2.2 Rom. I'm really getting frustrated with this.

no one has any other solutions for me?

Chitala383 said:
anyone?
Click to expand...
Click to collapse
Does your phone display an IMEI number?
Settings->About->Status
Don't need the number, just to know if you have it there....
Also do you still have Root/Unlocked bootloader?

yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.

Chitala383 said:
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Click to expand...
Click to collapse
Have you done a complete factory restore through Odin? You would lose root and unlocked bootloader, but it may be faster to restore to stock, and reroot/mod than to try to find an "easy" fix. I was having some issues the other day in between a few ROM's, but I just factory restored, and restarted from "scratch". Now I am running perfect.
You may have already tried, but on page 1 you asked if you should, and I did not see a confirmation you did so.

Had the same problem... And yes, the phone must be reprovisioned. Although sometimes you can just adjust the network settings and change it from NV. That worked for me also.
Sent from my SCH-I535 using Tapatalk 2

I flashed root 66 via Odin, bootloop. flashed the ma2 stock image, bootloop. then flashed the lk3 stock image with success. but still with the same results as before.

tomorrow I'll try flashing g1 and start from scratch there. what do u guys think?

well, I odin'd back to bone stock G1, rooted with rootdebugfs, flashed cwm with ez recovery, unlocked my bootloader with ez unlock, flashed liquidsmooth 4.2.2 rc2 and guess what. same ****!!!!!!!!!!!!! i'm really getting fed up with this. someone has to have a solution to this cuz this is really pissing me off.

Related

Flashing error!!!

I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
where did you get cm10 for the vzw phone? I thought it was for all of the other phones but vzw? Try going back to stock non root. try flashing the modems in the thread about this one.
phillyphill39 said:
where did you get cm10 for the vzw phone? I thought it was for all of the other phones but vzw? Try going back to stock non root. try flashing the modems in the thread about this one.
Click to expand...
Click to collapse
if you go to goo app its in his folders of roms i beleive. i have tried that. i switched to my wifes sim card and got same results, so must be something on the phone
pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
Flash the stock tar.md5 from here: http://samsung-updates.com/device/?id=scH-i535
Whatever you flashed put a custom kernel on there, and that's why you get that message.
pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
I don't mean to be rude, but development is not for questions
timothydonohue said:
I don't mean to be rude, but development is not for questions
Click to expand...
Click to collapse
no offense taken, but with only one question and answer section and that for all cell services could make this question a little different
pitmanr2003 said:
no offense taken, but with only one question and answer section and that for all cell services could make this question a little different
Click to expand...
Click to collapse
I have d2hackers cm10 up and running on my device...click link in sig!
i have tried new modem and fully stock rom. no luck. I was running dual boot before that if that could of caused issue. I am lost now.
pitmanr2003 said:
i have tried new modem and fully stock rom. no luck. I was running dual boot before that if that could of caused issue. I am lost now.
Click to expand...
Click to collapse
I am lost. i have tried everything and i am now where a beginner when it comes to android. Im afraid that if i take it back they will see it has been rooted.
pitmanr2003 said:
I am lost. i have tried everything and i am now where a beginner when it comes to android. Im afraid that if i take it back they will see it has been rooted.
Click to expand...
Click to collapse
wipe data then odin a factory stock image
droidstyle said:
wipe data then odin a factory stock image
Click to expand...
Click to collapse
tried that still wants to roam.
pitmanr2003 said:
tried that still wants to roam.
Click to expand...
Click to collapse
I have tried to odin stock and then wipe. still showing no data connection, and same thing when I put my wifes sim in. IM thinkiing it has something to do with the dual boot i had set up before. is there a way to repartion the internal sd card or emmc?
This seems to be happening to a lot of people flashing AOSP ROMs....this is why they warn you they are not responsible for what happens to your phone...especially with Betas.
There are many threads on this and several on how to get a workaround until someone figures out how to fix this.
Try doing a search on losing IMEI or roaming after flashing CM10...it is happening a lot...that is why I am just using rooted stock with VZW apps and TW frozen.
this problem I was having with no data or radio in CM10.
I used ODIN to go back to stock rooted (root 66).
When I did that I was boot looping in the puking rainbows 4GLTE boot animation.
I eventually figured out how to fix that by booting into recovery (press volume up, home button, and power button at the same time till phone boots). I then did a wipe data/factory reset.
My phone then booted fine into stock root.
I then proceeded to punch in *2767*3855# into my dialer immediately when I got stock root working. That did some sort of a factory reset / format. It all happened so quick I could barely read what it told me. The phone rebooted after a while.
I then downloaded EZ-Recovery for VZW Galaxy S3 app from the Play store.
I installed the custom recovery from Dhacker's CM10 post over on the droidhive forums using EZ recovery.
I also downloaded the CM10 file to flash and the Jelly Bean Google Apps file.
Rebooted into recovery, Wiped data/cache/dalvik.
Installed the CM10 file.
Installed the Jelly Bean apps.
Reboot.
Profit.
I now have a largely functional CM10 (as far as I can tell there are some camera issues). Data 3G/4G is working, so are calls and text and everything is dandy.
Did the *27 bla bla thing posted above and back to normal. Thanks everyone
Sent from my SCH-I535 using XDA App

[Q]No cell service

Hello. I am having a bit of an issue. Today after I decided after having fun with touch wiz i decided i wanted to go back to a backuped copy of ParAndorid and we it go to the home screen i got repeated errors of com.andorid.phone so i rebooted and since I haven't had any cell service. I put it back to factory, tryed different roms and such and non are working. I even tired the ##76786# and got nothing. Any ideas?
Im guessing you lost your IMEI, did you happen to back it up? http://forum.xda-developers.com/showthread.php?t=1852255
x714x said:
Im guessing you lost your IMEI, did you happen to back it up? http://forum.xda-developers.com/showthread.php?t=1852255
Click to expand...
Click to collapse
as far as ik its still there. Its showing a 99000020.... number. No, i didn't know if i had too.
Maybe your sim got jacked or something? Did you just do a reset on your phone or did you odin back to stock? If you just did a reset maybe odin a factory image and see if its corrected? Also before that maybe you can try flashing the radio/modem and see what that does?
x714x said:
Maybe your sim got jacked or something? Did you just do a reset on your phone or did you odin back to stock? If you just did a reset maybe odin a factory image and see if its corrected? Also before that maybe you can try flashing the radio/modem and see what that does?
Click to expand...
Click to collapse
I just did the factory restore in the rooted version of touch wiz i have installed and it corrected this issue. I ended up calling them to make sure it was nothing on my end. It was werid that a factory restore insdie of touch wiz would fix something that odin couldn't.
But yeah topic [solved] Thank you though x714x
Cool, glad you got it fixed!
Hello Everyone,
I ran into a problem today while trying to update to JB. I installed AllianceROM_I9300_JB_XXELK4-Base on my Galaxy S3. I noticed It changed the baseband to something different of what I have. Since I was not able to make calls, I decided to restore my backup trough CSW.
I noticed then that my IMEI had changed to something else.
My status now is: The IMEI I had is now different, the modem I had that used to work is not working anymore, I flashed a different version of the modem but I cant get it to register on the network.
Any help is appreciated.

[Q] HELP! may have fried my phone with CM 10.1 update!!

Hello all and Merry Christmas!
I am in dire need of assistence.
Last night I went to update my CM rom to the 10.1 Dec.21st nightly. I have now been told that they were known to be corrupted. Anyways now I have restored multiple recoveries and I cant get my calls/texts to go through. The only connection I seem to be able to get is back in Stock TouchWiz where it gives me the option to "enable roaming for this trip." Wifi and everything else still work fine. Any suggestions??
Thanks!
Pups
Anyone!! please!!
I haven't tried any of this, I don't run CM but you might want to give this a read. Not sure if this is even your problem.
http://forum.xda-developers.com/showthread.php?t=2065285
I hit the roaming issue with yesterday's build and I solved it rather easily.
You don't need to Odin anything.
Simply factory reset and flash back to any TouchWiz rom from recovery. It can even be a Jellybean one.
Older CM10 or CM10.1 builds seemed to work, but were far less effective at restoring reception.
bobAbooE said:
I haven't tried any of this, I don't run CM but you might want to give this a read. Not sure if this is even your problem.
http://forum.xda-developers.com/showthread.php?t=2065285
Click to expand...
Click to collapse
This is most definitely my problem how did you find this?
LLStarks said:
I hit the roaming issue with yesterday's build and I solved it rather easily.
You don't need to Odin anything.
Simply factory reset and flash back to any TouchWiz rom from recovery. It can even be a Jellybean one.
Older CM10 or CM10.1 builds seemed to work, but were far less effective at restoring reception.
Click to expand...
Click to collapse
Okay so when I flashed Dec 21st CM10.1 i got into a loop and the ROM wouldnt even run so I just pulled my battery and restored to my last nightly. THEN the phone aspects stopped working. Should I factory reset from my CM 10 nightly or from my stock touchwiz recovery file. I already factory reset from my touchwiz file using TWRP

[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.

Restored imei but not connecting to network like it should

I tried flashing cm one day and after hours of not being able to connect to the network I realized my imei was deleted. I restored it flashed back to paranoid 4.3 but have been having connection issues. Next to no service in my house and places I had 4g I have 1 x or searching for service. I noticed my prl is 0, imeisv is 0 and also my eri set to 0. I flashed back to stock and everything was fine but as I excepted ota to upgrade firmware the mentioned above went back to zero. I believe I didn't do something correctly it's more than bad reception. Any ideas?
Sent from my iPhone using Tapatalk
So, to clarify, on stock you have normal connectivity and the imei and meid is present in settings>about phone>status?
Sent from my SCH-I535 using Tapatalk 2
FC127 said:
So, to clarify, on stock you have normal connectivity and the imei and meid is present in settings>about phone>status?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Sorry about that, the phone had normal connectivity when I went back to stock and in settings-about-status all values were present
Imei hex dex
Imeisv
Prl
I'm completely lost I have a feeling I didn't do something correctly when I restored imei. Either in qpst or In hidden menus on the phone. I just tried going back to out the box without any firmware updates and I have the same connectivity issues
Sent from my iPhone using Tapatalk
Restore from a previous TWRP or CWM backup. I had the same problem before and restoring a backup was the only thing that worked. I even tried manually restoring the IMEI through QPST without any progress.
I'll give it a try thanks
Sent from my iPhone using Tapatalk
For whatever reason I can't access my back ups. In twrp I go to restore and folder is empty. My back ups are on my sd card which I've used several times before. I tried going into install then go directly to that folder but nothing happens just goes into sub cater gory. I'm so lost this seems to not be a common issue so there's. Of a lot of info out there
Sent from my iPhone using Tapatalk
I recently got through this issue too. After fixing my IMEI, ERI and MEID my phone would recognize a network but could not make calls. What I had to do was ODIN back to a stock unrooted ROM then complete a factory reset from INSIDE THE ROM, not from recovery. Reflashing a nandroid from recovery wouldn't work and simply flashing to a stock ROM wouldn't work, it was only after doing a factory reset using the ROM (Menu->Settings->Backup and Reset->Factory data reset) that I got connectivity back fully. This might work with a Touchwiz rooted rom but I don't know for sure. Obviously after that you'll need to re-root and re-flash whatever ROM you want or restor from a previous saved backup. ABSOLUTELY backup your IMEI information, if I knew what I was doing the first time and knew how simple it was and how little time it takes I would have done that first and avoided all this hassle!!
postal302 said:
I recently got through this issue too. After fixing my IMEI, ERI and MEID my phone would recognize a network but could not make calls. What I had to do was ODIN back to a stock unrooted ROM then complete a factory reset from INSIDE THE ROM, not from recovery. Reflashing a nandroid from recovery wouldn't work and simply flashing to a stock ROM wouldn't work, it was only after doing a factory reset using the ROM (Menu->Settings->Backup and Reset->Factory data reset) that I got connectivity back fully. This might work with a Touchwiz rooted rom but I don't know for sure. Obviously after that you'll need to re-root and re-flash whatever ROM you want or restor from a previous saved backup. ABSOLUTELY backup your IMEI information, if I knew what I was doing the first time and knew how simple it was and how little time it takes I would have done that first and avoided all this hassle!!
Click to expand...
Click to collapse
This seemed to of worked. This is the one issue I've had with this phone that seemed I wasn't going to be able to fix. It also doesn't seem to be a common issue so there isn't a lot of discussion about it. Thanks again I though I'd be stuck with my iphone5
Sent from my iPhone using Tapatalk
Maduro78 said:
This seemed to of worked. This is the one issue I've had with this phone that seemed I wasn't going to be able to fix. It also doesn't seem to be a common issue so there isn't a lot of discussion about it. Thanks again I though I'd be stuck with my iphone5
Click to expand...
Click to collapse
I'm glad this worked for you. I was banging my head against the wall for a few days trying to figure this out. If you haven't already done it, back up your IMEI using the link in my last post. It literally takes only minutes and saves TONS of hassle.
postal302 said:
I'm glad this worked for you. I was banging my head against the wall for a few days trying to figure this out. If you haven't already done it, back up your IMEI using the link in my last post. It literally takes only minutes and saves TONS of hassle.
Click to expand...
Click to collapse
where did you find a stock rom..EVERY link I have tried, seems to be down or no longer valid.
thanks
postal302 said:
I'm glad this worked for you. I was banging my head against the wall for a few days trying to figure this out. If you haven't already done it, back up your IMEI using the link in my last post. It literally takes only minutes and saves TONS of hassle.
Click to expand...
Click to collapse
I was at the point I was gonna chalk this phone up as a loss. It doesn't seem like a common issue so there isn't a whole lot of help out there for this issue. I'm so glad I decided to check back in this thread. I can now afford to buy better presents for Xmas lol. You saved the day.
Sent from my iPhone using Tapatalk
DeathCry said:
where did you find a stock rom..EVERY link I have tried, seems to be down or no longer valid.
thanks
Click to expand...
Click to collapse
I noticed the same thing. I've been using the same file for the last couple years without fail pm if you want it. Goo manager also has it.
Sent from my iPhone using Tapatalk
OP you MUST backup your IMEI. If you don't you are going to have a serious headache getting it back.
Sent from my SCH-I535 using Tapatalk
DeathCry said:
where did you find a stock rom..EVERY link I have tried, seems to be down or no longer valid.
thanks
Click to expand...
Click to collapse
Sorry I fell off the map on this, life's been busy lately!! All the links to the files I used are infact down. Were you able to get your hands on a stock rom? For all the repair work I used CleanROM, but I only flashed a stock ROM to do the factory reset. I'm actually wondering if doing a factory reset from the menu in CleanROM will do the same thing. Do your research so you don't brick your phone.
I went and looked on my computer and saw the file I used for a stock rom was a Root66 (pre-rooted) ROM.
For what it's worth, here's the links I used:
I started with this return to stock guide. Step three led me to this guide to flash a stock rom using ODIN. Step five of that guide had the links to the stock ROMs and stock pre-rooted ROMs. I was having trouble downloading a 4.1.2 ROM so I used a 4.1.1 instead.
If you still need a stock ROM let me know and I'll find a way to get the one I used to you.
postal302 said:
Sorry I fell off the map on this, life's been busy lately!! All the links to the files I used are infact down. Were you able to get your hands on a stock rom? For all the repair work I used CleanROM, but I only flashed a stock ROM to do the factory reset. I'm actually wondering if doing a factory reset from the menu in CleanROM will do the same thing. Do your research so you don't brick your phone.
I went and looked on my computer and saw the file I used for a stock rom was a Root66 (pre-rooted) ROM.
For what it's worth, here's the links I used:
I started with this return to stock guide. Step three led me to this guide to flash a stock rom using ODIN. Step five of that guide had the links to the stock ROMs and stock pre-rooted ROMs. I was having trouble downloading a 4.1.2 ROM so I used a 4.1.1 instead.
If you still need a stock ROM let me know and I'll find a way to get the one I used to you.
Click to expand...
Click to collapse
Hey, no worries.. Life is much more important. Thanks for responding. I did get fixed.
I went back to a 4.1.2 ROM, couldn't fix everything. Eventually got back to 4.0.4. Got everything straightened out. And backed that _ _ _ _ up.
Was than able to upgrade to 4.4.2 aosp ROM, of course without needing the backup. But I have it.
Thanks again....as is usually the case, not reading enough up front did me in. Let that be a lesson kids.
Sent from my Nexus 10 using Tapatalk 4
does anyone have a link to the 4.0.4 stock rom? all of the links i have found are no longer up.
Thanks

Categories

Resources