Today I updated my phone using kies. After the update was done the phone tried to boot but it couldn't get past the screen that says "Galaxy S GT-I9000".
So far I have tried to enter recovery/download modes, with no success.
Tried to connect the phone on my computer*, which recognized it (you could hear the "bleep" sound windows makes when a device is connected through usb.) but it didn't appear at Computer menu. Also kies recognized that there was phone connected but it keeps saying "Connecting" under Connected Devices tab.
*I'm using 64bit Windows 7 Ultimate
You'll need to either build or buy a Jig to get it into download mode and then you can reflash with Odin.
Did you ever use a custom rom on the phone? I assume not, but want to make sure.
If not, then you at least have warranty (don't you?) and can send it back for Samsung to revive your phone. Should you consider this, it would probably be wisest to not even try to repair your phone yourself.
However if you want to, here are three tips I found:
1) Connect your phone to your computer, open adb and type 'adb reboot download'. Your phone should reboot into download mode.
2) Originally posted here with a link to the mentioned ZIP: http://forum.xda-developers.com/showthread.php?t=728754 (look under "Manual Method")
For people that don't have the 3 button combo i made a script and a quick tutorial for doing it with ADB
ADB reboot recovery:
a) Download the easy reboot recovery.zip script and unzip it somewhere
b) In your phone's settings make sure USB Debugging is on (in settings -> applications -> development)
c) Connect phone with USB cable to pc
d) Wait until all the drivers are installed
e) Start reboot recovery.bat
f) The phone will now start in recovery
g) Follow step 7 of the normal tutorial
- If this does not work make sure USB debuging is enabled, kies is totally closed, the phone is connected and all the drivers are installed
3) This is from androidforums.com:
- Plug USB cable
- Remove battery
- Press AND HOLD volume down, power and menu key at the same time
- While pressing and holding the mentioned buttons, reinsert the battery (quite fiddly, I know)
- Let go of the buttons and you should go into Download mode.
Please tell me if anything helped.
Thanks for your help guys!
A.G. said:
1) Connect your phone to your computer, open adb and type 'adb reboot download'. Your phone should reboot into download mode.
Click to expand...
Click to collapse
Didn't work, adb gave me error "device not found", which would probably mean that the device isn't properly connected to my computer even though Windows did that bleep voice.
2) Originally posted here with a link to the mentioned ZIP: http://forum.xda-developers.com/showthread.php?t=728754 (look under "Manual Method")
For people that don't have the 3 button combo i made a script and a quick tutorial for doing it with ADB
ADB reboot recovery:
a) Download the easy reboot recovery.zip script and unzip it somewhere
b) In your phone's settings make sure USB Debugging is on (in settings -> applications -> development)
c) Connect phone with USB cable to pc
d) Wait until all the drivers are installed
e) Start reboot recovery.bat
f) The phone will now start in recovery
g) Follow step 7 of the normal tutorial
- If this does not work make sure USB debuging is enabled, kies is totally closed, the phone is connected and all the drivers are installed
Click to expand...
Click to collapse
This is something I didn't even try because I can't turn my phones USB debugging on. (can't access my settings )
3) This is from androidforums.com:
- Plug USB cable
- Remove battery
- Press AND HOLD volume down, power and menu key at the same time
- While pressing and holding the mentioned buttons, reinsert the battery (quite fiddly, I know)
- Let go of the buttons and you should go into Download mode.
Click to expand...
Click to collapse
Didn't work.
And no I have never used any custom ROMs on my phone. Probably taking my phone to the place I bought it from and see if I can get it fixed under warranty. Unfortunately that means I'm not going to have a phone to use for a while since I have no time to go there until sometime next week. If I can't get this thing fixed under warranty I'll probably just order a JIG and fix it that way.
If someone has more ideas please post them anyway, I want to fix this problem as fast as I can.
maybe a stupid question but you know how to get in dowload mode......
vol. down / home / power....
here are samsung drivers for your phone, uninstall everythin having to do with kies and install samsung drivers.
see if you can connect to ODIN now.
http://dl.dropbox.com/u/19506141/flash en drivers/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
(I'm reposting this thread per request. All credit and thanks goes to the original OP and to others that helped compile and write up this helpful info.
This is basic knowledge for the experienced Captivate user, but a treasure of info to the novice user.
Please keep all posts thread related. Thanks.)
***There are three parts to this thread - How to get into download mode, how to get into recovery mode, and how to solve problems connecting your Android device to your computer. I think you should be able to find where each one begins without too much trouble.***
----------------------------------------------------
GETTING INTO DOWNLOAD MODE
----------------------------------------------------
"Just get into download mode and..."
Ever find yourself with a phone that's misbehaving, and you can't seem to figure out how to get it to download mode?
Here's a list of things to try (many thanks AdamOutler and Pirateghost), sorted in a "where are you now" setup:
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol+ and Vol-, then insert your USB cable.
- Press and hold Vol+/Vol-, Insert Battery, Insert USB cable
- Press and hold Vol+/Vol-, Insert USB cable, Insert Battery
- Insert battery, then press and hold Vol-, then insert your USB cable.
- Press and hold Vol-, Insert Battery, Insert USB cable
- Press and hold Vol-, Insert USB cable, Insert Battery
- Use a 301Kohm jig between USB pins 4-5 (can be manufactured jig or homemade chain of resistors)
FROM A BATTERY CHARGING STATE
- With USB cable inserted into Android device, press and hold Vol+/Vol-, then press Power
- With USB cable inserted into Android device, press and hold Vol-, then press Power
- (Advanced Method) Use UART, and during battery charging, type "reboot download"
FROM CLOCKWORKMOD RECOVERY MENU
- Position the cursor (highlighted selection) on "Restart device", Plug in USB cable, press and hold Vol-, then hold Vol+, then press power
- (Where available) Use the "Reboot Download" option in the "Advanced" menu
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot download"
- (Where available) Use the rom's power menu option to reboot into download
- From a terminal, type "su", then "reboot download"
- Download the app "quickboot", follow the app directions to reach download mode.
ADVANCED METHODS - REQUIRE HARDWARE MODIFICATIONS OR MORE IN-DEPTH TECHNIQUES
I'm presenting these largely unedited, as I don't want to incorrectly type an important detail of something that I don't understand myself.
- Apply UnBrickable mod to your device, then remove the battery, insert the battery, and click the "Download Mode" button on the computer
- Use UART (619Kohm resistor between USB pins 4-5, D+=RX, D-=TX, 192500bps 8n1 comms), press and hold ENTER while booting, then type USB
----------------------------------------------------
GETTING INTO RECOVERY MODE (CWM RECOVERY)
----------------------------------------------------
(Thanks to TRusselo for writing this out)
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol+ and Vol-, then press and hold power. hold all 3 for 5 seconds.
- Press and hold Vol+/Vol-, Insert Battery, hold power. hold all 3 for 5 seconds
- Press and hold Vol+/Vol-, hold power, Insert Battery
- Insert battery, then press and hold Vol+, then press and hold power. hold all 3 for 5 seconds.- Press and hold Vol+, Insert Battery, hold power. hold all 3 for 5 seconds- Press and hold Vol+, hold power, Insert Battery
FROM A BATTERY CHARGING STATE
- With USB cable inserted into Android device, press and hold Vol+/Vol-, then press Power
- With USB cable inserted into Android device, press and hold Vol+, then press Power
- (Advanced Method) Use UART, and during battery charging, type "reboot recovery"
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot recovery"
- (Where available) Use the rom's advanced power menu (long press power in android OS) option to reboot into recovery
- From a terminal emulator, type "su", then "reboot recovery"
- Download the app "quickboot", follow the app directions to reach recovery mode.
----------------------------------------------------
UNIVERSAL FIRST STEPS FOR CONNECTION ISSUES
----------------------------------------------------
So you've got Odin/Heimdall up, the phone's in download mode, it's connected to the computer, but Odin/Heimdall is saying "What phone?". You've tried jiggling the handle, checking the blinker fluid levels, and even using the board stretcher, but the Android guy is smirking at you from inside that yellow triangle.
Although it is possible that there is something else at work that's preventing your phone from connecting, I would suggest trying these "universal first steps" to see if you can resolve the connection issues:
1. Turn off both devices - and I do mean full power-down. Go ahead and pull the phone's battery, if necessary.
2. Disconnect your phone from your computer at all points - USB out of phone, USB out of computer.
3. Start up your computer. Don't touch it, don't do anything to it. Let it fully boot and completely settle.
(Obviously, log in if it's necessary, but then let it finish booting before moving on to step 4.)
4. Start up your flashing program (Odin/Heimdall). Let that get completely started and settled.
(If on Vista/Win 7, make sure to "Run as Administrator" in the right-click menu.)
5. Connect your USB cable to a different port than the one you last had it connected to.
(If you're on a Windows desktop, the ports in the back of the computer are generally more stable and should be used. If you're on a laptop, use USB port #1)
Do not connect the phone to the cable yet.
6. Start your phone in download mode. Wait until you see the yellow triangle Android guy with the words "Do Not Turn Off Target".
7. Connect your cable to the phone. Let it sit until Odin/Heimdall recognizes it (which should only take a couple of seconds).
If, for some reason, Odin/Heimdall doesn't recognize the phone at this point, here are a few more things to check/try:
- Repeat steps 1-7 above, making sure to change USB ports. As dumb as it sounds, sometimes the phone or computer just doesn't like particular USB ports.
- With everything still up, switch USB ports.
- Try a different OS (if possible) - sometimes Ubuntu will recognize what Windows won't, and vice versa.
- Try doing this on a different computer - again, different OS, different USB ports, they're all links in a chain and sometimes you'll come across a configuration that doesn't have the weak link.
- Try a different cable. I've had a case where I couldn't do any flashing with one cable, but everything was rock-solid and smooth on the same machine with just a different cable.
- Fully uninstall your drivers, reboot the computer, reinstall the drivers, power down, and then start again from step 2. Sometimes faulty drivers are the problem.
- Remove the drivers for the flashing program you're not using. So, if you're using Heimdall, remove the Odin drivers. If Odin, remove the Heimdall drivers. This will eliminate any potential conflicts.
----Quick explanation of Heimdall / Odin driver conflicts----
If you've used both Heimdall and Odin on the same computer for flashing, you may have noticed that they don't interact nicely when it comes to drivers and ports. What's happening is that when Odin gets the setup it wants, it will overwrite any and all drivers for your phone assigned to any of the USB ports. When Heimdall gets its setup, it will write to the specific port that you have your phone plugged into.
So, to illustrate, assume you have 4 USB ports on your computer. If you use Odin's setup, it will make ports 1-4 "Odin ports". If your first setup is Heimdall, and you put your phone on port #1, you would have port #1 as a Heimdall port with 2-4 unassigned.
Where it gets tricky is if you use Odin or Heimdall after using the other one. Let's say you have a Heimdall port #2 and decide to flash using Odin. Once you set up Odin the way it wants to be set up, you will overwrite all the ports as Odin ports. This means you have no more Heimdall port #2, just Odin ports 1-4. If you use Heimdall after Odin, it will only reassign a single port. So if you had an Odin 1-4 setup and flashed using Heimdall on port #3, you would have Odin ports 1,2, and 4, and Heimdall port #3.
Confusing yet?
Here's the basic rules for planning when using Heimdall and Odin:
- If you're starting from scratch, Odin will write to all ports. Heimdall will write to the port your phone is plugged into.
- If you previously used Heimdall and are now using Odin, all the ports will become Odin ports. To use Heimdall again, you'll have to reinstall the Heimdall driver to the port you're going to use.
- If you previously used Odin and are now using Heimdall, only the port you're using with Heimdall will become a Heimdall port. If you can remember which port you're using and make that a dedicated Heimdall port, you can have the other ports remain Odin ports.
Images
View attachment 1431380 Download Mode screen
View attachment 1431385 Alternate Download Mode screen
View attachment 1431370 (Pre-Gingerbread Firmware upgrade fail screen) Possible alternate download mode. If not, then u need a Jig.
View attachment 1671424 No i897 Gingerbread Bootloaders installed screen. Heed all warnings about flashing bootloaders and then flash the i897 GB BLs to resolve this issue. See post #7 below for info on where to get the BLs.
USB Drivers
Device(Install),USB Driver (Software) (ver.5.02.0.2), Win XP/Vista/Windows 7, Released Jul 15, 2010
Title AT&T SGH-I897 (Captivate) USB Drivers (5.02.0.2)
Applicable Model SGH-I897 (Captivate)
Carrier or Corporate Customer AT&T
Description USB Drivers for use with Media Sync and Mass Storage
Downloaded directly from Samsung Support for SGH-I897...
View attachment SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip
Flashing Tools
Heimdall command line tool, Heimdall Frontend, Drivers...http://www.glassechidna.com.au/products/heimdall/
Note: Heimdall uses its own specific USB Drivers.
Odin Flashing Tool...Odin3 v1.83
Note: Odin uses the Samsung Captivate USB Drivers.
I'm having an issue that resulted from an attempt to flash a rooted kernel. I'm not sure what happened, but the result is an inability to enter recovery mode, and no connection in download mode. Normal boot ends in a screen resembling a scrambled cable channel that reboot loops. I do have heimdall and Odin installed at this point, but i had connection trouble before I tried Odin. I have done some searching but found nothing describing the static screen. If you require more info, I'll provide what I can.
Sent from my Amaze 4G using xda app-developers app
That pixelated screen means u do not have the i897 Gingerbread Bootloaders installed. So u need to flash the Odin or Heimdall i897ucKK4 one click WITH Bootloaders included. Then u can proceed to use regular Odin to flash the .tar version of the KK4 Corn Kernel so that u can get Root and as well have CWM Recovery that is included in that kernel, so then u can proceed with flashin a dev rom of ur choice.
See my signature link below, if u r on a pc or in a web browser, for the links u will need as far as what i just instructed u should do. :thumbup:
The [Utility] KK4 Easy Root by Red_81 that is in my sig link, will guide u to gettin Root and KK4 Corn Kernel. Be sure to hit Red_81's thanks button.
Sent from my SGH-I777 using xda premium
Added an image of the screen that occurs when the i897 GB Bootloaders are not installed. See post #2.
The safest way I have for those who need to get the i897 GB BLs to flash is here... Go to this post and use this Heimdall One Click ---> I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param, and Repartition-Heimdall One-Click.
That's the screen. Thank you very much for your data rich reply. I will give it a go when time permits.
Sent from my Amaze 4G using xda app-developers app
You are awesome. The heimdall one click with bootloader worked like a charm. It was as easy as one click! Thanks again.
Sent from my Amaze 4G using xda app-developers app
Thanks for all the info, however some of the topics placed in various links need an ajustment for Linux.
Don't waste your time using Ubuntu because java is not natively supported anymore for the 12.10 release.. I suggest using opensuse or fedora and visiting java.com to download the rpm as deb are not supported and this is much easier for a newbie to do than to build a deb package from sources..
Just a little tip, if you want to run hiemdall, you will need java runtime somehow, opensuse I know personally 12.2 came with an option to install the java dev kit, which is just as good as java runtime and includes a runtime with it. This will allow you to install android dev kit, another good tool to have for modding.
Sent from my SGH-I927 using xda premium
Samsung Captivate wont completely boot
Hello, I'm having a problem with my Samsung Captivate. It loads all the way to the last screen where the S comes into formation and it says Galaxy S at the bottom, then it restarts and repeats the entire startup. I used "I897UCKK4 CONTAINS Bootloaders" to see if it might fix the problem, but it's still doing it. Any suggestions please? thanks
Maybe a bad download. Try a fresh download. One without bootloaders. Since the bootloaders should be flashed to ur phone.
And try a different micro usb/usb cable. Also check in the phone's micro usb port to make sure it is free of dust, dirt, etc. And u could also try a different usb port on ur pc.
Make sure ur battery has a good charge as well.
Hope one of these helps.
Sent from my SAMSUNG-SGH-I747 using xda premium
Install ClockWorkMode
How to install ClockWorkMode on my Galaxy Captivate i897 mobile?
""Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system ""
This is not working for me. Can somebody help me on this issue.
Plz see and use TRusselo's Guide that is a stickied thread in this forum.
Basically u need to use Odin or Heimdall to flash a kernel that has cwm recovery baked in.
Sent from my SAMSUNG-SGH-I747 using xda premium
My experience to get back from soft brick
Just want to share my experience here:
I had captivate with CM10 installed and decided to flash it back to stocked rom and trade it in for new HTC One ($100 ,
First I flashed it with Odin and somehow when it reboot, it stuck at AT&T page (flashing every 3~5 seconds), and I can't get it back to download mode through all the key combinations recommended 4-2ndtwin without success (I did try all of them).
Then I got a 300kOhm resistor (measured it and showed 298.9kohm), without the hassle to make the USB jag (which was a mistake), use the legs to touch the 4 and 5 of Cappy's USB port, after multiple tries (average about 3 minutes effort that have one success), I was able to get to download mode.
I then tried to flash the "I897UCKK4 Odin One Click - Stock, CONTAINS Bootloaders, Re-partition, Full Wipe" got from this post:
http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
The flash stuck somehow in the middle of flash, it was probably after partition (not 100% sure though) per odin message. I waited for about one hour and decide to pull the battery out. When I reboot, it was not showing AT&T logo, instead went straight to phone --!-- computer screen.
Some posts suggested it is another download mode, but for me, it was not in download mode. Odin no longer responsed when I plug in the phone. Again, I tried all the combination in previous post to get it back to download mode, as well as tried multiple times (should be more than 10 successful trys) using the resistor, it all went back to same phone --!-- computer picture.
I almost gave it up but decided to give it last try by making the jag, it was not that hassle at all after I used a cheap car charge line (it was not even need to be cut, the plastic on the USB line was kind of like clamp shell, after removing four small clips, it completely dissembled and show the 4 and 5 legs, I wished I should have done it earlier!).
Then I connected the 300kOhm resistor to 4 and 5 legs of the USB line, put battery back to phone and plugged the jig into the phone, it still showed me the phone --!-- computer picture, and my computer was not response at all! It seems I had exhausted all the options and may have to give up the $100 trade-in credit.
I decided to switch the sequence and gave it last effort. Pulled the battery out, plugged in the jig, and put back the battery. Guess what, download mode appeared! I then was able to flash the stocked rom (the same rom I just mentioned) back to the phone and everything went well this time! I now can see the $100 gift card from HTC :laugh:
Thanks for all the information for this forum and you guys are great!
This thread and all the wonderful people in it have been very helpful
CM10.1 Boot Loop / Computer Won't Recognize In Download Mode
Hello all -
I think my Cappy has given up the ghost, but I thought I'd throw this out there to see if anyone had an idea.
Yesterday my Captivate (running CyanogenMod 10.1 M3) started looping the boot up screen. It's done this before, and when I just leave it, it will eventually start up normally. Not anymore. Plugging it in to charge starts boot looping the battery charging screen. I can't get it to reboot into recovery. I have tried every possible combination listed above. It just boot loops faster.
No problem, let's just flash the ROM again, right? It still goes into Download Mode fine. Except. I can't get a computer to recognize it at all. PC running Win 7 gives me an "USB device Not Recognized" error. Neither Odin nor Heimdall can see it. I have tried as much of the advice given above in this thread as I understand. I have tried all the different USB ports. I have tried three different machines. I have tried Win 7 and Mac OS X. I briefly tried Ubuntu but I'm too much of an Ubuntu noob to get heimdall running on it. I have tried two different cables. I have taken out the SD card. I have uninstalled and reinstalled the Samsung USB drivers. I don't know how to uninstall Odin and Heimdall drivers. Maybe someone can help me with that?
Thanks in advance for your thoughts.
Hey is there anyway to get captivate into download mode from a completely bricked state, something happened when my Odin finished and my phone screen won't show anything, i mean it just remains black.
Thanks in advance.
dragonfire2008 said:
Hey is there anyway to get captivate into download mode from a completely bricked state, something happened when my Odin finished and my phone screen won't show anything, i mean it just remains black.
Thanks in advance.
Click to expand...
Click to collapse
Won't show anything doesn't always mean bricked. Try this http://samsungcaptivate.wikia.com/wiki/Putting_the_Phone_into_Download_Mode.
Yeah none of those worked, I have tried everything to get the screen to show SOMETHING. Won't turn on, no download mode, no recovery, no nothing, just a black screen.