First, I'd like to say that I have seen other threads on this topic and tried but failed.
I've gone through different roms, stock roms, stock radio, Odin, etc. I attempted to download ADB but it doesn't work on my windows 8 and I've just gone through so many problems that I can't take it anymore. I need help.
I have a Samsung Galaxy S3 i535 on the Verizon network.
It started with me trying to root my phone
I used the Odin method and CM 10.1 with Clockwork mod.
Phone booted up and everything and had Superuser but kept getting errors about process.android failing/closing as well as other processes.
I needed Gapps so I tried to flash the one for CM 10.1 and the installation when I boot it up would always fail due to network error. It showed up every reboot so to get rid of the endless failing I tried to change the rom in recovery.
Changing to Synergy Mod
As I went through the installer for Synergy, everytime it got to the wiping data/cache portion it rebooted the phone and failed to install.
BUT, when I went back to CM 10.1 the Gapps screen had finally vanished.
At this point
I had signal but could not send out texts or calls and I had no data connectivity.
Stock Attempts
Tried multiple attempts on this site as well as others, mostly having to use Odin. As of now, I'm in Android 4.0.4 stock rom and recovery with call/text ability, stuck in roaming (little R/triangle above bars), Google Play not opening, and no ability to update software due to no network connection.
Please, I don't know what else to do. I'm going insane and am losing hope, I need the help of you beautiful people.
I'm in the Air Force and it's hard to spend this much time trying to fix this issue, a lot of things are tied to my phone with it being my only communication. I'm okay with rooting my phone again but I need to get the 4G data working first. Thank you in advance.
I'll try anything, even if I have before, and i'll post the results. Any help is appreciated.
If you're completely stock on 4.0.4 try reprovisioning your phone. Open dialer and type this *2767*3855#
Sent from my SCH-I535 using Tapatalk 4
Related
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
Why don't you try to Odin a pre-rooted Verizon stock can be found here http://forum.xda-developers.com/showthread.php?t=1984436 to see if it addressed both our your issues?
I just had some major issues with this as well. There is something wrong with the nightly versions of CM 10.1.
Like you - I flashed CM 10.1 12/18 and found that my data was not working. I then searched this forum and found that other users were having the no data issue as well. I decided that I would do the same and flash back to an earlier CM 10 release from December, but the update did not go as expected. Due to going 10.1 to 10 I had to wipe data/cache/dalvik. At this point I got CM 10 reinstalled, but the phone came up with NO cell coverage. I went to System Settings -> About -> Status and found that the phone was no longer registering my cellular network (Verizon) or phone number. My IMEI data was dead.
Luckily in my case I had already made backups of my IMEI data per this post: http://forum.xda-developers.com/showthread.php?t=1852255
I restored my IMEI and reflashed CM 10 12/16. Everything is now working as expected. Your issue sounds identical to mine - I just spent half the day fighting with the exact same issue. I definitely learned my lesson about staying so current with the NIGHTLY builds for day-to-day non-dev use. I knew it before, it just never bit me like this.
Anyways, I hope this information helps you somewhat. Good luck!
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
Hello, this is my first time posting on the forums here.
Recently I flashed the latest version of MIUI on my Verizon Galaxy s3. I decided that I preferred my previous rom; Jelly Bean's Build 10, and I restored it to my phone. After restoring the rom, I got a message saying that I was roaming, even though I am still in the same area where service has been working flawlessly. The first thing I tried to do was change the network type under network settings to LTE/CDMA but that choice was already selected. Thinking that I had no other options, I restored the stock rom that I had backed up on my device and I got the same issue. Thinking I could just send the phone back to Verizon, I unrooted the phone using the built in unroot tool in SuperSu Pro. I am now unrooted, but forgot to reflash the stock recovery (I am still using TWRP). I am just wondering what I should do about the issue, and if I were to send it back to verizon, would they be able to tell that I have a custom recovery. Sorry for being a noob and any help would be much appreciated.
Update: I rolled back to my rooted stock ROM and I used triangle away to reset the custom flash counter. I have also reflashed the stock recovery onto my device. Even though my phone appears to be unmodified I still have the same issue.
Sent from my SCH-I535 using xda app-developers app
there are SOOO many threads about how to fix the roaming issue it's not even funny....
^^^^^what he said!
This happened to me and what I had to do was ODIN to stock ICS rom and enter the code to reprovision sim. Google/forum search is your friend.
This is why Verizon locks down their phones! People who are not willing to search for a way to fix something that they screwed up is unacceptable. The bad thing is this phone is completely fixable with very little effort! Some people should not be allowed to flash anything!
I've dealing with so many issues ever since the DroidX so if there is one thing I've learned is there is ALWAYS a fix you may just need to do a little search if you can't find the resources your looking for on any of forums a simple google search will help you out.
So I finally took the plunge to AOSP since I have my note 2 to run stable. First thing I noticed was that the camera got a "can't connect to the camera" error. Fixed permissions, wiped multiple times, tried a couple different AOSP roms and nothing, so I looked deeper and found some file replacements for the data folders, tried that and still nothing. Wiped again flashed a stock rooted image and still nothing, so last resort was 2 different stock rooted and not-rooted images through ODIN. Successful flashes of both and still no camera.
I am stumped i thought my fail safe ODIN would work but it didn't if anyone has any suggestions I would greatly appreciate it.
p.s. my bootloder is unlocked.
::UPDATE::
Ok so after continuing the troubleshoot finally stumbled upon something. After restoring a stock ODIN of ICS from when i first got the phone I let Verizon run through and do its update and after it finished VOILA my camera's working. I honestly don't know how it happened but nothing else had worked, now i have to go through and unlock root and get a custom ROM again. hopefully this can help someone if this happens to them.
This has happened to me several times and I am seeing that other people are running into this problem with no fix found.
Everytime I try to install CM10.2 onto my xt926 I can never get past the unlocked bootloader warning screen after a reboot. I can still access CWM which is the recovery I'm using. I have tried clearing cache, data, factory reset, fixing permissions, reflashing the rom. The only way to get a working phone again is to flash stock 4.1.2 using RSD.
Then I remembered seeing an article a while ago saying that their were two versions of an OTA update for Razr HDs because for some reason their were slight differences between some phones, hardware wise.
Could this be the reason for these random phones not accepting CM10.2 installs?
Also if anyone has any ideas to get past this. I read someone had luck toggling bluetooth on and off for some reason but it didn't help me. I'm at a loss here and would love to play with Android 4.3 but I guess its just not in the cards...
ive got the same problem to i finally decided to get rid of safestrap and unlock my phone. now im stuck on stock rom because no roms will work after a reboot. theres two diferent stock 4.1.2 firmware files. one says mr4 the other one says mr2 anyone know the diference?
Not sure. I just use the RazrHD Utility 1.21 for that, its a lot easier. Also I have heard that 10.1 may work for us, just not 10.2 for whatever reason
1. TWRP is up
2. baseband G920R4TYU2BOF7/HW version G9020R4.02
3. No Mods
4. Rooted
So I tried flashing the Vader ROM, I was getting boot loops at the language selection screen. I go back and restore from backups my original stuff. Boot back up and now I'm getting the lovely "process.com.google.gapps has stopped" error. I'm assuming that I may need to find gapps for 5.1.1? I also tried flashing XtreStoLite ROM with the Aroma add on. Everything seemed to be working great with the exception of the data and no signal, which I am to assume is because I'm not using the correct carrier-specific stuff.
Go to download the stock ROM for my phone, and I keep getting an error as well. Odin won't flash it. One thing that I noticed is that the stock rom was 5.0.2 where when I got the phone 3 days ago it came with 5.1.1.
At this point, I'd like to be able to get it back to stock if possible. I jumped the gun and started flashing all sorts of things without checking to see if it would even for with a USCC galaxy s6. Any help would be much appreciated.
UPDATE: Problem seems to have resolved itself with the last restore. no more problems with gapps. However I am curious as to if any of these custom roms will work with a USCC variant