I noticed something interesting.
As others have mentioned, Clockwork seems to misbehave when it says its clearing cache. It appears to work, but in fact does not seem to be clearing it.
I was having the chipmonk audio, and other strangeness so I decided I would go back to the stock kernel. I did the double wipe as suggested, and surprisingly the audio issue is gone.
So, just curious, how many folks have the problem after doing a double wipe with clockwork, or a single wipe with Amon RA?
Personally I don't trust ClockworkMod. AmonRa works flawlessly and has a easier interface. Too many bugs reported about Clockwork.
Sent from my PC36100 using XDA App
Related
I have adrynalyne's Super Clean DL30 v.7 on my fascinate right now. He just upgraded to v.8 and I would like to install some of the features that were upgraded. Can I just flash this ROM over the previous version? I know you should usually clear data/factory reset in between flashing ROMs, but I just got everything perfect on this one and didn't want to have to do that. Does anyone know if it would potentially mess anything up or not run as well to do it this way?
Yes, flash this one over version 7. You do not need to wipe.
You can have some force close issues if data isn't wiped. I would suggest to start clean. But that's only my suggestion. If you wipe data always wipe twice as to insure everything is gone
Sent from my SCH-I500
SlightlyLifted said:
You can have some force close issues if data isn't wiped. I would suggest to start clean. But that's only my suggestion. If you wipe data always wipe twice as to insure everything is gone
Sent from my SCH-I500
Click to expand...
Click to collapse
Not saying you are wrong, but multiple people (including myself) just flashed without wiping and haven't had any issues.
Typically it is a good idea to wipe data/cache between flashes, but I don't think it is necessarily a requirement this time
I flashed 0.8 over 0.7 w/o clearing. Everything works just fine.
Sent from my SCH-I500 using XDA App
Alright. Thanks for the advice. I backed up my Tom through CWM first for good measure and I'm about to flash the updated dl30. Ill post here if something goes wrong haha.
Worked perfect. No problems (so far), in fact it seems to run better now, but that's probably just because the newer version haha.
But as far as I can tell SO FAR, there are no problems.
I did not wipe and it works great
Sent from my SCH-I500 using XDA App
I know I'm bad, but I never wipe... Hang on that came out wrong lol, only time I do data wipes are when I haver problems, just clear cache and run...
Sent from my SCH-I500 using XDA App
I used to forgo wiping until I finally realized that the source of my wonky softkey issues was (apparently) due to many many unwiped flashes. Now I wipe every time. Granted that was with DJ05/DL09 ROMS/kernels, but still... lesson learned.
Okay, I'm here everyday reading this stuff, Id first like to say you guys rock. Everyone here, and the makers of these awesome mods, you have made my phone and my life quit amazing, and less boring like stock!
It seems something is wrong
I sort of switch back and forth between cm and savage zen when each have an update. I love savage zen because of the higher resolution, makes my evo screen crystal clear, while cm is much more stable, and has not only the meat, but the potatoes and gravy, while savage only has the meat
But anyway, no matter what I do, gmail crashes, and media crashes, market doesn't work etc. The google apps in rom manager have worked before, when I was using 2.3.4 I was able to find that google app package somewhere online.
The google apps in rom manager that im thinking of says its compatible with 2.3.3, and well I used it for a few weeks perfectly. Silly me though I'm never satisfied...
I'm running 7.0.3.1, but it seems the google apps that comes with that package has never worked, you know when you check the box for google apps.
So instead I would do it manually, and again I mean it worked fine.
I decided to go back to savage zen, loved it (everytime deleting delvik cache and full wipe)
I think I am missing something...
The order I would do things is, wipe dalvik cache/data, install mod/google apps. I mean that has always worked before just fine. I tried a before and after also, booted it before restoring my data, nothing crashed, it all went smoothly.
In recovery, I go to restore, advanced restore, then restore data. My 2 latest backups both fail. Am I not restoring correctly, oh im sure this is all my fault.
Sorry im sure this has been answered many times over...I found a few threads but they wernt quite what I was looking for because the person I was reading about both times was using cm6, and I think I did the steps correctly..but thats what I'm here for, Please help me fix my bad *** phone.
Quick Update
Okay, so yeah I do still have more to learn. I was thinking well maybe if I just wipe the cache partition....(havnt done that before..just did full wipes)
Is this all my fault? Maybe all this going back and forth is just not good? lol
I figured this out by myself. I went into titanium backup, and wiped the cache of every program that was giving me the error. Done and done. I guess clockwork mod doesn't get rid of all cache?
Well..thanks anyway...I didn't find the fix on google, or anywhere for that matter..It just came to me..
I remember reading comments about how clockwork dosent nandroid wimax keys and does not fully wipe like it should, you should try switching to amon's RA recovery.
I switched to Amon Ra a few months ago. I agree it's way better and it's nice to be able to whipe dalvik cache without waiting a few minutes for it to even get to the right screen, but I have still had a few problems even after dalvik/cache wipe. Titanium backup is a nice way of cleaning things up also, media storage!
That's something I figured out, it was media that kept crashing and it's happened again, but I do flash like a junkie! Always making sure to wipe dalvik/cache and making a nandroid backup before flashing.
Going into settings, applications, media storage then clear data. Works like a charm.
Also once I had 2 ringtones playing when my phone rang...couldn't figure it out and did EVERYTHING. Clearing media storage saved the day.
I think I'm done flashing..may of found my perfect combo
Synergy rls1 + godmode with aggressive freedom kernal.
mmmmm delicious! RLS1 made the phone actually seem to be overclocked before overclocking it (If that makes sense LOL), it ran just as smooth as it did running cyanogen overclocked to 1190. Of course I overclocked it anyway
I recovered back to froyo from cm7 7.0.3 thinking I would give the gingerbread update a try. After seeing what bugs they had on gingerbread I went back fresh to cm7. I have cm7 7.0.3 on it no problem but when I try to put the newest nightly on it it does'nt do anything. It will download the nightly but when I tap it to install it say it will boot into recovery but dose'nt. I've tried it with 86,87 nightlys and it has done the same thing. Any help would be nice. Thanks.
Im guessing you are using ROM manager. If you are, dont. Just download the nightly zip from the thread on here for cm7, place on your sd card, reboot into recovery, nandroid, wipe cache and dalvik, and flash.
sitlet said:
Im guessing you are using ROM manager. If you are, dont. Just download the nightly zip from the thread on here for cm7, place on your sd card, reboot into recovery, nandroid, wipe cache and dalvik, and flash.
Click to expand...
Click to collapse
This. ROM manager, while convenient, is kind of a plague to us. This is because people learn to do all of their recovery based work through it and never learn how to work with the recovery (obvious by the fact that you haven't just booted into recovery and done it yourself, OP).
So do as this smart poster says.
Sent from my PC36100 using XDA App
SoraX64 said:
This. ROM manager, while convenient, is kind of a plague to us. This is because people learn to do all of their recovery based work through it and never learn how to work with the recovery (obvious by the fact that you haven't just booted into recovery and done it yourself, OP).
So do as this smart poster says.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I have done that in the past. It's just much easier to do it through rom manager. Used it several times before with no problems.
dvrdwn said:
I have done that in the past. It's just much easier to do it through rom manager. Used it several times before with no problems.
Click to expand...
Click to collapse
Have you tried clearing the data and cache with ROM manager and trying again?
dvrdwn said:
I have done that in the past. It's just much easier to do it through rom manager. Used it several times before with no problems.
Click to expand...
Click to collapse
Well now you ARE having a problem. And it's really not that much easier. Again, download zip, reboot to recovery, nandroid, clear cache and dalvik, and flash. Literally takes maybe 10 seconds more than Rom manager.
I was running cm7 since it was first released. I got a new phone so i decided to give my atrix to my younger brother. The problem is after i went through the process of putting the phone back to stock, there now seems to be dead zones on the phone. For example i cannot press the w,e,s, keys. Can anyone help me or tell me if i've done something wrong?
I'm not sure you did anything wrong specifically. Did you make sure the clear all the cache? How did you put stock back on it (IE. flashed stock via CWM, moto fastboot, etc)?.
Boot into recovery, wipe dalvik cache, system cache, reflash your firmware of choice, reboot.
Sent from my MB860 using Tapatalk
Ive had numerous problems with cm7 for atrix but ive found that backup everything you need with titanium backup and then just reflash the rom and wipe the data and davlik cache and it should. But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Sam
samdrake112 said:
But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Click to expand...
Click to collapse
The CM7 beta does not have the issues that the OP described so please don't let him think that's the reason.
OP, re-flash your phone with a different ROM or with CM7 again and see if it still persists.
I could be wrong, but it seems that older versions of TWRP had the "wipe internal memory" option but it's not listed in TWRP 2.5's wipe advanced options. I have heard that wiping "data" essentially wipes internal storage, but I am certain that even after wiping, rebooting into recovery and wiping again, stiff is still on the sdcard0. Amazon mp3's for instance. Not a big deal, but if it's not wiping the amazon mp3's what else may it be missing on the wipe?
My specific issue is that I have heard that the bluetooth issue is fixed on many of the 4.2.2 roms now (aokp apparently included in this, although according to the guy bringing us aokp it always had "no issues that he knows of" since it's release), however after flashing the latest aokp, I am still experiencing random lockups and reboots while attempting to use bluetooth. In fact, 2 versions ago, the bluetooth seemingly locked up far less than it is with the latest aokp I've flashed. So I want to make sure everything is wiped (if that's necessary), before doing a fresh install of aokp in hopes of experiencing the bluetooth without issue.
I know you're not a big fan of me, but I also missed this with the upgrade of TWRP. I've been using the "format data" option every time I flash a new ROM. I wipe caches, wipe system, format data, and reboot recovery and let it install SU prior to reboot. If you do this, make sure you move all the data you want to keep to external, pics, backups, etc.
Off topic, I promise you I'll clean up my act.
Sent from my Droid Razr M using xda app-developers app
RikRong said:
I know you're not a big fan of me, but I also missed this with the upgrade of TWRP. I've been using the "format data" option every time I flash a new ROM. I wipe caches, wipe system, format data, and reboot recovery and let it install SU prior to reboot. If you do this, make sure you move all the data you want to keep to external, pics, backups, etc.
Off topic, I promise you I'll clean up my act.
Sent from my Droid Razr M using xda app-developers app
Click to expand...
Click to collapse
Thank you sir, I will give this a shot and let you know how it goes. Hopefully this will do the trick. You are a changed man, RikRong!
Sent from my Droid Razr M using xda app-developers app