Dalvik cache after flashing stock - AT&T Samsung Galaxy S II Skyrocket SGH-I727

I flashed the stock AT&R ROM with Odin.
After setting back up and reinstalling apps I got an error during a market install saying there was not sufficient space for install.
I researched and found that some people have gotten this and remapped the cache to the SD card and it may be an issue with the Dalvik cache needing to be cleared.
After the flash of stock I did not restore phone to defaults via the stock recovery menu (vol up/vol dn/pwr). So I have now done that and am in the process of reinstalling again but it got me thinking...
If the only way to clear the Dalvik cache is to use CWM, then how to you maintain Stock (to get AT&T updates) because you need CWM to clear cache after flashing?
Or am I just severely confused??
Sent from my SAMSUNG-SGH-I727 using Tapatalk

To answer your question. Flash cwm in odin, clear dalvic cache. Then flash stock recovery. Done!!
Sent from my SAMSUNG-SGH-I727 using xda premium

This should be in q&a
Sent from my SAMSUNG-SGH-I727 using Tapatalk

Related

[Q] CM7 with gapps built in?

Hi all,
on my very first flash of CM7, I had to install gapps. All worked well and I was happy.
Since then, every time I flash CM7, I get gapps already installed (yes I wiped all, yes I cleared dalvik cache, I even did the lock/unlock thing in order to clear all data).
I somehow get the feeling that my flashes are not a "clean" install.
did anyone else experience this as well?
thanks...
On your first time on CM7, wipe everything, flash cm7, flash gapps. When you want to update cm7, jus wipe cache and dalvik, then flash the updated cm7. No need to reflash gapps, no need to do a full wipe either.... unless you want to.
-Nexus S
So you mean that from now on. Gapps will always be installed? Even after full wipe/ factory settings?
Sent from my Nexus S using XDA Premium App
asafru said:
So you mean that from now on. Gapps will always be installed? Even after full wipe/ factory settings?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
That's not what he meant. He meant that if you are upgrading CM7, you do not need a full wipe at all.
But after a full wipe your Gapsps should be gone. It's weird that it is still there after a wipe. :S
It's still there after a wipe... is there a way to make sure I full wipe correctly?
Sent from my Nexus S using XDA Premium App
asafru said:
It's still there after a wipe... is there a way to make sure I full wipe correctly?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Wipe Factory/Dalvik/Cache: Full Wipe
Wipe Factory: Removes Apps + Settings
Wipe Dalvik/Cache: Wipes the cache but your apps + settings remain.
Wiping factory will delete your Gapps.
Proper way to flash CM7:
1. Wipe Factory/Dalvik/Cache
2. Flash CM7
3. Flash Gapps
4. Flash Kernel (Optional)
5. Reboot
Proper way to upgrade
1. Wipe Dalvik/Cache (Optional)
2. Flash Kernel (Optional)
3. Flash CM7
3. Reboot
asafru said:
So you mean that from now on. Gapps will always be installed? Even after full wipe/ factory settings?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Upgrading to newer versions will now keep all your data in tact, so gapps will be there etc.
great, I think it's all sorted out now.
just one question though, I've read that CWM dalvic cache wipe doesn't work. Is that true?
If so, what is the best way to wipe dalvic cache and do factory reset (fastboot/adb commands are also welcome..)
asafru said:
great, I think it's all sorted out now.
just one question though, I've read that CWM dalvic cache wipe doesn't work. Is that true?
If so, what is the best way to wipe dalvic cache and do factory reset (fastboot/adb commands are also welcome..)
Click to expand...
Click to collapse
It works. Somebody confirmed this, the error that pops up during CWR is SD EXT.
You can check for yourself, run a logcat (search the forum) while the phones booting.

How should you flash a rom and a kernel?

What are the steps should u flash a kernel right after you flash a from or should you reboot then flash the kernel thanks for your help!
Sent from my Nexus S using xda premium
Hi There,
I always flashed the kernel right after flash the rom and haven't got any issues.
For a new rom, data factory reset, format /system and format /boot then flash straight away most of the time. For an upgrade, only wipe cache and dalvik cache.
For a kernel it depends, but generally just cache and dalvik cache will be fine.
Wipe cache and Dalvik cache before flashing ROM as well. I do wipes 2 or 3 times..
Sent from my Nexus S 4G using XDA App
I always do a double wipe before flashing any new rom and do a dalvik/cache-wipe before flashing a new kernel
For that i use the attached filed. Just flash via recovery (any). Helps to do it a little bit faster like doing in manual

[Q] custom ROM boot problem!

Hey everyone,
I'm a new-by to the tech world. I have a "google nexus s" running on ICS 4.0.4, I recently rooted my phone, flashed clockworkmod recovery and tried to install CM9 on my device. After the installation was completed through the clockworkmod, the boot image had showen up and continued to boot throughout the night and never showed up the home screen nor did the custom ROM open itself.
Can anyone give me a lil help as to about what this problem is or the reason why this is happening?
Any help would be really appreciated.
Thanx!
Did you do a full wipe and cache wipe? My suggestion is to do that and reinstall. You could also try a different ROM.
But wouldnt I loose my phone data if I do that?
Sent from my Nexus S using xda premium
i'm having the same problem for every ROM i try on my phone! what to do?
You have a bootloop, this appears because of kernel (boot.img) problems and/or inconsistent cache.
Please wipe/erase cache and Dalvik cache (this can be found in the Advanced menu). Wiping cache partition and Dalvik cache won't erase your personal data.
Make sure the previously flashed CM zip contained a boot.img file. If not, please flash a proper/recommended boot.img (kernel; which is in a zip file) or another rom (with boot.img).
When you flash a new rom over your stock.. first make a backup, then you need to wipe data, cache and dalvik cache..
Sent from my Nexus S using XDA app
Got a backup and mods are running cool! Thanx for the help!
Sent from my Nexus S using xda premium

I seriously can't figure it out.

I've been tinkering with androids for well over a year now and have rooted unlocked and s-off'ed amongst other things many different devices. For some reason I'm having trouble flashing kernels to my s3. Yes I'm unlocked and yes I'm flashing aosp kernels to aosp roms and touchwiz kernels to touchwiz roms. The problem seems most persistent on aosp roms and yes I've also checked that they both had the same cm10 commits. The only kernel I could get to boot was clean kernel on beans custom. Other than that no other kernels will work. The device will boot then the screen will start glitching up and then eventually bootloop. I've also made sure to wipe dalvik and cache plus fix permissions. I've also tried just flashing the kernel after doing a full wipe and starting with a new rom and have root 66ed back to stock and re unlocked. Is there something I'm missing here? I'm getting frustrated as I love custom kernels. Oh and the latest combo I tried was liquid smooth rc3 and lean kernel 1.0. Thanks guys.
Sent from my SCH-I535 using xda app-developers app
did you try wiping cach, davik cach, and fix permissions AFTER flashing then reboot?
Ofc wipe cach and dalvik cache before also.
My usual process goes something like this
*Wipe Cache
*Wipe Dalvik
*Flash Kernel
*Wipe Cache & Dalvik again
*Fix Permissions
Works like a charm every time.
Samsung Galaxy S3
i have had the same trouble once...fixed it by flashing back to a stock kernel first.
try this:
wipe cache & dalvik
flash stock kernel.zip- http://db.tt/ceeDTAfz
flash custom kernel
reboot
Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app
sumredhed567 said:
Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app
Click to expand...
Click to collapse
stock kernel = stock TW kernel
Sent from my SCH-I535 using xda app-developers app
Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app
sumredhed567 said:
Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
another thing you might try is formatting system in cwm.
droidstyle said:
another thing you might try is formatting system in cwm.
Click to expand...
Click to collapse
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!
sumredhed567 said:
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!
Click to expand...
Click to collapse
now when you odin back to stock, your booting into stock recovery after flashing the rom(root66) and doing a data wipe/factory reset correct? you said full wipe, but just want to be clear. it may be corrupted internal memory and might need to be reformatted.
I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app
sumredhed567 said:
I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
follow section 6 of my guide...link in sig!
Always perform a full/mega wipe as:
1) Wipe data/factory reset
2) Wipe cache partition
3) Wipe dalvik cache
4) In mounts/storage section wipe /system
5) wipe /data
6) wipe /cache
7) wipe /preload
Then flash new ROM.
For flashing a kernel, please perform steps 2 and 3.

[Q] what happens if i didnt wipe cache and delvik before updating cm10?

so i updated cm10 to a newer version and i didn't wipe anything i just flashed the zip file and everything booted up fine but now im worried that something may go wrong in the future can anyone help??
Boot to recovery and wipe cache and dalvik. Reboot and you should be good.
If you start getting issues, consider reflashing will all the wipes.
Sent from my Transformer using xda app-developers app

Categories

Resources