[Q] CyanogenMod broke voice service on all ROMs - Verizon Samsung Galaxy Note II

Here's what's happening:
I have a Galaxy Note 2 (i605) running Stock MC3 firmware. Everything is functioning perfectly. Then, I decide to unlock / flash cyanogenmod. After unlocking, everything still functions fine. After flashing cyanogenmod, my note will still connect to 4G, but will not send SMS, MMS, or phone calls.
No problem, I think. I odin back to stock MC3. Perfectly stock, same exact issue. How is it possible that something changed by installing cyanogenmod "sticks" through an odin-cycle?
Please someone help. I'm not enjoying having such an expensive paperweight.

Same exact problem here... trying to figure it out.

I had a similar issue on my s3. I had to use the unbrick files for Odin instead of the stock ones. It fixed it for me. Except my issue was I was stuck in roaming.
Sent from my KitKat note 2

ugh, now I'm stuck in roaming after using Odin root66

If you are on a stock rom go to settings > backup and reset > factory reset. Let the phone reboot on its own. When it reboots run through the setup and it should be working again once you finish. That's what worked for me.
Sent from my SCH-I605 using Tapatalk

N_Jones said:
If you are on a stock rom go to settings > backup and reset > factory reset. Let the phone reboot on its own. When it reboots run through the setup and it should be working again once you finish. That's what worked for me.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Wow...I cant believe that actually fixed the issue.

bwinger79 said:
Wow...I cant believe that actually fixed the issue.
Click to expand...
Click to collapse
I did that 3 or 4 times and it didn't work for me.
Exactly which stock odin flash did you use? I used root66_VZW_stock_system

I did not use Odin. I just flashed back to cleanrom and did the factory reset from settings not from recovery. Also I am using cwm and not twrp just in case that may make a difference.
Sent from my SCH-I605 using Tapatalk

I went back to stock, did the reset and got the radio working correctly after that. then rooted again. so annoying. bad CM10.2 bad!!

Just in case anyone else is like me and didn't thoroughly read this thread...
You must factory reset from the settings option, NOT FROM RECOVERY.
I'm not clear as to why that makes a difference, but after I Odin'd to stock and ran CASUAL, I kept using ServiceModeShortcut to toggle the modem, then rebooting into recovery to factory reset. Never worked. Then I reread this thread and realized I needed to do it from the settings menu instead. Worked first time! :victory:
What a stressful few hours. Totally thought I wrecked my phone...now, it's clean and ready to install a ROM. Think I'm sticking with Beans for a while :good:

Related

[Q] CM9 Alpha 13 - Can't activate service

So I flashed CM9 alpha 13(after wiping) but can't get service to activate on my phone. Same problem I'm having with alpha 9. I use the activate button when it starts and it tells me it failed. Under "About Phone" and "Status" I can see that the My Phone Number setting is wrong so is the MIN.
When I call my carrier to manually activate, the short codes they give me to manually input this info do not work.
Anybody else had this problem?
Go into Sprint Zone, and try to manually activate.
Sent from my MB855 using xda premium
Nevermind. That won't work. Sorry
Sent from my MB855 using xda premium
Flash cm9 and reboot dont install gapps till after it activates
Sent from my MB855 using XDA App
I will try this. Thank you sir!!
Ok, so I wiped... Flashed CM9. Rebooted. The activation call failed, so I called sprint to manually activate again. They asked me to punch in ##971912# which is supposed to pop up a dialog screen where I can manually input MIN etc but did not. Not sure what to do.
Flash back to a blur rom activate then reflash
tcf84 said:
Ok, so I wiped... Flashed CM9. Rebooted. The activation call failed, so I called sprint to manually activate again. They asked me to punch in ##971912# which is supposed to pop up a dialog screen where I can manually input MIN etc but did not. Not sure what to do.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Ok, I've got my phone up and running on Rocko's ROM. I'm doing a nand backup now. So, to be clear... I need go to my recovery. Data Reset and wipe dalvik cache. Then I need to flash CM9. I then need to activate(or make sure I'm still activated), and once that is confirmed I need to flash Gapps?
Sorry. I'm just trying to figure out where I went wrong the first time...
Try that, you're the first person to have issues so its a new issues
tcf84 said:
Ok, I've got my phone up and running on Rocko's ROM. I'm doing a nand backup now. So, to be clear... I need go to my recovery. Data Reset and wipe dalvik cache. Then I need to flash CM9. I then need to activate(or make sure I'm still activated), and once that is confirmed I need to flash Gapps?
Sorry. I'm just trying to figure out where I went wrong the first time...
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
tcf84 said:
So I flashed CM9 alpha 13(after wiping) but can't get service to activate on my phone. Same problem I'm having with alpha 9. I use the activate button when it starts and it tells me it failed. Under "About Phone" and "Status" I can see that the My Phone Number setting is wrong so is the MIN.
When I call my carrier to manually activate, the short codes they give me to manually input this info do not work.
Anybody else had this problem?
Click to expand...
Click to collapse
I had this problem as well. I've also bricked my phone flashing an electrify pudding by mistake on my photon. My fix after fixing my boot loader issues was: I reverted to completely stock. Then I called sprint and had to reactivate my phone. After getting everything working and having a secure connection for over a day I then flashed cm7 to make sure that would work. After it did I did a says wipe and wiped everything else. And flashed cm9 then went into recovery wiped and flashed again. Then I flashed gapps and boot up. After booting up I went back and wiped again. And then used the phone for about twenty minutes and wiped and flashed "all" again. It was a long drawn out process. But I have had none of the issues that people are having on the forum. Battery life is great after calibrating. 3G is almost as fast as the 4G I had. Never have a single reboot or battery pull. Wifi and Bluetooth bead on perfect. I'm new to xda but not development. I'd post my success in the forum, but I'm not yet at ten post.
Sent from my MB855 using XDA App
FanBoy_Hunter said:
I had this problem as well. I've also bricked my phone flashing an electrify pudding by mistake on my photon. My fix after fixing my boot loader issues was: I reverted to completely stock. Then I called sprint and had to reactivate my phone. After getting everything working and having a secure connection for over a day I then flashed cm7 to make sure that would work. After it did I did a says wipe and wiped everything else. And flashed cm9 then went into recovery wiped and flashed again. Then I flashed gapps and boot up. After booting up I went back and wiped again. And then used the phone for about twenty minutes and wiped and flashed "all" again. It was a long drawn out process. But I have had none of the issues that people are having on the forum. Battery life is great after calibrating. 3G is almost as fast as the 4G I had. Never have a single reboot or battery pull. Wifi and Bluetooth bead on perfect. I'm new to xda but not development. I'd post my success in the forum, but I'm not yet at ten post.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I tried reverting to stock as outlined by qbking77 but every time I sbf'ed the file as instructed I lost my recovery. The 'Unlocked' notice disappeared as it was supposed to but once I did that I couldn't get any recoveries to stick, stock or CWM, until I "re-unlocked" the phone with that sbf. Even then I couldn't get the stock recovery to write properly.
I'm pretty new to all of this. I unlocked my Optimus S and tried a few ROMs on it before I settled on Reborn Rom, but that's about my only experience with these things. I'm not incompetent(I hope) when it comes to this stuff, but it's definitely a learning curve. I'd like to master the whole process though so I can delve into the dev side of things a bit.
Joker - Thanks for the help. I'm up and running with no problems.
What did you do?
tcf84 said:
Joker - Thanks for the help. I'm up and running with no problems.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
A combination of what you and FanBoy suggested. First I wiped and flashed Rocko ROM. Got the phone to activate. Then I wiped. Flashed CM9. Wiped again. Booted up and verified service was active. Wiped again, Flashed CM9 again, wiped again, and flashed gapps v3.
I really don't know what the problem was to start. I originally tried to flash CM7 and couldn't get signal at all. So I flashed MIUI with the same issue. Finally I flashed CM9 and had signal but couldn't activate. So the problem wasn't tied to CM9, but I honestly have no idea what I did to lose signal/activation or to gain either of those back, but my phone does work now and I've successfully flashed both CM9 and Rocko without the loss of signal or service and have nand backups of both since my biggest problem originally stemmed from not having a nand backup of my latest working set up.
I think I hear the ice cream man!
tcf84 said:
A combination of what you and FanBoy suggested. First I wiped and flashed Rocko ROM. Got the phone to activate. Then I wiped. Flashed CM9. Wiped again. Booted up and verified service was active. Wiped again, Flashed CM9 again, wiped again, and flashed gapps v3.
I really don't know what the problem was to start. I originally tried to flash CM7 and couldn't get signal at all. So I flashed MIUI with the same issue. Finally I flashed CM9 and had signal but couldn't activate. So the problem wasn't tied to CM9, but I honestly have no idea what I did to lose signal/activation or to gain either of those back, but my phone does work now and I've successfully flashed both CM9 and Rocko without the loss of signal or service and have nand backups of both since my biggest problem originally stemmed from not having a nand backup of my latest working set up.
Click to expand...
Click to collapse
Most custom roms disallow communication from what ever it is that allows you to activate with sprint. I noticed that porting in sprintzone.apk often doesn't work and you can't activate with the dialer because it requires communication with sprintzone. So you need to flash to a rom that allows activation and then work your way back up. Glad to hear you got it working.

[Q] flashing and data

I'm on my second DNA I moonshined both phones and a week ago I flash the cm10.1 and had no data ie. Couldn't make a call couldn't text. Internet and everything worked after flashing cm10.1 it stuck on the first screen the "activating" screen so I flashed my backup which is the ROM it comes with out the box. And had no data there also.. Android 4.1.1. Sense 4.1+. Verizon exchanged my phone lucky for me. So i moonshined again and s-off and rooted. But scared to flash again in case this happens again. Coming from gs2, galaxy nexus and gs3 I haven't had to mess with bootloader at all. I guess where I'm going is what do I do if this happens again. I see a option to reset from boot loader? Will that fix the issue if it happens again. Is there something I'm missing before flashing?? I want to flash newtoroots sense 5 ROM just scared. If someone can provide some info on where o went wrong gladly appreciate it.
Sent from my HTC6435LVW using Tapatalk 2
swiftinmotion said:
I'm on my second DNA I moonshined both phones and a week ago I flash the cm10.1 and had no data ie. Couldn't make a call couldn't text. Internet and everything worked after flashing cm10.1 it stuck on the first screen the "activating" screen so I flashed my backup which is the ROM it comes with out the box. And had no data there also.. Android 4.1.1. Sense 4.1+. Verizon exchanged my phone lucky for me. So i moonshined again and s-off and rooted. But scared to flash again in case this happens again. Coming from gs2, galaxy nexus and gs3 I haven't had to mess with bootloader at all. I guess where I'm going is what do I do if this happens again. I see a option to reset from boot loader? Will that fix the issue if it happens again. Is there something I'm missing before flashing?? I want to flash newtoroots sense 5 ROM just scared. If someone can provide some info on where o went wrong gladly appreciate it.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
If this happens you can try the reset from bootloader but of that doesnt work you'll have to do revones return to stock method. There's a thread. Pretty much flashes the RUU (stock everything) and flash stock bootloader. Its not hard. I did this the other day to put my phone back to stock for my replacement.
Sent from my HTC6435LVW using xda app-developers app
swiftinmotion said:
I'm on my second DNA I moonshined both phones and a week ago I flash the cm10.1 and had no data ie. Couldn't make a call couldn't text. Internet and everything worked after flashing cm10.1 it stuck on the first screen the "activating" screen so I flashed my backup which is the ROM it comes with out the box. And had no data there also.. Android 4.1.1. Sense 4.1+. Verizon exchanged my phone lucky for me. So i moonshined again and s-off and rooted. But scared to flash again in case this happens again. Coming from gs2, galaxy nexus and gs3 I haven't had to mess with bootloader at all. I guess where I'm going is what do I do if this happens again. I see a option to reset from boot loader? Will that fix the issue if it happens again. Is there something I'm missing before flashing?? I want to flash newtoroots sense 5 ROM just scared. If someone can provide some info on where o went wrong gladly appreciate it.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
Sometimes That happen when a Rom like a JB 4.2.2 required to wipe the System in addition to the normal wipe/factory reset. so if you tried
to activate the phone which you already have activated (most skipp activation) the SIM Card reset (someone else said fry) and your location and phone number get lost. so RUU fix all the troubles, but now you can safe flash NOS 4.1.2 very stable normal wipe. is good idea keep in your computer a Stock Restore Backup file. Reset from Custom Recovery won't fix the issue, has to be from Stock Recovery.
http://teamw.in/androidmultiuser
http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Based on the info you gave none of your issues should be caused by the boot loader or moonshine, sounds like a ROM side or kernel side issue. The radio mode may have been switched when you flashed Roms. It should be on CDMA/LTE when on Verizon and WCDMA/GSM when on gsm/Sim. Not sure how APN settings are managed within CM non gsm im not sure there is even an option to edit them. These settings (radio/apns) deal with how the phone connects to the network. Voice and text should provision automatically on stock android, not sure how to manually provision. On Sense based Roms as long as a compatible version of EPST is running one can use special dialer codes to manually provision the phone for connectivity as well as access other helpful settings. From sense *#*#4636#*#* would be the code to reach the Phone Information containing the radio mode switch I mentioned previously.
Thanks for the replies guys. Yeah on jb4.2.2 that activating screen is usually passed right by for a quick second bit some how my phone got stuck on that screen. Oh well its rattled me to the point of not flashing lol. Just rocking nova launcher with some icon packs. Might try sense 5 ROM tonight. Wish me luck! Lmao
Sent from my HTC6435LVW using Tapatalk 2
d08speed3 said:
If this happens you can try the reset from bootloader but of that doesnt work you'll have to do revones return to stock method. There's a thread. Pretty much flashes the RUU (stock everything) and flash stock bootloader. Its not hard. I did this the other day to put my phone back to stock for my replacement.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
If it happens again go into boot loader and just do the reset option? Is that it do I need to have anything else? Thanks again for the reply
Sent from my HTC6435LVW using Tapatalk 2
Take out the sim card and re-insert it.
orangechoochoo said:
Take out the sim card and re-insert it.
Click to expand...
Click to collapse
Wasn't a Sim card problem.
Sent from my HTC6435LVW using Tapatalk 2
Some Info
swiftinmotion said:
Wasn't a Sim card problem.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
RUU (after Stock Phone Reset) is the only way to Recovery from this, this happen to me once, what happen
-Operator Network Change (u can only have Internet)
-APN Setting Doesn't matter if you change it a least it be edited . Unknown Network and Mobile/network type unknown
-Phone Info state Phone number 0000000000 Zeros, Min Unknown, PRL 00000, Meid zeros,
-Restore from you back up out the box: does not work or doesn't restore Call and Text ( this is the problem) Phone doesn't know your location
then u are having internet only 4g like in a Roaming State.
-Flash or push new Rom same Doesn't restore (call/text)
-Factory reset from a custom Recovery Doesn't restore as well
to skip the activating screen you can touch the four corners of the screen in this order
top left
top right
bottom right
bottom left
this will bypass the activating screen
once you're in the rom in cdma subscription change it to the other setting, I stopped using that rom so i cant lead you through it
the aosp roms made my screen flicker so i went back to sense 5
good luck
finanandroid said:
RUU (after Stock Phone Reset) is the only way to Recovery from this, this happen to me once, what happen
-Operator Network Change (u can only have Internet)
-APN Setting Doesn't matter if you change it a least it be edited . Unknown Network and Mobile/network type unknown
-Phone Info state Phone number 0000000000 Zeros, Min Unknown, PRL 00000, Meid zeros,
-Restore from you back up out the box: does not work or doesn't restore Call and Text ( this is the problem) Phone doesn't know your location
then u are having internet only 4g like in a Roaming State.
-Flash or push new Rom same Doesn't restore (call/text)
-Factory reset from a custom Recovery Doesn't restore as well
Click to expand...
Click to collapse
This Sucks Verizon actually exchanged my phone In store considering I don't know how to ruu or what that is I haven't flashed anything on this new phone to afraid of the same **** happening again. Damn! Is this a cm10.1 thing? Or a android 4.2.2 thing? Is it safe flashing sense based roms ? This is kind of a nightmare for me not flashing anything.
Sent from my HTC6435LVW using Tapatalk 2
hyphydragon said:
to skip the activating screen you can touch the four corners of the screen in this order
top left
top right
bottom right
bottom left
this will bypass the activating screen
once you're in the rom in cdma subscription change it to the other setting, I stopped using that rom so i cant lead you through it
the aosp roms made my screen flicker so i went back to sense 5
good luck
Click to expand...
Click to collapse
Was reading around right now seems like other people having same issue I had on cm10.1 and cm10.2.. Think it's safe to flash a sense 5 rom?? Or the same **** happening? Should of just stuck to my gs3 is what it seems =(
Sent from my HTC6435LVW using Tapatalk 2
swiftinmotion said:
This Sucks Verizon actually exchanged my phone In store considering I don't know how to ruu or what that is I haven't flashed anything on this new phone to afraid of the same **** happening again. Damn! Is this a cm10.1 thing? Or a android 4.2.2 thing? Is it safe flashing sense based roms ? This is kind of a nightmare for me not flashing anything.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
You can safe flash NOS_m7_v3.0.2_VZW_zip , if you have TWRP recovery, just wipe normal factory reset, don't do advanced/ system wipe as most guys recommended, never wipe Storage phone people get stuck without OS because erase everything . I Flashed doing just factory reset on TWRP. I recommend wait for AOSP Rom get most stables soon coming leaks from official Verizon Wireless for the DNA/One. sense /GPE edition
RUU is the Factory image /setting original HTC/Verizon for DNA so when you RUU it revert anything to factory out the box phone
The RUU thing you have to read this thread : http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Edit: Remember do always a nandroid Back up first before flash any Rom so you can easy restore your original Rom if something goes wrong.
additional I keep a Original Back up on my Computer.
finanandroid said:
You can safe flash NOS_m7_v3.0.2_VZW_zip , if you have TWRP recovery, just wipe normal factory reset, don't do advanced/ system wipe as most guys recommended, never wipe Storage phone people get stuck without OS because erase everything . I Flashed doing just factory reset on TWRP. I recommend wait for AOSP Rom get most stables soon coming leaks from official Verizon Wireless for the DNA/One. sense /GPE edition
RUU is the Factory image /setting original HTC/Verizon for DNA so when you RUU it revert anything to factory out the box phone
The RUU thing you have to read this thread : http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Edit: Remember do always a nandroid Back up first before flash any Rom so you can easy restore your original Rom if something goes wrong.
additional I keep a Original Back up on my Computer.
Click to expand...
Click to collapse
I use clockworkmod safe to use? Never used twrp. And I always make a back up that's what's weird. When I flashed cm10.1 and it couldn't activate thought it was odd so I flashed my back up and that was affected also no activation. Anyways. So your saying if I flash something to wipe data/factory reset but don't go into advanced? Just wipe dalvik?
Sent from my HTC6435LVW using Tapatalk 2
swiftinmotion said:
I use clockworkmod safe to use? Never used twrp. And I always make a back up that's what's weird. When I flashed cm10.1 and it couldn't activate thought it was odd so I flashed my back up and that was affected also no activation. Anyways. So your saying if I flash something to wipe data/factory reset but don't go into advanced? Just wipe dalvik?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
I don't use CWM by now, but just do data/factory reset and dalvik as well.

[Q] Unable to call or SMS and global mode

Hello!
First things first, I have searched the internet, not just XDA, far and wide for these problems. I have followed nearly every lead I could find before creating a post about this, I am at wits end and at this point have had to remove the phone from the premises before something bad happened to it.
My problems:
"Switch to Global mode" constantly pops up"
Cannot send or receive either texts nor phone calls
Setup:
Previously on CleanRom 3.5, decided to try CM10.2. Downloaded and installed CWM to use instead of TWRP, downloaded CM10.2, wiped cache, factory reset, installed CM10.2 zip file as well as Gapps for 4.3. CM10.2 exhibited the above behavior. Currently I am sitting on completely stock JB 4.1.2, the details are below.
Network: Unknown
Mobile Network type: Unknown:0
Service State: Out of service
Mobile Network State: Disconnected
Phone number: <correct #>
IMEI: <correct IMEI, validated per inside battery cover>
Android 4.1.2
Baseband: I605VRAMC3
Kernel: 3.0.31-1098177
[email protected]#1
SMP PREEMPT Fri Mar 29 10:58:51 KST 2013
Build Number: JZO54K.I605VRAMC3
Hardware Version: I605.06
Mitigation attempts:
Downgrade to CM10.1 (AOSP keyboard would not work)
Tried various AOSP and TW ROMs, to no avail.
Cleared cache, dalvik cache and factory reset between each attempt
Finally downloaded stock ROM, followed steps here (great guide btw!) using Odin, no change.
I truly don't know what else to do at this point. I feel like I've done everything I've seen and my problems are still around. I see a lot about IMEI (not sure what it is or what it does), but mine is present and has been throughout this ordeal. Occasionally my phone number would read as 000-000-3279, which was not correct, but that was only on the CM ROMs. Any help with this would be greatly appreciated, I don't want a Note 2 paper weight or media device hanging around, I want my phone back - stock form is fine. Thank you for reading all this and I appreciate any help that can be sent my way.
I am in this exact situation.
Was on stock, VRAMC3 and wanted to go custom.
The CASUAL exploit worked just fine, and once I had CWM I attempted to flash CM 10.2.
It just didn't seem right.
Every other ROM I've tried since that point I am unable to send/receive texts, and get the Global mode popup constantly.
I tried to revert back to stock via this thread: http://forum.xda-developers.com/showthread.php?t=2024207 But no luck.
Any help would be appreciated.
I ran into this last night while trying a new rom(coming from Beans 22). I can't call or receive calls. I can receive texts, but can't send them. Data works. I've tried multiple ROM's, and it's the same situation with each(CM10.2, 10.1, XenonHD). I just tried returning everything to stock with Odin, and continue to have the same issues. My phone number reads as 000-000-2780. My IMEI is correct. Service State: Out of service. If I switch to CMDA/LTE, I get hammered with "switch to global mode" popups. If anyone has any suggestions, please post them.
I had LTE and wifi when this happened to me, so I was able to download Telinfo from Play.
Also, I had ODINed back to Root66 so all the hidden menu options were available.
Your modem needs to reset, so go into device info and turn off your radio. Toggle to LTE/CDMA/EvDo and then turn radio back on.
I don't remember if a reboot was necessary.
My modem was fine after that.
Let me know if this works for you.
Sent from my SCH-I605 using XDA Premium 4 mobile app
pdinphx, I just toggled the radio using "ServiceMode Shortcut" and did a factory reset afterwards. It worked! Thanks!!!!
ap0ptosis said:
pdinphx, I just toggled the radio using "ServiceMode Shortcut" and did a factory reset afterwards. It worked! Thanks!!!!
Click to expand...
Click to collapse
hi.. same thing happened to me. Was trying different roms coming from Beans22, lost ability to make/receive calls but data connection was fine.
Questions:
Did you have to change rom back to factory stock before doing the radio toggle thing?
What is "ServiceMode Shortcut"?
Thanks much!
wutek, I did change back to factory stock before I did the radio toggle, but I think you can do it from whatever rom you flashed to. "ServiceMode Shortcut" is an app from the store that allows you to access the service mode menu. After installing it, go to testing>device information, and reset the modem from there as pdinphx advised. Good luck!
Having the same problem. Flashed 10.2 last night from cm11, didn't make a call just went to bed and woke up and had this problem. Tried using that app from 10.2 without any luck unless I am doing something wrong. I guess I am gonna try after using Odin. Anyone else having any luck?
Sent from my GT-P3110 using xda app-developers app
ap0ptosis said:
wutek, I did change back to factory stock before I did the radio toggle, but I think you can do it from whatever rom you flashed to. "ServiceMode Shortcut" is an app from the store that allows you to access the service mode menu. After installing it, go to testing>device information, and reset the modem from there as pdinphx advised. Good luck!
Click to expand...
Click to collapse
hi ap0ptosis,
quick update... I was able to regain radio after odin to root66, toggle using telinfo, factory reset. Thanks for the info on the ServiceMode Shortcut app.
To all.. thanks for the help... I am back and kicking. However, I am now staring at the big elephant in the room so have to ask the question... how did this all of the sudden start to happen? It started for me when I tried out some 4.3 Roms but radio going bonkers did not happen immediately. For me it happened overnight w/o me touching anything. The message I would continuously get is "Mobile network not available" . Also phone would keep asking to switch to global mode.
wutek said:
hi ap0ptosis,
quick update... I was able to regain radio after odin to root66, toggle using telinfo, factory reset. Thanks for the info on the ServiceMode Shortcut app.
To all.. thanks for the help... I am back and kicking. However, I am now staring at the big elephant in the room so have to ask the question... how did this all of the sudden start to happen? It started for me when I tried out some 4.3 Roms but radio going bonkers did not happen immediately. For me it happened overnight w/o me touching anything. The message I would continuously get is "Mobile network not available" . Also phone would keep asking to switch to global mode.
Click to expand...
Click to collapse
Glad you got yours going. When using root 66 do I still need to use the pit file alongside? Have the 66 downloaded but never used it.
Sent from my GT-P3110 using xda app-developers app
mikelikesbikes said:
Glad you got yours going. When using root 66 do I still need to use the pit file alongside? Have the 66 downloaded but never used it.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
hi mikelikesbikes.. I followed the exact instructions from the below url. So definitely, I used pit. Good Luck
http://forum.xda-developers.com/showthread.php?t=2024207
Have Odin running as I type using root 66 and the pit. How does one reset the radio from the playstore app? I see how to turn off the radio and change radio but not how to reset it. Obviously it is staring me in the face.
Sent from my GT-P3110 using xda app-developers app
So I got it going. Used the root 66 file and didn't have a operating system to boot into, only cwm recovery which was weird. So I used Odin and went back completely stock, and ran that app from the play store. Still didn't work until I factory reset from within settings and that was what got it I suppose. I wonder also what caused it and why others had the same issue on the same morning. Like I said previously I was running 4.4 for a few days and went back to 4.3. That's the only thing I did differently. Anyway, ran Casual, and running Beans 22 and happy.
Sent from my GT-P3110 using xda app-developers app
mikelikesbikes said:
So I got it going. Used the root 66 file and didn't have a operating system to boot into, only cwm recovery which was weird. So I used Odin and went back completely stock, and ran that app from the play store. Still didn't work until I factory reset from within settings and that was what got it I suppose. I wonder also what caused it and why others had the same issue on the same morning. Like I said previously I was running 4.4 for a few days and went back to 4.3. That's the only thing I did differently. Anyway, ran Casual, and running Beans 22 and happy.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Hi mikelikesbikes,
Glad u got it working again. Interesting... I did read somewhere that root66 may not work and if so, to use vz stock.
Correct, factory reset is within the phone>settings>backup reset menu... cheers
Not sure why this happens but I had the same thing happen to me. I tried cm11 and then switched to cm10 after switching back to tw rom I was in roaming only. A simple factory reset took care of the issue. So I think the common denominator here is the series of events cm11 to cm10 to touchwiz....
Sent from my SCH-I605 using Tapatalk
I had this problem coming from stock MC3 --> Root/Unlock --> CM 10.2
No calls / SMS on 10.2, and still nothing coming back to stock MC3.
You guys saved my ass, thanks! Toggling the radio / factory restore worked for me.
Anyone know what ROMs are SAFE to use without this issue appearing?
Back to normal, whew!
I had been stable on cm10.2 nightlies as of 11/29 with mc3. Installed cm11 everything was operational. I was able to bounce back and forth between my backups. As soon as I updated to the newest nightly for cm10.2, 12/1, that broke my voice/sms.
Ended up reverting back to stock, factory reset from settings in stock and was back up and running.
From here I used casual and tried to go back to the 12/1 nightly and still had the same issues.
Repeated stock process/casual and am now on slimrom 4.3 mc3 and running smoothly. Just wanted to get my problems and solution out there for more info.
This was a fairly common problem with the S3.
The key to fixing it is not in the factory reset but in the reprovisioning of the phone's modem, which typically requires a stock rom to access Samsung's hidden service menu.
Incidentally, even a touchwiz rom built off another carrier's base (or international base) can trigger this problem.
Sent from my SCH-I605 using XDA Premium 4 mobile app
N_Jones said:
Not sure why this happens but I had the same thing happen to me. I tried cm11 and then switched to cm10 after switching back to tw rom I was in roaming only. A simple factory reset took care of the issue. So I think the common denominator here is the series of events cm11 to cm10 to touchwiz....
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Agreed. Never had this problem before (thankfully). Think it's odd though several people had the same issue on the same morning.
Sent from my GT-P3110 using xda app-developers app
Same Issue
I'm running into the same issue as ya'll. Flashed CM 10.2, than flashed back to CleanRom 3.5 and not able to make calls or send text. Can receive text and all incoming calls go to Voicemail. I ODIN back to stock VRALJB, can't seem to get phone going again. Tried toggling Radio and Factory Data reset, but now the phone is just stuck in Roaming Mode. Any help?

[q] in desperate need of help!!

I am in need of some help ASAP.!!
Have a Samsung Galaxy Note 2. I had rooted it and flashed different Eclipse ROMs and decided to go with CarbonROM all in one night. I liked everything about Carbon until I noticed the next day I didn't have 4g anymore and wouldn't go over 2 bars of signal. So I decided i wanted to flash back to factory unrooted. I searched and searched and read and read to make sure just how to do it for my phone. I used Odin and it successfully flashed but than when it went to reboot it keeps flashing the startup "Samsung Galaxy Note II" over and over. Is this bootloop correct? If so i have searched and searched how to fix this and nothing is working. Either Odin gets stuck at SetupConnection, or hangs, wont even recognize my Note (I have uninstalled and reinstalled drivers multiple times.) and nothing is working. I have no access to recovery mode, only download.
I really need some help with this. Any input is greatly appreciated!!!!!!
If you are able to go into recovery then wipe to factory reset.... If not then try to install the stock rom via odin
Sent from my SCH-I605 using XDA Premium 4 mobile app
nikhil.kdhand said:
If you are able to go into recovery then wipe to factory reset.... If not then try to install the stock rom via odin
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to finally restore it back to factory. I ended up using a stock ROM from one thread used with a pit. file from the Root/Unroot Guide on this forum along with checking the re-partitioning. It was successful the first try amazingly, entered a true bootloop as i found out (flashed 4gLTE rainbow etc over and over.) and was able to access recovery mode. Wiped cache and factory reset and rebooted. Phone is now working!!
BUT... no 4g?? only 3g and signal is still somewhat weak compared to past signals. Do I need to alter APN, IMEI, or stuff like that?? :S
Also a sidenote, I used to be 4.2.2, and now after stock restore/flash I am 4.1.2. Is this a big deal and can I upgrade to lets say 4.3 without rooting or do custom ROMs update this or do they need a base to be added to? :S

Note 2 rebooting

I have a note 2 that I kept stock for a long time. And decided to root it about a week ago. I used the latest casual one click root. And it seemed all dandy initially until i went between a few different roms and it decided it wanted to shut off randomly and not boot back up past the note 2 screen on its own. But the odd part was it booted while connected to the wall or to the computer. So I flashed to 4.1.2 stock via odin and the issue still remains. I can only use it fine on charger. Is there something else im missing on flashing back to stock?
Sent from my SCH-I605 using XDA Free mobile app
Hmm when you installed 4.3 did you do so wiping everything could be an app causing the problem. Try it from brand new with no apps installed and see if that helps. Could be also a radio issue as well.
Sent from my XT1060 using Tapatalk
Yeah I wiped everything. Actually used odin twice to revert to stock 4.1.2. I tried a few cm nightlies before it began. Is there anything else I should flash on top of whats already been done?
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
Yeah I wiped everything. Actually used odin twice to revert to stock 4.1.2. I tried a few cm nightlies before it began. Is there anything else I should flash on top of whats already been done?
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
I've found that even after using ODIN to go back to stock 4.1.2, that there's still leftover data on the phone from custom ROM's. I've read where others had the same issue. I don't know why Odin doesn't seem to fully wipe everything ... but this has been my personal experience.
The way I've fixed this (and all this may not be necessary).. . is that after Odin'ing back to stock 4.1.2, I boot into stock recovery, then do a full factory reset and wipe cache. Then I booted into the stock Rom and used the bypass setup trick (touch the left side of the screen right above Emergency... then right side, then left, then right again, and then volume up... this should bypass setup to save time).
Then went into phone's settings and performed a factory reset from within the stock Rom too...
Finally... (because I'm a bit OCD... so this is probably not necessary), but I ODIN'd back to stock 4.1.2 one more time and then proceeded with using CASUAL again to root /unlock the bootloader).
I know this is a pain in the butt... but this has worked for me. Maybe others will have some better suggestions.
(Edit : Forgot to mention that if you're not wanting to return to stock to start over again... check out this thread (http://forum.xda-developers.com/showthread.php?p=53624921) on how to flash a stock recovery for the purposes of doing a proper data wipe... then can you odin your custom recovery back to the device without having to fully restore to stock... this can be a real time saver. Please make sure to thank the OP for the helpful info).
So in the end I tried to reset from stock recovery and wipe cache. Than do a reset from the settings and the issue presisted. But now I have root and recovery as well. So I may give a rom a try.
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
So in the end I tried to reset from stock recovery and wipe cache. Than do a reset from the settings and the issue presisted. But now I have root and recovery as well. So I may give a rom a try.
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
This is totally a guess, but I'm thinking that you may have a battery problem... and it's just a coincidence that these problems started happening around the same time that you rooted. You may try replacing the battery to see if that fixes things.... (you can get one pretty cheap off ebay or Amazon).
Yeah thats odd. I had bought another battery from a phone store I use to work at and have no issues now, back on 4.1.1 rooted.
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
Yeah thats odd. I had bought another battery from a phone store I use to work at and have no issues now, back on 4.1.1 rooted.
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Cool. Hopefully you'll have no more problems with it for a while.
:thumbup:

Categories

Resources