Clarifying here, it's a simple question.
I saw several people in the blu_spark custom kernel thread saying that you don't need to do a full wipe and flash stock OOS to flash the kernel. If I'm coming from stock rooted with TWRP, am I able to just flash the kernel itself without wiping anything? New to flashing custom things in general.
Dont know for sure, but what I'd suggest is to Flash the Kernel & Wipe Dalvik before reboot, thats what i do, no problems so far, same for updates too.
You don't need to wipe Cache/Dalvik because Kernel has nothing to do with them. Only thing you have to check for is if the Kernel you want to flash grabs the ramdisk from the Kernel that is installed or comes with its own.
Im using despair kernel
Scherzengel said:
You don't need to wipe Cache/Dalvik because Kernel has nothing to do with them. Only thing you have to check for is if the Kernel you want to flash grabs the ramdisk from the Kernel that is installed or comes with its own.
Click to expand...
Click to collapse
How would I be able to check this?
Ask the Dev of the Kernel you want to install. But first read the description of the Kernel and the Devs advice for Installation.
Most kernels do not require a whole system wipe like that. As long as the kernel is compatible with the ROM you should have no problems in just plain flashing it. You can find out if it is compatible by looking on the Original Posting by the developer. Another thing to note: if a kernel developer does not specify a ROM compatibility and yet a kernel installs and the ROM even boots up that does not mean you are completely bug free. An example of this would be using blu_spark's OOS kernel on CM 13. It will flash, boot, but your phone will lag, randomly reboot, apps will force close, etc.
He actually has a beta kernel for CM 13 so that you can use his customization and without above issues.
Related
Hi
I am new on the SGS2 though i have one Android Tablet.
I have been reading a lot and there is something i have not been able to find.
I want to root, , install CMW and install this custom ROM: Dynamic
http://forum.xda-developers.com/showthread.php?t=1582217
1.- Do i need to install first the CF-ROOT kernel matching my actual Firm to make the root or can i install the Siyah kernel at this will make the root anyway?
2.- If i install the CF-root using ODIN, do i need to install an specific kernel for that ROM? Or most kernels work with most rom?
Thanks.
I suggest you flashing the cf-root kernel with odin then you can install your custom rom from the modified recovery mode flashing the .zip file of the rom.
You can flash the siyah kernel after that, because generally custom roms mount a custom kernel which supports CWM (Clock Work Mod, the custom recovery).
If i helped u, press thanks.
if you are on ics you should be good flashing siyah but most of us here started with cf root
darkpollo said:
Hi
I am new on the SGS2 though i have one Android Tablet.
I have been reading a lot and there is something i have not been able to find.
I want to root, , install CMW and install this custom ROM: Dynamic
http://forum.xda-developers.com/showthread.php?t=1582217
1.- Do i need to install first the CF-ROOT kernel matching my actual Firm to make the root or can i install the Siyah kernel at this will make the root anyway?
2.- If i install the CF-root using ODIN, do i need to install an specific kernel for that ROM? Or most kernels work with most rom?
Thanks.
Click to expand...
Click to collapse
1/ follow the install notes stated for that rom also siyah kernel if flashed thru odin will give you root and install cwm/superuser
2/if you install cf root again follow install notes within that thread and it does say best to use same cf as your stock kernel or find one close to it to match
i prefer to use siyah less hassle but each to there own and everyone has there own choice
Thank you all.
I decided to go safe and try with CF-Root. Now i am rooted and i have installed the rom using the CWM.
Do you recommend to change the kernel again? I think that the rom has its own kernel but i am not sure.
Also something weird happen (little off topic), after wipe and reinstall the rom, i have some apps installed by default, some of them where on the old ROM.
I thought that all the apps will be deleted with the installation of the new rom.
Not sure how to fix it.
Thanks again
Apps will only be deleted by doing a full wipe in cwm. And you dont need to flash another kernel if you only want the root feature.. i think all the custom roms use a rooted kernel... some use cf-root, some siyah, some speedmod etc...
Well, i really prefer to use the features offered by other kernels. I was not sure if i can change the kernel keeping the Roms or if i need to reinstall everything afterwards.
How do i make a Full Wipe? most of the apps are bloatware and i do not want them.
Thanks
im also a noob and i use siyah without changing much
just OC to 1400 and choosing en demand for governor
darkpollo said:
Well, i really prefer to use the features offered by other kernels. I was not sure if i can change the kernel keeping the Roms or if i need to reinstall everything afterwards.
How do i make a Full Wipe? most of the apps are bloatware and i do not want them.
Thanks
Click to expand...
Click to collapse
You must go in the custom recovery and press "Data wipe/factory reset", so you wil have only the system apps, but you must start the phone configuration again.
U can flash another kernel if you want, there's no problem with the rom, but remember to do a dalvik wipe.
If youre thinking about to flash a new kernel, i would prefer to flash the kernel first (now) and then do a full wipe and dalvik wipe. Otherwise youre doing some work twice...
And if youre yet haveing some "bloatware" (e.g. from a provider branded firmware) after wipeing, you can delete them (be careful with system apps) with root explorer... (in "\system\app" folder....
darkpollo said:
Thank you all.
I decided to go safe and try with CF-Root. Now i am rooted and i have installed the rom using the CWM.
Do you recommend to change the kernel again? I think that the rom has its own kernel but i am not sure.
Also something weird happen (little off topic), after wipe and reinstall the rom, i have some apps installed by default, some of them where on the old ROM.
I thought that all the apps will be deleted with the installation of the new rom.
Not sure how to fix it.
Thanks again
Click to expand...
Click to collapse
If your happy with the results you get form using CF then by all means stay with it otherwise follow the thread in which your rom is based on users will often leave feedback on there selected kernels and setups like my signature for example check im sure theres users within your choosen thread with the same
I can advise using the kernel cleaning script after changing to another kernel. http://forum.xda-developers.com/showthread.php?t=1363738
This will prevent problems that left behind files from the old kernel can cause.
After flashing the file/script install the desired kernel
Thank you to everyone!
Ubbabubba said:
You must go in the custom recovery and press "Data wipe/factory reset", so you wil have only the system apps, but you must start the phone configuration again.
U can flash another kernel if you want, there's no problem with the rom, but remember to do a dalvik wipe.
Click to expand...
Click to collapse
I did the Data wipe/factory reset and everything as per the instructions:
*For a clean installation and no problem
- Download the ROM and put it on your S2.
- Go to Recovery
- Wipe data factory reset, wipe cache.
- In Advance: wipe dalvik cache and wipe battery stats.
- In mount and storage - format data , system and cache
- Install the zip file and you will get the CWM install completed message.
- Select Reboot Now and let the phone boot up to an Android setup screen.
- If there are Update, download it, put it on the phone, go to recovery and install it. Don't do wipes.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1582217
glowfinger said:
If youre thinking about to flash a new kernel, i would prefer to flash the kernel first (now) and then do a full wipe and dalvik wipe. Otherwise youre doing some work twice...
Click to expand...
Click to collapse
I think i am going to make it more than twice.
I will go to other kernel to try them. The battery on CF is not as good as i would like.
glowfinger said:
And if youre yet haveing some "bloatware" (e.g. from a provider branded firmware) after wipeing, you can delete them (be careful with system apps) with root explorer... (in "\system\app" folder....
Click to expand...
Click to collapse
That is the strange thing. I am not using any branded firmware, i came from one, but i thought everything was to be erased after the wipes and formats.
Spunkynitro said:
I can advise using the kernel cleaning script after changing to another kernel. http://forum.xda-developers.com/showthread.php?t=1363738
This will prevent problems that left behind files from the old kernel can cause.
After flashing the file/script install the desired kernel
Click to expand...
Click to collapse
I will use this on my next try this weekend.
If i do not understand wrong this is what i need to do:
Review the rom to find a kernel that suits it.
Use the kernel cleaning script
Install the new kernel.
Follow the instructions to flash the desired ROM with all the wipes and formats required.
Anything else?
I got tasked with fixing someones evo lte. He flashed a kernel. cm wont boot or when it does it says some error. now everything bootloops. i tried flashing back to a sense rom and it would hang on the installing kernel part of the installation. finally it finished but just bootlooped.
when it was able to have cm or aokp, can't remember which, to be installed and boot, it would still show that new kernel as the kernel running on the phone.
Ideas?
flash a new rom and then a new kernel?
ive never had the issue of not being able to get back to whatever kernel is packed with the rom.
and really, i've only been able to boot it once since it was brought to me.
right now its pretty much a boot loop all the time.
and yes, wipe, factory reset, wipe cache dalvik all that has been done multiple multiple times
im a One X user, so im familiar with this stuff but all the roms and kernels are different and so im also kinda lost here
thanks
Boot to bootloader and fastboot install kernel for the rom, make sure the base matches 2.13 kernel and ROM, sense with Sense, AOSP with AOSP etc. Meanrom and a few others have built in kernel installers but if for some reason it doesn't boot, extract boot.img from the rom zip.
Lately i'm experiencing problems with flashing custom roms (i.e. UltimaROM , Xperianze, whatever)
What i did is:
1: flash the latest CWM , touch and non -touch with Odin
2: download ROM of choice , copy to internal SD-card
3: reboot recovery, fact-reset, wipe cache + dalvik
4: flash rom ( with aroma installer )
5: boot phone
with booting it keeps hanging on the Samsung i9300 logo txt. It doesnt matter which rom i flash. it always keeps hanging.
I've tried alternative methods like flashing TWRP and do the same as above but again, no success. I also tried factory-reset after flash, cache wipe etc. no success.
The weirdest thing is: when i try to flash CM or MIUI ( current running MIUI ) , it works like a charm, but normal "custom" roms are not approved it seems.
does anyone have a suggestion for me what to do? or explain what i am doing wrong , or even better, can explain why CM-based ROMS work?
Have you checked the MD5 of your downloaded ROMs when they are on your SD card? Format system, data and pre-load before flashing? Tried flashing an alternative kernel/radio before you boot the first time?
If only stock based ROMs are a problem then it maybe something that is unique to them, probably a direct hardware hit via the kernel.
Try returning completely to stock to test, flashing Samsung's vanilla EMB5 via Odin - including stock recovery and full wipe. If that doesn't work then you may have a hardware issue that CM or MIUI doesn't use.
yeah good idea to return to stock and try all over again.
to your other questions: no i didnt flash another kernel after i flashed the custom rom. i've tried with several kernels which options were given to me in aroma installer ( boeffla, syah, stock )
md5: did that
format system and data: nope. kinda relied on the fact-reset + cache/dalvik
what do u mean with pre-load?
if I were you I would format data & system again manually after the fac. reset thing, or even more clean use the mega wipe flashable zip to have a clean slate to start from (it will format anything but the ext. sd-card). Then flash the rom from your ext. sd-card and see how it goes.
additional possibly helpful hints
hi there,
i'm not entirely sure if this will help you but generally speaking i came made a few observations about the fact that some people, mostly repeatingly the same users, encounter problems with their custom roms and/or flashing them, while others don't, albeit they are using the same devices.
i my selfe use 3 different devices, all rooted and running on pac 4.3, always lates nightly, as there are GT-N7100 - GT-I9100 - Nexus 4
not to the point
a) other than most other users i usually clean cache and dalvik cache as well before and after flashing the new rom and/or new nightly
and never encountrer any problems except those which everybody, using the same rom and nightly encounters.
b) whenever i flash an totally different rom and/or upgrade and/or downgrade to another level of android os, i.e. from 4.2.2 to 4.3, i perform
a clean install, including not only a factory reset, but as well a format sd-card, format cache and format system etc., again i cannot proof
which of these steps make a or the differnce but however, i never have problems others than thosw which everyone has with a version.
c) when using cusome kernels and due to the fact that some roms come with a kernel included, as well as with a custom recovery included,
it is strongly recommended not to forget to flas the kernel again after each flashing the new rom. one good example ist dorimanx kernel
for GT-I9100 which will not boot into recovery and reluctantly boot at all after a new flash of a pac nightly without reflashing the kernel.
d) try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
why that should, but however, sometimes it's better to be on the safe sid.
e) try to run whether the lastes version of custom recovery for your device, and or the use the included custom recovery of the rom or the
kernel. this again is one thing that can help to avoid some unexpected and hard to explain bootproblems and/or fc's etc.
hope that i could give you some new ideas how to avoid trouble while using custom roms and other hacks
magnamentis said:
try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
Click to expand...
Click to collapse
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
thanks for the explanation which makes totally sense, so my feeling which i could not explain was right always better to learn exactly why than just guessing
no thanks button found in your post however, so i want to thank you this way.
regards
hello all,
After upgrate cm-10.1.0-galaxysmtd.zip to cm-10.1.2-galaxysmtd.zip i dont have recovery mode, playstore and rom manager...
how to repair all ?
thanks in advance.
after some manipulation i have just a mode download....:crying:
problems with flashing roms and/or booting in to recovery
hi there,
i'm not entirely sure if this will help you but generally speaking i came made a few observations about the fact that some people, mostly repeatingly the same users, encounter problems with their custom roms and/or flashing them, while others don't, albeit they are using the same devices.
i my selfe use 3 different devices, all rooted and running on pac 4.3, always lates nightly, as there are GT-N7100 - GT-I9100 - Nexus 4
not to the point
a) other than most other users i usually clean cache and dalvik cache as well before and after flashing the new rom and/or new nightly
and never encountrer any problems except those which everybody, using the same rom and nightly encounters.
b) whenever i flash an totally different rom and/or upgrade and/or downgrade to another level of android os, i.e. from 4.2.2 to 4.3, i perform
a clean install, including not only a factory reset, but as well a format sd-card, format cache and format system etc., again i cannot proof
which of these steps make a or the differnce but however, i never have problems others than thosw which everyone has with a version.
c) when using cusome kernels and due to the fact that some roms come with a kernel included, as well as with a custom recovery included,
it is strongly recommended not to forget to flas the kernel again after each flashing the new rom. one good example ist dorimanx kernel
for GT-I9100 which will not boot into recovery and reluctantly boot at all after a new flash of a pac nightly without reflashing the kernel.
d) try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
why that should, but however, sometimes it's better to be on the safe sid.
e) try to run whether the lastes version of custom recovery for your device, and or the use the included custom recovery of the rom or the
kernel. this again is one thing that can help to avoid some unexpected and hard to explain bootproblems and/or fc's etc.
hope that i could give you some new ideas how to avoid trouble while using custom roms and other hacks
Hi,
I want to temporary boot my nexus 6 with ElementalX.
I'm familiar with the fastboot command fastboot boot boot.img
But what boot img I need to use after downloading the flashable zip file of the kernel?
Pics provided below, which file I need to use for the fastboot command?
I don't believe you can flash Elemental kernel in that regards as it is set up differently than many custom boot.imgs. Even if you did, you would be missing out on many functions of the kernel without the other settings being installed. You could either do a nandroid backup of your boot and system and restore that when you were done testing the kernel or dirty flash just the rom you are on (they have flashable stock roms in the forums) while just wiping the cache and dalvik cache.
es0tericcha0s said:
I don't believe you can flash Elemental kernel in that regards as it is set up differently than many custom boot.imgs. Even if you did, you would be missing out on many functions of the kernel without the other settings being installed. You could either do a nandroid backup of your boot and system and restore that when you were done testing the kernel or dirty flash just the rom you are on (they have flashable stock roms in the forums) while just wiping the cache and dalvik cache.
Click to expand...
Click to collapse
I only want to flash ElementalX in order to be able to use properly on Android M.
But I'll try to do a nandroidbackup . funny I never though to do that. Thanks.
Yea, for best results, use TWRP, make a backup, then flash what you need. No reason to keep a stock recovery setup if you are running a custom kernel and root as you will not want to take OTA updates anyway. Keep in mind that it is also recommended to update the radio and bootloader. I have seen reports of members being fine without them, but it's best practice to keep them all updated together. If you don't want to mess with any of that and don't care about being rooted or customized at all, then you will just want to unlock the bootloader and flash the factory img files from Google and then all partitions will be updated to official 6.0 and you'll be done with it. If you go that route, remember to backup your internal storage as unlocking the bootloader and the update will wipe everything.