So I'm on an i9000m that has had recovery enabled since purchase.
Anyway, I've been pretty confident with flashing it since I got it. Run a lot of firmwares etc... then finally went to CM6 Beta 3 and then tried CM7.
CM7 was super buggy though so I tried flashing JPY with heimdall. When I flashed JPY, it would go straight to recovery with some format errors. SO I figured it was because I previously had voodoo lagfix, and I put the voodoo kernel on.
Now the issue is, it works till the boot animation then goes to a black screen and buzzes like it's FCing. I don't think it's a fault with the internal memory because I can access it through CWM.
I can go to recovery and I can flash back to CM7, and it'll work. ALbeit with all the issues in CM7 right now.
Any ideas?
yes,
give Darky's ROM Resurrection Edition
a try, after that flash again to full Darky's 9.2 via cwm
that should hopefully do the trick
zacharias.maladroit said:
yes,
give Darky's ROM Resurrection Edition
a try, after that flash again to full Darky's 9.2 via cwm
that should hopefully do the trick
Click to expand...
Click to collapse
That worked wonders. Hopefully the CM7 bugs will be worked out soonish. It flies.
this really helps!!
tried EzBase before, but it got stuck. so its nice to have another lifesaver
btw I tried flashing EZBase over MIUI, because I got sick of its battery drain and bad video recording. Its very nice and smooth though... too sad
Related
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!
Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
+1 get clockwork recovery...you need to make sure the rom you are flashing is compatible with the version of CWR you are using.
For example a rom that needs to be installed with CWR3 you will need to install the zip presumably from CWR2. Pull the battery and reboot back to recovery - you should now be in the updated version of CWR. Then for safety sake - re install your zip.
Reboot and you should be all set.
I had lots of trouble going from 2.2 to 2.3. Flashing between 2.3 roms is very easy comparatively
milkytron said:
Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
Click to expand...
Click to collapse
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
pwnerman said:
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
Click to expand...
Click to collapse
I did have the bootloaders, I went back to stock before I did anything just to be safe. I'm gonna try what the other guys said though right now, wish me luck haha
jmtheiss said:
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
Click to expand...
Click to collapse
Alright so I have Andromeda 2.1 which is a froyo rom. Which method should I use to get to stock GB?
use Odin to flash gingerbread bootloaders then flash gingerbread roms
howtomen said:
use Odin to flash gingerbread bootloaders then flash gingerbread roms
Click to expand...
Click to collapse
I flashed the gingerbread stock rom and have it rooted with xcal's kernel, but when i flashed mosaic IV it got stuck at formatting partitions and i pulled the battery after about 15 minutes and then restarted my phone to find it stuck in a bootloop. So i had to start from stock again and now im back to gingerbread stock with root. I'm kinda scared to try again because it takes me like 30 minutes to get back to gingerbread stock with root. I think ill just stick with stock for a little bit
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
I have had my captivate for a while now and I have had a few problems with flashing Cyanogen based Roms since I went to CM7 then back to stock a while back.
I had CM7 running fine and went up to CM9 for months. I just recently went to REMics and had a problem with the sound and at the same time I had problems with my power button I the flashed to Paranoid Android for a few hours and was driving around so I took my phone to the AT&T warranty center to see about them replacing it and im out of warranty so I had them flash it to stock now I cant get my phone to CM7 I can get it to run Serendipity just fine but no CM7 can someone PLEASE help? It seems like I need to COMPLETELY clear the phone of all old rom data. Any solutions?
Try using one of these Stock I897UCKK4 Android 2.3.5 One Clicks and then flash the KK4 Corn Kernel version 7.0A to get the CWM Recovery u need to move on to what you are wanting to flash per that Rom's specific install instructions.
Done that
I have put my phone back to stock KK4 with and without bootloader. I had this problem before when I was going to CM7 the second time. Its just getting SO annoying now. Thanks though!
I forgot to say that when I go to flash the rom through CWM it starts reboots the phone the samsung Cyanogen screen comes up flashes onces then goes into CWM flashes a few things quickly and the last image I see is the "dead" androind laying on its back with the sign aboveits open front door.
I'm starting to think there is no help. Maybe I can trade my friend my captivate for his.
Have you tried flashing CM7 again after you see that CWM screen? I've always had to flash CM7 twice for it to take - once to get the MTD setup in place, a second time to actually flash the rom. You'll have to hold down V+/V-/Power to get to recovery while it's looping, but once it's there, try flashing CM7 again.
jmtheiss said:
Have you tried flashing CM7 again after you see that CWM screen? I've always had to flash CM7 twice for it to take - once to get the MTD setup in place, a second time to actually flash the rom. You'll have to hold down V+/V-/Power to get to recovery while it's looping, but once it's there, try flashing CM7 again.
Click to expand...
Click to collapse
I have tried with cm9 but not 7. I will try that once I get sick of Serendipity. I just set everything back up on this rom and installed my apps so I will wait a few more days.
Thanks You!
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.