Related
Im on cm7 with dragon kernel. If I wanted to flash faux kernel, do I need to reflash cm7? My guess is I would probably would need to reflash the entire ROM over.
Sent from my LG-P999 using XDA App
No, just wipe cache and dalvik cache in recovery then flash any kernel. And i believe if you want to go back with cm kernel, same wipe then reflash rom..
Sent from my LG-P999 using Tapatalk
noodles2224 said:
No, just wipe cache and dalvik cache in recovery then flash any kernel. And i believe if you want to go back with cm kernel, same wipe then reflash rom..
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
+1
I also started doing a fix permissions after flashing new kernel.!
fcisco13 said:
+1
I also started doing a fix permissions after flashing new kernel.!
Click to expand...
Click to collapse
I+1 for the fix permissions and I ndont see a stock cm kernel so I think he is right if you want stock cm kernel you have to reflash or restore a nandroid backup.
Couldn't you technically go thru advanced restore and just flash the kernel? I've only gone into there once but can't remember the options available. (This would be to restore cm7 kernel only, follow previous instructions for new kernels)
Sent from my LG-P999 using xda premium
wgrant said:
Couldn't you technically go thru advanced restore and just flash the kernel? I've only gone into there once but can't remember the options available. (This would be to restore cm7 kernel only, follow previous instructions for new kernels)
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I think advanced would only let you restore system, data, cache, dalvik cache, boot.img, individually
fcisco13 said:
I think advanced would only let you restore system, data, cache, dalvik cache, boot.img, individually
Click to expand...
Click to collapse
Just checked it and was about to edit my post. You are correct, no kernel option, would be cool if backups created included the currently installed kernel and you could restore thru that too.
Sent from my LG-P999 using xda premium
I just flashed the MXH Superlite rom (http://forum.xda-developers.com/showthread.php?t=1525638&page=43) as per the instructions onto my skyrocket i727. Wiped it, cleared dalvik cache and formatted the system. Installed the recommended modem followed by the rom, and the phone was stuck on the Samsung startup screen. I've recovered using a backup, but I really want to install this rom. Whats the problem here?
Try booting into cwm and re wipe and reinstall, try just the rom this time
Sent from my SAMSUNG-SGH-I727 using xda premium
I was gonna flash this ROM later tonight have other ppl had issues?
Sent from my SAMSUNG-SGH-I727
droid512 said:
I was gonna flash this ROM later tonight have other ppl had issues?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Your best bet is review the MHX-SUPERLITE thread in the Development section... and ask there. This rom is on my "next to flash" list as well...
I flashed it on a friends sr no issues but it progressively got slower and crawled after first reboot it was odd.
Sent from my SAMSUNG-SGH-I727
droid512 said:
I flashed it on a friends sr no issues but it progressively got slower and crawled after first reboot it was odd.
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Mhx will say its cuz he is stuck developing on a non apple device
Sent from my SAMSUNG-SGH-I727 using Tapatalk
You need to wipe everything a couple times before flashing on these phones and sometimes install 2-3 times too
Wipe data, cache partition, and delvik 3x's each and install twice or something
Non-bricked Skyrocket since 2-11-2012
I've never once installed multiple times multiple wipes yes but multiple installs????
Sent from my SAMSUNG-SGH-I727 using Tapatalk
safzal433 said:
I just flashed the MXH Superlite rom (http://forum.xda-developers.com/showthread.php?t=1525638&page=43) as per the instructions onto my skyrocket i727. Wiped it, cleared dalvik cache and formatted the system. Installed the recommended modem followed by the rom, and the phone was stuck on the Samsung startup screen. I've recovered using a backup, but I really want to install this rom. Whats the problem here?
Click to expand...
Click to collapse
Try Flashing a different Kernel
What I do every ROM flash and never an issue.
1. Flash Darkside
2. Flash Modem (if I'm changing)
3. Flash ROM
4. Reboot
Sent from my SAMSUNG-SGH-I727 using xda premium
i have just flashes cyangonmod 10 jelly bean for my htc one x at&t and it works good and looks good. the ROM was compatible with my phone and i downloaded it from xda. only problem is that the ROM will keep freezing randomly and i will have to reboot my phone. any suggestions?
Wipe before flashing.
lazarat said:
Wipe before flashing.
Click to expand...
Click to collapse
i completely wiped my entire phone haha. i tried flashing again and it does the same thing. should i delete cache before i reboot?
lazarat said:
Wipe before flashing.
Click to expand...
Click to collapse
it also happens right after i press the switch task button after 9 minuets of use
When in twrp you wipe dalvik cache, cache and factory wipe before flashing a new rom
lazarat said:
When in twrp you wipe dalvik cache, cache and factory wipe before flashing a new rom
Click to expand...
Click to collapse
Yes I did all of that.
Could be a corrupted ROM file from downloading from server. Try downloading it again and reflash it.
Sent from my One X using xda app-developers app
They flashing an old ROM like clean ROM 4.0 for some reason certain Ppl are having issues but flashing that ROM then re flashing cm10 seems to help...are u coming from a 4.0.4 ROM? That for sure causes issues as the jb is built off the 4.0.3 kernel
Sent from my One X using xda app-developers app
A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...
Brian Gove said:
A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...
Click to expand...
Click to collapse
If I switch ROM's I factory reset then wipe cache and dalvik cache. If it's a theme for example I only wipe cache and dalvik cache since the theme is suppose to be made for your ROM right?....don't see the reason to reflash the ROM as well.
Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium
Il throw a vote to whichever works.. I usually dirty wipe.. If I have issues then clean it and try again.. With nightlies I tend to be fine dirty a lot, but even still I will do a clean every couple weeks just because..
why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Dirty wipe
Sent from a SYNERGIZED GalaxySIII
When I dirty flash, I wipe data cache n dalvik cache. Once I flash what I wanted, I wipe those two once again n select "fix permissions" just in case
Sent from my SCH-I535 using Tapatalk 2
apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Click to expand...
Click to collapse
I disagree. I believe a dirty flash also wipes system. If you are 100% certain that your ROM build effectively wipes system as part of it's install routine, then you could skip this step, however I always wipe system to be safe. This works for me and I rarely need to wipe data or sd card(s).
---------- Post added at 11:01 AM ---------- Previous post was at 10:57 AM ----------
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that?
Click to expand...
Click to collapse
When changing Kernels but not the ROM in a separate recovery session than a ROM flash, you don't need to "dirty wipe." Just wipe cache and dalvik. Dalvik wipe is key so that the dalvik virtual machine can be rebuilt by the new kernel.
Thanks for the info guys.
I usually dirty on nightlies until I have issues. Always clean when switching roms.
Sent from my SGH-I535 using xda app-developers app
It is always good to complete wipe when switching roms.
Sent from my SCH-I535 using xda premium
What if im just switching between stock rom nandroid backups? Can I just restore from one to one? I only have two backups anyways both for stock. Never flashed a rom before
Tap'n
grin0048 said:
This isn't meant to be rude or anything, I'm just honestly wondering if there's any logical reason to think this is substantively different than just not wiping data?
Click to expand...
Click to collapse
I find that this method works better than just wiping cache and dalvik, since im advance restoring data over a clean flash. both ways are considered dirty flashing tho.
I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?
coldhardtruth said:
I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?
Click to expand...
Click to collapse
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app
droidstyle said:
why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form
Click to expand...
Click to collapse
Factory reset doesn't touch the davlik(Which I speculate(Guess) has to do more with the kernel than anything)
apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This is what I meant as a dirty flash when I made the thread yes...
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Usually when I flash a new kernel, or a different kernel, I just wipe the davlik cache and I am fine. There was some reboots after the first boot on the AOSP ROMs but afterwards it ran fine.
SlimSnoopOS said:
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
SlimSnoop is correct. According to one of the developers of a very prominent ROM the IMEI issue was because our phones got confused sometimes(Randomly phone to phone) and tried to reset during a flash. The data it tried to reset was bogus, therefor losing IMEI. He is also correct far as the wiping battery stats. It's only usefull when you have really strange results with battery. Google for the real reason to use them.
Far as backing up your IMEI so you will never run into the problem of losing it.... go into your terminal (almost every ROM has a Terminal emulator)
Type this:
su
then hit enter. Grant permissions
then type:
reboot nvbackup
then hit enter. This will make your phone do some shyt and reboot, but you really shouldn't need to worry about your IMEI after this. Regardless of how many ROMs you flash or what you do or who you date or who you kiss, etc... blah blah....
This really should be the end all for the IMEI...
annoyngduck said:
Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
New rom only when their bases are different , like going from ics to jb, or the dev says to do it (Even then Ill try it without a wipe because im lazy).
Themes I never wipe anything
Nightlies never wipe anything.
Edit: If I do have issues I then go back and wipe delvik and cache . That usually straightens out any issues and allows me to keep my setup.
tonu42 said:
Hey but you know I'm right
Click to expand...
Click to collapse
Actually you're not right.
Sent from my SCH-I535 using Tapatalk 2
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.