-----------------------------
axl409 said:
hi, just a simple question: what is the better way to flash a kernel? for now i do so:
-wipe dalvik cache
-flash kernel
-reboot
is the dalvik cache wipe a necessary step? if i don't do it, could been any error?
another question: i use nightly rom, and sometimes i also use lordmodUE kernel. the question is: when i upgrade nightly (i upgrade every day), i do this step:
-easy upgrade wipe
-flash rom
-flash gapps
-reboot
-then i go again into recovery
-dalvik cache
-flash kernel
-reboot
can i do so:
-easy upgrade wipe
-flash rom
-flash gapps
-flash kernel
-reboot
jumping the first reboot?
thanks all for reply
Click to expand...
Click to collapse
the reason why flashing is relatively complicated and requires so much process is to ensure that during the flashing process, every possible errors or elements that may contribute to errors are eliminated. the mix and matching of roms and kernels are literally endless, hence the possibility of errors such as boot loops and other issue can occur.
if it works for you it works, then stick with what you do. I generally always clear dalvik if applicable to your ROM. cache at times, should there be a large upgrade.
with what you had mentioned about cutting out the 2nd reboot, I generally did what you suggested when I was running CM7s and I didnt have any issues. hope that give you an idea.
-----------------------------
axl409 said:
hi, just a simple question: what is the better way to flash a kernel? for now i do so:
-wipe dalvik cache
-flash kernel
-reboot
is the dalvik cache wipe a necessary step? if i don't do it, could been any error?
another question: i use nightly rom, and sometimes i also use lordmodUE kernel. the question is: when i upgrade nightly (i upgrade every day), i do this step:
-easy upgrade wipe
-flash rom
-flash gapps
-reboot
-then i go again into recovery
-dalvik cache
-flash kernel
-reboot
can i do so:
-easy upgrade wipe
-flash rom
-flash gapps
-flash kernel
-reboot
jumping the first reboot?
thanks all for reply
Click to expand...
Click to collapse
Reboot your phone after you flash your custom ROM before you flash your kernel. It is known that you if you dont, custom kernel doesnt work properly. Its something to do with not letting your phone build the necessary files for your kernel. I guess thats why it takes longer for the 1st boot
Related
I got a simple question about flashing a rom, at this point its JellyTime.
I'm not really familiar with the order that you need to flash and if you need to flash the kernel separately?
My order is now:
- clean/wipe
- Flash ROM
- Flash gapps
- fastboot flash boot.img (is this step required, or does this already happen when flashing the ROM?)
Then the follow-up question is, does it affect the ROM when you boot the first time with an older kernel?
Spluh said:
I got a simple question about flashing a rom, at this point its JellyTime.
I'm not really familiar with the order that you need to flash and if you need to flash the kernel separately?
My order is now:
- clean/wipe
- Flash ROM
- Flash gapps
- fastboot flash boot.img (is this step required, or does this already happen when flashing the ROM?)
Then the follow-up question is, does it affect the ROM when you boot the first time with an older kernel?
Click to expand...
Click to collapse
You can flash the kernel basically anytime. I usually dirty flash kernels with no problem.
Also, no need to fastboot the boot.img. The rest of your order looks fine.
My order :
- format all partitions (except sdcard)
- wipe cache/dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot
But i think your steps should be fine as well.
Sent from my Desire HD using xda premium
How do you fix permissions ?
When I flashed gapps I saw that in the end its fixing permissions. Do I need to something manually ?
Kobibo said:
How do you fix permissions ?
When I flashed gapps I saw that in the end its fixing permissions. Do I need to something manually ?
Click to expand...
Click to collapse
You can fix permissions using recoveries like 4ext and stuff...remember to wipe cache and davlik if you are flashing just kernel.
Like he said use recovery 4ext there's an option at "tools".
[ Sent from my HTC Desire HD using XDA-Premium App ]
RayRayX91 said:
My order :
- format all partitions (except sdcard)
- wipe cache/dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot
But i think your steps should be fine as well.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Wiping cache+dalvik cache is redundant after formatting all partitions. A lot of people have this habit and recommend it, but its unnecessary. Dalvik-cache is located in the data partition. It's nothing special, its a folder there like any other, and contains classes.dex files for all apps on the device. When you format all partitions, data is formatted, so the dalvik-cache is wiped along with it. And the cache partition is formatted anyway. So wiping cache+dalvik again after formatting all partitions is of no use and unnecessary.
ai6908 said:
You can fix permissions using recoveries like 4ext and stuff...remember to wipe cache and davlik if you are flashing just kernel.
Click to expand...
Click to collapse
You don't need to wipe cache and dalvik after flashing a kernel. I used to do it too, but many times the devs themselves have said it isn't required. Lord Clockan said many times that wiping cache+dalvik is unnecessary after flashing a new kernel. When you think about it, it makes sense. Dalvik cache just contains classes.dex files for all the apps on the device and nothing else. When the dalvik-cache is rebuilt after a wipe, it pulls the classes.dex from each apk and puts it in the dalvik-cache folder (please correct me if I'm wrong). This isn't in any way related to the kernel and what it does. Regardless of the kernel flashed, the dalvik cache will remain the same. So it shouldn't make sense to wipe it for every kernel flash.
Sent from my Desire HD using xda premium
RayRayX91 said:
My order :
- format all partitions (except sdcard)
- wipe cache/dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot
But i think your steps should be fine as well.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Hello, I did all of the steps in this order and ROM is booting OK. But after that I have random freezes while doing different tasks (taking picture, going to settings, after unlock). Do you have any suggestions what can I do/change to fix this. This is happening on all Jelly Time releases - i tried R3, R4, R5.1 and also AOKP V6. When I flash IcoColdSandwich everything is running without problem.
I will appreciate your help. Thank you!
My order :
- wipe data/factory reset
- wipe cache
- wipe dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot
Thanks, that makes it clear.
So its possible that you flash the kernel when you are flashing the ROM!
I couldn't post in the development thread but thought this post might be helpful to a lot of people.
Now I could possibly be wrong about this, but if I am correct; all ROMs that are up to date currently are all synced to the stock CM10 Gerrit picks. Now having KTweaker is a very nice function; (With UV and OC), but since it is technically "out of date" there might be some instability. Another case of matter, Undervolting and Overclocking can cause issues depending on the hardware of your phone. Settings that should be able to work with MOST phones are posted in the OP. (First page.) If after those values you are getting reboots, you can try to increase the values to see if that helps in any way. Otherwise, if they are happening too much I would recommend sticking to the stock CM10 kernel. Even though the kernel is flashed by stock when first flashing the ROM, if you would like to re-flash the stock kernel you can download it from Task & Ktoonesz ROM in the OP. Make sure to give thanks to them as they are very helpful and as opposed to dealing with questions on the regular hopefully this post helps answer some. Thanks for the great ROM by the way guys. -
On another note, I am using this kernel with AOKP and have yet to run into any issues thus far. I am not sure if you have tried this, but you can try the settings on the OP for good performance/battery life but not without clearing/wiping the phone properly. I understand some people hate full wiping but I find it to be necessary before reporting anything not functional. If you haven't done this and I quote from everyone who has said this and posts that recommend this process.
(I personally only recommend doing this after charging your phone to 100% to avoid draining issues.)
After download of latest ROMs/Kernels:
Reboot to recovery
-Wipe Data/Factory Reset
-Wipe Cache
-Wipe Dalvik Cache
-Wipe Battery Stats (Optional) (100% battery recommended.)
-Flash ROM
-Flash 7/26 Gapps package (Most stable as opposed to customized packages such as Inverted Gapps)
-Go to advanced settings once again.
-Reboot RECOVERY.
-Flash Kernel
-Wipe Cache & Dalvik ONLY, once more.
-Finally, Fix Permissions.
-Main menu and Reboot System.
Sent from my T&K Blessed SGH-I747
jaysoblitzed said:
.
(I personally only recommend doing this after charging your phone to 100% to avoid draining issues.)
After download of latest ROMs/Kernels:
Reboot to recovery
-Wipe Data/Factory Reset
-Wipe Cache
-Wipe Dalvik Cache
-Wipe Battery Stats (Optional) (100% battery recommended.)
-Flash ROM
-Flash 7/26 Gapps package (Most stable as opposed to customized packages such as Inverted Gapps)
-Go to advanced settings once again.
-Reboot RECOVERY.
-Flash Kernel
-Wipe Cache & Dalvik ONLY, once more.
-Finally, Fix Permissions.
-Main menu and Reboot System.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Wiping battery stats is unnecessary on these phones because Samsung uses an automatic calibration.
meleii said:
Wiping battery stats is unnecessary on these phones because Samsung uses an automatic calibration.
Click to expand...
Click to collapse
Ah I see. That I was unaware of. Luckily I posted it as optional. I find my battery to last an extremely long time with heavy usage especially when listening to music and such. I have yet to encounter a problem so far. I also recommend to those who use it; to download flash player and use Titanium Backup to keep it easily accessible, since after flashing AOKP you lose the ability to download it from the app market by stock without changing the DPI. A lot easier for those who don't want to tinker with those settings.
Sent from my T&K Blessed SGH-I747
Total newb question but on the CM10 thread they say:
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Click to expand...
Click to collapse
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
oshax said:
Total newb question but on the CM10 thread they say:
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
Click to expand...
Click to collapse
dirty flash means you didnt wipe data/cache.
most of the time, you can dirty flash newer versions of the same rom over the older version of the rom you have.
HOWEVER, if you have problems, you need to wipe data/cache and reflash the rom completely
Zepius said:
dirty flash means you didnt wipe data/cache.
most of the time, you can dirty flash newer versions of the same rom over the older version of the rom you have.
HOWEVER, if you have problems, you need to wipe data/cache and reflash the rom completely
Click to expand...
Click to collapse
Guess I might as well wipe the cache and dalvik even on a dirty flash?
Thanks
I upgraded from CM10 M1 to M2 with only a wipe of Dalvik cache. Works fine.
I finished installing M2 after wiping both the cache and dalvik cache (figured I would do the cache just in case).
Worked great!
Thanks all
oshax said:
Total newb question but on the CM10 thread they say:
Instructions:
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
Click to expand...
Click to collapse
***what Nexus version do you have?*** i've used the below instructions with GSM GNex***
If you're coming from an AOSP CM9 rom, Do the following :
Download Maguro (or your models ROM+Gappsl).
- boot into recovery.
- Preform NANDroid Backup.
- Wipe Dalvik cache.
- Wipe Factory reset.
- Wipe Cache.
- install zip from SDcard>choose zip from SDcard>ROM.zip (your ROM)
- Flash Gapps.zip
- Flash kernel.zip (if you have one)
- go to Advanced> Fix Permissions
- Reboot system now !
- Enjoy.
***I've used this method for a trillion flashes !***
No need to wipe anything when updating nightlies. Like it was said before, wipe data and reflash when you face problems.
Sent from my i9250
bk201doesntexist said:
No need to wipe anything when updating nightlies. Like it was said before, wipe data and reflash when you face problems.
Sent from my i9250
Click to expand...
Click to collapse
+1
Hello, since I upgrade my Galaxy Nexus ( maguro ) to Android 4.3, I can't flash any kernel. When I boot, there are a lot of force close of PhoneUI, and my phone turns off. When I try to restart, he is locked on the bootanimation.
Things I tried :
-Wipe data + Flash Rom and gapps + boot + Flash kernel
-Come back to 4.2.2 ( same problem, even though I try to flash a 4.2.2 kernel )
-Flash the Factory Image in 4.2.2 and 4.3
What can I do ? Please help me, I'm desperate
( Sorry for my bad english, I'm french )
Try doing a full wipe, install ROM/GApps, boot, reboot, then kernel. My routine typically goes:
Wipe cache, Dalvik, system, and data.
Flash ROM
Flash GApps
Reboot phone
Once phone is booted again reboot to recovery
Wipe cache and Dalvik
Flash kernel
Reboot and done.
Never had a single problem doing it this way. May be a few unnecessary steps, but I don't mind as it's only a couple minutes at most.
I'm on zenity 22.02.17 build, and now it's out the 4.3.17 update. I have installed render kernel, so now can i just follow the update instructions (flash rom,gapps,supersu, wipe cache and dalvik and reboot) or i have to do something other ?
eraser3000 said:
I'm on zenity 22.02.17 build, and now it's out the 4.3.17 update. I have installed render kernel, so now can i just follow the update instructions (flash rom,gapps,supersu, wipe cache and dalvik and reboot) or i have to do something other ?
Click to expand...
Click to collapse
Flashing a rom will replace your custom kernel, so you'll need to reflash that as well