Hey folks,
being stuck in bootloops is one of the most annoying things for us powerusers.
Therefore I want to investigate a little bit deeper into this topic.
The normal procedure of "solving" the bootloops for me was flashing a base Gingerbread ROM by Ficeto (Mostly JVT) via ODIN, disabling Lagfix, entering CWM & flashing ICS again.
But one time (about 2 weeks ago) I had no time to go through this process, so I took the battery out of the phone (to abord the bootprocess & shut the phone down), placed it in again & putted the phone back in it's pocket.
About one hour later when I looked at it by accident (wanted to check the clock & forgot that it was bootlooping) the phone was fully booted & back to normal.
so the last 4 times my GT-i9000 (running nightlys of CM9) got stuck on the Bootscreen coming again & again, I took the battery out, placed it in again & let it bootloop for a while & after about 20 minutes baaam my SGS was properly booted?!
So my question/request is for you if you are stuck in bootloops:
[highlight]Please try the following:
1. Take the battery out & place it in again
2. Start the phone again
3. wait, wait, wait & be patient
4. Tell me if the problem solved itself or if after more than 2 hours of bootlooping nothing happened [/highlight]
if it didn't please tell me how long you've waited, what caused the looping & which nightly etc you where running!
just for clarification: with bootloops i mean being stuck on the Samsung Galaxy S / Cyanogenmod Screen where it is written in plain text which appears before you can enter recovery or the normal bootanimation appears. When my phone was/is bootlooping I also have no chance to enter Recovery. & I also know that it sounds strange that BL should solve themselves, but please try it!
[edit] I also read some time ago that there where other people with the same experience, this is why I opened a thread & I'm sure this is not a thing related to only my phone
I experienced something similar , also with CM9 . Phone working very hard , so i restarted it , but after the Galaxy S GT i9000 screen , the CM9 blue boot loaded for about 10 minutes and nothing , so I decided to enter in recovery ( I removed the battery , waited a minute , inserted it in the phone , and the recovery didn't work . Waited 10 minutes , and after that the recovery worked , and I reflashed CM9 , because it was the only rom I had in the internal SD card .
About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey
Thomas. said:
About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey
Click to expand...
Click to collapse
It would be nice if you could tell exactly what you did, if more people would do that we might be able to figure out why this thing happens to you and why it doesn't happen to me.
when i flash:
*phone not connected to pc or charger
*running stock kernel
*16 gb micro sdcard mounted
*all sorts of battery percentage, from 10 to 100 percent
*reboot recovery by terminal command "reboot recovery"
*format /cache
*flash the build from /mnt/sdcard/download
*flash gapps from same location
*run a script that wipes dalvic, removes several sounds and unwanted apps and fixes permission
*format /cache again
*reboot
I know this is a pretty weird procedure and it's in no way an advice to anyone, it is just an example of giving details that might lead to a common factor for bootloops.
Taptalked u see
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Thanks for your post!
What caused the bootloops?
fipsib said:
Thanks for your post!
What caused the bootloops?
Click to expand...
Click to collapse
1st time I got bootlooploop was [15/Jan/2012] I was trying to boot into Recovery via power button so I could upgrade from Build 12 to Build 13.
2nd time [2/April/2012]I was on AOKP B28 & I had booted into Recovery to wipe cache & dalvik & after successfully wiping, the bootloop came when I hit the 'Reboot' option to start the phone.
(AGAINST better judgement - since first bll I had avoided wiping cache & dalvik)
jep. I also had bootloop problems by wiping cache and dalvik cache. I was on SlimICS flashed midnight kernel. Everything was working just right but CPU scaling had some bugs for me so i removed init.d scripts went into recovery wiped cache and dalvik cache...and boom....bootloop :/. Now I'm back on CM7 because this is a rather annoying problem....
BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Can you link me CM7 kernel for Odin? thanks
farid993 said:
Can you link me CM7 kernel for Odin? thanks
Click to expand...
Click to collapse
Yep, here it is,
View attachment 1012442
This worked for me both times
[remember to leave UNCHECKED
Ensure Reboot, Repart, F-Reset]
Then boot into Recovery and restore Nandroid - no need to be flashing gingerbread.
Ever since the first nightly, I have been plagued by bootloops. Usually formatting /system, /data and /cache helped. But not this time. I tried to install the 19/4 nightly, and had gotten into bootloops. Yes, I have used custom kernels before.
However, even clearing init.d, clearing NSTools, flashing from FixRecovery, the cm7 kernel, even flashing with Heimdall (flashing stock kernel and custom kernel) could not get me out of the loop. Note: I tried the method as described in the OP.
What I finally did was format everything, excluding ext-sd. Format internal SD as well, after backing up some files. And BAM! That was it! Something on the SD corrupted the install. No bootloops, can even install custom kernel, no problem.
So, that may be a tip for people not able to get out of the bootloop, or experiencing constant bootloops.
Hey it's under Devs investigation now:
http://forum.xda-developers.com/showthread.php?t=1627689
My galaxy with CM9 started to bootloop yesterday, no way to enter recovery
I'll make you know in a couple of hours if something change leaving it on ..
If nothing change, is there a place where I can find CM9 kernel to flash with odin ?
thanks
Read Bejda's post, one post above yours.
Taptalked u see
wooops didnt see the second page of the thread
anyway leaving it there to bootloop didnt solve the problem
flashing semaphore kernel seems yes
Im having a problem with cm 10.1 stable rom 10.1.2. Ever since i flashed it, my phone has been rebooting constantly whenever I press the power button. Ive tried flashing nightlies 20130714 - 20130719 after this and nothing seems to get rid of that problem. Does anyone know a way to fix it without a full wipe?
Hi, in the past couple of days I have tried two 4.4.2 roms (cm 11 and ose)...
On both roms I get the black screen of dead when I woke up in the morning... (when this happens i have to press the volume down and power button to restart the phone)
Is this a common thing on 4.4 or this happens on all the custom roms? (I'm asking because on the rom thread this wasn't listed on the bugs)
vite0150 said:
Hi, in the past couple of days I have tried two 4.4.2 roms (cm 11 and ose)...
On both roms I get the black screen of dead when I woke up in the morning... (when this happens i have to press the volume down and power button to restart the phone)
Is this a common thing on 4.4 or this happens on all the custom roms? (I'm asking because on the rom thread this wasn't listed on the bugs)
Click to expand...
Click to collapse
This is not common at least not for CM11.
I've been running CM11 nightlies since they started to roll out, currently running 20/12 without issues.
I would recommend going to recovery, back up, and erase system, data, cache and dalvik, then flashing CM11 nightly to start clean.
I've been running CM11 and Validus13 ROMs since they became available and never had this issue.
I used the cm11 12\26 (latest i think).. And did a full wipe (even the internal sd got wiped)...
Something i didn't do was wipe cache and dalvik after flashing the rom, does it is required
I don't recall wiping Cache, Dalvik, or Data after installing 4.4 ROMs.
vite0150 said:
I used the cm11 12\26 (latest i think).. And did a full wipe (even the internal sd got wiped)...
Something i didn't do was wipe cache and dalvik after flashing the rom, does it is required
Click to expand...
Click to collapse
You should totally clean cache and dalvik when flashing new roms (CM usually does this by itself anyways). Make sure you're cleaning these, won't hurt at all anyways.
Ok, make a factory reset after flashing... Also i see in some roms that i gotta mount system and other things, i never did that (i didn't saw that in the instructions of the two roms that I've tried...)
Also I used for this couple of days the stock rom just to check that it wasn't a hardware problem... worked flawless...
Right now i'll try valadus... I'll let you know how it goes
Update: valadus gave me a lot of errors... Something like it couldn't write on storage/cwm... And when it was aborted it says that cache can't be mounted... So i ended up installing cm11 (the same that i flashed before)
You're running the latest CWM or Philz recovery?
Philz
It's strange because I'm running the latest CWM and I can install the latest Validus13, Cyanfox, CM11, and Probam without a problem.
Flashed probam last night, and it survived the night! Only thing I changed from before was wiping again after flashing...
Thanks for ur help
Update:
In the morning i connected the phone to the charger, and now i went to see if it was fully charged and surprise!!! It happened again!
Maybe is the charger cause I'm using a generic, but why it doesn't happen on stock rom?
At this moment i will just leave it stock and put it for sale, don't want to keep dealing with this...
Hi guys,
A couple days ago i noticed that on stock (att) rom i wasn't getting bsod but i do was getting reboots when charging the phone (i don't know how i didn't noticed it before)...
So maybe someone can tell what are the specs of the original power brick (amps, input, output) to find a similar one and see if that can solve the problem
Edit:
Nvm i found a samsung charger... Now everything is working flawless on OSE rom
Hi. I have very strange problem wit my phone. It gets random reboots all the time.
I use fxp latest nightlys, but i've tried cm and even got back to stock, and it still happens. I thought it was cause of oc or smth with system files. And the thing is it does not have a regular patern.
I wipe cache/dalvik or flash rom, phone boots and it is ok , next when I use it it reboots very often or even worse sometimes i can't get it working again coz it reboots, and when android is opening it reboots right away and then i have to flash rom again or clear dalvik.
Anyone can help ? Do I have to use warranty?
Rufus_0077 said:
Hi. I have very strange problem wit my phone. It gets random reboots all the time.
I use fxp latest nightlys, but i've tried cm and even got back to stock, and it still happens. I thought it was cause of oc or smth with system files. And the thing is it does not have a regular patern.
I wipe cache/dalvik or flash rom, phone boots and it is ok , next when I use it it reboots very often or even worse sometimes i can't get it working again coz it reboots, and when android is opening it reboots right away and then i have to flash rom again or clear dalvik.
Anyone can help ? Do I have to use warranty?
Click to expand...
Click to collapse
I recommend a complete fall-back to stock; which means flash everything (baseband, FOTAkernel, kernel etc) you can in Flashtool. If problem still persists, it really might be related to hardware, though this is only my guess.
Galaxy Note GT-N7000, I was on CM 11 and everything was working fine. I made my mind to try out Omni ROM. Installed TWRP and Omni ROM. Since then WiFi is not turning ON. When tried to turn ON from settings, the button moves to ON state stays grey for few seconds and moves back to Off. Now even after installing stock ROM or CM 11, the WiFi is not turning ON and same behavior observed.
Tried the following:
Factory reset.
Installed stock JB ROM.
Again installed CM 11 by doing wiping /data, /system, /cache.
Installed Custom Kernel
Based on the suggestions at some posts, opened up the phone to check any dust or hardware related issues, but nothing.
It doesn't seems to be a hardware issue, as WiFi turns ON occasionally, especially when a new ROM is installed but after a while stops working.
PS: ADB Debug log says "Unable to load driver."
Requesting help from experts on fixing this issue.