Hi there, I got a really disgusting problem with my beloved Defy.
I'm using SlimKat 4.4.2 since several months (without problems) but today I got a strange behaviour.
I was using the timer of the clock app and after that all apps crashed.
I have used the timer often before...
When every app crashed I tried to reboot, but I'm stuck at SlimKat logo.
Entering reovery menu is no problem but it won't help. I tried to clear dalvic cache and normal cache
and even installed SlimKat and gapps again but it won't boot. Always stuck at SlimKat logo.
Big question: why? It was working always without problems and now that?
Please help. Thanks in advance!
Related
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!!!
Hey I installed Liquidsmooth 2.7 yesterday and it kept rebooting. I tried flashing back to CM 10.1 RC5 because it wasn't doing that before. Again it kept rebooting. It reboots like every 30 secs. It's always a quick reboot as well. I flashed back to stock and locked the bootloader but nothing seems to fix it. Does anyone know how to fix this?
yes , install sabermod rom and trinity kernel . enjoy
Sent from my Nexus 10 using xda app-developers app
amjc14 said:
Hey I installed Liquidsmooth 2.7 yesterday and it kept rebooting. I tried flashing back to CM 10.1 RC5 because it wasn't doing that before. Again it kept rebooting. It reboots like every 30 secs. It's always a quick reboot as well. I flashed back to stock and locked the bootloader but nothing seems to fix it. Does anyone know how to fix this?
Click to expand...
Click to collapse
try the following:
wipe all caches, data & system
install ROM (i recommend SentinelROM 4.8 - it's very fast & stable)
install gapps (if needed)
wipe aigain all caches
reboot system
I tried that, I restored stock and locked the boot loader, I tried to root it again and nothing worked. I contacted Google and I'm getting it replaced. Thanks for the advice though
Sent from my Nexus 4 using Tapatalk 4 Beta
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
Hey guys,
so I recently flashed the Ressurection Remix ROM v5.6.0 and all was working fine until today the touch screen decided to stop working. I couldn't unlock the phone so I tried rebooting it and now it's stuck on the boot logo screen. I can access TWRP and the touch screen works fine so I think the ROM has an issue of some kind? Just wondering if anybody else has experienced a similar issue with this ROM at all? The phone is SM-G900I and I flashed the kltedv ROM onto it. As I said it worked fine for a couple of days then all of a sudden it decides to stop working
Any and all help is appreciated
Did you do a clean flash? If not, try a clean flash or installing again. Also, try clearing your cache and dalvik
Well I did a factory restore using TWRP before flashing the rom on and then cleared Cache and Davlik after installing (as per developer recommendation) and it was fine for a couple of days which is what's stumping me! :S