Related
As you are about to see, I'm new to this.
I have been attempting to root my Captivate. I have tried Galaxy One Click Root and Super One Click 1.7, among others.
My phone won't enter recovery mode. I have tried to install z4root, which the phone blocks. I've tried using sideload wonder machine, which doesn't work either.
I downgraded to 2.1....nothing. Reloaded 2.2....nothing.
Any advice would be helpful at this point, and please be specific, as I am slightly retarded.
It its rumored that Odin one click to jf 6 will actually get rid if the recovery/ download modes, maybe try flashing a cognition ROM
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
ryanmahan said:
It its rumored that Odin one click to jf 6 will actually get rid if the recovery/ download modes, maybe try flashing a cognition ROM
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
That's not a rumor, it's a fact. Does not happen with all models.
What about full odin to jf6? I personally like to use odin every so often to master clear.
It would explain why superone click wouldnt root my phone lst time i master cleared, too. Ended up installing cwm and flashing straight to rom(which took care of rooting and 3rd party apps)
mrhaley30705 said:
What about full odin to jf6? I personally like to use odin every so often to master clear.
It would explain why superone click wouldnt root my phone lst time i master cleared, too. Ended up installing cwm and flashing straight to rom(which took care of rooting and 3rd party apps)
Click to expand...
Click to collapse
As I said, I'm slightly retarded. Do you know of a forum with instructions for doing this? Everything else I've tried has just caused a face to appear on my phone's screen laughing at me.
When you use super one click, did you enable usb debugging?
Sent from a place my wife doesn't know about
The captivate is actually an extremely easy root process...
Download this file update.zip
Put it on your internal SD card (internal Memory) not your SD card you can remove
Turn off your phone
Once off hold both volume up and down and hold power until you see the AT&T boot screen then let go of all 3 buttons. You should see recovery mode soon. Select Reinstall Packages, congratulations you are now rooted.
Is that the modded cwm? I think he said he was on 2.2. Regular cwm won't work with froyo(signature verification errors). There is a modded one somewhere on this site that either replaces 3e, our fixed sig on cwm.
Sent from a place my wife doesn't know about
I think he downgraded to 2.1 again which is what you'll need to be on to use the method I described.
jayjr1105 said:
I think he downgraded to 2.1 again which is what you'll need to be on to use the method I described.
Click to expand...
Click to collapse
I'm running 2.2
1-Downloaded and installed file update.zip to internal sd. Turned off phone. Tried to enter recovery mode. Got blank screen, att screen, blank screen, att screen, blank screen, etc etc.
2-Tried to install z4root. Blocked by phone. Tried to use sideload wonder machine, which can't detect the phone (in usb debugging mode and mass storage (tried both))
3-Tried Super One Click, which ran but did nothing.
4-Flashed to 2.1 and factory reset. Tried (2) again. Failed. Tried 1-3. Failed.
5-Flashed to a different version of 2.2. Started over. Failed.
I've been using some of the mobile tech videos, but everytime I get to the "Eureka!" phase, my phone just laughs at me.
use odin full version to flash speedmod kernel on 2.2, i even do this on 2.1, but on 2.1 you need the .zip file on the sdcard before you start because the phone will not boot with a 2.2 kernel, only enter recovery.
once on speed mod kernel you can either root and flash a kernel for att roms or flash a new rom without the need to root, the new rom will be rooted.
if you are on 2.2 you will need a computer one way or another, flashing back to stock can be a pain for those with the 3 button problem and it is way more time consuming than flashing a kernel, i have never used the tools out there but i don't know of an easier way than flashing a kernel via odin, especially if you intend to flash a 3rd party rom. also any time you flash a sbl.bin or boot.bin can be a dangerous situation. bad flashes that break the boot loaders aren't common but it causes enough "omg i bricked" threads to keep me from recommending it. there is a odin one click with a 3 button fix, if you use that once it will be fixed untill you flash a rom with odin that changes the bootloaders again. im not sure if there is a .tar stock rom for odin without the bootloader but that would be a good idea if there isn't.
you must not have the right drivers installed.
2.2 cannot be rooted by using an update.zip....you will need to get your drivers working and adb seeing the device....
sharp1114 said:
I'm running 2.2
1-Downloaded and installed file update.zip to internal sd. Turned off phone. Tried to enter recovery mode. Got blank screen, att screen, blank screen, att screen, blank screen, etc etc.
2-Tried to install z4root. Blocked by phone. Tried to use sideload wonder machine, which can't detect the phone (in usb debugging mode and mass storage (tried both))
3-Tried Super One Click, which ran but did nothing.
4-Flashed to 2.1 and factory reset. Tried (2) again. Failed. Tried 1-3. Failed.
5-Flashed to a different version of 2.2. Started over. Failed.
I've been using some of the mobile tech videos, but everytime I get to the "Eureka!" phase, my phone just laughs at me.
Click to expand...
Click to collapse
sounds like you need the 3button fix first. there is an odin stock rom+3button fix, it should take you to 2.1 but you will get recovery mode. if that fixes the recovery mode 3-button combo and the phone boots you can put the rom of your choice on the sd card, then odin flash speedmod kernel and flash the new rom, warning the phone doesn't boot a 2.1 rom with speedmod kernel, i only do this as a faster way to get into cwm recovery, only do that if you intend to flash a rooted rom from 2.1.
Dani897 said:
use odin full version to flash speedmod kernel on 2.2, i even do this on 2.1, but on 2.1 you need the .zip file on the sdcard before you start because the phone will not boot with a 2.2 kernel, only enter recovery.
once on speed mod kernel you can either root and flash a kernel for att roms or flash a new rom without the need to root, the new rom will be rooted.
if you are on 2.2 you will need a computer one way or another, flashing back to stock can be a pain for those with the 3 button problem and it is way more time consuming than flashing a kernel, i have never used the tools out there but i don't know of an easier way than flashing a kernel via odin, especially if you intend to flash a 3rd party rom. also any time you flash a sbl.bin or boot.bin can be a dangerous situation. bad flashes that break the boot loaders aren't common but it causes enough "omg i bricked" threads to keep me from recommending it. there is a odin one click with a 3 button fix, if you use that once it will be fixed untill you flash a rom with odin that changes the bootloaders again. im not sure if there is a .tar stock rom for odin without the bootloader but that would be a good idea if there isn't.
Click to expand...
Click to collapse
Do you have a suggestion for a stable rom? I don't want to get to the point where I've got it working and throw a terrible third party on it. I'm just looking for device speed and controll over all apps, especially bloatware.
all of the available roms are stable. to be honest TiBu will remove bloat if you want it to.
Try them all and see which one you like. Pretty much all of the custom roms are better than stock. If you like to stay near stock but run more optimized, see Cognition. Otherwise see which one you like more. It's not a hard process if you read up on it.
sharp1114 said:
Do you have a suggestion for a stable rom? I don't want to get to the point where I've got it working and throw a terrible third party on it. I'm just looking for device speed and controll over all apps, especially bloatware.
Click to expand...
Click to collapse
it is hard to go wrong with cognition which is a stock rom with some mods and bloat removed and tethering enabled, that will have the proper kernel and modem for the captivate which for me has great call quality, also the disadvantages of not having hsupa are overblown.
there is also andromeda which is the rom from the armani captivate and is well polished and complete, has some of the more useful samsung apps. this can be used with a 2.2.1 kernel ported from the i9000 for a slight speed boost (shows in benchmarks, may not be detectable in user experience) this has hsupa and is designed for the captivate
i9000 ports are newer 2.2.1 versions and all of the features work now so you may want a newer firmware version from one of those..
there are many 2.2.1 i9000 roms that are fully functional. that is more a matter of feature set and theme preference it is hard to say one is better than the other. id say for stable the speedmod kernel is about the best on an i9000 port, for experimenting with overclock or undervolt i hear that the kernel with paragon is awesome.
now it is odd that you say you flashed a different version of 2.2 but cant get into recovery, was that in odin? can you get download without adb commands?
Dani897 said:
im not sure if there is a .tar stock rom for odin without the bootloader but that would be a good idea if there isn't.
Click to expand...
Click to collapse
Use this method to flash back to stock. Supposed to be much safer that doesn't mess with the bootloader files. I have been using it for about 3 weeks now to flash back to stock. You CAN however still use the one click odin to master clear once you have flashed back to stock.
Back on topic... I would flash back to 2.1 using the above method and master clear to start fresh with this issue. Once that is done look for mobiletechvideo's 3 button fix video on youtube. But even if you have 3 button issues the Galaxy S one click root program should still get you into recovery. It doesn't always succeed in copying the update.zip file to the internal SD card but you can do that manually and just use the program solely to get into recovery. Make sure you have USB debugging on. After the stock flash and master clear it is off by default and samsung kies is on. You might want to invest in a Jig also since you have 3 button issues, it may save you hide someday.
As far as a good rom goes. Really all the 2.2.1 roms are pretty stable and fast. I'm currently using Continuum 4 with the paragon kernel and it floats and sips battery. If you like the stock look you can use cognition. If you like the green themed gingerbread look you can use Phoenix, Serendipity, Firefly, or Paragon which is my personal fav but hasn't been updated in a month.
Anyways good luck. I'm sure you'll figure it out.
oops, got double posted somehow
Thanks for all your advice and help. I finally got it rooted.
I've tried Cognition 4.3 and Paragon, both of which I liked. I like the appearance of Paragon, but the optimization just doesn't seem to be there. Cognition is great for customization, but I the appearance is just to 'stockish' for me, if that makes sense. Something in between would be nice. (Ideas?)
I plan to try Phoenix Unleashed, but i can't get it to download.
The reason why the programs are having a hard time seeing your cappy is because you need the Serial COM driver available only by installing Samsumg's software: Kies Mini... don't run the program just install it. Once you do this Odin and the Wonder Root program can see the phone. I had this issue.
I just rooted and installed a custom rom, followed the guide here. and after i rebooted the first time i get a scribbler looking screen just random colors looks bad. now when i open recovery thats the screen i get on 3/4 of the screen and the rest is shrunk down. so i can barley see what im doing on the recovery.
it is a att captivate.
any one know anything about this?
i installed the mosaic IV and i cant get past the tutorial. keeps asking me to open keyboard and it just sends me back to the start of the tutorial. help!
You need to flash Gingerbread bootloaders. Go back to the Mosaic thread, look at the very first post. You should find further instruction there.
kingofall00 said:
I just rooted and installed a custom rom, followed the guide here. and after i rebooted the first time i get a scribbler looking screen just random colors looks bad. now when i open recovery thats the screen i get on 3/4 of the screen and the rest is shrunk down. so i can barley see what im doing on the recovery.
it is a att captivate.
any one know anything about this?
i installed the mosaic IV and i cant get past the tutorial. keeps asking me to open keyboard and it just sends me back to the start of the tutorial. help!
Click to expand...
Click to collapse
This is what you will get when you install a gingerbread rom without having the gingerbread bootloaders. Since you are still on the stock bootloaders you can try out DGs gingerbread which will flash bootloaders that ARE FOR our captivates and still have gingerbread goodness. I am not saying the i9000 roms aren't really awesome but a LOT of newbs have bricked their phones either installing the gingerbread bootloaders or trying to go back to stock bootloaders. Good luck with your venture.
So if you are determined to get Mosaic IV then flash the gingerbread bootloaders and then probably reflash the Mosaic IV rom and it should work. Just MAKE SURE you have a GOOD USB cable, good computer with the USB connected to a USB port on the motherboard. Good Luck
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
I can not push this enough. Please understand what you ate doing before doing it. This is the third thread with this same issue because people are not reading all the instructions or are trying to side step some if the steps to make it easier. I will say this. The right way is never easy, and the easy way is never right.
If you are not 100% sure on what you are doing, then don't do it.
Hey folks. I'm bailing on Gingerbread because it was causing me too many problems. I'm trying to get back on Firefly 3.0 and I'm stuck at getting the phone rooted.
Whenever I try to copy the Root.zip from the AIO folder over to the phone's root folder, I get an error about the parameter being incorrect. I'm not sure what to do at this point.
Use Fugu root? Easier.... Also depending on what Gingerbread you are on there are kernels that have the root scrip baked in them.
^ you misread he's not on gingerbread, he wants to flash firefly.
You don't need root to flash a ROM. Odin a kernel that has cwm baked in. boot into recovery and flash the ROM.
Thought he was on GB trying to get on... you know what ya I missread. @OP do what Studa said xD. Wonder why people think they need root to flash roms..... I blame Rom Manager.
I know I don't need to root the phone, but in order to get certain things done on the phone, it's necessary.
I'm actually at a wall right now. I used SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click which successfully booted my phone to ATT 2.2 firmware, but I can't get any Odin to pick up on it now. I've tried five different Odins.
At this point, I think once I get the phone up and running on Firefly, I'll be walking away from flashing until I get another phone. Then I can use this for testing, etc.
On a side note, before I started this project yesterday, my modem was messed up. Now it would seem I have a successful connection to wifi, which I couldn't get.
As great as that is, I still can't get Odin to pick up my phone. Any thoughts?
Was that kb2 package heimdall?
If so you have to uninstall the heimdall driver and reinstall the Samsung driver.
Either way I would reinstall the Samsung drivers but it is a must if you used heimdall add the drivers conflict.
Alright. That's done, but I'm on I896UXJL1-stock now, and I'm pretty sure in doing that through Odin 1.85 I unrooted the phone. Correct me if I'm wrong. That's why I used the ATT stuff, because it auto-rooted the phone.
So it would seem I have some issues to work through. I can either root my phone and be stuck with ATT firmware that I don't want, or I can unroot the phone and use Rogers stock and hope for the best with Firefly.
This is by far the most confusing computer-related issue I've ever worked with. There's too many options to play with and they all work differently.
Why would you be stuck on at&t firmware? Why do you need to root before flashing firefly? Why don't you root Rogers stock?
you're confusing everyone involved lol
Okay, so maybe I'm a little in the dark on the rooting issue. Basically, I'm going back to Firefly because I thought it was amazing. Fast, responsive, and no issues I can think of on my phone.
I'm rooting the phone because it's my understanding that in order to spoof my location in order to get certain apps (Google Music), I'd need to be rooted.
I'm having a hell of a time trying to get this done, and my biggest problem, to reiterate, is that I have about fifteen different Roms, all either ATT or Rogers, three different Pit files, and so, so many Odin programs.
I'm now on 2.1 with that Toronto stock firmware, in order to work around the 3e error in recovery mode when trying to put on Clockwork. Unfortunately, now I'm getting some other error in regards to the Update.Zip file, Status 7.
I apologize for confusing people, but I promise I've read as much as I can about the tools I'm using, but I'm running in circles, flashing back and forth trying to find solutions.
you do not need to root before flashing the rom. it will be rooted after and then you can do what you need to do to get your apps working if you need to (firefly contains canadian locale cause its based off of rogers froyo firmware) changing stuff before you flash so apps can work is a waste of time as the flash will overwrite the firmware you just tweaked.
now, since your on eclair i'm attaching an update.zip that contains cwm, put it in the root folder of your sdcard boot into recovery select reinstall packages twice and it should boot into cwm where you can then flash firefly.
You're a frickin' genius, Studa. Don't let anyone tell you otherwise. I've got Firefly on thanks to that Update file, and I'm getting the ball rolling on everything else. If I wasn't so broke, I'd donate, but I hope my thanks is good enough. I really appreciate the help. It cut through twelve hours of stupid.
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
in terminal emulator type su and then reboot recovery maybe it work
or may be you just flashed unsupported recovery
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
I have been having the same problem recently, but not just with this rom. I have flashed many roms to my device, but it appears that almost everytime i try to flash something now, the same exact thing happens as the OP. any information on what is wrong or how to fix this would be greatly appreciated.
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
Sometimes this happens, but i am usually still able to use the rom after i wait for awhile. Recently it just gets stuck at the ATT logo screen and does nothing else.
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
studacris said:
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
Click to expand...
Click to collapse
i just tried it with a solid connection and it almost instantly said failed in the red box. now i cant turn it on or get to download mode so im pretty sure it is hard bricked. is there any way you can help me with this?
EDIT: False alarm, i can still get to download mode so i can ODIN back to stock, but i do not know if i should risk it again
Whew that was close.
You can flash to stock using a bootloader less package, that way if it fails it can't hard brick.
Then if that works, find an entire stock gingerbread package with bootloaders included, and flash that instead of just the bootloader one click. this again, will involve risk, but full Odin package seem to work better on some phones than one clicks do.
I tried to flash the bootloader again and it succeeded. i then proceeded to try and flash Fasty KK4 v1.1 and once again i was stuck at the ATT logo. For some reason with every rom i flash, when the logo pops up, it starts dim and then get bright. After it gets bright, it stays that way and it is a real pain not being able to use custom roms anymore.
If you have the GB bls just make sure you follow LL's instructions in the OP for Fasty. I had the same issue, but it was me mistake for not following the istructions properly
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
i DO get a very colorful white noise screen whenever it boots up ...the screen goes away once it fully reboots....I wondered about it but just assumed it was a quirk of the FASTY III package...
Is Rom Manager a froyo based app?
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
studacris said:
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
Click to expand...
Click to collapse
Really? Rom Manager helped me a lot until this Fasty III installation....even in my previous rom Fasty II it worked fine and did great for backing up and restoring backups....saved my asss a few times with those restores lol....But if this program doesn't work for fasty III what comparable program can I use?
Also I still can't intorecovery mode...nothing works...I even tried using ADB and Droid Explorer....nothing seems to get it into recovery mode...
Am I going to have to flash back to stock ROM and try reinstalling fasty iii again? This seems all so tedious lol...
OR is there a way for me to flash back to Fasty II without having to go back to stock rom? or without having to access the recovery screen?
Thank you^
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
studacris said:
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
Click to expand...
Click to collapse
Thank you for the info!
Looks like fasty III is a GB based mod after all...I guess I should read up more on the rom before installing lol....I did not expect the dev to go from froyo to gb -_-
I was thinking of using your previous post for the one click gb bootloaders only....but it seems a little iffy and I can't afford to hardware brick the phone lol...
Makes me wonder tho...is it really THAT risky to flash bootloaders? It would make things simpler if i could just flash the gb bootloaders and go from there....
the whole flash should take less than a minute, where the actual writing takes only a few seconds...but if you were to lose communication in that awful window then it would be bad day.
But that is a small window, and if you have never had connection issues you should be ok if Odin tends to be iffy, you van try heimdall I've heard that works better for some.
Still haven't tried flashing the bootloaders because i'm scared of the possibility of hard bricking my phone... If worst case scenario was to happen and it gets hard bricked....are there any options to restore that phone? or is it just paper weight after?
Also until I flash those bootloaders there is no way to back up my phone or anything?
Thanks for all ur help btw!
another issue i am having is that the phone seems pretty laggy after installing this rom...even with tegra overclock premium and tweaking it up to 1252mhz 1275mv 1100mv setting...it still seems laggy when opening sms etc....is this just the results of a bad rom install? also battery life seems crappy....even after doing the battery recalibration...of course i couldn't wipe the battery stats since i cant get into recovery...
Hard bricks are recoverable by a hardware modification known as unbrickable mod, search for user Adam outler, or go to mobiletechvideos.com they both offer this service if you're not a soldering expert.
Battery recalibration does NOTHING the stats are reset everytime you charge to 100, and besides that they don't calculate your current battery level, just what's been using it, its what's used in settings> about phone> battery use. It has nothing to do with extending battery life.
oh lol...i have been reading all these threads where people are talking about how much their battery life improved after they did the recalibration and stat wipe ....well anyways I am going to attempt the bootloader flashing...I hope everything goes well! after that I want to try reflashing the fasty III ROM...
Do you have any recommendations as far as a good ROM for teh captivate? One that doesn't lag and has good gps & battery life? I would appreciate any help you can give.
Thanks!
I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
LOL OOPS thought i was in the dev section.... ignore..help below.
xCaptivateRx said:
I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
Click to expand...
Click to collapse
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
TRusselo said:
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
Click to expand...
Click to collapse
Very good responce...however after odin3 one clicking back to stock 2.1 eclair, I lost my clockwork mod folder that was on the internal SD, of course. Rookie mistake, I should've definately copied it on to the external SD card. Thanks for informing me of proper terminology. Also, after downloading rom manager and flashing, booting recovery, I can only access cwm through the rom manager, the three button fix doesn't work.
Why was this moved? I posted in general..
because you have a question/problem
rom manager is only used with 2.1 (for captivate). doesnt work on 2.2 or 2.3.X or 4.0.X
in all newer versions of android we "bake" cwm into the custom kernels we package into the custom roms. so there is no stock recovery and you dont need the update.zip.
dunno why you would flash all the way back to 2.1... EWWW.
in the dev section there is a sticky called odin master collection. use a newer stock rom. the master collection also has stocks versions, pre-packcaged with a custom cwm kernel so you can skip a step of getting it after going back to stock.
Do we know why this happened in the first place? Incompatible kernel? Is there a guide somewhere for moving from GB to ICS?
Sent from my SGH-I897 using XDA App
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Do you not have to flash back to 2.1 after having these problems? Right now my phone is at the soft brick screen, no button combo working. Not recognized by the computer either. I'm heading out to radio shack and make a USB jig in a bit. I'd love to just flash straight up to a gingerbread ROM if I can possibly get this thing in download mode. Anybody help a brotha out!
Edit: the sim is not activated, I just run it off Wi-Fi because big red is my carrier. This is my development phone. So I can't just KIES update to whatever the newest is.
Sent from my DROID X2 using XDA App
Any firmware should work, no need to go all the way to eclair...just flash gingerbread.
Don't think its been mentioned yet but when going from 2.2 to ICS, you have to flash the rom twice to get out of the bootloops. Sounds like you were at that point but when you flashed your nandroid instead of the ICS rom again, your phone must not have liked it.
aww.W.T.F? said:
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Click to expand...
Click to collapse
Not all ICS ROM's require GB bootloaders. I ran THS, and am now on vibranturk's AOKP and I came straight from 2.1
I think the issue was you're supposed to flash them twice. Well that fixed it for me. I dkbhave the gingerbread boot loaders now though
Sent from my SGH-I897 using xda premium
I went from bone stock Froyo 2.2 straight to THS ICS with no problems whatsoever. So some ICS Roms doesn't need GB bootloaders.
Sent from my SGH-I897 using xda premium
I'm on the same situation as the original poster: I'm on andromeda3 and now I want to upgrade to ICS. Right now my captivate has cwm 2.5.1.2 can I flash any ICS mod from there or do I need to do something else?
See this.... TRusselo's "Guide..." that is a Stickied Thread in the Q & A Forum.
I believe u will need the Gingerbread Bootloaders...
Sent from my SAMSUNG-SGH-I777 using xda premium