Database Info

[Q] Phone not recognizing USB cord at all

I'm running Darky's 6.0 Rom with xcaliburinhand's kernel. I began to realize my phone wouldn't charge when I plugged it into the charger. I tried flashing to stock using odin but once I'd get into download mode via the long-press menu when pressing the power button (because other methods that involve plugging in the cord and pushing buttons doesn't work since it's not recognizing the cable). I don't think it's a faulty cable or port since everything was working before I flashed the ROM. Anyone have any ideas on how to get the computer to recognize the phone so I can flash stock??
edit: When I do plug in the phone to the computer, I'll sometimes get a message saying the device isn't recognized.
(And yes I do have drivers installed.)
Also, I tried flashing other ROMs via CWM but I get error messages on all that I try. Such as can't mount .dev/block/st19 and can't mount SYSTEM
Edit: After a while I've noticed that it in fact is charging but the battery icon doesn't show it's charging. And in settings it shows it's not charging. But battery level is increasing

Have you tried a different computer to see if the usb port is bad?
Sent from my SAMSUNG-SGH-I897 using XDA App

Does it charge when you plug it into an ac adapter? You can also try reinstalling the drivers and see if that helps and/or try a different usb port. I've had issues with the drivers before.

Also try a different cable. My cable became defective somehow where xp no longer recognized it, yet would still show charging on the phone. All was back to normal after I got another "data/sync" cable.
Sent from my SAMSUNG-SGH-I897 using XDA App

I don't have a different computer to try it on but I've tried different ports. It's not the computer because it still won't show it's charging when I plug into the wall. And yes I think it does charge when it's plugged into a wall but it doesn't show it or turn on when I plug the cord into the phone. I don't think it's hardware. It has to be software since it just happened when I flashed the ROM. Also whenever I open contacts I get a force close of acore (a little off-topic, but still another issue). I also have tried reinstalling drivers. But also, it doesn't work when plugged into a wall charger. So it's definitely nothing with the computer

I just need to know if anyone knows how to force the computer to recognize the phone so I can flash to stock and hopefully that'll resolve the issue
update: I also tried v7 via CWM and no luck still.

Well I update xcaliburinhand's kernel by transferring it over bluetooth and that installed fine over CWM. Then I tried updating Darky's rom to v7 and that worked too. I booted up and got a million FC's. Tried to get into recovery and it just sits at AT&T screen. It's very tricky to even boot up the phone, and even when I do I can't do anything because of all the Force closes. I can't get back into recovery mode with any button combinations and when i try via the power long press I can get into download mode fine, but I still have the issue with the computer not recognizing it, so it's useless. Anyone have any ideas????? I'm getting sick at staring at this AT&T boot screen for so long. I have no idea of what to do next. Someone please help!!

Sorry to say it, but it sounds like your phone has serious hardware problems.

opcow said:
Sorry to say it, but it sounds like your phone has serious hardware problems.
Click to expand...
Click to collapse
Is there nothing I can do? Because I'm pretty sure I'm way past return date, and I didn't have a warranty.

well it sounds that you have messed it up. your installation is probably wrong somewhere, in fact i am even sure, but i dont want to hurt anybody.
do a clean install from scratch starting everything with ODIN (ie download mode)
first off all load a ancien but correct kernel, because in fact you don't even know what you lagfix is. load one of the zenkins kernels (ya-ok) no matter one of the recent ones.
start and go back into recovery, and adjust lagfix to ext4 only. not ext4/ext2
don't use not either the integrated voodoo.
it will format everything.
the again into recovery and disable lagfix
that will then reformat everything into rfs, that what it's needed.
then you go again into reboot and flash one of the ancien .tar files like xwjpa.
and then it shoudl startup.
and you can take it from there.

zoubidou said:
well it sounds that you have messed it up. your installation is probably wrong somewhere, in fact i am even sure, but i dont want to hurt anybody.
do a clean install from scratch starting everything with ODIN (ie download mode)
first off all load a ancien but correct kernel, because in fact you don't even know what you lagfix is. load one of the zenkins kernels (ya-ok) no matter one of the recent ones.
start and go back into recovery, and adjust lagfix to ext4 only. not ext4/ext2
don't use not either the integrated voodoo.
it will format everything.
the again into recovery and disable lagfix
that will then reformat everything into rfs, that what it's needed.
then you go again into reboot and flash one of the ancien .tar files like xwjpa.
and then it shoudl startup.
and you can take it from there.
Click to expand...
Click to collapse
Please read earlier posts... I cannot get into recovery mode and the computer won't recognize download mode.

mikel.canovas said:
Is there nothing I can do? Because I'm pretty sure I'm way past return date, and I didn't have a warranty.
Click to expand...
Click to collapse
Unless you have a bad USB cable causing all the weirdness with both charging and the PC connection, but that wouldn't explain all the other strange errors. It sounds to me like the phone is terminally ill.

opcow said:
Unless you have a bad USB cable causing all the weirdness with both charging and the PC connection, but that wouldn't explain all the other strange errors. It sounds to me like the phone is terminally ill.
Click to expand...
Click to collapse
Doesn't there have to be a way to revert to stock if it's all because of the ROM? I really don't want to just give up and throw away a semi-new Captivate and have to break contract to buy another one.

mikel.canovas said:
Doesn't there have to be a way to revert to stock if it's all because of the ROM? I really don't want to just give up and throw away a semi-new Captivate and have to break contract to buy another one.
Click to expand...
Click to collapse
I've seen no accounts of bad flashes causing problems like you described. Particularly the phone not being detected in download mode and the AC charging funkiness. Besides, you already tried reflashing it and not only did that not help, it revealed all sorts of other symptoms.

opcow said:
I've seen no accounts of bad flashes causing problems like you described. Particularly the phone not being detected in download mode and the AC charging funkiness. Besides, you already tried reflashing it and not only did that not help, it revealed all sorts of other symptoms.
Click to expand...
Click to collapse
Ok. Thanks. If anyone else has any other ideas. Please post

I've had the Captivate for around 4 months. Does anyone know if I short out the phone and say it got really hot then shut off, they will exchange it?

mikel.canovas said:
I've had the Captivate for around 4 months. Does anyone know if I short out the phone and say it got really hot then shut off, they will exchange it?
Click to expand...
Click to collapse
Or you could just rob a liquor store and use the proceeds to buy a new one.

[Q] Stuck

I have searched the threads but I haven't found something similar and if there is I apologize and point me in the right direction.
I have been running VEGAn Ginger Edition but decided to give Calkulins a try. Followed all the instructions and everything booted fine. I used it for a day then the next when I tried to boot the backlight turned on and nothing else. Tried going into CWM but wouldn't take. Tried turning it on and leaving it alone for a while but it didn't do anything. I plugged it into my computer to try NVFlash but my computer wouldn't recognize it. Any help would be much appreciated.

Hey I just want to probe a bit to maybe lend a hand... You say"it wouldn't take" in cwm what do you mean? What happens when you boot recovery?
Sent from my MB860 using XDA App

You may also want to try and hold down the power button for four or five seconds and try to 'force' a shutdown. Then try and turn it back on.

aver2one said:
Hey I just want to probe a bit to maybe lend a hand... You say"it wouldn't take" in cwm what do you mean? What happens when you boot recovery?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
When I hold the power button and the volume + button the backlight will turn on and it will not enter recovery mode. Only the back light will turn on, that is it

Zaphod-Beeblebrox said:
You may also want to try and hold down the power button for four or five seconds and try to 'force' a shutdown. Then try and turn it back on.
Click to expand...
Click to collapse
I tried that, but I wasn't for sure that it actually shut down so then I left it on overnight to drain the battery. This morning when I checked it the backlight wouldn't even turn on. I hooked it up to the charger and same thing, backlight only, won't be detected by Windows when plugged in.

ralien1983 said:
When I hold the power button and the volume + button the backlight will turn on and it will not enter recovery mode. Only the back light will turn on, that is it
Click to expand...
Click to collapse
ralien1983 said:
I tried that, but I wasn't for sure that it actually shut down so then I left it on overnight to drain the battery. This morning when I checked it the backlight wouldn't even turn on. I hooked it up to the charger and same thing, backlight only, won't be detected by Windows when plugged in.
Click to expand...
Click to collapse
Sounds like a softbrick!
NVFLASH to get back to stock,....then........ start over...
You will need windows/linux to be able to detect the GTAB via APX mode first.

tekrhino said:
Sounds like a softbrick!
NVFLASH to get back to stock,....then........ start over...
Click to expand...
Click to collapse
I thought I had to have the Gtab connected to my computer to NVFlash. If that is the case then my problem is that my computer will not recognize that the Gtab is connected.

ralien1983 said:
I tried that, but I wasn't for sure that it actually shut down so then I left it on overnight to drain the battery. This morning when I checked it the backlight wouldn't even turn on. I hooked it up to the charger and same thing, backlight only, won't be detected by Windows when plugged in.
Click to expand...
Click to collapse
ralien1983 said:
I thought I had to have the Gtab connected to my computer to NVFlash. If that is the case then my problem is that my computer will not recognize that the Gtab is connected.
Click to expand...
Click to collapse
You will need windows/linux to be able to detect the GTAB via APX mode first.

I have my Gtab plugged in to both power and USB mini. When I try to run nvflash_gtablet.bat it says there is no device connected. When I look at device manager there is no APX listed. What next?

ralien1983 said:
I have my Gtab plugged in to both power and USB mini. When I try to run nvflash_gtablet.bat it says there is no device connected. When I look at device manager there is no APX listed. What next?
Click to expand...
Click to collapse
You need to follow the instructions for NVFLASH.. they include instructions on how to get APX drivers working on your pc..

tekrhino said:
You need to follow the instructions for NVFLASH.. they include instructions on how to get APX drivers working on your pc..
Click to expand...
Click to collapse
Yes tekrhino is right you def need nvflash ...first fix the usb issue there's a ot of threads discussing how to fix usb issues like this http://forum.xda-developers.com/showthread.php?t=989320

Thanks everyone. Little user error made that harder than it should have been.

TF not connecting to PC / Can't get into APX mode

Used Nvflash to root a while back ago. Worked flawlessly.
Started having problems where the TF was not connecting up to the PC (both laptop and desktop). No problems charging. I know there's something going on cause when I plug the TF into the USB port, the screen comes on. When I unplug it the screen comes on.
Thought it possibly was the the ROM (Prime 1.7). Wiped caches and re-installed. Nothing. Wiped data & caches and re-installed Prime 1.7 from scratch. Nothing. Wiped data & caches and installed Prime 1.6. Nothing.
Everything works fine other than I cannot get the TF connected (detected) on the PC and I cannot get into APX mode. I'm sure they're related. Did a search for not being able to get into APX mode and found a couple but no help.
I can get into recovery and see the tf in adb. Don't know what else I should be looking at.
[Update]
Just got the TF back from Asus. Missed it sooo much.
The ticket inside said they couldn't find any problems with it.
By the time the TF was off to Asus, I got my extra charger and cable. Tried the new usb cable and bam, device found. Most likely I was in APX mode but due to the cable, would have never known. The odd thing is the cable charges both the TF and the dock perfectly. All that for a f-n cable.
Now I'm fighting with Asus to replace my cable.
I hope this finds its way into others having the same issue.

Are you trying with a Linux machine or Windows?
Make sur you have all the required drivers installed for windows. APX requires additional ones....
On linux you will not see the device automatically when in APX but you can execute the nvflash script

Unfortunately I only have Windows machines.
When I press Volume Up + Power, I get nothing. It doesn't detect there's an APX device in my device manager for me to even install the drivers.
Also tired Volume Up + Volume Down + Power and nothing

Went back to total stock and I still can't get into APX mode and can't connect to the PC.
Talked to Asus support and they're stumped. Was told they had to research and get back to me.
Sent from my HTC Glacier using XDA Premium App

This just happened to me. I booted HC then went to applications. Disabled/re-enabled USB debugging, then I went to device manager on windows and clicked "Scan for Hardware changes". It worked after that.

Tried that method as well.
Sent it off to Asus on a RMA. Crossing my fingers
Sent from my HTC Glacier using XDA Premium App

So this just randomly happens to me the day before I am supposed to sell it to someone. I went to nvflash it back to stock and noticed this issue. You said you restored it back to stock before you sent the RMA in, how did you go about doing so? I'd like to get it fixed so I can sell a functional unit.
Thanks

I'm also facing the same problem with my pc/laptop not detecting the TF101. The service center is of no help and they just give me the usual answers - try other pc, check the cable etc.
Moreover, I cannot go into recovery mode even with all the necessary drivers installed. Only a green droid with an exclamation mark.
I've no problem rooting the tf on older firmware. Wondering if the bootloader is locked.

I think it sounds like the usb cable as the op said it fixed his issue. I'm looking around for one to test on.
Sent from my DROID BIONIC using xda premium

Im on prime 1.7 and just experienced difficulty connecting, but can still charge. I just started the troubleshooting and found this thread. Disappointed, yet happy that its probably only the cable.

Well do you get any response from your computer? Anything, like a sound? a error installing drivers? a unknown device? Are you using the docking keyboard? Also this may not be the case but make sure you dont have a USB hub or anything extra on it. You can also try connecting it to the computer and open device manager and click scan for hardware changes. See if something new comes up. I have a couple more extensive ways of testing but let me know if this helps.

frankc123 said:
Well do you get any response from your computer? Anything, like a sound? a error installing drivers? a unknown device? Are you using the docking keyboard? Also this may not be the case but make sure you dont have a USB hub or anything extra on it. You can also try connecting it to the computer and open device manager and click scan for hardware changes. See if something new comes up. I have a couple more extensive ways of testing but let me know if this helps.
Click to expand...
Click to collapse
I recently tried to flash to different rom and got stuck in the Asus screen. And now I can't do anything with the tablet. It only shows as unknown devices on my pc. Any thought what happened and how to fixed it? I'm really appreciate your help

Tablet unplugged during NVFLASH

So my tablet got unplugged during the NVFLASH process shortly after formatting the partitions. It is now stuck in NVFLASH. Is there anyway I can reboot it or do I need to wait for the battery to drain and for it to die.
I have been having problems with my power button not responding when pressed so I filed for an RMA. They said to send it back but I wanted to flash back to stock before sending it. Could I send it to them like this ans say that it just stopped working or do I need to reflash to stock. Its a B50 so I know it can be fixed I just dont want to waste time waiting.

If you still have service on your tf they will repair your power button , i don't know if they flash new software files because of your button. What i do know they have to test your button and then they will see that it won't boot.
So with a bit of luck they will flash new files bcause of the whole startup problem with the power button.
Good luck

Let the battery drain, and NVFlash to stock. It will seriously help if you don't want to deal with any crap if they see you were rooted.

You don't have to let the battery drain.
When I bricked mine, my battery was low when I started the nvflash process, then the process failed b/c I forgot to put the files where they were needed, so I unplugged my transformer, let it charge for a little bit more so the battery wouldn't die while I found the files needed, then I plugged it back into my laptop and did a reboot into nvflash and let it do it's thing.

So I am having a weird issue with nvflash; it randomly quits mid-process. Sometimes nvflash stops when initializing the boot loader while other times it starts formatting the partitions and then stops. A few times it has even kicked my tablet out of apx mode.
Has this ever happened to anyone?

Is your cable bad? That's all I could think of, try several different USB ports as well.

Thing O Doom said:
Is your cable bad? That's all I could think of, try several different USB ports as well.
Click to expand...
Click to collapse
I tried multiple usb ports on two different computers. My macbook running ubuntu and a windows pc both have the same issue. I will try using another cable but dont know if that will help.
If I send the tablet back in this condition (no OS and NVFLASH not working), will they say its user error?

So I was never able to get the tablet to boot up. I am not sure what the issue was but I believe that the battery was almost dead but not quite. This left the tablet in nvflash mode, unable to charge. When I tried to transmit data however, it created too much of a load on the tablet and it would fail. I sent the tablet to asus as is and I just got a notification that they fixed everything and are sending it back to me. In case somebody is in the same situation as me it seems they did not care that all the partitions were formatted blank, just that there was no custom rom installed.

Good that it was resolve, and that they didn't give you any trouble.

[Q] Odin won't recognize phone after botched flash

So I'm stumped... I've flashed my Charge many times, no problems until now.
I wanted to flash back to stock ROM and had my Samsung drivers installed and Odin recognizing the phone and everything was good, but then Odin was taking WAAAAAAY too long. In the past this usually took about 20 mins. This time, after 45 mins and the progress bar hanging in the same place for 30+ mins on factory.rfs I disconnected the phone (I know this is where I screwed up). Now Odin won't recognize the phone at all. It does get into download mode, but Odin won't pick it up.
Same computer, same cable, and same USB ports as I've had when flashing this phone many times before. I don't know what my options are now. I don't think I can flash either the ROM or PIT without Odin at least recognizing the phone. What can I do now?

So I've done some more tinkering - trying different cords, multiple computers, uninstall/reinstall different drivers... What I've noticed on more than one computer is that Odin doesn't recognize the phone when it's in download mode ONLY.
If I power on the phone Odin is able to detect it and windows detects it as a Samsung USB device (even though the phone hangs on the Samsung logo). When I put it into download mode both the computer and Odin don't recognize it.

dragonlady726 said:
So I've done some more tinkering - trying different cords, multiple computers, uninstall/reinstall different drivers... What I've noticed on more than one computer is that Odin doesn't recognize the phone when it's in download mode ONLY.
If I power on the phone Odin is able to detect it and windows detects it as a Samsung USB device (even though the phone hangs on the Samsung logo). When I put it into download mode both the computer and Odin don't recognize it.
Click to expand...
Click to collapse
FWIW, I've also noticed a simple computer reboot fixes it....

jco23 said:
FWIW, I've also noticed a simple computer reboot fixes it....
Click to expand...
Click to collapse
I neglected to mention in my OP that I was going through the right protocol with driver uninstall/reinstall and rebooting each time. I rebooted again for good measure after seeing your post but I still get the same.
It's the same result from two different computers, one with Win7 and the other XP (I read in another thread that XP had worked better for some). If the phone is powered on, even though it doesn't successfully boot, Odin and Windows recognize it properly. If it's in download mode neither one recognize it, windows says the device failed to start and shows either unrecognized device or "Gadget Serial" (which would be a great name for a band, but google searches for it aren't much help).
I don't think it's a driver problem because it's recognized when the phone is powered on. But could there be a specific driver out there for the phone when in download mode only? I've flashed this phone dozens of times and never had a problem until now. I'm on the verge of forking over the $50 and sending it to JTAG if no one can suggest something else to try. Please help

did you make sure your phone is in debugging mode?... i forget who flashed what... or where I read something about flashing and it turned off their debugging mode...so check that first...and try reinstalling Odin on your computer... i don't think jtag is necessary on a Droid charge... if your phone is being recognized then it seems your missing a step...like maybe pulling your battery before hooking up the usb... or reinstalling the battery after going in download mode... and last of all check and make sure your not accidentally making mistakes when setting up your Odin before flashing... and last efforts to get a working phone would be going into cwm... volume up... home... and power button... hold while powering up and releasing on the second Samsung logo...and install your last back up...or reflash your rom with cache and dalvik wipes
Sent from my SCH-I510 using xda premium

curious, when you are/were performing the Odin process, were you still using the computer (web-surfing, e-mail, etc.)? in my experience, whenever I tried to multi-task on my computer while running Odin on my phone, Odin freezes. this has happened on more than one occasion. also, my toddler daughter even pressed the power button while Odin was running - so on three separate occasions, I've had a reflash interrupted. however, I've clearly been able to recover.
the key was using the right cord in the right port. I had one cord working fine for awhile, but then when I switched cords, it worked again.
also, some folks have had better success when removing the battery during the process.
finally, what are your steps exactly when flashing - and which guide are you using?

lukegman said:
did you make sure your phone is in debugging mode?... i forget who flashed what... or where I read something about flashing and it turned off their debugging mode...so check that first...and try reinstalling Odin on your computer... i don't think jtag is necessary on a Droid charge... if your phone is being recognized then it seems your missing a step...like maybe pulling your battery before hooking up the usb... or reinstalling the battery after going in download mode... and last of all check and make sure your not accidentally making mistakes when setting up your Odin before flashing... and last efforts to get a working phone would be going into cwm... volume up... home... and power button... hold while powering up and releasing on the second Samsung logo...and install your last back up...or reflash your rom with cache and dalvik wipes
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
I can't actually get the phone to boot (doesn't get past Samsung logo) so I don't know how I can tell if it's in debugging mode or how to change it if it's not.
Going in to download mode I've tried both battery in and out, using multiple USB ports and cables and can't get any version of Odin to detect it. I've tried v1.82 and 1.85 of Odin. I get the same result for both - Odin does not detect the phone when in download mode, but will detect it if it's powered on or just connected to the computer with battery in to "charge." But afaik I can't flash it when it's NOT in download mode
It won't boot into into recovery either... It never gets past Samsung logo no matter how long I hold the buttons... I've used recovery before, so I'm sure I'm giving the android 3-finger salute correctly.
I'm thinking maybe I got unlucky because the whole key to flashing is having Odin recognize the phone in download mode and that's the only time that Odin won't recognize it.
jco23 said:
curious, when you are/were performing the Odin process, were you still using the computer (web-surfing, e-mail, etc.)? in my experience, whenever I tried to multi-task on my computer while running Odin on my phone, Odin freezes. this has happened on more than one occasion. also, my toddler daughter even pressed the power button while Odin was running - so on three separate occasions, I've had a reflash interrupted. however, I've clearly been able to recover.
the key was using the right cord in the right port. I had one cord working fine for awhile, but then when I switched cords, it worked again.
also, some folks have had better success when removing the battery during the process.
finally, what are your steps exactly when flashing - and which guide are you using?
Click to expand...
Click to collapse
I wasn't actively multitasking during the bad flash, although I may have had email running in the background. Since then I've been rebooting and only had Odin running in the foreground when trying. I did use multiple usb ports/cables and try going into download with battery in/out.
As far as guides go, I had been using trparky's awesome guide for years until he took it down and lately went to the one in the dev forum here on xda: http://forum.xda-developers.com/showthread.php?t=1160580
Like I said, I'm thinking maybe I got unlucky because Odin recognizes the phone when plugged into the computer EXCEPT when it's in download mode and without that I don't know what else to do.

dragonlady726 said:
I can't actually get the phone to boot (doesn't get past Samsung logo) so I don't know how I can tell if it's in debugging mode or how to change it if it's not.
Going in to download mode I've tried both battery in and out, using multiple USB ports and cables and can't get any version of Odin to detect it. I've tried v1.82 and 1.85 of Odin. I get the same result for both - Odin does not detect the phone when in download mode, but will detect it if it's powered on or just connected to the computer with battery in to "charge." But afaik I can't flash it when it's NOT in download mode
It won't boot into into recovery either... It never gets past Samsung logo no matter how long I hold the buttons... I've used recovery before, so I'm sure I'm giving the android 3-finger salute correctly.
I'm thinking maybe I got unlucky because the whole key to flashing is having Odin recognize the phone in download mode and that's the only time that Odin won't recognize it.
I wasn't actively multitasking during the bad flash, although I may have had email running in the background. Since then I've been rebooting and only had Odin running in the foreground when trying. I did use multiple usb ports/cables and try going into download with battery in/out.
As far as guides go, I had been using trparky's awesome guide for years until he took it down and lately went to the one in the dev forum here on xda: http://forum.xda-developers.com/showthread.php?t=1160580
Like I said, I'm thinking maybe I got unlucky because Odin recognizes the phone when plugged into the computer EXCEPT when it's in download mode and without that I don't know what else to do.
Click to expand...
Click to collapse
Also, are you sure you have enough battery juice? To make sure, leave it plugged in to a wall outlet for about 30 min to an hour.
tappin' that....

Finally fixed - Bad USB port
Just to close out the thread, I did finally get my phone fixed. The issue was a bad USB port that decided to fail during flash. This is according to Josh from MobileTechVideos, who is a great guy with amazing customer service.
Longer version: I sent it off to MobileTechVideos/JTAG and after a week I got a call back saying the JTAG process didn't work and as a last resort they could try replacing the USB port itself. Josh told me that it was either the port or the controller, that the port was a known failure point on the Charge, and if replacing the port didn't work it meant the USB controller had failed and I'd be out of luck. He also said that if the port replacement didn't fix the issue he wouldn't charge me and refund my original payment (which impressed the hell out of me given the time he had already put into it and there was no guarantee that the extra work would fix it). This was late afternoon on Valentine's Day... he said that he'd get to swapping out the port the next day but an hour later called back to tell me that he replaced the port and flash was successful. I wish everyone was as straightforward in communication and dedicated to their job.
So yeah, MobileTechVideos is legit, Josh is a rock star, and send those guys your phone if something really screwy happens. They will take the time and go above and beyond if necessary to fix it, and you will absolutely get your money's worth.
Hoping that no one else is "lucky" enough to have their USB port fail mid-flash, but if your symptoms look like mine a bad port might be your problem.

I've heard nothing but good things about them. I've never used them myself, but I have directed a couple of people to them and heard nothing but glowing reviews.

Cool I managed to finally back up my sd card after a few attempts with a bad port (went out after a month of having the phone). I've been on a rotating batteries off a wall charger system, but need to odin because everytime I get down to 110-120 ish mb of internal memory my charge says low memory blah blah, I clear cache, play store , etc.
Needless to say people have said resorting back to stock ep4 etc with Odin should work, but I'm afraid mid flash something will happen. I have to jam the cord in, wrap extremenly tight while holding the phone at a perfect angle and sometimes it still will beep like being disconnected.

I have no idea if this would be possible for you, but I wonder if Mobile Odin could help you?