Hi at all,
I've installed cm-9.0.0 one month ago. All things were working fine and stable. No Problems. Yesterday my SGS rebooted automatically. After the reboot I couldn't determine any unusual behaviour. This morning my SGS reboots automatically again but now it's freezing by the second bootlogo (first bootlogo without cyanogen logo, second bootlogo with cyanogen logo). I also can't go into the wipe / CWM menu. Download menu works. Any ideas what's happened?
Best regards
Olli
Hi,
I also had an issue with v9.0.0 : I lost recovery when my phone was in my pocket !
By the way, latest CM9 build for SGS is 9.1.0. I would recommend you to give it a try as I think this build includes bug fixes. When I used this release, I did notice no bug.
Otherwise you could try the last monthly release called M2 but it is CM10, so JellyBean and not ICS.
http://download.cyanogenmod.com/?device=galaxysmtd
I had such a problem back in days, just go and flash ICS333 and datadata fix file and you will have a vary stable system, try to remove battery than try to enter CWR, if you couldn't, I hope more experience member than me can help
Sent from my GT-I9000 using xda app-developers app
i had this problem too. The biggest prob is the broken cwm. I couldnt reach and last way was always Odin.
Related
Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Beorn1 said:
Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Click to expand...
Click to collapse
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
This fixed the same issue for me.
Wiped everything and flashed CM9. Works great (but battery drain is incredible!!!)
Solved!
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
Thanks, I did this, and now I was able to boot again with Gueste 3.1 (I'd rather wait for a bit more stable and mature version of CM9).
Actually, I did this thing twice, and it still didn't help, and in the third time I tried to make a logcat (I'm rather new to this logcat thing), and while trying to boot and make a logcat at the same time it suddenly started workind
I just hope that it will stay good now, and that I won't have this problem again in future flashes...
Thanks!
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.
Hi,
Im using Cm7.2.0 RC1.
Every night during charge my OB reboots into the recovery mode. I didn't experience this problem with Zeus 4.02b or stock rom (shipped 2.2.0 and updated V20o).
It's a PITA, cause I use my phone as my alarm clock
Is there something like an error log? Does anybody already know a solution?
Tried google and this forum, no results
I had the same problem in an entirely different device but I know of some ways to possibly fix it. Check to see if you have the cyanogenmod tenkian kernel. Do this by opening up settings and scrolling down to the very bottom and hitting about phone. My other device randomly rebooted due to a problem with a kernel. What version of clockwork mod recovery do you have? Open up rom manager and update to the latest possible recovery by hitting "flash clockwork mod" at the top. If that doesn't fix it, boot into recovery and clear/wipe data (pain but usually fixes it) clear cache partition, and clear dalvik cache, then bootup and see. You can make a "logcat" file which gives details to devs about exactly what was happening when your device went wonky. I hope this helps
Sent from my LG-P970 using XDA, or something
vagubunt said:
Hi,
Im using Cm7.2.0 RC1.
Every night during charge my OB reboots into the recovery mode. I didn't experience this problem with Zeus 4.02b or stock rom (shipped 2.2.0 and updated V20o).
It's a PITA, cause I use my phone as my alarm clock
Is there something like an error log? Does anybody already know a solution?
Tried google and this forum, no results
Click to expand...
Click to collapse
reflash the file baby or the cm7 RC1 file babe
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
I installed cyanogenmod 10.2 nightly 20130824 accidentally, thinking that it was another 10.1 update (which by then was pretty stable), and realized that i made a big mistake: tonnes of bugs (focal, screen elements blacking out, play store not working).
But when i tried to boot into recovery to restore my clockworkmod full back up (which i do almost everytime i update CM), the "Galaxy Note N7000" boot screen comes up, and then a black screen. I can still boot back into the normal boot, but the tonnes of bugs just annoys me sooo much.
(i've tried to boot into recovery many times, to no avail)
Then, i tried to update it. I figured a newer version should at least be slightly more stable.
But updating cyanogenmod requires the phone to boot into recovery.
soooo fk.
Also when i try to boot into download mode, a screen showing an android icon and Downloading Do Not Turn Off Target pops out.
So after some google searches which didnt help, i came here to xda devs hoping you smart people could help me with this predicament.
Please tell me, has anyone experienced this problem on any phone and do you have any idea what to do?
It's a known bug with cm10.2. Follow this thread, just install phillz kernel to give you recovery, then you can flash cm10.1.
http://forum.xda-developers.com/showthread.php?p=45041491
Sent from my GT-N7000 using XDA Premium 4 mobile app