FIXED
Okay, I tested only nAa v10 and v11 kernels in combination with miniCM v2.1.8/2.1.9(currently) and sometimes when I restart my phone, the phone goes off, then on, and Purple LED starts, and screen is black (only backlight works) then I have to hard restart it (battery in-out), is this a hardware or kernel problem, and how can I fix it .I didn't have this problem before/after flashing other kernel's.
NOT FIXED
#2 - Camera problem
I've also got one more problem, since I've bought my phone, and now I mean all combinations of rom's 2.1, 2.2, 2.3, stock or custom, or even kernels, I've got a problem when I long press camera button, phone just freezes and restarts, this happens in 3 of 5 times. Once more, sorry for offtopic. Thanx in advance.
If you look at nAa kernel thread you'll see that the reboot loops occurs with everybody and it has not way to "fix". Its a bug that you have to live with it.
Tnx anyway..
Does someone now about my camera problem?
Hi there,
Have been using ICS on my galaxy s for a couple of months. However this is the second time out of the blue it's decided not to boot for me.
The first time I thought it was because I dropped it and reinstalled gingerbread through Odin, then went back to ICS which was a very lengthy process.
I haven't installed anything, and now after just using the phone as per normal and it's decided to stop working? Any tricks I can do?
Basically it boots up, gets to the loading screen and just does that forever. I can boot into recovery but not sure what I should be doing next.
You could try reflashing your rom from recovery .
I think it's necessary to know which ICS-rom, for example slim ICS 2.8 needs to flash kernel first and then the rom ...
Sent from my GT-I9000 using XDA
Thanks imgibby123, if that is the last resort I may as well try it.
I've actually forgotton which one it is, I flashed ages ago and was very stable it just literally broke itself (a number of apps where crashing this mornign (reader, gmail etcc), so I held down the power button, turned it off as per normal, now the phone won't get passed the loading boot animation).
It was cynogen something, team platypus - I feel stupid I can't recall the details. But the ROM is still on there so I'll try reflashing from recovery.
Edit: It's ICS 4.0.3 RC3.1, so obviously still a RC but still! It worked flawlessly for months before
Thanks for the help.
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
At morning i take my phone assumed stand by and when i pushed the power button he doesn't wake up. I try several time to reboot it normally( doesn't work), in recovery (doesn't work again) then i tried in download and it works !
I flashed the last kernel Semaphore 1.2.6 and it reboot kindly. But in the yesterday evening i left it with 67% of battery and when i rebooted it after flashing the battery was empty.
The question is :
Why the phone wouldn't reboot without kernel reflash ???
And why it emptied the battery like that ???
What software / Rom are you using?
I also had a lot of problems with semaphore but version 1.2.5. I was on CM9 then and used midnight, it was faster and less battery consuming.
I suggest to flash another kernel, seems kernel related. Maybe smart to use a kernel cleaning script before flashing another kernel.
I was on CM9 build 2012/05/07 with the semaphore kernel.
I've flashed CM 9.1 rom 2 weeks ago. Everything was perfect (well, ok camera app was a bit laggy). I installed it through CWM, like wiki says.
2 days ago, I was using phone as Navigation, and battery depleted to 0 (phone switched off). When I plugged it into a charger, battery charging animation was displayed, then phone switched off and so on (loop). Same situation is when I power on. CM logo endless loop.
Recovery doesn't start, download mode is working tho.
I checked different battery, same thing.
Is it software related problem ? Should I just flash phone again via ODIN or Heimdall?
I had something similar like this a few months ago because my nephew was pressing random buttons. I did indeed just reflash the phone again. Lucky for me I had a backup of my data so that fixed most of my problems.
Hope you figure it out,
Currently, I've flashed hardcore Kernel (CM wiki page) to flash CM9.1 rom.... it gives me Status 7 error (get.prop("ro.product.device")). Same with CM 10 Nightly.
Flashing Slim ICS gives me Status 0 error.
What should I do?
Hey just flash stock GB firmware via Odin then u r good to go...
Do post results
If my post helped, don't mind hitting THANKS
Yes it helped. Thanks.
Strange tho, stock 2.3.6 feels faster than CM9.1