yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] AdamOutler:
Did you apply the fix in the first/second post? The repartitioning problem requires correction before flashing and you cannot reinstall heimdall after applying the fix. This is a problem with the current version of heimdall.

You probly need a better USB cable. I flash crazy stuff on my device and have never encountered this problem. Right now I'm running vibrant "exclusively from T-Mobile" on my device.

Use my ModeDetect program to see if its detecting while you try different things. It will let you know if its actually bricked or if its just got a black screen.

Also, try a 301k ohm across USB pins 4 and 5.

Again, I flash some absolutely crazy stuff and recover with this flash.
[Captivate Android Development] AdamOutler:
Yep. check out the fix in the second post. Don't install heimdall when it asks.
[Captivate Android Development] michaelsucno:
1. Yes I used the fix (script for total resurrection of a device).

2. It goes to a black screen but the device its still working, I can easily put it in download mode by taking out the battery and connect the usb cable and press the volume buttons.

3. The mode detector says it is download mode.

obs: In my previous comments I attached 1 screen-shoot because I though that the program isn't flashing the pit file and other temp files, could you tell me if that could be causing troubles.
[Captivate Android Development] nok6100:
Still getting the errors when launching the .jar file. :confused:

I have attached a screenshot of the error, maybe it will help so u guys can point me in the right direction, and once again, I appreciate the help :)
[Captivate Android Development] michaelsucno:
I did those steps and flashed correctly, the problem is that my device still can not mount the internal sdcard.

While I was using the mode detector, I found that can still use adb when it is in recovery mode, There is a way to force mounting of SD from there?

Summary of what messed the partition:

Flash from CM7 to stock 2.3.4 (SAM firmware with pit 512 using Odin with repartition checked)

I bring this because I read in a forum that CM7 has a different partition format and some times it causes trouble when you don't flash to stock with one click. Maybe this could help to understand the origin of the problem. The thing is that I don't know if it still a software problem or if it became a hardware problem.

---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------

I tried to run heimdall on ubuntu virtual machine (OS: Win7), but I realized that its easier to install ubuntu directly in the computer and run it as parallel OS. Try it that way.
[Captivate Android Development] mrhaley30705:
Adam, can this be used on a Virtual machine?
[Captivate Android Development] AdamOutler:
How are you running it? Under Windows you should double-click and that's it. Try rebooting. If there's still a problem, I'd like to hear from one more person before taking that download down. It works on my computer, but I can't upload a new one from work, nor download that one to test.

michaelsucno is running it just fine.

Please redownload and try again. Try both of them.

The server was down last night and there was a bit of problems this morning. It's possible that only partial downloads were made.
[Captivate Android Development] michaelsucno:
Adam I used the mode detector with the black screen and it shows me Kies mode detected. It means that the rom is properly installed, isn't it?

---------- Post added at 01:04 PM ---------- Previous post was at 12:57 PM ----------

OK I will download it again right now.
[Captivate Android Development] AdamOutler:
I'm uploading a new copy to the server now... I found a way... I SSH'd into the TK server, set up some account information, then SSH'd into my home computer, and from my home computer, i SFTP'd into the team komin server and began uploading some files. From my SSH display which is SFTP'd into the server, it's saying it will be nearly 1.5 hours before both files are in place. I will then SSH into the server, then delete the old and finally replace them with the new.

edit: I can't believe i didn't think of this before... it's too simple!
[Captivate Android Development] Time_Zone:
Wierd. Couldn't find an apn after reboot. Had to do factory reset after installing and that fixed it. (root version.
[Captivate Android Development] AdamOutler:
If you are downloading now, your downloads will be interrupted. I'm replacing the new version on the server now.
[Captivate Android Development] miketucky350:
Thats why i tested on xp and not on my Linux mint/windows 7 pc. Everyone knows Xp is the worst os, and is testy with abd. I must say this old xp sh*tbox has always worked with this stuff very well. Its all about installing the drivers correctly. Easy enough right? Keep up the great work. All of us Ubuntu derivative lovers really appreciate it. As with odin were forced to use windows. I think all roms should come heimdall flashable so we all can enjoy :) Why not 1 click and forget it.
[Captivate Android Development] AdamOutler:
Not everyone knows how to properly make a firmware package. Once this comes out of beta (repartitioning problems) I will publish a video and documentation on what you need to know.
[Captivate Android Development] michaelsucno:
Adam,

I just downloaded it and flashed again, but it didn't worked. The partition is still messed.

Message:

E: Can't mount/dev/block/mmcblk0p1 (No such file or directory)
[Captivate Android Development] stayintwisted:
got it downloaded,, tried it,, first time it hung up at " handshaking with loke" so tried it again,, worked perfectly,,and I reemembered I forgot all about that darned 3e recovery ooops oh well put apex back on and I am a happy camper again,,good tool to have on file,, thanks for the work
[Captivate Android Development] AdamOutler:
That's your sdcard. Nothing can be done with that from heimdall. You need to reformat it from recovery.
[Captivate Android Development] michaelsucno:
Since it isn't mounted, recovery doesn't let me format it, looks like I'm in deep trouble
[Captivate Android Development] AdamOutler:
Try flashing this, then flash some custom rom with a better recovery after letting the stocker try to boot as much as it can.

You can't format a linux device with it mounted. You need a tool to format with though.
[Captivate Android Development] umanko:
will this work for me ?? I am on

Firmware version : 2.3.4

Baseband version : i897uckh3

kernel version : 2.6.35.7-i897uckh3-CL461307

This is the stock version of gingerbread I guess.
[Captivate Android Development] AdamOutler:
Stop right there..... the answer to this question is the same as "Do you have a Captivate?"

This works for everything. But read the second post. Heimdall is crippled for repartitioning.
[Captivate Android Development] GTKiller:
I used this and did get back to stock, I tried in install clockwork recovery to install custom roms and it wont do it. Odin also wont reconize the phone in download mode. What can i do
[Captivate Android Development] nok6100:
You have to uninstall the Heimdall drivers in order for ODIN to work.
[Captivate Android Development] GTKiller:
How do you do that. I did get clockwork installed finally using himedall suite, but I would still like to know how to uninstall the drivers. You mean the drivers from my computer
[Captivate Android Development] nok6100:
Yes, the drivers for heimdall will not allow ODIN to work in my experience. The heimdall drivers on your computer must be removed. I have not done that in quite a while so someone more experienced than I will have to give you the rundown on how to go about the driver removal process.
[Captivate Android Development] GTKiller:
I think I got it. Odin is installing now.
[Captivate Android Development] AdamOutler:
No... just install the closed source Samsung drivers. I hate windows for all of their abstractions and crazy stuff like this. Its very simple to run this on Linux or Mac.
[Captivate Android Development] mattern1974:
Thank you, Adam, for this package!!

My warranty is about up and I'm on my third Captivate. The last refurb they gave me had this firmware on it but I thought nothing of flashing back to JF6 stock to continue on my merry way (eventually) to Pinnacle.

Now I can see what I was "missing" with the AT&T Froyo update. It is definitely looking slower and all AT&T bloaty.

Thank you again!!
[Captivate Android Development] TayzGpa:
Adam; I am trying to flash back to stock from Andromeda 3.

I tried using this (both root and non-root). Everything looks like it went great. Phone reboots, etc. But now, if I make or receive a phone call, I cannot hear the other person, and they cannot hear me.

If they call me, my phone will ring and when I answer, I cannot hear them, they cannot hear me.

If I place a phone call, their phone will ring, I cannot hear it ring on my end, and when they answer I cannot hear them, they cannot hear me.

If I get a phone call and do not answer it, it will go to voice mail and they can leave a message, but I cant retrieve it because I cant hear after I dial the voice mail number.

I have tried flashing a different I897 modem but nothing seems to help.

I have also reflashed back to Andromeda 3 and the phone works fine.

I have a ATT Captivate revision 1012.

Any suggestions? :o
[Captivate Android Development] AdamOutler:
Mine works fine for calls. This is a total reflash of the device... If you want to ensure nothing is left behind, use the code in the first post to reformat.

If flashing again and reformatting do not work, then you must have a hardware problem.
[Captivate Android Development] TayzGpa:
Adam, thanks for your help and quick response. I did try reformatting and flashing again. This time with the Flash Bootloaders checked. Everything went just fine but I still had the same problems.

Flashed back to Andromeda3 and everything (including phone calls) is working just fine. Dont understand it, but that's the way it is.

Thanks again for all your help. I just stick with Andromeda for awhile ;-)
[Captivate Android Development] streetsmart999:
Thanks Adam awesome work...
[Captivate Android Development] mabovalu:
first try:

Kernel upload successful

Uploading RECOVERY

RECOVERY upload failed!

----------

2nd try:

Uploading KERNEL

KERNEL upload failed! (~ 46%)

----------

3rd try:

Uploading KERNEL

KERNEL upload failed! (~ 46%)

----

4th try:

KERNEL upload successful!

RECOVERY upload successful!

Uploading MODEM

MODEM upload failed! ( ~ 10% )

Ending session...

{ blue progress bar in Download Mode ~ 2 mm in length, ~ 5% }

Any advice?
[Captivate Android Development] dayv:
Sounds like a connection issue, bad cable or USB port.
[Captivate Android Development] mabovalu:
Thanks. I cycled through my eight (8) USB ports, and one the 2nd one got this to load. It kept re-booting into Recovery Mode so Odined back to JF6.

Thanks also to Adam for creating all these excellent programs.
[Captivate Android Development] streetsmart999:
Adam,

today I flashed the Rooted version... All is well, but there is no install from unknown sources in settings > Applications. Any idea how to get it?

Thanks for the hard work.
[Captivate Android Development] nok6100:
I was also playing around with this on my spare cappy last night, installed rooted version too.

Use "superoneclick" to get ability to install 3rd party apps outside of the market. I had to reboot after using "superoneclick", then I could install my own apps. There will be nothing in the menu on KB2 to allow unknown sources, its a gingerbread thing only to my knowledge.
[Captivate Android Development] streetsmart999:
I did it thru settings DB
[Captivate Android Development] AdamOutler:
It's supposed to reboot into recovery. That means you're loading a totally untouched version of software. If it does not boot into recovery then the phone has been booted before... or the partitons which were flashed reflect that the phone has been booted previously. That's just the way it comes from Samsung the first time it's loaded...

I could make it first-boot into download mode or battery charge mode if you'd like... lol.
[Captivate Android Development] kitkitfok:
Will this one-click will solve Soft-Brick?

I flash Darky rom JVT first, then I flash back UCKJ2, Brick my phone .........
[Captivate Android Development] klloyd:
This works great for me, LinuxMint, Debian edition. I do however have a question, or a request that is...

Can we get one with Clockwork already added in? Pain in the butt without it as you may know. Or can you load a stock"ish" rom with clockwork pre loaded? I'd pay to have a one click in linux with that!

KL
[Captivate Android Development] AdamOutler:
Here you go

http://files.teamkomin.com/Captivate/TalonDev-0.4.3-One-Click.jar

This will most likely put you into a bootloop... However, you'll have CWM.
[Captivate Android Development] klloyd:
Ok, I'll give it a go when I get home. Or just before I get off work. I'm coming from miui, and off to try other things. Heck, if I can get the pictures moved, I may try it sooner!
[Captivate Android Development] klloyd:
Confirmation number: 19Y32888VG636683E.

Worked like champ! Just fyi, it will indeed boot loop, so don't boot to it after you load the talen kernal, just use clockwork to load and go!

Thanks again!
[Captivate Android Development] keller.jeff:
Let's have a pool to see who thinks Adam has too much time on his hands!

Thanks for all your hard work! You have some incredible projects!

Sent from my SGH-I897
[Captivate Android Development] AdamOutler:
Hardly enough time... I just have my own beta one-click packaging which I have not yet released. I need to finish the safety and how-to part first. Its a matter of making a heimdall package and then running my one-click packager. I'm worried about Noobs making one-click nukes though.
[Captivate Android Development] bulletproof1013:
I've been modifying yours, for my own use.
[Captivate Android Development] abystus:
Will this reset any custom rom/kernel back to stock? I have Apex 7.1 on my phone with Talon 2.2 kernel currently. I am needing to go straight back to stock if possibly with the least amount of fuss. Hopefully this tool will do just that, but I would like to verify that I can handle such a job before I press that button. Any help is appreciated.
[Captivate Android Development] sixstringsg:
That's what it's designed for...
[Captivate Android Development] abystus:
Thanks for the response. I was just making sure because I know how easy these things are to brick... :)

Currently the software says:

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Beginning session...
Handshaking with Loke...

Progress bar is empty. Animated gif at right is still twirling. Device Status: Connected.

It's been doing that for some time. Does it just take a while?

Edit:

Nm. Restarted the app and now it appears to be doing something.
[Captivate Android Development] AdamOutler:
Looks like it's having problems communicating. You need to restart the unit.

Assuming that is all that you've done, you should be fine after a restart. For good measure, restart your computer too.
[Captivate Android Development] AdamOutler:
On linux... there's a problem with repartitioning on Windows.
[Captivate Android Development] sixstringsg:
Oops, forgot to mention that part...
[Captivate Android Development] abystus:
OK everything looks to be reset to stock now (except the first Galaxy S GT-I9000 Screen on boot). Is there a way to reset that screen to default as well? Thanks for the push heh.

@AdamOutler

Appears it was successful in Win7 64 bit.
[Captivate Android Development] AdamOutler:
You can reflash the bootloaders by ticking the "flash bootloaders" button. It's not available until you flash once. It should be fine, but it's safer to flash bootloaders on Linux with a new cable.
[Captivate Android Development] abystus:
I don't have direct access to a linux box. What are my odds on windows? :P
[Captivate Android Development] AdamOutler:
pretty good unless repartitioning is required. It should be fine. It's only a problem if you came from something like CyanogenMod or MiUI.

It's really easy to make a Linux box.. just put it on a USB stick and boot from that. Linux is also a good backup for Windows. http://ubuntu.com/download
[Captivate Android Development] abystus:
Worked like a charm. I will look into the linux stick thing :). BTW do you recommend any custom rom? I am looking for something that is fast, and that isn't a complete memory hog (the Apex I just came from was almost using all the memory being idle.) Again thanks for the help.

Edit:

Apparently my cellular internet connection isn't working (I have signal bars but no icon for internet) I've toggled it on and off but nothing. Even restarted the phone. Flight mode is off. Any tricks? Re-flashing now to see if it makes any difference.

I have reentered the APN (http://xdaforums.com/showthread.php?t=749599) and all is fine. Had me scared there for a second :).
[Captivate Android Development] psych0phobia:
Eh? Weren't the 1.3.1 binaries released already over at Glass Echidna?
[Captivate Android Development] mcala:
I use Ubuntu 11.10 & I have the open-icedtea-jdk open sourced java plugins. Does this helmdall package require the real java from oracle or can open-jdk be used. Cananical Ubuntu has decided to remove sun-java from the repos, some are pissed but I find the open source java to work fine for day to day web browsing.
[Captivate Android Development] jmtheiss:
Adam,

Thanks for this package - great work as always. If I could ask for one small modification (maybe a standalone package) - could you create a stock Heimdall one-click, with root, that also has the 3e recovery issue corrected?

I only ask because I used this to get back from trying CM7.1, and I had to put together my own Heimdall setup using another .pit file and an old xcal kernel with CWM to get around the 3e issue.

I'm not really sure if that's an easy fix, but if it is, that would be excellent.
[Captivate Android Development] AdamOutler:
I released a kernel with CWM. You can find it on the teamkomin.com website

I'm having issues still so I have not released 1.3.1 versions.

Both work fine. I use openjdk as well.
[Captivate Android Development] psych0phobia:
Oh! Right... For some whacky reason I spaced out on the fact that these are one-click packages.
[Captivate Android Development] jmtheiss:
Sounds good - I'm assuming it's the Talon 0.4.3 one-click. Thanks for pointing that out. I'll roll that into my "save myself from certain destruction" file folder.
[Captivate Android Development] AdamOutler:
yeah, that's it. it's a good way to get CWM on your phone. btw.. I just released that as a package, I had no part of development of the kernel itself.
[Captivate Android Development] jmtheiss:
Noted. I've used Talon in the past (that particular version, even), so it's a good package to have on hand.
[Captivate Android Development] icedd:
Can I use this to get out of a soft-brick?
[Captivate Android Development] AdamOutler:
Yes you can. Also one-click unbrick will work.
[Captivate Android Development] Darkuso:
Can i use this 3 button fix after flash this? http://xdaforums.com/showthread.php?t=812434
[Captivate Android Development] mrhaley30705:
No.no.no.no.no. For 3 reasons.

1 You will hard brick your phone

2 You really will hard brick your phone.

3 You should not need it after flashing GB bootloaders.

4 Yes, you really will hard brick your phone.
[Captivate Android Development] Darkuso:
Hehehe thanks man, i was asking because i going to flash CM7 and they ask for eclair/froyo bootloaders and 3 buttons for recovery.
[Captivate Android Development] mrhaley30705:
3 button for recovery is required, but it is now ok to use GB bootloaders.
[Captivate Android Development] Darkuso:
What? wait, do u mean that i can flash CM7 with GB bootloaders? Sorry im a bit confused! lol
[Captivate Android Development] mrhaley30705:
Dude, I got my threads mixed up. I thought I was in a GB thread, not Froyo. The3 button fix is safe as long as you don't have GB bootloaders. But, the GB bootloaders will fix the 3 button problem in a safer way.
[Captivate Android Development] sepherian:
I feel safer...

Idk why, i just feel safer with heimdall than odin. Like i know she's there to hold me when things go wrong...
[Captivate Android Development] EVOIXGSR:
I have a totally stock AT&T Captivate, I'm still on UCKB1, and Kies is telling me I have the latest firmware version from February's Froyo update. Also, going directly from the phone to search for latest software update says there is no update available. Whats the deal?

P.S. I've never rooted my device.
[Captivate Android Development] mrhaley30705:
Android 2.2 was the last official update from att/Samsung. The stuff you see here is all leaked firmware from Samsung. It's ridiculous that Europe and z Canada received 2.3.3 firmware already, with talks of Ice Cream Sandwich coming soon, and we are still officially at 2.2.

Although KB2 is what comes on the refurb phones now, maybe new ones too, it is still 2.2. Which is retarded,imho.
[Captivate Android Development] oops_iv:
links broken

the files wont seem to download for me :

http://files.teamkomin.com/index.php?dir=Captivate/

when i click any of them .. blah .. nothing :(

-this happens from chrome - ubuntu 11.04
[Captivate Android Development] jmtheiss:
Odd - I just went there and they seem to be working fine for me.

I'm on Win7 with Firefox - have you tried right-clicking and doing a "save target as" (or whatever chrome uses)?
[Captivate Android Development] AdamOutler:
Works on my infuse 4g.
[Captivate Android Development] mrhaley30705:
Works fine on my Captivate with dolphin mini
[Captivate Android Development] bhdunn:
Nokia OVI suite interferes with JAR one click files

I couldn't get the one click files to run, it took a couple days (Total 4 hours) of research but I found this cure for Windows 7 x64. Apparently Nokia OVI suite thinks JAR files belong to Nokia and many registry entries need to be cleared to get one click JAR's to work. The attached ZIP file contains a batch file that you can run as Administrator that will fix this.

I found this solution at: http://thepanz.netsons.org/post/windows7-jar-file-association-broken-with-nokia-ovi
[Captivate Android Development] Bust it:
Worked great on macbook pro, was stuck at the att white screen. Was able to restore every thing with nandroid.

Thanks, this made life a bit easer today.
[Captivate Android Development] wmbenham:
I'm getting hung at handshaking with LOKE: ERROR Failed to receive response.

I'm using Heimdall 1.3.1 on Mac OS X 10.7.2

EDIT:

Thank God I keep a jig around. Softbricked for a moment.

I tried both USB ports on my Macbook with the original usb cable that came with the phone and finally after twenty tries I got a partial download through 14% of recovery. I tried probably another five times and then decided I would try using the cable that came with my Kindle.

MUCH BETTER! First attempt made it almost the entire way through recovery, and Second attempt successfully flashed back to 2.2.

Thanks for all your hard work on this it certainly makes it easier being a mac user.
[Captivate Android Development] AdamOutler:
People don't realize how much a bad cable can impact download mode.
[Captivate Android Development] AdamOutler:
I've updated this package to a Heimdall One-Click 1.3.1. this is no longer a beta package. It works equally well on Linux, Windows and Mac.

Make sure that you install drivers on Windows and it never hurts to reboot.

We are still waiting for the Team Komin server to come online.
[Captivate Android Development] aalh:
tickee tockee:)