I have a Samsung Epic 4g that I have flashed to cricket, and I am having significant problems with the phone. It initially worked fine, but it eventually started shutting off on its own, dropping calls, and other issues. I thought it might be one of the battery saving programs I had tried, so I re-flashed the phone to a different Rom. The problems continued, so I tried to flash the CWM El30 to FC09, but it gave errors and would not process. I am also unable to install Google Apps, and the PlayStore would not load but gave connection errors.
I am leaving for a business trip tomorrow, and need to know if this is a hardware problem or a software problem that can be somehow fixed, so I can get a replacement phone. Does anyone have suggestions on how to fix the software issues, or ??????
johnmbailey said:
I have a Samsung Epic 4g that I have flashed to cricket, and I am having significant problems with the phone. It initially worked fine, but it eventually started shutting off on its own, dropping calls, and other issues. I thought it might be one of the battery saving programs I had tried, so I re-flashed the phone to a different Rom. The problems continued, so I tried to flash the CWM El30 to FC09, but it gave errors and would not process. I am also unable to install Google Apps, and the PlayStore would not load but gave connection errors.
I am leaving for a business trip tomorrow, and need to know if this is a hardware problem or a software problem that can be somehow fixed, so I can get a replacement phone. Does anyone have suggestions on how to fix the software issues, or ??????
Click to expand...
Click to collapse
if it gives you issues on stock fc09 i would say hardware. flash to fc09 stock from here and try. remember to click reset partition if you are on a bmt rom.
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
robertlewisca said:
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
Click to expand...
Click to collapse
I was having the same exact problem. I even changed phones thru warranty. The new phone did the same thing. New SIM card didn't help. I had a guy at tech support to push the update to me.
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
IDK, co-worker with a Skyrocket has had the same issue, but he doesn't care about the update, so he hasn't bothered to get it resolved.
If I didn't have a red GS3, I could goof around and tell you that is what the problem is...
Actually, if it were me having the issue, I'd walk into AT&T and have their guys mess around with it. No telling why some have more issues than others.
robertlewisca said:
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
Click to expand...
Click to collapse
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Not really a solution but you could install this http://forum.xda-developers.com/showthread.php?t=1902178 to be fully stock LH9 with Root. Or use the OTA zip from here http://forum.xda-developers.com/showthread.php?t=1896773.
aboveusonlysky said:
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Click to expand...
Click to collapse
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
78c10 said:
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
Click to expand...
Click to collapse
You mention in your signature that your phone is rooted. So, did you update OTA then root, or did you update after rooting through some other method? The challenge some of us are having is that we are not rooted, and cannot update OTA because of the 'server error' it gives us everytime we try.
Problem Solved - for me at least
Well, the problem is solved for me, and I thought I would share what I found out here in hopes it helps someone else.
First, I had the phone replaced under warranty. It appears to be a brand new phone. When I received the new phone, I started it up, went through the normal startup stuff - entered my Google account information, it backed up my info and settings. Before I loaded any apps, I went straight to the update screen, and tried to check for an update. I again got the 'communication failed' error. Bummer.
So, then, I did a factory reset on the new phone, but this time instead of entering the initial Google account info on the startup screens, I skipped through all of the initial screens, got to the home screen, then went straight to the update screen - and this time it worked! So, it must be something to do with the initial screens, and entering Google account information that caused the problem.
Then, I got to thinking - perhaps this might work on my old phone too. Since I just got the warranty phone today, I still had my old phone (which needs to be sent back). So, I did a factory reset on it, skipped all of the initial screens where it asks for Google account information, and it still didn't work on the old phone. So, I'm not sure what the original issue was.
By the way, after the update installed on the new phone, and I went through and entered all of the Google account settings, and then checked for the update again, and there was no error.
So, perhaps this might be helpful for others?
Hi guys. I am stuck at an impasse here and I know someone here will be able to help.
My wife and I just bought two Samsung Galaxy 2 Epics (refurbished) from the retailer Glyde. I purchased from them because they are partnered with my new carrier, Ting.
My phone activated and ported my number with no issues. Everything works perfectly.
Her phone appeared to activate and then rebooted. It will not go past the Sprint 4G animated opening. I have rebooted, wiped cache, and done factory reset. Still ... 4G logo animation appears and the screen either goes black (appears to shut down) or it just stays on the 4G logo without moving on and then a few minutes later goes black. The phone worked fine before we tried to activate it. It logged in her gmail and connected to wifi.
I am able to get to recovery mode. I was probably going to root and cyanogenmod mine. In your opinion, would this type of action possibly correct the problem with her phone? Is it possible to root and flash the original stock rom in a situation like this? Would that even work seeing that factory reset did no good?
I have contacted Glyde and am waiting - they may or may not replace. If they do replace that is a 2-3 week turn-around. I would rather work some magic here, if possible.
Thoughts and help are appreciated!
Brian
You might have to Odin a stock rom most likely
? Powered By My Moga Pro ?
9/10 Times if you can Odin it, you can fix it. BUT, restoring to stock via Odin will break your flash.
Chances are your flash is already cracked up a little.
A simple cricket nv gen google search combined with Odin, drivers, and DFS Tool. You'll be able to get it back up and running smoothly.
And if your device was on a stock rooted ROM, and you have a custom recovery, then flash a 4.1.2 Custom touchwiz ROM. That way, no programming will be lost.
If you decide to flash an AOSP/AOKP ROM like Cyanogen you could possibly break your flash.
2 cents.
fixed
Would you guys believe it was the battery? It was. I swapped batteries and the other phone started doing the same thing. Battery replaced and problem solved. I guess I panicked, but it sure seemed like a software issue. Thanks for the advice.
Got my Note 4 rooted it right away with no issues been running smoothly for a week or so. This weekend it has just got into a bootloop several times, the only thing I have been able to do is wipe data and start over. I mean I have Titanium Backup of all the apps but it is still a hassle. The only thing I have noticed is in the stock recovery it says "dm-verity failed"
I have read running a non-stock kernel will take car of this but not sure this is the issue. Has anyone else had this issue or have a solution?
It's the root. That root is causing that error to pop. Un-root your device.
I am trying to correct this issue as well for s friend who bought a used note smn910p.
It boots up
Its in the abnormal factory reset, reactivation loop i have to provide samsung account from unknown previous owner
rooted s5 smg900r4
fixed dm verity issue using kies3, updated firmware and initialization option.
rooted s5 smg900r4
All,
I just upgraded my wife's phone and would like to sell her old one, a Sprint Samsung Epic 4G Touch. based on my reading, the best approach for wiping the phone's data is to encrypt it. I have been trying this, but it keep failing with "Encryption failed: Unable to complete encryption due to interruption..."
The phone had been rooted, and thinking that that could be the problem, I downloaded a stock kernel and installed it. However, the problem persists. Is there anything else I can try?
After trying the process of resetting the phone, reflashing it, and encrypting several times, I thought that the problem was resolved - the progress bar for the encryption got all the way to 98% before it died. I tried again and it crapped at around 20%.
I am stuck - please help.
Thank you.