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
Related
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 just have a simple easy question I'm running cm9 and when I get a update threw rom manager what do I wipe before?
Sent from my Nexus S using XDA
Wiping just the cache and dalvik cache should work fine.
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.
Ok, I did a system wipe, cleared the dalvik and cache, rebooted to fastboot flashed the stable cm10 rom, went back into recovery and flashed rom and flashed gapps. cleared cache and dalvik and rebooted. Everything works fine but i keep getting a warning that states "Unfortunately Android(AOSP) keyboard has stopped. Would Gapps have anything to do with this?
RC196 said:
Ok, I did a system wipe, cleared the dalvik and cache, rebooted to fastboot flashed the stable cm10 rom, went back into recovery and flashed rom and flashed gapps. cleared cache and dalvik and rebooted. Everything works fine but i keep getting a warning that states "Unfortunately Android(AOSP) keyboard has stopped. Would Gapps have anything to do with this?
Click to expand...
Click to collapse
What hboot are you on bro? If its the latest, you need to flash the boot img FIRST. Then go and wipe all cache types, system and factory reset. Then flash CM.
Sent from my One X using xda premium
ToxicWaste said:
What hboot are you on bro? If its the latest, you need to flash the boot img FIRST. Then go and wipe all cache types, system and factory reset. Then flash CM.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I did all that. Sorry didn't provide all of it in details. I guess its becaue of Gapps 4.2. I'm flashing an older version of gapps.
Yep that was the problem. I wiped everything and reflashed rom and older version of Gapps and problem solved.
running stock rooted vrbmb1 and can not get M.O.A.R 4.01 to boot. Can someone help
Just wipe everything cache, dalvik cache, factory reset and wipe system then try if not you probably got a bad download and just redownload the Rom
Sent from my SCH-I535 using xda app-developers app