yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] koreancanuck:
Try this. Press volume up and down and hold it and plug your usb cable into your phone. Have ODIN open before doing it so your phone can be recognized by ODIN.
[Vibrant Android Development] Koush:
WARNING: From koush' IRC channel it seems this version may be (permanently?) bricking devices.

At the time of this writing only a single working flash has been reported, and several (full?) bricks.

--Chainfire

I just finished my recovery for Galaxy S. This requires some testing before I do the final release.

Recovery/Boot TAR download (do NOT extract):

http://bit.ly/czDrPC

932e5f7a9f09c9bc33b14a527f642933

Initramfs source: http://github.com/koush/i9000-leshak-initramfs/tree/koush

Installation instructions:

Install Odin3 v1.0 (MAKE SURE THIS IS THE VERSION YOU USE)

Start Odin3

Press PDA

Select the tar file (do NOT extract)

Start phone into download mode.

Press START to flash.

After 20 seconds or so, phone should automatically reboot.

Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads :)
[Vibrant Android Development] MBok:
You are awesome, man.
[Vibrant Android Development] junkdruggler:
And it has begun!
[Vibrant Android Development] MikeDo:
super noob question here sorry but what does clockwork do exactly? sorry don't kill me i'm just trying to learn
[Vibrant Android Development] dave012083:
buckle your seat belts.... here we go
[Vibrant Android Development] yvyv:
Lots of questions for the newbies, ready to beta test..

1- I'm on Mac, do I just drag this file to my internal or external SD CARD ? Do I look for the file and follow instructions in first post ?

2- Once installed, I'm I ready to install Paul's Rom ?

3- I notice there is two zip's to update....Apply or install ? which one for roms ?

Thank you all
[Vibrant Android Development] blackeyedbrian:
If you're unsure on how to use odin, watch this video

http://www.youtube.com/watch?v=PpWcM44On88 and http://www.youtube.com/watch?v=VzFE8-jWku0

Odin can be found here :

http://www.multiupload.com/2KS7YR7UXG
[Vibrant Android Development] jroid:
where do we download odin3 and how do I install it if it's not included in the .tar file not to be extracted?

EDIT: question answered. thnx
[Vibrant Android Development] kronos82:
In a nut shell Clockwork is a recovery image which allows you to not only flash new roms; but also alows back up and restore your phone.
[Vibrant Android Development] the3dman:
I have a button that says PDA is that what you meant or am I missing something (quite possible)?
[Vibrant Android Development] MikeDo:
so basically if i want to reset my phone back to stock this is what i use? can i get odin3 for mac?
[Vibrant Android Development] dattas:
+1 to the question if he meant PDA instead of PDU
[Vibrant Android Development] kopykatkiller:
This is for flashing custom roms. Backing up your phone between flashes, before flashes, managing sd partitions, flashing themes, recovering after bad flashes, wiping data, wiping apps, pretty much it is the heart and soul of your pretty new phone. This gives you a little piece of mind when modding your phone.
[Vibrant Android Development] junkdruggler:
I just updated the "Read before posting and Informative links" sticky... it contains the link to Odin3, the recovery and the drivers all in one place...
[Vibrant Android Development] the3dman:
Just found out on IRC that he did mean PDA not PDU. But I also found a post by someone saying they bricked, so be careful. Anyone successful yet?
[Vibrant Android Development] EugeneKay:
Just be warned, I'm fairly sure I've managed to (drunkenly) brick my Vibrant already via Odin3 flash that didn't finish.

Herp derp.
[Vibrant Android Development] the3dman:
Sorry man, your not alone another brick just reported.
[Vibrant Android Development] bubonik:
Define brick?

Phone -> PC?

That is not bricked. Have them reflash the files in the other thread.
[Vibrant Android Development] the3dman:
Bricked = Paperweight / Phone doing nothing / Not connecting to PC and not able to reflash. There are now reports of 3 full bricks.
[Vibrant Android Development] jroid:
yikes.. holding off till this gets stabilized.. on another note samsung kies looks a lil screwy to me and cannot even read any sub titles within the program, text is all glitchy. all I see are the icons and can navigate.
[Vibrant Android Development] SkOrPn:
Hopefully everyone is within their 14 day grace period if they brick them. Im waiting a bit longer. Not sure my heart could handle holding a $500 brick and re-installing my sim back into my crackberry. lol
[Vibrant Android Development] junkdruggler:
I successfully reflashed with ms_gurus method last night... My comp won't connect to my phone in dl mode so I can't flash this recovery tonight...
[Vibrant Android Development] GizDrak:
I was going to give this a shot but i will hold off plus my phone will not go in to download mode no matter how many times i try... I have no trouble getting in to recovery... It is just vol down plus power on boot right?
[Vibrant Android Development] jroid:
everyone who bricked, did u guys flash the xwjg1 files in odin3? maybe those files are out of date.. I see a load of other files beneath
[Vibrant Android Development] Introspektive:
Tempted. Probly best I wait till more research and test dummies have been used.
[Vibrant Android Development] the3dman:
For download mode power off phone and when it starts saying goodbye hold down volume up and down + power. Thats what worked for me.
[Vibrant Android Development] the3dman:
They can't flash anything as of now. Computer is not detecting phone.
[Vibrant Android Development] dattas:
You can do that, or if you get shell access, make sure you are root, then execute:

reboot download
[Vibrant Android Development] decepticon:
Here is Odin3 v1.0

I am posting this here too because in the Captivate forum people were asking.

http://www.multiupload.com/62EM4UM0MS
[Vibrant Android Development] jroid:
I'm referring to the file they flashed that bricked the phone
[Vibrant Android Development] the3dman:
Oh sorry... Not sure on that one.
[Vibrant Android Development] masr1979:
Test Dummies? that's not very respectful. Most of us know the risks we take, but that doesn't mean it's cool to disrespect people who brick their devices... specially since some actually know what they are doing/read instructions.

I'll be holding off a bit 'til Koush has a looksie, I already gave my G1 away, so I can't mess with this phone.... for now. We should try to figure out what's causing the problem; the guys that have bricks, did you remove the SIM and SD cards? I read that when using Odin you are supposed to do that. Also anyone that was successful outline what steps you took, your PC OS, anything that you think could be relevant. Likewise with the bricks.
[Vibrant Android Development] junkdruggler:
Yeah first time I tried my sdcard was inserted and it failed went to a crazy screen... Looked like a phone and comp connected by a cord... Took out the batt and sdcard and it worked...
[Vibrant Android Development] gravis86:
I'm pretty sure he's not calling them stupid, he just meant test dummies. You know, like crash-test dummies? It's just a figure of speech.

Although I personally do believe it takes a certain level of stupidity (and bravery, for that matter) to be an early-adopter, or to test certain things when there is high risk. But having said that, I'm proud to say I'm one of them :)
[Vibrant Android Development] DAKIDD236:
Are you guys sure that you bricked your device? can you enter recovery mode or download mode?
[Vibrant Android Development] jroid:
from my understanding, all we need to do is flash the recovery tar using odin3 not all the other firmware files in the video. maybe whoever bricked their phone flashed these files?
[Vibrant Android Development] the3dman:
Nope they only flashed the 1 file.
[Vibrant Android Development] YellowGTO:
From reading the other Galaxy S forum if you using anything other then Odin3 1.0 you will brick your phone. I think 3 versions of Odin3 are floating around make sure its 1.0
[Vibrant Android Development] masr1979:
Well I never did say it meant stupid (dummy), but it's the same as calling someone a guinea pig... not exactly the most flattering way to refer to someone that, whether they want to or not, is benefiting the rest of us, by possibly saving us from %&^%ing up our devices.

As I said, normally I would be on board, since I usually have 2 phones available, but that's not the case now. I think it takes more curiosity than stupidity or bravery, but let's dispense with the philosophical debate. Not the place for that, just kindly disregard the whole thing.

The .tar only contains one file, so I don't see how they could flash anything else. What we really need is for those that were successful to come forward and tell us how they went about it. Usually there would be a common flaw in execution... unless it's the HTC Wizard we are talking about, that thing was insanely screwy; I'm still surprised I never had any issues with it.
[Vibrant Android Development] DAKIDD236:
To be honest, I really don't think anybody flashed this recovery. After seeing the warning in the OP it would deter anyone from thinking twice about it. But, if someone did, I would really appreciate if you spoke up and told the community the steps you took!
[Vibrant Android Development] jroid:
I can't even get windows 7 to even detect the dam phone. I downloaded and installed the drivers and they install but the phone isn't being detected. oh well tomorrow's another day
[Vibrant Android Development] skater4690:
ok i flashed it and it worked somewhat now my phone boots up but immediately reboots
[Vibrant Android Development] kopykatkiller:
I was able to successfully flash the recovery.....but...and I do mean but....It bootloops about 30-40 times before I am able to successfully get to the home screen.

I am also able to load up the clockwork recovery.

Slider loads, buttons light up. Reboot.

If I touch the buttons and light them up during the Samsung Fly in boot logo...reboot.

This last power down I did, it has not come back up to the home screen for me yet, probably on self-reboot #80 now.

Going to try wiping again and see if I can get back in, seems it might have something to do with the buttons though.

Pulling my SD card allowed the boot cycle to complete.
[Vibrant Android Development] skater4690:
having the same problems let me know if you find a cure
[Vibrant Android Development] psychoace:
If you are bootlooping and have access to download mode still flash this file and it should fix it all.

http://files.samdroid.net/files/2forum/i9000_Kernel_LK9_01b9.7z

Thanks go out to cferral for figuring this one out.
[Vibrant Android Development] kopykatkiller:
Pulling my sd card allowed it to complete the boot process, I was able to insert it again after the boot completed.
[Vibrant Android Development] skater4690:
theres no file...
[Vibrant Android Development] skater4690:
omg thank you it worked!!! lol how do you get into recovery mode though? nevermind just rebooted...
[Vibrant Android Development] DAKIDD236:
Progress! Did you guys boot the phone into recovery and make and backups yet?
[Vibrant Android Development] psychoace:
http://forum.samdroid.net/f49/dev-kernel-i9000-root-lk9-01-beta9-22-06-2010-a-1319/ its in here
[Vibrant Android Development] skater4690:
ok now the link is right does this fix the upside down volume buttons?
[Vibrant Android Development] kopykatkiller:
I have completed a successful nandroid backup.
[Vibrant Android Development] DAKIDD236:
how are you so sure this fixes the bootloop?
[Vibrant Android Development] skater4690:
how do you get into recovery? i flashed already but dont know how and slightly afraid of getting stuck in a bootloop again and after the first start without the sd card then putting it back in it was ok for a sec then reboot but still had sd card in and booted fine no reboot yet
[Vibrant Android Development] masr1979:
Upside down buttons? Is this happening while in Recovery mode, or on the regular Android OS?
[Vibrant Android Development] kopykatkiller:
Hold power + vol Up + vol Down

I had the reboot issue again after doing the Nandroid back up, but once I pulled the SD it reboot a couple more times and came back up, put the SD card back in and all is running ok now. Until I reboot, then I have to repeat the process.
[Vibrant Android Development] skater4690:
regular os like instead of volume up for up button its the down button and theres not audible touch tones either...
[Vibrant Android Development] MikeDo:
good to hear there are people that have been successful. if yall could post up a video that would be great for the users on here not familiar with doing this. thanks!
[Vibrant Android Development] skater4690:
really just follow the instructions and youre ok besides the about 20 minute heart race youll get from doing this i was ****ing scared i was gonna brick
[Vibrant Android Development] YellowGTO:
Not very successful I would hold off a bit.
[Vibrant Android Development] kopykatkiller:
Volume buttons are reversed in the recovery and in Android once I boot, anyone else?
[Vibrant Android Development] skater4690:
same for me in android how do i get to recovery?
[Vibrant Android Development] skater4690:
nevermind figured it out going to do a nandroid as we speak

horrible news no external audio...
[Vibrant Android Development] DAKIDD236:
I've seen someone write about this in another Galaxy S forum, i'm in the process of seeing if they discovered a fix. I'll keep you updated.
[Vibrant Android Development] skater4690:
you think taking all the libs from our system dump and putting them into our system will fix the problems?
[Vibrant Android Development] fykick:
The reason vol buttons are flipped if you flashed the posted kernel a page or two back is cuz it was meant for EU version where the vol buttons are flipped.

If you have the same issue and jusy flashed the recovery, then its prob cuz the recovery was also written for the I9000 with reversed vol buttons
[Vibrant Android Development] skater4690:
well how would you suggest a fix?
[Vibrant Android Development] DAKIDD236:
write @koush on twitter and see if he has a quick fix, i think he based his recovery off of Leshaks international kernel
[Vibrant Android Development] skater4690:
if only i had a twitter i would but idk even how to read posts on it lol i just dont mess with twitter if anyone would kindly ask for me id appreciate it
[Vibrant Android Development] skater4690:
ok so far no external audio. no home button working. volume buttons backwards. market caused me a reboot. hhhmmm prolly leaving stuff out but overall signal seems better
[Vibrant Android Development] ryanolson7:
i'm getting the phone -> pc

how do you get back to download mode if you're stuck on the phone->pc screen

ahh.. hopefully getting that screen isn't a brick.
[Vibrant Android Development] Koush:
It looks like I will need to create a recovery *per* phone. The phones aren't as compatible as I thought. For now, revert back to stock zImage...
[Vibrant Android Development] skater4690:
how would i go about doing that?
[Vibrant Android Development] jmhalder:
disregarding any warnings, went ahead and flashed this, now the splashscreen says GT-i9000 or whatever, and drivers are installed for that rather than the US model, lol... vol. up/down is still correct, also the used added SD isnt mounted, other than that its all good... so why is the system kernel AND recovery part of the same package?
[Vibrant Android Development] skater4690:
your volume up and down are still good? how about external audio?
[Vibrant Android Development] YellowGTO:
You guys have FM radio now by any chance?
[Vibrant Android Development] skater4690:
doesnt matter cant use it no external audio
[Vibrant Android Development] jmhalder:
just did a nandroid, also got a MD5Sum error, rebooting now....... audio through the speaker is fine, and also through a pair of 3.5mm headphones... tested watching the double rainbow song on youtube! its so intense... but seriously, only thing that is an issue on my captivate is the external SD not working. and the MD5 for the nandroid not working.

*edit, rotates the screen 90 degrees from proper orientation, gonna try and calibrate that*
[Vibrant Android Development] skater4690:
maybe thats why cause you have a captivate and i have a vibrant my sd card works fine just no sound and buttons are f'd up idk what i should do maybe go back to stock and then re root but prolly tomorrow
[Vibrant Android Development] psychoace:
We found that all the bricks are fixable. Try letting your phone sit for 20 minutes on without a sim or sd card or try pulling the battery and putting it back in after a few minutes

This is what worked for a couple people

If you see this screen follow these commands while odin3 is opened.

"SIM+SD out, put the battery in. Plug in USB. Hold down both Volume keys, and then push power. Hold it. From the phone > pc screen, hold vol +/- and power, wait til it goes black then returns to that screen. When it goes black the 2nd time release power. " That should put you in download mode so you can install the recovery again.
[Vibrant Android Development] justanothercrowd:
From IRC

"So I just got the phone -> PC and I managed to get back into download mode. For you guys that are getting it. From that screen, hold vol +/- and power, wait til it goes black then returns to that screen. When it goes black the 2nd time release power."
[Vibrant Android Development] YellowGTO:
I figured it it loaded up and got a lock then we could confirm that the US Galaxy S have not had the radio removed hardware wise.
[Vibrant Android Development] EugeneKay:
For the "black second time method", note that you need to have Odin3 running and USB plugged in. It does take a bit of fiddling, so just spend time with it. Make sure BOTH volume clickers are depressed, and SD+SIM are out.

After you re-flash the recovery, it may be running sloooow. Try installing leshak's i9000 kernel(flash it at the Shovel screen, same way).
[Vibrant Android Development] psychoace:
You can find the kernel in here http://android.eugenekay.com/Vibrant/

Eugene couldn't link because he only has 4 posts so I'm doing it for him.
[Vibrant Android Development] EugeneKay:
Thanks.

I'm mirroring whatever Android stuff I use, as well as whatever else happens to amuse me. Feel free to abuse my server or make suggesting for what to upload(I'm a LOT more IRC active than here)
[Vibrant Android Development] TGA_Gunnman:
Man, I just got back from Ratt and Scorpions and missed all the action. Good thing I was at a concert or I'd be in the same boat. I'm wasted, going to bed.

Gunnman from Galaxy S
[Vibrant Android Development] psychoace:
Welcome back to the year 2010. Hey do you want to see a tv that is thinner then your keytar?
[Vibrant Android Development] decepticon:
Come back when you cut off your rat tail and get rid of that red Eddie Murphy jacket
[Vibrant Android Development] kopykatkiller:
omfg...lol
[Vibrant Android Development] caffeineighted:
So do we have a method to return to factory yet? All I'm seeing are methods that have broken pieces of the OS as a result.
[Vibrant Android Development] gothdroid:
Just bricked. Going to work on this tomorrow, I guess I have to go back to the crackberry for the day.
[Vibrant Android Development] kopykatkiller:
No way right now, currently having to use the beta rom so I can at least hear my phone ring. :(

Sent from my SGH-T959 using the XDA mobile application powered by Tapatalk
[Vibrant Android Development] ryanolson7:
the furthest i've gotten from getting away from phone-+!+-pc is to a screen that said reset phone or unknown upload mode and from there i couldn't go anywhere.

so i'm still at the phone->pc screen...

hopefully we can figure out other ways to get to download mode from here...
[Vibrant Android Development] skater4690:
what beta rom are you talking about? id love to have my phone ringing atleast...
[Vibrant Android Development] kopykatkiller:
http://xdaforums.com/showthread.php?t=728698

Even it is giving me problems. Force closes in Market, and Messaging.
[Vibrant Android Development] iBustCh3rries:
Patiently waiting for CM6 :-)
[Vibrant Android Development] mytmouse:
Early stages of dev are always risky. I'd like to try this recovery but am unclear of what sort of feedback Koush is looking for. Can this be clarified?
[Vibrant Android Development] Koush:
If you are stuck on the phone to PC screen, you are NOT bricked. During development, I ended up getting into this state a couple times myself. You can still get into download mode in the same fashion.

Connect your phone to USB so you get the phone->PC screen. Press and hold both volume up/down. Then press and also hold Home. Then start pressing and holding power for 2 seconds. After 2 seconds, let go of power. Continue holding volume up, volume down, and home, until you get into download mode.
[Vibrant Android Development] Koush:
Ramdisk is embedded in the kernel as an initramfs. That is how samsung does things. It's dumb.
[Vibrant Android Development] bubonik:
-Plug phone into usb

-This next bit depends on what firmware you had

--Tmo shipped: hold down vol +/- and power, screen will go back then return to that screen, once it goes black the 2nd time release power only

--Beta rom: hold down vol - and power, screen will go back then return to that screen, once it goes black the 2nd time release power only

Easiest method is of course: adb reboot download or #reboot download

It seems they've made it almost brick proof. You can flash almost any combination of firmwares, but they probably wont work.
[Vibrant Android Development] designgears:
http://xdaforums.com/showthread.php?t=731989

fix is in the first post.

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

stock rom flasher :)
[Vibrant Android Development] bubonik:
That firmware does not work on the vibrant.
[Vibrant Android Development] rhcp011235:
I support the hacking of these phones. But, I think you guys are nuts. I would never do this. Unless

A) I knew 100% i had the stock rom i could flash to go back to normal.

B) This recovery was made for the vibrant. ( as far as i know he did not make this on the vibrant it was the ATT version)

1) I see posts of people using the ATT version. Thats not a vibrant and what is it doing here?

So, Saying so. I dont understand why you guys are bricking $600 devices just for the sake of it. The phone is out 6 days. and for the ATT guys even less.

Wouldn't it be smart to wait for "working" versions? that dont state "Perm brick"

Just my option.
[Vibrant Android Development] daropedia:
Because someone has to brick a few to learn how to not brick them?

we're always gonna brick a few to start with
[Vibrant Android Development] bubonik:
All "bricks" have been recovered so far. Some of us still have the 14 day return window.
[Vibrant Android Development] skater4690:
will this stock rom work for the vibrant???
[Vibrant Android Development] masr1979:
If someone doesn't take the plunge we will never get "working" versions. That is not to say that everyone should just start flashig things, but if you do your homework and you understand what you need to do... go for it. If someone can't be bothered to do some research prior to flashing, and refuses to do some research post-flash if something should go wrong, then it's better for that person and everyone else if he/she waits.

Oh, it was assumed that all Galaxy S phones were almost identical, except for things like front facing cameras, radios (GSM/CDMA).

As Koush explained, seems that the European versions are a tad more different from the American counterparts, but what works on an American GSM verison should work on the other (ATT/Tmo). Now compatibility between roms made for the American GSM versions and the American CDMA versions is a different matter.