I know there are many threads about this, but nothing I've tried from those threads helped.
I had 08/28 and wanted to update to the new 10/18 build with custom kernel by quarx. I have a Defy with red lense.
Even with a full wipe (data, cache, dalvik) and only flashing either 10/18 or 10/18 with fixed 2ndboot.ko it get's stuck right after the Google-logo.
google-logo -> blue led -> logo goes away + red-led
then it's either stuck or goes in a bootloop after about 10sec
if I go to the bootloader the red led blinks for a second. don't know if this is helpful.
I know there are many people that suggest waiting for a while when there's the red led. This doesn't seem to help as I can't even get to the cyanogenmod logo and I've waited for about 15min without any success.
How long am I supposed to wait?
Someone suggested wiping /system, but I haven't found a way to do this within CWM-recovery.
Any pointers? Thanks in advance.
edit: I tried flashing 9/24 after a full-wipe and also got stuck in a bootloop. I might be missing something here...
have You tried to remove battery for several minutes?
it helps few users in CM10 thread. You may also check if "2nd-boot" is enabled in "boot" tab in 2nd-Init. Which governor do You use? for latest build it should be "Interactive" but You may try with others (boosted for example) and check if SIO mode (I/O Sheduler) is on in CPU Settings (value 1 says it's on).
You dont have to use fixed 2ndboot.ko with latest build. just flash CM10 (and update to 18.10 from 21.10) then google apps and You are done. You may also try installing latest build without any wipes (if You have nand backup).
*Please excuse my english
Related
I've seen a couple of threads that explain how I ended up where I am I think, but nothing so far on how to get out of it. So, any advice?
I updated to the 209 nightly the usual way (emmc install via clockwork recovery after wiping cache and dalvik) and it booted, started loading my home screen and clock widget, and then crashed completely and rebooted. Repeatedly.
I tried fixing permissions. I tried downgrading my version to 207, I tried upgrading to 210 and later 211. It either freezes or reboots.
After reading that the latest version of superuser needed to be installed before updating nightlies to avoid this type of problem and that it tied into overclocking, I was able to get into my nook by quickly going to the overclock settings and taking my max cpu down to 600 before it had a chance to lock and reboot. Yay right?
But the second I reboot, I have the same problem unless I race to undo the overclock again. Anything I can do to fix this? Or am I screwed and need to find an old backup or start from scratch again?
Hey there! I was updating my version of Paranoid Android and my kernel and it seemed fine at first but It yield some odd problems. I went into Clockworkmod recovery and Flashed my rom and kernel I then proceeded to wipe my cache and dalvik cache. I have done this many times before on many devices. I encountered a problem when I rebooted for the second time, I got the Android is updating apps display and I continued to get it every time I booted. The device would also randomly turn off when the screen dimmmed. I proceeded to set out and fix it. Here are the steps I took and the problems it caused.
Flashed stock rom-would not boot properly
Flash RESET kernel-I messed up and though this was a real kernel, my problems escalated from here.
Flashed stock rom and recovery.
Flashed reset kernel and then real kernel-Still had problems.
Flashed stock rom
My problems from all this accumulated somewhat and I can barely boot into fastboot. I get weird static screens and weird white noise sounds. It does not always let me boot into android and will get to the google logo 1 out of ten tries.
These is really unnerving and I have no clues whats what.
Note: I am using Faux123's kernels and his reset kernel.
Thanks a lot for any help!!!
Hi, I've searched my problem but came up only with "regular" reboot answers. Let me explain:
I was using the newest CM10 builds by Quarx as they were coming, and once in a while my phone rebooted/freezed. I was using nightlies so I was ok with that kinda of thing. But after flashing the last nightly (07/03), my phone was rebooting whenever I pushed him harder than opening the app drawer.
After wiping data, cache and everything else without any results, I've decided to flash an official SBF - Then the phone rebooted in the middle of the RSD flash process. I've started it again and it went ok... but now my phone is rebooting at the Moto logo, when I try to wipe the cache or factory reset through bootloader. I can't do anything with him.
Can someone give me any expectation? Something new to try? Or, hell, even a confirmation that my Defy is dead and there's nothing I can do?
SBF
Hi,
draw the battery,
wait a time,
put the battery inside,
start the steps to flash sbf,
after the flashing is finish make a factory reset in stock recovery,
install 2ndint ( i wrote something on the beginning like: After install 2ndinit restart, deactivat usb debug,and restart again),
Then install one of the beautiful CMs here.
cardosy said:
Hi, I've searched my problem but came up only with "regular" reboot answers. Let me explain:
I was using the newest CM10 builds by Quarx as they were coming, and once in a while my phone rebooted/freezed. I was using nightlies so I was ok with that kinda of thing. But after flashing the last nightly (07/03), my phone was rebooting whenever I pushed him harder than opening the app drawer.
After wiping data, cache and everything else without any results, I've decided to flash an official SBF - Then the phone rebooted in the middle of the RSD flash process. I've started it again and it went ok... but now my phone is rebooting at the Moto logo, when I try to wipe the cache or factory reset through bootloader. I can't do anything with him.
Can someone give me any expectation? Something new to try? Or, hell, even a confirmation that my Defy is dead and there's nothing I can do?
Click to expand...
Click to collapse
You just have to flash another rom using RSD lite, It will work.
Or just flash the official ROM which u had before installing the CM 10
Thanks for the attention, but I have tried flashing both his original SBF (Retail 2.3.7 from Brazil) and the Chinese one, both causing reboots when I try to wipe data/cache in recovery. If I let it turn on normally it reboots in the first steps (wifi and account configuration), so I can't even install 2ndinit or wipe data through the system. Any other ideas?
Hi Everyone,
I have installed the latest cm-10.1-20130709 build with 2.6.32 kernel,
Its been around 3rd - 4th time that my phone got stuck into bootloop over the last week,
And 2 of the times it happened is when my phone drained out the battery and later I charged the battery and the phone wont just start,
It gets stuck on the cyanogenmod bootscreen, all I can do is flash again,
Anyone knows any fix for this, or am I doing something wrong here ?
I always do a factory reset before and wipe cache/dalvik before and after flashing,.
I also tried just clearing the dalvik and cache and rebooting this way a screen shows up with text "Optimizing Apps" once that completes it says, "Starting Apps" but nothing happens, if i restart again it again gets stuck at cyanogenmod logo.
karan4 said:
Hi Everyone,
I have installed the latest cm-10.1-20130709 build with 2.6.32 kernel,
Its been around 3rd - 4th time that my phone got stuck into bootloop over the last week,
And 2 of the times it happened is when my phone drained out the battery and later I charged the battery and the phone wont just start,
It gets stuck on the cyanogenmod bootscreen, all I can do is flash again,
Anyone knows any fix for this, or am I doing something wrong here ?
I always do a factory reset before and wipe cache/dalvik before and after flashing,.
I also tried just clearing the dalvik and cache and rebooting this way a screen shows up with text "Optimizing Apps" once that completes it says, "Starting Apps" but nothing happens, if i restart again it again gets stuck at cyanogenmod logo.
Click to expand...
Click to collapse
Yes, that happens. I fixed that bootloop problem by taking data backups regularly. When bootloop occurs I just wipe data and restore the data from the backup. Bootloops have happened a lot of times using CM with AeroKernel. And you could have posted this in the support thread, or opened this thread in the Q&A section.
hotdog125 said:
Yes, that happens. I fixed that bootloop problem by taking data backups regularly. When bootloop occurs I just wipe data and restore the data from the backup. Bootloops have happened a lot of times using CM with AeroKernel. And you could have posted this in the support thread, or opened this thread in the Q&A section.
Click to expand...
Click to collapse
Thanks for the quick response,
Will use the Q&A section hence forth, for now I could not find an option to move this to Q&A section if any.
Hi all,
I've had CM11 installed and running on my Mi2s for a while and then my screen got cracked. Long story short, 2 month later i'm back to my Mi2s and CM11 does not start, it gets stuck on CM logo boot animation for a very long time (i think the longest i let it run was about 10 minutes).
Things i've tried with the same result:
DATA WIPE / FACTORY RESET, then re-install
DATA WIPE / FACTORY RESET, and installing other simialr ROMs: Omni, Gummy, Lungo
Installing same as above but on 2nd system (where I have WIUI)
Only similar ROM that did start was Mokee. WIUI also starts-up with no problem.
Any suggestions?
Thanks,
-arnon
Nobody?
Some more stuff i tried:
I've run the re-partition script hoping that the bootloop was due to not enough space, but no luck either.
I've also tried to format /system and then install, but no go.
Tried to install CM10.2.... nope
did you check that you have installed the correct rom for mi2s? you should download in ARIES in mokee. i have same problem with you before and I found that i downloaded a wrong rom from xiaomi forum.
cheers