Hello xda community. I have a pretty large issue that affects my Epic. I recently had my Epic broken by blunt impact to the screen. So I sent it in and they sent a replacement in less than a day. I had Frozen 1.2 on my old Epic, and I had zero issues. But since I got my replacement, its been nothing but a hassle.
It doesnt get nearly as good battery life, it randomly reboots to the ACS logo, then endlessly cycles until the battery is pulled. Then when its turned back on, everything force closes, rendering the phone un-usable. The only remedy is to go to Clockwork and repair permissions. This will fix it for half the day.
Any advice?
bbecker42 said:
Hello xda community. I have a pretty large issue that affects my Epic. I recently had my Epic broken by blunt impact to the screen. So I sent it in and they sent a replacement in less than a day. I had Frozen 1.2 on my old Epic, and I had zero issues. But since I got my replacement, its been nothing but a hassle.
It doesnt get nearly as good battery life, it randomly reboots to the ACS logo, then endlessly cycles until the battery is pulled. Then when its turned back on, everything force closes, rendering the phone un-usable. The only remedy is to go to Clockwork and repair permissions. This will fix it for half the day.
Any advice?
Click to expand...
Click to collapse
The force closing is probably due to not having Journaling on.
I believe in the SRF 1.2 OP, there is a JournalingOn.zip, flash that (no wipes) and that should stop the force closing.
If it still is unstable for you, I recommend just reflashing the ROM.
Hope this helps.
Follow Acer's directions. If for some reason you still have an issue, then I'd recommend redownloading the rom.
You may also want to try a different kernel.
nikon120 said:
Follow Acer's directions. If for some reason you still have an issue, then I'd recommend redownloading the rom.
You may also want to try a different kernel.
Click to expand...
Click to collapse
Exactly right
Sent from my SPH-D700 using XDA Premium App
I had friend who had the same issue. He went back to SFR1.1.1
then installed ACS updater and flashed SFR 1.2. That fixed his problem. I did it that way too and have not had any issues. Calibrate battery after flashing.
Sent from my SPH-D700 using XDA App
That sort of worked. It made it take longer for things to get hosed over again.So I tried resetting it to stock then flashing EG22, but each time I flash EG22, it doesnt do anything.The version stays at 2.2.1. What am I doing wrong?
What did you flash that is EG22?
Sent from my SPH-D700 using XDA Premium App
In order to better assist you, can you give us a step-by-step listing of everything you are doing? The files you are using with version #'s and your computer OS (with bit version).
I would recommend a full wipe of the phone, to remove any corrupted data
then do a clean install of SRF 1.2
then install the zip to turn on journaling
note: DO NOT use the reboot option until AFTER you have turned on journaling
What I did last night was returned it to factory stock EC05.
Im working with Windows 7 Home x64 on a Mac Pro, because for some reason neither Epic I've ever had will work with my custom built computer.
I flashed the EG22modem.bin with Odin 1.61. That didnt seem to do anything.
So later today, I am going to try this
http://forum.xda-developers.com/showthread.php?t=1184134
The modem only changes the baseband..
regardless, imo it sounds like the problems you are having are due to restoring backups.. is that the case?
I installed this
http://forum.xda-developers.com/showthread.php?t=1205024
and everything is hunky dory in the hood. Thanks for all the help
Related
I honestly cannot find the cause of this. I Have tried everything in my power to try to fix this problem but absolutely nothing seems to work. When using my phone regularly (only on froyo) my phone will get very very hot and then start a reboot loop where it keeps rebooting and rebooting and rebooting. I have the official 2.2 update. Currently not rooted but S-OFF. I wanted to see if the root was causing any problems but im still getting the reboots. I Love my Inc. and i love the AMOLED screen. I want to be able to fix this problem so i dont get stuck with a ****ty replacement. PLEEZ HELP MEEZ
first thing would be to tell everyone what ROM you're on and if you're running setCPU.
Sent from my ADR6300 using XDA App
mzmartipants said:
first thing would be to tell everyone what ROM you're on and if you're running setCPU.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
He said that he is using the stock ota update already
But if your using setcpu this is a great time to stop
Sent from my ADR6300 using XDA App
nope im running completely stock no rooting apps
I get them everyone in awhile when I recieve a text message in the background. Like if I'm in foursquare, or the internet browser for example. And recieve a text, it'll lock up and restart, sometimes it doesn't clear my uptime which is weird...
Sooooo no one can help?
Sent from my ADR6300 using XDA App
Pleez
Sent from my ADR6300 using XDA App
I get this problem all of the time and I will tell you it has nothing to do with root. In fact, I'm not sure it is even a software issue. I have done multiple factory resets to try to troubleshoot the problem.
There is a thread at AndroidForums about it that I am currently running, but I can't link to it evidently. Look in the Support section for the Incredible.
How did you update? You're running a 2.xx radio, right?
If your problems are surviving a full wipe + RUU, the most likely culprit is that your hardware is failing.
It's a full wipe stock 2.2 and yes I have the newest radio
I was having the same issue with my phone on Stock 2.1, Stock 2.2, custom ROMs, etc. No software updates/configurations would make the random reboots stop. Anything that taxed the CPU seemed to cause my reboots. The easiest way to reproduce was to just start GPS'ing somewhere. Within minutes, the phone would go into a reboot loop that would usually only stop after a battery pull.
I took the phone into VZW while it was doing a reboot loop, showed it to them, and they put in a replacement order for me. The replacement (yes, it's a refurb) has been rock solid over a few days of heavy use. I read that if you had an AMOLED screen, then you're replacement will also be AMOLED.
tl;dr; - random reboots on stock ROM with no mods is probably a hardware failure. Go with a refurb.
Decided to go to VZW and order a replacement. They told me it would be a new phone and not a refurb but I don't trust them. Anyways it comes Thursday. I shall report back my friends. I still find this problem to be so odd
About once a day while texting, a message gets stuck "sending" and I have to reboot the phone for the message to send. I am running stock DK28 with the ACS-dk28-signed ROM. I have seen some people having this issue on Quantum ROM too. Is anyone else having this issue and on which ROMs. Has anyone had it and found a fix? I have done the wipes and resinstalls so thinking it is some cache clearing problem. Will a different Mms.apk fix it?
Thanks.
I had that poblem with viperrom. since going with Nebula, I have not had that issue, however, I hav onl had it on my phone for four days
Sent from my SPH-D700 using XDA App
I had Nebula for a minute this weekend but had trouble getting Sprint Nav back on and needed it Saturday morning for a job so had a massive wipefest and odin'd back to DK28 and put ACS back on so hope that cleared it up. Will see today. Still looking for a ROM with a Sprint and Samsung package included to save the hunt for all the apps.
It's a DK28 feature. I never found any pattern to what caused it, at worst I got it every 20-30 texts (or every 3-4 days for me).
Tried multiple roms and stock DK28, all do it eventually, it is just a matter of time. For some reason early Bonsai roms *seemed* to go longer before the problem appeared (weeks).
DI18 and back don't have the issue, so it is likely the modem... never tried DG27 long enough to see if it was affected.
J had that too and use update prl e everywhere I go it seems when change location its getting stock. Now it went away for now fingers cross.
dito33
Sent from my SPH-D700 using XDA App
Hmm, i'm not having this issue! Interesting.
unique2me said:
Hmm, i'm not having this issue! Interesting.
Click to expand...
Click to collapse
What ROM are you running? Anything special on your install? Wipes? Odin?
Update: After a major wipefest, 3X each and 1X Dalvik, Odin to DK28, then wipefest, then flash ACS-signed-DK28 I am going on day 3 without this issue....keeping fingers crossed. (oops hard to txt that way)
I had this issue even on my stock phone. It seems to happen less since I flashed to sfr, but it is still annoying as hell and extremely hard on my battery life.
Anyone know of any solutions?
LunaticWolf said:
I had this issue even on my stock phone. It seems to happen less since I flashed to sfr, but it is still annoying as hell and extremely hard on my battery life.
Anyone know of any solutions?
Click to expand...
Click to collapse
I found out that clearing level 2 RaM was causing it. Stopped using Program Monitor widget.
Do you BONSAI?
kennyglass123 said:
I found out that clearing level 2 RaM was causing it. Stopped using Program Monitor widget.
Do you BONSAI?
Click to expand...
Click to collapse
I have been clearing at level 2.
Ill switch to just level 1. Thanks
Does anybody have any idea what would cause my Epic to shutdown several times a day and won't power back on without pulling the battery. I have tried doing data factory resets, Odin back to stock, different Roms and it keeps doing it. I've purchased a new battery and it still happens with the new battery. Anybody have any ideas or words of advice to help me fix this problem? Thanks in advance.
Are you rooted and running a overclock or underclock? If you have it set to 100mhz with the screen off some phones have trouble waking up from that. Also, if you are rooted, try going in to your CWM and wiping battery stats. Its under advanced. Make sure you do this when its fully charged.
downyours said:
Are you rooted and running a overclock or underclock? If you have it set to 100mhz with the screen off some phones have trouble waking up from that. Also, if you are rooted, try going in to your CWM and wiping battery stats. Its under advanced. Make sure you do this when its fully charged.
Click to expand...
Click to collapse
Yes its rooted. I have never messed with clock speeds, so it shouldnt be an issue with that I hope. Ive also tried wiping the battery stats as well in CWM. It first started when I flashed Syndicate Rom Frozen a few weeks ago. So I have tried several other roms since then and I still have the same problem. I even purchased a new battery and still have the same issue. Im lost in this one. Im not blaming the problem on Syndicate either, I was just letting you know when I first noticed the problem.
Sent from my SPH-D700 using Tapatalk
What happens when you open the keyboard? Does anything light up? Or does it just continue to stay off?
It stays completely off and blacked out when I open the keyboard. I have to pull the battery in and out to get anything.
Sent from my SPH-D700 using Tapatalk
And youve gone completely back to stock without root. No difference?
Also, the kernels that you have run, are they overclock kernels? What about the one your running now? If so, I think they are overclocked from the get go and possibly set for 100mhz on the low end. You might want to try and find SetCPU on the website here, (there is a free one) and set it to raise the speed on the low end. Also add a profile for screen off that changes to 200-400. It would be free and relatively easy to try.
Yeah I have used Odin to go back to stock. Then flashed new roms. I will try that program out and let you know. I'm using the new Viperrom Synergy now and its still happening. Ill try the SetCPU and let you know if it works. Thanks for all of your help.
Sent from my SPH-D700 using Tapatalk
dazednconfused1144 said:
Yeah I have used Odin to go back to stock. Then flashed new roms. I will try that program out and let you know. I'm using the new Viperrom Synergy now and its still happening. Ill try the SetCPU and let you know if it works. Thanks for all of your help.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I might be wrong, but I think the newest ViperRom is set by default at 200-1000. To reach the 1200 mark, you have to use SetCPU. Same for going under 200 (which is known to cause problems for some folks when the screen turns off).
I just wanted to say thanks for the help. I wanted to update you and let you know I finally found the problem. For some reason it had something to do with restoring my apps and data through Mybackup Pro and Titanium. I finally just started taking out different steps of what I was doing and finally just downloaded all of my apparently directly from the market and the problem went away. No more blackouts. I don't know why that would cause that problem, but it did. Thanks again for all of your replies and help.
Sent from my SPH-D700 using XDA Premium App
I have been having an issue with my phone shutting down on me. When I put it in sleep mode, and after a while try to turn it back on, the phone is completely shut off. The only way to turn it back on is to pull the battery. When it is plugged in, it never does this-even in sleep mode. This is also not ROM specific, it has happened on several different ROMS. Does anyone know how to fix this issue? Thank you for your help!!!!!!!
If you're using setcpu, raise the screen off clock speed.
Texted while driving
Thanks for the suggestion. I am using set CPU. I looked and can't find that setting. How do I get there?
I am getting the same thing on different ROMS. Specifically the latest Midnight and Syndicate ROMS, which are the only two ROMS I have ever ran. It just started this out of no where as well. I was running Midnight for over a week with no issues, and then yesterday it started shutting off multiple times. So, I wiped everything three times, and flashed Syndicate last night, and then this morning it started doing it again. I just Odin'd back to stock, and am going to see how it runs before rooting and flashing again. I would love to hear what could be causing this issue.
I've been having the same issue. I've had it with the latest Syndicate ROMs, Bonsai ROMs, and Midnight ROMs. It's been very frustrating as I've only been able to reproduce the issue after using the phone for a day our two. It only happens when on battery power and when the screen has been off for several minutes. I've always ensured Set CPU is set to minimum 200 mhz and I've also had the issue without set cpu installed, so I don't think that's it.
I've been doing lots of testing to determine what might be causing it and so far I've eliminated the kernel and ext4 as the culprit. I think it must be some relatively new tweak that all the custom ROMs are implementing. My latest theory is perhaps the NCIQ tweaks.
Thanks so much for the input. Hopefully someone can figure this thing out
Sent from my SPH-D700 using XDA Premium App
mpscmedic said:
I have been having an issue with my phone shutting down on me. When I put it in sleep mode, and after a while try to turn it back on, the phone is completely shut off. The only way to turn it back on is to pull the battery. When it is plugged in, it never does this-even in sleep mode. This is also not ROM specific, it has happened on several different ROMS. Does anyone know how to fix this issue? Thank you for your help!!!!!!!
Click to expand...
Click to collapse
I experienced the same issue, and reported it in the Bonsai 4.0.1 thread, as that's the ROM I'm using. I would defnitely like to know about the solution, as it is quite frustrating when this occurs and it does not allow using the phone without the battery power cycle.
Sent from my SPH-D700 using XDA App
Data corruption
I, have found it is best to fully wipe everything.
I installed srf and got freezes and random reboots.
Then i installed cm7, and re-flashed srf from that not a problem since.
This issue has been discussed before,and i suggested this remedy to fix the ailments.
It is tedious but it works just fine.
Not sure what the problem is, but you probably came from an EC05 stock rooted ROM.
I think that is the underlying cause of these problems.
fully wipe your phone 3 times wipe everything flash cm7 ,you dont need to flash the gapps then flash srf or bonsai and watch them run.
So this morning for no apparent reason my phone started freaking out and was flashing FC's on the screen, it appeared to be every app installed, Google, Touch Pro, etc... I pulled the battery, then re-booted and it just started over. I finally went back into CWM and reloaded SFR, then Genocide, then re-enabled Journaling (ran the zip) and everything seems to be okay now (except the battery has been sucking juice worst than being on stock). Just wonderin if anyone else has experienced this? I honestly didn't do anything to the phone, it was in my holster, I pulled it to check email. I love this rom, and I'd rather not go back to stock... thanks for any help.
Sounds like a bad flash. Flash it again only wipe before you do. Do a nand restore>advanced restore data from a known good nand.
Sent from my SPH-D700 using XDA App
and dont forget to calibrate your battery after a fresh rom flash.
This has happened to me on sfr 1.2, 3 times now. For no good reason. I ended up having to reinstall rom a few times when other fixes failed. Since I enabled journaling its been a good boy though.
Sent from my SPH-D700 using XDA Premium App
Thanks all, I did flash again (and yep, wiped x3 before doing it). I had journaling on to begin with (or at least I thought I did, I ran the zip to turn it on). We'll see how it plays out today. I love this rom.... Thanks for all the help.
libracolo said:
Thanks all, I did flash again (and yep, wiped x3 before doing it). I had journaling on to begin with (or at least I thought I did, I ran the zip to turn it on). We'll see how it plays out today. I love this rom.... Thanks for all the help.
Click to expand...
Click to collapse
I had a similar problem when I didn't have Journaling ON so double-check to make sure that you have the turned on after you reflash the ROM.
Goodroid said:
I had a similar problem when I didn't have Journaling ON so double-check to make sure that you have the turned on after you reflash the ROM.
Click to expand...
Click to collapse
Yeah I always turn Journaling on after I flash. It did it again today (for no apparent reason), all of a sudden I started getting FC's (from LauncherPro), so I couldn't get to the home screen or anything. I finally wiped everything again (x3 of course), reinstalled the Rom, then the Kernel, then turned Journaling On, then restored my last backup. It's getting just a little bit old, has anyone else had the problem of LauncherPro just FC for no apparent reason? Thanks!
libracolo said:
Yeah I always turn Journaling on after I flash. It did it again today (for no apparent reason), all of a sudden I started getting FC's (from LauncherPro), so I couldn't get to the home screen or anything. I finally wiped everything again (x3 of course), reinstalled the Rom, then the Kernel, then turned Journaling On, then restored my last backup. It's getting just a little bit old, has anyone else had the problem of LauncherPro just FC for no apparent reason? Thanks!
Click to expand...
Click to collapse
At this point, I would try downloading the ROM again. I would also check out different Kernel. I'm using Genocide 2.0 and it works perfectly.
Genocide 2.0 Kernel: http://forum.xda-developers.com/showthread.php?t=961614&highlight=genocide
libracolo said:
So this morning for no apparent reason my phone started freaking out and was flashing FC's on the screen, it appeared to be every app installed, Google, Touch Pro, etc... I pulled the battery, then re-booted and it just started over. I finally went back into CWM and reloaded SFR, then Genocide, then re-enabled Journaling (ran the zip) and everything seems to be okay now (except the battery has been sucking juice worst than being on stock). Just wonderin if anyone else has experienced this? I honestly didn't do anything to the phone, it was in my holster, I pulled it to check email. I love this rom, and I'd rather not go back to stock... thanks for any help.
Click to expand...
Click to collapse
We have the same thing with my Wife's phone. It started after her phone shut down from low battery. Then BOOM Force Closes, in Swype and Google Apps. I had to do a full wipe 3x and reload the ROM to get it to work again. MAJOR PITA!
Especially because she is much less forgiving of phone "flakyness" than I am.
Thoughts?
Snowdog1967 said:
We have the same thing with my Wife's phone. It started after her phone shut down from low battery. Then BOOM Force Closes, in Swype and Google Apps. I had to do a full wipe 3x and reload the ROM to get it to work again. MAJOR PITA!
Especially because she is much less forgiving of phone "flakyness" than I am.
Thoughts?
Click to expand...
Click to collapse
That's how I got it back to working. The 2nd time was from Launcher Pro FC'ing, but I wiped it again and re-imaged the Rom and Kernel. Then turned Journaling back on. I think it just gets in a "weird" state sometimes. It takes me about 3 minutes to re-run everything (including the backup once I re-image) and I guess I just don't see it as any worst than stuff I have to do to PC's all day long when testing....haha
Same happened to me. Just reinstalled rom and kernel
Sent from my SPH-D700 using XDA App