First off, i always do a nandroid backup before flashing a theme or ROM.. which usually saves me.
I've noticed recently that, pretty much every time I clear the cache 3 times, then clear Dalvik 3 times, (in clockwork 3), after flashing anything, upon reboot, i get the boot animation, then vibrate, then double vibrate > bootloop.
This seems to happen even if I don't flash anything following the cache clear. Has anyone else had this experience? I'm more interested in the cause of this. I've since restored everything manually, but I'm a total flash/pushaholic, and looking for ways to avoid this situation. Any help is appreciated.
Sent from my SPH-D700 using Tapatalk
Did you properly shut your phone down prior to the cache wipe? As in power off then wait for the vibrate to signal it shut off.
decalex said:
First off, i always do a nandroid backup before flashing a theme or ROM.. which usually saves me.
I've noticed recently that, pretty much every time I clear the cache 3 times, then clear Dalvik 3 times, (in clockwork 3), after flashing anything, upon reboot, i get the boot animation, then vibrate, then double vibrate > bootloop.
This seems to happen even if I don't flash anything following the cache clear. Has anyone else had this experience? I'm more interested in the cause of this. I've since restored everything manually, but I'm a total flash/pushaholic, and looking for ways to avoid this situation. Any help is appreciated.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Why are you clearing cache and dalvik 3 times after flashing? Once should be plenty sufficient..
As for the cause, I would assume its the dalvik clearing.. cache is its own partition, where the dalvik is is on the system partition, and you are probably corrupting it with excessive writes..
Sent from my SPH-D700 using XDA App
Also remember that the version of CWM 3 we run on the Epic currently is not official. It can be a PITA sometimes. Dameon has done an awesome job porting it so we can have ext4, but I'm hoping some of these issues get cleaned up when we have the official version.
063_XOBX said:
Did you properly shut your phone down prior to the cache wipe? As in power off then wait for the vibrate to signal it shut off.
Click to expand...
Click to collapse
Hm, I almost never do that, but I will start. I usually do the death grip, then reverse death grip into recovery. (Can i trademark that name?)
@Mattalica: also good to know I'm not totally alone on this. I hadn't considered that. Thk God for nandroid + unyaffs
@Chris41g: i was trying the cache wipes on their own just to try to isolate the issue.
Thx everyone for feedback.
Hm, I almost never do that, but I will start. I usually do the death grip, then reverse death grip into recovery. (Can i trademark that name?)
Click to expand...
Click to collapse
If your phone is running a "no-journaling" Rom that will cause corruption.
063_XOBX said:
If your phone is running a "no-journaling" Rom that will cause corruption.
Click to expand...
Click to collapse
Gotchya, yes, i remember reading that- I'm running bonsai 4.01 with twilight 1.1 kernel - i forget off-hand if journaling is enabled , but I'll research.
Sent from my SPH-D700 using Tapatalk
063_XOBX said:
If your phone is running a "no-journaling" Rom that will cause corruption.
Click to expand...
Click to collapse
No journaling alone will not corrupt data. You have to shut down improperly or have a lockup caused by an unstable App (like beta wireless tether) or an unstable overclock/undervolt.
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
No journaling alone will not corrupt data. You have to shut down improperly or have a lockup caused by an unstable App (like beta wireless tether) or an unstable overclock/undervolt.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
And that was what he did, I quote:
Hm, I almost never do that, but I will start. I usually do the death grip, then reverse death grip into recovery. (Can i trademark that name?)
Click to expand...
Click to collapse
063_XOBX said:
And that was what he did, I quote:
Click to expand...
Click to collapse
Yep, I know you know what your talkin about. I just didn't want decalex to take your response out of context, as some have been stating that the lack of journaling by itself causes corruption.
Is the vibrate, then double vibrate during the boot animation (then loop) indicative of "data corruption" ?
Next time it happens, I'll try to logcat.. I'm curious what is actually happening .. unless one of you already knows.
Sent from my SPH-D700 using Tapatalk
Related
I have seached and find reference to this pattern in multiple posts, but never an answer to what it means. Ever since ec05 my phone randomly does the pattern sometimes with no apparent problems or sometimes it happens while loading an app and then it force closes.
Thanks!
Sent from my SPH-D700 using XDA App
try re-flashing and that should solve your problem
Thanks, I will. I was just thinking there must be a meaning to the pattern. I seem to remember my moment did that once in a while also.
Sent from my SPH-D700 using XDA App
DexterDawg said:
Thanks, I will. I was just thinking there must be a meaning to the pattern. I seem to remember my moment did that once in a while also.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Any update if re-flashing fixed it? I'm having that problem as well, so odin again back to DI18 then flash using the update.zip again?
I have been busy all weekend and haven't had time. Will post results tomorrow. I just think there must be a description of what that means since I have had it happen on another android device also.
I think ultimately it may be a bad flash though because randomly I lose my signal and it doesn't come back until a reset. This happens when I am in a low signal area.
DQ
Sent from my SPH-D700 using XDA App
I get this too. Usually when an app is force closing.
younggangsta_s said:
when an app is force closing.
Click to expand...
Click to collapse
This
Sent from my SPH-D700 using Tapatalk
for what its worth, i wend to eb13 with the samsung tool then to ec05 with the update.zip and its still happening though not as frequent, can't even use my phone as my alarm as it will crash with that vibrate pattern and i'll have to pull the battery, looks like may need to take it to sprint again...
jojo08 said:
for what its worth, i wend to eb13 with the samsung tool then to ec05 with the update.zip and its still happening though not as frequent, can't even use my phone as my alarm as it will crash with that vibrate pattern and i'll have to pull the battery, looks like may need to take it to sprint again...
Click to expand...
Click to collapse
Did you root/remove apps? If so please list what you removed.
Sent from my SPH-D700 using Tapatalk
lafronz said:
Did you root/remove apps? If so please list what you removed.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I have rooted before but when I was having problems with stability wanted to make sure I was on stock so both times I upgraded to ec05 its been stock once upgraded from di18 (odined back to it) and currently from eb13 (using samsung exe)
Sent from my SPH-D700 using XDA App
Sorry it took so long to get back here.
I finally had time yesterday to go back to DI18. I couldn't remember the hard reset recommendations so I did that before and after running Odin. I was going to run the update.zip, but got sidetracked. When I got back to my phone it had d/l the OTA. I ran that then did another hard reset and cleared the cache. Then I ran 2.5.5 one click, and I may have even did one more hard reset at that time. (I know a little anal)
I also formatted my SD card (I think I read somewhere that this can be an issue also)
Since then I restored user apps and data through titanium and I have not had a single problem with the vibrate error.
The only thing I haven't tried on my phone is Sprint ID.
I'm thinking there are four possibilities, my flash to di18 may have been bad, the update.zip I used was slightly corrupted or didn't install properly, the SD card had issues now solved by the format, or it's Sprint ID.
DQ
You can view files in data/tombstones/ to find out which app is FCing.
can you elaborate on the hard reset?
jojo08 said:
can you elaborate on the hard reset?
Click to expand...
Click to collapse
vol down, camera, power. wipe date option
sorry maybe "hard reset" isn't used anymore, from the WinMO days.
if this happens to you check and see if you have the whoisit app installed this is what caused it on my epic just uninstall it
The 1-3 vibrate thing means an app has force-closed. If you are getting a lot of this after flashing a new rom and restoring apps and data, it probably means that the data is corrupted or not in a format that the new rom can deal with.
The only time this has happened to me is after I have gone from a rom based on eclair to a rom based on froyo, and even then it was the phone data, not the app data.
DexterDawg said:
I have seached and find reference to this pattern in multiple posts, but never an answer to what it means. Ever since ec05 my phone randomly does the pattern sometimes with no apparent problems or sometimes it happens while loading an app and then it force closes.
Thanks!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This mean that there is some corrupt data and that you need to do a system restore from a previous backup or reflash to fix this problem. Usually this happens when your phone turns off randomly or when you forget to wipe the partition or dalvik cache when flashing a Rom or a system file such as stock browser or keyboard through clockwork mode.
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
So I picked this phone up yesterday. Everything seems great, after about an hr I rooted the phone and installed cwr.
Suddenly after about another hr I got a random freeze and then it shut down, at the time I was browsing the web. Boot it back up and within 4 hrs I got 3 more freezes /shutdowns.
At this point I went ahead and installed EB1.1 this morning hoping this would solve the problem.
Well it didn't, I've had 5 shutdowns in about a 10 hr span.
Is anyone else experiencing this?
Unfortunately I wasn't stock long enough to see if it was caused by root and/or cwr.
Anyone have any idea what could be causing this?
The freezes /shutdowns have happened doing different things and even while not even being used.
[Problem] So it freezes and shutsdown right after and I have to do a battery pull because it won't let me reboot without it.
It happens randomly and quite often.
It's not a rom problem because it was happening before I flashed it.
Really happy with this phone and I really don't want to go exchange. Asking this forum before I call T-Mobile because most likely they will have me do a factory reset, for them that solves everything!
Thanks.
Hercules, Hercules!!
Run fix permissions in cwm
Sent from my SGH-T989 using XDA App
quest4fire said:
Run fix permissions in cwm
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
I fixed permissions when I flashed the rom.
What difference would it make to do it again?
What do you think the problem is that this would help?
Either way I'm gonna fix permission and see how it goes.
Thanks!
Hercules, Hercules!!
I have had my phone for over a week and started having issues about 2 days later after root. My battery would not update and i was running updates from the market and the phone froze and shut down.
Rebooted and charged over night. I woke up around 4am and my phone was very hot. I got up this morning and flashed EB1.1 and so far no issues. It was odd and i cant quite find the root cause as to why it froze. no real issues before i rooted and no issues after i flashed EB.
Sent from my SGH-T989 using XDA App
Wont hurt. Try wipe cache and data too
Sent from my SGH-T989 using XDA App
Well wiped cache and dalvik, also fixed permissions.
No go, same problem.
I'm gonna wait to flash any new rom the comes out to see if it fixes anything. If not I'll just have to return.
I know with my G2X I was having random reboots and flashing certain roms would fix it so hoping for the same here.
Hercules, Hercules!!
Not sure if this will help, but when I got the phone on release it would constantly shut down and would not turn on. I had to keep holding Power button, much longer than normal. I ended up restoring the phone to factory default settings. No more random shut downs since.
Any chance did you restore any apps on titanium backup with old system data? That can cause alot of issues.
Sent from my SGH-T989 using XDA App
Havoc1127 said:
Any chance did you restore any apps on titanium backup with old system data? That can cause alot of issues.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Yeah, I know bout that one. No I didn't do that, I actually wiped my SD card as well just in case something on there was causing it and no go.
I was curious to see if root could of caused any issues, but I guess not because no one else is reporting same issue.
Hercules, Hercules!!
_eroz said:
Not sure if this will help, but when I got the phone on release it would constantly shut down and would not turn on. I had to keep holding Power button, much longer than normal. I ended up restoring the phone to factory default settings. No more random shut downs since.
Click to expand...
Click to collapse
So were you still stock or had you rooted already?
So you're talking about a factory reset right?
Hercules, Hercules!!
htc2364 said:
So were you still stock or had you rooted already?
So you're talking about a factory reset right?
Hercules, Hercules!!
Click to expand...
Click to collapse
I was still on stock. Yes a factory reset.
The phone would shut off while in apps or trying to surf the web. It would also randomly shut off while in my pant pocket and in my jacket pocket.
I get random reboots, stock and stock rooted, haven't flashed a rom yet. Reboots a few times a day usually, is kind of annoying, gonna flash a rom, see if that helps, otherwise I'll be hitting up tmobile too.
Sure don't have this problem
u can always odin back to stock now that we have it!! that fixes most probs!!!
_eroz said:
I was still on stock. Yes a factory reset.
The phone would shut off while in apps or trying to surf the web. It would also randomly shut off while in my pant pocket and in my jacket pocket.
Click to expand...
Click to collapse
Yup, that's what mine is doing. I'm gonna try a reset today and see how it goes, thanks.
At least I know now that it would of done it stock.
Hercules, Hercules!!
vinterchaos said:
I get random reboots, stock and stock rooted, haven't flashed a rom yet. Reboots a few times a day usually, is kind of annoying, gonna flash a rom, see if that helps, otherwise I'll be hitting up tmobile too.
Click to expand...
Click to collapse
I used to have reboots problem with my G2X and flashing a rom fixed it. The weird thing about it was that it was certain roms, not all of them.
Hercules, Hercules!!
movieaddict said:
u can always odin back to stock now that we have it!! that fixes most probs!!!
Click to expand...
Click to collapse
I might just have to, thanks.
Hercules, Hercules!!
htc2364 said:
I might just have to, thanks.
Hercules, Hercules!!
Click to expand...
Click to collapse
did you try that?
vinterchaos said:
did you try that?
Click to expand...
Click to collapse
No, no yet. Haven't had time. But i'm still have the shutdowns.
Hercules, Hercules!!
Okay so since I flashed the Google images from 41d to 41f after it gets past the boot animation it comes up to android is updating each time. Anyone else out there experiencing this or is it suppose to happen? Not big deal just wondering.
Sent from my Galaxy Nexus
Do you have an update file on your Storage? Perhaps it's looking for one at every bootup?
Just a guess.
I have same problem. Could you be more specific? For what exactly to look and where?
Mine did that before and after flashing. Seen it happpening in video reviews when the phone boots up too...very common?
Nope wiped the "sdcard" and fastboot the whole image from google.
Glad I'm not the only one out there having this happen.
Sent from my Galaxy Nexus
Okay I got it to stop but here is what I did and now understand what it does.
Wipe dalvik and cache
Flashed this ROM http://forum.xda-developers.com/showthread.php?t=1372376
It then rebuilt the dalvik cache and cache on first boot and havent seen it since
Maybe if one of you are will to try this method out to see if it keeps happening
Wipe dalvik and cache
Then reboot
If that works then its just dalvik cache and cache that needed to be cleared out.
Just tried your last suggestion and it didn't work. The only difference was, that after wipe cache and restart, android upgrading start optimizing the applications. This take about 3 minutes (it's deppends of how many apps you have). After second reboot it just say Android updating and start immediately after that. I'm start thinking this is not a bug, but a feature.
Mine's done it since I bought it, just figured it was a feature.
well i think its just starting all the background services before you get to the homescreen... maybe to prevent laggs in the first seconds after start?
Pyrotechnic said:
Mine's done it since I bought it, just figured it was a feature.
Click to expand...
Click to collapse
Same here, I always thought it was normal that it is just checking for updates on startup.
sabooher said:
Same here, I always thought it was normal that it is just checking for updates on startup.
Click to expand...
Click to collapse
Same here. I thought it was a little weird at first, but it doesn't really bother me. Only takes a couple of seconds.
G1ost-26 said:
well i think its just starting all the background services before you get to the homescreen... maybe to prevent laggs in the first seconds after start?
Click to expand...
Click to collapse
sabooher said:
Same here, I always thought it was normal that it is just checking for updates on startup.
Click to expand...
Click to collapse
Most probably for both reasons
Maybe we will find out more since they just release 4.0.2
At least I am not the only one. Makes me feel a little better...but with over 100 apps it takes a while to finish...grumble.
Hosehead said:
At least I am not the only one. Makes me feel a little better...but with over 100 apps it takes a while to finish...grumble.
Click to expand...
Click to collapse
Hmm, I'd have thought it was only checking/updating the Android OS, not all your apps?
Sent from my Galaxy Nexus using XDA App
It's completely normal, doesn't anyone use the search function on this forum?
Ok, you say it's normal, all i know is that when i used a stock ROM with no mods/tweaks, just CWM and SuperSU it didn't happen
Recently I have observed the strangest behavior with my phone running cm10.
Whenever I am in this particular classroom, everything works fine until i open google chrome, the phone screen will start flickering and the reception bar instantly drops to 0, battery bar drains completely empty (or so it appears), and the phone screen hangs. The only way to recover from that is by pulling the battery. However the syndrome comes back without having to open the chrome the 2nd time and on.
The only way to completely recover from that is by pulling the battery and leaving the phone off, get out of the culprit classroom, go underground, get on the train and then turn the phone back on. That's when it will start behaving normal with remaining battery level intact. Turning the phone back on before I get underground will still bring back the problem even if I have already walked half mile from the campus.
This is simply beyond my comprehension. I don't know if the problem is caused by some sort of signal interference that exist in that room(I have never experienced this in other rooms prior to this semester). Why is it only triggered by operating chrome? And finally, why is it fixed by such an unorthodox method?
That sounds too crazy to be true...
Sent from my Nexus 7 using xda premium
Maybe "factory reset" reflash The ROM. You might be able to fix it by fixing the permissions! Sorry just ideas off the top of my head!
Sent from my SPH-D710 using xda premium
Jared King said:
Maybe "factory reset" reflash The ROM. You might be able to fix it by fixing the permissions! Sorry just ideas off the top of my head!
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Dastin suggests wiping everything except sd-card. My advice, if you really like CM, do that. Back everything up on pc, do complete wipe/format, reflash. Oh, and try battery spin test?
Sent from my SPH-D710BST using xda premium
Thanks, I will try all the suggestions.
However regardless of the outcome, I am still bewildered as to why the problem only occurs in that room and would not go away unless I go into the subway.
Are you experiencing any lapses in time? Strange marks on your body? I'm thinking aliens are the culprit here.
Definitely aliens. Or the government...
Sent from my SPH-D710 using xda premium
I switched the battery and it worked fine for some time until recently when it started acting up again. This time, I was able to replicate the issue at home by simply opening a webpage in Chrome.
maxspiderx said:
I switched the battery and it worked fine for some time until recently when it started acting up again. This time, I was able to replicate the issue at home by simply opening a webpage in Chrome.
Click to expand...
Click to collapse
Sounds like you need a fresh/clean install or you could try to wipe the chrome apps data and cache. You might even uninstall chrome and reinstall or yet wipe chrome data,cache and reboot recovery and wipe cache and dalvik. Short of that I agree w/the alien idea....lol. Get yourself an aluminum foil hat..
Gil81 said:
Sounds like you need a fresh/clean install or you could try to wipe the chrome apps data and cache. You might even uninstall chrome and reinstall or yet wipe chrome data,cache and reboot recovery and wipe cache and dalvik. Short of that I agree w/the alien idea....lol. Get yourself an aluminum foil hat..
Click to expand...
Click to collapse
isn't chrome bundled with gapps for CM/AOSP releases? OP could try reflashing gapps and wiping cache and dalvik. plus investing in an aluminum foil case wouldn't hurt, to prevent alien/government interference of course
OP have you tried reproducing this with any other browser like Firefox or Dolphin?
I have had this issue with Chrome since three second beta update. Never could rectify it. Nothing really showed when I read through the logcat. I had to quit using it.
Sent from my SPH-D710 using XDA Premium HD app