Hi together
I hope someone knows a solution.
I have GingerVillain 2.0 on my HTC Desire since weeks.
It works all perfectly. Only the notification bar freezes after a certain time. In this situation. It all still works, except that it refresht anymore.
Then I restart phone and it's fixed for the next hours.
Thank you for helping
Marcel
Try reflashing the rom without a wipe?
Sent from CM7
Reflashing
Meaple said:
Try reflashing the rom without a wipe?
Sent from CM7
Click to expand...
Click to collapse
I did flash first time GV 2.0 with wipe then recovery data with Titanium backup.
Then I had the issue.
After them I tried reflash without wipe. Today I have the same issue :-(
Do you have another idea?
Just seems a problem with the rom. You can do a proper wipe, factory reset, cache wipe and dalvik cache wipe, flash the rom but don't restore your data with titanium backup. If it's still doing it, try another rom if it's really bothering you. But like I said, seems like a problem with the rom which you can't do anything about.
Related
It keeps happening on my evo and im using the newest fresh rom and the current radio http://tweetphoto.com/33676911
jxb25 said:
It keeps happening on my evo and im using the newest fresh rom and the current radio http://tweetphoto.com/33676911
Click to expand...
Click to collapse
that's called a Force Close (FC). It usually happens with an unstable ROM/unstable app but more often it happens when you don't wipe (Cache/Dalvik) before installing a custom ROM.
Backup any important data that's not already on your sdcard, go back into recovery, wiple your cache and dalvik, and flash the ROM again. see if that helps you
initial said:
that's called a Force Close (FC). It usually happens with an unstable ROM/unstable app but more often it happens when you don't wipe (Cache/Dalvik) before installing a custom ROM.
Backup any important data that's not already on your sdcard, go back into recovery, wiple your cache and dalvik, and flash the ROM again. see if that helps you
Click to expand...
Click to collapse
even if im coming from the old fresh to the new fresh i still have to wipe
I'm not familiar with Fresh's ROMs, if you read his threads carefully I'm sure he'll tell you which version upgrades require a wipe and which don't. Usually a drastic upgrade will require a wipe. In your case a wipe will most likely fix these FCs
With the learning curve for the EVO still growing, its usually a good idea to wipe data/cache/dalvik when flashing new roms. Even updates. I haven't seen too many "No Wipe Necessary" around this forum. As long as you've got Titanium or MyBackup, wiping isnt as big of a headache as it used to be. Hope you get things figured out. Screwing with these phones can get frustrating. Dont know how many times I wished I hadnt messed with anything.
well i just wiped and reloaded fresh so hopefully this will fix everything
I have upgraded from my rooted 2.1 to the rooted official HTC 2.2. However to avoid having to reinstall things and setup my phone I did not wipe the data & cache before flashing the ROM.
Is this a particularly bad idea for some reason? Everything seems to work OK... so far!
elziko said:
I have upgraded from my rooted 2.1 to the rooted official HTC 2.2. However to avoid having to reinstall things and setup my phone I did not wipe the data & cache before flashing the ROM.
Is this a particularly bad idea for some reason? Everything seems to work OK... so far!
Click to expand...
Click to collapse
hm, did you do nandroid backup + titanium backup all data etc?
kmetek said:
hm, did you do nandroid backup + titanium backup all data etc?
Click to expand...
Click to collapse
yes I have a full nandroid backup of my original ROM should anything go wrong. I didn't do a titanium backup though because I thought that not wiping the data & cache would be easier.
If it doesn't work out then I can revert to my nandroid backup and start again, this time WITH a titanium backup.
I'm wondering what sort of problems I should expect?
elziko said:
I'm wondering what sort of problems I should expect?
Click to expand...
Click to collapse
The problem issue of not wiping data is kinda random... Sometimes when you flash a different ROM despite not wiping data it would work and sometimes it wouldnt.
When upgrade your ROM and flash the same ROM but with different version, you can do it without wiping. The impact should be minimum.
When you flash a different ROM that the currently using, there is a chance that not wiping might result in a boot-loop or the ROM not working as it should be.
The main guideline should be to flash any ROM and do a full wipe if you get a boot-loop or find any issue with the ROM. Doing a full wipe when flashing different ROMs is also recomended.
OK, thanks. Since I have all the backups to go back if needs be I think I'll carry on and see if I have any issues.
elziko said:
I have upgraded from my rooted 2.1 to the rooted official HTC 2.2. However to avoid having to reinstall things and setup my phone I did not wipe the data & cache before flashing the ROM.
Is this a particularly bad idea for some reason? Everything seems to work OK... so far!
Click to expand...
Click to collapse
Personally, I think it's a risky.
However, wait until you get problems, then do a full wipe, including Davlik cache and do NOT restore apps from a backup after.
Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn
please help me
I try about 3 roms and when I try to install new app the device reboot..
what should I do ??? please help me X_x
Which roms did you use?
Model: Wildfire S A510e
Recovery: unofficial CWM
Rom: JxMatteo_ROM_V1. 1 with Link2sd - OC - Rooted
apparently freezes and reboots can be a problem if you forget to clear everything before installing custom roms....so you need to do factory reset, clear all cache, clear dalvik cache or whatever it's called, then install rom.
this didn't actually work for me when i tried to put CM7 on my phone, i've ended up clearing it all, formatting evrything and just going back to stock because CM7 was so unstable on my phone.
but if you forgot to clear everything when you first installed, try that first?
Hope you get it going. If not, you can also install stock, but you can still partition the sd card and use link2sd to give you basically a gig of "internal" storage (it lets you install pretty much all apps to the 2nd partition on the sd card. running very well now on mine.
I was just about to create a thread about this problem. I flashed m1ndh4x8r's ROM onto my device after a bad experience with the CM7 nightly, fully wiped, permissions fixed. I was on that exact same ROM the day before flashing CM7 and it was working perfectly, did everything it said it would, apps installed just fine. And the first time I installed that ROM, I didn't wipe a single thing.
So, now I'm thinking we should revert to the stock ROM, then flash this one back over it with no wipes, then if that doesn't work, revert to stock again and try flashing the ROM the proper way, wipes and all.
I'll try fixing this every way I can. I'll tell you if I find a fix for myself that you could use as well
matt5eo said:
Which roms did you use?
Model: Wildfire S A510e
Recovery: unofficial CWM
Rom: JxMatteo_ROM_V1. 1 with Link2sd - OC - Rooted
Click to expand...
Click to collapse
1- JkantaruROM XE
2- alquez cyanogenmod 7
3- m1ndh4x8r
Gloris said:
apparently freezes and reboots can be a problem if you forget to clear everything before installing custom roms....so you need to do factory reset, clear all cache, clear dalvik cache or whatever it's called, then install rom.
this didn't actually work for me when i tried to put CM7 on my phone, i've ended up clearing it all, formatting evrything and just going back to stock because CM7 was so unstable on my phone.
but if you forgot to clear everything when you first installed, try that first?
Hope you get it going. If not, you can also install stock, but you can still partition the sd card and use link2sd to give you basically a gig of "internal" storage (it lets you install pretty much all apps to the 2nd partition on the sd card. running very well now on mine.
Click to expand...
Click to collapse
how can I go back to stock ?? and what is CM7 meaning???
johnnyspritz said:
I was just about to create a thread about this problem. I flashed m1ndh4x8r's ROM onto my device after a bad experience with the CM7 nightly, fully wiped, permissions fixed. I was on that exact same ROM the day before flashing CM7 and it was working perfectly, did everything it said it would, apps installed just fine. And the first time I installed that ROM, I didn't wipe a single thing.
So, now I'm thinking we should revert to the stock ROM, then flash this one back over it with no wipes, then if that doesn't work, revert to stock again and try flashing the ROM the proper way, wipes and all.
I'll try fixing this every way I can. I'll tell you if I find a fix for myself that you could use as well
Click to expand...
Click to collapse
Ok thank you , I'm waiting you
but can you tell me what is the CM7 ???
*_^AL_Ha$aN^_* said:
Ok thank you , I'm waiting you
but can you tell me what is the CM7 ???
Click to expand...
Click to collapse
is a type of rom... currently cm7.2 stable build... CM stands for cyanogenmod
check this site: cyanogenmod.com
Pretty much every ROM ever made says be sure to wipe EVERYTHING. They put that there for a reason. The only time time you MIGHT get away with not wiping is if your flashing the exact same ROM you just had. Then and only then, you might get away without wiping your dalvik.
Sent from my HTC_A510c using Tapatalk
Idk, the ROM worked fine for me, even though I think I didn't wipe anything. When I did wipe the phone before flashing, there was a problem. Though it could just be my device and my bad luck
God hates me, I don't know why I even bother living anymore -.-
EDIT: My faith in God is restored. Just flash this ROM instead. You'll be happy with it and it works just fine for me. Also, wipe EVERYTHING I can't agree that you always have to wipe everything, since not wiping actually solved a problem I had with CM7, but I think that was just an isolated case.
Hi all,
When I answer calls the microphone does not seem to activate and the caller can't hear me at all. The only work around is to switch to speaker and the microphone starts to work. Have to keep headphones with me all the time
I'm on CM 7.1.0 jordan stable, should I reflash this ROM again?
Thanks.
Could be a hardware problem, but yes, just reinstall the same build to see if it is not a software problem.
Try to only wiping dalvik cache before or after flashing the zip (without wiping cache or data) first and you will not lose any of your current settings or apps.
Good luck.
Thanks AL, but wiping dalvik cache did nothing, so I made a backup with recovery and did a clean install and the microphone is working
I must have messed up something in the settings... any ways if I restore the backup is there a way to restore CM7 default settings and test? can't seem to find them :/
Warfighter said:
Thanks AL, but wiping dalvik cache did nothing, so I made a backup with recovery and did a clean install and the microphone is working
I must have messed up something in the settings... any ways if I restore the backup is there a way to restore CM7 default settings and test? can't seem to find them :/
Click to expand...
Click to collapse
Well good that you now know that it's not hardare related.
The dalvik cache wipe was not a target solution on its own but just a step in what I would have done in order to keep yours apps, sms -and as much as you could- intact. So again; I would have just reinstalled the nightly AND wipe dalvik cache only (because it is always good to do so after a system installation).
But now, I would try to do this: wipe everything in cwm recovery (cache+data+dalvik), restore your nand and boot up.
If the problem is still there, then go back in cwm again and do what I just wrote above: dalvik cache wipe only and flash the nightly.
If it doesn't work, then backup your apps+data with TB, Astro or others and go clean install again...
Ok been re-flashing/restoring/testing... hence this late reply, the good news is that the microphone works now and I'm on the latest cm7.1 nightly.
The bad part is that the earpiece is dead?(on the current and clean install, maybe this was not working all along, with the mic) I know others have had issues with this? BUT seem to work only on skype calls, this would mean the earpiece is ok right, this is driving me nuts. any suggestions?
Or other recommended alternative ROM I can try or tests/debug form computer? really love CM tho.