I tried to install the latest and greatest version of cyanogenmod this morning but once it got to the activating part, it would not activate. I tried it a couple times, rebooted, wiped, installed and tried again, but nothing was working.
So, I had enough and wiped everything and restored my previous ROM's backup (CleanROM).
But now, even CleanROM can't connect to the mobile network. When I try to do the *228 thing, I first got an error something about a invalid SIM card. So, I rebooted and now the error message says "A Verizon Wireless SIM card has activated your service and updated your phone's roaming capabilities".
What's weird about that is that it doesn't even call, just pops up that message and I still have no network!
Could it be possible that have the wrong radio now? Anyone know what it's supposed to be and where to download the correct one?
Right now: I535VRLG7
What the f happened? What did cyanogenmod do to my phone??? Please help, my phone is dead in the water at this point.
Was it 10.1.0.1? I tried flashing it myself and data would not work either, first time ever happened to me since running CM. Apparently others are having issues with it as well reading the thread on the dev section. I restored my backup of 10.1.0 and it was fine again thankfully. Also you aren't supposed to *228 on a 4G phone, might want to do a search but others have said that can mess up your phone as well.
NeoMagus said:
Was it 10.1.0.1? I tried flashing it myself and data would not work either, first time ever happened to me since running CM. Apparently others are having issues with it as well reading the thread on the dev section. I restored my backup of 10.1.0 and it was fine again thankfully. Also you aren't supposed to *228 on a 4G phone, might want to do a search but others have said that can mess up your phone as well.
Click to expand...
Click to collapse
Yes, that's the version I was trying to install.
I created a backup of CleanROM that I was running before flashing, but that's not working now either. Network is dead for me.
I am having the exact same issue. Flashed the newest "stable" build of CM 10 and now the phone won't activate. Flashed CM10 RC5 and phone won't activate. Installed my backup I made before I flashed and it will not make/receive calls either. I tried searching the g+ community but did not see anything.:crying:
Jerniganc said:
I am having the exact same issue. Flashed the newest "stable" build of CM 10 and now the phone won't activate. Flashed CM10 RC5 and phone won't activate. Installed my backup I made before I flashed and it will not make/receive calls either. I tried searching the g+ community but did not see anything.:crying:
Click to expand...
Click to collapse
I've tried a bunch of stuff so far, but no luck fixing this. I'm waiting for some files to copy and I'm going to try again. This sucks. I'll post if I have any luck with a fix.
I'm having the same issue. What Baseband are you guys running?
Laxidasical said:
I'm having the same issue. What Baseband are you guys running?
Click to expand...
Click to collapse
I'm on I535VRBMB1, but I was on I535VRLG7 for some reason. Upgrading did not help.
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
I hope I don't have to do that also. I posted in the cm g+ community and I'm waiting on an answer atm. Jumped in irc chat but got no help.
Sent from my Nexus 7 using xda premium
---------- Post added at 06:48 PM ---------- Previous post was at 06:36 PM ----------
ned4spd8874 said:
I've tried a bunch of stuff so far, but no luck fixing this. I'm waiting for some files to copy and I'm going to try again. This sucks. I'll post if I have any luck with a fix.
Click to expand...
Click to collapse
ned4spd8874 said:
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
Click to expand...
Click to collapse
Found this post on G+. Looks like it is a known issue that a radio didn't make it into the build.
https://plus.google.com/110116306685366816729/posts/2wnDGwd9UtX
Jerniganc said:
Found this post on G+. Looks like it is a known issue that a radio didn't make it into the build.
https://plus.google.com/110116306685366816729/posts/2wnDGwd9UtX
Click to expand...
Click to collapse
But I've flashed the radio and it didn't work for me. I tried two different ones and neither worked.
ned4spd8874 said:
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
Click to expand...
Click to collapse
No need to take your phone back to verizon.....The way to fix it is to Odin back to I535VRALF2. Once stock dial *2767*3855# let it do it's thing when it finishes reboot. After that 4G will be back. Re root and flash CM 10.1.0 NOT 10.1.0.1
Well an update on this. I flashed MIUIv5 found here http://forum.xda-developers.com/showthread.php?t=2232800 and it booted up and worked like a champ. From there I booted back into CWM and wiped, etc and installed a fresh RC5 and gapps. When the phone booted up the phone would take calls but would force close. From here I booted back into CWM, again wiped and then installed my RC5 backup I made this morning that was working and crossed my fingers. Well when the phone booted up it is working 100%!
I guess my question is what did 10.1.0.1 break that a flash to MIUIv5 fix?
Same issue. I had to wipe everything, format everything (maybe wasn't needed), flashed the newest nightly, latest baseband (something something F1), and gApps of course. I then had to check the "mobile network" settings and change it to SIM card (instead of NV) then reboot, and it worked.
The "stable" builds have been less stable than the nightlies lately, dunno why...
i'm also having this issue guys, I've noticed that my imei is 0. I've tried punching in the codes to get the utility, but can't get anything working...totally lost
RESOLVED!
It was a PITA, but I got 4G back with CM!
This is how I did it, but be forewarned that your device will be wiped, and it will not be a quick fix.
I first used this post (Section 5) to Odin back to stock.:
http://forum.xda-developers.com/showthread.php?t=1762709
Once I was back to stock, the network was still not working. So I dialed "*2767*3855#", it did something, rebooted and then 4G worked!
After that, I was able to follow the same guide from above (Section 1) to root the device, unlock the bootloader and install a recovery.
Once I was at that point, I installed CM from recovery. I had wanted to install the cm stable version 10.1.0, however I failed to copy that to my SD card before I started this whole process.
I had just moved and don't have many of my "tools" (i.e. sd adapters), so I couldn't even download it on my computer and copy it over. Oh, I also performed a factory wipe at this point as well as format the davlik and system...oops. So, yeah, couldn't simply boot it back up easily to copy the files over...got ahead of myself.
Anyways, I kept my fingers crossed and installed the only one that was on the sd card which was the nightly from 6/29. The good news is that worked!
I have since installed the latest nightly (6/30), because why the heck not? I was already on the previous, so it "shouldn't" hurt, right????
Nope, didn't hurt!
So, now I am running the latest nightly with full network access!
Whew, what a pain! Hope this helps you guys!
ned4spd8874 said:
RESOLVED!
It was a PITA, but I got 4G back with CM!
This is how I did it, but be forewarned that your device will be wiped, and it will not be a quick fix.
I first used this post (Section 5) to Odin back to stock.:
http://forum.xda-developers.com/showthread.php?t=1762709
Once I was back to stock, the network was still not working. So I dialed "*2767*3855#", it did something, rebooted and then 4G worked!
After that, I was able to follow the same guide from above (Section 1) to root the device, unlock the bootloader and install a recovery.
Once I was at that point, I installed CM from recovery. I had wanted to install the cm stable version 10.1.0, however I failed to copy that to my SD card before I started this whole process.
I had just moved and don't have many of my "tools" (i.e. sd adapters), so I couldn't even download it on my computer and copy it over. Oh, I also performed a factory wipe at this point as well as format the davlik and system...oops. So, yeah, couldn't simply boot it back up easily to copy the files over...got ahead of myself.
Anyways, I kept my fingers crossed and installed the only one that was on the sd card which was the nightly from 6/29. The good news is that worked!
I have since installed the latest nightly (6/30), because why the heck not? I was already on the previous, so it "shouldn't" hurt, right????
Nope, didn't hurt!
So, now I am running the latest nightly with full network access!
Whew, what a pain! Hope this helps you guys!
Click to expand...
Click to collapse
Yes, this just worked for me..however I look to be roaming completely when still in Stock
luniz7 said:
No need to take your phone back to verizon.....The way to fix it is to Odin back to I535VRALF2. Once stock dial *2767*3855# let it do it's thing when it finishes reboot. After that 4G will be back. Re root and flash CM 10.1.0 NOT 10.1.0.1
Click to expand...
Click to collapse
This worked for me.
Thanks!
I'm on vacation and tried to flash 10.1.0.1 and got hosed on the the radio connection. Nothing would work. Found an old nightly, 6/21 I believe, on my external SD card. Flashed that bad boy and I'm up and running again. Will do more trouble shooting when I get home in a few weeks and have my PC in front of me.
Sent from my SCH-I535 using Tapatalk 2
Back to RC5
I had a similar issue, upgraded to 10.1.01 and lost all data connectivity. Wiped clean and tried to upgrade again, then I could not get past the network activation screen.
Wiped and went back to a backup of RC5 and it restarted with less issues, but I still needed to go and correct the Mobile Network RUIM/SIM settings before I got data back.
RC5 has been solid, so I'm going to stick to it until there's a fix for 10.1.01.
this didnt work for me
Related
My brother has had his Shift for over a month now and just recently it stopped making/receiving calls and texts.
The first day he got it, I rooted it (it had 2.2), put CM7 on it, and x99 kernel. This is the same setup my Shift, and my friend's Shift have.
Whenever he tries to make a call it says "Your authentication code could not be verified"
Should I hard reset this, call Sprint, un-root, or what?
Thanks.
PS: I rebooted it, and had it shut off for 30min before turning it back on. Should I do a battery pull? That would be slightly tricky since he has the Otter Box case on it.
You don't have to unroot. Just flash a Sense based Rom. Update your Profile and PRL. Then flash back to CM7. Don't Nand back when your done updating your PRL and Profile. That will just put you back where you were.
prboy1969 said:
You don't have to unroot. Just flash a Sense based Rom. Update your Profile and PRL. Then flash back to CM7. Don't Nand back when your done updating your PRL and Profile. That will just put you back where you were.
Click to expand...
Click to collapse
Now when I flash a Sense ROM, I need to wipe the data and cache right? Update the stuff, then flash CM7, gapps, and kernel right?
Just wanna make sure.
doratheconquistadora said:
Now when I flash a Sense ROM, I need to wipe the data and cache right? Update the stuff, then flash CM7, gapps, and kernel right?
Just wanna make sure.
Click to expand...
Click to collapse
Correct.. Do a full wipe, data/cache/dalvik (can't hurt to do it multiple times) Flash a Sense ROM and update PRL and Profile. Wipe EVERYTHING again and flash CM7, gapps and kernel.
Ok. So I downloaded the lastest Mik ROM
Wiped the data and cache. Used CWM to install Mik from the SD card.
Updated the Profile and the PRL.
Made a call to my Shift, rung once then gave me the same "Your authentication code could not be verified message again."
What do I need to do?
doratheconquistadora said:
Ok. So I downloaded the lastest Mik ROM
Wiped the data and cache. Used CWM to install Mik from the SD card.
Updated the Profile and the PRL.
Made a call to my Shift, rung once then gave me the same "Your authentication code could not be verified message again."
What do I need to do?
Click to expand...
Click to collapse
While your still on a Sense ROM, call Sprint and have them refresh your device.
crump84 said:
While your still on a Sense ROM, call Sprint and have them refresh your device.
Click to expand...
Click to collapse
Yeah that's what I'm doing now.
prboy1969 said:
You don't have to unroot. Just flash a Sense based Rom. Update your Profile and PRL. Then flash back to CM7. Don't Nand back when your done updating your PRL and Profile. That will just put you back where you were.
Click to expand...
Click to collapse
+1. Right this is what i did when i was experiencing the same problem, and it worked..
kevowanj said:
+1. Right this is what i did when i was experiencing the same problem, and it worked..
Click to expand...
Click to collapse
Yeah but it didn't for me :/ That's fine though, Sprint got his phone working again
Sent from my Speedy with the XDA app
---------- Post added at 01:48 PM ---------- Previous post was at 01:22 PM ----------
Well it's just one problem after another.
Text and calls work again. I wiped data and cache, then flashed the ROM, gapps, and the kernel.
But now the Wifi is broken...
Clicking on it just says Error.
Now what?
doratheconquistadora said:
Yeah but it didn't for me :/ That's fine though, Sprint got his phone working again
Sent from my Speedy with the XDA app
---------- Post added at 01:48 PM ---------- Previous post was at 01:22 PM ----------
Well it's just one problem after another.
Text and calls work again. I wiped data and cache, then flashed the ROM, gapps, and the kernel.
But now the Wifi is broken...
Clicking on it just says Error.
Now what?
Click to expand...
Click to collapse
What ROM and Kernel are you using? Also, try rebooting and see if you still get the error with WiFi
crump84 said:
What ROM and Kernel are you using? Also, try rebooting and see if you still get the error with WiFi
Click to expand...
Click to collapse
CM 7.0.3.1 and x99.
The same one my phone is using, and the one he was using before. I rebooted and it still just says Error.
I'm going to wipe data/cache, reflash the ROM. Reboot. Wipe cache and flash gapps. Reboot. Wipe cache and flash kernel. Reboot.
That should work then right?
doratheconquistadora said:
CM 7.0.3.1 and x99.
The same one my phone is using, and the one he was using before. I rebooted and it still just says Error.
I'm going to wipe data/cache, reflash the ROM. Reboot. Wipe cache and flash gapps. Reboot. Wipe cache and flash kernel. Reboot.
That should work then right?
Click to expand...
Click to collapse
That should work, just when you do a full wipe the first time it's best to wipe a few times. Also, I usually let my ROM settle in just a bit before I flash a custom kernel.
This happened to me a couple of days ago. i was running Cyclonic 1.1. Here are the steps I did to fix it.
1. Made a Backup.
2. Wiped everything (except sd of course).
3. Flashed a sense rom.
4. Chatted with sprint and they fixed it.
5. Then wiped everything again.
6. And finally restored my ROM.
And everything is working fine now.
Is this the same as the "error 16" issue? My sister got a new shift about a week ago, I downgraded, rooted and flashed it to cm7 right away, and it was fine for a couple of days before not letting her call or text, just saying "error 16".
I called sprint, they did something on their end, then it worked for six hours before doing the same thing. I called them again, tech support said he forced a refresh on all the servers the previous tech hadn't, then it was fine again for a day before getting the same issue. Third call, fixed for twelve hours. During the second call I flashed to mikshifted, wiping everything very well beforehand, updated the profile and prl before sprint fixed it and I went back to cm7.
The fourth call fixed it again, but broke 3g data. Phone failed with error 16 again today and the lady at sprint, upon being told that it was running CM7 said that until I put the stock rom back on, it's going to keep having the same problem. I don't think that's right, or no one else would be able to run an aftermarket room. Any ideas, people?
Just flash the latest nightly.
Mystery solved on my error 16 issue, anyway. Turns out when I flashed the froyo engineering build downgrading from 2.3 to be able to root, I didn't realize it downgraded the radios. My super smart boyfriend figured it out, and newer radio has no problem now keeping authenticated with Sprint.
e: never mind, it worked for about two and a half days and then error 16'd repeatedly again. Flashed to x99's stock rom, we'll see what happens there.
Hello all and Merry Christmas!
I am in dire need of assistence.
Last night I went to update my CM rom to the 10.1 Dec.21st nightly. I have now been told that they were known to be corrupted. Anyways now I have restored multiple recoveries and I cant get my calls/texts to go through. The only connection I seem to be able to get is back in Stock TouchWiz where it gives me the option to "enable roaming for this trip." Wifi and everything else still work fine. Any suggestions??
Thanks!
Pups
Anyone!! please!!
I haven't tried any of this, I don't run CM but you might want to give this a read. Not sure if this is even your problem.
http://forum.xda-developers.com/showthread.php?t=2065285
I hit the roaming issue with yesterday's build and I solved it rather easily.
You don't need to Odin anything.
Simply factory reset and flash back to any TouchWiz rom from recovery. It can even be a Jellybean one.
Older CM10 or CM10.1 builds seemed to work, but were far less effective at restoring reception.
bobAbooE said:
I haven't tried any of this, I don't run CM but you might want to give this a read. Not sure if this is even your problem.
http://forum.xda-developers.com/showthread.php?t=2065285
Click to expand...
Click to collapse
This is most definitely my problem how did you find this?
LLStarks said:
I hit the roaming issue with yesterday's build and I solved it rather easily.
You don't need to Odin anything.
Simply factory reset and flash back to any TouchWiz rom from recovery. It can even be a Jellybean one.
Older CM10 or CM10.1 builds seemed to work, but were far less effective at restoring reception.
Click to expand...
Click to collapse
Okay so when I flashed Dec 21st CM10.1 i got into a loop and the ROM wouldnt even run so I just pulled my battery and restored to my last nightly. THEN the phone aspects stopped working. Should I factory reset from my CM 10 nightly or from my stock touchwiz recovery file. I already factory reset from my touchwiz file using TWRP
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.
Hi, I just tried flashing cyanogenmod on my us cellular galaxy s3, and I ran into a problem. I followed a great youtube tutorial on how to flash cyanogen, and everything went fine. the tutorial used goomanager, and was done only using the phone, no computer. I flashed the rom after backing everything up through titanium, and everything appeared to be working like it should. After the flash was complete, the cyanogen animation popped up on my screen, but as soon as it finished loading, two messages popped up: setup wizard has stopped and goo.apps has stopped. I would hit okay, but the two messages just kept popping up. I restored my stock rom, but id still like to flash cyanogen and I need to know what I need to do to prevent this from happening again and how to restart the flash process. Any help would be greatly appreciated!
intelligentduck said:
Hi, I just tried flashing cyanogenmod on my us cellular galaxy s3, and I ran into a problem. I followed a great youtube tutorial on how to flash cyanogen, and everything went fine. the tutorial used goomanager, and was done only using the phone, no computer. I flashed the rom after backing everything up through titanium, and everything appeared to be working like it should. After the flash was complete, the cyanogen animation popped up on my screen, but as soon as it finished loading, two messages popped up: setup wizard has stopped and goo.apps has stopped. I would hit okay, but the two messages just kept popping up. I restored my stock rom, but id still like to flash cyanogen and I need to know what I need to do to prevent this from happening again and how to restart the flash process. Any help would be greatly appreciated!
Click to expand...
Click to collapse
before you flashed the rom did you wipe data and cache? you might also be on the nightly version, try looking for the stable version, and if its on 10.1 its on 10.1, theres nothing you can do but wait for it to become stable if it isent already.
Trozzul said:
before you flashed the rom did you wipe data and cache? you might also be on the nightly version, try looking for the stable version, and if its on 10.1 its on 10.1, theres nothing you can do but wait for it to become stable if it isent already.
Click to expand...
Click to collapse
Everything was wiped. what I think happened was when I backed everything up, I didn't set titanium to not restore my app data, causing a bootloop. I could be very wrong about that though. What I need to know is how to reflash it, as I have already tried to but when I do it brings up system recovery instead of reflashing. Is it because I already tried flashing it once? and if that's the case how do I start from scratch? Oh, and I did flash the stable version. it was 10.1.2
intelligentduck said:
Everything was wiped. what I think happened was when I backed everything up, I didn't set titanium to not restore my app data, causing a bootloop. I could be very wrong about that though. What I need to know is how to reflash it, as I have already tried to but when I do it brings up system recovery instead of reflashing. Is it because I already tried flashing it once? and if that's the case how do I start from scratch? Oh, and I did flash the stable version. it was 10.1.2
Click to expand...
Click to collapse
might want to try flashing a stock rom via odin cause it sounds like you have stock recovery now, i dont know if anyone will pick you up in the q&a section, since yours is us cellular i dont think they have a forum for that specific contractor just only t-mobile at&t and verizon would have one. you can ask them in their q&a but tell them your situation and that your on us cellular. good luck mate. if ya have any questions just ask right here.
Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
powerkatwedel said:
Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Yeah I have the latest build if twrp and I think I already has the correct Mode from a prior rom. I didn't even check to verify guess I got too excited. I'll check and report back. Thanks.
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
powerkatwedel said:
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
Click to expand...
Click to collapse
Any other ideas that may be causing this?
powerkatwedel said:
Any other ideas that may be causing this?
Click to expand...
Click to collapse
Here is another user solved the issue, take from the thread:
"What I did was upgrade my recovery with Goo, I removed the SD card, I wiped the internal memory (not sure if this is necessary but what the hell), factory wiped, installed 7.1, once the phone booted up I logged in to gmail, let it sync, didn't install anything else and rebooted just to make sure it reboots fine, and it worked. Then I installed all my apps with TB without data, just the apps. That is what I did. I had the same problem as you for two days and was frustrated but then I read that if you upgrade your recovery it would work fine. I am assuming you are trying to wipe cache and it is telling you that it can't be mounted, that is another problem I was having, so I am assuming that by wiping the internal memory it cleared that problem up. I hope this helps you out. Hopefully someone here can either back up what I am saying or call me crazy and help you out. Good luck."
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
powerkatwedel said:
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
Click to expand...
Click to collapse
I was never able to get the WiFi to work, so I switched roms and was able to get everything working on Wicked. Thanks for all the help.