so im trying to get MIUI on my evo, but when i flash it it sticks at the sprint bootloader. i got the rom from MIUI. anyone help?
Did you wipe everything before flashing? Have you tried other kernels?
i have wiped data and cache. and im sorry but im new at this, what is a kernel
first of all, try also wiping data ( i kno its hard, just back up with titanium backup), system, boot, and battery stats. that should boot right up.
Did you wipe dalvik? You need to wipe data/cache/dalvik when switching ROMs.
If you don't know what a kernel is then I HIGHLY suggest you spend a little time reading up on all this because that is Android 101. You should have known what a kernel is before attempting to flash anything. A kernel is basically the interface between the software and hardware of your phone. It has all the drivers and instructions that tell your hardware what to do. They are flashed the same way ROMs are flashed and can affect performance dramatically. Different kernels perform differently on different EVOs so you need to find one that works well for your device. Sometimes the kernels that come packaged with ROMs don't work well on some EVOs and can cause booting and performance problems.
Mas wipey before flashy! Wipe all data, save for sd card, twice before flashing this rom. The savaged kernel that comes with the rom is just fine. Also, I would avoid titanium backup like the plague, especially if you are going to use MIUI.
Swyped from my CM7 EvO
Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin
You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'
dntesinfrno said:
You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'
Click to expand...
Click to collapse
Thanks man, will try your method and report back.
once you flashed your ROM(aokp) you need to reboot and let the phone fully boot into android... after that reboot to recovery and try flashing your Gapp + kernel
don't forget all the wiping and fixing permission for each steps
edit: wow this tab was open for a long time i guess. there was no other answer when i wrote this browsing through my opened tabs.
dingrn said:
Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin
Click to expand...
Click to collapse
Kevin my phone is exactly having the same problem did you come to a resolution
Especially on aosp roms it might help to flash the rom, let it boot once, then boot into recovery and flash kernel, wipe cache & dalvik, and fix permissions.
Also i've heard that some people will have alot of reboots before the kernel starts running smooth and stable. Or you could just have a bad phone that doesn't like to be tweaked. If i were you i'd take advantage of that warranty and try to get a replacement.
sorry for being a newbie....but what do you mean by fix permissions? =/
ohaai said:
sorry for being a newbie....but what do you mean by fix permissions? =/
Click to expand...
Click to collapse
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.
jefferson9 said:
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.
Click to expand...
Click to collapse
ive tried so many different methods of flashing kernels and all of them result in huge problems with crashes and random reboots all methods posted earlier are a gigantic fail. Im returning this refurbished phone for another refurbished and will report back
droidfta said:
Kevin my phone is exactly having the same problem did you come to a resolution
Click to expand...
Click to collapse
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.
dingrn said:
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.
Click to expand...
Click to collapse
hey had the same exact problem. Got a new phone under warranty cpu temps run lower and stable under current kt747 kernel I'll wait a few more days before underclocking but it's defiantly the phone you just got a weak cpu like I did
Are there any special steps required flashing JB AOKP or CM10 from 2.3.6 Juggernaut 4.1v. With Synergy kernel.
Flashing new radios?
Kernels?
I'm looking for a DD. GB has served me well since I flashed back in Dec 11 but I would like to get with the times and Jelly Bean seems like a good fit.
I have searched the forums for a few days looking for similar posts but none seem to fit my circumstances.
Boot cwm, factory wipe, wipe partition cache, wipe dalvik, wipe system, flash rom, will reboot twice, mount system, flash again, flash gapps, I also backed up my efs
Sent from my dr0id running Liquid Smooth r0m
Any particular version of cwm. touch vs non touch. Ive read that a certain version of cwm had issues 6ish I believe.
Now this is my second Android tablet but I am still not sure about everything. I have installed a few kernels on my New Nexus to just see if I like it or not. Now with installing Kernels over kernels is it safe to do so? If not then why? I do clear the Dalvik cache and the cache since that is what you should preferably do before anything in recovery.
No.
when you flash a custom kernel you're already overwriting the stock or previous kernel.
Wiping caches for flashing kernels is also a complete waste of time.
I am not following who is doing what right now kernel wise but the only thing you may have to is reflash your ROM if a kernel Dev decides to something different with the ram disk. If not a the ROM than a reset stock kernel
My phone has been running super laggy lately. Shiny ROM (CDMA) 4.4.2 Rooted. I tried clearing cache and davlik through CWM. Seemed to help for a few days. I usually only wipe cache partition and dalvik before flashing a ROM or something. Without that second step, what (if anything) does this accomplish? Any chance that this temporary lag reduction is a telltale for a particular problem I should know about.
Thanks!
Did you wipe data and system before flashing your rom?
Sent from my Galaxy Nexus using XDA Premium HD app
judson75 said:
My phone has been running super laggy lately. Shiny ROM (CDMA) 4.4.2 Rooted. I tried clearing cache and davlik through CWM. Seemed to help for a few days. I usually only wipe cache partition and dalvik before flashing a ROM or something. Without that second step, what (if anything) does this accomplish? Any chance that this temporary lag reduction is a telltale for a particular problem I should know about.
Thanks!
Click to expand...
Click to collapse
I've never found a convincing answer for your question. But from what I can tell a cache partition is probably meant to keep things the system uses closer at hand. Wiping it will force the system to create a new cache of things it needs and may possibly improve performance. However I believe the guys from google are good enough to keep a caching system that doesn't "age" (I mean it shouldn't slow down with time).
I believe the reason it should be wiped when you flash a new rom, is because a new system should create it's own cache...
Anyway, if I were you, I'd try flashing a new kernel. Personally I find Fancy Kernel to be the best. I've tried a few and they all let me down eventually. Fancy Kernel has helped in android 4.3 when my phone was getting extremely laggy with franco kernel. It was like buying a new phone.
I've recently used Dirty V that came with OmniMetal Rom and, although it was fast, it used too much battery. Once again Fancy Kernel helped with that issue and the phone is just as fast.