I'm having issues with my Galaxy S6. I used Odin to return to stock, and now I'm getting an "Unfortunately, IMS Service has stopped" error every 2 or 3 seconds. The phone is essentially unusable.
Other Galaxy phones have had similar issues, and I've tried some of their suggestions. I wiped Media Storage and factory reset the phone through the recovery. I tried to find the DRM app to wipe, but it's not there in the app manager. Does anybody have any suggestions? They are greatly appreciated.
Thanks in advance.
Im having that same issue. I bricked my phone for about a week and I had just got the tar files to open and return my device to stock. Is it saying you have service? Ive been looking this up everywhere and have no luck with the s6 problem.
boristhebladexx said:
I'm having issues with my Galaxy S6. I used Odin to return to stock, and now I'm getting an "Unfortunately, IMS Service has stopped" error every 2 or 3 seconds. The phone is essentially unusable.
Other Galaxy phones have had similar issues, and I've tried some of their suggestions. I wiped Media Storage and factory reset the phone through the recovery. I tried to find the DRM app to wipe, but it's not there in the app manager.
Click to expand...
Click to collapse
Why did you return to stock? If you are planning to return/exchange the phone, then you may run into trouble if it is unusable.
3 options:
1. Attempt to reflash stock via Odin and hope it fixes the problem.
2. Restore a nandroid.
3. Clean flash a custom rom.
sublimaze said:
Why did you return to stock? If you are planning to return/exchange the phone, then you may run into trouble if it is unusable.
3 options:
1. Attempt to reflash stock via Odin and hope it fixes the problem.
2. Restore a nandroid.
3. Clean flash a custom rom.
Click to expand...
Click to collapse
i tried to reflash stock again and the same message kept coming up. i thought that restoring would wipe root so i dont know how you could flash a custom rom onto it. would you do that through the Odin program??
LiquidPhoenix said:
i tried to reflash stock again and the same message kept coming up. i thought that restoring would wipe root so i dont know how you could flash a custom rom onto it. would you do that through the Odin program??
Click to expand...
Click to collapse
Did you try restoring a nandroid?
Sent from my SM-G920T using Tapatalk
sublimaze said:
Did you try restoring a nandroid?
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
i never backed up a nandroid. im pretty new to android phones and the deep stuff because the only thing i ever learned was iphone. do they auto backup? and if so, how could i restore it??
thank you for your patience, i know its driving you crazy haha.
LiquidPhoenix said:
i never backed up a nandroid. im pretty new to android phones and the deep stuff because the only thing i ever learned was iphone. do they auto backup? and if so, how could i restore it??
Click to expand...
Click to collapse
Android lollipop gives you the option to transfer your apps to a new device when you setup the new device. You are also given this option when you flash a custom lollilop rom, because the setup wizard will see this as a new device. However, you should always make a backup of a good working rom setup prior to flashing a new rom or any mods. When I say a "good working rom ", I mean a rom that you might possibly want to go back to, in case your next rom flash doesn't go well or it has major issues that prevent you from using it as a daily driver (which you won't know until you flash it, obviously). The stock rom is definitely a "good working rom", and you should ALWAYS make a backup of stock before flashing anything else.
Since you don't have a backup of stock, then you are stuck with Odin getting you back to bone stock, which apparently isn't quite doing the job. The only other thing I can suggest is flashing a stock rooted rom (eg, no mods other than root). But make sure you clean flash, which also means mounting & wiping /system in recovery. I forgot how to do it in CWM/Phil's recovery, but in TWRP go to Mount, tap /system then go back to the main menu, go to Wipe > Advanced and select cache, dalvik cache, data and system, then swipe to erase. Now you have a totally clean slate.
sublimaze said:
Android lollipop gives you the option to transfer your apps to a new device when you setup the new device. You are also given this option when you flash a custom lollilop rom, because the setup wizard will see this as a new device. However, you should always make a backup of a good working rom setup prior to flashing a new rom or any mods. When I say a "good working rom ", I mean a rom that you might possibly want to go back to, in case your next rom flash doesn't go well or it has major issues that prevent you from using it as a daily driver (which you won't know until you flash it, obviously). The stock rom is definitely a "good working rom", and you should ALWAYS make a backup of stock before flashing anything else.
Since you don't have a backup of stock, then you are stuck with Odin getting you back to bone stock, which apparently isn't quite doing the job. The only other thing I can suggest is flashing a stock rooted rom (eg, no mods other than root). But make sure you clean flash, which also means mounting & wiping /system in recovery. I forgot how to do it in CWM/Phil's recovery, but in TWRP go to Mount, tap /system then go back to the main menu, go to Wipe > Advanced and select cache, dalvik cache, data and system, then swipe to erase. Now you have a totally clean slate.
Click to expand...
Click to collapse
Ive tried looking online for software thats compatible with my carrier (cricket) but I couldnt find it. The way that I bricked my phone was trying to flash TWRP recovery on my phone. Cricket is through at&t and has the locked bootloader. I used pingpong root to root it but apparently it wasnt compatible with my phone. I'm kinda stuck.
LiquidPhoenix said:
Ive tried looking online for software thats compatible with my carrier (cricket) but I couldnt find it. The way that I bricked my phone was trying to flash TWRP recovery on my phone. Cricket is through at&t and has the locked bootloader. I used pingpong root to root it but apparently it wasnt compatible with my phone. I'm kinda stuck.
Click to expand...
Click to collapse
I have never messed with Cricket phones. I know they piggyback on the AT&T network, but I don't know if the firmwares are different. You could go to a Cricket store and look at the display S6 to find out the exact firmware version, and try to find that on the web (posting in the AT&T forum might yield a faster response). But trying to flash TWRP was not a good idea. Good luck!
I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?
boristhebladexx said:
I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?
Click to expand...
Click to collapse
I tried this just now and all it said was "attempt thread failed (0/0)"
boristhebladexx said:
I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?
Click to expand...
Click to collapse
Yes it does make a difference to flash it into 4 different parts in case you have the entire firmware
Just wanted to throw my 2 cents in here, i woke to this lovely issue, which was rendering my phone unusable. I use a program call YouMail for voicemail, creeps my friends out when they get to my voice mail. Uninstall this program after wiping every cache imaginable, voila, no more issue. I haven't tried to reinstall it yet since i need to get some work done. Hope it helps in some way.
I have the same problem after flashing the stock firmware thru Odin on my S6 from Cricket. I also tried Factory Resert and Wiping the Cache, nothing seems to help at all. I get the annoying message about the IMS service. I've tried clearing the cache from contacts, ims service but no luck at at. Is there any other ROMs out there for the S6 from Cricket. Right now my phone is completely stock and has no service. Any word of advice would help, Thanks !
Edit: I flashed the CSC file thru odin and it got rid of the IMS error but now I have no service.
SRobby said:
Just wanted to throw my 2 cents in here, i woke to this lovely issue, which was rendering my phone unusable. I use a program call YouMail for voicemail, creeps my friends out when they get to my voice mail. Uninstall this program after wiping every cache imaginable, voila, no more issue. I haven't tried to reinstall it yet since i need to get some work done. Hope it helps in some way.
Click to expand...
Click to collapse
Not an expert in any sense of the term, so ignore this if it's dumb. When the OP and others having this issue are bringing your phones back up, does the issue start prior to phone setup? Or is your Google account restoring some app that could be causing the issue?
it didnt solve my problem
I have the s6 edge though ..do i have to wipe and install the rom again??
Unfortunately ims has stopped working pop up
I noticed the spinning sync icon at the top my s7 phone. It was constantly trying to sync my messengers app to the cloud. (I tuned the sync function off an it seems to have stopped the annoying message from popping up. :good::fingers-crossed:
eeee
boristhebladexx said:
I was attempting to return the phone to stock so I could sell it. I flashed the Cricket firmware, and ever since then I get the IMS service error. I can't flash a new ROM because I unrooted through Pingpong Root. When I flash through Odin, I only flash the AP .tar. Would it make a difference if I flashed all 4 (BL, AP, CP, CSC)?
Click to expand...
Click to collapse
just root the device an then install root unistaller
find all apps with the word ims
unistall all apps
restart phone
Magic!!!!
My Advanced Calling is not working. When I go into the AC settings it says it's already activated (see attached pic) yet I have no on/off button or anything giving me control of it like my girlfriend has on her unrooted, stock G4.
I am rooted on OC3, no roms or anything just stock. But for what it's worth I also could NOT get it to work when I was unrooted either.....
Anyone else having issues?
Factory reset
Same here.
dobbs3x said:
Factory reset
Click to expand...
Click to collapse
Don't wanna lose root and have to do the whole process over again :crying:
I am having the same issue, went through various reset and disable/enable on verizon's end. They are saying the only option left (in their troubleshooting tree anyways) is a factory reset, which I would ideally like to avoid.
Is there any benefit to an on device factory reset rather than pushing the stock OE2 via Odin?
I wonder if I did a factory reset, got AC to work, then re-rooted, if the AC would stick and continue working alright with root? Because I want both...
Ok guys so here's what I did.
I spent a ton of time in a support chat with samsung to no avail.
I finally flashed via odin, OE2 software (which was the out of box software for me) Rebooted and upon noticing that it wasn't a "full wipe" decided to do a factory reset.
Then I booted into recovery and performed the factory reset. At this point advanced calling was still listed as enabled on my verizon account.
I start up the phone, set it up (and deal with the annoying OTA download which I of course did not install) and the DT Ignite app pulls, plus other application updates. Lo and behold Advanced calling is available on my device. I download pingpongroot, perform it, verify it, and now I'm off to the races of getting my device back the way I wanted it.
I have titanium backup installed and I froze the "System Update" program and deleted the update.zip file from ./cache/fota. DT Ignite has also been disabled via the application manager.
I still have advanced calling and have verified it functions properly.
My only slight concern at this point is I have yet to reinstall adaway. Other than that I have performed all the major tinkering I did last time.
Hope this helps.
In short, an OE2 odin pull followed by a factory reset worked fine for me.
- JasonVaritekMVP
JasonVaritekMVP said:
Ok guys so here's what I did.
I spent a ton of time in a support chat with samsung to no avail.
I finally flashed via odin, OE2 software (which was the out of box software for me) Rebooted and upon noticing that it wasn't a "full wipe" decided to do a factory reset.
Then I booted into recovery and performed the factory reset. At this point advanced calling was still listed as enabled on my verizon account.
I start up the phone, set it up (and deal with the annoying OTA download which I of course did not install) and the DT Ignite app pulls, plus other application updates. Lo and behold Advanced calling is available on my device. I download pingpongroot, perform it, verify it, and now I'm off to the races of getting my device back the way I wanted it.
I have titanium backup installed and I froze the "System Update" program and deleted the update.zip file from ./cache/fota. DT Ignite has also been disabled via the application manager.
I still have advanced calling and have verified it functions properly.
My only slight concern at this point is I have yet to reinstall adaway. Other than that I have performed all the major tinkering I did last time.
Hope this helps.
In short, an OE2 odin pull followed by a factory reset worked fine for me.
- JasonVaritekMVP
Click to expand...
Click to collapse
I'm in a similar situation in that I have the same build and rooted. VZW Tech support advised me to use Software Repair Assistant. Does anyone know if this will affect my ability to root again, I mean once it restarts and does any auto updates? Also, does it restore all my data, settings, pictures, etc?
molgen said:
I'm in a similar situation in that I have the same build and rooted. VZW Tech support advised me to use Software Repair Assistant. Does anyone know if this will affect my ability to root again, I mean once it restarts and does any auto updates? Also, does it restore all my data, settings, pictures, etc?
Click to expand...
Click to collapse
I have never used the Software Repair Assistant tool but I'd be pretty wary of using a tool when I don't know exactly what it is doing. I'd hate to accidentally permit something to make my phone un-rootable. If you haven't tried re-flashing OE2 followed by a factory reset I'd give that a shot first.
- JasonVaritekMVP
I just purchased a new S6 today from Best Buy. I was lucky to get a OE2 version, saw it on the box labe before I bought it. I would like to root and install a ROM but I want to wait until my 14 day return period is over in case I'm not satisfied and decide to do something else. The prompt to update pops up constantly. It's very annoying and I'm concerned I may accidently tap the update button. I'm coming from a S4. On the S4 I was able to use Root Explorer to rename a couple of system files to stop the request for updates. Since I'm putting off rooting until after 14 days that method is not possible. I cannot uncheck to automatically upgrade because when I go to system update I only get the "update ready to install" message. I tried booting to recovery and wiping system cache but that had no effect. Any suggestions? Thanks
I used titanium backup to freeze mine but I know that requires root access... Before I had that I would constantly keep my phone in airplane mode and set mobile data limit low so it wouldn't dl it... Just an FYI I'm on a rooted gs6.. Still no exposed for our phones, it's for 5.1.1 and there's the risk for stage fright as its not patched on the root able version.
templton said:
I used titanium backup to freeze mine but I know that requires root access... Before I had that I would constantly keep my phone in airplane mode and set mobile data limit low so it wouldn't dl it... Just an FYI I'm on a rooted gs6.. Still no exposed for our phones, it's for 5.1.1 and there's the risk for stage fright as its not patched on the root able version.
Click to expand...
Click to collapse
Thank you very much for the reply. Someone on another forum suggested I do a factory reset, don't enter any user information during initial setup and disable auto check for updates. I tried that but apparently you can no longer stop checking for firmware updates. So I said screw it and rooted last night. I can always Odin back to stock if I decide not to keep the S6.
Eddie Hicks said:
Thank you very much for the reply. Someone on another forum suggested I do a factory reset, don't enter any user information during initial setup and disable auto check for updates. I tried that but apparently you can no longer stop checking for firmware updates. So I said screw it and rooted last night. I can always Odin back to stock if I decide not to keep the S6.
Click to expand...
Click to collapse
The smartest thing to do would be to root, freeze the SDM, then, If you no longer want the device, unroot using Odin
Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.