I have a stock phone. On the latest update. For some reason when I complete a wipe cache in recovery mode and select reboot phone says error right before it starts up. Would I need to factory reset? Was hoping I could wipe cache so I could see if it would fix some problems Ive been experiencing.
What's the error you see come up?
Just says error right before it reboots on the android logo in the background.
For some reason my phone keeps randomly rebooting. I'm gonna hit up tmobile on my day off.
krntehknik303 said:
For some reason my phone keeps randomly rebooting. I'm gonna hit up tmobile on my day off.
Click to expand...
Click to collapse
Does it say error after wiping cache? If not, then the cache wipe is probably successful. I'm not sure what the error would be if it throws it up when you say to reboot. But I doubt it has anything to do with wiping cache.
gspears said:
Does it say error after wiping cache? If not, then the cache wipe is probably successful. I'm not sure what the error would be if it throws it up when you say to reboot. But I doubt it has anything to do with wiping cache.
Click to expand...
Click to collapse
But how do I know that it did wipe the cache? Don't really notice much of a difference.
krntehknik303 said:
But how do I know that it did wipe the cache? Don't really notice much of a difference.
Click to expand...
Click to collapse
You won't notice much of a difference. It's normally only noticeable when it fixes some questionable behavior. If you clear cache and the questionable behavior is still there, it normally means there is another problem.
Related
[Q] "Clean Cache" & "Full Wipe" with xRecovery prior to flashing new rom?
Is it true that the best way to keep your phone in optimal state, is to clean the cache and do a full wipe with xRecovery every time before you flash your X10 with any (new) rom?
A friend told me that if you don't clean cache and do a full wipe before you flash to a new rom, the cache content of the rom you're on cannot be removed after flashing to a new rom because the new rom has no re-collection of the contents of the cache from the previous rom you were on.
That's bs... Xrecovery cleans the cache and wipes for you, watch what it says while you're flashing and you will see.
I always recommend doing it anyway just in case, full wipe, then wiping cache partition and finally dalvik cache.
I don`t know and really don`t care
I simply just wipe/clean EVERYTHING i can before any installation.
Result?
Never had most problems users have. Ever. So i will continue
rendeiro2005 said:
I don`t know and really don`t care
I simply just wipe/clean EVERYTHING i can before any installation.
Result?
Never had most problems users have. Ever. So i will continue
Click to expand...
Click to collapse
LOL LOL
fiscidtox said:
That's bs... Xrecovery cleans the cache and wipes for you, watch what it says while you're flashing and you will see.
I always recommend doing it anyway just in case, full wipe, then wiping cache partition and finally dalvik cache.
Click to expand...
Click to collapse
But if it is bs and xRecovery does it for you. Then why do you recommend doing it anyway? You got me slightly confused here.
Kimodroid said:
But if it is bs and xRecovery does it for you. Then why do you recommend doing it anyway? You got me slightly confused here.
Click to expand...
Click to collapse
All I'm saying is if you forget it's not a huge deal, and what he is saying isn't true...
I do it anyway just because when I had a htc hero devs used to recommend you did, so force of habit, yet I know for a fact that what he said isn't true. It could perhaps miss some data which is why you should still wipe, but that data would definitely not be stuck in limbo forever..
fiscidtox said:
All I'm saying is if you forget it's not a huge deal, and what he is saying isn't true...
I do it anyway just because when I had a htc hero devs used to recommend you did, so force of habit, yet I know for a fact that what he said isn't true. It could perhaps miss some data which is why you should still wipe, but that data would definitely not be stuck in limbo forever..
Click to expand...
Click to collapse
Thanks for clearifying that.
No problem
if not switching roms, does it make a difference to your system performance to occasionally wipe the dalvik cache and cache partition?
tdiddy1987 said:
if not switching roms, does it make a difference to your system performance to occasionally wipe the dalvik cache and cache partition?
Click to expand...
Click to collapse
I did it on beta 4 and it actually made my performance wayyy worse.. so much so that I had to go back to an earlier backup I had made. MY linpack dropped from 35 to about 6 and the battery started getting super hot, and was dropping insanely fast.
I wouldnt recommend it during usage of a rom. What you can do is get a cache cleaning app and use that regularly! I use cache cleaner ng
rendeiro2005 said:
I don`t know and really don`t care
I simply just wipe/clean EVERYTHING i can before any installation.
Result?
Never had most problems users have. Ever. So i will continue
Click to expand...
Click to collapse
+1 and here are a few more characters
I think this will help you get a "clean" install and saves you from other problems later?
Or is there Cons to always doing this?
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Hmm, I'd say this is Not normal. One of the big "selling points" of the gs3 and ICS is the quick boot time. For me it is very quick. Maybe u should try doing a factory reset and see if it stops this behavior??
Sent str8 from my half eaten Banilla Ice Cream Samich
ratledge said:
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Click to expand...
Click to collapse
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
That is not normal if it is happening on every boot, only if you wipe your dalvik cache then yes it will update.
id_twin said:
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
Click to expand...
Click to collapse
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Are you using a custom rom or rooted? Or are you completely stock?
Sent from my SCH-I535 using Tapatalk 2
ratledge said:
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Click to expand...
Click to collapse
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
krackerjac said:
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
Click to expand...
Click to collapse
Sure sounds like it. I'm using the "Route66" rooted ROM with the Invisiblek overclocking kernel in place of the recovery.
Most likely the overclock. i ran the stock rooted 66 with no issue. I also have titanium backup installed without that issue.
id_twin said:
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
Click to expand...
Click to collapse
Worth a shot. I'll give it a rip and report back... Thanks!
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
ratledge said:
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
Click to expand...
Click to collapse
Oh, well - factory reset, re-route66, invisiblek's v2 overclocked kernel. I'm good, no "Android is updating..." every time, and no mo unlocked icon on the main screen.
I dunno what I did, but the Sammy din't like it!
Thanks, guys!
Hi!
When i say sounds, i mean lock, touch, keyboard's sounds.
This have not happened to me since long time, but today, all of a sudden, phone stopped producing these sounds.
Anyone knows why?
and yes, Settings/sounds/I ticked ALL of the options.
fenchai said:
Hi!
When i say sounds, i mean lock, touch, keyboard's sounds.
This have not happened to me since long time, but today, all of a sudden, phone stopped producing these sounds.
Anyone knows why?
and yes, Settings/sounds/I ticked ALL of the options.
Click to expand...
Click to collapse
I don't know why but boot to recovery, wipe cache partition, wipe dalvik cache and see if it helps.
Jokesy said:
I don't know why but boot to recovery, wipe cache partition, wipe dalvik cache and see if it helps.
Click to expand...
Click to collapse
mmmm does cleaning cache and dalvic cache, deleates anything important to my device?
OH! I remembered!!!! I did accidentally Free unused data from recovery and i dont know what happened!!!
I've had my NT for quite a while now. Once I got it, I'm pretty sure I used the nook & zergy tool to root, and that's been it.
I've been on 1.4 forever, with CWM 5.5.04 as my recovery (on the emmc maybe? I don't need an sd to boot into it).
I've noticed that my stability has been declining, with random reboots here and there and rapid battery drain, so I decided it was time to get back to some flashing. I started with this http://forum.xda-developers.com/showthread.php?t=1494367, using the first 1.42 version as the others are dead. Everything loaded and booted fine, but it reboots with little provocation...you know, like, touching it, and may or may not go into a reboot cycle 3-4 times before chilling out. I still can't do much without triggering a reboot though. Search in the market? Reboot.
I attempted to restore using this http://forum.xda-developers.com/showthread.php?t=1402190, but it just boots right up normally. If I manually flash it it fails.
So, here I am with a non-bricked NT that doesn't do me much good, and I'm wondering how to get it back in order.
Are you wiping cache and dalvik cache from recovery?
Also, are the reboots occurring on battery power, or on charging as well?
Sent from my ST27i
I've done a data wipe and wiped the dalvik from cwm. I've not wiped the cache partition if that's what you're asking. Reboots are when it's unplugged or plugged.
n8w said:
I've done a data wipe and wiped the dalvik from cwm. I've not wiped the cache partition if that's what you're asking. Reboots are when it's unplugged or plugged.
Click to expand...
Click to collapse
Ok. Data wipe does wipe cache as well.
You could try a cm Rom to see if the problem persists, but if you are looking for warranty, better to stay on stock.
Also, if you pull last kernel message ( from /proc/kmsg) , some dev may be able to determine cause for reboot.
I think it's possible this is a hardware issue.
Sent from my ST27i
Thanks for jumping on this. I went ahead and wiped the cache partition, because "why not?" and I'll be damned, but I haven't had a reboot yet. Hitting search in the market was a sure trigger, and it's behaving well so far.
satan89 said:
Ok. Data wipe does wipe cache as well.
...
Click to expand...
Click to collapse
/Cache and /Data are two separate partitions on emmc, and unless something change in recent CWM/TWRP Recovery, there are separate menu options to wipe each of them.
/Data is typically used to hold user downloaded/installed apps, and should not need to be wiped except when upgrading to a different ROM or a different ROM version.
I really don't know much about how all that works, but for whatever reason, wiping the cache fixed my issue.
Sent from my DROID RAZR using Tapatalk 2
Hey all,
I got a problem with my s3... My phone is making random unlocking and locking sound (one after an other) while it's not using... Any solutions to fix this?
Try wiping cache and dalvic, if you are rooted, otherwise factory reset.
boomboomer said:
Try wiping cache and dalvic, if you are rooted, otherwise factory reset.
Click to expand...
Click to collapse
I don't really want to wipe out all my data from phone. Any other possibilities?