Database Info

[Solved-BADUSB]I think I managed to brick this Captivate

I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.

So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.

Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.

hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.

I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.

Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.

Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.

If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App

jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.

Windows will not recognize my phone.

No matter what i do it will not recognize. I have reloaded the driver and i cannot get it to work. I want to go back to stock but can't get started

need a few more details. There are a few threads about this topic already, but if you have AWD launcher or Launcherpro active, Windows will not see the phone through Keis. You have to switch back to the Touchwiz UI and Keis will see the phone.
Hope this helps.

I rooted my phone last week. Then decided to do 2.2 ...when i went to do it my my pc would not recognize the phone. I finally got it to work by selecting mass storage in usb mode. I managed to get 2.2 loaded. Now i want to go back to stock before trying another rom. When i plug the phone to the pc it charges but the pc comes up as not recognizing the phone. When i do try to enter download mode by holding the volume buttons and putting in the usb the phone just boots.
thanks

I think i finally got it...i tried cleaning the contacts and it seems to be working! Sort of....its hit or miss....the other thing...if my phone shuts off the only way i get it on is by holding the volumes and power button and pluggin in a cable....what the heck is that about?

gpzjack said:
I think i finally got it...i tried cleaning the contacts and it seems to be working! Sort of....its hit or miss....the other thing...if my phone shuts off the only way i get it on is by holding the volumes and power button and pluggin in a cable....what the heck is that about?
Click to expand...
Click to collapse
Wow that's a new one. I too have had problems getting my phone connected in Windows. At first I never had a problem but after installing Kies Mini I have never been able to get my phone to connect properly. I'll work on it this week and post any suggestions to see we can get this figured out.

sola fide said:
Wow that's a new one. I too have had problems getting my phone connected in Windows. At first I never had a problem but after installing Kies Mini I have never been able to get my phone to connect properly. I'll work on it this week and post any suggestions to see we can get this figured out.
Click to expand...
Click to collapse
See if this will help http://forum.xda-developers.com/showthread.php?t=798365&highlight=patching

i'm not using kies. i have two of these phones. My wifes phone connects with no problem. I think its corrosion on the port as someone else on here described...phone is running well now but will only turn on by the three button method and plugging in a usb cable

Need To Restore Nexus S 4g

I have an extreme problem with my Nexus. I've been through thick and thin with this phone, and I'm hoping you guys will help with a solution to this problem.
The power button to my Nexus is broken completely. I stabbed it so much that the clicking black part is completely removed from the slot (on the motherboard).
One time, my Nexus S died, and I realized I had no way to turn it back on. I tried every single method (battery pulling, button pressing, USB connecting, etc) with no answer. I finally was able to find a solution. I used Odin to restore the bootloader tar md5 file, and thus auto rebooting the nexus (when the box is checked). This worked like a charm, until I realize I made a fatal mistake.
I chose an md5 file for the ORIGINAL Nexus S (not 4g).
I was able to easily go into recovery with Quick Boot from the Play Store. I installed Raspbean Jellybean (02-05-13 build), but the installation was very faulty. The home button is nonfunctional (it vibrates when pressed, but nothing happens) and Browser is not working as it just closes itself instantly. Like an idiot, I didn't install Gapps before rebooting into the ROM.
Stuck in that dilemma, I used the built in email app to sync my Gmail account to the phone. I sent a Quick Boot APK to myself to try and open so I could reach recovery, but it said there's no type of program that can open that file (maybe because Gapps isn't installed).
The last thing I tried was Odin again. I tried to restore the ICS release keys, but Odin will not recognize my phone anymore for nothing. I tried 3 different USBs (2 with shorts, and 1 normal one. I don't know if the type of USB has anything to do with it). Nothing.
So here I am with a faulty, Gappless ROM on my Nexus S 4G with a completely broken power.
I'm wondering if you guys have any solution/suggestion to get Odin to recognize my phone again so I can restore it and work from there.
Apart from that, ANY solution to this problem is highly acceptable and greatly appreciated (ways to get into recovery, etc). I don't want this to be the last of me and my sweet ole Nexus =(,
Thanks x1000 XDA!

Hey Guys. I was actually able to reach recovery, because the ROM I'm using has a Power Menu widget in it's quick settings (Go Figure). But my phone is still unable to be recognized by Odin in Download mode. The phone is also not recognized by my pc at all. It only charges, no matter what USB I try. I even tried mounting in recovery, no go.
Please help. Thanks!

[Q] SGH-1727 overheating battery and Odin issue

I have a SGH-1727 running cm10.1 nightlies and ever since I flashed to cm10.1 my battery just goes nuts. It constantly overheats and drains 30% in a matter of minutes. I have swapped in a new battery same issue. I set the CPU gov to conservative and limit background processes to 4, still happens. I set a plain wallpaper and set screen brightness to dimmest possible, disable wifi bluetooth etc. disable haptic feedback and vibration and backlights. Still happens. I downloaded some battery app and it said I didn't have any crazy partial wakelocks and I shut almost all my syncing and my battery gets to about 105 degree and drains crazy fast. So I figured it has to be something with the kernal and or cm10.1 so I went to do a full wipe and unroot and reflash the stock rom put my phone into download mode opened Odin and it wasn't there. I have reinstalled kies 3 times I have even just installed just the drivers 3 times, I have tried 3 different computers running win 7 and 8. I am using a samsung cable, I have tried different USB ports and every time I plug my phone in it is not recognized by my computer. USB debugging is set up and frankly I am at a loss to why both of these issues are occurring. Any help would be greatly appreciated.

Have you tried with the stock USB cable that came with the phone? The last time I used Odin I couldn't get the phone recognized no matter what (I was having similar issues to you), but when I tried the stock cable it worked perfectly.

sailicalvin said:
I have a SGH-1727 running cm10.1 nightlies and ever since I flashed to cm10.1 my battery just goes nuts. It constantly overheats and drains 30% in a matter of minutes. I have swapped in a new battery same issue. I set the CPU gov to conservative and limit background processes to 4, still happens. I set a plain wallpaper and set screen brightness to dimmest possible, disable wifi bluetooth etc. disable haptic feedback and vibration and backlights. Still happens. I downloaded some battery app and it said I didn't have any crazy partial wakelocks and I shut almost all my syncing and my battery gets to about 105 degree and drains crazy fast. So I figured it has to be something with the kernal and or cm10.1 so I went to do a full wipe and unroot and reflash the stock rom put my phone into download mode opened Odin and it wasn't there. I have reinstalled kies 3 times I have even just installed just the drivers 3 times, I have tried 3 different computers running win 7 and 8. I am using a samsung cable, I have tried different USB ports and every time I plug my phone in it is not recognized by my computer. USB debugging is set up and frankly I am at a loss to why both of these issues are occurring. Any help would be greatly appreciated.
Click to expand...
Click to collapse
1. Disconnect your phone.
2. Uninstall the Samsung USB drivers app from your PC (you do have this installed, right?)
3. Google for the latest drivers for the Skyrocket and download them. Don't install yet.
4. Download USBDeview from here (pick either x86 or x64, depending on your OS)
5. Open it up, highlight everything that says Samnsung and uninstall them.
6. Reboot. (don't skip this step)
7. Install the latest official Samsung USB drivers you downloaded in step 3.
8. Reboot (don't skip this step)
9. Connect your phone directly to a USB port on the back your computer. DON'T use a hub or a front connector port.
10. Let the driver install wizard do it's thing. Check Device Manager and see if any drivers failed to install.
11. If everything installed, ODIN should work. If not, you could have a bad port on your phone, a bad cable, or something else.
Good luck.

Add ,
12.Stock Rogers JB rom (tar format) from sammobile does not odin flash on the skyrocket I727..

taranis17 said:
1. Disconnect your phone.
2. Uninstall the Samsung USB drivers app from your PC (you do have this installed, right?)
3. Google for the latest drivers for the Skyrocket and download them. Don't install yet.
4. Download USBDeview from here (pick either x86 or x64, depending on your OS)
5. Open it up, highlight everything that says Samnsung and uninstall them.
6. Reboot. (don't skip this step)
7. Install the latest official Samsung USB drivers you downloaded in step 3.
8. Reboot (don't skip this step)
9. Connect your phone directly to a USB port on the back your computer. DON'T use a hub or a front connector port.
10. Let the driver install wizard do it's thing. Check Device Manager and see if any drivers failed to install.
11. If everything installed, ODIN should work. If not, you could have a bad port on your phone, a bad cable, or something else.
Good luck.
Click to expand...
Click to collapse
So I follow these instructions to the T and no dice. I have been using the original USB cable that came with the phone and I have also tried another Samsung USB cable. Every time I plug the phone in it says that this is an unrecognized device.
Just a thought, this phone has been rooted and flashed multiple times however the flash count is 0 and the it says it has the stock samsung OS. Would a ROM issue cause my phone to be "unidentifiable?"

Try on a different pc

mahanddeem said:
Try on a different pc
Click to expand...
Click to collapse
Did that with the same issue.

Something is borked in your driver library. You'll have to manually select the right drivers in DM. No PNP for you it seems...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

taranis17 said:
Something is borked in your driver library. You'll have to manually select the right drivers in DM. No PNP for you it seems...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
It seems like a driver issue but I have tried to connect it to 5 different computers all running different OSs and it is still not recognized. Is it possible the ROM screwed up the device ID or something along those lines?

im basically in the same boat, my phone was running CM 10.1 for a while no problem, but then i suddenly started getting major overheating and battery drain issues.
when i tried to restore to stock, my pc did recognize my phone, but ODIN kept failing. I had to do it literally about 20 times. I did manage to restore to stock in ODIN but still having the same issues, although not quite as bad.
I did try to go back to CM 10.1 again to see if that made a difference and it got worse again with overheating and battery drain. When i tried to root it, it again kept failing in ODIN and i had to do it many times until it worked.
I went back to stock second time, again odin kept failing and had to do it many times. It still has overheating and batter issues. but its manageable with two batterires and frequent charging.
one thing with charging is it will overheat and stop charging unless i charge with back cover off ( still charges slow) or just turn the phone off and charge (charges fast)

captainsurrey said:
im basically in the same boat, my phone was running CM 10.1 for a while no problem, but then i suddenly started getting major overheating and battery drain issues.
when i tried to restore to stock, my pc did recognize my phone, but ODIN kept failing. I had to do it literally about 20 times. I did manage to restore to stock in ODIN but still having the same issues, although not quite as bad.
I did try to go back to CM 10.1 again to see if that made a difference and it got worse again with overheating and battery drain. When i tried to root it, it again kept failing in ODIN and i had to do it many times until it worked.
I went back to stock second time, again odin kept failing and had to do it many times. It still has overheating and batter issues. but its manageable with two batterires and frequent charging.
one thing with charging is it will overheat and stop charging unless i charge with back cover off ( still charges slow) or just turn the phone off and charge (charges fast)
Click to expand...
Click to collapse
How did you get the device to be recognized by the PC and ODIN?

[Q] Bricked worse than I thought? Help! (long)

Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,

JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
Interesting problem. I have bricked my phone a bunch of times and have always been able to get back to at least "download Mode". The method I use to go to "Download Mode" is With the usb cable plugged into the computer only, power off the phone. If phone wont power off, or stay powered off, pull battery, then put battery back in. Now hold vol down and vol up buttons only, keep holding these buttons as you plug the usb cable into the phone. In 3 seconds the download screen should appear. I hope this helps you get your phone back.

JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
This sounds like a time where a jig would be helpful. Any chance you can have your wife order one, and send to you? http://www.youtube.com/watch?v=D7I4dFX_iJ4
This should put you straight into download mode, and you can then flash.

Thanks, guys. I continued fiddling and got the phone into DL mode.
I also noted that when plugging and unplugging the phone, it would show up in zadig as "unknown device."
I tried to load the drivers on that, but (a) it still shows up as "unknown device" and (b) when I run HOC it doesn't see the phone under the list of compatible devices.
So.... still kind of stuck.
Any more ideas?

Oop. duplicate post

It's been awhile since I've played with the one clicks, but, "serial gadget" is what I remember seeing when I used them.

Right. MORE messing around later and "Serial Gadget" is it.
That said, I still think I have a driver issue. I have tried uninstalling and reinstalling the zadig-recommended drivers for Serial Gadget several times. I also tried manually installing the drivers from Super One Click.
Anyway, now when I load up HOC I get the green <<connected>> at bottom; but then sometimes it wants me to install the drivers (again) and sometimes it gets past that part, but then goes to
Flashing Kernel: 0%
...hangs there for about 10 seconds and then
Failed!
So... driver thing you think?
Thanks again,

If you reboot the phone after the 0% hanging for 10 seconds, does it go to the yellow exclamation mark screen? If so, just reflash again and you should be back to working... both my and my wife's phone always did that when I had to flash a kernel.

That's just another download screen that theraze is describing.

Exacatly. But the alternate download screen always came up after restarting the phone after a 'failed' flash where it stayed at 0% where it was successfully communicating through the cable. That just meant to not break the drivers or unplug anything... just reboot fast and finish up quickly.

Okay - I can definitely try that! It had not occurred to me to try and reboot the phone right then.
Question, though - when I get the "Failed!" Then HOC essentially hangs, when it says something along the lines of "ending session..." and never progresses from there. So how do you "restart quickly?" Because I have to like, close and reopen HOC. I guess I will see if it succeeds at ending the session when I reboot.
I will try it again. Strange though, sometimes HOC accepts the existing driver (I managed to DL the Samsung driver installer) and sometimes it wants to reinstall "WinUSB." does that make sense? Is the WinUSB an acceptable one?

The winusb is the right driver for heimdall, it doesn't like the Samsung driver.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Samsung drivers and the one click drivers clash. Yes, uninstall Samsung completely if you want to use the one click.

Hm. Thanks for that - might be part of the problem.
Dunno what I did differently, if anything, but last night I tried flashing again and this time it went through! I was very glad to see the whole HOC process completed successfully!
So anyway - thanks so much for the help, guys.