After flashing between a couple ROMs the other night, I noticed under 'About Phone' that my phone number is different (it says 000-000-5777). After doing some research and coming to find out about this IMEI issue, I checked to make sure that my IMEI was still in tact, which it is (and I went ahead and backed it up). The only thing that is different is my phone number isn't showing up correctly.
I can still receive calls and MMS and I am getting my 4G service. Is this something worth worrying about or should I just forget about it as long as my IMEI is still there?
Thanks ahead of time for any input.
Atwooooood said:
After flashing between a couple ROMs the other night, I noticed under 'About Phone' that my phone number is different (it says 000-000-5777). After doing some research and coming to find out about this IMEI issue, I checked to make sure that my IMEI was still in tact, which it is (and I went ahead and backed it up). The only thing that is different is my phone number isn't showing up correctly.
I can still receive calls and MMS and I am getting my 4G service. Is this something worth worrying about or should I just forget about it as long as my IMEI is still there?
Thanks ahead of time for any input.
Click to expand...
Click to collapse
Read through the following thread regarding someone with a similar issue who fixed it: http://forum.xda-developers.com/showthread.php?t=2042116
pdykstra said:
Read through the following thread regarding someone with a similar issue who fixed it: http://forum.xda-developers.com/showthread.php?t=2042116
Click to expand...
Click to collapse
I saw that thread, but was just wanting to know if my phone number not being displayed correctly is anything to worry about if I am still getting service. I didn't know if it was something that needed to be fixed or just an effect of the ROM.
Which ROM are you running? If your still getting service, then it's probably not an emergency. I'm not sure if it will cause a real problem for you or not, but personally I would fix it to be on the safe side. If you odin back to Root66, backup your data, and then enter the re-provision code you should be back to normal. Then you could re-flash whatever ROM you are currently on.
If it's not causing you any problems, then it's up to you whether or not you want to spend the time on a fix.
and iitabon
pdykstra said:
Which ROM are you running? If your still getting service, then it's probably not an emergency. I'm not sure if it will cause a real problem for you or not, but personally I would fix it to be on the safe side. If you odin back to Root66, backup your data, and then enter the re-provision code you should be back to normal. Then you could re-flash whatever ROM you are currently on.
If it's not causing you any problems, then it's up to you whether or not you want to spend the time on a fix.
Click to expand...
Click to collapse
I am running Liquid Smooth Jelly Bean REV9.
When you say root back to Root66, what exactly is Root66 if you don't mind to clarify? And also, what is the provision code?
Thanks for your help.
Atwooooood said:
I am running Liquid Smooth Jelly Bean REV9.
When you say root back to Root66, what exactly is Root66 if you don't mind to clarify? And also, what is the provision code?
Thanks for your help.
Click to expand...
Click to collapse
Root66 is the original stock, rooted image of the initial firmware that shipped with the Verizon Galaxy S3. It can be downloaded from here and must be flashed through ODIN: http://forum.xda-developers.com/showthread.php?t=1762204
The re-provision code is done by typing *2767*3855# into the dialer. It will factory reset your device, so make sure you back up your data before entering it.
I can't guarantee this will fix your issue, but has fixed other similar problems in the past. The only reason you need to go back to Root66 is because Samsung removed the re-provision code from more recent builds because it is a security issue (the code can be embedded on websites to reset your device without you opting to do so).
pdykstra said:
Root66 is the original stock, rooted image of the initial firmware that shipped with the Verizon Galaxy S3. It can be downloaded from here and must be flashed through ODIN: http://forum.xda-developers.com/showthread.php?t=1762204
The re-provision code is done by typing *2767*3855# into the dialer. It will factory reset your device, so make sure you back up your data before entering it.
I can't guarantee this will fix your issue, but has fixed other similar problems in the past. The only reason you need to go back to Root66 is because Samsung removed the re-provision code from more recent builds because it is a security issue (the code can be embedded on websites to reset your device without you opting to do so).
Click to expand...
Click to collapse
Thanks for your help. After flashing back to stock, rooting/unlocking again and flashing back to Liquid Smooth, my phone number is appearing correctly.
I guess I spoke too soon. After a reboot, I noticed that my phone number under About Phone was displayed as "Unknown", and after rebooting a second time, it was displaying the number it did before (000-000-5777). Every time I reboot my phone, I get presented with an endless activation screen that I have to either hit the physical home button or do the 4 corner tap method to get rid of. I'm starting to think that the activation screen is what is causing this issue, considering after I reflashed Liquid Smooth and wasn't presented with the activation screen and my phone number was appearing correctly.
I guess this isn't really anything to worry about since I am getting full functionality out of my phone. But if anyone happens to have any input on this issue, feel free to chime in.
That's strange.. is it possible your SIM card is going bad?
Not the sim. Try rebooting but dont unlock the screen until it has a data connection. Once it does go see if the number is still the same or if its your number
Sent from my SCH-I535 using xda app-developers app
pdykstra said:
That's strange.. is it possible your SIM card is going bad?
Click to expand...
Click to collapse
Doubt it, I've only had the phone a couple weeks.
vabeachfc3s said:
Not the sim. Try rebooting but dont unlock the screen until it has a data connection. Once it does go see if the number is still the same or if its your number
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I always let the phone acquire a connection before unlocking, but am still presented with an activation screen and the phone number is still messed up. It hasn't been affecting my data or calls so I guess there is no sense in fooling with something so minor.
Thanks to both of your for your suggestions and input.
Mine does it too man.
Sent from my SCH-I535 using xda app-developers app
Try another rom and see if you get the same problem
Sent from my SCH-I535 using xda premium
Watoy said:
Try another rom and see if you get the same problem
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
He will. Alot of defective gs3s around.
Sent from my SCH-I535 using xda app-developers app
Related
It updated OTA on it's own and was working last night. This morning I looked at my phone and it was connected. I moved it and it lost signal and hasn't gotten it since. I can't force it to connect, will get roaming but roaming in this area is emergency only.
AtomicPC said:
It updated OTA on it's own and was working last night. This morning I looked at my phone and it was connected. I moved it and it lost signal and hasn't gotten it since. I can't force it to connect, will get roaming but roaming in this area is emergency only.
Click to expand...
Click to collapse
Slight update, no APN settings are on here, won't save when I try to add them. Well it saves but then it still shows none.
Its busted, reflash
Sent from my Nexus S using xda premium
xsteven77x said:
Its busted, reflash
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Just did that. Still nothing.
Ok I've flashed 4.0.4 then CWM to 4.1.1 and nothing. Flashed 4.0.4 and nothing then flashed GB on it and nothing. I'm out of ideas.
Maybe you didn't save properly? Don't press back when done inputting everything, but press menu>save.
If that doesn't work, there's a remote possibility it's a problem with the SIM card. You might want to go to your carrier store and ask for a new one; in my experience this is usually free. Other than that, if flashing a whole new ROM doesn't fix it, I have a hard time understanding how it could be anything other than a hardware issue.
zorak950 said:
If that doesn't work, there's a remote possibility it's a problem with the SIM card. You might want to go to your carrier store and ask for a new one; in my experience this is usually free. Other than that, if flashing a whole new ROM doesn't fix it, I have a hard time understanding how it could be anything other than a hardware issue.
Click to expand...
Click to collapse
It was the sim card. I wished I would have thought of that before I wiped everything though. Oh well I got a clean install and learned a lesson. Never skip step 3...
Was running MIUI, lost my IMEI, recovered it, still will not activate. ODIN Flashed back to factory and my phone still will not activate, IMEI, MEID is showing correct in my phone info. when I call out I get the please hold for an operator to assist you. little triangle is showing. No clue what to do now. Sim card is fine, it works in my other phone.
Recovered EMEI with nvrestore, it locked up, I pulled the battery and tried restarting but it still would not boot, so I Flashed Factory rom with ODIN again and it worked, I now have data and the phone activated. Really strange.
Glad I backed the IMEI up three ways. This was the third time I have lost the IMEI and connectivity. This last time was the worst though, took me a couple hours to get the darn thing working again.
Yea last time that happened to me, I just unrooted and back to stock. Lady at the Verizon store couldn't figure it out even with new sim and they gave me a replacement no Q asked. Lol
Sent from my SCH-I535 using xda premium
fawkiPhone said:
Yea last time that happened to me, I just unrooted and back to stock. Lady at the Verizon store couldn't figure it out even with new sim and they gave me a replacement no Q asked. Lol
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
But if you got a good device new it is better to fix the IEMI than take a chance on a refurb that was bad when new and returned especially since it is so easy to prevent and fix now.
Make sense
Sent from my SCH-I535 using xda premium
Cwciwatch said:
Was running MIUI, lost my IMEI, recovered it, still will not activate. ODIN Flashed back to factory and my phone still will not activate, IMEI, MEID is showing correct in my phone info. when I call out I get the please hold for an operator to assist you. little triangle is showing. No clue what to do now. Sim card is fine, it works in my other phone.
Recovered EMEI with nvrestore, it locked up, I pulled the battery and tried restarting but it still would not boot, so I Flashed Factory rom with ODIN again and it worked, I now have data and the phone activated. Really strange.
Click to expand...
Click to collapse
Pretty annoying all the people that can't flash there phones. I'm sure it wasn't a imie issue. Next time save yourself the time and try flashing a touchwiz ROM first and then reprovision the phone by dialing *2767*3855#.
Sent from my SCH-I535 using Tapatalk 2
johnnilsson said:
Pretty annoying all the people that can't flash there phones. I'm sure it wasn't a imie issue. Next time save yourself the time and try flashing a touchwiz ROM first and then reprovision the phone by dialing *2767*3855#.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Even more annoying the someone would waist the space complaining about others instead of just sharing their knowledge and sparing us the drama. Jeesh man.
This quality message was brought to you by a guy that hangs in the woods.
johnnilsson said:
Pretty annoying all the people that can't flash there phones. I'm sure it wasn't a imie issue. Next time save yourself the time and try flashing a touchwiz ROM first and then reprovision the phone by dialing *2767*3855#.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the good information. Sorry I annoyed you.
Probably was something I missed. Originally, before I restored the meid my phone number was showing as 000-000-0120 so I am pretty sure the meid was borked, I restored using the meid repair utility but still could not get authorized, I Odin flashed back to stock but it still didn't work, I did the nvrestore then had to Oden flash a stock rom again which solved the problem and everything is working peachy now. I am sure there was an easier way but at the time I was at a loss. I thought I screwed it up.
BTW, this is my third smart phone and I been flashing roms etc almost daily for years now so I am not entirely green.
Cwciwatch said:
Thanks for the good information. Sorry I annoyed you.
Probably was something I missed. Originally, before I restored the meid my phone number was showing as 000-000-0120 so I am pretty sure the meid was borked, I restored using the meid repair utility but still could not get authorized, I Odin flashed back to stock but it still didn't work, I did the nvrestore then had to Oden flash a stock rom again which solved the problem and everything is working peachy now. I am sure there was an easier way but at the time I was at a loss. I thought I screwed it up.
BTW, this is my third smart phone and I been flashing roms etc almost daily for years now so I am not entirely green.
Click to expand...
Click to collapse
I guess u should of explained more. What's annoying is the fact that in every thread there is someone with some issue that is hashing out the same old problems that have been gone over time time and time again. Asking for questions or help when there answer is in 5000000000000000000 other threads.
Sent from my SCH-I535 using Tapatalk 2
It is annoying to see the same question asked over and over, but that is part of the reason why the forum is here. I agree that too many people ask before even bothering to do a search first.
This quality message was brought to you by a guy that hangs in the woods.
I was on Liquidsmooth ROM. Every thing was working fine until I crossed the border to Canada that is when I tried to make a call n I noticed that I had no signal no data. Went into wireless settings and under network mode it was on -home only- tried to change it but it wouldn't stick. Since then I flashed a couple other ROMs no change then I ODINed back to stock factory but still no change. When I'm in USA everything works fine when I cross into Canada I loose signal n data. I think I'm stuck in -home only- mode cause my phone is not switching into roaming. When in mobile networks settings under Roaming it says Not roaming. In Phone Status under Mobile network type it says unknown Service state -out of service-.
I have my phone #
My ERI Verizon is 5
My. IMEI is fine ( the usual #s)
My IMEISV. is 00
Can anyone help please . I cross the border 2-3 Times a week for a day or 2 n I need it to work in Canada for business n personal use. So please Help
Sent from my SCH-I510 using xda app-developers app
I also tried reflashing the radios but that didn't help either. I upgraded through OTA after Odin to stock factory still no change. Everything works fine when I'm in USA but no data and no cel signal in Canada.
And yes I'm talking about my S3. The Charge is my backup phone.
Sent from my SCH-I510 using xda app-developers app
I guess no-one has any ideas how to unfreez from -home only- wireless network and get the phone roaming.
Anyway at least some of you took the time to look at my thread thanks.
I'll be checking back once a day maybe someone figures this out b4 me thanks.
Sent from my SCH-I535 using xda app-developers app
To clarify, Everything was working fine until you flashed LiquidSmooth?
And then when you flashed other ROMs, and back to the stock ROM, you couldn't get services back to normal, which you had prior to flashing other than your stock ROM?
If the above is accurate, after you experienced your issues, did you flash back to the Nandroid you made prior to installing LiquidSmooth?
Or did you Always have issues when going into Canada?
I found this for now:
http://answers.yahoo.com/question/index?qid=20060804184552AALctoB
The only thing I can think of is try repro visioning your phone with the dialer code. I can't remember it right now, but you can find it with Google. It may not help at ask, but it's worth a shot. I've heard it does reset your phone so have a backup of any data you want to keep.
Sent from my SGS3 running Eclipse 2.1
kintwofan said:
The only thing I can think of is try repro visioning your phone with the dialer code. I can't remember it right now, but you can find it with Google. It may not help at ask, but it's worth a shot. I've heard it does reset your phone so have a backup of any data you want to keep.
Sent from my SGS3 running Eclipse 2.1
Click to expand...
Click to collapse
I don't know if that's the answer to the op's issues, but if it is, you'll find the reprovisioning code here:
https://community.verizonwireless.com/thread/777932?start=310&tstart=0
Biker1 said:
I don't know if that's the answer to the op's issues, but if it is, you'll find the reprovisioning code here:
https://community.verizonwireless.com/thread/777932?start=310&tstart=0
Click to expand...
Click to collapse
Code will reprovision but must be on TW ICS for it to work.
Biker1 said:
I don't know if that's the answer to the op's issues, but if it is, you'll find the reprovisioning code here:
https://community.verizonwireless.com/thread/777932?start=310&tstart=0
Click to expand...
Click to collapse
I didn't see the code in there.... that's a lot of reading so dial this. *2767*3855#
I'm not sure if it will fix his problem either, probably won't, but seems the op has tried everything else so it's worth a shot.
Sent from my SGS3 running Eclipse 2.1
Thank you guys . I might have to do the dialer codes cause I did try everything else
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
I didn't see the code in there.... that's a lot of reading so dial this. *2767*3855#
I'm not sure if it will fix his problem either, probably won't, but seems the op has tried everything else so it's worth a shot.
Sent from my SGS3 running Eclipse 2.1
Click to expand...
Click to collapse
It's in 311, 2nd post down.
Biker1 said:
It's in 311, 2nd post down.
Click to expand...
Click to collapse
Oh, well pulled up from my phone it gave me the mobile site which started at the first post. So that's why I didn't see it, I read a lot but not 311 posts.
Sent from my SGS3 running Eclipse 2.1
kintwofan said:
Oh, well pulled up from my phone it gave me the mobile site which started at the first post. So that's why I didn't see it, I read a lot but not 311 posts.
Sent from my SGS3 running Eclipse 2.1
Click to expand...
Click to collapse
Lol!
Nah, 300 posts is a bit much
When I went to the link via my S3, the exact page showed up with 311 on it.
I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!
In case of emergency!
...Awesome... said:
In case of emergency!
Click to expand...
Click to collapse
I dropped my s3 in some water and quickly grabbed it, and dried it off. Everything seemed to be working ok, but then i noticed that it's acting like i don't have my sd card in it when i do. My wifes card gets recognized right away when i put it in, so i think my sd card is no good. Any suggestions on how i can recover data from it?? Thanx
ryanallaire said:
I dropped my s3 in some water and quickly grabbed it, and dried it off. Everything seemed to be working ok, but then i noticed that it's acting like i don't have my sd card in it when i do. My wifes card gets recognized right away when i put it in, so i think my sd card is no good. Any suggestions on how i can recover data from it?? Thanx
Click to expand...
Click to collapse
So your SD card doesn't read but hers does? And yeah then just get a new SD card go on a computer take your files off of it and put em back on the new SD card
Sent from my SCH-I535 using Tapatalk 2
Hi,
New to the S3 and this rom. Root, flash went well, and so far, I'm loving this rom. One problem that is stumping me is this:
Using ADW launcher, have a direct dial short cut to voice mail. The voice mail contact is set up to dial *86 ,,xxxx, so with one tap, I can call vm and access messages.
However, the keyboard then becomes non responsive. I can't delete or save messages, and if I have multiple messages, can't get to the next one.
Any suggestions on how to work around this appreciated.
I'm running the 3.2 beta version of LS, and really only have this, and one other minor issue.
Thank you.
Still haven't solved this, but here's more clarification:
Phone is running LiquidSmooth 4.2.1m v2.1m beta 3.2
1. Using a 'direct dial shortcut. the rom dialer has a contact set up named voicemail, that is programmed: *86;,,XXXX. When I hit the direct dial shortcut, voicemail is dialed, xxxx is sent, and I can hear my first voicemail. The problem is the dialpad is non responsive. So, I can't save or delete the first voicemail, nor can I proceed to listen to the next one.
If I dial *86, and enter the password manually, then the dial pad works.
Even if I dial any contact withGoDialer, then, open keyboard to dial and extension, I get the stock dialer.
I drive a lot, and need as few distractions as possible. Any suggestions on how to fix this would be greatly appreciated.
Thank you.
Have u tried using a different launcher just to be sure its not hardware/ROM related it might be the launcher?
Sent from my HTC One S using Tapatalk 2
--------------If you like puzzle, tackle this---------------
I tried pretty much everything on the internet before posting here.
My stock/no root phone started bootlooping. So I used Odin and root66.tar to get it back. Everything seemed to be good. After I got 3 updates:1) 30mb, 2) 60mb and 3) JB updated OTA. After 60Mb update my phone said Samsung and shows unlocked lock. After JB update my phone bootloops again.
I though it it was a bad update and reflashed stock no root 4.0.4 and OTA did the same thing.
I tried the gs3 tool to flash the recovery and it always fails.
I would appreciate any help.... I have been dealing with this non sense for the past 24h.
...Awesome... said:
Have u tried using a different launcher just to be sure its not hardware/ROM related it might be the launcher?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Yes. I've been using ADW launcher, tried it with Nova, got the exact same result.
Alright, I'll try here. So, I'm on cleanrom 5.6. As far as I can tell everything is working, and there aren't any actual problems, but the phone doesn't know what the network is in settings and and when I drag down the notification bar it doesn't say it at the bottom. Anyone have an idea?
Sent from my SCH-I535 using xda app-developers app
MEID
does your cellular service connect? Also you are on verizon right? and did you do a dirty flash of cleanrom 5.6?
LtZKilla said:
Alright, I'll try here. So, I'm on cleanrom 5.6. As far as I can tell everything is working, and there aren't any actual problems, but the phone doesn't know what the network is in settings and and when I drag down the notification bar it doesn't say it at the bottom. Anyone have an idea?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
jwattt said:
does your cellular service connect? Also you are on verizon right? and did you do a dirty flash of cleanrom 5.6?
Click to expand...
Click to collapse
Yeah, my cell service connects and I can text and call. It just doesn't seem to have any idea that my carrier is verizon and it kinda seems odd.
Sent from my SCH-I535 using xda app-developers app
I am trying to install the stock systemui.apk file on my phone after I screwed up and flashed the wrong one, but installation always fails. I have moved the .apk to the /system/app folder and have changed the permission of the .apk but the file still won't install. What can I do?
carrier
Since you carrier wont load I believe following this tutorial with help fix your problem but check the conditions. Im not allowed to post links apparently so I attached it. I'll also flash cleanrom 5.6 and find out if its a software thing and get back to you. But it seems to me like its a MEID issue. So check the conditions in the link and if they are true I'd go that way. If not re-flash, clean install would be my suggestion. Yeah I run Cynagenmod 10.1 and it even knows I'm on Verizon. And Scott's roms always have the carrier.
LtZKilla said:
Yeah, my cell service connects and I can text and call. It just doesn't seem to have any idea that my carrier is verizon and it kinda seems odd.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
havy15 said:
So your SD card doesn't read but hers does? And yeah then just get a new SD card go on a computer take your files off of it and put em back on the new SD card
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
computer doesn't see the card at all..
I can't recall when I last had it working but my NFC completely stopped working. I have tried reverting back to absolute stock rooted nandroid. That didn't work so I Odin booted back to the original unrooted firmware. Still same problem. If I try to uncheck NFC from the more options it moves over and is immediately flipped back. I have gone into a Verizon wireless store to seek help but the guy made a sarcastic remark that his iPhone wouldn't have that problem...but I also as a few other notes I have tried hells ROM and also flashing the NFC file with the ROM which also didn't work and have tried the few NFC Google wallet fixes I have seen, also sadly no luck. I'm stubborn and don't want to give up if anyone knows if there is a possible fix, hope you can possibly help!
Sent from my SCH-I535 using xda app-developers app
replacement?
I think you may have a faulty chip. Also is your battery NFC capable? But to be honest Verizon will replace it for free if your under the 1 year warranty and don't have water damage or anything like that. Because if it doesn't work on the stock rom it's most likely a hardware problem in this case. So I would contact your carrier about that.
CeeMillz said:
I can't recall when I last had it working but my NFC completely stopped working. I have tried reverting back to absolute stock rooted nandroid. That didn't work so I Odin booted back to the original unrooted firmware. Still same problem. If I try to uncheck NFC from the more options it moves over and is immediately flipped back. I have gone into a Verizon wireless store to seek help but the guy made a sarcastic remark that his iPhone wouldn't have that problem...but I also as a few other notes I have tried hells ROM and also flashing the NFC file with the ROM which also didn't work and have tried the few NFC Google wallet fixes I have seen, also sadly no luck. I'm stubborn and don't want to give up if anyone knows if there is a possible fix, hope you can possibly help!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have the stock battery and when I did call Verizon the first time they wanted me to contact Samsung first then get back to them so I figured i'd bring it here. It had worked before so I was wondering if maybe it fried somehow? Phone has never been dropped, no water damage, watch because I said that i'll drop it in 5 minutes and shatter my screen I guess I'll just try Samsung tomorrow and see what they have to say.
nfc
Actually I just thought of something else to try. Have you gone in and force quit nfc and cleared the app data? That may resolve the problem. Nfc will be under all apps and it is named nfc service.
CeeMillz said:
I have the stock battery and when I did call Verizon the first time they wanted me to contact Samsung first then get back to them so I figured i'd bring it here. It had worked before so I was wondering if maybe it fried somehow? Phone has never been dropped, no water damage, watch because I said that i'll drop it in 5 minutes and shatter my screen I guess I'll just try Samsung tomorrow and see what they have to say.
Click to expand...
Click to collapse
jwattt said:
Actually I just thought of something else to try. Have you gone in and force quit nfc and cleared the app data? That may resolve the problem. Nfc will be under all apps and it is named nfc service.
Click to expand...
Click to collapse
Good idea, just tried it and it didn't do anything. Also tried that, rebooted recovery, wiped dalvick and cache fixed permissions then tried again with no luck. =/
nfc
Are you using a non stock kernel? Also when you went back to stock did you erase everything on the phone?
CeeMillz said:
Good idea, just tried it and it didn't do anything. Also tried that, rebooted recovery, wiped dalvick and cache fixed permissions then tried again with no luck. =/
Click to expand...
Click to collapse
I can't send text or phone calls after CWM recovery flash.
I initially rooted my i535 sg3 using this method http://forum.xda-developers.com/showthread.php?t=1840030
I then flashed 4.2.2 Pacman. Used this for a few days and everything was ok but battery life was horrible so I flashed, I think CleanRom, then Liquid RC1. I'm not sure where in the process of flashing but I noticed that my reception was weak compared to stock and then I couldn't send outgoing text or calls all together. I've searched everywhere and I have seen similar issues/symptoms but non of the fixes have worked for me. Here's my current setup.
Model SCH-I535
Android Version 4.1.2
Baseband I535VRBMA2
Kernal 3.0.30-861013
Build JZO54K.I535VRBMA2
Status
Netowork = Unknown
Mobile Network Type = 1xRTT.6
Service State = In Service
Roaming = Roaming
Mobile Netowrk State = Disconnected
My Phone # = 000-000-8561 (last 4 aren't even correct)
IMEI looks correct
IP Address = Unavailable
Thanks for any help/advice.
Pozman1 said:
I can't send text or phone calls after CWM recovery flash.
I initially rooted my i535 sg3 using this method http://forum.xda-developers.com/showthread.php?t=1840030
I then flashed 4.2.2 Pacman. Used this for a few days and everything was ok but battery life was horrible so I flashed, I think CleanRom, then Liquid RC1. I'm not sure where in the process of flashing but I noticed that my reception was weak compared to stock and then I couldn't send outgoing text or calls all together. I've searched everywhere and I have seen similar issues/symptoms but non of the fixes have worked for me. Here's my current setup.
Model SCH-I535
Android Version 4.1.2
Baseband I535VRBMA2
Kernal 3.0.30-861013
Build JZO54K.I535VRBMA2
Status
Netowork = Unknown
Mobile Network Type = 1xRTT.6
Service State = In Service
Roaming = Roaming
Mobile Netowrk State = Disconnected
My Phone # = 000-000-8561 (last 4 aren't even correct)
IMEI looks correct
IP Address = Unavailable
Thanks for any help/advice.
Click to expand...
Click to collapse
Have you tried odining back to stock? Somewhere along the way from AOSP back to TW you might have lost/changed some sys data.
Feels like it lost the IMEI, even if it looks correct. Getting stuck on roaming and possibly the weird phone number may mean that's what went wrong.
Sent from my SCH-I535 using xda app-developers app
sworld said:
Feels like it lost the IMEI, even if it looks correct. Getting stuck on roaming and possibly the weird phone number may mean that's what went wrong.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I was able to Odin back to a stock unrooted 4.0.4 rom but it did not fix the issue. Is there a good way to restore IMEI?
Did you try to reprovision after you used Odin to get back to stock 4.04? A lot of people have had success after doing that, including myself. Be warned, it will completely wipe your phone.
HHF2 said:
Did you try to reprovision after you used Odin to get back to stock 4.04? A lot of people have had success after doing that, including myself. Be warned, it will completely wipe your phone.
Click to expand...
Click to collapse
I'm somewhat new to this and have no clue what "Reprovision" does. I found this comment on one post "reprovision your device with dialer code *2767*3855#". When I dialed this it said that when roaming that you have to use an area code and then hangs up? I really hope I don't have to dish out $600 to Verizon! I'm at a loss right not.
You need to enable the hidden menu before you can use the reprovision code. Dial *#22745927 and enable the hidden menu. Now the reprovision code should work. You shouldn't have to hit send at the end of the code. It should work as soon as you enter the last digit. This is assuming you are still on ICS.
Pozman1 said:
I'm somewhat new to this and have no clue what "Reprovision" does. I found this comment on one post "reprovision your device with dialer code *2767*3855#". When I dialed this it said that when roaming that you have to use an area code and then hangs up? I really hope I don't have to dish out $600 to Verizon! I'm at a loss right not.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2066731
I think I found a thread that has solved this for me.
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/show....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.
OMG THANK YOU GUYS!! This thread saved my sanity! I had flashed the latest MIUI 4.1.2 and wasn't a big fan so I flashed my backup and *POOF* no data! I had no clue how it happened (still don't fully understand it), tried every basic "go-to fix" in the book, and scoured the forums for two days without luck. The suggestions in Pozman1's last thread post to flash back to the VRALG1 4.0.4 ROM and the I535VRLHE radio did the trick! The only thing I had to do differently was use the *#7780# Factory Reset Code instead of the *2767*3855# Reprovisioning Code, for whatever reason that code just wouldn't work. Anyway, thanks again!
Thanks!
I spent all last night and most of this morning trying to figure out what was wrong with my phone. I was not connecting to the network and went through the forums searching for the solution to my problem. I odin'ed, flashed, prayed, hoped and then did it all over again all the way back to 4.04. until I landed here.
I was finally ready to give up, so I went to the Verizon site to see if my IMEI was listed and if it matched my phone. Both my phone and my wife's phone were different than the phones we actually have. I got on chat with verizon support and they fixed it right up. I got my 4g back. Now, I'm updating my way back up to the present.
I've been able to solve every problem I've had by lurking/searching these forums. I've been doing this for a couple years now. I really should have registered and started thanking people a long time ago. I have bought apk's off of google play and donated some beer money, but probably not enough. After I post this, I'll take some time and spread the thanks I owe.
I've registered and planted this response here so that if someone else is having the same problem, they might think to go check their account and make sure they've actually got the same phone their carrier thinks they do. Sometimes, it helps to start with the simple stuff.
Thanks to everyone!