I have posted this before and thought i had fixed it but it is back and my other method isnt working this time.
I flashed CM7 ages ago but since january this year my 3g has been acting up and now i have no 3g or wifi at all and the status bar icons for them have turned white but are still there. I haven't tried reflashing cm7 but i will try tomorrow is there any alternatives to reflashing?
P.s. - my 3g and wifi work on stock Froyo
Before reflashing, did you do all wipes (dalvik, cache...)?
HTC Bravo said:
Before reflashing, did you do all wipes (dalvik, cache...)?
Click to expand...
Click to collapse
He is right, try wiping dalvik cache... If that doesn`t help the only other option is flashing the rom again.
Ive wiped cache and dalvik cache but that was the other method which worked before. I dont think it is actually wiping my cache because my cache and dalvik cache are on sd... so ill move them back then wipe them again and ill repost what happens.
Thanks
EDIT: I just remembered that my cache is cleaned daily by an app so ill just wipe dalvik.
Seems to have fixed it for the moment, but it might re occur like before. Thanks anyway.
Related
flashed SRF 1.1.0 a couple days ago (first time rooting and all -- yeehaw!), so this is a n00b question
i know that for that, i had to data data, cache, and dalvik cache
i've also flashed the Vision kernel, which ... seemed like it didn't require wiping data or cache or dalvik cache
i've also flashed an impaled keyboard tweak and that one seemed to require wiping just cache and dalvik cache, but not data (as i recall)
so... i'm just confused, and wondering... when do i know if i need to wipe data, or just cache/dalvik, or none at all?
i just flashed the AOSP screen lock zip .. didn't see any instructions, so i figure wipe cache and dalvik, but not data (didn't want to lose my texts was my thinking)... and i just made that up. and that seemed to work. but i figure if i knew the rules of thumb, i'd feel better like i knew what i was doing
any clues / insights would be super appreciated!!
The only time u wipe:
1.
Data/Cache/Dalvik
For a rom flash that says on the rom thread wipe wipe wipe
2.
Cache/Dalvik
Is mainly when u flash themes its reccomended
3.
As for kernals and other mods unless it says to wipe then you dont need to...
Nice info so far.
After you have done this a while you can start drawing from your brain through osmosis and you will understand: if it doesn't work the way you want....EXPERIMENT.
Sent from Bonsai 7.0.3
the above post is correct, sorta.
anytime u flash something that mods /system its good practice to wipe cache and dalvik cache.
flashing a kernel, u will want to wipe cache/dalvik cache just to be safe. it prevents any sort of incompatibility between kernels.
my 2 cents
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.
Ive since seen both sides of the fence on this one.. but are people still wiping caches ( dalvik etc ) when installing new kernels? Or is that one of those old practices?
Still doing a wipe of cache and dalvik cache when updating kernel. Its the best practice.
I would strongly suggest wiping cache and dalvik before flashing your new kernel, or anything else for that matter. I've been wiping, flashing, wiping again before rebooting, letting the phone sit idle for 10 minutes after first reboot,and then reboot again. Use as you would normally from there. Just how i do it. So far so good.
Papa Smurf151 said:
Still doing a wipe of cache and dalvik cache when updating kernel. Its the best practice.
Click to expand...
Click to collapse
I agree...I have always wipes the caches when I flashed a new kernel and never had a problem...better safe than sorry
Sent from my PC36100 using XDA App
Just did a clean install of Anthem v2.1 and everything booted up fine. I went into recovery, wiped data, dalvik, and cache, and installed the latest gingertiny kernel. When I reboot from recovery, I get bootloop. What's wrong?
prinzmetal6 said:
Just did a clean install of Anthem v2.1 and everything booted up fine. I went into recovery, wiped data, dalvik, and cache, and installed the latest gingertiny kernel. When I reboot from recovery, I get bootloop. What's wrong?
Click to expand...
Click to collapse
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.
cmlusco said:
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.
Click to expand...
Click to collapse
Thank you!
cmlusco said:
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.
Click to expand...
Click to collapse
Just to add to this. NEVER wipe data after flashing a Sense 3 or Sense 3.5 ROM. Actually even some Sense 2.1 ROMs that is a bad idea.
This is because the way these ROMS are built as the storage in /system cannot hold the whole ROM so they have to build part of it in /data. So wiping data will clear the ROM components as well as the user data. If you have to wipe data, plan to reflash the ROM again. So I say don't wipe data AFTER flashing the ROM unless you plan on reflashing the ROM. You can and will probably need to wipe data before flashing the ROM though.
Is there a reason why Titanium Backup isn't working? When I try to restore the progress bar just doesn't do anything...I had this problem with my Galaxy Tab and I had to change the app processing mode but is there a different issue?
prinzmetal6 said:
Is there a reason why Titanium Backup isn't working? When I try to restore the progress bar just doesn't do anything...I had this problem with my Galaxy Tab and I had to change the app processing mode but is there a different issue?
Click to expand...
Click to collapse
Make sure USB debuggging is on. If it is, I don't know.
I think the problem is that I ran out of internal memory, I have a huge sd card so I think I can solve this problem. Thank you for replying though. I would've posted something on the actual rom page but I don't have enough thumbs up
I'm using CM7.2 with Link2SD. Everything was working fine for a long time, until just now... I wiped Dalvik cache, and the phone got into bootloop after restart... How is this even possible? Then wiped cache partition, still nothing. I don't want to factory reset... Is there a simple way to bring it to life?
SignumPL said:
I'm using CM7.2 with Link2SD. Everything was working fine for a long time, until just now... I wiped Dalvik cache, and the phone got into bootloop after restart... How is this even possible? Then wiped cache partition, still nothing. I don't want to factory reset... Is there a simple way to bring it to life?
Click to expand...
Click to collapse
Need a few more details:
- What were your trying to do? Why did you wipe dalvik in the first place?
- How did you partition your sd card?
- Which hboot are you on?
I take it you can still get into recovery? Make a backup anyway, you can recover stuff afterwards in the event you have to full wipe.
I've personally never had any luck with Link2SD, with CM7 I recommend you are on cm7r2 hboot and use S2E or Darktremor for A2SD, use either to move apps and dalvik to sd-ext.