Hi, I recently rooted my LG Optimus Black (P970) and flashed the Surpressed ROM. Everything is working fine, but whenever I set the time to use network-provided values the clock goes to the wrong time.
Most of the researching I've done on this has pointed towards people not wiping the cache when flashing a new rom.
I wiped the cache and dlavik cache before flashing Surpressed V7, then flashed the updates immediately after (7.1, 7.2, 7.3, 7.5). I DID NOT wipe the cache before installing the updates, assuming it wasn't necessary because I literally flashed V7.0, rebooted, flashed the 7.1 update, rebooted, etc. until 7.5 was installed. Was it necessary for me to wipe the cache between updates?
I have wiped the cache and dlavik after installing 7.5, but that didn't solve my problem. Just wondering if anyone has thoughts about what I should do next. Should I wipe the caches and install 7.5 from the SD again? or do I have to do a factory wipe and restart at flashing 7.0, then flash the updates (wiping cache in between each)?
Thanks in advance for any help!
Most probably you do not need to reflash them all. If I am not mistaken every time you reboot the cache is build from scratch (that's why it takes some time to boot the first time). What you can do is to fix permissions to check whether it helps, then you can always try to reflash the last update and before and after you flash it wipe cache and dalvik cache. If you factory reset your mobile you will still be on the same last update. What it does is only removes the data not the system.
steven8590 said:
Most probably you do not need to reflash them all. If I am not mistaken every time you reboot the cache is build from scratch (that's why it takes some time to boot the first time). What you can do is to fix permissions to check whether it helps, then you can always try to reflash the last update and before and after you flash it wipe cache and dalvik cache. If you factory reset your mobile you will still be on the same last update. What it does is only removes the data not the system.
Click to expand...
Click to collapse
Thanks for the advice and clarification. Sorry, but what exactly do you mean by "fix permissions"?
srix9 said:
Thanks for the advice and clarification. Sorry, but what exactly do you mean by "fix permissions"?
Click to expand...
Click to collapse
Nevermind - just realized that this is a function in ROM Manager. I'll give it a try and see how it goes. If it doesn't work, I'll try wiping cache and flashing the latest update of Surpressed.
srix9 said:
Nevermind - just realized that this is a function in ROM Manager. I'll give it a try and see how it goes. If it doesn't work, I'll try wiping cache and flashing the latest update of Surpressed.
Click to expand...
Click to collapse
UPDATE - I fixed the permissions, rebooted, and so far after a couple hours of running the time seems to be staying correct. Thanks again for the suggestion stevens8590
srix9 said:
UPDATE - I fixed the permissions, rebooted, and so far after a couple hours of running the time seems to be staying correct. Thanks again for the suggestion stevens8590
Click to expand...
Click to collapse
And it looks like I spoke too soon. The clock is currently 3 hours 45 minutes behind the actual time. With it being off by that amount I would assume that it isn't a timezone issue. I will try wiping the cache/dlavik, reinstalling Surpressed 7.5, wiping cache/dlavik and rebooting. Will update on that once I have it running for a while. In the meantime, any other thoughts are more than welcomed!
Related
Sorry, this might be kind of a noob question, but i see build 23 is out for CM7. If i flash the new build, do i need to totally set up my phone all over again?
My last experience with CM ROMS on my G1 was that if you are upgrading to a new CM version a wipe is recommended but not necessary. However, if you do not wipe and experience problems it will be the first troubleshooting step suggested to you
YMMV on the MT4G builds, but that's how it worked with the G1
Genocaust said:
My last experience with CM ROMS on my G1 was that if you are upgrading to a new CM version a wipe is recommended but not necessary. However, if you do not wipe and experience problems it will be the first troubleshooting step suggested to you
YMMV on the MT4G builds, but that's how it worked with the G1
Click to expand...
Click to collapse
Thanks. Ugh, i didn't even think about that when i flashed CM7. Seems like it is a real PITA to wipe every time and have to configure all the settings again.
I had good success on my move from stock -> Ice Glacier (un-crapwared stock) by making a full TitaniumBackup of -everything- and then restoring it app by app (along with settings). They are similarly built ROMs, and it worked well for me with minimal downtime. You may want to consider trying that if you are just changing between CM flavors, as I would presume they are mostly backward compatible with a few fixes/features here and there. At worst it may leave you with just system settings to redo.
When i flash a new CMNightly all i do is wipe the cache and the Dalv/Cache and i've yet to have any problems. If you are worried about wiping and restoring everything. you might want to look into Titanium Backup.
thanks. I flashed without wiping and it seems to be fine. I was worried more about my system settings than apps.
Sent from my HTC Glacier using XDA App
shortskoolbus said:
thanks. I flashed without wiping and it seems to be fine. I was worried more about my system settings than apps.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Wiping the Cache and wiping the Dalv Cache will not reset the phone. Only a full wipe will do that.
To my understanding, a "full wipe/factory reset" in Clockwork Recovery will only clear /cache, /data, and Davlik cache. /boot and /system will not be touched. Some users moving from Froyo to Gingerbread have had problems with /system, and a wipe of /system (from within Clockwork Recovery or from adb) has solved some problems for people, beyond what a full wipe can do. Discussions are in the CM7 thread in the Application Development subforum.
I know, most people refuse to search for anything.
i usually wipe the Cache and the Dalv Cache when updating nightlies, but several times i've wiped nothing and just flashed the new one on top and its always worked just fine for me
I always do a full wipe when installing roms. Setting it up each time makes me think its a whole new phone which is cool.
You do NOT need to wipe when upgrading to a new version of the same ROM. I've probably flashed 10 no-wipe updates of cm7 on my phone and it's still perfectly stable, no force closes or anything.
Boot into recovery and wipe cache and dalvik cache before flashing. Give it a few mins to "settle" on the first boot, reboot again and you're good to go.
Worst-case scenario you'll just wipe and reflash anyway, and nothing lost.
This is a flashable zip that simply returns your kernel and wireless.ko to stock GB 2.3.3 as delivered by LG in the update. This is for people who have played around with custom kernels and wish to go back to stock for whatever reason. Caveat: I have not tried the zip myself but one user has reported he has used it with success. This is a simple flash that simply replaces the boot.img and wireless.ko with the files from stock, so you should have no problems with it.
Disclaimer: I am not responsible if you brick your phone, void your warranty, or any other pain or suffering you may experience as the result of flashing this kernel.
Note: Always wipe the Dalvik Cache when flashing a new kernel. If you don't unintended consequences (i.e., boot stuck on LG logo or boot loop) may result. The first boot after flashing will take around five minutes or so. Please be patient and don't report your phone is bricked while it is still booting and rebuilding the Dalvik Cache, which takes several minutes depending on how many apps are installed.
Please report back any success or failures here.
Enjoy!
Attachments:
P999-GB-Kernel-Stock.zip (4.26 MB)
MD5: 52b1f38ff846082aed99bf8ac7fdb756
Reserved for future use by the OP.
This has been needed for a while. Thanks!
Thanks
Sent from my LG-P999 using xda premium
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
mojorisin7178 said:
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
Click to expand...
Click to collapse
This thread is for the stock kernel. Please post your question in the EB 2.1 and Trinity Kernel threads.
This is useful thanks, wish we had one for cm7.....
ONLY the D. Cache should be cleared right?
SyntekSystems said:
ONLY the D. Cache should be cleared right?
Click to expand...
Click to collapse
Yes. The Dalvik Cache is the crucial thing you need to clear when you flash any system file, kernel, etc. If you don't a bootloop or stuck boot is a likely result. If you flash a different rom then you should wipe the system also to be safe.
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
SyntekSystems said:
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
Click to expand...
Click to collapse
No reason to clear normal cache. In fact, if you use Rom Manager, that will delete the recovery it flashed as that is where it keeps it.
First of all I'm new to this forum.I've not find any specific ans to my issue so I'm creating this thread.I've installed custom ROM Oxygen,Franco Kernel to my LGp500 through clockwork MOD recovery.It was working perfectly.
Now the prob is that with my over enthusiasm of flashing and testing new things.I've flashed the same ROM thrice and kernel twice(such an idiot I'm).Now My Phone has become unresponsive or bricked(in tech jargon).When I switch on the phone Its showing LG logo but after that it freezes out there,No key is working,nothing is booting,I've tried several time but it ends up same thing.So to end up the process I was removing battery everytime. Though with power+home+vol(-) clockworkmod working fine.
PLz plz help..I've no other phone to use..
Clear your cache, davlik (in advanced) and then try again.
NanoNoodle said:
Clear your cache, davlik (in advanced) and then try again.
Click to expand...
Click to collapse
tried,Its not working.
Good people plz help.
ib0rg said:
Good people plz help.
Click to expand...
Click to collapse
Do you have a nandroid to restore from? If you don't, try wiping everything (data, cache, and dalvik) and just flash the ROM, and reboot.
It sounds like you've soft bricked your phone and i've done it many times myself. Simple fix, just clear all cache, format everything and do a fresh flash of rom.
I don't see that you have answered yet. Did you get it to boot after clearing data as well?
Sent from my LG-P500 using XDA
mrcorey said:
I don't see that you have answered yet. Did you get it to boot after clearing data as well?
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
I've cleared everything (data,cache and dalvik) through clockwork mod,Then tried to boot,Its not booting.
I've no Nandroid backup.
Today I'll do a fresh flash after clearing everything,then I'l try to reboot.Lets see what happened.
Thanks its working after fresh install.
Glad to see its working now, make sure to do a nandroid backup incase you break something again
Hey everyone. I have a rooted HTC One S. I downloader ROM Manager and downloaded CM10. i installed it, but on startup, the CM10 boot animation just keeps going and going. the longest i let it go was close to 20 mins. I'm pretty sure tht this shouldn't be happening, any thoughts or suggestions would be nice.
have you followed all those steps: http://forum.xda-developers.com/showthread.php?t=1889339&highlight=cyanogenmod
?
most important thing is to wipe your system partition / dalvik cache.
if coming from another rom (stock or whatsoever) you need to do a factory reset too.
back up your data before, cause it will be gone then.
xXFlippyXx said:
have you followed all those steps: http://forum.xda-developers.com/showthread.php?t=1889339&highlight=cyanogenmod
?
most important thing is to wipe your system partition / dalvik cache.
if coming from another rom (stock or whatsoever) you need to do a factory reset too.
back up your data before, cause it will be gone then.
Click to expand...
Click to collapse
A wipe was all that needed to be done. The problem was ROM Manager wasnt wiping prior to installation. Thanks for the help, +1.
I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
1. So I first tried to uninstall that app with Rom Toolbox. Didn't help.
2. Then I cleared data and cache from Phone services. Didn't help.
3. Then I booted to recovery and wiped cache. No help.
4. Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
5. So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.
Yep, wiping everything is clean flash, or wipe everything but internal storage (if still problems, delete . Android folder beforehand).
Sent from my Pixel using XDA-Developers Legacy app
simeoni said:
I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
So I first tried to uninstall that app with Rom Toolbox. Didn't help.
Then I cleared data and cache from Phone services. Didn't help.
Then I booted to recovery and wiped cache. No help.
Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.
Click to expand...
Click to collapse
for mw to be clean i would flash stock firmware then do the following procedure here
https://forum.xda-developers.com/tmobile-g4/development/turbo-cleaning-proceure-h811-t3417606
simeoni said:
I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
So I first tried to uninstall that app with Rom Toolbox. Didn't help.
Then I cleared data and cache from Phone services. Didn't help.
Then I booted to recovery and wiped cache. No help.
Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.
Click to expand...
Click to collapse
A factory reset isn't a clean flash. A clean flash is wipe system, data, dalvik/art cache. You have flashed the camera app to your system partition, so you have to wipe /system in twrp too (together with /data and /cache if you want to make a clean flash). But in your case it should be enough to wipe system and then reflash your Rom to get rid of your issue
rob rich said:
A factory reset isn't a clean flash. A clean flash is wipe system, data, dalvik/art cache. You have flashed the camera app to your system partition, so you have to wipe /system in twrp too (together with /data and /cache if you want to make a clean flash). But in your case it should be enough to wipe system and then reflash your Rom to get rid of your issue
Click to expand...
Click to collapse
OK, thanks. Maybe in my step 4 above I thought that factory reset was enough but I didn't notice that it does not wipe system. So I went too far and wiped all my data, too.
But earlier when I have flashed different roms and they always tell that you must do clean flash, I didn't wipe system. So I thought clean flash was just factory reset. Still those different roms were working ok. Next time I try to remember wipe system also.