First up, I haven't posted here much, but I definitely don't consider myself useless.
I'm always flashing (with Odin and CWM zip flashes) different ROMS and experimenting.
I know that I can flash back to stock/Darkys Resurrection etc if I want to get my phone working again, but I'd really like to experiment more with CM7.
The issue I'm having is that after I thought I followed all of the install steps, when I reboot, the phone just keeps going back to recovery, not booting the ROM.
The first time I was coming from Darkys 9.3 (with EXT4 on all partitions inc. System). I didn't disable lagfix first, it didn't tell me to in CM7 instructions, so didnt think it was needed. I was also already using 500Hz Speedmod, so I didn't flash the Kernel first.
I had no issues with any steps, but after flashing cm7-galaxys-initial-20110220.zip, wiping and rebooting, I just ended up back in recovery.
So I thought I would do it all again, from the start. I reflashed Darkys 9.2 Resurrection through Odin. This time I disabled Lagfix. I then installed the speedmod kernel that comes with the CM7 package.
Then I followed the steps. Again, I land in recovery, and again rebooting the phone just puts me back in recovery.
Any help?
abbaskip said:
First up, I haven't posted here much, but I definitely don't consider myself useless.
I'm always flashing (with Odin and CWM zip flashes) different ROMS and experimenting.
I know that I can flash back to stock/Darkys Resurrection etc if I want to get my phone working again, but I'd really like to experiment more with CM7.
The issue I'm having is that after I thought I followed all of the install steps, when I reboot, the phone just keeps going back to recovery, not booting the ROM.
The first time I was coming from Darkys 9.3 (with EXT4 on all partitions inc. System). I didn't disable lagfix first, it didn't tell me to in CM7 instructions, so didnt think it was needed. I was also already using 500Hz Speedmod, so I didn't flash the Kernel first.
I had no issues with any steps, but after flashing cm7-galaxys-initial-20110220.zip, wiping and rebooting, I just ended up back in recovery.
So I thought I would do it all again, from the start. I reflashed Darkys 9.2 Resurrection through Odin. This time I disabled Lagfix. I then installed the speedmod kernel that comes with the CM7 package.
Then I followed the steps. Again, I land in recovery, and again rebooting the phone just puts me back in recovery.
Any help?
Click to expand...
Click to collapse
Did you use the 3 button combo to get in the recovery the first time
lownoise said:
Did you use the 3 button combo to get in the recovery the first time
Click to expand...
Click to collapse
EVERY time.
I made sure that I either powered down or battery pulled (depending where I was when I needed to go to recovery). Then I three-buttoned into recovery.
Uh... of course you're going to mess up your phone if you don't disable the lagfix... ALWAYS disable the lagfix before you flash, no matter what.
jujjk said:
Uh... of course you're going to mess up your phone if you don't disable the lagfix... ALWAYS disable the lagfix before you flash, no matter what.
Click to expand...
Click to collapse
Yeah, but I've retried the installation. Using Darkys Resurrection, I went back to having a fully function 2.2 ROM again. Disabled lagfix, and then followed the steps again. Same outcome.
dumb ? #1 You don't have your usb plugged in when you do this?
Reason I ask, is that on some HTC models, this happened if you left the usb connected.
Also it happens on 'certain' versions of CWM, V3 i think, worth a thought.
Also try coming in from a different kernel, maybe speedmod, your constant appears to be darky
silashack said:
dumb ? #1 You don't have your usb plugged in when you do this?
Reason I ask, is that on some HTC models, this happened if you left the usb connected.
Also it happens on 'certain' versions of CWM, V3 i think, worth a thought.
Also try coming in from a different kernel, maybe speedmod, your constant appears to be darky
Click to expand...
Click to collapse
We'll see how I go. I can't remember now if I had USB plugged in or not.
I'm downloading stock JPY now, and I'll go from there. See how we go!
So I just did it all again, starting from a stock JPY. And so far so good. Seems either Darky's was the problem, OR I had a USB cable plugged in (which I don't think I did)
Yep.
I'm now getting into CM7.
Everything seems great, though I can't get wifi working. But that's for the CM7 thread!
Related
Hi all,
I upgraded to Gingerbread and Juwe's ROM last night and all went well. That is until today when I ran the script to convert the filesystem to ext4. It rebooted into CWM and all seemed to go well except my phone is now stuck in a boot-loop. It gets as far as the initial "Galaxy S GT-I9000 Samsung" screen and then restarts to it every few seconds.
Background:
I followed the instructions as given in Juwes thread. Initially flashed XWJVB XEE firmware with bootloaders from this thread (this exact firmware I think) with re-partition,etc checked. After that I flashed CF-Root-XW_XEE_JVB-v3.1-CWM3RFS (no-repartition) and flashed ROM. ROM was working perfectly till I ran ext4.
Does anyone know of any way to fix this problem? I can boot into Download mode and CWM Recovery v3.0.0.5. I'm trying to avoid reflashing the ROM but if I can't get a solution soon I guess I'll just have to do that
Hmmm,
Are you able to get into recovery or download mode?
Edit: Just noticed you can.
Another question,
What did you use to convert to ext4?
Did you install Chainfire's ext4 addon?
electrotune1200 said:
Another question,
What did you use to convert to ext4?
Did you install Chainfire's ext4 addon?
Click to expand...
Click to collapse
Ya it's Chainfire's ext4 addon I used. Although it's just occurred to me that I think I used the one packaged with the ROM instead of the newest one from Chainfire's thread. Could it be an older version?
Yeah I really don't know about that. When we get the phone sorted, I would install his most recent addon to see if that's the issue.
As far as I know, you may only have 2 options.
First, you can try to do a factory reset in CWM.
If that fails, I'd start from the beginning, flashing with a 512 pit and re-partion.
electrotune1200 said:
Yeah I really don't know about that. When we get the phone sorted, I would install his most recent addon to see if that's the issue.
As far as I know, you may only have 2 options.
First, you can try to do a factory reset in CWM.
If that fails, I'd start from the beginning, flashing with a 512 pit and re-partion.
Click to expand...
Click to collapse
I was afraid you'd say that. Just got the phone setup as I wanted it
Just tried the factory reset in CWM and no joy. Guess I'll re-partition when I get home. Should probably be doing some work at the moment anyway
Sorry man,
Next time, set everything up after you convert it to ext4. Might save you another headache.
Also, make sure you have some free space on your internal sd card. I try to leave 1.5gb free for file system conversions.
Oh and,
get some work done already
Before you go and flash everything again.
Try flashing Chainfire's 3.1 kernal again. It might pull it out of the boot loop. Worth a shot though before starting all over.
Hopefully it works out for you without starting all over.
I tried reflashing the kernel but no joy. Just went with the complete reflash in the end. Was painless enough because I had everything set up to go from the night before
Thanks for all the help electrotune! Appreciate it
I am trying to install the latest cognition onto my samsung captivate. I have installed the gingerbread things successfully, however, when I try to flash the cognition kernal via clockwork mod, I get a signature verification error.
Furthermore, when I try to flash other kernals with an older CWM or the cf-roots, my phone just loops the boot screen. To fix it, all I do is put kernalKF1 back into the pda spot and start odin.
Also, I noticed that with zImage-root, I get the looping boot screen, but with the red fish instead.
Is the red fish supposed to still be in the boot screen after I flash the kernalKF1?
I am not sure if something is wrong with my odin or what... bottom line is, I want to install the latest cognition and be done with it. I have spent 7 hours on this already. lol at having an evening of free time.
bluDog said:
I am trying to install the latest cognition onto my samsung captivate. I have installed the gingerbread things successfully, however, when I try to flash the cognition kernal via clockwork mod, I get a signature verification error.
Furthermore, when I try to flash other kernals with an older CWM or the cf-roots, my phone just loops the boot screen. To fix it, all I do is put kernalKF1 back into the pda spot and start odin.
Also, I noticed that with zImage-root, I get the looping boot screen, but with the red fish instead.
Is the red fish supposed to still be in the boot screen after I flash the kernalKF1?
I am not sure if something is wrong with my odin or what... bottom line is, I want to install the latest cognition and be done with it. I have spent 7 hours on this already. lol at having an evening of free time.
Click to expand...
Click to collapse
Flashing Cognition 5V2 is a little "tirickier" than most. DG posted an updated initial kernel. I would flash the ODIN version in step 2. That kernel supports EXT4 formatting tools for a "stock" kernel which normally would not support voodoo. I would start off making sure you don't have lagfix enabled for system or data, flash KF1 (without bootloaders if you have them already) and then start with step 2 - ODIN. Hopefully that helps.
RichMD said:
Flashing Cognition 5V2 is a little "tirickier" than most. DG posted an updated initial kernel. I would flash the ODIN version in step 2. That kernel supports EXT4 formatting tools for a "stock" kernel which normally would not support voodoo. I would start off making sure you don't have lagfix enabled for system or data, flash KF1 (without bootloaders if you have them already) and then start with step 2 - ODIN. Hopefully that helps.
Click to expand...
Click to collapse
This helped me out, thanks a bunch I used odin for the kernal instead of cwm and it worked fine. I have no idea why I didn't even try that. Sad thing is, I figured it was only going to take maybe a minute or two, if that, to get cognition installed, and it did... haha, hours wasted.
Again, thank you.
I have a couple more questions, this time, concerning Cognition itself:
1) In the feature list of cognition, it says it has a custom launcher layout. Where can I find this? I just see stock touchwiz.
2) Everything that I install/download goes into my external sd card, so whenever I take it out, none of my apps work. How can I set it back to install into the internal sd?
I used SuperOneClick to root my phone, and now I'm looking through the Captivate Guide to see what else I can do with an unrooted phone. I started with Rom Manager.
So I clicked "Flash Clockwork Mod Recovery," and it was fine. I select my phone (Galaxy S - Captivate, not the Captivate MTD). I pressed "Backup Current ROM," but when I press "Okay," it restarts my phone to the blue menu. So I press "reset phone now," and I try to start from the beginning again. According to the guide, it says to restart it until it works. It's rebooting each time instead with no change. When I go to manage and restore backups, nothing is listed.
When I load up Rom Manager, under "Flash Clockwork Mod Recovery," it just says
"Current recovery: Clockwork mod 2.5.1.2
Latest Recovery: Clockwork mod 2.5.1.2"
Anyone know what I'm doing wrong? I'm using stock 2.2 Froyo and GO Launcher with Cartoon Theme (if that matters).
I've already tried TRusselo's method regarding the 3e issue with stock 2.2 phones: http://forum.xda-developers.com/showthread.php?t=1052991
Do I need SGS Kernel Flasher? If so, what kernel do I need?
/EDIT: Check my post 5 for my latest issue.
Why not just flash a KB1 kernel with cwm in it? I know Desing Gears cog 4.x.x kernels works, and probably eXistZ's kb1 kernel as well. They have cwm cooked in the + few other things like Voodoo, etc.
Also I believe your supposed to click install package as well. I could be wrong since its been a long while since I've used that method.
prbassplayer said:
Why not just flash a KB1 kernel with cwm in it? I know Desing Gears cog 4.x.x kernels works, and probably eXistZ's kb1 kernel as well. They have cwm cooked in the + few other things like Voodoo, etc.
Click to expand...
Click to collapse
I'm much too amateur with phones to do that.
The only reason I decided to finally root my phone was because my warranty is up, and because I found TheUnlocker's youtube account + Captivate guide. I figured with step-by-step instructions, there's no way I could screw up. Boy, was I wrong.
Dude...
http://forum.xda-developers.com/showthread.php?t=1232703 and then
http://forum.xda-developers.com/showthread.php?t=1236891
If you dont want Victory ROM then at least install Boogs Kernel and enjoy Clockwork Recovery!
Steve
Stevenrogers_420 said:
Dude...
http://forum.xda-developers.com/showthread.php?t=1232703 and then
http://forum.xda-developers.com/showthread.php?t=1236891
If you dont want Victory ROM then at least install Boogs Kernel and enjoy Clockwork Recovery!
Steve
Click to expand...
Click to collapse
I plan to use Cyanogenmod 7 eventually. The reason I haven't flashed a ROM is because I'm not 100% sure how yet. That's why I'm taking lots of small steps.
A lot of these ROMs also mention Odin, which I didn't use. I used SuperOneClick.
I went online and tried to flash my phone according to this guy's steps:
http://www.youtube.com/watch?v=6KvCxdYZ0nk
Okay, so even though I followed all of his steps, I get to the part where I'm supposed to find the MIUI file in my SD card, and it doesn't exist... even though I transferred it over. How come my phone doesn't recognize it? Phone is barely functional at the moment after I flashed it back to 2.1, and I'm encountering a lot of lag/bugs. If I plug in my phone to my computer without Debugging on, it fails to download drivers.
Does anyone know the best fix out of this situation?
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.