Develop Bugs

MIUI - stuck on bootloader

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

Evo stuck on boot animation screen - CM7

I just flashed a fresh cm7 rc4, along with gapps, and zendroid kernel (avs i think i'm not sure which one).
Things were working great. I was using the phone, had just installed widget locker, and then tried to plug my phone into the computer.
Thats when the trouble started. For some reason, usb debugging worked, even the wireless tether worked, but I could not get the sd card to be on the computer, the option just never came up.
To fix the problem, I tried resetting the phone, but when I did so the phone became stufk on the cm7 boot animation for a few hours. What do I do?
I would just do a fresh install, but this is actually the third time that I have gotten stuck on the bootloading screen with cm7, so I just need to find a solution. Please help.
-AJ

Really need some help with this, guys...need my phone back

You're not alone. I installed GApps along with CM7. Stuck in Boot animation. My wife is pissed.

You posted in the wrong section. I will transfer this over to the EVO Q&A area.
I am assuming that you have your EVO rooted. If you are stuck in a bootloop, simply pull your battery, put it back in and press the power button while holding Vol Down. This will make you go into bootloader. From there, simply go into recovery, wipe everything, and reflash the rom. I have done CM7 and gapps and have no issue.

egzthunder1 said:
You posted in the wrong section. I will transfer this over to the EVO Q&A area.
I am assuming that you have your EVO rooted. If you are stuck in a bootloop, simply pull your battery, put it back in and press the power button while holding Vol Down. This will make you go into bootloader. From there, simply go into recovery, wipe everything, and reflash the rom. I have done CM7 and gapps and have no issue.
Click to expand...
Click to collapse
I did that, many times. One time, it just worked. Didn't do anything different as far as I know, but kind of makes me unsure about future flashes etc.

Pull your battery out, wipe data, cache, and dalvik cache in recovery. Flash ONLY CM7 and the google apps. I think the kernel might be the problem for the bootloop.

harryprk2x said:
Pull your battery out, wipe data, cache, and dalvik cache in recovery. Flash ONLY CM7 and the google apps. I think the kernel might be the problem for the bootloop.
Click to expand...
Click to collapse
I never wipe any of those things seperately, I just use calkulin's format all. That couldn't be the source of any problems right?? I mean, I always believed that that was the best way.

Thanks. I ended up doing that. All is better now.
Sent from my rooted Thunderbolt with VirusROM AirborneTB. Xda premium

My problem was installing both at the same time.
Sent from my rooted Thunderbolt with VirusROM AirborneTB. Xda premium

thenimboo said:
I never wipe any of those things seperately, I just use calkulin's format all. That couldn't be the source of any problems right?? I mean, I always believed that that was the best way.
Click to expand...
Click to collapse
I've used Caulkin's format all twice, and both times, I got stuck in the white screen boot loop and had to reflash Amon Ra, just to get back to recovery and flash one of my nandroids.
Wiping everything in recovery works perfectly fine for me.

I use Calk's format all at least a few times a week, sometimes a couple times a day. Always works fine.

Did you wipe?
Did you wipe the data/cache from the handset? if not do so through clockwork

Few Questions

Ok rooted my DHD about week ago with AAHK have now try 3 diffrence roms. the newest rom (icecold sandwish) is doing so weird things once in allpications settings phone was showing only like every 3th letter or so and some where was only some mess reboot fixed this. also have got some random crushes but had some with original 2.3.5. Also had some weird battery problems used battery to 0% loaded up to 100% and when started phone it says was still 0% and switching off stucked on screen replug battery fixed this.
batween on 1 and 2 rom didint clear cache did only factory reset between 2-3 (current) did full clear so wondering is my phone now bit mess cos didint do the cache and dalvik cache between 1 and 2 or is it normal to do some little bugs?
just wondering as i have now custom rom can i have back my original android what was in before root if it havent been backuped?
and last when you press power and - volum at start screen is hboot recovery and factory reset what will it do actually the same as in recovery or will it reset the devise to same state as it was when i 1st got it ?
Ty All!

Do not do the factory reset - it will only make things really bad.
When in recovery, before flashing a rom:
Wipe data/factory reset
Wipe dalvik
Format all partitions (except sd card)
That will make sure a good install of whatever rom you choose.
All ics roms are buggy. The devs are still working on them.
Suggestion: flash a gb rom.
You should be able to find a stock rooted rom if thats what you want.
Sent from a dream.

One you need to full wipe and then flash rom. On ice cold the messed up letters no need to reboot its the launcher so go into launcher setting and restart launcher should fix issue. If your on ice cold see if you have the cfs kernel or bfs kernel cfs is known to cause reboots. As for hboot you can enter recovery that way do not wipe factoey reset there without a rom on sd to flash. It erases everything and if you don't have a rom to flash after your will regret it and be back here asking why phone won't turn on.
Welcome and enjoy the reading and learning.
Sent from my Desire HD using xda premium

[HELP] My GS3 hates customs kernels

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

Quick! Help!

Flashed Liquid Nitro from CM 10.0.0....wiped cache, wiped devick.....phone stuck on "rethink possible" how do i get into recovery?
...and won't be doing that again. WTF? at least i know how to boot into recovery from my phone.

mgofpickens said:
Flashed Liquid Nitro from CM 10.0.0....wiped cache, wiped devick.....phone stuck on "rethink possible" how do i get into recovery?
...and won't be doing that again. WTF? at least i know how to boot into recovery from my phone.
Click to expand...
Click to collapse
When you switch from CM9 (ICS) to CM10 you should do a full wipe. Really, when you flash any ROM you should do a full wipe; but especially if you're jumping from JB to ICS or vice versa. And I'm assuming you got back into recovery, but if not: turn phone off. Hold volume down + power until the factory reset screen comes on. Press power button twice and instead of performing a factory reset, you should be taken into CWM recovery.

Thank YOU!
lordcheeto03 said:
When you switch from CM9 (ICS) to CM10 you should do a full wipe. Really, when you flash any ROM you should do a full wipe; but especially if you're jumping from JB to ICS or vice versa. And I'm assuming you got back into recovery, but if not: turn phone off. Hold volume down + power until the factory reset screen comes on. Press power button twice and instead of performing a factory reset, you should be taken into CWM recovery.
Click to expand...
Click to collapse
i would like to try this out...so i do a complete wipe? and i didn't realize liquid nitro was ics. i really like the funtion of jb, but the battery sucks real bad. i read through, what i thought was detailed. anyway, when i make a complete change in the rom, i need to do a wipe?

wait...
mgofpickens said:
i would like to try this out...so i do a complete wipe? and i didn't realize liquid nitro was ics. i really like the funtion of jb, but the battery sucks real bad. i read through, what i thought was detailed. anyway, when i make a complete change in the rom, i need to do a wipe?
Click to expand...
Click to collapse
a rom is replacing the /system partition, right? so why would i need to wipe? i went from cm 9 to cm 10 quite easily. i really don't understand. i mean, i thought i did. partition: system, data, recovery, boot. right?

mgofpickens said:
a rom is replacing the /system partition, right? so why would i need to wipe? i went from cm 9 to cm 10 quite easily. i really don't understand. i mean, i thought i did. partition: system, data, recovery, boot. right?
Click to expand...
Click to collapse
Yes, ROM replaces /system, but it doesn't format before the install. Kinda like if you install a version of Linux on top of a different version without formatting you'll still have some junk floating around from the previous install. I use TWRP and before each new flash I wipe /system, /data, and /cache.... dalvik, from what I've noticed seems to not really be needed to wipe: every time I tried it it tells me it doesn't exist. I think in CWM there's an option to do full wipe, not sure; but I'd use that if it is.
Liquid Nitro is stock/rooted/debloated ICS with a few other goodies thrown in, then you have CM9 (and it's variants) which are ICS based. As far as jellybean goes, the P93x only has CM10 and it's numerous variants. You can, without too much hassle, perform a dirty flash over CM10 and it's variants, but you're just asking for bootloops and whatnot trying a dirty flash from ICS to JB based. Again, I'm not advocating to dirty flash unless you're just updating from a previous build of the same ROM, but it's less likely to cause problems when you at least stay within the same android version.

lordcheeto03 said:
Yes, ROM replaces /system, but it doesn't format before the install.
Click to expand...
Click to collapse
It does format actually. Really the only reason to format system manually is if you want to prevent it from backing up and restoring your Gapps. Doesn't hurt anything though.

drumist said:
It does format actually. Really the only reason to format system manually is if you want to prevent it from backing up and restoring your Gapps. Doesn't hurt anything though.
Click to expand...
Click to collapse
I stand corrected. Thank you.