This is intended for people which run KIES and device is not seen, neither the message "connecting..." appear on KIES, and MTP application does not start on Samsung galaxy.
If you moved com.android.* and com.sec.android.* into some path which is not /data/data you may have this problem. At least this is what happend to me, after I moved file back MTP start and Kies recognize the device.
never moved anything it simply does not work on Windows 7 32bit.
no magic helped ... no formating internal sd nor anything else ... i've read whole fracking day on the web how to deal with this issue and none of the solution worked.
SGS GT-i9000 ECLAIR.XFJM3 rooted
disabling launcherpro fixed it for me.
im told other launchers cause issues too
Eh, really, problems on Win 7 32bit? Haha that's so strange because it works almost flawlessly on Windows 7 64bit. Perhaps the first time there's better support for 64bit than 32bit.
Yes, you MUST run TWlauncher (standard launcher in Touchwiz) and if you got Windows 7, you might wanna download some third party drivers.
I'm on Windows 7 64bit and I downloaded the win7 x64 samsung galaxy s drivers form softpedia.
well the mtp driver doesnt install on my 64 bit computer.
It works on windows 7 32 and 64 bit just fine
No third party drivers and no magic. It's all down to individual system config otherwise it would be the same for everybody.
Incidentally, there is an update out for Kies taking it to version 1.5.1.10074_45
g0c said:
never moved anything it simply does not work on Windows 7 32bit.
no magic helped ... no formating internal sd nor anything else ... i've read whole fracking day on the web how to deal with this issue and none of the solution worked.
SGS GT-i9000 ECLAIR.XFJM3 rooted
Click to expand...
Click to collapse
have you googled for FileSearcherforKiesFix and tried that? the only thing that fixed it for me.
Strange. Kies works fine on my both computers: Win7 x64 and WinXP. Had some issues before, but new Kies works without any issues.
hello all,
i got the gt-i9000 like 2 months back the kies s/w was workin fine for the first few days now the app itself fails to lauch even if the fone is not connected.
I have uninstalled and reinstalled kies s/w like a million times.
The installation is always successful but when i click on the kies icon to start the program nuthin happens :s
Please help.
Oh yeah i am running Win7 32bit legit.
BronzedDroid said:
Eh, really, problems on Win 7 32bit? Haha that's so strange because it works almost flawlessly on Windows 7 64bit. Perhaps the first time there's better support for 64bit than 32bit.
Click to expand...
Click to collapse
Works fine for W7 32bit flawlessly to. Also for me on 2.2 it works under launcher pro as well, added bonus of not having to use home switcher (or the like) every time I connect the phone
rocketpaul said:
well the mtp driver doesnt install on my 64 bit computer.
Click to expand...
Click to collapse
It works fine on my copy of Windows 7 64bit, but I have to switch to touchwiz, and go to driver recovery in the kies menu.
I use XP at home and at work.
From home with JP6 and Kies 1.5.3.10093_82 I can connect fine using a cheap USB cable and with phone having Samsung Kies as default running LauncherPro.
At work Kies cannot connect to the phone... it just says connecting, please wait.... all the time, its wierd...
I guess I have to remove all the USB hubs on the work computer.... Will install Windows 7 Pro 64 bit at work soon so... maybe ill just wait until then...
Kies not working with LauncherPro. You have to create a shortcut to MTP Application, when you connected the phone and selected Kies need to start with this shortcut.
This is the only way to connect Kies with LauncherPro.
Somewhere I read about this, LaucherPro not recognised like TW.
Hope this helps.
The only way I have ever ever gotten kies was following these steps:
1. Completely close kies
2. Connect your phone
3. Open up device manager, find I9000 (should be under portable devices), right-click and disable (if device manager lags after you click disable then unplug the phone)
4. Replugin the phone and wait for it to say connected on the phone's screen
5. Re-enable I9000 in device manager
6. Fire up Kies and it should connect
These steps have worked every time for me
ps: I'm on Windows 7 x64
http://arvindgaba.com/computer/sams...o-install-for-samsung-galaxy-s-kies-resolved/
Not tested but seems to be approved
I'm on linux so i never used kies. Jusi odin all the way and i have nothing to complain about
This issue has become rediculous. Samsung fail so much with this usb ****. I run Win 7 32 bit and kies previously worked and even when it occassionally wouldn't I used odin.
Now unfortunately the phone just isn't recognised even after various driver and spftware reinstallations and registry deletions etc... etc... etc....
Odin will bluescreen XP if it's running in a VirtualBox guest, but not after sending just enough to the phone to corrupt something. If you happened to be flashing your bootloader, congratulations, you just bricked your phone. Thankfully it wasn't the bootloader I was flashing and I can still get the phone into Odin mode; I'm gonna try to recover it when I get home to my Win7 desktop machine.
Heimdall does not support the Captivate Glide yet, and I tried Odin in Wine -- it doesn't see the phone. For the time being you *NEED* a native Windows machine to root the Glide -- the usual workarounds simply don't work.
You should NEVER flash or do anything with your phone without a proper setup. Heck, I wouldn't even flash without being on a laptop (for the battery) or a comp connected to a UPS.
This is good information to know but it would be incredibly stupid to flash while using an emulated OS. If you're on Linux or Mac, go to a friends house with Windows. It simply isn't worth the risk.
Thanks for the confirmation and to everyone else-don't do it. Just do things the right way.
It's a locally hosted VM running on a laptop, so yeah, I had the battery backup
I've done this before with other devices and this is the first time I've run into an issue where the VM actually broke things enough to corrupt stuff on the phone. Every other time it's been either, it went off without a hitch, or I can't quite bridge the connection from the host to the VM. Even from a theory standpoint, hey, companies use VMs for critical server systems. There's nothing dicey about a VM, at least until you run into a weird bug like this.
It's just that in this particular case, in the particular combination of Odin, XP guest, and Ubuntu host, something goes horribly wrong insidie the VM and crashes out XP. Actually, it's worse than that -- my XP VM won't boot anymore. What the hell happened.... gotta be a bug in VirtualBox.
Oh well. Hey, that's the whole point of recovery mode, right?
Definitely just use a PC running Windows. It sounds like you know what you're doing but if you're flashing recovery or a radio image, theres no point in the extra risk. If you're just doing a ROM and already have recovery there, you should be fine because you can always drop a new ROM on the SD and reinstall from there.
I've never bricked a phone myself but I do all of my friends phones. I think the scariest I've had was upgrading WinMo on my friends old Blackjack from 5.5 to 6.5. The official flash program froze at 85% or so. I let it sit for an extra hour and was almost sure it would be bricked but thankfully once I pulled the battery on it, it booted right up to 6.5.
But things like that happening..I wouldn't even mess around with an emulated OS and pushing a flash of recovery or something. Best to just be safe and go to a friends house if you have to.
I'm curious if you would have had better results is you were using VMWare instead of Virtualbox.
I've not used Virtualbox before, but I've read that VMWare has superior performance and hardware pass-thru.
I use VMWare a LOT (like a whole, whole lot), and I've never had any sort of trouble with the hardware pass-thru.
ericpeacock79 said:
I'm curious if you would have had better results is you were using VMWare instead of Virtualbox.
I've not used Virtualbox before, but I've read that VMWare has superior performance and hardware pass-thru.
I use VMWare a LOT (like a whole, whole lot), and I've never had any sort of trouble with the hardware pass-thru.
Click to expand...
Click to collapse
I didn't have any passthrough problems with VirtualBox either... until I got this phone. It's a really oddball corner case. I wonder if Odin does something weird with the Windows USB drivers...
what i did was run parallels on mac, with a Windows 7 guest to flash rooted rom and then CWMR. now i just put the zip to flash on my sdcard which i can access fine on mac.
Hey guys, I have been trying to get Windows 7 Drivers to work properly with adb on my A100. I have a Virtual Machine of Windows 7 and I have manually added the USB device ID's to the VBox settings for the VM client, Windows 7 sees the device ok and will mount the device fine via MTP. I can even get the drivers to say that they are working properly for the device, but when it all comes down to it they aren't.
I have tried using the ADB driver from the Android SDK which of course won't work out of the box since the device ID's aren't made for the Iconia A100, however I modified them to match the vendor/device IDs, but still - no go. I can do ' adb devices' and it will either show the device as offline or will just say the name and serial#, but when I try to connect it either says 'device offline' or it will give me a adb protocol error.
I don't know what else to really try, and at this point I am really thinking Virtualbox isn't passing the USB properly to the Guest OS, but what is odd, is my HTC WildFire S will work fine with adb (same binary).
I have also tried the Acer drivers that are available on the Acer Website, as well as a few other device drivers that I can't recall off the top of my head.
I guess some people are wondering if this is working in Linux why am I so concerned about getting it to work in a Virtual Machine running Windows. In short the answer is: I am developing kernels and recovery for the A100 as many may already know, and I am working on some automated installers that are cross platform compatible and I need to test the Windows side of things before I make releases, yet it's a bit hard to do when Windows is such a PITA when it comes to anything Android.. Yea, I'm a Linux person I know it's obvious - but I need this working somehow in a Virtual Machine because I'm not willing to do a native install of Windows on any of my machines, simple as that lol..
Anyone who may have a Virtualbox install of Windows 7 (or vista) that has adb working with their A100, please let me know the adb drivers you used and if at all possible attach them here, or give me a direct link. I greatly appreciate the help guys!
Here is a snippet of the troubles:
Code:
List of devices attached
037c624643a033d7 device
C:\Users\Lance\Downloads\godmachine81-Acer-A100-TWRP-Installer\godmachine81-Acer
-A100-TWRP-Installer-c8ccd42>adb shell
error: protocol fault (status 72 6f 6f 74?!)
**Edit: I kinda found a solution to my own problem, but not a great one. The problem was with EHCI 2.0 in VirtualBox, when this setting is disabled it will allow adb to work correctly, however on Windows 7 it will break the USB host so there is no possible way to use the tablet period, with Windows XP however it works fine. Windows XP has the exact same issue, but the USB Hub will actually work without EHCI 2.0, not really sure if there is a workaround to the Windows 7 problem, but I didn't really mess with it long - I'd say one might be able to uninstall the USB adapter and reinstall it after disabling EHCI and then also reinstall the Acer drivers. I got tired of fooling with windows 7 and just installed a copy of XP, wrote the batch script for windows, and will soon be uninstalling most likely haha.. Hope this might be some good info for others who run into a similar issue
Let's see....Where do I start...
I've tried the Mac route....No luck in any successful root using Mac OS X. With that being said, I have done the following.
I have virtually booted my Mac OS X to simultaneously boot into Windows XP SP3 Home Edition using VMWare Fusion Professional Version 5.0.3 (1040386).
I went to this link here ( after deleting all Samsung drivers from previous tries and restarted windows ) and installed the driver on the Windows XP Virtual Machine.
SAMSUNG_USB_Driver_for_Mobile_Phones.zip (25.32MB)
I then went and downloaded two versions of Odin. Version 1.87 and Version 3.07.
I also downloaded Heimdall Suite V 1.4.0
I essentially followed the steps in this Youtube video by qbking77.
How to Root the Samsung Epic 4G on FC09 - Latest
With everything said and done, my phone isn't recognized in Odin or Heimdall. However, it's recognized in normal mode. It obviously doesn't root like that.
I put my phone in download mode, plug it in. Let it sit for at least 5 minutes even though it technically should be less than a minute for the USB detection to come up. It doesn't detect anything at all.
I've used 3 other cables.
I've double checked the settings with VMware Fusion for the USB Configuration. Essentially, when I have XP running, anything that is plugged in via USB will automatically connect to XP rather than OS X.
Any help on this would be great! Thanks in advance.
Edit
Edit
To my knowledge, heimdall was made to do the same thing as odin, but on Mac OSX and Linux. Try dual booting?
Sent from my SPH-D700 using Tapatalk 2
I have used a windows vm and throught vmware rooted my epic. I lack the mac and virtualizing a mac to virtualize a winblows box is too much fun for this lad.
Sent from my SPH-D700 using xda app-developers app
Djinn23 said:
I have used a windows vm and throught vmware rooted my epic. I lack the mac and virtualizing a mac to virtualize a winblows box is too much fun for this lad.
Click to expand...
Click to collapse
I'm not quite sure what you mean by this.
DarkXShadowX21 said:
I'm not quite sure what you mean by this.
Click to expand...
Click to collapse
I'm not sure what he means either, but maybe Heimdall didn't work because I think Heimdall and Odin files are packaged slightly differently.
Have you followed the instructions in post #2 in this thread?
The Windows issue may be the USB Driver. When I updated Windows version, my old driver failed to COM link with my phone in ODIN while I was still able to read and write to USB as well as gain adb access. I searched and found another poster stating the latest driver from Samsung fixed it. Worked for me as well. Try the link below.
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Disclaimer: Samsung, nor I, assume no responsibility; use at own risk... usual TOS.
Here, in case anyone has trouble finding the cwm-5.0.2.7-epic4g.tar (for ODIN) thanks to kennyglass123
Sent from my SPH-D700 using xda app-developers app
samep said:
The Windows issue may be the USB Driver. When I updated Windows version, my old driver failed to COM link with my phone in ODIN while I was still able to read and write to USB as well as gain adb access. I searched and found another poster stating the latest driver from Samsung fixed it. Worked for me as well. Try the link below.
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Disclaimer: Samsung, nor I, assume no responsibility; use at own risk... usual TOS.
Here, in case anyone has trouble finding the cwm-5.0.2.7-epic4g.tar (for ODIN) thanks to kennyglass123
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Thank you for some insight on this. I have switched out my Windows XP for Windows 7 Ultimate ( I've actually read a few people who used this on a virtual machine and it worked perfectly for them ) . I turned on the automatic updates and everything was updated. Windows 7 is working perfectly. The problem is still occurring though. I have used every version of Odin from 1.83 to 3.09. I put my SPH-D700 into download mode and if I configure vmware to "ask" for what to use when I plug it in in the USB menu, I've managed to get as far as the window popping up to allow me to select windows. I made it pop up by booting into download mode without the battery in and putting in after I put it into download mode. With that being said, nothing shows up in Odin still. I have used several drivers for this device. Here's the list of drivers I used:
Samsung USB Driver for Mobile Phones 1.3.8
Samsung USB Driver for Mobile Phones v1.5.14.0
Samsung USB Driver for Mobile Phones v1.5.27.0
SAMSUNG USB Driver for Mobile Phones ( No Version, default I believe )
Samsung Kies ( It downloads the default driver automatically )
I've also was trying to use this tar file:
SPH D700 FC09 8Gb REL.tar.md5
I have installed, uninstalled, and rebooted every time I did this to ensure that drivers would't conflict.
I even brought my phone to my neighbors house to use his XP machine. I brought the software with me to do this. I also had to update his USB drivers because of the yellow exclamation mark in the device manager menu. I did that and was able to fix his USB driver. It still didn't recognize my device. ( I believe it was his computer though because it's in really bad shape :/ )
I was told at one point that I could have a faulty secondary bootloader. If that's the case, is there a way to fix that myself? If that's not the case, I'm just not sure what to do at this point to root this phone. I've felt like I've exhausted all my options other than to find someone who has a decent windows machine and try with that.
I have a Mac OS X 10.8.4 and tried using Heimdall. That didn't work at all. From my understanding, Heimdall is used to root? Flash devices? Both? Regardless, it didn't work when I tried using it on Mac. Hence why I am using VMWare Fusion Pro ( The latest version before the newest 6 that just came out ) with Windows 7 Ultimate.
If there is anything that I am missing, anything at all that I could successfully root this phone with the methods I have been trying, some information on how to do this would be great! I've been trying to root this phone for quite awhile now with no success.
I would give the tar a try that you gave me but without Odin recognizing the device, I have no way of being able to do anything. That "COM" never shows up. Currently, I have the Samsung USB Driver for Mobile Phones v1.5.14.0 driver installed because that is the exact one from the Samsung website specifically for the SPH-D700.
jeffreyjicha said:
To my knowledge, heimdall was made to do the same thing as odin, but on Mac OSX and Linux. Try dual booting?
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
I haven't tried boot camp with windows yet. I used to have a dual boot set up that way but I have not set that back up yet. That is one avenue I have not tried thus far. I may actually give that a go just for kicks. As for as my previous post goes, I've been just working at it through VMWare Fusion Pro which is a virtual machine for Windows.
jeffreyjicha said:
I'm not sure what he means either, but maybe Heimdall didn't work because I think Heimdall and Odin files are packaged slightly differently.
Have you followed the instructions in post #2 in this thread?
Click to expand...
Click to collapse
Thank you for the link to this specific thread. I actually have not come across that one yet. I appreciate you linking me up with it! I'll be reviewing that thread tomorrow and see if I come across something useful in it.
DarkXShadowX21 said:
Thank you for some insight on this. I have switched out my Windows XP for Windows 7 Ultimate ( I've actually read a few people who used this on a virtual machine and it worked perfectly for them ) . I turned on the automatic updates and everything was updated. Windows 7 is working perfectly. The problem is still occurring though. I have used every version of Odin from 1.83 to 3.09. I put my SPH-D700 into download mode and if I configure vmware to "ask" for what to use when I plug it in in the USB menu, I've managed to get as far as the window popping up to allow me to select windows. I made it pop up by booting into download mode without the battery in and putting in after I put it into download mode. With that being said, nothing shows up in Odin still. I have used several drivers for this device. Here's the list of drivers I used:
Samsung USB Driver for Mobile Phones 1.3.8
Samsung USB Driver for Mobile Phones v1.5.14.0
Samsung USB Driver for Mobile Phones v1.5.27.0
SAMSUNG USB Driver for Mobile Phones ( No Version, default I believe )
Samsung Kies ( It downloads the default driver automatically )
I've also was trying to use this tar file:
SPH D700 FC09 8Gb REL.tar.md5
I have installed, uninstalled, and rebooted every time I did this to ensure that drivers would't conflict.
I even brought my phone to my neighbors house to use his XP machine. I brought the software with me to do this. I also had to update his USB drivers because of the yellow exclamation mark in the device manager menu. I did that and was able to fix his USB driver. It still didn't recognize my device. ( I believe it was his computer though because it's in really bad shape :/ )
I was told at one point that I could have a faulty secondary bootloader. If that's the case, is there a way to fix that myself? If that's not the case, I'm just not sure what to do at this point to root this phone. I've felt like I've exhausted all my options other than to find someone who has a decent windows machine and try with that.
I have a Mac OS X 10.8.4 and tried using Heimdall. That didn't work at all. From my understanding, Heimdall is used to root? Flash devices? Both? Regardless, it didn't work when I tried using it on Mac. Hence why I am using VMWare Fusion Pro ( The latest version before the newest 6 that just came out ) with Windows 7 Ultimate.
If there is anything that I am missing, anything at all that I could successfully root this phone with the methods I have been trying, some information on how to do this would be great! I've been trying to root this phone for quite awhile now with no success.
I would give the tar a try that you gave me but without Odin recognizing the device, I have no way of being able to do anything. That "COM" never shows up. Currently, I have the Samsung USB Driver for Mobile Phones v1.5.14.0 driver installed because that is the exact one from the Samsung website specifically for the SPH-D700.
Click to expand...
Click to collapse
I wish I took better notes when solving this... I can't help the MAC Heimdall method but if you want to get Windows working, I'd stay with that USB driver and try installing Microsoft Visual Basic Power Packs 3.0 I'm also using ODIN3 v1.85. You didn't mention the PIT Victory file; it's needed if following the un-brick method with repartition enabled.
Funny thing about newer Windows versions, they're lighter and don't include needed packages to develop.
My recall is bad; I've rooted two different phones and setup to theme apk's again and downloaded several packages and depends and can't recall which package needed the depends for Windows... but looking at my Windows setup, I can at least tell you what I installed. The Visual Basic auto-installer works with Windows to tell you what version of Visual Basic you need for your applications when you attempt an install so follow the guidance it gives if it suggests another Visual Basic Version. I know I needed java for adb and Android SDK and I had to modify Environmental Variables to allow those applications to see each other but I don't think you need all that to root. Hope that helps some; maybe someone else more savvy with Windows or Heimdall can jump in and help.
Edit: Forgot to mention that you should open a new ODIN session for each file pushed. Once ODIN is opened, hold power and 1 button on slide-out kb while plugging the USB cable in. You should see the COM added within seconds, not minutes. The battery can stay out while using USB with ODIN; the intent is to prevent a reboot after file install so you can unplug USB after it attempts to reboot (it cannot without a battery), close ODIN and re-open ODIN and enter download mode to install the cwm recovery tar. If you get that far, you don't actually have to boot that rooted tar; just install battery, three finger salute into recovery and flash a MTD custom ROM; all customs ROMs in forum should auto-convert from BML to MTD (or you can stay with the rooted stock or flash custom BML ROM... Important to remember there is no autoconvert from MTD back to BML; that's what ODIN with repartition and PIT file is for as well as recovering a semi-bricked phone). Good Luck.
If Odin still does not recognize it borrow someone's thick BlackBerry cable.
Good one; forgot about that. My Samsung cable didn't work so the wife and I swapped cables long ago. I got her HTC USB cable and it has served me well except that the outer shell has frayed at and around the connectors.
Sent from my SPH-D700 using xda app-developers app
samep said:
I wish I took better notes when solving this... I can't help the MAC Heimdall method but if you want to get Windows working, I'd stay with that USB driver and try installing Microsoft Visual Basic Power Packs 3.0 I'm also using ODIN3 v1.85. You didn't mention the PIT Victory file; it's needed if following the un-brick method with repartition enabled.
Funny thing about newer Windows versions, they're lighter and don't include needed packages to develop.
My recall is bad; I've rooted two different phones and setup to theme apk's again and downloaded several packages and depends and can't recall which package needed the depends for Windows... but looking at my Windows setup, I can at least tell you what I installed. The Visual Basic auto-installer works with Windows to tell you what version of Visual Basic you need for your applications when you attempt an install so follow the guidance it gives if it suggests another Visual Basic Version. I know I needed java for adb and Android SDK and I had to modify Environmental Variables to allow those applications to see each other but I don't think you need all that to root. Hope that helps some; maybe someone else more savvy with Windows or Heimdall can jump in and help.
Edit: Forgot to mention that you should open a new ODIN session for each file pushed. Once ODIN is opened, hold power and 1 button on slide-out kb while plugging the USB cable in. You should see the COM added within seconds, not minutes. The battery can stay out while using USB with ODIN; the intent is to prevent a reboot after file install so you can unplug USB after it attempts to reboot (it cannot without a battery), close ODIN and re-open ODIN and enter download mode to install the cwm recovery tar. If you get that far, you don't actually have to boot that rooted tar; just install battery, three finger salute into recovery and flash a MTD custom ROM; all customs ROMs in forum should auto-convert from BML to MTD (or you can stay with the rooted stock or flash custom BML ROM... Important to remember there is no autoconvert from MTD back to BML; that's what ODIN with repartition and PIT file is for as well as recovering a semi-bricked phone). Good Luck.
Click to expand...
Click to collapse
I downloaded and installed Visual Basic. I'm not quite sure what that was suppose to do honestly. It didn't seem like anything changed. I still don't have the "COM" showing up in Odin 1.85. You are right about me forgetting to mention the "PIT" file. I actually did have that. ( victory_8G_100528.pit )
I loaded that into Odin as well as the ( SPH D700 FC09 8Gb REL.tar.md5 ) into the "PDA" section of Odin. Even though the "COM" didn't show up, I tried to run in anyways, this was the message I got in the console.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, these are the USB cables I am using. One is a short one and the one the the "B" on it is a normal length. I don't know what the "B" stands for but I don't know if that's a Blackberry one or not.
Also, will Odin still recognize the device if the MicroSD card is in? I actually never tried without taking it out.
Gotta say I agree with Kenny on the cable.
When I tried to replace my frayed cable with a "data sync" mini USB cable, it did not support adb.
Go with what you know; borrow or invest in a thick BlackBerry mini USB cable.
Can't guarantee but I think the cable is your problem.
Sent from my SPH-D700 using xda app-developers app
Blackberry USB Cable
kennyglass123 said:
If Odin still does not recognize it borrow someone's thick BlackBerry cable.
Click to expand...
Click to collapse
samep said:
Gotta say I agree with Kenny on the cable.
When I tried to replace my frayed cable with a "data sync" mini USB cable, it did not support adb.
Go with what you know; borrow or invest in a thick BlackBerry mini USB cable.
Can't guarantee but I think the cable is your problem.
Click to expand...
Click to collapse
Do one of you perhaps have any good sources for where I could get a decent inexpensive Blackberry USB Cable? I've looked up quite a few but since I'm not certain that I would make the correct purchase, perhaps one of you could point me in the right direction. I would appreciate it. Thanks
Would this be a decent one to buy?
New OEM BlackBerry Micro USB 1m Data Cable Charge & Sync 9900 9930 9800 9810
I just went ahead and purchased it. With a 30 day return policy and the price only being $1.99, it's not really that big of a deal. Lol! I suppose we just wait and see what happens when I receive this cable. Let the waiting begin...
DarkXShadowX21 said:
Do one of you perhaps have any good sources for where I could get a decent inexpensive Blackberry USB Cable? I've looked up quite a few but since I'm not certain that I would make the correct purchase, perhaps one of you could point me in the right direction. I would appreciate it. Thanks
Would this be a decent one to buy?
New OEM BlackBerry Micro USB 1m Data Cable Charge & Sync 9900 9930 9800 9810
I just went ahead and purchased it. With a 30 day return policy and the price only being $1.99, it's not really that big of a deal. Lol! I suppose we just wait and see what happens when I receive this cable. Let the waiting begin...
Click to expand...
Click to collapse
Yes! That one will definitely work. I usually buy 5 when I need them.
kennyglass123 said:
Yes! That one will definitely work. I usually buy 5 when I need them.
Click to expand...
Click to collapse
I just received the cable. It didn't work... :/
I'm uninstalling and reinstalling the Samsung USB Driver for Mobile Phones v1.5.14.0 driver. I'll try again to see what happens.
I suppose I need to diagnose this issue in order for this to work. I don't see how a Samsung Galaxy S1 Epic 4G SPH-D700 is drawing to much power in download mode though....
I even put my mac into safe mode so it would load a new set of kernals rather than the ones from the cache files. That still didn't work for 2 reasons.
1.) Heimdall Front-end doesn't recognize the device in download mode
2.) I'm not able to boot into windows with VMWare Fusion because that specific kernal isn't loaded into safe mode.
Only necessary kernals are being used in safe mode.... I'll keep updating as I go.
Update on my Windows 8 Pro USB driver issues.. but maybe old news.
@DarkXShadowX21,
I posted earlier that I had to install Microsoft Visual Basic Power Packs3. I found the note in my logs were referenced to a problem I was having with the HTC USB driver, AFIAK, I came upon a post somewhere in xda stating I needed it (exact reason or problem I had at that time not noted). So when I ran the installer, I got a pop-up stating I must first install Microsoft.NET Framework 2.0 Running that installer, I got another pop-up stating I needed Microsoft.NET Framework 3.0, instead. Both programs installed without error. Dependencies were determined by programs already installed in my system. Anyway, my PC now sees both phones correctly now. But looking at my update history, I'm getting security updates for Microsoft.NET Framework 3.5 and 4.5 (both versions).
Looking at my Windows Control Panel/Programs and Features, I have Microsoft Visual c++ 2005 Redistributable and Microsoft Visual c++ 2008 Redistributable x86 9.0.30729.4148 these show as being installed the next day but all I had in my notes following that was some developing programs I installed. The 30729 looks to be part of the Android-SDK bundle for Windows. I also have java installed for developing. IIRC, these are not requirements for ODIN; I had minimal effort getting ODIN to work on my wife's Windows7 laptop but at least for the HTC phone and drivers, Windows 8 Pro was lacking some tools. After getting the HTC USB drivers functional and rooting that phone, I only had to get the right Samsung USB driver to get ODIN COM to work. But since I did the HTC first, not sure if any of the above was needed for ODIN to see the Epic.
Good luck.
samep said:
@DarkXShadowX21,
I posted earlier that I had to install Microsoft Visual Basic Power Packs3. I found the note in my logs were referenced to a problem I was having with the HTC USB driver, AFIAK, I came upon a post somewhere in xda stating I needed it (exact reason or problem I had at that time not noted). So when I ran the installer, I got a pop-up stating I must first install Microsoft.NET Framework 2.0 Running that installer, I got another pop-up stating I needed Microsoft.NET Framework 3.0, instead. Both programs installed without error. Dependencies were determined by programs already installed in my system. Anyway, my PC now sees both phones correctly now. But looking at my update history, I'm getting security updates for Microsoft.NET Framework 3.5 and 4.5 (both versions).
Looking at my Windows Control Panel/Programs and Features, I have Microsoft Visual c++ 2005 Redistributable and Microsoft Visual c++ 2008 Redistributable x86 9.0.30729.4148 these show as being installed the next day but all I had in my notes following that was some developing programs I installed. The 30729 looks to be part of the Android-SDK bundle for Windows. I also have java installed for developing. IIRC, these are not requirements for ODIN; I had minimal effort getting ODIN to work on my wife's Windows7 laptop but at least for the HTC phone and drivers, Windows 8 Pro was lacking some tools. After getting the HTC USB drivers functional and rooting that phone, I only had to get the right Samsung USB driver to get ODIN COM to work. But since I did the HTC first, not sure if any of the above was needed for ODIN to see the Epic.
Good luck.
Click to expand...
Click to collapse
For Windows 7,
I went ahead and downloaded this
Microsoft .NET Framework 4 (Standalone Installer). I actually downloaded on top of the download you provided me with. I'm pretty sure this is ok because this is the most updated version of .NET Framework for Windows 7. After the installation, nothing happened by the way. I didn't get a pop up asking to update anything further. I have 3.0 installed and the version for Windows 7 that I provided.
As far as setting up all the additional programs for the HTC drivers, I don't really need to do that since this is a Samsung device obviously. I understand you are stating that to explain that you were able to get your Samsung device seen after installing drivers for the HTC and finding the correct driver.
As far as finding the correct driver, I suppose I need to figure out EXACTLY which driver it is that is going to allow Odin to recognize the SPH-D700 in "Download Mode".
I used the Samsung USB Driver for Mobile Phones v1.5.14.0 only because I found a source from Samsung directly that this is the correct driver for this device.
I've also read that Samsung Kies was able to install the default Samsung drivers for most Samsung devices and that also have worked for them. It didn't work for me.
After the installation of .NET Framework I went ahead and tried to plug in my device to see if Odin would recognize it.
COM Never showed up.
I left the USB cable in, removed the battery, put the battery back to to show this pop up.
Ever after I click windows. Nothing showed up in Odin....