yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] HDMitch:
Return To Stock Issues

I am having the exact same issue, I have spent several hours reading and following YouTube video to make sure I am doing this correctly and always get stuck with ODIN unable to reconnect to the phone after putting it into download mode. Windows gives a warning "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it."

This is the same issue on both my WindowsXP and Windows7 x64 system, proper drivers install.

Some guidance would be great!
[Captivate Android Development] GRACO:
May be you can use an alternative method?

http://xdaforums.com/showthread.php?t=818439
[Captivate Android Development] sjavvaji:
my 1009 will only take odin v1.7 and jh3...u gotta just search up ur model because this really only works for 1007 and earlier

-1007: use this

1008: use the 3-button fix version

1009: go to samfirmware and use odin v1.7 and jh3

1010: can only flash with odin v1.7 and jh2
[Captivate Android Development] hooshman:
I thought I bricked my phone for a second..

So I tried doing this and for some reason i got the phone+!+computer screen. i freaked out cuz adb wouldn't recognize the phone or anything.. This method worked for me though.

Method 3:(KEY COMBO)

Remove the battery, sim card, sdcard if you have one

Insert the battery

Hold both Volume buttons (from i9000 just down, don't touch the power button)

Plug in the USB cable and continue holding both Volume buttons
[Captivate Android Development] chasesavestheday:
found this for you fellow 1010'ers. i havent tried yet but i read it and it looks promising. cheers.

http://xdaforums.com/showpost.php?p=10056254&postcount=36

full thread: http://xdaforums.com/showthread.php?t=883491
[Captivate Android Development] eep2378:
I'm running vm ware on my imac using windows 7. I am not able to install the usb drivers from the op. I'm running the 64 bit version. When running the installation wizard it starts the install but then it just stops and says cannot complete the install?

Sent from my SGH-T959D
[Captivate Android Development] fri3dric3boi:
i just got the captivate, will this work on jh7?
[Captivate Android Development] Pirateghost:
its JF6 which is older than jh7....it works 'on' your computer and if you flash it to your phone, it will put JF6 on it... there is no 'working on' jh7
[Captivate Android Development] JamesR913:
Nevermind.
[Captivate Android Development] sjavvaji:
THIS SHOULD BE ON THE FIRST POST!!!

Sent from my 1.4ghz Cappy on Darky's JPY
[Captivate Android Development] steelechamp:
Without VMware

So I managed to get this running on my Mac by COMPLETELY porting it.... Do I just follow the same instructions minus the drivers ? If you want also, I could post the port for Mac users?
[Captivate Android Development] ryude:
I have a 1009 and I have used this one-click about 25 times without any issues.
[Captivate Android Development] agentfusion:
Almost immediately mine went past file analysis.

<ID:0/004> File analysis..

<ID:1/003> File analysis..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> Sbl.bin

<ID:0/004> boot.bin

<ID:0/004> cache.rfs

<ID:0/004> dbdata.rfs

<ID:0/004> factoryfs.rfs

That's where I'm at now... with a progress bar both on ODIN and my Captivate.. so if yours is hanging like that, something is wrong and you should try to restart ODIN until it works properly.
[Captivate Android Development] agentfusion:
Okay... tried to use ODIN, it froze, I restarted it... now my phone won't do anything at all. I can't get it to even TRY to boot. Anyone got any ideas?
[Captivate Android Development] opcow:
Remove the battery and sim card for a minute or so and try again.
[Captivate Android Development] tazman171:
I've been using Odin one click JF6 for a long time but on this last flash I couldn't get into download mode and have win7 64b recognize the usb at the same time. Every thing is fine until download mode is started, win7 gives a "couldn't install device drivers" error and nothing I do gets Win7 to recognize the phone in download mode. My previous flash this happened in the first 20% of flashing and damn near bricked my phone.

Has anyone experienced this with odin one click JF6 and Win7 64b lately?

I've been using it since Aug with no probs until now on the same PC and I flash a lot.

Any info on similar experiences would be appreciated. :cool:
[Captivate Android Development] tazman171:
Like opcow said or/and get a jig or make one; http://xdaforums.com/showthread.php?p=9217793 link has good info and even a pdf guide I believe. Another link; http://xdaforums.com/showpost.php?p=9040478&postcount=28

I had this happen to my phone, got it back by a boot load ;) of finagling with the battery, but the jig is the easiest method I know of. :cool:
[Captivate Android Development] cuddles11a:
help

i cant get master clear to work. help please? i got to every step but master clear never showed up.
[Captivate Android Development] tazman171:
You have to be booted into the phone's operating system and have USB debugging off Edit: ON , massive brain lag I guess with mass storage set in the usb settings for master clear to work. :cool:
[Captivate Android Development] agentfusion:
I just exchanged it for a new one. It was one of the random shut down defective ones anyway. Back to stock for now
[Captivate Android Development] spartan062984:
Actually.....

I believe USB Debugging has to be on. Now i have flashed a few ROMs myself, and Master Cleared quite a few times. If memory serves me well, I believe it does have to be on. Although it has been a while since my last Mod (back in the days when Cognition 2.0 was considered the $hiz), and things do change. So if it works for you then disregard my bantering in the wind. To quote DG:

Just making sure for MY knowledge as well.
[Captivate Android Development] tazman171:
Yeah, you're right, debugging on and booted into Op system, don't know what I was thinking about :confused:, other than the 20 other threads I'm posting in LOL. Good catch, edited the post. :cool:
[Captivate Android Development] spartan062984:
No worries, you watch my back, and i got yours. lol :cool:
[Captivate Android Development] CapMad:
was stuck in file analysis

I was stuck in file analysis, them I did all steps once again and everything went right !

Steps:

open Odin

remove battery, sd-card, SIM card

replace battery

hold up+down volume (never touch on/off button)

plug USB cabble (Download mode appears)

release up+down volume

click "Start" button, in 1 minute you will see it reboot and you have your captivate back just like new !

Now I am going to flash AXURA 2.5
[Captivate Android Development] GGXtreme:
Used this on my Captivate and after the phone auto-rebooted, it's semi-bricked (looping AT&T logo). Also, it no longer goes into download mode or recovery mode through any button combo (button combos were working fine before Odin), it just shows a frozen battery charging icon.

I'm trying to make a hardware jig, but USB-B tips don't fit into my Captivate at all, and the cable that came with the phone has a PCB in the tip that I haven't figured out yet.
[Captivate Android Development] opcow:
<sigh> another one-click victim. I don't know why the OP doesn't have a huge red waring that using this on most 1008 and all later batches will remove your recover and download mode button combos possibly leaving you in need of a hardware jig if things go wrong. It's stupidly irresponsible IMO--particularly in light of the fact that there is another way to flash back to stock and not lose the combo.
[Captivate Android Development] GGXtreme:
Found that out a bit too late :o My phone is batch 1010 I think. I was just following the instructions in the Cezar's ROM thread because doing things without the one-click step resulted in no phone/messaging apps on my Captivate. I'm working on getting a working jig now.
[Captivate Android Development] tazman171:
LOL, ;) Thanks, deal, and Happy New Year! :cool:
[Captivate Android Development] Mac11700:
Well...it works great with the 1012 builds...Had no problem at all doing mine..

Mac
[Captivate Android Development] opcow:
It works great right up until the day when it fails and you can't reflash.
[Captivate Android Development] GGXtreme:
Well I've managed to make a working hardware jig out of resistors, electrical tape and my own blood. The problem is, nothing I seem to flash in download mode with any version of Odin (including the 3-button fix version) seems to do anything. My phone is still stuck on the AT&T logo upon reboot, and recovery menu and download mode through the button combos are still disabled, requiring me to hold my awkward jig in place all over again. Is there any way I can fully restore my phone while in download mode *besides* Odin?
[Captivate Android Development] opcow:
There's heimdall. Does odin say everything succeeded? Are you running odin as administrator (explicitly, not just running from a user account with administrator privileges)? Have you tried odin version 1.7? Have you tried this? How about the JH7 odin flashable update?
[Captivate Android Development] GGXtreme:
Yes and yes. Eventually, I randomly flashed an old version of Cognition and it worked fine (although the recovery menu showed errors like "Data wipe failed"). Then I used Clockworkmod to restore a backup I had of Darky's 7.5, only now the power button no longer works to select things in the recovery menu. Not to get off-topic, but is there a simple fix for this? I can no longer use the recovery menu at all since I select anything, and Clockworkmod doesn't start unless I am able to select "apply sdcard:update.zip".
[Captivate Android Development] opcow:
Sounds like you have a kernel with a broken recovery. That happened to me once many moons ago and it was then that I, myself, discovered that the one-click had killed my button combos. Luckily, I was able to "adb reboot download" and reflash. You could try that, but you don't seem to be having good luck with odin. Maybe try the odin flashable JH7 or the C3P0LOL which will atleast flash a fixed sbl.bin (assuming they work at all). If you use the JH7 package you may need to use the 512 pit file and check the repartition option.
[Captivate Android Development] GGXtreme:
Can you possibly link me to any sort of factory reset or Odin-flashable stock ROM that *isn't* one-click? I'm able to flash ROMs with both the PIT and PDA files using normal Odin, but I can only find stock ROMs and none of them seem to fix my recovery menu. Master clear also doesn't work, it just says "Master clear started....." and nothing happens to the phone at all.
[Captivate Android Development] agentfusion:
Happened again with the new phone. Damnit. I get it back into download mode after bricking, but it always hangs or fails at the Factory step. One time, the screen on the phone turned completely yellow. I'm going to keep trying tonight until it either won't go into download mode after taking out the battery for a few minutes, or I get so frustrated I decide to give up until tomorrow.
[Captivate Android Development] opcow:
Master clear is done with the phone booted up to the ui and debugging on, if I recall. I linked C3P0LOL's stock ROM with the fix earlier. I897UCJH7 is the odin flashable version of the OTA update and I believe it also fixes the button combos.
[Captivate Android Development] GGXtreme:
I had tried C3P0LOL's ROM, but it had no different results than the once-click Odin in this thread (won't go past AT&T screen + disabled button combinations on boot). The I897UCJH7 says to flash JH6 first, but I can only find the kernel for JH6 (not the whole ROM), will I be fine flashing it over my messed up JPY custom ROM? Or is there somewhere I can find the entire stock JH6 ROM? Sorry to keep pestering you, but I'll be out of a phone for 2 years if I can't get this fixed.
[Captivate Android Development] opcow:
I hate to ask, but do you think you could make your sig a little more ginormous? Maybe you could add longcat?
[Captivate Android Development] opcow:
The C3P0LOL one has the entire ROM. You might try the pda.tar and pit.pit in that thread with a different odin flasher. Always run odin as administrator and be sure you have odin loaded up and ready to go before you plug the phone into the computer. Also, you may as well to pull your sim card and battery before flashing wait 30 seconds or so and put the battery back in (you shouldn't have to do that, but sometimes it helps).
[Captivate Android Development] GGXtreme:
Well, I think I made progress...sort of. I tried flashing the PDA.tar and PIT.pit file from C3P0LOL's thread using the Odin that successfully flashed Cognition (re-partition and auto reboot unchecked). After it completed, I pulled the battery, disconnected the USB, put the battery back in and powered the phone on. The screen shows a small green android in the upper left with some sort of speech bubble over it (the android and bubble are mostly obscured by red text including "RST_STAT = 0x4, PWIC_IRQ1 = 0x40..."). In large yellow text to the right of the android are the words, "KERNEL PANIC UPLOAD MODE". This never ends...

Edit: I flashed 2 kernel updates on top of the Kernel Panic-ed phone and even though it still gets Kernel Panic on boot, I was able to get into a fully-functioning 2e recovery screen, and then into Clockworkmod. So I restored back to the Darky 7.5 ROM. But that's not what I want to do, I want to reset my phone to a stock JF6 to try other ROMs! >_<
[Captivate Android Development] sn707:
I ran Odin with no problems. It finished, but I am having the grey battery when I try and get into download mode. It wont boot past the Att screen.

I have seen quite a few others reading through this thread with the same thing happen. My Captivate is batch 1010 and there is no recovery and no download mode. I tried the flashing black screen method also. Is a Jig my only hope?

Thanks guys, I have used Odin at least twice with no problems. I was just going to put it back to stock as I had a buyer for it today. Looks like that isnt going to work out...

As a note if anyone in the Los Angeles area has a jig I could buy or use give me a call 541-944-4774 (Oregon number,I just moved:)
[Captivate Android Development] opcow:
Yes, one-click victim number 4,973, you'll probably need a JIG.
[Captivate Android Development] mersinbebesi:
I unroot my phone installed CWM and try to install the gingerbread I put the files externel micro SD card

it was going well but it says there is a error on line xxx than it's stock on screen. I removed the battery

I tried 3 button and power button doesn't respond I tried the download mode It worked I was reading XDA pages

I installed your oddin software I installed the drivers and wauuv

I just bought beer man thank you it was brick and you save my phone have enjoy with you beer :D
[Captivate Android Development] ksimilie:
Does anyone know why this happens?
[Captivate Android Development] opcow:
Because the one-click flasher replaces the sbl with one that breaks the key combos on most batch 1008 phones and (as far as I know) all later batches.
[Captivate Android Development] GGXtreme:
I figured that much. However, does anyone know why the one-click fails to restore a working JF6 ROM on my Captivate? There are no errors in Odin (regular or one-click), it claims success and my phone no longer boots (3-button combo is suddenly disabled, requiring a jig). I've tried every method mentioned on this forum of flashing my Captivate back to stock Eclair, and none have worked so far. I have no problem flashing custom 2.2 and 2.2.1 ROM's including Darky's, Cezar's and Cognition, as well as custom kernels using Odin. I've even run stock Froyo before. My phone is batch 1010.

But I really would like to be able to fully restore my phone back to stock to work out some problems and cleanly flash ROM's, but I've gotten no help any of the other times I asked about this.
[Captivate Android Development] redeuxx:
I was wondering if I had to disable any lagfix when restoring to stock? ... or do I not have to?
[Captivate Android Development] ptdexter:
EasterEgg - Captivate powers down / sleeps and never wakes!

So I've got the captivate bonus feature where it turns itself off for no good reason. I have seen some people with sleep problems but I dont think this is a sleep problem. When I hold the power button for a sec or so when this has happened the phone begins to power up - but I never pull the battery. Also I do not have clockwerk installed.

Anyway I'm wondering if this is a ODIN Froyo 2.2 EasterEgg (I897UCJI6-OCD-REV02-Low is what I have running now) or if this is a hardware problem with the captivate (and will happen regardless of the firmware on the phone). Anyone know?

I dont necessarily need the Froyo ODIN firmware, its just what I first found and tried. Anyway if anyone else has any recommendations for ODIN firmwares I'm all ears. I'm looking for;

-Android 2.2 or newer (2.3 would be sexy)

-Speed

-Reliability

-Fully functioning (wifi/3g/etc...)

If there are "better" options out there I'm happy for any suggestions. Any help is appreciated, thanks.
[Captivate Android Development] nosenuggets45:
So I just ran this to flash back from an old Cognition build. However, it seems to have KILLED my button combos to get into recovery mode. What can I do here? I'm going to try to get into it via ADB, but even that is giving me troubles. I also can't get into download mode it seems, atm. Please, help, ANYONE.

EDIT: After a frustrating 20+ attempts and methods to get into Recovery Mode, I somehow managed it. Then the One-Click-Root didn't work, so I had to manually place the Update.zip onto the phone. Long story short, I'm booting up Darkys 7.8 ROM as we speak. Hope it all works.
[Captivate Android Development] Mac11700:
So..if this is the case..what is the proper way of flashing a new rom..and then returning to a stock state if need be ? You should start a thread and describe exactly what to do from the time of rooting to keep this from happening. I may have just gotten lucky 1 time...and don't really feel like pushing my luck needlessly.

Mac
[Captivate Android Development] GGXtreme:
Some posts in the other Odin thread indicate that for all Captivates batch 1008 to 1010, the closest you can get to stock is JH3 using Odin 1.7. Roms before JH3 (like JF6) and Odin one-click will NOT work.

Well...this sucks.

Edit: See my post below http://xdaforums.com/showpost.php?p=10309886&postcount=1469
[Captivate Android Development] opcow:
Glad you got it working. Do yourself a huge favor and never flash to stock again unless you really have to (and you never should unless something went horribly wrong). If you do need to go back then use the correct stock flasher that doesn't kill your button combos.

And, btw, since Darkyy's probably doesn't include sbl.bin (that's a good thing) you probably still don't have working combos.
[Captivate Android Development] Mac11700:
opcow...check your PM's

Mac
[Captivate Android Development] nosenuggets45:
So far so good. Just reinstalling everything with Titanium now. Somehow, magically, the button combo to get into the Recovery Mode works! No idea what happened there. The last thing I did was try to run the software update on the stock ROM, then all of a sudden, I could get into recovery mode via the buttons.

Pretty sure it isn't the tools fault, but last time I use ODIN willingly. That was a HUGE pia, 3 hours later.
[Captivate Android Development] opcow:
If you open up a few CWM flashable ROM zips you will see that they delete and format everything (this doesn't apply to no-wipe versions, of course, which are meant to be flashed over previous versions of the same ROM). Normally there is no need to flash to stock. Just flash the ROM. I do it all the time. I don't normally flash multiple ROMs a day, but I have probably flashed 6 times in the last 2 days. I never went to stock and I don't disable lagfix because Voodoo and ULV are compatible and CWM recovery understands ext4 (of course if you decide to flash a non lagfixed ROM the you should disable the lagfix). I flash one ROM on top of another.

If your drivers and USB are all working and you carefully follow the proper procedure the risk is probably small, but things can happen and it makes no sense to flash to stock when the benefit is nil and the cost is time and a significantly increased risk of bricking.
[Captivate Android Development] Mac11700:
OK...but answer me on this then please...

From what I have seen..most threads or recommendations have been as soon as one roots their phone..to do a back up of the original rom....

Now..IF...this is one of the newer builds that come with JH7 pre-installed from the factory..If one wanted to return to stock..couldn't one dis-able any voodoo, oc/uv,lag fix..and simply revert back to the first back up ?

Since this was already a back up of the original stock rom..

just rooted

...wouldn't this be the most logical thing to do..Then if a person has a need to return the phone for service or elects to sell it..they still can with out the need to do this.. ? Otherwise...why even bother doing a nand back up of the original rom in the first place..? Doing this..one would have to flash anything..just restore what they started out with ?

I've never been able to find a definite answer on this..since there have been so many people saying you need to flash to stock whenever starting on a new rom..and in my layman's eyes..since many have done exactly as I have..and did just this first..it would seem to be the easiest and safest solution to this issue..

While this may not have any bearing for those with earlier builds..it certainly does for those of us that have the later builds..

Mac
[Captivate Android Development] Mac11700:
There certainly needs to be some new warning in all the How to threads covering this subject for those just getting into rooting and flashing...The most I have seen is a brief mention of flashing a different Odin...If every custom rom thread this is suggested as the only approach prior to flashing their rom...they will be causing a lot of grief and frustration...

Also what should be included in those threads, Wiki's, How to Guides,FAQ's of the developers roms....

a complete explanation

of how to save the original Nav_bin files and save the original Android ID #..and how to reinstall them in the easiest manner...prior to flashing any custom rom...

Mac
[Captivate Android Development] opcow:
Yeah that's a good idea to save your /efs (nv_data.bin, etc)

Haven't tried it. I may flash to JH7 do a CWM backup and the flash Perception or something the try to restore over that. I suspect there may be problem doing a CWM restore of 2.1 over a 2.2 ROM, but like I said, I haven't tried that.

If it works yeah.

Yeah. Personally, that's a situation where I would just use Odin (just not the one-click from the OP). Odin is fine for what it's for. It's recommending it as a pre-ROM flashing routine that I think is wreckless. If you absolutely have to get back to bone stock then it may be the only way.

There was a time when, for example you had to flash to stock and use a certain modem drive to enable the 850 band before flashing i9000 ROMs. There may have been other reasons why it was once necessary.

I suspect it's mostly that people didn't know what other ROMs were doing to the filesystems and felt that flashing back to stock gave a common base starting point. That's an understandable philosophy, but there's really no voodoo going on in any of the ROMs I've used. The update scripts clean everything out if they work correctly and if they don't you certainly don't want old stock stuff hanging around any more than you do anything else.
[Captivate Android Development] GGXtreme:
For those with Batch 1008 through batch 1010 phones who cannot get Odin one-click to work:
[Captivate Android Development] Jamez0905:
While using Odin for the second time my phone went to a red screen during factoryfs.rfs step, I waited for 45 minutes and my phone was not doing anything. I pulled the battery and now my phone won't turn on, it just barely illuminates the screen on a black background when I try to...Have I bricked my phone? If so is there any fix?