Hi,
I was running cm9 successfully for about 2 months, I would get occasions where the screen would go black and unresponsive. I had to pull the battery and reboot and it would be fine. I thought this was fairly normal for a cm9 nightly as it didn't happen very often. A few days ago this happened to me, and upon pulling the battery and rebooting, the phone just went into bootloops. I could not access cwm, so had to flash JW5 via odin, rooted it and attempted to flash cm9 again, this too results in bootloops.
Can anybody help? Being stuck with Samsung firmware is such a regression after having used cm9.
I've tried the same 2.3.6 firmware i installed with an older cm9 nightly which i know worked when i flashed it but get the same results.
Help me please.
Rob.
If you lose recovery you can usually get it back by flashing the semaphore kernel .tar in Odin
First Download and flash cm7 (Download From their official site). Thema cm9 : 100% works 4 me. Or look in The nighty thread and read The instructions
Gesendet von meinem GT-I9000 mit Tapatalk 2
slaphead20 said:
If you lose recovery you can usually get it back by flashing the semaphore kernel .tar in Odin
Click to expand...
Click to collapse
lol wish I knew that before, must have flashed Samsung 2.3.6 fully a good 10 times. Got it working now though, had to flash cm9 3 times in total; first time it flashes really quick and reboots into cwm with errors, then i had to flash it again twice and it installed properly. (I was only flashing it again once after the initial error).
I had this problem too. First, you don't need to remove battery, holding the Power-button will restart your phone even if it hangs. I never got the data back after the boot-loops. I recommend using titanium backup, I have it set to backup all my data every second night, so I can keep almost all my application data even if the nightly was bad.
Related
I try to install but don't work... after that i flash it, the phone lock to logo screen "google" and i can't go to CWM i must use odin to reflash. If install rc3.1 it's all ok.
Where is the problem?
Thanks.
Did you try looking at the help page on the thread in the development section? It's right before the post is finished, there will be a link that will lead you there.
Hope that helps, if not I can try to just copy and paste the instructions hahaha
scheccia said:
I try to install but don't work... after that i flash it, the phone lock to logo screen "google" and i can't go to CWM i must use odin to reflash. If install rc3.1 it's all ok.
Where is the problem?
Thanks.
Click to expand...
Click to collapse
Did you do a full wipe before flashing RC4.1?
kabracity said:
Did you do a full wipe before flashing RC4.1?
Click to expand...
Click to collapse
yes... i try to flash a miui rom first also.
I try to do a full wipe... i try to install a original rom... but when i flash rc4.1 the phone stuck to logo.
Ensure you have backed up your EFS directory; if you don't know how ask.
To be honest, there appears to be some inconsistency in the reliability of the 4.1 RC release (across handsets); I have had persistent WIFI issues and then when the wifi fix was released I found the phone to just be a little laggy.
My advice if RC 3.1 works well for you is to keep it on there for now and wait for the next release they make.
However, if you still wish to flash it, there is no 100% working way - just keep factory reset, dalvik wipe, cache wipe, reset until it starts working! That's what I did as the original instructions did not work for me.
torrentship said:
Ensure you have backed up your EFS directory; if you don't know how ask.
To be honest, there appears to be some inconsistency in the reliability of the 4.1 RC release (across handsets); I have had persistent WIFI issues and then when the wifi fix was released I found the phone to just be a little laggy.
My advice if RC 3.1 works well for you is to keep it on there for now and wait for the next release they make.
However, if you still wish to flash it, there is no 100% working way - just keep factory reset, dalvik wipe, cache wipe, reset until it starts working! That's what I did as the original instructions did not work for me.
Click to expand...
Click to collapse
I agree with you... RC3 was fine for me... fast and all worked... RC4 has some wifi issues... It switch on/off and doesnt stop till i reboot the phone... im thinking about to downgrade to RC3.1 and wait till the next release...
Sent from my GT-I9000 using XDA App
torrentship said:
However, if you still wish to flash it, there is no 100% working way - just keep factory reset, dalvik wipe, cache wipe, reset until it starts working! That's what I did as the original instructions did not work for me.
Click to expand...
Click to collapse
Yes i try it(no backup efs)
If i flash 2 time the rom the phone stuck it and i can't enter in cmw
.. is the only rom that give me this problem... bha...
Hello, have you tried to download the rom again? Maybe it's a bad download..
That's odd, for me i got stats 7 but was because i was flashing the I9000B version and my phone was with the CWM for I9000. Try using odin and flash a sotck rom, after that install the CWM and then the RC4.1.
If anyone want to know the procedure that i do to install the RC4.1 is this:
Starting for CM7 --> flash the ARO 2.3.3 rom to re-write the bootloader (check this option in odin) --> flash the ZTO 2.2 rom to re-partition in original size partitions --> flash the 2.2.1 ARO because it's a nice rom and don't have all the trash that is present in ZTO version --> through kies flahs the ARO 2.3.3 original.
After that the procedure to install the RC4.1 is the standard: flash CWM then install the ROM.
I had problems going from 3.1 to 4.1. Same issue as OP.
Process I followed:
-Flashed CWM through heimdall
-Flashed devil kernel
-Flashed CM7 (had to do this twice in a row)
-Flashed ICSSGS 3.1
-Flashed 4.1 but before I rebooted my phone, I flashed Devil one last time.
Since then, phone has been rocking along just fine!
Sent from my GT-I9000 using Tapatalk
Bena1988 said:
Hello, have you tried to download the rom again? Maybe it's a bad download..
Click to expand...
Click to collapse
Yes... three times.
I'm having the same problem here.
I tried the first point on the Common Issues page but I'm still not able to go into CWM!
I flashed the Speemod Kernel using heimdll but I can't go back to CM7. I'm getting a Stat 7 error.
Also tried the Devils kernel (Devil_1.0_CFS) with no help ....
Any ideas?
Just wondering...
MaesterB said:
I had problems going from 3.1 to 4.1. Same issue as OP.
Process I followed:
-Flashed CWM through heimdall
-Flashed devil kernel
-Flashed CM7 (had to do this twice in a row)
-Flashed ICSSGS 3.1
-Flashed 4.1 but before I rebooted my phone, I flashed Devil one last time.
Since then, phone has been rocking along just fine!
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
why on earth did you flash the CM7 as a part of the process? I always have just downloaded an appropriate kernel (devil, stockplus etc..) + ICS ROM (latest was RC4.1), once I'd rooted my stock 2.3.6 ROM with CF-Root (takes only 5 minutes). ICSSGS' ROMs can be applied straight on top of any previous ROM, the only requirement is that you have root privileges + CWM installed. Flashing CM7 is often frustrating, at least for me. I personally see no point in flashing it before the ICS ROM. If you know better, pleasy enlighten me
Arvokm said:
why on earth did you flash the CM7 as a part of the process? I always have just downloaded an appropriate kernel (devil, stockplus etc..) + ICS ROM (latest was RC4.1), once I'd rooted my stock 2.3.6 ROM with CF-Root (takes only 5 minutes). ICSSGS' ROMs can be applied straight on top of any previous ROM, the only requirement is that you have root privileges + CWM installed. Flashing CM7 is often frustrating, at least for me. I personally see no point in flashing it before the ICS ROM. If you know better, pleasy enlighten me
Click to expand...
Click to collapse
Thats the way I do all went well...
Sent from my GT-I9000 using XDA App
I wanted to flash CyanogenMod 7.1 on my Samsung Galaxy S.
I flashed before a Froyo Bootloader (because I had Firmware 2.3.3) on it, copied the CM7.1 Rom on internal storage and tried to flash through Recovery.
While updating it shows me the install process till:
Checking state of BML/MTD
then it interruptes the install process and restarts the phone. But then it just shows me the Samsung logo and nothing happens (=freeze).
No chance to start the phone, altough I restart it several times.
Then I can flash again with Odin to the starting state again. The files for that I found here (german):
http://www.giga.de/smartphones/samsung-galaxy-s-i9000/tipps/samsung-galaxy-s-cyanogenmod-7-flashen/
EZodin
EZbase-CSC-XXJV1.tar.md5
EZbase-PDA-XWJS3.tar.md5
EZbase-PHONE-XXJVE.tar.md5
Ezbase.pit
How can I flash CM7.1 now..?
Sometimes the cm7 rom will need flashed twice....you should be able to flash from any gingerbread rom also as cm7 was updated a while back to allow this. Try again, and if the phone starts bootlooping-pull the battery, replace and get into recovery-then reflash rom.
Unfortunately i cant enter recovery after unsuccessful flash. I have to use odin and flash back to old froyo... then i tried to reflash again to cm7.1 but it was always the same.
Thx anyway for ur answer...!
Hmmmmm ;(
Gesendet von meinem HTC Desire mit Tapatalk
no ideas? it is urgent.. ;(
it's really strange. it happened to me and I solved like this:
I removed the battery
volume up key + power button + home button
in recovery,I wipe everything and reflash of the rom
If recovery doesn't work, you need to reflash a stock rom, and a kernel with root and CWM
puuhh, at least another one who had this issue...
ok i understood that if i cant flash to cm7.1 then i have to chosse another rom, maybe just a stock rom.
but can anybody recommend a custom rom which will work? it is just a file system problem here, isnt it?
Done it!
Trying to flash the stable Rom didnt work.
Then i tried the nightly (181) and it took a while then it restarted. but when it was starting for the first time i got a loop while booting.
but this time i could enter the recovery (after stable installation it wasnt possible anymore) and i could reflash it (nightly again). and this time it worked!!! yeah finally after over 8 hours of work....
i hope i could help somebody who has got same issues
Glad you got it -and cm9 is now an easy upgrade from the latest nightly
Hello everyone.
For a few days I've been having an annoying issue with my SGS.
For months I've been flashing many ROMs, especially ICS ones, and I never had any problems when I followed the instructions.
But since last tuesday, I regularly get bootloops with no reason. An hour ago, I flashed Gummy 1.2 on my phone, set everything up, configured my account and everything else. Then, I put one of the latest builds on my phone, tried to reboot to recovery as usual, but it began to bootloop. I didn't flash anything new for it to happen, and I can't seem to get why it does it.
I can't access to Recovery (freezes at kernel startup screen), only to Download mode. This means I have to reflash GB with Odin everytime it happens, then CM9 back, and then a custom ICS.
It never happened before tuesday, and it seems recurrent now, no matter what ROM, Kernel or Modem I use.
I've had my phone for almost two years, is it getting used up?
I'd appreciate if somebody could help me!
Have you tried a complete wipe including format internal sd? Then flash fresh gingerbread base.
Slim 4.2_Semaphore 1.2.5s_Cobalt Theme
If you lose recovery flashing the Odin semaphore kernel usually does the trick
vanisleryan said:
Have you tried a complete wipe including format internal sd? Then flash fresh gingerbread base.
Click to expand...
Click to collapse
Not really sure it would work..
slaphead20 said:
If you lose recovery flashing the Odin semaphore kernel usually does the trick
Click to expand...
Click to collapse
Yeah, I also think that'll do the trick if it happens again. But i'd rather prevent it than fix it every time. Thanks anyways
You could try flashing back to gb using my recovery kit, see if it helps, in the zip is all you need
Ezodin
Ezbase jvu ROM
Cf root kernel
Pit
Instructions with diagrams!
Here's link to it
http://db.tt/MOGZx01S
slaphead20 said:
You could try flashing back to gb using my recovery kit, see if it helps, in the zip is all you need
Ezodin
Ezbase jvu ROM
Cf root kernel
Pit
Instructions with diagrams!
Here's link to it
http://db.tt/MOGZx01S
Click to expand...
Click to collapse
Thanks mate, really, but I have no problem flashing back to GB.
My issue is that i'm getting Bootloops without any reason.
Flashed Gummy 1.2 back, no problem since yesterday, recovery's clean for now.
Sent from my GT-I9000 using xda app-developers app
Little "update". So far so good since yesterday, but could it be kernel-related?
Every time I had this issue, I ran Semaphore 1.2.2s.
Anyways, thanks a lot for trying to help me, I appreciate it, and if it happens again, be sure I'll try what you told me
Hi I was running Helly Bean and I was experiencing some lag that i couldnt fix so i decided it was time to start fresh (phone was getting to be a mess anyways) so i formatted my phone and one-click to a stock rom. (rogers i896 2.3.3 with bootloader). I used heimdell to flash kernel with recovery, then flashed devil kernel, reboot recovery, then flashed helly bean as per thread instruction and my phone kept booting into recovery only. So i tried to start over 2 more times with the same results, I even tried to flash CM9 stable release and it yielded the same results.
Can anyone shed some light as to what i messed up? My only option now is to use stock app since i cant seem to get anything else to work...(pleas dont make me go back to touchwiz)
Any help is appreciated,
Thanks.
PS phone works fine on stock rom
This happened to me once... I think it has to do with repartitioning and Devil kernel. If you flash devil first, it seems that something is telling the CM installer that the partitions are all good to go, even though it is clearly not the case. So use heimdall to flash the first kernel, and go straight to the ROM install, making sure to flash the ROM a second time after it reboots into the new recovery.
korockinout13 said:
This happened to me once... I think it has to do with repartitioning and Devil kernel. If you flash devil first, it seems that something is telling the CM installer that the partitions are all good to go, even though it is clearly not the case. So use heimdall to flash the first kernel, and go straight to the ROM install, making sure to flash the ROM a second time after it reboots into the new recovery.
Click to expand...
Click to collapse
Thanks, works first time!!! Looks like im going to have IMEI problems but thats another battle lol
odin to stock 2.3.6, charge to 100%, then go to recovery, 4w, 2f, then install helly bean.
just went thru this last week.... accidentally flashed incorrect ROM to Captivate and phone started acting wiered.
Then came to know i have the wrong bootloaders and kernel. Just installed GB bootloaders and phone started booting to recovery.
then tried to flash ics rom and soft bricked my phone.
Used the "hold both volume buttons and plugin the USB cable to computer" to get into download. then ODIN to stock GB. then used KKroot and then flashed Slim ICS. Now the phone works great.
Hi all,
Hoping someone knows how to solve this issue.
I have been running the CM10.2 nightlies and downloading and flashing manually without too much issue.
I decided to try the app 'CyanogenROM Downloader' aka CM Downloader.
It worked fine to download the latest nightly but when I used a future which booths the phone into CWM and flashes automatically it just started looping.
It loads CWM and starts flashing but only gets a quarter of the way through before the screen flickers and the flash starts from the beginning.
If I reboot the phone by holding power and volume up until it buzzes 3 times it still loads directly into CWM and attempts to flash again but gets stuck in the same loop.
Do I have to flash back to a stock ROM now using flashtool to fix this?
I have the same issue on PAC nightlies. Try to flash an older or custom (with twrp) kernel to use recovery and flash the newest cm over it.
Gesendet von meinem C6603 mit Tapatalk 4
ozzy lion said:
Hi all,
Hoping someone knows how to solve this issue.
I have been running the CM10.2 nightlies and downloading and flashing manually without too much issue.
I decided to try the app 'CyanogenROM Downloader' aka CM Downloader.
It worked fine to download the latest nightly but when I used a future which booths the phone into CWM and flashes automatically it just started looping.
It loads CWM and starts flashing but only gets a quarter of the way through before the screen flickers and the flash starts from the beginning.
If I reboot the phone by holding power and volume up until it buzzes 3 times it still loads directly into CWM and attempts to flash again but gets stuck in the same loop.
Do I have to flash back to a stock ROM now using flashtool to fix this?
Click to expand...
Click to collapse
so do a factory reset from the recovery and wipe devack chache
khamees_xi said:
so do a factory reset from the recovery and wipe devack chache
Click to expand...
Click to collapse
Thanks for the reply.
The issue was it wouldn't let me into the recovery menu.
All good now. I left it off for an hour and it booted fine. I manually launched CWM and flashed the ROM and it worked fine. I'll let the CM Downloader app devs know of the issue.