[Q] Stuck in roam no call/text out but can receive incoming text - Verizon Samsung Galaxy S III

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!

Related

JB 4.1.1 Won't connect to tmobile towers

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

[Q] Phone will will not activate. IMEI is correct, Sim card is fine.

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.

[Q] Phone number is different but IMEI is normal

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

[Q] Stumped. Please Help!

Alright, to begin. About a month ago I lost my GPS. Meaning, my phone could not locate itself. Move up to the end of last week...I was unable to send text messages, call out or receive calls. I WAS able to receive text messages. Also, I could use my mobile data (i.e. Internet). Then, I lost ALL capabilities and the phone went to asking me if I wanted to switch to GLOBAL ROAMING. Still, at this point I could ODIN flash to stock. However, I could not ROOT the phone. Even with flashing back to stock (unrooting), the phone would not call, or text, etc...Okay, still with me? So, yesterday, I took the phone to the local Verizon Corporate store to have them look at it. A new SIM card did not fix the problem. In fact, when he booted the phone, the boot and splash screen both came up with a picture of a big LOCK (that was unlocked) and the word "CUSTOM". He looked at us and said, "That's not supposed to be there.". It never was until that time (mind you, I had unrooted). The phone wouldn't even boot to the VZW stock recovery. He was awesome to work with and we did so for over an hour. He was going to replace the phone with a new one under insurance (even though I don't have insurance on the phone). But the phone was not in the system. They couldn't find it. "Like it doesn't exist". So, today I am still messing with it and have been all over the internet looking for a solution. I've ODIN'd the stupid thing so many times in the last two days. NOW, I DON'T have the big un-locked LOCK or the "CUSTOM" anymore, but I can't get past the setup screen because the phone is ROAMING! It will ask which language, then, at the next screen, it tells me to wait while it connects to Verizon Wireless and activates itself. At this point, the phone will make a phone call, ON ITS OWN, and I listen to people telling me that I may be eligible for a $100 gift card as well as other advertisements. I used to be able to pull down the notification bar and setup my wifi. Now, I can't do that.
I've tried every stock ROM available all the way back to 4.0.4. At first, that's what I would do and then, just apply the OTAs until i reached 4.1.2. Now, I can't even get that far.
I'm sure I've forgotten some things, but please ask away if that will help clear anything up. I've never had any problems with this device. Could it be a virus? Or is it doomed for the recycler? I have no idea what to do. Thanks.
Also, I remembered, when I was able to see my phone's info it showed I was connected to the network and everything looked as it should and would, normally. I still couldn't send texts, call, etc...on Verizon's customer representative end, they would also say that it would look like the phone was trying to do something but never would.
When I would request my IMEI#, it checked out fine. However, when I would use the dialer for the IMEI check, I would get the IMEI# followed by a /01 or /02. Not sure what that means, but thought I'd throw that out there, as well. Thanks
Now, when I'm in the aforementioned set up screen, my phone direct-calls Alltel. "Thank you for calling Alltel". WTH.
Sent from my GT-P3110 using xda premium
just for a baseline where is the phone at now? As in what Rom, base(modem), bootloader locked/unlocked, kernel, prl, eri, imei still there not messed up?
Sent from my SCH-I535 using Tapatalk 4 Beta
Your phone is shot. Same thing happened to my original s3. Started with gps, then started losing internet, and messages not working then making calls started to go. I tried everything I could. I had to call Verizon and get them to send me a replacement.
Sent from my SCH-I535 using xda premium
bbolton_98 said:
just for a baseline where is the phone at now? As in what Rom, base(modem), bootloader locked/unlocked, kernel, prl, eri, imei still there not messed up?
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi. Unfortunately, I couldn't give the specifics because I don't really know. Other than, the last flash I did was Odin back to stock (un-root) and do all the OTA updates (up to 4.1.2). So, whatever all the stock, non-rooted S3s are running. Sorry I couldn't give more info. Thanks.
Sent from my GT-P3110 using Tapatalk 2
bbqsfire said:
Your phone is shot. Same thing happened to my original s3. Started with gps, then started losing internet, and messages not working then making calls started to go. I tried everything I could. I had to call Verizon and get them to send me a replacement.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Thanks. Yeah, I was on the phone from 11pm last night until 1am this morning with Verizon and they couldn't get it working. Put in another "network fix" ticket but haven't heard back. Looks hopeless. My contract is up and I am really looking forward to the S4, but money is tight and I was going to wait a bit before that purchase. I was using an old Samsung SCH-U900 Flipshot as my backup. I don't have to tell anyone, but that sucked. Now, I can't even use that because they need the line clear for the work order. So, I'm helpless. How the heck did I survive before cell phones?!
Sent from my GT-P3110 using Tapatalk 2
Welp, as a follow up, sent the phone off to Samsung. They sent it back with an updated PRL...and it WORKS!!! :good:
bbolton_98 said:
Thanks for the update, good to know to watch for prl. Glad you got it fixed.
Cruzin' tha GS3 w/Synergy Rom & Anthrax Kernel
Click to expand...
Click to collapse
Hey, no problem and thanks. I was going crazy with the old Droid X. Anyway, because of the outcome, I thought it would be a good reason to post and maybe help others. ORIGINALLY, when we first called Verizon, that's the first thing I wanted them to try. Or at least let me try. I just couldn't get past the language set up screen and the phone making calls on its own. All they would do is a factory reset. Still not sure why the phone went berserk and changed up on me. Oh well, it's back now and I couldn't be happier.

[Q] No Signal/Emergency Service Only after ODINing stock rom

Hi, guys.
I recently had my gps abruptly go out and did a bunch of stuff to my phone in an attempt to rectify it.
to include:
running "gps sgtatus" tools and recalibrating/downloading agps data
tightening all the screws on the back of the phone
inserting a piece of paper below the contact plate for the gps antenna
restoring back to a stock 4.1.2 rom via odin just to access the stupid samsung service mode and doing a nv rebuild
none of these worked. i've basically accepted that my phone will never navigate me anywhere ever again.
HOWEVER, now my signal is going crazy.
Ever since i did the odin flash, I've had:
dropped coverage to "no signal" or "emergency calls only" every five minutes or so with no consistency
virtually unusable sms, with a single push maybe once every 10 minutes
anytime i do attempt to flash something fresh, a signal outage of at least five minutes ocurrs during the initial configuration of the rom
what i've attempted to do to rectify this so far is:
reinstall just about every nandroid restore package i've made since before the odin flash
install every rom i have on my phone, anywhere from JB to KK and touchwiz to aosp
install every baseband i could find, to include MB1, MF1, and ML1 (via recovery .zips)
what the heck can i do?
everything is so unreliable that i basically have a glorified wifi-only device about 80% of the time.
The phone stats:
SCHI535
VRBMF1 modem (had ML1 at one point via recovery .zip, but reverted back)
ParanoidAndroid 4.4 BETA1
Sounds like to me you just a got a bad egg. How long have you had the phone? Honestly with all you have done so far I would just Odin stock, reset flash counter, lock the bootloader and get a replacement from VZW. This sounds like a hardware failure.
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
Sounds like to me you just a got a bad egg. How long have you had the phone? Honestly with all you have done so far I would just Odin stock, reset flash counter, lock the bootloader and get a replacement from VZW. This sounds like a hardware failure.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
i've had it since last april. like i said, i'm okay with the gps not working for now. if i could just get the thing reliable for the next week, that would be great.
i highly doubt multiple hardware components would fail so close to one another, especially with me seeing the side effects immediately after flashing via odin.
how about this:
i'm trying to eliminate all variables, so i'll go as far back to stock as possible.
would going all the way back to 4.0.4 VRALG1 with a locked bootloader remove any software issues?
myleskeller said:
i've had it since last april. like i said, i'm okay with the gps not working for now. if i could just get the thing reliable for the next week, that would be great.
i highly doubt multiple hardware components would fail so close to one another, especially with me seeing the side effects immediately after flashing via odin.
how about this:
i'm trying to eliminate all variables, so i'll go as far back to stock as possible.
would going all the way back to 4.0.4 VRALG1 with a locked bootloader remove any software issues?
Click to expand...
Click to collapse
With all due respect, if you go back to stock and the problem Is not fixed its a hardware problem. Simple as that. And no going back to 4.0.4 will not help. Also seeing these problems arise right after flashing stock proves its not a software problem because if it was it would be fixed by flashing stock.
Sent from my SCH-I535 using Tapatalk
Sent from my SCH-I535 using Tapatalk
well, i was able to discover that my imei somehow got wiped, because i never noticed that i could never actually make calls and had the symptoms of this thread.
i followed the instructions in this post, and now i don't even have 4g anymore. 100% tablet mode.
*digs self further into hole*
disregard. i had to check a bunch of boxes in the mobile network options to re-enable data for some reason. basic call functionality still inoperable.
myleskeller said:
well, i was able to discover that my imei somehow got wiped, because i never noticed that i could never actually make calls and had the symptoms of this thread.
i followed the instructions in this post, and now i don't even have 4g anymore. 100% tablet mode.
*digs self further into hole*
disregard. i had to check a bunch of boxes in the mobile network options to re-enable data for some reason. basic call functionality still inoperable.
Click to expand...
Click to collapse
do you have a backup of your IMEI? Even if you restored your IMEI you would still have GPS issues I would think.
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
do you have a backup of your IMEI? Even if you restored your IMEI you would still have GPS issues I would think.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
i did not have/make a backup, but i think i got the IMEI straightened out.
and i'm not focused on the gps issues currently. i just need to make/receive calls.
i would like to reiterate that, at this time, my phone does the following:
has a fully functioning LTE connection any time that i would ordinarily have one
receives sms and mms with absolutely no delay
rarely if ever sends sms/mms at all
makes emergency (911) calls with no issue
will dial out for ordinary calls, but never actually connects or begins ringing
this makes me think it couldn't be hardware failure if the antenna still works for functions like sms reception and outgoing emergency calls.
is there anything else i could try?
myleskeller said:
i did not have/make a backup, but i think i got the IMEI straightened out.
and i'm not focused on the gps issues currently. i just need to make/receive calls.
i would like to reiterate that, at this time, my phone does the following:
has a fully functioning LTE connection any time that i would ordinarily have one
receives sms and mms with absolutely no delay
rarely if ever sends sms/mms at all
makes emergency (911) calls with no issue
will dial out for ordinary calls, but never actually connects or begins ringing
this makes me think it couldn't be hardware failure if the antenna still works for functions like sms reception and outgoing emergency calls.
is there anything else i could try?
Click to expand...
Click to collapse
What is your PRL an SV #

Categories

Resources