Hello, been lurking a long time, reading a long time, but now it seems I need to reach out for help.
I have searched and read through many many posts and still cannot get my captivate to enter download mode. Ive read posts that say its unbrickable and others that say if its got a soft brick your toast.
Currently no matter what I do i am constantly stuck at the "phone---!---pc" screen.
Ive tried the vol+ and pwr, vol- and pwr, vol- and vol+ and pwr, middle vol button and pwr, all three vol buttons and power. Ive tried every variation of releasing and holding different buttons after a power cycle. Nothing seems to work.
Ive also tried making a jig. Ive got a micro usb plug ive chopped up, soldered on (3) 100k ohm resistors - no go. Tried (3) 100k and (1) 1k - no go. The value jumps between 295k ohms to 300k ohms. Does it need to be 301k exactly? That would require more than (3)100ks as they are usually +/-5%.
Backstory: was running stock, flashed to Cognition 3.02. Didn't have any issues with cog, just decided to try something different. Decided to go with Serendipity 4.1.
Used odin (I897UCJF6-final-OCD-REV0, the only one i could find, all the links are dead) to flash back to stock. Stock ran fine for the 10 minutes it was on there.
Then used the one click root
downloaded rom manager, used rom manager to add clockwork.
Used clockwork to enter recovery mode
installed from zip (serendipity 4.1) - this failed the first time and it took me quite a while to re-enter download mode.
After serendipity was flashed it would consistently lock up around the 2min mark.
Got back into download mode via clockwork/rom manager in attempt to use odin again. This is where it all fell apart. Odin froze the first time around, pulled battery, did the whole show again. Flash attempt #2 failed again also. This is where I am currently at. Now all ive got is the ----!---- screen and nothing seems to work.
Am I toasted? Or is there something I simply missed during my grief stricken panic after being without a phone for 2 days.
Search jig go to radio shack
Same recommendation as above poster.
Go to Radioshack, spend a $1 and get it done.
Did it just this morning.
http://www.youtube.com/watch?v=D0aoabVtPJ8
What build is your phone, located under battery, mine is 1008
Just got it working.
I had made several jigs earlier. Followed several youtube videos and still couldnt get it. I had to fine tune it to 301k ohms exactly. Required about 5 resistors. Using three 100k ohm resistors did not work...
(model 1008 also)
jhaury said:
Used odin (I897UCJF6-final-OCD-REV0, the only one i could find, all the links are dead) to flash back to stock. Stock ran fine for the 10 minutes it was on there.
Then used the one click root
downloaded rom manager, used rom manager to add clockwork.
Used clockwork to enter recovery mode
installed from zip (serendipity 4.1) - this failed the first time and it took me quite a while to re-enter download mode.
After serendipity was flashed it would consistently lock up around the 2min mark.
Got back into download mode via clockwork/rom manager in attempt to use odin again. This is where it all fell apart. Odin froze the first time around, pulled battery, did the whole show again. Flash attempt #2 failed again also. This is where I am currently at. Now all ive got is the ----!---- screen and nothing seems to work.
Click to expand...
Click to collapse
I had the same issue, if you used that version of odin and you have a 1012 version of the phone then that's what caused the issue. I am on xda app so I cannot look through my posts, but click on my name and look at the posts and you will find some in a thread about brinking and I told some details that might help.
Sent from my Samsung Captivate with ParagonRC3 using XDA App
So whats the best thing to do here?
Your saying I cannot use Odin to revert to stock, I must use froyo 2.2. any other 2.2 rom (or something more specific)?
Or is it something to do with Serendipity?
jhaury said:
So whats the best thing to do here?
Your saying I cannot use Odin to revert to stock, I must use froyo 2.2. any other 2.2 rom (or something more specific)?
Or is it something to do with Serendipity?
Click to expand...
Click to collapse
If you are build 1008 you should be able to use odin, try another rom
Easy
1. Pull battery out.
2. Put battery in.
3. Hold volume buttons.
4. Plug in the usb cable.
5. Done.
Jordan, that wont work if he is in a restart loop like I was. The only way to get it working is to make a jig with 3 100k watt resistors and jig pins 4 and 5. Once it is in download mode, flash to froyo if you have a 1010 or higher version phone (This can be found under the battery, my version is 1012). If you have an older version then you can flash back to stock. There is an odin flasher that will flash you to froyo, I will just have to look for it.
I personally use paragonrc3 myself and it works great. My issue was very similar to yours. Once you get it in dl mode, try out stock froyo and see if it works. If that does then you can most likely use any up to date ROM.
Sent from my Samsung Captivate with ParagonRC3 using XDA App
I was able to get into download mode, it had to be 301k exactly.
I tried it again and my phone does not like Serendipity 4. Serendipity hangs completely and every time around the 2 1/2min mark. I went back to Cognition.
Version 1008, originally the 3 buttons and the usb cable worked, then they didn't, and now they still don't. But I've got the jig now so eh.
Related
I have a samsung captivate that I had Perception 9 on, I was disabling the lag fix and restarted my phone (the lag fix wasn't working properly). I was forced into the at&t world phone ghost loop and was unable to go into recovery or download mode with any form of the 3 button combination.
I went to radio shack and jimmy rigged a nice usb jig and was able to get into download mode from there. I downloaded the Odin one touch to revert back to stock 2.1, everything flashed correctly, but when it went to restart (after i got the green PASS in odin) I am still stuck at the AT&T world phone loop.
Any suggestions?
Stabfast said:
I have a samsung captivate that I had Perception 9 on, I was disabling the lag fix and restarted my phone (the lag fix wasn't working properly). I was forced into the at&t world phone ghost loop and was unable to go into recovery or download mode with any form of the 3 button combination.
I went to radio shack and jimmy rigged a nice usb jig and was able to get into download mode from there. I downloaded the Odin one touch to revert back to stock 2.1, everything flashed correctly, but when it went to restart (after i got the green PASS in odin) I am still stuck at the AT&T world phone loop.
Any suggestions?
Click to expand...
Click to collapse
Try this
Remove any cables from phone to PC
1. Shutdown your phone
2. Remove battery
3. Remove SIM card and any SD cards you installed
4. Start ODIN one click installed on your PC
5. Press both volume up & down together and keeping them pressed, connect the USB cable to PC
6. Your phone should go to download mode and ODIN should identify it
Now start and see.
Let me know what happens
If what luv2rip doesn't work try my method:
http://forum.xda-developers.com/showthread.php?t=889128
Stabfast said:
I have a samsung captivate that I had Perception 9 on, I was disabling the lag fix and restarted my phone (the lag fix wasn't working properly). I was forced into the at&t world phone ghost loop and was unable to go into recovery or download mode with any form of the 3 button combination.
I went to radio shack and jimmy rigged a nice usb jig and was able to get into download mode from there. I downloaded the Odin one touch to revert back to stock 2.1, everything flashed correctly, but when it went to restart (after i got the green PASS in odin) I am still stuck at the AT&T world phone loop.
Any suggestions?
Click to expand...
Click to collapse
I had a similar issue earlier today. When dealing with Odin it seems that the best method to use is the one luv2rip described.
In my case, my little buddy (phone) kept freezing on solid colored screens. So I decided to try a different PC... and BAMMM! Worked like magic.
.... maybe it still had some Voodoo left in there =)
I forgot to mention that I recently went from XP to Vista on the PC that gave me problems. Since the "upgrade" was made Ive had sooo many things malfunction. The PC wouldnt even acknowledging the phone was plugged into it =/
AstroLuigi said:
I had a similar issue earlier today. When dealing with Odin it seems that the best method to use is the one luv2rip described.
In my case, my little buddy (phone) kept freezing on solid colored screens. So I decided to try a different PC... and BAMMM! Worked like magic.
.... maybe it still had some Voodoo left in there =)
I forgot to mention that I recently went from XP to Vista on the PC that gave me problems. Since the "upgrade" was made Ive had sooo many things malfunction. The PC wouldnt even acknowledging the phone was plugged into it =/
Click to expand...
Click to collapse
Vista? Well there's your problem. Windows 7, enough said!
Sent from a phone somewhere in the universe
Also, check your phone's build # (under your battery). The 1010 build phones have problems with Odin 1-click because they won't accept JF6 firmware. Per reports from other users, they will only accept JH2 or above firmware.
If that is your issue, you can use the method posted by Breakin' Ranh to return to stock.
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
muleman said:
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
Click to expand...
Click to collapse
Hmm I'd say if the USB jig didn't work, you're not soft bricked. That's a hard brick.
What kind of USB jig are you using?
Was it a ROM or a kernel you flashed? which one, version etc.?
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
donation rewards for anybody that can help! lol this is depressing, my old captivate isnt this sensitive and has been through hell and back, but this SGS4g.... im dissappointed in.
Uninstall all the drivers for the phone make sure you have the right ones also, and try plugging it into a usb 2.0 slot then run it again, this seemed to work for me. I ran into the same issue I plugged in my jig but it gave me a black screen, but odin recognized it and I flashedthe kd1 update and it was fixed. Hope this helps
muleman said:
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
Click to expand...
Click to collapse
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Along with what krylon said, maybe a bad download, try download file again
Sent from my SGH-T959V using XDA Premium App
will do thanks guys, ill try it tonight and let ya know how it goes for me.
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
krylon360 said:
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Click to expand...
Click to collapse
youre the man.... Thanks much
muleman said:
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
Click to expand...
Click to collapse
Heimdall works at that same warning screen too. I've done it on my SGS4G.
I am confused..
sgyee said:
Heimdall works at that same warning screen too. I've done it on my SGS4G.
Click to expand...
Click to collapse
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
amishraa said:
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
Click to expand...
Click to collapse
If its currently in the state which I'm assuming..
-won't turn on, no sign of life period...
-plugging it in the wall charger won't even show the green battery status...
-won't get recognized when plugged into pc (or odin)...
-all combinations of buttons and battery pulling+usb cable plugging does nothing...
Yea I think its safe to say it went to a land far far away just like my friend's phone and only Samsung can revive it now.. Because I remember reading all the stories how everyone brought theres back to life so easily with the button combos or the jig usage, but those phones all at least showed a sign of life with that cable screen. But if its pitch black like I'm assuming then...
Same here. The jig didn't seem to work - I still got the cell + comp but odin worked anyway and reflashed stock. It's probably better to run Odin off a desktop if you have one.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. In most cases I have been able recognize the phone using odin. A few of the key steps that I have used to get the phone recognizable in odin are:
1. If the computer says "usb not recognized" when initially plugging in the phone, uplug it and plug it back in. Most of the time when I do this the phone is recognized as samsung device.
1b: If odin now recognizes the phone after running through step 1 I will try to flash the files again. it will usually fail after trying to load the flash files on the first try. I have to mess around with this process a few times and I can usually get a successful flash.
2. I had an case when having to deal with this problem yesterday. I was running through steps 1,1b and not having success. Odin was hanging, (I forget which step). I let it sit for about 10 minutes and was still hanging. I unplugged the phone with odin still hanging pulled battery, powered on, plugged back in. Odin, which was still open and still trying to connect, continued its already started process after plugging it back in!!! This was an accident to still have the odin running and trying to connect, but after reconnecting the phone it successfully flashed!
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
These kind of observations are especially helpful! I can concur that I get the same <phone..!..pc> error, when odin tries to flash and gets a write fail, however, I do not have the "re-partition" option set. I then have to run through my previously mentioned steps to try to get a successful flash.
My question is what can i do to keep odin from failing to write when flashing?? I have only been using PDA packages, with the exception of using discrete packages (pit,csc,phone,pda) when loading the 2.3.4 rom leak.
It seems like the flashing write error in odin in causing the <phone..!..pc> error quite often with different flash processes. Does anyone have a solution to what might be causing this write error and what can be done to prevent this whole cycle? If so I sticky or new thread might be useful for other users. It has caused to have to warranty my first phone, urrrg!
Scariest feeling ever........ Not seeing your phone come up on Odin.
Sent from my SGH-T959V using XDA Premium App
Woops ahahahha. Was talkin to my friend. SOrry!
fvnktion said:
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. ..... [cut] ......
Click to expand...
Click to collapse
I had the same issue yesterday, when I tried to flash KD1 vanilla (stock) ROM
using ODIN, it failed the first 4 seconds, it boots into fuzzy looking screen and
that's it, every time I tried to boot it the fuzzy screen fades away to pitch black.
there is 2 possibilities that messed up the whole thing for me:
1) Bad ROM.. (i.e, can't be used with ODIN) although some members said it works
but don't know if there anything special to do before hand, if I want to downgrade.
2) Samsung Kies' fault, I installed just right before I used ODIN, and told me my
device is not registered.. hmm.
It could be both cases, but I suspect Kies the culprit, I had to uninstall it, and
uninstall the drivers came with it, installed the drivers found here in these forums,
and Odin recognized a COM port, although black screen on the phone, flashed
to KH1 and I am back to business. phew..
GB is awesome, but I can't stand the weak WIFI issue even with the latest KH1
I have to stand 3 feet away from my router to get a solid signal, with froyo
vanilla rom, I was able to connect like 50 feet away. but that's another problem
not for this thread.
Heh funny thing I read today in some thread, there is a conflict between Kies and
Odin after the incident happened. my fault for not reading a lot, jumping the gun
almost cost me the phone :/
I was playing around last night with updating my phone with a different and everything was fine. Today, I installed the proper kernel and it installed and ran fine. I decided I would install a different kernel, one that has audio via USB for the dock and after I selected the file with Odin, I started the install and then I noticed Odin said something about it being finished and removed. Now I started my phone and it just sits at the screen that says Galaxy S. The phone will not start and I cannot get into recovery or download mode. I have tried every button combination I could find online. Does anyone have any suggestions on how I can get into either download mode to install the kernel again, or recovery so I can just install the zip to reload the software.
Have you tried a jig or adb to get into download mode?
Sent from 234 Elm Street
I have never been able to properly get adb working, I know I am doing something wrong, but I actually just finally got it working. I was able to use One Click Root to have it restart my phone into recovery mode and I was able to reinstall the software and kernel. Everything is going good now, except I can't use the kernel I wanted to use because I don't know if it has CWM3.
This is the kernel that I actually wanna install.
http://forum.xda-developers.com/showthread.php?t=916233
You have SOFT bricked it which means you can get it out of it without JTAG at this point. Go to YouTube and search ODIN 1 Click and watch the video I made to help flash stock firmware.
Any updates OP?
Have you tried taking out and reinserting the battery then volume up, volume down while inserting your USB cable? That saved me one time. Then I bought a JIG.
Thanks for all the help, but I actually figured it out. I had forgotten I installed bootloaders and it changed the button combinations for Continuum.
Well, Ive been flashing roms for a while now and I have an issue with my captivate.
Lets start in the beginning. I had my captivate on THS ICS rom and It was going great. But my captivate isn't that great anymore. The power button is broken, but I was able to go around that. (Sidenote: It turns on when I plug in the battery.) Anyway, I wanted to go back to stock because I did have the right bootloaders. (I couldnt get into download mode with the button combination. I thought it was the bootloaders fault. Im I wrong?) I wanted to switch to I9000 bootloaders but I had to start fresh. But before all that, I noticed that while I was on ICS rom, I was unable to go to download mode. I used to before, but it magically disappeared (I know it didnt, I know I did something to it but I don't quite remember when it happened.) So I was unable to flash a new rom, if I wanted to.
A couple of days ago, I bought a jig and it worked! It took me straight to download mode. So I decided to get my Captivate and make it go back to stock. So I opened Odin, it found my Cappy and I clicked start. But, it stopped at factoryfs.rfs. I waited a half hour and nothing. So I unplugged it and now it won't turn on. But it can still go into Download Mode and be seen by Odin but it just wont finish. I tried both odin one click and the regular odin. I looked everywhere for more than six hours and nothing came up. Please guys, if anyone knows what I can do to fix it, please reply.
I might have missed something, but just ask if you need any more info. Please help me.
Edit: I forgot to add this:
While I was on the ICS rom, I switched over to CM7 to see if the process of going back to stock would be easier. Thats when I tried to flash stock. It didnt work as well as I thought it would.
And I knew that I didnt have I9000 bootloaders because I installed the Icy Glitch kernel and each time I tried to have DIDDLE on it would go to deep sleep mode and I was unable to wake it back up.
As long as you can get to download mode you are fine. Try flashing a different stock from. Or using Hiemdell
I've tried both odin and Hiemdell. But with Hiemdell, it would always tell me that I dont have the drivers installed. So, it installs it for me. Even with the drivers installed, it keeps telling me that I dont have the proper drivers installed.
I have had this exact problem, where a bricked captivate can get into download mode but when restored to stock through a one-click, it freezes on the factoryfs.rfs. However, in my case after freezing at this stage, the phone was completely inoperable, and could not even enter download mode, so I am suprised yours could.
What works for me is to remove the battery, wait for a few seconds, put the battery back in, use the usb jig to enter download mode, and then WITHOUT the phone plugged into the pc, download and open this one-click file http://http://forum.xda-developers.com/showthread.php?t=731989.
Once the odin one click is open, plug the usb cable into the pc, and then into the phone. This one-click has never failed me. Hope this helps.
Ok, now it passed. I don't know what I did but now its back up and running. But now it boots up into recovery. I can't select anything because my phone's power button is broken. What do I do?
Juiceboy125 said:
Ok, now it passed. I don't know what I did but now its back up and running. But now it boots up into recovery. I can't select anything because my phone's power button is broken. What do I do?
Click to expand...
Click to collapse
Depending on the CWM recovery you're in, you can sometimes use the search capacitive key to do the same thing as the power button will do.
I had the same problem you had with Odin stopping on flashing a file, turns out I was using a third party USB cable. I switched to the USB cable provided by Samsung when I bought my cappy and problem solved. Hope that helps.
Sent from my SGH-I897 using XDA
Finally!
Well, I got my Cappy up and running again. While I was stuck in the CWM I just decided to install Gingerbread using a One click and it worked. Now I'm back to CM9. Thanks guys for the suggestions. I guess I just needed to wait and double check everything.
Hey there, apologies in advance if I have submitted this thread in the wrong section. I really looked as hard as I could before posting.
Well I rooted my phone, got super user on there, then got clockworkmod red, and then attempted to put the ice cream sandwich mod on my phone, thats where everything went sour. Phone would not go past screen that says samsung. I tried a few times to get it to go past that point, and just nothing. I then attempted to use odin to have my phone put back, but now I cannot even get the phone to open up clockworkmod.
To put it very simply. The only thing I have access to now is the download option (holding both volume up and down while inserting the usb cable from the computer) I have searched the internet high and low for something to run through odin to put my phone back to the way it was. I keep coming up with dead links and long dead downloads. I was able to use the gtg ultimate unbrick, but all that managed to accomplish was to have my phone say at&t instead of rogers.
Im still at the screen that says samsung, with no access to a recovery menu at this point. I only have the download option.
Can anyone help me salvage my phone?
edit: I appear to have been able to reput clockworkmod back on the phone with odin. Thats all I have been able to do.
When flashing any ics Rom/port from.gingerbread/red recovery you will need to double flash...I'm seeing a lot of people.with bricks lately and I think the problem is they are not reading enough before flashing ics...
So you have cwm correct? Boot into cwm by holding volume up down and power button. If you have no roms hen go to mounts and storage and mount USB then plug it into the pc and copy over the Rom...if its gingerbread Rom.just one flash...if its ics then flash, you will get stuck on Samsung screen so boot back into cwm...you will either boot into a blue or some distorted rainbowy cwm...just reflash he Rom
If you can't do that...then idk what else to do as I don't know much about rogers phones and what is and isn't compatible with them...but u would suggest qksters heimdal one click back to stock uclb3...its always worked for me...but not sure if it will work with rogers...
Sent from my HTC PH39100 using XDA
Mytheos said:
Hey there, apologies in advance if I have submitted this thread in the wrong section. I really looked as hard as I could before posting.
Well I rooted my phone, got super user on there, then got clockworkmod red, and then attempted to put the ice cream sandwich mod on my phone, thats where everything went sour. Phone would not go past screen that says samsung. I tried a few times to get it to go past that point, and just nothing. I then attempted to use odin to have my phone put back, but now I cannot even get the phone to open up clockworkmod.
To put it very simply. The only thing I have access to now is the download option (holding both volume up and down while inserting the usb cable from the computer) I have searched the internet high and low for something to run through odin to put my phone back to the way it was. I keep coming up with dead links and long dead downloads. I was able to use the gtg ultimate unbrick, but all that managed to accomplish was to have my phone say at&t instead of rogers.
Im still at the screen that says samsung, with no access to a recovery menu at this point. I only have the download option.
Can anyone help me salvage my phone?
edit: I appear to have been able to reput clockworkmod back on the phone with odin. Thats all I have been able to do.
Click to expand...
Click to collapse
If u can get to dl ur fine
Sent from my SAMSUNG-SGH-I717 using xda premium
http://forum.xda-developers.com/showthread.php?t=1331381
Use this link/program from download mode to get to stock 2.3.6.
Wait, if you can get to download mode, you can reflash JScott's option C from here, then get into CWM red, flash the ICS of your choice, reboot into CWM blue (press and hold vol up/vol dn/power 5 seconds when stuck at sammy screen), wipe data/cache/dalvik, reboot and you should have ICS.
I understand that some people will never get "it", but reading the entire post for flashing/modding firmware is a MUST.