[Q] Custom ROM flashing without SIM, also /system wipe question - Verizon Samsung Galaxy S III

Hey guys. I just bought a Verizon Galaxy S3 from eBay. I rooted it, flashed a custom rom, bricked it, etc. Now I'm back to stock. I have a new SIM card but it's not activated yet. It will be activated in a couple days. I was going to flash Synergy Rom until I read that it does this thing when you flash their custom kernel; it auto picks what carrier your phone has and flashes the files accordingly. Since I don't have a carrier, I was wondering what would happen if I flashed it. I'm signed in on my gmail which I use on my original Galaxy S also. That one has T-Mobile. I'm a little worried that it will somehow know that my gmail is attached to T-Mobile and flash T-Mobile files. I know I could just use stock kernel and not go through all this, but I figured if the question hasn't been asked, then it should be asked.
One last thing. I was reading that I should wipe cache, dalvik, and (I could but I didn't have to)-wipe /system, before flashing a new rom.
I was wondering if I should wipe /system or if that would ruin the custom bootloader + SU, or custom bootchain, or anything else I did to my phone.
(I know I said I'm back at stock but then I went ahead and flashed the custom bootchain and "SU+Bootloader_FIXED.zip".)

So what is the question? Is your bootloader unlocked? Some ROMs mention to have this unlocked for whatever reason I'm unsure.
You don't need to be activate to flash (I didn't have sim interested when I flash synergy)
For a wipe I did the following.
Wipe cache partition
Wipe dalvik cache
Format /system
Format /data
Format cache

Reply
I guess basically what my question is, is what is inside "/system"?
And, should I wait to flash the custom kernel that comes with synergy rom until i have an activated SIM in my phone; so the auto checker in the kernel detects that I have verizon? Or does it not look at my SIM to determine that, rather at some other part of my phone?

I believe the OS is in /system and if you didn't wipe this you put a ROM on top of another ROM. Follow my procedure when you flash a fresh ROM.
Maybe someone can further explain your question about the auto checker because this is not something i've heard of.

Alright, so I just did what you said and started flashing Synergy Rom. One thing that I immediately noticed was, that it took longer to write to /system, which I'm guessing is good, because it actually had the chance to write all the files it needed.
Also, because I left the custom bootchain on there, it flashed the stock kernel while doing the rom installation and it went through OK. Which didn't happen the first time; probably because I flashed the stock bootchain and then the rom.
I'm booting into the phone now. For the first time in 3 days it's not stuck on the Samsung boot logo!
Thank you so much for that recommendation!!
It seems as if it's working
:good::good:

I will need help flashing without a sim card, i will be getting my gs3 soon and flashing it to page plus. Therefore my 4g doesn't work and i have no sim card. So i will using aosp ROMs cuz i just flat out hate touch wiz. Can any of you gs3 veterans help? Please and thank you!
Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2

Related

[Q] D2G saved from Brick now boots into Recovery every reboot

Hey,
So I was a victim of not enough reading and doing to much at one.
I had a rooted stock GB ROM on my D2G and through easy enough, BootStrap, CWM via Rom Manager and flash CM 7.1. All should be good.
WRONG
I got hung up at the red M logo and try various things to revert to stock b/c there was no way I was getting into the CWM recovery console again.
After failing at every corner a random and 10,000th battery pull I ended up in CWM.
Since the one thing I did right was a nandroid backup I was restored it and the phone booted. I then shut down, dropped in SIM (rogers) and booted back up.
Now everytime I reboot it takes me to CWM. Forcing me to hit reboot system now otherwise it sits in recovery.
Any way to have it not boot into recovery? Just boot normal?
Thanks.
First, if you are on Rogers in Canada - do not bother trying CM7 - doesn't work properly on GSM. Stock firmware will be much more useful.
Second - There are two CM7's (if you are determined to try it) - one is Froyo base (the one found on CyanogenMod site) and the other one is GB base. It seems you flashed the Froyo based one on top of Gingerbread thus you ended up stuck on red M logo. To fix the problem - you have to either try flashing GB base CM7 from CWM or (better) SBF and start over. Again - if you want Froyo based CM - use the 2.4.29/2.4.33 SBF. If you want to try the Gingerbread based one (check rootzwiki for more info), flash the GB SBF that was recently made available or flash 2.4.29/330 and OTA to 4.5.608. Root, CWM and so and so. But pick your CM7 package carefully!
But if you are not on CDMA - you better don't waste your time with CM7.
Thanks for the reply. The phone boots fine now.
One question tho.
I have some how lost the Accounts and Sync Option.
If I do a factory reset (from phone settings not recovery mode)will I loose root and will I loose the Gingerbread OTA update that was done on the phone before I got it?
Or do you know how to recover something like Accounts and Sync?
I am going to be sticking with the Stock ROM
Have you disabled any system apps? This could be a reason for broken accounts.
As far as factory reset, either from phone menu or from recovery, will not remove root or any other changes you might have made in /system. It simply deletes /data partition.
Sent from my Galaxy Nexus using Tapatalk
leobg said:
Have you disabled any system apps? This could be a reason for broken accounts.
As far as factory reset, either from phone menu or from recovery, will not remove root or any other changes you might have made in /system. It simply deletes /data partition.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks I discovered that I had deleted the "Setup.apk" without backing up.
Retrieved that app from another member and all is well.

Rooted, Backed-Up, Flashed to Synergy...First timer...How to load backups now?

So I left Apple, came to Android, rooted my VZW GS3. First time I've ever done anything like this, so I'm new to it. I backed up EVERYTHING using TiBu, did the IMEI backup, Full system/image backup using CWM, unlocked bootloader, etc. Then I flashed to Synergy r46 (august 20th - yesterday's release).
Now I'm at work and my back-up pulled my contacts via Verizon's server, but how do I get back EVERYTHING else? SMS/MMS logs, call logs, apps, app data, etc? Do I need to download TiBu again (fresh from google market) and then load my backups off my Ext-SD card, or what? I guess I'm a bit confused as to where my TiBu items were even stored/saved...I assume it was the ExtSD card, otherwise I would have lost them all upon flashing to Synergy, correct?
Any help to get all my apps and data back on my newly Synergized phone would be awesome!!!! Thanks in advance!!!
Yes download titanium and then point it to the directory you had your back ups saved to (its sd card by default, and which is your phone storage btw) then tab to backup/restore click the check, then once your app data populates, and select run next to restore apps and data.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Sent from my SCH-I535 using Tapatalk 2
I used titanuium backup pro to back up all my Apps and system data. And when I flash a new rom I just redownload titanium pro and it automatically restores all my Apps and system data. It is the easiest app I have used. So to answer ur question.....back up ur apps with titanium then after flashing a new rom go and redownload titanium and restore your system data and apps or just apps alone if that's what u prefer? Does that answer ur question or would u like more detailed instructions?
Sent from my SCH-I535 using xda app-developers app
Welcome to android!
Sent from my SCH-I535 using Tapatalk 2
Another very nice feature of Titanium Backup is its ability to pull data from CWM nandroids. There have been a few times where I was quick to flash a new rom without doing a backup of my apps. This has saved me much time from having to re-flash the nandroid backup, backup via TB, then re-flash to the new rom.
voodoomanx said:
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Click to expand...
Click to collapse
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Weioo said:
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Click to expand...
Click to collapse
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
dan_joegibbsfan said:
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Click to expand...
Click to collapse
I'm fairly certain I did "wipe data/factory reset," I just wasn't sure how it was labeled when I typed that out, but that's really ringing a bell. I think I may have gotten the errors before (using ROM Manager) because I hadn't factory reset? Seems to me I'm good to go! However, my question regarding TiBu still remains.
Edit: In regards to informing you about r46, I'm not sure what to report as I've never used a previous Synergy and have no idea how to compare, other than to the rooted stock ROM. I have heard reports of battery life being worse than the stock ROM, and I can confirm this. I've barely used the phone since I flashed to Synergy and it's dropped 15% battery life in ~3 hours. Seems faster than before but I'm unsure.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
dan_joegibbsfan said:
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
Click to expand...
Click to collapse
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I used the EZ-unlock app in the play store. I did see that a custom kernel was loaded however when i flashed back to my nandroid (stock rooted) I am back on the orignal kernel. Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I agree I have yet to have Synergy boot loop although I'm still on 1.7. I would try to wipe cache and dalvik cache and see if that helps or you could be over clocking to high.
Sent from my Transformer TF101 using xda premium
nguyenvn said:
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
Click to expand...
Click to collapse
I don't know the answer to that specifically. All I know was that I was stable before another modification I made (that said it wouldn't work but I tried it anyway). Since restoring from backup and reloading Synergy and theme I have not seen any weird rebooting anymore.
nguyenvn said:
Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
Click to expand...
Click to collapse
I'm not familiar with that method. I've only used Odin, even when I did have to redo everything I used Odin to stock de-bloated rooted .md5 then CWM'd from there.
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
nguyenvn said:
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
Click to expand...
Click to collapse
That may very well be the issue. 1.9ghz is a very aggressive overclock, and i wouldn't be surprised if was unstable on a good number of phones. Synergy's supposed to boot at 1.5ghz max by default - I don't know whether that was successfully implemented. I personally think it's silly to OC such a capable phone, anyway. Back in the days of the Droid 1, an overclock from the stock 550mhz to 800mhz-900mhz was an enormous improvement. Today, the only thing OCing the S3 gets you is a <10% improvement in Quadrant, more heat, possible instability, and no perceptible difference outside of those silly synthetic benchmarks.
Anyway, in this thread, there seems to be a fair bit of confusion as far as what's what in the android partitions. I'll give you a short rundown.
"aboot" is what's referred to here as the bootloader. It checks to see whether the next partition in the boot sequence, "boot", is authorized. When you unlocked your bootloader, you overwrote aboot with a version that does not perform that check.
"boot" contains your kernel. If your ROM has a custom kernel, it contains a boot.img to overwrite boot.
"system" is the meat of the OS. This is primarily what ROMs flash.
"data" contains all of your apps and settings. When you perform a factory reset, you're reformatting data. If you're flashing a ROM that is significantly different from what you're on now, some of those old settings and data can cause errors, force closes, random reboots, and boot loops. When in doubt, wipe data before flashing a new ROM. When going from one version of a ROM to a newer, very similar version of the same ROM (nightly to nightly), you probably don't need to wipe data, but make a backup just in case. dalvik-cache is also in data; if you wipe data, you've automatically wiped the dalvik cache. It's redundant to wipe data and then wipe dalvik cache.
"cache" is just that, the cache partition. Clearing it won't make you loose anything, at least not anything Android won't silently replace.
So far it seems to be pretty stable on r50. I installed system tuner and brought it down to 1.5 Ghz. I'm not sure why 1.9 is set to default. Doesn't seem like a good idea to me. Thanks all for the help/advice.

[Q] n00b seeking help with custom ROM installation

Long time lurker (though I can't say I always understood everything I read), first time poster.
I've had several iPhones in the past and I finally decided to try the other option. I got a Verizon GS3 last November and I couldn't be happier.
However, like many others, I'm looking to get more from my phone. I do like TouchWiz (I have used a Nexus 4 for a week and didn't like the stock android), so I want to stay with about the same UI that I have now. I did some research and found that Synergy is probably the best option for me in terms of getting a bit more from my phone but still staying with (mostly) the same UI. Of course, getting rid of all the annoying Verizon apps is a huge bonus too.
This is what I have done already:
Used this method to root and unlock my bootloader: http://forum.xda-developers.com/showthread.php?t=2332825
Used TWRP to make a full backup of my phone to an external SD card
Used Titanium Backup to make a full backup of my apps to an external SD card
Here are my questions:
I have the latest Verizon OTA installed (June 20th, I535VRBMF1). I have read all the posts from the last 14 days on the Synergy thread and I think I understand that since my phone has a newer firmware than the one in the latest synergy ROM, I will need to downgrade my firmware before installing the ROM to avoid camera and wifi problems. Is this correct? Someone linked there to I535VRBMB1_firmware.zip. How do I install this firmware? I have ODIN but when I choose PDA it will not let me choose the zip file. When I extract it, ODIN doesn't find anything too.
What kind of wipe should I perform before I flash to Synergy? Should I take my SD card out for the wipe or leave it in? Do I even need to wipe?
Can I install the ROM from ROM Manager or should I always use recovery mode and TWRP?
Is it recommended to just restore my Titanium full backup after the wipe? Should I have backed up everything except verizon apps if I don't want these? Should I just restore those apps where I want my old data (like game progress)?
Thanks in advance for any help. I have learned a lot from these forums but I feel I need a bit more clarifications before I proceed with a task that may be damaging for my device.
Slartibartfast_ said:
Long time lurker (though I can't say I always understood everything I read), first time poster.
I've had several iPhones in the past and I finally decided to try the other option. I got a Verizon GS3 last November and I couldn't be happier.
However, like many others, I'm looking to get more from my phone. I do like TouchWiz (I have used a Nexus 4 for a week and didn't like the stock android), so I want to stay with about the same UI that I have now. I did some research and found that Synergy is probably the best option for me in terms of getting a bit more from my phone but still staying with (mostly) the same UI. Of course, getting rid of all the annoying Verizon apps is a huge bonus too.
This is what I have done already:
Used this method to root and unlock my bootloader: http://forum.xda-developers.com/showthread.php?t=2332825
Used TWRP to make a full backup of my phone to an external SD card
Used Titanium Backup to make a full backup of my apps to an external SD card
Here are my questions:
I have the latest Verizon OTA installed (June 20th, I535VRBMF1). I have read all the posts from the last 14 days on the Synergy thread and I think I understand that since my phone has a newer firmware than the one in the latest synergy ROM, I will need to downgrade my firmware before installing the ROM to avoid camera and wifi problems. Is this correct? Someone linked there to I535VRBMB1_firmware.zip. How do I install this firmware? I have ODIN but when I choose PDA it will not let me choose the zip file. When I extract it, ODIN doesn't find anything too.
What kind of wipe should I perform before I flash to Synergy? Should I take my SD card out for the wipe or leave it in? Do I even need to wipe?
Can I install the ROM from ROM Manager or should I always use recovery mode and TWRP?
Is it recommended to just restore my Titanium full backup after the wipe? Should I have backed up everything except verizon apps if I don't want these? Should I just restore those apps where I want my old data (like game progress)?
Thanks in advance for any help. I have learned a lot from these forums but I feel I need a bit more clarifications before I proceed with a task that may be damaging for my device.
Click to expand...
Click to collapse
1 - You can roll back to MB1, or flash a kernel that supports the camera w/MF1. The camera not working seems to be the primary issue. I know Ktoonsez kernel works as do a couple of others.
2 - Wipe system, cache and Dalvik. You don't need to do anything with your card.
3 - At least the first time, I'd recommend using TWRP in recovery mode to flash your new ROM. Someone else may have a different opinion, but you'll already be in TWRP to wipe everything.
4 - Different people have different experiences with TiBU. Most would recommend not restoring system data, but apps(non-system) and app. data is usually okay.
lvgdgts said:
1 - You can roll back to MB1, or flash a kernel that supports the camera w/MF1. The camera not working seems to be the primary issue. I know Ktoonsez kernel works as do a couple of others.
2 - Wipe system, cache and Dalvik. You don't need to do anything with your card.
3 - At least the first time, I'd recommend using TWRP in recovery mode to flash your new ROM. Someone else may have a different opinion, but you'll already be in TWRP to wipe everything.
4 - Different people have different experiences with TiBU. Most would recommend not restoring system data, but apps(non-system) and app. data is usually okay.
Click to expand...
Click to collapse
I appreciate your detailed response!
I'm probably going to attempt this tomorrow. Will report back with what my results. It looks like BoneStock might be another good option for me + save me the kernel replacement or firmware flash. I have some reading to do now
Slartibartfast_ said:
Here are my questions:
I have the latest Verizon OTA installed (June 20th, I535VRBMF1). I have read all the posts from the last 14 days on the Synergy thread and I think I understand that since my phone has a newer firmware than the one in the latest synergy ROM, I will need to downgrade my firmware before installing the ROM to avoid camera and wifi problems. Is this correct? Someone linked there to I535VRBMB1_firmware.zip. How do I install this firmware? I have ODIN but when I choose PDA it will not let me choose the zip file. When I extract it, ODIN doesn't find anything too.
Click to expand...
Click to collapse
Just to add onto lvgdgts' post: files ending with ".zip" are flashed in recovery, files ending with ".tar" or ".tar.md5" are flashed via Odin.
SlimSnoopOS said:
Just to add onto lvgdgts' post: files ending with ".zip" are flashed in recovery, files ending with ".tar" or ".tar.md5" are flashed via Odin.
Click to expand...
Click to collapse
Thanks!
I decided to go with BoneStock 3.1. Whole process took less than half an hour. Used TWRP manager to wipe+install the ROM. Restore from Titanium restored 95% of my stuff, only needed to manually restore my text messages.
Thanks for the help!

[Q] "Unfortunately, IMS Service has stopped"

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

LG nexus 5 (hammerhead) android version 6.0.1 question?

hey guys, i could not find anything similar to what i'm about to ask in the forum, and if it is there but i missed it somehow, i apologize! as of lately i have been working entirely too much and sleeping very little!
lol so here it is, i have the hammerhead d820 version, and it is currently running the 6.0.1 version of android. I rooted it with nrt, and now i would like to flash a custom rom for my very first time! so, i just want to know if i would be able to go from the current version of android that i am running, (marshmellow) would i be able to skip nougat and just flash oreo?
or is that not going to work?
- a confused chick
lol thanks for the help!
Flashing new ROM in almost all cases completely wipes /system partition (and /boot partition) and overwrites it with new ROM data so it doesn't matter what was flashed before as everything there is replaced.
As root is usually installed to /system partition it will be gone after reflashing, unless new ROM already contains root (if not just root it again).
After flashing new ROM through custom recovery (TWRP/CWM) make sure to do factory reset (wipe /data partition). It wipes all your data from the phone so make a backup before, but is often necessary for new ROM to even boot or work reliably.
Halamix2 said:
Flashing new ROM in almost all cases completely wipes /system partition (and /boot partition) and overwrites it with new ROM data so it doesn't matter what was flashed before as everything there is replaced.
As root is usually installed to /system partition it will be gone after reflashing, unless new ROM already contains root (if not just root it again).
After flashing new ROM through custom recovery (TWRP/CWM) make sure to do factory reset (wipe /data partition). It wipes all your data from the phone so make a backup before, but is often necessary for new ROM to even boot or work reliably.
Click to expand...
Click to collapse
Oh wow i have been so insanely busy over the past month and a bit that i did not even see your reply til just now!!
what a piss off my hammerhead ended up being.... I had the damn thing for less than a month, the p.o.s ended up just refusing to take any charge at all.
well off to the box of fail with you, hammerhead! Was great to almost get to know ya, hahaha... *sigh*
Anyways i am now using the Galaxy SM-G903W (the s5 neo, and you bet i have root privileges! and a phone that i previously owned for a short time, the HUAWEI RIO-AL00 (MAIMENG 4) has made it's way back into my "teck desk"
P.s; to the mods and to all of my fellow devs and anyone that is a part of the forum..
PLEASE accept my sincere apology for how many different topics that i seemingly have managed to squish into the thread here that i originally created... I am going to continue my search to attempt to answer my questions, and if nothing jumps out at me please, everybody stay tuned for the next thread created by yours truly;
Xo cheers =)
Sent from my s5neoltecan using XDA Labs

Categories

Resources