[Q] Clockworkmod Completely messed up - Captivate Q&A, Help & Troubleshooting

I decided today I was going to switch my ROM on my Samsung Galaxy S Captivate so I first tried to switch to Andromeda 3. It would not install so I restored my back up to the first back up I made that was the stock ROM after rooting and tried again to install Andromeda 3. So it finally installed but I didn't like it so I found a really cool ROM called Mosaic LINK-(http://forum.xda-developers.com/showthread.php?t=892973) which I installed. Now whenever I start up my phone I get a whole bunch of colored lines going across my screen but strangely enough it goes to the boot loader and works great but now I cannot get into recovery.
Every time I attempt to get into recovery I get the colorful lines across my screen and it freezes. I tried to flash the Clockworkmod recovery but it gives me only 4 model options to chose from (Galaxy S i9000, GalaxyS i9000 (MTD), Google Nexus S, and Nexus S 4G). I have tried flashing it to the Galaxy S i9000 but does not fix the problem.
I have looked on google trying to find a solution to my possibly corrupted recovery but cannot find anything similar and would love to hear some opinions on this because of right now I am stuck with the ROM forever.
Thank you

dalek823 said:
I decided today I was going to switch my ROM on my Samsung Galaxy S Captivate so I first tried to switch to Andromeda 3. It would not install so I restored my back up to the first back up I made that was the stock ROM after rooting and tried again to install Andromeda 3. So it finally installed but I didn't like it so I found a really cool ROM called Mosaic LINK-(http://forum.xda-developers.com/showthread.php?t=892973) which I installed. Now whenever I start up my phone I get a whole bunch of colored lines going across my screen but strangely enough it goes to the boot loader and works great but now I cannot get into recovery.
Every time I attempt to get into recovery I get the colorful lines across my screen and it freezes. I tried to flash the Clockworkmod recovery but it gives me only 4 model options to chose from (Galaxy S i9000, GalaxyS i9000 (MTD), Google Nexus S, and Nexus S 4G). I have tried flashing it to the Galaxy S i9000 but does not fix the problem.
I have looked on google trying to find a solution to my possibly corrupted recovery but cannot find anything similar and would love to hear some opinions on this because of right now I am stuck with the ROM forever.
Thank you
Click to expand...
Click to collapse
I don't have the same phone but since I root it I got those lines. Now, do you get in recovery by pressing vol-down and power at the same time?
Kingdom Revolution 7/23-1.77
Freedom a0.6 UNIVERSAL
Hardware 003.

OP there are instructions on post 2 of the mosaic thread that you did not follow you were supposed to flash stock I9000 gingerbread first to update your bootloaders THEN flash a kernel that has cwm with odin and THEN flash the rom, but since you've already flashed mosaic use this to update the bootloaders and it will solve your issues. http://forum.xda-developers.com/showthread.php?t=1180807
Next time please post in the rom specific q&a thread to keep the forum from getting cluttered that's why they're there.

dalek823,
Did u flash the i9000 gingerbread bootloaders/ stock i9000 gb/ or xcal's reorient kernel ??
(studacris, i didn't see ur post b4 i posted mine. Would not have posted the same answer if i would have seen urs first.)
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

studacris said:
OP there are instructions on post 2 of the mosaic thread that you did not follow you were supposed to flash stock I9000 gingerbread first to update your bootloaders THEN flash a kernel that has cwm with odin and THEN flash the rom, but since you've already flashed mosaic use this to update the bootloaders and it will solve your issues. http://forum.xda-developers.com/showthread.php?t=1180807
Next time please post in the rom specific q&a thread to keep the forum from getting cluttered that's why they're there.
Click to expand...
Click to collapse
Thanks for the referral.

So I am going to try this fix you guys are suggesting with the i9000 boot loaders but I have a question. Will I need to reinstall boot loaders for I897 in the future then if I want to go back to the ROMs I used in the past and from now on do I have to use ROMs for i9000 only?
Thanks for the help guys, I really appreciate it

No they are backwards compatible but to down grade to froyo flash a froyo kernel with odin and then flash the rom in cwm.
DO NOT FLASH THE 3 BUTTON FIX WITH GINGERBREAD BOOTLOADERS. it will mix a gingerbread primary and a froyo secondary and will HARD BRICK you're phone.

What do you mean, I shouldnt flash the 3 button fix?, how do I avoid that?

They are a zip and a .tar package to fix broken button combos. they were made for eclair/froyo but flashing them on gingerbread will brick the phone.
So to avoid doing that just don't flash either of those...

Ok, I will avoid any flashes to fix buttons. Thank you for all your help and I am happy to say my phone now goes into recovery again.
THANK YOU!!!!!!

You're welcome
Enjoy mosaic it was made by a bunch of lunatics

Related

[Q] Quick Question Regarding Odin, ADB and Flashing

Hello all! Long time lurker, first time poster! I'm on the verge (halfway through actually) of flashing my first custom rom: Serendipity 6.3. However I have run into a couple of issues that may or not be a problem.
1) I successfully used Odin 1click to flash back to stock from the official Froyo update when I went to master clear however at roughly 95% completion (On the Odin download bar) I got some sort of runtime error that had to force close Odin while the factory reset was occurring on the phone. Thankfully the phone rebooted and appeared to have wiped the Internal SD successfully. Was wondering if I should just re-download Odin if I plan on master clearing again. I abused the search function for the Cappy forums but couldn't find a solution to this specific problem.
2) After the whole Odin debacle I just decided to go on ahead with flashing Serendipity but ran into another problem... I cant reboot into recovery whereas I could prior to flashing back to stock... So I guess my question here is: Is it ok to use ADB reboot recovery to reinstall the packages that Serendipity uses as it's update.zip? Or should I download figure out how to use the other version of Odin that flashes the 3 button recovery?
I apologize for the length and possible redundancy and really dont want to step on any toes here but I have been wading through the sea of material (via the search function I promise!) on here and just get bogged down by the sheer volume of information out there on these multiple subjects...
If anyone could help me clarify any of this I would greatly appreciate it! You have truly taken me from wondering what rooting meant to beginning to experiment with custom roms! This site is truly a great resource!
Flash back to stock agin. Then try rooting it. Next install "rom manger" from market and install captivate update.zip . Next reboot into recovery (volume buttons plus power and release when see at&t screen) install packages then on clockwork manger recovery screen instal zip from sd and install your rom. But to hard reset dial *2767*3855#. But reflash stock sup don't have problems when flash your rom. Also cognition is as good rom if like stock look. P.m. me if need anything else.
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Rooting confusion

My brother rooted his Captivate 6 months ago or more. He kept the stock ROM, and now would like to try a custom ROM. Unfortunately, he doesn't remember much about what he did. He said he downloaded a program, plugged in his phone, and it rooted him.
I assumed that I should be able to boot into recovery and flash a ROM from there. I looked up how to boot into recovery, and tried the 'hold down vol/up and power on' approach. Instead of a recovery menu, it goes directly to some kind of update screen with this text:
movi-check start..!!
... <lines removed>
install default apk files please wait
I've searched for these lines, and cannot find why this is coming up. I did find that this should have ended with a message that the install finished, but after leaving it for 10 minutes, it seemed to just reboot. Perhaps the message did come up, and then it immediately rebooted.
Does anyone know why the phone is in this state where there is no recovery menu? If I install ROM Manager and flash ClockworkMod is that likely to work and not cause harm?
Need a little more info... is it stock 2.1 or 2.2? If it's Froyo 2.2 then the stock recovery is tricky to get around if you're new to flashing or modding.
jack man said:
Need a little more info... is it stock 2.1 or 2.2? If it's Froyo 2.2 then the stock recovery is tricky to get around if you're new to flashing or modding.
Click to expand...
Click to collapse
Thanks. It is stock 2.2.
I am not new to flashing, and I'm comfortable with adb and other tools. I'm just not familiar with the Samsung Captivate.
Is the screen that comes up with 'movi_check' the stock recovery? it appears to be automatically trying to update something.
Probably just be easier to use Odin to flash stock 2.1 and root and get recovery on it. Then you can flash any (2.2) ROM you want on it, or you could use Odin or Heimdall to flash Gingerbread onto it (recommended). There are tutorials all in the development section.
Sent from my SGH-I897 using XDA App
Reamer09 said:
Probably just be easier to use Odin to flash stock 2.1 and root and get recovery on it. Then you can flash any (2.2) ROM you want on it, or you could use Odin or Heimdall to flash Gingerbread onto it (recommended). There are tutorials all in the development section.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
If its a newer build it wont like 2.1 (alot of newer builds bootloop with 2.1). If your captivate is one of the newer builds and has the 3e recovery here is a guide to get past it.
As to flashing Gb you will need GB bootloaders wich carries risk. Please READ on how too and risk that may happen. Its a small risk but you can hard brick the phone if you mess up bootloaders or if the booloader fails to flash.
Another option is flashing KB1 2.2 froyo and using Desing Gear's Cog 4.x.x kernel. You will have clock work mod. There's a ton of ways to do it most of wich are in the forums already so search and if you have doubts ask
prbassplayer said:
If its a newer build it wont like 2.1 (alot of newer builds bootloop with 2.1). If your captivate is one of the newer builds and has the 3e recovery here is a guide to get past it.
As to flashing Gb you will need GB bootloaders wich carries risk. Please READ on how too and risk that may happen. Its a small risk but you can hard brick the phone if you mess up bootloaders or if the booloader fails to flash.
Another option is flashing KB1 2.2 froyo and using Desing Gear's Cog 4.x.x kernel. You will have clock work mod. There's a ton of ways to do it most of wich are in the forums already so search and if you have doubts ask
Click to expand...
Click to collapse
It crossed my mind that newer builds wouldn't like 2.1, but I wasn't 100%, that's why I recommended going to GB. Just reading the instructions a few times and being prepared the risk is very low to hard brick. Just make sure to know exactly what you're doing when you choose which files for the primary and secondary boot loaders.
But said person is asking info on something as simple as rooting, Hence there are easier less evasive ways to get past 3e.
prbassplayer said:
But said person is asking info on something as simple as rooting, Hence there are easier less evasive ways to get past 3e.
Click to expand...
Click to collapse
Just to clarify, I'm not asking about rooting, but about flashing and the recovery console. I'm an EVO user, and I just don't know the idiosyncrasies of the Captivate.
Am I correct that the messages I get when trying to go to recovery (starting with movi_check start) are normal, and that after those messages I should get the recovery console? If so, it seems to be stuck on the "install default apk files please wait" step, as this doesn't seem to complete.
I do see the steps on how to flash, and can follow them carefully, but since I am not getting the recovery console, I am not sure what might be wrong.
glenwill said:
Just to clarify, I'm not asking about rooting, but about flashing and the recovery console. I'm an EVO user, and I just don't know the idiosyncrasies of the Captivate.
Am I correct that the messages I get when trying to go to recovery (starting with movi_check start) are normal, and that after those messages I should get the recovery console? If so, it seems to be stuck on the "install default apk files please wait" step, as this doesn't seem to complete.
I do see the steps on how to flash, and can follow them carefully, but since I am not getting the recovery console, I am not sure what might be wrong.
Click to expand...
Click to collapse
You can't flash a rom with stock recovery. You need clockwork mod wich can be achieve by using rom manager (needs root) or flashign with Odin a kernel that has it built in
prbassplayer said:
You can't flash a rom with stock recovery. You need clockwork mod wich can be achieve by using rom manager (needs root) or flashign with Odin a kernel that has it built in
Click to expand...
Click to collapse
Thanks for your help. I do understand I can't flash with stock recovery.
Both the 'Read BEFORE flashing' and the 'How to Install a custom ROM' guides instruct to install clockwork mod. I am aware that installing a new recovery needs to be done before flashing on probably any device.
I guess my primary confusion was whether the 'movi_check start' verbage is normal to see when I am trying to go to Recovery before installing Clockwork. Another google search finally found a hit that says it is normal to see this. I'm still not clear whether I should be concerned that it hangs on the "install default apk files" step.
Since it hangs, I don't ever get any kind of recovery menu, so it wasn't obvious to me that I was actually in the stock recovery.
Assuming this doesn't indicate any issues, I'll proceed with the instructions and all should be well.
Well I hope you are able to work it out. ^^

Power Reset or Unknown Upload Mode When flashing modems or google apps

I'm running CM9, before that CM7, and before that I had a problem with my 3-button recovery I believe I was on stock 2.2 I had used a fix somewhere in the forum for the 3 button fix and it worked. But now for example if I flash a different modem and or Google apps it does flash but then I get Power Reset or Unknown Upload Mode error screen. I have to pull the battery out and it will reboot. I think this may have something to due to the boot loaders? Any help would be helpful thanks.
I think it's a product of that 3 bottom fix, which you should never flash again. To be sure, you should probably just get on gingerbread bootloaders
Sent from my CM9 ICS i897 Captivate
Reminder, probably can't flash bootloaders while on cm/ics. I think the framework difference in that and Samsung causes problems. Also, try reformatting your internal memory sd card, just back everything you want to keep up first.
Lookup any Heimdall one click GB ROMs and enable bootloaders update. Apex ROM one of them.
is there a way i can just flash the boot loaders without going back to stock?
dave1977nj said:
is there a way i can just flash the boot loaders without going back to stock?
Click to expand...
Click to collapse
You technically can, but you won't be able to boot without flashing to stock from there. So don't do it
Sent from my CM9 ICS i897 Captivate
Well it was a pain in the a$$ went to stock UCKK4 2.3.5 had to root that then had to change the kernel to corn for CWM recovery and flahed CM9 back. Took me like 2 hours the problem is now fixed
dave1977nj said:
Well it was a pain in the a$$ went to stock UCKK4 2.3.5 had to root that then had to change the kernel to corn for CWM recovery and flahed CM9 back. Took me like 2 hours the problem is now fixed
Click to expand...
Click to collapse
You can root from corn. It's really easy
Sent from my CM9 ICS i897 Captivate
I flashed my captivate out of box having 3-button issue and installed cyanogen mod 9 which did not detect my PC so I tried to downgrade to cm_captivatemtd_full-179 from which I could not boot. Its continuously rebooting from bootloaders screen. Can you please help me fixing it..?
sriram_mech86 said:
I flashed my captivate out of box having 3-button issue and installed cyanogen mod 9 which did not detect my PC so I tried to downgrade to cm_captivatemtd_full-179 from which I could not boot. Its continuously rebooting from bootloaders screen. Can you please help me fixing it..?
Click to expand...
Click to collapse
To clarify, are you only seeing the white AT&T World Phone screen?
Sent from my CM9 ICS i897 Captivate
I can see the At&T white screen....after that its goes into cyanogen mod screen and then cwm mode pops and again restating...
sriram_mech86 said:
I can see the At&T white screen....after that its goes into cyanogen mod screen and then cwm mode pops and again restating...
Click to expand...
Click to collapse
Boot into recovery, do a factory reset, wipe dalvik cache, then install from SD card.
cant go back to stock rom galaxy i897 at&t
hello can someone help me please? i have a samsung i897 captivate it turns on but dont starts logo at&t pass google logo pass then a multicolor image appears and thats all, i try with the hard reset but fail the only thing that appears its this,
modem booting...
end modem booting.
now start usb upload.
an android image Power reset or UNKNOWN UPLOAD MODE,
i only want the stock rom from at&t help me please

Download/Recovery Mode ok, BUT cannot bootup

I was running on froyo before I started process, and now I cannot boot up. This is what I did:
First I used the step 1 in the cyanogenmod wiki (http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide) to install the ClockworkMod Recovery, everything is fine, until the final reboot step. after the ATT screen, the screen get into total unrecognized mode, and the unit will restart, and so on and on, in a loop.
Then I tried to use the speedmod-K13E with GB bootloader one click, and I still can't get into the system, but now it just stuck at the Galaxy S samsung screen, after the ATT screen, and no loop, just stuck.
Any suggesstions? Is there a stock rom I can restore back to using the external sd card? the internal sd card currently only has the cyanogenmod 9 on it. I have going through the different posts for the past two days, got really confused. If someone can point me to a step by step guide, or something similiar, really appericiated.
BTW, the recovery mode has the following:"ClockworkMod Recovery v2.5.1.0 SpeedMod ULFK
I'm on windows 7 32bit. And I donot need to save any data on the phone. It can be wipe clean.
Did u try rebooting into cwm recovery and try to re install the rom again ?
U may need GB bootloaders as well for cm 9 (?? I'm not sure though)
Sent from my SAMSUNG-SGH-I777 using xda premium
If you still want to run cm9 try flashing a more recent kernel inn recovery. look in the Dev section for glitch kernel or devil kernel (i like devil) they have a more recent version of cwm that should work. I haven't used this method with cm9 but it worked with aokp.
Sent from phone with app
well.. my advice is try reflashing to the stock rom using the one click in this thread [Stock ROMs](OneClicks Master Collection)+[Kernels (Stock & w/ CWM)]+[Modems] UPDATED
(kk4 reccomended)
download one of the odin one click there, and flash your rom back to stock gingerbread, oh yeah, choose the rom without the bootloader.
if that doesn't get you anywhere, please reply to my post.
lan_baba said:
I was running on froyo before I started process, and now I cannot boot up. This is what I did:
First I used the step 1 in the cyanogenmod wiki (http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide) to install the ClockworkMod Recovery, everything is fine, until the final reboot step. after the ATT screen, the screen get into total unrecognized mode, and the unit will restart, and so on and on, in a loop.
Then I tried to use the speedmod-K13E with GB bootloader one click, and I still can't get into the system, but now it just stuck at the Galaxy S samsung screen, after the ATT screen, and no loop, just stuck.
Any suggesstions? Is there a stock rom I can restore back to using the external sd card? the internal sd card currently only has the cyanogenmod 9 on it. I have going through the different posts for the past two days, got really confused. If someone can point me to a step by step guide, or something similiar, really appericiated.
BTW, the recovery mode has the following:"ClockworkMod Recovery v2.5.1.0 SpeedMod ULFK
I'm on windows 7 32bit. And I donot need to save any data on the phone. It can be wipe clean.
Click to expand...
Click to collapse
You should be good to go. You should be on GB bootloaders. Just reflash CM9 in CWM.
Solved.
For some unknown reason, I can net get ODIN to communication with my device, I tried multiple device, and it seems ODIN just does not work.
I used the 3rd post in your link, with Heimdall I successfully installed the KK4 and then I used the cyanogenmod wiki again, this times it works. It seems the old stock rom won't work for the wiki, must use the new stock rom.
Thanks for all the helps, guys.
irfarf said:
well.. my advice is try reflashing to the stock rom using the one click in this thread [Stock ROMs](OneClicks Master Collection)+[Kernels (Stock & w/ CWM)]+[Modems] UPDATED
(kk4 reccomended)
download one of the odin one click there, and flash your rom back to stock gingerbread, oh yeah, choose the rom without the bootloader.
if that doesn't get you anywhere, please reply to my post.
Click to expand...
Click to collapse
lan_baba said:
Solved.
For some unknown reason, I can net get ODIN to communication with my device, I tried multiple device, and it seems ODIN just does not work.
I used the 3rd post in your link, with Heimdall I successfully installed the KK4 and then I used the cyanogenmod wiki again, this times it works. It seems the old stock rom won't work for the wiki, must use the new stock rom.
Thanks for all the helps, guys.
Click to expand...
Click to collapse
you're welcome,
glad i can help

[PLEASE HELP] I cant install JB or even ICS because of downgrade

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!

Categories

Resources