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
Related
My maps gps lock got totally f*cked by synergy 1.7 so it was suggested to go back to stock and reroot since flashing new rom from clean wipe did not work.
A lot of links and methods are out of date, so I was wondering what the best way to get back to stock at this point.
I have the latest odin on my computer, I guess I'm looking for the most recent or most reliable stock image to flash.
Thanks
SGS3 production
SGS3 production
I think a lot of people recommend the root66 stock..... But I'd try noSympathy's image
Sent from my SCH-I535 using Tapatalk 2
I'm rooting immediately after so whatever is a proven version will make me happy
SGS3 production
They're both rooted so no need to do after. Both are tried and true, noSympathy's is based off the last OTA but some people like to start from scratch so that would be root66.
Sent from my SCH-I535 using Tapatalk 2
I want to get back to unrooted stock.
I can't seem to locate the route66 stock image
SGS3 production
http://forum.xda-developers.com/showthread.php?t=1762204
It's up to you but it's just more work to go unrooted then root yourself. Check the development threat there maybe an un rooted image there
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:36 AM ---------- Previous post was at 07:27 AM ----------
http://forum.xda-developers.com/showthread.php?t=1755386
Thought there would be a newer one but here's unrooted...
Sent from my SCH-I535 using Tapatalk 2
My main reason to flash stock was I was told that would be the only way to restore my faulty gps lock.
Do you think flashing a stock rooted image would do the same for me? Or should I flash unrooted image then start fresh? Time is not a concern, im patient
SGS3 production
FormeriPhoney said:
My main reason to flash stock was I was told that would be the only way to restore my faulty gps lock.
Do you think flashing a stock rooted image would do the same for me? Or should I flash unrooted image then start fresh? Time is not a concern, im patient
SGS3 production
Click to expand...
Click to collapse
Flash back to stock then root. Click link in sig.
i tried this......still having the same issue, switched from CM10 back to stock and had issues with my GPS being way off, like by 3300 meters off haha.....so flashed back to stock, still had the issue, so i used the rooted stock image and flashed that and i'm still off by about over 2k meters.....don't use my navigation or maps all that much but when i do need it i'll have a bit of an issue lol
I had issues with my gps for a few days. If was real flaky but got better with synergy 1.5. I have since move to 1.6 with a fresh install and am still okay. Check out a app called gps status. See if you can see any gps satellites. Maybe in that app clear your agps state in tools. Then if that doesn't work try to download gps assistance with the same app in the same settings. Make sure your out side for this stuff with your gps. It's probably not gonna hit ya sitting on the couch.
Sent from my SCH-I535 using Tapatalk 2
FormeriPhoney said:
My maps gps lock got totally f*cked by synergy 1.7 so it was suggested to go back to stock and reroot since flashing new rom from clean wipe did not work.
A lot of links and methods are out of date, so I was wondering what the best way to get back to stock at this point.
I have the latest odin on my computer, I guess I'm looking for the most recent or most reliable stock image to flash.
Thanks
SGS3 production
SGS3 production
Click to expand...
Click to collapse
I used the stock image from here:
http://samsung-updates.com/device/?id=SCH-I535
and used this method for rooting:
http://forum.xda-developers.com/showthread.php?t=1792342
my gps doesnt work at all
After Odin back to stock, non rooted image my GPS is fixed.
Now on CM10, loving it. Not sure if I'll ever try synergy again bc of that nightmare situation.
I use my gps pretty much all day. I needz it
SGS3 production
New AOKP JB issue with radio
Well I am trying to get something fixed and I am going through a complete restore to do this.
But just so you are aware the new AOKP JB release will kill your data. I learned a hard lesson with this when trying to recover and nandroid back to my previous rom. It killed my data completely and would not allow me to do anything with data in any rom. I used the root66 stock rom in hopes it would work, and that didnt even solve the issue.
Right now I am restoring a factory image through kies and seeing if that will do what I need. If it does, I am sticking with stock roms for awhile until AOSP roms have more time to develope with less bugs.
douglasf01 said:
Well I am trying to get something fixed and I am going through a complete restore to do this.
But just so you are aware the new AOKP JB release will kill your data. I learned a hard lesson with this when trying to recover and nandroid back to my previous rom. It killed my data completely and would not allow me to do anything with data in any rom. I used the root66 stock rom in hopes it would work, and that didnt even solve the issue.
Right now I am restoring a factory image through kies and seeing if that will do what I need. If it does, I am sticking with stock roms for awhile until AOSP roms have more time to develope with less bugs.
Click to expand...
Click to collapse
It sounds like you may have lost your IMEI or MEID. I hope you made a backup with QPST.
still had IMEI
toy028 said:
It sounds like you may have lost your IMEI or MEID. I hope you made a backup with QPST.
Click to expand...
Click to collapse
Well it turns out I still had my imei present on my phone and even after a factory reset like I did wit kies it still didnt work. Initially I wasnt able to get past the activation screen on the root66 rom, but I was able to with the stock factory image from kies in which case this allowed me to follow the steps in this link.
http://forum.xda-developers.com/showthread.php?t=1838791
Once I did that my phone rebooted and everything came back as it was never gone, well except for all of my data on the internal sd card, but that is to be expected.
After 2 hours of going through numerous steps I finally found a fix, mind you not the most simple of fixes, but a fix none the less.
I think I am just going to stay stock for awhile like I mentioned and wait for the OTA that comes out in 2014 lol, unless in review of AOSP roms the issues present now are gone after sometime.
Tks
Nice. Tks
Gps works like a champ on beans!
Gps seems to work substantially better on cm10 than on stock....ran the GPS test and i locked onto 14/19 satellites.
Beamed via NFC through the local store to the internet from my SGS3.
Ok, EVERY ics or above rom wipes my imei and renders the phone useless. I'm not a noob by any means, I follow the directions to the letter, and the imei number is toast EVERY time! I even backed it up, restored it... but it still shows just a bunch of stars. What in the world am I doing wrong?
The trouble started when I flashed the a mtd jb rom. I restored from the backup, got data back, but phone had no sound during calls. I had to go back to stock via a one click to restore the imei number. I was running jb right up until the mtd change. Now, I can't run ANYTHING, CM7 or above. No matter how or what I flash, it wipes the imei
I've been working on this for a week now, can't figure out what I'm doing wrong. I'm lost and back to gingerbread until I figure something out. Any help would be greatly appreciated.
klloyd said:
Ok, EVERY ics or above rom wipes my imei and renders the phone useless. I'm not a noob by any means, I follow the directions to the letter, and the imei number is toast EVERY time! I even backed it up, restored it... but it still shows just a bunch of stars. What in the world am I doing wrong?
The trouble started when I flashed the a mtd jb rom. I restored from the backup, got data back, but phone had no sound during calls. I had to go back to stock via a one click to restore the imei number. I was running jb right up until the mtd change. Now, I can't run ANYTHING, CM7 or above. No matter how or what I flash, it wipes the imei
I've been working on this for a week now, can't figure out what I'm doing wrong. I'm lost and back to gingerbread until I figure something out. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Just wondering. Did you back it up with the EFS in the Infuse Toolkit? According to the OP, EFS Partition Backup (protect your phone's IMEI information, find unlock info) forum.xd
http://forum.xda-developers.com/showthread.php?t=1702026
No, I used what ever the app is posted on the jb pages. Quick and simple. Makes a folder called eds backup. Inside u find a .tar file with the whole folder zipped up. I didn't find a place in the toolkit for restoring just that info. I can't even do.cm7 now, anything above gingerbread wipes the imei number, every single time.
If there were a one click to ice or jb, might would help. Beats me. I'm.completely stumped now. Never had trouble flashing anything.
klloyd said:
No, I used what ever the app is posted on the jb pages. Quick and simple. Makes a folder called eds backup. Inside u find a .tar file with the whole folder zipped up. I didn't find a place in the toolkit for restoring just that info. I can't even do.cm7 now, anything above gingerbread wipes the imei number, every single time.
If there were a one click to ice or jb, might would help. Beats me. I'm.completely stumped now. Never had trouble flashing anything.
Click to expand...
Click to collapse
Which JB were you trying to use? You might as well one click back to GB, try the toolkit in CWM, back up the EFS, and then flash one of the ICS ROMS. After flashing ICS ROM and before you reboot, use the toolkit to restore EFS and test it to see if it works. Not sure why it is happening with ICS but you never know what will work sometimes. That's half the fun of testing and most of the frustration of testing.
I know ALL about frustrating! You know, with all I've done, restoring it BEFORE I reboot on the install hasn't even entered my mind! Ill give it a shot. As for which one.... all of them of course!
Ill look closer at the toolkit, maybe it will work. Ill let you know!
klloyd said:
I know ALL about frustrating! You know, with all I've done, restoring it BEFORE I reboot on the install hasn't even entered my mind! Ill give it a shot. As for which one.... all of them of course!
Ill look closer at the toolkit, maybe it will work. Ill let you know!
Click to expand...
Click to collapse
Just curious, but what version of cwm are you flashing from? It was suggested somewhere that it may depend upon if your flashing from cwm5/6 or 3/2, and I believe it may be true.
Sent from my SGH-I997 using xda app-developers app
OK, I've backed up the efs folder via the toolkit, BUT, nowhere.in there is there an option to restore it. I looked and looked! Whole rom,, different scripts, nothing about restoring the info u just backed up.
Now I went from red cwm to cm9, blue, early version. Everything was working fine until I switched from Scott's 8/31 build to cypher.(is that right?) Cyphers worked fine, but I've never been able to flash any other rom since, unless its a gingerbread rom. They all fail. The failures started with paranoid 2.0 9/6 build. I had no trouble until then. I've run every rom out there at one time or another, never had a moments trouble. Now on the other hand, I'm stuck!
BTW, I've even tried roms prior to mtd, still wipes the imei number. That is cm7, cm9 early versions.
klloyd said:
OK, I've backed up the efs folder via the toolkit, BUT, nowhere.in there is there an option to restore it. I looked and looked! Whole rom,, different scripts, nothing about restoring the info u just backed up.
Now I went from red cwm to cm9, blue, early version. Everything was working fine until I switched from Scott's 8/31 build to cypher.(is that right?) Cyphers worked fine, but I've never been able to flash any other rom since, unless its a gingerbread rom. They all fail. The failures started with paranoid 2.0 9/6 build. I had no trouble until then. I've run every rom out there at one time or another, never had a moments trouble. Now on the other hand, I'm stuck!
BTW, I've even tried roms prior to mtd, still wipes the imei number. That is cm7, cm9 early versions.
Click to expand...
Click to collapse
Here you go.
http://forum.xda-developers.com/showthread.php?t=1858842&highlight=restore+efs
I actually did the search on here... most of which pertains to the nexus and its imei being incorrect due to a GPS file. The windows file, efspro I've found is missing files, or doesn't work in.windows 7. I've not made it to trying Odin yet, but I'm gonna try tonight. The part that is confusingbme is, why can't I flash files BEFORE mtd? Something has changed...
I've been flashing things since the very day the captivate came out, I've not had trouble till now. Maybe someone can make a heimdall one.click to jb with the new filing system...? I'd pay $20 for for one!
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.
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.
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.