yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] sparker366:
Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.

If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.

Steps

1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.

2: When the att screen comes on your pc should make a notification sound that the device is connected.

3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.

Mileage may vary but should work.

This has saved me a few times.
[Captivate Android Development] bulletproof1013:
STICKY
[Captivate Android Development] bobbylx:
Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.

Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.

I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.
[Captivate Android Development] creepyncrawly:
+1

This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.
[Captivate Android Development] Pirateghost:
This thing is getting buried in the BS posts....BACK TO THE TOP!

definitely sticky
[Captivate Android Development] tweek1020:
Bump Bump Bump

Great Info
[Captivate Android Development] bobbylx:
Updated original post with extra info.
[Captivate Android Development] bobbylx:
Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.
[Captivate Android Development] HBeezy:
Thanks, great info.
[Captivate Android Development] Scottbg1:
FWIW........

I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.

One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.

Thanks for the post, my vote for sticky as well.
[Captivate Android Development] spartan07:
+1 sticky
[Captivate Android Development] bobbylx:
Moving this to the top. More questions in QA that can be helped by reading these tips first.
[Captivate Android Development] othermark:
I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.

The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.

Test md5 checksums on the source and this file and make sure these match.

(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).

This will ensure your USB connection is stable enough for long, error free transfers to the phone.

Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.
[Captivate Android Development] bobbylx:
Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.
[Captivate Android Development] ootz0rz:
Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply :) Thank you!
[Captivate Android Development] balishared:
thanks for the reminder

there's so many steps to install a rom...

specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!

another good reason flashing stock with odin before flashing new rom ;)
[Captivate Android Development] mattbeau:
I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.
[Captivate Android Development] DOAlaboratories:
Let's keep this bumped.
[Captivate Android Development] xredjokerx:
love it. *thumbs up*
[Captivate Android Development] Verrigan:
I find it funny that the flaming in every other General thread in this section is not in this one. ;)
[Captivate Android Development] sschrupp:
this should definitely be a sticky.
[Captivate Android Development] ice3186:
why isn't it already!

+1 for this, it would save years of time!
[Captivate Android Development] Belaflek:
Amen to that bruddah
[Captivate Android Development] ootz0rz:
Is making a nandroid backup not sufficient to cover that as well?

Sent from my SAMSUNG-SGH-I896
[Captivate Android Development] lbbo2002:
I had to use this info recently so lets Sticky this beasty.

Personally if you have odin open, hold both volume buttons at the same time and plug in the USB to the phone it jumps right in to download mode every time (even with the sim and ext SD card in).

Anyone having issues with master clear.... seems the last few tries are not working for me, Weird.
[Captivate Android Development] kaiser_tytnii:
if anyone could possibly help, it'd be much appreciated

my problem is described here... :(:(

http://xdaforums.com/showthread.php?t=857538
[Captivate Android Development] hillbilly12345:
Problem reinstalling packages

this is somewhat related to your post and maybe you can help.

I receive the following error message when i try reinstalling packages from recovery screen running Froyo 2.2 on captivate

E:failed to verify whole-file signature

E:signature verification failed

Installation aborted.
[Captivate Android Development] malfuncion:
If you flashed the STOCK 2.2 ROM, via ODIN 1 click per say, the factory 3e recovery will not work with the Clockwork recovery. It cannot verify the signarture- the problem you have.

To fix this you will either need to flash some kernel from the threads here using the REAL ODIN (not 1 click) or you will need to flash another 2.2 rom from the factory 2.1 eclair (JH7).
[Captivate Android Development] NightVVulf:
Thanks man! This is some great info, I sure wish I had this before I had to take my phone back to AT&T.
[Captivate Android Development] slifer315:
I would just like to remind everyone that actually does read this before flashing to test if you have the button combination for recovery and download before flashing anthing to your phone. if you find out that you do not have the combinations enabled, you need to use the fix posted in the OP.
[Captivate Android Development] nappent:
I just tried this and it just keeps going into the AT&T Logo loop... I think I'm really screwed
[Captivate Android Development] CLShortFuse:
I suggest you add a section to say that you should get your unlock code while you're still on stock before jumping to 2.2 (which will wipe the code from your device)

I suggest SuperOneClick
[Captivate Android Development] tazman171:
Tried what?

It doesn't actually get wiped, there is a file that contains it in hex or something like that. I think there is an app for getting it from that file. But it's still a good idea to write it down with android ID changer or the app you mentioned. :cool:
[Captivate Android Development] CLShortFuse:
Yes, that file gets the code wiped to 0xFFFFFF in hex
[Captivate Android Development] tazman171:
I must have gotten lucky, I never lost mine. I do change it after every flash but it had been 5 or 6 cog froyos before I actually wrote it down when going to stock JF6. Copied and changed it with Android ID Changer and I suddenly had access to apps I hadn't been able to update for a while. I must have had it backed up somewhere that master clear, etc. hadn't touched it. :cool:

On the bricked note, last night I was flashing back to JF6 with Odin one click. About a quarter way into it windows decided that my samsung usb drivers should quit and disable my my flash. The phone screen went a real dim red and that was that. Waited for 10 min+ but Odin saw no device nor Windows, Win 7Pro 64 bit, for that matter. Pulled the battery and nothing, no battery charging graphic, no home button lights, vibration, NOTHING! So I fiddled with it, rebooted the comp to no avail.

My sim and sd were already removed before flashing so I resurrected my Tilt just in case and went to the forums.

I found a post somewhere (can't remember where, sorry) about just barely making battery contact with the contacts on the phone while holding vol +- and power down with the USB plugged in and Odin running to get some sign of life.

I did this for about 5 min after letting the phone sit for 30 secs or so with no battery or usb card and got 6 lines of red text to come up then disappear.

Kept doing the "trick" and after about 10 mins the phone suddenly came on in download mode! Yes! :D, flashed to stock then put Perception 8 non oc/uv on with no problems.

I wish I remembered who posted that but THANK YOU!

My phone acted 100% dead, no power, lights, etc. Battery was 100% before I tried flashing back to stock and out of over 20+ flashes I've never had this happen. So I guess even the dead captivate can rise, lol. :cool:
[Captivate Android Development] Pirateghost:
he wasnt talking about your android ID, he was talking about the UNLOCK code so that the phone can be used on other carriers
[Captivate Android Development] tazman171:
Well, I totally missed that part. And I did read the previous pages.

LOL, sorry CL wasn't trying to argue anyway. :o
[Captivate Android Development] yahooserious:
This happened to me last night and i had never been bricked before. This was a serious problem but the solution was close to what you tried.

What I was told to do worked each time i needed to bring it back into download mode cause of multiple stalled re-flashes.

the method should make it to the top of this thread too as I have been successful every time.

remove sim, memory card and battery. Hold Power button to drain any residual power. Start odin on your computer. Press the volume rocker ONLY. Plug USB into computer. Put Battery into the phone. DONE!

I was hard bricked with black screen and 6 red lines of text.

The above methood worked EVERY time (i couldnt get a complete flash on my desktop..so i tried on my notebook and flash went 1 time smooth as silk.)

Cheers and thanks to all the helping hands in this community XDA rocks!
[Captivate Android Development] tazman171:
Glad it worked for you too yahooserious. It took a while for me to get it to work as it was DEAD, but the hour of constanlty trying seemed better than the $300 or $400 option that was on the table.

The method you used for DL mode is what I always used when a flash "stalled" but mine was beyond that, it was lifeless as in no charge indicator, lights, buzzes, anything for a good 4 or 5 hrs. Never had that before but also never had windows dump my usb drivers while in the first stage of flashing to stock.

Just wish I could find the post where the guy was talking about lightly contacting the battery to the contacts repeatedly. I know that's what shocked the phone back to life as I had tried everything I could find in many different forums, but that was what got the red text briefly, 6 lines. I knew then that it wasn't hopeless. :cool:
[Captivate Android Development] 1tontomato:
I had this exact problem over thanksgiving weekend. My phone was was was hard bricked I was getting the "phone + computer" it took some effort to get it into download but I got it there and when I was recovering with odin the connection got lost the screen went blue and then nothing. It was dead totally unresponsive no charging or boot screen nothing but once I got a black screen with redlines. After a lot of attempts to revive it I gave up called ATT warranty for a replacement. Luckily I opted for the slow mail service and kept reading. Yesterday I saw the above post and now I can say "yes even now your phone is not bricked even though it does NOTHING"

step 1) first thing I did was charge the battery with my replacement phone as the bricked phone was no longer able to charge the battery

step 2) open odin1 click and hooked up the usb to the phone and computer no battery

step 3) inserted the battery holding only volume up+down

step 4) "BOOM" download mode and a happy dance
[Captivate Android Development] xdeslitx:
nevermind...took a gamble and it worked
[Captivate Android Development] tazman171:
Right on 1tontomato and xdeslitx! Glad it worked for you guys, great feeling when that download screen finally came up huh! :D Really glad to see this working for other people! :cool:
[Captivate Android Development] DroidAsk:
Hi all,

Please help me. I feel like an idiot. I did not set usb debugging mode before attempting to flash a voodoo kernel. Now I get the phone-!-pc screen all the time. I can still get into download mode though, but no luck getting into recovery. Is there anything I can do to save my situation?
[Captivate Android Development] silverslotcar:
Download odin one click jf6 then open it on your pc (assuming u have the right drivers installed) then put your device into download mode then plug it in via usb and flash.

sent from my cappy running Di11igafs Rom 2.5 overclocked at 1280 with JK4 modem!!!
[Captivate Android Development] DroidAsk:
Hi silverslotcar, my phone is the international version of galaxy s and not the captivate. I had my problem reposted in the correct phone model forum now but will this work for the international version of galaxy s too?
[Captivate Android Development] silverslotcar:
Nooooooo sorry. Its captivate specific.
[Captivate Android Development] DroidAsk:
Oh well.. thanks anyway silverslotcar. I should have been more careful and made sure I set to usb debugging before attempting to flash voodoo.
[Captivate Android Development] tazman171:
If you can get to download mode you're in great shape! Odin is what you need for your phone now. Odin is Samsung's flashing software and there are version for your divice. Now that your post is moved to the correct thread I'm sure you can find an Odin version that will work for you.

Read this page from the I-9000 thread;

http://xdaforums.com/showthread.php?t=810682

AND DEFINITLY THIS ONE;

http://xdaforums.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Recovery_Mode

Save that page and understand it and refer to it. Understanding the ins and outs will save you a lot of grief, like your current sitrep.

:cool:
[Captivate Android Development] malicenfz:
Thank you for this thread, I'm about to attempt to learn some basic commands on the SDK
[Captivate Android Development] avgjoegeek:
Added to the Q&A sticky - hopefully more people will read this before posting in the Dev/Q&A forums now.
[Captivate Android Development] bobbylx:
Nice. One of these days I'll add some images back to the original post showing how to add SDK tools to windows PATH.
[Captivate Android Development] reinbeau:
Please do! :)
[Captivate Android Development] CatalystWon:
Thank you CLShortFuse.:)

I'm looking for a pre-owned Captivate. It may have stock AT&T 2.2 on it (not sure). If so, does this mean I can't unlock it???

Any advice is appreciated!
[Captivate Android Development] BAleR:
for some reason I cannot get adb working, when i goto cmd and type in adb shell it says it is not recognized as an internal or external command, operable program or batch file

1) start-> run-> sysdm.cpl

this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.

2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.

3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:

4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.

5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.

I did that, i downloaded sdk, installed samsung drivers, put the sdk in C: named it SDK, I added ;C:\sdk\tools to the system variables reboot, and it gives me that error. can anyone help me with this please? I'm on winxp net4 framwork im not sure what im missing
[Captivate Android Development] Reynaldinho111:
Do you have the newest sdk?? If so open command prompt and do the following, hit enter after each line

cd\

cd AndroidSDK\platform-tools\

Then try your shell command.

In the recent sdk they moved adb from tools to platform tools.

sent from my beloved cappy!!
[Captivate Android Development] BAleR:
Thanks I just happened to read a txt that said that it moved, i updated the file and corrected it and works now. I do have a small question if you would be so kind, Im not sure what build my captivate is, how do I check for that? its on 2.2 and it says under system/about - Build Number: FROYO.UCKB1, and can I just use the superoneclick to root then go on to flash the GB BL and ROM?
[Captivate Android Development] oxlong27:
Your build number is under your battery
[Captivate Android Development] BAleR:
is it MODEL: SGH-1897?

or

0168?
[Captivate Android Development] Pirateghost:
neither......its a number representative of the build month/year

1006-1106

1006 = June 2010

1007 = July 2010

etc

1101 = January 2011

1102 = February 2011

etc
[Captivate Android Development] BAleR:
So its where the bar code is on the phone correct? if so, its 1010, can I just use the AIO tool box and go down the list?
[Captivate Android Development] Reynaldinho111:
Honestly you dont even need to root to flash to gb. Just read the how to flash to to stock gb thread (a couple times) basically if you follow the instructions its almoat impossible to go wrong, from there youre good to flash a custom rom. Ima look for the how to thread and post it up here unless youve already found it. If you have any questions just shoot me a pm man

sent from my beloved cappy!!
[Captivate Android Development] Udonitron:
Slightly on but off topic here.

Just bought a used Captivate for my Dad to usher him into the 21st century of cell phones (LOL) and the phone seems to have already been rooted etc however it has the AT&T World Phone logo on boot up and a VERY basic barebones TouchWiz interface without any of the Samsung widgets etc.

Is there a nice vanilla ROM out there of the TouchWiz skin without any of the bloatware etc?

Been reading all these threads but it seems the Sammy's are quite different from HTC ROMs etc.

Cheers in advance!
[Captivate Android Development] reinbeau:
There's Serendipity 6.4, people are pretty happy with that still, Froyo based, you'll have to theme it, however, to get the updated Swype, or Serendipity VII, which is Gingerbread based (see next paragraph), again, apply a theme to get the updated Swype. I'm sold on MikeyMike's ROMs, YMMV.

A friend of mine likes Apex. Most of the ROMs have gone to Gingerbread, which means you'll be flashing bootloaders. There's lots more in the Captivate Android Development section. Now that I think of it, the Cognition line of ROMs is supposed to be totally Captivate based (those others are I9000 based, I think), so that might be a good option - but again, it's Gingerbread.

Hope some of this helps! :)
[Captivate Android Development] Udonitron:
+1 for you, cheers man

It seems the phone has Cognition on it right now as the internal SD has Cognition 100.zip sitting in there.

Looks like TouchWiz but missing all the widgets etc.

By flashing bootloaders you are talking booting into recovery and flashing via that route, yeah?

That is what I am familiar with on HTC's.

Seems things are different with the Sammys and I want to make sure I know the route if I ever want to flash my S II.
[Captivate Android Development] reinbeau:
No, that's not what I mean at all. Going from one major version to the next on Android usually involves flashing bootloaders, which is separate from flashing the ROM. Froyo is Android 2.2.x. Gingerbread is 2.3.x. So, let's back the bus up. When you go into Settings/About Phone, what does it say under Firmware version?
[Captivate Android Development] Udonitron:
Haha no no, I understand that for sure.

The one I just bought is on Gingerbread (2.3.3)
[Captivate Android Development] reinbeau:
Then it must have thew new Cognition installed. I'd go to that thread and redownload whatever the most up to date version is and flash that. You can go to any of the GB roms with those bootloaders. I always read the first post of a thread, and then skim the last few pages - or even more, to get a feel for what's going on with that particular rom. The Serendipity VII theme is pretty basic, if you want to give that a try. Good luck with it, I hope your dad enjoys his new phone!
[Captivate Android Development] olo567:
Might want to update the original post so the : and ( are separated by a space otherwise it gets rendered as a ":("
[Captivate Android Development] reinbeau:
Unsticking

I am unsticking this, it's an older thread and most all of this info is covered in other stickies.
[EVO 4G General] craig198:
hey guys was just wondering if there is an app to disconnect the battery from charging while under usb power. I like to use gps on long trips and the battery gets pretty hot and thats not good for it.

So is there an app for this? is this a good idea? would be much easier than taking apart my case and taking out the battery while using gps. on second thought I guess the battery would still get warm just from the proximity of it to the gps/cell antenna
[EVO 4G General] topdawgn8:
I don't think there is. I've been wanting to play around with developing an app. I may give this a try in the future.

I have a mount that connects to my vent while in the car. Keep cool air running over it and the temp shouldn't exceed 35C. I run wireless tether, gps, 4g and mobile radios with no problem.
[EVO 4G General] craig198:
no ac and being in florida only adds to the heat
[EVO 4G General] jcuthjr:
I would try SetCpu...you can use that to change the underclock the cpu when it gets above a certain temp (which should cool it down)
[EVO 4G General] craig198:
that would help but not when i need the cpu cycles for tile loading while using gps navigation. Guess takin out the battery and running straight usb power is the only option. Or leave battery in and shorten its lifespan. they are pretty cheap anyways.
[EVO 4G General] Junon:
I don't think you CAN run it off USB power with no battery in it, can you?
[EVO 4G General] craig198:
nope you cant. oh well
[Galaxy S I9000 Q&A, Help & Troubleshooting] Jamie-:
TouchWiz seems to place a randomly coloured square background to non-stock icons, sometimes with a pattern. Is it somehow possible to have the same effects when using ADW or LP? I don't like TW itself too much but adore the iPhone style icon effect.
[Galaxy S I9000 Q&A, Help & Troubleshooting] jersr:
It should automatically apply hockey's icon effect (see themes & apps section) ;-)
[Galaxy S I9000 Q&A, Help & Troubleshooting] Jamie-:
Hi, have you managed to get those icons working with ADW or LP? If so could you share how you did it?
[Galaxy S I9000 Q&A, Help & Troubleshooting] BlackDino:
I am also interested.